Develop Bugs

Final Stock RUU 3.35.617.12 for HTC One M9, need Help

hello,
i found this RUU a few hrs ago and i am not sure it works or not and when yes, OTA upgrades works also or not ??
http://www.androidpolice.com/2015/1...0-1-to-the-unlocked-one-a9-6-0-to-the-one-m9/
i am unlocked and S-Off,
(bootloader) kernel: lk
(bootloader) product: htc_himaulatt
(bootloader) version: 1.0
(bootloader) imei:
(bootloader) version-main: 3.35.617.12
(bootloader) boot-mode: download
(bootloader) version-baseband: 01.01_U11440792_97.00.51203G_F
(bootloader) version-bootloader: 1.0.0.0000
(bootloader) mid: 0PJA10000
(bootloader) cid: 11111111
all:
finished. total time: 0.015s
thx regards

lollopatrollo said:
hello,
i found this RUU a few hrs ago and i am not sure it works or not and when yes, OTA upgrades works also or not ??
http://www.androidpolice.com/2015/1...0-1-to-the-unlocked-one-a9-6-0-to-the-one-m9/
i am unlocked and S-Off,
(bootloader) kernel: lk
(bootloader) product: htc_himaulatt
(bootloader) version: 1.0
(bootloader) imei:
(bootloader) version-main: 3.35.617.12
(bootloader) boot-mode: download
(bootloader) version-baseband: 01.01_U11440792_97.00.51203G_F
(bootloader) version-bootloader: 1.0.0.0000
(bootloader) mid: 0PJA10000
(bootloader) cid: 11111111
all:
finished. total time: 0.015s
thx regards
Click to expand...
Click to collapse
Are you asking a question or what?
Your clearly already on Android 6
Sent from my HTC One M9 using Tapatalk

clsA said:
Are you asking a question or what?
Your clearly already on Android 6
Sent from my HTC One M9 using Tapatalk
Click to expand...
Click to collapse
Op is asking if ota still work with that rom.

yes it is a questiopn, cause my is my system based on non signet RUU firmware. i donmt have a clean RUU and dont get OTA updates. it works very bad and slow + i dont understand really how i can install TWRP on the m9. i found a few options but i need a RUU/OTA to create a bootable 0PJAIMG.zip right ? found something like that in here XDA
"You can make your own zip version. You just need an android-info.txt file from an RUU (or firmware.zip from OTA). Zip it up with the TWRP image (renamed to recovery.img) and place on the root of your FAT32-formatted SD card in download mode."
so all what i m looking for is a fresh clean install, recieve OTA updates and a little stability, thats why i ask. do u know why i dont get OTA updates ? maybe i did a mistake...
thx

shivadow said:
Op is asking if ota still work with that rom.
Click to expand...
Click to collapse
yes, works all good. my problem is still to create a working 0PJAIMG.zip with TWRP without brick the phone. it s not my phone, i flash it for a friend and he want to use viper venom.
is it possible to flash it without TWRP on the phone ? maybe with ADB or something. think get the stock OTA files is not really important for him too..
thnx guys, many hrs no sleep brain burns ^^
regards

lollopatrollo said:
yes, works all good. my problem is still to create a working 0PJAIMG.zip with TWRP without brick the phone. it s not my phone, i flash it for a friend and he want to use viper venom.
is it possible to flash it without TWRP on the phone ? maybe with ADB or something. think get the stock OTA files is not really important for him too..
thnx guys, many hrs no sleep brain burns ^^
regards
Click to expand...
Click to collapse
if you install TWRP and root your phone at all you will not get OTA updates
if you want OTA you cannot install custom recovery and root.
The only way to get OTA is by having untouched system partition and Stock recovery
The links below in my Signature contain all the files and links you need to...
1.convert and update your phone to DevEd Android 6
2.Install TWRP and SuperSU 2.64
3.and the files needed to return to stock later if another OTA is released

Thanks for this! =D just what i needed!!!

Hello, and VERY sorry to cross post, but my phone is unusable and I wasn't getting any response in the T-Mobile section. Here is what I asked:
I have been searching through XDA for a couple of hours now, and now I must post. Sorry if this has been answered and I just couldn't find the right post.
I have been trying to follow instructions to return my T-Mobile HTC One M9 to stock using RUU, but every time I attempt to flash the RUU, I get this:
target reported max download size of 800000000 bytes
Invalid sparse file format at header magi
error: write_sparse_skip_chunk: don't care size 1349472896 is not a multiple of the block size 4096
error: write_sparse_skip_chunk: don't care size 542282368 is not a multiple of the block size 4096
sending sparse 'zip' (781102 KB)...
error: write_sparse_skip_chunk: don't care size 1349472896 is not a multiple of the block size 4096
error: write_sparse_skip_chunk: don't care size 1349472896 is not a multiple of the block size 4096
OKAY [ 52.307s]
writing 'zip'...
(bootloader) HOSD CL#505029
(bootloader) ERR [SD_UPDATE_ERR] update_fb_ZIP_buf: can not find ZIP hea
(bootloader) der
(bootloader) ERR [SD_UPDATE_ERR] sddownload failed: 22
(bootloader) ERR Update zip file failed.
(bootloader) ERR ZIP ERROR, exit read zip loop
(bootloader) Update zip file OK
(bootloader) ERR ZIP ERROR CODE, 22
(bootloader) [email protected]
FAILED (remote: 22: fail to flash via downloadzip)
finished. total time: 54.408s
I have re-downloaded, re-flashed firmware, but can't seem to get it to complete. Any help would be most appreciated.
Click to expand...
Click to collapse

its just AT&T or all can flash it?

Unrooted HTC M8 Stock Converted to GPE - Won't OTA and Phone Signal Issues

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?

Hard bricked after flashed inapporiate version of firmware

I originally want to downgrade from 7.0 to 6.0, so I restored stock 6.0 twrp backup. But it stuck on bootloop, so silly me thought "must be a firmware problem, I should try flash 6.0 firmware".(same one as my twrp backup version)
OKAY [ 4.123s]
writing 'zip'...
(bootloader) HOSD CL#857212
(bootloader) Perform pre-update
(bootloader) get 12 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]
FAILED (remote: 90 hboot pre-update! please flush image again immediately )
finished. total time: 6.217s
After flashed firmware.zip extracted from ota's, I'm unable to boot anymore - charging screen screen won't even appear!
Of course, adb's not responding..
1. What exactly have I done wrong? I'd like to learn from mistakes.
2. Except from jtag, is warranty my only way out?
Thank you guys for your answer!

29988122 said:
I originally want to downgrade from 7.0 to 6.0, so I restored stock 6.0 twrp backup. But it stuck on bootloop, so silly me thought "must be a firmware problem, I should try flash 6.0 firmware".(same one as my twrp backup version)
OKAY [ 4.123s]
writing 'zip'...
(bootloader) HOSD CL#857212
(bootloader) Perform pre-update
(bootloader) get 12 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]
FAILED (remote: 90 hboot pre-update! please flush image again immediately )
finished. total time: 6.217s
After flashed firmware.zip extracted from ota's, I'm unable to boot anymore - charging screen screen won't even appear!
Of course, adb's not responding..
1. What exactly have I done wrong? I'd like to learn from mistakes.
2. Except from jtag, is warranty my only way out?
Thank you guys for your answer!
Click to expand...
Click to collapse
...you didn't flash the firmware, just executed the hboot pre-update.
You would have had to enter and run the fastboot flash zip command again, as it clearly said there.
Edit: your fault was to flash an incremental firmware that you extracted from an ota. You would have had to flash a full/combined firmware from @Sneakyghost 's thread.

29988122 said:
I originally want to downgrade from 7.0 to 6.0, so I restored stock 6.0 twrp backup. But it stuck on bootloop, so silly me thought "must be a firmware problem, I should try flash 6.0 firmware".(same one as my twrp backup version)
OKAY [ 4.123s]
writing 'zip'...
(bootloader) HOSD CL#857212
(bootloader) Perform pre-update
(bootloader) get 12 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]
FAILED (remote: 90 hboot pre-update! please flush image again immediately )
finished. total time: 6.217s
After flashed firmware.zip extracted from ota's, I'm unable to boot anymore - charging screen screen won't even appear!
Of course, adb's not responding..
1. What exactly have I done wrong? I'd like to learn from mistakes.
2. Except from jtag, is warranty my only way out?
Thank you guys for your answer!
Click to expand...
Click to collapse
You fault was, that you used a incremental ota firmware, for the downgrade.
You should have used a RUU or minimum a full firmware package, for the downgrade.
Edit:
You still have access to the bootloader?
Or is the device completely dead?
Sent from my HTC 10 using XDA Labs

Black-FR said:
You fault was, that you used a incremental ota firmware, for the downgrade.
You should have used a RUU or minimum a full firmware package, for the downgrade.
Edit:
You still have access to the bootloader?
Or is the device completely dead?
Sent from my HTC 10 using XDA Labs
Click to expand...
Click to collapse
Thank you for bearing with me - a noob.
I checked Sneakyghost's full firmware thread, but it seemed that I need at least access to bootloader.
The problem is - the device is completely dead, tried up volume+down volume+power button combo, no avail.
Also, while connected to PC, adb shown no device founded. Therefore no adb reboot bootloader.

29988122 said:
Thank you for bearing with me - a noob.
I checked Sneakyghost's full firmware thread, but it seemed that I need at least access to bootloader.
The problem is - the device is completely dead, tried up volume+down volume+power button combo, no avail.
Also, while connected to PC, adb shown no device founded. Therefore no adb reboot bootloader.
Click to expand...
Click to collapse
If there is no reaction of the device, while you push and hold the three buttons (power + volume up + volume down), for approximately 10 second to 1 minute, then it's most likely a hard brick.
And yes, you would need fastboot connection in the boot loader, to flash single firmware partitions.
But without access to the boot loader, is your device pretty much dead now.
Sent from my HTC 10 using XDA Labs

Black-FR said:
You fault was, that you used a incremental ota firmware, for the downgrade.
You should have used a RUU or minimum a full firmware package, for the downgrade.
Edit:
You still have access to the bootloader?
Or is the device completely dead?
Sent from my HTC 10 using XDA Labs
Click to expand...
Click to collapse
Black-FR said:
If there is no reaction of the device, while you push and hold the three buttons (power + volume up + volume down), for approximately 10 second to 1 minute, then it's most likely a hard brick.
And yes, you would need fastboot connection in the boot loader, to flash single firmware partitions.
But without access to the boot loader, is your device pretty much dead now.
Sent from my HTC 10 using XDA Labs
Click to expand...
Click to collapse
Guess warranty is the only way out : (
At least I learned a lesson. Next time I'll flash full firmware instead of incremented ones!

29988122 said:
Guess warranty is the only way out : (
At least I learned a lesson. Next time I'll flash full firmware instead of incremented ones!
Click to expand...
Click to collapse
mine is in the same state. after trying to update to newest nougat fw
apparently i either had a bad download or bad sdcard. its a damn good lesson learned for sure
did you do the warranty route? if so, did they charge you or did they replace the device?

Ouch! Yep, that's a bricker. I highly doubt you will have a claim to a warranty. Worth a try though. You guys should always go with the full RUU from HTC whenever possible. Even sneakyghost will tell you that is the safest route. You can upgrade or downgrade your device with the RUU and it has everything you need. Good luck on the next one.

-4ndr01d- said:
mine is in the same state. after trying to update to newest nougat fw
apparently i either had a bad download or bad sdcard. its a damn good lesson learned for sure
did you do the warranty route? if so, did they charge you or did they replace the device?
Click to expand...
Click to collapse
They replaced the motherboard for me. The only cost comes from another purchase of sunshine.
Disclaimer: I live in Taiwan, where htc's headquarter is, your experience might differ.

29988122 said:
They replaced the motherboard for me. The only cost comes from another purchase of sunshine.
Disclaimer: I live in Taiwan, where htc's headquarter is, your experience might differ.
Click to expand...
Click to collapse
ah, I see. so I'm guessing all photos and things are lost when getting a new mobo (wishful thinking)

[SOLVED] Need some help update my phone from 5.0.1 to 6.0

Hi.
first off i have to say im completely new to this, and been googling all day for how to update my phone from 5.0.1 to 6.0 as it doesnt get it automatic but cant find what i feel is the right way for me. so i feel pretty stuck
this far i figure i most likely have an asian modell of m8, would like to upgrade it so i later on will get automatic updates (if it will ever be more coming for this one )
so as a noob i need some help on how to solve this issue
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.24.21331147A1.09G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 4.18.708.12
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: **************
(bootloader) imei: **************
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B13000
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: 3aa067db
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0

you can update it using RUU.zip
however you have s-off device which is heavily modified ( supercid,dev ed or t mobile mid and Asian firmware )
so if you want t update the current firmware then
downoad this RUU
https://mega.nz/#!nQUTEQgS!705whK7tyPvtUgUQwLenweGTJepoHQDeBgsiHhrYVlQ
and follow this instruction to flash it
https://forum.xda-developers.com/showpost.php?p=64926626&postcount=6
start from "2. Download htc_fastboot.exe" all the steps and files before this step is not for you
p.s backup your files before flashing as the RUU will wipe your internal storage

that didnt work to well, tryed several times (even with different usb ports, same result)
C:\htc>htc_fastboot.exe flash zip RUU.zip
sending 'zip'... (53966 KB) OKAY
sending time = 3.056 secs
writing 'zip'... (bootloader) rom parsing start ...
(bootloader) rom parsing finish ...
(bootloader) zip header checking...
(bootloader) zip info parsing...
FAILED (status read failed (Too many links))
Execution time is 3(s)

rmhalvorsen said:
that didnt work to well, tryed several times (even with different usb ports, same result)
C:\htc>htc_fastboot.exe flash zip RUU.zip
sending 'zip'... (53966 KB) OKAY
sending time = 3.056 secs
writing 'zip'... (bootloader) rom parsing start ...
(bootloader) rom parsing finish ...
(bootloader) zip header checking...
(bootloader) zip info parsing...
FAILED (status read failed (Too many links))
Execution time is 3(s)
Click to expand...
Click to collapse
try the other method to flash the RUU
rename the RUU to 0P6BIMG.zip then put it in sd card ( formatted as fat32 ) and reboot to bootloader ( hboot )
it will scan for the file and asks to flash it just confirm
let's see how this goes

uhm, nope thats not working eighter
cant see/mount card when booted normally eighter

rmhalvorsen said:
uhm, nope thats not working eighter
cant see/mount card when booted normally eighter
Click to expand...
Click to collapse
try to flash this firmware first ( flash using the same commands i the earlier guide i linked above )
https://mega.nz/#!bMpgkRrY!74hn2pGPKaX6aQhNDchSany6JmRtROm-zeozzhoSWac
note: if you are not on the stock rom/kernel flashing the firmware will wipe the os so you will need to flash the firmware then flash the RUU
after flash the firmware with success reboot to bootloader then reboot to RUU mode and flash the RUU again
if you see this error “Error 90 hboot pre-update..." repeat the flashing command again immediately

Failed
C:\htc>htc_fastboot flash zip fw_6.16.708.1.zip
sending 'zip'... (53849 KB) OKAY
sending time = 3.025 secs
writing 'zip'... (bootloader) zip header checking...
(bootloader) shift signature_size for header checking...
(bootloader) zip info parsing...
(bootloader) checking model ID...
FAIL41 model id check fail
FAILED (remote: 41 model id check fail)
Execution time is 4(s)

rmhalvorsen said:
Failed
C:\htc>htc_fastboot flash zip fw_6.16.708.1.zip
sending 'zip'... (53849 KB) OKAY
sending time = 3.025 secs
writing 'zip'... (bootloader) zip header checking...
(bootloader) shift signature_size for header checking...
(bootloader) zip info parsing...
(bootloader) checking model ID...
FAIL41 model id check fail
FAILED (remote: 41 model id check fail)
Execution time is 4(s)
Click to expand...
Click to collapse
that's because your mid is 0P6B13000 and cid supercid
the right mid for this firmware is 0P6B63000 and cid HTC__622
you have tow options
1- flash the developer edition marshmallow firmware and RRU.exe
2-change the MID to 0P6B63000 and flash the asian firmware/RUU again
your choice and i think both options are valid for you
option 1
flash this firmware https://mega.nz/#!iZJHDKZK!wKL6TkHz8u5eXA6HfhUfgPDdfeTcCZMxygc9Mm_GGg8
then reboot to bootloader and run this RUU.exe from your pc as a normal app http://www.htc.com/us/support/htc-one-m8/news/
direct link for the RUU.exe
http://dl3.htc.com/application/RUU_...2.1540.4.exe?_ga=1.5739063.5870829.1473114560
option 2
change the mid to 0P6B63000
reboot to twrp ( flash it if you don't yet ) and connect your device to pc
type this 4 commands in cmd window ( press enter after each command )
adb shell
Code:
echo -ne '\x30\x00\x50\x00\x36\x00\x42\x00\x36\x00\x33\x00\x30\x00\x30\x00\x30' | dd of=/dev/block/mmcblk0p5 bs=1 seek=16384
the above command is very sensitive and long command just copy and paste it not write it your self
exit
adb reboot bootloader
then flash the firmware again and followed by the RUU
source for change mid https://forum.xda-developers.com/showthread.php?t=2708581
your mid command isn't available in this thread i edited a close one to be valid for 0P6B63000 ( i'm not an expert )
and i recommend you to choose option 1 ( any way it's your choice following my own command or use the most trusted option 1 )

flash firmware was sucessful.
but the ruu.exe loads up and i accept the terms and hit next, then the app just dies/quits, only thing i see is that languagebar icon flashes when this happends
im running genuine windows 7 64bit, does it need to be runned in a compability mode of some sort ?

rmhalvorsen said:
flash firmware was sucessful.
but the ruu.exe loads up and i accept the terms and hit next, then the app just dies/quits, only thing i see is that languagebar icon flashes when this happends
im running genuine windows 7 64bit, does it need to be runned in a compability mode of some sort ?
Click to expand...
Click to collapse
Try again with RUU and if possible reboot both devices ( pc and phone )
try with another usb port
Windows 7 is the most compatible os to run the RUU so try again
Sent from my HTC M8 using XDA Labs

still a no go, tried all 4 availible usb ports and rebooted between them all, downloaded ruu once more . still app just dies when i accept and hit next

now i have tried from another two computers, with just the same result, ruu.exe dies upon accepting terms and hitting next.

rmhalvorsen said:
now i have tried from another two computers, with just the same result, ruu.exe dies upon accepting terms and hitting next.
Click to expand...
Click to collapse
you are missing some libraries
download and install this
https://www.microsoft.com/en-us/download/details.aspx?id=26368
then run the RUU again

there it goes, worked perfectly and now up and running updated
thanks a lot for your time struggeling with my noobyness, would not have get this done right without you.
atleast now i know what to do next time i buy a new phone on ebay
just one last question, if i now go into meny or hboot and do factory reset, will it restores it to current flashed image again or mess things up? just so i dont mess this up in a year or so, if things starts to hang up

rmhalvorsen said:
there it goes, worked perfectly and now up and running updated
thanks a lot for your time struggeling with my noobyness, would not have get this done right without you.
Click to expand...
Click to collapse
there is a button for that
rmhalvorsen said:
just one last question, if i now go into meny or hboot and do factory reset, will it restores it to current flashed image again or mess things up? just so i dont mess this up in a year or so, if things starts to hang up
Click to expand...
Click to collapse
no worry you are on complete stock state anytime you will make a factory reset it will just wipe the user data
but no need for that now as it already wiped everything on the device :good:

Good to know
Guess this thread can me marked as SOLVED! :good:

rmhalvorsen said:
Guess this thread can me marked as SOLVED! :good:
Click to expand...
Click to collapse
If you like, you can do that yourself, by going to the top post and editing the thread title to add [SOLVED].
The mods don't go around looking for threads to mark as solved.

will it be possible to flash my phone with this one ? 0P6BIMG_M8_UL_M60_SENSE70_MR_HTC_Europe_6.12.401.4_Radio_1.29.214500021.12G_20.72.4196t.01_release_464360_signed
.zip
maybe im wrong but i think maybe this would be my solution to get lte/4g working for telenor norway, as it wont connect to other then gprs/hspa now.
??

rmhalvorsen said:
will it be possible to flash my phone with this one ? 0P6BIMG_M8_UL_M60_SENSE70_MR_HTC_Europe_6.12.401.4_Radio_1.29.214500021.12G_20.72.4196t.01_release_464360_signed
.zip
maybe im wrong but i think maybe this would be my solution to get lte/4g working for telenor norway, as it wont connect to other then gprs/hspa now.
??
Click to expand...
Click to collapse
Looks like you already answered this question yourself based on the thread you started here: https://forum.xda-developers.com/htc-one-m8/help/help-to-change-radio-basebands-htc-one-t3582804
Please try to avoid bouncing around to different threads. Or at a minimum, if you answer your own question, go back and post what the solution was, so folks don't waste time trying to help you with a question which was already self answered.

noted edited this to solved
well, can atleast say that the rom worked on my phone....(but did not solve the problem in my other thread.)

Boot or sound after flashing ROM'S , maybe a firmware issue?

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!