[Q] Can't make backup for DINC+SLCD - Droid Incredible Q&A, Help & Troubleshooting

My phone is working right now.
I read tons of forums and info about rooting - doesn't mean I know much about it.
If it helps in your replies, please note I am a linux expert and I don't need help understanding file systems, files, busybox commands, etc.
I followed jonsuh dot com's guide entitled /2010/11/ "root-your-droid-incredible-how-to" [I've heard I can't leave links, hence I obfuscated it]
phone is new, nothing installed (well actually, just ConnectBot for ssh, and the verizon&htc bloatware)
specs
htc incredible with SLCD
hboot 0.92.0000
radio 2.15.00.07.28
installed the modified android usb driver for my windows 7 32bit machine
started the reflash_package.exe from unrevoked
selected the cwm slcd recovery image
set my phone to usb debug
plugged in phone to pc
clicked ok in unrevoked to begin flash
6 minutes pass with reboots
hboot shows S-OFF and cwm boot
phone starts up, applications show superuser permission
ok fun, everything i read says to make backups before i do anything. note that all i want to do is remove the bloatware, that's the only reason i'm here!
so, i install rom manager from the market
i allow unknown sources at this point
i try to choose "Backup Current ROM" - error message says I need cwm recovery
so, first option in rom mgr, "Flash ClockworkMod Recovery", i select that one
I give it root access
Next, I select "Backup Current ROM"
phone reboots, screen bricked (black with white bars)
I freak out here ... bad (swore a couple times, not my style)
So, I go to hboot (cwm), select recovery, screen goes white with black lines on side and one at the bottom...I let it sit for 10 minutes
Pull battery
Reboot, phone works again
This time I return to ROM Manager, ROM Manager now things cwm recovery is installed
I select "Backup Current ROM"
Phone reboots
screen black with white bars on side
I reboot to cwm, select recovery, wait 6 minutes
Pull battery
Reboot, phone works again
And that's where I am right now. I'm not going to even touch ROM Manager until I feel confident I'm not going to jack up the slcd drivers again.
Thanks to everyone in advance!
-Payo

ok have 2 things for you to try
1: make sure you have enough room to create a nandroid backup on your SD, as this has cause problems for people in the past.
2: find amon RA recovery .img in that allows you to flash in h-boot
Being computer savvy like you say i would think you wouldnt pull the battery while its making a back up, i know it feels like its a long time when your screen is black but trust me its doing its thing u just cant see. But above all i honestly reccomend AMON RA recovery for the droid incredible as it fixes the issue with the slcd...hope this helps
http://forum.xda-developers.com/showthread.php?t=758874 heres the link for AMON RA just follow the flashing directions and remeber wont be able to use rom manager with this other than just to simply boot into recovery, but honestly I think rom manager isnt that useful anyway IMO

I'm amazed how much I see this advise I don't remember where I read it but there is a version of cwm that you can use when using unrEVOked, I am running it on my phone as I type this. I don't have it with me atm but ill post it and how to get unrEVOked.to use it.instead of the one it is installing.

putting it back together again
Austin:
I enjoy your jab at me for claiming to be savvy and yet careless for removing the battery during such a critical operation. I knew making such claims would surely invite the least of comments like yours . As you point out, it is difficult to wait patiently in high stress situations.
1. Make sure there is sufficient space on the SD card.
> There is 1.61 GB free of 1.81GB
> The SD is FAT formatted
2. Get AmonRa
> Roger. Download completed.
Should I use unrevoked to 'push' amonra to my phone? Oh, you say that site has flashing instructions. I'll review them.
I now have strong objections to using ROM Manager - I have been burned. So, if you say it is not that useful, well, I'm an easy sell. How do you recommend I create a backup?
jmc:
I used the version of cwm that was specifically built for SLCD screens. It was (to my best guess) ROM Manager's fault (perhaps it ships with a bad cwm that it flashed over my good one). Had I used a bad cwm initially with unrevoked (note, I did not run the default option with unrevoked, but selected a custom recovery image - as per jonsuh's guide that I linked) I would have had a screen-brick from the very beginning.
Austin:
I assumed that my new stock phone would not have HTC Sync (read somewhere to remove it if you've added it, which I haven't), but when I browsed the phone on my pc with a usb link, I saw that the phone's drive has HTC_Sync_2.0.40.exe. I would guess that this exe would be presented to my windows machine if I were to choose 'htc sync' on the phone when connecting (as opposed to charge only or removable drive). Am I wrong? Should I be concerned about this?
So my next step is to start reading about amonra - and then prepare to flash the drive.
Thank you very much,
Payo

yea just download the AMON RA recovery boot into H-BOOT (volume down+power) and it will automatically pick up the file and promt you to update simply click yes and after its done select recovery from H-BOOT menu and boom you will now see AMON RA then procede to complete your nandroid back up

http://www.incredibleforum.com/forum/htc-incredible-hacks/5721-i-rooted-now-i-only-see-black-screen-white-bars-recovery.html

In the crosshairs
"download the AmonR RA recovery boot into H-BOOT"
I think what you're saying is to copy the amonra to the sd card's root dir (named PB31IMG.zip) and allow update, then select recovery. My only concern -- what if something goes wrong? Heh, I just feel there is no safety net. Does a stock version PB31IMG.zip for my incredible+slcd exist out there for download? Or can I always depend on the 'revert to stock' option in h-boot?
"then procede to complete your nandroid back up"
With what tool? How? I've not found anything on this that makes sense to me.
Appreciated
-Payo

Yea creating a nandroid back up is an option within the custom recovery read up a little bit more so you understand vital parts or gaining root and flashing custom roms I suggest you scour the wiki
Sent from my ADR6300 using XDA App

payonel said:
"download the AmonR RA recovery boot into H-BOOT"
I think what you're saying is to copy the amonra to the sd card's root dir (named PB31IMG.zip) and allow update, then select recovery. My only concern -- what if something goes wrong? Heh, I just feel there is no safety net. Does a stock version PB31IMG.zip for my incredible+slcd exist out there for download? Or can I always depend on the 'revert to stock' option in h-boot?
"then procede to complete your nandroid back up"
With what tool? How? I've not found anything on this that makes sense to me.
Appreciated
-Payo
Click to expand...
Click to collapse
Ok you PM'ed me, so here's what I'll do:
Get fastboot, make sure it is in /yoursdk/tools
- fastboot oem rebootRUU
- fastboot flash recovery recovery-RA-2.0.img
- fastboot reboot
- done
Note that AmonRA and CWM are not compatible.
A side note: Without pointing a finger, I'd still think about whether you really need S-OFF or not, it's ment for developers and people that are ready to brick the phone for the sake of it.
Hope this helps

no s-off needed
1. Why fastboot and not an update drop on the sdcard/PB31IMG.zip? A lot of people opine the update method is preferred.
2. I'm nervous about ruu bc I've not read anything about it (and it takes me hours of reading before I feel safe to procede with these things).
3. In this thread I was pointed to RA 1.8.1, and you suggest 2.0. I saw 2.0 was the latest, but was concerned it was for the HTC GSM Desire only. (according the post I saw about 2.0 by amon_ra himself).
4. I don't care to test roms, only remove bloatware and have su -- I can see why I don't need s-off for this (but unrevoked just seemed the most reliable method at the time). Can I turn s-on without reverting to factory? How would you recommend I do this? [note, i am a developer, but anything to protect me from bricking!]
5. I've installed the CWM recovery...but (oh noob i am) does that mean i'm running cwm? I don't think I am. I don't want a custom mod. Clockwork is the boot level tool, and there is a mod, clockworkmod as well, right? Oof..given how much I've read, I would think this would be clear to me by now.
Again, much thanks to everyone,
Payo

If I am following what you are saying you are seeing the issues with the cwm that is suppose to work with SLCD screens then thats odd, I havent had any issues with it, besides rom manager not being able to reboot into recovery 9dont know if thats the recovery's fault though.) Just in case you havent tried it try this one though, its the one I was talking about.
For any future browsers, and just fyi, in order to change the recovery that is installed using UnrEVOked once the program is loaded up you click file in the top left corner and then select custom recovery, then browse to where you downloaded the recovery.img to.

you CANNOT use the clockwork mod recovery that comes with unrevoked for SLCD inc. results in black screen with white bars.

tylerwagler said:
you CANNOT use the clockwork mod recovery that comes with unrevoked for SLCD inc. results in black screen with white bars.
Click to expand...
Click to collapse
That's been established a while ago. If you read my post you will see that I have provided instructions on how to make it use the version that does work, that I included. Read before you post.

Related

[Q] need help rooting PLEASE

OK I just bought an Incredible a few days ago and tried my luck at rooting. I did a lot of research before hand and I am usually pretty good with this kind of stuff but obviously not good enough. I have tried everything I can find online but nothing seems to work properly. My phone came with stock 2.2 and I rooted with unrevoked 3. The rooting actually worked fine, there is s-off and I have the super user app, I have even been able to download the tethering app and use it. The main problem is that the Clockworkmod recovery screen does not pop up. No matter what I do, even right after the rooting process, my incredible goes to the HTC screen that is all white then a black bar or two appear on it, followed by a complete black screen with two white edges going down the sides. No green text nothing and then it just boots up normally. I have tried rooting on a mac, Windows xp (via boot camp), on a windows 7 computer. Nothing changes. I just wanna know is there something simple that I am just not doing properly, maybe some sort of setting that needs to get adjusted, I have selected charge only, remember this, and usb debugging. Please let me know if it is the fact that it is stock 2.2 and I have to wait until a new version of unrevoked comes out or am I doing something wrong. The phone works fine and everything for the time being but I want to be able to overclock, undervolt, remove bloatware, etc. I greatly appreciate any help that someone could give me. I am to the point of trying to find someone local and paying them, but it seems like no one nearby even knows how to do this or just has an iphone and can jailbreak that...lol....
So you ran unrevoked 3.21 first, which roots your phone and also installs clockworkmod. And then you ran unrevoked forever, which enables s-off. Correct?
How are you getting to recovery screen? Since you have superuser access, download the app Quickboot, which can reboot into recovery. If you flash everything right, and unrevoked had no issues, recovery should definitely be on there.
Download rom manager, titanium backup, and setcpu from market. Use TI to do a batch backup, use rom manager to boot into recovery. You will have to flash a different kernel to get anything out of setcpu, you could just pick a rom that has a modified kernel.
Sent from my ADR6300 using XDA App
To get to the recover screen from a powered off stand point:
1. Phone powered off
2. hold down vol -(volume down) and Power button at the same time until hboot comes up.
3. hit the vol -(volume down) once or until Recovery is selected and press the power button once.
4. Should show splash screen of HTC Incredible and then should be in ClockworkMod Recovery.
To get to recovery while phone is running you can download couple apps that will do it. Rom Manager will which you can reboot into Clockword Recovery and many more things. As mentioned before Quickboot will work also.
You say you just got it, is this one of the new Incredibles with an SLCD screen (instead of AMOLED)? They are the ones with "VW3" at the end of the sku. If so from what I have read in the last few days it seems clockworkmod recovery does not support these yet. There are a few posts on this forum about this, try searching "slcd incredible clockworkmod" or some variations. The general idea seems to be that amon ra recovery is working on these phones and that you gotta use that instead of clockworkmod for now.
I have one of these on order and should be able to mess with it this week ...

[q] new evo root method

I am currently running the 2.02 hboot and am looking for help on rooting to the Amon Ra recovery, or if anyone has a suggestion of a better running recovery. I also need to be able to download the files and step by step on how to root it. I had an evo with the 0.93 and was able to root it with ease but my 2.02 is giving me hell and i desperately miss my rooted evo!!!. I am not familiar with how to run ADB shells, nor do i even know what that is or where to find some of the files these methods say you need. Please!!!
STEP BY STEP FOR DUMMIES?!?!?!?!?????
Here is the link on how to root 2.02 hboot. The link also has the files that you need to root. read the thread and good luck:
http://forum.xda-developers.com/showthread.php?t=829045
Evo_tech said:
I am currently running the 2.02 hboot and am looking for help on rooting to the Amon Ra recovery, or if anyone has a suggestion of a better running recovery. I also need to be able to download the files and step by step on how to root it. I had an evo with the 0.93 and was able to root it with ease but my 2.02 is giving me hell and i desperately miss my rooted evo!!!. I am not familiar with how to run ADB shells, nor do i even know what that is or where to find some of the files these methods say you need. Please!!!
STEP BY STEP FOR DUMMIES?!?!?!?!?????
Click to expand...
Click to collapse
Facepalm...
DRAG AND DROP maybe?
alright, like i have said before. i am not that smart when it comes to this. When i was rooting my 0.93 this is step by step how i did it.
connected phone to comp.
usb drive selected
drag and drop unrevoked forever.zip and rage against the cage and pc36img
then went to unrevoked.com and ran the relash package.
now i re ran the pc36 img to unroot. (this is the only way i got my amon ra 2.2 recovery to work)
i then rebooted and hooked up to the comp. again and deleted those files from my sd.
Then downloaded amon ra package.
drag and dropped those files to the sd.
pulled the battery and then pushed volume down and power to the hboot screen,
then i let the pc36 try to load (which obviously doesnt because its already stock.)
Then went to recovery (had to do it a couple times to go through correctly) but it would then just go straight to the amon ra recovery screen and when fully booted would show a skull and crossbones (2.2 root) in the app drawer.
IS THERE NOT JUST A SIMPLE DRAG AND DROP METHOD?!?!?
I do appreciate the page suggestion however that is the page and thread that i have been trying to figure out for a while now.
Evo_tech said:
alright, like i have said before. i am not that smart when it comes to this. When i was rooting my 0.93 this is step by step how i did it.
connected phone to comp.
usb drive selected
drag and drop unrevoked forever.zip and rage against the cage and pc36img
then went to unrevoked.com and ran the relash package.
now i re ran the pc36 img to unroot. (this is the only way i got my amon ra 2.2 recovery to work)
i then rebooted and hooked up to the comp. again and deleted those files from my sd.
Then downloaded amon ra package.
drag and dropped those files to the sd.
pulled the battery and then pushed volume down and power to the hboot screen,
then i let the pc36 try to load (which obviously doesnt because its already stock.)
Then went to recovery (had to do it a couple times to go through correctly) but it would then just go straight to the amon ra recovery screen and when fully booted would show a skull and crossbones (2.2 root) in the app drawer.
IS THERE NOT JUST A SIMPLE DRAG AND DROP METHOD?!?!?
I do appreciate the page suggestion however that is the page and thread that i have been trying to figure out for a while now.
Click to expand...
Click to collapse
ok that will work to but heres the deal ALOT OF MISTAKES CAN BE MADE THAT WAY! if your not comfortable rooting your phone line by line your self check this thred out it might be your salvation[ROOT] ~~~ HTC EVO - Universal Auto Root ~~~ (updated for 2.02)(12/15/10)
alright well I have downloaded the autoroot file noted in your link post that you gave me and am to the step where you select the Auto root .bat and it should run.
However. it brings up the command prompt and just sits there saying checking for ADB.
I have followed each step so far to a T and it still sits there. I am on my own computer so i am using this as the administrator like it says to do if it just sits there and flashes the cursor in the prompt.
Is there something I am missing here?

[Q] Bricked if I cannot reach recovery?

Sounds like there weren't any ideas in Q&A for this one, and I haven't seen much in terms of not being able to access recovery, so here goes...
I was happily using CM7, and while reading through a Diablo III news page (hopefully it comes out soon ), my phone rebooted into a boot loop. Weird, but I figured at worst I would wipe data and reinstall a ROM. Unfortunately, I can't get into recovery any longer.
If I boot the phone normally, I see the white HTC splash screen for a few seconds, then it reboots. I can use HBOOT fine, but as soon as I try to reboot normally / boot into recovery / boot into Restore Factory Defaults, my phone will reset. Let me clarify...
Pull and replace battery
Boot into HBOOT (volume down + power)
Select Recovery
Phone reboots and reaches CWM Recovery 3 for about 1/2 second, not long enough for me to click anything
Phone reboots into boot loop
I've used HBOOT to flash to CWM Recovery 3.0.0.8, downgraded to the stock radio, run the 2.2 RUU. I'm still running up against the same boot loop problem.
I wouldn't be surprised if it was a hardware problem, but I'm anxious to hear if anyone has ideas to try first. Additionally, is there any way to restore to S-ON through HBOOT in case I need to bring this into a Verizon store? I have fastboot.exe that can recognize the device over USB while the device is in HBOOT, maybe this will help?
Thanks!
Current state: Ran 2.2 RUU, S-OFF, HBOOT-0.92.0000, AMOLED, 2.15.00.07.28 radio
Thanks again.
Had this exact issue while running cm7. First couple of from when it was crackflashers. I couldn't find anything to help or fix it. I got a new dinc because I can't afford to be without for long.
Good luck dude.
Sent from my ADR6300 using Tapatalk
Thanks for the note. Maybe my fate will be the same. Did you get any sympathy from Verizon?
Doesn't sound like there are even any suggestions using fastboot, lol. [crickets chirping]
Can you flash cwm 2.5.x and try? Not sure if it will help but worth a shot?
sent from a phone
Yeah take out battery, then pull out sd card put it into a adapter and insert it to ur pc. Then find the file that was shipped specifically for ur device it looks something like this PC130mg.zip or some crap like that anyways put that on the root of your sd card. load ur card back to your phone now into hboot(volume down plus power) mode. Your phone will auto detect that file and start to ask if u want to install update say yes boom it will flash back to stock.....however my only concern would be if u need to turn s-ON before u do this.
I did this for a evo 4g and it worked but I turned s-ON first as it was in the instructions I was following. I think maybe the update file checks to see if ur S-off or on. But don't quote me on that.
Sent from my PG06100 using Tapatalk
popasmurfn23 said:
Yeah take out battery, then pull out sd card put it into a adapter and insert it to ur pc. Then find the file that was shipped specifically for ur device it looks something like this PC130mg.zip or some crap like that anyways put that on the root of your sd card. load ur card back to your phone now into bootloader (volume down plus power) mode. Your phone will auto detect that file and start to ask if u want to install update say yes boom it will flash back to stock.....however my only concern would be if u need to turn s-ON before u do this.
I did this for a evo 4g and it worked but I turned s-ON first as it was in the instructions I was following. I think maybe the update file checks to see if ur S-off or on. But don't quote me on that.
Sent from my PG06100 using Tapatalk
Click to expand...
Click to collapse
Yeah, I agree with popasmurf. Put the PB31IMG.zip on your sdcard. Then let hboot discover and update it. It'll be back to stock and youll have to reroot but better than a paperweight.
You can find the image here -----> http://dougpiston.com/?page_id=108
I'm assuming you have a dinc.
sent by carrier pigeon
hope that helps
@phazeone let's say he just does that. Now his phone reboots and is on stock and looses his root, now he can root it again and then turn the S-on by the single file flash from recovery mode, and then use the update file again to flash the phone back to normal stock without root ( if he was taking it back) so whenever u want to manipulate the S security u must be rooted correct?
Sent from my PG06100 using Tapatalk
popasmurfn23 said:
@phazeone let's say he just does that. Now his phone reboots and is on stock and looses his root, now he can root it again and then turn the S-on by the single file flash from recovery mode, and then use the update file again to flash the phone back to normal stock without root ( if he was taking it back) so whenever u want to manipulate the S security u must be rooted correct?
Sent from my PG06100 using Tapatalk
Click to expand...
Click to collapse
You are correct.
popasmurfn23 said:
Yeah take out battery, then pull out sd card put it into a adapter and insert it to ur pc. Then find the file that was shipped specifically for ur device it looks something like this PC130mg.zip or some crap like that anyways put that on the root of your sd card. load ur card back to your phone now into hboot(volume down plus power) mode. Your phone will auto detect that file and start to ask if u want to install update say yes boom it will flash back to stock.....however my only concern would be if u need to turn s-ON before u do this.
I did this for a evo 4g and it worked but I turned s-ON first as it was in the instructions I was following. I think maybe the update file checks to see if ur S-off or on. But don't quote me on that.
Sent from my PG06100 using Tapatalk
Click to expand...
Click to collapse
phaze one said:
Yeah, I agree with popasmurf. Put the PB31IMG.zip on your sdcard. Then let hboot discover and update it. It'll be back to stock and youll have to reroot but better than a paperweight.
You can find the image here -----> http://dougpiston.com/?page_id=108
I'm assuming you have a dinc.
sent by carrier pigeon
Click to expand...
Click to collapse
Thanks for the replies.
I tried this method to flash back to the stock 2.2 image before I started this thread. That's what I meant by "I've used HBOOT to ... run the 2.2 RUU." The stock image seemed to install properly in HBOOT. I have evidence that it successfully went back to stock, since I get the original ! triangle graphic instead of CWM when I try to enter recovery from HBOOT. However, I only see the graphic pop up for a brief second before it reboots again. Trying to boot into recovery or the ROM itself still result in a reboot.
I cannot achieve S-ON without having access to recovery, at least there's no way that I've found to do it through HBOOT.
Any other thoughts? I think it's a hardware problem. It appears the phone is back to stock (except it's still S-OFF), but everything outside of HBOOT causes a boot loop. I stopped in at Verizon this afternoon and they'll be sending a new phone to arrive by Tuesday. At this point, it'd be nice to try all avenues of repair for the future benefit of others that run into this problem.
Probably bad memory chips on the phone. Since it happened all of a sudden during normal use it usually indicates hardware failure.
That is pretty much what I determined. Bad hardware. Sorry for your trouble but is nice to know I'm not the only person to ever have this. Also nice to know I didn't miss something that could've brought it back to life.
I filed an insurance claim. Figured since I have had it for years and never used it I'd take advantage.
Sent from my ADR6300 using Tapatalk
You can boot your phone like regular right? Just let it launch up or do you get loops?
Nevermind i see what ur saying. when i was flashing incorrect kernals i would get the same behavior from my phone. So i suggest you take phazeones link and try that file.Because u might have the incorrect file. There might be more than meets the eye make sure u got the right file.
When i searched for my zip file for my evo there was like 4 of them. They had to match what was said in the upper left corner of my hboot screen. So let me knoe if it worked
I wonder if he could just wipe that SD card, place a new Rom etc on it and reinstall. Bricking displays no response you've got a better shot at recovering course your SD card/battery could be bad
Since you're trying to flash the 3.x.x.x version of CWM, that may be your issue. Here's a zip for 2.5.0.5, one of the most stable earlier Recoveries. Flash through hboot as per usual.
If that doesn't work, (I'm assuming that you can boot the phone normally at this point) try re-rooting with the Unrevoked tool.
Then use Rom Manager to flash a newer Recovery (be sure to check Erase Previous Recovery under Settings). If that still doesn't work, I'll see about packaging an RUU in a PB31IMG.zip with a valid version of CWM as the recovery.img within that zip. I'm not sure about the practicality of this final option, but if it comes down to it, I'll attempt to package that up for you.
This sounds incredibly frustrating. Thus my interest in the matter.
There's gotta be a way to fix this... even if it's just long enough to get S-On and keep your warranty valid.
Sent via my Incredible CM7 Gingerbread sorcery.
Crans said:
I wonder if he could just wipe that SD card, place a new Rom etc on it and reinstall. Bricking displays no response you've got a better shot at recovering course your SD card/battery could be bad
Click to expand...
Click to collapse
This would work if he could access CWM Recovery, but he can't, thus the issue.
I wonder if he could mount something from within hboot and replace the binary code for the recovery image with a bunch of zeroes and then try flashing another through hboot again.
Sent via my Incredible CM7 Gingerbread sorcery.
I was JUST about to post the same topic when I came across this. I have done the stock image restore, restored BACK to hboot 0.92, back to the most current INC radio, and have tried flashing CW3.0 and Amon_RA. Everything flashes fine but the boot loop continues and if I try to enter recovery, it lasts maybe one full second before rebooting again. The only thing that I can think of that would create this situation for me was that earlier I was trying to update the PRL via *228 on MIUI but the dialpad never popped up so I hung up.
popasmurfn23 said:
So i suggest you take phazeones link and try that file.Because u might have the incorrect file. There might be more than meets the eye make sure u got the right file.
When i searched for my zip file for my evo there was like 4 of them. They had to match what was said in the upper left corner of my hboot screen. So let me knoe if it worked
Click to expand...
Click to collapse
I'll take another crack at it, but I don't think I had gotten the wrong image. No worries though, it's easy enough to try again using the link on page 1 directly. Can't hurt, right ;-)
RegnierD said:
Since you're trying to flash the 3.x.x.x version of CWM, that may be your issue. Here's a zip for 2.5.0.5, one of the most stable earlier Recoveries. Flash through hboot as per usual.
Click to expand...
Click to collapse
Sure. Once again, worth a shot.
RegnierD said:
This sounds incredibly frustrating. Thus my interest in the matter.
There's gotta be a way to fix this... even if it's just long enough to get S-On and keep your warranty valid.
Click to expand...
Click to collapse
Thanks for the sympathy . Like I mentioned, I visited the Verizon store and a new one is on its way... doesn't that mean that it doesn't matter (other than for science sake) whether this gets S-On or even fixed?
[waiting for flash of build-3.26.605.1-release-152016-baseband-2.15.00.07.28-hboot-0.92.0000_PB31IMG.zip]
It just seems unlikely that this is a problem with flashing the wrong recovery, or the wrong stock image, since booting into recovery and booting normally both exhibit the same behavior. If I could boot normally into recovery but not boot into a stock image, I would suspect that I had flashed the wrong image. Since both have the same problem, I think it might be something else.
[finished flashing build-3.26.605.1-release-152016-baseband-2.15.00.07.28-hboot-0.92.0000_PB31IMG.zip]
Same behavior. White htc Incredible splash screen -> darkness for a second (presumably while the ROM tries to boot) -> reboot.
Alternatively, HBOOT -> Recovery -> White htc Incredible screen -> Triangle / ! error screen for a half second -> reboot.
[finished flashing CWM 2.5.0.5]
Same behavior:
HBOOT -> Recovery -> White htc Incredible screen -> CWM recovery 2.5.0.5 for a half second (this confirms that it flashed properly) -> reboot.

[Q] Unique problem(Stuck at splash screen.Cannot get into recovery mode, only Hboot

I thought I had it all figured. Root, with Clockwork Recovery, Rom Manager. Nothing could go wrong. Now I am stuck at the splash screen with no Clockwork Recovery.
I searched fourum after forum to find a solution, but mine seems to be different. Just so you know I am 21, and a freelance computer technician so I am not afraid of the command line
What have I done to my device:
=Originally it had 2.1
=I rooted the phone via exploid method
=I installed CyanogenMod 6.1.1
+My computer only recognized my phone in HBoot mode, I think usb debugging is turned off though because I cannot acces my sd while it is in my phone.
I do have a microsd card reader
+I tried Esprimg.zip updates. It works .but I still cannot get into recovery mode.
For extra precaution, I backed up all of my sd card data on my pc.
Symptoms and problems:
+I am stuck at the white My tough slide 3g splash screen.
Holding up and power for at least 30 seconds does not get me in recovery mode. All I see is the white My tough slide 3g splash screen. No Black screen with a triangle(Biggest Problem)
+Holding down and power does get me into the HBoot.
+The recovery option will make the Mytouch slide reboot, but it will freeze at the splash screen.
+The clear storage option executed, but it did not solve my problems.
+I have also removed the battery, sim, and sd card.
Summuaray-
I need to get Into Recovery mode, but when I press up and power it does not work. I only see a white.I never though there would be a day where I could not get into recovery.
Also, I constantly charge the device so it wont turn off during an update.
Do you have S-OFF? If you do it should not be hard to recover.
If you don't I can't think of any other method now. But just to make sure which Esprimg.zip method did you tried? Because that should work in the first place.
Mine says S-On
Esprimg.zip
I used my microsd card reader to put esprimg.zip on the sd card. Boot the device while holding down and power. I let the phone check for the esprimg.zip and then the update was successful.
Conclusion:
I hold up and power and i cannot access recovery mode.
Possible causes:
By doing the clear storage, would that change my device to s-on. Honestly I never noticed s-on until now. However, I was able to root and get clockword mod 6.1.1 and it ran smoothly for a weeks.
darko4 said:
By doing the clear storage, would that change my device to s-on.
Click to expand...
Click to collapse
No. Only by flashing another bootloader will you get S-ON back. You probably did not have S-OFF before anyways but FYI Esprimg.zip does flash the bootloader so you're stuck on S-ON for now.
If the Esprimg.zip update method was successful it should have flashed back the stock recovery for you. I can't think of anything that could go wrong at this point except that u have a bad or corrupted Esprimg.zip. Did you use the champion build or the ENG build? If me I'd try to download it again and give it another go.
Good luck!
Ok so Esprimg.zip may be bad, and pretty much that is my only saviour;ok I understand.
I was using Esprimg.zip from other guides. Those were 137 mb
This time I used the one from here.
HOW-TO * Flash the Eng-Release to the Slide *6/15/2010
http://forum.xda-developers.com/showthread.php?t=703076
I am going to assume this the the eng build. It was 137.1 mb.
If this does not work the I guess I have to go champion build.
------------------------------------------------------------------
Failed
Champion build esprimg.zip is next.
A few more ideas.
manually install the recovery using fastboot.
troubleshooting without simcard?
My spl s-on so would that be possible?
Is there a way to maybe re root?
I read in one post that a guy sold it on ebay..i would hate to do that with just a month of ownership. would Htc make a warranty request even though I bought it used. Besides you only see bootloader and hboot spl s-on so how could they tell?
So you reach the screen where it asked you whether you want to install the update, you choose "yes" and it goes on to flash everything, radio, bootloader, yada yada, and it fails to boot?
Basically with S-OFF you can boot into fastboot and run
fastboot flash recovery recovery.img
in this case recovery img is CWM recovery. With S-ON fastboot flash is disable so it's not possible.
EDIT: If you do have the champion build on it's basically stock.
I have this exact same issue right now, I've tried the champion and engineering builds of ESPRIMG but with no success. I can't think of anything else that would be causing this in the first place, which is making it so difficult to troubleshoot. The only difference is that I was using CM7 instead of 6, but the exact same thing is going on. I have tried everything that the OP has with no luck. The only possible cause I can think of is that something was somehow corrupted while the phone was on and sitting on my table...because when I picked it back up, it was off and when I tried to boot, I got splash screen... Any other ideas?? I'm all out and just sitting here waiting for some genius light bulb to go off....attic's kinda dusty though..
With S-ON fastboot flash is disable so it's not possible.
So basically these are my options
esprimg.zip (if that does not work then use different)
Hboot clear memory,
with S-ON I have limited option
and keep it charged.
Although with fastboot and s-on is there something I could do?
Would rerooting be an option
darko4 said:
Would rerooting be an option
Click to expand...
Click to collapse
I don't see a root method in the forum that does not involve booting into a usable system.
Wait, you guys were able to flash the esprimg.zip right? Because in the guide when it says it requires root it's for flashing the mtd0.img first before rebooting into HBoot. Since you don't have a working system you cannot do that and if HBoot refuse to take your esprimg.zip then you need to do the Goldcard method. Otherwise I don't see why having root will make a difference.
So at this stage of the game I should do this..
1.get on my knees
2.put my hands together.
3.and just pray?
ok all jokes aside. Continue to try Esprimg.zip and update(all are successful but I still get splash)
I can't change my recovery since I have s-on
and no way of getting s off since i cant get in the phone, not even recovery,just h boot
So in a sense i have a lovely soft bricked mytouch 3g slide.
Later I might compose a list of the programs i had on the device, but i doubt that would make a difference. I appreciate the help and assistance, I am going to click the thank button for you gents.
In the mean while i got a tmobile comet for 136 one day shipping..No rooting on this one cause finals are coming and I do not have time to troubleshoot for hours. I love android cause of custom roms, but not being able to get in recovery mode...ah say no more. I am going to be one of those people who just downloads free software and complain to phone carriers about OTA.
Same here. I held off rooting and all until my exams were over because I know I'm going to go all the way until I get S-OFF.
I know many discourage S-OFF because it can potentially brick during the process but if you do read up and follow instructions very carefully it is really not that risky. And it'll be very useful in situations like this.
I'm sorry to hear you have a soft-brick. Maybe a dev will stumble upon and provides new insights but I afraid this is all we have in the forum for now.
to be honest i skimmed through the post, and im sure you did try this but just want to ask have you tried the official RUU update to see if you can get things back up running that way?
yeah I understand following directions carefully, but when you follow all of directions and get it working,and make backups, but then you turn the phone off and then turn it on. Then all of this happens.
ah let me stop my whining and download more esprimg.zip .
I just want to know what caused it. was it an application, cause if that is the case then I want to know so no one else get hurt.
(one interesting note, avg antivirus said my device was infected with viruses. It said with the apps, I did not clean it. i uninstalled avg. I presumed it was a false alarm cause the phone is rooted with applications with high privileged) Oh well
---------------------------------------------------------------------------------------------------------------------------------------------------
oh well. back to the esprimg.zip
never tried RUU, if it comes in a esprimg.zip then i guess i can try. if not then i do not know how to use it with mine in its current state
S on (so no advanced fast boot options
Hboot only
no recovery.
clear memory
only productive thing is successful esprimg.zip updates
its the official update to froyo, and need HTCsync and the RUU from htc how the installs procces goes i dont really know, but im sure there is a RUU update that you can use to update via bootloader,
ok i got htc sync
and the official exe.
my pc only detects the device in hboot. The device will read usb hboot.
1 might fiddle around for 20 mins to see whats what.
.
If it was like a esmprimg.zip then it would seem more feasible.
goood luck hope you get your phone back up and running
well a week ago it finally booted. I felt that it was a fluke so I pressed the power button to reboot. I tried to turn it back on then it was stuck at the splash screen.
I am now starting to think it is a hardware problem. Either way the unrooted tmobile comet,yes it is small, is doing wonders. The battery life is way better then a iphone 3g.
Just remember guys, if you get an android phone, make sure it is a popular one. That way you are more likely to get support because of the bigger fan base. Oh well it was fun while it lasted. The only thing I hate is that i could have gotten an xbox 360 for the same price. oh well, thanks for the assistance. i will lets you know any further updates.

Incredible won't boot into CM7 or Recovery

I've look around for over an hour and can't find anything quite like this. I didn't try to change anything or put on a new rom - nothing - it just stopped working.
I've been running CM7 for months just fine. I've had to re-install it a few times due to various random errors and whatnot but for the most part it has been fine.
Phone was working fine. I plugged it in and went to bed.
I woke up this morning to my phone getting to the white HTC Incredible page and then perpetually rebooting.
I can't get past that either to get into recovery or CM7.
I can get into hboot but I have no idea what to do there.
What the hell could have happened over night?
Any chance this can be fixed or is it bricked?
This is a known issue. This happened to my phone and 2 subsequent replacements before I got one that it didn't happen to.
I'd call Verizon or take it in - hopefully you're still in your warranty.
thumpernc24 said:
I've look around for over an hour and can't find anything quite like this. I didn't try to change anything or put on a new rom - nothing - it just stopped working.
I've been running CM7 for months just fine. I've had to re-install it a few times due to various random errors and whatnot but for the most part it has been fine.
Phone was working fine. I plugged it in and went to bed.
I woke up this morning to my phone getting to the white HTC Incredible page and then perpetually rebooting.
I can't get past that either to get into recovery or CM7.
I can get into hboot but I have no idea what to do there.
What the hell could have happened over night?
Any chance this can be fixed or is it bricked?
Click to expand...
Click to collapse
If you can get into hboot. you should be able to RUU to stock and re root.
synisterwolf said:
If you can get into hboot. you should be able to RUU to stock and re root.
Click to expand...
Click to collapse
tried to do that too at the hboot menu and I get the same problem.
I have the extended warranty from Verizon but are they going to check if it is rooted?
thumpernc24 said:
tried to do that too at the hboot menu and I get the same problem.
I have the extended warranty from Verizon but are they going to check if it is rooted?
Click to expand...
Click to collapse
if you can get into hboot they will see at the top it says S=off. you might want to try to get it back to S=on
synisterwolf said:
if you can get into hboot they will see at the top it says S=off. you might want to try to get it back to S=on
Click to expand...
Click to collapse
any clues how to do that?
i've been looking around like crazy and can't seem to figure it out.
Feel dumb - I just need to get this done so I can take it in and get a new phone - it is driving me insane!
In order to get s-on you will need a custom recovery installed and then use the s-on tool provided by unrevoked. So you will need to flash a custom recovery thru hboot and then flash the s-on tool thru recovery, and then ruu either thru hboot with a PB31IMG.zip, or with a ruu.exe with your pc. You can get the recovery image and ruus from here http://www.pvillecomp.com. You can get the s-on tool from the unrevoked forever site.
thumpernc24 said:
any clues how to do that?
i've been looking around like crazy and can't seem to figure it out.
Feel dumb - I just need to get this done so I can take it in and get a new phone - it is driving me insane!
Click to expand...
Click to collapse
same way you got it off.
unrevoked.com has this info see link below. i also quoted the area you need to look but read it all please.
http://unrevoked.com/rootwiki/doku.php/public/forever
Installation Instructions
To install unrevoked forever on your phone, perform the following steps.
If your phone does not already have a custom recovery, use unrevoked3 to root your phone.
The installation process cannot take place if the phone does not have a custom recovery installed.
Download the most recent ''unrevoked-forever.zip'' to a temporary location on your computer.
The update can be installed like any custom .zip file. Simply flash it from your custom recovery. Both Amon_RA and Clockworkmod Recoveries support custom .zip installs from the sdcard.
Either select the option to install a .zip from your SD card, or apply it as an update.zip as follows:
Place the update.zip file into the root of your SD card. You can do this with adb with the command: adb push unrevoked-forever.zip /sdcard/update.zip
Reboot your phone into recovery mode. You can do this by removing your phone's battery, holding down the VOLUME DOWN button, and inserting the battery; at the menu, press VOLUME DOWN to highlight recovery, then press POWER to select it.
Did you read the important safety information above?
Do so now before continuing.
Select apply sdcard:update.zip from the menu.
Press VOLUME DOWN until Yes is highlighted, then select it.
Review the output to determine if there were any errors.
If messages beginning in E: appear, stop! If possible, join IRC for support.
Restart the phone normally, then reboot the phone into the bootloader. This can be done by holding VOLUME DOWN while powering the system up. Observe at the top that S-OFF appears.
Optional, but recommended: show your support (and your S-OFF bootloader) by flashing a custom splash screen!
"How can this be removed or undone if I need to take my phone in for service?
Download the latest ''S-ON'' tool to a temporary location and follow the installation instructions above to run it. Once your phone is S-ON, you may lose root permanently if you install an official update."
---------- Post added at 12:10 PM ---------- Previous post was at 12:01 PM ----------
i also found this video for you. i hope it helps.
http://androidforums.com/incredible...ideo-howto-unroot-incredible-downgrading.html
I tried that and it didn't work
I followed the video and now my phone is even more messed up.
Won't get past bootloader, still have s-off.
now when i power on it boots straight into bootloader so it's really obvious. Wonderful. fml.
I obviously can't fix it and I need a phone. I'm going to the verizon store and see what they say
thumpernc24 said:
I tried that and it didn't work
I followed the video and now my phone is even more messed up.
Won't get past bootloader, still have s-off.
now when i power on it boots straight into bootloader so it's really obvious. Wonderful. fml.
I obviously can't fix it and I need a phone. I'm going to the verizon store and see what they say
Click to expand...
Click to collapse
So you can get into hboot and your s-off, but you cant get clockwork recovery to flash as a PB31IMG.zip? What does it say when it auto searches for the file? You say you cant get into recovery, what exactly happens when you select recovery in hboot?
Same thing it does when it tries to regular boot.
Well - it did before i tried to apply that PB file in Hboot. Now it doesn't do anything at all period.
Verizon didn't really look at it and just said they would warranty it for me. Woo!
thumpernc24 said:
Same thing it does when it tries to regular boot.
Well - it did before i tried to apply that PB file in Hboot. Now it doesn't do anything at all period.
Verizon didn't really look at it and just said they would warranty it for me. Woo!
Click to expand...
Click to collapse
Well if they cant get into hboot they cant check if you are rooted so your good to go. once it gets to factory they just plug it into a machine and it reflashes everything so they dont check it.
as I said before - when I select recovery it does the same thing as when i tried to normal boot (well now the recovery option isn't even there anymore)
But what it did was go to the white HTC Incredible screen and then just start rebooting over and over....
similar problem
i flashed the new cyanogen 7.1.0 stable earlier today and did a complete wipe. 3g wouldn't work no matter what i tried. suddenly, the phone is now in a boot loop (just rebooted on it's own). I get one vibrate, the white "HTC Incredible" screen and it reboots, rinse, repeat. I do have access to hboot (0.92).
I have attempted to flash what appears to be every available option for recoveries including clockwork, RA, and stock. it says everything installs fine and i reboot. still unable to access recovery in any way, just starts the same boot loop.
attempted RUU both via PC and .zip extraction. PC method says i'm not connected via usb despite proper drivers and phone recognition by window 7 and .zip acts as if everything applies appropriately then produces the same boot loop.
I have tried everything I can find over the last 6 hours of searching various forums. Anyone have an idea on a potential fix or a way to get s-on without being able to access recovery?
I'm about to exercise my insurance plan and put this phone under my tires and slowly back up...all replies are greatly appreciated

Categories

Resources