[Q] Clockworkmod Recovery Help! - Droid Incredible Q&A, Help & Troubleshooting

Hey All,
I am a long time "rooter" (June of 2010) on my Dinc. However, I am trying to Flash the new version of Clockworkmod Recovery. I open Rom Manager, click option 1 to "Flash ClockworkMod Recovery" to version 3.0.0.5. It asks me to verify my phone (Dink) and then says it flashed correctly. So, I reboot into Recovery and it is still the green text and says version 2.5.x.x. I reboot the phone and look in Rom Manager again it is says my Current version is 3.0.0.5. So, Rom Manager thinks I have the latest version of Recovery but I don't. I have tried other methods of Flashing the new version but that isn't working either. Specifically, I tried the ADB Shell. I get into ADB Shell just fine, but when I try to mount the SDCARD I get an error. I can boot the phone up and navigate just fine to the SDCARD. So I am not sure what the issue is. Any help would be greatly appreciated.
**UPDATE** I also had update.zip on the root of my sdcard, I deleted that and it still doesn't work.

i think you have reformat the partition

carepack said:
i think you have reformat the partition
Click to expand...
Click to collapse
Will that do damage? What partition, the SDcard? Please elaborate. Do that in the Clockworkmod Recovery?

FWIW, the new clockwork has compatibility issues with 95% of the flashable roms and extras out there right now. I wish I had not updated, and I am unable to go back (a nand restore would not do it.) Unless you feel a pressing need, you may be better off with the old version.
I got so frustrated, I switched my recovery to Amon_RA, which seems to work better for me at this point.

CJeep said:
FWIW, the new clockwork has compatibility issues with 95% of the flashable roms and extras out there right now. I wish I had not updated, and I am unable to go back (a nand restore would not do it.) Unless you feel a pressing need, you may be better off with the old version.
I got so frustrated, I switched my recovery to Amon_RA, which seems to work better for me at this point.
Click to expand...
Click to collapse
Ok, well I am using CM7 ROM and I think you have to have the new version. I reallly like CM7 so it would be worth it for me if I can get it to work. Can I use Amon RA with CM7 Rom?

foldog22 said:
Ok, well I am using CM7 ROM and I think you have to have the new version. I reallly like CM7 so it would be worth it for me if I can get it to work. Can I use Amon RA with CM7 Rom?
Click to expand...
Click to collapse
You do not need the new recovery for CM7 to work. You should also go to 3.0.0.8, there are problems with 3.0.0.5
See http://forum.xda-developers.com/showthread.php?t=970032 for details.

CJeep said:
FWIW, the new clockwork has compatibility issues with 95% of the flashable roms and extras out there right now. I wish I had not updated, and I am unable to go back (a nand restore would not do it.) Unless you feel a pressing need, you may be better off with the old version.
I got so frustrated, I switched my recovery to Amon_RA, which seems to work better for me at this point.
Click to expand...
Click to collapse
See http://forum.xda-developers.com/showthread.php?t=970032 on how to downgrade clockworkmod.
If your theme/extras developers have not upgraded their install scripts (like they have been warned to do for quite a few months) then this is the reason they do not work with the new CWM.

I followed the instructions but it still isn't working. I think the issue is ADB Shell can't mount the SDCARD. While in recovery, I can navigate to the SDCARD, but for some reason ADB Shell can't mount it. I tried all three methods as prescribed in the link. None work.

foldog22 said:
I followed the instructions but it still isn't working. I think the issue is ADB Shell can't mount the SDCARD. While in recovery, I can navigate to the SDCARD, but for some reason ADB Shell can't mount it. I tried all three methods as prescribed in the link. None work.
Click to expand...
Click to collapse
While you are booted in recovery I do not believe you can flash a new one. Boot to your ROM and try from there.

I figured it out. I ran the Unrevoked for Life patch and at that point it would let me update the Recovery image. Not sure if that was a prereq. or not. However, I am still experiencing issues. I am running CM7 with 3.0.0.8 Recovery. I am trying to update the nightly builds and it fails. Using Rom Manager to update my rom, it downloads the update. Reboots into Recovery and then says something about E:\ failure.

Well, I finally got the new recovery image but I can't update CM7 ROM's. It downloads the "Nightly Updates" but then says it can't mount E:\ when it reboots into recovery.

Related

[Q] cant access recovery after root with unrevoked 3.21

Hey guys and gals,
This is my first post and i need some help. Here's the story.
I rooted my phone a few weeks ago, everything went stunningly easy, and worked great. Clockworkmod recovery was installed (by unrevoked) at this time. While driving home I broke my phone's screen and had to get a replacement phone. Asurion had a phone to me within 18 hours (my word they're fast). I slapped the 16GB SD card from my first phone in and I was off and running.
So I have my new phone with my original 16GB SD card and set it up normally again. I wanted to wait a bit and get it set prior to rooting again. Tonight I rooted the phone with Unrevoked 3.21 as I did before. It went much faster than before. I now have S-Off but clockworkmod recovery is not on my hboot screen and recovery mode doesn't work at all. Just a black screen for about 15 seconds before loading into the OS.
Have I screwed up a one click root? I've tried a few things.
I used droid-life as a guide to help me root.
Phone Stats:
Droid Incredible
Asurion replacement
OS 2.2
radio 2.15.00.07.28
kernel 2.6.32.15-gb7b01d1
build 3.21.605.1 CL231334 release-keys
Although clockworkmod recovery isn't in Hboot the reflash tool still says "Recovery Image: ClockworkMod Recovery" on the bottom. I have tried renaming the clockworkmod folder on the SD card to see if it would create a new one, or boot into clockworkmod recovery after realizing the folder is not there.
I have also tried formatting my SD card and running the reflash tool again. Again no dice, no recovery mode.
I have tried unrevoked 3.21 after every change.
What have I done? what do I do? any suggestions?
Thanks for anybody and everybody's input. I appreciate it. I would like to start flashing roms but really dont want to mess with it if I dont have a recovery option.
-MOJO
Is it a complete download of the unrevoked tool? Sounds almost like the recovery package isn't there. Try redownloading unrevoked and run it again. Do you have root and Superuser app at least? If so, try downloading and running ROM Manager and tell it to flash Clockwork again. Still no dice, try telling it to flash RA recovery. And for the record, which screen do you have?
I wish I knew
PonsAsinorem said:
And for the record, which screen do you have?
Click to expand...
Click to collapse
thanks for the quick reply I will try that. Yes I have root and the superuser app.
I dont know how to tell which screen I have, but I was wondering the same thing. BoyGeniusReport says its incredibly hard to tell the difference and I haven't found were it says SLED vs AMOLED
Grrrr
PonsAsinorem said:
Is it a complete download of the unrevoked tool? Sounds almost like the recovery package isn't there. Still no dice, try telling it to flash RA recovery.
Click to expand...
Click to collapse
Downloaded unrevoked 3.21 straight from unrevoked twice.
Tried the reflashing clockworkmod recovery, no dice.
Whats an RA recovery?
RandomMOJO said:
Downloaded unrevoked 3.21 straight from unrevoked twice.
Tried the reflashing clockworkmod recovery, no dice.
Whats an RA recovery?
Click to expand...
Click to collapse
It's an alternate recovery. Here's the link: http://forum.xda-developers.com/showthread.php?t=758874
It's also the second to the last option in ROM Manager. Flash Alternate Recovery: RA_GNM Recovery v1.7.6
I actually like that one better. It was able to format my SD card correctly. I just miss the integration with ROM Manager.
Phew... It worked.
the alternate recovery worked.
now if I want to flash ROMs do I need to know anything in particular before doing so with the AMON_RA recovery tool.
I downloaded the a4d utility that I found when doing a search for AMON_RA on appbrain. It asks if I want to flash my phone to unlock my bootloader (and void my warranty, haha).
do I need to unlock my bootloader before flashing ROM's
I like the sense UI. thats all I have actually used. Is there anything better? what are suggested, STABLE, ROMs/kernels for the DInc? or should I stay "stock 2.2 rooted"?
RandomMOJO said:
the alternate recovery worked.
now if I want to flash ROMs do I need to know anything in particular before doing so with the AMON_RA recovery tool.
I downloaded the a4d utility that I found when doing a search for AMON_RA on appbrain. It asks if I want to flash my phone to unlock my bootloader (and void my warranty, haha).
do I need to unlock my bootloader before flashing ROM's
I like the sense UI. thats all I have actually used. Is there anything better? what are suggested, STABLE, ROMs/kernels for the DInc? or should I stay "stock 2.2 rooted"?
Click to expand...
Click to collapse
Uncommon sense with king kernel bfs # 5 is as good or better than stock.
Btw. Hboot only shows recovery, not clockwork recovery. Did you ever try selecting recovery from hboot?
silverxbv2 said:
Uncommon sense with king kernel bfs # 5 is as good or better than stock.
Click to expand...
Click to collapse
and still has all the capabilities of stock 2.2 (GPS, WIFI Tether, etc), I know that was a problem at one point. I assume/hope all has been fixed with those issues.
With flashing ROMs. do Custom ROM's have the bloatwear (CityID) removed?
RandomMOJO said:
and still has all the capabilities of stock 2.2 (GPS, WIFI Tether, etc), I know that was a problem at one point. I assume/hope all has been fixed with those issues.
With flashing ROMs. do Custom ROM's have the bloatwear (CityID) removed?
Click to expand...
Click to collapse
Uncommon sense has some of it removed. Some of it you can remove yourself. It's the only rom I've donated to and had on my phone more than two days.
Just be careful if removing stuff. Some of it has other dependencies. There are guides on how to remove things safely without breaking other functionality.
Also do a backup first. I'm not sure how amon ra works, but it must be in there somewhere.
RandomMOJO said:
and still has all the capabilities of stock 2.2 (GPS, WIFI Tether, etc), I know that was a problem at one point. I assume/hope all has been fixed with those issues.
With flashing ROMs. do Custom ROM's have the bloatwear (CityID) removed?
Click to expand...
Click to collapse
I used to use Virtuous 3.0.1, but I've switched over to Redemption ROM 2.0.5
silverxbv2 said:
Also do a backup first. I'm not sure how amon ra works, but it must be in there somewhere.
Click to expand...
Click to collapse
It is. In the main menu, just like Clockwork
So I definitely have recovery with the amon_RA 1.7.6 alternative recovery with the ROM manager. but from what I have read I can no longer use ROM manager to flash.
Now I have been searching for information/instructions on how to use AMON_RA but have come up short, at least recently written stuff. I can find a ton of information about clockworkmod which I assume is because of Unrevoked 3.21.
PonsAsinorem as you said you miss the integration of ROM manager. I really want to use ROM manager.
I read somewhere in XDA that people were having trouble using clockworkmod and ROM manager and it could be because of a corrupted cache. there were some LIMITED instructions about using ADB to fix it but I wasn't completely understanding them.
I think my problem is spawning from using my old SD card and maybe a corrupted cache. I have made a back up using Amon_RA (actually two).
Does anyone think that completely formatting my SD card (after moving my backups to my MAC) and factory restoring my phone. then reflashed using unrevoked 3.21, or reflashed clockworkmod recovery using rom manager would work to solve my problem with clockworkmod recovery?
I would have backups if it didn't work. I would just have to restore the Amon_RA backup if I screwed anything up or wanted my SD card back... Right?
Thanks for all the help so far.
MOJO
Found this and it solved the problem for me:
http://androidforums.com/incredible...ckwork-recovery-blank-screen.html#post1723460
dirtpan said:
Found this and it solved the problem for me:
http://androidforums.com/incredible...ckwork-recovery-blank-screen.html#post1723460
Click to expand...
Click to collapse
Dirtpan. you're a lifesaver thanks for pointing me at this. saved clockwork for me. All this time, its because I have the new SLCD screen as opposed to the AMOLED screen.
For the record, my wife has an AMOLED screen and I an SLCD. I can see no discernible difference.
Thanks again everybody for the help.
MOJO

Clockwork 3.x does not flash properly?, want to go back to 2.5.x? Look here!

I'm looking for CW 2.5.0.1(?) so I can flash radio and other files. It seems like 3.x "aborts" install with some files.
I have not been able to find the 2.5.x CW img for the Evo. Also, now that my phone is crippled (flashed a new ROM), how do I install the 2.5.x over the 3.x? ROM Manager does not give me the option to flash back to 2.5.x
Thanks for any quick help!
BTW, I'm not using RA because it doesn't seem to allow me to navigate the SD directory to chose files to flash. If there is something I'm missing, let me know.
Edit:
See post #7 below, it contains the file to get you back to 2.5.0.1!!
snovvman said:
I'm looking for CW 2.5.0.1(?) so I can flash radio and other files. It seems like 3.x "aborts" install with some files.
I have not been able to find the 2.5.x CW img for the Evo. Also, now that my phone is crippled (flashed a new ROM), how do I install the 2.5.x over the 3.x? ROM Manager does not give me the option to flash back to 2.5.x
I believe that the new clockwork is causing problems for a lot of people, myself included. I cant revert to an old clockwork like 2.5 either. I just had to flash RA 1.8 on my phone and my wife's Evo.
Click to expand...
Click to collapse
Rom manager has an option at the very bottom called "all clockwork recoveries"... Use that and select whatever build you want.
Sent from my pants. You figure out how I typed it.
Justin.G11 said:
Rom manager has an option at the very bottom called "all clockwork recoveries"... Use that and select whatever build you want.
Sent from my pants. You figure out how I typed it.
Click to expand...
Click to collapse
For some reason that method isn't working for a lot of people, myself included. The thing that is working is to flash RA 1.8
I tried several times to revert to an old clockwork and kept getting an error.
go here... http://www.clockworkmod.com/download/recoveries/
click the supersonic recovery you want... make sure its the .zip file.
put on ur SD card and flash. hope this helps
Justin.G11 said:
Rom manager has an option at the very bottom called "all clockwork recoveries"... Use that and select whatever build you want.
Sent from my pants. You figure out how I typed it.
Click to expand...
Click to collapse
cbond007 said:
For some reason that method isn't working for a lot of people, myself included. The thing that is working is to flash RA 1.8
I tried several times to revert to an old clockwork and kept getting an error.
Click to expand...
Click to collapse
Correct, the older versions in ROM Manager do not work for the Evo.
I ended up finding a pc36img.zip and flashed it. I am now back to 2.5.0.1. I don't use RA because I can't select files. It's a pain when I have a lot of files to flash.
Here is the Clockwork 2.5.0.1, packaged flashable.
Put it in the root of your SD, boot into bootloader, let it update, and life is good again...
Edit: Some additional info to save you some searching:
Make sure you flash using bootloader and NOT your current recovery. Power off, hold Vol Down, and Power On. Let it update the image, then reboot into recovery again. At that point, you should see 2.5.0.1.
ROM Manager does not properly downgrade. 2.5.1.4/3, I have been told, is not for Evo. You will need to flash manully as I described.
snovvman said:
It seems like 3.x "aborts" install with some files.
Click to expand...
Click to collapse
There's a more sinister problem with 3.0.0.1 (which appears to have now been retracted, as ROM Manager, after updating me to 3.0.0.1, is now showing "Latest Recovery: 3.0.0.0" at the time I write this).
It's only sheer chance that I had another unrelated problem, or I would have been screwed -- the Nandroid backup is broken in 3.0.0.1 (it completed the backup operation within about 2-3 seconds, clearly not having backed up everything!)
Edit: I checked in the backup directory, and the only files backed up by 3.0.0.1 were boot.img and recovery.img
Now that I reverted to 3.0.0.0, at least the backup takes a good long time and seems to be listing all the usual stuff, but I don't feel that I can trust 3.0 now.
I'm going back to what was working for me a couple of days ago (2.5.1.2) when I tried CyanogenMod (6.1.1) for the first time. ROM Manager and ClockworkMod Recovery handled it all so perfectly that I kicked it off with checkboxes enabled for the "back it up" and "wipe" options, got called away for about 1/2 hour, and when I returned, there was CM6 in all its beauty, even including the Google apps.
Is there an "official" place to report bugs for ClockworkMod Recovery? I noticed that the clockworkmod.com web site has gone poof (Google cache shows it intact on Dec 11th).
--tgi
HTC Supersonic / Sprint EVO 4G / Hardware 002
myn's Rooted Froyo 2.2 3.29.651.5 Radio 2.15.00.09.01 Kernel 2.6.32-ge2fb08e [email protected] #11
I'm sorry, but as an AR Recovery user, I see no reason to switch to Clockwork other than being able to browse folders other than the root of your memory card for ZIPs. AR seems much more stable and has had all of the features (except that one) that CW recently had added.
tgi007 said:
There's a more sinister problem with 3.0.0.1 (which appears to have now been retracted, as ROM Manager, after updating me to 3.0.0.1, is now showing "Latest Recovery: 3.0.0.0" at the time I write this).
[/COLOR]
Click to expand...
Click to collapse
When ROM Manager prompted me to update tonight, I got 3.0.0.2. I was able to complete a backup, including the WiMax partition. Going back to the advanced restore menu, I was given the option to backup WiMax and other partitions seperately.
Does flashing work properly now?
At this point I'm afraid to try.
Product F(RED) said:
Does flashing work properly now?
Click to expand...
Click to collapse
Flashing works just fine with 2.5.0.1.
snovvman said:
Flashing works just fine with 2.5.0.1.
Click to expand...
Click to collapse
+1
.......
snovvman said:
Here is the Clockwork 2.5.0.1, packaged flashable.
Put it in the root of your SD, boot into bootloader, let it update, and life is good again...
Click to expand...
Click to collapse
I have a Root folder I made in sd card and put the image file in folder in bootloader now its not reading it. what to do?
Edit: I figured it out and works perfect!! Thanks Button..
Product F(RED) said:
I'm sorry, but as an AR Recovery user, I see no reason to switch to Clockwork other than being able to browse folders other than the root of your memory card for ZIPs. AR seems much more stable and has had all of the features (except that one) that CW recently had added.
Click to expand...
Click to collapse
+1 on this I will have to admit other than folder search I see nothing better about CW over AR and AR has great wiping features and usb mode. But to each its own...
Product F(RED) said:
I'm sorry, but as an AR Recovery user, I see no reason to switch to Clockwork other than being able to browse folders other than the root of your memory card for ZIPs. AR seems much more stable and has had all of the features (except that one) that CW recently had added.
Click to expand...
Click to collapse
playya said:
+1 on this I will have to admit other than folder search I see nothing better about CW over AR and AR has great wiping features and usb mode. But to each its own...
Click to expand...
Click to collapse
Question for yoru guys: When you flash with RA (/AR), do you just rename the file and put it into the root of SD each time? Is there an easier way to flash with RA that I am not aware of?
snovvman said:
Here is the Clockwork 2.5.0.1, packaged flashable.
Put it in the root of your SD, boot into bootloader, let it update, and life is good again...
Click to expand...
Click to collapse
I tried this it says it runs the recovery but after I reboot and run rom manager it says clockworkmod 3.0.0.2. Am I missing a step?
snovvman said:
Question for yoru guys: When you flash with RA (/AR), do you just rename the file and put it into the root of SD each time? Is there an easier way to flash with RA that I am not aware of?
Click to expand...
Click to collapse
Not defending CW, but it does have USB Mode. It's just tucked away in the menu.
If I'm on my PC, I download and then just drag to the phone or I use Dropbox, then Astro to move it to the root. If I'm not, then I use Astro. I don't have to rename anything.
ARG! I flashed 2.5.0.1 and still non of my old backups work they all hang at the white htc boot screen. I am just booting into recovery and running restore should I be doing something first?

[Q] rooted evo... bricked evo... help!

got my evo about a month ago. rooted lastnight since unrevoked finally pushed out their 3.3 version which is updated for my version of hboot (2.02). the root went very smoothly. i installed the latest cyanogenmod rom, only to discover there was no market or gmail app with the rom! wish i had known that before. after doing some research online, i found out i needed to flash or install a "gapps" apk. so, looked around for that for a couple hours and couldn't find it. i downloaded what i thought would be the right .zip file to get the market on my phone (a vending.apk that was listed in another thread having to do with this same issue). so anyway... downloaded that, moved it to the root of my sd card, flashed it through clockworkmod recovery (by the way, everything up until this point was perfect) and finally rebooted my phone... only it never rebooted. the white htc EVO 4G screen was there. then, black screen, as if it was about to begin the cyanogenmod boot screen and fully boot. but, no. it went from white evo screen to black screen... to OFF. after this, i couldn't even turn it on to get it into hboot or access recovery. tried to do that for two hours. and finally i was able to get in... so i tried doing a factory/data reset through recovery, then a cache clear, then reboot. nothing. same thing. went back into recovery, tried reflashing cyanogenmod rom again. nothing. tried flashing myn's rom. nothing. all i get is installation aborted.
i am pretty sure that this is not a complete brick since i am now able to access hboot and recovery. but if i can't flash anything... and i'm stuck in hboot and recovery and cant boot my phone... what the hell do i do now? please help me figure this out!! anybody have any good advice or a known fix...??
Boot into recovery. Do a factory reset. then wipe cache and dalvik catch. Re flash cynagon and let it boot. You then need to find gapps.zip. Boot into recovery flashing gapps.zip.
i did all that. step by step. and when i reflashed the rom, that is when it wouldn't install, saying installation aborted. but, i'm gonna do it again. let's see if my phone wants to play nice now...
brtnygrey said:
i did all that. step by step. and when i reflashed the rom, that is when it wouldn't install, saying installation aborted. but, i'm gonna do it again. let's see if my phone wants to play nice now...
Click to expand...
Click to collapse
If that does not work! you are going to have to update with sprint lovers rom, that is in a PCM36IMG.ZIP. Install it by holding the _vol and th power button, boot into boot loader, than it will search for the zip file and ask you if you want to update, say yes ans just weigh for it to be done. Its going to take few minutes first boot! just hold on. I hope this helps in anyway.
evolishesh said:
If that does not work! you are going to have to update with sprint lovers rom, that is in a PCM36IMG.ZIP. Install it by holding the _vol and th power button, boot into boot loader, than it will search for the zip file and ask you if you want to update, say yes ans just weigh for it to be done. Its going to take few minutes first boot! just hold on. I hope this helps in anyway.
Click to expand...
Click to collapse
do you think that sprintlovers rom will install even if no other rom will install? because... i was able to install Gapps.zip file just fine. but every rom i install is unsuccessful.
brtnygrey said:
do you think that sprintlovers rom will install even if no other rom will install? because... i was able to install Gapps.zip file just fine. but every rom i install is unsuccessful.
Click to expand...
Click to collapse
The springlovers rom gets flashed the same way sprint flashes there upgrades so it should
Sent from my SPH-D700 using Tapatalk
mysteryemotionz said:
The springlovers rom gets flashed the same way sprint flashes there upgrades so it should
Sent from my SPH-D700 using Tapatalk
Click to expand...
Click to collapse
ok is the install through recovery supposed to be almost instantaneous? it didn't take a minute like every other rom. and after reboot (10 minutes ago) i'm still sitting on the white htc EVO 4G screen. i don't think this is working either. but i really do appreciate your help. any other suggestions? is there anything else through recovery that I can do (since i cant make it past that) that might fix my system? anything in partition? i'm so stuck!
mysteryemotionz said:
The springlovers rom gets flashed the same way sprint flashes there upgrades so it should
Sent from my SPH-D700 using Tapatalk
Click to expand...
Click to collapse
and also... when i go into hboot, and it runs through the "checking sd" thing before i can select options... it says "no image or wrong image". what?
Nothing is working!!
Did you try a rooted RUU yet?
http://forum.xda-developers.com/wiki/index.php?title=HTC_Supersonic/ROMs
Wipe everything twice first (just to be safe). Are you using Amon RA or Clockwork, by the way? The only other thing I can think of would be that your SD card isn't formatted properly, but that would have to mean you intentionally formatted it or put in a new one that didn't have the right files on it.
SilverZero said:
Did you try a rooted RUU yet?
http://forum.xda-developers.com/wiki/index.php?title=HTC_Supersonic/ROMs
Wipe everything twice first (just to be safe). Are you using Amon RA or Clockwork, by the way? The only other thing I can think of would be that your SD card isn't formatted properly, but that would have to mean you intentionally formatted it or put in a new one that didn't have the right files on it.
Click to expand...
Click to collapse
i am using clockwork. i've wiped so many times... but i can't make anything happen. and, i did format the sd card eventually, but not until a couple of hours ago... and only as a last resort because nothing else worked and i've been trying to fix this since last night, so i figured it couldn't hurt. but if that is part of the problem... how can i fix it? thanks for your response. i don't know what else to do other than take it in for a switch.l but if i can get into hboot... then sprint can too... and they will see that i'm rooted and void warranty. so am i completely screwed?
I had same issue.
I just reflashed the sprintlover rom (PC36IMG.ZIP) which came with Amon_RA recovery.
Then i installed the CM6 with Amon_RA recovery and everything works fine now.
Good that i did Titanium backup few days before
This is happening to me too. Almost everything he's describing is the same. Except I installed a gapps.zip and then it wouldn't boot after that. No matter what I flash, it either gives me a status 7 error and aborts the install or it may "install successfully" but it never boots. Also tried the pc36img.zip as well. I had a nandroid backup and tried to restore that, but that aborts saying cannot flash boot image. Tried a rooted and also an unrooted stock ruu, they won't work and the .exe version on a pc can't find my phone when I plug it in and power it on. Anyone have any Ideas for me. I can get more specific error messages and hboot numbers, etc. if needed.
I think you should get Amon recovery PCIMG zip file and change recovries and try everything again... IMO
Edit: I posted the Amon file and all you have to do is rename it to PCIMG.zip. Also I think the gapps you were looking for you can find on the cm site itself or within that thread. Sorry if it sounds like I a being negative but I see alot of people get on noob and I wondered why but unfortunately its because things like this happen. In the OP for CM6 it says to use Amon and backup your keys. Now if you get your phone backup you got to first check and make sure your RSA keys are in tact unless you backed them up already.
Joeykrim has a app on the market to check or there are numerous threads on what to do. Sorry and hope it works out for you if not INS is your friend
View attachment PC36IMG-Amon-V2.2.1.zip
playya said:
I think you should get Amon recovery PCIMG zip file and change recovries and try everything again... IMO
Click to expand...
Click to collapse
some people dont like clockwork with the evo's...thats just the general feeling im getting from the boards. i just got my evo rooted and what not. i use clockwork and it has worked well for what i need.
op, try amon like has been suggested.
tailsthecat3 said:
some people dont like clockwork with the evo's...thats just the general feeling im getting from the boards. i just got my evo rooted and what not. i use clockwork and it has worked well for what i need.
op, try amon like has been suggested.
Click to expand...
Click to collapse
Yea but have you tried Amon and from what I read and this is from developers Amon has a much better handle on things as far as backing stuff up, partitions and protection of keys.
I ran Clockwork on my wifes phone because to me its simple and works with Rom manager but after a while I just said F it and switched since it was messing up my backups. Hey to each his own..
Ok, I don't believe that your device is bricked. You may have flash the wrong gapps or something, but is should be easy to fix.
First, download these 3 files and put them on the root of your SD card:
Cyanogen 6 stable for evo
Latest gapps for HDPI
Calkulin's format all
Red through first, then follow my instructions EXACTLY:
1.) Boot into recovery.
2.) Flash Calkulin's all format. This will wipe everything that needs wiping. (everything but the SD card)
3.) Without exiting recovery immediately flash the CM6 .zip. Do not flash the gapps yet.
4.) Reboot the device now. It will boot into cyanogen, but will not have market or anything. Once fully booted, reboot to recovery.
5.) Do not wipe or anything, just flash the gapps HDPI.
6.) Boot the phone and enjoy.
Evo won't load any roms, can only get into clockwork recovery
Okay, so if I try your steps, just like before The install gets almost to the end, then I get:
"assert failed: write_raw_image ("/tmp/boot.img","boot")
E:Error in /sdcard/update-cm-6.1.2-supersonic-signed.zip
(Status 7)
Installation aborted.
Sorry Playya, I wanted to try this one more time first. I'm going to try loading Amon Ra now. do I need to rename it to pcimg.zip or should i just flash the current file name?
In case it helps anyone, I have
ClockworkMod Recovery v2.5.0.1
my boot loader screen shows
SUPERSONIC EVT3 SHIP S-OFF
HBOOT-2.10.0001
MICROP-041f
TOUBH PANEL-ATMELC03_16ac
RADIO-2.15.00.11.19
Oct 15 2010
Awesome, Amon Ra Worked, and now i'm up and running on cyanogen mod with google apps as well. My only problem now, is I can't backup, when I try it says oops... something went wrong! Please check the recovery log!
hcavlnch said:
Awesome, Amon Ra Worked, and now i'm up and running on cyanogen mod with google apps as well. My only problem now, is I can't backup, when I try it says oops... something went wrong! Please check the recovery log!
Click to expand...
Click to collapse
it may say oops if you battery level is low... I think Amon is so much better its just that Unrevoked puts Clockwork in with their root so people get lazy and leave it in... Amon - its the way to go.
1. Charge your battery and try again
2. Backup your wimax keys - then check how big the file is and hopefully its like 12 megs... If so keys may be ok

Major Major Issues With 2.1 - 2.3 (Rooted/Unrooted)

Hey guys,
So here's what happened and is happening:
1. I was running a custom ROM (Baked Snack 1.7) on Froyo (2.2). The phone was working fine but I wanted to try Gingerbread 2.3.3 out because I heard it had great battery life.
2. My phone would not update to 2.3.3 from Baked Snack. I thought it might have something to do with it being rooted. I used this method to unroot...and I think I only got through the first part:
http://www.thedroiddemos.com/2010/09/10/how-to-unroot-the-evo-in-2-steps/
I installed the S-On tool like he said to. Then I moved the "new updated version" of PC36IMG (I had the old version on my card already). He said something about the "S-Off" appearing on his phone but not the viewer's...well, mine says S-Off.
So fast forwarding, I got Sprint to push me the update for 2.3.3. It downloaded it, but then a voicemail error came up saying I had 2 voicemails. Then when I called voicemail, it said I had no messages. Sprint said a Sprint store would have to physically go into the phone to erase the error.
I also got a second update message that said there were minor enhancements to Gingerbread. I tried downloading them but the installation failed. Sprint told me to ignore the update, that there had been issues with Gingerbread (and the update) and that they were working on getting these resolved.
Somehow I managed to clear the phone and get back to 2.1. Here's what my system says when I look at the Phone Information:
Firmware Version: 2.1-update1
When I boot into the main bootloader/Recovery menu (Phone Off + Power Button + Volume Down), here's what it says:
Supersonic EVT2-2 ENG S-OFF
HBOOT-0.76.2000 (PC3610000)
If I click down to Recovery from this menu and press "Power" to enter it, NOW I get a picture of an EVO with a Red Triangle/Exclamation Point. This means I have to take my battery out and restart the phone.
Also, the OTA SimpleRoot procedure doesn't seem to work on the phone either. When I originally set it back, the procedure worked. Now it just goes through the motions on the computer but nothing happens with the phone (rebooting, skating Androids, etc.)
All I want to do is basically put it back 2.2 and re-run Baked Snack 1.7 which was giving me NO issues.
If someone could help me with this issue, I would be very grateful.
Well you have a simple fix. The error you got with the triangle and red ! is you booting into recovery, but no recovery is loaded [stock recovery]. Head over to the development section, and download the recovery of your choice. Personally I recommend in order: twrp [team win recovery project] , amon ra 2.3, cwm 3.0+. After you have your recovery installed, boot back into recovery and flash your baked snack rom. Also, don't manually take an OTA of 2.3.3 as it can't be rooted. if you want to try a gingerbread rom, simply download CM7, evervolv, deck's, ect rom and flash it like any other rom. Just backup your previous rom before flashing so you can go back.
teh roxxorz said:
Well you have a simple fix. The error you got with the triangle and red ! is you booting into recovery, but no recovery is loaded [stock recovery]. Head over to the development section, and download the recovery of your choice. Personally I recommend in order: twrp [team win recovery project] , amon ra 2.3, cwm 3.0+. After you have your recovery installed, boot back into recovery and flash your baked snack rom. Also, don't manually take an OTA of 2.3.3 as it can't be rooted. if you want to try a gingerbread rom, simply download CM7, evervolv, deck's, ect rom and flash it like any other rom. Just backup your previous rom before flashing so you can go back.
Click to expand...
Click to collapse
You like TWRP better??
I haven't tried it yet
HipKat said:
You like TWRP better??
I haven't tried it yet
Click to expand...
Click to collapse
Basically amon ra, but better. it has some additional options, such as the option to automatically reboot after a successful flash [good for doing a single flash, but if you're doing multiple, checked it at the last flash.] You have the option to compress backups to save space, though it takes a little bit longer, and they have some built in skins you can change at will. And MOAR.
I tried rooting using this method:
http://www.androidcentral.com/evo-4g-root-instructions
I put the PC36IMG on the root of my SD card and let the phone update in bootloader. It seemed to work fine, updated, rebooted the phone, etc.
Then I downloaded ROM Manager so I could let Clockwork install and then install Amon Ra....when ROM Manager tried installing Clockwork, it gave me the following message: "An error occurred while attempting to run privileged commands!"
It also will not let me flash an alternate recovery. I have the file "recovery-RA-supersonic-v2.3.img" on the root of my SD card right now.
What does this mean? Does this mean I'm not rooted? Or some other issue? I remember eons ago when I tried using this program I got the same message but I don't remember how I got around it. (obviously I did though)
Is there a different way I should install it?
nbakid2000 said:
I tried rooting using this method:
http://www.androidcentral.com/evo-4g-root-instructions
I put the PC36IMG on the root of my SD card and let the phone update in bootloader. It seemed to work fine, updated, rebooted the phone, etc.
Then I downloaded ROM Manager so I could let Clockwork install and then install Amon Ra....when ROM Manager tried installing Clockwork, it gave me the following message: "An error occurred while attempting to run privileged commands!"
It also will not let me flash an alternate recovery. I have the file "recovery-RA-supersonic-v2.3.img" on the root of my SD card right now.
What does this mean? Does this mean I'm not rooted? Or some other issue? I remember eons ago when I tried using this program I got the same message but I don't remember how I got around it. (obviously I did though)
Is there a different way I should install it?
Click to expand...
Click to collapse
That's a bit outdated; use unrevoked. I've already done the linking for you.
1. http://unrevoked.com/rootwiki/doku.php/public/windows_hboot_driver_install <- Download and install the modified hboot drivers, follow the instructions.
2. On your phone, enable usb debugging from the applications > development, in settings
3. Connect your phone to your pc via usb cable, leave it on the home screen, no apps should be running; restart the phone just to be sure.
4. http://unrevoked.com/rootwiki/doku.php/public/windows_hboot_driver_install <- download and run unrevoked
It'll take 3-5 minutes and reboot about 2 times, don't touch in the process, it'll say done at the end. Also, this will only work if on 2.2 still. if on 2.3.3, you're outta luck.
Okay, forget Rom Manager, forget "rooting" your phone - at least according to the normal use of the word.
Delete any PC36IMG files you may have on your SD card, then download this one of Amon Ra 2.3: http://db.tt/WP0beNa
Don't rename it, don't extract it... just put it on the root of your SD card. Then download whatever rom you want to use. Put it on the root of your SD card or in a folder that you'll remember. Amon Ra (and possibly other recoveries) can flash zips that are inside of folders. Just be sure that you know where it is because you'll need to navigate to it in recovery.
Then boot into the bootloader and let it flash the way you've done with other PC36IMG files. When it asks you to reboot just decline and then select recovery. I would make a backup just in case, then flash your rom.
Sent from my PC36100 using Tapatalk
Thank you guys, I will try these methods when I get back from work tonight. I really really appreciate it, I was about having a meltdown without my phone (the way I want it).
I'll report back either way. (and yes, I'm still on 2.1-update1)
nbakid2000 said:
Thank you guys, I will try these methods when I get back from work tonight. I really really appreciate it, I was about having a meltdown without my phone (the way I want it).
I'll report back either way. (and yes, I'm still on 2.1-update1)
Click to expand...
Click to collapse
Well between plainjane and myself, you'll be rooted before dinner time!
teh roxxorz said:
Well between plainjane and myself, you'll be rooted before dinner time!
Click to expand...
Click to collapse
OK, I forgot to mention this earlier...last time I was stuck in the Boot Sequence where it kept looping the Sprint and 4G logo....now that I'm rooted using plainjane's method (thank you) I'm stuck with the same thing.
I flashed the recovery, then flashed the Baked Snack ROM....now I'm in the Baked Snack bootload section....and it just keeps looping.
Is this an issue with my system that can be resolved?
EDIT: So weird. I went back into Recovery and wiped everything and set the phone back to original condition...and voila, Baked Snack comes up as the ROM! So now it appears it's for the most part back to normal and back to where I wanted it....thank you guys again.
Now can anyone point me in the direction of the latest radios, etc. that I can download and flash?
And why would it be giving me those looping problems, and then go back to normal when I cleared/wiped everything?
I mean, I'm happy this happened but I don't want the same things happening if I decide to flash another ROM at some point.

[Q] What Am I Doing Wrong...?

I have unbricked this phone probably 15 times in the past day trying to just install a custom ROM.
I run through the unbricking process, get root, load the stock AT&T ROM, factory reset, and it boots just fine from there. However, after I load Clockwork Mod and try to load any custom ROMs at all, the phone will just bootloop forever. It also appears to remove the Clockwork Mod recovery image as well, since I no longer am able to get back into recovery after the flash of the new ROM.
I've scoured this forum for hours, and I'm at a complete loss. Any ideas?
P.S. I made a backup of my ROM before doing all of this using the latest version of Clockwork Mod, but was unable to restore it. It seems that the 6.x.x.x version of the recovery for this phone is busted in some way, it always reports that it can't access any of the root folders, even though the phone has been rooted. The 5.x.x.x versions don't seem to do this, but I still have issues flashing.
SectorNine50 said:
I have unbricked this phone probably 15 times in the past day trying to just install a custom ROM.
I run through the unbricking process, get root, load the stock AT&T ROM, factory reset, and it boots just fine from there. However, after I load Clockwork Mod and try to load any custom ROMs at all, the phone will just bootloop forever. It also appears to remove the Clockwork Mod recovery image as well, since I no longer am able to get back into recovery after the flash of the new ROM.
I've scoured this forum for hours, and I'm at a complete loss. Any ideas?
P.S. I made a backup of my ROM before doing all of this using the latest version of Clockwork Mod, but was unable to restore it. It seems that the 6.x.x.x version of the recovery for this phone is busted in some way, it always reports that it can't access any of the root folders, even though the phone has been rooted. The 5.x.x.x versions don't seem to do this, but I still have issues flashing.
Click to expand...
Click to collapse
Is it possible that your hosts file needs modifying when installing the AT&T ROM? If the LG Support tool connects to LG's servers instead of your local http you set up, it will load the official ICS and completely wipe your phone to install that ROM... With my limited amount of knowledge, that's about all I could see if the process removes CWM Recovery.
Also, CWM 6.x is working fine for me, even manually flashed the touch recovery a few minutes ago, backed up my ROM and installed an updated ROM. No problems at all.
SectorNine50 said:
I have unbricked this phone probably 15 times in the past day trying to just install a custom ROM.
I run through the unbricking process, get root, load the stock AT&T ROM, factory reset, and it boots just fine from there. However, after I load Clockwork Mod and try to load any custom ROMs at all, the phone will just bootloop forever. It also appears to remove the Clockwork Mod recovery image as well, since I no longer am able to get back into recovery after the flash of the new ROM.
I've scoured this forum for hours, and I'm at a complete loss. Any ideas?
P.S. I made a backup of my ROM before doing all of this using the latest version of Clockwork Mod, but was unable to restore it. It seems that the 6.x.x.x version of the recovery for this phone is busted in some way, it always reports that it can't access any of the root folders, even though the phone has been rooted. The 5.x.x.x versions don't seem to do this, but I still have issues flashing.
Click to expand...
Click to collapse
I don't know if anyone has tried the unbrick method with the new version of cwm but you might try twrp. When a similar version of cwm was in beta there were all sorts of issues. So maybe they haven't been fixed. Also are you installing cwm from GB? ICS has a locked boot loader so that might also be an issue.
http://forum.xda-developers.com/showthread.php?t=1888910
Now I would start with the unbricking guide for a 16th time but follow the directions to install twrp instead of cwm. You might also find you like it better. Good luck.
Sent from my LG-P930 using xda app-developers app
lordcheeto03 said:
Is it possible that your hosts file needs modifying when installing the AT&T ROM? If the LG Support tool connects to LG's servers instead of your local http you set up, it will load the official ICS and completely wipe your phone to install that ROM... With my limited amount of knowledge, that's about all I could see if the process removes CWM Recovery.
Also, CWM 6.x is working fine for me, even manually flashed the touch recovery a few minutes ago, backed up my ROM and installed an updated ROM. No problems at all.
Click to expand...
Click to collapse
I don't believe that the unbricking process would work if the hosts file was wrong, but I checked it again anyway, and it appears to be correct.
The AT&T ROM gets pushed via the abd shell after the unbrick and rooting process. The root appears to work, as the AT&T ROM that I push works fine, it's just not the ROM I want!
Swetnes said:
I don't know if anyone has tried the unbrick method with the new version of cwm but you might try twrp. When a similar version of cwm was in beta there were all sorts of issues. So maybe they haven't been fixed. Also are you installing cwm from GB? ICS has a locked boot loader so that might also be an issue.
http://forum.xda-developers.com/showthread.php?t=1888910
Now I would start with the unbricking guide for a 16th time but follow the directions to install twrp instead of cwm. You might also find you like it better. Good luck.
Sent from my LG-P930 using xda app-developers app
Click to expand...
Click to collapse
After the unbricking process (after I get through all the nonsense on the Korean ROM), the phone is running the GB AT&T ROM, from there I push the CWM recovery.img to the phone using the abd shell. All seems to be working perfectly up until I go to flash the custom ROM! I don't get any errors when I flash the .zip either.
Initially I had installed CWM 6.x.x.x using the ROM Manager application. That's before all this nonsense started, and the phone was on the stock (but rooted) AT&T ICS ROM, so I know that's why I "bricked" my phone the first time.
I'll give TWRP a shot, hopefully that will work.
SectorNine50 said:
I don't believe that the unbricking process would work if the hosts file was wrong, but I checked it again anyway, and it appears to be correct.
The AT&T ROM gets pushed via the abd shell after the unbrick and rooting process. The root appears to work, as the AT&T ROM that I push works fine, it's just not the ROM I want!
After the unbricking process (after I get through all the nonsense on the Korean ROM), the phone is running the GB AT&T ROM, from there I push the CWM recovery.img to the phone using the abd shell. All seems to be working perfectly up until I go to flash the custom ROM! I don't get any errors when I flash the .zip either.
Initially I had installed CWM 6.x.x.x using the ROM Manager application. That's before all this nonsense started, and the phone was on the stock (but rooted) AT&T ICS ROM, so I know that's why I "bricked" my phone the first time.
I'll give TWRP a shot, hopefully that will work.
Click to expand...
Click to collapse
Ok so we know it's not the boot loader issue of ICS after dozens if not hundreds of successful installs using the unbricking guide the only thing left is the new version of cwm. Hopefully twrp will do the trick for you. Has anyone out there successfully completed the unbricking guide with the new version of cwm?
Sent from my LG-P930 using xda app-developers app
Swetnes said:
Ok so we know it's not the boot loader issue of ICS after dozens if not hundreds of successful installs using the unbricking guide the only thing left is the new version of cwm. Hopefully twrp will do the trick for you. Has anyone out there successfully completed the unbricking guide with the new version of cwm?
Sent from my LG-P930 using xda app-developers app
Click to expand...
Click to collapse
I haven't tried the TWRP recovery a shot yet, since I haven't been home, but I figured it was worth pointing out that the CWM 5.x.x.x (can't remember exact version numbers right now) didn't work for me either. Every time I flashed a ROM, I'd end up with a boot loop on first boot, and then when I'd try to go back into recovery, I'd find that it wouldn't go back in there either.
It was basically acting like when I flashed the ROM that it overwrote the recovery partition, except no one else seems to have this same issue. Yet, if I didn't flash a ROM, I was able to go in and out of CWM recovery as often as I wanted.
Bah.
SectorNine50 said:
I haven't tried the TWRP recovery a shot yet, since I haven't been home, but I figured it was worth pointing out that the CWM 5.x.x.x (can't remember exact version numbers right now) didn't work for me either. Every time I flashed a ROM, I'd end up with a boot loop on first boot, and then when I'd try to go back into recovery, I'd find that it wouldn't go back in there either.
It was basically acting like when I flashed the ROM that it overwrote the recovery partition, except no one else seems to have this same issue. Yet, if I didn't flash a ROM, I was able to go in and out of CWM recovery as often as I wanted.
Bah.
Click to expand...
Click to collapse
Can you clarify exactly what method you are using to flash the ROM? I just can't imagine a scenario where flashing a ROM would overwrite the recovery. What ROM are you flashing?
Also, please confirm what phone you have.
drumist said:
Can you clarify exactly what method you are using to flash the ROM? I just can't imagine a scenario where flashing a ROM would overwrite the recovery. What ROM are you flashing?
Also, please confirm what phone you have.
Click to expand...
Click to collapse
Sure, I may be using the wrong term (my first experiences with custom ROMs date back to Windows Mobile, so the terminology probably blends together), but I'm basically loading the .zip from the SD Card in CWM. I've tried both the CM9 P930 ROM and Paranoid Android CM10.
That was my thought too, I didn't think that the custom ROMs even had recovery images in them. I may be wrong in saying that it deletes CWM, but after the wipe and flash I am no longer able to access it.
I have the LG Nitro HD, and from what I can gather, that is the P930, correct? I hope the issue I'm having is as simple as I'm flashing for the wrong phone...
By the way, thank you all for your help and input, I really appreciate it!
SectorNine50 said:
Sure, I may be using the wrong term (my first experiences with custom ROMs date back to Windows Mobile, so the terminology probably blends together), but I'm basically loading the .zip from the SD Card in CWM. I've tried both the CM9 P930 ROM and Paranoid Android CM10.
That was my thought too, I didn't think that the custom ROMs even had recovery images in them. I may be wrong in saying that it deletes CWM, but after the wipe and flash I am no longer able to access it.
I have the LG Nitro HD, and from what I can gather, that is the P930, correct? I hope the issue I'm having is as simple as I'm flashing for the wrong phone...
By the way, thank you all for your help and input, I really appreciate it!
Click to expand...
Click to collapse
You are correct, the Nitro is P930. And I'm sure this doesn't need pointing out, but when you download the ROM, make sure it's for P93x and not SU640. Most of the ROMS in the developer section have versions for both models.
Also, when you say you can't access CWM after flashing a ROM, how are you trying to access it? Holding Power+Volume down until the Factory Reset screen pops up? It still shows that screen even with CWM installed, but when you press the power button to perform the factory reset it SHOULD take you into CWM Recovery instead.
SectorNine50 said:
Sure, I may be using the wrong term (my first experiences with custom ROMs date back to Windows Mobile, so the terminology probably blends together), but I'm basically loading the .zip from the SD Card in CWM. I've tried both the CM9 P930 ROM and Paranoid Android CM10.
That was my thought too, I didn't think that the custom ROMs even had recovery images in them. I may be wrong in saying that it deletes CWM, but after the wipe and flash I am no longer able to access it.
I have the LG Nitro HD, and from what I can gather, that is the P930, correct? I hope the issue I'm having is as simple as I'm flashing for the wrong phone...
By the way, thank you all for your help and input, I really appreciate it!
Click to expand...
Click to collapse
To access recovery, turn the device completely off. (If you're in a bootloop, pull battery or hold power button for ~20 seconds until screen stays off.) Then when phone is off, press and hold volume down and power buttons at the same time, not releasing until you see text asking if you want to factory reset. Press power button twice to confirm and you'll get to recovery.
Is this the method you're using to try to get to CWM?
My guess as to why you are getting bootloops is that you aren't wiping data first.
Yup, that's how I'm accessing CWM. After the flash, after I press the power button twice, I get something similar to a boot loop. A recovery boot loop, if you will.
Well, I've tried a couple ways now. I've tried using the "factory reset/wipe user data" menu item in CWM, and I've tried going into each partition and wiping them individually before flashing as well.
Just got home, I'll try flashing using the TWRP and let you guys know.
SectorNine50 said:
Yup, that's how I'm accessing CWM. After the flash, after I press the power button twice, I get something similar to a boot loop. A recovery boot loop, if you will.
Well, I've tried a couple ways now. I've tried using the "factory reset/wipe user data" menu item in CWM, and I've tried going into each partition and wiping them individually before flashing as well.
Just got home, I'll try flashing using the TWRP and let you guys know.
Click to expand...
Click to collapse
Good luck. Other possible things to try:
1) Check zip MD5 hash (or just redownload and replace) to make sure it's not corrupted.
2) Reformat entire SD card.
Interesting update:
I decided to give getting back into CWM recovery one more shot before I went through the process of re-unbricking again, and this time it managed to get in (for whatever reason).
So, I did a factory wipe, cleared dalvik cache, flashed the ParanoidAndroid ROM, backed out, did another factory wipe, and tried to reboot into the newly flashed ROM.
No luck. Boot looped, and didn't even get to the ROM animation. Following that, I had trouble getting back into the CWM recovery. Managed to try about 5 times and finally got in, however CWM stated:
Code:
CWM-based Recovery v5.0.2.7
E:Error in /cache/recovery/last_log
(Read-only file system)
So... my phone may have potentially unrooted it's self, somehow... Interestingly, it still shows the file systems as mounted.
So, now I'm doing a full SD card reformat. Figured I'd get that variable out of the way before I go any further.
SectorNine50 said:
Interesting update:
I decided to give getting back into CWM recovery one more shot before I went through the process of re-unbricking again, and this time it managed to get in (for whatever reason).
So, I did a factory wipe, cleared dalvik cache, flashed the ParanoidAndroid ROM, backed out, did another factory wipe, and tried to reboot into the newly flashed ROM.
No luck. Boot looped, and didn't even get to the ROM animation. Following that, I had trouble getting back into the CWM recovery. Managed to try about 5 times and finally got in, however CWM stated:
Code:
CWM-based Recovery v5.0.2.7
E:Error in /cache/recovery/last_log
(Read-only file system)
So... my phone may have potentially unrooted it's self, somehow... Interestingly, it still shows the file systems as mounted.
So, now I'm doing a full SD card reformat. Figured I'd get that variable out of the way before I go any further.
Click to expand...
Click to collapse
You are installing the wrong version of CWM. Never use anything older than 5.8.2.0. This is the one you want: http://download2.clockworkmod.com/recoveries/recovery-clockwork-5.8.2.0-p930.img
Anything older than that is known to not work.
Second thing: You seem to have an incorrect understanding of what "root" means. Having "root" simply means you have administrator access to your current ROM. When you install a new ROM, whether you had root access to your old ROM is meaningless frankly.
drumist said:
You are installing the wrong version of CWM. Never use anything older than 5.8.2.0. This is the one you want: http://download2.clockworkmod.com/recoveries/recovery-clockwork-5.8.2.0-p930.img
Anything older than that is known to not work.
Second thing: You seem to have an incorrect understanding of what "root" means. Having "root" simply means you have administrator access to your current ROM. When you install a new ROM, whether you had root access to your old ROM is meaningless frankly.
Click to expand...
Click to collapse
Ah, thank you! I must've been viewing an old thread. Now that I look at the version number, it appears that's the version I had been hunting for since the newest one didn't work.
Interesting, I most certainly misunderstood, I was under the impression that "rooting" the device was a filesystem level permission change. Good to know!
It seems like we are getting closer to a solution here. Thanks for your patience!
Well, that appears to have been my problem the whole time! That's kind of embarrassing, considering how much time I sunk into this and how simple the solution was!
Anyway, thank you all very much! I assume that TWRP would have also solved my problems as well. It would seem that both the older and newest versions of CWM have some problems (at least for me!).
SectorNine50 said:
Well, that appears to have been my problem the whole time! That's kind of embarrassing, considering how much time I sunk into this and how simple the solution was!
Anyway, thank you all very much! I assume that TWRP would have also solved my problems as well. It would seem that both the older and newest versions of CWM have some problems (at least for me!).
Click to expand...
Click to collapse
Yeah, the new one (6.0.1.5) just came out. I'll have to test it to see if it works for me.
For what it's worth, I haven't had any issues with 6.0.1.5 yet. The touch version is a must, though.
Malnilion said:
For what it's worth, I haven't had any issues with 6.0.1.5 yet. The touch version is a must, though.
Click to expand...
Click to collapse
Have you had a chance to compare to twrp?
Sent from my LG-P930 using xda app-developers app
Swetnes said:
Have you had a chance to compare to twrp?
Sent from my LG-P930 using xda app-developers app
Click to expand...
Click to collapse
I really enjoy the integration Rom Manager/CM Updater has with CWM. If twrp is capable of running the install scripts those two use, I might consider trying it out, but I don't really like manually going through the steps to flash a rom every day.

Categories

Resources