[GUIDE] Unlock/Root/Flash for HTC One XL - AT&T, Rogers HTC One X, Telstra One XL

[GUIDE] Unlock/Root/Flash for HTC One XL - AT&T, Rogers HTC One X, Telstra 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

Related

Phone Kinda Bricked

I have HTC Panache. I tried to install Ice Cream Sandwitch on my Phone
http://forum.xda-developers.com/showthread.php?t=1341847&page=17
The phone rebooted using ROM manager. it was extracting. I believe I pressed the power button. Anyways, the phone rebooted and now its just showing the MI logo and a sound that indicates that its a new rom but doesnot goes futher..
I tried to reboot using adb . But when I go into the Clockwork mod recovery, it just shows a hat with a yellow round arrow underneath it. My Clock work mod recovery version is 5.0.2.0

Just discovered
My version is as follows. Is it some thing to be worried ?
<6>[ 6.091674] mmcblk0: mmc0:0001 M4G2DE 2.10 GiB

Your recovery is corrupt. Assuming you have s-off, you can try flashing cwm recovery through bootloader via adb. Search the forum and you will find instructions on how to do that.

chem.manish said:
Your recovery is corrupt. Assuming you have s-off, you can try flashing cwm recovery through bootloader via adb. Search the forum and you will find instructions on how to do that.
Click to expand...
Click to collapse
find the recovery file, rename to "recovery.img" for easy typing, and put it in your adb tools folder.
reboot your phone into bootloader (volume down/power), and connect to computer. when connected to the computer, the phone should automatically switch into fastboot USB mode
type:
Code:
fastboot devices
to make sure device is seen. if it is, proceed. if not, get the drivers.
TYPE THIS EXACTLY!!!
Code:
fastboot flash recovery recovery.img
it should give you a # of bytes sent or something like that
then type
Code:
fastboot reboot recovery
and welcome back to clockworkmod recovery!
if this helped, hit the thanks button.

saranhai said:
find the recovery file, rename to "recovery.img" for easy typing, and put it in your adb tools folder.
reboot your phone into bootloader (volume down/power), and connect to computer. when connected to the computer, the phone should automatically switch into fastboot USB mode
type:
Code:
fastboot devces
to make sure device is seen. if it is, proceed. if not, get the drivers.
TYPE THIS EXACTLY!!!
Code:
fastboot flash recovery recovery.img
it should give you a # of bytes sent or something like that
then type
Code:
fastboot reboot recovery
and welcome back to clockworkmod recovery!
if this helped, hit the thanks button.
Click to expand...
Click to collapse
Correction, first command should be-
fastboot devices

Ok. I did flashboot the recovery. then it installed the rom automatically. Now I am on MyTouch4g T-Mobile ROM. I Installed ROM Manager but following are the errors now
Flash ClockWorkMod :- An Error occured while attempting to run privileged command !
Same happens when I click on Install ROM. In start, it says that No Super User found. Though, I am sure I rooted the phone. Thats why I have a new ROM on my phone
--
When I write Fastboot it says, it is not a recognizable command

ahaseeb said:
Ok. I did flashboot the recovery. then it installed the rom automatically. Now I am on MyTouch4g T-Mobile ROM. I Installed ROM Manager but following are the errors now
Flash ClockWorkMod :- An Error occured while attempting to run privileged command !
Same happens when I click on Install ROM. In start, it says that No Super User found. Though, I am sure I rooted the phone. Thats why I have a new ROM on my phone
--
When I write Fastboot it says, it is not a recognizable command
Click to expand...
Click to collapse
Do you have superuser installed on your phone?
Do you have adb installed on your computer?
Sent from my HTC Glacier Sense 3.5 using xda premium

saranhai said:
Do you have superuser installed on your phone?
Do you have adb installed on your computer?
Sent from my HTC Glacier Sense 3.5 using xda premium
Click to expand...
Click to collapse
He sure has adb if he sees that privileged command error.
I would suggest now you find full pd15img.zip which has rom, recovery and flash thru bootloader. Once you are up and running stock, re-root the device.

He has S-OFF, but he doesn't have engineering bootloader. Which makes him unable to run fastboot commands. That's the standard bad news for those who root and don't flash engineering bootloaders.
But, his phone boots to adb, which is good enough - so the engineering bootloader could be flashed by adb, or at least the recovery could be flashed by adb. The last one can be done using flash_image executable while in adb root shell.

Off topic but what the engineer bootloader what the differences between are regular boot loader ?
Sent from my Tweaked out RCmix3D myTouch 4G via xda premium !

Tez MyTouch said:
Off topic but what the engineer bootloader what the differences between are regular boot loader ?
Sent from my Tweaked out RCmix3D myTouch 4G via xda premium !
Click to expand...
Click to collapse
eng bootloader you can use fastboot with, and you can change more stuff.
correct me if i'm wrong...

chem.manish said:
He sure has adb if he sees that privileged command error.
I would suggest now you find full pd15img.zip which has rom, recovery and flash thru bootloader. Once you are up and running stock, re-root the device.
Click to expand...
Click to collapse
You mean I should follow all the steps of rooting once again ?
Jack_R1 said:
He has S-OFF, but he doesn't have engineering bootloader. Which makes him unable to run fastboot commands. That's the standard bad news for those who root and don't flash engineering bootloaders.
But, his phone boots to adb, which is good enough - so the engineering bootloader could be flashed by adb, or at least the recovery could be flashed by adb. The last one can be done using flash_image executable while in adb root shell.
Click to expand...
Click to collapse
So you mean, I should install bootloader using adb again ?
What was the command flash ... ?
When I type reboot recovery, it goes into the bootloader and a phone appears.. Thats all

When your phone is booting, run "adb shell" and watch. The "#" sign should appear.
If the shell stays and doesn't drop out when the phone is bootlooping (the sign is still there after 2-3 minutes) - you're good to go.
WARNING: YOU'LL BE FLASHING BOOTLOADER. WRONG MOVE - AND YOUR PHONE IS A BRICK.
Since you're already running a rooted OS, "adb shell" should present you with "#" sign.
The thread below has steps to flash engineering bootloader. Don't use those steps, but download the bootloader and check the md5sum (do me a favor and don't ask how to do it, simple googling will spill you 200000000 answers). Put the bootloader into your ADB directory.
http://forum.xda-developers.com/showthread.php?t=858996
Direct link to the file: http://www.megaupload.com/?d=NN5726Z8
md5sum: df4fd77f44993eb05a4732210d2eddc6
Now, to flash engineering bootloader while you're in the ADB root shell, use these steps:
Open Windows' Command prompt in the ADB directory (DO NOT enter ADB shell yet!).
Type (EXACTLY as below):
adb push hboot_dhd.nb0 /data/local/
adb shell
("#" should appear)
cd /data/local/
dd if=hboot_dhd.nb0 of=/dev/block/mmcblk0p18
You should see something like: 2048 bytes in 2048 bytes out 1048576 bytes copied blah blah blah
Now reboot into bootloader, see that you have 0.85.2007 version, enter FASTBOOT mode (select FASTBOOT with volume keys and press power button), and from there you can follow the suggestion above to fastboot flash the recovery, or anything you want.
And on the side note: you won't see any ICS in MIUI that you've attempted flashing. You should have read the thread - it clearly says "all the ICS changes are under the hood, visually it's just a regular MIUI".

I do not see # sign when i type adb shell..
Means I have to root again ?

What do you see? "$"?
In that case, try typing "su" and see if it brings you root.
If it doesn't - you can try to achieve temp root like when downgrading, using fr3vo.
For instructions - section "gain temp root" from the following thread:
http://forum.xda-developers.com/showthread.php?t=1178912
In case it doesn't help you - you'll need to apply PD15IMG in bootloader as suggested to bring you back to stock, and then re-root.

this link returns me error
an error occured while running the exploit <-1> errno 25..
Probbaly because its already exploited may be ?
I am stuck and confused..
Dont know what to do :S

Jack_R1 said:
In case it doesn't help you - you'll need to apply PD15IMG in bootloader as suggested to bring you back to stock, and then re-root.
Click to expand...
Click to collapse
This.
Please google up "mt4g return to stock" or "mt4g apply pd15img", I'm sure there are enough guides to find.

Though applying pd15img.zip is pretty simple, there is even a simpler way for you to return to stock - just find the panache ruu executable in dev section, connect your phone to pc and run that exe.

Is this the file you are referring to ?
http://dl.dropbox.com/u/25823285/RUU...466_signed.exe
I have heard about phones being bricked. So do I need to be extra careful ?

It worked. Great. Now I am on HTC Sense. 2.1 !
Sounds great
Now should i start from zero again ?

[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!

[Q] Boot loop after failed boot.img replacement

Edit: solution to the problem in post #4
I have accidentally replaced my boot.img with fastboot - now the phone is stuck in a boot loop/freeze
the bootloader is unlocked
it is S-ON
it is an unlocked (not branded phone)
running twrp 2.6.0.0
both adb and fastboot appear to work
the phone is not rooted (that was where the problem started...)
I have access to hboot and recovery, but that is it
I have erased everything (cache, system, dalvik, sd) several times and tried a number of suggestions found on other threads describing similar problems.
I can't get access to the SD card from a PC, and fastboot flash or adb push both fail to transfer a stock RUU (JmzM4StockRootedDeOdex-WWE-1.22.401.1.zip) to the phone.
I have replace the kernel (and flashed the appropriate boot.img with it) to get out of the boot loop.
Any suggestion would be greatly appreciated! gettting desperate now...
Thanks, K
----------
the recovery screen reads:
***TAMPERED***
***UNLOCKED***
M4_UL PVT SHIP S-ON RL
HBOOT-2.21.0000
RADIO-1.22.40e.00.07
OpenDSP-v15.2.0268.0819
OS-1.40.401.1
eMMC-boot 1024MB

ilchkai said:
I have accidentally replaced my boot.img with fastboot - now the phone is stuck in a boot loop/freeze
the bootloader is unlocked
it is S-ON
it is an unlocked (not branded phone)
running twrp 2.6.0.0
both adb and fastboot appear to work
the phone is not rooted (that was where the problem started...)
I have access to hboot and recovery, but that is it
I have erased everything (cache, system, dalvik, sd) several times and tried a number of suggestions found on other threads describing similar problems.
I can't get access to the SD card from a PC, and fastboot flash or adb push both fail to transfer a stock RUU (JmzM4StockRootedDeOdex-WWE-1.22.401.1.zip) to the phone.
I have replace the kernel (and flashed the appropriate boot.img with it) to get out of the boot loop.
Any suggestion would be greatly appreciated! gettting desperate now...
Thanks, K
----------
the recovery screen reads:
***TAMPERED***
***UNLOCKED***
M4_UL PVT SHIP S-ON RL
HBOOT-2.21.0000
RADIO-1.22.40e.00.07
OpenDSP-v15.2.0268.0819
OS-1.40.401.1
eMMC-boot 1024MB
Click to expand...
Click to collapse
Hi! If you still need help, PM me and we'll get it sorted, no problem.....

nelvinchi said:
Hi! If you still need help, PM me and we'll get it sorted, no problem.....
Click to expand...
Click to collapse
excellent - thanks, pm sent

Here is the solution to the above problem, no guarantees – just thought I share it here if anyone else is in the same predicament… I was walked through this by nelvinchi - many thanks for that !!!!
(n.b. I can't post urls yet as I am a noobie here, so that you will need to find the required files in the forum somewhere - maybe someone can leave links to the appropriate files in a post below)
Required files:
1. ABD (get the smaller version from the forum)
-> download this and extract to a folder called c:\adb\
2. Updated Super SU "UPDATE-SuperSU-v1.86.zip"
3. Rom (Stock2.12.401.1Deodex(tr1gg3r84).zip)
-> SuperSU and Rom, into the same folder as above (c:\adb\)
(4. TeamWinRecoveryProject recovery, here version 2.6.0.0)
Procedure:
[NB.: I had access to bootloader (unlocked) & recovery (twrp 2.6.0.0); the phone was S-ON]
Open a command prompt from the folder (shift+right click somewhere in the window and choose “open command window here”, or WIN+R and enter cmd and press enter and navigate to the folder where the files and adb are located)
Boot phone to recovery
Go to the mount menu, check system and data [data was not selectable, thus I had to: Go to wipe menu, Format data, Type yes, after that reboot to recovery, and mount menu, check system and data…]
Back to main menu
Plug your phone into computer (mine was plugged in all along, so no worries)
In the cmd prompt (on PC) type: adb devices [phone should be found and indicated by the serial number and the status, in this case it should say recovery after the number – proceed if phone is found]
Type: adb push Stock2.12.401.1Deodex(tr1gg3r84).zip /sdcard/
[there is no indication of progress when pushing, just be patient – it will take a few minutes. And, just in case – if you need to interrupt/cancel the push process it can be done with Ctrl+c]
Type: adb push UPDATE-SuperSU-v1.86.zip /sdcard/
On the phone, in recovery, Go to install
Choose the NEW rom (Stock2.12.401.1Deodex(tr1gg3r84).zip)
Choose add more zips and add the SuperSU zip
Confirm flash
When done, DON'T reboot, go back, reboot menu, reboot recovery
On the PC, open the ROM zip, and extract boot.img to the folder (c:\adb\) [this will need you to have 7zip or Winrar or similar installed on your computer]
Reboot menu and select Reboot bootloader
Select fastboot (fastboot should be indicated by fastboot USB)
On the PC type fastboot flash boot boot.img
Choose bootloader, then recovery
In recovery: Go to wipe, Advanced wipe, Check cache and dalvik, and wipe!
Go to Reboot menu, and Reboot system
Now, don't panic – it will take some time to do its thing… the phone should be fine after that and normal setup process should start.
!!! Massive thanks to nelvinchi, who walked me through this process!!!

Links
A little late, but:
SuperSU: http://download.chainfire.eu/372/SuperSU/UPDATE-SuperSU-v1.86.zip?retrieve_file=1
Stock Flashable zip: https://mega.co.nz/#!8d0jhQTS!N2V5KTty4spxzNOwU-43vzqd3BF_ektVbH_TuHec26c
TWRP: http://forum.xda-developers.com/showthread.php?t=2418938
ADB: http://forum.xda-developers.com/showthread.php?p=42407269 (i think you ment this one, right?)
Yaaay, fixed my mini. Thx for these instructions!
:laugh:

ilchkai said:
Here is the solution to the above problem, no guarantees – just thought I share it here if anyone else is in the same predicament… I was walked through this by nelvinchi - many thanks for that !!!!
(n.b. I can't post urls yet as I am a noobie here, so that you will need to find the required files in the forum somewhere - maybe someone can leave links to the appropriate files in a post below)
Required files:
1. ABD (get the smaller version from the forum)
-> download this and extract to a folder called c:\adb\
2. Updated Super SU "UPDATE-SuperSU-v1.86.zip"
3. Rom (Stock2.12.401.1Deodex(tr1gg3r84).zip)
-> SuperSU and Rom, into the same folder as above (c:\adb\)
(4. TeamWinRecoveryProject recovery, here version 2.6.0.0)
Procedure:
[NB.: I had access to bootloader (unlocked) & recovery (twrp 2.6.0.0); the phone was S-ON]
Open a command prompt from the folder (shift+right click somewhere in the window and choose “open command window here”, or WIN+R and enter cmd and press enter and navigate to the folder where the files and adb are located)
Boot phone to recovery
Go to the mount menu, check system and data [data was not selectable, thus I had to: Go to wipe menu, Format data, Type yes, after that reboot to recovery, and mount menu, check system and data…]
Back to main menu
Plug your phone into computer (mine was plugged in all along, so no worries)
In the cmd prompt (on PC) type: adb devices [phone should be found and indicated by the serial number and the status, in this case it should say recovery after the number – proceed if phone is found]
Type: adb push Stock2.12.401.1Deodex(tr1gg3r84).zip /sdcard/
[there is no indication of progress when pushing, just be patient – it will take a few minutes. And, just in case – if you need to interrupt/cancel the push process it can be done with Ctrl+c]
Type: adb push UPDATE-SuperSU-v1.86.zip /sdcard/
On the phone, in recovery, Go to install
Choose the NEW rom (Stock2.12.401.1Deodex(tr1gg3r84).zip)
Choose add more zips and add the SuperSU zip
Confirm flash
When done, DON'T reboot, go back, reboot menu, reboot recovery
On the PC, open the ROM zip, and extract boot.img to the folder (c:\adb\) [this will need you to have 7zip or Winrar or similar installed on your computer]
Reboot menu and select Reboot bootloader
Select fastboot (fastboot should be indicated by fastboot USB)
On the PC type fastboot flash boot boot.img
Choose bootloader, then recovery
In recovery: Go to wipe, Advanced wipe, Check cache and dalvik, and wipe!
Go to Reboot menu, and Reboot system
Now, don't panic – it will take some time to do its thing… the phone should be fine after that and normal setup process should start.
!!! Massive thanks to nelvinchi, who walked me through this process!!!
Click to expand...
Click to collapse
I followed these instrutions to a T but im still getting boot loopat the HTC screen
I am Unlocked bootloader
S-Off
cid-CWS__001
hboot 2.19.0000
radio 1.19.40d.00.14
any suggestion?

please help
romy134 said:
I followed these instrutions to a T but im still getting boot loopat the HTC screen
I am Unlocked bootloader
S-Off
cid-CWS__001
hboot 2.19.0000
radio 1.19.40d.00.14
any suggestion?
Click to expand...
Click to collapse
I'm having the same problem.
I've followed those instructions over and over with different roms but TWRP always tells me that there is no OS installed when I do the final reboot. I am stuck at the white HTC screen and can't get any rom to load up. Please help.
This is what my bootloader says:
--TAMPERED--
--UNLOCKED--
M4_UL PVT SHIP S-ON RL
HBOOT-2.22.0000
RADIO-1.25.40G.00.19
OPENDSP-V19.2.0268.0927
OS-3.10.502.3
eMMC-boot 1024mb
I can flash recoveries and boot.img. ADB works to push roms into /sdcard/, can also sideload. I'm suspecting my filesystem/ partition data is all screwed but but can't figure out why Roms won't load.
I got the phone yesterday and it was untouched, stock. I tried to follow this guide (http://forum.xda-developers.com/showthread.php?t=2789272) to get it rooted and install a custom rom. I got stuck at getting S-OFF. rumrunner was giving me the "Fatal: download latest package" error. I also could not get su in the shell to try firewater. At this point I was reading that people had luck getting S-OFF after installing JmzM4StockRootedOdex-WWE-1.22.401.1 custom rom and kernel. I tried to do that but I wasn't sure what I was doing and ended up with no OS and a bootloop at the white HTC screen. I have a bit of Android experience from messing with the HP touchpad tablet but I'm rusty and this phone has me beat right now.
Thanks for your help.

...
try replacing TWRP with an older version (mine was 2.6.0.0) and reset/clear/delete/format everything from there and restart the process outlined above
and apparently S-Off is pointless and very risky on this model, there is no reason to do it - it will just cause problems
good luck and I hope some else who has actual knowledge about this will get back to you

ilchkai said:
try replacing TWRP with an older version (mine was 2.6.0.0) and reset/clear/delete/format everything from there and restart the process outlined above
and apparently S-Off is pointless and very risky on this model, there is no reason to do it - it will just cause problems
good luck and I hope some else who has actual knowledge about this will get back to you
Click to expand...
Click to collapse
Thanks.. I've been using TWRP 2.7.1.0 because I read that I have the newer partion scheme with HBOOT 2.22 but I'm not really sure.
When I try TWRP 2.7.1.1 ADB doesn't work and I get a different /sdcard/ than in 2.7.1.0. Not sure what's going on there either.
The only reason I tried S-off is because I blindly followed that guide on how to get the HTC one mini up to date and that was the 2nd step. I should have skipped it and paid more attention to the custom rom flashing aspect.
I'll try TWRP 2.6.0.0 as I don't have many other options at this point.. I also tried to use CWM recovery but it couldnt flash a rom either.
Thanks for your input.

Can't Update to 11.0-XNPH38r Incremental (Chinese OPO)

So I bought a Chinese OnePlus One, and it came pre-installed with CM 11 version 11.0-XNPH33r.
Connected to wifi, and got the system update for 11.0-XNPH38r Incremental, so I click download and install.
It reboots phone, then it loads ColorOS recovery looking screen with Chinese written on it and a green loading bar, then The CM splash icons comes back and loads. (alien looking guy with an arrow circling around his head)
After all that, I go to check the version and I'm still stuck at 11.0-XNPH33r!
I tried manually doing it from ColorOS recovery with 11.0-XNPH38r Incremental zip file, it installs about 3/4 of the way and then fails.
My Kernel Version is : 3.4.0-cyanogenmod-g0ad30e5
My ColorOS Recovery Version is : 1.2 (Rooted)
I've been looking around the forums, and I see people manually updating using TWRP which I don't have.
Can someone please help me, and if you have a solution can you please give me a step by step direction since I'm new to flashing/rooting and this phone.

I have a guide thread here:
http://forum.xda-developers.com/showthread.php?t=2839471
It contains instructions on how to unlock your bootloader and install TWRP recovery (sections 1 and 2). Before doing anything though you should check the status of your bootloader because it might already be unlocked. You'll need to follow the instructions at the top of the guide to install your phone drivers and also adb/fastboot via the Android SDK. Once you have done that you can boot your phone into fastboot mode (hold power + volume up), connect your phone to your PC via usb cable, open a command prompt from your fastboot folder (shift + right click anywhere within the foler, then select open command prompt here), and issue this command:
Code:
fastboot oem device-info
Please post the results here.

Thanks man, I'll try that out.

timmaaa said:
I have a guide thread here:
http://forum.xda-developers.com/showthread.php?t=2839471
It contains instructions on how to unlock your bootloader and install TWRP recovery (sections 1 and 2). Before doing anything though you should check the status of your bootloader because it might already be unlocked. You'll need to follow the instructions at the top of the guide to install your phone drivers and also adb/fastboot via the Android SDK. Once you have done that you can boot your phone into fastboot mode (hold power + volume up), connect your phone to your PC via usb cable, open a command prompt from your fastboot folder (shift + right click anywhere within the foler, then select open command prompt here), and issue this command:
Code:
fastboot oem device-info
Please post the results here.
Click to expand...
Click to collapse
TY for you help. I manage to get a custom recovery (TWRP), but I still can't update past 33R, when I update I get "E:Error executing updater binary in zip '/cache/cm-bacon-3628510d76-to-ac1ccf7921-signed.zip
I also have this phone SuperSU fully rooted I think

TheOneinNeed said:
TY for you help. I manage to get a custom recovery (TWRP), but I still can't update past 33R, when I update I get "E:Error executing updater binary in zip '/cache/cm-bacon-3628510d76-to-ac1ccf7921-signed.zip
I also have this phone SuperSU fully rooted I think
Click to expand...
Click to collapse
Go to section 8 of my guide and flash the stock images. Make sure you remove the -w of the last command though or it'll wipe all your user data.
Transmitted via Bacon

timmaaa said:
Go to section 8 of my guide and flash the stock images. Make sure you remove the -w of the last command though or it'll wipe all your user data.
Transmitted via Bacon
Click to expand...
Click to collapse
Thanks man. I actually tried the flashing of 44s on the guide you sent me and it worked. Sorry for my last reply. You've been a great help and my phone is up to date.
Two last question if you don't mind. When the new update comes, can I install through Settings> About Phones> System Updates
or do I have to do something similar to the flashing I just did
after flashing my custom recovery is gone (TWRP) and the Cyanogen Mod Recovery took its place. Should I leave it like that or get TWRP and if TWRP is the answer, do I use the same method I did installing the custom recovery?

You should now have no problems receiving automatic updates through the settings menu. You can leave the stock recovery if you want to, or you can flash TWRP again. If you don't intend on flashing any custom ROMs or mods then the stock recovery should suit you just fine. Flashing a recovery is done via fastboot.
Code:
fastboot flash recovery twrp-2.8.4.1.img
(where the recovery filename is twrp-2.8.4.1.img)

timmaaa said:
You should now have no problems receiving automatic updates through the settings menu. You can leave the stock recovery if you want to, or you can flash TWRP again. If you don't intend on flashing any custom ROMs or mods then the stock recovery should suit you just fine. Flashing a recovery is done via fastboot.
Code:
fastboot flash recovery twrp-2.8.4.1.img
(where the recovery filename is twrp-2.8.4.1.img)
Click to expand...
Click to collapse
Thank you for your time and effort to help.
I appreciate it a lot. Thanks again!

The Ultimate guide to flash and root Xperia L (aka, taoshan)

This thread will guide you to flash a custom recovery, Root the device, flash custom ROMs. Firstly, read the entire post and then start your work.
I am a noob. But I have a little experience of rooting and flashing. This device gave me nightmares which are less than as compared to the Xperia Sola which I bricked some years back.
My device has a problem. It does not help install twrp with the traditional ways we know like we can see in the Official TWRP website using "dd" method, the Cyanogenmod link using fastboot commands, the Flashify method, the RecoveryApp method whose apk I never found and the Recovery Installer Utility.
I came to know that either my phone don't have the recovery partition or the phone is overriding all the commands.
Using fastboot commands would give the error like in this post.
Using Flashify would tell me there's no recovery partition found. Rashr would complete the flash process but after booting to recovery, there was no TWRP, just the stock Android recovery.
If you read carefully on the twrp page of XL, there's a line which caught my attention late enough.
It means that TWRP may not work on your device unless you install other custom software as well.
Click to expand...
Click to collapse
Flashing custom kernels with flashtool is easy and they come with recovery pre-installed and lots of amazing stuff, but they won't do any good with the stock ROM. I've tried the Extended stock kernel, the Phantom Kernel and the Thunderzap 4.15.
After surfing the web and forums of other devices, I found that there is a chance I can fix things by updating/repairing software via PC Companion. But something happened and repair also failed.
I can't tell the reason why this happened. And I didn't store the logs. But with trial and error I found some workarounds.
Actual Methods start here
Rooting the device
If you only want to root your device for various reasons, then you will need nothing but a Rootkit. Check out this post about Rooting Xperia L.
But if you are planning to install custom ROMs for your device, then skip this rooting step. It won't be necessary for this condition.
Flashing custom recovery
*Try this method only if above-mentioned method fails*
1. Download TWRP 3.2.1 img. The 3.2.2 and 3.2.3 versions work perfectly but they caused the screen to flicker like hell on my device. Rename the file to 'twrp.img'
2. Download and install adb and fastboot drivers system-wide.
3. Connect your device to PC via USB cable and enabling USB-debugging mode.
4. Open Windows Powershell/Command Prompt in the twrp download directory by pressing Shift and clicking right mouse button.
5. Use fastboot command on stock ROM without root and Unlocked Bootloader. Instead of flashing twrp image to recovery, flash to boot. Use the code:
Code:
adb devices
adb reboot fastboot
Wait for device to boot into fastboot mode. A blue LED will flash when connected.
Code:
fastboot flash boot twrp.img
fastboot reboot
After reboot, don't boot to system. Boot to recovery by pressing volume up repeatedly when pink LED glows. Stop when device vibrates and LED color changes
Flashing custom ROMs
Once the recovery is installed, everything becomes easy. you can find different custom ROMs on the device page here on XDA.
My favorite one is The resurrection Remix Nougat. It is stable enough to be your daily driver. You can head to that page and follow their instructions. But I will also provide steps here.
When in TWRP after the last step, move the downloaded zip file of the ROM and GApps you want to install to the storage of the device by simply connecting via USB.
After that, in TWRP click on Wipe->Advanced->Tick on System, Cache, Dalvik cache. Then Do swipe to begin wipe.
After wipe, go back to main menu. Tap on install, select from the list the ROM zip. then tap on Add more zips and select the GApps zip and then Swipe to start flashing.
After flashing, reboot to system. The first boot takes time. Don't panic if it won't boot.
Install TWRP to FOTAKernel
After booting to your new ROM, you can install the TWRP to your FOTAKernel.
This can be done as following:
Get the downloaded TWRP img file and push it to the device using command line. Open command prompt in the TWRP directory and type,
Code:
adb root
adb wait-for-device
adb push twrp.img /tmp/twrp.img
Now extract the TWRP image to the FOTA partition code,
Code:
adb shell dd if=/tmp/twrp.img of=/dev/block/platform/msm_sdcc.1/by-name/FOTAKernel
Now reboot to recovery
Code:
adb reboot recovery
Note that custom ROMs often come with Root access inbuilt. If your ROM happened to be not, and your ROM is based on Lollipop or later version of Android, you can root with Magisk. Just read carefully before proceeding.
Comments are welcome!

Hi.
I'm following this thread and I'm stuck on the fifth step "... flash to boot. Use the code:
adb devicesadb reboot fastboot "
I think my Sony Xperia L C2105 does not have the fastboot mode.
Here's what I did:
Drivers for Xpleria L are installed.
The bootloader is unlocked (I think!)
1 - installed 15-second ADB
2 - open Windows power shell
3 - Command: adb devices
Response is: "List of devices attached: ZH8001ADB3 device"
4 - Command: adb reboot fastboot
Response is: long pause, phone booted but in normal mode, and light is red ...!
5 - Command: fastboot flash boot twrp.img;
Response is: "<waiting for device>";
- phone still running in normal mode and the light is red.
- few minutes later, the phone is charging with green light present.
I think the phone is rooted.
I used the code provided by the Sony website to unlock the bootloader.
Using the Root Checker Basic app, I get the info: "Congratulations! Root access is properly installed on this device!"
But if I type in the dialer *#*#7378423#*#*, and go to Service info > Configuration > Rooting status is "Boootloader unlock allowed" !!
Is that why it does not work?
I tried switching it off and doing Boot into Xperia L Fastboot Mode Using HARDWARE BUTTONS, but the phone is dark, with no picture, and the led turns blue.
Using the command:
PS C: \ adb> adb devices
List of devices attached
PS C: \ adb>
I've been trying to do that for a few days now and I still have not managed it, even using other advice.
Can someone tell me what to do?
Thank you in advance.

Everterra said:
Hi.
I'm following this thread and I'm stuck on the fifth step "... flash to boot. Use the code:
adb devicesadb reboot fastboot "
I think my Sony Xperia L C2105 does not have the fastboot mode.
.......
Click to expand...
Click to collapse
1. When in fastboot mode, you should type in cmd "fastboot devices" to check the device connectivity. If you can't, then connect using hardware keys.
2. Blue light indicates that you are in fastboot mode. If list of attached devices are blank, that means drivers are not installed (properly). Connect your phone again in fastboot mode and check your drivers page, Win+X > M (I am assuming you must be on windows). There must be a tiny yellow triangle on your device's name. Right click on it and uninstall it and remove device. Try again installing drivers from the flashtool's folder. Disable driver signature enforcement if you are having trouble going the straight way.
3. Your bootloader is still locked because if it had unlocked then the message displayed would have been, "Bootloader Unlocked: Yes" or something like that. Try flashing your stock ROM via Flashtool. Wipe cache and data while flashing. After flashing stock Rom, try unlocking bootloader again. I believe you are using Flashtool.
4. If you are rooted, then you must have any SuperSU app installed on your device. And it's all good even if you are rooted.

Database Info

welcome