Hello everyone.
I have the following on my M9:
H:\HTC>fastboot getvar all
< waiting for device >
(bootloader) kernel: lk
(bootloader) product: htc_himauhl
(bootloader) version: 1.0
(bootloader) imei: 3572260XXXXXXXX
(bootloader) version-main: 4.30.617.2
(bootloader) boot-mode: download
(bootloader) version-baseband: 01.04_U11440601_71.02.50709G_F
(bootloader) version-bootloader: 1.0.0.0000
(bootloader) mid: 0PJA10000
(bootloader) cid: 11111111
Having this issues while flashing rom's:
- Flashed three ROM's correctly, after flashing i get continous loop and no boot;
- Flashed three ROM's correctly, and after booting i get sound issues ( for example alarm sounds can't be played since i get the warning "It wans't possible to play this file" ) can't also make phone calls because appears "Dialling" but nothing appens and the phone app crashes/freezes.
I'm starting to think i might have a firmware issue, since it can't be a software problem ( these problems appened in all three correctly flashed ROM's ).
Considering to downgrade firmware to 4.28.401.3, so i can check if the problems persist.
Any tips or help to try and solve this would be appreciated.
Thanks in advance
What you're planning to do isn't a downgrade it's a conversion. Those firmware versions belong to different SKUs and therefore aren't related with each other. (There is neither a 4.30.401.x firmware nor a 4.28.617.x one.)
What I noticed is that you don't use the correct MID and CID for your SKU. These mismatches aren't the cause for your issues, though.
Are you sure that you own the international variant (codename: 0PJA10000)? What's engraved on the backside of the phone (keep in mind that the engraving lacks two zeros)?
It actually doesn't matter which SKU (401 or 617) you use with the custom roms of this section. Therefore, the issue is most probably caused by something else.
The possible reasons that come to my mind at the moment are:
- You actually own a CDMA phone and flashed a GSM firmware. (Some kind of firmware flash did happen in the past since CID and MID don't match the SKU.)
- Your phone's hardware is broken.
- The rom files got broken during the download. (This can be checked by verifying the MD5 checksum of the files.)
- There is some kind of other user error that we don't know about, yet.
Edit: It actually is the last reason. GAPPS are only needed for non-Sense-based roms. You break every custom rom that is based on HTC Sense if you flash them.
Edit2: And you didn't update your firmware, correctly. That archive you mentioned only contains the aboot and not the whole firmware. This way you created a frankenfirm. The best solution I can recommend is following the conversion guide in the ReadMe thread (c.f. the General or the Q&A section), properly flashing the latest 617 RUU and then trying to flash a custom rom with the latest TWRP version.
Sent from my HTC One M9 using XDA Labs
Flippy498 said:
What you're planning to do isn't a downgrade it's a conversion. Those firmware versions belong to different SKUs and therefore aren't related with each other.
What I noticed is that you don't use the correct MID and CID for your SKU. These mismatches aren't the cause for your issues, though.
Are you sure that you own the international variant (codename: 0PJA10000)? What's engraved on the backside of the phone (keep in mind that the engraving lacks two zeros)?
It actually doesn't matter which SKU (401 or 617) you use with the custom roms of this section. Therefore, the issue is most probably caused by something else.
The possible reasons that come to my mind at the moment are:
- You actually own a CDMA phone and flashed a GSM firmware. (Some kind of firmware flash did happen in the past since CID and MID don't match the SKU.)
- Your phone's hardware is broken.
- The rom files got broken during the download. (This can be checked by verifying the MD5 checksum of the files.)
- There is some kind of other user error that we don't know about, yet.
Click to expand...
Click to collapse
First of all thanks for the time spent to try and help me.
Engraved on the backside it's 0PJA100, so it's really international variant (codename: 0PJA10000).
My phone is GSM, bought and used in Portugal ( Europe ) but i think i might have flashed a wrong firmware because :
- i bought a HTC 10 and after that i flashed the current firmware and flashed the ROM, however i never tested everything since i didn't used the M9 anymore.I only noticed this issues now because my HTC 10 is broken and i needed to use the M9;
- i'm not into the broken hardware, since everything was ok before flashing firmware and ROM and after that i kept my M9 stored and not in use;
- one ROM file could be broken during download, but i have flashed correctly three ROM'S and the problem persists in all of them ( would be really bad luck that all three ROM'S where corrupted );
- i've been checking firmware posts and can't find where did i got this firmware from, since i see everywhere that 4.28.401.3 is the latest.
So downgrading/flashing firmware could serve to see if the problem persists.
My question is can i flash the M9_4.28.401.3_WWE_TWRP3100_NoWipe from https://forum.xda-developers.com/one-m9/development/firmware-t3068243?
Edit : Saw your edit's now i finished writing, even if i don't install GAPPS the problems persist.
Thanks for the help will do the edit 2 now.
---------- Post added at 01:08 PM ---------- Previous post was at 12:53 PM ----------
Flippy498 said:
Edit2: And you didn't update your firmware, correctly. That archive you mentioned only contains the aboot and not the whole firmware. This way you created a frankenfirm. The best solution I can recommend is following the conversion guide in the ReadMe thread (c.f. the General or the Q&A section), properly flashing the latest 617 RUU and then trying to flash a custom rom with the latest TWRP version.
Click to expand...
Click to collapse
Just to check if i'm understanding correctly:
- you are refering to https://forum.xda-developers.com/showpost.php?p=71421945&postcount=5
- i must flash the HTC One M9 4.23.617.1 from https://www.htc.com/us/support/rom-downloads.html
- flash latest TWRP and flash custom ROM.
4.28.401.3 is the latest European firmware for the international hardware variant (0PJA10000). 4.30.617.12 is the latest firmware for the US unlocked/developer variant (0PJA11000). The "correct" version would be the 401 for your phone.
However, since the GSM variants are almost one and the same version of the phone you can convert one into the other without problems.
Edit:
lmcmil said:
Just to check if i'm understanding correctly:
- you are refering to https://forum.xda-developers.com/showpost.php?p=71421945&postcount=5
- i must flash the HTC One M9 4.23.617.1 from https://www.htc.com/us/support/rom-downloads.html
- flash latest TWRP and flash custom ROM.
Click to expand...
Click to collapse
Yes, that's the guide I'm talking about. But no, that's not the latest RUU. Check the downloads in the RUU section of the ReadMe thread.
Flippy498 said:
4.28.401.3 is the latest European firmware for the international hardware variant (0PJA10000). 4.30.617.12 is the latest firmware for the US unlocked/developer variant (0PJA11000).
Since the GSM variants are almost one and the same version of the phone you can convert one into the other without problems.
Click to expand...
Click to collapse
So i flashed ( and incorrectly ) the US firmware...
Thanks a lot Flippy498,
GSM RUUs
codename: hima_uhl - MID: 0PJA10000
SKU: 401 - CID: HTC__001, HTC__J15, HTC__102, HTC__Y13, HTC__A07, HTC__032, HTC__016, HTC__M27, HTC__002 or HTC__031
4.28.401.3
0PJAIMG_HIMA_UHL_N70_SENSE80_MR_HTC_Europe_4.28.401.3_Radio_01.01_U114401011_117.00.61117G_2_F_release_498151_signed_2.zip
The correct one?
I have SuperCID, and 0PJA10000 MID if i understood correctly i do not need to change them correct?
Sorry for the "late" reply. I don't have enough free time for being online all the time.
What you flashed (according to the older post of yours that I linked in one of my previous posts) was just the aboot. In other words you only updated one of many partitions of your phone's firmware (there are around 50 if I'm not mistaken). Therefore, most partitions of your phone were still running outdated versions of the firmware. That's why you weren't able to flash the custom roms successfully.
Flashing a US GSM firmware on a European GSM phone isn't a real mistake. The differences between the GSM versions are almost non-existent. That's why many convert their phones from one version to the other. The catch is that you actually need to convert all partitions and not only one like you did.
The 4.28.401.3 RUU you mentioned is the correct one if you want to use the firmware that originally belonged to your phone. You're already using the correct MID for that RUU. You need to change your CID though. The SCID isn't recommended on this phone since it lost many benefits that it had on older HTC devices. The compatible CIDs are the ones that you listed in your last post. It doesn't matter which one you choose. If you want to know the meaning of each you need to take a look at Sneakyghost's CID & MID list (it's linked in the Further Reading Section of the ReadMe thread).
All available methods for flashing a RUU are listed in the RUU section in which you already found the file.
Flippy498 said:
Sorry for the "late" reply. I don't have enough free time for being online all the time.
Click to expand...
Click to collapse
Sure thing mate, i'm really thankfull for all the help and time spent trying to help me.
Changed the CID to HTC__001, formatted a micro sd in fat32, placed the ruu zip file and changed it's name to flash it.
However i'm getting the following error : failed: -2, 12:fail to flash via download zip
12 SIGNATURE FAIL: The phone expects an HTC signature and can't find one or found a wrong one. This error occurs if you try to flash a RUU that uses a different encryption key than the one your phone is using (e.g. firmware 3.x and older vs. 4.x)
Is there a way i can solve this flashing error?
Oh, I forgot that the encryption keys changed between firmware 3.x and 4.x. Since your phone didn't get updated properly it's probably still using the 3.x keys. You need to either flash the latest 3.x RUU and to update the phone via the update function of the system settings or you flash the 4.28.401.3 full wipe pack from sneakyghost's thread and the RUU, afterwards. Both, OTAs and Sneakyghost's packs, aren't encrypted whereas RUUs are encrypted. Users with S-ON can only use the OTA method but your phone is S-OFF so using Sneakyghost's packs shouldn't be a problem.
Sent from my HTC One M9 using XDA Labs
Flippy498 said:
Oh, I forgot that the encryption keys changed between firmware 3.x and 4.x. Since your phone didn't get updated properly it's probably still using the 3.x keys. You need to either flash the latest 3.x RUU and to update the phone via the update function of the system settings or you flash the 4.28.401.3 full wipe pack from sneakyghost's thread and the RUU, afterwards. Both, OTAs and Sneakyghost's packs, aren't encrypted whereas RUUs are encrypted. Users with S-ON can only use the OTA method but your phone is S-OFF so using Sneakyghost's packs shouldn't be a problem.
Sent from my HTC One M9 using XDA Labs
Click to expand...
Click to collapse
Thanks once again Flippy498 for your time spent in this issue.
Noob question, why do i always have to flash the RUU?
You don't "have to". It's just a way of starting from scratch which is highly recommended if you made mistakes while flashing firmware files. RUUs rewrite all partitions with stock files and since they get made by HTC you can rest assured that they fix all soft- and firmware related problems on your phone. Sneakyghost's packs on the other hand are custom made (although they contain official files).
Even Sneakyghost's thread contains a sentence with content similar to "If you messed up with flashing firmware files and something isn't working properly you should flash a RUU".
Sent from my HTC One M9 using XDA Labs
Flashed firmware
L:\HTC>fastboot flash zip Firmware.zip
target reported max download size of 800000000 bytes
sending 'zip' (134636 KB)...
OKAY [ 7.166s]
writing 'zip'...
(bootloader) HOSD CL#576582
(bootloader) GPT is up-to-dated. [17408]
(bootloader) Perform pre-update
(bootloader) [email protected]
(bootloader) [email protected]%
(bootloader) [email protected]
(bootloader) [email protected]
(bootloader) [email protected]
(bootloader) [email protected]
(bootloader) [email protected]
(bootloader) [email protected]
(bootloader) [email protected]
(bootloader) [email protected]%
(bootloader) [email protected]%
(bootloader) [email protected]
(bootloader) [email protected]
(bootloader) [email protected]
(bootloader) [email protected]%
(bootloader) [email protected]
(bootloader) [email protected]
(bootloader) [email protected]%
(bootloader) [email protected]%
(bootloader) [email protected]%
(bootloader) [email protected]
(bootloader) [email protected]
(bootloader) [email protected]
(bootloader) [email protected]
(bootloader) [email protected]%
(bootloader) [email protected]
FAILED (remote: 90 hboot pre-update! please flush image again immediately)
finished. total time: 8.488s
L:\HTC>fastboot flash zip Firmware.zip
< waiting for device >
target reported max download size of 800000000 bytes
sending 'zip' (134636 KB)...
OKAY [ 7.268s]
writing 'zip'...
(bootloader) HOSD CL#869604
(bootloader) GPT (gpt_main_32g.img) is up-to-dated. [17408]
(bootloader) WARN Skip bootlocker.img due to unmatched partition name
(bootloader) WARN Skip cir.img due to unmatched partition name
(bootloader) WARN Skip cmnlib32.img due to unmatched partition name
(bootloader) WARN Skip cmnlib64.img due to unmatched partition name
(bootloader) WARN Skip keymaster.img due to unmatched partition name
(bootloader) get 24 images from zip(zip_type=3)
(bootloader) [email protected]
(bootloader) [email protected]%
(bootloader) [email protected]%
(bootloader) [email protected]%
(bootloader) [email protected]%
(bootloader) [email protected]%
(bootloader) [email protected]%
(bootloader) [email protected]%
(bootloader) [email protected]%
(bootloader) [email protected]%
(bootloader) [email protected]%
(bootloader) [email protected]%
(bootloader) [email protected]%
(bootloader) [email protected]%
(bootloader) [email protected]%
(bootloader) [email protected]%
(bootloader) [email protected]%
(bootloader) [email protected]%
(bootloader) [email protected]%
(bootloader) [email protected]%
(bootloader) [email protected]%
(bootloader) [email protected]%
(bootloader) [email protected]%
(bootloader) [email protected]%
(bootloader) [email protected]%
(bootloader) [email protected]%
(bootloader) [email protected]%
(bootloader) [email protected]%
(bootloader) [email protected]%
(bootloader) [email protected]%
(bootloader) [email protected]%
(bootloader) [email protected]%
(bootloader) [email protected]
(bootloader) Update zip file OK
(bootloader) [email protected]
OKAY [ 70.608s]
finished. total time: 77.876s
L:\HTC>
PS 1 - Finished flashing RUU using SD card method now, waiting for first boot
PS 2 - First boot went ok, tested the issues i had earlier and they are gone!
Will now flash a TWRP recovey and custom ROM
PS3 - Flashed LeeDrOiD_10_V4.0.0-R119 rom for HTC ONE M9 ROM and all is working :good::good:
THANKS A LOT for all the help and spent time Flippy498, if we live closer i would buy you a few beers!
lmcmil said:
THANKS A LOT for all the help and spent time Flippy498, if we live closer i would buy you a few beers!
Click to expand...
Click to collapse
You still can use his DONATE button
lucyr03 said:
You still can use his DONATE button
Click to expand...
Click to collapse
Considering do it!
Related
Hello All,
I have tried to follow all these tutorials, but my issues is not listed yet.
Original rom was on Vodafone, tried to gain S-OFF, but it failed saying that is not possible for my device yet? So I was kind of stuck with Tampered, Unlocked but S-ON
By mistake I have wipe everything through customer recovery as I have left myself with No OS. Tried different RUU, latest one isRUU_M8_TMOUS_1.57.531.7, but can't go anywhere and always stuck on Signature check 132 Error or 150 error
I did reboot boot loader and I did relock.
Tried also a Sideload rom, comes up with the error that is either insufficient space, can not read sideload. cant't push through adb either comes with error
Also is there a way to gain S-OFF in the bootloader only?
Looking forward to your thoughts and possible solution.
Many thanks
Also: when i run the relock command this one comes up.
(bootloader) [PGFS] partition_update_pgfs: pg1fs_security
(bootloader) Lock successfully...
(bootloader) deinit_lcd
(bootloader) mipi display off
(bootloader) mdp_clock_off
(bootloader) turn off fd8c2308 failed 1 times. Try again...
(bootloader) disable_mmss_clk done
(bootloader) pll1_disable done
(bootloader) TZ_HTC_SVC_DISABLE ret = -1610744452 (0x9FFDFD7C)
(bootloader) [CRITICAL] SPMI write command failure: cmd_id =
0, error
(bootloader) = 4
(bootloader) [CRITICAL] SPMI write command failure: cmd_id =
0, error
(bootloader) = 4
(bootloader) [INFO] Rebooting device
FAILED (status read failed (Too many links))
finished. total time: 1.153s
Answer me this quickly, if you have a Vodafone, S-ON, why on God's green earth would you flash a RUU for T-Mobile US?
arnasx69 said:
Hello All,
I have tried to follow all these tutorials, but my issues is not listed yet.
Original rom was on Vodafone, tried to gain S-OFF, but it failed saying that is not possible for my device yet? So I was kind of stuck with Tampered, Unlocked but S-ON
By mistake I have wipe everything through customer recovery as I have left myself with No OS. Tried different RUU, latest one isRUU_M8_TMOUS_1.57.531.7, but can't go anywhere and always stuck on Signature check 132 Error or 150 error
I did reboot boot loader and I did relock.
Tried also a Sideload rom, comes up with the error that is either insufficient space, can not read sideload. cant't push through adb either comes with error
Also is there a way to gain S-OFF in the bootloader only?
Looking forward to your thoughts and possible solution.
Many thanks
Also: when i run the relock command this one comes up.
(bootloader) [PGFS] partition_update_pgfs: pg1fs_security
(bootloader) Lock successfully...
(bootloader) deinit_lcd
(bootloader) mipi display off
(bootloader) mdp_clock_off
(bootloader) turn off fd8c2308 failed 1 times. Try again...
(bootloader) disable_mmss_clk done
(bootloader) pll1_disable done
(bootloader) TZ_HTC_SVC_DISABLE ret = -1610744452 (0x9FFDFD7C)
(bootloader) [CRITICAL] SPMI write command failure: cmd_id =
0, error
(bootloader) = 4
(bootloader) [CRITICAL] SPMI write command failure: cmd_id =
0, error
(bootloader) = 4
(bootloader) [INFO] Rebooting device
FAILED (status read failed (Too many links))
finished. total time: 1.153s
Click to expand...
Click to collapse
Flash a custom ROM. Put the firmware and gapps on your sdcard.
I think he should just restore his phone to stock ROM after he flashed a custom ROM. If he doesn't know the difference between Vodafone and T-Mobile then I don't know... To make matters worst he knows he has no OS on his device and then he goes to try and lock the bootloader, in the hopes of achieving what?
Put a ROM on a SD card, flash it through custom recovery, download a stock ROM for your device from the Collection thread in General section. Restore the device back to stock and rather leave the flashing until you read up on the basics and get a better understanding of these things before you really mess up mate.
Thank guys,
I have tried T-mobile because i found somewhere in the forum. I thought it was a bit strange.
Customer roms don't work either. comes up with errors, can not mount cache.
I don't really know where to start any help would be much appreciated.
Never had issues with other android phones but this one is tough.
arnasx69 said:
Thank guys,
I have tried T-mobile because i found somewhere in the forum. I thought it was a bit strange.
Customer roms don't work either. comes up with errors, can not mount cache.
I don't really know where to start any help would be much appreciated.
Never had issues with other android phones but this one is tough.
Click to expand...
Click to collapse
Make sure bootloader is UNLOCKED, and keep it unlocked (only relock if you need to return phone to HTC)
What custom rom did you try? what custom recovery do you have?
RossMacgill said:
Make sure bootloader is UNLOCKED, and keep it unlocked (only relock if you need to return phone to HTC)
What custom rom did you try? what custom recovery do you have?
Click to expand...
Click to collapse
Clockwork Recovery
tried all sort of roms, just tried to put android_revolution_HD, aroma installer went fine which was an improvement. but still stuck on HTC one logo again.
UPDATE: OK managed to get in the stock rom working. But no WIFI is not working. Tried to update to the newest firmware and it comes up with incorrect model ID.
arnasx69 said:
Clockwork Recovery
tried all sort of roms, just tried to put android_revolution_HD, aroma installer went fine which was an improvement. but still stuck on HTC one logo again.
UPDATE: OK managed to get in the stock rom working. But no WIFI is not working. Tried to update to the newest firmware and it comes up with incorrect model ID.
Click to expand...
Click to collapse
wifi is not working because you have installed the newest version, use the version you had before, like 4.4.2/4.4.3 etc that way you can then update to latest firmware.
arnasx69 said:
Clockwork Recovery
tried all sort of roms, just tried to put android_revolution_HD, aroma installer went fine which was an improvement. but still stuck on HTC one logo again.
UPDATE: OK managed to get in the stock rom working. But no WIFI is not working. Tried to update to the newest firmware and it comes up with incorrect model ID.
Click to expand...
Click to collapse
RossMacgill said:
wifi is not working because you have installed the newest version, use the version you had before, like 4.4.2/4.4.3 etc that way you can then update to latest firmware.
Click to expand...
Click to collapse
Also, your MID (model id) and CID must match the firmware you are flashing since you are not S-off, and therefore not superCID.
In fastboot and hooked up to your PC in ADB, type fastboot getvar all. The output it gives you will tell you your CID and MID(modelid).
Then look for firmware that matches those.
Or get S-off with sunshine (best $25 you will spend on your phone), and go superCID to flash firmware from any carrier.
Thank you guys for your support. my version list is bellow. So which is the correct firmware version am I looking for?
Got confused again about MID and CID matching numbers
Thank you
< waiting for device >
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.18.0.0000
(bootloader) version-baseband: 1.19.21331147A1.09
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: xxxx
(bootloader) imei: xxxx
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B10000
(bootloader) cidnum: VODAP001
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: 5e4b24e4
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
arnasx69 said:
Thank you guys for your support. my version list is bellow. So which is the correct firmware version am I looking for?
Got confused again about MID and CID matching numbers
Thank you
< waiting for device >
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.18.0.0000
(bootloader) version-baseband: 1.19.21331147A1.09
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: xxxx
(bootloader) imei: xxxx
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B10000
(bootloader) cidnum: VODAP001
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: 5e4b24e4
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
Click to expand...
Click to collapse
This is your MID modelid: 0P6B10000
THIS IS your CID cidnum: VODAP001
Check those guides http://forum.xda-developers.com/htc-one-m8/general/vomerguides-m8-bootldr-unlock-s-off-t2800727
http://http://forum.xda-developers.com/htc-one-m8/development/progress-fuu-m8-t2813792
http://forum.xda-developers.com/showthread.php?t=2736921
http://forum.xda-developers.com/htc-one-m8/development/firmware-flashing-panic-attacks-t2824048 And for the record, HTC phones are not tough to work on( s-off,firmware,recovery,etc) if you can read the guides before you do anything.
Gunman84 said:
This is your MID modelid: 0P6B10000
THIS IS your CID cidnum: VODAP001
Check those guides http://forum.xda-developers.com/htc-one-m8/general/vomerguides-m8-bootldr-unlock-s-off-t2800727
http://http://forum.xda-developers.com/htc-one-m8/development/progress-fuu-m8-t2813792
http://forum.xda-developers.com/showthread.php?t=2736921
http://forum.xda-developers.com/htc-one-m8/development/firmware-flashing-panic-attacks-t2824048 And for the record, HTC phones are not tough to work on( s-off,firmware,recovery,etc) if you can read the guides before you do anything.
Click to expand...
Click to collapse
Thank you for your sarcastic reply. I went through all guides before posting this. But in non of the guides explains how to match these numbers to get a "matching firmware"
Thank you
also éven if he would try on s-on a T-Mobile RUU von vodafone cid it would never work
if you really don't know how to Flash custom roms etc properly please Keep your phone stock!
If you got the stock Rom working i would go S-Off with Sunshine and go Super CID (11111111) with Sunshine.
Then you can flash what ever Rom you want.
arnasx69 said:
Thank you for your sarcastic reply. I went through all guides before posting this. But in non of the guides explains how to match these numbers to get a "matching firmware"
Thank you
Click to expand...
Click to collapse
I'm sorry but you probably missed something. What i would is, S-off, Super CID(fastboot oem writecid 11111111) Super CID "allows you to flash ANY ROM to the device regardless of the carrier" (taken straight from the S-OFF sticky). You can certainly S-OFF, install custom recovery, and begin flashing custom ROMs without Super CID, but you will be limited in your choice of ROMs to those that are the same carrier as you have
CID is the Country Identifier, a code which is stored on your phone and software uses to determine which country or region the phone is for. HTC updates, for example, use it to determine (among other things) which languages to install.
SuperCID is a special code, 11111111, which means that software from any region can be installed. Last, flash recovery and flash new rom
Gunman84 said:
I'm sorry but you probably missed something. What i would is, S-off, Super CID(fastboot oem writecid 11111111) Super CID "allows you to flash ANY ROM to the device regardless of the carrier" (taken straight from the S-OFF sticky). You can certainly S-OFF, install custom recovery, and begin flashing custom ROMs without Super CID, but you will be limited in your choice of ROMs to those that are the same carrier as you have
CID is the Country Identifier, a code which is stored on your phone and software uses to determine which country or region the phone is for. HTC updates, for example, use it to determine (among other things) which languages to install.
SuperCID is a special code, 11111111, which means that software from any region can be installed. Last, flash recovery and flash new rom
Click to expand...
Click to collapse
Actually, CID is Carrier ID, not country identifier.. That's why his says VODAP001 (his carrier being Vodafone) and not his country (whichever of the 21 countries Vodafone is available in)
arnasx69 said:
Thank you guys for your support. my version list is bellow. So which is the correct firmware version am I looking for?
Got confused again about MID and CID matching numbers
Thank you
(bootloader) modelid: 0P6B10000
(bootloader) cidnum: VODAP001
Click to expand...
Click to collapse
Why don't you do the easy way :
1. Flash TWRP - link in my sig
2. Download the stock nandroid backup for your CID/MID - software version no. 2.22.161.6
http://forum.xda-developers.com/showpost.php?p=55302130&postcount=1884
3. Restore that nandroid backup
4. Fastboot flash the stock recovery for 2.22.161.6 - link as above
5. Do OTA to 4.4.4 - software version no. 3.29.161.5
6. Once complete - then you decide whether you want keep it stock or flash custom ROM.
7. If you want to flash custom ROM
a- flash the TWRP again
b- install any GSM based 4.4.4 ROM of your choice - everything should work including wifi
Note : on any case above - no need and don't relock bootloader
ckpv5 said:
Why don't you do the easy way :
1. Flash TWRP - link in my sig
2. Download the stock nandroid backup for your CID/MID - software version no. 2.22.161.6
http://forum.xda-developers.com/showpost.php?p=55302130&postcount=1884
3. Restore that nandroid backup
4. Fastboot flash the stock recovery for 2.22.161.6 - link as above
5. Do OTA to 4.4.4 - software version no. 3.29.161.5
6. Once complete - then you decide whether you want keep it stock or flash custom ROM.
7. If you want to flash custom ROM
a- flash the TWRP again
b- install any GSM based 4.4.4 ROM of your choice - everything should work including wifi
Note : on any case above - no need and don't relock bootloader
Click to expand...
Click to collapse
Best answer I could ever get. Thank you to all who helped me to solve by it looks very simple issue.
And last one is there a way to go back to LOCKED with S-ON, from what I see Firewater is not supporting my phone.
Thanks
arnasx69 said:
Best answer I could ever get. Thank you to all who helped me to solve by it looks very simple issue.
And last one is there a way to go back to LOCKED with S-ON, from what I see Firewater is not supporting my phone.
Thanks
Click to expand...
Click to collapse
No only with sunshine possible, made by same devs but costs 25$ but will 100% s-off your device
Sent from my HTC One m8 with lollipop and Dolby Mobile Plus!
One-M8-Master said:
No only with sunshine possible, made by same devs but costs 25$ but will 100% s-off your device
Sent from my HTC One m8 with lollipop and Dolby Mobile Plus!
Click to expand...
Click to collapse
Not true, not 100 %. Maybe V3 will do that. Keep in mind that the version of sunshine that is now on the market is not working with all the devices.
Hi to all, recently i got my m8 but wifi wont turn on at all. I got soff, unlocked by htcdev, rooted and arhd rom and elemental kernel.
I need help pls i read in a thread about flashing boot. Img for fixing my issue but im confused.
all-in said:
Hi to all, recently i got my m8 but wifi wont turn on at all. I got soff, unlocked by htcdev, rooted and arhd rom and elemental kernel.
I need help pls i read in a thread about flashing boot. Img for fixing my issue but im confused.
Click to expand...
Click to collapse
Check your firmware against your installed rom version - happens when firmware needs update
Htc
Forgot to mention that it wouldnt turn on since it came out the box.
Kernel - 3.4.0 elemental
Baseband - 1.19.21331147a1
Build numb - 3.28.401.9
Htc
Hboot - 3.18.0.0000
Radio- 1.19.21331147a1
Os - doesn't mention anything at all
all-in said:
Forgot to mention that it wouldnt turn on since it came out the box.
Kernel - 3.4.0 elemental
Baseband - 1.19.21331147a1
Build numb - 3.28.401.9
Click to expand...
Click to collapse
Yeah, that baseband is wrong against that 3.28.401.9, update firmware, should be 1.22.223.....
So which firmware you suggest, any link to download a zip to flash?
What about the os that is empty?
all-in said:
So which firmware you suggest, any link to download a zip to flash?
What about the os that is empty?
Click to expand...
Click to collapse
OS is blank because you got custom recovery, probably TWRP - flash firmware from within fastboot -- http://xda7.androidrevolution.org/db_mirror/Firmware/HTC/HTC_One_M8/401/3.28.401.9.zip
ill try this and let u know with what i came up.
i got a message : sending 'zip' (43011 KB)... OKAY [ 4.162s]
writing 'zip'... INFOadopting the signature contained in this image
FAILED (remote: not allowed)
all-in said:
ill try this and let u know with what i came up.
i got a message : sending 'zip' (43011 KB)... OKAY [ 4.162s]
writing 'zip'... INFOadopting the signature contained in this image
FAILED (remote: not allowed)
Click to expand...
Click to collapse
You gotta do - fastboot oem rebootRUU and only then execute the next command
fastboot oem rebootRUU command doesnt do anything so i booted in fastboot my own and this message came up. wana smash the phone on the wall. really omg.
target reported max download size of 1830612992 bytes
sending 'zip' (43011 KB)...
OKAY [ 2.599s]
writing 'zip'...
(bootloader) adopting the signature contained in this image...
(bootloader) zip header checking...
(bootloader) zip info parsing...
FAILED (remote: 99 unknown fail)
finished. total time: 2.858s
the baseband is still 1.19.21.....
is baseband = radio? cant get this to work.
soff
Ok what i need is s-off as i thought i had it. firewater doesnt work anymore as it mentiones in thread. there is sunshine method but it costs 25 dollars. lolz no way. is there another way to gain s off?
Im a bit confused . Please some help guys. I got s-on,does that mean i cant flash another firmware to get my wifi to work?
all-in said:
Im a bit confused . Please some help guys. I got s-on,does that mean i cant flash another firmware to get my wifi to work?
Click to expand...
Click to collapse
I would really recommend you S-Off your device, if you want to flash firmware
otherwise:
1- flash signed firmware incrementally, signed firmware expects previous updates to already be there, so if you skip directly to the last, you'll end up stuck with a high version firmware, but missing previous updates!!!!!!
2- you need to relock your bootloader, for fastboot oem rebootRUU mode flashes to work
Thanks for the response.
i tryed to s-off with firewater but i think this service has stopped?or does it still work as a method?
Device is s-on with unlocked bootloader. I read that with s-on u cant flash kernels-radios-baseband. Is radio equal to baseband? a guy in earlier post said that to get my wifi working i have to update the firmware. Exactly he said that baseband is wrong against that 3.28.401.9, update firmware, should be 1.22.223.
So how do i get that firmware + how i flash it + in what state should the device be?
thats what im asking
all-in said:
Thanks for the response.
i tryed to s-off with firewater but i think this service has stopped?or does it still work as a method?
Device is s-on with unlocked bootloader. I read that with s-on u cant flash kernels-radios-baseband. Is radio equal to baseband? a guy in earlier post said that to get my wifi working i have to update the firmware. Exactly he said that baseband is wrong against that 3.28.401.9, update firmware, should be 1.22.223.
So how do i get that firmware + how i flash it + in what state should the device be?
thats what im asking
Click to expand...
Click to collapse
hi, just a quick FYI, you need to quote (ie reply) or mention (for example @ nkk71 <- without the space) someone, for them to get notified ... otherwise it may go unnoticed.
anyway,
1- firewater is discontinued and in either case was not very suited for the M8 anyway, except for some of the very early models it would have failed. sunshine ($25) is the only known software solution for s-off
2- the response earlier about what you see in Settings->About (3.28.401.9) only refers to the version the ROM (not firmware) is based on
3- the firmware you get from a "fastboot getvar all" from version-main; if that's missing (a bug in some twrp versions), you can make an educated guess by looking at hboot version + radio + date in bootloader
4- radio is equal to baseband, but not equal to firmware.... firmware contains a lot more than just hboot and radio
5- with s-on, you can only flash signed firmwares (these are usually extracted from OTA.zips), and have to match your MID and CID... you also need to have bootloader relocked for RUU mode flash to work
^^ plus, since those are updates, they will only contain whatever was changed from the previous OTA update, that's why if you intend on staying s-on, you should flash those incrementally, and not skip a version
(for example, the "latest" signed firmware could just be an update to hboot or something, but missing all the previous radio, touchscreen, etc updates.... because and official update [by definition] implies all the previous updates were already installed)
hope that helps a bit
nkk71 said:
hi, just a quick FYI, you need to quote (ie reply) or mention (for example @ nkk71 <- without the space) someone, for them to get notified ... otherwise it may go unnoticed.
anyway,
1- firewater is discontinued and in either case was not very suited for the M8 anyway, except for some of the very early models it would have failed. sunshine ($25) is the only known software solution for s-off
2- the response earlier about what you see in Settings->About (3.28.401.9) only refers to the version the ROM (not firmware) is based on
3- the firmware you get from a "fastboot getvar all" from version-main; if that's missing (a bug in some twrp versions), you can make an educated guess by looking at hboot version + radio + date in bootloader
4- radio is equal to baseband, but not equal to firmware.... firmware contains a lot more than just hboot and radio
5- with s-on, you can only flash signed firmwares (these are usually extracted from OTA.zips), and have to match your MID and CID... you also need to have bootloader relocked for RUU mode flash to work
^^ plus, since those are updates, they will only contain whatever was changed from the previous OTA update, that's why if you intend on staying s-on, you should flash those incrementally, and not skip a version
(for example, the "latest" signed firmware could just be an update to hboot or something, but missing all the previous radio, touchscreen, etc updates.... because and official update [by definition] implies all the previous updates were already installed)
hope that helps a bit
Click to expand...
Click to collapse
Ok for start ill relock the device and i come back for further steps.i hope we can fix this.
all-in said:
Ok for start ill relock the device and i come back for further steps.i hope we can fix this.
Click to expand...
Click to collapse
i relocked my device.so what steps do i follow now?
any thread i should follow to get this updates step by step to reach the latest firware.
after some search on the forum i found these http://xda7.androidrevolution.org/db_mirror/Firmware/index.php?dir=HTC%2FHTC_One_M8%2F which i think is the right step, but im confused in which folder should i pick and which firmware updates should i download and flash.
this is my getvar command layout :
C:\adb>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.18.0.0000
(bootloader) version-baseband: 1.19.21331147A1.09G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: SH4ADWM03441
(bootloader) imei: ----------------------
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B10000
(bootloader) cidnum: HTC__304
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: 5e4b24e4
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all-in said:
i relocked my device.so what steps do i follow now?
any thread i should follow to get this updates step by step to reach the latest firware.
after some search on the forum i found these http://xda7.androidrevolution.org/db_mirror/Firmware/index.php?dir=HTC%2FHTC_One_M8%2F which i think is the right step, but im confused in which folder should i pick and which firmware updates should i download and flash.
this is my getvar command layout :
C:\adb>fastboot getvar all
(bootloader) version-bootloader: 3.18.0.0000
(bootloader) version-baseband: 1.19.21331147A1.09G
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) product: m8_ul
(bootloader) modelid: 0P6B10000
(bootloader) cidnum: HTC__304
Click to expand...
Click to collapse
your hboot+baseband version would indicate you are either on 2.22.401.4 or .5 (minor difference)
you should flash in increasing order:
3.28.401.6.zip
3.28.401.7.zip
3.28.401.9.zip
from here: http://xda7.androidrevolution.org/db_mirror/Firmware/index.php?dir=HTC/HTC_One_M8/401/
fastboot oem rebootRUU
fastboot flash zip 3.28.401.6.zip
fastboot flash zip 3.28.401.6.zip <- yes twice, make sure it says successful/finished
fastboot reboot-bootloader
once you are back in bootloader, make sure the OS- line has been updated to the version you flashed, and is not in red (if it is in red, that means the flash didnt complete properly)
then repeat the above commands for the 2 other firmwares
Note: the higher the firmware, the less chances of getting S-OFF, just to let you know
Hi All,
I did a Flash conversion from Stock HTC Sense to GPE on my Taiwan Purchased unlocked unrooted HTC M8. After reboot the phone will not do the OTA even thought it reminds me there is one and the signal strength has been really bad (goes to 0 all the time where it previously was 100% under sense).
These were the steps I followed:
1. Installed TWRP
2. Wiped with TWRP
3. With TWRP i flashed the GPE Rom : MRA58k.h6 release keys - Please not i tried other versions but they all had mid5 failures.
4. rebooted without the root.
After rebooting the phone is fine except the signal strength goes to 0 all the time and i receive the notification for :
system update: "Android M Upgrade for user/release-keys... The message goes on to say, "This is an operating system upgrade for MRA58k.H8. This software will upgrade your device to Android version M including December Security Updates....
After it prepared to install it reboots to twrp. I can find the update in the cache but it fails to install.
I would be happy with either GPE or Sense. Any advice you can offer would be great. Thanks
Post fastboot getvar all result (without serial & imei no.) then we'll see what actually you need to do
Here you go:
C:\adb>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.29.214500021.24_2G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 6.12.709.4
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: *************
(bootloader) imei: *************
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B11000
(bootloader) cidnum: HTC__621
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: 76df2b54
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.047s
NYTWBEN said:
Here you go:
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.29.214500021.24_2G
(bootloader) version-main: 6.12.709.4
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) modelid: 0P6B11000
(bootloader) cidnum: HTC__621
(bootloader) security: on
Click to expand...
Click to collapse
You getvar show that there was never a conversion done. What you did only running a GPE ROM on your device. You can't do conversion on a S-On device.
Since you want to run a GPE ROM .. you should run the latest GPE which is Marshmallow same as your getvar.
You can try what I'm running now - http://forum.xda-developers.com/htc...om-htc-one-m8-gpe-stock-custom-aroma-t3254245
or just search and try other GPE with tag MRA85K.H8 in Development section - there are three of them if I'm not wrong
ckpv5 said:
You getvar show that there was never a conversion done. What you did only running a GPE ROM on your device. You can't do conversion on a S-On device.
Since you want to run a GPE ROM .. you should run the latest GPE which is Marshmallow same as your getvar.
You can try what I'm running now - http://forum.xda-developers.com/htc...om-htc-one-m8-gpe-stock-custom-aroma-t3254245
or just search and try other GPE with tag MRA85K.H8 in Development section - there are three of them if I'm not wrong
Click to expand...
Click to collapse
I tried to flash the Aroma Rom from your link and unfortunately got the following failure message:
C:\adb>fastboot flash zip firmware.zip
target reported max download size of 1826418688 bytes
sending 'zip' (733155 KB)...
OKAY [ 27.528s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) zip info parsing...
FAILED (remote: 24 parsing android-info fail)
finished. total time: 28.514s
You don't need to all those firmware flashing ... remember your device is S-On ?
Won't work for you
Have you ever install a custom ROM before ?
Install TWRP recovery
download the ROM zip
put the ROM zip on your sdcard (either internal or external, your choice)
boot to recovery
select install and browse the ROM zip
install ROM
done... reboot
This is my first time playing with Roms -- Hopefully i will get better over time.
I tried what you said but something NEW is going wrong.
I copied the files to the internal sd card and when i look for them in TWRP they are gone. I rebooted and looked for the files from the file explorer on my computer and they are there now. Also, the files are visible from the ES file explorer app i use. Previously when flashed the rom i was able to copy files onto my internal SD from my desktop.
I don't quite understand what you mean .. but I guess you can see the ROM zip in your internal storage when you connect to PC.
Check which version of TWRP that you installed. You need to use TWRP 2.8.7.0
When in recovery, check mount - enable MTP, you can see the file on PC. If yes, your TWRP should see your ROM zip when select Install menu - make sure the storage is internal storage/sdcard
ckpv5 said:
I don't quite understand what you mean .. but I guess you can see the ROM zip in your internal storage when you connect to PC.
Check which version of TWRP that you installed. You need to use TWRP 2.8.7.0
When in recovery, check mount - enable MTP, you can see the file on PC. If yes, your TWRP should see your ROM zip when select Install menu - make sure the storage is internal storage/sdcard
Click to expand...
Click to collapse
Ok, I had the removable SD card shared as part of of the internal memory (not sure how to describe that). After I separated the removable sd I was able to copy the files over without a problem and the install worked smoothly. Also, the signal strength seems to have improved a bit. It still seems to pop down to no signal at all sometimes but much less frequently.
Thanks for your help!
Ok, So the signal LTE issue is really bad.
With the stock sense rom i was always at full LTE signal now the phone shows either no signal or very low.
Is there an easy way to flash the HTC Sense Rom back on with the phone in its current state (unrooted converted to GPE via TWRP Flash)? I have seen some threads but they all are talking about rooted phones.
Thanks.
With a proper s-off device what's the proper setting/command to get the OTA updates to work?
I had previously modified the CID without any issue - Then via searching, I realized I hadn't changed the MID.
I did that, to match the GPE one, and well I now broke it - Phone wouldn't boot. Did a quick side-load which apparently wiped my entire phone and failed.
So now I have no phone :[ back to the grind with a clean slate I guess
TeckniX said:
I had previously modified the CID without any issue - Then via searching, I realized I hadn't changed the MID.
I did that, to match the GPE one, and well I now broke it - Phone wouldn't boot. Did a quick side-load which apparently wiped my entire phone and failed.
So now I have no phone :[ back to the grind with a clean slate I guess
Click to expand...
Click to collapse
Post fastboot getvar all (without serial & imei no.) .. maybe something can be done to your device.
TeckniX said:
I had previously modified the CID without any issue - Then via searching, I realized I hadn't changed the MID.
I did that, to match the GPE one, and well I now broke it - Phone wouldn't boot. Did a quick side-load which apparently wiped my entire phone and failed.
Click to expand...
Click to collapse
I'm confused about your description. What exactly is the state of the phone (screen won't turn on? Any charge LED?), and did it get that way immediately after issuing the adb command to change the MID? What does this have to do with sideload?
Where did you get the command to change MID, and did you copy/paste it exactly?
How did he convert an "S-ON" phone from stock SENSE to GPE ? Correct me if I am wrong, with Security ON,you cannot write some partitions of system (obviously sense and gpe uses different firmwares and partitions), I think he should flash SENSE or GPE RUU to fix all problems right?
Hi all,
I wasn't really sure how to title this thread, however I have some problems with my phone that I have been trying to sort for a few days, and have reached the limit of my understanding of what I'm reading here and elsewhere. So bear with me and I'll tell you all I know and hopefully someone can help.
I have just bought a used M9 (originally on O2 UK) which I was aware wouldn't boot into anything other than Download or Bootloader. The previous owner had tried to root it and install a custom ROM. On booting it up it hangs on the white HTC One splash screen (I left it overnight)
On booting to download mode I get the following:
***Unlocked
htc_himuahl PVT S-OFF
CID-11111111
MID-0PJAI10000
ColorID-DEF00
LK-1.0.0.0000
RADIO-01.01_U114401011_117.00.61117G_2
OpenDSP-20.7.3.00535.8994_1012
OS-4.14.401.7
NOV 26 2016, 00:36:11(836457)
On booting to bootloader I get the following:
Software Statusfficial
Unlocked
S-OFF
Output from getvar all:
(bootloader) kernel: lk
(bootloader) product: htc_himauhl
(bootloader) version: 1.0
(bootloader) serialno: HT557YJ00558
(bootloader) current-slot:
(bootloader) imei: xxxxxxxxxxxxxxxxx
(bootloader) version-main: 4.14.401.7
(bootloader) boot-mode: download
(bootloader) version-baseband: 01.01_U114401011_117.00.61117G_2_F
(bootloader) version-bootloader: 1.0.0.0000
(bootloader) mid: 0PJA10000
(bootloader) cid: 11111111
Initially on booting to recovery I just got an error message saying that recovery couldn't be loaded and vol up or down to go back to bootloader.
I have since managed to flash TWRP v2.8.5.0 but newer versions of TWRP will not work. They appear to flash OK but on booting to recovery I'm back to the fail to load recovery error.
From TWRP I tried to flash Android Revolution which is a known good copy and running on my other M9. The Aroma installer completes and reports success, but the phone again hangs on the HTC One splash screen (left for over 12 hours).
When flashing Android Revolution using ADB/Fastboot I get
G:\Documents\M9\Minimal ADB and Fastboot>fastboot flash zip AR.zip
target reported max download size of 800000000 bytes
Invalid sparse file format at header magi
error: write_sparse_skip_chunk: don't care size 1698471794 is not a multiple of the block size 4096
sending sparse 'zip' (0 KB)...
error: write_sparse_skip_chunk: don't care size 1698471794 is not a multiple of the block size 4096
error: write_sparse_skip_chunk: don't care size 1698471794 is not a multiple of the block size 4096
OKAY [ 1.011s]
writing 'zip'...
(bootloader) HOSD CL#836547
(bootloader) ERR lzipv1_init : Cannot read header len bytes
(bootloader) ERR lzipv2_init : Cannot open file /dev/fastboot_download_R
(bootloader) ABNBx
(bootloader) ERR preload central directory info failed (EOCD).
FAILED (remote: 99 RU_UNKNOWN_FAIL terrible mishap with original ret: 0)
finished. total time: 3.076s
I also have a known good copy of the original O2 ROM/recovery Package named 0PAIMG which I have used previously to restore my other M9 to stock.
When trying to flash this from TWRP, TWRP reverts to it's own splash screen then restarts.
When trying to flash 0PAIMG from a SD card in the phone I get 12 RU_ZIP_FAIL
When trying to flash 0PAIMG from a PC I get error cannot load 0PJAIMG
It appears that I can flash stock recovery images and back to TWRP with no problem
Any thoughts? And sorry for the long post!
Thanks
Neil
Just flashed M9_1.32.206.14_FullStock_Rename_To_ROM.zip from this site
G:\Documents\M9\Minimal ADB and Fastboot>fastboot flash zip ROM.zip
target reported max download size of 800000000 bytes
sending 'zip' (208044 KB)...
OKAY [ 11.052s]
writing 'zip'...
(bootloader) HOSD CL#506785
(bootloader) GPT is up-to-dated. [17408]
(bootloader) [email protected]
(bootloader) [email protected]%
(bootloader) [email protected]%
(bootloader) [email protected]%
(bootloader) [email protected]%
(bootloader) [email protected]%
(bootloader) [email protected]%
(bootloader) [email protected]%
(bootloader) [email protected]%
(bootloader) [email protected]%
(bootloader) [email protected]%
(bootloader) [email protected]%
(bootloader) [email protected]%
(bootloader) [email protected]%
(bootloader) [email protected]%
(bootloader) [email protected]%
(bootloader) [email protected]%
(bootloader) [email protected]%
(bootloader) [email protected]%
(bootloader) [email protected]%
(bootloader) [email protected]%
(bootloader) [email protected]%
(bootloader) [email protected]%
(bootloader) [email protected]%
(bootloader) [email protected]%
(bootloader) [email protected]%
(bootloader) [email protected]%
(bootloader) [email protected]%
(bootloader) [email protected]%
(bootloader) [email protected]%
(bootloader) [email protected]%
(bootloader) [email protected]%
(bootloader) [email protected]%
(bootloader) [email protected]%
(bootloader) [email protected]%
(bootloader) [email protected]%
(bootloader) [email protected]
(bootloader) Update zip file OK
(bootloader) [email protected]
OKAY [ 69.250s]
finished. total time: 80.303s
Phone hanging on HTC Powered by Android white splash screen.
I'm going to stop trying to flash stuff now and wait for some help.
Thanks
Neil
njc999 said:
OS-4.14.401.7
[...]
(bootloader) version-main: 4.14.401.7
[...]
I also have a known good copy of the original O2 ROM/recovery Package named 0PAIMG which I have used previously to restore my other M9 to stock.
When trying to flash this from TWRP, TWRP reverts to it's own splash screen then restarts.
When trying to flash 0PAIMG from a SD card in the phone I get 12 RU_ZIP_FAIL
When trying to flash 0PAIMG from a PC I get error cannot load 0PJAIMG
Click to expand...
Click to collapse
njc999 said:
Just flashed M9_1.32.206.14_FullStock_Rename_To_ROM.zip from this site
[...]
I'm going to stop trying to flash stuff now and wait for some help
Click to expand...
Click to collapse
Fortunately you stopped flashing. Flashing random files on a S-OFF phone can be really dangerous since the phone won't warn you anymore if you do something wrong.
SKU 401 is the unbranded European firmware and not O2 (=206). And RUUs aren't meant to get flashed via TWRP. You need to flash them either via HTC_fastboot (the normal fastboot will fail) or via an SD card. You couldn't use the O2 RUU since there is no 4.x RUU for that SKU and you can't use 3.x or older RUUs if a phone is running firmware 4.x.
And the phone isn't booting since the firmware pack you flashed doesn't contain a system/rom. It's as the name suggests only the blank firmware. Therefore, if the phone wasn't booting before you started flashing it won't boot after you flashed that firmware pack.
Do yourself a favor and (re-read) the ReadMe thread. After that get the phone back to 3.35.401.12 and install all OTAs up to version 4.14.401.7. If you prefer the O2 branding then use the 3.35.206.13 RUU instead of the 3.35.401.12 one. However, I don't know whether android n is already available for O2...
Flippy498 said:
Fortunately you stopped flashing. Flashing random files on a S-OFF phone can be really dangerous since the phone won't warn you anymore if you do something wrong.
SKU 401 is the unbranded European firmware and not O2 (=206). And RUUs aren't meant to get flashed via TWRP. You need to flash them either via HTC_fastboot (the normal fastboot will fail) or via an SD card. You couldn't use the O2 RUU since there is no 4.x RUU for that SKU and you can't use 3.x or older RUUs if a phone is running firmware 4.x.
And the phone isn't booting since the firmware pack you flashed doesn't contain a system/rom. It's as the name suggests only the blank firmware. Therefore, if the phone wasn't booting before you started flashing it won't boot after you flashed that firmware pack.
Do yourself a favor and (re-read) the ReadMe thread. After that get the phone back to 3.35.401.12 and install all OTAs up to version 4.14.401.7. If you prefer the O2 branding then use the 3.35.206.13 RUU instead of the 3.35.401.12 one. However, I don't know whether android n is already available for O2...
Click to expand...
Click to collapse
mtThanks Flippy. The phone came to me with the 401 firmware installed, but I have to be honest and say that I was unaware that you couldn't just install any firmware on an s-off phone. I bought this M9 very cheaply as a bit of a project to keep me entertained while my broken ankle fixes... and if I got it working to replace the one that I broke when I came off my motorcycle.
Fortunately, I have managed to get the phone to recognise the 0PAIMG.zip file by saving the file on a 4GB sd which I put in the phone, and booting into download mode without a SIM card installed. The phone has now booted up and seems to be doing everything it should.
In download mode I now have:
***unlocked
htc_himauhl PVT S-OFF
CID-11111111
LK-1.0.0.0000
RADIO-01.01_U11440792_93.00.51117G_F
OpenDSP-15.6.1.00522.8994_1026
OS-3.35.206.13
Dec 22 2015, 15:18:13(670363)
In Bootloader mode I have:
***Software Statusfficial
***Unlocked
***S-off
This all looks good now, right?
I have a stock android recovery:
HTC/htc_himauhl/htc_himauhl6.0/MR58Kbuildteam2221509user/release-keys
Assuming all is OK I intend to flash TWRP and then install Android Revolution. I'm confident doing this process and I want to get rid of the 02 bloatware
I'm not sure about installing the OTAs as you suggest as I don't really understand what I'm doing and what files to flash-is it OK to leave this seeing as the phone is now working?
Thanks,
Neil
njc999 said:
The phone came to me with the 401 firmware installed, but I have to be honest and say that I was unaware that you couldn't just install any firmware on an s-off phone.
Click to expand...
Click to collapse
S-OFF means the phone allows you to flash files that aren't signed by HTC. It has nothing to do with the encryption HTC uses.
njc999 said:
CID-11111111
[...]
This all looks good now, right?
Click to expand...
Click to collapse
As explained in the ReadMe thread using a CID that corresponds to your SKU is recommended instead of using the SCID.
njc999 said:
Assuming all is OK I intend to flash TWRP and then install Android Revolution. I'm confident doing this process and I want to get rid of the 02 bloatware
Click to expand...
Click to collapse
Why did you flash a O2 branded RUU on an unbranded phone so that it gets cluttered with O2 bloatware if you want to get rid of the bloatware afterwards? :silly:
njc999 said:
I'm not sure about installing the OTAs as you suggest as I don't really understand what I'm doing and what files to flash-is it OK to leave this seeing as the phone is now working?
Click to expand...
Click to collapse
Why don't you use the software update function of the stock rom (which won't work due to the SCID, at the moment - however, it should work, again, if you change the CID) for that purpose? Be aware that you can't use ARHD if your phone got updated to firmware 4.x since ARHD is EOL and still based on firmware 3.x.
Flippy498 said:
S-OFF means the phone allows you to flash files that aren't signed by HTC. It has nothing to do with the encryption HTC uses.
As explained in the ReadMe thread using a CID that corresponds to your SKU is recommended instead of using the SCID.
Why did you flash a O2 branded RUU on an unbranded phone so that it gets cluttered with O2 bloatware if you want to get rid of the bloatware afterwards? :silly:
Why don't you use the software update function of the stock rom (which won't work due to the SCID, at the moment) for that purpose? Be aware that you can't use ARHD if your phone got updated to firmware 4.x since ARHD is EOL and still based on firmware 3.x.
Click to expand...
Click to collapse
OK I'm going to change the CID to O2___001
I flashed the 02 branded RUU because the phone was originally on 02 when it was new and I thought that this was the best chance of getting it to do something positive. Presumably once I had got back to 3.35.206.13 I could have flashed TWRP then installed Android Revolution straight away? Never said I was an expert lol
Thanks
Neil
If ARHD is your goal and you don't want to install Android n (if it's available for the phone) then you can directly flash TWRP and ARHD from 3.35.206.13.
Sent from my HTC One M9 using XDA Labs
SOLVED - THANKS!
Dear community,
Goal: I want to put a HTC One M8 device into stock. The phone used to be unlocked before and had a custom rom (think it was LineAge).
I already made it to restore it to stock by following the tutorial here in this forum.
Everything fine, but WIFI and bluetooth do not work, I cannot switch them on. I have read that this may be caused by an incompatible firmware version?
Please understand, that I am very new to the topic and have read a lot of stuff, tutorials and because of so many different information and missing experience from my side, I am not sure what to do.
fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.25.214500021.06G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 4.16.401.13
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: ***
(bootloader) imei: ***
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B10000
(bootloader) cidnum: HTC__203
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: f063fb42
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: -0.000s
The phone is now relocked and I cannot access TWRP anymore. Trying to reinstall it using fastboot throws out the following lines:
fastboot flash recovery twrp-3.2.3-1-m8.img
target reported max download size of 1826414592 bytes
sending 'recovery' (20168 KB)...
OKAY [ 1.810s]
writing 'recovery'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 2.528s
Think because the bootloader is locked?
I have really no clue how to proceed.
gskill150 said:
I already made it to restore it to stock by following the tutorial here in this forum.
Everything fine, but WIFI and bluetooth do not work, I cannot switch them on. I have read that this may be caused by an incompatible firmware version?
Click to expand...
Click to collapse
Probably correct, that mostly likely, you restored the wrong TWRP backup version (not compatible with the firmware on the phone - firmware is not the same thing as the ROM or TWRP backup - that part may be confusing).
What version number TWRP backup did you restore (using the guide)?
gskill150 said:
The phone is now relocked and I cannot access TWRP anymore. Trying to reinstall it using fastboot throws out the following lines:
fastboot flash recovery twrp-3.2.3-1-m8.img
target reported max download size of 1826414592 bytes
sending 'recovery' (20168 KB)...
OKAY [ 1.810s]
writing 'recovery'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 2.528s
Think because the bootloader is locked?
Click to expand...
Click to collapse
Yes, this is because you relocked the bootloader. You can't flash a custom recovery with a locked or relocked bootloader, by definition.
But relocking the bootloader is not part of the guide, in regards to restoring a TWRP backup. What exactly were you trying to accomplish the relocking the bootloader?
I took the twrp-3.2.3-1-m8.img (following this instruction out of the tutorial: recommended 2.8.7.0 or latest for 4.xx.xxx.x & 6.xx.xxx.x TWRP backup)
I relocked the bootloader because I Wanted to directly flash the stock RUU using the ruu.zip on SD-Card method.
I dont know if I am allowed to post a link to another forum. According to their Tutorial, if I am S-On and want to flash the stock ruu I Need to lock the bootloader before proceeding. Being already on firmware 4.16.401.13, I dont Need to downgrade it if I flash an image 4.16.401.10 which I found in their image directories. I would try this next. Or what do you recommend?
(bootloader) version-main: 4.16.401.13
-> is this the firmware? I am afraid that I am mixing up firmware and ROM/RUU.
Thanks and best regards
gskill150 said:
I took the twrp-3.2.3-1-m8.img (following this instruction out of the tutorial: recommended 2.8.7.0 or latest for 4.xx.xxx.x & 6.xx.xxx.x TWRP backup)
Click to expand...
Click to collapse
I probably wasn't completely clear, but I was asking: what version number backup (M8 operating system version number) you tried to restore, not the TWRP version number. In other words, which file exactly did you download from the stock backup tutorial you linked? Was it 4.16.401.13 or 6.12.401.4, etc.
gskill150 said:
I relocked the bootloader because I Wanted to directly flash the stock RUU using the ruu.zip on SD-Card method.
I dont know if I am allowed to post a link to another forum. According to their Tutorial, if I am S-On and want to flash the stock ruu I Need to lock the bootloader before proceeding. Being already on firmware 4.16.401.13, I dont Need to downgrade it if I flash an image 4.16.401.10 which I found in their image directories.
Click to expand...
Click to collapse
It would have been best to supply this information up front, all the things you have tried, and the reason for the current status. Otherwise, you see that it is very confusing that you describe for almost the entirety of your top post about trying to restore a stock TWRP backup, but don't mention trying (or intending to) to flash the RUU? Which is a completely different path.
You can't post "clickable" links yet (think you need >10 posts). But you can post the link, then obfuscate it by changing some characters, such as "dotcom", which we can then change back, and cut/paste into the browser to see where you got the file.
I'm not certain what you mean by "their image directories". Do you mean HTC (or something else)? If you mean HTC, then I don't think you have an RUU, since HTC typically does not post RUUs for your version M8. Although there are some "leaked" ones posted by users.
So it's important to know the source of the RUU(?) file you intend to try, such as a link or at least the exact file name of what you downloaded (file size in MB or GB would also be useful to tell what it is).
gskill150 said:
(bootloader) version-main: 4.16.401.13
-> is this the firmware? I am afraid that I am mixing up firmware and ROM/RUU.
Click to expand...
Click to collapse
In short, yes, that is the current version number of the firmware on the phone.
When "firmware" is discussed for this device, it does not refer to the ROM or OS number. But rather, firmware is a small file that is needed for the ROM to work and includes hboot, radio, and a number of other partitions (Bluetooth, WiFI), but does not contain the ROM itself. This is confusing, as some folks like to use the terms "firmware" and "ROM" interchangeably. At least for this device, you should wipe that notion from your mind.
Flashing a custom ROM or restoring a stock TWRP backup will not touch firmware, as flashing a ROM by TWRP will only change the system and boot.img partitions, and not touch things like hboot, radio. And flashing a ROM in TWRP will also not affect the version number reported in getvar. That number will only change if you flash firmware.zip or RUU.
RUU is a complete factory image (40+ partitions) which also includes firmware. Some folks will call the RUU the "stock ROM" but you can now see, it is much more than that.
A little confusing, right?
First of all, many thanks for your detailed help and sorry for providing incomplete information from my side. This topic is really hard to understand and confuses me a lot. Sorry for that.
redpoint73 said:
I probably wasn't completely clear, but I was asking: what version number backup (M8 operating system version number) you tried to restore, not the TWRP version number. In other words, which file exactly did you download from the stock backup tutorial you linked? Was it 4.16.401.13 or 6.12.401.4, etc.
Click to expand...
Click to collapse
I took, 4.16.401.13 out of www DOT mega DOT nz/#!X9IjVASb!bNCxQJlDbX40cLHGlmP1qk0SaYfW93lo8jicFv81B-4
It would have been best to supply this information up front, all the things you have tried, and the reason for the current status. Otherwise, you see that it is very confusing that you describe for almost the entirety of your top post about trying to restore a stock TWRP backup, but don't mention trying (or intending to) to flash the RUU? Which is a completely different path.
Click to expand...
Click to collapse
Sorry for that - as written I am new to the topic and was mixing up things that do not belong together (RUU, ROM, firmware). Again in a few words: phone used to have LineAgeOS (CustomRom) and I just wanted get rid of it and restore the original android version as if I had bought the phone completely new
I tried it through TWRP because I found this tutorial here in the forum and thought this would be the right path.
You can't post "clickable" links yet (think you need >10 posts). But you can post the link, then obfuscate it by changing some characters, such as "dotcom", which we can then change back, and cut/paste into the browser to see where you got the file.
Click to expand...
Click to collapse
As next steps and after having relocked the bootloader I was planning to perform the steps mentioned in this tutorial (sorry it is German) in the Page: www DOT handy-faq DOT de/forum/htc-one-m8-stock-rom-wiederherstellen-via-ruu-t314727/
and doing method 1 (flashing RUU using RUU.zip) with the use of a RUU 4.16.401.10 (which can be found on www DOT androidfilehost DOT com/?fid=95916177934518148
I'm not certain what you mean by "their image directories". Do you mean HTC (or something else)? If you mean HTC, then I don't think you have an RUU, since HTC typically does not post RUUs for your version M8. Although there are some "leaked" ones posted by users.
So it's important to know the source of the RUU(?) file you intend to try, such as a link or at least the exact file name of what you downloaded (file size in MB or GB would also be useful to tell what it is).
Click to expand...
Click to collapse
I meant the RUUs from the other guide I have just posted above
A little confusing, right?
Click to expand...
Click to collapse
To be honest, now it is completely clear to me thanks to your really good explanation. Thanks mate!
So I could go for the ruu.zip flashing path to achieve what I want right?
gskill150 said:
I took, 4.16.401.13 out of www DOT mega DOT nz/#!X9IjVASb!bNCxQJlDbX40cLHGlmP1qk0SaYfW93lo8jicFv81B-4
Click to expand...
Click to collapse
That is the right number stock backup to restore (same number as firmware number - version main in getvar). I don't know why you are having issues with WiFi and Bluetooth.
Might be a problem with the firmware. Flashing RUU is probably the best approach. Not only will it restore the stock ROM, but also restore stock firmware. Which hopefully will resolve your WiFi and Bluetooth issue.
gskill150 said:
As next steps and after having relocked the bootloader I was planning to perform the steps mentioned in this tutorial (sorry it is German) in the Page: www DOT handy-faq DOT de/forum/htc-one-m8-stock-rom-wiederherstellen-via-ruu-t314727/
and doing method 1 (flashing RUU using RUU.zip) with the use of a RUU 4.16.401.10 (which can be found on www DOT androidfilehost DOT com/?fid=95916177934518148
So I could go for the ruu.zip flashing path to achieve what I want right?
Click to expand...
Click to collapse
That RUU should be okay. Alternately, you can flash the Marshmallow RUU, which will not only restore you to stock image, but also have the most updated (last) version. Marshmallow RUU and instructions here: https://forum.xda-developers.com/showpost.php?p=64926626&postcount=6
Note, that you should use the htc_fastboot as directed in the instructions, not the "generic" Google fastboot. The generic one can't handle the large RUU file size (about 1.5 GB).
redpoint73 said:
Alternately, you can flash the Marshmallow RUU, which will not only restore you to stock image, but also have the most updated (last) version. Marshmallow RUU and instructions here: https://forum.xda-developers.com/showpost.php?p=64926626&postcount=6
Note, that you should use the htc_fastboot as directed in the instructions, not the "generic" Google fastboot. The generic one can't handle the large RUU file size (about 1.5 GB).
Click to expand...
Click to collapse
Hi, thanks for your reply. I will give it a try! :good:
gskill150 said:
Hi, thanks for your reply. I will give it a try! :good:
Click to expand...
Click to collapse
It worked using the guide I posted (with the ruu.exe).
Issue solved. Wifi Problem fixed. Learned a lot! Appreciating this Forum and especially your help so much. Thanks!!!
gskill150 said:
It worked using the guide I posted (with the ruu.exe).
Issue solved. Wifi Problem fixed. Learned a lot! Appreciating this Forum and especially your help so much. Thanks!!!
Click to expand...
Click to collapse
You're quite welcome. Glad it worked for you.
Hello guys,
I have an HTC one m8 , I have been running a rooted device with custom rom which has been working terribly on my device...Now I want to return to stock rom, I have relocked bootloader and it's on s-on...I have tried out diverse RUU but all seems not working...I'm always getting this error in the process "rom update utility cannot update your andriod phone"" which i guess the ruu's have been using are not compatible with my phone...I would so much appreciate if anyone can get me the RUU executable file for my device that will be compatible with it........ Here is the fastboot getvar all details....Your prompt responses will be appreciated
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.29.214500021.12G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: S**********6
(bootloader) imei: 35*************7
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B10000
(bootloader) cidnum: T-MOB009
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: 76df2b54
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.062s
Jjohnson0830 said:
I have tried out diverse RUU but all seems not working...
(bootloader) modelid: 0P6B10000
(bootloader) cidnum: T-MOB009
Click to expand...
Click to collapse
You can't just guess at which RUU and expect it to work. The RUU needs to match the CID/MID on your version M8. And your version M8, I'm pretty sure doesn't even have an RUU. So whatever you tried, was the wrong RUU.
Return to stock using the stock TWRP backup, where you also posted.
On that note, please don't post the same question to multiple threads. It won't get you help any faster. It just confuses you and those trying to help you. Do you really intend on checking and updating 3 different threads, if folks start helping you in different places? That never happens.
redpoint73 said:
You can't just guess at which RUU and expect it to work. The RUU needs to match the CID/MID on your version M8. And your version M8, I'm pretty sure doesn't even have an RUU. So whatever you tried, was the wrong RUU.
Return to stock using the stock TWRP backup, where you also posted.
On that note, please don't post the same question to multiple threads. It won't get you help any faster. It just confuses you and those trying to help you. Do you really intend on checking and updating 3 different threads, if folks start helping you in different places? That never happens.
Click to expand...
Click to collapse
Ok, pls where can i get the stock TWRP backup and how am i going to return to stock using it?
Thanks and sorry again for what happened, I mean crossing posts...I think i needed to just respond to your responses on all the 3 threads i posted...it won't repeat itself again
Jjohnson0830 said:
Thanks and sorry again for what happened, I mean crossing posts...I think i needed to just respond to your responses on all the 3 threads i posted...it won't repeat itself again
Click to expand...
Click to collapse
No, you really don't. Please.