Develop Bugs

I Killed my EVO and need help

I know, first thing to do is search search search... maybe I'm using the wrong keywords but I just cannot find a solution to my problem...
I had rooted with Simple Root OTA and was using DamageControl 3.2.3
Since Froyo came out I decided to unroot and just go stock to test it out
From what I had read, I could just run RUU_Supersonic_1.32.651.6_Radio_1.39.00.05.31_release_171253_signed.exe and all would be fine. I hit the USB connection error and just restarted the exe as stated and all was fine until I hit the Bootloader Version error and then my phone was stuck in a boot loop. My phone now has HBOOT version 0.79.0000 and cannot boot.
I can still get to my custom recovery (RA) so I tried to NAND restore my DC backup and same thing, boot loop. (I also stupidly lost my original NAND backup so cant even try that)
So now I have no idea what to do, I just know there is a solution but for the life of me cannot find it anywhere.
Sigh, please someone, help an Android newcomer...

Since you have Amon Ra wipe the data and cache then install another ROM.
If you want to use Froyo, CM6 or Backed Snacks are both good choices.
A bit more in-depth:
On PC
1. Download the ROM of your choice
On Phone
2. Boot to Amon Ra
3. Put it in storage mode
On PC
4. Move the ROM you downloaded onto the phone.
On Phone
5. Take it out of storage mode
6. Wipe data/cache/dalvik cache
7. Choose "Install from ZIP" then choose your ROM
8. Let it install then boot
9. You should be set

I tried such a step with Fresh 3.0 and unfortunately it was no dice.
I just finally hit upon a solution before I passed out from frustration and exhaustion.
I ran the newest RUU 1.47.* and copied the rom.zip over and renamed it to PC36IMG.zip to install it directly from the phone and it worked like a charm, I then upgraded to Froyo via the OTA.
The speed increase (thanks to JIT) and better battery life is all I really wanted, I can wait until its rooted to get back anything I miss.
Thanks for they reply

ch3vr0n5 said:
I tried such a step with Fresh 3.0 and unfortunately it was no dice.
I just finally hit upon a solution before I passed out from frustration and exhaustion.
I ran the newest RUU 1.47.* and copied the rom.zip over and renamed it to PC36IMG.zip to install it directly from the phone and it worked like a charm, I then upgraded to Froyo via the OTA.
The speed increase (thanks to JIT) and better battery life is all I really wanted, I can wait until its rooted to get back anything I miss.
Thanks for they reply
Click to expand...
Click to collapse
but you do know 2.2 roms are out so you unrooted and went to stock 2.2 instead of downloading an existing 2.2 rooted rom : \

I can't get my GPS to work no matter what I do, please help me.

It stays stuck on searching for GPS and never finds signal. I remember a month or so ago when i flashed the MIUI rom I also went in with file manager and replaced the froyo GPS driver with the GB GPS driver so that be why, but I have no clue. I have to go on a long road trip in an hour and I have no printer here at home so a GPS would be nice. What are some fixes that I can try?
EDIT: I'm currently using Kushdecks latest rom.

backup your rom, install sense 2.2 rom. don't even login just skip it all, dial ##gpsclrx# then enter your msl, reboot, open google maps, wait for lock on your location, turn off phone and restore your backup

Thank you, and formally thanked. Trying this now. Crossing my fingers that this works. I didn't think that you could revert back to a 2.2 rom after having flashed a GB rom.

you can flash any rom, anytime. you said you had an hour and 2.2 roms are smaller

NewZJ said:
you can flash any rom, anytime. you said you had an hour and 2.2 roms are smaller
Click to expand...
Click to collapse
Dang it, now when I try to create a nandroid backup it says "oops...something went wrong. Please check recovery log". I think it may be because I don't have enough space on my SD card. I have amon_ra recovery installed, not sure which version as I haven't updated in a while.

Try this! Unzip and place the attached file on root of sd. Using a file manager like Estrongs or Root Explorer copy and paste into /system/lib/hw over-writing the original file. Reboot and all should be good.

Man, I'm sorry!! I misunderstood your post...looks like you've already got that one.
Sorry bro

jhoffy22 said:
Dang it, now when I try to create a nandroid backup it says "oops...something went wrong. Please check recovery log". I think it may be because I don't have enough space on my SD card. I have amon_ra recovery installed, not sure which version as I haven't updated in a while.
Click to expand...
Click to collapse
I had that problem a while ago, I was using v1.8 and I just upgraded to 2.3 and it fixed the problem. I could restore my previous nandroid backups without problem.

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

Hey guys,
So here's what happened and is happening:
1. I was running a custom ROM (Baked Snack 1.7) on Froyo (2.2). The phone was working fine but I wanted to try Gingerbread 2.3.3 out because I heard it had great battery life.
2. My phone would not update to 2.3.3 from Baked Snack. I thought it might have something to do with it being rooted. I used this method to unroot...and I think I only got through the first part:
http://www.thedroiddemos.com/2010/09/10/how-to-unroot-the-evo-in-2-steps/
I installed the S-On tool like he said to. Then I moved the "new updated version" of PC36IMG (I had the old version on my card already). He said something about the "S-Off" appearing on his phone but not the viewer's...well, mine says S-Off.
So fast forwarding, I got Sprint to push me the update for 2.3.3. It downloaded it, but then a voicemail error came up saying I had 2 voicemails. Then when I called voicemail, it said I had no messages. Sprint said a Sprint store would have to physically go into the phone to erase the error.
I also got a second update message that said there were minor enhancements to Gingerbread. I tried downloading them but the installation failed. Sprint told me to ignore the update, that there had been issues with Gingerbread (and the update) and that they were working on getting these resolved.
Somehow I managed to clear the phone and get back to 2.1. Here's what my system says when I look at the Phone Information:
Firmware Version: 2.1-update1
When I boot into the main bootloader/Recovery menu (Phone Off + Power Button + Volume Down), here's what it says:
Supersonic EVT2-2 ENG S-OFF
HBOOT-0.76.2000 (PC3610000)
If I click down to Recovery from this menu and press "Power" to enter it, NOW I get a picture of an EVO with a Red Triangle/Exclamation Point. This means I have to take my battery out and restart the phone.
Also, the OTA SimpleRoot procedure doesn't seem to work on the phone either. When I originally set it back, the procedure worked. Now it just goes through the motions on the computer but nothing happens with the phone (rebooting, skating Androids, etc.)
All I want to do is basically put it back 2.2 and re-run Baked Snack 1.7 which was giving me NO issues.
If someone could help me with this issue, I would be very grateful.

Well you have a simple fix. The error you got with the triangle and red ! is you booting into recovery, but no recovery is loaded [stock recovery]. Head over to the development section, and download the recovery of your choice. Personally I recommend in order: twrp [team win recovery project] , amon ra 2.3, cwm 3.0+. After you have your recovery installed, boot back into recovery and flash your baked snack rom. Also, don't manually take an OTA of 2.3.3 as it can't be rooted. if you want to try a gingerbread rom, simply download CM7, evervolv, deck's, ect rom and flash it like any other rom. Just backup your previous rom before flashing so you can go back.

teh roxxorz said:
Well you have a simple fix. The error you got with the triangle and red ! is you booting into recovery, but no recovery is loaded [stock recovery]. Head over to the development section, and download the recovery of your choice. Personally I recommend in order: twrp [team win recovery project] , amon ra 2.3, cwm 3.0+. After you have your recovery installed, boot back into recovery and flash your baked snack rom. Also, don't manually take an OTA of 2.3.3 as it can't be rooted. if you want to try a gingerbread rom, simply download CM7, evervolv, deck's, ect rom and flash it like any other rom. Just backup your previous rom before flashing so you can go back.
Click to expand...
Click to collapse
You like TWRP better??
I haven't tried it yet

HipKat said:
You like TWRP better??
I haven't tried it yet
Click to expand...
Click to collapse
Basically amon ra, but better. it has some additional options, such as the option to automatically reboot after a successful flash [good for doing a single flash, but if you're doing multiple, checked it at the last flash.] You have the option to compress backups to save space, though it takes a little bit longer, and they have some built in skins you can change at will. And MOAR.

I tried rooting using this method:
http://www.androidcentral.com/evo-4g-root-instructions
I put the PC36IMG on the root of my SD card and let the phone update in bootloader. It seemed to work fine, updated, rebooted the phone, etc.
Then I downloaded ROM Manager so I could let Clockwork install and then install Amon Ra....when ROM Manager tried installing Clockwork, it gave me the following message: "An error occurred while attempting to run privileged commands!"
It also will not let me flash an alternate recovery. I have the file "recovery-RA-supersonic-v2.3.img" on the root of my SD card right now.
What does this mean? Does this mean I'm not rooted? Or some other issue? I remember eons ago when I tried using this program I got the same message but I don't remember how I got around it. (obviously I did though)
Is there a different way I should install it?

nbakid2000 said:
I tried rooting using this method:
http://www.androidcentral.com/evo-4g-root-instructions
I put the PC36IMG on the root of my SD card and let the phone update in bootloader. It seemed to work fine, updated, rebooted the phone, etc.
Then I downloaded ROM Manager so I could let Clockwork install and then install Amon Ra....when ROM Manager tried installing Clockwork, it gave me the following message: "An error occurred while attempting to run privileged commands!"
It also will not let me flash an alternate recovery. I have the file "recovery-RA-supersonic-v2.3.img" on the root of my SD card right now.
What does this mean? Does this mean I'm not rooted? Or some other issue? I remember eons ago when I tried using this program I got the same message but I don't remember how I got around it. (obviously I did though)
Is there a different way I should install it?
Click to expand...
Click to collapse
That's a bit outdated; use unrevoked. I've already done the linking for you.
1. http://unrevoked.com/rootwiki/doku.php/public/windows_hboot_driver_install <- Download and install the modified hboot drivers, follow the instructions.
2. On your phone, enable usb debugging from the applications > development, in settings
3. Connect your phone to your pc via usb cable, leave it on the home screen, no apps should be running; restart the phone just to be sure.
4. http://unrevoked.com/rootwiki/doku.php/public/windows_hboot_driver_install <- download and run unrevoked
It'll take 3-5 minutes and reboot about 2 times, don't touch in the process, it'll say done at the end. Also, this will only work if on 2.2 still. if on 2.3.3, you're outta luck.

Okay, forget Rom Manager, forget "rooting" your phone - at least according to the normal use of the word.
Delete any PC36IMG files you may have on your SD card, then download this one of Amon Ra 2.3: http://db.tt/WP0beNa
Don't rename it, don't extract it... just put it on the root of your SD card. Then download whatever rom you want to use. Put it on the root of your SD card or in a folder that you'll remember. Amon Ra (and possibly other recoveries) can flash zips that are inside of folders. Just be sure that you know where it is because you'll need to navigate to it in recovery.
Then boot into the bootloader and let it flash the way you've done with other PC36IMG files. When it asks you to reboot just decline and then select recovery. I would make a backup just in case, then flash your rom.
Sent from my PC36100 using Tapatalk

Thank you guys, I will try these methods when I get back from work tonight. I really really appreciate it, I was about having a meltdown without my phone (the way I want it).
I'll report back either way. (and yes, I'm still on 2.1-update1)

nbakid2000 said:
Thank you guys, I will try these methods when I get back from work tonight. I really really appreciate it, I was about having a meltdown without my phone (the way I want it).
I'll report back either way. (and yes, I'm still on 2.1-update1)
Click to expand...
Click to collapse
Well between plainjane and myself, you'll be rooted before dinner time!

teh roxxorz said:
Well between plainjane and myself, you'll be rooted before dinner time!
Click to expand...
Click to collapse
OK, I forgot to mention this earlier...last time I was stuck in the Boot Sequence where it kept looping the Sprint and 4G logo....now that I'm rooted using plainjane's method (thank you) I'm stuck with the same thing.
I flashed the recovery, then flashed the Baked Snack ROM....now I'm in the Baked Snack bootload section....and it just keeps looping.
Is this an issue with my system that can be resolved?

EDIT: So weird. I went back into Recovery and wiped everything and set the phone back to original condition...and voila, Baked Snack comes up as the ROM! So now it appears it's for the most part back to normal and back to where I wanted it....thank you guys again.
Now can anyone point me in the direction of the latest radios, etc. that I can download and flash?
And why would it be giving me those looping problems, and then go back to normal when I cleared/wiped everything?
I mean, I'm happy this happened but I don't want the same things happening if I decide to flash another ROM at some point.

pc36img problems

I have been using the very stable pc36img spring lovers version. I flashed a bunch of roms yesterday like I usually do. The last one was the miui rom from yesterday. It didn't work. tried to do a nandroid update but could not. Then I used the pc36img that has worked well for a while but everything updated except the system. it said failure-UZ. luckily later I was able to instal a hybrid rom with MANY bugs. I no longer can upload my contacts. If you have an idea or can point me in the direction of a pc36img that may solve this I would greatly appreciate it. I know I should have moved my backups to the sd card but I messed up here. Please help. Thanks

Honestly you should stop flashing roms as PC36IMG because you'll forget what they are eventually. Download the rom you want, place it on your sd card, then do a full wipe, and flash it in recovery, boot up, and you should be fine.

That is what I do. but after flashing yesterday's miui rom from the zip file my system wouldn't let me do a nandroid backup. In desparation I used my pc36img update and now a I am screwed

pc36img probs
yesterday I flashed a bunch of roms from the sd card but something happened after the miui zip file

pc36img
in desparation I used the pc36img update. Now I am looking for a way to fix the system update part of the pc36img update which doesn't work. I only use the pc36img when nothing else works.

can anyone point in the direction of some good pc36img files. I am very desperate here. I have tried everything

Take it to Sprint, tell them it just broke. They will happily load stock GB, then you can start over.
KJ

it is S-off. warrenty is finished. also I would like to fix it myself. All of these little messups teach me a lot

Did you try wiping everything except sdcard 3 times in recovery than flashing a .zip rom in recovery
Sent from my PC36100 using XDA App

pc36img probs
I will try that. It will have to wait until monday bc I am on call this weekend. I can't lose my phone. thanks for the tip. I will post the results on monday. I hope it works. btw should I wipe with the sdcard removed?

pc36img
I couldn't wait. I tried it and it again said Fail-UZ when updating the system. it also said image unzipping fail. Any other ideas?

The only PC36IMG's you should ever flash, really is recovery and RUU. Everything else you should do in recovery with a flashable zip.

jjdellorusso said:
I couldn't wait. I tried it and it again said Fail-UZ when updating the system. it also said image unzipping fail. Any other ideas?
Click to expand...
Click to collapse
You hav to flash in {recovery} not bootloader
Download file (click link below) Keep as is go into bootloader let it scan hit no if it ask to update then hit recovery then click wipe then wipe everything except sdcard 3 times then hit flash zip from sdcard then go to this file that you downloaded and select it
http://link.geekfor.me/freshevo431
Sent from my PC36100 using XDA App

pc36imgprobs
tried wiping 3 times
now I can use roms but when running pc36img (sprint lovers) it always sais fail-uz (failure unzipping) should I just ignore this and move on??? I don't really know the significance of this. I can flash working roms now but something makes me feel uncertain. Why can't I update the system with the ruu? any other ideas?

pc36img probs
just wiped everything again... and still no dice. The phone now works like it did before, but the pc36img (sprint lovers) system update always fails. I am running hboot 6.16.1002. Is that the wrong one?

jjdellorusso said:
just wiped everything again... and still no dice. The phone now works like it did before, but the pc36img (sprint lovers) system update always fails. I am running hboot 6.16.1002. Is that the wrong one?
Click to expand...
Click to collapse
ok this is all i can think of:
1 - get the original pc36img.zip file and put it in your sd
2 - delete the amon ra pc36img.zip that you have
3 - go into bootloader and when asked to update hit yes
4 - when asked to reboot hit yes
5 - if your phone reboots fine (i will give it a pretty good amount of time) download rom manager
6 - in rom manager flash Clock Work Mod (CWM)
7 - Then make a back up (optional).
8 - scroll down in Rom manager and flash alternate recovery (this will give you amon ra w/o having to put the pc36img.zip into your sd card.
9 - do what you wanted to do at first.

jjdellorusso said:
I have been using the very stable pc36img spring lovers version. I flashed a bunch of roms yesterday like I usually do. The last one was the miui rom from yesterday. It didn't work. tried to do a nandroid update but could not. Then I used the pc36img that has worked well for a while but everything updated except the system. it said failure-UZ. luckily later I was able to instal a hybrid rom with MANY bugs. I no longer can upload my contacts. If you have an idea or can point me in the direction of a pc36img that may solve this I would greatly appreciate it. I know I should have moved my backups to the sd card but I messed up here. Please help. Thanks
Click to expand...
Click to collapse
You guys are talking about PC36IMG.zip as if its a ROM that is being flashed. Sprint Lovers, if I am not mistaken, is a ROM that should be flashed via recovery like all ROMs should be. You should not be flashing PC36IMG.zip files through Bootloader unless you are updating radios, RUU back to stock, splash screen updates, etc. It sounds like you are spending a lot of time flashing things via bootloader and that is what got you in this mess to begin with. Can you get into recovery? If so then download any ROM, enter recovery, wipe cache/dalvik cache/data, flash ROM, and then quit using the bootloader before you permanently screw up your phone. This problem should be able to be fixed without the use of a PC36IMG.zip file. Because you've gotten flash happy in your bootloader and as of right now you can't tell us exactly what you've flashed.
If you cant get into recovery then just download Amon Ra v2.3, flash it, and then do the steps I mentioned above. It's not difficult. Just stop getting flash happy with your bootloader.

There is a version of Sprint lovers that can be flashed thru bootloader
And for jj that might just mean the pc36img is corrupted you can download a new one but I say just nice on and use recovery instead of bootloader
Sent from my PC36100 using XDA App

jjdellorusso said:
it is S-off. warrenty is finished. also I would like to fix it myself. All of these little messups teach me a lot
Click to expand...
Click to collapse
"Warranty's" can be restored

pc36img probs
hmmm? I have tried everything as described above. maybe my sprint lovers pc36img has been corrupted. but I really don't think so bc I saved it in many different sdcards and in my computer. Should I try another .zip? can anyone point me to other pc36img files that may help. I must say that I do not flash anything by pc36img, but after I flashed hybrid I couldn't do anything. In desperation I tried my sprint lovers pc36img assuming I could go back. I had to many backups saved and it told me that I didn't have enough space when I tried to do a nandroid backup. I guess the take home message is to save nandroid backups to the sd card also. unfortunately mine is lost.

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