This guide is for the T-Mobile HTC One M8. Bootloader Version: 3.16.0.0000
Disclaimer: I am not responsible for your device. You are performing the steps detailed in this post at your own risk. Support for any phone unlocked through this method falls upon you. Assume that this method voids any warranty that may have come with your phone. Also, currently there is no known way to restore the T-Mobile variant to complete stock settings after using HTC Dev Unlock and/or achieving S-Off. Maybe at a later date this could be possible, but not yet.
*Please do not quote this post. It's so long.*
Support for recoveries, firewater, or other tools used herein should be asked in their respective thread or forum.
Firewater does not work on every T-Mobile M8. If, when running firewater, you see "Whelp, this sucks..." firewater will not work on your phone. Right now firewater is the only method to achieve S-Off on our M8 variant.
There was speculation that the phone's build date might be a reference for who's phone was compatible with firewater. This is not the case. There is no correlation between build date and compatibility. A further explanation is given under the S-Off instructions.
This thread is for people that understand what this whole post means. If you are unsure of the terms, please search. The terminology is readily available and nothing should be difficult to find.
I work and go to graduate school, so this thread will be updated periodically, but I will not be able to provide a lot of support. This guide reflects my steps to achieve root and S-Off, and is just intended to give someone new to the phone an easy to read step-by-step guide of what the process will be.
I also hope we can condense the large amount of information floating around about achieving S-Off on our variant into one thread.
Required Files:
HTC Dev Unlock Process:
Google Android SDK zip:
http://developer.android.com/sdk/index.html
Java Runtime Environment:
http://java.com
HTC Sync (Windows Only):
http://www.htc.com/www/help/
Recovery (choose one):
Team Win Recovery Project (TWRP) 2.7.x for GSM Phones
http://teamw.in/project/twrp2/225
PhilZ Touch ClockworkMod (CWM) Recovery
http://forum.xda-developers.com/showthread.php?t=2703223
S-Off:
Firewater
http://firewater-soff.com/instructions/
Firewater M8 Original Thread
http://forum.xda-developers.com/showthread.php?p=51698035
Useful Commands:
adb devices
(after installing adb, this will tell you if your phone is detected by the computer)
expected output:
Code:
C:\sdk\platform-tools>adb devices
List of devices attached
FAXXXXXXXXXXdevice
fastboot devices
(after copying the fastboot utility downloaded during the HTC Dev Unlock process to your sdk\platform-tools\ directory, this will tell you if your phone is detected by the computer)
expected output:
Code:
C:\sdk\platform-tools>fastboot devices
List of devices attached
FAXXXXXXXXXXfastboot
1. Unlock bootloader via HTC Dev Unlock (http://www.htcdev.com/bootloader)
a. At the top of the page, either register for a new account or log in with an existing one
b. Under "Supported Devices" choose "All Other Supported Models"
c. Click "Begin Unlock Bootloader"
d. A prompt will ask you to continue. Read this. If this prompt scares you, stop immediately. Otherwise, press "Yes" to continue
e. Accept the legal terms and conditions.
f. Follow the on-screen steps provided.
Step 1
After powering down, press Volume Down and while pressing Volume Down, press Power holding both buttons to start the device into Bootloader mode. If you have difficulty, power up normally, go to Settings->Battery and deselect Fast boot. Power down and try again.
Step 2
Use the Volume buttons to select up or down. Highlight Fastboot and press the Power button.
Step 3
Connect the device to the computer via a usb cable
Step 4
Download the fastboot binary for your OS using the provided linksg. Follow the on-screen steps provided
Step 5
Open a command Prompt: Windows: Start->"cmd" Mac: Applications->Utilities->Terminal.app Linux: Terminal
Type in Command Prompt: fastboot oem get_identifier_token.
Step 6
You will see a long block of text. Copy and paste this text into the the token field below (in the Windows command prompt: Right Click > Mark > highlight the block of text > Right click to copy. Mac users can use cmd-option to mark and select text.).
When copying the token, start with this line:
>
And end with this line:
>
(Note: Do not copy the INFO or (bootloader) prefix)
Step 7
Paste this string of text into the token field and hit Submit in order to receive your unlock code binary file. You will receive this information in your email.h. After hitting submit, HTC will send you an email. Sender is HTC-Unlockbootloader. Subject is "The key to unlocking your HTC Device."
Email Message:
Hi Recipient
Attached in this mail is your unlock bootloader key file. To use this file to unlock your device, simply follow the remaining instructions on the website to complete the process and successfully unlock your bootloader.
Please remember that unlocking your bootloader may void all or parts of your warranty and your device may not function as intended by HTC. Unlocking the bootloader is for development purposes only.
* Click here to continue the bootloader unlocking process.
The bootloader unlock key file can only be applied to the device with which you generated the token.
Please do not reply to this email which is auto-sent by server.
If you need to contact us with questions please click here.
Sincerly,
HTC
Click to expand...
Click to collapse
Attached to the email is Unlock_code.bin. This is the file you will need to download in order to unlock your bootloader. This file is device specific. You cannot use this file to unlock any other HTC phone. Please do not try as this will probably result in a brick.
Click the link provided in the email to continue the steps to unlock your bootloaderi. Follow the on-screen steps provided
Step 8
You will receive an email with the attachment: Unlock_code.bin. Save this file in the same folder as your fastboot files (For Example: C:\Android).
If, after a short period of time, you have not yet received the mail, or you have received an email from HTC, but does not contain an attached file, it is possible that more stringent spam filters and anti-virus programs will block this mail or attachment.
In order to ensure that you receive the email with the attachment, we suggest you consider using a non-corporate email server as corporate servers tend to have more stringent attachment policies. If you have not received the email at all, please check your spam folder in your email client to check if the email was filtered out.
Step 9
In the command prompt type: fastboot flash unlocktoken Unlock_code.bin. In the command prompt you will see the following message:
Code:
fastboot flash unlocktoken Unlock_code.bin
sending 'unlocktoken' ...
OKAY [ 0.151s]
writing 'unlocktoken'...
unlock token check successfully
OKAY [0.006s]
finished. total time: 0.158s
Step 10
On your phone you will now see the disclaimer. Please read this carefully as this action may void your warranty. Use the Volume buttons to highlight your choice, and the Power button to make your selection. If you select Yes, your phone will be reset to its’ factory default settings, and your bootloader will be unlocked. If you select No, your phone will reboot and no modifications will have been made.
Step 11
To re-lock your bootloader, in the command prompt, type: fastboot oem lock.
Note: This will not restore the factory default lock, but will simply re-lock the bootloader so no further changes can be made. Furthermore, if you want to unlock your bootloader again, simply repeat step 9 with your original unlock key file to unlock your phone again.j. Congratulations, your phone now has an unlocked bootloader! If your phone hasn't done so already, reboot it and let it sit at the welcome screen for the requisite 5-10 minutes to settle. Turn off your phone, and reboot to HBOOT with volume down + power button. Select fastboot.
2. Install a custom recovery
As far as I know, there are two recoveries that are fully functional with our M8 variant:
TWRP
PhilZ Touch CWMa. Download your chosen recovery from the above links.
b. Rename it recovery.img
c. Drop it in the same folder as your adb and fastboot binaries.
d. After booting to fastboot mode, make sure your device is still plugged in and run the following command in your command window:
fastboot devices
Your computer shouldn't have any troubles recognizing your phone since we just went through the bootloader unlock, but it's always best to be safe.e. Now run the command:
fastboot flash recovery recovery.img
Expected output:
Code:
C:\sdk\platform-tools>fastboot flash recovery recovery.img
sending 'recovery' ...
OKAY [ 0.871s]
writing 'recovery'...
OKAY [ 1.501s]
finished. total time: 2.543s
f. Congratulations! You now have a custom recovery installed.
g. I recommend immediately making a backup of your fresh operating system (pre-root) by selecting HBOOT from the fastboot menu, then selecting and booting into recovery
h. After booting into your new custom recovery select backup from your list of options and proceed to select your backup location (internal or micro sd) and continue to the backup. It will be quite large, but this will provide you a good starting point should you ever need to restore to factory settings for any reason.
i. I use TWRP, because it will automatically prompt you to install root and SuperSU upon rebooting from recovery.
I am unsure how to achieve root after flashing PhilZ Touch. If anyone provides the info I will add it to this guide.
3. Achieve S-Off (Hopefully!)
The instructions to attaining S-Off are listed on the firewater s-off page linked above. They are really comprehensive and you should follow them to the letter. Make sure that you read through their prerequisites as well.
Note: On prerequisite number four, it states that you must be "HTCDEV unlocked/rooted." Please read this as you must be HTCDEV unlocked AND rooted.
I didn't want to post the firewater team's instructions here (I didn't ask permission yet), so this section will be more for information regarding the S-Off process that I have gathered from other threads and this one going forward.
Issues seen with Firewater:
Firewater does not work on every T-Mobile M8. If, when running firewater, you see "Whelp, this sucks..." firewater will not work on your phone.
There was speculation that the build date was an indicator of compatibility with firewater's S-Off method. As several people expected, there is no correlation. There are batches of components that HTC purchased from various manufacturers that vary in compatibility with the firewater exploit. At this point there is no known method to determine if your phone will be compatible with firewater. Unfortunately, it's just a shot in the dark. So, if you're comfortable, give it a shot and hopefully you're compatible.
Issue: Firewater hangs but does not give the "Whelp this sucks..." message:
Possible Solutions: Your device is likely compatible. You must be persistent. Keep trying.
Hit Ctrl+C to exit the exploit and try again starting from "adb reboot" (from @Fenny)
Unplug your USB cable, reboot your phone manually. Once it boots up, plug in your USB cable (from @epsix)
Plug in your USB cable, adb reboot. Once it boots, go to Developer Options and uncheck and recheck USB Debugging (from @epsix)
Install BusyBox (from @renn9420)Issue: After running adb reboot command and pushing firewater phone shows up as "offline"
Possible Solutions: Make sure that you granted su permissions to your adb shell through SuperSU
I had this happen to me. I would go to run the command and suddenly, the phone is disconnected. I ran through the adb reboot steps a couple of times and finally when executing firewater it ran. Went through the steps 3 times before it ran.
4: Other
a. @Fenny noticed that /data/preload/ gets emptied after HTC Dev Unlock. If you're hanging onto your stock ROM and don't plan to change to a custom OS you'll want to replace these files. Go here to replace them: http://forum.xda-developers.com/showthread.php?t=2714522
Thanks go to:
@beaups - firewater
@Dees_Troy - TWRP
@Phil3759 - PhilZ Touch
@Fenny - Stock + ROM, Hacked HBOOT, Preload data & more
@Turge - ViperOneM8
@Chainfire - SuperSU
@jcase - for looking into getting weaksauce working on our phones
FYI I didn't develop firewater, just weaksauce. That is @beaups baby
Sent from my HTC One_M8 using XDA Premium 4 mobile app
jcase said:
FYI I didn't develop firewater, just weaksauce. That is @beaups baby
Sent from my HTC One_M8 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Thanks for the info! Changed in OP.
Your posting title is slightly misleading since a good portion of T-mobiles m8s are not compatible with firewater.
Where do you find the build date
Sent from my HTC One_M8 using XDA Premium 4 mobile app
fryingpan0613 said:
Where do you find the build date
Sent from my HTC One_M8 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
It's on the bottom edge of the box on the same sticker as IMEI.
Sent from my HTC One M8
egcthree said:
Your posting title is slightly misleading since a good portion of T-mobiles m8s are not compatible with firewater.
Click to expand...
Click to collapse
Updated OP to show that firewater may not work without having to show the contents of the S-Off info. Thanks for the comment.
I get the whelp yada yada and my build date is 4/10/14 do I need to have busy box installed?
Sent from my HTC One M8
OctoberNexus said:
I get the whelp yada yada and my build date is 4/10/14 do I need to have busy box installed?
Sent from my HTC One M8
Click to expand...
Click to collapse
Nope. That means that firewater won't work for you and S-Off isn't yet achievable for your phone.
OP updated with your build date.
Sent from my HTC One M8
Hopefully there will be another way in the future until then running GPE ROM which is a lot better than nothing still not what I had in mind when purchasing this thing.
Sent from my HTC One M8
Glad someone condensed everything down into an instructional guide. This should be stickied (if it's not already).
Thanks bro! :good::good:
thanks for writing this up!! got the dang Whelp message tho build date of 04/05/2014 if you want to add that to the list
VolcanicSkunk said:
This guide is for the T-Mobile HTC One M8. Bootloader Version: 3.16.0.0000
Disclaimer: I am not responsible for your device. You are performing the steps detailed in this post at your own risk. Support for any phone unlocked through this method falls upon you. Assume that this method voids any warranty that may have come with your phone. Also, currently there is no known way to restore the T-Mobile variant to complete stock settings after using HTC Dev Unlock and/or achieving S-Off. Maybe at a later date this could be possible, but not yet.
*Please do not quote this post. It's so long.*
Support for recoveries, firewater, or other tools used herein should be asked in their respective thread or forum.
Firewater does not work on every T-Mobile M8. If, when running firewater, you see "Whelp, this sucks..." firewater will not work on your phone. Right now firewater is the only method to achieve S-Off on our M8 variant.
This thread is for people that understand what this whole post means. If you are unsure of the terms, please search. The terminology is readily available and nothing should be difficult to find.
I work and go to graduate school, so this thread will be updated periodically, but I will not be able to provide a lot of support. This guide reflects my steps to achieve root and S-Off, and is just intended to give someone new to the phone an easy to read step-by-step guide of what the process will be.
I also hope we can condense the large amount of information floating around about achieving S-Off on our variant into one thread.
Required Files:
HTC Dev Unlock Process:
Google Android SDK zip:
http://developer.android.com/sdk/index.html
Java Runtime Environment:
http://java.com
HTC Sync (Windows Only):
http://www.htc.com/www/help/
Recovery (choose one):
Team Win Recovery Project (TWRP) 2.7.x for GSM Phones
http://teamw.in/project/twrp2/225
PhilZ Touch ClockworkMod (CWM) Recovery
http://forum.xda-developers.com/showthread.php?t=2703223
S-Off:
Firewater
http://firewater-soff.com/instructions/
Firewater M8 Original Thread
http://forum.xda-developers.com/showthread.php?p=51698035
Useful Commands:
adb devices
(after installing adb, this will tell you if your phone is detected by the computer)
expected output:
Code:
C:\sdk\platform-tools>adb devices
List of devices attached
FAXXXXXXXXXX device
fastboot devices
(after copying the fastboot utility downloaded during the HTC Dev Unlock process to your sdk\platform-tools\ directory, this will tell you if your phone is detected by the computer)
expected output:
Code:
C:\sdk\platform-tools>fastboot devices
List of devices attached
FAXXXXXXXXXX fastboot
1. Unlock bootloader via HTC Dev Unlock (http://www.htcdev.com/bootloader)
a. At the top of the page, either register for a new account or log in with an existing one
b. Under "Supported Devices" choose "All Other Supported Models"
c. Click "Begin Unlock Bootloader"
d. A prompt will ask you to continue. Read this. If this prompt scares you, stop immediately. Otherwise, press "Yes" to continue
e. Accept the legal terms and conditions.
f. Follow the on-screen steps provided.
Step 1
After powering down, press Volume Down and while pressing Volume Down, press Power holding both buttons to start the device into Bootloader mode. If you have difficulty, power up normally, go to Settings->Battery and deselect Fast boot. Power down and try again.
Step 2
Use the Volume buttons to select up or down. Highlight Fastboot and press the Power button.
Step 3
Connect the device to the computer via a usb cable
Step 4
Download the fastboot binary for your OS using the provided links g. Follow the on-screen steps provided
Step 5
Open a command Prompt: Windows: Start->"cmd" Mac: Applications->Utilities->Terminal.app Linux: Terminal
Type in Command Prompt: fastboot oem get_identifier_token.
Step 6
You will see a long block of text. Copy and paste this text into the the token field below (in the Windows command prompt: Right Click > Mark > highlight the block of text > Right click to copy. Mac users can use cmd-option to mark and select text.).
When copying the token, start with this line:
<<<< Identifier Token Start >>>>
And end with this line:
<<<<< Identifier Token End >>>>>
(Note: Do not copy the INFO or (bootloader) prefix)
Step 7
Paste this string of text into the token field and hit Submit in order to receive your unlock code binary file. You will receive this information in your email. h. After hitting submit, HTC will send you an email. Sender is HTC-Unlockbootloader. Subject is "The key to unlocking your HTC Device."
Email Message:
Attached to the email is Unlock_code.bin. This is the file you will need to download in order to unlock your bootloader. This file is device specific. You cannot use this file to unlock any other HTC phone. Please do not try as this will probably result in a brick.
Click the link provided in the email to continue the steps to unlock your bootloader i. Follow the on-screen steps provided
Step 8
You will receive an email with the attachment: Unlock_code.bin. Save this file in the same folder as your fastboot files (For Example: C:\Android).
If, after a short period of time, you have not yet received the mail, or you have received an email from HTC, but does not contain an attached file, it is possible that more stringent spam filters and anti-virus programs will block this mail or attachment.
In order to ensure that you receive the email with the attachment, we suggest you consider using a non-corporate email server as corporate servers tend to have more stringent attachment policies. If you have not received the email at all, please check your spam folder in your email client to check if the email was filtered out.
Step 9
In the command prompt type: fastboot flash unlocktoken Unlock_code.bin. In the command prompt you will see the following message:
Code:
fastboot flash unlocktoken Unlock_code.bin
sending 'unlocktoken' <0KB>...
OKAY [ 0.151s]
writing 'unlocktoken'...
<bootloader> unlock token check successfully
OKAY [0.006s]
finished. total time: 0.158s
Step 10
On your phone you will now see the disclaimer. Please read this carefully as this action may void your warranty. Use the Volume buttons to highlight your choice, and the Power button to make your selection. If you select Yes, your phone will be reset to its’ factory default settings, and your bootloader will be unlocked. If you select No, your phone will reboot and no modifications will have been made.
Step 11
To re-lock your bootloader, in the command prompt, type: fastboot oem lock.
Note: This will not restore the factory default lock, but will simply re-lock the bootloader so no further changes can be made. Furthermore, if you want to unlock your bootloader again, simply repeat step 9 with your original unlock key file to unlock your phone again. j. Congratulations, your phone now has an unlocked bootloader! If your phone hasn't done so already, reboot it and let it sit at the welcome screen for the requisite 5-10 minutes to settle. Turn off your phone, and reboot to HBOOT with volume down + power button. Select fastboot.
2. Install a custom recovery
As far as I know, there are two recoveries that are fully functional with our M8 variant:
TWRP
PhilZ Touch CWM a. Download your chosen recovery from the above links.
b. Rename it recovery.img
c. Drop it in the same folder as your adb and fastboot binaries.
d. After booting to fastboot mode, make sure your device is still plugged in and run the following command in your command window:
fastboot devices
Your computer shouldn't have any troubles recognizing your phone since we just went through the bootloader unlock, but it's always best to be safe. e. Now run the command:
fastboot flash recovery recovery.img
Expected output:
Code:
C:\sdk\platform-tools>fastboot flash recovery recovery.img
sending 'recovery' <14,818KB>...
OKAY [ 0.871s]
writing 'recovery'...
OKAY [ 1.501s]
finished. total time: 2.543s
f. Congratulations! You now have a custom recovery installed.
g. I recommend immediately making a backup of your fresh operating system (pre-root) by selecting HBOOT from the fastboot menu, then selecting and booting into recovery
h. After booting into your new custom recovery select backup from your list of options and proceed to select your backup location (internal or micro sd) and continue to the backup. It will be quite large, but this will provide you a good starting point should you ever need to restore to factory settings for any reason.
i. I use TWRP, because it will automatically prompt you to install root and SuperSU upon rebooting from recovery.
I am unsure how to achieve root after flashing PhilZ Touch. If anyone provides the info I will add it to this guide.
3. Achieve S-Off (Hopefully!)
The instructions to attaining S-Off are listed on the firewater s-off page linked above. They are really comprehensive and you should follow them to the letter. Make sure that you read through their prerequisites as well.
Note: On prerequisite number four, it states that you must be "HTCDEV unlocked/rooted." Please read this as you must be HTCDEV unlocked AND rooted.
I didn't want to post the firewater team's instructions here (I didn't ask permission yet), so this section will be more for information regarding the S-Off process that I have gathered from other threads and this one going forward.
Issues seen with Firewater:
Firewater does not work on every T-Mobile M8. If, when running firewater, you see "Whelp, this sucks..." firewater will not work on your phone.
The speculation is, there are different components used during the builds due to sourcing those components from different companies. It seems that some people believe that the phone build date may indicate the devices that have components that are compatible with the exploit. So we'll document this to try to see who achieved S-Off on which build dates.
Issue: Firewater hangs but does not give the "Whelp this sucks..." message:
Possible Solutions: Your device is likely compatible. You must be persistent. Keep trying.
Hit Ctrl+C to exit the exploit and try again starting from "adb reboot" (from @Fenny)
Unplug your USB cable, reboot your phone manually. Once it boots up, plug in your USB cable (from @epsix)
Plug in your USB cable, adb reboot. Once it boots, go to Developer Options and uncheck and recheck USB Debugging (from @epsix)
Install BusyBox (from @renn9420) Issue: After running adb reboot command and pushing firewater phone shows up as "offline"
Possible Solutions: Make sure that you granted su permissions to your adb shell through SuperSU
I had this happen to me. I would go to run the command and suddenly, the phone is disconnected. I ran through the adb reboot steps a couple of times and finally when executing firewater it ran. Went through the steps 3 times before it ran.
Build Dates S-Off Achieved On:
04/01/2014
04/04/2014
04/07/2014
04/12/2014
Build Dates S-Off Not Achieved On:
04/03/2014 x2
04/08/2014
04/09/2014
04/10/2014
04/11/2014
4: Other
a. @Fenny noticed that /data/preload/ gets emptied after HTC Dev Unlock. If you're hanging onto your stock ROM and don't plan to change to a custom OS you'll want to replace these files. Go here to replace them: http://forum.xda-developers.com/showthread.php?t=2714522
Thanks go to:
@beaups - firewater
@Dees_Troy - TWRP
@Phil3759 - PhilZ Touch
@Fenny - Stock + ROM, Hacked HBOOT, Preload data & more
@Turge - ViperOneM8
@Chainfire - SuperSU
@jcase - for looking into getting weaksauce working on our phones
Click to expand...
Click to collapse
tks
tnez said:
thanks for writing this up!! got the dang Whelp message tho build date of 04/05/2014 if you want to add that to the list
Click to expand...
Click to collapse
Thanks for posting your results. OP updated with your build date.
abutran said:
tks
Click to expand...
Click to collapse
You're welcome. If you don't mind, please edit your post to remove the quote of the OP. It keeps the thread much shorter for people on mobile devices. Thanks.
Sent from my HTC One M8
uoY_redruM said:
Glad someone condensed everything down into an instructional guide. This should be stickied (if it's not already).
Thanks bro! :good::good:
Click to expand...
Click to collapse
Saw your post in the other thread and agreed with you! It was way too many pages to sift through.
Sent from my HTC One M8
Anyone good to go with a build date of 04/01/2014?
donciclon said:
Anyone good to go with a build date of 04/01/2014?
Click to expand...
Click to collapse
My build date is 04/01/2014 and I was able to achieve S-Off. If you try it, let us know the results. We haven't pinned down if the build date is the indicator. I'm hoping like hell it is though.
Sent from my HTC One M8
04/07/2014 build date no go... Got the whelp message as well.
Sent from my HTC One_M8 using Tapatalk
irrelephant said:
04/07/2014 build date no go... Got the whelp message as well.
Sent from my HTC One_M8 using Tapatalk
Click to expand...
Click to collapse
As I've said in the other thread it is the luck of the draw. Assembly date and location have little to do with it. It's a matter of what components were put into your device and that is a matter of what components were available at the time of assembly.
Just because one device was produced with exploitable components on one day doesn't mean another device wasn't produced with unexploitable components on the same day. A run of a particular component can run out at any time. When it does the next available run of components will be used.
Behold_this said:
As I've said in the other thread it is the luck of the draw. Assembly date and location have little to do with it. It's a matter of what components were put into your device and that is a matter of what components were available at the time of assembly.
Just because one device was produced with exploitable components on one day doesn't mean another device wasn't produced with unexploitable components on the same day.
Click to expand...
Click to collapse
That's what I was thinking too. Multiple runs happen on any given day.
I was hoping it would be as simple as the build date. Of course we're not that lucky though. Lol. Whelp.... Back to the drawing board.
Sent from my HTC One M8
Behold_this said:
As I've said in the other thread it is the luck of the draw. Assembly date and location have little to do with it. It's a matter of what components were put into your device and that is a matter of what components were available at the time of assembly.
Just because one device was produced with exploitable components on one day doesn't mean another device wasn't produced with unexploitable components on the same day. A run of a particular component can run out at any time. When it does the next available run of components will be used.
Click to expand...
Click to collapse
Well what information might be of assistance and I will gladly provide it. I'm pretty good with adb, and willing.
Sent from my HTC One_M8 using Tapatalk
Related
Hi there and Welcome to my Ultimate Stock to Custom ROM Awesomeness Thread!
-----
There are still many of people out there who are thinking about Unlocking their Bootloaders, Rooting and installing a custom ROM onto their HTC One X.
I recently did so myself and although I've been a member on XDA for a while now and I rooted my old HTC Sensation I found the process to vary with my HOX.
Now there are many amazing Guides and "How-To's" already out there on XDA but I thought that I'd compile a lot of what's already in those threads and turn all of the yummyness that's already out there on XDA and write this from a first timers perspective.
Disclaimer:- Please note that I'm no expert when it comes to this stuff and I'm not amazing at trouble shooting, if you follow this guide it should turn out fine but if not then this is no fault of my own, you do all of this at your own risk! As I say, it should be fine and you should get through this guide fine. There may be better ways of doing what I'm showing you in this guide but this is how I did it and it worked out okay for me. If you know of a better way the please feel free to state so in the following thread.
-NOTE-
THIS GUIDE IS FOR ICS ROMS ONLY, NOT JB ROMS.
So after that disclaimer relax, read, re-read and take your time and hopefully by the end of this guide you'll have a Custom Rom running on your HOX and without too much panicking and worrying. It's a bit wordy and a bit lengthy but it's an in depth guide.
BEFORE WE START! Go to your HTC One X, Settings, Developer Options and make sure that you've got USB debugging checked! I also always have Fast boot checked in the Power options as well, it's not really important for this guide but I like to know that when I turn my HTC One X off that it is truly off!
Also if you wish you can pop into security and check on 'Allow installation of non-Market apps in Unknown Sources. Again, not really important for this guide but always good to have checked!
---NOTE---
In this guide I talk about using ARHD 9.2, this is because it's the latest version that's been released at the time of writing. Naturally ARHD will be updated but the guide will still be okay to follow.
Lets Get Started!
---
Installing HTC Sync and the Android SDK onto your PC:-
Before we start anything I personally think that it's a good idea to get these two steps out of the way as we're going to need to use these tools a bit later on.
HTC Sync
To install HTC Sync the best way to do this is to follow this LINK and click on the Download link on the right hand side. Follow the Set-Up wizard and get HTC Sync installed onto your PC. Now I'm sure that I don't have to talk you through this step so we'll leave this part now and move onto getting the Android SDK.
Thanks to EddyOS for this recommendation:
EddyOS said:
Better to recommend HTC Sync Manager as that's for the One Series phones...
http://www.htc.com/www/help/htc-one-x/#download
Click to expand...
Click to collapse
So feel free to download either HTC Sync (It's the only version I've personally used), or download HTC Sync Manager as it's designed specifically for the One Series.
Android SDK
Now that you've gotten HTC Sync set-up onto your machine we'll start with the Android SDK, you can find the installation files here: Android SDK For Windows, Click on the "Download the SDK For Windows link.". Let it download the Run the file.
Now to make life a bit easier for us later, when you get to the menu for choosing the Destination of the program we'll alter this for ease of use later. When I'm in set-up it automatically sets the location to
C:\Documents and Settings\James\Local Settings\Application Data\Android\android-sdk
Click to expand...
Click to collapse
We'll change this to:
C:\Android\android-sdk
Click to expand...
Click to collapse
Continue with the install.
Once installed the SDK 'should' open itself, if not then open it from the start menu.
You'll be shown a screen that has a load of options on it and a button at the bottom that says 'Install [X] Packages', Make sure that you have Android SDK and Android SDK Platform Tools checked (See Image).
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
The program will automatically select numerous other options, it's fine to leave these checked. the installation may take some time depending on your PC etc...
Now that's all finished we can move onto something a little more productive!
Backing Up Your Data:-
When I went to Unlock My Bootloader I read that I'd loose my data and I wasn't too happy about this, I came across this thread '[GUIDE] Full Phone Backup without Unlock or Root', which was a life saver, I'll talk you through some of it just so that we can get a backup made but if you want more concise instructions then make the jump to the thread and have a look!
Now, to backup!
Open your Command Prompt, for those of you who don't know how to do this it's Start > Run... > CMD > Okay. Now that you've got your Command Prompt open we'll need to find adb.exe, which should be at this location
C:\Android\android-sdk\platform-tools
Click to expand...
Click to collapse
as this is where we chose the Android SDK to be located when we installed it earlier!
So to find this in the command prompt type in
cd \Android\android-sdk\platform-tools
Click to expand...
Click to collapse
This will take you to that location. (See Image)
Now that we're in the platform-tools part of your PC in command prompt, it's the perfect time to plug in your HOX via USB to your PC, just choose 'Charge Only' for now.
Now back in CMD (command prompt) enter these values:
adb backup -apk -shared -all -f C:\backup\backup20111230.ab
Click to expand...
Click to collapse
Please note that this will create a folder in your C:\ called 'backup', this is where your backup will exist, also please not that you can call your backup whatever you like, it doesn't have to be 'backup20111230.ab' but I prefer to choose the days date, so mine today would be 'backup20082012.ab', 20th August 2012. Once you've typed this into CMD you'll be prompted to unlock your phones screen and continue backup (See Image)
So unlock your phone screen, choose a password (write this down somewhere as you'll need to to replace the backup onto your phone after we've put a custom ROM onto it) let it start to backup!
Now there is a common issue with the backup's freezing at
com.android.sharedstoragebackup
Click to expand...
Click to collapse
If this is the case for you, just unplug the phone, exit out of CMD, plug the phone back in, get back into cd \Android\android-sdk\platform-tools in the CMD and this time alter the backup command so that it reads:
adb backup -apk -noshared -all -f C:\backup\backup20111230.ab
Click to expand...
Click to collapse
All you've done now is change -shared to -noshared, let the backup continue, hopefully it'll complete!
Now that you've got your backup all safely stowed away on your PC it's time to get down to business! Unlocking your Bootloader!
---
Unlock the Bootloader:-
Did you install HTC Sync at the start? As now you're going to need it!
Navigate your web browser to www.htcdev.com/bootloader and click register at the top, complete the registration process, making sure that you use an email address that you have access to.
Once registered make your way back to www.htcdev.com/bootloader and sign-in.
Once signed-in at the supported devices drop down select 'All Other Supported Models' and click on Begin Unlock Bootloader.
Now before we move onto anything else we're going to want the Fastboot Files, which Cursed4Eva is kindly hosting here: Fastboot Files
Once downloaded, on your PC go to the folder C:\Android and inside that folder create a new folder called fastboot, so you'll have
C:\Android\fastboot
Click to expand...
Click to collapse
Now the fastboot files that I linked to earlier come in a Zip file, unzip it to C:\Android\fastboot, this makes it easier to find it in CMD.
Now back @ htcdev, you've registered and signed in? Good, you've chosen All Other Supported Models and clicked Begin Unlock Bootloader, it'll ask you if you wish to continue, click yes, then the Legal Terms will pop up, just click that you acknowledge both terms and continue with 'Proceed to Unlock Instructions'.
Now click through the instructions until Step 8, ignore everything else.
Now turn off your HOX, now we'll turn on the HOX into the Bootloader, so press and hold down the Volume Down Button and whilst pressing the Power Button, continue to hold this down, the phone may vibrate and bleep a bit but continue to hold it down until you are greeted with a screen that has some options on it, Fastboot, Recovery etc... Now the touch screen wont work so we navigate using the volume buttons & Power Button, press down on the Power Button wile you have Fastboot selected, you'll enter Fastboot Mode with the options HBoot, Reboot, Reboot Bootloader & Power Down. You'll see above these options it'll have Fastboot written and highlighted in Red, leave the phone as it is, just plug it into the PC via USB and that highlighted 'Fastboot' will become 'Fastboot USB'.
Now open CMD, enter
cd \Android\fastboot
Click to expand...
Click to collapse
This will access the fastboot folder in your C:
Now in CMD once you're in the fastboot folder enter this command:
fastboot oem get_identifier_token
Click to expand...
Click to collapse
Now it'll bring up the Identifier Token. (see Image)
Now using your mouse, right click in CMD where it says
<<<< Identifier Token Start >>>>
Click to expand...
Click to collapse
Highlight it to where it says
<<<<< Identifier Token End >>>>>
Click to expand...
Click to collapse
Now on your keyboard, once you've highlighted the Identifier Token press 'Ctrl + C' to copy the Identifier Token.
Now back at the HTC Dev website, scroll down to after Step 10, where it says My Device Identifier Token:, Click in that field and either press Ctrl + V or right click and paste your Identifier Token into that field.
Now Click Submit.
You'll now be taken to a page where you'll be informed to check your emails.
Open up your emails and you'll have an email from HTC and in that email will be an attachment, this will be called Unlock_code.bin.
Download it and place it in your fastboot folder at C:\Android\fastboot.
There will also be a link in the email which will say like "Continue with Bootloader Unlock Procedure" or something like that, Click it.
Back in CMD, you should still be at C:\Android\fastboot, now type in
fastboot flash unlocktoken Unlock_code.bin
Click to expand...
Click to collapse
Please note the Capital 'U' in Unlock_token.bin, press Enter.
Now look back to your HTC One X screen, it'll have two options on it.
1. YES Unlock Bootloader
2. NO Do not Unlock Bootloader
Select Yes with the volume keys and press the power button, the phone will turn itself off and reboot,
CONGRATULATIONS YOU'VE UNLOCKED YOUR BOOTLOADER!
---
Installing a Custom Recovery (Clockwork Mod) and Superuser Access, ROOTING YOUR HTC ONE X:-
Now that we've unlocked the bootloader we're really close to finishing the whole procedure and getting a custom ROM onto our HTC One seX!
Please note that there will be no images or screenshots from here on as a majority of this is all done on the phone handset bar the flashing of the recovery.img onto the handset.
Follow these links:
SuperSU for Super User Access, download the CWM installable ZIP: http://download.chainfire.eu/204/SuperSU/CWM-SuperSU-v0.94.zip courtesy of ChainFire, Please donate to this guy so he can buy some beers
Clockworkmod Touch Recovery Thread: Download the latest Official Recovery
Again, please donate to broncogr and buy this guy a beer or at least hit Thanks.
So now that you've downloaded both files;
The CWM-SuperSU-v0.94.Zip file and the recovery-clockwork-touch-5.8.4.0-endeavoru.img
Right click on the recovery-clockwork-touch-5.8.4.0-endeavoru.img file and rename it to recovery.img, this makes it easier to work with later.
Connect your HTC One X to your USB cable and then to the PC, choose Disk Drive, next, copy and paste the CWM-SuperSU-v0.94.Zip file onto the root of the SD card for your HOX. Once that's on there, change the phones USB connection to charge only.
Open CMD, now get back into the fastboot folder in CMD, do you remember how to do this? It's C:\Android\fastboot then press Enter.
Now start the phone back up into the Bootloader, press and hold Vol Down and press Power Button, once in the Bootloader, once again, select Fastboot and then leave the phone as it is, running in Fastboot USB.
Back to CMD, type in this command:
fastboot flash recovery recovery.img
Click to expand...
Click to collapse
Press Enter. You've just flashed a custom recovery onto your HOX, Once that's finished, type 'exit' into CMD to close the CMD panel.
Back on your HTC One X, using the Volume buttons navigate down to Power Down, once the phone is off, with it still connected to the PC via USB, start it up again into the Bootloader (Vol Down + Power). Once in the Bootloader select Recovery, hit Power. You'll then load up into Clockwork Mod Recovery.
Now you can use either the touch screen or the volume buttons. Navigate to 'Install ZIP from SD Card', hit the Power Button, next select 'Choose ZIP from SD Card'. Now you'll need to scroll right to the bottom of the list to the CWM-SuperSU-v0.94.Zip you placed on the phone earlier.
Click it and it'll ask you if you want to install, select yes install, and let it do it's thing, Then select 'Go Back', Reboot System Now.
Once the phone has shut itself down and restarted, go to the Play Store / Google Market and Install Titanium Backup: Titanium Backup Root. Let it install, once that's finished, start the App on your HTC One X and it'll ask you for Super User Access, grant/accept it.
With the older versions of TiBu (Titanium Backup) You had to go to the problems section and install BusyBox but i believe that it does it automatically now (At least it did for me) So when you start up TiBu You'll see this on screen:
Root Access: OK
Click to expand...
Click to collapse
CONGRATULATIONS YOU'VE ROOTED YOUR HTC ONE X!
---
Making a Nandroid Backup:-
Now that you're rooted and have a custom recovery we'll make a Nandroid Backup, this is EXTREMELY IMPORTANT as it'll act as your fail safe if flashing the custom ROM goes 'Tits-Up'.
Nandroid:To backup the current running rom.
Click to expand...
Click to collapse
When you make a Nandroid backup you are essentially making a carbon copy of how the phone is at that point in time. It doesn't matter if it's a stock rom or a custom rom.
If you are flashing a custom rom onto a phone and it goes wrong or has bugs in it or you don't like it you can restore the Nandroid backup and turn back the clock so that the phone will be as it was when you made the Nandroid backup, as you can see, it's important to do this.
To make a Nandroid backup, turn off your handset, power up into the bootloader, go to recovery, once in recovery there will be the option Backup/Restore, choose backup, let the phone perform the backup - this may take a little time. Once it's finished, just choose restart/reboot phone.
There you have it your very first Nandroid backup!
If it makes you feel a little easier, before flashing a custom rom onto your phone you can transfer the Nandroid backup onto a PC.
Just connect your handset to a PC via USB cable, Disk Drive, then once you can get into the phone on the PC, enter the Clockworkmod folder and make a copy onto the PC of the 'backup' folder.
To restore a Nandroid backup, providing you have the Clockworkmod\backup folder on your phones SD card, enter recovery, and in the option Backup/Restore, just choose 'restore' and off it goes, you've restored the Nandroid backup.
Many people make Nandroid backups before the flash a custom rom onto their phone, even seasoned veterans do this as it's your one fail safe against a disastrous occurrence... messing your HOX up! Some people make them Monthly, Weekly and even a few make them daily!
-NB-
BEFORE PERFORMING A NANDROID RESTORE, PLEASE PLEASE PLEASE READ THIS POST!!!
http://forum.xda-developers.com/showpost.php?p=32084184&postcount=138
Now onto flashing ARHD!!!
---
Installing Android Revolution HD 9.2:-
We're so close to having a Custom ROM on our HTC One X, not far to go now!
Make sure you have at least 35% Battery when you do this! Preferably more, I cannot stress this enough!!!
Pop on over to Mike1986's ARHD Thread here: ARHD Thread Donate to Mike1986 if you like or Thank him as his work is brilliant!
Scroll down to the DOWNLOADS section and download Android Revolution 9.2, boot.img for 9.0.x and Super Wipe.
Next connect your phone to your PC and select Disk Drive, now copy the SuperWipe file and the ARHD 9.2 ROM onto your phones SD card at Root, no need to go any deeper.
Next take the boot.img for 9.0.x file (it's named Flash_boot_9.0.x.rar) and copy it to C:\Android, once the file is there, right click and Extract Here.
Now boot your HOX up into the Bootloader (Vol Down + Power) and then go into fastboot, connect your HOX to the PC to get Fastboot USB.
Now that you're connected, go back to C:\Android and click on the file called
install-boot-windows
Click to expand...
Click to collapse
In the CMD panel it'll ask you to hit any key, so just press Spacebar or whatever, it'll do it's thing, it might ask you to press any key again or it'll just finish.
Back over to your handset, Press the power button to get back into HBoot and then select Recovery.
Once Clockworkmod Touch Recovery has started once again choose the option 'Install ZIP from SD Card', then 'Choose ZIP from SD Card', now scroll down to the Superwipe ZIP, make sure you choose this and not the ARHD ROM, Anyway, choose the Superwipe script and select Yes when it asks you if you want to Wipe.
Once it's performed the wipe, select Go Back and now repeat 'Install ZIP from SD Card', then 'Choose ZIP from SD Card', this time select the ARHD ROM file.
The setup for ARHD will begin, on your handset select next, then select Agree, then next again.
You'll come across a screen that has two check boxes on it, one will say
Wipe Data Partition
Click to expand...
Click to collapse
Select this.
Tweeks: You'll be presented with a screen of Tweeks that can be included into the flashing of the ROM, I personally choose
Improve EXT4 Performance, Force GPU2, Improve Multitasking, Experimental Tweeks and the last option, I can't remember what it is
Click to expand...
Click to collapse
Click Install, It'll finish, then Reboot.
Now don't panic, the first reboot can take up to 5 Minutes to complete, this is why it's imperative to have over 35% battery life as a shut down now can be disastrous!
Once it's rebooted you just have to setup your phone like you would do if it was fresh from the box.
Restore data backup:-
Now all that's left is to restore your data that you backed up at the beginning!
Open CMD, enter
cd \Android\android-sdk\platform-tools
Click to expand...
Click to collapse
Now do you remember where you saved your backup? Good!
Now in CMD enter the location and file name of your backup
adb restore C:\backup\backup20082012.ab
Click to expand...
Click to collapse
Remember mine was todays date! On your HOX screen you'll be asked to enter your password that you chose when making the backup, it'll do it's thing Et Voila!
You've restored all your lovely data, remember, the stuff you had on the phone when it was stock? Nice!
CONGRATULATIONS!!!
YOU'VE MADE A DATA BACKUP, UNLOCKED YOUR BOOTLOADER, ROOTED & INSTALLED A CUSTOM ROM AND REINSTALLED YOUR DATA ONTO YOUR HTC ONE X!!!
I hope that you find this guide useful and that you've managed to fumble your way through it without too much trouble or many hiccups.
If you have any questions or hit any problems please feel free to ask, I'll try to help you if I can.
If this guide has helped you at all then please hit Thanks
GLHF!!!
The-Last-Hylian
---DISCLAIMER---
If I've said anything wrong or given out the wrong info, then please PM me and I'll make amendments.
Also, instead of donating to me or whatever, instead I'd just like to place a link to my site here: Tuffphones - The home of tough, rugged and waterproof mobile phones. (If I'm not allowed this link here please PM me and I'll remove it)
Reserved
nicely written. once my hox is replaced and finally working, i think i shall have to refer back to this
Would it be worth sticky-ing this thread to the top of General?
Great thread mate. I sincerely believe that it deserves to be stickies for everyone to see, because you did a very thorough and detailed Jacob that will surely be helpful to newcomers. You deserve your own praise too. I'm one of those holding back on unlocking my HOX since I'm waiting for an unofficial unlock method and contemplating if it's even worth holding on a HTC device and not just going back to my iPhone which was easier to hack and modify (imo).
Sent from my HTC One X using Tapatalk 2
Better to recommend HTC Sync Manager as that's for the One Series phones...
http://www.htc.com/www/help/htc-one-x/#download
Yes
Well done on this! Super site
Check back to this thread soon!
I'm going to write into my reserved #2 post about how to get the best out of your HOX for gaming!
EddyOS said:
Better to recommend HTC Sync Manager as that's for the One Series phones...
http://www.htc.com/www/help/htc-one-x/#download
Click to expand...
Click to collapse
I mainly choose HTC Sync as it's the only one I've used and I thought I'd only write about what I know so that way I know it's reasonably accurate.
Thanks for the tip + link EddyOS, I'll add that into the OP as an alternative.
Good one! Explained everything required. N00b friendly xD
death__machine said:
Good one! Explained everything required. N00b friendly xD
Click to expand...
Click to collapse
Thanks that was what I was aiming for
I figure that even if something is really complicated to do (which granted not much of what I wrote about is), if you write the instructions with proper and correct grammatical English then people will understand it a lot better.
Hi the last hylians, i currently new with hox, mine previous was sgs. It looks difficult to install custom rom with hox rather than sgs. First i want to know, mine software is 1.29.707.11, can i install all the custom rom or just a particular one with the same software. Thanks
Sent from my HTC One X using xda app-developers app
neoandresk said:
Hi the last hylians, i currently new with hox, mine previous was sgs. It looks difficult to install custom rom with hox rather than sgs. First i want to know, mine software is 1.29.707.11, can i install all the custom rom or just a particular one with the same software. Thanks
Sent from my HTC One X using xda app-developers app
Click to expand...
Click to collapse
Hi there,
As long as you have a decent grasp of the English language and can follow instructions reasonably well then installing a custom ROM isn't too difficult, I'm sure you could muddle through
.707 is that Malaysia/Indonesia?
I believe that you could install a custom ROM that would be x.xx.401.xx as you'd be unlocking the bootloader so theoretically can install any OS on the phone that you like, the region for the OTA therefore wouldn't need apply as you wouldn't get FOTA's afterwards anyway.
It might be worth asking on the Android Revolution HD thread and posting a link to this thread so that way you can get a 2nd opinion.
Afaik you'd be fine however.
T-L-H
This isn't knocking the guide, as it's good, BUT everything you have here is already available online if people were bothered to search for it - especially the bootloader unlocking as HTC have a detailed guide on their own website
You should also highlight the importance of downloading the RUU for your phone before unlocking. If it's not available add a note to proceed with caution
Still, good work
EddyOS said:
This isn't knocking the guide, as it's good, BUT everything you have here is already available online if people were bothered to search for it - especially the bootloader unlocking as HTC have a detailed guide on their own website
You should also highlight the importance of downloading the RUU for your phone before unlocking. If it's not available add a note to proceed with caution
Still, good work
Click to expand...
Click to collapse
Thanks for that, I should mention about downloading the RUU for the phone in case you want to revert back, I was going to add that into the reserved #2 post at a later date, 'How to revert back to Stock'
Yeah I'm aware that there is a lot of info out here on XDA already but like I said at the start of my OP, it's all in different places, some of it is difficult to understand and it's quite fragmented in parts and there isn't really a 'Start-to-Finish' guide out there, or at least not one that I've seen. Even then, people can still find what they need, have access to all the relevant tools but still not be able to proceed, either due to lack of English skills or understanding, intelligence etc... So I thought I'd write it up in real 'laymans terms'.
But as you say, the info's already here for those who've learnt to use the search button
Thanks for repyling, fyi mine is indonesia.
Sent from my HTC One X using xda app-developers app
neoandresk said:
Thanks for repyling, fyi mine is indonesia.
Sent from my HTC One X using xda app-developers app
Click to expand...
Click to collapse
How did you get on?
Hi mate! at first, thanks for this "noob" tuturial! i think i'm going to try it later.. i have some questions i would like to know before i continue as i don't root/flash roms since my htc hero.. would be thankful if you cared to help me
i have just installed the ruu on mine with 4.0.4 and senses 4.1.
- Will i be able to make a complete rom backup of my actual rom (exactly as it is, with my configs, apps, etc. i user to do it everytime when i was flashing a new rom on my hero so i could revert if anything went wrong or i didn't like the new rom).
- if not, is there a way to reinstall the ruu or the official rom later if i decide for it so i can receive official updates? In other words, can i revert to an "original" state?
And finaly, is there anything that is not working on revolution rom?
thanks a lot!
Hey Porsche. V,
The answer to both of your questions is essentially 'Yes'.
You'll find in my OP one section called 'Backing up your data', depending on which instructions you decide to enter will depend on what gets backed up, take a look at that section and the forum thread that I linked to from that, that'll give you an idea on what to enter into CMD.
It'll be something like
Code:
adb backup -apk -shared -all -f C:\backup\backup21082012.ab
There's a good list of the factory ROMs here, download the relevant one for your handset, RUU etc... then put the phone in fastboot USB and enter into cmd from cd \Android\fastboot
Code:
fastboot oem lock
That'll relock the bootloader, I think that's correct anyway, never done it myself, I know many others have however but yes you can revert back to how the phone is stock, bar the Bootloader saying 'Relocked' instead of 'Locked'.
You can also make a Nandroid backup (always recommended, I should add that into my guide) before flashing any new ROMs, especially when coming from stock
Read these;
1:- http://forum.xda-developers.com/showthread.php?t=1660807
2:- http://forum.xda-developers.com/showthread.php?t=1543604
3:- DEFINITELY READ THIS http://forum.xda-developers.com/wiki/HTC_One_X#Total_recovery_-_flashing_a_RUU_to_completely_restore_your_phone
The ARHD ROM is the most stable ROM there is, everything works, it's the best!
Porsche.V said:
Hi mate! at first, thanks for this "noob" tuturial! i think i'm going to try it later.. i have some questions i would like to know before i continue as i don't root/flash roms since my htc hero.. would be thankful if you cared to help me
i have just installed the ruu on mine with 4.0.4 and senses 4.1.
- Will i be able to make a complete rom backup of my actual rom (exactly as it is, with my configs, apps, etc. i user to do it everytime when i was flashing a new rom on my hero so i could revert if anything went wrong or i didn't like the new rom).
- if not, is there a way to reinstall the ruu or the official rom later if i decide for it so i can receive official updates? In other words, can i revert to an "original" state?
thanks a lot!
Click to expand...
Click to collapse
instaling Revolution rom now! thanks for the tuturial!
I have been true some web sites and have not found a solution for this problem. I have a HTC Desire HD, sow called HTC ACE, I got it from Orange UK, Android Version 2.3.5, HTC Sence Version 3.0 With Software 3.13.61.5, and I would be pleased to debrand this machine, but always come to the same decision I cannot duet yet, I would like to receive some suggestions on how to debrand it, I will try everything and after that right everything I have done until be successful, thank's
PauloMHAlmeida said:
I have been true some web sites and have not found a solution for this problem. I have a HTC Desire HD, sow called HTC ACE, I got it from Orange UK, Android Version 2.3.5, HTC Sence Version 3.0 With Software 3.13.61.5, and I would be pleased to debrand this machine, but always come to the same decision I cannot duet yet, I would like to receive some suggestions on how to debrand it, I will try everything and after that right everything I have done until be successful, thank's
Click to expand...
Click to collapse
Before you do anything — Make a backup
Don't forget to back up your data. If you have synced the device with a Google account, then the contacts, calendar, Gmail, & select other Google-related data will not be lost and will come back after the next sync. However, you should backup anything you want to keep that is not stored on the SD card:
SMS/MMS messages,
Call Log,
Bookmarks,
Applications; use Titanium Backup or the Astro File Manager, for example,
Any application data not on the SD card.
It would also be a good idea to backup everything stored on the SD card in the rare case the SD card must be formatted to resolve any major problems.
MyBackup Root, SMS Backup & Restore, and Call Backup & Restore are all free applications that can assist with backing up your data.
Downgrade to an exploitable Firmware
AT&T Inspire 4G: Firmware Downgrade: Froyo, Gingerbread
HTC Desire HD: Firmware Downgrade: Froyo, Gingerbread
Rooting the HTC Ace
WARNING: ROOTING THE HTC ACE WILL VOID THE WARRANTY.
Before you begin, if VISIONary is installed on the HTC Ace, uninstall it before continuing.
You will need ADB on the computer to root the HTC Ace and to flash the necessary files for radio S-OFF. Follow the Android SDK guide, to get the ADB shell on the computer.
Download busybox, the ClockworkMod Recovery, the Engineering HBoot, gfree 0.7, psneuter, root_psn, Superuser package:
busybox: Download
md5: 25c5db694c987995909cc3166d4f01b0
ClockworkMod Recovery: Download
md5: 072a643b0aba983a4b9994db0e113c5e
Engineering HBoot: Download
md5: b2c8834905bfa2349f5223077493140a
gfree 0.9: Download
md5: 2dd45594b1ecb084401d428432f87010
psneuter: Download
md5: 89c2dec8d72d87b4c669f44dd31c8d17
root_psn: Download
md5: c8fe38ef55eb8951def9ff17b2eb99c1
Superuser package: Download
md5: 43d9a40b63e916635d5ad7ca32433fab
Unzip the zip files and copy the contents to the same folder as adb (the /platform-tools folder within the Android SDK folder).
Connect the HTC Ace to the computer via USB.
Make sure USB debugging is enabled on the HTC Ace by checking Settings » Applications » Development » USB debugging.
On the computer, open terminal and run the following commands:
adb push busybox /data/local/tmp/
adb push gfree /data/local/tmp/
adb push hboot-eng.img /data/local/tmp/
adb push psneuter /data/local/tmp/
adb push recovery-clockwork-5.0.2.3-ace.img /data/local/tmp/recovery.img
adb push root_psn /data/local/tmp/
adb push su /sdcard/
adb push Superuser.apk /sdcard/
adb shell
chmod 755 /data/local/tmp/*
/data/local/tmp/psneuter
NOTE: You will drop out of the shell after this command. Restart the shell using:
adb shell
cd /data/local/tmp
./gfree -f -b hboot-eng.img -y recovery.img
As it is very important that the hboot was installed correctly gfree calculates md5sums of the partition. It will calculate the following 3 checksums
md5sum #1 - checksum of partition 18 before the installation
md5sum #2 - checksum of the hboot image that should be installed
md5sum #3 - checksum of partition 18 after the installation
The messages that you what to see are either/or
md5sum #1 == md5sum #2 - the hboot image is already installed -> skipping installation
md5sum #3 == md5sum #2 - the hboot image was successfully installed -> OK!
If you get a different error message you should run for help at then DO NOT REBOOT and join #G2Root on Freenode for further help.
If gfree worked correctly continue with:
./root_psn
sync
reboot
The HTC Ace is now rooted with S-OFF, the Engineering HBoot & the ClockworkMod Recovery. Continue to the next section.
Flashing CyanogenMod
If the {{{device}}} has been rooted, unlocked, etc. through steps other than the method described above or running a custom ROM other than CyanogenMod and you are having issues flashing or booting CyanogenMod, it is recommended the {{{device}}} be returned to stock & start over with the full instructions provided above.
Method via Recovery
Download the [[Devices Overview#{{{device}}}|latest version]] of CyanogenMod.
Optional: Download the Google Apps for the device.
Place the CyanogenMod update.zip file on the root of the SD card.
Optional: Place the Google Apps .zip on the root of the SD card also.
Boot into the ClockworkMod Recovery.
Once the device boots into the ClockworkMod Recovery, use the side volume buttons to move around, and either the power button or the trackball to select.
Optional: Select backup and restore to create a backup of current installation on the {{{device}}}.
Select the option to Wipe data/factory reset.
Then select the option to Wipe cache partition.
Select Install zip from sdcard.
Select Choose zip from sdcard.
Select the CyanogenMod update.zip.
Optional: Install the Google Apps by performing steps 7 - 9 again and choosing the Google Apps update.zip.
Once the installation has finished, select +++++Go Back+++++ to get back to the main menu, and select the Reboot system now option. The {{{device}}} should now boot into CyanogenMod.
Method via ROM Manager
Launch RomManager.
Optional: Choose the first option in the app, Flash ClockworkMod Recovery to update to the latest version.
Select the Download ROM option from the main menu in the ROM Manager.
Select the CyanogenMod option, and then choose the latest version of CyanogenMod from the menu.
Optional: When you select the latest version of CyanogenMod, check the Google Apps option.
Once the ROM is finished downloading, it asks if you would like to Backup Existing ROM and Wipe Data and Cache.
If Superuser prompts for root permissions check to Remember and then Allow.
The {{{device}}} will now reboot into the recovery, wipe data and cache, and then install CyanogenMod. When it's finished installing it will reboot into CyanogenMod.
:crying:
I have try that was another fail lol...
PauloMHAlmeida said:
I have been true some web sites and have not found a solution for this problem. I have a HTC Desire HD, sow called HTC ACE, I got it from Orange UK, Android Version 2.3.5, HTC Sence Version 3.0 With Software 3.13.61.5, and I would be pleased to debrand this machine, but always come to the same decision I cannot duet yet, I would like to receive some suggestions on how to debrand it, I will try everything and after that right everything I have done until be successful, thank's
Click to expand...
Click to collapse
GUIDE] Downgrade from 3.13 (Sense 3.0) roms
This guide is for phones shipped with froyo and updated to the 3.x firmware! For phones shipped with gingerbread (even the lower versions) please read attn1's posts in this thread!
With the Sense 3.0 upgrade HTC patched against fre3vo, so we can no longer temproot to use misc_version on that firmware. Lucky us, a new exploit was issued @rootzwiki. This exploit was tested at #g2root (freenode) and was able to temproot a 3.13.161.3 firmware version.
The usual disclaimer applies: Everything you do is your responsibility, no one can be held accountable for the state you put yourself and/or your phone into.
If you meet troubles search for help at IRC: freenode, #g2root
make sure your phone is in 'charge only' mode and the 'fast boot' feature is turned off.
What you need:
tacoroot
misc_version NOTE: you need THAT version of misc_version. Earlier versions would not work.
flashgc for a goldcard
1.32 PD98IMG.zip
put all files in your platform-tools directory (unzip misc_version and tacoroot.sh)
Code:
adb push tacoroot.sh /data/local/tmp/tacoroot
adb push misc_version /data/local/tmp/
adb push flashgc /data/local/tmp/
adb push PD98IMG.zip /sdcard/
NOTE: the last command will take a long time
After all files are pushed you have to run tacoroot:
Code:
adb shell
chmod 755 /data/local/tmp/*
/data/local/tmp/tacoroot --setup
This command will reboot the phone to recovery. Once it is done, use vol up/power then choose 'reboot' to reboot the phone. After it boots (it will bootloop, that's expected):
Code:
adb shell
/data/local/tmp/tacoroot --root
this command will kick you out of adb shell, so we need to return there and see the # sign of root access, after which we can change the main version and create a goldcard:
Code:
adb shell
cd /data/local/tmp
./misc_version -s 1.00.000.0
./flashgc
./tacoroot --undo
After these commands are done, the phone should get rebooted by tacoroot. After it boots, boot to bootloader to flash the 1.32 firmware:
Code:
adb reboot bootloader
Once in bootloader, use the vol buttons to go to 'bootloader' and the power button to execute. The rom will flash. Enjoy!
Credits:
the tacoroot team
skorgon for flashgc
Donate to RevSkills and EFF!
fail againnnnnn:crying:
PauloMHAlmeida said:
I have been true some web sites and have not found a solution for this problem. I have a HTC Desire HD, sow called HTC ACE, I got it from Orange UK, Android Version 2.3.5, HTC Sence Version 3.0 With Software 3.13.61.5, and I would be pleased to debrand this machine, but always come to the same decision I cannot duet yet, I would like to receive some suggestions on how to debrand it, I will try everything and after that right everything I have done until be successful, thank's
Click to expand...
Click to collapse
use this
http://forum.xda-developers.com/showthread.php?t=1377119
For the last few days I have try new software
Z4root No chance another fail...
for debrand use latest RUU, WWE version.. no branded
for rooting use advanced ace hack kit
The Advanced Ace Hack Kit – for HTC Desire HD and HTC Inspire
failed..........
new Advanced Ace Hack Kit system
I just found a new chance and I'm trying it
with new Advanced Ace Hack Kit system, I found it at http://tau.shadowchild.nl/attn1/?p=74
was Posted on July 26, 2012
The Advanced Ace Hack Kit – for HTC Desire HD and HTC Inspire
AAHK will work on Inspires on AT&T’s latest ROM, 3.20.502.52 only after following the steps outlined here: http://tau.shadowchild.nl/attn1/?p=88 .
Warnings:
If your PC environment is not ready to run this kit, there is a good chance your device will not boot properly until you fix your PC or switch to another and re-run the hack kit from the partial boot. READ THIS ENTIRE POST and READ THE EFFEN MANUAL! There is no substitute for READING for COMPREHENSION
Do NOT use earlier versions Ace Hack Kit (12.x and lower) on Inspire or DHD devices shipped with Gingerbread.
Do NOT attempt to downgrade a Inspire or DHD shipped with Gingerbread with a Froyo RUU.
Do NOT attempt to install earlier ENG HBOOTs on these models. AAHK now has Hboots that safely support fastboot image flashing.
Doing this WILL severely degrade bootloader performance on Inspires and DHDs and causes issues trying to install RUUs. In other words, it WILL jam you up. (Note: Issue confirmed on later DHDs – ignore at your own risk).
Sense 3, including those with RELOCKED HTC BOOTLOADERS (NOTE: NOT UNLOCKED – MUST BE LOCKED OR RELOCKED) is auto-detected in hack step. Option is given to download a GB RUU and downgrade or abort. This WILL wipe data.
#include <std_disclaimer.h>
/*
Your warranty is now void.
I am not responsible for bricked devices, dead SD cards,
thermonuclear war, or you getting fired because you can’t tether. Please
do some research if you have any concerns about features included in this
TOOL before running it! YOU are choosing to make these modifications, and if
you point the finger at me for messing up your device, I will laugh at you.
*/
(Disclaimer borrowed heavily from cyanogenmod)
Features:
COMPLETELY INTEGRATED/INVISIBLE GOLD CARD PROCESS
Custom AAHK Bootloaders support popular ENG S-OFF functions for both Sense 2 and Sense 3 partition layouts
Only ONE menu step – HACK ACE
No ROM downgrade required (only radio/kernel) for devices not running sense 3
The original ROM is retained (except when downgrade from Sense3-GB is required)
No wiping data for devices not running sense 3
Rom is fully functional (yes, inc wifi)
Fully rooted with insecure boot image (supports adb remount for rw system)
Busybox manager app installed
Radio S-Off, superCid & carrier sim unlock
Correct Radio is automagically restored for HSPA+ operation
Clockworkmod Recovery included
All known Inspire/DHD builds supported
Easy return to stock for SOME builds (See the Effen Manual – not all carrier RUUs are available)
Notes:
Please do NOT run the hack step if you are already S-OFF AND are running a custom ROM. It’s pointless, and while it won’t brick you, you can get jammed up a bit. This is for stock devices only.
You MUST read the ENTIRE EFFEN MANUAL in order to run the hack kit.
Do NOT try to run this from a VM – particularly VirtualBox. You WILL get jammed up and may wind up flashing an RUU to recover, losing data in the process.
After kernel downgrade – video is lost on boot – this is okay as adb is working and can be used to finish the process. If the process fails, it can be restarted once the PC environment is corrected. When the process completes successfully, everything is restored and fully working.
Youtube videos are neat demos, but they make poor guides. READ THE EFFEN MANUAL. “There is no substitute for reading for comprehension.” – GenePoole
Make sure you extract the hack kit to your pc maintaining the directory structure in the archive you downloaded. The docs will be in the root directory of the unarchived kit, as will the scripts. READ THE EFFEN MANUAL.
I can’t believe that so many people are asking where the effen manual is. THE EFFEN MANUAL IS IN THE EFFEN HACK KIT.
This kit should work fine on HTC Inspire and HTC Desire HD Software versions below 3.06.405.1 which require the radio/kernel downgrade before a root exploit is available.
Windows Prep:
IMPORTANT – disable all malware (Antivirus detection etc) detection before unarchiving the hack kit. Keep it off thoughout the hack kit processes. Many Windows malware detection programs report false positives, deleting or binding critical files required by the process.
IMPORTANT – Remove or disable all services and daemons you can, particulary anything Apple, blackberry, PDAnet, Microsoft Mobile, anything USB not required for this task, any resource hogs. Also disconnect all un-needed USB devices and USB HUBs.
Remove HTC Sync and drivers.
Only after completing the above steps, install the drivers contained in the Hack Kit (see the Effen Manual) BEFORE plugging in the phone.
Connect the phone to the computer via a USB port connected to the system board – not a front panel port or a hub or extention port.
Verify successful android device driver installation in device manager.
Issues during downgrade:
IMPORTANT: BEFORE SWITCHING FROM DISK DRIVE TO CHARGE ONLY MODE, ALWAYS EJECT THE SDCARD WITH PC SOFTWARE TO FLUSH WRITE BUFFERS AND AVOID CORRUPTING THE SDCARD.
model ID incorrect update fail – this is because your goldcard is not working.
READ THE EFFEN MANUAL. Reading is fundamental.
Download:
Note: AAHK filename uses ddmmyyyy naming convention.
aahk-11092012.zip
md5: 5727960aa167b305b8f3561ffbbb1360
viperbjk is with Revskills, and his contribution is key to finally allowing one step processing where a goldcard is required. The entire process is now one menu step. A second step will be required to clear your conscience –
DONATE to:
Revskills.
and/or
Electronic Frontier Foundation
Note: No money has been accepted for the AAHK or support of the AAHK by myself or anyone working with me on it.
If you have read this post and the effen-manual and get stuck during processing,
help is available in IRC at http://webchat.freenode.net/?channels= – aahkSupport
Yes, there are stupid questions.
Questions that will get you immediately kickbanned from the IRC channel with no further explanation:
Q: Do I need to flash a ROM after the hack kit is finished?
A: Kickban. The hack kit is a complete, one step process. If it finishes correctly, you are finished. What part of “fully functional” is vague?
Q: Do I need to flash a radio after the hack kit is finished?
A: Kickban. The hack kit is a complete, one step process. If it finishes correctly, you are finished. What part of “fully functional” is vague?
Q: The options menu has options to flash radios. Do I need to flash a radio?
A: Kickban. What part of “optional” is vague? This option is to make it easy for people who may have flashed another radio and want to flash back to these particular radios.
Q: Do I need to plug in the phone?
A: Kickban. If you know how to enable usb debugging without a USB connection, then I’ll change this policy. In the meantime, asking such a question just makes me think you have not read anything and/or have dedicated yourself to being an idiot.
Q: What’s the best ROM?
A: Kickban. The whole point of this is to give YOU control and allow YOU to decide. Yes, we prefer CM7 and I think it’s the only real Android choice available, but don’t ask us to think for you. If you don’t see that pretty much everything else is either ripped off or HTC Non-Sense, then you haven’t done your homework and that’s okay. Just don’t ask, because in the end, it’s YOUR choice.
Q: Facebook doesn’t work.
A: Kickban. This has nothing to do with anything but Facebook. Go ask Facebook, not us.
Q: I can’t find the pass key.
A: Kickban. Really? Then you did not really read the Effen Manual. If you really did, then you would not ask. Really.
Q: My phone won’t boot – how do I fix my HBOOT?
A: Kickban. We’ve been warning people not to flash Froyo Hboots (Including HTC ENG ones) on devices shipped with GB for going on a year now. If you do this and screw up, it’s not our fault and you’re on your own.
This IRC channel is for people who read, attempt and get stuck because of PC issues or an occasional bug introduced with a new feature. It’s not for people to troll those who dedicate their time for support without any compensation by asking a series of mindless, inane questions and observations for attention. We’re too busy for that – even if we have nothing to do. It’s beyond annoying and you will be kickbanned without warning. Read, search, think, try, then ask.
The people in #aahkSupport have been helping noobs without compensation for over a year now, with generally very good results and a generally good nature, despite being abused by some on almost a daily basis.
Thanks to:
Revskills for their fantastic gold card algorithym
GenePoole for the kickass android goldcard binary based on above
agrabren for fre3vo, the Gingerbread temproot used
scotty2 for finding the vold exploit and the author of psneuter
Guhl for misc_version and gfree
hyuh for misc_version revisions and Hboots with ENG features
jcase for taco root
shad0wf0x for his windows scripting contributions
ktilcu for DOC contributions
anthony1s for his review and unique perpective
neolobster for his generous file hosting
The > 150,000 downloaders of the hack kit, most of whom seem to get though it without issue.
and they have amazing feedback's, lets try it now....
sow far as I see he dues everything you just need to site back and wait, look's amazing.........
new Advanced Ace Hack Kit system
thanks for the new development!
let's see in a hour time how he dues lol
PauloMHAlmeida said:
sow far as I see he dues everything you just need to site back and wait, look's amazing.........
new Advanced Ace Hack Kit system
thanks for the new development!
let's see in a hour time how he dues lol
Click to expand...
Click to collapse
Well, don't forget that you also need to read the "effen manual!"
I have not forget to read it but is a fail....
thanks for telling me that but I found the solution for all S-ON HTC...
and for the Hboot lol
is a big journey I made on the last months, and I have put some staff all together and got it made lol
just wait for my next post how to duet....
look for my next post
There's no need to make the phone S-OFF (like some people say).
PauloMHAlmeida said:
look for my next post
There's no need to make the phone S-OFF (like some people say).
Click to expand...
Click to collapse
With S-ON your bootloader is locked.
And without ENG S-OFF you can't change the radio.
S-OFF is necessary for me
And btw... i don't know what you do..
But with the Hack Kit i've rooted about 15 DHDs in my circle of friends.
Some devices with problems. But after manually downgrade with RUU no problems at all.
I'm finish here Just look for my next publication Thanks
fr34kde said:
With S-ON your bootloader is locked.
And without ENG S-OFF you can't change the radio.
S-OFF is necessary for me
And btw... i don't know what you do..
But with the Hack Kit i've rooted about 15 DHDs in my circle of friends.
Some devices with problems. But after manually downgrade with RUU no problems at all.
Click to expand...
Click to collapse
There's no need to make the phone S-OFF (like some people say).
Disable fast/quick reboot (Settings » Power » Fastboot)
Download all
Fastboot commander.zip http://www.mediafire.com/download.php?xsu7c3m981o9gb8
Google.zip http://www.mediafire.com/download.php?cm9pdoh2g9mkgvb
Superuser-3.1.3-arm-signed http://www.mediafire.com/download.php?kzpbhq13jb085s8
Android ultimate toolbox pro http://www.mediafire.com/download.php?6m5w39zmb6ph8gq
Recovery.img http://www.mediafire.com/download.php?grl8wsjzxihhfwf
Update http://www.mediafire.com/download.php?dzkww8zaq7sxhae
Fastboot.bin http://www.mediafire.com/download.php?bhzth13p4kvow4v
Copy in to the root of your sd card after been formatted
Google.zip + Update.zip + Superuser-3.1.3-arm-signed.zip
On your pc create a new folder on C: and name it HTC for easy access and copy in to the folder
Recovery.img + fastboot binary
Install on your PC
Fastboot commander.zip + Android ultimate toolbox pro
Start rooting
Unlock bootloader: http://htcdev.com/bootloader/
Put the phone in Fastboot USB mode (Turn off, hold Volume Down + Power)
fastboot oem get_identifier_token
fastboot flash unlocktoken Unlock_code.bin (file from email)
Install ClockWorkMod recovery the recovery.img from my link our use android ultimate box to flash recovery
fastboot flash recovery recovery.img
Make a backup
Start clockworkmod recovery (Fastboot mode, Recovery)
Select backup and restore
Select backup
Go to your mobile start it as Fastboot and go to recovery
You go in to Clockworkmod Recovery V5.0.2.7 from the Ace Hack Kit
On the top is the menu with + and – buttons just scrool in to advanced and press power
Select “Wipe Dalvik Cache”
Then select “Wipe Battery Stats”
Then select “And go back”
Then select “Wipe data/Factory reset”
Then select “Wipe cache Partition” (Now you have cleaned all the old staf from your mobile)
Now let’s start rebuild the HTC
Select "apply update from sdcard"
Then select "Yes - install update.zip" to confirm
Then select "install zip from sdcard"
Then select “google.zip”
Then select "Yes - install google.zip" to confirm
Then select "install zip from sdcard"
Then select "su-3.0-efgh-signed.zip"
Then select "Yes - install su-3.0-efgh-signed.zip" to confirm
Then go back to your pc for the files you have download and unzip update and copy Boot.bin to the file you created C:\HTC
o Flash boot.img trough fastboot:
o fastboot flash boot boot.img
o Reboot
• Done
• You should have now a white screan from HTC for at least 5 minutes and after will sart the new room, just let it on for a couple minutes and you will see the sucess….
All my files are at http://www.mediafire.com/?al6dsdcd6c02f
Enjoy it, next I will say how to sort google play problem I found it easy lol…
PauloMHAlmeida said:
[....]
Unlock bootloader: http://htcdev.com/bootloader/
[....]
Click to expand...
Click to collapse
And thats the point.
You do what S-OFF does through HTC-Tool.
Now u unlocked the bootloader and your warranty is gone because your device is registered now.
Why should anyone go the complicated way if there is an easy way?
Firts have 2 types of waranty, 1st the manufactors warranty. That runs off 3 years after your purchase, 2nd the software warranty... And HTC have take off that point on the warranty, now you can unlock our relock the bootloader from your HTC with out lost of your warranty... By the way that's the reason HTC created HTC devoluppers web page...
And if you want to understand that just read all my post's. Changing our due hboot s-off make you lost warranty lol....
Sent from my HTC Desire HD A9191 using xda app-developers app
Unlocking Your Bootloader
HTC is committed to listening to users and delivering customer satisfaction. We have heard your voice and starting now, we will allow our bootloader to be unlocked for 2011 models going forward. We plan on releasing the updates that will allow you to unlock your bootloader in the coming months, please keep an eye on this website for more details on which devices will be adding this feature. We are extremely pleased to see the energy and enthusiasm from our fans and loyal customers, and we are excited to see what you are capable of. HTC eagerly anticipates your innovations.
It is our responsibility to caution you that not all claims resulting or caused by or from the unlocking of the bootloader may be covered under warranty. Please note that unlocking your bootloader does not mean that you will be able to unlock the SIM lock. Unlocking your SIM lock is at the discretion of your operator/carrier and is not part of the bootloader unlocking scope.
Our devices have been designed with our hardware and software specifications in mind and unlocking the bootloader will change the software and may cause unexpected side effects. It is impossible for HTC to ensure the proper functioning of your device after this. In the worst case scenario, it is possible that your device may be physically damaged due to overheating or the behavior of your device might be altered including, but not limited to, hearing aid compatibility (HAC) and specific absorption rate (SAR) values.
Some content on your device may also be invalidated and cannot be accessed any more because of invalid DRM security keys. This includes content that you may have purchased through a 3rd party vendor and through HTC. Furthermore, although you will still be able to receive updates to your device via FOTA (“firmware over the air”), we do not guarantee that updating your device via FOTA will not render your device unusable. Please understand that you will not be able to return your device to the original state and going forward your device may not be held covered under the warranty for all claims resulting from the unlocking of the bootloader. HTC bears no responsibility if your device is no longer usable afterwards.
HTC is committed to assisting customers in unlocking bootloaders for HTC devices. However, due to some of our carrier customers concerns, certain models with specific restrictions may not be able to be unlocked. Please refer to our list of supported devices to see if your device is eligible for unlocking the bootloader.
We strongly suggest that you do not unlock the bootloader unless you are confident that you understand the risks involved. This is a technical procedure and the side effects could possibly necessitate repairs to your device not covered under warranty. If you are still interested in unlocking the bootloader, and you understand the consequences both to your device and to your warranty, then you may refer to the following pages where we have provided the unlocking instructions.
Un lo c k Bo o tlo ad er
Unl oc k th e pos s ib ilit i es wit h to ta l cu s t omi zat io n
Unlock Bootloader
Frequently Asked Questions Preview Unlock Process
Supported Devices
Select “All other supported models” if you cannot find your phone in this list. Devices launched after 9/2011 will be shipped with the unlock capability. Please check back often for updates on the unlock status of additional devices.
------- Select Your Device ------
Beg i n Unl o ck Bo ot l o ad er
* Indicates HBOOT update required.
HTC is committed to assisting customers in unlocking bootloaders for HTC devices. However, certain models may not be unlockable due to operator restrictions. We continue to work with our partners on this, check back often for ongoing updates about unlockable devices.
Copyright © 2012 HTC Corporation. All rights reserved. Terms of Use Privacy Policy About HTCdev HTCDev Affiliates Follow Us Comments - Tell HTCdev what YOU want.
For other HTC devices supported by FacePalm, please see this thread: http://forum.xda-developers.com/showthread.php?t=2155069
Welcome to Facepalm S-Off for modern HTC phones.
Credits and terms:
Exploit by beaups, full guide, testing, and concept by jcase and beaups. Thanks to dsb9938 and dr_drache for support and testing. Thanks also to all of the regulars at teamandirc.
Both beaups and jcase will collect the applicable active bounties. Further donations are greatly appreciated and can be sent to:
beaups - [email protected] - http://forum.xda-developers.com/donatetome.php?u=711482
jcase - [email protected] - http://forum.xda-developers.com/donatetome.php?u=2376614
dsb9938 - [email protected] - http://forum.xda-developers.com/donatetome.php?u=2963256
dr_drache - [email protected] - https://www.paypal.com/cgi-bin/webscr?cmd=_s-xclick&hosted_button_id=6LRSY8MT8P3A6
You can also come by irc for support or just to say thanks: #FacePalm http://chat.andirc.net:8080/?channels=facepalm
While this process shouldn’t be too risky, bricks can happen. None of us will be accountable. If you are worried, don’t do it.
This is a pretty simple method, however, you will need to have a working adb and fastboot environment. This method will work on any operating system that supports adb and fastboot. You should understand how to use a terminal window in your O/S. If you don’t understand adb and fastboot, you probably don’t need S-off.
Lastly, the work herein should not be stolen, repackaged, one clicked, bat’d, etc. soffbin3 is not GPL and may not be reused, integrated into other work, reposted, or redistributed without our permission.
For this to work, you must be rooted and have superCID (unlock/custom recovery is optional), see the threads below for help and information regarding obtaining superCID, unlock, root, etc. Note these threads are provided for convenience only. Please look for support for them in each respective thread if you need it, do NOT clutter this thread with support requests regarding obtaining superCID and/or root! If you try this process without superCID, it will not work, and you may have issues!:
SuperCID for HTC One VX:
http://forum.xda-developers.com/showthread.php?t=2161402
Download modified boot.img:
http://d-h.st/NDT (mirror http://androidfiles.org/securekey.php?file=TotemC2/s-off/OneVX-rescure.img)
Download signed firmware:
http://androidfiles.org/securekey.php?file=TotemC2/s-off/rom.zip 481722658bfc79cab4c9d92d819da655 (Do not worry, as long as you have superCID this will not flash and data will not be wiped)
1)
Code:
adb reboot bootloader
2)
Code:
fastboot oem rebootRUU
(wait for black HTC Screen)
3)
Code:
fastboot flash zip rom.zip
(This will take some time, time will be reduce once someone provides me with an update.zip from an OTA)
After a while, You should see the following error “FAILED (remote: 92 supercid! please flush image again immediately)”
7) Immediately issue the following command:
Code:
fastboot boot OneVX-rescure.img
(this is fastboot boot, NOT fastboot flash!)
8)
Code:
adb reboot bootloader
9) You should see what you are looking for!
If you need help or just care to say thanks, join us on IRC: #FacePalm http://chat.andirc.net:8080/?channels=facepalm
Enjoy.
Thanks! S-off now and working on recovery
https://www.dropbox.com/s/i3gczu19kwfuazr/2013-02-22 16.16.23.jpg
This is great! Can't believe this is here ! :happy dance:
nevermind size is too huge!
This worked for me, but now my boot animation don't work, I just get a black screen during boot up.
Replicatorz said:
This worked for me, but now my boot animation don't work, I just get a black screen during boot up.
Click to expand...
Click to collapse
either flash ruu or flash the boot.img from my root package. Same thing happened to me during testing.
can somebody help me. what directory do i put those 2 files that i downloaded ? thanks
grigoriisi said:
can somebody help me. what directory do i put those 2 files that i downloaded ? thanks
Click to expand...
Click to collapse
Same as your adb and fastboot folders.
Success!
When you issue the "fastboot flash zip rom.zip" command, the one that takes awhile, there will be some other output in the terminal. Don't get nervous and jump the gun, it will print, pause, print, pause, etc. Just to be sure I opened a second cmd prompt in that directory and had "fastboot boot OneVX-rescure.img" already typed and ready to press enter. When the first terminal finished the command and returned me to the C:> prompt, I made sure I saw the failed message then pressed enter immediately in the second. Worked like a charm!
Thanks to all devs who contributed!
Work's great, now i'm totally free with me VX
May I get any issue if I just root & install TWRP without S OFF and SuperCID?
Sent from my GT-N5100 using Tapatalk 2
instruction please
jpnazar08 said:
instruction please
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?p=38346549
Sent from my HTC One VX using xda app-developers app
sidaivelez said:
http://forum.xda-developers.com/showthread.php?p=38346549
Sent from my HTC One VX using xda app-developers app
Click to expand...
Click to collapse
fastboot flash zip rom.zip cant load the zip why???
This is how the firmware gets loaded. Just follow the steps all is good by the end
Sent from my HTC One VX using xda app-developers app
i got scid to work, but the link for "rom.zip" is down. any where else i can get it? nvm. found it.
File not found sir ! rom.zip
You can find it here: androidfiles.org
jcase said:
For other HTC devices supported by FacePalm, please see this thread: http://forum.xda-developers.com/showthread.php?t=2155069
Welcome to Facepalm S-Off for modern HTC phones.
Credits and terms:
Exploit by beaups, full guide, testing, and concept by jcase and beaups. Thanks to dsb9938 and dr_drache for support and testing. Thanks also to all of the regulars at teamandirc.
Both beaups and jcase will collect the applicable active bounties. Further donations are greatly appreciated and can be sent to:
beaups - [email protected] - http://forum.xda-developers.com/donatetome.php?u=711482
jcase - [email protected] - http://forum.xda-developers.com/donatetome.php?u=2376614
dsb9938 - [email protected] - http://forum.xda-developers.com/donatetome.php?u=2963256
dr_drache - [email protected] - https://www.paypal.com/cgi-bin/webscr?cmd=_s-xclick&hosted_button_id=6LRSY8MT8P3A6
You can also come by irc for support or just to say thanks: #FacePalm http://chat.andirc.net:8080/?channels=facepalm
While this process shouldn’t be too risky, bricks can happen. None of us will be accountable. If you are worried, don’t do it.
This is a pretty simple method, however, you will need to have a working adb and fastboot environment. This method will work on any operating system that supports adb and fastboot. You should understand how to use a terminal window in your O/S. If you don’t understand adb and fastboot, you probably don’t need S-off.
Lastly, the work herein should not be stolen, repackaged, one clicked, bat’d, etc. soffbin3 is not GPL and may not be reused, integrated into other work, reposted, or redistributed without our permission.
For this to work, you must be rooted and have superCID (unlock/custom recovery is optional), see the threads below for help and information regarding obtaining superCID, unlock, root, etc. Note these threads are provided for convenience only. Please look for support for them in each respective thread if you need it, do NOT clutter this thread with support requests regarding obtaining superCID and/or root! If you try this process without superCID, it will not work, and you may have issues!:
SuperCID for HTC One VX:
http://forum.xda-developers.com/showthread.php?t=2161402
Download modified boot.img:
http://d-h.st/NDT (mirror http://androidfiles.org/securekey.php?file=TotemC2/s-off/OneVX-rescure.img)
Download signed firmware:
http://androidfiles.org/securekey.php?file=TotemC2/s-off/rom.zip 481722658bfc79cab4c9d92d819da655 (Do not worry, as long as you have superCID this will not flash and data will not be wiped)
1)
Code:
adb reboot bootloader
2)
Code:
fastboot oem rebootRUU
(wait for black HTC Screen)
3)
Code:
fastboot flash zip rom.zip
(This will take some time, time will be reduce once someone provides me with an update.zip from an OTA)
After a while, You should see the following error “FAILED (remote: 92 supercid! please flush image again immediately)”
7) Immediately issue the following command:
Code:
fastboot boot OneVX-rescure.img
(this is fastboot boot, NOT fastboot flash!)
8)
Code:
adb reboot bootloader
9) You should see what you are looking for!
If you need help or just care to say thanks, join us on IRC: #FacePalm http://chat.andirc.net:8080/?channels=facepalm
Enjoy.
Click to expand...
Click to collapse
the rom is link is dead
Code Of Conduct123 said:
the rom is link is dead
Click to expand...
Click to collapse
and I no longer have it, you will either have to hunt it down, or try a new solution like SunShine (which im not sure works on this phone, worth a try)
Is it Bricked?
and how long does it stay on the black htc screen
MY ISSUE seems unique!! Please, is anyone able to figure this out?
I have a HTC Wilfire S A510e that I've been trying to root for three months!
It's stats are:
***LOCKED***
Marvel PVT SHIP S-ON RL
MICROP-0451
Radio 7.57.39.10M
Android: 2.3.5
ROM: 2.26.401.3
Kernal: 2.6.35.10
HBoot: 1.09.
HTC Sense Version: 2.1
SO...I created my a/c on HTCDEV.COM, tick all boxes etc. No need to update bootloader, as per instructions, so I "proceed to next step".
I created \Android ( in My Documents) on my Dell Latitude D630 (using Windows XP); downloaded the "Fastboot binary, Windows (unzip the file before executing)" file [Fastboot-Zip] to \Android & also the recommended Android SDK zip, Java Runtime Environment. I already have HTC Sync 3.3.63. All unzipped. I set up my HTC- fastboot off, usb debugging enabled, bootloader screen up> click on fastboot, usb into it, the phone registers "Fastboot USB" and then open the cmd prompt on my pc.
The problem I encounter is this:
On the cmd prompt instructions:
I open cmd prompt- My pc cmd line says c:\documents and settings\administrater>[blinking cursor]. I type- c: cd \Android at the blinking cursor. That's okay as my cmd line returns- c:\documents and settings\administrater>[blinking cursor] again.
I type- c: \Android> fastboot oem get_identifier_token at the blinking cursor [hit enter] and...
Nothing happens! Nothing at all- not even the "waiting for device" problem that seems to be common at this stage.
I'm meant to get:
INFO <Please cut following info>
INFO <<<< Identifier Token Start >>>>
INFO {**multi lines of numerical text**}
I get nothing!
What's going wrong?? I've done weeks and weeks of research using google search; read hundreds of threads on multiple sites; in frustration I've even asked a question on Yahoo Answers, Android Forums & emailed HTCdev, but had only one answer and it was to use another port and another cable, both of which I've done, neither worked.
I just don't get it. Any assistance would be fantastic.
Thanks, Gerry
GERJDOY said:
MY ISSUE seems unique!! Please, is anyone able to figure this out?
I have a HTC Wilfire S A510e that I've been trying to root for three months!
It's stats are:
***LOCKED***
Marvel PVT SHIP S-ON RL
MICROP-0451
Radio 7.57.39.10M
Android: 2.3.5
ROM: 2.26.401.3
Kernal: 2.6.35.10
HBoot: 1.09.
HTC Sense Version: 2.1
SO...I created my a/c on HTCDEV.COM, tick all boxes etc. No need to update bootloader, as per instructions, so I "proceed to next step".
I created \Android ( in My Documents) on my Dell Latitude D630 (using Windows XP); downloaded the "Fastboot binary, Windows (unzip the file before executing)" file [Fastboot-Zip] to \Android & also the recommended Android SDK zip, Java Runtime Environment. I already have HTC Sync 3.3.63. All unzipped. I set up my HTC- fastboot off, usb debugging enabled, bootloader screen up> click on fastboot, usb into it, the phone registers "Fastboot USB" and then open the cmd prompt on my pc.
The problem I encounter is this:
On the cmd prompt instructions:
I open cmd prompt- My pc cmd line says c:\documents and settings\administrater>[blinking cursor]. I type- c: cd \Android at the blinking cursor. That's okay as my cmd line returns- c:\documents and settings\administrater>[blinking cursor] again.
I type- c: \Android> fastboot oem get_identifier_token at the blinking cursor [hit enter] and...
Nothing happens! Nothing at all- not even the "waiting for device" problem that seems to be common at this stage.
I'm meant to get:
INFO <Please cut following info>
INFO <<<< Identifier Token Start >>>>
INFO {**multi lines of numerical text**}
I get nothing!
What's going wrong?? I've done weeks and weeks of research using google search; read hundreds of threads on multiple sites; in frustration I've even asked a question on Yahoo Answers, Android Forums & emailed HTCdev, but had only one answer and it was to use another port and another cable, both of which I've done, neither worked.
I just don't get it. Any assistance would be fantastic.
Thanks, Gerry
Click to expand...
Click to collapse
First things first, your problem is not unique..........just less often found
The reason you are not able to get an Identifier token is because of HTC Sync............. HTC Sync usually tends to block any ADB or Fastboot commands
So all you have to do is uninstall HTC Sync, don't worry about it as uninstalling it won't remove the drivers
Thanks very much for replying csoulr666
I promptly uninstalled HTC Sync, leaving:
HTC BMP USB Driver (Ver: 1.0.5375 ) 0.35MB
HTC Driver Installer (4.5..001 ) 2.82MB
and have tried the "get token" process again.
It has not worked.
Do you think that I should also uninstall the HTC Driver Installer?
GERJDOY said:
Thanks very much for replying csoulr666
I promptly uninstalled HTC Sync, leaving:
HTC BMP USB Driver (Ver: 1.0.5375 ) 0.35MB
HTC Driver Installer (4.5..001 ) 2.82MB
and have tried the "get token" process again.
It has not worked.
Do you think that I should also uninstall the HTC Driver Installer?
Click to expand...
Click to collapse
It should work now IMHO, did you see if your device is being recognized using "fastboot devices"???
Plus setting the folder to apply commands("cd"), try using the complete path that comes in the address bar in My Computer/Windows Explorer..........It would be like C................documents and settings......blah blah blah
Hi,
If you can not find a solution for your method of getting the token, you may try another method that worked fine for me.
1) Search for HTC Wildfire S All-In-One Toolkit V2.1 post.
2) Read carefully the whole post.
3) Uninstall everything related to HTC (HTC Sync, USB drivers, everything).
4) Do not use USB hubs or USB 3.0 ports. Enable USB Debugging at the phone settings and plug the phone directly to an USB 2.0 port without the SIM and SD cards (they may be erased while unlocking). Choose the Charge only option in your phone.
5) Proceed with the tool steps (select the step and click on 'go')(in useful links there is a link to a step by step guide):
a) Install the drivers.
b) Register at HTCDev (this is already done).
c) Get the ID (beware, you will see and empty command prompt, close it, and a second command window will appear with the token)
d) Submit the token to HTCDev.
e) Get the Unlock_code.bin file from your e-mail account.
f) Unlock the boot loader.
6) Once you have finished, I recommend to install the clockworkmod recovery with the same tool. Download the right version GSM or CDMA from the Clockworkmod official site. Beware: make sure that you download the right version for your phone. I think yours is GSM, but I am not an expert, sorry. It may be fatal if the wrong version is installed (brick). Choose the option your own recovery in the tool.
7) Create a backup before doing anything else.
8) You are ready to get a permanent root or install a ROM.
I hope this helps you. Feel free to ask any question. Regards.
GERJDOY said:
MY ISSUE seems unique!! Please, is anyone able to figure this out?
I have a HTC Wilfire S A510e that I've been trying to root for three months!
It's stats are:
***LOCKED***
Marvel PVT SHIP S-ON RL
MICROP-0451
Radio 7.57.39.10M
Android: 2.3.5
ROM: 2.26.401.3
Kernal: 2.6.35.10
HBoot: 1.09.
HTC Sense Version: 2.1
SO...I created my a/c on HTCDEV.COM, tick all boxes etc. No need to update bootloader, as per instructions, so I "proceed to next step".
I created \Android ( in My Documents) on my Dell Latitude D630 (using Windows XP); downloaded the "Fastboot binary, Windows (unzip the file before executing)" file [Fastboot-Zip] to \Android & also the recommended Android SDK zip, Java Runtime Environment. I already have HTC Sync 3.3.63. All unzipped. I set up my HTC- fastboot off, usb debugging enabled, bootloader screen up> click on fastboot, usb into it, the phone registers "Fastboot USB" and then open the cmd prompt on my pc.
The problem I encounter is this:
On the cmd prompt instructions:
I open cmd prompt- My pc cmd line says c:\documents and settings\administrater>[blinking cursor]. I type- c: cd \Android at the blinking cursor. That's okay as my cmd line returns- c:\documents and settings\administrater>[blinking cursor] again.
I type- c: \Android> fastboot oem get_identifier_token at the blinking cursor [hit enter] and...
Nothing happens! Nothing at all- not even the "waiting for device" problem that seems to be common at this stage.
I'm meant to get:
INFO <Please cut following info>
INFO <<<< Identifier Token Start >>>>
INFO {**multi lines of numerical text**}
I get nothing!
What's going wrong?? I've done weeks and weeks of research using google search; read hundreds of threads on multiple sites; in frustration I've even asked a question on Yahoo Answers, Android Forums & emailed HTCdev, but had only one answer and it was to use another port and another cable, both of which I've done, neither worked.
I just don't get it. Any assistance would be fantastic.
Thanks, Gerry
Click to expand...
Click to collapse
I think you are doing wrong with the c: android step you should first "cd android" and then enter "fastboot oem get_identifier_token"
csoulr666 said:
It should work now IMHO, did you see if your device is being recognized using "fastboot devices"???
Plus setting the folder to apply commands("cd"), try using the complete path that comes in the address bar in My Computer/Windows Explorer..........It would be like C................documents and settings......blah blah blah
Click to expand...
Click to collapse
Thanks for your continued time and assistance csoulr666. It's taken me a while to reply because after having no sucess having followed your advice, I decided to delete EVERYTHING and IT ALL FRESH, monitoring all downloads as they happened and ensuring I followed all steps and instructions PRECISELY, in case I did something wrong the first time around 3 months ago!
And following your recommendation I retried using the full path when typing both commands and it still didn't work. I'm not sure what you meant by "........your device is being recognized using "fastboot devices"???"
However, as you've mentioned "fastboot", I think I've identified an issue with the fastboot binaries from HTCdev. Please see my new post below.
aWFSuser said:
I think you are doing wrong with the c: android step you should first "cd android" and then enter "fastboot oem get_identifier_token"
Click to expand...
Click to collapse
aWFSuser- thank you for the advice.Yes, I do use the c: cd \Android command first, everytime I try the cmd process, even if it's after somthing silly like removing the sd card from the phone, putting a new one in (to render the "as disk drive" option available in the "USB connection type") on the handset, changing the USB port I'm using to a different one etc.
But thanks.
ukyo_tachibana said:
Hi,
If you can not find a solution for your method of getting the token, you may try another method that worked fine for me.
1) Search for HTC Wildfire S All-In-One Toolkit V2.1 post.
2) Read carefully the whole post.
3) Uninstall everything related to HTC (HTC Sync, USB drivers, everything).
4) Do not use USB hubs or USB 3.0 ports. Enable USB Debugging at the phone settings and plug the phone directly to an USB 2.0 port.
5) Proceed with the tool steps (select the step and click on 'go')(in useful links there is a link to a step by step guide):
a) Install the drivers.
b) Register at HTCDev (this is already done).
c) Get the ID (beware, you will see and empty command prompt, close it, and a second command window will appear with the token)
d) Submit the token to HTCDev.
e) Get the Unlock_code.bin file from your e-mail account.
f) Unlock the boot loader.
6) Once you have finished, I recommend to install the clockworkmod recovery with the same tool. Download the right version GSM or CDMA from the Clockworkmod official site. Beware: make sure that you download the right version for your phone. I think yours is GSM, but I am not an expert, sorry. It may be fatal if the wrong version is installed (brick). Choose the option your own recovery in the tool.
7) Create a backup before doing anything else.
8) You are ready to get a permanent root or install a ROM.
I hope this helps you. Feel free to ask any question. Regards.
Click to expand...
Click to collapse
Thanks so much ukyo_tachibana.
I will try this method, if I have failed to identify the issue correctly.
After having the problem of being unable to obtain my identifier token for so long, (trying now for 3 months!), I've been looking for a way to unlock bootloader & root- that works for the Wildfire S WITHOUT having to use the "get_identifier" process.
THANK YOU for this method!
It's taken me a while because after having no sucess, I decided to delete EVERYTHING and IT ALL FRESH, monitoring all downloads as they happened and ensuring I followed all steps and instructions PRECISELY, in case I did something wrong the first time around 3 months ago!
So, once again:
I created a folder: double click Local Disk C: then \Document&Settings and \administrater >Make a new folder. Called it Android.
Downloaded from HTCdev's links- HTC Sync, Java Runtime Enviroment & Google Android SDK to \Android.
(1) SYNC. Uninstalled Sync, as per csoulr666's advice. Used Control Panel> Add or Remove programs. This left HTC Driver Installer & HTC BMP USB Driver & also setup_3.3.63 (in \Android).
(2) JAVA. Opened chromeinstall-7u51(Runtime) and installed. Checked it installed correctly via Verify Java Version on java.com.
(3) SDK. Unzipped the zipped folder adt-bundle-windows-x86-201... It created a new folder- "adt-bundle-windows-x86-201.." with 2 subfolders & 1 application in it; subfolders (1)"eclipse" & (2)"sdk" along with the application "SDK Manager". NOW, as per instruction following the SDK download, (just in case it was relevant to what I am doing, although I don't think so as Eclipse is a developer tool as I understand it), I opened the eclipse sub-folder & opened (ran) the Eclipse application which set itself up in \workforce. I exited Eclipse in case it interfered with anything else. I did not run, open or do anything else with the adt folder at this stage.
Set up my HTC as per instruction- fastboot off, debugging on & usb to disk drive, (I've also tried it on the charge only setting), downloaded fastboot-win binaries from HTCdev to \Android. Clicked unzip and it generated 1 new folder _MACOSX & an application- fastboot; both in \Android. NOW HTCdev says "open cmd prompt...etc". So I did and retried the process twice. Once typing c: cd \Android. Then the c: \Android> fastboot oem...etc. It didn't work. So I repeated the process using the full path in both the commands- c:\Documents and Settings\administrater\ cd \Android; then c:\Doc...Sett...\admin...\Android> fastboot....Once again nothing. IT DID NOT WORK.
HOWEVER: I did notice 2 things!
(1) Probably nothing but there was a new folder created in \administrater, right beside the Android folder. As I was working from \Android, I didn't notice when happened. I did not do it. It called itself .android; ( "a dot" and a lowrecase "a" for android). I can't recall at what stage of the process this came into being. It contains 1 folder- "avd", which is empty, & 3 files- "adbkey" file, "adbkey.pub" file & "ddms.cfg" file.
(2) Just, following the latest failure of the cmd process working, I thought maybe I was meant to do more than just unzip the fastboot-win, so I went to the fastboot application and tried to open it, It said:
"The application failed to start because AdbWinApi.dll was not found. Re-installing the application may fix the problem"
So I deleted it, re-downloaded from HTCdev, unzipped. Opened prompt, reran the cmd "get_identifier" process and it still hasn't worked. Again I to run the fastboot.exe in \Android
It still says "...application failed...AdbWinApi was not found. Re-installing the application...".
Does this mean the file download itself on HTCdev,com is corrupt? Could THIS BE the source of my problem????
Thanks.
I'm attaching a zip with the files I use for this stuff............Extract them in a folder, use the "cd" command to it and then try to obtain the token
csoulr666 said:
I'm attaching a zip with the files I use for this stuff............Extract them in a folder, use the "cd" command to it and then try to obtain the token
Click to expand...
Click to collapse
***csoulr666
Yes!! Thank you for the files. HTC's MUST BE corrupt, as your's have worked a treat & also. they behave differently ( "fastboot" application) when <highlight/right click > is used!! No error message! THANK YOU for your files. ***
They worked & after three months and hundreds of hours research, I HAVE MY TOKEN!! You guys are BRILLIANT!
However, there is a new issue, perhaps you can help with this also...
I copied the token exactly as HTC stated on their website. I started at <<<Identifier Token Start>>> & ended with <<<IIdentifier Token End>>>.
There are 18 lines in total- 16 lines of alpha/numeric sandwiched between the above 2 of text.
Both of HTC's examples also have the same line-count (18 in total 16 + 2) & layout as mine.
But when submitted, the website rejects it and the following error is returned:
Error Code: Invalid Bootloader Token Length.
Error Reason: The submitted Token appears to be the wrong length and won't work.
I've spent most of last night on this. I've tried logging in and out of HTCdev, copied and pasted multiple attempts (busy web traffic perhaps). I have cleared browser cookies/cache & history in case it's something like that. Counted and recounted my token in comparison with their examples, in case I made a mistake somehow. What am I doing wrong??.
Also, today when I tried the cmd get_token process, I got a different token i.e. a completely different set of 16 lines of alpha/numeric text. Is the token different every time it's requested?
Thank you all for your expert help
GERJDOY said:
***csoulr666
Yes!! Thank you for the files. HTC's MUST BE corrupt, as your's have worked a treat & also. they behave differently ( "fastboot" application) when <highlight/right click > is used!! No error message! THANK YOU for your files. ***
They worked & after three months and hundreds of hours research, I HAVE MY TOKEN!! You guys are BRILLIANT!
However, there is a new issue, perhaps you can help with this also...
I copied the token exactly as HTC stated on their website. I started at <<<Identifier Token Start>>> & ended with <<<IIdentifier Token End>>>.
There are 18 lines in total- 16 lines of alpha/numeric sandwiched between the above 2 of text.
Both of HTC's examples also have the same line-count (18 in total 16 + 2) & layout as mine.
But when submitted, the website rejects it and the following error is returned:
Error Code: Invalid Bootloader Token Length.
Error Reason: The submitted Token appears to be the wrong length and won't work.
I've spent most of last night on this. I've tried logging in and out of HTCdev, copied and pasted multiple attempts (busy web traffic perhaps). I have cleared browser cookies/cache & history in case it's something like that. Counted and recounted my token in comparison with their examples, in case I made a mistake somehow. What am I doing wrong??.
Also, today when I tried the cmd get_token process, I got a different token i.e. a completely different set of 16 lines of alpha/numeric text. Is the token different every time it's requested?
Thank you all for your expert help
Click to expand...
Click to collapse
see whether you have copied the code correctly as instructed at HTCdev
Hi,
The token seems to be different every time you retrieve it, I don't know why (maybe someone can enlighten us ).
Regarding the token copy/paste. At the command window: right click, select mark, draw the rectangle enclosing the <<<< Identifier Token Start >>>> and <<<<< Identifier Token End >>>>> (this also includes all the alphanumeric token), right click again to copy. Now, paste it in Notepad, PSPad or any other text editor, and make sure that there are no white spaces, tabs, or any other special character, such as this example:
Code:
<<<< Identifier Token Start >>>>
5C1161E707F362366365EA333A6B51D6
7B52743B74534195B1C0CD07E738AEA3
93A6BD42CFA2C05006C6282B590CEDC3
6593DE3AEF7786B79527C1027E871C3D
9DDD04692D8F653D9BD548D86CB0AC58
01CDF6096D229B7E418BD74E8AC2311C
77D92CE222450E4B233CEC2286DD9CA4
C0871C78B430F4474C74FCE113E95C2D
2134C5495D588B3A580710A226A6675C
3D9F01CB8A8EF628A4EC2BB867E47D3E
2476FE360221DC834197EAECCA4BB09A
243420AEB1CFC713A658FC0A156448A9
6859FF58473B71BDFFFF5FFF292B066B
9CA1B055827C43BFE0F30A656906801E
35FD964354DAA6F83A38FE7D7452B97A
171BDB3A9D280118C638240DEDA452DE
<<<<< Identifier Token End >>>>>
If you select previous lines, there are no unwanted characters, check it. Once you are sure that everything is okay, submit the token to HTC.
I hope this post helps you. Regards.
By the way, two comments:
1) Note that unlocking HBoot is a destructive process, you will loose everything in the phone memory (similar to a factory reset). Besides, the SIM card and the SD card may be also erased, so remove both before starting.
2) If you want to install a custom rom, you don't know which one to install yet and you want some help, I can suggest one that has been working like a charm for more than one year in my Wildfire S. It is based on the last stock rom, but with several tweaks to overcome the limitations of the terminal (amount of RAM, internal storage, etc.). Do not hesitate to ask.
Regards.
ukyo_tachibana said:
Hi,
The token seems to be different every time you retrieve it, I don't know why (maybe someone can enlighten us ).
Regarding the token copy/paste. At the command window: right click, select mark, draw the rectangle enclosing the <<<< Identifier Token Start >>>> and <<<<< Identifier Token End >>>>> (this also includes all the alphanumeric token), right click again to copy. Now, paste it in Notepad, PSPad or any other text editor, and make sure that there are no white spaces, tabs, or any other special character, such as this example:
Code:
<<<< Identifier Token Start >>>>
5C1161E707F362366365EA333A6B51D6
7B52743B74534195B1C0CD07E738AEA3
93A6BD42CFA2C05006C6282B590CEDC3
6593DE3AEF7786B79527C1027E871C3D
9DDD04692D8F653D9BD548D86CB0AC58
01CDF6096D229B7E418BD74E8AC2311C
77D92CE222450E4B233CEC2286DD9CA4
C0871C78B430F4474C74FCE113E95C2D
2134C5495D588B3A580710A226A6675C
3D9F01CB8A8EF628A4EC2BB867E47D3E
2476FE360221DC834197EAECCA4BB09A
243420AEB1CFC713A658FC0A156448A9
6859FF58473B71BDFFFF5FFF292B066B
9CA1B055827C43BFE0F30A656906801E
35FD964354DAA6F83A38FE7D7452B97A
171BDB3A9D280118C638240DEDA452DE
<<<<< Identifier Token End >>>>>
If you select previous lines, there are no unwanted characters, check it. Once you are sure that everything is okay, submit the token to HTC.
I hope this post helps you. Regards.
Click to expand...
Click to collapse
BRILLIANT!!
I followed your recommendation- copy to notepad- there were white spaces:
Note: the <right click/copy> function was not available in cmd prompt.
I had to "mark" and then ctrl & c to copy.
I had spaces at the end of each of the token's lines.
Thanks. Token successfully submitted- just over ten minutes ago. Awaiting an email back from HTCdev with an unlock key and link for Unlock completion!
I assumed I'd have it instantaneously...but I'll be patient; it's taken this long to get this far...what's a few hours? more.
I have not given ANY thought to ROMs etc.
This part of the process baffles me.
This all began three months ago when I got the Wildfire S- my first ANDROID phone- and I noticed there are loads of pre-installed apps on it, many of which I have absolutely no interest in: like Peep, News & Weather, Maps & tons more via: Applications>Running Services>All. TO MY UTTER AMAZMENT I could not delete any of them!
Call me old fashioned but I would like to decide what I put on my phone and have total control over them. On this phone certain apps would start up of their own volition i.e. when the handset was powered off, then on; gather information and data; all without me even using/ activating them e.g. Google services/ Facebook. I could stop them manually, but like I said they would reassert themselves on start-up.
I'm unclear yet exactly what I can safely get rid of without damaging my handset, I need to do research I know, as some processes may be vital to the phone's operation, but I have been consumed with this first basic step- Unlocking the BootLoader.
Ideally, I would love to start with an empty phone- just the basics: calls/messages/phone book/ calender/ alarm facilities with a browser.
A normal, basic phone.
Any extra apps I am then free to decide upon, install, set permissions (where possible) & remove as & if I choose.
Thanks.
Hi,
Did you get the unlock binary file? It should take no longer than a few minutes (or even less) to send it to your e-mail account. Did you successfully unlock the HBoot? Let us know . Regards.
ukyo_tachibana said:
Hi,
Did you get the unlock binary file? It should take no longer than a few minutes (or even less) to send it to your e-mail account. Did you successfully unlock the HBoot? Let us know . Regards.
Click to expand...
Click to collapse
Hi ukyo_tachibana,
Thank you for your ongoing interest. I appreciate it greatly.
I have been checking my email address all night last night, and also today, awaiting my email from HTCdev.
No! As yet (over 24 hours later), I have not yet received my response.
HTCdev's site confirmed that I successfully sent my token when I did. I remained logged in for a hour and a half afterwards, just so the site would notice/ remember me. Sounds daft, but I really want this episode to finish now after all this time. I really thought I had cracked this step!
The web page said to expect and email with my unlock code and a link to directions to help me complete the process.
Now, over 24 hours later, I still have not received any communication from them. I check my email address- the one I used to register with them and, in late December of last year, communicate as to why I the "get_identifier token" process was not working- ever hour or so for the file & link. So I'm sure the site has my correct email address.
I was actually wondering what to do now as I'm unsure as whether I should wait X amount of time, contact them via the "contact us" option on their web site or resend a token to them and risk confusing the process. Basically I'm just playing the waiting/ unsure-of-next-move game.
Thanks.
Hi,
Do not despair . The token should be send to you in question of seconds (but in order to be safe wait a few minutes, no more than 5 minutes). The email sender should be something like [email protected] and the subject should be The key to unlocking your HTC Device (at least, this is what I received).
I would:
1) Search for the email in any other folder than the Inbox, such as spam. Your email provider may have archived the message in a different folder.
If you are not able to find the message:
2) Try to find your email white list and add htc.com and htcdev.com to the list, in order to avoid that emails from HTC or HTC Dev go to the spam folder or are erased.
3) Check that you activated your account. Register at the website is not enough, you also must activate your account clicking on the link that HTC send to confirm your email address. I know that this question is a bit stupid, but it just to cover all the possibilities that I can think about.
4) Get and send again the token.
I hope this helps you. Regards.
I have my email now.
Before I proceed, as I'm a complete techno-novice, I was just looking into how to create a full back up of my stock ROM, in case I decided to pass on the phone later I can return it to it's current out-of-the box condition- with all it's apps etc. Also I need to be clear on the root process files. I don't have the original SD Card. I have two to hand though- a 2GB & 4 GB.
Step 1- Unlock BootLoader.
REALLY, REALLY NOT sure of the rest:
Step 2- download CWM Recovery from (http://www.clockworkmod.com/rommanager/) 5.0.2.8 for the Wiidfire S to my PC.
?Move to SD Card
?Hboot>Recovery>chooseCWM and there should be an option to "Back-Up/ Restore"
?Select this option and "Back-Up". Wait for stoc ROM to be copied onto SD Card. When it has this is the back-up phase complete
As I understand it this will give me a re-installation disk type set up for my current ROM.
Step 3
?Find and download a file to my PC called "Root Zip".
?Transfer it to my SD Card
?Hboot>Recovery>choose file and it roots the phone itself.
Step4
?Find and download a file called "SuperSU"
?Move to SD Card and install.
??This gives me an app called "SuperSU" which allows me now to modify my phone how I like it to be- prevent apps starting at boot/ remove any preinstalled ones that I don't want or do I need to install a custom ROM?
Thanks,
My goal for this thread is to gather as much info for the BLU Life One X 2016.
Specs
Screen: 5.2", 1080 x 1920 pixels, ~424 ppi, Gorilla Glass 3
Memory: 2 GB RAM, 16 GB storage, microSD slot (up to 64GB)
Camera: 13 MP rear, 5 MP front, LED flash front & rear, [email protected] video
Battery: Li-Ion 2900 mAh
Chipset: Mediatek MT6753
CPU: Octa-core 1.3 GHz Cortex-A53
GPU: Mali-T720
Model: L0070UU
Links & Other General Resources
BLU Products
Amazon: Black - White
GSMArena
BLU Products Development Team (Google+)
L0070UU User Manual
ClanGSM claim to have firmware files for our phone but it would cost $$$ to download: / mnt / data / ftp / Flashes / BLU / Life One X / L0070UU /
Similar Phones
Wiko Fever (GSMArena)
Micromax Canvas 5 (GSMArena)
XOLO Black 1X (GSMArena)
Elephone P8000 (CM12.1) and P6000 Pro
Quantum Go 4G (PhoneMore)
WARNING: *I* cannot be held responsible for anything *you* do to *your* phone!
Note: While I use a variety of operating systems on a regular basis everything here will be Windows 10 focused.
ADB & Fastboot
Before doing most things mentioned below you will need "adb" and "fastboot" installed. Two of your options are to install the Android SDK Tools or the Minimal ADB and Fastboot tool. If you are somewhat new to this I highly recommend the second one. Go here, download the latest version (1.3.1 as of this writing), and install it. When setup is complete you should have an icon for the Minimal ADB and Fastboot tool.
Note: I highly recommend you add "C:\Program Files (x86)\Minimal ADB and Fastboot" to your PATH variable in Windows. This way you can open a Command Prompt anywhere and use adb or fastboot.
Drivers
I recently setup a 5th gen Kindle Fire 7" tablet on my Windows 10 desktop. Because the BLU Life One X 2016 and the Kindle Fire are similar enough it just worked. To use the Amazon drivers you can find them on this page: https://developer.amazon.com/public...etting-up-your-kindle-fire-tablet-for-testing. The direct link is https://s3.amazonaws.com/android-sdk-manager/redist/kindle_fire_usb_driver.zip. Extract the zip file and then run KindleDrivers.exe.
Unlock Bootloader, Install Custom Recovery, and Install Root
Note #1: All credit for this guide goes to manos78's post for rooting the Wiko Fever!!! You can check it out here.
Note #2: I use Windows 10 on every PC I own. I assume Windows 7 and 8 should work just fine but cannot test that.
Note #3: The following assumes you have setup ADB and the proper drivers before beginning. I will try to detail that at a future time.
Note #4: Your phone will be completely erased. If there is anything you want to save do so beforehand.
1) Unlock Bootloader
Power on the phone and skip through all of the setup options
Go to Settings -> About device
Tap Build number five times to enable Developer options
Go to Settings -> Developer options
Enable OEM unlocking
Enable USB debugging
Plug the phone in to your PC and authorize it
Open a Command Prompt
Type adb reboot-bootloader
The phone should reboot and in a very tiny font at the bottom you should see => FASTBOOT mode
Type fastboot devices to verify that your PC sees it correctly
Type fastboot oem unlock
Press Volume Up to say Yes and wait for this to finish
Type fastboot getvar all and look for (bootloader) unlocked: yes
Type fastboot reboot
You should see your phone reboot a couple times as it erases the phone
2) Install Custom Recovery
Note #1: We will flash a version of CWM or TWRP that was built for a Wiko Fever as they appear to be fully compatible with the BLU Life One X 2016. Go to this thread and download the latest CWM (http://www.sendspace.com/file/4g87bj) or TWRP (http://www.sendspace.com/file/y4jel8). Extract the img file. Again, many thanks to manos78 for CWM and hanuma for TWRP!!!
Power on the phone
You can configure your phone now or just skip through all of the setup options and do that later
Go to Settings -> About device
Tap Build number five times to enable Developer options
Go to Settings -> Developer options
Enable OEM unlocking
Enable USB debugging
Plug the phone in to your PC and authorize it
Open a Command Prompt to wherever you extracted the .img file
Type adb reboot-bootloader
The phone should reboot and in a very tiny font at the bottom you should see => FASTBOOT mode
Type fastboot devices to verify that your PC sees it correctly
For CWM type fastboot flash recovery recovery-custom-wiko-fever.img or for TWRP type fastboot flash recovery TWRP_WikoFever_2.8.7.0.img
Type fastboot reboot
Note: If your phone does not reboot then just hold the power button until it turns off. Hold the power button again until it turns back on.
3) Install Root
Note: While there are newer beta versions of the SuperSU app I am not sure if they will work properly on our stock rom. You can test one of those out and report back but I would recommend you do a full backup beforehand.
Download BETA-SuperSU-v2.52.zip and save it to the phone's internal memory or an inserted microSD card
Plug the phone in to your PC
Open a Command Prompt
Type adb reboot recovery
You should now be in CWM. Go to Install zip, find BETA-SuperSU-v2.52.zip, and install it
When it finishes go to Go Back -> Reboot Phone -> No
Once the phone boots up launch SuperSU and configure it as you like
Xposed
Download the latest version of Xposed for sdk22 and arm64 from here. As of this writing it is xposed-v79-sdk22-arm64.zip. Also download XposedInstaller_3.0_alpha4.apk and xposed-uninstaller-20150831-arm64.zip (just in case).
Reboot into CWM or TWRP and do a full backup
Install xposed-v79-sdk22-arm64.zip and then reboot
Cross your fingers and hopefully your phone will start properly. Mine rebooted like five times during the "Android is starting" step but finally finished.
Once your phone boots up install XposedInstaller_3.0_alpha4.apk
ViPER4Android
ViPER4Android adds audio effects to your Android device and is beloved by many. First we will install SELinuxModeChanger and then ViPER4Android. Special thanks to Tha Watcher for his original write-up here.
1) SELinuxModeChanger
Go to the SELinuxModeChanger page on F-Droid, download the latest version (3.2 as of this writing) or use this direct link, and save it to your Desktop
Launch Minimal ADB and Fastboot and type adb install %USERPROFILE%\Desktop\com.mrbimc.selinux_42.apk
On the phone you may see a prompt saying Installation Blocked. If so, click the little triangle and tap Install anyway (unsafe). If you see a failure just do it again and it should work.
Launch the SELinuxModeChanger app on your phone, grant it root permissions, and click Permissive
Note: If you have any issues with SELinuxModeChanger then head over to the XDA thread.
2) ViPER4Android
Download the latest version in zip format from here and extract ViPER4Android_FX_A4.x.apk to your Desktop
Launch Minimal ADB and Fastboot and type adb install %USERPROFILE%\Desktop\ViPER4Android_FX_A4.x.apk
Launch the ViPER4Android app on your phone, click Yes when prompted, click Super Audio Quality, and then click OK
Grant root access when prompted
Click OK
Reboot your phone
Note: Once your phone reboots you can start configuring ViPER4Android. I cannot really help much with that but feel free to look over the official XDA thread or their Settings Explained page on the official website.
Engineering Mode
Note: If I were you I would not change anything unless you absolutely know what you are doing!
I cannot seem to get the phone codes to work. You can install the MTK Engineering Mode app from the Google Play Store.
WARNING: *I* cannot be held responsible for anything *you* do to *your* phone!
Frequently Asked Questions
WARNING: *I* cannot be held responsible for anything *you* do to *your* phone!
MTK Droid Tool
MTK SP Flash Tool
Latest Version: 5.1548.00.000
WARNING: *I* cannot be held responsible for anything *you* do to *your* phone!
WARNING: *I* cannot be held responsible for anything *you* do to *your* phone!
Q: How can I tell if my model is the BLU Life One X 2016?
A: Go here and see if it is the same model.
Q: When I try to use adb root I get the following error: adbd cannot run as root in production builds
A: You can purchase and install [root] adbd Insecure by Chainfire. Once installed, launch the app, grant it root access, and then check Enable insecure adbd and Enable at boot
Q: How do I (re)mount /system as read-write?
A: Install [root] adbd Insecure as mentioned above, open a Command Prompt, type adb root, and then adb remount rw
Q: How can I disable the audio that plays when starting up or shutting down my phone?
A: Using a file explorer with root access, or an adb shell, delete or rename (with .bak at the end) /system/media/bootaudio.mp3 and /system/media/shutaudio.mp3 and then reboot your phone.
WARNING: *I* cannot be held responsible for anything *you* do to *your* phone!
Reserved #4
Have you tried porting the Elephone rom for the Blu? They both have a MT6753, so from what I understand from reading on XDA it might work. You might need to make changes suggested at http://forum.xda-developers.com/showthread.php?t=2701283.
Has anyone been brave enough to try this yet?
---------- Post added at 02:16 AM ---------- Previous post was at 02:12 AM ----------
I'm receiving my phone tomorrow so i might be the guinea pig...lol
Did this last night on my phone. Most difficult part for myself was finding the correct drivers as this is my first mediatek device. Ended up being my fifth attempt that had the correct set.
After I had the drivers it was extremely similar to a nexus process.
Do you have a link to the drivers
Sent from my 6045X using Tapatalk
I must inform you that I am still running good ol' Windows 7 so there's that.
All credit on my end comes from [Tutorial] Flash/Root/update elephone P8000 by vetkak and the first step with the link. Its not a real link, but a copy and past of the mega.co link had the proper drivers.
If you're on Windows 10 there is a separate thread out there somewhere with instructions for that.
OK thanks
Sent from my 6045X using Tapatalk
I feel like it needs mention that after flashing the recovery (I used the TWRP flavor) that after the fastboot command you need to immediately power off the phone, instead of rebooting, then do the volume up + power button press to get to the custom recovery.
SCrid2000 said:
Have you tried porting the Elephone rom for the Blu? They both have a MT6753, so from what I understand from reading on XDA it might work. You might need to make changes suggested at http://forum.xda-developers.com/showthread.php?t=2701283.
Click to expand...
Click to collapse
Unfortunately the guy that was bringing up the elephone p8000 has sold it and subsequently not be supporting it any longer. I'm happy enough there is custom recovery options and root. An AOSP ROM would be nice, but naturally the custom gestures would be lost.
jmcneil919 said:
Has anyone been brave enough to try this yet?
Click to expand...
Click to collapse
I did but from the original Wiko Fever thread instructions. I did this a couple of weeks before he actually posted this thread and I made my own instructions that I think are clearer and more concise than the Wiko thread; however, rogersa2k's guide is pretty thorough and easy to understand besides the following correction....
The fastboot reboot after flashing the custom recovery doesn't yield the same results, because when I did that it did NOT work! I corrected it by help from a comment by member yrude (and as hottcakes mentions above) and made my own instructions with the addition of adding the installation for Viper4Android. But I hesitate to post it on XDA as I don't want to step on any toes. However, I did post it on Google+, Amazon and GSMarena. If people want this alternate guide and notify me to post it, then I will. Otherwise, I'll keep it off XDA.
hottcakes said:
I must inform you that I am still running good ol' Windows 7 so there's that.
All credit on my end comes from [Tutorial] Flash/Root/update elephone P8000 by vetkak and the first step with the link. Its not a real link, but a copy and past of the mega.co link had the proper drivers.
If you're on Windows 10 there is a separate thread out there somewhere with instructions for that.
Click to expand...
Click to collapse
I was trying to using the link to download the driver, but the mega site asked for "decryption key" before I can download. Is there a key available to share? Thanks,
Tha Watcher said:
I did but from the original Wiko Fever thread instructions. I did this a couple of weeks before he actually posted this thread and I made my own instructions that I think are clearer and more concise than the Wiko thread; however, rogersa2k's guide is pretty thorough and easy to understand besides the following correction....
The fastboot reboot after flashing the custom recovery doesn't yield the same results, because when I did that it did NOT work! I corrected it by help from a comment by member yrude (and as hottcakes mentions above) and made my own instructions with the addition of adding the installation for Viper4Android. But I hesitate to post it on XDA as I don't want to step on any toes. However, I did post it on Google+, Amazon and GSMarena. If people want this alternate guide and notify me to post it, then I will. Otherwise, I'll keep it off XDA.
Click to expand...
Click to collapse
Pls post yours here. I saw your Amazon comment and tried to follow it. Everything seemed to work till I run "fastboot oem unlock" then the PC just displays "Waiting for device response...." and my BLOX never showed any response on screen. I suspected that I did not have the driver for this particular type cellphone device. Thanks,
clu1688 said:
Pls post yours here. I saw your Amazon comment and tried to follow it. Everything seemed to work till I run "fastboot oem unlock" then the PC just displays "Waiting for device response...." and my BLOX never showed any response on screen. I suspected that I did not have the driver for this particular type cellphone device. Thanks,
Click to expand...
Click to collapse
I appreciate that but the only way I'd post it in this thread is if the OP says it's fine. I do not like hijacking or taking over other people's threads.
It sounds like ADB is actually not loaded or working on your computer or otherwise you wouldn't get that message. I could be wrong, though. To test to see if it is indeed working and drivers are properly loaded, what does it respond when you type: adb devices
SCrid2000 said:
Have you tried porting the Elephone rom for the Blu?...
Click to expand...
Click to collapse
Not yet, but I do plan to try to start with that. It's nice that Elephone released the source code for the P8000 so that could help as well. If I ever get to this I will need lots of help.
jmcneil919 said:
Has anyone been brave enough to try this yet?
Click to expand...
Click to collapse
Everything that *I* post in the OP will be something that I tested on my own device first unless I specifically mention otherwise.
hottcakes said:
I feel like it needs mention that after flashing the recovery (I used the TWRP flavor) that after the fastboot command you need to immediately power off the phone, instead of rebooting, then do the volume up + power button press to get to the custom recovery.
Click to expand...
Click to collapse
I will add a note about that but some of us had issues so I chose the alternate method that has worked for me the first time every time.