[Q] Phone Bricked. Please help! - Droid Incredible Q&A, Help & Troubleshooting

Okay, so I was unrooting my droid incredible and it brought it to stock 2.1 i was trying to install the update.zip to update it to 2.2, but it wasnt working...so i tried installing the 2.2 RUU onto it...and now when i try to turn on my phone it always boots into the Bootloader...what should i do?
Note: LED charging light still comes on, and i can still go into recovery(stock recovery though since my phone is no longer rooted)
If theres no way to fix it, can i just play dumb and tell verizon its not starting up, because doesnt HTC have to reflash everything anyway for security purposes....the only downside though is they would probably send me an SLCD Incredible

First and foremost, your phone is not bricked... not even close.
Simply try reinstalling the 2.1 RUU. Being that it's signed by HTC, you should be able to do what you need to in the stock recoveryThat being said, your update.zip probably failed because your phone was restored to a state prior to the May OTA. Without being at the correct software version, you cannot use the update.zip to install Froyo.

If you get the bootloader, you should be ok. I think the zip has to be on the root of the SD and named update.zip for the stock recovery.
Sent from my DInc

Look in the android development forum for "the ultimate back to stock thread". download the "PB31IMGxxxxx" file there, rename it to just PB31IMG.zip and put it on the root of your sd card. Go into the bootloader and let it run the update. This will bring you back to a 2.2 stock. From there you can re-root and do whatever else you like.
Sent from my ADR6300 using XDA App

Okay, well it was the get back to stock thread that i followed...and i know that i was trying to do the update.zip from a version of android that was too old, because i was the one who posted a thread a few months back with the update.zip in it. However, i was obviously stupid enough to not save teh "May" OTA and now the link is dead. Some people were reporting however that it still worked without it, so i wanted to see for myself.
In any case, it seems that a 5 hour battery pull seemed to do the trick, go figure. Can someone explain to me what a battery pull on this kind of stuff makes a difference and why the length of time sometimes makes a difference as well?

Related

Did my little brother brick his Evo? v.OTA

He ran the original OTA update the day before yesterday, he didn't run it twice like everyone else that had issues.. He's not bricked in the "won't power on or boot" sense of the term, it WILL boot up. But it's pretty much completely unusable, it keeps trying to remove and install widgets on its own, the touch screen does the opposite of whatever he touches, swiping between screens hangs and sits in between each screen, it keeps opening the htc weather widget and won't let you back out of it.. voice search keeps popping up randomly. It tries to install the htc coin flip widget, a lot. It basically takes 5 to 10 tries to get anything to work right, and when something does work right it's only for a minute.
He wasn't rooted in any way, and he tried doing a factory restore through the settings menu, as well as formatting the sd card.
Radio shack has no eta on a replacement and sprint says to just return the phone and get a different kind of phone if they are out of evo's (seriously..? wtf).
You guys are smart, is there anything he can do to try and troubleshoot this?
there currently isnt a way to root after the ota update, so the suggestion to try some cooked roms is out the window.
i dont want to be the bearer of bad news, but it doesnt look good.
I think he can try restoring to factory.
Download this:
http://www.joeyconway.me/evo/stock/...Radio_1.39.00.05.31_release_171253_signed.zip
Rename it PC36IMG.zip and put it on the root of the SD card.
Turn off the phone, hold volume down and turn it on, it should boot into hboot, sort of a factory recovery
It will automatically detect the zip file and ask if you want to apply it. Select yes, and it should restore to factory.
If you continue to have problems, then there is probably something wrong with the phone and it'll need to be returned.
Hope this helps!
Could this in anyway void my warrenty or make sprint un-willing to give me a new phone/ repair my phone if this fix does not work?
if that is stock, they would not be able to find out even if it further messed up the phone by attempting that method
...err taking a look, if he has the newest ota, then I am not sure if that link will work because it is a lower version. you would need to find the one that is for 1.47...
I am not even sure if that would work, but hey it is worth a shot if the phone doesnt work already
Use this ruu
It'll bring you back to stock with the latest OTA included.

[Q] problem flashing myns rls4

help with flashing myns 2.2
Hey guys I've been reading the threads for a while and finally decided to root my evo last night using unrevoked..I made a nandroid as well ad a ti backup. I download myns last night and I think I put it into the root if my SD card according to directions I found using astro. I keep on trying to flash the Rom from my recovery and it goes about 3/4 of the way then aborts and states E:can't symlink/system/bin/ then e: failures at line 15. Then finally symlink busybox system : xbin.. I have not partitioned my SD card yet since I have read places there is no need to.. if anyone could shed some light on this is really appreciate it..BTW I'm on stock froyo atm
Hey guys I've been reading the threads for a while and finally decided to root my evo last night using unrevoked..I made a nandroid as well ad a ti backup. I download myns last night on my phone and I think I put it into the root if my SD card according to directions I found using astro. I keep on trying to flash the Rom from my recovery and it goes about 3/4 of the way then aborts and states E:can't symlink/system/bin/ then e: failures at line 15. Then finally symlink busybox system : xbin.. I have not partitioned my SD card yet since I have read places there is no need to.. if anyone could shed some light on this is really appreciate it..BTW I'm on stock froyo atm
are you s-off, what recovery?
Could be a corrupt download so I would try to redownload the rom and then reinstall. But what hardware version and hboot do you have?
Yes s is on..and the recovery is clockwork..
Wrong section bud, don't post questions in here especially since you already posted in Q&A. But you need your S-OFF thats why your having problems.
definitely need s-off, but have you tried to DL it again?
yea i thought it might be on the wrong forum so i reposted it there after, i apologize. how do i get the s off. Im not very good at this.. im interested in alt his stuff but not very good yet..i thought when i rooted it would turn s off..and yea ive tried installing it several time with no luck and same error
in another thread someone told me that its not working bc im still s-on..how do i turn that off.. hardware version 0003
First, you need to verify whether s is on or off. To do this, power down your phone, and hold the volume down button while you power it back on. It will boot into a white screen with 3 Androids on skateboards at the bottom. The very first line at the top of the screen will indicate if s is off or on.
If you rooted with Unrevoked, s should be off. However, I believe that before you can flash custom roms, you need to unlock NAND by flashing the engineering SPL onto your phone. On the same screen where you see if s is on or off, it needs to say Hboot: 0.76.2000 on the second line. If it has any other version of the hboot, you will not be able to flash custom roms.
This is what I did 1 week ago when I rooted my girl's Evo (also a 0003):
1) Ran Unrevoked for root.
2) Installed ROM Manager to flash recoveries & TI for back-ups.
3) Put Myn's RLS 4 on root of SD, and tried to flash via recovery; got errors similar to yours.
4) Downloaded engineering spl and placed on root of SD
5) Went back into recovery and flashed the eng. spl (at this point, I tried to boot it and the phone had no rom and would loop at the white HTC EVO 4G screen).
6) Got the phone back in recovery by doing a battery pull, powering on while holding volume down, and selected recovery.
7) From the recovery, I flashed Myn's RLS 4, my favorite kernel, a custom boot screen, and then rebooted.
8) Opened a beer and relaxed.
Don't forget to wipe everything twice! Also, before you flash the eng. spl, make sure you go into ROM manager and use the option to "flash an alternate recovery" so you do everything with Amon recovery which does a better job wiping. However, with Amon you cannot navigate through all the folders on your SD card to find what you want to flash. All flashable files MUST be placed in a .zip format in the root of your SD card (meaning out in the open and NOT inside any folders)
I hate using ADB, and if you follow these steps precisely, you will not need it.
Good luck!
i will try what you say to do..im just nervous bc that sounds complicated with my limited computer skills..i just dont understand why s-on is still there..isnt that the point of rooting.. can i unroot and run unrevoked forever?..is there any difference ?
firmbiz94 said:
i will try what you say to do..im just nervous bc that sounds complicated with my limited computer skills..i just dont understand why s-on is still there..isnt that the point of rooting.. can i unroot and run unrevoked forever?..is there any difference ?
Click to expand...
Click to collapse
Sent from my PC36100 using XDA App
Check your hboot version, and see what it is. If it is hboot 2.02, that is your problem. Unrevoked doesn't work (yet)with that hboot version. Currently, the only way to root that hboot version is the "boss" method. Can be found in the development section. You can check by doing the same thing the guy before mentioned, hold vol down, and power button together. Then you will see the version, at the bottom I think. When did you get your Evo? What hardware version are you? ( settings, about phone, hardware info) software info the same way, see if your build 3.29 or 3.30.
Edit: looks like the thread is now "like a pinecone" rather than "like a boss"
OP: Rooting does not turn s off. Root allows you to run programs that require root access. With root, you can run wireless tether, ROM Manager, Titanium back up, Shootme app for screen shots, etc.
However, to flash custom roms, you need to have NAND access and that is done by flashing the engineering hboot. You can find the engineering hboot here:
http://forum.xda-developers.com/attachment.php?attachmentid=342668&d=1276481802
Like k2buckley, if you have the 2.02 hboot, you need to follow this root guide:
http://forum.xda-developers.com/showthread.php?t=829045
It requires lots of ADB and this is for more advanced users. If you are going to try it, make sure your battery is completely charged before you start messing with it. I HIGHLY recommend you search YouTube for video tutorias on the root method you need to use and watch it from beginning to end (twice if you need to) to make sure this is something you feel you can do before you dive in.
Merged 2 threads.
I finaLly figured it out..I got frustrated and figured I'd flash unrevoked forever..I downloaded to SD card and flashed it..that turned nand off..then I flashed myns..and it worked..i couldn't believe it..thanks for your help guys..
I downloaded shootme to take a shot of my software to so you guys. But when I try to attach a file it doesn't do anything when I press search..anyways so far I really like the Rom and netarchy kernel..I think I'm gonna be addicted and flash often although I nandroid backed this one since I like it..any other suggestions for sense roms..I just want to have a blazing fast Evo..not sure if I wanna go aosp though..

[Q] Bricked Incredible and can't flash into recovery

So i rooted my brother's incredible and then he started installing system updates and now everything force closes. I put the zip onto the sd card but when I try to reboot into recovery, the screen blacks out with white lines down the sides...any suggestions? I told him that I would just probably have to find a way to take his phone back to stock...I'm a n00b myself so still trying to figure this out.
UCE HAMOCIDE said:
So i rooted my brother's incredible and then he started installing system updates and now everything force closes. I put the zip onto the sd card but when I try to reboot into recovery, the screen blacks out with white lines down the sides...any suggestions? I told him that I would just probably have to find a way to take his phone back to stock...I'm a n00b myself so still trying to figure this out.
Click to expand...
Click to collapse
It sounds like it's an slcd screen. Did you use the latest unrevoked? I think that comes with an slcd compatible clockwork.
Sent from my ADR6300 using XDA App
This is what i will guess happened...because it happened to me too.
1. when you rooted his phone, you never checked that recovery was actually worked.
2. It was when you tried to recover is when you discovered it didn't work.
As the previous problem is probably because of the slcd screen. Unrevoked 3.3 supports installing recovery to the slcd versions of the phone.
3. After you gave your brother the phone back, a few hours later the nagging "system update avaliable" pop-up well, popped-up and he in stalled it thus erasing the root.
you can simply unroot it again using Unrevoked, but you will simply continue getting the message unless u are familiar enough with adb or terminal to make it stop.
The first thing you need to do after you re-root it is download Rom Manager from the marketplace and BACK UP the current setup...
If your brother really likes the feel of the Sense UI then you can DL the Virtuous Rom straight from the app. Plus the Virtuous app includes the modded flash and hulu apps.
Or you can try many of the other avaliable Roms in the app. I reccomend buying the full app btw b/c its a life saver...or at the very least leave the ads on.
also..your phone is not "bricked". It is a simple matter of removing removing the battery and putting it back in to get you on the road to recovery...pun intended.
I also HIGHLY reccomend using the search function.
http://forum.xda-developers.com/showthread.php?t=855515
I hope this helps.
I didn't think the ota would work with a custom recovery.
Sent from my ADR6300 using XDA App
LoL, thats sorta the point...the OTA doesnt work. It frazzles the phone and removes the S-OFF
brownrt said:
LoL, thats sorta the point...the OTA doesnt work. It frazzles the phone and removes the S-OFF
Click to expand...
Click to collapse
Maybe that's the case with a stock rooted phone, but installing the ota from skyraider doesn't work and doesn't break root or soff.
Sent from my ADR6300 using XDA App

Boot Loops, forever.

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.

[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)

Categories

Resources