Is there a way to get this phone back to stock? I have been searching everywhere with no luck so far.
Download either the 2.08 or 2.17 RUU .exe file, reboot bootloader, fastboot oem lock, run RUU file.
Thanks for the response. I just thought I only had to download a RUU and change the name to PG86IMG and flash it. What do you mean by oem lock?
Before running the ruu, put the phone in fastboot mode and in a command prompt type "fastboot oem lock" no quotes
squiggs95 said:
Before running the ruu, put the phone in fastboot mode and in a command prompt type "fastboot oem lock" no quotes
Click to expand...
Click to collapse
C:\Users\[email protected]#[email protected]>fastboot oem lock
'fastboot' is not recognized as an internal or external command,
operable program or batch file.
Is what I got
i dont think there is a way to do this when you are s-on
sorry!!!
Do u have drivers and fastboot installed?
Drivers yes, fastboot apparently not.
Nvm, I had to go to the Fastboot folder, hold shift then right click. Open command window here.
Although it still had all the applications I had installed. Is that normal?
Usually not. When i unrooted mine all my apps were gone. If u go into your bootloader does it say you are relocked?
squiggs95 said:
Usually not. When i unrooted mine all my apps were gone. If u go into your bootloader does it say you are relocked?
Click to expand...
Click to collapse
Yeah it says "relocked" and clockwork recovery was gone... I assume it worked?
! twitty said:
Yeah it says "relocked" and clockwork recovery was gone... I assume it worked?
Click to expand...
Click to collapse
youll know if it worked when you have that pg86img.zip on the root of your sdcard and then relock your phone and then boot into hboot by holding volume down and the power button and watch for the blue bar on the upper right to load the new file...
Fastboot folder???
! twitty said:
Drivers yes, fastboot apparently not.
Nvm, I had to go to the Fastboot folder, hold shift then right click. Open command window here.
Although it still had all the applications I had installed. Is that normal?
Click to expand...
Click to collapse
So where do I find this Fastboot folder? I need to unroot my wifes phone due to the bottom buttons aren't working properly and it is on Hboot 1.5 s-on... t/u for your help.
kaw900r said:
So where do I find this Fastboot folder? I need to unroot my wifes phone due to the bottom buttons aren't working properly and it is on Hboot 1.5 s-on... t/u for your help.
Click to expand...
Click to collapse
Once you lock your bootloader its still gonna show "relocked" anyway. They will know that you had it rooted. Just find a stock unrooted Rom. Save your self the hastle. I could be wrong though but I am pretty sure that you will get a watermarked bootloader once you relock. They might not even check the bootloader and if they do they might not care.
Sent from my PG86100 using xda premium
kaw900r said:
So where do I find this Fastboot folder? I need to unroot my wifes phone due to the bottom buttons aren't working properly and it is on Hboot 1.5 s-on... t/u for your help.
Click to expand...
Click to collapse
You wipe first in recovery then go back to hboot
fastboot oem lock with adb
Relocks you
Now just find and download the 2.17 RUU EXE run it and your set man.
When you rooted your phone you had a folder at the root of your C drive in which you probably downloaded and extracted a zip file in with the root files you used. After you put your phone in fast goot, Go to command prompt type cd /"name of file you extracted that in", hit enter, then type adb, hit enter again, then type fastboot oem lock. You will then have S-ON and be able to run the RUU to un-root
Related
All, I am sorry I didn't search more, but I am desperate. I go on travel in a few hours.
Long story short, my phone stopped working with 3g, I spent 4-5 hours on phone with sprint trying to fix. THey want it back to the store. It was HTC unlocked with Fresh. I used fastoot to do fastboot OEM lock, the phone rebooted and goes back to the bootloader screen, I can't get it to go back to Android
It says Tampered, Relocked, security warning. Please. Any help. Can I RUU from fastboot?
Yes
As long as you have the boot loader locked you can run the RUU, you can find the RUU in Android Developement.
Hook the phone to your computer, open a command prompt and type "adb reboot recovery" make sure USB debugging is checked. That should get you into TWRP recovery, then go from there.
musicman625 said:
As long as you have the boot loader locked you can run the RUU, you can find the RUU in Android Developement.
Hook the phone to your computer, open a command prompt and type "adb reboot recovery" make sure USB debugging is checked. That should get you into TWRP recovery, then go from there.
Click to expand...
Click to collapse
After relocking the bootloader, I can no longer enter recovery. RUU doesn't seem to want to run because my phone is not up and running (it is already at fastboot prompt). Can I just get it to recognize my phone in fastboot mode somehow?
U need to unlock it again and flash the stock Rom if u relock it with a custom Rom it doesn't allow it to boot
Sent from my EVO using xda premium
adma84 said:
After relocking the bootloader, I can no longer enter recovery. RUU doesn't seem to want to run because my phone is not up and running (it is already at fastboot prompt). Can I just get it to recognize my phone in fastboot mode somehow?
Click to expand...
Click to collapse
As long as you have the proper drivers you should be able to run the RUU from fastboot. While in fastboot if you type 'fastboot devices' (without quotes) is your phone listed?
Sent from my ELTE using Tapatalk 2
dylan6879 said:
U need to unlock it again and flash the stock Rom if u relock it with a custom Rom it doesn't allow it to boot
Sent from my EVO using xda premium
Click to expand...
Click to collapse
Didn't know that was the case. Thanks
crump84 said:
As long as you have the proper drivers you should be able to run the RUU from fastboot. While in fastboot if you type 'fastboot devices' (without quotes) is your phone listed?
Sent from my ELTE using Tapatalk 2
Click to expand...
Click to collapse
RUU is finally running now. Failed several times, and then just started working. I hope it works. Thank you everyone. Will post back
This happened to me as well. The only thing that I did that finally made it work, was to make sure that the path that I performed the fastboot oem lock command in was the path that contained the fastboot file.
When I did this, it would boot into my custom ROM and I was able to run the RUU without any problems.
When I would try to run the RUU from bootloader it would always tell me my battery was low, even though I was over 90%.
Happend to me too . I just ran ruu while in fastboot .
Sent from my EVO using xda premium
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.
Hello
I'm trying to revert back to complete stock (stock rom, no root, S-ON) and following this guide/post:
http://forum.xda-developers.com/showthread.php?p=33770807
For that i need to do check the CID and then write back the original CID (Though i can skip this because i didn't use HTC Dev method at all, just original root and revolutionary S-OFF)
Then i need to do "fastboot oem lock" before running the RUU.. but here in lies my problem.
For some reason i can't get fastboot to work.
ADB works fine and i can push and pull files when in android or recovery, but as soon as i enter hboot and try to use fastboot commands, i just get "< Waiting for device >" and have to close the CMD window. (Before you ask, yes it does say "FASTBOOT USB" on the screen)
I have tried both using my standard adb and fastboot files, and i have also tried downloading the latest android SDK and using those files, but neither to any luck.
Anyone have any idea? It might be something simple, as i haven't had to use fastboot before now.
I'm guessing it can't be a driver problem as i can connect fine with ADB and it shows my device when doing "adb devices" (Though it does not show my device when i do "fastboot devices", it just skips the line entirely and prompts me to enter something new).
- Moon
Moonbloom said:
I'm guessing it can't be a driver problem as i can connect fine with ADB and it shows my device when doing "adb devices" (Though it does not show my device when i do "fastboot devices", it just skips the line entirely and prompts me to enter something new).
Click to expand...
Click to collapse
If "fastboot devices" doesn't show the serial number of your phone, none of the other fastboot commands are going to work.
Have you tried disconnecting the phone, rebooting your PC and then connecting the phone again? If that doesn't work, try uninstalling the drivers, rebooting the PC, then reinstalling the drivers.
ramjet73
ramjet73 said:
If "fastboot devices" doesn't show the serial number of your phone, none of the other fastboot commands are going to work.
Have you tried disconnecting the phone, rebooting your PC and then connecting the phone again? If that doesn't work, try uninstalling the drivers, rebooting the PC, then reinstalling the drivers.
ramjet73
Click to expand...
Click to collapse
Tried to reboot the computer, no change.
Decided to try using my laptop before going through the trouble of reinstalling drivers, and it worked
My laptop can see my device fine using "fastboot devices" and i'm able to get my CID (cid: 0202)
Thanks for trying to help me out anyways I might be back with more questions
EDIT: I just google'd a bit and found another command to get the CID "fastboot oem readcid" and it shows HTC_Y13 (which i find more believable tbh).
Is your hboot unlocked?
I am s-off, but couldn't use fastboot commands untill i unlocked my bootloader again..
klect said:
Is your hboot unlocked?
I am s-off, but couldn't use fastboot commands untill i unlocked my bootloader again..
Click to expand...
Click to collapse
There's no need to unlock the bootloader if you are S-OFF.
If you want to run fastboot commands like "flash" or "erase" just install a custom bootloader like ENG, JBear or Revoutionary from the current bootloader. It's better to keep the bootloader locked since that's the stock status and it makes it much easier to return the phone to 100% stock.
AFAIK, the "*** RELOCKED ***" heading you get when locking an unlocked bootloader which flags to HTC/Sprint that you modified the phone can only be undone with the JuopunutBear wire trick.
ramjet73
For me IT was the only way to get fastboot working though...
Sent from my Evo 3D GSM using xda app-developers app
klect said:
For me IT was the only way to get fastboot working though...
Click to expand...
Click to collapse
Did you try one of the JuopunutBear bootloaders (GB or ICS) for the GSM version of the Evo 3D? That should allow the fastboot commands without unlocking.
ramjet73
Yeah, after i s-offed i flashed the ICS jb hboot, but no luck...
So i decided to flash the 1.49.0007 hboot and unlock it the htcdev way.
But if you want to lock it again, you can simply redo the wiretrick right?
klect said:
Yeah, after i s-offed i flashed the ICS jb hboot, but no luck...
So i decided to flash the 1.49.0007 hboot and unlock it the htcdev way.
But if you want to lock it again, you can simply redo the wiretrick right?
Click to expand...
Click to collapse
That's correct.
ramjet73
For all those who were directed here...
This solved my problem when everybody else's advice failed, and it was the easiest.
http://forums.androidcentral.com/ve...how-install-device-drivers-android-1-0-a.html
I successfully got S-OFF on my Evo V. Now I'm trying to downgrade my hboot to 1.04 ENG. My current hboot is the one JBear puts on after getting S-OFF.
When trying to flash the PG86IMG.zip through fastboot, it gives me the "CID Incorrect!" error and have to power off. My CID is "SPCS_002"
Any help is greatly appreciated.
*EDIT*
Lol. It seems like I find the answer right after I made the thread everytime. I had to edit the PG86IMG.zip to use my CID.
FussyQBert said:
*EDIT*
Lol. It seems like I find the answer right after I made the thread everytime. I had to edit the PG86IMG.zip to use my CID.
Click to expand...
Click to collapse
You could also use the hboot downloads from this post which have been modified to work with both the Sprint (SPCS_001) and Virgin Mobile (SPCS_002) CID's.
ramjet73
ramjet73 said:
You could also use the hboot downloads from this post which have been modified to work with both the Sprint (SPCS_001) and Virgin Mobile (SPCS_002) CID's.
ramjet73
Click to expand...
Click to collapse
Well, I did use an hboot from that post. I tried editing the text file inside to remove the SPCS_001 but this still didn't work. Now when trying to flash through the bootloader, it parses the zip but then doesn't install.
Not sure what's going on :crying:
*EDIT*
Ok now I might have screwed something up. I was able to flash through the command line fastboot, rather than the bootloader. I flashed through the command line using these commands:
fastboot oem rebootRUU
fastboot flash zip PG86IMG_ENG_1.04-hboot.zip
Now my phone is stuck on the RUU HTC screen (the black with silver letters). The progress bar is about 3/4 full
FussyQBert said:
*EDIT*
Ok now I might have screwed something up. I was able to flash through the command line fastboot, rather than the bootloader. I flashed through the command line using these commands:
fastboot oem rebootRUU
fastboot flash zip PG86IMG_ENG_1.04-hboot.zip
Now my phone is stuck on the RUU HTC screen (the black with silver letters)
Click to expand...
Click to collapse
Did you issue the "fastboot reboot" or "fastboot reboot-bootloader" command after the flash finished? Or you can just remove/replace the battery then power on.
ramjet73
Hey guys, I need to return my phone to verizon because of a simcard/PUK lock error. I'm on the current OTA update (2.06) but still unlocked, rooted and S-off. I need to go back to bone stock if possible. Can I still follow the guide in this thread to go back to stock??
http://forum.xda-developers.com/showthread.php?t=2017525
Anyone?
scheirere said:
Anyone?
Click to expand...
Click to collapse
You don't have to relock your phone all you have to do is flash the ENG Bootloader then you can run the RUU. Make sure you have all the drivers you need installed first or it WILL fail.
ENG Bootloader:
http://forum.xda-developers.com/showthread.php?t=2156713
Also this won't take away your S-Off the only way to get to S-On is by running a special command. Once S-Off always S-Off.
zone23,
Thanks a million! One more question....I'm not familiar with RUU. Do you have a link to were I might find that file?
Thanks again,
Eric
scheirere said:
zone23,
Thanks a million! One more question....I'm not familiar with RUU. Do you have a link to were I might find that file?
Thanks again,
Eric
Click to expand...
Click to collapse
Yes try here:
http://forum.xda-developers.com/showpost.php?p=37277937&postcount=66
Oh and don't forget to hit thanks on that post.
Ok, now I'm a little confused. I downloaded both files. The modded ENG bootloader and the RUU zip file from the links. But what order. Sorry but I'm not familiar with this stuff and don't want to dig myself into a deeper hole by bricking this thing.
Is this the proceedure?
1. adb reboot bootloader
2. fastboot oem rebootRUU (using the RUU_DLX_WL_JB_45.exe file?)
3. fastboot flash zip ModdedPL832IMG.zip
Anything else I'm missing? Also, what drivers? The same ones I installed when I rooted the phone?
Thanks in advance guys!
scheirere said:
Ok, now I'm a little confused. I downloaded both files. The modded ENG bootloader and the RUU zip file from the links. But what order. Sorry but I'm not familiar with this stuff and don't want to dig myself into a deeper hole by bricking this thing.
Is this the proceedure?
1. adb reboot bootloader
2. fastboot oem rebootRUU (using the RUU_DLX_WL_JB_45.exe file?)
3. fastboot flash zip ModdedPL832IMG.zip
Anything else I'm missing? Also, what drivers? The same ones I installed when I rooted the phone?
Thanks in advance guys!
Click to expand...
Click to collapse
This first:
1. adb reboot bootloader
2. fastboot oem rebootRUU
3. fastboot flash zip ModdedPL832IMG.zip
4. Profit
making sure that the .zip is in the same folder as fastboot
then run the RUU after you reboot the phone.
Yes it should be the same drivers you used when rooting.
Looks like I spoke too soon on those downloaded files. The download of the RUU file bombed out on me and I didn't realize it. When I go back to the site in the link, and try to download the file now, it just sits waiting. I guess the site is down? Any other links or locations?
Downloads working now maybe keep trying they say they are under a DDOS attack. Here it is from hotfile but I can't confirm this as real.
HERE
OK, I got partway thru the steps. everything went well until I tried to fastboot flash the ModdedPL832img file. I get a message "writing 'zip'....FAILED (remote not allowed)"
Any ideas/suggestions?
scheirere said:
OK, I got partway thru the steps. everything went well until I tried to fastboot flash the ModdedPL832img file. I get a message "writing 'zip'....FAILED (remote not allowed)"
Any ideas/suggestions?
Click to expand...
Click to collapse
After step 1, but before step 2, do this:
fastboot devices
If you don't get a device id, then you don't have the proper drivers installed.
If you get a device id, then try step 2 again ...
If that doesn't work, then I don't know
Maybe try a different USB port on your computer also use the OEM cable if you can.
Thanks guys for the suggestions. Unfortunately, still no luck. Same results when flashing the Modded file. I did try adb devices as suggested and got the device ID. So I think the drivers are OK. I also tried another USB port just to see if it helped. No go.
Just because I'm pretty new to this stuff, here's a detailed list of what I'm doing.....
1.) ADB reboot bootloader (from a command prompt)
Phone reboots to bootloader screen with Fastboot USB in red, hightlighted.
The screen no longer displays the "TAMPERED" heading at the top. So it looks like I'm making some progress.
2.) fastboot oem rebootRUU (from a command prompt again)
Phone screen goes from white to black with nothing but a large HTC logo in white.
Nothing else happens at this point. I've let the phone sit for 30 minutes with no apparent change and nothing on the host PC.
I then went thru my computer to the directory were the RUU_DLX.... file resides and executed (double clicked) it. I get an RUU - InstallShield screen and then I go thru the HTC rom update utility steps. After a few steps the utility does it's thing and the phone then reboots.
3.) ADB reboot bootloader again
Phone reboots into bootloader screen
4.) fastboot flash zip ModdedPL832IMG.zip (from a command prompt)
Phone does nothing but the command screen returns:
sending 'zip' (485 KB)...OKAY [ 0.266s]
writing 'zip'...FAILED (remote: not allowed)"
pretty much immediately
Am I doing this correctly?
At this point the bootloader screen no longer says tampered. Can I just relock the bootloader so it's s-on again?
BTW, here's what the bootloader screen shows:
*** UNLOCKED ***
MONARUDO PVT SHP S-OFF
CID-22222222
HBOOT-1.33.0001
RADIO-1.00.00.1023_3
OpenDSP-v4.120.240.0920
eMMC-boot
Oct 23 2012,21:34:05
Or can I just send the phone back as it is?
Bootloader uses a different driver than ADB. My advise is to boot into the bootloader then verify in device manager that the driver is loaded. See attached. Flashing the RUU will not get you S-On you need a command to do that and I don't know what it is off the top of my head I have never used it.