Database Develop

[Q] how to downgrade firmware

I updated firmware to 2.24.401(s-off),but now I have a camera issue,I want to go back to 1.29.708.16(I can't find this firmware) then turn to s-on for warranty,there isn't update to 4.2 in HK(where I bought the phone),so how can I downgrade firmware to 1.29,and can I change the firmware number by change "mainver" in android-info.txt ?

dingnangen said:
I updated firmware to 2.24.401(s-off),but now I have a camera issue,I want to go back to 1.29.708.16(I can't find this firmware) then turn to s-on for warranty,there isn't update to 4.2 in HK(where I bought the phone),so how can I downgrade firmware to 1.29,and can I change the firmware number by change "mainver" in android-info.txt ?
Click to expand...
Click to collapse
If you are returning your phone for service then you can run an RUU if your phone has one.
It will reset everything back to stock, even the firmware. Check here:
http://forum.xda-developers.com/showthread.php?p=39588860

crushalot said:
If you are returning your phone for service then you can run an RUU if your phone has one.
It will reset everything back to stock, even the firmware. Check here:
http://forum.xda-developers.com/showthread.php?p=39588860
Click to expand...
Click to collapse
can 2.24 firmware use 1.29 ruu?how to do it ?

dingnangen said:
can 2.24 firmware use 1.29 ruu?how to do it ?
Click to expand...
Click to collapse
If your s-off then a RUU can downgrade your firmware. (I did this on a phone I returned for service without issues) If you are still s-on I don't think it will.
You just download the RUU.exe and run it on your PC and it guides you through resetting everything on the phone.

crushalot said:
If your s-off then a RUU can downgrade your firmware. (I did this on a phone I returned for service without issues) If you are still s-on I don't think it will.
You just download the RUU.exe and run it on your PC and it guides you through resetting everything on the phone.
Click to expand...
Click to collapse
thank you very much,i'll try it.if there aren't my ruus of region,I use other region ruu,can I get warranty?

That depends on the carrier/vendor. If you don't have a RUU you could also run an RUU for another area (Since your S-off) to downgrade the firmware and then root it and use one of the posted stock nandroids to restore to your proper areas stock config. Then do the stuff to re-lock your bootloader. http://forum.xda-developers.com/showthread.php?p=43458497

crushalot said:
That depends on the carrier/vendor. If you don't have a RUU you could also run an RUU for another area (Since your S-off) to downgrade the firmware and then root it and use one of the posted stock nandroids to restore to your proper areas stock config. Then do the stuff to re-lock your bootloader. http://forum.xda-developers.com/showthread.php?p=43458497
Click to expand...
Click to collapse
I can back to stock rom,but firmware version can't change,because there aren't ruu of HongKong,any ideas to change firmware version?

Since your S-off you can change your CID to use another RUU like this one:
http://bugsylawson.com/files/file/1...14325013-1033115001-release-311678-signedexe/
The RUU will set the device firmware back to stock. Then restore your stock ROM and you should be ok.
Also if you have it stock rom and setup now, you may just want to put S-on so that it says Locked and S-on on bootloader and your vendor will probably not care about the firmware version.

crushalot said:
Since your S-off you can change your CID to use another RUU like this one:
http://bugsylawson.com/files/file/1...14325013-1033115001-release-311678-signedexe/
The RUU will set the device firmware back to stock. Then restore your stock ROM and you should be ok.
Also if you have it stock rom and setup now, you may just want to put S-on so that it says Locked and S-on on bootloader and your vendor will probably not care about the firmware version.
Click to expand...
Click to collapse
thank you ,downing ruu now . is there Hboots red warning by using ruu back to stock?

dingnangen said:
thank you ,downing ruu now . is there Hboots red warning by using ruu back to stock?
Click to expand...
Click to collapse
The red warning in hboot is from being unlocked. Once you have back to stock (especially recovery) then the red warning will be gone. For sure after re-locking.

crushalot said:
Since your S-off you can change your CID to use another RUU like this one:
http://bugsylawson.com/files/file/1...14325013-1033115001-release-311678-signedexe/
The RUU will set the device firmware back to stock. Then restore your stock ROM and you should be ok.
Also if you have it stock rom and setup now, you may just want to put S-on so that it says Locked and S-on on bootloader and your vendor will probably not care about the firmware version.
Click to expand...
Click to collapse
how to backup my stock recovery,because I must flash custom recovery to restore my rom,then back to the stock recovery.

dingnangen said:
how to backup my stock recovery,because I must flash custom recovery to restore my rom,then back to the stock recovery.
Click to expand...
Click to collapse
Sorry, I'm not sure I understand what you are asking here.

crushalot said:
Sorry, I'm not sure I understand what you are asking here.
Click to expand...
Click to collapse
how can I backup stock recovery?
because there are not ruu of HK,so I should use TWRP to restore nandroid backup from HK htc one. then back to stock recovery .

Yes you would TWRP to restore and then flash the stock recovery and relock.
Here is a post where I helped another and it has the stock recovery and instructions for flashing if needed.
http://forum.xda-developers.com/showpost.php?p=43625746&postcount=17
Just an FYI that this method will not downgrade the firmware, but just get you back to locked and a stock look, but with the newer firmware.
Let me know if you need something else.

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.

[Q] Want to restore TELUS unit to as stock as possible

Hi Guys,
I want to restore a TELUS Canada HTC One back to as stock as possible for warranty exchange purposes.
There is no RUU available for TELUS, but I do have a TWRP Nandroid backup. The device's HBOOT has been updated to 1.54, and the device is currently S-OFF / SuperCID via Revone and obviously unlocked bootloader with TWRP recovery. As well, the device is running the ARHD ROM.
What order / process do I need to follow to get this back to as stock-like as possible?

WorldIRC said:
Hi Guys,
I want to restore a TELUS Canada HTC One back to as stock as possible for warranty exchange purposes.
There is no RUU available for TELUS, but I do have a TWRP Nandroid backup. The device's HBOOT has been updated to 1.54, and the device is currently S-OFF / SuperCID via Revone and obviously unlocked bootloader with TWRP recovery. As well, the device is running the ARHD ROM.
What order / process do I need to follow to get this back to as stock-like as possible?
Click to expand...
Click to collapse
-Manually flash back the stock 1.44 hboot (and any custom splash you may have flashed)
-Nandroid restore (make sure it includes recovery, if not manually flash the stock one)
- Set CID back to stock
- S-on with revone
- Relock bootloader
Let me know if you need help with any of the steps.

crushalot said:
-Manually flash back the stock 1.44 hboot (and any custom splash you may have flashed)
-Nandroid restore (make sure it includes recovery, if not manually flash the stock one)
- Set CID back to stock
- S-on with revone
- Relock bootloader
Let me know if you need help with any of the steps.
Click to expand...
Click to collapse
Where would I get the stock 1.44 HBOOT and stock Recovery? I'm using the TELUS TWRP Recovery from here: http://forum.xda-developers.com/showthread.php?t=2207874

WorldIRC said:
Where would I get the stock 1.44 HBOOT and stock Recovery? I'm using the TELUS TWRP Recovery from here: http://forum.xda-developers.com/showthread.php?t=2207874
Click to expand...
Click to collapse
The Nandroid should include the stock recovery.
The stock hboot can be downloaded here: http://d-h.st/qfc
It is from post 2 of sneakyghost's guide which has the instructions as well:
http://forum.xda-developers.com/showthread.php?t=2316726
Let me know if you need anything else.

crushalot said:
The Nandroid should include the stock recovery.
The stock hboot can be downloaded here: http://d-h.st/qfc
It is from post 2 of sneakyghost's guide which has the instructions as well:
http://forum.xda-developers.com/showthread.php?t=2316726
Let me know if you need anything else.
Click to expand...
Click to collapse
Curious -- since making a Nandroid requires a custom recovery, how would that Nandroid contain the stock recovery?

WorldIRC said:
Curious -- since making a Nandroid requires a custom recovery, how would that Nandroid contain the stock recovery?
Click to expand...
Click to collapse
A few different ways. First, once you have a custom recovery installed, the 2 main recovery's used (TWRP & CWM) have an option to backup the recovery.
Second, when a new user unlocks their bootloader, they can then use fastboot commands to boot the custom recovery but keep the stock recovery installed and then it can take a backup of it. Example would be:
fastboot boot customrecovery.img
Also possible via a few different other more complicated methods.
If the nandroid you download doesn't have the stock recovery (the few that I downloaded for parts all had the recoveries, so I assumed it was a requirement before they would post a backup) then just give a shout around here and I can find a link for you.

crushalot said:
A few different ways. First, once you have a custom recovery installed, the 2 main recovery's used (TWRP & CWM) have an option to backup the recovery.
Second, when a new user unlocks their bootloader, they can then use fastboot commands to boot the custom recovery but keep the stock recovery installed and then it can take a backup of it. Example would be:
fastboot boot customrecovery.img
Also possible via a few different other more complicated methods.
If the nandroid you download doesn't have the stock recovery (the few that I downloaded for parts all had the recoveries, so I assumed it was a requirement before they would post a backup) then just give a shout around here and I can find a link for you.
Click to expand...
Click to collapse
Awesome -- I'll be trying this once my replacement unit has arrived. I'll let you know how everything works out.

crushalot said:
A few different ways. First, once you have a custom recovery installed, the 2 main recovery's used (TWRP & CWM) have an option to backup the recovery.
Second, when a new user unlocks their bootloader, they can then use fastboot commands to boot the custom recovery but keep the stock recovery installed and then it can take a backup of it. Example would be:
fastboot boot customrecovery.img
Also possible via a few different other more complicated methods.
If the nandroid you download doesn't have the stock recovery (the few that I downloaded for parts all had the recoveries, so I assumed it was a requirement before they would post a backup) then just give a shout around here and I can find a link for you.
Click to expand...
Click to collapse
Not sure why I'm having so much difficulty with this.
I've restored the 1.44 HBOOT referenced above.
I've restored the stock TELUS ROM via TWRP referenced above.
I can boot into the phone, but I have no touch-screen response now. Also, that TWRP backup did not include the stock recovery and I'm not sure which one I should push.
Tried flashing: http://forum.xda-developers.com/showpost.php?p=41953560&postcount=32 and now I have a red triangle recovery.....

OK, everything is normal. The red triangle means it is the stock recovery.
The touchscreen doesn't work because you must have updated your firmware. If you still have s-off then you can downgrade that back to stock before s-on and re-lock. Go to this thread:
http://forum.xda-developers.com/showthread.php?t=2316726
Download and install the package he has for " Base 1.29 Firmware, original unmodified"
After that you should be stock and just need to s-on and re-lock the bootloader.

crushalot said:
OK, everything is normal. The red triangle means it is the stock recovery.
The touchscreen doesn't work because you must have updated your firmware. If you still have s-off then you can downgrade that back to stock before s-on and re-lock. Go to this thread:
http://forum.xda-developers.com/showthread.php?t=2316726
Download and install the package he has for " Base 1.29 Firmware, original unmodified"
After that you should be stock and just need to s-on and re-lock the bootloader.
Click to expand...
Click to collapse
That site needs a "decryption key"?

WorldIRC said:
That site needs a "decryption key"?
Click to expand...
Click to collapse
Not sure what thats about. I will look into it and try to host those files on my site. However for now, you only need the touchpad driver part of the firmware which can be downloaded from his thread without a key here:
https://mega.co.nz/#!7YB1GCAJ!LaWJ8x5Vsjrw9YrLTIe262ZslZBNwRgp6i0qx2M_lIw

crushalot said:
Not sure what thats about. I will look into it and try to host those files on my site. However for now, you only need the touchpad driver part of the firmware which can be downloaded from his thread without a key here:
https://mega.co.nz/#!7YB1GCAJ!LaWJ8x5Vsjrw9YrLTIe262ZslZBNwRgp6i0qx2M_lIw
Click to expand...
Click to collapse
How am I flashing this?

WorldIRC said:
How am I flashing this?
Click to expand...
Click to collapse
Same way as the firmware zip's. You use the same guide from post 1.

crushalot said:
Same way as the firmware zip's. You use the same guide from post 1.
Click to expand...
Click to collapse
Thought so, wasn't 100% sure
Anyways - that worked. I have control of my Touch Screen. I'll await your response on the rest of the firmware, at which point I'll finish everything up and send you some beer for your time

WorldIRC said:
Thought so, wasn't 100% sure
Anyways - that worked. I have control of my Touch Screen. I'll await your response on the rest of the firmware, at which point I'll finish everything up and send you some beer for your time
Click to expand...
Click to collapse
Here you go bud. This is the stock firmware from 1.29.401.12. It has the stock radio and recovery(just in case).
https://dl.dropboxusercontent.com/u/36946918/1.29.401.12.zip
If you flash that, it should put everything back to complete stock in regards to the firmware.
Should be able to s-on and relock afterwards and should be no signs of mods.
Let me know if you need help finishing up.

crushalot said:
Here you go bud. This is the stock firmware from 1.29.401.12. It has the stock radio and recovery(just in case).
https://dl.dropboxusercontent.com/u/36946918/1.29.401.12.zip
If you flash that, it should put everything back to complete stock in regards to the firmware.
Should be able to s-on and relock afterwards and should be no signs of mods.
Let me know if you need help finishing up.
Click to expand...
Click to collapse
Will give it a shot later today and let you know!

crushalot said:
Here you go bud. This is the stock firmware from 1.29.401.12. It has the stock radio and recovery(just in case).
https://dl.dropboxusercontent.com/u/36946918/1.29.401.12.zip
If you flash that, it should put everything back to complete stock in regards to the firmware.
Should be able to s-on and relock afterwards and should be no signs of mods.
Let me know if you need help finishing up.
Click to expand...
Click to collapse
Well now I've done it. Reflashed the firmware, put my CID back to TELUS001. Went back to S-ON, locked BOOTLOADER.
Now I am showing TAMPERED / LOCKED.
I reunlocked the bootloader, and am now showing TAMPERED / UNLOCKED, with stock recovery. I put back on TWRP and it shows TAMPERED / UNLOCKED.
I tried re-running REVONE and I am unable to go back to S-OFF.
What the heck happened?

WorldIRC said:
Well now I've done it. Reflashed the firmware, put my CID back to TELUS001. Went back to S-ON, locked BOOTLOADER.
Now I am showing TAMPERED / LOCKED.
I reunlocked the bootloader, and am now showing TAMPERED / UNLOCKED, with stock recovery. I put back on TWRP and it shows TAMPERED / UNLOCKED.
I tried re-running REVONE and I am unable to go back to S-OFF.
What the heck happened?
Click to expand...
Click to collapse
Can you verify your hboot is back down to level 1.44?
If it is, we should be able to revone to s-off again, but we may need to try a few times.
Did you have tampered displayed before you went s-on?
It did display locked rather than relocked so that it good. However it must be picking something up as non original as that is what causes the tampered flag.

crushalot said:
Can you verify your hboot is back down to level 1.44?
If it is, we should be able to revone to s-off again, but we may need to try a few times.
Did you have tampered displayed before you went s-on?
It did display locked rather than relocked so that it good. However it must be picking something up as non original as that is what causes the tampered flag.
Click to expand...
Click to collapse
Yes, I am on HBOOT 1.44 from April 2013.
Tampered was not present before (I had hidden it with Revone). Tampered came back only after I re-locked the bootloader (with the stock recovery via firmware file you provided to me).
I tried to go S-OFF but I keep getting error 2 or 6 when doing ./revone -P
Meanwhile no issues doing 2 other phones with Revone (fresh out of box).

WorldIRC said:
Yes, I am on HBOOT 1.44 from April 2013.
Tampered was not present before (I had hidden it with Revone). Tampered came back only after I re-locked the bootloader (with the stock recovery via firmware file you provided to me).
I tried to go S-OFF but I keep getting error 2 or 6 when doing ./revone -P
Meanwhile no issues doing 2 other phones with Revone (fresh out of box).
Click to expand...
Click to collapse
I had one phone that gave me trouble with revone. I tried it like 20 times and nothing was working. Then I ran all the commands in a terminal window on the phone rather than adb shell and it worked. Can you try that?
There are also some other good tips in the revone thread, but I forget them all and will have to read it again.
It wouldn't have been the recovery as that for sure was the stock recovery. Did you download the stock nandroid or did you make it yourself?

[Q] Australia unbranded wanted to go complete STOCK

Firstly, Aussie dont have RUU, so I am going to use Europe since aussie are 1.28.980.17 for 4.1.2
Currently, I am on stock 4.2.2 with CWM recovery and "RELOCKED" bootloader (I typed fastboot oem lock) and s-off.
But, I want to try this and not quite sure if it is going to work or not.
1. Since I relocked bootloader, I cant flash stock recovery.
2. Use RUU_M7_UL_JB_50_HTC_Europe_1.28.401.7_Radio_4A.13. 3231.27_10.31.1131.05_release_310878_signed.exe to get 1.44 hboot.
3. unlock bootloader again using revone
4. Flash CWM then restore from my own 4.1.2 CWM backup.
5. Flash stock 1.29.980.17 firmware.zip
6. Lock bootloader and s-on
7. OTA update for 4.2.2
Is this going to work?
Thanks in advance :laugh:

reservin said:
Firstly, Aussie dont have RUU, so I am going to use Europe since aussie are 1.28.980.17 for 4.1.2
Currently, I am on stock 4.2.2 with CWM recovery and "RELOCKED" bootloader (I typed fastboot oem lock) and s-off.
But, I want to try this and not quite sure if it is going to work or not.
1. Since I relocked bootloader, I cant flash stock recovery.
2. Use RUU_M7_UL_JB_50_HTC_Europe_1.28.401.7_Radio_4A.13. 3231.27_10.31.1131.05_release_310878_signed.exe to get 1.44 hboot.
3. unlock bootloader again using revone
4. Flash CWM then restore from my own 4.1.2 CWM backup.
5. Flash stock 1.29.980.17 firmware.zip
6. Lock bootloader and s-on
7. OTA update for 4.2.2
Is this going to work?
Thanks in advance :laugh:
Click to expand...
Click to collapse
Your method will work, but you could also see if someone has uploaded a nandroid backup of your Aussie stock. Just a thought.

kibmikey1 said:
Your method will work, but you could also see if someone has uploaded a nandroid backup of your Aussie stock. Just a thought.
Click to expand...
Click to collapse
So flashing RUU doesnt require unlocked bootloader. is it right?
Yeah I saw aussie stock unbranded CWM as well.
Thanks!!
BTW, after I restore from nandroid backup, then receive OTA of 4.2.2, does that contains 4.2.2 firmware.zip as well?
If it is, then I do not need flash 1.29.980.17 firmware.zip before right?

reservin said:
So flashing RUU doesnt require unlocked bootloader. is it right?
Yeah I saw aussie stock unbranded CWM as well.
Thanks!!
BTW, after I restore from nandroid backup, then receive OTA of 4.2.2, does that contains 4.2.2 firmware.zip as well?
If it is, then I do not need flash 1.29.980.17 firmware.zip before right?
Click to expand...
Click to collapse
4.2.2. OTA, as far as I know, will contain the firmware, but you could flash it just to make sure everything is right. All the OTA will do is write over it anyway, so no harm, no foul either way. I would double check what firmware you need for the rom you're flashing, just to be sure.
Here's a link to that nandroid backup, too. Hope it goes smoothly.

kibmikey1 said:
4.2.2. OTA, as far as I know, will contain the firmware, but you could flash it just to make sure everything is right. All the OTA will do is write over it anyway, so no harm, no foul either way. I would double check what firmware you need for the rom you're flashing, just to be sure.
Here's a link to that nandroid backup, too. Hope it goes smoothly.
Click to expand...
Click to collapse
I successfully flashed Europe RUU with 1.44 hboot!
Now I am restoring nandroid 4.1.2 backup. I still need aussie 4.1.2 firmware.zip as well right?

You do realise that if you go to S On then update to 4.2.2 you will have hboot 1.54 and will be unable to get S Off back ?
Sent from my HTC One using xda app-developers app

paul_59 said:
You do realise that if you go to S On then update to 4.2.2 you will have hboot 1.54 and will be unable to get S Off back ?
Sent from my HTC One using xda app-developers app
Click to expand...
Click to collapse
Yep. I need to visit service center next week.
Now i am not sure if OTA still can be applied on Australian rom + European firmware with locked bootloader and s-on..

Factory reset without Ruu?

I am having a hard time restoring my phone to stock for a warranty return.
Basically i can't find a Orang001 RUU restore file, i don't think one exists! I have found a CWM recovery file, however when restoring it just hangs at the HTC logo and won't reboot.
I'm starting to think i will have to give up.
Is there any advise you can give to restore my phone??

Grale said:
I am having a hard time restoring my phone to stock for a warranty return.
Basically i can't find a Orang001 RUU restore file, i don't think one exists! I have found a CWM recovery file, however when restoring it just hangs at the HTC logo and won't reboot.
I'm starting to think i will have to give up.
Is there any advise you can give to restore my phone??
Click to expand...
Click to collapse
Have you tried factory resetting your phone then restoring?

squabbi said:
Have you tried factory resetting your phone then restoring?
Click to expand...
Click to collapse
Sorry i typed this out quickly this morning.
I am S-OFF / Unlocked ect.. Running Android HD rom. I have no backup of the original rom.

I made this guide a while back - http://forum.xda-developers.com/showthread.php?t=2519259
For myself it was returning to complete stock 02 UK. There was no RUU for me either
http://www.htc1guru.com/dld/m7-cwm-nandroid-backup-cid-orang001-1-28-61-7-2013-04-22-zip/ this is an earlier nandroid version for Orange
Try the steps on my thread and hope they work for you. I would leave the phone as s off though. When changing your CID back to Orange ORANG001

Grale said:
Sorry i typed this out quickly this morning.
I am S-OFF / Unlocked ect.. Running Android HD rom. I have no backup of the original rom.
Click to expand...
Click to collapse
Thats fine!
No need for the original rom, you said you found a cwm restore file. Did you try factory resetting then doing the cwm restore?

stovie_steve said:
I made this guide a while back - http://forum.xda-developers.com/showthread.php?t=2519259
For myself it was returning to complete stock 02 UK. There was no RUU for me either
http://www.htc1guru.com/dld/m7-cwm-nandroid-backup-cid-orang001-1-28-61-7-2013-04-22-zip/ this is an earlier nandroid version for Orange
Try the steps on my thread and hope they work for you. I would leave the phone as s off though. When changing your CID back to Orange ORANG001
Click to expand...
Click to collapse
Stovie_steve, this looks likes just what i need!!
4. Downgrade hboot to 1.44 from sneakyghost http://d-h.st/qfc:
The link is down buddy, any other links for that?? :good:

Grale said:
Stovie_steve, this looks likes just what i need!!
4. Downgrade hboot to 1.44 from sneakyghost http://d-h.st/qfc:
The link is down buddy, any other links for that?? :good:
Click to expand...
Click to collapse
Not surprised the Link is down - I made that post ages ago and should probably update it...
http://www.htc1guru.com/dld/1-29-401-12_hboot_1-44-zip/

I'm up to:
5. Downloaded 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
6. Reboot into bootloader and fastboot oem writecid O2___001 followed by fastboot oem writesecureflag 3. This will return to S-ON but it will be reobtained again in a few minutes ****NOTE I DID THIS STEP TO S-ON BUT IT MIGHT NOT BE NECESSARY****
No 5. I take it i just run the RUU and install then No 6. instead of writing CID O2___001 i write my original ORANG001 ?
Thanks for your help so far, much appreciated :good:

Grale said:
I'm up to:
5. Downloaded 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
6. Reboot into bootloader and fastboot oem writecid O2___001 followed by fastboot oem writesecureflag 3. This will return to S-ON but it will be reobtained again in a few minutes ****NOTE I DID THIS STEP TO S-ON BUT IT MIGHT NOT BE NECESSARY****
No 5. I take it i just run the RUU and install then No 6. instead of writing CID O2___001 i write my original ORANG001 ?
Thanks for your help so far, much appreciated :good:
Click to expand...
Click to collapse
Yeah thats right. If you check the thread again I've cleaned it up a bit. Anywhere I've mentioned O2 you just substitute it for ORANG001
Any problems just get back to me!

stovie_steve said:
Yeah thats right. If you check the thread again I've cleaned it up a bit. Anywhere I've mentioned O2 you just substitute it for ORANG001
Any problems just get back to me!
Click to expand...
Click to collapse
Just a quick one. I've gone through to no.6. I have installed the orang001 nand and i am ready to reboot, however it is saying:
Root access is missing. Root device?
THIS CAN NOT BE UNDONE.
Which should i choose??
No.
Yes. Root device (/system/xbin/su)

Grale said:
Just a quick one. I've gone through to no.6. I have installed the orang001 nand and i am ready to reboot, however it is saying:
Root access is missing. Root device?
THIS CAN NOT BE UNDONE.
Which should i choose??
No.
Yes. Root device (/system/xbin/su)
Click to expand...
Click to collapse
You can choose yes and continue as normal. Once you reboot, just to be sure re-run revone, and run the remove TAMPERED command and make sure the bootloader is UNLOCKED

stovie_steve said:
You can choose yes and continue as normal. Once you reboot, just to be sure re-run revone, and run the remove TAMPERED command and make sure the bootloader is UNLOCKED
Click to expand...
Click to collapse
Thank you. I've spent 4 days pulling my hair out!!
Everything is back to stock now.. Fingers crossed it makes it through the warranty checks
Thanks again, you are awesome

Grale said:
Thank you. I've spent 4 days pulling my hair out!!
Everything is back to stock now.. Fingers crossed it makes it through the warranty checks
Thanks again, you are awesome
Click to expand...
Click to collapse
No problem, you're welcome save the page as a bookmark for future reference to get back to stock again I recommend not OTA'ing right all the way up to the latest hboot as its much harder to obtain s off on later hboots!
Enjoy stock!