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.
Hi,
my htc desire is bricked... impossible to boot etc..
when i put battery and i push on power button, in 4 corners exclamation in triangles appear. (image in attachment)
my phone is S-OFF, android 2.1
i tried upgrade with sd card.. and with android sdk tools..but is not working.
Please HELP !!!
thnx.
screen image
please give full details of your phone. What hboot? custom? what RUU?
What did you do before it broke? in what order? then what happened?
i can't see any detail.. I have access only to the fast boot.
never custom firmware.. never s-on
during the upgrade i disconnect the phone.. and i tried really all things.. installing RUU from sdcard , upload RUU with sdk tool etc. etc..
before trying updates the SDK tools i had access to the boot menu (with power + volume down combinations) but now i can not even have that.. only screen with 4 exclamation icon.. and fastboot access with sdk-tools (android 1.0 phone drivers)
since 4 days i try everything... but no result.
this htc really make me sick.
please help me.
thank you advance
Alright then, how did you s-off? What RUU did you use?
You just rooted and kept the same software?
If you disconnected during upgrade you may have bricked it and only HTC can resolve.
When you RUU what failure message do you get?
Sent from my HTC Desire using xda premium
I am sure if you can get into Hboot / Fastboot all is not lost, just use adb commands to restore functionality to your phone, like reflashing recovery and stuff.
BRAVO PVT1 SHIP S-ON
HBOOT-1.02.0001
MICROP-031d
TOUCH PANEL-SYNW0101
RADIO-5.11.05.27
RUU
my boot screen when i connect and disconnect usb cable.
C:\Android>adb devices
List of devices attached
C:\Android>fastboot devices
HT05MPL05537 fastboot
fastboot working well... but adb not detect my phone
C:\Android>fastboot flash zip C:\Users\Didan\Downloads\ota1.zip
sending 'zip' (90221 KB)... OKAY [ 13.479s]
writing 'zip'... INFOsignature checking...
FAILED (remote: 12 signature verify fail)
finished. total time: 29.226s
i tried with all possible shipped-roms.com roms...
aghhh!!! htccc come backkk pleasee
When you install a RUU, it should say what has failed. Need to know that
Sent from my HTC Desire using xda premium
now i have a gold card (two different.. 2gb and 4gb mmc)
but impossible to install any RUU... signature verify fail , radio update error or partition update errors..
i try with "fastboot.exe flash zip rom.zip" etc.. etc....
or installing HBOOT bravo_alphaspl-1.img.. signature verify fail.
tried with gingerbread
[1] RADIO_VZ - Fail-PU
2 SPLASH 1 - OK
3 RECOVERY - OK
4 SPLASH2 OK
5 RADIO_CUST OK
6 BOOTLOADER OK
7 USERDATA OK
8 SYSTEM OK
9 BOOT OK
Partition update fail!
Update Fail!
Looks like a radio brick. You never did tell me what RUU you are using.
You cant use fastboot if you are S-ON
I had that to, and i get it running again.
In my case i had flashed the cm7r2 from alpharev before, so i had to use the downgrader first, to install my stock RUU.
After downgrading i startet the RUU.exe from windows, in the first try it stoped with an error.
If this happens you have to do all steps exactly ass the RUU installer says.
In the first try i didnt do that just klicked the steps away and didnt even read what RUU recomends.
But in the second try i did all these steps and i get my phone up running again.
And its important to use the right RUU for your phone otherwise you will get an signature fail
Edit: If your not s-off and you have isues getting into recovery, try to flash revolutionary, will gain you s-off and clockworkmod recovery
http://revolutionary.io/ just follow the steps below
nullinger said:
I had that to, and i get it running again.
In my case i had flashed the cm7r2 from alpharev before, so i had to use the downgrader first, to install my stock RUU.
After downgrading i startet the RUU.exe from windows, in the first try it stoped with an error.
If this happens you have to do all steps exactly ass the RUU installer says.
In the first try i didnt do that just klicked the steps away and didnt even read what RUU recomends.
But in the second try i did all these steps and i get my phone up running again.
And its important to use the right RUU for your phone otherwise you will get an signature fail
Edit: If your not s-off and you have isues getting into recovery, try to flash revolutionary, will gain you s-off and clockworkmod recovery
http://revolutionary.io/ just follow the steps below
Click to expand...
Click to collapse
Is not s-off and the phone wont boot so none of this will work.
He said
386dx said:
fastboot working well... but adb not detect my phone
Click to expand...
Click to collapse
If fastboot works then he should be able to flash an recovery via cmd in windows
and then he could use revolutionary to or am i wrong ?
EDIT: Have you ever installed a different HBoot from alpharev before ??
nullinger said:
He said
If fastboot works then he should be able to flash an recovery via cmd in windows
and then he could use revolutionary to or am i wrong ?
EDIT: Have you ever installed a different HBoot from alpharev before ??
Click to expand...
Click to collapse
You need an S-off alpharev SPL to enable fastboot flash command support. He is S-ON so he cannot fastboot flash anything.
Sorry but i think you are wrong this should work
http://forum.xda-developers.com/showpost.php?p=16761324&postcount=2
nullinger said:
Sorry but i think you are wrong this should work
http://forum.xda-developers.com/showpost.php?p=16761324&postcount=2
Click to expand...
Click to collapse
no.
10char
Ok, You're right, and I have peace and quiet.
Or hey, why won´t we let him try if it works instead of saying NO
I have an Incredible that has Cyanogenmod 7 on it. A couple weeks ago it stopped working in that it would just reboot after the white HTC incredible screen. I can get it to go to Hboot, but if I try to go into Recovery it just reboots immediately.
I flashed a new Hboot successfully, but once it reboots I get stuck in the loop again.
Both Clear Storage and Factory Reset start the boot loop as well.
Anyone have an idea of what I can do or does this sound like a hardware issue? My computer recognizes it, but I'm not sure what good that does me since I can't get it to boot or go into Recovery.
Here's the info from Hboot in case it's helps
Code:
INCREDIBLEC XC SHIP S-OFF
HBOOT-0.92.0000
MICROP-0417
TOUCH PANEL-ATMEL24_16ab
RADIO-2.15.00.07.28
Jul 23 2010, 18:06:51
GreyhoundX said:
I have an Incredible that has Cyanogenmod 7 on it. A couple weeks ago it stopped working in that it would just reboot after the white HTC incredible screen. I can get it to go to Hboot, but if I try to go into Recovery it just reboots immediately.
I flashed a new Hboot successfully, but once it reboots I get stuck in the loop again.
Both Clear Storage and Factory Reset start the boot loop as well.
Anyone have an idea of what I can do or does this sound like a hardware issue? My computer recognizes it, but I'm not sure what good that does me since I can't get it to boot or go into Recovery.
Here's the info from Hboot in case it's helps
Code:
INCREDIBLEC XC SHIP S-OFF
HBOOT-0.92.0000
MICROP-0417
TOUCH PANEL-ATMEL24_16ab
RADIO-2.15.00.07.28
Jul 23 2010, 18:06:51
Click to expand...
Click to collapse
I would flash an ruu thru hboot and then do a factory rest from hboot. Then if it boots fine flash cwm recovery thru hboot and then the su binaty thru recovery to regain root. Once you have recovery working again then flash back to cm7 or another rom of your choice thru recovery.
Or you could try to just reflash cwm recovery thru hboot, and then if you can access recovery wipe everything in mounts and storage except sdcard and emmc, and then restore a nandroid or flash a new rom.
RUU's - http://pvillecomp.com/?page_id=22
Latest cwm recovery - http://dinc.does-it.net/Recoveries/CWM_5.0.2.0/PB31IMG.zip
Latest su binary - http://dinc.does-it.net/SuperUser/SuperUser_3.0.7.zip
How to flash with hboot - http://pvillecomp.com/?page_id=79
You may also want to upgrade to the newest radio 2.15.10.07.07 - http://pvillecomp.com/?page_id=18
I flashed the PB31IMG from here (wasn't the newest): http://pvillecomp.com/?page_id=22
The flash seemed to work, but once it rebooted it went into the loop again. All the options in Hboot just throw it into the same white-screen loop, including Factory Reset and Recovery.
The only thing I see different in Hboot is my radio is now 2.15.10.07.07
GreyhoundX said:
I flashed the PB31IMG from here (wasn't the newest): http://pvillecomp.com/?page_id=22
The flash seemed to work, but once it rebooted it went into the loop again. All the options in Hboot just throw it into the same white-screen loop, including Factory Reset and Recovery.
The only thing I see different in Hboot is my radio is now 2.15.10.07.07
Click to expand...
Click to collapse
Try flashing the recovery and then see if you can access it.
If you have adb setup and have fastboot, you can try to erase the recovery partition by typing " fastboot erase recovery " without quotes into a cmd prompt on your pc. And then flash the recovery from above. Sounds like something is either messed up with your boot or recovery partition or img.
You can also try to use fastboot to erase the boot partition " fastboot erase boot " and then try an ruu again.
I tried both Clockwork 5 and Stock HTC from here: http://pvillecomp.com/?page_id=28
They both boot-looped after flashing.
When I try to go into Recovery now, I get the white screen then a quick flash of a phone image with a red triangle on top.
GreyhoundX said:
I tried both Clockwork 5 and Stock HTC from here: http://pvillecomp.com/?page_id=28
They both boot-looped after flashing.
When I try to go into Recovery now, I get the white screen then a quick flash of a phone image with a red triangle on top.
Click to expand...
Click to collapse
That red triangle is the stock recovery, try to do a factory reset now or try the sugestions i added to the post above.
Factory reset doesn't work. It shows me a phone with a green circle then goes into the boot loop.
I'll try the ADB stuff later today when I'm back from work. I've never used it before. Thanks so much for helping.
How do I connect to the phone via ADB when it's in Hboot? I just get "error: device not found" Every tutorial I found requires the phone to be booted to use ADB.
GreyhoundX said:
How do I connect to the phone via ADB when it's in Hboot? I just get "error: device not found" Every tutorial I found requires the phone to be booted to use ADB.
Click to expand...
Click to collapse
Adb will not work in hboot but fastboot will. You can use adb in recovery though, not just booted to the os. The error device not found is probably because you were trying adb from hboot, or because you dont have the correct drivers on your pc. Adb and fastboot are 2 different programs, fastboot is not an adb command. If you need the fastboot.exe file or the drivers you can get them here. http://dinc.does-it.net/ADB/ADB-Fastboot-USB-Drivers_v4_(x86)(x64).zip
I ran "fastboot erase boot" and it said "erasing 'boot'...FAILED (remote: not allowed)". Can I try running or flashing something else?
If I run "fastboot devices" it shows my device ID with fastboot next to it so I know it's connecting.
Thanks for putting up with this, can't imagine what caused this.
Hmm not sure, seems it may be some sort of hardware issue or disk failure. If you cant get it to boot after an ruu, and you cant factory reset or access a custom recovery or get fastboot to erase or flash, im not sure what else you could do. My only other sugestion would be to try the ruu.exe that you do from your pc with the phone connected. Flash the stock recovery PB31IMG.zip first before doing so as i believe its required for the ruu.exe. It may work and it may not im not exactly sure how the ruu.exe works as i have never used one, but i believe you just boot into hboot and then run the exe on your pc.
I haven't flashed through Fastboot because I don't know how. I tried flashing a few of the stock images, but I get errors everytime like "whoops: didn't find expected signature" or "archive does not contain android-info.txt".
Is there something I'm doing wrong?
GreyhoundX said:
I haven't flashed through Fastboot because I don't know how. I tried flashing a few of the stock images, but I get errors everytime like "whoops: didn't find expected signature" or "archive does not contain android-info.txt".
Is there something I'm doing wrong?
Click to expand...
Click to collapse
Take a PB31IMG.zip ruu ( http://pvillecomp.com/?page_id=22 ) and rename it update.zip
Put the update.zip file on your pc in the same folder as the fastboot.exe file. (Where adb is installed)
Boot into hboot with the phone pluged in to the pc. Make sure it says fastboot in red at the top of the hboot screen.
Open a cmd prompt to the directory where fastboot.exe is (eg C:\ADB\)
Type without quotes " fastboot update update.zip " and hit enter.
Here is some good info on fastboot.
http://wiki.cyanogenmod.com/wiki/Fastboot
Should I be able to open the zip on my computer? All the ones I download from that site are invalid according to Windows. This is the one I tried (3rd link on that page): http://pvillecomp.com/wp/wp-content/uploads/Images/Gingerbread-Stock_PB31IMG.zip
I did exactly what you said and got a similar result to before.
Code:
C:\adb>fastboot update update.zip
Whoops: didn't find expected signature
read_central_directory_entry failed
error: failed to access zipdata in 'ö╓°ÑAa.òo♥Gûl╔←☺☼‼6«T▀ésαu*z¿♥M╦▌‼A←4,<Lσ╡≥↕ ªº─ ΦSÉ╢t↕←Θ■√╣F'
GreyhoundX said:
Should I be able to open the zip on my computer? All the ones I download from that site are invalid according to Windows. This is the one I tried (3rd link on that page): http://pvillecomp.com/wp/wp-content/uploads/Images/Gingerbread-Stock_PB31IMG.zip
I did exactly what you said and got a similar result to before.
Code:
C:\adb>fastboot update update.zip
Whoops: didn't find expected signature
read_central_directory_entry failed
error: failed to access zipdata in 'ö╓°ÑAa.òo♥Gûl╔←☺☼‼6«T▀ésαu*z¿♥M╦▌‼A←4,<Lσ╡≥↕ ªº─ ΦSÉ╢t↕←Θ■√╣F'
Click to expand...
Click to collapse
Use 7-zip, winzip and winrar dont work the best for android files.
Think I'm just going to give up on this one since the flashing doesn't work...what a hassle. I wish there was some diagnostics tool that would just tell me if the phone is physically broken.
My problem: (I'm a total noob)
1. used Unrevoked 3.21 to ROOT - finished
2. used Revolutionary to S-OFF - finished
However, desire went into bootloop. Finally loaded, worked fine. After restart - same bootloop.
3. Decided I would just restore everything by flashing stock RUU as in video (noob proof guide)
used 2.29.405.14 32.49.00.32U_5.11.05.27 (same as mine)
Finished installation, but on boot desire gets stuck on white HTC screen.
Details:
Revolutionary
Bravo pvt1 S-OFF
Hboot 6.93.1002
Tried the following methods described in bortak's troubleshooting guide:
[1] didn't work - press "Recovery" --> white HTC screen
[2] Method 1 - Android flasher freezes after: "booting, OKAY, finished." --> white HTC screen. Recovery --> white HTC screen.
[2] Method 2 - "fastboot oem gencheckpt"- phone goes to white HTC screen - cmd freezes after "Info hboot time"
Disconnect phone -> "failed (status read failed (too many links)) finished. total time". Recovery --> white HTC screen.
Could you help me, please?
Should I just try to rerun the same RUU on fastboot? Or flash the same ROM with PB99IMG.zip method? Any other actions necessary or any other suggestions?
VytasLTU said:
My problem: (I'm a total noob)
1. used Unrevoked 3.21 to ROOT - finished
2. used Revolutionary to S-OFF - finished
However, desire went into bootloop. Finally loaded, worked fine. After restart - same bootloop.
3. Decided I would just restore everything by flashing stock RUU as in video (noob proof guide)
used 2.29.405.14 32.49.00.32U_5.11.05.27 (same as mine)
Finished installation, but on boot desire gets stuck on white HTC screen.
Details:
Revolutionary
Bravo pvt1 S-OFF
Hboot 6.93.1002
Tried the following methods described in bortak's troubleshooting guide:
[1] didn't work - press "Recovery" --> white HTC screen
[2] Method 1 - Android flasher freezes after: "booting, OKAY, finished." --> white HTC screen. Recovery --> white HTC screen.
[2] Method 2 - "fastboot oem gencheckpt"- phone goes to white HTC screen - cmd freezes after "Info hboot time"
Disconnect phone -> "failed (status read failed (too many links)) finished. total time". Recovery --> white HTC screen.
Could you help me, please?
Should I just try to rerun the same RUU on fastboot? Or flash the same ROM with PB99IMG.zip method? Any other actions necessary or any other suggestions?
Click to expand...
Click to collapse
Code:
I know I just replied differently on my guide, but try this first.
Get cmd out and type some things! You'll need fastboot for this, you can find a zip file which contains all you need on my guide, attached in one of my posts called fastboot.zip. unzip it into c:\
Download a recovery image (.img file), rename it to recovery.img and place it into c:\ boot your phone into fastboot mode (when it's off, hold back and power), and plug it in via USB.
[code]fastboot flash recovery recovery.img
fastboot oem gencheckpt
This should flash and boot your new recovery. If it doesn't work then grab the 2.3 RUU from resources on my guide. You don't need a goldcard, or anything. Just the RUU, boot into fastboot, plug in via usb and run RUU.exe
[PROBLEM SOLVED]
Thanks, bortak. The first method didn't work.
Installed 2.3 RUU - finished installation:
windows - "this program might not have installed correctly"
desire - bootloop.
Removed sd card, booted - everything's fine, inserted sd card - everything's fine. Tried rebooting - fine.
The device seems to be running fine.
[PROBLEM SOLVED]
At last I'm able to enjoy my desire
bortak, thank you very very much for you support )
same problem
dear bortak, same problem as above am having.
after s-off i can see only HTC logo when its on, even if i wana open recovery mod still the same,
i tried your link http://forum.xda-developers.com/showthread.php?t=1275632 [2] method.
in this the problem is CMD is failed to sent file to phone, Its says <Failed : Remote not Allowed >
BRAVO PVT4 SHIP S-OFF
HBOOT-0.93.0001
MICROP-051d
TOUCH PANEL-SYNT0101
RADIO-5.11.05.27
Please help me :crying:
rizadrkm said:
dear bortak, same problem as above am having.
after s-off i can see only HTC logo when its on, even if i wana open recovery mod still the same,
i tried your link http://forum.xda-developers.com/showthread.php?t=1275632 [2] method.
in this the problem is CMD is failed to sent file to phone, Its says <Failed : Remote not Allowed >
BRAVO PVT4 SHIP S-OFF
HBOOT-0.93.0001
MICROP-051d
TOUCH PANEL-SYNT0101
RADIO-5.11.05.27
Please help me :crying:
Click to expand...
Click to collapse
Flashing another rom doesn't work?
abaaaabbbb63 said:
Flashing another rom doesn't work?
Click to expand...
Click to collapse
no dude, i cannot even open recovery mood, If i try by cmd am getting error
FAILED <remote: not allowed>
please help me
rizadrkm said:
no dude, i cannot even open recovery mood, If i try by cmd am getting error
FAILED <remote: not allowed>
please help me
Click to expand...
Click to collapse
In my sig, there's an sd-card partitioning guide. In that guide, you will find methods to install 4ext recovery. Try them.
thanks dude, i will try and let you know, :good:
jmcclue said:
Updated to the latest version, 4ext Recovery Touch v1.0.0.5 RC9
EDIT: No need to rename it now, just download and put on sdcard.
Edited because some people could not get it to work because renaming it was the hardest thing in the world :banghead:
All credits to Madmaxx for this great recovery....
Download PB99IMG.zip and put it on ur sdcard and then with ur phone off hold volume down + power. ur bootloader will look for the PB99IMG then ask u if u want to update recovery, volume up for YES, it will then ask you to reboot device, volume down for NO. Once its finished u now have 4ext recovery and just use volume buttons to navigate to recovery then press power button to enter recovery. I have tried it myself and it works, its the exact same method to install as Alpharev's hboots via PB99IMG.
Dont forget u must be S-OFF lol
Dont forget to delete it off sdcard once ur done or u will get asked to update everytime u enter bootloader
MD5 - 79496e1478ea56e33f3f2d90ac88adfe
(Also u can extract the PB99IMG.zip file and flash recovery.img via fastboot commands or android flasher)
Click to expand...
Click to collapse
All over above said i followed but nothing happened I think the SD is not detected. what shall i do now ? do i have to format the SD like FAT32 or somethings like that ?
---------- Post added at 07:29 AM ---------- Previous post was at 07:14 AM ----------
My CID version is 11111111
i got this via cmd comnd (fastboot getvar cid)
I am fadup with my phone, please help me to fix this
So none of the methods worked? Not even the PB99img?
Weird.
Try doing it with another sd-card.
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!!