TWRP won't play nicely - AT&T, Rogers HTC One X, Telstra One XL

Can anyone tell me what I'm doing wrong?
Phone is a UK HTC One XL Evita on Orange
I used the Windroid tool to unlock the bootloader. That worked fine. Then I used it to flash TWRP and SuperSU. But I can't get TWRP to run. When I choose recovery, the phone just displays one of two splash screens (One is a phone with two arrows in a circle. Other is HTC warning- HTC internal development build, not for distribution). Then the phone reboots, so there is no access to recovery.
I tried loading CWM from Rom Manager, but that fails too.
(I'm just trying to root it. Should be easy. It's not)
Edit : relax I'm there. I installed CWM via fastboot, which has allowed me to install SuperSU. So I appear to be rooted at last.
So-do I now need S-Off?

Related

HELP i soft bricked my htc one s (s4)

i have htc one s (s4) tmobile us after buying i unlocked bootloader with the help of hdcdev.com then cwm flashed then
rooted then i installed venom rom all went well.
After that i installed rommanager from market in that i checked download rom option at that time rommanager given
me popup to install cwm recovery. i clicked yes :crying:
After that i am not able to boot into bootloader mode, i also tried all in one toolkit still not get into bootloader mode.
Now its only restarting and going into recovery
baba7444 said:
i have htc one s (s4) tmobile us after buying i unlocked bootloader with the help of hdcdev.com then cwm flashed then
rooted then i installed venom rom all went well.
After that i installed rommanager from market in that i checked download rom option at that time rommanager given
me popup to install cwm recovery. i clicked yes :crying:
After that i am not able to boot into bootloader mode, i also tried all in one toolkit still not get into bootloader mode.
Now its only restarting and going into recovery
Click to expand...
Click to collapse
MOD -- please delete this thread, mysteriously i switched off the phone, and restarted it, and it started properly , i am extremely sorry creating this thread
I know it may be crazy, but a similar situation happened to me too.
My HTC One S (S4) had just been unlocked, CWM installed, and installed Venom. I went to use Boot_Flash_Script and then into recovery to Clear Cache. After that point my phone wouldn't boot. It would flash quickly, then have a black screen for 10-15 seconds with the orange LED glow then straight into recovery. Any option to wipe and reinstall the rom didn't work.
Solution: An Aha! Moment... I had forced a shutoff by holding vol up + vol down + top power for 10 seconds. UNPLUG the USB cable! Then after turning it on again with no buttons pushed, it went into Venom.
Whew... Posting an explanation in case anyone else cannot get into hboot / bootloader and thought to have bricked their htc one s. I thought it was bricked until I unplugged the cable and fully shut it off.
:laugh:

[Q] [HELP] Loop + No access to Recovery

That's my first post here in the One S forum and, unfortunately, not a happy one.
I used to have fun with modding a long time ago, with the HTC Desire, but when I bought the One S, I didn't even root it, until yesterday.
To unlock the bootloader and install the TWRP recovery I used the All-in-One toolkit; then I installed a MIUI v5 porting and updated to the latest version.
Not satisfied with it, this morning I decided to try Sense 5 with TrickDroid 10.3.2: I did a TWRP backup, wiped the necessary and installed the zip.
Now the phone is in an infinite loop.. that would be ok, but I can't get to fastboot or recovery.
The problem is that even before I wasn't able to get to fastboot with the button combo (even if I disabled fastboot in MIUI settings), and to access the recovery I used the command provided in the All-in-One toolkit.
I'm not able to use the All-in-One toolkit since the device can't be found while turning on.
So now I'm here with my phone vibrating every 30 seconds or so and that's a bit frustrating...
Do any of you know what to do?
If you need any further information just ask, and sorry for my English, I hope everything is clear.
Thank you in advance
Francesco
P.S.: It is the S4 version.
fracaccia said:
That's my first post here in the One S forum and, unfortunately, not a happy one.
I used to have fun with modding a long time ago, with the HTC Desire, but when I bought the One S, I didn't even root it, until yesterday.
To unlock the bootloader and install the TWRP recovery I used the All-in-One toolkit; then I installed a MIUI v5 porting and updated to the latest version.
Not satisfied with it, this morning I decided to try Sense 5 with TrickDroid 10.3.2: I did a TWRP backup, wiped the necessary and installed the zip.
Now the phone is in an infinite loop.. that would be ok, but I can't get to fastboot or recovery.
The problem is that even before I wasn't able to get to fastboot with the button combo (even if I disabled fastboot in MIUI settings), and to access the recovery I used the command provided in the All-in-One toolkit.
I'm not able to use the All-in-One toolkit since the device can't be found while turning on.
So now I'm here with my phone vibrating every 30 seconds or so and that's a bit frustrating...
Do any of you know what to do?
If you need any further information just ask, and sorry for my English, I hope everything is clear.
Thank you in advance
Francesco
P.S.: It is the S4 version.
Click to expand...
Click to collapse
Did you flash boot.img after flashing the rom ?
vatsaman said:
Did you flash boot.img after flashing the rom ?
Click to expand...
Click to collapse
I'm now having the same problem: exactly I forgot to flash boot.img after flashing the rom, and my HTC One S now seems to be bricked.
Yesterday I could turn it on and go into HBOOT, but when I chose Recovery or Factory Reset it rebooted and after the HTC logo, a warning logo appeared. Now I cannot do anything with this.
Can you pls give me some advise or how I can fix this problem? Many thanks!:good:
Trung Del said:
I'm now having the same problem: exactly I forgot to flash boot.img after flashing the rom, and my HTC One S now seems to be bricked.
Yesterday I could turn it on and go into HBOOT, but when I chose Recovery or Factory Reset it rebooted and after the HTC logo, a warning logo appeared. Now I cannot do anything with this.
Can you pls give me some advise or how I can fix this problem? Many thanks!:good:
Click to expand...
Click to collapse
That is not a brick lol :laugh:
That warning logo isn't a big deal. Everyone who has unlocked their bootloader gets it. And seems like you have erased your recovery by selecting "Factory Reset".
1. Download All-In-One Tool kit for HTC One S from the Development forum.
2. Flash a custom recovery. TWRP recommended.
3. Boot into recovery, mount sd card, copy your rom.
4. Flash your ROM.
5. Boot into fastboot
6. flash boot.img
7. Restart :good:
vatsaman said:
That is not a brick lol :laugh:
That warning logo isn't a big deal. Everyone who has unlocked their bootloader gets it. And seems like you have erased your recovery by selecting "Factory Reset".
1. Download All-In-One Tool kit for HTC One S from the Development forum.
2. Flash a custom recovery. TWRP recommended.
3. Boot into recovery, mount sd card, copy your rom.
4. Flash your ROM.
5. Boot into fastboot
6. flash boot.img
7. Restart :good:
Click to expand...
Click to collapse
On waiting for your reply I did exactly the same way that you recommended, thanks anyway. But even I tried so many times, my HTC One S's still stucked at the HTC logo
p.s: I tried to flash this ROM: http://forum.xda-developers.com/showthread.php?t=1910738
Trung Del said:
On waiting for your reply I did exactly the same way that you recommended, thanks anyway. But even I tried so many times, my HTC One S's still stucked at the HTC logo
p.s: I tried to flash this ROM: http://forum.xda-developers.com/showthread.php?t=1910738
Click to expand...
Click to collapse
Did you try to remove the SIM card? Mine was stuck in bootloop and only way it worked for me was to remove SIM card, press power button for 10 or more seconds and it eventually booted into bootloader. hope it work for you...

[Q] [Help] Phone only boots to TWRP

having some troubles with my vzw m8. i just got the phone, used sunshine to get s-off then downlaoded the twrp app to install the recovery.
since i was on stock and didnt have a super reboot menu, i powered down. did the vol down+power to get to the bootloader.
then chose recovery it gave me the device with the red ! sign. then i fiddled with the buttons and it went to TWRP. That seems funny to begin, but it gets better.
Now, i can't boot normally. it always goes to TWRP. any ideas?
HBOOT 3.16
mangler1055 said:
having some troubles with my vzw m8. i just got the phone, used sunshine to get s-off then downlaoded the twrp app to install the recovery.
since i was on stock and didnt have a super reboot menu, i powered down. did the vol down+power to get to the bootloader.
then chose recovery it gave me the device with the red ! sign. then i fiddled with the buttons and it went to TWRP. That seems funny to begin, but it gets better.
Now, i can't boot normally. it always goes to TWRP. any ideas?
HBOOT 3.16
Click to expand...
Click to collapse
I had a similar problem when I first S-Off'd and rooted my M8 with the firewater method, could only get the phone to boot into recovery. Go to http://forum.xda-developers.com/showthread.php?t=2708628 and look for the section of the first post for -- *Unsecured Kernel --, try flashing that, it finally let me boot to the ROM and return to normal functionality.
Zhamel said:
I had a similar problem when I first S-Off'd and rooted my M8 with the firewater method, could only get the phone to boot into recovery. Go to http://forum.xda-developers.com/showthread.php?t=2708628 and look for the section of the first post for -- *Unsecured Kernel --, try flashing that, it finally let me boot to the ROM and return to normal functionality.
Click to expand...
Click to collapse
you flashed it to the wrong partition..if so all you need to do is fastboot flash twrp an then reboot your recovery it will be twrp in the right place. Just restore a backup you made an you will be all set...if you have no backup..smh then load a ROM to your SD card via PC then do as above flash ROM of SD card an that will fix your issue.
quoted wrong person. My bad
Sent from my HTC6525LVW using XDA Premium 4 mobile app
mangler1055 said:
having some troubles with my vzw m8. i just got the phone, used sunshine to get s-off then downlaoded the twrp app to install the recovery.
since i was on stock and didnt have a super reboot menu, i powered down. did the vol down+power to get to the bootloader.
then chose recovery it gave me the device with the red ! sign. then i fiddled with the buttons and it went to TWRP. That seems funny to begin, but it gets better.
Now, i can't boot normally. it always goes to TWRP. any ideas?
HBOOT 3.16
Click to expand...
Click to collapse
Read my above post. I meant to quote you.
Sent from my HTC6525LVW using XDA Premium 4 mobile app

[Completed] Pressing recovery buttons shows lying dead Android then to stock instead of TWRP

I wanted to get a custom recovery for my device: [Qnet Luxgen] to be able to flash Xpose Framework for the VirtualSensor module for my Smartphone. First I rooted my phone with Kingoroot app and it seemed fine, then I used the app Flashify to flash the ZIP of Xpose Framework but after reboot my phone would just show an exclamation mark coming drom an Android that's lying down.
I tried other methods, I gone to the bootloader and flash it through fastboot. I got my oem unlocked and flashed my recovery.img and boot.img and this one would make my phone screen blank in half and had gone into a bootloop. So I download the ROM update of my device (lucky there was one) and flashed the whole thing, luckily it got my phone back up. I thought that that was because the TWRP.img I downloaded wasn't compatible with my devices so I looked through TWRP to download the appropriate one. Unfortunately there wasn't one with my device name so instead I searched for TWRP compatible with MTK devices (Chinaphone Brand) since my phone seemes like a chinabrand and found out about "Easy Magic TWRP installer for MTK". It seemed to have recognise my device as an MTK device and the installation went good. But when I restart my phone AFTER FLASH and got into recovery mode it just shows again the dead Android and if I press long enough it would go to stock recovery. What seems to be the problem with this?
MordecaiBot said:
I wanted to get a custom recovery for my device: [Qnet Luxgen] to be able to flash Xpose Framework for the VirtualSensor module for my Smartphone. First I rooted my phone with Kingoroot app and it seemed fine, then I used the app Flashify to flash the ZIP of Xpose Framework but after reboot my phone would just show an exclamation mark coming drom an Android that's lying down.
I tried other methods, I gone to the bootloader and flash it through fastboot. I got my oem unlocked and flashed my recovery.img and boot.img and this one would make my phone screen blank in half and had gone into a bootloop. So I download the ROM update of my device (lucky there was one) and flashed the whole thing, luckily it got my phone back up. I thought that that was because the TWRP.img I downloaded wasn't compatible with my devices so I looked through TWRP to download the appropriate one. Unfortunately there wasn't one with my device name so instead I searched for TWRP compatible with MTK devices (Chinaphone Brand) since my phone seemes like a chinabrand and found out about "Easy Magic TWRP installer for MTK". It seemed to have recognise my device as an MTK device and the installation went good. But when I restart my phone AFTER FLASH and got into recovery mode it just shows again the dead Android and if I press long enough it would go to stock recovery. What seems to be the problem with this?
Click to expand...
Click to collapse
Greetings and welcome to xda. If you ask in this thread here
http://forum.xda-developers.com/showthread.php?t=2798257&page=48
hopefully the experts there can assist you
Good Luck
Sawdoctor

Wileyfox Spark X

Hi all,
This is not the right forum, but I didn't see one specifically for Spark X models, so I'm sorry.
A friend of mine has a Wileyfox Spark X device, which was bootloader unlocked, had TWRP 3.0.2 installed and was running on the original firmware (6.0.1) but rooted and xposed installed.
Now an update came out for Android 7. To update the device, I put back the original firmware and recovery, started doing the upgrades and all went smooth.
Device is up and running on Android 7, however when I now try to install TWRP again, it won't work.
(fastboot flash the TWRP recovery (same version as before - 3.0.2) seems to work ok. I then go to pull the battery after flashing, put battery back, and start recovery by pressing vol down and power.
I see the device going to a black screen, then reboot and keeps doing this as long as I keep the vol down pressed. Once I release the device continues normal boot and goes into Android.
I assume this has to do with a change in Android 7?
Seems I can get TWRP working again, if I flash the original boot image, however then ofcourse the Android boot doesn't work anymore. (additionally once in TWRP, it seems /system cannot be mounted anymore and TWRP thinks no system is installed)
So in short, I believe I should get a newer TWRP version that is compatible with Android 7. I tried the different versions available on twrp.me (up to 3.1.1.0) however to no avail. None works with the latest android.
As such, the device is able to run in android 7, but without root. (no adb root option in developer options, adb root doesn't work either, kingroot etc also no go)
Does anyone have any options that I can still try? or could help me with a proper TWRP version that should work? (I did find some TWRP recoveries on 4pda (russian website) for Spark + that claim to be for Android 7, but those didn't work either))
Thanks !
@Asansi
I'm sorry I can't help you, but may I ask how you rooted the phone? I can't get mine to be properly rooted.
I can help you with any problem. I'm a senior person in that model since I have been using it ever since. If you could like
Sent from my Wileyfox Spark using XDA
HackerAce said:
I can help you with any problem. I'm a senior person in that model since I have been using it ever since. If you could like
Sent from my Wileyfox Spark using XDA
Click to expand...
Click to collapse
Apologies for ressurecring a zombie thread but, OP has a spark X and you have a Spark, so it would appear that you SENIOR person in that model failed at the very first hurdle.
Am still wonderng if there is an sign of a 7.0 compatible twrp for spark X? Don't suppose anyone has a link to the latest Spark X firmware either?
TWRP versions
Asansi said:
Hi all,
This is not the right forum, but I didn't see one specifically for Spark X models, so I'm sorry.
A friend of mine has a Wileyfox Spark X device, which was bootloader unlocked, had TWRP 3.0.2 installed and was running on the original firmware (6.0.1) but rooted and xposed installed.
Now an update came out for Android 7. To update the device, I put back the original firmware and recovery, started doing the upgrades and all went smooth.
Device is up and running on Android 7, however when I now try to install TWRP again, it won't work.
(fastboot flash the TWRP recovery (same version as before - 3.0.2) seems to work ok. I then go to pull the battery after flashing, put battery back, and start recovery by pressing vol down and power.
I see the device going to a black screen, then reboot and keeps doing this as long as I keep the vol down pressed. Once I release the device continues normal boot and goes into Android.
I assume this has to do with a change in Android 7?
Seems I can get TWRP working again, if I flash the original boot image, however then ofcourse the Android boot doesn't work anymore. (additionally once in TWRP, it seems /system cannot be mounted anymore and TWRP thinks no system is installed)
So in short, I believe I should get a newer TWRP version that is compatible with Android 7. I tried the different versions available on twrp.me (up to 3.1.1.0) however to no avail. None works with the latest android.
As such, the device is able to run in android 7, but without root. (no adb root option in developer options, adb root doesn't work either, kingroot etc also no go)
Does anyone have any options that I can still try? or could help me with a proper TWRP version that should work? (I did find some TWRP recoveries on 4pda (russian website) for Spark + that claim to be for Android 7, but those didn't work either))
Thanks !
Click to expand...
Click to collapse
I've tried TWRP 3.0.2-0 (i.e. latest from https://dl.twrp.me/porridgek3/): it flashes Ok but it won't boot up afterwards. I've tried 3.0.2-0 but as you say "it seems /system cannot be mounted anymore and TWRP thinks no system is installed)". After letting it finish, Root Checker (not unsurprisingly) says that device is not rooted. Have you progressed with this issue? BTW I've emailed TWRP Support (from their web page) asking if they have a working version.
Same problem here, It's pretty annoying. My sister's getting this same phone (on Android 6) soon so I might just make a full backup with TWRP on it and somehow restore it on my phone.
Systemless Root
I can't decide whether to try the rooting method given in https://android.stackexchange.com/questions/160130/how-do-i-install-systemless-supersu-in-samsung
The method is:
Sometimes the need for a systemless installation of SuperSU is not detected by the installation script, to force this to occur follow the following steps.
Start TWRP 3.0 or higher on the device
Go to Advanced - Terminal
In the terminal, enter echo SYSTEMLESS=true>>/data/.supersu
Press Enter
Exit to the TWRP main menu
Flash the current SuperSU as per normal
When flashing SuperSU, you should see in the TWRP recovery log screen mentions of system-less installation and patching of the boot image.
Has anyone had experience of this method?
Resurrection! This post shall LIIIIVE!
No, seriously tho, does anyone have any updates on the issue? Or could at least point me in the right direction to root a Wileyfox Spark X? At this point, any help is much appreciated, since I have not been able to get ANY method working for me.
Thanks a lot
Sent from my Wileyfox Spark X using XDA Labs
Systemless Root
ScreamingSteve said:
Resurrection! This post shall LIIIIVE!
No, seriously tho, does anyone have any updates on the issue? Or could at least point me in the right direction to root a Wileyfox Spark X? At this point, any help is much appreciated, since I have not been able to get ANY method working for me.
Thanks a lot
Sent from my Wileyfox Spark X using XDA Labs
Click to expand...
Click to collapse
Steve,
Have you tried the method detailed in post #7?
johnaaronrose said:
Steve,
Have you tried the method detailed in post #7?
Click to expand...
Click to collapse
I am afraid not, since I can't install TWRP. One info would help me out a lot tho: would an Android-Downgrade (from 7.0 to CM13) help with installing TWRP and rooting?
Steps taken earlier:
quite literally everything (that would make sense even remotely)
Steps taken today:
- Downloading TWRP 3.2.1-0 (https://twrp.me/wileyfox/wileyfoxsparkx.html)
- fastboot-unlocking the bootloader (no issues)
- trying to install TWRP (no issues there either)
- when trying to reboot straight to recovery, I don't get past the bootlogo, suggesting to me that either the install or TWRP was corrupted.
Any help one might get?
Thanks a lot?
TWRP
ScreamingSteve said:
I am afraid not, since I can't install TWRP. One info would help me out a lot tho: would an Android-Downgrade (from 7.0 to CM13) help with installing TWRP and rooting?
Steps taken earlier:
quite literally everything (that would make sense even remotely)
Steps taken today:
- Downloading TWRP 3.2.1-0 (https://twrp.me/wileyfox/wileyfoxsparkx.html)
- fastboot-unlocking the bootloader (no issues)
- trying to install TWRP (no issues there either)
- when trying to reboot straight to recovery, I don't get past the bootlogo, suggesting to me that either the install or TWRP was corrupted.
Any help one might get?
Thanks a lot?
Click to expand...
Click to collapse
The only version that I had success with was 3.0.2 from https://dl.twrp.me/porridgek3/"]https://dl.twrp.me/porridgek3/[/URL]
Even then, It's all hit & miss getting into TWRP:
1. If I do anything after flashing (e.g. booting as normal), I have to go into fastboot & flash TWRP again.
2. Once I have flashed TWRP (i.e. still in fastboot mode), I can't leave fastboot mode. Also, the phone will not switch off unless I remove the battery and put it back in after approx 10 seconds.
3. Even then it often refuses to load TWRP i.e. it goes into the Android Boot menu.
AlwaysLivid suggested that you can boot to TWRP by executing "fastboot boot recovery.img" (where recovery.img is the TWRP img file renamed) on MSDOS Prompt / Terminal according to whether you're using Windows or a Linux distro (e.g. Ubuntu which I use). Presumably this would be after you have taken the battery out for a few seconds before inserting it again and have then booted into the appropriate mode with the Volume Down & Power buttons held down.
johnaaronrose said:
The only version that I had success with was 3.0.2 from https://dl.twrp.me/porridgek3/"]https://dl.twrp.me/porridgek3/[/URL]
Even then, It's all hit & miss getting into TWRP:
1. If I do anything after flashing (e.g. booting as normal), I have to go into fastboot & flash TWRP again.
2. Once I have flashed TWRP (i.e. still in fastboot mode), I can't leave fastboot mode. Also, the phone will not switch off unless I remove the battery and put it back in after approx 10 seconds.
3. Even then it often refuses to load TWRP i.e. it goes into the Android Boot menu.
AlwaysLivid suggested that you can boot to TWRP by executing "fastboot boot recovery.img" (where recovery.img is the TWRP img file renamed) on MSDOS Prompt / Terminal according to whether you're using Windows or a Linux distro (e.g. Ubuntu which I use). Presumably this would be after you have taken the battery out for a few seconds before inserting it again and have then booted into the appropriate mode with the Volume Down & Power buttons held down.
Click to expand...
Click to collapse
Thanks a lot, I'll try your method, the explicit call to boot the TWRP image could really help.
Thanks for your extended explanation tho, showed me some new ways to eventually get this stuff to work.
Sent from my Wileyfox Spark X using XDA Labs
johnaaronrose said:
I can't decide whether to try the rooting method given in https://android.stackexchange.com/questions/160130/how-do-i-install-systemless-supersu-in-samsung
The method is:
Sometimes the need for a systemless installation of SuperSU is not detected by the installation script, to force this to occur follow the following steps.
Start TWRP 3.0 or higher on the device
Go to Advanced - Terminal
In the terminal, enter echo SYSTEMLESS=true>>/data/.supersu
Press Enter
Exit to the TWRP main menu
Flash the current SuperSU as per normal
When flashing SuperSU, you should see in the TWRP recovery log screen mentions of system-less installation and patching of the boot image.
Has anyone had experience of this method?
Click to expand...
Click to collapse
Finally, your advice with "Fastboot boot twrp.img" worked magic!
Got twrp installed, but now I'm facing the same problem as you with the systemless root. I'll dig around a little and see what I can find.

Categories

Resources