Related
This has been mentioned elsewhere, even by me but I think it has fallen through the cracks. It may be an unrelated problem but when trying to use CWM to do a backup it fails saying that /system cannot be mounted.
The issue it may be related to is that CWM on boot installed via either method fails to stick past the initial reboot. It looks to me that it is restoring an image on start up each time undoing any changes. It must not be changing everything because the root sticks. I have made sure init.d support has been installed. The phone is an AT&T branded MB865, has been rooted and is running stock 2.3.6 firmware.
Any pointers will be appreciated and I come from an embedded Linux background so I'm willing to help out, but why re-invent the wheel if this has already been solved.
cdlees said:
This has been mentioned elsewhere, even by me but I think it has fallen through the cracks. It may be an unrelated problem but when trying to use CWM to do a backup it fails saying that /system cannot be mounted.
The issue it may be related to is that CWM on boot installed via either method fails to stick past the initial reboot. It looks to me that it is restoring an image on start up each time undoing any changes. It must not be changing everything because the root sticks. I have made sure init.d support has been installed. The phone is an AT&T branded MB865, has been rooted and is running stock 2.3.6 firmware.
Any pointers will be appreciated and I come from an embedded Linux background so I'm willing to help out, but why re-invent the wheel if this has already been solved.
Click to expand...
Click to collapse
Update your busybox .
I had thought of that, running BusyBox 1.20, 1.20.1 fails to install. As 1.20 is fairly recent I doubt this is the problem. The initial install of CWM via Power Boost works, so busybox is installed correctly. An old version of busy box wouldn't explain the not being able to mount /system as as far as I know it isn't used by CWM for this purpose, but I could be wrong. But it could explain the CWM not sticking problem.
Further investigation shows that the system partition does not change between doing a PowerBoost CWM install and after a reboot meaning that there is nothing screwy going on like the boot sequence over writing files in system so that CWM isn't persistent. Can anyone enlighten me on the boot sequence so I can take a look to see if anything is getting over written?
This of course gets me no closer on why CWM can't mount system but it is just one of two problems.
cdlees said:
Further investigation shows that the system partition does not change between doing a PowerBoost CWM install and after a reboot meaning that there is nothing screwy going on like the boot sequence over writing files in system so that CWM isn't persistent. Can anyone enlighten me on the boot sequence so I can take a look to see if anything is getting over written?
This of course gets me no closer on why CWM can't mount system but it is just one of two problems.
Click to expand...
Click to collapse
Have you tried "fix permissions" in cwm?.then reboot and see if it still gives you that error when you go back into cwm
Sent from my MB865 using xda premium
I'm pretty sure I had already tried all that, but just to be sure I did it all again, here is what happened
PowerBoost CWM install
Reboot into CWM
CWM Fix permissions
CWM recovery restart
CWM backup
Failed due to not being able to mount /system
Power cycled, didn't boot into CWM
Since permissions may have changed once CWM Fix permissions had been run
PowerBoost CWM install
Reboot
Enters CWM
Reboot
Didn't boot into CWM
Surely I'm not the only one seeing this problem?
cdlees said:
I'm pretty sure I had already tried all that, but just to be sure I did it all again, here is what happened
PowerBoost CWM install
Reboot into CWM
CWM Fix permissions
CWM recovery restart
CWM backup
Failed due to not being able to mount /system
Power cycled, didn't boot into CWM
Since permissions may have changed once CWM Fix permissions had been run
PowerBoost CWM install
Reboot
Enters CWM
Reboot
Didn't boot into CWM
Surely I'm not the only one seeing this problem?
Click to expand...
Click to collapse
Well once u reboot your phone it goes into cwm. When u reboot from cwm its suppose to go into rom not cwm again.
Sent from my MB865 using xda premium
Have u tried manually mounting system in cwm and see what happens?
Also what version of busybox do u have installed? . Should be 19.4. Nothing higher.
Sent from my MB865 using xda premium
rdavisct said:
Well once u reboot your phone it goes into cwm. When u reboot from cwm its suppose to go into rom not cwm again.
Click to expand...
Click to collapse
I realise this but I was under the impression that if the phone is power cycled or reboot from Android then it will go into CWM on restart.
Still doesn't explain the inability to mount /system
rdavisct said:
Have u tried manually mounting system in cwm and see what happens?
Also what version of busybox do u have installed? . Should be 19.4. Nothing higher.
Click to expand...
Click to collapse
I'm running BusyBox 1.19.4. I just tried to manually mount /system from CWM, same problem. Just to make sure that mounting works I mounted a few other things that were not already mounted.
cdlees said:
I'm running BusyBox 1.19.4. I just tried to manually mount /system from CWM, same problem. Just to make sure that mounting works I mounted a few other things that were not already mounted.
Click to expand...
Click to collapse
Id say rsd flash 2.3.5 . Root. Install atrix bootstrapper. And see if problem persists.
Sent from my MB865 using xda premium
Ok, reflashed back to 2.3.5, rooted, Bootstraped, tried to mount /system from CWM, no luck, same error. Tried to install CWM on boot using the zip from CWM, didn't seem to work. Tried the fix permissions script from CWM, still doesn't work.
There is something up with this phone, is it possible that Motorola has decided to be extra evil.
I till haven't gotten very far with this but I have some more information on what may be the issue. I can get it to update the system partition by flashing a zip. I decided to give it a go with SCV6 as I was sure I'd be able to recover if it failed. It flashed just fine but on reboot it dropped out to the fastboot screen. This is where I decided to get creative, I mounted the system.img file from from the stock fimware, deleted its contents and replaced it with what is in the SCV6 zip system directory, after all this is what CWM will be doing as far as I could tell. I then flashed this file using moto-fastboot. It failed on boot dropping out at fastboot again.
Running out of time for the day I decide to just restore it back to stock, I have a Linux script to automate the process, on completion, same failure. What had happened is I had mounted the system.img file to look inside and then unmounted it, and this may have changed a signature or checksum in the filesystem so it failed to boot. Re-extracting the system.img file and flashing again worked fine.
Are there different versions of the bootloader that do different things? Mine just being a total pain and not allowing much at all.
Just realised the install script puts in a whole pile of symlinks, not having them would cause a boot failure on creating the image the way I did. It will be possible to create an image with said symlinks.
This though fails to explain while mounting and then unmounting the system.img makes it fail.
I may just be talking to myself here but I have some relevant information relating to the original problem of not being able to mount /system which is why flashing doesn't work as well as the flashing scripts don't actually check to see if the system partition is mounted, they just assume it is.
In CWM if you try to mount /system then look at the log it says
mount: mounting /dev/block/mmcblk1p20 on /system failed: Invalid argument
Now the question is, what is the mount line it is trying to execute and which argument is invalid? Can someone with a working phone go into CWM, unmount /system if its mounted by default and then mount it, look at the log and tell me what it says regarding the mounting of system.
Here is the really interesting part, once the phone has booted and checking what is actually mounted on /system its /dev/block/mmcblk1p21, so CWM is trying to mount the wrong partition
I worked out the problem, I was using the Razr bootstrap which obviously mounts a different partition as system, I had followed some instructions that I read somewhere that the Razr version worked and gave a link to said package. Once I swapped to the atrix 2 version it all works, I'll attempt to install SCV6 tomorrow night when I have some time.
can't mount /system!
[/COLOR]
cdlees said:
I till haven't gotten very far with this but I have some more information on what may be the issue. I can get it to update the system partition by flashing a zip. I decided to give it a go with SCV6 as I was sure I'd be able to recover if it failed. It flashed just fine but on reboot it dropped out to the fastboot screen. This is where I decided to get creative, I mounted the system.img file from from the stock fimware, deleted its contents and replaced it with what is in the SCV6 zip system directory, after all this is what CWM will be doing as far as I could tell. I then flashed this file using moto-fastboot. It failed on boot dropping out at fastboot again.
Running out of time for the day I decide to just restore it back to stock, I have a Linux script to automate the process, on completion, same failure. What had happened is I had mounted the system.img file to look inside and then unmounted it, and this may have changed a signature or checksum in the filesystem so it failed to boot. Re-extracting the system.img file and flashing again worked fine.
Are there different versions of the bootloader that do different things? Mine just being a total pain and not allowing much at all.
Click to expand...
Click to collapse
Can you please post the link/s, i have the same problem as you
I managed to successfully compile CWM Recovery from sources for A9, but with a few issues (key-mapping where touch buttons don't work, etc)
Decided to take the jump to compiling CM.
Modified the extract-files from sgs2 but I have no knowledge when it comes to libraries, proprietary files, 'blobs', what the options in the makefiles mean,etc.
I have absolutely no idea what I'm supposed to do next, as compiling for unsupported devices doesn't give me many search results. I have the CyanogenMod GB branch synced, and a device tree for A9 set up, with a few file modifications done.
Any and all help, references, links to explanations are welcome.
Managed to compile it, finally, check posts below.
Sources: https://github.com/Siarc/a9
Shark- said:
I managed to successfully compile CWM Recovery from sources for A9, but with a few issues (key-mapping where touch buttons don't work, etc)
Decided to take the jump to compiling CM.
Modified the extract-files from sgs2 but I have no knowledge when it comes to libraries, proprietary files, 'blobs', what the options in the makefiles mean,etc.
I have absolutely no idea what I'm supposed to do next, as compiling for unsupported devices doesn't give me many search results. I have the CyanogenMod GB branch synced, and a device tree for A9 set up, with a few file modifications done.
Any and all help, references, links to explanations are welcome.
Sources: https://github.com/Siarc/a9
Click to expand...
Click to collapse
Dude, the only help i could give is test the ROM , let me know when you want it and i will be more than happy to help :fingers-crossed:
I've spent a lot of time, and it's simply not worth it, cannot even manage to get it to compile in the right directory. I can't believe there are so many people who have the knowledge but not one single reply.
CM7!
Flash at your OWN RISK.
I will not be held responsible if you brick/mess up your device.
This is meant for the A9, not anything else.
This is an experimental build, I cannot even guarantee that it will boot.
==========================================================================
Download : http://www.mediafire.com/?f85rdpx0kvbtmvh
Code:
SHA1: dd40f0cef5b40d8a8b5b3966e29074889bad9b8e
MD5: c2a28a1d012f2b3a4a1f79ead24c8d66
I'll be damned if you even get to the standby screen. I don't have the time to test it right now and restore backups if it doesn't work.
If it doesn't work, the screen will probably go blank and you should reboot into recovery (or you may get a bootloop)
If you think it has got past boot, try and run logcat and dmesg and post back the logs so I can know what went wrong.
Using dmesg and logcat: http://www.flashmyandroid.com/forum...ogcat-and-dmesg-outputs-for-trouble-shooting-!
Before flashing:
Backup all sdcard contents.
Make nandroid backup via CWM, test restore it, copy to computer just in case.
-------------------------------------------------------------------------------------------------------------
Make sure you have a nandroid backup (and test it out! if you get MD5 mismatch like I did, you'll be spending a lot more time getting your phone restored) on your phone /sdcard as well as your computer.
A microSD card reader (in case the sdcard gets wiped and you have no means of transferring your nandroid backup)
-------------------------------------------------------------------------------------------------------------
Instructions:
Place zip file on /sdcard
Flash zip via CWM (If you don't already have it, this is the one: http://www.mediafire.com/?aen9w6uinz923hy)
Wipe /data, /cache and dalvik-cache from CWM.
Reboot
Used the stock kernel, device tree is over here: https://github.com/Siarc/a9
[I have also tried manually flashing a previous build's system image, it wouldn't work, restored nandroid, everything back to normal.]
Only testers who are comfortable flashing ROMs and have a computer with fastboot working should try it out, in case there is a need to flash the recovery partition.
Shark- said:
Flash at your OWN RISK.
I will not be held responsible if you brick/mess up your device.
This is meant for the A9, not anything else.
This is an experimental build, I cannot even guarantee that it will boot.
==========================================================================
Download : http://www.mediafire.com/?f85rdpx0kvbtmvh
Code:
SHA1: dd40f0cef5b40d8a8b5b3966e29074889bad9b8e
MD5: c2a28a1d012f2b3a4a1f79ead24c8d66
I'll be damned if you even get to the standby screen. I don't have the time to test it right now and restore backups if it doesn't work.
If it doesn't work, the screen will probably go blank and you should reboot into recovery (or you may get a bootloop)
If you think it has got past boot, try and run logcat and dmesg and post back the logs so I can know what went wrong.
Using dmesg and logcat: http://www.flashmyandroid.com/forum...ogcat-and-dmesg-outputs-for-trouble-shooting-!
Before flashing:
Backup all sdcard contents.
Make nandroid backup via CWM, test restore it, copy to computer just in case.
-------------------------------------------------------------------------------------------------------------
Make sure you have a nandroid backup (and test it out! if you get MD5 mismatch like I did, you'll be spending a lot more time getting your phone restored) on your phone /sdcard as well as your computer.
A microSD card reader (in case the sdcard gets wiped and you have no means of transferring your nandroid backup)
-------------------------------------------------------------------------------------------------------------
Instructions:
Place zip file on /sdcard
Flash zip via CWM (If you don't already have it, this is the one: http://www.mediafire.com/?aen9w6uinz923hy)
Wipe /data, /cache and dalvik-cache from CWM.
Reboot
Used the stock kernel, device tree is over here: https://github.com/Siarc/a9
[I have also tried manually flashing a previous build's system image, it wouldn't work, restored nandroid, everything back to normal.]
Only testers who are comfortable flashing ROMs and have a computer with fastboot working should try it out, in case there is a need to flash the recovery partition.
Click to expand...
Click to collapse
I will test it bro..
thnks for compiling.
Shark- said:
Flash at your OWN RISK.
I will not be held responsible if you brick/mess up your device.
This is meant for the A9, not anything else.
This is an experimental build, I cannot even guarantee that it will boot.
==========================================================================
Download : http://www.mediafire.com/?f85rdpx0kvbtmvh
Code:
SHA1: dd40f0cef5b40d8a8b5b3966e29074889bad9b8e
MD5: c2a28a1d012f2b3a4a1f79ead24c8d66
I'll be damned if you even get to the standby screen. I don't have the time to test it right now and restore backups if it doesn't work.
If it doesn't work, the screen will probably go blank and you should reboot into recovery (or you may get a bootloop)
If you think it has got past boot, try and run logcat and dmesg and post back the logs so I can know what went wrong.
Using dmesg and logcat: http://www.flashmyandroid.com/forum...ogcat-and-dmesg-outputs-for-trouble-shooting-!
Before flashing:
Backup all sdcard contents.
Make nandroid backup via CWM, test restore it, copy to computer just in case.
-------------------------------------------------------------------------------------------------------------
Make sure you have a nandroid backup (and test it out! if you get MD5 mismatch like I did, you'll be spending a lot more time getting your phone restored) on your phone /sdcard as well as your computer.
A microSD card reader (in case the sdcard gets wiped and you have no means of transferring your nandroid backup)
-------------------------------------------------------------------------------------------------------------
Instructions:
Place zip file on /sdcard
Flash zip via CWM (If you don't already have it, this is the one: http://www.mediafire.com/?aen9w6uinz923hy)
Wipe /data, /cache and dalvik-cache from CWM.
Reboot
Used the stock kernel, device tree is over here: https://github.com/Siarc/a9
[I have also tried manually flashing a previous build's system image, it wouldn't work, restored nandroid, everything back to normal.]
Only testers who are comfortable flashing ROMs and have a computer with fastboot working should try it out, in case there is a need to flash the recovery partition.
Click to expand...
Click to collapse
I did as u said..
i wiped data / chache/ delvik cache .. But not able to install..
i m writing the exact error...
" Installing update..
assert failed : getprop("ro.product.device")== "a9" || getprop("ro.build.product") =="a9" ||getprop("ro.product.board")== "a9"
E: Error in /sdcard/cm7-20120911-UNOFFICIAL-a9.zip
(status 7)
Installation aborted. "
vijetaverma said:
I did as u said..
i wiped data / chache/ delvik cache .. But not able to install..
i m writing the exact error...
" Installing update..
assert failed : getprop("ro.product.device")== "a9" || getprop("ro.build.product") =="a9" ||getprop("ro.product.board")== "a9"
E: Error in /sdcard/cm7-20120911-UNOFFICIAL-a9.zip
(status 7)
Installation aborted. "
Click to expand...
Click to collapse
In the /system directory, edit the build.prop file and add this line:
Code:
ro.build.product=a9
Make sure it persists after a reboot.
Great work Friend's
Shark- said:
In the /system directory, edit the build.prop file and add this line:
Code:
ro.build.product=a9
Make sure it persists after a reboot.
Click to expand...
Click to collapse
Bro please reply fast cant Waite now.I also want to install cm7
Shark- said:
In the /system directory, edit the build.prop file and add this line:
Code:
ro.build.product=a9
Make sure it persists after a reboot.
Click to expand...
Click to collapse
just woke up..
I m adding that line.. will Post result in a while
---------- Post added at 10:28 AM ---------- Previous post was at 10:00 AM ----------
Still not able to install..
Error
"
same as previous one..
(status 7)
Installation aborted
"
Any more info like the previous one? Ro.build anything?
Sent from my A9 using xda app-developers app
Shark- said:
Any more info like the previous one? Ro.build anything?
Sent from my A9 using xda app-developers app
Click to expand...
Click to collapse
all same as before..nothing changed..
Can you post the complete log
Sent from my A9 using xda app-developers app
There is no systemui.apk in the build, so it's never gonna boot up
I think without kernel sources developing cm7 is impossible.
Anyway I really appreciate the effort you took in trying to compile cm7 for our device
Sent from my A9 using xda app-developers app
SystemUI can be copied in the makefiles , and I wouldn't say its impossible to compile, just very difficult.
Sent from my A9 using xda app-developers app
No phone.apk, conversations.apk camera.apk, systemui.And many permissions xml file are missing.You can't use stock apk instead of these, they need to be build specially for our device.
The reason why I said it is impossible is I have seen very good devs finding it very difficult to build cm7 for devices having kernel source released.our device don't even have kernel source available.Normal gingerbread kernel without any modification won't boot up cm7.
Sent from my A9 using xda app-developers app
Well thanks for the encouragement
Sent from my A9 using xda app-developers app
mahfoozceecy said:
There is no systemui.apk in the build, so it's never gonna boot up
I think without kernel sources developing cm7 is impossible.
Anyway I really appreciate the effort you took in trying to compile cm7 for our device
Sent from my A9 using xda app-developers app
Click to expand...
Click to collapse
Shark- said:
SystemUI can be copied in the makefiles , and I wouldn't say its impossible to compile, just very difficult.
Sent from my A9 using xda app-developers app
Click to expand...
Click to collapse
mahfoozceecy said:
No phone.apk, conversations.apk camera.apk, systemui.And many permissions xml file are missing.You can't use stock apk instead of these, they need to be build specially for our device.
The reason why I said it is impossible is I have seen very good devs finding it very difficult to build cm7 for devices having kernel source released.our device don't even have kernel source available.Normal gingerbread kernel without any modification won't boot up cm7.
Sent from my A9 using xda app-developers app
Click to expand...
Click to collapse
Shark- said:
Well thanks for the encouragement
Sent from my A9 using xda app-developers app
Click to expand...
Click to collapse
So guys is anyone working on CM7 for A9 ?
MiUi Rom released..
http://forum.xda-developers.com/showthread.php?p=41289727
Hi Guys
I got CWM Touch 5.8.1.5 working on Infuse complete with working touch. Someone will have to build into kernel until we get flashable recovery going. I should mention that recovery.fstab mounts to mtd block so this probably won't work on bml roms. I might do a bml version if enough people want it, but someone would have to get me a bml mount list as I am running jellybean.
Installation
Flash the zip the same way you would any rom zip or you can rename zip to update.zip and place at /sdcard/, then in cwm apply /sdcard/update.zip. Will disappear on reboot, so keep the zip. Still trying to figure out how to flash permanently.
Bugs
10/2 Build: All of the mounts that can work now do. JT confirmed for me that the ones that don't work at this point aren't mountable (boot, recovery, and efs). Will try to take those out of the menu later, but for now this is ready to go. Same install process for now. ROM dev could build this build into a rom's boot.img now though it all works.
Download
CWM Touch 5.8.1.5 10/2 Build
blscallions said:
Hi Guys
I got CWM Touch 5.8.1.5 working on Infuse complete with working touch. Will upload in a few minutes as flashable zip. Someone will have to build into kernel until we get flashable recovery going.
Installation
Flash the zip the same way you would any rom zip or you can rename zip to update.zip and place at /sdcard/, then in cwm apply /sdcard/update.zip. Will disappear on reboot, so keep the zip. Still trying to figure out how to flash permanently.
Bugs
A few of the mounts are not working right now, need to update recovery.fstab to point to correct mount. Will upload new version once I get mounts fixed.
Download
CWM Touch 5.8.1.5
Click to expand...
Click to collapse
man thats super cool!!!!!!
could you use the TWRP injection script that those guys have going?
it strips out the old recovery from the kernel image and injects a new one...
also 5.x works fine with jb right?
hazard66 said:
man thats super cool!!!!!!
could you use the TWRP injection script that those guys have going?
it strips out the old recovery from the kernel image and injects a new one...
also 5.x works fine with jb right?
Click to expand...
Click to collapse
twrp doesn't work with jellybean so i can't use that injection method. MG and I are working on fixing it though. Yes 5.x is working with jellybean, but like I mentioned under bugs some mounts aren't acting right, such as /emmc and /efs, not sure why, might not even be necessary cause I was able to flash paranoid without those mounted.
blscallions said:
twrp doesn't work with jellybean so i can't use that injection method. MG and I are working on fixing it though. Yes 5.x is working with jellybean, but like I mentioned under bugs some mounts aren't acting right, such as /emmc and /efs, not sure why, might not even be necessary cause I was able to flash paranoid without those mounted.
Click to expand...
Click to collapse
iirc /emmc never mounted right on the infuse in 5.x -- at least, i have not experienced it
i remember installing 6 and being like "wow i can see my sdcard!"
maybe other ppl have had different experiences heh
twrp is pretty nice ive never used cwm touch on the ol infuser
hazard66 said:
iirc /emmc never mounted right on the infuse in 5.x -- at least, i have not experienced it
i remember installing 6 and being like "wow i can see my sdcard!"
maybe other ppl have had different experiences heh
twrp is pretty nice ive never used cwm touch on the ol infuser
Click to expand...
Click to collapse
Dude! Thank You, you just reminded me why i can't find /emmc in mounts. i took out my external card out when i flashed paranoid. still you might be right about 5.x problem with external, but at least now i can find the mount location lol. almost had a dumb blonde moment
blscallions said:
Dude! Thank You, you just reminded me why i can't find /emmc in mounts. i took out my external card out when i flashed paranoid. still you might be right about 5.x problem with external, but at least now i can find the mount location lol. almost had a dumb blonde moment
Click to expand...
Click to collapse
ahh found your problems. maybe.... all the mtd blocks are yaff2 not ext4, change that. only /data is ext4 on mtd. also some modification of recovery might be needed to get the /emmc working since it is a symlink on the infuse. the actual mount point for emmc is /storage/sdcard1 the volume name is emmc and the device path can be a number of different things (linux is weird)... this will take some experimentation or research to fix. the /emmc symlink just points anything looking for /emmc to /storage/sdcard1.
if you use the right device path for the external sdcard you might still have a prblem using /emmc as a mount pont since it is a special file not an empty folder.. if you change the mount point i don't know if the recovery menu will know to look for it. if there is a config file for the menu it may also need editing.
edit, i don't see any other config files, so you might maybe need the source code to fix the external sdcard mounting.... but maybe just maybe it simply uses recovery.fstab to find the list of mount points to list in the menu in the first place. all i can say is try changing /emmc to /storage/scard1 and see if the menu changes.
Dani897 said:
ahh found your problems. maybe.... all the mtd blocks are yaff2 not ext4, change that. only /data is ext4 on mtd. also some modification of recovery might be needed to get the /emmc working since it is a symlink on the infuse. the actual mount point for emmc is /storage/sdcard1 the volume name is emmc and the device path can be a number of different things (linux is weird)... this will take some experimentation or research to fix. the /emmc symlink just points anything looking for /emmc to /storage/sdcard1.
if you use the right device path for the external sdcard you might still have a prblem using /emmc as a mount pont since it is a special file not an empty folder.. if you change the mount point i don't know if the recovery menu will know to look for it. if there is a config file for the menu it may also need editing.
edit, i don't see any other config files, so you might maybe need the source code to fix the external sdcard mounting.... but maybe just maybe it simply uses recovery.fstab to find the list of mount points to list in the menu in the first place. all i can say is try changing /emmc to /storage/scard1 and see if the menu changes.
Click to expand...
Click to collapse
yeah in my most current build (not the one on here, not complete yet so not uploaded) I have changed the blocks to yaffs2 except data is ext4. gonna work on emmc today and might take your advice and contact jt about efs problem.
recovery.fstab is in the etc/ folder in the zip. i've got most of the mounts working now. just the two bad ones now so i am getting there.
i have been playing with the idea of using flash_image to flash recovery.img, but i'm not sure yet where recovery.img is located in our mtd structure. i posted that question in Q&A. i don't think the old method of flashing recovery is ever gonna work on mtd. no matter how you pull boot.img from the system cwm still says that boot.img does not contain ramdisk.
Edit: I tried mounting emmc to /storage/sdcard1, and that's not the right path. internal sdcard mounts to /dev/block/mmcblk0p1 and that path i'm sure works (tested myself) so i think maybe external might use one of these mmcblk too? Put my external back in this morning gonna run mount command and see if she shows me where she hides.
Yahtzee! Found /emmc, proper mount should point to /dev/block/mmcblk1p1. All I'm lacking now is /efs, which does show in mount command but when it tries to mount it says it cant find the block to mount it, perhaps this is a permision problem? I'm also lacking the option to mount boot and recovery, but i don't think those options are gonna be doable on infuse, not much good to us anyway since we cant write directly to those blocks that i know of.
Just a tidbit of info on mounts... you've got your terminology mixed up. /emmc doesn't point to /dev/whatever, it's the other way around. The /dev/whatever file is actually a device/block file which means it's just a fake file that allows you to access the hardware on the system via kernel drivers. You then mount that to a path on the system with a file system type (ie, through a fs driver) to store/access the data.
Just in case you were mixed up (might help you with any future problems, etc...)!
10/2 Build
Got a new build out there for you. All the mounts that can work do. Will try to take boot, recovery, and efs out of the mounts menu later. Download link in OP has been updated. For now work for me has stopped; hard-bricked my infuse, no power or download mode. Tried a recovery install procedure that was a bad idea. Hopefully ATT will replace.
blscallions said:
Hi Guys
I got CWM Touch 5.8.1.5 working on Infuse complete with working touch. Someone will have to build into kernel until we get flashable recovery going. I should mention that recovery.fstab mounts to mtd block so this probably won't work on bml roms. I might do a bml version if enough people want it, but someone would have to get me a bml mount list as I am running jellybean.
Installation
Flash the zip the same way you would any rom zip or you can rename zip to update.zip and place at /sdcard/, then in cwm apply /sdcard/update.zip. Will disappear on reboot, so keep the zip. Still trying to figure out how to flash permanently.
Bugs
10/2 Build: All of the mounts that can work now do. JT confirmed for me that the ones that don't work at this point aren't mountable (boot, recovery, and efs). Will try to take those out of the menu later, but for now this is ready to go. Same install process for now. ROM dev could build this build into a rom's boot.img now though it all works.
Download
CWM Touch 5.8.1.5 10/2 Build
Click to expand...
Click to collapse
Prolly gonna sound like a complete ass but....when I click on the link it shows a series of folders....as if I unzipped the file. So where do I download the actual .zip file from?
---------- Post added at 10:19 PM ---------- Previous post was at 09:40 PM ----------
I'm an idiot.....nvm thank you
KFlannigan5 said:
Prolly gonna sound like a complete ass but....when I click on the link it shows a series of folders....as if I unzipped the file. So where do I download the actual .zip file from?
---------- Post added at 10:19 PM ---------- Previous post was at 09:40 PM ----------
I'm an idiot.....nvm thank you
Click to expand...
Click to collapse
Docs is confusing that way... in a "desktop" browser, top left corner will be a file menu type thing where you can select download. Not very noticeable at all... don't feel dumb, I've been using computers for over 20 years and had the same wtf moment you had - took me a while to notice it!
j.smith said:
Docs is confusing that way... in a "desktop" browser, top left corner will be a file menu type thing where you can select download. Not very noticeable at all... don't feel dumb, I've been using computers for over 20 years and had the same wtf moment you had - took me a while to notice it!
Click to expand...
Click to collapse
Yeah I saw the "file" button .......the recovery works awesome. Wishing for a permanent solution. Anyone know of a good kernel? Takes me forever to charge and the battery life is atrocious. Thanks in advance.
There is s big bug with cache not being wipeable
Sent from my SGH-I997 using XDA Premium HD app
nobody wants to update this. :~(
<TheJackofClubs> http://forum.xda-developers.com/showthread.php?t=1908609 <- add touch to cwm <3
<Araemo> TheJackofClubs: no
<TheJackofClubs> aw
<Araemo>
Hey XDA ! =D
I'm still interested in installing Cyanogenmod 10 on my LG Optimus One P500h, but I want to make sure I follow the steps properly first - this is my first time installing a custom ROM, and when I heard it was possible to install Android 4.0 on the P500h, I performed a backup from ROM Manager, and I "bricked" my device a few days ago. XD
I wouldn't want this to happen again, but at least, I must say I have more experience now, and learned a lesson.
Did many searches on how to install CWM with Cyanogenmod 10, I found many different ways to do it, and I'm still unsure of which procedure follow.
Read the FAQ and that was really helpful.
I will list the procedure that I would normally try - please correct me if I forget anything:
0. Root the device
Done that already. I'm on Android 2.3. When I flashed the KDZ on my LG (and so to my surprise, got me updated from 2.2 to 2.3.3) , I've used V20A_00.KDZ, so I *assume* this is the second baseband.
1. Compact/Trim Cyanogenmod ROM
Downloaded CM10 here. This look correct: http://forum.xda-developers.com/showthread.php?t=1811325
January 8: Build 7/Final
I chose C10 over C11 because more things are compatible I believe - was it Bluetooth that did not worked under C11, but does on C10 ?
Anyways, that solve a known problem: many users said they loose network after the ROM installation. Shinobisoft confirmed it was because of the lack of space on the System partition, right ? Compacting the ROM would also fix problems for installing Link2SD ?
I've downloaded the tool "OOne ROM Editor" and opened it - it doesn't look complicated at all. What apps are safe to delete ? Will converting them to "user app" save space for system apps (I'm not sure - Where are the apps stored when defined as "User"? SD card rather than /System ?) ? Can I delete fonts without problems (I don't see why I can't keep ONLY 3-4 fonts, not 10) ? Then how much space will be left on the device ?
Read I cannot delete LatinIME.apk. Is this the default keyboard? 20MB is huge, there's no way to compact this file, right ?
Assuming there's like 10MB free, network will work, but I will have no choice but to use Link2SD to install apps fully on SD card, is this correct ?
2. Baseband stuff
Ehm, what are we referring to as "baseband" in first place?
All ROMs starting with CM7 are new baseband. If your device had Android 2.2 prior to flashing, you are on old-baseband. There is a patch for that also in the LG Optimus One FAQ on the first page, not sure which post off the top of my head tho. If your device had Android 2.3 on it then you have a new baseband device which shouldn't require any patches.
Click to expand...
Click to collapse
Allright, this should make this a lot easier - as I said, I originally was on Android 2.2, when I bricked the phone, I flashed "V20A_00" throught KDZ Updated, then I rebooted as 2.3.3, so I shouldn't do anything, right ?
In "About Phone", it's listed "Software Version: LG-P500h-v20a".
3. Install ClockworkMod Recovery
This look like the tricky part.
A lot of people on other sites said to use ROM Manager...
shinobisoft said:
First, serious word of advice. Stay away from ROM Manager. It does not handle this device correctly.
Click to expand...
Click to collapse
ROM Manager's way of flashing recovery is broken by design. Do NOT use it unless you are comfortable with rescuing your phone via ADB/fastboot like many people before.
Click to expand...
Click to collapse
Yes, ROM Manager is completely broken in this regard. It needs to download a signed ZIP and discard it and report an error when verification fails. Heck, ZIP format has even its own CRC check. What ROM Manager is doing (download whatever .IMG and flash it no matter what) is a nice WTF! Broken by design, go rewrite from scratch!
Click to expand...
Click to collapse
I don't trust the use of ROM Manager anymore on my device, and I'm not comfortable with using it again. I actually wonder: When I press VolumeUp-Home-Power, the phone perform a factory reset (Many people asked already why. This apparently mean that CWM is not installed).
But is it really installed? ROM Manager actually says: "Actual Recovery: ClockworkMod Recover 5.0.2.0". What? Am I supposed to press VolumeUp-Home-Power to verify, only to do another factory reset?
So what would the non-ROM-Manager method be ? I found this one here:
http://forum.xda-developers.com/showthread.php?t=1146566
I know about the Android Terminal Emulator already, and as a Linux user on PC, the commands "su", "cat", "chmod", "mount" are not unknow to me. I should be able to do this... That's not risky ?
So when CWM will be installed, I should be able to boot in it using "VolumeUp-Home-Power"; in theory, this is a bootloader, so if the ROM get screwed up, I *should* be able to access the bootloader to restore the ROM (I compare this to a PC BIOS - the OS is screwed, but BIOS remain accesible) ?
How could I explain that when I bricked my device with ROM Manager, I couldn't perform a factory reset, and only had access to Emergency Mode (I assume there is not such thing as a "Recovery Mode" on a P500h stock, new/untouched. The equivalent immediatly perform a factory reset) ?
All Android devices have a recovery partition. This is essentially a section of the device’s memory devoted to a very basic recovery system that is separate from the normal operating system. This is normally used by manufacturers for recovering a broken device (as even if the operating system crashes, the recovery image has a chance of still being access and used to reflash the operating system, etc.).
Click to expand...
Click to collapse
By default, the LG P500h recovery partition perform an immediate factory reset - CWM will be installed here, so I should be able to access it if the ROM freak out. But why couldn't I access the factory reset, when I bricked the device? That's what I wonder.
4. Access CWM and do a Nandroid Backup to SD Card
I will now have the files boot, cache, data, recovery and system, as well as"nandroid.md5" on SD card.
5. Wipe everything, clean SD Card
Perform "Wipe data/factory reset". This will format the /data, /cache, /sdext, and .android_secure
Select the "Advanced" option and on the next screen select "Wipe Dalvik Cache". Confirm the wipe.
Not necessary but I do it anyway, in the "Advanced" screen select "Wipe battery stats" and the confirm that wipe
For a clean installation I recommend formatting the system partition too. From CWM home screen select "mounts and storage". On the next screen select "format /system" and then confirm the format.
Press the back button until you are back in the CWM home screen. Select "Install zip from sdcard" and then select "Choose zip from sdcard". Browse your sdcard for the ROM to install and select it. Confirm the installation. Now wait for the install to finish.
Go back to CWM's home screen. Select "reboot system now" option and let the device boot. The initial boot will take a couple of minutes. Don't panic.
Click to expand...
Click to collapse
6. Partition SD card (?)
Is this at that point that I should do it, in CWM ? Or wait until I access Cyanogenmod and use a software on PC to partition ?
Assuming I don't partition, I guess I definitely will lack space for applications (Due to the space of Android 4.0) ?
I will do "Partition SD Card>EXT4 1024MB>Swap:64MB. Is this correct?
7. Install Cyanogenmod
Install ZIP from SD Card, choose the CM ZIP;
8. Install Google Apps
Once the install is done, I won't reboot and immediately install Google Apps, with "Install ZIP from SD card". I chose this package (Working on JellyBean):
http://forum.xda-developers.com/showthread.php?t=1917411
Then I should reboot in CyanogenMod and finally install Link2SD, I believe.
***
..Did I forgot anything ?
I *believe* that makes sense, but this is my first time installing a ROM - I doesn't look *that* hard, I did researches, but things can go wrong... :/
What should I do if I screw things up? Use KDZ Updater again ?
I'm still a little worried about that baseband thing, and the lost network connection.
Thanks for the input, cheers!
1) Use FlashImageGUI app to flash recovery/or use Recovery.IMG flasher by @shinobisoft
2) Forget the baseband stuff
3) Factory reset is the default action when you boot into stock recovery
4) If you partition SD card your data will be wiped anyway
Sent from my GT-I9082 using Tapatalk
akiratoriyama said:
1) Use FlashImageGUI app to flash recovery/or use Recovery.IMG flasher by @shinobisoft
2) Forget the baseband stuff
3) Factory reset is the default action when you boot into stock recovery
4) If you partition SD card your data will be wiped anyway
Sent from my GT-I9082 using Tapatalk
Click to expand...
Click to collapse
1) I've checked FlashImage GUI, it look really simple to use. This is what I see now:
https://dl.dropboxusercontent.com/u/67605655/snap20140216_103936.png
For flashing a recovery image, should I select Clear Dalvik & Clear Cache ? Do I have to enable USB Debugging?
Where can I find the recovery image for CWM ? Here maybe: http://forum.xda-developers.com/showthread.php?t=1523050
I don't know, I would download CWM v5.0.2.7_Touch_p500-Build 4.zip.
Would the terminal emulator method would be easier (I still need to find recovery.img)?
Code:
$ su
# mount -o remount rw /system
# cat /sdcard/flash_image > /system/xbin/flash_image
# chmod 755 /system/xbin/flash_image
# flash_image recovery /sdcard/recovery.img
# mount -o remount ro /system
# reboot recovery
Since I have no Nandroid backup (I cannot do it until CWM is installed), what could I do if something goes wrong ?
2-3) Excellent, thank you.
4) I plan on partitionning, but at which point shoud I preferably do it?
Thank you, I appreciate the help - sorry for all the newbie questions.
1) Recovery image is in the zip fie itself. Extract it
The terminal method you're telling is just what FlashImage GUI does (notice the word 'GUI' )
2) Partition it whenever you want. Just backup your stuff before doing it.
3) As much I hate to say, the thanks button is there for a reason
Regards,
akiratoriyama.
Sent from my GT-I9082 using Tapatalk
akiratoriyama said:
1) Use FlashImageGUI app to flash recovery/or use Recovery.IMG flasher by @shinobisoft
2) Forget the baseband stuff
3) Factory reset is the default action when you boot into stock recovery
4) If you partition SD card your data will be wiped anyway
Sent from my GT-I9082 using Tapatalk
Click to expand...
Click to collapse
akiratoriyama said:
1) Recovery image is in the zip fie itself. Extract it
The terminal method you're telling is just what FlashImage GUI does (notice the word 'GUI' )
2) Partition it whenever you want. Just backup your stuff before doing it.
3) As much I hate to say, the thanks button is there for a reason
Regards,
akiratoriyama.
Sent from my GT-I9082 using Tapatalk
Click to expand...
Click to collapse
Ok, so I've downloaded ClockworkMod_5.0.2.0_Recovery_ThunderG_Official here: http://forum.xda-developers.com/showthread.php?t=1523050
Extracted the ZIP and put the file recovery.img at the root of the SD Card (USB storage); so now all I have to do would be to start FlashImage GUI, select "Recovery Image", browse and choose the file recovery.img, then flash (I won't select Clear Dalvik & Clear Cache unless I have to (It's not selected by default, so I assume it's not require - although I've backed up my stuff already).
It's that simple?
I'm still in a learning stage, I bricked the device once with ROM Manager, so if that work, I should be more confident for the rest (I will take a Nandroid backup). Thanks for all the great explanations - Will press the thanks button soon
(How much thanks can I give per thread?)
GameX2 said:
Ok, so I've downloaded ClockworkMod_5.0.2.0_Recovery_ThunderG_Official here: http://forum.xda-developers.com/showthread.php?t=1523050
Extracted the ZIP and put the file recovery.img at the root of the SD Card (USB storage); so now all I have to do would be to start FlashImage GUI, select "Recovery Image", browse and choose the file recovery.img, then flash (I won't select Clear Dalvik & Clear Cache unless I have to (It's not selected by default, so I assume it's not require - although I've backed up my stuff already).
It's that simple?
I'm still in a learning stage, I bricked the device once with ROM Manager, so if that work, I should be more confident for the rest (I will take a Nandroid backup). Thanks for all the great explanations - Will press the thanks button soon
(How much thanks can I give per thread?)
Click to expand...
Click to collapse
Don't worry you won't brick it.
(Talking from my experience of completely hard bricking aka dead booting my device due to kdz)
Just flash it.
It's that simple
Sent from my GT-I9082 using Tapatalk
akiratoriyama said:
Don't worry you won't brick it.
(Talking from my experience of completely hard bricking aka dead booting my device due to kdz)
Just flash it.
It's that simple
Sent from my GT-I9082 using Tapatalk
Click to expand...
Click to collapse
Allright, I got it!
I saw the success message, then used the keys to reboot in recovery, that worked!
At the boot, I can read "ClockworkMod Recovery v5.0.2.0 E: Bad boot message "recovery ".
I believe the "E: Bad boot message "recovery " is a known issue, and but is not a problem - please let me know if I have to do anything about this.
So now I will compact the Cyanogenmod ROM (I don't know how much space I should free, but I'll try to free a decent ammount), and perform a Nandroid backup to SD card.
I believe the hardest/scariest is done. From now, if the ROM install fail, I could just restore the backup, I guess.
Are they any case when CWM is unaccessible (When I bricked my device, I had no access to stock recovery (which only perform factory reset) but just Emergency Mode. Why was that?) ?
Thank you, I will let you know about the rest.
(Will press the thanks button at the end I don't know if it's OK to thanks on multiple posts on one thread, on this forum)
EDIT:
That error message means you dont have SD-ext. Ignore it.
Click to expand...
Click to collapse
EDIT 2: Nandroid backup succesfully taken! I now have the files .android_secure.vfat.tar, boot.img, cache.yaffs2.img, data.yaffs2.img, nandroid.md5, recovery.img and system.yaffs2.img. Will backup these on my PC.
It's OK to thanks on multiple post.You just have a limit of 8 thanks per day.
ROM manager made anything inaccessible except emergency mode or fast boot mode for some people.
(When I flashed my Oone with CWM, ROM manager worked like a charm)
You can flash the ROM now
Regards,
akiratoriyama.
Sent from my GT-I9082 using Tapatalk
akiratoriyama said:
Don't worry you won't brick it.
(Talking from my experience of completely hard bricking aka dead booting my device due to kdz)
Just flash it.
It's that simple
Sent from my GT-I9082 using Tapatalk
Click to expand...
Click to collapse
akiratoriyama said:
It's OK to thanks on multiple post.You just have a limit of 8 thanks per day.
ROM manager made anything inaccessible except emergency mode or fast boot mode for some people.
(When I flashed my Oone with CWM, ROM manager worked like a charm)
You can flash the ROM now
Regards,
akiratoriyama.
Sent from my GT-I9082 using Tapatalk
Click to expand...
Click to collapse
I appreciate the information;
It's quite akwards that ROM Manager broke everything (And I asked for a BACKUP - that's so broken, it brick the device when you want to BACKUP <__<) - when it rebooted, it was in Fastboot mode, and I never saw that mode before. Tried a few recommended commands without problems, but when I rebooted, I only had access to Emergency Mode.
What would be informative for me to know, is that ROM Manager seems to not only have screwed the ROM, but the stock bootloader as well. Weird.
Shinobisoft said we need to compact the CM10 ROM with his utility first, because the System partition is too small (Otherwise, I will have no network). I will do that, I have the tool, that doesn't look complicated.
From now, I am backing up my SD Card content (DATA is backed up too) with Nandroid present on SD, so I could start formatting, immediately followed by SD partitioning.
I guess I should be fine at that point - if anything goes wrong, I should have the option to restore the Nandroid backup.
Will let you know when I'll have the ROM compacted (Probably today).
EDIT: YAY !
Everything worked as we expected! I saved my SD Card on my computer, wiped it, partition it from CWM (EXT: 1024MB, SWAP: 64MB. I have a 16 Micro SD, class 4 (Can't afford higher class much, for now), then installed the compacted ROM. Immediately after, I installed Gapps, then rebooted.
That worked !! This ROM is DOPE ! Totally worth upgrading ! Blazing fast !! (Will be slower with apps installed, but well)
I also have a working network!
There is one thing that "failed", I cannot get Link2SD to work. It always says "cannot create mount script". I checked with Windows (I know by experience that I should absolutely not edit Unix partitions in Windows, I just check), and the FAT32 partition is the first, then I have a EXT4 partition, then the Linux-Swap, I don't know why it doesn't work.
I used Gparted to format the EXT4 partition to EXT2, but same problem, "cannot create mount script". What am I supposed to do ?
Thanks youuu !! =D
I'm really happy to have done this on my own, with help - I now have more experience with Android, I have experience with Windows, Linux OS and OS X, but never did I tried flashing a ROM yet.
@GameX2
Just woke up to see this post
How much free space is there on your /system partition ?
Link2SD should be working.
Sent from my GT-I9082 using Tapatalk
akiratoriyama said:
@GameX2
Just woke up to see this post
How much free space is there on your /system partition ?
Link2SD should be working.
Sent from my GT-I9082 using Tapatalk
Click to expand...
Click to collapse
Hi,
Tanks for replying. out of 200mb, I have 70Mb free, but on /data. Last time i checked, /system was almost full (where can i check system size?).
Seems like lot of people have this link2sd issue.
@GameX2 use root explorer, it will tell you the remaining system space
@xu3sno or @ibub can you please help me ?
Sent from my GT-I9082 using Tapatalk
akiratoriyama said:
@GameX2 use root explorer, it will tell you the remaining system space
@xu3sno or @ibub can you please help me ?
Sent from my GT-I9082 using Tapatalk
Click to expand...
Click to collapse
That's what I've thought, according to "Storage Analyzer", /sysem has as minimum free space of 84KB (!) and a maximum of 4.63 MB.
Did not experience any weird stuff, for now.
sd-ext folder doest exist at root, but it's empty.
GameX2 said:
That's what I've thought, according to "Storage Analyzer", /sysem has as minimum free space of 84KB (!) and a maximum of 4.63 MB.
Did not experience any weird stuff, for now.
sd-ext folder doest exist at root, but it's empty.
Click to expand...
Click to collapse
Link2SD needs at least a MB to create mount scripts.
Delete some system apps like TerminalEmulator, CM File manager, Email, Exchange services.
Also use mini LatinIME.
Sent from my GT-I9082 using Tapatalk
akiratoriyama said:
@GameX2 use root explorer, it will tell you the remaining system space
@xu3sno or @ibub can you please help me ?
Sent from my GT-I9082 using Tapatalk
Click to expand...
Click to collapse
@akiratoriyama
Yes, that's right. You can check /system space by using Root Explorer. Or go to
Settings>About phone>Partition info.
I got 10+MB space left on /system partiton after trimmed the ROM and installed mini gapps.
You're right, Link2SD only works if there is 3MB, at least, left in system partition.
Sent from my LG-P500 using xda app-developers app
GameX2 said:
That's what I've thought, according to "Storage Analyzer", /sysem has as minimum free space of 84KB (!) and a maximum of 4.63 MB.
Did not experience any weird stuff, for now.
sd-ext folder doest exist at root, but it's empty.
Click to expand...
Click to collapse
Once you have success with link2sd creating mount scripts, you can access at /data/sdext. Been a long time since I ran Jan 8 cm-10, but I seem to recall that partition info is not in settings/about phone. But link2sd will have it. Or there are other apps. When viewing storage info from settings menu, don't confuse internal memory with /system (190mb). Internal that is shown there is/data (200mb).
Sent from my LG-P509 using Tapatalk 2
Link2SD needs at least a MB to create mount scripts.
Delete some system apps like TerminalEmulator, CM File manager, Email, Exchange services.
Also use mini LatinIME.
Click to expand...
Click to collapse
It worked !!
Geez, I went to 170MB of internal MB to 1GB, that's just plain insaneee !
Now I can use my LG P500h for an extra 2 years.
ibub said:
Once you have success with link2sd creating mount scripts, you can access at /data/sdext. Been a long time since I ran Jan 8 cm-10, but I seem to recall that partition info is not in settings/about phone. But link2sd will have it. Or there are other apps. When viewing storage info from settings menu, don't confuse internal memory with /system (190mb). Internal that is shown there is/data (200mb).
Sent from my LG-P509 using Tapatalk 2
Click to expand...
Click to collapse
Thank you! I was confused, because sd-ext2 at root is empty - nice to find it in /data/sdext2.
Suceess !!
Thanks !!
How Do I Install?
GameX2 said:
1) I've checked FlashImage GUI, it look really simple to use. This is what I see now:
https://dl.dropboxusercontent.com/u/67605655/snap20140216_103936.png
For flashing a recovery image, should I select Clear Dalvik & Clear Cache ? Do I have to enable USB Debugging?
Where can I find the recovery image for CWM ? Here maybe: http://forum.xda-developers.com/showthread.php?t=1523050
I don't know, I would download CWM v5.0.2.7_Touch_p500-Build 4.zip.
Would the terminal emulator method would be easier (I still need to find recovery.img)?
Code:
$ su
# mount -o remount rw /system
# cat /sdcard/flash_image > /system/xbin/flash_image
# chmod 755 /system/xbin/flash_image
# flash_image recovery /sdcard/recovery.img
# mount -o remount ro /system
# reboot recovery
Since I have no Nandroid backup (I cannot do it until CWM is installed), what could I do if something goes wrong ?
2-3) Excellent, thank you.
4) I plan on partitionning, but at which point shoud I preferably do it?
Thank you, I appreciate the help - sorry for all the newbie questions.
Click to expand...
Click to collapse
A bit new to installing a recovery and custom ROM on this LG Optimus One (very familiar with Sony phones though), apologies for the newbie-ness. I have all of the files as per this thread, but how do I install the GUI app without a file manager app?
Drachinos said:
A bit new to installing a recovery and custom ROM on this LG Optimus One (very familiar with Sony phones though), apologies for the newbie-ness. I have all of the files as per this thread, but how do I install the GUI app without a file manager app?
Click to expand...
Click to collapse
Install some file manager from play store. In phone settings (not file manager) choose security. Then choose to allow installation from unknown sources. Then open your file manager, scroll to sdcard/downloads/ ,and click on flashimage GUI.apk. Installation process will start.
Sent from my LG-P509 using Tapatalk 2
ibub said:
Install some file manager from play store. In phone settings (not file manager) choose security. Then choose to allow installation from unknown sources. Then open your file manager, scroll to sdcard/downloads/ ,and click on flashimage GUI.apk. Installation process will start.
Sent from my LG-P509 using Tapatalk 2
Click to expand...
Click to collapse
I guess I was thinking too much (or not at all!) Simplicity is the key a lot of times!
I tried all of the points in this thread and now this Optimus One has root, recovery and a new ROM. Thanks everyone! :good:
TF700t
I am on twrp-3.0.2-0. I followed the following steps.
1. Full wipe
2. Format /data
3. Change /data to f2fs
4. Flash KatKiss-6.0_TF700T_029.zip
5. Flash OpenGapps ARM 6.0 Pico
6. Flash SuperSU BETA 2.52
7. Wipe cache/dalvik
8. Reboot
The tablet boots with the message "Storage space running out. Make sure there is at least 250mb free space". This is not only cosmetic but prevents me from installing some apps and enable sync on gmail.
I tried following the steps 2 times thinking I may have had done something wrong the first time each time with format of /data.
What am I doing wrong? Is there any way to increase the size of the system partition from TWRP? What are my options?
Are you trying to install apps to /system? They should go to /data, your system partition is pretty much filled with the rom.
In adb shell run cat /proc/partitions and post the result
Sent from my Nexus 5X using Tapatalk
Out of space in /system after clean install
I have pretty much exactly the same problem as @smodak - after formatting all partitions in TWRP and changing /data to f2fs I followed the published instructions - installed KatKiss from recovery, then SU 2.52 beta, then open gapps ARM 6.0 pico. All went well except that gapps won't install as there is only 102Mb free in the /system partition.
So I'm just flashing the gapps package in TWRP but it is obviously trying to install to /system instead of /data as you suspected @berndblb... I wonder if this is an error in the installer package configuration?
I had a look through the gapps zip but couldn't find anything explicitly referencing /system, so I'm not sure how to direct the installer to install to /data instead... any suggestions gratefully received. Meantime I might download a different flavour gapps and see if it behaves differently.
Thanks!
I downloaded open_gapps-arm-6.0-full and tried again - still trying to install to /system.
Is it possible to change this behaviour?
You cannot install the full gapps version. The system partition is not large enough. Download and flash the pico version. It has only the essential Gapps, those that need to be in /system to work.
If you're missing any Google apps install them from Play. Then they will install to /data
Yep, already tried pico first - not enough space. Was hoping that the /system target was an error but have since learnt this is by design in open gapps.
I'm having trouble finding any other distribution that targets /data - do you know of any?
Thanks.
Thousands of people have downloaded the rom and flashed the recommended pico gapps without a problem, including yours truly.. And your system partition is not large enough??? I don't think so. I have no idea what it is you are doing, but you are doing something wrong....
Back to basics I would recommend: double check each step and start over
Sigh... I've come so far - from a soft brick to a working OS, I can almost taste it! OK, back to square one. Wipe and try again.
Tell me if this sounds right though - TWRP is reporting that my /system is 503Mb in total, and after installing KK and SU 401Mb is used. So, only 102Mb free. Am I somehow chewing up extra space during the install, or is this what you'd expect, and the partition size you'd expect? The gapps pico zip is 155Mb so if it's trying to extract everything to /system during install, and these sizes are right, it's hard to see how it's ever going to work.
multiSingularity said:
Sigh... I've come so far - from a soft brick to a working OS, I can almost taste it! OK, back to square one. Wipe and try again.
Tell me if this sounds right though - TWRP is reporting that my /system is 503Mb in total, and after installing KK and SU 401Mb is used. So, only 102Mb free. Am I somehow chewing up extra space during the install, or is this what you'd expect, and the partition size you'd expect? The gapps pico zip is 155Mb so if it's trying to extract everything to /system during install, and these sizes are right, it's hard to see how it's ever going to work.
Click to expand...
Click to collapse
Where do you see the 503mb size? The TF700 has a 768 mb /system partition.
Format system, then flash rom, gapps and super su in that order.
With Nougatella, pico gapps and SuperSU I have 563 mb on /system.
Install and run DiskInfo from Play to see your partition size and what's in use.
Ooops, sorry - you can't boot the thing.. Didn't mean to twist the knife. :laugh:
Open a terminal in TWRP and run: cat /proc/partitions
You'll see that mmcblk0p1 is 786432 kb which equals 768 MB.
I would be stunned if you see anything dirfferent
berndblb said:
Where do you see the 503mb size? If I remember correctly the TF700 has a ~760 mb /system partition.
Format system, then flash rom, gapps and super su in that order
Click to expand...
Click to collapse
TWRP 3.0.2.1 > Wipe > Advanced Wipe > Select "System" > Repair or Change File System. Shows 503Mb for /system, ~59Gb for /data.
I'm wondering if there might be temp directories left over from installs that need cleaning up? Could I resize those two partitions without a high risk of bricking my tab again?
I'll try reflashing in your order... I was going from the instructions in the KK thread that said to do SU before gapps. Maybe that will help.
---------- Post added at 03:27 PM ---------- Previous post was at 03:13 PM ----------
berndblb said:
Install and run DiskInfo from Play to see your partition size and what's in use
Click to expand...
Click to collapse
Heh, it's a bit hard to access the Play Store without being able to install gapps!
multiSingularity said:
Heh, it's a bit hard to access the Play Store without being able to install gapps!
Click to expand...
Click to collapse
Yeah, I realized that, read my edit above
---------- Post added at 09:33 PM ---------- Previous post was at 09:30 PM ----------
multiSingularity said:
TWRP 3.0.2.1 > Wipe > Advanced Wipe > Select "System" > Repair or Change File System. Shows 503Mb for /system, ~59Gb for /data.
I'm wondering if there might be temp directories left over from installs that need cleaning up? Could I resize those two partitions without a high risk of bricking my tab again?
Click to expand...
Click to collapse
Mhh, definitely format system because in the same place TWRP shows me 755 mb for /system.
No, you cannot resize the partitions and you don't need to....
berndblb said:
Open a terminal in TWRP and run: cat /proc/partitions
You'll see that mmcblk0p1 is 786432 kb which equals 768 MB.
I would be stunned if you see anything dirfferent
Click to expand...
Click to collapse
Prepare to be stunned.
mmcblk0p1 is 524288 in size.
Unsurprisingly, formatting and reflashing KK then gapps still failed. I've attached the gapps installation log for some light reading.
(Scratches head) Soooo... something is screwy with my system partition size. I've never resized it (if that's even possible) so I don't know what's going on.
multiSingularity said:
Prepare to be stunned.
mmcblk0p1 is 524288 in size.
Unsurprisingly, formatting and reflashing KK then gapps still failed. I've attached the gapps installation log for some light reading.
(Scratches head) Soooo... something is screwy with my system partition size. I've never resized it (if that's even possible) so I don't know what's going on.
Click to expand...
Click to collapse
I am stunned and scratching my head. This is after running a format in TWRP???
It's late here and I'm going to sleep on this. c u later
berndblb said:
I am stunned and scratching my head. This is after running a format in TWRP???
It's late here and I'm going to sleep on this. c u later
Click to expand...
Click to collapse
Hey, thanks for all your help so far. I really appreciate the time you've put in answering my questions! Sleep tight.
Had to downgrade to KK 5.1.1 to get it all to fit. Worked OK, but noticably slower than Nougat. I did a little jiggerypokery with KK 7.1 in the TWRP terminal window and moved the /system/app directory to my sdcard (set up as Adoptable Storage) with a symlink to it under /system. Hoping this should work OK... it certainly gave me enough space to install gapps. Time to test.
Yeah well that was a bit of a flop. Got stuck on the boot animation. Tried moving some different directories out of system to sdcard or to /data and symlinking but no dice any which way. Tried leaving directories in situ but moving large files and symlinking those (eg foreign font files) but still no joy.
Unless there's a way to delete and recreate the system and data partitions I think I'm stuck on 5.1 till the end of time.
multiSingularity said:
Yeah well that was a bit of a flop. Got stuck on the boot animation. Tried moving some different directories out of system to sdcard or to /data and symlinking but no dice any which way. Tried leaving directories in situ but moving large files and symlinking those (eg foreign font files) but still no joy.
Unless there's a way to delete and recreate the system and data partitions I think I'm stuck on 5.1 till the end of time.
Click to expand...
Click to collapse
You really think the tablet will last that long?? :silly:
How about flashing the thing back to stock. AFAIK flashing the stock blob in fastboot puts everything back to stock. I have no idea if it also recreates the partition table though... Worth a shot if you ask me.
It's called a buster99 and typically used if you're stuck with an 'unrecoverable bootloader error'. Google those terms and you'll find the steps easy enough.
berndblb said:
You really think the tablet will last that long?? :silly:
How about flashing the thing back to stock. AFAIK flashing the stock blob in fastboot puts everything back to stock. I have no idea if it also recreates the partition table though... Worth a shot if you ask me.
It's called a buster99 and typically used if you're stuck with an 'unrecoverable bootloader error'. Google those terms and you'll find the steps easy enough.
Click to expand...
Click to collapse
Yeah, I used buster99's approach to recover from my soft brick. It's worth a go, for sure. Will let you know how it goes.
OK, here's the latest.
Flashing the stock ASUS ROM via fastboot failed because the staging partition is too small - it can't even get off first base.
HOWEVER... the lightbulb went on as to why my partitions are all out of whack - a while ago when I started experimenting with resurrecting my Infinity I accidentally flashed a stock TF201 ROM onto it, and this has clearly recreated TF201-sized partitions for me. So, this is an ecouraging sign that doing the same with the right ROM will fix the issue - if only we can get it to complete.
I'm thinking if I could delete all partitions except system and recovery, or even recreate a properly sized staging, and then flash the stock ROM it would likely create the missing partitions as it goes. Thoughts?
Now that explains a lot!
I seem to remember that _that posted a flashable partition table somewhere quite a while ago.... pt.blob I think it was.... I'll dig for it later today...
---------- Post added at 06:00 AM ---------- Previous post was at 05:52 AM ----------
Or you say wth and just flash the TF201 Katkiss to it
Which bootloader do you have on there now? The 700 or 201?