Htc m9 soft bricked - One (M9) Q&A, Help & Troubleshooting

Hi everyone i hope I put this in the right area I'm new to forums and if not I'm sorry and could the admin please put me in the right place so I known for next time we'll here's my problem I have an AT&T m9 bootloader locked rooted and s-off with twrp recovery 2.8.6.0 well I tryed flashing the viperone rom on it with the bootloader locked I assumed sence i rooted it the bootloader was unlocked well it was not and so its now soft bricked it I can still get in to recovery but it hangs on the logo screen if I try to boot it up and I've tryed the ruu for it that another post told me to use but every time I try I get error code 150 unknown error and when I go to download mode it says at the bottom file /mnt/media_rw/ext_sd/opjaimg.zip file not found and the memory card I have is 64 gigs if that makes a difference if any one can help me that would be much appreciated and thanks for any help anyone can give
me

Unlock the bootloader via htcdev and flash viperone via twrp

htc m9
degerli43 said:
Unlock the bootloader via htcdev and flash viperone via twrp
Click to expand...
Click to collapse
hi iv tried what you said but i dont get that long list like im suppose to iget this
Microsoft Windows [Version 10.0.10586]
(c) 2015 Microsoft Corporation. All rights reserved.
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot oem get_identifier_token
...
(bootloader) [KillSwitch] : /dev/block/bootdevice/by-name/frp
(bootloader) [KillSwitch] Last Byte is 0X00, disable unlock
(bootloader) [KillSwitch] oem unlock Turn Off!
OKAY [ 0.012s]
finished. total time: 0.014s
C:\Program Files (x86)\Minimal ADB and Fastboot>
and when im in the bootloader i dont have a fastboot option do i not have fastboot poperly installed mabe

OEM unlocking should be ticked in Settings>developer options

side_flip15 said:
OEM unlocking should be ticked in Settings>developer options
Click to expand...
Click to collapse
It should all ready be off because the guy I paid to get the frp off checked oem unlocking to be able to get the s-off and I can't get to settings anyway cause it's soft bricked

Well based on the fastboot command output it seems like its not.
Please run fastboot getvar all and post the output here. remove the SN and IMEI

side_flip15 said:
Well based on the fastboot command output it seems like its not.
Please run fastboot getvar all and post the output here. remove the SN and IMEI
Click to expand...
Click to collapse
Microsoft Windows [Version 10.0.10586]
(c) 2015 Microsoft Corporation. All rights reserved.
C:\Users\Owner>fastboot getvar all
(bootloader) kernel: lk
(bootloader) product: htc_himaulatt
(bootloader) version: 1.0
(bootloader) imei:
(bootloader) version-main: 2.11.502.18
(bootloader) boot-mode: download
(bootloader) version-baseband: 01.01_U11440601_72.02.50602A_F
(bootloader) version-bootloader: 1.0.0.0000
(bootloader) mid: 0PJA11000
(bootloader) cid: 11111111
all:
finished. total time: 0.046s
i all so made sure fastboot was properly installed

Looks like you have a dev edition.
Two options for you...
1. Since you are s-off already you can try to unlock bootloader without htcdev. check this link for instructions. After unlock you can flash latest TWRP here. You're still in LP firmware so latest Viper ROm will not work for you. You will need to flash MM dev edition firmware, dl here.. After flashing you can install the latest Viper Rom via TWRP.
2. You can find the MM RUU or ROm.zip here. Run RUU or flash Rom.zip. This will already upgrade your M9 to MM.
good luck!

side_flip15 said:
Looks like you have a dev edition.
Two options for you...
1. Since you are s-off already you can try to unlock bootloader without htcdev. check this link for instructions. After unlock you can flash latest TWRP here. You're still in LP firmware so latest Viper ROm will not work for you. You will need to flash MM dev edition firmware, dl here.. After flashing you can install the latest Viper Rom via TWRP.
2. You can find the MM RUU or ROm.zip here. Run RUU or flash Rom.zip. This will already upgrade your M9 to MM.
good luck!
Click to expand...
Click to collapse
Now it's saying that adb server is out of dare then says killing all I did was Uninstall adb and reinstall it yesterday

Related

Soft Bricked (Locked / S-Off / Recovery broken?)

Hey guys!
I really hope anyone can help me out with this.
So, today I thought "Why not upgrading to 5.1 and unbranding it?". I followed a tutorial on a german android forum to unbrand it.
But I was unlocked and rooted so I had to return the changes in order to update it. I changed the CID to HTC__102, made it S-ON again and even locked it, then tried flashing a non branded european RUU via my microSD card, which somehow failed and I ended up having a bootloop. So I upgraded my firmware aswell to 2.10.401.1 but now the recovery is not even working i only get a red triangle, which might be a common problem with 5.1 on our M9, as I read later on.
Download mode, fastboot etc is working fine
edit: stock recovery is working as well
Can anybody help me get my M9 going again?
I thought about try another flash with a unlocked ROM via microSD card but I'm not sure which one as the one I mentioned failed.
Here are some more details about my current situation:
(bootloader) kernel: lk
(bootloader) product: htc_himauhl
(bootloader) version: 1.0
(bootloader) imei: XXXXX
(bootloader) version-main: 2.10.401.1
(bootloader) boot-mode: download
(bootloader) version-baseband: 01.04_U11440601_71.02.50709G_F
(bootloader) version-bootloader: 1.0.0.0000
(bootloader) mid: 0PJA10000
(bootloader) cid: HTC__102
Click to expand...
Click to collapse
edit: In another thread I read how to boot into the stock recovery and it's working. But still not booting
easy...soff again unlock bootloader, then download dev 2.8 zip rom, place it on sdcard and enter download mode, press volume up to start flash and you will have a brand new developer edition 2.8 (you will loose all info) you must have mid 0JPA11000 cid BS_US001., read a topic on this on xda how to change att to developer...
LLegion said:
easy...soff again unlock bootloader, then download dev 2.8 zip rom, place it on sdcard and enter download mode, press volume up to start flash and you will have a brand new developer edition 2.8 (you will loose all info) you must have mid 0JPA11000 cid BS_US001., read a topic on this on xda how to change att to developer...
Click to expand...
Click to collapse
Thanks, but how do i set it to S-Off again? I've used Sunshine's S-Off app before. But I'm not able to boot anymore.
At first never post your IMEI number online.
If you are not S-OFFed any more you cannot flash anything to recovery partition as long as you are not at least htc_dev unlocked.
The only thing that could help you now is to flash a custom recovery in boot partition and then to try to fix the recovery partition from it.
In order to do this you should unlock your bootloader again by using Unlock_code.bin
Code:
fastboot flash unlocktoken Unlock_code.bin
or if it has "relocked" status you could possibly use the command
Code:
fastboot oem unlock
then you should reboot in download mode again
Code:
fastboot oem rebootRUU
and flash the boot partition with a custom recovery
Code:
fastboot flash boot recovery.img
Now logically you should be able to boot into recovery (probably from bootloader) or by using the command
Code:
fastboot reboot recovery
If for some reason you cannot flash a custom recovery on boot partition you could try to extract the system.img from (probably any German RUU [HTC-GER] as long as you have HTC__102 cid number) and flash it with fastboot command
Code:
fastboot flash system system.img
By this way you could probably fix your breaked system partition
You should also erase the /cache and /data partitions so you could avoid the bootloop (even without to flash an original system.img)
Gatosbil said:
At first never post your IMEI number online.
Click to expand...
Click to collapse
Thanks. I've corrected it.
Gatosbil said:
In order to do this you should unlock your bootloader again by using Unlock_code.bin
Code:
fastboot flash unlocktoken Unlock_code.bin
Click to expand...
Click to collapse
I can't generate a new one because OEM unlock is turned off :\
Same goes with reflashing the previous Unlock_code.bin
> htc_fastboot flash unlocktoken Unlock_code.bin
sending 'unlocktoken' (0 KB)... OKAY
writing 'unlocktoken'... (bootloader) flash unlocktoken
(bootloader) [KillSwitch] : /dev/block/bootdevice/by-name/frp
(bootloader) [KillSwitch] Last Byte is 0X00, disable unlock
(bootloader) [KillSwitch] oem unlock Turn Off!
OKAY
Execution time is 20(ms)
Click to expand...
Click to collapse
Gatosbil said:
or if it has "relocked" status you could possibly use the command
Code:
fastboot oem unlock
Click to expand...
Click to collapse
Indeed, it is "relocked". But when I'm using the command I'll get "[ERR] Command error !!!"
Any suggestions for that? I'll try the other steps once I solved this.
Edit: I can't use ADB because I'm using the stock recovery atm.
Also there is no RUU for 2.10.401.1 yet so I guess I have to sent it in?
Btw: I'm already hating the new 5.1 oem lock feature.
This was your mistake:
Army92 said:
made it S-ON again
Click to expand...
Click to collapse
I don't care what anyone tells you, don't ever, ever go back to s-on once you are s-off. It's totally unnecessary and a potential risk, as you've discovered. By doing it, you've locked your phone into a bad configuration. You can't unlock unless you can boot to the OS and check "allow OEM unlocking." You can't flash a recovery because you're locked. You can't run a RUU because none exists for your CID. You're going to have to return it and hope HTC will fix it.
iElvis said:
This was your mistake:
I don't care what anyone tells you, don't ever, ever go back to s-on once you are s-off. It's totally unnecessary and a potential risk, as you've discovered. By doing it, you've locked your phone into a bad configuration. You can't unlock unless you can boot to the OS and check "allow OEM unlocking." You can't flash a recovery because you're locked. You can't run a RUU because none exists for your CID. You're going to have to return it and hope HTC will fix it.
Click to expand...
Click to collapse
That's what I thought. Thanks, I'll contact HTC and see if they can fix it.
Edit: I'm sending it to HTC today. Just a warning to all users out there: Do not lock your bootloader and uncheck "Enable OEM unlocking" because you are not able to do anything about it when your devices isn't working properly!
Army92 said:
Just a warning to all users out there: Do not lock your bootloader and uncheck "Enable OEM unlocking" because you are not able to do anything about it when your devices isn't working properly!
Click to expand...
Click to collapse
If it's any consolation, you're far from the first person to get tripped up by this new feature. Lots of Nexus 6s got bricked when it first rolled out because of situations just like yours.
iElvis said:
If it's any consolation, you're far from the first person to get tripped up by this new feature. Lots of Nexus 6s got bricked when it first rolled out because of situations just like yours.
Click to expand...
Click to collapse
Yeah I've read that too. Thanks for your condolence. Will report again when I get my M9 back in 2 weeks (I hope).
Update: So today I got my lovely One M9 back it lasted 10 days until I got it back in my hands.
They changed the mainboard and haven't charged anything. My phone status went back to official, S-Off and locked bootloader.
Army92 said:
Update: So today I got my lovely One M9 back it lasted 10 days until I got it back in my hands.
They changed the mainboard and haven't charged anything. My phone status went back to official, S-Off and locked bootloader.
Click to expand...
Click to collapse
They sent you an s-off phone?
iElvis said:
They sent you an s-off phone?
Click to expand...
Click to collapse
Oh, sorry my bad. I meant S-On of course
soft breaked htc one m9 s-off please help
hy
rom: cm13 himaul
device:htc one m9 unlocked/developer edition
statue:s-off
(bootloader) kernel: lk
(bootloader) product: htc_himaulatt
(bootloader) version: 1.0
(bootloader) imei: xxxxxxxxxxxxx
(bootloader) version-main: 1.32.617.30
(bootloader) boot-mode: download
(bootloader) version-bootloader: 1.0.0.0000
(bootloader) mid: 0PJA11000
(bootloader) cid: BS_US001
ok i have rooted cm13 20160603 nighties by supersu 2.74 beta with xposed 85 arm 64
yesterday i was disabling my boot image when it restarted by itself and never boot in to system again so i went to my custom recovery twrp latest version to reflash the whole cm13 again it didnt work then i wiped the whole internal storage and reflashed the cm13 and it said fail cant flash cm thats when my battery died so i charged it after 3 hours i came back went to bootloader menu then clicked on custom recovery it didnt even start so i plugged it to usb used fastboot to flash custom frimware from here (used the no wipe zip)
http://forum.xda-developers.com/one-m9/development/firmware-t3068243
it flashed but custom frimware didnt fix it so i used the wipe zip version with viper one latest system image to flash it failed so now i am stock in bootloader (download mode works) without access of recovery and no system.img or recovery and i cant find a way to fix it
websites i visited just in case
http://forum.xda-developers.com/one-m9/general/stock-nand-backup-ota-update-collection-t3132698
http://forum.xda-developers.com/one-m9/development/firmware-t3068243
any help would be appreciated
:crying::crying::crying:

HELP PLS! Bootloader OS version and software number not the same

Hi All,
I'm not sure how I managed to do this but I think I bricked my phone
My bootloader was unlocked and the phone was rooted. I wanted to bring the phone back to stock in order to be able to install an OTA update.
I flashed the stock ROM and was able to install the OTA update.
After this I ran into a problem where the phone would boot and upgrade apps then right before finishing the boot it would reboot and start the process all over again. Looping everytime that the upgrade apps would finish.
Log story short I ended up restarting the process of going back to stock to try everything from scratch again. Things were not working so I foolishly relocked the bootloader thinking it wouldn't be an issue to unlock again with the unlock_code.bin file that I had used previously.
Now the phone will boot into the bootloader and into download mode but not into recovery.
Ive tried flashing the stock recovery and the TWRP recovery and even the recovery from the OTA update but none will flash as the bootloader is locked.
I tried to unlock the bootloader again but cannot and here is the reason why.
The bootloader thinks my OS is 5.1 but really the OS on the phone is 5.0.2
C:\Users\Dan\Desktop\HTC One\One M9>fastboot getvar all
(bootloader) kernel: lk
(bootloader) product: htc_himaulatt
(bootloader) version: 1.0
(bootloader) imei:
(bootloader) version-main: 2.11.666.2
(bootloader) boot-mode: RUU
(bootloader) version-baseband: 01.02_U11440601_77.04.50715G_2_F
(bootloader) version-bootloader: 1.0.0.0000
(bootloader) mid: 0PJA11000
(bootloader) cid: BM___001
all:
finished. total time: 0.033s
Software number on my phone is 1.32.666.30 but version-main is 2.11.666.2
Fastboot oem unlock does not work as the bootloader is looking for a flag that is set by selecting the developer option of unlock bootloader but that developer option only exists in android 5.1+
Being as the OS on my phone is 5.0.2 I don't have that option in my developer options.
When I boot into RUU with "fastboot oem rebootRUU" and I try to flash my stock rom I now get this.
C:\Users\Dan\Desktop\HTC One\One M9>htc_fastboot flash zip 0PJAIMG.zip
sending 'zip'... (94347 KB) OKAY
sending time = 5.298 secs
writing 'zip'... (bootloader) HOSD CL#579410
(bootloader) ERR [SD_UPDATE_ERR] Main version NOT ALLOWED
(bootloader) ERR [SD_UPDATE_ERR] sddownload failed: 19
(bootloader) ERR Update zip file failed.
(bootloader) ERR ZIP ERROR, exit read zip loop
(bootloader) ERR ZIP signature checking failed...
(bootloader) Update zip file OK
(bootloader) ERR ZIP ERROR CODE, 19
(bootloader) [email protected]
FAIL19: fail to flash via downloadzip
FAILED (remote: 19: fail to flash via downloadzip)
Execution time is 10(s)
I found a tool called misctool which can change the main version to whatever I choose - If I could change the main version back to 1.32.666.30 I'm assuming this would allow me to flash the stock ROM again and get me back up and running.
The problem is that misctool requires root and I cannot get root without unlocking the bootloader which I cannot unlock because the OS on my phone does not have the option to do so
I read about using nautilus within ubuntu to be able to push files into root areas of my phone and have tried to go this route but I cant get my phone to appear in ubuntu while its in download mode.
Sigh if only I could find a way to get root to be able to change the version-main I think my troubles would be a thing of the past
Can anyone shed any light on my dismal situation?
Your phone is bricked until there is a ruu for your cid/mid. You've made the same mistake as many people before you, which was relocking your bootloader before ticking the allow oem unlock option.
Sent from my HTC One M9 using Tapatalk
iElvis said:
Your phone is bricked until there is a ruu for your cid/mid. You've made the same mistake as many people before you, which was relocking your bootloader before ticking the allow oem unlock option.
Sent from my HTC One M9 using Tapatalk
Click to expand...
Click to collapse
How.. He didnt have the option to begin with. Like many others dont as 5.1 is the version with the unlock option. 5.0.1/.2 don't have the option so you cannot tick unlock, update and unlock the bl.
If you cannot see the logic, please explain your method.
I wish I stole my HTC M9. It's a pile of ****.
Thats the thing,
I was never able to boot into 5.1. As I mentioned in my OP the phone kept rebooting at finishing boot after optimizing the apps.
I figured flashing the stock ROM back on to the phone would let me start over again..
It wasn't until after I relocked the bootloader and started to get errors when trying to unlock it again that I read about the "Allow OEM Unlock" option within the developer options of the phone.
Now that the original ROM is back on the phone that option does not exist in my develop options as the OS version is 5.0.2
I'm wondering why flashing the stock ROM didn't put the stock bootloader version back on the phone at the same time.
All I know now is that the bootloader requires the "Allow OEM Unlock" option to be checked (as it seems to think my software number is 2.11.666.2) in order to let me unlock my bootloader which I cannot do as I the option does not exist in the developer options of 5.0.2.
If only I could gain root while in the adb shell. With that I could use misctool to set the software version back to 1.32.666.30 which I think would then allow me to re-flash my stock ROM, put the bootloader back to what it was, and allow me to unlock it again.
Who creates the RUUs? HTC? HTC and my carrier? Waiting for that to come around is a terrible outcome. I think I will have better luck waiting for a root shell exploit to come around.
Ahhhh what a crappy situation.
shivadow said:
I wish I stole my HTC M9. It's a pile of ****.
Click to expand...
Click to collapse
Mwahahahaha I'm starting to feel the same way!
Of course you could not have ticked the oem unlock option before starting the process. That wasn't what I meant.
The problem is that you upgraded to 5.1 via ota (that's why your version-main says 2.11), so now you have to tick it to unlock. It was locking after the ota but before getting your OS straightened out that was the mistake. Now you're stuck.
There seems to be a problem with the 2.11 update that causes this boot loop issue. I have not seen a fix since I don't believe HTC has released a RUU for 2.11. But, as you recognized in the OP, relocking in the middle of this was not the solution.
I was able to flash the firmware from the 2.11.666.2 OTA.
Now I can no longer boot into the 1.32.666.30 OS but I can boot into the stock recovery but there is not much I can do from there.
I've tried to sideload the OTA but of course it doesnt work because of the changes to the system partition from when I was rooted.
Ive tried to flash a twrp system.emmc.win from a stock backup of the 1.32.666.30 but it errors out with signature verification failed. Im assuming because its a backup of the 1.32.666.30 and not the 2.11.666.2?
Would it make sense that if I could find a system img of the Bell Mobility 2.11.666.2 I would be able to sideload it? Maybe that would fix the issues with the system partition and allow the OTA to complete s that I could then at least boot into the phone ?
Or am I looking at smashing this thing and going to buy another one?
Try to S-Off your phone. Though it probably won't work without root.
omar302 said:
Try to S-Off your phone. Though it probably won't work without root.
Click to expand...
Click to collapse
Thanks Omar. I don't think I can go for S-OFF as my bootloader is relocked and I can't re unlock it.
Root is gone too except for the mess that it made to the system partition. Which is why I cant sideload the OTA.
If only I could get rid of the OTA verification. It would install and I think my phone would let me boot into the os where I could finally choose the "Enable OEM Unlock" option in the developer options.
Right now im trying to find an OTA for Bell Mobility that updated the OS to 5.0.2 if I could find that I could flash that firmware which would probably put the bootloader back to 1.32.666.30.
That way I could unlock the bootloader through adb etc.
I seriously think Im screwed unless if I could find that firmware or find out a way to fool the OTA into believing nothing changed with the system partition so that it would complete the install sigh
You might try an earlier ruu.zip for your CID and see if you can load it from the sdcard in Download mode. This would downgrade you to something functional. You can downgrade firmware on the M9 even with s-on as long as the aboot has not changed. Not sure if this will work for you, but it's worth a shot.
If it works, get root and s-off, then just flash everything manually. I've seen too many people screw up their phones trying to revert to stock to get OTAs.
iElvis said:
You might try an earlier ruu.zip for your CID and see if you can load it from the sdcard in Download mode. This would downgrade you to something functional. You can downgrade firmware on the M9 even with s-on as long as the aboot has not changed.
Click to expand...
Click to collapse
Sadly that's not true. What I learned during the last weeks (from trying to help others like Amr Nasser or Denis Meissner) is that a downgrade with S-ON is only possible if the first and the second version number are the same before and after the downgrade. That means a downgrade from 1.32.xxx.15 to 1.32.xxx.8 is possible but from 1.40.xxx.8 to any 1.32 version is not. The same applies to downgrades from 2.xx versions.
Flippy498 said:
Sadly that's not true. What I learned during the last weeks (from trying to help others like Amr Nasser or Denis Meissner) is that a downgrade with S-ON is only possible if the first and the second version number are the same before and after the downgrade. That means a downgrade from 1.32.xxx.15 to 1.32.xxx.8 is possible but from 1.40.xxx.8 to any 1.32 version is not. The same applies to downgrades from 2.xx versions.
Click to expand...
Click to collapse
Probably because the aboot version has changed between those versions. At least that was how it was explained to me by someone more knowledgable a while back.
iElvis said:
Probably because the aboot version has changed between those versions. At least that was how it was explained to me by someone more knowledgable a while back.
Click to expand...
Click to collapse
According to my phone it's still version 1.0.0.0000. That's why I don't understand why a downgrade is impossible.
D:\Root>fastboot getvar all
(bootloader) kernel: lk
(bootloader) product: htc_himauhl
(bootloader) version: 1.0
(bootloader) imei:
(bootloader) version-main: 2.10.401.1
(bootloader) boot-mode: download
(bootloader) version-baseband: 01.04_U11440601_71.02.50709G_F
(bootloader) version-bootloader: 1.0.0.0000
(bootloader) mid: 0PJA10000
(bootloader) cid: HTC__102
all:
finished. total time: 0.016s
Edit: Don't get me wrong. I don't want to start an argument. I'm just trying to understand this phone.
Flippy498 said:
Edit: Don't get me wrong. I don't want to start an argument. I'm just trying to understand this phone.
Click to expand...
Click to collapse
No that's what I thought. Someone else insisted the aboot version was what mattered. But I haven't tried it myself so I'm just passing on what I was told.

HTC m9 in bootloop after re-locking the bootloader

Hi,
Well, as the title said i'm stuck in bootloop after re-locking the bootloader.
Here is the history of what happened:
Unlocked the bootloader
flashed TWERP recovery and rooted.
I saw I can't install OTA updates so I unrooted the phone and flashed back to stock recovery. Still couldn't install OTA updates.
Unlocked the bootloader again and restored system partition back to original "untouched" status (from this thread: http://forum.xda-developers.com/tmobile-one-m9/general/please-read-rooting-using-twrp-t3069022). Only to realize i'm not on t-mobile, but the phone worked anyway .
Flashed back to stock recovery but still couldn't install the updates (If I remember correctly I got a massage that my software was tampered).
I'm S-on so I thought before trying the sunshine app I'll relock the bootloader. So I did that and that's it.
Here's were I'm now:
software status: modified
RELOCKED
S-ON
I can access stock recovery and download mode.
ADB devices doesn't recognize the phone (all drivers are ok and up to date and I've tried different cables and usb ports)
On the other hand, fasboot devices does work and recognize my phone.
So I come to you with help after going though tons of pages, guides and what not. I'm at it for a week now and no luck.
Help me XDA-Kanobi, you're my only hope
Thanks
Yotam
unlock with fastboot
Sorry to bump but is there any way to unlock it with fastboot maybe since it's the only way I can connect?
any suggestion or idea will be helpful
Thanks
Yotam
yotamh said:
Sorry to bump but is there any way to unlock it with fastboot maybe since it's the only way I can connect?
any suggestion or idea will be helpful
Thanks
Yotam
Click to expand...
Click to collapse
What's your current firmware? Is the allow OEM unlock option (or how ever it was called in English) activated in the developer options (only important for firmware versions with a 2 or higher at the beginning)? If yes you can re-unlock with the unlock_token you got from HTCdev.
Flippy498 said:
What's your current firmware? Is the allow OEM unlock option (or how ever it was called in English) activated in the developer options (only important for firmware versions with a 2 or higher at the beginning)? If yes you can re-unlock with the unlock_token you got from HTCdev.
Click to expand...
Click to collapse
My current firmware is 5.0.something. To be honest I don't remember and can't check.
I've tired to re-unlock with the unlock_token you got from HTCdev but it didn't work. I've got the token with fastboot but only in download mode an then when I tried to unlock with the file they send you to the mail It gives an error that I can check later when I'm home.
Yotam
yotamh said:
My current firmware is 5.0.something. To be honest I don't remember and can't check.
I've tired to re-unlock with the unlock_token you got from HTCdev but it didn't work. I've got the token with fastboot but only in download mode an then when I tried to unlock with the file they send you to the mail It gives an error that I can check later when I'm home.
Yotam
Click to expand...
Click to collapse
It seems like you're talking about the android version not the firmware version since there is no 5.0.XXX.X firmware for the M9. For now it might be the best solution to wait until you're home.
yotamh said:
Hi,
Well, as the title said i'm stuck in bootloop after re-locking the bootloader.
Here is the history of what happened:
Unlocked the bootloader
flashed TWERP recovery and rooted.
I saw I can't install OTA updates so I unrooted the phone and flashed back to stock recovery. Still couldn't install OTA updates.
Unlocked the bootloader again and restored system partition back to original "untouched" status (from this thread: http://forum.xda-developers.com/tmobile-one-m9/general/please-read-rooting-using-twrp-t3069022). Only to realize i'm not on t-mobile, but the phone worked anyway .
Flashed back to stock recovery but still couldn't install the updates (If I remember correctly I got a massage that my software was tampered).
I'm S-on so I thought before trying the sunshine app I'll relock the bootloader. So I did that and that's it.
Here's were I'm now:
software status: modified
RELOCKED
S-ON
I can access stock recovery and download mode.
ADB devices doesn't recognize the phone (all drivers are ok and up to date and I've tried different cables and usb ports)
On the other hand, fasboot devices does work and recognize my phone.
So I come to you with help after going though tons of pages, guides and what not. I'm at it for a week now and no luck.
Help me XDA-Kanobi, you're my only hope
Thanks
Yotam
Click to expand...
Click to collapse
OK OK dont get frenetic...DO AS EXACTLY AS I SAY OK?.................boot into download MODE Only and follow SAKITECH video on how to root M9, then flash a custom rom or SD Zip-Ruu to allow phone to boot again. =D hope this helps!
LLegion said:
OK OK dont get frenetic...DO AS EXACTLY AS I SAY OK?.................boot into download MODE Only and follow SAKITECH video on how to root M9, then flash a custom rom or SD Zip-Ruu to allow phone to boot again. =D hope this helps!
Click to expand...
Click to collapse
the problem is I can't unlock the bootloader. ADB devices doesn't work
Flippy498 said:
What's your current firmware? Is the allow OEM unlock option (or how ever it was called in English) activated in the developer options (only important for firmware versions with a 2 or higher at the beginning)? If yes you can re-unlock with the unlock_token you got from HTCdev.
Click to expand...
Click to collapse
how can I check the firmware version from the bootloader?
(under os in download mode I see - 1.32.401.15. is that the firmware?
yotamh said:
how can I check the firmware version from the bootloader?
(under os in download mode I see - 1.32.401.15. is that the firmware?
Click to expand...
Click to collapse
Yes, that's correct. And with that firmware your problems can be solved without much hassle. Just download either the 1.32.401.15 or the 1.40.401.8 RUU which are both linked in my google sheet (link can be found in my signature). Follow the instructions and your phone should be usable again in no time. If you choose the 1.40.401.8 RUU there's one OTA less you need to install after you recovered your phone.
And a little advice for the future: If you want to install future OTAs then you don't need to relock your bootloader. If your phone isn't completely stock this will always result in a bootloop.
Flippy498 said:
Yes, that's correct. And with that firmware your problems can be solved without much hassle. Just download either the 1.32.401.15 or the 1.40.401.8 RUU which are both linked in the google sheet in my signature. Follow the instructions and your phone should be usable again in no time. If you choose the 1.40.401.8 RUU there's one OTA less you need to install after you recovered your phone.
And a little advice for the future: If you want to install future OTAs then you don't need to relock your bootloader. If your phone isn't completely stock this will always result in a bootloop.
Click to expand...
Click to collapse
Thanks a lot for the answer. Is it possible to flash the RUU if I'm S-ON??
yotamh said:
Thanks a lot for the answer. Is it possible to flash the RUU if I'm S-ON??
Click to expand...
Click to collapse
Of course. The only things you cannot do is downgrading or flashing RUUs that have a different SKU (=the three numbers behind the second dot in the firmware version). RUUs with the same version as your phone or higher versions are fine, though.
Flippy498 said:
Of course. The only things you cannot do is downgrading or flashing RUUs that have a different SKU (=the three numbers behind the second dot in the firmware version). RUUs with the same version as your phone or higher versions are fine, though.
Click to expand...
Click to collapse
HI
So i'm trying to flash the RUU and I'm getting this:
C:\Users\Yotam\Desktop\Phone files>fastboot flash zip M9_1.32.401.15_FullStock_rename_to_ROM.zip <----I've tried to change it to ROM.zip as well but I get the same error
target reported max download size of 800000000 bytes
sending 'zip' (111548 KB)...
OKAY [ 7.869s]
writing 'zip'...
(bootloader) HOSD CL#506785
(bootloader) GPT is up-to-dated. [17408]
(bootloader) Perform pre-update
(bootloader) ERR ZIP signature checking failed...
(bootloader) ERR [SD_UPDATE_ERR] sddownload failed: 8
(bootloader) ERR Update zip file failed.
(bootloader) Update zip file OK
(bootloader) ERR ZIP ERROR CODE, 8
(bootloader) [email protected]
FAILED (remote: 8: fail to flash via downloadzip)
finished. total time: 12.962s
The ZIP file is fine (i've downloaded it twice just to be sure), phone is with the sd card in it (I though it's worth mentioning), S-ON.
Not sure what else...what seems to be the issue here?
some more info
fastboot getvar all
(bootloader) kernel: lk
(bootloader) product: htc_himauhl
(bootloader) version: 1.0
(bootloader) imei:
(bootloader) version-main: 1.32.401.15
(bootloader) boot-mode: RUU
(bootloader) version-bootloader: 1.0.0.0000
(bootloader) mid: 0PJA10000
(bootloader) cid: HTC__016
all:
finished. total time: 0.014s
yotamh said:
HI
So i'm trying to flash the RUU and I'm getting this:
C:\Users\Yotam\Desktop\Phone files>fastboot flash zip M9_1.32.401.15_FullStock_rename_to_ROM.zip <----I've tried to change it to ROM.zip as well but I get the same error
target reported max download size of 800000000 bytes
sending 'zip' (111548 KB)...
OKAY [ 7.869s]
writing 'zip'...
(bootloader) HOSD CL#506785
(bootloader) GPT is up-to-dated. [17408]
(bootloader) Perform pre-update
(bootloader) ERR ZIP signature checking failed...
(bootloader) ERR [SD_UPDATE_ERR] sddownload failed: 8
(bootloader) ERR Update zip file failed.
(bootloader) Update zip file OK
(bootloader) ERR ZIP ERROR CODE, 8
(bootloader) [email protected]
FAILED (remote: 8: fail to flash via downloadzip)
finished. total time: 12.962s
The ZIP file is fine (i've downloaded it twice just to be sure), phone is with the sd card in it (I though it's worth mentioning), S-ON.
Not sure what else...what seems to be the issue here?
Click to expand...
Click to collapse
yotamh said:
some more info
fastboot getvar all
(bootloader) kernel: lk
(bootloader) product: htc_himauhl
(bootloader) version: 1.0
(bootloader) imei:
(bootloader) version-main: 1.32.401.15
(bootloader) boot-mode: RUU
(bootloader) version-bootloader: 1.0.0.0000
(bootloader) mid: 0PJA10000
(bootloader) cid: HTC__016
all:
finished. total time: 0.014s
Click to expand...
Click to collapse
For your own safety you should delete your IMEI as it can be used for phone scam by others.
Why are you trying to flash one of Sneakyghosts' firmware packs? They can only be used with S-OFF and do not contain a rom. I've already explained earlier that you can find the needed RUUs and instructions in the google sheet in my signature.
Flippy498 said:
For your own safety you should delete your IMEI as it can be used for phone scam by others.
Why are you trying to flash one of Sneakyghosts' firmware packs? They can only be used with S-OFF and do not contain a rom. I've already explained earlier that you can find the needed RUUs and instructions in the google sheet in my signature.
Click to expand...
Click to collapse
Hi thanks for the top about the IMEI I've changed it.
and sorry, I didn't understood the the original comment and got in to the a wrong line in the comment. I'll try again with the correct file (2gb will take some to download). Again, thank you for your answer and patient. It's nice to see people try to help. :good:
THANK YOU so much! everything is working and even updated! thanks!
it seems i have a strange issue after all.
my phone doesn't detect my htc headphones. It recognize other headphone and the HTC headphones works with other devices.
it looks like a software issue.
Flippy498 said:
For your own safety you should delete your IMEI as it can be used for phone scam by others.
Why are you trying to flash one of Sneakyghosts' firmware packs? They can only be used with S-OFF and do not contain a rom. [REMOVED BECAUSE I'M A NEWBIE]I've already explained earlier that you can find the needed RUUs and instructions in the google sheet in my signature[/URL].
Click to expand...
Click to collapse
Hi I know this is probably old but I was in this exact same predicament and I had "tried everything" and your instructions brought my phone back to life!! I am so grateful after almost a week of adb commands and zip files that got me nowhere! THANK YOU SO MUCH!!!:good:

hit a roadblock while trying to revert my 816 to stock. please help.

Hi guys.
I rooted my 816 using CWM and SuperSU months ago. Now, there's an OTA update to Android 6.0 which will hopefully render the usefulness of root obsolete, as I mostly need it for link2sd (they also cite better RAM management as a new feature, which should get rid of the horrible lag on Lollipop).
I know I have to go back to full stock, and I read a simple guide somewhere, and I thought, why don't I give it a crack. So, it said I should just "fastboot oem lock" the phone and flash the correct .zip RUU. After much trouble with connectivity and driver issues between my computer (adb server is out of date. killing...; device offline; errors etc.) I FINALLY (after hours of troubleshooting) managed to go into fastboot via USB and lock the bootloader. Great. But, when I tried to flash the .zip, it just says waiting for device, indefinitely. Tried to go into recovery via the power buttons on the phone, but it shows an error and simply refuses to. As a sidenote, root still works, but the phone displays this in fastboot: Relocked, Security Warning.
Basically, I'm afraid to proceed because I think I'm on the wrong track, and could end up f'ing up my device altogether. I'm from Croatia so I downloaded the 5.0.1 EU version .zip from here: (can't post link, just search htcdev downloads, it's the first one).
I hate opening new threads because I'm sure someone has already had the problems I'm having, but I just can't keep searching the web for hours on end trying to find a solution. Forgive me for this guys, and please help a poor noob in need if you can.
Could you please post your device info? (Make sure to delete serialno. and imei!)
To get your device info, you'll need to make sure all drivers are up-to-date.(HTC Sync, Java and ADB)
After installing,
- Navigate to ADB folder and click on any free space while holding the shift Key
- Choose 'Open command window here'
- Once cmd is started use this command
Code:
fastboot devices
and check if your device is listed, then type
Code:
fastboot getvar all
and copy/paste code here.
nukaru said:
Could you please post your device info? (Make sure to delete serialno. and imei!)
To get your device info, you'll need to make sure all drivers are up-to-date.(HTC Sync, Java and ADB)
After installing,
- Navigate to ADB folder and click on any free space while holding the shift Key
- Choose 'Open command window here'
- Once cmd is started use this command
Code:
fastboot devices
and check if your device is listed, then type
Code:
fastboot getvar all
and copy/paste code here.
Click to expand...
Click to collapse
Oh great, you're from Germany, so you have an EU 816 too. It's an a5ul just like yours. I'll send the full info text as soon as i install SDK tools completely.
I noticed that in your guide you first flash the stock ROM, and only then lock the bootloader. In the guide I found it said to first lock the bootloader, and then flash the stock ROM. So right now, I have a locked bootloader and CWM recovery I can't get into. Is this going to be a problem?
No, you first flash the stock recovery, then relock bootloader. And if your flashed recovery works you flash the RUU.
running fastboot devices does literally nothing, just sends me to the next line.
running adb devices, on the other hand, lists my device.
great, so I messed up there. do you know how I can fix it?
Are you able to boot into fastboot USB? Have you tried the fastboot getvar all comand?
If yes, first you need to flash the stock recovery and check if the flash was a success. If you can get into recovery without any errors, relock bootloader and place the RUU file on sd-card. Boot to bootloader again and the flashing should start on its own.
nukaru said:
Are you able to boot into fastboot USB? Have you tried the fastboot getvar all comand?
If yes, first you need to flash the stock recovery and check if the flash was a success. If you can get into recovery without any errors, relock bootloader and place the RUU file on sd-card. Boot to bootloader again and the flashing should start on its own.
Click to expand...
Click to collapse
I managed to get the getvar command to work: here's the info
C:\Program Files (x86)\Android\android-sdk\platform-tools>adb reboot bootloader
C:\Program Files (x86)\Android\android-sdk\platform-tools>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.101.111011.20.0123
(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: a5_ul
(bootloader) platform: hTCBmsm8226
(bootloader) modelid: 0P9C20000
(bootloader) cidnum: HTC__032
(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: 09813c97
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.054s
The files from my guide should work with your device.
so it doesn't matter that my bootloader is now locked? I can just follow your guide and it should work?
Have you flashed stock recovery BEFORE locking bootloader? You have to install stock recovery or the RUU won't flash. It's all in the guide.
No, i didn't. I locked the bootloader and then tried to flash the stock RUU. That's the problem.
I wish I'd seen your guide before I did anything. I assume trying to flash anything now won't work, and that I'll have to unlock the bootloader again?
edofot said:
No, i didn't. I locked the bootloader and then tried to flash the stock RUU. That's the problem.
I wish I'd seen your guide before I did anything. I assume trying to flash anything now won't work, and that I'll have to unlock the bootloader again?
Click to expand...
Click to collapse
Did you type this before flashing the RUU?
Code:
fastboot oem rebootRUU
Nope. I tried to flash the RUU with fastboot flash ... .zip but it just said: waiting for device; and nothing happened. So I'll try the rebootRUU command when I get home from classes.
You need to flash the stock recovery, otherwise you won't be able to flash any official RUU.
Unlock bootloader, flash stock recovery, relock bootloader and flash RUU.
The command won't work, since you have a custom recovery. You need to get rid of that first.
nukaru said:
You need to flash the stock recovery, otherwise you won't be able to flash any official RUU.
Unlock bootloader, flash stock recovery, relock bootloader and flash RUU.
The command won't work, since you have a custom recovery. You need to get rid of that first.
Click to expand...
Click to collapse
I unlocked the bootloader, and did everything your guide said. Everything worked perfectly.
I just have a problem right now flashing the 0P9CIMG.zip. I can't flash it over the computer (it says the data length is too large or something similar), and I can't move it to sd-card on my phone. I tried moving other files and other .zip files, and that works. I tried redownloading from mega.nz, nothing. I'm thinking the .zip gets corrupted when downloading. Can you maybe re-upload it or send it to me through a different medium?
edofot said:
I unlocked the bootloader, and did everything your guide said. Everything worked perfectly.
I just have a problem right now flashing the 0P9CIMG.zip. I can't flash it over the computer (it says the data length is too large or something similar), and I can't move it to sd-card on my phone. I tried moving other files and other .zip files, and that works. I tried redownloading from mega.nz, nothing. I'm thinking the .zip gets corrupted when downloading. Can you maybe re-upload it or send it to me through a different medium?
Click to expand...
Click to collapse
Use this HTC mini-SDK
Gibz97 said:
Use this HTC mini-SDK
Click to expand...
Click to collapse
Tried it.
Stumped by this:
Code:
C:\Users\Korisnik\Desktop\HTC mini SDK>fastboot flash zip 0P9CIMG.zip
sending 'zip'... (51060 KB) OKAY
sending time = 2.709 secs
writing 'zip'... (bootloader) adopting the signature contained in this image...
(bootloader) signature checking...
FAILnot allowed
FAILED (remote: not allowed)
Execution time is 7(s)
edofot said:
Tried it.
Stumped by this:
Code:
C:\Users\Korisnik\Desktop\HTC mini SDK>fastboot flash zip 0P9CIMG.zip
sending 'zip'... (51060 KB) OKAY
sending time = 2.709 secs
writing 'zip'... (bootloader) adopting the signature contained in this image...
(bootloader) signature checking...
FAILnot allowed
FAILED (remote: not allowed)
Execution time is 7(s)
Click to expand...
Click to collapse
First type this. It will reboot phone into a black screen with a silver HTC logo:
Code:
fastboot oem rebootRUU
then type:
Code:
fastboot erase cache
then type:
Code:
fastboot flash zip 0P9CIMG.zip
Sorry, I was looking for an sd-card adapter, I wasn't here.
Update: Moved the 09PCIMG.zip to the sd-card successfully this time and am flashing the img now from sd-card! Seems to be going well so far.
Success
Finally! Did it, works like a charm.
I'm still amazed by how fast the phone really is when it's stock.
Viele Dank, @nukaru, du wärst eine sehr grosse hilfe. Wenn du nach Kroatien kommst, melde mich an, du hast ein Bier und/oder Kaffe von mich (at least I tried, even without google translate)
Thank you too @Gibz97, really appreciate the effort.
If anyone reading this has the same questions I had, just follow nukaru's guide, it has all you need to know. If you have an A5_UL, it's gonna work.

Please, Please, Please! Help...

Okay so I wanted to update the firmware of my device and since I'm S-On had to wait for signed ones, so in order to do so I need to re-lock the bootloader, which I did, but since I did it won't boot into anything at all... Recovery (TWRP was installed, rookie mistake I know), I attempted several times to unlock the bootloader again and every time it says "successful" but when rebooted the red dialog in the boot loader STILL says "Re-Locked"...
GETVAR info is here
F:\ADB\Fastboot>fastboot getvar all
(bootloader) kernel: lk
(bootloader) product: htc_himauhl
(bootloader) version: 1.0
(bootloader) imei: ****************
(bootloader) version-main: 2.10.161.7
(bootloader) boot-mode: download
(bootloader) version-baseband: 01.01_U11440601_86.09.50723G_F
(bootloader) version-bootloader: 1.0.0.0000
(bootloader) mid: 0PJA10000
(bootloader) cid: VODAP001
all:
finished. total time: 0.021s
Click to expand...
Click to collapse
And the info on my bootloader says this exactly...
HTC Download Mode
*** RELOCKED ***
htc_himauh1 PVT S-ON
LK-1.0.0.000
RADIO-01.01_U11440601_86.09.50723G_f
OpenDSP-v29.2.6-00492-M8994_0702
OS-2.10.161.7
Jul 30 2015,21:55:16(584440)
Click to expand...
Click to collapse
I'm at my wits end, I'm looking for an RUU.zip or .EXE file I can use to actually flash back to stock so I don't make such a stupid mistake again but for the life of me I can't find one (if indeed that's that only way I can do it?), flashing recovery won't work, flashing firmware packages won't work due to it being a locked bootloader that will not unlock for some reason.
Any help that anyone can provide is much apreciated..
MrHappyman said:
Okay so I wanted to update the firmware of my device and since I'm S-On had to wait for signed ones, so in order to do so I need to re-lock the bootloader, which I did, but since I did it won't boot into anything at all... Recovery (TWRP was installed, rookie mistake I know), I attempted several times to unlock the bootloader again and every time it says "successful" but when rebooted the red dialog in the boot loader STILL says "Re-Locked"...
GETVAR info is here
And the info on my bootloader says this exactly...
I'm at my wits end, I'm looking for an RUU.zip or .EXE file I can use to actually flash back to stock so I don't make such a stupid mistake again but for the life of me I can't find one (if indeed that's that only way I can do it?), flashing recovery won't work, flashing firmware packages won't work due to it being a locked bootloader that will not unlock for some reason.
Any help that anyone can provide is much apreciated..
Click to expand...
Click to collapse
What command do you use to unlock again?
Have you tried flashing the unlocktoken again in Download mode?
fastboot flash unlocktoken unlock_code.bin
What's the exact output after executing the above command?

Categories

Resources