Hello,
So i wanted to uptade my htc m9u to 7 nougat. i unlocked my bootloader then i flashed twrp recovery and installed root, but when i tried to reboot it remains stuck on loop with logo screen and the red text under it...what can i do?
i found some useful files here: androidfilehost.com/?w=search&s=3.36.709.3&type=files
this is the file that passed the loop: boot_3.36.709.3_root.img....but now my touchscreen is not working at all...
please help...
thanks...
Are you aware that only certain versions of twrp work with certain firmwares.
You need to try to return your phone to its stock state. See flippy's or sneakyghosts threads for help before you completely knacker your phone.
Beamed in by telepathy.
I did not know that only certain version of twrp work with my firmware....
I found a stock recovery for my version i flashed it but it is still looping bootscreen...
In the bootloader it says. Unlocked s-on software status:modified
That may be because you flashed all sorts.. As I already said, you need to go back to stock state with the proper ruu for your phone otherwise you dont know what is stopping the phone from booting so it'll stay like that.
Most likely you've flashed a firmware for the wrong device and that'll be it, dead phone.
As far as I know, you can't flash standard m9 firmware on an m9u.
Beamed in by telepathy.
Ok...but i flashed one stock that paseed the bootloader but the touch is not working...what can i do?
That means that i have a bricked phone ...it cant be undone?
shivadow said:
As far as I know, you can't flash standard m9 firmware on an m9u.
Click to expand...
Click to collapse
Not sure how you define "standard" but the M9u is a overall name for the GSM M9 that doesn't distinguish between hima_ul and hima_uhl. The version with SKU 709 is the same as the 401 one if you look at the hardware.
@Tymmybike: As already mentioned by shivadow, read my thread (and flash a RUU).
However, I don't know what you've been doing there or why you've been doing it. If you want to update your phone's firmware you just need to use the software update function of the stock rom. Flashing TWRP and rooting your phone doesn't make any sense at all since they can break the OTA function if not used correctly due to the block-based OTAs that google introduced with android 5.
And just for the record: The bootloop probably got caused by flashing an incompatible SuperSU version. You wouldn't be the first who did that mistake.
Sent from my HTC One M9 using XDA Labs
I made that mistake too.. I make a lot of mistakes.. Dont know if you noticed.. Its quite difficult..
Beamed in by telepathy.
Flippy498 said:
Not sure how you define "standard" but the M9u is a overall name for the GSM M9 that doesn't distinguish between hima_ul and hima_uhl. The version with SKU 709 is the same as the 401 one if you look at the hardware.
@Tymmybike: As already mentioned by shivadow, read my thread (and flash a RUU).
However, I don't know what you've been doing there or why you've been doing it. If you want to update your phone's firmware you just need to use the software update function of the stock rom. Flashing TWRP and rooting your phone doesn't make any sense at all since they can break the OTA function if not used correctly due to the block-based OTAs that google introduced with android 5.
And just for the record: The bootloop probably got caused by flashing an incompatible SuperSU version. You wouldn't be the first who did that mistake.
Sent from my HTC One M9 using XDA Labs
Click to expand...
Click to collapse
I can't find the correct RUU for my model:
kernel: lk
product: htc_himauhl
version: 1.0
version-main: 3.36.709.3
boot-mode: download
version-baseband: 01.01_U11440792_97.00.51203G_F
version-bootloader: 1.0.0.0000
mid: 0PJA10000
cid: HTC__032
i tried from sku 709 and says didn't match cid, also the one in 401 is not working either...
what can i do?
Flippy498 i wanted to uptade normally but it said: your phone is not using a stock rom or sometging like that.
Tymmybike said:
I can't find the correct RUU for my model
version-main: 3.36.709.3
mid: 0PJA10000
cid: HTC__032
i tried from sku 709 and says didn't match cid, also the one in 401 is not working either...
what can i do?
Flippy498 i wanted to uptade normally but it said: your phone is not using a stock rom or sometging like that.
Click to expand...
Click to collapse
That doesn't surprise me if I look at the data you gave me. (For your own safety: remove your IMEI from your post, btw.) Your CID doesn't belong to your SKU. Is the phone S-OFF? I guess you bought it second hand since it looks like the previous owner borked it. However, the problem should be fixable.
What do you mean with you tried "the one" 401 RUU. There are 7 different 401 RUUs in the ReadMe thread. Try to flash the 3.x one. If that isn't possible and if the phone isn't S-OFF then you'll need to use sunshine for getting S-OFF and being able to fix the phone. If you're lucky and the previous owner used sunshine, as well, then you won't have to pay, again.
Sent from my HTC One M9 using XDA Labs
Flippy498 said:
That doesn't surprise me if I look at the data you gave me. (For your own safety: remove your IMEI from your post, btw.) Your CID doesn't belong to your SKU. Is the phone S-OFF? I guess you bought it second hand since it looks like the previous owner borked it. However, the problem should be fixable.
What do you mean with you tried "the one" 401 RUU. There are 7 different 401 RUUs in the ReadMe thread. Try to flash the 3.x one. If that isn't possible and if the phone isn't S-OFF then you'll need to use sunshine for getting S-OFF and being able to fix the phone. If you're lucky and the previous owner used sunshine, as well, then you won't have to pay, again.
Sent from my HTC One M9 using XDA Labs
Click to expand...
Click to collapse
i tried to flash the 3.35.401.12 and it's not working...
for what and why i have to pay?
how do i install sunshine? because i saw it's a .apk
"Doesn't work" can mean anything. What's the exact error message?
Sunshine gets installed like any other apk. Open the file with a file explorer on your phone and let android install the app. It's a paid app. That's why I said you might need to pay. However, that might be unnecessary if your phone already is S-OFF.
Flippy498 said:
Well, it would help if you would use the correct RUU for your firmware and not just a random one...
Sunshine is a paid app.
Sent from my HTC One M9 using XDA Labs
Click to expand...
Click to collapse
i tried to install 3.36.709.3 but is not working because it has the wrong cid, like you said i think the previous owner messed it up.
i downloaded form the sunshine website the latest apk(when do i have to pay), sorry but i dont't understand...how can i install the apk if my phone is not booting?
sorry if i am annoing but i can't seem to understand...
Tymmybike said:
i tried to install 3.36.709.3 but is not working because it has the wrong cid, like you said i think the previous owner messed it up.
Click to expand...
Click to collapse
Yeah, I know. I edited my last post. I confused this thread with another one I'm currently writing in. Sorry. If the phone isn't booting then you aren't able to install/use sunshine.
Edit: Didn't you say earlier that you got out of the bootloop? Is your bootloader still unlocked? Is TWRP still installed? If the last two questions can be answered with yes you could restore the stock backup that corresponds your current firmware via TWRP. This would at least solve the bootloop problem. If needed, you could then use the sunshine app to set the phone S-OFF.
Flippy498 said:
Yeah, I know. I edited my last post. I confused this thread with another one I'm currently writing in. Sorry. If the phone isn't booting then you aren't able to install/use sunshine.
Click to expand...
Click to collapse
well when i installed the 3.35.401.32 from cid: HTC__032 it says: 19 RU_MAIN_VER_FAIL os-version in android-info missing or i
when i intsall the 3.36.709.3 from vid CID: HTC__621 it says: 7 RU_CID_FAIL cid in android-info mismatched
As far as I know there is no 3.35.401.32 RUU. I guess that's just a typo and you meant a 12 at the end, didn't you?
Is the phone S-ON or S-OFF? Depending on that answer we would need to set it S-OFF before we can continue (c.f. the edit of my last post)...
Flippy498 said:
As far as I know there is no 3.35.401.32 RUU. I guess that's just a typo and you meant a 12 at the end, didn't you?
Is the phone S-ON or S-OFF? Depending on that answer we would need to set it S-OFF before we can continue (c.f. the edit of my last post)...
Click to expand...
Click to collapse
yeah it wa a typo i meant 12
the phone is s-on
i got out of bootloop if i flashed boot_3.36.709.3_root.img but the touchscreen is not working at all....
the bootloader is unlocked and the twrp is still installed(i installed it now)....
Alright. Then restore the backup that corresponds to your current firmware version. Files and instructions are located in the ReadMe thread. After that you need to install the sunshine app and get S-OFF. Then you need to follow the conversion guide in the ReadMe thread. Choose the CID and the RUU according to the firmware that you actually want to use. If you want to use the 401 firmware then please try HTC__001 instead of the CID that your phone is using at the moment. After that your phone should be fixed.
Sent from my HTC One M9 using XDA Labs
Related
Hey all,
I got in a sticky situation. I am trying to flash on Cyanogenmod and it is proved to be difficult.
Right now, I am relocked, with S-OFF, Hboot, 2.14 and version 3.18.502.6.
I used to be HTC__001, then I used the tool kit to root and achieve CID 11111111. However, I wasn't able to flash Cyanmod because I wasn't a high enough HBOOT. So I used another toolkit to flash a higher HBOOT, well that flashed on the HTC__621 and really F'd stuff up.
Eventually I recovered and I was able to boot in my rom, but now I am looking to get to a point where I can flash Cyanogenmod.
I assume I have to go through htcdev again to get new unlock bins because I am on a new cid? Could I simply try flashing the stock RUU for Evita (I assume it is Evita because it is the ATT version of the HTC One x?)
Any help would be greatly appreciate as this situation is beyond anything I can find help with on the forums.
Cheers!
Technically, my phone is a HTC__001, but it says HTC__621.
Is it possible to use this RUU since I am S-Off?
RUU_Evita_UL_ATT_US_1.44.502.1_Radio_0.15.3201.09_release_249105.EXE?
weenrock said:
Technically, my phone is a HTC__001, but it says HTC__621.
Is it possible to use this RUU since I am S-Off?
RUU_Evita_UL_ATT_US_1.44.502.1_Radio_0.15.3201.09_release_249105.EXE?
Click to expand...
Click to collapse
I tried flashing the above RUU, but I got error 131: CUSTOMER ID ERROR. I assume because I am CID HTC__621... Anyway I can change this back to HTC__001?
Cheers!
Wrong forum, this is the international hox forum. Not the evita (at&t) hox XL forum.
Mr Hofs said:
Wrong forum, this is the international hox forum. Not the evita (at&t) hox XL forum.
Click to expand...
Click to collapse
Doh. Confusing. Sorry mate.
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.
Hello to everyone!
I have HTC M8(second hand...) I check the IMEI and i see is from Australia - Sold to Singapore. I don't know if it means something.
It was unlocked bootloader and modified software(Custom ROM-android 6), S-OFF and CID was 11111111(I don't know what was the original CID, because this is how i bought the phone)
I decided to get it back to stock. I found a few threads about how to get the HTC M8 fully stock, but nothing works for now. l have the the stock recovery, stock boot.img and locked the bootloader.
When i installed/restored from the RUU file it was ok. When i check for updates it's downloading, but cannot install.
There is a message:
'Variant system version - We have determined that your phone may be running a modified version of its system software. For your protection, we cannot update your phone. Please revert your phone to the official HTC system software to update your phone. If you did not modify your system software or would like help reverting your system please contact us via the support section at HTC - Mobile Phones, Smartphones, Cell Phones, Tablets'
I'm sure i have official software, stock recovery and boot.img, but i have no idea why this message appears.
Right now i am using InsertCoin ROM and i have noticed the message, that tells "Software status: Modified or Official" Mine tells always OFFICIAL. No matter if i have installed insertcoin or stock rom.
Here is the infor from my bootloader:
***Software status: Official*** (Just to remind... I'm with insertcoin rom)
***UNLOCKED***
M8_UL PVT SHIP S-OFF
CID - 11111111
HBOOT-3.19.0.0000
RADIO-1.25.214500021.06G
OpenDSP-v48.2.2-00564-M8974_FO.1211
OS-4.16.401.10
eMMC-boot 2048MB
Jan 15 2015, 22:51:08.0
Can anyone tell me how to download the official updates?
(sorry for my english)
No one can help with this ?
Jared89 said:
I decided to get it back to stock. I found a few threads about how to get the HTC M8 fully stock, but nothing works for now. l have the the stock recovery, stock boot.img and locked the bootloader.
Click to expand...
Click to collapse
None of that includes an actual stock ROM, which is required to OTA.
Jared89 said:
When i installed/restored from the RUU file it was ok. When i check for updates it's downloading, but cannot install.
Click to expand...
Click to collapse
You're sure the RUU installed correctly, with no errors?
Did you try to update immediately after RUU, with not mods at all (unlocking the bootloader, root, custom ROM)?
redpoint73 said:
None of that includes an actual stock ROM, which is required to OTA.
You're sure the RUU installed correctly, with no errors?
Did you try to update immediately after RUU, with not mods at all (unlocking the bootloader, root, custom ROM)?
Click to expand...
Click to collapse
Yes. I have no errors during the installing process and after that...
And yes... I try to update immediately after the phone boot to the home screen. I have no idea how to fix this. With my previous HTC M8 i was using the same custom rom(InsertCoin) and when i decidet to go back to stock, all i was doing is to lock the bootloader and install the RUU. Then i'm able to get the updates with no problems.
Jared89 said:
when i decidet to go back to stock, all i was doing is to lock the bootloader and install the RUU. Then i'm able to get the updates with no problems.
Click to expand...
Click to collapse
Yes, its strange. RUU by definition should put you on a fully stock image, and therefore allow OTA updates.
You can try to RUU straight to 6.12.401: http://forum.xda-developers.com/showpost.php?p=64926626&postcount=6
Curious to see if you get the same error with that RUU.
redpoint73 said:
Yes, its strange. RUU by definition should put you on a fully stock image, and therefore allow OTA updates.
You can try to RUU straight to 6.12.401: http://forum.xda-developers.com/showpost.php?p=64926626&postcount=6
Curious to see if you get the same error with that RUU.
Click to expand...
Click to collapse
I was trying this a few times. It says there is not enough space or something. C
I'm still looking for solution. Any suggestion is welcome!
Are you still S-OFF? On the M9 one hast to change the CID from SuperCID (11111111) back to a WWE CID to take the update to MM, as HTC uses a new routine to check the state of the phone.
In your case you'd have to reboot to fastboot mode, open a command prompt and change the CID to HTC__001 (8 digits!!) by using the command "fastboot oem writecid HTC__001"
Send by the swarm intelligence of my coffee machine ?.
Yes, i'm still S-OFF.
Thanks! I will try it and i will let you know if it works.
HTCNerdYoda said:
Are you still S-OFF? On the M9 one hast to change the CID from SuperCID (11111111) back to a WWE CID to take the update to MM, as HTC uses a new routine to check the state of the phone.
In your case you'd have to reboot to fastboot mode, open a command prompt and change the CID to HTC__001 (8 digits!!) by using the command "fastboot oem writecid HTC__001"
Send by the swarm intelligence of my coffee machine .
Click to expand...
Click to collapse
I just try your method, but when i try to get it back to stock with RUU.exe i get Error 130, which means is a wrong device. I gues i will have to get back the super CID?
Jared89 said:
I just try your method, but when i try to get it back to stock with RUU.exe i get Error 130, which means is a wrong device. I gues i will have to get back the super CID?
Click to expand...
Click to collapse
Which RUU are you using? In case of an x.xx.401.x RUU it is indeed WWE. Thus the CID should be HTC__001 or HTC__102.
maybe you should tray to RUU with the later one and if it doesn't work go back to SuperCID.
Send by the swarm intelligence of my coffee machine ?.
HTCNerdYoda said:
Which RUU are you using? In case of an x.xx.401.x RUU it is indeed WWE. Thus the CID should be HTC__001 or HTC__102.
maybe you should tray to RUU with the later one and if it doesn't work go back to SuperCID.
Send by the swarm intelligence of my coffee machine .
Click to expand...
Click to collapse
4.16.401.10 Europe.
I can't use the latest RUU, because is only on ZIP file. When i try to install it with fastboot it says there is no space or something.
You could rename the RUU zip to 0P6BIMG.zip and copy it to the root direction of a - at max - 32GB microSD card that has been formatted to fat32.
Insert this SD into your M8 and reboot to bootloader. It will then recognize the RUU and start to flash it automatically.
After a full flash you got to take the SD Card out again, to prevent it to start again during the next reboot
Send by the swarm intelligence of my coffee machine ?.
HTCNerdYoda said:
You could rename the RUU zip to 0P6BIMG.zip and copy it to the root direction of a - at max - 32GB microSD card that has been formatted to fat32.
Insert this SD into your M8 and reboot to bootloader. It will then recognize the RUU and start to flash it automatically.
After a full flash you got to take the SD Card out again, to prevent it to start again during the next reboot
Send by the swarm intelligence of my coffee machine .
Click to expand...
Click to collapse
I'll try this later. Just flashed the RUU(4.16.401.10_Europe), but even with CID HTC__02 i get "Variant system version" message...
Jared89 said:
I'll try this later. Just flashed the RUU(4.16.401.10_Europe), but even with CID HTC__02 i get "Variant system version" message...
Click to expand...
Click to collapse
Sure you took HTC__02, as it hast to have 8 digits and thus HTC__102. In case it doesn't help return to SuperCID 11111111.
Send by the swarm intelligence of my coffee machine ?.
HTCNerdYoda said:
Sure you took HTC__02, as it hast to have 8 digits and thus HTC__102. In case it doesn't help return to SuperCID 11111111.
Send by the swarm intelligence of my coffee machine .
Click to expand...
Click to collapse
Nothing works for now. I bring it back to InsertCoin rom.
My phone is from Singapore, so i might need the correct RUU for it. I have no idea!
Jared89 said:
Nothing works for now. I bring it back to InsertCoin rom.
My phone is from Singapore, so i might need the correct RUU for it. I have no idea!
Click to expand...
Click to collapse
Your problem is not the SuperCID 11111111 but wrong MID for the ROM that you installed.
To run a EU RUU x.xx.401.x, the MID must be 0P6B10000
You said your device is from Singapore, most probably the MID is 0P6B11000 and that's the reason for your "Variant System Version" error.
You can check your current MID by running command fastboot getvar mid
And for S-Off, there is no need to relock bootloader for OTA or running a RUU.
ckpv5 said:
Your problem is not the SuperCID 11111111 but wrong MID for the ROM that you installed.
To run a EU RUU x.xx.401.x, the MID must be 0P6B10000
You said your device is from Singapore, most probably the MID is 0P6B11000 and that's the reason for your "Variant System Version" error.
You can check your current MID by running command fastboot getvar mid
And for S-Off, there is no need to relock bootloader for OTA or running a RUU.
Click to expand...
Click to collapse
Didn't think about that. MID is 0P6B11000, as you said. I have changed it to 0P6B10000. I'll try later if i get the updates. Thanks a lot for the info!
Ok, when i changed MID the problem was solved! Now i get all the updates! Thanks a lot!
I followed instructions from this post:
http://forum.xda-developers.com/showthread.php?t=2708581
Hey guys, I know there's a crazy amount of unrooting threads here and everywhere else on the internet, but the more I search the more confused I get. So here's my short situation and my few questions:
Got a T-mobile M8, rooted, S-On, Unlocked, Running S.ROM. I'm trying to do the Tmobile JUMP thing to get the new HTC 10, so I'm trying to unroot this as much as possible. I've found at least 7 different ways with different outcomes on how to do this, so here are my questions:
-I keep reading you can just flash the RUU with no other prerequisites and it'll take your phone back to stock (except for the "Relocked" status). Is this true?
-Follow up to previous question: has anyone had any experience with returning a Relocked phone to Tmobile for their JUMP plan? (Not warranty exchange, I feel they're more strict with that)
-Is the only way to change the Relocked status to Locked by going S-Off with Sunshine and doing all of the 8923479324 steps in order to erase all of the tampered flags?
-What is the BEST method with the BEST outcome to go back to full stock on the M8?
Thanks in advance!
TehAsher said:
-I keep reading you can just flash the RUU with no other prerequisites and it'll take your phone back to stock (except for the "Relocked" status). Is this true?
Click to expand...
Click to collapse
The statement "no other prerequisites" is not specific enough. If you mean stock ROM and/or stock recovery (which folks sometimes think is needed to RUU), its true that neither are needed in order to RUU.
There are however some prerequisites:
1) PC required. Win7 and USB 2.0 for the best compatibility with RUU.
2) RUU needs to be intended for your version (CID and MID)
3) RUU version needs to be greater or equal to main version on the phone (this requirement is bypassed with s-off)
4) Relocked or locked bootloaded (this requirement also bypassed with s-off)
TehAsher said:
-Is the only way to change the Relocked status to Locked by going S-Off with Sunshine and doing all of the 8923479324 steps in order to erase all of the tampered flags?
Click to expand...
Click to collapse
Correct.
TehAsher said:
-What is the BEST method with the BEST outcome to go back to full stock on the M8?
Click to expand...
Click to collapse
T-Mob is not my carrier, and I know nothing of their Jump program. But in most cases, the best bet with returning a phone is to RUU to stock, and make the bootloader LOCKED. Return to s-on (after s-off) is probably not needed.
Thanks for the info! I guess I'll be getting sunshine then and try to follow all of these guides. So if I S-off with sunshine, as long as I check my CID and MID (I got the RUU from the HTC website, but I'll double check it anyways), I can flash that and return to stock. And afterwards I can find a guide on how to reset the tampered flags and the Locked status?
TehAsher said:
And afterwards I can find a guide on how to reset the tampered flags and the Locked status?
Click to expand...
Click to collapse
Yes, that is what I would suggest. Guide on how to make it LOCKED and remove TAMPERED:
http://forum.xda-developers.com/showthread.php?t=2708571
How I went back to stock
I was rooted and running custom ROMS, but when MM came out I wanted to make sure that my firmware/radio was updated. So for me this is what I did
- first I am s-on
- When I unlocked the bootloader, just before I installed TWRP, I made a copy of the recovery. Also I backed up my stock ROM. Both I kept
So to restore:
- I re-installed via TWRP, the stock ROM, and made sure that I didn't root it
- I re-installed the stock recovery
- rebooted and phone saw the MM upgrade and proceeded to upgrade.
If you don't have the recovery/stock ROM you will need to remember what version of android you were on when you overwrote the recovery with TWRP. If your firmware + recovery + OS do not match the update won't work.
-brad
redpoint73 said:
Yes, that is what I would suggest. Guide on how to make it LOCKED and remove TAMPERED:
http://forum.xda-developers.com/showthread.php?t=2708571
Click to expand...
Click to collapse
Awesome, got my phone S-Off. I tried installing the RUU from the HTC website but I got an error and it failed, saying something about I'm using the wrong RUU. This is my CID and MID:
MID: 0P6B13000
CID: T-MOB010
I used this link to get my RUU:
http://www.htc.com/us/support/rom-downloads.html#tmobile
Am I doing something wrong?
TehAsher said:
I tried installing the RUU from the HTC website but I got an error and it failed, saying something about I'm using the wrong RUU. This is my CID and MID:
MID: 0P6B13000
CID: T-MOB010
I used this link to get my RUU:
http://www.htc.com/us/support/rom-downloads.html#tmobile
Am I doing something wrong?
Click to expand...
Click to collapse
What error number? If 155 or 159, you can't RUU from LP to MM (this is a new requirement they added with MM). You either need to flash the 6.20.531.5 full stock firmware from here, then run the RUU again. Or run the T-Mobile LP RUU.
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.