• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Root Stuck in CWM 6.0.4.5

J

JPJoller

Member
i updated recovery through Rom Manager app to 6.0.4.5 last night and now it will not boot past recovery. It also wont install any backups, failing at restoring /data. I cant flash any roms i have as it only boots back into recovery afterwards. Any help would be appreciated, as i use my phone at work and am sitting here now with nothing.

I also posted this in the PACE thread as it seems there was some discussion regarding the new CWM.
 
Sorry about that. The recovery builds go live automatically and there were some issues yesterday.

I'll hook you up with the old recovery shortly.
 
tdm said:
Sorry about that. The recovery builds go live automatically and there were some issues yesterday.

I'll hook you up with the old recovery shortly.
Click to expand...

Not a problem, i was reading and up to date with some of the issues, but i was getting antsy!! Thanks for the help.
 
I had success with following method a while ago (not the same version of CWM that you have though), I think it should still work if everything else fails:

Use the official LG mobile update tool and select "recovery" option from the menu. It will kick your phone in download mode and install stock. You can then re-root and install CWM recovery (previously working version) and go from there
 
Here is a working 6.0.4.5 recovery:

http://www.vmroms.com/~vmstorage/quattrimus/iproj/cwmt-6.0.4.5-vs920.img
md5=e8deccd98fc6fa72253a2c86c6d1fbc2

To install from within recovery:

Code: 
adb push cwmt-6.0.4.5-vs920.img /
adb shell dd if=/cwmt-6.0.4.5-vs920.img of=/dev/block/mmcblk0p13
adb shell sync

To install from Android:

Code: 
adb push cwmt-6.0.4.5-vs920.img /data/local/tmp
adb shell dd if=/data/local/tmp/cwmt-6.0.4.5-vs920.img of=/dev/block/mmcblk0p13
adb shell sync

If adb does not have root permission, do this instead:

Code: 
adb push cwmt-6.0.4.5-vs920.img /data/local/tmp
adb shell
su
dd if=/data/local/tmp/cwmt-6.0.4.5-vs920.img of=/dev/block/mmcblk0p13
sync

In any case, if you ever find yourself stuck in recovery and just want to get out, you can reset the recovery flag in NVRAM like this:

Code: 
adb shell dd if=/dev/zero bs=1 seek=7864320 count=84 conv=notrunc of=/dev/block/mmcblk0p25
 
It is a su apk issue and su has a fix for it if your using super su it has been fixed and its now 1.69 .
 
tdm said:
...

In any case, if you ever find yourself stuck in recovery and just want to get out, you can reset the recovery flag in NVRAM like this:

Code: 
adb shell dd if=/dev/zero bs=1 seek=7864320 count=84 conv=notrunc of=/dev/block/mmcblk0p25
Click to expand...

...and, I know it should go without saying, but do not blame TDM if you break your phone. The command above is overwriting 84 blocks of data at a specific address in your phones internal memory/storage. If you typo anything in the command above, bad things may result. :)
 
  • Like
Reactions: tdm
tdm said:
Here is a working 6.0.4.5 recovery:

http://www.vmroms.com/~vmstorage/quattrimus/iproj/cwmt-6.0.4.5-vs920.img
md5=e8deccd98fc6fa72253a2c86c6d1fbc2

To install from within recovery:

Code: 
adb push cwmt-6.0.4.5-vs920.img /
adb shell dd if=/cwmt-6.0.4.5-vs920.img of=/dev/block/mmcblk0p13
adb shell sync

To install from Android:

Code: 
adb push cwmt-6.0.4.5-vs920.img /data/local/tmp
adb shell dd if=/data/local/tmp/cwmt-6.0.4.5-vs920.img of=/dev/block/mmcblk0p13
adb shell sync

If adb does not have root permission, do this instead:

Code: 
adb push cwmt-6.0.4.5-vs920.img /data/local/tmp
adb shell
su
dd if=/data/local/tmp/cwmt-6.0.4.5-vs920.img of=/dev/block/mmcblk0p13
sync

In any case, if you ever find yourself stuck in recovery and just want to get out, you can reset the recovery flag in NVRAM like this:

Code: 
adb shell dd if=/dev/zero bs=1 seek=7864320 count=84 conv=notrunc of=/dev/block/mmcblk0p25
Click to expand...

Im sorry, but i have no idea how to do this....
 
JPJoller said:
Im sorry, but i have no idea how to do this....
Click to expand...
What ever you do, DO NOT .cab flash anything to your phone. You will have a brick on your hands.

Grab this file:
http://androidfiles.massivefilehost.com/cwm_touch/cwm_bootloop_fix.zip

Place it on your SD card and flash it like you would any rom. It will clear the flag that is causing you to boot into recovery. Then flash the new, and hopefully fixed, CWM Recovery, but keep that file on your sdcard in case you run into issues again.
 
Yoinx said:
Have you not used adb before? They're are guides around

Sent from my VS920 4G using Tapatalk 2
Click to expand...

Believe it or not, despite rooting and flashing numerous android devices, I have never used adb. I was looking into guides while at work, downloaded what I thought to be correct (adb universal driver, and android SDK) I was unsure where to go from there once I was in cwm. I tried running "adb devices" in cmd but it said adb was an unknown path.... I can get USB mounting to work, it has it mounted as f drive which I can view and edit/add files, but in windows "devices" there is vs920 that states it is unknown and there are no drivers. I downloaded LG drivers, installed, and tried to have windows use that folder to look for drivers but no help.
 
You need to find the latest ADB (the one in the PWNAGE tool won't work on JB+). Change your root settings in dev options to APPS/ADB. Then open a command prompt and cd to the directory with ADB.exe. Then you should be able to adb devices, and after accepting the security prompt on the phone... have ADB access.

Sorry for the short reply before... I don't like typing long answers on tapatalk.
 
Because TDM was nice and posted an updated CWM image, here is a zip that will automate the install process. Just flash this zip like you would any rom, but it may take two boots to get you out of recovery. One to boot into the updated recovery which clears the flag, and a second boot to get back into your ROM.

http://androidfiles.massivefilehost.com/cwm_touch/CWM_6.0.4.5_Spec.zip


TDM:

Feel free to link this where ever you need to.
 
Neph81 said:
Because TDM was nice and posted an updated CWM image, here is a zip that will automate the install process. Just flash this zip like you would any rom, but it may take two boots to get you out of recovery. One to boot into the updated recovery which clears the flag, and a second boot to get back into your ROM.

http://androidfiles.massivefilehost.com/cwm_touch/CWM_6.0.4.5_Spec.zip


TDM:

Feel free to link this where ever you need to.
Click to expand...


Not that it's a huge deal, but you could wipe the nvram through edify (a little more difficult) or include a script with the dd command, and package extract it to /tmp and execute it to prevent having to reboot into recovery once for the script to execute
 
Neph81 said:
Because TDM was nice and posted an updated CWM image, here is a zip that will automate the install process. Just flash this zip like you would any rom, but it may take two boots to get you out of recovery. One to boot into the updated recovery which clears the flag, and a second boot to get back into your ROM.

http://androidfiles.massivefilehost.com/cwm_touch/CWM_6.0.4.5_Spec.zip


TDM:

Feel free to link this where ever you need to.
Click to expand...

Thank you guys very much for the tips. I truly appreciate it. I will try this and report back.
 
Neph81 said:
Because TDM was nice and posted an updated CWM image, here is a zip that will automate the install process. Just flash this zip like you would any rom, but it may take two boots to get you out of recovery. One to boot into the updated recovery which clears the flag, and a second boot to get back into your ROM.

http://androidfiles.massivefilehost.com/cwm_touch/CWM_6.0.4.5_Spec.zip


TDM:

Feel free to link this where ever you need to.
Click to expand...

I used this method and everything seemed fine until I attempted to install a .zip file. I got a Status 7 error. Anyone else running into this or am I an isolated case?
 
I got that error also when trying to flash KitKat Pace 4.4 test file probably because I may have messed with the build.prop renaming "vs920" to "i_vzw". I'm nandroid'ing back to cm10.2 11/10/13 build now and play with build.prop to see if I can get that "Status 7" error to go away.
 
HueyT said:
I got that error also when trying to flash KitKat Pace 4.4 test file probably because I may have messed with the build.prop renaming "vs920" to "i_vzw". I'm nandroid'ing back to cm10.2 11/10/13 build now and play with build.prop to see if I can get that "Status 7" error to go away.
Click to expand...

Nothing you did, that assert is based off the build.prop in the recovery... the edits to the Rom are separate.

Sent from my VS920 4G using Tapatalk 2
 
tdm said:
I guess I'll need to verify the ota assert in the ROMs when kk gets going.
Click to expand...
Actually, CWM Recovery needs to be rebuilt. Anyone that flashed the new recovery will not be able to flash current Spectrum roms as they all look for vs920 and the product/device in this new recovery both report i_vzw. It will be easier to fix this now than it will be to try and get people to run a certain recovery based on which ROM they want to flash.

Edit: I could always repack the current recovery with the correct info, but people that flash it from Rom Manager would still get a bad copy.
 
Would love to have a recovery version that shows the device as vs920. Preferably in a flashable zip. Only way to update cm any further than the nightly released on the 10th.
 
You could also just manually edit the Rom's zip and remove the assert at the top of the edify script until it's fixed.
 
And here is where the new SDcard path is coming back to bite us and Koush will need to fix it as it's a ROM Manager issue.
Code: 
I:Checking for extendedcommand...
I:Running extendedcommand...
Waiting for SD Card to mount (20s)
I:605 Volume sdcard /storage/sdcard0 state changed from 1 (Idle-Unmounted) to 3 (Checking)
I:/storage/sdcard0: Checking
I:605 Volume sdcard /storage/sdcard0 state changed from 3 (Checking) to 4 (Mounted)
I:/storage/sdcard0: Mounted
I:200 0 volume operation succeeded
SD Card mounted...
Verifying SD Card marker...
3585b816ff344d71f57b145e06231a8f
I:Running script:
I:
run_program("/sbin/cp", "-R", "/cache/recovery", "/tmp/recovery");
ui_print("ROM Manager Version 5.5.3.0");
ui_print("November 15, 2013");
assert(backup_rom("/sdcard/clockworkmod/backup/2013-11-15-22.56.08"));

parse returned 0; 0 errors encountered
about to run program [/sbin/cp] with 4 args
ROM Manager Version 5.5.3.0
November 15, 2013
E:unknown volume for path [/sdcard/clockworkmod/backup/2013-11-15-22.56.08]
Can't mount backup path.

result was NULL, message is: assert failed: backup_rom("/sdcard/clockworkmod/backup/2013-11-15-22.56.08")
/tmp/recovery.log was copied to /sdcard/clockworkmod/recovery.log. Please open ROM Manager to report the issue.
Backups on the modded (fixed the assert check) version of CWM Touch I'm about to post will not work correctly if triggered through ROM Manager. You'll need to reboot into recovery and then do a backup manually. I'll also be posting a second zip that contains the old recovery for people who want to downgrade to the older, some what easier to use version, until all the bugs can be worked out of this version.
 
You must log in or register to reply here.
Back
Top Bottom