Uhhhh Ohhhh... EVO repeatedly rebooting - EVO 4G Q&A, Help & Troubleshooting

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

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

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

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

Uhhhh Ohhhh wrong section

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

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

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

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

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

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

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

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

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

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

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

Related

few noob questions after finally rooting

Hey guys, long time lurker, first time poster.
I finally gave in and fully rooted my EVO and successfully flashed the newest damagecontrol rom. Afterwards, I took some time and set up my phone like how it used to be with the apps, settings, etc. Just a few questions from after this.
If I wanted to flash a different ROM, it is recommended to do a data wipe, correct? And also a NAND backup. Does this mean that my phone will be reset to factory settings again - using the new ROM as a base? In other words, would I have to rearrange my screens, settings, etc. if I wanted to try out a new ROM?
If not a different ROM, but an updated version of my current ROM, do I just flash that on top of what I have? (i.e. DC4.0 is released, do I have to wipe everything again before upgrading?)
If the answer is yes to both these questions, what are the easiest/quickest ways to get my phone looking/acting the way I like when getting a new ROM?
also, I followed toast's method step by step, and got the Amon Ra recovery on my phone as well. What is the function of this? Sorry for all the questions, I have everything working fine, but I'm just curious as to what and how things work on the phone. What is the difference between the amon ra recovery and following steps to use clockword for recovery?
Thanks a lot
baxtercat said:
Hey guys, long time lurker, first time poster.
I finally gave in and fully rooted my EVO and successfully flashed the newest damagecontrol rom. Afterwards, I took some time and set up my phone like how it used to be with the apps, settings, etc. Just a few questions from after this.
1. If I wanted to flash a different ROM, it is recommended to do a data wipe, correct? And also a NAND backup. Does this mean that my phone will be reset to factory settings again - using the new ROM as a base? In other words, would I have to rearrange my screens, settings, etc. if I wanted to try out a new ROM?
2. If not a different ROM, but an updated version of my current ROM, do I just flash that on top of what I have? (i.e. DC4.0 is released, do I have to wipe everything again before upgrading?)
If the answer is yes to both these questions, what are the easiest/quickest ways to get my phone looking/acting the way I like when getting a new ROM?
Click to expand...
Click to collapse
baxtercat said:
also, I followed toast's method step by step, and got the Amon Ra recovery on my phone as well. What is the function of this? Sorry for all the questions, I have everything working fine, but I'm just curious as to what and how things work on the phone. What is the difference between the amon ra recovery and following steps to use clockword for recovery?
Thanks a lot
Click to expand...
Click to collapse
Hello there, iv done videos on this rom for youtube, if you want the links let me know but ill go as it follows.
Ok, if you want to test out new roms, just do a nand backup of the one you have now, after that. WIPE both Factory and Delvic cache. Then flash the new rom in your phone adn you will be fine.
Ok, i know DC does this, i dont know about the others yet, But if a new update comes out, just flash that DC update over yours and it will be fine. All user data will be there. YOU shouldn't have boot loop ether. If so, then you will have to wipe again. I didn't and im fine. ( I use fresh evo right now. loving it. )
As for the NAND backup. This saves EVERYTHING so once you are tired of a old rom and wanna try another, just restory the back up and your fine.
super-6-1 said:
Hello there, iv done videos on this rom for youtube, if you want the links let me know but ill go as it follows.
Ok, if you want to test out new roms, just do a nand backup of the one you have now, after that. WIPE both Factory and Delvic cache. Then flash the new rom in your phone adn you will be fine.
Ok, i know DC does this, i dont know about the others yet, But if a new update comes out, just flash that DC update over yours and it will be fine. All user data will be there. YOU shouldn't have boot loop ether. If so, then you will have to wipe again. I didn't and im fine. ( I use fresh evo right now. loving it. )
As for the NAND backup. This saves EVERYTHING so once you are tired of a old rom and wanna try another, just restory the back up and your fine.
Click to expand...
Click to collapse
Wow, thanks for the quick reply! That cleared up a lot of things for me.
So if I have everything set up the way I want, it is recommended to do a NAND backup at this point?
Also, what are the pros/cons of using Rom Manager (marketplace)?
Thanks a lot
baxtercat said:
Wow, thanks for the quick reply! That cleared up a lot of things for me.
So if I have everything set up the way I want, it is recommended to do a NAND backup at this point?
Also, what are the pros/cons of using Rom Manager (marketplace)?
Thanks a lot
Click to expand...
Click to collapse
well if i was you, wait till you wanna flash something else THEN do a nand back up.
as far as rom manager goes, i dont use it. I just come on here and see whats new and what going on, you get a lot more from here then on rom manager, Plus, its free
super-6-1 said:
well if i was you, wait till you wanna flash something else THEN do a nand back up.
as far as rom manager goes, i dont use it. I just come on here and see whats new and what going on, you get a lot more from here then on rom manager, Plus, its free
Click to expand...
Click to collapse
This is what I was thinking as well. Thanks
could you be kind enough to explain the different recovery files and their uses?
baxtercat said:
This is what I was thinking as well. Thanks
could you be kind enough to explain the different recovery files and their uses?
Click to expand...
Click to collapse
what do you mean? like the different kinds of recoverys? Really i just stay with toasts, his is more stable and as far as the clockmod one, It has issues with formatting the Factory cashe.
Honestly, for someone that is completely new to flashing roms, backing up etc., Rom Mgr. is the best thing for you. You may not have the absolute cutting edge of available roms, but it makes flashing/backing up extremely easy and straightforward. That is how I got started with my previous Droid until I felt comfortable enough to flash the old fashion way. I have literally flashed and backed up hundreds of times using clockwork mod (rom manager recovery) and have not had a single issue. Plus, the app is only a couple bucks if I remembe correctly. I would start there to gain some experience, then move on to flashing zips from here.
just my opinion.
Will rom manager work if I have Amon RA's Recovery?
I think it may replace your recovery

What do I do now?

Okay, first timer here and I have a few questions. I just completed rooting my phone via Simple Root. My build number is now 1.17.651.1.
My questions are as follows:
1) Now that I am rooted, what installation files can I delete from my SD Card?
2) I see that I need to do a recovery flash, do I do this immediately? What one do you recommend?
3) After I do the flash, are there any others files I need to install before I do a custom rom?
4) Which custom rom do you recommend?
5) Am I leaving anything else out that I forgot?
Thank you so much in advance!
SHicks18 said:
Okay, first timer here and I have a few questions. I just completed rooting my phone via Simple Root. My build number is now 1.17.651.1.
My questions are as follows:
1) Now that I am rooted, what installation files can I delete from my SD Card?
2) I see that I need to do a recovery flash, do I do this immediately? What one do you recommend?
3) After I do the flash, are there any others files I need to install before I do a custom rom?
4) Which custom rom do you recommend?
5) Am I leaving anything else out that I forgot?
Thank you so much in advance!
Click to expand...
Click to collapse
After you have rooted you can delete nearly anything you want, I wouldn't suggest doing it because I doubt you know what to do. But you do have the freedom to..
I would suggest you flash a recovery as soon as possible. It makes life easier. The two most common recovery are Amon Ra And clockwork.. I use amon Ra just because it had a better wipe feature but clockwork is used in rom manAger (look in to it).
After rooting you can look into upgrading your radio and your wimax and your kernal.
Custom roms are like sneakers, They all have different purpose and size. The most common ones are damagedcontrol and fresh. Do your research and experiment and find your sneaker. You can also just wait til the official stable cm6 comes out. For now I use fresh.
Try oUt some themes and different apps that are for rooted devices only. And there us always something neiw to do with your evo.
Sent from my SUPERSONIC reEVOlution using xda app
I am in the same boat as OP. I managed to make my way through SimpleRoot. But I am having a heck of a time digging through the forums to figure out what to do next. I feel like kind of an idiot, but I have no idea how to set up my backup/recovery "amon ra" right? And then I'd like to install the rooted 1.47 build and update my radio and wimax. Any direction would be VERY appreciated.
Thanks for the reply. Mind pointing me in the right direction for the radio kernel and wimax?
I'm new to this too. Read up a lot first. Easy root looks to make it pretty easy, but I learned more doing it the hard way. Used the two part method in dev section, by toast I think, with adb, nand unlock and all. Helps to understand the odd file structure, and what different parts do. You have to try things too, and just hope you don't f up. Using cm6 now and its pretty cool. Have fun man.
Sent from my PC36100 using XDA App
Liked he said read. And do a lot of it. Last thing you want is to brick your phone
Sent from my SUPERSONIC reEVOlution using xda app
gangsterholla179 said:
I would suggest you flash a recovery as soon as possible. It makes life easier. The two most common recovery are Amon Ra And clockwork.. I use amon Ra just because it had a better wipe feature but clockwork is used in rom manAger (look in to it).
Click to expand...
Click to collapse
What's wrong with Clockwork's wipe feature?
http://forum.xda-developers.com/showthread.php?t=734564&highlight=clockwork
Also, as for flashing a recovery, if you install ROM Manager from the market, it will give you an option to flash either Clockwork or Amon RA. It will stay there even if you flash new ROMs later, though there's a quirk where a new ROM Manager install will ask you to flash recovery, but then if one is already there it won't really change it, it just needs to see it to believe it.
Installing new files won't make a difference if you switch ROMs. It wipes your data when you re-flash, so you'll lose it all anyway (unless you back up your apps with Titanium Backup or MyBackup). All you need is a recovery installed - and I actually recommend Clockwork, but only because I use it myself and I have no problems with it - and you can reboot into it, install a new ROM, and start playing. I've never flashed from ROM Manager, even though it gives the option, but I imagine it does the same thing, but runs it automatically after a recovery reboot.
Read the "favorite ROM" thread with the poll attached, lots of good ROM recommendations in there. I'll say it once more: I'm using Fresh 1.0.1 and netarchy's 3.7.3c kernel (Fresh-compatible version). It's so fast and smooth.
If you like your current setup but want to try a new ROM, use ROM Manager (or Clockwork as a recovery reboot) to do a Clockwork backup. That way you can return to your current state if you want to. It's basically a system image that you can restore.
Here's one helpful page to start with.
And have fun.
Back on fresh 0.5.3, clockwork was not doing a great job with the wipe, causing the boot to loop. I believe it wasn't completely wiping the dalik cache.
Sent from my SUPERSONIC reEVOlution using xda app

[Q] Question about restoring stock ROM on Evo 4G

So, yesterday, I decided to finally jump into the abyss and try to root my Evo. Luckily, everything went completely smooth the first time (never had that happen with any other device). I was actually surprised how easy this root was.
Anyway...my question is, if I decide to flash another ROM on my phone, or rather, in 10 minutes WHEN I flash another ROM onto my phone, if I decide I don't like it, how do I reflash my original NANDROID backup back onto the phone?
I was able to navigate on my SD to where the backup was saved, but shouldn't it be a ZIP file or something? I only have individual backup files.
Also, sorry for the noob question.
Thanks in advance for your help
You go into recovery to do a nandroid restore. Its not something you flash. There is an option for backups and restore. You just run those. I like to do a full wipe before a restore though, just in case. Oh, and keep your backups in the original folder, thats where recovery will get them from
I appreciate the quick response! Thanks
No prob, hope it helped
It definitely helped to get back to the stock ROM, but now it appears as though no other ROMs are working for me. I've tried MIUI and MikFroyo, and they both get stuck in boot loops. There's something I'm apparently not doing right. Hmmm.
Did you wipe data/cache/dalvik before flashing the roms?
mosesport said:
It definitely helped to get back to the stock ROM, but now it appears as though no other ROMs are working for me. I've tried MIUI and MikFroyo, and they both get stuck in boot loops. There's something I'm apparently not doing right. Hmmm.
Click to expand...
Click to collapse
Are you updated to the latest Radio and pri? You have to check what version you have and what version you need to flash the rom you want to use. That is most likely the problem. I know older kernels do not like the new radio or pri. You probably have to update them and you should be fine.

[Q] I know you guys get sick of helping noob but I just rooted and need help!

I have been wanting to root and try a custom rom but I was scared of brick. Anyway I finally rooted with Unrevoked 3.3 which installed Clockwork recovery also and after that I installed rom manager. When I went to do a backup of current rom it said I need to install Clockwork recovery first but its there already. I know there is guides everywhere but thats the problem not sure which to use to learn what to do before I try flashing new rom. What about kernel I really don't understand where to go from here. I am rooted and Clockwork recovery flashed but don't know where to go from here. I am not a idiot just a little guidance please! I really want learn process of installing new and restoring old roms with my Evo. How do I know what other updates need to done before using a certain rom like kernel and radio? Thanks Alot To Anyone That Can Help A Fellow Android Lover!
You try reflashing clockwork recovery?
Sent From My Evo4G Running Sense 3.0
No I just cheked to see if I could boot to recovery with vol/power buttons and seems fine Clockwork Recovery is there. So I should just let Rom Manager try to install Clockwork Recovery again? What would be my steps to installing new rom after I get rom manager to backup current rom? Thanks Alot!
Well first backup your rom and wimax keys and then go to the xda android development section and download a rom, clear cache /dalvik/ and I think its system restore something like that..I don't use cwr
Sent from my PC36100 using XDA Premium App
savannahmick said:
No I just cheked to see if I could boot to recovery with vol/power buttons and seems fine Clockwork Recovery is there. So I should just let Rom Manager try to install Clockwork Recovery again? What would be my steps to installing new rom after I get rom manager to backup current rom? Thanks Alot!
Click to expand...
Click to collapse
Just dl rom go to rom manager
I think its install from memory card and rom manager takes care of the rest....you can also dl roms from this forum on ur phone it makes it easier
Sent From My Evo4G Running Sense 3.0
First of all, if you're certain that your recovery is installed, then you need to decide what rom and what type of rom you want to install? For instance, do you want a Sense based rom (the HTC overlay that your EVO came with) or an AOSP rom (Pure Android like on the Nexus)? For a sense based rom, I suggest Myn's Warm TwoPointTwo RLS-5. You can see photos of it as well as download it from here: http://forum.xda-developers.com/showthread.php?t=793471 and for an AOSP rom, I suggest Salvage-Mod 1.2.1. It can be downloaded from here: http://www.salvage-mod.com/node/4. Make sure you download the Google Applications from the same page. Whichever you decide to flash or any others, put them on your SD card. Now shutdown your device. Simultaneously press the DOWN volume button and the power button until your device starts. There will be a short pause and then a few lines of text will scroll across the screen. Afterwards, you will see a set of options. One of the options will be "recovery". By the way, look at the top of the screen and make sure it displays "S-OFF". If it displays "S-ON", you are not rooted. Anyway, select recovery. Your phone will vibrate and display a white EVO screen and then boot into recovery. Your recovery should be ClockworkMod. Go into the backup menu and select nandroid backup to make a backup of your current setup. You can always restore your device to the way it was if you don't like your new roms, mods, themes and kernels. After you've made your backup, go to the wipe menu and wipe everything except the SD card. After that, go to the flash zip menu and flash the rom you want to try. After it's finished, it should prompt you to reboot. Do so and be patient. You will appear to hang at a couple of places. Be patient. Let it finish. Be patient. Do not pull the battery. Be patient. After some time, you will see your rom's splash screen and then your new homescreen. If it is a sense based rom, go to menu-settings-system updates and select update profile after you've signed in with your Google credentials. Enjoy your new rom.
posting & replying via the XDA Premium app.
dougjamal said:
First of all, if you're certain that your recovery is installed, then you need to decide what rom and what type of rom you want to install? For instance, do you want a Sense based rom (the HTC overlay that your EVO came with) or an AOSP rom (Pure Android like on the Nexus)? For a sense based rom, I suggest Myn's Warm TwoPointTwo RLS-5. You can see photos of it as well as download it from here: http://forum.xda-developers.com/showthread.php?t=793471 and for an AOSP rom, I suggest Salvage-Mod 1.2.1. It can be downloaded from here: http://www.salvage-mod.com/node/4. Make sure you download the Google Applications from the same page. Whichever you decide to flash or any others, put them on your SD card. Now shutdown your device. Simultaneously press the DOWN volume button and the power button until your device starts. There will be a short pause and then a few lines of text will scroll across the screen. Afterwards, you will see a set of options. One of the options will be "recovery". By the way, look at the top of the screen and make sure it displays "S-OFF". If it displays "S-ON", you are not rooted. Anyway, select recovery. Your phone will vibrate and display a white EVO screen and then boot into recovery. Your recovery should be ClockworkMod. Go into the backup menu and select nandroid backup to make a backup of your current setup. You can always restore your device to the way it was if you don't like your new roms, mods, themes and kernels. After you've made your backup, go to the wipe menu and wipe everything except the SD card. After that, go to the flash zip menu and flash the rom you want to try. After it's finished, it should ask you to reboot. Do so and be patient. You will appear to hang at a couple of places. Be patient. Let it finish. Be patient. Do not pull the battery. Be patient. After some time, you will see your rom's splash screen and then your new homescreen. If it is a sense based rom, go to menu-settings-system updates and select update profile after you've signed in with your Google credentials. Enjoy your new rom.
posting & replying via the XDA Premium app.
Click to expand...
Click to collapse
Yeah that's what I meant....I suck at instructions lol
Sent From My Evo4G Running Sense 3.0
One more thing I just let Rom Manager install recovery and after that I did backup. The next step would be to dl rom and place it in sd card right? Do I need to rename file or update kernel or radio and where do I put the new rom for manager to find? Also I didn't use Unrevoked forever just 3.3 will I need to run the forever app also? I know what a noob! Man I really Thank You for helping! I am dying to try some new roms Froyo is boring. What rom what rom do you recommend? Thanks Again!
droidguy718 said:
Yeah that's what I meant....I suck at instructions lol
Sent From My Evo4G Running Sense 3.0
Click to expand...
Click to collapse
(Laughing)....no problem, my friend. We're all here to help. Take care...
posting & replying via the XDA Premium app.
Root of card is preferred but anywhere is fine since you will have to point rom manager to it. Alot of roms come with kernels so I wouldn't sweat it. No need to rename. A good starting rom are any kingsroms insane fast and all features usually work most are still froyo but look much different than ur stock rom
Sent From My Evo4G Running Sense 3.0
dougjamal said:
(Laughing)....no problem, my friend. We're all here to help. Take care...
posting & replying via the XDA Premium app.
Click to expand...
Click to collapse
Wouldn't say I'm a noob but I'm moderately knowledgeable in the flash process, I use amon RA (much better in my opinion) but was never good at giving instruction or directions lol
Sent From My Evo4G Running Sense 3.0
droidguy718 said:
Wouldn't say I'm a noob but I'm moderately knowledgeable in the flash process, I use amon RA (much better in my opinion) but was never good at giving instruction or directions lol
Sent From My Evo4G Running Sense 3.0
Click to expand...
Click to collapse
I, too, use amon RA and love it. As for not giving good instructions, don't worry about it. There have been numerous times when I've given summarized instructions because I either assumed the OP knew what I was talking about or I was rushing because I had something else to do. The important thing to remember is that you helped. Period!...
posting & replying via the XDA Premium app.
Thanks I am amazed how quick you helped me out! I am charging battery and then I will wipe and flash a rom with fingers crossed! I am a little scared I am not rich this is the only phone I have but you have a risk when doing any os changes with anything I guess! I will post results of first rom flash!
savannahmick said:
Thanks I am amazed how quick you helped me out! I am charging battery and then I will wipe and flash a rom with fingers crossed! I am a little scared I am not rich this is the only phone I have but you have a risk when doing any os changes with anything I guess! I will post results of first rom flash!
Click to expand...
Click to collapse
Not to worry if u run into any problems there are many threads with instructions to unbrick or fix ur problem and people here are usually very quick to help that's why I love it here....and rom manager is very good at not making mistakes in the flash process I used it when I first started so ur in good hands
Sent From My Evo4G Running Sense 3.0
And another case of a ROM Manager mishap....
HipKat said:
And another case of a ROM Manager mishap....
Click to expand...
Click to collapse
Hopefully, all will go well.
posting & replying via the XDA Premium app.
One last thing how do I install the google apps after rom flash? I think I am going to try Salavge-Mod 1.2.1. Last question for awhile I swear! THANKS AGAIN!
Just d/l the latest version, put it on your sd card, reboot to recovery and flash it, then when you reboot to system, you'll get the prompt to go to the market and d/l each app.
savannahmick said:
One last thing how do I install the google apps after rom flash? I think I am going to try Salavge-Mod 1.2.1. Last question for awhile I swear! THANKS AGAIN!
Click to expand...
Click to collapse
You can either flash it immediately after flashing Salvage-Mod or boot into Salvage-Mod first and then press and hold the power button until the menu appear
Select reboot and then select recovery. Once you're back into recovery, wipe cache & dalvik cache and then flash the Google applications (gapps). Afterwards, reboot.
posting & replying via the XDA Premium app.
savannahmick said:
One last thing how do I install the google apps after rom flash? I think I am going to try Salavge-Mod 1.2.1. Last question for awhile I swear! THANKS AGAIN!
Click to expand...
Click to collapse
-steps into the fray-
Well I first off wana say, you were in good hands with dougjamal.
To flash gapps:
1. Download the latest gapps / the ones provided in the salvage mod thread
2. Boot into recovery.
3. After you have flashed the salvage mod rom, wipe your cache and dalvik cache, then flash the gapps zip.

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

Categories

Resources