Related
There are a few threads here which provide radios to flash and information on how to flash them. I am writing this guide so people know what the different ways of flashing a radio are and what the repercussions of each method are.
Flashing methods
Method 1) Using fastboot (Recomended)
Step 1) Download the radio. If the radio is a zip file, open it and extract radio.img
Step 2) Connect your phone and enable debug mode
Step 3) Use adb to send your phone to boot loader with the command "adb reboot bootloader". Alternately, you can switch off our phone and turn it on with power+volume down pressed and get teh same result
Step 4) Once you are in fastboot mode in the boot loader aka hboot and your phone is connected to the PC via the cable, type the command "fastboot flash radio radio.img" making sure radio.img is in the same folder as fastboot & your command prompt session
Pros of this method:
mainver doesn't change
Avoids issues such as Security Warning - Stuck in bootloader
Method 2) Flash from HBoot with PG32IMG.zip
Step 1) Download the radio which is in a zip file
Step 2) Copy it to a SD card which is a gold card. If you don't have one, create a gold card first
Step 3) Switch off our phone and turn it on with power+volume down pressed. This will take you to HBoot and the file will be flashed after confirmation from you
Cons of this method:
mainver can change based on the mainver mentioned in android-info.txt
Requires a gold card
Pros of this method:
You can reduce your mainver when needed.
Why is this a pro and a con?
It's a con because if you don't know about this and increase your mainver before installing stock, you could get a bootloader Security warning leading to your phone not coming out of the boot loader. Don't worry, that post I linked to also has a fix but it's a pain for your.
It's a pro because if you want to go back to stock and the ROM you want has a lower mainver, being S-off allows you to run unsigned code and that allows you to reduce your mainver.
The choice is yours. You decide.
FAQs
1) Why do I need a radio update?
It is said that when you install a ROM, you should have a radio to match to give you good performance and not have a negative effect on reception/battery life etc. (this is something I've read on XDA threads).
2) What do I need to flash radios?
An android phone (of course ) which is S-Off.
3) Does it matter (for radio installation) if I S-Offed using a XTC Clip/AlphaRevX/Revolutionary?
No. If you're S-Off already, you're good to go.
4) Where do I get my radios?
Threads such as these exist
5) I'm going to go back to stock. What should I check?
Check your phone's mainver. If the ROM's mainver is equal to or greater than your phone's mainver, you can install it
6) How do I check what my mainver is?
Connect your phone and type the command "fastboot getvar all"
7) How do I reduce my mainver?
If you want to downgrade your to a stock rom with lower main ver, you can use method 2 and edit the mainver in android-info.txt inside the zip file, put the txt back into the zip and then flash it on your phone. Your mainver will be lower and now you can install a stock ROM with any mainver.
I personally choose to keep my mainver at 2.00.000.0 allowing me to install any stock GB ROM I'd want to
Thankyou John!
This should be sticky & in development.
neo-X said:
Thankyou John!
This should be sticky & in development.
Click to expand...
Click to collapse
A moderator can do both. Anyone out there?
Thank you very much for the clear instructions! I've been looking for some time now and I finally got a proper radio version now!
Someone requested the RIL for 3805.06.03.16 radio on this post for the Bell Incredible S
http://forum.xda-developers.com/showpost.php?p=16905369&postcount=2716
I would like to say that from the size and what the zip contain it look fishy..beware.
Normaly radio are like 10mb and the file he give in his post is 354kb...??
Just a warning if I am right just look fishy and since I am new to this world it's possible it's legit but it does not look great when it contain a folder with this name: "__MACOSX\"
It look like the actual radio it is actually located on this thread.
http://forum.xda-developers.com/showthread.php?t=1129014
•From the 2.32.1010.1 RUU:
•20.2810.30.085AU_3805.06.03.16
md5: c8c0be410c97e9bf82cdad54d4da0ef4
Some questions re flashing radios.
I've just moved over to the IS from a Desire and the radio flashing methods seem a bit more complicated. Why is that?
Do you still need a Gold Card even on a sim free handset?
Is it not possible to copy the radio file to SD and flash it with CWM?
UKseagull said:
Some questions re flashing radios.
I've just moved over to the IS from a Desire and the radio flashing methods seem a bit more complicated. Why is that?
Do you still need a Gold Card even on a sim free handset?
Is it not possible to copy the radio file to SD and flash it with CWM?
Click to expand...
Click to collapse
you can rename it to PG32IMG.zip
reboot your phone while holding power and volume down and flash it through there
---------- Post added at 09:23 PM ---------- Previous post was at 09:11 PM ----------
I never use a goldcard... I should probably make one
Cheers Scooby, is your phone a sim free version?
I thought that gold cards were only required for branded handsets?
I'm still quite curious as to why the radio can't be flashed directly with CWM?
UKseagull said:
Cheers Scooby, is your phone a sim free version?
I thought that gold cards were only required for branded handsets?
I'm still quite curious as to why the radio can't be flashed directly with CWM?
Click to expand...
Click to collapse
mine was a bell branded that I unlocked to use with telus.
I'm not sure about your second question, I just think a bad flash this way could brick your phone I think that's why you don't do it that way
Thanks
John Anderton said:
There are a few threads here which provide radios to flash and information on how to flash them. I am writing this guide so people know what the different ways of flashing a radio are and what the repercussions of each method are.
Flashing methods
Method 1) Using fastboot (Recomended)
Step 1) Download the radio. If the radio is a zip file, open it and extract radio.img
Step 2) Connect your phone and enable debug mode
Step 3) Use adb to send your phone to boot loader with the command "adb reboot bootloader". Alternately, you can switch off our phone and turn it on with power+volume down pressed and get teh same result
Step 4) Once you are in fastboot mode in the boot loader aka hboot and your phone is connected to the PC via the cable, type the command "fastboot flash radio radio.img" making sure radio.img is in the same folder as fastboot & your command prompt session
Pros of this method:
mainver doesn't change
Avoids issues such as Security Warning - Stuck in bootloader
Method 2) Flash from HBoot with PG32IMG.zip
Step 1) Download the radio which is in a zip file
Step 2) Copy it to a SD card which is a gold card. If you don't have one, create a gold card first
Step 3) Switch off our phone and turn it on with power+volume down pressed. This will take you to HBoot and the file will be flashed after confirmation from you
Cons of this method:
mainver can change based on the mainver mentioned in android-info.txt
Requires a gold card
Pros of this method:
You can reduce your mainver when needed.
Why is this a pro and a con?
It's a con because if you don't know about this and increase your mainver before installing stock, you could get a bootloader Security warning leading to your phone not coming out of the boot loader. Don't worry, that post I linked to also has a fix but it's a pain for your.
It's a pro because if you want to go back to stock and the ROM you want has a lower mainver, being S-off allows you to run unsigned code and that allows you to reduce your mainver.
The choice is yours. You decide.
FAQs
1) Why do I need a radio update?
It is said that when you install a ROM, you should have a radio to match to give you good performance and not have a negative effect on reception/battery life etc. (this is something I've read on XDA threads).
2) What do I need to flash radios?
An android phone (of course ) which is S-Off.
3) Does it matter (for radio installation) if I S-Offed using a XTC Clip/AlphaRevX/Revolutionary?
No. If you're S-Off already, you're good to go.
4) Where do I get my radios?
Threads such as these exist
5) I'm going to go back to stock. What should I check?
Check your phone's mainver. If the ROM's mainver is equal to or greater than your phone's mainver, you can install it
6) How do I check what my mainver is?
Connect your phone and type the command "fastboot getvar all"
7) How do I reduce my mainver?
If you want to downgrade your to a stock rom with lower main ver, you can use method 2 and edit the mainver in android-info.txt inside the zip file, put the txt back into the zip and then flash it on your phone. Your mainver will be lower and now you can install a stock ROM with any mainver.
I personally choose to keep my mainver at 2.00.000.0 allowing me to install any stock GB ROM I'd want to
Click to expand...
Click to collapse
Thank you for this guide,very usefully!!!
Clearly explained, thanks JA. I think this should be in the sticky section. Can any forum admin do the needful please?
Sent from my HTC Incredible S
Sprint HTC M8 Hboot Versions & Info
I am not a developer-this is simply my contribution to the Sprint HTC M8 community as a way to help users have a basic understanding of what Hboot is, and understand the differences and capabilities between Hboot versions. You are free to include my work if you are putting together a guide or FAQ of your own, I only ask that you give credit where credit is due. I've taken a lot of time and put some effort into making this guide as complete as possible, but if you see something you'd like to have added or have a question or comment, feel free to do so. You can also reach me via PM. I do currently own this device, and I will try my best to keep this guide up to date. I am not responsible for any misinterpretations of the information contained within this guide, and I will not be held liable or responsible should you damage your phone or cause an act of war. Now, let's get started.
What is Hboot? Without getting too technical, Hboot is your bootloader. Its functions are similar to that of the BIOS (Basic Input/Output System) on a PC. The bootloader provides a level of security for your phone by preventing unsigned software and firmware from being installed on your phone. At times, the bootloader will be updated to provide bug fixes and security patches. This sounds like a good thing, but it's really just a roadblock for those of us who like to tinker with our phones. This is where unlocking the bootloader comes in to play. Unlocking the bootloader allows us to install custom recoveries, from which we can flash custom ROM's to our phones. Still, however, depending upon the bootloader security, you are still limited to what you can do once the bootloader is unlocked. Unlocking the bootloader on the M8 is accomplished using HTC Dev or the Sunshine S-off exploit. I won't delve into the actual process of unlocking the bootloader, as this is covered elsewhere.
S-on vs. S-off. When you received your M8 new, it shipped with a locked bootloader and was S-on, which meant that bootloader security was on. While true that unlocking the bootloader gives some added functionality, like being able to install a custom recovery such as TWRP (Team Win Recovery Project) or CWM Touch, and allowing the flashing of a custom ROM, there are still limitations. This is where S-off comes in to play. If S-on means security on, then yes, S-off means security off. Once S-off, the bootloader's security is completely removed. Once S-off, you can write permanently to the system partition, install unsigned firmware, mask your Hboot and remove the red development disclaimer from the splash screen, among other things. As more than one developer has put it, you are essentially future-proofing your device. This is especially true given the restrictions that HTC has put in place on the newer bootloaders. Think of bootloader unlocking and S-off like a bank. Bootloader unlocking gets you in the front door; S-off gets you into the vault.
Currently, S-off is available via the SunShine exploit ONLY. For more information regarding S-off, check out this thread here.
The bootloader screen
How do you access the bootloader menu? If you're running a Sense ROM, make sure you have fastboot disabled in settings. You can go to Menu>Settings>Power and make sure fastboot isn't enabled. Don't confuse the fastboot setting with fastboot in the bootloader-they are not the same. Power your phone completely off. Press and hold the volume down button, then press and hold the power button (most custom ROM's normally let you reboot to the bootloader from the power menu, also). After several seconds you will be presented with a white screen with some information in the top left corner of the screen. Stock, the top line will say "Locked". Once unlocked, the top line will read "Unlocked". If the bootloader has been relocked, the top line will read "Relocked" and will also show a security warning. Once unlocked or relocked, there will also be a "Tampered" warning, as well (as of the 3.19 Hboot update, this line has been replaced with "Software status: Official or Software status: Modified, depending upon whether or not you're stock or using a custom ROM). Below that is the HTC device codename, which is M8_WHL (this is Sprint-specific, as M8's on other carriers have other designations). On this same line, you will see whether the phone is S-on or S-off. The third line from the top is the Hboot version, and below that is the radio (baseband) version. Also different from previous HTC phones is the OS version, which can be found two lines below the radio version. From the bootloader menu there are also options to power off the phone, reboot the bootloader, enter fastboot mode, factory reset and go to recovery. To navigate the menu, simply use the volume keys to move up and down, and use the power button to select. From the bootloader screen you can select the "fastboot" option, whereby you can connect your phone to your PC and issue commands via fastboot USB if you have the correct drivers installed on your computer. You have to have a properly working ADB (Android Debug Bridge) and Fastboot environment set up on your computer first in order to do so. You also have to use it when using HTC Dev to unlock your bootloader, so it comes in handy in more ways than one and doesn't hurt to have it on your computer should you ever need to use it. If you ever find your device caught in a boot loop, when the screen goes black you can hold the volume down button down and the device will boot into the bootloader. Alternatively, if the device is hung up on the splash screen, hold power+volume up until the screen goes black. Release power+volume up and press the volume down button until the bootloader screen appears.
Below is a list of current Hboot versions for the Sprint M8 with corresponding software & baseband (firmware) versions:
Hboot 3.16:
Baseband 1.05.20.0227_2/software version 1.12.651.17; baseband 1.05.20.0321/software version 1.54.651.8; software version 1.54.654.10/baseband version 1.08.20.0610
Harman Kardon version: Baseband 1.05.20.0227_2/software version 1.54.654.9; Baseband 1.05.20.0321/software version 1.54.654.13; baseband 1.08.20.0610/software version 1.54.654.15
Hboot 3.18:
Software version 2.16.651.4/baseband 1.08.20.0612_4
Harmon Kardon version: 2.16.654.4/baseband 1.08.20.0612_4
Hboot 3.19:
Software version 3.30.651.2/baseband 1.08.20.0916; software version 3.31.651.2*/baseband 1.08.20.0916; software version 4.20.651.4/baseband 1.09.20.0119; software version 4.25.651.14/baseband 1.09.20.0209; software version 4.25.651.18*/baseband 1.09.20.0209; software version 6.20.651.3/baseband 1.09.20.1112
Harmon Kardon version: Software version 3.30.654.2/baseband 1.08.20.0916; software version 3.31.654.2*/baseband 1.08.20.0916; software version 4.20.654.10/baseband 1.09.20.0119; software version 4.25.654.14/baseband 1.09.20.0209; software version 4.25.654.18*/baseband 1.09.20.0209; software version 6.20.654.3/baseband 1.09.20.1112
*Software versions 3.31.65x.2 & 4.25.65x.18 did not include a baseband version update.
***Please use the firmware & Hboot that corresponds to the software version of the ROM you're using, otherwise, Wi-Fi and other hardware may not work properly. To update to Marshmallow (Android 6.0) via RUU from Lollipop or KitKat, you must install the firmware for Marshmallow first, otherwise the RUU will fail.***
CID Numbers (Sprint only):
SPCS_001: standard Sprint M8 (software 651)
SPCS_004: Harman/Kardon version M8 (software 654)
Bootloader unlocking tools:
HTC Dev
Sloth's Rooting Guide
hasoon2000's Root Toolkit
WinDroid HTC Universal Toolkit
How to obtain S-off:
SunShine
***The SunShine exploit can be used to unlock the bootloader as well as gain S-off, making unlocking with HTC Dev unnecessary.***
I take no credit for any of the tools or methods listed above. The above listed tools are the property of their respective developers/contributors.
S-off vs. Root
There always seems to be some confusion among some users regarding root and S-off. First off, they are not the same thing. Root is a method by which users can run privileged commands on their device.
Rooting is typically accomplished by a security exploit that allows the su (superuser) binary to be installed on the device, which in turn installs either the SuperUser or SuperSU app on the device. Both of these apps give the user the ability to grant or deny root apps to function. In addition to running certain apps (like WiFi tether, Root Explorer or Titanium Backup), root privilege can also allow the removal of files and apps which could not be removed by a user with an unrooted phone (for example, removing carrier-installed "bloatware").
Some users think that you must be S-off in order to have what they call "full root", which is simply not the case, as root and S-off are independent of one another. It's actually quite the contrary, as you can have a phone that is S-off but does not have root access. How is this so? Remember, S-off simply means that the bootloader's security is off. In order to root a phone, you must have a custom recovery installed and have the proper superuser binary in place for root to work. S-off methods are not always available when a new phone is released (or when a phone receives updated software and/or firmware), which is why we have methods like HTC Dev to unlock our bootloader.
If a method to gain S-off is available, it's best to use it. Like I stated earlier, S-off is virtually future-proofing your phone, so regardless of any updates that may come out, once you're S-off, that's it: you're S-off until a method is released to put the device back to S-on, and that's something the device user typically initiates. S-off trumps bootloader unlocking because being simply bootloader unlocked, there are still security restrictions on the device. S-off removes those restrictions. But, as stated earlier, without a custom recovery and superuser in place, the device is not rooted. The ideal situation is to be rooted and S-off.
A quick word of caution regarding S-off. With the bootloader's security off, there is no longer any protection should you flash a corrupt or incompatible file to your device, so know & understand what you're doing and don't do something foolish to turn your device in to an expensive paperweight.
Firmware Updates
From time to time, it may be necessary to update your phone's firmware, sometimes referred to as your radios or your baseband. This can be done for a number of reasons, ranging from call quality or data connection issues or poor battery life due to outdated firmware, just to name a few things. Personally, I like to keep my firmware version updated to whatever the newest corresponding software version is at the time. Keep in mind that firmware and software are not the same. Software is the ROM you flash via recovery. Firmware is the radios, PRI and whatever other bits a developer chooses to include. The only time you get both packaged together is in a OTA (Over The Air) update sent out by the phone carrier, or by RUU. Since rooted users don't typically take OTA updates, we have to rely on developers to pull the firmware from the update package and re-package it for our use. You must be S-off to install modified firmware on your device. To update your firmware, first download the applicable firmware package. You can download the file to either your phone or your computer. Typically, the file will have an MD5 sum that acts as a fingerprint to verify that your download matches that of the original. You can use an app like Android File verifier to check the MD5 of the downloaded file versus that of the original file. If the MD5's match, you're good to go. If not, you need to download the file again, making sure you check the MD5 again. This is important, as you don't want to screw up a firmware update. A bad firmware flash is a good way to turn your phone into an expensive paperweight. Once you have the file downloaded you need to transfer it to the root (not in a folder) of your external microSD card. Firmware updates cannot be run from the phone's internal memory. Check and make sure that the file is named 0P6BIMG.zip (If using your computer, Windows often hides the .zip extension so if you don't see it on your computer, right-click on the file and select "Properties" to see if the .zip extension is there, which it should be). If you downloaded the file directly to your phone, you can use a file manager like Astro file manager or Root Explorer to check that the file is properly named. The bootloader will be looking for the file named 0P6BIMG and, if improperly named, will not locate it. Sometimes the file won't require renaming but it's important to check and make sure, to save you some headache down the road. Make sure you also have a decent charge on your battery, because if your phone dies during the firmware update, you'll end up with a bricked device, most likely. Now, you need to reboot to the bootloader, which was discussed previously. Your phone should reboot to Fastboot mode. Use the volume buttons to navigate to the "Bootloader" option in the menu, and press the power button to make your selection. The bootloader will now scan for the firmware update on your SD card, and once it finds it, will prompt you as to whether or not you wish to start the update. Once again, use the volume buttons to make your choice. The update may take a couple of minutes to complete, at which time you'll be prompted to either power off the phone or reboot. Reboot the phone, then go to Menu>Settings>About Phone>Software info and check your baseband version and see if it corresponds to the firmware update you just installed. Once you've done this and confirmed that the update was successful, delete the 0P6BIMG.zip file from your SD card (if you don't do this, you will be prompted to update your firmware every time you reboot to the bootloader). If the update fails from the bootloader, go back through the steps outlined above and double-check that you have done everything correctly. For more information regarding firmware updates, see Captain Throwback's firmware thread or OMJ's RUU thread. Links to both threads can be found at the bottom of this post.
RUU's
Occasionally, you may encounter an issue which requires a RUU (ROM Update Utility). This is an update package released either by an OEM (like HTC) or a developer. It is designed to put the phone back to stock condition. This can be done for a variety of reasons including updating to a newer software version or for returning the phone back to stock to have the device serviced by the carrier or manufacturer. Note that if your device is S-on, you can only run a RUU with the same software/firmware version that you're currently running, or a newer version. If you're S-off, the same applies, and in addition, you can also downgrade to an older version than what's installed on your device. Running a RUU may in some cases re-lock your bootloader and also unroot your phone. To root again, you'll need to unlock the bootloader, install a custom recovery and install the necessary SU binary. On S-off phones, the device will remain S-off but the bootloader may need to be unlocked again with HTC Dev. See the bottom of this post for a complete list of links to current available RUU's.
To run a RUU, simply download the RUU you wish to install to your PC, then connect your phone and PC via USB cable. While booted to the Android OS, simply double-click the RUU file on your computer to start the installer, then follow the on-screen instructions. Normally, a RUU is run while the phone is booted to the OS but alternatively, can be run while the phone is connected to the computer via Fastboot USB mode. Simply connect the phone and PC via Fastboot USB mode, then double-click the RUU file on your computer to start the installer. If your device is S-on you will need to relock your bootloader to run a RUU. Use the command "fastboot oem lock" to relock your bootloader (without quotation marks). You need to install HTC Sync to your computer to get the proper drivers installed to help connect your device to your computer.
***Note that actual instructions for running the RUU may differ from the instructions posted above. Refer to the directions for the specific RUU for installation instructions.***
S-on Kernel Flashing
Below is a short guide on how to flash kernels while S-on. For some ROM's, like GPE, this is required. If you're not sure if you need to manually install the kernel, check the OP for the ROM you want to install. Check out the link below for an easy how-to on setting up ADB on your computer (credit to Jerry Hildenbrand at Android Central for the write-up). The guide also includes a basic set of commands that users might find useful while using ADB. You can install the latest version of HTC Sync to get drivers for your computer.
How to set up ADB and ADB commands
If no kernel installer is included as part of the ROM, there are two basic ways to flash a kernel to your phone while S-on. The first method is using an app from the Play store called Flashify. Simply follow the instructions in the app. The second method is to flash the kernel via Fastboot, which I will explain below.
First, download the ROM of your choosing to your phone. Once you've done this, navigate to where you downloaded the ROM on your computer and extract the boot.img from the ROM zip file. Place it in your ADB tools folder. The boot.img is the ROM's kernel, which is needed for the ROM to work. Without getting too technical, the kernel allows the phone's hardware and software to work together. Boot into recovery and flash the ROM zip. Now, reboot to the bootloader. Your phone should say Fastboot, highlighted in red. If not, use your volume keys to highlight the Fastboot option from the menu we discussed previously, then use the power button to select. You should then see the word Fastboot highlighted in red. Connect your phone and PC via USB cable. Once the connection is complete, you will see "Fastboot" change to "Fastboot USB". Open up your ADB/Fastboot terminal (Shift+Right click on the folder, then choose the option to open up a command line), then follow the instructions below:
Type:
Code:
fastboot devices
Press enter. Your phone's serial number should be output on the line below, so now you know that fastboot recognizes your phone.
Now, type:
Code:
fastboot flash boot boot.img
Press enter. The kernel should then be flashed to your phone, unless you get an error message in the terminal. Once successful, you can reboot your phone. Remember that the first boot will take several minutes.
Thanks to:
@Sloth. Check out his FAQ here.
@Captain_Throwback Check out his firmware thread here.
@hasoon2000 for his root toolkit. @Rapscallion16 for his WinDroid toolkit.
@regaw_leinad for his thread explaining S-off.
@O.M.J for his RUU thread. Find it here.
If you're looking to return your device back to stock, check [URL=" http://forum.xda-developers.com/showthread.php?t=2826343" ]here.[/URL] Thanks to @miggsr for this guide.
Enjoy
nice write up. Hopefully we see s-off very soon.
Sim-X said:
nice write up. Hopefully we see s-off very soon.
Click to expand...
Click to collapse
It will come in due time
Sent from my EVO LTE
Added a link for Bachatu's custom Hboot for Hboot 3.16.
Added info & links regarding firmware updates. Also added info from most recent OTA.
thank you FinZ28. picked up my m8 wed last week. couldnt even make it a week! :good::good: i was getting the itch to root sat. been reading up on it. this thread is what pushed me to do it. so well laid out and explained. ive rooted since the og evo days, but never really understood what was going on. thank you for the clear explanations!
View attachment 2700916
View attachment 2700917
v01rider said:
thank you FinZ28. picked up my m8 wed last week. couldnt even make it a week! :good::good: i was getting the itch to root sat. been reading up on it. this thread is what pushed me to do it. so well laid out and explained. ive rooted since the og evo days, but never really understood what was going on. thank you for the clear explanations!
View attachment 2700916
View attachment 2700917
Click to expand...
Click to collapse
Glad to be of assistance
Things have definitely changed since the OG EVO days. Now there is essentially one way to root all HTC devices, as opposed to the old days of Unrevoked and Revolutionary.
Sent from my HTC device
Added info for RUU's and a link to OMJ's RUU. Also added a link for the WinDroid Universal HTC toolkit.
v01rider said:
thank you FinZ28. picked up my m8 wed last week. couldnt even make it a week! :good::good: i was getting the itch to root sat. been reading up on it. this thread is what pushed me to do it. so well laid out and explained. ive rooted since the og evo days, but never really understood what was going on. thank you for the clear explanations!
View attachment 2700916
View attachment 2700917
Click to expand...
Click to collapse
You should try removing the Tampered banner now that you're S-Off
brandonair95 said:
You should try removing the Tampered banner now that you're S-Off
Click to expand...
Click to collapse
done!
Can i flash non Sprint RUU on the Sprint phone?
x017in said:
Can i flash non Sprint RUU on the Sprint phone?
Click to expand...
Click to collapse
Someone might want to look at it, but my suspicion is no. There are big enough nuances with the versions of the variants that I wouldn't recommend it without the okay from one of our respected devs.
Sent from M8 on XDA Premium APP
joshuaw84 said:
Someone might want to look at it, but my suspicion is no. There are big enough nuances with the versions of the variants that I wouldn't recommend it without the okay from one of our respected devs.
Sent from M8 on XDA Premium APP
Click to expand...
Click to collapse
Agreed:thumbup:
It's one thing to flash a ROM that isn't specific to Sprint. It's another to flash a RUU, which includes firmware, Hboot, etc. I don't believe it would be a good idea.
Sent from my HTC device
It's working without any problem.
I know that currently there are two HK software versions available (1.54.654.9 & 1.54.654.13). If anybody has the applicable radio (baseband) versions for each one, would you mind posting it here so I can update my guide? Did a bit of searching but haven't come up with anything beyond the software version numbers. For that matter, the radio versions may be the same as the non-HK version. Either way, let me know.
Magnum_Enforcer said:
I know that currently there are two HK software versions available (1.54.654.9 & 1.54.654.13). If anybody has the applicable radio (baseband) versions for each one, would you mind posting it here so I can update my guide? Did a bit of searching but haven't come up with anything beyond the software version numbers. For that matter, the radio versions may be the same as the non-HK version. Either way, let me know.
Click to expand...
Click to collapse
I think the radios are all the same.
BD619 said:
I think the radios are all the same.
Click to expand...
Click to collapse
Just wanted to be sure. I was updating my guide with the HK version info and was just trying to be thorough
Updated with info from latest OTA.
Updated with link & info for SunShine S-off.
Great thread, Thanks Magnum.
Sent from my 831C using XDA Premium 4 mobile app
Download link to
OTA for HTC One 7 CID=TELST001 Software update 6.11.841.9 (181.54Mb) - December 23, 2014.
I unzipped this file, extracted the firmware.zip and upgrade my HTC One 7 (Telstra Australia) rooted and s-off.
I am unable to post link to this OTA file.
PM me if you like.
Crtl-Q
This could help me.
Hi,
I have my daughters HTC One M7, which is bricked after she tried to do a system update last weekend. It seems the battery ran out in the process and the handset is now in recovery mode. Telstra were no help to her in getting the problem fixed and sadly there are a lot of photos and other data on the phone.
Although I have an electronic/computing/comm's background I haven't done much with fixing HTC androids (my Sony's seem to not have any problems so far - touchwood) but I am comfortable enough to try and get the handset back up and working. So I have been trying without much success to find an RUU to match the info from getvar all.
: version-main: 6.11.841.9 , modelid: PN0714000 and cidnum: TELST001
Your post looked worth following up, so I have joined XDA so I can get some information.
Can you give me a clue as to where to find this RUU and also, do you have any other info that might help me in recovering the phone? There is quite a lot of information on this interweb about these handsets and similar problems but a lot of it doesn't match what I see on the handset and PC when trying to flash the device.
I am a newbie here so I am not fully conversant with the protocols so please go gentle on me
Hey mate.
Go to the XDA HTC one Australian users thread. @deeevan on that thread has supplied almost all the Telstra OTA's if you go through it. Was about to step you through flashing a stock RUU, but not sure if it's possible if the phone isn't rooted or s-off. Had your daughter got s-off before the accident? It's important that you only flash the RUU that is next in line from 6.11.841.9 or that exact version as you can re brick you phone if you skip an RUU.
Joeisgood99 said:
Hey mate.
Go to the XDA HTC one Australian users thread. @deeevan on that thread has supplied almost all the Telstra OTA's if you go through it. Was about to step you through flashing a stock RUU, but not sure if it's possible if the phone isn't rooted or s-off. Had your daughter got s-off before the accident? It's important that you only flash the RUU that is next in line from 6.11.841.9 or that exact version as you can re brick you phone if you skip an RUU.
Click to expand...
Click to collapse
Thanks for your help Joeisgood, I am having a look at that thread but as yet can't find the right RUU if there is one there. I am new to the forum as well so it isn't so intuitive to me as yet.
The handset is S-On (from getvars) so I am not sure what to do really. There is a lot of information available on fixing a bricked M7 but honestly, so of it isn't easy to understand and a lot of the guides seem to miss important steps (perhaps through a presumption that you already know/have that bit of info) or are aimed toward phones that are actually still working - such as references to turn on/off USB debugging which of course I can't get to. I haven't found a 'complete', easy to follow, step by step guide to cover my situation.
So I guess, that as the handset won't respond to any of the standard recovery options I am going to have to resort to other means. I am cautious about this - sure I can't make the phone worse than it is really, but there is data on it that I would like to try and recover (yes, I have jumped up and down time and again about backing up phone data!). I am not entirely sure that reloading the firmware will save that data anyway but I would still like to try.
So after all my research I am thinking that what I need to do is:
1. Flash a different recovery onto the phone (TWRP seems the most liked)? What version do I require or just the 'latest' one and how do I tell?
2. Get the Android SDK and in particular the ADB/Fastboot tools (I have the HTC tools, which I used fastboot to query the phone with getvars)? Again do I need a specific version for the M7? How do I know which version I am getting?
3. Use adb sideload to get the RUU (which I have yet to find the correct one) onto the phone? Is the Guru_Reset option the way to go if I can find a version, especiall with S-ON?
Anything else I need to consider or have to hand?
1. Flash a different recovery onto the phone (TWRP seems the most liked)? What version do I require or just the 'latest' one and how do I tell?
As well as S-ON, I assume it is also bootloader locked (as your daughter wouldn't have known/cared to unlock it). Unfortunately, flashing a custom recovery/going S-OFF etc requires unlocking the bootloader ... which means the data is wiped
2. Get the Android SDK and in particular the ADB/Fastboot tools (I have the HTC tools, which I used fastboot to query the phone with getvars)? Again do I need a specific version for the M7? How do I know which version I am getting?
You should already have adb along with fastboot. I do know there's issues with Win 8 so do some reading up on that, I don't have that OS so I can't help.
I don't have much experience with stock recovery, so I'm not sure what you can and can't do in it.
- Do the adb devices, adb shell, adb backup, adb pull commands work while in recovery?
- I think there's a menu option like 'install from phone storage'? When you select that, are you able to see the sdcard folder listing - that will at least confirm the data is still intact?
- If possible, try find the OTA file on the phone (look in the Downloads folder) and re-attempt the update.
3. Use adb sideload to get the RUU (which I have yet to find the correct one) onto the phone? Is the Guru_Reset option the way to go if I can find a version, especiall with S-ON
More bad news, with some hope
- HTC have never issued an RUU (which would wipe the phone so you don't want that) for any Australian version. But users have captured the OTA updates which will patch a phone to the next version
- All the files I uploaded are x.x.980.x while Telstra is x.x.841.x. They will not work on this phone.
- Flashing the Guru Reset requires a custom recovery which requires unlocking your bootloader which requires wiping data :-/
- Try sideloading the OTA from Qhaz. It may not work as you are already on that version, you may need to find the 7.x.841.x OTA
deeevan said:
1. Flash a different recovery onto the phone (TWRP seems the most liked)? What version do I require or just the 'latest' one and how do I tell?
As well as S-ON, I assume it is also bootloader locked (as your daughter wouldn't have known/cared to unlock it). Unfortunately, flashing a custom recovery/going S-OFF etc requires unlocking the bootloader ... which means the data is wiped
2. Get the Android SDK and in particular the ADB/Fastboot tools (I have the HTC tools, which I used fastboot to query the phone with getvars)? Again do I need a specific version for the M7? How do I know which version I am getting?
You should already have adb along with fastboot. I do know there's issues with Win 8 so do some reading up on that, I don't have that OS so I can't help.
I don't have much experience with stock recovery, so I'm not sure what you can and can't do in it.
- Do the adb devices, adb shell, adb backup, adb pull commands work while in recovery?
- I think there's a menu option like 'install from phone storage'? When you select that, are you able to see the sdcard folder listing - that will at least confirm the data is still intact?
- If possible, try find the OTA file on the phone (look in the Downloads folder) and re-attempt the update.
3. Use adb sideload to get the RUU (which I have yet to find the correct one) onto the phone? Is the Guru_Reset option the way to go if I can find a version, especiall with S-ON
More bad news, with some hope
- HTC have never issued an RUU (which would wipe the phone so you don't want that) for any Australian version. But users have captured the OTA updates which will patch a phone to the next version
- All the files I uploaded are x.x.980.x while Telstra is x.x.841.x. They will not work on this phone.
- Flashing the Guru Reset requires a custom recovery which requires unlocking your bootloader which requires wiping data :-/
- Try sideloading the OTA from Qhaz. It may not work as you are already on that version, you may need to find the 7.x.841.x OTA
Click to expand...
Click to collapse
Thanks Deevan.. all useful information and much appreciated as there are lots of different comments and advices out there, hard to know which one is correct.
1. Yes, the phone is Locked and S-ON - never any need to change it until this failed update.. From your comment do I assume that unlocking the phone will wipe all the data? Am I able to sideload an OTA with it locked and S-ON?
2. I am using Win 7 to do all this. Yes, adb is in the same folder as fastboot. Trying the adb devices command in recovery mode returned zilch (nothing lested). I haven't tried those other commands but I will do. Going into Fastboot in recovery I do get a fastboot usb indicator and fastboot devices command returns the handset listed. That is why I was wondering if I needed to unlock it or use something like TWRP to get more recovery options. The Install from Phone storage did nothing that I could see just back to the exclamation mark in a triangle screen.. none of the stock recovery options did anything else.. Maybe the data is already wiped? If it's gone then it's gone. The bright side is that then opens up more options for me to get the handset working again I guess?
3. OK, I will stop looking for an RUU and hunt an 6.x.841.x or 7.x.841.x OTA instead or is the Guru_Reset a better option - there is no need for anything other than what is on the stock device really. A very basic user.
Thanks again for offering your advice, I appreciate it.
A Guru Reset (if one existed for a Telstra phone) is a custom ROM (which just happens to install stock files) and can only be flashed via custom recovery, which you do not have. You can try sideloading an OTA (you can do this locked because it's an official signed package), anything else requires unlocking your bootloader which may affect your warranty with no guarantees it enables you to do anything that would fix the phone. Corruption is highly likely if it died halfway through updating.
If the data is gone, I would accept the replacement phone and go nuts playing with that
It is solved! For the answer look at my post below
Hello guys,
phone HTC one M8 Harman Kardon Edition
Happens that in my urge to unlock my phone sim lock I firstly changed the MID to unlocked SIM Dev edition MID and CID to SuperCID, well that went great until I was dumb enough to try to flash a Dev edition RUU to the phone and then i lost my TWRP recovery and everything went haywire. cause now i try to flash Recovery through fastboot and it suceeds but the phone gets stuck in entering recovery, Im not able to flash a Sprint RUU for HK because 1. i havent found one and 2. it probably wont load because of the MID which is 0P6B1200 if im correct.
please help me either load the Custom recovery so i can have access to adb, or any other way to fix it.
thank you!!
if someone could please give me any ideas, or contact anyone who could help me, it would be greatly apreciated, i can pay up to 20 usd through paypal if anyone can help me!!!
Change your MID back to Sprint and run the Sprint HK RUU...should be good to go.
Nevermind.. As long as you see hboot menu and capable to select different options you are safe and in healthy state.. Even if you want to brk things.. You won't be able to brk.. Just flash twrp 2.8 again using fastboot commands.. You should back on track...
thank you but no
Sarvesh.huddedar said:
Nevermind.. As long as you see hboot menu and capable to select different options you are safe and in healthy state.. Even if you want to brk things.. You won't be able to brk.. Just flash twrp 2.8 again using fastboot commands.. You should back on track...
Click to expand...
Click to collapse
I dont know what is going on but i did that already, even trying the new recovery image, and it gets stuck in the Entering Recovery... step
"Fastboot erase cache" and make sure you are flashing the correct version of twrp(change the MID back to the original one, this is dangerous if there is hardware difference across the 2 MIDs)
Guys all off your help was greatly apreciated but there was something wrong
Ok guys so I was able to fix it.
Although it looked like it was easy to flash the twrp recovery, remember I ran the ATT RUU so the hboot was wrong according to the phone. This means it wouldnt flash the recovery correctly, however something strange happened when i tryed to entered recovery after flashing, it would connect to the computer. When that happened the only thing i thought was that twrp has adb interface, so i instantly checked devices and proceeded to change back the MID. Once that was through i flashed Android 4.4.2 Sprint RUU non HK since the HK was giving unlock issues, then, pasted the Modded HtcOMADM_SPCS.apk and did the
Su am start com.redbend.vdmc/com.htc.omadm.test.TestMainActivity
Then clicked on sim lock
(You must be rooted and check for the moded file in the sim unlock thread on the general section)
And now i was fully funcional and GSM unlocked outside US.
I proceeded then by flashing HK lollipop RUU and then i was back on track.
Hey
jseb14 said:
Ok guys so I was able to fix it.
Although it looked like it was easy to flash the twrp recovery, remember I ran the ATT RUU so the hboot was wrong according to the phone. This means it wouldnt flash the recovery correctly, however something strange happened when i tryed to entered recovery after flashing, it would connect to the computer. When that happened the only thing i thought was that twrp has adb interface, so i instantly checked devices and proceeded to change back the MID. Once that was through i flashed Android 4.4.2 Sprint RUU non HK since the HK was giving unlock issues, then, pasted the Modded HtcOMADM_SPCS.apk and did the
Su am start com.redbend.vdmc/com.htc.omadm.test.TestMainActivity
Then clicked on sim lock
(You must be rooted and check for the moded file in the sim unlock thread on the general section)
And now i was fully funcional and GSM unlocked outside US.
I proceeded then by flashing HK lollipop RUU and then i was back on track.
Click to expand...
Click to collapse
Where do you type the "su ...." command into?
So, I have several international HTC m7s (HTC 802w) at work and I'm trying to flash TWRP on these devices. All of them are at least S-off and some unlocked. This one particular device I'm trying to flash is both s-off and unlocked (but these weren't done by me). Interesting thing is, the twrp flashes normally in fastboot, but when I reboot into recovery, there is black screen only. If I attach usb in this state, computer detects MTP device and I can browse the phone contents and when I run adb devices, it says the device is in recovery. Does this mean twrp is flashed but can't correctly boot into it? What can I do to successfully boot into it?
My HBoot is 2.49 and CID is 11111111.
Edit: Another "interesting" bit. When I open back cover, it indeed says HTC 802w, but installed system is 802t.
asakurato said:
So, I have several international HTC m7s (HTC 802w) at work and I'm trying to flash TWRP on these devices. All of them are at least S-off and some unlocked. This one particular device I'm trying to flash is both s-off and unlocked (but these weren't done by me). Interesting thing is, the twrp flashes normally in fastboot, but when I reboot into recovery, there is black screen only. If I attach usb in this state, computer detects MTP device and I can browse the phone contents and when I run adb devices, it says the device is in recovery. Does this mean twrp is flashed but can't correctly boot into it? What can I do to successfully boot into it?
My HBoot is 2.49 and CID is 11111111.
Click to expand...
Click to collapse
Are you sure your twrp img is the one for the 802 model? Because the versions you'll find linked everywhere in this forum section is for the 801 model (the single sim variant).
The dual sim twrp versions are there:
https://twrp.me/htc/htconem7dualsim.html
Edit: Another "interesting" bit. When I open back cover, it indeed says HTC 802w, but installed system is 802t.
Click to expand...
Click to collapse
Someone probably converted this phone from w to t. You can dump the mfg partition to look at the original MID/CID if you really want to know what it was when it shipped from the factory.
alray said:
Are you sure your twrp img is the one for the 802 model? Because the versions you'll find linked everywhere in this forum section is for the 801 model (the single sim variant).
The dual sim twrp versions are there:
https://twrp.me/htc/htconem7dualsim.html
Someone probably converted this phone from w to t. You can dump the mfg partition to look at the original MID/CID if you really want to know what it was when it shipped from the factory.
Click to expand...
Click to collapse
Damn, so that's where I was messing up. I even read getvar multiple times, but somehow didn't pay attention that codename is cdtu. And no, I'm not interested what was shipped from factory, I just thought it had something to do with not being able to boot into twrp.
Another question then. What roms can I flash on cdtu? I have tried AICP from M7 forum, but it ended with error 7.
Edit: Can you tell me how to convert it back to 802w?