Database Develop

[Q] Downgrade HBoot 2.00 Gingerbread 2.3.5 with HTC sence 3.0 "Permission denied"

[Q] Downgrade HBoot 2.00 Gingerbread 2.3.5 with HTC sence 3.0 "Permission denied"
I think it's the right place to ask this question
I read almost every thread, however I got confused and couldn't for the life of me, figure out what to do
Here's the problem that is asked so many times, but all with confusing discussions:
I got HTC Incredible s with Gingerbread 2.3.5 and Hboot 2.00 and software number 3.09.415.2
I did the unlock via HTCdev -------------------> no problem
Installed recovery ---------------------------------> no problem
The problem is, I can't downgrade Hboot 2.00 to 1.16 or 1.13. I face this problem after giving command for adb shell:
cd C:\Android
adb.exe shell
adb misc_version /data/local/tmp/ ----------------> from this point. All i get is "permission denied"
I tried using HTC toolkit, making a gold card (the process in which 3 questions were to answer: you device rooted? - want a goldcard?-got unlocked via HTCdev?) - HIS tool.... none would work and after doing these steps, RUU wouldn't install with the error.
can anyone give me a hand?
thanks

Use the script that is in this thread. It should work just fine.
http://forum.xda-developers.com/showthread.php?t=1373697
Just because you have unlocked the bootloader does not mean you are rooted.
You should probably try answering NO to the are you rooted question and see where that gets you.

tpbklake said:
Use the script that is in this thread. It should work just fine.
http://forum.xda-developers.com/showthread.php?t=1373697
Just because you have unlocked the bootloader does not mean you are rooted.
You should probably try answering NO to the are you rooted question and see where that gets you.
Click to expand...
Click to collapse
I did. I responded with no, and of course another time with yes.
but nonetheless, RUU aborts and tells me that I haven't picked the right RUU.
Edit: I forgot to tell, I flashed Superuser through recovery, nothing changed

mr-baan said:
I did. I responded with no, and of course another time with yes.
but nonetheless, RUU aborts and tells me that I haven't picked the right RUU.
Edit: I forgot to tell, I flashed Superuser through recovery, nothing changed
Click to expand...
Click to collapse
Flashing SuperUser will give your apps root access, but in order to run the script successfully, you need a ROM that has an unsecured boot.img, such as any custom ROM. Try installing CM 7 and then re-run the script.
That is why you are getting the access denied message while the script is running.

tpbklake said:
Flashing SuperUser will give your apps root access, but in order to run the script successfully, you need a ROM that has an unsecured boot.img, such as any custom ROM. Try installing CM 7 and then re-run the script.
That is why you are getting the access denied message while the script is running.
Click to expand...
Click to collapse
Thanks for the info.
CM7? Where can I find that?
If you mean cm7 ROM, as far as i know, it's a custom ROM. will I be able to install a ROM regarding my cell is s-on and don't have access to root?

mr-baan said:
Thanks for the info.
CM7? Where can I find that?
If you mean cm7 ROM, as far as i know, it's a custom ROM. will I be able to install a ROM regarding my cell is s-on and don't have access to root?
Click to expand...
Click to collapse
You will just be required to pull the boot.img from the .zip file. After installing the ROM, reboot to fasboot menu.
Then type in command: fastboot flash boot boot.img
Both "boot" are required and do not forget the .img at the end. If you changed the file name, just replace the second "boot" in the command line with whatever u renamed it to but do not forget to put .img at the end

072665995 said:
You will just be required to pull the boot.img from the .zip file. After installing the ROM, reboot to fasboot menu.
Then type in command: fastboot flash boot boot.img
Both "boot" are required and do not forget the .img at the end. If you changed the file name, just replace the second "boot" in the command line with whatever u renamed it to but do not forget to put .img at the end
Click to expand...
Click to collapse
I'm sorry, could you expand your answer a little bit and guide me more specifically?
thanks

When u download CM7, its in the form of a .zip file. Open the zip file using winrar or whatever unzipping tool u use. Open it, do not extract it. When you open it, you will find a file named "boot." This is a .img file. Copy (not cut) this file where u have adb.exe, fastboot.exe, and AdbWinApi.dll. I will assume u have these files when u downloaded Android SDK. For simplicity sake, do not rename it. Then put the ROM onto your phone and flash the ROM through your recovery. The boot.img file is in the ROM. After you finish flashing the ROM, reboot to bootloader and from there, enter fastboot mode (shud be the first option. just click power button to select it. Then on you computer, open command prompt and navigate to the file with the boot.img, adb.exe, fastboot.exe, and AdbWinApi.dll. In the command prompt, it should say cd c:/(wherever your android stuff is in)/ another folder maybe for organization)/.....>
from there type in fastboot flash boot boot.img
After a few seconds the ROM will have been flashed to your phone. Reboot and u have CM7 on your phone. Then run the RUU.
If the RUU fails, tell us the error number. Although i dont really know much about this, tpblake does and im sure hed be willing to tell you what the error code means cuz the RUU really doesnt tell u jack.

So I did, step by step
I did all, cm7 worked perfectly. then I did as you said, fastboot boot boot.img
As foreseen, error 155 popped out. "please get the correct ROM update utility and try again"
I would be thankful if you guys help me through.
Yet I have another question. If installing custom ROMs are this easily possible, then why should we do the s-off?

Re: [Q] Downgrade HBoot 2.00 Gingerbread 2.3.5 with HTC sence 3.0 "Permission denied"
mr-baan said:
So I did, step by step
I did all, cm7 worked perfectly. then I did as you said, fastboot boot boot.img
As foreseen, error 155 popped out. "please get the correct ROM update utility and try again"
I would be thankful if you guys help me through.
Yet I have another question. If installing custom ROMs are this easily possible, then why should we do the s-off?
Click to expand...
Click to collapse
You have to s-off to change hboot , rom , kernel , and radio. If you want to downgrade just relock the bootloader and then run the ruu
Sent from my Incredible S using xda premium

zulmajdi said:
You have to s-off to change hboot , rom , kernel , and radio. If you want to downgrade just relock the bootloader and then run the ruu
Sent from my Incredible S using xda premium
Click to expand...
Click to collapse
Once I did the relock, it faced security problems and wasn't working, so I had to unlock it again.
About the second question of mine, I know what s-off is for. My question is, moments ago I flashed CM7 custom ROM to my phone and it works properly. For installing ROMs, being s-off doesn't seem so necessary. or am I wrong?

zulmajdi said:
You have to s-off to change hboot , rom , kernel , and radio. If you want to downgrade just relock the bootloader and then run the ruu
Sent from my Incredible S using xda premium
Click to expand...
Click to collapse
Yes this. Error 155 will pop up if u have an unlocked bootloader. Relock bootloader and rerun RUU assuming the script ran everything right
Edit: To your above question, yes S-OFF isnt necessary. However, it is necessary for some ROMs to have S-OFF or Blackrose HBOOT, the latter of which can only be obtained from achieving S-OFF. And what kind of security problems

Re: [Q] Downgrade HBoot 2.00 Gingerbread 2.3.5 with HTC sence 3.0 "Permission denied"
mr-baan said:
Once I did the relock, it faced security problems and wasn't working, so I had to unlock it again.
About the second question of mine, I know what s-off is for. My question is, moments ago I flashed CM7 custom ROM to my phone and it works properly. For installing ROMs, being s-off doesn't seem so necessary. or am I wrong?
Click to expand...
Click to collapse
No you're not. If you want to custom install radio , kernel , hboot and rom need to gain s-off but some rom no need to s-off. Like miui rom need s-off and hboot blackrose. Just ignore the security thingy. I had the same problem before for the security but i just run the ruu and install it works. It say security problem on fastboot rite? Then just run the ruu while you on fastboot mode. Hope it works
Also adb shell command need super permission from the device. You have to root your device.
Sent from my Incredible S using xda premium

thank you all. it worked. my Hboot is now 1.13.0000
now Revolutionary is giving me crap! It says: invalid Beta key... I did it like a thousend times!
Quick question. shall I unlock it again? because when I do, In the process of HTCdev, I get this error: <fastboot> unknown error

Re: [Q] Downgrade HBoot 2.00 Gingerbread 2.3.5 with HTC sence 3.0 "Permission denied"
mr-baan said:
thank you all. it worked. my Hboot is now 1.13.0000
now Revolutionary is giving me crap!
Quick question. shall I unlock it again? because when I do, In the process of HTCdev, I get this error: unknown error
Click to expand...
Click to collapse
There is a video for incs device tutorial to set revolutionary at youtube. Watch it and try. Glad we can help you ^^
Sent from my Incredible S using xda premium

zulmajdi said:
There is a video for incs device tutorial to set revolutionary at youtube. Watch it and try. Glad we can help you ^^
Sent from my Incredible S using xda premium
Click to expand...
Click to collapse
Oh, I know how. I have this cell phone for about two years. It was root and s-off was due. But some accidents happened and I sent it for warranty, they sent it back with Hboot 2.00.0000.
But my problem is, Beta code sent by revolutionary is invalid when inserted in revolutionary.exe command propmt.

Thank you guys, this worked.
To sum it up, If you have "permission denied" problem with runme - and then, installing the RUU - relock your phone, run the RUU. and everything is there.
Peace

Re: [Q] Downgrade HBoot 2.00 Gingerbread 2.3.5 with HTC sence 3.0 "Permission denied"
mr-baan said:
Thank you guys, this worked.
To sum it up, If you have "permission denied" problem with runme - and then, installing the RUU - relock your phone, run the RUU. and everything is there.
Peace
Click to expand...
Click to collapse
Install blackrose and you basicly done my friend have a good day
Sent from my Incredible S using xda premium

Rogers stock htc one ruu? ? ? ?

I have been searching for weeks to find the stock Ruu for the HTC One on Rogers.
Does any one know the download link?
Able to upload it?
Or point me in the right direction to find the ruu?
It would be a lot of help and greatly appreciated. I have not had this problem with any other phone. Not even the galaxy s4.
Sent from my SGH-I337M using xda premium

Leonidas87 said:
I have been searching for weeks to find the stock Ruu for the HTC One on Rogers.
Does any one know the download link?
Able to upload it?
Or point me in the right direction to find the ruu?
It would be a lot of help and greatly appreciated. I have not had this problem with any other phone. Not even the galaxy s4.
Sent from my SGH-I337M using xda premium
Click to expand...
Click to collapse
I also wasn't able to find it. I need it too.

It has to be out there somewhere. You can not tell me Rogers has kept it on lock when even the Rogers ruins is out for the s4.
DRIVING ME CRAZY BECAUSE I HAVE A DEAD PIXEL AND WOULD LIKE TO USE MY WARANTY. (Not yelling just emphasising frustration)
Sent from my SGH-I337M using xda premium

So no one knows where this is?
Sent from my SGH-I337M using xda premium

Who releases the RUU's? HTC or Rogers?

HM796 said:
Who releases the RUU's? HTC or Rogers?
Click to expand...
Click to collapse
Correct me if I'm wrong, but I think it's HTC who releases RUUs. I don't know if the carrier has a say on that though.

there is no rogers ruu at the moment

Check here, I think this is what you are looking for?
http://www.htcdev.com/devcenter/downloads/P10

twigggs said:
Check here, I think this is what you are looking for?
Click to expand...
Click to collapse
that's actually helpful;
on that same website theres a filter at the top
click "One" for device
and "Rogers" for carrier then click find files
I found the one for my specific build but it's a .tar file and i have no idea how to flash it lol
if anyone knows anything about how to do this, this is the file name i downloaded: m7-jb-crc-3.4.10-42e6c45.tar

rogers ruu
Rogers stock RUU anyone please?

lelloo said:
Rogers stock RUU anyone please?
Click to expand...
Click to collapse
I need it too

bigystyle84 said:
I need it too
Click to expand...
Click to collapse
Perhaps they're waiting for the 4.2.2 update to put out a bunch of RUU's? Just guessing. I have heard that they're not released, they're leaked. But all the US ones are available on htc.com. I was at the rogers store a few days ago and they said they don't have it and HTC will put them out, but I think that's bs. What if somebody needed their phone factory reset and it was all covered under warranty? Would they throw the device out and ship a new one? No, it'd be much cheaper and more convenient to run the ROM update utility. I don't see what harm it'd be doing to upload a file that they already have. After all android is meant to be open-source and like you can modify it as you wish.
For people who are in desperate need of a factory reset, get supercid and run the Cingular (at&t) ruu. That's worst case scenario though. I have my phone running stock rogers but I used the ota file and the nandroid backup. I can write a quick tutorial on how to do that if anyone wants. Also I have erased tampered and relocked to just say locked and reverted s-off to s-on. Again can make another quick tutorial if anyone wants.
Point is they need to release the ruu and its stupid that at&t has released theirs but rogers hasn't because they're basically the same company, just modified for each country. Hopefully rogers ruu is out soon.
Sent from my HTC One using xda app-developers app

Rogers htc one unroot
I have a rogers htc one thats on the stock rom but is rooted i want to unroot and lock the bootloader how would i do this please help i could not fina an ruu
---------- Post added at 01:26 AM ---------- Previous post was at 01:01 AM ----------
zelliott7234 said:
Perhaps they're waiting for the 4.2.2 update to put out a bunch of RUU's? Just guessing. I have heard that they're not released, they're leaked. But all the US ones are available on htc.com. I was at the rogers store a few days ago and they said they don't have it and HTC will put them out, but I think that's bs. What if somebody needed their phone factory reset and it was all covered under warranty? Would they throw the device out and ship a new one? No, it'd be much cheaper and more convenient to run the ROM update utility. I don't see what harm it'd be doing to upload a file that they already have. After all android is meant to be open-source and like you can modify it as you wish.
For people who are in desperate need of a factory reset, get supercid and run the Cingular (at&t) ruu. That's worst case scenario though. I have my phone running stock rogers but I used the ota file and the nandroid backup. I can write a quick tutorial on how to do that if anyone wants. Also I have erased tampered and relocked to just say locked and reverted s-off to s-on. Again can make another quick tutorial if anyone wants.
Point is they need to release the ruu and its stupid that at&t has released theirs but rogers hasn't because they're basically the same company, just modified for each country. Hopefully rogers ruu is out soon.
Sent from my HTC One using xda app-developers app
Click to expand...
Click to collapse
Can you write a tutorial please

arshbrar1997 said:
I have a rogers htc one thats on the stock rom but is rooted i want to unroot and lock the bootloader how would i do this please help i could not fina an ruu
---------- Post added at 01:26 AM ---------- Previous post was at 01:01 AM ----------
Can you write a tutorial please
Click to expand...
Click to collapse
You will need:
fastboot/adb
http://bugsylawson.com/files/file/1...314-release-318662-signedms4ef8qvnqbkudqrzip/
http://bugsylawson.com/files/file/1857-m7-cwm-nandroid-backup-cid-roger001-12963117/
http://download2.clockworkmod.com/recoveries/recovery-clockwork-touch-6.0.3.1-m7.img
http://revolutionary.io/revone
1. flash cwm recovery
Code:
fastboot flash recovery recovery-clockwork-touch-6.0.3.1-m7.img
2. Copy the nandroid backup you downloaded to this folder on your phone [MAKE SURE YOU EXTRACT IT TO A FOLDER FIRST, THEN COPY THE FOLDER] : /sdcard/clockworkmod/backup
3. Boot into recovery:
Code:
adb reboot recovery
4. Go to backup and restore > restore > select the nandroid backup folder you copied to your phone
5. Let the nandroid backup restore
6. Extract the Rogers OTA update, then extract the firmware.zip inside of it
7. Take the recovery.img and flash it
Code:
fastboot flash recovery recovery.img
8. Lock the bootloader
Code:
fastboot oem lock
9. In normal mode push revone to your /data/local/tmp/
Code:
adb push revone /data/local/tmp/
10. Open ADB shell
Code:
adb shell
11. cd and chmod revone
Code:
cd /data/local/tmp
Code:
chmod 755 revone
12. Run this commmand
Code:
./revone -P
13. Assuming revone reboots success, reboot by holding the power button for 15 seconds
14. Once you've rebooted, do this:
Code:
adb shell
cd /data/local/tmp
./revone -s 0 -u
15. Once revone reports success, reboot again by holding power for 15 seconds
16. Do this:
Code:
adb shell
cd /data/local/tmp
./revone -t
17. Reboot again if revone is succesful
18.
Code:
adb shell
cd /data/local/tmp
./revone -l
19. Assuming revone reports success again, reboot to the bootloader
Code:
adb reboot bootloader
20.
Code:
fastboot oem writesecureflag 3
21.
Code:
fastboot reboot-bootloader
You should now have tampered erased, relocked changed to locked and S-ON. If you want you can do a factory reset from settings or from the bootloader, but you should be good.

Thank you
1. flash cwm recovery
Code:
fastboot flash recovery recovery-clockwork-touch-6.0.3.1-m7.img
2. Copy the nandroid backup you downloaded to this folder on your phone [MAKE SURE YOU EXTRACT IT TO A FOLDER FIRST, THEN COPY THE FOLDER] : /sdcard/clockworkmod/backup
3. Boot into recovery:
Code:
adb reboot recovery
4. Go to backup and restore > restore > select the nandroid backup folder you copied to your phone
5. Let the nandroid backup restore
6. Extract the Rogers OTA update, then extract the firmware.zip inside of it
7. Take the recovery.img and flash it
Code:
fastboot flash recovery recovery.img
8. Lock the bootloader
Code:
fastboot oem lock
9. In normal mode push revone to your /data/local/tmp/
Code:
adb push revone /data/local/tmp/
10. Open ADB shell
Code:
adb shell
11. cd and chmod revone
Code:
cd /data/local/tmp
Code:
chmod 755 revone
12. Run this commmand
Code:
./revone -P
13. Assuming revone reboots success, reboot by holding the power button for 15 seconds
14. Once you've rebooted, do this:
Code:
adb shell
cd /data/local/tmp
./revone -s 0 -u
15. Once revone reports success, reboot again by holding power for 15 seconds
16. Do this:
Code:
adb shell
cd /data/local/tmp
./revone -t
17. Reboot again if revone is succesful
18.
Code:
adb shell
cd /data/local/tmp
./revone -l
19. Assuming revone reports success again, reboot to the bootloader
Code:
adb reboot bootloader
20.
Code:
fastboot oem writesecureflag 3
21.
Code:
fastboot reboot-bootloader
You should now have tampered erased, relocked changed to locked and S-ON. If you want you can do a factory reset from settings or from the bootloader, but you should be good.[/QUOTE]
Thanks for taking the time to write this ill let you know how it goes

arshbrar1997 said:
Thanks for taking the time to write this ill let you know how it goes
Click to expand...
Click to collapse
No problem, worked for me. Let me know of any issues.

thanks for the steps. I did all steps fine until the ./revone -P command where my phone always reboots after gaining root access. revone successful is never shown.
any ideas? I've tried this on 2 different computers (xp and win7).
i can't post this problem in the actual s-off thread cause I"m too new.

allisfair said:
thanks for the steps. I did all steps fine until the ./revone -P command where my phone always reboots after gaining root access. revone successful is never shown.
any ideas? I've tried this on 2 different computers (xp and win7).
i can't post this problem in the actual s-off thread cause I"m too new.
Click to expand...
Click to collapse
Copied this from the revone thread
a. If revone reports success reboot the device and proceed to step 14
b. If revone reboots the device (we'll pretend this isn't an undiagnosed random crash) please wait 2 minutes then try again from step 11.
c. If revone reports that you need to reboot and try again please reboot and try again from step 11.
Sent from my HTC One using xda app-developers app

I need Roger's HTC One Stock Nandroid
zelliott7234 said:
Perhaps they're waiting for the 4.2.2 update to put out a bunch of RUU's? Just guessing. I have heard that they're not released, they're leaked. But all the US ones are available on htc.com. I was at the rogers store a few days ago and they said they don't have it and HTC will put them out, but I think that's bs. What if somebody needed their phone factory reset and it was all covered under warranty? Would they throw the device out and ship a new one? No, it'd be much cheaper and more convenient to run the ROM update utility. I don't see what harm it'd be doing to upload a file that they already have. After all android is meant to be open-source and like you can modify it as you wish.
For people who are in desperate need of a factory reset, get supercid and run the Cingular (at&t) ruu. That's worst case scenario though. I have my phone running stock rogers but I used the ota file and the nandroid backup. I can write a quick tutorial on how to do that if anyone wants. Also I have erased tampered and relocked to just say locked and reverted s-off to s-on. Again can make another quick tutorial if anyone wants.
Point is they need to release the ruu and its stupid that at&t has released theirs but rogers hasn't because they're basically the same company, just modified for each country. Hopefully rogers ruu is out soon.
Sent from my HTC One using xda app-developers app
Click to expand...
Click to collapse
Hi, I bricked my phone but I managed to fix it, although I had to flash a custom Stock Android ROM. But I want to go back to Sense 5, I'm with Rogers so the RUU is not an option and the Nandroid backup on the list of RUUs, OTAs and Nandroids gives me MD5 mismatch so I can't flash it. I don't want to get a super CID because I'd like to get OTA updates from HTC. Really what I want is to have my phone just as it was when I bought it. I have the bootloader unlocked, S-Off, and my CID is ROGER001. Can you help me with the Nandroid backup?

Rogers Htc One stock ruu
Does someone have Rogers Htc One stock ruu ?
please help.

Guide - Get s-off on 1.31 HTC One (Sprint) Update:

Hello, here is a very simple guide to be able to use revone to s-off on the 1.31 update.
Make sure you have dev unlocked and you flashed a custom recovery (CWM or TWRP both work fine)
After that, you need to make sure adb works (if you can't figure out how to do any of this, I will not help you. If you can't find out basic things about Android, then you shouldn't have s-off)
So, as we all know, HTC has made it so with newer bootloaders, you cannot downgrade to older firmwares. Well, this is true except when the software version changes but the hboot version doesn't. So all we need to do is this:
Boot into recovery
adb shell
echo "1.29.651.10" | dd of=/dev/block/mmcblk0p19 bs=1 seek=160
adb reboot bootloader
fastboot oem lock
then just flash an RUU of 1.29 and it'll work out. All you do is flash the misc partition to contain the proper mainver and it works.

Indirect said:
Hello, here is a very simple guide to be able to use revone to s-off on the 1.31 update.
Make sure you have dev unlocked and you flashed a custom recovery (CWM or TWRP both work fine)
After that, you need to make sure adb works (if you can't figure out how to do any of this, I will not help you. If you can't find out basic things about Android, then you shouldn't have s-off)
So, as we all know, HTC has made it so with newer bootloaders, you cannot downgrade to older firmwares. Well, this is true except when the software version changes but the hboot version doesn't. So all we need to do is this:
Boot into recovery
adb shell
echo "1.29.651.10" | dd if=/dev/block/mmcblk0p19 bs=1 seek=160
adb reboot bootloader
then just flash an RUU of 1.29 and it'll work out. All you do is flash the misc partition to contain the proper mainver and it works.
Click to expand...
Click to collapse
Flash an ruu.zip or can it be ruu.exe also? Should revone be done after the ruu?
Sent from my PG86100 using xda app-developers app

bleichtman said:
Flash an ruu.zip or can it be ruu.exe also? Should revone be done after the ruu?
Sent from my PG86100 using xda app-developers app
Click to expand...
Click to collapse
either or and yes. After you RUU.

Indirect said:
either or and yes. After you RUU.
Click to expand...
Click to collapse
Just to be sure cause I'm having issues. This will allow me to flash a 1.29 ruu after having the 1.31 update? This could save me!
Sent from my PG86100 using xda app-developers app

bleichtman said:
Just to be sure cause I'm having issues. This will allow me to flash a 1.29 ruu after having the 1.31 update? This could save me!
Sent from my PG86100 using xda app-developers app
Click to expand...
Click to collapse
Yes...as it is said in the post.

Indirect said:
Yes...as it is said in the post.
Click to expand...
Click to collapse
Thank you...had a lot of aggravation lately. Sorry for the stupid question.
Sent from my PG86100 using xda app-developers app

So I didn't see this post but did something slightly different and it worked perfect.
Unlocked the bootloader via HTCdev
pushed TWRP for Sprint
Flashed SuperSu
Then followed the revone instructions particularly step 3 su (and going onto the device to grant access.) and everything worked perfect and never had to downgrade from 1.31.
MG

Nice work Indirect good lookin out

Win for Indirect!
Sent from my HTCONE using xda premium

THANK YOU!!!
I owe you!!!

Indirect... you saved many a phones. I have been searching for this and read many a post where people were scrambling (not necessarily for s-off, but the fact that they relocked the bootloader and could not run the 1.29 RUU. I encountered the same thing but just unlocked again and flashed my stock nandroid. Thanks!
If I run just...
Boot into recovery
adb shell
echo "1.29.651.10" | dd of=/dev/block/mmcblk0p19 bs=1 seek=160
adb reboot bootloader
fastboot oem lock
then just flash an RUU of 1.29
Does that leave me with a stock build and s-on? In the event I had to part with the One, etc.

Yes.
Sent from my hidden jewel

Indirect said:
Yes.
Click to expand...
Click to collapse
Kind of related thing happened to me, what do I make of this?
I was S-OFF, but with the newest firmware and custom ROM, TWRP installed.
I did the fastboot oem lock, then RUU'ed back to OMJ's straight up stock Sprint_HTC_One_m7wls_1.29.651.10_RUU.zip
Once that got booted up I went ahead and did the system update to 1.31.
NOW, when I go into bootloader it says "relocked" up top, but says S-OFF. S-OFF?!? Didn't I relock it and RUU?
Also, when I try to enter recovery, all I get is a phone with a red triangle above it.

FlowingAway said:
Kind of related thing happened to me, what do I make of this?
I was S-OFF, but with the newest firmware and custom ROM, TWRP installed.
I did the fastboot oem lock, then RUU'ed back to OMJ's straight up stock Sprint_HTC_One_m7wls_1.29.651.10_RUU.zip
Once that got booted up I went ahead and did the system update to 1.31.
NOW, when I go into bootloader it says "relocked" up top, but says S-OFF. S-OFF?!? Didn't I relock it and RUU?
Also, when I try to enter recovery, all I get is a phone with a red triangle above it.
Click to expand...
Click to collapse
When you RUU, it doesn't turn the security back on, hence the S-Off still. However, it does put the stock recovery back on, which is why it has the phone with the red triangle. If you want S-On, you can flash the Stock H-boot, or use Revone to make it say locked instead of relocked and say S-On (I believe it can do that, although I'm not entirely sure.) As for recovery, just re-flash twrp in fastboot.
Edit: "Fastboot OEM lock" doesn't mess with security at all. It just re-locks the bootloader.
Sent from my HTCONE using xda premium

If I am S-on and want a factory recovery, can a stock recovery be flashed in fastboot once back to 1.31?

enmriley said:
If I am S-on and want a factory recovery, can a stock recovery be flashed in fastboot once back to 1.31?
Click to expand...
Click to collapse
Yes.
Sent from my HTCONE using xda premium

plegrand said:
Yes.
Sent from my HTCONE using xda premium
Click to expand...
Click to collapse
Thanks. one more question on this topic. The recovery (or screen) with the red triangle will flag a problem with Sprint right? I assumed the RUU didn't flash the stock recovery when I saw this. I am trying to get around the screen with the red triangle. Will flashing a stock recovery replace this? If not can you provide guidance on doing so after the 1.29 RUU is flashed as described in the OP?

enmriley said:
Thanks. one more question on this topic. The recovery (or screen) with the red triangle will flag a problem with Sprint right? I assumed the RUU didn't flash the stock recovery when I saw this. I am trying to get around the screen with the red triangle. Will flashing a stock recovery replace this? If not can you provide guidance on doing so after the 1.29 RUU is flashed as described in the OP?
Click to expand...
Click to collapse
What? The red triangle means you booted into recovery but something went wrong, either there's no update to flash or something like that. Are you trying to now update to 1.31 after the 1.29 RUU?
Sent from my HTCONE using xda premium

No, I went through the process defined in the OP to return to stock executing a 1.29 RUU. This seemed to work fine. I then received the OTA update to 1.31. After refusing the update several times I accepted it. I didn't go into recovery before accepting the OTA update (not sure that would matter but it would have identified the red triangle apart from the 1.31 uodate) Now when I boot to recovery I get the red triangle where I was expecting to see the stock boot menu.

so i ran the echo command and get seek 1seek64 failed am i in the clear to flash the ruu or what should i do kind of scared to move away from recovery
it worked xD thanks dude

[SOLVED] When going stock is not easy like in the guides

Hi,
i can't get to stock with the two RUU methods.
The RUU.exe file doesnt starts on both Windows 7 (64-Bit) PCs. I rightclick the exe file (4.19.401.9) and wanna start it with admin privileges. But an error is appearing.
When i want to install the ruu.zip (2.19.401.1) than it says: too many links.
I have s-off (firewater), unlocked bootloader, custom-rom (CM) and custom recovery (twrp).
I ve read that i have to lock my bootloader before i have to flash ruu.exe
But there are two ways for locking my bootloader:
fastboot oem lock
or
adb shell
su (if needed to get a # prompt)
echo -ne '\x00\x00\x00\x00' | dd of=/dev/block/mmcblk0p3 bs=1 seek=33796
(i would very strongly recomend you copy/paste this)
exit
(exit a second time if you need to to get back to a normal > prompt)
adb reboot bootloader
Which one of both should i do? But when my exe file doesnt starts i think i dont have to do it and i just should try the zip method. What are the requirements for ruu.zip? Oh, and is it important that the ruuzip file should have the original name? i renamed it to ruu.zip
Here are my links which i have used:
http://forum.xda-developers.com/showthread.php?t=2358738
http://forum.xda-developers.com/showthread.php?t=2475914
*EDIT*
Maybe you should know what i want to do. I just want an device without Tampered.

I got the same error because my anti virus aborted the download so I downloaded only the half ruu.exe :/
Gesendet von meinem HTC One mit Tapatalk

If all you want to do is remove tampered there are a million different guides. You don't need to run a ruu. Google it
Sent from my GT-I9305 using xda app-developers app

i have to add something: i just want my htc one like the day i unpacked it. stock rom, locked and no tampered because i want my device itself to update OTAs. I dont want to do it manually anymore. I just want full HTC One stock.
And have no antivirus software on my PCs. Dont need it. The problem sits in front of the PC in the most cases i think. But i try to check the hash sum first.
*EDIT*
I have installed the latest stock ROM from here now just as a compromise solution until i can go 100% stock.

If you can't get a ruu to install. If you flash the stock recovery if you can find it for the version you are on you can accept otas
Sent from my GT-I9305 using xda app-developers app

nateboi81 said:
If you can't get a ruu to install. If you flash the stock recovery if you can find it for the version you are on you can accept otas
Sent from my GT-I9305 using xda app-developers app
Click to expand...
Click to collapse
I have the stock recovery too. When I flash it, I can flash ruu.zip too?

NONAME111 said:
*EDIT*
Maybe you should know what i want to do. I just want an device without Tampered.
Click to expand...
Click to collapse
if you're ok with adb commands use this: http://forum.xda-developers.com/showthread.php?t=2477792
or this tool: http://forum.xda-developers.com/showthread.php?t=2527194
I recommend running the adb commands in a custom recovery (because you'll automatically have superuser privileges)
and, obviously this is only possible with S-OFF, and I highly recommend you never go back to S-ON!!
if you do need to go back to 100% stock, you can also take a look at my guide: http://forum.xda-developers.com/showthread.php?t=2541082
(recommend you skip S-On)
if you have questions, post them in my thread along with a "fastboot getvar all" (excluding IMEI and s/n)

when trying to run ruu.exe on mine I had to downgrade my hboot (from 1.56 to 1.44) first for it to run. Once I'd downgraded the RUU ran straight away

nkk71 said:
if you're ok with adb commands use this: http://forum.xda-developers.com/showthread.php?t=2477792
or this tool: http://forum.xda-developers.com/showthread.php?t=2527194
I recommend running the adb commands in a custom recovery (because you'll automatically have superuser privileges)
and, obviously this is only possible with S-OFF, and I highly recommend you never go back to S-ON!!
if you do need to go back to 100% stock, you can also take a look at my guide: http://forum.xda-developers.com/showthread.php?t=2541082
(recommend you skip S-On)
if you have questions, post them in my thread along with a "fastboot getvar all" (excluding IMEI and s/n)
Click to expand...
Click to collapse
Thank you!
I have no stock ROM with locked bootloader, no tampered and s-on.
Now I feel "clean".
Thread can be closed!
PS: The best part is to update from my Android v4.1.2 with OTAs to Android v4.4.2! I like updating things!

NONAME111 said:
Thank you!
I have no stock ROM with locked bootloader, no tampered and s-on.
Now I feel "clean".
Thread can be closed!
PS: The best part is to update from my Android v4.1.2 with OTAs to Android v4.4.2! I like updating things!
Click to expand...
Click to collapse
no problem,
and if you could also edit the main thread title to include [SOLVED] (go to 1st post click EDIT, at the bottom of the edit window click GO ADVANCED, then you can edit the main title), thanks :good:

Restore to Stock

I have a (sprint) H/K edition M8 running 4.4.2 rooted with TWRP recovery, s-on with 1.54.654.13 & SPCS-004. I wish to return to stock to get the Lollipop update and then return to root. Im at a loss as to what to do please help any advice is appreciated.

Check out the thread in the link below. Use the RUU for the HK Lollipop update. You'll need to relock your bootloader before running the RUU. After running the RUU you'll need to unlock your bootloader and reinstall TWRP. You can then flash a ROM.
http://forum.xda-developers.com/showthread.php?t=2729173

How would i lock my bootloader without getting s-off? The only way i know of to do it is to pay for Sunshine.

AlexN18 said:
How would i lock my bootloader without getting s-off? The only way i know of to do it is to pay for Sunshine.
Click to expand...
Click to collapse
Connect your phone to your computer. Run the command fastboot oem lock. That will relock your bootloader.

My adb isnt recognizing my phone, have the stock google drivers & htc drivers installed and ive tried with my phone both powered on and in fastboot. I believe there might be a driver issue but im not really sure

AlexN18 said:
My adb isnt recognizing my phone, have the stock google drivers & htc drivers installed and ive tried with my phone both powered on and in fastboot. I believe there might be a driver issue but im not really sure
Click to expand...
Click to collapse
Try this to get the drivers sorted.

Ive already had that installed idk what could be going on

Not to hijack the thread but how do I put it back to 100% stock so I can do a warranty return? I am mostly talking about how to remove s-off. I figure I need to have it back to s-on to do the warranty return.
Sent from my HTC One m8 running ViperOne 4.3.0

Phrostbite said:
Not to hijack the thread but how do I put it back to 100% stock so I can do a warranty return? I am mostly talking about how to remove s-off. I figure I need to have it back to s-on to do the warranty return.
Sent from my HTC One m8 running ViperOne 4.3.0
Click to expand...
Click to collapse
Go here:
http://forum.xda-developers.com/showthread.php?t=2826343

Okay, fixed the driver issues, this is what happens when i attempt it both from standard command window & adb command window

AlexN18 said:
Okay, fixed the driver issues, this is what happens when i attempt it both from standard command window & adb command window
Click to expand...
Click to collapse
You have to make sure you install the drivers in recovery,bootloader, and OS
ADB = OS and recovery
Fastboot = hboot/fastbootusb.
The waiting for device might be that you are not in fastbootusb

bootloader says RELOCKED, attempting to run RUU...

successful update, thanks for the help guys. Is there any way to get my on screen buttons changed to the new shape and to root again?

AlexN18 said:
successful update, thanks for the help guys. Is there any way to get my on screen buttons changed to the new shape and to root again?
Click to expand...
Click to collapse
You can install TWRP and root just like you were on any other update. Android version does not matter. Just make sure you unlock the bootloader again, you can use the same unlock token from HTC dev. Then you want to install recovery
Code:
fasboot flash recovery recovery.img
After that, from fastboot, boot into recovery and then reboot system. If you use a newer TWRP it will prompt you to install superSU.