Database Develop

[Tutorial][Rescue]Sprint HTC One users that flash GSM roms on their CDMA devices.

Hello XDA,
I have noticed a lot of Sprint(CDMA) HTC One users on the latest 4.3/4.4.2 OTA are flashing 4.3/4.4.2 GSM roms and soft bricking their devices lately.
I have personally rescued a several devices in the past couple months so I'm posting this guide in hopes that it will save some headaches and stress for Sprint users.
This guide is for Sprint HTC One users only.
3.04.651.2 RUU Thanks @OMJ
3.05.651.6 RUU From HTC
4.06.651.4 RUU Thanks @OMJ and @-viperboy-
5.03.651.3 RUU Thanks @OMJ **Note you will have to update your hboot to 1.57 in order for this RUU to work...solution is flash the 5.03.651.3 s-on firmware first.**
5.05.651.2 RUU
6.23.651.6 RUU Latest from htc.com
Device not recognized? (If you are using Windows 8.1 this will most likely not work unless your hboot is 1.55 or 1.56 or 1.57)
On your PC go to device manager and find your phone(usually M7WLS), right click and select properties
Select the driver tab
Select update driver
Select browse my comp
Let me pick
Look for ADB USB device or similar should be one of the first couple choices
Select MyHTC install and you should be good
Latest HTC Drivers AFH
Video showing how to flash the firmware Thanks @thoughtlesskyle
If you are S-OFF flash
3.04.651.2 s-off firmware
3.05.651.5 s-off firmware
3.05.651.6 s-off firmware
4.06.651.4 s-off firmware
5.03.651.3 s-off firmware
5.05.651.2 s-off firmware (Sense 6) and you are done.
If you are already on 4.06.651.4 or 4.06.651.9 you will have to flash the 3.05.651.6 s-off firmware first...reason being is the 4.06 s-off firmware does not have the latest radio included (use the same commands from 5.)
6.23.651.6 s-off firmware Latest and most likely the last.
**Note the 5.03.651.3 firmware has a new radio so no need to flash the older version to get the radio.**
If you are s-on follow these steps ALL the way to the end (there are no shortcuts unless you are s-off and step 9 is optional as noted)
1.Download
3.04.651.2 s-on firmware
3.05.651.5 s-on firmware
3.05.651.6 s-on firmware
4.06.651.4 s-on firmware
5.03.651.3 s-on firmware
5.05.651.2 s-on firmware (Sense 6)
6.23.651.6 s-on firmware Latest and most likely the last.
2.Rename it firmware.zip (put the firmware.zip into the platform tools folder or the folder attached below)
3.Boot to bootloader
4.Lock bootloader(fastboot oem lock)
5.Then use these commands:
Code:
Fastboot oem rebootRUU
Fastboot flash zip firmware.zip
Fastboot reboot-bootloader
6.If you get this error after the second command(most likely will)
Code:
failed 90 hboot pre-update! please flush image again immediately
press the UP Arrow on your keyboard and press enter to issue the command again.
7.Then unlock the bootloader again and re-flash Latest TWRP. (before formatting go to setting/screen and disable screen timeout)
8.Within Latest TWRP select Wipe > Format Data(it will ask you to confirm by typing YES) once done adb push a rom to your phone (adb push nameofrom.zip /sdcard/ ).
8a. If you are using the 4.06.651.4 s-on firmware I would suggest you push this Stock Rooted Odexed Rom to your device or it may not boot.
8b. After flashing the 4.06.651.4 rom you will most likely need to flash the latest radio because the 4.06 firmware does not have a radio included find it HERE
8c. If you are using the 5.03.651.3 s-on firmware I would suggest you push this 5.03.651.3_Stock | Rooted | 4.4.2 | Sense 6 to your device or it may not boot.
8d. If you are using the 6.23.651.6 s-on firmware I would suggest you push this [STOCK ROM] [5.0.2] [SENSE 6] Sprint 6.16.651.2 AND 6.23.651.3 to your device or it may not boot.
9.Optional but recommended: S-OFF using Sunshine
10.Win lol :victory:
Thanks @OMJ for the firmware
Thanks @thoughtlesskyle for the 5.03.651.3 firmware and stock odex rom
Thanks @beaups and @Fuses for Rumrunner and Firewater
Thanks @WayneQuasar for helping me figure out the correct order to do these steps(many hours and many failed attempts before we figured it out lol)
If you need assistance I'll be happy to help.
If you need help add me on hangouts [email protected]
First come first served please tell me your XDA name and a link to what you are having problems with.

bigdaddy619 said:
Hello XDA,
I have noticed a lot of Sprint(CDMA) HTC One users on the latest 4.3 OTA are flashing 4.3 GSM roms and soft bricking their devices lately.
I have personally rescued a few devices in the past week so I'm posting this guide in hopes that it will save some headaches and stress for Sprint users.
This guide is for Sprint HTC One users only.
Device not recognized? (If you are using Windows 8.1 this will most likely not work)
On your PC go to device manager and find your phone(usually M7WLS), right click and select properties
Select the driver tab
Select update driver
Select browse my comp
Let me pick
Look for ADB USB device or similar should be one of the first couple choices
Select MyHTC install and you should be good
1.Download the s-on firmware zip
2.Rename it firmware.zip (put the firmware.zip into the folder you use to open your cmd window or the folder attached below)
3.Boot to bootloader
4.Lock bootloader(fastboot oem lock)
5.Then use these commands:
Code:
Fastboot oem rebootRUU
Fastboot flash zip firmware.zip
Fastboot reboot-bootloader
6.If you get this error after the second command(most likely will)
Code:
failed 90 hboot pre-update! please flush image again
press the UP Arrow on your keyboard and press enter to issue the command again.
7.Then unlock the bootloader again and re-flash TWRP.
8.Within TWRP select Wipe > Format Data(it will ask you to confirm by typing YES) once done sideload or adb push a rom to your phone.
9.Optional but recommended: S-OFF using Rumrunner
10.Win lol :victory:
Thanks @OMJ for the firmware
Thanks @beaups and @Fuses for Rumrunner
Thanks @WayneQuasar for helping me figure out the correct order to do these steps(many hours and many failed attempts before we figured it out lol)
If you need assistance I'll be happy to help.
Click to expand...
Click to collapse
I have followed your steps exactly, after I flash TWRP I try to enter recovery and it says "entering recovery..." for a few seconds then goes to a normal boot to a black screen. What should I do?

Did you flash the Sprint version of twrp
http://techerrata.com/browse/twrp2/m7wls 2.6.3.0

bigdaddy619 said:
Did you flash the Sprint version of twrp
http://techerrata.com/browse/twrp2/m7wls 2.6.3.0
Click to expand...
Click to collapse
I think so, but I am going to try with the link you gave.
---------- Post added at 11:00 PM ---------- Previous post was at 10:53 PM ----------
bigdaddy619 said:
Did you flash the Sprint version of twrp
http://techerrata.com/browse/twrp2/m7wls 2.6.3.0
Click to expand...
Click to collapse
Okay this worked!! Sorry I am very new to this, I know how to sideload, but what ROM should I use? I just want to get to stock rooted. does that mean OMJ's?

MacSkizzle said:
I think so, but I am going to try with the link you gave.
---------- Post added at 11:00 PM ---------- Previous post was at 10:53 PM ----------
Okay this worked!! Sorry I am very new to this, I know how to sideload, but what ROM should I use? I just want to get to stock rooted. does that mean OMJ's?
Click to expand...
Click to collapse
You can use OMJ's stock rooted or there is a Reset tool in Development if you want completely stock

bigdaddy619 said:
You can use OMJ's stock rooted or there is a Reset tool in Development if you want completely stock
Click to expand...
Click to collapse
Thank you so much! You really don't know how much stress you've relieved from me.:highfive:

MacSkizzle said:
Thank you so much! You really don't know how much stress you've relieved from me.:highfive:
Click to expand...
Click to collapse
NP good luck and yes I do know I help 2-3 a day haha

bigdaddy619 said:
NP good luck and yes I do know I help 2-3 a day haha
Click to expand...
Click to collapse
You aren't in the clear yet. When I start ADB sideload, it forever says starting adb sideload feature... What now?

MacSkizzle said:
You aren't in the clear yet. When I start ADB sideload, it forever says starting adb sideload feature... What now?
Click to expand...
Click to collapse
You have to put the zip in the folder you are using to run your commands
type adb sideload romname.zip
Then press enter

bigdaddy619 said:
You have to put the zip in the folder you are using to run your commands
type adb sideload romname.zip
Then press enter
Click to expand...
Click to collapse
I did that and got error: device not found. my adb version is 1.0.31, is it something wrong with drivers? again thanks for bearing with me

MacSkizzle said:
I did that and got error: device not found. my adb version is 1.0.31, is it something wrong with drivers? again thanks for bearing with me
Click to expand...
Click to collapse
Look in post one to fix the drivers

bigdaddy619 said:
Look in post one to fix the drivers
Click to expand...
Click to collapse
I already had the MyHTC drivers installed. I'm still getting "Starting ADB sideload feature..." on my phone and "error device not found" in my command.

MacSkizzle said:
I already had the MyHTC drivers installed. I'm still getting "Starting ADB sideload feature..." on my phone and "error device not found" in my command.
Click to expand...
Click to collapse
Uninstall it and start over, I know there are a few versions maybe you are using an older version coz it sounds like a driver issue

bigdaddy619 said:
Uninstall it and start over, I know there are a few versions maybe you are using an older version coz it sounds like a driver issue
Click to expand...
Click to collapse
After uninstalling the driver, i found my M7WLS and went to update the driver. I selected "Android USB Devices" the only drivers available are samsung ones.?

MacSkizzle said:
After uninstalling the driver, i found my M7WLS and went to update the driver. I selected "Android USB Devices" the only drivers available are samsung ones.?
Click to expand...
Click to collapse
Get the latest drivers from HERE the ones dated 6/6/13 and also the BMP drivers

bigdaddy619 said:
Get the latest drivers from HERE the ones dated 6/6/13 and also the BMP drivers
Click to expand...
Click to collapse
Downloaded and installed them, now there's nothing like ADB USB devices in my drivers to choose

MacSkizzle said:
Downloaded and installed them, now there's nothing like ADB USB devices in my drivers to choose
Click to expand...
Click to collapse
It should be one of the first 2 choices
Also try unistalling everything HTC and reboot your PC and re-install

bigdaddy619 said:
It should be one of the first 2 choices
Click to expand...
Click to collapse
My first two choices are 61883 device class and avc devices. did i somehow install drivers wrong?!

Did you see my edit?

bigdaddy619 said:
Did you see my edit?
Click to expand...
Click to collapse
will try
---------- Post added at 12:58 AM ---------- Previous post was at 12:41 AM ----------
MacSkizzle said:
will try
Click to expand...
Click to collapse
So I got the drivers installed but when I enter adb sideload on my phone it still just says starting. I tried sideloading a rom anyways and a whole mess of stuff shows up but doesn't reboot my phone or anything.

[GUIDE] Returning to 100% Stock for O2-UK Customers

Hi All,
I have merely followed the instructions of other devs here to get my phone back to complete stock O2. I believe this guide could work for other carrier based models as well
Mods - Feel free to post this wherever or make any changes.
These are the steps I took to get back to S-ON, reset the ***TAMPERED*** flag and lock the bootloader. The reason why I post this is because I had several issues getting back to stock, and this is for anyone who is having the same issues
I had several scary messages when going back to S-ON when I thought I was completely stock, which included the "Security Warning" message in bootloader when running fastboot oem writesecureflag 3. I also had a message when booting up the stock ROM in 3.62.206.1 saying "TAMPER DETECTED - REBOOTING after trying fastboot oem writesecureflag 3. Once in bootloader, the tampered message re-appeared and I was S-ON and LOCKED. After running all the steps, I have been able to reboot several times and factory reset without the ***TAMPERED*** reappearing
Step 1: Getting S-off
If you are using bootloader 1.44 - Use Revone http://forum.xda-developers.com/showthread.php?t=2314582
For bootloaders 1.5x you should download the Sunshine app at http://theroot.ninja/
The closer you are to stock ROM/stock kernel the better. To S-off it will cost you a mere $25, but it works in 5 mins and no need for computers/adb commands
Step 2: Remove ***TAMPERED***
After getting S-OFF, reset the ***TAMPERED*** flag and lock the bootloader using the following commands from these posts http://forum.xda-developers.com/showthread.php?p=46183050#post46183050 and http://forum.xda-developers.com/showthread.php?t=2477792 (credit to scotty1223)
To LOCK the Bootloader
To LOCK your bootloader,enter the following:
adb devices
adb shell
su (if needed to get a # prompt)
echo -ne '\x00\x00\x00\x00' | dd of=/dev/block/mmcblk0p3 bs=1 seek=33796
(i would very strongly recomend you copy/paste this)
exit
(exit a second time if you need to to get back to a normal > prompt)
adb reboot bootloader
Click to expand...
Click to collapse
To reset the TAMPER in bootloader
Enter the following:
adb devices
adb shell
su (if needed to get a # prompt)
echo -ne '\x00' | dd of=/dev/block/mmcblk0p7 bs=1 seek=4265988
(i would very strongly recomend you copy/paste this)
exit
(exit a second time if you need to to get back to a normal > prompt)
adb reboot bootloader
Click to expand...
Click to collapse
Step 3: Downgrade your Hboot to 1.44
Download the Hboot 1.44 from http://www.htc1guru.com/dld/1-29-401-12_hboot_1-44-zip/
Before flashing, The android-info.txt file needs modified by clicking into the file (not extracting it) and changing the model ID to whatever your model is. This can be checked by running the command fastboot getvar all and checking the model ID number
Now flash the Hboot. To do this, boot to bootloader screen using the command adb reboot-bootloader
Type the following commands:
fastboot oem rebootRUU
fastboot flash zip 1.29.401.12_hboot_1.44.zip
After it finishes, execute the command again to complete the flash:
fastboot flash zip 1.29.401.12_hboot_1.44.zip
Fastboot reboot
Step 4: Run an earlier RUU from 1.29.xxx.xx
We need to run and earlier RUU first. For now, change CID to HTC__032
Download RUU_M7_UL_JB_50_HTC_Europe_1.28.401.7_Radio_4A.13. 3231.27_10.31.1131.05_release_310878_signed from thanks to crushalot, http://d-h.st/Gt8. This will reset the phone back to complete stock, but not stock for the original CID O2___001. Once the RUU installs, reboot into bootloader and run the following command
fastboot oem writecid O2___001.
Check your bootloader and you should see the phone is still S-OFF and the CID is now for O2.
Step 5: Getting S-OFF again
This is if for some reason the phone has gone back to S-ON. To be honest, I did this step anyways just to be safe. Download, push and flash revone using the commands on the toolkit and ensure that the phone is not ***TAMPERED***
Using Revone, Unlock the bootloader - adb reboot bootloader to check it is unlocked
Step 6: Restoring an earlier backup
Download M7 CWM Nandroid Backup CID O2__102 1.27.206.1 2013-03-30 from crushalot's page on XDA and extract the file to the PC until you have a folder with a date on it and time (2013-03-11.17.58.27)
Make a new folder in your HTC one called clockworkmod. Inside here place a new folder called backup (all lower case). Place the backup here
Also, download http://forum.xda-developers.com/showthread.php?t=2200628 and place onto your SD Card. Once you flash the nandroid backup, go ahead and flash this. It will fix the missing preload apps (calculator, flashlight etc) which happens when unlocking the bootloader, and if these apps are missing can cause future OTA's to fail
Download CWM recovery and rename to CWMTG.img and place in your adb folder. You can also download Hassoon's Toolkit and copy the recovery from there if you like. At this point, ensure your bootloader is UNLOCKED.
From the fasboot menu, type the following
Fastboot boot CWMTG.img
This will boot into the recovery without installing it. Restore the nandroid backup you downloaded earlier and install the preload fix. Reboot
Step 7: Restoring stock recovery, Locking the Bootloader and install updates via OTA
Download the stock recovery for O2 from here http://d-h.st/l1q and flash via fastboot
Once booted up, lock the bootloader using Revone and remove tampered (run the command anyway even if it doesn't say ***TAMPERED***. Check for OTA - The one I got was for 2.24.206.1
Step 8: Returning to S-ON
Verify that the bootloader is LOCKED, not ***TAMPERED*** and hboot is 1.54 with the OS confirming your firmware
Type the command: Fastboot oem writesecureflag 3
Enjoy complete stock and continue with the OTA's
If I helped in any way just click thanks!

Hi,
I followed your instructions up to point 13 - which is where the first problems in your instructions start. The page you are referring to doesn't exist anymore. Unfortunately you also didn't mention what exactly needs to be downloaded, which means people don't know what they have to look for. All I found was "trickdroid". Is that the one you were referring to?
14 - my bootloader is still unlocked, however I followed these instrucktions
16 - I am unable to boot any other image. During the steps you posted - which I followed - at some stage my system went S-ON. Revone is unable to map memory (and noone actually is able to answer me what that means even though there are many people that seem to have that issue) and rumrunner also is not capable anymore of bypassing the S-ON.
I don't know why I can't boot a recovery image, I assume it is because of the S-ON? There is for a millisecond a bootscreen with a red error message text, however I can't read it, because it's too fast.
So I am basically two steps away from getting back to stock and I don't know what to do so I can boot into the recovery image.
HTC One / O2 / hboot 1.44
Could anyone help me with this? I really don't know what to do and I have no experience whatsoever. And I don't wanna break my phone more than it is already

dispereo said:
Hi,
I followed your instructions up to point 13 - which is where the first problems in your instructions start. The page you are referring to doesn't exist anymore. Unfortunately you also didn't mention what exactly needs to be downloaded, which means people don't know what they have to look for. All I found was "trickdroid". Is that the one you were referring to?
14 - my bootloader is still unlocked, however I followed these instrucktions
16 - I am unable to boot any other image. During the steps you posted - which I followed - at some stage my system went S-ON. Revone is unable to map memory (and noone actually is able to answer me what that means even though there are many people that seem to have that issue) and rumrunner also is not capable anymore of bypassing the S-ON.
I don't know why I can't boot a recovery image, I assume it is because of the S-ON? There is for a millisecond a bootscreen with a red error message text, however I can't read it, because it's too fast.
So I am basically two steps away from getting back to stock and I don't know what to do so I can boot into the recovery image.
HTC One / O2 / hboot 1.44
Could anyone help me with this? I really don't know what to do and I have no experience whatsoever. And I don't wanna break my phone more than it is already
Click to expand...
Click to collapse
Don't know why the links don't post correctly - 13: http://forum.xda-developers.com/showthread.php?t=2200628

dispereo said:
Hi,
I followed your instructions up to point 13 - which is where the first problems in your instructions start. The page you are referring to doesn't exist anymore. Unfortunately you also didn't mention what exactly needs to be downloaded, which means people don't know what they have to look for. All I found was "trickdroid". Is that the one you were referring to?
14 - my bootloader is still unlocked, however I followed these instrucktions
16 - I am unable to boot any other image. During the steps you posted - which I followed - at some stage my system went S-ON. Revone is unable to map memory (and noone actually is able to answer me what that means even though there are many people that seem to have that issue) and rumrunner also is not capable anymore of bypassing the S-ON.
I don't know why I can't boot a recovery image, I assume it is because of the S-ON? There is for a millisecond a bootscreen with a red error message text, however I can't read it, because it's too fast.
So I am basically two steps away from getting back to stock and I don't know what to do so I can boot into the recovery image.
HTC One / O2 / hboot 1.44
Could anyone help me with this? I really don't know what to do and I have no experience whatsoever. And I don't wanna break my phone more than it is already
Click to expand...
Click to collapse
I also had the failed map memory error. Only way I could fix it was by repeating the command until it worked. Only happened once bit I'm aware of this being an issue
As for booting into the recovery image - is the image in your fastboot folder? And are you typing fastboot boot CWMTG.img (or whatever name.img)
Wt is the status of the bootloader?

stovie_steve said:
I also had the failed map memory error. Only way I could fix it was by repeating the command until it worked. Only happened once bit I'm aware of this being an issue
As for booting into the recovery image - is the image in your fastboot folder? And are you typing fastboot boot CWMTG.img (or whatever name.img)
Wt is the status of the bootloader?
Click to expand...
Click to collapse
Also the red error message is because you are booting into a custom recovery and this is normal. It would also say entering recovery at the top of the screen. Are you using the CWMTG.img from hasoon's toolkit in your fastboot/adb folder?

stovie_steve said:
I also had the failed map memory error. Only way I could fix it was by repeating the command until it worked. Only happened once bit I'm aware of this being an issue
As for booting into the recovery image - is the image in your fastboot folder? And are you typing fastboot boot CWMTG.img (or whatever name.img)
Wt is the status of the bootloader?
Click to expand...
Click to collapse
I've been repeating it over and over again (rough guess, about 15x) and it doesn't work. Still the map memory error.
I put the recovery-clockwork-6.0.4.3-m7ul.img (and I tried 2 others on their website) in the c:\android (where my adb/fastboot exe are in)
My bootloader says "unlocked" (however I manually unlocked again, just in case) - no change.
I entered fastboot boot recovery-clockwork-6.0.4.3-m7ul.img and then it just reboots (assuming it crashes and has the failsafe reboot)
---------- Post added at 02:18 AM ---------- Previous post was at 02:10 AM ----------
stovie_steve said:
Also the red error message is because you are booting into a custom recovery and this is normal. It would also say entering recovery at the top of the screen. Are you using the CWMTG.img from hasoon's toolkit in your fastboot/adb folder?
Click to expand...
Click to collapse
No I downloaded it manually. Because you say "fastboot boot" it won't flash it. But Hasoon's tool says "flash recovery" which sounds to me like overwriting (flashing) the current original, that would be thing i don't want. So i am a bit confused there.

dispereo said:
I've been repeating it over and over again (rough guess, about 15x) and it doesn't work. Still the map memory error.
I put the recovery-clockwork-6.0.4.3-m7ul.img (and I tried 2 others on their website) in the c:\android (where my adb/fastboot exe are in)
My bootloader says "unlocked" (however I manually unlocked again, just in case) - no change.
I entered fastboot boot recovery-clockwork-6.0.4.3-m7ul.img and then it just reboots (assuming it crashes and has the failsafe reboot)
---------- Post added at 02:18 AM ---------- Previous post was at 02:10 AM ----------
No I downloaded it manually. Because you say "fastboot boot" it won't flash it. But Hasoon's tool says "flash recovery" which sounds to me like overwriting (flashing) the current original, that would be thing i don't want. So i am a bit confused there.
Click to expand...
Click to collapse
What I did was pull the recovery image from hasoon's toolkit, not download the recovery image from the website. If you download the toolkit and go to the directory where you downloaded it there is a folder called recoveries where I copied the image to my adb folder. I did NOT use the toolkit as this involved flashing it so please try it that way instead of downloading it from the website
As for manually unlocking again - how to you do this without revone working? And put of curiosity are you using the toolkit to push/flash revone? If so I would reboot the phone between every step and try it again
Try that and see

stovie_steve said:
What I did was pull the recovery image from hasoon's toolkit, not download the recovery image from the website. If you download the toolkit and go to the directory where you downloaded it there is a folder called recoveries where I copied the image to my adb folder. I did NOT use the toolkit as this involved flashing it so please try it that way instead of downloading it from the website
As for manually unlocking again - how to you do this without revone working? And put of curiosity are you using the toolkit to push/flash revone? If so I would reboot the phone between every step and try it again
Try that and see
Click to expand...
Click to collapse
I got to 17 now (had to adjust minor things to get that work, thanks for your help!) and the problem is, my phone obviously doesn't support revone anymore as it doesn't have the permissions. Can I lock manually (with the HTC Dev command?) and I haven't had a ****TAMPERED**** since I installed the RUU.zip, do I still need to do 17. remove the tampered flag ? If so, how to do that with revone not having the permissions?
Almost there... almost there... *nervous*

So, I updated, I couldn't wait for a reply.
Now I've got "relocked" in the hboot, which is the way HTC Dev intended it (as far as I understand). Is there a way to get rid of that afterwards?

dispereo said:
So, I updated, I couldn't wait for a reply.
Now I've got "relocked" in the hboot, which is the way HTC Dev intended it (as far as I understand). Is there a way to get rid of that afterwards?
Click to expand...
Click to collapse
you should set it to LOCKED (not relocked), using either revone or http://forum.xda-developers.com/showthread.php?t=2475914 (or any of the other method available)

Thanks! Will have a look into that. So my phone updated without an issue now, and I am on Android 4.3 actually which made me wonder... if I ever do have to do a factory reset, what's the phone being reset to? Do you know that by chance?

dispereo said:
Thanks! Will have a look into that. So my phone updated without an issue now, and I am on Android 4.3 actually which made me wonder... if I ever do have to do a factory reset, what's the phone being reset to? Do you know that by chance?
Click to expand...
Click to collapse
Factory reset will just wipe everything (rephrase DATA) off your phone, it will not change ROM, firmware or anything like that, so it will remain on 4.3

nkk71 said:
Factory reset will just wipe everything (rephrase DATA) off your phone, it will not change ROM, firmware or anything like that, so it will remain on 4.3
Click to expand...
Click to collapse
Awesome, thanks for that. Phew. So now I am just stuck on a "re-locked" bootloader because rumrunner can't seem to find a way to get S-OFF again, as hboot 1.55 was installed. So i prolly got to wait until someone found a way to do that.
Thanks A LOT (!!!) for your help!

dispereo said:
Awesome, thanks for that. Phew. So now I am just stuck on a "re-locked" bootloader because rumrunner can't seem to find a way to get S-OFF again. So i prolly got to wait until someone found a way to do that.
Thanks A LOT (!!!) for your help!
Click to expand...
Click to collapse
No problem
As for rumrunner it should work on 4.3 (ie base 3.62.xxx.x), if it's currently not, the guys are updating it quite frequently, but if I recall correctly, it's best to have unlocked bootloader and ROOT.
Cheers

nkk71 said:
No problem
As for rumrunner it should work on 4.3 (ie base 3.62.xxx.x), if it's currently not, the guys are updating it quite frequently, but if I recall correctly, it's best to have unlocked bootloader and ROOT.
Cheers
Click to expand...
Click to collapse
I found a major issue here... when you boot it up and are in the setup screen, it says in red:
This is a test device. Tell HTC is automatically enabled so that HTC can collect critical information about the device during testing. It is not possible to turn this feature off on this phone.
Where did that come from? That sucks...

dispereo said:
I found a major issue here... when you boot it up and are in the setup screen, it says in red:
This is a test device. Tell HTC is automatically enabled so that HTC can collect critical information about the device during testing. It is not possible to turn this feature off on this phone.
Where did that come from? That sucks...
Click to expand...
Click to collapse
That usually comes if you have S-Off, I though you said you went back S-On

nkk71 said:
That usually comes if you have S-Off, I though you said you went back S-On
Click to expand...
Click to collapse
I did! Weird... I am repeating the procedure again.
---------- Post added at 07:32 PM ---------- Previous post was at 07:09 PM ----------
dispereo said:
I did! Weird... I am repeating the procedure again.
Click to expand...
Click to collapse
The bootloader is definitely unlocked as I just did it manually again with the HTC Dev unlock_token.bin.
The locking procedure from the website you posted:
C:\Android>adb shell
[email protected]:/ $ su
su
/system/bin/sh: su: not found
127|[email protected]:/ $ echo -ne '\x00\x00\x00\x00' | dd of=/dev/block/mmcblk0p3 bs=1
seek=33796
dd of=/dev/block/mmcblk0p3 bs=1 seek=33796 <
/dev/block/mmcblk0p3: cannot open for write: Permission denied
1|[email protected]:/ $
Rumrunner:
!! Do NOT for any reason taunt, unplug, drop, eat or pet your device !!
Please wait....
..........
Checking for updates......
Test 1: Rebooting into bootloader
Waiting for fastboot (6/120)
Waiting
Test 2: Booting device
Waiting for ADB (28/120)
Device detected.....................
[------------------------------------------------------------]
Rebooting into bootloader (again)
Waiting for fastboot (6/120)
Waiting for ADB (27/120)
ERROR: looks like device is not rooted AND lacks an unsecure kernel. su or FU!!
!
Press ENTER to exit
---------- Post added at 07:37 PM ---------- Previous post was at 07:32 PM ----------
dispereo said:
I did! Weird... I am repeating the procedure again.
---------- Post added at 07:32 PM ---------- Previous post was at 07:09 PM ----------
The bootloader is definitely unlocked as I just did it manually again with the HTC Dev unlock_token.bin.
The locking procedure from the website you posted:
C:\Android>adb shell
[email protected]:/ $ su
su
/system/bin/sh: su: not found
127|[email protected]:/ $ echo -ne '\x00\x00\x00\x00' | dd of=/dev/block/mmcblk0p3 bs=1
seek=33796
dd of=/dev/block/mmcblk0p3 bs=1 seek=33796 <
/dev/block/mmcblk0p3: cannot open for write: Permission denied
1|[email protected]:/ $
Rumrunner:
!! Do NOT for any reason taunt, unplug, drop, eat or pet your device !!
Please wait....
..........
Checking for updates......
Test 1: Rebooting into bootloader
Waiting for fastboot (6/120)
Waiting
Test 2: Booting device
Waiting for ADB (28/120)
Device detected.....................
[------------------------------------------------------------]
Rebooting into bootloader (again)
Waiting for fastboot (6/120)
Waiting for ADB (27/120)
ERROR: looks like device is not rooted AND lacks an unsecure kernel. su or FU!!
!
Press ENTER to exit
Click to expand...
Click to collapse
And someone had the same question here:
http://forum.xda-developers.com/showthread.php?t=2470957
Apparently with 1.55 it's not possible to get S-OFF (even though I didn't go S-ON at any stage, at least not myself...)

dispereo said:
Apparently with 1.55 it's not possible to get S-OFF (even though I didn't go S-ON at any stage, at least not myself...)
Click to expand...
Click to collapse
I'm 100% sure that before rumrunner was changed to a universal toolkit, there were quite a few packages for base 3.xx (hboot 1.55) including 3.62.401.x and they worked.
But like your output said:
ERROR: looks like device is not rooted AND lacks an unsecure kernel. su or FU!!
Click to expand...
Click to collapse
you would need to flash a ROM with ROOT (maybe a Guru Reset) compatible with your firmware for it to work. (obviously you need to be unlocked to flash ROM)
Also, going from S-Off to S-On on hboot 1.55 will result in "tamper detected - rebooting" and showing TAMPERED again, so you'll need to do that before hboot 1.55 (at least I'm well over 50% sure of that by now).
If the universal rumrunner tool really does not work for you at this time, I'm sure they're fixing it and it will be along soon.
EDIT: fastboot oem writesecureflag 3 is what makes you go S-On, and you have to do it, no way it's done by itself

nkk71 said:
I'm 100% sure that before rumrunner was changed to a universal toolkit, there were quite a few packages for base 3.xx (hboot 1.55) including 3.62.401.x and they worked.
But like your output said:
you would need to flash a ROM with ROOT (maybe a Guru Reset) compatible with your firmware for it to work. (obviously you need to be unlocked to flash ROM)
Also, going from S-Off to S-On on hboot 1.55 will result in "tamper detected - rebooting" and showing TAMPERED again, so you'll need to do that before hboot 1.55 (at least I'm well over 50% sure of that by now).
If the universal rumrunner tool really does not work for you at this time, I'm sure they're fixing it and it will be along soon.
EDIT: fastboot oem writesecureflag 3 is what makes you go S-On, and you have to do it, no way it's done by itself
Click to expand...
Click to collapse
I might have done that, even though I thought I left that out. However, my bootloader says ***** relocked ***** , that's all. It doesn't say ***** tampered ***** (that definitely disappeared after putting the ruu.zip on, I didn't have to do anything. i was wondering about that because you specifially mention it in your walkthrough but for me it disappeared automatically right at the start of the procedure.)

dispereo said:
I might have done that, even though I thought I left that out.
Click to expand...
Click to collapse
No way to go S-On without doing it yourself, no big deal, as long as you can unlock again.
dispereo said:
It doesn't say ***** tampered ***** (that definitely disappeared after putting the ruu.zip on
Click to expand...
Click to collapse
In theory, as long as you have stock ROM and stock recovery, the tampered should not show up, even if unlocked (S-On or S-Off), however for some, it did stay, even under those conditions. no real idea why. repeating myself: tampered should go away as soon as you have stock recovery.
dispereo said:
i was wondering about that because you specifially mention it in your walkthrough
Click to expand...
Click to collapse
Not my guide, it's @stovie_steve guide. I'm just visiting :cyclops:
So if you want to start over again, you need to get unlocked, flash a ROM compatible with your current firmware, which has root, and use rumrunner to get s-off.
I'm off for tonight see you guys around....

[SOLVED] HTC One Bootloader Unlock

Hey, i have tried to unlock the bootloader a few times but there appears no disclaimer. I have used the instruction from several websites.
I type in the CMD the command: fastboot flash unlocktoken Unlock_code.bin and after one second he has finished that but it happens nothing on the phone.
Can anybody help me?

steini793 said:
Hey, i have tried to unlock the bootloader a few times but there appears no disclaimer. I have used the instruction from several websites.
I type in the CMD the command: fastboot flash unlocktoken Unlock_code.bin and after one second he has finished that but it happens nothing on the phone.
Can anybody help me?
Click to expand...
Click to collapse
please post a "fastboot getvar all" (excluding IMEI and s/n) and a screenshot of bootloader

Ok they are in the attachment.

steini793 said:
Ok they are in the attachment.
Click to expand...
Click to collapse
1- GPE -> have you tried "fastboot oem unlock"
2- what kind of recovery do you have?

I have tried it now but i get an error and nothing else happens.
i dont know which kind i cant open it. When i klick on recovery there comes "no command".
EDIT: Nothing works...
I've downgraded my hboot to version 1.44 and then i tried revone but it also dont work.

steini793 said:
I have tried it now but i get an error and nothing else happens.
i dont know which kind i cant open it. When i klick on recovery there comes "no command".
EDIT: Nothing works...
I've downgraded my hboot to version 1.44 and then i tried revone but it also dont work.
Click to expand...
Click to collapse
you have stock recovery and your phone is not responding to fastboot devices ... are you using windows 8.1 ?
From stock recovery you push power + vol+ to see the menu
this is what you should see
Unlock your bootloader, but do not flash your custom recovery yet.
Reboot.
Your device will force-boot into stock recovery, wipe data and cache, then reboot again.
Let the device boot all the way to the welcome screen.
Reboot back into fastboot mode.
Flash the custom recovery and fastboot erase cache.
Reboot.
Click to expand...
Click to collapse

steini793 said:
I have tried it now but i get an error and nothing else happens.
i dont know which kind i cant open it. When i klick on recovery there comes "no command".
EDIT: Nothing works...
I've downgraded my hboot to version 1.44 and then i tried revone but it also dont work.
Click to expand...
Click to collapse
since you're locked, you won't be able to flash anything normally, but you can flash firmware.zip in RUU mode since you are S-Off, so here's a thought:
use the TWRP recovery "firmware" by @cschmitt http://forum.xda-developers.com/showpost.php?p=49635087&postcount=9
you flash that in ruu mode, so
fastboot oem rebootRUU
fastboot flash zip firmware_twrp.zip <- make sure it says Successful
fastboot reboot-bootloader
this it what the output will look like: http://forum.xda-developers.com/showpost.php?p=49666237&postcount=13
then enter recovery, and use adb commands (in TWRP) to unlock bootloader: http://forum.xda-developers.com/showthread.php?t=2475914

@nkk71
it doesnt work it comes custom id check fail
Can i change the cid number in the android.txt file in the zip?

steini793 said:
@nkk71
it doesnt work it comes custom id check fail
Click to expand...
Click to collapse
i just checked and GOOGL001 is in there:
Code:
modelid: PN0710000
modelid: PN0711000
modelid: PN0712000
modelid: PN0713000
modelid: PN0714000
modelid: PN071****
cidnum: 11111111
cidnum: T-MOB010
cidnum: CWS__001
cidnum: BS_US001
cidnum: GOOGL001
just temporarily change to SuperCID:
fastboot oem writecid 11111111" <- eight ones
fastboot reboot-bootloader
and try again
PS: copy/paste is usually easier to read than screenshots (either set Command Prompt properties to QuickEdit), or check the attachment

and edroyer
Ok thanks it works, i have now installed the zip and i am in the Recovery
but how can i use the adb commands in the TWRP?

steini793 said:
Ok thanks it works, i have now installed the zip and i am in the Recovery
but how can i use the adb commands in the TWRP?
Click to expand...
Click to collapse
adb works just fine in recovery, type adb devices
and it should come back with your serial number followed by "recovery" indicating you are in recovery
then use the adb commands to UNLOCK

Yes the bootloader is unlocked now, thanks so much for your help

steini793 said:
Yes the bootloader is unlocked now, thanks so much for your help
Click to expand...
Click to collapse
no problem, feel free to hit the thanks button, and also edit the main thread title to include [SOLVED] thanks.
remember to stay S-Off!!

[Q] Trouble with [OS - 1.10.605.2]

Having trouble with this OS because I want to update to (Sense 5.5) (4.4.2) but I'm stuck on (Sense 5.0) (4.2.2). Just becoming extremely frustrated and cannot find a firmware update to move my OS up to 1.10.605.10 or even 1.10.605.8.
I am on Verizon and have HBOOT - 1.54, Superuser, S-OFF, and Bootloader Unlocked. Right now after what I have been reading today it seems as if I am stuck with this OS and wont be able to receive the OTA updates to get a better ROM.
Although one good thing that happened is I just got my recovery working today thanks to "philz_touch_6.19.3-m7vzw"
So if anybody and I mean anybody has any suggestions on how I can do this or even point me in the direction of the best ROM for my requirements it would be greatly appreciated.
I do not remember rooting being this difficult with my Thunderbolt.
Best regards,

xxshererxx said:
Having trouble with this OS because I want to update to (Sense 5.5) (4.4.2) but I'm stuck on (Sense 5.0) (4.2.2). Just becoming extremely frustrated and cannot find a firmware update to move my OS up to 1.10.605.10 or even 1.10.605.8.
I am on Verizon and have HBOOT - 1.54, Superuser, S-OFF, and Bootloader Unlocked. Right now after what I have been reading today it seems as if I am stuck with this OS and wont be able to receive the OTA updates to get a better ROM.
Although one good thing that happened is I just got my recovery working today thanks to "philz_touch_6.19.3-m7vzw"
So if anybody and I mean anybody has any suggestions on how I can do this or even point me in the direction of the best ROM for my requirements it would be greatly appreciated.
I do not remember rooting being this difficult with my Thunderbolt.
Best regards,
Click to expand...
Click to collapse
does the phone even see any updates available ?

clsA said:
does the phone even see any updates available ?
Click to expand...
Click to collapse
No it does not...

xxshererxx said:
No it does not...
Click to expand...
Click to collapse
this RUU will get you to .10
http://www.htc1guru.com/dld/ruu-zip-m7_wl_jb_50_vzw_1-10-605-10_decrypted-zip/
Instructions for Flashing RUU Zip Files:
Download the RUU.zip file and place in your ADB/fastboot folder. I would recommend renaming the zip file to something simple like ruu.zip.
Boot your phone into the bootloader by holding the power and vol up/down buttons at the same time until you see the bootloader screen or if you have your phone booted you can use the ADB command:
adb reboot-bootloader
Now use these fastboot commands:
fastboot oem rebootRUU
Should see the Silver HTC logo. Now issue this command to flash your phone using the ruu.zip file:
fastboot flash zip ruu.zip
Now the first time you issue a command to flash firmware/ruu in fastboot it only prepares the flash. You have to issue the exact command again:
fastboot flash zip ruu.zip
The green status bar usually does not reach the 100% mark. When the output in the command window is complete, you can reboot:
fastboot reboot
**Notes about the RUU.zip method. You still need to have the proper CID for the RUU. You can run the RUU.zip with super CID, but you will have to lock your bootloader first. If you are running the RUU.zip as base to downgrade all your firmware because you are going to then going to restore a stock Nandroid so the RUU might not be made for your MID, so you may need to edit the android-info.txt inside the ruu.zip to include your MID or CID.

clsA said:
this RUU will get you to .10
Instructions for Flashing RUU Zip Files:
Download the RUU.zip file and place in your ADB/fastboot folder. I would recommend renaming the zip file to something simple like ruu.zip.
Boot your phone into the bootloader by holding the power and vol up/down buttons at the same time until you see the bootloader screen or if you have your phone booted you can use the ADB command:
adb reboot-bootloader
Now use these fastboot commands:
fastboot oem rebootRUU
Should see the Silver HTC logo. Now issue this command to flash your phone using the ruu.zip file:
fastboot flash zip ruu.zip
Now the first time you issue a command to flash firmware/ruu in fastboot it only prepares the flash. You have to issue the exact command again:
fastboot flash zip ruu.zip
The green status bar usually does not reach the 100% mark. When the output in the command window is complete, you can reboot:
fastboot reboot
**Notes about the RUU.zip method. You still need to have the proper CID for the RUU. You can run the RUU.zip with super CID, but you will have to lock your bootloader first. If you are running the RUU.zip as base to downgrade all your firmware because you are going to then going to restore a stock Nandroid so the RUU might not be made for your MID, so you may need to edit the android-info.txt inside the ruu.zip to include your MID or CID.
Click to expand...
Click to collapse
Just curious so after I flash this RUU, what is my next step? To download a custom ROM suitable for 4.4.2?

xxshererxx said:
Just curious so after I flash this RUU, what is my next step? To download a custom ROM suitable for 4.4.2?
Click to expand...
Click to collapse
no... hopefully get the OTA update

clsA said:
no... hopefully get the OTA update
Click to expand...
Click to collapse
Ok, so lets say it all works and I install the OTA update. Then what?

Also I'm "SuperCID 11111111" probably should have mentioned this earlier.
Everything worked and had no issues, but now I'm confused on what to do next.
I don't want to install the newest OTA update because it seems that people are having issues with it.

xxshererxx said:
Also I'm "SuperCID 11111111" probably should have mentioned this earlier.
Everything worked and had no issues, but now I'm confused on what to do next.
I don't want to install the newest OTA update because it seems that people are having issues with it.
Click to expand...
Click to collapse
Then just flash back to your custom recovery and root the phone
flash this from recovery >> http://download.chainfire.eu/382/SuperSU/UPDATE-SuperSU-v1.93.zip
Also if you choose to flash roms please stay in the Verizon forums.. most of the Roms you find in this area are not for your phone

clsA said:
Then just flash back to your custom recovery and root the phone
flash this from recovery >> http://download.chainfire.eu/382/SuperSU/UPDATE-SuperSU-v1.93.zip
Also if you choose to flash roms please stay in the Verizon forums.. most of the Roms you find in this area are not for your phone
Click to expand...
Click to collapse
Alright so after tinkering around all day I have, HBoot-1.56, with KitKat 4.4.2, and OS- 3.11.605.1.
I have the bootloader unlocked thanks to SuperCID
Also S-OFF
I just cant find a way to root it or which recovery to flash on it.
Any suggestions?

xxshererxx said:
Alright so after tinkering around all day I have, HBoot-1.56, with KitKat 4.4.2, and OS- 3.11.605.1.
I have the bootloader unlocked thanks to SuperCID
Also S-OFF
I just cant find a way to root it or which recovery to flash on it.
Any suggestions?
Click to expand...
Click to collapse
Are you still stuck ? OS- 3.11.605.1 is not android 4.4.2 it's 4.3
what happened to the recovery you used in the first post ?
openrecovery-twrp-2.6.3.4-m7vzw.img
http://flyhalf205.com/getdownload.php?file=recoveries/openrecovery-twrp-2.6.3.4-m7vzw.img

Yeah I was a little to tired to realize what I was talking about last night.
I was going back and forth between studying java, ascii, and unix for my exam earlier today and trying to get my phone squared away.
Now I'm curious about updating my baseband unless it really won't make much of a difference.
But this is where I ended up at.
Sent from my HTC6500LVW using xda app-developers app

[Q] htc one m7 ul soft bricked, no recovery, s-on, bootloader relocked

Hi, i know i'm an idiot. someone please help me
i have an htc one (m7)
unlocked bootloader (wroked fine)
tried rooting (worked fine)
installed custom recovery
tried flashing a custom rom, my nephew pressed the power button and the computer shut down.
now i have an expensive brick to play with.
have been looking for an ruu file to flash via hassoon's toolkit but i have found nothing but broken files.
CID: HTC001
modelid: pn0710000
Bootloader: relocked
S-on
No recovery installed. (error comes up when trying to flash a new one via fastboot cmd)
Please help! :good:

darrylu8 said:
Hi, i know i'm an idiot. someone please help me
i have an htc one (m7)
unlocked bootloader (wroked fine)
tried rooting (worked fine)
installed custom recovery
tried flashing a custom rom, my nephew pressed the power button and the computer shut down.
now i have an expensive brick to play with.
have been looking for an ruu file to flash via hassoon's toolkit but i have found nothing but broken files.
CID: HTC001
modelid: pn0710000
Bootloader: relocked
S-on
No recovery installed. (error comes up when trying to flash a new one via fastboot cmd)
Please help! :good:
Click to expand...
Click to collapse
The PC has nothing to do with flashing a rom ... what really happened

clsA said:
The PC has nothing to do with flashing a rom ... what really happened
Click to expand...
Click to collapse
it was while i tried to flash via the toolkit. was an error message came up, (can't remember what it said)
i just need to find a way to get s-off while my phone has nothing on it. theres no recovery (option is there though!)
i have bootloader/fastboot access. read somewhere that i have to relock the bootloader to flash an ruu. but others say i need s-off and the bootloader doesn't matter. its getting quite frustrating lol

darrylu8 said:
it was while i tried to flash via the toolkit. was an error message came up, (can't remember what it said)
i just need to find a way to get s-off while my phone has nothing on it. theres no recovery (option is there though!)
i have bootloader/fastboot access. read somewhere that i have to relock the bootloader to flash an ruu. but others say i need s-off and the bootloader doesn't matter. its getting quite frustrating lol
Click to expand...
Click to collapse
Yeah calm down ...
ditch the toolkit and just install fastboot/adb
use the zip below to make a fastboot folder in c:\
we'll be working from their
I'll post the steps you need to get your phone up and running

clsA said:
Yeah calm down ...
ditch the toolkit and just install fastboot/adb
use the zip below to make a fastboot folder in c:\
we'll be working from their
I'll post the steps you need to get your phone up and running
Click to expand...
Click to collapse
Unlock the bootloader at HTCDEV
then from fastboot USB
Flash recovery TWRP 2.6.3.3
http://techerrata.com/browse/twrp2/m7
fastboot flash recovery openrecovery-twrp-2.6.3.3-m7.img
fastboot erase cache
fastboot reboot-bootloader
then sideload this Rom to your phone
http://www.androidrevolution.org/downloader/download.php?file=Android_Revolution_HD-One_31.6.zip
TWRP / Advanced / ADB Sideload - swipe to sideload
From PC adb / fastboot folder
you use
adb sideload name-of-rom.zip
make sure the rom is in the same folder as adb / fastboot