Alright, because there is constant stupidity regarding the bootloader security state for HTC devices. I feel that I can clarify and help remove some myths and misconceptions.
Let's start with the most important one:
What is S-off?
S-off is us turning off the security flag stored in the NV RAM of our device. This allows us to flash unsigned files (zips and images) to our device. The difference is stated below of why you need a zip vs an image.
S-off is not root either. Root is just a binary stored in /system and just doesnt get removed if the device has s-off. S-off just means integrity of file system / partitions aren't checked on the device. So this means the two are exclusive of each other from a user standpoint.
HTC IS JUST GOING TO TURN S-ON AND RUIN IT FOR EVERYBODY!
No, they aren't. For a few good reasons, one of which is their own engineers have s-off to begin with.
The @secuflag (S-on/S-off) is there to verify hboots and other various image files on the device to begin with. When we have s-off on a newer device but idiot user decides to turn s-on for whatever reason and we have a modified hboot? The device will brick because you broke its chain of trust. It thought you were friends but you slept with it's girlfriend or whatever. Now if HTC were to suddenly turn s-on, this would break chains of trust for those who used something like Moonshine with a patched hboot. It was their OTA that caused it. They are then held liable for it and they have to fix it under warranty. You know how much that costs them? Imagine giving 1000's of people new phones because you singlehandedly broke them all. Good job dude.
Not only that, they cant turn S-on by just updating images on the device. It's stored in the NV-RAM. They would need an entirely different method than just flashing through recovery.
Next point is:
S-off means you can flash whatever you want using fastboot flash.
Now because s-off processes before gave us patched hboots, we didnt know any better. This is all wrong. fastboot flash barely works on newer phones unless dev unlocked. Now that not all s-off's give a patched hboot it's good to know the following. The only way to install something with a locked bootloader but s-off, is to use flash zip. This means that you dont just "fastboot flash recovery" or boot.img. You need to create a zip with android-info.txt and whatever files your flashing. With the lock placed on devices, unless you htc dev unlock or flash a modified hboot, it wont allow you to flash because the dev unlock is a different part than what flashes the zips.
More info about patched / eng hboots:
Now that we've seen what we lose without a patched hboot, what does it add exactly? Well, a patched or engineering hboot allows you to fastboot flash pretty much every partition on the device with an unsigned image directly (such as fastboot flash hboot hboot.img or fastboot flash splash1 splash1.img) without giving you a not allowed or command error. The reason these are useful is because it saves time. I really dont want to always have to build a zip so I always use patched hboots. They also give you access to more commands as well which I can't remember off the top of my head. These are all commands mainly used by HTC engineers and software testers.
Final point that I can think of (may add more):
That green progress bar needs to be full when fastboot flashing a zip. While it's a pretty green bar and looks very useful...for whatever reason, htc has decided to make it wrongly report progress when in use. This can lead to users freaking out and just leaving their phone in RUU mode for however until someone tells them they're idiots for it. this progress bar means literally nothing and my favorite quote about it is: "Progress bar is like tits on a snake. Interesting but pointless." Ignore the progress bar. If the command line says the zip finished, just fastboot reboot or reboot-bootloader. It will help you finish whatever the heck you're trying to do.
Nice write-up I added it to the FAQ's thread Q9 Thanks
Very nice thread, thanks
+1 on that green progress bar, when I removed the red writing on the splash screen I saw the progress bar not don't but in command prompt it said finished so I said whatever and just rebooted
Sent from my HTC One using Tapatalk 2
Reminds me of a certain thread I wrote about a year ago
S-OFF explained - by a Developer
Didn't even know that existed.
Sent from my hidden jewel
Question, let's say I have s-off and flash the superuser app and all the required busybox files... Can I use root required apps like titanium backup and wireless tether?
I only ask because I've been hesitatent to root. I just don't want to Dev unlock via HTC and officially void my warranty. The sealed in battery has me extremely paranoid as its generally the first thing I've had to replace with previous HTC devices.
This leads me to the following question, if the response to the first was no... Is there a way to use root apps without using the HTC Dev tool
Please note: I'm not a developer and this was not clear to me in the write up.
You don't need s-off to root.
You do need to root to use apps that require root access.
budeone said:
You don't need s-off to root.
You do need to root to use apps that require root access.
Click to expand...
Click to collapse
You've stated the obvious...but thanks for the response!
I just want to know if we can get root without going through HTC, or if it will be possible in the near future thanks to the s-off development. It's my understanding that you do not need root to get s-off.
bnapy said:
You've stated the obvious...but thanks for the response!
I just want to know if we can get root without going through HTC, or if it will be possible in the near future thanks to the s-off development. It's my understanding that you do not need root to get s-off.
Click to expand...
Click to collapse
I found this link, may answer your question.
http://www.pocketables.com/2012/08/...nlocked-bootloader-in-the-htc-evo-series.html
As described in this thread an Android-info.txt file can be used to fastboot flash update.zip where the contents of the zip are TWRP and the .txt file.
I am S-OFF Locked on 1.31 stock
I want to flash TWRP via the method described above. (Or alternatively the superuser apk)
I have a img file of TWRP.
I need an Android-info.txt file that will work. Where is an example of this file so I can attempt this? Does anyone have a link?
Indirect said:
That green progress bar needs to be full when fastboot flashing a zip. While it's a pretty green bar and looks very useful...for whatever reason, htc has decided to make it wrongly report progress when in use. This can lead to users freaking out and just leaving their phone in RUU mode for however until someone tells them they're idiots for it. this progress bar means literally nothing and my favorite quote about it is: "Progress bar is like tits on a snake. Interesting but pointless." Ignore the progress bar. If the command line says the zip finished, just fastboot reboot or reboot-bootloader. It will help you finish whatever the heck you're trying to do.
Click to expand...
Click to collapse
I don't know about "tits on a snake," but many progress bars I've seen are both uninteresting and pointless. They do generally serve their purpose of keeping impatient/inexperienced users from hammering away at things they don't understand and inadvertently breaking them.
tws101 said:
I need an Android-info.txt file that will work. Where is an example of this file so I can attempt this? Does anyone have a link?
Click to expand...
Click to collapse
Here is the version straight from the 1.31..651.2 OTA firmware.zip. Although you may not need the "btype" or "aareport" lines. I have flashed TWRP in the past without those lines included.
tws101 said:
As described in this thread an Android-info.txt file can be used to fastboot flash update.zip where the contents of the zip are TWRP and the .txt file.
I am S-OFF Locked on 1.31 stock
I want to flash TWRP via the method described above. (Or alternatively the superuser apk)
I have a img file of TWRP.
I need an Android-info.txt file that will work. Where is an example of this file so I can attempt this? Does anyone have a link?
Click to expand...
Click to collapse
PillowMetal said:
Here is the version straight from the 1.31..651.2 OTA firmware.zip. Although you may not need the "btype" or "aareport" lines. I have flashed TWRP in the past without those lines included.
Click to expand...
Click to collapse
Another misconception about S-OFF is that you need a "valid android-info.txt" when flashing from fastboot. When you're S-OFF, the bootloader completely disregards that file. All you need is to make a zip with whatever you want flashed, and then add any android-info.txt file in there. The default one that I include in the plugin template for my Bootloader Customizer is actually completely empty and it works fine as well. As long as there is a file (irregardless of file size) in the zip named android-info.txt, you'll be able to flash it fine, just as long as you ARE S-OFF.
regaw_leinad said:
As long as there is a file (irregardless of file size) in the zip named android-info.txt, you'll be able to flash it fine, just as long as you ARE S-OFF.
Click to expand...
Click to collapse
That's good to know, and thanks for the bootloader customizer, I have been using it for years, as well as your "rebooter" which is very convenient. Glad to see you in the One forums!
regaw_leinad said:
As long as there is a file (irregardless of file size) in the zip named android-info.txt, you'll be able to flash it fine, just as long as you ARE S-OFF.
Click to expand...
Click to collapse
Just to follow up, I discovered that at least with the Sprint HTC One, you need the following three lines at a minimum when flashing from rebootRUU or you will get an error stating:
FAILED (remote: 24 parsing android-info fail)
Code:
modelid: PN0720000
cidnum: SPCS_001
mainver: 1.29.651.10
So it looks like S-OFF validation of android_info.txt has stiffened up since the EVO 4G LTE days.
PillowMetal said:
Just to follow up, I discovered that at least with the Sprint HTC One, you need the following three lines at a minimum when flashing from rebootRUU or you will get an error stating:
FAILED (remote: 24 parsing android-info fail)
Code:
modelid: PN0720000
cidnum: SPCS_001
mainver: 1.29.651.10
So it looks like S-OFF validation of android_info.txt has stiffened up since the EVO 4G LTE days.
Click to expand...
Click to collapse
Ah, you don't have a bootloader that allows fastboot flashing? That must be why. If you were flashing straight from the hboot, you don't need it. Didn't realize you guys had to use RUU mode.
regaw_leinad said:
Didn't realize you guys had to use RUU mode.
Click to expand...
Click to collapse
I would LOVE to be able to flash from hboot, it was so convenient and didn't require a computer. But alas, no SD Card on the Sprint variant, so no hboot flashing.
It has been said that we can use USB-OTG to perform the hboot flashing, but I have yet to get a known compatible and working USB drive to be recognized or even looked at when starting up the bootloader, although the drive works fine when rebooted to system or even recovery. It just doesn't search for external mounts like the old EVO 4G LTE hboot did on startup.
There's a thread for the small number of us who care and wan't to do this, but can't...
http://forum.xda-developers.com/showthread.php?t=2320252
And specifically, my experiences trying to get it to work.
http://forum.xda-developers.com/showpost.php?p=44444102&postcount=9
http://forum.xda-developers.com/showpost.php?p=44494480&postcount=11
Any insight or things you can share regarding this would be greatly appreciated.
PillowMetal said:
I would LOVE to be able to flash from hboot, it was so convenient and didn't require a computer. But alas, no SD Card on the Sprint variant, so no hboot flashing.
It has been said that we can use USB-OTG to perform the hboot flashing, but I have yet to get a known compatible and working USB drive to be recognized or even looked at when starting up the bootloader, although the drive works fine when rebooted to system or even recovery. It just doesn't search for external mounts like the old EVO 4G LTE hboot did on startup.
There's a thread for the small number of us who care and wan't to do this, but can't...
http://forum.xda-developers.com/showthread.php?t=2320252
And specifically, my experiences trying to get it to work.
http://forum.xda-developers.com/showpost.php?p=44444102&postcount=9
http://forum.xda-developers.com/showpost.php?p=44494480&postcount=11
Any insight or things you can share regarding this would be greatly appreciated.
Click to expand...
Click to collapse
You know, it might depend on the type of drive, and it might depend on the file system your drive is formatted to. I have 0 experience using USB-OTG, so I'm probably not the best one to ask unfortunately But if you do get it working, be sure to make a guide or something! Try playing around with different formatting of your drive possibly
regaw_leinad said:
You know, it might depend on the type of drive, and it might depend on the file system your drive is formatted to. I have 0 experience using USB-OTG, so I'm probably not the best one to ask unfortunately But if you do get it working, be sure to make a guide or something! Try playing around with different formatting of your drive possibly
Click to expand...
Click to collapse
Ah, never thought of trying different formatting, there are different allocation unit sizes I could use... thanks! I will definitely make a guide if I get this resolved because it is driving me crazy, so I'm sure there are others too.
Related
This tutorial will help you downgrade back to software version '1.22.605.0' this software version is based on the shipped ROM before the OTA.
1) download: http://shipped-roms.com/shipped/Inc...dio_1.00.03.04.06_release_161493_NoDriver.exe
2)Run the RUU.
NOTE: you do not need your device to extract the ROM.zip from the RUU (Radio Update Utility)
Click to expand...
Click to collapse
A. after step number 2 you will see an image like this:
3) now go to your start menu and click on RUN in the textfield type %temp% and click ok. "you should see"
4) search threw all the folders that start off something like this {D3D2296B-5E22-46DB-BEF4-D7235D4BB485} inside this folder will be another folder with many stuff inside SCROLL DOWN till you see the ROM.zip
5) just drag and drop the ROM.zip onto your desktop like so:
6) renmae the rom.zip to PB31IMG.zip place it on the root of your SDCARD and boot into your hboot (power off the device then while holding the volume down + power will boot you into hboot)
7) the device will load the PB31IMG.zip and tell you if you want to update just volume up for yes, and when prompted to reboot just volume up for yes on your device and your DONE!!!
Hope this helps anyone...!!
ID*
do you have to be connected to htc sync in order to do this or can you just download the file to your pc desktop and connect your incredible via the usb than run the file.
what is RUU exactly, if it is an application where do I download it from
slumpey326 said:
do you have to be connected to htc sync in order to do this or can you just download the file to your pc desktop and connect your incredible via the usb than run the file.
what is RUU exactly, if it is an application where do I download it from
Click to expand...
Click to collapse
you do not need htc sync to extract the rom.zip
(RUU = Radio Update Utility)
this is mainly a how to extract the images from the rom.zip inside a RUU nothing more
ZOMG WILL THIS HALP ME HAS ROOT???????????????????????
Sorry, had to. =P Thanks for the guide!
Thanks
Thanks. Worked perfectly.
When I'm in the hboot menu the phone is saying that there is either no image or its the wrong image. What gives?
You probaly renamed it as
<filename>.zip.zip
Usally Windows dont Turn ON Extension in Browsers
Nope. I know better than that.
So are devs working on rooting pre-OTA, OTA, or both (meaning whichever works best)?
EDIT: I'm just wondering if that's why we have this instruction set posted. I guess if pre-OTA is rooted everyone will want to downgrade.
I don't understand the point of this, although it may be due to the fact I'm a android noob. I went into the recovery menu (I had already applied the OTA update) and selected "clear storage". That wiped my phone and sent me back to pre OTA state. I'm pretty sure of this because the next time I turned on my phone It started bugging me about an exchange update. What's the point of going through this complicated procedure?
i really dont understand the point of this????
suzook said:
i really dont understand the point of this????
Click to expand...
Click to collapse
Title says it all... if a hack for root is found in the updated bootloader everyone who wants root will be able to downgrade to be able to apply the hack is pretty much all this is for
suzook said:
i really dont understand the point of this????
Click to expand...
Click to collapse
Some of us are seeing the 1x for network speed a lot more, or for the first time after the update. This would revert us back to not seeing 1x.
But why do all of this when clear storage does the same thing with less hassle
psmafia said:
But why do all of this when clear storage does the same thing with less hassle
Click to expand...
Click to collapse
I don't think clear storage takes you back to pre-OTA... you have to do that manually, im sure.
RLKirk said:
I don't think clear storage takes you back to pre-OTA... you have to do that manually, im sure.
Click to expand...
Click to collapse
Definitely not. If you want to go to pre-OTA you need to follow this method.
If clear storage got me to pre-OTA i wouldn't still be fighting with this.
Seriously does anyone have any insight into why the heck this isn't working for me?
It's saying:
SD Checking....
Loading [pb31diag.zip]
no image!
Loading [pb31diag.nbl]
no image or wrong image!
Loading [pb31img.zip]
no image!
Loading [pb31img.nbl]
no image or wrong image!
then kicks me back to the hboot screen.
I'd really like to get my reliable 3g back.
Someone posted another one of these files, one with HBOOT .79 I believe. If you update hboot, then you can't downgrade then right?
TNS201 said:
Someone posted another one of these files, one with HBOOT .79 I believe. If you update hboot, then you can't downgrade then right?
Click to expand...
Click to collapse
False. HBOOT .77 and .79 are 'inter-flashable'. It goes both ways.
Well both ROM.zip have different Version details so i suspect that Downgrading from 0.79 to 0.77 SPL is Possible
0.77
ModelID: PB3120000
CIDNUM: VZW__001
MainVer: 1.22.605.0
HbootPreUpdate: 11
0.79
ModelID: PB3120000
CIDNUM: VZW__001
MainVer: 1.22.605.2
HbootPreUpdate: 13
Hello all. First off, great resource here :cyclops:
I am currently trying to update my HTC One (AT&T) so that I can run the 4.3 Google Play Rom (it sticks on boot screen at the moment)
After that I tried to update firmware as seen here http://forum.xda-developers.com/showthread.php?t=2182823
(I am using model PN0712000 and CID CWS__001)
I have downloaded the appropriate file and followed the instructions but get stuck after step 6 "Type: fastboot oem rebootRUU and wait for device to reboot"
When I type the reboot command it boots to a black screen that just says "HTC" and sticks there. And I try to load the firmware it says "cannot load firmware.zip unknown error"
For reference the device is currently running a 4.2.2 rom (ends TBalden) if that matters
Any thoughts?
Thanks!
S-OFF? Unless you have a legit GE one, you'll have to be s-off to do it.
If you are, you'll need to delete the zip you are trying to flash in fastboot, reboot comp and try a fresh download.
Also id personally say run the command
fastboot oem writecid 11111111
after you have s-off
EDIT: failed to see that you are att... You'll only be able to ruu to the Cingular ruu without s-off. I can't tell which stock firmware you linked as it brought me to some random post in that thread lol
Sent from my One using Tapatalk 2
InflatedTitan said:
S-OFF? Unless you have a legit GE one, you'll have to be s-off to do it.
If you are, you'll need to delete the zip you are trying to flash in fastboot, reboot comp and try a fresh download.
Also id personally say run the command
fastboot oem writecid 11111111
after you have s-off
Sent from my One using Tapatalk 2
Click to expand...
Click to collapse
Oh I missed that detail. S-On at the moment. Based upon my limited tenure with rooting and my understanding of the potential flops in S-OFF I will probably stay away from anything that requires that (for the time being at least).
Is there some reason that I can install the 4.2.2 Rom but this 4.3 and Bigxie 4.3 both fail? Do they require firmware change? Something else I'm missing? The installer for this ROM is pretty self explanatory. And I am wiping before hand (both in the ROM install and in TWRP).
Same result every time though (never ending HTC screen)
Thanks again
Not sure why it won't boot. There should be no extra steps with this phone such as flashing separate boot.img....
Other ROMs flash fine?
S-off does have it warnings and potentials... But the revone s-off method carries and extreemmmeelllyy small chance of being fatal to your phone. I'd usually try to talk someone out of modding if you're not comfortable with it. But revone is a couple adb commands that are pretty newb friendly
Sent from my One using Tapatalk 2
InflatedTitan said:
Not sure why it won't boot. There should be no extra steps with this phone such as flashing separate boot.img....
Other ROMs flash fine?
S-off does have it warnings and potentials... But the revone s-off method carries and extreemmmeelllyy small chance of being fatal to your phone. I'd usually try to talk someone out of modding if you're not comfortable with it. But revone is a couple adb commands that are pretty newb friendly
Sent from my One using Tapatalk 2
Click to expand...
Click to collapse
Well I'm 1 for 3 as outlined above. The bigxie_m7_GPe_odexed_tbalden 4.2.2 works fine. The two 4.3 roms do not work... including ARHD and bigxie_m7_GPe_JWR66V_odexed-signed.
Is there an easy way to just "go back to stock" and then try again? The back to stock tutorials all seem a good bit involved.
Edit: Bigxie 4.3 just worked...maybe I'll just stick with that presuming there are no big issues with it?
Are there any big reasons to update the radio? If so can I do after ROM load?
Thanks for all your help btw.
Still wondering why this particular rom won't load. Any other takers? Bigxie still running at the moment.
I bet mike1986. knows!
Folks,
I am not sure if someone has faced similar issue, as I went through lot of forums and couldnt find anything which helped me to fix it.
I have my HTC One with AT7T which is not rooted and tried to udpate RUU using computer which is available latest at HTC downloads site.
Unfortunately, it didnt update my Android but I am left with Black sceeen which comes up after this message.
*** LOCKED ***
M7_UL PVT SHIP S-ON RH
HBOOT-1.44.0000
RADIO-4A.13.3231.20
OpenDSP-v26.120.274.0202
eMMC-boot
RUU
Need urgent help on this, Fortunately I have my data backed up but I need my phone recovered.
sameermis said:
Folks,
I am not sure if someone has faced similar issue, as I went through lot of forums and couldnt find anything which helped me to fix it.
I have my HTC One with AT7T which is not rooted and tried to udpate RUU using computer which is available latest at HTC downloads site.
Unfortunately, it didnt update my Android but I am left with Black sceeen which comes up after this message.
*** LOCKED ***
M7_UL PVT SHIP S-ON RH
HBOOT-1.44.0000
RADIO-4A.13.3231.20
OpenDSP-v26.120.274.0202
eMMC-boot
RUU
Need urgent help on this, Fortunately I have my data backed up but I need my phone recovered.
Click to expand...
Click to collapse
There are a few things you can do:
1. Press and hold your power button for ten more more seconds until it restarts. If it boots into android, you need to do a few things before you try and flash again. You need to S-off and unlock your bootloader. To accomplish this, see here to S-off, and here to unlock your bootloader. You need to S-off first. Of course, if these methods seem like too much, you can always use this all in one toolkit to accomplish everything you need. Remember to S-off, then unlock the bootloader. After that, re-try the update again.
2. Make sure the zip of what you're flashing supports your MID (Model ID) and CID. You can find this in the Android-info.txt file of the zip you're trying to flash. If your specs are not there, add them in. You're model id will be PN07***** and your CID will look like HTC__001, etc. Add them in just as the others in that file look like. Save it, and then try to flash it again. In order for this to work, you most likely need to be unlocked and S-off, so follow the methods above to accomplish that and try this again if it didn't work without it.
3. If you're using the RUU.exe, then you need to make sure your firmware and recovery are stock before trying to flash the rom, or you could run into issues during the flash (i.e. the RUU fail screen you described). For this, you will need to search here for your native files. I suggest looking here for a copy of your stock rom. Once you have that, extract the stock recovery img from the zip and flash that to your phone. For firmware, I suggest looking here as a starting point. He has many downloads of different firmware available, and at the very least, you can find the right one you need and then search for it here. Once you have it, flash it, and then re-try running the RUU.exe again. Hopefully it will get through the process.
I hope these methods provide at least some help or get you on the way to recovery If you have any questions, please let me know.
-Mike
kibmikey1 said:
There are a few things you can do:
1. Press and hold your power button for ten more more seconds until it restarts. If it boots into android, you need to do a few things before you try and flash again. You need to S-off and unlock your bootloader. To accomplish this, see here to S-off, and here to unlock your bootloader. You need to S-off first. Of course, if these methods seem like too much, you can always use this all in one toolkit to accomplish everything you need. Remember to S-off, then unlock the bootloader. After that, re-try the update again.
2. Make sure the zip of what you're flashing supports your MID (Model ID) and CID. You can find this in the Android-info.txt file of the zip you're trying to flash. If your specs are not there, add them in. You're model id will be PN07***** and your CID will look like HTC__001, etc. Add them in just as the others in that file look like. Save it, and then try to flash it again. In order for this to work, you most likely need to be unlocked and S-off, so follow the methods above to accomplish that and try this again if it didn't work without it.
3. If you're using the RUU.exe, then you need to make sure your firmware and recovery are stock before trying to flash the rom, or you could run into issues during the flash (i.e. the RUU fail screen you described). For this, you will need to search here for your native files. I suggest looking here for a copy of your stock rom. Once you have that, extract the stock recovery img from the zip and flash that to your phone. For firmware, I suggest looking here as a starting point. He has many downloads of different firmware available, and at the very least, you can find the right one you need and then search for it here. Once you have it, flash it, and then re-try running the RUU.exe again. Hopefully it will get through the process.
I hope these methods provide at least some help or get you on the way to recovery If you have any questions, please let me know.
-Mike
Click to expand...
Click to collapse
Thanks Mike, I tried your Step 1, all it does it comes to a black screen with 4 triangles at the top.
sameermis said:
Thanks Mike, I tried your Step 1, all it does it comes to a black screen with 4 triangles at the top.
Click to expand...
Click to collapse
What exactly are you trying to flash? Are you using a zip or the exe? It sounds like you're stuck in the middle of a flash, and the basic idea is you need to finish it. Can you get to any other area of the phone? Bootloader? Recovery?
Edit: since your model is an att version, you should be able to run the RUU.exe and reflash stock. I'm going to list the instructions on how to do this, hope it works. This is a pretty simple method that will, unfortunately, wipe your phone, but will get it going again. Here goes:
You need: The Android SDK. Install it, get any updates for it too. You also need the RUU exe file from HTCdev.com. To get this, once on HTCDev, go to kernel source codes, then click see downloads above it. From there, filter by: One, blank, blank, v4.3. That will bring up the RUU exe you want. It's the first one. Download it. Now comes the steps to follow.
1. If you can, restart the phone by holding down power and the vol. down button. You should now be at a white screen, which is your bootloader. Let it be.
2. Now, with your phone connected to your pc, your going to run a series of commands through adb and fastboot to start.
3. Go to the folder that contains the sdk files you downloaded. It should be something like adt-bundle-windows. In that folder, go to sdk, then platform-tools. On the platform-tools folder, hold down shift and right click. Open a command prompt when the menu comes up.
4. Now, your command window should read C:\whatever\thisis\foryou\adt-bundle-windows\sdk\platform-tools>.
5. The first command is getting you to a clean RUU mode. So, type: fastboot oem rebootRUU
this will restart your phone into RUU mode. It should be a silver HTC logo. That's it for the commands!
6. Now, open the RUU.exe, and run through the steps. It's fairly easy from here. Just let it run, and if all works correctly, it will restart the phone into Android, and you will have a fresh, working copy of 4.3 on your phone.
Let me know if you need any clarification, or if anything goes wrong. Hope we get it this time.
-Mike
Hello Everyone,
I have a question,
Does anyone know if it is possible to create a flashable zip for HBOOTs, to flash via recovery, if you are S-OFF. I understand that it can be done via fastboot, but I would like to know if it can be done via recovery. If so, can you please enlighten me? Thanks.
troby86 said:
Does anyone know if it is possible to create a flashable zip for HBOOTs, to flash via recovery, if you are S-OFF. I understand that it can be done via fastboot, but I would like to know if it can be done via recovery. If so, can you please enlighten me? Thanks.
Click to expand...
Click to collapse
IF this is possible, it's very dangerous because it bypasses the normal checks that the bootloader does before installing a recovery (and obviously would require S-Off). But the way a flashable .zip works is that it has files, and a script that installs the files. You could (probably) write a script that checks the phone model, then writes an image file to the partition where HBOOT lives. Why do you want to do this?
fenstre said:
IF this is possible, it's very dangerous because it bypasses the normal checks that the bootloader does before installing a recovery (and obviously would require S-Off). But the way a flashable .zip works is that it has files, and a script that installs the files. You could (probably) write a script that checks the phone model, then writes an image file to the partition where HBOOT lives. Why do you want to do this?
Click to expand...
Click to collapse
The only reason I wanted to try this, is because I flashed HBOOT 1.44 to my phone, and ADB and FASTBOOT does not work with that HBOOT and Windows 8.1 combined, and all the computers in my house are on Windows 8.1. However, I used a live Linux USB and flashed back 1.56 HBOOT, so all is good now.
troby86 said:
The only reason I wanted to try this, is because I flashed HBOOT 1.44 to my phone, and ADB and FASTBOOT does not work with that HBOOT and Windows 8.1 combined, and all the computers in my house are on Windows 8.1. However, I used a live Linux USB and flashed back 1.56 HBOOT, so all is good now.
Click to expand...
Click to collapse
Good to know. That's much smarter. (Note: the flash-within-recovery solution makes me especially nervous because I've tried to flash the wrong OS for my phone 2-3 times. The built-in safeguards have always saved me.)
Hi guys
Basically I need to send my device into HTC for repair. It is S-OFF and I have a stock HTC European _001 rom on it. I really really need to restore to the UK O2_001 stock rom and get back to S-ON to avoid any possible issues with the warranty.
The problem is I can't find any O2 UK zips or nandroid backups to flash. For some reason the RUU files do not work for me, and I really don't have the time to be troubleshooting this.
I would really appreciate it if someone could upload a nandroid backup that I can use very soon? Otherwise I'll need to stick with the unbranded HTC Europe rom and risk them knowing I've unlocked the device.
Thanks for any help.
fade2black101 said:
Hi guys
Basically I need to send my device into HTC for repair. It is S-OFF and I have a stock HTC European _001 rom on it. I really really need to restore to the UK O2_001 stock rom and get back to S-ON to avoid any possible issues with the warranty.
The problem is I can't find any O2 UK zips or nandroid backups to flash. For some reason the RUU files do not work for me, and I really don't have the time to be troubleshooting this.
I would really appreciate it if someone could upload a nandroid backup that I can use very soon? Otherwise I'll need to stick with the unbranded HTC Europe rom and risk them knowing I've unlocked the device.
Thanks for any help.
Click to expand...
Click to collapse
if you want to follow my guide http://forum.xda-developers.com/showthread.php?t=2541082
Files you'll need are in post #7 under "HTC One M7_UL - modelid=PN0710000 - cidlist=O2___001,O2___102"
EDIT: there's also this RUU http://androidruu.com/getdownload.p...8_10.38r.1157.04L_release_353143_signed_2.exe
but as mentioned in my guide, i don't encourage going s-off to s-on on newer firmware
nkk71 said:
if you want to follow my guide http://forum.xda-developers.com/showthread.php?t=2541082
Files you'll need are in post #7 under "HTC One M7_UL - modelid=PN0710000 - cidlist=O2___001,O2___102"
EDIT: there's also this RUU http://androidruu.com/getdownload.p...8_10.38r.1157.04L_release_353143_signed_2.exe
but as mentioned in my guide, i don't encourage going s-off to s-on on newer firmware
Click to expand...
Click to collapse
Hello, thanks for that
Unfortunately I can't seem to downgrade the bootloader. I'm on 1.61.
Not entirely sure what to do now.. Will it be possible to achieve S-ON again and lock the bootloader without downgrading the hboot?
I don't really have time to spend ages on this, as the phone will be getting collected on Friday and I'm busy with work. I also don't really have time to troubleshoot the 100000 reasons why RUU.exe files aren't working for me and why I can't downgrade the bootloader. May just have to send it in unlocked and hope for the best.
fade2black101 said:
Hello, thanks for that
Unfortunately I can't seem to downgrade the bootloader. I'm on 1.61.
Not entirely sure what to do now.. Will it be possible to achieve S-ON again and lock the bootloader without downgrading the hboot?
I don't really have time to spend ages on this, as the phone will be getting collected on Friday and I'm busy with work. I also don't really have time to troubleshoot the 100000 reasons why RUU.exe files aren't working for me and why I can't downgrade the bootloader. May just have to send it in unlocked and hope for the best.
Click to expand...
Click to collapse
so quick and dirty? (and hope for the best)... did you use sunshine to s-off? before i post the steps.
haha
And yes I did. And I plan to use it again when I get phone back. Let me know your suggestion and I'll give it a go when I have some time
fade2black101 said:
haha
And yes I did. And I plan to use it again when I get phone back. Let me know your suggestion and I'll give it a go when I have some time
Click to expand...
Click to collapse
okay cool, i only asked because sunshine will work again (without needing to pay again), in case that infamous "tamper detected - rebooting" happens (shouldnt in your case but just in case it does)
gimme a few minutes, and i'll post instructions with links....
Thanks
I will check this out tomorrow when I have some time
fade2black101 said:
Thanks
I will check this out tomorrow when I have some time
Click to expand...
Click to collapse
okay, should be easy enough:
1) download Guru_Bootloader_Reset_1.0.zip and put it on your virtual storage
2) download 4.19.401.9-TWRP2633_combined_nowipe.zip
if need be change cid to a compatible one:
Code:
fastboot oem writecid HTC__001
fastboot reboot-bootloader
flash firmware
Code:
fastboot oem rebootRUU
fastboot flash zip 4.19.401.9-TWRP2633_combined_nowipe.zip
fastboot flash zip 4.19.401.9-TWRP2633_combined_nowipe.zip
fastboot reboot-bootloader
set back O2 UK cid:
Code:
fastboot oem writecid O2___001
fastboot reboot-bootloader
3) go to RECOVERY (it should be TWRP 2.6.3.3 from the file above) and run the Bootloader Reset
--> remove TAMPERED
--> set LOCKED
4) go back to bootloader, and check it says LOCKED, and no more TAMPERED
5) download RUU_4.20.206.16.EXE
and run it
(if it "exits" for some unknown reason, make sure you have this installed vcredist)
6) reboot the phone to make sure it boots up fine, do not take OTA updates
7) if you really insist, go s-on
Code:
fastboot oem writesecureflag 3
8) reboot three times (do not take any OTAs, especially above 6.xx), and make sure no TAMPERED is triggered
nkk71
You're a star! Thank you so much for that. After hours spent fumbling about I spent 20 minutes following your instructions today and everything worked perfectly. The Visual C++ file you suggested did the trick too, even after I installed several other (wrong ones) yesterday. Really happy this is finally sorted
Just a quick question. I haven't gone back to S-ON yet. I think it may not be neccessary for the warranty, but maybe I shouldn't risk it as I can always just gain S-OFF again via Sunshine once I get the phone back (unless they inexplicably change the motherboard). I'm wondering if there is a high risk of bricking my device if I run that S-ON command?
Cheers once again!
fade2black101 said:
nkk71
You're a star! Thank you so much for that. After hours spent fumbling about I spent 20 minutes following your instructions today and everything worked perfectly. The Visual C++ file you suggested did the trick too, even after I installed several other (wrong ones) yesterday. Really happy this is finally sorted
Just a quick question. I haven't gone back to S-ON yet. I think it may not be neccessary for the warranty, but maybe I shouldn't risk it as I can always just gain S-OFF again via Sunshine once I get the phone back (unless they inexplicably change the motherboard). I'm wondering if there is a high risk of bricking my device if I run that S-ON command?
Cheers once again!
Click to expand...
Click to collapse
there's no risk in bricking using that "fastboot oem writesecureflag 3" command to set s-on; the RUU would have set everything back to stock; if in the unlikely event the "TAMPERED" comes back, you'll need to s-off again, and use my guide with the 1.xx RUU + nandroid method
as for sending it in S-OFF, it's really country/carrier/service centre/person specific.... from what i've seen UK is one of the most tolerant countries (some people have even sent the phone in with tamperd and running a custom rom, and still got the camera fixed)
but it's your call, i cant really say for sure how they would react.
and if all is good now, could you 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 and good luck