How do I unlock the boot loader when there is no oem setting to allow unlocking the boot loader in developer options? I have the token the phone is running marshmallow. It is S off and has CID 11111111. One thing can I flash TWRP to my phone without messing with the boot loader. If so then I can just use TWRP to flash the model ID and EU RRU thanks in advance. Just read I cannot flash TWRP without unlocking the boot loader.
jconradb said:
How do I unlock the boot loader when there is no oem setting to allow unlocking the boot loader in developer options? I have the token the phone is running marshmallow. It is S off and has CID 11111111. One thing can I flash TWRP to my phone without messing with the boot loader. If so then I can just use TWRP to flash the model ID and EU RRU thanks in advance. Just read I cannot flash TWRP without unlocking the boot loader.
Click to expand...
Click to collapse
I'm not sure what your exact situation is but i don't think OEM unlocking through Settings is an option. Have you tried this ... See link below
https://forum.xda-developers.com/showthread.php?t=2708571
Aimless Rambler said:
I'm not sure what your exact situation is but i don't think OEM unlocking through Settings is an option. Have you tried this ... See link below
https://forum.xda-developers.com/showthread.php?t=2708571
Click to expand...
Click to collapse
Yes my comment is vague, I want to unlock my boot loader but cannot. All settings on the M8 are set such as USB debugging and I have the unlocking code from HTC. When I proceed to unlock the phone and choose option to unlock the phone, phone reboots but the boot loader is still locked. On the HTC web site it states with Marshmallow this can happen and you must go to developers options and highlight OEM option to unlock the boot loader but the option is not there and I'm stuck. Thank you for your reply
Did you try fastboot oem unlock? If it's soff and supercid, should be all that is needed
miffymiffy said:
Did you try fastboot oem unlock? If it's soff and supercid, should be all that is needed
Click to expand...
Click to collapse
Thank you so much I will try that later today and get back to you. Again thanks for the reply ?
miffymiffy said:
Did you try fastboot oem unlock? If it's soff and supercid, should be all that is needed
Click to expand...
Click to collapse
Far as I know, this will not work.
May need to use the following method (if unlock token doesn't work) and root is also required:
https://forum.xda-developers.com/showthread.php?t=2708571
---------- Post added at 12:27 PM ---------- Previous post was at 12:16 PM ----------
jconradb said:
If so then I can just use TWRP to flash the model ID and EU RRU thanks in advance. Just read I cannot flash TWRP without unlocking the boot loader.
Click to expand...
Click to collapse
It is correct, you cannot flash TWRP with a locked bootloader (needs to be unlocked) by definition.
But you also don't flash an RUU in TWRP. You also may not need to change the MID, depending on what version you have.
Please do fastboot getvar all, and post the results (delete IMEI and serial number before posting). Need to verify some details before supplying advice, which may be harmful to your device.
redpoint73 said:
Far as I know, this will not work.
May need to use the following method (if unlock token doesn't work) and root is also required:
https://forum.xda-developers.com/showthread.php?t=2708571
---------- Post added at 12:27 PM ---------- Previous post was at 12:16 PM ----------
It is correct, you cannot flash TWRP with a locked bootloader (needs to be unlocked) by definition.
But you also don't flash an RUU in TWRP. You also may not need to change the MID, depending on what version you have.
Please do fastboot getvar all, and post the results (delete IMEI and serial number before posting). Need to verify some details before supplying advice, which may be harmful to your device.
Click to expand...
Click to collapse
Here you go and thanks
jconradb said:
Here you go and thanks
Click to expand...
Click to collapse
What RUU are you trying to run, and how exactly (command syntax, etc.)?
Are you actually getting a model ID error when running the RUU?
redpoint73 said:
What RUU are you trying to run, and how exactly (command syntax, etc.)?
Are you actually getting a model ID error when running the RUU?
Click to expand...
Click to collapse
I want to change to EU RUU so as I understand I must change model id as mine is developer model id as is my RUU. Plus rooting would be nice
jconradb said:
I want to change to EU RUU
Click to expand...
Click to collapse
I should have been more specific. What RUU number, and where did you get it from?
jconradb said:
I want to change to EU RUU so as I understand I must change model id as mine is developer model id as is my RUU.
Click to expand...
Click to collapse
Your model ID (MID) is for AT&T and Developer's Edition.
You may or may not need to change the MID, in order to run the Euro RUU. Sometimes (often) having SuperCID (11111111) will bypass the MID check for RUUs. So I would suggest running the RUU, and see if it gives you model ID error, or if it just work (before messing with the MID, if you don't have to).
redpoint73 said:
I should have been more specific. What RUU number, and where did you get it from?
Your model ID (MID) is for AT&T and Developer's Edition.
You may or may not need to change the MID, in order to run the Euro RUU. Sometimes (often) having SuperCID (11111111) will bypass the MID check for RUUs. So I would suggest running the RUU, and see if it gives you model ID error, or if it just work (before messing with the MID, if you don't have to).
Click to expand...
Click to collapse
Actually this whole thing started when I installed the developer RUU on the phone. After this I noticed when I launched the camera a message came that the lens is blocked. I think it's a RUU issue. You see the RUU I had before which was Kit Kat camera worked but many other issues. The marshmallow RUU was downloaded from a member of this forum forget his name
jconradb said:
Actually this whole thing started when I installed the developer RUU on the phone. After this I noticed when I launched the camera a message came that the lens is blocked. I think it's a RUU issue.
Click to expand...
Click to collapse
Unlikely an issue with the RUU itself. I was on the Dev Edition RUU for a while (as have many others), and the camera worked fine. But it's not a bad idea to try the Euro RUU, and see if that helps.
jconradb said:
The marshmallow RUU was downloaded from a member of this forum forget his name
Click to expand...
Click to collapse
Wow, that is remarkably vague. The file doesn't have a version number, or name? Not providing any useful info, forces us to guess. Lucky for you, I have a pretty good guess.
Try the following Euro RUU, and instructions:
https://forum.xda-developers.com/showpost.php?p=64926626&postcount=6
Alternately, if you have an SD card, rename the RUU zip to 0P6BIMG.zip put the file on the SD card, insert in phone, and reboot to bootloader, and it should install automatically.
Let us know if it installs, or if you get error messages (and what the error messages are, specifically).
redpoint73 said:
Unlikely an issue with the RUU itself. I was on the Dev Edition RUU for a while (as have many others), and the camera worked fine. But it's not a bad idea to try the Euro RUU, and see if that helps.
Wow, that is remarkably vague. The file doesn't have a version number, or name? Not providing any useful info, forces us to guess. Lucky for you, I have a pretty good guess.
Try the following Euro RUU, and instructions:
https://forum.xda-developers.com/showpost.php?p=64926626&postcount=6
Alternately, if you have an SD card, rename the RUU zip to 0P6BIMG.zip put the file on the SD card, insert in phone, and reboot to bootloader, and it should install automatically.
Let us know if it installs, or if you get error messages (and what the error messages are, specifically).
Click to expand...
Click to collapse
Ckpv5 was his name on this forum he uploaded the file
jconradb said:
Ckpv5 was his name on this forum he uploaded the file
Click to expand...
Click to collapse
So to do your install I can do this with the standard recovery and model id I have
jconradb said:
So to do your install I can do this with the standard recovery and model id I have
Click to expand...
Click to collapse
Recovery doesn't matter for RUU install, it will be overwritten by stock recovery regardless of what is presently there.
Model ID is what I mentioned before. The RUU may or may not work with your MID. If it fails with model ID error, we know we need to change the MID. If it works, then it works.
redpoint73 said:
Recovery doesn't matter for RUU install, it will be overwritten by stock recovery regardless of what is presently there.
Model ID is what I mentioned before. The RUU may or may not work with your MID. If it fails with model ID error, we know we need to change the MID. If it works, then it works.
Click to expand...
Click to collapse
Hello I am worried to flash the RUU because I tried to change the mid to EU using adb she'll message permission denied oem blocked, stupid at&t
jconradb said:
Hello I am worried to flash the RUU because I tried to change the mid to EU using adb she'll message permission denied oem blocked, stupid at&t
Click to expand...
Click to collapse
AT&T has nothing to do with it, it's not what "oem blocked" means. This is probably pilot error. Do you have root, since it's required to change the MID?
And you are not following my advice why, because of some assumed or imagined fear that isn't based on any fact? Flashing the RUU with the wrong MID is not going to harm the device. The worst that will happen is an error message (wrong model) and the RUU will not install. The phone remains exactly as it was before you tried the RUU. And meaning you have to change the MID to run the RUU.
Best case, the RUU works, and you no longer have to mess with changing the MID.
redpoint73 said:
AT&T has nothing to do with it, it's not what "oem blocked" means. This is probably pilot error. Do you have root, since it's required to change the MID?
And you are not following my advice why, because of some assumed or imagined fear that isn't based on any fact? Flashing the RUU with the wrong MID is not going to harm the device. The worst that will happen is an error message (wrong model) and the RUU will not install. The phone remains exactly as it was before you tried the RUU. And meaning you have to change the MID to run the RUU.
Best case, the RUU works, and you no longer have to mess with changing the MID.
Click to expand...
Click to collapse
OK I will follow your advice thank you for your time and effort
redpoint73 said:
AT&T has nothing to do with it, it's not what "oem blocked" means. This is probably pilot error. Do you have root, since it's required to change the MID?
And you are not following my advice why, because of some assumed or imagined fear that isn't based on any fact? Flashing the RUU with the wrong MID is not going to harm the device. The worst that will happen is an error message (wrong model) and the RUU will not install. The phone remains exactly as it was before you tried the RUU. And meaning you have to change the MID to run the RUU.
Best case, the RUU works, and you no longer have to mess with changing the MID.
Click to expand...
Click to collapse
OK let's assume this RUU works will try tomorrow I think. How would I root this phone remembering the issues to unlock the boot loader. The unlock code did not work because of the oem option missing developer
jconradb said:
OK let's assume this RUU works will try tomorrow I think. How would I root this phone remembering the issues to unlock the boot loader. The unlock code did not work because of the oem option missing developer
Click to expand...
Click to collapse
oem unlocking being "missing" is not the problem. It wasn't on most OS builds for the M8, and was only added later. In fact, I'm not sure it was ever present on this device (or maybe just some versions). If it's not there, you don't need to enable it. Unlocking the bootloader should work normally.
So clearly, something is wrong, if you are doing the bootloader unlock, and it doesn't work. Let's try to run the RUU, and go from there.
Related
Hi people I hope one of your intelligent folk can help me out. Basically I bought a M8 on eBay at good price. The problem with it is it is STUCK in BOOTLOADER.
When I got the phone it was rooted, boot loader unlocked, and TWRP recovery. So after spending close to 7 hours trying to get this thing back to 100% STOCK, I think I am running of options. So after doing a LOT OF research I learnt that I need RUU to take back to stock but in order to do that I needed to UNROOT, so I CMD; "OEM lock" which made the phone "Relocked" "Tampered". So I thought I was done but now I am still having the same issue as I had before which is in RUU I keeping getting "131 Customer ID Error". Apparently that errors means I am using the wrong region RUU, but how is that possible when I am using the Sprint RUU found on XDA?!? So basically, I believe my solution is that to get my S-off but how can I get my S-off if the only thing I can access is the Bootloader?
Someone please help me! I am willing to paypal money if needed. Thank you.
Check the CID by going into fastboot and type the command:
fastboot getvar all
Are you sure it the Sprint variant? Does the Sprint version have the carrier's logo on it somewhere?
redpoint73 said:
Check the CID by going into fastboot and type the command:
fastboot getvar all
Are you sure it the Sprint variant? Does the Sprint version have the carrier's logo on it somewhere?
Click to expand...
Click to collapse
This is what I get:
Also, i am positive this is Sprint version and I should also mention that when I first got the phone I was able to flash roms since it had twrp on it, but everytime i would flash a rom it would keep rebooting about 10 seconds into the os. Which is why I went the RUU route. The RUU i am using can be found here: http://forum.xda-developers.com/showthread.php?t=2729173
The EXE version gives me the 131 error and the ADB version also give me an error.
@YungMoola15 hey man, delete your imei from the post. Your imei should be private.
stathis95194 said:
@YungMoola15 hey man, delete your imei from the post. Your imei should be private.
Click to expand...
Click to collapse
To OP, its true you should never post IMEI. In any case, just for the record I never told you to post the info returned from "getvar all" (although the vast majority of that info aside from IMEI is not personal info); I just told you to check the CID using that command.
Does the device's CID match that of Sprint (don't personally know what that is)?
---------- Post added at 10:16 AM ---------- Previous post was at 10:15 AM ----------
YungMoola15 said:
The RUU i am using can be found here: http://forum.xda-developers.com/showthread.php?t=2729173
The EXE version gives me the 131 error and the ADB version also give me an error.
Click to expand...
Click to collapse
Is says right in the first post of that thread that you need SuperCID to run this RUU; and even gives the fastboot command to change to SuperCID.
As the title says, I'm trying to root my HTC One X. I currently am on 4.0.4 Android version, 4.0 HTC Sense version, and software number is 2.20.502.7 710RD. I found a video tutorial with this exact software and phone and I followed all of the steps. I figured out how to install adb and fastboot so I could use fastboot commands. I changed my CID to 11111111 and got my HTC dev code. However when I go to type in the command: fastboot flash unlock Unlock_code.bin I keep getting the same error message. The error message is (Boootloader) FAILED (signature verify fail). In the tutorial this did not happen so I don't really know what to do at this point. If someone could please help that would be much appreciated.
Hello
Are you sure you have the correct unlock code?
Did you copy it correctly?
Did you place the unlock code in the fastboot folder on your PC before executing the command?
Try a different cable and/or USB port. Dont connect via a HUB
Why did you need to change the CID?
Have a look at http://onexroot.com/one-x-root/how-to-root-one-x/
Dont change to S-OFF in case you do something wrong, this will save you by keeping S-ON
Reply
grwalker said:
Hello
Are you sure you have the correct unlock code?
Did you copy it correctly?
Did you place the unlock code in the fastboot folder on your PC before executing the command?
Try a different cable and/or USB port. Dont connect via a HUB
Why did you need to change the CID?
Dont change to S-OFF in case you do something wrong, this will save you by keeping S-ON
Click to expand...
Click to collapse
Yes I copied the unlock token correctly and everything. I have not tried different USB ports. I needed to change the CID because on the One X the CID needs to be 11111111 in order to root. I haven't changed to S-OFF yet. Any other help?
The One X does not need to be 11111111 to root.
I really believe that your bootloader is still locked. Please double check and make sure the unlock code was copied exactly as per the procedure in the link i sent. Even the slightest mistake in copying will cause a fail
In fastboot mode, what does it say at the top of the screen
Also try fastboot oem unlock
grwalker said:
The One X does not need to be 11111111 to root.
I really believe that your bootloader is still locked. Please double check and make sure the unlock code was copied exactly as per the procedure in the link i sent. Even the slightest mistake in copying will cause a fail
In fastboot mode, what does it say at the top of the screen
Also try fastboot oem unlock
Click to expand...
Click to collapse
I copied the code down correctly undoubtedly, at the top it says
*** TAMPERED***
*** LOCKED ***
Hboot 1.14
Should my bootloader say unlocked???
Yes it should say unlocked.
What I think has happened is that you used an incorrect/incomplete unlock code to unlock the bootloader. Hence the word TAMPERED. Perhaps even changing your CID also didn't help. Not sure.
You said you followed a video? send link of method you used
What was your original CID?
Try unlocking bootloader again. In post #2 there is a link to a tutorial. Follow this exactly.
Also double check in fastboot mode to see it it says S-OFF. To change your CID i am sure you must have changed to S-OFF?
Unlocking boot loader does not root the phone. It's just the first step
Also (but not a problem) you have an old bootloader. 1.14. That will need to be updated if you want to flash custom ROMS
grwalker said:
Yes it should say unlocked.
What I think has happened is that you used an incorrect/incomplete unlock code to unlock the bootloader. Hence the word TAMPERED. Perhaps even changing your CID also didn't help. Not sure.
You said you followed a video? send link of method you used
What was your original CID?
Try unlocking bootloader again. In post #2 there is a link to a tutorial. Follow this exactly.
Also double check in fastboot mode to see it it says S-OFF. To change your CID i am sure you must have changed to S-OFF?
Unlocking boot loader does not root the phone. It's just the first step
Also (but not a problem) you have an old bootloader. 1.14. That will need to be updated if you want to flash custom ROMS
Click to expand...
Click to collapse
I can't post a link here but if you google "how to root htc one 2.20" it should be the first one and it is by max lee. I don't have S-OFF because I used a one click method to change my CID and to get the code.
Do you an AT&T phone?
I hope so. This method is for an AT&T HTC One X
grwalker said:
Do you an AT&T phone?
I hope so. This method is for an AT&T HTC One X
Click to expand...
Click to collapse
Yes I have that exact one
Then i can only suggest that you copied the token incorrectly.
Watch the tutorial again and then try it again
I'm a very new android user, so please forgive my ignorance.
I'm using a sim unlocked AT&T M8 outside USA with a different carrier. Right now, the bootloader is Locked, CID is 11111111 and S-OFF. I've downloaded the official marshmallow AT&T RUU for m8 from htc website.
I follow the install instructions until the update actually starts. Then it stops after about 10-20 seconds and shows Error 155: unknown error and enters into the recovery steps (in the RUU). My current software number is 4.28.502.2 and im trying to update to RUU_M8_UL_M60_SENSE70_ATT_MR_Cingular_US_6.20.502.5
Can someone please help me out with this? I've been trying for over a week now. I will never receive the OTA's since I'm not using an AT&T sim. So RUU is the only other option left. Thanks a lot in advance.
http://forum.xda-developers.com/showpost.php?p=66886759&postcount=23
ckpv5 said:
http://forum.xda-developers.com/showpost.php?p=66886759&postcount=23
Click to expand...
Click to collapse
Thanks for your reply man, but im extremely lost here. Could you please guide me step by step? I've downloaded the firmware. Where do I put it? I've tried the adb folder. But it show error: can not locate firmware.zip.
Edit: Another question. Is that firmware applicable for my device?
The firmware is applicable BUT since you're using your device outside USA and not on AT&T carrier, S-Off .. the best thing for you to do is fully convert your device to other region, maybe a EU region or Dev Edition .. more suitable for you.
I read somewhere, with the latest firmware you may have calls problem due to Voice HD implemented by AT&T
If you're interested in converting, I will guide you (when I am available)
ckpv5 said:
The firmware is applicable BUT since you're using your device outside USA and not on AT&T carrier, S-Off .. the best thing for you to do is fully convert your device to other region, maybe a EU region or Dev Edition .. more suitable for you.
I read somewhere, with the latest firmware you may have calls problem due to Voice HD implemented by AT&T
If you're interested in converting, I will guide you (when I am available)
Click to expand...
Click to collapse
That would be very kind of you, thanks. Though, i think I've already messed up my phone. I finally got to update with the firmware in the link. The RUU was going on smoothly as well, until it reached 38% when Error 155 showed up again. The phone then went on to the bootloader screen with no options for fastboot, restore or such. I restarted it and entered the bootloader. My firmware is being shown as 6.20.502.5 but when rebooting the phone it won't go past the screen with the HTC logo. I'd be extremely grateful if you could help me out of this mess.
Also, when i open htc sync man, OS number and HTC Sense number shows up as blank, while the firmware number is shown as 6.20.502.5
Big-Bonsai said:
Also, when i open htc sync man, OS number and HTC Sense number shows up as blank, while the firmware number is shown as 6.20.502.5
Click to expand...
Click to collapse
Aren't you supposed to uninstall Htc Sync Manager before you run the RUU ?
That was clearly stated in link that I gave you earlier, and you also need PC with USB 2.0
Uninstall HTC Sync Manager but leave HTC USB drivers then try again to run RUU after you put the device on bootloader/fastboot mode.
ckpv5 said:
Aren't you supposed to uninstall Htc Sync Manager before you run the RUU ?
That was clearly stated in link that I gave you earlier, and you also need PC with USB 2.0
Click to expand...
Click to collapse
Yeah I did. I re-installed it later to see if it would show any information.
Most important is RUU must complete 100%, no error 155
I never use Htc Sync Manager, so I don't know what is shown there.
ckpv5 said:
Most important is RUU must complete 100%, no error 155
I never use Htc Sync Manager, so I don't know what is shown there.
Click to expand...
Click to collapse
So I'm gonna try the RUU again. I'll keep you updated. You've been a big help. Thanks a lot!!
Big-Bonsai said:
I'm a very new android user, so please forgive my ignorance.
I'm using a sim unlocked AT&T M8 outside USA with a different carrier. Right now, the bootloader is Locked, CID is 11111111 and S-OFF. I've downloaded the official marshmallow AT&T RUU for m8 from htc website.
I follow the install instructions until the update actually starts. Then it stops after about 10-20 seconds and shows Error 155: unknown error and enters into the recovery steps (in the RUU). My current software number is 4.28.502.2 and im trying to update to RUU_M8_UL_M60_SENSE70_ATT_MR_Cingular_US_6.20.502.5
Can someone please help me out with this? I've been trying for over a week now. I will never receive the OTA's since I'm not using an AT&T sim. So RUU is the only other option left. Thanks a lot in advance.
Click to expand...
Click to collapse
I don't know if it's the problem,but did you try the RUU after unlocking your bootloader as you are S-OFF?
I think it's supposed to be unlocked if you have S-OFF.
Edit:Just got to know that S-OFF devices have nothing to do with unlocked or locked bootloader.
Why don't you try a EU RUU?Mine was also a AT&T device,but I converted it.
Jongla said:
I don't know if it's the problem,but did you try the RUU after unlocking your bootloader as you are S-OFF?
I think it's supposed to be unlocked if you have S-OFF.
Edit:Just got to know that S-OFF devices have nothing to do with unlocked or locked bootloader.
Why don't you try a EU RUU?Mine was also a AT&T device,but I converted it.
Click to expand...
Click to collapse
Hey man, thanks for replying here. I sent you a pm. Could you please check?
ckpv5 said:
Most important is RUU must complete 100%, no error 155
I never use Htc Sync Manager, so I don't know what is shown there.
Click to expand...
Click to collapse
Hello there. I kind of made it work. What I did was take the rom.zip from the ruu file and flash it via htc fastboot special. And it worked well. The only problem I'm facing now is that the boot animations are EXTREMELY slow. But once it's past that, everything seems pretty normal. I wiped the cache from recovery but that didn't help. Do you have any suggestions for me?
Big-Bonsai said:
\The only problem I'm facing now is that the boot animations are EXTREMELY slow. But once it's past that, everything seems pretty normal. I wiped the cache from recovery but that didn't help.
Click to expand...
Click to collapse
Meaning the boot animations are slow every time you boot, or just the first time (its unclear from what you've posted)? First time booting after RUU will be slow, due to cache being setup, etc. And clearing cache will cause that process to repeat when you start up again.
---------- Post added at 09:32 AM ---------- Previous post was at 09:30 AM ----------
Jongla said:
I think it's supposed to be unlocked if you have S-OFF.
Edit:Just got to know that S-OFF devices have nothing to do with unlocked or locked bootloader.
Click to expand...
Click to collapse
Neither of those statements is entirely correct.
With s-off, you can run an RUU with bootloader locked or relocked. Essentially, the check for the bootloader unlocked condition is bypassed with s-off.
But having the bootloader locked still means its locked (even with s-off). Meaning you can't do things like flash custom recovery with bootloader locked (even with s-off).
redpoint73 said:
Meaning the boot animations are slow every time you boot, or just the first time (its unclear from what you've posted)? First time booting after RUU will be slow, due to cache being setup, etc. And clearing cache will cause that process to repeat when you start up again.
Hello there. Thanks for the reply. What I meant was, the boot animations are slow every time I reboot the device.
Things I have already done:
1. Flashed the rom.zip again.
2. Factory reset.
3. Wiped the cache from recovery multiple times.
4. Restarted in all possible ways. Normal restart. Power off, wait 10 minutes and power on again. Pressed the power and volume up button for restarting. Reboot via fastboot.
I'd really appreciate if you could help me out.
Click to expand...
Click to collapse
redpoint73 said:
Meaning the boot animations are slow every time you boot, or just the first time (its unclear from what you've posted)? First time booting after RUU will be slow, due to cache being setup, etc. And clearing cache will cause that process to repeat when you start up again.
---------- Post added at 09:32 AM ---------- Previous post was at 09:30 AM ----------
Neither of those statements is entirely correct.
With s-off, you can run an RUU with bootloader locked or relocked. Essentially, the check for the bootloader unlocked condition is bypassed with s-off.
But having the bootloader locked still means its locked (even with s-off). Meaning you can't do things like flash custom recovery with bootloader locked (even with s-off).
Click to expand...
Click to collapse
Hello there. Thanks for the reply. What I meant was, the boot animations are slow every time I reboot the device.
Things I have already done:
1. Flashed the rom.zip again.
2. Factory reset.
3. Wiped the cache from recovery multiple times.
4. Restarted in all possible ways. Normal restart. Power off, wait 10 minutes and power on again. Pressed the power and volume up button for restarting. Reboot via fastboot.
I'd really appreciate if you could help me out.
Since you've already flashed the RUU again, I don't think there is much else you can do. Maybe its a common issue with the new build?
redpoint73 said:
Since you've already flashed the RUU again, I don't think there is much else you can do. Maybe its a common issue with the new build?
Click to expand...
Click to collapse
Man I searched EVERYWHERE. People dont seem to have any problems like this. What I did find out was that this might happen if the firmware or kernel numbers dont match (or something?). Can you tell me if I did anything wrong?
Big-Bonsai said:
What I did find out was that this might happen if the firmware or kernel numbers dont match (or something?).
Click to expand...
Click to collapse
That only applies to flashing ROMs in custom recovery. WHich is completely different from RUU. RUU re-writes all partitions, including firmware, kernel, ROM, and a bunch of others. So there isn't a possibility of a mismatch; as long as the RUU ran properly. And since you ran the RUU twice, you pretty much eliminated the possibility it didn't install completely.
Some other options you may consider:
1) Unlock the bootloader, flash TWRP custom recovery, flash a different ROM and see if the slow boot issue persists.
2) Change CID and/or MID (which you are free to do since you are s-off) and try another RUU; such as Developer's Edition or Euro.
redpoint73 said:
That only applies to flashing ROMs in custom recovery. WHich is completely different from RUU. RUU re-writes all partitions, including firmware, kernel, ROM, and a bunch of others. So there isn't a possibility of a mismatch; as long as the RUU ran properly. And since you ran the RUU twice, you pretty much eliminated the possibility it didn't install completely.
Some other options you may consider:
1) Unlock the bootloader, flash TWRP custom recovery, flash a different ROM and see if the slow boot issue persists.
2) Change CID and/or MID (which you are free to do since you are s-off) and try another RUU; such as Developer's Edition or Euro.
Click to expand...
Click to collapse
Thank you so much for the reply. I'd like to take your second suggestion. Can you please point me to the right direction? Or guide me through the steps. I don't know if it's asking too much of you. Thanks anyways.
Big-Bonsai said:
Thank you so much for the reply. I'd like to take your second suggestion. Can you please point me to the right direction? Or guide me through the steps.
Click to expand...
Click to collapse
Which version do you want to "convert" to?
Dev Ed is easy, it shares the same model ID (MID) as AT&T, and you already have SuperCID. So all you would need to do is run the MM Dev Ed RUU: http://dl3.htc.com/application/RUU_M8_UL_M60_SENSE70_MR_BrightstarUS_WWE_6.12.1540.4.exe
Euro is a bit more steps, you would need to change to the Euro MID: http://forum.xda-developers.com/showthread.php?t=2708581
Then run Euro MM RUU, noting that relocking bootloader is not needed for you (since you have s-off): http://forum.xda-developers.com/showpost.php?p=64926626&postcount=6
I have an s off unlocked phone. Any of you know if its possible to downgrade to an older update? The new us update is affecting my calls and signal so i need to go back.
Just run the old RUU exe and you'll be set.
Sent from my HTC 10 using Tapatalk
effortless said:
Just run the old RUU exe and you'll be set.
Click to expand...
Click to collapse
Depends. If his handset is s-on he can't "just" run the old ruu. With s-on you can't downgrade the bootloader to a lower version.
So it's either doable with s-off or look for the OS via a backup and try to restore that and run it on the new firmware.
Mr Hofs said:
Depends. If his handset is s-on he can't "just" run the old ruu. With s-on you can't downgrade the bootloader to a lower version.
So it's either doable with s-off or look for the OS via a backup and try to restore that and run it on the new firmware.
Click to expand...
Click to collapse
They state they have an s-off unlocked phone in their first sentence.
Sent from my HTC 10 using Tapatalk
I have HTC10 with s-off and trying to revert to stock with ruu and keep getting error message with wrong version.
pocutzz said:
I have HTC10 with s-off and trying to revert to stock with ruu and keep getting error message with wrong version.
Click to expand...
Click to collapse
Please post the error, so we can see it and help.
andybones said:
Please post the error, so we can see it and help.
Click to expand...
Click to collapse
So in the meantime i reflashed twrp and recovery and restored a backup.
But in the conclusion all i want now is to revert to full stock (i have no backup of that). Can i do that with s-off and bootloader re-locked? the reason that i want to do that is to recieve further updates ota. The reason i did all this to my phone was because the 4g was working when it wanted (not only 4g but mobile data in general). Now i'm thinking of reversing to stock, maybe future updates will solve this or to send the phone back for waranty.
So i need to flash stock, can you guide me from this point to achieve that?
My current software is 1.95.401.3, the phone was unlocked but not developer edition.Cid is HTC__34.
Help me what to do next and i will do one by one until i succeed (sry for my bad english)
@pocutzz you need SuperCID. In download mode, connect phone to pc and open a command window on your computer, type out "fastboot oem writecid 11111111" (I advice you copy and paste this but without the quotation marks), and then you will gain SuperCID. With this, you will be able to install any firmware/RUU regardless of CID.
@ OP, if you want to downgrade, since you are S-OFF there is no need to relock bootloader. As long as your have SuperCID you can downgrade to any firmware just like that. Download RUU and run it.
ZeroInfinity said:
@pocutzz you need SuperCID. In download mode, connect phone to pc and open a command window on your computer, type out "fastboot oem writecid 11111111" (I advice you copy and paste this but without the quotation marks), and then you will gain SuperCID. With this, you will be able to install any firmware/RUU regardless of CID.
@ OP, if you want to downgrade, since you are S-OFF there is no need to relock bootloader. As long as your have SuperCID you can downgrade to any firmware just like that. Download RUU and run it.
Click to expand...
Click to collapse
But after i do super cid what version do you recomend to flash? it will be full stock after? i will be able to recieve updates ota?
pocutzz said:
But after i do super cid what version do you recomend to flash? it will be full stock after? i will be able to recieve updates ota?
Click to expand...
Click to collapse
if you RUU you should still be able to receive OTA afterwards but don't count on me for that one as I've never restored back to stock before. You can search for previous HTC 10 RUUs on google, I recommend not going too far back and just going on the update before the 1.95 one (1.90 I think). Not every version has an RUU so if you can't find an RUU you want, try and find an older version.
ZeroInfinity said:
if you RUU you should still be able to receive OTA afterwards but don't count on me for that one as I've never restored back to stock before. You can search for previous HTC 10 RUUs on google, I recommend not going too far back and just going on the update before the 1.95 one (1.90 I think). Not every version has an RUU so if you can't find an RUU you want, try and find an older version.
Click to expand...
Click to collapse
There is one on the htc website like unlocked/developer edition like 1.91 XXXX , think that will be ok?
pocutzz said:
There is one on the htc website like unlocked/developer edition like 1.91 XXXX , think that will be ok?
Click to expand...
Click to collapse
It should be fine, yes. Make sure you have SuperCID and remember that you do not have to relock your bootloader when running the RUU as you are already S-OFF
ZeroInfinity said:
It should be fine, yes. Make sure you have SuperCID and remember that you do not have to relock your bootloader when running the RUU as you are already S-OFF
Click to expand...
Click to collapse
i re-locked before i run sunshine for s-off. i will try to do that in a few minutes
i have done superCID, but before i try to flas the ruu, wanted to ask you, after that what remains? like s-off,root,twrp,custom recovery?
Okey so i did the superCID, in download mode it shows me the 1111111 but on the phone when i run CID Getter still says HTC__034 (that is how it suppose to show?), i copied from here like you said.Downloaded the ruu.exe from htc website,and when it runs it resets my phone to download mode,the bar goes instantly to 100% and the ruu installer says the 155 error,incorect version i think.
What do i do next?
Maybe MID problem?i've read something about it for HTC M8 i have mid 2PS620000. Maybe the ruu.exe on htc website is for US and i need EU?
Later edit: So i put the global variant with .401. in the sd card and it started to flash, i will se what is what...
pocutzz said:
i have done superCID, but before i try to flas the ruu, wanted to ask you, after that what remains? like s-off,root,twrp,custom recovery?
Okey so i did the superCID, in download mode it shows me the 1111111 but on the phone when i run CID Getter still says HTC__034 (that is how it suppose to show?), i copied from here like you said.Downloaded the ruu.exe from htc website,and when it runs it resets my phone to download mode,the bar goes instantly to 100% and the ruu installer says the 155 error,incorect version i think.
What do i do next?
Maybe MID problem?i've read something about it for HTC M8 i have mid 2PS620000. Maybe the ruu.exe on htc website is for US and i need EU?
Later edit: So i put the global variant with .401. in the sd card and it started to flash, i will se what is what...
Click to expand...
Click to collapse
S-OFF will never be wiped, if you have relocked then it will remain relocked state. Everything else is wiped and restored to stock including recovery, system, data, Internal Storage MIGHT BE WIPED I am not so sure.
if it shows SuperCID in download mode it should be fine. All you needed to do to get it was to execute that command line I posted before.
ZeroInfinity said:
S-OFF will never be wiped, if you have relocked then it will remain relocked state. Everything else is wiped and restored to stock including recovery, system, data, Internal Storage MIGHT BE WIPED I am not so sure.
if it shows SuperCID in download mode it should be fine. All you needed to do to get it was to execute that command line I posted before.
Click to expand...
Click to collapse
thank You for the info.i just flashed from sd card the 401 version, an got the updates,think everything is okey,i will write again after all is good. Ty very much
about 3 friends of mine have bricked htc 10 when trying to downgrade the firmware (Sprint, KKDI and unlocked variant all s-off) I want to ask if I can use the image to sdcard method to unbrick ???
I have a htc M8 UL
Radio_1.29.214500021.12
OP6B10000
S OFF
Unlocked bootloader
Ive tried relocking the bootloader and using htc RUU exe but it didnt work
ive tried the hboot with the ( maybe ) PROPER ruu zip ( 0P6BIMG_M8_UL_M60_SENSE70_MR_HTC_Europe_6.12.401.4_Radio_1.29.214500021.12G_20.72.4196t.01_release_464360_signed.zip)
BUT it said ' error saying device halted due to large image update fail!
press power to reboot.
Do i really need to turn s off and rewrite the cid and mid or there is another way ??
Please help ( my first thread)
The problem is
To get the stock ruu flashed i need to modify the cid and mid
to modify them i need to turn s on to s off
to do that i need sunshine witch it says " there is a problem with your rom"
im stuck i guess
YahyaChagri said:
The problem is
To get the stock ruu flashed i need to modify the cid and mid
to modify them i need to turn s on to s off
to do that i need sunshine witch it says " there is a problem with your rom"
im stuck i guess
Click to expand...
Click to collapse
Try this method. I just reverted back to stock tonight and I'm now completing my OTAs. Seems to be working just fine for now. Make sure you follow each and every steps. Make sure you choose the version with good CID and MID.
https://forum.xda-developers.com/htc-one-m8/help/tutorial-how-to-stock-stock-twrp-t3086860
Hope it helps.
YahyaChagri said:
to modify them i need to turn s on to s off
Click to expand...
Click to collapse
YahyaChagri said:
S OFF
Do i really need to turn s off and rewrite the cid and mid or there is another way ??
Click to expand...
Click to collapse
Based on what you posted, the phone is already s-off.
However, the "large image" error is NOT a result of wrong MID/CID. It means something else is wrong. Are you using the SD card method to flash the RUU, or fastboot? If fastboot, what are the exact commands you are using?
Also, you do not need to change CID/MID if you are running the signed RUU intended for your specific model. There are many "Euro" versions of the M8. And not all of them will work with that particular RUU. In order to verify whether the RUU is correct or not, we need more info. Do fastboot getvar all, and post the results (delete IMEI and serial number before posting).
---------- Post added at 09:20 AM ---------- Previous post was at 09:18 AM ----------
brodude said:
Try this method. I just reverted back to stock tonight and I'm now completing my OTAs. Seems to be working just fine for now. Make sure you follow each and every steps. Make sure you choose the version with good CID and MID.
https://forum.xda-developers.com/htc-one-m8/help/tutorial-how-to-stock-stock-twrp-t3086860
Click to expand...
Click to collapse
This method is certainly valid. Although requires more steps than running RUU. If in fact, the OP has the correct RUU for his version.