Database Develop

[Q] how to check original network HTC one,need to download RUU to flash stock ROM?

I got two HTC phones i bought them online and I am not sure about the original network of these phones. I would like to bring it back to stock roms but i do not know which RUU i should download , How would i know which network phones are these. Both of them are stuck at first screen and i cannot check them SIM card.
Please help ?

Brownpanda said:
I got two HTC phones i bought them online and I am not sure about the original network of these phones. I would like to bring it back to stock roms but i do not know which RUU i should download , How would i know which network phones are these. Both of them are stuck at first screen and i cannot check them SIM card.
Please help ?
Click to expand...
Click to collapse
What do you mean they are both stuck at the first screen ?
the bootloader ?
whats it say on the bootloader / power + vol down

clsA said:
What do you mean they are both stuck at the first screen ?
the bootloader ?
whats it say on the bootloader / power + vol down
Click to expand...
Click to collapse
Thanks for your reply .. lets start one by one .. attached is the screenshot for first phone
On XDA i have found some of the CWM backup files for Rogers canada, Both of phones have CWM installed. Could you please let me know if i can use these files for backup
M7 CWM Nandroid Backup / CID ROGER001 / 1.29.631.17 (Rogers - Thanks to Whampahoofus)
I am trying to find on my end too , please let me know if u can find any link for canada HTC one RUU links ?

Brownpanda said:
Thanks for your reply .. lets start one by one .. attached is the screenshot for first phone
On XDA i have found some of the CWM backup files for Rogers canada, Both of phones have CWM installed. Could you please let me know if i can use these files for backup
M7 CWM Nandroid Backup / CID ROGER001 / 1.29.631.17 (Rogers - Thanks to Whampahoofus)
I am trying to find on my end too , please let me know if u can find any link for canada HTC one RUU links ?
Click to expand...
Click to collapse
You need @SaHiLzZ he's the Rogers guy
Sent from my HTC One using Tapatalk 4

Fastboot getvar all should give model id and main version. First stop would be to s-off.

I have CWRP installed in both of my devices, as i was researching on internet (mostly XDA) , i have found there is no RUU available for Canadian networks like bell , rogers. telus right now . i bought it in Canada so i assume they are on Canadian networks. Just want to know if i download CWM nandroid backup for different Canadian networks would it work ?
If yes, HTC one M7 does not come with any sd card slot and most of the procedure says CWM can restore files (cwm nandroid backups )from sd card. So how can i do it on HTC one M7 ?

Brownpanda said:
I have CWRP installed in both of my devices, as i was researching on internet (mostly XDA) , i have found there is no RUU available for Canadian networks like bell , rogers. telus right now . i bought it in Canada so i assume they are on Canadian networks. Just want to know if i download CWM nandroid backup for different Canadian networks would it work ?
If yes, HTC one M7 does not come with any sd card slot and most of the procedure says CWM can restore files (cwm nandroid backups )from sd card. So how can i do it on HTC one M7 ?
Click to expand...
Click to collapse
Have a look here
http://forum.xda-developers.com/showthread.php?t=2529225
if you still have questions I'm here

clsA said:
You need @SaHiLzZ he's the Rogers guy
Sent from my HTC One using Tapatalk 4
Click to expand...
Click to collapse
i went thru his threadt SaHiLzZ , got very good information from that guy, In his thread, he suggested i should S-off to do any further work even other member suggested me same thing . I have downloaded ramrunner software to do that. But it came back with error message my phone is not rooted right now. Could you please let me know how can i root this phone in CWM mode ?
Thanks clsA for this link, thats the same link i followed from sahilz thread, As per step 10 I am trying to s-off my phone with ramrunner but its not rooted

Brownpanda said:
i went thru his threadt SaHiLzZ , got very good information from that guy, In his thread, he suggested i should S-off to do any further work even other member suggested me same thing . I have downloaded ramrunner software to do that. But it came back with error message my phone is not rooted right now. Could you please let me know how can i root this phone in CWM mode ?
Thanks clsA for this link, thats the same link i followed from sahilz thread, As per step 10 I am trying to s-off my phone with ramrunner but its not rooted
Click to expand...
Click to collapse
flash this in recovery same as a rom
http://download.chainfire.eu/382/SuperSU/UPDATE-SuperSU-v1.93.zip

clsA said:
flash this in recovery same as a rom
http://download.chainfire.eu/382/SuperSU/UPDATE-SuperSU-v1.93.zip
Click to expand...
Click to collapse
Please consider me as novice in CWM recovery, I have tried all options but cannot find how can i transfer superuser files from my PC to my phone now, I cannot go beyond CWM recovery so my PC is not recognizing my phone right now.

Brownpanda said:
Please consider me as novice in CWM recovery, I have tried all options but cannot find how can i transfer superuser files from my PC to my phone now, I cannot go beyond CWM recovery so my PC is not recognizing my phone right now.
Click to expand...
Click to collapse
I don't use CWM ..so you need to find sideload usually under some advanced setting.
you start the sideload and then from your pc fastboot / adb folder
you adb sideload <Name of file>.zip
just be sure the files your trying to sideload are in the same folder as adb / fastboot. the alternative is to Push the files
the command is
adb push <name of file>.zip /sdcard/ <don't forget the space between .zip /sdcard/
This works for any file you want to copy to your phone

clsA said:
I don't use CWM ..so you need to find sideload usually under some advanced setting.
you start the sideload and then from your pc fastboot / adb folder
you adb sideload <Name of file>.zip
just be sure the files your trying to sideload are in the same folder as adb / fastboot. the alternative is to Push the files
the command is
adb push <name of file>.zip /sdcard/ <don't forget the space between .zip /sdcard/
This works for any file you want to copy to your phone
Click to expand...
Click to collapse
I don't know where i went wrong but now I am stuck at this point. Please check attachment
My device is no longer recognized by my computer or adb , just got stuck in there, last thing i tried on this phone was ramrunner when it came back with error message " My phone is not rooted"
Now i cannot enter in CWM recovery , it come back to same bootloader screen everytime i try to entered recovery
EDITED :
Latest updates on my phone is
Just changed the USB port on my pc and it finally recognized my phone. Now in fastboot devices command i can see my device listed, but on adb it does not show my device listed
researched a little bit more so i found lot of people used different version of CWM or TWRP to make it work so tried few but got these error messages when tried to flash recoveries
FAILED : remote signature verify fail
any ideas ?
bootloader is still at Tampered, re locked and security warning screen !!!!

Brownpanda said:
I don't know where i went wrong but now I am stuck at this point. Please check attachment
My device is no longer recognized by my computer or adb , just got stuck in there, last thing i tried on this phone was ramrunner when it came back with error message " My phone is not rooted"
Now i cannot enter in CWM recovery , it come back to same bootloader screen everytime i try to entered recovery
EDITED :
Latest updates on my phone is
Just changed the USB port on my pc and it finally recognized my phone. Now in fastboot devices command i can see my device listed, but on adb it does not show my device listed
researched a little bit more so i found lot of people used different version of CWM or TWRP to make it work so tried few but got these error messages when tried to flash recoveries
FAILED : remote signature verify fail
any ideas ?
bootloader is still at Tampered, re locked and security warning screen !!!!
Click to expand...
Click to collapse
Unlock the bootloader so you can update your recovery
Sent from my HTC One using Tapatalk 4

clsA said:
Unlock the bootloader so you can update your recovery
Sent from my HTC One using Tapatalk 4
Click to expand...
Click to collapse
I have tried to unlock it but its giving me some error messages, anyways now my bootloader is in relock position so i found this thread
http://forum.xda-developers.com/showthread.php?t=2251800
As suggested i downloaded Telus zip file and followed the procedure, it came back with error message.
signature failed ...............any ideas what does this error message means ??

clsA said:
Unlock the bootloader so you can update your recovery
Sent from my HTC One using Tapatalk 4
Click to expand...
Click to collapse
Brownpanda said:
I have tried to unlock it but its giving me some error messages, anyways now my bootloader is in relock position so i found this thread
http://forum.xda-developers.com/showthread.php?t=2251800
As suggested i downloaded Telus zip file and followed the procedure, it came back with error message.
signature failed ...............any ideas what does this error message means ??
Click to expand...
Click to collapse
This is going from good to bad to worse.
I recommend you relax a little, doing things in a hurry/rush/panic is not going to be good or get you anywhere !!
Now 1st go back to HTCdev, and unlock you bootloader using a new unlock token.... you shouldnt have locked in the first place, and reading guides dating back to April 2013 (ie pre S-Off days), is not going to help either.

nkk71 said:
This is going from good to bad to worse.
I recommend you relax a little, doing things in a hurry/rush/panic is not going to be good or get you anywhere !!
Now 1st go back to HTCdev, and unlock you bootloader using a new unlock token.... you shouldnt have locked in the first place, and reading guides dating back to April 2013 (ie pre S-Off days), is not going to help either.
Click to expand...
Click to collapse
Even i was thinking same thing , thanks for your help, I am not doing anything on this phone for next few hours now and will start from beginning ...please advice me how should i proceed ..

Brownpanda said:
Even i was thinking same thing , thanks for your help, I am not doing anything on this phone for next few hours now and will start from beginning ...please advice me how should i proceed ..
Click to expand...
Click to collapse
Do you have a functioning ROM?
If yes, then there could be multiple options, but the below will be the easiest:
If no, then you have to unlock using HTCdev: http://www.htcdev.com/bootloader/
you need to register an account with a real email (where you receive the unlock token)
in "Supported Devices" choose All other supported models, and follow the instructions.

Thanks , sorry I don't have functioning Rom , only had this RUU zip file from telus Canada , as I mentioned I did not know about original network of this phone , bought it from Canada so just assumed its on Canadian network , relock boot loader happened after I used ram runner software to s-off it , my phone was not rooted and it came with error message , so could not do s-off it , I am having nice break from this phone , as you suggested I will start from scratch tonight , will let u know guys , thanks for your help so far
Sent from my HTC One using Tapatalk

Short steps.
1. Unlock bootloader.
2. Place phone in fastboot mode and type fastboot getvar all, and copy paste the output here.
Wait for further instructions.
sent from my mobile device

SaHiLzZ said:
Short steps.
1. Unlock bootloader.
2. Place phone in fastboot mode and type fastboot getvar all, and copy paste the output here.
Wait for further instructions.
sent from my mobile device
Click to expand...
Click to collapse
Sorry I am trying to unlock my bootloader, After copying pasting my identifier token on HTC dev website it come back with this error message
We're sorry, but it appears your attempt to unlock the bootloader on this device has failed. This could be caused by several factors including simple errors in the entry of the unlock token, problems with your device, or a lack of manufacturer support for the unlocking process. Please see the specific error code listed below, and try again if necessary.
Error Code: 140.
Error Reason: Token Decryption Fail.
after command fastboot getvar all I am getting this info if that helps
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.44.0000
(bootloader) version-baseband: 4A.14.3250.13
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.29.666.17
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: HT34RW905405
(bootloader) imei: 354439053765923
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: BM___001
(bootloader) battery-status: good
(bootloader) battery-voltage: 3789mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
getvar:all FAILED (status read failed (Too many links))
finished. total time: 0.076s

Bricked Phone? PLEASE HELP!

My HTC One decided suddenly to not wake up this morning even though I had left it at 80 percent charge before I went to sleep. I put it to charge for 8 hours and when I came back, it still would not turn on. I can only get into the fastboot menu but my computer will not recognize my phone whatsoever- it says android 1.0 on my windows 7 computer. I know all of the correct drivers are installed because this is the same computer I used to root my phone. I am rooted with ARHD and TWRP. I have also tried holding the volume and power under a bright light and I can only get into the fastboot. Whenever I try to enter recovery, it gets stock on the "entering recovery" sign and when I try to boot the phone, it gets stuck on the splash screen.
I have not changed anything to my phone in the last month or so and this comes completely at random.
Any and all help will be greatly appreciated. Thanks!
EDIT: I can only get fastboot connectivity. Not ADB

xeron72548 said:
My HTC One decided suddenly to not wake up this morning even though I had left it at 80 percent charge before I went to sleep. I put it to charge for 8 hours and when I came back, it still would not turn on. I can only get into the fastboot menu but my computer will not recognize my phone whatsoever- it says android 1.0 on my windows 7 computer. I know all of the correct drivers are installed because this is the same computer I used to root my phone. I am rooted with ARHD and TWRP. I have also tried holding the volume and power under a bright light and I can only get into the fastboot. Whenever I try to enter recovery, it gets stock on the "entering recovery" sign and when I try to boot the phone, it gets stuck on the splash screen.
I have not changed anything to my phone in the last month or so and this comes completely at random.
Any and all help will be greatly appreciated. Thanks!
Click to expand...
Click to collapse
post your getvar all/bootloader information please

moha_moha20106 said:
post your getvar all/bootloader information please
Click to expand...
Click to collapse
Here it is:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.44.0000
(bootloader) version-baseband: 4A.14.3250.13
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.29.1540.17
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: FA34MW908198
(bootloader) imei: #################### (done intentionally)
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: BS_US001
(bootloader) battery-status: good
(bootloader) battery-voltage: 3716mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
getvar:all FAILED (status read failed (Too many links))
finished. total time: 0.062s
I can get fastboot connectivity but no ADB connectivity

xeron72548 said:
I can't get any of that because my phone isn't being picked up by my computer. I don't think it's a driver issue because this is the same computer i used to root the phone.
Click to expand...
Click to collapse
I've had the same problem
I could solve the problem by pushing the power button for few seconds until the buttom start blinking while I was trying to enter the recovery
probably this helps you

xeron72548 said:
I can't get any of that because my phone isn't being picked up by my computer. I don't think it's a driver issue because this is the same computer i used to root the phone.
Click to expand...
Click to collapse
can you check FAQ #2 in my guide if that's the problem.

try nkk71 method, it will resolve your problem
this is your correct RUU.exe

PS: @ OP, please edit and remove IMEI from your posts
---------- Post added at 02:17 AM ---------- Previous post was at 02:11 AM ----------
moha_moha20106 said:
this is your correct RUU.exe
Click to expand...
Click to collapse
I know you're eagerly trying to help, but you should take it easy a little more, before suggesting ruu's at every single point, and in every recent post.
going from 1.29.1540.17 to 4.19.1540.9, with S-On could really be a one way trip ... not necessarily a bad one, but just a one way trip.

moha_moha20106 said:
post your getvar all/bootloader information please
Click to expand...
Click to collapse
nkk71 said:
can you check FAQ #2 in my guide if that's the problem.
Click to expand...
Click to collapse
I can't do that because there is no driver not installed popup. When not in fastboot mode (just in the bootloader), the phone doesn't show up as anything in device manager

nkk71 said:
PS: @ OP, please edit and remove IMEI from your posts
---------- Post added at 02:17 AM ---------- Previous post was at 02:11 AM ----------
I know you're eagerly trying to help, but you should take it easy a little more, before suggesting ruu's at every single point, and in every recent post.
going from 1.29.1540.17 to 4.19.1540.9, with S-On could really be a one way trip ... not necessarily a bad one, but just a one way trip.
Click to expand...
Click to collapse
i know what you mean dear, but there's no RUU.exe between 1.29.1540.17 and 4.19.1540.9 i was found, so i suggest this one to back to stock after use your FAQ#2 method
with my respect, i learned more from you

xeron72548 said:
I can't do that because there is no driver not installed popup. When not in fastboot mode (just in the bootloader), the phone doesn't show up as anything in device manager
Click to expand...
Click to collapse
forget the pop-up!! check Windows Device Manager
your phone has 3 options:
1- bootloader (where you do fastboot commands)
2- custom recovery (TWRP or CWM), (where you can do adb commands)
3- booted ROM, if USB debugging is enabled you can use adb commands
in all three modes, the drivers "need to install", if they dont, you need to manually select them

nkk71 said:
forget the pop-up!! check Windows Device Manager
your phone has 3 options:
1- bootloader (where you do fastboot commands)
2- custom recovery (TWRP or CWM), (where you can do adb commands)
3- booted ROM, if USB debugging is enabled you can use adb commands
in all three modes, the drivers "need to install", if they dont, you need to manually select them
Click to expand...
Click to collapse
I can't get into my recovery. It freezes on the "entering recovery" screen every time. And for number 3, i can't even boot up my phone. I know this might be a bit unorthodox, but would you mind doing a teamviewer session with me?
Also, my phone DOES NOT show up in device manager unless it is in fastboot

xeron72548 said:
I can't get into my recovery. It freezes on the "entering recovery" screen every time. And for number 3, i can't even boot up my phone. I know this might be a bit unorthodox, but would you mind doing a teamviewer session with me?
Click to expand...
Click to collapse
Sorry, just turned off my pc and going to bed soon (it's almost 3am here, and I have to go to work in 4 hours)
Have you tried downloading the recovery again, make sure md5 is correct!! And don't forget to: fastboot erase cache
If that doesn't work, we can do teamviewer tomorrow.
Sorry, too late for me.
Sent from my HTC One using Tapatalk
---------- Post added at 02:49 AM ---------- Previous post was at 02:43 AM ----------
xeron72548 said:
I can't get into my recovery. It freezes on the "entering recovery" screen every time. And for number 3, i can't even boot up my phone. I know this might be a bit unorthodox, but would you mind doing a teamviewer session with me?
Also, my phone DOES NOT show up in device manager unless it is in fastboot
Click to expand...
Click to collapse
U know what, send me teamviewer Id and pass on PM... Booting up, but not more than 20 minutes, okay?
Sent from my HTC One using Tapatalk
---------- Post added at 02:58 AM ---------- Previous post was at 02:49 AM ----------
xeron72548 said:
I can't get into my recovery. It freezes on the "entering recovery" screen every time. And for number 3, i can't even boot up my phone. I know this might be a bit unorthodox, but would you mind doing a teamviewer session with me?
Also, my phone DOES NOT show up in device manager unless it is in fastboot
Click to expand...
Click to collapse
waiting...

moha_moha20106 said:
try nkk71 method, it will resolve your problem
this is your correct RUU.exe
Click to expand...
Click to collapse
Hey. I'm really thinking of using the RUU but the radio on the RUU you gave me doesn't match the one that is on my phone. Would this be a problem?

xeron72548 said:
Hey. I'm really thinking of using the RUU but the radio on the RUU you gave me doesn't match the one that is on my phone. Would this be a problem?
Click to expand...
Click to collapse
no problem for that

moha_moha20106 said:
no problem for that
Click to expand...
Click to collapse
For some reason the download speed is extremely slow. About 50kbs
Is this normal?

xeron72548 said:
For some reason the download speed is extremely slow. About 50kbs
Is this normal?
Click to expand...
Click to collapse
maybe you far from server , so the speed is slow
be patient

moha_moha20106 said:
maybe you far from server , so the speed is slow
be patient
Click to expand...
Click to collapse
I tried running the RUU and it said it was the wrong RUU. Is there another one that I should download?

xeron72548 said:
I tried running the RUU and it said it was the wrong RUU. Is there another one that I should download?
Click to expand...
Click to collapse
Also, my bootloader used to say this but now there is nothing after the version-main. It's blank
(bootloader) version-main: 1.29.1540.17

xeron72548 said:
Also, my bootloader used to say this but now there is nothing after the version-main. It's blank
(bootloader) version-main: 1.29.1540.17
Click to expand...
Click to collapse
does your phone S-off ?
what's your HBoot ver. ?

moha_moha20106 said:
does your phone S-off ?
what's your HBoot ver. ?
Click to expand...
Click to collapse
My phone is s-on and my bootloader version (version-main) is blank whenever I do getvar all

Htc One stuck on Logo, need 1.29.666.17 RUU to flash or another solution

EDIT: This is the Htc One (M7) btw. Guess it was obvious because of the version it came with out of the box, but just to clear any confusion.
EDIT 2: Meant to say my Device was S-On* NOT S-Off. Sorry.
So I'm completely new to Android, and yesterday was the day I got my first ever Android device.
It came with Sense 5 and android 4.1.2 out of the box.
After a while of playing around with my new phone I started checking for updates to get it to the latest version. When I first check it showed that a small update was available and I started downloading it. I noticed that when this update was installing it would first go into that screen where it shows that phone with a green arrow and a download bar, and then all of a sudden it would restart and go back to the Htc One Logo. It did this a few times before finally completing the upgrade.
I checked for updates again and this time it showed me Android 4.3 + Sense 5.5. I downloaded and started installing the upgrade. It did the same thing as last time but I decided I'd power off the device (Figured out later this was what caused this whole problem) and power it on again. After I did that it was stuck on the Htc Logo.
I went on the bootloader and tried factory resetting but it just brought me back to the Htc Logo again.
I found a few threads telling me to hook up my device to the computer, load up fastboot and use cmd to clear the cache and it should work. That failed too however.
After talking with a few of my friends who happen to be android experts, they told me that I because I had turned off the device in the middle of the update I had somehow corrupted some system partition thing and I'd need to flash the stock rom on once again.
After almost 24 hours of research, I've gotten to a point where I've almost figured it out but I hit a bump. My device is not rooted and is S-On (Bootloader used to be locked but in the process of fixing it).
According to my friends because my device is S-On I won't be able to flash Custom roms and need a RUU file that is specific to my carrier. I found out that I basically need the RUU file that has the same number as 1.29.666.17
This apparently is almost non-existent on the web. This is the bump I've hit and I have no idea what I can do now.
Any help would be appreciated.
Also note that I am incredibly new to android. Never rooted or anything in my life before. I've had quite the learning curve in the past day though.

Can you post a fastboot getvar all using command prompt and remove your imei and serial no please?
Sent from my HTC One using xda app-developers app

stovie_steve said:
Can you post a fastboot getvar all using command prompt and remove your imei and serial no please?
Sent from my HTC One using xda app-developers app
Click to expand...
Click to collapse
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.44.0000
(bootloader) version-baseband: 4A.14.3250.13
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.29.666.17
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: BM___001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4319mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
getvar:all FAILED (status read failed (Too many links))
finished. total time: 0.047s

Als26 said:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.44.0000
(bootloader) version-baseband: 4A.14.3250.13
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.29.666.17
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: BM___001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4319mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
getvar:all FAILED (status read failed (Too many links))
finished. total time: 0.047s
Click to expand...
Click to collapse
you phone is not s-off
your going to have to unlock the bootloader and flash custom recovery and a rom to attempt to get s-off so you can convert your phone to the international or developer version
instructions on how to convert here >> http://forum.xda-developers.com/showthread.php?t=2356401

clsA said:
you phone is not s-off
your going to have to unlock the bootloader and flash custom recovery and a rom to attempt to get s-off so you can convert your phone to the international or developer version
Click to expand...
Click to collapse
That was my mistake, I did mean to say S-On.
I did try to get the S-Off using an Htc One Toolkit (http://forum.xda-developers.com/showthread.php?t=2364445)
However right after Step 1a (downloading Firewater), I moved to step 1b (rebooting my device) it kept saying "adb reboot
error: device not found"
I googled this and it told I had to enable USB debugging, which I can only do through the settings of the phone apparently. And I can't access it so I'm not sure if I can still S-Off my device.

When you enable USB debugging does a pop up box come up on your phone when connecting to your computer to allow the computer to connect?
Sent from my HTC One using xda app-developers app

stovie_steve said:
When you enable USB debugging does a pop up box come up on your phone when connecting to your computer to allow the computer to connect?
Sent from my HTC One using xda app-developers app
Click to expand...
Click to collapse
See that's the thing, I can't enable USB Debugging because my phone is stuck on the bootlogo.
I don't think there's a way for me to enable USB debugging without having access to there phone, or is there?

Als26 said:
See that's the thing, I can't enable USB Debugging because my phone is stuck on the bootlogo.
I don't think there's a way for me to enable USB debugging without having access to there phone, or is there?
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/m7ul
fastboot flash recovery openrecovery-twrp-2.6.3.4-m7ul.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

clsA said:
Unlock the bootloader at HTCDEV
then from fastboot USB
Flash recovery TWRP 2.6.3.3
fastboot flash recovery openrecovery-twrp-2.6.3.4-m7ul.img
fastboot erase cache
fastboot reboot-bootloader
then sideload this Rom to your phone
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
Click to expand...
Click to collapse
Alright so did what you said, successfully flashed the new recovery.
Sideloading seems to be giving me some trouble though.
After I "swiped to sideload" I get this
Updating partition details...
E: Unable to mount '/cache'
Full SELinux support is present.
E: Unable to mount '/cache'
E: Unable to mount '/cache'
Starting ADB sideload feature...
Been stuck at that for about 15minutes now.
About 5 minutes in I thought I was maybe supposed to use my pc to sideload, but cmd said "error: device not found".
Thanks again for your help by the way.

Als26 said:
Alright so did what you said, successfully flashed the new recovery.
Sideloading seems to be giving me some trouble though.
After I "swiped to sideload" I get this
Updating partition details...
E: Unable to mount '/cache'
Full SELinux support is present.
E: Unable to mount '/cache'
E: Unable to mount '/cache'
Starting ADB sideload feature...
Been stuck at that for about 15minutes now.
About 5 minutes in I thought I was maybe supposed to use my pc to sideload, but cmd said "error: device not found".
Thanks again for your help by the way.
Click to expand...
Click to collapse
Your going to have to get your drivers fixed on the pc
Try and install these
http://www.mediafire.com/download/j55vk6qbbr6250c/HTCDriver_4.8.0.002.exe

clsA said:
Your going to have to get your drivers fixed on the pc
Try and install these
http://www.mediafire.com/download/j55vk6qbbr6250c/HTCDriver_4.8.0.002.exe
Click to expand...
Click to collapse
Didn't work. Ran the file, used device manager to manually locate the files in Program Files (x86) and double clicked "HTC". Just keeps saying it couldn't find the driver software for my device.
But if I understand correctly, all I have to do is find a way to update the drivers and I'll be able to sideload the Rom, and hopefully I'll have a working HTC One once again?

Als26 said:
Didn't work. Ran the file, used device manager to manually locate the files in Program Files (x86) and double clicked "HTC". Just keeps saying it couldn't find the driver software for my device.
But if I understand correctly, all I have to do is find a way to update the drivers and I'll be able to sideload the Rom, and hopefully I'll have a working HTC One once again?
Click to expand...
Click to collapse
yes or use a usb otg cable to load a rom to your phone from TWRP

clsA said:
yes or use a usb otg cable to load a rom to your phone from TWRP
Click to expand...
Click to collapse
Gave up trying to install new drivers and instead opted to pay a small fee to get it fixed.
Thanks again for the help, may have worked if I got those drivers installed.

Als26 said:
Gave up trying to install new drivers and instead opted to pay a small fee to get it fixed.
Thanks again for the help, may have worked if I got those drivers installed.
Click to expand...
Click to collapse
ok

clsA said:
ok
Click to expand...
Click to collapse
A few quick questions.
The rom will work even if I'm S-ON right?
Also if I do fix my phone using this method, is there a way for me to return it to the stock rom?

Als26 said:
A few quick questions.
The rom will work even if I'm S-ON right?
Also if I do fix my phone using this method, is there a way for me to return it to the stock rom?
Click to expand...
Click to collapse
Sounds like you haven't read anything about, rooting, S-Off, firmware,hboots,roms, etc..
Suffice to say most people on this forum have more trouble going back to full out of the box stock than anything else.. compared to that, unlocking bootloader, rooting and flashing roms is a doddle(very easy). Suggestion...Read first.
Sent from my HTC One using XDA Premium 4 mobile app

bored_stupid said:
Sounds like you haven't read anything about, rooting, S-Off, firmware,hboots,roms, etc..
Suffice to say most people on this forum have more trouble going back to full out of the box stock than anything else.. compared to that, unlocking bootloader, rooting and flashing roms is a doddle(very easy). Suggestion...Read first.
Sent from my HTC One using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I have not :/
I usually do my research before attempting to do anything to any of my devices, but since I had no intention of rooting/S-ff/Unlocking bootloaders I'm just incredibly clueless. Did some reasearch and it does look like sideloading Roms work on S-On devices. :good:
I have a question for you, or anyone else that knows, but the guy I sent my phone to repair told me the following:
Since I couldn't find the RUU specific to my device, I tried using a Nandroid backup that someone uploaded (This was for Bell Mobile). According to him, he says I must have tried flashing a corrupt rom or something so it's no longer an easy fix. He wants me to pay $130 so he can send it back to some factory to get it fixed. He's telling that this is no longer a soft-brick, but a hard-brick (note that the phone can still access the bootloader, recovery, etc).
I'm pretty sure this guys trying to milk me out of my money, so I told him I'd pick it up tomorrow and get back to him later.
I just want to make sure that what he's saying isn't true though, since I'm not exactly knowledgeable about this and I have a pretty good chance of being wrong.

Als26 said:
I have not :/
I usually do my research before attempting to do anything to any of my devices, but since I had no intention of rooting/S-ff/Unlocking bootloaders I'm just incredibly clueless. Did some reasearch and it does look like sideloading Roms work on S-On devices. :good:
I have a question for you, or anyone else that knows, but the guy I sent my phone to repair told me the following:
Since I couldn't find the RUU specific to my device, I tried using a Nandroid backup that someone uploaded (This was for Bell Mobile). According to him, he says I must have tried flashing a corrupt rom or something so it's no longer an easy fix. He wants me to pay $130 so he can send it back to some factory to get it fixed. He's telling that this is no longer a soft-brick, but a hard-brick (note that the phone can still access the bootloader, recovery, etc).
I'm pretty sure this guys trying to milk me out of my money, so I told him I'd pick it up tomorrow and get back to him later.
I just want to make sure that what he's saying isn't true though, since I'm not exactly knowledgeable about this and I have a pretty good chance of being wrong.
Click to expand...
Click to collapse
Sure sounds like a scam to me, I'm pretty sure we can get your phone working if your willing to read and learn

clsA said:
Sure sounds like a scam to me, I'm pretty sure we can get your phone working if your willing to read and learn
Click to expand...
Click to collapse
Definitely am. Going to pick up the phone tomorrow and try out sideloading through a USB Otg cable. I'll report back with the results. Really hoping this will work.

clsA said:
Sure sounds like a scam to me, I'm pretty sure we can get your phone working if your willing to read and learn
Click to expand...
Click to collapse
Fixed it!
I sideloaded the rom you linked me through a USB Otg Cable. Thanks a lot for your help!
Now I just want to get it back completley to stock.
If I backup my phone through this rom and then go back to stock, I'm assuming my backup file will restore all my contacts/settings/photos etc?

[SOLVED] Can't load RUU, no adb, fastboot remote not allowed

I'm truly stuck and could use your help guys. Here's the situation.
m7 Rogers canada edition.
No OS, no rom zips on the phone
Can't sideload because adb can't see the device
Fastboot often gives me an error when i try to flash an image
the phone boots into TWRP rather than attempting an OS
attempts at executing the RUU crashes the exe
I have NO idea how to get out of this.
My info
s-off
relocked
cid-roger001
I'm just trying to get back to stock at this point but nothing seems to work. Help me obi wan kinobi. you're my only hope.

With adb sideload, have a look in the device manager for 'one' and manually update the driver to the android device bridge driver.

craiglay said:
With adb sideload, have a look in the device manager for 'one' and manually update the driver to the android device bridge driver.
Click to expand...
Click to collapse
In device manager I only see My HTC under android devices, not ONE. ANd how do i update the drive to the adb driver? Where would i find that?
Thanks so much for getting back to me. Been on this for almost 24 hours and I have no idea how to fix this.

Thing is, the drivers were fine yesterday. So, somehow i don't think it's a driver thing. I think it's to do with somethign i messed up on the phone. I just reDLed the ADB + Fastboot + Drivers and I pointed the driver update to that folder (including subfolders) and windows says my drivers are up to date. Unless i should be selecting a specific file, i don't know if this solves my issue.

Nope, you were right. I now have adb access. So, what to do now? I'm afraid of trying to sideload cause that wasn't working before and I don't believe recovery is working. Somehow the phone think recovery is the OS. it boots into twrp but if i get into the bootloader and try to go into recovery, recovery won't load. So something's definitely wrong. Good thing is, i have adb now, so i'm sure i have more options, but if you could point me in the right direction, i'd really appreciate it.

Ugh. Actually, adb devices is still not listing my phone. WTF? I'm at a complete loss here.

adb/fastboot drivers from here
http://forum.xda-developers.com/showthread.php?t=2588979
and read here to get PC talking to phone
http://forum.xda-developers.com/showpost.php?p=52135024&postcount=2
Sent from my HTC One using XDA Premium 4 mobile app

thanks bored_stupid. I installed the ADB Installer v1.3 but still no go. List of devices remains blank when i run adb devices. the second link you posted, i don't really see anything that pertains to this issue. Am I missing something?

It's a FAQs. One will relate to your PC.
Sent from my HTC One using XDA Premium 4 mobile app

Ya, no, i know it's an FAQ, but it doesn't seem to cover the adb issue anywhere. At this point, i don't really care how i get back to stock whether via adb or fastboot or what, but as is, I have a completely bricked phone. I've done hours and hours of research, tried a whole slew of different things but nothing seems to work fastboot, adb and ruu.exe none of those options seem to be working. I have no external sd card that i could throw an img onto, so what options do i have here? Is there some other method you can think of that I could use to get the stock rom, hell or any rom onto this phone so i can at least have a proper recovery and OS installed? From there I'm sure i'll be able to get back to stock, but right now, as is, i am completely paralyzed. I appreciate your help man. THanks for taking the time.

vijn said:
Ya, no, i know it's an FAQ, but it doesn't seem to cover the adb issue anywhere. At this point, i don't really care how i get back to stock whether via adb or fastboot or what, but as is, I have a completely bricked phone. I've done hours and hours of research, tried a whole slew of different things but nothing seems to work fastboot, adb and ruu.exe none of those options seem to be working. I have no external sd card that i could throw an img onto, so what options do i have here? Is there some other method you can think of that I could use to get the stock rom, hell or any rom onto this phone so i can at least have a proper recovery and OS installed? From there I'm sure i'll be able to get back to stock, but right now, as is, i am completely paralyzed. I appreciate your help man. THanks for taking the time.
Click to expand...
Click to collapse
I think its more of a HTC one driver issue..
Download HTCSync. install then just delete HTCSync.. the drivers will remain..

I'm afraid if fastboot, adb or ruu's arent working, you have a driver issue or a completely bricked phone. Watch the device manager while you plug the phone into the computer. If you've enabled adb sideload in twrp, the device that appears needs to have the driver changed to android device bridge.

Installed Sync. Not sure how to delete it. You mean uninstall it? Either way, i closed htc sync, connected the phone. Ran adb devices and still list of devices attached is blank.
Is there no way you know of to completely wipe the phone, or use fastboot to install a rom or something. i can't even think clearly anymore. But i've been in worse situations with other phones, in terms of not even being able to turn the phone on, yet, I can't figure out what options i have left. Clearly, I'd love to get adb working, but i'm thinking maybe there's another way that I haven't considered. Though of course, as I mentioned, fastboot gives an error too most of the time. Thanks for following up.

craiglay said:
I'm afraid if fastboot, adb or ruu's arent working, you have a driver issue or a completely bricked phone. Watch the device manager while you plug the phone into the computer. If you've enabled adb sideload in twrp, the device that appears needs to have the driver changed to android device bridge.
Click to expand...
Click to collapse
Hey craig. When i connect the phone to the PC, My HTC (that's what it's called) shows up under Android USB Devices. I've tried updating the driver software. But I'm not sure how to change the driver to android device bridge. I assume you mean manually find a specific driver and install it, but what file am I looking for and where would i find it? I've installed a few driver packages and HTC sync. I can't imagine that i don't have the proper drivers installed, but I'm happy to try again if i know what i'm looking for.

Is 'my htc' happening in twrp? Ive seen it appear during boot before. To sideload, you need to boot into twrp, i think its in advanced then tap adb sideload.
Fastboot should be able to flash an ruu zip file from your desktop but i couldnt get it to work with 4.19.401.11. I got an error like 02 file too large..

vijn said:
Nope, you were right. I now have adb access. So, what to do now? I'm afraid of trying to sideload cause that wasn't working before and I don't believe recovery is working. Somehow the phone think recovery is the OS. it boots into twrp but if i get into the bootloader and try to go into recovery, recovery won't load. So something's definitely wrong. Good thing is, i have adb now, so i'm sure i have more options, but if you could point me in the right direction, i'd really appreciate it.
Click to expand...
Click to collapse
vijn said:
i can't even think clearly anymore.
Click to expand...
Click to collapse
Sorry, i know this is a pretty useless post, since I'm signing off, but:
1- post a "fastboot getvar all" (excluding IMEI and s/n)
2- a screenshot of your bootloader
3- How did you end up in this situation? did you "fastboot flash boot <name of recovery>.img"? what else did you flash?
and you sound kinda tired and fed up, may i recommend to take a break

Here's my getvar.
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.57.0000
(bootloader) version-baseband: 4T.27.3218.14
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 5.11.631.8
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: ROGER001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4324mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-e47fb74b
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.071s
No idea how to get a SS of my bootloader, but here's what's written:
M7_UL PVT SHIP S-OFF RH
CID-ROGER001
HBOOT-1.57.0000
Radio-4T.27.3218.14
OpenDSP-v32.120.274.0909
OS-5.11.631.8
eMMC-boot 2048MB
May 9 2014,00:36:41.0
How i got into this? Hehe. I was on stock rooted and unlocked. I installed the latest network provided OTA. Then, I tried to get root back. From that point on, i really can't remember what happened. I was having issues with root, which i needed to get my backup root working. I read some research saying the latest OTA caused rooting issues. I then decided, why not try the GPE edition. Well, must have missed a step or something because from that point on, it was all downhill. I am fed up, but I rather just get this done to be honest. But thanks nkk.
@craiglay - My HTC is what's showing up in my device manager on my PC. I know i need to boot into TWRP to sideload, but it just doesn't work. Remember, i can't get into recovery from the bootloader. The only way to get into recovery is if i reboot and don't get into the bootloader. TWRP will boot up automatically instead of the OS (which is non-existant). I'd love to try to flash a RUU but i can't find a .zip version for the m7. Any chance you know where I can find one? In addition, i usually get a error: closed error when trying to flash via fastboot

Sorry, its been a long day, comprehension is failing!!
Try here for ruu zip files and instructions

Thanks craig but i"ve been there many times. Unfortunately all the RUUs are actually exe files. And when I try running the exe file, it crashes every time. http://forum.xda-developers.com/showthread.php?t=2428276 has some zipped RUUs but i'm not sure which i can use. And in fact, that's where I got the original GPE version. Thing is, even when i try to flash those, via fastboot, i get an error. ex:
F:\Downloads\Android\The ONE\FINAL ROOT&RECOVERY METHOD\HTCOneRoot>fastboot flash zip RUU-Zip-M7_Google-Edition_4.4_3.58.1700.5.zip
sending 'zip' (506183 KB)...
OKAY [ 21.294s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) zip info parsing...
(bootloader) checking model ID...
(bootloader) checking custom ID...
FAILED (remote: 42 custom id check fail)
finished. total time: 21.800s
Or I'll get a remote: closed error.

I guess its because your CID is set to ROGER001 and not a Google Edition. I suggest running the ruu for your CID as it looks like you've tried to go to GE and missed a step. Edit: you've told me you have.. Its late..
There is a drop down box for zip files in downloads. I personally flashed a guru zip in twrp to return to stock.

Returning Phone Question

So, my HTC One got hit with the unresolvable "Can't charge unless turned off" bug and I'm going to be forced to return it if I can. My HTC One is unlocked, rooted and CM11 is installed. I also have SuperCID and S-Off. I also do not have warranty anymore because it's been 1 year since I got my phone, so I'm not sure how well it's going to go by returning this phone and hoping for a replacement.
Has anyone else had any experience with this? Do I just return it to stock as best as I can (All of the Google links to doing this are outdated with broken download links now, so if anyone could link me to a full guide to address all of my "customizations" to my phone to return to stock, it'd be highly appreciated) and go into the AT&T store hoping for a refurbished model replacement at least? Is there a phone manufacturer warranty of sorts? Will they check my phone to see the bootloader unlock counter or whatever? I heard they use a tool/program that checks to see how many times your bootloader has been unlocked or something.
I really need to get this phone fixed because it's having an awful lot of issues with it and I rely heavily on this phone for work. Not only that, but I had to pay retail for this phone when I got it back in June or so of 2013 so I'd like to fix these issues or get it replaced so I can re-sell it once my upgrade is available in a year.
If anyone could please help me, give me advice or point me in the direction of 'returning to stock' guides in all of the customization categories I listed, I'd be tremendously appreciative. I'm assuming the best way to do it is just walk into the AT&T store after returning to stock and act like a moron that barely knows how to turn the phone on and ask them if I can get a replacement under manufacturer warranty for these electronic bugged problems.
What do you all think?

Leather Sock said:
If anyone could please help me, give me advice or point me in the direction of 'returning to stock' guides in all of the customization categories I listed, I'd be tremendously appreciative. I'm assuming the best way to do it is just walk into the AT&T store after returning to stock and act like a moron that barely knows how to turn the phone on and ask them if I can get a replacement under manufacturer warranty for these electronic bugged problems.
Click to expand...
Click to collapse
Can you post the output of "fastboot getvar all" (excluding IMEI and s/n)

nkk71 said:
Can you post the output of "fastboot getvar all" (excluding IMEI and s/n)
Click to expand...
Click to collapse
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.44.0000
(bootloader) version-baseband: 4A.17.3250.20
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 4139mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
getvar:all FAILED (status read failed (Too many links))
finished. total time: 0.078s

Leather Sock said:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.44.0000
(bootloader) version-baseband: 4A.17.3250.20
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) product: m7_ul
(bootloader) modelid: PN0712000
(bootloader) cidnum: 11111111
finished. total time: 0.078s
Click to expand...
Click to collapse
You said you were originally on AT&T right? in which case CID should be CWS__001
so set it back:
fastboot oem writecid CWS__001 <- two underscores
fastboot oem reboot-bootloader
Then follow my guide: http://forum.xda-developers.com/showthread.php?t=2541082
using RUU.ZIP method (posts #1, #2, and #4), using this RUU Zip M7_UL_JB_50_Cingular - 1.26.502.15 - decrypted.zip
Note, if you already have a custom recovery installed, you don't need to change it to set your phone LOCKED and untampered
I prefer staying S-Off, but that's something only you can decide.

nkk71 said:
You said you were originally on AT&T right? in which case CID should be CWS__001
so set it back:
fastboot oem writecid CWS__001 <- two underscores
fastboot oem reboot-bootloader
Then follow my guide: http://forum.xda-developers.com/showthread.php?t=2541082
using RUU.ZIP method (posts #1, #2, and #4), using this RUU Zip M7_UL_JB_50_Cingular - 1.26.502.15 - decrypted.zip
Note, if you already have a custom recovery installed, you don't need to change it to set your phone LOCKED and untampered
I prefer staying S-Off, but that's something only you can decide.
Click to expand...
Click to collapse
Thank you so much for your help! I figured I had to go to S-On to return it fully to stock. I don't want there to be any issues when I go to return it since I've done the naughty stuff behind the scenes and I'm trying to get the best possible chance I can at getting a replacement. I've also never returned a phone or anything of the sort so I'm not sure what to expect or how much I'll have to talk them into the replacement. I do have a custom recovery being TWRP's latest version but I'm not necessarily sure what you mean. I imagine once I begin the process I'll understand!

Leather Sock said:
Thank you so much for your help! I figured I had to go to S-On to return it fully to stock. I don't want there to be any issues when I go to return it since I've done the naughty stuff behind the scenes and I'm trying to get the best possible chance I can at getting a replacement. I've also never returned a phone or anything of the sort so I'm not sure what to expect or how much I'll have to talk them into the replacement. I do have a custom recovery being TWRP's latest version but I'm not necessarily sure what you mean. I imagine once I begin the process I'll understand!
Click to expand...
Click to collapse
you need custom recovery to use adb command or use the Guru Bootloader Reset (which allows you to remove TAMPERED and set the phone to LOCKED not RELOCKED),
so it should be straightforward for you:
1) use Guru Bootloader Reset or adb commands to remove TAMPERED and set LOCKED
2) flash ruu.zip twice
---> first flash will give you "FAILED (remote: 90 hboot pre-update! please flush image again immediately)"
---> second flash should give you: "(bootloader) ...... Successful, OKAY [200.187s], finished. total time: 242.101s"
3) bootup phone just to make sure everything is OK, do not take OTA updates!! (at least yet)
4) set S-On
5) take OTAs if you want

nkk71 said:
you need custom recovery to use adb command or use the Guru Bootloader Reset (which allows you to remove TAMPERED and set the phone to LOCKED not RELOCKED),
so it should be straightforward for you:
1) use Guru Bootloader Reset or adb commands to remove TAMPERED and set LOCKED
2) flash ruu.zip twice
---> first flash will give you "FAILED (remote: 90 hboot pre-update! please flush image again immediately)"
---> second flash should give you: "(bootloader) ...... Successful, OKAY [200.187s], finished. total time: 242.101s"
3) bootup phone just to make sure everything is OK, do not take OTA updates!! (at least yet)
4) set S-On
5) take OTAs if you want
Click to expand...
Click to collapse
Thank you! Okay, from what I understand, I just need to do the following:
1. Put Guru Bootloader Reset + Ruu file you linked me to on my SD card like I would a custom ROM, ready to be unzipped.
2. Backup device stuff and reboot into TWRP
3. Install Zip for Guru Bootloader Reset and do the following in it's GUI to remove Tampered (I don't have it right now) and set my status to "Locked"
4. Reboot back into the recovery, not the ROM, and Install Zip "Ruu.zip" by flashing it. I'll get an error, and then I flash it one more time and I'm done and able to boot into stock Sense rom with OTA updates.
5. Remove S-On with that easy command via Fastboot. (However, didn't you say I needed a recovery to do this? Don't I do this while I still have TWRP or do I just keep TWRP on there? I don't see anywhere, where I'm removing TWRP)
Is that right? Am I missing any important details? Will this hide my past activities enough to get a replacement do you think?

Leather Sock said:
Thank you! Okay, from what I understand, I just need to do the following:
1. Put Guru Bootloader Reset + Ruu file you linked me to on my SD card like I would a custom ROM, ready to be unzipped.
2. Backup device stuff and reboot into TWRP
3. Install Zip for Guru Bootloader Reset and do the following in it's GUI to remove Tampered (I don't have it right now) and set my status to "Locked"
4. Reboot back into the recovery, not the ROM, and Install Zip "Ruu.zip" by flashing it. I'll get an error, and then I flash it one more time and I'm done and able to boot into stock Sense rom with OTA updates.
5. Remove S-On with that easy command via Fastboot. (However, didn't you say I needed a recovery to do this? Don't I do this while I still have TWRP or do I just keep TWRP on there? I don't see anywhere, where I'm removing TWRP)
Is that right? Am I missing any important details? Will this hide my past activities enough to get a replacement do you think?
Click to expand...
Click to collapse
Not really
First off, using ruu will completely wipe your phone!! everything including internal storage, so if there is anything on your phone you want to keep, you need to back that up to your PC.
Second, the fastboot commands are run on your PC, while the phone is connected and you are in bootloader showing FASTBOOT USB (just like you did to get the "fastboot getvar all"
So:
1- put Guru Bootloader Reset on your internal storage -> OK
2- use TWRP to "install" Guru Bootloader Reset -> OK, remove TAMPERED (even if it's not there), set LOCKED -> OK
go back to bootloader and confirm LOCKED
3- on your PC with phone connected in FASTBOOT USB:
fastboot oem rebootRUU
fastboot flash zip ruu.zip
fastboot flash zip ruu.zip <- yes TWICE, the first one will report “failed flush again”, the second one will succeed.
fastboot reboot-bootloader
4- reboot the phone (it will be wiped clean), just to make sure everything is OK, do not take OTA updates.
5- set S-On using
fastboot oem writesecureflag 3
done.

nkk71 said:
Not really
First off, using ruu will completely wipe your phone!! everything including internal storage, so if there is anything on your phone you want to keep, you need to back that up to your PC.
Second, the fastboot commands are run on your PC, while the phone is connected and you are in bootloader showing FASTBOOT USB (just like you did to get the "fastboot getvar all"
So:
1- put Guru Bootloader Reset on your internal storage -> OK
2- use TWRP to "install" Guru Bootloader Reset -> OK, remove TAMPERED (even if it's not there), set LOCKED -> OK
go back to bootloader and confirm LOCKED
3- on your PC with phone connected in FASTBOOT USB:
fastboot oem rebootRUU
fastboot flash zip ruu.zip
fastboot flash zip ruu.zip <- yes TWICE, the first one will report “failed flush again”, the second one will succeed.
fastboot reboot-bootloader
4- reboot the phone (it will be wiped clean), just to make sure everything is OK, do not take OTA updates.
5- set S-On using
fastboot oem writesecureflag 3
done.
Click to expand...
Click to collapse
Oh! Whew, glad I didn't do it yet then (still waiting for the RUU to download). Alright, apart from pictures/videos I don't think there's anything else on my Internal Storage that I care about unless there's other common stuff I'm forgetting. I also backed up my contacts and emailed them to me so I should be good there as well. Backed up my apps too.
One last final question and I promise I'll let you go! Will TWRP in this process, ever be removed or is it okay that it remains on there? When I flash the RUU, is that what removes it when it wipes the phone? If so, how will the fastboot work without TWRP if RUU removes it?
Oh, editing this in. When I go to install RUU, do I put the .zip file in my adb folder containing fastboot?

Leather Sock said:
Oh! Whew, glad I didn't do it yet then (still waiting for the RUU to download). Alright, apart from pictures/videos I don't think there's anything else on my Internal Storage that I care about unless there's other common stuff I'm forgetting. I also backed up my contacts and emailed them to me so I should be good there as well. Backed up my apps too.
One last final question and I promise I'll let you go! Will TWRP in this process, ever be removed or is it okay that it remains on there? When I flash the RUU, is that what removes it when it wipes the phone? If so, how will the fastboot work without TWRP if RUU removes it?
Click to expand...
Click to collapse
1- Everything (literally) will be removed / wiped / replaced after flashing a RUU... the phone will be just like "out of the box"
2- You only need TWRP to run the Guru Bootloader Reset, after that there's no more use for it, and you actually have to get rid of it for the phone to be 100% stock. (the ruu will replace twrp with the stock recovery)
3- fastboot commands are only run while the phone is in bootloader not recovery
fastboot.exe commands = bootloader/FASTBOOT USB
adb.exe commands = custom recovery or booted ROM with USB debugging enabled
EDIT: yes, rename the downloaded file to ruu.zip (for simplicity) and place it in your adb folder
make sure to check MD5 on the download
(and if you are using Windows Explorer to rename, be careful not to rename it to ruu.zip.zip)

nkk71 said:
1- Everything (literally) will be removed / wiped / replaced after flashing a RUU... the phone will be just like "out of the box"
2- You only need TWRP to run the Guru Bootloader Reset, after that there's no more use for it, and you actually have to get rid of it for the phone to be 100% stock. (the ruu will replace twrp with the stock recovery)
3- fastboot commands are only run while the phone is in bootloader not recovery
fastboot.exe commands = bootloader/FASTBOOT USB
adb.exe commands = custom recovery or booted ROM with USB debugging enabled
EDIT: yes, rename the downloaded file to ruu.zip and place it in your adb folder
Click to expand...
Click to collapse
Jeez, you're awesome. I really did not expect to get this much help, especially not this thorough and from the guy who wrote the guide himself! Thank you a ton, I extremely appreciate all of your help and I'll be returning this bad boy to stock in the coming hour or so. You took a lot of nerves off my mind and hopefully I'll be able to get this thing replaced!

Leather Sock said:
Jeez, you're awesome. I really did not expect to get this much help, especially not this thorough and from the guy who wrote the guide himself! Thank you a ton, I extremely appreciate all of your help and I'll be returning this bad boy to stock in the coming hour or so. You took a lot of nerves off my mind and hopefully I'll be able to get this thing replaced!
Click to expand...
Click to collapse
No problem, and Good Luck with replacement

nkk71 said:
No problem, and Good Luck with replacement
Click to expand...
Click to collapse
I'm having one problem. I don't know how to take off S-Off now that I've flashed the RUU. Everything is working perfectly and I don't have any OTA's done yet but I can't figure out how to get fastboot to work or whatever. It just says waiting for my device

Leather Sock said:
I'm having one problem. I don't know how to take off S-Off now that I've flashed the RUU. Everything is working perfectly and I don't have any OTA's done yet but I can't figure out how to get fastboot to work or whatever. It just says waiting for my device
Click to expand...
Click to collapse
Scratch that. Got it!