I wanted to know if we could update clockwork recovery threw rom manager currently have 2.0.13 the new one is 2.0.21.
Sent from my ADR6300 using XDA App
jeaton313 said:
I wanted to know if we could update clockwork recovery threw rom manager currently have 2.0.13 the new one is 2.0.21.
Sent from my ADR6300 using XDA App
Click to expand...
Click to collapse
Just update and boot to recovery and see if it stuck or not. If I remember correctly it doesn't stick right now because we don't have NAND root. I had to use the unrevoked flash tool for both updates so far otherwise it just downloads but never flashes.
I am conditioning my batterystats.bin right now so I cannot try it, sorry.
You can boot into once you flash it with Rom Manager but once you reboot it its gone, just tried it.
Ok I'll give my clarification again:
"Fully rooted" is a meaningless term. You have superuser access on your phone, that means you have root.
An additional level of protection that HTC has added to their phones is a NAND-flash chip which is locked by a memory protection unit. This is below the OS level, and thus below superuser. You can still have full root access to your phone, and not have access to this chip. The reflash tool unlocks NAND and reflashes the recovery partition.
The only way to unlock this at the hardware level is an exploit, or by changing hboot such that it does not initiate the NAND protection. We are still hesitant to flash hboot. If you mess up reflashing recovery, you have an unlimited number of chances to get it right. If you mess up reflashing hboot, you have a permanent brick.
Thus, since the recovery partition is protected by this hardware-level memory protection unit, ROM manager cannot reflash the recovery partition. You people seem to say that this is "not fully rooted" so "it is not sticking". Whatever. Yes, it won't "stick". No, this doesn't actually matter. You get *precisely* the same effect by updating in ROM manager. If there is a critical update that requires flashing, we will make sure that our users obtain this update.
Ryan
unrevoked team
rpearl said:
If you mess up reflashing recovery, you have an unlimited number of chances to get it right. If you mess up reflashing hboot, you have a permanent brick.
Click to expand...
Click to collapse
Thanks for the clarification.
Why, may I ask, is your team so hesitant to flash hboot? This was integral part to development on the G1/Dream until this year, when certain saavy devs developed workarounds for flash-storage limitations (i.e., no ROMs above 64mb). Many of us took the DangerSPL leap and our G1s lived to run 30mb+ extra partition space. Why the hesitancy on Unrevoked's part, then? Are the chances very good that the procedure will brick/trip nand-security to lock-up the device -- a.k.a. bricking it?
I'm curious, any info is appreciated.
There appears to be error-code-correction which we triggered last time we tried flashing hboot, resulting in binny's brick.
We think we can try again, and we will soon enough.
Can you flash the new recovery with unrevoked flash tool.
Sent from my ADR6300 using XDA App
I flashed the Clockwork Mod Recovery to 2.0.21 and when I reboot Rom Manager says I have 2.0.21 still. It seems to have stuck for me?
Try turning off the phone and then booting into recovery. Im prtty sure it wont stick then
Sent from my ADR6300 using XDA App
I have rebooted, went into recovery, wiped the device, loaded a rom, and installed Rom Manager again. It still says it has 2.0.21. Maybe Rom Manager is just reading it wrong?
My clockwork recovery has stuck as well. I also updated it with rom manager and its still there. Has been for a couple weeks now.
Sent from my HTC Incredible using Tapatalk
intenselyinsane said:
My clockwork recovery has stuck as well. I also updated it with rom manager and its still there. Has been for a couple weeks now.
Sent from my HTC Incredible using Tapatalk
Click to expand...
Click to collapse
Don't reboot into recovery from rom manager. Physically turn off the phone by using the power button or pulling the battery, and then boot into recovery by holding down power and volume down and then selecting recovery. Then check your version of recovery.
I have booted through rom manager, pulled the battery, used quick boot recovery and used adb reboot recovery. All have the same one.
Sent from my HTC Incredible using Tapatalk
rpearl said:
Ok I'll give my clarification again:
"Fully rooted" is a meaningless term. You have superuser access on your phone, that means you have root.
An additional level of protection that HTC has added to their phones is a NAND-flash chip which is locked by a memory protection unit. This is below the OS level, and thus below superuser. You can still have full root access to your phone, and not have access to this chip. The reflash tool unlocks NAND and reflashes the recovery partition.
The only way to unlock this at the hardware level is an exploit, or by changing hboot such that it does not initiate the NAND protection. We are still hesitant to flash hboot. If you mess up reflashing recovery, you have an unlimited number of chances to get it right. If you mess up reflashing hboot, you have a permanent brick.
Thus, since the recovery partition is protected by this hardware-level memory protection unit, ROM manager cannot reflash the recovery partition. You people seem to say that this is "not fully rooted" so "it is not sticking". Whatever. Yes, it won't "stick". No, this doesn't actually matter. You get *precisely* the same effect by updating in ROM manager. If there is a critical update that requires flashing, we will make sure that our users obtain this update.
Ryan
unrevoked team
Click to expand...
Click to collapse
Ryan-
Thanks for the detailed reply - it's the first explanation I've read regarding the protected NAND memory and makes perfect sense. I appreciate your taking the time out to 'splain it.
You can flash the new recovery on rom manager it works.
Sent from my ADR6300 using XDA App
giantcrazy said:
Ryan-
Thanks for the detailed reply - it's the first explanation I've read regarding the protected NAND memory and makes perfect sense. I appreciate your taking the time out to 'splain it.
Click to expand...
Click to collapse
Agreed 100000000000% - Much Appreciated!
fader01 said:
I flashed the Clockwork Mod Recovery to 2.0.21 and when I reboot Rom Manager says I have 2.0.21 still. It seems to have stuck for me?
Click to expand...
Click to collapse
doesn't make sense... you flashed it to something you wanted? And it shows its the one you flashed? so whats the problem? 2.0.2.1 is the most current version.
x1208x said:
doesn't make sense... you flashed it to something you wanted? And it shows its the one you flashed? so whats the problem? 2.0.2.1 is the most current version.
Click to expand...
Click to collapse
Well if you read the whole thread you would see others saying it doesnt stick. So I was puzzled as to why it seemed to stick for me.
But after I went into Clockwork and looked at the version there I understood what everyone was saying ... Rom Manager is saying its the newest version but in realitity it is the old version still.
fader01 said:
Well if you read the whole thread you would see others saying it doesnt stick. So I was puzzled as to why it seemed to stick for me.
But after I went into Clockwork and looked at the version there I understood what everyone was saying ... Rom Manager is saying its the newest version but in realitity it is the old version still.
Click to expand...
Click to collapse
Oh i see what you are saying. weird. tweet koush!
x1208x said:
Oh i see what you are saying. weird. tweet koush!
Click to expand...
Click to collapse
He knows it doesn't work... it can't work for reasons already explained by rpearl. It also doesn't matter that it doesn't work.
Please don't make Koush cranky with unnecessary noise.
Related
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
Does clockworkmod overwrite the stock recovery? If it does then to me it is not a safe method to root a phone. If something goes wrong while flashing clockwork you will lose the stock recovery and can never reflash anything else. Is my understanding correct? This is why I am hesitant to root my phone. Please advice.
Thanks.
datzstr8 said:
Does clockworkmod overwrite the stock recovery? If it does then to me it is not a safe method to root a phone. If something goes wrong while flashing clockwork you will lose the stock recovery and can never reflash anything else. Is my understanding correct? This is why I am hesitant to root my phone. Please advice.
Thanks.
Click to expand...
Click to collapse
Its fairly safe. You could always flash the recovery thru odin found here:
http://forum.xda-developers.com/showthread.php?t=1332103
Has anyone tried to flash clockwork and failed? What happened afterwards? I assume odin won't work anymore because it requires a recovery partition to work.
I guess what I am still confused about is if clockwork writes over the stock recovery or does it keep the stock recovery in-tacked. I would prefer the later since then you can never break your phone.
With my dilemma would it be best for me to not install clockwork and just use an insecure kernel? Thanks.
It does overwrite the stock recovery i believe. But its very safe to flash. Ive never heard of someone borking a phone installing cwm recovery.
I have literally NEVER had a problem with clockworkmod, it's one of the best pieces of mobile software I've ever used.
kabuk1 said:
I have literally NEVER had a problem with clockworkmod, it's one of the best pieces of mobile software I've ever used.
Click to expand...
Click to collapse
Whole heartedly agree.
Sent from my SGH-T989 using xda premium
datzstr8 said:
Has anyone tried to flash clockwork and failed? What happened afterwards? I assume odin won't work anymore because it requires a recovery partition to work.
I guess what I am still confused about is if clockwork writes over the stock recovery or does it keep the stock recovery in-tacked. I would prefer the later since then you can never break your phone.
Click to expand...
Click to collapse
Odin has NOTHING to do with the recovery partition. ODIN only works in download mode on your phone. You can have a blank recovery partition and it'll still work, as well as the rom, and flashing other things too. The recovery partition stock has one function, to do a factory reset incase of problems. (Not to be confused with the one from inside android, that only formats /data. This one replaces the system partition as well.) CWM is very safe, I really wouldn't worry about it. Just follow the instructions carefully and you'll be fine.
Also, once you get cwm installed on there, I'd suggest doing a backup before you make any changes. Always handy to have your stock image at hand, just incase.
And also, even with stock recovery, you can still break your phone. It's not easy to brick a GS2, but it can be done. Just remember, as long as you can get the phone into download mode, it's not bricked. You can always odin back the stock partitions if you run into issues.
I was a little worried about using it with this phone. No problems to report. Just had to make backup in recovery.
Sent from my SGH-T989 using xda premium
Thanks mstrk242 for the great explanation. I thought the "download" and "recovery" were two states of a single program. It is clear now that they are separate. You just cleared all my worries.
You said "It's not easy to brick a GS2, but it can be done," can you tell me how this can happen? Just curious. Thanks much.
If you're going to be rooting/flashing at all, you'll have to get comfortable with cwm, Odin, and the other tools that are available for the phone.
This is my second Android phone, both have been rooted with custom roms, and at any point I've run into trouble (which is rare) I've found the tools and the help I need on here by searching a little bit. If you're willing to spend the time doing a bit of reading and know your way around a computer a bit, you won't have a problem. Just make sure you're 100% sure whatever you're flashing is for YOUR phone hardware.
It's not nearly as scary as it sounds once you get going on it and there's a lot to benefit from it.
Cheers and good luck.
Sent from my SGH-T989 using xda premium
datzstr8 said:
Thanks mstrk242 for the great explanation. I thought the "download" and "recovery" were two states of a single program. It is clear now that they are separate. You just cleared all my worries.
You said "It's not easy to brick a GS2, but it can be done," can you tell me how this can happen? Just curious. Thanks much.
Click to expand...
Click to collapse
Easiest way is to flash a rom for the wrong phone and mess up the partition table. (IE flash an international version of the gs2 rom, you'll brick.)
As long as you get cwm installed on there, and flash the correct roms, you should really be ok.
You can go back to the stock recovery easily. You can do it through Odin or flash an unroot rom
Sent from my SGH-T989 with ClockworkMod ★Touch★ Recovery 5.8.1.3
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.
Hello all,
I have partially bricked my phone while attempting to root. Admittedly, I am very much so a novice when it comes to rooting android devices, but I have learned a lot while attempting to fix it. My problem is that when I power it up, it hangs at the white HTC splash screen and never boots past that. At first, I tried simply to flash a stock rom. No success. I have also tried using an RUU and a stock clockwork recovery image. No success with either of these. While fiddling around in recovery, however, I have noticed something that might be the cause of the problem. Anytime I attempt to do anything in recovery, most of the time the following messages are returned: "error mounting /data/!" and "error mounting /cache/!"
Now, it is my belief that somehow (and I'm embarrassed to admit I've done such a number on my poor little phone) I deleted or incorrectly formatted the internal partitions, rendering them unusable. I have been reading, and it seems that the solution lies within a tool called sdparted. However, I am very afraid to totally brick my phone, so I came here for some help. Basically, I'm hoping someone can explain it to me like I'm 12 years old, haha.
Anyway, are my assumptions correct, or do I have a totally different kind of problem? Ideally, I would like to just completely return this to stock and bring about the end of this nightmare. Anyone who can help, I'm begging for your expertise!
Here is all the data I could think to give you all about my phone:
S-On
HBoot:0.98.0000
Radio:1.09.01.0312
Recovery-
Build: RA-VIVOW-v3.0.8
Well first mistake was unlocking instead of s-off. Also, try a a newer recovery like 4ext.net
Sent from my ASUS Transformer Pad TF300T using Tapatalk 4 Beta
tylerlawhon said:
Well first mistake was unlocking instead of s-off. Also, try a a newer recovery like 4ext.net
Sent from my ASUS Transformer Pad TF300T using Tapatalk 4 Beta
Click to expand...
Click to collapse
Not sure you can flash 4ext through adb...isn't only an apk that installs the recovery (if I remember correctly). I would try the latest CWM recovery first. And I agree that you need to get S-OFF - try one of the guides (like the one by Prototype).
tylerlawhon said:
Well first mistake was unlocking instead of s-off. Also, try a a newer recovery like 4ext.net
Sent from my ASUS Transformer Pad TF300T using Tapatalk 4 Beta
Click to expand...
Click to collapse
Hmmmm... Just logging in real quick after a hard day of work, will try that tomorrow and let you know the results.
brymaster5000 said:
Not sure you can flash 4ext through adb...isn't only an apk that installs the recovery (if I remember correctly). I would try the latest CWM recovery first. And I agree that you need to get S-OFF - try one of the guides (like the one by Prototype).
Click to expand...
Click to collapse
Ok, I tried flashing several different CWM images. Do you mean install CWM recovery over my current Ra recovery? And then proceed? Because as it stands, after attempting to flash the images through recovery, (and while it goes through most of it while looking successful) it seems to finish too quickly. Then, after rebooting, nothing was changed.
How would I go about installing CWM recovery over my current recovery? Should I bother doing this? Or how can I achieve S-Off from my current state? I vaguely remember coming to the conclusion that I couldn't get to S-off until I just completely flashed it back to stock. But then again, it's been a week since I've played with this phone. And I'm a complete noob. So any further advice would be appreciated.
RRCriswell said:
Hmmmm... Just logging in real quick after a hard day of work, will try that tomorrow and let you know the results.
Ok, I tried flashing several different CWM images. Do you mean install CWM recovery over my current Ra recovery? And then proceed? Because as it stands, after attempting to flash the images through recovery, (and while it goes through most of it while looking successful) it seems to finish too quickly. Then, after rebooting, nothing was changed.
How would I go about installing CWM recovery over my current recovery? Should I bother doing this? Or how can I achieve S-Off from my current state? I vaguely remember coming to the conclusion that I couldn't get to S-off until I just completely flashed it back to stock. But then again, it's been a week since I've played with this phone. And I'm a complete noob. So any further advice would be appreciated.
Click to expand...
Click to collapse
Use prototype's guide in the dev section. Look for the cwm thread and click on the flash instructions through adb command.
Sent from my Ascended Dinc2.
i have the exact same issue with a Inc 1. i have tried everything (including sdparted) with absolutely no luck. tried flashing the stock RUU, even unrooted and nothing worked. never could find anyone to know of a fix. i wish you the best of luck. will be watching this in hopes that you figure something out.
I've been searching for a solution before writing my own post, for I'm aware there are probably many, many topics of people dealing with the same issue.
Well, here's is my problem.
I've got two wildfires A3333. Flashed CM 7.2.0 on both of them, successfully. GPS does work on only one of them. I've tried the GPS test on the other one. The compass is working, the localization is not.
So, as said before, I've googled for some solution for the other one, and here comes the temporary downgrading of CWM to 2.5.0.7 and then installing one of the following: buzz.radio-3.35.15.31-signed.zip, buzz.radio-3.35.20.10-signed.zip or buzz.radio-3.35.19.25-signed.zip that will be put on the SD.
Ok, everything is set up, let's reboot to recovery.
Now, the recovery screen is showing version 3.0.0.6 and I don't know if that's normal, since I've set it to 2.5.0.7 before rebooting. Won't mind for now.
Let's flash the zips. And all I get is this message, with all of the radios:
E: signature verification failed
Installation aborted.
Uhm, let's try by setting the option toggle signature verification to disabled.
Here's a different message:
Amend scripting (update-script) is no longer supported. Amend scripting was deprecated by Google in Android 1.5. It was necessary to remove it when upgrading to the Clockworkmod 3.0 Gingerbread based recovery.
Please switch to Edify scripting (updater-script and update-binary) to create working update zip packages.
Installation aborted.
It seems that the 3.0.0.6 version shown on the main menu is kind of relevant... Should it show 2.5.0.7 instead of that? What now?
Thanks in advance.
After flashing the temporary CWM,it'll automatically boot into that CWM version. Now flash the radio with that.
And if you reboot you'll return to the CWM version you had before.
To fix GPS you could also use this method,
http://forum.xda-developers.com/showthread.php?t=2354499
lakshan_456 said:
After flashing the temporary CWM,it'll automatically boot into that CWM version. Now flash the radio with that.
And if you reboot you'll return to the CWM version you had before.
To fix GPS you could also use this method,
http://forum.xda-developers.com/showthread.php?t=2354499
Click to expand...
Click to collapse
Yes, if by "flashing the temporary CWM" you mean entering the ROM manager, tapping on All ClockwordMod Recoveries, download the 2.5.0.7 version, let it install and tap Reboot into recovery, well that's exactly what I did. And the recovery screen is showing me this 3.0.0.6 version anyway, which is kind of suspicious to me.
I've already read the topic you linked, some days ago, but that means having to wipe the CM 7.2.0 and reinstall it later and I'm not sure whether I can backup the apps that are in the EXT partition since I'm using Link2SD. And honestly, I'm not even sure I'm able to make a good backup.
Snakebar said:
Yes, if by "flashing the temporary CWM" you mean entering the ROM manager, tapping on All ClockwordMod Recoveries, download the 2.5.0.7 version, let it install and tap Reboot into recovery, well that's exactly what I did. And the recovery screen is showing me this 3.0.0.6 version anyway, which is kind of suspicious to me.
I've already read the topic you linked, some days ago, but that means having to wipe the CM 7.2.0 and reinstall it later and I'm not sure whether I can backup the apps that are in the EXT partition since I'm using Link2SD. And honestly, I'm not even sure I'm able to make a good backup.
Click to expand...
Click to collapse
I wouldn't really recommend using ROM Manager, and what I meant by flashing was to flash the CWM zip with your current Clockworkmod recovery.
And also consider upgrading your recovery.
And about the guide, just make a nandroid backup with CWM, and restore it instead of flashing a new rom.
Hope this helps
I shall give a try to it all and let you know.
One last question before I proceed. In order to upgrade my recovery I'd have to download the latest CWM available for Buzz and install it the same way I'll do with v2.5.0.7 (of course, after that step), am I right?
Thanks!
Ok, I've installed the v2.5.0.7 via the install from .zip option and got to install the radios. Woo!!
No, hold back.
Now the GPS icon is showing up but GPStest doesn't detect any activity.
I've installed 13.55.55.24H_3.35.20.10 first, then 13.45.55.24H_3.35.15.31 and then 13.53.55.24H_3.35.19.25. Same result.
Now should I rely on plan B?
I've read of someone who got it working by installing the 3 radios in crescent order. Is it worth a try?
Snakebar said:
I shall give a try to it all and let you know.
One last question before I proceed. In order to upgrade my recovery I'd have to download the latest CWM available for Buzz and install it the same way I'll do with v2.5.0.7 (of course, after that step), am I right?
Thanks!
Click to expand...
Click to collapse
No, that'll only be temporary, as with 2.5.
Get the PC49IMG.zip file for that recovery, put it on the root of the SD, reboot to bootloader, it'll scan and will ask to install, select yes, you're done.
First GPS fix will take some time, maybe from 2-10 mins.
I've only flashed the .20.10 Radio. It worked for me...
Or if you have a sense rom or the backup of your stock rom, give the guide a try...
Try this radio file. link, worked for me under cwm 2.5.0.7
lakshan_456 said:
No, that'll only be temporary, as with 2.5.
Get the PC49IMG.zip file for that recovery, put it on the root of the SD, reboot to bootloader, it'll scan and will ask to install, select yes, you're done.
First GPS fix will take some time, maybe from 2-10 mins.
I've only flashed the .20.10 Radio. It worked for me...
Or if you have a sense rom or the backup of your stock rom, give the guide a try...
Click to expand...
Click to collapse
My fault, there's something I should make clear.
The radios I've been talking about before have been installed on the first Wildfire, the one I said the GPS was working (and in the meanwhile it proved to be untrue as I discovered the GPS icon has never showed up before flashing the radio). This one Wildfire has CWM 2.5.0.1, installed with Unrevoked. The second Wildfire (which I'd like to use as my usual phone) was rooted with PC49IMG as Unrevoked wouldn't work with it and is running CWM 3.0.0.6, which I've reported in the first post.
For now, let's discard the CWM 3.0.0.6 phone.
It is on the CWM 2.5.0.1 phone where I've temporarily installed 2.5.0.7 and flashed the radios. Could it be relevant?
(maybe I'd better update the CWM anyway)
ChristianPe said:
Try this radio file. link, worked for me under cwm 2.5.0.7
Click to expand...
Click to collapse
Uhm, link is broken. My CWM 2.5.0.7 looks to be working properly anyway.
stick with 2.5.0.7 recovery and 20.10 radios, that worked for me using Navitel, as for file here.
Flashed Froyo 2.2.1 shipped ROM... and GPS didn't work on it either. Great.
I've restored my CM backup and found out all my link2SD linked apps to be screwed in return. Vanished. Link2SD says there's soooo much free space in that second partition... can't imagine when it's been formatted, but nevermind.
ChristianPe said:
stick with 2.5.0.7 recovery and 20.10 radios, that worked for me using Navitel, as for file here.
Click to expand...
Click to collapse
I've already got that radio version but tried to flash the one you've gently provided me, well, same as the other radios. Icon showing but no activity at all.
I give up.
Snakebar said:
Flashed Froyo 2.2.1 shipped ROM... and GPS didn't work on it either. Great.
I've restored my CM backup and found out all my link2SD linked apps to be screwed in return. Vanished. Link2SD says there's soooo much free space in that second partition... can't imagine when it's been formatted, but nevermind.
I've already got that radio version but tried to flash the one you've gently provided me, well, same as the other radios. Icon showing but no activity at all.
I give up.
Click to expand...
Click to collapse
where you at?, i might be a weather-related issue?
ChristianPe said:
where you at?, i might be a weather-related issue?
Click to expand...
Click to collapse
Unlikely, it's been some days I'm testing the GPS on the phone. But I shall test it away from home to be sure.
I'm from Naples, (IT) by the way.
Snakebar said:
It is on the CWM 2.5.0.1 phone where I've temporarily installed 2.5.0.7 and flashed the radios. Could it be relevant?
(maybe I'd better update the CWM anyway)
Click to expand...
Click to collapse
Not really sure if CWM matters or not, we use 2.5 to flash radios because the flashing script is different from currently used ones.
Ty upgrading anyway,
Are you sure it isn't a hardware fault. If GPS doesnt work in stock rom, it could possibly be a hardware issue...
lakshan_456 said:
Not really sure if CWM matters or not, we use 2.5 to flash radios because the flashing script is different from currently used ones.
Ty upgrading anyway,
Are you sure it isn't a hardware fault. If GPS doesnt work in stock rom, it could possibly be a hardware issue...
Click to expand...
Click to collapse
Too weird it happens on both devices, even if... well them both have had a nice dive in the sea but GPS used to work before flashing the new ROMs on each phone.
Sure there's something not correct in my procedure but can't find it out.
Snakebar said:
Too weird it happens on both devices, even if... well them both have had a nice dive in the sea but GPS used to work before flashing the new ROMs on each phone.
Sure there's something not correct in my procedure but can't find it out.
Click to expand...
Click to collapse
Well, I'm sorry mate. unless its a hardware fault or something I'm not in the know of, there are no more solutions I can think of.
Behold! He's thinking back.
It just looks like it's not able to track many satellites. Well, at least that's a relief.
Snakebar said:
Behold! He's thinking back.
It just looks like it's not able to track many satellites. Well, at least that's a relief.
Click to expand...
Click to collapse
Indeed it is, atleast it wasn't a hardware issue
Well done mate...
P.S. :- I'd recommend using 'GPS status and Toolbox' app which is much better than GPStest.
Sent from my HTC Wildfire using Tapatalk 2
lakshan_456 said:
P.S. :- I'd recommend using 'GPS status and Toolbox' app which is much better than GPStest.
Click to expand...
Click to collapse
Done!
~400s for first GPS lock... yeesh...
Snakebar said:
Done!
~400s for first GPS lock... yeesh...
Click to expand...
Click to collapse
Mission accomplished.
Cheers
Sent from my HTC Wildfire using Tapatalk 2