Related
Hello,
I've been rooted for over a year now. Have flashed back and forth roms around hundreds of times now. Unfortunately an hour after flashing synergy godmode and some of the godmode tweaks, my phone rebooted while idling and bootloops.
Now i am stuck in hboot and can not enter recovery. I am using hboot 0.76.2000 (pc3610000) and s-off. I have tried flashing seperate clockwork and amon-ra embedded pc36img.zip, these say that they will complete updating but then will bootloop after i try to enter recovery. I have tried these updates with a different sd card (as my current sd card w/godmode may be an ext2 partition?) but that has not changed anything either.
As i understand, I can only push files with adb through recovery; which i can not get into.
If anyone can please help it would be very much appreciated.
Thank you in advance
try this way? its how i flash my recoveries when im switching or testing...
remove any pc36img.zip files from your sd and boot to your bootloader...
when you bootloader boots up let it scan for the pc36img whatever thing and let it say not found...
now highlight fastboot and click the power button and wait for FASTBOOT USB to show up...
then type in these codes...
Code:
fastboot devices
it should output some info, if you get some serial number then your good
then type in...
Code:
fastboot flash recovery *whatever the name of the recovery your using is*
so like for amon_ra 2.3 (which is what i use is)
Code:
fastboot flash recovery recovery-RA-supersonic-v2.3.img
just make sure that the recovery img file is in the same directory as the fastboot.exe file on your comp (its should be with all your other sdk stuff like adb.exe and such)
if all goes well then itll say
pushing recovery OKAY
writing recovery OKAY
and the amount of time it took...
then click back into your bootloader and go to the newly written recovery
(i apologize in advance if you already tried this with no avail)
I've set up fastboot usb and done this. Everything wrote ok and finished, however i still bootloop when trying to access recovery. I have tried multiple recoveries including clockwork 3, recovery-RA-supersonic-v2.3.img, and doing entire nandroid restores using nandroid recovery batch script. In both cases everything passes and nothing seems to be functional afterwards.
Any other ideas?
dunno man.. im just trying to visualize how it bootloops going to recovery.. it should be the white htc screen (or any other splash you may have set on there) and then boink recovery... does it like just sit there on the splash and thats it?
try letting it boot normal and then when it goes to the rom loading screen type in
Code:
adb reboot recovery
other than that something is totally askew bro
When booting, i'll get the white htc screen for 4-5 seconds, then it'll power off and reboot, unless i boot to hboot. When i hit recovery, it goes black for a second, then reboots to htc screen and repeats.
I've also tried complete wiping recovery and reloading using fastboot commander, and doing full pc36img.zip that include hboot, radio wiimax updates etc http://forum.xda-developers.com/showthread.php?t=830153&highlight=wimax
I may just go into a sprint store today. Was trying to avoid it as I really don't want to be stock again.
This may be a little progress....
I updated to hboot 0.93.0000
Now when i try to flash recoveries by hboot they pass and bootloop still, but when i try to flash recoveries by fastboot via pc -
"writing recovery..
FAILED (remote: not allowed)
does this provide any insight? going to try downgrading hboot again
the only hboot that allows fastboot commands is 0.76 unfortunately
try running an ruu maybe? other than that i havent the slightest idea
I used this RUU - http://forum.xda-developers.com/showthread.php?p=7529500
It passed every step, but still bootloops when booting to ROM and Recovery.
I'm out of ideas....
I'm going to go with hardware problem.
Sent from my PC36100 using XDA Premium App
bad sector on the internal flash memory ?
My brother has the same problem and i have been trying to fix it with no luck. When i boot the phone up its beeps/vibrate 5 times, then sits on a black screen. I can get into hboot and load pc.....whatever files, it says they work but still reboot, 5 beep, ect. I was going to try an RUU next i see that didnt work for op.
i just ran into this problem today. I was at work when it randomly rebooted and now is stuck in a bootloop. i have tried everything even using the latest RUU. it finished but still bootloops. I am also not able to get into recovery. Sucks because im out of warranty.
So let me get this straight...you can't go into recovery because there's no recovery? You've installed drivers and ran RUU and still nothing? That seems weird because i had the same issue when i first rooted my phone with unrevoked, all i did was run the RUU and it restored my phone back to "stock" and i re-rooted again but this time using z4 root. You might just have to take the phone back to Sprint
Same issue but worse
I'm having the same issue as the OP except that my buttons (power and volume up/down) will not respond. I have scoured these and other forums for a situation like mine and have found none.
I have tried flashing recoveries, RUU's and jsut about anything someone says.
First screen says:
supersonic evt3 ship s-off
hboot-2.10.0001
touch panel atmelc03_16ac
oct 15 2010 12:01:00
hboot
fastboot
recovery
clear storage
simlock
hboot usb
then it scans the sd card for the pc36img zip. It will load but will freeze on the next screen:
parsing...... [sd zip]
1. boot loader
2. radio
3. boot
4. recovery
5. system
6. user data
7. splash
8. wimax
it will stick here and I am completely lost. My old Palm Pre will only suffice for a day.... max.
If anyone has come across a situation like this that might help me, would you please point me in the right direction. Thanks!
kdbrown5 said:
This may be a little progress....
I updated to hboot 0.93.0000
Now when i try to flash recoveries by hboot they pass and bootloop still, but when i try to flash recoveries by fastboot via pc -
"writing recovery..
FAILED (remote: not allowed)
does this provide any insight? going to try downgrading hboot again
Click to expand...
Click to collapse
If you look in autoroot thread in my sig the "tools" zip has something that will let you flash different partitions from fastboot. If you use that to flash the PC36IMG from here it will give you the eng hboot back and possibly reflash whatever got corrupted.
Keep in mind, that will only work properly if you are not using one of the 2.xx hboots. Only phones with a 0.9x hboot will let you use it.
Hello!
Here are some details:
BRAVO PVT4 SHIP S-ON
HBOOT 0.93.0001
MICORP-051d
RADIO 5.09.05.30_C
I'm rooted, and was running the latest version of Oxygen (as of a few days ago).
I did a search, but couldn't find anything.
So here is my problem: a few days ago my phone, after installing the latest version of Oxygen, I noticed my phone was shutting down after prolonged use. I thought it was because of overheating, caused by an overclocking problem or something.
Now, however, it won't get past the white loading screen with HTC on it. I can hold volume down and get into HBOOT, but as soon as I select recovery, the same white HTC screen shows up. The screen stays there until I have to remove the battery. It never boots up, and I cannot get into recovery.
I have tried:
Clearing storage from the HBOOT menu
Reflashing Clockwordmod (however, I realized you have to be S-Off to do this, and I can't find any methods that allow me to S-Off from within HBOOT or Fastboot (which is all I can get into)).
The phone is recognized via ADB when in Fastboot, but I don't know where to go from there.
Any help or suggestions would be greatly appreciated. Like I said, I did a fruitless search, but if this question has already been answered, a link would be fantastic as well. Thank you for your time!
If you boot into your HBOOT and then fastboot, You can use the revolutionary tool, to gain S-OFF from there, At the end of it, it shall even ask if you wan to install Clockworkmod, and it is 4.0.1. instead of the offical 2.5.0.7.
New features
I'm running the Revolutionary tool, and it's stuck at "Waiting for device..."
My phone is in Fastboot, connected via USB, and I've downloaded and installed the HTC Desire Fastboot drivers. It's showing all OK in device manager, but the revolutionary .exe won't see it. Am I doing something wrong?
I wouldnt say you were doing anything wrong, Just the phone seems a tad more broken than it looks
http://wiki.rootzwiki.com/index.php/HTC_Desire
I'm following those directions 100%, but it looks like the revolutionary tool won't see my device. Are you sure it can s-off while in Fastboot?
I have no idea where to go from here - I have a useless phone that won't even go into recovery. More help would be amazing.
IWAS HAVING THE SAME PROPLEM
thats wat i did
u can down load this file
update :: I cant put the link :S
google for PB99IMG.zip
Download it
if the name wasnt exact match rename it to PB99IMG.zip
and pull ur sd card put it in card reader
then copy it into sd card root folder
then put the memory back into the phone
press vol down and power
then relase
it will autumatic setup the stok RUU of ur HTC desire
that will remove the rooting and make ur phone brand new
N.P if the instalation didt sucess and said CID incorrect
then u need
gold card
make ur gold card then put the files in ur gold card put it in the phone and enter boot menu
instaltion will sucess this time
worked for me
I've been running CM7 on my phone for quite some time along with SOS and recently the latest CM7 from here. Somehow my phone appears to be bricked. Perhaps from a faulty nandroid that I restored? It goes into bootloader but I can't do much there. When I select recovery I get the 5 vibes of death and black screen. I can get to CWM with USB connected, but CWM can't mount the sdcard. And somehow I noticed I have S-ON. I originally rooted with unrevoked. Can anyone offer any advice on how to proceed?
Flash Amon Ra. CWM is just not a good recovery with the Evo, but even so, with AR, I've had my recovery get corrupted twice with the same error you're having (Both times were after the only 2 times I ran a superwipe) and had to reflash my recovery, which fixed it.
And I can do that by getting a copy of Amon Ra in the PC36IMG.zip format, like here?
ogp said:
And I can do that by getting a copy of Amon Ra in the PC36IMG.zip format, like here?
Click to expand...
Click to collapse
Yes.This is a good site to get what you need.
ogp said:
And I can do that by getting a copy of Amon Ra in the PC36IMG.zip format, like
Click to expand...
Click to collapse
not bricked
Your recovery is corrupted. Just place the PM36IMG in the root of the SD Card and as soon as you PWR+Vol- your phone will rub the update package and you will then be able to enter recovery. If you phone turns on, it's not bricked. There is always a way to fix it. Message me at any step you get to and if your phone won't go any farther I will message you back with the solution.
Ok, so I've copied that file to my sdcard and booted. hboot sees the file and it appears to load with a vertical blue indicator to the right. But I never get any prompts to install. Once the indicator completes, it goes back to the hboot menu. Will this not install because I have S-ON?
Ahh, well, yeah, I didn't know you were S-on. You have to be S-off to flash a custom recovery
Ok. I'm not sure how I got S-ON. I'm pretty sure it was off so I could flash CM7 and CWM, etc. Anyway, can I easily turn it off?
I've got hboot 2.10.0001
Radio 2.15.00.11.19
I can get it to boot into CM7 but it won't recognize the sdcard.
I can't seem to get my phone working with adb. I have adb enabled and when I connect my usb cable to my phone and laptop, the phone says debugging enabled but my laptop can't talk to it via adb. I also tried to ensure hboot drivers are installed and I still show android bootloader interface in device manager. When I boot into bootloader and select hboot usb and then connect my usb cable, it shows hboot usb plug but adb devices still shows nothing connected. So my sdcard and usb seem to not be working properly.
What can I load via hboot with S-ON? I've tried to update the radio as well as loading a rooted stock rom by loading the files on my sdcard as PC36IMG.zip. hboot sees them and loads/checks them, but I never get the option to install. I even tried stock 1.32.651.1 and it loads and checks but I still don't get the option to install.
Nothing. You need to run the RUU, either via pc36img or by the exe on your computer, re-root, and then flash recovery
Could there be something wrong with my bootloader? I tried to run this RUU and it definitely gets loaded and checked, but I never get the option to install. It just goes back to the bootloader menu. Any ideas why I don't get the option to install? Is the RUU version too old for my phone/bootloader version? I don't think I can run the .exe since I'm having a difficult time getting my phone to talk to my pc via USB.
So I was able to get it to show up in adb by booting into bootloader and selecting hboot usb and then going into recovery. When I try to run unrevoked3 I get the error Device "/sbin/sh: getprop: not found" is not supported at this time.
I think you'll need to run Revolutionary, although it's been so long since I rooted, or follwed rooting processes, I'm not sure, based on your Hboot version, but that determines which root process you'll need to use.
Sorry this is dragging on so long.
Also, jump on IRC, Freenode #htc-evo.
Those guys are great at helping people out
My phone is still rooted, it just has S-ON for some reason. I looked at Revolutionary but wasn't sure that applied since my hboot version, 2.10.0001, isn't listed in the options and I'm having trouble talking to my phone via usb/adb.
HipKat said:
I think you'll need to run Revolutionary, although it's been so long since I rooted, or follwed rooting processes, I'm not sure, based on your Hboot version, but that determines which root process you'll need to use.
Sorry this is dragging on so long.
Also, jump on IRC, Freenode #htc-evo.
Those guys are great at helping people out
Click to expand...
Click to collapse
No one on IRC seems to have an input....
ogp said:
No one on IRC seems to have an input....
Click to expand...
Click to collapse
First, you have the wrong drivers installed to run any RUU (not PC36IMG). You need Fastboot drivers, not Hboot drivers from here. (INSTALL IT TO YOUR COMPUTER).
http://www.4shared.com/get/InLGg_UI/HTCDriver300007.html
Second, you have the wrong PC36IMG file (not RUU) for your Hboot 2.10.
Either one of these files should work for you to unroot since they each have the same Hboot 2.10.
http://shipped-roms.com/download.ph...15.00.11.19_NV_1.90_release_161482_signed.exe
http://goo-inside.me/stock/superson...15.00.11.19_NV_1.90_release_161482_signed.zip
Third, you will need those Hboot USB drivers you installed in Hboot USB to run unrevoked (the reflash program) from your computer, not recovery. Make sure when you go to Hboot USB (by clicking on Hboot in the bootloader and observing "Hboot USB" highlighted in blue, not just "Hboot" highlighted) with your phone connected to your computer, that your device manager still reads "Android Bootloader Interface", or you will have to reinstall them (in "Hboot USB").
The unrevoked reflash program (not unrevoked-forever) can be found from this link.
http://downloads.unrevoked.com/recovery/3.32/reflash_package.exe
Reboot back into your phone's operating system, then run the unrevoked program, and you should be OK.
Thanks!
I was able to flash the stock .zip and get back to stock. hboot usb shows Android Bootloader Interface. I boot into stock I enable usb debugging. My computer then tries to load drivers for new hardware "Qualcomm CDMA Technologies MSM" and the screen goes black and the phone vibrate 5 times. Any ideas?
ogp said:
Thanks!
I was able to flash the stock .zip and get back to stock. hboot usb shows Android Bootloader Interface. I boot into stock I enable usb debugging. My computer then tries to load drivers for new hardware "Qualcomm CDMA Technologies MSM" and the screen goes black and the phone vibrate 5 times. Any ideas?
Click to expand...
Click to collapse
Try pulling the battery. Can you get into the bootloader, and also, can your computer still read the phone after a battery pull and trying to boot into the bootloader or trying to boot into the operating system?
ogp said:
Thanks!
I was able to flash the stock .zip and get back to stock. hboot usb shows Android Bootloader Interface. I boot into stock I enable usb debugging. My computer then tries to load drivers for new hardware "Qualcomm CDMA Technologies MSM" and the screen goes black and the phone vibrate 5 times. Any ideas?
Click to expand...
Click to collapse
Uh-oh. You might need to end up doing this:
http://forum.xda-developers.com/showthread.php?p=21765954#post21765954
Hey guys,
Here's the basic situation. I got this phone from a friend who knows nothing about flashing/rooting/etc. And yet he had flashed the phone with MUIU and ended in a bootloop. I fixed it for him. A month later my friend decided to flash it from Verizon to Frawg. Apparently a customer rep did the whole thing for him, long story short, it is stuck in a boot loop with the white HTC screen.
I figure the boot.img is corrupt. It also goes straight to a the white HTC screen loop whenever you select recovery or factory reset from HBOOT.
I have tried PB31IMG.zip flashing (multiple stock/recovery imgs/ROMS with no luck) - its S-ON btw.
I have tried fastboot adb which I am fairly knowledgable in, I know the environmental paths, and the drivers are correct, it all works with my other androids.
When flashing any ROM/recovery image/anything, I always get a failure message stating its missing signatures. This occurs when using fastboot recovery (path) commands to flash individual recovery images as well as the fastboot boot and fastboot update PB31IMG.zip commands.
I have tried to S-Off using HTCDEV method. But even when attempting the fastboot oem get_identifier_token I get a failure bootrom message <bootrom> [ERR] Command error!!!
RUU is no luck... even charged it says I have less than 30%battery error, when I get it to work after erasing cache on adb, it will say resetting bootloader, and once it has reset the phone, the phone ends up connecting via USB with a black screen as CDMA technologies to my pc. RUU then says USB has been disconnected. I can only access the USB driver while in HBOOT and FASTBOOT.
So basically the microsd flash method, adb flash method, and RUU are no goes at this point unless there's something I am doing wrong (I have been researching so many different forums, and discussions and have found a handful like my situation with no solution.
This is a last cry before I render my friends phone a paperweight. Thank you for anything! :good:
SPECS:::
INCREDIBLEC XC SHIP S-ON
HBOOT-0.92.0000
MICROP-0417
TOUCH PANEL-ATMEL224_16ab
RADIO-2.15.10.07.07
JULY 23 2010,10:06:51
ragus15 said:
Hey guys,
Here's the basic situation. I got this phone from a friend who knows nothing about flashing/rooting/etc. And yet he had flashed the phone with MUIU and ended in a bootloop. I fixed it for him. A month later my friend decided to flash it from Verizon to Frawg. Apparently a customer rep did the whole thing for him, long story short, it is stuck in a boot loop with the white HTC screen.
I figure the boot.img is corrupt. It also goes straight to a the white HTC screen loop whenever you select recovery or factory reset from HBOOT.
I have tried PB31IMG.zip flashing (multiple stock/recovery imgs/ROMS with no luck) - its S-ON btw.
I have tried fastboot adb which I am fairly knowledgable in, I know the environmental paths, and the drivers are correct, it all works with my other androids.
When flashing any ROM/recovery image/anything, I always get a failure message stating its missing signatures. This occurs when using fastboot recovery (path) commands to flash individual recovery images as well as the fastboot boot and fastboot update PB31IMG.zip commands.
I have tried to S-Off using HTCDEV method. But even when attempting the fastboot oem get_identifier_token I get a failure bootrom message [ERR] Command error!!!
RUU is no luck... even charged it says I have less than 30%battery error, when I get it to work after erasing cache on adb, it will say resetting bootloader, and once it has reset the phone, the phone ends up connecting via USB with a black screen as CDMA technologies to my pc. RUU then says USB has been disconnected. I can only access the USB driver while in HBOOT and FASTBOOT.
So basically the microsd flash method, adb flash method, and RUU are no goes at this point unless there's something I am doing wrong (I have been researching so many different forums, and discussions and have found a handful like my situation with no solution.
This is a last cry before I render my friends phone a paperweight. Thank you for anything! :good:
SPECS:::
INCREDIBLEC XC SHIP S-ON
HBOOT-0.92.0000
MICROP-0417
TOUCH PANEL-ATMEL224_16ab
RADIO-2.15.10.07.07
JULY 23 2010,10:06:51
Click to expand...
Click to collapse
Try this ruu its the newest officially signed ruu, so it will work with s-on. http://dinc.does-it.net/Stock_Images/4.08.605.15/PB31IMG.zip Place it on your sdcard in no folders and boot to hboot. It should find the file and prompt to press vol up to install. If it errors or dosent find it backup and format your sdcard fat32 with a pc and try again.
The reason the fastboot identifier dosent work is because you need to be on the 1.02 or 1.07 hboot to be able to unlock it. The ruu above will give you 1.07.
From there you can unlock the bootloader, fastboot flash recovery, and flash su thru recovery, then you will be rooted. Then if desired you can downgrade and get s-off.
I'm having a similar problem, but after using the PC-side RUU program, the PC reported the installation as failed while the phone hung on black screen with a full progress bar and 'htc', along with a single exclamation point at the end of the bar. When I unplugged the phone from the computer, it returned to the HBOOT screen where there were a number of phone elements and 'OK' in blue text, above a partition error and write failed message.
I did a battery pull to try the RUU's 'advanced recovery', and the phone now no longer boots.
I have no idea what shenanigans this is. No kernel screen, HBOOT is inaccessible, no charging light while plugged in, I've tried different SD cards and without any... I can't get it to respond at all.
Halp?
Trygon said:
I'm having a similar problem, but after using the PC-side RUU program, the PC reported the installation as failed while the phone hung on black screen with a full progress bar and 'htc', along with a single exclamation point at the end of the bar. When I unplugged the phone from the computer, it returned to the HBOOT screen where there were a number of phone elements and 'OK' in blue text, above a partition error and write failed message.
I did a battery pull to try the RUU's 'advanced recovery', and the phone now no longer boots.
I have no idea what shenanigans this is. No kernel screen, HBOOT is inaccessible, no charging light while plugged in, I've tried different SD cards and without any... I can't get it to respond at all.
Halp?
Click to expand...
Click to collapse
Sorry but it sounds like the phone is bricked, and unrecoverable. If it wont boot, or boot to hboot, there really is no way to even try anything. Does it turn on at all?
cmlusco said:
Sorry but it sounds like the phone is bricked, and unrecoverable. If it wont boot, or boot to hboot, there really is no way to even try anything. Does it turn on at all?
Click to expand...
Click to collapse
Holy cow, props on the quick reply. You're pretty much confirming my fears. I've tried a few combinations of battery and usb connections, but there's no vibration nor ADB signal.
I can't say I've ever seen a stock utility behave this way, so user beware. It's also worth noting that I have no history on this phone's modifications - Just that it was S-ON and locked when I got it, in bootloops between kernel and ROM, and attempting to access recovery looped it too.
cmlusco said:
Try this ruu its the newest officially signed ruu, so it will work with s-on. Place it on your sdcard in no folders and boot to hboot. It should find the file and prompt to press vol up to install. If it errors or dosent find it backup and format your sdcard fat32 with a pc and try again.
The reason the fastboot identifier dosent work is because you need to be on the 1.02 or 1.07 hboot to be able to unlock it. The ruu above will give you 1.07.
From there you can unlock the bootloader, fastboot flash recovery, and flash su thru recovery, then you will be rooted. Then if desired you can downgrade and get s-off.
Click to expand...
Click to collapse
Good news and bad news,
Good news: upgrade worked, and I was able to unlock the boot-loader via HTCDEV.
Bad news: I can flash recoveries all day long, boot images, etc via fast-boot and it shows the bars when flashing on my phone. But when I click recovery, I still get a white HTC splash screen. I think that the NV.img was messed up being that they flashed Frawg or Straight talk over to the network. What can I do? As far as I know there is no way for me to S-OFF, am I softbricked? Maybe there is a way to repair the kernel? IDK, any suggestions at this point would be amazing.
ragus15 said:
Good news and bad news,
Good news: upgrade worked, and I was able to unlock the boot-loader via HTCDEV.
Bad news: I can flash recoveries all day long, boot images, etc via fast-boot and it shows the bars when flashing on my phone. But when I click recovery, I still get a white HTC splash screen. I think that the NV.img was messed up being that they flashed Frawg or Straight talk over to the network. What can I do? As far as I know there is no way for me to S-OFF, am I softbricked? Maybe there is a way to repair the kernel? IDK, any suggestions at this point would be amazing.
Click to expand...
Click to collapse
The ruu should have flashed a correct nv img. Have you tried flashing amon ra recovery, or did you see if you could access the stock recovery after you did the ruu?
cmlusco said:
The ruu should have flashed a correct nv img. Have you tried flashing amon ra recovery, or did you see if you could access the stock recovery after you did the ruu?
Click to expand...
Click to collapse
I can retry the RUU to make sure it was correctly downloaded. After the 1st RUU attempt, I still had a straight to white htc screen loop when choosing the recovery. I have tried Clockwork, stock, and Amon Ra recoveries via the fastboot flash recovery recovery.img method and also the fastboot boot recovery.img methods.
ragus15 said:
I can retry the RUU to make sure it was correctly downloaded. After the 1st RUU attempt, I still had a straight to white htc screen loop when choosing the recovery. I have tried Clockwork, stock, and Amon Ra recoveries via the fastboot flash recovery recovery.img method and also the fastboot boot recovery.img methods.
Click to expand...
Click to collapse
Did you try erasing recovery before flashing?
fastboot erase recovery
Then
fastboot flash recovery recovery.img
Can you boot to the os or no?
cmlusco said:
Did you try erasing recovery before flashing?
fastboot erase recovery
Then
fastboot flash recovery recovery.img
Can you boot to the os or no?
Click to expand...
Click to collapse
I have tried fastboot erase recovery followed by the flash and still get the white HTC image. I am not able to boot the os... i get white HTC splash image over and over, and the USB driver that tries to mount to my desktop in the bootloop is not Android 1.0, it is CMDA technologies. I have no idea what that is or if that has to do with the previous frawg/straight talk flash attempts.
Hey everyone.. any help on this would be greatly appreciated, has caused a lot of stress.
The phone was successfully downgraded to hboot 2.10 from hboot 2.18 a while back, s-off was achieved, all things were working perfectly with gingerbread roms and the sort.
I decided I wanted an ICS rom as my main boot-up, but was having difficulties installing it and finding a cooperable kernal/radio to get it to flash..
(looking back this probably wasn't the real issue as to why the ROM wouldn't load, and this base ICS rom that I was drawn to was not at all the one I should have been getting conclusion/direction from)
Anyways, I see now that I was trying to flash an Evo V 4G ICS rom, and in install this rom led me to update an EVO V 4g radio.
This was the rom I was trying to install:
http://androidforums.com/evo-v-4g-a...om-harmonia-3-17-17nov12-ics-sense-3-6-a.html
And in reading up on that lead me to this link
http://androidforums.com/evo-v-4g-all-things-root/648747-update.html
where I flashed the 'OTA_Shooter_ICS_35_S_Sprint_WWE_VM_1.14.652.0-1.13.652.2_release_291083f0wrax77ry0w073p' update.
Soon thereafter I found myself back with S-ON (previously was s-off), with no roms able to install.
I can get adb/sd functionallity in fastboot/hboot and have amonRA 2.3 installed as my recovery that I can get too.
In fact, in amonRA gingerbread roms say they install correctly, and I also have a nandroid backup of 'system' 'restore' 'data' 'cache' 'boot' which I believe I performed before the radio update.
They both say installed/updated correctly (new rom flash/nandroid), but upon rebooting the system, the evo 4G just vibrates 3 times, flashes its LED, and that's it. Blank screen - nothing.
Please, any help on this?
To sum it up:
I flashed the above incompatible radio in attempt to get a rom working which on foresight was for the EVO V 4G instead of the EVO 4G.
Upon doing this my hboot stayed the same (2.10), but it reverted my from S-OFF back to S-ON.
Confusing enough my radio on the hboot menu says '2.15.00.08.08', which is the latest EVO 4G radio according to here:
http://forum.xda-developers.com/showthread.php?t=715485
Hboot 2.10 USB boots fine with vol down + power, have ADB capabilities to it, and recovery boots fine to amonRA.
Much thanks in advance, I really want to get this running again!
echoedge said:
Hey everyone.. any help on this would be greatly appreciated, has caused a lot of stress.
The phone was successfully downgraded to hboot 2.10 from hboot 2.18 a while back, s-off was achieved, all things were working perfectly with gingerbread roms and the sort.
I decided I wanted an ICS rom as my main boot-up, but was having difficulties installing it and finding a cooperable kernal/radio to get it to flash..
(looking back this probably wasn't the real issue as to why the ROM wouldn't load, and this base ICS rom that I was drawn to was not at all the one I should have been getting conclusion/direction from)
Anyways, I see now that I was trying to flash an Evo V 4G ICS rom, and in install this rom led me to update an EVO V 4g radio.
This was the rom I was trying to install:
http://androidforums.com/evo-v-4g-a...om-harmonia-3-17-17nov12-ics-sense-3-6-a.html
And in reading up on that lead me to this link
http://androidforums.com/evo-v-4g-all-things-root/648747-update.html
where I flashed the 'OTA_Shooter_ICS_35_S_Sprint_WWE_VM_1.14.652.0-1.13.652.2_release_291083f0wrax77ry0w073p' update.
Soon thereafter I found myself back with S-ON (previously was s-off), with no roms able to install.
I can get adb/sd functionallity in fastboot/hboot and have amonRA 2.3 installed as my recovery that I can get too.
In fact, in amonRA gingerbread roms say they install correctly, and I also have a nandroid backup of 'system' 'restore' 'data' 'cache' 'boot' which I believe I performed before the radio update.
They both say installed/updated correctly (new rom flash/nandroid), but upon rebooting the system, the evo 4G just vibrates 3 times, flashes its LED, and that's it. Blank screen - nothing.
Please, any help on this?
To sum it up:
I flashed the above incompatible radio in attempt to get a rom working which on foresight was for the EVO V 4G instead of the EVO 4G.
Upon doing this my hboot stayed the same (2.10), but it reverted my from S-OFF back to S-ON.
Confusing enough my radio on the hboot menu says '2.15.00.08.08', which is the latest EVO 4G radio according to here:
http://forum.xda-developers.com/showthread.php?t=715485
Hboot 2.10 USB boots fine with vol down + power, have ADB capabilities to it, and recovery boots fine to amonRA.
Much thanks in advance, I really want to get this running again!
Click to expand...
Click to collapse
You're going to need to upgrade your device to the latest available RUU version (4.67.651.3), unlock your bootloader with HTCDev, flash a custom recovery, root your device, and then downgrade your misc partition (again). That should normalize your device (if one of the earlier steps doesn't do it).
echoedge said:
Hey everyone.. any help on this would be greatly appreciated, has caused a lot of stress.
The phone was successfully downgraded to hboot 2.10 from hboot 2.18 a while back, s-off was achieved, all things were working perfectly with gingerbread roms and the sort.
I decided I wanted an ICS rom as my main boot-up, but was having difficulties installing it and finding a cooperable kernal/radio to get it to flash..
(looking back this probably wasn't the real issue as to why the ROM wouldn't load, and this base ICS rom that I was drawn to was not at all the one I should have been getting conclusion/direction from)
Anyways, I see now that I was trying to flash an Evo V 4G ICS rom, and in install this rom led me to update an EVO V 4g radio.
This was the rom I was trying to install:
http://androidforums.com/evo-v-4g-a...om-harmonia-3-17-17nov12-ics-sense-3-6-a.html
And in reading up on that lead me to this link
http://androidforums.com/evo-v-4g-all-things-root/648747-update.html
where I flashed the 'OTA_Shooter_ICS_35_S_Sprint_WWE_VM_1.14.652.0-1.13.652.2_release_291083f0wrax77ry0w073p' update.
Soon thereafter I found myself back with S-ON (previously was s-off), with no roms able to install.
I can get adb/sd functionallity in fastboot/hboot and have amonRA 2.3 installed as my recovery that I can get too.
In fact, in amonRA gingerbread roms say they install correctly, and I also have a nandroid backup of 'system' 'restore' 'data' 'cache' 'boot' which I believe I performed before the radio update.
They both say installed/updated correctly (new rom flash/nandroid), but upon rebooting the system, the evo 4G just vibrates 3 times, flashes its LED, and that's it. Blank screen - nothing.
Please, any help on this?
To sum it up:
I flashed the above incompatible radio in attempt to get a rom working which on foresight was for the EVO V 4G instead of the EVO 4G.
Upon doing this my hboot stayed the same (2.10), but it reverted my from S-OFF back to S-ON.
Confusing enough my radio on the hboot menu says '2.15.00.08.08', which is the latest EVO 4G radio according to here:
http://forum.xda-developers.com/showthread.php?t=715485
Hboot 2.10 USB boots fine with vol down + power, have ADB capabilities to it, and recovery boots fine to amonRA.
Much thanks in advance, I really want to get this running again!
Click to expand...
Click to collapse
have you tried running a RUU yet? it should restore your phone back to stock radio hboot system and a few other things
Okay, I will try to get the latest RUU up and running.
I see them listed here
http://wiki.rootzwiki.com/HTC_EVO_4G_Downloads
but all the links are dead -- will look for a mirror right now.
I see there are three different methods for flashing the RUU - an update.zip I can flash in amonRA, a PC36IMG I can flash in hboot and an radio.img file I can do in fastboot adb..
I also find a .exe file
RUU_SuperSonic_GB_Sprint_WWE_4.67.651.3_Radio_2.15.00.12.19_NV_2.33_release_234563_signed.exe
but it's an .exe file?
and they all seem to differentiate in size from a like 10mg PC36IMG to a 220mb version as the .exe is..
so many different choices, what's my best option for the situation
Thanks a bunch for the quick replies!
echoedge said:
Okay, I will try to get the latest RUU up and running.
I see them listed here
http://wiki.rootzwiki.com/HTC_EVO_4G_Downloads
but all the links are dead -- will look for a mirror right now.
I see there are three different methods for flashing the RUU - an update.zip I can flash in amonRA, a PC36IMG I can flash in hboot and an radio.img file I can do in fastboot adb..
I also find a .exe file
RUU_SuperSonic_GB_Sprint_WWE_4.67.651.3_Radio_2.15.00.12.19_NV_2.33_release_234563_signed.exe
but it's an .exe file?
and they all seem to differentiate in size from a like 10mg PC36IMG to a 220mb version as the .exe is..
so many different choices, what's my best option for the situation
Thanks a bunch for the quick replies!
Click to expand...
Click to collapse
The RUU is run from the PC while you're in fastboot mode. That'll work fine. Or you can use the PC36IMG from here and flash in HBOOT (bootloader).
Cool, thanks.
Okay, I downloaded the .zip and .exe-- ended up using Captain's link to HBoot the RUU by renaming it to PC36IMG.zip
So then booted up in hboot, it detected the PC36IMG -- went through the list.. check, check, check, check, completed and done.
Rebooted the phone, now instead of just a black screen with the 3 vibrations and led flashes, it goes to the "EVO 4G" white screen loader, then 5-10 seconds later, goes blank and does the 3 vibration thing again.
Back to HBoot.
Noticed the only change was the radio oversion now says 2.15.00.11.19 now
So now my next step is to do the HTCDev method I assume?
Fastboot USB'd- phone detected by W7 just fine.
I type in 'fastboot devices' and it detects the phone and gives the serial number, so fastboot seems to be in working order.
I then type in the command 'fastboot oem get_identifier_token'
and am getting the error
C:\Android>fastboot oem get_identifier_token
... INFO[ERR] Command error !!!
OKAY [ 0.008s]
finished. total time: 0.008s
Click to expand...
Click to collapse
and seem to be stuck here.. tried re-installing my htc sync, redid the get_identifier_token command and the same error persists.
Any suggestions?
echoedge said:
Cool, thanks.
Okay, I downloaded the .zip and .exe-- ended up using Captain's link to HBoot the RUU by renaming it to PC36IMG.zip
So then booted up in hboot, it detected the PC36IMG -- went through the list.. check, check, check, check, completed and done.
Rebooted the phone, now instead of just a black screen with the 3 vibrations and led flashes, it goes to the "EVO 4G" white screen loader, then 5-10 seconds later, goes blank and does the 3 vibration thing again.
Back to HBoot.
Noticed the only change was the radio oversion now says 2.15.00.11.19 now
So now my next step is to do the HTCDev method I assume?
Fastboot USB'd- phone detected by W7 just fine.
I type in 'fastboot devices' and it detects the phone and gives the serial number, so fastboot seems to be in working order.
I then type in the command 'fastboot oem get_identifier_token'
and am getting the error
and seem to be stuck here.. tried re-installing my htc sync, redid the get_identifier_token command and the same error persists.
Any suggestions?
Click to expand...
Click to collapse
What does your bootloader screen say? S-ON or S-OFF? What are your HBOOT and radio versions? Because it doesn't sound like the zip file finished installing. It should reboot once during the process, and then continue on flashing for around 10 minutes. Did it do that?
Captain_Throwback said:
What does your bootloader screen say? S-ON or S-OFF? What are your HBOOT and radio versions? Because it doesn't sound like the zip file finished installing. It should reboot once during the process, and then continue on flashing for around 10 minutes. Did it do that?
Click to expand...
Click to collapse
Yes, it did that.. went through all the checkmarks with success down to WiMax I believe was the last one.
It did reset once during the process.. I remember because I was confused, didn't know if it turned off or what, then it turned itself back on, continued with the process and installed the rest of it.
The only thing that changed was the radio version from 2.15.00.08.08 to 2.15.00.11.19 after the RUU/Hboot/PCIMG36 img flash.
Bootloader says... I'll type it all out
SUPERSONIC EVT2-3 SHIP S-ON
HBOOT-2.10.0001
MICROP-041f
TOUCH PANEL-ATMEL224_16ab
RADIO-2.15.00.11.19
Oct 15 2010, 12:07:00
Click to expand...
Click to collapse
Should I try re-flashing again using the .exe file, does everything seem right on the bootloader?
Okay, I think I might have put the wrong PC36IMG file directing towards 11.19
(too many files in my Downloads folder )
Lemme try again.. I see the radio version should be 12.19, which is what Captain's link provided
Okay, I used the proper 12.19 PCIMG36 file this time,
now the bootloader says
*** LOCKED (OOW) ***
SUPERSONIC EVT2-3 SHIP S-ON
HBOOT-2.18.0001
MICROP-041f
TOUCH PANEL-ATMEL224_16ab
RADIO-2.15.00.12.19
Dec 21, 2011, 12:50:32
Click to expand...
Click to collapse
Looks like it's back to its original state
I'm assuming it works now, still updating as I type this, will try the token and the other steps to get it back down to 2.10 with s-off and back to where it should be
Thanks for the help guys.
I'll let you know if it works, I'm assuming it will and I know the steps to perform at this stage.
One more question though which got me into this original mess,
do I need to update the kernal/radio/anything in order to get an ICS rom loaded on the Evo 4G?
Or was that issue mute just because I was trying to flash an Evo V 4g/incompatible rom?
Thanks again!!
Okay.. all is going well, but there seems to be something strange going on, don't think it's normal.
After I flashed superuser, I restarted it and it once again went to the black screen with the 3 vibrations.
Took out the battery, put it back in, powered on. Booted to sprint stock.
Enabled USB debugging/disabled Fast Boot.
Then put the USB in, and the notification sound popped up on my computer detecting the phone.. but the phone itself did nothing. It isn't even charging (battery indicator at top stays still).. my settings are set to 'charge only' and 'pop-up and ask me' on connection settings.
Pressed power button, went to restart, and it powered down and again went to black screen with the three vibrations.
Took the battery out, put it back in, turned it on.. went back to sprint stock.
Plugged USB cable in again-- same thing, no pop-up on phone that it's connected, although my computer notifies me that it is.
Tried on two different computers with different USB cables, no luck.
ADB shell doesn't work, no devices found if I try it anyways.
Help
Thanks
echoedge said:
Okay.. all is going well, but there seems to be something strange going on, don't think it's normal.
After I flashed superuser, I restarted it and it once again went to the black screen with the 3 vibrations.
Took out the battery, put it back in, powered on. Booted to sprint stock.
Enabled USB debugging/disabled Fast Boot.
Then put the USB in, and the notification sound popped up on my computer detecting the phone.. but the phone itself did nothing. It isn't even charging (battery indicator at top stays still).. my settings are set to 'charge only' and 'pop-up and ask me' on connection settings.
Pressed power button, went to restart, and it powered down and again went to black screen with the three vibrations.
Took the battery out, put it back in, turned it on.. went back to sprint stock.
Plugged USB cable in again-- same thing, no pop-up on phone that it's connected, although my computer notifies me that it is.
Tried on two different computers with different USB cables, no luck.
ADB shell doesn't work, no devices found if I try it anyways.
Help
Thanks
Click to expand...
Click to collapse
Just as I suspected. Your misc partition is corrupted, causing your sd card to not be recognized, and ADB to be broken. I've been there before, and this is fixable. First, to get your SD card working, you'll need to boot into fastboot (so that your display reads FASTBOOT USB), and from the command prompt on your computer, from the folder where your fastboot.exe resides, type the following command (taken from here - thanks to Calkulin):
Code:
fastboot oem enableqxdm 0
After that completes, boot into recovery. I'd like to check and see if adb will work in recovery - that'll be easier than the alternative, which is flashing a ROM with Wireless ADB enabled, and using those commands to flash the misc partition from the computer. After you get recovery booted, type
Code:
adb devices
at the command prompt and let us know if your device shows up in recovery mode.
Tried going back into hboot.. plugged it in,
was detected, but had to re-install drivers on my w7 machine I noticed.
after i figured out that hboot usb worked, went to recovery, went to restart now.
went to black screen and noticed it is vibrating 5 times now (before it was 3)
took out battery, turned back on, back to sprint stock. still no usb capabilities within the rom.
btw my bootloader now says
** unlocked **
s-on
hboot-2.18.0001
radio-2.15.00.12.19
also,
tried going back into recovery, and re-flashed the superuser file. installed fine.
this time instead of going to 'reboot now' went to shut down.. it shut down fine. I turned it back on, turned on fine.
It only seems to be doing the black-screen and 5 vibrations when I reboot.
Tried plugging it in again to pc, checked settings - nothing.
Am confused now, not sure what's wrong
EDIT:
okay, just read Capt. Throwback's reply AFTER posting this, will give that ago. Thanks CT
Captain_Throwback said:
Just as I suspected. Your misc partition is corrupted, causing your sd card to not be recognized, and ADB to be broken. I've been there before, and this is fixable. First, to get your SD card working, you'll need to boot into fastboot (so that your display reads FASTBOOT USB), and from the command prompt on your computer, from the folder where your fastboot.exe resides, type the following command (taken from here - thanks to Calkulin):
Code:
fastboot oem enableqxdm 0
After that completes, boot into recovery. I'd like to check and see if adb will work in recovery - that'll be easier than the alternative, which is flashing a ROM with Wireless ADB enabled, and using those commands to flash the misc partition from the computer. After you get recovery booted, type
Code:
adb devices
at the command prompt and let us know if your device shows up in recovery mode.
Click to expand...
Click to collapse
I remember having to do that command because my SD card wasn't detected before I flashed the RUU and making this thread.
This is because it was very noticable my SD card wasn't being detected.. any PC36IMG file in hboot wouldn't be detected, and recovery wouldn't mount nor find an sd card. After doing that command above the SD card worked.
But anyways, ADB worked in hboot and I successfully did that command.
ADB did not work in recovery unfortunately.
Are you sure it's an issue of my sd card being detected? My misc partition is probably corrupted I assume which is giving me these errors, but SD card even before doing that above command in hboot and recovery worked fine (was able to browse my sd card/mount it.. flashed superuser on it. I only say that because before when I had to do that command to get the SD working in the beginning of all this the SD card had no access to anything at all, and in recovery would give me a can't mount mnt/mmc*** (or something like that).., that's when I googled the error and found that solution that Calkulin provided.
But i'm not sure.. what are my options now?
echoedge said:
I remember having to do that command because my SD card wasn't detected before I flashed the RUU and making this thread.
This is because it was very noticable my SD card wasn't being detected.. any PC36IMG file in hboot wouldn't be detected, and recovery wouldn't mount nor find an sd card. After doing that command above the SD card worked.
But anyways, ADB worked in hboot and I successfully did that command.
ADB did not work in recovery unfortunately.
Are you sure it's an issue of my sd card being detected? My misc partition is probably corrupted I assume which is giving me these errors, but SD card even before doing that above command in hboot and recovery worked fine (was able to browse my sd card/mount it.. flashed superuser on it. I only say that because before when I had to do that command to get the SD working in the beginning of all this the SD card had no access to anything at all, and in recovery would give me a can't mount mnt/mmc*** (or something like that).., that's when I googled the error and found that solution that Calkulin provided.
But i'm not sure.. what are my options now?
Click to expand...
Click to collapse
You're going to need to flash a ROM with Wireless ADB enabled, or manually use Terminal Emulator to flash the misc partition, as per the instructions in my "Downgrade HBOOT" thread. If you still have the flash_image and mtd-eng.img on your SD card, Terminal might be the easiest way to do it (hopefully it'll let you). If not, we'll have to go the Wireless ADB route, as I did here.
Okay, i'm not sure if it worked or not.
I su'd into terminal and did the commands.
the terminal froze though so I had to take the battery out, but that was after I pressed enter on the three commands..
I noticed in my bootloader it says *** LOCKED ***
and it also says I'm S-OFF..
Now I'm trying to flash over the 11.19 radio PC36IMG.zip but now it seems the bootloader is not detecting my sd card..
I tried the command to get sd working again. That worked okay.
I booted into recovery, and my sd card is mounted and in there I can browse my SD card contents.
But in hboot it tries to detect the PC36IMG.zip and just passes it by.
Did the misc partition commands work properly, what's messing with it now?
I'm still able to ADB/fastboot USB in hboot by the way, it just isn't detecting my PC36IMG file.
Should I try to manually do it, or am I missing something?
Also I booted into the sprint stock rom, plugged in the USB and now that functionality is working fine.. prompts up, charge only, etc.
Seems I'm almost there... :fingers-crossed:
echoedge said:
Okay, i'm not sure if it worked or not.
I su'd into terminal and did the commands.
the terminal froze though so I had to take the battery out, but that was after I pressed enter on the three commands..
I noticed in my bootloader it says *** LOCKED ***
and it also says I'm S-OFF..
Now I'm trying to flash over the 11.19 radio PC36IMG.zip but now it seems the bootloader is not detecting my sd card..
I tried the command to get sd working again. That worked okay.
I booted into recovery, and my sd card is mounted and in there I can browse my SD card contents.
But in hboot it tries to detect the PC36IMG.zip and just passes it by.
Did the misc partition commands work properly, what's messing with it now?
I'm still able to ADB/fastboot USB in hboot by the way, it just isn't detecting my PC36IMG file.
Should I try to manually do it, or am I missing something?
Click to expand...
Click to collapse
If you're back to S-OFF, you might be okay. Try flashing the 4.67 PC36IMG.zip in HBOOT again. After you do that, you should still be S-OFF, if everything is working properly, and hopefully everything else will be working too.
It's also possible that the misc partition flash was incomplete. Since you're now S-OFF, and presumably ADB is working, you should be able to run the commands over USB.
Okay, I had to put in a bigger SD card for it to detect the PC36IMG to detect- installed perfectly.
Also had to reflash amonRA recovery.
I was already S-OFF for whatever reason so yup, after that I was good to go! :good:
Booted to recovery, made a backup, wiped data/factory reset, an flashed an ICS rom. Just booted up, everything is working great
Thanks a bunch everyone (esp Capt. Throwback) for getting this resolved quick and painlessly
Am very relieved to get this working once again as normal, wasn't sure if I would be able
Thanks again!!