Develop Bugs

New clockwork recovery on rom manager

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.

[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

Rooted Desire with unrevoked, now things are messed up

Hello
I recently rooted my phone with unrevoked when things was starting to **** me up..yeah I know it sounds bad and it's that bad.
I rooted my phone and everything was fine until I came to the Clockworkmod screen after the startup. Below the meny I was able to read this.
Code:
ClockworkMod Recovery v2.5.0.7
E:Can't find MISC:
E:Can't mount CACHE:recovery/command
E:Can't find MISC:
E:Can't mount CACHE:recovery/log
E:Can't find MISC:
After some research I realise this is bad but I don't know how bad it is.
I can tell you guys I got the Bravo PTV(?)4 S-ON..no other mentions.
The phone works as it could but i'm concerned and want my phone to work properly..as it should. Does anyone here have a clue, whatsoever I have to do to make this work like a charm.
I red this http://forum.xda-developers.com/showthread.php?t=853583&page=7 thread and it seems like Amonra works as a replacement to clockworkmod but I don't know how to make this work. As far as I understand it I have to reflash my phone with Amonra, like Clockworkmod.

SD card. Probably you didnt make a gold card.
I hate to say it, but, even I went through this mess.
1. Make a "gold card" of your SD card. You can find this by google. You own a Desire. This is a fact of life.
2. After a gold card, do a root of your phone. I would also flash Clockworkmod recovery, personally I use ROM Manager for this
then and only then, can you think about flashing a ROM
after you do a nandbackup
and wipe all 3 cache memories
then flash through recovery, and not RM
God forbid there are 12 billion threads on this.
3. Drink a hell of a lotta beer, and call us next week.
4, Dont even think about special sd partitions yet
hell, if you cant do a simple flash, why do ya wanna do all the spectacular ****.......

This should help:
http://forum.xda-developers.com/showthread.php?t=839621

Moscow Desire said:
SD card. Probably you didnt make a gold card.
I hate to say it, but, even I went through this mess.
1. Make a "gold card" of your SD card. You can find this by google. You own a Desire. This is a fact of life.
2. After a gold card, do a root of your phone.
then and only then, can you think about flashing a ROM
God forbid there are 12 billion threads on this.
When you finish, you will have a super user icon in programs.
3. Drink a hell of a lotta beer, and call us next week.
Click to expand...
Click to collapse
Hahaha, thank you. No I havn't made any gold cards but I got a hell of a lotta beer in the refrigerator.
I already got the super user icon in programs?
Thank you stringer. I've been looking at this thread for a long time now but i'm concurned. There's no problem for me to flash the damn thing, absolutly not..the thing I don't know is how it would make any sense. If I install that program, it still doesn't remove the clockworkmod which drives me crazy.

stringer7 said:
This should help:
http://forum.xda-developers.com/showthread.php?t=839621
Click to expand...
Click to collapse
I tried that but unrevoked keeps saying "Failed to get root. Is your firmware to new?" after a 4-5 minutes. I have tried it two times know.

jenordfoto said:
I tried that but unrevoked keeps saying "Failed to get root. Is your firmware to new?" after a 4-5 minutes. I have tried it two times know.
Click to expand...
Click to collapse
Ok I did a little more reading. So you have root, and because you have pvt4, clockwork recovery isn't working properly and you need to replace it with Ra.
I think it would work to s-off your device (http://www.alpharev.nl) and then use fastboot to erase clockwork and flash Ra.
http://forum.xda-developers.com/showthread.php?t=619153
http://android.modaco.com/content/htc-hero-hero-modaco-com/302508/solved-using-adb-fastboot-help-to-flash-recovery/
I think that's the best plan, but I suggest researching it yourself too!

stringer7 said:
Ok I did a little more reading. So you have root, and because you have pvt4, clockwork recovery isn't working properly and you need to replace it with Ra.
I think it would work to s-off your device (http://www.alpharev.nl) and then use fastboot to erase clockwork and flash Ra.
http://forum.xda-developers.com/showthread.php?t=619153
http://android.modaco.com/content/htc-hero-hero-modaco-com/302508/solved-using-adb-fastboot-help-to-flash-recovery/
I think that's the best plan, but I suggest researching it yourself too!
Click to expand...
Click to collapse
Wow, thanks. Seem to be at bit risky to do that step..uh. I will do some research on my own. By the way, isn't it possible to unroot my device and then root it again?
Edit: And what happends if I install Clockworkmod via rom manager? Could it possible fix the problem? Does it really matter if it's flashed into my device or not. If I install that and enter recovery mode through the rom manager, could it possible be another working version of cwm?

jenordfoto said:
Wow, thanks. Seem to be at bit risky to do that step..uh. I will do some research on my own. By the way, isn't it possible to unroot my device and then root it again?
Edit: And what happends if I install Clockworkmod via rom manager? Could it possible fix the problem? Does it really matter if it's flashed into my device or not. If I install that and enter recovery mode through the rom manager, could it possible be another working version of cwm?
Click to expand...
Click to collapse
I had this exact same issue with my PV4 desire. You don't need to flash AlphaRev to get past the "firmware too new" error (I didn't). All I did was resetting android back to factory setting and unrevoked with Amonra recovery.

jenordfoto said:
Wow, thanks. Seem to be at bit risky to do that step..uh. I will do some research on my own. By the way, isn't it possible to unroot my device and then root it again?
Edit: And what happends if I install Clockworkmod via rom manager? Could it possible fix the problem? Does it really matter if it's flashed into my device or not. If I install that and enter recovery mode through the rom manager, could it possible be another working version of cwm?
Click to expand...
Click to collapse
No worries, s-off is about the same ad rooting, but yes you can unroot and root again ad the poster below suggests. Never thought of that!
The important bit is making sure to use the Ra recovery.

drSTRIFE said:
I had this exact same issue with my PV4 desire. You don't need to flash AlphaRev to get past the "firmware too new" error (I didn't). All I did was resetting android back to factory setting and unrevoked with Amonra recovery.
Click to expand...
Click to collapse
Good call, that's easier!

Same here. PVt-4. S-On.
I started with CWM, got the same error. Then, tried to root again with amon-ra, and it says firmware too new.
Solution: On the phone, Go to Settings-->Applications-->Manage Applications. Uninstall the Zysploit apk.
Run unrevoked again with amon-ra. All done.

drSTRIFE said:
I had this exact same issue with my PV4 desire. You don't need to flash AlphaRev to get past the "firmware too new" error (I didn't). All I did was resetting android back to factory setting and unrevoked with Amonra recovery.
Click to expand...
Click to collapse
The thing is, I can't factory reset my phone. I've tried but the phone dosn't reset itself, no..it ends up at clockwork mod after a reboot and when I reboot it from there, still everything is left untouched in my phone.
axbilly said:
Same here. PVt-4. S-On.
I started with CWM, got the same error. Then, tried to root again with amon-ra, and it says firmware too new.
Solution: On the phone, Go to Settings-->Applications-->Manage Applications. Uninstall the Zysploit apk.
Run unrevoked again with amon-ra. All done.
Click to expand...
Click to collapse
This sounds too easy, are you for real? I mean, that's your first post..not that convincing tho. Can someone else recommend this method, I don't have to hurry since my phone is working normal..just that messy thing with cwm.
Thanks for all help so far, I appriciate it.

Yes indeed. I was surprised myself.
Anyway, I took from this forum.
http://forum.xda-developers.com/showthread.php?t=1063879
It worked for me. I had the same problem. I started with CWM, I have SU in the app drawer, thinking I have root the phone. But when I try to flash with Redux ROM, I got the error. So, I didn't want to S-OFF, so I decided to go with Amon-RA. And got that error saying firmware too new.
Then I found that thread....it did well for me.
Good Luck.

I've just checked and can't see a zysploit.apk so don't think it will apply.
Easiest thing for you to do would be to s-off and flash a new recovery.
Sent from my HTC Desire using Tapatalk

Thank you axbilly, I will check that out. Many thanks.
mikep99 said:
I've just checked and can't see a zysploit.apk so don't think it will apply.
Easiest thing for you to do would be to s-off and flash a new recovery.
Sent from my HTC Desire using Tapatalk
Click to expand...
Click to collapse
You're wrong, when you're in applications..then press All Applications and scroll to the bottom, there it is.
Yeah, if this dosn't work I will try something else. I want to flash the new sense rom, otherwise I wouldn't care.

Fair enough, must be a PVT4 thing then.
Sent from my HTC Desire using Tapatalk

After I flash with amon-ra and flash with Redux, zysploit.apk is no longer there in my apps. Perhaps this is only used by CWM?

What do you mean? Don't you think my phone is rooted?
What is S-ON/OFF anyway, does it mind if I unchecked Disable phone security in unrevoked?
Sounds nice to me, I should give it a try and do as you say.
Remove the apk and retry flashing it with AmonRa.

My first try with unrevoked wtih CWM got the cache error that you've posted on first page.
I found in the forum if you're PVT-4 and erase size < 40000, CWM won't work and it will prompt you that cache error.
This forum suggest that to go with amon-ra...and so I did.
Can't comment on s-on or s-off, many thread on this already.
Anyhow, for me I wanted root because I want to install Redux. Since CWM didn't work for me, so I went with amon-ra.

IT WORKED. I don't know how to thank you axbilly, this was really easy compared to the other ways installing amonra. Cheers mate!
Thank you too stringer!

HTC G2 White Screen with Andromadus ROM 1.1.2

Hi All, let me start with a warning…
total Android n00b here, doing his first ROM flash on a newly rooted T-Mobile G2. I’ve read and searched a bit in the forum threads to see if I could solve this on my own, but I do need help.
VISION PVT SHIP S-OFF
HBOOT - 0.82.0000 (PC1010000)
MICROP - 0425
RADIO - 26.02.01.15_M2
eMMC - boot
Aug 20 2010, 16:51:01
This is from using the instructions in Strawmetal’s PDF guide to Downgrading from Gingerbread to Froyo and Root. I am working with a G2 phone that was set to Factory Reset before rooting, so there is no user data to backup or worry about.
1. I downloaded the Andromadus Mimicry 1.1.2 ROM image, and verified the md5 checksum on my sdcard using the AFV Legacy application. The Gapps image also was verified as well.
2. Using ROM Manager 5.0.0.8 from the Google Market, I ran Clockwork Recovery to install the Andromadus image. I left all settings on defaults and the installer ran fine.
3. When it restarted, I was left stuck at the white HTC screen for ages… the longest I left it was 20 mins. After that, I pulled the battery and restarted. Same white HTC screen.
4. I tried using Volume (+) key and Power On to get back to Clockwork Recovery, but the phone vibrated (buzzed) 3x times quickly, and the Power LED lamp pulsed an amber color. Again, yank battery, restart, same white HTC screen.
5. finally I decided to read more of the help for adb, and found the command “adb reboot-bootloader”. This let me get into the default Recovery mode, and it proceeded to find the PC10IMG.zip I still had on the sdcard from doing the Froyo downgrade. Recovery checked it out, ran it and restored the stock Froyo image and my phone did a proper restart. WHEW.
After that, I had to run adb to install the hboot recovery image file, and the busybox checksums were valid according to Strawmetal’s PDF instructions to get permanent root back after restoring the stock Froyo image.
I have done this process about 4 times, and am really good at typing inside adb now
But I’m lost…
-did I pick a ROM that doesn’t work with the G2? Other posters to the forum thread appear to be using the HTC Vision or G2.
-is ROM Manager not a good way to install a ROM?
-when I tried to get back into Recovery, what do the 3x buzzes/amber power LED mean?
-I never got to install the Gapps image; was I supposed to install that first, then the ROM image?
I imagine I did something wrong (duh!), but I can’t spot it. If someone can help me through this, I’d appreciate some advice very much.
thanks!

Rather than clockwork, use 4EXT recovery, much better for our device. ROM manager and clockwork have grown very iffy over the past year. Don't use rom manager to install a rom, download the zip yourself and manually install it in recovery.
Next you need to find the "superwipe+ext4.zip" floating around here, it is indispensable for FULLY wiping your phone when switching roms.
Mimicry works fine on the G2, in fact everything (except a few sense roms that need a Desire Z hboot) in the development section runs fine on the G2.
So....get the ROM, GApps for that ROM, the Superwipe zip (you will flash this right before you begin flashing the rom) on your SD card and make sure you are using 4EXT recovery (find the link in the dev section).
Make sure before you do ANYTHING you make a Nandroid backup (using your recovery).

Your issue is actually addressed in the Mimicry OP, please read it first. That said, the problem is almost certainly because you're coming from GB without a full wipe. You can use 4ext to repartiton/wipe all, or you can use superwipe+ext4 as mentioned by Nospin.
Sent from my HTC Vision using xda premium

Hi Nospin,
Thank you very much for your suggestions!
I will revise my root and remove Clockwork, and switch to 4EXT instead.
I appreciate the idea of "superwipe"; I will look for that as well today.
If I understand everything right...
-replace CWM with 4EXT
-place superwipe.zip, Gapps.zip and the Mimicry ROM.zip on the top level of the sdcard first.
-reboot the phone and run 4EXT recovery
-select superwipe to run first, then the ROM and then Gapps
-then restart the phone
When I used CWM before to install the ROM, it rebooted on its own before I could install Gapps. Will 4EXT let me do each install right after each other or do I have to return to 4EXT for each separate install?
regards,
motionmonk
Nospin said:
Rather than clockwork, use 4EXT recovery, much better for our device. ROM manager and clockwork have grown very iffy over the past year. Don't use rom manager to install a rom, download the zip yourself and manually install it in recovery.
Next you need to find the "superwipe+ext4.zip" floating around here, it is indispensable for FULLY wiping your phone when switching roms.
Mimicry works fine on the G2, in fact everything (except a few sense roms that need a Desire Z hboot) in the development section runs fine on the G2.
So....get the ROM, GApps for that ROM, the Superwipe zip (you will flash this right before you begin flashing the rom) on your SD card and make sure you are using 4EXT recovery (find the link in the dev section).
Make sure before you do ANYTHING you make a Nandroid backup (using your recovery).
Click to expand...
Click to collapse

Hi blk_jack,
I went back to the Mimicry page and re-read the FAQ section.
I think what I got out of it the first time was that if the ROM flash failed, it could be a corrupt ROM image. I will definitely use 4EXT to repartition before I try again with a ROM flash.
I guess I am still getting used to the terms for everything; can 4EXT do the nandroid backup? or is there a better process for setting that up?
thank you!
motionmonk
blk_jack said:
Your issue is actually addressed in the Mimicry OP, please read it first. That said, the problem is almost certainly because you're coming from GB without a full wipe. You can use 4ext to repartiton/wipe all, or you can use superwipe+ext4 as mentioned by Nospin.
Sent from my HTC Vision using xda premium
Click to expand...
Click to collapse

Yes, you should be able to flash the rom and then GApps without rebooting. Give me a few and I will send you a PM with a few links....

Shot you a PM.

Thanks! I'll check it out :good:
Nospin said:
Shot you a PM.
Click to expand...
Click to collapse

Update-not working
Ok...
I re-flashed back to stock Froyo, and did a permanent root.
Installed 4ext Recovery (instead of Clockwork), and got a copy of SuperwipeG2+ext4;
I copied new checksum'd copies of Mimicry 1.1.2 ROM and GApps to my sdcard.
Booted into 4ext Recovery and installed from .zip the SuperwipeG2+ext4 file.
System, data and cache are all converted to ext4 partitions.
Wiped the system and data and cache partitions.
Installed from inside Recovery the Mimicry ROM and then the GApps archives.
No errors reported.
Upon reboot, I still get the white HTC screen. UGH.
I've left it on in that state for 30 mins... I had to yank the battery after that in shame...
I have tried to make sure that I read up on background steps, and I feel I do understand the overall process, but something is still getting in the way. I am doing this as I mentioned in an earlier post on a factory reset G2 with a clean erased SD card (has the stock Froyo image, Andromadus Mimicry ROM and GApps only). There is no SIM card installed either, wifi is off (to avoid OTA upgrade requests).
Are there other things I can try, or info I can supply that would help? I think I'm so close to getting this done... I must be overlooking something obvious.

I run that by rom along with Cm9 beta..... Try adding that to your boot process. Just Cm9 beta..... Other than version of crash.... That's just what I have experienced
Sent from my HTC Vision using xda premium

Hi amogil,
Just to be sure I understand, are you saying you are swapping between Andromadus and CM9 beta on your phone?
Did you flash CM9 first? and then Andromadus?
or just carrying the CM9 beta image and running Andromadus?
Sorry, I'm all sorts of confused here lol
thanks
amogil said:
I run that by rom along with Cm9 beta..... Try adding that to your boot process. Just Cm9 beta..... Other than version of crash.... That's just what I have experienced
Sent from my HTC Vision using xda premium
Click to expand...
Click to collapse

Ugh....it's frustrating isn't it?
Can you boot into any other rom? For example if you downloaded CM7.2? If you don't have any problems we can eliminate some possibilities.....
I had a similar problem booting into Mimicry my first time, in that I could get past the white HTC screen but after that my screen would just go black. After a couple frustrating hours what ended up working for me was downloading the older version (1.1.1 I think?) and that booted up fine . Then after letting that boot I went back into recovery and flashed 1.1.2 without wiping (I might have wiped cache and dalvik...). Everything worked great after that. Not the same problem as you, but similar.....

It's definitely a thought, and I believe that's what amogil is telling me too...
Ya, I can try a different ROM and report back.
I guess I should go back to stock Froyo and then start from CM7.2, and if that boots, try Mimicry again?
-from the Andromadus FAQ, it says it if a different ROM is based on ICS9, you shouldn't have to wipe. But with CM7, I'd have to wipe the Dalvik cache, yes?
-since CM7 is obviously not based on ICS9, would being able to launch into that show some details I can't see at present? Just was curious.
Or, do you think it better to go stock Froyo and then the older Mimicry ROM?
Either way, I'll make sure that I use the Superwipe to set things to ext4 first.
thanks guys for the ideas,
motionmonk
Nospin said:
Ugh....it's frustrating isn't it?
Can you boot into any other rom? For example if you downloaded CM7.2? If you don't have any problems we can eliminate some possibilities.....
I had a similar problem booting into Mimicry my first time, in that I could get past the white HTC screen but after that my screen would just go black. After a couple frustrating hours what ended up working for me was downloading the older version (1.1.1 I think?) and that booted up fine . Then after letting that boot I went back into recovery and flashed 1.1.2 without wiping (I might have wiped cache and dalvik...). Everything worked great after that. Not the same problem as you, but similar.....
Click to expand...
Click to collapse

The boot.img should be the issue for a rom to not boot from the. Htc whitescreen. My guess is that you have a false s-off.
Sent from my HTC Vision using xda premium

SUCCESS!
Woohoo!
It works!
Since I had an ICS9 ROM already in place and was planning to wipe back to stock anyways, I tried flashing the older Andromadus 1.1.0 ROM.
What a surprise and treat to see the startup animation!
After poking around for an hour inside it, I then tried Recovery to reflash to the newest 1.1.2 ROM.
YAY! It works!
OMG, having a new ROM is like having a new phone-- there are so many improvements to the UI and it's quick and speedy versus GB. Dang, I'm happy now :victory:
Observations:
1. I did notice that inside Recovery, my touchscreen was barely functional when I tried to update from 1.1.0 up to 1.1.2-- I had to use the Volume +/- and the d-pad button to make selections. After the flash, the touchscreen is as responsive as ever.
2. it's got me thinking, that there must be a setting that is expected in the v1.1.2 ROM that the v1.1.0 ROM installed. Or could something else be the issue? I mean absolutely no disrespect to the developers... but on the technical side, I'm just curious what possibilities exist that might lead to this situation.
3. backup question... when I use MyBackup Pro, I know I can make an archive of the apps I've installed, and an archive of the data (documents, music, settings). Is a nandroid backup different from that? when I see the backup/restore options inside of 4ext Recovery, what are those doing that's different from what I get from MyBackup Pro?
thanks for all the help and encouragement. I have a new ROM installed! :good:

strawmetal said:
The boot.img should be the issue for a rom to not boot from the. Htc whitescreen. My guess is that you have a false s-off.
Sent from my HTC Vision using xda premium
Click to expand...
Click to collapse
Oooh, a possibility. We will see if he can boot a different rom.
Whenever you switch roms (even if they are using the same Android version as a base) I suggest a full wipe. (Wipe all user data + Dalvik Cache + Cache, or just flash the superwipe zip). When upgrading the rom you are currently on (say upgrading CM Nightlies or going from Mimicry 1.1.1 to 1.1.2) you only need to really wipe cache and dalvik cache. Unless the dev states otherwise of course.

Hi strawmetal,
It turns out that I did have s-off after all...
1. after one of the many attempts to flash the ROM image and restoring back to stock Froyo, I said that "I'm gonna start this entire process over to be sure." So I get stuck using the fre3vo tool for about 30 minutes, rebooting and trying different address ranges to find the exploit.
Never found one... oh no, what did I do to the phone now??
-then it hit me; if it can't find an exploit... then it must already been used!
2. also, I did check each time I was in bootloader that my S-OFF was there and the radio and hboot were not changing versions.
3. Hehe, and the best indication was... being able to boot up finally!
I also have your Strawmetal.CM.V6.zip on my sdcard; if the downflash (?) to the Andromadus older ROM didn't work, yours was the CM7 image I wanted to try. If it's ok, I think I want to play around inside CM9 for a bit and then try yours out after that. I don't want to overwhelm my poor brain!
thank you for your suggestion... that definitely would be something to check as well.
strawmetal said:
The boot.img should be the issue for a rom to not boot from the. Htc whitescreen. My guess is that you have a false s-off.
Sent from my HTC Vision using xda premium
Click to expand...
Click to collapse

Thank You All!
A big shout out to:
Nospin
blk_jack
amogil
strawmetal
for taking the time out to help a total n00b stumble through his first ROM flash.
I really appreciate the points you guys made, and the help provided.
Thank you!
I hope that one day I can help someone else out with a problem and pass the kindness forward.
Yay! I have a working ROM!
motionmonk

motionmonk said:
Hi strawmetal,
It turns out that I did have s-off after all...
1. after one of the many attempts to flash the ROM image and restoring back to stock Froyo, I said that "I'm gonna start this entire process over to be sure." So I get stuck using the fre3vo tool for about 30 minutes, rebooting and trying different address ranges to find the exploit.
Never found one... oh no, what did I do to the phone now??
-then it hit me; if it can't find an exploit... then it must already been used!
2. also, I did check each time I was in bootloader that my S-OFF was there and the radio and hboot were not changing versions.
3. Hehe, and the best indication was... being able to boot up finally!
I also have your Strawmetal.CM.V6.zip on my sdcard; if the downflash (?) to the Andromadus older ROM didn't work, yours was the CM7 image I wanted to try. If it's ok, I think I want to play around inside CM9 for a bit and then try yours out after that. I don't want to overwhelm my poor brain!
thank you for your suggestion... that definitely would be something to check as well.
Click to expand...
Click to collapse
The bootloader can show a false s-off. I've personally experienced this. By the time "HTCDev bootloader unlock" came out i was already rooted. But as curious as I was I decided to try it out. Flashed an RUU ( my my why would I do that ) Got back s-on( guess this was false too) then I used HTCDev method to prove i'm a total noob. Then i relocked it using Nipqer's guide and followed setherio's method again. I was able to use the stock froyo, but no other rom would boot( false s-off being the culprit ). This time I ran to #g2root on freenode. Nipqer saved me.

WOW. i just realized there is SO MUCH I need to catch up on!
I'll have to look up some of these guides later today... but the RUU is the ROM upgrade, right?
Did you ever find a reason why you got the false S-OFF flag? It's clear that the way I was looking at the failed fre3vo exploit as proof of S-OFF isn't always going to be true... but how would you separate a false S-OFF flag from lets say a wrong hboot image?
BTW, your PDF on downgrading and rooting the G2 was a godsend. Very very helpful and clear.
One of the reasons why I took so long to try rooting was that I was confused by the different methods and the replies of X not working, Y is a better way... going through your guide and the info here on xda cleared alot of things up. :good:
strawmetal said:
The bootloader can show a false s-off. I've personally experienced this. By the time "HTCDev bootloader unlock" came out i was already rooted. But as curious as I was I decided to try it out. Flashed an RUU ( my my why would I do that ) Got back s-on( guess this was false too) then I used HTCDev method to prove i'm a total noob. Then i relocked it using Nipqer's guide and followed setherio's method again. I was able to use the stock froyo, but no other rom would boot( false s-off being the culprit ). This time I ran to #g2root on freenode. Nipqer saved me.
Click to expand...
Click to collapse

Unable to flash radio

Hi guys,
I have a wildfire with hboot-6.01.1002 S-off and radio 3.35.20.10.
I had the gps bug, so I tried all the ways to fix it but without success. So I tried to reflash radio and just trying to flash older versions I found out that the radio doesn't get flashed.
I tried laptop method too but with win8 is impossible for my wildfire to get recognized and all the tricks seen on internet or on this forum don't work.
Ooops I forgot to say that from RomManager I downgrade to cwm 2.x, then I reboot the phone, but in recovery I see again cwm 5.x, so everytime I install from there the 2.x version and I flash radio, but at system reboot I find 3.35.20.10 radio again.
Could you help me pls?
ps. sorry for my bad english.

sangkavr said:
Ooops I forgot to say that from RomManager I downgrade to cwm 2.x, then I reboot the phone, but in recovery I see again cwm 5.x, so everytime I install from there the 2.x version and I flash radio, but at system reboot I find 3.35.20.10 radio again.
Click to expand...
Click to collapse
You can try to use a temporary 2.x flashable cwm zip file and flash it after a cwm recovery reboot: I have cwm 6 installed and reflashing the radio in this way I usually fix GPS and WiFi problems (I have to do it once or twice every time after I install a new ROM).
Sent from my HTC Wildfire using xda app-developers app

Hi, could you explain me the procedure?
Where do I find a temporary cwm?
--- do you mean install a cwm 2.x in recovery mode? It doesn't work, I wrote it in the first post too.

mate, you don't have to flash a new radio to fix the GPS issue.
Here's what I do,
#Turn GPS on in your current ROM, and wait for a stable location fix,
#while GPS is still on, power off the phone.
#Now boot into recovery and flash your new ROM
#now after flashing and booting into your new ROM you'll be able to use GPS again.
You'll have to do this everytime you flash a new gingerbread ROM or above..
if your current ROM doesn't have working GPS, just flash Sense ROM, the GPS will work. then do as I said.
I always though flashing radio's are a little risky, as this is a risk free method, I think everyone should use this instead..
cheers ...

upon latesxt
Every time I try a sense rom at installing point I lose screen, just some colored strips, do you remember 80 cabinet game before loading? if yes ... those ones
But that's really strange that i'm not able to flash radio anyway.

sangkavr said:
Every time I try a sense rom at installing point I lose screen, just some colored strips, do you remember 80 cabinet game before loading? if yes ... those ones
But that's really strange that i'm not able to flash radio anyway.
Click to expand...
Click to collapse
I'm guessing you're referring to RemPuzzle ROM which has Aroma installer.
yea Aroma installer does that on cwm5.
only way to fix that is to revert to CWM4 permanent ( untill you decide to go back to a higher cwm version.)
anyway try another sense ROM, like DK's custom ROM or similar ..
cheers..

I was just reading about DK roms, it has to be installed using a temporary cwm.
Just a curiosity: all newer roms are cyano based?

sangkavr said:
I was just reading about DK roms, it has to be installed using a temporary cwm.
Just a curiosity: all newer roms are cyano based?
Click to expand...
Click to collapse
Yes, most gingerbread and up roms are usually bases on CM.
About the temporary cwm. Just flash it as a normal zip and you'd get temporary cwm2.5 , flash DK with that, after reboot you'll be back on your current cwm version.
Sent from my HTC Wildfire using Tapatalk 2

Just a thing, I flash a sense rom, after that I wait gps fix and then I install cyano rom. But without wipe or format?
I ask that cause before I use Mtd partition procedure to have more free space, and without any format and wipe I can't do that.

sangkavr said:
Just a thing, I flash a sense rom, after that I wait gps fix and then I install cyano rom. But without wipe or format?
I ask that cause before I use Mtd partition procedure to have more free space, and without any format and wipe I can't do that.
Click to expand...
Click to collapse
No no... just wipe everything. And also the Dalvik cache. Then install the new ROM. After rebooting to your new ROM GPS would work.
Sent from my HTC Wildfire using Tapatalk 2

Ehm .. dkmod roms failed to install cause "installation aborted", 4.6.2 and 4.7.
I tried joyOs but gps doesn't start. With Rempuzzle I have screen problems.
It seems I have to forget gps.

Flashing a radio requires at least 30mb on cache, so make sure you aren't using a custom mtd setup.
If its not the case, try flashing a 2.x permanent recovery and then flash the radio.

sangkavr said:
Ehm .. dkmod roms failed to install cause "installation aborted", 4.6.2 and 4.7.
I tried joyOs but gps doesn't start. With Rempuzzle I have screen problems.
It seems I have to forget gps.
Click to expand...
Click to collapse
you got installation aborted msg with CWM 2?
Mate, then try CM6. its a froyo ROM. and can be flashed with any CWM version. and as I remember GPS works without any issues. get it from http://get.cm/?device=buzz
then try again my steps.
hope it'll work. Good luck
cheers..

Thanks, cyano6 works.

sangkavr said:
Thanks, cyano6 works.
Click to expand...
Click to collapse
I'm glad you got it sorted
Cheers...

But now jellybread doesn't boot
arghhhhhh

sangkavr said:
But now jellybread doesn't boot
arghhhhhh
Click to expand...
Click to collapse
are you using custom mtd partitions?
if yes, there is an additional zip file to flash after flashing a new ROM.

I tried with higher mtd values but nothing, without mtd no problem, but without mtd this phone is useless for me.

sangkavr said:
I tried with higher mtd values but nothing, without mtd no problem, but without mtd this phone is useless for me.
Click to expand...
Click to collapse
If you have followed all the steps.correctly for custom mtd partitioning, it should work.
If it still fails, try link2sd, its an app. It moves apps to a separate partion in SDcard and saves internal storage.
But you have to partion your SDcard for that.
I suggest you should recheck if you followed all the steps correctly for mtd partioning. And remember to flash the bravo-boot.zip ( I don't remember the exact name) after flashing a ROM..
Sent from my HTC Wildfire using Tapatalk 2

I'm sure I followed all the steps, but I'm gonna try again.
Further jellybread is now on (without mtd) but without gapps too and they're integrated in the rom.
Android is trying to make me crazy