Develop Bugs

[Q] Soft brick - can't push ROM to phone

Hello,
I am trying to fix my issue and have done a ton of reading but can't figure out where to go from here. I've had my phone rooted for months and tried to flash a newer custom ROM today and it ended up locking my phone into a boot loop. I was able to get out of it and had to re install a recovery tool (have installed both CWM and TWRP and they work fine). But I can't actually get a ROM back onto my phone because I don't have one on the SD card and I can't get one to it. I just want to put a stock ROM back onto it at this point.
I can't boot into windows to access the SD card because whenever I boot the phone normally it just goes back to boot looping. I have tried ADB push when in recovery to put a ROM on the SD card and I continually get permission denied when I try to do that. I have tried ADB sideloader and I can't get that to work either. How can I go about getting a ROM to my phone so I can flash it via CWM/TWRP?
Fastboot works fine and I can flash recoveries no problem. ADB appear to work but I can't understand why I can't just get push to work. Any help would be greatly appreciated.
HTC One M7 on Verizon.
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.54.0000
(bootloader) version-baseband: 1.12.42.0731
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.10.605.8
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno:xxx
(bootloader) imei: xxx
(bootloader) meid: xxx
(bootloader) product: m7_wlv
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0731000
(bootloader) cidnum: VZW__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4325mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-97af273845
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.070s

If you type "adb devices" from a Command Prompt, do you see your phone listed?
Try powering off your phone, then holding Power+VolDown until you get to HBOOT. From there, enter recovery (TWRP is my preferred). ADB push does not require anything to be done prior to using it, so assuming you can see your phone with "adb devices", proceed like this:
Rename the ROM you want to flash to ROM.zip
Type "adb push ROM.zip /sdcard/" No quotes
If the ROM is around 1GB, this will take 5-10 minutes.
Once done, use TWRP file manager (under Advanced) to verify the file is there.
Reboot back into recovery and verify it's still there. If it is, install it. If it's not, you will have to RUU back to stock and go through the unlock process again.

NotATreoFan said:
If you type "adb devices" from a Command Prompt, do you see your phone listed?
Try powering off your phone, then holding Power+VolDown until you get to HBOOT. From there, enter recovery (TWRP is my preferred). ADB push does not require anything to be done prior to using it, so assuming you can see your phone with "adb devices", proceed like this:
Rename the ROM you want to flash to ROM.zip
Type "adb push ROM.zip /sdcard/" No quotes
If the ROM is around 1GB, this will take 5-10 minutes.
Once done, use TWRP file manager (under Advanced) to verify the file is there.
Reboot back into recovery and verify it's still there. If it is, install it. If it's not, you will have to RUU back to stock and go through the unlock process again.
Click to expand...
Click to collapse
No it isn't showing up when I do that while in recovery.
C:\Users\Mat\Desktop\adb>adb devices
List of devices attached

factor00 said:
No it isn't showing up when I do that while in recovery.
C:\Users\Mat\Desktop\adb>adb devices
List of devices attached
Click to expand...
Click to collapse
What about fastboot?

NotATreoFan said:
What about fastboot?
Click to expand...
Click to collapse
Yes fastboot is working. I can see the phone info still. You said I can just RUU. I didn't realize I could do that. That's fine with me I have no issue with that.
I just re-lock the boot loader and then run the RUU from windows? Would this be the appropriate file? RUU Zip M7 WL JB 50 VZW 1.10.605.10 Decrypted from HTC1 Guru.com (I can't post the actual link do to the forum rules.) The CID and model id match what my phone says.
Thanks for all your help!

factor00 said:
Yes fastboot is working. I can see the phone info still. You said I can just RUU. I didn't realize I could do that. That's fine with me I have no issue with that.
I just re-lock the boot loader and then run the RUU from windows? Would this be the appropriate file? RUU Zip M7 WL JB 50 VZW 1.10.605.10 Decrypted from HTC1 Guru.com (I can't post the actual link do to the forum rules.) The CID and model id match what my phone says.
Thanks for all your help!
Click to expand...
Click to collapse
I haven't done anything RUU in a while, so I don't want to steer you wrong. But I believe you can use decrypted to get everything up and running. Check the general forum for a guide on returning to stock.
Sent from my HTC6525LVW using XDA Premium 4 mobile app

Just remember to keep s-off while running the ruu

Fastboot

I need to unselect fastboot in my settings, but my phone wont even turn on pass the htc logo. Can someone please help me?

You don't really need to unselect "Fast boot" in settings. Its not even an option in Settings anymore in Lollipop or Marshmallow.
Even if you are still on Kitkat (few people are) the only thing that "Fast boot" affected, is that it prevented booting into bootloader from a power-off condition. But if you force a reboot (which is distinctly different from power-off), you can still get to bootloader:
1) Hold power + vol up until phone reboots (may take a minute or more, if you are stuck on the HTC logo screen)
2) Once the screen goes dark to reboot (but before the HTC logo screen comes back up) let go of the buttons, and hold only the vol down button. Don't let go of vol down, until you see the bootloader screen.
3) If it didn't work, you just didn't get the timing right. You either started pressing vol down too late, or let go too early. Just repeat steps 1 & 2 above until you get it right.

Thank you for help. I already unlock my m8(by HTC dev) and I get recovery and install from recovery superSU zip file. But i cant finished superSU parts(so I am still without s-off and root?), because my telephone still cant load android(I am still on ``HTC one`` logo). So question can I put original firmware into memory card and reinstall all system?

dzefas said:
Thank you for help. I already unlock my m8(by HTC dev) and I get recovery and install from recovery superSU zip file. But i cant finished superSU parts(so I am still without s-off and root?), because my telephone still cant load android(I am still on ``HTC one`` logo). So question can I put original firmware into memory card and reinstall all system?
Click to expand...
Click to collapse
Many folks get fail to boot after trying to root; due to using an old SuperSU version. If the phone is on Marshmallow (Android 6), you need SuperSU 2.52 or later (2.65 is recommended as the latest stable version).
If this is the case for you (on MM and used an old version SuperSU) then flashing SuperSU 2.65 should allow the phone to boot (and with root).
You should also use current version TWRP 3.0

yes i am using TWRP 3.0.2 and superSU version is 2.65. I am still stuck on `HTC ONE logo`.

dzefas said:
So question can I put original firmware into memory card and reinstall all system?
Click to expand...
Click to collapse
Probably your best bet is to restore a stock nandroid that matches your version.
You didn't make a backup in TWRP before rooting? You should always do that, for this very reason (in case you run into problems and need to restore).
For more specific help on what version, do fastboot getvar all, and post the results (delete IMEI and serial number before posting).
---------- Post added at 03:16 PM ---------- Previous post was at 03:12 PM ----------
dzefas said:
yes i am using TWRP 3.0.2 and superSU version is 2.65. I am still stuck on `HTC ONE logo`.
Click to expand...
Click to collapse
Its not clear, were those the versions you used to begin with, or you tried them after my recommendation?

I tried those versions before your recommendations.

after several tryings, telephone trying load. I mean 'Android is starting optimizing app 21 of 133'

And still after optimizining stuck on ``green HTC``...even i can regulate sound, but this is it.

(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.29.214500021.12G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 6.12.401.4
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno:
(bootloader) imei:
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B10000
(bootloader) cidnum: HTC__102
(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: 76df2b54
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!

So question can I put original firmware into memory card and reinstall all system?

dzefas said:
So question can I put original firmware into memory card and reinstall all system?
Click to expand...
Click to collapse
Not firmware but a RUU zip.
Note : MUST relock bootloader
Boot to fastboot/bootloader mode then run command in terminal
fastboot oem lock
What you need :
1. a MicroSD
2. Download the 6.12.401.4 RUU zip - https://www.androidfilehost.com/?fid=24369303960687057
3. Rename the file to 0P6BIMG.zip (that's a zero not "O")
4. Put the 0P6BIMG.zip on your microSD
5. Boot your device to bootloader/fastboot then select hboot, it will scan the update zip and ask whether to update - volume up to select yes
6. Let it do its stuff
7. Once completed, reboot
8. Delete the 0P6BIMG.zip on your microSD (or remove the microSD)
9. done

I to do relock, but still cant find right file in microSD card...why? I check several time of file name...

And now telephone cant even load himself, recovery etc. How to back from RELOCKED?

dzefas said:
I to do relock, but still cant find right file in microSD card...why? I check several time of file name...
Click to expand...
Click to collapse
Having the bootloader unlocked or not (relocked, locked) , has nothing to do with it finding the file. It will find it either way (but fail to install if bootloader is unlocked).
You sure you named the file properly (first character is "zero" not letter "O")?
Also, make sure you turned off the Windows option to hide file extensions (which is ON by default). Otherwise, you may have named it 0P6BIMG.zip.zip and not know it.

HTC with locked internal memory

Folks
I need help to solve a problem.
I bought a HTC One M8x and decided to set up a rom custon. I study the subject before. I took the program kit available for the M8 and follow all the steps to unlock. All this function normally, however when installing the ROM custon the device just gave error. I was exploring the tool I ended up pressing and making procedures that were not listed, but apparently did not issue before starting the installation made the backup and then wipe. I started the procedure to install, entered the install section and located the ROM and sent install. After a while appeared an error saying that the installation was not possible, I managed to recover the backup, but the phone was not the same. I realized that my internal memory is no longer visible, I can not download pictures or audios in whatsapp, another thing I noticed is that the file manager also does not provide the internal memory (directories, programs, and others). When I try to synchronize your phone with your computer to the same thing, I can see the micro SD, but can not see the internal memory. I possibly when I was digging the Recovery program just blocking the internal memory and wanted to know how do to reverse. Does anyone have any ideas.

Do you have access to bootloader? if yes. You can try to restore your phone with HTC RUU

ddfilho said:
I took the program kit available for the M8 and follow all the steps to unlock. All this function normally, however when installing the ROM custon the device just gave error.
Click to expand...
Click to collapse
Using the (now outdated) toolkit was a mistake. Whenever modding these devices, you need to research the current methods applicable to the current state of the phone, not methods from 2 years ago (and all the toolkits have not been updated in that long or more).
The toolkit installs an obsolete version of TWRP, and that is probably why the ROM is failing to flash. It probably also wiped out your OS version on bootloader screen and getvar (not a major issue, but an inconvenience if you want to determine the firmware number).
You should update to more current version of TWRP. But you'll probably need to solve the issue of your internal storage first, which is apparently been corrupted. Go into TWRP, and try the option in Wipe to "Format Data" (button next to "Advanced"). This usually fixes the corrupt internal storage issue.
Also do fastboot getvar all, and post the results, so we can see more info about the phone, and more properly provide guidance. Delete IMEI and serial number before posting.

I have access to the bootloader but do not know run this action. Could you tell me where I can walkthrougt to do so.
Thank you for your help

Pardon
Now that saw the second message. I will perform this procedure now

Friend
Your solution worked perfectly.
I wanted your help to make the second action, I entered the bootloader and accessed the fastboot but did not find the getvar option. Could you tell me how to do it.
I found the TWRP 3.0.2, I believe it is the last version but need help because I believe that the update version is not simple, I installed the 2.7.0.2 version.
Thanks again

ddfilho said:
I wanted your help to make the second action, I entered the bootloader and accessed the fastboot but did not find the getvar option. Could you tell me how to do it.
Click to expand...
Click to collapse
This isn't an option on the phone, if that is what you mean. Its a fastboot command issued from your PC, and you'd know how to issue a fastboot command if you unlocked the bootloader via HTCDev.com, instead of letting the toolkit do it for you. Which is another reason I don't like the toolkits: they shortcut the learning process, and leave you without the skills to solve basic problems, which almost inevitably happen.
You're going to need to figure out where fastboot.exe was installed during the bootloader unlock process. Once you've found that, you can then:
1) Connect phone to PC, booted into bootloader-fastboot mode
2) On PC, open a window for the folder that contains fastboot.exe
3) Hover mouse cursor over the window, and Shift+Right Mouse button, then select "Open command window here" and this will open up Command Prompt to the fastboot directory
4) In Command Prompt window, type: fastboot getvar all
5) You will see output with details about the phone, to copy the desired text, right click on the command window, select Edit>Mark, then highlight the desired text (getvar output) and press Enter. Then paste the text.
6) Be sure to delete IMEI and serial number from getvar output before posting it here
ddfilho said:
I found the TWRP 3.0.2, I believe it is the last version but need help because I believe that the update version is not simple, I installed the 2.7.0.2 version.
Click to expand...
Click to collapse
Exact TWRP version depends on your current firmware, which we can determine from the getvar output above.
Once we've determined the proper TWRP version, its easily installed by putting the file in your fastboot folder, and flashing with fastboot command. Again, we see how valuable it is to know how to use fastboot. But don't try that, until we've determined the proper version from getvar output.

I managed to perform the procedure now. See the information:
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.29.214500021.24_2G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno:
(bootloader) imei:
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B11000
(bootloader) cidnum: HTC__621
(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: 205bdca3
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.017s

ddfilho said:
I managed to perform the procedure now. See the information:
(bootloader) version-baseband: 1.29.214500021.24_2G
(bootloader) version-main:
Click to expand...
Click to collapse
As I suspected, your firmware number (version-main) info was wiped out by using an obsolete version of TWRP (known bug). But luckily I know the radio number corresponds to Marshmallow firmware.
Flash TWRP 3.0.2 using the fastboot install method here. No need to install Android SDK, or drivers noted in the instructions, since you already have fastboot setup (and you're a fastboot expert now ); and not need to reboot using adb, if you do it using the button combo other otherwise.
After getting the updated TWRP version installed, you should be able to put the desired custom ROM on the phone, and flash it. If not, take note of any error messages or other behaviors, and post them here.

redpoint73 said:
As I suspected, your firmware number (version-main) info was wiped out by using an obsolete version of TWRP (known bug). But luckily I know the radio number corresponds to Marshmallow firmware.
Flash TWRP 3.0.2 using the fastboot install method here. No need to install Android SDK, or drivers noted in the instructions, since you already have fastboot setup (and you're a fastboot expert now ); and not need to reboot using adb, if you do it using the button combo other otherwise.
After getting the updated TWRP version installed, you should be able to put the desired custom ROM on the phone, and flash it. If not, take note of any error messages or other behaviors, and post them here.
Click to expand...
Click to collapse
Folks
Thank you for your help
I managed to update TWRP following the instructions, but when I tried to install the ROM did not succeed.
It gave an error as if he could not open the file or install, see the message:
Error opening: `/and-sec/uuuuuuuu.uuu'(I/O error) ===> Several lines with mensagem.
You know how I can be able to install any rom?

In TWRP go to WIPE then select Format data, type yes
Then go to REBOOT select recovery ... now try again to install ROM

[Solved] Bootloop issue on Stock phone. Possible to fix without loss of data?

Hi Everyone
Newbie here so please be gentle. I have a HTC One M9 that has gone into a permanent bootloop for no apparent reason. It happened yesterday. Noticed that my phone was a bit sluggish so I decided to restart it but it didnt completely restart and went into the boot loop. The only significant change that I can think of was that I updated HTC Senses via the play store a few days ago and this was the first time I have restarted the phone after that update.
I have not modified the phone in any way and has the stock rom installed. I can access the bootloader and recovery mode. Here is a dump of fastboot getvar all command:
With the phone in Bootloader screen
C:\Temp\AndroidApp>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
all:
finished. total time: 0.149s
With the phone in download mode:
C:\Temp\AndroidApp>fastboot getvar all
(bootloader) kernel: lk
(bootloader) product: htc_himauhl
(bootloader) version: 1.0
(bootloader) version-main: 3.35.401.12
(bootloader) boot-mode: download
(bootloader) version-baseband: 01.01_U11440792_97.00.51203G_F
(bootloader) version-bootloader: 1.0.0.0000
(bootloader) mid: 0PJA10000
(bootloader) cid: HTC__001
all:
finished. total time: 0.047s
I do not have developer mode or USB debug enabled (wish I had enabled these before this happend!! )
I have tried to install an OTA update via the the 'Apply Update from SD card' method (from recovery mode) and tried to use the OTA_HIMA_UHL_M60_SENSE70_MR_HTC_Europe_3.35.401.32-3.35.401.12_release_487250.zip but I get an error after the 'verifying current system...' message which says:
System partition has unexpected contents E:Error in /sideload/package.zip
(Status 7)
Installation aborted.
Considering that I have not modified the phone in anyway, not sure why I am getting this error message as I was hoping that applying the OTA might fix the bootloop issue. If I was able to update using the OTA, would that have solved my issue? Is there any way of overcoming the Status 7 error?
Considering that I dont have developer mode enabled and USB debug enabled, is there any posibility to accessing the system files and flashing the system partition with a stock image without having to wipe personal data or do I have no choice but to do a factory reset, loose all my data and hope for the best? Any advice and step by step guide would be appreciated. Even if I can access my personal data on the internal drive and copy it somewhere else, that would be a result!
Many thanks
Rob

There is a very strong chance the nand has failed and the phone is dead.
How big is the file you're flashing?. It should be at least 2Gb. If it is less than 2Gb then it's the ota.
If the file is 2Gb or more then rename it to 0PJAIMG.ZIP,
copy it to the "external" sdcard,
boot the phone into download mode and you should see "press vol up to flash" in yellow at the bottom of the screen.
Press vol up and it will flash. (make sure your phone is plugged into a charger).
When it is complete it will auto reboot. Do not turn the phone off even if it looks 'frozen'. The process should take 5-10 minutes.

shivadow said:
There is a very strong chance the nand has failed and the phone is dead.
How big is the file you're flashing?. It should be at least 2Gb. If it is less than 2Gb then it's the ota.
If the file is 2Gb or more then rename it to 0PJAIMG.ZIP,
copy it to the "external" sdcard,
boot the phone into download mode and you should see "press vol up to flash" in yellow at the bottom of the screen.
Press vol up and it will flash. (make sure your phone is plugged into a charger).
When it is complete it will auto reboot. Do not turn the phone off even if it looks 'frozen'. The process should take 5-10 minutes.
Click to expand...
Click to collapse
Thanks you very much!!!
Phone is alive again thanks to your instructions. I had given up after trying different things. I tried flashing the RUU via fastboot but kept getting an error 9 (something to do with security). Even the factory reset option from the recovery menu wasnt working (it formatted, unpackaged and then rebooted into the boot loop) hence I gave up hope and bought a Nokia 8 as a replacement (Still prefer the M9 but I'll give the Nokia some time). If you had responded towards the begining of the week, you could have saved me £300
Any ideas why the factory reset option did not work considering that I had not modified the phone in any way? (S-ON, bootloader locked, no custom ROMS or recovery mods)
Thanks again for your help. :good:

Unfortunately I don't have time to monitor the forum and answer immediately, even if it saves someone a few quid.
Under the consumer rights act (UK) you can return the phone within the 2 week grace period for a no quibble money back. You don't need a reason. After 2 weeks the device must be faulty.
The factory reset didn't work because android is inherently broken. There is no real valid explanation at this stage but the android developers know about it but do not know how to fix it.
In all circumstances where issues are encountered flashing stock the ruu via zip should be on the cards as it fixes many things on htc phones.

I've got a
22 RU_HEADER_ERROR
22 RU_HEADER_ERROR
FAIL22 RU_HEADER_ERROR
.... Help ?

shivadow said:
There is a very strong chance the nand has failed and the phone is dead.
How big is the file you're flashing?. It should be at least 2Gb. If it is less than 2Gb then it's the ota.
If the file is 2Gb or more then rename it to 0PJAIMG.ZIP,
copy it to the "external" sdcard,
boot the phone into download mode and you should see "press vol up to flash" in yellow at the bottom of the screen.
Press vol up and it will flash. (make sure your phone is plugged into a charger).
When it is complete it will auto reboot. Do not turn the phone off even if it looks 'frozen'. The process should take 5-10 minutes.
Click to expand...
Click to collapse
Thanks. Do you know any other way to do that without sd card?

bricked htc m9

hi i was given an m9 so im trying to resurrect it first a few stats
soft version modified
locked
s-on
security warning
i can get into recovery mode
android recovery
htc/htc_himauhl/htc_himauhl
6.0/mra58k/buildteam02041257user/release-keys
then menu
reboot sys
reboot to bootloader
apply update from adb
apply update from sd card
wipe data/factory reset
wipe cache partition
power off
them some messages support api3
handle_cota_install install cwpkg to /cache/cota/cwpkg.zip
please any ideas??????????

First, we need to know more about your device.
You need adb and fastboot installed(I recommend Minimal ADB & Fastboot if you don't have already), HTC Drivers.
Put your phone in download mode and do "fastboot getvar all" remove imei/sn from output and post here.

lucyr03 said:
First, we need to know more about your device.
You need adb and fastboot installed(I recommend Minimal ADB & Fastboot if you don't have already), HTC Drivers.
Put your phone in download mode and do "fastboot getvar all" remove imei/sn from output and post here.
Click to expand...
Click to collapse
(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
hi yes have adb just downloaded the original rru tyed to install via sd card but it failed

glinjik said:
(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
hi yes have adb just downloaded the original rru tyed to install via sd card but it failed
Click to expand...
Click to collapse
Do the command again from download mode not bootloader
Sent from my OnePlus 2 using XDA Labs

lucyr03 said:
Do the command again from download mode not bootloader
hi cant get into download mode it comes up in red
failed to boot to download mode press vol
up or down to back to menu
then htc log
then in red
this build is for development purposes only do not distribute outside of htc without htc's written permission failure to comply may lead to legal action
Click to expand...
Click to collapse

No download mode means no way to flash. Dead phone.

hi so i persisted and tryed holding power button vol up down etc and somehow got to this
HTC Download Mode
****locked*****
htc_himauhl pvt s-on
lk-1.0.0.0000
radio-01.01_u11440792_95.00.51130g_f
opendsp-15.6.1.00.522.8994_1026
os-3.35.61.14
feb 4 2016, 13:06:46(670363)
then the following
system info
show barcode
reboot to bootloader
reboot to download mode
reboot
power down
then in yellow
security warning
blah blah
sd card not mounted

glinjik said:
hi so i persisted and tryed holding power button vol up down etc and somehow got to this
HTC Download Mode
****locked*****
htc_himauhl pvt s-on
lk-1.0.0.0000
radio-01.01_u11440792_95.00.51130g_f
opendsp-15.6.1.00.522.8994_1026
os-3.35.61.14
feb 4 2016, 13:06:46(670363)
then the following
system info
show barcode
reboot to bootloader
reboot to download mode
reboot
power down
then in yellow
security warning
blah blah
sd card not mounted
Click to expand...
Click to collapse
I can't find a ruu for your phone.
Try to unlock bootloader, flash twrp and flash any marshmallow based sense custom rom.
Your only way to revert to full stock is s-off.
Sent from my OnePlus 2 using XDA Labs

hi is it possible to unlock bootloader from adb in download mode or twrp? is it possible to get soff in this mode?
i have the correct rru but i tryed to flash from sd
so i renamed the rru to opjaimg.zip
i get to flash menu press vol up to start flash
start ui_updating
it just goes back to bootloader

this is the rru i got
0PJAIMG_HIMA_UHL_M60_SENSE70_MR_Orange_UK_3.35.61.14_Radio_01.01_U11440792_95.00.51130G_F_release_472007_combined_signed.zip

after trying again managed to get to recovery mode
android recovery
htc/htc_himauhl/htc_himauhl
6.0/mra58k/buildteam02041257
user/release-keys
use volume up/down and power
then reboot system now
reeboot to bootloader
apply update from adb
apply update from sd card
wipe data/ factory reset
wipe cache partition
power off
tryed apply update from sd card
gives following
e:failed to set up expected mounts for install aborting
e: failed to mount / devlog (invalid argument) try emmc mount
e: cant find device node for mount point/devlog
the list goes on
the goes back to recovery mode

You need to rename it to 0PJAIMG.zip
The first character it's zero(0) not O
And boot in download mode and follow the on screen instructions
Sent from my OnePlus 2 using XDA Labs

that 0 might b the problem il try that and report back thank you so far

tried the official rom just goes back to bootloader gonna try a custom rom next fingers crossed

tried flashing from sd get
255
255
fail 255

glinjik said:
tried flashing from sd get
255
255
fail 255
Click to expand...
Click to collapse
Fail 255 indicated a broken SD card as far as i know.

il give it a go with a different sd card

Hello,
i have a big problem with my HTC one M9 OS 3.35.161.12( s-on, bootloader locked)
Recovery mode is broken , i'm able to enter into download mode, but when i want to flash a zip file i have problems to enter into RUU Mode because it is in a bootloop after i give the command "htc_fastboot oem rebootRUU" , it means the phone attempts to enter into RUU mode but it keeps just restarting in the black screen with htc Logo for 2 -3 sec.
can annybody pls tell me what can i do to repair the RUU mode?