Im trying to get the OTA update that came out in November or so onto a coworkers dinc that we rooted with Unrevoked. It is currently s-off and I need to turn s-on with the appropriate file and then run the update. For some reason when I go into recovery mode to attempt the s-on process all I get is a black screen. Its almost like Clockwork recovery will not fully load. There are no options or anything for me to choose from, its just completely frozen on a black screen (with white borders on 3 edges).
Ive tried to reflash the Clockwork recovery image, thinking something was wrong with it, by using Unrevoked reflash.exe but even that doesnt work. It jsut says 'failed to flash recovery image.' All this is being done on the same machine that the dinc was rooted on.
Is there anyone who has seen this before and can help me?
Edit:
Ive now attempted to put TWO different dincs into recovery and get the same thing. Black screen, no options in green text. Ive waited as long at 10 minutes and nothing ever appears. They just sit there like that. On another note, booting mine to recovery works just fine. All are running baseband 2.15.00.07.28.
takuya619 said:
Im trying to get the OTA update that came out in November or so onto a coworkers dinc that we rooted with Unrevoked. It is currently s-off and I need to turn s-on with the appropriate file and then run the update. For some reason when I go into recovery mode to attempt the s-on process all I get is a black screen. Its almost like Clockwork recovery will not fully load. There are no options or anything for me to choose from, its just completely frozen on a black screen (with white borders on 3 edges).
Ive tried to reflash the Clockwork recovery image, thinking something was wrong with it, by using Unrevoked reflash.exe but even that doesnt work. It jsut says 'failed to flash recovery image.' All this is being done on the same machine that the dinc was rooted on.
Is there anyone who has seen this before and can help me?
Edit:
Ive now attempted to put TWO different dincs into recovery and get the same thing. Black screen, no options in green text. Ive waited as long at 10 minutes and nothing ever appears. They justsit there like that.
Click to expand...
Click to collapse
Are you using the latest Unrevoked?
Look at this:http://forum.xda-developers.com/showthread.php?t=855515&highlight=slcd
Use the search button, there are other threads with the same or similar problem that got resolved.
I did use the search button and found some threads that talked about a black screen, but from looking at those, they were actually getting the green text options and just did not know to use the touch sensor button in place of the power button. This appears to be a different issue. Maybe I am using the seach feature incorrectly, or not putting in the right verbiage, but it only provided unrelated threads.
Thanks for the input. I will make sure I am using the latest unrevoked executable and see if it makes a difference in getting the Clockwork recovery back on and functional.
UPDATE: Unresolved. The phone now has the update applied, but I am unable to re root it and provide wifi tethering. Unrevoked is saying that the process failed and asks if the firmware is too recent. What is this all about? I had no issues doing this when I did it to my phone over a month ago. Any further ideas?
takuya619 said:
UPDATE: Unresolved. The phone now has the update applied, but I am unable to re root it and provide wifi tethering. Unrevoked is saying that the process failed and asks if the firmware is too recent. What is this all about? I had no issues doing this when I did it to my phone over a month ago. Any further ideas?
Click to expand...
Click to collapse
Are you sure you applied the November update? I know there was a more recent OTA that went out, I believe that patched the loophole that unrEVOked used. Maybe you flashed that by accident?
It was definitely the November update. A further search on google actually pointed me in the direction of uninstalling programs that may interfere with the root and also putting it into disk mode when plugged in via USB. I found a program that was erroneously left the during the reflash and once it was removed, the re-root with unrevoked finally worked.
Things seem to be working now, finally. Im now attempting the re-root on the second of the coworkers' phones.
If they have SLCD, you need to flash an SLCD-compatible version of clockwork. Read here
Related
Ok so I am having a strange issue here. I tried to root my buddy's incredible using the newest version of unrevoked. It went through successfully but I noticed when going into the bootloader that it still states S-ON. Also, when I click on Recovery, it takes me to a black screen with white lines on the side. I have tried flashing the recovery multiple times by using the PB31IMG.zip method to no avail. I am guessing at this time the root did not take. So when I try to use Unrevoked again it tells me that root is unsuccessful, my software may be too new (or something to that affect. I have tried it 3 more times, no dice. Just for ****s, I downloaded terminal and it works, I can get superuser access. I tried flashing a recovery at that point with the flash_image method and that doesnt work either, it says image not found or something like that. I dont know if it rooted and didnt turn S-OFF, or if it isn't rooted at all. I tried downloading and just going back to an unrooted stock rom and it said that the software version is older and failed. I have been at it for hours. Please someone help. Thanks in advance.
(By the way, I accidentally posted this in the General Discussion Q&A when I meant to post this here so it's a repost.)
You have to choose in the menu to have unrevoked install s-off.
Your friend's screen is an SLCD screen, not an AMOLED screen. This is why you are getting the black screen with white bars. You need to look on here for the instructions on how flash a recovery compatible with SLCD screens.
Here you go this should get you what you need - http://forum.xda-developers.com/showthread.php?t=855515&highlight=slcd
Thanks so much for the reply. That thread is a lot more informative than the one that was linked in the stickied thread. I fixed it by downloading an RUU and running Unrevoked again. For some reason it just didnt take that time. Thanks again!
Ok so it has happened to me finally.
I was installing a rom. It was unsuccessful so i restored my last backup.
It restored and upon reboot i got 5 vibrates and black screen.
i can get to hboot and hboot usb
hboot ver 92
radio 78
I have tried a couple pb31img. they install all with ok and then 5 vibrate no boot.
I can get to recovery and flash update.zip. 5 vibrates no boot.
I have a replacement on the way.
But i really want to fix it! any ideas?
sorry wrong place mods please move to q&a
/10 characters
Try reformatting your memory card to FAT32 and then put the PB31IMG.zip to the root and try again.
reformat suggestion
did that. only two files on card are pb31img and update.zip. freshly formatted fat32
This is in the wrong section.
But to answer your question, RUU.
Also, root voids warranty. So if they happen to look into it and see that your device is rooted, you'll likely get charged the $100 insurance deductable. Unless you don't have the insurance.. then you'll end up paying the full $549 or whatever it is.
Sent from my ADR6300 using XDA App
un-root and get a refurb. happened twice to me allready/
stoffelck said:
Ok so it has happened to me finally.
I was installing a rom. It was unsuccessful so i restored my last backup.
It restored and upon reboot i got 5 vibrates and black screen.
i can get to hboot and hboot usb
hboot ver 92
radio 78
I have tried a couple pb31img. they install all with ok and then 5 vibrate no boot.
I can get to recovery and flash update.zip. 5 vibrates no boot.
I have a replacement on the way.
But i really want to fix it! any ideas?
Click to expand...
Click to collapse
I've had this happen before. I'm not sure why the nandroid restore would fail, but it may have been because of a near-full SD card. I was stuck at hboot for a while, but couldn't get into recovery. I tried to enter recovery like 30 times and it worked once so I wiped and installed my rom.
i can get into recovery but it is the stock recovery. can only flash update.zip. if i had a rom could i rename it update.zip?
stoffelck said:
i can get into recovery but it is the stock recovery. can only flash update.zip. if i had a rom could i rename it update.zip?
Click to expand...
Click to collapse
no, root is needed for any rom other than HTC
also, then phone will boot if you have it plugged in. get a refurb, ask for over night delivery, they never say no.
stoffelck said:
Ok so it has happened to me finally.
I was installing a rom. It was unsuccessful so i restored my last backup.
It restored and upon reboot i got 5 vibrates and black screen.
i can get to hboot and hboot usb
hboot ver 92
radio 78
I have tried a couple pb31img. they install all with ok and then 5 vibrate no boot.
I can get to recovery and flash update.zip. 5 vibrates no boot.
I have a replacement on the way.
But i really want to fix it! any ideas?
Click to expand...
Click to collapse
I have the same trouble. This happened Monday afternoon after backing up via clockworkmod, full wipe, and flashing cm_inc_full-0.zip. 5 buzzes and green LED flash at boot after the white splash screen.
Previously, I had S-OFF, but after the buzzing, hboot shows S-ON.
I can get the phone to boot completely if I have it connected to my computer, but as soon as I disconnect the cable, the display blacks out, 5 buzzes and green LED flash.
I have flashed the latest Verizon stock PB31IMG (build-3.26.605.1-release-152016-baseband-2.15.00.07.28-hboot-0.92.0000_PB31IMG.zip) and it is successful, but the phone still behaves the same. Trying to flash older stock Verizon firmware does not work, because hboot knows it is older, and refuses to install.
I cannot get adb to recognize the phone, no matter what I do, but fastboot sees the phone at hboot. RUU also does not work, it never sees the phone. Unrevoked starts to run, but quickly stops with a communication error.
From what I have read on this forum and others, this issue is happening quite frequently in the last few days.
I tried the "old school" method for rooting, by running a adb shell loop and trying the eject sd card method. That did not work.
Does anyone have any suggestions as to try?
Alpha Maven said:
I have the same trouble. This happened Monday afternoon after backing up via clockworkmod, full wipe, and flashing cm_inc_full-0.zip. 5 buzzes and green LED flash at boot after the white splash screen.
Previously, I had S-OFF, but after the buzzing, hboot shows S-ON.
I can get the phone to boot completely if I have it connected to my computer, but as soon as I disconnect the cable, the display blacks out, 5 buzzes and green LED flash.
I have flashed the latest Verizon stock PB31IMG (build-3.26.605.1-release-152016-baseband-2.15.00.07.28-hboot-0.92.0000_PB31IMG.zip) and it is successful, but the phone still behaves the same. Trying to flash older stock Verizon firmware does not work, because hboot knows it is older, and refuses to install.
I cannot get adb to recognize the phone, no matter what I do, but fastboot sees the phone at hboot. RUU also does not work, it never sees the phone. Unrevoked starts to run, but quickly stops with a communication error.
From what I have read on this forum and others, this issue is happening quite frequently in the last few days.
I tried the "old school" method for rooting, by running a adb shell loop and trying the eject sd card method. That did not work.
Does anyone have any suggestions as to try?
Click to expand...
Click to collapse
yea, un-root, s-on and get a refurb.
It might be helpful to know which ROM(s) were being flashed when this happened, to see if there is any consistency.
i had been flashing the #XX-inc-cm7src-syko-eng packages before I flashed cm_inc_full-0.zip
I am having this same problem, to the letter. I had been running Skyraider and wanted to try MIUI. However, I was only preparing to flash a new rom. I hadn't even put the rom on the sd card yet. It was giving me issues getting into clockwork and when I finally managed to get in, it wouldn't backup. I reformatted my sd card and tried again; it said it succeeded doing the nandroid backup and when I rebooted it started doing the 5 vibration no boot thing. I never actually even loaded a rom, all I did was a nandroid backup, which I can't find on my sd card now so it apparently failed despite the message.
I messed with this for a day and managed to get the stock november OTA loaded with s-on via timely connection and disconnection to my pc, so I shouldn't have a warranty issue. I took it into the verizon store and they overnight shipped me a refurb. Unfortunately, it was evening when I went in so it could apparently take until monday
In the meantime, I can still use it if I turn it on while connected to my pc and disconnect as soon as I see the "quietly brilliant" screen. If you wait until it boots all the way in it will usually shut down vibrating when you disconnect it. Hope that helps someone that just needs the phone to work for a bit. Would love to know if someone finds out what is happening and if there is a way to fix it.
Don't know if this helps but I had been having issues with my phone frequently telling me the sd card was mounted read only leading into this, but it would usually fix itself if I tapped the icon that popped up. I also had lost the ability to unmount the sd card prior to this, and the phone would no longer work as a mass storage device when connected to the pc. I thought it was a problem with Skyraider but now I'm not so sure. Don't know if others are also experiencing this, but even now that I got it running on stock and into the os the 8gb internal phone storage and my sd card no longer register.
This basing on the info I have gather from people smarter then myself...
5 vibs = qualcomm download mode. From what i have been able to gather a simple batt pull should resolve the issue.
The way you get into this download mode is by pressing the vol+/- at the same time. Kinda explains the reason it is becoming so frequent.
I have no proof to back this up but give it shot.
Okay, so do you have CWM at this point?
CWM?
Sent from my ADR6300 using XDA App
Ok, I'll try to keep this simple and informative.
I have been rooted with unrEVOked for months. Last night I flashed CyanogenMod 7 RC2. (I've posted this there too on their forums) Today my Evo crashed while using the app QR Droid, and now goes into a boot loop after the "htc EVO 4g" white screen. It loads that screen, then goes black, reboots and does this cycle until I pull the battery.
I can get into hboot. (v 2.10.001, Clockworkmod), S-OFF, updated radio last night when I actually could before I flashed CM7 RC2 to 2.15.00.11.19.
Here is where the problem deepens, and is very similar to this thread; Bricked Evo, and cant factory wipe. Help please
When I try to select Recovery, the boot-loop starts over; so i actually cant get into recovery and flash anything from the sd card it also does not give me any triangle bull**** or whatever, just starts the boot loop.
I have a card reader for my micro sd card; I took everything off of it and put an RUU on it, renamed it PC36IMG.zip, got into hboot, tried to update it and it failed, goes back to the boot loop. I believe the ruu was outdated.
Can someone link me to the most recent recovery image? I should use to get back to stock? I think that is my problem, the ruu is out of date.
Or any other input would be greatly appreciated.
Thanks
I tried this recovery image to know effect, when i reboot after applying update it goes back into loop; CANT POST LINK YET!
mhport2 said:
Ok, I'll try to keep this simple and informative.
I have been rooted with unrEVOked for months. Last night I flashed CyanogenMod 7 RC2. (I've posted this there too on their forums) Today my Evo crashed while using the app QR Droid, and now goes into a boot loop after the "htc EVO 4g" white screen. It loads that screen, then goes black, reboots and does this cycle until I pull the battery.
I can get into hboot. (v 2.10.001, Clockworkmod), S-OFF, updated radio last night when I actually could before I flashed CM7 RC2 to 2.15.00.11.19.
Here is where the problem deepens, and is very similar to this thread; Bricked Evo, and cant factory wipe. Help please
When I try to select Recovery, the boot-loop starts over; so i actually cant get into recovery and flash anything from the sd card it also does not give me any triangle bull**** or whatever, just starts the boot loop.
I have a card reader for my micro sd card; I took everything off of it and put an RUU on it, renamed it PC36IMG.zip, got into hboot, tried to update it and it failed, goes back to the boot loop. I believe the ruu was outdated.
Can someone link me to the most recent recovery image? I should use to get back to stock? I think that is my problem, the ruu is out of date.
Or any other input would be greatly appreciated.
Thanks
I tried this recovery image to know effect, when i reboot after applying update it goes back into loop; CANT POST LINK YET!
Click to expand...
Click to collapse
I attatched a PC36IMG of Amon Ra recovery version 2.3. You can try flashing that from the bootloader. I will also provide a link to the most recent RUU's and PC36IMG's. This link actually has all of them, old and new. Hope you're able to recover the phone dude. Good luck.
http://forum.xda-developers.com/showthread.php?t=884060&highlight=hboot-0.97+ruu
thanks, I have clockworkmod from when i unrevoked and had it updated via the CM7 rom manger last night, does that matter?
I tried that img you attached, it did not work, Im not exactly sure how to use the RUU's could someone explain what else I should do?
mhport2 said:
thanks, I have clockworkmod from when i unrevoked and had it updated via the CM7 rom manger last night, does that matter?
Click to expand...
Click to collapse
should'nt make any difference at all. I'm not sure how your initial problem happened, but you are not the first I've seen this happen to. Most that I've seen were recent, and were running CM7. Not sure what's up with that, but if you search the q and a section, you'll find a few similar threads. Very strange. I hope you ge it working again.
Happened to me and a few others a week or 2 ago. There was no fix that we found. Pc36img wont work, ruu won't work. U won't be able to do anything to get s-off to s-on either (in my experience.) Even tho u can get to bootloader, if its like what happened to me and a few others, ur bricked. I got mine warranty replaced (but they're still gonna charge me $125 for returning an unrecoverable phone) another guy threw his out his car window and they charged him $100 to replace his "lost" phone. Those are the only options I know of.
Sent from my PC36100 using XDA App
Hi All
Firstly I am sorry if the answer to this is buried somewhere in this forum, but I have honestly spent about 4 hours ready through threads trying to find a solution to my problem and have not got anywhere.
I originally 'rooted' my phone with Unrevoked. I ran Calkulin's rom for ages (what a great rom builder!). I then had a mysterious problem with my phone whereby all incoming calls went to voicemail. It required visiting a Sprint store, and unfortunately flashing back to stock.
At the store, my phone was upgraded to Sprint 2.3.3. Now my phone is working, I would now like to go back to custom roms.
When I boot in to recovery my phone shows S-OFF and HBOOT 2.16.0001
I have tried to downgrade my phone to an older version of the Sprint rom, but cannot get it to install (I just get the red exclamation mark icon). Forcing the rom install in the recovery menu (the Sprint recovery menu with the blue menu options) doesn't work either.
I have also tried the "recovery-windows.bat" tool, that lets you reboot into recovery mode, but it won't recognize my phone is connected, and crashes, and no reboot
The key is that I have S-OFF, so I should be able to downgrade... and once I find out how to, I know how to take it from there, but I can't find a way to downgrade that works!
Any help would really be appreciated!
Thanks
Loz
Download the amon ra recovery zip, rename to pc36img.zip, place on root of sd card. When in hboot it should read the file and ask to install it. After that you should be able to get into recovery from hboot.
ljstevens said:
Hi All
Firstly I am sorry if the answer to this is buried somewhere in this forum, but I have honestly spent about 4 hours ready through threads trying to find a solution to my problem and have not got anywhere.
I originally 'rooted' my phone with Unrevoked. I ran Calkulin's rom for ages (what a great rom builder!). I then had a mysterious problem with my phone whereby all incoming calls went to voicemail. It required visiting a Sprint store, and unfortunately flashing back to stock.
At the store, my phone was upgraded to Sprint 2.3.3. Now my phone is working, I would now like to go back to custom roms.
When I boot in to recovery my phone shows S-OFF and HBOOT 2.16.0001
I have tried to downgrade my phone to an older version of the Sprint rom, but cannot get it to install (I just get the red exclamation mark icon). Forcing the rom install in the recovery menu (the Sprint recovery menu with the blue menu options) doesn't work either.
I have also tried the "recovery-windows.bat" tool, that lets you reboot into recovery mode, but it won't recognize my phone is connected, and crashes, and no reboot
The key is that I have S-OFF, so I should be able to downgrade... and once I find out how to, I know how to take it from there, but I can't find a way to downgrade that works!
Any help would really be appreciated!
Thanks
Loz
Click to expand...
Click to collapse
Download the pc36img of amon_ra, toss it on your sdcard, and reboot into the bootloader. It should install the recovery and let you get back to flashing Roms. I did almost the exact same thing, have s-off with 2.16 and have no problems flashing roms after I got a recovery installed.
Sent from my PC36100 using XDA App
Thanks guys, successfully flashed back to a REAL rom! Annoyed I couldn't find this simple solution! Soooooo many hours reading through threads.
Hello. I'm in a bit of a bind which I cannot get myself out of, so I am posting here. I've been around for over a year lingering, updating, trying new things, etc. I came across a free Incredible, which I attempted to root, and install a ROM onto. I rooted the phone with Unrevoked 3, booted into Clockwork mod recovery, made a nandroid, and installed the ROM. The installation was successful, however, on boot after the HTC splash screen the phone vibrates 5 times and the led flashes green constantly. The same thing happened when I tried to boot into recovery.
I found that the phone booted to the Set Up, which crashed, if it was plugged into a computer. I ADB saw the device but I could not push files or execute commands. Unrevoked S-OFF would not work also.
After Googling, I found a 2.2 RUU, which installed successfully, but I get the same boot problems. If the USB is plugged into a computer before the phone is turned on I actually get to Android and can play around. The phone will not recognize any memory, SD or internal; only phone memory is recognized. I tried ADB again with no luck, most likely has to do with the phone not recognizing memory. So I flashed the RUU from HBOOT which flashed fine, but the same problems still persist.
I am out of ideas, which I hope someone has anything I can try.
S-ON
HBOOT 0.92
MICROP-0417
TOUCH PANEL - ATMELC03_16AC
RADIO 2.15.00.07.28
Edit: I tried to be as detailed as possible, so ask any questions if I did not make since.
Check this out
http://pvillecomp.com/?page_id=33
Thank you, trying it now.
cmlusco said:
Check this out
http://pvillecomp.com/?page_id=33
Click to expand...
Click to collapse
I cannot thank you enough.
Edit: Unrevoked gave me s-off. I want to be clear this time before I install any ROM. Do I need to run unrevoked-forever.zip? I am 99.999% positive I do not since I already have s-off. I want to get a new ROM on tonight.
Unrevoked 3 now contains the forever patch, as previous versions did not. So you are good to go flash away, after making a nandroid of course
No need for unrevoked forever if you are s-off
Thanks! On my way to a new ROM.