Develop Bugs

Phone turns off after going to sleep not sure where I went wrong.

Hi guys,
I am having problems with my phone. Whenever I flash I ROM and the phone goes to sleep it turns off and reboots. Here is what I have done to the phone. Please tell me what I did wrong or what I need to do.
Started with a AT&T HTC One M9
Purchased an unlock code and Network unlocked the device
Rooted the device
S-Off
SuperCID
Then flashed Venom ROM
I have tried some other ROM's as well and they are doing the same thing.
I am using an AT&T Straight Talk SIM with service active.
Thanks guys,
Rocky

grimreaper1014 said:
Hi guys,
I am having problems with my phone. Whenever I flash I ROM and the phone goes to sleep it turns off and reboots. Here is what I have done to the phone. Please tell me what I did wrong or what I need to do.
Started with a AT&T HTC One M9
Purchased an unlock code and Network unlocked the device
Rooted the device
S-Off
Then flashed Venom ROM
I have tried some other ROM's as well and they are doing the same thing.
I am using an AT&T Straight Talk SIM with service active.
Thanks guys,
Rocky
Click to expand...
Click to collapse
Check to see if your firmware matches the base of the ROMs that you are flashing

grimreaper1014 said:
Hi guys,
I am having problems with my phone. Whenever I flash I ROM and the phone goes to sleep it turns off and reboots. Here is what I have done to the phone. Please tell me what I did wrong or what I need to do.
Started with a AT&T HTC One M9
Purchased an unlock code and Network unlocked the device
Rooted the device
S-Off
Then flashed Venom ROM
I have tried some other ROM's as well and they are doing the same thing.
I am using an AT&T Straight Talk SIM with service active.
Thanks guys,
Rocky
Click to expand...
Click to collapse
You need to update your firmware or flash a 1.32 kernel. You're running a 1.40-based rom on top of your original firmware. This will cause reboots on waking the phone. It is a well-known issue.

Thanks for your help guys. Where can I get the firmware I need?

[/COLOR]
grimreaper1014 said:
Thanks for your help guys. Where can I get the firmware I need?
Click to expand...
Click to collapse
Make sure you read all info and do not skip anything, also have a back up made in case you run into any issues.
(edit: added link, make sure you find the one that matches your phone and CID.)
(edit 2: added 3rd link)
http://forum.xda-developers.com/one-m9/development/firmware-t3068243
http://forum.xda-developers.com/one-m9/development/ota-1-32-401-15-firmware-noredtext-t3072571
http://forum.xda-developers.com/one-m9/general/stock-nand-backup-ota-update-collection-t3132698

I forgot to mention I have SuperCID as well. Therefore, I need to flash the international 1.40 firmware right? I think where I screwed up at is I'm not sure if the phone was updated to the latest factory firmware before root, s-off, and supercid.

grimreaper1014 said:
I forgot to mention I have SuperCID as well. Therefore, I need to flash the international 1.40 firmware right? I think where I screwed up at is I'm not sure if the phone was updated to the latest factory firmware before root, s-off, and supercid.
Click to expand...
Click to collapse
Check out first link, I'm pretty sure your answer will be somewhere in the thread.

This is so complicated. I wish I would of bought the Nexus 6. Yeah I can't get it to flash. I think I got a $700 brick. I haven't been able to use my phone for over a week because of this crap.
C:\Users\Rocky\adb>fastboot flash zip ROM.zip
target reported max download size of 800000000 bytes
sending 'zip' (61704 KB)...
OKAY [ 4.015s]
writing 'zip'...
(bootloader) HOSD CL#549783
(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) Update zip file OK
(bootloader) [email protected]
OKAY [ 7.727s]
finished. total time: 11.742s
Now I'm stuck here.
For “pre-update FAIL 90 ..." do:
- Let the phone reboot itself into Download Mode. If it doesn't boot to download mode, force it back there (From Android with adb reboot download or with the button method, see "step 1").
- If the flash does not auto-resume, run the same flash command again which you just ran (press arrow up on your keyboard to get to the previous command in console)
I have tried everything it says but phone just stays one the screen with the phone image with the bar that indicates its flashing.

grimreaper1014 said:
This is so complicated. I wish I would of bought the Nexus 6. Yeah I can't get it to flash. I think I got a $700 brick. I haven't been able to use my phone for over a week because of this crap.
C:\Users\Rocky\AppData>fastboot flash zip ROM.zip
error: cannot load 'ROM.zip'
Click to expand...
Click to collapse
Nah I don't think it's bricked, that is if you can access the download mode screen where you flash via fastboot. You need to ask a dev that knows more about this stuff

BUBBA DUB'S said:
Nah I don't think it's bricked, that is if you can access the download mode screen where you flash via fastboot. You need to ask a dev that knows more about this stuff
Click to expand...
Click to collapse
I don't even know how to contact any. I need my phone so I can make calls to get my car repaired. I hit a deer on the way to work and need to get it repaired. Can't even setup an appointment.
I have tried typing abd reboot download
C:\Users\Rocky\adb>adb reboot download
error: device not found
I have tried holding Vol+Down
I get nothing... It won't reboot.
I have tried reflashing
It just hangs at the flashing screen
It must be flashed it went all the way through with no error 90 it just doesn't reboot. So I guess I will just flash a ROM and see what happens.

It says ok and 100% behind each image except the touch panel drivers and the sensor hub, which is ok.
The flash was ok and you're good to go. The phone is fine. Just place a ROM on your sdcard and reflash that now. Then wait 10-30 minutes for IT to boot (depending on the number of apps you have, the optimizing of ART cache can take very long).
Mobile Post

Sneakyghost said:
It says ok and 100% behind each image except the touch panel drivers and the sensor hub, which is ok.
The flash was ok and you're good to go. The phone is fine. Just place a ROM on your sdcard and reflash that now. Then wait 10-30 minutes for IT to boot (depending on the number of apps you have, the optimizing of ART cache can take very long).
Mobile Post
Click to expand...
Click to collapse
Thanks for your reply. Will I have to do this every time I flash a new ROM or will it always be done now? I was able to get it working one other time but as soon as I flashed ElementalX it started doing the reboot thing again. I really want to use ElementalX.

ElementalX is currently based on an older 1.32 kernel and requires you to run old firmware. So either go back to 1.32 firmware or wait till Flar2 releases a 1.40 kernel.
And usually you don't have to always update your firmware - often times, ROM's run fine on non-matching firmware. You just have to be aware of the fact that HTC's intention is to keep firmware and ROM at the same development level, there is no support whatsoever for a firmware/ROM mismatch. For that reason, most ROM devs also recommend to update firmware when the ROM updates. This is the simple version of the story - it can get more complex. Just memorize that keeping firmware and ROM at the same level is a very good idea and that you will receive no support anywhere if you don't.

help plzzz my m9 dead failed to boot to download mode

no recovery
no download mode
***LOKED***
***S-ON***

Details please.
What can you boot into, if anything? (Bootloader, system, recovery & download mode).
What variant do you have (CID & MID, if possible)?
What did you do that brought your phone to this point?

computerslayer said:
Details please.
What can you boot into, if anything? (Bootloader, system, recovery & download mode).
What variant do you have (CID & MID, if possible)?
What did you do that brought your phone to this point?
Click to expand...
Click to collapse
Reading information...
Using Fastboot mode...
Reading common information
(bootloader) version:0.5
(bootloader) variant:MTP eMMC
(bootloader) secure:yes
(bootloader) version-baseband:
(bootloader) version-bootloader:
(bootloader) max-download-size: 0x20000000
(bootloader) partition-type:cache:ext4
(bootloader) partition-size:cache: 0x14000000
(bootloader) partition-type:userdata:ext4
(bootloader) partition-size:userdata: 0x5e0000000
(bootloader) partition-type:system:ext4
(bootloader) partition-size:system: 0x118000000
(bootloader) serialno:HT53SYJ09030
Execution time is 140(ms)
all:
Reading secure flag information
... (bootloader) read secure flag: 3
Execution time is 15(ms)
OKAY
Reading CID information
Execution time is 15(ms)
... FAILunknown command
FAILED (remote: unknown command)
Reading MEID information
Execution time is 15(ms)
... FAILunknown command
FAILED (remote: unknown command)
Read information failed

aboelgasim said:
Reading information...
Using Fastboot mode...
Reading common information
(bootloader) version:0.5
(bootloader) variant:MTP eMMC
(bootloader) secure:yes
(bootloader) version-baseband:
(bootloader) version-bootloader:
(bootloader) max-download-size: 0x20000000
(bootloader) partition-type:cache:ext4
(bootloader) partition-size:cache: 0x14000000
(bootloader) partition-type:userdata:ext4
(bootloader) partition-size:userdata: 0x5e0000000
(bootloader) partition-type:system:ext4
(bootloader) partition-size:system: 0x118000000
(bootloader) serialno:HT53SYJ09030
Execution time is 140(ms)
all:
Reading secure flag information
... (bootloader) read secure flag: 3
Execution time is 15(ms)
OKAY
Reading CID information
Execution time is 15(ms)
... FAILunknown command
FAILED (remote: unknown command)
Reading MEID information
Execution time is 15(ms)
... FAILunknown command
FAILED (remote: unknown command)
Read information failed
Click to expand...
Click to collapse
mod- 0PJA110
CID 11111111

aboelgasim said:
mod- 0PJA110
CID 11111111
Click to expand...
Click to collapse
Excellent. Tell us about what happened to get to this point. Also, what can you boot into, if anything?

Your MID indicates that you have the unlocked/developer edition of the phone, so my advice would be to use the RUU for that device. You'll have to boot into the bootloader and connect your phone to a PC (this RUU won't run on any other operating system), but it should restore your phone completely to stock.
Be aware that using a RUU is a destructive restore - it'll wipe everything on the phone.
(It's weird that you're S-ON and yet have a CID of 11111111, which is the SuperCID. Changing the CID is only possible after S-OFF.)

extract hosd.img from your firmware.zip and flash via fastboot in bootloader. You should be able to boot to DL mode again.

side_flip15 said:
extract hosd.img from your firmware.zip and flash via fastboot in bootloader. You should be able to boot to DL mode again.
Click to expand...
Click to collapse
Awesome! I would never have thought of that. Another reason I love XDA.

computerslayer said:
Excellent. Tell us about what happened to get to this point. Also, what can you boot into, if anything?
Click to expand...
Click to collapse
after back s-on

computerslayer said:
Awesome! I would never have thought of that. Another reason I love XDA.
Click to expand...
Click to collapse
C:\Program Files\Minimal ADB and Fastboot>fastboot flash hosd hosd_signed.img
target reported max download size of 536870912 bytes
sending 'hosd' (38128 KB)...
OKAY [ 1.544s]
writing 'hosd'...
OKAY [ 0.671s]
finished. total time: 2.231s
but i still cant open download mode

I notice there is still no explanation on how the device got to this stage. I advise waiting until op explains before committing.
Sent from my HTC One M9 using Tapatalk

My suggestion was based from my experience. I got the same problem before. Not sure how it happened but flashing hosd fixes my device.
You can try flashing hosd from any 3.35.xxx firmware. I'm on dev edition firmware but hosd does not work, tried hosd from 401 and it worked.

shivadow said:
I notice there is still no explanation on how the device got to this stage. I advise waiting until op explains before committing.
Sent from my HTC One M9 using Tapatalk
Click to expand...
Click to collapse
I wanted to back s-on

side_flip15 said:
My suggestion was based from my experience. I got the same problem before. Not sure how it happened but flashing hosd fixes my device.
You can try flashing hosd from any 3.35.xxx firmware. I'm on dev edition firmware but hosd does not work, tried hosd from 401 and it worked.
Click to expand...
Click to collapse
search abote 3.35.401 firmware ???

So what did you do? Tell us the steps you took that caused your phone to be in this state.

aboelgasim said:
no recovery
no download mode
***LOKED***
***S-ON***
Click to expand...
Click to collapse
What have you done to get the phone into this state?.
If you do not tell us what you have done so far, we cannot help you.
computerslayer said:
Your MID indicates that you have the unlocked/developer edition of the phone, so my advice would be to use the RUU for that device. You'll have to boot into the bootloader and connect your phone to a PC (this RUU won't run on any other operating system), but it should restore your phone completely to stock.
Be aware that using a RUU is a destructive restore - it'll wipe everything on the phone.
(It's weird that you're S-ON and yet have a CID of 11111111, which is the SuperCID. Changing the CID is only possible after S-OFF.)
Click to expand...
Click to collapse
Borked it trying to get supercid on an s-on phone?
Sent from my HTC One M9 using Tapatalk

computerslayer said:
So what did you do? Tell us the steps you took that caused your phone to be in this state.
Click to expand...
Click to collapse
try back s-on by xtc2clip by SD mode editor

aboelgasim said:
try back s-on by xtc2clip by SD mode editor
Click to expand...
Click to collapse
Right. So, what steps did you take? Describe, in detail, what you did.
Then describe the state of your phone right now. For example, can your phone boot into the a)system or b)the bootloader or c)download mode or d)recovery or e)more than one of these (which ones)?
One sentence descriptions are not enough - you're giving answers with so little detail that we can't give reliable advice.

Exactly what happened to me.
Was playing with the xtc2clip returning back to s-on using sd mode. Ended up with corrupted download mode.
Try flashing hosd from .401. It should fix the problem.

side_flip15 said:
Exactly what happened to me.
Was playing with the xtc2clip returning back to s-on using sd mode. Ended up with corrupted download mode.
Try flashing hosd from .401. It should fix the problem.
Click to expand...
Click to collapse
send any link blzzz

M9 possible partition corruption?

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] 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!