[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
Hi all,
I'm trying to save a relative's HTC One S which got its internal storage wiped.
Currently I can access Hboot, fastboot, and recovery (that's it) but I get the error in the attachment when I'm in fastboot USB
I'm unable to mount the internal storage or flash a new recovery too.
Information about the phone:
*** UNLOCKED ***
VLE PVT SHIP S-ON RL
HBOOT-1.13.0000
RADIO-0.17.31501S.10_2
OpenDSP-v28.1.0.32.0504
eMMC-boot
Apr 20 2012, 15:14:18
TWRP Version 2.5.0.0
Any help is appreciated!
Thanks!
In fastboot usb do you have fastboot command recognize the device? If you issue "fastboot devices" what you get?
Sent from nowhere over the air...
Rapier said:
In fastboot usb do you have fastboot command recognize the device? If you issue "fastboot devices" what you get?
Sent from nowhere over the air...
Click to expand...
Click to collapse
When I type fastboot devices nothing appears.
remove old htc drivers and htc sync too, download and install these latest drivers ( http://forum.xda-developers.com/showthread.php?t=2217396 ) , then try connect fastboot again . If nothing happens tell us.
if you use windows 8.1 try these, same procedure ( http://forum.xda-developers.com/showthread.php?t=2544146 )
beerfly said:
remove old htc drivers and htc sync too, download and install these latest drivers ( http://forum.xda-developers.com/showthread.php?t=2217396 ) , then try connect fastboot again . If nothing happens tell us.
if you use windows 8.1 try these, same procedure ( http://forum.xda-developers.com/showthread.php?t=2544146 )
Click to expand...
Click to collapse
I got it detected on another computer;
I relocked the bootloader with "fastboot oem lock" but now it doesn't enter recovery mode, and has *** SECURITY WARNING *** at the top of the screen
what exactly you did when the computer detected your phone, what steps and stuff you used.
beerfly said:
what exactly you did when the computer detected your phone, what steps and stuff you used.
Click to expand...
Click to collapse
Typed "fastboot devices" to see if the phone was connected
Typed "fastboot oem lock" to relock bootloader
Used WinDroid Universal HTC Toolkit to flash TWRP 2.7.0.0
And that's where I am now. Thanks!
065271538 said:
Typed "fastboot devices" to see if the phone was connected
Typed "fastboot oem lock" to relock bootloader
Used WinDroid Universal HTC Toolkit to flash TWRP 2.7.0.0
And that's where I am now. Thanks!
Click to expand...
Click to collapse
Bootloader need to be UNlocked when installing recovery, now you need to go back to stock, unlock re locked bootloader and then put recovery. Thats why the security messege appears.
beerfly said:
Bootloader need to be UNlocked when installing recovery, now you need to go back to stock, unlock re locked bootloader and then put recovery. Thats why the security messege appears.
Click to expand...
Click to collapse
Okay thanks for that! I got TWRP 2.6.1.0 installed (anything higher would cause a reboot loop) and have Internal SDcard mounted in recovery mode. Where do I go from here? I'm just looking to go back to a stock device (no more hassles)
Thanks again!
I guess find an RUU that matches your device. You can run a new RUU as well.
http://forum.xda-developers.com/showthread.php?t=2678700
That worked!
Thanks to everyone
Can you tell us what RUU you used?
Thanks!
A friend has given me his Desire S to fix what I originally thought was just a stuck power button that prevented it from starting up. But the button is now fixes and I've been trying the last few days to get it to start up.
What I have tried so far is to enter Recovery mode, but upon choosing it, the phone would just go to the HTC logo screen, fibrate once and then fibrate agian after a second or two for a few times and the screen would go blank. The same happens with normal bootup. It also seems that the phone is still running with the blank screen because I have to pull the battery to startup again.
I then tried to use the latest RUU (Android 4.0) from HTC but the phone is not recognized by the computer (I think it is because it didn't startup enough to be able to present itself to the computer). So I unlocked it and used fastboot (from Ubuntu as OS) to flash the recovery (recovery_signed.img) and boot (boot_signed.img) from the RUU. With this recovery and normal startup would remain at the HTC screen and wouldn't go blank as before - still fibrates a few times.
I also tried to rename the rom.zip to PG88IMG.zip and putting it on a SD and the bootloader does detect it, but presents the normal boot screen afterwards (I think it complains about it being incorrect - the display is too quick for me to see the error).
Now I also have a Desire S and made a backup of it before I installed a custom ROM. So I also tried the recovery.img that I have from this backup, but then recovery is stuck on the blank screen again.
Is there anything that I did wrong, missed or may not have tried yet? And how can I go about to fix it?
PHONE DETAILS (from bootloader screen)
*** UNLOCKED ***
SAGA PVT SHIP S-ON RL
HBOOT-2.00.0002
RADIO-3822.10.08.04_M
eMMC-boot
The PG88IMG wont work coz ur s-on. Ul need to extract the zip file and put the recovery.img in ur fastboot folder and then flash it from fastboot, volume down + power then select select fastboot then plug ur phone into pc and open a fastboot command window and type
fastboot flash recovery recovery.img
Also a ruu u run from fastboot and u need to relock ur bootloader.
(i dunno how all this is done using ubuntu but thats how on windows so im sure ul know or figure it out)
Ok, didn't know that I needed S-OFF for PG88IMG - thanks for pointing that out . I did flash the recovery (paragraph 3), it is just named `recovery_signed.img` and not 'recovery.img` - I assume that there isn't a difference between the two?
Do I open the RUU while in fastboot on the phone (after relocking) or do I run it from a fastboot command?
(On Ubuntu fastboot is installed as a program so I can call it after I CD to the extracted rom folder and I assume it is working since I didn't get any errors)
Pieter2627 said:
Ok, didn't know that I needed S-OFF for PG88IMG - thanks for pointing that out . I did flash the recovery (paragraph 3), it is just named `recovery_signed.img` and not 'recovery.img` - I assume that there isn't a difference between the two?
Click to expand...
Click to collapse
Well it depends, could be 4ext recovery, CWM, or TWRP. But as far as the name, could be called peterpan.img and it wouldnt matter haha
Pieter2627 said:
Do I open the RUU while in fastboot on the phone (after relocking) or do I run it from a fastboot command?
Click to expand...
Click to collapse
Yh boot ur phone into fastboot, connect it to pc, relock bootloader and then run ruu. The ruu should be exe file so just double click it to run.
Ok, relocked it and went into fastboot mode and then opened the RUU, but was not recognized. Then followed this (droid-now.com/2013/10/fix-working-fastboot-drivers-windows-8-1-x64/) since I used Win 8.1 for the RUU and it flashed successfully.
But it is still stuck on the HTC screen - gave it 30 minutes for the first boot after flash. Recovery is also still stuck, so I reflashed and same issue.
Radio is now 3831.19.00.110
I relocked my developers phone before installing the 1.57.617.60 RUU. Afterwards I have not been able to unlock it (it shows "relock"). It did not recognize "fastboot oem get_identifier_token". It did act on "fastboot flash unlocktoken Unlock_code.bin", but failed with an error "cannot flash this partition in s-on state". The OEM Unlock is enabled in the Developers options. I reinstalled the RUU via SDcard but no change. So now I have a stock phone, unrooted, and no apparent way to unlock it and get back to root, TWRP, and custom ROM. Which seems to imply no access to my backups with TWRP and TiBU.
Anyone have any ideas? Perhaps Sunshine could root?
Thanks in advance,
Greg
Did you run the "fastboot oem get_identifier_token" commands in download mode or fastboot mode? That command only works in download mode.
Thank you - that did it. BTW there is no "fastboot" mode anymore, only bootloader and download modes. I started from normal operating mode and then used "adb reboot bootloader" which put the phone in bootloader mode, not download mode. The instructions I was following left out the part about selecting download mode before continuing.
Thanks again,
Greg
This is fun - the instructions for installing TWRP also left out that step, and - surprise - didn't work. Switched to download mode and all was well.
Greg
CarinaPDX said:
This is fun - the instructions for installing TWRP also left out that step, and - surprise - didn't work. Switched to download mode and all was well.
Greg
Click to expand...
Click to collapse
It's really easier if you just reboot directly to download mode, so there is no 'extra step.'
hi my oneplus 7 pro 1910 stuck at bootloader and when i press start or recovery it gets back to the bootloader screen i cant even turn off the phone
i accidentally wiped all partitions in twrp and made a format .
anyhelp ? ive tried to do the fastboot rom flash but my pc doesnt detect my phone
i tried almost every solution i found but nothing works
Your bootloader needs to be unlocked to use a fastboot ROM.
Is it unlocked?
@soka said:
Your bootloader needs to be unlocked to use a fastboot ROM.
Is it unlocked?
Click to expand...
Click to collapse
Yes it’s unlocked , any help
Search on the fast boot rom thread for the fast boot rom version you were last on, i have used this many times and it worked.
One thing to note, after it flashed everything , I ended up in crash dump error. I went into stock recovery and wiped/formatted my device and it boot up great.
https://forum.xda-developers.com/t/msm-tool-guac-for-all.3934691/ - just follow this guide
One thing that worked for me is when your phone is plugged into your pc open a command prompt and type fastboot boot twrp-*.img (make sure it is the .img not .zip), and from there download the twrp installer .zip and flash that, reboot to recovery, and install the OTA for your device (OTAs can be found at this thread).
If it fails to boot and gives you an error, try fastboot getvar all to see which slot is currently active then do fastboot --set-active=*inactive slot letter* then fastboot --set-active=*original active slot letter* then try to boot to the twrp .img from fastboot again. If fastboot doesn't detect your device at all, try seeing if adb devices outputs anything, and if it does type adb reboot bootloader