Hi All,
Is it just me, or does anybody else agree that someone somewhere should post a nice, easy to read RUU guide with screenshots that mean something.
I've always looked for a good guide with easy to use screenshots that ACTUALLY EXPLAINS the process of choosing the correct RUU, what you should look at and why.
Yes I know theres a couple of guides on it, but non of them explain how to pick the correct RUU for your device, and why that RUU is the right one.
Most of the time, I leave the RUU Guide threads knowing as little as I knew about RUU's to start with.
There is actually 1 rule to find the correct ruu.
Fastboot getvar version-main
That command tells the number of the ruu you need as a minimal number to start with. And in our case it has to start with endevouru because it's the codename for our hox.
So if your number is 3.14.401.31 you need a ruu that matches that exactly.
You can however flash different ruu's but it has to have a higher number. For example :
2.17.401 = main number, that number can go a step forward and flash the 3.14.401 ruu.
Obviously you can only downgrade with a ruu if you have s-off. So someone who is on 3.14.401 and a s-on device can not install the 2.17 ruu because it tries to downgrade the bootloader.
Hope this answers your question a little bit.
Cheers.
Sent from my HTC One X using XDA Premium 4 mobile app
Mr Hofs said:
There is actually 1 rule to find the correct ruu.
Fastboot getvar version-main
That command tells the number of the ruu you need as a minimal number to start with. And in our case it has to start with endevouru because it's the codename for our hox.
So if your number is 3.14.401.31 you need a ruu that matches that exactly.
You can however flash different ruu's but it has to have a higher number. For example :
2.17.401 = main number, that number can go a step forward and flash the 3.14.401 ruu.
Obviously you can only downgrade with a ruu if you have s-off. So someone who is on 3.14.401 and a s-on device can not install the 2.17 ruu because it tries to downgrade the bootloader.
Hope this answers your question a little bit.
Cheers.
Sent from my HTC One X using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Cheers Hofs
Don't think theres an RUU for my version then :/
Mr hofs?
I have a couple questions my self.
Correct me if I am wrong please.
1. RUU's Come in 2 forms and EXE and ZIP format
2. EXE will be a windows Executable RUU from HTC for a specific model and variant of a htc device.
3. Zip Format is for use in Fastboot to restore to stock for a specific model and variant of a htc device.
Furthermore I have these questions.
Are there Encrypted and Decrypted RUU's - If so What is the difference?
Will flashing a RUU regardless of Encrypted or Decrypted result in S-ON after it successfully completes?
Thanks,
---------- Post added at 02:14 PM ---------- Previous post was at 02:13 PM ----------
Mr Hofs said:
There is actually 1 rule to find the correct ruu.
Fastboot getvar version-main
That command tells the number of the ruu you need as a minimal number to start with. And in our case it has to start with endevouru because it's the codename for our hox.
So if your number is 3.14.401.31 you need a ruu that matches that exactly.
You can however flash different ruu's but it has to have a higher number. For example :
2.17.401 = main number, that number can go a step forward and flash the 3.14.401 ruu.
Obviously you can only downgrade with a ruu if you have s-off. So someone who is on 3.14.401 and a s-on device can not install the 2.17 ruu because it tries to downgrade the bootloader.
Hope this answers your question a little bit.
Cheers.
Sent from my HTC One X using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Very useful..
DeadPhoenix said:
Mr hofs?
I have a couple questions my self.
Correct me if I am wrong please.
1. RUU's Come in 2 forms and EXE and ZIP format
2. EXE will be a windows Executable RUU from HTC for a specific model and variant of a htc device.
3. Zip Format is for use in Fastboot to restore to stock for a specific model and variant of a htc device.
Furthermore I have these questions.
Are there Encrypted and Decrypted RUU's - If so What is the difference?
Will flashing a RUU regardless of Encrypted or Decrypted result in S-ON after it successfully completes?
Thanks,
---------- Post added at 02:14 PM ---------- Previous post was at 02:13 PM ----------
Very useful..
Click to expand...
Click to collapse
1: for hox at least only .exe format.
2: correct
3: i never seen a zip ruu for the hox
4: ruu's are encrypted (maybe some older ones not)
5: if you have s-off a ruu will not make you s-on (most of us users are s-on already anyway)
Cheers.
Mr Hofs said:
1: for hox at least only .exe format.
2: correct
3: i never seen a zip ruu for the hox
4: ruu's are encrypted (maybe some older ones not)
5: if you have s-off a ruu will not make you s-on (most of us users are s-on already anyway)
Cheers.
Click to expand...
Click to collapse
I am asking for the HTC One Max(hom) forums. We are getting conflicting answers about S-ON after a Encrypted or decrypted RUU is run. We appear to have a decrypted version for Verizon in our forums.
We wanted to get some definitive answers for a help thread I started.
Ah, can't say this about another device. I only know these things count for the hox....
Related
hi , just got my phone from ebay and its a superCID one so it seem it cant find any ota , can anyone point me to the most recent RUU ?
or if anyone does have it on his disk can he upload that RUU on dropbox ? thanks in advance
Before anyone can suggest the latest of RUU for you, you need to give more details especially what your current software version no. is ... maybe you have the latest one that is why no OTA update for your device.
ckpv5 said:
Before anyone can suggest the latest of RUU for you, you need to give more details especially what your current software version no. is ... maybe you have the latest one that is why no OTA update for your device.
Click to expand...
Click to collapse
it is a demo unit , in a white box , it has superCID and S-ON , the version is 1.46.401.1
Never see a RUU with that no.
Make sure you take care of it, it is not easy to find RUU now as HTC is hunting down people who publish RUU at the moment. But still you can google for it, there are various site with RUUs.
I don't know much about SuperCID, previously you simply run any RUU to your device when you have a SuperCID.
What I understand now is that you need to change the CID to the RUU that you want to flash.
For example, you want to flash an Asia_WWE RUU, you need to change your CID from 111111 to HTC__044 then you can run *.*.707.* RUU. Then again say you want to flash a EU_WWE, you need to change the CID to HTC__001 first then only run the *.**.401.*
BTW, the latest for .401 is 2.22.401.1
HTCRUU has been taken down for now, due to HTC...right now there are NO ruu's to download unless someone has them somewhere
ckpv5 said:
Never see a RUU with that no.
Make sure you take care of it, it is not easy to find RUU now as HTC is hunting down people who publish RUU at the moment. But still you can google for it, there are various site with RUUs.
I don't know much about SuperCID, previously you simply run any RUU to your device when you have a SuperCID.
What I understand now is that you need to change the CID to the RUU that you want to flash.
For example, you want to flash an Asia_WWE RUU, you need to change your CID from 111111 to HTC__044 then you can run *.*.707.* RUU. Then again say you want to flash a EU_WWE, you need to change the CID to HTC__001 first then only run the *.**.401.*
BTW, the latest for .401 is 2.22.401.1
Click to expand...
Click to collapse
thanks a lot mate , i've been able to download the 2.22.401.1 RUU from a chinese site and succesfully flashed with phone in fastboot mode
stesa said:
thanks a lot mate , i've been able to download the 2.22.401.1 RUU from a chinese site and succesfully flashed with phone in fastboot mode
Click to expand...
Click to collapse
:good::good:
Hi guys.Im new to HTC one X.I just bought an HTC one X from e-bay and it came pre rooted thought the phone looks brandnew.I tried to insert a sim and my phone keeps on showing an error saying process.com.android.phone is stopped and it does not show any signal bars.After several reboots sometimes signal bars do appear sometimes.But i am unable to make or recieve calls as my phone app keeps on force closing. My phone has stock ICS.
So if i flash a stock RUU will the problem be solved or is there anything that i can do to make my phone work?thank you.
I would recommend flashing a stock RUU.
You would need to check your CID and whether your bootloader is locked or unlocked. To do this, you can hold power+volume up down buttons to reboot phone to bootloader and see the first line.
The RUU you flash must match your CID.
Recommended for you:
RUUs: http://forum.xda-developers.com/wiki/HTC_One_X#Total_recovery_-_flashing_a_RUU_to_completely_restore_your_phone
About CID and other info: http://forum.xda-developers.com/showthread.php?t=2031359
Power button + volume down button (not up)
And post the outcome of this fastboot command
Fastboot getvar version-main
Tony Tan said:
I would recommend flashing a stock RUU.
You would need to check your CID and whether your bootloader is locked or unlocked. To do this, you can hold power+volume up down buttons to reboot phone to bootloader and see the first line.
The RUU you flash must match your CID.
Recommended for you:
RUUs: http://forum.xda-developers.com/wiki/HTC_One_X#Total_recovery_-_flashing_a_RUU_to_completely_restore_your_phone
About CID and other info: http://forum.xda-developers.com/showthread.php?t=2031359
Click to expand...
Click to collapse
Thanks for the help(i hit the thanks button too
one more question.Mine has got super CID.
So what RUU should i flash?
You mean Super CID 11111111?
Did you check with:
fastboot getvar cid
fastboot oem readcid
If my understanding is correct, you should be able to flash any RUU with any CID in that case.
Just make sure the RUU you are flashing is for your device model (HTC One X Endeavor, not HTC One XL or anything else)
I have never owned a supercid device though, so you might want to confirm with someone else.
For RUU downloads:
http://forum.xda-developers.com/showthread.php?t=2094113
http://forum.xda-developers.com/showthread.php?t=2189048
Credits to Mr Hofs for helping me find the links.
nuwanmw1988 said:
Thanks for the help(i hit the thanks button too
one more question.Mine has got super CID.
So what RUU should i flash?
Click to expand...
Click to collapse
Tony Tan said:
You mean Super CID 111111111?
Did you check with:
fastboot getvar cid
fastboot oem readcid
If my understanding is correct, you should be able to flash any RUU with any CID in that case.
Just make sure the RUU you are flashing is for your device model (HTC One X Endeavor, not HTC One XL or anything else)
I have never owned a supercid device though, so you might want to confirm with someone else.
For RUU downloads:
http://forum.xda-developers.com/showthread.php?t=2094113
http://forum.xda-developers.com/showthread.php?t=2189048
Credits to Mr Hofs for helping me find the links.
Click to expand...
Click to collapse
yup..its 11111111
Then you can flash any ruu basically !
Thanx guys..my phone is back to life now.
Sent from my HTC One X using xda premium
Hello guys,
Been wondering for a while how people find the right RUU.I know they use the command fastboot getvar version-main and that they get a couple of numbers out of that. I have heard that you need the same number ruu or higher than the number that pops out when doing that command is that right? And where do people get the ruu from?
Also, what is a CID? And last but not least: when flashing firmware you flash a custom bootloader am I right? Some roms require some kind of firmware and I do not understand the point of it yet. What if you want to get back to your original bootloader?
I tried using other threads but it is very unclear to me. I would really like to know how to get people the correct ruus so I can help myself and other people as well
Sent from my HTC One X using xda app-developers app
A ruu must indeed match the number that comes out of the fastboot command, it can't be lower because the ruu contains a lower hboot version. We need S-OFF to do that, and S-OFF is not available for our phones. Some have it but they are lucky.
A ruu may be higher as the number except for a lower hboot then 1.12 to 3.14. So when somebody is on software version 1.29 he can't run a 3.14 ruu. A 2.17 based ruu is a must before the 3.14 one ..... that is if they are available to begin with. Ruu's after 3.14 are rare. Some have been released but most are not.
CID is a customer ID, its a region code. My cid is HTC__E11 that means a dutch region. It also tells if a phone is carrier branded like vodaphone or O2
And about the firmware that can be flashed ......its a standalone firmware to upgrade the hboot to a JB one, that goes for every hboot version. So if you have 1.29 software version (hboot 0.95-0.96) then you can straight away flash it to 3.14 hboot 1.31-1.39. Not like the ruu where this is impossible to do.
Hope this explains some question marks ?
Links to ruu's :
http://forum.xda-developers.com/showthread.php?t=2189048
http://forum.xda-developers.com/showthread.php?t=2094113
Link to firmwares :
http://forum.xda-developers.com/showthread.php?t=1957376
And if a ruu is not available they need to return to stock with a stock nandroid backup. No other way to do it then !
Links to stock back-ups :
http://forum.xda-developers.com/showthread.php?t=1975140
http://forum.xda-developers.com/showthread.php?t=2189048
Cheers !
Mr Hofs
Thanks alot. Could you name a reason why someone would want to know his CID? Is that for firmware purposes? I'm on holiday now so I can't find my ruu. Once I get home ill try to find it on my own thanks for the info I understand much better now
Sent from my HTC One X using xda app-developers app
Well a cid is for me not so important, but the info listed in the threads sometimes go on cid first so its easier searching. The main version number tells me everything.
It gives me the info what hboot version, what software number and if its carrier branded ..... but that's also some experience i picked up lately
Edit :
Ow yeah sometimes carrier branded phones have the same cid but a different software version. Example :
1 cid has software 2.17.206 as number and the same cid has software 2.17.207 as version. So sometimes its good to know the cid too.
Mr Hofs said:
A ruu must indeed match the number that comes out of the fastboot command, it can't be lower because the ruu contains a lower hboot version. We need S-OFF to do that, and S-OFF is not available for our phones. Some have it but they are lucky.
A ruu may be higher as the number except for a lower hboot then 1.12 to 3.14. So when somebody is on software version 1.29 he can't run a 3.14 ruu. A 2.17 based ruu is a must before the 3.14 one ..... that is if they are available to begin with. Ruu's after 3.14 are rare. Some have been released but most are not.
CID is a customer ID, its a region code. My cid is HTC__E11 that means a dutch region. It also tells if a phone is carrier branded like vodaphone or O2
And about the firmware that can be flashed ......its a standalone firmware to upgrade the hboot to a JB one, that goes for every hboot version. So if you have 1.29 software version (hboot 0.95-0.96) then you can straight away flash it to 3.14 hboot 1.31-1.39. Not like the ruu where this is impossible to do.
Hope this explains some question marks ?
Links to ruu's :
http://forum.xda-developers.com/showthread.php?t=2189048
http://forum.xda-developers.com/showthread.php?t=2094113
Link to firmwares :
http://forum.xda-developers.com/showthread.php?t=1957376
And if a ruu is not available they need to return to stock with a stock nandroid backup. No other way to do it then !
Links to stock back-ups :
http://forum.xda-developers.com/showthread.php?t=1975140
http://forum.xda-developers.com/showthread.php?t=2189048
Cheers !
Mr Hofs
Click to expand...
Click to collapse
How do you know what software version you are running to begin with? I mean it doesnt add up. You can have a 1.29 bootloader but its hboot 0.95-0.96? That Part I don't get yet but the rest is clear ty
Edit: ah the software version is the oneu get from cmd and you find an ruu based on that and on your hboot version am I right?
Sent from my HTC One X using xda app-developers app
The 1.29, 2.17 and 3.14 number i mentioned are the rom software numbers and they are linked to hboot numbers like 0.95-0.96 and 2.17 is 1.12 and from 3.14 to 3.20 its 1.31-1.39
Thanks, will try to find my ruu if I'm home
Sent from my HTC One X using xda app-developers app
Hi there im new with htc phones i have buy htc one m8 and there was 4.4.3 android operating system when i buy there was unlocked bootloader but s-on and i have tryed install with twrp android 5.0.1 but its only boots once and bick after reboot so i wanna stock rom to use phone normal and all the rom's ruu dosn't installs i get error so can any one say what firmware version are for my htc ? here is bootloader info
imei:
imei2: Not Supported
meid: 00000000
product: m8_ul
platform: hTCB
modelid: 0P6B10000
cidnum: ORANGB10
battery-status:Good
battery-voltag
partition-layoout:Generic
security: on
build-mode: SH
boot-mode: FAS
commitno-bootl
hbootpreupdate
gencheckpt: 0
After Xperia phone this phone gives me to many questions about software ...
Ainster said:
was unlocked bootloader but s-on and i have tryed install with twrp android 5.0.1 but its only boots once and bick after reboot
Click to expand...
Click to collapse
You need to update your firmware to run Android 5.0 ROMs.
Ainster said:
all the rom's ruu dosn't installs i get error
Click to expand...
Click to collapse
What error number(s)?
You need to run the RUU that matches your CID and MID. It sounds like you may have tried more than one (and possibly RUUs not meant for your CID,MID).
Also, since you are s-on, you need to relock the bootloader to RUU. This is done with fastboot, using the command: fastboot oem lock
---------- Post added at 10:36 AM ---------- Previous post was at 10:34 AM ----------
Ainster said:
here is bootloader info
imei: Delete
imei2: Not Supported
meid: 00000000
product: m8_ul
platform: hTCB
modelid: 0P6B10000
cidnum: ORANGB10
battery-status:Good
battery-voltag
partition-layoout:Generic
security: on
build-mode: SH
boot-mode: FAS
commitno-bootl
hbootpreupdate
gencheckpt: 0
Click to expand...
Click to collapse
You left out much of the important getvar data, while leaving in something you should never post online (IMEI) since its personal data. I've notified the mods to delete your IMEI.
I have deleted imei i got error that ruu cant read bootloader if i remember 199 error and what kind of information you need to help me find what software match for my htc ? By the way i was tryed with locked bootloader still same error
Ainster said:
i got error that ruu cant read bootloader if i remember 199 error
Click to expand...
Click to collapse
Not familiar with that error. Are you sure that is what it says? You can run the RUU again to make sure.
Ainster said:
what kind of information you need to help me find what software match for my htc ?
Click to expand...
Click to collapse
hboot number
main version number
What RUUs you are trying.
redpoint73 said:
Not familiar with that error. Are you sure that is what it says? You can run the RUU again to make sure.
hboot number
main version number
What RUUs you are trying.
Click to expand...
Click to collapse
hboot - 3.16.0.0000
CID - ORANGB10
But no main versions its showing nothing i have tryed many off RUUs can you give me one RUU with ones you thin should work ill try and say all the errors if i get them .
Ainster said:
hboot - 3.16.0.0000
CID - ORANGB10
But no main versions its showing nothing i have tryed many off RUUs can you give me one RUU with ones you thin should work ill try and say all the errors if i get them .
Click to expand...
Click to collapse
I don't know if there is an RUU for your CID. I'm guessing no.
If that is the case, you can try to return to stock 4.4.2 ROM (for your CID) and stock recovery, OTA update all the way up to Lollipop (which will update the firmware). Then you can run the current custom ROMs.
redpoint73 said:
I don't know if there is an RUU for your CID. I'm guessing no.
If that is the case, you can try to return to stock 4.4.2 ROM (for your CID) and stock recovery, OTA update all the way up to Lollipop (which will update the firmware). Then you can run the current custom ROMs.
Click to expand...
Click to collapse
So i whould try the RUU of 4.4.2rom with this CID ? By the way did i need to find my cid rom becouse when i buy phone there was unoficial rom with sence ... And bootloader unlocked only this CID can match on my htc ?
Ainster said:
So i whould try the RUU of 4.4.2rom with this CID ? By the way did i need to find my cid rom becouse when i buy phone there was unoficial rom with sence ... And bootloader unlocked only this CID can match on my htc ?
Click to expand...
Click to collapse
You can flash most 4.4.2 ROMs (stock or custom), and it will at least get the running again.
If you can find an RUU for your CID, it doesn't matter which build. It will re-image all software and firmware. The only restriction is that you cannot go backwards ("downgrade") with s-on. Otherwise, you can RUU to 4.4.3, 4.4.4 or 5.0. But the RUU must match your CID and MID.
The only way to change CID and MID is with s-off. S-off is by sunshine, and requires a device that can boot into OS.
Ainster said:
hboot - 3.16.0.0000
CID - ORANGB10
But no main versions its showing nothing i have tryed many off RUUs can you give me one RUU with ones you thin should work ill try and say all the errors if i get them .
Click to expand...
Click to collapse
Try changing you CID. Just connect your device to a computer and open ADB. Boot your phone into fastboot (it should say "Fastboot USB"). Then copy paste:
fastboot oem writeCID T-MOB010
Sent from my HTC One_M8 using XDA Free mobile app
note_3_t-mo said:
Try changing you CID. Just connect your device to a computer and open ADB. Boot your phone into fastboot (it should say "Fastboot USB"). Then copy paste:
fastboot oem writeCID T-MOB010
Click to expand...
Click to collapse
You need s-off to change CID.
Tryed one got error 130 model id error so id dosn't match ... Maybe some one have ideas how to find RUU with same ID and CID ? Becouse HTC is hard to find Sony much easyer download xperia firm and choose any of words rom's on htc I dosn't think sometink like that program are ??? Or any other solutions maybe with out S-Off?
Ainster said:
Tryed one got error 130 model id error so id dosn't match ... Maybe some one have ideas how to find RUU with same ID and CID ?
Click to expand...
Click to collapse
It seems you are just running RUUs without much reason or methodology? Any saying "one" gave you an error without any info on which RUU doesn't tell us enough for us to help you properly.
The carrier name is usually indicated in the RUU file name, plus the build number is also indicated. For instance, it looks like ORANGB10 corresponds to software build numbers xx.xx.69 where the "69" is specific to your CID. Therefore, you want to be looking for an RUU with the build number xx.xx.69 in the filename, assuming such an RUU exists.
But honestly, I've searched around and don't seen any reference to an RUU for ORANGB10, so I'm inclined to believe you are looking for something that doesn't exist.
Ainster said:
Or any other solutions maybe with out S-Off?
Click to expand...
Click to collapse
I've already given you 2 solutions that will work with s-on:
1) Flash a stock or custom ROM with Android 4.4.2 base, using TWRP. This will at least get the phone bootable again. The firmware will still be outdated, and you won't be able to run any current ROMs. But at least the phone will work.
2) Revert to the stock nandroid backup you made before flashing any ROMs, if you made one (and you really always should before flashing any ROMs on any Android device). From there, return to stock recovery, and you should be able to OTA update in order to update firmware.
Stock recovery files can be found here: http://forum.xda-developers.com/showthread.php?t=2701376&highlight=orangb10
Note that if the exact stock recovery for your main/build version is not available, the recovery for the same "base" should work (as noted in Post #3 of the above linked thread). Example, if your stock main version is 1.54.69, than any stock recovery corresponding to build 1.54.xx should work.
3) If you didn't make a nandroid backup, you can try to find the stock nandroid for your CID. You will want the stock nandroid that corresponds to your present main version, which you say is not listed (common TWRP bug) but based on your hboot number (3.16) your main version is proabably 1.xx
I don't see a stock nandroid posted for your CID on the following threads. So you may post to one of those threads, and see if someone can post a nandroid for you:
http://forum.xda-developers.com/showthread.php?t=2701376&highlight=orangb10
http://forum.xda-developers.com/htc-one-m8/help/tutorial-how-to-stock-stock-twrp-t3086860
The goal here is to get back to the stock ROM (and the build number that corresponds to your firmware) and stock recovery, same as Method 2 above. Then OTA up to Lollipop in order to update firmware.
4) Get the phone running again, per Method 1 above. Then run sunshine to S-off. Once you have s-off you can "manually" update the firmware. It seems you want to avoid paying for sunshine. But if none of the above methods are satisfactory, this may be your last option.
redpoint73 said:
It seems you are just running RUUs without much reason or methodology? Any saying "one" gave you an error without any info on which RUU doesn't tell us enough for us to help you properly.
The carrier name is usually indicated in the RUU file name, plus the build number is also indicated. For instance, it looks like ORANGB10 corresponds to software build numbers xx.xx.69 where the "69" is specific to your CID. Therefore, you want to be looking for an RUU with the build number xx.xx.69 in the filename, assuming such an RUU exists.
But honestly, I've searched around and don't seen any reference to an RUU for ORANGB10, so I'm inclined to believe you are looking for something that doesn't exist.
I've already given you 2 solutions that will work with s-on:
1) Flash a stock or custom ROM with Android 4.4.2 base, using TWRP. This will at least get the phone bootable again. The firmware will still be outdated, and you won't be able to run any current ROMs. But at least the phone will work.
2) Revert to the stock nandroid backup you made before flashing any ROMs, if you made one (and you really always should before flashing any ROMs on any Android device). From there, return to stock recovery, and you should be able to OTA update in order to update firmware.
Stock recovery files can be found here: http://forum.xda-developers.com/showthread.php?t=2701376&highlight=orangb10
Note that if the exact stock recovery for your main/build version is not available, the recovery for the same "base" should work (as noted in Post #3 of the above linked thread). Example, if your stock main version is 1.54.69, than any stock recovery corresponding to build 1.54.xx should work.
3) If you didn't make a nandroid backup, you can try to find the stock nandroid for your CID. You will want the stock nandroid that corresponds to your present main version, which you say is not listed (common TWRP bug) but based on your hboot number (3.16) your main version is proabably 1.xx
I don't see a stock nandroid posted for your CID on the following threads. So you may post to one of those threads, and see if someone can post a nandroid for you:
http://forum.xda-developers.com/showthread.php?t=2701376&highlight=orangb10
http://forum.xda-developers.com/htc-one-m8/help/tutorial-how-to-stock-stock-twrp-t3086860
The goal here is to get back to the stock ROM (and the build number that corresponds to your firmware) and stock recovery, same as Method 2 above. Then OTA up to Lollipop in order to update firmware.
4) Get the phone running again, per Method 1 above. Then run sunshine to S-off. Once you have s-off you can "manually" update the firmware. It seems you want to avoid paying for sunshine. But if none of the above methods are satisfactory, this may be your last option.
Click to expand...
Click to collapse
The reasion why im not takes backup of my stock androdi that there was other android system not stock this is freands phone hes buy it in shop but when he buy it phone was unlocked and with other wersion of android not stock one and thet was 4.4.3 android with ones dosn't get updates by default and google play dosn't connect to servers .
Yes searching for that RUU is hard no probliem i have installed 4.4.2 with recovery good thing phone works.
I read about sunshine its easyest way when s-off but there is another probliems thanks for help ill check all the things what you writted me .
Ainster said:
The reasion why im not takes backup of my stock androdi that there was other android system not stock this is freands phone hes buy it in shop but when he buy it phone was unlocked and with other wersion of android not stock one and thet was 4.4.3 android with ones dosn't get updates by default and google play dosn't connect to servers .
Yes searching for that RUU is hard no probliem i have installed 4.4.2 with recovery good thing phone works.
I read about sunshine its easyest way when s-off but there is another probliems thanks for help ill check all the things what you writted me .
Click to expand...
Click to collapse
You can start with 1.54.69.5 backup.
Then do multiple OTA 1.54.69.5 --> 1.70.69.2 --> 2.26.69.1 --> 3.33.69.1 --> 4.19.69.3
Don't have time to upload my TWRP backups but you can get a Philz recovery backup here (belongs to someone else) - https://drive.google.com/file/d/0BxUEBSB4XdsRa3RoS3JBVjVQREk/edit
Please note you need Philz recovery installed then restore the backup which already include a stock recovery in it. Restore (select all) then do OTA.
After relocking the bootloader, my phone is doesn't boot to system it just shows the htc logo and goes straight into bootloader.
Here is the info that it shows:
***Software status: Modified***
*** RELOCKED***
***Security Warning ***
M8_UL_CA PVT SHIP S-ON
HBOOT-3.19.0.000
RADIO-1.24.21331147A1.09G
OpenDSP-v62.2.2-00593-M8974_HM.1118
OS-4.16.1540.8
HBOOT
RAMDUMP
REBOOT
REBOOT FASTBOOT
POWER DOWN
I saw it on this thread that I can download an run RUU to fix this, and I've download this file for my AT&T M8. My question is, will it be all right to run this? I'm just making sure as I don't wanna brick my device. And if this not the way to go, can anyone help me in any way? Any help would be great.
gamesprin said:
After relocking the bootloader, my phone is doesn't boot to system it just shows the htc logo and goes straight into bootloader.
Here is the info that it shows:
***Software status: Modified***
*** RELOCKED***
***Security Warning ***
M8_UL_CA PVT SHIP S-ON
HBOOT-3.19.0.000
RADIO-1.24.21331147A1.09G
OpenDSP-v62.2.2-00593-M8974_HM.1118
OS-4.16.1540.8
HBOOT
RAMDUMP
REBOOT
REBOOT FASTBOOT
POWER DOWN
I saw it on this thread that I can download an run RUU to fix this, and I've download this file for my AT&T M8. My question is, will it be all right to run this? I'm just making sure as I don't wanna brick my device. And if this not the way to go, can anyone help me in any way? Any help would be great.
Click to expand...
Click to collapse
That's the wrong RUU. You need this one.
1. But my HTC One M8 is AT&T, don't I need one for that?
2. Will it be all right if I do this? Will I brick my phone or damage the software in any way?
gamesprin said:
1. But my HTC One M8 is AT&T, don't I need one for that?
2. Will it be all right if I do this? Will I brick my phone or damage the software in any way?
Click to expand...
Click to collapse
You have the Developers Edition model of the M8, which was sold by AT&T. You can tell that from your firmware version (OS) in your bootloader readout.
Regular AT&T models will show the firmware version being x.xx.502.x
Dev Ed model will show x.xx.1540.x
You won't damage your phone, but you might have to flash the firmware first before running the RUU if it fails. I'm not sure where to find a signed firmware (you need signed if S-On) but you could search for it.
Try running the RUU first to see if it works. You won't brick, you'll just get an error and the installation will abort if it won't work (if you need to flash the firmware first).
You could also try out the methods in this thread to return to stock ROM and recovery, and update via the official OTA.
Okay, thank you very much.
I'll try the RUU first and see what happens. Thanks again.
xunholyx said:
......I'm not sure where to find a signed firmware (you need signed if S-On) but you could search for it.
Click to expand...
Click to collapse
Post #5 in my backup thread is MM signed firmware collection.
ckpv5 said:
Post #5 in my backup thread is MM signed firmware collection.
Click to expand...
Click to collapse
Cool! I haven't been in your OP for a while now. Very nice addition.
Hey, I got a 155 error saying RUU can't update my phone, I need to download the proper RUU. Please help me. I'm freaking out.
EDIT: I found this from this site, saying that 617 has replaced 1540 after the M9, maybe i need to download another RUU?
gamesprin said:
Hey, I got a 155 error saying RUU can't update my phone, I need to download the proper RUU. Please help me. I'm freaking out.
Click to expand...
Click to collapse
Crap! I forgot to tell you that since you are S-On you will need to relock your bootloader first
In fastboot: fastboot oem lock then run the RUU again
xunholyx said:
Crap! I forgot to tell you that since you are S-On you will need to relock your bootloader first
In fastboot: fastboot oem lock then run the RUU again
Click to expand...
Click to collapse
Did it. says 'bootloader already locked". Sorry for not including this info in the previous reply.
i guess, this has made s-on after flashing wrong firmware. (MID has changed or has flashed modified firmware; you or someone else). you have to s-off again to flash ruu.
post a fastboot getvar all without S/N & IMEI to see exactly what has happened.
gamesprin said:
I found this from this site, saying that 617 has replaced 1540 after the M9, maybe i need to download another RUU?
Click to expand...
Click to collapse
This is for the M9 and devices made after (M10). This doesn't apply to the M8.
The RUU linked by xunholyx is the right one.
Did you try to flash the stock firmware (6.12.1540.4) then the RUU, as already advised?
---------- Post added at 01:16 PM ---------- Previous post was at 01:12 PM ----------
gamesprin said:
1. But my HTC One M8 is AT&T, don't I need one for that?
Click to expand...
Click to collapse
How do you know its the AT&T version? Does it have the AT&T "globe" logo on back cover?
If so, it was probably s-off at one time, than had its CID changed, and RUU flashed to "convert" it to US Developer's Edition software.
You need to flash the RUU that matches the current CID, it doesn't matter what it was "originally". And most folks won't want the AT&T bloat and limitations, anyway.
After getting the error, I flashed the firmware mentioned here.
After that the RUU ran flawlessly.