Aplogies if this is not the best starting point but have been reading for 10 hours and am reluctant to take a next step after failure of s-off that has stuck phone in bootloader.
Details
Copied all SD card data to PC
Rooted phone as described by HTCdev
Used SKG utility to attempt s-off
Controlbear got stuck in some strage loop waiting for device after process had started. Never even got prompted to try the wire trick :-( 30 mins later I had to pull the pin
rebooting phone gave me the Controlbear black screen with Green arrow but could now not connect to the device using controlbear just said waiting for device then press any key to exit
Phone will not boot to android OS
when USB connected to phone in bootloader it says FASTBOOT USB and
fastboot devices lists my connected device so USB is OK
Followed instructions at unlimited.io/troubleshooting to try to recover controlbear -f seemed to do somthing so then did
fastboot flash boot recovery_backup.img
which failed could not find image !!!!! der
downloaded 4ext recovery.img
fastboot flash boot recovery.img
worked
Now have
Details of boot
*** UNLOCKED ***
Pyramid PVT SHIP S-ON RL
HBOOT 1.27.0000
Radio 11.24.3504.10_M
OpenADSP-v)2.6.0.2226.00.0131
cMMC-boot
CID reported by fastboot getvar cid is BM__001
Just tried everything from bootloader but always got back bootloader screen no Controlbear screen with arrow as before
At a whim I ran the controlbear -f again and whammo it came up with the 4ext recovery which I was happy to see. Despite doing a backup before starting anything 4ext says no backup present :-(
How can I recover device? I have downloaded the Bell stock RUU which should be correct for this device. Running it says device image version is 3.32.666.13Hesitant to try anything without some good advice. Hopefully I can recover and try the s-off agin but it's been a painful ride. Is it just as simple as clicking update on the RUU exe?
thanks
The backups are not present its saying when you are doing controlbear -f
That means you have no backup present in that controlbear folder
This can be either because of
1.you have another copy of controlbear folder where you done the soff process and where the controlbear saved the backups
(there will be boot_backup.img, recovery_ backup.img)
2.you deleted those images from the controlbear folder
Now what you can do is
1.just find the boot_backup.img and flash it via bootloader
fastboot flash boot boot_backup.img
That will get you out of the Juopunutbear screen..
No need to run the ruu in this case
Edit: and with regards to the 4EXT backup.. The backup will be stored in sdcard and during soff process the sdcard will be wiped.. That's why 4EXT said no backup present.. Just format your sdcard again.. Copy the sdcard backup from your pc (at least copy the Clockworkmod/backup folder to sdcard with the same path in sdcard... It holds your rom backup if you did any)
Then try the 4EXT backup
Sent from my pyramid.. Through blazing fast sonic waves
If your problem was solved, it's a good idea to add [SOLVED] to the topic.
Still in trouble
HI thanks for the advice. Went to the io help and they said relock boot and reflash RUU. Now I have not RUU'd at all as have not been able to find a suitable one. But did fastboot oem lock as suggested. Can I now unlock it again as your post made way more sense and I found the recovery stuff you are speaking of. Just need to unlock and I should be able to recover. is there an unlock command?
markwatson said:
HI thanks for the advice. Went to the io help and they said relock boot and reflash RUU. Now I have not RUU'd at all as have not been able to find a suitable one. But did fastboot oem lock as suggested. Can I now unlock it again as your post made way more sense and I found the recovery stuff you are speaking of. Just need to unlock and I should be able to recover. is there an unlock command?
Click to expand...
Click to collapse
Copy the unlock_code.bin to the folder with adb & fastboot.
Then
Code:
fastboot flash unlocktoken unlock_code.bin
Also, please come down to this channel for support. (I'm only going to help there because you used the tool)
SOLVED
Solved Problem
Hi All Thanks to some sterling efforts by KGS1992 my problem was solved. Take care ye all to ensure that you ensure you get the correct version of controlbear there are many and you need the correct one for your android version. I'll post a detailed summary tomorrow I'm bushed.
In November, I helped my friend unlock and root his T-Mobile HTC One S using Hasoon's All-In-One-Toolkit.
He left the ROM as stock, and hasn't uninstalled any apps or bloats.
A couple weeks ago he got the OTA message to update. When he hits the notification to proceed with the update, the following happens:
phone resets
clockwork mod recovery v5.8.3.1
finding update package...
e: unknown volume for path [internals dcard: download/OTA_Ville_U_ICS_40_S_TMOUS_2.35.531.10-1.84.531.2_release_2978576yp8mjiw19tsxxey.zip]
e: can't mount INTERNAL SDCARDownload/OTA(tons of numbers).zip
His current software version is 1.84.531.2.710ORD, and he's on Android 4.0.3.
What needs to be done to enable the OTA update? I'm not near him, but I can talk him through it with Skype. I'm just not used to the HTC environment and terminology.
All he needs is to relock bootloader and install stock recovery, here is a link to download it from my dropbox..
http://db.tt/YTK06p9b
how to install stock recovery
Can you please explain how to relock the bootloader and how to install the stock recovery.
shadowch31 said:
All he needs is to relock bootloader and install stock recovery, here is a link to download it from my dropbox..
Click to expand...
Click to collapse
espaniol said:
Can you please explain how to relock the bootloader and how to install the stock recovery.
Click to expand...
Click to collapse
shadowch31 said:
All he needs is to relock bootloader and install stock recovery, here is a link to download it from my dropbox..
Click to expand...
Click to collapse
Put the phone into bootloader.
Type in the following command in a command shell, opened in the adb directory: fastboot oem lock
espaniol said:
Can you please explain how to relock the bootloader and how to install the stock recovery.
shadowch31 said:
All he needs is to relock bootloader and install stock recovery, here is a link to download it from my dropbox..
Click to expand...
Click to collapse
Your friend will need to have the phone drivers installed and an adb/fastboot folder set up (similar to the "data" folder from Hasoon's All-In-One-Toolkit with fastboot, adb, etc.). Get the phone to the bootloader then go to fastboot mode and connect the USB (it should say "fastboot usb"). Now flash the stock recovery by running the following command in the terminal:
Code:
fastboot flash recovery stock_recovery.img
then lock the bootloader with this command:
Code:
fastboot oem lock
as Raptylos suggested
Click to expand...
Click to collapse
I know that the new roms use a new kernel now.
I'm on 1.14 Hboot
S-ON
*UNLOCKED
*TAMPERED
I am rooted (Not sure if supercid but I assume so)
Since you have to be on 3.18 now, and be S-OFF, Do I have to go back to stock, do official 3.18 OTA and then unlock bootloader and root again?
I'm kind of confused.
(At&t One X)
The best way to do it is just to become s-off and then run the RUU. You need to have SuperCID to get s-off so you'll need to clarify that first. Boot into bootloader, connect your phone to pc (I'm assuming you have adb/fastboot installed on your pc), make sure it says fastboot usb on your phone screen, then open a command prompt in your fastboot folder and issue the following command:
fastboot oem readcid
Hopefully it'll come up as 11111111 or 22222222 and you can continue to the s-off thread here. If it turns out you don't have SuperCID, you'll need to do that first.
While you're doing that you might as well start downloading the 3.18 RUU, then run it once you've completed the previously mentioned steps.
Once the RUU is finished you'll need to flash a custom recovery again, I recommend using TWRP 2.6. Use the following commands:
fastboot flash recovery "TWRP.img"
(Whatever the exact name of the recovery file is, without the talking marks)
fastboot erase cache
fastboot reboot-bootloader
Now you should be able to select recovery and flash whatever ROM you want to.
Sent from my Evita
timmaaa said:
The best way to do it is just to become s-off and then run the RUU. You need to have SuperCID to get s-off so you'll need to clarify that first. Boot into bootloader, connect your phone to pc (I'm assuming you have adb/fastboot installed on your pc), make sure it says fastboot usb on your phone screen, then open a command prompt in your fastboot folder and issue the following command:
fastboot oem readcid
Hopefully it'll come up as 11111111 or 22222222 and you can continue to the s-off thread here. If it turns out you don't have SuperCID, you'll need to do that first.
While you're doing that you might as well start downloading the 3.18 RUU, then run it once you've completed the previously mentioned steps.
Once the RUU is finished you'll need to flash a custom recovery again, I recommend using TWRP 2.6. Use the following commands:
fastboot flash recovery "TWRP.img"
(Whatever the exact name of the recovery file is, without the talking marks)
fastboot erase cache
fastboot reboot-bootloader
Now you should be able to select recovery and flash whatever ROM you want to.
Sent from my Evita
Click to expand...
Click to collapse
I'm trying to get back to stock.
Just sick of this phone.
I didn't know about the 2.20 to 3.18 bricking problem with s-on. so I bricked my phone. warranty replacement on it. got the new on, did the ota update to 3.18. used hasoon's tool to root and unlock the bootloader. got soff, downgraded my touch to use the cm10.1 nightly. and just have had a TON of problems since.
phone turning off, getting stuck in boot loops. tried going to cm10.0 and had the same issues, was able to load a backup from the htc sense rom before I put CM on and even that will reboot and get stuck in a boot loop.
I wish I hadn't touched the damn thing.
Now I'm scared to run the RUU 3.18 because last time it bricked my phone.
I do have my boot loader unlocked, on hboot 2.14 and have s-off.
Should I be okay to run that RUU you listed?
Yeah if you're s-off you can just run the RUU and you'll be back to stock.
Sent from my Evita
timmaaa said:
Yeah if you're s-off you can just run the RUU and you'll be back to stock.
Sent from my Evita
Click to expand...
Click to collapse
Thank you so much! I followed everything you said and it worked, only problem is the TWRP, it freezes for a sec when I click to reboot and then goes unresponsive until it restarts.
[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