Quote:
Originally Posted by Lmiller1708
So you guys still can't write to the cache partition?
If so try changing this line on the MAKEDEV's
mknod -m 0666 /dev/mtd/mtd4 c 90 6
to
mknod -m 0666 /dev/mtd/mtd4 c 90 8
I stated this before but never looked at the push, but I was also uncertain about it... Sorry about that. 
But maybe the cache getting corrupt is something different... Kinda like the losing of some widgets on the Android home screen?
As for not being able to write to the recovery partition are you still using the same starting place as before. 0x4000000?
I won't be able to test for a while today for I forgot my phone at home.  |
I say test it out. move the dalvik cache to the cache partition and beat it up..
. im using the default mtdparts on git. But i cant format the recovery partition it since it keeps saying its protected. So we may need to shift stuff around a bit.
Quote:
Originally Posted by Lmiller1708
Nate if you keep getting your Android install stuck in a bootloop it means you are most likely having some permission issues.
Specifically this file: /system/etc/dbus.conf
Here is what the Vogue changes them too...
chown 1002:1002 /system/etc/dbus.conf
chmod 0444 /system/etc/dbus.conf
@ACL,
How are you creating your andriodinstall.tgz?
I'm thinking we are having issues with permissions coming right from the tgz.
Here is mine... Probably not right but it works once I run the fixperm script
Code:
echo "Making androidupdate.tar"
cd androidupdate
chown -R 0:0 *
tar -cvzf ../androidupdate.tar *
chown -R lance:lance *
cd ..
echo "Moving androidupdate.tar"
cp androidupdate.tar ~/Desktop/Android/1.Complete_Build/ANDROID/
echo "Making androidinstall.tar"
cd androidinstall
chown -R 0:0 *
tar -cvzf ../androidinstall.tar *
chown -R lance:lance *
cd ..
echo "Moving androidinstall.tar"
cp androidinstall.tar ~/Desktop/Android/1.Complete_Build/ANDROID/
cp install-seq.sh ~/Desktop/Android/1.Complete_Build/ANDROID/
echo "Completed..."
|
Hmm bootloop you say ? we need logs bro. Permissions issues are easy to spot since android bitches about it. So yes you could be right, the android may have bad permissions on the tgz which we need to fix. I havent had a boot loop in ages tho so that my be something else.