Related
Any time I try to flash a rom that is sense based my phone instead of booting like a normal phone it boots to the HTC screen then restarts and boots into TWRP. Anyone know of a fix? I tried to wipe system, data, cache and dalvik cache but nothing works.
EDIT: When I try to install the stock rom it says some symlinks failed and error executing updater binary in zip
are you using a GPE phone if you are the partitions are a bit different and you have to go through the process of converting your phone.
syaoran68 said:
are you using a GPE phone if you are the partitions are a bit different and you have to go through the process of converting your phone.
Click to expand...
Click to collapse
It is from ATT, it had sense stock but I accidentally formatted the entire phone now my hboot screen looks different. it is black with a droid in the middle instead of white with the droids on skateboards. and the splash screen has a small black unlocked lock at the bottom instead of the normal htc splash.
Rye Cribby Tree said:
It is from ATT, it had sense stock but I accidentally formatted the entire phone now my hboot screen looks different. it is black with a droid in the middle instead of white with the droids on skateboards. and the splash screen has a small black unlocked lock at the bottom instead of the normal htc splash.
Click to expand...
Click to collapse
What did you do to "format" it?
redpoint73 said:
What did you do to "format" it?
Click to expand...
Click to collapse
I ticked all the boxes in twrp and deleted everything.
I think you installed a GPE firmware, you'll need to find a rolled up (rather than an OTA) Sense firmware for your device. I take it you're S-Off?
BenPope said:
I think you installed a GPE firmware, you'll need to find a rolled up (rather than an OTA) Sense firmware for your device. I take it you're S-Off?
Click to expand...
Click to collapse
Nah, firewater doesn't work for me unfortunately.
Rye Cribby Tree said:
It is from ATT, it had sense stock but I accidentally formatted the entire phone now my hboot screen looks different. it is black with a droid in the middle instead of white with the droids on skateboards. and the splash screen has a small black unlocked lock at the bottom instead of the normal htc splash.
Click to expand...
Click to collapse
Rye Cribby Tree said:
Nah, firewater doesn't work for me unfortunately.
Click to expand...
Click to collapse
I don't know what's going on. Unless I'm mistaken, that sounds like the GPE boot screen, which you could only flash if you're S-Off.
BenPope said:
I don't know what's going on. Unless I'm mistaken, that sounds like the GPE boot screen, which you could only flash if you're S-Off.
Click to expand...
Click to collapse
I can flash GPE roms fine.
Rye Cribby Tree said:
I can flash GPE roms fine.
Click to expand...
Click to collapse
My point is that as far as I know, the splash screen is in the firmware. You would need to be S-Off to flash that firmware. Anyway, I can't help.
If that is in fact the GPEboot splash (I'm not that familiar with GPE) you should still be able to get into bootloader, you might just be doing the button combo wrong. Nothing you wiped affects hboot; nor can it be overwritten with s-on (aside from a signed hboot for your version).
Hold down the Power and vol up button to force the phone to reboot. The moment the screen goes dark, let go of vol up, and hold vol down until you see the hboot screen. If you see any screen but the white hboot screen, you probably just pressed vol down too late, or let go of it too early.
Or adb reboot bootloader.
redpoint73 said:
If that is in fact the GPEboot splash (I'm not that familiar with GPE) you should still be able to get into bootloader, you might just be doing the button combo wrong. Nothing you wiped affects hboot; nor can it be overwritten with s-on (aside from a signed hboot for your version).
Hold down the Power and vol up button to force the phone to reboot. The moment the screen goes dark, let go of vol up, and hold vol down until you see the hboot screen. If you see any screen but the white hboot screen, you probably just pressed vol down too late, or let go of it too early.
Or adb reboot bootloader.
Click to expand...
Click to collapse
This is what it looks like.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
But it use to look like this
Wow, strange. As I mentioned, I'm not that familiar with GPE, but it must have a different hboot (not a splash screen like the other responses was suggesting). You shouldn't be able to change hboot with s-on.
So did you try to do a GPE conversion? As I mentioned, nothing in TWRP could have caused this.
This also explains why you can't install/boot Sense ROMs. As another mentioned, the GPE partitioning is different, so that prevents Sense ROMs from running.
What version/carrier do you have?
redpoint73 said:
Wow, strange. As I mentioned, I'm not that familiar with GPE, but it must have a different hboot (not a splash screen like the other responses was suggesting). You shouldn't be able to change hboot with s-on.
So did you try to do a GPE conversion? As I mentioned, nothing in TWRP could have caused this.
This also explains why you can't install/boot Sense ROMs. As another mentioned, the GPE partitioning is different, so that prevents Sense ROMs from running.
What version/carrier do you have?
Click to expand...
Click to collapse
AT&T, I flashed a stock recovery to try and get OTA's from a GPE rom and it soft bricked my phone. After that all the changes happened. Also the splash screen when you first boot the phone has a small unlocked lock picture at the bottom. It looks like this but under powered by android is a little lock.
Rye Cribby Tree said:
This is what it looks like.http://www.htc1guru.com/wp-content/uploads/2013/08/39DarkBootloader.jpg[
/IMG][/QUOTE]
That says M7_UL... Are you just indicating colour scheme?
Click to expand...
Click to collapse
BenPope said:
That says M7_UL... Are you just indicating colour scheme?
Click to expand...
Click to collapse
Yeah, I was just talking about the image on the phone.
I am in the same boat as the OP. Did the GPE conversion with S-On somehow and here I am stuck with GPe and AOSP ROMs only
The Colorscene is nothing to worry. GPE-HTC phones have always been black (Black Hboot = GPE; White = HTC)
Have you tried to use a superCID and flash the first one (iirc 1.54...)Rom? Got that working on my old M7
@fromeo85, how was you able to convert your device to GPE with S-On? I mean, you have to change the CID to GOOGL001, which obviously just works if you are S-Off
I'm pretty much in the same boat as a few others here - except I know exactly where I went wrong and learned a valuable lesson.....
Before I started all this, I had S-OFF, Root and running ViperOne on my M8
Wanted to try out a AOSP Rom and used a 4.4.3 GPE ROM, which flashed successfully (not sure how, it shouldn't have).
Once the M8 was running 4.4.3 GPE, it prompted for an update to 4.4.4 which I accepted. The update failed and booted into TWRP instead. I was overly determined to get 4.4.4 installed (should have left it alone at this point instead)
I rebooted into bootloader and very very stupidly, flashed the GPE recovery, rebooted and accepted the install to 4.4.4.
This boot looped my phone, corrupted internal storage, and reapplied security (S-On).
I was able to get internal storage cleared up and successfully installed CM11 so at least I'm booting something and its not bricked.
At this point, I'm back to a bootable state with CM11 - but can't return to Sense. I've tried to install InsertCoin and ViperOne - both fail towards the end of installation - writing permissions and installing busybox - same with restoring ROM via recovery. Also, the original GPE ROM fails installation, but doesn't give any errors.
I've tried to S-Off with revone, firewater, SunShine and rumrunner - all fail. I need S-Off to get HBoot back to a version that can boot Sense or open up security so a Sense based ROM can install successfully. Also tried to SuperCID, which requires S-OFF so that fails as well.
So I'm stuck with:
- S-On
- version-bootloader: 3.18.0.0000
- version-baseband: 1.14.21331931.LA02_2G
- modelid: 0P6B13000
- cidnum: T-MOB010
I've tried flashing current (and previous versions) stock Firmware and using different versions of RUU but all fail with hboot version check failed and S-On. Flashing GPE 4.4.x (4.4.3 and 4.4.4) firmware fail as well but cant remember the exact error off the top of my head.
I'm at a loss.. Over the years I've read plenty of tutorials and have a pretty decent understanding of the Android ROM ecosystem. I've searched all over to no avail. If the GPE Recovery and/or 4.4.4 Update would have left Security Off, I wouldn't have any issues since I could flash firmware or HBoot and install ViperOne or any other Sense based ROMs....
I've been racking my brain trying to fix this for 2 days now so I've come here for a bit of help... I've tried to list all my troubleshooting steps in here, but I know I've missed some
Any ideas?? One thing that would really come in handy right now is one of the several S-Off methods to work on AOSP Roms.
CorzCorry said:
@fromeo85, how was you able to convert your device to GPE with S-On? I mean, you have to change the CID to GOOGL001, which obviously just works if you are S-Off
Click to expand...
Click to collapse
@CorzCorry I am not entirely sure but I ended up using Sunshine to gain S-Off when I was on the stock GPE ROM and everything is golden now. Though I am sticking with GPE since I prefer a vanilla experience over any OEM UI overlay.
I hope that someone can help me with this problem. Sorry it is such a long post, but I thought it might help with diagnosis if I wrote it all down.
I have an HTC One X with Android 4.02. It was purchased from Optus. I followed the process on the HTC web site to root and unlock the phone. Since that time I have never been able to update automatically. I contacted both Optus and HTC and was told that this was because of the root and, more or less, “bad luck!” I’ve tried to manually update the zip file with CWM but just get an error message and abort update.
From time to time, the phone would lag badly and run slower and slower. The only way that I could fix it was to backup all the apps and data using Titanium backup; uninstall all the apps; and then re-install them. Afterwards, all would be fine again for several months. A couple of months ago, it began to happen again and I uninstalled/reinstalled, but this time it didn’t help. Finally, after trying to figure out what to do, I did a system reset and then reinstalled everything and everything worked fine except that one of my apps (one I use all the time!) now will not work at all.
I decided that this might be because I needed to update to a newer version of Android. Unfortunately, when I tried to install CM 10.2, the installation failed. I thought that this might be because the Bootloader was too old (v. 0.95) but I read that if it was an AOSP Rom that I wouldn’t need to update the bootloader. So, I tried to flash Xenon, but again no luck. I’ve scoured the forums, but can’t seem to find anything that matches this issue.
The phone is definitely rooted. I’ve previously installed new Roms on my old HTC Desire, so I’m pretty sure I’m doing it right. However, I’m by no means a particularly sophisticated user and quite often the discussion in the forums is a bit esoteric for me.
Do I need to update the bootloader? If I do, then do I need to unroot the phone first then update then re-root?
Any ideas would be appreciated.
kosraeboy said:
I hope that someone can help me with this problem. Sorry it is such a long post, but I thought it might help with diagnosis if I wrote it all down.
I have an HTC One X with Android 4.02. It was purchased from Optus. I followed the process on the HTC web site to root and unlock the phone. Since that time I have never been able to update automatically. I contacted both Optus and HTC and was told that this was because of the root and, more or less, “bad luck!” I’ve tried to manually update the zip file with CWM but just get an error message and abort update.
From time to time, the phone would lag badly and run slower and slower. The only way that I could fix it was to backup all the apps and data using Titanium backup; uninstall all the apps; and then re-install them. Afterwards, all would be fine again for several months. A couple of months ago, it began to happen again and I uninstalled/reinstalled, but this time it didn’t help. Finally, after trying to figure out what to do, I did a system reset and then reinstalled everything and everything worked fine except that one of my apps (one I use all the time!) now will not work at all.
I decided that this might be because I needed to update to a newer version of Android. Unfortunately, when I tried to install CM 10.2, the installation failed. I thought that this might be because the Bootloader was too old (v. 0.95) but I read that if it was an AOSP Rom that I wouldn’t need to update the bootloader. So, I tried to flash Xenon, but again no luck. I’ve scoured the forums, but can’t seem to find anything that matches this issue.
The phone is definitely rooted. I’ve previously installed new Roms on my old HTC Desire, so I’m pretty sure I’m doing it right. However, I’m by no means a particularly sophisticated user and quite often the discussion in the forums is a bit esoteric for me.
Do I need to update the bootloader? If I do, then do I need to unroot the phone first then update then re-root?
Any ideas would be appreciated.
Click to expand...
Click to collapse
Hi
Can you give some details of the phone? CID?, international version?, S-On or off?, etc?
In short i think it is a good idea to update to a more recent bootloader. Then get yourself on to a newer ROM.
You might also want to consider twrp (big) as a new recovery.
This forum has lots of info.
Also take a look at www.onexroot.com
Thanks
The CID is OPTUS001.
The phone was purchased in Australia from the Optus network - I'm guessing then, that is an international.
The phone is S-on. From what I was reading when I was figuring out how to find whether it was On or Off, it seems like it needs to be Off to install any new Rom. I'd that right?
THanks for your help.
kosraeboy said:
The CID is OPTUS001.
The phone was purchased in Australia from the Optus network - I'm guessing then, that is an international.
The phone is S-on. From what I was reading when I was figuring out how to find whether it was On or Off, it seems like it needs to be Off to install any new Rom. I'd that right?
THanks for your help.
Click to expand...
Click to collapse
What is your error in CWM?
kosraeboy said:
The CID is OPTUS001.
The phone was purchased in Australia from the Optus network - I'm guessing then, that is an international.
The phone is S-on. From what I was reading when I was figuring out how to find whether it was On or Off, it seems like it needs to be Off to install any new Rom. I'd that right?
THanks for your help.
Click to expand...
Click to collapse
You can flash ROMs with S-ON. I fact its good to leave it as S-ON in case you flash the wrong firmware. Saved my bacon a few times.
Even if you bought it through Optus doesn't necessarily mean an international. Ca you post a screen shot of the boot loader screen. That will tell us.
Also an you find the CID number? There's some apps that can give you the the number. It looks like HTC-xyz. This will help in finding the right firmware.
good luck.
Noobdead said:
What is your error in CWM?
Click to expand...
Click to collapse
Hopefully this image works.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
grwalker said:
You can flash ROMs with S-ON. I fact its good to leave it as S-ON in case you flash the wrong firmware. Saved my bacon a few times.
Even if you bought it through Optus doesn't necessarily mean an international. Ca you post a screen shot of the boot loader screen. That will tell us.
Also an you find the CID number? There's some apps that can give you the the number. It looks like HTC-xyz. This will help in finding the right firmware.
good luck.
Click to expand...
Click to collapse
The CID Number is: OPTUS0001
Here is bootloader screen.
kosraeboy said:
The CID Number is: OPTUS0001
Here is bootloader screen.
Click to expand...
Click to collapse
Can you post the boot loader screen shot again please. The link didn't work
Trying again
I made a mistake with the CID. It is: OPTUS001
Hopefully this will work this time.
kosraeboy said:
I made a mistake with the CID. It is: OPTUS001
Hopefully this will work this time.
Click to expand...
Click to collapse
Nope, link still doesn't work. Use the attachments button when replying to attached the screenshot.
If that still doesn't work then let me know what the first three lines are when you are in fastboot mode. (Hold Vol down and power until you enter fastboot). The reason i want this info is to confirm you have the international version of HOX. If the second line contains the words "Endeavoru" then you have the international version, and we can then find the right ROM and recovery for you to use.
Also this is the link to download Hboot 1.36 for OPTUS001. http://d-h.st/users/ClydeB1/?fld_id=8110. Download this and keep it handy.
I am assuming that your bootloader is unlocked. First line tells you this. Did you use the site http://www.htcdev.com/bootloader/? Do you still have the unlock token?
Here are the first 9 lines. Don't know why it doesn't work.
*** UNLOCKED ***
ENDEAVORU PVT SsiteHIP S-ON RL
HBOOT-0.95.0000
CPLD-None
MICROP-None
RADIO-None
eMMC-bootmode : disabled
CPU-bootmode : disabled
HW Secure boot : enabled
Unlocked with htcdev.com. I no longer have the token, but can I get it by logging into htcdev site?
I'll download the firmware.zip file.
Thanks
kosraeboy said:
Here are the first 9 lines. Don't know why it doesn't work.
*** UNLOCKED ***
ENDEAVORU PVT SsiteHIP S-ON RL
HBOOT-0.95.0000
CPLD-None
MICROP-None
RADIO-None
eMMC-bootmode : disabled
CPU-bootmode : disabled
HW Secure boot : enabled
Unlocked with htcdev.com. I no longer have the token, but can I get it by logging into htcdev site?
I'll download the firmware.zip file.
Thanks
Click to expand...
Click to collapse
Man give me the result from command fastboot getvar version-main then I will tell you from where to download the RUU and you will download it and relock your bootloader and run it you are with low hboot and have chance to have RUU for your main version
kosraeboy said:
Here are the first 9 lines. Don't know why it doesn't work.
*** UNLOCKED ***
ENDEAVORU PVT SsiteHIP S-ON RL
HBOOT-0.95.0000
CPLD-None
MICROP-None
RADIO-None
eMMC-bootmode : disabled
CPU-bootmode : disabled
HW Secure boot : enabled
Unlocked with htcdev.com. I no longer have the token, but can I get it by logging into htcdev site?
I'll download the firmware.zip file.
Thanks
Click to expand...
Click to collapse
The unlock token usually arrives by email. Do you still have the email? If not go thru the process again and get the token. Then keep the token. You need it after you flash the firmware.zip (new HBOOT)
The question you might want to think about is what ROM are you planning to install? That suggests the custom recovery you need to install. For instance HOX international works well on Lollipop but you have to reformat the memory using twrp-big. A simple task that you can find on www.onexroot.com.
Once you answer the ROM question, the steps would be as follows. Instructions can be provided if needs be.
1. Flash custom recovery of your choice
2 Flash the firmware.zip (HBOOT)
3. Flash the ROM of your choise.
Or you can go down the path that Thant is suggesting. I did the Lollipop upgrade using Resurrection Remix ROM after doing steps 1 and 2.
Thanks
grwalker said:
The unlock token usually arrives by email. Do you still have the email? If not go thru the process again and get the token. Then keep the token. You need it after you flash the firmware.zip (new HBOOT)
The question you might want to think about is what ROM are you planning to install? That suggests the custom recovery you need to install. For instance HOX international works well on Lollipop but you have to reformat the memory using twrp-big. A simple task that you can find on www.onexroot.com.
Once you answer the ROM question, the steps would be as follows. Instructions can be provided if needs be.
1. Flash custom recovery of your choice
2 Flash the firmware.zip (HBOOT)
3. Flash the ROM of your choise.
Or you can go down the path that Thant is suggesting. I did the Lollipop upgrade using Resurrection Remix ROM after doing steps 1 and 2.
Thanks
Click to expand...
Click to collapse
Step 1 must to be after step 2, because if he flash firmware after recovery will be with stock recovery and not be possible to flash rom with stock recovery and must to flash again custom recovery. But how I think he is not a good with android devices don't have good skil to flash the firmware by him self. I suggest to answare my question and then to see if we can find RUU
Thank you both. Sorry for the delay in responding. Family emergency and I've not had time. I'll follow up in a day or so.
Sorry for the delay
Thant said:
Man give me the result from command fastboot getvar version-main then I will tell you from where to download the RUU and you will download it and relock your bootloader and run it you are with low hboot and have chance to have RUU for your main version
Click to expand...
Click to collapse
Hi Thant:
The result is: version-main: 1.29.980.11
kosraeboy said:
Hi Thant:
The result is: version-main: 1.29.980.11
Click to expand...
Click to collapse
OK Reloack with command fastboot oem lock your bootloader and run this RUU if you get error try to find nandroid backup I will try to find you stock recovery but first try to run the RUU and report back after that:fingers-crossed:
Thant said:
OK Reloack with command fastboot oem lock your bootloader and run this RUU if you get error try to find nandroid backup I will try to find you stock recovery but first try to run the RUU and report back after that:fingers-crossed:
Click to expand...
Click to collapse
Thanks. I'll try it and let you know.
I've tried running the RUU. When it asks me to verify the ROM image version I want to update, the "To:"version is the same as the "From:"version. They are both 1.28.980.11 Before I go ahead, is that correct? Shouldn't it be a different version of the ROM image?
kosraeboy said:
I've tried running the RUU. When it asks me to verify the ROM image version I want to update, the "To:"version is the same as the "From:"version. They are both 1.28.980.11 Before I go ahead, is that correct? Shouldn't it be a different version of the ROM image?
Click to expand...
Click to collapse
GO and see if the RUU will finish if yes this is good if give you error we will see what will do.
Yes they are the same but if RUU finish you will be complete stock and then will update wia Wi-Fi stock rom to latest hboot. Don't forget to relock your bootloader
replay if rUU finish and dont forget to make nandroid backup when you install new rom after update to latest hboot for your carrier
☆★☆ [7.0][FIRMWARE/RUU] Verizon HTC One M9 Nougat 4.49.605.16 Resources ☆★☆
Nougat for the Verizon HTC One M9
STOCK FIRMWARE ZIPS AND RUU
YOU MUST BE S-OFF TO USE ANY OF THESE FILES ***EXCEPT THE RUU
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
______________________________
Verizon Wireless is pleased to announce a software update for your device.
This software update has been tested to help optimize device performance, resolve known issues and apply the latest security patches.
Current Software Update Benefits
Software Version: 4.49.605.16
Android® Security Patch Level: 2017-11-01, including Krack security patch
Verizon Wireless is pleased to announce a new software update for your HTC One M9.
Android® 7.0 Nougat improves your mobile experience with new battery-smart features and multitasking enhancements.
This update also includes the latest Android security updates and bug fixes.
Use two apps at same time with multi-window view:
To activate multi-window view, touch and hold the Recent Apps button.
Whichever app you're currently using will go to the top of the screen on your HTC One M9, with a list of recent apps along the bottom.
Select the second app you want to use from the list.
Drag the divider to resize the app windows, or to maximize either active app.
Split-screen view:
Multitasking has never been easier, use 2 apps on screen at the same time.
To enable Split-screen mode (Portrait orientation):
Touch and hold the Recent Apps button.
Tap and hold the app you want to use and drag it to the top of your screen.
To use an app on the bottom screen:
Swipe up or down through your recent apps.
Tap the app you want to use.
If you have one app open, you can also switch to Split-screen view by tapping and holding the Recent Apps button, and your current app will move to the top half of the screen.
Data saver:
With Android Nougat on the HTC One M9, you can now enable Data Saver to restrict specific apps from using data in the background.
Under the Data Usage menu, open Data Saver and slide or tap it on.
You can then go through a list of apps installed on your device, and enable background data for each one you want.
Easier Settings app navigation:
When in Settings, you can quickly hop between various sections by dragging in from the left edge.
Settings are broken down into the same categories as the main list, but using the slide-out menu eliminates the need to tap the back button, scroll, and then select another setting category.
Quicker multi-tasking:
You can now double-tap the Recent Apps button to quickly switch between your two most recently used apps.
For example, if you're writing an email in Gmail™ but need to look something up, you can open Chrome™, find and copy a link, then double-tap the recent apps button and your HTC One M9 will switch back to Gmail.
Reply with speed:
You can now reply directly in notifications from apps like Facebook Messenger, Hangouts, or Messenger directly, so you can have a conversation without having to bounce between apps.
______________________________
FIRMWARE DOWNLOADS:
FIRMWARE ZIPS ARE IN POST #2
NO RED TEXT and FAUX LOCKED ABOOTS ARE IN POST #3http://forum.xda-developers.com/showpost.php?p=65358023&postcount=3http://forum.xda-developers.com/showpost.php?p=65358023&postcount=3
FULL SIGNED RUUs ARE IN POST #4 (can be used with S-Off and S-On)
ROM DOWNLOADS:
POSTED HERE
Standard Disclaimer:
Code:
You are aware that writing to your devices' partitions increases your risks.
You understand and agree that i cannot be held responsible for such or any other damages.
The flash process is theoretically safe and tested.
However you are the brains behind the wheel and you are solely responsible for the execution of the processes.
I will not accept any responsibility.
I only provide access to the files and the information and you choose to execute them or not.
You understand that you should not use any files from here, if you are not willing to accept the risk.
Rom and Firmware 101
XDA:DevDB Information
★ ☆ [6.0][FIRMWARE/RUU] Verizon HTC One M9 Nougat 4.49.605.16 Resources ☆ ★, ROM for the Verizon HTC One (M9)
Contributors
santod040
ROM OS Version: 7.x Nougat
ROM Kernel: Linux 3.10.x
Version Information
Status: Stable
Current Stable Version: 4.49.605.16
Stable Release Date: 2017-04-11
Created 2016-02-16
Last Updated 2018-01-26
Firmware zips
FIRMWARE
YOU MUST BE S-OFF TO USE ANY OF THESE FILES
How to manually flash firmware zips:
(sd card method also works, but I recommend fastboot)
Place the zip in your fastboot/adb directory on your computer.
Put the device in fastboot(bootloader) mode
(Volume down and power until menu appears, select bootloader using power button, Download Mode works as well on the m9)
Connect the device to the computer
Enter the following commands from terminal/command prompt in the fastboot directory, one at a time:
fastboot oem rebootRUU (this puts the device in RUU mode)
fastboot flash zip firmware.zip (rename file to firmware.zip to make it simple/optional)
It will say that the update did not finish, to flush again, so repeat the above step:
fastboot flash zip firmware.zip
Important: the flash process halts at around 75% to 90% on phone screen! This is normal and a safety precaution!
The last few percent is the reboot, which is NOT happening automatically, so you get a chance to check the console output before reboot to make sure it is safe to reboot!
The bar will only fill up to 100% once you type the following command:
Click to expand...
Click to collapse
fastboot reboot-bootloader (this reboots the device to bootloader)
If your current fastboot isn't working/throws errors, please use the HTC fastboot in the zip below:
HTC_fastboot.zip
Replace existing commands with the HTC_fastboot prefix.
So for example, instead of:
Code:
fastboot flash zip firmware.zip
You would do this instead:
Code:
HTC_fastboot flash zip firmware.zip
To be applied in RUU Mode/Fastboot flashable zips:
NOUGAT
4.49.605.16
4.49.605.16_NoBoot-NoRecovery_firmware.zip
(This is what MOST users should flash or the one right below this which includes the latest Twrp at time of posting)
4.49.605.16_NoBoot_TWRP3.2.1-0_firmware.zip
4.49.605.16_Stock_Recovery.zip
4.49.605.16_Stock_BootImg.zip
4.49.605.16_FULL_firmware.zip (WILL WIPE)
(contains stock recovery and stock boot.img and should not be flashed over a custom rom)
Older Files
NOUGAT
4.49.605.11
4.49.605.11_NoBoot-NoRecovery_firmware.zip
(This is what MOST users should flash or the one right below this which includes the latest Twrp at time of posting)
4.49.605.11_NoBoot_TWRP3.1.1-0_firmware.zip
4.49.605.11_Stock_Recovery.zip
4.49.605.11_Stock_BootImg.zip
4.49.605.11_FULL_firmware.zip (WILL WIPE)
(contains stock recovery and stock boot.img and should not be flashed over a custom rom)
Marshmallow
3.37.605.38
3.37.605.38_NoBoot-NoRecovery_firmware.zip
(This is what MOST users should flash or the one right below this which includes the latest Twrp at time of posting)
3.37.605.38_NoBoot_TWRP3.1.1-0_firmware.zip
3.37.605.38_Stock_Recovery.zip
3.37.605.38_Stock_BootImg.zip
3.37.605.38_FULL_firmware.zip (WILL WIPE)
(contains stock recovery and stock boot.img and should not be flashed over a custom rom)
3.37.605.28
3.37.605.28_NoBoot-NoRecovery_firmware.zip
(This is what MOST users should flash or the one right below this which includes the latest Twrp at time of posting)
3.37.605.28_NoBoot_TWRP3.1.0-0_firmware.zip
3.37.605.28_Stock_Recovery.zip
3.37.605.28_Stock_BootImg.zip
3.37.605.28_FULL_firmware.zip
(contains stock recovery and stock boot.img and should not be flashed over a custom rom)
3.37.605.19
3.37.605.19_NoBoot-NoRecovery_firmware.zip
(This is what MOST users should flash or the one right below this which includes the latest Twrp at time of posting)
3.37.605.19_NoBoot_TWRP3.0.2-0_firmware.zip
3.37.605.19_Stock_Recovery.zip
3.37.605.19_Stock_BootImg.zip
3.37.605.19_FULL_firmware.zip
(contains stock recovery and stock boot.img and should not be flashed over a custom rom)
3.37.605.17
3.37.605.17_NoBoot-NoRecovery_firmware.zip
(This is what MOST users should flash or the one right below this which includes the latest Twrp at time of posting)
3.37.605.17_NoBoot_TWRP3.0.2-0_firmware.zip
3.37.605.17_Stock_Recovery.zip
3.37.605.17_Stock_BootImg.zip
3.37.605.17_FULL_firmware.zip
(contains stock recovery and stock boot.img and should not be flashed over a custom rom)
3.37.605.15
3.37.605.15_NoBoot-NoRecovery_firmware.zip
(This is what MOST users should flash or the one right below this which includes the latest Twrp at time of posting)
3.37.605.15_NoBoot_TWRP3.0.2-0_firmware.zip
3.37.605.15_Stock_Recovery.zip
3.37.605.15_Stock_BootImg.zip
3.37.605.15_FULL_firmware.zip
(contains stock recovery and stock boot.img and should not be flashed over a custom rom, especially if it's not Marshmallow)
3.37.605.13
3.37.605.13_NoBoot-NoRecovery_firmware.zip
(This is what MOST users should flash or the one right below this which includes the latest Twrp at time of posting)
3.37.605.13_NoBoot_TWRP3.0.2-0_firmware.zip
3.37.605.13_Stock_Recovery.zip
3.37.605.13_Stock_BootImg.zip
3.37.605.13_FULL_firmware.zip
(contains stock recovery and stock boot.img and should not be flashed over a custom rom, especially if it's not Marshmallow)
3.37.605.7
3.37.605.7_NoBoot-NoRecovery_firmware.zip
(This is what MOST users should flash or the one right below this which includes the latest Twrp at time of posting)
3.37.605.7_NoBoot_TWRP3.0.0-1_firmware.zip
3.37.605.7_Stock_Recovery.zip
3.37.605.7_Stock_BootImg.zip
3.37.605.7_FULL_firmware.zip
(conatins stock recovery and stock boot.img and should not be flashed over a custom rom, especially if it's not Marshmallow)
To be applied in Stock Recovery:
3.37.605.7_OTAPkg.zip
For Developers Use:
nothing to see here....
[/SIZE]
No Red Text Aboots
Does the red development text on the splash screen bother you after unlocking your device?
If so, I have a modified hboot for you that takes care of it.
This was simply hex edited by me to remove the text from the screen, no other changes were made.
I have tested it and it is 100% proven to work without any side effects.
I originally did this for the Verizon Droid DNA and HTC One (m7) and was asked to do it for the One Max, Butterfly S, HTC One (m8), and now also the HTC One (m9).
FROM THIS >>>
TO THIS >>>
Let's get to it!
You must be S-Off to do this!
To Install:
Download your Modified aboot:
-No Red Text aboots-
3.37.605.28_NoRedText_aboot.zip
Old Files:
3.37.605.17_NoRedText_aboot.zip
3.37.605.15_NoRedText_aboot.zip
3.37.605.13_NoRedText_aboot.zip
3.37.605.7_NoRedText_aboot.zip
Since I initially posted these:
I had a couple requests for a modified hboot/aboot that shows the device as being Locked and S-On, while being completely unlocked and S-Off.
I went ahead and made that as per request and made it for several devices.
The process is the same as it is for the NoRedText aboot, with the exception of the filename.
These also have the red text removed, like the No Red Text aboots above.
-Faux Locked aboots: (not really Locked and S-on but appear that way)
3.37.605.28_FauxLocked_aboot.zip
Old Files:
3.37.605.17_FauxLocked_aboot.zip
3.37.605.15_FauxLocked_aboot.zip
3.37.605.13_FauxLocked_aboot.zip
3.37.605.7_FauxLocked_aboot.zip
__________________________
Ok, Now you have your aboot of choice, let's proceed:
Place the zip in your fastboot/adb directory on your computer.
Put the device in fastboot/Download mode
(Volume down and power until menu appears, select fastboot using power button)
Connect the device to the computer
Enter the following commands from terminal/command prompt in the fastboot directory, one at a time:
fastboot oem rebootRUU (this puts the device in RUU mode)
fastboot flash zip filename_aboot.zip (this flashes the modified aboot zip file)
Important: the flash process halts at around 75% to 90% on phone screen! This is normal and a safety precaution!
The last few percent is the reboot, which is NOT happening automatically, so you get a chance to check the console output before reboot to make sure it is safe to reboot!
The bar will only fill up to 100% once you type the following command:
fastboot reboot-bootloader (this reboots the device to bootloader)
That's it, you're done. You can now reboot and not see the red text anymore.
If you have any questions or issues, let me know.
Verizon Official M9 RUU Collection
4.49.605.16 Official Signed RUU
Android 7.0 Nougat
Verizon HTC One M9
This RUU may be used on S-Off and S-On devices
and
WILL WIPE
DOWNLOAD:
RUU:
0PJAIMG_HIMA_WL[email protected]70710_CNV_1.26_002_release_520623_combined_signed_2_4.zip
OLDER RUU'S
Android 7.0 Nougat
4.49.605.11 Official Signed RUU
Android 7.0 Nougat
Verizon HTC One M9
This RUU may be used on S-Off and S-On devices
and
WILL WIPE
DOWNLOAD:
RUU:
0PJAIMG_HIMA_WL[email protected]70710_CNV_1.26_002_release_511276_combined_signed_2_4.zip
Android 6.0 Marshmallow
This RUU may be used on S-Off and S-On devices
and
WILL WIPE .
3.37.605.38 Official Signed RUU
0PJAIMG_HIMA_WL[email protected]60105_CNV_1.26_002_release_508660_combined_signed_2_4.zip
3.37.605.19 Official Signed RUU
Android 6.0 Marshmallow
Verizon HTC One M9
This RUU may be used on S-Off and S-On devices .
RUU:
0PJAIMG_HIMA_WL_M60[email protected]60105_CNV_1.26_002_release_492355_signed_1.zip
HBOOT ZIP:
0PJAIMG_HIMA_WL_M60[email protected]60105_CNV_1.26_002_release_492355_hboot_1.zip
3.37.605.13 Official Signed RUU
Android 6.0 Marshmallow
Verizon HTC One M9
This RUU may be used on S-Off and S-On devices.
DOWNLOAD:
0PJAIMG_HIMA_WL_M60_S[email protected]60105_CNV_1.26_002_release_485015_signed_1.zip
_________
3.37.605.7 Official Signed RUU
Android 6.0 Marshmallow
Verizon HTC One M9
This RUU may be used on S-Off and S-On devices.
DOWNLOAD:
0PJAIMG_HIMA_WL_M6[email protected]60105_CNV_1.26_002_release_469809_signed_1.zip
How To Apply/Install:
Download the file and Check the MD5 sum
Rename the file to 0PJAIMG.zip
Place file in the root of an external sd card formatted in fat32
Boot to aboot (power off phone, hold volume down and power at the same time)
Use volume keys to navigate to "Download Mode" and select it using the power button.
Once in download mode it should automatically find the file, and prompt you to press volume up to flash it or down to cancel.
Go ahead and press volume up and allow it to flash the file.
Phone should reboot several times and eventually reboot you into the OS.
DONE!!
____
thx...u gonna create & post system.img?
OMJ said:
thx...u gonna create & post system.img?
Click to expand...
Click to collapse
No problem.
It's in progress now... :good:
Am I correct in assuming the 3.37.605.7_OTAPkg.zip needs to be flashed in original recovery not TWRP?
Threefifty said:
Am I correct in assuming the 3.37.605.7_OTAPkg.zip needs to be flashed in original recovery not TWRP?
Click to expand...
Click to collapse
yes, but even w/ stock recovery, if the system partition checksum has changed at all, the ota will fail...
Is it possible to use the OTAPkg.zip file to install the update rather than accepting it over the air? I tried the OTA update this morning but it failed halfway through the download and won't resume after failing. I'm 100% stock so I wasn't sure if i could flash this in the stock recovery or not without having to do a full wipe.
dynofrk666 said:
Is it possible to use the OTAPkg.zip file to install the update rather than accepting it over the air? I tried the OTA update this morning but it failed halfway through the download and won't resume after failing. I'm 100% stock so I wasn't sure if i could flash this in the stock recovery or not without having to do a full wipe.
Click to expand...
Click to collapse
No, unfortunately.
Thanks for the reply! One more question, does the file name have to be something specific when on the stock recovery or will your file name work?
dynofrk666 said:
Thanks for the reply! One more question, does the file name have to be something specific when on the stock recovery or will your file name work?
Click to expand...
Click to collapse
It actually doesn't work at all on this device/update.
My refresh button couldn't be more worn out. LOL Santod you are the man!
Btw does anyone know if 3.37 firmware will work with the current lollipop roms? Kinda afraid of flashing it and then not having a functioning phone while I wait for the ROM to upload.
I'm on Viper 3.5.0. Android 5.1. which one can I flash via twrp and what recovery does it come with. Or will it not effect recovery. Or do I need to go back to stock?
Sent from my HTC One M9
Tommydorns said:
I'm on Viper 3.5.0. Android 5.1. which one can I flash via twrp and what recovery does it come with. Or will it not effect recovery. Or do I need to go back to stock?
Sent from my HTC One M9
Click to expand...
Click to collapse
See the OP for more details, as I've been adding to it as I go.
Still have questions, let me know...not sure what you are asking exactly.
So far, everything posted is strictly firmware and is not flashable in recovery mode, aside from the OTAPkg.zip which is only flashed on a stock device with stock recovery.
santod040 said:
See the OP for more details, as I've been adding to it as I go.
Still have questions, let me know...not sure what you are asking exactly.
So far, everything posted is strictly firmware and is not flashable in recovery mode, aside from the OTAPkg.zip which is only flashed on a stock device with stock recovery.
Click to expand...
Click to collapse
Oh ok. Thank you, that answered it. I remember @dottat made a custom one for the last firmware release that didn't require you to go back to stock.
Sent from my HTC One M9
Tommydorns said:
Oh ok. Thank you, that answered it. I remember @dottat made a custom one for the last firmware release that didn't require you to go back to stock.
Sent from my HTC One M9
Click to expand...
Click to collapse
A custom "one" what?
What is it you are looking for? Software and firmware are two separate things.
There will be a rom(software) posted eventually, right now there is not yet.
The firmware doesn't require you to be stock, the official OTA update that is posted does.
Not clear on what you are looking for, if you are looking for a stock rooted rom, be patient, it's on the way... :good:
Oh ok... I am patient. Sorry to seem impatient
Sent from my HTC One M9
Has anyone flashed the TWRP 3.0 Recovery firmware and then booted into a Lollipop rom ?
Just want to check if the new firmware is compatible with old lollipop roms until the MM ROMS are ready.
Tommydorns said:
Oh ok... I am patient. Sorry to seem impatient
Sent from my HTC One M9
Click to expand...
Click to collapse
No need to be sorry, just wasn't clear on what it was you were looking for.
Now we are both clear on things.
Hi,
Yesterday I started trying to root my phone, needless to say it didn't go too well. As the title says, I'm unable to access recovery mode, and this morning when I tried to update to andriod 6.0, that wouldn't work either.
I successfully unlocked the bootloader, I think. It says unlocked in bootloader anyway. I have now relocked it to see if it will update with a locked bootloader.
Okay, so to describe what happens when I try to boot into recovery: The HTC logo shows up for a second or so, then the screen goes black and I have to boot it up from start. Also, I noticed, don't know if this is relevant, but in order for me to get into bootloader I have to hold vol down and power for at least 20 seconds, that does't seem normal to me.
I have downloaded a RUU from an HTC site(can't link, first post), but of course that wont install because im S-ON, which I don't know what it means. Anyway, the RUU wizard tells me to get the corret one, even though im fairly sure I am using the correct one.
my CID is HTC__Y13, do't know if that is going to help.
When trying to root I followed the htconeroot websites guide. again can't link :/
I have no idea what to do from here, if anyone who actually knows how these things work could help me, I would apreciate it greatly.
Thanks in advance!
Post fastboot getvar all result without serial & imei no.
Then we'll see what you need to do.
You may need these drivers installed : http://forum.xda-developers.com/showpost.php?p=64926362&postcount=4
Hey, thanks for replying!
Here is my getvar stats. If you don't mind me asking, why should I not post serial or ime no.?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Oh, also my battery is almost fully charged, still says 0mv... Don't know why, maybe somehow my phone incorrectly detects that my battery is too low when trying to run recover/update and quits because of low battery level?
You don't post serial and imei so you don't get your phone stolen. Those numbers can let someone report the phone as stolen, and have it become rejected by the carriers and such. As for the main issue you have, I'm S-OFF personally, so I flash everything manually. I haven't dealt with much of anything with S-ON aside from pure stock which does everything on it's own.
Trauken said:
Hey, thanks for replying!
Here is my getvar stats. If you don't mind me asking, why should I not post serial or ime no.?
Oh, also my battery is almost fully charged, still says 0mv... Don't know why, maybe somehow my phone incorrectly detects that my battery is too low when trying to run recover/update and quits because of low battery level?
Click to expand...
Click to collapse
Because those are personal info .. bad people can use the data to hack or something. So it's best not to post them.
The battery show as 0 on getvar result is normal ...
back to your problem ....
Your device is not a M8 but a different device called M8s
So the custom recovery that you installed most probably for M8 and definitely won't work on M8s.
And be frank with you, I am not familiar with your kind of device. There is a separate thread for M8s - http://forum.xda-developers.com/htc-one-m8/one-m8s-general
You can ask help here : http://forum.xda-developers.com/htc-one-m8/one-m8s-general/make-custom-recovery-htc-one-m8s-t3114245
or here : http://forum.xda-developers.com/htc...lp-thread-htc-one-m8s-to-stock-howto-t3190238
maybe someone with your device version will help you
Wow! I feel so stupid now...
Thanks alot for your help guys!
I'll try using the correct stuff instead and see if I can solve things, thanks again!
By the way, what would be the easiest way to go about this?
My bootloader is locked and I can't unlock it again since I have used the wrong recovery mod... So I can't just flash the recovery mode now, can I?
Could I use the RUU to somehow restore my recovery mode ? That would be great.
You can unlock the bootloader again with the same unlock_code.bin that you applied to HtcDev.
This time use correct TWRP meant for M8s to root it. You can find it in that M8s thread.
I don't know whether there is RUU for your software version. As I mentioned above, those people in M8s thread know better.
Since your device is not rooted (most probably), why don't you do the update from 1.21.401.1 to Marshmallow 2.10.401.1 ?
You just need to reflash the stock recovery but you need to find either 1.21.401.1 0r 2.10.401.1 stock recovery.img
Well the problem is I can't reflash since my bootloader is locked, and I can't unlock my bootloader because whenever I go into the "do you really want to unlock bootloader" screen and say yes, it shows the HTC logo and then turns off again... Very frustrating.
I know I'm currently in the wrong section, but since I already have your attention and the fact that you seem to know your stuff, what do you think I should do?
Trauken said:
Well the problem is I can't reflash since my bootloader is locked, and I can't unlock my bootloader because whenever I go into the "do you really want to unlock bootloader" screen and say yes, it shows the HTC logo and then turns off again... Very frustrating.
I know I'm in the wrong section currently, but since I already have your attention and the fact that you seem to know your stuff, what do you think I should do?
Click to expand...
Click to collapse
OK .. you need to flash 1.21.401.1 signed firmware.zip
I'll try to find one (hopefully is available) but I'll do this tomorrow. It's already 1.45 am here .. I need to rest soon.
Meantime try to search/google 1.21.401.1 OTA.zip or firmware.zip. If you can find one (but make sure it is for M8s not M9 or any other device) .. you just need to run these command to flash it.
fastboot oem rebootRUU
fastboot flash zip firmware.zip
you'll see error
fastboot flash zip firmware.zip (one more time)
fastboot reboot-bootloader
this should fix your problem . your problem now is wrong recovery installed but unable to reinstall correct recovery alone because bootloader is relocked.
Thanks man!
If only the world was made up of people like you!
Get some rest, I'm not in any hurry!
I'll try to get the RUU version that I fits my phone, I'm guessing I can't use a newer one because I'm S-ON? Anyway, you don't have to answer now.
Thanks alot again, really appreiciate your help!
Trauken said:
I'll try to get the RUU version that I fits my phone, I'm guessing I can't use a newer one because I'm S-ON? Anyway, you don't have to answer now.
Click to expand...
Click to collapse
If there is a newer one 2.10.401.1 yes you can use, you can't use older version than 1.21.401.1 like 1.11.401.1 or 1.11.401.10 , higher version is ok.
Good night.
Hey, hopefully I don't wake you up somehow.
I found what I think is the right file, it was named the same thing you told me to flash.
When using the commands you told me I get this:
I can't understand any of it really, I'll google around some more and see if I can find what is wrong.
It happened that I woke up for a drink.
Just wait for tomorrow, I already have the correct firmware.zip for you.
Edit : try this - https://drive.google.com/file/d/0B4jGj3SfskzMVElpa0MxTlpCRGM/view?usp=sharing
See whether you can download it, posted on mobile.
I'll check your progress tomorrow
The last command to exit that cmd prompt screen is fastboot reboot-bootloader
Have to get some sleep, saw your answer just now lying in bed...
Will continue as soon as I wake up
EDIT- Okay so I couldn't wait lol.
Did as you said but I get this:
Am I supposed to put the firmware.zip in the fastboot folder. I did that, I'm guessing that's right...
Here is a picture of my fastboot folder in case it is somehow useful:
Trauken said:
Did as you said but I get this:
Am I supposed to put the firmware.zip in the fastboot folder. I did that, I'm guessing that's right...
Here is a picture of my fastboot folder in case it is somehow useful:
Click to expand...
Click to collapse
It seems like the generic fastboot.exe is not working for this. You should try using the htc_fastboot.exe
https://ruu.lalleman.net/HTC_M8S(QL_UL)/Tools/Fastboot/
put the htc_fastboot.exe in your fastboot folder, then try again with commands
fastboot oem rebootRUU
htc_fastboot flash zip firmware.zip
error...
repeat htc_fastboot flash zip firmware.zip
fastboot reboot-bootloader
If this also fails, the last thing that you can do (you need microSD) ...
rename the firmware.zip to 0PKVIMG.zip (that's a zero not "O")
put 0PKVIMG.zip on your microSD (not in any folder)
on bootloader select hboot
it will scan the file and ask whether to update
volume up to update
once completed reboot
(remember to remove this 0PKVIMG.zip from microSD after reboot)
Thank you once again.
My phone now propely works thanks to you.
The htc_fastboot.exe seems to have done the trick. What is it that it actually does?
I can't stress enough how grateful I am!
Trauken said:
Thank you once again.
My phone now propely works thanks to you.
The htc_fastboot.exe seems to have done the trick. What is it that it actually does?
I can't stress enough how grateful I am!
Click to expand...
Click to collapse
Most probably the HTC encryption on the htc signed firmware.zip only can be read by htc_fastboot.exe
Great that you solved your problem .. you should update to the latest Marshmallow 2.10.401.1
As this is M8s device matter, I requested moderator to move this thread to M8s section
when i type "htc_fastboo oem rebootRUU" it restarting normally and bootloop
Hello,
my tmobile m8 is stuck in bootloader after trying to flash signed firmware.
I any attempts using flashboot do not work.
Can anyone please help me bring my phone back to life in anyway possible.
Ive been trying to find a RUU.zip file to try on my sd card, although i cant seem to find a download link to a zip file and i am on a MAC so the .exe wont work for me.
can someone please help!!!
jdub1983 said:
Hello,
my tmobile m8 is stuck in bootloader after trying to flash signed firmware.
I any attempts using flashboot do not work.
Can anyone please help me bring my phone back to life in anyway possible.
Ive been trying to find a RUU.zip file to try on my sd card, although i cant seem to find a download link to a zip file and i am on a MAC so the .exe wont work for me.
can someone please help!!!
Click to expand...
Click to collapse
What does it say next to "OS" in your bootloader?
xunholyx said:
What does it say next to "OS" in your bootloader?
Click to expand...
Click to collapse
Nothing is listed next to os in the bootloader mene
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
jdub1983 said:
my tmobile m8 is stuck in bootloader after trying to flash signed firmware.
Click to expand...
Click to collapse
Was the firmware install successful, or not?
Even with a successful firmware flash, the intended and expected result is no boot to OS. Or alternately, you will need to unlock bootloader, flash TWRP, and restore a stock TWRP backup.
jdub1983 said:
I any attempts using flashboot do not work.
Click to expand...
Click to collapse
Do you mean fastboot?
What exactly did you try, what were the results, specific error messages, etc.
Just say "any attempts . . do not work" doesn't give us enough info to be helpful.
redpoint73 said:
Was the firmware install successful, or not?
Even with a successful firmware flash, the intended and expected result is no boot to OS. Or alternately, you will need to unlock bootloader, flash TWRP, and restore a stock TWRP backup.
Do you mean fastboot?
What exactly did you try, what were the results, specific error messages, etc.
Just say "any attempts . . do not work" doesn't give us enough info to be helpful.
Click to expand...
Click to collapse
My apologies, fastboot is what I meant.
I'm not at my MAC to copy and paste, I can when I get home after work.
None of the firmware attempts were successful. None of the attempts to flash a recovery were successful either.
Originally I attempted a signed firmware flash from the SD card, renaming the zip, and letting hboot do it's thing. No errors from that method, just rebooted back to the OS.
If you give me a few things to do when I'm in front of the computer I'll execute them later on and report back the results.
jdub1983 said:
My apologies, fastboot is what I meant.
I'm not at my MAC to copy and paste, I can when I get home after work.
None of the firmware attempts were successful. None of the attempts to flash a recovery were successful either.
Click to expand...
Click to collapse
You need to tell us what the error messages were, in order for us to troubleshoot the fastboot problem.
Otherwise, we don't know if the firmware flash was unsuccessful due to wrong firmware, etc.; or if you simply have an issue with USB connectivity.
Try fastboot devices, and see is the output is the phone's serial number. This would mean fastboot is working properly. No need to tell us the serial number (as it's personal info, should not be posted online) - just tell us yes/no.
If the result is "waiting" or no devices connected, or some other error, tell us.
You also need to tell use the firmware numer(s) you tried to flash, and would be nice to see the exact commands, outputs, etc.
jdub1983 said:
None of the attempts to flash a recovery were successful either.
Click to expand...
Click to collapse
Do you mean custom recovery? If so, is it TWRP? What version number?
You can't flash custom recovery (TWRP) with a locked (relocked) bootloader. You need to unlock it again, to flash TWRP.
When asking for help, you should really try to give as many specifics and details as possible. So far, you really haven't provided much specific detail, at all.
jdub1983 said:
Originally I attempted a signed firmware flash from the SD card, renaming the zip, and letting hboot do it's thing. No errors from that method, just rebooted back to the OS.
Click to expand...
Click to collapse
It appears that firmware flash was not successful. Otherwise, the version number of the firmware would be listed on the bootloader screen for OS number.
What number firmware did you try to flash?
redpoint73 said:
You need to tell us what the error messages were, in order for us to troubleshoot the fastboot problem.
Otherwise, we don't know if the firmware flash was unsuccessful due to wrong firmware, etc.; or if you simply have an issue with USB connectivity.
Try fastboot devices, and see is the output is the phone's serial number. This would mean fastboot is working properly. No need to tell us the serial number (as it's personal info, should not be posted online) - just tell us yes/no.
If the result is "waiting" or no devices connected, or some other error, tell us.
You also need to tell use the firmware numer(s) you tried to flash, and would be nice to see the exact commands, outputs, etc.
Do you mean custom recovery? If so, is it TWRP? What version number?
You can't flash custom recovery (TWRP) with a locked (relocked) bootloader. You need to unlock it again, to flash TWRP.
When asking for help, you should really try to give as many specifics and details as possible. So far, you really haven't provided much specific detail, at all.
It appears that firmware flash was not successful. Otherwise, the version number of the firmware would be listed on the bootloader screen for OS number.
What number firmware did you try to flash?
Click to expand...
Click to collapse
When I get home I'll re-try some of the flashes and let you know what the errors say. I originally tried to flash tmobiles latest firmware, full wipe 6.20.531.5 if memory is serving me right now. Downloaded from sneaky ghosts thread. Attempted via sdcard and fastboot. I'll re run the fastboot flash and report the error again, however there wasn't an error code number reported, was all text.
As for TWRP, I'll unlock bootloader again and try and flash again and report the error it gave me.
Thanks for the help, and apologize for not having complete info for you to work off at the moment.
Greatly appreciated!
jdub1983 said:
I'll re run the fastboot flash and report the error again, however there wasn't an error code number reported, was all text.
Click to expand...
Click to collapse
I didn't specify that it had to be an error code number. If the response is all text, tell us what it is. Cut and paste, or do a screenshot, if that is easier. Either way, it will probably tell me what is going wrong.
jdub1983 said:
When I get home I'll re-try some of the flashes and let you know what the errors say. I originally tried to flash tmobiles latest firmware, full wipe 6.20.531.5 if memory is serving me right now. Downloaded from sneaky ghosts thread. Attempted via sdcard and fastboot. I'll re run the fastboot flash and report the error again, however there wasn't an error code number reported, was all text.
As for TWRP, I'll unlock bootloader again and try and flash again and report the error it gave me.
Thanks for the help, and apologize for not having complete info for you to work off at the moment.
Greatly appreciated!
Click to expand...
Click to collapse
Sneakyghost doesn't supply signed firmware. Everything he does is modified, and can only be flashed if you are S-Off
xunholyx said:
Sneakyghost doesn't supply signed firmware. Everything he does is modified, and can only be flashed if you are S-Off
Click to expand...
Click to collapse
Doesn't he have 2 options he offers, the no wipe, which he modifies, and the fullwipe, which I thought were signed?
xunholyx said:
Sneakyghost doesn't supply signed firmware. Everything he does is modified, and can only be flashed if you are S-Off
Click to expand...
Click to collapse
As I suspected, but I could never remember.
OP can find signed firmware here: https://forum.xda-developers.com/showpost.php?p=60218734&postcount=5
Can't find a zip version of the T-Mobile RUU. So you may need to resort to restoring the stock TWRP backup from the same thread as the signed firmware: https://forum.xda-developers.com/htc-one-m8/help/tutorial-how-to-stock-stock-twrp-t3086860
But that depends on what exactly your end goal is. Are you trying to return to full Marshmallow stock, or something else?
---------- Post added at 12:09 PM ---------- Previous post was at 12:07 PM ----------
jdub1983 said:
Doesn't he have 2 options he offers, the no wipe, which he modifies, and the fullwipe, which I thought were signed?
Click to expand...
Click to collapse
He offers No Wipe (which is modified firmware) and Full Stock (which does wipe). But full stock does not mean it's signed. I remember these not being signed also (like xunholyx said). And you can't flash unsigned firmware, unless you have s-off.
jdub1983 said:
Doesn't he have 2 options he offers, the no wipe, which he modifies, and the fullwipe, which I thought were signed?
Click to expand...
Click to collapse
No, they aren't.
Since you are S-On and wiping anyway, the best thing for you to do would just to run an RUU. I'll extract the ROM.zip (RUU.zip) from the T-Mo RUU.exe when I get home in a bit (an hour or two) and link you here to it. You'll be able to flash that via your SD card.
EDIT: I see now that Redpoint has already linked you up. :good: Easier for me
xunholyx said:
Since you are S-On and wiping anyway, the best thing for you to do would just to run an RUU. I'll extract the ROM.zip (RUU.zip) from the T-Mo RUU.exe when I get home in a bit (an hour or two) and link you here to it. You'll be able to flash that via your SD card.
Click to expand...
Click to collapse
I agree the RUU is easier for him, since he is already relocked and (as you mentioned) wiping anyway. Restoring a TWRP backup (by method I linked) is a lot more steps.
redpoint73 said:
As I suspected, but I could never remember.
OP can find signed firmware here: https://forum.xda-developers.com/showpost.php?p=60218734&postcount=5
Can't find a zip version of the T-Mobile RUU. So you may need to resort to restoring the stock TWRP backup from the same thread as the signed firmware: https://forum.xda-developers.com/htc-one-m8/help/tutorial-how-to-stock-stock-twrp-t3086860
But that depends on what exactly your end goal is. Are you trying to return to full Marshmallow stock, or something else?
---------- Post added at 12:09 PM ---------- Previous post was at 12:07 PM ----------
He offers No Wipe (which is modified firmware) and Full Stock (which does wipe). But full stock does not mean it's signed. I remember these not being signed also (like xunholyx said). And you can't flash unsigned firmware, unless you have s-off.
Click to expand...
Click to collapse
Gotcha! If I'm s-on though, how did everything get screwed up? Guess it's not important now.
I'd like to get the m8 upgraded to latest firmware, radio, etc for T-Mobile network. Was planning on installing a custom ROM once it was upgraded, such as lineageOS or leedroid Rom. Something simple really, my m8 is my backup phone.
redpoint73 said:
I agree the RUU is easier for him, since he is already relocked and (as you mentioned) wiping anyway. Restoring a TWRP backup (by method I linked) is a lot more steps.
Click to expand...
Click to collapse
Would be great to have the ruu zip, been looking for a one for a few days. However if you want to hold off, I'm happy to go through the long get process as it will be good practice and refresher for me, if I run into any issues I can then hit you up for the zip ruu. Whatever is good for you kind souls helping me out!
Thank you!
jdub1983 said:
If I'm s-on though, how did everything get screwed up?
Click to expand...
Click to collapse
Once you relock the bootloader with s-on, the phone is rendered unable to boot to OS, as it expects RUU to be run.
OS number is blank in bootloader, usually due to an old version of TWRP being used it the past (known bug).
Other than that, your fastboot issues are often a problem on the PC side. But would need to know the exact error messages to troubleshoot further.
jdub1983 said:
I'd like to get the m8 upgraded to latest firmware, radio, etc for T-Mobile network. Was planning on installing a custom ROM once it was upgraded, such as lineageOS or leedroid Rom.
Click to expand...
Click to collapse
If the intent to flash a custom ROM right away, I would suggest just flashing the signed firmware 6.20.531.5 from the link I provided. Then unlock bootloader again, flash TWRP 3.1.0 (current version) and flash the ROM of your choice.
No point in restoring a stock TWRP backup, if you are just going to then flash a custom ROM.
redpoint73 said:
I agree the RUU is easier for him, since he is already relocked and (as you mentioned) wiping anyway. Restoring a TWRP backup (by method I linked) is a lot more steps.
Click to expand...
Click to collapse
redpoint73 said:
Once you relock the bootloader with s-on, the phone is rendered unable to boot to OS, as it expects RUU to be run.
OS number is blank in bootloader, usually due to an old version of TWRP being used it the past (known bug).
Other than that, your fastboot issues are often a problem on the PC side. But would need to know the exact error messages to troubleshoot further.
If the intent to flash a custom ROM right away, I would suggest just flashing the signed firmware 6.20.531.5 from the link I provided. Then unlock bootloader again, flash TWRP 3.1.0 (current version) and flash the ROM of your choice.
No point in restoring a stock TWRP backup, if you are just going to then flash a custom ROM.
Click to expand...
Click to collapse
I'll give it a whirl when I get home and let you know of any errors, if any, hopefully not.
Question ahead of time: I noticed after re-locking the bootloader, the command "fastboot oem rebootruu" wasn't recognized, does this play into the fact that the phone is expecting a ruu, and therefore already in ruu mode?
Thanks again!
jdub1983 said:
Question ahead of time: I noticed after re-locking the bootloader, the command "fastboot oem rebootruu" wasn't recognized, does this play into the fact that the phone is expecting a ruu, and therefore already in ruu mode?
Click to expand...
Click to collapse
I doubt it. Rather, I think your syntax was incorrect (if you typed it exactly as you did before) as the part "RUU" (no quotes) should be in caps:
fastboot oem rebootRUU
If the phone is in RUU mode, it will show a black screen, with HTC logo.
jdub1983 said:
Would be great to have the ruu zip, been looking for a one for a few days. However if you want to hold off, I'm happy to go through the long get process as it will be good practice and refresher for me, if I run into any issues I can then hit you up for the zip ruu. Whatever is good for you kind souls helping me out!
Thank you!
Click to expand...
Click to collapse
Here's the RUU.zip for you.
you both are amazing, thank you!
I feel so silly, considering I was using sneaky ghosts unsigned fullwipe firmware... Blah!
Again, you both are awesome, kind to a moron! The universe will provide for you both!
Thanks again!!!
Everything is working wonderful!!!!!