Boot Loops, forever. - Droid Incredible Q&A, Help & Troubleshooting

So, I don't really post on forums because I'm pretty tech-savvy, but I have a big problem that I can't fix, and I can usually fix everything (thanks to you guys!)
This morning, my incredible acted up as I was checking an e-mail and it froze, so I decided to battery pull because restarting my phone didn't work. (Note, my incredible has been running VERY solidly on a CM7.1 nightly). As I tried to boot up the phone again, it would stay on the white HTC Incredible screen. When I rebooted into recovery thru HBOOT, i realized that there was an error mounting something, like recovery_log, or something like that (i didn't mind this because I thought I knew what I was doing), but I tried restoring my old nandroid backup that was working well, but it didn't work. It said it couldn't format /data or something... It ended up staying on the white HTC incredible screen. So, I wiped data/cache like 10 times, and dalvik cache as well and tried re-flashing a clean install of cm7.1 stable, but didn't work again - led me straight to the white Incredible screen. So, installing a fresh rom AND restoring a solid backup didn't work... so...
I found the RUU 2.3 stock rom on the development forums, and tried to install that like I do with the radios (PB31IMG.zip) through HBOOT, but no cigar. It did go PASSED the white screen, but boot loops at the Droid eye.
So, I thought I'd find a different stock img, and found the 2.2 official OTA .zip and installed it the same way, but got the exact same result (boot loops, forever).
Any suggestions? I can't think of anything else.... I feel like my phone is bricked, but I didn't do anything to make that happen.
I feel like something happened that made me not able to format the /data, and stuff. I even formatted my SDcard in case it was the problem.
Any help is appreciated. Thanks!

Load the RUU onto a different fat32 sd card and see if you are able to boot.
Sent from my ADR6300 using XDA Premium App

i'll try that and give an update. thanks for the reply!
*update* no luck. same thing happens. i tried on three different sdcards formatted fat32...

Can you factory reset and flash a ROM from a different sd than the one you were using? Description sounds like bad sd, and AOSP roms interact with the sd on boot. If original (CM 7) sd is toast, it'll never boot, hence different sd card and prefably RUU
Sent from my ADR6300 using XDA Premium App

I had this happen once where no matter what rom i flashed all i got was bootloops. I had to get the stock froyo ruu.exe that you run from your pc and install it that way. Then once installed boot up and go to settings/sd & phone storage and do a factory reset from there. This factory reset is a true reset as it wipes out vzw programing also. After reset folow on screen steps to reactivate your phone, you can skip the rest of the setup. Once thats done your good to go just flash clockwork or amon ra recovery and then flash what ever rom you want. No guarantees but it worked for me.
NOTE: This assumes you are s-off, if your not after flashing the ruu you will have to use unrevoked to regain root and s-off again.

You can also try wiping /system and /boot.

*token post to get my post count high enough to ask for help in the hacking section, dumb rule btw. FAIL*
Mine is now stuck in a continuous boot as well. It's not rooted and have no idea how to fix it.
I see instructions in this thread but they mean nothing to someone who doesn't know what the abbreviations stand for or how to go about the commands required.

sl4m said:
*token post to get my post count high enough to ask for help in the hacking section, dumb rule btw. FAIL*
Mine is now stuck in a continuous boot as well. It's not rooted and have no idea how to fix it.
I see instructions in this thread but they mean nothing to someone who doesn't know what the abbreviations stand for or how to go about the commands required.
Click to expand...
Click to collapse
if you are non root. you will need to download the RUU.exe for 2.2 and install if from you pc.
http://androidforums.com/htc-droid-...mplest-instructions-ever-windows-xp-only.html
follow that and your phone will be back to the day you got it out of the box.

All the recommendations prior to Synisterwolf's post require root.
Some of the "abbreviations" are detailed in the Droid Incredible Development section. If you head over there you can read up on a beginners guide to root terms and helpful links in one of the top four threads namely:
If You're New to Modding/Rooting, Read This First! (Updated 08/05/10)
I will say though:
CM7.1 = CyanogenMod 7.1 (this is a rom)
OTA = Over The Air
2.2 = Froyo (Android software version 2.2)
RUU = basically refers to a file that people use to revert back to the Droid Incredible's pre-root status. Although there are additional steps as well.

SlimSnoopOS said:
All the recommendations prior to Synisterwolf's post require root.
Some of the "abbreviations" are detailed in the Droid Incredible Development section. If you head over there you can read up on a beginners guide to root terms and helpful links in one of the top four threads namely:
If You're New to Modding/Rooting, Read This First! (Updated 08/05/10)
I will say though:
CM7.1 = CyanogenMod 7.1 (this is a rom)
OTA = Over The Air
2.2 = Froyo (Android software version 2.2)
RUU = basically refers to a file that people use to revert back to the Droid Incredible's pre-root status. Although there are additional steps as well.
Click to expand...
Click to collapse
RUU = ROM Update Utility

no luck, I installed the program on my XP machine, but the app can't connect to the phone.
The phone literally keeps rebooting over and over.

sl4m said:
no luck, I installed the program on my XP machine, but the app can't connect to the phone.
The phone literally keeps rebooting over and over.
Click to expand...
Click to collapse
Then its gotta be a hardware failure.
Sent from my sexy assistant. (AMOLED HTC Incredible)

wow... what a bummer. thanks for the help anyway, it's much appreciated.

sl4m said:
no luck, I installed the program on my XP machine, but the app can't connect to the phone.
The phone literally keeps rebooting over and over.
Click to expand...
Click to collapse
Does it give any specific error code when it says it can't connect to the phone?
Someone correct me if I'm wrong but don't you have to have HTC sync installed on your pc to use an ruu.exe? Do you have that installed?
Sent from my ADR6300 using xda premium

I'll try it again to verify the code, I'm pretty sure it was "170"

sl4m said:
*token post to get my post count high enough to ask for help in the hacking section, dumb rule btw. FAIL*
Mine is now stuck in a continuous boot as well. It's not rooted and have no idea how to fix it.
I see instructions in this thread but they mean nothing to someone who doesn't know what the abbreviations stand for or how to go about the commands required.
Click to expand...
Click to collapse
I had this issue the first time i rooted my phone and attempted to put on a ROM, and i resolved it when i found this post to get back to stock. I also used this to fix a problem where my phone had a black screen with a line through it on booting to recovery or attempting to do a nandroid back up:
droidforums.net/forum/droid-incredible-hacks/95406-how-correctly-unroot-incredible.html
All i did was basically use the PB31IMG Method without turning s=on, ( i had stock radio and still have 7.28 )
1) download that PB31IMG.zip and drop it on the root of your sd card ( it has to be named ( PB31IMG.zip ) so make use you have file extensions showing on your PC.
2) boot to hboot and and let see the file and install it
3) used unrevoked ( remove sd card ) to aquire root again.
idk if this helps, but this seems to get me out of the few weird situations i had

sl4m said:
I'll try it again to verify the code, I'm pretty sure it was "170"
Click to expand...
Click to collapse
Check this out to fix your 170 error.
http://androidforums.com/incredible...170-171-solution-windows-7-a.html#post1472468

This low key happened to me and I booted in to HBOOT and went to clear storage and it did its thing and booted up, from there I had to activate it then I was set!
Sent from my ADR6300 using XDA App

=D
Sent from sweet snacks off tapatalk.

Related

Problems flashing, need help please!!!

Ok, so here is what I have done: I have already rooted my phone, etc, and have flashed some different roms on my phone, and have not had any problems until now. I recently tried the miui rom, but didn't like it.I just flashed the newest miui rom, and it was acting really weird, so I decided to go back to the virtuous rom which I had used before. For whatever reason, I am getting this error: E: can't mount /dev/block/mmcblk0p1 (file exists), and the installation aborts. I did the wipe data deal, and I also tried to reinstall the miui rom. It says that installs fine, but it won't get past the htc incredible screen. Any suggestions? Also, I didn't want to try this and mess things up further, but can I restore a backup I had done when I had the virtuous rom installed, or do I have to have the rom already working properly? Kind of a noob question, I know.
calamari85 said:
Ok, so here is what I have done: I have already rooted my phone, etc, and have flashed some different roms on my phone, and have not had any problems until now. I recently tried the miui rom, but didn't like it.I just flashed the newest miui rom, and it was acting really weird, so I decided to go back to the virtuous rom which I had used before. For whatever reason, I am getting this error: E: can't mount /dev/block/mmcblk0p1 (file exists), and the installation aborts. I did the wipe data deal, and I also tried to reinstall the miui rom. It says that installs fine, but it won't get past the htc incredible screen. Any suggestions?
Click to expand...
Click to collapse
Hmmm... Do you have any Nandroids from earlier roms? That'd be the easiest route.
If not, since you can't even get to a homescreen, you might try an RUU reset, but let's hope it won't come to that for now.
I get that too, but only when going into the menu for Dalvik Cache wiping, and it never actually gets in my way, it just pops up and then I can keep going on about my business.
1. yes you can restore the backup whether a rom is currently working or not
2. post questions in the correct forum
If you can't get a nandroid backup to work, you may have to RUU back to stock.
Here's the older one that will still let you use unrevoked after. Just rename this PB31IMG.zip, load up H-boot, follow the prompts, and be patient. Then run unrevoked when it finishes and install rom manager to restore your backup. If the backup still won't work, try a fresh install of virtuous.
Sorry
g00s3y said:
1. yes you can restore the backup whether a rom is currently working or not
2. post questions in the correct forum
Click to expand...
Click to collapse
My apologies, where should I have posted? And can I move the thread so it is in the correct place?
calamari85 said:
My apologies, where should I have posted? And can I move the thread so it is in the correct place?
Click to expand...
Click to collapse
Probably in the Q & A General Forum, but don't worry about it this time, just as long as it doesn't end up being a frequent thing.
But I don't know about being able to move the thread, I think that's a Moderator power.
Regarding your issue though, either use the RUU link posted above, or try Nandroid-ing back.
No go
I tried restoring a backup, and got cannot mount /data, along with the previous error... It changed my boot animation, but has not restored my phone. should I do this RUU back to stock? Sorry for not being very good at this, and I definitely appreciate the help.
calamari85 said:
I tried restoring a backup, and got cannot mount /data, along with the previous error... It changed my boot animation, but has not restored my phone. should I do this RUU back to stock? Sorry for not being very good at this, and I definitely appreciate the help.
Click to expand...
Click to collapse
It's cool.
Yes, you'll need it on the root of your SD-card (not in any folders), run it through hboot, and then you'll have to re-run the unrEVOked tool from your PC. I would also suggest running the S-Off tool afterwards, just to be safe. That has saved me once before.
Make sure you have at least 50% battery before you do the hboot flash. VERY IMPORTANT. If your phone dies or loses power while updating the radio files from the RUU, your phone is as good as bricked.
If you get stuck with the unrEVOked tool at waiting for root for more than fifteen minutes, post back here again and we'll continue from there.
EDIT: Actually, run the unrEVOked Forever S-Off tool through CWM recovery before doing this, as a pure precautionary measure.
I'm an idiot apparently
Well, I am really sorry guys, I won't ask any more questions on here. Apparently I am super stupid. I figured it out, I left out some info because it didn't even register as relevant, but it was the key apparently. So I just go a new sd card, and I formated it on my computer, and just dropped the zip files on there, and was trying to flash like that, and apparently the phone didn't like the new sd card, or it needed info off the old one, because once I put it back in and tried flashing from it, it works fine now. Sorry for bothering everyone, I am going to go sit in the corner in shame now.
calamari85 said:
Well, I am really sorry guys, I won't ask any more questions on here. Apparently I am super stupid. I figured it out, I left out some info because it didn't even register as relevant, but it was the key apparently. So I just go a new sd card, and I formated it on my computer, and just dropped the zip files on there, and was trying to flash like that, and apparently the phone didn't like the new sd card, or it needed info off the old one, because once I put it back in and tried flashing from it, it works fine now. Sorry for bothering everyone, I am going to go sit in the corner in shame now.
Click to expand...
Click to collapse
Hahaha! No worries, we all have our moments!
Glad you figured it out. Be sure to make a backup of your current rom on your new SD card right away haha.

[Q] Rooted g2 won't boot past htc screen

Hello all.
I have a t-mobile g2, currently S-OFF, which is sitting in hboot/fastboot right now. I will not boot past the HTC screen.
I attained root last night using this method, and it worked without problems. I then gave a few apps (terminal and shark, to be precise) superuser access. Went to sleep.
This morning, I wanted to delete some apps and change some system fonts around (wanted to use the ubuntu font instead of droidsans). deleted photobucket at amazon mp3. while trying to change the fonts, I changed permissions on the /system/ folder to 777 (chmod 777 /system/). Changing the fonts wasn't working out, so i decided to leave it alone and just reboot my device. upon reboot, it would no longer boot past the htc boot screen. It will, however, go into hboot/fastboot mode without a problem. I tried going into recovery mode and using the update.zip (e4aaacea73af.OTA_Vision_TMUS_1.22.531.8-1.1.19.531.1_release_signed.zip renamed). No luck. Also, i tried researching on the forums and using adb to try to unbrick, but adb doesn't recognize any device being plugged in. fastboot did work, though, and i wrote the original recovery.img file into the phone (although I don't know where it goes when this is done...) and now I don't know where to go next. any help?
Try wiping your data and flashing a new rom on there. Some roms have a OC kernel so I would also make sure u know what kind of kernel the rom has. If its OCed I would download o non OCed kernel. Reason being some are like OCed to the max which makes the phone not boot, and when turned off sleeping doesn't want to turn back on.
Sent from my HTC Vision using XDA Premium App
Vandale said:
Try wiping your data and flashing a new rom on there. Some roms have a OC kernel so I would also make sure u know what kind of kernel the rom has. If its OCed I would download o non OCed kernel. Reason being some are like OCed to the max which makes the phone not boot, and when turned off sleeping doesn't want to turn back on.
Sent from my HTC Vision using XDA Premium App
Click to expand...
Click to collapse
I had stock android that came with the phone, I just got it about a week ago. Is there any way to find the standard/stock android rom for the g2? if anyone could link it and let me know how to flash it, that would be amazing.
Update:
I've been doing a bit more research, and I found that it might be possible to flash a stock rom (PC10IMG.zip). I downloaded the TMOUS one provided in this thread and shortened it to PC10IMG.zip. Once I do that, I go into Hboot, and when it checks for the different nbh/zip images, it always tells me "no image"/"no image or wrong image!". HELP!!!
consciousdawn said:
Update:
I've been doing a bit more research, and I found that it might be possible to flash a stock rom (PC10IMG.zip). I downloaded the TMOUS one provided in this thread and shortened it to PC10IMG.zip. Once I do that, I go into Hboot, and when it checks for the different nbh/zip images, it always tells me "no image"/"no image or wrong image!". HELP!!!
Click to expand...
Click to collapse
Which one did you download? The first few on there were pre-release ROMs. The 1.19.531.1 ROM was the release ROM originally. Most recent G2's come with 1.22 (the OTA update) pre-installed, which we do not currently have a PC10IMG.zip for. If your G2 had 1.22 (e.g., you already had wifi-calling and tethering), you won't be able to use the 1.19 PC10IMG unless you used gfree to obtain S-OFF. If you did not (i.e., you only flashed the engineering HBOOT), you should not try to flash this file (it will replace your HBOOT with the shipping version and then quit mid-flash because it sees you already have a higher version installed). Even if you did obtain S-OFF with gfree, flashing this file will cause you to lose your engineering HBOOT and root (though you will still have S-OFF, so it's easy to re-root).
As was stated earlier, the easiest/best thing to do at this point is flash a custom ROM. If you still want the stock look-and-feel, here is a pre-rooted stock G2 ROM: http://forum.xda-developers.com/showthread.php?t=836042. You want to flash it through ClockworkMod recovery. I'm assuming you hadn't installed this already or you would have a backup of your ROM that you could have simply restored. You can install ClockworkMod recovery through fastboot though (there is a thread in the dev section or you can search for one of the many guides on it).
Also, you will probably want to get the de-odex version of the stock ROM. If you are doing any kind of theming or UI modifications, that is usually required (or your changes will cause a bootloop). Without knowing the details of what you tried to do, I'm guessing this is what happened to you (since the stock ROM is odex'ed).
ianmcquinn said:
As was stated earlier, the easiest/best thing to do at this point is flash a custom ROM. If you still want the stock look-and-feel, here is a pre-rooted stock G2 ROM: http://forum.xda-developers.com/showthread.php?t=836042. You want to flash it through ClockworkMod recovery. I'm assuming you hadn't installed this already or you would have a backup of your ROM that you could have simply restored. You can install ClockworkMod recovery through fastboot though (there is a thread in the dev section or you can search for one of the many guides on it).
Also, you will probably want to get the de-odex version of the stock ROM. If you are doing any kind of theming or UI modifications, that is usually required (or your changes will cause a bootloop). Without knowing the details of what you tried to do, I'm guessing this is what happened to you (since the stock ROM is odex'ed).
Click to expand...
Click to collapse
Do you mean this thread? I have been trying to follow along and it's a bit confusing (although I feel that's due largely in part to grammatical/usage errors). what you are saying does help a lot though. I just need to learn how to install Clockworkmod Recovery through fastboot. *googles away* in the meantime, feel free to link me to another thread which helps me do this. Thanks a million.
UPDATE:
I finally figured out what I was doing. So I used fastboot to flash a clockworkmod recovery.img onto my g2. When I went to recovery, after booting into hboot, it went to the HTC screen, as it should. Guess what I got? loopboot, once again T_T. Luckily I still have the official recovery.img, and reflashed that. Did I do something wrong? Please let me know.
consciousdawn said:
UPDATE:
I finally figured out what I was doing. So I used fastboot to flash a clockworkmod recovery.img onto my g2. When I went to recovery, after booting into hboot, it went to the HTC screen, as it should. Guess what I got? loopboot, once again T_T. Luckily I still have the official recovery.img, and reflashed that. Did I do something wrong? Please let me know.
Click to expand...
Click to collapse
Wait, so what exactly happened? You entered the bootloader (white screen with green Android guys at the bottom), selected to enter recovery (using volume down and power button to select), and then was presented with an HTC logo? That means ClockworkMod recovery did not successfully flash. Did you get any errors when you used flashboot?
That's exactly what happened, and no, not at all. It said it flashed successfully. Maybe I don't have the correct version of Clockworkmod? If you could please link me to a good one, that would be great.
UPDATE!!
So I found an official clockworkmod 2.5.1.2, and now when I boot into recovery, it shows the HTC logo and then goes to clockworkmod. This is amazing. Thank you guys for all your help, I have learned something new today.
Now, can someone explain the difference between odexed and deodexed? please? lol.
ianmcquinn said:
Wait, so what exactly happened? You entered the bootloader (white screen with green Android guys at the bottom), selected to enter recovery (using volume down and power button to select), and then was presented with an HTC logo? That means ClockworkMod recovery did not successfully flash. Did you get any errors when you used flashboot?
Click to expand...
Click to collapse
Looks like I cried victory too quickly. While I do get the menu for clockworkmod (every time I boot, for that matter), every time I issue a command, such as reboot now, or install from SDcard, and even advanced, the screen goes black. GRRR, WHAT AM I DOING WRONG? I've been at this since about 1 today T_T
Just wanted to say that I'm the biggest noob on the planet. While I did upgrade to cwm 3.0.0.5, i didn't know it allowed the use of the main controls. I got my phone up and running now. Thank you for all the help. Good night :]

[Q] Completed Factory Reset (MIUI) and SDCard format and now soft-bricked!

Hey folks,
Thanks for taking the time to read/assist. I don't typically do these kinds of posts and am at my wit's end!
Phone's Previous Setup - MIUI Gingerbread, Rooted (but with S-ON after the fact).
What happened:
My HTC Incredible finally got to the point of being practically unuseable with laggy behavior and random restarts and the like, so I decided to complete a reset to factory settings or wipe.
I completed my backups using Titanium (apps) and ClockworkMod Recovery (full backup). After this, I went ahead and opened up Settings and directed the phone to complete a Reset to Factory Settings. It ran through the process, rebooted, and came up jelly. While no custom apps were installed (expected), my folder settings on my main home page were saved, along with some previous text messages. I was pleasantly surprised.
From here, I wished to wipe the SD Card so as to make sure it was clean of any residual folders/files that might cause conflict down the road (based on advice from others). So, headed to the SD card part of the settings. Had to unmount the SD card to format, proceeded to do so.
Here's where things went wonky: Despite receiving a confirmation that the SD card format had proceeded, nothing else ever happened. I attempted to mount the card again w/o luck (kept getting a msg that it was now unmounted). Eventually, I decided to go ahead and restart the phone and see if that helps. Big mistake.
From this point forward, the phone refuses to fully start up into any Android ROM. Initially, it hung on the white HTC Incredible splash screen (yes, even w/ giving it an hour+ of time). I tried wiping and reflashing different ROMS over the period of the day yesterday to no avail.
Doing a full recovery via ClockworkMod (from my backup that I made before and copied back onto the SD card via USB) leaves me stuck on the HTC Incredible white splash screen.
MIUI - 2.2.10
Hangs on white splash screen
No go w/ or w/o SD card installed
MIUI - 2.2.17
Loads past white and MIUI splash screens
Instead of loading into Android homescreen, immediately loads up "Encryption" error and directs to "reset phone."
Repeated restart and attempts of resetting phone don't work
No go w/ or w/o SD card installed.
MIUI - 1.12.9
Hangs on white splash screen.
No go w/ or w/o SD card installed.
CM - 7.1.0
Hangs/loops on CM splash screen.
No go w/ or w/o SD card installed.
CM - 6.1.0
Hangs/loops on CM splash screen.
No go w/ or w/o SD card installed.
I looked into HBOOT options, getting PB31IMG.ZIP and PG86IMG.ZIP.img thinking maybe I could try reverting to stock at a friend's suggestion. HBOOT sees the files and "checks" them, even briefly showing a small vertical blue loading bar at the top-right corner, but never attempts to run/update them as I am lead to expect from all the instructions/encounters I've found on the net suggest. The screen info flashes by so quickly, I can barely read it, but I confirmed that it said "checking" and not updating or such. x.x
I considered trying to flash an updated copy of ClockworkMod Recovery, but I cannot do that w/o being able to load up the phone into Android.
I cannot run anything desktop-side, like ADB, as they all require the phone started up and put into USB-debugging mode.
I've looked into and tried all this and more, but nothing seems to be working.
My next idea is to try to forcibly downgrade the phone. Reasoning being that I read that the HBOOT will not try to update if it senses that the ROM is newer than its default settings(?). So, I need a good choice of "old" ROM that I can attempt to install via the HBOOT or CWM Recovery, and verify I have the correct files for HBOOT to try updating/running.
Again, this is a speculative attempt, but I'm willing to try whatever might work! Otherwise, I've got a fancy brick and my well-being on the line w/ no $$ to replace the phone. x.x
Thanks again for reading and hopefully offering some wonderful assistance! Sorry it's so long!
Feel free to ask Qs if you need clarification on stuff.
wigmuke said:
Hey folks,
Thanks for taking the time to read/assist. I don't typically do these kinds of posts and am at my wit's end!
Phone's Previous Setup - MIUI Gingerbread, Rooted (but with S-ON after the fact).
What happened:
My HTC Incredible finally got to the point of being practically unuseable with laggy behavior and random restarts and the like, so I decided to complete a reset to factory settings or wipe.
I completed my backups using Titanium (apps) and ClockworkMod Recovery (full backup). After this, I went ahead and opened up Settings and directed the phone to complete a Reset to Factory Settings. It ran through the process, rebooted, and came up jelly. While no custom apps were installed (expected), my folder settings on my main home page were saved, along with some previous text messages. I was pleasantly surprised.
From here, I wished to wipe the SD Card so as to make sure it was clean of any residual folders/files that might cause conflict down the road (based on advice from others). So, headed to the SD card part of the settings. Had to unmount the SD card to format, proceeded to do so.
Here's where things went wonky: Despite receiving a confirmation that the SD card format had proceeded, nothing else ever happened. I attempted to mount the card again w/o luck (kept getting a msg that it was now unmounted). Eventually, I decided to go ahead and restart the phone and see if that helps. Big mistake.
From this point forward, the phone refuses to fully start up into any Android ROM. Initially, it hung on the white HTC Incredible splash screen (yes, even w/ giving it an hour+ of time). I tried wiping and reflashing different ROMS over the period of the day yesterday to no avail.
Doing a full recovery via ClockworkMod (from my backup that I made before and copied back onto the SD card via USB) leaves me stuck on the HTC Incredible white splash screen.
MIUI - 2.2.10
Hangs on white splash screen
No go w/ or w/o SD card installed
MIUI - 2.2.17
Loads past white and MIUI splash screens
Instead of loading into Android homescreen, immediately loads up "Encryption" error and directs to "reset phone."
Repeated restart and attempts of resetting phone don't work
No go w/ or w/o SD card installed.
MIUI - 1.12.9
Hangs on white splash screen.
No go w/ or w/o SD card installed.
CM - 7.1.0
Hangs/loops on CM splash screen.
No go w/ or w/o SD card installed.
CM - 6.1.0
Hangs/loops on CM splash screen.
No go w/ or w/o SD card installed.
I looked into HBOOT options, getting PB31IMG.ZIP and PG86IMG.ZIP.img thinking maybe I could try reverting to stock at a friend's suggestion. HBOOT sees the files and "checks" them, even briefly showing a small vertical blue loading bar at the top-right corner, but never attempts to run/update them as I am lead to expect from all the instructions/encounters I've found on the net suggest. The screen info flashes by so quickly, I can barely read it, but I confirmed that it said "checking" and not updating or such. x.x
I considered trying to flash an updated copy of ClockworkMod Recovery, but I cannot do that w/o being able to load up the phone into Android.
I cannot run anything desktop-side, like ADB, as they all require the phone started up and put into USB-debugging mode.
I've looked into and tried all this and more, but nothing seems to be working.
My next idea is to try to forcibly downgrade the phone. Reasoning being that I read that the HBOOT will not try to update if it senses that the ROM is newer than its default settings(?). So, I need a good choice of "old" ROM that I can attempt to install via the HBOOT or CWM Recovery, and verify I have the correct files for HBOOT to try updating/running.
Again, this is a speculative attempt, but I'm willing to try whatever might work! Otherwise, I've got a fancy brick and my well-being on the line w/ no $$ to replace it. x.x
Thanks again for reading and hopefully offering some wonderful assistance! Sorry it's so long!
Feel free to ask Qs if you need clarification on stuff.
Click to expand...
Click to collapse
You need to gain s-off again before flashing with clockwork. How come you turned it back on?
"In a nutshell, S-OFF means that the NAND portion of the device is unlocked and can be written to. The default setting for HTC’s devices is S-ON, which means that neither can you access certain areas of the system nor can you guarantee a permanent root. Furthermore, signature check for firmware images is also ensured by the S-ON flag."
edit:
gain s=off boot into CMW wipe data, and factory reset. Flash a new rom of your choice and then boot. should get you back to a working phone.
synisterwolf said:
You need to gain s-off again before flashing with clockwork. How come you turned it back on?
"In a nutshell, S-OFF means that the NAND portion of the device is unlocked and can be written to. The default setting for HTC’s devices is S-ON, which means that neither can you access certain areas of the system nor can you guarantee a permanent root. Furthermore, signature check for firmware images is also ensured by the S-ON flag."
edit:
gain s=off boot into CMW wipe data, and factory reset. Flash a new rom of your choice and then boot. should get you back to a working phone.
Click to expand...
Click to collapse
The first time my phone was rooted/flashed, my bf did it for me. He used Unrevoked to root it and install CWM Recovery (v2.5.1.2 presently). I recall conversation being that having S-On would be better security with regards to the cell carrier (e.g., good to leave on, bad if off as they can see you rooted). So I agreed to having it put back to S-On, which I understood he then took care of.
Fast-forward a year and he now tells me he didn't actually end up running the other Unrevoked (Forever) tool to put S-On back in place, but that it simply *was*, so he left it that way. o.o;
Keep in mind, I've flashed 3 different ROMs since he originally rooted and flashed, w/o issues.
I pulled up everything to try re-rooting it again (to gain S-Off), but the instructions required having the phone loaded up and in debugging mode, which I cannot do as I cannot start up the phone past recovery in the first place.
Did I miss something that allows it via recovery? Going to check again in the meantime.
wigmuke said:
The first time my phone was rooted/flashed, my bf did it for me. He used Unrevoked to root it and install CWM Recovery (v2.5.1.2 presently). I recall conversation being that having S-On would be better security with regards to the cell carrier (e.g., good to leave on, bad if off as they can see you rooted). So I agreed to having it put back to S-On, which I understood he then took care of.
Fast-forward a year and he now tells me he didn't actually end up running the other Unrevoked (Forever) tool to put S-On back in place, but that it simply *was*, so he left it that way. o.o;
Keep in mind, I've flashed 3 different ROMs since he originally rooted and flashed, w/o issues.
I pulled up everything to try re-rooting it again (to gain S-Off), but the instructions required having the phone loaded up and in debugging mode, which I cannot do as I cannot start up the phone past recovery in the first place.
Did I miss something that allows it via recovery? Going to check again in the meantime.
Click to expand...
Click to collapse
actually its better to keep it s=off so this type of situation wont happen. Your carrier cant see your hboot from my understanding on how this phone works. They dont care if you have root or not, unless you are trying to exchange the phone for another one from them or for insurance reasons. With root you only void your warranty on the phone and not your contract or anything to do with VZW. S=off is just a NAND lock, meaning you cant add your own custom recover to the phone, and you are limited to builds that come from VZW themselves (ie the security signature check).
If you ever want to take the phone back to them because its defective or call insurance then you need to remove root and S=on. but thats the only time you need to toggle the NAND lock.
ok so you will need to ruu to stock, downgrade then gain s=off over again:
for the ruu for GB:
http://forum.xda-developers.com/showthread.php?t=1227279
a guide to do this all after you ruu:
http://forum.xda-developers.com/showthread.php?t=1306400
OMG I may've gotten it!
So I decided to give things another go with attempting to revert to stock again, as at this point, nothing is going to work other than via HBOOT.
I completed another reformat of the SD Card (Fat32) to be on the overcautious side and copied over ONLY the PB32IMG.zip file and restarted into HBOOT.
(Ah.. new user, so not allowed to post the link of where I got it.)
This time, much like before, it scanned, found the file, and did a parsing/loading. However, THIS TIME it actually prompted me to update! I chose yes (Vol+) and let it do its thing.
At this time, I am happy to announce that it actually is back up stock!
Wooohoo! Now to get it back to how I like it again. XD
If nothing else, hope this information helps someone else later on.
wigmuke said:
OMG I may've gotten it!
So I decided to give things another go with attempting to revert to stock again, as at this point, nothing is going to work other than via HBOOT.
I completed another reformat of the SD Card (Fat32) to be on the overcautious side and copied over ONLY the PB32IMG.zip file and restarted into HBOOT.
(Ah.. new user, so not allowed to post the link of where I got it.)
This time, much like before, it scanned, found the file, and did a parsing/loading. However, THIS TIME it actually prompted me to update! I chose yes (Vol+) and let it do its thing.
At this time, I am happy to announce that it actually is back up stock!
Wooohoo! Now to get it back to how I like it again. XD
If nothing else, hope this information helps someone else later on.
Click to expand...
Click to collapse
You might have lost root if you did the ruu from hboot. to check download the app "super user" from market that will tell you if you still have root or not.
Alright, now that I'm back to stock and runnin' smoothly, I need to figure out what route to take for rooting and flashing. Everyone talks about Unrevoked3, but I've heard there're other newer tools, too.
What would you recommend?
....also, sorry for the weird delay/disjointed/incomplete responses. I keep forgetting that XDA severely limits my posting capabilities. I wanted to say super thanks wolf, for all your help and sticking with me! Your input is appreciated. And yes, I'm pretty sure I lost all root, etc. It is back to "out-of-the-box" stock as far as I can tell.
wigmuke said:
Alright, now that I'm back to stock and runnin' smoothly, I need to figure out what route to take for rooting and flashing. Everyone talks about Unrevoked3, but I've heard there're other newer tools, too.
What would you all recommend?
Click to expand...
Click to collapse
unrevoked3 is the easiest way. but you will need to downgrade to android 2.2 for the security exploit.
http://forum.xda-developers.com/showthread.php?t=1306400
Edit: fixed link
---------- Post added at 10:44 AM ---------- Previous post was at 10:35 AM ----------
wigmuke said:
....also, sorry for the weird delay/disjointed/incomplete responses. I keep forgetting that XDA severely limits my posting capabilities. I wanted to say super thanks wolf, for all your help and sticking with me! Your input is appreciated. And yes, I'm pretty sure I lost all root, etc. It is back to "out-of-the-box" stock as far as I can tell.
Click to expand...
Click to collapse
lol now worries. easiest way to get to the 10 limit is just pad the count in here. ie just say something 10 times and you are good to go.
synisterwolf said:
unrevoked3 is the easiest way. but you will need to downgrade to android 2.2 for the security exploit.
http://forum.xda-developers.com/showthread.php?t=1306400
Edit: fixed link
Click to expand...
Click to collapse
Good news, I'm on 2.2 stock right now (just checked to confirm). So should be able to just go ahead and run Unrevoked3 then.
Also, the most popular recovery I'm aware of is ClockworkMod Recovery. I found that it's up to version 5.0.2.0. Would you recommend anything else or know of a newer version?
Figure if I'm going to do this, might as well do it right.
wigmuke said:
Good news, I'm on 2.2 stock right now (just checked to confirm). So should be able to just go ahead and run Unrevoked3 then.
Also, the most popular recovery I'm aware of is ClockworkMod Recovery. I found that it's up to version 5.0.2.0. Would you recommend anything else or know of a newer version?
Figure if I'm going to do this, might as well do it right.
Click to expand...
Click to collapse
Nope I'm RunNing that one and it works well.
Sent from my sexy assistant. (AMOLED HTC Incredible)

Confirm Steps & Apps to Install New ROM on G2 (Mimicry 1.3.2)

I have had my G2 for about 18 months and have been running into a lot of issues recently. I've decided to fix those issues by rooting & getting a new ROM installed. I'm a tech savvy guy, but have not done anything on the phone end due to not wanting to break whats working. I've decided to go with the Mimicry 1.3.2 ROM since the install process uses Aroma and is very straight forward. Before I pull the trigger, I just want to make sure I have all the steps clear so that I don't go "Oh sh**" in the middle because I missed a step. There's also a couple of steps that I'm not clear on. Here's what I researched:
-Root phone using HTC's bootloader unlocker
-Format phone's flash memory to EXT4
--What is the best app to do this with? Will my phone work with Gingerbread after I make this change?
-Download Mimicry 1.3.2 and Google Apps put the zip files on my phone (not SD card)
-Power off phone and then push the volume down and power buttons together and choose to install the ROM
-Answer prompts in Aroma (including installing WiFi calling)
-Flash Google apps
--How exactly is that done?
-Restart phone and start setting up apps again.
Does that look correct and is there anything that I'm missing? Thank you in advance for your help.
Well first off I would stay away from HTC official unlocked bootloader, its worthless and will give you headaches in the future
use the wiki to root, either follow the wiki in cyanogen or here on xda, if you even slightly tech savvy it will be easy
following that guide you will have clockwork recovery, but I suggest moving to 4ext recovery, among many reasons is the ability to format to ext4. Otherwise the next easiest way to format would be to flash a super wipe script with ext4 format written to it (just search xda and you'll find it easier)
Now after you are rooted with an engineering s-off hboot consider flash the .19 radio, not super important but many find this to have the best reception and battery life.
Next make sure your SD card is fat32, I also suggest an ext4 partition there as well (easily done through recovery) but skip the swap
Now feel free to flash mimicry, and may I add this is one other best ICS Roms for the vision, and blk_jck is a very helpful Dev as well.
Good luck, if you run into issues there will be answers all over xda, just search a bit, happy flashing!
Sent from my Nexus 7 using xda premium
Thanks
Thanks for the heads up on the HTC bootloader. I'll check out the Wiki on how to PermRoot my phone.
Mimicry, recovery, soft bricks, and new ROM
Agree with demkantor, the step-by-steps so painstakingly described in cyanwiki are your best bet.
Likewise, using 4ext in place of clockwork is also my recommendation, as I've used both now and
find the latter more polished and stable.
I recently rooted and updated for the first time. Got successfully as far as ICS using cyan's instruction,
then decided to use mimicry after reading about the radio updates etc posted by madmaxx. I think the sequence in which i
carried these out was flawed, because after updating the radio instruction sets, I re-flashed mimicry to take advantage of the
updated radio features and to install the wi-fi telephony; that was my downfall. I got caught in a boot-loop. Oh sh*t, indeed.
I could not, for the life of me, get past the HTC white screen. Being a total noob, I had no
idea where to go to next. I searched this website and cyan's a lot, and realised the term for what I now had was a 'soft
brick' or 'semi brick'. Could not get the device to be recognised via ADB, and could not access the sdcard directory.
I scratched my head for a few days (I had bought another phone prior to playing with the old G2), and came up with the
idea of just accessing the sdcard via my laptop, directly. In the midst of this, I turned on the phone (after taking the card
out), and voila, the phone now cycled into engineering hboot !
I subsequently was able to edit the sdcard directly via the laptop (using an micro sd card adapter), and removed the pc10?.img file
that was left over the radio update. Having recovered to this point, I re-flashed mimicry 1.3.1 (via 4ext) and so was able to get a completely
functional phone again.
The point of all of the is this: 1. To all the previous post-ers, both here and at cyanwiki...You guys rock. Can't say that enough. Even more:
2. A 'soft brick' may be anything but...a little bit of not-very-complicated experimentation afterward can pay off big time. Lastly, I tried
mimicry 1.3.2, but kept getting a heap of error messages. Needless to say, I was a bit spooked by the previous stuff-up, so I quickly reverted
to 1.3.1, which appears to be 100% stable (IMHO).
Cheers
1.3.2 adds few framework level changes and no device level changes. Definitely nothing that should cause errors or problems booting anyway.
Sent from my HTC Vision using xda premium
Good Info
timram said:
Agree with demkantor, the step-by-steps so painstakingly described in cyanwiki are your best bet.
Likewise, using 4ext in place of clockwork is also my recommendation, as I've used both now and
find the latter more polished and stable.
I recently rooted and updated for the first time. Got successfully as far as ICS using cyan's instruction,
then decided to use mimicry after reading about the radio updates etc posted by madmaxx. I think the sequence in which i
carried these out was flawed, because after updating the radio instruction sets, I re-flashed mimicry to take advantage of the
updated radio features and to install the wi-fi telephony; that was my downfall. I got caught in a boot-loop. Oh sh*t, indeed.
I could not, for the life of me, get past the HTC white screen. Being a total noob, I had no
idea where to go to next. I searched this website and cyan's a lot, and realised the term for what I now had was a 'soft
brick' or 'semi brick'. Could not get the device to be recognised via ADB, and could not access the sdcard directory.
I scratched my head for a few days (I had bought another phone prior to playing with the old G2), and came up with the
idea of just accessing the sdcard via my laptop, directly. In the midst of this, I turned on the phone (after taking the card
out), and voila, the phone now cycled into engineering hboot !
I subsequently was able to edit the sdcard directly via the laptop (using an micro sd card adapter), and removed the pc10?.img file
that was left over the radio update. Having recovered to this point, I re-flashed mimicry 1.3.1 (via 4ext) and so was able to get a completely
functional phone again.
The point of all of the is this: 1. To all the previous post-ers, both here and at cyanwiki...You guys rock. Can't say that enough. Even more:
2. A 'soft brick' may be anything but...a little bit of not-very-complicated experimentation afterward can pay off big time. Lastly, I tried
mimicry 1.3.2, but kept getting a heap of error messages. Needless to say, I was a bit spooked by the previous stuff-up, so I quickly reverted
to 1.3.1, which appears to be 100% stable (IMHO).
Cheers
Click to expand...
Click to collapse
Thanks for that info. I am taking a look at the Cyanogen Wiki and seeing what I have to do. I'm thinking that I will jump directly to Mimicry 1.3.2 instead of installing Cyanogen 9 first. Hopefully that file doesn't hang out there and causes that boot loop to happen to me (thanks for that explanation, BTW).
So do I have to use that ClockworkMod to load the ROM, or does EXT4 do the same thing (as far as loading the rom goes)?
...where thanks is due
many thx, blk jack, I should have specifically mentioned your awesome contributions as well, and
have remedied with thanks meter as i came/come across it.
Will re-try the 1.3.2 shortly. If I run in to the same glitches, I will try and make note of the specific errors
(or any other bugs, for that matter) and let you know.
Use the following guide, it is incredibly simple yet swift. Contains root methods for both the DesireZ and the T-Mobile G2 :
http://wiki.cyanogenmod.com/wiki/TMobile_G2:_Rooting
Checking it out now
iamnoobie said:
Use the following guide, it is incredibly simple yet swift. Contains root methods for both the DesireZ and the T-Mobile G2 :
Click to expand...
Click to collapse
I'm actually looking at that wiki right now. I just finished backing up all the contents on my SD card. I can't backup the apps on my phone since it's not rooted, and I can't use a backup app unless I'm root. So it looks like that is a catch 22. Personally, I don't mind wiping everything anyways since I'm going to be making the jump to ICS. I guess I'll have to beat all those levels in cut the rope again :crying:
@deadeye
actually, the only important bits are your contacts, sms's, phone logs, etc (if these matter to you), which i think you can backup via gmail. Additionally, any other (or all) files on the SD card, you should be able to just copy directly onto a folder in your laptop or desktop (see the post I made above). HTH.
timram said:
@deadeye
actually, the only important bits are your contacts, sms's, phone logs, etc (if these matter to you), which i think you can backup via gmail. Additionally, any other (or all) files on the SD card, you should be able to just copy directly onto a folder in your laptop or desktop (see the post I made above). HTH.
Click to expand...
Click to collapse
Thanks for that. I've now downloaded the Android SDK and am now trying to test the connection to my G2 using adb. So far, no connection. Grrrr. I'm looking around now to see how to get my phone detected by adb since it doesn't seem to have anything on the cyanogen wiki.
you downloaded adb.exe from within the sdk right? find the folder it is in (usualy platform tools) hold shift right click within the folder and choose open command here
now type adb devices, you should se some letters and numbers that means you good if not need to trouble shoot some more
alternatively you can change the path within enviromental variables so you can open a cmd anywhere
Sent from my HTC Vision using xda premium
HTC Sync
demkantor said:
you downloaded adb.exe from within the sdk right? find the folder it is in (usualy platform tools) hold shift right click within the folder and choose open command here
now type adb devices, you should se some letters and numbers that means you good if not need to trouble shoot some more
alternatively you can change the path within enviromental variables so you can open a cmd anywhere
Sent from my HTC Vision using xda premium
Click to expand...
Click to collapse
I tried the adb devices command and it didn't return any connected devices. Looking in the xda wiki, they are saying that I need to have HTC Sync installed. I'm downloading that right now. They probably should put that in the cyanogenmod wiki also.
I got my phone detected by adb! I did some preliminary checking and I think I should be good to go on rooting. I think I will root my phone tomorrow when I have plenty of time to troubleshoot any issues that my come up.
This is just the thread I was looking for. I'm also an old (60) tech-savvy guy who has never rooted his phone, and was nervous about which set of rooting instructions (cyan-wiki or Setherio/Strawmetal?; the latter is more recently updated, seems a bit more detailed, and has newer versions of some utilities) which recovery, ClockworkMod or ext4, and which ROM, Cm9 unofficial or mimicry or even AOKP...
You all seem to feel cyan-wiki instructions better (right?) ext4 and mimicry... Shall I go for it? Last suggestions?
Thanks,
Dave
Sent from my T-Mobile G2 using xda app-developers app
prairie-dad said:
You all seem to feel cyan-wiki instructions better (right?) ext4 and mimicry... Shall I go for it? Last suggestions?
Click to expand...
Click to collapse
Cyan wiki worked for me! (strawmetal didn't - I blame myself though).
ext4 and mimicry are what I'm running now (after going through CWM, CM 7.2 and CM9 RC1 & RC2) and I'm very happy with both. Mimicry is great!
prairie-dad said:
This is just the thread I was looking for. I'm also an old (60) tech-savvy guy who has never rooted his phone, and was nervous about which set of rooting instructions (cyan-wiki or Setherio/Strawmetal?; the latter is more recently updated, seems a bit more detailed, and has newer versions of some utilities) which recovery, ClockworkMod or ext4, and which ROM, Cm9 unofficial or mimicry or even AOKP...
You all seem to feel cyan-wiki instructions better (right?) ext4 and mimicry... Shall I go for it? Last suggestions?
Thanks,
Dave
Sent from my T-Mobile G2 using xda app-developers app
Click to expand...
Click to collapse
setherios guide is just for the downgrade process
the cyanogen wiki, xda wiki, and strawmetals pdf guide are all more or less the same guide, just writen a tad differently
as for the recovery 4ext is far superior but feel free to switch recoveries later if it complicates thing, very easy to do
as for a rom choice there are many good ones and it will be hard to recommened one so try a few, make nandroid backups, and see where your prefernce lies. if you like ics then my personal opinions are elitemod ics or mimicry, both are great. don't care much for sense so you will have to explore by yourself on those (you will need the dz hboot if you want any sense roms - easily done)
if you want gingerbread try ilwt or elitemod cm7 (this is still the rom I almost always use, even curently)
have fun, read, read some more, search when stuck... this is should all be easy as you say your tech savvy - happy flashing!
Sent from my HTC Vision using xda premium
minor glitches, but rooted and s-off fine
demkantor said:
setherios guide is just for the downgrade process
the cyanogen wiki, xda wiki, and strawmetals pdf guide are all more or less the same guide, just writen a tad differently
as for the recovery 4ext is far superior but feel free to switch recoveries later if it complicates thing, very easy to do
as for a rom choice there are many good ones and it will be hard to recommened one so try a few, make nandroid backups, and see where your prefernce lies. if you like ics then my personal opinions are elitemod ics or mimicry, both are great. don't care much for sense so you will have to explore by yourself on those (you will need the dz hboot if you want any sense roms - easily done)
if you want gingerbread try ilwt or elitemod cm7 (this is still the rom I almost always use, even curently)
have fun, read, read some more, search when stuck... this is should all be easy as you say your tech savvy - happy flashing!
Sent from my HTC Vision using xda premium
Click to expand...
Click to collapse
all went well till the very, very, very end. I went to reboot into clockwork recovery, and...nothing doing! holding down the trackball, volume down and power...and waiting and waiting...just got me into the bootloader with no option to go to recovery...just reboot, reboot the boot loader, and power down.
So I thought, maybe I somehow failed to get the recovery img where I wanted it...no big deal. I logged onto the old Market (this is 2.2, after all) and purchased 4ext (which is what seems to be everyone's choice) and installed it. Then I said I wanted to reboot with mimicry and gapps, hit "go," and...it rebooted into ClockworkMod Recovery...where it now sits, I assume backing up the existing system. Mimicry 1.3.2 and gapps images were sitting on my sdcard root, btw.
Very odd, and a little perplexing...I will wait it out a while before powering off and up again.
any thoughts? Must I remove clockwork mod manually (I assume that when I installed 4ext it made itselfthe default recovery method...) or does 4ext just sit atop Clockwork Mod...and what I am seeing now is normal...? I've been waiting a few minutes now, and see nothing but the Clockword Mod icon, the top hat.
Sigh...but pretty clearly almost all the way home.
Thanks to all,
dave
I've never used an app to install a recovery, always used fastboot.
But to answer your question 4ext does replace clockwork, it does not sit on top of it. Just downloading the app well... downloads the app. You must then go into the app and choose to download and install the recovery, after this from within the recovery flash your ROM (and gapps etc. If needed)
I have the 4ext app just for the purpose of supporting the Dev as anything that does me good deserves my money but I really have never bothered much with it so off hand I can't tell you the exact steps to do this but I'm sure it s very straight forward.
Good luck and let us know how all turns out
Sent from my Nexus 7 using xda premium
darn ClockWorkMod/4ext clash!
demkantor said:
I've never used an app to install a recovery, always used fastboot.
But to answer your question 4ext does replace clockwork, it does not sit on top of it. Just downloading the app well... downloads the app. You must then go into the app and choose to download and install the recovery, after this from within the recovery flash your ROM (and gapps etc. If needed)
I have the 4ext app just for the purpose of supporting the Dev as anything that does me good deserves my money but I really have never bothered much with it so off hand I can't tell you the exact steps to do this but I'm sure it s very straight forward.
Good luck and let us know how all turns out
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
Thanks...I sat and looked at it for a while, then hit power, and up came the ClockworkMod menu...and did nothing. When I asked _it_ to load a zip from the sdcard...it still sat there stupidly...nice menu but no action. so I rebooted with trackball/volume-down and power...and still can't get to the bootloader menu...the only way is to attach via usb, and do adb reboot bootloader...which gives me a bootloader menu showing no recovery app...just the same options as before. ugh. I wonder what the recovery.img is...? I went through the steps of installing 4ext...and it said it had installed itself.
well, I will poke around a tad more...midnight now...at least I have a working phone on 2.2, rooted, S-OFF, etc.
dave
---------- Post added at 07:33 AM ---------- Previous post was at 06:42 AM ----------
prairie-dad said:
Thanks...I sat and looked at it for a while, then hit power, and up came the ClockworkMod menu...and did nothing. When I asked _it_ to load a zip from the sdcard...it still sat there stupidly...nice menu but no action. so I rebooted with trackball/volume-down and power...and still can't get to the bootloader menu...the only way is to attach via usb, and do adb reboot bootloader...which gives me a bootloader menu showing no recovery app...just the same options as before. ugh. I wonder what the recovery.img is...? I went through the steps of installing 4ext...and it said it had installed itself.
well, I will poke around a tad more...midnight now...at least I have a working phone on 2.2, rooted, S-OFF, etc.
dave
Click to expand...
Click to collapse
Mimicry is booting now. All good. I ended up using the clockwork mod version, 3. something, that I installed when following (too slavishly?) the CM wiki's instructions (otherwise excellent!) Then (and now) I have problems booting into the bootloader, and it doesn't show a recovery option... Running 4ext (which I purchased) seems to be great (looks really useful) until rebooting...when CWM comes up instead.
I kept using volume up or down to pick what I wanted, then pushed the power button to select...wrong! It's the trackball you click, which I only hit upon by accident. Once I got that working, I flashed mimicry and Gapps, and I am off to the races again.
Thanks to all, but I want to figure out what is with recovery for the future.
What buttons do I push to get to bootloader...so far all I have gotten to work is via USB cable and "dab reboot boot loader."
dave

Rebooting over and over again

Hello,
sorry if u will find this thread to be repeated, but I was searching so much, and nothing helped me. After all, I think you are my last chance.
So to the problem:
One day I rebooted my Desire Z - rooted, CyanogenMod 7.2.0 RC# ( # is number can't remember which one - 2 or 3). Then I haven't paid attention to it and when I came home I noticed that phone is turned-off. So I turned it on: HTC white screen with green htc logo, CM loading screen and PIN code screen. So i entered PIN everything started loading ( i mean icons in notification bar appeared ) and then it happened: reboot. So again: logo, CM screen, PIN. I was bit slow so I didn't manage to enter PIN code and phone rebooted again. So it appears like it reboots in periods. So I start searching around the internet. I tried some things which I knew how to do, but I always found some problem. For example I can't mount USB storage while in CWM v5.0.2.7.
It appears to be boot loop, but I am not sure because I got to entering PIN code.
Help me, pls... I'm clueless.
P.S.: Sorry for my english, it's not my native language.
helper
YOU HAVE TO REINSTALL HBOOT AND FLASH A NEW ROM I WONT RECOMMEND GOING BACTO YOUR OLD ROM
get the hboot zip from http://www.virtuousrom.com/2011/06/t-mobile-g2-users-migrating-to-desirez.html put the file in the root of your sdcard hboot wiil recognize it and asked if you want to update after this remove the memory card use a card reader and on your pc delete the file put it back and enjoy dont forget to flash a new rom since this will delete every thing (oh use the card reader to put the file in you sd since you cant mount it from cmw
HIT THANKS IF I HELPED:good:
strip419 said:
YOU HAVE TO REINSTALL HBOOT AND FLASH A NEW ROM I WONT RECOMMEND GOING BACTO YOUR OLD ROM
get the hboot zip from http://www.virtuousrom.com/2011/06/t-mobile-g2-users-migrating-to-desirez.html put the file in the root of your sdcard hboot wiil recognize it and asked if you want to update after this remove the memory card use a card reader and on your pc delete the file put it back and enjoy dont forget to flash a new rom since this will delete every thing (oh use the card reader to put the file in you sd since you cant mount it from cmw
HIT THANKS IF I HELPED:good:
Click to expand...
Click to collapse
Umm, don't do that ^^^^^
But it does look like you have some serious issues, try this, boot into recovery and wipe cache and dalvik, now flash cm7 on top of it
If it still is causing issues then you need to do a full wipe (even better if you super wipe or fastboot -w)
Then flash ROM of choice, cm7 is great and there are many good Roms based off of cm7 I would also recommend, elitemod or ilwt for a couple nice options
Sent from my Nexus 7 using xda premium
demkantor said:
Umm, don't do that ^^^^^
But it does look like you have some serious issues, try this, boot into recovery and wipe cache and dalvik, now flash cm7 on top of it
If it still is causing issues then you need to do a full wipe (even better if you super wipe or fastboot -w)
Then flash ROM of choice, cm7 is great and there are many good Roms based off of cm7 I would also recommend, elitemod or ilwt for a couple nice options
Click to expand...
Click to collapse
I am at work right now and I left phone at home, but I can tell you I tried wiping cache. Problem appeared when I showed log of this wiping and there was something like app2s something with partitions or something like. I already formatted my card in PC (FAT32, not quick format, non-USB card reader - normal one). Should I try different card (card is gold card CID-11111111 (i don't know how many ones ))?
And if I will try what strip419 said, could something possibly happen to my phone ( in wrong way)?
Draftur said:
And if I will try what strip419 said, could something possibly happen to my phone ( in wrong way)?
Click to expand...
Click to collapse
I wouldn't bother with reflashing the hboot, I would try more 'non-destructive' solutions first.
Reflashing thé hboot is thé only way to format all partitions do away with any thing that could be doing this of cos you could brick your phone but if you follow rules its gonna be okay if you have adk on your pc then you could use the command tool to clear this but that could do worse damage if you are a noob so its up to you man try or keep looking for a. Solution that will end up like mine any way
Sent from my HTC Desire Z using xda app-developers app
strip419 said:
Reflashing thé hboot is thé only way to format all partitions do away with any thing that could be doing this of cos you could brick your phone but if you follow rules its gonna be okay if you have adk on your pc then you could use the command tool to clear this but that could do worse damage if you are a noob so its up to you man try or keep looking for a. Solution that will end up like mine any way
Sent from my HTC Desire Z using xda app-developers app
Click to expand...
Click to collapse
... No it's not, 4EXT Recovery -> Wipe/Format -> Format all partitions (except SDcard).
And how does hé get that recovery working when hé cant even boot or can hé flash it from cwm recovery?????
TRY
Sent from my HTC Desire Z using xda app-developers app
strip419 said:
And how does hé get that recovery working when hé cant even boot or can hé flash it from cwm recovery?????
TRY
Sent from my HTC Desire Z using xda app-developers app
Click to expand...
Click to collapse
You can flash recovery from fastboot or via PC10IMG.zip the same way doing a hboot reinstall would work, except in this case you don't go to such extremes to do the entire hboot over again, just the recovery and go from there. If it's an ENG hboot can use fastboot directly to flash the recovery.img, otherwise you pack it into a PC10IMG.zip and place it on the SD card.
Worse case scenario, the internal memory is fried, and attempting to do a full hboot reinstall would most likely brick it as opposed to only trying to flash a portion.
I had a repetitive reboot issue when flashing a previous ROM as well.
My noob solution was to put PC10IMG.zip back on the SD card, boot to recovery using ADB and then going through the whole process of reinstalling hboot and putting on a known ROM. Didn't brick mine and I'm new to this...
Could have done with finding this forum earlier.
all should know to be careful doing that method, if it were a stock rom and you simply flashed the pc10img.zip with radio hboot, etc in it you could get a brick easy, especially if you don't have a working rom with adb functionality.
what would happen would be (this is if you have eng s-off as most root users do) your phone would begin by flashing the bootloader, after this it would reboot and attempt to flash flash the radio, only problem is the new hboot would be ship s-on and therefore would get stuck, leving you a soft brick with a little luck it would be possible to fix this but it could be that it is unfixable depending on the exact circumstances
all this is just to say be careful what you do, noob or not, if you aren't 100% sure what you are doing when flashing firmware a brick is easy
Sent from my HTC Vision using xda premium
I have a similar problem but not sure if it's the same one... When I boot up my phone it goes through all the boot images fine, but when it starts it starts sometimes with my background showing and sometimes in a blank screen but both saying Android System at the top then shortly after shut down (usually shows shutting down not just straight up turns off) I have flashed new roms, reflashed backups, even got a jelly bean rom to go through the optimizing apps screen thing then would go to a blank screen with Android System on top again, and shut down.
Any help would be amazing! I've had my G2 since it's release and would hate to think it ran out of hearts :crying:
SoftAndDeep said:
I have a similar problem but not sure if it's the same one... When I boot up my phone it goes through all the boot images fine, but when it starts it starts sometimes with my background showing and sometimes in a blank screen but both saying Android System at the top then shortly after shut down (usually shows shutting down not just straight up turns off) I have flashed new roms, reflashed backups, even got a jelly bean rom to go through the optimizing apps screen thing then would go to a blank screen with Android System on top again, and shut down.
Any help would be amazing! I've had my G2 since it's release and would hate to think it ran out of hearts :crying:
Click to expand...
Click to collapse
You have my exact problem! Have you found a fix for it?
Magnumxxxl said:
You have my exact problem! Have you found a fix for it?
Click to expand...
Click to collapse
I also have the same problem. I attempted to use superwipe g2 to no avail.
I have clockwork recovery installed, and every custom rom I try to use seems to crash 5-10 seconds after finishing to loading screen for say cm7 or cm9.
I do not have a goldcard so am wondering what the best course of action would be. I am reluctant to follow the Hboot advise as the risks mentioned seem great.
everyone having these issues should go to irc freenode #g2root (just google it) and can receive real time help there. there are too many possiblities of what is going wrong and not enough information being given to help here well.
once things are figured out and all is working post back here to explain what the problem/fix was so future people finding this thread may have an easier time
Sent from my HTC Vision using xda premium
demkantor said:
everyone having these issues should go to irc freenode #g2root (just google it) and can receive real time help there. there are too many possiblities of what is going wrong and not enough information being given to help here well.
once things are figured out and all is working post back here to explain what the problem/fix was so future people finding this thread may have an easier time
Sent from my HTC Vision using xda premium
Click to expand...
Click to collapse
What is the hboot way? What does that do? I'll try it, my G2 is already useless now, anything that will fix it including a dangerous way tell me
well hboot (also known as bootloader or spl) is sorta like bios on a pc. but I don't suggest trying anything rash and can't help much unless I know paticulars of your situation, if you give that I can see what I can do, but like I said before if you would like some realtime help go to freenode.
if you want help here give me details, what exactly is your problem, what have you tried to do to fix it, what method specificaly did you use to obtain root, write down everything on your hboot screen (again you get there by holding volume down while powering on)
Sent from my HTC Vision using xda premium
demkantor said:
well hboot (also known as bootloader or spl) is sorta like bios on a pc. but I don't suggest trying anything rash and can't help much unless I know paticulars of your situation, if you give that I can see what I can do, but like I said before if you would like some realtime help go to freenode.
if you want help here give me details, what exactly is your problem, what have you tried to do to fix it, what method specificaly did you use to obtain root, write down everything on your hboot screen (again you get there by holding volume down while powering on)
Sent from my HTC Vision using xda premium
Click to expand...
Click to collapse
Well I bought this phone at a swapmeet last year for 40 bucks. Everything worked and it was on gingerbread last year. In a week I googled and found a way to root by using the thread here in the forum by using adb and downgrading to froyo which was a pain for a noob using adb I just add lol, I was on elitemod gb for many months, until I was playing music a few days ago it just rebooted itself and it wouldn't boot correctly. Here's how it goes, htc white screen, boot animation, then it says android system on the top left and all black under and it shuts itself off. EVERY rom I have flashed it does that, I wiped completely and use the superwipe g2+ and still no dice. I couldn't find the 4ext recovery, I need it as a flashable zip to try it.
not really you should be able to flash it via fastboot (which is my opinion the prefered way anyhow) just google search for the image.
but I still need to know what is on your hboot screen or I can't help much further
Sent from my HTC Vision using xda premium
demkantor said:
not really you should be able to flash it via fastboot (which is my opinion the prefered way anyhow) just google search for the image.
but I still need to know what is on your hboot screen or I can't help much further
Sent from my HTC Vision using xda premium
Click to expand...
Click to collapse
Do you have twitter so I can show you there with ease?

Categories

Resources