TWRP is probably corrupted? (I can't really press anything) - Samsung Galaxy S7 SM-G930F - Samsung Galaxy S7 Questions and Answers

So I wanted to make a backup using TWRP but apparently TWRP itself just didn't work.
So my main issue is that pressing almost anything doesn't give an input (Install works fine while Wipe only works when pressing but the actual UI is broken and I can't go back).
So at this point my phone is stuck in a TWRP bootloop since I cannot press the reboot option. Also, I tried flashing TWRP again and it didn't work. What should I do?

salamianchoivy said:
So I wanted to make a backup using TWRP but apparently TWRP itself just didn't work.
So my main issue is that pressing almost anything doesn't give an input (Install works fine while Wipe only works when pressing but the actual UI is broken and I can't go back).
So at this point my phone is stuck in a TWRP bootloop since I cannot press the reboot option. Also, I tried flashing TWRP again and it didn't work. What should I do?
Click to expand...
Click to collapse
When you connect via adb, then you can execute the commands described in the FAQ for TWRP and all other commands available in the shell.

Which version of TWRP are you using? The latest official one doesn't want to install for me, because it's 1MB larger than the actual recovery partition - could this have something to do with the strange behaviour?

Related

TWRP alternative?

So here is what I am stuck:
I have a SM-G9208 international edition. I have been working around and finally managed to get TWRP flashed using ODIN and boot into recovery. the problem is that the touch screen does not work for some reason.
So I am looking for a recovery that does not require touch screen. I was hoping to find a recovery that I can flash through ODIN and only uses physical buttons. Does any know where I can find such a thing?
Hey mate. I was searching for Philz for some time - go for it http://arter97.com/browse/exynos7420/kernel/4.3/. This guy has it for probably all models. And buttons are apparently working.
On the other hand you flashed the correct TWRP?
davebugyi said:
On the other hand you flashed the correct TWRP?
Click to expand...
Click to collapse
How many versions of TWRP exists? I only found one version on the official website:
https://dl.twrp.me/zeroflte/
the last file (twrp-2.8.7.1-zeroflte.img.tar) is the one that actually successfully boots into recovery but after that no-touch problem exists. the rest do not work.
Saafir said:
Could try OTG cable with a mouse.
Click to expand...
Click to collapse
I never thought of that. Does TWRP support mouse out of the box or special build of TWRP is needed?
Saafir said:
Yep, TWRP supports it. Should be fine. Had to do it on a G2 with a broke screen
Click to expand...
Click to collapse
It indeed worked. now I can actually do things in TWRP using USB OTG mouse. But there is a new problem: once I use mouse in TWRP, the phone gets stuck in a boot loop after I exit TWRP The only fix is to flash the full image using ODIN
For whoever that may come across this:
TWRP does allow you to work through adb command shell. boot into recovery, attach to your laptop and do:
adb devices
once you get a response do:
adb shell
and then you can do all kind of stuff like:
twrp install filename
twrp backup
twrp restore
I have the same problem but instead like a dumb ass I installed twrp twice and it messed up my screen each time I touch to the right it touches to the left and left is right. So does anybody have a costum recovery or a stock recovery for SM-G920T1 or SM-G920T

The usual: recovery is not seandroid enforcing! FIXED

OK, I know this is a problem that many before had and I've researched the subject thoroughly. But I've only found ways to recover your phone from the soft-brick (one of those fake rubber bricks used in movies:laugh status which was something I did by myself by flashing a stock recovery via odin.
Now my problem is a different one: I have updated my s6 to stock 6.0.1 and all went fine. I then rooted the phone by installing SpaceX kernel and went on to flash recovery via odin. That is when the problem occurred and I've not been able to solve it. I tried flashing also via flashify but with the same result, i.e. phone frozen at the samsung galaxy s6 screen with the damn "recovery is not ......".
What could I try? Anyone knows how to circumvent this issue?
Thanks for any help.
Luca
Just flash this TWRP http://www.mediafire.com/?16c1zxj8gdz3mj4 (AP in Odin with F. Reset Time and Auto Reboot checked), it will boot automatically to recovery,
You will have a working recovery, but it can't reboot or shutdown the phone.
For that, click to "Advanced", "Terminal", and when the keyboard shows up, just type "reboot" or "halt"(without the ") et click on "enter".
Reboot: reboots the phone (the phone will reboot in system)
Halt: shutdown the phone
DJPops said:
Just flash this TWRP http://www.mediafire.com/?16c1zxj8gdz3mj4 (AP in Odin with F. Reset Time and Auto Reboot checked), it will boot automatically to recovery,
You will have a working recovery, but it can't reboot or shutdown the phone.
For that, click to "Advanced", "Terminal", and when the keyboard shows up, just type "reboot" or "halt"(without the ") et click on "enter".
Reboot: reboots the phone (the phone will reboot in system)
Halt: shutdown the phone
Click to expand...
Click to collapse
Thanks: I will try that right away and report back here. Is the procedure of rebooting and shutting down the phone permanent or is it just the 1st boot (I sense it is a permanent thing, but I hope it isn't). If, later on I flash a custom rom and then re-flash the recovery, will this thing go away?
Why is this seandroid thing happening? Are you able to explain it to me?
It's not permanent
Just the first boot. "It erase a boot script that say to your device to boot into recovery" (small explanation, it's not exactly that).
This happen sometimes when you try to update the Su binary via the SuperSU app (it try to reboot the device into recovery, but sometimes it doesn't work and the device is "stuck" on the recovery)
This message shows up on every boot if you have a custom kernel, and if you boot on recovery, it will maybe shows up (depend of your recovery).
It was stucking on this screen because the recovery that you tried to flash is not compatible with marshmallow bootloader. The link in my first answer is a working marshmallow TWRP, for S6 (not S6 edge/+).
DJPops said:
Just flash this TWRP http://www.mediafire.com/?16c1zxj8gdz3mj4 (AP in Odin with F. Reset Time and Auto Reboot checked), it will boot automatically to recovery,
You will have a working recovery, but it can't reboot or shutdown the phone.
For that, click to "Advanced", "Terminal", and when the keyboard shows up, just type "reboot" or "halt"(without the ") et click on "enter".
Reboot: reboots the phone (the phone will reboot in system)
Halt: shutdown the phone
Click to expand...
Click to collapse
Woohoo! It worked! I have a custom recovery, although i have to reboot the phone with a crank
Thanks a lot. Now I'm gonna go on messing it up some more!
DJPops said:
It's not permanent
Just the first boot. "It erase a boot script that say to your device to boot into recovery" (small explanation, it's not exactly that).
This happen sometimes when you try to update the Su binary via the SuperSU app (it try to reboot the device into recovery, but sometimes it doesn't work and the device is "stuck" on the recovery)
This message shows up on every boot if you have a custom kernel, and if you boot on recovery, it will maybe shows up (depend of your recovery).
It was stucking on this screen because the recovery that you tried to flash is not compatible with marshmallow bootloader. The link in my first answer is a working marshmallow TWRP, for S6 (not S6 edge/+).
Click to expand...
Click to collapse
Alas, it seems that it is permanent! It doesn't reboot into anything (neither system nor recovery. Haven't tried download, but I assume it would be the same thing). Furthermore it gets stuck and needs to be rebooted by pressing voldown and power. then it turns on into recovery again. It is a small price to pay, so no worries, but I always like to understand why things happen!
Could I have done another mistake?
Out of interest what random recovery did you give him? lol
Try arter97s mod of twrp 3.0.0-0
http://arter97.com/browse/exynos7420/recovery/twrp/g920fi/
Seems to be the best working mod of latest twrp at the moment. No issues booting etc, just no USB otg support currently.
Sent from my SM-G920I using Tapatalk
self_slaughter said:
Out of interest what random recovery did you give him? lol
Try arter97s mod of twrp 3.0.0-0
http://arter97.com/browse/exynos7420/recovery/twrp/g920fi/
Seems to be the best working mod of latest twrp at the moment. No issues booting etc, just no USB otg support currently.
Sent from my SM-G920I using Tapatalk
Click to expand...
Click to collapse
Oh yes!! This one really works all the way, reboot and all. However, af as you know, is there any of the previous version of TWRP that "agrees" with M bootloader?
Thanks mate
Luca
ManhIT modded recovery not a random recovery you know :mrgreen:
Haha, I was just wondering since it was just a mediafire link saying flash this.
Glad that arters recovery worked a bit better for you.
Recovery's are a bit hit and miss at the moment. That's the best one I've found so far.
I still haven't even got marshmallow, still rocking the latest lollipop which suffers similar problems.
Sent from my SM-G920I using Tapatalk
Oh okay, I'm french and I found this link on a french forum...
I used this recovery on my 920F and apart the reboot, it's working perfectly !

Phone loading into recovery menu after factory reset?

Hey, I rooted my S6 edge (I believe just using the CF autoroot ROM, if my terminology is correct, I'm not too well versed here) and installed a custom recovery menu (TWRP 3.0) a few months ago and everything was working fine.
Today I decided that I wanted to wipe my phone, and I quickly googled to see if a factory reset from the settings app would play well with a rooted phone, and it said it would, it lied. Now my phone is rebooting only into the TWRP menu. I don't know what to do to fix it.
I've tried reloading the back up I made when I installed TWRP, it restores successfully but when rebooting it crashes. I have to reboot using Power+VolDown+Home. I also tried to just reinstall the ROM (assuming that going to Reboot - Download would be the same as using the stock recovery menu) but it also crashes so I don't think ODIN can detect it, the phone does however get recognised by my computer
I'm completely lost on what to do now, as I'm rather new to this, so any help would be appreciated!
thefomaster said:
Hey, I rooted my S6 edge (I believe just using the CF autoroot ROM, if my terminology is correct, I'm not too well versed here) and installed a custom recovery menu (TWRP 3.0) a few months ago and everything was working fine.
Today I decided that I wanted to wipe my phone, and I quickly googled to see if a factory reset from the settings app would play well with a rooted phone, and it said it would, it lied. Now my phone is rebooting only into the TWRP menu. I don't know what to do to fix it.
I've tried reloading the back up I made when I installed TWRP, it restores successfully but when rebooting it crashes. I have to reboot using Power+VolDown+Home. I also tried to just reinstall the ROM (assuming that going to Reboot - Download would be the same as using the stock recovery menu) but it also crashes so I don't think ODIN can detect it, the phone does however get recognised by my computer
I'm completely lost on what to do now, as I'm rather new to this, so any help would be appreciated!
Click to expand...
Click to collapse
Probably need to reflash stock firmware. Then reflash twrp if you want to.
Sent from my SM-G925F
Press volume down and power button after so 10 sec it will not reboot in first time try and try
If this dont work jst copy super su file and update it in trwp it will auto reboot. Try this hope this will work if works thn hit thanks button
Rosli59564 said:
Probably need to reflash stock firmware. Then reflash twrp if you want to.
Sent from my SM-G925F
Click to expand...
Click to collapse
yash_.shah said:
Press volume down and power button after so 10 sec it will not reboot in first time try and try
If this dont work jst copy super su file and update it in trwp it will auto reboot. Try this hope this will work if works thn hit thanks button
Click to expand...
Click to collapse
Thank you both for replying. I couldn't get it too turn off, however I did manage to install a custom ROM through TWRP itself. I think I've just installed TWRP wrong, so thats why it was crashing, so I'll update and reinstall when I'm next at home to see if that stops it crashing. Everything seems to be working now though, so thanks!

Honor 8 Can't Download Firmware, Can't Flash, Bricked? [Solved]

Hi, after trying unlock my bootloader, I couldn't get into recovery mode without "Your phone cannot be trusted" getting stuck on my screen.
I re-locked the boot loader but now when I go into recovery it says "Data Partition is corrupted please format" then it asks me to connect to a wifi network which then just shows errors everytime the password comes up.
I tried to turn on USB Debugging to ADB sideload a firmware, but I can't because the phone has been resetted; if I try to enter a wifi password the keyboard doesnt show it's just the google voice (which doesn't work) with no options. If i skip the wifi option it just goes on the google login and gets stuck on "Checking Info".
Any solutions to the problem please?
EDIT: I just re-unlocked the bootloader and now its permanently stuck on "Your device cannot be trusted, booting now" regardless of what buttons I press during startup
EDIT 2: I fixed it, it was long and complicated but I got it to work, here's how.
1. When flashing TWRP, I realized I was flashing the TWRP for EMUI 4, so I flashed TWRP for EMUI 5. (Make sure Bootloader is unlocked)
First have all the adb/fastboot drivers, for windows shift + right click the folder and click "Open Command here"
Make sure the twrp img file is in the same folder as the adb folder.
On the honor 8 phone, if it is stuck like mine, turn the phone off and then hold Volume Down + Power Button until the download mode is on the screen
Type "fastboot flash recovery (twrpfilename).img"
Once it's done, turn it off and then hold power button + volume up AND volume down at once till TWRP comes on
(Continuously hold it, if the "Your Device cannot be trusted" screen comes on release)
2. (Make sure internal storage and data are backed up externally for this)
Reset system, data, cache/dalvik, and internal storage
3. Download Update.zip and the second .zip from a website on google, search Honor 8 Manual Nougat and click the link from smartstocknews (I can't post links) but do not follow the steps from that website, and also download GAPPS from open GAPPS. Make sure ARM64 is selected and not ARM as well as 7.0
4. After wiping, mount the Honor 8 by connecting it via USB to a computer, and press "Mount" on TWRP
Upload the both update.zip and update_data_full_hw_eu.zip and GAPPS ARM64 7.0 to internal or external storage
5. Exit mount and go to install, install the zips in this specific order and do not reboot in between
A) Update.zip
B) Update_data_full_hw_eu.zip
C) GAPPS.zip
6. Reboot after GAPPS is done (it might show already installed, if that's the case then it's alright, reboot anyways)
Download the 70mb package for firmware downgrade and the latest marshmallow firmware from your regional huawei's website.
Extract the small package and put the .app file in a folder called dload on the SD card and insert it in your phone.
Boot by holding volume + volume - and pressing power, holding all 3 buttons until the phone vibrates.
The package will flash and afterwards you repeat the process, this time using an .app file from the full marshmallow firmware.
The 70mb package installs not matter how messed up your file system is, and makes your phone ready for the MM firmware. This process brings any brick back to life. Good luck.
I too was trying to root my FRD-L04 and apparently used the wrong TWRP because now I get...
Code:
Unable to open ' ' to wipe crypto key
Unable to wipe Data
Unable to format to remove encryption
Failed to mount /data (invalid argument)
and I cant get the keyboard loaded so I can log into my wifi when I do a factory reset. I really have no idea how best to attack this...my phone is bricked I can get into TWRP 3.0.2.0 recovery, sideload, and fastboot (i think). I am currently downloading the stock ROM for my device and will try to sideload it.
I feel I need to fix the data issues thought before trying to load the ROM as I dont think my data partition is working at all now. Does anyone have any suggestions or a step-by-step guide on how to fix my bricked phone?
I've tried all sort of things today but no matter what, I cant get a keyboard working so I guess that means I'm screwed....
EDIT - my phone doesnt have a insertable SD card so I cant fix things the way the above poster suggests.
menriquez said:
I too was trying to root my FRD-L04 and apparently used the wrong TWRP because now I get...
Code:
Unable to open ' ' to wipe crypto key
Unable to wipe Data
Unable to format to remove encryption
Failed to mount /data (invalid argument)
and I cant get the keyboard loaded so I can log into my wifi when I do a factory reset. I really have no idea how best to attack this...my phone is bricked I can get into TWRP 3.0.2.0 recovery, sideload, and fastboot (i think). I am currently downloading the stock ROM for my device and will try to sideload it.
I feel I need to fix the data issues thought before trying to load the ROM as I dont think my data partition is working at all now. Does anyone have any suggestions or a step-by-step guide on how to fix my bricked phone?
I've tried all sort of things today but no matter what, I cant get a keyboard working so I guess that means I'm screwed....
EDIT - my phone doesnt have a insertable SD card so I cant fix things the way the above poster suggests.
Click to expand...
Click to collapse
If you have nougat just flash the correct recovery from the twrp you already have. https://forum.xda-developers.com/honor-8/development/twrp-t3566563
sysak said:
If you have nougat just flash the correct recovery from the twrp you already have. https://forum.xda-developers.com/honor-8/development/twrp-t3566563
Click to expand...
Click to collapse
This is truly one of the worse phones I have ever had when it comes to root and such. My frustration over what, for a unbranded unlocked phone that *should* probably SHIP with root, this phone has and is putting me through is super high.
That being said...so I flashed the new 3.1.0.0 recovery. Before doing that, I had just tried to Unbrick the phone with flashing B162 image with 3.0.3.0...so now the phone is totally frozen in the "Your device has been unlocked and can't be trusted..." screen. Nothing I seem to do can get it out of this mode.
I want to install the rooted b378 boot.img file I just downloaded, but am unable to find the button commands to get the bootloader loaded. Does anyone have any suggestions in somehow trying to save the day with this damned phone?
much thanks in advance.
EDIT: So I got the phone in bootloader mode by pressing vol up/vol down/power and inserting the usb cable...i flashed the rooted boot.img and twrp 3.1.0.1 to both recovery and recovery2 and now i can get into recovery. I feel like I may actually have a chance now to fix this damn thing...
So can anyone point me in a direction where, from this point with the new recovery loaded and the modded boot image installed, where i can get this phone working?? ill use ANY ROM it dont really matter at this point...
Don't worry. It's really easy, once you know what to do, just realy easy to screw up if you don't. If your phone is a mess just roll back to android 6 using the procedure i described above. Once your phone works, update to nougat and install twrp and root following this guide: https://forum.xda-developers.com/honor-8/development/twrp-t3566563
Same issue
Ramonator said:
Hi, after trying unlock my bootloader, I couldn't get into recovery mode without "Your phone cannot be trusted" getting stuck on my screen.
I re-locked the boot loader but now when I go into recovery it says "Data Partition is corrupted please format" then it asks me to connect to a wifi network which then just shows errors everytime the password comes up.
I tried to turn on USB Debugging to ADB sideload a firmware, but I can't because the phone has been resetted; if I try to enter a wifi password the keyboard doesnt show it's just the google voice (which doesn't work) with no options. If i skip the wifi option it just goes on the google login and gets stuck on "Checking Info".
Any solutions to the problem please?
EDIT: I just re-unlocked the bootloader and now its permanently stuck on "Your device cannot be trusted, booting now" regardless of what buttons I press during startup
EDIT 2: I fixed it, it was long and complicated but I got it to work, here's how.
1. When flashing TWRP, I realized I was flashing the TWRP for EMUI 4, so I flashed TWRP for EMUI 5. (Make sure Bootloader is unlocked)
First have all the adb/fastboot drivers, for windows shift + right click the folder and click "Open Command here"
Make sure the twrp img file is in the same folder as the adb folder.
On the honor 8 phone, if it is stuck like mine, turn the phone off and then hold Volume Down + Power Button until the download mode is on the screen
Type "fastboot flash recovery (twrpfilename).img"
Once it's done, turn it off and then hold power button + volume up AND volume down at once till TWRP comes on
(Continuously hold it, if the "Your Device cannot be trusted" screen comes on release)
2. (Make sure internal storage and data are backed up externally for this)
Reset system, data, cache/dalvik, and internal storage
3. Download Update.zip and the second .zip from a website on google, search Honor 8 Manual Nougat and click the link from smartstocknews (I can't post links) but do not follow the steps from that website, and also download GAPPS from open GAPPS. Make sure ARM64 is selected and not ARM as well as 7.0
4. After wiping, mount the Honor 8 by connecting it via USB to a computer, and press "Mount" on TWRP
Upload the both update.zip and update_data_full_hw_eu.zip and GAPPS ARM64 7.0 to internal or external storage
5. Exit mount and go to install, install the zips in this specific order and do not reboot in between
A) Update.zip
B) Update_data_full_hw_eu.zip
C) GAPPS.zip
6. Reboot after GAPPS is done (it might show already installed, if that's the case then it's alright, reboot anyways)
Click to expand...
Click to collapse
I pretty much have the same issue. No keyboard showing, just the stupid voice thing, and the Bootloader is Relocked. How did you get it fully unlocked. I can't get it. I guess let me get that resolved first (the bootloader) and I can try to go from there. Please help me.
UPDATE: Never mind I fixed it. I'm not really for sure how either but I think it mainly was just persistence.
Didn't work
Hello, so earlier today I tried to install RROS newest version in hope to get magisk/unrooting my phone because I'm addicted to snapchat and I rooted my phone with SuperSU earlier but didn't know u can't login to snapchat after that. It failed idk why, (I followed instructions very clearly and searched info from internet before doing that) causing me to brick my phone so when I booted it, it only showed black screen. After couple hours not finding way to get into twrp with my circumstances I managed to flash boot, recovery and system images, I tried to reboot and see what happens, (just in case, I kinda knew I didn't had ROM installed at the time, I also was hoping RROS to boot) nothing happened expect my phone got stuck in boot screen for booting EMUI, which was not installed obviously. Again after couple hours I stumbled to your post and managed to finally get myself into TWRP, I followed again ur instructions and everything was going fine, no erros, not anything. When Gapps was finished installing, I rebooted and again it just got stuck into booting screen. I did press and hold Power button, vol+, vol- and got myself into some kind of ROM installing screen, (hard to explain I don't exactly know what is name of it) and no it wasn't Huawei erecovery screen (Power button & Vol+ and no it didn't work me either saying that "getting package info failed") so in that ROM installing screen it just was stuck at 5% installing, and now I don't know what to do. My phone got locked again and I'm stuck at booting screen.
Note:
I don't have SD Card, should I get one and install stock rom?
Sorry for being kinda unclear but I'm tired it was 7 hours ago I got my phone bricked and have surfed on the web finding for answers ever since.
Also as you might notice, yes, I'm new to modding devices etc but still I'm not totally noob. Please help ASAP.
[SOLVED] So after hour of watching netflix as depressed teen I tried to reboot my phone again just in case, got stuck in booting screen. Then I held Power Button + Vol+ and got myself into EMUI stock recovery mode, I chose wipe cache partition and wipe data/factory reset, after that I rebooted my phone, it was stuck in booting screen for like 2 minutes but then it actually finished booting and now my phone is again functioning and god bless locked & unrooted.

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