Develop Bugs

[TUTORIAL] How to S-OFF your HTC Desire

Hi there !
Many people here want to be S-OFF on their HTC Desire but don't know how to be, this thread is for you !
Credits goes to all AlphaRev developpers.
What is S-OFF ?
(Quotes from original AlphaRev website)
HTC implemented security on their newer generation phones. This flag, called @secuflag, controls whether your phone has
it's NAND or flash unlocked. Most noticeably, S-ON (security on) will read-lock your /system and /recovery partition, to name a few. Also, secuflag controls whether zip files being flashed through recovery or fastboot, are signed by HTC.
The now notorious S-OFF (security off) will disable this NAND security.
Since we are unable to access the Radio NVRAM itself (where secuflag is stored), we turned our attention to HBOOT.
Click to expand...
Click to collapse
For more informations about AlphaRev S-OFF, read the OFFICIAL Thread HERE.
There is many solutions to install S-OFF, this tutorial will show you few methods.
TRY AT YOUR OWN RISK ! I'am not responsible of bricked phone, for more help try the OFFICIAL Thread.
PREREQUISITES :
a ROOTed HTC Desire ROM with debugging option enabled on it.
a computer running Windows XP/Vista/Seven (32 or 64 bits), Linux, or Emulation via WMware etc.
a computer which can boot USB devices (for USB method only)
a branded USB Key 32Mb or more (for USB method) or a CD to burn (for CD method).
EASIEST method so far seems to be now by "Revolutionary" method.
Please check this out before trying solutions below (they are manual and maybe outdated, because I don't have the time keep updated this topic, moreover I don't own anymore a HTC Desire).
STEP-BY-STEP GUIDES :
.: USB METHOD :.
Be sure to Nandroid backup your device from recovery (just in case).
Download the latest Universal USB Installer or UnetBootin.
Download ISO Reflash Utility from AlphaRev website.
Install the software of your choice.
Open it, and select your USB device and your AlphaRev ISO freshly downloaded.
Create your bootable USB key.
Reboot your computer and boot on the USB key you freshly created.
Press any key to accept the disclamer.
Once you are in your ROM, plug your Desire with the USB cable on your computer.
/!\ DON'T TOUCH ANYTHING TILL YOU GET THE FINISH MESSAGE AT STEP 3 /!\
(Some users reports it can take over 1 hour. Passed this time, pull out the battery and reboot your phone).
The USB key method worked 100% for me, I personally installed my S-OFF exactly like that on my Desire.
.: CD METHOD :. (by jshields)
Clic HERE
.: VirtualBox METHOD :. (by Stewge)
Clic HERE
.: VMWare METHOD :. (by -V-O-Y-A-G-E-R-)
Clic HERE
Congratulations ! you are done !
Note : If for some unknown reasons you cannot access your Recovery anymore, it's normal, you must flash your Recovery using "fastboot" (SDK Android Kit must be installed on your running computer).
You have the choice between flashing a custom recovery like ClockWork one or put the original one but I sugger you the custom one which gives you much many more features
How to flash your recovery using ClockWork's image :
Download Clockworkmod 2.5.0.7 recovery image from official AlphaRev thread for bravo.
Move the file into "C:\android-sdk-windows\tools" (default sdk android folder's installation).
Verify MD5 checksum of the image with a freeware like HashCalc or something (IMPORTANT !).
Go to the main menu of your AlphaRev HBOOT (turn on your device with return button pressed).
Go to "FASTBOOT" mode.
Go to your computer and open a new terminal (Administrator privileges required if Windows Vista or 7).
Enter exactly this (without ") : "fastboot flash recovery recovery-clockwork-2.5.0.7-bravo.img".
Now you will have a ClockWork Recovery image installed and working
Note 2 : If your device freeze on boot logo, apply your Nandroid backup that your did before S-OFF.. that should do the trick.
If one day you want to S-ON your phone again, just reflash an original RUU rom !
Need supports ? all kind of questions must be posted on this thread directly. Be sure to read the whole thread (or at least 5 latest pages) before asking any question.
If you enjoy this guide, don't forget to rate it
{
"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"
}
stars, and clicking the
button (right below) is always appreciated to keep this thread maintained
LIKE MY WORK ?
OFFER ME A
!​​

Thank you so much, been waiting for this, will try it out later

nice tut but you can avoid installing anything, You can just use UnetBootin

Or CD version
1.download Alpha Rev.iso
2.burn .iso image to CD using a iso burning software eg. Power ISO
3.boot from CD eg. Hold F12 at boot
4.press the Legendary enter
TIPS connect USB when the CD has booted
Any problems just pm me
Sent from my HTC Desire s-off

Beaverman20 said:
nice tut but you can avoid installing anything, You can just use UnetBootin
Click to expand...
Click to collapse
It's nearly the same, you don't have to install universal usb installer, however, it is Windows-only.
Sent from my HTC Desire using XDA App

Really good work... a simple and clear guide

jshields said:
Or CD version
1.download Alpha Rev.iso
2.burn .iso image to CD using a iso burning software eg. Power ISO
3.boot from CD eg. Hold F12 at boot
4.press the Legendary enter
TIPS connect USB when the CD has booted
Any problems just pm me
Sent from my HTC Desire s-off
Click to expand...
Click to collapse
Yeah, I found it much easier to just burn to a rewrittable CD. F8 on bootup to load up my boot menu, then I selected my CD Rom.

nice tut, simple and very clearly...
oh don't forget to put in the first post for ppl who gets stuck at stage 3 (it happen to me) just to wait for about 30 minutes or more (don't know exactly how long, just for safety), and then pull out the battery and reboot the phone...
many ppl report it work....
Sent from my HTC Desire using Tapatalk

I think I'm done with the flashing of the hboot from alpharev
But now my phone keeps rebooting to the fastboot screen.
I've tried removing the battery and rebooting again, reboot from fastboot, reboot from clockwork recovery... but i still cant boot up my rom.......
Anyone can shed me a light on what went wrong?

All options to apply S-off should be included, this is a 'how to', and this is not THE only way to do it, personally I found virtual box the easiest method for me. I just think that some other options should be made clear to people, maybe people that have used a different method could add their own ' how to' to this thread?
Great idea though to help people.
sent from my HTC Desire, powered by a SuperVillain using XDA App.

Sorry to noob it up here but what are the benefits of S-OFF. im guessing it means security. does this enable us to hack the kernal? as a user who doesnt do programming but likes to mod my phone alot what could i gain out of this?
thankyou in advance

Yeah sorry for newbies here but what is the benefits of this s-off?

eozen81 said:
Yeah sorry for newbies here but what is the benefits of this s-off?
Click to expand...
Click to collapse
Maybe its a good thing to sum up the benefits on the first page, to stop these kind of questions and making it a 500 page topic where you cant find answers...
I know if you read the forum, or use google you can find all the info
Info from the http://alpharev.shadowchild.nl/ site
HTC implemented security on their newer generation phones. This flag, called @secuflag, controls whether your phone has
it's NAND or flash unlocked. Most noticeably, S-ON (security on) will read-lock your /system and /recovery partition, to name a few. Also, secuflag controls whether zip files being flashed through recovery or fastboot, are signed by HTC.
The now notorious S-OFF (security off) will disable this NAND security.

I gonna change a bit the tutorial, and add the other solutions. Will do a link directly of posters with the solution he use, will be easier for me

AndroidGX said:
I gonna change a bit the tutorial, and add the other solutions. Will do a link directly of posters with the solution he use, will be easier for me
Click to expand...
Click to collapse
allrighty then

Ok, many changes on the tutorial, hope you like it
Tried to do as clear as possible, and add some features.
If any method to add please PM me, I will add it with your name directly from your post here.
Thanks!

AndroidGX said:
Ok, many changes on the tutorial, hope you like it
Tried to do as clear as possible, and add some features.
If any method to add please PM me, I will add it with your name directly from your post here.
Thanks!
Click to expand...
Click to collapse
looks great !

I have now read all the information i can find about S-OFF - Only advantage i can find is that you can change bootscreen.. What are the options if i choose to make S-OFF on my phone - What else can i change ? My phone is rooted, and i have flashed roms and kernels with S-ON - So you guys really need to show more advantages to this than what has already been written..

Nobody is trying to sell you anything. Why don't you GTFO?

ionhide said:
I have now read all the information i can find about S-OFF - Only advantage i can find is that you can change bootscreen.. What are the options if i choose to make S-OFF on my phone - What else can i change ? My phone is rooted, and i have flashed roms and kernels with S-ON - So you guys really need to show more advantages to this than what has already been written..
Click to expand...
Click to collapse
You post in the wrong thread, go say that in the original S-OFF thread (gave in first post).
Here is just a help for people who want to install S-OFF feature on their Desire. Nothing else.

[ROM] EZbase v3.0 [25/04/2011] - odin / heimdall - Easy Full Graphical How-To

{
"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"
}
EZbase, is a fully deodexed and zipaligned pre rooted odin / heimdall image for people wanting to move from stock ROM's to custom ROM's. It used by a lot of people for a recovery image if it all goes wrong, simply flash this and you on a stock Samsung image with root and 2e recovery.
Still testing the new recovery & kernel so attached is a copy of EZbase with stock CWM Recovery, until the new recovery has been 100% tested!
Screenshots:
Main Recovery - Recovery Backup - Recovery Install - EZOdin​
Features:
Gingerbread & Froyo
Simple Recovery Menu
Added:
RomManager 3.0.xxx
TitaniumBackup 3.7.2
Notes:
Please read the EZbase How-To v2.00 - http://nfye.eu/EZbase/i9000/EZbase-2.00.pdf
Donators:
Euphoria
Thanks To:
RazvanG - 3-Button Combo Fix
Tr0jAn - Testing & Documentation Review
​

Downloads:
EZbase How-To
ROM
Gingerbread EZbase v4.0
Froyo EZbase v2.0
Other
EZOdin
Android Debug Bridge (a.k.a. adb)​

Reserved
Reserved 10 Chars

This is a Step by Step guide how to flash EZbase to your Samsung Galaxy S.​
There are lots of different ways to flash ROMs to your Samsung Galaxy S, Personally I use heimdall but thats because I use *nix. I find this one to be easiest and fastest for windows users.
If you complete this guide there the worlds your oyster, simply copy different mods/ROMs to the SD Card and flash directly from there going back to your base at any time should you need to revert back.
If you have any issues what so ever, the best place to begin is a clean EZbase flash.
NOTE: No root or anything is required, you can simply do this on a stock Samsung ROM.
Contents
What you need
Flash EZbase
Install Custom ROM
Other Information
ADB - Android Debug Bridge
Enable Debugging Mode
Mass Storage
Download Mode
Recovery Mode
3-Button Combo Fix
Warning!
There have been many reports about a problematic batch of Samsung Galaxy S phones that are not able to boot into recovery or download mode. If you are going to flash a ROM please make sure you can enter these modes before doing ANYTHING. See the 3-button combo fix if you cannot access Recovery Mode.
What you need:
EZOdin - http://nfye.eu/EZbase/i9000/EZOdin.exe
EZbase
Custom ROM (only if you wish to use a third party ROM)
- E.G. insanity - http://forum.xda-developers.com/showthread.php?t=843019
Nice to Have
Android Debug Bridge (a.k.a. adb) - http://nfye.eu/EZbase/i9000/adb.zip
Download all the EZOdin, EZbase CSC, PDA, PHONE and PIT if you do not have Samsung Kies installed, The Samsung USB Drivers will be required to. For simplicity sake place all the files into a single directory e.g. c:\toolkit\ however they can be placed where you like, hopefully in the future I might get all the requirements into an installer.
If you do not have Samsung Kies installed please install the Samsung USB Drivers and make sure your device is recognised by the OS. Once all the pre requisites have been fulfilled, then please continue to Step One or Step Two. If Samsung Kies is used please make sure you kill all Samsung Kies related services that are running (kies, tray agent, etc.)
Check that your phone has sufficient power, unplug your phone if it is plugged into USB or wall charger. Type *#0228# in to the dialler and check Voltage is at least 3800(mV).
Flash EZbase
Repartition is not mandatory, but it does not hurt to repartition the phone.
Start Phone in Download Mode (No Cable Attached)
Open EZOdin.
- Check Re-Partition
- Select EZbase.pit as PIT
- Select EZbase-PDA-XWJS3.tar.md5 as PDA
- Select EZbase-PHONE-XXJVE.tar.md5 as PHONE
- Select EZbase-CSC-XXJV1.tar.md5 as CSC
Connect Phone with USB Cable - Once ID:COM is yellow you are safe to continue.
Select Start
Complete, now wait for your phone to fully start-up before you continue with anything.
Install Custom ROM
Copy the ROM onto the Internal SD Card. This can be done via adb or placing your phone in USB debug mode and mounting the USB as storage.
Reboot the phone in recovery mode
Select "Install ZIP File"
Select "choose zip from sdcard"
Select "insanity-0.x.x.zip"
Select "Yes - Install"
Wait a while it installs the new ROM.
Select "Reboot Phone"
NOTE: As this is a de-odex`d ROM, First boot will take some time.
Other Information
ADB - Android Debug Bridge
To use the Android Debug Bridge you need to enable Debugging Mode first. Once enabled you will be able to use ADB and do a number of things.
Enable Debugging Mode
Press "Menu"
Select "Settings"
Select "Applications"
Select "Development"
Check "USB debugging"
Select "Yes"
Connect the phone to the USB cable and plug the other end directly into the PC.
NOTE: The computer should start installing the necessary ADB drivers. A total of three devices will be installed (Samsung Android Composite ADB Interface, Samsung Android USB Modem, Samsung USB Composite Device.
You should also now see two icons in the notification area.
Mass Storage
It is possible to mount the internal SD and microSD card as storage on your local pc, this is useful if you do not wish to use adb to copy files around.
If you wish to use your device as Mass Storage:
Pull down the notification area
Select "USB connected"
Select "Connect USB storage"
You should now be able to see your device in explorer
You should always safely eject the storage
Select "Turn Off"
Download Mode
To enter download mode, you hold the Volume Down + Home + Power. See image bellow:
Recovery Mode
To enter download mode, you hold the Volume Up + Home + Power See image bellow:
3-Button Combo Fix
You will need the following:
adb
root
xvi32 - http://nfye.eu/EZbase/i9000/xvi32.exe
P-SBL.tar.md5 - http://nfye.eu/EZbase/i9000/P-SBL.tar.md5
How To Check is Phone is Compatible:
adb shell
$ su (a superuser request will be displayed on the phone screen, accept it).
# dd if=/dev/block/bml1 of=/sdcard/bml1.dump
# exit
C:\adb pull /sdcard/bml1.dump
Open the bml1.dump file with XVI32.
- Search (in ASCII Mode) for OFNI.
If the block reads "[email protected]" just follow the tutorial below, as it is safe to fix.
NOTE: If it reads "x0" then STOP as this FiX will BRICK your phone if applied.
Open EZOdin
- Select the "P-SBL.tar.md5" as PDA file.
- Check "Bootloader Update"
Connect Phone with USB Cable and place phone in download mode (ADB method)
Once "ID:COM" is yellow you are safe to continue.
Select "Start"
NOTE: It should take three seconds to complete. After the update phone will reboot automatically. Do this at your own risk!

Reserved
Reserved Number 2

I was looking for this. Thanks. Will try insanity after this.
Darky's 9.3|Voodoo 5.4.1|ZSJPE|Lagfix OFF

Thanks again nitr8, I will use this on your next update of Insanity rom...
Nice

Great stuff - used EZBase earlier before flashing Insanity 0.6.6.
Like rixsta will use this method before future Rom flashes
Sent from my GT-I9000 using XDA Premium App

Thank you nitr8 =]

As always if you need any help man give me a call

Is this EZOdin safe/tested?
How is it different than the original (besides the UI, ofc)?

RayearthX said:
Is this EZOdin safe/tested?
How is it different than the original (besides the UI, ofc)?
Click to expand...
Click to collapse
Do you think I would release this untested? Yes its been tested, its STOCK Odin, with a revamped UI.

nitr8 said:
Do you think I would release this untested? Yes its been tested, its STOCK Odin, with a revamped UI.
Click to expand...
Click to collapse
YES! You could release it just for testing purposes
Just wanted to be sure.

RayearthX said:
YES! You could release it just for testing purposes
Just wanted to be sure.
Click to expand...
Click to collapse
it is check out post2

Nice you're pulling this up now!
I wondered, why you didn't release this.
Cheers,
Joël
Sent from my GT-I9000 using XDA Premium App

Darkyy said:
Nice you're pulling this up now!
I wondered, why you didn't release this.
Cheers,
Joël
Click to expand...
Click to collapse
It was ready a while back, we was about to do it and then a new firware came out and it got put on the back burner
My phone was on 6.6 but as it needed testing I redid it as per the written instructions just so we knew it worked 100%
IF people follow the guide then they SHOULD get a 100% working insanity rom with no hassle.. (we live in hope )
TrOjAn

Thanks for this, it's a nice initiative. I've been doing the same, just with different files from samfirmwares + I've needed to install a kernel to get easy access to root + cwm so this lets me skip that part
One thing though, you might want to either put this in your guide, or alternatively modify the app, but that Odin you have is version 1.7.. which has given me trouble (Windows 7, 32bit) in the past. Odin 1.82 works fine so just as a tip for people who might have problems getting odin to work
Aside from that this is a great idea!

akselic said:
One thing though, you might want to either put this in your guide, or alternatively modify the app, but that Odin you have is version 1.7.. which has given me trouble (Windows 7, 32bit) in the past. Odin 1.82 works fine so just as a tip for people who might have problems getting odin to work
Aside from that this is a great idea!
Click to expand...
Click to collapse
Hmm.. strange, Im on 1.7 Windows 7 32bit and I have not seen any issues.
What sort of issues have you had??
TrOjAn

TrOjAnUK said:
Hmm.. strange, Im on 1.7 Windows 7 32bit and I have not seen any issues.
What sort of issues have you had??
TrOjAn
Click to expand...
Click to collapse
odin either not connecting or just standing there doing nothing, never found out why but after using 1.82 its worked fine so I never felt like going back
and your files work with the standard odin anyway so it's not a big deal

akselic said:
odin either not connecting or just standing there doing nothing, never found out why but after using 1.82 its worked fine so I never felt like going back
and your files work with the standard odin anyway so it's not a big deal
Click to expand...
Click to collapse
Yes I have has similar like that happen as it goes, re installing the drivers normally fixed it
Anyway, glad you like it.. hopefully more will find the benifits of EZBase
TrOjAn

[Guide] -The Ultimate Stock to Custom ROM Awesomeness thread - Noob friendly

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!

Reverting back to Fire OS from CM11

Hello All!
I decided to install CM 11 a few days ago and then thought I'd like to go back to Fire OS. I followed the instructions as much as I could from the thread on here to revert back but I have ran into a problem. I could only get 4.6.1 installed but obviously, 4.6.3 is out and my phone can see it's there to download (and it does (try to) download - every time I restart my phone). When the download finishes the phone says there is an error and it can't update but then I can search for the update and so on. I have tried doing it the way Amazon suggest from my PC but to no avail.
I can only assume that this has something to do with the fact I went from 4.6.3 to CM 11 and then back to 4.6.1 and the phones still sees itself has partially being on 4.6.3?
Any help is much appreciated!
Thanks

doing it the way Amazon suggest from my PC but to no avail
Click to expand...
Click to collapse
That means you downloaded the 4.6.3 BIN image and tried sideloading it via ADB?
If not, take a look at this (scroll down to the paragraph "Recovery / Sideload Factory Images")
I think OTA update is useless at this point but using the Amazon stock recovery is very reliable, I used it many times in the beginning for testing purposes.
Just give us some details when you encounter problems, e.g. driver missing when connected to PC, etc. ... and don't forget your backup for important apps & app settings.

I tried doing this before and the CMD does not show as any devices being connected. I have it in debugging mode and plugged it in but Windows did not see it even though the phone shows as being connected. Also, just in case I tried using the command you send and it just says "* cannot read 'update.bin' *".

You have the phone connected while booted up in Fire OS OR booted up in recovery mode like the guide suggests?
Sounds like you're missing ADB drivers / Windows failed to change the drivers when phone is connected in ADB recovery mode. Indicators:
• Windows did not "see" the phone
• The command line in CMD doesn't work without proper ADB configuration
If you boot up your phone in recovery mode / ADB mode, you will need additional ADB device drivers for your Windows system.
The regular (Amazon / Kindle) USB driver that is used when you connect your phone to the PC won't work, it's simply not the same method.
That's why your phone "disappears" as soon as you (re)boot into recovery / ADB sideload mode.
Open your "device manager" (assuming, you're using Windows as your main OS) and check for your device with missing drivers.
{
"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"
}
Try this tool (& driver) ADB, Fastboot and Drivers
Maybe you need to manually check for the "new" device and update the drivers:
Open the device manager while your phone is connected in recovery mode.
Look for its entry in the device list.
Remove it (Deinstall it).
Then "scan for hardware changes":
The device should appear in list the again, it will install the needed driver automatically (best case scenario)
or
you will have to update the device drivers manually:
You can even use (old) "Google USB drivers", I successfully tested google drivers from 2010 on Win 7 x64 with this phone in ADB mode.
If everything worked as planned, it should look like this: next to your device name, it will say "sideload":

It seems that on Windows 10 it works/looks different. I updated the driver that was suggested but I had another one which also needed updating which I have just done and appears to now let the cmd see the device properly and also allowing me to sideload.
Device manager does not see it as an Android device but as a Samsung device. Not sure why this is unless the device drivers used were Samsung ones but I guess that is irrelevant now. I will post my results once the update has finished.
Also, thanks for the help with this. Your information did help and with a bit of tweaking, it appears to have worked.

Thanks for mentioning so early that you use Windows 10, that makes it so much easier for me. :laugh:
Nah, but it looks like you will be good from here on out...
Btw. by sideloading the image, it will erase "everything" on your device, so you get clean system without leftovers, just like you hoped for.

Can you add the link for the thread you used to revert back from CM11 to FireOS?

paulalva05 said:
Can you add the link for the thread you used to revert back from CM11 to FireOS?
Click to expand...
Click to collapse
The link is actually in the first reply but I have put it below anyway!
http://forum.xda-developers.com/showpost.php?p=61271723&postcount=2

Bingo Bronson said:
You have the phone connected while booted up in Fire OS OR booted up in recovery mode like the guide suggests?
Sounds like you're missing ADB drivers / Windows failed to change the drivers when phone is connected in ADB recovery mode. Indicators:
• Windows did not "see" the phone
• The command line in CMD doesn't work without proper ADB configuration
If you boot up your phone in recovery mode / ADB mode, you will need additional ADB device drivers for your Windows system.
The regular (Amazon / Kindle) USB driver that is used when you connect your phone to the PC won't work, it's simply not the same method.
That's why your phone "disappears" as soon as you (re)boot into recovery / ADB sideload mode.
Open your "device manager" (assuming, you're using Windows as your main OS) and check for your device with missing drivers.
Try this tool (& driver) ADB, Fastboot and Drivers
Maybe you need to manually check for the "new" device and update the drivers:
Open the device manager while your phone is connected in recovery mode.
Look for its entry in the device list.
Remove it (Deinstall it).
Then "scan for hardware changes":
The device should appear in list the again, it will install the needed driver automatically (best case scenario)
or
you will have to update the device drivers manually:
You can even use (old) "Google USB drivers", I successfully tested google drivers from 2010 on Win 7 x64 with this phone in ADB mode.
If everything worked as planned, it should look like this: next to your device name, it will say "sideload":
Click to expand...
Click to collapse
Hi, thank you for the detailed instruction. My pc can recognize and show the name of my firephone, just like what you showed in the image. But when I type "adb sideload update.bin", it still says "cannot read update.bin" What can I do now? Thank you so much.

iHuyou said:
But when I type "adb sideload update.bin", it still says "cannot read update.bin" What can I do now? Thank you so much.
Click to expand...
Click to collapse
Validate the MD5 checksum, maybe your downloaded image is corrupted...

Is the update.bin file in a different directory?

Bingo Bronson said:
Validate the MD5 checksum maybe your downloaded image is corrupted...
Click to expand...
Click to collapse
Hi, Bingo Bronson, thank you for your reply. What I downloaded from the link in your original post is a WinRAR ZIP archive. When I open it, there are multiple file and folders in there. There is a file called boot.img, should I change its name to update.bin and sideload it? But it is only 8Mb. Can you give a little more detailed instruction? Thanks

iHuyou said:
[...] is a WinRAR ZIP archive. But it is only 8Mb. Can you give a little more detailed instruction? Thanks
Click to expand...
Click to collapse
Whoops, I think you took a wrong turn there somewhere, too many files, what to choose...!?!
edit: Slight misunderstanding, luckily iHuyou found the solution by himself. :victory:
This is the direct download link from Amazon for the latest GSM unlocked version: http://fire-phone-updates.s3.amazon...update-fire-phone-35.4.6.3_user_463001620.bin
An here is the direct download link from Amazon for the latest AT&T version: http://fire-phone-updates.s3.amazon...HC5/update-kindle-32.4.6.5_user_465000520.bin
I don't know which version you had installed, so just pick the link according to your initial Fire OS version. Reply again if you have further questions. :good:

Bingo Bronson said:
Whoops, I think you took a wrong turn there somewhere, too many files, what to choose...!?!
I don't know which version you had installed, so just pick the link according to your initial Fire OS version. Reply again if you have further questions. :good:
Click to expand...
Click to collapse
Thanks again, Bingo Bronson. I figured it out. The bin file has to be in the same directory as the adb file, otherwise adb cannot find the bin file therefore cannot read it. I have successfully sideloaded 4.6.5 following your post. Thank you!

Blank Screen amazon fire phone
Hello Guys i need help with my amazon fire phone, I tried to revert back from cm11 to stock rom (http://www.android.gs/downgrade-amazon-fire-phone-to-stock-fire-os-3-5/) using this site's method i got error sideloading from stock recovery then i tried it from safe strap recovery and it went successful but before sideloading update.bin from safestrap recovey i wiped and i did not know what options i selected but now my fone wont boot only black screen and when i connect it to pc it shows 3,4 partitions and says format, format... what went wrong ?

Workarounds for low internal memory

I bought the XZ1C from USA to India as it is not available at all in Indian markets (and never will be - because no compact devices were launched in India). I love this device except for one thing. Low internal memory - and I bet others might also be annoyed by this. There's two workarounds that I could immediately think of but can't be implemented with this Device.
1. Adoptable storage : Adopt external SD card as internal storage - this is one of the coolest features Oreo has to offer, but can't be used in this device. I went through a lot of blog posts and followed the steps, also read about the adoptable storage leading to no solution. I have a Samsung 128GB EVO SD card and I tried to adopt it as an internal storage in more than one ways with no success.
2. Move apps to SD : I thought I could move at least some apps if not all to external SD but this feature that was introduced in Android 2.2 (I remember using it on my Samsung Galaxy Apollo i5801) and re-introduced in 5.0. But this is also not working. I also tried enabling 'Force allow apps on external' under developer options which didn't work.
As I don't have this phone officially supported in my country, I want to check if someone can contact Sony support in their country (US, UK, Germany) to help fix this through an update maybe?
Another purpose of this thread is to discuss alternate workarounds if anyone has tried any and worked for them.

Unfortunately you're out of luck. I don't think any Xperias to date has ever supported adoptable storage.
As for moving apps to SD, it was never an option for this phone. I don't know if this was a decision with Sony's Oreo implementation across all models, or just certain models, or what, but you can't do that.
You'd probably have to look at root options, but beware, unlocking the bootloader to root comes with consequences and compromises.

mhaha said:
Unfortunately you're out of luck. I don't think any Xperias to date has ever supported adoptable storage.
As for moving apps to SD, it was never an option for this phone. I don't know if this was a decision with Sony's Oreo implementation across all models, or just certain models, or what, but you can't do that.
You'd probably have to look at root options, but beware, unlocking the bootloader to root comes with consequences and compromises.
Click to expand...
Click to collapse
I agree with you. I am going to wait for a while and see if Sony pushes an update that provides move apps to SD option (which I highly doubt they will). But if there comes a point where I desperately need space, I will root the phone. Out of 6 phones that I've used in past 6 years, this is the first one I haven't rooted and ain't planning to.

Possible Solution
I've looked at a thread from the sony forums. Some people were able to get the microSD card to work by factory resetting the phone with the SD card inside. Hope this helps.
What I've done now is to factory reset the phone with the sd card inserted and boot and setup the phone with the sd card in place this time. Then format it again thru the phone (I have not activated sd card encryption yet) and all of a sudden spotify, netflix, ... work with the sd card just as expected.
So perhaps one of you, who experience the same thing, might want try out if this is reproduceable.
Keep the sd card in the phone
Factory reset (I did it via the Xperia companion desktop software)
Boot it up again
Format SD Card
Click to expand...
Click to collapse

Antilogy said:
I've looked at a thread from the sony forums. Some people were able to get the microSD card to work by factory resetting the phone with the SD card inside. Hope this helps.
Click to expand...
Click to collapse
Don't understand what u guys are talking about.
Either use SD card as internal memory (I know for sure that is disabled by Sony, for good reasons..) or simply make Netflix, Spotify etc use sd card to keep music / movies... Because If it's the second case, I can do that without any problem, just inserted my Samsung Evo 128 gb use it on the go, no pb,no particular steps...

Dany XP said:
Don't understand what u guys are talking about.
Either use SD card as internal memory (I know for sure that is disable by Sony, for good reasons..) or simply make Netflix, Spotify etc use sd card to keep music / movies... Because If it's the second case, I can do that without any problem, just inserted my Samsung Evo 128 gb use it on the go, no pb,no particular steps...
Click to expand...
Click to collapse
That means the TC should be able to do that.

Antilogy said:
That means the TC should be able to do that.
Click to expand...
Click to collapse
What r u referring to?
( and "tc" =?... This ain't Twitter u know.. U can write as long as u can ?)

Dany XP said:
Don't understand what u guys are talking about.
Either use SD card as internal memory (I know for sure that is disabled by Sony, for good reasons..) or simply make Netflix, Spotify etc use sd card to keep music / movies... Because If it's the second case, I can do that without any problem, just inserted my Samsung Evo 128 gb use it on the go, no pb,no particular steps...
Click to expand...
Click to collapse
Dany XP said:
What r u referring to?
( and "tc" =?... This ain't Twitter u know.. U can write as long as u can )
Click to expand...
Click to collapse
Sorry. I meant to say topic creator. In this case that would be @kaustubhg123.

You can actually use a little neat trick:
Unlock your bootloader
Install XperiFix ( https://www.xperifix.com ) - XDA Thread to restore camera and X-R,BionZ functions (thanks a lot Sony, for nothing)
Xperifix auto install Magisk 16
Use [Magisk Module] Magic Folder Binder (fbind) module to "join" your internal folders with SDCARD and bind folders like Downloads, DCIM, .android
For example if you download a file, even if the phone downloads it to the internal memory it will be actually on the SDCARD. fbind also moves the old data to sdcard when you configure fbind.

mhaha said:
Unfortunately you're out of luck. I don't think any Xperias to date has ever supported adoptable storage.
As for moving apps to SD, it was never an option for this phone. I don't know if this was a decision with Sony's Oreo implementation across all models, or just certain models, or what, but you can't do that.
You'd probably have to look at root options, but beware, unlocking the bootloader to root comes with consequences and compromises.
Click to expand...
Click to collapse
I'm still very very green to android and to using Xperia Android phones ... what consequences and compromises are to be faced wtih rooting bootloader? From looking at former threads from over 4yrs ago it seemed that rooting was THE holy grail and raison de T'etre for having an Android (reason for being/having).

Supa_Fly said:
I'm still very very green to android and to using Xperia Android phones ... what consequences and compromises are to be faced wtih rooting bootloader? From looking at former threads from over 4yrs ago it seemed that rooting was THE holy grail and raison de T'etre for having an Android (reason for being/having).
Click to expand...
Click to collapse
Sony have given developers and java enthusiasts the finger with this latest bootloader. There isn't a way to save the encrypted keys (unique to your phone) before unlocking it. So you can unlock it to do development, but it's a one way step, which breaks the camera and a few other functions.
In the past my two main reasons for rooting were to theme the phone a different colour and to save battery. Theming can be done without root now and my battery lasts three days anyway.
Having said that, I have just flashed sToRm//'s TWRP + KERNEL + ROOT + DRM fix/restore (because there’s a rooting enthusiast inside every android owner) and everything is working perfectly. The camera is working and all the software functions correctly.
But rooting the phone to get you control over moving apps to the SD card is a bit extreme and a lot of work for a very minor inconvenience. What are you doing with a small compact phone if you want to use two or three hundred apps?

Dany XP said:
Don't understand what u guys are talking about.
Either use SD card as internal memory (I know for sure that is disabled by Sony, for good reasons..) or simply make Netflix, Spotify etc use sd card to keep music / movies... Because If it's the second case, I can do that without any problem, just inserted my Samsung Evo 128 gb use it on the go, no pb,no particular steps...
Click to expand...
Click to collapse
What good reasons?
I have enabled all apps to save their things on SD card (The camera app stores all photos on SD by default but the stupid Album app stores its thumbnails data on internal memory for no reason). My main big issue is with WhatsApp which stores its data on internal memory and provides no option to store it on SD card. WhatsApp is almost 11GB on my phone now.

mhaha said:
As for moving apps to SD, it was never an option for this phone. I don't know if this was a decision with Sony's Oreo implementation across all models, or just certain models, or what, but you can't do that..
Click to expand...
Click to collapse
The Xperia V & Z1c both allowed apps to store their data on SD (Spotify, Audible, etc.) but can't do it on this phone :/ Apparently, Oreo blocks us from using our SD card in this way.

luminoso said:
You can actually use a little neat trick:
Unlock your bootloader
Install XperiFix ( https://www.xperifix.com ) - XDA Thread to restore camera and X-R,BionZ functions (thanks a lot Sony, for nothing)
Xperifix auto install Magisk 16
Use [Magisk Module] Magic Folder Binder (fbind) module to "join" your internal folders with SDCARD and bind folders like Downloads, DCIM, .android
For example if you download a file, even if the phone downloads it to the internal memory it will be actually on the SDCARD. fbind also moves the old data to sdcard when you configure fbind.
Click to expand...
Click to collapse
so, luminoso, in that case, can i transfer apps from phone to sd card?
because you are talking about bind the download folder, but having 10gb on my whatsaap i was really interested in move this ffrom phone storage to sd card

reckfield said:
so, luminoso, in that case, can i transfer apps from phone to sd card?
because you are talking about bind the download folder, but having 10gb on my whatsaap i was really interested in move this ffrom phone storage to sd card
Click to expand...
Click to collapse
You can bind whatsapp folder in that case

luminoso said:
You can bind whatsapp folder in that case
Click to expand...
Click to collapse
I decided to go ahead with xperifix, i have g441 compact xz1 european version, last firmware a.12a.179. i tried several times , but its not working with xperifix 2.5 last version
i attached some logs
error: device unauthorized.
This adb server's $ADB_VENDOR_KEYS is not set
Try 'adb kill-server' if that seems wrong.
Otherwise check for a confirmation dialog on your device.
06-6-2018_18-14-51 ===> List /system
Luminoso, do you have any idea¨?

reckfield said:
I decided to go ahead with xperifix, i have g441 compact xz1 european version, last firmware a.12a.179. i tried several times , but its not working with xperifix 2.5 last version
i attached some logs
error: device unauthorized.
This adb server's $ADB_VENDOR_KEYS is not set
Try 'adb kill-server' if that seems wrong.
Otherwise check for a confirmation dialog on your device.
06-6-2018_18-14-51 ===> List /system
Luminoso, do you have any idea¨?
Click to expand...
Click to collapse
Patching of your twrp recovey is needed.
I had to patch it with the last recovery (26. May) https://forum.xda-developers.com/xp...t/recovery-twrp-3-1-1-stock-security-t3706704
if you do it your twrp is not safe !
At first download Android kitchen, extract it.
Copy your twrp file into the folder and open unpackimgbat
After finish you have a folder called "ramdisk", open it.
Inside you open the file "prop.default" with your texteditor.
find the following two parameter and set them to 0:
ro.secure=1
ro.adb.secure=1
save the file, go one folder up and click on repackimg.bat.
You have a "new-recovery.img" file.
Boot your device into fastboot:
fastboot flash recovery <path of your new recovery.img>
The solution works, but device security is in danger.
You can use it, or wait for a new twrp.

Raz0Rfail said:
Patching of your twrp recovey is needed.
I had to patch it with the last recovery (26. May) https://forum.xda-developers.com/xp...t/recovery-twrp-3-1-1-stock-security-t3706704
if you do it your twrp is not safe !
At first download Android kitchen, extract it.
Copy your twrp file into the folder and open unpackimgbat
After finish you have a folder called "ramdisk", open it.
Inside you open the file "prop.default" with your texteditor.
find the following two parameter and set them to 0:
ro.secure=1
ro.adb.secure=1
save the file, go one folder up and click on repackimg.bat.
You have a "new-recovery.img" file.
Boot your device into fastboot:
fastboot flash recovery <path of your new recovery.img>
The solution works, but device security is in danger.
You can use it, or wait for a new twrp.
Click to expand...
Click to collapse
Thanks raz0rfail, it seems that has a solution in this.
three considerations allow me to ask you.
1. firstly, im encouraged to follow your instructions, but im entering a completely new field, Idont know whats android kitchen , how to copy "my twrp file into the folder", and after carrying out this instructions, should I open again xperifix, and launch the rooting process? if so, There is any risk xperfix overwrite the "previous patched" twrp as you told me in the last post?
2. when will the new twrp launch? because the last update on twrp's website was december 2017
3. Storm's xperifix 3.0 it is worth it to wait its release? because maybe waiting one month more, probably my twrp problem could be solved?
I'm confused, but thank you for you reply, at least you give me a little of chance of fix this problem

reckfield said:
Thanks raz0rfail, it seems that has a solution in this.
three considerations allow me to ask you.
1. firstly, im encouraged to follow your instructions, but im entering a completely new field, Idont know whats android kitchen , how to copy "my twrp file into the folder", and after carrying out this instructions, should I open again xperifix, and launch the rooting process? if so, There is any risk xperfix overwrite the "previous patched" twrp as you told me in the last post?
Xperifix will always download the twrp image from his servers, you have to go a little around to use your twrp file, or he updates his img-file on his server.
2. when will the new twrp launch? because the last update on twrp's website was december 2017
Your device twrp has nothing to do with the generic release from twrp. Read the text below your qoute.
3. Storm's xperifix 3.0 it is worth it to wait its release? because maybe waiting one month more, probably my twrp problem could be solved?
I don't know what he will change, but if he always redownload the twrp file from his server, he has to update the img-file.
I'm confused, but thank you for you reply, at least you give me a little of chance of fix this problem
Click to expand...
Click to collapse
OK I will start from scratch with explaining:
TWRP (TeamWin Recovery Project) brought a TWRP version out called 3.2.1 or so, but released twrp version is generic for all android devices.
So some devices have special requirements for a working twrp recovery and a Device Developer patch the generic twrp version to get it working on this device.
It needs time but on many devices it's mandatory.
So i meant in the last thread entry not the generic twrp version from TWRP creator, i meant the modificated version from our device developer which creates our twrp version.
Currently he hasn't released a version which works with the last XZ1 compact firmware 47.1.A.12.205.
And if you use a different twrp which not works on your new firmware, you will get the message $ADB_VENDOR_KEYS is not set or the message adb device is unauthorized.
My tutorial shows you how to modificate your twrp version which you get from Xperifix to get it working with the new firmware.
But if you use my twrp, your device isn't secured as you used a the correct twrp recovery from our device developer.
So you can decide if you want to use the new firmware and magisk and my cam and stay a little unsecure or you wait if the device has created a working twrp for the firmware and xperifix has updated the img-file on his server.
Execution steps for patching your twrp recovery image and get cam and magisk working again on new firmware.
At first download Android Image kitchen from here:
https://forum.xda-developers.com/showthread.php?t=2073775
Download minimal adb and fastboot from here:
https://androidfilehost.com/?fid=962187416754459552
Extract both Zip-Files on a place you want.
Then you have under C:\Xperifix\DATA\TWRP an .img-File called xz1c-twrp.img if Storm didn't change the paths.
Copy this file into the folder where you extracted Android Image Kitchen.
Execute Unpackimg.bat and change parameter in the file as described. Then execute repackimg.bat.
Open cmd.exe with windows-key + r-key. Enter cmd.exe and execute it.
Open the folder where you have extracted minimal adb and fastboot and copy the filepath of it.
switch back to cmd and enter the command cd + your path and press enter.
You should now be inside your folder inside cmd.
Then open the folder where you have extracted android Image Kitchen and right click on the new-recovery.img and in contextmenu click copy path.
switch back to cmd and enter the following command:
fastboot flash recovery and right click and click on insert to insert the image path. But don't execute it!
Next step have to do with Xperiix:
Reboot your phone into fastboot and start executing XperiFix.
if You got the message in XperiFix that the recovery is flashed unplug your phone and boot it again into fastboot.
Now execute the command inside cmd.exe
click up on your keyboard to get the last command inside cmd and replace the word "flash" with "boot" and your phone start booting into correct twrp image.
Now let Xperifix work until it's finished and you should have a working cam and magisk.

Raz0Rfail said:
OK I will start from scratch with explaining:
TWRP (TeamWin Recovery Project) brought a TWRP version out called 3.2.1 or so, but released twrp version is generic for all android devices.
So some devices have special requirements for a working twrp recovery and a Device Developer patch the generic twrp version to get it working on this device.
It needs time but on many devices it's mandatory.
So i meant in the last thread entry not the generic twrp version from TWRP creator, i meant the modificated version from our device developer which creates our twrp version.
Currently he hasn't released a version which works with the last XZ1 compact firmware 47.1.A.12.205.
And if you use a different twrp which not works on your new firmware, you will get the message $ADB_VENDOR_KEYS is not set or the message adb device is unauthorized.
My tutorial shows you how to modificate your twrp version which you get from Xperifix to get it working with the new firmware.
But if you use my twrp, your device isn't secured as you used a the correct twrp recovery from our device developer.
So you can decide if you want to use the new firmware and magisk and my cam and stay a little unsecure or you wait if the device has created a working twrp for the firmware and xperifix has updated the img-file on his server.
Execution steps for patching your twrp recovery image and get cam and magisk working again on new firmware.
At first download Android Image kitchen from here:
https://forum.xda-developers.com/showthread.php?t=2073775
Download minimal adb and fastboot from here:
https://androidfilehost.com/?fid=962187416754459552
Extract both Zip-Files on a place you want.
Then you have under C:\Xperifix\DATA\TWRP an .img-File called xz1c-twrp.img if Storm didn't change the paths.
Copy this file into the folder where you extracted Android Image Kitchen.
Execute Unpackimg.bat and change parameter in the file as described. Then execute repackimg.bat.
Open cmd.exe with windows-key + r-key. Enter cmd.exe and execute it.
Open the folder where you have extracted minimal adb and fastboot and copy the filepath of it.
switch back to cmd and enter the command cd + your path and press enter.
You should now be inside your folder inside cmd.
Then open the folder where you have extracted android Image Kitchen and right click on the new-recovery.img and in contextmenu click copy path.
switch back to cmd and enter the following command:
fastboot flash recovery and right click and click on insert to insert the image path. But don't execute it!
Next step have to do with Xperiix:
Reboot your phone into fastboot and start executing XperiFix.
if You got the message in XperiFix that the recovery is flashed unplug your phone and boot it again into fastboot.
Now execute the command inside cmd.exe
click up on your keyboard to get the last command inside cmd and replace the word "flash" with "boot" and your phone start booting into correct twrp image.
Now let Xperifix work until it's finished and you should have a working cam and magisk.
Click to expand...
Click to collapse
the descriptions are absolutely precise to follow and thanks you,
in the folder data, according your description there must be this directory C:\Xperifix\DATA\TWRP an .img-File.
on my xperifix there is not such folder. attach you some images, (I also reinstall xperfix 2.5 ruling out if I lost some folders)
{
"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"
}