Related
Hi. After I have rooted my phone, there is a problem with update from HTC. I receive the update (1.40.401.8) over air and download it, but it stops at team win recovery project (2.8.6.0) after reboot. Anyone with same problem ?
Please help...
olesol70 said:
Hi. After I have rooted my phone, there is a problem with update from HTC. I receive the update (1.40.401.8) over air and download it, but it stops at team win recovery project (2.8.6.0) after reboot. Anyone with same problem ?
Please help...
Click to expand...
Click to collapse
Dude....you should really read....
The general thread is full with topics about how to take a ota update when you are rooted.
When you change your system like when rooting and with that a custom recovery you can't just take a ota update!
Guessing you didn't make a system backup before you rooted either? You need this if you want to take a ota.
Now the only way is to restore a ruu or use someone else their system backup.
All of this is mention in the treads where you learn how to root....
Before you try to restore a unmodified system image or ruu .....READ!
You need to use your correct image and ruu. Not any ruu or image will do.!!!
Sent from my HTC One M9 using XDA Free mobile app
Hi
Not sure if I understand what you mean, but my phone works just fine. I just have to reboot after "no go" with teamwin.
What you are saying, is that it is not possible to install updates om my phone ?
Ole
dannylow79 said:
Dude....you should really read....
The general thread is full with topics about how to take a ota update when you are rooted.
When you change your system like when rooting and with that a custom recovery you can't just take a ota update!
Guessing you didn't make a system backup before you rooted either? You need this if you want to take a ota.
Now the only way is to restore a ruu or use someone else their system backup.
All of this is mention in the treads where you learn how to root....
Before you try to restore a unmodified system image or ruu .....READ!
You need to use your correct image and ruu. Not any ruu or image will do.!!!
Sent from my HTC One M9 using XDA Free mobile app
Click to expand...
Click to collapse
If you want to take ota updates then you need to run a RUU for your device to put it back to stock then OTA updates will work.
You can not flash/install a OTA update with a custom recovery (TWRP)
Sent from my HTC One M9 using Tapatalk
You have to be 100% stock to take an OTA. It's a security feature to prevent bricks. Even having /system mounted r/w will cause an OTA to fail.
Taking OTAs when rooted is generally a bad idea anyway. I have seen people brick their phones in the past doing it, though they are so locked down now that I doubt it's possible on this phone.
Let me see if I understand...
-U bought a m9
-unlocked your boot loader.
-installed TWRP
-rooted your m9
-u got a message to install the update 1.40
-now u are stuck at TWRP?
If this is the case, you can't install the update correctly because your device is not stock.
By stock I mean:
- non rooted
- stock recovery
- stock unmodified system.
Without being stock your update will fail.
If I didn't understand correctly, please explain.
Sent from my HTC One M9 using XDA Free mobile app
Hi, that is correct, but I manage to reboot the phone and it works just fine. I only want the lates battery and camera improvements. I have tried this:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash zip firmware_M9.zip
target reported max download size of 800000000 bytes
sending 'zip' (111548 KB)...
OKAY [ 6.404s]
writing 'zip'...
(bootloader) HOSD CL#506785
(bootloader) GPT is up-to-dated. [17408]
(bootloader) Perform pre-update
(bootloader) ERR ZIP signature checking failed...
(bootloader) ERR [SD_UPDATE_ERR] Not allow flash image except boot/recov
(bootloader) ery/system
(bootloader) ERR [SD_UPDATE_ERR] sddownload failed: 14
(bootloader) ERR Update zip file failed.
(bootloader) Update zip file OK
(bootloader) ERR ZIP ERROR CODE, 14
(bootloader) [email protected]
FAILED (remote: 14: fail to flash via downloadzip)
finished. total time: 10.530s
You have to be s-off to flash an unsigned firmware package.
olesol70 said:
Hi, that is correct, but I manage to reboot the phone and it works just fine. I only want the lates battery and camera improvements. I have tried this:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash zip firmware_M9.zip
target reported max download size of 800000000 bytes
sending 'zip' (111548 KB)...
OKAY [ 6.404s]
writing 'zip'...
(bootloader) HOSD CL#506785
(bootloader) GPT is up-to-dated. [17408]
(bootloader) Perform pre-update
(bootloader) ERR ZIP signature checking failed...
(bootloader) ERR [SD_UPDATE_ERR] Not allow flash image except boot/recov
(bootloader) ery/system
(bootloader) ERR [SD_UPDATE_ERR] sddownload failed: 14
(bootloader) ERR Update zip file failed.
(bootloader) Update zip file OK
(bootloader) ERR ZIP ERROR CODE, 14
(bootloader) [email protected]
FAILED (remote: 14: fail to flash via downloadzip)
finished. total time: 10.530s
Click to expand...
Click to collapse
http://forum.xda-developers.com/one-m9/general/best-unlocking-bootloader-rooting-guide-t3087354
Read from step 5....( better read it all ?)
You'll be OK.
Sent from my HTC One M9 using XDA Free mobile app
Thanks guys. It worked!!
What i did was S-off with sundhine.
Second I followed a guide on naldotech dot com how-to-flash-ruu-firmware-htc-one-m9
All perfect now. I also now will remember to backup when I root.
Have a nice weekend.
olesol70 said:
Thanks guys. It worked!!
What i did was S-off with sundhine.
Second I followed a guide on naldotech dot com how-to-flash-ruu-firmware-htc-one-m9
All perfect now. I also now will remember to backup when I root.
Have a nice weekend.
Click to expand...
Click to collapse
Glad it worked! Have a nice weekend too!
Sent from my HTC One M9 using XDA Free mobile app
Hi hoping someone can help me - I've just wasted two days trying to get my phone to work again, but right now, it only goes to the bootloader.
I have HTC One M9, with S-ON, rooted, with TWRP bootloader installed. I can not get any ROMs to install at all - actually, they do install, just don't boot. I believe this is because I don't have the correct firmware version installed. I can't get any firmware to install. When trying to update firmware, I get;-
Code:
fastboot flash zip firmware_M9.ziptarget reported max download size of 800000000 bytes
sending 'zip' (61607 KB)...
OKAY [ 5.419s]
writing 'zip'...
(bootloader) HOSD CL#576582
(bootloader) ERR [SD_UPDATE_ERR] Main version NOT ALLOWED
(bootloader) ERR [SD_UPDATE_ERR] sddownload failed: 19
(bootloader) ERR Update zip file failed.
(bootloader) ERR ZIP ERROR, exit read zip loop
(bootloader) ERR ZIP signature checking failed...
(bootloader) Update zip file OK
(bootloader) ERR ZIP ERROR CODE, 19
(bootloader) [email protected]
I think this is because of the S-ON.
Can someone please help me, otherwise I'm going to have to throw this thing in the bin, and buy a new phone?
Thanks, Seth
Ok - so I've progressed, in as much as I've managed to put an old unofficial copy of CM12 on it. This has at least got me up and running.
Now need to get it back to Stock so I can patch firmware, and then install latest version of CM13.
Only, all the guides I read, say to flash Stock you need S-OFF - which I can only achieve by running Sunshine unlock - but I can't run Sunshine Unlock on this unofficial version of CM12.
Does anyone have any ideas they can throw my way? Thanks
SethHelstrip said:
Hi hoping someone can help me - I've just wasted two days trying to get my phone to work again, but right now, it only goes to the bootloader.
I have HTC One M9, with S-ON, rooted, with TWRP bootloader installed. I can not get any ROMs to install at all - actually, they do install, just don't boot. I believe this is because I don't have the correct firmware version installed. I can't get any firmware to install. When trying to update firmware, I get;-
Code:
fastboot flash zip firmware_M9.ziptarget reported max download size of 800000000 bytes
sending 'zip' (61607 KB)...
OKAY [ 5.419s]
writing 'zip'...
(bootloader) HOSD CL#576582
(bootloader) ERR [SD_UPDATE_ERR] Main version NOT ALLOWED
(bootloader) ERR [SD_UPDATE_ERR] sddownload failed: 19
(bootloader) ERR Update zip file failed.
(bootloader) ERR ZIP ERROR, exit read zip loop
(bootloader) ERR ZIP signature checking failed...
(bootloader) Update zip file OK
(bootloader) ERR ZIP ERROR CODE, 19
(bootloader) [email protected]
I think this is because of the S-ON.
Can someone please help me, otherwise I'm going to have to throw this thing in the bin, and buy a new phone?
Thanks, Seth
Click to expand...
Click to collapse
Buddy once u install the rom, take the boot.img frm the rom zip file & flash it via adb in bootloader mode it will flash evn if ur s-on, custom roms need their respective boot.img files to be flashed when s-on in case of s-off its done by twrp or cwm recovery hope it helps
Hi Seth,
So the great news is that you do not need to be S-OFF to upgrade your firmware, which is what it sounds like you need to do.
Unfortunately, you can't take an OTA update, so you need to flash an RUU. While this will reset your phone (wiping everything but your SD card), it will also get your phone up to date.
Do you know which variant of the M9 you have? Once you get that information, you can use download the appropriate RUU and flash it to your phone. I've included some links below that are helpful - I especially recommend Flippy498's Google sheet, which has almost everything you need (with instructions!) to update your firmware.
Peace,
Computerslayer
Useful links for modding your HTC M9
Flippy498's Google Sheet
- the end-all, be-all resource for HTC M9 restoration
SKU-, CID- and MID-List by Sneakyghost and Behold_this
- a spreadsheet for using your CID & MID to identify your phone
HTC Sync Manager
- installs the necessary drivers & ADB tools for the HTC M9
Instructions for obtaining your CID, MID & software version on Windows:
a. Install HTC Sync Manager (this will install the necessary drivers & ADB tools)
b. Boot your phone into download mode (from a powered off state, turn on by holding the POWER+DOWNVOL)
c. Connect your phone to your PC
d. Open a command prompt window
e. Navigate to the ADB tools folder, typically C:\Program Files (x86)\HTC\HTC Sync Manager\HTC Sync
- assuming the path is correct, you can cut & paste this command into your terminal: cd C:\Program Files (x86)\HTC\HTC Sync Manager\HTC Sync
f. Execute the following command in a terminal (command prompt): fastboot getvar all
g. Copy the lines that mention product, version-main, mid, and cid.
still sinking....
Thanks for the info guys. So I decided the best path was to RUU back to Stock then upgrade firmware OTA.
So, I tried to connect phone to HTC Sync Manager, but get the dreaded USB can't connect 170 error - even though the OS can see the phone, and its memory card fine.
So I decided to try Ubuntu to extract the RUU, so I can just patch it on SD card. However, I can't get the unruu program to compile properly, because its got some error with the required version of unshield.
So I'm at a dead-end, and resisting putting a hammer through the screen of this phone, which has now cost me about 4 days worth of effort - and still doesn't work.
The only thing I've managed to get working on it so far, is a crappy unofficial copy of CM12 - that crashes about 15-20 times a day.
Can anyone please offer me some advice, or a stock rom.zip for an unlocked m9?
SethHelstrip said:
Thanks for the info guys. So I decided the best path was to RUU back to Stock then upgrade firmware OTA.
So, I tried to connect phone to HTC Sync Manager, but get the dreaded USB can't connect 170 error - even though the OS can see the phone, and its memory card fine.
So I decided to try Ubuntu to extract the RUU, so I can just patch it on SD card. However, I can't get the unruu program to compile properly, because its got some error with the required version of unshield.
So I'm at a dead-end, and resisting putting a hammer through the screen of this phone, which has now cost me about 4 days worth of effort - and still doesn't work.
The only thing I've managed to get working on it so far, is a crappy unofficial copy of CM12 - that crashes about 15-20 times a day.
Can anyone please offer me some advice, or a stock rom.zip for an unlocked m9?
Click to expand...
Click to collapse
If you can pull you CID & MID, it'll be easy to identify which RUU you need. Most are easily found online.
So more progress. Having relocked my bootloader, I am now able to get the HTC RUU exe to connect to the phone from Windows. Only problem now is that I'm getting the
ERROR [155]: UNKNOWN ERROR
this makes me think I've got the wrong RUU. I'm pretty sure I've got the correct SKU, but not sure about the rest of it. From running fastboot getvar all I get;-
(bootloader) kernel: lk
(bootloader) product: htc_himauhl
(bootloader) version: 1.0
(bootloader) version-main: 2.10.401.1
(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: HTC__001
all:
And I'm using the
RUU_HIMA_UHL_L50_SENSE70_HTC_Europe_1.32.401.17_Radio_01.01_U11440261_56.02.50306G_2_F_release_429340_signed_2_4.exe
Can someone please help me - I now have a phone that won't go beyond the bootloader. Thanks
Ok, so I think the problem here, is the RUU I have is a downgrade from the existing version. With that in mind, can someone please help me out massively by pointing me in the direction of the correct RUU?
Thanks again.
https://www.google.com/url?q=https:...835000&usg=AFQjCNH9n1vZCmPvw5wWJ10C1wFJqx6YYA
Use this. Rename it to 0PJAIMG.zip copy it to your externel sd card. Reboot to download mode and press vol up than wait. Your phone will have latest firmware with 6.0
awesome - thanks for your help
SOLVED UPDATE: I did some more reading. I took the Bell (BM) rom zip
(named "0PJAIMG_HIMA_UL_L50_SENSE70_ATT_BM_1.32.666.6_R2_Radio_01.01_U11440221_59.04.50303G_2_F_release_426170_signed.zip"), and renamed it to "0PJAIMG.zip".
Copied that to the root of a microSD card and put that into the phone.
Booted phone with VOLDOWN+POWER and the flash process began. It rebooted a couple of times during the process. It said to hit POWER to finish. After that, phone booted normally (like out-of-the-box again).
With that said, I still would like to have root... so would still appreciate any input as to what I did wrong below. Thank you!
Hello. I'm afraid I have messed my phone up a bit, and would really appreciate it if someone could help me out.
It's a Bell HTC One M9 (0PJA110), and it is (was?) on 5.0.2 Lollipop. According to the RUU EXE I just tried (unsuccessfully), it says it is an image version (or HTC system version) 1.32.666.6.
Here's what I did, from out-of-the-box. I just wanted root access so I could use Titanium Backup, so I read a bunch of threads to get started. I thought I had gathered enough knowledge, so I:
1) Unlocked bootloader via htcdev
2) Flashed "htc-one-m9-lollipop-twrp-2.8.7.0-hima.img" to recovery. (I chose this version because I read in some threads that version 3 or higher of twrp doesn't work well if it is flashed to a Lollipop phone).
3) Rebooted, went immediately into recovery (so that TWRP could ensure it doesn't get overwritten)
4) Then rebooted again, and went into recovery (to make sure TWRP was still there)
5) At this point, I should have let the phone boot normally, to make sure that was OK. But I did not... so I cannot tell if this is where my trouble began
6) Next, in TWRP, I flashed "SR1-SuperSU-v2.79-SR1-20161221223537.zip". It seemed to go well.
7) Reboot from TWRP.
8) Phone shows first HTC logo, then goes to a black screen (black but illuminated). That's it.
My next thing to try was this Bell TWRP zip from a nice post on here. Filename is "Stock_Bell_LP_5.0.1_1.32.666.30_TWRP.zip". I tried to flash it via TWRP but it failed right away (I do not have the exact output but can try again to get the text, it if that helps).
Naturally I was starting to get worried, so I immediately started looking for RUU's so I could start over.
1) I re-locked bootloader
2) I tried a generic RUU ("RUU_HIMA_UL_M60_SENSE70_ATT_MR_NA_Gen_Unlock_3.35.617.31.exe") but it would not flash - I assume it is checking CID and knows it's not correct for my phone
3) I downloaded a Bell-specific zip from Androidruu ("0PJAIMG_HIMA_UL_L50_SENSE70_ATT_BM_1.32.666.6_R2_Radio_01.01_U11440221_59.04.50303G_2_F_release_426170_signed.zip", verified the MD5 matched whatever androidruu.com said it was.
4) Renamed the zip to rom.zip to make the next commands easier
5) Ran "fastboot oem rebootRUU", verified the RUU screen appeared, then "fastboot flash zip rom.zip"
It didn't work Here is the output:
Code:
target reported max download size of 800000000 bytes
Invalid sparse file format at header magi
sending sparse 'zip' (67085 KB)...
OKAY [ 4.791s]
writing 'zip'...
(bootloader) HOSD CL#493992
(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) ERR ZIP signature checking failed...
(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: 8.552s
I wish I could try a Bell RUU exe... but I am having a hell of a time finding one.
Any advice would be appreciated (regarding anything I did wrong up above, or regarding how I can get myself out of this mess). Thank you for reading.
Download the latest RUU to your device. In dowload mode type fastboot oem rebootRUU. Entering the Htc screen, run RUU.exe.
Dark Stranger said:
Download the latest RUU to your device. In dowload mode type fastboot oem rebootRUU. Entering the Htc screen, run RUU.exe.
Click to expand...
Click to collapse
Thank you, but same result as my earlier attempt. The EXE itself can get the phone from bootloader mode/download mode into RUU mode, and it starts the process, but fails with "please get the correct rom update utility".
I assume it's because this RUU is not an exact match for my phone.
So today I had issues flashing LeeDroid which I want for some super battery saving where apparently it was good for that. Anyway in the end the sim card wasn't being recognized and it was really buggy and I went and reread the thread on LeeDroid and it said something about updating firmware. So then I stumble upon RUUs and that looked like the way to go to update all firmware and all that lovely jazz so I downloaded the international/developer one (as I got mine in Australia with code himauhl) but it gave me error 132 and said signature error, so I double checked the numbers, my phone has OS-3.38.841.6 where I think I need to match the RUU with the three digit number in that thing so the 841, however, HTC doesn't provide an RUU for the One M9 with 841. I did some research but nothing came up so I was hoping you guys could help me out.
By the way I have S-On but I am not prepared to pay $25 for S-Off, which is why I'm trying to use this method.
Phone is currently running latest version of Lineage OS 14.1
(Quick stat reminder: HTC One M9, himauhl, OS-3.38.841.6)
THANKS IN ADVANCE!
Edit:
So after further research I found: www.androidruu.com
I managed to find an ruu for my phone but a little problem. I'm on version 3.38.841..... and this ruu is on 1.32.841...... that means that I probably need S-Off to do it? I know you can't downgrade firmwares without S-Off so I think now the answer is to try harder to find a later ruu? Just needing some confirmation and hoping someone might know a better way. Thanks!
Edit 2:
My adventure continues. I managed to get S-Off, eventually gave up and paid for Sunshine, oh well. Anyway! I then used the htc_fastboot commands to change my cid to BS_US001 and then my mid to OPJA11000 and I thought all was well and good HOWEVER the RUU.exe for the developer version still returns error 132 and even using the htc_fastboot so flash the 4.30.612.12 zip file returned a ERR Model ID not matched and Model ID Not allowed. I have no idea what I'm doing at this stage, any ideas are truly most welcome. Thanks!
Edit 3:
At this stage I'm still not sure of the problem. My actual device model is the OPJA100 and I changed it to OPJA11000 and tried to flash an RUU with the same MID (11000) but to no success. Then I changed my CID to the super 11111111 but still with no success. I'm going to try to get a ruu.zip and then change the info.txt modlid to OPJA100 to see how that goes.
Edit 4:
I AM A COMPLETE IDIOT!!!!
I am sorry if I have wasted anyone's time, but it was all due to one little typo, turns out the RUU I had was for 0PJA11000 (ALL ZEROS) where I had OPJA11000 (First O was the letter O) hence causing the stuff up.
Hope this helps someone out there too! CHECK YOUR OOOOSSSSSS
So, just to further define the issue a bit more here is an error dump:
D:\Android Platform-Tools>htc_fastboot flash zip 0PJAIMG.zip
htc_fastboot v3.0.9.2 (2015-05-29)
found large-zip header, file count: 7
processing file 1/7...
sending 'zip' (92974 KB)...
OKAY [ 5.352s]
writing 'zip'...
(bootloader) HOSD CL#683910
(bootloader) ERR Model ID not matched
(bootloader) ERR [SD_UPDATE_ERR] MODEL ID NOT ALLOWED
(bootloader) ERR [SD_UPDATE_ERR] sddownload failed: 10
(bootloader) ERR Update zip file failed.
(bootloader) ERR ZIP ERROR, exit read zip loop
(bootloader) Update zip file OK
(bootloader) ERR ZIP ERROR CODE, 10
(bootloader) [email protected]
FAILED (remote: 10 RU_MODELID_FAIL modelid in android-info mismatched )
finished. total time: 7.473s
htc_fastboot finished. total time: 8.548s
I am suffering from a bootloop in my phone, lineage suddenly decided to crash trebuchet, and phone turned off. Bootloader works, download mode works, recovery absolutely DOES NOT, It gives me the black HTC logo and turns off and on when I put the "fastboot oem lock" option, and just redirects back to the bootloop when I don't. I can use fastboot to flash files to it, I flashed TWRP old and new, but nonetheless, it bootloops when picking recovery once more. I have S-ON, with the bootloader unlocked. I'd love to buy the sunny license and turn S-OFF, but have no way of accessing my OS anymore.
Here are my details.
(bootloader) kernel: lk
(bootloader) product: htc_himawhl
(bootloader) version: 1.0
(bootloader) version-main: 3.41.651.4
(bootloader) boot-mode: download
(bootloader) version-baseband: [email protected]
(bootloader) version-bootloader: 1.0.0.0000
(bootloader) mid: 0PJA20000
(bootloader) cid: SPCS_001
Here is my recovery flashing log
target reported max download size of 800000000 bytes
sending 'recovery' (20084 KB)...
OKAY [ 2.097s]
writing 'recovery'...
(bootloader) HOSD CL#695981
(bootloader) [email protected]
(bootloader) [email protected]%
(bootloader) Update partition OK
(bootloader) [email protected]
OKAY [ 1.838s]
finished. total time: 3.939s
I've tried flashing a signed stock ROM, but I know I need to re-lock the bootloader, the "fastboot oem lock" option doesn't work too well either, it just resets without actually locking anything. It can't hold a flash it seems.
(bootloader) [KillSwitch] : /dev/block/bootdevice/by-name/frp (bootloader) [KillSwitch] Last Byte is 0X01, enable unlock (bootloader) RELOCK device
I've tried the "0PJAIMG.zip" method in download mode, but it just gives me these errors as well.
22 RU_HEADER_ERROR
22 RU_HEADER_ERROR
FAIL22 RU_HEADER_ERROR
If my phone gets a file that matches up, it freezes for a bit, THEN goes back to another bootloop. It's frustrating.
9 RU_SECURITY_FAIL is also another error I get when trying to flash the .zip by fastboot, they're so annoying.
target reported max download size of 800000000 bytes
Invalid sparse file format at header magi
error: write_sparse_skip_chunk: don't care size 2136250206 is not a multiple of the block size 4096
sending sparse 'zip' 1/1 (0 KB)...
error: write_sparse_skip_chunk: don't care size 2136250206 is not a multiple of the block size 4096
error: write_sparse_skip_chunk: don't care size 2136250206 is not a multiple of the block size 4096
OKAY [ 1.028s]
writing 'zip' 1/1...
(bootloader) HOSD CL#695981
FAILED (remote: 9 RU_SECURITY_FAIL zip from usb command in download mode)
finished. total time: 2.053s
Then after that, I tried flashing "0PJAIMG_HIMA_WHL_L50_SENSE70_SPCS_Sprint_WWE_1.32.651.17_Radio_1.10.C1144022_50312.5_NV_SPCS_0.23_003_release_425355_signed_RYDAH805.zip" via download mode with the SD card, and it gave me a FAIL19 RU_MAIN_VER_FAIL error that I don't understand that well, but I did find a reddit thread on it. I may have messed up my partitions.
https://www.reddit.com/r/AndroidQuestions/comments/69i53h/help_with_htc_m9_fail19_ru_main_ver_fail/
HOSD is also yet another method that ends up in failure
sending 'hosd' (38148 KB)... OKAY
writing 'hosd'... (bootloader) HOSD CL#695981
FAIL35 RU_PARTITION_NOT_SUPPORT hosd
FAILED (remote: 35 RU_PARTITION_NOT_SUPPORT hosd)
Execution time is 4(s)
Here are a list of things that DIDN'T work
-Firmware Flashing
-Boot/TWRP Flashing
-fastboot oem unlock
-the "Power then Volume up" trick, it just redirects me to a white HTC splash screeen
-Recovery from bootloader option
-signed .img files
https://androidforums.com/threads/htc-one-m8-brick-stuck-on-boot.927336/
After finding the thread above, I'm starting to think it might be a hardware error, it now gives me a "Failed to boot to recovery mode" error,. The eMMc may be messed up, ughhhhhhhh
Any way to recover my files, at least? If anyone here has any clues on getting my phone to working condition, I'd appreciate it a ton, hell, I might even pay you for helping me, better than losing all my data!
Will add as much info as possible and update my current status if asked.
Stop before you break it.
Find the official stock signed firmware ruu in .zip format that matches your current firmware. Ie 3.41.651.x (x can be any number but the other 3 octets MUST MATCH). Rename it to 0PJAIMG.ZIP and copy to the external sdcard.
DO NOT relock/lock the bootloader and DO NOT s-on.
Boot to download mode (Black screen red writing) and at the bottom, in yellow text, you should see "press vol up to flash"..
shivadow said:
Stop before you break it.
DO NOT relock/lock the bootloader and DO NOT s-on.
Boot to download mode (Black screen red writing) and at the bottom, in yellow text, you should see "press vol up to flash"..
Click to expand...
Click to collapse
That's unfortunately the issue, I AM S-On, never turned it off, which has pretty much sealed this poor phones fate I assume. If not, I'm betting I would have already flashed a no wipe .zip successfully. It's a shame, since this could have been prevented if I knew this phone was prevalent to system corruption, now the only thing I can depend on is obtaining a compatible recovery, since mine isn't working, download/fastboot is the only thing I have now.
It also seems I cannot find the "RUU_HIMA_WHL_M60_SENSE70_SPCS_MR_Sprint_WWE_3.41.651.4.zip" over the web, would an .exe work if I rename the extension as .zip?
S-on or s-off doesn't matter. What i meant is if you go s-off there is no need to ever s-on again. Same for bootloader. If it's unlocked then you don't ever need to lock/relock it.
Exe or zip but sometimes exe fails. Exe must be run on a pc and have the phone connected via USB. Zip must be run from external sdcard. It MUST be that version regardless.
Your only way without buggering it further is to flash the stock firmware. It will replace the recovery etc itself and will be safer than messing around with it, if it flashes OK.
shivadow said:
S-on or s-off doesn't matter. What i meant is if you go s-off there is no need to ever s-on again. Same for bootloader. If it's unlocked then you don't ever need to lock/relock it.
.
Click to expand...
Click to collapse
Then I'm assuming the correct fw "0PJAIMG.zip" would flash successfully even with an unlocked bootloader?
RebeccaSugar said:
Then I'm assuming the correct fw "0PJAIMG.zip" would flash successfully even with an unlocked bootloader?
Click to expand...
Click to collapse
Correct.
If you prefer the *.zip over the *.exe then take a look at the "further reading" section of the ReadMe thread. There's a link to a decryption tool. Download the correct version for your computer. If you use windows, you can drag and drop the *.exe onto the decryption tool and it will extract the *.zip for you. On Linux and Mac you'll probably need to use some commands.
Sent from my HTC One M9 using XDA Labs
Flippy498 said:
Correct.
If you prefer the *.zip over the *.exe then take a look at the "further reading" section of the ReadMe thread. There's a link to a decryption tool. Download the correct version for your computer. If you use windows, you can drag and drop the *.exe onto the decryption tool and it will extract the *.zip for you. On Linux and Mac you'll probably need to use some commands.
Sent from my HTC One M9 using XDA Labs
Click to expand...
Click to collapse
Done, though, after doing the "0PJAIMG.zip" method once more, it interrupts the flash with a very fast error(?) message highlighted in white then quickly reverts to bootlooping the recovery splash screen (Black Background with Silver HTC Logo)
I decided to flash the boot.img and system.img
target reported max download size of 800000000 bytes
sending 'recovery' (20084 KB)...
OKAY [ 2.097s]
writing 'recovery'...
(bootloader) HOSD CL#695981
(bootloader) [email protected]
(bootloader) [email protected]%
(bootloader) Update partition OK
(bootloader) [email protected]
OKAY [ 1.838s]
finished. total time: 3.939s
(bootloader) kernel: lk
(bootloader) product: htc_himawhl
(bootloader) version: 1.0
(bootloader) imei: 990005027515833
(bootloader) version-main: 3.41.651.4
(bootloader) boot-mode: download
(bootloader) version-baseband: [email protected]
(bootloader) version-bootloader: 1.0.0.0000
(bootloader) mid: 0PJA20000
(bootloader) cid: SPCS_001
C:\Users\Infinity>Documents\Pack\fastboot.exe flash system C:\Users\Infinity\Documents\James\HTC\OUT_0PJA_3.41.651.21\system\system.img
target reported max download size of 800000000 bytes
Invalid sparse file format at header magi
erasing 'system'...
OKAY [ 0.232s]
sending sparse 'system' 1/6 (743090 KB)...
OKAY [ 40.331s]
writing 'system' 1/6...
(bootloader) HOSD CL#695981
(bootloader) [email protected]
(bootloader) [email protected]%
(bootloader) Update partition OK
(bootloader) [email protected]
OKAY [ 28.653s]
sending sparse 'system' 2/6 (725823 KB)...
OKAY [ 39.600s]
writing 'system' 2/6...
(bootloader) HOSD CL#695981
(bootloader) [email protected]
(bootloader) [email protected]%
(bootloader) Update partition OK
(bootloader) [email protected]
OKAY [ 27.937s]
sending sparse 'system' 3/6 (776453 KB)...
OKAY [ 42.390s]
writing 'system' 3/6...
(bootloader) HOSD CL#695981
(bootloader) [email protected]
(bootloader) [email protected]%
(bootloader) Update partition OK
(bootloader) [email protected]
OKAY [ 30.090s]
sending sparse 'system' 4/6 (764994 KB)...
OKAY [ 41.446s]
writing 'system' 4/6...
(bootloader) HOSD CL#695981
(bootloader) [email protected]
(bootloader) [email protected]%
(bootloader) Update partition OK
(bootloader) [email protected]
OKAY [ 30.371s]
sending sparse 'system' 5/6 (775925 KB)...
OKAY [ 42.348s]
writing 'system' 5/6...
(bootloader) HOSD CL#695981
(bootloader) [email protected]
(bootloader) [email protected]%
(bootloader) Update partition OK
(bootloader) [email protected]
OKAY [ 29.562s]
sending sparse 'system' 6/6 (546809 KB)...
OKAY [ 31.210s]
writing 'system' 6/6...
(bootloader) HOSD CL#695981
(bootloader) [email protected]
(bootloader) [email protected]%
(bootloader) Update partition OK
(bootloader) [email protected]
OKAY [ 21.738s]
finished. total time: 405.943s
They were successful, apparently, but I've seen no changes. When booting, it just hangs on the white splash screen with the green htc logo and the "This build is for development, etc" warning.
If only I had a way to boot a working recovery, the more I do this, the more it seems like it is without a shadow of a doubt, a hardware problem.
Here are some logs, the fw seems to match up with my phone just fine, nonetheles...
View attachment RUU_Decrypt_LOG-0PJA20000_3.41.651.21_2018-04-01_025319.txt
View attachment android-info.txt
View attachment android-info2.txt
View attachment backup_android-info.txt
I noticed that you used fastboot. Be aware that flashing RUUs isn't possible with the generic fastboot files. You'll need htc_fastboot. A download link can be found in the RUU section of the ReadMe thread.
Are you sure that the SD card isn't broken? (Never use old cards for flashing RUUs. They can corrupt the files.) Did you try another one? Normally the extracted *.zip should flash just fine via an SD card.
I'd try a different SD card and flashing the RUU via htc_fastboot. (Flashing only the system and the boot.img might not be sufficient.) If both methods fail then the phone's hardware is most probably damaged and there's nothing you could do.
Sent from my HTC One M9 using XDA Labs
Flippy498 said:
I noticed that you used fastboot. Be aware that flashing RUUs isn't possible with the generic fastboot files. You'll need htc_fastboot. A download link can be found in the RUU section of the ReadMe thread.
Are you sure that the SD card isn't broken? (Never use old cards for flashing RUUs. They can corrupt the files.) Did you try another one? Normally the extracted *.zip should flash just fine via an SD card.
I'd try a different SD card and flashing the RUU via htc_fastboot. (Flashing only the system and the boot.img might not be sufficient.) If both methods fail then the phone's hardware is most probably damaged and there's nothing you could do.
Sent from my HTC One M9 using XDA Labs
Click to expand...
Click to collapse
I used a different SD card, formatted it to fat32 then exFAT, and nothing happened, it just gave me another error and rebooted. Though, after the reboot I manually booted the download mode and the same happened. Except this time, it gave me a list of all the .img files at 0% inside the "0PJAIMG.zip" before abruptly shutting off.
I took your advice on using the manual htc_fastboot to flash the "0PJAIMG.zip", even with the powershell, and it still fails.
htc_fastboot v3.0.9.2 (2015-05-29)
target rom version: 3.41.651.21
found large-zip header, file count: 8
processing file 1/8...
sending 'zip' (88845 KB)...
OKAY [ 5.992s]
writing 'zip'...
(bootloader) HOSD CL#695981
FAILED (remote: 9 RU_SECURITY_FAIL zip from usb command in download mode)
finished. total time: 7.195s
htc_fastboot finished. total time: 8.782s
I did a bit of spelunking and came across this users post, that had the same issue as I.
repl1ca said:
Ok...so hopefully I didn't foobar something. I went to go back to stock since I'm returning my phone soon (1 year lease), so I relocked my bootloader before trying to flash the RUU (I'm S-ON by the way). Relock went fine, but the phone immediately returned to the bootloader with a "*** Security Warning***" message and now the phone won't boot into the ROM or recovery. I tried booting into download mode and flashing the RUU zip, but I am getting the following message:
Code:
C:\Program Files (x86)\Android\android-sdk\platform-tools>fastboot flash zip d:\downloads\0PJAIMG.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 2330284468 is not a multiple of the block size 4096
sending sparse 'zip' (0 KB)...
error: write_sparse_skip_chunk: don't care size 2330284468 is not a multiple of the block size 4096
error: write_sparse_skip_chunk: don't care size 2330284468 is not a multiple of the block size 4096
OKAY [ 1.015s]
writing 'zip'...
(bootloader) HOSD CL#695981
FAILED (remote: 9 RU_SECURITY_FAIL zip from usb command in download mode)
finished. total time: 2.017s
I also tried running the RUU exe in download mode, but that didn't work either.
Hopefully I am doing something wrong and didn't mess the phone up! I will be forever in debt to whoever can help me.
P.S. - I also tried unlocking the bootloader again but that is failing as well!! (Even though it says successful...)
_____________________________________________________________________________
EDIT: Ok, so I gave my Windows account full access to the platform-tools folder (which includes fastboot and the unlock token) and tried unlocking again, and it worked?! ROM is booting now, but how do I avoid having this happen again and return to stock? TIA
Click to expand...
Click to collapse
What did he mean by "Full Access to the platform-tools folder"? That may be my meal ticket to getting my phone working or nothing else.
You have to go into Windows Explorer on your computer and find the platform-tools folder. Once you find it, right click on it and go to Properties, then the Security tab. On that tab, add your Windows username in there and make sure the Full Access box is checked. Hit Apply, then OK.
My post is really old, so I'm having a hard time remembering what the actual issue was [emoji23]
Sent from my SM-G965U using Tapatalk
Security fail means the ruu is corrupt. Remote:9 I think is unsigned ruu. You need to be flashing a signed ruu.zip.
shivadow said:
Security fail means the ruu is corrupt. Remote:9 I think is unsigned ruu. You need to be flashing a signed ruu.zip.
Click to expand...
Click to collapse
That's what bothers me the most, the ruu I have IS signed, you sure I don't need S-OFF, or to lock the bootloader?
Security or bootloader make no odds. If you had s-off life would probably be easier..
Exactly which file are you flashing? Have you checked the md5 hash?
shivadow said:
Security or bootloader make no odds. If you had s-off life would probably be easier..
Exactly which file are you flashing? Have you checked the md5 hash?
Click to expand...
Click to collapse
I'll probably buy the XTC 2 Clip chip thing needed to manually turn S-OFF, I don't care about paying a little extra, as long as I can recover all my files in the phone.
I am flashing a "3.41.651.21" .zip from extracted from "RUU_HIMA_WHL_M60_SENSE70_SPCS_MR_Sprint_WWE_3.41.651.21.exe"
The MD5 hash for it is "f41f1b941eb3f9f9ecaebcbf235e87af"
Which looking up the hash reveals to be the version for my exact same hardware, kernel and software version
https://androidfilehost.com/?fid=312978532265363975
I'm more than confident S-OFF is the only way to fix it. Unless there are cases of android bricking, even with a working fastboot. Something, a type of security, is preventing files from being read/flashed, unless It's an eMMc error. Two verdicts now.
You most probably won't be able to recover any files at this point. Flashing a RUU will delete everything that's stored on your phone. Even S-OFF won't change that. S-OFF will only enable downgrading with older RUUs. Converting the phone isn't recommended unless you're willing to risk getting a paperweight since it's a CDMA device.
I haven't seen error 9 before I read about it in this thread. Since you already tried different methods and the md5 checksum of your manually extracted RUU seems to match the one of the AFH RUU, chances are high that the phone's hardware is broken.
Sorry for the bad news.
Sent from my HTC One M9 using XDA Labs
Flippy498 said:
You most probably won't be able to recover any files at this point. Flashing a RUU will delete everything that's stored on your phone. Even S-OFF won't change that. S-OFF will only enable downgrading with older RUUs. Converting the phone isn't recommended unless you're willing to risk getting a paperweight since it's a CDMA device.
Click to expand...
Click to collapse
At this point, it's already a paperweight, what's an extra $100 invested on the XTC 2 Clip going to do? Haha! If I can't recover the files, I'll just make an attempt at salvaging this phone and giving it away to someone else.
Flippy498 said:
I haven't seen error 9 before I read about it in this thread. Since you already tried different methods and the md5 checksum of your manually extracted RUU seems to match the one of the AFH RUU, chances are high that the phone's hardware is broken..
Click to expand...
Click to collapse
That IS a fear, especially about hearing about the "horrors" of the Hynix eMMc from people in the the thread I linked in the OP, and others in gsmhosting, this device might have just been another victim of faulty circuitry, which actually has me steamed.
http://forum.gsmhosting.com/vbb/f961/htc-one-m9-bootloop-2214236/#3
This is going to be my brave (read: foolish) attempt.
The biggest problem of the M9 is the Snapdragon 810 processor. Although later firmware revisions fixed the overheating (more or less) the heat damages that emerged from to the usage of older firmware versions aren't fixable.
Most phones that got sold with this processor suffer from similar issues, sooner or later. If you check the xda forums from other 2015 flagship devices with the SD810 you'll see that they all have some kind of sudden bootloop death problem.
And as said before, getting S-OFF won't change your situation. If you really want to try a method that has a slightly chance of being successful you should search for a jtag device like e.g. a riff-box. The thing is I personally don't have any experiences with jtagging. I only know that it can still help in situations in which there already seems to be no hope, anymore. Check sneakyghost's firmware thread in the development section. If I remember correctly, post #5 contains info or at least a link with further info about the topic. Be aware that these devices can be quite expensive.
Sent from my HTC One M9 using XDA Labs
Flippy498 said:
The biggest problem of the M9 is the Snapdragon 810 processor. Although later firmware revisions fixed the overheating (more or less) the heat damages that emerged from to the usage of older firmware versions aren't fixable.
Most phones that got sold with this processor suffer from similar issues, sooner or later. If you check the xda forums from other 2015 flagship devices with the SD810 you'll see that they all have some kind of sudden bootloop death problem.
Click to expand...
Click to collapse
I've heard things like that before! It shorts out the board or something above those lines, if heating is an issue, then it certainly did that to mine, which may be the fault of the missing recovery and bootloop, along with one crash I remember! Yes, I remembered I had one crash, the screen had all sorts of garbled colorful static on it and the phone made a beeping noise, why didn't I remember that!? I'm an idiot. That should have been a clear warning to back up everything, I should have reminded myself of the issues with the 810 Processor. Whether the crash months earlier had anything to do with what might have either been a sign of decay, or just a coincidence is beyond me, but knowing my current position with this phone, I'll go with the former.
Flippy498 said:
And as said before, getting S-OFF won't change your situation. If you really want to try a method that has a slightly chance of being successful you should search for a jtag device like e.g. a riff-box. The thing is I personally don't have any experiences with jtagging. I only know that it can still help in situations in which there already seems to be no hope, anymore. Check sneakyghost's firmware thread in the development section. If I remember correctly, post #5 contains info or at least a link with further info about the topic. Be aware that these devices can be quite expensive.
Click to expand...
Click to collapse
Lucky for you (and me) I do! I've successfully soldered about 5 things in the past, so this phone should be familiar territory! I just cancelled the XTC 2 Clip order, and instead ordered myself a Riff Box, I saw that it supports my HTC 9, and I thank you for telling me this! I work much better under hardware than software (Thanks ADHD), I'll check out. I immensely appreciate your help, and you taking time out of your day to give me sources, it truly, honestly means a lot. The device is around $120, not horribly expensive, my wallet can take it, I'll update you on my progress later in the thread! Thanks again!
Woah, apparently I don't NEED to solder? Well, this just makes it easier I'd say! BUT, I don't trust myself enough to risk destroying the sensitive data inside my device, so I will e-mail Tecardo and offer him a price for helping me instead. Can't trust myself enough not to screw up!
Oh, only 120 bucks? Don't ask me why but I had a higher price in mind. Either my mind betrayed me or the riff box got cheaper...
Sent from my HTC One M9 using XDA Labs
Flippy498 said:
Oh, only 120 bucks? Don't ask me why but I had a higher price in mind. Either my mind betrayed me or the riff box got cheaper...
Click to expand...
Click to collapse
Well, in your defense, there ARE bundles that are priced ridiculously high (In the $500's for some damned reason) even though you can get the same bundles separately, for less than half of what they ask.