Develop Bugs

Phone automatically starts into bootloader and flashing doesnt work

So as you might have heard, android 6.0 is out on htc one m8 now, and as usual i wanted to update. I got my device into a bootloop after unrooting and downloading some OTA's online, and messing around with stuff that didnt work.
But now im rly stuck, when i boot my phone up it automatically boots into bootloader. I cant flash a boot.img because i get a signature verify fail. Updating with RUU returns error 130 and factory resetting doesnt do anything at all(in fastboot and in recovery). plzzzz help

Hi,
Did you try to reflash your recovery and try to install another rom like ViperOne M8? Or if you want i can send you the stock ROM Android 6.0

Laurens54321 said:
So as you might have heard, android 6.0 is out on htc one m8 now, and as usual i wanted to update. I got my device into a bootloop after unrooting and downloading some OTA's online, and messing around with stuff that didnt work.
But now im rly stuck, when i boot my phone up it automatically boots into bootloader. I cant flash a boot.img because i get a signature verify fail. Updating with RUU returns error 130 and factory resetting doesnt do anything at all(in fastboot and in recovery). plzzzz help
Click to expand...
Click to collapse
You seem to be going about things rather haphazardly:
1) Not sure exactly what "some OTAs" refers to. But there is typically only one OTA that will properly work. That being the one that is for your CID (carrier version) and for the next software version (can't skip any).
2) Along the same lines, you can't just flash any RUU. It has to be for your CID and MID (Error 130 usually means wrong MID), and equal or greater version number than main version on the phone (no "downgrading" unless you have s-off).
3) "messing around with stuff that didnt work" doesn't tell us anything about how you got to the current condition. You need to be specific and detailed, if you want us to be able to tell what you did, and how to recovery.
4) You can't unroot and OTA, it has to be a stock (never rooted) ROM and stock recovery.
5) boot.img in itself probably won't help your situation. And signature verify fail usually means you tried to flash without the bootloader unlocked (which won't work).

Are you S-OFF? If so, this works;
1) Download 0P6BIMG.zip. You'll have to Google
"dottat @ XDA M8 RUU" to get the file as I haven't
made at least ten posts here and can't post links yet.
2) Place 0P6BIMG.zip on an SD card formatted fat32 ONLY.
3) Boot your phone, allow HBOOT to recognize 0P6BIMG.zip
and follow the prompts.
RESULT: This will land you on STOCK kitkat 1.55.605.2
pre-rooted with stock recovery.
----------------------------------------------------------------
CREDIT: dottat @ XDA

Cannot flash

Hi,
I have a very urgent issue and I need your help.
I have a M9 which had Android Revolution 16. Wifi was not working, wrong MAC address (02:00:00...)
Well I tried to reflash it, and somewhere along the way I must have screwed something up.
I tried to flash Venom...error.
I tried stock RUU - 0PJAIMG_HIMA_UHL_L50_SENSE70_HTC_Europe_1.32.401.15_R1_Radio_01.01_U11440261_56.02.50306G_2_F_release_426891_signed
Also error - i belied the MID and CID are ok 0PJA10000 HTC__001
Phone is S-ON
Before that I followed a tutorial in which is was described to lock the bootloader.
Well, here it f. everything up.
Recovery is not working anymore and I cannot flash it recovery and RU_SECURITY_FAIL bootloader isn't bl_unlocke
I installed the unlock-code.bin, successfully
Still same issue.
Bootloader shows UNNOWN, Download mode shows still locked.
What can I do?

I have now TWRP, issue was because of the used fastboot soft.
Now to install a new rom...

I installed three different roms, wifi still fails to load.
I cannot install venom, Error status 7 (it fails at busybox)
Do you think I can resolve the wifi issue if I go S-OFF and flash the RUU in the first post?
Thank you.

sahara101 said:
I installed three different roms, wifi still fails to load.
I cannot install venom, Error status 7 (it fails at busybox)
Do you think I can resolve the wifi issue if I go S-OFF and flash the RUU in the first post?
Thank you.
Click to expand...
Click to collapse
The problem is the recovery. Incomplete/corrupt/rogue. Redownload and check its md5 + file size. Flash if it is correct.
If you have the same issue find another twrp.
S-off is probably the best investment you can make for your m9. It perplex's me why people only choose to root and then flash custom roms knowing it isn't the full access they are looking for.
Sent from my HTC One M9 using Tapatalk

OTA Update fails to install on HTC one M9. Help!

I recently bought an Unlocked HTC one M9 from eBay. It was on Android 5.0.2 (1.32.617.6) and I received an update notification for 1.32.617.30. When I clicked to install it, it fails saying error in cache with error 7. I think since it's a used phone the device software has been tampered before therefore the OTA update fails. I don't know the device history.This is what I found in bootloader mode.
Software status: Official
S-OFF
Bootloader:Locked
It is super CID (11111111)
And it has stock recovery.
I have tried flashing 1.32.617.6 stock ROM from stock recovery after I found it on XDA. It also failed saying signature verification failed. I searched this forum and found that someone had the same issue and they had to flash 1.32.617.6 using a SD card formatted to FAT32. I don't have a SD card so I couldn't try it.
I also tried HTC's latest RUU. EXE for Unlocked/Developer edition but it doesn't run well. It starts and shuts down after it asks me to agree to terms and conditions. I have latest HTC sync manager and it recognizes my phone. I will be trying this again on some other computer.
I really want to update my device to the latest version of OS. Please help me! I don't know what else to try.

You cannot flash an ruu because the device is modified. The easiest option is to flash an unsigned update. Unlock your bootloader and enable usb debugging first though.
Beamed in by telepathy.

I don't understand in what way the device is modified because it says bootloader Locked not relocked and everyrhing is stock. I thought it might have been restored to stock after rooting or what not. If that is the case shouldn't I be able to install OTA update?
Anyways I wanted to know if there is some way where I don't need to unlock bootloader or root it. I want to stay on stock OS.

Update: used RUU.EXE on Windows 7 computer and it worked. For some reason Windows 8/10 is not good with running external exe files.

Bricked HTC One M9

I have an HTC One M9 that up until yesterday had an unlocked bootloader and had S-Off.
It was running a pretty old ROM so I decided to update it. My first attempt was Viper.
After installing through TWRP recovery it would only take me to the TWRP boot screen after rebooting.
I attempted another ROM, this time Revolution and got the same results.
I’ve been messing with it for hours and somehow I have S-ON and the bootloader is locked. Actually it says RELOCKED.
It has no OS and it will no longer go to Recovery mode. I think the TWRP I tried to install is too new for it.
I’ve performed the HTC bootloader unlock procedure a few times and although it says successful, after reboot, its still relocked.
Am I screwed, or is there something more I can try?

If bootloader is looked, the only solution is to try to flasher the latest ruu according to the model of your M9. It goes into downloading mode??

Dark Stranger said:
If bootloader is looked, the only solution is to try to flasher the latest ruu according to the model of your M9. It goes into downloading mode??
Click to expand...
Click to collapse
Yes, it goes into download mode. I've tried the only Telus ruu I could find (RUU_HIMA_UL_M60_SENSE70_ATT_MR_NA_Gen_Unlock_3.35.617.31.exe)
and I get a Error 131 Customer ID Error.
I just tried a Sprint ruu (RUU_HIMA_WHL_M60_SENSE70_SPCS_MR_Sprint_WWE_3.41.651.21.exe) and I got Error 155 Unknown Error. They both fail right after it displays Updating Signatures.
I'm in Canada and it's a Telus phone but it's carrier unlocked.
Do I need to use a Telus RUU or should any Canadian RUU work on it?

are you sure yours already s-off?
1. re flash lastest TWRP
2. flash required lastest firmware (s-off)
Firmware 3.35.401.12 is required for proper installation! Download (S-OFF ONLY)
3. flash your fav lastest custom rom

Yes, it's definitely S-On.
Any Canadians out there? After some reading I realize I need an RUU of a specific sku. In my case 661.
I need a Telus RUU of 2.11.661.5 or higher for the M9. I'm hoping that will resolve my issue.

sprint/s-on/unlocked/rooted tried to upgrade firmware, now no firmware will take

was running bad boys marshmallow with TWRP 3.0, bootloader unlocked, s-on, unsure of firmware version
google maps would not work properly. rebooted the phone. stuck on optimizing apps. tried troubleshooting, ultimately decided to upgrade to badboyz nuget.
it required firmware, which I attempted to flash in download mode:
4.27.651.4 Signed Firmware from OTA, removed recovery (fastboot flashable): https://www.androidfilehost.com/?fid=457095661767155280
signed version without recovery... should have been fine for s-on with TWRP, yet it failed, wiped TWRP for stock recovery, and removed the developer flag from the boot screen.... which is as far as it will boot. also, I tried multiple other signed RUU and they all fail giving OS errors. not sure where to go from here. still have access to stock recovery, SD card, download mode, etc
edit
this firmware successfully upgraded, but I still get stuck at htc screen with no dev flag: https://androidfilehost.com/?fid=673368273298946816
edit
after letting it sit at the HTC screen for about 15 min, it actually booted. hopefully this will help someone else out.

To update firmware you need the full update, not the ota.

shivadow said:
To update firmware you need the full update, not the ota.
Click to expand...
Click to collapse
yea I realized that after the fact, it was the first signed firmware suggested for the rom update.
even after that, I must have tried 6 or 7 full firmware that also failed with various errors. someone linked the most recent one in a thread for my original rom and that worked.