Requirements / Downloads
Huawei VTR-L09 with unlocked bootloader (I not tested in other version)
Minimal ADB & Fastboot
Patched Recovery_Ramdisk VTR-L09
Rooting your device
1. Unzip Minimal ADB & Fastboot to any folder of your PC
2. Download the patched file for your device and copy it to Minimal ADB & Fastboot folder.
3. Start your smartphone in fastboot mode pressing [Vol-]+[Power] and connect it to your PC.
4. Open a Powershell window in your Minimal ADB & Fastboot folder by [Shift]+[Rightclick].
5. Flash the Recovery_Ramdisk:
Code:
fastboot flash recovery_ramdisk name_of_your_patched_file.img
Adjusting Magisk Manager and patching files by yourself
1. Download Magisk Manager to your phone and install.
2. Check "force encryption" and "AVB 2.0" boxes.
To patch yourself recovery_ramdisk:
3. a) copy the ORIGINAL RECOVERY_RAMDISK VTR-L09 PIE version 9.0.1.165 C432 to anywhere on your P10
b) Patch your *.img, that you have copied in any folder to your smartphone by pressing "Install" --> "Install" --> "Patch boot image" in Magisk Manager.
4. Transfer the patched file (You will find it in your download folder of your smartphone. It will be called "patched_boot.img".) to your PC, start Smartphone in fastboot mode and flash:
Code:
fastboot flash recovery_ramdisk name_of_your_patched_file.img
(You must adapt the file name to the real name of your file, e.g. patched_boot.img)
AFTER FLASHING YOUR PATCHED BOOT ON FASTBOOT, UNPLUG YOUR USB, PRESS [VOL+] + [Power], KEEP VOL+ UNTIL REBOOTS, IT WILL REBOOT ON YOUR SYSTEM ROOTED.
To actualize Magisk:
4.b) Choose in Magisk Manager: "Install" --> "Install" --> "Direct Install (Recommended)" --> Restart
espaciosalter20 said:
Requirements / Downloads
Huawei VTR-L09 with unlocked bootloader (I not tested in other version)
Minimal ADB & Fastboot
Patched Recovery_Ramdisk VTR-L09
Rooting your device
1. Unzip Minimal ADB & Fastboot to any folder of your PC
2. Download the patched file for your device and copy it to Minimal ADB & Fastboot folder.
3. Start your smartphone in fastboot mode pressing [Vol-]+[Power] and connect it to your PC.
4. Open a Powershell window in your Minimal ADB & Fastboot folder by [Shift]+[Rightclick].
5. Flash the Recovery_Ramdisk:
Code:
fastboot flash recovery_ramdisk name_of_your_patched_file.img
Adjusting Magisk Manager and patching files by yourself
1. Download Magisk Manager to your phone and install.
2. Check "force encryption" and "AVB 2.0" boxes.
To patch yourself recovery_ramdisk:
3. a) copy the ORIGINAL RECOVERY_RAMDISK VTR-L09 PIE version 9.0.1.165 C432 to anywhere on your P10
b) Patch your *.img, that you have copied in any folder to your smartphone by pressing "Install" --> "Install" --> "Patch boot image" in Magisk Manager.
4. Transfer the patched file (You will find it in your download folder of your smartphone. It will be called "patched_boot.img".) to your PC, start Smartphone in fastboot mode and flash:
Code:
fastboot flash recovery_ramdisk name_of_your_patched_file.img
(You must adapt the file name to the real name of your file, e.g. patched_boot.img)
AFTER FLASHING YOUR PATCHED BOOT ON FASTBOOT, UNPLUG YOUR USB, PRESS [VOL+] + [Power], KEEP VOL+ UNTIL REBOOTS, IT WILL REBOOT ON YOUR SYSTEM ROOTED.
To actualize Magisk:
4.b) Choose in Magisk Manager: "Install" --> "Install" --> "Direct Install (Recommended)" --> Restart
Click to expand...
Click to collapse
hi, I followed your guide, the root with magisk works, but the display at the extreme edges left and right are not working at touch.
do you have any advice for me.
Thank you
L29
Guide works fine with L29 too, sent email with patched recovery to OP.:good:
Worked on my VKY-L29, thanks a lot!
Update: Need some help! After any reboot magisk uninstall itself and lose the root, so it's impossible to install any module since I need to restart after installing them. Anyone with this problem? Someone knows what can it be causing this?
Piombofed said:
hi, I followed your guide, the root with magisk works, but the display at the extreme edges left and right are not working at touch.
do you have any advice for me.
Thank you
Click to expand...
Click to collapse
Idem here with my p10 vtr-l09c432 with firmware 9.0.1.163.
If i boot normal, i have android 9 without root and touch work fine.
If i boot with [vol+] + [power] from recovery workaround android start with right privileges and magisk work fine but from now the touchscreen no work at extreme left and right border for all height display, boring problem in keyboard and navigation top bar.
ps: i have manual patched my original extract recovery_ramdisk.img from update.app with magisk 18 and beta19, some result.
_neoxxx_ said:
Idem here with my p10 vtr-l09c432 with firmware 9.0.1.163.
If i boot normal, i have android 9 without root and touch work fine.
If i boot with [vol+] + [power] from recovery workaround android start with right privileges and magisk work fine but from now the touchscreen no work at extreme left and right border for all height display, boring problem in keyboard and navigation top bar.
ps: i have manual patched my original extract recovery_ramdisk.img from update.app with magisk 18 and beta19, some result.
Click to expand...
Click to collapse
Try also to report the problem directly on the magisk developer's forum, maybe if many of them report it, you can try to correct or make a Patch.
_neoxxx_ said:
Idem here with my p10 vtr-l09c432 with firmware 9.0.1.163.
If i boot normal, i have android 9 without root and touch work fine.
If i boot with [vol+] + [power] from recovery workaround android start with right privileges and magisk work fine but from now the touchscreen no work at extreme left and right border for all height display, boring problem in keyboard and navigation top bar.
ps: i have manual patched my original extract recovery_ramdisk.img from update.app with magisk 18 and beta19, some result.
Click to expand...
Click to collapse
I've seen this before on custom ROMs; the workaround I've used is, as root:
stop aptouch
If that does it, a magisk module that provides an empty file for /vendor/bin/aptouch_daemon (or a late start script that runs the above command) would correct it as well.
irony_delerium said:
I've seen this before on custom ROMs; the workaround I've used is, as root:
stop aptouch
......
Click to expand...
Click to collapse
You are rock bro!!
"stop aptouch" executed from root shell terminal work like a charm and touchscreen work again.
I reply with this solution in my open issues on official magisk github.
.. go to automate this at boot.
Now my question is: why aptouch is involved in root privilege escalation?
Update: i just add this to /system/etc/init/init.system.rc at end of file:
Code:
# Aptouch_daemon fix
service aptouch /system/bin/true
class late_start
disabled
oneshot
.. now at every boot my touch work again.
Does this problem appear for every vtl l29?
Do I have to invoke the command every boot?
Do this kind of "dual boot" will be "fixed"?
I hope will be fixed if possible, or rooting on pie will be annoying
RealPsygnosis said:
...
Do I have to invoke the command every boot?
Do this kind of "dual boot" will be "fixed"?
I hope will be fixed if possible, or rooting on pie will be annoying
Click to expand...
Click to collapse
.. Why? i reboot my phone every 3/4 weeks.
Only plus [vol+]..
No twrp or root annoying..
_neoxxx_ said:
You are rock bro!!
"stop aptouch" executed from root shell terminal work like a charm and touchscreen work again.
I reply with this solution in my open issues on official magisk github.
.. go to automate this at boot.
Now my question is: why aptouch is involved in root privilege escalation?
Update: i just add this to /system/etc/init/init.system.rc at end of file:
Code:
# Aptouch_daemon fix
service aptouch /system/bin/true
class late_start
disabled
oneshot
.. now at every boot my touch work again.
Click to expand...
Click to collapse
Congratulations, with stop aptouch magisk and touch working perfectly, the only problem with the script, copying and pasting doesn't work for me .. Do you have a solution? Thank you
Sorry for my English
Edit: I was writing the script directly from the phone, doing from pc now works perfectly..Thanks a lot
_neoxxx_ said:
You are rock bro!!
"stop aptouch" executed from root shell terminal work like a charm and touchscreen work again.
I reply with this solution in my open issues on official magisk github.
.. go to automate this at boot.
Now my question is: why aptouch is involved in root privilege escalation?
Update: i just add this to /system/etc/init/init.system.rc at end of file:
.. now at every boot my touch work again.
Click to expand...
Click to collapse
I don't think it's that it's involved in root. It's probably that something else isn't processed quite correctly, but I haven't figured out what yet myself. I've just disabled it in all of my custom builds since I determined that was causing problems and didn't seem to provide any functionality to a custom ROM, and it doesn't end up causing any problems.
That init snippet is actually pretty much the same as I use for disabling it. (You don't actually need to append it to an existing file, either - you can create a new one in /system/etc/init, so long as it has the '.rc' extension it'll be picked up by init.)
Root huawei p10 plus.
Hi guys. I read the guide to root my huawei p10 plus. But this is possible without bootloader unlock, or I need to first enable the bootloader unlock? Thank you soo much. Cheers
---------- Post added at 02:23 PM ---------- Previous post was at 02:19 PM ----------
Hello guys. I read the guide to root my huawei p10 plus, but I need to unlock bootloader first or I can do it with a bootloader disable? Thank you so much. Cheers
A way to install zips ??
Hi all guys, I followed this guide to root my P10 vtr-l09 with PIE and it works actually everything like a glance. I also edit init script for fixing the touch problem when started as root, thank to you all!!
But I wonder how I can install an installable .zip, for instance, with this configuration.
In other words ... In Oreo I had my device rooted, and I had TWRP 3.2.1 + Magisk. When I wanted to flash any installable .zip, I booted in twrp and install. Now, since I didn't find a TWRP 3.2.3+ suitable for Vtr-L09 (for Pie), I used this method for rooting my device .. but I can't install a flashable .zip as I wish.
Any suggestions?
( Sorry if this may appear as a dumb question to anybody... :laugh: )
Thanks in advance, and thanks for your hard work.
G.
Hello,
I'm unable to modify the init.system.rc file.
I tried nano directly on the phone (with su before) => Read-only file system
I tried with my computer (with su before) => Read-only file system
How do you mofify it please ?
Christian
---------- Post added at 12:50 PM ---------- Previous post was at 12:37 PM ----------
christrodr said:
Hello,
I'm unable to modify the init.system.rc file.
I tried nano directly on the phone (with su before) => Read-only file system
I tried with my computer (with su before) => Read-only file system
How do you mofify it please ?
Christian
Click to expand...
Click to collapse
Solved using a file explorer.
But why can't we do this via the commandline and su ?
Christian.
christrodr said:
Hello,
I'm unable to modify the init.system.rc file.
I tried nano directly on the phone (with su before) => Read-only file system
I tried with my computer (with su before) => Read-only file system
How do you mofify it please ?
Christian
---------- Post added at 12:50 PM ---------- Previous post was at 12:37 PM ----------
Solved using a file explorer.
But why can't we do this via the commandline and su ?
Christian.
Click to expand...
Click to collapse
You can - but you have to make sure that system is mounted r/w. A file explorer will remount the filesystem for writing so it can modify the file. And, of course, on the command line, you're best off doing it through /sbin/.core/mirror/system (iirc), not /system - you may end up modifying the tmpfs mounted by Magisk depending on what you've got installed as far as modules go.
irony_delerium said:
You can - but you have to make sure that system is mounted r/w. A file explorer will remount the filesystem for writing so it can modify the file. And, of course, on the command line, you're best off doing it through /sbin/.core/mirror/system (iirc), not /system - you may end up modifying the tmpfs mounted by Magisk depending on what you've got installed as far as modules go.
Click to expand...
Click to collapse
Ok,
Thanks for the explanation.
gabolander said:
Hi all guys, I followed this guide to root my P10 vtr-l09 with PIE and it works actually everything like a glance. I also edit init script for fixing the touch problem when started as root, thank to you all!!
But I wonder how I can install an installable .zip, for instance, with this configuration.
In other words ... In Oreo I had my device rooted, and I had TWRP 3.2.1 + Magisk. When I wanted to flash any installable .zip, I booted in twrp and install. Now, since I didn't find a TWRP 3.2.3+ suitable for Vtr-L09 (for Pie), I used this method for rooting my device .. but I can't install a flashable .zip as I wish.
Any suggestions?
( Sorry if this may appear as a dumb question to anybody... [emoji23] )
Thanks in advance, and thanks for your hard work.
G.
Click to expand...
Click to collapse
Any suggestions?
Inviato dal mio VTR-L09 utilizzando Tapatalk
gabolander said:
Any suggestions?
Inviato dal mio VTR-L09 utilizzando Tapatalk
Click to expand...
Click to collapse
Go to the mate9 forums and find unofficial build topic for RR, in that topic you have twrp which works on P10 but just for .zip installation. Backup doesn't work because of encryption and i didn't tried .img installation.
Here is the link to topic: https://forum.xda-developers.com/mate-9/development/rom-resurrection-remix-v7-0-t3911232
Papolak said:
Guide works fine with L29 too, sent email with patched recovery to OP.:good:
Click to expand...
Click to collapse
can you send em here too ?? this is my telegram acc https://t.me/d0nf1rd
Related
I posted this a while ago in the [sm-a320fl][7.0][firmware] thread. Now in a new thread, so everybody will find it.
I'm not responsible for any damage. My phone was not branded.
This tutorial is only for SM-A320FL, also known as Galaxy A3!
Make sure you read the whole tutorial before doing anything.
Make a backup of your data. You need to make a factory reset!
Also read the additional information in the separated threads! Knox will be tripped after that, so you can't use it any more. And no more Warranty!
You can find a Android 7 version with the latest security patch with google or just use the linked one. Make sure the CSC is correct for your country/language.
1. Download the following stuff:
Android 7 A320FLXXU1BQH7_A320FLOXA1BQH7_A320FLXXU1BQG6.zip thx to tys0n
Latest Odin3
twrp_3.1.1-1_sm-a320f_11917 thx to ashyx
[*]Boot image patch no-verity-no-encrypt_ashyx thx to ashyx
[*][UNOFFICIAL] Material Design Xposed Installer [09/09/17] thx to DVDandroid
Xposed Installer 3.1.5 thx to rovo89
Magisk thx to topjohnwu
2. Flash Android 7 via Odin. There are enough tutorials on how to do that. Basicly unzip the Android 7 zip file and assign the AP_... file to the AP slot, the BL_... file to the BL slot and so on.
2.a Unlock OEM: Settings -> Developer Options -> OEM unlocking More Information
3. Flash TWRP via Odin; Thread with additional informations
Instructions summary:
Flash with ODIN 3.10.7 in the AP slot.
Put your device in DOWNLOAD mode.
Uncheck Auto reboot.
Load the respective file below into the AP slot and hit start.
After flashing and ODIN reports PASS immediately reboot to recovery by holding POWER + VOL DOWN.
As soon as the screen goes blank change to VOL UP whilst holding POWER + HOME.
You should now see TWRP recovery.
Click to expand...
Click to collapse
4. Now install via TWRP the Boot image patch no-verity-no-encrypt_ashyx. To do that, just copy the zip file to your SD card. Go to TWRP and install it with the Install option within TWRP. Reboot to System.
4. Format Data in TWRP. To do that click on Wipe -> Format Data in TWRP. After that all your data is lost! Reboot to System.
5. Copy the Xposed Installer APK file to your SD card and install the APK. Make sure you have third party sources enabled. Reboot to TWRP.
6. Copy the Magisk ZIP file to your SD card and install it via TWRP. Reboot to System.
7. Open the Magisk Manager and enable root access via SuperUser within the Manager.
8. Open the Magisk Manager and search for Xposed Framework SDK 24. You need the SDK 24 or else it won't work. Install Xposed.
8. Open Xposed Installer and install the latest Xposed framework. Follow the steps displayed.
9. Now you should have root access, Magisk and Xposed up and running.
Quotes and additional information:
[RECOVERY][ROOT][TWRP 3.1.1-1] Galaxy A3 - SM-A320F/FL/Y (2017) by ashyx
[*][UNOFFICIAL] Material Design Xposed Installer [09/09/17] by DVDandroid
[2017.9.6] Magisk v14.0 - Root & Universal Systemless Interface [Android 5.0+] by topjohnwu
[*][2017.9.9][Magisk][SDK 21-25] Xposed v87.3 - Universal Systemless Compatibility by topjohnwu
[OFFICIAL] Xposed for Lollipop/Marshmallow/Nougat/Oreo by rovo89
---------- Post added at 11:22 AM ---------- Previous post was at 11:07 AM ----------
khanvict90 said:
Any body else have lag with the patern unlock screen ?
Click to expand...
Click to collapse
I had the same problem and it drove me crazy. It appeared every time after I rooted my phone with the old "flash the SuperUser.zip via TWRP" method.
After I rooted my phone via Magisk (Tutorial above), there is no more annoying lag. :good:
Trying to install sdk25/sdk25 and getting an error:
Wrong Android version:
This file is for: SDK25
Please download the correct package
for your Android version
Failed
Installation error
simple_s said:
8. Open the Magisk Manager and search for Xposed Framework SDK 24. You need the SDK 24 or else it won't work. Install Xposed.
Click to expand...
Click to collapse
Anyway, I face the lockscreen lag even if I use Magisk to root my phone. So, sadly no luck for me...
Thanks for the tutorial.
I have two questions.
1. is it needed to use the Xposed installer by DVDandroid, or does the official one do the same job when using Xposed Magisk module?
2. I read you end in a bootloop when using the Magisk way on the Superman ROM thread for S7
https://forum.xda-developers.com/showpost.php?p=74048136&postcount=11120
answer here
https://forum.xda-developers.com/showpost.php?p=74054639&postcount=11125
does this also happen with A320FL? I installed Xposed in system because of that and have no problems.
y2klol said:
Trying to install sdk25/sdk25 and getting an error:
Wrong Android version:
This file is for: SDK25
Please download the correct package
for your Android version
Failed
Installation error
Click to expand...
Click to collapse
Please read the tutorial! You need SDK 24 if you are on Android 7.
Pat750 said:
Thanks for the tutorial.
I have two questions.
1. is it needed to use the Xposed installer by DVDandroid, or does the official one do the same job when using Xposed Magisk module?
Click to expand...
Click to collapse
I didn't try that. Maybe it will work.
Pat750 said:
2. I read you end in a bootloop when using the Magisk way on the Superman ROM thread for S7
https://forum.xda-developers.com/showpost.php?p=74048136&postcount=11120
answer here
https://forum.xda-developers.com/showpost.php?p=74054639&postcount=11125
does this also happen with A320FL? I installed Xposed in system because of that and have no problems.
Click to expand...
Click to collapse
In my opinion it will do the same thing and get stuck in a boot loop. Didn't try it.
simple_s said:
Please read the tutorial! You need SDK 24 if you are on Android 7.
In my message I stated that I tried both sdk24 and sdk25 neither worked. I only posted the error message for sdk25 but it was the same for 24.
Click to expand...
Click to collapse
y2klol said:
Trying to install sdk25/sdk25 and getting an error:
Wrong Android version:
This file is for: SDK25
Please download the correct package
for your Android version
Failed
Installation error
Click to expand...
Click to collapse
y2klol said:
In my message I stated that I tried both sdk24 and sdk25 neither worked. I only posted the error message for sdk25 but it was the same for 24.
Click to expand...
Click to collapse
In your original post you wrote SDK25 twice. So it is not obvious you meant SDK24 and SDK25.
I'm sorry that it didn't work for you. Did you use all the files in the tutorial? What phone do you have and what Android 7 version?
Is it normal that the system takes a while to boot after flashing no verity no encrypt?
Should i hard reset? It is been like 5 mins
ii_Troy said:
Is it normal that the system takes a while to boot after flashing no verity no encrypt?
Should i hard reset? It is been like 5 mins
Click to expand...
Click to collapse
I had the same issue - turns out I missed the formatting step in TWRP.
Before flashing no verity, go to Wipe > Format Data Partition (I cant remember the exact wording)
simple_s said:
In your original post you wrote SDK25 twice. So it is not obvious you meant SDK24 and SDK25.
I'm sorry that it didn't work for you. Did you use all the files in the tutorial? What phone do you have and what Android 7 version?
Click to expand...
Click to collapse
Oh yes, I did. My apologies. It's A5 (2017) and the firmware is A520FXXS2BQJ1 - Galaxy A5 SM-A520F OPS Australia (Optus). Do I have to use the one posted? What is that?
y2klol said:
Oh yes, I did. My apologies. It's A5 (2017) and the firmware is A520FXXS2BQJ1 - Galaxy A5 SM-A520F OPS Australia (Optus). Do I have to use the one posted? What is that?
Click to expand...
Click to collapse
I only tried this tutorial on an A3. Especially the firmware and the TWRP are specialised for the A3. I think the A5 has also quite a different hardware.
Maybe someone in this thread can help you. They root A5:
A5 Root
All works great on my Galaxy A320FL, thanks !!
atlantix1 said:
Anyway, I face the lockscreen lag even if I use Magisk to root my phone. So, sadly no luck for me...
Click to expand...
Click to collapse
its because you fllashed no verify no encrypt this zip should only be flash when you root with super su ...
am i the only one here finding this tutorial poorly written? example:
"4. Now install via TWRP the Boot image patch no-verity-no-encrypt_ashyx. To do that, just copy the zip file to your SD card. Go to TWRP and install it with the Install option within TWRP. Reboot to System."
if you that and you decide to root with magisk you are fked you are gonna face the lock screen delay after you enter the password.
"5. Copy the XposedInstaller_by_dvdandroid_09_09_17.apk file to your SD card and install the APK. Make sure you have third party sources enabled. Reboot to TWRP."
do we install it?? do we just leave it there???
"8. Open the Magisk Manager and search for Xposed Framework SDK 24. You need the SDK 24 or else it won't work. Install Xposed. "
witch means = find the module and install it, then enable it, then reboot. now go to exposed and install it then reboot again, now you do have it.
by the way sorry for my bad english .
Hi there.
I found something interesting by accident.
Maybe it is not necessary to install the Xposed Framework via Magisk.
Just use the Magisk Manager as a Super SU replacement and install the Xposed Framework (latest version is 89) directly via the new Xposed Installer (latest version is 3.1.5).
Official Xposed by rovo89
It seems that the phone is running a little bit smoother.
Also it seems that the boot patch is causing some problems.
Maybe the whole tutorial needs to be overlooked. But unfortunately I have now time right now.
nekos95 said:
am i the only one here finding this tutorial poorly written? example:
"4. Now install via TWRP the Boot image patch no-verity-no-encrypt_ashyx. To do that, just copy the zip file to your SD card. Go to TWRP and install it with the Install option within TWRP. Reboot to System."
if you that and you decide to root with magisk you are fked you are gonna face the lock screen delay after you enter the password.
"5. Copy the XposedInstaller_by_dvdandroid_09_09_17.apk file to your SD card and install the APK. Make sure you have third party sources enabled. Reboot to TWRP."
do we install it?? do we just leave it there???
"8. Open the Magisk Manager and search for Xposed Framework SDK 24. You need the SDK 24 or else it won't work. Install Xposed. "
witch means = find the module and install it, then enable it, then reboot. now go to exposed and install it then reboot again, now you do have it.
by the way sorry for my bad english .
Click to expand...
Click to collapse
Sorry to hear that. Maybe you can write a new and better one.
simple_s said:
Sorry to hear that. Maybe you can write a new and better one.
Click to expand...
Click to collapse
i kinda just did ... insteed of being ironic you should fix what you did wrong here , you might not realising this but not everyone here has experience to figure things out by himself and your tutorial is causing issues .
nekos95 said:
am i the only one here finding this tutorial poorly written? example:
"4. Now install via TWRP the Boot image patch no-verity-no-encrypt_ashyx. To do that, just copy the zip file to your SD card. Go to TWRP and install it with the Install option within TWRP. Reboot to System."
if you that and you decide to root with magisk you are fked you are gonna face the lock screen delay after you enter the password.
"5. Copy the XposedInstaller_by_dvdandroid_09_09_17.apk file to your SD card and install the APK. Make sure you have third party sources enabled. Reboot to TWRP."
do we install it?? do we just leave it there???
"8. Open the Magisk Manager and search for Xposed Framework SDK 24. You need the SDK 24 or else it won't work. Install Xposed. "
witch means = find the module and install it, then enable it, then reboot. now go to exposed and install it then reboot again, now you do have it.
by the way sorry for my bad english .
Click to expand...
Click to collapse
Sorry I have to replay again. I had just a few minutes this morning.
At point 5 I clearly wrote that you have to install the apk!
At point 8 it should be clear that you have to follow the instructions from Xposed. Everybody knows that and has nothing to do with the basic tutorial.
nekos95 said:
i kinda just did ... insteed of being ironic you should fix what you did wrong here , you might not realising this but not everyone here has experience to figure things out by himself and your tutorial is causing issues .
Click to expand...
Click to collapse
Xposed, Root and what not is nothing for beginners. I clearly mentioned that you have to read a lot of stuff. This is not for beginners. Instead of whining and telling me how to do stuff, just write your own thread. Link everything and mention resources. Not everything in this world is baby save. You have to educate yourself!
I overlooked the whole tutorial. I think it is better now and baby save.
Hello,
I cannot get this to work.
Flashing Android 7.0 works
Installing TWRP works
Installing the xposed apk works
but after flashing the magisk zip file i get the message "verification failed" when trying to boot
How can i fix this?
Edit: I managed to fix it. I had to format after install TWRP
BananaOctopus said:
Hello,
I cannot get this to work.
Flashing Android 7.0 works
Installing TWRP works
Installing the xposed apk works
but after flashing the magisk zip file i get the message "verification failed" when trying to boot
How can i fix this?
Edit: I managed to fix it. I had to format after install TWRP
Click to expand...
Click to collapse
Thank you for your help. I updated my phone to the newest Android 7 version today. I had the same problem and solved it with your method. So I implemented this step into the tutorial.
Warning!!! I’m not responsible for anything (death, destruction, or nuclear war) which happens to you & your stuffs after following this guide.
Downloads :-
RR-Magisk-Root-vivo-Y51L.zip
TipsyOS Prerooted ROM
How to Install ?
1. Make sure you have RR rom installed(Get it Here) before flashing RR-Magisk-17.2-vivo-Y51L.zip
2. Reboot to TWRP recovery
3. Install RR-Magisk-17.2-vivo-Y51L.zip or TipsyOs-prerooted.zip, whatever your choice is.
4. Reboot to System.
5. If root worked, Come back and the hit the thanks button below!
:Video Tutorial on the same:
https://www.youtube.com/watch?v=omUggCUJGGk
-:NOTES FOR VIVO Y51L DEVS:-1. Played with Magisk once for around 3 hours
2. You wanna know ? Seriously ? Okay
3. Disable Selinux which isn't needed by root ! (Just for fun)
4. Downlad Magisk-latest.zip
5. Extract magiskinit from arm folder
6. Push magiskinit to /data/local/tmp
7. Run :
adb shell
cd data/local/tmp
chmod 755 magiskinit
./magiskinit -x magisk magisk
exit
adb pull /data/local/magiskinit8. Now you will get an file with name magisk in the current dir
9. Place it in the /system/xbin/ folder of your rom
10. Place Magisk Manager apk in /sytem/app/Magisk
11. Now, boot.img part :
Following things to be done in boot.img :
Created /sbin/permissive.sh
Patched default.prop, fstab.qcom, init.environ.rc, init.rc, init.recovery.service.rc, init.root.rc, init.superuser.rc (create one if..), sepolicy, service_contexts
If you wanna know the stuff i added in these files, just search 'Naveen' in all those files (Yeah, i reckon that, i'm Superlazy to find & write those here even though i can write 55wpm)12. What about how to patch sepolicy ? Uh, I used supolicy by @Chainfire (Thanks man....)
13. How to find selinux denies ? Install audit2allow in your linux system & :
adb shell dmesg | audit2allow -p (your sepolicy here, use 'adb pull /sys/fs/selinux/policy') > selinux.error
Now push supolicy to phone (Download SuperSU.zip)
adb push ./ /data/local/tmp/tony/
adb shell
cd /data/local/tmp/tony/
chmod 755 *
./supolicy --live "error here"
./supolicy --save /data/local/tmp/tony/new_sepolicy
exit
adb pull /data/local/tmp/tony/new_sepolicy
Rename new_sepolicy to sepolicy & replace your original one in boot.img
Repack your boot.img13. This won't work with stock rom since we get operation not permitted errors while trying to exec su, i think it's Linux Capabilities (Read more about that here : http://man7.org/linux/man-pages/man7/capabilities.7.html) Don't ask me why it works in cm roms if kernel is the problem
14. Whatever you wanna ask me, reply here please (I'm don't check private messages anymore)
Official Telegram Group for Vivo Y51L/Y21L : https://t.me/vivodevelopment
Fix for bugs
Please fix the bugs asap....i am facing audio and video playback problems
#ask
are you facing mic and call problem?
use y51l kernal
bro.
can you use y51l kernal to patch file?
so that y51l may get rooted with no bugs
Bugs are there
*Front camera not working
*Flash light not working
*Magisk not installing
y51 kernal source restore
can you make tutorial to restore y51 kernal source .also there a wifi bug wont turn on
device stuck at app starting up....pls hlp
installed the miui root boot.img and twrp.img but after rebooting the device was stuck
Can't root
How to download
Magisk cannot run in third-party ROM
It's a pity that my favorite ROM cannot be ROOT. It's not that the installation fails, but it always stops working.
I have a more useful method for rooting vivo y51L
Requirements:-
OTG
Data cable
A second phone
Bootloader unlock
Bugjaeger application
Root checker application
Your custom ROM or stock ROM zip file
Firstly we have to unzip our stock or custom ROM zip file, after unzipping file we have to move out boot.img file and save it in our internal storage . After that we have to flash the boot.img file in magisk and after flashing we will get a magisk patch in our download folder . We have to send that patch to our second phone and save it in it's internal storage .after that we have to boot our phone in fastboot mode and for that we have to power off our device and press volume down and power button .After booting the device in fastboot mode you have to connect otg in your second device and data cable in fastboot device . After that connect data cable and otg , after connecting the Bugjaeger application will open automatically . after that find an icon which looks like lightning in app and click that , after that you will find a blue dot at the bottom of the screen . Click that button and you will get inside command section after that type the first command :- Fastboot devices and click the play button at the right side. After that you will see a serial number which means you are connected. After that write the second command :- Fastboot flash boot , after writing it we will find a paper clip type button at the top right corner , just click that and attach the magisk patch which we sent to our second device and tap the play button at the right side . After the command has succeeded we have have to reboot our fastboot phone after removing data cable and otg . After rebooting just open root checker application and keep internet on , Click on verify root. Your phone is rooted now.
Now do whatever you want to do
Fun fact :- this method works on every phone
Those who want to say me thanks for this method please reply me
Bypass bootloader guide https://forum.xda-developers.com/xiaomi-redmi-5a/how-to/bypass-bootloader-lock-redmi-5ariva-t3772381 by dev @xaacnz.
A little bit of disclaimer......
Appender is for those who are currently using bypass bootloader hack above, so there is no need of manually appending blocks to boot image/recoevry image after every flash. Appender automatically appends the 4k bytes to boot image and recovery image.
NOTE: DO NOT QUOTE WHOLE POST OR I WILL IGNORE
Appender-v4 Download below
Changelog:
Appender-v4
*Fixed Appender on system-as-root boot images (Appender breaks GSI with system-as-root, don't use GSI)
*Improved overall code
Appender-v3
*Initial test version
Recommended twrp: Pitch black recovery
Link
Appender-v4.zip is for boot image
Appender-v4-rec.zip is for recovery image
Appender Usage
1. Flash rom
2. Flash magisk for root (skip if you don't need root)
3. Flash custom kernel (skip if you don't need custom kernel)
4. After that flash Appender-v4.zip
5. Reboot
Appender Recovery Version Usage
1. Flash recovery image
2. Flash Appender-v4-rec.zip
3. Reboot Recovery
CAUTION: Appender must be flashed EVERY time you modify boot image or recovery image.
And don't forget to press thanks if this tool has helped you
Reporting errors.
After flashing appender, send the file /cache/recovery/last_log if Appender didn't worked, and also metion the issue you are facing.
Credits and thanks
@osm0sis for Anykernel3
@xaacnz for bypass bl guide
steeldriver (stackexchange) for helping me with commands
busybox team
Old method
Note1: Even though no data is erased in this process it is recommended to take backup.
What this guide covers.
1. Rooting your device
2. Flashing custom kernel
All without need to unlock bootloader
Well there are two ways with which you can do this
Requirements
For PC based method
1. Working twrp recovery (if you dont have twrp installed follow this guide)
2. Pc must have linux installed, if you have windows don't worry install WSL using this link
3. Android image kitchen for your respective OS.
4. Latest magisk zip from here
For Android only
1. Working twrp
2. Any hex editor(Note2) for android/windows (optional)
3. Latest Magisk manager app only (for root only)
4. Android Image kitchen- android, windows/linux (for custom kernel only)
Steps for PC based1. Flash magisk zip or any kernel. Don't reboot system.
2. Go to backup senction in twrp and backup boot.
3. Connect your device to PC and look where you backed up boot and copy boot.emmc.win to Android image kitchen folder and rename to boot.img
4. Run unpackimg.sh or double click on unpackimg.bat. Then run repackimg.sh or double click on repackimg.bat. You will see image-new.img in the same folder
5. On windows hold Shift and right click in file manager with mouse, you will see open linux shell here, click it. OR if you have linux (specifically ubuntu) then right click and select open terminal here in Nautilus.
6. Run (to append 4k block, note that you can append block to any file specified by "of" parameter like of=twrp.img, of=boot.img etc)
Code:
printf 'x30x83x19x89x64' | dd of=image-new.img ibs=4096 conv=sync,notrunc oflag=append
7. Copy the image-new.img to your phone anywhere you prefer.
8. Flash image-new.img using twrp to boot partition.
9. Reboot
Steps for non-PC based (*outdated and some kernels won't work fully)[/CENTER]
1. Extract boot.img from your currently installed rom and put it in internal storage of your phone (if you do not want to flash custom kernel skip to step 4)
*2. Download custom kernel you want to flash, extract zImage from the flashable kernel zip
*3. Unpack boot image using android image kitchen, in the split_img folder delete "boot.img-zImage" and put zImage you extracted in split_img folder and rename it to "boot.img-zImage"
*For custom kernel only
4. Install magisk manager apk on your phone
5. open magisk manager, you will see magisk is not installed select install (first one), a popup will appear telling to install magisk, select install, then select Patch a file, select the boot.img file that you extracted, then let magisk manager do the rest, after finishing the magisk-patched.img file will be stored in Downloads folder of your internal storage
6. Open the patched_boot.img in hex editor
7. To make the patched_boot.img to boot append(Note2) a 4k block which begins with 0x30, 0x83, 0x19, 0x89, 0x64 to patched_boot.img, and save the file
8. Boot into twrp and flash patched_boot.img
9. Done, reboot
Note2: On Linux you can use dd command to append
Code:
printf 'x30x83x19x89x64' | dd of=testfile ibs=4096 conv=sync,notrunc oflag=append
Note3: If you get error cannot mount twrp while flashing, use recommend twrp above
If you get error related to ramdisk compression, use Appender-v4 or above
XDA:DevDB Information
Appender for Redmi 5A (bypass bootloader), Tool/Utility for the Xiaomi Redmi 5A
Contributors
saurabh6377
Version Information
Status: Beta
Current Beta Version: 4
Beta Release Date: 2019-09-29
Created 2019-09-28
Last Updated 2019-09-29
Reserved
_saurabh__._ said:
As a followup to this guide https://forum.xda-developers.com/xiaomi-redmi-5a/how-to/bypass-bootloader-lock-redmi-5ariva-t3772381 by dev @xaacnz without him this guide might not be here, I am making this guide so you can root your device or flash any custom kernel without unlocking your device.
Code:
Your warranty will be void now
I am not responsible for anything wrong happens to your device
Note1: Even though no data is erased in this process it is recommended to take backup.
What this guide covers.
1. Rooting your device
2. Flashing custom kernel
All without need to unlock bootloader
Requirements
1. Working twrp recovery (if you dont have twrp installed follow this guide)
2. Any hex editor for android/linux/windows (yes you absolutely dont need a pc)
3. Latest Magisk manager app only (for root only)
4. Android Image kitchen- android, windows/linux (for custom kernel only)
Steps1. Extract boot.img from your currently installed rom and put it in internal storage of your phone (if you do not want to flash custom kernel skip to step 4)
*2. Download custom kernel you want to flash, extract zImage from the flashable kernel zip
*3. Unpack boot image using android image kitchen, in the split_img folder delete "boot.img-zImage" and put zImage you extracted in split_img folder and rename it to "boot.img-zImage"
*For custom kernel only
4. Install magisk manager apk on your phone
5. open magisk manager, you will see magisk is not installed select install (first one), a popup will appear telling to install magisk, select install, then select Patch Boot Image File, select the boot.img file that you extracted, then let magisk manager do the rest, after finishing the patched_boot.img file will be stored in Downloads folder of your internal storage
6. Open the patched_boot.img in hex editor
7. To make the patched_boot.img to boot append a 4k block which begins with 0x30, 0x83, 0x19, 0x89, 0x64 to patched_boot.img, and save the file
8. Boot into twrp and flash patched_boot.img
9. Done, reboot
Note2: If you get error cannot mount twrp while flashing the image, use vendor twrp
Note3: If I get time I will later make a script that automates the process.
Click to expand...
Click to collapse
Thanks it worked but i didn't appended 4k block to patched_boot.img it worked without appending 4k block.
Sonu1123 said:
Thanks it worked but i didn't appended 4k block to patched_boot.img it worked without appending 4k block.
Click to expand...
Click to collapse
Let me verify this, I will update the guide once this is verified.
Sonu1123 said:
Thanks it worked but i didn't appended 4k block to patched_boot.img it worked without appending 4k block.
Click to expand...
Click to collapse
If you didn't append 4k block to patched_boot.img and you have locked bootloader then flashing magisk directly from twrp must work also because both processes are same. And likewise you can also flash custom kernel directly using twrp without extracting boot.img. In my case I have to append 4k block to patched_boot.img for system to boot.
_saurabh__._ said:
If you didn't append 4k block to patched_boot.img and you have locked bootloader then flashing magisk directly from twrp must work also because both processes are same. And likewise you can also flash custom kernel directly using twrp without extracting boot.img. In my case I have to append 4k block to patched_boot.img for system to boot.
Click to expand...
Click to collapse
I don't know how it worked but when i tried it again system crashed then i appended 4k block to patched_boot.img to get magisk intalled.
I have one more question what about xposed for pixel experience rom for riva and can i flash it directly without modifying it.
Edit:I am on pixel experience latest android pie version.
Sonu1123 said:
I don't know how it worked but when i tried it again system crashed then i appended 4k block to patched_boot.img to get magisk intalled.
I have one more question what about xposed for pixel experience rom for riva and can i flash it directly without modifying it.
Edit:I am on pixel experience latest android pie version.
Click to expand...
Click to collapse
Yes you can install xposed. Simple rule of thumb is that you can flash anything that does not touch boot image and xposed doesn't it only writes to /system partition so no issues.
Xposed is not available for pie yet, but the unofficial EdXposed magisk module was tested by me and it works good on pixel experience.
Kindly ask you to upload some zip file to your OP, containing following files:
- tmp\hack_splash.xml
- tmp\prog_emmc_firehose_8917_ddr.mbn
- tmp\recovery.img
- tmp\splash.img
- tmp\twrp.xml
- fh_loader.exe
- QSaharaServer.exe
- a text file containing steps 9-11 and link to xaacnz thread (for credits)
_saurabh__._ said:
As a followup to this guide https://forum.xda-developers.com/xiaomi-redmi-5a/how-to/bypass-bootloader-lock-redmi-5ariva-t3772381 by dev @xaacnz without him this guide might not be here, I am making this guide so you can root your device or flash any custom kernel without unlocking your device.
Code:
Your warranty will be void now
I am not responsible for anything wrong happens to your device
Note1: Even though no data is erased in this process it is recommended to take backup.
What this guide covers.
1. Rooting your device
2. Flashing custom kernel
All without need to unlock bootloader
Requirements
1. Working twrp recovery (if you dont have twrp installed follow this guide)
2. Any hex editor(Note2) for android/windows (yes you absolutely dont need a pc)
3. Latest Magisk manager app only (for root only)
4. Android Image kitchen- android, windows/linux (for custom kernel only)
Steps1. Extract boot.img from your currently installed rom and put it in internal storage of your phone (if you do not want to flash custom kernel skip to step 4)
*2. Download custom kernel you want to flash, extract zImage from the flashable kernel zip
*3. Unpack boot image using android image kitchen, in the split_img folder delete "boot.img-zImage" and put zImage you extracted in split_img folder and rename it to "boot.img-zImage"
*For custom kernel only
4. Install magisk manager apk on your phone
5. open magisk manager, you will see magisk is not installed select install (first one), a popup will appear telling to install magisk, select install, then select Patch Boot Image File, select the boot.img file that you extracted, then let magisk manager do the rest, after finishing the patched_boot.img file will be stored in Downloads folder of your internal storage
6. Open the patched_boot.img in hex editor
7. To make the patched_boot.img to boot append(Note2) a 4k block which begins with 0x30, 0x83, 0x19, 0x89, 0x64 to patched_boot.img, and save the file
8. Boot into twrp and flash patched_boot.img
9. Done, reboot
Note2: On Linux you can use dd command to append
Code:
printf '\x30\x83\x19\x89\x64' | dd of=testfile ibs=4096 conv=sync,notrunc oflag=append
Note3: If you get error cannot mount twrp while flashing the image, use vendor twrp
Note4: If I get time I will later make a script that automates the process.
Click to expand...
Click to collapse
Please upload the patched files.
- hack_splash.xml
- recovery.img
- twrp.img
- splash.img
- twrp.xml
It really helps me to know how to append blocks.
Please upload these files for us.
Thanks and regards.
Anshu lakra said:
aIecxs said:
Dude, youre waiting for 2 months, wish i could help you... Maybe here more better luck?
https://forum.xda-developers.com/showthread.php?t=3911660
Click to expand...
Click to collapse
Have you flashed custom ROM ?
---------- Post added at 03:54 AM ---------- Previous post was at 03:52 AM ----------
Nobody is uploading or posting link.
Click to expand...
Click to collapse
Nope. I don't have this phone anymore. Just be patient, _saurabh__._ will upload patched files as soon as he has time, he's busy at moment
aIecxs said:
Nope. I don't have this phone anymore. Just be patient, _saurabh__._ will upload patched files as soon as he has time, he's busy at moment
Click to expand...
Click to collapse
Thanks sir i am waiting .
saurabh6377 said:
As a followup to this guide https://forum.xda-developers.com/xiaomi-redmi-5a/how-to/bypass-bootloader-lock-redmi-5ariva-t3772381 by dev @xaacnz without him this guide might not be here, I am making this guide so you can root your device or flash any custom kernel without unlocking your device.
NOTE: YOU NEED TO FOLLOW THE ABOVE GUIDE IF YOU HAVEN'T, THEN COME BACK HERE
Code:
Your warranty will be void now
I am not responsible for anything wrong happens to your device
Note1: Even though no data is erased in this process it is recommended to take backup.
What this guide covers.
1. Rooting your device
2. Flashing custom kernel
All without need to unlock bootloader
Well there are two ways with which you can do this
Requirements
For PC based method
1. Working twrp recovery (if you dont have twrp installed follow this guide)
2. Pc must have linux installed, if you have windows don't worry install WSL using this link
3. Android image kitchen for your respective OS.
4. Latest magisk zip from here
For Android only
1. Working twrp
2. Any hex editor(Note2) for android/windows (optional)
3. Latest Magisk manager app only (for root only)
4. Android Image kitchen- android, windows/linux (for custom kernel only)
Steps for PC based1. Flash magisk zip or any kernel. Don't reboot system.
2. Go to backup senction in twrp and backup boot.
3. Connect your device to PC and look where you backed up boot and copy boot.emmc.win to Android image kitchen folder and rename to boot.img
4. Run unpackimg.sh or double click on unpackimg.bat. Then run repackimg.sh or double click on repackimg.bat. You will see image-new.img in the same folder
5. On windows hold Shift and right click in file manager with mouse, you will see open linux shell here, click it. OR if you have linux (specifically ubuntu) then right click and select open terminal here in Nautilus.
6. Run (to append 4k block, note that you can append block to any file specified by "of" parameter like of=twrp.img, of=boot.img etc)
Code:
printf '\x30\x83\x19\x89\x64' | dd of=image-new.img ibs=4096 conv=sync,notrunc oflag=append
7. Copy the image-new.img to your phone anywhere you prefer.
8. Flash image-new.img using twrp to boot partition.
9. Reboot
Steps for non-PC based (*outdated and some kernels won't work fully)[/CENTER]
1. Extract boot.img from your currently installed rom and put it in internal storage of your phone (if you do not want to flash custom kernel skip to step 4)
*2. Download custom kernel you want to flash, extract zImage from the flashable kernel zip
*3. Unpack boot image using android image kitchen, in the split_img folder delete "boot.img-zImage" and put zImage you extracted in split_img folder and rename it to "boot.img-zImage"
*For custom kernel only
4. Install magisk manager apk on your phone
5. open magisk manager, you will see magisk is not installed select install (first one), a popup will appear telling to install magisk, select install, then select Patch a file, select the boot.img file that you extracted, then let magisk manager do the rest, after finishing the magisk-patched.img file will be stored in Downloads folder of your internal storage
6. Open the patched_boot.img in hex editor
7. To make the patched_boot.img to boot append(Note2) a 4k block which begins with 0x30, 0x83, 0x19, 0x89, 0x64 to patched_boot.img, and save the file
8. Boot into twrp and flash patched_boot.img
9. Done, reboot
Note2: On Linux you can use dd command to append
Code:
printf '\x30\x83\x19\x89\x64' | dd of=testfile ibs=4096 conv=sync,notrunc oflag=append
Note3: If you get error cannot mount twrp while flashing the image, use vendor twrp
Note4: If I get time I will later make a script that automates the process.
Click to expand...
Click to collapse
script .you promised script. are looking forward to !!! You are welcome
If this is like an LG Bump situation you should just make a Pull Request to Magisk to add detection of the magic and to re-add it after automatically. I'll see about adding support for it to my Android Image Kitchen as well.
Edit: Also @saurabh6377 isn't using AK3 correctly.. he left in all the stuff from the example and edited the Backend to add the printf (which it clearly says not to do) instead of putting it in anykernel.sh.
not necessary there is official unlock tool from xiaomi
aIecxs said:
not necessary there is official unlock tool from xiaomi
Click to expand...
Click to collapse
This is for those who weren't successful unlocking via official method.
osm0sis said:
Edit: Also @saurabh6377 isn't using AK3 correctly.. he left in all the stuff from the example and edited the Backend to add the printf (which it clearly says not to do) instead of putting it in anykernel.sh.
Click to expand...
Click to collapse
Yeah, that is why I said experimental, I have my exams coming and I am just starting to learn all the stuff. It takes a lot of time figuring out everything (for beginner).
That is why I modified anykernel methods of flashing boot image.
EDIT: After my exams will be over, I will try to make another version of appender using anykernel correctly.
@osm0sis Also, the bytes must be appended to final boot.img before flashing, but ak3 builds and flashes boot image in same method (write_boot), so I have to modify that method. Correct me if I am wrong.
osm0sis said:
If this is like an LG Bump situation you should just make a Pull Request to Magisk to add detection of the magic and to re-add it after automatically. I'll see about adding support for it to my Android Image Kitchen as well.
Click to expand...
Click to collapse
Not really needed, people can just unlock, it is for those who are using bypass bootloader exploit because they cannot unlock (most likely in case if someone have bought from untrusted source). And append doesn't work always.
Sent from my Redmi Note 7 using XDA Labs
saurabh6377 said:
Yeah, that is why I said experimental, I have my exams coming and I am just starting to learn all the stuff. It takes a lot of time figuring out everything (for beginner).
That is why I modified anykernel methods of flashing boot image.
EDIT: After my exams will be over, I will try to make another version of appender using anykernel correctly.
@osm0sis Also, the bytes must be appended to final boot.img before flashing, but ak3 builds and flashes boot image in same method (write_boot), so I have to modify that method. Correct me if I am wrong.
Not really needed, people can just unlock, it is for those who are using bypass bootloader exploit because they cannot unlock (most likely in case if someone have bought from untrusted source). And append doesn't work always.
Click to expand...
Click to collapse
Cool. I just worry what that stuff intended for tuna (Galaxy Nexus) could do. If you don't need to touch the ramdisk you could just use split_boot; so it doesn't unpack the ramdisk unnecessarily.
You can use repack_ramdisk; (if unpacked) and flash_boot; instead of write_boot; to get more granular control and be able to act on the final image before flash. :good:
Good luck with your exams! :fingers-crossed:
@osm0sis thanks, I will make another version of appender soon.
I have one question though
I want to edit /vendor/etc/fstab.qcom to enable forceencrypt using anykernel
In fstab.qcom I have this
/dev/block/bootdevice/by-name/userdata /data ext4 rw,nosuid,nodev,noatime,noauto_da_alloc wait,formattable,check,encryptable=footer,quota
I want to change "encryptable" to "forceencrypt" using anykernel.
What is proper way?
Sent from my Redmi Note 7 using XDA Labs
saurabh6377 said:
@osm0sis thanks, I will make another version of appender soon.
I have one question though
I want to edit /vendor/etc/fstab.qcom to enable forceencrypt using anykernel
In fstab.qcom I have this
/dev/block/bootdevice/by-name/userdata /data ext4 rw,nosuid,nodev,noatime,noauto_da_alloc wait,formattable,check,encryptable=footer,quota
I want to change "encryptable" to "forceencrypt" using anykernel.
What is proper way?
Click to expand...
Click to collapse
Well that's not necessarily an AnyKernel "thing" because it's a vendor partition modification, but yeah you could do that somewhere in anykernel.sh as part of a flash if you want, just remember to mount vendor rw first and back to ro after. The AK3 patch_fstab function might work for you.
Hey ges any video for this step?
7. To make the patched_boot.img to boot append a 4k block which begins with 0x30, 0x83, 0x19, 0x89, 0x64 to patched_boot.img, and save the file
How to flash phh's system arm64-A/B GSI on the Redmi 9's (lancelot) dynamic system partition
All the development credits for this GSI go to @phhusson. For more information head over to his thread.
Bugs:
• Auto brightness (works with an overlay)
• Brightness slider
• Headphone jack
• Offline charging?
• VoLTE?
For bug fixes refer to Post #2 or search for reported bugs on Phh's treble experimentations issues tracker on GitHub.
What is working:
Everything else
WARNING:
Only proceed if you know what you are doing! Be aware of the risks associated to unlocking your bootloader. Ensure to have the MIUI Fastboot ROM downloaded to restore your device in case it soft bricks. All your data will be deleted during the process so a backup is essential. Charge your device to at least 50% before proceeding.
Requirements:
1) Unlocked bootloader here
2) Latest Android platform tools here
3) MIUI stock recovery (maintain it to be able to boot into userspace fastboot)
4) Xiaomi fastbootd drivers here
5) Phh-Treble GSI (Use a system-arm64-ab-gapps) here
6) vbmeta.img here
Steps:
Run the commands below within the platform-tools folder after enabling debugging in Developer settings on your phone.
1) adb devices (to authorize debugging)
2) adb reboot bootloader (to boot into fastboot mode)
3) fastboot reboot fastboot (to boot into userspace fastboot)
4) fastboot flash system system.img
5) fastboot -w
6) fastboot flash vbmeta vbmeta.img (use attached null vbmeta to disable avb)
7) fastboot reboot
Notes:
• First time boot takes 1 minute. phh's GSI has root by default however the logical system partition is read only. Any system mods should be done as Magisk modules systemlessly. A patched boot.img may cause bootlooping on Android 11 GSIs however Magisk now works fine even on R GSIs on MTK devices, thanks to @topjohnwu!
• System can be RW such as to push overlays. Thanks to the great phhusson!
• A better way to disable Android Verified Boot is by running below command using a stock vbmeta image file:
Code:
fastboot --disable-verification flash vbmeta vbmeta.img
Fixes:
I'll post fixes to bugs as suggested by users in this thread here.
• Brightness slider and headphone jack [Credit to @M47Z and @Shas45558] — Run code below in root ADB shell or any Terminal app on your phone:
Code:
su
setprop persist.sys.qcom-brightness $(cat /sys/class/leds/lcd-backlight/max_brightness)
setprop persist.sys.overlay.devinputjack true
reboot
• Note that CAOS by @eremitein has the above fixes integrated and is based on phhusson's AOSP.
How is the performance .any lag ?
Once you boot there are no lags. FYI my device is only 3 GB RAM. I just observed that booting is a little faster with the lighter Phh-Treble system installed as compared to Havoc. Maybe that's something for you to consider.
nielsync said:
Once you boot there are no lags. FYI my device is only 3 GB RAM. I just observed that booting is a little faster with the lighter Phh-Treble system installed as compared to Havoc. Maybe that's something for you to consider.
Click to expand...
Click to collapse
Is your headphones work??is brightness work?
Headphones not working but good enough BT audio works with speakers. Haven't tested in call audio on BT earphones though. Also not sure about USB-C audio output. Someone who has tested can share with us. Brightness is also broken.
I need testers
I built the overlay but I need testers to see if the overlay is working
Overlay link : github.com/mehdiFa-web/overlay
Mido2222 said:
I built the overlay but I need testers to see if the overlay is working
Overlay link : github.com/mehdiFa-web/overlay
Click to expand...
Click to collapse
Edit: Not working. Refer to post #18 for info.
Mido2222 said:
I built the overlay but I need testers to see if the overlay is working
Overlay link : github.com/mehdiFa-web/overlay
Click to expand...
Click to collapse
how did you pushed it into /vendor/overlay/ ?
I get the permission denied error everytime with adb and with any root file explorer on the phone too.
kW_ said:
how did you pushed it into /vendor/overlay/ ?
I get the permission denied error everytime with adb and with any root file explorer on the phone too.
Click to expand...
Click to collapse
I didn't test it I just build it . You should have root just copy it into your phone's /system/overlay/, and set permission to rw-r--r-- / 0644. If you can't then maybe we can't edit system partition . You can use root explorer.
Well. I can't change permissions and copy it. I have seen that other roms doesn't have read only on the system partition so i will try it later. Lineageos is one of these roms maybe.
Gsi will not boot with magisk_patch boot.img.....
So no root access......
How you push file into system or vendor??
Shas45558 said:
Gsi will not boot with magisk_patch boot.img.....
So no root access......
How you push file into system or vendor??
Click to expand...
Click to collapse
Phh-Treble has root so you are good to go. On the other hand without flashing a custom recovery I got root on Havoc-OS through flashing the patched boot image and even installed a module in Magisk manager without any issues. Its just that the way the system partition is mounted on these new phones released with Q makes it almost impossible to modify it. Let a genius surprise us.
nielsync said:
Phh-Treble has root so you are good to go. On the other hand without flashing a custom recovery I got root on Havoc-OS through flashing the patched boot image and even installed a module in Magisk manager without any issues. Its just that the way the system partition is mounted on these new phones released with Q makes it almost impossible to modify it. Let a genius surprise us.
Click to expand...
Click to collapse
In my case when I flash patch boot my gsi wili not boot....
What gsi are you use?? Give the link plz
@nielsync
So im a genius nd going to surprise you if anyone wants to modify system partition then custom recovery is must required e.g in Twrp mount /system , /vendor then go to file manager in twrp i forgot the name of tab in which you ll find the filemanager you can find it yourself lmao ,then select the file by finding in ur storage nd then copy and paste it in desired location and then after pasting go to path where you pasted it,Select it and give it 0644 permissions and restart ..Boom.( I think root is necessary because without root the changes revert )
Abdul [email protected] said:
@nielsync
So im a genius nd going to surprise you if anyone wants to modify system partition then custom recovery is must required e.g in Twrp mount /system , /vendor then go to file manager in twrp i forgot the name of tab in which you ll find the filemanager you can find it yourself lmao ,then select the file by finding in ur storage nd then copy and paste it in desired location and then after pasting go to path where you pasted it,Select it and give it 0644 permissions and restart ..Boom.( I think root is necessary because without root the changes revert )
Click to expand...
Click to collapse
File manager is in Advanced tab of TWRP. In theory and in devices released with the now old partition structure it was that simple. You have a right to claim anything Mr. Genius You seem to be ahead of even @Dees_Troy and his team over at TWRP despite this wonderful explanation!
Shas45558 said:
In my case when I flash patch boot my gsi wili not boot....
What gsi are you use?? Give the link plz
Click to expand...
Click to collapse
I've used both Phh-Treble and Havoc-OS and can confirm that Magisk works on both without any issues. My boot image was already patched on MIUI so I only installed the manager application each time after flashing the GSI. See screenshots of Magisk Manager on Phh-Treble below.
Mido2222 said:
I built the overlay but I need testers to see if the overlay is working
Overlay link : github.com/mehdiFa-web/overlay
Click to expand...
Click to collapse
no it does not work
i mount the gsi system file on linux via loop disk...
then i place your apk /system/overly/
but the brightness is not work...
you can mount raw img file on linux ......
first creat folder on root via this cmd..
sudo mkdir /mnt/system
mount system.img via this cmd
sudo mount system.img /mnt/system
now you can edit system.img via root permission via this cmd...
sudo nautilus
now a file manager pop up with root
go to /mnt/system
copy your file where you want...and unmount via this cmd...
sudo umount /mnt/system
Thanks @Shas45558 for confirming that, it's still difficult to mod the installed system on the phone itself. I tried and got a 'permission denied' error via terminal in a custom recovery.
nielsync said:
Thanks @Shas45558 for confirming that, it's still difficult to mod the installed system on the phone itself. I tried and got a 'permission denied' error via terminal in a custom recovery.
Click to expand...
Click to collapse
That's why I use pc with Linux and do the above things to puss the file inside system.img....
This thread is now defunct. I have moved to iPhone. Sorry about this.
Take care everybody.
Regards,
Magnetox
Appreciate this! If I'm already unlocked, is it possible to remove the -w in the flash-all script before running for a rooted install without wiping user data?
Wi1son said:
Appreciate this! If I'm already unlocked, is it possible to remove the -w in the flash-all script before running for a rooted install without wiping user data?
Click to expand...
Click to collapse
I would leave it as is, but if you want to try it, go ahead (might brick).
Hi ! Thanks for it.
Just a question After flash the Rom when the phone reboot before copy magisk manager can restore my Google backup ?
And how I do when they had an update ?
Thanks
ggkameleon said:
Hi ! Thanks for it.
Just a question After flash the Rom when the phone reboot before copy magisk manager can restore my Google backup ?
And how I do when they had an update ?
Thanks
Click to expand...
Click to collapse
Yes that should be fine. Just restore normally. But don't forget magisk otherwise it won't have proper root.
Might be a silly question, but, does this stock image work with Google Fi?
Also, a little confused with some of the directions...
In step 1 it says "Download the appropriate rar package for your system and install."
Does this mean download my stock image from Google and install it with Magisk, or... ?
In step 9 it says, " Once in fastboot, and the bootloader, run "fastboot devices" from the "BRAMBLE" folder. "
Does this mean to run "fastboot devices" as a command inside the command prompt from the "BRAMBLE" folder or to open one of the tools inside the platform tools folder?
Also, in step 11, where do I find the "appropriate flash-all command on your operating system"?
These are just a bit confusing to me. Don't want to brick my phone, so any help is appreciated.
Thanks
SpecialKCF22 said:
Also, a little confused with some of the directions...
...
Thanks
Click to expand...
Click to collapse
Download the WinRAR package in the mega.nz folder for your OS.
Both, platform tools should be in that BRAMBLE folder. Example fastboot.exe should be in BRAMBLE.
You will find this in your BRAMBLE folder when you properly extract platform tools and the .rar into the BRAMBLE folder.
SpecialKCF22 said:
Might be a silly question, but, does this stock image work with Google Fi?
Click to expand...
Click to collapse
It's just stock with root, so if the Pixel 4a 5g works normally it will too.
Magnetox said:
Download the WinRAR package in the mega.nz folder for your OS.
Both, platform tools should be in that BRAMBLE folder. Example fastboot.exe should be in BRAMBLE.
You will find this in your BRAMBLE folder when you properly extract platform tools and the .rar into the BRAMBLE folder.
Click to expand...
Click to collapse
You're not very detailed and you didn't answer the questions. I'll pass on this method. Thanks
SpecialKCF22 said:
You're not very detailed and you didn't answer the questions. I'll pass on this method. Thanks
Click to expand...
Click to collapse
Feel free to PM
Magnetox said:
Yes that should be fine. Just restore normally. But don't forget magisk otherwise it won't have proper root.
Click to expand...
Click to collapse
So, will update delete the magisk app? Or what do you mean when write "don't forget magisk"?
Ryav said:
So, will update delete the magisk app? Or what do you mean when write "don't forget magisk"?
Click to expand...
Click to collapse
I mean don't forget to install it and assure you have proper root after.
Does this one works with Google pay. My rooted build of RD1A.200810.022.A4 doesn't pass the safety check on magisk manager. Thank you
imFonk said:
Does this one works with Google pay. My rooted build of RD1A.200810.022.A4 doesn't pass the safety check on magisk manager. Thank you
Click to expand...
Click to collapse
MAGISK MODULE ❯ Universal SafetyNet Fix 1.1.0
Thanks for this! FYI for anyone curious the newest Magisk 8.07 does work, you don't need to use the linked file.
dadozer said:
Thanks for this! FYI for anyone curious the newest Magisk 8.07 does work, you don't need to use the linked file.
Click to expand...
Click to collapse
Yes feel free to do this. The APK that is linked works fine as well and will update itself with your permission.
Magnetox said:
Hey everybody,
Here is the latest Android 11 January 2021 update rooted (I will keep it updated). It's all clean. It is the Google stock system image with root applied (comes with GAPPS). You can cleanly flash your device with this as long as your fastboot (bootloader) is working.
Download LINK:
File folder on MEGA
mega.nz
Steps:
1) Download the appropriate rar package for your system and install.
2) Download the appropriate platform-tools package for your operating system (this contains ADB and Fastboot) and extract it in a folder we'll call "BRAMBLE" (we will use this folder for the install).
3) Download the bramble-rq1a.210105.003.rar file (this is the stock rom). Extract it to the "BRAMBLE" folder. You will want to see all the files (ie. the flash-all.sh) all in the folder the same folder that contains the ADB and Fastboot tools.
4) Download MagiskManager-v8.0.4.apk, this will be used after the install and installed on the device.
5) Enable USB debugging and OEM unlocking (the bootloader unlock) in developer options (smash on build a bunch of times in a row real fast to enable developer options in about phone).
7) Navigate to the "BRAMBLE" folder with a terminal or command prompt (depending on your operating system) and run "adb devices" with root or administrator access in your terminal or command prompt on your computer (respectively there). Allow the USB debugging to connect to your computer forever on your phone, something should pop up. It should appear in the terminal or command prompt. If not you need to accept USB debugging on your phone (forever).
8) Put in the command "adb reboot bootloader" once your device appears.
9) Once in fastboot, and the bootloader, run "fastboot devices" from the "BRAMBLE" folder. This should return your device. If not, something is wrong and restart. Another way of reaching fastboot is restarting your phone and holding VOLUME DOWN.
10) Make sure your device is unlocked, run "fastboot flashing unlock".
11) In the "BRAMBLE" folder, run the appropriate flash-all command on your operating system. This will take a while and completely reflash the system with the Stock ROM with root. You will see the progress as it appears.
12) Once it's done, your phone will reboot. Just wait for it to start up and do as you normally would on a new flash.
13) Move the MagiskManager-v8.0.4.apk onto the phone, and install it. It will confirm you have partial root and ask you to apply something more and reboot. Do so.
14) When rebooted, your phone will be fully flashed and rooted. Feel free to download a root verification app, I recommend this one. It should be working fine. Grant root permission forever to it.
If you have any questions, feel free to ask. You can install the ElementalX kernel on this rom for Pixel 4a 5g. Download this. It's a great kernel tool and it will help you with full root access download and install the kernel. It's the kernel I'm using.
Regards,
Magnetox
Click to expand...
Click to collapse
i could not install magisk, the 13th step in your guide might not be complete.
i managed to root, and got to pass safety net, and google pay working.
i have to move the boot.img from the zip file included in the package you provided, move it to internal storage, patch it in magisk manager.
then i moved the patched boot.img to my pc, did adb reboot bootloader, then fastboot flash [patched boot.img] and then only i was fully rooted.
i also flash the safetynet-fix-v1.1.1.zip module in magisk to pass satefynet.
hope it could help out, i digged all night yesterday to get this done lol.
MegaJuif said:
i could not install magisk, the 13th step in your guide might not be complete.
i managed to root, and got to pass safety net, and google pay working.
i have to move the boot.img from the zip file included in the package you provided, move it to internal storage, patch it in magisk manager.
then i moved the patched boot.img to my pc, did adb reboot bootloader, then fastboot flash [patched boot.img] and then only i was fully rooted.
i also flash the safetynet-fix-v1.1.1.zip module in magisk to pass satefynet.
hope it could help out, i digged all night yesterday to get this done lol.
Click to expand...
Click to collapse
I updated it with the latest 8.0.7 magisk. Hope this fixes it. (Uploading now)
Upload complete! (Magisk 8.0.7)