Database Info

[Q] Can't access root and Google apps

I recently rooted my phone (T-Mobile US Nexus S) and installed the 4.0.3 OTA update from this thread, but now I cannot access any Google apps or get root access on any of the apps that require it.

SounderBruce said:
I recently rooted my phone (T-Mobile US Nexus S) and installed the 4.0.3 OTA update from this thread, but now I cannot access any Google apps or get root access on any of the apps that require it.
Click to expand...
Click to collapse
Ok! first download : http://www.4shared.com/zip/XG506hyV/icsroot-fastboot-recovey.html
just unpack, connect your device and click run.bat.....Good luck!

I ran the .bat, but I get an error saying "Device already rooted", but it is still not recognized as rooted by SuperUser.
Alternatively, is it possible to completely wipe the phone of everything (including root) so I can start over with a fresh phone?

Of course you can, and might be the best idea if you don't mind doing it.
Make sure you have the latest CWM recovery on your phone, download the FULL ROM from this thread (i'm not american so i don't know exactly, but from what i know yours is the I9020T, so get that ROM) and copy it to the SDCard. Now go into recovery, wipe system/data and dalvik cache, then flash the ROM.
Do make sure you have the right ROM though. This will get you 100% fresh and untouched 4.0.3. You can probably clear out any non-personal folders on the sdcard too, but that shouldn't do any harm anyway.
After this, use the attached file from this thread to root, and feel free to update root/superuser.

Actually, that's what I did...I can't use CWM recovery because its displaying an error of no root. So how do I wipe this or fix CWM?

Is your boot loader unlocked? And are you trying to flash cwm through fastboot?
Note to backup your sdcard if unlocking the bootloader.

Harbb said:
Is your boot loader unlocked? And are you trying to flash cwm through fastboot?
Note to backup your sdcard if unlocking the bootloader.
Click to expand...
Click to collapse
My bootloader is apparently unlocked and I'm trying to flash through fastboot.

Are you sure the following is satisfied:
-open padlock and google logo on boot
-fastboot (on phone) says "bootloader status: unlocked" or something of the like
-you are using: "fastboot flash recovery "C:\path\to\recovery.img""
-you are using the above command while connected to the PC via USB (with working drivers) and that you are in fastboot mode on the phone (turn off phone --> hold Vol. Up then hold Power TOGETHER for about 2 seconds, should give you reboot and recovery options)
It is necessary to be in the bootloader/fastboot interface on the phone when you run the command. Hopefully it was something simple that i said above, otherwise i'm completely lost.

1. Yes
2. Yes
3. I didn't use that method to root...
4. I'll try that.

3 is just flashing recovery, that is the code u type into cmd/terminal to reflash the recovery img. It isn't rooting the phone. 4 is how to get into the mode on the phone to use the command.
Its a bit confusing at first but makes much more sense once you do it one or two times.

Where do I go to get the recovery image?

The latest ClockWorkMod Recovery can be found on this page. Just scroll down to Nexus S and download 5.0.2.0 crespo .img. Then just direct fastboot to the folder you have it saved in while using the "fastboot flash recovery C:\path\to\recovery.img" command.

Ok. I've tried this, but in command prompt, I get the following error:
C:\Users\Bruce>fastboot flash recovery C:\Users\Bruce\Downloads\recovery.img
'fastboot' is not recognized as an internal or external command,
operable program or batch file.

Check out this rooting guide, however only go up to step 5 (and do NOT type "fastboot oem unlock", do everything up until that point). This will setup fastboot for you, and setup drivers for your computer. Once this is done, do what you did above and it should work successfully.
Remember to cd (change directory) in cmd to where you unzipped that folder.

There isn't a link...

Sorry, stuffed that up. I fixed the link in my previous post pointing to NexusSHacks - How to Root Nexus S.

It's worked, but when I try to go to the recovery menu, the Google/unlocked padlock screen freezes or it displays an Android with its chest compartment open and a red triangular ! symbol.

I just had a really long reply and managed to lose it by closing the page..
That's the stock bootloader you see there, it probably didnt flash or you rebooted your phone. And make sure that you are flashing the latest CWM you downloaded before.

I flashed the latest CWM, but when I try to go to recovery, my phone freezes at the Google logo with the unlocked padlock.

Have you tried flashing it again, or maybe redownloading the file? And of course making sure it is the NEXUS S version which you are downloading.
Alternatively, try just "fastboot boot recovery.img", replacing recovery.img with the full name and path of cwm.
edit: btw, i'll be gone for an hour or two Bruce so i can answer any more questions/issues when i get back

[GUIDE] Complete Flashing Guide | Rooting | Going Back To Stock | 05.05.2013

{
"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"
}
Hello User! Before you start reading, I must warn you. First of all, flashing your first custom ROM might end up having ORD. What is ORD you can read here.
Secondly, keep in mind whatever you do, you do it at your own risk. Probability that you will brick your device is very, very small, and if you will follow proper guides, read carefully first post of the thread you are going to use ROM/kernel/recovery/other from, it is almost impossible to brick the device. No, my intention is not to encourage you. Don't even enter bootloader mode on your device if you can't/not going to read what others (probably more experienced) users got to say. Unlocking/flashing process is a very easy and short process, but it requires your attention, reading, thinking and understanding ability.
The best place to start is this thread and this video - click here​
I think you are ready now. So where should you start? You probably don't know yet. So let me briefly tell you what options you have:
You might want to root your device and keep 100% stock ROM
You might want to flash custom recovery to be able to create nandroid backups
You might want to flash custom kernel
You might want to flash custom ROM
You might want to have a custom ROM with ability to make you a coffee <--- forget about that one!
You might want to use some UI modifications like % battery
...
Whatever your option is, you need to start from unlocking your bootloader. Unlocking bootloader doesn't mean disabling all security. Your device will remain S-ON, however instead of "LOCKED" from now on it will be "UNLOCKED" or "RELOCKED" (if you decide to lock it back later). What does it mean? Basically you will be able to change content of system, recovery and boot partitions on your device. So let's unlock your device first.
Unlocking bootloader
What you need to know before unlocking the bootloader:
This operation will wipe entire content of your data partition. Read more about negative effects of unlocked bootloader - Negative effects of unlocked bootloader
This operation will not void your warranty, however opinions in this subject are divided. Read more about flashing custom ROMs and warranty - Unlocking bootloader or flashing custom ROM doesn't void your warranty!
If you are not sure if your device has virtual SD card or hardware SD card, read more here - Virtual SD card on Android
HTC One Developer Editions comes with already unlocked bootloader, so you can skip this step if you own HTC One DE.
Download this mini-sdk package and extract it to c:\mini-sdk
Visit htcdev.com site and create your account
Log in into newly created account and on the main site click "Unlock Bootloader" image <click here to see the image>
Click on "Get started" button <click here to see the image>
Expand the list of supported devieces and search for your device model name <click here to see the image>
If you can not find your device on the list, select "All Other Supported Models" <click here to see the image>
Click on "Begin Unlock Bootloader" button
On the "Are you sure you want to continue?" screen click on "Yes" button <click here to see the image>
Tick both boxes and click on "Procced to Unlock Instructions" <click here to see the image>
Follow carefully first 4 steps and click on "Proceed To Step 5" button. Ignore "Required Resources" section on the right side of the screen
Skip Step 5, 6, 7 and click on "Proceed To Step 8" button.
Open up command prompt ( Start > Run > type cmd and hit enter ). The window that appears is called Command Prompt. <click here to see the image>
Navigate to where you unzipped "mini-sdk" package (type in Command Prompt: cd c:\mini-sdk). Note: make sure the path is not c:\mini-sdk\mini-sdk
Follow very carefully steps 8 and 9. At the end click on "Submit" button.
You will receive an e-mail from HTCDev with Unlock_code.bin file attached and a link to the second part of the instructions.
Download Unlock_code.bin file from the e-mail you received and save it to c:\mini-sdk location.
In the Command Prompt type following command: fastboot flash unlocktoken Unlock_code.bin
On your device screen you will be now asked if you are sure that you want to unlock your bootloader. With volume keys navigate to proper answer and press power button to confirm. Keep in mind this procedure will wipe content of your data partition, including virtual SD card.
After it's done, your bootloader should have "UNLOCKED" text at the top.
Your bootloader is now unlocked. Whatever you want to do next, you need custom recovery for it. Every Android device has recovery partition, but with stock Android recovery you can't do much. Custom recoveries allows you to perform nandroid backup (backup content of your system, userdata and boot partitions) flash .zip packages (custom ROMs, mods, themes etc.) wipe content of your device and more. So let's flash custom recovery first. There are plenty of recoveries, including 4EXT, CWM, TWRP and more. Find the one you believe is best for you (make sure it's compiled for your device model!) and
Flashing custom recovery
What you need to know before flashing custom recovery:
After flashing custom recovery you can always revert to your stock recovery. This procedure will be described later.
Your bootloader needs to be "UNLOCKED". "LOCKED" or "RELOCKED" bootloaders can't flash custom recovery.
This operation will cause your bootloader to show "TAMPERED" text below "UNLOCKED".
For safety reasons, first what you should do is nandroid backup inside recovery. You might need it during "going back to stock" procedure.
Download custom recovery of your choice and rename it to recovery.img
Move recovery.img to c:\mini-sdk location
Connect your device to the PC
Boot your device in fastboot mode (like you did during unlocking bootloader - power off the device and turn it on using power + vol down buttons and select "FASTBOOT")
Open up command prompt ( Start > Run > type cmd and hit enter ). The window that appears is called Command Prompt. <click here to see the image>
Navigate to where you unzipped "mini-sdk" package (type in Command Prompt: cd c:\mini-sdk). Note: make sure the path is not c:\mini-sdk\mini-sdk
In the Command Prompt type following command: fastboot boot recovery.img (this command might not with newer hboots)
Command above will not permantently flash custom recovery, but it will just boot it. Why? Because that way we can backup your original, stock recovery image before we replace it with custom one.
Perform a nandroid backup.
After nandroid backup is done, reboot the device in fastboot mode again.
In the Command Prompt type following command: fastboot flash recovery recovery.img
Now that your bootloader is unlocked and you have custom recovery flashed, you should decide what you want to do next. Let's assume you want to flash a custom ROM.
Flashing custom ROM
What you need to know before flashing custom ROM:
There are many custom ROMs out there. Some of them are more or less modified versions of HTC stock ROMs with HTC Sense. You might also find some AOSP, AOKP or CM ROMs based on pure Android UI without any HTC software on it. Choice is yours. Personally, I recommend you optimized ROMs with HTC Sense on board.
After flashing custom ROM you can always revert to your stock ROM. This procedure will be described later.
Download custom ROM of your choice and copy it to the internal memory of your device (virtual SD card or other)
Boot your device in recovery mode (power off the device and turn it on using power + vol down buttons and select "RECOVERY")
In main menu, select "install zip from sdcard" and "choose zip from sdcard".
Navigate to the location of custom ROM (zip) package and confirm flashing procedure.
Follow the steps on the screen. Every developer use slightly different options in his ROM installer, so just make sure you read it carefully.
If you can't flash custom ROM due to AROMA freezes, there is nothing to be worried about. Just ask for help the developer of your custom ROM.
After flashing process is complete, reboot the device.
However, you might not want to use any of the custom ROMs available, but just be able to have root access on your device. This also can be easily done!
Rooting stock ROM
What you need to know before rooting stock ROM:
You can "un-root" it easily.
As long as you won't change any files on system partition, you still will be able to download and install official OTA updates.
Download Rooting Tools
Boot your device in recovery mode (power off the device and turn it on using power + vol down buttons and select "RECOVERY")
In main menu, select "install zip from sdcard" and "choose zip from sdcard".
Navigate to the location of Rooting Tools (zip) package and confirm flashing procedure.
After flashing process is complete, reboot the device. Your device has now SuperUser.apk, su binary and busybox installed.
If you are not happy with being rooted, or you can't find any custom ROM for your needs, or you need to sell/return your device and you want it to have stock software on board, it's very easy operation.
Going back to stock
What you need to know before going back to stock:
Your bootloader will never be "LOCKED" again. You can't restore it. You can only relock it.
"TAMPERED" text in bootloader will disappear only after proceeding method 2.
There are 3 main methods. All three will be described below.
Method 1 - only for users with .401 devices (for more info click here - RUU variants)
Visit this thread - [ROM] HTC One *STOCK* ROM
Download stock odexed version of most recent firmware and recovery.img
Move recovery.img to c:\mini-sdk location
Boot your device in recovery mode (power off the device and turn it on using power + vol down buttons and select "RECOVERY")
In main menu, select "install zip from sdcard" and "choose zip from sdcard".
Navigate to the location of stock ROM (zip) package and confirm flashing procedure.
After flashing process is complete, reboot the device in bootloader mode.
Connect your device to the PC
Boot your device in fastboot mode (like you did during unlocking bootloader - power off the device and turn it on using power + vol down buttons and select "FASTBOOT")
Open up command prompt ( Start > Run > type cmd and hit enter ). The window that appears is called Command Prompt. <click here to see the image>
Navigate to where you unzipped "mini-sdk" package (type in Command Prompt: cd c:\mini-sdk). Note: make sure the path is not c:\mini-sdk\mini-sdk
In the Command Prompt type following command: fastboot flash recovery recovery.img
You have now stock boot, system and recovery partitions. Time to relock your bootloader.
In the Command Prompt type following command: fastboot oem lock
Method 2 - flashing RUU (ROM Update Utility)
Visit this or this thread.
Find proper RUU for your device
Connect your device to the PC
Boot your device in fastboot mode (like you did during unlocking bootloader - power off the device and turn it on using power + vol down buttons and select "FASTBOOT")
Open up command prompt ( Start > Run > type cmd and hit enter ). The window that appears is called Command Prompt. <click here to see the image>
Navigate to where you unzipped "mini-sdk" package (type in Command Prompt: cd c:\mini-sdk). Note: make sure the path is not c:\mini-sdk\mini-sdk
In the Command Prompt type following command: fastboot oem lock
Flash RUU and follow on screen instructions.
You have now completely stock software on your device.
Method 3 - flashing nandroid backup
In custom recovery restore nandroid backup you did after flashing custom recovery for the first time.
If you performed nandroid backup before permanently flashing custom recovery, your stock recovery should be now flashed.
If you still have custom recovery, extract recovery.img from your nandroid backup.
Move recovery.img to c:\mini-sdk location
Connect your device to the PC
Boot your device in fastboot mode (like you did during unlocking bootloader - power off the device and turn it on using power + vol down buttons and select "FASTBOOT")
Open up command prompt ( Start > Run > type cmd and hit enter ). The window that appears is called Command Prompt. <click here to see the image>
Navigate to where you unzipped "mini-sdk" package (type in Command Prompt: cd c:\mini-sdk). Note: make sure the path is not c:\mini-sdk\mini-sdk
In the Command Prompt type following command: fastboot flash recovery recovery.img
You have now stock boot, system and recovery partitions. Time to relock your bootloader.
In the Command Prompt type following command: fastboot oem lock
Here are some videos you might find helpful:
1) by Flow-Wolf
How to Unlock the bootloader
How to Flash the recovery
How to root the HTC One
2) by udimars30
How to Unbrick/Unroot/Flash stock Rom Back on HTC ONE

General FAQ
General FAQ
1. The zip installation just freezes in AROMA, what should I do?
This is a well known issue involving the AROMA installer, and this will occur with any ROM zip in any recovery. If it freezes, hold Power and Vol-Down until your phone reboots (If this fails, plug your phone into your PC and in CMD type 'adb reboot') Now go back into recovery and start the installation again. It is reported by many users that the installation works better if you don't use the touchscreen for navigation through AROMA - instead, use Vol-Up/Down to navigate and the Power button to select
UPDATE: Please make sure you have the latest recovery version. It is reported that CWM 6.0.3.2 fixes the freezes!​
2. When I try to enter recovery it just blinks for a second and the phone reboots. How do I get into recovery?
Use Vol-Down + Power to enter fastboot mode. Now connect the phone to the PC and use 'fastboot erase cache'. After that it should be able to boot recovery correctly.​
3. The phone rebooted itself while installing a ROM, now it just bootloops. How should I recover my phone?
Reboot into recovery and flash again. If recovery won't load, check FAQ 2.​
4. Do I need to wipe my data everytime I flash a new version of a ROM?
No, a data wipe is only needed when you come from stock or another custom ROM. It is also recommended but not manadtory to wipe when there is a base update. For a more specific answer, please check the Thread of the ROM you are using. The developers will tell you, when a wipe is mandatory.​
5. Do I need to flash boot.img seperately?
The majority of ROM installers will flash the boot.img for you. Yes, even when you are S-ON. This is possible on the One. Make sure to read the instructions for your ROM.​
6. Do I need to update my radio to flash a ROM?
It is not needed. You can do it if you want to. Newer radios can improve signal, bluetooth, WiFi... Refer to the following thread for more information: Link And also check this thread for a method to update radio in recovery: Link​
7. My device is not recognized by adb and fastboot. What should I do?
Make sure you have the latest HTC Drivers (Thread) running and your SDK is up-to-date. Try another USB Port and make sure your cable is working.​
8. What is S-OFF and do I need it to flash a ROM/Kernel/Recovery/Radio?
S-OFF means that your bootloader is fully unlocked and allows you to write to more partition than you usually can. You would also be able to flash unsigned firmware. You don't need S-OFF for ROMs, kernels, recoveries and also not for radios (Check FAQ 6)​
9. What is the best ROM/Kernel/Recovery?
I really can't answer that question. It greatly depends on what you like. As mentioned in the first post there are Sense, AOKP, AOSP, CM... ROMs. Also there are several kernels, some focusing on performance, some focusing on battery life. Go on and try a few to see what fits you best. You should always make a nandroid backup, so you can go back to another ROM later.​
10. I forgot to put a ROM on my sdcard before wiping/flashing kernel and my phone won't boot now. How do I get a ROM on there?
If you have a nandroid backup on the phone, resore it. If you don't have a backup, copy the ROM you wanted to install to the phone via 'adb push rom-name.zip /data/media/rom-name.zip' Then flash as described above.​
11. Will unlocking or relocking wipe my device?
Unlocking will wipe your device. So please backup your data! Relocking will NOT wipe it, just when you unlock again.​
12. My issue is not mentioned here and/or my phone is still not working after trying to recover. What should I do?
You are always free to post in this thread or the ROM/Kernel/Recovery/Radio thread. You will find helpful members who will support you in solving your problem.​
Note: The FAQ are always under construction. New QAs will be added when the get F(requent) (You can also contact me if you find a Q that is not covered here)

There was no complete guide, so I decided to write one myself I hope users will enjoy it!
That was a lot of text for me to write, so if I made mistake somewhere, please feel free to correct me! This thread is generally still under construction and I will improve first post in time

Reserved.

Great work
Hey Mate
Great work... very well done!
Now everything should be clear...
CHeers
K.

Fantastic guide, is tampered a new thing for the HTC One? I don't remember the One X having the issue?

Thanks so much for this

ste1164 said:
Fantastic guide, is tampered a new thing for the HTC One? I don't remember the One X having the issue?
Click to expand...
Click to collapse
Yes, it's sort of new sign for HTC that user did something more then just unlocking.

mike1986. said:
Yes, it's sort of new sign for HTC that user did something more then just unlocking.
Click to expand...
Click to collapse
Ah right okay still thinking about rooting mine

sorry for asking but what is mini-sdk? unlocked the bootloader with all-in-one tool. is it something in the android sdk? where to get it? thanks

ggp759 said:
sorry for asking but what is mini-sdk? unlocked the bootloader with all-in-one tool. is it something in the android sdk? where to get it? thanks
Click to expand...
Click to collapse
It's the package of needed files I created. You can download it by clicking on the link.

mike1986. said:
It's the package of needed files I created. You can download it by clicking on the link.
Click to expand...
Click to collapse
Thanks did not see that. link does not work though.

ggp759 said:
Thanks did not see that. link does not work though.
Click to expand...
Click to collapse
Fixed now

can you explain me something ?
if I click negative effects of unlocked bootloader, it says I can't receive OTA updates.
but in your Rooting stock rom section, you said we can still receive OTA updates.
is there something I'm missing or didnt read correctly ?
also, is the procedure the same for all HTC One, no matter which carrier I bought it from ?

grat_master said:
can you explain me something ?
if I click negative effects of unlocked bootloader, it says I can't receive OTA updates.
but in your Rooting stock rom section, you said we can still receive OTA updates.
is there something I'm missing or didnt read correctly ?
also, is the procedure the same for all HTC One, no matter which carrier I bought it from ?
Click to expand...
Click to collapse
1. Well, I decided not to mention some things to avoid confusion. At the moment unlocking bootloader removes content of /data/preload partition, so indeed, installing OTA will fail. But I truly hope that HTC will fix it at some point and unlocking bootloader won't cause some stock apps to be missing.
2. Which procedure?

by procedures, I meant unlocking bootloader / root / flash custom kernels and/or roms, etc
basically, everything in your guide in 1st post. I live in Canada, I will be buying HTC One from Rogers, so I wonder if all your guides works on every HTC One coming from all carriers/stores/countries.
I'm used to root and flash on Xperia Arc, but never owned an HTC cell phone.
Thanks for quick reply, I really appreciate your work !

grat_master said:
by procedures, I meant unlocking bootloader / root / flash custom kernels and/or roms, etc
basically, everything in your guide in 1st post. I live in Canada, I will be buying HTC One from Rogers, so I wonder if all your guides works on every HTC One coming from all carriers/stores/parts of the world.
I'm used to root and flash on Xperia Arc, but never owned an HTC cell phone.
Thanks for quick reply, I reaaly appreciate all your work !
Click to expand...
Click to collapse
Yes, I think it applies to all HTC One variants.

Great tutorial and FAQs, thanks for sharing!
It's been a while since my last HTC Android device and this will be handy as soon as I get my M7!

OMG! This must have been a lot of work to make this tutorial! Thank you so much for this, i think many people will be using this thread!
Sent from my HTC One using xda app-developers app

Keupie said:
OMG! This must have been a lot of work to make this tutorial! Thank you so much for this, i think many people will be using this thread!
Sent from my HTC One using xda app-developers app
Click to expand...
Click to collapse
I did my very best!

[GUIDE] Unlock/Root/Flash for HTC One XL

[SIZE=+3]Heisenberg's How-To Guide For Beginners[/SIZE]
[SIZE=+2]HTC One XL, AT&T, Rogers HTC One X, Telstra One XL[/SIZE]
{
"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"
}
[SIZE=+1]Intro[/SIZE]
This thread will serve as a location for basic how-to guides for the HTC One XL (Evita). I'm going to start off with a couple of the more obvious ones and go from there. If anyone has any suggestions for additions please feel free to let me know.
Please note: you'll need a working adb/fastboot environment on your PC to get through some of these guides. There are many guides on how to install adb/fastboot available on XDA.
This is not a q&a/help thread, if you have questions regarding the processes mentioned here please ask in the appropriate place
By attempting any of the processes listed this thread you accept full responsibility for your actions. I will not be held responsible if your device stops working, catches on fire, or turns into a hipster and claims to have been modified before it was cool. Make sure you read a section and fully understand it before attempting it.
[SIZE=+1]Index[/SIZE]
How To Unlock The Bootloader On An AT&T Phone With 3.18 Software
How To Unlock The Bootloader On An AT&T Phone With 5.18 Software
How To Install A Custom Recovery On Your Device
How To Make A Nandroid Backup With TWRP Recovery
How To Install A ROM with TWRP Recovery
How To Flash A Boot.img With Fastboot
How To Install A Custom Kernel With TWRP Recovery
How To Make Sure You Can Pretty Much Always Recover From An Accidentally Wiped System
How To Flash The 2.15 Firmware
[SIZE=+1]1. How To Unlock The Bootloader On An AT&T Phone With 3.18 Software[/SIZE]
All AT&T phones are blocked from having their bootloader unlocked at htcdev, they achieve this by checking the CID of the device. Any device with the at&t CID (CWS__001) will not be able to do it, so you need to get temp root which allows you to get SuperCID (11111111). There is a dev thread dedicated to this exploit but it doesn't contain the most user-friendly directions so here's a quick guide.
Download the xpwn.tar.gz file from here.
Extract it into your fastboot folder.
Make sure you're booted into Android with usb debugging enabled. Connect your phone to your PC via usb cable.
Open a command prompt from within your fastboot folder (navigate to where you have fastboot.exe located on your PC, shift + right click anywhere within that folder, select open command prompt here).
Test the connection by entering this command:
Code:
adb devices
It should return your device serial number, once you've verified a connection you can start the process.
Command #1
Code:
adb push oneXchopper /data/local/tmp/xpwn
Command #2
Code:
adb push busybox /data/local/tmp/busybox
Command #3
Code:
adb push ownage /data/local/tmp/phase1.sh
Command #4
Code:
adb shell chmod 755 /data/local/tmp/xpwn /data/local/tmp/busybox
Command #5
Code:
adb shell ln -s /data/local/tmp/busybox /data/local/tmp/sed
Command #6
Code:
adb shell "/data/local/tmp/xpwn"
Command #7
Code:
adb reboot bootloader
Now test if it worked by entering this command:
Code:
fastboot oem readcid
Hopefully you'll see 11111111, then you can go to htcdev and unlock your bootloader.
[SIZE=+1]2. How To Unlock The Bootloader On An AT&T Phone With 5.18 Software[/SIZE]
All AT&T phones are blocked from having their bootloader unlocked at htcdev, they achieve this by checking the CID of the device. Any device with the at&t CID (CWS__001) will not be able to do it, so you need to use an exploit which allows you to get SuperCID (11111111). There is no actual single exploit to do this on the 5.18 firmware, you need to use a couple of separate methods in conjunction to get it done.
Go to the Weaksauce thread and get temporary root using that tool.
Once you have temp-root you need to go to the Rumrunner S-off site and use that tool to get s-off. Make sure you read the instructions carefully. The device will have to reboot during the s-off process, which means that the Weaksauce app may or may not automatically root again after boot, you need to keep an eye on this because if it doesn't you'll need to do it manually when the device boots up otherwise the rumrunner method won't work. This can be frustrating, this is a finicky process, this isn't exactly the easiest method in the world but it does indeed work.
Checking your bootloader to ensure that you have s-off.
Boot into the bootloader, make sure your phone is connected to your PC via usb, and issue this command:
Code:
fastboot oem writecid 11111111
Confirm that you now have SuperCID with this command:
Code:
fastboot oem readcid
That's it, once you have SuperCID you can go to htcdev and unlock your bootloader.
[SIZE=+1]3. How To Install A Custom Recovery On Your Device[/SIZE]
Prerequisites: unlocked bootloader.
Download the recovery of your choice.
Check the md5 to verify its integrity (where possible).
Place the file in your fastboot folder (this is where fastboot.exe is located on your PC).
Put the phone in fastboot mode and connect it to your PC via usb cable.
Open a command prompt from within your fastboot folder (shift + right click, select open command prompt here), and enter the following commands:
Code:
fastboot flash recovery openrecovery-twrp-2.8.7.0-evita.img
(The recovery filename in the command will change depending on which recovery you're flashing)
Code:
fastboot erase cache
Code:
fastboot reboot
Select the recovery option from your bootloader screen to enter your custom recovery.
[SIZE=+1]4. How To Make A Nandroid Backup With TWRP Recovery[/SIZE]
Prerequisites: unlocked bootloader, TWRP recovery.
A nandroid backup is a very important thing to have before installing any custom software on your device. It's basically a backup of your stock system that you can fall back on if anything goes wrong or if you just want your stock ROM back. You can also use the backup tool to create a backup of your favourite ROM set up exactly the way you like it. The backup you create can be easily restored using the restore tool in TWRP recovery.
All you need to do is enter TWRP recovery, select the backup option from the TWRP home screen, check the system/data/boot boxes, and swipe to backup. The process will take a few minutes.
Please note: Backups can easily take up over 1gb of space in your internal storage. Moving them to a PC or external drive is a great idea to save space on your phone.
[SIZE=+1]5. How To Install A ROM with TWRP Recovery[/SIZE]
Prerequisites: unlocked bootloader, TWRP recovery.
Installing a ROM is a pretty straight forward and easy process. Before you install anything you should make a nandroid backup (instructions above).
Download a ROM and appropriate Gapps package (if required) and place on your device.
Boot into your custom recovery.
Perform a full wipe.
Select the wipe option from the TWRP home screen.
Select advanced wipe.
Check the system, data, cache, and dalvik cache options.
Swipe to wipe.
Install the ROM.
Select the install option from the TWRP home screen.
Navigate to where you have the ROM zip stored on your sd card and select it.
Swipe to install.
Most ROMs will run an installer script at this point but some ROMs have what is called an Aroma Installer which allow you to choose some install options before the script runs.​
If you're flashing an aosp (not Sense based) ROM you will also need to install the appropriate gapps package directly after installing the ROM.
Once you've installed all necessary zips you'll have an option to wipe cache/dalvik and an option to reboot system. Wipe the cache/dalvik, hit the back button, and hit the reboot system button.
Please note: if your phone has a hboot of 1.14 or higher and is s-on you'll also need to flash the boot.img with fastboot. Do not hit the reboot system button at the end of this process. Hit the home button, select the reboot option from the TWRP home screen, then hit the reboot bootloader button. Instructions to flash the boot.img are below.
[SIZE=+1]6. How To Flash A Boot.img With Fastboot[/SIZE]
Prerequisites: unlocked bootloader.
If your phone has a hboot of 1.14 or higher and is s-on, flashing a ROM or kernel through your recovery of choice won't be enough to boot the phone. The boot.img included in the ROM zip is unable to be installed by the recovery due to a security restriction that was introduced in the 1.14 hboot. Every time you want to flash a ROM you also need to flash the boot.img manually via fastboot.
Open/extract/view the ROM zip and in the root directory you'll see a file called "boot.img", copy this file and put it in your fastboot folder on your PC.
After you've flashed the ROM in recovery, instead of selecting a normal reboot select to reboot to the bootloader.
Once your phone has booted into the bootloader you can connect it to your PC, it should now say "fastboot usb" on the screen.
Open a command prompt from within your fastboot folder (shift + right click, select open command prompt here) and issue this fastboot command:
Code:
fastboot flash boot boot.img
It'll take a few seconds to flash the boot.img.
Once it's finished you can use the following command to reboot:
Code:
fastboot reboot
Now your phone should successfully boot up into your brand new ROM. Remember, each time you want to flash a new ROM you need to flash the boot.img as well. If you decide to get s-off on your device you will no longer need to go through this process.
[SIZE=+1]7. How To Install A Custom Kernel With TWRP Recovery[/SIZE]
Prerequisites: unlocked bootloader, TWRP recovery.
A custom kernel can open up a new level of control over your device, such as overclocking/underclocking, undervolting, changing governors, changing I/O schedulers, adjusting colour calibrations, adjusting sound calibrations, and many other options.
Download a kernel that is compatible with your current ROM.
Check the md5 to verify its integrity.
Enter TWRP recovery.
Select the install option from the TWRP home screen.
Navigate to the kernel and select it.
Swipe to install.
You'll have an option to wipe cache/dalvik and an option to reboot system. Wipe the cache/dalvik, hit the back button, and hit the reboot system button.
Once your phone has booted up you can use a kernel tuning app to change governors, I/O scheduler, clock speed, and other options. Some of the popular kernel apps are Trickster Mod, No Frills, Kernel Tuner, and many more.
[SIZE=+1]8. How To Make Sure You Can Pretty Much Always Recover From An Accidentally Wiped System[/SIZE]
Prerequisites: unlocked bootloader, TWRP recovery.
There may come a time when you accidentally wipe your OS while trying to perform a basic cache wipe in recovery. Don't laugh, it can happen to the best of us. The best way to insure yourself against being stuck in recovery is to keep a ROM zip or a TWRP/CWM backup (a nandroid backup) on your sd card at all times.
This solution seems like common sense but apparently there are quite a few people out there who don't store a ROM or backup on their phone. You might think it's easy to just mount the sd card and copy a ROM across to your phone from your PC (which is definitely an option), but there's always a chance that you won't be near your PC at the time, or it won't recognise your phone properly. Basically you need to insure yourself against Murphy's law.
[SIZE=+1]9. How To Flash The 2.15 Firmware[/SIZE]
Prerequisites: unlocked bootloader, s-off, SuperCID.
Warning! If you have the middle eastern variant (Evita_utl) do not flash this firmware, it is not compatible with your device and will cause irreparable damage.
Download the firmware from here.
Place it in your fastboot folder and rename it to "215firmware.zip" to make things easier later on.
Reboot into the bootloader and connect your phone to your PC via usb cable.
Open a command prompt from within your fastboot folder (shift + right click, select open command prompt here) and issue this fastboot command to check your fastboot connection:
Code:
fastboot devices
Once you've established a working connection (it'll show your serial number) you can start the process with this command:
Code:
fastboot oem rebootRUU
The phone will now boot into rebootRUU mode which is a black screen with the HTC logo.
Issue this command:
Code:
fastboot flash zip 215firmware.zip
If the output ends with "FAILED (remote: 90 hboot pre-update! please flush image again immediately)", run the previous command again. If it ends with "INFO..... OK", just reboot to the bootloader with this command:
Code:
fastboot reboot-bootloader
Verify the flash was successful by checking the hboot version and radio version in the bootloader screen. They should be as follows:
Hboot: 2.15
Radio: 1.31a.32.45.16_2
Reboot your phone by issuing this command:
Code:
fastboot reboot
Please note that the progress bar on the screen of your phone won't ever reach 100% even after the process is finished. As long as the process says it's finished in the command prompt it's safe to reboot.
Donate To Me
Sent from my Evita

For further information

The download link for the 2.18 firmware doesn't appear to be working.

hdk703 said:
The download link for the 2.18 firmware doesn't appear to be working.
Click to expand...
Click to collapse
Thanks for the heads up, I'll try to track it down and upload it again.
Transmitted via Bacon

hdk703 said:
The download link for the 2.18 firmware doesn't appear to be working.
Click to expand...
Click to collapse
Fixed.
Transmitted via Bacon

unable to transfer on HTC onex AT&T
C:\adb>adb devices
List of devices attached
HT282W306697 device
C:\adb>adb push oneXchopper /data/local/tmp/xpwn
cannot stat 'oneXchopper': No such file or directory
C:\adb>cd xpwn
C:\adb\xpwn>adb push oneXchopper /data/local/tmp/xpwn
4177 KB/s (1283460 bytes in 0.300s)
C:\adb\xpwn>adb push busybox /data/local/tmp/busybox
2809 KB/s (811432 bytes in 0.282s)
C:\adb\xpwn>adb push ownage /data/local/tmp/phase1.sh
24 KB/s (296 bytes in 0.012s)
C:\adb\xpwn>adb shell chmod 755 /data/local/tmp/xpwn /data/local/tmp/busybox
C:\adb\xpwn>adb shell ln -s /data/local/tmp/busybox /data/local/tmp/sed
C:\adb\xpwn>adb reboot bootloader
C:\adb\xpwn>fastboot oem readcid
...
(bootloader) cid: CWS__001
OKAY [ 0.011s]
finished. total time: 0.012s
C:\adb\xpwn>

Ive soft bricked my htc one x AT&T and my computer does not recognize my device
@timma U need to help me man !!!! Ive soft bricked my htc one x at&t(Deleted my ROM) . When i start my phone with normal Power on i just GET the white HTC screen . I am able to reach to the TWRP screen its got the following details :
S-ON RL
HBOOT-1.14.002
RADIO-0.19as.32.09.11_2
I tried fastboot and recovery mode and when i try and restart it it tells me no os installed.
I use Ubuntu 14.04 installed the android SDK with eclipse and tried the adb sideload with a custom rom but it does not find my device
though when its switched off and usb attached to my computer it charges.
WHAT TO DO ? PLZ HELP ME :crying:!!!!!!!!!!

solodancer said:
@timma U need to help me man !!!! Ive soft bricked my htc one x at&t(Deleted my ROM) . When i start my phone with normal Power on i just GET the white HTC screen . I am able to reach to the TWRP screen its got the following details :
S-ON RL
HBOOT-1.14.002
RADIO-0.19as.32.09.11_2
I tried fastboot and recovery mode and when i try and restart it it tells me no os installed.
I use Ubuntu 14.04 installed the android SDK with eclipse and tried the adb sideload with a custom rom but it does not find my device
though when its switched off and usb attached to my computer it charges.
WHAT TO DO ? PLZ HELP ME :crying:!!!!!!!!!!
Click to expand...
Click to collapse
Ok, first, the screen with the s-on, hboot, radio details isn't your TWRP screen, that's your bootloader. What recovery do you have installed?
Transmitted via Bacon

timmaaa said:
Ok, first, the screen with the s-on, hboot, radio details isn't your TWRP screen, that's your bootloader. What recovery do you have installed?
Transmitted via Bacon
Click to expand...
Click to collapse
From the Bootloader screen when i click on recovery option it takes me to the TWRP v2.6.3.0 screen.

solodancer said:
From the Bootloader screen when i click on recovery option it takes me to the TWRP v2.6.3.0 screen.
Click to expand...
Click to collapse
Ok. You're gonna need to flash a ROM, but first you're gonna need to copy one from your PC to your phone. In order to do that you're gonna need to temporarily install TWRP 2.6, it's the last version that actually allows to your mount your internal storage to a PC. Download it from here
https://goo.im/devs/OpenRecovery/evita/openrecovery-twrp-2.6.0.0-evita.img/
Flash it with fastboot:
Code:
fastboot flash recovery openrecovery-twrp-2.6.0.0-evita.img
Once that's done, boot into TWRP and select the mount option from the main menu, connect your phone to your PC, and then hit the mount usb storage option. Your phone should now mount to your PC as a removable drive which will allow you to transfer a ROM zip across.
Now to the next part. You need to get s-off, because you need to update your firmware in order to run any recent ROM. The best way to get s-off is to flash the Kickdroid 5.0 ROM, and then use Rumrunner to get s-off. Once you have s-off you can update your firmware (instructions at beginning of this thread). Once you've done that you can flash whatever ROM you like (for aosp ROMs you'll need to put TWRP 2.6.3.0 or above back on your phone).
Kickdroid
Rumrunner

timmaaa said:
Ok. You're gonna need to flash a ROM, but first you're gonna need to copy one from your PC to your phone. In order to do that you're gonna need to temporarily install TWRP 2.6, it's the last version that actually allows to your mount your internal storage to a PC. Download it from here
https://goo.im/devs/OpenRecovery/evita/openrecovery-twrp-2.6.0.0-evita.img/
Flash it with fastboot:
Code:
fastboot flash recovery openrecovery-twrp-2.6.0.0-evita.img
Once that's done, boot into TWRP and select the mount option from the main menu, connect your phone to your PC, and then hit the mount usb storage option. Your phone should now mount to your PC as a removable drive which will allow you to transfer a ROM zip across.
Now to the next part. You need to get s-off, because you need to update your firmware in order to run any recent ROM. The best way to get s-off is to flash the Kickdroid 5.0 ROM, and then use Rumrunner to get s-off. Once you have s-off you can update your firmware (instructions at beginning of this thread). Once you've done that you can flash whatever ROM you like (for aosp ROMs you'll need to put TWRP 2.6.3.0 or above back on your phone).
Kickdroid
Rumrunner
Click to expand...
Click to collapse
Thanks a lot for the help but could you please explain to me the 1. step in a bit detail how do i go about installing twrp-2.6.0.0 image ? what steps do i need to follow on my phone ?
1. I connected my phone to the pc i see the charging light flashing
2. went to the bootloader screen and selected the fastboot mode.
3. ran the fastboot command on pc
4.In the bootloader screen selected reboot bootloader
but now on reboot in fastboot mode i dont see a fastboot usb mode and the command it keeps on waiting for the device nothing happens after that .
Am i doing something wrong?

solodancer said:
Thanks a lot for the help but could you please explain to me the 1. step in a bit detail how do i go about installing twrp-2.6.0.0 image ? what steps do i need to follow on my phone ?
1. I connected my phone to the pc i see the charging light flashing
2. went to the bootloader screen and selected the fastboot mode.
3. ran the fastboot command on pc
4.In the bootloader screen selected reboot bootloader
but now on reboot in fastboot mode i dont see a fastboot usb mode and the command it keeps on waiting for the device nothing happens after that .
Am i doing something wrong?
Click to expand...
Click to collapse
Have you selected recovery from the bootloader menu to confirm that the recovery image flashed?
Transmitted via Bacon

timmaaa said:
Have you selected recovery from the bootloader menu to confirm that the recovery image flashed?
Transmitted via Bacon
Click to expand...
Click to collapse
selected the recovery from the bootloader it opens up the old TWRP v2.6.3.0 screen

solodancer said:
selected the recovery from the bootloader it opens up the old TWRP v2.6.3.0 screen
Click to expand...
Click to collapse
Please try flashing the recovery again and copy/paste all of the text from the command prompt here so I can have a look.
Transmitted via Bacon

timmaaa said:
Please try flashing the recovery again and copy/paste all of the text from the command prompt here so I can have a look.
Transmitted via Bacon
Click to expand...
Click to collapse
hey this is what i see
Code:
[email protected]:/home/solo/Downloads# fastboot flash recovery openrecovery-twrp-2.6.0.0-evita.img
< waiting for device >

solodancer said:
hey this is what i see
Code:
[email protected]:/home/solo/Downloads# fastboot flash recovery openrecovery-twrp-2.6.0.0-evita.img
< waiting for device >
Click to expand...
Click to collapse
What mode is your phone in?
Transmitted via Bacon

timmaaa said:
What mode is your phone in?
Transmitted via Bacon
Click to expand...
Click to collapse
from the bootloader menu i selected fastboot and then reboot bootloader

solodancer said:
from the bootloader menu i selected fastboot and then reboot bootloader
Click to expand...
Click to collapse
Why are you selecting reboot bootloader? Just get into fastboot mode and then flash the recovery.
Transmitted via Bacon

solodancer said:
from the bootloader menu i selected fastboot and then reboot bootloader
Click to expand...
Click to collapse
in the fastboot mode i see 4 options bootloader, reboot, reboot bootloader and power down . what should i do next?

solodancer said:
in the fastboot mode i see 4 options bootloader, reboot, reboot bootloader and power down . what should i do next?
Click to expand...
Click to collapse
What do you mean? While in fastboot mode you flash the recovery.
Transmitted via Bacon

Help please.

Long time android user and "moder" here. Never owned an HTC device other than the ONE which I didn't have long. I just acquired this phone from some guy at my job who tried to mod it and he has it rooted with CM10 (which is ICS right? because it's ICS on it don't remember if it was 10 or not). I've downloaded, many, many roms over the past few days from JB to KK and tried to flash them and I successfully flash them in CWM but it just stays on the white HTC screen, and doesn't boot up. Any idea why this is happening?

C-4Nati said:
Long time android user and "moder" here. Never owned an HTC device other than the ONE which I didn't have long. I just acquired this phone from some guy at my job who tried to mod it and he has it rooted with CM10 (which is ICS right? because it's ICS on it don't remember if it was 10 or not). I've downloaded, many, many roms over the past few days from JB to KK and tried to flash them and I successfully flash them in CWM but it just stays on the white HTC screen, and doesn't boot up. Any idea why this is happening?
Click to expand...
Click to collapse
if you are on S-ON flash 4ext recovery
format all partitions except sdcard from 4ext
enable smartflash from 4ext
flash the rom
done

@C-4Nati also..if your bootloader is still s-on state (and stil using cwm recovery)..did you already flashing a boot.img from the rom that you had already installed..?
if not yet..you can try flashing it through fastboot.. "fastboot flash boot boot.img"

JJeamy said:
@C-4Nati also..if your bootloader is still s-on state (and stil using cwm recovery)..did you already flashing a boot.img from the rom that you had already installed..?
if not yet..you can try flashing it through fastboot.. "fastboot flash boot boot.img"
Click to expand...
Click to collapse
No he didn't flash a boot.IMG and its s on. No idea to do what you said :/ any guides you could link to

C-4Nati said:
No he didn't flash a boot.IMG and its s on. No idea to do what you said :/ any guides you could link to
Click to expand...
Click to collapse
If we know ur bootloader details then would make things easier, (turn off phone then press volume down + power) anyway, both these links will get u to where u want to be
http://forum.xda-developers.com/showthread.php?t=1864053
Or here. http://forum.xda-developers.com/showthread.php?t=1631861
Also as @rzr86 said, flash latest 4ext recovery (added below)

jmcclue said:
If we know ur bootloader details then would make things easier, (turn off phone then press volume down + power) anyway, both these links will get u to where u want to be
http://forum.xda-developers.com/showthread.php?t=1864053
Or here. http://forum.xda-developers.com/showthread.php?t=1631861
Also as @rzr86 said, flash latest 4ext recovery (added below)
Click to expand...
Click to collapse
This is 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"
}

C-4Nati said:
This is it.
Click to expand...
Click to collapse
ok, have u fastboot setup on ur pc?

jmcclue said:
ok, have u fastboot setup on ur pc?
Click to expand...
Click to collapse
I'm not sure so I'm assuming that means no lol.

C-4Nati said:
I'm not sure so I'm assuming that means no lol.
Click to expand...
Click to collapse
click the first link i posted n set it up

jmcclue said:
click the first link i posted n set it up
Click to expand...
Click to collapse
I installed the sdk and fastboot and everything, and when I enter the fastboot oem token indentifier command all the command prompt says is waiting on device. I've double checked all instructions and it just keeps saying waiting on device.
Edit- I tried to flash the 4ext in cwm and it said installation aborted everytime.

C-4Nati said:
I installed the sdk and fastboot and everything, and when I enter the fastboot oem token indentifier command all the command prompt says is waiting on device. I've double checked all instructions and it just keeps saying waiting on device.
Edit- I tried to flash the 4ext in cwm and it said installation aborted everytime.
Click to expand...
Click to collapse
you are already unlocked your bootloader..so you don't need get identifier token again to unlock your bootloader..
1. first way..like what rzr86 and jmcclue said above..because you're still s-on but already had unlocked bootloader..they've suggest you to installing 4ext recovery for the next future you can easily installing of custom rom...because 4ext recovery is already option "SmartFlash" that fuction can installing custom rom with automatically supported also installing a boot.img from the rom itself under s-on devices like yours..
to installing that 4ext recovery...you can download recovery.zip from here.., then extracted that recovery.zip file to get recovery.img file...then copied recovery.img file to your sdk / adb folder (that are a same place as your adb.exe and fastboot.exe), after that...you can boot your phone to bootloader mode..then select "FASTBOOT" from there, then plug your phone to pc..until indicator in the phone has "FASTBOOT-USB", after that you can open cmd from your adb folder (just press and hold shift + right click on empty space from that folder and select "Open command window here") ...then typing command "fastboot devices" ..see if the output has detect your phone serial number.. if so...then continued typing "fastboot flash recovery recovery.img" then "fastboot reboot-bootloader" done..now you can tested it go to your 4ext recovery..and now you can enabled it "SmartFlash" from tools option before you installing any custom rom from 4ext recovery...
2. second way...if you don't want change you cwm recovery..you can fix your booting stuck by just flashing a boot.img extracted from the rom.zip itself with manual flashing from fastboot..
to do that...firstly just copied rom.zip that you wanna installing to another folder..then extracting / unzipping that file...then copied boot.img to your adb / sdk (same place as your adb.exe and fastboot.exe) folder..then after you've already installing that custom rom from cwm..you must reboot your phone to bootloader again (don't booting the rom first), then select FASTBOOT from there..then plug your phone to pc until indicator in your phone has FASTBOOT-USB..then open cmd from your adb / sdk folder..then typing command "fastboot flash boot boot.img" then "fastboot reboot" done...now you can see that the phone can booting of the rom normally or not..
hope this help..

JJeamy said:
you are already unlocked your bootloader..so you don't need get identifier token again to unlock your bootloader..
1. first way..like what rzr86 and jmcclue said above..because you're still s-on but already had unlocked bootloader..they've suggest you to installing 4ext recovery for the next future you can easily installing of custom rom...because 4ext recovery is already option "SmartFlash" that fuction can installing custom rom with automatically supported also installing a boot.img from the rom itself under s-on devices like yours..
to installing that 4ext recovery...you can download recovery.zip from here.., then extracted that recovery.zip file to get recovery.img file...then copied recovery.img file to your sdk / adb folder (that are a same place as your adb.exe and fastboot.exe), after that...you can boot your phone to bootloader mode..then select "FASTBOOT" from there, then plug your phone to pc..until indicator in the phone has "FASTBOOT-USB", after that you can open cmd from your adb folder (just press and hold shift + right click on empty space from that folder and select "Open command window here") ...then typing command "fastboot devices" ..see if the output has detect your phone serial number.. if so...then continued typing "fastboot flash recovery recovery.img" then "fastboot reboot-bootloader" done..now you can tested it go to your 4ext recovery..and now you can enabled it "SmartFlash" from tools option before you installing any custom rom from 4ext recovery...
2. second way...if you don't want change you cwm recovery..you can fix your booting stuck by just flashing a boot.img extracted from the rom.zip itself with manual flashing from fastboot..
to do that...firstly just copied rom.zip that you wanna installing to another folder..then extracting / unzipping that file...then copied boot.img to your adb / sdk (same place as your adb.exe and fastboot.exe) folder..then after you've already installing that custom rom from cwm..you must reboot your phone to bootloader again (don't booting the rom first), then select FASTBOOT from there..then plug your phone to pc until indicator in your phone has FASTBOOT-USB..then open cmd from your adb / sdk folder..then typing command "fastboot flash boot boot.img" then "fastboot reboot" done...now you can see that the phone can booting of the rom normally or not..
hope this help..
Click to expand...
Click to collapse
Hey, I really really appreciate you trying to help. Both those directions are clear and I know I could easily do either but the only problem is for some reason my computer doesn't recognize the phone and when in fastboot mode it never says fastboot-usb and cmd always says waiting on device. I know usb debugging is enabled but I'm on an aosp rom so I didn't have the option to uncheck fastboot under power, is that the problem maybe? I have android SDK installed and the app "htc sync" so I'm not sure why it doesn't recognize the phone.
edit -it did end up saying "fastboot usb" but in cmd it still said waiting on device and when I typed fastboot devices no serial number came up.

C-4Nati said:
Hey, I really really appreciate you trying to help. Both those directions are clear and I know I could easily do either but the only problem is for some reason my computer doesn't recognize the phone and when in fastboot mode it never says fastboot-usb and cmd always says waiting on device. I know usb debugging is enabled but I'm on an aosp rom so I didn't have the option to uncheck fastboot under power, is that the problem maybe? I have android SDK installed and the app "htc sync" so I'm not sure why it doesn't recognize the phone.
Click to expand...
Click to collapse
what OS you have on your computer?

Mile_zdr said:
what OS you have on your computer?
Click to expand...
Click to collapse
Let me edit my previous post, as in the bootloader it did end up saying "fastboot usb" but in cmd it still said waiting on device and when I typed fastboot devices no serial number came up. I have windows 8.1

C-4Nati said:
Let me edit my previous post, as in the bootloader it did end up saying "fastboot usb" but in cmd it still said waiting on device and when I typed fastboot devices no serial number came up. I have windows 8.1
Click to expand...
Click to collapse
Could this have something to do with it? For some reason the device is recognized if I go into device and printers but it's not listed under the "this PC" area like all my other devices go to. It also wont let me browse the phones internal storage for some reason. http://i.imgur.com/FnhjwYa.png
edit - this is what it says while I'm in fastboot mode and plug the phone in.

C-4Nati said:
Could this have something to do with it? For some reason the device is recognized if I go into device and printers but it's not listed under the "this PC" area like all my other devices go to. It also wont let me browse the phones internal storage for some reason. http://i.imgur.com/FnhjwYa.png
edit - this is what it says while I'm in fastboot mode and plug the phone in.
Click to expand...
Click to collapse
i lot of people have problems with fasboot and win 8.1 i don't know does have solution, but try with win 7 if you have another computer

Mile_zdr said:
i lot of people have problems with fasboot and win 8.1 i don't know does have solution, but try with win 7 if you have another computer
Click to expand...
Click to collapse
I used my windows 7 pc and everything worked. You guys are all AWESOME! and I appreciate all the help. Now I'm having problems with getting signal lol -.- I purchased an unlock code from a website and when I put my t mobile sim it and the phone boots it says enter code and I do and it says network unlock successful but I won't get signal at all. I've rebooted and entered code again and taken sim out and put back in to no avail lol. This phone just won't be easy lol.

C-4Nati said:
I used my windows 7 pc and everything worked. You guys are all AWESOME! and I appreciate all the help. Now I'm having problems with getting signal lol -.- I purchased an unlock code from a website and when I put my t mobile sim it and the phone boots it says enter code and I do and it says network unlock successful but I won't get signal at all. I've rebooted and entered code again and taken sim out and put back in to no avail lol. This phone just won't be easy lol.
Click to expand...
Click to collapse
dial *#*#4636#*#* than go to phone information and set the network to WCDMA prefered see if it work

Mile_zdr said:
dial *#*#4636#*#* than go to phone information and set the network to WCDMA prefered see if it work
Click to expand...
Click to collapse
I did that an it didn't do anything. This is originally a T-Mobile phone but a local company called Cincinnati Bell (which is also a GSM/sim card using company) buys units to resell and locks them on their service. I have T-Mobile and paid for the unlock code so I could use T-Mobile on it but so far it's not working (though it says network unlock successful).

C-4Nati said:
I did that an it didn't do anything. This is originally a T-Mobile phone but a local company called Cincinnati Bell (which is also a GSM/sim card using company) buys units to resell and locks them on their service. I have T-Mobile and paid for the unlock code so I could use T-Mobile on it but so far it's not working (though it says network unlock successful).
Click to expand...
Click to collapse
?
I don't know what to tell you... :/ do you have another sim card from other carrier just to see everything work's okey?

I'm really stuck getting recovery installed - please help?

Hi all,
I've followed various sets of instructions for installing a recovery onto my E6653. I was able to get recovery to boot successfully using the sony-recovery-z5.img found HERE, but it can't see, mount, format or wipe my ext SD card at all in this recovery so I can't initiate the install of a ROM from it.
I've tried stacks of other recoveries and boot images (kernels?), including:
[TWRP][E6653/E6603/E6633/E6683] 3.0.2 , all ROMs
[TWRP][E6653/E6603] 2.8.7.0 and Stock Rootable Kernel [2015-11-15]
[KERNEL][E6653/E6633/E6683] Zach's Kernel Playground for Z5, WIP (work in progress)
https://www.gizdev.com/sony-xperia-z5-e6653e6603-unlock-bootloader-install-twrp-recovery-root/
but none of these work - the phone will no longer boot after flashing boot.img (stuck at sony logo) and the recoveries will not launch - don't get the 'amber LED' which various guides tell me to press Vol Down at.
I'm using
Code:
fastboot boot recovery.img
to boot the phone into recovery and
Code:
fastboot flash recovery recovery.img
to flash it, which hasn't worked at all. All of theTWRP versions I have found around the place do not work at all - it stays at the SONY white boot up screen. I have seen other kernels in .zip files and was extracting them to flash the boot.img file but looking now that seems incorrect - how do I flash the .zip file? Maybe that's unrelated but I seem to be missing something there
At the moment, the only way I can use my phone is if I flash the firmware in flashmode, using Flashtool.
My steps, from stock, were:
get unlock code from sony
enable USB debugging
turn on "Enable OEM Unlock"
issue "adb reboot bootloader"
issue oem unlock command
reboot phone and confirmed "Bootloader Unlocked: YES"
issue "adb reboot bootloader"
Then what should I do? What other steps do I need to take to get from stock onto a custom ROM such as this one? Please tell me step-by-step (like i'm 5) and assume you're talking me through it and I know nothing... because I am clearly missing some obvious step that nobody else here has struggled with.
Thanks heaps in advance for your help guys

[snip]

TimTams said:
Hi all,
I've followed various sets of instructions for installing a recovery onto my E6653. I was able to get recovery to boot successfully using the sony-recovery-z5.img found HERE, but it can't see, mount, format or wipe my ext SD card at all in this recovery so I can't initiate the install of a ROM from it.
I've tried stacks of other recoveries and boot images (kernels?), including:
[TWRP][E6653/E6603/E6633/E6683] 3.0.2 , all ROMs
[TWRP][E6653/E6603] 2.8.7.0 and Stock Rootable Kernel [2015-11-15]
[KERNEL][E6653/E6633/E6683] Zach's Kernel Playground for Z5, WIP (work in progress)
https://www.gizdev.com/sony-xperia-z5-e6653e6603-unlock-bootloader-install-twrp-recovery-root/
but none of these work - the phone will no longer boot after flashing boot.img (stuck at sony logo) and the recoveries will not launch. I'm using
Code:
fastboot flash boot boot.img
to write the boot images and
Code:
fastboot boot recovery.img
to boot the phone into recovery. All of the other TWRP versions I have found around the place do not work at all - it stays at the SONY white boot up screen. I have seen other kernels in .zip files and was extracting them to flash the boot.img file but looking now that seems incorrect - how do I flash the .zip file? Maybe that's unrelated but I seem to be missing something there
At the moment, the only way I can use my phone is if I flash the firmware in flashmode, using Flashtool.
My steps, from stock, were:
get unlock code from sony
enable USB debugging
turn on "Enable OEM Unlock"
issue "adb reboot bootloader"
issue oem unlock command
reboot phone and confirmed "Bootloader Unlocked: YES"
issue "adb reboot bootloader"
Then what should I do? What other steps do I need to take to get from stock onto a custom ROM such as this one? Please tell me step-by-step (like i'm 5) and assume you're talking me through it and I know nothing... because I am clearly missing some obvious step that nobody else here has struggled with.
Thanks heaps in advance for your help guys
Click to expand...
Click to collapse
I don't think your bootloader is unlocked because:
1: your device won't boot after flashing an image.
2: your rooting status says: bootloader unlock allowed.
(if unlocked, it says rooting status: bootloader unlocked)
Yes means it can be unlocked.
Unless you unlocked already and use drm fix because then it still shows yes but Im pretty sure your bootloader isn't unlocked.
BTW this thread belongs in Q&A section.
You can request a movement by hitting the small "!" triangle button underneath your post when viewing this page in a browser.
Sent from my E6653 using XDA-Developers mobile app

Thanks heaps - that sounds like it might be the issue, I'll have a play and post back here. It would explain why I've had so much trouble with what seems like a simple task
langeveld024 said:
I don't think your bootloader is unlocked
...
Click to expand...
Click to collapse
EDIT:
It looks like this was done correctly.
{
"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"
}
I'm not sure I want to go and have another crack at flashing a recovery... I couldn't seem to get any of them to work.

I've just followed this guide to installing recovery and it hasn't worked... I still just get stuck at the sony logo. Any ideas why? How do I know the recovery image linked is correct for my phone?
http://www.digitbin.com/unlock-bootloader-flash-twrp-root-sony-xperia-z5/

OK, I got recovery installed! Thanks to this guy: http://forum.xda-developers.com/xperia-z5/help/boot-flashmode-fastboot-t3457818
mentions what no other guide mentions...
I need to have a custom kernel before I can flash recovery (first mention of this I've seen)
The kernel I flash needs to match the firmware I have installed
With that, I had instant success.
EDIT:
And now I have managed to get a custom ROM installed at last My procedure was, for anyone that be stuck in a similar way:
If your phone already won't boot:
Download Flashtool and install it. I have mirrored it here as all the sources I found were very slow: http://noobs.wtf/uploads/flashtool-0.9.22.3-windows.exe
Go to the 'drivers' folder inside your Flashtool install directory (default C:\Flashtool\drivers) and follow the instructions to install the "flashmode" driver
Select XperiFirm within Flashtool and download the correct firmware for your phone - mine was "Xperia Z5 > Sumire > E6653 > Australia > Telstra AU > 32.2.A.0.253 / R5C"
Turn off your phone and boot it in flashmode - Insert USB while holding vol down until the LED is green
Once Flashtool has finished downloading your firmware, go back to the main screen and click the 'lightning' button to flash your phone with the new firmware that should show up in the list - leave all the options unticked. Wait for it to say 'complete - un plug your phone'
Your phone should now boot successfully
To install a custom ROM:
I was not able to access my SD card in any version of TWRP - so copy your ROM to the internal storage of your phone. I used v1.5.0 of THIS ROM successfully.
Copy v36 (or newer) of THIS KERNEL .zip file to your internal storage as well. (v32 and higher are in the google docs link) NOTE this must match the firmware version - v36 was the one I used because, as above, I re-flashed my phone with 32.2.A.0.253 from Flashtool. The appropriate versions are listed on that link
[*]Also download TWP-3.0.2-2-E6653.img (or newer equivalent) from that same link.
[*]Follow the instructions HERE to unlock your bootloader (and make sure your fastboot drivers are installed correctly)
[*]Reboot your phone and re-enter fastboot mode (vol-up while plugging in USB) you can issue the command 'fastboot oem unlock' and it will return 'already rooted' if it has been done correctly
[*]Now with your phone in fastboot mode, issue the commands "fastboot flash recovery TWP-3.0.2-2-E6653.img" then "fastboot boot TWP-3.0.2-2-E6653.img" to install and then boot into TWRP recovery
[*]Once in TWRP, go to "Install" and install first the Kernel, then install the ROM, making sure to do the wipes
For me, this completed the process of installing a custom ROM I was stuck on the lack of info around installing the kernal and whatnot.

TimTams said:
I was stuck on the lack of info around installing the kernal and whatnot.
Click to expand...
Click to collapse
But the info was right here on the forum's, wasn't it?
Sent from my E6653 using XDA-Developers mobile app

langeveld024 said:
But the info was right here on the forum's, wasn't it?
Sent from my E6653 using XDA-Developers mobile app
Click to expand...
Click to collapse
not in any of the guides that outline how to go from "stock" to one of the custom ROMs, no.

TimTams said:
not in any of the guides that outline how to go from "stock" to one of the custom ROMs, no.
Click to expand...
Click to collapse
Hmm maybe u should suggest the OP of those threads to add this information then.
I personally never read those guides lol[emoji14](not anymore at least, at some point I was learning about this like you as well, we all had to learn)
Sent from my E6653 using XDA-Developers mobile app