Hello,
I bought an HTC M9 Hima uhl yesterday, and of course as soons as home I checked the latest official rom available and the one installed on my phone.
Mine was 2.10 something and I saw there was a 3.35 on some website.
So first things before playing to much with the phone, update to last official rom.
First I unlocked the bootloader, S was already OFF and it is SUPERCID.
I downloaded this RUU...exe and started the update. Everything went fine until 50% of the update, and I got an error saying my device is not the correct model for this udpate.
You could not check that before starting the update!?!?!?!
Indeed, the RUU I got was fro HIMA UL and not UHL ! A mistake on the website I downloaded the file from... and I did not check it ...:crying:
My phone is now stuck on the HTC first splash screen, I can access download mode etc...
It seems this update messed with my phone as now, in download mode it says it is himaulatt !!! not himauhl anymore! (but still unlocked, supercid and S-off)
So I managed to find an 0PJAIMG 3.35 fro Hima uhl, I used HTC_fastboot to udpate my phone again, but each time I got this error:
(bootloader) HOSD CL#669696
(bootloader) ERR Model ID not matched
(bootloader) ERR [SD_UPDATE_ERR] MODEL ID NOT ALLOWED
(bootloader) ERR [SD_UPDATE_ERR] sddownload failed: 10
(bootloader) ERR Update zip file failed.
(bootloader) ERR ZIP ERROR, exit read zip loop
(bootloader) Update zip file OK
(bootloader) ERR ZIP ERROR CODE, 10
(bootloader) [email protected]
FAILED (remote: 10 RU_MODELID_FAIL modelid in android-info mismatched )
I don't get it, if I am supercid it should not be a problem, right? Or is it because the first update messed with the model ID ?? (himaulatt instead of himauhl)
I tried the same thing with a 1.32v of an 0PJAIMG image... but still the same problem.
I also tried with TWRP but it says it cannot find the carrier and something wrong with the zip file.
Right now I am trying to get a RUU for HIMA UHL, downloading it....
But if anyone has an other idea of what I can do... please help:crying:
Thank you so much!!!
Change your MID to PJA11000.
fastboot oem writemid 0PJA11000
run RUU again.
side_flip15 said:
Change your MID to PJA11000.
fastboot oem writemid 0PJA11000
run RUU again.
Click to expand...
Click to collapse
Thanks I will try
What is this MID ?
SHould I run RUU UHL or UL will be ok this time?
Is it going to put back the correct model HIMA UHL in the bootloader?
Error 157 with the same RUU HIMA UL ... same error than before actually
and now with a RUU HIMA UHL (ASIA_TW) error 155 :crying::crying::crying:
That was my last solution... I don't know what to do now:crying:
Here is my bootloader screen after the first update with HIMA UL (while it was hima uhl):
Some errors !
Before it was fine
This > dl3.htc.com/application/RUU_HIMA_UL_M60_SENSE70_ATT_MR_NA_Gen_Unlock_3.35.617.12.exe
This will convert your M9 to dev edition.
here's the link fyr..
http://forum.xda-developers.com/showpost.php?p=64451344&postcount=123
side_flip15 said:
This > dl3.htc.com/application/RUU_HIMA_UL_M60_SENSE70_ATT_MR_NA_Gen_Unlock_3.35.617.12.exe
This will convert your M9 to dev edition.
here's the link fyr..
http://forum.xda-developers.com/showpost.php?p=64451344&postcount=123
Click to expand...
Click to collapse
Actually this is exactly this RUU I downloaded first and with which I had this error and my phone bricked
So this HIMA UL or HIMA UHL is not important ? I can use both is ok?
Actually, I finally managed to flash a 0PJAIMG but an UHL version, unfortunately it is a 1.35 version for the rom ....
I have downloaded again the RUU_HIMA_UL_M60_SENSE70_ATT_MR_NA_Gen_Unlock_3.35. 617.12.exe
And again it stopped at 75% (stuck there for half an hour, no activity anymore) this time with no error message until I unplugged the usb cable and I got an error 155.... and of course my phone was bricked again..
Now I am reflashing the 0PJAIMG and I am trying to find the same in a more recent version..
The error you got during first ruu is because your MID does not match with the ruu. That is why I asked you to change MID.
Also you should never interrupt RUU flashing. You might end up with a paper weight device.
In the images you attached looks like you are alread in the latest dev edition firmware. Easiest possible option you can do is flash twrp recovery and flash custom rom of your choice.
Get the latest twrp img here
Flash in download mode
fastboot flash recovery <filename.img>
Download rom your choice and flash in twrp
side_flip15 said:
The error you got during first ruu is because your MID does not match with the ruu. That is why I asked you to change MID.
Also you should never interrupt RUU flashing. You might end up with a paper weight device.
In the images you attached looks like you are alread in the latest dev edition firmware. Easiest possible option you can do is flash twrp recovery and flash custom rom of your choice.
Get the latest twrp img here
Flash in download mode
fastboot flash recovery <filename.img>
Download rom your choice and flash in twrp
Click to expand...
Click to collapse
I did change the MID as you ask me to do, but I still have an error if I do so, Error 157. I did not interrupt RUU update, it was totally crashed.
I tried to use TWRP to flash a custom ROM but here again it fails or I got stuck on the splash screen.
So here is what I managed to do:
-I went back to a stock rom HIMA UHL (1.32) and I finally got my phone working ( I had to put back my MID to 0PJA10000) => this put back my bootloader in order, no more error and back to himauhl.
-I flashed the international Firmware for HIMA UHL (3.35.401.12 with TWRP included)
-I flashed Leedroid ROM latest version and everything is fine !!:laugh:
I still have this question, I feel it is not possible to change an HIMA UHL WWE to HIMA UL Developer. Let me know if I am wrong but each time I tried it bricked my phone and messed with my bootloader.
Mittel said:
I did change the MID as you ask me to do, but I still have an error if I do so, Error 157. I did not interrupt RUU update, it was totally crashed.
I tried to use TWRP to flash a custom ROM but here again it fails or I got stuck on the splash screen.
So here is what I managed to do:
-I went back to a stock rom HIMA UHL (1.32) and I finally got my phone working ( I had to put back my MID to 0PJA10000) => this put back my bootloader in order, no more error and back to himauhl.
-I flashed the international Firmware for HIMA UHL (3.35.401.12 with TWRP included)
-I flashed Leedroid ROM latest version and everything is fine !!:laugh:
I still have this question, I feel it is not possible to change an HIMA UHL WWE to HIMA UL Developer. Let me know if I am wrong but each time I tried it bricked my phone and messed with my bootloader.
Click to expand...
Click to collapse
Yes you can. Mine is actually converted from WWE Asia.
You don't really need to go back to 1.32, you're already in 3.35 firmware looking at the images you posted. You just need to flash TWRP and flash Leedroid ROM. Saves you a lot of time but glad you made it work again.
side_flip15 said:
Yes you can. Mine is actually converted from WWE Asia.
You don't really need to go back to 1.32, you're already in 3.35 firmware looking at the images you posted. You just need to flash TWRP and flash Leedroid ROM. Saves you a lot of time but glad you made it work again.
Click to expand...
Click to collapse
Ok weird that each time I did my phone ended bricked even after changing MID etc....
Thanks anyway for the help
Related
I downloaded an RUU file, which I think is the correct one for my device. My CID output looks like this:
... INFODEBUG: cid: HTC__001
And according to this post, I should be using the HTC-WWE RUU. So I downloaded an RUU from a 3rd party website (I believe it was 4shared, because FileFactory has never once had a free user download slot available to me). So the file that I downloaded was:
RUU_ENDEAVOR_U_ICS_40_hTC_Asia_WWE_1.29.707.11_Radio_1.1204.105.14_release_260743_signed.exe
I flashed recovery as well as boot, and then i relocked the bootloader. When I booted back into the boot loader and tried to run the RUU it gave me an error message, "Error [131] customer id error"
Can someone please help me get this sorted out?
I looked up my phone IMEI number on the htc's website to find out the edition/region.
Mine is the HongKong version, so I downloaded the ASIA_HK RUU.
Because you can only upgrade or flash the same version (NO DOWNGRADE), you need to check the version of the RUU.
I didnt remember my stock version, so I went to hboot and looked for the radio version. Then I found the ASIA_HK RUU with the same Radio version and flashed, and worked.
So my advice is to check if you are downgrading the phone. If you do not know, check the radio version, and find the RUU with that radio.
xMemphisx said:
I downloaded an RUU file, which I think is the correct one for my device. My CID output looks like this:
... INFODEBUG: cid: HTC__001
And according to this post, I should be using the HTC-WWE RUU. So I downloaded an RUU from a 3rd party website (I believe it was 4shared, because FileFactory has never once had a free user download slot available to me). So the file that I downloaded was:
RUU_ENDEAVOR_U_ICS_40_hTC_Asia_WWE_1.29.707.11_Radio_1.1204.105.14_release_260743_signed.exe
I flashed recovery as well as boot, and then i relocked the bootloader. When I booted back into the boot loader and tried to run the RUU it gave me an error message, "Error [131] customer id error"
Can someone please help me get this sorted out?
Click to expand...
Click to collapse
From that RUU name it looks like you are downloading the asian RUU you will need to download RUU_ENDEAVOR_U_ICS_40_HTC_Europe_1.29.401.11_Radio_1.1204.105.1...etc.
xMemphisx said:
I downloaded an RUU file, which I think is the correct one for my device. My CID output looks like this:
... INFODEBUG: cid: HTC__001
And according to this post, I should be using the HTC-WWE RUU. So I downloaded an RUU from a 3rd party website (I believe it was 4shared, because FileFactory has never once had a free user download slot available to me). So the file that I downloaded was:
RUU_ENDEAVOR_U_ICS_40_hTC_Asia_WWE_1.29.707.11_Radio_1.1204.105.14_release_260743_signed.exe
I flashed recovery as well as boot, and then i relocked the bootloader. When I booted back into the boot loader and tried to run the RUU it gave me an error message, "Error [131] customer id error"
Can someone please help me get this sorted out?
Click to expand...
Click to collapse
It's a wrong RUU for your device with HTC__001.
This is the correct one : http://hoxroms.serveftp.com/RUU_END...Radio_1.1204.105.14_release_260491_signed.exe
i have tried to get back to stock by flashing an ruu file i downloaded RUU_ENDEAVOR_U_JB_45_S_HTC_Europe_3.14.401.31_R_Radio_5.1204.162.29_release_302015_signed
since my HOX is WWE. i tried to run the exe after re locking bootloader of course,but it gives an error (ERROR 140 BOOTLOADER VERSION ERROR) i tried it more than once so i figured the problem or i think i have my phone is running on 3.20.401.1 and the ruu is 3.14.401.31 i looked every where for 3.20.401.1 ruu but no luck have any one got a link for it?.or some one can help me solve this problem?
Ruu will never see the daylight with that number. If you want stock.....get one in the general section - nandroid backup collection ! More than enough to choose from
The nand has to match :
Fastboot getvar version-main
EDIT :
And if your CID is not present, take the 3.20.401 from another CID and and restore it, then flash back the stock recovery. Do not relock the bootloader (not needed) and update via about - software updates in the settings menu
if i flash a nandroid from another CID will it cause any problems?
downloading your 3.20.401.1 CID HTC__E11
No software issues won't be there. It's just that it's from another cid, it needs one official ota to pull the cid straight. After that you can also relock the bootloader if you wish
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
Anybody knows for what Country is this CID?
Br Tom
At least Denmark!
its european cid!
MaximN97 said:
its european cid!
Click to expand...
Click to collapse
So an HTC 10 with the HTC__034 CID is suitable for use in all of EU, right ?
Right.
TomF1979 said:
Anybody knows for what Country is this CID?
Br Tom
Click to expand...
Click to collapse
apart from what you mentioned this is what i had got from @andybones .....
will check with him if he could get a more extensive list or he could put a sticky with cid as i used to wonder myself...
cidnum: HTC__001 (HTC WWE)
cidnum: HTC__E11 (HTC NL)
cidnum: HTC__102 (HTC DE)
cidnum: HTC__203 (HTC FR)
cidnum: HTC__405 (HTC IT)
cidnum: HTC__Y13 (HTC NO)
cidnum: HTC__304 (HTC ES)
cidnum: HTC__032 (HTC Eastern Europe)
cidnum: HTC__A07 (HTC RU)
cidnum: HTC__J15 (HTC Arabia)
cidnum: HTC__016 (HTC South Africa)
and this is from gsmforum... (could be outdated)
Asia-HK-CHT HTC__622
ATT CWS__001
BM BM___001
H3G-AT H3G__106
H3G-DAN H3G__F05
H3G-Italy H3G__402
H3G-ROI H3G__003
H3G-SWE H3G__G04
H3G-UK H3G__001
HTC-Asia-SEA HTC__037
HTC-Asia-SEA-WWE HTC__044
HTC-Australia HTC__023
HTC-BE HTC__E41
HTC-Czech HTC__C24
HTC-Denmark HTC__F08
HTC-Dutch HTC__E11
HTC-EastEurope HTC__032
HTC-ELL HTC__N34
HTC-FRA HTC__203
HTC-FRA-Bouygues HTC__247
HTC-FRA-NRJ HTC__249
HTC-GCC HTC__J15
HTC-GER HTC__102
HTC-India HTC__038
HTC Israel HTC__K18
HTC-ITA HTC__405
HTC-Nor HTC__Y13
HTC-Norway HTC__H10
HTC-Poland HTC__B25
HTC-PTG HTC__506
HTC-Russia HTC__A07
HTC-SPA HTC__304
HTC-Sweden HTC__G09
HTC-Tesco HTC__052
HTC-Turkey HTC__M27
HTC-WWE HTC__001
TWM-TW HTC__621
VODA-Africa-South HTC__016
Heres all I could find
http://xda-developers-fix.blogspot.com/2016/05/1304011-flashable-zip-ruu-for-htc-10.html#
HTC Europe
https://commons.wikimedia.org/wiki/File:1302_Eindhoven_-_HTC_034.jpg
or perhaps, The Netherlands?
can't update HTC__034
Hello guys,
I have a problem since I used the Leedroid Nougat update. My phone cant uncrypted the datas. So I decided to install a RUU. Then I relock my HTC 10 htc_034(bought on HTC France website) and tried to install RUU for Europe (Marshmallow and Nougat) but it can't recover. I've the message that the ROM isn't for this version of phone (RUU.exe) or by SD card "19 RU_MAIN_VER_FAILED os-version in android-info missing or i".
This is the informations I have with getvar :
kernel : lk
product : htc_pmeuhl
version : 1.0
version-main : 1.95.401.3
boot-mode : download
version-baseband : [email protected]
version-bootloader : 1.0.0.0000
mid: 2PS620000
cid : HTC__034
I've tried these RUUs:
RUU_PERFUME_WL_N70_SENSE80GP_MR_NA_Gen_Unlock_2.28.617.8
RUU_PERFUME_WL_M60_SENSE80GP_NA_Gen_Unlock_1.96.617.20 (1)
2PS6IMG_PE[email protected]60331.4_41.13_F_release_478442_signed_2_4
2PS6IMG_PER[email protected]60714.2_59.06_F_release_483306_combined_signed_2
I tried to download RUUs in different websites but still same problem
What can I do?
Thanx
djlaludo2 said:
Hello guys,
I have a problem since I used the Leedroid Nougat update. My phone cant uncrypted the datas. So I decided to install a RUU. Then I relock my HTC 10 htc_034(bought on HTC France website) and tried to install RUU for Europe (Marshmallow and Nougat) but it can't recover. I've the message that the ROM isn't for this version of phone (RUU.exe) or by SD card "19 RU_MAIN_VER_FAILED os-version in android-info missing or i".
This is the informations I have with getvar :
kernel : lk
product : htc_pmeuhl
version : 1.0
version-main : 1.95.401.3
boot-mode : download
version-baseband : [email protected]
version-bootloader : 1.0.0.0000
mid: 2PS620000
cid : HTC__034
I've tried these RUUs:
RUU_PERFUME_WL_N70_SENSE80GP_MR_NA_Gen_Unlock_2.28.617.8
RUU_PERFUME_WL_M60_SENSE80GP_NA_Gen_Unlock_1.96.617.20 (1)
2PS6IMG_PE[email protected]60331.4_41.13_F_release_478442_signed_2_4
2PS6IMG_PER[email protected]60714.2_59.06_F_release_483306_combined_signed_2
I tried to download RUUs in different websites but still same problem
What can I do?
Thanx
Click to expand...
Click to collapse
I'm gonna guess you're S-On. The first two ruus you linked are not for your phone and you can't flash them. The other two are for your phone but are older than what you already have, and you can't downgrade your firmware if you're s-on.
Look around in the stock/backup thread or elsewhere for an RUU or full stock backup that matches your version
Tarima said:
I'm gonna guess you're S-On. The first two ruus you linked are not for your phone and you can't flash them. The other two are for your phone but are older than what you already have, and you can't downgrade your firmware if you're s-on.
Look around in the stock/backup thread or elsewhere for an RUU or full stock backup that matches your version
Click to expand...
Click to collapse
Yes, i'm S-ON. I don't find a RUU version for my model with firmware >= 1.95
I've read a new post for a guy who has the exact problem (caused by SuperSU wich does not good support encryption) but he didn't relock and choose TWRP with a ROM.
So i'm RELOCK, S-ON, without good RUU, what can I do?
Can I change CID to use the RUU I've downloaded?
Or if not I can return to a custom ROM... Is it easy to re-unlock the phone or should I use the same procedure with adb and fastboot I used the first time I unlocked?
Thanks a lot
djlaludo2 said:
Yes, i'm S-ON. I don't find a RUU version for my model with firmware >= 1.95
I've read a new post for a guy who has the exact problem (caused by SuperSU wich does not good support encryption) but he didn't relock and choose TWRP with a ROM.
So i'm RELOCK, S-ON, without good RUU, what can I do?
Can I change CID to use the RUU I've downloaded?
Or if not I can return to a custom ROM... Is it easy to re-unlock the phone or should I use the same procedure with adb and fastboot I used the first time I unlocked?
Thanks a lot
Click to expand...
Click to collapse
You cannot change cid if you're s-on.
I'm not sure about re-unlocking your bootloader but it should be the same process you used initially. As for supersu, the newer versions do support encryption. I've always had my phone encrypted, and rooted. Are you using the latest version of supersu?
Returning to custom Rom should work fine, especially if you format your internal storage (backup everything first). But I'm not fully clear on what your issue is.
I think the problem is that the version of TWRP you are using (which I'm guessing is 3.0.2-6 or lower) has issues with Nougat. There's two things that break it, I believe. It can't decrypt data after you install Nougat, or it doesnt work at all on the Nougat firmware if one installs that (2.28.XXX.X), which you havent.
TWRP has an updated version (3.0.2-7) that does now support Nougat, so I would suggest flashing that over the TWRP you currently have., it might help fix your problem.
Tarima said:
You cannot change cid if you're s-on.
I'm not sure about re-unlocking your bootloader but it should be the same process you used initially. As for supersu, the newer versions do support encryption. I've always had my phone encrypted, and rooted. Are you using the latest version of supersu?
Returning to custom Rom should work fine, especially if you format your internal storage (backup everything first). But I'm not fully clear on what your issue is.
Click to expand...
Click to collapse
I've seen the command : fastboot unlock, do you think I can try that to see if it unlocks quickly before doing the big process by HTC Dev?
For my problem of encryption, it started when SuperSU did the update itself by Google Play in the beginning of this week. After reboot, I think I already lost all datas because the phone can't read crypted datas... My 64GB SD-card crashed just a few days before... Bad luck this week...
Leedroid Nougat's ROM still in Beta version. I'm little affraid to re-install this ROM, do you know a good Nougat one's which works fine on HTC10?
Thank you!
---------- Post added at 12:58 PM ---------- Previous post was at 12:49 PM ----------
silegeek said:
I think the problem is that the version of TWRP you are using (which I'm guessing is 3.0.2-6 or lower) has issues with Nougat. There's two things that break it, I believe. It can't decrypt data after you install Nougat, or it doesnt work at all on the Nougat firmware if one installs that (2.28.XXX.X), which you havent.
TWRP has an updated version (3.0.2-7) that does now support Nougat, so I would suggest flashing that over the TWRP you currently have., it might help fix your problem.
Click to expand...
Click to collapse
Yes my TWRP version was the last one on 2016 september, so not compatible with Nougat as you said. Can I install the new version with "fastboot flash recovery twrp.img" (I relocked to try to install RUU)?
Do you think I will recover my datas after that or should I erase all?
Thank you :good:
djlaludo2 said:
I've seen the command : fastboot unlock, do you think I can try that to see if it unlocks quickly before doing the big process by HTC Dev?
For my problem of encryption, it started when SuperSU did the update itself by Google Play in the beginning of this week. After reboot, I think I already lost all datas because the phone can't read crypted datas... My 64GB SD-card crashed just a few days before... Bad luck this week...
Leedroid Nougat's ROM still in Beta version. I'm little affraid to re-install this ROM, do you know a good Nougat one's which works fine on HTC10?
Thank you!
---------- Post added at 12:58 PM ---------- Previous post was at 12:49 PM ----------
Yes my TWRP version was the last one on 2016 september, so not compatible with Nougat as you said. Can I install the new version with "fastboot flash recovery twrp.img" (I relocked to try to install RUU)?
Do you think I will recover my datas after that or should I erase all?
Thank you :good:
Click to expand...
Click to collapse
Without s-off, I THINK you need an unlocked bootloader to flash recovery from the download.
I never tried to flash anything with bootloader locked so I have no idea, but I'm guessing it's the case. But yeah, once unlocked, it's just fastboot flash recovery TWRP-recovery.img
djlaludo2 said:
Yes my TWRP version was the last one on 2016 september, so not compatible with Nougat as you said. Can I install the new version with "fastboot flash recovery twrp.img"
Click to expand...
Click to collapse
Just install the new version of TWRP from your existing version of TWRP. Switch to Install Img mode if it's not in a flashable Zip.
silegeek said:
Without s-off, I THINK you need an unlocked bootloader to flash recovery from the download.
I never tried to flash anything with bootloader locked so I have no idea, but I'm guessing it's the case. But yeah, once unlocked, it's just fastboot flash recovery TWRP-recovery.img
Click to expand...
Click to collapse
Thanx for all this help but...
Good news I put the last TWRP using the old one. It works so I decided to reinstall Leedroid Nougat with full wipe, all new with encryption. Installation ok, green htc logo at startup and.......I still have the message that the key is the good one for uncrypt phone but it doesn't work so I have to reset. So I do the same operation without encryption. Same result,phone can't be uncrypted.
Remember, I RELOCKed the phone. Then I tried to unlock... With fastboot and my old key file. I had an error message it says the file wasn't good (don't remeber exactly but sounds it wasn't the good file). So...I decided to send fastboot oem get_identifier_token and it responds FAILED (remote:unknown command) so I can't unlock by this way....
Just a thing, maybe normal, when I go into TWRP, it asks for the unlock code and said it's wrong so i choose cancel and swipe to access at the menu to install.
Just seen I have the 3.0.2.5 TWRP so the flash of new TWRP didn't succeed ... I try to write with fastboot flash recovery but it says "FAILED (remote: cannot flash this partition in s-on state"
What do you suggest guys?
djlaludo2 said:
Thanx for all this help but...
Good news I put the last TWRP using the old one. It works so I decided to reinstall Leedroid Nougat with full wipe, all new with encryption. Installation ok, green htc logo at startup and.......I still have the message that the key is the good one for uncrypt phone but it doesn't work so I have to reset. So I do the same operation without encryption. Same result,phone can't be uncrypted.
Remember, I RELOCKed the phone. Then I tried to unlock... With fastboot and my old key file. I had an error message it says the file wasn't good (don't remeber exactly but sounds it wasn't the good file). So...I decided to send fastboot oem get_identifier_token and it responds FAILED (remote:unknown command) so I can't unlock by this way....
Just a thing, maybe normal, when I go into TWRP, it asks for the unlock code and said it's wrong so i choose cancel and swipe to access at the menu to install.
Just seen I have the 3.0.2.5 TWRP so the flash of new TWRP didn't succeed ... I try to write with fastboot flash recovery but it says "FAILED (remote: cannot flash this partition in s-on state"
What do you suggest guys?
Click to expand...
Click to collapse
When you run
fastboot oem get_identifier_token
are you doing it from the bootloader or from the Download? You need to be in the Download mode for fastboot to operate properly. The bootloader is the white screen. The Download is the black screen
You can get to the download mode from the Bootloader by highlighing the option that says "Boot to Download Mode"
Or you can just go there straight away by pressing Volume Down and Power. From the download mode fastboot oem get_identifier_token shoud work. From there you put the token on the HTC Website and they provide you with the Unlock_code.bin
fastboot flash unlocktoken Unlock_code.bin
silegeek said:
When you run
fastboot oem get_identifier_token
are you doing it from the bootloader or from the Download? You need to be in the Download mode for fastboot to operate properly. The bootloader is the white screen. The Download is the black screen
You can get to the download mode from the Bootloader by highlighing the option that says "Boot to Download Mode"
Or you can just go there straight away by pressing Volume Down and Power. From the download mode fastboot oem get_identifier_token shoud work. From there you put the token on the HTC Website and they provide you with the Unlock_code.bin
fastboot flash unlocktoken Unlock_code.bin
Click to expand...
Click to collapse
:silly::silly::silly: Oh god yes for the last tests I was in the bootloader! Before I often rooted HTC M8 which haven't the DOWNLOAD mode, so after hours of war with my phone my mind wasn't very clear
For the story, in download mode I unlocked the phone. After from TWRP I installed the last version. Then it restarted and all was recover :victory:
Thank you all very much for your assistance and reactivity:good::good::good:
djlaludo2 said:
:silly::silly::silly: Oh god yes for the last tests I was in the bootloader! Before I often rooted HTC M8 which haven't the DOWNLOAD mode, so after hours of war with my phone my mind wasn't very clear
For the story, in download mode I unlocked the phone. After from TWRP I installed the last version. Then it restarted and all was recover :victory:
Thank you all very much for your assistance and reactivity:good::good::good:
Click to expand...
Click to collapse
Dear guys,
I restarted my phone... And the problem appears again, can't uncrypt the phone!
I installed by TWRP last version of SuperSU. Not efficient.
So I install again last version of TWRP and it restarted and works good.
But I'm affraid to restart the phone... Do you have any idea to fix that definitely? Wait new version of TWRP? Flash Nougat firmware?
Or do you have an HTC link where I can download the good RUU for my phone (can't find with Google)?
Thanx a lot! :silly:
djlaludo2 said:
Yes, i'm S-ON. I don't find a RUU version for my model with firmware >= 1.95
I've read a new post for a guy who has the exact problem (caused by SuperSU wich does not good support encryption) but he didn't relock and choose TWRP with a ROM.
So i'm RELOCK, S-ON, without good RUU, what can I do?
Can I change CID to use the RUU I've downloaded?
Or if not I can return to a custom ROM... Is it easy to re-unlock the phone or should I use the same procedure with adb and fastboot I used the first time I unlocked?
Thanks a lot
Click to expand...
Click to collapse
Do not try to change the CID, you have to be s-off for that