Related
(At first: I'm a noob when it comes to this and I know this has been a big mistake)(Also, my first language isn't English, so please be nice ) So today, I tried to root my HTC One M9 with this video: (I did EXACTLY those steps one by one)
sakitech - How to Root your HTC One M9 (Full Guide)
(Can't post links yet)
I did get a bootloop (Yay), so I started to get frustrated. After that, I searched for fixes and deleted some things (Which has been the biggest mistake I've ever done in my life). Now I seriously dont know what to do. I can't enter the Recovery mode, I can't do sh*t. Even my computer cannot detect my smartphone anymore..... Whenever I type smth like "adb reboot recovery" it says it FAILED..... If I try to get into Recovery mode, it tells me: "failed to boot to recovery mode".
So one of the only Screens I can get is the Bootloader and download reboot screen. (Not exactly sure if there's more)
"Software status: Modified" " RELOCKED" "S-ON"
-All this Boot-Stuff-
I can't even get to the Homescreen, in fact, I can't install SunShine to get S-OFF. I don't even want it rooted anymore, I just want it to work again
Please, help me somehow ._.
(Sorry for grammar fails)
//Edit: I installed the M9Toolkit by SQUABBI and I discovered, that none of those Commands have any effect on my phone. Doesn't matter what I'm pressing, either it's "No Device Found" or nothing happens.
Which model you've? CID, MID? You need to RUU your device through SD-Card method. Since you're S-On, you can only use signed firmwares.
What do you mean by which model do I have? As I said, I'm a noob if it comes to this (Bought it from amazon, so I dont have any trouble with Verizon and stuff)
CID: HTC__102
MID: 0PJA10000
Loligerloler said:
What do you mean by which model do I have? As I said, I'm a noob if it comes to this (Bought it from amazon, so I dont have any trouble with Verizon and stuff)
CID: HTC__102
MID: 0PJA10000
Click to expand...
Click to collapse
Do you have skype or hangouts? i could help you out over live chat.
Just chiming in with the old "why root it if you have no clue what you're doing".
You need to unlock the oem bootloader lock as you have relocked it so now it wont allow you to do much.. Thats the hard bit. Not sure how you do that as I've never borked it so bad.
Once unlocked, if you can re-unlock it, you can flash twrp 2.9.0.1 and supersu 2.65.
I advise doing any oem ota's prior to rooting and taking a twrp full system backup (4gb). If you include data in the backup you need 12gb free on internal memory.
Sent from my HTC One M9 using Tapatalk
So true ._. Was a huge mistake ...
I didnt really care about rooting it anymore, so I tried EVERYTHING to work again somehow.
Thank god Black_Eyes posted the right thing.
I just pasted the right RUU file on my SD-Card and installed it on the phone. Had to reboot a few times but in the end it worked.
Loligerloler said:
So true ._. Was a huge mistake ...
I didnt really care about rooting it anymore, so I tried EVERYTHING to work again somehow.
Thank god Black_Eyes posted the right thing.
I just pasted the right RUU file on my SD-Card and installed it on the phone. Had to reboot a few times but in the end it worked.
Click to expand...
Click to collapse
I too have the same issue. Sakitech . So what should I do? I've unlocked bootloader and S-ON. What did you do? From where did you download the stock ROM for your device? How did you install it? With TWRP or Download mode or they stock recovery?
anirudh.das13 said:
I too have the same issue. Sakitech . So what should I do? I've unlocked bootloader and S-ON. What did you do? From where did you download the stock ROM for your device? How did you install it? With TWRP or Download mode or they stock recovery?
Click to expand...
Click to collapse
I've relocked the bootloader (which isnt that hard).
Then I searched the internet for the correct RUU(It's a german page, I dont think you would understand anything ).
I copied the RUU onto(?) my SD-Card (You gotta rename it to: "0PJAIMG.zip" without " ), and sticked it into my phone and started the download mode. It asked me if I want to install it and so on. Had to reboot it a couple of times though.
After it installed properly I deleted the file from my SD-Card and I was fine.
Loligerloler said:
I've relocked the bootloader (which isnt that hard).
Then I searched the internet for the correct RUU(It's a german page, I dont think you would understand anything ).
I copied the RUU onto(?) my SD-Card (You gotta rename it to: "0PJAIMG.zip" without " ), and sticked it into my phone and started the download mode. It asked me if I want to install it and so on. Had to reboot it a couple of times though.
After it installed properly I deleted the file from my SD-Card and I was fine.
Click to expand...
Click to collapse
I've tried this thousand times. But I get an error after it starts to flash. It says- Error: -2: -14: Failed to flash from downloadzip. What is this? I tried this with both Unlocked and Re-locked bootloader. But same error. Is this due to incompatible RUU? If possible can you search the RUU for my device and post the link here?
Kernel: lk
Product: htc_himauhl
Version: 1.0
Version-main: 1.32.401.17
Boot-mode: download
Version-bootloader: 1.0.0.0000
mid: 0PJA10000
Cid: HTC_J15
Above given are my device's info.
anirudh.das13 said:
I've tried this thousand times. But I get an error after it starts to flash. It says- Error: -2: -14: Failed to flash from downloadzip. What is this? I tried this with both Unlocked and Re-locked bootloader. But same error. Is this due to incompatible RUU? If possible can you search the RUU for my device and post the link here?
Kernel: lk
Product: htc_himauhl
Version: 1.0
Version-main: 1.32.401.17
Boot-mode: download
Version-bootloader: 1.0.0.0000
mid: 0PJA10000
Cid: HTC_J15
Above given are my device's info.
Click to expand...
Click to collapse
Sadly, I'm not the best when it comes to this But make sure you rename the zip file and dont put it in any folder. Just copy it directly on the card. Relocked is important too (I guess). Most of the files I am finding are German ones, so I can't promise if this works all the time.
Maybe install the firmware at first (Works just like the RUU, rename and copy) :
https://www.androidfilehost.com/?fid=24341993505161594
I would stick to this RUU:
https://www.androidfilehost.com/?fid=23991606952595217
i see that your cid is HTC_J15. As far as i know, the RUU must match both your cid and mid (correct me if im wrong). Are you from egypt?
anirudh.das13 said:
I've tried this thousand times. But I get an error after it starts to flash. It says- Error: -2: -14: Failed to flash from downloadzip. What is this? I tried this with both Unlocked and Re-locked bootloader. But same error. Is this due to incompatible RUU? If possible can you search the RUU for my device and post the link here?
Kernel: lk
Product: htc_himauhl
Version: 1.0
Version-main: 1.32.401.17
Boot-mode: download
Version-bootloader: 1.0.0.0000
mid: 0PJA10000
Cid: HTC_J15
Above given are my device's info.
Click to expand...
Click to collapse
What size is the sdcard? For some reason, it has to be 32GB or less and FAT32.
iElvis said:
What size is the sdcard? For some reason, it has to be 32GB or less and FAT32.
Click to expand...
Click to collapse
It is 4GB with Fat 32
---------- Post added at 04:49 PM ---------- Previous post was at 04:44 PM ----------
Roobwz said:
i see that your cid is HTC_J15. As far as i know, the RUU must match both your cid and mid (correct me if im wrong). Are you from egypt?
Click to expand...
Click to collapse
I searched a long and finally found stock ROM in HTC DEV/downloads. My device was manufactured in Saudi Arabia. But in that site it shows that my version(1.32.401.17) matches with WWE S Africa. How's that possible?
Loligerloler said:
Sadly, I'm not the best when it comes to this But make sure you rename the zip file and dont put it in any folder. Just copy it directly on the card. Relocked is important too (I guess). Most of the files I am finding are German ones, so I can't promise if this works all the time.
Maybe install the firmware at first (Works just like the RUU, rename and copy) :
https://www.androidfilehost.com/?fid=24341993505161594
I would stick to this RUU:
https://www.androidfilehost.com/?fid=23991606952595217
Click to expand...
Click to collapse
I downloaded the Firmware. Then booted into RUU reboot(black screen with white HTC logo). Then I flashed the Firmware with fastboot flash zip firmware. zip. After this I get a failed error (14: failed to flash with downloadzip). What is this? The same error comes when I install via download mode by remaining the file to 0PJAIMG.zip. What to do now?
Have you checked the download for matching md5 and filesize? Could be a corrupt file.
Sent from my HTC One M9 using Tapatalk
would you mind helping me too?
Black_Eyes said:
Which model you've? CID, MID? You need to RUU your device through SD-Card method. Since you're S-On, you can only use signed firmwares.
Click to expand...
Click to collapse
I see you know what's going on with the m9. I had a slow WiFi problem, so I messed with things. Tried to clear the system cache and did something to the bootloader, now I'm stuck in airplane mode. Of course I dropped my Sim card in the dark messing with it. My phone company (ntelos) has no idea what I'm talking about and put me in a loaner phone. They have now been bought by sprint and no longer offer the m9. So... I'm trying to fix it and move it to another carrier. Maybe... or just fix it for fun..lol
How would I reset the bootloader to the way it was before I deleted random stuff?
Thanks
Hey guys. Need some help remembering how to do this stuff and what info i need to get some real help sorting out my misses phone.
Ive not done this for a very long time...since i re did my old HTC HD2.
So...the misses has had her HTC One M8 for over a year now. Bought off Ebay and all is good. An update needed to be done about 6 months ago but the wife said it failed all the time. I had a look and found it had a TWRP boot loader on and a custom ROM installed (i guess). The phone will not even connect to sync manager (my original M8 will) but is seen by Windows and can view the internal storage and SD storage.
So, want to revert it back to a stock M8 image but am confused about what i need to get to make this happen.
I know my M8 is on version 6.12.401.4 and have downloaded a recovery image with that number. Also, the TWRP version on the misses phone is v2.8.6.1.
Please can someone with a lot more brain power help me to revert her phone back to stock and save me from a moaning wife (and not moaning in the good way )
Thx in advance for any help
What's the OS- no. written on bootloader ?
If that is blank, post the fastboot getvar all result without serial & imei no.
If there is OS- with no. and it's a GSM device, check the thread linked in my signature for how-to and the files needed.
Hi ckpv5 and thx for the reply
Well i have no idea whats going on with this phone or what the misses has been playing around with.
So after i come home from work to day..she shoved the phone in my hand and said "its broke...go fix it". So had a look........and now it stops on the HTC screen and will go no further. When i connect it to the PC...i can see the internal storage and the SD card. There seems to be not much on the internal storage....so not sure if she has deleted the actual OS on the phone and thats why it will not boot through. There is 10.5GB free of 10.6GB
Im sorry for being really dumb but i cant seem to get the info from the fastboot getvar all results. Not sure if its me or the phone but tried what was posted and got nothing :/
So...not sure if this helps but this is whats on the bootloader screen:
*** software status: Modified ***
*** UNLOCKED ***
M8_UL PVT SHIP S-ON
HBOOT-3.19.0.0000
RADIO-1.25.214500021.0GG
OpenDSP-v48.2.2-00567-M8974_FO.1211
OS-
eMMC-boot 2048MB
Jan 15 2015,22:51:08.290
TWRS is on version 3.0.2.0
I dont know if that helps you to point me in the right direction or help me out but please let me know as now have a moody wife :/
Thx again in advance
stuka69 said:
When i connect it to the PC...i can see the internal storage and the SD card. There seems to be not much on the internal storage....so not sure if she has deleted the actual OS on the phone and thats why it will not boot through. There is 10.5GB free of 10.6GB
Click to expand...
Click to collapse
10.6 GB internal storage is just the user accessible part. This means its the 16 GB version, and the balance (5.4 GB) is reserved for the OS (and that partition is not viewable in Windows).
It doesn't prove whether the OS has been deleted or not (it still may be - but doesn't prove so).
stuka69 said:
Im sorry for being really dumb but i cant seem to get the info from the fastboot getvar all results. Not sure if its me or the phone but tried what was posted and got nothing :/
Click to expand...
Click to collapse
Are you in bootloader, and have fastboot mode selected (FASTBOOT highlighted in red near the top of screen)?
Is so, try another cable, or another USB port on the PC. Does the command work on your phone?
stuka69 said:
HBOOT-3.19.0.0000
RADIO-1.25.214500021.0GG
Click to expand...
Click to collapse
The radio number corresponds to Lollipop (version number 5.xx). The stock nandroid you mention in the first post 6.12.401 is Marshmallow, and therefore won't work.
stuka69 said:
TWRS is on version 3.0.2.0
Click to expand...
Click to collapse
I'm confused, the top post say TWRP 2.8.6.1 is installed?
---------- Post added at 11:15 AM ---------- Previous post was at 10:38 AM ----------
stuka69 said:
I know my M8 is on version 6.12.401.4 and have downloaded a recovery image with that number.
Click to expand...
Click to collapse
Be careful, I think you have your terminology mixed up here.
A recovery image is not a ROM or OS. Recovery image refers to a custom recovery (like TWRP) or stock recovery (stock analogue of TWRP), which is only the tiny stock/official application which installs OS updates, etc.
A TWRP backup or stock ROM (OS) is typically around 1.5 GB (for Sense ROMs). Stock recovery image is around 10 MB.
In any case, as already mentioned, the version number 6.12.401 (even if you are referring to stock TWRP backup) won't work on your wife's phone (mismatch the current LP firmware).
Hi redpoint
Thx for your reply and trying to help me.
Yes you are correct...it is 16GB storage. Just goes to show how long i have been out of the loop with these sorts of things and probably why im having trouble sorting this out
Thx for clearing up that the radio version is for a Lollypop version and for setting me straight on on recovery and ROM terminology.
Now...can i post the phone to some one to sort out for me lol
OK....managed to get the fastboot getvar all result
INFOversion: 0.5
INFOversion-bootloader: 3.19.0.0000
INFOversion-baseband: 1.25.214500021.06G
INFOversion-cpld: None
INFOversion-microp: None
INFOversion-main:
INFOversion-misc: PVT SHIP S-ON
INFOserialno:
INFOimei:
INFOimei2: Not Support
INFOmeid: 00000000000000
INFOproduct: m8_ul
INFOplatform: hTCBmsm8974
INFOmodelid: 0P6B10000
INFOcidnum: HTC__001
INFObattery-status: good
INFObattery-voltage: 0mV
INFOpartition-layout: Generic
INFOsecurity: on
INFObuild-mode: SHIP
INFOboot-mode: FASTBOOT
INFOcommitno-bootloader: 3aa067db
INFOhbootpreupdate: 11
INFOgencheckpt: 0
Does that help you guys. If it does....please can you point me in the right direction on what files i need and how to go about setting the phone back to its stock image.
Once again....im really thankful for all the help you guys have given so far and any thats to come.
That's a EU device.
To get back to stock and directly to the latest Marshmallow, you can follow this
http://forum.xda-developers.com/showpost.php?p=64926626&postcount=6
thx ckpv5...ill give it a try when i get home from work
stuka69 said:
thx ckpv5...ill give it a try when i get home from work
Click to expand...
Click to collapse
ckpv5's advice is excellent, as always. But one thing I'd add, is that the RUU update method he linked will wipe all data on the phone. If there is anything on the phone your wife wants to retrieve/keep (that isn't backed up to removable SD or off the phone - such as PC or cloud), you might try to restore the stock TWRP backup (restore Lollipop) and corresponding stock recovery, retrieve the data, and from there either see if the update installs properly, otherwise update to MM using the RUU method linked by ckpv5 above.
To restore stock TWRP backup for Lollipop, use ckpv5's thread (also linked in his signature) and install the stock TWRP backup and stock recovery for 4.16.401.10 or 4.16.401.13 (can't tell which exactly, I just know its one of those from the radio number). Necessary files and instruction in the thread: http://forum.xda-developers.com/htc-one-m8/help/tutorial-how-to-stock-stock-twrp-t3086860
Now, we don't exactly know what caused the phone to stop booting in the first place, so I'd suggest to make it clear to your wife up front, that you may or may not be able to retrieve any data. But its certainly worth a try.
Of course, if there isn't any data your wife wants to keep, you can go ahead with ckpv5's original advice to update by RUU.
Yeah there is nothing on the phone that she wants to keep now
So, tried it out but when i go to flash it says it cannot open the zip file. Below is the cmd string:
Microsoft Windows [Version 10.0.10586]
(c) 2015 Microsoft Corporation. All rights reserved.
C:\Users\st00kz>cd desktop
C:\Users\st00kz\Desktop>cd ruu
C:\Users\st00kz\Desktop\RUU>fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ -0.000s]
finished. total time: -0.000s
C:\Users\st00kz\Desktop\RUU>fastboot oem rebootRUU
...
(bootloader) Start Verify: 3
OKAY [ 0.000s]
finished. total time: 0.000s
C:\Users\st00kz\Desktop\RUU>htc_fastboot flash zip RUU.zip
error: preprocess_file : Cannot open file RUU.zip
C:\Users\st00kz\Desktop\RUU>
After typing the "fastboot oem rebootRUU" the phone reboots and has HTC on a black screen and stays there. Is that correct?
I also tested the files in the zip and it looks like some are corrupted:
C:\Users\st00kz\Desktop\RUU\RUU.zip.zip: The archive is corrupt
C:\Users\st00kz\Desktop\RUU\RUU.zip.zip: Checksum error in dzdata_32g.img. The file is corrupt
I tried downloading it on all the mirrors from this link in your other post https://www.androidfilehost.com/?fid=24369303960687057
Am i doing it right??? if so...is there another place that i can find the zip file???
Thx for all your advice again guys
1. The zip is not corrupted but it is encypted so you can't open it.
2. Read the above when you tested the zip. It seems your windows extension is hidden, when you rename the file to RUU.zip, you actually rename it to RUU.zip.zip, that's why you have the error (read that warning in the guide). Rename the file to RUU and do the test again, can you see now it is read as RUU.zip ? If yes, retry the procedure but this time run the flashing part with :
fastboot oem rebootRUU
htc_fastboot flash zip RUU
3. Don't skip the upper part in the guide, to relock bootloader if current bootloader status is unlocked.
stuka69 said:
So, tried it out but when i go to flash it says it cannot open the zip file.
Click to expand...
Click to collapse
There is nothing in ckpv5's instructions that say to open the RUU zip. I don't know why folks are always trying to do this.
The command "fastboot flash zip xx.zip" expects exactly that, an unaltered zip file to flash. Download, rename, and flash it, that's all. The zip file doesn't need to be unzipped or anything like that.
Once you mess with the zip, (which isn't actually possible without the HTC encryption key - and trust me you can't do it) you make the zip unsigned, which also means you then can't flash it with s-on, by definition.
So moral of the story, leave the zip alone (aside from renaming it) and flash it.
stuka69 said:
C:\Users\st00kz\Desktop\RUU>htc_fastboot flash zip RUU.zip
error: preprocess_file : Cannot open file RUU.zip
Click to expand...
Click to collapse
I can see how this part may have led you to believe something was wrong with the zip, and to further examine it (possibly leading you to try to unzip it). But as ckpv5 mentioned, this error is almost always a result of folks not having the zip file in the right location: either simply not in the right folder (same folder as htc_fastboot.exe) or more commonly you unwittingly named it "RUU.zip.zip" due to Windows defaults.
Do yourself a favor, and turn off the Windows setting to hide file extensions (which is usually enabled by default): Control Panel>Folder Options>View tab, and deselect the option "Hide extensions of known file types".
ckpv5 said:
1. The zip is not corrupted but it is encypted so you can't open it.
2. Read the above when you tested the zip. It seems your windows extension is hidden, when you rename the file to RUU.zip, you actually rename it to RUU.zip.zip, that's why you have the error (read that warning in the guide). Rename the file to RUU and do the test again, can you see now it is read as RUU.zip ? If yes, retry the procedure but this time run the flashing part with :
fastboot oem rebootRUU
htc_fastboot flash zip RUU
3. Don't skip the upper part in the guide, to relock bootloader if current bootloader status is unlocked.
Click to expand...
Click to collapse
Ahh ok got you now. Sorry ...must have missed the part about the windows extension (misses bleating in my ear about getting this sorted and other nonsense ) Ill go back and have another look with out her around.
And yes I did the upper part of the guide. I relocked the bootloader.
Thx again for your help. I will owe you a lot of beers soon
In case the above not working for you, here is the easier one ...
1. Download the RUU_M8_UL_L50_SENSE60_MR_HTC_Europe_4.16.401.10_Radio_1.25.214500021.06G_20.68.4196t.01_F_release_417003_signed.exe from http://androidruu.com/?developer=M8
2. Connect the device to PC (in fastboot/bootloader mode)
3. Right click the exe and select run as administrator, follow all the instructions, accept/agree, next, update, next, blablabla until it complete. (You need PC with USB2.0 and HTC USB drivers installed - I believe you already have these)
4. After reboot, setting up everything, go to settings - about - software update - do the checking, download, install OTA update.
There are many methods to fix your phone. Just try these two options first. I'll be travelling back to home in the morning (I won't be able to reply to any question that you may have during that time) and I'll be home in the evening and will check your progress.
Its alive...its alive i tell you
Guys...you have mine and the wifes greatest appreciation of what you have helped with. Thx for all your time and patience with me. It was just that damned file extension
If you guys are ever in the south UK at any time...let me know and ill buy you some beers
Thanks once again guys
Joe
Great :good::good:
Nice work; and happy to help.
Hey, how old is "old" anyway, if I may ask? I'm 43.
LOL ok not as old as you then...but even thats not old
Im 38...just feel a lot older when trying to remember this stuff...and my 4 girls dont help either
stuka69 said:
LOL ok not as old as you then...but even thats not old
Im 38...just feel a lot older when trying to remember this stuff...and my 4 girls dont help either
Click to expand...
Click to collapse
4 girls, yikes!
I have 2 young daughters at home myself. And that is why I'm rarely on XDA at home, lol.
Hello everybody
I'm the owner of a HTC One M9 and I really love it! I'm kind of newbie on Android.
This is my case, I can't upgrade my firmware to 6.0.1 (or later) I'm still on Android 5.0.2 and I tried to install a cyanogenmod firm that kind of fit with my model... BUT! it start to have some many problems.. like the display starts to break the images and start to repetitive the image like an a glitch... when a phone call comes it turn off or restart it was like a dead phone... Then I install a MaximusHD 1.0.0 and it come back the same way it was but it returns to Android 5.0.2... I already unlock my phone and it's S-OFF via sunshine...
So, If you have some info that help me fix this (upgrade to Android 6.0.1 or later) or you have the same experience please leave your comment!
My data:
MODEL: htc_himawl
CID: LRA_001
MID: OPJA30000
Cheers!
Alvaro
Boot your phone into download mode, connect it to your computer and make sure ADB and FASTBOOT drivers are installed and working.
To ensure your device is connected, type "fastboot devices".
Your Bootloader needs to be unlocked, this is done with "fastboot oem unlock".
First step: Change your CID to SuperCID "fastboot writecid 11111111"
Second step: Change your MID to 0PJA1100 "fastboot writemid 0PJA1100"
Third step: Flash latest RUU for developer edition. To make sure you have the right RUU, usually it is x.x.617.x.
Kartoffelrudi said:
[...]First step: Change your CID to SuperCID "fastboot writecid 11111111"
Second step: Change your MID to 0PJA1100 "fastboot writemid 0PJA1100"
Third step: Flash latest RUU for developer edition. To make sure you have the right RUU, usually it is x.x.617.x.
Click to expand...
Click to collapse
Please don't give such advise if you don't know what you're talking about. The OP owns a CDMA device and the dev firmware is GSM. GSM and CDMA aren't compatible and you can't convert the one into the other due to their different partition layouts. In the worst case this can lead to unrecoverable damages.
Edit: This post isn't meant to be an offense. I just want to prevent the OP from doing something he/she could regret afterwards.
Edit 2 @cedricpixler: You'll need a windows PC if you want to use the following instructions. Win 10 and 8 (or 8.1) might not work whereas win 7 is always fine. I'm using win 10 myself without any problems but others have been reporting that they needed to use a win 7 PC.
Charge your phone to at least 50 %.
Go to HTC's US website and download the latest RUU for your SKU. Your current firmware is stated in Download Mode in the line that starts with "OS". The SKU are the numbers behind the second dot of the firmware version.
If not already done you should download and install the HTC Sync manager. Uninstall it directly, afterwards. This way you update the needed drivers to the latest version. If you keep the manager you might face some connectivity issues during the upcoming steps. Next you need to boot your phone to Download Mode and to connect it via USB (if possible use a 2.0 cable and port instead of 3.0) with your PC.
Disconnect your PC from the internet. Disable your antivirus program and your firewall and execute the RUU as an admin. In some cases the flashing process might take some time so don't worry if it hasn't finished after 10 minutes.
When the RUU has finished you can re-activate your av program and your firewall. Afterwards you can re-connect your PC with the internet. Your phone should be up to date now.
Not every step is actually essential but if you follow these instructions the most frequently occurring problems should be prevented.
Sidenote: Every problem you faced with custom roms is based on the difference between your current firmware and the base of the mentioned roms.
If you want to use a sense-based custom rom after you updated your firmware you need to re-flash the stock boot.img of your firmware after you flashed the rom. For non-sense-based roms like CM you need to flash thicklizards mono kernel. If you don't do this your phone won't recognize your sim card.
Sent from my HTC One S using XDA Labs
Thank you @Flippy498, I will take this steps you write and I will write here the results.
Somebody from LlaTooFer Maximus was helping me and send me this
"Well, your device is not capable with my custom rom due to different hardware. I recommend you to install Viper ROM prior that you need to update CID to VZW__001 and flash this full firmware https://www.androidfilehost.com/?fid=24651430732237625
After that you have to flash this RUU https://www.androidfilehost.com/?fid=24651430732238098
Once you do that you can install custom twrp recovery https://dl.twrp.me/hima/twrp-3.0.2-0-hima.img.html and custom rom http://forum.xda-developers.com/one-m9/development/rom-viperonem9-1-0-0-tweaks-hub-t3072773
Make sure you set Verizon during installation."
I tried the first step (installing the full firmware but this error comes up "C:\Program Files (x86)\platform-tools>fastboot flash zip 3.37.605.13_FULL_firmware.zip
target reported max download size of 800000000 bytes
sending 'zip' (41818 KB)...
OKAY [ 3.430s]
writing 'zip'...
(bootloader) HOSD CL#523158
(bootloader) ERR CID not matched
(bootloader) ERR [SD_UPDATE_ERR] CID NOT ALLOWED
(bootloader) ERR [SD_UPDATE_ERR] sddownload failed: 7
(bootloader) ERR Update zip file failed.
(bootloader) Update zip file OK
(bootloader) ERR ZIP ERROR CODE, 7
(bootloader) [email protected]
FAILED (remote: 7: fail to flash via downloadzip)
finished. total time: 4.567s"
But they or he doesn't tell me whats going on.... or what to do next.. @Flippy498 do you know if this instructions could help to change my CID or MID..? and If my phone is CDMA can I re Write the CID or MID
cedricpixler said:
[...]"Well, your device is not capable with my custom rom due to different hardware. I recommend you to install Viper ROM prior that you need to update CID to VZW__001 and flash this full firmware https://www.androidfilehost.com/?fid=24651430732237625
After that you have to flash this RUU https://www.androidfilehost.com/?fid=24651430732238098
Once you do that you can install custom twrp recovery https://dl.twrp.me/hima/twrp-3.0.2-0-hima.img.html and custom rom http://forum.xda-developers.com/one-m9/development/rom-viperonem9-1-0-0-tweaks-hub-t3072773
Make sure you set Verizon during installation."[...]
Click to expand...
Click to collapse
Interesting, being a 24/7 Viper user since the One S was my main device I didn't know that Llabtoofer doesn't support CDMA devices at all.
My bad. I missed the fact that you don't have the Verizon CID. (I only looked at your MID and wasn't even aware that this MID belongs to more than one CID.) If you want to change your CID then you need to do so manually via fastboot use "fastboot oem writecid VZW__001" while your phone is booted to Download Mode and connected to your PC via USB. Flashing that firmware pack before the RUU shouldn't be necessary (but it shouldn't hurt either). Besides I would download the latest 605 RUU (605 is the Verizon SKU) directly from HTC. Afterwards it's your choice whether you stay on stock or whether you want to install the latest Viper rom.
The MID of a CDMA device should never be changed. Even the sprint firmware (CDMA, too) isn't compatible with Verizon devices and vice versa. Changing the CID should be fine, though.
Sent from my HTC One S using XDA Labs
Update: Well I save my phone! the fact is that I just change the CID to VZW__001 and practically I followed the instructions I posted here and flash the last ViperOne firm and Kaboom! I have the latest firmware and it's so stable! If any one has the problem I had just ask me how I do.
Cheers!
@Flippy498 I see that Nugat comes for HTC M9, did you know if there is any official 7.0 stock from HTC? for CDMA phones like mine? Cheers!
Only the dev edition (GSM) got the update yet.
Last year Android M got released one day before Christmas for that sku and most of the rest of the world received it between mid January and the end of February 2016. Therefore I think that the unbranded skus might get the update around the end of this year (if we're lucky) or at the beginning of 2017. Branded skus like the CDMA ones always need a little more time than the unbranded ones due to all the bloat the carriers want HTC to add to the system.
I don't have a direct link at hand but there is an article on the xda portal which explains in general (not HTC-specific) why carrier-branded phones need to wait that much for their updates. If I remember correctly it got published sometime during the summer.
Sent from my HTC One M9 using XDA Labs
I am really new to all this, long ago I rooted my phone (don't know how cause I was really clueless and just watched tutorials), so now I wanted to just update my phone, but they say I have to unroot my phone to have updates on my HTC M8(Gold OPTUS). So I went into recovery mode and accidently wiped the whole data, I cross marked System, data, etc. So now I have no OS, after couple while, I've managed to use my SD card reader and put the SD card onto the computer and download the Viper Rom. Put the SD card back into the device and I installed everything and it went smoothly. When I was testing everything out the WiFi was not working, I tried turning it on, it just wouldn't swipe on or even locate any other WiFi. So I've read online that I need to update my firmware, and in order to update my do that I need to go back to my original version and update the OTA? I'm not sure what they mean about that. The version that came with the phone was v4.4.2 KitKat. Thank you I really appreciate the help!! By the way my phone use to be S-OFF but after all this now it is S-ON
When I try fastboot getar all, this is the info
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.18.0.0000
(bootloader) version-baseband: 1.19.21331147A1.09G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno:
(bootloader) imei:
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B11000
(bootloader) cidnum: TELST001
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: 23c984e1
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
eatme3 said:
So I've read online that I need to update my firmware, and in order to update my do that I need to go back to my original version and update the OTA?
Click to expand...
Click to collapse
Returning to the original stock (unrooted) ROM and stock recovery (matching your current, outdated KitKat firmware) should trigger OTA (over the air) updates, which will update the OS and firmware. You will probably have several updates, which will eventually bring everything up to the latest Marshmallow version.
See the following instructions and files. I believe you want to restore the stock TWRP backup 1.54.841.8 and corresponding recovery.
https://forum.xda-developers.com/htc-one-m8/help/tutorial-how-to-stock-stock-twrp-t3086860
Alternately, you can install firmware 6.12.841.4 using Post #5 of that same thread, then restore stock backup 6.12.841.4. (Post #4).
It also appears that in general, you need to slow down, and have a better understanding of the proper methods and processes before rushing headlong into doing something. Wiping things in TWRP is not the proper way to unroot (doesn't unroot anything). And its obvious to you now, wiping things without knowing what the results will be (system) was not a good idea.
Do yourself a favor, and take some time to read up, learn, and gain some real understanding. Do that before diving into any of the methods. If some things seem unclear, come back here and ask. YouTube is not a valid path to real understanding, and guessing how to do things, is a bad idea also.
redpoint73 said:
Returning to the original stock (unrooted) ROM and stock recovery (matching your current, outdated KitKat firmware) should trigger OTA (over the air) updates, which will update the OS and firmware. You will probably have several updates, which will eventually bring everything up to the latest Marshmallow version.
See the following instructions and files. I believe you want to restore the stock TWRP backup 1.54.841.8 and corresponding recovery.
https://forum.xda-developers.com/htc-one-m8/help/tutorial-how-to-stock-stock-twrp-t3086860
Alternately, you can install firmware 6.12.841.4 using Post #5 of that same thread, then restore stock backup 6.12.841.4. (Post #4).
It also appears that in general, you need to slow down, and have a better understanding of the proper methods and processes before rushing headlong into doing something. Wiping things in TWRP is not the proper way to unroot (doesn't unroot anything). And its obvious to you now, wiping things without knowing what the results will be (system) was not a good idea.
Do yourself a favor, and take some time to read up, learn, and gain some real understanding. Do that before diving into any of the methods. If some things seem unclear, come back here and ask. YouTube is not a valid path to real understanding, and guessing how to do things, is a bad idea also.
Click to expand...
Click to collapse
I have followed the instructions and read through everything, but the problem is that I don't have any backups nor I have created any backup files.
eatme3 said:
I have followed the instructions and read through everything, but the problem is that I don't have any backups nor I have created any backup files.
Click to expand...
Click to collapse
Did you click the link???
redpoint73 said:
Did you click the link???
Click to expand...
Click to collapse
I'm not sure what you mean by that, I clicked the link you directed me to it, found the backup version that was recommended, but in the instructions it says I need to have a folder name backups in the TWRP folder in the internal storage but I do not have one as I haven't created a backup
eatme3 said:
I'm not sure what you mean by that, I clicked the link you directed me to it, found the backup version that was recommended, but in the instructions it says I need to have a folder name backups in the TWRP folder in the internal storage but I do not have one as I haven't created a backup
Click to expand...
Click to collapse
Ok, now I understand the problem. Next time, try to be more specific about what the problem is, what step you are stuck on, etc. Sorry, I misunderstood, and thought you were saying you had no backup to restore (when the link has all the files you need).
The folder structure is created by TWRP when you make a backup. Try going into TWRP, select BACKUP. Then just check the "boot" option. Its not actually important to make a backup of anything; rather to just force TWRP to create the proper folder structure, in which to place the downloaded files. And boot.img is the smallest thing to backup; you won't actually use the backup for anything, think of it as just a "dummy" backup.
After you do that, you should have the folder structure similar to indicated in the guide. Its based on your phone's unique serial number, so its not that easy to make the folder with a file manager, etc. (which is why I'm telling you to do it the way I just indicated).
Simply put, if the problem is that you haven't made a backup . . . then just make a backup!
redpoint73 said:
Ok, now I understand the problem. Next time, try to be more specific about what the problem is, what step you are stuck on, etc. Sorry, I misunderstood, and thought you were saying you had no backup to restore (when the link has all the files you need).
The folder structure is created by TWRP when you make a backup. Try going into TWRP, select BACKUP. Then just check the "boot" option. Its not actually important to make a backup of anything; rather to just force TWRP to create the proper folder structure, in which to place the downloaded files. And boot.img is the smallest thing to backup; you won't actually use the backup for anything, think of it as just a "dummy" backup.
After you do that, you should have the folder structure similar to indicated in the guide. Its based on your phone's unique serial number, so its not that easy to make the folder with a file manager, etc. (which is why I'm telling you to do it the way I just indicated).
Simply put, if the problem is that you haven't made a backup . . . then just make a backup!
Click to expand...
Click to collapse
The first method didn't work, I am trying the second method but it seems when I get to the CMD where i type fastboot flash zip fw_xxxxxx.zip, it just says can't load and now I am stuck on this screen, can't go into recovery or even boot info the OS. Any suggestion?
eatme3 said:
The first method didn't work
Click to expand...
Click to collapse
Please provide more detail as to why it didn't work. Step that failed or you got stuck on, error messages, results, etc. Describe your actions in detail.
If it didn't work, its mostly likely pilot error, which is fixable.
If you didn't get method 1 to work, I don't think method 2 will go much better. You'll still have to restore a stock TWRP backup after you flash the MM firmware. The only difference is that you are restoring a MM backup, instead of a KK one (and saving you from doing multiple OTA updates).
eatme3 said:
I am trying the second method but it seems when I get to the CMD where i type fastboot flash zip fw_xxxxxx.zip, it just says can't load and now I am stuck on this screen, can't go into recovery or even boot info the OS.
Click to expand...
Click to collapse
"Cannot load' always means that you either didn't put the firmware zip in the right place, or renamed it incorrectly (if you renamed it).
Again, I would need you to describe the exact steps you did, in order to figure out what you did wrong (and exact commands used). The file needs to be in the same folder as fastboot.exe, and the file syntax needs to be exact (a single wrong character will cause the command to fail). Did you rename the file? If so, to what?
I assume you locked the bootloader (per the instructions) which by definition renders the phone unable to boot (so this is a normal and expected result based on what you've done). I recommend to keep trying to flash the firmware to flash (figure out what you did wrong). Then you'll need to unlock the bootloader again, install TWRP, and the Marshmallow stock backup.
Sorr
redpoint73 said:
Please provide more detail as to why it didn't work. Step that failed or you got stuck on, error messages, results, etc. Describe your actions in detail.
If it didn't work, its mostly likely pilot error, which is fixable.
If you didn't get method 1 to work, I don't think method 2 will go much better. You'll still have to restore a stock TWRP backup after you flash the MM firmware. The only difference is that you are restoring a MM backup, instead of a KK one (and saving you from doing multiple OTA updates).
"Cannot load' always means that you either didn't put the firmware zip in the right place, or renamed it incorrectly (if you renamed it).
Again, I would need you to describe the exact steps you did, in order to figure out what you did wrong (and exact commands used). The file needs to be in the same folder as fastboot.exe, and the file syntax needs to be exact (a single wrong character will cause the command to fail). Did you rename the file? If so, to what?
I assume you locked the bootloader (per the instructions) which by definition renders the phone unable to boot (so this is a normal and expected result based on what you've done). I recommend to keep trying to flash the firmware to flash (figure out what you did wrong). Then you'll need to unlock the bootloader again, install TWRP, and the Marshmallow stock backup.
Click to expand...
Click to collapse
Sorry the first method I skipped because I thought it wouldn't work without the backup folder, I am doing method 2 and this keeps staying here target
reported max download size of 1830612992 bytes
sending 'zip' (31474 KB)...
And I'm on the gray HTC when I boot into fastboot oem rebootRUU screen
I'm currently doing method one now instead of two, when I created a the backup folder on checking the Boot, I look into the HTC and there is no Backup in the TWRP folder, Ahh sorry it seems that I cannot see it on my computer when I am in recovery mode but when I go to my actual OS I can see it and extract it.
eatme3 said:
Sorry the first method I skipped because I thought it wouldn't work without the backup folder, I am doing method 2 and this keeps staying here target
reported max download size of 1830612992 bytes
sending 'zip' (31474 KB)...
And I'm on the gray HTC when I boot into fastboot oem rebootRUU screen
I'm currently doing method one now instead of two, when I created a the backup folder on checking the Boot, I look into the HTC and there is no Backup in the TWRP folder, Ahh sorry it seems that I cannot see it on my computer when I am in recovery mode but when I go to my actual OS I can see it and extract it.
Click to expand...
Click to collapse
OMG I LOVE YA!!! I LOVE YOU!! After freaking 4 hours of being clueless and stressed out, you sir have changed my life and made me the happiest man on earth! I really appreciate your help a lot! Everything is back to normal after doing method one! Once again thank you so much! Oh by the way, why does it keep updating and not install the update? It just boots my phone into recovery mode TWRP and when I turn my phone back on again, it asks me to install it again if i want, and it's installing the same update and update all over again, v4.4.3, not sure why?
Read the instructions thoroughly.
You need to install stock recovery to do update.
It won't work on TWRP.
ckpv5 said:
Read the instructions thoroughly.
You need to install stock recovery to do update.
It won't work on TWRP.
Click to expand...
Click to collapse
Do I have to download the matching stock recovery that is the same number as the download in post #2
Yes
2.23.841.1 backup + 2.23.841.1 stock recovery
Please edit the post and delete the serial number and imei
ckpv5 said:
Yes
2.23.841.1 backup + 2.23.841.1 stock recovery
Click to expand...
Click to collapse
Do as ckpv5 says. The man is wise.
Looks like I was off by one version (1.x versus 2.x). Since the OS number (main version in getvar) was wiped out (known issue with old version of TWRP which was originally used to root it) I was trying to go by the hboot and radio number. Hard to recall those old hboot and radio numbers from 2 years ago!
redpoint73 said:
Do as ckpv5 says. The man is wise.
Looks like I was off by one version (1.x versus 2.x). Since the OS number (main version in getvar) was wiped out (known issue with old version of TWRP which was originally used to root it) I was trying to go by the hboot and radio number. Hard to recall those old hboot and radio numbers from 2 years ago!
Click to expand...
Click to collapse
I always go for hboot version.
3.16 - 1.xx
3.18 - 2.xx
for 3.19 then we'll see the baseband no.
Ok Guy's
In the last few weeks there are more and more people struggling
with their devices so I decided to make a thread about a POSSIBLE fix.
It seems nobody knows what happens exactly.. but at some point the
download mode is no more accessible and you can only enter booloader mode with the white screen.
And once more this is only a Possible fix....no magical repair for your defective emmc or something like that.
This should only be a little help for some of you guys I´m not responsible for anything.
You do this on your own.
If it works, a hit on the thanks button would be nice, if not sad to say but I think you have to
go to the repair center.
We are starting at the point that you are familiar with fastboot and have a correct setup with drivers etc. on
your PC. (If not... search the forum and read how to set it up)
Files are signed so they should be also flashable with s-on.
Steps:
1. Download the Package for your Android-Version :
Lollipop:
https://www.dropbox.com/s/ts8tur5tkzv1o4l/0PJA_HIMA_L51_service_hosd_collection_900002.zip?dl=0
Marshmallow:
https://www.dropbox.com/s/pgw3hslknajl9kc/0PJA_HIMA_M60_service_hosd_collection_900001.zip?dl=0
Nougat:
https://www.dropbox.com/s/2azzxi9q65iilsj/0PJA_HIMA_N70_service_hosd_collection_9000033.zip?dl=0
2. Unzip it and take the CORRECT hosd.img for your version. (best is... you know wich version you have)
3. Connect M9 in bootlader mode and flash with fastboot:
fastboot flash hosd <filname>.img
4. MAYBE now you can enter download mode again.
5. If you don't know what version you have you can try one file after another..
fastboot outputs only okay when the right hosd.img is flashed.
(try to boot to download after every file)
6. If no one work it's pretty sure that your emmc is broken.
There is nothing more I know or I can do for you
so I can't give more support after this point.
Good Luck
broken link
You can reload the files
finitura said:
broken link
You can reload the files
Click to expand...
Click to collapse
This link will be around for a while... https://drive.google.com/folderview?id=0B4vTiHTBB629bFBtd3FUS01Ia1U
Beamed in by telepathy.
thank you
Thank you for this post which already the last hope for many people but please if you have to the files for Android Nougat please upload it many phone are broken after nougat update
thank you in advance
puede volver a subir el enlace
To everyone whos's searching for alternative/new download links:
You can find the hosd.img inside of the RUUs that are posted in the ReadMe thread. The decryption tool that is linked in its RUU section will help you to extract the needed file from the encrypted RUUs.
For being on the safe side you should only use files from RUUs that are matching your current firmware version. You can try to use the files from other RUUs with a similar version if there's none available for your current firmware/your SKU, though. However, never flash a CDMA file on a GSM phone or vice versa.
Hi guys,
maybe you can help me, otherwise I will open a new thread.
I got a M9 here from a friend that i wanted to fix.
Mode: Modified
S-ON
Bootloader: Locked
It began, that the Phone and SMS/MMS apps on the phone dissapeared until one day it didn't even boot up.
Can't flash anything because i can't access download mode or recovery mode, both say:
"Failed to boot to download/recovery mode" in red warning font...
I downloaded all signed htc one m9 firmwares from:
handy-faq.de/forum/htc-one-m9-firmware-ruus-otas-backups-stock-recoveries-t314182/#comment-2885828 and tried to flash every hosd.img file from the firmwares via fastboot. always got back "OKAY", rebootet but still didn't work...
Also tried to follow this tutorial:
handy-faq.de/forum/geloest-htc-m9-wiederbeleben-t320617/?page=1 and tried to flash the other files as well, but they always say "FAILED, cannot flash this partition in S-ON state" for example for aboot or other .img files...
Could you help me? Also read that some M9 have Storage Failures or problems.
I can't give you info of getvar all command in fastboot, because that doesn't work without download/recovery mode.
Thanks in advance!
Chris
There's probably nothing you (personally) can do. That looks like faulty hardware. The main problem of the M9 is the same that every smartphone with the snapdragon 810 is suffering from. Depending on the usage of the phone the soc is roasting the phone's internals. The latest firmware version fixes the overheating but it won't repair damages that got created while the phone was used with one of the older firmware versions.
If the warranty is still valid you can send the phone to HTC for letting them change the motherboard. The data on the phone is lost, though.
Sent from my HTC One M9 using XDA Labs
Hey,
woah that reply came fast, didn't expect that.
Much thanks for the info!
Yeah the app dissapearence and then the complete failure of the phone made me think of that too... but thanks for clarification!
That a subsequent update of the firmware does not make the board functional again makes sense, haha...
I will have a look if I/he can still get a change of the motherboard by warranty, if not i will gonna just put it into the trash bin.
Well, there's no reason not to answer if I'm around and have the time to write a post. (On the other hand it might happen that I don't have enough time for several days.)
It's a bit funny that Handy-FAQ is back online. That guest account that answered in the second thread you linked is mine. I left the site over a year ago and as far as I heard from my former fellow team members the site got shut down some months ago...
Sent from my HTC One M9 using XDA Labs
Can you please re upload the files i wan't to try them out?
joostnl said:
Can you please re upload the files i wan't to try them out?
Click to expand...
Click to collapse
c.f. what I wrote on page 1 of this thread:
Flippy498 said:
To everyone whos's searching for alternative/new download links:
You can find the hosd.img inside of the RUUs that are posted in the ReadMe thread. The decryption tool that is linked in its RUU section will help you to extract the needed file from the encrypted RUUs.
For being on the safe side you should only use files from RUUs that are matching your current firmware version. You can try to use the files from other RUUs with a similar version if there's none available for your current firmware/your SKU, though. However, never flash a CDMA file on a GSM phone or vice versa.
Click to expand...
Click to collapse
Flippy498 said:
There's probably nothing you (personally) can do. That looks like faulty hardware. The main problem of the M9 is the same that every smartphone with the snapdragon 810 is suffering from. Depending on the usage of the phone the soc is roasting the phone's internals. The latest firmware version fixes the overheating but it won't repair damages that got created while the phone was used with one of the older firmware versions.
If the warranty is still valid you can send the phone to HTC for letting them change the motherboard. The data on the phone is lost, though.
Sent from my HTC One M9 using XDA Labs
Click to expand...
Click to collapse
Hey there,
I will get a broken m9 (already paid for it) for less money which doesn´t start anymore after the update (to nougat?) but had no issues since 2 years like she told me.
I hope it´s only a bootloop, got not more information about that problem (owner has no clue about it).
I may need those files...
I think the newest firmware is installed so if i can´t access the bootloader, could you upload me this file?
I don´t want to restore stock, i want to unlock the bootloader and flash LineageOS and use it as daily driver.
My One M8 is a great phone but a cheap upgrade isn´t bad
D:\HTC M9\L51>fastboot getvar all
(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:HT55CYJ00237
all:
finished. total time: 0.125s
i am stuck on bootloader mod doesn't go on download mod nor to recovery mod.
can't boot to Android as well,
All the other values for CID, MID and other stuff is blank when I do indivdual fastboot getvar command.
can I bring my M9 to life with any stock image flashing with Fastboot command.
If yes please let me know which stock image I use and how to flash?
Thanks
Files reuploaded + nougat hosd if somebody need good luck