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
Related
*********************************************************
Sorry to all but I just don't have the time to maintain this thread like I used to
You can check out http://forum.gizmolord.com/android-modding/pantech-burst-quick-guides/ as that seems to be a pretty nice arrangement of Burst stuff.
If anyone wants to use the guides I wrote up in a different thread, please feel free to do so.
*********************************************************
I did not develop any of the following root, CWM, or Stock ROMs. I just wrote up the instructions and am using this thread to organize current and hopefully future development to make it easier to locate needed files and instructions to use the files.
No need to thank me. Thank those that really deserve it, the devs
Thanks!: jcase, Attn1, IOMonster, and any others I may have missed
Let me know if there is any suggestions to improve the instructions or if something is not clear, if there is something I may have missed, or especially if there is someone else that should be thanked.
*Note: My computer is Windows 7 64bit, directories will be different on 32bit Windows. I have no idea how to do this on Linux but if someone does know how, please feel free to add instructions to this thread or PM me the instructions and I will edit my post to include them and will acknowledge that you wrote them.
*I am not responsible nor are any of the devs responsible for any lost data or bricked devices. Follow at your own risk and be sure to Back up your data before doing anything.
Prep Work
Setup Pantech Burst drivers on Windows computer
1-Download and install Pantech PC Suite
2-Launch Pantech PC Suite and update if it asks. When PC Suite is fully updated, plug phone into computer until device is recognized.
Alternative: Download and Install Drivers with [USB_Driver]PSMN_Install_V1_1_0_0.exe (Mirror)
*Note: I have not used this method so I am not sure if it works
Setup Windows computer so you can send commands to phone
1-Download and install Java Development Kit from http://www.oracle.com/technetwork/java/javase/downloads/index.html
2-Download and install Android SDK from developer.android.com/sdk/index.html
2-Start SDK Manager and check the box next to “Android SDK Platform-tools” and install package.
Setting up Linux for ADB to recognize Pantech Burst *Thanks jackattack79
[HOW-TO] using fastboot on mac os X *Thanks aed0101 for the how to
Setup phone so it can receive commands from computer
Go to settings > Applications > Development > turn on USB Debugging
Root & CWM
FOR GINGERBREAD
Root phone
1-Download prestoroot.img (mirror) and save it to “C:\Program Files (x86)\Android\android-sdk\platform-tools”
2-Now open your command line and navigate it to “C:\Program Files (x86)\Android\android-sdk\platform-tools” folder
3-Run the following command
Code:
adb reboot bootloader
4-When the bootloader screen shows up on your phone then wait a few seconds to make sure your phone is recognized by the computer then run the following command
Code:
fastboot boot prestoroot.img
5-After phone reboots itself, shut the phone down and turn it back on again.
6-When the phone boots up this time, download Superuser from Google Play
Install ClockWorkMod
1-Download cwm-5.0.2.7-presto.img (mirror) and save it to “C:\Program Files (x86)\Android\android-sdk\platform-tools”
2-Now open your command line and navigate it to “C:\Program Files (x86)\Android\android-sdk\platform-tools” folder
3-Run the following command
Code:
adb reboot bootloader
4-When the bootloader screen shows up on your phone then wait a few seconds to make sure your phone is recognized by the computer then run the following commands
Code:
fastboot flash recovery cwm-5.0.2.7-presto.img
fastboot reboot
5-To access CWM, hold the volume down button while powering device on
6-To use CWM, Volume up and down will scroll up and down and Power button will select
FOR ICE CREAM SANDWICH
CWM & Root
UnRoot (Revert back to stock)
FOR GINGERBREAD May not work if you have updated to ICS. I have not tried. Let me know if you do try though
*You will need both Stock ROM and Stock Recovery to apply OTA update when/if they are released
**Restoring these will most likely wipe your data so be sure to backup first!!!
Restore stock ROM with CWM
1-Download one of the following zipped backup:
Presto-GRJ90_11282011.zip (mirror) (original firmware)
JUUS03122012.zip (mirror) (1st stock update)
JUUS06252012.zip (mirror) (2nd stock update, newest)
2-extract zip to the "/sdcard/external_sd/clockworkmod/backup/"*
3-If you have CWM installed on phone, boot into CWM and skip to step 7*
4-If you don't have CWM installed, Download cwm-5.0.2.7-presto.img (mirror) and save it to “C:\Program Files (x86)\Android\android-sdk\platform-tools”
5-open your command line and navigate it to “C:\Program Files (x86)\Android\android-sdk\platform-tools” folder
6-Run the following commands
Code:
adb reboot bootloader
fastboot boot cwm-5.0.2.7-presto.img
7-backup and restore > restore > select backup to restore > Yes – Restore
8-You may need to do a “wipe data/factory reset”, “wipe cache partition”, and Wipe Dalvik Cache” to get OTA updates that AT&T/Pantech push out.
9-reboot system now
Stock recovery
*Recovering to Stock ROM via CWM does not restore Stock recovery. Here is how to restore Stock Recovery.
1-Download recovery.img (mirror) and save it to “C:\Program Files (x86)\Android\android-sdk\platform-tools”
2-Now open your command line and navigate it to “C:\Program Files (x86)\Android\android-sdk\platform-tools” folder
3-Run the following command
Code:
adb reboot bootloader
4-When the bootloader screen shows up on your phone then wait a few seconds to make sure your phone is recognized by the computer then run the following commands
Code:
fastboot flash recovery recovery.img
fastboot reboot
Alternative method for stock JUUS03122012 and Recovery:
1-Download PANTECH_PRESTO_BIN_JUUS03122012.pdl (mirror)
2-Download P9070_Download_Tool_v3.3.zip (mirror) and extract it
3-Boot phone into Emergency Download Mode - With device off, press and hold power + Volume Up + Volume Down
4-Execute P9070_Download.exe
5-Select “Open File” and select the PANTECH_PRESTO_BIN_JUUS03122012.pdl file
6-Select “Reload File”
7-Select Download
8-Just select the default location for the XML log file
*I had to do this twice as it failed the first time and the second time it was successfull
FOR ICE CREAM SANDWICH
Burst's Upgrade to ICS (mirror)
Customization
Burst's Upgrade to ICS (mirror)
ROMs
Gizmolord
CM9 ROM - Still a lot not working on it but it does boot which is awesome. Looks like we should thank jznomoney for building this ROM and whoever leaked this ROM. *Install via CWM using the "Install zip from storage" option. May want to do a full wipe and a dalvik wipe before booting into it.
MODs
[MOD] HULU Flash Hack - Flashex - Thanks NoSudo
[MOD] Pantech Burst - Native Hotspot/Tethering Enabled (Root) - Thanks lost_
[APK] Seeder entropy generator to provide significant lag reduction
Customizing
UOT Kitchen: You will need framework-res.apk and SystemUI.apk from your phone
Check for Stock Updates more than once a day
Settings > Manage Applications > All > AT&T software update > Clear data > OK
Go back to Settings > AT&T software update > Back > AT&T software update > Check for update
Partition List for the Burst - Thanks to Davepmer
mmcblk0p1 /firmware
mmcblk0p8 /boot
mmcblk0p13 /system
mmcblk0p14 /data
mmcblk0p15 /persist
mmcblk0p16 /cache
mmcblk0p17 /tombstones
mmcblk0p18 /recovery
mmcblk0p19 /etc/firmware/misc_mdm
mmcblk0p27 /mnt/sdcard
mmcblk1p1 /mnt/sdcard/external_sd
Cool Apps
Sony Panaramic Beta Cam app (verfied works with Pantech Burst because I've been playing with it making cubicle views all day )
Holo Launcher (for those who want the ICS launcher now!)
Burst Related Links
Pantech Burst Love, Anyone? Anyone?
Pantech Burst Essentials (You are here now)
Pantech Burst Port in Progress
Cyanogen-presto
FYI guys the JUUS03122012.zip file seems to be corrupt-there's no way to open it as a zip (I tried with 7-zip as well as windows explorer on multiple downloads). Does anybody have a working version of this file since Pantech isn't pushing it out?
tekdemon said:
FYI guys the JUUS03122012.zip file seems to be corrupt-there's no way to open it as a zip (I tried with 7-zip as well as windows explorer on multiple downloads). Does anybody have a working version of this file since Pantech isn't pushing it out?
Click to expand...
Click to collapse
I re-uploaded it. Give it a try now.
Reserved for marcusmarcus
Reserved for marcusmarcus
kagedws6 said:
Presto-GRJ90_11282011.zip is corrupt
Found this on Jcase's profile. its 200+mb and the file dropbox had was only 160mb
Click to expand...
Click to collapse
OK, that is fixed now. I uploaded all the files through a web browser and that way seems to corrupt the files. I uploaded all the files through the drop box client on my computer now so they should all be working.
I also cleaned up the unrooting section and added the cwm backup for the latest update that was pushed out.
marcusmarcus said:
OK, that is fixed now. I uploaded all the files through a web browser and that way seems to corrupt the files. I uploaded all the files through the drop box client on my computer now so they should all be working.
I also cleaned up the unrooting section and added the cwm backup for the latest update that was pushed out.
Click to expand...
Click to collapse
I went ahead and pointed the similar consolidated thread I started to this one because yours is done way cleaner and its more up to date
Is it possible to root the latest room JUUS06252012 with PrestoRoot.img ?
tangbunna said:
Is it possible to root the latest room JUUS06252012 with PrestoRoot.img ?
Click to expand...
Click to collapse
yes. after you root you will need to reboot once more for it to show the correct kernel version.
Shared with Rootzwiki hoping to drum up some more support for our phone
kagedws6 said:
Shared with Rootzwiki hoping to drum up some more support for our phone
Click to expand...
Click to collapse
Great! The more places we can get information posted, the more interest we can hopefully get for this phone. I pretty much stick to XDA. If anyone else knows any other sites, feel free to quote these instructions or link to these ones.
I noticed that the cm9 file under the ROMS link was updated 4 days ago, any major changes yo those version? Also, thank you to all who is making this possible.
marcusmarcus said:
Root phone
1-Download prestoroot.img and save it to “C:\Program Files (x86)\Android\android-sdk\platform-tools”
2-Now open your command line and navigate it to “C:\Program Files (x86)\Android\android-sdk\platform-tools” folder
3-Run the following command
Code:
adb reboot bootloader
4-When the bootloader screen shows up on your phone then wait a few seconds to make sure your phone is recognized by the computer then run the following command
Code:
fastboot boot prestoroot.img
5-After phone reboots itself, shut the phone down and turn it back on again.
6-When the phone boots up this time, download Superuser from Google Play
Install ClockWorkMod
1-Download cwm-5.0.2.7-presto.img and save it to “C:\Program Files (x86)\Android\android-sdk\platform-tools”
2-Now open your command line and navigate it to “C:\Program Files (x86)\Android\android-sdk\platform-tools” folder
3-Run the following command
Code:
adb reboot bootloader
4-When the bootloader screen shows up on your phone then wait a few seconds to make sure your phone is recognized by the computer then run the following commands
Code:
fastboot flash recovery cwm-5.0.2.7-presto.img
fastboot reboot
5-To access CWM, hold the volume down button while powering device on
6-To use CWM, Volume up and down will scroll up and down and Power button will select
Click to expand...
Click to collapse
5-After phone reboots itself, shut the phone down and turn it back on again.
Since people are already in the command line you might as well just place a command for "adb reboot" here.
Great job with this post by the way. Just a suggestion for people new to all of this. Not to mention, the more they work from the command line the more they will become comfortable with it.
Just a warning. By flashing a full PDL file you are risking to brick your device in case something goes wrong, as PDL file flashes bootloader and radio.
Use it only if nothing else works.
Got native HotSpot enabled.
my device intex cloud m6 1gb ram 8gb rom is not rooting.Please tell how to root
How to root Intex Cloud M6 8gb and 16gb smartphones.
Hello there,
This query was posted a long time ago by you and i am not sure if you have found the solution or not. But as far as i am aware, it is pretty hard to root this device. It runs on a Spreadtrum chipset sc7731. However, recently i figured out how to root this device.
It seems like that the device's default.prop file comes with a configuration :
Code:
ro.secure=1
which makes it impossible to root this device with absolutely any rooting software out there including the one-click apps.
To be able to root this device, the only efficient way is to replace the stock recovery with a custom one, deleting the default su binary file inside the /system/xbin folder as well as in the /system/bin folder, installing the SuperSU.zip file and finally by installing the Kingroot apk which will ultimately root the device.
I personally prefer the TWRP but there is no official release out there for this device. So, i ported a custom recovery for it in my spare time ( It may appear somewhat ridiculous but i had nothing more interesting to do so i changed the layout :silly
I have attached the recovery file below.
After you have downloaded the recovery as well as the SuperSU.zip, here are the steps to root it:-
Download the minimal adb fastboot for windows. You may google it, its available easily. (It turns out it may be the only tool that may work effectively in case your device is not getting recognized by any other adb.)
Rename the recovery as twrp and place it inside the Minimal adb and fastboot folder.
Connect the device via a USB cable and make sure adb debugging is on inside the developer options.
Now open the Minimal adb and fastboot tool and type the following commands inside the prompt:-
Code:
adb devices
adb reboot bootloader
fastboot devices
fastboot flash recovery twrp.img
fastboot reboot
Type the commands in the exact sequence. Your device will boot normally. Now, time to checkout the recovery. Type the following command inside the prompt.
Code:
adb reboot recovery
In a few seconds, you will have the custom twrp booted in front of you. Now, open the Mount tab inside the recovery and check the system option within it.
Head back to the recovery homescreen and open the Advanced tab which is followed by opening the File Manager tab.
Inside the file manager, follow the path to the pre-existing su binary file, i.e /system/xbin and delete it. Do the same with the su file present on /system/bin.
Now, head back to the recovery home ,open Install tab and select the SuperSU.zip wherever you placed it and swipe to confirm the installation.
Reboot system. (It will probably boot without the logo so don't worry if it does.)
Now Google the Kingroot.apk, download it and install it. Give it a run, it will probably fail.
So get rid of the other superuser app i.e, SuperSU app via the option present inside it, i.e "Cleanup to install other superuser app" or something like that.
After a few seconds, it will disappear from the device and probably the same might happen with the Kingroot app.
Reboot the device.
Re-install the Kingroot app and run it again.
Congrats! You just rooted your device. Go ahead and check the root via an app like Rootchecker.
Here is the custom recovery file: -
HTML:
https://adarshkushwah.github.io/Custom-recovery-for-Intex-Cloud-M6-8gb-and-16gb/
If you have any query regarding this, do let me know. :good:
(I would be glad if you or anyone who finds this post useful would thank me) Cheers!
Hello there,
First-off, i would like to thank the Chainfire for the SuperSU files and the Kingroot for making the rooting process easier.
As far as i am aware, it is pretty hard to root this device. It runs on a Spreadtrum chipset sc7731. However, recently i figured out how to root this device.
->> REQUIREMENTS:
1. Minimal adb and fastboot tool.
2. Kingroot app.
3. As usual, a working brain.
->> METHOD:
It seems like that the device's default.prop file comes with a configuration :
Code:
ro.secure=1
which makes it impossible to root this device with absolutely any rooting software out there including the one-click apps.
To be able to root this device, the only efficient way is to replace the stock recovery with a custom one, deleting the default su binary file inside the /system/xbin folder as well as in the /system/bin folder, installing the SuperSU.zip file and finally by installing the Kingroot apk which will ultimately root the device.
I personally prefer the TWRP but there is no official release out there for this device. So, i ported a custom recovery for it in my spare time ( It may appear somewhat ridiculous but i had nothing more interesting to do so i changed the layout :silly
I have attached the recovery file below as well as the SuperSU.zip files below.
After you have downloaded the recovery as well as the SuperSU.zip, here are the steps to root it:-
Download the minimal adb fastboot for windows. You may google it, its available easily. (It turns out it may be the only tool that may work effectively in case your device is not getting recognized by any other adb.)
Rename the recovery as twrp and place it inside the Minimal adb and fastboot folder.
Connect the device via a USB cable and make sure adb debugging is on inside the developer options.
Now open the Minimal adb and fastboot tool and type the following commands inside the prompt:-
Code:
adb devices
adb reboot bootloader
fastboot devices
fastboot flash recovery twrp.img
fastboot reboot
Type the commands in the exact sequence. Your device will boot normally. Now, time to checkout the recovery. Type the following command inside the prompt
.
Code:
adb reboot recovery
In a few seconds, you will have the custom twrp booted in front of you. Now, open the Mount tab inside the recovery and check the system option within it.
Head back to the recovery homescreen and open the Advanced tab which is followed by opening the File Manager tab.
Inside the file manager, follow the path to the pre-existing su binary file, i.e /system/xbin and delete it. Do the same with the su file present on /system/bin.
Now, head back to the recovery home ,open Install tab and select the SuperSU.zip wherever you placed it and swipe to confirm the installation.
Reboot system. (It will probably boot without the logo so don't worry if it does.)
Now Google the Kingroot.apk, download it and install it. Give it a run, it will probably fail.
So get rid of the other superuser app i.e, SuperSU app via the option present inside it, i.e "Cleanup to install other superuser app" or something like that.
After a few seconds, it will disappear from the device and probably the same might happen with the Kingroot app.
Reboot the device.
Re-install the Kingroot app and run it again.
Congrats! You just rooted your device. Go ahead and check the root via an app like Rootchecker.
The custom recovery file has been attached and happens to be in the .zip format so kindly extract the recovery from it.
If you have any query regarding this, do let me know. :v
(I would be glad if you or anyone who finds this post useful would thank me) Cheers!
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
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....