Tried to downgrade to stock. Help - Droid Incredible Q&A, Help & Troubleshooting

I rooted and installed the leaked OTA. After hearing about the possible 2.2 I tried to downgrade the radio. Something messed up along the way and now I'm stuck with an incredible that is showing no internal memory (won't even let me save a picture), will not read an SD card and keeps rebooting when I remove the usb cable. I'm stuck in a real hard place. If anyone can assist me in restoring my phone and how to go about it, it would be appreciated. Also it is now showing my phone as an unknown device when I connect to the pc and I can not get into adb.

Can you reboot into recovery? (power off, then hold volume down while powering back on) then select recovery?
If you can get into clockworkmod recovery, we can get you back up and running.

do a hard reset. if that doesnt work, take it back to vzw and make up a story on how it got the way it is.
TIP: i dont think you can downgrade the radio.
Sent from my Incredible using XDA App

I started following this tutorial http://www.youtube.com/watch?v=eeuiURZZZds and after trying to run 'flash_image misc mtd0.img', it said I did not have enough memory so I just unplugged the phone and tried to reboot, but it brought me to the recovery console and it's the stock one. So the stock img was able to install. I don't even have clockwork now. I should have left it alone. I have a constant sd card icon with a ?.

just hard reset or ruu . if this doesnt work, then i think you bricked your radoio. do you have 3g?
Sent from my Incredible using XDA App

Jd is right. Just ruu back to the leaked ota. If you can get to stock recovery you should be able to ruu. Once your back up and running we might be able to help you downgrade. First things first.

Just tried the hard reset it was a no go. I have 3G service and I made some calls to make sure it worked. After the hard reset it is still showing the sd card icon with ?. For the RUU do I need any drivers because the phone is showing up now as an unknown device.

Just give it a shot.

ruu is the way to go. your problem is more sever than hard reset fixijg.
Sent from my Incredible using XDA App

P.s. If you follow the downgrade tutorial by "IncredibleDoes" you can use an sdcard adapter and put the card into your pc (since your phone usb drivers aren't working), copy the "pb31img" file over, then reboot back into hboot, and it will put you right back to the original stock in one step.

If you have a card reader on your pc, turn the phone off, put the card in the pc and make sure it's formatted properly. Then put the ruu file on the card. (Follow the instructions in the unroot sticky topic.) Then put card back in phone and boot into stock recovery. It should apply the update.
Sent from Incredible using Tapatalk.

[email protected]

hows the ruu going?
Sent from my Incredible using XDA App

I'm still trying. It's not looking good. Hboot is still version .79 after I flashed the stock img. I'm probably going to have to call it a night for now though. I'll be back tomorrow to trouble shoot it some more. I'll write more after I try it again. Thanks for the help tonight!

of you need additional help feel free to pm me anytime.
Sent from my Incredible using XDA App

Hboot is NOT going to downgrade....no matter what you do. The stock (pre-ota) rom will run fine with the newer hboot version.

samwathegreat said:
Hboot is NOT going to downgrade....no matter what you do. The stock (pre-ota) rom will run fine with the newer hboot version.
Click to expand...
Click to collapse
Yes it will downgrade, as the ota leak is a newer version of .79. that is, if you follow the procedure right.
Also, yes you can downgrade the radio, in response to an earlier post.
If you got out of memory type messages running through that method, then you did it wrong. Maybe you tried it outside of clockwork? I haven't watched the video to do it, but seeing how I made the original post for it, I know it works.

Interesting! I wasn't aware of that breakthrough (hboot downgrade).
In that case, I suggest ruu'ing back to the leaked OTA (so that your USB and SD are both working again), then try following the instructions that adrynalyne referenced.
Good Luck.

http://forum.xda-developers.com/showthread.php?t=727263

I ruu'ed the img. The phone starts up and works normally. Except it still shows the internal and SD card memory as unavailable and the usb restarting after removing the cable. I tried to reload the leaked OTA through recovery, but it gets an error saying the file is not on the SD card.

Related

[Q] Is my phone bricked

Hope anyone can help me. Has soon tried everything without success. Phone is rooted with bootloader 0.80 Radio. 5.09.00.20 March 29 2010 and defrost system version 4.3
Have bootloader 0.80 which says wrong version when booted, and Touch panel fail sometimes. The phone can boot up sometimes, but after 2 to 3 my phone goes black and can only be started up again by taking out the battery. Is there any possibility to get the phone back to the original as it can be sent for repair. Believe, in fact it could be something hardware does not. If it can not be done, can it be made without it costing more than a new phone
Have u tried another rom?
If u want to send it to repair u need this RUU to unroot
http://shipped-roms.com/shipped/Bra...3.00.32U_5.09.00.20_release_140022_signed.exe
I use it to unroot mine, but u need to be sure your screen is amoled, this is for AMOLED screen ONLY
Sent from my HTC Desire using XDA App
Thanks for the quick reply. Have tried with another ROM without success. Have tried with a RUU. Unfortunately, the phone will not be in usb mode when i try to sync HTC. Windows writes that there is connection to usb port. Can you get RUU in zip format so it can be loaded via Update.zip / recovery mode. The RUU you recommend that can be used for Danish phones. Whew, lots of questions.
Yes u can install the RUU threw Sdcard, try and find a SAPPIMG containing froyo2.2 or u can try and downgrade to 2.1 and see if the phone works properly, i only have links to the 2.1 here u are:
http://shipped-roms.com/shipped/Bra...8U_4.06.00.02_2_release_126984_signed_txt.zip
1. download the file to SD card.
2. rename to PB99IMG.zip
3. boot into recovery (turn phone on while holding down volume)
4. just let it load the zip file and press yes when asked to install
This will get u back to 2.1 so then u can try OTA updates or running RUU´s again.
manchesterob said:
Thanks for the quick reply. Have tried with another ROM without success. Have tried with a RUU. Unfortunately, the phone will not be in usb mode when i try to sync HTC. Windows writes that there is connection to usb port. Can you get RUU in zip format so it can be loaded via Update.zip / recovery mode. The RUU you recommend that can be used for Danish phones. Whew, lots of questions.
Click to expand...
Click to collapse
Probably u have USB Bricked, look for threads explaning how to fix USB Brick..
Many thanks for your help. Try it during the night. The problems with the phone locks and the screen goes black and can only be restarted by taking the battery out, because it surely wrong bootloader or brincked usb
Have tried to install PB99IMG.zip. Unfortunately, when it only to load up a bit of the column before the phone goes black again, and battery removal to restart. Anyone have an explanation for this. I completely drained of ideas
U seem to have a true brick.I broker my friends magic.
The new jtag riff box can now fix bricked desires
Sent from my HTC Desire using XDA App

[Q] I need help

Early this morning, I rooted my Droid Incredible using the Unrevoked 3 method. After doing so, I completely forgot to create a nandroid backup and went ahead to install a custom ROM (Cyanogen Mod). Now here's the issue. I want to get back to the Stock 2.2 sense. I tried to unroot my droid, but nothing seems to be working. Can someone please help?
You need to flash a stock rom back before unrooting.
Where can I get a stock ROM. I think I just bricked it now because it won't even boot Cyanogen Mod. It's stuck at the HTC Incredible white screen.
Do you know what type of screen you're using? Slcd or amoled ? Each method has a different way of unrooting. Just in a Google search engine type in who to unroot Droid incredible, and then the what screen it is. You can potentially brick your phone if you use the amoled method on a slcd one.
With the amolcd screen it's as simple as finding the right file, hence doing the search engine. When you get the file, all you have to do is just place it in the root of your phone, and turn off your phone and press and hold the power button and the volume button at the same time.
With slcd you have to do it different way. Assuming you haven't messed with the radio, if you did, you have to flash a 07.28 radio. But assuming you didn't touch that, you have to flash something that puts s-on. Ans then after that you have to put a file into the root of your SD card and then flash appropriately.
Now I did this multiple times, rooting and unrooting, and for some reason there's always so
Something drawing me back into rooting and flashing a new rom. There's no greater satisfaction than knowing you can do anything with your phone. But it's entirely your choice.
Oh yeah, to figure out what screen you have go to settings then about phone then hardware information and 002 is amoled and 003 is slcd. Google is your best friend after you figure out what screen you have. Good luck!
Sent from my Incredible using XDA App
You haven't officially bricked it until you can't power it on at all. Try taking out the battery and then holding the power button and volume down. If you can access the white boot screen where it gives you a choice of accessing recovery there is still plenty of hope. Don't freak out you haven't bricked your phone
Sent from my Incredible using XDA App
I can't load anything. The farthest I can go is to ClockWord Recovery, and when I try to reboot the phone, it's stuck on HTC Incredible. That being said, I can't check what screen type I have. However, before it was bricked, I did flash a file to make S- on. And, when I tried degrading my firmware, nothing happened. :/
OK first off the name of the first that you flash should start with a "p" I don't exactly remember the exact file name. Make sure you have s-on, I'm sure you do. And then put that p something file into the root of your SD card. root as in, it isn't in any folder.
Now when you flash this, you don't do it in clockwork recovery, you do it through hboot I believe. Hboot is the white screen when you hold on the power button and volume down. It should automatically read the p something file. And it'll ask you if you want to update. Say yes and then just let it install
Sent from my Incredible using XDA App
PB31IMG, I attempted to Flash it in HBOOT, but it didn't work. Now, I can't even connect my Droid to my computer.
I'm screwed.
Sorry for the double post, but I just followed some whacked-out tutorial that told me to format everything via Clockworkmod Recovery...now when I boot my phone, it goes straight to HBOOT and won't do anything...
OK what can you do exactly, you can get to hboot and what else. Also when did you buy your Droid incredible ? We might be able to figure out which screen you have based on that. Oh yeah and where did you buy it from? Also, even if you can't mount it you can still easily take out your SD card to flash files that way. Don't lose hope, we can still get back to stock
Sent from my Incredible using XDA App
lazysleepyboi said:
OK what can you do exactly, you can get to hboot and what else. Also when did you buy your Droid incredible ? We might be able to figure out which screen you have based on that. Oh yeah and where did you buy it from? Also, even if you can't mount it you can still easily take out your SD card to flash files that way. Don't lose hope, we can still get back to stock
Sent from my Incredible using XDA App
Click to expand...
Click to collapse
I bought it near the beginning of October, I believe it was the 9th? And, I bought it at Verizon.
Aside from being able to get to HBOOT, I can get to Clockworkmod Recovery...but that's about it.
Can't remember exactly how to tell but know you can tell by the model #under the battery on the phone.
Sent from my ADR6300 using Tapatalk
If you could get to clockwork u should be able to flash a rom if your sd wont mount use a card reader and plug directly into your comp
Meetii said:
I bought it near the beginning of October, I believe it was the 9th? And, I bought it at Verizon.
Aside from being able to get to HBOOT, I can get to Clockworkmod Recovery...but that's about it.
Click to expand...
Click to collapse
HTC Incredible 2.3.1
Meetii said:
I bought it near the beginning of October, I believe it was the 9th? And, I bought it at Verizon.
Aside from being able to get to HBOOT, I can get to Clockworkmod Recovery...but that's about it.
Click to expand...
Click to collapse
my brother bought his dinc before you and he got a SLCD screen, chances are that's what you have.
here's the page i used to unroot my brother's SLCD screen,
http://dougpiston.com/?p=7
follow it exactly, and just like jaysckap said, you can always take out your microsd card and put it into a usb reader
lazysleepyboi said:
my brother bought his dinc before you and he got a SLCD screen, chances are that's what you have.
here's the page i used to unroot my brother's SLCD screen,
http://dougpiston.com/?p=7
follow it exactly, and just like jaysckap said, you can always take out your microsd card and put it into a usb reader
Click to expand...
Click to collapse
That's the exact tutorial that I followed, but it didn't work.
Meetii said:
That's the exact tutorial that I followed, but it didn't work.
Click to expand...
Click to collapse
ok can you tell me how you flashed the included file? did you put it into the root of the SD card?
For now i would get a rom on your sd so your phone will boot up and do a nand backup so you at least have a working phone when i get home ill try and help you out
Meetii said:
That's the exact tutorial that I followed, but it didn't work.
Click to expand...
Click to collapse
HTC Incredible 2.3.1
Ok if you have a card reader for you SD card load it in and open you card on your PC. You need to make sure that the sd card is in FAT32 format otherwise when you try to load the PB31IMG file it wont read it. To check this go to my computer, find the removable drive for the SD card right click and go to properties, you should see what format its in. If it's FAT format copy everything from your sdcard to a folder on your PC, go back and right click on the removable drive and format the card to FAT32. Then of course copy everything back to your card. Then try the PB31IMG file again in hboot.
I would personally just go in recovery and wipe to factory, then choose the option to install zip from card and install the rom or which ever rom you want so the phone loads again. Good luck!
For now, I'm going to flash a new rom and hopefully I can fully boot my Droid again. Afterwards, I'll try to flash that file again. BUT, the first time I did it, I put it in the root of my SD card and booted HBOOT and nothing happened.
EDIT: This ROM is going to take close to 30 minute to download , so I guess I'll be back in 30 minutes; don't leave me please.
do you have a sd card reader? if you do, pop out your sd card and make sure it's format is FAT32, nothing will happen if it isnt FAT32

[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] Possibly bricked EVO, can get into bootloader S-OFF

I can get my Evo into the bootloader, but it won't allow me to reboot (it goes to the HTC Evo screen, then the screen goes dark and vibrates 5 times), I'll pull the battery and go back into the bootloader, I'll try to go into recovery and its does the same as rebooting. If someone can advise me what I can do to fix this, I would appreciate it. I messed up when I flashed an old Radio (2.15.00.07.21) Wont do that ever again :-(!
Specs: HBoot 2.10
Radio: 2.15.00.07.21
S-Off
3.29.651.5
I am a noob at this so please be nice, I also get the radio_v2 fail-pu when trying to update the phone, I'm not sure if i have the right PC36IMG file, thank you for your time!
raidernation said:
I can get my Evo into the bootloader, but it won't allow me to reboot (it goes to the HTC Evo screen, then the screen goes dark and vibrates 5 times), I'll pull the battery and go back into the bootloader, I'll try to go into recovery and its does the same as rebooting. If someone can advise me what I can do to fix this, I would appreciate it. I messed up when I flashed an old Radio (2.15.00.07.21) Wont do that ever again :-(!
Specs: HBoot 2.10
Radio: 2.15.00.07.21
S-Off
3.29.651.5
I am a noob at this so please be nice, I also get the radio_v2 fail-pu when trying to update the phone, I'm not sure if i have the right PC36IMG file, thank you for your time!
Click to expand...
Click to collapse
I don't even recognize that as any radio I've seen for the Evo. The last one ended in. 11.19 or something like that. The one before that ended with. 01.09 I believe. I don't recognize the one you used. Are you positive it was an Evo radio...? Your situation doesn't sound good though. I would try running an RUU from fastboot, but if you did flash a non evo radio, your probably in trouble...someone correct me if im wrong and that is indeed an evo radio.
Sent from my PC36100 using XDA App
Have you attempted running a 3.29 RUU?
http://www.shipped-roms.com/shipped/Supersonic/
Download the 3.29 version, boot your phone into the bootloader, select fastboot, connect to your pc. Once it shows fastboot usb on the phone, run the ruu exe.
k2buckley said:
I don't even recognize that as any radio I've seen for the Evo. The last one ended in. 11.19 or something like that. The one before that ended with. 01.09 I believe. I don't recognize the one you used. Are you positive it was an Evo radio...? Your situation doesn't sound good though. I would try running an RUU from fastboot, but if you did flash a non evo radio, your probably in trouble...someone correct me if im wrong and that is indeed an evo radio.
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
It is, I just checked; its rolled back 3 versions from the 11.19 version.
Can't he place a PGimg.zip on root of his SD card and fastboot from his phone to return him to stock s -off ?
sent from a sweet paper weight.
ibsk8 said:
Can't he place a PGimg.zip on root of his SD card and fastboot from his phone to return him to stock s -off ?
sent from a sweet paper weight.
Click to expand...
Click to collapse
He can place a PC36IMG form of the RUU and do it that way, but if he wanted s-on, he'd need to flash the unrevoked s-on tool from recovery, which he can't get to.
raidernation said:
I can get my Evo into the bootloader, but it won't allow me to reboot (it goes to the HTC Evo screen, then the screen goes dark and vibrates 5 times), I'll pull the battery and go back into the bootloader, I'll try to go into recovery and its does the same as rebooting. If someone can advise me what I can do to fix this, I would appreciate it. I messed up when I flashed an old Radio (2.15.00.07.21) Wont do that ever again :-(!
Specs: HBoot 2.10
Radio: 2.15.00.07.21
S-Off
3.29.651.5
I am a noob at this so please be nice, I also get the radio_v2 fail-pu when trying to update the phone, I'm not sure if i have the right PC36IMG file, thank you for your time!
Click to expand...
Click to collapse
Try to basicaly reroot id try to hook to pc and run the hboot driver to fix the driver hopefully that will get you back into recovery. And id stick with flashin roms not radios its to risky. Did you back up your wimax keys?
Borked
Ok hi. So here's the deal:
My EVO can boot into bootloader, and it can get into recovery. Cool right? NO!!!
here's where the problem starts: I installed a corrupted ROMand of course, like every ROM, I wiped everything before flashing that one, and ended up not having a system to fall back on... And now the only thing I can do is get into the Bootloader and recovery.
The following issues I'm having, and the thins I have tried are:
1. I have tried putting the PC36IMG.ZIP at the root of the sd card.
- That didnt work though, and I figured that would only make sense, due to the fact that in recovery, it says "E: cant mount sd card"... So why/how would it work in bootloader?
2. It says "wrong image" when it tries to update the IMG file
3. I'm not a complete noob, I am willing to try ADB, I just dont know the commands to use :-( and IDK what to "push" or, even how to get the computer (PC, NOT a mac) to recognize the phone since it's... well, borked, I guess.
4. I' guessing that's the ONLY way to truly fix the phone and flash another ROM... is from the PC? But if so, HOW? Please help me.
Enmund said:
Ok hi. So here's the deal:
My EVO can boot into bootloader, and it can get into recovery. Cool right? NO!!!
here's where the problem starts: I installed a corrupted ROMand of course, like every ROM, I wiped everything before flashing that one, and ended up not having a system to fall back on... And now the only thing I can do is get into the Bootloader and recovery.
The following issues I'm having, and the thins I have tried are:
1. I have tried putting the PC36IMG.ZIP at the root of the sd card.
- That didnt work though, and I figured that would only make sense, due to the fact that in recovery, it says "E: cant mount sd card"... So why/how would it work in bootloader?
2. It says "wrong image" when it tries to update the IMG file
3. I'm not a complete noob, I am willing to try ADB, I just dont know the commands to use :-( and IDK what to "push" or, even how to get the computer (PC, NOT a mac) to recognize the phone since it's... well, borked, I guess.
4. I' guessing that's the ONLY way to truly fix the phone and flash another ROM... is from the PC? But if so, HOW? Please help me.
Click to expand...
Click to collapse
Make sure your sdcard is formatted FAT32.
Sent from my Galaxy Nexus using Tapatalk 2
fastboot oem enableqxdm 0
fastboot reboot
Use these commands through adb
Sent from my PC36100 using xda premium
That will remount your SD card
Sent from my PC36100 using xda premium
stevenskanse said:
fastboot oem enableqxdm 0
fastboot reboot
Use these commands through adb
Sent from my PC36100 using xda premium
Click to expand...
Click to collapse
Hey that sounds like it would work, but my question is...How do I get the phone detected on the pc, if the phone cant read the sd card? You get what I'm saying? Like, what buttons do I press to enable the USB to be picked up on the computer? Thnks a lot man.
That happened to me. You have to hold BOTH the Vol+ and Vol- Buttons at the same time until it starts vibrating. You also have to connect it to the computer in order to make it vibrate.
EDIT: You have to take out the battery while plugged in. Sorry for forgetting
When u put the PC36IMG.zip (named exactly like that) on your SD card, are u sure it wasn't named PC36IMG.zip.zip or any other variant of the correct name? Use a card adapter to put file in main folder of SD then put it back in phone. Then boot to bootloader n test. What recovery did u have installed when you tried to flash a radio? Clockwork will not flash radios
{ParanoiA} said:
When u put the PC36IMG.zip (named exactly like that) on your SD card, are u sure it wasn't named PC36IMG.zip.zip or any other variant of the correct name? Use a card adapter to put file in main folder of SD then put it back in phone. Then boot to bootloader n test. What recovery did u have installed when you tried to flash a radio? Clockwork will not flash radios
Click to expand...
Click to collapse
Yes I did... It says wrong image

HELP! Constant Network Error! Tons of info inside, please help :(

I know. It looks like a lengthy read. But all the information you could possibly need I've provided. Please let me know what you think. Also, I've done some searchign around but none of the scenarios I found were a result to flash back to stock sprint RUU.
The error reads as follows: "Attention. A network error has occurred. Retry, or cancel and return to the previous screen."
What actually happens: Anytime I open Marketplace, Facebook app, send a message through KakaoTalk or GroupMe, pretty much anything that uses the 3G, 4G data, it doesn't work. The message only comes up when I try to use the marketplace app. All other apps just say there was a connection error, connecting to the server, etc.
When I hit "Retry" it goes right back to the same dialog pop up, as if it doesnt even re"try". The top notification bar goes from 3G and then disappears, then goes from 3G and just continually disappears. It doesnt matter if I have 4G on or WiFi, it will just goes back to 3G when attempting to gain data, and then disappears and the error happens.
My Timeline of events: I first had been running Synergy and everything was fine. Suddenly my wall charger (or any wall charger for that matter) stopped working when plugged in. The car charger still works, but no HTC wall chargers, odd. So I decided to use that insurance for good and bring it into sprint. Gotta unroot and all that jazz first though. I downloaded the "RUU_Supersonic_1.32.651.1_Radio_1.39.00.04.26_release_171253.exe" and found a way to connect my phone to the PC, and finished the wizard. Mind you, before I did this, I went into recovery (while on synergy) and did a dalvik cache wipe, data/factory wipe and cache wipe, then went back into hboot and ran the wizard from there. Everything went fine, the ROM install was successful, I no longer have recovery and it was the stock sprint ROM.
Where things got fishy...: After it was running through all the constant reboots and things, I let the phone sit while I did other things. I came back to it, signed into my gmail and facebook fine, then went to marketplace. I started downloading all my purchased apps and since that was going to take some time, I let it sit again and went off.
Fishy part: I come back to he phone, and would normally just pull down notification taskbar, and hit clear all notifications, since it said a bunch of things had sucessfully installed, but I notcied it also said "System update complete." Hmmm, I didn't start any system update...did it do it automatically? It had to of. I went to check for an OTA (HTC software update) and it found "System upgrade 1.47.651.1 (30.15 MB) - FOTA update." I canceled it since I pretty sure doing an OTA update on a rooted ROM is a no-no.
So what the heck is the problem here, I never had these issues before until I went back to the stock sprint ROM. I've already updated PRL a few times, does nothing.
Should I go back and reflash it and this time make sure it doesnt do a system upgrade until I've turned S-OFF back to S-ON? Once the phone is S-ON is it safe to update OTA?
My About Phone details are a sfollows:
Firmware version: 2.1-update1
Baseband version: 1.39.00.05.31
Kernal version: 2.6.29-a2443432
Build number: 1.32.651.6 CL171253 release-keys
Software number: 1.32.651.6
Browser version: WebKit 3.1
PRI version: 1.90_003
PRL version: 60683
Any help, advice, suggestions are welcome!!!!! Please hook me up fellas, I'm a little bogged down about the upset.
UPDATE:
Okay. Since I am an impatient person and the last resort was going to re-flash the RUU, I'm just going to do that. And then make sure there is no system update. Once that is done, I'll run the S-ON tool from somewhere, hopefully I won't need recovery for anything, aaand then we'll see where we are. If you're reading all this PLEASE reply with something, anything to let me know somewhere out there is alive! lol, please.
With phone s on and stock ruu loaded it should be fine to accept update...wow u might get froyo lol. And it might help with your data issue...idk much but I know a little.
Edit: maybe try a newer ruu that might help with the data as well. not sure how HTC updates but i think it goes one at a time instead of newest available
Sent from my PG86100 using xda premium
Well the phone is still S-OFF right now, but now that I'm on the stock sprint RUU I dont have a custom recovery anymore, so how am i supposed to flash the unrevoked-forever-son.zip and the PCIMG36 thing!!??! How do I get back a recovery, do I just reflash something like synergy...!?
Here is amon ra recovery. Put on root of SD card and flash in bootloader. http://db.tt/TOsdM52P
This should get u recovery back so u can flash the s on tool. Then run a newer ruu, there is a thread in the EVO dev section with the latest, and hopefully it will also fix your data problems
Sent from my PG86100 using xda premium
gunfromsako said:
Here is amon ra recovery. Put on root of SD card and flash in bootloader. http://db.tt/TOsdM52P
This should get u recovery back so u can flash the s on tool. Then run a newer ruu, there is a thread in the EVO dev section with the latest, and hopefully it will also fix your data problems
Sent from my PG86100 using xda premium
Click to expand...
Click to collapse
Okay, I downloaded the file, put it on SD card, unplugged it, opened hboot and it tried loading the PC36IMG file, it said wrong image or soemthing like that about 6 times and then went back to the regular screen. Although, it has ALWAYS said wrong image for me, so I'm not worried about that.
So now I just went down and hit recovery and its a no go.
OKAY! Now my phone goes straight to the black screen with a Phone on it, and a little red triable with an exclamation point inside everytime now. It used to only come up when i tried going into recovery. now it comes up everytime i load up the phone. does this mean, its bricked...
EDIT: nvm, I was able to load HBOOT thank god, but still having trouble getting the damn recovery.
Well go to amon ra thread in the EVO dev section and dl th pc36img from there...maybe u got a bad dl...
It's here: recovery-RA-supersonic-v2.3.img - MD5Sum: c00243750cc79e4a1dd4888db175b19f
Sent from my PG86100 using xda premium
Okay, so downloaded the file "recovery-RA-supersonic-v2.3.img", put it (recovery-RA-supersonic-v2.3.img) on SD, turned phone off, and now powering on in HBOOT.
After its finished doing whatever it does, can i go straight to recovery, or do i need to reboot again for changes to take effect?
Well, it did the wrong image no image thing again like it always does, and then i tried going into recovery aaaand it didnt work.
Also u should read these I think:
http://forum.xda-developers.com/showthread.php?t=1151733
How to Unroot Your Phone if Using Unrevoked 3
Or
http://forum.xda-developers.com/showthread.php?t=1245649
***How to unROOT Revolutionary from HTC Evo 4G*** EASY! UnROOT and ROOT! 10/20/11
Depending on which method you used to root your phone..
Sent from my PG86100 using xda premium
Did u rename it PC36IMG.ZIP? Be sure not to name it PC36IMG.ZIP.ZIP Sometimes windows hides extentions
Sent from my PG86100 using xda premium
gunfromsako said:
Did u rename it PC36IMG.ZIP? Be sure not to name it PC36IMG.ZIP.ZIP Sometimes windows hides extentions
Sent from my PG86100 using xda premium
Click to expand...
Click to collapse
Yyyeeaaah, about that. I forgot to rename it. *facepalm* Just did it, powering in through HBOOT AGAIN. still did the wrong image no image thing, but this time, about it actually did some progress bar thing on the right hand side. but just for a second, and then went back to saying it was the wrong image or no image.
I highlighted the entier file name "recovery-RA-supersonic-v2.3.img" and renamed it to "PC36IMG.ZIP" and then it turned into a zip file. restarted the phone in nboot and didnt work.
Oops I posted the .img for adb sorry here is the pc36img...*facepalm*
PC36IMG.zip - MD5SUM: 6dbb98f9cfa35033982c3803d2520466
Sent from my PG86100 using xda premium
Okay, so check it out.
I ran the "RUU_Supersonic_1.32.651.1_Radio_1.39.00.04.26_rele ase_171253.exe" before and flashed that, but i remember that i had to unroot my gf's phone back in june, so i went to my downlaod list and saw that i used "RUU_SuperSonic_S_Sprint_WWE_3.70.651.1_Radio_2.15.00.11.19_NV_1.90_release_161482_signed.exe"
So I just did that, and the 3G data seems to be fine. [email protected] Now onward to unrooting.
Now that I have stock ROM, do I just run a S-ON tool and fix it? But I dont have custom recovery, wtf this is effing confusing...
gunfromsako said:
Oops I posted the .img for adb sorry here is the pc36img...
PC36IMG.zip - MD5SUM: 6dbb98f9cfa35033982c3803d2520466
Sent from my PG86100 using xda premium
Click to expand...
Click to collapse
AH HA! lol, okay cool. So when I download this, and put it on my SD and then reboot into hboot, i'll have custom recovery? and then i can run s-on with 3.70? then eventually update OTA...?
Maybe I am wrong and it won't flash recovery with a non rooted ROM but I thought would because of s-off it should... Should of flashed the s on before u ran the ruu. It's signed with HTC keys and would of been fine.
Sent from my PG86100 using xda premium
gunfromsako said:
Maybe I am wrong and it won't flash recovery with a non rooted ROM but I thought would because of s-off it should... Should of flashed the s on before u ran the ruu. It's signed with HTC keys and would of been fine.
Sent from my PG86100 using xda premium
Click to expand...
Click to collapse
YOU DID IT! Horrayy!!!! Thank you my kind, kind kind kind sir!
I am on recovery right now. So now do i follow these instructions...
How to Unroot the HTC EVO 4G
◄●REQUIRED DOWNLOADS●►
Unrevoked S-On Tool
PC36IMG
◄●SIMPLE INSTRUCTIONS●►
If you're comfortable with everything Android related(flashing, recovery, etc.) then its just 2 simple steps:
If you used Unrevoked Forever at any time, flash unrevoked-forever-son.zip from recovery until hboot shows S-ON
Flash the PC36IMG.zip from hboot
◄●DETAILED INSTRUCTIONS●►
If you need a little more guidance, follow these instructions.
◄●If you have used Unrevoked forever, start here●►
Make sure you have downloaded the files linked above. Do not extract them
Connect your phone to your computer via USB and change to "Disk Drive" by dragging down from the notification bar.
If you have NOT used Unrevoked Forever, skip to the instructions below. If you have, transfer unrevoked-forever-son.zip to the root of your sdcard. Do NOT transfer the PC36IMG yet. It'll only cause a hassle and make this take longer.
Once complete, power off the phone
reboot into the recovery by holding VOL DOWN + POWER until it boots to the white screen. Then select RECOVERY.
Depending on what recovery you're using, you need to flash a zip. Select the unrevoked-foreverson.zip that you just transferred and complete the flash.
When complete, power off the phone. Reboot into the bootloader by holding VOL DOWN + POWER until it boots to the white screen. If it says S-ON at the top, select RECOVERY and skip to step 9. If it says S-OFF, repeat steps 5-7 Until it does.
◄●If you have NEVER used Unrevoked forever, start here●►
Power off the phone and reboot into the recovery by holding VOL DOWN + POWER until it boots to the white screen. Then select RECOVERY.
Connect via USB. There is an option for this in both Amon RA and Clockwork.
Transfer the PC36IMG.zip to the root of your sdcard.
EJECT THE PHONE FROM THE COMPUTER and then turn off USB in Recovery
Power off the phone and reboot into the bootloader by holding VOL DOWN + POWER until it boots to the white screen.
It should check the PC36IMG.zip and then ask you YES/NO to apply the update. Press VOL UP for YES
Once complete, Press VOL UP to reboot.
You are now unrooted!
Have I ever used unrevoked? idk if i have! where do i start, or do i just run the s-on tool...?
Yes as long as u rooted with unrevoked and NOT REVOLUTIONARY... make sure to remove/rename the recovery pc36img on root of SD...once s on is achieved either run a ruu or the pc36img from that thread...off to kickboxing I go glad I could help...
Sent from my PG86100 using xda premium
How did u root your phone? When did u root it?
Sent from my PG86100 using xda premium

Categories

Resources