DInc will not go past boot screen. (failed rom install) HELP! - Droid Incredible Q&A, Help & Troubleshooting

So I'm new here, and to the whole phone tweaking thing. I've been messing with my phone lately and was happily content with my rooted phone and decided to attempt installing jagermod. admittedly i did not read up as much as i should and now after reinstalling i have managed to mess my phone up royally. so, i've tried recovering from a backup, i get the MD5 thing that never goes away, i've tried factory resetting, tried hard resetting, nothing works... it will not boot past the htc logo and then glitches out with black lines... anyhow any help would be great. thank you.
-jsav666

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

Mine did this also at one time and I found out it was a error from a incompatible kernal
Sent from my ADR6300 using XDA App

Black lines, or a black strip w/ white lines on either side?
If you see white lines on either side of black strip, sounds like a recovery type mismatch based on AMOLED or SLCD?
Regardless, search for the content from Doug Piston, who should be able to remedy what you are seeing. It may take resetting it to stock (RUU), but his thread(s) have the info you need.
hth

Related

[Q] Rooting random issues?

I'm pretty new to this rooting for Android, I recently got my Incredible.. I used unrevoked to root my incredible. I did it normally like USB debugging and all that. Soon as it started to root it, the phone rebooted itself like it was supposed too, got to the HTC Incredible screen (the first screen on the boot up) and black screen and white bars on the sides. Now I got this phone like November 27th.. and I'm pretty postive my screen is an SLCD? And that seems to be what the problem is with the black screen white bars.. Thing is, of course the black screen white bars stayed there, so I pulled the battery out and put it pack in. It loaded up normally and it seemed to be rooted fine. It had the Superuser (ninja). And everything was normal. I downloaded ROM Manager and then downloaded the Flash ClockWorkMod Recovery, and then I clicked on Cynagen Mod and went down to Google apps. Downloaded it, installed it, then it asked to reboot. ALL OF WHAT I JUST DID, (followed from The Start to Finish Guide to Rooting Your Android Phone, I con't post links yet) .. So as it rebooted it got the HTC Incredible screen (the first screen on the boot up) and it did the black screen white bars. I removed the battery either twice or three times.. And still nothing, I THEN FOLLWED THIS Incredibleforum dot com (I rooted and now I only see a black screen with white bars in recovery.) and went to the Hboot menu and went down to recovery and selected it. It rebooted and still black screen white bars at the HTC Incredible screen. I then tried his other method and went to download that file and went to unrevoked and did the custom recovery and put recovery in the file and plugged my phone in. ( He actually said to like check USB debugging, which I couldnt actually do because I couldnt get to my menu..) So then after plugging it in and showing the orange light for charging. It did nothing other then charge. I turned it on ( I'm pretty sure, it might have turned on by itself) and it worked. It got the menu screen. And everything was the same. ROM Manager was still there, same with superuser. And the 3 game apps that I downloaded before I rebooted for Google Apps. I haven't found Google Apps, I'm not really sure where Google Apps would be anyways.. But what I'm getting at here is, What actually happened????? Why those white bars?? And will this happen everytime I have to reboot? If someone could just give me their best answer or an explanation It would really help. I'm new to this stuff.. But I'm getting nervous with this black screen thing white bars.. and I'm debating wether to just unroot..(how easy is unrooting?).. But my phone is fine now, I haven't tried like downloading anything but everything seems to be working fine.. Where could I find Google Apps? And which ROM? Cynagen Mod Or Bugless Beast.. Please Help
You have an slcd screen. Your recovery is for smiled. Use unrevocks recovery for slcd screens. As I have read you need that one for recovery to work properly. I don't have an slcd so I don't know to much about that end
Just cruise the forums there is tons of info out there.
Sent from CM Nightly 11-20 using Tapatalk.
I had similar issues, and poster above is correct... I was able to flash a modified clockwork recovery to get it working with slcd...but I'm halfway afraid to try any ROM Manager abilities due to the different recovery :>
Just flash the modified Clockwork- very simple and works perfectly. I have the zip if you want it.
Ok cool can I have the zip file? And would I have to like uninstall anything in order to use revoked again?... and just a quick question.. 'recovery' is basically _______?
P.S. Whats like rebooting into recovery
mcolib8 said:
Ok cool can I have the zip file? And would I have to like uninstall anything in order to use revoked again?... and just a quick question.. 'recovery' is basically _______?
P.S. Whats like rebooting into recovery
Click to expand...
Click to collapse
http://www.megaupload.com/?d=7O9ZPP2T
You don't need to uninstall anything from your phone obviously, but I'd uninstall any unrEVOKed stuff from your computer before you do the new version. Recovery is basically the tool that lets you modify the phone. You go there to do nandroid backups and restores, and to flash zips. Let me know if you need instructions on how to apply the fix.
Yeah I'm new to this rooting stuff so if you could just give me a few instructions it'd be really helpful. thanks
mcolib8 said:
Yeah I'm new to this rooting stuff so if you could just give me a few instructions it'd be really helpful. thanks
Click to expand...
Click to collapse
1. Mount your phone as disk drive (I'm assuming you know how to do that, if not, lemme know)
2. Move the file to the root of your sd card (not in any folders) and make sure you don't re-name it at all.
3. Disconnect your phone, wait for the card to format, and then yank your battery.
4. Put the battery back in, hold Volume Down+Power.
5. You'll see your bootloader and it will find the file automatically, let it install it.
6. Once it's done, yank your battery again and repeat Step 4.
7. This time, choose not to install it, and instead choose Recovery- should load up Clockwork just fine. Easiest way to access Clockwork in the future is thru ROM Manager- there's an option to boot into recovery.
PS. might wanna check your clockwork version first thru ROM Manager- my version is 2.5.0.5 and I'm not sure if Koush has included the SLCD fix in any of the newer versions, so I'd make sure you have that version before doing this.
From what I gather, the black screen and white bars is the ClockworkMod recovery that you booted into. It works fine, but the SLCD is incompatible with the current ROM Manager ClockworkMod (I have it too, ADB works when it's running). So the display is the only thing messed up.
I'd love to get ClockworkMod to work correctly though. Anyone know how I can flash the recovery to Amon Ra, or get ClockworkMod working? I have a mod .zip file for Clockwork, but I'm unsure on how to use it.
Edit... responded too late. Thanks for the advice!
Sent from my ADR6300 using XDA App
ithuwakaga said:
From what I gather, the black screen and white bars is the ClockworkMod recovery that you booted into. It works fine, but the SLCD is incompatible with the current ROM Manager ClockworkMod (I have it too, ADB works when it's running). So the display is the only thing messed up.
I'd love to get ClockworkMod to work correctly though. Anyone know how I can flash the recovery to Amon Ra, or get ClockworkMod working? I have a mod .zip file for Clockwork, but I'm unsure on how to use it.
Sent from my ADR6300 using XDA App
Click to expand...
Click to collapse
I'm guessing you didn't read to the end of the thread before you posted
iBowToAndroid said:
I'm guessing you didn't read to the end of the thread before you posted
Click to expand...
Click to collapse
Didn't see it at the time. I'm still ungodly slow at typing on this, haha.
Do you have any advice on flashing with CyanogenMod? I read the wiki and it talked about updating a radio, but there were several options. What should I be looking for?
I'm kinda terrified trying it with these new SLCD phones, and any help would be greatly appreciated!
Sent from my ADR6300 using XDA App
ithuwakaga said:
Didn't see it at the time. I'm still ungodly slow at typing on this, haha.
Do you have any advice on flashing with CyanogenMod? I read the wiki and it talked about updating a radio, but there were several options. What should I be looking for?
I'm kinda terrified trying it with these new SLCD phones, and any help would be greatly appreciated!
Sent from my ADR6300 using XDA App
Click to expand...
Click to collapse
Sorry, I haven't found a ROM I like as much as stock Sense, so I just use that, but with my own mods. shipped-roms.com is a nice website.. Otherwise, almost any Android forum site will have a CM section since it's so popular..
iBowToAndroid said:
Sorry, I haven't found a ROM I like as much as stock Sense, so I just use that, but with my own mods. shipped-roms.com is a nice website.. Otherwise, almost any Android forum site will have a CM section since it's so popular..
Click to expand...
Click to collapse
Thank you!
Sent from my ADR6300 using XDA App

[Q] Try to restore backup --> Bricked!

Hiya,
Firstly, yes, I did a search. Here's my problem.
I used unrevoked and rooted my phone, so I could remove bloatware, tether etc. I then installed the hydra kernel to OC to 1.113 (stock volt), and this worked fine too. Couple weeks passed, everything's dandy, and today I decided to give Cyanogenmod 6.1 a try. So I get that up and running and decide that I like the Sense UI better, so I go into the ROM Manager app and tried to restore a backup that I made before installing the ROM. So the phone restarted, and then displayed the HTC Incredible logo and it stayed there.
I waited 30 minutes, pulled the battery, tried to boot. Same thing.
I held down vol down and went into HBOOT, and selected recovery. I get the black screen with vertical white lines on the sides. Waited thirty minutes, no change.
I then tried to reset factory settings through main HBOOT menu. Got the black screen with white stripes again.
So, it appears I bricked my phone. My theory is that the space on my SD card was too low and when I did the backup not all the information was saved, and when the phone tried to reset it pooped out, on account of the fact that the restore data was incomplete.
Thoughts? I do have the Best Buy warranty on this thing, so I'm wondering how that could offer some sort of solution (although I am pretty sure they will not like the fact that it has been rooted..). So in summary: Halp!!
Thanks yall.
IHateMayonnaise
Hater of Mayonnaise,
Have you ever been inside the recovery, working? I'm guessing no. The screen you described is an older clockwork recovery on an incompatible LCD screen. Try one of the newer recoveries. 2.5.1.2 should work work, as well as BAMod, and I believe Doug piston has one up. Rename the file to the proper PB31IMG.zip format and load from HBOOT. After that, look for your backup or install a new ROM.
You're not bricked till the phone doesn't turn on.
Sent from my ADR6300 using XDA App
PonsAsinorem said:
Hater of Mayonnaise,
Have you ever been inside the recovery, working? I'm guessing no. The screen you described is an older clockwork recovery on an incompatible LCD screen. Try one of the newer recoveries. 2.5.1.2 should work work, as well as BAMod, and I believe Doug piston has one up. Rename the file to the proper PB31IMG.zip format and load from HBOOT. After that, look for your backup or install a new ROM.
You're not bricked till the phone doesn't turn on.
Sent from my ADR6300 using XDA App
Click to expand...
Click to collapse
Yes I've been in it many times. When I first tried (while rooting my phone) I had the same thing happen, but I got the newer recovery or something (I forget what I did) and it went away. Why would this problem come back?
Maybe koush didn't fix the new one, so when you upgraded it broke. Go back to the older one that did work and all is dandy.
Sent from my ADR6300 using XDA App
yep it worked thanks!
lost android process
my phone gives the message android .process.acore has stopped unexpectedly.
cant get anything to work.
Just fyi. Bricked is completely dead. Not stuck at a boot screen.
Sent from my Sprint Galaxy Tab
+1 on this bricked is thrown around far too much
shoman24v said:
Just fyi. Bricked is completely dead. Not stuck at a boot screen.
Sent from my Sprint Galaxy Tab
Click to expand...
Click to collapse
Sent from my Incredible using XDA App
uwintoday said:
my phone gives the message android .process.acore has stopped unexpectedly.
cant get anything to work.
Click to expand...
Click to collapse
Which ROM?
Sent from my ADR6300 using XDA App
uwintoday said:
my phone gives the message android .process.acore has stopped unexpectedly.
cant get anything to work.
Click to expand...
Click to collapse
When does this happen? It started happening to me after I flashed data throttle zip on OMGB v6. only when I toggle 3G though.
Sent from my Htc Incredible using XDA App
android .process.acore
[ROM] SkyRaider Vanilla 3.0.1 RC3 ran this for a few days. did a back up and installed Incredible Gingerbread[Android 2.3 ran this for around twenty minutes. no back up done and tryed to install The Ultimate Droid 2.5.0. Thats when the problem started.
my phone has the andorid in the middle of the screen and says touch to continue. gives this error android .process.acore when android is touched. can only dial 911.
Since you didn't do a backup, make sure you do a complete wipe. If necessary, do a RUU and try again.
Sent from my ADR6300 using XDA App
android .process.acore
I dont see a complete wipe option.
I only have hboot options.
uwintoday said:
I dont see a complete wipe option.
I only have hboot options.
Click to expand...
Click to collapse
Factory reset, or something similar. Can't remember exactly. If not there, try fastboot.
Sent from my ADR6300 using Tapatalk
the ruu updates says loading PB31IMG.zip no image wrong image
Try going into the phone from safe mode. It might help you figure out if its the rom or an app on the rom.
Sent from my ADR6300 using Tapatalk
uwintoday said:
the ruu updates says loading PB31IMG.zip no image wrong image
Click to expand...
Click to collapse
Which means either your sd card is not FAT32, or you named it wrong.
Sent from my ADR6300 using Tapatalk
Or the file may have been corrupted during download. See if the md5 checksum matches that posted on the download site.
________________________________
Unrevoked forever
SkyRaider Sense 3.5
Radio 2.15.00.11.15
This is driving me crazy. No phone for days.
Ok i formated the sd card to fat32 via my computer sd slot. downloaded radio to computer from here
radios/2.15.00.07.28/ copy PB31IMG.zip to sd card via computer. with s off i did this , power off phone. Hold DOWN volume and press power. to accesses the hboot screen. hboot updateed PB31IMG.zip. yeah.
when i rebooted it goes into this endless loop of the red eye and the word droid.
Please advise.
Thanks
It isn't the radio you need to flash. An RUU is a stock rom as delivered by HTC. Try one of these.
http://shipped-roms.com/shipped/Incredible/
Sounds like you may need to reflash recovery too.
Edit: On second thought, you're recovery is probably ok. I was getting your problem confused with the original poster's problem.
http://www.koushikdutta.com/2010/02/clockwork-recovery-image.html
________________________________
Unrevoked forever
SkyRaider Sense 3.5
Radio 2.15.00.11.15

[Q] Please Help! Looping

Ok... here's the deal. I just decided to switch roms finally to see what is new out there. I had been running an old version of Uber Kingdom. Here is the problem I am having. It is boot looping. Relatively simple problem to fix usually. But wait, there's more! It is boot looping in every single rom I install. Sometimes it won't boot to clockwork properly either and I have to pull the battery. Is there someway I can fix this? Or is this a hardware problem (which I kind of doubt)? I just don't understand what the heck is going on. I have been flashing different roms left and right for the past few hours trying to get this thing to stabilize. Sometimes it will boot up into the rom, I will get mostly through the google accounts setup, and then it will restart, and then loop. Other times it won't even get past the white incredible screen, and then sometimes it will make it into the rom splash screen. I have attempted to install CM7 nightly, Uber kingdom, and Synergy so far. I can flash the new rom, I can mount the SD card in clockwork, but then it begins to loop again as soon as I leave clockwork.
Let me know if you need any other information.
Is there a way to just completely redo EVERYTHING, clockwork, rom, everything, just to make sure I have a nice clean slate?
Thanks a ton for reading through this novel. I am extremely frustrated.
~Will
PS, I may not get back to this thread until morning. I have to get to sleep for work. Sorry if I don't respond right away to information requests. Thanks again!
If you can mount the SD card, download the stock RUU from www.dougpiston.com, put it on the root of the SD card named exactly PB31IMG.zip, and boot into hboot to install it. Your phone should be restored to stock, a clean slate.
Tried a different SD?
Sent from my ADR6300 using XDA Premium App
How are you downloading and flashing the ROM? I had this problem when trying to do everything through Rom Manager. Even trying to flash in recovery with a ROM downloaded through ROM Manager would loop.
Update
Well, I was just getting ready to flash the original RUU when I tried one last time to restore my old Uber rom setup and it worked (whereas the last 3 times of doing exactly the same process didn't). It stopped looping at least, even though I am still running the same rom I was before. I think tonight I am still going to attempt to flash the RUU anyway and start over anew.
To answer the questions before, No, I did not try a different SD. I didn't know it could make that much difference. Still on the original one that came with the phone.
As the downloading and flashing process goes, I was downloading direct from the XDA forums on my laptop, then transferring the files via USB. I have never really liked using the Rom Manager. It cuts me out of the XDA loop and I don't get to see all the bleeding edge discussions, etc...
So I will try to flash everything new tonight, and then post my results for anyone who is curious. Thanks for the help guys!

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