I'm trying to get my 1.58Hboot phone over to S-Off so i can downgrade my hboot easily to try out some more interesting roms. I have the steps and guides to get this done, but it requires me to have a stock rom. i have a stock rooted odex rom but it says it has to be plain stock.
So i feel like i've tried alot of things to try to get this stock rom:
RUU files
PG86IMG.zip files
Which all failed to do anything... is there anyway to get this done easy like maybe just flash something with 4ext?
Any help would be much appreciated, thanks.
akin175 said:
Which all failed to do anything... is there anyway to get this done easy like maybe just flash something with 4ext?
Any help would be much appreciated, thanks.
Click to expand...
Click to collapse
How did they fail? What error messages did you get?
The zip version of the RUU should flash from the bootloader even if you are S-ON.
ramjet73
ramjet73 said:
How did they fail? What error messages did you get?
The zip version of the RUU should flash from the bootloader even if you are S-ON.
ramjet73
Click to expand...
Click to collapse
I don't get any errors on those, my bootloader finds the zip it parses the file then does nothing with it, it just goes back to the main directory screen.
The Ruu.exe file says updating form image 2.89.651.2 to 289.651.2 then it takes my screen to the "HTC" screen and it says "sending" but then gives me ERROR 155 UNKNOWN ERROR
akin175 said:
I don't get any errors on those, my bootloader finds the zip it parses the file then does nothing with it, it just goes back to the main directory screen.
The Ruu.exe file says updating form image 2.89.651.2 to 289.651.2 then it takes my screen to the "HTC" screen and it says "sending" but then gives me ERROR 155 UNKNOWN ERROR
Click to expand...
Click to collapse
Have you relocked your bootloader before attempting to flash the RUU?
Try issuing the following fastboot commands and post the output here:
fastboot getvar cid
fastboot getvar mainver
ramjet73
ramjet73 said:
Have you relocked your bootloader before attempting to flash the RUU?
Try issuing the following fastboot commands and post the output here:
fastboot getvar cid
fastboot getvar mainver
ramjet73
Click to expand...
Click to collapse
No i havn't, i thought it had to be unlocked to flash anything.
I'm not 100% sure where you me to issue these commands, i've only really used ADB to unlock my phone.
akin175 said:
No i havn't, i thought it had to be unlocked to flash anything.
I'm not 100% sure where you me to issue these commands, i've only really used ADB to unlock my phone.
Click to expand...
Click to collapse
You had to use fastboot to flash the unlock token and your custom recovery. It's in the same directory as ADB.
Since you didn't relock your bootloader you could start with Step1 in this guide and it has everything you need to get to S-OFF.
ramjet73
ramjet73 said:
You had to use fastboot to flash the unlock token and your custom recovery. It's in the same directory as ADB.
Since you didn't relock your bootloader you could start with Step1 in this guide and it has everything you need to get to S-OFF.
ramjet73
Click to expand...
Click to collapse
I figured it out while after i posted that and now feel dumb for posting that.
c:\>cd adb
c:\ADB>fastboot getvar cid
cid: SPCS_001
finished. total time: 0.000s
c:\ADB> fastboot getvar mainver
mainver: 2.89.651.2
finished. total time: 0.010s
c:\ADB>
ramjet73 said:
You had to use fastboot to flash the unlock token and your custom recovery. It's in the same directory as ADB.
Since you didn't relock your bootloader you could start with Step1 in this guide and it has everything you need to get to S-OFF.
ramjet73
Click to expand...
Click to collapse
I checked out your link and it's the wire trick way like i wanted to do, so i'll be following it set by step, thank you very much i really appreciate your time .
akin175 said:
cid: SPCS_001
mainver: 2.89.651.2
Click to expand...
Click to collapse
OK, you're good to go.
Just follow the guide and you should be able to get S-OFF.
ramjet73
Related
Tried following the instructions on this site to flash the latest HTC firmware and I could not install it from 4EXT. Renamed the file to PG86IMG.zip and flashed it from fastboot but hit an error. Tried to run the RUU for my radio version and every single one has hit an error (Update Failed! Main Version is older!).
The phone was originally HBOOT 1.40 S-OFF but it is now HBOOT 1.57 with s-on (which I did). I want to return the phone back to stock and start fresh but I really don't know how. Can I return back to HBOOT 1.40 or do I have to flash to the latest 1.50 and downgrade?
I'm really stumped by this one and any help would be greatly appreciated.
I'm as new to the forums as you, but I did a little messing and reading around. In order to return your phone to the same way you bought it, you need to downgrade hboot to version 1.4 and then run the RUU.exe of your firmware version (I'm not sure which version it is for your phone, it was 2.17.651.5 for me but I got my phone with hboot 1.5). The downgrade thread is here [it's very tricky to brick it, make sure the light is a solid faint red (NOT BLINKING) in order to do it successfully]. Hopefully someone else can tell you which RUU version to use (to run before the downgrade if you get the *Security Warning* in hboot, as well as the one to use after in order to return to the way you were when you got the phone). I just downloaded all the RUU's and ran them all until one worked.
LesbianSeagull said:
Tried following the instructions on this site to flash the latest HTC firmware and I could not install it from 4EXT. Renamed the file to PG86IMG.zip and flashed it from fastboot but hit an error. Tried to run the RUU for my radio version and every single one has hit an error (Update Failed! Main Version is older!).
The phone was originally HBOOT 1.40 S-OFF but it is now HBOOT 1.57 with s-on (which I did). I want to return the phone back to stock and start fresh but I really don't know how. Can I return back to HBOOT 1.40 or do I have to flash to the latest 1.50 and downgrade?
I'm really stumped by this one and any help would be greatly appreciated.
Click to expand...
Click to collapse
Hi, did you unlock and root your phone using the HTC method?
If so I think I may be able to help.
koty2012 said:
Hi, did you unlock and root your phone using the HTC method?
If so I think I may be able to help.
Click to expand...
Click to collapse
I think it was the Revolutionary method. Can't remember for sure since I did it quite a long time ago.
LesbianSeagull said:
I think it was the Revolutionary method. Can't remember for sure since I did it quite a long time ago.
Click to expand...
Click to collapse
Pm me your email, and if you'd like I could email you the RUU I have and you could see if it'll work. I'll walk you through it. You have gmail right?
Bizarre1 said:
I'm as new to the forums as you, but I did a little messing and reading around. In order to return your phone to the same way you bought it, you need to downgrade hboot to version 1.4 and then run the RUU.exe of your firmware version (I'm not sure which version it is for your phone, it was 2.17.651.5 for me but I got my phone with hboot 1.5). The downgrade thread is here [it's very tricky to brick it, make sure the light is a solid faint red (NOT BLINKING) in order to do it successfully]. Hopefully someone else can tell you which RUU version to use (to run before the downgrade if you get the *Security Warning* in hboot, as well as the one to use after in order to return to the way you were when you got the phone). I just downloaded all the RUU's and ran them all until one worked.
Click to expand...
Click to collapse
Just tried that, but I got the same HBOOT error message and I couldn't start the update in order to brick.
LesbianSeagull said:
Just tried that, but I got the same HBOOT error message and I couldn't start the update in order to brick.
Click to expand...
Click to collapse
Since you got that error, you need to flash the 2.08 or 2.17 RUU.exe to get rid of it. Try running the RUU while in the fastboot menu, and make sure you have the HTC drivers installed on your computer.
Have you tried both RUUs to no avail?
*Edit: I believe the drivers will install if you install HTC sync. Unfortunately I cant post the link to it, but just do a Google for HTC Evo 3D drivers. It's on HTC's website
koty2012 said:
Pm me your email, and if you'd like I could email you the RUU I have and you could see if it'll work. I'll walk you through it. You have gmail right?
Click to expand...
Click to collapse
PM'd and thanked
Bizarre1 said:
Since you got that error, you need to flash the 2.08 or 2.17 RUU.exe to get rid of it. Try running the RUU while in the fastboot menu, and make sure you have the HTC drivers installed on your computer.
Have you tried both RUUs to no avail?
Click to expand...
Click to collapse
Tried both
Code:
RUU_Shooter_S_Sprint_WWE_2.08.651.2_Radio_0.97.10.0808_NV_SPCS_1.31_003_release_208230_signed
RUU_Shooter_S_Sprint_WWE_2.17.651.5_Radio_1.06.00.1216_NV_NV_spcs_1.42_release_233304_signed
Both of which gave me the same error. the RUU connects over fastbootusb but halts at a specific point in the install, so I assume I have the right HTC drivers. I can find the install point in question if that would help.
Tried both
Code:
RUU_Shooter_S_Sprint_WWE_2.08.651.2_Radio_0.97.10.0808_NV_SPCS_1.31_003_release_208230_signed
RUU_Shooter_S_Sprint_WWE_2.17.651.5_Radio_1.06.00.1216_NV_NV_spcs_1.42_release_233304_signed
Both of which gave me the same error. the RUU connects over fastbootusb but halts at a specific point in the install, so I assume I have the right HTC drivers. I can find the install point in question if that would help.
Click to expand...
Click to collapse
That's really strange. Just to make sure you have the right drivers, go to Control Panel and then to Device Manager and see if your phone is there. It should be under "Android USB devices" or the like. Also, is USB debugging on before the going into hboot?
*Edit: Some more little things, HTC Sync should be uninstalled from your computer, and your phone should be locked.
LesbianSeagull said:
Tried following the instructions on this site to flash the latest HTC firmware and I could not install it from 4EXT. Renamed the file to PG86IMG.zip and flashed it from fastboot but hit an error. Tried to run the RUU for my radio version and every single one has hit an error (Update Failed! Main Version is older!).
The phone was originally HBOOT 1.40 S-OFF but it is now HBOOT 1.57 with s-on (which I did). I want to return the phone back to stock and start fresh but I really don't know how. Can I return back to HBOOT 1.40 or do I have to flash to the latest 1.50 and downgrade?
I'm really stumped by this one and any help would be greatly appreciated.
Click to expand...
Click to collapse
Did you flash the vm firmware ??
#Root-Hack_Mod*Always\
laie1472 said:
Did you flash the vm firmware ??
#Root-Hack_Mod*Always\
Click to expand...
Click to collapse
I used the instructions and download links from androidadvices(dot)com/update-htc-evo-3d-cdma-leaked-ics-403-firmware/. Reading the instructions now I see that I didn't put the phone into USB recovery mode. I can't get back into the ROM to do so and I can't get into my recovery either.
Your currently on hboot 1.57 and thats your your getting an update fail since 2.17 RUU has hboot1.50 Im not sure their is a way to downgrade this firmware unless you try the downgrade method for hboot 1.50 but that could maybe cause in a permanent brick.
iTzLOLtrain said:
Your currently on hboot 1.57 and thats your your getting an update fail since 2.17 RUU has hboot1.50 Im not sure their is a way to downgrade this firmware unless you try the downgrade method for hboot 1.50 but that could maybe cause in a permanent brick.
Click to expand...
Click to collapse
I'm trying that now. Hopefully it works!
So I tried bricking the phone using Unknownforce's method but everytime I would try and flash the 2.17 PG86IMG file in fastboot I get the same Hboot Version error. I also tried the Shooter_ICS_35_S_Sprint zip by renaming it to PG86IMG and and flashing in fastboot (since it has the matching hboot version), but I get a CID incorrect error. I'm trying to unlock my bootloader by using the HTC method in order to change the CID, but when I do so it gives me this in terminal.
Code:
C:\rootevo3dnew>fastboot flash unlocktoken unlock_code.bin
sending 'unlocktoken' (0 KB)...
OKAY [ 0.151s]
writing 'unlocktoken'...
(bootloader) unlock token check successfully
OKAY [ 0.008s]
finished. total time: 0.159s
C:\rootevo3dnew>fastboot oem writecid htc__001
...
(bootloader) shooter_init_sd, SD card already power on
(bootloader) sdcc_init_memory_device done
(bootloader) [FAT_ERROR] fat_open_file: can not find SMART_IO.CRD
(bootloader) [JAVACARD_ERR] SMART_IO.CRD cann't find
OKAY [ 0.198s]
finished. total time: 0.198s
My bootloader still says it's locked but the unlock_code.bin in ADB looks like it's working. Can anyone tell me what is happening? This is the only thing holding me back from downgrading and it's frustrating
LesbianSeagull said:
So I tried bricking the phone using Unknownforce's method but everytime I would try and flash the 2.17 PG86IMG file in fastboot I get the same Hboot Version error. I also tried the Shooter_ICS_35_S_Sprint zip by renaming it to PG86IMG and and flashing in fastboot (since it has the matching hboot version), but I get a CID incorrect error. I'm trying to unlock my bootloader by using the HTC method in order to change the CID, but when I do so it gives me this in terminal.
Code:
C:\rootevo3dnew>fastboot flash unlocktoken unlock_code.bin
sending 'unlocktoken' (0 KB)...
OKAY [ 0.151s]
writing 'unlocktoken'...
(bootloader) unlock token check successfully
OKAY [ 0.008s]
finished. total time: 0.159s
C:\rootevo3dnew>fastboot oem writecid htc__001
...
(bootloader) shooter_init_sd, SD card already power on
(bootloader) sdcc_init_memory_device done
(bootloader) [FAT_ERROR] fat_open_file: can not find SMART_IO.CRD
(bootloader) [JAVACARD_ERR] SMART_IO.CRD cann't find
OKAY [ 0.198s]
finished. total time: 0.198s
My bootloader still says it's locked but the unlock_code.bin in ADB looks like it's working. Can anyone tell me what is happening? This is the only thing holding me back from downgrading and it's frustrating
Click to expand...
Click to collapse
Hey sorry I so abrubtly had to go earlier, did you try again to flash the cwm.img? If you can get into backup and restore I feel as if you might be able to just go back to the previous hboot and ROM you had , not making any promises though.
koty2012 said:
Hey sorry I so abrubtly had to go earlier, did you try again to flash the cwm.img? If you can get into backup and restore I feel as if you might be able to just go back to the previous hboot and ROM you had , not making any promises though.
Click to expand...
Click to collapse
Just gave it another shot, but I got the same error:
Code:
C:\rootevo3dnew>fastboot flash boot cwm.img
sending 'boot' (4832 KB)...
OKAY [ 1.130s]
writing 'boot'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 1.928s
EDIT: Also tried running the 2.17 RUU again and it fails after attempting a signature check as well.
LesbianSeagull said:
Just gave it another shot, but I got the same error:
Code:
C:\rootevo3dnew>fastboot flash boot cwm.img
sending 'boot' (4832 KB)...
OKAY [ 1.130s]
writing 'boot'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 1.928s
EDIT: Also tried running the 2.17 RUU again and it fails after attempting a signature check as well.
Click to expand...
Click to collapse
I believe you don't flash that as boot. You flash cwm.img (clock work mod) as a recovery. Try
C:\rootevo3dnew>fastboot flash recovery cwm.img
*Edit: make sure your cwm.img is in your C:\rootevo3dnew folder.
Then after that, boot into the bootloader and go to recovery to access clockwork mod. See if you have any backups (which will save you a TON of pain by putting you back on hboot 1.4 with whatever former ROM you backed it up with)
Sent from my Evo 3D using XDA
Bizarre1 said:
I believe you don't flash that as boot. You flash cwm.img (clock work mod) as a recovery. Try
C:\rootevo3dnew>fastboot flash recovery cwm.img
*Edit: make sure your cwm.img is in your C:\rootevo3dnew folder.
Then after that, boot into the bootloader and go to recovery to access clockwork mod. See if you have any backups (which will save you a TON of pain by putting you back on hboot 1.4 with whatever former ROM you backed it up with)
Sent from my Evo 3D using XDA
Click to expand...
Click to collapse
Tried it, still gave me the signature verification error. I think it's because the bootloader is locked.
bump
Is there anything else I can try???
I know someone on XDA has to have a solution to this...
LesbianSeagull said:
Is there anything else I can try???
I know someone on XDA has to have a solution to this...
Click to expand...
Click to collapse
You have to be unlocked to flash the recovery image. Does it not say its unlocked at the top of HBOOT after using the HTC method?
Sent from the mobile paperweight itself!
I have been trying to root my 3d for liek 2 days now and have searched every where and tried ever trick i can find. No matter what i cannot seem to figure out what is going on.
I am hboot 1.58 S-ON i keep getting an error that the RUU i have is not the right one i have downloaded 3 different ones and all say the same thing i have read many thread and tried many ways to root this thing. I relock before using RUU but no matter what i get this message. It also will not flash any recovery, It just gets stuck at "sending"
i have the right drivers and everything. my computer sees my phone when i type "fastboot devices". any help would be so great.
lulzy1 said:
I have been trying to root my 3d for liek 2 days now and have searched every where and tried ever trick i can find. No matter what i cannot seem to figure out what is going on.
I am hboot 1.58 S-ON i keep getting an error that the RUU i have is not the right one i have downloaded 3 different ones and all say the same thing i have read many thread and tried many ways to root this thing. I relock before using RUU but no matter what i get this message. It also will not flash any recovery, It just gets stuck at "sending"
i have the right drivers and everything. my computer sees my phone when i type "fastboot devices". any help would be so great.
Click to expand...
Click to collapse
Based on your bootloader version, it sounds like you have a Sprint Evo 3D. I have a guide here that should help you get the the right RUU flashed, then get root and S-OFF.
ramjet73
ramjet73 said:
Based on your bootloader version, it sounds like you have a Sprint Evo 3D. I have a guide here that should help you get the the right RUU flashed, then get root and S-OFF.
ramjet73
Click to expand...
Click to collapse
your guide is the first guide I tried with no luck.. and yes im sprint
lulzy1 said:
your guide is the first guide I tried with no luck.. and yes im sprint
Click to expand...
Click to collapse
Then you need to give more specifics. If you can post the header information displayed in your bootloader here, and give the text of the error messages you are getting when you try to flash the RUU contained in the download, that will make it easier to help.
Also, please issue the following commands from fastboot and post the output here:
fastboot getvar cid
fastboot getvar mainver
ramjet73
Definitely post up the information ramjet73 is asking for.
Btw ramjet, you are quick. You always beat me to it!
Also curious if you are running the Ruu while booted up or from fastboot?
This seems blaringly obvious but if you are s-on, did you relock the bootloader?
Sent from my PG86100 using Tapatalk 2
ramjet73 said:
Then you need to give more specifics. If you can post the header information displayed in your bootloader here, and give the text of the error messages you are getting when you try to flash the RUU contained in the download, that will make it easier to help.
Also, please issue the following commands from fastboot and post the output here:
fastboot getvar cid
fastboot getvar mainver
ramjet73
Click to expand...
Click to collapse
bootloader header
***unlocked*** (currently, as I relock it to run RUU)
SHOOTER XC SHIP S-ON RL
HBOOT-1.58.0000
eMMC-boot
C:\Users\lulzyl\Desktop\QADERSO\Root>fastboot getvar cid
cid: SPCS_001
finished. total time: -0.000s
C:\Users\lulzyl\Desktop\QADERSO\Root>fastboot getvar mainver
mainver: SPCS_001
finished. total time: 0.005s
My battery is too low to run RUU right and im about to go to sleep I will update with the exact wording tomorrow but it says that Do not have the right RUU for my device. and if i am remembering correctly it says error 155 but I cant be 100% positive.
what i am using is RUU_Shooter_ICS_35_S_Sprint_WWE_2.89.651.2_Radio_1.09.00.0706__NV_NV_SPCS_1.43_release_271101_signed
Brian706 said:
Also curious if you are running the Ruu while booted up or from fastboot?
This seems blaringly obvious but if you are s-on, did you relock the bootloader?
Click to expand...
Click to collapse
He said in the OP that "I relock before using RUU but no matter what i get this message", but that's why I want to see his bootloader info and the text of the message he is getting.
I always recommend starting the RUU.exe with the phone in "fastboot usb" mode, but in theory it should work even if he is booted into Android.
Let's see what he has to say.
lulzy1 said:
C:\Users\lulzyl\Desktop\QADERSO\Root>fastboot getvar mainver
mainver: SPCS_001
finished. total time: 0.005s
Click to expand...
Click to collapse
That mainver doesn't look right. I should be 2.89.651.2 if you are on hboot 1.58. If that's really the current mainver it would explain why you can't flash the RUU. I have no idea how that could have been changed without flashing something with an incorrect android-info.txt in a PG86IMG.zip file, which requires S-OFF, or someone setting the mainver incorrectly via ADB. Did you get the phone new or used?
Please verify that is correct, and if it is, it will need to changed before the RUU will take.
Also, when you try to run the RUU.exe again make sure the phone is in fastboot USB mode.
ramjet73
I will rerun the comand later to make sure, I always run it from fastboot usb. Also i got the phone as an insurance replacement. sprint sucks so bad there is no telling if the phone is actually new or not
ok.. update I redid your command this morning and got what you were looking for.
C:\Users\lulzy\Desktop\QADERSO\Root>fastboot getvar mainver
mainver: 2.89.651.2
finished. total time: 0.000s
here is what RUU continues to give me no matter if im in fastboot usb or just the home screen
ERROR [155]: UNKNOWN ERROR
The ROM Update Utility cannot update your android phone.
Please get the correct ROM Update Utility and try again.
This is using the one you have in your RUU file ramjet and when this happens i get the black HTC screen but it has no loading bar and nothing in all the corners
lulzy1 said:
here is what RUU continues to give me no matter if im in fastboot usb or just the home screen
ERROR [155]: UNKNOWN ERROR
The ROM Update Utility cannot update your android phone.
Please get the correct ROM Update Utility and try again.
This is using the one you have in your RUU file ramjet and when this happens i get the black HTC screen but it has no loading bar and nothing in all the corners
Click to expand...
Click to collapse
So your CID and mainver look OK.
The 155 error usually means your current bootloader is unlocked.
Try relocking your your bootloader, then remove and and replace the battery and start the bootloader. Since your bootloader is currently unlocked, the status should show as "*** RELOCKED ***". Make sure it does and that you are connected to your PC in "fastboot usb" mode, then try it again.
If that doesn't work, you can try downloading just the RUU.exe from here. It's the same one that is in the QADERSO .zip file, but it's worth a try.
ramjet73
during my previous attempt it was relocked, anytime i try running RUU from fastboot it says it cant run because my battery is too low (i have 93% battery and i dont get the warning if i run from the home screen) i cannot run RUU from fastboot because this is all i ever see even after re downloading
lulzy1 said:
during my previous attempt it was relocked, anytime i try running RUU from fastboot it says it cant run because my battery is too low (i have 93% battery and i dont get the warning if i run from the home screen) i cannot run RUU from fastboot because this is all i ever see even after re downloading
Click to expand...
Click to collapse
The battery low indicator in fastboot mode sounds like a hardware problem to me. If your battery isn't charging correctly it may be a problem with your cable or USB port. Many people have gotten the RUU.exe to flash successfully by changing to a different cable and/or PC, but if you can't do that I suggest fully charging the battery with the A/C adapter that came with the phone before trying to flash the RUU.exe again.
Flashing the RUU.exe with the phone in Android mode may be masking the problem, but something is not right with your hardware.
ramjet73
all done!! different computer and cord works.
Thanks alot
How do you relock the hboot? I'm getting the same error. Thanks.
"fastboot OEM lock"
Phone:
Sprint HTC EVO 3D
Root & S-Off(JBear)
HBoot: JBear 1.58.5858
Firmware: 2.89.651.5
Radio: 1.09.00.0706
Rom: FroZenROM Ep 2.1
Kernel: AnthraX 2.7.0
Recovery: TWRP 2.3.3.0
SDCard: San Disk 64GB Extreme Class 10 UHS-1 (Low External Storage Wizard? Uninstall)
i need help
i need some help fixing my phone i rooted it had it working well for about 2 hours changed somthing now im stuck on the htc green and white sceen
my bootloader says relocked ive been trying to follow the guides but nothing seems to work, right now the phone is in the bootloader as thats all ive been able to access i have a virgin mobile evo 3d with hboot 1.58..can somebody please help me? or is my phone screwed?
Your phone is not screwed
What did you change? I'm guessing you either flashed a rom that's incompatible with your current hboot or you are s-on and need to flash the kernel separately.
What recovery do you have installed?
Brian706 said:
Your phone is not screwed
What did you change? I'm guessing you either flashed a rom that's incompatible with your current hboot or you are s-on and need to flash the kernel separately.
What recovery do you have installed?
Click to expand...
Click to collapse
thanks for the response but i actually managed to fix it yesterday. idk what i changed but i was using the clockworld recovery but it wouldnt install the stock shooter file so i used 4ext and its all bueno now except it boots as a sprint phone now but whatever i can deal with that
Glad you got it!
I'd stick with 4ext. I have heard cwm doesn't play well with this device but have not experienced it first hand.
Yea I won't be putting that back on my phone now I have a question I believe I have the vmobile stock shooter on my pc I need to fast boot that to get my splash screen and stuff back right? Cause right now when I turn it on it says sprint
How do i unroot my Sprint HTC EVO 3D AND RETURN TO STOCK..
UNLOCKED
SHOOTER XC SHIP S-OFF RL
HBOO1.58.0000
THANKS!
Follow one of the multiple guides.
sent from MY BAD A$$ ET4G
patrao_n said:
Follow one of the multiple guides.
sent from MY BAD A$$ ET4G
Click to expand...
Click to collapse
what multiple guildes?
I myself just run the RUU when I want stock. It's simple.
Sent from my shooter using xda premium
Unroot Help
If you want to unroot, first find the Stock Hboot 1.58, then install it.
Then run the RUU for your device.
Lastly, in fastboot (adb), run "reboot bootloader" then run "fastboot oem writesecureflag 3".
Congrats, you will now be unrooted with bootloader *LOCKED*.
If you need any more help, feel free to PM me.
Boris Spektor said:
then run "fastboot oem writesecureflag 3".
Click to expand...
Click to collapse
DON'T RUN THIS.........
What are you trying to do?
Boris Spektor said:
If you want to unroot, first find the Stock Hboot 1.58, then install it.
Then run the RUU for your device.
Lastly, in fastboot (adb), run "reboot bootloader" then run "fastboot oem writesecureflag 3".
Congrats, you will now be unrooted with bootloader *LOCKED*.
If you need any more help, feel free to PM me.
Click to expand...
Click to collapse
raptoro07 said:
DON'T RUN THIS.........
What are you trying to do?
Click to expand...
Click to collapse
He said to run the RUU before issuing that command so it should be fine if the intent is to return to 100% stock, including S-ON. It's not really necessary to flash the stock bootloader before flashing the RUU but it might save having to restart the RUU if it hangs after flashing the bootloader. The OP said he was already on hboot 1.58 anyway.
You will also need to to lock the bootloader with a zip file in recovery since flashing the RUU doesn't do that. I have a guide here that includes everything you need.
Good luck!
ramjet73
ramjet73 said:
He said to run the RUU before issuing that command so it should be fine if the intent is to return to 100% stock, including S-ON. It's not really necessary to flash the stock bootloader before flashing the RUU but it might save having to restart the RUU if it hangs after flashing the bootloader. The OP said he was already on hboot 1.58 anyway.
You will also need to to lock the bootloader with a zip file in recovery since flashing the RUU doesn't do that. I have a guide here that includes everything you need.
Good luck!
ramjet73
Click to expand...
Click to collapse
When i reinstalled the stock Hboot manually (via bootloader) it showed *LOCKED* for me.
Just wondering, how does flashing a zip file in recovery, (which doesn't touch the Hboot) turn it *LOCKED*?
Boris Spektor said:
When i reinstalled the stock Hboot manually (via bootloader) it showed *LOCKED* for me.
Just wondering, how does flashing a zip file in recovery, (which doesn't touch the Hboot) turn it *LOCKED*?
Click to expand...
Click to collapse
That's because you were locked already and it just wasn't showing because the custom hboot masks that status.
There's a link to a thread that explains how the lock zip file works in this post.
ramjet73
Thanks guys for all your help....
Back to stock.
But my HBOOT is still showing S-OFF
SHOOTER XC SHIP S-OFF RL
How do iget S-OFF TO S-ON...
PSid not run this command yet..(fastboot oem writesecureflag 3)
Hello guys,
i have soffed my phone and tried a few custom roms but not one worked properly for me so i want to go back to stock rom.
I have found the page where all of them are listed but i have no clue which one to take. Which one is the newest stock rom for Austria, Europe?
TIA
Come in guys, cant be that no one knows.
dosada said:
Come in guys, cant be that no one knows.
Click to expand...
Click to collapse
The available RUU's for the Evo 3D/V are linked from step 2 in this this post.
You would probably want the highest numbered build for the European GSM model.
ramjet73
Somehow i must have messed up something. There are two different Europe RUU
RUU_Shooter_U_HTC_Europe_1.20.401.2_Radio_10.53.9020.00_10.13.9020.08_2M_release_203403_signed.exe 388469KB 17 2013-01-29 10:02:36
and
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.exe 444142KB 21 2013-01-29 09:40:53
But i cant install either of them. I allways get error 155, meaning i have got the wrong ruu.
Is there some way to force the damn thing to accept some of the roms? need my phone, am stuck with a damn samsung jet at the moment
dosada said:
Is there some way to force the damn thing to accept some of the roms? need my phone, am stuck with a damn samsung jet at the moment
Click to expand...
Click to collapse
Use the following fastboot commands to display your current CID and mainver:
fastboot getvar cid
fastboot getvar mainver
Click to expand...
Click to collapse
Post the values here and that should help identify what RUU you need.
The mainver can be changed by flashing zip files but have you ever changed your CID?
ramjet73
C:\Android>fastboot getvar cid
< waiting for device >
cid: HTC__102
finished. total time: 0.003s
C:\Android>fastboot getvar mainver
mainver: 3.28.401.1
finished. total time: 0.016s
That is what i get. The only thing i did is unlock the bootloader on htcdev and then root by instructions i found here
1_Press the power and volume down button at the same time
2_Go to fastboot make sure your phone is connected to the PC
3_Make sure you have Your Original ROM
4_You need a recovery go to http://d-h.st/Ikz
5_When you used adb and fastboot on htcdev press ctrl shift right click(you will see command window press it) on the folder you putted them and copy recovery.img to that folder
6_type fastboot flash recovery recovery.img
7_go to bootloader and choose recovery
8_toggle usb storage
9_copy this file http://downloads.androidsu.com/super...ghi-signed.zip to your sd card
10_In recovery choose install from sd card
11_choose zip
12_choose the zip from sd card
13_choose zip you copied and install
14_reboot
dosada said:
C:\Android>fastboot getvar cid
< waiting for device >
cid: HTC__102
finished. total time: 0.003s
C:\Android>fastboot getvar mainver
mainver: 3.28.401.1
finished. total time: 0.016s
That is what i get. The only thing i did is unlock the bootloader on htcdev and then root by instructions i found here
Click to expand...
Click to collapse
OK, you're fine.
The reason you are getting the 155 error for the RUU is because you need to lock the bootloader with the following command before running it:
fastboot oem lock
Click to expand...
Click to collapse
Try doing that and then running the RUU_SHOOTER_U_ICS_35_S_HTC_Europe_3.28.401.1 version of the RUU again.
ramjet73
Thank you very much. That was the problem. Worked perfectly
Okay guys. I unlocked with Moonshine, was on a Carbon ROM 10.1, updated last night to a 10.2 based Carbon ROM and lost my data. I found out to get it back, I needed to RUU back to stock. Downloaded the RUU and tried to run but it tells me that fastboot.exe and adb.exe have stopped working (I am on Windows 8). In the meantime, I missed a step and re-locked the bootloader early.
Trying to re-unlock with Moonshine and it continually reboots my phone at the "Launching Temproot" stage. Tried to unlock with Facepalm and it worked fine except it didn't fail (as it's designed too) Try to run the next step from Facepalm (The boot stage) and it fails.
Now when I hard reboot get out of the HTC screen from Facepalm, it hangs on the splash screen which is custom. Also after I performed Facepalm, it overwrote my custom recovery so that's gone and it won't let me write another one because the bootloader is locked.
I'm am at a complete loss here and am very afraid that my DNA it toast but I know there is a glimmer of hope because I can access fastboot. Any help from the masters here at XDA would be great.
Snowman1771 said:
Okay guys. I unlocked with Moonshine, was on a Carbon ROM 10.1, updated last night to a 10.2 based Carbon ROM and lost my data. I found out to get it back, I needed to RUU back to stock. Downloaded the RUU and tried to run but it tells me that fastboot.exe and adb.exe have stopped working (I am on Windows 8). In the meantime, I missed a step and re-locked the bootloader early.
Trying to re-unlock with Moonshine and it continually reboots my phone at the "Launching Temproot" stage. Tried to unlock with Facepalm and it worked fine except it didn't fail (as it's designed too) Try to run the next step from Facepalm (The boot stage) and it fails.
Now when I hard reboot get out of the HTC screen from Facepalm, it hangs on the splash screen which is custom. Also after I performed Facepalm, it overwrote my custom recovery so that's gone and it won't let me write another one because the bootloader is locked.
I'm am at a complete loss here and am very afraid that my DNA it toast but I know there is a glimmer of hope because I can access fastboot. Any help from the masters here at XDA would be great.
Click to expand...
Click to collapse
Wow! 1)..RUU does totally format, erase and finally restore the original system that came with the phone as new. so you loose everything
2) Try it from Windows 7 PC
3) Return to stock on Moonshine S-Off > http://forum.xda-developers.com/showthread.php?t=2293919&highlight=flash+radio
Okay, Tried RUU from a Windows 7 pc and no dice, I get error 170 (USB connection) but no fastboot or adb failures. I was able to flash the stock 1.15 HBOOT but when I go to fastboot it tells me my HBOOT is version 1.33.
Tried Facepalm to no avail, It still won't fail after the first command as its supposed to. Tried Moonshine as well but wouldn't work because debugging isn't enabled.
Found a guide that said to find the RUU rom in the temp files and put that on the sd-card which I can't do because it won't boot, but thought I would try to flash it and this is what it did - P.S. The Rom is the PB99IMG file
C:\Users\Owner\Desktop\adt-bundle-windows-x86_64-20130729\sdk\tools>fastboot oem
rebootRUU
...
(bootloader) Start Verify: 0
OKAY [ 0.045s]
finished. total time: 0.045s
C:\Users\Owner\Desktop\adt-bundle-windows-x86_64-20130729\sdk\tools>fastboot fla
sh zip PB99IMG.zip
sending 'zip' (913111 KB)...
OKAY [ 40.273s]
writing 'zip'...
(bootloader) rom parsing start ...
(bootloader) rom parsing finish ...
(bootloader) zip header checking...
(bootloader) zip info parsing...
FAILED (remote: 22 loading zip info fail)
finished. total time: 46.433s
C:\Users\Owner\Desktop\adt-bundle-windows-x86_64-20130729\sdk\tools>
Snowman1771 said:
Okay, Tried RUU from a Windows 7 pc and no dice, I get error 170 (USB connection) but no fastboot or adb failures. I was able to flash the stock 1.15 HBOOT but when I go to fastboot it tells me my HBOOT is version 1.33.
Tried Facepalm to no avail, It still won't fail after the first command as its supposed to. Tried Moonshine as well but wouldn't work because debugging isn't enabled.
Found a guide that said to find the RUU rom in the temp files and put that on the sd-card which I can't do because it won't boot, but thought I would try to flash it and this is what it did - P.S. The Rom is the PB99IMG file
C:\Users\Owner\Desktop\adt-bundle-windows-x86_64-20130729\sdk\tools>fastboot oem
rebootRUU
...
(bootloader) Start Verify: 0
OKAY [ 0.045s]
finished. total time: 0.045s
C:\Users\Owner\Desktop\adt-bundle-windows-x86_64-20130729\sdk\tools>fastboot fla
sh zip PB99IMG.zip
sending 'zip' (913111 KB)...
OKAY [ 40.273s]
writing 'zip'...
(bootloader) rom parsing start ...
(bootloader) rom parsing finish ...
(bootloader) zip header checking...
(bootloader) zip info parsing...
FAILED (remote: 22 loading zip info fail)
finished. total time: 46.433s
C:\Users\Owner\Desktop\adt-bundle-windows-x86_64-20130729\sdk\tools>
Click to expand...
Click to collapse
where did you get the instructions found with this PB99IMG.zip file?
Your Bootloader is locked or unlocked?
letschky said:
where did you get the instructions found with this PB99IMG.zip file?
Your Bootloader is locked or unlocked?
Click to expand...
Click to collapse
IDK it may work, worked in a different phone, but have to be pushed to the sd card
http://forum.xda-developers.com/showthread.php?p=32574569
letschky said:
where did you get the instructions found with this PB99IMG.zip file?
Your Bootloader is locked or unlocked?
Click to expand...
Click to collapse
Here is the link to what I used to get the PB99IMG.zip - It is the same one finanandroid posted
http://forum.xda-developers.com/showthread.php?p=32574569
And my Bootloader is locked because I was following this guide (http://forum.xda-developers.com/showthread.php?t=2293919) and spaced out and locked the bootloader without realizing I needed to flash the stock HBOOT and Splash screen, That's what I get for trying to do it at 11:30 at night.
Snowman1771 said:
Here is the link to what I used to get the PB99IMG.zip - It is the same one finanandroid posted
http://forum.xda-developers.com/showthread.php?p=32574569
And my Bootloader is locked because I was following this guide (http://forum.xda-developers.com/showthread.php?t=2293919) and spaced out and locked the bootloader without realizing I needed to flash the stock HBOOT and Splash screen, That's what I get for trying to do it at 11:30 at night.
Click to expand...
Click to collapse
Where are you currently?
s-off?
locked?
whats your CID read as in fastboot?
Also are you on windows 8 or 8.1 and do you have working drivers to begin with.
I have S-ON and Bootloader is locked,Problem,i have Software 1.15 but i flash the HBoot,Boot.img ... To make Moonshine S-OFF.This is the 2.06 Kernel with Software 1.15 and i have Problem with Wifi and the Screen flackered white.And the next Problem,i can't unlock the Bootloader witn Hboot 1.33,i hope you understand me.
jake.corey.jacobs said:
Where are you currently?
s-off?
locked?
whats your CID read as in fastboot?
Also are you on windows 8 or 8.1 and do you have working drivers to begin with.
Click to expand...
Click to collapse
My bootloader screen reads,
"Tampered
Locked
Monarudo pvt ship s-off
CID-VZW_001
HBOOT-1.33.0001
RADIO-1.01.01.0110"
I am on Windows 8 (and have access to a Windows 7 desktop) and yes, I have working drivers.
Moonshine and face palm are failing because you're already s-off
Try a different usb port and flash the stock splash screen, then run RUU
Phaded said:
Moonshine and face palm are failing because you're already s-off
Try a different usb port and flash the stock splash screen, then run RUU
Click to expand...
Click to collapse
Okay I tried both of my 2.0 USB slots and neither worked, Here is what I get -
C:\Users\Matt\Desktop\adt-bundle-windows-x86_64-20130522\sdk\tools>fastboot flas
h splash1 splash.img
sending 'splash1' (4050 KB)...
OKAY [ 0.616s]
writing 'splash1'...
FAILED (remote: not allowed)
finished. total time: 0.653s
You need to unlock... Um try htcdev and go for an unlock token. Since you're s-off it may work.
Fastboot oem unlock might work as well. Try that first, then if no go try htcdev
Phaded said:
You need to unlock... Um try htcdev and go for an unlock token. Since you're s-off it may work.
Fastboot oem unlock might work as well. Try that first, then if no go try htcdev
Click to expand...
Click to collapse
Just tried to OEM unlock and nothing, it gives me this.
C:\Users\Owner\Desktop\adt-bundle-windows-x86_64-20130729\sdk\tools>fastboot oem
unlock
...
(bootloader) [ERR] Command error !!!
OKAY [ 0.010s]
finished. total time: 0.010s
The command is "fastboot oem unlock" isn't?
Just looked into HTC Dev and the DNA is not listed as being supported.
Snowman1771 said:
Just looked into HTC Dev and the DNA is not listed as being supported.
Click to expand...
Click to collapse
you have to select other devices.
Like Jake said, scroll to the other devices part, then try
jake.corey.jacobs said:
you have to select other devices.
Click to expand...
Click to collapse
Just tried and it failed, here is what it said.
Error Code: 160.
Error Reason: MID Not Allowed.
Snowman1771 said:
Just tried and it failed, here is what it said.
Error Code: 160.
Error Reason: MID Not Allowed.
Click to expand...
Click to collapse
does your CID say vzw_001 or 111111 or 222222
You may be able to write the cid since you're s-off. Don't hold me to that tho.
jake.corey.jacobs said:
does your CID say vzw_001 or 111111 or 222222
Click to expand...
Click to collapse
The CID says VZW_001.