I've been trying to install CyanogenMod for my endeavoru by the instructions in their wiki. These are the steps I took in the very beginning:
Unlock via HTC Dev
Flashed CWM
Entered CWM
Ran the CWM backup function
Wipe data/factory reset
Transferred over the .zip file
Attempted to flash from sdcard
The installation aborted because I apparently have an insufficient version of HBOOT (1.12.0000). The page on endeavoru itself had a note on this, but the install page doesn't, so like a fool I thought there would be instructions relating to that when it became relevant. Thinking what to do, I figured maybe upgrading HBOOT is the same as flashing boot.img (which IS mentioned in the install guide), so I did that as well, but the HBOOT version stayed the same.
I was uncomfortable with not feeling in control of events, so I thought I'd get back to the stock OS as a way to reassure myself and make an external (nandroid?) backup. I thought using CWM's backup/restore function would make that possible, but when I did a restore and rebooted it just went into a bootloop. (There was a FAQ item on this, but it assumed I had a zip file to get the boot.img out of, which I don't -- this was a recovery).
Easier than finding a stock rom would seem to be just to upgrade HBOOT. I found this guide on the topic, but the link to firmware doesn't work. I've found others using Search, but they don't work either. (I have HTC__Y13.) One site that has files is here, but I'm being cautious because the phone isn't cheap and I'm trying hard not to brick it. First, the site is in German (I speak a little, but I can't bee 100% sure what these things are saying); second, the link didn't come from xda-developers, so I'm wary of trusting it out of hand.
Would you suggest going on a search for another ROM (2.17.401.2), or flashing HBOOT (with a file from the German site or from somewhere else), or some other thing? The main thing I'm concerned about for the moment is having a functional phone in the next few days.
Also, can I generally expect the battery to not run out while plugged in by USB?
Thanks in advance.
Grab the firmware.zip from the german site, it seems good.
You can get the boot.img for your nandroid backup by selecting mounts and storage > mount usb storage > /sdcard/clockworkmod/backup/
Your device will charge, provided that you are booted in recovery and the version is 5.8.4.0.
Sent from my One X using xda premium
Also, you shouldn't be concerned when flashing a HBOOT, because the package will have to be signed by HTC.
And before flashing anything you will have to flash original recovery, and relock bootloader. This basically means you will be unbrickable!
Unless something goes wrong in the process ofcourse (unlikely)
hallydamaster said:
Also, you shouldn't be concerned when flashing a HBOOT, because the package will have to be signed by HTC.
And before flashing anything you will have to flash original recovery, and relock bootloader. This basically means you will be unbrickable!
Unless something goes wrong in the process ofcourse (unlikely)
Click to expand...
Click to collapse
To flash the hboot you don't need to flash back the stock recovery first ...... Just relock, flash the firmware, unlock, flash a custom recovery again and install a new rom
Thanks. It looks like I got the lock and flash done fine, but it hangs on unlock:
Code:
[~/endeavory] fastboot oem lock
...
OKAY [ 0.000s]
finished. total time: 0.001s
[~/endeavory] fastboot oem rebootRUU [13:14]
...
(bootloader) Save data from original MSC...
(bootloader) Save data from SIF...
(bootloader) Update partition data to SIF partition
(bootloader) Update partition data from original MSC...
(bootloader) [MSG] OKAY
OKAY [ 0.190s]finished. total time: 0.190s
[~/endeavory] fastboot flash zip firmware.zip [13:15]
sending 'zip' (12876 KB)...
OKAY [ 1.757s]
writing 'zip'...
(bootloader) adopting the signature contained in this image...
(bootloader) signature checking...
(bootloader) checking model ID...
(bootloader) checking custom ID...
(bootloader) checking main version...
(bootloader) checking hboot version...
(bootloader) start image[hboot] unzipping for pre-update check...
(bootloader) start image[hboot] flushing...
(bootloader) signature checking...
FAILED (remote: 90 hboot pre-update! please flush image again immediately)
finished. total time: 5.116s
[~/endeavory] fastboot flash zip firmware.zip [13:15]
< waiting for device >
sending 'zip' (12876 KB)...
OKAY [ 1.661s]
writing 'zip'...
(bootloader) adopting the signature contained in this image...
(bootloader) signature checking...
(bootloader) checking model ID...
(bootloader) checking custom ID...
(bootloader) checking main version...
(bootloader) checking hboot version...
(bootloader) start image[boot] unzipping & flushing...
(bootloader) Format partition LNX done
(bootloader) [RUU]WP,boot,100
(bootloader) start image[recovery] unzipping & flushing...
(bootloader) Format partition SOS done
(bootloader) [RUU]WP,recovery,100
(bootloader) ERASE backup cid
OKAY [ 3.176s]
finished. total time: 4.837s
[~/endeavory] fastboot flash unlocktoken
Unlock_code.bin [13:16]
sending 'unlocktoken' (0 KB)...
OKAY [ 0.021s]
writing 'unlocktoken'...
(bootloader) unlock token check successfully
What I'm seeing right now is a black screen with a htc logo and a full green status bar. It's been this way for a while.
What should I do? Is it safe to terminate the unlock command?
Yeah press ctrl+c and reboot phone.
Sent from my One X using xda premium
All right, I'm happily using HBOOT 1.39 now with a CyanogenMod nightly running, and ready to explore this supermarket of excitement and possibility.
I terminated the process and rebooted, which worked fine, and flashed boot.img and CWM and then CM from recovery.
Thanks again to all of you.
I've been trying to upgrade my phone to 2.12 or 2.22.
At the first my issues were because I was not S-Off but i solved that problem.
Now, when i try to flash the file I get this
(bootloader) checking model ID...
FAILED (remote: 41 model id check fail)
Searching on the internet I found that obviously I have the wrong file (duh!). But my question is, how do I know what model I have?
I have always thought I have the International model. I bought it from Amazon "HTC One M8 factory unlocked - 32GB".
What is the exact file I need then?
try to get fastboot getvar all and past it (excluding ur imei)
I finally did it. I was missing the superCID.
But even though it was succesful i still show the same old Build number. However the baseband changed to 1.19.21331147A....
Did I get the upgrade?
pinktheater said:
I finally did it. I was missing the superCID.
But even though it was succesful i still show the same old Build number. However the baseband changed to 1.19.21331147A....
Did I get the upgrade?
Click to expand...
Click to collapse
I think you need to do it twice, 1st time updates the HBOOT, 2nd time does everything else?
No is not that. I have tried the upgrade 3 times already.
It finishes OK:
(bootloader) start image[rcdata] unzipping & flushing...
(bootloader) ...... Successful
(bootloader) current_image_number=15
OKAY [ 61.177s]
finished. total time: 64.034s
C:\adb>
But then I go to my phone and I still see this:
One question, if I download the OTA file, the upgrade process is the same? (Using adb/fastboot commands to flash a zip)
Hello , please help , I unlock bootloader flash TWRP 2.7.0.2 , root , after update to TWRP 3.0.0.2 , and go to recovery stays on the screen , some solution
You can't use TWRP 3.x.x.x when your hboot is lower than 3.19.0000
or lower than lollipop firmware
Install TWRP 2.8.x.x
ckpv5 said:
You can't use TWRP 3.x.x.x when your hboot is lower than 3.19.0000
or lower than lollipop firmware
Install TWRP 2.8.x.x
Click to expand...
Click to collapse
The same happens when I install 2.8.4.0 , and when I install any rom does not give me the animation start , nothing but the same screen until it comes to system
TWRP 2.8.4.0 & above is meant for firmware 4.x
If your firmware is 1.x & 2.x, use 2.8.1.0
If your firmware is 3.x, use 2.8.3.0
See simple guide here : http://forum.xda-developers.com/htc-one-m8/help/tutorial-how-to-stock-stock-twrp-t3086860
Can you post fastboot getvar all result (without serial & imei no.) then we'll see what is best for you.
ckpv5 said:
TWRP 2.8.4.0 & above is meant for firmware 4.x
If your firmware is 1.x & 2.x, use 2.8.1.0
If your firmware is 3.x, use 2.8.3.0
See simple guide here : http://forum.xda-developers.com/htc-one-m8/help/tutorial-how-to-stock-stock-twrp-t3086860
Can you post fastboot getvar all result (without serial & imei no.) then we'll see what is best for you.
Click to expand...
Click to collapse
You can restore a backup TWRP lollipop with this firmware kitkat ?Cid HTC _332 for example el 4.32.600.2,thanks
No.. you need to restore 1.12.600.20 backup and update to 4.32.600.2 then later update to Marshmallow 6.17.600.3
Install TWRP 2.8.1.0
Restore 1.12.600.20 backup
Install stock recovery 4.32.600.2
Do OTA
Everything that you need are in my backup thread that I linked above
ckpv5 said:
No.. you need to restore 1.12.600.20 backup and update to 4.32.600.2 then later update to Marshmallow 6.17.600.3
Install TWRP 2.8.1.0
Restore 1.12.600.20 backup
Install stock recovery 4.32.600.2
Do OTA
Everything that you need are in my backup thread that I linked above
Click to expand...
Click to collapse
but I 'm s -on and here in Mexico no update to MM via Ota
vences31 said:
but I 'm s -on and here in Mexico no update to MM via Ota
Click to expand...
Click to collapse
Backup and recovery flash stock you suggested , to download the update via OTA lollipop and restarts to install and stays on the white screen with HTC logo , do I have root not know if this is the error ?
Make sure you don't accept root when asked by TWRP.
After OTA is downloaded, let the system install it, no manual install. The first boot will take time.
ckpv5 said:
Make sure you don't accept root when asked by TWRP.
After OTA is downloaded, let the system install it, no manual install. The first boot will take time.
Click to expand...
Click to collapse
but the image of the phone does not appear installing the update
After you restore 1.12.600.20 backup & install 4.32.600.2 stock recovery, the phone booted fine ?
When doing restore, you wipe all cache, dalvik-cache, data & system ? And you restore all boot, data & system ?
Let's say it booted fine, then you check OTA, download & let system install, then it should boot to recovery ... but instead of going to recovery, it get stuck on white screen.. is this what happening ?
Press both power + volume up buttons to reboot the device and try redo the process.
ckpv5 said:
After you restore 1.12.600.20 backup & install 4.32.600.2 stock recovery, the phone booted fine ?
When doing restore, you wipe all cache, dalvik-cache, data & system ? And you restore all boot, data & system ?
Let's say it booted fine, then you check OTA, download & let system install, then it should boot to recovery ... but instead of going to recovery, it get stuck on white screen.. is this what happening ?
Click to expand...
Click to collapse
Yes...try again
If this is not successful .. I'll write another method later tonight.
I have to go now ... will be around after 12 hours
ckpv5 said:
If this is not successful .. I'll write another method later tonight.
I have to go now ... will be around after 12 hours
Click to expand...
Click to collapse
and because if I install a custom rom 6.0.1 does not give me the boot animation and wifi when entering the system is switched off screen,thanks for your time
vences31 said:
and because if I install a custom rom 6.0.1 does not give me the boot animation and wifi when entering the system is switched off screen,thanks for your time
Click to expand...
Click to collapse
That's because your current firmware is too low to handle a 6.0.x custom ROM
I really don't get it why you can't update. Had the same experience before with someone else but the problem was down to not following the guide accordingly.
http://forum.xda-developers.com/showpost.php?p=64730207&postcount=683
You said before, if you install TWRP 2.8.4.0, you can boot to recovery ? If yes, I'll give you another way as your intention is to install custom ROM
ckpv5 said:
That's because your current firmware is too low to handle a 6.0.x custom ROM
I really don't get it why you can't update. Had the same experience before with someone else but the problem was down to not following the guide accordingly.
http://forum.xda-developers.com/showpost.php?p=64730207&postcount=683
You said before, if you install TWRP 2.8.4.0, you can boot to recovery ? If yes, I'll give you another way as your intention is to install custom ROM
Click to expand...
Click to collapse
I want to have Android 6.0 functional either official or custom ROM , or at least spend KitKat , if there are other ways please shares , Eh understood many things thanks to you and now I understand , with other devices I've had it was easier but this has been difficult
You're on KiKat now.. I'm preparing files for you to manually update to lollipop.
Once done, I want you to try to update to Marshmallow. If no success, I'll tell how to manually update to Marshmallow after you tried system update.
This will involve relocking bootloader assuming your device is S-On (you don't give fastboot getvar all result that I asked before)
1. Install TWRP 2.8.4.0 (as you said this is the highest TWRP version that you can install and can boot to it)
2. Download the 4.32.600.2 backup and restore - http://forum.xda-developers.com/htc-one-m8/help/tutorial-how-to-stock-stock-twrp-t3086860
(just follow the steps as in the guide 1-10 only, skip the rest)
3. Download fw_4.32.600.2.zip - https://sourceforge.net/projects/htconem8/files/fw_4.32.600.2.zip/download
4. Install the firmware
1. If the bootloader is UNLOCKED (for S-On device only), relock it with commands:
fastboot oem lock
fastboot reboot-bootloader
If the bootloader is LOCKED or RELOCKED, skip the above.
2. Put the device in bootloader/fastboot mode and connect to PC, run these commands
fastboot oem rebootRUU
fastboot flash zip fw_4.32.600.2.zip
you'll see ERROR/FAILED, repeat
fastboot flash zip fw_4.32.600.2.zip
fastboot reboot-bootloader
You should see the OS written 4.32.600.2 (in green color) on the bootloader.
Now reboot the device .. once the setup completed, check OTA. You should have 6.17.600.3 OTA, download and let system install.
Once the OTA installation is completed and phone rebooted to OS ... you now have a Marshmallow updated firmware & ROM.
You can unlock bootloader again with unlock_code.bin that you received from HTC or apply a new one.
Once unlocked, install TWRP 3.0.2-0, you can install any custom ROM that you like
ckpv5 said:
You're on KiKat now.. I'm preparing files for you to manually update to lollipop.
Once done, I want you to try to update to Marshmallow. If no success, I'll tell how to manually update to Marshmallow after you tried system update.
This will involve relocking bootloader assuming your device is S-On (you don't give fastboot getvar all result that I asked before)
1. Install TWRP 2.8.4.0 (as you said this is the highest TWRP version that you can install and can boot to it)
2. Download the 4.32.600.2 backup and restore - http://forum.xda-developers.com/htc-one-m8/help/tutorial-how-to-stock-stock-twrp-t3086860
(just follow the steps as in the guide 1-10 only, skip the rest)
3. Download fw_4.32.600.2.zip - https://sourceforge.net/projects/htconem8/files/fw_4.32.600.2.zip/download
4. Install the firmware
1. If the bootloader is UNLOCKED (for S-On device only), relock it with commands:
fastboot oem lock
fastboot reboot-bootloader
If the bootloader is LOCKED or RELOCKED, skip the above.
2. Put the device in bootloader/fastboot mode and connect to PC, run these commands
fastboot oem rebootRUU
fastboot flash zip fw_4.32.600.2.zip
you'll see ERROR/FAILED, repeat
fastboot flash zip fw_4.32.600.2.zip
fastboot reboot-bootloader
You should see the OS written 4.32.600.2 (in green color) on the bootloader.
Now reboot the device .. once the setup completed, check OTA. You should have 6.17.600.3 OTA, download and let system install.
Once the OTA installation is completed and phone rebooted to OS ... you now have a Marshmallow updated firmware & ROM.
You can unlock bootloader again with unlock_code.bin that you received from HTC or apply a new one.
Once unlocked, install TWRP 3.0.2-0, you can install any custom ROM that you like
Click to expand...
Click to collapse
I have to let you start 4.32.xxx After restoring the device. ? , He asked that the hboot 3.16.xxx I have is only for the version of KitKat?*
Don't start after restore 4.32.600.2, only boot to bootloader to install 4.32.600.2 firmware. This will get you to hboot 3.18.0000
Only after you installed firmware then only you can restart.
If this also you cannot follow the guide, I don't know how else to help you.
My first guide should be the easiest way but you keep saying it didn't boot. I believe because the guide was not followed accordingly.
@joikep - are you still around ? If yes, maybe you can help as it seems we have language barrier here.
ckpv5 said:
Don't start after restore 4.32.600.2, only boot to bootloader to install 4.32.600.2 firmware. This will get you to hboot 3.18.0000
Only after you installed firmware then only you can restart.
If this also you cannot follow the guide, I don't know how else to help you.
My first guide should be the easiest way but you keep saying it didn't boot. I believe because the guide was not followed accordingly.
@joikep - are you still around ? If yes, maybe you can help as it seems we have language barrier here.
Click to expand...
Click to collapse
if properly flash the firmware? , or failed normal? I appear in red letters 4.32.600.2 in bootloader , but start system , signal device is connected , but disconnects wifi and on every moment
(bootloader) [PGFS] partition_update_pgfs: pg1fs_security
(bootloader) Lock successfully...
(bootloader) deinit_lcd
(bootloader) mipi display off
(bootloader) mdp_clock_off
(bootloader) disable_mmss_clk done
(bootloader) pll1_disable done
(bootloader) TZ_HTC_SVC_DISABLE ret = 536739196 (0x1FFDFD7C)
(bootloader) [CRITICAL] SPMI write command failure: cmd_id =
0, error
(bootloader) = 4
(bootloader) [CRITICAL] SPMI write command failure: cmd_id =
0, error
(bootloader) = 4
(bootloader) [INFO] Rebooting device
FAILED (status read failed (No such file or directory))
finished. total time: 1.376s
C:\Users\mauricio\Downloads\One_M8_All-In-One_Kit_v\Data>fastboot oem rebootRUU
...
(bootloader) Start Verify: 3
OKAY [ 0.031s]
finished. total time: 0.128s
C:\Users\mauricio\Downloads\One_M8_All-In-One_Kit_v\Data>fastboot flash fw_4.32.
600.2.zip
unknown partition 'fw_4.32.600.2.zip'
error: cannot determine image filename for 'fw_4.32.600.2.zip'
C:\Users\mauricio\Downloads\One_M8_All-In-One_Kit_v\Data>fastboot flash zip fw_4
.32.600.2.zip
target reported max download size of 1830711296 bytes
sending 'zip' (52971 KB)...
OKAY [ 2.455s]
writing 'zip'...
(bootloader) adopting the signature contained in this image...
(bootloader) signature checking...
(bootloader) zip header checking...
(bootloader) zip info parsing...
(bootloader) checking model ID...
(bootloader) checking custom ID...
(bootloader) checking main version...
(bootloader) checking hboot version...
(bootloader) start image[hboot] unzipping for pre-update check...
(bootloader) start image[hboot] flushing...
(bootloader) signature checking...
(bootloader) [RUU]WP,hboot,0
(bootloader) [RUU]WP,hboot,99
(bootloader) [RUU]WP,hboot,100
(bootloader) ...... Successful
FAILED (remote: 90 hboot pre-update! please flush image again immediately)
finished. total time: 8.354s
C:\Users\mauricio\Downloads\One_M8_All-In-One_Kit_v\Data>fastboot reboot-bootloa
der
rebooting into bootloader...
OKAY [ 0.016s]
finished. total time: 0.109
SOLVED UPDATE: I did some more reading. I took the Bell (BM) rom zip
(named "0PJAIMG_HIMA_UL_L50_SENSE70_ATT_BM_1.32.666.6_R2_Radio_01.01_U11440221_59.04.50303G_2_F_release_426170_signed.zip"), and renamed it to "0PJAIMG.zip".
Copied that to the root of a microSD card and put that into the phone.
Booted phone with VOLDOWN+POWER and the flash process began. It rebooted a couple of times during the process. It said to hit POWER to finish. After that, phone booted normally (like out-of-the-box again).
With that said, I still would like to have root... so would still appreciate any input as to what I did wrong below. Thank you!
Hello. I'm afraid I have messed my phone up a bit, and would really appreciate it if someone could help me out.
It's a Bell HTC One M9 (0PJA110), and it is (was?) on 5.0.2 Lollipop. According to the RUU EXE I just tried (unsuccessfully), it says it is an image version (or HTC system version) 1.32.666.6.
Here's what I did, from out-of-the-box. I just wanted root access so I could use Titanium Backup, so I read a bunch of threads to get started. I thought I had gathered enough knowledge, so I:
1) Unlocked bootloader via htcdev
2) Flashed "htc-one-m9-lollipop-twrp-2.8.7.0-hima.img" to recovery. (I chose this version because I read in some threads that version 3 or higher of twrp doesn't work well if it is flashed to a Lollipop phone).
3) Rebooted, went immediately into recovery (so that TWRP could ensure it doesn't get overwritten)
4) Then rebooted again, and went into recovery (to make sure TWRP was still there)
5) At this point, I should have let the phone boot normally, to make sure that was OK. But I did not... so I cannot tell if this is where my trouble began
6) Next, in TWRP, I flashed "SR1-SuperSU-v2.79-SR1-20161221223537.zip". It seemed to go well.
7) Reboot from TWRP.
8) Phone shows first HTC logo, then goes to a black screen (black but illuminated). That's it.
My next thing to try was this Bell TWRP zip from a nice post on here. Filename is "Stock_Bell_LP_5.0.1_1.32.666.30_TWRP.zip". I tried to flash it via TWRP but it failed right away (I do not have the exact output but can try again to get the text, it if that helps).
Naturally I was starting to get worried, so I immediately started looking for RUU's so I could start over.
1) I re-locked bootloader
2) I tried a generic RUU ("RUU_HIMA_UL_M60_SENSE70_ATT_MR_NA_Gen_Unlock_3.35.617.31.exe") but it would not flash - I assume it is checking CID and knows it's not correct for my phone
3) I downloaded a Bell-specific zip from Androidruu ("0PJAIMG_HIMA_UL_L50_SENSE70_ATT_BM_1.32.666.6_R2_Radio_01.01_U11440221_59.04.50303G_2_F_release_426170_signed.zip", verified the MD5 matched whatever androidruu.com said it was.
4) Renamed the zip to rom.zip to make the next commands easier
5) Ran "fastboot oem rebootRUU", verified the RUU screen appeared, then "fastboot flash zip rom.zip"
It didn't work Here is the output:
Code:
target reported max download size of 800000000 bytes
Invalid sparse file format at header magi
sending sparse 'zip' (67085 KB)...
OKAY [ 4.791s]
writing 'zip'...
(bootloader) HOSD CL#493992
(bootloader) ERR [SD_UPDATE_ERR] update_fb_ZIP_buf: can not find ZIP hea
(bootloader) der
(bootloader) ERR [SD_UPDATE_ERR] sddownload failed: 22
(bootloader) ERR Update zip file failed.
(bootloader) ERR ZIP ERROR, exit read zip loop
(bootloader) ERR ZIP signature checking failed...
(bootloader) Update zip file OK
(bootloader) ERR ZIP ERROR CODE, 22
(bootloader) [email protected]
FAILED (remote: 22: fail to flash via downloadzip)
finished. total time: 8.552s
I wish I could try a Bell RUU exe... but I am having a hell of a time finding one.
Any advice would be appreciated (regarding anything I did wrong up above, or regarding how I can get myself out of this mess). Thank you for reading.
Download the latest RUU to your device. In dowload mode type fastboot oem rebootRUU. Entering the Htc screen, run RUU.exe.
Dark Stranger said:
Download the latest RUU to your device. In dowload mode type fastboot oem rebootRUU. Entering the Htc screen, run RUU.exe.
Click to expand...
Click to collapse
Thank you, but same result as my earlier attempt. The EXE itself can get the phone from bootloader mode/download mode into RUU mode, and it starts the process, but fails with "please get the correct rom update utility".
I assume it's because this RUU is not an exact match for my phone.
Hi,
I had tried rooting my At&T HTC One M9 using the NOOB friendly guide written by KingInTheNorth. After completing, my phone wouldn't boot up. It got into a bootloop. I then found a guide (from another website) on how to reload the stock RUU. I followed the direction but it looks as if the file was bad. The following is copied from the command prompt.
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash zip C:/Use
Downloads/M9fullstock.zip
target reported max download size of 800000000 bytes
sending 'zip' (79642 KB)...
OKAY [ 5.185s]
writing 'zip'...
(bootloader) HOSD CL#682052
(bootloader) GPT is up-to-dated. [17408]
(bootloader) Perform pre-update
(bootloader) ERR ZIP signature checking failed...
(bootloader) ERR [SD_UPDATE_ERR] Not allow flash image except boot/recov
(bootloader) ery/system
(bootloader) ERR [SD_UPDATE_ERR] sddownload failed: 14
(bootloader) ERR Update zip file failed.
(bootloader) Update zip file OK
(bootloader) ERR ZIP ERROR CODE, 14
(bootloader) [email protected]
FAILED (remote: 14 RU_ZIP_INFO_ERROR android-info missing or malformed )
finished. total time: 8.400s
Now my phone is stuck on the screen that shows a phone with a green arrow in a green circle pointing down. I've tried rebooting but it doesn't respond to any button presses. Did I ruin my phone? Can anyone help?
Try to type fastboot reboot in your command prompt. It should reboot your phone. If you're lucky it will reboot your phone normally and it's fully functional. If not, your phone will boot into bootloader which will mean your rom is wiped.
That's not a RUU that you were trying to flash and the guide written by KingInTheNorth is outdated since different firmware versions of the M9 can only get rooted with different versions of SuperSU. Check the ReadMe thread for the guides and files you may need.
@Suurbier91: Never recommend people to reboot if a flash failed unless they know exactly what's going on. There are some flashing errors that can only get fixed if the phone gets flashed immediately, again. A reboot makes those bricks permanent and unrecoverable.
Thanks for the direct to the Read Me. I've found a lot of good information there. After my battery died, I charged the phone and it's coming back on. It still has a boot loop that lasts for between five to ten minutes before booting up. I am going to try following one of the threads I found on here to get back to stock. Hopefully that will take care of the boot loop issue. I was wanted to root it so I could upgrade to Nougat. The phone was originally AT&T but I paid to unlock it and I'm now on Cricket but I don't receive any OTA updates.
That's probably so because the phone is only sim unlocked but still using the AT&T firmware. Don't ask me why they're allowed to do so (it wouldn't be possible in the EU) but AT&T won't let you download OTAs if there isn't an AT&T sim card inserted into your phone.
If you don't need the AT&T branded firmware then I'd get S-OFF and convert my phone to the dev edition if I were you. If you choose to stay on the AT&T firmware then you can update your phone via a RUU. Be aware that it's not possible to update from firmware 3.x or lower to firmware 4.x via RUUs due to new encryption keys.
Sent from my HTC One M9 using XDA Labs