Develop Bugs

[Q] Stuck at bootscreen after every single custom ROM flash.

hi
I´ve rooted and flashed my desire several times. rooted with unrevoked3 everytime and tried different roms like leedroid 2.2d, 2.2 f and rcmixhd 0.13. First time i did it i flashed leedroid 2.2d and it worked fine. After 1,5 months running leedroid my phone rebooted due to the overheating problems that 50 % of us suffer from (i rebooted it manually several times during those months and it worked until this day).
It got stuck at the bootupscreen with white background and green HTCtext. couldn´t install RUU via windows, had to grab the PB99IMG.zip onto my SD and boot into bootloader and restore my phone this way. Then i rooted it AGAIN, and flashed rcmixhd 0.13. Success! But only until i rebooted it manually, stuck at bootupscreen again.
I restored the phone from SD with pb99img as earlier. Flashed rcmixhd again and made sure i wiped everything (dalvik, cache, formatted sdcard and created a EXT), success! Until i rebooted my desire...back again.
Now im running stock non-rooted froyo. I´m getting tired of spending the night fixing it but i still want to use senseHD and i like tweaking stuff..
Do any of u guys recognize this problem and what can i do to fix it?
If any of you are from sweden, plz answer in swedish!

Same problem here, the only way i got to install a custom rom was by installing update-cm-6.1.0-Desire-signed.zip. Then installed a custom rom by using the "Rom Manager" tool.
Downloading and flashing through recovery mode, "No, can do!"

Ok, but "update-cm-6.1.0-Desire-signed.zip" isn´t that a custom ROM? Did you install that through ROM manager?
And did you flash another ROM on top of it?

Suddenjr said:
Ok, but "update-cm-6.1.0-Desire-signed.zip" isn´t that a custom ROM? Did you install that through ROM manager?
And did you flash another ROM on top of it?
Click to expand...
Click to collapse
yes this is a custom rom, i did a normal flash first to "update-cm-6.1.0-Desire-signed.zip" (some how that worked???). Then i reflashed through the "ROM manager" tool.

Do you remember to always wipe everything in Recovery before flashing a new rom?
Seems like I always used to have a bootloop or bootfreeze when did not do the proper wipe.

remmyhi said:
Do you remember to always wipe everything in Recovery before flashing a new rom?
Seems like I always used to have a bootloop or bootfreeze when did not do the proper wipe.
Click to expand...
Click to collapse
i wiped everything even the Dalvik Cache, didn't help a thing.
Could is be that is has something to do with rom's that are not signed?

I have this same problem now, any possible sollutions?

Perdonally i would suggest to reformat your sd cards and try again. Dont forget to wipe everything.
Sent from my LeeDroided Desire HD

Happend to me once or twice.
What to do is, Turn of the phone take out battery do the neccessary wipes and formatting,
root
install clockwork mod from market, go to it and choose install recovery
install rom
install kernel (might affect it somehow)
reboot

[HELP] Bootloop sense roms... (Stock Table)

I recently moved to CM7 and S-OFF. I used the alpha-rev method and flashed the CM7 hboot
Seeing the new Leedroid GB rom, I figured I'd give it a try. So I did a full backup, wiped everything, flashed the stock Hboot from Alpha-rev website, then flashed the Leedroid rom and... BOOTLOOP.
I then tried version 2.4, and same thing.
Following this I flashed Redux, which was nice but slow and I was able to confirm that I had 148 Mb of internal memory...
I then redownloaded Leedroid 3.0.5, thinking my file was perhaps corrupt, and still nothing...
I even tried restoring an my old CoolSenseHD 9 nandroid, which passed the splash screen, but looped at the boot screen.
Any ideas??

I had a similar problem. Go into CWM and format system, data and cache.

Well I'm on Ra-desire-v2.0.0 recovery, and when I do full wipe, it formats everything... something I've done about 10 times in the past 2 hours...
Any other ideas? Is RA somehow incompatible with sense? Should I switch to CWM with fastboot?
EDIT: I've managed to get a stock rooted rom to work... So why not LeeDroid???

i think your recovery is outdated, this can cause bootloops, something to do with your recovery version not able to handle new updater-script.
so update your recovery, you dont have to remove current one, just get the fake-flash.zip of any new recovery (clockworkmod 3.0.2.7) put it on ur sdcard, then in AmonRa select to flash the fake-flash.zip file and it should boot up CWM. then wipe all and flash the ROM.
other than that make sure you have correct partiton layout on ur sd (ext needed ofc) and obviously, correct hboot table.

I tried flashing the latest CWM, then wiping everything and flashing leedroid, but no luck. Then I tried putting AmonRA recovery back, and I tried once more, but still no luck. Then I tried flashing the latest Gingerbread MIUI, and that worked like a charm....
So that rules out my recovery being outdated, and I did flash the latest Radio, so that's good too... I really can't pinpoint the issue, but regardless, I'm really liking MIUI, so that's good I guess.
And as for partitioning, my SD card had a 500MB EXT3 partition for Leedroid, as specified on his page, and my partition table was set to Stock Bravo. I reflashed that Hboot about 4 times just to make sure...

TheSobadef said:
Well I'm on Ra-desire-v2.0.0 recovery, and when I do full wipe, it formats everything... something I've done about 10 times in the past 2 hours...
Any other ideas? Is RA somehow incompatible with sense? Should I switch to CWM with fastboot?
EDIT: I've managed to get a stock rooted rom to work... So why not LeeDroid???
Click to expand...
Click to collapse
As I said, I had this exact problem and solved it by formatting system in CWM. I could flash certain Roms like redux but not leedroid.
AmonRA does not have an option to format system, just wipe which is different.

But even with CWM, I couldn't do it...

I'm guessing it's because the boot.img is too big in the leedroid GB rom, and you have corrupted blocks which limit the allowable size or something. I have that problem with my Desire with certain roms.. which really sucks. Maybe it's because we have Telus branded Desire's lol....

Well I don't believe the Telus Desire is branded (no telus bloatware like other phones, no logo or anything)... I mean I never had to make a gold card, and I haven't been on stock since december...
I just find it wierd that I used to be able to run Froyo leedroid (version 2.3d), but now that I try and flash 2.4 (also froyo) or 3.0 (GB) I have no luck

Have you tried using the RUU to get stock ROM, use Unrevoked and then get the LeeDroid version you wanted?

Are you trying to load htc sense roms on cw7 hboot? Of course it won't work, there is not enough space for the rom.

^If you read my posts, you would know that I have not been using the CM7 HBoot, but the stock Hboot, which is why I was able to load a stock rooted sense rom.
The thing is, I'm afraid to use and RUU because Telus didn't modify their roms in anyway, so carrier RUUs don't exist, yet the phone is locked to Telus... I haven't created a gold-card yet because I haven't had to, yet I feel as though an RUU can jeopardize all of this.

[Q] Can't flash any gingerbread ROM

Hi
I'm trying to flash a gingerbread rom to my desire but I always end up being stuck on the HTC logo. I tried several ROMS( opendesire, modaco with sense and without, some more too but can't remember the names,... ) The only gingerbread ROM that installs is CM7, but i have market problems that annoy the hell out of me ( can't find certain apps, need to hack to install bigger apps ). A shame because i really like CM, but i want to compare with others
Any idea why gingerbread won't flash correctly. I have tried several froyo ROMS without any issues before, by the way
I have
BRAVO PVT1 SHIP S-ON
HBOOT-0.93.0001
RADIO-5.14.05.17
thx
ntdst

Did you remember to wipe your data between each different install?
That's the most common problem when you get stuck at boot.

i use rom-manager and always create a back-up and wipe.
I also tried with an empty SD-Card and repartioned it ( with rom-manager ). The results are always the same, every gingerbread rom gets stuck. I thought there was something wrong with the partitions or maybe i need s-off for gingerbread... ?

What version of CWM do you have? Did you update manually to the new radio for the GB Roms?
- Recommended RADIO
http://insertcoin.dataninja.net/Addons/Radio/
If you flash the 32.56.00.32U_5.17.05.23. Radio a good idea will be to flash
the ril-firmare-drivers updates for it too
Click to expand...
Click to collapse

I'm using Rom Manager v4.2.0.2
It is possible that i flashed that radio with a previous modaco sense/froyo ROM.
should i first flash that one you mention and then try again?

Okay, Rom Manager Is not a recovery What's your recovery exactly?
And what ROMs do you try to flash?
AFAIK, you need to flash that first in order to get booted.

sorry clockworkmod 2.5.0.7 is current recovery
I really tried several ROMS
Modaco sense gingerbread
Modaco without sense
opendesire
oxygen
etc...
all and always stuck on HTC Logo except for CM7, that one works fine except for the market issues

- Clockworkmod Recovery 3.x.x.x (Recommended to be used! 2.x recoveries MAY have some problems with the updater-script => boot loop)
Click to expand...
Click to collapse
I found this in one of the ROM threads.
So my suggestion:
First try to update the radio to the newest (alredy posted the link).
If that does not help, then try to update your recovery.

updating radio and flashing updates did not help
i'm still stuck when trying to install oxygen
I could use some help in updating my recovery. I f i do this with rom manager 2.5.0.7 is the most recent.
I seems there's a 2.5.1.2 out and 3.x.x.x is not advised. Is there an update zip somewhere to use?

People report that Insertcoin S v22 can be installed with 2.5.0.7
Make sure you do a full wipe in THE RECOVERY, not ROM Manager or any program.
Too boot into recovery hold down Power+Vol Down while phone is off.
There:
1. Wipe data/factory reset
2. Wipe cahce
3. Under advanced menu > Wipe dalvik-cache
Also make sure your SD card is partitioned right.
And for the update - you can only update your recovery if you are S-OFF or you use Unrevoked3 with a custom recovery image.

Grab a copy of Ubuntu and check that the apps2sd partition on your card is formatted correctly. I tried all ways of formatting and partitioning (via clockwork/rom manager) and it never formatted correctly and always caused HTC boot sticking.
If I completely reformatted SD and reflashed an older rom (like Leedroid 2.3) would then boot fine. I then used Rom Manager to repartition & format SD, boot ubuntu (live CD is enough - no install required) then reformatted partition to EXT4, flashed and worked fine.
Also, is 2.5.0.7 your TRUE recovery version? Turn your phone on with vol-down held then select recovery - does the version change to an older one? If this is the case you may need to re-root is (Unrevoked) to update your recovery version permanantly.
Hope that helps.

If you are S-off you can flash newest recovery using fastboot, this flash would be permanent!
fastboot flash recovery recovery-clockwork-3.0.2.8-bravo.img

i agree with TMSsecret,
the gingerbread ROMs i have used seem to need a more recent version of HBOOT. First time I tried to flash LeeDroid 3.0.2, it didnt work. Applied S-OFF (which updates your HBOOT during the process) and tried again, worked no worries. Also, if you're keen to install the latest ROMs, upgrade to clockworkmod recovery 3.x... It took me a few tries to get FASTBOOT working properly (possibly because my version of windows XP has had too long to decompose), but if you persevere, it will work.
The best way to make sure your ROM will work is a thorough research session. Not slagging you at all, just pointing out the obvious. Look up everything to do with your intended ROM and read the threads.

Status 7, installation aborted

Hello, I have successfully rooted my HTC Desire running android 2.2 with HBOOT V 0.93.0001 using the Unrevoked method. I Installed ROM Manager and installed ClockWorkMod V 2.5.0.7. I also made a backup.
The purpose was to install a custom ROM, in order to get rid of the Orange bloatware that is on the phone, as well as trying something new.
However whenever I try to instal any ROMS I get an error (Status 7 - installation aborted.)
I then updated the Radio to radio 5.10.05.30 and tried again, same error.
I've tried Cyanogenmod 7, as well as the Oxygen ROM and both aren't working.
I have spent most of today trying to get it to work, and googled alot however I just can't fix this error
Thanks.

you have to do a full wipe data and cache then go to advanced and erase dalvik cache. After all the above you can now install new rom. And if your trying to install new gingerbread you must s off your phone and then update the recovery to the latest one. which i believe is 3.2.0.2 i dunno something like that

When I do a factory reset it just says E: Can't find MISC
No app2sd partition found.
E:cant mount cache:recovery/log
etc etc
says the same thing with wiping the cache, although it does say "cache wipe complete"
when I select wipe Dalvik cache the screen just flickers and appears to do nothing...
What do you mean about updating the recovery, you mean the HBOOT?

Why can nobody answer this? I've literally been reading stuff ALL DAY just to fix this error, yet still can't solve the problem.
Didn't think installing a ROM could be so hard....

I get it you need to back everything up onto your pc from your sd card then go to market on your phone download rom manager and partition your sd with 512mb ext and 0mb swap. and then install any rom u like

Thanks for your help but that didn't work. Not sure what to do.

Which hardwarerevision does your desire have (boot into hboot and read the first line, number behind the word pvt)?

"bravo pvt4 shop s-on"

Just did a hard factory reset, installed ROM Manager and tried again, still didn't work
Also just tried to get my backup restored in the meantime (so I have contacts) oh no, "This does not seem to be a valid backup. The MD5 file is missing"
Can anything else possibly go wrong?

So your hardwarerevision is pvt4. You cannot use clockworkmod recovery and still less rom manager with this one. Download amonra recovery, integrate it in unrevoked (file>custom recovery>choose downloaded amonra recovery) and run unrevoked (like last time) again.
No warranty for any damage.
And a real good advice: Never use rom manager, it's a horrible software which mostly causes heavy and horrible problems!!! Run all operations directly in recovery instead.

Trying that now

MatDrOiD said:
So your hardwarerevision is pvt4. You cannot use clockworkmod recovery and still less rom manager with this one. Download amonra recovery, integrate it in unrevoked (file>custom recovery>choose downloaded amonra recovery) and run unrevoked (like last time) again.
No warranty for any damage.
And a real good advice: Never use rom manager, it's a horrible software which mostly causes heavy and horrible problems!!! Run all operations directly in recovery instead.
Click to expand...
Click to collapse
Are there known issues with revision pvt 4 and ROM manager/ClockWorkMod?
Did just what you said and it's working perfect, I performed a Nandroid backup so I can always go back to the stock ROM, I also unchecked unrevoked forever so the warrenty should be okay IF I go back?
Thanks so much!!!!

rmayling said:
Are there known issues with revision pvt 4 and ROM manager/ClockWorkMod?
Did just what you said and it's working perfect, I performed a Nandroid backup so I can always go back to the stock ROM, I also unchecked unrevoked forever so the warrenty should be okay IF I go back?
Thanks so much!!!!
Click to expand...
Click to collapse
Yes, there are known issues, especially the one you had, which is imho the most important and worst one, because you cannot flash anything.
This disclaimer was referred to me. But yeah, warranty of your provider should be okay if going back to stock.
No problem, happy I could help. Congratulations to you.
Swyped from my HTC Desire using XDA App

Hi there. This might be a bit late but I think I finally find out hot to solve it. It is all because you haven't S-Off your mobile.

so m not goin to get a solution over this,.,.

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