Like the title says I'm soft bricked and no ruu will work beacuse my boot loader is unlocked and "fastboot oem lock" doesn't work. I'm S-On and I have access to the bootloader, download mode, and twrp, but twrp wont mount any partitions and shows internal storage as 0mb. P.S. this is a Tmobile HTC One M9. Please anyone I need help and I'm leaving for a trip tomorrow. Thanks!
Heres what i get from getvar all
C:\Users\Noah\Desktop\Minimal ADB and Fastboot>htc_fastboot getvar all
(bootloader) version:0.5
(bootloader) variant:MTP eMMC
(bootloader) secure:yes
(bootloader) version-baseband:
(bootloader) version-bootloader:
(bootloader) max-download-size: 0x20000000
(bootloader) partition-type:cache:ext4
(bootloader) partition-size:cache: 0x14000000
(bootloader) partition-type:userdata:ext4
(bootloader) partition-size:userdata: 0x5e0000000
(bootloader) partition-type:system:ext4
(bootloader) partition-size:system: 0x118000000
(bootloader) serialno:REDACTED
all:
Execution time is 135(ms)
(bootloader) kernel: lk
(bootloader) product: htc_himaul
(bootloader) version: 1.0
(bootloader) imei: REDACTED
(bootloader) version-main: 3.39.531.7
(bootloader) boot-mode: download
(bootloader) version-baseband: 01.01_U11440801_97.04.60111G_F
(bootloader) version-bootloader: 1.0.0.0000
(bootloader) mid: 0PJA12000
(bootloader) cid: T-MOB010
all:
finished. total time: 0.067s
You tried sideloading a rom via TWRP?
Sent from my HTC 10 using XDA Labs
squ89r97 said:
You tried sideloading a rom via TWRP?
Sent from my HTC 10 using XDA Labs
Click to expand...
Click to collapse
Ill try that and get back to you. one minute.
Fails everytime I try to sideload this is what I get.
C:\Users\Noah\Desktop\Minimal ADB and Fastboot>adb sideload stock-deodex.zip
loading: 'stock-deodex.zip'
* cannot read 'stock-deodex.zip' *
C:\Users\Noah\Desktop\Minimal ADB and Fastboot>adb sideload viperone.zip
loading: 'viperone.zip'
* cannot read 'viperone.zip' *
C:\Users\Noah\Desktop\Minimal ADB and Fastboot>adb sideload firmware.zip
loading: 'firmware.zip'
* cannot read 'firmware.zip' *
Try renaming the file in windows without the .zip sounds random I know, but I experienced this a long long time ago. So if you have a file called firmware.zip rename it firmware. But still use firmware.zip in your adb command.
Sent from my HTC 10 using XDA Labs
squ89r97 said:
Try renaming the file in windows without the .zip sounds random I know, but I experienced this a long long time ago. So if you have a file called firmware.zip rename it firmware. But still use firmware.zip in your adb command.
Sent from my HTC 10 using XDA Labs
Click to expand...
Click to collapse
ok Ill try that.
I renamed the file. I also tried renaming the file in the command. It fails the same way as before.
C:\Users\Noah\Desktop\Minimal ADB and Fastboot>adb sideload stock-deodex.zip
loading: 'stock-deodex.zip'
* cannot read 'stock-deodex.zip' *
C:\Users\Noah\Desktop\Minimal ADB and Fastboot>adb sideload stock-deodex
loading: 'stock-deodex'
* cannot read 'stock-deodex' *
narms72 said:
I renamed the file. I also tried renaming the file in the command. It fails the same way as before.
C:\Users\Noah\Desktop\Minimal ADB and Fastboot>adb sideload stock-deodex.zip
loading: 'stock-deodex.zip'
* cannot read 'stock-deodex.zip' *
C:\Users\Noah\Desktop\Minimal ADB and Fastboot>adb sideload stock-deodex
loading: 'stock-deodex'
* cannot read 'stock-deodex' *
Click to expand...
Click to collapse
Are you running cmd with administration rights? You can also type adb sideload command, then drag and drop your firmware into the cmd window.
Not sure where your firmware is saved, but it should be in the same folder as your adb, in your case. C:\Users\Noah\Desktop\Minimal ADB and Fastboot
Sent from my HTC 10 using XDA Labs
squ89r97 said:
Are you running cmd with administration rights? You can also type adb sideload command, then drag and drop your firmware into the cmd window.
Not sure where your firmware is saved, but it should be in the same folder as your adb, in your case. C:\Users\Noah\Desktop\Minimal ADB and Fastboot
Sent from my HTC 10 using XDA Labs
Click to expand...
Click to collapse
Unfortunately I get the exact same response.
I think the reason ruus fail is because my bootloader is unlocked, but whenever I try fastboot oem lock it doesnt work.
Rather than troubleshoot what you're doing, your best bet is to access Flippy498’s spreadsheet and read through his instructions in the RUU section. He's got a simple walkthrough that should set you on the right path.
computerslayer said:
Rather than troubleshoot what you're doing, your best bet is to access Flippy498’s spreadsheet and read through his instructions in the RUU section. He's got a simple walkthrough that should set you on the right path.
Click to expand...
Click to collapse
Ive read it. My bootloader wont lock though so ruus fail.
narms72 said:
Ive read it. My bootloader wont lock though so ruus fail.
Click to expand...
Click to collapse
I'm certain bootloader status doesn't matter to RUUs. What method of applying the RUU have you attempted (fastboot, sd card or executable)?
Is your phone a US T-Mobile variant? Besides the RUU in zip form, there is a Windows executable RUU (you'll need to install HTC Sync Manager first) available.
Edit: Well I was certain....ly wrong! Thank you Flippy498 for the correction (see post below)
computerslayer said:
I'm certain bootloader status doesn't matter to RUUs.
Click to expand...
Click to collapse
It does matter if you use fastboot or an *.exe (which actually does nothing more than using fastboot for you ). Both require a locked or relocked bootloader if you're S-ON. On the other hand for S-OFF users or if you use the SD card method the bootloader status doesn't matter.
Sent from my HTC One M9 using XDA Labs
Flippy498 said:
It does matter if you use fastboot or an *.exe (which actually does nothing more than using fastboot for you ). Both require a locked or relocked bootloader if you're S-ON. On the other hand for S-OFF users or if you use the SD card method the bootloader status doesn't matter.
Sent from my HTC One M9 using XDA Labs
Click to expand...
Click to collapse
I have the developer edition of the phone (still S-ON) and the RUU executable install even though it has an unlocked bootloader - I concluded that RUUs ignored bootloader status. Thank you for the correction.
The developer edition is (as far as I know) an exception due to its factory unlocked bootloader.
Sent from my HTC One S using XDA Labs
Flippy498 said:
The developer edition is (as far as I know) an exception due to its factory unlocked bootloader.
Click to expand...
Click to collapse
I'm guessing that's the reason the bootloader cannot be locked in this instance? Another bit of knowledge in the memory banks.
Sent from my HTC 10 using XDA Labs
As far as I know the bootloader can always be relocked. That's the reason for all the issues people have if they don't enable oem unlock and relock although their system is not completely stock (e.g. TWRP is still installed). The phone's security checks will prevent the phone from booting because it notices that the system is manipulated. If you don't have a compatible RUU in that situation or if your phone isn't S-OFF you're unable to solve the problem on your own. The only solutions are a java card/xtc clip or llabtoofers RUU service.
However you can't re-S-ON always due to some other security checks.
It might be helpful if the OP could post the error that appears when he tries to relock the bootloader.
Sent from my HTC One M9 using XDA Labs
Flippy498 said:
As far as I know the bootloader can always be relocked. That's the reason for all the issues people have if they don't enable oem unlock and relock although their system is not completely stock (e.g. TWRP is still installed). The phone's security checks will prevent the phone from booting because it notices that the system is manipulated. If you don't have a compatible RUU in that situation or if your phone isn't S-OFF you're unable to solve the problem on your own. The only solutions are a java card/xtc clip or llabtoofers RUU service.
However you can't re-S-ON always due to some other security checks.
It might be helpful if the OP could post the error that appears when he tries to relock the bootloader.
Click to expand...
Click to collapse
@Flippy498 the font of knowledge, thanks for all you expertise.
I know this sounds like sarcasm, but it's truly not.
Sent from my HTC 10 using XDA Labs
Related
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.
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
After a long wait I finally got my ota update to Nougat.
But there is another problem, I cant finish the update because my phone showed that error.
I'm on stock M9 in bootloader it says software status official, locked, and s-on. No root, as I have checked it using root checker. Recovery is there.
I never modified my phone. And its fine back when I updated from lollipop to mm via ota, there is no problem.
And as far as I know, my phone is on correct mid and cid, SKU 708, mid 0PJA10000 exactly the same with mid engraved on my phone, and cid HTC__044
But when I update mm to nougat, this variant system version error shows up
I have tried to flash RUU of my current firmware, but still nothing.
Please help me, where did I do wrong? or how can I solve this problem?
Bumping this because I got the same thing too.
My device is not even rooted!
Did you guys flash a RUU for your current firmware and try to download the OTA, again?
Flippy498 said:
Did you guys flash a RUU for your current firmware and try to download the OTA, again?
Click to expand...
Click to collapse
I did, but the problem stays there.
Flippy498 said:
Did you guys flash a RUU for your current firmware and try to download the OTA, again?
Click to expand...
Click to collapse
I dont know how to flash the RUU.
But anyway, is there a way to check whether i can flash the OTA on my own?
vglaksana said:
I did, but the problem stays there.
Click to expand...
Click to collapse
Can you please copy and paste the fastboot getvar all output here (without your IMEI!)? It might help us to help you.
-marco- said:
I dont know how to flash the RUU.
Click to expand...
Click to collapse
Well, there is a thread pinned above all the other threads in this section that is even called "ReadMe" and people still tend to completely ignore it...
-marco- said:
But anyway, is there a way to check whether i can flash the OTA on my own?
Click to expand...
Click to collapse
If you can't flash an OTA via the software update function then you can't flash it via fastboot, either. Your phone doesn't pass the security checks that google implemented with android 5 so the method you use for flashing the OTA doesn't matter.
Flash a RUU and re-try to install the OTA. If that still doesn't matter then please copy and paste your fastboot getvar all output here (without your IMEI!), as well.
Flippy498 said:
Can you please copy and paste the fastboot getvar all output here (without your IMEI!)? It might help us to help you.
Click to expand...
Click to collapse
Here it is
C:\Users\Vito G. Laksana\Desktop\New folder>fastboot getvar all
(bootloader) kernel: lk
(bootloader) product: htc_himauhl
(bootloader) version: 1.0
(bootloader) imei:
(bootloader) version-main: 3.42.708.3
(bootloader) boot-mode: download
(bootloader) version-baseband: 01.01_U114,10801_97.64.60111G_F
(bootloader) version-bootloader: 1.0.0.0000
(bootloader) mid: 0PJA10000
(bootloader) cid: HTC 044
all: inished. total time: 0.016s
Above is getvar all from before I flashed my current RUU. I believe it wouldn't change anything, as I can't get fastboot getvar all working now.
vglaksana said:
(bootloader) cid: HTC 044
Click to expand...
Click to collapse
If that is an exact copy of the output then it's no miracle that you can't install the OTA. That CID doesn't exist. It needs to be HTC__044 (8 letters, numbers or symbols in total and no spaces). You need S-OFF for being able to correct your CID.
Sent from my HTC One M9 using XDA Labs
Flippy498 said:
If that is an exact copy of the output then it's no miracle that you can't install the OTA. That CID doesn't exist. It needs to be HTC__044 (8 letters, numbers or symbols in total and no spaces). You need S-OFF for being able to correct your CID.
Sent from my HTC One M9 using XDA Labs
Click to expand...
Click to collapse
Ah my bad. The correct CID is HTC__044, as I mentioned in the thread first post.
I just using image to text converter because I have screencap of the output and didn't see that straight away.
Ah ok. And I already hoped that we found the cause of the problem... There have been some threads about devices that got bought in the US, S-OFFed and reflashed to non-US versions for selling them in other countries, in the past (around the time when firmware 2.x was the latest one). In most cases the sellers didn't convert the phones correctly and the buyers faced similar errors to your one when they tried to install an OTA.
Unfortunately there's nothing strange I can find in that output, then.
Sent from my HTC One M9 using XDA Labs
Flippy498 said:
Ah ok. And I already hoped that we found the cause of the problem... There have been some threads about devices that got bought in the US, S-OFFed and reflashed to non-US versions for selling them in other countries, in the past (around the time when firmware 2.x was the latest one). In most cases the sellers didn't convert the phones correctly and the buyers faced similar errors to your one when they tried to install an OTA.
Unfortunately there's nothing strange I can find in that output, then.
Sent from my HTC One M9 using XDA Labs
Click to expand...
Click to collapse
Thanks for helping me figuring out the problem.
If that is the problem, then why I have successfully update from lollipop to mm?
Yes i did buy it second hand, he said that the phone is from Singapore, and from the getvar output it is make sense that my phone came from Singapore.
Soo...I believe my only option is to S-OFF and convert to other version to get the update, is that correct?
I just re-read your opening post. Looks like I missed the part with the engraving. The US variant has a different engraving than the one you mentioned. So my assumption is probably wrong.
Since I have no clue what might cause your problem I actually don't see any other solution than getting S-OFF and converting the phone.
If there was a publicly available 4.x RUU for your SKU you could have asked Sneakyghost whether he creates a firmware package for you. By flashing that (S-OFF needed) you would have been able to use the 4.x RUU although you never installed the corresponding OTA. This way you could have kept your SKU. However, I haven't seen a public download link for such a RUU, yet. Therefore, you'll need to convert to a different SKU if you want the latest firmware.
Since you're still on firmware 3.x you need to flash one of Sneakyghost's 4.x packages before you can flash a 4.x RUU of the SKU that you want to convert to. Or you use a 3.x RUU for converting and try to install the OTA of the new SKU, afterwards. (The latter will probably take longer in total.)
Alternatively, you can wait some more days and see if some else has a better idea.
Sent from my HTC One M9 using XDA Labs
Flippy498 said:
Can you please copy and paste the fastboot getvar all output here (without your IMEI!)? It might help us to help you.
Click to expand...
Click to collapse
I rebooted into bootloader to get the getvar but it doesnt work.
adb lists no devices.
Also, see the enclosed pic. that's as far as i managed to get.
Adb won't work if the device isn't booted to system or recovery mode.
And since the fastboot mode doesn't exist anymore on the M9 and all newer HTC phones you need to boot to download mode.
Sent from my HTC One M9 using XDA Labs
Flippy498 said:
Adb won't work if the device isn't booted to system or recovery mode.
And since the fastboot mode doesn't exist anymore on the M9 and all newer HTC phones you need to boot to download mode.
Sent from my HTC One M9 using XDA Labs
Click to expand...
Click to collapse
booted to system: adb sees device but says it's offline
booted to dl mode: adb can't see the device.
anyway, i took picture of what dl mode looks like. Attached.
Yeah, that's how it's supposed to be. ADB can only be used if the phone is booted to the system or the recovery mode. You can't use ADB commands while it's booted to the bootloader or the download mode. You need to use fastboot commands in these modes.
Sent from my HTC One M9 using XDA Labs
Flippy498 said:
Yeah, that's how it's supposed to be. ADB can only be used if the phone is booted to the system or the recovery mode. You can't use ADB commands while it's booted to the bootloader or the download mode. You need to use fastboot commands in these modes.
Sent from my HTC One M9 using XDA Labs
Click to expand...
Click to collapse
apparently i had a problem with drivers. i have fixed it now, that's why it gave empty devices.
Ok went back to bootloader mode. run fastboot getvar all:
Code:
(bootloader) version:0.5
(bootloader) variant:MTP eMMC
(bootloader) secure:yes
(bootloader) version-baseband:
(bootloader) version-bootloader:
(bootloader) max-download-size: 0x20000000
(bootloader) partition-type:cache:ext4
(bootloader) partition-size:cache: 0x14000000
(bootloader) partition-type:userdata:ext4
(bootloader) partition-size:userdata: 0x5e0000000
(bootloader) partition-type:system:ext4
(bootloader) partition-size:system: 0x118000000
(bootloader) serialno:HT54GYJ05021
all:
finished. total time: 0.132s
this is instead the same taken from dl mode:
Code:
(bootloader) kernel: lk
(bootloader) product: htc_himauhl
(bootloader) version: 1.0
(bootloader) version-main: 3.42.708.3
(bootloader) boot-mode: download
(bootloader) version-baseband: 01.01_U11440801_97.04.60111G_F
(bootloader) version-bootloader: 1.0.0.0000
(bootloader) mid: 0PJA10000
(bootloader) cid: HTC__044
all:
finished. total time: 0.006s
what now?
Mhm, there's nothing strange in that output, either.
Can you flash a RUU and re-try installing the OTA? If that doesn't fix the problem then the only other option is converting the phone as I already suggested to vglaksana.
Sent from my HTC One M9 using XDA Labs
Flippy498 said:
Can you flash a RUU and re-try installing the OTA?
Click to expand...
Click to collapse
can you point me to a guide on how to do this?
and also where can i find my relevant RUU?
thanks.
I already did so in my first reply to you.
Sent from my HTC One M9 using XDA Labs
Hi everyone,
A few months ago I switched to Lineage 14 on my M9 (himaul, cid 102, s-on). I followed the instructions here.
Since the M9 will no longer get any updates, and I'm experiencing random reboots and crashes, I want to go back to stock (rom+recovery). I read a few threads here but I'm still confused. Is there a step by step guide that explains how to do it?
Thanks in advance
annascott said:
Hi everyone,
A few months ago I switched to Lineage 14 on my M9 (himaul, cid 102, s-on). I followed the instructions here.
Since the M9 will no longer get any updates, and I'm experiencing random reboots and crashes, I want to go back to stock (rom+recovery). I read a few threads here but I'm still confused. Is there a step by step guide that explains how to do it?
Thanks in advance
Click to expand...
Click to collapse
Do "fastboot getvar all" in download and post result here(remove your imei/sn).
(bootloader) kernel: lk
(bootloader) product: htc_himauhl
(bootloader) version: 1.0
(bootloader) current-slot:
(bootloader) version-main: 4.28.401.3
(bootloader) boot-mode: download
(bootloader) version-baseband: 01.01_U114401011_117.00.61117G_2_F
(bootloader) version-bootloader: 1.0.0.0000
(bootloader) mid: 0PJA10000
(bootloader) cid: HTC__102
all:
finished. total time: 0.008s
This is the ruu: https://androidfilehost.com/?fid=961840155545567615
First make sure you saved all of your data because this procedure will wipe all of your data and your internal storage.
Boot in download
"fastboot flash zip ruu.zip" - do the command again when requested.
Note: Make sure to replace ruu.zip with your file.
"fastboot reboot"
And that's it? Everything will go back to how it was out of the box?
annascott said:
And that's it? Everything will go back to how it was out of the box?
Click to expand...
Click to collapse
Yes. except the unlocked bootloader and s-off if you have, but the rom will be completely stock.
Is there a point to re-lock the bootloader? (if it's even possible)
annascott said:
Is there a point to re-lock the bootloader? (if it's even possible)
Click to expand...
Click to collapse
It's possible but isn't needed. And if you want to unlock it again will wipe your data.
"fastboot oem lock"
tyvm!!! I'll try it later on.
Just to highlight that if you have an unlocked bootloader do not relock or lock it. If you have s-off there is no need at all to s-on.
Flashing back to stock doesn't wipe data but any updates from there on will.
Make sure you delete all your crap apps as it'll take an age for your phone to boot after the flash from optimisation of said crap apps.
Instead of fastboot method just rename the firmware zip to 0PJA10000.zip, copy to external sd card and boot to download mode. Press vol up to flash. Wait 10 mins and you're back to stock.
Tried flashing with fastboot, getting the error "target reported max download size of 800000000 bytes Invalid sparse file format at header magi".
What do I do?
annascott said:
Tried flashing with fastboot, getting the error "target reported max download size of 800000000 bytes Invalid sparse file format at header magi".
What do I do?
Click to expand...
Click to collapse
Make sure you have htc_fastboot.exe, not generic fastboot.exe
If this doesn't work, try the sdcard method.
Sent from my HTC One M9 using Tapatalk
Now I'm getting "FAIL9 RU_SECURITY_FAIL zip from usb command in download mode FAILED (remote: 9 RU_SECURITY_FAIL zip from usb command in download mode) Execution time is 9(s)".
SD method didn't work for me, but I may have done it wrong...
Is there a mirror for this file? Download had taken a few hourse for some reason (tried a few times). May the file is corrupt.
annascott said:
Now I'm getting "FAIL9 RU_SECURITY_FAIL zip from usb command in download mode FAILED (remote: 9 RU_SECURITY_FAIL zip from usb command in download mode) Execution time is 9(s)".
SD method didn't work for me, but I may have done it wrong...
Click to expand...
Click to collapse
You need to rename the file to 0PJA100.zip and put in the root of your external sdcard, boot in download and follow onscreen instructions.
Sent from my HTC One M9 using Tapatalk
You mean the external_sd folder?
annascott said:
You mean the external_sd folder?
Click to expand...
Click to collapse
Yes.. this folder it's actually your physical sdcard inserted in the right side slot...
Sent from my HTC One M9 using Tapatalk
I don't have an sd card
Is there another way?
annascott said:
I don't have an sd card
Is there another way?
Click to expand...
Click to collapse
No, these 2 are the only methods.
Actually does exists another method, the ruu.exe, but I don't think you'll find an exe ruu with latest version(4.28.401.3)
Make sure your downloaded ruu isn't corrupted(checksum) and place it in your adb folder.
Make sure you have htc_fastboot.exe in the same adb folder and do the commands with "htc_fastboot" instead of "fastboot"
If you still have error, try to flash from RUU mode(htc_fastboot oem rebootRUU).
Sent from my HTC One M9 using Tapatalk
htc_fastboot oem rebootRUU then file path?
annascott said:
htc_fastboot oem rebootRUU then file path?
Click to expand...
Click to collapse
"htc_fastboot oem rebootRUU" it's the entire command, this will boot your phone in ruu mode.
Then: "htc_fastboot flash zip path_to_ruu.zip" - do the command again when request.
After finishing do "fastboot reboot"
Hope you understand now, I think you never used fastboot...
Sent from my HTC One M9 using Tapatalk
So I'm trying to restore a HTC 10 of a friend of mine which is in a boot loop.
I can enter bootloader mode (white background with four options), but I cannot enter download mode.
Bootlocker is locked and S-ON, i also think USB debugging is still disabled.
I want to try to follow these steps: https://forum.xda-developers.com/showpost.php?p=72992391&postcount=26
However, ADB does not even seem to detect the device in bootloader mode even though Windows recognizes it as being a HTC device.
I'm at the stage of just throwing the device away, as I think it is bricked. Anyone has any ideas left?
PirateNL said:
So I'm trying to restore a HTC 10 of a friend of mine which is in a boot loop.
I can enter bootloader mode (white background with four options), but I cannot enter download mode.
Bootlocker is locked and S-ON, i also think USB debugging is still enabled.
I want to try to follow these steps: https://forum.xda-developers.com/showpost.php?p=72992391&postcount=26
However, ADB does not even seem to detect the device in bootloader mode even though Windows recognizes it as being a HTC device.
I'm at the stage of just throwing the device away, as I think it is bricked. Anyone has any ideas left?
Click to expand...
Click to collapse
im in the same situation ,i'm currently looking at data recovery option from gillware since apparently they literally go the extra mile physically to extract data. but im hoping there is options for me to unbrick it before deciding on that option
venom55521 said:
im in the same situation ,i'm currently looking at data recovery option from gillware since apparently they literally go the extra mile physically to extract data. but im hoping there is options for me to unbrick it before deciding on that option
Click to expand...
Click to collapse
Well at least the data on the device is not worth much to my friend. Let me know if you find were able to unbrick it
PirateNL said:
So I'm trying to restore a HTC 10 of a friend of mine which is in a boot loop.
I can enter bootloader mode (white background with four options), but I cannot enter download mode.
Bootlocker is locked and S-ON, i also think USB debugging is still disabled.
I want to try to follow these steps: https://forum.xda-developers.com/showpost.php?p=72992391&postcount=26
However, ADB does not even seem to detect the device in bootloader mode even though Windows recognizes it as being a HTC device.
I'm at the stage of just throwing the device away, as I think it is bricked. Anyone has any ideas left?
Click to expand...
Click to collapse
ADB won't detect it if USB debugging is turned off.
Can you boot to RUU mode? If so you could restore it perhaps that way. If you are booted to that you can run an RUU.exe
The command is:
fastboot oem rebootRUU
xunholyx said:
ADB won't detect it if USB debugging is turned off.
Can you boot to RUU mode? If so you could restore it perhaps that way. If you are booted to that you can run an RUU.exe
The command is:
fastboot oem rebootRUU
Click to expand...
Click to collapse
Thanks for your reply. I'm not sure on how I can execute that command without ADB/USB debugging being enabled? Any advice there?
PirateNL said:
Thanks for your reply. I'm not sure on how I can execute that command without ADB/USB debugging being enabled? Any advice there?
Click to expand...
Click to collapse
You don't have to have USB debugging on to use fastboot commands, only ADB commands. For many fastboot commands, you need an unlocked bootloader. For this one you don't. Or at least you didn't on the M8 before HTC introduced download mode. I'm pretty sure it will still work.
xunholyx said:
You don't have to have USB debugging on to use fastboot commands, only ADB commands. For many fastboot commands, you need an unlocked bootloader. For this one you don't. Or at least you didn't on the M8 before HTC introduced download mode. I'm pretty sure it will still work.
Click to expand...
Click to collapse
So I only had time to test this today. And you were right i was able to trigger this command:
fastboot oem rebootRUU
The phone then rebooted showed the grey HTC boot screen and soon after it started the boot loop sequence again. What am I suppose to do now? Is there anything I can flash in this RUU mode? Thanks again for your help.
PirateNL said:
So I only had time to test this today. And you were right i was able to trigger this command:
fastboot oem rebootRUU
The phone then rebooted showed the grey HTC boot screen and soon after it started the boot loop sequence again. What am I suppose to do now? Is there anything I can flash in this RUU mode? Thanks again for your help.
Click to expand...
Click to collapse
You can flash an RUU in RUU mode. An RUU is HTC's "ROM Update Utility". It's a full system image. You would need to know his model type, like Sprint, AT&T, US Unlocked, etc Then you could download the appropriate RUU for it.
Does it boot to RUU mode with the red security warning at the bottom? If so, enter fastboot getvar all, and you can find the firmware version the phone is on now. It's listed under "version-main". Get the RUU with the same version number as that, and flash it in RUU mode.
If you can get the firmware version and you post it here, I can direct you to the proper RUU to download.
xunholyx said:
You can flash an RUU in RUU mode. An RUU is HTC's "ROM Update Utility". It's a full system image. You would need to know his model type, like Sprint, AT&T, US Unlocked, etc Then you could download the appropriate RUU for it.
Does it boot to RUU mode with the red security warning at the bottom? If so, enter fastboot getvar all, and you can find the firmware version the phone is on now. It's listed under "version-main". Get the RUU with the same version number as that, and flash it in RUU mode.
If you can get the firmware version and you post it here, I can direct you to the proper RUU to download.
Click to expand...
Click to collapse
Unfortunately I do not see the red security warning, it just a grey HTC logo for a few seconds, then it reboots and then shows a white HTC logo + "powered by android" and then its stuck in the boot loop again.
The phone is an EU-model, this is the output you requested:
Code:
C:\adb>fastboot.exe getvar all
(bootloader) version:0.5
(bootloader) ramdump-mode:false
(bootloader) variant:Surf eMMC
(bootloader) secure:yes
(bootloader) version-baseband:
(bootloader) version-bootloader:
(bootloader) max-download-size: 0x20000000
(bootloader) partition-type:cache:ext4
(bootloader) partition-size:cache: 0xe000000
(bootloader) partition-type:userdata:ext4
(bootloader) partition-size:userdata: 0x61e000000
(bootloader) partition-type:system:ext4
(bootloader) partition-size:system: 0xef000000
(bootloader) serialno:FA69KBN01219
all:
finished. total time: 0.360s
The version-main variable does not seem to be there
xunholyx said:
You can flash an RUU in RUU mode. An RUU is HTC's "ROM Update Utility". It's a full system image. You would need to know his model type, like Sprint, AT&T, US Unlocked, etc Then you could download the appropriate RUU for it.
Does it boot to RUU mode with the red security warning at the bottom? If so, enter fastboot getvar all, and you can find the firmware version the phone is on now. It's listed under "version-main". Get the RUU with the same version number as that, and flash it in RUU mode.
If you can get the firmware version and you post it here, I can direct you to the proper RUU to download.
Click to expand...
Click to collapse
Hey man, if you have some time today. Could you please look at the output I sent? Im not sure what to do next.
Thanks in advance
PirateNL said:
Hey man, if you have some time today. Could you please look at the output I sent? Im not sure what to do next.
Thanks in advance
Click to expand...
Click to collapse
The readout doesn't really say anything. With the HTC 10, and starting with the M9 I believe (I never owned one), you can only get a proper getvar from download mode or RUU mode. You can't get one from bootloader anymore like you used to be able to.
You said it was a EU model, so I would suspect it's WWE. The RUUs for that are available, but you can't flash it in bootloader, only download or RUU mode.
exactly the same problem here
PirateNL said:
Unfortunately I do not see the red security warning, it just a grey HTC logo for a few seconds, then it reboots and then shows a white HTC logo + "powered by android" and then its stuck in the boot loop again.
The phone is an EU-model, this is the output you requested:
Code:
C:\adb>fastboot.exe getvar all
(bootloader) version:0.5
(bootloader) ramdump-mode:false
(bootloader) variant:Surf eMMC
(bootloader) secure:yes
(bootloader) version-baseband:
(bootloader) version-bootloader:
(bootloader) max-download-size: 0x20000000
(bootloader) partition-type:cache:ext4
(bootloader) partition-size:cache: 0xe000000
(bootloader) partition-type:userdata:ext4
(bootloader) partition-size:userdata: 0x61e000000
(bootloader) partition-type:system:ext4
(bootloader) partition-size:system: 0xef000000
(bootloader) serialno:FA69KBN01219
all:
finished. total time: 0.360s
The version-main variable does not seem to be there
Click to expand...
Click to collapse
I have exactly the same problem with my HTC10, i don't have access to download mode, recovey, system, i even tried to boot to an image of twrp and i can't.
Code:
D:\Android\platform-tools>fastboot getvar all
(bootloader) version:0.5
(bootloader) ramdump-mode:false
(bootloader) variant:Surf eMMC
(bootloader) boot-mode:FASTBOOT
(bootloader) secure:yes
(bootloader) version-baseband:
(bootloader) version-bootloader:
(bootloader) max-download-size: 0x20000000
(bootloader) partition-type:cache:ext4
(bootloader) partition-size:cache: 0xe000000
(bootloader) partition-type:userdata:ext4
(bootloader) partition-size:userdata: 0x61e000000
(bootloader) partition-type:system:ext4
(bootloader) partition-size:system: 0xef000000
(bootloader) serialno:FA661BN06728
all:
Finished. Total time: 0.393s
Click to expand...
Click to collapse
Click to expand...
Click to collapse
xunholyx said:
The readout doesn't really say anything. With the HTC 10, and starting with the M9 I believe (I never owned one), you can only get a proper getvar from download mode or RUU mode. You can't get one from bootloader anymore like you used to be able to.
You said it was a EU model, so I would suspect it's WWE. The RUUs for that are available, but you can't flash it in bootloader, only download or RUU mode.
Click to expand...
Click to collapse
OK that makes sense. But as you know I cannot get into RUU nor download mode. I guess it really is bricked then. Oh well thanks for your time and help.
PirateNL said:
OK that makes sense. But as you know I cannot get into RUU nor download mode. I guess it really is bricked then. Oh well thanks for your time and help.
Click to expand...
Click to collapse
It might not be. A friend reminded me of a method in a conversation about something else. I'm at work right now, but I'll reply again later on when I'm home
Here's how you may be able to fix it. If you flash all of the parts of the firmware.zip included in the RUU, you essentially are flashing the RUU (mostly, but not exactly).
You can flash the individual parts in bootloader.
Here is a link to the instructions
Here is a link to the firmware you will need.
And as I've already stated, I assume he has WWE firmware. This firmware is not carrier branded. You said he had the European model so I'm going with that.
You can already boot to bootloader, so obviously you can skip that part of the instructions.
Good luck! Hopefully you can bring it back to life.
no luck
xunholyx said:
Here's how you may be able to fix it. If you flash all of the parts of the firmware.zip included in the RUU, you essentially are flashing the RUU (mostly, but not exactly).
You can flash the individual parts in bootloader.
Here is a link to the instructions
Here is a link to the firmware you will need.
And as I've already stated, I assume he has WWE firmware. This firmware is not carrier branded. You said he had the European model so I'm going with that.
You can already boot to bootloader, so obviously you can skip that part of the instructions.
Good luck! Hopefully you can bring it back to life.
Click to expand...
Click to collapse
D:\Android\platform-tools>fastboot flash radio radio.img
Sending 'radio' (54629 KB) OKAY [ 1.341s]
Writing 'radio' FAILED (remote: 'cannot flash
this partition in s-on state')
fastboot: error: Command failed
it says that because it is in S-On state, any ideia ohow can i change the S state?
thank you mate
xunholyx said:
Here's how you may be able to fix it. If you flash all of the parts of the firmware.zip included in the RUU, you essentially are flashing the RUU (mostly, but not exactly).
You can flash the individual parts in bootloader.
Here is a link to the instructions
Here is a link to the firmware you will need.
And as I've already stated, I assume he has WWE firmware. This firmware is not carrier branded. You said he had the European model so I'm going with that.
You can already boot to bootloader, so obviously you can skip that part of the instructions.
Good luck! Hopefully you can bring it back to life.
Click to expand...
Click to collapse
Tried to revive it today. Unfortunately getting the same error as our friend in the post above me:
Code:
C:\adb>fastboot flash radio radio.img
< waiting for device >
target reported max download size of 536870912 bytes
sending 'radio' (54629 KB)...
OKAY [ 1.366s]
writing 'radio'...
FAILED (remote: cannot flash this partition in s-on state)
finished. total time: 1.456s
So to summarize:
- Not able to boot into download/recovery/RUU mode
- Cannot flash images using fastboot due to S-ON
I guess that's it, RIP HTC 10.
PirateNL said:
Tried to revive it today. Unfortunately getting the same error as our friend in the post above me:
Code:
C:\adb>fastboot flash radio radio.img
< waiting for device >
target reported max download size of 536870912 bytes
sending 'radio' (54629 KB)...
OKAY [ 1.366s]
writing 'radio'...
FAILED (remote: cannot flash this partition in s-on state)
finished. total time: 1.456s
So to summarize:
- Not able to boot into download/recovery/RUU mode
- Cannot flash images using fastboot due to S-ON
I guess that's it, RIP HTC 10.
Click to expand...
Click to collapse
costum rom was installed on my phone I deleted everything with trwp normally I should have installed a new rom file but I didn't now the htc logo is stuck, there is twrp unlocked but I can't access it the boot loader does not open, because there is no rom, it does not open normally, there is only htc logo and red warning, maybe I can open the security mode or something else I am very tired