Quote:
Originally Posted by [ACL]
If you are doing the upgrade to frx6 i can see a potential issue. the setup to mount the ext2 is using loop0 as well, and thats wht is needed for the modules. So modules will need to go back to loop3
well when you adb into the system. look for this
/system/lib/modules/2.6.27.46-01268-ga175a7c.sqsh
This has to be there before android starts. The initrd should mount this and make a link back to modules under the correct version. So something in there is failing.
apps? never tried apps via adnroidupdate. are the files getting copied over correctly?
edit: oops looks like nate cleaned up my mess and already put everything back to loop3 .. good looking out.
|
For the install script, I have it loop mount on loop0, but as soon as the file copy is done, it deletes that mount. When you originally committed it, loop3 was not being made in MAKEDEVS, so I added that, but I don't think you ever committed the change to move modules to loop0 (probably were just testing it).
For depmod, our version is pretty dumb. It doesn't have the ability to accept any commands, so it will only depmod if /system/lib/modules/uname/ is there. This is why depmod during the install script fails and gives that error in the bootlog.txt.
Installing apps using the androidupdate.tgz is a little weird. The APK's have to be formatted properly, or they will not install. For example, Superuser.apk works perfectly fine, but I cannot get other APK's like Terminal to install from my Titanium Backup if I just toss it in the /system/app folder.
Also, I think I've ironed out the issues with root. Titanium Backup installs Busybox to the data partition where it looks for it just fine, but other programs don't know to look there, so they fail. If you download Busybox from the Market, it thinks there is no space left in system, but you can install it to /system/xbin anyway... Once Busybox is installed, ES File Explorer (et al) allow root access without issues (after a restart).