Database Develop

Is it possible to go back to Stock - Completely - To sell the phone?

I have a Mint Condition HTC One phone I am trying to sell - Mostly just because I also own a Nexus 4 and love it - and decided I'd rather keep it and use the money on the HTC One on something else.
I'm having a hard time selling it because the "everything is unlocked" is making people scared to buy it.
It's S-OFF, SuperCID, TWRP 2.6.0.1, Bootloader Unlocked, Running 2.24 Firmware and Android Revolution 12.1, Sim Unlocked too.
It's originally a Rogers Canada HTC One
Is there any way (or guide) to completely make it stock again to help sell it? Any help would be appreciated.

Yep, just flash the Rogers RUU (if available) and then you're good to go! If there isn't one then use one of the Nandroids provided and then get the stock recovery and relock the bootloader

don't forget to go back to S-ON after flashing the RUU

herwegan said:
don't forget to go back to S-ON after flashing the RUU
Click to expand...
Click to collapse
Hmm... never flashed a RUU before. Will need to do some reading.
Anyone know where to find a Rogers RUU?
I don't care if its Rogers specifically - it can be Telus or Bell too as long as it works.
I just want to go back to Stock so it's capable of updating OTA somehow if possible.

bigystyle84 said:
Hmm... never flashed a RUU before. Will need to do some reading.
Anyone know where to find a Rogers RUU?
I don't care if its Rogers specifically - it can be Telus or Bell too as long as it works.
I just want to go back to Stock so it's capable of updating OTA somehow if possible.
Click to expand...
Click to collapse
just download the RUU (sorry, don't know if there is one for your carrier), be sure to be s-off, and then run the RUU.exe or flash the RUU.zip.
the RUU will flash stock recovery, stock rom and i think it will even relock your bootloader. and then you'll be able to download OTA-updates again.
last step is to put it back to s-on and you should be done..

Ruu for bell. Rogers, telus is not available yet, your best bet is to flash the stock wwe Ruu. Remember to flash the stock hboot if you are using a modified hboot for the red lines or you would brick your device
Sent from my HTC One using XDA Premium HD app

EnIXmA said:
Ruu for bell. Rogers, telus is not available yet, your best bet is to flash the stock wwe Ruu. Remember to flash the stock hboot if you are using a modified hboot for the red lines or you would brick your device
Sent from my HTC One using XDA Premium HD app
Click to expand...
Click to collapse
Thanks
I'm S-OFF using the Revone Method
I'm on firmware 2.24 and HBoot 1.54 (Still S-Off though)
If anyone has time, can somebody give me a real quick overview on what I need to do? I'll buy ya a beer!
I'm not real familiar with HTC Devices - This was my first experience and to be honest, Right now I'm wishing I didn't do this if I knew before hand I was going to flip it so fast.

Ok no problem
First download the RUU from here: http://forum.xda-developers.com/showthread.php?p=39588860
and run the .exe.
then you'll have stock hboot and stock recovery + stock rom.
After this you can use hasoon2000's toolkit to get back to s-on: http://forum.xda-developers.com/showthread.php?t=2183942
Be sure you never installed a custom hboot before and you are using a official hboot. Better check twice if the red warning text is there before you go s-on
And that's it
No beer needed, "thanks-button" is enough
Cheers

herwegan said:
Ok no problem
First download the RUU from here: http://forum.xda-developers.com/showthread.php?p=39588860
and run the .exe.
then you'll have stock hboot and stock recovery + stock rom.
After this you can use hasoon2000's toolkit to get back to s-on: http://forum.xda-developers.com/showthread.php?t=2183942
Be sure you never installed a custom hboot before and you are using a official hboot. Better check twice if the red warning text is there before you go s-on
And that's it
No beer needed, "thanks-button" is enough
Cheers
Click to expand...
Click to collapse
You cant run the RUU with Super CID. You will have to change it to one that matches the RUU you choose before running it, but keep s-off. Then you should be able to use the tool as mentioned above or do all the things manually. You can use my guide if you like:
http://forum.xda-developers.com/showthread.php?p=43458497

Thanks for the help.
Which specific RUU should I flash? I don't see a Generic WWE One in that thread - just a couple of WWE ones for Developer Editions. Should I use an AT&T one? I can change the CID back to whatever is needed.
Am I able to do this somehow with the Nandroid backup for Rogers in that thread?
Also - What do you mean by "check for the red lines" exactly? I am on HBoot 1.54, Is there a easy way of going back to 1.44?
Sorry for all the questions - I'm kinda annoyed there isn't a Rogers RUU available. Last thing I need is a bricked phone - I'm only selling it as I honestly I shouldn't have bought it to begin with (Financially)

Where are you going to try and sell it? If to another user in Canada with one of those carriers, then they wouldn't to buy the unit with a AT&T image on it, I would think.
However running the ATT one would be a very easy way to reset everything including the hboot (no worry about red lines if run the RUU). Then you could sell to a US buyer who is going to use ATT (Tmobile also has a RUU). My guide for reseting to ATT:
http://forum.xda-developers.com/showthread.php?p=43458497
There are some threads around here where users are resetting Rodgers back to stock but it is much harder without a RUU and I am not sure of your comfort level.
To use one of the Rodgers Nandroids to do a complete reset to stock I would:
Change the CID to CWS__001 and run the ATT RUU to reset all your firmware, hboot etc, back to stock. You will still have unlocked bootloader and s-off, so you can then change back to your stock CID and then use the fastboot command to boot (but not install) a custom recovery in order to restore the Rodgers Nandroid and then just relock and s-on. Should be 100% Rodgers stock.
Code:
fastboot boot yourcustomrecovery.img
You can only use this method to boot a recovery without installing it, if on hboot 1.44, so that is why I recommend using the RUU to downgrade all that stuff for you.
Let me know if you need more help. I'd be happy to guide you.
Crush
PS - Love your Avatar. You should change your location to "Parts Unknown" to complete the joke. I may have to bust out a Conky avatar now!

bigystyle84 said:
Thanks for the help.
Which specific RUU should I flash? I don't see a Generic WWE One in that thread - just a couple of WWE ones for Developer Editions. Should I use an AT&T one? I can change the CID back to whatever is needed.
Click to expand...
Click to collapse
you could take the latest open europe RUU (RUU_M7_UL_JB_50_HTC_Europe_1.28.401.7), or take an AT&T one.. don't really know which one would be better for your situation you'll know it better
Am I able to do this somehow with the Nandroid backup for Rogers in that thread?
Click to expand...
Click to collapse
this is also an option. you can flash this nandroid backup through cwm recovery. but then you'd have to manually install stock recovery and lock the bootloader/go back to s-on. why not :good:
Also - What do you mean by "check for the red lines" exactly? I am on HBoot 1.54, Is there a easy way of going back to 1.44?
Click to expand...
Click to collapse
you can stay on 1.54 if everything works fine after flashing the older firmware. the "warning text" is related to this thread: http://forum.xda-developers.com/showthread.php?t=2316726
but if you've never installed a custom HBoot you don't have to worry about this when going back to s-on. just check once if the red warning text in the bootscreen is there.
Sorry for all the questions - I'm kinda annoyed there isn't a Rogers RUU available. Last thing I need is a bricked phone - I'm only selling it as I honestly I shouldn't have bought it to begin with (Financially)
Click to expand...
Click to collapse
hope it works :fingers-crossed:

crushalot said:
Where are you going to try and sell it? If to another user in Canada with one of those carriers, then they wouldn't to buy the unit with a AT&T image on it, I would think.
However running the ATT one would be a very easy way to reset everything including the hboot (no worry about red lines if run the RUU). Then you could sell to a US buyer who is going to use ATT (Tmobile also has a RUU). My guide for reseting to ATT:
http://forum.xda-developers.com/showthread.php?p=43458497
There are some threads around here where users are resetting Rodgers back to stock but it is much harder without a RUU and I am not sure of your comfort level.
To use one of the Rodgers Nandroids to do a complete reset to stock I would:
Change the CID to CWS__001 and run the ATT RUU to reset all your firmware, hboot etc, back to stock. You will still have unlocked bootloader and s-off, so you can then change back to your stock CID and then use the fastboot command to boot (but not install) a custom recovery in order to restore the Rodgers Nandroid and then just relock and s-on. Should be 100% Rodgers stock.
Code:
fastboot boot yourcustomrecovery.img
You can only use this method to boot a recovery without installing it, if on hboot 1.44, so that is why I recommend using the RUU to downgrade all that stuff for you.
Let me know if you need more help. I'd be happy to guide you.
Crush
PS - Love your Avatar. You should change your location to "Parts Unknown" to complete the joke. I may have to bust out a Conky avatar now!
Click to expand...
Click to collapse
Hey, I'm trying to do the same thing as OP, and this thread has been the closest thing to my issue. I'm trying to return everything on my phone to stock, however my Canadian carrier is Bell. Currently my HTC One has the bootloader unlocked, is rooted, TWRP recovery, and TrickDroid installed.
If I understand your instructions correctly, what I should do (given I want to restore using a nandroid backup) is:
1) S-Off my phone
2) Change the CID to CWS___001 and run the ATT RUU
3) Change the CID back to my original (BM_001 is what I think it is, do you know how I can make sure? What command to run for ADB?)
4) The Nandroid backup from http://forum.xda-developers.com/showthread.php?t=2207874&highlight=bell+update for my phone is for CWM (it's this one: M7 CWM Nandroid Backup / CID BM___001 / 1.29.666.5), does that mean I have to change my recovery from TWRP to CWM at this point?
5) Use fastboot to boot the recovery --> two questions regarding this, 1) why would I not install the .zip I downloaded from step 4? 2) where do I get the recovery.img? Just the one that is in the zip? In which case, shouldn't I also has to boot the boot.img or anything else?
6) I also want to upgrade the radio, should that be done last?
Thanks for all your help!
Lastly, I'm looking for a ROM to flash afterwards, I was wondering if you had any suggestions/know of a ROM that can allow me to use the swipe2sleep features, as well as hold the back touch button to force kill an app.

Just sell it on swappa. They love rooted unlocked modded phones.

Reverting Back from Google Edition !

So, first of all i want to say that i wouldn`t have written here if i hadn`t tried every possible way. I want to know where i did wrong, because this is the case and i wand to ask for your help.
The situation : I flashed the google edition to my htc one, it was fine, and i didn`t quite like it so i wanted to go back.
Now the show starts. I flashed Hboot 1.44, got the old bootloader back, and then when i tried to flash the old ruu zip it says : couldnt allocate 1034027008bytes. Also i have tried the exe file and it stops right at the start and says connection interrupted or some sort like this and it doesn`t continue.
I have S-off, unlocked bootloader. I had stock 4.2.2 with htc__001 cid, and twrp as recovery and of course it was rooted. I flashed the Google Edition after i put the stock recovery.
Thank you in advance for all your help.

details
Bloodrave said:
So, first of all i want to say that i wouldn`t have written here if i hadn`t tried every possible way. I want to know where i did wrong, because this is the case and i wand to ask for your help.
The situation : I flashed the google edition to my htc one, it was fine, and i didn`t quite like it so i wanted to go back.
Now the show starts. I flashed Hboot 1.44, got the old bootloader back, and then when i tried to flash the old ruu zip it says : couldnt allocate 1034027008bytes. Also i have tried the exe file and it stops right at the start and says connection interrupted or some sort like this and it doesn`t continue.
I have S-off, unlocked bootloader. I had stock 4.2.2 with htc__001 cid, and twrp as recovery and of course it was rooted. I flashed the Google Edition after i put the stock recovery.
Thank you in advance for all your help.
Click to expand...
Click to collapse
What phone is it? Developer Edition?
First thing is to change your CID to a Super CID 11111111
Then you need the proper RUU file for the phone. If its an ATT version
you can flash the 4.3 Developer Edition RUU on the HTC site.
CC

cc999 said:
What phone is it? Developer Edition?
First thing is to change your CID to a Super CID 11111111
Then you need the proper RUU file for the phone. If its an ATT version
you can flash the 4.3 Developer Edition RUU on the HTC site.
CC
Click to expand...
Click to collapse
@cc999: first of all thank you for your answer. I have the CID changed to supercid 11111111 and i want to flash the europe version. I have tried with both variants from the thread with the RUUs. The Zips and Exe`s dont work.

hboot
Bloodrave said:
@cc999: first of all thank you for your answer. I have the CID changed to supercid 11111111 and i want to flash the europe version. I have tried with both variants from the thread with the RUUs. The Zips and Exe`s dont work.
Click to expand...
Click to collapse
Then your Hboot 1.44 may not be the correct one. PM me with your email and I will give
you the correct one.
CC

I have tried once again with the 1.44 Hboot and the zip from htc official website , the developer edition one.
Still no luck.

With the help of cc999 i managed to revert back to 4.3 Developer Edition.
Apparently there was a mess in my adb and usb drivers.
So i managed to install the 4.3 Developer Edition on another laptop and it worked just fine.
Thank you again cc999 for the support.

You should use the stock recovery to flash the ruu.exe. Makes life so much easier!
Sent from my HTC One using Tapatalk 4

[Q] t-mobile fully converted to 4.3 gpe with 1.54 hboot and trying to RUU

i tried searching and could not find a similar scenario:
originally my htc one was on t-mobile with its proper cid. i am no s-offed, google cid and running the gpe 4.3 ruu with the 1.54 hboot. since i am s-off, can't i run any ruu withouth having to revert to 1.44 hboot? t-mobile came out with their 4.3 OTA and wanted to try that or the developer's edition 4.3 ruu,
i was planning to reboot into bootloader put it in fastboot mode, plug it the computer till it reads fastboot usb then run the RUU.exe, am i missing anything?

Think ill subscribe here. Im in the same boat but on mine im using the SuperCID 11111111.
I too have a TMO unit that i converted to GPE and love it. Now that 4.3 is official on TMO id like to go back to it and see how well it performs..
I kinda forgot half the steps i took to get to GPE so i feel like im starting over again. LOL

I had to flash a previous firmware via fastboot first in order for the T-Mobile 1.27.531.11 RUU to flash my One. I used a firmware zip for 1.27.531.11 since I had that on hand already.

[Q] How do I convert a GPE to latest Developer Edition or Sense 6 rom

Thanks in advance for any help... I've searched and come up empty in terms of up-to-date stuff. I'm super-cid, unlocked bootloader, s-off (phone came that way off a private sale) with a RUU conversion to GPE. I want to take advantage of the sense 6 update especially the new battery saving mode. Really wondering weather:
1- downgrading firmware is still a thing coming from GPE and going to the latest Sense 6 roms
2- Weather I should use an RUU or try flashing a custom recovery and a wrong
3- Weather there's any other watch-outs I should know

Change your CID/MID accordingly for Dev edition and run the http://www.androidruu.com/getdownlo...3_SENSE50_MR_BrightstarUS_WWE_3.22.1540.1.exe
This will get you going all the way to Sense 6 with a few updates. Do not LOCK boot loader or turn S-ON

Thanks! I tried this and got an ruu fail. My phone was left in a weird version of the recovery/fastboot screen that said ruu but I rebooted and it was fine. Just not sure if I should try again.

komienski said:
Thanks! I tried this and got an ruu fail. My phone was left in a weird version of the recovery/fastboot screen that said ruu but I rebooted and it was fine. Just not sure if I should try again.
Click to expand...
Click to collapse
Without further details can't help

komienski said:
Thanks! I tried this and got an ruu fail. My phone was left in a weird version of the recovery/fastboot screen that said ruu but I rebooted and it was fine. Just not sure if I should try again.
Click to expand...
Click to collapse
Based on the google searches I've done, this is normal. The HTC RUU installation never actually finishes. You just need to wait until the progress bar stops moving, make a coffee, then reboot and hope you haven't just bricked the phone.
SaHiLzZ said:
Without further details can't help
Click to expand...
Click to collapse
See above--what happened to him is normal.

Just to clarify it rebooted back into the previous (gpe) system. Flashing the ruu failed with a message about getting the correct one for my phone, which is odd because I am supercid and s-off.

komienski said:
Just to clarify it rebooted back into the previous (gpe) system. Flashing the ruu failed with a message about getting the correct one for my phone, which is odd because I am supercid and s-off.
Click to expand...
Click to collapse
Change cid to BS_US001 and make sure mid is PN0712000
Sent from my HTC One using XDA Free mobile app

[Q] Lost in an attempted update, AT&T M7 Sense 5.0 to 6.0

Good afternoon everyone,
So what my current situation is:
HTC ONE M7 -AT&T(Best Buy Blue Edition) activated on Criket
Android 4.3
Sense 5.0
Tampered
RElocked
S-off
HBOOT-1.55
TWRP-2.8.7.0
I'm attempting to update using the RUU from HTC's website for my phone. Everytime I run it, as soon as it starts to send the first package the installer has an error and is forced to close. I have the PC and my phone talking in FASTBOOT USB with the above current situation. I was getting the 155 error, but with the help of this forum I have gotten past that.
All I want to do is update my phone so I can get the better battery life and get Facebook working in my blinkfeed again.
Where do I go from here?
I am very computer literate, I just don't have a whole lot of experience with bootloading android. Flashing wasn't so hard though, and I'm comfortable in ADB/Fastboot. I have been going through all the guides on here I could find. It is how I got this far, but now I just don't know what to do. I still keep getting the same error.
P.S. Thanks for all the resources guys, it has already been such a big help!

Update: I was able to successfully run to completion the RUU for Cingular Sense 5.0 version 3.17 the same one as my phone, so now in the interest of sounding stupid I'm going to download and try Sense 5.5 and then step up to Sense 6.0 staying on the Cingular RUU path.
TLDR: old Update:
While I wait I decided to tinker. So for ****s and giggles I tried installing the RUU from "Android RUU" UL-3.17 the same version I already have. No real reason, just to see what would happen. It is progressing now, but has already made it much further than any attempt at installing the RUU from HTC which is also an UL Cingular version, but for version 7.23.
Just in case this information helps in my diagnosis.

Alright, So update to Sense 5.5 fails everytime at 5% again. Now it is saying it is an Error 171 USB Connection error.
I tried it on both USB 3.0 and USB 2.0.

Refuge88 said:
Update: I was able to successfully run to completion the RUU for Cingular Sense 5.0 version 3.17 the same one as my phone, so now in the interest of sounding stupid I'm going to download and try Sense 5.5 and then step up to Sense 6.0 staying on the Cingular RUU path.
TLDR: old Update:
While I wait I decided to tinker. So for ****s and giggles I tried installing the RUU from "Android RUU" UL-3.17 the same version I already have. No real reason, just to see what would happen. It is progressing now, but has already made it much further than any attempt at installing the RUU from HTC which is also an UL Cingular version, but for version 7.23.
Just in case this information helps in my diagnosis.
Click to expand...
Click to collapse
you can't flash a 7.xx.xxx.x RUU if your phone isn't already running at least a 6.xx.xxx.x firmware. May I ask why you want to stay on cingular version (at&t) ? If you are not using an at&t sim card you won't receive ota updates and since you are not on at&t you don't need all the at&t bloatware on your phone... You already have s-off you could simply change your cid to the developer edition or supercid and use the developer edition ruu...

alray said:
you can't flash a 7.xx.xxx.x RUU if your phone isn't already running at least a 6.xx.xxx.x firmware. May I ask why you want to stay on cingular version (at&t) ? If you are not using an at&t sim card you won't receive ota updates and since you are not on at&t you don't need all the at&t bloatware on your phone... You already have s-off you could simply change your cid to the developer edition or supercid and use the developer edition ruu...
Click to expand...
Click to collapse
I'm not opposed to that, the only reason I was trying to stick with it was just to leave as few variables as possible since this is foreign territory to me.
As long as I still get Sense 6.0 I'll run any RUU.
Which one would you recommend if so?

Refuge88 said:
I'm not opposed to that, the only reason I was trying to stick with it was just to leave as few variables as possible since this is foreign territory to me.
As long as I still get Sense 6.0 I'll run any RUU.
Which one would you recommend if so?
Click to expand...
Click to collapse
I would simply flash the developer edition 6.07.1540.2 firmware first so your phone will accept the 7.17.1540.7 ruu.
you'll then receive an ota update to 7.17.1540.21 which is the final version with android 5.0.2 htc sense 6.0
If you want to go that way, you'll need to:
change your cid to supercid or dev edition cid:
Code:
fastboot oem writecid BS_US001
fastboot reboot-bootloader
or
Code:
fastboot oem writecid 11111111
fastboot reboot-bootloader
flash the 6.07.1540.2 stock firmware:
Code:
fastboot oem rebootRUU
fastboot flash zip Firmware_6.07.1540.2.zip
fastboot flash zip Firmware_6.07.1540.2.zip
fastboot reboot-bootloader
and flash (run) the 7.07.1540.7 ruu.exe.

So after I flash 6xxx, I simply run the Brightstar RUU you linked? Or do I try and do it through the cmd again?

Refuge88 said:
So after I flash 6xxx, I simply run the Brightstar RUU you linked?
Click to expand...
Click to collapse
Yes after updating the firmware to 6.07.1540.2 your phone will accept the 7.17.1540.7 ruu, just run the ruu.exe with the phone still in bootloader mode.

alray said:
Yes after updating the firmware to 6.07.1540.2 your phone will accept the 7.17.1540.7 ruu, just run the ruu.exe with the phone still in bootloader mode.
Click to expand...
Click to collapse
Wooohooo!!! I'm in and updated! Now I just need to check for a software update to get the OTA one correct?

Refuge88 said:
Wooohooo!!! I'm in and updated! Now I just need to check for a software update to get the OTA one correct?
Click to expand...
Click to collapse
yes, there will be only one update, from 7.17.1540.7 to 7.17.1540.21, if you don't receive any notification for it, let me know I'll link the ota update zip file and explain you how to flash it manually.

alray said:
yes, there will be only one update, from 7.17.1540.7 to 7.17.1540.21, if you don't receive any notification for it, let me know I'll link the ota update zip file and explain you how to flash it manually.
Click to expand...
Click to collapse
Thank you for all of your help good sir. I've been fighting with this since 8 o clock last night...
Update: all taken care of, now it is just a matter of installing my apps and setting things back up again.
Thank you again sir, you were very helpful and straight to the point! Exactly what I needed.

Ok, one thing I've run into, while installing my apps and updated and such.
Facebook won't install. It gives me "Unknown error code -504"
I tried clearing cache's and no go, I googled it but I can't find a 504 code.

Refuge88 said:
Ok, one thing I've run into, while installing my apps and updated and such.
Facebook won't install. It gives me "Unknown error code -504"
I tried clearing cache's and no go, I googled it but I can't find a 504 code.
Click to expand...
Click to collapse
Clear google play cache, find the facebook installation folder (com.facebook.katana), deleted everything, reboot the phone and try to install again.