Ok, i post it because i think i've read it all and still no fix.
I have 1.5 hboot S-ON HTCUnlocked, custom recovery.
putting the ruu in the SD does not work (unlocked or relocked)
when relocked there is a security warning and the phone doesn't boot, only bootloader.
Stock Rom and htc update just end in the red "!" symbol because i have custom recovery.
I flashed a "stock recovery" i downloaded using fastboot, same problem.
So, does anyone in the same circumstances have succided updating the firmware, antennas, etc?
fcomeba said:
Ok, i post it because i think i've read it all and still no fix.
I have 1.5 hboot S-ON HTCUnlocked, custom recovery.
putting the ruu in the SD does not work (unlocked or relocked)
when relocked there is a security warning and the phone doesn't boot, only bootloader.
Stock Rom and htc update just end in the red "!" symbol because i have custom recovery.
I flashed a "stock recovery" i downloaded using fastboot, same problem.
So, does anyone in the same circumstances have succided updating the firmware, antennas, etc?
Click to expand...
Click to collapse
extract all the .img files from the RUU zip and flash them one by one using fastboot. That should work.
Try to flash in this order (you must be unlocked again): boot, system & userdata. let it boot then access again fastboot and then flash recovery.
lets see what happens.
Thanks
Well I just solve the problem, i expect it help some people in the future.
I had tu relock it again using fastboot oem lock.
download the RUU exe format.
I couldn'y run the OS because relocked and I think the custom roms previously installed by myself messed something so I couldn't start "relocked"
So start the phone in Bootloader (holding down button).
Relock using fastboot oem lock
Once relocked run the RUU app on your computer (It wont read your actual firmware, antennas, etc... just tell you the ones it will update).
Follow the instructions and Voila, your are updated...
So the bottom lines are:
being locked (relocked) no matter what, and run the RUU app because it won't ask for the recovery image installed.
Thanks megabiteg I would like to try your method but my phone is already fixed.
What computer app you talkin about I need to update mine
Sent from my PG86100 using xda premium
search for this
It's like a RUU PC Version.
the one i used was named:
RUU_Shooter_S_Sprint_WWE_2.17.651.5_Radio_1.06.00.1216_NV_NV_spcs_1.42_release_233304_signed
Google it, i hope you'll find it.
I think WWE_2.17.651.5 is the lastest update, you could also apply an older version, just search for it.
Also follow my instruction, i couldn't get my phone updated with other method
I have directions for both the .exe & zip versions in the guide/flashing notes in my signature. Post 1.5
Sent from my PG86100 using Tapatalk
fcomeba said:
Well I just solve the problem, i expect it help some people in the future.
I had tu relock it again using fastboot oem lock.
download the RUU exe format.
I couldn'y run the OS because relocked and I think the custom roms previously installed by myself messed something so I couldn't start "relocked"
So start the phone in Bootloader (holding down button).
Relock using fastboot oem lock
Once relocked run the RUU app on your computer (It wont read your actual firmware, antennas, etc... just tell you the ones it will update).
Follow the instructions and Voila, your are updated...
So the bottom lines are:
being locked (relocked) no matter what, and run the RUU app because it won't ask for the recovery image installed.
Thanks megabiteg I would like to try your method but my phone is already fixed.
Click to expand...
Click to collapse
I am about to try this because I have been having the exact same problem. I have been trying to update my phone for the past 4 days and I am just about through with trying.
It worked! If any one else needs the .exe here is the link.
goo-inside.me/devs/zanzibar/Shooter/RUU_Shooter_S_Sprint_WWE_2.17.651.5_Radio_1.06.00.1216_NV_NV_spcs_1.42_release_233304_signed.exe
fcomeba said:
Well I just solve the problem, i expect it help some people in the future.
I had tu relock it again using fastboot oem lock.
download the RUU exe format.
I couldn'y run the OS because relocked and I think the custom roms previously installed by myself messed something so I couldn't start "relocked"
So start the phone in Bootloader (holding down button).
Relock using fastboot oem lock
Once relocked run the RUU app on your computer (It wont read your actual firmware, antennas, etc... just tell you the ones it will update).
Follow the instructions and Voila, your are updated...
So the bottom lines are:
being locked (relocked) no matter what, and run the RUU app because it won't ask for the recovery image installed.
Thanks megabiteg I would like to try your method but my phone is already fixed.
Click to expand...
Click to collapse
There's stickies on this you know.. could've saved yourself a lot of time.
G.Newton said:
There's stickies on this you know.. could've saved yourself a lot of time.
Click to expand...
Click to collapse
Yep, and the guide in my signature that I suggested has links to the stickied threads also.
Related
Hi, did a stupid thing and did the OTA update without reading the forum. The first update went through but after the 2nd big update, my phone is stuck at the white HTC screen. My phone is HTCdev unlocked and was on stock GB. My hboot version is
Unlocked
Vigor PUT Ship S-On RL
Hboot 2.11.0000
eMMC-boot
Oct 6 2011
I've looked through the forums for a solution and so far I taken the following steps
1) I have tried to reflash through the hboot using rezound_AndroidPolice_3.14.605.12_PH98IMG.zip, but it won't reflash. It goes through the loading processing but at the end I don't get the do you want to update promt. It just brings me back to the fastboot, recovery, factory reset etc menu
2) Then tried reflash to stock GB (http://forum.xda-developers.com/showthread.php?t=1812084), that update worked I think since after the loading screen, it asked if I wanted to update and I clicked yes. But after that, still stuck at the white HTC screen
3) Did factory reset twice, once through hboot and then another time at the Recovery mode, still doesn't work
So now I'm completely lost in how to get my phone back to working state again. Any advice??
Thanks in advance.
Is your bootloader still unlocked? You can't take a stock rom with an unlocked bootloader. You have to relock it first.
If you can get to Fastboot, run "fastboot oem lock"
shrike1978 said:
Is your bootloader still unlocked? You can't take a stock rom with an unlocked bootloader. You have to relock it first.
If you can get to Fastboot, run "fastboot oem lock"
Click to expand...
Click to collapse
I've seen reference to "Fastboo" and running command prompt, but I have no idea how that process works. Can you explain or provide links in how to do this?
Thanks
merfolk17 said:
I've seen reference to "Fastboo" and running command prompt, but I have no idea how that process works. Can you explain or provide links in how to do this?
Thanks
Click to expand...
Click to collapse
Download fast boot files press right click select run command over here then follow the command mentioned above
Make sure u have the stock recovery before relocking ur boot loader
Sent from my HTC One X using xda app-developers app
hasibzaman said:
Download fast boot files press right click select run command over here then follow the command mentioned above
Make sure u have the stock recovery before relocking ur boot loader
Sent from my HTC One X using xda app-developers app
Click to expand...
Click to collapse
I have the Andriod SDK installed, so can you clarify what exactly do I right click and also how can I check if I do have the stock recovery flashed?
I've figured out how to use fastboot, but when I connect by phone to my computer and run the lock command, it says its waiting for the device to connect. Any suggestions?
it means your PC did not recognise the phone in fastboot. install htc drivers (through HTC sync), connect phone to PC, reboot to bootloader and select fastboot. you can see it changes to fastboot usb
I'm on the same boat, but my phone was completely stock when I took the OTA.
I used this link to unlock my phone. You can use it as reference to relock it
http://www.theandroidsoul.com/how-to-unlock-htc-one-x-bootloader/
Hope this can help you, Cheers.
I'm struggling with all the terminology and methods with flashing. Basically I just wanted root, so I read several different guides and got a rooted status and managed to install the Amon Ra recovery. However my bootloader (also called HBOOT - is that correct?) shows tampered / unlocked now. Basically, I want to flash back to the most current build and try again.
Would the link on the Android Police forums to download RUU 4.03.605.2 be latest Verizon build as if it were fresh out of the box?
I checked on the wiki, but didn't see anything for the Rezound there.
Also, to use this utility, I relock my bootloader using HTCDev and then move this zipped file to my sd card and reboot to the bootloader either using adb or the power + volume down, correct? It will see the zip file and begin flashing or do I run an executable from my PC with the phone connected? I'm not S-Off because I figured that is way above my head at this point.
I appreciate any help anyone can offer.
The tampered just means you have a custom recovery like Amon Ra installed.
Sent from my ADR6425LVW using xda app-developers app
oatlord said:
I'm struggling with all the terminology and methods with flashing. Basically I just wanted root, so I read several different guides and got a rooted status and managed to install the Amon Ra recovery. However my bootloader (also called HBOOT - is that correct?) shows tampered / unlocked now. Basically, I want to flash back to the most current build and try again.
Would the link on the Android Police forums to download RUU 4.03.605.2 be latest Verizon build as if it were fresh out of the box?
I checked on the wiki, but didn't see anything for the Rezound there.
Also, to use this utility, I relock my bootloader using HTCDev and then move this zipped file to my sd card and reboot to the bootloader either using adb or the power + volume down, correct? It will see the zip file and begin flashing or do I run an executable from my PC with the phone connected? I'm not S-Off because I figured that is way above my head at this point.
I appreciate any help anyone can offer.
Click to expand...
Click to collapse
4.03.605..2 is the latest vzw build.
jbh00jh said:
4.03.605..2 is the latest vzw build.
Click to expand...
Click to collapse
If I want to load that RUU, do I have to relock my bootloader? Will I be able to load the file from the Android Police forum without being S-OFF since I've rooted and loaded a recovery?
oatlord said:
If I want to load that RUU, do I have to relock my bootloader? Will I be able to load the file from the Android Police forum without being S-OFF since I've rooted and loaded a recovery?
Click to expand...
Click to collapse
Having S-OFF negates the need to relock your bootloader.
You should be able to flash the "RUU" zip file with your phone in its current condition.
If you do some research in this section in the S-OFF threads, you'll get some good info about not re locking after s-off.
Re-locking is only necessary if you don't have s-off.
Sent from my ADR6425LVW using Tapatalk 2
to reinstall the RUU, first make sure you have fastboot on your PC and your phone is in the fastboot menu of the bootloader and connected to your PC. It should say "fastboot USB". (If you don't have the HTC drivers installed, download HTC Sync 3.0 and that should install it. I haven't gotten it to work on Windows 8 so if you use Windows 8 use these drivers)
Open a command prompt, change the directory to where your fastboot.exe is (example: cd c:\fastboot_directory). Type in 'fastboot oem lock'. Your phone will restart, then boot up. Turn it off, reboot to the bootloader and make sure it says *RELOCKED* on the top. Then, go back to fastboot and in your cmd window, type in 'fastboot oem rebootRUU'. Your phone will reboot and show a black screen with a grey HTC logo. Copy the RUU (doesn't matter if it's named PH98IMG.zip or something else) into the same folder as fastboot.exe and type in 'fastboot flash zip ruu_zip_name.zip' (obviously replacing ruu_zip_name.zip with the zip's actual name). The terminal will start sending the zip and details will be displayed on your computer screen. Your phone will also have a progress bar. Once the terminal on your computer says it's finished, you can reboot your phone.
I am currently S-On, unlocked, running Newts One XXX with the Global OTA (4.03.605) Sense 4 Kernel. I would now like to get the 4.03.605.2 firmware installed. Would the procedure described above work for my situation or is there another method I can use.
My next leap is to go S-off but for now I would just like to get the firmware updated before reflashing Newts.
Thanks in advance.
Yes, you can use the above method fine. However, going S-Off is very easy. It seems like a daunting task, but if you read the directions thoroughly it is very easy. I used the .5 version of Juopunutbear and it worked without a hitch. You are already unlocked and rooted, so if you S-Off, you won't have to do it all over again. From there you can flash the RUU, flash a FLASHABLE version of AR 3.15, then reflash any rom that you want. You will only get the benefit from global with roms that are built aroung the .2 base, but you will get updated radios. I haven't honestly noticed much of a difference with the new radios though.
layneja said:
I am currently S-On, unlocked, running Newts One XXX with the Global OTA (4.03.605) Sense 4 Kernel. I would now like to get the 4.03.605.2 firmware installed. Would the procedure described above work for my situation or is there another method I can use.
My next leap is to go S-off but for now I would just like to get the firmware updated before reflashing Newts.
Thanks in advance.
Click to expand...
Click to collapse
Flash stock recovery here's a link http://www.mediafire.com/?wb21d2gdurui2c6 then lock bootloader. (Fastboot OEM lock)
After locking bootloader(cuz your s-on) rename the ruu you downloaded from android police To PH98IMG put on your sd return sd phone boot into bootloader run update, if it stops and powers off mid update remove battery and start it again, It flashed the hboot first then you gotta go back In And finish the update.
sent from my s-on reZound rockin viperRez Rom on latest ICS firmware
---------- Post added at 11:41 AM ---------- Previous post was at 10:59 AM ----------
layneja said:
I am currently S-On, unlocked, running Newts One XXX with the Global OTA (4.03.605) Sense 4 Kernel. I would now like to get the 4.03.605.2 firmware installed. Would the procedure described above work for my situation or is there another method I can use.
My next leap is to go S-off but for now I would just like to get the firmware updated before reflashing Newts.
Thanks in advance.
Click to expand...
Click to collapse
Also to avoid any problems do a factory reset in hboot after update is installed. Being that we're s-on when we re-unlock it does it for us but I've heard some people are having problems after the ruu if they didn't FDR while on stock recovery.. just a heads up
sent from my s-on reZound rockin viperRez Rom on latest ICS firmware
famouscollin said:
Flash stock recovery here's a link (removed cause I'm too new) then lock bootloader. (Fastboot OEM lock)
After locking bootloader(cuz your s-on) rename the ruu you downloaded from android police To PH98IMG put on your sd return sd phone boot into bootloader run update, if it stops and powers off mid update remove battery and start it again, It flashed the hboot first then you gotta go back In And finish the update.
sent from my s-on reZound rockin viperRez Rom on latest ICS firmware
---------- Post added at 11:41 AM ---------- Previous post was at 10:59 AM ----------
Also to avoid any problems do a factory reset in hboot after update is installed. Being that we're s-on when we re-unlock it does it for us but I've heard some people are having problems after the ruu if they didn't FDR while on stock recovery.. just a heads up
sent from my s-on reZound rockin viperRez Rom on latest ICS firmware
Click to expand...
Click to collapse
Just to clarify: when you reboot using "adb reboot" or power + volume down, are you booting into the bootloader or hboot? I've read the guides but still a little confused there.
Also, what does the stock recovery do versus something like Amon Ra? Does the stock recovery allow for creating backups and what-not? Sorry to be a total noob here. I can bake cookies or something for you all for your help, hehe.
WookieFan said:
Having S-OFF negates the need to relock your bootloader.
You should be able to flash the "RUU" zip file with your phone in its current condition.
If you do some research in this section in the S-OFF threads, you'll get some good info about not re locking after s-off.
Re-locking is only necessary if you don't have s-off.
Sent from my ADR6425LVW using Tapatalk 2
Click to expand...
Click to collapse
if you're s-off you shouldn't have to unlock.
---------- Post added at 07:17 PM ---------- Previous post was at 07:11 PM ----------
oatlord said:
Just to clarify: when you reboot using "adb reboot" or power + volume down, are you booting into the bootloader or hboot? I've read the guides but still a little confused there.
Also, what does the stock recovery do versus something like Amon Ra? Does the stock recovery allow for creating backups and what-not? Sorry to be a total noob here. I can bake cookies or something for you all for your help, hehe.
Click to expand...
Click to collapse
The bootloader is the hboot. You power on holding vol down to get there.
The stock recovery does not allow you to create backups, or do much at all I'm pretty sure. That is why we have custom ones.
If i helped throw me a thanks
iamwalterwhite said:
Yes, you can use the above method fine. However, going S-Off is very easy. It seems like a daunting task, but if you read the directions thoroughly it is very easy. I used the .5 version of Juopunutbear and it worked without a hitch. You are already unlocked and rooted, so if you S-Off, you won't have to do it all over again. From there you can flash the RUU, flash a FLASHABLE version of AR 3.15, then reflash any rom that you want. You will only get the benefit from global with roms that are built aroung the .2 base, but you will get updated radios. I haven't honestly noticed much of a difference with the new radios though.
Click to expand...
Click to collapse
Do you mean flash the RUU in the bootloader and then the recovery also in bootloader? i only ask cause im at school and i forgot my microsd adapter so i cant rename the zips so that I can flash both of them from there, but if i can do it from recovery then im set
xxtsxx said:
Do you mean flash the RUU in the bootloader and then the recovery also in bootloader? i only ask cause im at school and i forgot my microsd adapter so i cant rename the zips so that I can flash both of them from there, but if i can do it from recovery then im set
Click to expand...
Click to collapse
Sorry that you never got an answer to this. Yes, you should flash both recovery (stock) and the RUU as PH98IMG zip files. Wait to start this process until you have a pc/sd card reader available. Trying this without those basic tools is going to make this a frustrating process for you.
Sent from my ADR6425LVW using Tapatalk 2
I bought Evo which was already upgraded to ICS (OTA I assume), and it was branded I think. I've unlocked it via HTCDev, flashed '4ext touch recovery' and then rooted. Then I flashed MIUI ICS ROM, and everything is OK for now.
I want to use BootManager to flash multiple ROMs. It requires s-off. I tried it already with s-on, because I've read that SmartFlash (from 4ext recovery) makes my phone like s-off, so ROM on SD card installed, but won't boot. I had many problems going back to my Phone ROM, I restored my backup, wiped many times, installed fresh ROM and still had a bootloop. Finally I got it working again by flashing boot.img via fastboot (glad I did nandroid backup before). I didn't try again with different ROM, because after 2 hours of trying to recover my base ROM I've had enough. So I'm pretty sure BootManager will work better if my phone will be s-off.
So my question is - what to do next? We have so many guides and different comments here, sometimes the same method works for one, and doesn't work for another one, and I'm really confused.
I assume I should follow the instructions here http://forum.xda-developers.com/showthread.php?t=1743466 but I don't understand few things:
friend.evil said:
flash an ICS ROM from recovery(Method B from 10 to 14)
open ICS ROM.zip and extract boot.img to a folder which contains adb, fastboot and AdbWinApi.dll
go to fastboot and type:
fastboot flash boot boot.img
fastboot reboot
Click to expand...
Click to collapse
Do I have to do this if I'm already have MIUI with root privileges? Do I still need that boot.img from MIUI, and put it together with fastboot.exe?
Or should I restore stock ICS? I'm pretty sure I did nandroid backup before flashing MIUI.
friend.evil said:
12_Notice when you s-off the phone the hboot is corrupted i advice after s-off to follow the methods In E_(from 1 to 4)
Click to expand...
Click to collapse
Do I need to fix hboot after s-off? What hboot version I have after doing steps 1 to 4 from section E? There's a big zip file (PG86IMG.zip), is it another ROM or what?
And most important question - if method D doesn't work, method F is recommended, but:
elias17 said:
Hboot s on will only flash roms that are based on ics 3.28xx and sense 4 roms using a special boot.img ! U can never flash GB roms until u go s off like i did its a tricky process but it works and now i can flash any rom in the gsm section
Click to expand...
Click to collapse
friend.evil said:
2_flash Leedroid GB ROM from recovery http://leedroid.ftp.rshost.eu/Shoote....zip(Don't forget to wipe data/factory reset and wipe cache + dalvik)
Click to expand...
Click to collapse
I don't get it - can I flash GB ROM or not if I have hboot 1.53.0007 s-on? Can I use method F if method D fail?
Sorry for my english, I'm from Poland.
Thanks in advance for any tip.
You're confusing yourself, What you need to do my friend is.
1. Download RUU, Run RUU
2. HTC Unlock bootloader again
3. Do the Juopunutbear Wiretrick to get s-off
4. Download the 1.04 ENG hboot (There is one of those for the GSM I think... not sure though)
5. Flash a badass Android 4.2.1 rom. They work.
There's much more detailed guides on what to do, BUT This is a summary of what you want.
Be sure to hit thanks [= I'm almost to 100
Which RUU should I search for? GB or ICS?
But isn't the 1+2 the same as restoring my ICS Stock ROM from backup?
I think hboot 1.49.0007 would be enough, I've read that BootManager works well with that version.
1. Yes you can just restore your stock ics backup BUT you will have to root it using the file provided in method B.
2. Yes the 1.49.0007 hboot is best for gsm
3. You can flash a GB rom with your hboot no problem. It just dont think it will boot. so technically you should be able to do the wire trick with a GB rom flashed(not booted into). You'll be in fastboot mode for the wiretrick. There are different files for GB and ICS when doing the wiretrick
Your best bet is to run an ICS RUU, unlock bootloader, root rom, do the wire trick, change hboot to 1.49.0007 and then flash any rom you want
Backup was made right after I made root, is it enough? I just don't want to go through the entire process from the beginning (unlocking, rooting etc).
mars28 said:
Backup was made right after I made root, is it enough? I just don't want to go through the entire process from the beginning (unlocking, rooting etc).
Click to expand...
Click to collapse
That should work But unlocking again is really easy
You should still have you unlock token in the same place,
You just plug up to the computer hop into fastboot usb and type
Fastboot flash unlocktoken Unlock_Code.bin
to unlock and then
fastboot flash recovery recovery.img
for a recovery,
Then move SU to your sd card and flash it in recovery.
Then your all ready for the wire trick, The more you do these things the more experience you get at them and the better you get with fastboot. I suggest you go through the process opposed to just restoring (First off it's much much safer) and you'll know the ropes if you (or anyone else) has this problem.
Maybe you're right. I'll try with RUU. But I see it's hard to find the correct one these days, some old links died. I have a file called "RUU_SHOOTER_U_ICS_35_S_HTC_Europe_3.28.401.1_Radio_11.77.3504.00U_11.25.3504.06_M_release_262714_signed" which I have downloaded right before I started unlocking my Evo, could it be the correct one?
I didn't know I can use old "unlock_code.bin", I saw that everytime I read the token from the device, it was different. So I assumed that I have to flash bin that match the token.
mars28 said:
Maybe you're right. I'll try with RUU. But I see it's hard to find the correct one these days, some old links died. I have a file called "RUU_SHOOTER_U_ICS_35_S_HTC_Europe_3.28.401.1_Radio_11.77.3504.00U_11.25.3504.06_M_release_262714_signed" which I have downloaded right before I started unlocking my Evo, could it be the correct one?
I didn't know I can use old "unlock_code.bin", I saw that everytime I read the token from the device, it was different. So I assumed that I have to flash bin that match the token.
Click to expand...
Click to collapse
The token and the unlock code are specific to the phone, And doesn't change until you get a new phone.
And that seems to be the right one, Do you live in Europe? lol Shooter u means GSM and ICS means it's the latest RUU.
mars28 said:
Maybe you're right. I'll try with RUU. But I see it's hard to find the correct one these days, some old links died. I have a file called "RUU_SHOOTER_U_ICS_35_S_HTC_Europe_3.28.401.1_Radio_11.77.3504.00U_11.25.3504.06_M_release_262714_signed" which I have downloaded right before I started unlocking my Evo, could it be the correct one?
I didn't know I can use old "unlock_code.bin", I saw that everytime I read the token from the device, it was different. So I assumed that I have to flash bin that match the token.
Click to expand...
Click to collapse
you can easily get a new token from htc dev web site
Sent from my HTC EVO 3D X515m using xda app-developers app
Can't_Live_Without_My_Evo said:
And that seems to be the right one, Do you live in Europe? lol Shooter u means GSM and ICS means it's the latest RUU.
Click to expand...
Click to collapse
I know I use shooter_u, I asked because I've found another RUU which have "Rogers_WWE" in name of the file, and the rest of the file name is identical, and I remember that I had to choose "rogers" when I was unlocking via htcdev. That's why I wasn't 100% sure if I had to choose "HTC_Europe" or "Rogers_WWE".
Another thing which confuses me:
http://forum.xda-developers.com/showthread.php?t=1495358
mpgrimm2 said:
Note 3: If you previously did the HTC Unlock, you'd have to "RELOCK" BEFORE running the RUU.
To do this from fastboot type: fastboot oem lock
Click to expand...
Click to collapse
Should I do this or start directly with RUU.exe? My phone is currently "UNLOCKED, hboot 1.53.0007, s-on".
And what about CID? I've read somewhere that I have to change to supercid or something, to be able to flash zips via fastboot. How to check my current CID?
Search for cid getter on play store to get your cid
You certainly need to relock you hboot before running RUU. For the correct ruu you should check the box that your phone came in. It should have the details (atleast i think so)
P.S. you probably don't need to change cid. Infact i'd recommend you not to do that just yet
Got the CID, it's HTC__032. I want to be prepared, who knows what might come up during the whole process.
friend.evil said:
12_Notice when you s-off the phone the hboot is corrupted i advice after s-off to follow the methods In E_(from 1 to 4)
Click to expand...
Click to collapse
What means "corrupted"? Phone won't boot or what?
Eeh, if I knew that hboot 1.53.x is so problematic, I would buy Evo with GB on-board.
mars28 said:
Got the CID, it's HTC__032. I want to be prepared, who knows what might come up during the whole process.
What means "corrupted"? Phone won't boot or what?
Eeh, if I knew that hboot 1.53.x is so problematic, I would buy Evo with GB on-board.
Click to expand...
Click to collapse
I think yours might be an european model. i had the exact same cid as yours.
when you get to that step of corrupted hboot just follow the steps on this thread and flash hboot 1.49.0007
http://forum.xda-developers.com/showthread.php?t=1906172
Cant kive without my evis comments about the wire trick are bang on. It will fix everything. Having s-off is just much easier so do the wire trick. It will work. My wife and I both have an evo. I had to do the wire trick twice on hers for it to work and four times on mine for it to work. Be patient if it fails the first few times. And if the screen gets stuck on the jounuo whatever screen you can fix that.
If you are stuck at Juopunutbear screen and if you can go to bootloader you need to connect the phone to pc, go to fastboot ( should say fastboot usb)*Go to controlbear folder (from where you ran controlbear to begin withon you pc then open command window in it (hold shift and right click, that willopen command window rigjt there and then*when you get into it you need to enter:
"ControlBear.exe -f" no quotes or "ControlBear f" notice the space after the exe !
Lots of peopke forget to put it in and say it didnt work.
I presume this will fix the problem
Sent from my SAMSUNG-SGH-I317 using xda app-developers app
My phone is now s-off. I didn't flash RUU, just restored stock rooted ROM from backup, did the wire trick (just one time, surprisingly) and everything went nice and smooth. Then I flashed hboot 1.49.0007 with no problems at all. Thanks guys for the tips.
One more thing - my phone state is now "LOCKED" - should I bother?
So I got what I wanted - I've installed ROM in BootManager (the one which doesn't boot before, while phone was 's-on') and this time it booted from SD. Today I'll try more ROMs in BootManager.
Locked doesn't matter as long as you are s-off. It only creates problems if you ever plan on using fastboot commands. Trust me, you dont need to bother with it
But if you really want to know heres a quote from ramjet where he explains it a bit.
ramjet73 said:
Once the RUU.exe is run and the stock bootloader is installed, the phone will be bootloader S-ON regardless of the radio S-OFF status. To run fastboot commands like "flash" and "erase" the stock bootloader needs to be unlocked by the htcdev method or a custom bootloader modified to support those commands needs to be flashed, which requires radio S-OFF.
Click to expand...
Click to collapse
I was given a phone to try to resurrect from the dead. It powers on directly to the bootloader screen and does no more. I really know nothing about this phone model. Before I start, I want to know if it is even possible. The screen says the following:
*** LOCKED ***
SHOOTER XC SHIP S-ON RL
HBOOT-1.57.0000
eMMC-boot
Apr 20 2012, 17:39:22
And then there are the normal bootloader options. Can this thing be saved?
silenthatred said:
I was given a phone to try to resurrect from the dead. It powers on directly to the bootloader screen and does no more. I really know nothing about this phone model. Before I start, I want to know if it is even possible. The screen says the following:
*** LOCKED ***
SHOOTER XC SHIP S-ON RL
HBOOT-1.57.0000
eMMC-boot
Apr 20 2012, 17:39:22
And then there are the normal bootloader options. Can this thing be saved?
Click to expand...
Click to collapse
if you can get to the bootloader screen and access the fastboot selection,plug it into a computer and get it to read fastbootusb then its fixable,first find your token and unlock the bootloader, then from there install a custom recovery , next copy the stock ROM over to your sdcard and boot into recovery... select install zip from sdcard and guide yourself to where the file is located ,select it and let it install... from there it should be able to reboot and boot up into the ROM
wloftus said:
if you can get to the bootloader screen and access the fastboot selection,plug it into a computer and get it to read fastbootusb then its fixable,first find your token and unlock the bootloader, then from there install a custom recovery , next copy the stock ROM over to your sdcard and boot into recovery... select install zip from sdcard and guide yourself to where the file is located ,select it and let it install... from there it should be able to reboot and boot up into the ROM
Click to expand...
Click to collapse
Thanks, it does show fastboot usb...find your token? Not sure what that means. I'll search around a bit when I get home. My original Evo 4G I did root, but don't remember that part.
silenthatred said:
Thanks, it does show fastboot usb...find your token? Not sure what that means. I'll search around a bit when I get home. My original Evo 4G I did root, but don't remember that part.
Click to expand...
Click to collapse
You don't need to unlock the bootloader to fix it, and you shouldn't unlock it anyways, until you have it fully booted properly.
Run the RUU EXE from a PC for the 3.28 update (or whatever the later version is) while the phone is connected via fastboot USB mode, it will re-flash the ROM and should boot properly then.
Unknownforce said:
You don't need to unlock the bootloader to fix it, and you shouldn't unlock it anyways, until you have it fully booted properly.
Run the RUU EXE from a PC for the 3.28 update (or whatever the later version is) while the phone is connected via fastboot USB mode, it will re-flash the ROM and should boot properly then.
Click to expand...
Click to collapse
RUU.EXE finds it and then gets to the restarting into bootloader step and the phone restarts. Then it just saying waiting for bootloader until it times out, but the bootloader is up on the phone.
silenthatred said:
RUU.EXE finds it and then gets to the restarting into bootloader step and the phone restarts. Then it just saying waiting for bootloader until it times out, but the bootloader is up on the phone.
Click to expand...
Click to collapse
This happens sometimes if you have a custom bootloader installed when you flash the RUU. Just cancel the Windows task and restart it and you should be fine.
ramjet73
wloftus said:
if you can get to the bootloader screen and access the fastboot selection,plug it into a computer and get it to read fastbootusb then its fixable,first find your token and unlock the bootloader, then from there install a custom recovery , next copy the stock ROM over to your sdcard and boot into recovery... select install zip from sdcard and guide yourself to where the file is located ,select it and let it install... from there it should be able to reboot and boot up into the ROM
Click to expand...
Click to collapse
Unknownforce said:
You don't need to unlock the bootloader to fix it, and you shouldn't unlock it anyways, until you have it fully booted properly.
Run the RUU EXE from a PC for the 3.28 update (or whatever the later version is) while the phone is connected via fastboot USB mode, it will re-flash the ROM and should boot properly then.
Click to expand...
Click to collapse
Couple things since I have looked into this a little more. Despite it saying Sprint on the front, it is a Virgin Mobile phone. It has the OTA that came down on it, so I can't flash the older RUU. It says it is an older version. So it looks like unlocking the bootloader is my only option? Question is, how do I do that from the bootloader? I was able to get the token and have the unlock_code.bin file, but the instructions to flash it seem to rely on having a working ROM to complete it, which I don't have. The phone is stuck in a bootloader loop. S-OFF, I have the answer. But it is S-ON, so not sure what to do.
silenthatred said:
Couple things since I have looked into this a little more. Despite it saying Sprint on the front, it is a Virgin Mobile phone. It has the OTA that came down on it, so I can't flash the older RUU. It says it is an older version. So it looks like unlocking the bootloader is my only option? Question is, how do I do that from the bootloader? I was able to get the token and have the unlock_code.bin file, but the instructions to flash it seem to rely on having a working ROM to complete it, which I don't have. The phone is stuck in a bootloader loop. S-OFF, I have the answer. But it is S-ON, so not sure what to do.
Click to expand...
Click to collapse
You are right that the Virgin Mobile RUU can't be flashed when S-ON and the OTA has been installed unless you can flash a zip to downgrade your main version (mainver) and you have to be unlocked and rooted to do that.
The unlock_code.bin file is flashed via fastboot USB mode so it might work, but if you've tried that and it doesn't you may be able to use unknownforce's hboot downgrade method to get straight to S-OFF. I don't know of anyone that's done it on an Evo V 4G but it might work if you use the RUU zip file for that model.
ramjet73
ramjet73 said:
You are right that the Virgin Mobile RUU can't be flashed when S-ON and the OTA has been installed unless you can flash a zip to downgrade your main version (mainver) and you have to be unlocked and rooted to do that.
The unlock_code.bin file is flashed via fastboot USB mode so it might work, but if you've tried that and it doesn't you may be able to use unknownforce's hboot downgrade method to get straight to S-OFF. I don't know of anyone that's done it on an Evo V 4G but it might work if you use the RUU zip file for that model.
ramjet73
Click to expand...
Click to collapse
It flashes unlock_code.bin to the phone successfully, but the next steps say to click yes on the screen to unlock on the phone. Can't access that without a working ROM. I'll try unknownforce's method when I get home, thanks for the help!
ramjet73 said:
You are right that the Virgin Mobile RUU can't be flashed when S-ON and the OTA has been installed unless you can flash a zip to downgrade your main version (mainver) and you have to be unlocked and rooted to do that.
Click to expand...
Click to collapse
Why is this? Is there not a full RUU for the latest version?
ramjet73 said:
The unlock_code.bin file is flashed via fastboot USB mode so it might work, but if you've tried that and it doesn't you may be able to use unknownforce's hboot downgrade method to get straight to S-OFF. I don't know of anyone that's done it on an Evo V 4G but it might work if you use the RUU zip file for that model.
ramjet73
Click to expand...
Click to collapse
You still have to brick the device for this and I haven't been able to brick it without using a full RUU flash, which he apparently can't do?
silenthatred said:
It flashes unlock_code.bin to the phone successfully, but the next steps say to click yes on the screen to unlock on the phone. Can't access that without a working ROM. I'll try unknownforce's method when I get home, thanks for the help!
Click to expand...
Click to collapse
Does it still say ** LOCKED ** Or does it say ** UNLOCKED ** now?
Unknownforce said:
Why is this? Is there not a full RUU for the latest version?
Click to expand...
Click to collapse
No. Virgin Mobile released an OTA update in November but there's no RUU that corresponds to it available yet. Fortunately, the bootloader version didn't change so the original RUU can be flashed with S-ON if the mainver is set low, but you need to be unlocked and rooted already to flash the zip file that does that.
You still have to brick the device for this and I haven't been able to brick it without using a full RUU flash, which he apparently can't do?
Click to expand...
Click to collapse
That would be a problem for him then. I don't know of anyway to flash the RUU with S-ON after the OTA has been installed if the bootloader is actually locked and he can't unlock it.
ramjet73
Yeah, not looking good. Thanks for the help though!
Semi-noob here, would appreciate any help!
S-Off using revone, flashed CWM, and then ROM'd. Found an issue with the phone (wireless charger not working), so need to return to stock before bringing to Verizon. Used adb to S-On, and now, I am STUCK in Fastboot (or is it called Hboot?)!
None of the "options in Fastboot do anything (Bootloader, Reboot, Reboot Bootloader, Factory Reset). I can't get anywhere past Fastboot!
I think my problem was that I did not flash the stock ROM first, before S-on again. The phone no longer goes into Bootloader, so I don't know how to flash a ROM at this point.
Any help would be majorly appreciated! Thank you, oh wise ones...
geeDoh said:
Semi-noob here, would appreciate any help!
S-Off using revone, flashed CWM, and then ROM'd. Found an issue with the phone (wireless charger not working), so need to return to stock before bringing to Verizon. Used adb to S-On, and now, I am STUCK in Fastboot (or is it called Hboot?)!
None of the "options in Fastboot do anything (Bootloader, Reboot, Reboot Bootloader, Factory Reset). I can't get anywhere past Fastboot!
I think my problem was that I did not flash the stock ROM first, before S-on again. The phone no longer goes into Bootloader, so I don't know how to flash a ROM at this point.
Any help would be majorly appreciated! Thank you, oh wise ones...
Click to expand...
Click to collapse
The good news is, if you really are stuck in fastboot, you can still use adb/fastboot commands to get your phone working again. There is an important distinction between fastboot and hboot, though: fastboot is basically the bootloader's "debug" mode, while hboot is the regular bootloader mode. You won't be able to do much if your bootloader says "hboot" above the available options, but if it says "fastboot" or "fastboot usb" you're fine.
You should try to get s-off again (assuming you haven't relocked your bootloader) either via revone or facepalm, then flash a stock rom and proceed from there.
Clarification: if you have relocked your bootloader, unlock, then get s-off.
Used adb to S-On? Meaning what exactly? Did you lock beforehand?
I currently have S-on. I used revone's method to S-off.
I think the problem is that I have relocked the bootloader (phone shows LOCKED) with a custom ROM installed. I think I should have flashed a stock ROM before relocking. Would this have caused the problem I'm having?
I am not sure how to get S-off again, because I am stuck on the FASTBOOT. Selecting Bootloader/Reboot/Reboot Bootloader just returns me to the same screen. When I try to enter any line items (in Terminal), adb says there are no devices connected (this is probably due to the fact that my phone no longer boots to the homescreen). Any suggestions of how to get S-off again??
Thanks...
What method did you use for S-ON? There are guides here that lay out every step needed to return to stock.
Also when in fastboot, you need to use fastboot, not adb. Type in fastboot devices. Does your device ID show?
I would suggest trying to run the RUU. Although it may not work depending on HBOOT version and the fact you are now S-ON.
Can you boot into Recovery? If so, is there a ROM still on the phone? If so, try flashing it...
geeDoh said:
I currently have S-on. I used revone's method to S-off.
I think the problem is that I have relocked the bootloader (phone shows LOCKED) with a custom ROM installed. I think I should have flashed a stock ROM before relocking. Would this have caused the problem I'm having?
I am not sure how to get S-off again, because I am stuck on the FASTBOOT. Selecting Bootloader/Reboot/Reboot Bootloader just returns me to the same screen. When I try to enter any line items (in Terminal), adb says there are no devices connected (this is probably due to the fact that my phone no longer boots to the homescreen). Any suggestions of how to get S-off again??
Thanks...
Click to expand...
Click to collapse
Does the unit show up in device manager? You may need to install a driver.
Phaded said:
What method did you use for S-ON? There are guides here that lay out every step needed to return to stock.
Also when in fastboot, you need to use fastboot, not adb. Type in fastboot devices. Does your device ID show?
I would suggest trying to run the RUU. Although it may not work depending on HBOOT version and the fact you are now S-ON.
Can you boot into Recovery? If so, is there a ROM still on the phone? If so, try flashing it...
Click to expand...
Click to collapse
Oh, using Fastboot gave me my device ID. What can I do now??
I can't get into Recovery from Fastboot USB. The option for Bootloader and Reboot Bootloader are there, but selecting them just returns me to Fastboot USB. I assume this is because I am already S-On again...?
geeDoh said:
Oh, using Fastboot gave me my device ID. What can I do now??
I can't get into Recovery from Fastboot USB. The option for Bootloader and Reboot Bootloader are there, but selecting them just returns me to Fastboot USB. I assume this is because I am already S-On again...?
Click to expand...
Click to collapse
Select bootloader, then recovery. The menus look the same, but they are different.
If you can boot into recovery, what is it? Stock or custom?
Phaded said:
Select bootloader, then recovery. The menus look the same, but they are different.
If you can boot into recovery, what is it? Stock or custom?
Click to expand...
Click to collapse
When I select Bootloader -> Recovery, the HTC screen flashes, then I'm returned to Fastboot USB.
geeDoh said:
When I select Bootloader -> Recovery, the HTC screen flashes, then I'm returned to Fastboot USB.
Click to expand...
Click to collapse
That's because you have unsigned boot.img and/or recovery and relocked the device.
You need to RUU or unlock again to boot to anything.
Any tips on how to unlock again? (and once I am unlocked, i assume I need to load Recovery, and from there, flash a stock ROM?)
geeDoh said:
Any tips on how to unlock again? (and once I am unlocked, i assume I need to load Recovery, and from there, flash a stock ROM?)
Click to expand...
Click to collapse
Run Moonshine.
If that fails, RUU to stock.
You didn't happen to make an unlock_code.bin with htc did you?
No, i didn't. Not even sure what that is...haha...
I'm going to run RUU, and hope that works! Thanks for everyones input...
still no luck! =T
So, I've tried running RUU (this is the RUU file I'm using: RUU_DLX_WL_JB_45_VERIZON_WWE_1.15.605.4_Radio_1.00.00.1023_3_NV_VZW_1.98_002_release_290923_signed), but after it runs for a while (it says it is erasing data, then sending to the phone),
RUU says I am currently on 2.06, so is this the correct RUU file?
Another option for me, other than putting the phone back to stock, is for me to completely brick it. I tried unplugging and powering off the phone while RUU was running, but it still comes back to Fastboot. Suggestions?
Thanks again....
geeDoh said:
So, I've tried running RUU (this is the RUU file I'm using: RUU_DLX_WL_JB_45_VERIZON_WWE_1.15.605.4_Radio_1.00.00.1023_3_NV_VZW_1.98_002_release_290923_signed), but after it runs for a while (it says it is erasing data, then sending to the phone),
RUU says I am currently on 2.06, so is this the correct RUU file?
Another option for me, other than putting the phone back to stock, is for me to completely brick it. I tried unplugging and powering off the phone while RUU was running, but it still comes back to Fastboot. Suggestions?
Thanks again....
Click to expand...
Click to collapse
Just run the RUU. There is only one RUU. You are on 2.06, that's why it tells you that. Let the whole thing run.
You cannot downgrade via RUU. You need to unlock the phone, s-off it (facepalm should suffice) then you can RUU back to 1.15 if you choose.
beaups said:
You cannot downgrade via RUU. You need to unlock the phone, s-off it (facepalm should suffice) then you can RUU back to 1.15 if you choose.
Click to expand...
Click to collapse
Ah forgot he went back to S-On.
Phaded said:
Ah forgot he went back to S-On.
Click to expand...
Click to collapse
I have the same problem. Since it was relocked, the htc dev site can't give the bin file to unlock it again. So I'm stuck in fastboot usb mode and I can't do anything about it. If only I can unlock it again, then I can move on from there.
okyere said:
I have the same problem. Since it was relocked, the htc dev site can't give the bin file to unlock it again. So I'm stuck in fastboot usb mode and I can't do anything about it. If only I can unlock it again, then I can move on from there.
Click to expand...
Click to collapse
Still have the token? Or the email that it got sent in?