Develop Bugs

Newest fresh radios/kernals and setting up Amon Ra Flash

Hello all,
I followed the guide to root my phone that was titled "Idiot proof root quide" that can be found on the androidforums. I then installed fresh 0.3 and I've been running that for a while and had no desire to flash the new fresh roms. Well, now that fresh has released a ROM with froyo at its base I've decided to make the jump.
Yesterday I downloaded and installed the latest rom from fresh (3.1.0.1) but I was unaware that there were new radio updates and kernals to install. This is where I'm running into trouble. For some reason when I have 3.1.0.1 installed my phone wont stay connected to the computer. Once I plug the USB cord in it will ask me if I wan't to charge, disk drive, etc but then 2 seconds later it will disconnect. I've gone back to fresh 0.3 and it works fine.
SO, my questions are:
1. How do I install the latest radio for fresh (please help me with links, I've looked but have become easily frustrated)
2. How do I install the latest kernal with Amon Ra flash (it is my understanding that you need this to install the newest radio/kernal). I understand I need fastbook and the android SDK but I don't think I'm setting these two applications up correctly when I download them.
If you can direct me to any threads that will assist me I will greatly appreciate it.
Thanks!

another way you can try is putting the radios on before you flash the rom to fresh3. I would flash using AMon Ra just because there have been reports of clockwork not fully clearing cache/dalvik. The best way to do this in my opinion is if you have rom manager installed at the bottom you will find flash alternate recovery, use that then try clearing wiping everything and reflashing. If you put the radios on your sd card first jsut boot into froyo once then power down flash radio boot, power down flash wimax. boot.
then try and see if you usb is still having problems. If it is let us know.

Download the radios and kernels you want with your phone, then reboot into recovery. All of them flash like ROMs, just select the zip you want and flash it. Just don't wipe first.
I think the order would be kernel first, then radio, then WiMax if necessary. Always reboot at least between radio and WiMax, maybe after kernel as well.

RyboCollier said:
Hello all,
I followed the guide to root my phone that was titled "Idiot proof root quide" that can be found on the androidforums. I then installed fresh 0.3 and I've been running that for a while and had no desire to flash the new fresh roms. Well, now that fresh has released a ROM with froyo at its base I've decided to make the jump.
Yesterday I downloaded and installed the latest rom from fresh (3.1.0.1) but I was unaware that there were new radio updates and kernals to install. This is where I'm running into trouble. For some reason when I have 3.1.0.1 installed my phone wont stay connected to the computer. Once I plug the USB cord in it will ask me if I wan't to charge, disk drive, etc but then 2 seconds later it will disconnect so I went back to fresh 0.3 and it works fine.
SO, my questions are:
1. How do I install the latest radio for fresh (please help me with links, I've looked but have become easily frustrated)
2. How do I install the latest kernal with Amon Ra flash (it is my understanding that you need this to install the newest radio/kernal).
If you can direct me to any threads that will assist me I will greatly appreciate it.
Thanks!
Click to expand...
Click to collapse
New Radio: http://geekfor.me/evo/radio/baseband-215000728/
New Wimax Radio: http://geekfor.me/evo/radio/wimax-26023r01/
No need a custom Kernel for now, the ROM has its own, if you want a Kernel anyways you can flash Netarchy's Revision 3.7.6c - Froyoized but it has a side effects with the camera pixels!

SilverZero said:
Download the radios and kernels you want with your phone, then reboot into recovery. All of them flash like ROMs, just select the zip you want and flash it. Just don't wipe first.
I think the order would be kernel first, then radio, then WiMax if necessary. Always reboot at least between radio and WiMax, maybe after kernel as well.
Click to expand...
Click to collapse
3 out of 5? lol

Wow, thank you for the quick responses guys/gals! So it seems that I was making this more difficult than it needs to be.
Summary of what I need to do:
1. Flash new kernel if I choose to but each ROM comes with a custom kernel.
2. Flash new radio update.
3. Flash Wimax update.
4. Flash fresh 3.1.0.1
Now, I hope this also solves my USB issue that I'm having which only occurs when I have 3.1.0.1 flashed. I'm going to take omegasun18's advice and see if that will correct my issue.

RyboCollier said:
Wow, thank you for the quick responses guys/gals! So it seems that I was making this more difficult than it needs to be.
Summary of what I need to do:
1. Flash new kernel if I choose to but each ROM comes with a custom kernel.
2. Flash new radio update.
3. Flash Wimax update.
4. Flash fresh 3.1.0.1
Now, I hope this also solves my USB issue that I'm having which only occurs when I have 3.1.0.1 flashed. I'm going to take omegasun18's advice and see if that will correct my issue.
Click to expand...
Click to collapse
well i would do it ......
Fresh rom + radio, the reboot, wimax, then reboot again, then kernel, that's waht i did and have everything working no 30fps cap, wi fi tether and all the stuff (remember about the camera issue)
*edit* remember something, you have to left the custom kernel to the end, because as i told you before the rom has its own kernel and will overwrite any other you installed previously

So leave the kernel to the end? Does that kernel you recommended remove the 30fps cap?

yep make sure if you do a kernal you do it AFTER the rom. the radios shouldnt matteer since msot roms dont acctually change the radios when flashed. but i normaly start with the rom and work my way up but otherwise you have it.

RyboCollier said:
So leave the kernel to the end? Does that kernel you recommended remove the 30fps cap?
Click to expand...
Click to collapse
Well..................

I keep running into an issue where my contacts keep crashing when I open the people application or try to send a text message. Any idea as to why this might be happening?

RyboCollier said:
I keep running into an issue where my contacts keep crashing when I open the people application or try to send a text message. Any idea as to why this might be happening?
Click to expand...
Click to collapse
What rom? did you wipe?

Uhhhh Ohhhh... EVO repeatedly rebooting

Now, I thought, "hey, I'm not a novice with flashing ROM images, nor am I a *nix or system notice..." So, I decided to cook a ROM using the Online ROM kitchen: http://evo.feeder.pk/
I had run unrevoked3 + unrevoked forever, so I had clockwork recovery.
So, I copied the zipped ROM generated off the online ROM kitchen to the sdcard and then via clockwork installed /sdcard/update.zip (the ROM).
So, everything installed okay, then upon reboot, it seems to go into a reboot loop.
Lucky for me I performed a nandroid backup before installing the newly built ROM, and I'm in them middle of performing a nandroid restore; which I hope will resolve the problem.
1) Will the nandroid restore actually restore my entire phone back to how it was previously?
2) How do I actually install another ROM properly?
These are pretty n00b questions, but any help is appreciated.
Thanks,
Matt

branded said:
Now, I thought, "hey, I'm not a novice with flashing ROM images, nor am I a *nix or system notice..." So, I decided to cook a ROM using the Online ROM kitchen: http://evo.feeder.pk/
I had run unrevoked3 + unrevoked forever, so I had clockwork recovery.
So, I copied the zipped ROM generated off the online ROM kitchen to the sdcard and then via clockwork installed /sdcard/update.zip (the ROM).
So, everything installed okay, then upon reboot, it seems to go into a reboot loop.
Lucky for me I performed a nandroid backup before installing the newly built ROM, and I'm in them middle of performing a nandroid restore; which I hope will resolve the problem.
1) Will the nandroid restore actually restore my entire phone back to how it was previously?
2) How do I actually install another ROM properly?
These are pretty n00b questions, but any help is appreciated.
Thanks,
Matt
Click to expand...
Click to collapse
1) Its supposed to...
2) From what it sounds like, you installed everything okay, just with a bad ROM image. Installing any of the other ROMs already posted should relieve you of your bootloops (as should the nandroid). Unless you try overclocking, which some folks experience bootloops when overclocked over 1.15.

nol3n said:
1) Its supposed to...
2) From what it sounds like, you installed everything okay, just with a bad ROM image. Installing any of the other ROMs already posted should relieve you of your bootloops (as should the nandroid). Unless you try overclocking, which some folks experience bootloops when overclocked over 1.15.
Click to expand...
Click to collapse
Thank you sir. nandroid obviously did restore everything back to normal (wasn't sure to what extent nandroid backed up the device, but it looks like every single thing was backed up).
As for a ROM, I really just want the stock froyo ROM, but rooted... Do you have any suggestions? I can't go OTA since I have clockwork recovery.
Thanks,
Matt

branded said:
Thank you sir. nandroid obviously did restore everything back to normal (wasn't sure to what extent nandroid backed up the device, but it looks like every single thing was backed up).
As for a ROM, I really just want the stock froyo ROM, but rooted... Do you have any suggestions? I can't go OTA since I have clockwork recovery.
Thanks,
Matt
Click to expand...
Click to collapse
I have flashed most of the ROMs here, but I have mostly been using CM6 (Cyanogenmod 6) since it came out. I did try Baked Snack, which is a very nice ROM with a beautiful theme, but it is Sense based and if by any chance you wanted to use a Wiimote for emulators, you cant. It is based off the HTC bluetooth stack, CM6 is not. Its kinda nice to get nightly (experimental) updates to flash if you want to also.
Its all a matter of personal preference, but my BEST results have been with CM6 - benchmark, features, and otherwise.
*E* You also may want to consider posting something like this in the Q&A forum next time...

Uhhhh Ohhhh wrong section

nol3n said:
I have flashed most of the ROMs here, but I have mostly been using CM6 (Cyanogenmod 6) since it came out. I did try Baked Snack, which is a very nice ROM with a beautiful theme, but it is Sense based and if by any chance you wanted to use a Wiimote for emulators, you cant. It is based off the HTC bluetooth stack, CM6 is not. Its kinda nice to get nightly (experimental) updates to flash if you want to also.
Its all a matter of personal preference, but my BEST results have been with CM6 - benchmark, features, and otherwise.
Click to expand...
Click to collapse
Very cool. I'll take a look but I really want Sense, which I'm not sure if CM6 has. Thanks.
Sporkman said:
Uhhhh Ohhhh wrong section
Click to expand...
Click to collapse
Just flag the post and request a mod move it. There's really little reason to post a reply. It seemed like the best place given the descriptions of all the EVO sub-forums.

branded said:
Thank you sir. nandroid obviously did restore everything back to normal (wasn't sure to what extent nandroid backed up the device, but it looks like every single thing was backed up).
As for a ROM, I really just want the stock froyo ROM, but rooted... Do you have any suggestions? I can't go OTA since I have clockwork recovery.
Thanks,
Matt
Click to expand...
Click to collapse
Just get netarchys rooted stock rom and you should be ok... just make sure you get the rooted version

Next time do a wipe of your davik cache before installing any rom

playya said:
Just get netarchys rooted stock rom and you should be ok... just make sure you get the rooted version
Click to expand...
Click to collapse
Thanks playya...
http://forum.xda-developers.com/showthread.php?t=740520
http://forum.xda-developers.com/showthread.php?t=719763
evolol said:
Next time do a wipe of your davik cache before installing any rom
Click to expand...
Click to collapse
http://forum.androidcentral.com/htc...-clockwork-clears-dalvik-cache-just-fine.html
http://forum.xda-developers.com/showpost.php?p=4535156&postcount=4
http://androidforums.com/all-things-root-eris/76110-what-dalvik-cache.html#post710236
And thank you both for ignoring that racist bag of donkey twats that responded earlier.

branded said:
Thanks playya... do you have a link?
http://forum.xda-developers.com/showpost.php?p=4535156&postcount=4
http://androidforums.com/all-things-root-eris/76110-what-dalvik-cache.html#post710236
And thank you both for ignoring that racist bag of donkey twats that responded earlier.
Click to expand...
Click to collapse
no problem quote from last response at that forum
Quote:
Originally Posted by Tamasabian View Post
Ok. So I should just clear it when I do a data wipe to flash a new rom? Will it be a problem if I just do a data wipe and flash a new rom without doing the dalvik cache?
i have had issues when i dont clear the dalvik cache, but never had issues when i do. just cear it, nothing bad will happen and only good can come of it

Sporkman said:
Uhhhh Ohhhh wrong section
Click to expand...
Click to collapse
agreed, theres a section for Q&A

evolol said:
no problem quote from last response at that forum
Quote:
Originally Posted by Tamasabian View Post
Ok. So I should just clear it when I do a data wipe to flash a new rom? Will it be a problem if I just do a data wipe and flash a new rom without doing the dalvik cache?
i have had issues when i dont clear the dalvik cache, but never had issues when i do. just cear it, nothing bad will happen and only good can come of it
Click to expand...
Click to collapse
Cool thank you I will do that and attempt to reflash this ROM that I cooked.
Rocklee99 said:
agreed, theres a section for Q&A
Click to expand...
Click to collapse
Flag the thread and request a mod move it. Glad that you all really want to up your post count so badly, shows real dedication to the forums cleanliness.

Your welcome...now show your dedication to this forum by following instructions & quit cluttering the development section with basic Questions

Not to delf: seems like I fall under a ClockworkRecovery user who's dalvik cache doesn't actually clear. (http://forum.xda-developers.com/showthread.php?t=719763) Kick ass!

I have the same problem as you!!!! I posted it in the wrong forum though so I'll briefly psot my problem and maybe someone can help me. I was trying to update my radio to the latest radio and it worked. I then realized I didn't have a 4g signal and the mod I was using supports 4g. So I tried updating to the latest wimax and then my phone started rebooting. After it boots android it reboots after a bout a minute or 2.
I FIXED it with a nandroid restore which had my 2.1-1 back up which I made during the idiot proof guide. So thinking that I can always use that backup as a restore I tried re-installing the radios because I don't see how they could not work on my phone and thought maybe I had a corrupt file, but voila my phone started rebooting again, but this time nandroid restore tells me to fix it via adb restore, BUT my usb isn't working either. So I'm stuck and have no idea on how to get this thing to load my restore. Any help would be appreciated.

I didn't read you're reply. But after installing RA, I think I'll be alright...
Here's the deal from start to finish...
download and install the android SDK
install all the necessary drivers
restart in recovery mode ( adb restart recovery or hold volume down when powering on the device)
use adb shell to access the shell while the device is in recovery
1) install RA recovery using adb method (http://forum.xda-developers.com/showthread.php?t=705026) This may or may not be okay with or without running unrevoked first... not sure if flash_image was placed on the device by unrevoked.
2) reboot into recovery
3) flush dalvik cache via RA recovery.
4) flush cache via RA recovery.
5) use adb push to copy a downloaded ROM zip to /sdcard/update.zip (using RA recovery to mount the /sdcard/ partition)
- I've downloaded http://forum.xda-developers.com/showthread.php?p=7512117
6) Install update.zip from sdcard in RA recovery
- After booting into the new ROM one time, I allowed it to start and configured... then performed 3,4,5 against flashing a new kernel: http://forum.xda-developers.com/showthread.php?t=719763
And that should be that. I'm currently downloading the ROM, so I don't know how it'll be.

[Q] Back to Gingerbread after going ICS?

If this has been asked before then please forgive me...
I can not go back to any backup I had of CM7 or Gingerbread Sense ROM since upgrading to some Alpha ICS roms. I've tried wiping everything & started from scratch on these roms but I always get stuck at "failed to write boot partition from /tmp/boot.img" It doesn't matter what Gingerbread ROM I choose with the exception of MIUI rom (don't know why). I thought maybe I could use that as a stepping stone to go back from there but nogo. I've used RA's recovery & CWM with no success. Any ideas?

davidnjessicacruz said:
If this has been asked before then please forgive me...
I can not go back to any backup I had of CM7 or Gingerbread Sense ROM since upgrading to some Alpha ICS roms. I've tried wiping everything & started from scratch on these roms but I always get stuck at "failed to write boot partition from /tmp/boot.img" It doesn't matter what Gingerbread ROM I choose with the exception of MIUI rom (don't know why). I thought maybe I could use that as a stepping stone to go back from there but nogo. I've used RA's recovery & CWM with no success. Any ideas?
Click to expand...
Click to collapse
I would recommend tracking down calkulins format zip for the evo

1brainsurgeon said:
I would recommend tracking down calkulins format zip for the evo
Click to expand...
Click to collapse
Yeah... tried that already... Didn't fix it...

davidnjessicacruz said:
If this has been asked before then please forgive me...
I can not go back to any backup I had of CM7 or Gingerbread Sense ROM since upgrading to some Alpha ICS roms. I've tried wiping everything & started from scratch on these roms but I always get stuck at "failed to write boot partition from /tmp/boot.img" It doesn't matter what Gingerbread ROM I choose with the exception of MIUI rom (don't know why). I thought maybe I could use that as a stepping stone to go back from there but nogo. I've used RA's recovery & CWM with no success. Any ideas?
Click to expand...
Click to collapse
I can say with certainty that I don't have this problem. I've flashed every ROM from here to Timbuktu, AOKP, Deck's, Evervolv, and have had no problem restoring a nandroid of, or flashing MikG, Mik3D, MikRunny, The Express, or any other ROM I may have forgotten.
That boot partition error doesn't sound good, though. What HBOOT version do you use?

Captain_Throwback said:
I can say with certainty that I don't have this problem. I've flashed every ROM from here to Timbuktu, AOKP, Deck's, Evervolv, and have had no problem restoring a nandroid of, or flashing MikG, Mik3D, MikRunny, The Express, or any other ROM I may have forgotten.
That boot partition error doesn't sound good, though. What HBOOT version do you use?
Click to expand...
Click to collapse
HBOOT 0.97 is what I'm still using... never upgraded... should I & how do you recommend that I do so?

davidnjessicacruz said:
HBOOT 0.97 is what I'm still using... never upgraded... should I & how do you recommend that I do so?
Click to expand...
Click to collapse
No reason to upgrade - just wondering.
I'd recommend you flash a stock ROM in the bootloader - that should normalize everything, and then try those other ROMs again.

Captain_Throwback said:
No reason to upgrade - just wondering.
I'd recommend you flash a stock ROM in the bootloader - that should normalize everything, and then try those other ROMs again.
Click to expand...
Click to collapse
I assume your talking about in the recovery (aka amon ra/ clockworkmod), if so then I've tried that as well. Same issue.... This is not sounding good for me.

davidnjessicacruz said:
I assume your talking about in the recovery (aka amon ra/ clockworkmod), if so then I've tried that as well. Same issue.... This is not sounding good for me.
Click to expand...
Click to collapse
I believe he's talking about a RUU
Sent from my PC36100 using XDA App

evo4gnoob said:
I believe he's talking about a RUU
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
The stock one? Wow... don't even know how to flash that back.... hmm... I'll see if I can find it here, if not then I'll google it. I'll keep you informed.... hopefully bricking does not ensue.... any help here would be great as well

davidnjessicacruz said:
The stock one? Wow... don't even know how to flash that back.... hmm... I'll see if I can find it here, if not then I'll google it. I'll keep you informed.... hopefully bricking does not ensue.... any help here would be great as well
Click to expand...
Click to collapse
In the first "My Links" link in my sig, there are 3 of them.
They're PC36IMG files - you rename the file to exactly that - PC36IMG.zip - and put the file on the root of your sd card. Then you reboot your device into bootloader (HBOOT) mode. From a powered off state, hold the Volume down button and then press and hold the power button until you see the HBOOT screen. The file should be recognized and loaded, and after a minute or so it will ask you to update. Press Volume Up to accept, and then wait for a while.
NOTE: This will upgrade your HBOOT, but that's no big deal. The phone will reboot into the bootloader once near the beginning of the process by itself - that is also okay. Don't touch anything while it's updating.
At the end of the process, you'll need to find a PC36IMG for your preferred recovery (RA-supersonic-v2.3 recommended), which you will flash the same way as the ROM (in fact, you can replace the ROM file with the recovery file - unless you want to hold on to it, then you can just move or rename it).

Captain_Throwback said:
In the first "My Links" link in my sig, there are 3 of them.
They're PC36IMG files - you rename the file to exactly that - PC36IMG.zip - and put the file on the root of your sd card. Then you reboot your device into bootloader (HBOOT) mode. From a powered off state, hold the Volume down button and then press and hold the power button until you see the HBOOT screen. The file should be recognized and loaded, and after a minute or so it will ask you to update. Press Volume Up to accept, and then wait for a while.
NOTE: This will upgrade your HBOOT, but that's no big deal. The phone will reboot into the bootloader once near the beginning of the process by itself - that is also okay. Don't touch anything while it's updating.
At the end of the process, you'll need to find a PC36IMG for your preferred recovery (RA-supersonic-v2.3 recommended), which you will flash the same way as the ROM (in fact, you can replace the ROM file with the recovery file - unless you want to hold on to it, then you can just move or rename it).
Click to expand...
Click to collapse
Failed on #4 Boot.... it stated "failed - PU" "Partition failed" Fun times.... Now the phone is a brick (stuck at the white screen).... Where there is a will then there is a way so I'll find a way.... any help would be appreciated though....

Sooo... I was able to flash back my alternate recovery using a PC36IMG version of it. Thank god for the rooted community.... Restoring back my last backup. Funny though, that I still could not restore a rooted stock backup I had or a new upgraded .zip that I wanted to use. Common denominator in all this (even when trying to use the 4.24.651.1 version of the stock software PC36IMG), it can not write the boot.img Any one else had this problem? Next I will try to RUU which will technically make me lose root but I should be able to get it back, assuming I'm successful, since I still have S-OFF.
PS: My HBOOT now, btw, is 2.16.0001 so I know that the original attempt to get back to gingerbread was succesful

[Q]droid gtr rom v1.0 not booting

Ok so I flashed it the first time and it was successful but noticed market was not opening so I flash the latest gapps for cyonogen mod and then everthing fc so wiped and flash and now it won't even boot it gets stuck on splash screen. Is it cause of SD card is on ext 4 or is it smellkus recovery or what?? Any help is much appreciative

Try wiping cache and dalvik then fix permissions in recovery.

Did you flash the correct ROM for your specific phone model and carrier? I had the the problem of flashing a T-Mobile ROM for my GS2 a while back, due to my excitement about using an ICS rom.

Ryan_28 said:
Did you flash the correct ROM for your specific phone model and carrier? I had the the problem of flashing a T-Mobile ROM for my GS2 a while back, due to my excitement about using an ICS rom.
Click to expand...
Click to collapse
Exactly...I've never heard of this rom for the evo. So I question it.

teh roxxorz said:
Exactly...I've never heard of this rom for the evo. So I question it.
Click to expand...
Click to collapse
no its for the evo its under evo general development it was just released

Can you boot into recovery? If so, I think your best bet is to restore a backup, delete the faulty ROM, and try reinstalling it if you want that specific ROM badly enough. That has worked for me a few times.

Ryan_28 said:
Can you boot into recovery? If so, I think your best bet is to restore a backup, delete the faulty ROM, and try reinstalling it if you want that specific ROM badly enough. That has worked for me a few times.[/Q
Yes I could go into recovery and I actually fixed the issue. I'm guessing it was the recovery itself that I was using because now I flashed Among RA recovery and now is booted and working fine. A great Tom overall. Thanks guys for your help
Click to expand...
Click to collapse

Not to bother anyone, but I was trying to run the droid GTRv2.0 ROM on my EVO 4G and it wont get past the first screen.

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