[Q] HTC One Android Update || Black Screen with triangles - Need urgent help - One (M7) Q&A, Help & Troubleshooting

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

Related

Fixing some misconceptions about S-off

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.

Restoring HTC ONE to Stock (Vodafone UK)

I've currently got Android Revolution HD 12.1 installed, however I need to return the phone to Vodafone UK Stock, due to returning the phone.
I found this link, which seems to give instructions on restoring the HTC ONE, however apart from downloading the OTA_M7_UL_JB_50_Vodafone_UK.......zip file from here, I'm really not sure which method to follow.
This is the information I have from the Software Information on my phone:
Android version: 4.2.2
Kernel version: 3.4.10-g445d072
Baseband version: 4A.14.3250.13_10.33.1150.01L
Build number: 2.24.401.1.CL211355
I would really appreciate some assistance
robot1000 said:
I've currently got Android Revolution HD 12.1 installed, however I need to return the phone to Vodafone UK Stock, due to returning the phone.
I found this link, which seems to give instructions on restoring the HTC ONE, however apart from downloading the OTA_M7_UL_JB_50_Vodafone_UK.......zip file from here, I'm really not sure which method to follow.
This is the information I have from the Software Information on my phone:
Android version: 4.2.2
Kernel version: 3.4.10-g445d072
Baseband version: 4A.14.3250.13_10.33.1150.01L
Build number: 2.24.401.1.CL211355
I would really appreciate some assistance
Click to expand...
Click to collapse
Here is a link to all RUU`s, zips and CWM/TWRP recovery rom`s http://forum.xda-developers.com/showthread.php?t=2207874. You`ll need S-Off however to downgrade the Hboot. If you`re not S-Off you cannot Flasha RUU with a older Hboot. Guess you`re on HBoot 1.54.000 now. Till the revone devs find a way to modify the S-Off exploit you`re stuck, link http://forum.xda-developers.com/showthread.php?t=2314582.
gee2012 said:
Here is a link to all RUU`s, zips and CWM/TWRP recovery rom`s http://forum.xda-developers.com/showthread.php?t=2207874. You`ll need S-Off however to downgrade the Hboot. If you`re not S-Off you cannot Flasha RUU with a older Hboot. Guess you`re on HBoot 1.54.000 now. Till the revone devs find a way to modify the S-Off exploit you`re stuck, link http://forum.xda-developers.com/showthread.php?t=2314582.
Click to expand...
Click to collapse
Thanks for responding
I've already downloaded the OTA's: Vodafone UK file from that link, however I'm really not sure what I should be doing with it
Edit
Just curious, if my phone is S-ON, how have I been able to install a custom ROM and recovery?
robot1000 said:
Thanks for responding
I've already downloaded the OTA's: Vodafone UK file from that link, however I'm really not sure what I should be doing with it
Edit
Just curious, if my phone is S-ON, how have I been able to install a custom ROM and recovery?
Click to expand...
Click to collapse
If the bootloader is unlocked but you`re S-On you can flash a custom recovery and roms, you however cannot downgrade or flash a newer Hboot afaik. You can`t do anything with the OTA atm, not even flash a Vodafone CWM recovery i`am afraid.
gee2012 said:
If the bootloader is unlocked but you`re S-On you can flash a custom recovery and roms, you however cannot downgrade or flash a newer Hboot afaik.
Click to expand...
Click to collapse
With regards to the Vodafone zip file, is it possible to flash that somehow and give the impression that's in factory state?
robot1000 said:
With regards to the Vodafone zip file, is it possible to flash that somehow and give the impression that's in factory state?
Click to expand...
Click to collapse
No mate, you don`t have a Vodafone rom, you have a custom recovery and you would need to lock the bootloader. It is not possible atm, stick with the rom you`re on for now and do not lock bootloader. Wait for revone to modify the bootloader xploit to get S-Off.
gee2012 said:
No mate, you don`t have a Vodafone rom, you have a custom recovery and you would need to lock the bootloader. It is not possible atm, stick with the rom you`re on for now and do not lock bootloader. Wait for revone to modify the bootloader xploit to get S-Off.
Click to expand...
Click to collapse
I've just gone into Bootloader and it's showing Hboot as 1.44.0000 !!
Would you mind giving me a brief outline on what I should be doing to get my phone back to vodafone stock?y
Many Thanks
Would flashing the Vodafone OTA zip file in recovery be safe or do I need to S-Off the device?
Please can someone advise
Thanks
Wow, you have quite the adventure in front of you my friend if you want to return your phone to a pure stock state. I'll outline the steps and you can do some work and find the guides to complete them. Assuming you're on hboot 1.44 you'll need to go ahead and s-off, you can then remove the tampered flag. After you're s-off you're then going to need to double check you're using a stock unmodified hboot (you should be) and flash the pertinent RUU based on your phone - there are plenty of guides on how to select this. You'll then need to s-on again, google the command "fastboot oem writesecureflag 3" to find some information on how to do that.
Basically you've got your work cut out mate, sorry I can't be more help but the process I've mentioned aren't as simple or as safe as unlocking the bootloader. You'll need to put some effort and most importantly care as any one of them can brick your phone. Once you're s-off you've opened up very sensitive partitions which if changed or written to wrongly can instantly brick your phone. As such I'd do a lot of research before you undertake any of these steps, this is just off the top of my head to give you some guidance so I'd also check them, you really can't be too careful when playing around with £500 worth of tech. Good luck!
postfatal said:
Wow, you have quite the adventure in front of you my friend if you want to return your phone to a pure stock state. I'll outline the steps and you can do some work and find the guides to complete them. Assuming you're on hboot 1.44 you'll need to go ahead and s-off, you can then remove the tampered flag. After you're s-off you're then going to need to double check you're using a stock unmodified hboot (you should be) and flash the pertinent RUU based on your phone - there are plenty of guides on how to select this. You'll then need to s-on again, google the command "fastboot oem writesecureflag 3" to find some information on how to do that.
Basically you've got your work cut out mate, sorry I can't be more help but the process I've mentioned aren't as simple or as safe as unlocking the bootloader. You'll need to put some effort and most importantly care as any one of them can brick your phone. Once you're s-off you've opened up very sensitive partitions which if changed or written to wrongly can instantly brick your phone. As such I'd do a lot of research before you undertake any of these steps, this is just off the top of my head to give you some guidance so I'd also check them, you really can't be too careful when playing around with £500 worth of tech. Good luck!
Click to expand...
Click to collapse
Thanks for you response
I'm now S-Off, however what I can't get my head around is the RUU part. The Vodafone ROM that I require seems to be an OTA zip update, however I'm unsure on how to flash this as it doesn't seem to be RUU
robot1000 said:
Thanks for you response
I'm now S-Off, however what I can't get my head around is the RUU part. The Vodafone ROM that I require seems to be an OTA zip update, however I'm unsure on how to flash this as it doesn't seem to be RUU
Click to expand...
Click to collapse
You cannot do it with an OTA zip... you need a full RUU but unfortunately there doesn't seem to be one available for Vodafone UK.
This one seems to be the closest one for you.... it's stock HTC Europe. I don't think at this time that returning to stock Vodafone is a possibility.
If you're sending it back for repair or replacement you could take a chance on sending it as it is.
postfatal said:
Wow, you have quite the adventure in front of you my friend if you want to return your phone to a pure stock state. I'll outline the steps and you can do some work and find the guides to complete them. Assuming you're on hboot 1.44 you'll need to go ahead and s-off, you can then remove the tampered flag. After you're s-off you're then going to need to double check you're using a stock unmodified hboot (you should be) and flash the pertinent RUU based on your phone - there are plenty of guides on how to select this. You'll then need to s-on again, google the command "fastboot oem writesecureflag 3" to find some information on how to do that.
Basically you've got your work cut out mate, sorry I can't be more help but the process I've mentioned aren't as simple or as safe as unlocking the bootloader. You'll need to put some effort and most importantly care as any one of them can brick your phone. Once you're s-off you've opened up very sensitive partitions which if changed or written to wrongly can instantly brick your phone. As such I'd do a lot of research before you undertake any of these steps, this is just off the top of my head to give you some guidance so I'd also check them, you really can't be too careful when playing around with £500 worth of tech. Good luck!
Click to expand...
Click to collapse
rider5512 said:
You cannot do it with an OTA zip... you need a full RUU but unfortunately there doesn't seem to be one available for Vodafone UK.
This one seems to be the closest one for you.... it's stock HTC Europe. I don't think at this time that returning to stock Vodafone is a possibility.
If you're sending it back for repair or replacement you could take a chance on sending it as it is.
Click to expand...
Click to collapse
Thank you for replying.
I've run that RUU from the link you provided and it stated that it's updating from 1.29.161.11 to 1.28.401.7, however an Error [131] message appeared stating 'Customer ID Error'.
Any ideas?
robot1000 said:
Thank you for replying.
I've run that RUU from the link you provided and it stated that it's updating from 1.29.161.11 to 1.28.401.7, however an Error [131] message appeared stating 'Customer ID Error'.
Any ideas?
Click to expand...
Click to collapse
Ok... you need to change that ID in the phone.
Reboot the phone to bootloader then fastboot and connect to pc then from your ADB directory on PC issue the command "fastboot oem writecid HTC__001" this will then give you the right ID for the RUU.
Note it's HTC__001.... 2 underscores !

[Solved]how to unroot and relock htc one devise in Mac and use full stock rom

Guys pls help, I need to unroot and relock my HTC One device for repair purposes.. I want to send it back to HTC Service Center and claim back the warranty to fix the camera problem. Thanks alot
[SOLVED]
Fully stock and downgraded to H-Boot 1.44 Android 4.1.2
Thanks to @nkk71
mctodd said:
Guys pls help, I need to unroot and relock my HTC One device for repair purposes.. I want to send it back to HTC Service Center and claim back the warranty to fix the camera problem. Thanks alot
Click to expand...
Click to collapse
Their are guides and even Youtube videos that give you step by step directions on how to accomplish this. Just check the threads and or Youtube
blakphoenix said:
Their are guides and even Youtube videos that give you step by step directions on how to accomplish this. Just check the threads and or Youtube
Click to expand...
Click to collapse
Thanks for the reply, but mostly in youtube where out of date..
mctodd said:
Thanks for the reply, but mostly in youtube where out of date..
Click to expand...
Click to collapse
mctodd said:
Hi nkk71, I know it's a bit annoying to have someone bothering you but seems like your the one the good guys that can patiently help some one frustrated on going back to stock (like brand new). I am having a problem on going back to stock. Here is my spec on Bootloader mode.
M7_U Htc One model
Hboot-1.54.0000
Radio-4A.17.3250.14
OpebDSP-v31.120.272.0617
OS-2.24.707.3
EMMC-boot
HTC_044
One of my problem also is i rooted it with mac and there is no unrooting instructions for mac.. Pls help if you have any idea, i just have to send it back to repair. Thanks.
P. S i am willing to pay via paypal if necessary
Click to expand...
Click to collapse
can you post a "fastboot getvar all" (and remove IMEI and s/n before posting)
Also what ROM are you on now?
EDIT: payment will not be necessary, all I ask is if I helped you hit the thanks button
nkk71 said:
can you post a "fastboot getvar all" (and remove IMEI and s/n before posting)
Also what ROM are you on now?
EDIT: payment will not be necessary, all I ask is if I helped you hit the thanks button
Click to expand...
Click to collapse
I am not in my computer at the moment cuz im at work im just using my One, the Rom that i am using at the moment is Android Revolution HD 13.1. Is it ok to fastboot through fx app so i can send you the info..
mctodd said:
I am not in my computer at the moment cuz im at work im just using my One, the Rom that i am using at the moment is Android Revolution HD 13.1. Is it ok to fastboot through fx app so i can send you the info..
Click to expand...
Click to collapse
No worries, do it later, as I'm not on s computer either for the time being. I'll be on again later, but only for an hour or two, so it might have to wait till tomorrow anyway.
Sent from my HTC One using Tapatalk
This your firmware ? 2.24.707.3
Do you have a nandroid backup of it ?
What does it say on your bootloader ?
also, on a mac you will need to type the following before any command:
./
so ./adb devices
./fastboot devices
mctodd said:
I am not in my computer at the moment cuz im at work im just using my One, the Rom that i am using at the moment is Android Revolution HD 13.1. Is it ok to fastboot through fx app so i can send you the info..
Click to expand...
Click to collapse
Well this is going to be a bit of good news / bad news.
Good news, there's a full RUU exe for you:
http://www.htc1guru.com/dld/ruu_m7_..._10-30-1131-05_release_309365_signed_2_4-exe/
Bad news it's a Windows executable, so you'll need to run that from a Windows PC. This will however allow you to go 100% stock!!!!
BUT, BEFORE THAT, there are some prerequisites. I'll outline the steps:
1- You need to get S-Off. since you're on 1.54 you need to use rumrunner.us method (which is either Windows or Linux, I think). This would involve a stock ROM as well, I don't know if ARHD 13.1 will do or not. It's something you have to check on the rumrunner thread. I havent looked into it much, so you're going to need help from someone else and/or do some reading into this.
2- Once S-Off, you need to remove the TAMPERED sign: http://forum.xda-developers.com/showthread.php?t=2477792
3- While still on S-Off, you need to "LOCKED" your bootloader (not "RELOCKED"): http://forum.xda-developers.com/showthread.php?t=2475914
4- Finally run the above RUU, because you are S-Off it WILL allow you to downgrade. Since it's a full RUU it should put your phone completely back to stock (and not even break the touchscreen drivers, the way nandroid backups do).
EDIT: and it will update everything to stock: hboot, recovery, ROM, etc. so no need to mess with all that, unlike most users
IMHO, keep S-Off, as some phones do ship S-Off. The only dead giveaways that you "messed" with your phone, are the TAMPERED, RELOCKED, and red text at boot-up.
However if you are more comfortable with S-On ("fastboot oem writesecureflag 3") ONLY do so after you are completely satisfied that everything is back to stock.
So it looks like you're going to need a Windows PC, but other than that, you can go back to fully 100% stock "relatively" easily compared to what many have and are going through.
nkk71 said:
Well this is going to be a bit of good news / bad news.
Good news, there's a full RUU exe for you:
http://www.htc1guru.com/dld/ruu_m7_..._10-30-1131-05_release_309365_signed_2_4-exe/
Bad news it's a Windows executable, so you'll need to run that from a Windows PC. This will however allow you to go 100% stock!!!!
BUT, BEFORE THAT, there are some prerequisites. I'll outline the steps:
1- You need to get S-Off. since you're on 1.54 you need to use rumrunner.us method (which is either Windows or Linux, I think). This would involve a stock ROM as well, I don't know if ARHD 13.1 will do or not. It's something you have to check on the rumrunner thread. I havent looked into it much, so you're going to need help from someone else and/or do some reading into this.
2- Once S-Off, you need to remove the TAMPERED sign: http://forum.xda-developers.com/showthread.php?t=2477792
3- While still on S-Off, you need to "LOCKED" your bootloader (not "RELOCKED"): http://forum.xda-developers.com/showthread.php?t=2475914
4- Finally run the above RUU, because you are S-Off it WILL allow you to downgrade. Since it's a full RUU it should put your phone completely back to stock (and not even break the touchscreen drivers, the way nandroid backups do).
EDIT: and it will update everything to stock: hboot, recovery, ROM, etc. so no need to mess with all that, unlike most users
IMHO, keep S-Off, as some phones do ship S-Off. The only dead giveaways that you "messed" with your phone, are the TAMPERED, RELOCKED, and red text at boot-up.
However if you are more comfortable with S-On ("fastboot oem writesecureflag 3") ONLY do so after you are completely satisfied that everything is back to stock.
So it looks like you're going to need a Windows PC, but other than that, you can go back to fully 100% stock "relatively" easily compared to what many have and are going through.
Click to expand...
Click to collapse
Thanks for yours patient on making this replies and research man.. i really do appreciate it.
Heres the screen shot that you requested earlier.
I am a bit confused with this OS-2.24.707.3 and build number 2.24.401.8 Which one is really my ROm version?? Any idea?
nkk71 said:
Well this is going to be a bit of good news / bad news.
Good news, there's a full RUU exe for you:
http://www.htc1guru.com/dld/ruu_m7_..._10-30-1131-05_release_309365_signed_2_4-exe/
Bad news it's a Windows executable, so you'll need to run that from a Windows PC. This will however allow you to go 100% stock!!!!
BUT, BEFORE THAT, there are some prerequisites. I'll outline the steps:
1- You need to get S-Off. since you're on 1.54 you need to use rumrunner.us method (which is either Windows or Linux, I think). This would involve a stock ROM as well, I don't know if ARHD 13.1 will do or not. It's something you have to check on the rumrunner thread. I havent looked into it much, so you're going to need help from someone else and/or do some reading into this.
2- Once S-Off, you need to remove the TAMPERED sign: http://forum.xda-developers.com/showthread.php?t=2477792
3- While still on S-Off, you need to "LOCKED" your bootloader (not "RELOCKED"): http://forum.xda-developers.com/showthread.php?t=2475914
4- Finally run the above RUU, because you are S-Off it WILL allow you to downgrade. Since it's a full RUU it should put your phone completely back to stock (and not even break the touchscreen drivers, the way nandroid backups do).
EDIT: and it will update everything to stock: hboot, recovery, ROM, etc. so no need to mess with all that, unlike most users
IMHO, keep S-Off, as some phones do ship S-Off. The only dead giveaways that you "messed" with your phone, are the TAMPERED, RELOCKED, and red text at boot-up.
However if you are more comfortable with S-On ("fastboot oem writesecureflag 3") ONLY do so after you are completely satisfied that everything is back to stock.
So it looks like you're going to need a Windows PC, but other than that, you can go back to fully 100% stock "relatively" easily compared to what many have and are going through.
Click to expand...
Click to collapse
Hi nkk71, I am confused which version of ROM that i have.. Im afraid to download it might be a wrong one.
In bootloader Mode I can see this O.S-2.24.707.3
but in settings i can see a build number 2.24.401.8 CL235216 release keys which one will i download for RUU Stock
mctodd said:
Hi nkk71, I am confused which version of ROM that i have.. Im afraid to download it might be a wrong one.
In bootloader Mode I can see this O.S-2.24.707.3
but in settings i can see a build number 2.24.401.8 CL235216 release keys which one will i download for RUU Stock
Click to expand...
Click to collapse
Bootloader shows the "more" correct version x.xx.707.x
In settings it only shows the ROM you are based on.
Go for the RUU with .707. in it.
Keep s-off for the time being, that will allow u to change in case u need to. I have to sign off for today...
Sent from my HTC One using Tapatalk
nkk71 said:
Well this is going to be a bit of good news / bad news.
Good news, there's a full RUU exe for you:
http://www.htc1guru.com/dld/ruu_m7_..._10-30-1131-05_release_309365_signed_2_4-exe/
Bad news it's a Windows executable, so you'll need to run that from a Windows PC. This will however allow you to go 100% stock!!!!
BUT, BEFORE THAT, there are some prerequisites. I'll outline the steps:
1- You need to get S-Off. since you're on 1.54 you need to use rumrunner.us method (which is either Windows or Linux, I think). This would involve a stock ROM as well, I don't know if ARHD 13.1 will do or not. It's something you have to check on the rumrunner thread. I havent looked into it much, so you're going to need help from someone else and/or do some reading into this.
2- Once S-Off, you need to remove the TAMPERED sign: http://forum.xda-developers.com/showthread.php?t=2477792
3- While still on S-Off, you need to "LOCKED" your bootloader (not "RELOCKED"): http://forum.xda-developers.com/showthread.php?t=2475914
4- Finally run the above RUU, because you are S-Off it WILL allow you to downgrade. Since it's a full RUU it should put your phone completely back to stock (and not even break the touchscreen drivers, the way nandroid backups do).
EDIT: and it will update everything to stock: hboot, recovery, ROM, etc. so no need to mess with all that, unlike most users
IMHO, keep S-Off, as some phones do ship S-Off. The only dead giveaways that you "messed" with your phone, are the TAMPERED, RELOCKED, and red text at boot-up.
However if you are more comfortable with S-On ("fastboot oem writesecureflag 3") ONLY do so after you are completely satisfied that everything is back to stock.
So it looks like you're going to need a Windows PC, but other than that, you can go back to fully 100% stock "relatively" easily compared to what many have and are going through.
Click to expand...
Click to collapse
nkk71 said:
Bootloader shows the "more" correct version x.xx.707.x
In settings it only shows the ROM you are based on.
Go for the RUU with .707. in it.
Keep s-off for the time being, that will allow u to change in case u need to. I have to sign off for today...
Sent from my HTC One using Tapatalk
Click to expand...
Click to collapse
Thanks alot man.. Your such a help..
nkk71 said:
Well this is going to be a bit of good news / bad news.
Good news, there's a full RUU exe for you:
http://www.htc1guru.com/dld/ruu_m7_..._10-30-1131-05_release_309365_signed_2_4-exe/
Bad news it's a Windows executable, so you'll need to run that from a Windows PC. This will however allow you to go 100% stock!!!!
BUT, BEFORE THAT, there are some prerequisites. I'll outline the steps:
1- You need to get S-Off. since you're on 1.54 you need to use rumrunner.us method (which is either Windows or Linux, I think). This would involve a stock ROM as well, I don't know if ARHD 13.1 will do or not. It's something you have to check on the rumrunner thread. I havent looked into it much, so you're going to need help from someone else and/or do some reading into this.
2- Once S-Off, you need to remove the TAMPERED sign: http://forum.xda-developers.com/showthread.php?t=2477792
3- While still on S-Off, you need to "LOCKED" your bootloader (not "RELOCKED"): http://forum.xda-developers.com/showthread.php?t=2475914
4- Finally run the above RUU, because you are S-Off it WILL allow you to downgrade. Since it's a full RUU it should put your phone completely back to stock (and not even break the touchscreen drivers, the way nandroid backups do).
EDIT: and it will update everything to stock: hboot, recovery, ROM, etc. so no need to mess with all that, unlike most users
IMHO, keep S-Off, as some phones do ship S-Off. The only dead giveaways that you "messed" with your phone, are the TAMPERED, RELOCKED, and red text at boot-up.
However if you are more comfortable with S-On ("fastboot oem writesecureflag 3") ONLY do so after you are completely satisfied that everything is back to stock.
So it looks like you're going to need a Windows PC, but other than that, you can go back to fully 100% stock "relatively" easily compared to what many have and are going through.
Click to expand...
Click to collapse
Hi nkk71, is it possible to flash the ruu that you linked above to back to stock so i'll be able to run rumrunner S-off.. Cuz i tried in ARHD 13.1 didnt work after 8 pouring it says "please wait 30 seconds and run rumrunner again,press enter to exit" I had multiple attempts already and never worked..
nkk71 said:
Well this is going to be a bit of good news / bad news.
Good news, there's a full RUU exe for you:
http://www.htc1guru.com/dld/ruu_m7_..._10-30-1131-05_release_309365_signed_2_4-exe/
Bad news it's a Windows executable, so you'll need to run that from a Windows PC. This will however allow you to go 100% stock!!!!
BUT, BEFORE THAT, there are some prerequisites. I'll outline the steps:
1- You need to get S-Off. since you're on 1.54 you need to use rumrunner.us method (which is either Windows or Linux, I think). This would involve a stock ROM as well, I don't know if ARHD 13.1 will do or not. It's something you have to check on the rumrunner thread. I havent looked into it much, so you're going to need help from someone else and/or do some reading into this.
2- Once S-Off, you need to remove the TAMPERED sign: http://forum.xda-developers.com/showthread.php?t=2477792
3- While still on S-Off, you need to "LOCKED" your bootloader (not "RELOCKED"): http://forum.xda-developers.com/showthread.php?t=2475914
4- Finally run the above RUU, because you are S-Off it WILL allow you to downgrade. Since it's a full RUU it should put your phone completely back to stock (and not even break the touchscreen drivers, the way nandroid backups do).
EDIT: and it will update everything to stock: hboot, recovery, ROM, etc. so no need to mess with all that, unlike most users
IMHO, keep S-Off, as some phones do ship S-Off. The only dead giveaways that you "messed" with your phone, are the TAMPERED, RELOCKED, and red text at boot-up.
However if you are more comfortable with S-On ("fastboot oem writesecureflag 3") ONLY do so after you are completely satisfied that everything is back to stock.
So it looks like you're going to need a Windows PC, but other than that, you can go back to fully 100% stock "relatively" easily compared to what many have and are going through.
Click to expand...
Click to collapse
Hi there nkk71, did you see my new THREAD?? Pls help me man im in big trouble now. cannot flash a rom. Even though its successfully installed keeps bringing me back to recovery. thanks in advance
mctodd said:
Hi there nkk71, did you see my new THREAD?? Pls help me man im in big trouble now. cannot flash a rom. Even though its successfully installed keeps bringing me back to recovery. thanks in advance
Click to expand...
Click to collapse
I'll get back to u in an hour or two...
Sent from my HTC One using Tapatalk
nkk71 said:
Well this is going to be a bit of good news / bad news.
Good news, there's a full RUU exe for you:
http://www.htc1guru.com/dld/ruu_m7_..._10-30-1131-05_release_309365_signed_2_4-exe/
Bad news it's a Windows executable, so you'll need to run that from a Windows PC. This will however allow you to go 100% stock!!!!
BUT, BEFORE THAT, there are some prerequisites. I'll outline the steps:
1- You need to get S-Off. since you're on 1.54 you need to use rumrunner.us method (which is either Windows or Linux, I think). This would involve a stock ROM as well, I don't know if ARHD 13.1 will do or not. It's something you have to check on the rumrunner thread. I havent looked into it much, so you're going to need help from someone else and/or do some reading into this.
2- Once S-Off, you need to remove the TAMPERED sign: http://forum.xda-developers.com/showthread.php?t=2477792
3- While still on S-Off, you need to "LOCKED" your bootloader (not "RELOCKED"): http://forum.xda-developers.com/showthread.php?t=2475914
4- Finally run the above RUU, because you are S-Off it WILL allow you to downgrade. Since it's a full RUU it should put your phone completely back to stock (and not even break the touchscreen drivers, the way nandroid backups do).
EDIT: and it will update everything to stock: hboot, recovery, ROM, etc. so no need to mess with all that, unlike most users
IMHO, keep S-Off, as some phones do ship S-Off. The only dead giveaways that you "messed" with your phone, are the TAMPERED, RELOCKED, and red text at boot-up.
However if you are more comfortable with S-On ("fastboot oem writesecureflag 3") ONLY do so after you are completely satisfied that everything is back to stock.
So it looks like you're going to need a Windows PC, but other than that, you can go back to fully 100% stock "relatively" easily compared to what many have and are going through.
Click to expand...
Click to collapse
At number 4. Did mean that i have to manually downgrade or it is automatic??
mctodd said:
At number 4. Did mean that i have to manually downgrade or it is automatic??
Click to expand...
Click to collapse
It's automatic. If there's an error let me know
Keep S-Off !!
nkk71 said:
It's automatic. If there's an error let me know
Keep S-Off !!
Click to expand...
Click to collapse
I did run the RUU 2.26.707.5, it didnt succeed..I says wrong MID..!!Could i change MID since im S-Off at the moment? but my bootloader is already locked.
mctodd said:
I did run the RUU 2.26.707.5, it didnt succeed..I says wrong MID..!!Could i change MID since im S-Off at the moment? but my bootloader is already locked.
Click to expand...
Click to collapse
my bad, didnt check your MID, anyway instead of changing it download this: http://www.htc1guru.com/dld/ruu-zip...0-01_release_312087_signed_2_4_decrypted-zip/
for simplicity, rename the file to "ruu.zip" and place it in your adb folder.
it's a RUU zip file not exe, so you need to flash it:
so get to bootloader/FASTBOOT USB (either using "adb reboot bootloader" or POWER + VOLDOWN buttons)
then:
fastboot oem rebootRUU
fastboot flash zip ruu.zip
fastboot flash zip ruu.zip <- yes twice, the first time it will come back with "failed flush again", the second time it should report success
fastboot reboot-bootloader
fastboot getvar all <- to confirm it downgraded
nkk71 said:
my bad, didnt check your MID, anyway instead of changing it download this: http://www.htc1guru.com/dld/ruu-zip...0-01_release_312087_signed_2_4_decrypted-zip/
for simplicity, rename the file to "ruu.zip" and place it in your adb folder.
it's a RUU zip file not exe, so you need to flash it:
so get to bootloader/FASTBOOT USB (either using "adb reboot bootloader" or POWER + VOLDOWN buttons)
then:
fastboot oem rebootRUU
fastboot flash zip ruu.zip
fastboot flash zip ruu.zip <- yes twice, the first time it will come back with "failed flush again", the second time it should report success
fastboot reboot-bootloader
fastboot getvar all <- to confirm it downgraded
Click to expand...
Click to collapse
Once it succeeded it is ready for service repair to claim warranty? Thanks

[SOLVED] Stock O2 UK Nandroid or Zip?

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

Can't get back to stock. Computer won't recognize phone now.

So my current setup is this:
Tampered
Relocked
SecurityWarning
M7_MLS PVT SHIP S-ON RH
HBOOT 1.57.0000
Radio 1.01.20.0904_2
Open DSPv32.120.274.0909
OS-3.04.651.2o (the little o at the end of this line is highlighted)
eMMC-boot 2048MB
I'm just trying to get this phone back in working condition so I can give it to my daughter. But nothing I do is working. Currently phone boots into some old version, not sure what. But I can't do over the air updates because it just reboots into the bootloader and won't finish.
I've refreshed back to stock from the bootloader, and started down the path found in this thread:
http://forum.xda-developers.com/showthread.php?t=2618524
to get S-OFF (NOTE: I'm on hboot 1.57 and it's for 1.55, but I have no idea how to get back to 1.55)
I got through the first step (tricking it into thinking it's on version 3.04.651.2) and now when I do an adb devices, it isn't seeing my phone anymore. Also, I seem to have lost recovery? I had TRWP on there and now if I try to select 'recovery' it just returns to the bootloader screen and won't go into recovery any more.
Help. It literally just want to wipe the thing and put something useable on it. Stock, rooted or not, whatever. If I try to update the software on the phone from within the phone settings, it reboots into the bootloader and gets stuck.
Thanks in advance!
Probably the easiest thing to do then is to flash the full firmware first. Then run the RUU. You probably can get by with just the RUU, but it sometimes errors out if the firmware is not flashed first. You can get the firmware and the RUU (along with basic instructions on how to use them) from here: http://forum.xda-developers.com/showthread.php?t=2795856
coal686 said:
Probably the easiest thing to do then is to flash the full firmware first. Then run the RUU. You probably can get by with just the RUU, but it sometimes errors out if the firmware is not flashed first. You can get the firmware and the RUU (along with basic instructions on how to use them) from here: http://forum.xda-developers.com/showthread.php?t=2795856
Click to expand...
Click to collapse
That worked! Thank you so much!!

Categories

Resources