Hello
I have (or had) a HTC FLyer with s-off and perma root until yesterday when I decided to upgrade to HC. Until the HTCDEV part, everything went ok, I didn't get any issue.
But during unlock bootloader via HTCDEV, it didn't go as the website directed. When I entered "fastboot oem get_identifier_token", I got a msg like this:
"... INFO [ERR] Command error !!! OKAY [0.007s] finised. total time: 0.008s"
This wasn't normal according to HTCDEv web page, but I somehow went to the next step #15, 'fastboot flash recovery revolutionary-cwm-4.0.1.4-flyer.newhboot.img', again everything seemd ok.
Nest step, clockwork mode - recovery THIS IS WHERE I GOT STUCK. When I "click" recovery on bootloader screen it goes to HTC screen and stuck there. I can get back to bootloader screen again by pushing power button long and then vol down - power; but I can no longer continue to CWM, therefore can't flash honeycomb syetem.zip.
When power down and vol-down+power to access bootloader menu, switching between fastboot and bootloader, there's a quick screen (it passes so quick that I couldn't figure out completely) where it says PG41IMG.zip, PG41DIAG etc. not found.
I downloaded the PG41IMG.zip, transferred to the root of the MicroSD card and booted. At the bootloader screen, this time it installed the filen and then later asked me if I wanted to update. Said "yes" with vol- and it updated the system after 5-6 mins.
As the installation ended, device opened but with 2.3.3 (Previous fw was Turkish ROM with 2.3.4 and with this 2.3.3, Turkish language was available only for Germany, Austria and Switzerland and not for Turkey. Then I used RUU_Flyer_HTC_WWE_2.23.405.3_R_Radio_20.3504.30.089BU_3809.07.04.06_M_release_204108_signed if anything could revert back, nothing but updated to 2.3.4, baseband changed to 20.3501 from 20.3504, still S-off.
BUT
* HBoot is STILL 6.10.1002 and didn't go back old one 1.11.1003
* CANNOT go into recovery mode. (first a phone icone with green arrows appear than a phone icon with red exclamation sign shows up), no recovery or CWM, so cannot go anything other.
I tried to re-install HC, but this time failed in radio writing, stuck there. Not a chance to more since RECOVERY gone.
Now the tablet is working (no brick) with 2.3.4 WWE EU rom.
Any idea how to re-install with CWM working and hboot initial version? What's the best way make a clean system?
Thanks
Once you executed the RUU , you are totally back to stock ,unrooted at the version of whatever RUU you used. I would run the RUU again to get everything back to stock, working. You need to go through the root process and install CWM again as if fresh from the box. If still stuck, go to GlobalTron's Revert to GB thread on this forum.
Thanks DigitalMD for comment.
Actually bootloader screen tells I'm still s-off but guess you're right I should be unrooted. To recover CWM, I've installed su-3.0-beta4-efgh-signed.zip to sdcart, but it doesn't seem to load it.
By the way, I'm still in GB 2.3.4 do I have to still revert back to GB with Globaltron to recover hboot?
Thanks & regards,
It depends. If its booting normally, then no. But you will need to do the install of revolution CWM recovery.
Could you please elaborate on how to re-install CWM recovery?
thanks
I actually do not understand what your current status is.
Does the device boot into normal operation?
If so, what version?
DigitalMD said:
I actually do not understand what your current status is.
Does the device boot into normal operation?
If so, what version?
Click to expand...
Click to collapse
Ok let me try to explain more in details. You know here's the guide I followed
http://android.modaco.com/topic/345950-installing-honeycomb-on-your-flyer-the-complete-guide/
Below photo is where I stuck at #15 after trying to enter recovery mode.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
At this moment, when I swithced between fastboot and bootloader, there was an error (this screen passes so quick so I couldn't take a complete shot). Here I was completely stuck, tablet didn't turn on at all.
Looking at the above photo, I though I needed PG41img.zip; I downloaded it and copied to rootfolder of sdcard. Then the following case happened:
I said "yes" and it worked for some time and then tablet came back to life. I then used another RUU. And now the tablet is working with this rom (GB 2.3.4). Now the bootloader is as follows:
Ok, now is the PROBLEM. At this status, when I go to RECOVERY and select it by pressing power; first this screen comes;
After this screen show up for a few seconds, then this screen comes and I cannot go any further for CWM.
At this status, if I press power button for 20-30 sec, it opens normally with an error "HTC recovered from a serious error, do you want to send report" etc. and other functions seems to work normal.
Now I would ask;
* How could I fix this issue, recover "recovery" and re-load CWM?
* How can I go back and re-load HC?
By the way, I got errors during bootloader unlock with HTCDEV.
Hope it's more clear now
kego said:
Ok let me try to explain more in details. You know here's the guide I followed
http://android.modaco.com/topic/345950-installing-honeycomb-on-your-flyer-the-complete-guide/
Below photo is where I stuck at #15 after trying to enter recovery mode.
At this moment, when I swithced between fastboot and bootloader, there was an error (this screen passes so quick so I couldn't take a complete shot). Here I was completely stuck, tablet didn't turn on at all.
Looking at the above photo, I though I needed PG41img.zip; I downloaded it and copied to rootfolder of sdcard. Then the following case happened:
I said "yes" and it worked for some time and then tablet came back to life. I then used another RUU. And now the tablet is working with this rom (GB 2.3.4). Now the bootloader is as follows:
Ok, now is the PROBLEM. At this status, when I go to RECOVERY and select it by pressing power; first this screen comes;
After this screen show up for a few seconds, then this screen comes and I cannot go any further for CWM.
At this status, if I press power button for 20-30 sec, it opens normally with an error "HTC recovered from a serious error, do you want to send report" etc. and other functions seems to work normal.
Now I would ask;
* How could I fix this issue, recover "recovery" and re-load CWM?
* How can I go back and re-load HC?
By the way, I got errors during bootloader unlock with HTCDEV.
Hope it's more clear now
Click to expand...
Click to collapse
you can reinstall with fastboot
fastboot flash recovery recovery_name.img
Ok, you need to go through the Revolution root process again and let it download and install CWM recovery.
I am a bit puzzled by the bootloader still being Revolution vs. stock. You might need to run the RUU revert process again.
Then if you want to go to HC , you have to redo that entire process again.
I think you need your original unlock.bin from the HTC site if you want to unlock the step it says to unlock the bootloader.
Basically you are back to total stock unrooted, no CWM recovery.
viera77 said:
you can reinstall with fastboot
fastboot flash recovery recovery_name.img
Click to expand...
Click to collapse
Sorry, which file recovery_name.img should be? Do I have to download an image file?
Thanks.
use this
http://revolutionary.io/
DigitalMD said:
Ok, you need to go through the Revolution root process again and let it download and install CWM recovery.
I am a bit puzzled by the bootloader still being Revolution vs. stock. You might need to run the RUU revert process again.
Then if you want to go to HC , you have to redo that entire process again.
I think you need your original unlock.bin from the HTC site if you want to unlock the step it says to unlock the bootloader.
Basically you are back to total stock unrooted, no CWM recovery.
Click to expand...
Click to collapse
As seen, I am still S-off. In order to do Revolution root, in any case I have to go to recovery but this was is closed?
After PG41IMG.zip update and resurrected the tablet, I used RUU_Flyer_HTC_WWE 2.23.405.3_R_Radio_20.3504.30.08 9BU_3809.07.04.06_M_release_204108_signed
rom to return back to original hboot but didn't work. You mean I have to re-run it?
Unlocking from HTCDEV was actually where eveything started. There's the commend "fastboot oem get_identifier_token". According to HTC guide, I have to get some string to be submitted but I recieved error instead like "command error"
Need some magic wand to roll back everything where it was
Thanks.
DigitalMD said:
use this
http://revolutionary.io/
Click to expand...
Click to collapse
HBOOT now changed to 6.10.1002, so not sure if this will work, since it says it supports only hboots 1.10.0000 and 1.11.0003. But still let me give a try.
Thanks.
I think revolutionary.io also doesn't work
Says waiting for device even the device is connected and show up in device manager.
kego said:
I think revolutionary.io also doesn't work
Says waiting for device even the device is connected and show up in device manager.
Click to expand...
Click to collapse
try with fastboot
http://forum.xda-developers.com/showthread.php?p=14693680
viera77 said:
try with fastboot
http://forum.xda-developers.com/showthread.php?p=14693680
Click to expand...
Click to collapse
viera77, thanks, now that worked!!
Now I can enter recovery CWM.
But still issues with HTCDEV unlock, get the same error. Any idea how to go on HC installation?
kego said:
viera77, thanks, now that worked!!
Now I can enter recovery CWM.
But still issues with HTCDEV unlock, get the same error. Any idea how to go on HC installation?
Click to expand...
Click to collapse
because you have soff (revolutionary)
If you are a beginner, HC to install can be risky
Hello,
True, I am beginner. Actually previously I had Advent Vega and Galaxy Tab and especially Advent, I am a bit familiar to HC. But I found HTC a lot complex compared to these
About s-off and HTCDEV unlock here is Paul's guide:
7. Unlock your Flyer's bootloader with Revolutionary.
.
.
14. You are now in a state where you must unlock the bootloader using the HTC tools - visit http://www.htcdev.com/bootloader/ and follow the instructions (Flyer compatability isn't listed, but it'll work)
I think in any case, Flyer is s-off'ed before doing official unlock. Do I miss something?
Many thanks
Turn on usb debugging on the phone and run revolutionary again.
globatron said:
Turn on usb debugging on the phone and run revolutionary again.
Click to expand...
Click to collapse
USB debugging was always on during all processes, never disabled. And revolutionary didn't work neither. Still "waiting for device..."
Seems I need to do s-on somehow but don't know. DigitalMD suggests to run RUU for unrooted and s-on system but this didn't work for my case. Not sure for root, but still s-off.
Related
Well I did some research and I hope I could explain how to un-brick your Flyer/HTC View..
Step 1: Do not freak out!
Step 2 Click here to download your Stock Rom
Step 3 Put your tablet it in recovery. By pressing down the Power button and the Vol Down button. While you have your USB plug to your PC
Step 4 Download adb file
Once you DL extract the file to your desktop.
Step 5,6,&7
Code:
cd C:\adb
Code:
adb devices
Code:
adb reboot oem-78
^^^This will make your Tablet Run RUU exe files
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Step 8 Click and Run your Rom for your tablet. This will take 10-15 mins.
<--- HTC View ( Express )
Step 9 You could open your eyes and your Tablet is unbrick.
Please forgive me for a sloppy way to explain but these are the steps to get your tablet to un brick. Plus I am not responsible WHAT SO EVER!!! Just trying to help
Technically there is no way to unbrick a device, because for a device to be truly bricked it has to be completely unusable, no recovery no nothing. Who cares about technicalities though, good job, I'm sure this will help someone down the road!
andmaf said:
Technically there is no way to unbrick a device, because for a device to be truly bricked it has to be completely unusable, no recovery no nothing. Who cares about technicalities though, good job, I'm sure this will help someone down the road!
Click to expand...
Click to collapse
That's true, at most this fixes a semi-brick. Some people consider it a brick, if there is no way to brick it back to life, without opening up the device.
How about some explanation of how you semi-bricked your Flyer/View? Trying to root, what step you got stuck on, etc. What were the symptoms? Stuck on boot splash screen, etc.
But thanks for posting.
redpoint73 said:
That's true, at most this fixes a semi-brick. Some people consider it a brick, if there is no way to brick it back to life, without opening up the device.
How about some explanation of how you semi-bricked your Flyer/View? Trying to root, what step you got stuck on, etc. What were the symptoms? Stuck on boot splash screen, etc.
But thanks for posting.
Click to expand...
Click to collapse
I was stuck on HTC logo, it took me 3 hours how to figure out. Again for noobs like myself we do call brick because we don't know what to do....
andmaf said:
Technically there is no way to unbrick a device, because for a device to be truly bricked it has to be completely unusable, no recovery no nothing. Who cares about technicalities though, good job, I'm sure this will help someone down the road!
Click to expand...
Click to collapse
Thanks for your input, then again there are noobs like myself.
You should be able to take the same RUU file and rename it to PG41IMG.zip, place it on the root of the sdcard, then boot into bootloader, and it will automatically check for the file and ask if you want to install. Does the same as what the OP does but with no ADB required.
***DO NOT*** leave this PG41IMG.zip on your sdcard. If you get caught in a bootloop or something similar it will prevent you from getting to recovery. Once hboot detects that file it only lets you choose install or reboot. So you can't select recovery without removing/renaming the file.
Sent from my HTC Thunderbolt
JBO1018 said:
You should be able to take the same RUU file and rename it to PG41IMG.zip, place it on the root of the sdcard, then boot into bootloader, and it will automatically check for the file and ask if you want to install. Does the same as what the OP does but with no ADB required.
***DO NOT*** leave this PG41IMG.zip on your sdcard. If you get caught in a bootloop or something similar it will prevent you from getting to recovery. Once hboot detects that file it only lets you choose install or reboot. So you can't select recovery without removing/renaming the file.
Sent from my HTC Thunderbolt
Click to expand...
Click to collapse
I had tried that, that didn't work.
CuzinBucksBx said:
I had tried that, that didn't work.
Click to expand...
Click to collapse
You must have made a mistake.
Check out this thread:
http://forum.xda-developers.com/showthread.php?t=1175589
When you download it on a windows pc, if the pc is setup to NOT show file extensions, and you name it .zip the file will end up being named PG41IMG.zip.zip causing it to fail. That is the most common reason for it to fail. It is also case sensitive, and MUST be on the root of the sdcard, not on any folders.
P-G-4-1-I-M-G
It works on basically every HTC Android device ever made and has worked on this particular one for other people.
Sent from my HTC Thunderbolt
CuzinBucksBx said:
I was stuck on HTC logo, it took me 3 hours how to figure out. Again for noobs like myself we do call brick because we don't know what to do....
Click to expand...
Click to collapse
Still didn't answer all my questions. What step, or what were you trying to do when you got stuck on the boot splash? Add this info to the OP, so people know what situation this "How To" is applicable for.
And its not a brick, just because you didn't know what to do.
Please! Help!!!!
I am stuck in the boot loader! no way to reboot the phone
I tried to install on the sd card PG41IMG.zip but the phone after something similar to an installation didn't reboot!!!
help help help!!!!
viskas said:
I am stuck in the boot loader! no way to reboot the phone
I tried to install on the sd card PG41IMG.zip but the phone after something similar to an installation didn't reboot!!!
help help help!!!!
Click to expand...
Click to collapse
There isn't an option to reboot that you can scroll to with the volume buttons and select with the power button??
If it did install the RUU you would have seen it saying stuff about unpacking and such on the screen, and a litle progress bar usually in the upper right hand corner tho it could be placed differently on a tablet. Either way after it install an RUU the only thing you should be able to do is press power to reboot.
Sent from my HTC Thunderbolt
Does this upgrade the hboot from the 1.1xxxx? Because I want root after unsemibricking my flyer.
ikingblack said:
Does this upgrade the hboot from the 1.1xxxx? Because I want root after unsemibricking my flyer.
Click to expand...
Click to collapse
Just use the ROM for your operator or the same WWE RUU that is used for the goldcard with a goldcard.
globatron said:
Just use the ROM for your operator or the same WWE RUU that is used for the goldcard with a goldcard.
Click to expand...
Click to collapse
Alright, thanks.
CuzinBucksBx said:
Well I did some research and I hope I could explain how to un-brick your Flyer/HTC View..
Step 1: Do not freak out!
Step 2 Click here to download your Stock Rom
Step 3 Put your tablet it in recovery. By pressing down the Power button and the Vol Down button. While you have your USB plug to your PC
Step 4 Download adb file
Once you DL extract the file to your desktop.
Step 5,6,&7
Code:
cd C:\adb
Code:
adb devices
Code:
adb reboot oem-78
^^^This will make your Tablet Run RUU exe files
Step 8 Click and Run your Rom for your tablet. This will take 10-15 mins.
<--- HTC View ( Express )
Step 9 You could open your eyes and your Tablet is unbrick.
Please forgive me for a sloppy way to explain but these are the steps to get your tablet to un brick. Plus I am not responsible WHAT SO EVER!!! Just trying to help
Click to expand...
Click to collapse
Much gratitude for saving my butt! Your instructions worked to a T!
alexv59 said:
Much gratitude for saving my butt! Your instructions worked to a T!
Click to expand...
Click to collapse
At least someone in this thread appreciated my help.
OK i followed the instructions provided. However when i go to type the commands into the cmd prompt im told it ist a valid file path or name. HELP!! I am S-OFF and yes call me stupid i did not load the custom recovery after. SO I am stock recovery/bootloader with S-OFF and it wont boot past the HTCscreen.
mizono said:
OK i followed the instructions provided. However when i go to type the commands into the cmd prompt im told it ist a valid file path or name. HELP!! I am S-OFF and yes call me stupid i did not load the custom recovery after. SO I am stock recovery/bootloader with S-OFF and it wont boot past the HTCscreen.
Click to expand...
Click to collapse
LMAO...that makes two of us!
Blaqdymun said:
LMAO...that makes two of us!
Click to expand...
Click to collapse
I didn't do any adb pushing ....
just put phone in recovery/fastboot
Ran the RUU and WHELLA!!!
THANK YOU SO MUCH!!!!
DAPS!
I install with RUU, give error code :
WRONG BOOTLOADER.
And if i install with PG41IMG.zip other error:
Main version is older!
Update Fail!
Press Power to Reboot.
and adb devices show nothing.
C:\flyer>adb reboot oem-78
error: device not found
but fastboot can connect
C:\flyer>fastboot devices
HT16ET400059 fastboot
C:\flyer>fastboot flash boot stock-hc-flyer-boot.img
sending 'boot' (3242 KB)... OKAY
writing 'boot'... INFOsignature checking...
FAILED (remote: signature verify fail)
EDIT: My Flyer runs now.
I have reunlocked from htc homepage.
Hi,
I'm stuck in this situation with my htc evo view 4g device.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
everytime I try to reboot, or enter recovery, or factory reset it just hangs at this screen:
I try to flash this stock rom
RUU_Express_Sprint_WWE_1.22.651.1_Radio_1.05.11.0531_NV_2.28_SPCS_release_198141_signed
(via both RUU on my pc and goldcard with PG41IMG.zip), it was flashed flawlessly, but when finished it hangs in that "htc" screen.
I tried to s-off by revolutionary but I can not access the android working screen so that can not enable usb debugging mode, on the pc it just shows
waiting for device ....
Click to expand...
Click to collapse
I tried to unlock the bootloader via htcdev (I know my view 4g isn't in the supported list yet, but at least fastboot should read its info, but I was wrong). At step 8, it shows:
C:\Android>fastboot oem get_identifier_token
...
(bootloader) [ERR] Command error !!!
OKAY [ 0.007s]
finished. total time: 0.007s
Click to expand...
Click to collapse
It still boots in to fastboot mode,and I could see that it's s-on, hboot is 1.13. Now I want to make it s-off or unlock the bootloader in order to flash a custom rom.
Can some one please help me with this ?
Thanks a lot,
Medkid
I tried to unlock the htc view's bootloader by htcdev, at steps 8 it shows me this
C:\Android>fastboot oem get_identifier_token
...
(bootloader) [ERR] Command error !!!
OKAY [ 0.007s]
finished. total time: 0.007s
Click to expand...
Click to collapse
can you help ? plz
what were you trying to do when you got into this situation and did you run the ruu more than once?
mcord11758 said:
what were you trying to do when you got into this situation and did you run the ruu more than once?
Click to expand...
Click to collapse
Upload the logs from c:\ruu_log
yes, I try to run RUU about 10 times, and It always runs till the end, but after that my device just hangs at htc screen
mcord11758 said:
what were you trying to do when you got into this situation and did you run the ruu more than once?
Click to expand...
Click to collapse
I don't know what happened to my evo view, I didn't s-off it before. My brother borrowed it and when he gave it back to me, it was just in that situation, hung at htc screen. So I tried to flash another stock rom (actually , it's the rom running in my device) , but I have no luck to bring it back
Are you sure you're using the 1.22.651.1 RUU?
The reason for asking is that the RUU process is detecting that as the version-main on your device but is then saying there is a version check failure which would indicate that that is not the RUU you are using.
I tried the RUU in the first post, also another sprint express RUU 1.18 with no success bcoz of a bootloader error. I download these 2 roms from this thread
http://forum.xda-developers.com/showthread.php?t=1062184
You must use the 1.22.651.1 ROM, can you run that again and collect the RUU log for that version.
revolutionary root
medkid said:
I've a htc evo view 4g device. Now, it's stuck in the semibrick circumstance i think. It still boots in to fastboot mode,and I could see that it's s-on, hboot is 1.13. Now I want to make it s-off or unlock the bootloader in order to flash a custom rom. I tried the stock rom RUU_Express_Sprint_WWE_1.22.651.1_Radio_1.05.11.05 31_NV_2.28_SPCS_release_198141_signed , it did flash but when it reboots it just hangs up at "htc" white screen.
I tried htcdev to unlock the bootloader but they do not support View 4g yet.
I tried revolution pre 0.4 without any luck because it asks for the device to enter the working screen. The tool only shows "wating device..."
Can some one please help me with this ?
Thanks a lot,
Medkid
Click to expand...
Click to collapse
I used the same method as I did on the Evo 3D for my HTC view tablet and it works My view is rooted hope this helps in anyway
dlo227 said:
I used the same method as I did on the Evo 3D for my HTC view tablet and it works My view is rooted hope this helps in anyway
Click to expand...
Click to collapse
thanks for your answer. But in order to make revolutionary to work, you have to access android working screen to enable the "usb debugging mode", if not, there is no luck. htcdev tool does not ask for this, everything is working on the fastboot mode. Unfortunately, somehow fastboot.exe couldn't read my device info in the step 8.
@globatron, I'll try to reflash it and upload the log. Thanks so much for joining me
Try pulling the rom.zip out of the 1.22 ruu.
Rename the zip PG41IMG.zip (.zip is the extension not part of the name, some people actually make that mistake).
Place the PGxx.zip in the root of an sdcard and place the card in the device.
Boot the device into bootloader/fastboot and let it read and hopefully it should install and get you back to a running state.
I find running ruu's can most times be a pain than a saviour.
lovethyEVO said:
Try pulling the rom.zip out of the 1.22 ruu.
Rename the zip PG41IMG.zip (.zip is the extension not part of the name, some people actually make that mistake).
Place the PGxx.zip in the root of an sdcard and place the card in the device.
Boot the device into bootloader/fastboot and let it read and hopefully it should install and get you back to a running state.
I find running ruu's can most times be a pain than a saviour.
Click to expand...
Click to collapse
thanks for your advice, I did try it that way with no success. let me make thing clearer in the first post.....
Run the RUU again as I said, with the version I specified. I need to see a log that is definitely for that version.
Sorry for the delay, it seems that the main battery is low, I can't run the RUU right now. It is charging. Sorry for that
when you have enough power to do this, delete all the old log files before running the RUU so only the ones from this run are included.
okay, here it is the log file
ok, that RUU was entirely successful. Does it boot now or is it still the same?
It's still the same, hangs at htc screen
try removing the sdcard and a factory reset (both together) then see if it will boot with the card still removed. If not take it in for repair telling sprint that you tried to take an OTA update then this happened.
I WILL NOT BE RESPONSIBLE IF YOU BRICK YOUR DEVICE OR YOU LOSE YOUR ALREADY UNLOCKED BOOTLOADER
THIS ONLY WILL WORK IF YOU HAVE UNLOCKED YOUR BOOTLOADER BEFORE THE OTA
GOOD LUCK TO ANYONE BRAVE ENOUGH TO TAKE THE PLUNGE
IF YOU ARE S-OFF PLEASE VISIT THIS THREAD
To better explain this guide, what it does is explains how to get the 2.04 OTA firmware without losing your already ***Unlocked*** bootloader. You will have to lock your bootloader, then RUU back to 1.15, re-unlock your bootloader and take the OTA and then re-flash a custom recovery.
This is what I did and it should work (Not a 100% Guarantee) :
Download the 1.15 RUU
Have your ORIGINAL Unlock_code.bin token ready (from when you've unlocked your bootloader on the 1.15 release)
Backup ALL of your sdcard contents as this will completely wipe the device
Have about 30~60 minutes to sit down and do this
[Step 1]:
Boot into Bootloader and if you aren't in fastboot click on fastboot to get there and if it says " fastboot usb " you're good now
[Step 2]:
Enter the following command:
Code:
fastboot oem lock
Then let it do its thing, it might reboot.
[Step 2a]:
Boot back into fastboot then right click RUU and click on " Run as Administrator " then follow the on screen instructions.
[Step 3]:
After the RUU finishes power off the device and then boot back into bootloader again and get to " fastboot usb " then open command prompt and navigate to where you have your " Unlock_code.bin "
[Step 3a]:
Enter the following code:
Code:
fastboot flash unlocktoken Unlock_code.bin
[Step 3b]:
On your device use [Vol Up] to select " Yes " and then [Power] to proceed.
[Step 4]:
Then boot up and go to the " Update System " and check for an update (It should prompt you to take the OTA, do it)
You should now be good to go with the latest firmware and all thats left it to reflash TWRP or CWM and either a ROM of your choice or a Nandroid.
*** TAMPERED ***
*** UNLOCKED ***
Click to expand...
Click to collapse
Here is a good ROM to flash after OTA [ROM][2.04.605.2] Stock Rooted Deodexed Zipaligned Semi-Debloated + Extras
After I completed all of these steps and took the OTA, I did not have to reflash the Unlock_code.bin file to unlock my bootloader it stayed unlocked after I took the OTA but in case yours does not just re-flash the Unlock_code.bin file one more time and it should do the trick.
Here is my proof that it worked for me:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I see that this procedure keeps the bootloader unlocked. So I'm assuming that this will also allow us to reinstall superuser (supersu) again?
ghstrdr1985 said:
I see that this procedure keeps the bootloader unlocked. So I'm assuming that this will also allow us to reinstall superuser (supersu) again?
Click to expand...
Click to collapse
Yes or if you have a nandroid you can also restore that and it will be like it was just with the new firmware
That's all I did was re flash twrp and restored my nandroid and I'm all good
Sent from my HTC6435LVW using XDA Premium HD app
This is not how I did it, but glad it worked for you. I followed the guide here: http://forum.xda-developers.com/showthread.php?t=2017525
I backed up my pics, movies, music and whatnot, then I flashed TWRP 2.4.1.0 and did a Nandroid backup of system and data. TWRP is known on our device to make better backups and restores than CWR. ***NOTE*** flashing the RUU will completely wipe your phone including your backup. Make sure you copy the entire TWRP folder to your PC!!!***
Next, I locked my bootloader using:
Code:
fastboot oem lock
I then flashed the RUU as administrator. When the device boots up don't worry about GPS or signing into Google. Force an OTA update under Settings\About\Software update. Accept the update. It will download and then ask you if you want to apply. Answer yes.
The phone will reboot into stock recovery and start flashing updates. It will reboot the recovery at least once while doing so. Do not touch your phone until it boots into Android automatically. Again, don't worry about GPS or Google login. You SHOULD boot into a message that says the 2.04 update was successful. The first reboot from my "update" did not stick. I had to force another OTA update download and told it to apply again. It worked for me the second time.
Once you have a successful 2.04 update, fastboot into bootloader and unlock your bootloader again with your original unlock_code.bin.
I'm not sure if this applies any more, but step 8 of that guide says to flash the unlocked kernel and recovery. He's referring to the kernel ripped from dsb's s-off dev phone he got from the DNA launch. It allows for root access and custom recoveries to be installed. I'm not sure if this is necessary any more, but it's the only kernel I know that when you flash it, it automatically makes the phone boot into Android and you have the new "Do no not distribute outside of HTC blah blah blah" HTC logo screen. It also makes your bootloader say ***TAMPERED*** again.
I've uploaded it here (Right click and save)
After it boots into Android copy the TWRP directory back from your PC. Reboot into fastboot and flash TWRP and any kernel you want. Restore your backup (system and data.) Flash any kernel modules necessary. Wipe dalvik cache and cache (do not factory reset or wipe system.) Reboot and PROFIT. (Restore your pics, movies, music and whatnot.)
Again, this is how I did it. YMMV.
docnok63 said:
This is not how I did it, but glad it worked for you. I followed the guide here: http://forum.xda-developers.com/showthread.php?t=2017525
I backed up my pics, movies, music and whatnot, then I flashed TWRP 2.4.1.0 and did a Nandroid backup of system and data. TWRP is known on our device to make better backups and restores than CWR. ***NOTE*** flashing the RUU will completely wipe your phone including your backup. Make sure you copy the entire TWRP folder to your PC!!!***
Next, I locked my bootloader using:
Code:
fastboot oem lock
I then flashed the RUU as administrator. When the device boots up don't worry about GPS or signing into Google. Force an OTA update under Settings\About\Software update. Accept the update. It will download and then ask you if you want to apply. Answer yes.
The phone will reboot into stock recovery and start flashing updates. It will reboot the recovery at least once while doing so. Do not touch your phone until it boots into Android automatically. Again, don't worry about GPS or Google login. You SHOULD boot into a message that says the 2.04 update was successful. The first reboot from my "update" did not stick. I had to force another OTA update download and told it to apply again. It worked for me the second time.
I'm not sure if this applies any more, but step 8 of that guide says to flash the unlocked kernel and recovery. He's referring to the kernel ripped from dsb's s-off dev phone he got from the DNA launch. It allows for root access and custom recoveries to be installed. I'm not sure if this is necessary any more, but it's the only kernel I know that when you flash it, it automatically makes the phone boot into Android and you have the new "Do no not distribute outside of HTC blah blah blah" HTC logo screen. It also makes your bootloader say ***TAMPERED*** again.
I've uploaded it here (Right click and save)
After it boots into Android copy the TWRP directory back from your PC. Reboot into fastboot and flash TWRP and any kernel you want. Restore your backup (system and data.) Flash any kernel modules necessary. Wipe dalvik cache and cache (do not factory reset or wipe system.) Reboot and PROFIT. (Restore your pics, movies, music and whatnot.)
Again, this is how I did it. YMMV.
Click to expand...
Click to collapse
Thanks I forgot to add the Fastboot oem lock command...i fixed the op
I based my guide off of my own experience and the exact steps i took, to me its pretty straight forward and took as little effort as possible, it doesnt require flashing as much
That guide is to get back to Stock 1.15 what my guide is, is how to get the OTA 2.04 w/o losing the unlocked bootloader, and i wanted to make a more clean guide and put in in the Q & A section so people would see it if they came here to ask the question. Just trying to be helpful oh and that RUU link in that other guide is for the transformer TF300 Tablet haha
.torrented said:
Thanks I forgot to add the Fastboot oem lock command...i fixed the op
Click to expand...
Click to collapse
You're welcome. You never flashed unsecure.img? What kernel are you using? Do you have the "Do not distribute outside of HTC blah blah blah" in your logo? Does your bootloader say tampered?
docnok63 said:
You're welcome. You never flashed unsecure.img? What kernel are you using? Do you have the "Do not distribute outside of HTC blah blah blah" in your logo? Does your bootloader say tampered?
Click to expand...
Click to collapse
look at where i have "This is my proof" section and no After I RUU'ed I didnt have to flash anything besides the Unlock_code.bin file... I did restore my previous nandroid but it had the same kernel as the ota has
and the only way to get rid of the HTC garbage is to get S-OFF and change some things in the hboot.img
When I click your proof button, nothing happens. All other "show content" work.
The newer kernels may allow root and custom recovery without messing with the HTC boot screen and putting tampered on the bootloader. I just did it to be better safe than sorry.
docnok63 said:
When I click your proof button, nothing happens. All other "show content" work.
The newer kernels may allow root and custom recovery without messing with the HTC boot screen and putting tampered on the bootloader. I just did it to better safe than sorry.
Click to expand...
Click to collapse
Oh well it should have loaded some pictures that I uploaded I'm on the OTA stock kernel. And the the tampered msg I believe is related to using a custom recovery as well as the boot screen msg
Everything seems to be working like all my root apps and such
Sent from my HTC6435LVW using XDA Premium HD app
Ok so I followed the procedures here but cannot re-unlock the bootloader. OTA came through fine. When I attempted to apply the unlock token, the warning screen comes up & I vol+ to yes & press the power button. I let it run its cycle & then adb reboot bootloader to a relocked bootloader. I will attempting this a 3rd time. Do I need to continue doing this until it's unlocked?
ghstrdr1985 said:
Ok so I followed the procedures here but cannot re-unlock the bootloader. OTA came through fine. When I attempted to apply the unlock token, the warning screen comes up & I vol+ to yes & press the power button. I let it run its cycle & then adb reboot bootloader to a relocked bootloader. I will attempting this a 3rd time. Do I need to continue doing this until it's unlocked?
Click to expand...
Click to collapse
I going to assume it is, but I have to ask if it's the token you got from unlocking the first time? I've seen it posted that getting a new token from HTCdev does not work.
Yes it is the original token. 3 times so far hasn't done the trick. I read elsewhere that to just keep doing it until it finally sticks.
docnok63 said:
I going to assume it is, but I have to ask if it's the token you got from unlocking the first time? I've seen it posted that getting a new token from HTCdev does not work.
Click to expand...
Click to collapse
Yes it's the one from the very first time you would have unlocked the bootloader. After the OTA HTC has patched the exploit so you wouldn't even get to the step where you would get an Unlock_code.bin. I believe they patched the SuperCID hack.
ghstrdr1985 said:
Yes it is the original token. 3 times so far hasn't done the trick. I read elsewhere that to just keep doing it until it finally sticks.
Click to expand...
Click to collapse
Yea I've heard this as well, just keep trying. Best of luck to you. Try this, power off the device fully then boot strait into the bootloader and then flash it.
After re-reading the procedures over & over, should I have unlocked the bootloader before OR after the OTA? The reason I ask is because I sent the OTA before trying to unlock the bootloader.
ghstrdr1985 said:
After re-reading the procedures over & over, should I have unlocked the bootloader before OR after the OTA? The reason I ask is because I sent the OTA before trying to unlock the bootloader.
Click to expand...
Click to collapse
First you would have Locked it
Then ran the RUU
Then Unlocked it with your token
Then take the OTA
Then flash a recovery
But I also said that if the OTA locked it back up to run the token again and it should have did the trick(this part im not 100% certain because mine didnt re-lock after I took the OTA (it stayed unlocked)
what do you get in the Command prompt when you run the token? and are you in fastboot when you do it or are you in bootloader when you do it?
As you can see, I didn't try to re-unlock until after getting the OTA. I'm not sure if it matters when you do it, but you have to do it in order to get root access and flash a custom recovery.
Command prompt says it completed successfully. I'm in fastboot usb mode. I suppose I could try the RUU again & unlock the bootloader BEFORE the OTA...or is it too late to run the RUU again?
**EDIT***
Nevermind. It FINALLY unlocked. I think that was the 5th time. Again, I do thank you for all of your support on this. I must say this guide is probably the most straight-forward one here.
ghstrdr1985 said:
Command prompt says it completed successfully. I'm in fastboot usb mode. I suppose I could try the RUU again & unlock the bootloader BEFORE the OTA...or is it too late to run the RUU again?
Click to expand...
Click to collapse
This I've never tried so I can't help you out with it.
.torrented said:
This I've never tried so I can't help you out with it.
Click to expand...
Click to collapse
It's all good. I finally got it to unlock after 5 attempts.:highfive: Thank you, though.
worked for me first time! thanks
So I'm a real noob to rooting, so please be patient. My wife dropped her phone in the washing machine without noticing, and it went through a whole cycle. Long story story, her HTC EVO 3d is dead, and had to buy used one off ebay. Just got it yesterday, it's been rooted with stock 2.3.4 rom. She was never a fan of this, so I looked into getting her a custom ICS rom. Already installed was the Revolutionary CWM recovery from the previous owner. How this differs from regular CWM, I'm not sure. I went ahead and download ROM manager and assumed I flashed the recovery to regular CWM. I then proceeded to reboot with the power and vol down buttons, and was searching the recovery menus again, and I noticed Revolutionary CWM was still on the phone. Then I somehow accidentally installed a custom rom I downloaded on the sd card, into the recovery menu. Well now the phone doesn't go past the HTC logo and I'm at a loss. Any help or am I doomed?
First thing you need to do is pull out the battery, put it back in and hold power+vol down button.
should get you into bootloader. Tell us what it says there. like s-on/off hboot version etc. you probably should be able to access recovery from there as well
How to fix recovery
Im not such an expert on android, rooting etc but that knowlegde I have ill share
As far as I know, I may be wrong, the HBoot version you have wont make a difference,
Try -
- take battery out
- replace battery and hold volume up rfirst and then press and hold power (boots in hboot after +/- 3 seconds)
- now use power, and volume buttons, boot into fafstboot(should just be power button)
- plug usb cable in computer and connect phone
- if you have fastboot, navigate to the exe (fastboot.exe) else just google fastboot download
- google your choice of recovery, 4 ext (i prefer) or cwm,etc its a zip file(extract the recovery.img file) or just a plain recovery.img file
- place this recovery.img file in the exact diractory as fastboot
- now make sure your phone says FASTBOOT USB, ,if it doesnt, check that ur phone is connected, try different usb ports or other cables
- press windows key and 'r' @ the same time, then run cmd
- navigate to fastboot directory
- type " fastboot devices" to check if cmd picks up ur phone , result should be a serial num- mine eg would look like (HN225NM5698)
- then if it did pick up device...
- type " fastboot flash recovery recovery.img " flashes ur custoom recovery u downloaded to ur phone
- now to boot into recovery type " fastboot boot recovery.img " OR to reboot type " fastboot reboot " phone reboots
IF ABOVE INSTRUCTIONS DID NOT SOLVE PROBLEM
try, if possilbe, booting into OS, download ROM manager and flash CWM recovery through that, if that doesnt work
try running a RUU, (remember to change ur CID to match RUU) and lock ur bootloader
if all else fails, follow my post @ ask team derp ur q pg.550, that might help:good:
cybergurken said:
the HBoot version you have wont make a difference,
Click to expand...
Click to collapse
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
@OP
If you want a completely up to date phone just use the latest RUU. It will update everything to the latest.
Then if root is not important leave it. And if you want root then just flash a recovery and then superuser zip.
EDIT : I see you edited it yourself.
EM|NEM said:
First thing you need to do is pull out the battery, put it back in and hold power+vol down button.
should get you into bootloader. Tell us what it says there. like s-on/off hboot version etc. you probably should be able to access recovery from there as well
Click to expand...
Click to collapse
Yes, I'm able to get into both bootloader and Revolutionary CWM Recovery. Bootloader states:
***UNLOCKED***
SHOOTER XC SHIP S-ON RL
HBOOT-1.50.0000
eMMC-boot
Aug 7 2011, 10:21:40
If you want to run roms w/o problems I'd suggest you get s-off.
http://forum.xda-developers.com/showthread.php?t=1889438
This guide should be sufficient
EM|NEM said:
If you want to run roms w/o problems I'd suggest you get s-off.
http://forum.xda-developers.com/showthread.php?t=1889438
This guide should be sufficient
Click to expand...
Click to collapse
Awesome, I will look into this guide. Should I do the guide step by step or just the wire trick for s-off?
@EM|NEM
Oops My Bad..
How can i forget that i had hboot 1.5 and wasnt able to use revolutionary so i did unknownforce's bricking method.
Thanks.
the wire-trick requires stock rom although some people have managed to get it to work with custom roms. you'll probably need to run the RUU to get back to stock so its best if you follow all the steps.
---------- Post added at 01:16 AM ---------- Previous post was at 01:07 AM ----------
mnomaanw said:
NO WAIT! Why do you want to go the harder way when you already have hboot 1.50, which can be s-offed without wiretrick !
Go to revolutionary.io and set your 3d free.
Dont run the ICS RUU , just run the 2.08 gingerbread ruu again and use revolutionary.
Click to expand...
Click to collapse
isnt a 1.4 hboot required for cdma? i'm not sure about this as i have a gsm device
Ok, so because it's my wife's phone, and she could care less if it's rooted or not, what is my best option here? All she'd like is stock ICS, like on her last non-rooted stock Evo 3D. Would it be best to flash ICS ruu and call it done? Is this the easiet way to get it back to basic ICS as OTA updates won't work?
cmsanchez00 said:
Ok, so because it's my wife's phone, and she could care less if it's rooted or not, what is my best option here? All she'd like is stock ICS, like on her last non-rooted stock Evo 3D. Would it be best to flash ICS ruu and call it done? Is this the easiet way to get it back to basic ICS as OTA updates won't work?
Click to expand...
Click to collapse
Yes sir! OTAs will work after clean RUU flash. And if you ever want to s-off or just unlock through htcdev, you can always do that later.
cmsanchez00 said:
Ok, so because it's my wife's phone, and she could care less if it's rooted or not, what is my best option here? All she'd like is stock ICS, like on her last non-rooted stock Evo 3D. Would it be best to flash ICS ruu and call it done? Is this the easiet way to get it back to basic ICS as OTA updates won't work?
Click to expand...
Click to collapse
If she want stock ics then the ruu well be enough
Sent from my HTC Sensation Z710e using Tapatalk 2
mnomaanw said:
Yes sir! OTAs will work after clean RUU flash. And if you ever want to s-off or just unlock through htcdev, you can always do that later.
Click to expand...
Click to collapse
Awesome, thanks for your help everyone. Appreciate it.
cmsanchez00 said:
Awesome, thanks for your help everyone. Appreciate it.
Just to confirm, I can use either the Gingerbread OR the ICS ruu correct?
Click to expand...
Click to collapse
yes but once you use ICS, you cannot use gingerbread again unless you are s-off.....you can flash same version of gingerbread or an updated version of gingerbread or ICS but you cannot flash old version once you update...in short , you cannot downgrade.
mnomaanw said:
yes but once you use ICS, you cannot use gingerbread again unless you are s-off.....you can flash same version of gingerbread or an updated version of gingerbread or ICS but you cannot flash old version once you update...in short , you cannot downgrade.
Click to expand...
Click to collapse
Perfect. Makes sense.
So I tried flashing ruu but cannot because pc cannot recognize phone, as I can't get it to go past htc logo as it just hangs there. It's basically sitting in a Charge Only mode. I'm only able to access bootloader screen. Sooooo, next option would be to place RUU on sd card and install from there, correct? Does ruu need to be zip file in order to flash in recovery screen? Or can I still use the exe file that's sitting on my desktop?
Boot into boot loader and select fastboot and connect phone to pc ...phone should show fastboot usb.then run the RUU and let it complete the process . It's not necessary to boot into android if you are in fastboot mode.
EDIT : oh sorry I forgot, that you will have to relock the boot loader before using RUU using "fastboot oem lock" command
mnomaanw said:
Boot into boot loader and select fastboot and connect phone to pc ...phone should show fastboot usb.then run the RUU and let it complete the process . It's not necessary to boot into android if you are in fastboot mode.
EDIT : oh sorry I forgot, that you will have to relock the boot loader before using RUU using "fastboot oem lock" command
Click to expand...
Click to collapse
So, here's my issue, I can see FASTBOOT USB show up no problem in bootloader, but my problem is, my pc won't recognize my phone through usb cable. My phone doesn't show up in windows explorer. Before, I could just change the USB from "charge only" to "Disk Drive" and my pc would list my sd card at Drive E. That's my issue, if pc can't see phone, I can't relock bootloader and can't run ruu. Am I missing a step here?
cmsanchez00 said:
So, here's my issue, I can see FASTBOOT USB show up no problem in bootloader, but my problem is, my pc won't recognize my phone through usb cable. My phone doesn't show up in windows explorer. Before, I could just change the USB from "charge only" to "Disk Drive" and my pc would list my sd card at Drive E. That's my issue, if pc can't see phone, I can't relock bootloader and can't run ruu. Am I missing a step here?
Click to expand...
Click to collapse
If you have htc sync on your pc uninstall it and install htc drivers (google it) and restart your pc
Also if you have antivirus disabled it too
Sent from my HTC Sensation Z710e using Tapatalk 2
hanisod said:
If you have htc sync on your pc uninstall it and install htc drivers (google it) and restart your pc
Also if you have antivirus disabled it too
Sent from my HTC Sensation Z710e using Tapatalk 2
Click to expand...
Click to collapse
I don't have HTC sync and I installed the htc drivers. No bueno.
Only way I can get my pc to recognize phone is if I go into recovery and "Mount USB Storage" - this is the only way File Exporer pops up my sd card.
I have an HTC Evo 3d Sprint (SHOOTER XC ENG), S-OFF RL, HBOOT-1.04.2000 (PG8610000), eMMC-boot, RADIO-11.25.3504.06_M
Anyway, here's what I did:
I wanted to necromancy the phone back to life. Years ago, it was my primary phone, and was rooted with MeanRom and a custom kernel from -that guy-.
First thing I did was, from 4ext Recovery, a full wipe of everything like 6 times. Then I installed ViperROM. Everything was great, except that the reason I was trying this was to test the phone out with FreedomPop, meaning I'd have to do a carrier release (##72786#), and ViperROM wasn't letting me do that. So, off with ViperROM...I went back into 4ext and wiped everything again. Tried Revolution HD, and it wouldn't load past the "quietly brilliant" screen. Decided to ditch that plan and go back to "stock".
So, I downloaded the Yoda's "stock ICS" ROM, and figured I'd update my radios while I was at it. Radio update with PM86IMG.zip worked fine, then went to install the ROM.
Not only does it not boot past the HTC screen (doesn't even get to the "quietly brilliant" screen), but now 4ext is gone!
So, I need a new recovery. I've tried to flash TWRP using the update.zip method: I downloaded twrp-3.0.2-0-shooter.img from their website, renamed it "recovery.img", put it in a .zip file (uncompressed) named PG86IMG.zip, put it into the root of my sdcard, then booted into HBOOT.
It runs the auto-loading, finds the file, then suddenly goes back to bootloader. There's a millisecond there where it looks like there's an error message (after it says "parsing PG86IMG.zip"), but before I can read it, I'm back in HBOOT.
RUU doesn't recognize the device, nor does adb, nor does just my bare computer.
Any help?
You should put your phone in bootloader mode and use
fastboot flash recovery recovery.img
Command to flash recovey.
Vogie said:
You should put your phone in bootloader mode and use
fastboot flash recovery recovery.img
Command to flash recovey.
Click to expand...
Click to collapse
Thank you for the reply.
Unfortunately, as I said above, adb isn't working. The fastboot usb flag comes on when I plug it into a computer, but nothing on the computer recognizes that anything is plugged in at all.
Are you in bootloader menu? I think you are not.
How to go to bootloader menu: Do a battery pull first then do the power and volume down.
OR:
Just to clear things up, the proper procedure to access the Bootloader Screen on the EVO 3 D is as you stated, turn off Fastboot, power down and then hold the Volume DOWN key while pressing the power button for a couple of seconds.
refere to http://forums.androidcentral.com/ht...hacks/97491-how-access-evo-3d-bootloader.html
Vogie said:
Are you in bootloader menu? I think you are not.
Click to expand...
Click to collapse
I am. For certain. I know what the bootloader is, heh.
When I first power+vol.down, the phone boots into bootloader (obviously), attempts to flash the PG86IMG.zip on the root of my SD, then goes back to bootloader. If I select Recovery from there, I get sent back to Fastboot.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I think my partitions are gone, could be the problem. The recovery.img file inside PG86IMG.zip is supposed to flash to the recovery partition, and the matching names is how the bootloader knows to do that. If the recovery partition is gone, there's nowhere to flash the recovery.img to.
Does that sound feasible to anyone?
If that's the case, how do I get my partitions back? Remember, plugging the phone into my computer does nothing - it does not show up on the computer AT ALL.
Update:
On a hunch, I tried using PG86IMG.zip to flash a copy of 4ext Recovery. It worked (dunno why TWRP, CMRecovery, or Stock recovery didn't, maybe there was something left over of 4ext that made it incompatible with others).
So, having a functional recovery, I proceeded to try flashing a ROM. I went with Yoda's "stock" above again. Install went perfectly smooth, but after reboot, frozen at the HTC screen. Battery pull, Vol-Down/Power to get into bootloader, choose recovery and BLAM...no recovery again (phone gets kicked out of bootloader into Fastboot mode, again).
Re-flashed 4ext again...again it worked fine...loaded the ROM...again it installed fine...reboot...BLAM.
Is there something wrong with my ROM selection? I'll try a different one tomorrow.
Update:
Aha! Turns out that my hboot...Eng-hboot 1.04.2000...is incompatible with newer kernels.
Anyone have a link to Anthrax 3.6?
So, I flashed Viper 3D ROM, figuring that it worked before, although I was on earlier radios then.
It flashed just fine, Aroma installer went through everything, then asked to reboot. At first I didn't do it, because I wanted to check out stuff in the recovery first. So, when I rebooted through the recovery, it just rebooted back INTO recovery. I powered down, tried to power up, went straight to recovery. So I did another full wipe of everything, and installed Viper 3D ROM again. This time I selected the reboot option at the end of the Aroma installer. Immediately went into bootloops. It gets to the Viper 3D loading screen, then bootloops.
So I found Chad's old kernel and flashed that, thinking it might help. Now it bootloops four times exactly, then freezes on the Viper 3D loading screen.
By the way, I feel like I'm talking to myself here.
I've reflashed Viper3D a few times now, with no luck. It installs just fine, and I can boot into it as far as the Viper3d logo, but that's all.
Still a kernel problem, you think?
(Not like anyone is actually reading this besides me....)
Updated the radios again and now it actually booted Viper 3D ROM!
Going through the setup process now. Will report back once it's done, to see if I still have the original problem of not being able to do a carrier release.
Thanks for all your help everyone![/sarcasm]
Yep, still can't do ##72786#. Asks me if I want to execute the command, I click OK, it does nothing.
Oh well, I'll find a TeamVenom guy and ask them.
Just in case anyone actually reads this, I'm still unable to use any of the hidden dialer codes. According to Jan, this is a known issue with ViperROM, but he doesn't know how to fix it, and Virus is AWOL, heh.
Does anyone know of any other hboot-agnostic ROMs for the Evo 3D?
MY HTC EVO #D CDMA also BOT loop
i want help ,my htc evo 3d cdma boot loop