Good day, don't know if this is right place to ask, have searched site for similar threads to no avail? I have a Samsung A10s, (sm-a107f) with Android 10, Magisk 22.1 installed, no ramdisk, SAR yes, flashed stock kernel with patched AP. Boot into Magisk via recovery, all good , phone rooted, but will no detect sim card, aeroplane mode dimly lit, cannot toggle, if i boot phone normally (no magisk root ) the siim card is detected, making me think that the problem lies with Magisk, could someone kindly advise, Cheers in advance. Bruce
Confused: Magisk Recovery? Never heard of that.
jwoegerbauer said:
Confused: Magisk Recovery? Never heard of that.
Click to expand...
Click to collapse
sorry maybe not explaining it clearly, will to to explain as I understand it. Because of no ramdisk, you install magisk into recovery, to get to magisk root you have to push power and volume up buttons as though you were wanting to boot into recovery, hence me calling it magisk recovery, if you just push power button the phone boots into unrooted mode, hope that explains it.
i
Hi still need help with original request , would really appreciate it. simple steps if you could
Related
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.
Hello,
I was using Magisk wihtout any issue until last update of my Mate 9. Now software version is 9.1.0.252 (C432E7R1P8) and as after every upgrade I re-patch my recovery_ramdis.img and patch from fastboot. In order to boot with root, I used recovery mode and it entered in system with root privileges. After the last update I did the same but recovery mode enters in recovery mode and system shows as non-rooted.
Please help, how to root my Mate 9?
hi, you must install busybox from magisk modules. But huawei changed file system to erofs. Because of some folders only read. We cant delete and change anything from system anymore.
And adaway is not working.
i downgraded to b191.
mavera said:
hi, you must install busybox from magisk modules. But huawei changed file system to erofs. Because of some folders only read. We cant delete and change anything from system anymore.
And adaway is not working.
i downgraded to b191.
Click to expand...
Click to collapse
Magisk does not change anything in system folder. Magisk is not enabled therefore I cannot install busybox. In Emui9 there was a workaround but seems it doesn't work anymore.
You must press to volume up and power buttons when opening for magisk enabling.
SonOfTheRain said:
Hello,
I was using Magisk wihtout any issue until last update of my Mate 9. Now software version is 9.1.0.252 (C432E7R1P8) and as after every upgrade I re-patch my recovery_ramdis.img and patch from fastboot. In order to boot with root, I used recovery mode and it entered in system with root privileges. After the last update I did the same but recovery mode enters in recovery mode and system shows as non-rooted.
Please help, how to root my Mate 9?
Click to expand...
Click to collapse
Huawei disabled booting to Recovery directly using Vol up and power, you end up in eRecovery instead. Easiest way is to flash magisk patched from fastboot, boot phone, enable USB Debugging in dev options (if you haven't already), and use adb to reboot. Command is:
adb reboot recovery
You can also flash patched image, boot to eRecovery and select the Wipe/Factory reset option, this will boot to recovery which is now Magisk so it'll boot to system with magisk. (Be careful though as the wipe command will still be there, so if you flash back recovery and boot to it your phone will automatically wipe. You can remove the file /cache/recovery/command to prevent this)
ante0 said:
Huawei disabled booting to Recovery directly using Vol up and power, you end up in eRecovery instead. Easiest way is to flash magisk patched from fastboot, boot phone, enable USB Debugging in dev options (if you haven't already), and use adb to reboot. Command is:
adb reboot recovery
You can also flash patched image, boot to eRecovery and select the Wipe/Factory reset option, this will boot to recovery which is now Magisk so it'll boot to system with magisk. (Be careful though as the wipe command will still be there, so if you flash back recovery and boot to it your phone will automatically wipe. You can remove the file /cache/recovery/command to prevent this)
Click to expand...
Click to collapse
Thank you for information. So we returned back to "tethered jailbreak" times with Apple Is there any workaround for this or so far the only solution? Wipe data option is quite unsafe for me, easy to forget and after firmware update to have a wiped device.
SonOfTheRain said:
Thank you for information. So we returned back to "tethered jailbreak" times with Apple Is there any workaround for this or so far the only solution? Wipe data option is quite unsafe for me, easy to forget and after firmware update to have a wiped device.
Click to expand...
Click to collapse
It will loop to recovery after you boot to magisk the first time, so each normal reboot will lead to Magisk. You can force eRecovery/normal boot if you plug in USB and boot holding vol up.
ante0 said:
It will loop to recovery after you boot to magisk the first time, so each normal reboot will lead to Magisk. You can force eRecovery/normal boot if you plug in USB and boot holding vol up.
Click to expand...
Click to collapse
It will loop to recovery if battery dies or if I shut down the phone and boot again or it will lead to non Magisk environment?
SonOfTheRain said:
It will loop to recovery if battery dies or if I shut down the phone and boot again or it will lead to non Magisk environment?
Click to expand...
Click to collapse
I haven't actually tested what happens if battery dies. It will loop if you shut down.
ante0 said:
I haven't actually tested what happens if battery dies. It will loop if you shut down.
Click to expand...
Click to collapse
I have rooted my device with 9.1 magisk but after root dialer and messaging app not worked and i rollback to 9.0 with very difficulty. If any one know how to root then i can told.
Azan Mughal said:
I have rooted my device with 9.1 magisk but after root dialer and messaging app not worked and i rollback to 9.0 with very difficulty. If any one know how to root then i can told.
Click to expand...
Click to collapse
https://forum.xda-developers.com/mate-10/how-to/fix-messages-dialer-9-1-root-required-t3955964
I need local.prop from product/etc/prop/local.prop from emui 9.1.0.252 any one 9.1 rooted user can help
Azan Mughal said:
I need local.prop from product/etc/prop/local.prop from emui 9.1.0.252 any one 9.1 rooted user can help
Click to expand...
Click to collapse
Here you go
SonOfTheRain said:
Here you go
Click to expand...
Click to collapse
Thanks bro
SonOfTheRain said:
Here you go
Click to expand...
Click to collapse
this file is for root?
Hi guys, so i have an untouched p10 on the version above, to install magisk is it as easy as asking one of you for the RECOVERY_RAMDIS.img (not yet in the firmware database) and patch it if it hasnt using pc then also on the pc rebooting to recovery and done? Also has restart and flat battery been tested? I read above that you must use shutdown
Its a vtr-l29 if it makes a difference
:crying:Hi guys,
I have rooted my OnePlus 7 with magisk and twrp installed.
I'm on latest oos 10.0.2.
I tried to install Edxposed framework via magisk and I ended I bootloop.
I couldn't enter recovery in between the bootloop so I waited until a full power down.
During bootloop the phone got heated up and I'm worried that the overheat generated might have effected my device hardware.
Can someone pls tell me about this..
Will something happen or already happened to my device hardware with that overheat???
Phvr said:
:crying:Hi guys,
I have rooted my OnePlus 7 with magisk and twrp installed.
I'm on latest oos 10.0.2.
I tried to install Edxposed framework via magisk and I ended I bootloop.
I couldn't enter recovery in between the bootloop so I waited until a full power down.
During bootloop the phone got heated up and I'm worried that the overheat generated might have effected my device hardware.
Can someone pls tell me about this..
Will something happen or already happened to my device hardware with that overheat???
Click to expand...
Click to collapse
Hello, there are thermal sensors that will prevent overheating. cpu will throttle down for example if the temperature is too high
GuestD1057 said:
:crying:Hi guys,
I have rooted my OnePlus 7 with magisk and twrp installed.
I'm on latest oos 10.0.2.
I tried to install Edxposed framework via magisk and I ended I bootloop.
I couldn't enter recovery in between the bootloop so I waited until a full power down.
During bootloop the phone got heated up and I'm worried that the overheat generated might have effected my device hardware.
Can someone pls tell me about this..
Will something happen or already happened to my device hardware with that overheat???
Click to expand...
Click to collapse
You will be fine, but you could always get in bootloader mode by holding both Volume and power button to shut it down, and them boot into bootloader.
Once you are in bootloader, boot your phone in recovery using fastboot boot recovery-image.
Once you are in recovery, you can do magisk uninstaller.
If you don't have those files on phone, you can run from adb
Boot into twrp and flash magisk disabler file
https://forum.xda-developers.com/apps/magisk/magisk-v16-3-magisk-modules-remover-t3776718/amp/
Hi all,
today I updated Magisk on my H830 (stock H83030c with TWRP) and now it's stuck in a boot loop.
Since the phone does not support flashing in fastboot, is there any way to fix this without re-flashing a stock kdz?
<edit>
The phone is showing the "bootloader unlocked warning", then flashes black and shows the warning again, over and over.
I can't enter TWRP, only fastboot and download mode.
Thanks,
schalli110
Never mind.
Mashing the power button like crazy finally got me into TWRP and I was able to reflash a stock boot.img and then an old version of Magisk.
Phew.
I'll leave this thread in the hopes it helps other poor souls.
I have the exact same problem (thanks Magisk team!). Can you expound on the power button technique that allowed you to access TWRP? By repeatedly pressing it?
Funny, I've seen multiple posts about this happening on G5 phones after the Magisk update, but nothing on the Magisk threads.
hello everyone, today i tried to flash twrp on my phone (rooted with magisk and running stock samsung rom), the flash was successful and i was able to boot into twrp but i coudnt access my storage or anything else, so i saw a guide saying to change the filesystem to ext2 then ext4, after i did that i could access most of the other folders but not the storage foldier as it still showed 0mb. i thought i just need to reboot my device to fix the issue but now im stuck on a bootloop. i cant poweroff the device since no button combination is currently working. is there anything i can do to power it off or do i have to wait a few days till the battery drains to 0?
[RECOVERY][UNOFFICIAL] TWRP for Galaxy A53 5G (Exynos)
Team Win Recovery Project 3.x, or twrp3 for short, is a custom recovery built with ease of use and customization in mind. Its a fully touch driven user interface no more volume rocker or power buttons to mash. The GUI is also fully XML driven and...
forum.xda-developers.com
this is the link i used to flash twrp except i didnt follow the wipe instructions because i dont want to use a custom os.
and if nothing else works and i have to wait a few days till it drains to 0, will i be able to boot back into samsung's recovery mode or is this device hard bricked?
help will be greatly appreciated.
This phone doesn't have the nice feature of holding the power button for force off so that is a negative here.
I don't think you should have edit:changed the partition types. If that was necessary it would be a ridiculous thing for other Android roms to have to do. Its all Android so should have worked without that.
Its unlikely that anything new will result from a cold boot verses a warm boot. Worth a shot I suppose but don't hold your breath. Expect nothing new.
If its stuck without Odin, fastboot, ADB, all buttons not doing anything, can't ingest and do something from sd card, can't show up via USB on computer, etc with nothing at all then its totally finished since nothing can be done. Consider it a loss and learn from it.
I'd like to also state that there are for some reason people who supposedly bring roms over to devices and they don't have the device so therefore don't really know if it works or not. You have to be careful about the guides you follow. I've seen someone try with a device that could not be unlocked ever for anyone and that person thought it would work. Live and learn.
sandsofmyst said:
This phone doesn't have the nice feature of holding the power button for force off so that is a negative here.
I don't think you should have edit:changed the partition types. If that was necessary it would be a ridiculous thing for other Android roms to have to do. Its all Android so should have worked without that.
Its unlikely that anything new will result from a cold boot verses a warm boot. Worth a shot I suppose but don't hold your breath. Expect nothing new.
If its stuck without Odin, fastboot, ADB, all buttons not doing anything, can't ingest and do something from sd card, can't show up via USB on computer, etc with nothing at all then its totally finished since nothing can be done. Consider it a loss and learn from it.
I'd like to also state that there are for some reason people who supposedly bring roms over to devices and they don't have the device so therefore don't really know if it works or not. You have to be careful about the guides you follow. I've seen someone try with a device that could not be unlocked ever for anyone and that person thought it would work. Live and learn.
Click to expand...
Click to collapse
hello, i was able to boot the phone into twrp and do a factory reset, i had to time the vol up + power button at exactly the time when the screen went black and it worked!. but now i have a question, if i want to get twrp again and i dont plan to flash a custom rom like it says in the guide, how do i get twrp to recognize my storage? and do you flash twrp before installing an os or after because ive done it after installing the os.
floppen22 said:
hello, i was able to boot the phone into twrp and do a factory reset, i had to time the vol up + power button at exactly the time when the screen went black and it worked!. but now i have a question, if i want to get twrp again and i dont plan to flash a custom rom like it says in the guide, how do i get twrp to recognize my storage? and do you flash twrp before installing an os or after because ive done it after installing the os.
Click to expand...
Click to collapse
yeah so it seems like the issue isnt with changing the file system or anything because i installed twrp again and tried rebooting and i got the same bootloop issue, but if i flash a rom then ill lose twrp like it happened last time so i dont understand what im supposed to do
you have to format data in twrp otherwise it won't see your storage folder.
once formatted reboot to twrp then reboot to system, it should reboot to stock rom and the set up pages.
beanbean50 said:
you have to format data in twrp otherwise it won't see your storage folder.
once formatted reboot to twrp then reboot to system, it should reboot to stock rom and the set up pages.
Click to expand...
Click to collapse
wipe>format data>type yes>reboot to recovery. i did that and still cant reboot to system bootloop issue persists
yes you did it correctly this time, is there anyway to undo your 'filesystem to ext2 then ext4'?
or maybe you have to flash the custom kernel to get it all up and running again
beanbean50 said:
or maybe you have to flash the custom kernel to get it all up and running again
Click to expand...
Click to collapse
how do i do that? the kernel folder in the guide doesnt have any tar or .img file to flash
floppen22 said:
how do i do that? the kernel folder in the guide doesnt have any tar or .img file to flash
Click to expand...
Click to collapse
it's a zip file so it should flash in twrp
beanbean50 said:
it's a zip file so it should flash in twrp
Click to expand...
Click to collapse
yes i was able to boot into my phone after flashing the kernel. thank you so much.
Try a different version of TWRP I remember this happened to me before and I installed a different version and it was fine