Related
I have an HTC Incredible that i ran the first unrevoked2 update to get root on my device, then unrevoked3 to get s-off. I then was pushed the 2.2 OTA update, which when done through the phone fail. So, like an idiot of course, I ran the update.zip from clockworkmod and now my device is acting all strange (practically bricked).
After the update, the 'droid' eye loads, then goes to a white HTC page where a small dialogue box goes from 0 to 95% then reboots, repeatedly, until I interrupt this via a battery pull. I then get into my phone, but the camera, sdcard, wifi, etc are not recognized. Eventually I get a force close prompt for 'system' which I can wait or force close, either choice, my device will reboot at max 5 minutes.
I have the following showing at HBOOT
Incredible XC Ship S-ON (i ran the s-on update now)
HBOOT-0.77.0000
...
RADIO-2.15.00.07.28
I'd like to get my phone either running Froyo, or back to the stock ROM, and am in need of help. I've ran several PB31IMG.zip files located through numerous guides and dozens of searches to try and get back to stock, but I either get 'update failed' because of some kind of version check, or the update doesn't work (maybe now because I'm s-on?).
I'm in sad need of help, I found another thread where someone else was in my similar situation on another forum but its old, no one is responding, and the update worked for them and not myself. I'd really appreciate it if someone would walk me through un-screwing my device if possible. Much appreciated.
alright well if i was you i would do this.
turn security back off (s-off)
grab the PB31IMG.zip for 2.2 froyo/ or if you want the ota again grab the 2.1
then it should work fine. but i also see the your hboot is not up to date for froyo so maybe find the PB31IMG.zip for 0.92 hboot. i dont have any idea about where it is located but i have the file for 2.2. but alas, i dont have a place to upload it soo yeeaaah. anyway that is what my first choice would be. choose to follow or not.
p.s. i know i say but alot haha
BTW yes, PB31IMG's wont work because you are s-on. and the ota probably did not work because you had clockworkmod recovery instead of stock recovery. thats all i got for ya. hope my terrible explanations help
Well, this might be more promising.
I did notice that my HBOOT was quite out of date, so amongst all of the files I've downloaded, I'm pretty sure the one that might have done it for me was the RUU update file. I of course re-ran the s-off update from unrevoked-forever, then started hacking away at the RUU update. I downloaded the RUU update from Google, ran it, copied the rom.zip file from the temporary files location, renamed it to PB31IMG.zip, copied it to the root, and then poof, noticed the HBOOT was updated (looks like this could have been the root problem).
Needless to say, i'm back to setting up my device (raw), hope that I can still get to root on my device; but at least I'm back to an operating phone!
OK
Looks like I'm at HBOOT-0.92.0000 with IncredibleC XC ship S-OFF still; RADIO-2.15.00.07.28.
Doesn't look like I have a recovery mode (clockworkmod).
I'm guessing if I'm going to root my device I'll need to re-install clockworkmod? Thanks for any future help.
so you still have the reboot thing, going on
Sent from my ADR6300 using XDA App
tjamscad said:
so you still have the reboot thing, going on
Click to expand...
Click to collapse
No, my device is unbricked (so to speak). Since updating using the full RUU it successfully re-flashed everything. Only problem I have to fix now is rooting my device again.
Well I guess I have my work cut out for me searching how to get my s-off phone rooted again. Anyone got a suggestion?
Sent from my ADR6300 using XDA App
if your phone is s-off then search around for a custom recovery in the pb31img format. flash in bootloader, reboot into recovery and flash the rooted rom of your choice.
So my fix was:
1. Ensure phone is already rooted and S-OFF
2. download RUU_Incredible_C_Froyo_VERIZON_WWE_3.21.605.1_Radio_2.15.00.07.28.exe
3. Run the RUU file
4. Go to my temporary files location, sort by date, and look for the rom.zip file
5. copy that file off someplace else and rename it PB31IMG.zip, cancel RUU Update program
6. Copy PB31IMG.zip to the root of the SD Card
7. Boot my device holding volume down (HBOOT)
8. Allow the update to proceed (will reboot phone almost immediately to update HBOOT from 0.77 to 0.92)
9. Once update was completed, phone reboots final time after prompt
10. Setup phone again (RUU Update is a clean flash)
Still looking out for better instructions on how to re-root my device other than a manual one, but if I must then I must =) Was hoping that I could use unrevoked3, but the last push didn't work out.
you have to do it manually cause unrevoked doest work on newest ota
I can help you reroot if you need it. Im glad you have everythig else worked out though. Congratulations!
sent from Ioslver
ok well basically load this in bootloader and you are rerooted.
the download link for the file is here:
http://www.mediafire.com/?oj6aqi1ceqpm58g
patalo said:
ok well basically load this in bootloader and you are rerooted.
the download link for the file is here:
http://www.mediafire.com/?oj6aqi1ceqpm58g
Click to expand...
Click to collapse
So that PB31IMG.zip (renamed) will re-install the most recent clockworkmod recovery? I saw some other post which also had a 'payload-update.zip' and a 'su-2.3.2.1-ef-signed.zip' file ... not sure if I'm missing something.
Also, according to their latest release (their = unrevoked), http://unrevoked.com/rootwiki/doku.php/public/unrevoked3 - This supposedly works with all versions of supported phones. Of course, when I go to http://unrevoked.com/rootwiki/doku.php/public/unrevoked2 it says that unrevoked3 doesn't work with stock Android 2.2 phones... which I'm guessing might be my condition since I had to flash the rom.zip file from RUU_Incredible_C_Froyo_VERIZON_WWE_3.21.605.1_Radio_2.15.00.07.28_2k4k_NV_1.50_PRL58006_release_143351_signed.exe that I got from google.
Some clarification would be appreciated.
Looks like I'm back to root. Ran the PB31IMG.zip that was about 2.86mb, then payload-update.zip and the Su zip (anyone know where the most recent one is? Says there is an update).
Now to test WiFi tether again, see if I still need that evo driver still.
Sent from my ADR6300 using XDA App
You don't need the payload and stuff. After s-off all you need is the clockworkmod PB31IMG.zip to get root back
sent from Ioslver
The wifi tether has nothig to do with root. On some roms or just sometimes it wont work.
sent from Ioslver
I Have a Question, Would it be Possible to Root the Phone With a Update.zip From Android Recovery, Where it Says (Install From Update.zip)? Either That or Turn S-Off, Or Install Su, Clockwork Recovery...... Something? If Someone Can Help Please Do!! Or If Someone Can Try to Sign a Update.zip For Me With S-Off in it!! (Unrevoked.4Ever) I'd Loveto Find a Easier way that can be Done WITHOUT CONNECTING TO A (USB) PORT PC!!
Technically no. Because rooting your device is getting rid of the stock recovery so you can install rims and whatnot. But you can root through hboot easily with s-off or with s-on use unrevoked.
sent from Ioslver
So I'm wondering if the payload-update.zip was damaging in some way.
In any event, now I'm constantly being nagged about another 17.7mb update from Verizon which of course, like the Android 2.2 update, won't apply via the usual system update message.
I don't know where I can find this file, but it says this:
---
Android Update
Downloaded and verified 17.7 MB
This software update includes the installation of V CAST Apps, Slacker, and many other improvements for your DRIOD Incredible by HTC. ... blah blah blah ...
---
I don't know if this is the infamous 'November' update or not. I know that I updated my rom from the RUU file downloaded from dl.google.com, so its possible that I don't have this patching. Some clarification on what this download is, where I can find it (online or my phone), and if it is possible to apply this update and how (so I don't keep getting annoyed with it).
Hey guys,
I've search through many forums for someone with similiar problems but to no avail.
I had my EVO rooted with unrevoked 3. I needed to have my phone repaired at the sprint store and since a rooted phone constitutes a voided warranty, I attempted to UN-root. I followed the DROID DEMO 2-STEP UNROOT to the tee.
After attempting to flash the pc36img, It gave me the error of :Main version older
Tried to flash the stock ruu image, wouldn't work either. Someone told me to remove the s-on image on my sd card and replace with s-off. I did that and it let me flash the pc36img, went through all the ok's and after complete and reboot, it boots to fastboot only. Also, I cannot get into recovery(triangle screen).
I downloaded android sdk with the usb drivers so I could flash the unrevoked recovery image through adb. When I go to command prompt to enter adb, the device is not found. Im guessing because USB DEBUGGING has to be enabled on the device. Since I cannot get into recovery nor boot my OS, is there any other method of forcing usb debugging on the device?
Or, If there something else I could do to get my evo to boot normally?
Any help would be definitely appreciated(A LOT!!!)
Im not really an expert(i know, why did I play around with something im not familiar with) So please bare with me. Thanks in advance!!
You're nowhere near bricked. Quickest solution would be to push Amon_RA over fastboot, then flash the same version or older ROM as the 2-step solution so you can actually use it.
If for some reason that gives you trouble, you're still S-OFF so just grab a rooted PC36IMG.ZIP and let the bootloader flash that one. Then you can still push Amon_RA through the OS using the Rom Manager (the one for clockwork, but which lets you flash alternate/Amon_RA recovery).
EDIT: I think the 1st method (fastboot commands) might only work on hboot 0.76 which you are probably not on. Use the 2nd method (ROM Manager), more info here: http://forum.xda-developers.com/showthread.php?t=744918
Thanks for your help! I guess I had a bad version of pc36img, I re-downloaded another version and it worked perfectly.
Thanks again, bro
So, I have had my EVO rooted for a while now but it has recently developed a charging issue with the USB port. I want to take it into Sprint to have it looked at so I need it unrooted.
I used unrevoked to root it in the first place so I followed the instructions on their site to unroot. I hit and odd snag at that point. You are supposed to flash the s-on path in recovery, which worked fine, then reboot to HBOOT and let it install the PC36img file, which is where my problem first started. No matter how many times I tried it would not install that file. It kept saying it was older than the rom version I was running. From there I also tried multiple times to install from HTC Sync with offical RUUs which achieved the same result. Getting frustrated I put s-off back on and tried the pc36img once more with great success. It booted right into an older stock version of Android.
Here is where I'm currently at. I went back to HBOOT and tried to launch recovery and...oops...the custom recovery is gone and all that is left is the very stock 3 option one where the only thing I can flash is update.zip leaving me unable to enable s-on again so I can take it to the Sprint store.
I have tried rerooting again with unrevoked and it keeps failing to install custom recovery. Any ideas? Is there possibly an update.zip out there that would turn s-off to s-on?
Thanks.
I tried to update my Hboot the other day to .92 i believe from .78. Thinking it was as simple as flashing it through bootloader and thats it. I was stuck at the white htc screen for hours so I figured I was screwed. I wiped everything with no luck and then I flashed something so now my HBoot is 0.77.0000 and my Radio is 1.00.03.04.06. I was previously running CM7 nightlies. After flashing whatever zip I did I was trying to reverse what I did by "downgrading" and what I did was delete everything. I cant boot and I also dont have recovery anymore. I can only use Bootloader. PLease any help I can get is appreciated. If u can tell me how to fix this ill make a 10 dollar donation to your paypal. My e-mail is [email protected] if u want me e-mail any information. Thanks a ton
Try the following link.
You may need to get an usb sd card reader. That way you can put the needed files using your pc.
I am sure someone more knowledgeable will come along to help you.
I read somewhere that if you can get to the bootloader, it might have not neen bricked yet.
http://dougpiston.com/?page_id=77
Download this file
http://www.fourty.net/~berzerker/sto....605.1_RUU.zip
Rename it to PB31IMG.zip, put it on the root of your SD card, Boot into the bootloader (hold vol- and pwr) and let it run the update. After it is done you will be back to a stock 2.2.
I forgot to mention in my initial post that I also updated my radio to the newest 2.15 but still had recovery after I did that and after that is when I tried to downgrade everything and lost my recovery. Didnt know if that makes a difference or not. Thanks for the quick replies
Goos3y that link you sent me says 404 not found.
ok there is hope. I am a littl confused though. Do you have recovery?
No i do not have recovery only hboot. I am using my lady's Droid X with my SD card to put any files on the card that I need to.
http://dougpiston.com/?page_id=108 download the PB31IMG.zip put it on the root of the sd card and flash through bootloader as previously stated. Make sure it is named PB31IMG.zip or it wont get recognized. You will loose root and have S on. Thank doug piston for the dl.
sent from my streak7
this is not in the right section but if you can still get into recovery restore a working nandroid back up. after that go to backup and restore>advanced restore and restore your boot image. im pretty sure upgrading you hboot erases your boot image.
EDIT: I saw that someone posted a PB31IMG up earlier. I'd try that one first,
This is for the RUU exe.
An RUU is a program which links to any phone that can get into bootloader, and installs a completely unrooted stock image to your phone. It can be done either by using the linked program (an exe) or getting an ruu version that is a zip and running it on bootloader with a specific filename "PB31IMG.zip"
This tutorial is for the EXE version linked below.
WARNING: I have no idea what happens if this is used on an SLCD incredible.
Therefore, you need to know what kind of screen you have, and I'm no expert on that.
DONT use this RUU if you find out you have an SLCD screen.
I am not sure whether android sdk tools or htc usb drivers are nessesary for the ruu, so if anyone can comment on the necessity of these, i would appreciate it.
Heres what you need:
1. A PC
2. The RUU exe file
3. a cable to connect the PC to your phone
4. The knowledge of whether your phone is an SLCD or not.
Instructions:
1. Hook up your phone to the computer
2. Put the phone into hboot
3. Run the ruu
4. If it messes up at the usb detection thing, keep the phone plugged in, exit the ruu program, and then run it again. It should work then.
At the end of this process you should have a fully functional unrooted froyo incredible.
You dont need to give anyone $10. We all want your phone to work.
The link:
http://forum.xda-developers.com/showthread.php?t=829783&highlight=ruu
Thanks Football!
Hellzya said:
http://dougpiston.com/?page_id=108 download the PB31IMG.zip put it on the root of the sd card and flash through bootloader as previously stated. Make sure it is named PB31IMG.zip or it wont get recognized. You will loose root and have S on. Thank doug piston for the dl.
sent from my streak7
Click to expand...
Click to collapse
You will lose root (easy to get back) but will still be S-off.
You can either use the PB31IMG or the .exe method. Just grab the files off doug piston's website. We've had a lot of problems with SLCD owners grabbing the RUU off youtube and other sites then having a screen that no longer works.
I tried the PB31IMG zip method but in hboot after searching through the file it says no image. I am going to try the RUU now. Do i need to have the android sdk stuff on this computer for the RUU to run correctly? I am using a different laptop, one which does not have the driver files installed that I needed to initially root my INC.?
s197 said:
You will lose root (easy to get back) but will still be S-off.
You can either use the PB31IMG or the .exe method. Just grab the files off doug piston's website. We've had a lot of problems with SLCD owners grabbing the RUU off youtube and other sites then having a screen that no longer works.
Click to expand...
Click to collapse
Unfortunately Marty, its not easy to tell which is amoled and SLCD without having the phone on to verify that its hardware revision is 002 or 003.
002=amoled
003=slcd
If you still have the box i'd recommend looking at it.
I thought you loosed s-off but ok. Did you make sure the PB31IMG.zip was not named .zip.zip?
sent from my streak7
marty454 said:
I tried the PB31IMG zip method but in hboot after searching through the file it says no image. I am going to try the RUU now. Do i need to have the android sdk stuff on this computer for the RUU to run correctly? I am using a different laptop, one which does not have the driver files installed that I needed to initially root my INC.?
Click to expand...
Click to collapse
Well, if you run it without them, and it doesnt work, it wont make anything worse. It just wont work, and then youll know. It probably has nothing to do with the SDK and more to do with HBOOT USB drivers. I would say go for it without any of that.
The most important thing you can know is that your incredible is not bricked. Its totally fixable.
I screwed mine up in precisely the same fashion early on, and used the EXE with good success.
Im positive. I got the phone in august of 10 through verizon. I dont have the box anymore. I have looked into it before and think "think" I have the amoled screen.
marty454 said:
Im positive. I got the phone in august of 10 through verizon. I dont have the box anymore. I have looked into it before and think "think" I have the amoled screen.
Click to expand...
Click to collapse
August = AMOLED
SLCD didnt start to ship until september.
The RUU is loading now. Its at 76% on Updating system. So, if this does work where does my phone stand? Do I need to re-root get s-off and things of that nature?
You will still have s-off. Your phone will be on a .92 hboot with the 2.15 radio. You will need to either rerun the root tool to get recovery back or use a recovery that is flashable through hboot. If using the PB31IMG didn't work for you before I suggest rerunning the tool.
Once recovery is installed do not attempt to restore from within recovery, instead download another rom and flash it through recovery.
Just wanted to drop back in and say thanks to everyone who helped me get my INC back. I really appreciate it and I can throw the BB Storm back in the closet!
Hi Guys, I posted this in Android Software and Hacking General, but I didn't get a reply. Probably the wrong section!
my HTC Desire GSM is stuck in Fastboot and won't boot into the ROM. The background to this issue is that I installed S-Off and then ClockworkMod and flashed Cyogenmod 7 to see if it would fix a reboot issue on the phone. The damn thing just reboots itself when the CPU is used heavily...
Anywho, after realising that Cyogen wouldn't resolve the issue I flashed the standard Virgin UK rom back over it and upgraded to 2.22.351.2 via the system update feature. The problem was that ClockwordMod was still installed and I had to get rid of it to sent the phone off for repair to Virgin!
So I did further research and found that I could flash HBoot via the AlphaRev.nl downgrader tool. I downloaded it and popped it into the root of my SD card and it flashed the bootloader back to Hboot 0.80.0000. That should have been it, but all of the sudden the phone no longer boots into the Rom. All it does is to power on and then go into Fastboot. That's it! When I try putting the standard Virgin Rom back onto the SD it tries to load it and then says "Main Version is older!" "Update Fail!".
How do I get around this now? The phone doesn't boot, so I can't re-flash S-Off and start again, not am I able to run the stock Virgin Rom within Windows because it complains about the versions.
Is there any ways around this situation? I just want to get the phone back to stock so I can send it to Virgin and get it repaired.
P.S. I *have* used the search function and spent the last 4 hours testing various things but I'm now stuck.
Cheers Guys!
Mich
Well you obviously fckd up with the Downgrader, you should have run it first BEFORE RUU. Also did you flashed Stock Hboot prior to Downgrader? (if you used CM7 earlier)
I never played around with the hboot downgrading etc. so i wont be able to help you but im sure there is some workaround...
as your returning your phone anyway why don't you try the official HTC gingerbread update from the HTC developer site (sorry I don't have a link). It should return your phone to stock and when you get it back you need to use revolutionary to get s-off back. Also, there is a sticky from user bortac which has loads of help and trouble shooting advice.
iain2510 said:
as your returning your phone anyway why don't you try the official HTC gingerbread update from the HTC developer site (sorry I don't have a link). It should return your phone to stock and when you get it back you need to use revolutionary to get s-off back. Also, there is a sticky from user bortac which has loads of help and trouble shooting advice.
Click to expand...
Click to collapse
Any advice that uses the 2.3.3 RUU to fix something is plain bad advice - it can just make your problem a LOT worse.
@OP Go onto my guide, look at RUU problems for help
What you need to do:
-Make a goldcard (there is a tutorial there)
-Flash the WWE RUU
Guys, upgrading to Gingerbread has actually brought the phone back from the dead! =) And I can now return it to Virgin to get it repaired properly. The symptoms are that while the phone is plugged in and charging, and I'm doing stuff (taxing the CPU), the phone will eventually simply rebooting itself. Just *BANG*! And it's gone. And once it starts it's a bit of a run-away thing and just keeps on doing it until you leave the phone alone for a bit. Virgin had a look at it and simply re-flashed it, thinking that they could away with that. Typical, overworked, non-creative call centre workers..... I'm well pissed off with them!
Gonna send it back next week and force them to swap the motherboard or something, cause this is a serious fault with the phone.