Related
Hey everyone,
new here and to rooting/flashing in general.
I've somewhat successfully converted my verizon M8 to work on Tmobile by using weaksauce 2.0 to root, then Sunshine to gain S-off. Flashed TRWP custom recovery with flashify, backed up my stock vzw setup (4.4.4), then flashed ViperoneM8 with tmobile extras to the phone. The phone works great 90% of the time on Tmo, with 4gLTE, mms, sms, wifi all working. But I will get random dropped general mobile service (no data, can't make calls, text won't go through). This is easily fixed with airplane mode toggle.
Sooo, I wanted to see how other roms work on my phone with Tmobile service, specifically ARHD 34.0 and/or change phone to developer edition and upgrade to Lollipop. But both roms require prerequisite upgrading of firmware. My phone won't let me change the firmware via ADB or RUU. I've tried changing to superCID and going back to relocked mode, but still won't work. I get error 155 when attempting to upgrade via RUU and cannot find firmware.zip when using adv/fastboot.
I came across an old thread about other rooted models that suggest upgrading the HBOOT. Can anyone verify this suggestion and guide me toward which specific HBOOT software to change to?
Thanks for the help,
-Ant
Tritan84 said:
Hey everyone,
new here and to rooting/flashing in general.
I've somewhat successfully converted my verizon M8 to work on Tmobile by using weaksauce 2.0 to root, then Sunshine to gain S-off. Flashed TRWP custom recovery with flashify, backed up my stock vzw setup (4.4.4), then flashed ViperoneM8 with tmobile extras to the phone. The phone works great 90% of the time on Tmo, with 4gLTE, mms, sms, wifi all working. But I will get random dropped general mobile service (no data, can't make calls, text won't go through). This is easily fixed with airplane mode toggle.
Sooo, I wanted to see how other roms work on my phone with Tmobile service, specifically ARHD 34.0 and/or change phone to developer edition and upgrade to Lollipop. But both roms require prerequisite upgrading of firmware. My phone won't let me change the firmware via ADB or RUU. I've tried changing to superCID and going back to relocked mode, but still won't work. I get error 155 when attempting to upgrade via RUU and cannot find firmware.zip when using adv/fastboot.
I came across an old thread about other rooted models that suggest upgrading the HBOOT. Can anyone verify this suggestion and guide me toward which specific HBOOT software to change to?
Thanks for the help,
-Ant
Click to expand...
Click to collapse
If your stock was 4.4.4, your firmware and hboot should be fine to run ARHD. I don't think that WWE firmware (x.xx.401.x) is compatible with T-Mo (x.xx.531.x). The firmware you have now (3.32.531.2?) will be fine.
xunholyx said:
If your stock was 4.4.4, your firmware and hboot should be fine to run ARHD. I don't think that WWE firmware (x.xx.401.x) is compatible with T-Mo (x.xx.531.x). The firmware you have now (3.32.531.2?) will be fine.
Click to expand...
Click to collapse
I'll go ahead and try to flash ARHD 34 and see how it goes on TMo. It does say that firmware upgrade should be done prior. Think I'll run in to the wifi/network issues?
Tritan84 said:
I'll go ahead and try to flash ARHD 34 and see how it goes on TMo. It does say that firmware upgrade should be done prior. Think I'll run in to the wifi/network issues?
Click to expand...
Click to collapse
You shouldn't have wifi issues. ViperOne is building a Lollipop version right now, and 4.4.4 firmware works fine with it.
The ARHD thread does recommend a full wipe with the non-matching firmware/ROM base though.
xunholyx said:
You shouldn't have wifi issues. ViperOne is building a Lollipop version right now, and 4.4.4 firmware works fine with it.
Click to expand...
Click to collapse
OK cool. I'll give it a shot. I really like the Viperone rom, but it's just annoying to have a random loss of network a couple times a day and having to toggle airplane mode. Any thoughts on why that would be happening?
Tritan84 said:
OK cool. I'll give it a shot. I really like the Viperone rom, but it's just annoying to have a random loss of network a couple times a day and having to toggle airplane mode. Any thoughts on why that would be happening?
Click to expand...
Click to collapse
Probably because of the conversion from Verizon to T-Mo.
xunholyx said:
Probably because of the conversion from Verizon to T-Mo.
Click to expand...
Click to collapse
EMERGENCY!! stuck in bootloader/fastboot loop! Won't allow me to go into recovery. Won't allow factory reset. The ROM said it installed succesfully. Banner says modified/Relocked. trying to unlock via htcdev unlock code but fastboot says cannot load 'Unlock_code.bin'
Please help
Tritan84 said:
EMERGENCY!! stuck in bootloader/fastboot loop! Won't allow me to go into recovery. Won't allow factory reset. The ROM said it installed succesfully. Banner says modified/Relocked. trying to unlock via htcdev unlock code but fastboot says cannot load 'Unlock_code.bin'
Please help
Click to expand...
Click to collapse
Oh man, what did you do? In your bootloader under OS is your firmware number. Is it still your old firmware? I don't know how you re-locked.
If you are in fastboot, type fastboot reboot-recovery and see if that works.
xunholyx said:
Oh man, what did you do? In your bootloader under OS is your firmware number. Is it still your old firmware? I don't know how you re-locked.
If you are in fastboot, type fastboot reboot-recovery and see if that works.
Click to expand...
Click to collapse
OS-3.28.605.4 (4.16.1540.8)
when i put in fastboot reboot-recovery, just a long list of commands show up
Tritan84 said:
OS-3.28.605.4 (4.16.1540.8)
when i put in fastboot reboot-recovery, just a long list of commands show up
Click to expand...
Click to collapse
I was relocked previously trying to update firmware. I completely forgot to unlock it before the ROM flash. I would assume the ROM wouldnt flash though if the phone was relocked. I'm still S-off. Fastboot isn't recognizing the files i want to flash. Won't flash the unlock code. Wouldn't flash a zip file before when trying to update firmware. Can I somehow fix why fastboot isn't flashing files, then try to use unlock code?
possible progress?? I wasn't in the correct file to fastboot flash files. I moved the unlock code download to the correct file as flashboot, then flashed it. It says "unlock token check successfully." but now it seems the phone is stuck in white htc screen. Is it ok to power down the phone when in this screen? maybe loading the software from new ROM?
so I went ahead and powered down the phone. Still S-off. Now has UNLOCKED banner, but behaving the same. Stuck in bootloader loop. Won't allow me to get into recovery
Tritan84 said:
I was relocked previously trying to update firmware. I completely forgot to unlock it before the ROM flash. I would assume the ROM wouldnt flash though if the phone was relocked. I'm still S-off. Fastboot isn't recognizing the files i want to flash. Won't flash the unlock code. Wouldn't flash a zip file before when trying to update firmware. Can I somehow fix why fastboot isn't flashing files, then try to use unlock code?
Click to expand...
Click to collapse
Okay. Being S-Off you don't need to lock your bootloader to flash firmware. But since you were trying to flash Developer Edition firmware, you would have to flash a stock Dev Ed backup first, and change your MID and CID.
Leave your phone plugged into your PC.
Go here and follow the option 2 instructions. You want the APP/EXE version to download. It should fix you up.
where do you people come from..you're a self proclaimed noob who has executed an unsupported carrier switch, which ends up with a half functional device as a result.. and then you decide to crank the up the hilarity to warp drive stupid by flashing ANOTHHER unsupported ROM combination on top.
the random signal dropping is most certainly a result of this conversion as I have a couple of related support tickets saying the same.
you should be thankful that unholy is so patient and willing to help.. and that we know he has nothing better to do
xunholyx said:
Okay. Being S-Off you don't need to lock your bootloader to flash firmware. But since you were trying to flash Developer Edition firmware, you would have to flash a stock Dev Ed backup first, and change your MID and CID.
Leave your phone plugged into your PC.
Go here and follow the option 2 instructions. You want the APP/EXE version to download. It should fix you up.
Click to expand...
Click to collapse
I Got ERROR [130]: Model ID Error
The firmware update utility cannot update your android phone.
Please get the correct Firmware update utility and try again.
I should note that when I got to the prompt to upgrade current firmware to new firmware.....the new firmware was not a sequence of numbers. It looked like random symbols.
nitephlight said:
where do you people come from..you're a self proclaimed noob who has executed an unsupported carrier switch, which ends up with a half functional device as a result.. and then you decide to crank the up the hilarity to warp drive stupid by flashing ANOTHHER unsupported ROM combination on top.
the random signal dropping is most certainly a result of this conversion as I have a couple of related support tickets saying the same.
you should be thankful that unholy is so patient and willing to help.. and that we know he has nothing better to do
Click to expand...
Click to collapse
I truly do appreciate Unholy's help. He's been great.
I've definitely been humbled by this experience.
Tritan84 said:
I truly do appreciate Unholy's help. He's been great.
I've definitely been humbled by this experience.
Click to expand...
Click to collapse
I'm not going to be able to come up with a solution tonight. Sorry. I'm going to have to consult with someone who is more of a firmware expert than I am. And the guy whom I will be talking to is probably just waking up (lives in Germany). I'll get back to you as soon as I can. Crappy, I know.
---------- Post added at 11:00 PM ---------- Previous post was at 10:44 PM ----------
Tritan84 said:
I Got ERROR [130]: Model ID Error
The firmware update utility cannot update your android phone.
Please get the correct Firmware update utility and try again.
I should note that when I got to the prompt to upgrade current firmware to new firmware.....the new firmware was not a sequence of numbers. It looked like random symbols.
Click to expand...
Click to collapse
You probably just have to change your MID back to M8_VZW. There are tutorials on xda. It's 11pm here and I get up at 4:30. I'm tired and need to sleep. Like I said, sorry. I'll give you more help tomorrow if you don't figure it out before hand on your own.
xunholyx said:
I'm not going to be able to come up with a solution tonight. Sorry. I'm going to have to consult with someone who is more of a firmware expert than I am. And the guy whom I will be talking to is probably just waking up (lives in Germany). I'll get back to you as soon as I can. Crappy, I know.
---------- Post added at 11:00 PM ---------- Previous post was at 10:44 PM ----------
You probably just have to change your MID back to M8_VZW. There are tutorials on xda. It's 11pm here and I get up at 4:30. I'm tired and need to sleep. Like I said, sorry. I'll give you more help tomorrow if you don't figure it out before hand on your own.
Click to expand...
Click to collapse
I think you're right. I've tried to search how to change modelid via fastboot since I can't boot the phone to run adb, but all the tutorials seem to be based on using adb. Is their a way to change via fastboot only?
SUCCESS! Well, I was able to reinstall TWRP via the appropriate adb/fastboot commands and flash my nandroid backup.
Unholy, I know you mentioned doing this command, but I did not know I had to put the .img file name within that command....result of being such a noob. You were awesome and I greatly appreciate you help.
Tritan84 said:
SUCCESS! Well, I was able to reinstall TWRP via the appropriate adb/fastboot commands and flash my nandroid backup.
Unholy, I know you mentioned doing this command, but I did not know I had to put the .img file name within that command....result of being such a noob. You were awesome and I greatly appreciate you help.
Click to expand...
Click to collapse
Cool. I glad you got everything sorted. :good:
Yeah and the guy from Germany doesn't have the time to look into this anyway...
Made a series of mistakes that led me to only have access to fastboot and recovery. It appears I'm capable of flashing things in fastboot. I can't access download mode at all (gives me an error saying it's unable to boot into download mode), which I believe you need in order to flash RUUs in the first place.
If anybody has a TWRP backup of system and boot that'd be awesome, but really need an img of download mode or a RUU or something to help me recover everything to normal. I am S-OFF and bootloader is unlocked.
Checked HTCdev and nothing was there for this device. All help appreciated.
How do you have fastboot when fastboot comands are done from download mode? Dont you have a stock system image that you made?
He means bootloader mode, the white screen. I think OP is SOL. That's why it's important to make backups, especially for exotic devices. I'm not sure if it's possible, but since he's s-off his best bet would be to convert to an unlocked or Verizon device if at all possible just to get the device working again and wait for either an ruu or backup.
If he is soffed he can flash an international ruu
Sent from my HTC 10 using XDA-Developers mobile app
Android The Greek said:
If he is soffed he can flash an international ruu
Click to expand...
Click to collapse
Cid and mid still needs to match
How did you go with this, OP? I just got the HTV32 (HTC10) here in Japan, and unlike previous HTC's I have owned here (Desire, M7), there seems to be no RUUs for Japan anywhere (or am I not looking hard enough...). Website HTCsoku seems very short on info on this model, and the former repository for all things HTC in Japan for modders and tinkerers, 'Scottish Vinegar', has disappeared. Will be getting Sunshine then flashing TWRP and SuperSU soon, but I always like to have the option of stock images, etc., handy, just in case things go tits up.
I remembered the case of failure to entering Download Mode in M9 which solution is flashing the hosd image (extract from firmware), you can give it a try
androg said:
How did you go with this, OP? I just got the HTV32 (HTC10) here in Japan, and unlike previous HTC's I have owned here (Desire, M7), there seems to be no RUUs for Japan anywhere (or am I not looking hard enough...). Website HTCsoku seems very short on info on this model, and the former repository for all things HTC in Japan for modders and tinkerers, 'Scottish Vinegar', has disappeared. Will be getting Sunshine then flashing TWRP and SuperSU soon, but I always like to have the option of stock images, etc., handy, just in case things go tits up.
Click to expand...
Click to collapse
Unfortunately was not able to get a hold of the stock RUU. I took my phone to my carrier and they gave me a new one free of charge despite the unlocked bootloader, S-OFF and TWRP being installed. Was just more careful on the replacement phone.
I actually am still looking for a stock RUU though.
Personally I made a TWRP backup before installing SuperSU. That way I can update with OTAs later on. (once we get an OTA we'll be able to pull the stock recovery img from it and update without issue).
Trying to convert this model to an international model was a terrible mistake. Au KDDI does not play well with these types of things. My Butterfly 3 is permanently SIM locked on AU's network for attempting the same thing (was trying to get Marshmallow at the time, which coincidentally is being released for the device next week).
I have been running Xposed and SuperSU with no issues at all though. If you get any "device encrypted" error after S-OFFing, just factory reset the data in TWRP.
Many domo's, DarkRazorZ!
I read that twrp-3.0.2-6-pme.img is the one to go for - that what you used?
Good you had no grief from HTC Japan. I actually sent back my M7 for the purple camera issue a few years back and did very little to disguise the fact it was unlocked and S-Offed. I think they are all fellow modders there and don't give a damn what we do. One reason why HTC is awesome.
I am now waiting for Nougat on the HTC10 (they (AU) just did a press release that it will be pushed soon), and as soon as that is on my phone, I shall be going the Sunshine route and installing aforementioned TWRP and so on. Getting fidgety, though... Xposed, Amplify, ad blocking... lemme at 'em.
DarkRazorZ said:
Unfortunately was not able to get a hold of the stock RUU. I took my phone to my carrier and they gave me a new one free of charge despite the unlocked bootloader, S-OFF and TWRP being installed. Was just more careful on the replacement phone.
I actually am still looking for a stock RUU though.
Personally I made a TWRP backup before installing SuperSU. That way I can update with OTAs later on. (once we get an OTA we'll be able to pull the stock recovery img from it and update without issue).
Trying to convert this model to an international model was a terrible mistake. Au KDDI does not play well with these types of things. My Butterfly 3 is permanently SIM locked on AU's network for attempting the same thing (was trying to get Marshmallow at the time, which coincidentally is being released for the device next week).
I have been running Xposed and SuperSU with no issues at all though. If you get any "device encrypted" error after S-OFFing, just factory reset the data in TWRP.
Click to expand...
Click to collapse
Hey I was wondering if you could help me on how to get a replacement device, I ran into the same problem as you did. Thanks
Hello DarkRazorZ.
I'm curious about your attempt to convert HTV32 to international.
It couldn't be done because of hardware compatibility issue among HTV32 and international?
Or because of just your own mistake in the process?
Did you try a method like this?
http://forum.xda-developers.com/htc-10/help/convert-htc-10-to-unlocked-t3384460
I'm in Japan and considering to buy HTV32, and I want to use it with international firmware.
I know this is your thread, but I can't find any information about this on web.
So could you share me your knowledge. Thanks.
the us unlocked version can be used on KDDI Au but the verizon radio has to be flashed for it to work and even then, you will only get 2g speeds.
Quadrider10 said:
the us unlocked version can be used on KDDI Au but the verizon radio has to be flashed for it to work and even then, you will only get 2g speeds.
Click to expand...
Click to collapse
No, I'm considering to buy HTV32(= HTC10 for Japan region), not other.
Well I'll make a new thread about this issue.
Thanks for replying Quadrider10, and sorry for disturbing DarkRazorZ.
Made a series of mistakes that led me to only have access to fastboot and recovery. It appears I'm capable of flashing things in fastboot. , which I believe you need in order to flash a stock or RUUs in the first place.
If anybody has a TWRP backup of system and boot that'd be awesome, but really need an img of download mode or a RUU or something to help me recover everything to normal. I am S-OFF and bootloader is unlocked.
DarkRazorZ said:
Made a series of mistakes that led me to only have access to fastboot and recovery. It appears I'm capable of flashing things in fastboot. I can't access download mode at all (gives me an error saying it's unable to boot into download mode), which I believe you need in order to flash RUUs in the first place.
If anybody has a TWRP backup of system and boot that'd be awesome, but really need an img of download mode or a RUU or something to help me recover everything to normal. I am S-OFF and bootloader is unlocked.
Checked HTCdev and nothing was there for this device. All help appreciated.
Click to expand...
Click to collapse
hii can u help me how to unlock bootloader on HTC 10 AU version
aSSikn said:
hii can u help me how to unlock bootloader on HTC 10 AU version
Click to expand...
Click to collapse
follow this tut:
https://www.htcdev.com/bootloader/
s2kaka said:
follow this tut:
htcdev
Click to expand...
Click to collapse
i already follow that tutor yesterday.. but when i insert token number the site always says error 170 "CID not allowed"
Okay, I'm giving up, I need someone to help me.
I was given my neighbours HTC One M9. It was working just fine. After he gave it to me, first thing I did was a factory reset because he didn't delete anything.
After that, the problems began. When I boot up the phone, even directly after resetting and even before the setup, I get an error "Google App stopped working". And after that, all couple of seconds another "com.google.process.gapps stopped working".
I tried several of the fixes out there on the web, but it didn't go away. I did another factory reset, and again even when I setup the phone I get those errors.
There is still Android 6.0 on the phone, so I wanted to update to 7.1
During install, I got the red triangle screen, on both attemps. Well, f*ck.
So, I went on to install a new OS. Never did this before, so I though this is a good chance to learn some more about Android.
It just got even more strange. When I'm in the bootloader, I saw
***Software status: Modified***
S-ON
LOCKED
***Security Warning***
Especially the modified software was very strange, since my neighbour has neither a clue nor any interested of fiddling with phones.
When I tried to go into Download Mode, it said "failed to boot into download mode".
Recovery mode worked just fine.
Therefore, I couldn't do anything to install a new OS.
Next I bought the Sunshine App and S-OFFd my phone, which worked just fine.
Now I'm S-OFF, unlocked and the Security Warning has gone. The software is apparently still modified.
But when I go into download mode, I get the black screen with the silver logo and red text for a while, then the phone proceeds to boot normally.
What the f*uck? I'm just out of idead what to do now. Please don't let it be a dead nand... it's such a nice phone, and apart from the google app errors, it works perfectly. I used it for some surfing around today and it works really well. I can't imagine it being broken.
Thanks for your help!
What variant do you have? Firmware version?
side_flip15 said:
What variant do you have? Firmware version?
Click to expand...
Click to collapse
Firmware is 3.35.166.12
I don't know exactly about the variant, this is what the IMEI checker says:
SKU , VF , German , CHE , HTC , CH , Swisscom , Bootloader Lock , Dark Gunmetal/Dark Gunmetal , w/o SIM Lock , HIMA#UHL-D1
I have a bug report of the gapps-Error. Would that be helpful?
I have some bad news for you:
According to everything that you describe in the opening post it's the dead nand issue. There's nothing you can do. And if you send the phone to HTC they will change the motherboard which means that you have to buy sunshine, again, after they send the phone back to you.
@Flippy498 Is the "failed to boot into download mode"? error a sign of dead nand? This happened to me before. I flashed hosd.img via bootloader to fix this. Still using my M9.
It's the combination of several things that make me think it's a dead nand:
The security warning indicates that there is no OS installed. If that happened without manually deleting the OS via a custom recovery like TWRP then chances are high that the nand died.
The software status is modified although the phone is locked and S-ON. The only other explanation for this combination would be that the owner failed while using one of the 100% stock guides that convert S-OFF back to S-ON, Unlocked back to Locked and modified back to original. However, the dead nand issue is quite common during the recent months and the guides are hidden somewhere in the Genereal section (in other words: not located on the first page). Therefore, I think that chances are higher that it's the dead nand issue.
Last but not least: The black download mode error screen in combination with the other two symptoms.
Did you report about your tries to revive your phone somewhere here on xda? Do you have a link? What kind of symptoms did you face aside from the black error screen? Has your phone been S-ON or S-OFF?
If you really faced a dead nand issue and could repair your phone by your own that would be a game-changing and I could finally overhaul the FAQ of the ReadMe thread. However, discussions like the one that starts with this post make me think that you might have faced a different problem with your download mode since it really looks like the dead nand isn't fixable without changing the hardware.
Flippy498 said:
I have some bad news for you:
According to everything that you describe in the opening post it's the dead nand issue. There's nothing you can do. And if you send the phone to HTC they will change the motherboard which means that you have to buy sunshine, again, after they send the phone back to you.
Click to expand...
Click to collapse
Flippy498 said:
It's the combination of several things that make me think it's a dead nand:
The security warning indicates that there is no OS installed. If that happened without manually deleting the OS via a custom recovery like TWRP then chances are high that the nand died.
The software status is modified although the phone is locked and S-ON. The only other explanation for this combination would be that the owner failed while using one of the 100% stock guides that convert S-OFF back to S-ON, Unlocked back to Locked and modified back to original. However, the dead nand issue is quite common during the recent months and the guides are hidden somewhere in the Genereal section (in other words: not located on the first page). Therefore, I think that chances are higher that it's the dead nand issue.
Last but not least: The black download mode error screen in combination with the other two symptoms.
Did you report about your tries to revive your phone somewhere here on xda? Do you have a link? What kind of symptoms did you face aside from the black error screen? Has your phone been S-ON or S-OFF?
I didn't have to revive it, except that Google-error it works beautifully. That' broken download mode the only symptom I have. The phone is (meanwhile after Sunshine) S-OFF
If you really faced a dead nand issue and could repair your phone by your own that would be a game-changing and I could finally overhaul the FAQ of the ReadMe thread. However, discussions like the one that starts with this post make me think that you might have faced a different problem with your download mode since it really looks like the dead nand isn't fixable without changing the hardware.
Click to expand...
Click to collapse
Well, there are two things that leave me hoping it's not a dead nand.
• Apart from that com.google.process.gapps-error, it works like a charm. No crashes, no sudden reboots. I really can't imagine a broken part of a motherboard making no trouble, wouldn't that render the part
useless? And is that Google-App Error really relatable?
• After letting the Sunshine App do its job, I don't get an error message in the download mode (well, it just boots normally after a while), the security warning has gone as well. Only the modified software is
suspicious.
side_flip15 said:
@Flippy498 Is the "failed to boot into download mode"? error a sign of dead nand? This happened to me before. I flashed hosd.img via bootloader to fix this. Still using my M9.
Click to expand...
Click to collapse
I've heard of that as well. I didn't really find any tutorial on that and I'm a bit afraid to experiment with that. Do you mind sharing how you achieved that?
Instructions are linked in the FAQ of the ReadMe thread. They're the solution for the blue download mode issue.
The thing is that the download mode can't just break without either you actively manipulating it or the hardware of the phone dying. The same applies to that security warning. Either you manually delete the OS or the hardware fails and the phone isn't able to read the installed OS correctly, anymore. Therefore, I wouldn't put my hopes too high if I were you. Of course I could be wrong but I've read a lot of reports of dead nand phones since last year's summer and my feeling tells me that this is another one.
As a sidenote: You're the first user that tried to S-OFF/successfully S-OFFed his phone after such errors occurred since sunshine can't unlock the bootloader on firmware 4.x and hasn't been able to do so on older firmware versions when the issue appeared the first time. Therefore, I don't know which influence sunshine has on the whole situation.
Sent from my HTC One M9 using XDA Labs
Flippy498 said:
Instructions are linked in the FAQ of the ReadMe thread. They're the solution for the blue download mode issue. Great, thanks!
The thing is that the download mode can't just break without either you actively manipulating it or the hardware of the phone dying. The same applies to that security warning. Either you manually delete the OS or the hardware fails and the phone isn't able to read the installed OS correctly, anymore. Therefore, I wouldn't put my hopes too high if I were you. Of course I could be wrong but I've read a lot of reports of dead nand phones since last year's summer and my feeling tells me that this is another one.
Click to expand...
Click to collapse
Yes, I know. Maybe I just don't want to accept that fact to keep my motivation to try to save the phone...
So what my optimism suspects is that somewhere deep in the firmware there is something corrupted. That leaves the System modified and the Google app confused.
After all, recovery mode works just fine. If you check what other people experience with a dead nand, it's got to do with sudden reboots, bootloops, failed download AND recovery modes et cetera.
As a sidenote: You're the first user that tried to S-OFF/successfully S-OFFed his phone after such errors occurred since sunshine can't unlock the bootloader on firmware 4.x and hasn't been able to do so on older firmware versions when the issue appeared the first time. Therefore, I don't know which influence sunshine has on the whole situation.
Click to expand...
Click to collapse
A little more hope rised in me...
sechsgangschakter said:
I've heard of that as well. I didn't really find any tutorial on that and I'm a bit afraid to experiment with that. Do you mind sharing how you achieved that?
Click to expand...
Click to collapse
You can try this...
Get the firmware.zip matching your current firmware @Flippy498 's thread here. Links are in the spreadsheet in post #2. Extract the hosd.img from the zip and flash in bootloader mode .
Code:
fastboot flash hosd hosd.img
then try to reboot to download mode. If it does not work, try other firmware.zip but should be in the same build number at least X.XX.
SAME HERE PROBLEM PLEASE HELP
I HAVE HTC ONE M9 OPJA100 JUST GO ON LOCKED SCREEN WHEN REBOOT TO BOOTLOADER ITS RESTART AGAIN EVEN NOT GO DOWNLOAD MODE OR RECOVERY MODE.
I WAS JUST MAKE ROOT THEN ITS STUCK ON LOGO
NOT GO FASTBOOT MODE TO CHECK CID OR FIRMWARE
WHAT I DO ?????
ITS LOCKED
S-ON ALSO
side_flip15 said:
You can try this...
Get the firmware.zip matching your current firmware @Flippy498 's thread here. Links are in the spreadsheet in post #2. Extract the hosd.img from the zip and flash in bootloader mode .
Code:
fastboot flash hosd hosd.img
then try to reboot to download mode. If it does not work, try other firmware.zip but should be in the same build number at least X.XX.
Click to expand...
Click to collapse
THANK YOU!!!!
It finally works!
Edit: I installed resurrection Remix. Working perfectly, I really don't think there is anything dead in that phone. It's great, thank you for your help!
sechsgangschakter said:
THANK YOU!!!!
It finally works!
Edit: I installed resurrection Remix. Working perfectly, I really don't think there is anything dead in that phone. It's great, thank you for your help!
Click to expand...
Click to collapse
Glad I helped you:highfive:
side_flip15 said:
Get the firmware.zip matching your current firmware @Flippy498 's thread here. Links are in the spreadsheet in post #2. Extract the hosd.img from the zip and flash in bootloader mode .
Click to expand...
Click to collapse
Just for the record, that's not my thread. It's owned by Sneakyghost.
@sechsgangchakter: I'm glad to hear that your phone is working, again.
Flippy498 said:
Just for the record, that's not my thread. It's owned by Sneakyghost.
Click to expand...
Click to collapse
Oh god! Sorry
Credits to @Sneakyghost :highfive:
Hello, I am having a very similar issue. I am looking for the hosd.img file for Verizon. I dont see it at https://docs.google.com/spreadsheets/d/1ZaiJ3F_f76sVa4daU5H62OYi5Bj23LEBBv4xDTQ8y-M/pubhtml. Please help. Thanks
You won't find any CDMA files in that spreadsheet because the xda thread that sheet belongs to only supports GSM devices and clearly states that it'll never support CDMA.
Flippy498 said:
You won't find any CDMA files in that spreadsheet because the xda thread that sheet belongs to only supports GSM devices and clearly states that it'll never support CDMA.
Click to expand...
Click to collapse
So no one knows of one available for Verizon m9? What would happen if I used a GSM one?
You would probably damage your phone unrecoverably. GSM and CDMA are not compatible with each other due to the different partition layouts.
However, why don't you extract the needed file from a RUU that matches your current firmware version? That's how those firmware packs in the linked thread got made, as well. There's a thread with a RUU extraction tool linked in the RUU section of the ReadMe thread.
Sent from my HTC One S using XDA Labs
Flippy498 said:
You would probably damage your phone unrecoverably. GSM and CDMA are not compatible with each other due to the different partition layouts.
However, why don't you extract the needed file from a RUU that matches your current firmware version? That's how those firmware packs in the linked thread got made, as well. There's a thread with a RUU extraction tool linked in the RUU section of the ReadMe thread.
Sent from my HTC One S using XDA Labs
Click to expand...
Click to collapse
Good idea, ill give that a try. Thanks
Ok so in the last thread I started I learned how flashing ROMS works, with the matching firmware, CID's, and other stuff, but now I have another issue... The ROM that I was able to flash was the TeamVenom Viper One ROM for Android L (Lolipop)....The ROM version I used was Viper 3.5.0, but now I would like to upgrade to Viper 6.1.0, but it requires Android M (HTC Firmware 3.x).... I do not have a stock ROM to go back to update, and the HTCDev RUU.exe to update gives error code 132 (similar to error code 12, Thanks for the ReadMe page btw @Flippy498), which is a signature error (which is odd because it is straight from HTCDev) and I cannot find a zip file of 3.xx.502.xx to flash that isn't A) corrupted upon download, or B) has a working link... I don't think I can update Viper because it says "Flashing the new Android M firmware is a must, else your phone won’t boot!!" (trust me it doesn't boot, I've tried)... But I read somewhere that having a Team Venom account will allow you to receive OTA updates, yet when I check for OTA updates through the Venom app in the app drawer it doesn't find any available updates, which I know is incorrect because as I said I'm still on Android L (5.1)... What would I need to do from here, how would I A)fix HTC installer, or B) does anybody have a WORKING flashable stock android zip to update from Lollipop to Marshmallow...
Thanks in advanced!
Forum N00b,
qwsderter
qwsderter said:
but now I would like to upgrade to Viper 6.1.0, but it requires Android M (HTC Firmware 3.x)
Click to expand...
Click to collapse
It's actually recommended to use firmware 4.x for Viper 6.1.0 (although the rom boots on 3.x, as well).
qwsderter said:
I do not have a stock ROM to go back to update, and the HTCDev RUU.exe to update gives error code 132 (similar to error code 12, Thanks for the ReadMe page btw @Flippy498), which is a signature error (which is odd because it is straight from HTCDev)
Click to expand...
Click to collapse
It's not odd at all. Re-read the explanation of the error or the RUU section. Both explain why the flash fails.
qwsderter said:
I cannot find a zip file of 3.xx.502.xx to flash that isn't A) corrupted upon download, or B) has a working link
Click to expand...
Click to collapse
I checked the link in the ReadMe thread. It'sworking fine. If the file gets corrupted during the download then it's due to your setup (e.g. an interruption of your internet connection during the download, etc.).
qwsderter said:
But I read somewhere that having a Team Venom account will allow you to receive OTA updates, yet when I check for OTA updates through the Venom app in the app drawer it doesn't find any available updates, which I know is incorrect because as I said I'm still on Android L (5.1)
Click to expand...
Click to collapse
There is no OTA for updating Venom 3.5.0. Custom roms can't update your firmware. Therefore, you need to update it on your own and to flash a full rom whenever the rom's base get's changed. The OTAs only update the rom (e.g. from 3.0.0 to 3.1.0). That's why there isn't an OTA for 6.0.0 -> 6.1.0, either. 6.1.0 is based on a different firmware than 6.0.0. You might want to read the article that is labeled as "The difference between rom and firmware" in the further reading section of the ReadMe thread.
Flippy498 said:
It's actually recommended to use firmware 4.x for Viper 6.1.0 (although the rom boots on 3.x, as well).
It's not odd at all. Re-read the explanation of the error or the RUU section. Both explain why the flash fails.
I checked the link in the ReadMe thread. It'sworking fine. If the file gets corrupted during the download then it's due to your setup (e.g. an interruption of your internet connection during the download, etc.).
There is no OTA for updating Venom 3.5.0. Custom roms can't update your firmware. Therefore, you need to update it on your own and to flash a full rom whenever the rom's base get's changed. The OTAs only update the rom (e.g. from 3.0.0 to 3.1.0). That's why there isn't an OTA for 6.0.0 -> 6.1.0, either. 6.1.0 is based on a different firmware than 6.0.0. You might want to read the article that is labeled as "The difference between rom and firmware" in the further reading section of the ReadMe thread.
Click to expand...
Click to collapse
Hey thanks Flippy you are the clutch, but I can verify that the files ARE corrupt.... I have downloaded it twice, and I have google fiber so I can guarantee that the connection was consistent. Winrar said the file was corrupted, along with when trying to flash TWRP would flash.... Any other ideas, you are the master at this Flippy, there must be another way...
qwsderter said:
Hey thanks Flippy you are the clutch, but I can verify that the files ARE corrupt.... I have downloaded it twice, and I have google fiber so I can guarantee that the connection was consistent. Winrar said the file was corrupted, along with when trying to flash TWRP would flash....
Click to expand...
Click to collapse
You should re-read the ReadMe thread. They're not corrupt. I thought that with "corrupt" you meant the MD5 checksum wouldn't match after the download. That WinRar error message is expected behaviour.
Flippy498 said:
You should re-read the ReadMe thread. They're not corrupt. I thought that with "corrupt" you meant the MD5 checksum wouldn't match after the download. That WinRar error message is expected behaviour.
Click to expand...
Click to collapse
Ah gotcha... So I used the decryption tool to make a SD flashable zip, and what do you know, TWRP crashes when I swipe to flash... How come I can flash other ROMs but I can't flash stock roms without it crashing (Device turns off)
Please don't tinker around without knowing what you're doing and (as said before) read what got written in the FAQ and the RUU section. Extracting the *.zip wasn't needed at all since there already is a download link for an extracted *.zip. In addition, there are step by step instructions how RUUs can/need to get flashed.
Sent from my HTC One M9 using XDA Labs
Flippy498 said:
Please don't tinker around without knowing what you're doing and (as said before) read what got written in the FAQ and the RUU section. Extracting the *.zip wasn't needed at all since there already is a download link for an extracted *.zip. In addition, there are step by step instructions how RUUs can/need to get flashed.
Sent from my HTC One M9 using XDA Labs
Click to expand...
Click to collapse
Ok thank you "again" I have officially read your ENTIRE guide 3 times now, Not trying to offend you or make shame of your work, but the problem is I "THINK" that I am following your work.... I download the RUU for my phone (in this case SKU: 502 - CID: CWS__001 VERSION 2.11.502 (I have also tried 3.38.502.41 to no avail)) and everything is going as planned, I have verified that BOTH the CID and MID are matching that of my phone.... But when I plug SD card into Phone in download mode I get no such asked if I want to flash the file (as your guide says to do).... Ok so if I try to flash through TWRP it crashes, and if I try to Fastboot Flash the file I get what is seen in the picture attachment, and then nothing happens, except the bootloader page says "Under flash" and adds another line saying Under flash everytime I press the power button... My phone is S-OFF, is there another possible way to do this.... I swear to go I have read your ReadMe thread and I'm not just being arrogant, but my phone WILL not flash to ANY STOCK ROM downloaded anywhere from the Internet... @Flippy498 I promise there has to be something I missed in your ReadMe (I HAVE NO IDEA HOW I COULD) or i'm getting damaged ROMs... I'm sorry that you have to put up with me and help me thus far, and let me say the XDA community deserves people like you, and less people like me who think they know what they are doing until something breaks...
EDIT: It seems the phone is missing a located at /dev/fastboot_download_j in the CMD screenshot. Should that be said issue how would I go about fixing that...
Your SD card isn't bigger than 32gb and formatted to fat32? The file is placed in the root directory of the card and renamed to 0PJAIMG.zip (not 0PJAIMG.zip.zip and not OPJAIMG.zip)? The SD card method as it is written there already got used by a lot of users without any issues. The problem in this case must be on your end. What kind of error is stated at the bottom of your download mode? The M9 always tells you what's wrong. Either the SD card isn't mounted correctly (in other words you're using an unsupported format) or the 0PJAIMG.zip file is missing (in other words either non-existent on your sd card, placed in the wrong direction or renamed wrongly).
And of course TWRP crashes. Not every *.zip file can get flashed via TWRP just because it's a *.zip. (Just like not every *.zip can/should get unzipped just because it's a *.zip.) The only methods that can be used for flashing a RUU are mentioned in the ReadMe thread. And that's what I meant with "don't tinker around". You're doing things with files they're not meant to be done with.
The fastboot flash on the other hand can't work with the commands shown in your screenshot. That's a mistake in my guide. :silly: And it's even explained in the text above the instructions. I'm wondering why nobody (including me) noticed that before. I can only assume that it's because fastboot flashing doesn't get used that often for RUUS. The commands need to start with "htc_fastboot" not "fastboot". The normal fastboot isn't able to flash RUUs. I've fixed that part. Thanks for making me aware of that.
And in regard to the "damaged roms": The ReadMe thread explains how to check whether your downloads are fine (key word: md5).
Flippy498 said:
Your SD card isn't bigger than 32gb and formatted to fat32? The file is placed in the root directory of the card and renamed to 0PJAIMG.zip (not 0PJAIMG.zip.zip and not OPJAIMG.zip)? The SD card method as it is written there already got used by a lot of users without any issues. The problem in this case must be on your end. What kind of error is stated at the bottom of your download mode? The M9 always tells you what's wrong. Either the SD card isn't mounted correctly (in other words you're using an unsupported format) or the 0PJAIMG.zip file is missing (in other words either non-existent on your sd card, placed in the wrong direction or renamed wrongly).
And of course TWRP crashes. Not every *.zip file can get flashed via TWRP just because it's a *.zip. (Just like not every *.zip can/should get unzipped just because it's a *.zip.) The only methods that can be used for flashing a RUU are mentioned in the ReadMe thread. And that's what I meant with "don't tinker around". You're doing things with files they're not meant to be done with.
The fastboot flash on the other hand can't work with the commands shown in your screenshot. That's a mistake in my guide. :silly: And it's even explained in the text above the instructions. I'm wondering why nobody (including me) noticed that before. I can only assume that it's because fastboot flashing doesn't get used that often for RUUS. The commands need to start with "htc_fastboot" not "fastboot". The normal fastboot isn't able to flash RUUs. I've fixed that part. Thanks for making me aware of that.
And in regard to the "damaged roms": The ReadMe thread explains how to check whether your downloads are fine (key word: md5).
Click to expand...
Click to collapse
Once again Thank you for helping me out, the htc_flashboot command was what I needed, I was able to flash the stock rom through the command.... May I just say, you sir know what you are doing, and I wish you continue to help other people on this forms just like you've helped me.... I Installed the 2.x rom, but the OTA update didn't work for some reason... so I'm gonna flash the 4.x and then install ViperOne again...
And when I was saying "Damaged Roms" I was not implying that it was corrupted over the internet, but rather that they were never working in the first place...
Oh, that microSD card I had is in the trash now, since the only device that recognizes it is my pc, I assume it is on the brink of death...
Thanks again,
qwsderter
qwsderter said:
I Installed the 2.x rom, but the OTA update didn't work for some reason
Click to expand...
Click to collapse
That's probably like that due to AT&T denying OTAs to phones that currently aren't using an AT&T sim card. You wouldn't be the first user that isn't able to receive AT&T updates for the M9. Don't ask me why they're allowed to do so. Something like that wouldn't be possible in the EU.
qwsderter said:
so I'm gonna flash the 4.x and then install ViperOne again
Click to expand...
Click to collapse
Don't forget that you need to flash one of Sneakyghost's firmware packs if you want to be able to flash 4.x RUUs. (Keyword: encryption keys)
qwsderter said:
And when I was saying "Damaged Roms" I was not implying that it was corrupted over the internet, but rather that they were never working in the first place
Click to expand...
Click to collapse
That's actually the difference between my ReadMe thread and most of the RUU collections on other websites. The files only get linked if they're known to be working whereas other sites link every RUU they can find. There are a lot more RUUs for the M9 out there than the ones I listed. However, these RUUs either aren't able to get flashed successfully or their roms aren't able to receive any OTAs - e.g. there's a second RUU for firmware 1.32.401.15 than the one that is linked in my thread and if you flash that other RUU you're stuck on its firmware version until you flash a different RUU.
qwsderter said:
Oh, that microSD card I had is in the trash now, since the only device that recognizes it is my pc, I assume it is on the brink of death
Click to expand...
Click to collapse
If it's really broken you should thank whichever god you believe in that your phone wasn't able to recognize the card. Since your phone is S-OFF all security checks on your phone are disabled. That means if a file gets corrputed on the SD card due to its partition being messed up your phone would still accept the broken RUU, nonetheless. This would most likely lead to unrecoverable damages. In other words, chances are high in such situations that you create a fancy but expensive paperweigth.
Flippy498 said:
That's probably like that due to AT&T denying OTAs to phones that currently aren't using an AT&T sim card. You wouldn't be the first user that isn't able to receive AT&T updates for the M9. Don't ask me why they're allowed to do so. Something like that wouldn't be possible in the EU.
Click to expand...
Click to collapse
Funny, I thought the same thing, until I realized it was ATT who I am paying every month to rip my girlfriend and I off. Well oh well, I know you are in Germany (From your profile) but if you ever come to the United States, I will say from my personal experience (my opinion, not facts) ATT has seemed to have the broadest coverage, but also is the (2nd) most constrictive (Verizon seems very constraining), to me ATT feels premium but they are also (in my opinion) the most likely to royally screw up... Oh well, no OTA time to flash!!!
Flippy498 said:
If it's really broken you should thank whichever god you believe in that your phone wasn't able to recognize the card. Since your phone is S-OFF all security checks on your phone are disabled. That means if a file gets corrputed on the SD card due to its partition being messed up your phone would still accept the broken RUU, nonetheless. This would most likely lead to unrecoverable damages. In other words, chances are high in such situations that you create a fancy but expensive paperweigth.
Click to expand...
Click to collapse
Trust me, when I tried the SD card in the phone I thought, "That is a little odd", then both of my ASUS MemoPads didn't detect it either EVEN THOUGH THEY WERE RUNNING, I just assumed that they didn't work because MemoPads are the most budget friendly tablets ever and something broke, so I go to my Nexus 7 and realize it doesn't have an SD card slot so I couldn't test, so I popped the card in our Camera... Low and behold it doesnt detect.... Now the true question, why did my desktop detect it, eh whatever not worth my time.... The gods were looking down on me, they broke my $10 microSD and not my more than 10$ phone.....
Once again thank you for the help Flippy, you have no idea how much it hurt using my iPhone 5 for 2 days, I felt so inferior
So i was trying to install the latest nougat roms and realized i need to be on 4.xx for them.
I am on 3.xx
So i tried to update via the latest ruu from htc.
http://www.htc.com/us/support/rom-downloads.html
Did not work.
Then i realized that the rom was for a developers edition phone which mine is not.
So i downloaded the latest 3.xx rom. for the non developer phone.
After i downloaded it, I realized it was the same 4.xx ruu that i downloaded before. So i thought my mistake.
Go back and download AGAIN and yup, the link they provide in the "details and instuctions" section for the 3.xx rom is definitely for the 4.xx ruu.
When i click the download link without going into details. the link does not work.
Weird thing. on this page http://www.htc.com/us/support/updates.aspx
They do not specify developer edition.
So now the question is. IS 4.xx the latest update for all t-mo m9 phones and i am just having a problem installing.
Or do i need to find the 3.xx rom from a different source.
So i checked on a friends stock m9 and indeed it has the 4.47 update.
So i guess i am just doing something wrong. I am rooted but i never chose the option in twrp to modify files.
I can connect to the ruu in download mode. I tells me the correct rom that i have on the phone and offers to update. Once i choose update it seems to work fine. Reboots my phone then gives me error 123.
I cant seem to find a zip for it. Or a copy of the older ruu.
If anybody can point me in the direction of a database somewhere that would be super helpful. I know the mods used to keep them stickied at the top.
I do have a ruu and zip on my computer from a couple years ago that i will try too.
Tried to flash the last ruu i flashed before. got error 155 and now am stuck in flashing mode. With a half flashed phone. no way to reset it. 10 second power button does not work. cant pull the battery as the ruu advises me to do.
Guess im waiting for the phone to die from 100%
I think the problem is simple and something i totally forgot in the last couple years.
I NEED TO RE LOCK MY BOOTLOADER. but who knows. apparently its just me on here.
SO LONG FOR GOOD ADVICE FROM XDA.
BOOOO.
Please don't forget that this is a forum and not a support-hotline/-chat where people get payed for replying immediately. Most of us are doing this as their hobby and aren't able to be online 24/7. It might take some time till you get a reply. Especially if you post in a section that shows almost no activity aside from some new questions being asked. Most (former) users have already moved on to other devices due to the age of the M9 and many devs left the development scene due to the end users on xda that became more and more toxic and demanding during the last couple of years.
myphonesbetter said:
So i was trying to install the latest nougat roms and realized i need to be on 4.xx for them.
I am on 3.xx
Click to expand...
Click to collapse
You actually don't need firmware 4.x. Firmware 3.x is compatible with the latest custom roms, as well. They only run "better" on firmware 4.x.
myphonesbetter said:
So i tried to update via the latest ruu from htc.
http://www.htc.com/us/support/rom-downloads.html
Did not work.
Then i realized that the rom was for a developers edition phone which mine is not.
So i downloaded the latest 3.xx rom. for the non developer phone.
After i downloaded it, I realized it was the same 4.xx ruu that i downloaded before. So i thought my mistake.
Go back and download AGAIN and yup, the link they provide in the "details and instuctions" section for the 3.xx rom is definitely for the 4.xx ruu.
When i click the download link without going into details. the link does not work.
Click to expand...
Click to collapse
HTC is a bit lazy in regard to updating their webpage. You're always only able to download the latest RUU. However, you don't mention which variant you own. There is more than just one non-dev edition variant. Nevermind, you mentioned it in one if your following posts.
myphonesbetter said:
Weird thing. on this page http://www.htc.com/us/support/updates.aspx
They do not specify developer edition.
So now the question is. IS 4.xx the latest update for all t-mo m9 phones and i am just having a problem installing.
Or do i need to find the 3.xx rom from a different source.
Click to expand...
Click to collapse
Firmware 4.x is the latest version for all SKUs/variants and there won't be any further updates since the M9 reached the EOL stage almost a year ago.
myphonesbetter said:
So i checked on a friends stock m9 and indeed it has the 4.47 update.
Click to expand...
Click to collapse
Is that a typo? I only know about firmware 4.27.531.6 for the T-Mobile US variant.
myphonesbetter said:
So i guess i am just doing something wrong. I am rooted but i never chose the option in twrp to modify files.
Click to expand...
Click to collapse
It's possible to break the OTA-update function by modifying the system via a root file explorer, as well.
myphonesbetter said:
I can connect to the ruu in download mode. I tells me the correct rom that i have on the phone and offers to update. Once i choose update it seems to work fine. Reboots my phone then gives me error 123.
Click to expand...
Click to collapse
Is that another typo? I'd have expected error 132 since firmware 3.x and 4.x are using different encryption keys. You can't update using a RUU. You need to use the software update function of the system settings.
myphonesbetter said:
I cant seem to find a zip for it. Or a copy of the older ruu.
If anybody can point me in the direction of a database somewhere that would be super helpful. I know the mods used to keep them stickied at the top.
Click to expand...
Click to collapse
The "database" is still stickied (in not only one but two subforums of the M9 section - the general and the q&a section). Therefore, I'm a bit surprised that you weren't able to find what you're looking for. In addition the thread I'm talking about is not only a database, it even contains all information you would have needed for solving your issues, already.
myphonesbetter said:
I do have a ruu and zip on my computer from a couple years ago that i will try too.
Click to expand...
Click to collapse
If the RUU is older than your current firmware then you won't be able to use it.
myphonesbetter said:
Tried to flash the last ruu i flashed before. got error 155 and now am stuck in flashing mode. With a half flashed phone. no way to reset it. 10 second power button does not work. cant pull the battery as the ruu advises me to do.
Guess im waiting for the phone to die from 100%
Click to expand...
Click to collapse
Error 155 means that you either try to flash a RUU that is too old or made for a different variant than the one you own. The key combination you're looking for is the power button plus volume down up and you need to keep them pressed for about 30 seconds. HTC changed that on one of the devices that came out before the M9. Letting the battery die is a bad idea, though. You'll damage it this way.
myphonesbetter said:
I think the problem is simple and something i totally forgot in the last couple years.
I NEED TO RE LOCK MY BOOTLOADER. but who knows. apparently its just me on here.
Click to expand...
Click to collapse
No you don't. I can't discourage people enough from relocking this phone's bootloader if the phone is S-ON and not 100% stock and you don't have a RUU at hand that you already used successfully on your phone. HTC's security checks will prevent the device from booting if anything is modified (e.g. TWP being installed) while the bootloader is locked or relocked. They don't differentiate between "broken" and "custom" files and think that the modified software is broken. Therefore, the checks are trying to prevent the hardware from getting damaged by preventing the device from booting. In addition, if OEM Unlock isn't activated in the developer settings of the currently installed rom then there is no way to re-unlock the phone. That's an FRP (factory reset protection) Google introduced with android 5.1 (which equals firmware 2.x of the M9).
Flippy498 said:
Please don't forget that this is a forum and not a support-hotline/-chat where people get payed for replying immediately. Most of us are doing this as their hobby and aren't able to be online 24/7. It might take some time till you get a reply. Especially if you post in a section that shows almost no activity aside from some new questions being asked. Most (former) users have already moved on to other devices due to the age of the M9 and many devs left the development scene due to the end users on xda that became more and more toxic and demanding during the last couple of years.
Click to expand...
Click to collapse
Yah. I get it. Was kind of just shouting to get some attention.
Ive noticed that not just this forum but many other forums that i used to use have lossed a lot of popularity.
I think because facbook groups and things like reddit that cover all subjects.
The problem with those places is that they are so unorganized.
Maybe thats also part of why its become so unorganized here. just what people are used to.
I honestly wasnt expecting actual info. Thank you.
Flippy498 said:
You actually don't need firmware 4.x. Firmware 3.x is compatible with the latest custom roms, as well. They only run "better" on firmware 4.x.
Click to expand...
Click to collapse
Well i was afraid to brick it so i figured out (accidentally) how to update.
Flippy498 said:
Firmware 4.x is the latest version for all SKUs/variants and there won't be any further updates since the M9 reached the EOL stage almost a year ago.
Is that a typo? I only know about firmware 4.27.531.6 for the T-Mobile US variant It's possible to break the OTA-update function by modifying the system via a root file explorer, as well..
Click to expand...
Click to collapse
Yes that was. it is 4.27.
I could not find any older ruu's on their site. Or anywhere for that matter. none with active links at least.
Flippy498 said:
Is that another typo? I'd have expected error 132 since firmware 3.x and 4.x are using different encryption keys. You can't update using a RUU. You need to use the software update function of the system settings.
Click to expand...
Click to collapse
Yes 132. I did not realize that. Do you mean i would need to update via ota? by searching for updates.
Flippy498 said:
If the RUU is older than your current firmware then you won't be able to use it.
Error 155 means that you either try to flash a RUU that is too old or made for a different variant than the one you own. The key combination you're looking for is the power button plus volume down and you need to keep them pressed for about 30 seconds. HTC changed that on one of the devices that came out before the M9. Letting the battery die is a bad idea, though. You'll damage it this way.
Click to expand...
Click to collapse
So i was originally trying to flash the latest frimware 4.27.xxx but i kept getting error 132.
And on the htc website it has 2 sections for ruu's m9 ans m9 developer. So i just figured it was the wrong one.
So i figured i would try the last ruu that i flashed before installing the rom that i ran for almost 2 years (lee droid)
when i flashed that, it got halfway through and gave me error 155. but left my phone in the middle of an update. Apparently the power button is disabled during this process.
it tell you to pull the battery or hold the power button for 10 seconds then try to recover from the boot using the ruu.
Well i could not reboot the phone so i just started the recover process. This rebooted my phone a few times then just started flashing the rom. To my surprise it worked.
It also re-locked my phone.
After that, now that im stock, i tried to flash the 4.27 ruu. still 132.
So i tried to run the ota's and they worked.
Took about 4 hours and 7 updates or so. probably 5 gigs on the data plan but finally it finshed with a 1.1 gig update to 4.27.
Im not sure why the first flash failed or why it worked, but eventually it did work.
Flippy498 said:
No you don't. I can't discourage people enough from relocking this phone's bootloader if the phone is S-ON and not 100% stock and you don't have a RUU at hand that you already used successfully on your phone. HTC's security checks will prevent the device from booting if anything is modified (e.g. TWRP being installed) while the bootloader is locked or relocked. They don't differentiate between "broken" and "custom" files and think that the modified software is broken. Therefore, the checks are trying to prevent the hardware from getting damaged by preventing the device from booting. In addition, if OEM Unlock isn't activated in the developer settings of the currently installed rom then there is no way to re-unlock the phone. That's an FRP (factory reset protection) Google introduced with android 5.1 (which equals firmware 2.x of the M9).
Click to expand...
Click to collapse
Ive always relocked my htcs before running an ruu. If not then they never seem to work. I dont mind it because it takes about 10 seconds. and i already hae the token. I actually remembered the majority of the commands.
Maybe its causing another problem that i dont know about.
I did see the oem unlock in developer options if that is what you are talking about.
I was using the last ruu that i had used. but i also flashed a rom and it was a long time in between.
Also i installed the old version of lee droid on 4.27.xxx and it seemed to work fine. I did this on accident though. Flashed the wrong zip. Re-flashed the latest 4.0 and it seems to be working great. Noticing a couple little lags. Might go to the stock rom just rooted and debloated. It seemed to run a little smoother than leedroid for the time i was using it. but i felt like they were trying to extract my stem cells via confusing TOS agreements.
myphonesbetter said:
Apparently the power button is disabled during this process.
it tell you to pull the battery or hold the power button for 10 seconds then try to recover from the boot using the ruu.
[...]
It also re-locked my phone.
After that, now that im stock, i tried to flash the 4.27 ruu. still 132.
So i tried to run the ota's and they worked.
Ive always relocked my htcs before running an ruu. If not then they never seem to work. I dont mind it because it takes about 10 seconds. and i already hae the token. I actually remembered the majority of the commands.
Maybe its causing another problem that i dont know about.
I did see the oem unlock in developer options if that is what you are talking about.
Click to expand...
Click to collapse
The power button isn't disabled. As said in my last post, you need to press the power button and the volume down button for 30 seconds. It's always been like that on the M9 since HTC already changed that on the M7 or M8 (can't tell you which one exactly it was).
Relocking was only needed on HTC phones that are older than the M9. HTC changed that with the M9. And as said in my last post, re-locking the M9 if you don't have a RUU at hand that you already used successfully is more than dangerous due to Google's FRP. You might end with a non-booting non-unlockable phone.
In addition, a relocked dootloader doesn't change the fact, that your phone is missing the needed encryption keys. That's why the 4.x RUU still failed.
However, it's nice to hear that you could solve your problems now. ?
Sent from my HTC One M9 using XDA Labs
Ah, I made a mistake while writing my posts. It's power and volume up. Not power and volume down. :silly: