Database Info

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.

ROOT BLU R1 PLUS - R0051UU ROM 6.0 V13 - MT6737m

Unlock Bootloader and Root BLU R1 Plus
Yes it has been done
Thanks to @lopestom for all his help and porting TWRP to this device
Thanks to RootJunky for FRP Unlock.img
Thanks to Larry Miller for testing with his device
This has been done to Three 16 G devices and One 32 G device to date
WARNING:
Code:
[B][COLOR="red"]
DO NOT FLASH RECOVERY WITH SP FLASHTOOL AS IT
COULD BRICK DEVICE!![/COLOR][/B]
For use SPFT you need special file. So here's the best way is using ADB-fastboot to unlock bootloader, flash FRP Unlock.img and recovery!!
At all times it is necessary to think in safety not to have a bricked device.
Then for the uninformed users:
Code:
[B][COLOR="Red"]MAKE A BACKUP OF THE ROM WITH TWRP AND COPY FOR YOUR PC![/COLOR][/B]
This method uses adb and fastboot commands to achieve root
Before any actions: copy all that you need from SDcard internal to PC!
If you want backup calls, messages, contacts (different by goggle contatcs or if you can record all the contacts in your google contacts account directly through the contacts application).
For backup, use any application from google play! Save in your PC! After all the processes you can restore them using the same application that you used.
- Instructions to PROCESS:
1. On phone open setting
about phone, tap 7 times in build number
Enable Developer Options
Enable USB Debugging
2. On PC search the folder of adb and fastboot minimal ( included in zip to install }
Unzip and Place unlock.img , recoveryTWRP.img and SR3-SuperSU-v2.79-SR3-20170114223742.zip in adb and fastboot minimal folder
Open adb terminal
Code:
adb devices
to ensure connection
Code:
adb reboot bootloader
Code:
fastboot flash frp unlock.img
Code:
fastboot oem unlock
( Confirm with volume up select on phone )
Code:
fastboot flash recovery recoveryTWRP.img
Fastboot will show image flashed but due to BLUs locking of device fastboot reboot will not function
So ….
Unplug device , Hold power off until device turns off
Hold Volume up and Plug device back into PC ,
Continue to hold volume up until TWRP boots fully
Select Wipe , Select Format Data ( don’t worry if any errors show )
Reboot TWRP Recovery
Select Mount , Select Mount USB Storage
Open Device on PC , Move SR3-SuperSU zip to device external_sd
Unmount
Select Install
Select external_sd
Select SU zip and install in TWRP
Select Reboot System
Phone May reboot several time do not interrupt boot
Unlocked bootloader and TWRP
xposed arm v89 has been tested and works , Gravitybox 6.5.3 has been tested and works
Download link
TWRP_Root_R1_Plus.zip
mirror: TWRP Root R1 Plus.zip
William Smith
XDA:DevDB Information
[TUT] Unblocking & Unlocking - Installing TWRP - ROOT, Kernel for all devices (see above for details)
Contributors
lopestom, donnasbrt1
Source Code: https://forum.xda-developers.com/android/general/blu-blu-vivo-kernel-sources-t3767993
Kernel Special Features:
Version Information
Status: Stable
Current Stable Version: 1.0
Stable Release Date: 2018-09-18
Created 2018-09-19
Last Updated 2018-09-24

More in info: Stock ROM - TWRP - TWRP Backup - Lineage 14.1 (almost bug free)
Link of Stock ROM - TWRP - TWRP Backup - Lineage 14.1 (almost bug free)
Click me post #13
.

lopestom said:
Unlock Bootloader and Root BLU R1 Plus
Yes it has been done
Click to expand...
Click to collapse
This is too late for me. I returned this phone long ago.

Add one more 32G device, very happy now, this has been in the closet waiting for root and today it comes to life! Can't thank you enough!!! Works great!!!
---------- Post added at 12:53 AM ---------- Previous post was at 12:20 AM ----------
I installed SuperSU without thinking. Is it too late or is it possible to install Magisk instead?

Donphillipe said:
Add one more 32G device, very happy now, this has been in the closet waiting for root and today it comes to life! Can't thank you enough!!! Works great!!!
---------- Post added at 12:53 AM ---------- Previous post was at 12:20 AM ----------
I installed SuperSU without thinking. Is it too late or is it possible to install Magisk instead?
Click to expand...
Click to collapse
both of them have built in part of there install, a series of commands that remove other root, But is best to remove su before flash majisk. From the superSU app. in the menu is option to full remove superSU. Do that, then reboot make sure it is ok. Then try magisk. Note that it 'should' work, but it seems you will be first to try it.

Just tried to uninstall SuperUS and it no longer boots, locks up at the BLU screen. I was following these steps: https://android.gadgethacks.com/how-to/magisk-101-switch-from-supersu-magisk-pass-safetynet-0177578/
Should have made a backup when I had the chance. Oh, well it's like they say, live and forget and forget again.
So I guess I'll cross my fingers that this factory image I downloaded is not full of malware and is on the up and up.

The factory image I downloaded must be corrupt or something else is wrong. I tried flashing the factory image I downloaded "Blu_R0051UU_MT6737M_V13_REPAIR" and I received the error: ERROR: SBROM_DOWNLOAD_DA_FAIL (2004)
I still can boot to TWRP but I have no backup image in this format. If anyone has a factor or TWRP to share, please let me know.

Tried a different laptop, a couple of new cables and the error is still the same (see above) using the latest version of Flash Tool (v5.1828.01) to download the supposed stock ROM found online (http://www.mediafire.com/file/25su5934zm65vgb/Blu_R0051UU_MT6737M_V13_REPAIR.zip). I also deselected everything in Flashtool from the scatter file except "system" and it still would not load. Note that the only way to put the phone in a state that will communicate with the flash tool is to first hold the vol up and power button for a long time and keep holding them in until the BLU logo disappears and the TWRP menu appears. Here you select Reboot and then Power Off and only then will the flash tool try to communicate with the device when you plug the USB cable in. That's when the long red bar moves across the footer of the screen with 100% and a little later the error messages I named above occurs. Looks like I'm bricked unless I can find a kind soul to share a TWRP backup.

Donphillipe said:
Tried a different laptop, a couple of new cables and the error is still the same (see above) using the latest version of Flash Tool (v5.1828.01) to download the supposed stock ROM found online (http://www.mediafire.com/file/25su5934zm65vgb/Blu_R0051UU_MT6737M_V13_REPAIR.zip). I also deselected everything in Flashtool from the scatter file except "system" and it still would not load. Note that the only way to put the phone in a state that will communicate with the flash tool is to first hold the vol up and power button for a long time and keep holding them in until the BLU logo disappears and the TWRP menu appears. Here you select Reboot and then Power Off and only then will the flash tool try to communicate with the device when you plug the USB cable in. That's when the long red bar moves across the footer of the screen with 100% and a little later the error messages I named above occurs. Looks like I'm bricked unless I can find a kind soul to share a TWRP backup.
Click to expand...
Click to collapse
Larry Miller has also supplied a TWRP backup for this device ..thanks Larry
TWRP backup
Donphillipe said:
I installed SuperSU without thinking. Is it too late or is it possible to install Magisk instead?
Click to expand...
Click to collapse
With Supersu installed you can install Magisk and after remove suspersu......
Donphillipe said:
Just tried to uninstall SuperUS and it no longer boots, locks up at the BLU screen. I was following these steps: link
Should have made a backup when I had the chance. Oh, well it's like they say, live and forget and forget again.
So I guess I'll cross my fingers that this factory image I downloaded is not full of malware and is on the up and up.
Click to expand...
Click to collapse
After removed Supersu or Magisk the ROM can't start because have Custom recovery installed and made modified system option..... So in this case need install again supersu or magisk!
At all times it is necessary to think in safety not to have a bricked device.
Then for the uninformed users: MAKE A BACKUP OF THE ROM WITH TWRP AND COPY FOR YOUR PC!
Sent from my BLUBOO Xtouch using XDA Labs

Fixed, can't thank you enough!

Wiped the phone and did a full restore, everything looked good. I rebooted to TWRP tried to install Magisk V 17, 17.1 and 17.2 and all of them fail install with error;
! Boot image patched by unsupported programs
! Please restore stock boot image
Updater process ended with ERROR : 1
Error installing zip file xxxxxx
---------- Post added at 03:25 AM ---------- Previous post was at 03:10 AM ----------
Also fails SafetyNet check, not sure if it is supposed to or not. This is after restoring from the TWRP image supplied above and without rooting with SuperSU.

I no have the device in my hands. So you can install old version of magisk v15 or v16?
So if you need more information so you can enter here: BLU Development Team
Donphillipe said:
Wiped the phone and did a full restore, everything looked good. I rebooted to TWRP tried to install Magisk V 17, 17.1 and 17.2 and all of them fail install with error;
! Boot image patched by unsupported programs
! Please restore stock boot image
Updater process ended with ERROR : 1
Error installing zip file xxxxxx
Also fails SafetyNet check, not sure if it is supposed to or not. This is after restoring from the TWRP image supplied above and without rooting with SuperSU.
Click to expand...
Click to collapse

More in info on device R1 Plus
For anyone having issue with root or device issues .
If you can return to twrp and select power off this will allow required selection for so flashtool .Or if bootloop press and hold button combo and insert USB during power down of bootloop . Button combo for preloader is volume up and then power button then plug in device
Stock ROM here
https://www.mediafire.com/download/nbm2vt2dne5s2pc
TWRP
https://www.mediafire.com/download/hjmjpgepfbnjy7h
TWRP Backup
https://www.mediafire.com/download/eaxx8fla8a9a247
Lineage 14.1 (almost bug free)
https://www.mediafire.com/folder/fqqj9hqqascs0/Lineage 14.1 R1 Plus
Lineage has bug in OFF charging animation phone charges just no animation and rear camera macro focus
No other bugs have been found at this time
Xposed does work with this build v89-sdk25 arm
Thanks to Lopestom and Larry Miller for there support with this

donnasbrt1 said:
For anyone having issue with root or device issues .
If you can return to twrp and select power off this will allow required selection for so flashtool .Or if bootloop press and hold button combo and insert USB during power down of bootloop . Button combo for preloader is volume up and then power button then plug in device
Stock ROM here
https://www.mediafire.com/download/nbm2vt2dne5s2pc
TWRP
https://www.mediafire.com/download/hjmjpgepfbnjy7h
TWRP Backup
https://www.mediafire.com/download/eaxx8fla8a9a247
Lineage 14.1 (almost bug free)
https://www.mediafire.com/folder/fqqj9hqqascs0/Lineage 14.1 R1 Plus
Lineage has bug in OFF charging animation phone charges just no animation and rear camera macro focus
No other bugs have been found at this time
Xposed does work with this build v89-sdk25 arm
Thanks to Lopestom and Larry Miller for there support with this
Click to expand...
Click to collapse
Hello, which driver did you use? I can't get download mode work right

When loading bootloader ..power off device ...press volume up ..then power ( at the same time ) then plug device into pc ..device should load ..then device should flash .. do not flash preloader or imei issues may result

Any update on the progress lineage 14.1 on this phone? I use it for a day waa bit laggy

Not at this time Lineage 14.1 was a test run for the device and I have not had time to finish yet and am also working Resurrection Remix right now .Camera porting has been a bit tricky as there are alot...alot of simlinks on stock rom for camera functions . I will have more time soon to work on it a bit more

donnasbrt1 said:
Not at this time Lineage 14.1 was a test run for the device and I have not had time to finish yet and am also working Resurrection Remix right now .Camera porting has been a bit tricky as there are alot...alot of simlinks on stock rom for camera functions . I will have more time soon to work on it a bit more
Click to expand...
Click to collapse
Any update or ETA? I might put off a phone purchase if a build with a working camera comes along.... P.S. Another annoying bug I face is that videos don't play in some apps e.g. google photos, WhatsApp statuses and on Snapchat. Videos on Youtube and Facebook play fine. Fingers crossed for some good news! Wishing you a happy holiday season!

You can allways run stock rooted with xposed and gavitybox until bugs are worked out. Just a thought .Happy holidays to you also

+1 32G successful
Thanks for this! Waited for so long for a method.
Now: since I'm kinda newbie to root, I'm doubtful on how to detect custom kernels to flash based on this device model. Or is it possible to flash whatever?
I need something like 'ElementalX' or related.

one plus 6 p only boot to emergency mode !

hi all
need help
i try to install via
Magisk couple of things
the phone only boot to emergency mode after restart
i have open boot-loader and twrp installed
what can i do to fix that ?
thanks ahay

Magisk uninstaller flash that and it should remove all mods.

yes but can i install it 'the computer dont recognize the phone ?
i try to do hard reset 'but only twrp is coming after i hold down Volume Down and Power buttons for a couple of seconds.

i hope my phone is not dead

If you can get into TWRP, you can reboot to bootloader and flash the fastboot Zip from the following thread. It will wipe the data. You can also delete the data from twrp and see if it boots to system. A clean install would be better IMO. Good luck!
https://forum.xda-developers.com/oneplus-6/how-to/rom-stock-fastboot-roms-oneplus-6-t3796665

In TWRP, use adb push "filename" to /sdcard/ to get the uninstaller on your device. If you can boot into is after that, remove the magisk modules you most recently flashed. What module did you use?

9.1.0.252 (C432E7R1P8) root does not work

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

No bootloader access?

Hi there!
This is my first Samsung phone that I attempted to root. It's a Sprint Note 5 with *3DRH1 firmware, and it refuses to drop-down to bootloader level. Trying with either adb, or Vol+,Home,Power key press combination, or selecting "reboot to bootloader" from recovery ends up booting right back into system. I've read one mention about Sprint preventing such access, but is there a way around this?
That's one problem. The other is inability to flush (with Odin) the TWRP recovery, even though Odin reports success. After that, booting to recovery first displays "Installing system software" on a blue background, then a warning "No command", and only then ends up on native recovery.
The one thing I was successful in was to boot into Download mode, and I guess this would allow me to flush other original firmware. Is that right? What older firmware would allow me to root this phone? Is that the route to take, or is there magic trick/key press combination that can invoke the bootloader mode? Thanks for any pointers.

Note 5 doesnt have a bootloader
If you want to root or use any custom roms, you need TWRP,
Steps to root:-
1) Download the latest version of twrp for your device from TWRP's website
2) place it in AP in Odin
3) Close your phone then press Volume Down, Home Button, Power button simultaneously to boot to Odin/Download Mode
4) connect to your PC and flash twrp
5) Download Magisk v23 from Magisk's github.
6) use an OTG or place it on your phone's sdcard.
7) Install it from TWRP
The reason i said v23 instead of v24 is because Magisk Hide is off as default for v24, so, better to install v23 then update magisk later from its app.
Download TWRP for nobleltespr
Download TWRP Open Recovery for nobleltespr
dl.twrp.me
Release Magisk v20.3 · topjohnwu/Magisk
Fix magiskboot crashing when dealing with lz4_legacy format Full Changelog: here
github.com