Related
Detailed in this post is a way to downgrade your Incredible S Hboot version 1.16 and above to version 1.13 so it can be s-offed using revolutionary. This is made possible with the TacoRoot exploit, an unsecured kernel, misc_version_universal and an automated goldcard algorithm.
Please note that phones with the latest ICS hboot (2.02 currently) will have to be bootloader UNLOCKED from htcdev.com. If your hboot 2.02 phone does not have an unlocked bootloader, do NOT run this script.
(Insert usual disclaimer: not responsible for your bricked phone blah blah etc).
Beware also that you will lose everything on the phone so back it all up if necessary.
Always make sure the script has completed without error before continuing with the RUU downgrade.
Requires:
MicroSD card (2GB,4GB or 8GB recommended).
Windows PC.
HTC Sync (Installed then uninstalled for ADB drivers).
View attachment IncS_MVDTKv3.4.1.zip [highlight]Link to post, not attachment. No mirrors please.[/highlight]
RUU used for downgrade, model number PG3213000(Typical IncS)
Dropbox Mirror
Alternate RUU for Canadian Bell or South American IncS users, model number PG3212000
Dropbox Mirror
Procedure:
Extract all the files from the downgrade toolkit to your PC and run runme.cmd, following the instructions on screen. The only inputs you should be required to make are:
1. Answering y or n at the prompts
2. Rebooting your phone out of recovery (also when/if prompted)
You may receive this error during the script operation "rm failed for /data/data/recovery/log, No such file or directory" This error can be disregarded.
Then run the RUU Downgrade (takes a while, around 10 mins so be patient).
When its finished running, you can verify if you have 1.13.0000 hboot by entering hboot (power on phone + vol down).
Then you can run revolutionary to get your s-off!
Video Guide kindly provided by locn:
Use on stock ICS device
Part 1. This video goes through the process of down grading HBOOT to 1.13.0000 so that we can then use revolutionary method to gain S-OFF.
http://youtu.be/PbwE6pXOdco
Part 2. This video covers how to get S-OFF on the HTC IncS using revolutionary method.
http://youtu.be/alSEpJMJrjo
Support: (Before asking for help make sure you read and follow the instructions in both the procedure and the script)
While every possible precaution has been taken to ensure the script works on all versions of our phone under all windows environments, there is a possibility that you may get stuck on a step and require assistance. To make this process go as quickly as possible for both parties, please include the following information when requesting help:
A full output of the script, either by screenshot or copy/paste
The operating system specifics: hboot version, stock or custom(provide name) recovery or Rom and if the phone is rooted
(optional)An output of the command "fastboot getvar all" deleting imei and serial no.
Changelog:
v3.4.1 Corrected syntax causing errors for rooted users
v3.4 Added option for users on stock ICS hboot (2.02)
v3.3 Fixed main version downgrade and goldcard creation issues for some users & other minor fixes
v3.2 Repackaged and re-encoded in windows environment for compatibility issues
v3.1 Fixed issue with gold card creation on non-rooted phones
v3.0 Changed temp root method to TacoRoot changed misc_version to misc_version_universal & other minor fixes
v2.1 Changed downgrade version to help prevent user error & other minor fixes
v2.0 Added goldcard script and relock bootloader for users unlocked via htcdev
v1.1 Added option in batch file for rooted and non-rooted users
v1.0 original upload
Credits:
tpbklake: For his unsecured kernel
jcase: Author of TacoRoot
hyuh: For misc_version_universal
viperbjk from RevSkills: For the goldcard algorithm.
GenePoole: For the android goldcard binary.
Revolutionary Team: For s-off Hboot.
And to everyone who contributed. If I have missed anyone that would like to be credited on this guide, pm me and I will be happy to oblige.
Just ran through the process, worked flawlessly. S-OFF at last!
Forgot to try without creating the Goldcard so can't confirm that one.
Thanks again NonVerbose.
Just to confirm, the gold card is required.
So happy to finally have s-off. Very annoying not being able to use OTA updates.
Cheers for the confirmation st.matt. I'll edit the guide.
Can this method of downgrading to HBoot 1.13 be used after unlocking the HBoot 1.16 via HTC method?
There should be no problems using this downgrade with unlocked boot. Be aware though that when downgraded, the 1.13 may be locked... until you use revolutionary of course
Have to try this on my girlfriend's IncS. Haven't had any luck making goldcards though.. never seems to work for me
Should be able to restore her nandroid backup once it's all done though, right?
tangcla said:
Have to try this on my girlfriend's IncS. Haven't had any luck making goldcards though.. never seems to work for me
Should be able to restore her nandroid backup once it's all done though, right?
Click to expand...
Click to collapse
Yes, as soon as the s-off process is complete you can restore nandroid or any other backup with no fear of losing s-off.
Cant seem to get it working
Hey guys, I gave this a try last night with no success.
I have 2 IncS, 1 came with HBOOT 1.13, and the other 1.16. I have made a gold card in the past for my first IncS so that I could get temp root access and upgrade using an RUU without issues, but this time i ran into a few problems.
The second IncS has been unlocked via HTC dev, is rooted and has ARHD 1.19 on it (HBOOT 1.16)
Followed the guide exactly as described, but when I got to the point of running the IncS downgrader, there were a couple of errors (sorry, forgot to note them down), but by the time the process got to the end, it reported that is completed successfully?
When I ran the RUU, it said i was upgrading from 2.30.405.1 to 2.30.405.1? I was expecting to see from version 1? I got an error pretty soon saying I need to use the correct RUU to upgrade, and couldn't get any further.
So then I ran the downgrader again, but half way it got stuck in a boot loop. I left it alone, and 5 mins later, the batch file completed (without errors), but remained in the boot loop. I waited another 10, but it never left the boot loop, so I continued with the RUU upgrade. This time it told me i was upgrading from version 1 to 2.30.405.1, it got a little further (deleting user data, then sending....), but stopped again.
Removed battery, rebooted into fastboot mode. Ran the downgrader again, and it completed successfully without any issues! Ran the RUU, this time it got a little further again, it told me it was deleting user data, then sending.......
Eventually it threw another error, and remained on the black screen with the HTC logo (no progress bar, and nothing in the corners either)
I removed the battery and booted into bootloader. It went into what looks like the usual bootloader screen, only the following message was displayed:
ruu error
Security Check Failed!
At this point i thought I would have to restore the nandroid backup i made before beginning this process, but when i put the original micro SD card in and booted normally, the rom was exactly as i left it!
I did this on Windows 7, with all drivers installed (I use this notebook for android app development, so I know the SDK and drivers are complete, and my first IncS is used for debugging apps), and I used a very old 256Mb micro SD card to create the gold card.
I know it's a lot to ask, but any help would be appreciated.
Thanks for the feedback arhidi, sorry to hear that you're having problems.
arhidi said:
Removed battery, rebooted into fastboot mode. Ran the downgrader again, and it completed successfully without any issues! Ran the RUU, this time it got a little further again, it told me it was deleting user data, then sending.......
Eventually it threw another error, and remained on the black screen with the HTC logo (no progress bar, and nothing in the corners either)
I removed the battery and booted into bootloader. It went into what looks like the usual bootloader screen, only the following message was displayed:
ruu error
Security Check Failed!
At this point i thought I would have to restore the nandroid backup i made before beginning this process, but when i put the original micro SD card in and booted normally, the rom was exactly as i left it!
Click to expand...
Click to collapse
Security check failed points to a problem with the goldcard try creating it again using the steps in the guide.
Try turning fast boot mode off if you haven't already (Settings » Power » Fastboot)
Please run the downgrader while the phone is booted normally (charge mode) as the temproot could be negated between leaving fastboot and booting the rom.
I'm assuming you are using a stock rom, the RUU should be reporting that you are "upgrading" from a higher version to a lower version.
One last thing, the phone should not be rebooting through the main version downgrading process (runme.bat) if it does please run it again before continuing to the RUU downgrade step.
If you receive errors in the main version downgrade, please note them and report back.
Good luck
Edit: sorry didn't see you're rooted and running custom rom
An alternative to running the runme.bat you can just copy the misc_version to your ADB folder and enter the following commands:
Code:
adb push misc_version /data/local/tmp
adb shell
chmod 777 /data/local/tmp/misc_version
/data/local/tmp/misc_version -s 1.00.000.0
exit
Then run the RUU
Nonverbose said:
Security check failed points to a problem with the goldcard try creating it again using the steps in the guide.
Click to expand...
Click to collapse
I have a spare 2Gb micro SD, I'll try creating a gold card with that instead.
Nonverbose said:
Edit: sorry didn't see you're rooted and running custom rom
An alternative to running the runme.bat you can just copy the misc_version to your ADB folder and enter the following commands:
Code:
adb push misc_version /data/local/tmp
adb shell
chmod 777 /data/local/tmp/misc_version
/data/local/tmp/misc_version -s 1.00.000.0
exit
Then run the RUU
Click to expand...
Click to collapse
I'll try that instead, was going to look at those scripts but then ran out of time.
Thanks again.
No problem, let me know how it goes. The guide was actually written for stock ROM but it should be able to work with custom.
ERROR [155]: UNKNOWN ERROR
The ROM Update Utility cannot update your Android phone.
Please get the correct ROM Update Utility and try again
arhidi said:
ERROR [155]: UNKNOWN ERROR
The ROM Update Utility cannot update your Android phone.
Please get the correct ROM Update Utility and try again
Click to expand...
Click to collapse
Can you restore back to stock rom? The ruu must be checking the installed from before it updates.
If you're getting error 155 and your gold card definitely works then try going into fastboot before starting the RUU downgrade.
st.matt said:
If you're getting error 155 and your gold card definitely works then try going into fastboot before starting the RUU downgrade.
Click to expand...
Click to collapse
How do we know if the goldcard definitely works?
tangcla said:
How do we know if the goldcard definitely works?
Click to expand...
Click to collapse
As far as I know there's no software to verify the creation of the gold card. The only way to know for sure is if the card mounts properly and works with the ruu downgrade.
Ok - it's sending now... let's hope it works!
---------- Post added at 10:19 PM ---------- Previous post was at 10:11 PM ----------
tangcla said:
Ok - it's sending now... let's hope it works!
Click to expand...
Click to collapse
It worked! Yay!
Heh, congratz
tried with 2 different sd cards and cannot finish the process with the RUU
ERROR [155]
followed all the instructions and recomendations without success
i unlocked the bootloader previously, maybe is related
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
Hi all! First of all I'm sorry if this has been asked previously but after 3 hours of searching I was unable to find a straight answer and I have tenths of bookmarks opened...
Right so, just got my "new" (used) phone delivered today. 6 months old, currently running stock 4.4.2 with Sense 6.0 under the GiffGaff network. Straight away I went and tried to flash a new ROM onto it (flashed a few roms previously to my HTC Sensation with no problems). So just the usual routine: fastboot > HTCdev > get token ... and here where the first problem occurred. I couldn't get the token as I was getting the following error:
(bootloader) [ERR] Command error !!!
OKAY [ 0.010s]
finished. total time: 0.010sRestarting the phone/PC didn't help, changing USB debug on/off also didn't help. Fastboot unlock oem command didn't work either as it gave me the same error. So I went and downloaded the Hasoon2000's AIO tool to see if that will work but again no luck. When hitting the "Get Token ID" I get an error that the phone is offline - . - . So I had a little search on the net and found out that maybe it's due to my HBOOT version which is 1.57 and is S-ON . However I have no idea how to change that nor if it'll actually solve my problem and I don't want to do anything outside the box so that I don't get my phone bricked.
Any ideas what might be wrong/what am I doing wrong/solutions? I'm clueless at the moment and about to run out of patience... Any help is more then welcome
bboybtek said:
(bootloader) [ERR] Command error !!!
OKAY [ 0.010s]
finished. total time: 0.010sWhat was the exact command?
Click to expand...
Click to collapse
changing USB debug on/off also didn't help.
Click to expand...
Click to collapse
usb debug doesn't matters in bootloader, only in the OS or in recovery for adb commands.
Fastboot unlock oem command didn't work either
Click to expand...
Click to collapse
this command is blocked, so it will not work.
So I went and downloaded the Hasoon2000's AIO tool
Click to expand...
Click to collapse
Hasoon2000 did a great job with his toolkit, but I recommend (and many others) not using toolkits. use fasboot and adb directly from the command window, much better when you are trying to find what doesnt work. Be sure to have the latest sdk on your computer, and latest htc drivers. Also make sure to use 2.0 usb ports, not 3.0
I get an error that the phone is offline
Click to expand...
Click to collapse
What is the output of "fastboot devices" ?
So I had a little search on the net and found out that maybe it's due to my HBOOT version which is 1.57 and is S-ON
Click to expand...
Click to collapse
not sure about that, I really doubt you can't unlock bootloader because of hboot 1.57.
Any ideas what might be wrong/what am I doing wrong/solutions?
Click to expand...
Click to collapse
follow this guide:
Thanks for the reply mate. I watched the video again but I had no luck. However, thanks to that video I went and downloaded the huge SDK archive from HTC site. Instead of using the small archive with "essential" files for the adb, I used the one from HTC site (it has many more files in adb folder) and guess what, it worked! Now, I'm very happy that I finally unlocked it but my question now is, why didn't it work with just the "essential" files? All tutorials videos/forum posts etc. mentioned just the 4 files and not the big HTC package so if it wasn't for the fact that I was desperate I don't think I would of ever unlock this biatch...
Right, instead of creating a new thread I'm just going to ask here. So I successfully unlocked the device and using this video I tried to root the phone. Everything went smoothly, all successful and so on. However when I downloaded the root checker it gives me a message saying the the device is not properly rooted . I then tried with firewater s-off but no luck here either. I've attached the image of how my cmd looks when trying the firewater method. I really thought it's going to be a bit easier to flash this phone... Any advice here guys?
Edit: I just realised that the phone is still S-ON...how did this happen even tho I successfully installed everything that's required...?
Edit2: Tried the temp-root method with firewater but even this doesn't work. I'm getting an error and fail messages (image attached). I think I've run out of ideas here :/
bboybtek said:
Right, instead of creating a new thread I'm just going to ask here. So I successfully unlocked the device and using this video I tried to root the phone. Everything went smoothly, all successful and so on. However when I downloaded the root checker it gives me a message saying the the device is not properly rooted . I then tried with firewater s-off but no luck here either. I've attached the image of how my cmd looks when trying the firewater method. I really thought it's going to be a bit easier to flash this phone... Any advice here guys?
Edit: I just realised that the phone is still S-ON...how did this happen even tho I successfully installed everything that's required...?
Edit2: Tried the temp-root method with firewater but even this doesn't work. I'm getting an error and fail messages (image attached). I think I've run out of ideas here :/
Click to expand...
Click to collapse
first, why are you trying to s-off? s-off is not required to flash custom roms (except for GPE roms), only an unlocked bootloader and a custom recovery (twrp 2.6.3.3) are needed. You definitively need a fully rooted phone to use firewater and an unsecured kernel would also help. Btw almost all custom roms out here are pre-rooted, so just flash a rom and you'll be fine.
and that video you have linked is very outdated, twrp 2.5.0.0 lol. just flash twrp 2.6.3.3 and then boot in recovery. Quit the recovery and you'll be prompted to install root.
but anyway, is your goal is to flash a custom rom, you don't need to root before, they are all (almost) pre-rooted.
alray said:
first, why are you trying to s-off? s-off is not required to flash custom roms (except for GPE roms), only an unlocked bootloader and a custom recovery (twrp 2.6.3.3) are needed. You definitively need a fully rooted phone to use firewater and an unsecured kernel would also help. Btw almost all custom roms out here are pre-rooted, so just flash a rom and you'll be fine.
and that video you have linked is very outdated, twrp 2.5.0.0 lol. just flash twrp 2.6.3.3 and then boot in recovery. Quit the recovery and you'll be prompted to install root.
but anyway, is your goal is to flash a custom rom, you don't need to root before, they are all (almost) pre-rooted.
Click to expand...
Click to collapse
I got lost a little bit with all the tutorials I found, that's why I thought I need s-off lol. I know the video is a bit old that's why I used twrp 2.7.1.1 with SU 3.2 . I'm planning on installing ViperOne rom so I'm just going to go ahead and try that and hopefully everything will be working. Thanks again for the reply mate
bboybtek said:
I got lost a little bit with all the tutorials I found, that's why I thought I need s-off lol. I know the video is a bit old that's why I used twrp 2.7.1.1 with SU 3.2 . I'm planning on installing ViperOne rom so I'm just going to go ahead and try that and hopefully everything will be working. Thanks again for the reply mate
Click to expand...
Click to collapse
Make a backup using TWRP first..
Also the file you should have used should be SuperSU-2.02.. but if you are going to flash a new rom, point is moot.
SaHiLzZ said:
but if you are going to flash a new rom, point is moot.
Click to expand...
Click to collapse
yeah I've installed a new rom and everything is running perfectly fine! Thanks for the tips chaps!
Please read and understand the guide and accompanying links in their entirety before beginning.XDA and I am not responsible for anything you do to your phone.
This guide should work for anyone trying to RUU their phone, but let me give you my background on this first.
While trying to run an RUU to reset my phone, I kept running into an issue: "htc_fastboot.exe has stopped working". I could get my phone to restart, but the RUU would not run successfully. I searched this site and the internet for an answer, but could not find anything that worked for me. Also, a lot of people in Q&A tend to have issues getting the RUU to work. That's why I'm writing this guide. Hopefully someone who is having trouble will search and stumble across it. I tried everything I could find - Windows 7, 8.1, different RUUs, etc and this is how I finally fixed it. I am s-off by the way and did this in Windows 8.1 Update so the guide is written from that perspective.
Steps:
1. Make sure that your computer can see your phone when you boot into fastboot. It should say Fastboot in red that changes to Fastboot USB when plugged into your computer. There are guides that help with this, so I'm not going to go into much detail. Basically you install HTC Sync to your computer and then uninstall it but leave the drivers.
2. Get a copy of fastboot and ADB. The easiest way is to get the SDK from Google (tools only) as it also includes drivers, but you can get just fastboot and adb from here (I did not use this tool personally).
3. To verify that your phone and computer are talking, open a command prompt window (I always open as administrator) and go to the folder that contains fastboot. Type "fastboot devices" (no quotes) and it should list your phone. If it does not, something did not work right with steps 1 and 2.
4. If you are s-off, you do not need to lock the bootloader. If you are s-on, then you need to lock the bootloader by typing "fastboot oem lock" (again, no quotes).
5. Download the Full Firmware from RUU here. While you're there, get the RUU as well. Make sure to get the one that is not decrypted (first link). Copy both into the folder with fastboot.
6. Flash the firmware file using fastboot following the directions in the OP from where you got it. To summarize, rename the firmware zip file to firmware.zip. Then at a command prompt, type "fastboot oem rebootRUU". When the phone shows a black screen that says HTC, type "fastboot flash zip firmware.zip". The command prompt window will show a bunch of stuff as it does its thing. When you get back to the command prompt, it's finished. At this point, type "fastboot reboot-bootloader" to restart back into the (hopefully now stock) bootloader. Personally, I had to repeat the last command again because it failed the first time.
7. At this point, you should be in the stock hboot. It should say fastboot USB in red. Now time to RUU.
8. The current RUU is an exe so run the RUU you download before (if you have a zip file, unzip the RUU and run ARUWizard.exe). I personally ran it as an administrator just to make sure limited privileges didn't cause an issue. Read each screen and keep clicking next. Eventually it will do its thing. It takes about ten minutes and sometimes seems to be frozen. Have patience grasshopper.
And that's it. I'm now running pure stock (not for long I'm sure), still s-off. If you are s-on, you will have to unlock your bootloader again.
Good luck!
I'll be the first to troll post in this guide
Nice work brother.
I've noticed the newer RUU's (M7 and M8) require you to have the matching hboot to run correctly even if your device is s-off.
I didn't know what it meant in step 8 to "unzip the RUU" since my RUU was an EXE file that could not be unzipped. After step 7, I just ran the RUU executable and it ran as expected. I was able to run everything else just like the steps say, but for step 8 I just ran the RUU executable I had downloaded for my Sprint HTC One.
Thanks for the guide!
kushanson said:
I didn't know what it meant in step 8 to "unzip the RUU" since my RUU was an EXE file that could not be unzipped. After step 7, I just ran the RUU executable and it ran as expected. I was able to run everything else just like the steps say, but for step 8 I just ran the RUU executable I had downloaded for my Sprint HTC One.
Thanks for the guide!
Click to expand...
Click to collapse
You're welcome. Glad it helped. Also, thank you for the heads up about the RUU being an exe now. It was a zip file when I wrote the guide. I've fixed the guide to reflect the change.
Dude...
I was soft bricked for about an hour until I found this. It seems fairly obvious to me now, but for some reason I had thought that only flashing the full_firmware zip in fastboot would suffice. I guess the tiny file size (80MB unzipped???) should have tipped me off.
Regardless, I'm back up and running. Thanks, coal.
i am getting error bootloader signature failed how to fix please
rajnshubham said:
i am getting error bootloader signature failed how to fix please
Click to expand...
Click to collapse
I'm guessing you are s-on. If so, you cannot flash the firmware file (I'm s-off and wrote the guide from that perspective). You most likely can just skip that step and run the ruu.exe.
coal686 said:
This guide should work for anyone trying to RUU their phone, but let me give you my background on this first.
Good luck!
Click to expand...
Click to collapse
Thanks for your guided I was able to fix an old One that I had laying around, thanks again
coal686 said:
I'm guessing you are s-on. If so, you cannot flash the firmware file (I'm s-off and wrote the guide from that perspective). You most likely can just skip that step and run the ruu.exe.
Click to expand...
Click to collapse
i think the problem was due to same hboot error. i get to know this thing few days back. anyway thanks coal686. now i updated with the ruu having hboot 1.56 and now i m on kitkat 4.4.2 stock. i can update now to higher ones. thanks buddy
I want to make sure I understand something in the steps. I know the first step is to fastboot the full firmware ruu but then comes something I'm not sure about. Do I follow that up with the. exe file?
I am s-off with 1.60.
Sent from my HTCONE using XDA Free mobile app
biker57 said:
I want to make sure I understand something in the steps. I know the first step is to fastboot the full firmware ruu but then comes something I'm not sure about. Do I follow that up with the. exe file?
I am s-off with 1.60.
Sent from my HTCONE using XDA Free mobile app
Click to expand...
Click to collapse
Thanks for using my guide!
The first step is to flash the "full firmware from RUU" (it's actually labelled that way in the OP of the linked post). It's only the firmware, not the full RUU. Then, follow that up with the .exe file which is the entire RUU. For some reason, the RUU wouldn't run for me without flashing the firmware first.
Since you are already on hboot 1.6, you probably don't have to flash the firmware first, but I'd do it just to be safe.
I normally think of a. exe file as executable. Is this something I can run or need to fastboot?
Sent from my HTCONE using XDA Free mobile app
biker57 said:
I normally think of a. exe file as executable. Is this something I can run or need to fastboot?
Sent from my HTCONE using XDA Free mobile app
Click to expand...
Click to collapse
Just run it. Fastboot flash the firmware then just run the RUU exe.
Just wanted to report that I had the same problem with htc_fastboot.exe stopped working error and I was stuck on 3.22.1540.1 JB and there was no way on upgrading my software because OTAs would download but I would get a red mark when installing. So I skkipped most of your steps because I was not rooted or unlocked, I was all stock but reflashed the same software I was on, 3.22.1540.1 zip and did it twice since first time I got FAILED message in ADB. Once my phone restarted I tried flashing a newer RUU and still got htc_fastboot.exe error on KK and LP RUUs so just for luck tried downloading OTA from the phone but this time it DID install. So I upgraded to 4.15.1540.9 and currently downloading 4.19.1540.4. Hopefully everything goes right and I can get LP running on my phone.
cowboysgz said:
Just wanted to report that I had the same problem with htc_fastboot.exe stopped working error and I was stuck on 3.22.1540.1 JB and there was no way on upgrading my software because OTAs would download but I would get a red mark when installing. So I skkipped most of your steps because I was not rooted or unlocked, I was all stock but reflashed the same software I was on, 3.22.1540.1 zip and did it twice since first time I got FAILED message in ADB. Once my phone restarted I tried flashing a newer RUU and still got htc_fastboot.exe error on KK and LP RUUs so just for luck tried downloading OTA from the phone but this time it DID install. So I upgraded to 4.15.1540.9 and currently downloading 4.19.1540.4. Hopefully everything goes right and I can get LP running on my phone.
Click to expand...
Click to collapse
.
Thanks
Device not recognized
Whenever I plug in my device and go to fastboot, my computer tells me "USB Device not recognized". I've installed the drivers from HTC, I even went to Decide manager on my PC to see if the device appears at all. It shows on the top under "Android USB Device" and it's labeled "My HTC" but it has the error symbol on it, so o deviced to unistall the driver and install it manually. It said that I already had the correct driver.
The reason I'm trying to do all this is, back in 2013 I had put Viper ROM on my device, it worked great, I also installed cyanogen mod as well and that worked great, at the time I wanted to have the double tap to wake feature, so I installed a custom Kernel to allow that. When I had booted up my phone the HTC logo didn t go away, then the lock screen showed up, I unlocked my phone, the HTC logo was still there, then my home screen finally opened and some apps wouldn't open. Then it would restart, so I rebooted it and it would do the same thing, turn on, show the HTC, start then restart. I could go into recovery fine, Install updated version of rom, and the same problem persists
Is there any reason the RUU exe file would stop working only two screens in? I basically run it, accept the terms, click next... then nothing....... what SHOULD it be doing? Best, Rich
krakora said:
Is there any reason the RUU exe file would stop working only two screens in? I basically run it, accept the terms, click next... then nothing....... what SHOULD it be doing? Best, Rich
Click to expand...
Click to collapse
I meant to add this to my guide and didn't get around to it. You're missing a Visual C++ 2008 runtime. See this thread:
https://forum.xda-developers.com/sprint-htc-one/help/solved-ruu-starts-disappears-accepting-t3224469
coal686 said:
I meant to add this to my guide and didn't get around to it. You're missing a Visual C++ 2008 runtime. See this thread:
https://forum.xda-developers.com/sprint-htc-one/help/solved-ruu-starts-disappears-accepting-t3224469
Click to expand...
Click to collapse
Thanks so much Coal, that absolutely worked. The RUU exe runs for me, but getting 155 unknown error. Evidently its not the right RUU for my device. My bootloader is "relocked" already, S-on. So confusing. When I was following the directions on the guide, when flashing the firmware, I was getting the 12 missing signatures error also, I'm assuming its not reading it as an HTC signed firmware. Any ideas on my next direction? Best, Rich
Hi - I've spent a lot of time googling and going round in circles, so I'm sorry if this is answered somewhere.
I have switched an AT&T-branded M7 to T-mobile. After updating apns, everything is good EXCEPT hotspot/tethering. AT&T have custom apps in there that force the hotpot to hit the AT&T network - and therefore fail. I have tried Foxfi (says not supported), tried to run HTC's T-Mobile RUU after booting phone in fastboot (got error code 130) ... and am now confused as to what I should try next. It seems like the ideal would be to just put a T-mobile ROM on instead of the current AT&T one? I am hoping that someone can confirm this is a correct way to go, and then [hopefully] give me a couple of broad directions on what I need to do ... would it be the following: (1) unlock bootloader, (2) get root access, (3) flash different ROM. Or if there is a better option, please advise.
Any help much appreciated ... I have learned a lot, but also realize I still know so little ... it is frustrating, don't really have time with two children etc.
Android v4.4.2
HTC Sense V6.0
Software # 5.12.502.2
HTC SDK API Level: 6.20
Thank you!
adyoung70 said:
Hi - I've spent a lot of time googling and going round in circles, so I'm sorry if this is answered somewhere.
I have switched an AT&T-branded M7 to T-mobile. After updating apns, everything is good EXCEPT hotspot/tethering. AT&T have custom apps in there that force the hotpot to hit the AT&T network - and therefore fail. I have tried Foxfi (says not supported), tried to run HTC's T-Mobile RUU after booting phone in fastboot (got error code 130) ... and am now confused as to what I should try next. It seems like the ideal would be to just put a T-mobile ROM on instead of the current AT&T one? I am hoping that someone can confirm this is a correct way to go, and then [hopefully] give me a couple of broad directions on what I need to do ... would it be the following: (1) unlock bootloader, (2) get root access, (3) flash different ROM. Or if there is a better option, please advise.
Any help much appreciated ... I have learned a lot, but also realize I still know so little ... it is frustrating, don't really have time with two children etc.
Android v4.4.2
HTC Sense V6.0
Software # 5.12.502.2
HTC SDK API Level: 6.20
Thank you!
Click to expand...
Click to collapse
you need s-off to totally convert your phone to t-mobile
try unlock bootloader
flash TWRP 2.6.3.3
fastboot flash recovery openrecovery-twrp-2.6.3.3-m7.img
fastboot erase cache
fastboot reboot-bootloader
From recovery
Flash SuperSU
Flash Bulletproof Kernel
Then get s-off with Firewater
Now you can change CID
fastboot oem writecid T-MOB010
you'll need the MID_Change_1.01.zip
https://www.androidfilehost.com/?fid=23501681358538634
to change the MID to PN0713000
Now you can use the T-mobile RUU
clsA - Thanks for laying all this out. I presume, but can you confirm, that I would use the AT&T version of firewater? (as opposed to the T-Mobile version)
hboot_firewater_ATT_v4.18.502.7.zip
I'll report back with results - just have a little research to do so I understand all the steps.
Thanks again!
adyoung70 said:
clsA - Thanks for laying all this out. I presume, but can you confirm, that I would use the AT&T version of firewater? (as opposed to the T-Mobile version)
hboot_firewater_ATT_v4.18.502.7.zip
I'll report back with results - just have a little research to do so I understand all the steps.
Thanks again!
Click to expand...
Click to collapse
That's hboot. Do not use.
Use firewater, the S-Off software. You should also be able to use a custom ROM like ARHD/Venom/etc.
adyoung70 said:
clsA - Thanks for laying all this out. I presume, but can you confirm, that I would use the AT&T version of firewater? (as opposed to the T-Mobile version)
hboot_firewater_ATT_v4.18.502.7.zip
I'll report back with results - just have a little research to do so I understand all the steps.
Thanks again!
Click to expand...
Click to collapse
SaHiLzZ said:
That's hboot. Do not use.
Use firewater, the S-Off software. You should also be able to use a custom ROM like ARHD/Venom/etc.
Click to expand...
Click to collapse
SaHiLzZ is correct you don't need that hboot at all
just follow the instructions for s-off
the stock rom will s-off just fine with the bulletproof kernel
thanks ...
Thanks clsA and SaHiLzZ - sorry, somehow I ended up on the wrong download page at the firewater site, duh ... so thanks for straightening me out.
I have downloaded everything and will give it a go in the next few days - then report back.
I have seen posts elsewhere with people having the same issue, so I think this thread will serve a good purpose - quite a few switching to t-mob at the moment from AT&T.
You are the best - thank you!!!!!
Thank you both for your help. My AT&T phone is now a T-Mobile phone and hotspot works beautifully!
clsA - I'll send you some beer money in the next couple of days - I think I saw a donate link somewhere.
While I'm sure this would take an expert 20-30 mins or so, it took me a couple of hours, because I was googling as I went and second-guessing the whole way ... but it all went smoothly, albeit slowly. Being a novice, I was a little uncertain when to use adb and fastboot commands, and sometimes I had the device connected when I shouldn't (e.g. I had it in fastboot mode for adb commands and got "error device not found"), and I did not initially realize I had to type "su" at the '#'prompt when installing firewater.
A couple of quick notes to clsA's excellent list:
- download the fastboot and adb drivers, and then uninstall HTC Sync (if you have it) - I had to use a manual method, that included added the path to the environment variables.
... then follow clsA's list, beginning with unlocking your bootloader ... I googled each of his steps - there are plenty of videos/how-to's out there
- the MID_Change_1.01.zip is installed via TWRP in recovery mode, then you pick the option for your carrier install (in my case t-mobile MID=PN0713000).
Thanks again!!
adyoung70 said:
Thank you both for your help. My AT&T phone is now a T-Mobile phone and hotspot works beautifully!
clsA - I'll send you some beer money in the next couple of days - I think I saw a donate link somewhere.
While I'm sure this would take an expert 20-30 mins or so, it took me a couple of hours, because I was googling as I went and second-guessing the whole way ... but it all went smoothly, albeit slowly. Being a novice, I was a little uncertain when to use adb and fastboot commands, and sometimes I had the device connected when I shouldn't (e.g. I had it in fastboot mode for adb commands and got "error device not found"), and I did not initially realize I had to type "su" at the '#'prompt when installing firewater.
A couple of quick notes to clsA's excellent list:
- download the fastboot and adb drivers, and then uninstall HTC Sync (if you have it) - I had to use a manual method, that included added the path to the environment variables.
... then follow clsA's list, beginning with unlocking your bootloader ... I googled each of his steps - there are plenty of videos/how-to's out there
- the MID_Change_1.01.zip is installed via TWRP in recovery mode, then you pick the option for your carrier install (in my case t-mobile MID=PN0713000).
Thanks again!!
Click to expand...
Click to collapse
Good Job ! I'm glad it worked out for you.