So today a client brings in her One Max to our shop and explains she bought it on eBay and it never mentioned being modded. The phone boots with a warning message and without doing the correct processes, manages to make it even worse. Currently we are able to boot it into recovery mode and we see:
*** UNLOCKED ***
T6WL PVT SHIP S-OFF RH
CID-VZW__001
HBOOT-2.49.0000
RADIO-1.36.60.0520
OpenDSP-v33.120.274_T6.0829
QSC-
OS-
eMMC-boot 2048MB
Sept 1 2015, 12:43:04.0
HBOOT
FASTBOOT
RECOVERY
FACTORY RESET
SIMLOCK
CHECK SMARTSD
IMAGE CRC
SHOW BARCODE
and at this point, I'm trying just to find a way to load the OEM ROM/Firmware to restore the phone back to factory. Any help/ideas?
@computermikes
Best thing is to run a RUU which will take it all back to factory defaults...
This right here should get it to work. http://flyhalf205.com/RUU/t6vzw/0P3...0_NV_VZW_4.60_002_release_385874_signed_1.exe
You'll need to make sure you have the fastboot drivers installed before attempting to run the file. Google is your friend to get that working...
If that doesn't work. I've always heard that running http://www.htc.com/us/software/htc-sync-manager/ you can recover the latest OEM software for Verizon phones.
NOTE: After running either one. You will need to get back into that HBOOT screen you typed out and select the option for factory reset.
Related
Hey all, I am thinking about selling my HOX+ and the buyer doesn't want the phone rooted for warranty purposes. Is there a way for me to remove root and restore everything to stock? Thanks in advance!
Please reboot in bootloader and tell me your hboot version and confirm AT&T/TELUS version.
I see HBOOT version but not the AT&T/Telus version.
Here's everything I see
EVITARE_UL PVT SHIP S-ON RL
HBOOT 1.32.0000
CPLD-None
MICROP-None
RADIO-SSD:1.09.55.17
eMMC-bootmode: disabled
CPU-bootmode: disabled
HW Secure boot: enabled
MODEM TYPE: MDM921
Oct 20 2012, 13:45:56
eyecrispy said:
I see HBOOT version but not the AT&T/Telus version.
EVITARE_UL PVT SHIP S-ON RL
Click to expand...
Click to collapse
Sure, this is the confirmation.
You need this RUU for your AT&T
Reboot in bootloader mode
Plug in your USB cable
Open a adb command window
At the prompt type>fastboot oem lock
Your phone will reboot.
Again in bootloader mode with FASTBOOT USB highlighted simply run the RUU downloaded
Your phone will be completely wiped including SD card.
What exactly is the RUU? What does it do?
Also, once I do that, how do I get the stock ROM back on it?
Also, once I get back to stock recovery how do I get back to bootloader?
RUU = ROM Update Utility
This will update and restore your phone to it's original state including boot, recovery, rom, etc. Your phone will be exactly like it was the first time you press the Power button.
To access Bootloader simply hold your Volume down rocker and press Power button.
I ran the RUU a few times and it has been stuck on the "Verifying information on your Android phone. Please wait ..." screen for a long time. How long does the RUU run?
I am running win7 from a virtual machine. Not sure if that makes a difference. But the RUU didn't seem to work. Do you have a MD5 for the RUU file you posted?
Would that work if you registered your phone on htcdev.com? Warranty will be void if you unlocked your device, it doesn't matter if its locked again.
eyecrispy said:
I ran the RUU a few times and it has been stuck on the "Verifying information on your Android phone. Please wait ..." screen for a long time. How long does the RUU run?
I am running win7 from a virtual machine. Not sure if that makes a difference. But the RUU didn't seem to work. Do you have a MD5 for the RUU file you posted?
Click to expand...
Click to collapse
Yes maybe the VM can be a problem, I will do search about this. One thing I know. some people says the needed many try before it worked.
MD5 : 3B951A3195E60712A62A4DB6AC181CC7
You can try this one if you want an alternative : RUU_EVITARE_UL_JB_45_Cingular_US
Thanks. What's the difference between the two exe files?
They are the same, only the source is different. Since I am having an TELUS phone I can't test if any of those files are working so I gave you two different source to download the file just "in case..."
In bootloader it will state re-locked after locking bootloader again so its not possible to get back all stock again.
Sent from my HTC One X+ using xda premium
Hi Folks,
since the microphon of my T-Mobile Germany HTC One broke, i went back to stock via Nandroid Backup flashed the matching firmware, locked the Bootloader and put S-On. Everything went fine. My Bootloader looked like this:
*** LOCKED ***
M7_UL PVT SHIP S-ON RH
CID-T-MOB101
HBOOT-1.44.0000
Afterwards i booted normally and tried to install the T-Mobile OTA Updates. I was able to download them correctly but after clicking install the phone booted into bootloader and showed the following:
*** TAMPERED ***
*** LOCKED ***
*** SECURITY WARNING ***
M7_UL PVT SHIP S-ON RH
CID-T-MOB101
HBOOT-1.44.0000
This happens every time I try to update via OTA. When i reboot normally the security warning doesn't appear but the Tampered flag still does. The phones boots normally and everything is working fine except updates!
I gained S-OFF originally with revone but right now i am not able to unlock and s-off through revone anymore. The proccess always stops with error code = -6. So I am not able to repeat what i did to gain stock.
Something strange I recognized is, that when i type "getvar version-main" with fastboot it shows 1.20.401.1 which is not the version number of the firmware i flashed (this was 1.29.161.11).
Any suggestions what to do now to remove the tampered flag, to unlock the bootloader and get back s-off to repeat all the steps, or a completely different way to solve the problem are welcome!
I have to return my One to T-Mobile with 100% Stock and the newest available version released and approved from the carrier in order to get a new one!
Thanks in advance!
Hello there, I am using an AT&T HTC One and have somehow screwed it up completely. I have ClockworkMod 6.0.3.1 installed and was trying to update my ROM to a 4.4 one, but it was a bad flash with some error, thus leading me to just restart it. However, I found that I cannot get past the HTC white screen, and it just reboots right into ClockworkMod without even being detected by my computer. I can access the bootloader, and recovery, but cannot get my computer or the adb services to recognize my phone. Is there anything I can do?
here is my bootloader screen btw:
*** TAMPERED ***
*** UNLOCKED ***
M7_UL PVT SHIP S-ON RH
HBOOT-1.55.000
RADIO-4A.19.3263.13
OpenDSP-v31.120.274.0617
OS-3.17.502.3
eMMC-boot 2048MB
Sep 10 2013,01:32:23.0
Let me know if there is anymore information that you need.
my phone's OS has been wiped via twrp v2.6.0 because i screwed something up and thought wiping the system would just wipe the change i made. clearly it wiped the entire OS and so now all i have is a device that can boot into botloader. i have tried several times to use th RUU that everyone said to use in order to revert it to the factory condition, but every time it comes back with the 158 error saying i dont have the correct ROM to put on it just after it attempts to update the signature. the RUU i downloaded is titled RUU_EVITARE_UL_JB_45_Cingular_US_1.15.502.9_Radio_1.09.55.17_18.20.95.55L_release_290329_signed.exe and i have had multiple sources say this is the one i need for my device yet every time i run the RUU it comes back with the same error. everything else about the RUU seemed to work. when i boot the device into bootloader the section at the top reads
*** RELOCKED ***
EVITARE_UL PVT SHIP S-ON RL
HBOOT-1.73.0000
CPLD-None
MICROP-None
RADIO-SSD:2.21.5517.15
eMMC-bootmode: disabled
CPU-bootmode : disabled
HW Secure boot:enabled
MODEM TYPE : MDM9215M
Sep 30 2013, 17:16:15
all i want is the correct RUU for my device and a working phone. i cant afford another phone and i need a working phone. please please somebody help.
Farrric said:
my phone's OS has been wiped via twrp v2.6.0 because i screwed something up and thought wiping the system would just wipe the change i made. clearly it wiped the entire OS and so now all i have is a device that can boot into botloader. i have tried several times to use th RUU that everyone said to use in order to revert it to the factory condition, but every time it comes back with the 158 error saying i dont have the correct ROM to put on it just after it attempts to update the signature. the RUU i downloaded is titled RUU_EVITARE_UL_JB_45_Cingular_US_1.15.502.9_Radio_1.09.55.17_18.20.95.55L_release_290329_signed.exe and i have had multiple sources say this is the one i need for my device yet every time i run the RUU it comes back with the same error. everything else about the RUU seemed to work. when i boot the device into bootloader the section at the top reads
*** RELOCKED ***
EVITARE_UL PVT SHIP S-ON RL
HBOOT-1.73.0000
CPLD-None
MICROP-None
RADIO-SSD:2.21.5517.15
eMMC-bootmode: disabled
CPU-bootmode : disabled
HW Secure boot:enabled
MODEM TYPE : MDM9215M
Sep 30 2013, 17:16:15
all i want is the correct RUU for my device and a working phone. i cant afford another phone and i need a working phone. please please somebody help.
Click to expand...
Click to collapse
I imagine you can have TWRP mount the storage and put one of the ROMs (like Elegencia) and then flash it.
Farrric said:
my phone's OS has been wiped via twrp v2.6.0 because i screwed something up and thought wiping the system would just wipe the change i made. clearly it wiped the entire OS and so now all i have is a device that can boot into botloader. i have tried several times to use th RUU that everyone said to use in order to revert it to the factory condition, but every time it comes back with the 158 error saying i dont have the correct ROM to put on it just after it attempts to update the signature. the RUU i downloaded is titled RUU_EVITARE_UL_JB_45_Cingular_US_1.15.502.9_Radio_1.09.55.17_18.20.95.55L_release_290329_signed.exe and i have had multiple sources say this is the one i need for my device yet every time i run the RUU it comes back with the same error. everything else about the RUU seemed to work. when i boot the device into bootloader the section at the top reads
*** RELOCKED ***
EVITARE_UL PVT SHIP S-ON RL
HBOOT-1.73.0000
CPLD-None
MICROP-None
RADIO-SSD:2.21.5517.15
eMMC-bootmode: disabled
CPU-bootmode : disabled
HW Secure boot:enabled
MODEM TYPE : MDM9215M
Sep 30 2013, 17:16:15
all i want is the correct RUU for my device and a working phone. i cant afford another phone and i need a working phone. please please somebody help.
Click to expand...
Click to collapse
according to your hboot you have the newest hboot (1.73)for the android 4.2.2 sense5 which is why the ruu you have wont flash that is the old 4.1.1 ruu meant for hboot 1.40 so youll either need to sideload a rom or wait for the official RUU to be released.
I was trying to unroot my phone and return to stock HTC Sense because I was having issues with the latest cyanogenmod and didn't want to deal with it anymore while I waited for the Samsung Galaxy note 4 to come out. After reading several tutorials I downloaded the latest Cingular RUU from a link on another thread here. I connected my phone through fastboot and ran "fastboot oem lock". After that when I ran the RUU it made it to where it begins the process and after the process started it gave me "error 158: image error". It's now stuck in fastboot and I can't find a way to get out of it, I've only ever installed custom roms through custom recovery so any concepts you say to try will probably be new to me so link to a tutorial or something. (I did try two RUUs from two different sources).
On my phone I see:
*** TAMPERED ***
*** RELOADED ***
*** Security Warning ***
M7_UL PVT SHIP S-ON RD
HBOOT-1.44.0000
RADIO-4A.17.3250.20
OpenDSP-v31.120.274.0617
eMMC-boot
Jul 5 2013,16:04:18:-1
With the options:
FASTBOOT
RECOVERY
FACTORY RESET
SIMLOCK
IMAGE CECT
SHOW BARCODE
I have refrained from trying any of the options for fear of messing things up farther, any help is much appreciated.
waffleman5132 said:
I was trying to unroot my phone and return to stock HTC Sense because I was having issues with the latest cyanogenmod and didn't want to deal with it anymore while I waited for the Samsung Galaxy note 4 to come out. After reading several tutorials I downloaded the latest Cingular RUU from a link on another thread here. I connected my phone through fastboot and ran "fastboot oem lock". After that when I ran the RUU it made it to where it begins the process and after the process started it gave me "error 158: image error". It's now stuck in fastboot and I can't find a way to get out of it, I've only ever installed custom roms through custom recovery so any concepts you say to try will probably be new to me so link to a tutorial or something. (I did try two RUUs from two different sources).
On my phone I see:
*** TAMPERED ***
*** RELOADED ***
*** Security Warning ***
M7_UL PVT SHIP S-ON RD
HBOOT-1.44.0000
RADIO-4A.17.3250.20
OpenDSP-v31.120.274.0617
eMMC-boot
Jul 5 2013,16:04:18:-1
With the options:
FASTBOOT
RECOVERY
FACTORY RESET
SIMLOCK
IMAGE CECT
SHOW BARCODE
I have refrained from trying any of the options for fear of messing things up farther, any help is much appreciated.
Click to expand...
Click to collapse
You have a very old hboot 1.44
you need to flash an old RUU first then a more recent one.
after the first RUU you should consider getting the phone s-off as it gets harder with the newer 1.57 hboot
http://dl3.htc.com/application/RUU_...13_10.38j.1157.04_release_334235_signed_2.exe
After you flash that your phone will try to update to 4.xx.502.x
if you want s-off don't take the update, instead unlock the bootloader and flash a custom rom and bulletproof kernel and get s-off with rumrunner or firewater
This worked thank you, you're awesome.
waffleman5132 said:
This worked thank you, you're awesome.
Click to expand...
Click to collapse
no problem ..use the thanks button I'm approaching 1000 thanks