Related
got my evo about a month ago. rooted lastnight since unrevoked finally pushed out their 3.3 version which is updated for my version of hboot (2.02). the root went very smoothly. i installed the latest cyanogenmod rom, only to discover there was no market or gmail app with the rom! wish i had known that before. after doing some research online, i found out i needed to flash or install a "gapps" apk. so, looked around for that for a couple hours and couldn't find it. i downloaded what i thought would be the right .zip file to get the market on my phone (a vending.apk that was listed in another thread having to do with this same issue). so anyway... downloaded that, moved it to the root of my sd card, flashed it through clockworkmod recovery (by the way, everything up until this point was perfect) and finally rebooted my phone... only it never rebooted. the white htc EVO 4G screen was there. then, black screen, as if it was about to begin the cyanogenmod boot screen and fully boot. but, no. it went from white evo screen to black screen... to OFF. after this, i couldn't even turn it on to get it into hboot or access recovery. tried to do that for two hours. and finally i was able to get in... so i tried doing a factory/data reset through recovery, then a cache clear, then reboot. nothing. same thing. went back into recovery, tried reflashing cyanogenmod rom again. nothing. tried flashing myn's rom. nothing. all i get is installation aborted.
i am pretty sure that this is not a complete brick since i am now able to access hboot and recovery. but if i can't flash anything... and i'm stuck in hboot and recovery and cant boot my phone... what the hell do i do now? please help me figure this out!! anybody have any good advice or a known fix...??
Boot into recovery. Do a factory reset. then wipe cache and dalvik catch. Re flash cynagon and let it boot. You then need to find gapps.zip. Boot into recovery flashing gapps.zip.
i did all that. step by step. and when i reflashed the rom, that is when it wouldn't install, saying installation aborted. but, i'm gonna do it again. let's see if my phone wants to play nice now...
brtnygrey said:
i did all that. step by step. and when i reflashed the rom, that is when it wouldn't install, saying installation aborted. but, i'm gonna do it again. let's see if my phone wants to play nice now...
Click to expand...
Click to collapse
If that does not work! you are going to have to update with sprint lovers rom, that is in a PCM36IMG.ZIP. Install it by holding the _vol and th power button, boot into boot loader, than it will search for the zip file and ask you if you want to update, say yes ans just weigh for it to be done. Its going to take few minutes first boot! just hold on. I hope this helps in anyway.
evolishesh said:
If that does not work! you are going to have to update with sprint lovers rom, that is in a PCM36IMG.ZIP. Install it by holding the _vol and th power button, boot into boot loader, than it will search for the zip file and ask you if you want to update, say yes ans just weigh for it to be done. Its going to take few minutes first boot! just hold on. I hope this helps in anyway.
Click to expand...
Click to collapse
do you think that sprintlovers rom will install even if no other rom will install? because... i was able to install Gapps.zip file just fine. but every rom i install is unsuccessful.
brtnygrey said:
do you think that sprintlovers rom will install even if no other rom will install? because... i was able to install Gapps.zip file just fine. but every rom i install is unsuccessful.
Click to expand...
Click to collapse
The springlovers rom gets flashed the same way sprint flashes there upgrades so it should
Sent from my SPH-D700 using Tapatalk
mysteryemotionz said:
The springlovers rom gets flashed the same way sprint flashes there upgrades so it should
Sent from my SPH-D700 using Tapatalk
Click to expand...
Click to collapse
ok is the install through recovery supposed to be almost instantaneous? it didn't take a minute like every other rom. and after reboot (10 minutes ago) i'm still sitting on the white htc EVO 4G screen. i don't think this is working either. but i really do appreciate your help. any other suggestions? is there anything else through recovery that I can do (since i cant make it past that) that might fix my system? anything in partition? i'm so stuck!
mysteryemotionz said:
The springlovers rom gets flashed the same way sprint flashes there upgrades so it should
Sent from my SPH-D700 using Tapatalk
Click to expand...
Click to collapse
and also... when i go into hboot, and it runs through the "checking sd" thing before i can select options... it says "no image or wrong image". what?
Nothing is working!!
Did you try a rooted RUU yet?
http://forum.xda-developers.com/wiki/index.php?title=HTC_Supersonic/ROMs
Wipe everything twice first (just to be safe). Are you using Amon RA or Clockwork, by the way? The only other thing I can think of would be that your SD card isn't formatted properly, but that would have to mean you intentionally formatted it or put in a new one that didn't have the right files on it.
SilverZero said:
Did you try a rooted RUU yet?
http://forum.xda-developers.com/wiki/index.php?title=HTC_Supersonic/ROMs
Wipe everything twice first (just to be safe). Are you using Amon RA or Clockwork, by the way? The only other thing I can think of would be that your SD card isn't formatted properly, but that would have to mean you intentionally formatted it or put in a new one that didn't have the right files on it.
Click to expand...
Click to collapse
i am using clockwork. i've wiped so many times... but i can't make anything happen. and, i did format the sd card eventually, but not until a couple of hours ago... and only as a last resort because nothing else worked and i've been trying to fix this since last night, so i figured it couldn't hurt. but if that is part of the problem... how can i fix it? thanks for your response. i don't know what else to do other than take it in for a switch.l but if i can get into hboot... then sprint can too... and they will see that i'm rooted and void warranty. so am i completely screwed?
I had same issue.
I just reflashed the sprintlover rom (PC36IMG.ZIP) which came with Amon_RA recovery.
Then i installed the CM6 with Amon_RA recovery and everything works fine now.
Good that i did Titanium backup few days before
This is happening to me too. Almost everything he's describing is the same. Except I installed a gapps.zip and then it wouldn't boot after that. No matter what I flash, it either gives me a status 7 error and aborts the install or it may "install successfully" but it never boots. Also tried the pc36img.zip as well. I had a nandroid backup and tried to restore that, but that aborts saying cannot flash boot image. Tried a rooted and also an unrooted stock ruu, they won't work and the .exe version on a pc can't find my phone when I plug it in and power it on. Anyone have any Ideas for me. I can get more specific error messages and hboot numbers, etc. if needed.
I think you should get Amon recovery PCIMG zip file and change recovries and try everything again... IMO
Edit: I posted the Amon file and all you have to do is rename it to PCIMG.zip. Also I think the gapps you were looking for you can find on the cm site itself or within that thread. Sorry if it sounds like I a being negative but I see alot of people get on noob and I wondered why but unfortunately its because things like this happen. In the OP for CM6 it says to use Amon and backup your keys. Now if you get your phone backup you got to first check and make sure your RSA keys are in tact unless you backed them up already.
Joeykrim has a app on the market to check or there are numerous threads on what to do. Sorry and hope it works out for you if not INS is your friend
View attachment PC36IMG-Amon-V2.2.1.zip
playya said:
I think you should get Amon recovery PCIMG zip file and change recovries and try everything again... IMO
Click to expand...
Click to collapse
some people dont like clockwork with the evo's...thats just the general feeling im getting from the boards. i just got my evo rooted and what not. i use clockwork and it has worked well for what i need.
op, try amon like has been suggested.
tailsthecat3 said:
some people dont like clockwork with the evo's...thats just the general feeling im getting from the boards. i just got my evo rooted and what not. i use clockwork and it has worked well for what i need.
op, try amon like has been suggested.
Click to expand...
Click to collapse
Yea but have you tried Amon and from what I read and this is from developers Amon has a much better handle on things as far as backing stuff up, partitions and protection of keys.
I ran Clockwork on my wifes phone because to me its simple and works with Rom manager but after a while I just said F it and switched since it was messing up my backups. Hey to each his own..
Ok, I don't believe that your device is bricked. You may have flash the wrong gapps or something, but is should be easy to fix.
First, download these 3 files and put them on the root of your SD card:
Cyanogen 6 stable for evo
Latest gapps for HDPI
Calkulin's format all
Red through first, then follow my instructions EXACTLY:
1.) Boot into recovery.
2.) Flash Calkulin's all format. This will wipe everything that needs wiping. (everything but the SD card)
3.) Without exiting recovery immediately flash the CM6 .zip. Do not flash the gapps yet.
4.) Reboot the device now. It will boot into cyanogen, but will not have market or anything. Once fully booted, reboot to recovery.
5.) Do not wipe or anything, just flash the gapps HDPI.
6.) Boot the phone and enjoy.
Evo won't load any roms, can only get into clockwork recovery
Okay, so if I try your steps, just like before The install gets almost to the end, then I get:
"assert failed: write_raw_image ("/tmp/boot.img","boot")
E:Error in /sdcard/update-cm-6.1.2-supersonic-signed.zip
(Status 7)
Installation aborted.
Sorry Playya, I wanted to try this one more time first. I'm going to try loading Amon Ra now. do I need to rename it to pcimg.zip or should i just flash the current file name?
In case it helps anyone, I have
ClockworkMod Recovery v2.5.0.1
my boot loader screen shows
SUPERSONIC EVT3 SHIP S-OFF
HBOOT-2.10.0001
MICROP-041f
TOUBH PANEL-ATMELC03_16ac
RADIO-2.15.00.11.19
Oct 15 2010
Awesome, Amon Ra Worked, and now i'm up and running on cyanogen mod with google apps as well. My only problem now, is I can't backup, when I try it says oops... something went wrong! Please check the recovery log!
hcavlnch said:
Awesome, Amon Ra Worked, and now i'm up and running on cyanogen mod with google apps as well. My only problem now, is I can't backup, when I try it says oops... something went wrong! Please check the recovery log!
Click to expand...
Click to collapse
it may say oops if you battery level is low... I think Amon is so much better its just that Unrevoked puts Clockwork in with their root so people get lazy and leave it in... Amon - its the way to go.
1. Charge your battery and try again
2. Backup your wimax keys - then check how big the file is and hopefully its like 12 megs... If so keys may be ok
Good evening,
before I start:
HTC Desire HD
Orange Branded
Clockwordmod Recovery
I was out and about today when I recieved a nice message telling me there was a system update to download and install. I got within WiFi signal and downloaded it. when I tried to run it, it kept hanging on the ClockwordMod (CWM) Recovery page. First it told me that it couldn't mount the SD card where the update was stored. So I mounted the SD card through CWM and tried again. This time it told me that it couldn't be verified. So I turned that off too. Then it told me something else didn't work so I disabled that (sorry, I can't remember but it begins with 'A'). I tried a final time to install the update but it wouldn't work still.
Then the phone wouldn't load. It just hung on the HTC white screen for about ten mins with no movement.
I removed the battery, reloaded by pressing Vol Down + On. I have tried every menu item but the loader tells me that an image (beginning with P****.zip) is missing. It lets me load the clockworkmod recovery page so I have tried to restore a backup that I made about a week ago. It restored it, (or so it said) but when I then told it to reload it still hangs on the HTC white screen.
It's now been hanging for ten mins and I'm just leaving it.
Does it just need to be left for a long time to reload from the HTC white screen?
If it does not reload, how can I get it to?
Many thanks for your impending help!
You havent bricked your phone, a bricked phone wont power on! For future reference, remember, you cannot flash an ota update with a custom recovery installed. As you have found out it messes your device up. Ok you have 2 options.
1. Try a full wipe from the mounts and storage menu. Then try to restore your backup.
2. Flash a custom rom from recovery.
Sent from my Desire HD using Tapatalk
AndroHero said:
You havent bricked your phone, a bricked phone wont power on! For future reference, remember, you cannot flash an ota update with a custom recovery installed. As you have found out it messes your device up. Ok you have 2 options.
1. Try a full wipe from the mounts and storage menu. Then try to restore your backup.
2. Flash a custom rom from recovery.
Click to expand...
Click to collapse
I really thought restoring my backup would have done it.
I now need to try a custom rom.
AndroHero said:
You havent bricked your phone, a bricked phone wont power on! For future reference, remember, you cannot flash an ota update with a custom recovery installed. As you have found out it messes your device up. Ok you have 2 options.
1. Try a full wipe from the mounts and storage menu. Then try to restore your backup.
2. Flash a custom rom from recovery.
Sent from my Desire HD using Tapatalk
Click to expand...
Click to collapse
Would you happen to know where I can get the Orange ACE Rom from?
I've tried to install the Cyanogen Mod but that has got me no further.
I downloaded the most uptodate build of Cyanogen Mod (7) and copied it to my SD Card.
Through ClockworkMod Recovery I installed Cyanogen Mod and it told me that it had been successful. I restarted the phone and it got past the HTC white screen.....
I was very excited until it is not sat here on the Cyanogen Mod screen which just loads over and over again repeatedly.
Any other ideas please? I suspect I need the Orange ACE Stock Rom....is it available?
did you wipe your phone before trying to flash the new roms as AndroHero suggested?
if not try that first (you can do it via clockwork recovery or via easy full wipe from mero01 -> http://forum.xda-developers.com/showthread.php?t=868720)
-shadeless- said:
did you wipe your phone before trying to flash the new roms as AndroHero suggested?
if not try that first (you can do it via clockwork recovery or via easy full wipe from mero01 -> http://forum.xda-developers.com/showthread.php?t=868720)
Click to expand...
Click to collapse
yes, the only thing I didn't wipe was the SD card because that's where the rom / backup is stored. Do i need to completely wipe that then put the backup back on there?
as far as i know, it shouldn't be necessary. but i'm not really sure, sorry.
you could try formatting your sd card, wouldn't hurt, but maybe it would be better to wait for someone with more knowledge about android than me.
-shadeless- said:
as far as i know, it shouldn't be necessary. but i'm not really sure, sorry.
you could try formatting your sd card, wouldn't hurt, but maybe it would be better to wait for someone with more knowledge about android than me.
Click to expand...
Click to collapse
Thanks for your help so far. I am trying everything. If I could find the actual Orange Stock Rom (Ace) then I might get somewhere. I don't want to install a custom rom if not necessary.
EDIT: I have found an Orange Stock Rom (RUU). How do i install it?
I can only get to the bootloader screen so do I plug the USB cable in at this point and run the RUU from the PC once the drivers have installed? Do I put the RUU on the SD card and somehow run it from there?
i think this is the newest stock rom : http://forum.xda-developers.com/showthread.php?t=969374&highlight=orange+rom
but as AndroHero already mentioned, i think you can't flash stock RUUs with cwm recovery.
p.s. did you give easy wipe from the link from my previous post a try ?
-shadeless- said:
i think this is the newest stock rom : http://forum.xda-developers.com/showthread.php?t=969374&highlight=orange+rom
but as AndroHero already mentioned, i think you can't flash stock RUUs with cwm recovery.
p.s. did you give easy wipe from the link from my previous post a try ?
Click to expand...
Click to collapse
I must admit that i've not yet tried the Easy Wipe. At the moment I am downloading an older stock Rom (the one that was on there before this happened) and am following some other instructions to extract the PD98IMG.ZIP which appears to be missing.
I DID go through CWM to competely wipe everything with the exception of the SD card and i managed to almost get CyanogenMod working....it would work for about 20seconds before reloading again....very strange. It has given me hope though. I tried wiping everything before doing the restore of my original backup but still nothing.
the download is taking ages so I'll give easy wipe a go.....wait....
SOLVED
thank you for all who helped.
I solved this problem by downloading an older Orange Stock Rom from the link above. After that, I followed instructions in: http://forum.xda-developers.com/showthread.php?t=841890 and reinstalled the rom.zip that it mentions. Sure enough, I am back to where I started about 3 weeks ago but because everything was backed up to the cloud I really don't mind at all. Sure, I have to root it with VISIONary again to remove all the apps that Orange have stuffed in but I can cope with that.
In fact, the worst thing is that I completed Angry Birds and Angry Birds Seasons and now i have no proof!!
Thanks again all.
glad that you could finally solved it!
i, too just lost all my angry birds saves because i just downgraded so that i could root my dhd
If this has been asked before then please forgive me...
I can not go back to any backup I had of CM7 or Gingerbread Sense ROM since upgrading to some Alpha ICS roms. I've tried wiping everything & started from scratch on these roms but I always get stuck at "failed to write boot partition from /tmp/boot.img" It doesn't matter what Gingerbread ROM I choose with the exception of MIUI rom (don't know why). I thought maybe I could use that as a stepping stone to go back from there but nogo. I've used RA's recovery & CWM with no success. Any ideas?
davidnjessicacruz said:
If this has been asked before then please forgive me...
I can not go back to any backup I had of CM7 or Gingerbread Sense ROM since upgrading to some Alpha ICS roms. I've tried wiping everything & started from scratch on these roms but I always get stuck at "failed to write boot partition from /tmp/boot.img" It doesn't matter what Gingerbread ROM I choose with the exception of MIUI rom (don't know why). I thought maybe I could use that as a stepping stone to go back from there but nogo. I've used RA's recovery & CWM with no success. Any ideas?
Click to expand...
Click to collapse
I would recommend tracking down calkulins format zip for the evo
1brainsurgeon said:
I would recommend tracking down calkulins format zip for the evo
Click to expand...
Click to collapse
Yeah... tried that already... Didn't fix it...
davidnjessicacruz said:
If this has been asked before then please forgive me...
I can not go back to any backup I had of CM7 or Gingerbread Sense ROM since upgrading to some Alpha ICS roms. I've tried wiping everything & started from scratch on these roms but I always get stuck at "failed to write boot partition from /tmp/boot.img" It doesn't matter what Gingerbread ROM I choose with the exception of MIUI rom (don't know why). I thought maybe I could use that as a stepping stone to go back from there but nogo. I've used RA's recovery & CWM with no success. Any ideas?
Click to expand...
Click to collapse
I can say with certainty that I don't have this problem. I've flashed every ROM from here to Timbuktu, AOKP, Deck's, Evervolv, and have had no problem restoring a nandroid of, or flashing MikG, Mik3D, MikRunny, The Express, or any other ROM I may have forgotten.
That boot partition error doesn't sound good, though. What HBOOT version do you use?
Captain_Throwback said:
I can say with certainty that I don't have this problem. I've flashed every ROM from here to Timbuktu, AOKP, Deck's, Evervolv, and have had no problem restoring a nandroid of, or flashing MikG, Mik3D, MikRunny, The Express, or any other ROM I may have forgotten.
That boot partition error doesn't sound good, though. What HBOOT version do you use?
Click to expand...
Click to collapse
HBOOT 0.97 is what I'm still using... never upgraded... should I & how do you recommend that I do so?
davidnjessicacruz said:
HBOOT 0.97 is what I'm still using... never upgraded... should I & how do you recommend that I do so?
Click to expand...
Click to collapse
No reason to upgrade - just wondering.
I'd recommend you flash a stock ROM in the bootloader - that should normalize everything, and then try those other ROMs again.
Captain_Throwback said:
No reason to upgrade - just wondering.
I'd recommend you flash a stock ROM in the bootloader - that should normalize everything, and then try those other ROMs again.
Click to expand...
Click to collapse
I assume your talking about in the recovery (aka amon ra/ clockworkmod), if so then I've tried that as well. Same issue.... This is not sounding good for me.
davidnjessicacruz said:
I assume your talking about in the recovery (aka amon ra/ clockworkmod), if so then I've tried that as well. Same issue.... This is not sounding good for me.
Click to expand...
Click to collapse
I believe he's talking about a RUU
Sent from my PC36100 using XDA App
evo4gnoob said:
I believe he's talking about a RUU
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
The stock one? Wow... don't even know how to flash that back.... hmm... I'll see if I can find it here, if not then I'll google it. I'll keep you informed.... hopefully bricking does not ensue.... any help here would be great as well
davidnjessicacruz said:
The stock one? Wow... don't even know how to flash that back.... hmm... I'll see if I can find it here, if not then I'll google it. I'll keep you informed.... hopefully bricking does not ensue.... any help here would be great as well
Click to expand...
Click to collapse
In the first "My Links" link in my sig, there are 3 of them.
They're PC36IMG files - you rename the file to exactly that - PC36IMG.zip - and put the file on the root of your sd card. Then you reboot your device into bootloader (HBOOT) mode. From a powered off state, hold the Volume down button and then press and hold the power button until you see the HBOOT screen. The file should be recognized and loaded, and after a minute or so it will ask you to update. Press Volume Up to accept, and then wait for a while.
NOTE: This will upgrade your HBOOT, but that's no big deal. The phone will reboot into the bootloader once near the beginning of the process by itself - that is also okay. Don't touch anything while it's updating.
At the end of the process, you'll need to find a PC36IMG for your preferred recovery (RA-supersonic-v2.3 recommended), which you will flash the same way as the ROM (in fact, you can replace the ROM file with the recovery file - unless you want to hold on to it, then you can just move or rename it).
Captain_Throwback said:
In the first "My Links" link in my sig, there are 3 of them.
They're PC36IMG files - you rename the file to exactly that - PC36IMG.zip - and put the file on the root of your sd card. Then you reboot your device into bootloader (HBOOT) mode. From a powered off state, hold the Volume down button and then press and hold the power button until you see the HBOOT screen. The file should be recognized and loaded, and after a minute or so it will ask you to update. Press Volume Up to accept, and then wait for a while.
NOTE: This will upgrade your HBOOT, but that's no big deal. The phone will reboot into the bootloader once near the beginning of the process by itself - that is also okay. Don't touch anything while it's updating.
At the end of the process, you'll need to find a PC36IMG for your preferred recovery (RA-supersonic-v2.3 recommended), which you will flash the same way as the ROM (in fact, you can replace the ROM file with the recovery file - unless you want to hold on to it, then you can just move or rename it).
Click to expand...
Click to collapse
Failed on #4 Boot.... it stated "failed - PU" "Partition failed" Fun times.... Now the phone is a brick (stuck at the white screen).... Where there is a will then there is a way so I'll find a way.... any help would be appreciated though....
Sooo... I was able to flash back my alternate recovery using a PC36IMG version of it. Thank god for the rooted community.... Restoring back my last backup. Funny though, that I still could not restore a rooted stock backup I had or a new upgraded .zip that I wanted to use. Common denominator in all this (even when trying to use the 4.24.651.1 version of the stock software PC36IMG), it can not write the boot.img Any one else had this problem? Next I will try to RUU which will technically make me lose root but I should be able to get it back, assuming I'm successful, since I still have S-OFF.
PS: My HBOOT now, btw, is 2.16.0001 so I know that the original attempt to get back to gingerbread was succesful
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
Hey Guys Thank You For Taking A Look At My Thread.Lets Cut To The Chase.I Have A HUGE PROBLEM with my Replacement Incredible 2.I Rooted my phone with Tacoroot,and everything was fine.Flashed Condemed CM7.2 and started realizing i didn't like it as much,so i made a BACKUP just in case i wanted to return to the CM goodness.Went to TSMTrinity's Sense 2.1 Version 4.5 S,and here's where the problem started happening. After I set up everything on my Sense 2.1 ROM,i backed it up,the screen would get to the boot animation,get past the boot animation,id see my lock screen for 1 SECOND,and then it would start the bootup again.seeing as this was a problem,i WIPED All Cache and Factory Reset/Wipe Data on My Revolutionary Recovery.Then,I Restored the 2.1 Backup that i created and everything was fine again.Then again,i decided to Flash Mikrunny's Sense 3.5 ROM,which after i set up,worked fine,UNTIL YESTERDAY.I was driving in my car yesterday,listening to music on The STOCK HTC Music app on Sense 3.5,and the phone rebooted on its own.And it would not stop until i took the battery out.I got home,charged the battery for a bit,(shut down that is),then headed to recovery.I took out the SD card and rebooted the phone,but no luck.tried this rebooting process for an hour,until i decided to wipe cache and factory reset to my 2.1 ROM BACKUP.it works,but i just wanna know,am i doing something noobingly wrong when backing up and restoring roms? Also,i use Revolutionary's Backup,or I think its called Nandroid,to do backups and restores,and ROM MANAGER to edit their names and delete them.Also,an added side to his problem,when i boot to the Hboot screen,when it loads,for a few of the items it says,missing or wrong image.could that be the problem?? THANK YOU SO MUCH WHO REPLIES AND HELPS.:crying:
DroidUser_Wind said:
Hey Guys Thank You For Taking A Look At My Thread.Lets Cut To The Chase.I Have A HUGE PROBLEM with my Replacement Incredible 2.I Rooted my phone with Tacoroot,and everything was fine.Flashed Condemed CM7.2 and started realizing i didn't like it as much,so i made a BACKUP just in case i wanted to return to the CM goodness.Went to TSMTrinity's Sense 2.1 Version 4.5 S,and here's where the problem started happening. After I set up everything on my Sense 2.1 ROM,i backed it up,the screen would get to the boot animation,get past the boot animation,id see my lock screen for 1 SECOND,and then it would start the bootup again.seeing as this was a problem,i WIPED All Cache and Factory Reset/Wipe Data on My Revolutionary Recovery.Then,I Restored the 2.1 Backup that i created and everything was fine again.Then again,i decided to Flash Mikrunny's Sense 3.5 ROM,which after i set up,worked fine,UNTIL YESTERDAY.I was driving in my car yesterday,listening to music on The STOCK HTC Music app on Sense 3.5,and the phone rebooted on its own.And it would not stop until i took the battery out.I got home,charged the battery for a bit,(shut down that is),then headed to recovery.I took out the SD card and rebooted the phone,but no luck.tried this rebooting process for an hour,until i decided to wipe cache and factory reset to my 2.1 ROM BACKUP.it works,but i just wanna know,am i doing something noobingly wrong when backing up and restoring roms? Also,i use Revolutionary's Backup,or I think its called Nandroid,to do backups and restores,and ROM MANAGER to edit their names and delete them.Also,an added side to his problem,when i boot to the Hboot screen,when it loads,for a few of the items it says,missing or wrong image.could that be the problem?? THANK YOU SO MUCH WHO REPLIES AND HELPS.:crying:
Click to expand...
Click to collapse
1..update your recovery which is probly clockwork mod....i suggest you get your phone usable for a few minutes and go to 4ext.net and download and install that..its touch based recovery or also check out twrp if you want an alt if you dont like it
2....update your radio ...newest one can be found in the venom rom thread i think there are directions there http://forum.xda-developers.com/showthread.php?t=1953899
3.....wipe everything ....check out my wipe script in the dev section if you want max cleanification http://forum.xda-developers.com/showthread.php?t=2013242
4...flash what ever rom...if you like sense use viper i hear good things or check out my incredibly paranoid rom or all the other roms ..pick your poison
chillybean said:
1..update your recovery which is probly clockwork mod....i suggest you get your phone usable for a few minutes and go to 4ext.net and download and install that..its touch based recovery or also check out twrp if you want an alt if you dont like it
2....update your radio ...newest one can be found in the venom rom thread i think there are directions there http://forum.xda-developers.com/showthread.php?t=1953899
3.....wipe everything ....check out my wipe script in the dev section if you want max cleanification http://forum.xda-developers.com/showthread.php?t=2013242
4...flash what ever rom...if you like sense use viper i hear good things or check out my incredibly paranoid rom or all the other roms ..pick your poison
Click to expand...
Click to collapse
DUDE.THANK YOU so MUCH FOR REPLYING.Ill try what you told me tonight,and ill let you know how it goes down.thanks again chills.:good:
chillybean said:
1..update your recovery which is probly clockwork mod....i suggest you get your phone usable for a few minutes and go to 4ext.net and download and install that..its touch based recovery or also check out twrp if you want an alt if you dont like it
2....update your radio ...newest one can be found in the venom rom thread i think there are directions there http://forum.xda-developers.com/showthread.php?t=1953899
3.....wipe everything ....check out my wipe script in the dev section if you want max cleanification http://forum.xda-developers.com/showthread.php?t=2013242
4...flash what ever rom...if you like sense use viper i hear good things or check out my incredibly paranoid rom or all the other roms ..pick your poison
Click to expand...
Click to collapse
What OP wrote applies to me as well. I am looking for something better than aerovan's CM9 (which has been my DD), and thought I would give Viper a try. Without fail, bootlooping (which I could have guessed since I did tacoroot and this seems to be an issue with sense based roms).
That said, I tried steps 1 through 4 and the bootlooping stopped in Viper - it goes through startup and just shuts down before leaving the boot screen. One strange thing that I noticed is that the ICS Firmware/radio with Viper (which I loaded in CWM), wouldn't load in 4ext. Maybe I'll give paranoid a go if I can't resolve this bootlooping issue in Viper! I hope OP has better luck.
U don't flash radio in cwm..look for a how to.. can't explain I'm working sry
Sent from my Incredible 2 using xda app-developers app
I'm not as knowledgeable as Chilly, but a thought did occur to me. if the cm9 rom included a kernel on the flash and then you went to a sense based rom that didn't include a kernel that could cause a problem. I believe that I read that cm using a kernel that is asop based while sense roms use a different based kernel. You may check to see what kernel you have and then check for the recomended kernel for that rom and flash that kernel. don't forget to wipe.
Jasonp0 said:
I'm not as knowledgeable as Chilly, but a thought did occur to me. if the cm9 rom included a kernel on the flash and then you went to a sense based rom that didn't include a kernel that could cause a problem. I believe that I read that cm using a kernel that is asop based while sense roms use a different based kernel. You may check to see what kernel you have and then check for the recomended kernel for that rom and flash that kernel. don't forget to wipe.
Click to expand...
Click to collapse
All of the roms come with a kernel for our phone, but certainly, don't flash a sense kernel with aosp or vice versa after rom flash. Chilly is right. Flashing a newer radio should fix the problem and the radio is flashed with a PG32IMG.zip in the bootloader, not in the recovery.
gtdtm said:
All of the roms come with a kernel for our phone, but certainly, don't flash a sense kernel with aosp or vice versa after rom flash. Chilly is right. Flashing a newer radio should fix the problem and the radio is flashed with a PG32IMG.zip in the bootloader, not in the recovery.
Click to expand...
Click to collapse
Good call. When chilly said you don't flash kernels in recovery I hit my head. I flashed the radio, but now my challenge is getting back into recovery since I renamed the file and bootloader always finds it and wants to reboot or I load CM9 which stays on flash screen. I'll figure something out, maybe with adb. Thanks.
Power down, pop the sd out, boot to recovery, rename file, profit.
gtdtm said:
Power down, pop the sd out, boot to recovery, rename file, profit.
Click to expand...
Click to collapse
Didn't think of that. adb did the trick though. In business with VenomInc!
Thank you all.
digitalshepard said:
Didn't think of that. adb did the trick though. In business with VenomInc!
Thank you all.
Click to expand...
Click to collapse
good lucking going back to aosp lol
almost thesame problem
chillybean said:
U don't flash radio in cwm..look for a how to.. can't explain I'm working sry
Sent from my Incredible 2 using xda app-developers app
Click to expand...
Click to collapse
i made a stupid mistake of flashing radio in recovery, in fact the radio is for Samsung at&t and now my phone vibrates it doesnt show htc quietly brilliant, only vibrates and orange light with black screen untill i pull out the battery... i was able to return to stuck and it can only boot if its connected to power, it doesn't read sd card while android is booted and in recovery to, only in bootloader it reads sd... error in mounting if i try to... i flashed RUU.exe 2.3.3 and 2 other RUUs for my droid inc 2 but it keeps vibrating... please help me!!! thanks
I made the same mistake when i first gained s-off for my dinc2. the thing with the venom rom tho is if you ever want to go back to aosp ull need to gets chill's anti-venom zip and flash it through recovery because doing a normal wipe wont do the trick. also a helpful trick that worked for me with roms if i ever start getting boot loops i go into recovery from the bootloader menu and i wipe the dalvik cache under advanced and then wipe the chache under mounts and storage and it always works like a charm for me. but ive also learned that you have to be careful which kernel you flash with the rom of your choice because not only will it cause lags if you happen to get past the boot animation to the main screen but in some cases it can cause breaks in your framework like your wifi data etc. im not an expert tho those are just suggestions that im familiar with because theyve already happened to me before. hope this helps in any way.