Related
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.
Hey guys,
I tried to root my my evo 4g with the instructions from the sticky and when I started the autoroot file as it said, it would get to found root then establishing something and the cmd would close out and my phone would stay in the bootloader mode. Instructions said to go to recovery if it didn't continue and I did go into recovery and all it gave me was a black screen with the red triangle and nothing was happening so I pulled out the battery to restart the phone. Now my phone boots up normally and it just freezes up after maybe 30 seconds of use everytime and just reboots and it repeats over and over again nonstop. It won't be recognized by my computers and it just says unidentified with the CDMA drivers not working and the phone does not recognize the SD card when its running and booted up. Please help if you guys know what I could do to make it stop restarting. Thanks in advance!
Try re-rooting via unrevoked. Click on unrevoked in my signature and follow the directions, but first, boot into the bootloader screen (after shutting off the device, simultaneously press the DOWN volume button and the power button until the device starts). Look at the top of the screen and see if it displays "S-OFF". If it does, great, you're rooted, bit if it displays "S-ON" then follow the rooting method of unrevoked or retry the method you used. If it does indeed display "S-OFF", I suggest you flash a custom recovery like amon_RA.
posting & replying via the XDA Premium app.
Well I can't do that since it won't recognize the phone through USB or recognize the SD card
Update: I just flashed my evo with the stock 3.70.651.1 rom using a card reader putting the PC36IM something file on the SD card and used bootloader to flash and It's still not recognizing the SD card and it's still freezing up 1 minute after it has booted up and restarts and repeats the loop.
I sorta have a similar problem. I have a rooted evo running CM7 .
trying to use HDMI cable with a 1080p vizio LCD TV. Nothing happens. Does CM7 support the HDMI video out.
Sent from my PC36100 using XDA Premium App
SprintTouchPro2 said:
Hey guys,
I tried to root my my evo 4g with the instructions from the sticky and when I started the autoroot file as it said, it would get to found root then establishing something and the cmd would close out and my phone would stay in the bootloader mode. Instructions said to go to recovery if it didn't continue and I did go into recovery and all it gave me was a black screen with the red triangle and nothing was happening so I pulled out the battery to restart the phone. Now my phone boots up normally and it just freezes up after maybe 30 seconds of use everytime and just reboots and it repeats over and over again nonstop. It won't be recognized by my computers and it just says unidentified with the CDMA drivers not working and the phone does not recognize the SD card when its running and booted up. Please help if you guys know what I could do to make it stop restarting. Thanks in advance!
Click to expand...
Click to collapse
can you send me the autorootlog.txt file? that should show what happened to it. And def don't try rooting it with anything else while the phone is in an inconsistent state, that is just asking to corrupt it.
Use unrevoked 3 my guide has all you need links and so on
I like unrevoked 3 easy to root and unroot . All the other programs that work for rooting can make unrooting a pain in the butt. Do what you want you want .
You don't have a recovery installed that's why you get black screen and triangles . Use amon 2.3
reaper24 said:
Use unrevoked 3 my guide has all you need links and so on
I like unrevoked 3 easy to root and unroot . All the other programs that work for rooting can make unrooting a pain in the butt. Do what you want you want .
Click to expand...
Click to collapse
how is unrooting different?
xHausx said:
how is unrooting different?
Click to expand...
Click to collapse
I'm not going to war with you on that man just saying turn s off flash a stock Ruu the latest and your good to go. Trying to find a auto or one click unrooting program to unroot can be a pain to do if your h boot is to new or old .
I'm sure your way is good I just prefer unrevoked 3 is all. Not dogging your root way. Just familiar with unrevoked 3 use it to root everyone's phone I know.
reaper24 said:
I'm not going to war with you on that man just saying turn s off flash a stock Ruu the latest and your good to go. Trying to find a auto or one click unrooting program to unroot can be a pain to do if your h boot is to new or old .
I'm sure your way is good I just prefer unrevoked 3 is all. Not dogging your root way. Just familiar with unrevoked 3 use it to root everyone's phone I know.
Click to expand...
Click to collapse
Well you're saying there's a difference in how you have to unroot when it's not true. Or at least that I know of, if there is I'm curious as to how.
Autoroot will try to downgrade the hboot to the unlocked engineering leak, if successful it's finished and all you have to do to unroot is run the RUU. If it's unable to downgrade the hboot it will bring up the stock recovery and use unrevoked forever to unlock the nand; when this is used you have to flash the s-on tool (that is left on the sdcard as URFSOn.zip) and then flash the RUU to unroot.
Unrevoked 3 breaks in through the hboot and unlocks the nand through the radio, so you will also have to use the s-on tool and flash the RUU.
You're also telling him to keep trying to root when his phone is obviously in a weird state, that's bad advice unless you want him to end up bricked like a ton of people did when the latest firmware came out.
xHausx said:
Well you're saying there's a difference in how you have to unroot when it's not true. Or at least that I know of, if there is I'm curious as to how.
Autoroot will try to downgrade the hboot to the unlocked engineering leak, if successful it's finished and all you have to do to unroot is run the RUU. If it's unable to downgrade the hboot it will bring up the stock recovery and use unrevoked forever to unlock the nand; when this is used you have to flash the s-on tool (that is left on the sdcard as URFSOn.zip) and then flash the RUU to unroot.
Unrevoked 3 breaks in through the hboot and unlocks the nand through the radio, so you will also have to use the s-on tool and flash the RUU.
You're also telling him to keep trying to root when his phone is obviously in a weird state, that's bad advice unless you want him to end up bricked like a ton of people did when the latest firmware came out.
Click to expand...
Click to collapse
no I'm not telling him to brick his phone. He doesn't have a recovery on his phone that is what he needs . Just saying if he does end up rerooting at some point he can try unrevoked 3 just a suggestion. My advice isn't bad not new to rooting or flashing. Pretty good at trouble shooting .
Well how do I get a recovery? I thought I have one since I have the option to go there? Gives me a red triangle with a phone under it. Once i mash the volume up and down and power button at the same time and hold it in for a bit a menu pops up to update from SD card or to clear storage and some other options. But anyway I reflashed the stock rom from bootloader and it's still doing the freeze after 30 seconds of use and restarts over and over again. So how do I actually get recovery and what do I do after that to make this stupid restarting of my phone to stop.
SprintTouchPro2 said:
Well how do I get a recovery? I thought I have one since I have the option to go there? Gives me a red triangle with a phone under it. Once i mash the volume up and down and power button at the same time and hold it in for a bit a menu pops up to update from SD card or to clear storage and some other options. But anyway I reflashed the stock rom from bootloader and it's still doing the freeze after 30 seconds of use and restarts over and over again. So how do I actually get recovery and what do I do after that to make this stupid restarting of my phone to stop.
Click to expand...
Click to collapse
I'll need to take a look at your autorootlog.txt file in order to find out what's up with your phone. It should be in the autoroot folder and you can post it by using the 'manage attachments' button, if it doesn't want to let you for some reason you can also email it to me.
edit: odds are you're phone is still locked but it won't hurt to try flashing the recovery, all you have to do to flash it is run the FlashZip script that came with AutoRoot and select the one that says Amon RA - hausmod. That's if it's unlocked of course, if it says s-on or that the security is still on then your phone will reject it.
There you go, there is my autorootlog
I'm not too worried about this as I took the phone to sprint and they ordered me a new phone since they didn't know what was wrong with it and I'll get it today or tomorrow but I just want to figure out what went wrong so that I know what to do if I am to root my new phone..cause this autoroot I used on this website messed up and I followed every step perfectly.
alright here is what happened. i was in twrp2 rc0.2 and was flashing a theme .zip made from the zipthemer app. i wiped cache and dalvik and flashed like normal and then after the flash it gave me an option to reboot system. i clicked it and it should have booted into my rom. instead it showed what would have been the white htc evo splash screen (mine is different) and then went to a black screen, vibrated 5 times, and i have the green notification light flashing.
i pulled the battery. booted into the bootloader and tried to go to recovery. ended up doing the same black screen vibrate etc. so i went back to bootloader to try to reflash the recovery since i still had the pc36img.zip on my sd. it scanned for the file looked like it read it but instead skipped past it and never gave me an option to flash the recovery. i tried multiple times, a series of battery pulls and no luck.
anyone got a clue as to whats up? im thinking i have a bad block and i heard of some jtag program or something to fix it but i have no idea what it is or how to use it.
p.s. yes i did google and i didn't find anything of much use... hell of a Christmas huh?
EDIT: odd. i have been rooted since january and now after this started it says im s-on. think i could use an ruu? the sd wont mount and im pretty sure they run from your sd so is there a way of using and ruu from a computer?
PhxkinMassacre said:
alright here is what happened. i was in twrp2 rc0.2 and was flashing a theme .zip made from the zipthemer app. i wiped cache and dalvik and flashed like normal and then after the flash it gave me an option to reboot system. i clicked it and it should have booted into my rom. instead it showed what would have been the white htc evo splash screen (mine is different) and then went to a black screen, vibrated 5 times, and i have the green notification light flashing.
i pulled the battery. booted into the bootloader and tried to go to recovery. ended up doing the same black screen vibrate etc. so i went back to bootloader to try to reflash the recovery since i still had the pc36img.zip on my sd. it scanned for the file looked like it read it but instead skipped past it and never gave me an option to flash the recovery. i tried multiple times, a series of battery pulls and no luck.
anyone got a clue as to whats up? im thinking i have a bad block and i heard of some jtag program or something to fix it but i have no idea what it is or how to use it.
p.s. yes i did google and i didn't find anything of much use... hell of a Christmas huh?
EDIT: odd. i have been rooted since january and now after this started it says im s-on. think i could use an ruu? the sd wont mount and im pretty sure they run from your sd so is there a way of using and ruu from a computer?
Click to expand...
Click to collapse
You can run a ruu through fastboot
Sent from my PC36100 using XDA App
evo4gnoob said:
You can run a ruu through fastboot
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
im downloading a 2.2 ruu. ill get back to you as to if it works or not
ok. i try to run the ruu and it gives me a main-version ERROR so i hit close and disconnect my phone. but then a window pops up saying update. so i plug in my phone again go to fastboot but then fastboot freezes and i cant navigate up and down with the volume keys. i then hit update but it just hangs at rebooting to bootloader and wont do anything...
If you can get back to Hboot, try to find a pc36img for the ruu you need and use the Ruu for the phone you have, not just any Ruu.
Use this site: http://goo-inside.me/supersonic/ruu to find your RUU
HipKat said:
If you can get back to Hboot, try to find a pc36img for the ruu you need and use the Ruu for the phone you have, not just any Ruu.
Use this site: http://goo-inside.me/supersonic/ruu to find your RUU
Click to expand...
Click to collapse
i tried the sdcard ruu for the latest gb update. it goes through. installs everything ok. but then when it reboots it goes back to the same 5 vibrates and black screen with flashing light.
after i did the sdcard ruu the windows ruu was able to go through unlike before. so i plugged in my phone it did its thing successfully. and again to no avail its still got the 5 vibrate etc.
and other options such as a block remap? i was running decks at the time which is based off cyanogen and i heard that cyanogen had been screwing blocks lately...
edit: i have no idea how a block remap would work... i just saw it in a thread that i believe you posted in like 3 days ago or so...
The 5 vibrates means it's in maintenance mode. (Diagnostics?)
I'm not sure what that means, exactly, but I don't think you're bricked, however, you DID say you were S-on, I believe, so if you are, try to re-root (look up root method for your hboot version) and them flash a recovery (Prefer Amon Ra) if it is successful.
If that works, wipe everything you can, except SD Card, wipe Dalvik Cache and Cache twice, then flash a ROM.
HipKat said:
The 5 vibrates means it's in maintenance mode. (Diagnostics?)
I'm not sure what that means, exactly, but I don't think you're bricked, however, you DID say you were S-on, I believe, so if you are, try to re-root (look up root method for your hboot version) and them flash a recovery (Prefer Amon Ra) if it is successful.
If that works, wipe everything you can, except SD Card, wipe Dalvik Cache and Cache twice, then flash a ROM.
Click to expand...
Click to collapse
He can't get sd to mount
Sent from my PC36100 using XDA App
ok. i went to a friends house and just let my evo chill out on my desk and when i got back it booted right up since i got 1 successful ruu in. now that being said it only stays up for about 3 minutes and then shuts off and goes into the vibrate and blink stage so im gonna try a logcat and see if i can get anything useful out of it. there is some hope here boys
ok. i have tried ruu 2 more times. i tried to root a few times. all to no avail. nothing works. i still turns on for only 3 minutes at a time and then goes blank and vibrates.
my device is less than year old but i didn't get a warranty so does anyone know what the deal is with getting a replacement? my bootloader says s-on and its on a stock rom due to the 934759345734 ruu's i did so they won't know i was rooted. so is there like a 1 year manufacturer warranty for this without having to break out $100?
Best bet is to just call Sprint and find out. They may just offer you a trade in.
So i was running a miui rom and did a clean wipe to try and a new rom. I couldn't get past the boot screen of the rom so i figured it was just a bad download. so i went and unrooted the phone. i have Hboot .92 thew radio is 2.15.10.07.07. i have the phone to s-on. i downloaded and installed the stock verizon gingerbread rom by renaming it to th P whatever lol. the reboots gets to the incredible screen then goes the htc quetly brilliant screen then it does the droid sound and i get the red snapdragon logos. but when it get's to the droid eye after it circle goes back and forth once then freezes on the second one. it sits there for like 3 or 4 minutes and then it just reboots to the droid sound and snapdrogon screen then the droid eye and stops and just keeps repeating this. i am hoping someone on might have a cure for this. the only thing i can get into iss hboot. hoping it's not fried. thanks for your time. and sorry for the long post, just trying to be very detailed to get the right help.
scoobntaz1996 said:
So i was running a miui rom and did a clean wipe to try and a new rom. I couldn't get past the boot screen of the rom so i figured it was just a bad download. so i went and unrooted the phone. i have Hboot .92 thew radio is 2.15.10.07.07. i have the phone to s-on. i downloaded and installed the stock verizon gingerbread rom by renaming it to th P whatever lol. the reboots gets to the incredible screen then goes the htc quetly brilliant screen then it does the droid sound and i get the red snapdragon logos. but when it get's to the droid eye after it circle goes back and forth once then freezes on the second one. it sits there for like 3 or 4 minutes and then it just reboots to the droid sound and snapdrogon screen then the droid eye and stops and just keeps repeating this. i am hoping someone on might have a cure for this. the only thing i can get into iss hboot. hoping it's not fried. thanks for your time. and sorry for the long post, just trying to be very detailed to get the right help.
Click to expand...
Click to collapse
Have you tried doing a factory reset from hboot, and then reflashing the ruu (PB31IMG.zip file) thru hboot again. Also why did you go s-on, just makes it way harder to reroot or fix issues like these? The only reason anyone should ever go s-on is if you need to return it to verizon under warranty.
the reason for s-on is because i was selling it and the new owner just wanted it stock. they know nothing about rooting or any of this kinda stuff. i do believe i tried the factory reset but i will give it a go again.
so i believe i have found the problem. and doing some research it's my own fault. i am still on the .07.07 radio baseband and i found out that i should have downgraded before getting s-on. now i don't know if i can fix this problem or did i just ruin my phone. hoping for some good news. thanks
scoobntaz1996 said:
so i believe i have found the problem. and doing some research it's my own fault. i am still on the .07.07 radio baseband and i found out that i should have downgraded before getting s-on. now i don't know if i can fix this problem or did i just ruin my phone. hoping for some good news. thanks
Click to expand...
Click to collapse
Im pretty sure you have to downgrade the radio to get s-on. As in it wont work to get you s-on if your not on the right radio. Are you sure you didnt downgrade and doing the ruu just upgraded it again?
I would try doing the latest ruu.exe with a pc, instead of PB31IMG.zip.
i would love to but the pc will not read the phone because it just boot loops.
scoobntaz1996 said:
i would love to but the pc will not read the phone because it just boot loops.
Click to expand...
Click to collapse
Try flashing the PB31IMG.zip ruu with fastboot. androidforums.com/incredible-all-things-root/487280-easier-way-flash-pb31img-files.html
do you happen to have a workable link for the adb and fastboot. the link on android forums is through megauploiad and is not a workable link.
scoobntaz1996 said:
do you happen to have a workable link for the adb and fastboot. the link on android forums is through megauploiad and is not a workable link.
Click to expand...
Click to collapse
Here ya go: http://dinc.does-it.net/ADB/ADB-Fastboot-USB-Drivers_v4_(x86)(x64).zip
phone is not recognized in hboot or fast boot. it says hboot usb and fastboot usb on my phone but when i go in the coomand prompt on my pc it doesn't show any devices.
scoobntaz1996 said:
phone is not recognized in hboot or fast boot. it says hboot usb and fastboot usb on my phone but when i go in the coomand prompt on my pc it doesn't show any devices.
Click to expand...
Click to collapse
Have you installed the phone drivers on your pc?
i have installed everything that i can to try and get this phone working. hboot comes comes up on the phone just fine and i can get to fastboot on the phone. when i go to recovery from fastboot it goes to the green triangle then it turns red. i do the volume and power to get to recovery but when it comes up i get a bunch of error messages. and am at a lost with this. all i know is i don't think it is bricked because i can get to hboot. when i try to install another pB file from hboot it either does not do anything or it tells me it failed because it was an older version. i am pretty sure it is a software problem i just can't figure it out.
My Incredible is in a bootloop. I have gone back to stock. The phone will work for a few minutes then just reboot non-stop. I did a factory reset and that did not help.
I can't keep the phone on long enough to do anything. The irony in all of this is that it started to do this 2 weeks after I became eligable for an upgrade...
Smells fishy...now I either wait for Incredible 4G or get the Rezound.
[email protected] Verizon...
Do you have a recovery on the phone still or did you get rid of it when returning to stock? I'm not sure I've heard of this before but if you post the status of your hboot that might be able to help someone help you.
and personally between the two I would go with the Incredible 4G but that's just me being loyal to HTC i guess.
Recovery is gone/does not work. I'll post the HBOOT version later, don't have the phone atm.
binaryhat said:
Recovery is gone/does not work. I'll post the HBOOT version later, don't have the phone atm.
Click to expand...
Click to collapse
Post hboot version, s-on or off, and current android version.
cmlusco said:
Post hboot version, s-on or off, and current android version.
Click to expand...
Click to collapse
Will do tomorrow...left the phone at work.
S-off
HBOOT-0.92
Radio-2.15.00.07.28
Stock Android
I know it sounds very round-about but you may need to flash CWM back on to the phone so you can flash unrevoked's s-on tool, I don't know for sure that this is what is causing the problem but you want s-on when you are in stock, especially if you plan on giving the phone to Verizon- if it has been messed with they won't want to handle it because they will say it is not their problem. (I have heard that Verizon has admitted to not checking very carefully, but it can't hurt to be careful yourself)
How can I flash CWM if I can't keep the phone on for more than a minute?
sounds like your kinda having the same problem i am having. the difference is my is s-on. i can get to hboot but when i try to go to recovery from there it comes up with a bunch of errors. and mine just bootloops at the droid eye.
that is a very valid point. It still can't hurt to try, I remember when I rooted my phone, it didn't take all that long to flash CWM.
You also might want to consider booting into safe mode to see if that keeps in on longer, I am copying and pasting these instructions from technipages.com because xda won't let me post links until they trust me more or something:
Sometimes services and apps you install on your HTC Droid Incredible can interfere with its functionality. If you’ve reached a point where the phone freezes at startup or malfunctions in a way that you can’t remove the problem, Safe Mode is the answer. Booting in Safe Mode will load only software and drivers from factory defaults. This should allow you access to remove whatever ails your smartphone.
1. Turn the device off. If the power button doesn’t do the trick, remove and replace the battery.
2. Power the device on.
3. When the logo appears, press and hold the Menu button.
4. Continue holding the Menu button until you see the home screen.
The words Safe Mode should appear in the lower left corner if you performed the steps correctly.
Click to expand...
Click to collapse
I apologize if you don't have any luck, but I am only trying to help
I'll try safe mode (should have) and see if that works.
binaryhat said:
I'll try safe mode (should have) and see if that works.
Click to expand...
Click to collapse
Does the phone shut off when your in hboot too? You need to do as sugested and flash cwm thru hboot, and then see if you can access recovery long enough to wipe everything in mounts and storrage except sd and emmc, then flash superuser, and a rom.
scoobntaz1996 said:
sounds like your kinda having the same problem i am having. the difference is my is s-on. i can get to hboot but when i try to go to recovery from there it comes up with a bunch of errors. and mine just bootloops at the droid eye.
Click to expand...
Click to collapse
Whats your hboot and android version? Have you tried an ruu?
EDIT: Nevermind i forgot i was allready talking to you in the other thread.