Develop Bugs

[Q] Please help, weird Desire, dont work with any custom ROM !

Maybe you think im just too stupid or whatever, but im not i know how to root, to debrand, to wipe and so on. Im using a PVT4 desire which was vodafone branded (2.33.161...) with hboot 0.93. I downgraded and rooted it sucessfully and have (2.29.405.5) everything works fine. If i want to flash any custom rom, sense or sense hd (using amonra 2.0.0) ..everything works until standby ..on nearly each standby the phone freezes or hangs up or whatever ..the only thing that helps , is pulling out the battery and insert it again. So not any custom rom works for me and i hate it. i love the htc sense on hd roms and i really like some themes, but i cant really use it please anybody could try to help me why this happens. i really did nothin wrong for partition i used gparted like described mostly and in the end i set my phone s off (cuz i thaught this maybe would help) of course sucessfully. i tried diffrent ext partitions, i tried another battery, i tried another sdcard, i stopped the automatic email refresh ...,i tried app2sd+ and data2sd, i actually did nothin and let the rom the way it was ...but again it freezes on standby (not the first, not every, but the most of a day) ... my boyfriend has the same phone, also with pvt4 ...and for him everything works great without any issues. so please anybody help to fix this or at first find out why that happens
greetings

FlyGirly said:
Maybe you think im just too stupid or whatever, but im not i know how to root, to debrand, to wipe and so on. Im using a PVT4 desire which was vodafone branded (2.33.161...) with hboot 0.93. I downgraded and rooted it sucessfully and have (2.29.405.5) everything works fine. If i want to flash any custom rom, sense or sense hd (using amonra 2.0.0) ..everything works until standby ..on nearly each standby the phone freezes or hangs up or whatever ..the only thing that helps , is pulling out the battery and insert it again. So not any custom rom works for me and i hate it. i love the htc sense on hd roms and i really like some themes, but i cant really use it please anybody could try to help me why this happens. i really did nothin wrong for partition i used gparted like described mostly and in the end i set my phone s off (cuz i thaught this maybe would help) of course sucessfully. i tried diffrent ext partitions, i tried another battery, i tried another sdcard, i stopped the automatic email refresh ...,i tried app2sd+ and data2sd, i actually did nothin and let the rom the way it was ...but again it freezes on standby (not the first, not every, but the most of a day) ... my boyfriend has the same phone, also with pvt4 ...and for him everything works great without any issues. so please anybody help to fix this or at first find out why that happens
greetings
Click to expand...
Click to collapse
Have you tried flashing a ROM using CWM recovery?

No i didnt. Could that be the reason for this problem ? I used amonra because cwm could not flash zip files as far as i know ?
Sent from my HTC Desire using XDA App

i had a similar problem with my g/f's phone, had been rooted for 6 months, had several custom roms, ( though she only likes sense roms ) i did an update, and it just kept freezing, so i tried several other sense roms, and they all kept freezing, no matter how many full wipes i did, they would just freeze.
so i installed a stock android rom, then from the stock android rom, flashed the sense rom, it worked after that, i duno why it did, i just know it worked for me, duno if it helps but might be worth a try.
Also i use CWM too.

Amon Ra Latest
Is this the version of Amon Ra you use?
http://forum.xda-developers.com/showpost.php?p=9447821&postcount=152

mintvilla said:
i had a similar problem with my g/f's phone, had been rooted for 6 months, had several custom roms, ( though she only likes sense roms ) i did an update, and it just kept freezing, so i tried several other sense roms, and they all kept freezing, no matter how many full wipes i did, they would just freeze.
so i installed a stock android rom, then from the stock android rom, flashed the sense rom, it worked after that, i duno why it did, i just know it worked for me, duno if it helps but might be worth a try.
Also i use CWM too.
Click to expand...
Click to collapse
i dont really understand that stock rom part ...at downgrading i used the pb99img (2.29.405.5) from shipped .like it was told on some german site cuz i normally got an radio_V2 fail pu at the image loading on hboot ...with that there were no failures..so i guess this is my "base" that i rooted and with that i did everything else.. do u mean i should install a custom stock rom !? or maybe give me an example please

papadcha said:
Is this the version of Amon Ra you use?
http://forum.xda-developers.com/showpost.php?p=9447821&postcount=152
Click to expand...
Click to collapse
yes thats it

FlyGirly said:
No i didnt. Could that be the reason for this problem ? I used amonra because cwm could not flash zip files as far as i know ?
Sent from my HTC Desire using XDA App
Click to expand...
Click to collapse
CWM flashes zip files with no problem. Just use an older version like 2.5.1.8 or something.

ShirazSuleman said:
CWM flashes zip files with no problem. Just use an older version like 2.5.1.8 or something.
Click to expand...
Click to collapse
ok i will try this out ..but i need to know ..could the nand backup i did with amonra be restored with cwm !?

FlyGirly said:
ok i will try this out ..but i need to know ..could the nand backup i did with amonra be restored with cwm !?
Click to expand...
Click to collapse
Don't think so.

FlyGirly said:
ok i will try this out ..but i need to know ..could the nand backup i did with amonra be restored with cwm !?
Click to expand...
Click to collapse
nope, it definitely won't work. if you wanna try cwm, v2.5.0.7 is the best and most rock solid. is your phone s-offed?

Yes i have s off ..the easiest way to get clockwork in my opinion is using s off again and install it (can i do this or does that some damage to my phone ?) I read that v2.5.1.8 is suporting pvt4 desires. So i guess thats the best ?
Sent from my HTC Desire using XDA App

oops my bad. didn't notice the pvt4 part. you can just download the android sdk and use the fastboot command or you can use android flasher which has a simple straight forward gui.

could i also use unrevoked !? and use instead the ra desire 2.0.0 img the cwm img !? i like using things i already know instead of new stuff ..and im not so good at fastboot commands ...and i cant find the cwm 2.5.1.8 from alpharev

FlyGirly said:
could i also use unrevoked !? and use instead the ra desire 2.0.0 img the cwm img !? i like using things i already know instead of new stuff ..and im not so good at fastboot commands ...and i cant find the cwm 2.5.1.8 from alpharev
Click to expand...
Click to collapse
flashing with unrevoked can screw up your superuser app. ra 2.0.0 doesn't backup the whole ext partition only app if i recall correctly. i'm not sure if ra supports pvt4. couldn't find any mention of it in the thread's first post.
the alpharev cwm is here

MrDevil said:
flashing with unrevoked can screw up your superuser app. ra 2.0.0 doesn't backup the whole ext partition only app if i recall correctly. i'm not sure if ra supports pvt4. couldn't find any mention of it in the thread's first post.
the alpharev cwm is here
Click to expand...
Click to collapse
i guess i expressed myself wrong ..i have ra desire 2.0.0 ..and i guess it works ...i meant that img i flashed by getting root with unrevoked ... my question was if i easily could flash the cwm image with unrevoked ....but in the meantime i read that a rooted phone cant be rooted again ..so nevermind

FlyGirly said:
i guess i expressed myself wrong ..i have ra desire 2.0.0 ..and i guess it works ...i meant that img i flashed by getting root with unrevoked ... my question was if i easily could flash the cwm image with unrevoked ....but in the meantime i read that a rooted phone cant be rooted again ..so nevermind
Click to expand...
Click to collapse
yes u can flash it with unrevoked. just mentioning that it screws up your superuser app.

after searching the whole time ..the alpharev version ..i finally saw that u already posted
using unrevoked worked fine dont care about superuser dont have it atm... trying an custom rom now ...hope my issue will have an end

Just my 2 cents... AFAIK for PVT4 desires AmonRA is recommended, cause CWM has issues. At least that's what I read about PVT4 (earsize 40000).

Hi guys, i only got my desire yesterday (bye bye cliq/dext at last) and can confirm what nagypapi is saying as i have a uk desire pvt-4 with 40000 errorsize and CWM definately doesn't work, i had a small problem where unrevoked 3.32 wouldn't properly install amonRA or CWM, in the end i had to use unrevoked 3.21 and i'm now running ReflexTSenseHD 1.8 Sense DHD 2.2 FRF91 A2SD+ OC'd to 1113Mhz. Have tried flashing a lot of the roms available and not all of them seem to work for me. CyanogenMOD7 and Oxygen v2.0 RC7 get to the setup screen and then go into an endless bootloop, whilst DeFroST 6.1a, RCMixHD v3.0 and Amethyst RC7 won't load past the htc splash screen. I have H BOOT S-ON still as i'm not entirely confident at attempting the AlphaRev 1.8 method just yet, could this be the cause?
Thanks in advance for any replies, kingears

Recovery with HBOOT 0.93, Custom Rom Doesn't boot

Dear xda members,
I'm currently stuck on a problem with my Desire.
I had to Unroot my Desire because it needed to be repaired. Now that's done and I want to get it rooted again the only problem is, I now have HBOOT 0.93.
I've tried to unroot it with UnRevoked and installed ClockWorkMod as custom recovery. and I'm not trying to get it back to HBOOT 0.80 with a PB99IMG file but that doesn't work.
I installed a Custom rom through the ClockWorkMod Recovery, Custom Rom Ginger Villain but it doesn't boot.
I don't know what to do anymore? How can I get it back to HBOOT 0.80 or install a custom rom that does boot without problems?
Hope someone has the answer, I'll keep trying in the meantime!

This has nothing to do with your hboot version... Don't know why you would think so..
On gsm desire all current hboot versions are rootable, and i take it you have got it rooted without trouble on hboot 0.93 so there is no problem.
If the phone doesn't boot a fresh install of a custom rom even after a full wipe something is wrong, but do you get an error in recovery when flashing?
Also what was repaired? If your mainboard was replaced there is a good chance you have got the new hw revision which means you will need an alternate recovery.

I thought maybe the custom rom wasn't made for the HBOOT version or wasn't supported, thought they were related.
and I think I got it rooted because there wasn't any error with Unrevokedand I got a recovery.
I didn't get any errors installing the custom rom.
My IMEI didn't change so I don't think the Mainboard is replaced?
There was a problem with the speaker.
But should I just install another rom and try if that one works?
UPDATE:
After trying 4 RUU's I've finally got one that works. so now I'm back to Stock Froyo with Sense.
Guess I have to try it again now.
I'm trying to install Ginger Villain Again but again I only get a bootloop the whole time. I don't get any errors at all in the process only bootloops...
And I now have the exact same bootloop with Oxygen rom

I now got it back to HBOOT 0.83 but still with every Rom I get bootloops. Is there anything I missed? I got it rooted, got a recovery installed and wiped everything before installing.

SterAllures said:
I now got it back to HBOOT 0.83 but still with every Rom I get bootloops. Is there anything I missed? I got it rooted, got a recovery installed and wiped everything before installing.
Click to expand...
Click to collapse
Did u format SD Card and partitioned it as corresponding in the ROM Thread instructions?
For example if you flashing d2ext or app2sd ROM you need a FAT32 + EXT3/4 primary partitions (FAT32 always first!).

Lol had the same problem.
You did not clear all the cache and stuff. I cant remember all the ones.
think it is
cache
wipe phone data
davlik
not sure if there is another one
basically this is your problem. I wasted so much time figuring this out because i was too lazy to wipe them
all your roms will boot until you wipe your phone properly

MIUI: Stuck on BOOT

Yesterday, I decided to flash a MIUI (beta) rom, but I am stuck on the 'shiny android boot loading screen'. Before flashing the ROM I had Wiped all user DATA/CACHE/DALVIK-CACHE/EXT and all other as well as formatting my SD card to the following:
HTML:
Swap Size: 0MB
EXT 4: 1GB
No matter what I do, whether it's pulling out the battery and leaving it or wipe cache again it just gets stuck on the same old boot screen doing nothing.
Here are my phone specs:
HTML:
S-OFF PVT1 Revolutionary
HBOOT-6.93.1002
RADIO-5.17.05.23
I know I dob't have USB Brick because it works fine and I can boot into Recovery and Bootloader/FastBoot. I don't understand why this has happened as I had flashed a MIUI ROM 2 months agao and everything went well, it could be that my H-BOOT is different or I have S-OFF.
Please help me resolve this issue.
Many Thanks.

Latest version happened to do the same for me.
I just flashed it a couple of times. It works now.
The strangest thing was, that it was no bootloop or any error - it just sat there for infinity.

Does the Rom require a different hboot? Or might it need an ext 3 partition?
Sent from my HTC Desire using XDA App

davebugyi said:
Latest version happened to do the same for me.
I just flashed it a couple of times. It works now.
The strangest thing was, that it was no bootloop or any error - it just sat there for infinity.
Click to expand...
Click to collapse
Yes, that is what is happening here, but I flashed it several times and no go. The setup seems so quick to be installed...it only lasts 40 seconds and says it's complete.
ste1164 said:
Does the Rom require a different hboot? Or might it need an ext 3 partition?
Click to expand...
Click to collapse
I have no idea, surely not?

I have alpharev sense HBOOT, but MIUI should work with all others (except for oxygen/oxygenr2)
I'd recommend to download the .zip again and check md5 sum - then flash again.

Which version of MIUI is it that you flashed?
Mine has to have an EXT3 partition or it wont work ..

EDIT:
/facepalm
I can't believe I expected the ROM to be installed just by flashing the 'Pack' which I didn't reliase is just an language pack. I thought the term 'Pack' meant everything including the ROM, lol.
ISSUE Ressolved. Thanks anyways guys.

Deeco7 said:
... Ressolved...
Click to expand...
Click to collapse
And this to your topic's name to help others.

Aha I'm glad you solved it.
Sent from my HTC Desire using XDA App

Phone hangs after new ROM install

Hello all!
Yesterday I decided I wanted to try the latest RCMix ROM (v2.2b). Usually I do the update from ROM Manager, but it informed me there was a new version to download so I downloaded it.
Anyway, I proceeded with it and installed the ROM and everything went fine, until it rebooted, which it then just hung on the s-off boot screen. I waited for an hour but to no avail so had to take out the battery.
So, I tried to do it again manually by doing a factory wipe/clear cache/clear dalvik cache and flashed again, but again, same thing happened even though it said it had installed ok. I tried doing this 5 times before I gave up (although leaving 20 minutes on the boot screen before giving up each time)
Next I decided that maybe it was the new version of the ROM, so I downloaded the v2.1 of it, but still got the same problem, so then I decided to try my original one (v2.0) because it worked fine previously, but this also didn't work!
Finally, I decided I best try a different ROM altogether, so I tried the LeeDroid ROM (which I've used in the past,albeit a previous version), but this also has the same problem.
So, I'm a bit stuck what to do, hence why I've had to post on here. I've read that the latest clockworkmod recovery has some issues, does this still apply? Could this be the cause of my problem? I've tried finding a previous version of clockworkmod to install via sd card to test it out, but had no luck finding one.
Does anyone else have any suggestions on what I can do? Please bare in mind that I'm not very good with all the technical side of this so please try keep it as simple as possible for me!
My phone recovery says the following:
AlphaRev CM7 r2
BRAVO PVT1 SHIP S-OFF
HBOOT-6.93.1002
MICROP-031d
TOUCH PANEL-SYNW0101
RADIO-5.10.05.23
ClockworkMod Recovery v5.0.2.0
Thanks in advance for your help

hi there, do the roms you are trying require an ext partition on the sd card?

elliottg61 said:
hi there, do the roms you are trying require an ext partition on the sd card?
Click to expand...
Click to collapse
I believe they do yes. I did forget to mention I do have my SD card partitioned with 1GB~ ext partition

go to mounts and storage
format:
-boot
-system
-data
-cache
-sd-ext
-NOT SD-CARD!!!!!!!!!!!!!!!
Try to flash the rom again

bortak said:
go to mounts and storage
format:
-boot
-system
-data
-cache
-sd-ext
-NOT SD-CARD!!!!!!!!!!!!!!!
Try to flash the rom again
Click to expand...
Click to collapse
Out of curiosity, what would happen if I did SD-Card?
I shall try it now anyway and let you know

smhouston said:
Out of curiosity, what would happen if I did SD-Card?
I shall try it now anyway and let you know
Click to expand...
Click to collapse
I wonder what would formatting my Sd-Card do, possibly delete anything and everything off of it?

bortak said:
I wonder what would formatting my Sd-Card do, possibly delete anything and everything off of it?
Click to expand...
Click to collapse
lol I mean would it have any affect on the ROM installation process? Obviously I'd lose all my personal data but I have it all backed up anyway
Waiting to see if it'll load atm, still on the same screen, but only been 5 minutes so far. What's the next option if this doesn't work? I was thinking about just trying to go back to stock and start it all form scratch again.

As suspected, it still did the same thing :-(

Are the roms you are installing for specific use with the CM7 Hboot?

You mentioned Rom manager at the start, are you downloading your roms through there or from your pc?
Sent from my HTC Desire

Try EVERYTHING without ROM manager....

rootSU said:
Are the roms you are installing for specific use with the CM7 Hboot?
Click to expand...
Click to collapse
I think the RCMiX used to be
mistaliu said:
You mentioned Rom manager at the start, are you downloading your roms through there or from your pc?
Sent from my HTC Desire
Click to expand...
Click to collapse
I usually download the ROMs manually, place on the SD card, then do the install by selecting the option in ROM Manager
rootSU said:
Try EVERYTHING without ROM manager....
Click to expand...
Click to collapse
I'm going to remember this for the future!
After me being impatient (you'll probably be disheartened to hear) I've decided to go the stock way to try get me back to the beginning. After a lot of messing around (reformatting sd-card and placing files on it via a laptop which had the files put on there via USB flash drive!) I think I've managed to get it down to stock again. The bootloader screen thingy says:
BRAVO UNKNOWN SHIP S-ON
HBOOT-0.75.0000
MICROP-031d
TOUCH PANEL-SYNW0101
RADIO-4.05.00.11
and when I try select the RECOVERY option it just displays the red triangle (I believe this is because it's not rooted or something (can't currently remember how got it working last time)?)
The problem now though is I would have though I should be able to boot normally now? What happens is when I press the power button it just goes straight into the bootlader screen.

At the triangle, you press vol UP + Power to get to stock recovery. Cant do much there but factory reset though.
did you fastboot flash the downgrader.img from Alpharev before running the RUU?

rootSU said:
At the triangle, you press vol UP + Power to get to stock recovery. Cant do much there but factory reset though.
did you fastboot flash the downgrader.img from Alpharev before running the RUU?
Click to expand...
Click to collapse
I've just tried the up + power but when I do it displays the menu options i.e. Apply sdcard:update.zip and wipe data/factory reset; however, it has a yellow message below saying E:Can't open /cache/recovery/command ..... should I be concerned?
Yes I flashed the bravo_downgrade.img located at http://alpharev.nl/ by doing it via the SD card. Currently I can't connect to my phone via adb

smhouston said:
I've just tried the up + power but when I do it displays the menu options i.e. Apply sdcard:update.zip and wipe data/factory reset; however, it has a yellow message below saying E:Can't open /cache/recovery/command ..... should I be concerned?
Yes I flashed the bravo_downgrade.img located at http://alpharev.nl/ by doing it via the SD card. Currently I can't connect to my phone via adb
Click to expand...
Click to collapse
That error always comes up on stock recovery I think. It always did for me anyway.
I'd be tempted to factory reset then run an RUU again.

rootSU said:
That error always comes up on stock recovery I think. It always did for me anyway.
I'd be tempted to factory reset then run an RUU again.
Click to expand...
Click to collapse
That's ok then. Do you have any recommended RUUs? My phone was bought unbranded and unlocked

If truly unbranded 2.29.405.5
Sent from my HTC Desire using XDA App

smhouston said:
That's ok then. Do you have any recommended RUUs? My phone was bought unbranded and unlocked
Click to expand...
Click to collapse
I've just tried the following RUU after doing a factory reset:
RUU_Bravo_HTC_Europe_1.15.405.3_Radio_32.30.00.28U_4.05.00.11_release_121865
However when going through the instructions it said that my current image is:
2.29.405.5
I proceeded anyway by pressing Update, and it ended up with the following error:
ERROR[140]: BOOTLOADER VERSION ERROR
From what I've quickly googled, it sounds like I got that error because the RUU I was trying to install was less than the one currently installed? If so then how can I get one that is newer as I can't see any newer ones than that!
EDIT: I'll try using the one you suggested again

If it starts with a 1 its android 2.1. You do not want that. It must start with a 2 at least
Sent from my HTC Desire using XDA App

rootSU said:
If it starts with a 1 its android 2.1. You do not want that. It must start with a 2 at least
Sent from my HTC Desire using XDA App
Click to expand...
Click to collapse
Wahey, you'll be pleased to know it's worked! Thank you all for your time and patience with me. Got to admit I thought I was doomed!

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