Related
Hello All,
For systemless root on the latest magisk, can I just install latest magisk manager and let it do its thing, or do I have to flash a custom boot image first?
if I'm not mistaken, magisk manager will need magisksu...
so you will flash the magisk zip, it will patch your kernel with magisk / su support... (I don't even know what u mean by 'custom boot image')...
then magisk manager will work.
-Be completely stock
-Install Magisk manager 5.4.0
-Let it patch boot image
-Flash patched boot image in fastboot
-Done and profit
Good luck.
Cheers
Edit: make sure you're bootloader is and stays unlocked offcourse.
Sent from my Google Pixel using XDA Labs
Just flash magisk zip through TWRP
Sgace said:
-Be completely stock
-Install Magisk manager 5.4.0
-Let it patch boot image
-Flash patched boot image in fastboot
-Done and profit
Good luck.
Sent from my Google Pixel using XDA Labs
Click to expand...
Click to collapse
Thanks! thought so with the latest version, so I don't need to flash TWRP, I can just unlock bootloader and let Magisk do the rest right? As you can see in this thread, people post conflicting stuff, mostly from before when magisksu was unable to deal with the A/B partitioning
Pinktank said:
Thanks! thought so with the latest version, so I don't need to flash TWRP, I can just unlock bootloader and let Magisk do the rest right? As you can see in this thread, people post conflicting stuff, mostly from before when magisksu was unable to deal with the A/B partitioning
Click to expand...
Click to collapse
Yes, unlock bootloader if you haven't already (this will factory reset your phone) and then follow my first post.
No need for twrp anymore.
Cheers
Sent from my Google Pixel using XDA Labs
Sgace said:
Yes, unlock bootloader if you haven't already (this will factory reset your phone) and then follow my first post.
No need for twrp anymore.
Cheers
Sent from my Google Pixel using XDA Labs
Click to expand...
Click to collapse
Thanks a million, somebody should sticky this as people are still going with the other methods. I'll straight flash the image before unlocking to iron out possible kinks from various updated.
Pinktank said:
Thanks a million, somebody should sticky this as people are still going with the other methods. I'll straight flash the image before unlocking to iron out possible kinks from various updated.
Click to expand...
Click to collapse
ya, sorry for any confusion, I may have added. ***I was not aware of using this newer method, seems handy fir some people... however; ... it's still rather pointless to use for some of us and doesn't obsolete using twrp;
1. I'm a kernel Dev, so I'm frequently flashing builds.
2. using magisk manager to patch a custom kernel, just would add unnecessary steps to the process.
it's much faster to just fastboot into twrp. flash kernel and magisk in one go, reboot...done. ***this would also be true for anyone flashing zips, that aren't magisk related.
still though; easy great tip for people who only need magisk.
nine7nine said:
ya, sorry for any confusion, I may have added. ***I was not aware of using this newer method, seems handy fir some people... however; ... it's still rather pointless to use for some of us and doesn't obsolete using twrp;
1. I'm a kernel Dev, so I'm frequently flashing builds.
2. using magisk manager to patch a custom kernel, just would add unnecessary steps to the process.
it's much faster to just fastboot into twrp. flash kernel and magisk in one go, reboot...done. ***this would also be true for anyone flashing zips, that aren't magisk related.
still though; easy great tip for people who only need magisk.
Click to expand...
Click to collapse
no problem. The nice thing about the magisk method is that it actually slips in the necessary changes during boot without static patching, keeping the system the same. Not sure how it would roll with custom kernel booting
Pinktank said:
no problem. The nice thing about the magisk method is that it actually slips in the necessary changes during boot without static patching, keeping the system the same. Not sure how it would roll with custom kernel booting
Click to expand...
Click to collapse
Yeah, I'm not too sure either. It would require probably changing my workflow, unpacking / repacking stock boot.img, adding in my init rc scripts, then using the magisk method ~ that sounds less automated, at first glance...
Right now, I build the kernel, then pop it into into a folder, zip it and flash it (all of the other parts are taken care of / setup).... I love magisk though; great root / systemless method. glad to see it opensource nad always improving
Pinktank said:
Thanks a million, somebody should sticky this as people are still going with the other methods. I'll straight flash the image before unlocking to iron out possible kinks from various updated.
Click to expand...
Click to collapse
You're welcome. Let us know how it worked out for you.
Cheers
Sent from my Google Pixel using XDA Labs
Hi Guys,
Note : By doing this, you know that you're gonna do a modification to your phone, and im not in any way, responsible for what happen after. Escape Route for if something wrong happen is provided, but YOU DO THIS ON YOUR OWN RISK
since this phone is fairly new, at this moment a clear rooting method haven't established yet. This is what this thread for.
Based on information gathered from P20 Lite Forum (the rooting guide for that device even already up - here), it seems the old trick of rooting (from Mate 10 Pro) using Patched Boot Method is working fine. And Magisk is working
Basically this method need few pre-requisites :
1. Unlocked Bootloader (by getting the code here ) - and if you not sure how to do it, go here for the guide
2. Stock Boot (or RAMDISK to be precise for this phone) - I managed to extract it from 8.1.0.106 ROM version for CLT-L29 (download here)
3. Magisk Manager 5.5.4 (from Magisk Thread) to patch the .img above, or
4. Patched RAMDISK image (i patched it) from here
5. and of course computer with ADB & Fastboot installed (make sure you have latest SDK to prevent something not working)
Now, to Root it, all you need to do is,
1. Boot into bootloader
2. Type
Code:
fastboot flash ramdisk patched_boot.img
(patched_boot.img is the file you download from prerequisites number 4, placed it in the same directory with your adb & fastboot - i assume you know that already)
3. Reboot
4. You now should have root access, download Magisk Manager to manage modules and superuser
(you might need to flash this module if you failed to pass safetynet)
In case something go wrong, flash back the stock RAMDISK from pre-requistes number 2 above using same method as what u did to flash the patched one.
That way worked. Thanks.
Edit:
Just as a hint. To get magisk work as it should..
After boot into the system and installed Magisk Manager, install Magisk from there again, so you dont get any /data/magisk problems.
SafteyNet passed then.
Fingers crossed twrp is possible soon
Works on CLT-L09
I have a German single Sim from Vodafone tested the root yesterday and works very well
Would this method work on CLT-L09 model? Thanks
danifilth4king said:
Would this method work on CLT-L09 model? Thanks
Click to expand...
Click to collapse
The post before you just confirmed yourbquestion, LoL
Yes it does
This is awesome, thanks for sharing! I thought I could live without root but after only half a day, I've decided I can't!
Before I do this, I was wondering where you managed to get the stock rom (quote below)?
otonieru said:
2. Stock Boot (or RAMDISK to be precise for this phone) - I managed to extract it from 8.1.0.106 ROM version for CLT-L29 (download here)
Click to expand...
Click to collapse
fl4r3 said:
This is awesome, thanks for sharing! I thought I could live without root but after only half a day, I've decided I can't!
Before I do this, I was wondering where you managed to get the stock rom (quote below)?
Click to expand...
Click to collapse
It's from www.allrom.ir (its in persian) and there's another site, rusian one if am not mistaken, but i forget the exact address
Great, thanks for that! I managed to find it on allrom.ir
Hey guys, I need some help please! I unlocked bootloader through Huawei website which went fine and then when I flashed the patched boot.img through fastboot and tried to reboot my phone has told me there was a critical error while booting. It won't boot to system and just loops a few times and then boots to Huawei eRecovery. This is my first Huawei device and I'm clueless as to how to recover
Any ideas would be much appreciated! Thanks
**EDIT*** false alarm! I managed to boot to fastboot and restore the ramdisk from the first post
danifilth4king said:
Hey guys, I need some help please! I unlocked bootloader through Huawei website which went fine and then when I flashed the patched boot.img through fastboot and tried to reboot my phone has told me there was a critical error while booting. It won't boot to system and just loops a few times and then boots to Huawei eRecovery. This is my first Huawei device and I'm clueless as to how to recover
Any ideas would be much appreciated! Thanks
**EDIT*** false alarm! I managed to boot to fastboot and restore the ramdisk from the first post
Click to expand...
Click to collapse
What is your phone model ? CLT-L29 or L09 ? And what is your ROM version ?
otonieru said:
What is your phone model ? CLT-L29 or L09 ? And what is your ROM version ?
Click to expand...
Click to collapse
It's CLT-L09, build number 8.1.0.103(C782)
It's and EE UK handset. Any ideas why it wouldn't have worked? Thanks
danifilth4king said:
It's CLT-L09, build number 8.1.0.103(C782)
It's and EE UK handset. Any ideas why it wouldn't have worked? Thanks
Click to expand...
Click to collapse
The ramdisk.img was taken from .106 ROM, so its actually newer than what installed on your phone. That might become issue,
But, do you managed to revive the phone using the stock ramdisk from first post ?
otonieru said:
The ramdisk.img was taken from .106 ROM, so its actually newer than what installed on your phone. That might become issue,
But, do you managed to revive the phone using the stock ramdisk from first post ?
Click to expand...
Click to collapse
Yes thank you, the stock ramdisk from the first post allowed my phone to boot normally again. Do you think if I use magisk manager app to patch the stock ramdisk it will work for me? Or is that the same as what you did to make the patched boot.img anyway?
danifilth4king said:
Yes thank you, the stock ramdisk from the first post allowed my phone to boot normally again. Do you think if I use magisk manager app to patch the stock ramdisk it will work for me? Or is that the same as what you did to make the patched boot.img anyway?
Click to expand...
Click to collapse
If you have the 103 rom, and able to extract the ramdisk yourself, you can try patch it yourself.
Have you tried to flash the patch ramdisk one more time ? In case it just a bad flash.
Because if you manage to boot using stock one. It means your system has no problem using .106 boot image and the patched one should work as well
otonieru said:
If you have the 103 rom, and able to extract the ramdisk yourself, you can try patch it yourself.
Have you tried to flash the patch ramdisk one more time ? In case it just a bad flash.
Because if you manage to boot using stock one. It means your system has no problem using .106 boot image and the patched one should work as well
Click to expand...
Click to collapse
Ok I will try again and report back. How do you boot into fastboot from device off state by the way? I had difficulty doing it earlier. Thanks again!
danifilth4king said:
Ok I will try again and report back. How do you boot into fastboot from device off state by the way? I had difficulty doing it earlier. Thanks again!
Click to expand...
Click to collapse
Its better to do it from ON state, and use adb reboot bootloader command
otonieru said:
Its better to do it from ON state, and use adb reboot bootloader command
Click to expand...
Click to collapse
I mean if the patched boot.img still doesn't work again and the device won't boot to system? I did it before when I flashed back to stock ramdisk, but I don't know how I entered fastboot exactly lol
danifilth4king said:
I mean if the patched boot.img still doesn't work again and the device won't boot to system? I did it before when I flashed back to stock ramdisk, but I don't know how I entered fastboot exactly lol
Click to expand...
Click to collapse
Put the device off and hold power button and volume down. You should come directly into the rescue mode.
danifilth4king said:
I mean if the patched boot.img still doesn't work again and the device won't boot to system? I did it before when I flashed back to stock ramdisk, but I don't know how I entered fastboot exactly lol
Click to expand...
Click to collapse
Ah, sorry, i got it wrong. Yes, its power n volume down.
So after 2 weeks of debugging and trying to figure out why Treble GSI were not booting, then booting only for some users the final answer has been found.
This bootloader is way too stateful.
So if you try directly with proper vbmeta & system.img, you won't notice anything, it will just work, that's why some people say it works.
If you try system first without doing vbmeta, then it will mark the slot as not bootable. Flashing vbmeta afterwards will NOT mark it as bootable.
it also requires the latest fastboot with --disable-verity and --disable-verification, don't know why yet exactly.
Now if you bootloop to mark it as bootable again, you need to flash the boot partition of the slot.
Even worse than that "fastboot boot" works only if current slot is not marked as not bootable, so any try to launch TWRP fails once your in this mode.
This same issue also applies to users trying to restore to stock sometimes.
This means that the One Plus 6 will require proper documentation on how to do things, and people will have to stick to it, see official instructions in post 2.
Now that we know what the exact cause is, and how to deal with it, let the development begin.
PS
Doesn't seem to be OP fault, just stock Qualcomm bootloader.
Credits to Phhusson and me for making this possible, providing phh a device, documenting the findings and all.
WARNING This is still ALPHA
OFFICIAL INSTRUCTIONS
Correct installation procedure of a GSI on the One Plus 6, determined together with @phhusson
Make sure you unlocked the bootloader and that you have the absolute latest ADB and Fastboot from Google, none of the minimal packages we know of will work!
Then in fastboot flash the following, WITHOUT rebooting in between! this needs to be done all in one go!
Code:
fastboot flash boot_a boot.img
fastboot flash boot_b boot.img
Use the STOCK boot image!
Then flash the GSI system image of your choice
Code:
fastboot flash system_a system.img
fastboot flash system_b system.img
Then flash STOCK vbmeta image with the specific commands!
Code:
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
then just fastboot reboot or select start on the phone.
---------------------------------------------------------------------------------------------------------------------------------------------------
If the above fails and you get a bootloop you will have to repeat all the steps above.
---------------------------------------------------------------------------------------------------------------------------------------------------
So if its marking it as unbootable can't you fastboot --set-active=other to get back to a bootable state?
@Exelios
Thank you for sharing.
Thread moved. Since this appears to be documentation rather than a physical product, this is the proper subforum.
Thank you!
-RJ
Great work man,
I had held off trying as I didn't know if it would work for me or not. Looking forward to trying this out!!!
Sent from my OnePlus6 using XDA Labs
joemossjr said:
So if its marking it as unbootable can't you fastboot --set-active=other to get back to a bootable state?
Click to expand...
Click to collapse
Yeah you can do that once, but to get your first slot back you will need to re flash boot also at some point.
And remember once you flash boot you need to root and TWRP again.
Sent from my OnePlus 6 using XDA Labs
CertifiedBlyndGuy said:
Thread moved. Since this appears to be documentation rather than a physical product, this is the proper subforum.
Thank you!
-RJ
Click to expand...
Click to collapse
An actual piece of software will be added by the end of the day.
Sent from my OnePlus 6 using XDA Labs
Any more details of what you found?, i tried numerous bootloader verity combos, only system.img that boots is aosp v18.
DocRambone said:
Any more details of what you found?, i tried numerous bootloader verity combos, only system.img that boots is aosp v18.
Click to expand...
Click to collapse
Give it a day, phh is trying to implement fixes to the findings in a more elegant and easier way for the end user, this thread was more intended to share our findings with other devs.
DocRambone said:
Any more details of what you found?, i tried numerous bootloader verity combos, only system.img that boots is aosp v18.
Click to expand...
Click to collapse
I've booted multiple roms comsic aosp aosip they boot just gotta get it right the first time
Exelios said:
An actual piece of software will be added by the end of the day.
Sent from my OnePlus 6 using XDA Labs
Click to expand...
Click to collapse
Ok. Just PM me and I'll move the thread when it happens
Still investigating, there is probably still something to this I'm missing
Exelios said:
Still investigating, there is probably still something to this I'm missing
Click to expand...
Click to collapse
What is the findings so far?
DocRambone said:
What is the findings so far?
Click to expand...
Click to collapse
Other then what's in the OP there seems to be also something else causing issues, not sure yet what exactly it is
Nope, phh just gave me the wrong vbmeta.img, one needs to use stock vbmeta not a modified one omg
I feel like an idiot now
But LOS still doesn't boot, something regarding sensors, stuck on boot logo.
Exelios said:
Other then what's in the OP there seems to be also something else causing issues, not sure yet what exactly it is
Nope, phh just gave me the wrong vbmeta.img, one needs to use stock vbmeta not a modified one omg
I feel like an idiot now
But LOS still doesn't boot, something regarding sensors, stuck on boot logo.
Click to expand...
Click to collapse
I couldn't get v19 of phh's AOSP to boot for the longest time until I tried this! Thanks man!! :good:
I have cleaned up the OP and added clear instructions in post 2.
Tho LOS still doesn't boot for now, but that's because of a bug specific to the GSI, not a bootloader issue.
Delete
CertifiedBlyndGuy said:
Ok. Just PM me and I'll move the thread when it happens
Click to expand...
Click to collapse
Might I ask to make this a sticky?
Because every developer needs to be aware of it, this doesn't affect just GSI, one can run in the same issue even if flashing TWRP or restoring to stock or anything.
And every user should know about the official way to do things on the One Plus 6, which is slightly different then all other phones.
Thanks
The instructions in post 2 is the same as in the treble thread, still no boot other than aosp v18
Hi, I was trying to flash some new gsi and I found this https://forum.xda-developers.com/pr...ment/rom-android-p-developer-preview-t3816659
Working Android Q! Bugs are normal with base 10.0.3.0 - Fingerprint not working... etc.
I used traditional method:
-Flash base
-fastboot erase system
-fastboot -w
- TWRP- flash Permissiver_V2.zip and Disable force encryption
Voila! Enjoy
Bug: Notch support
Hello,
First of all Congratulations for your success,
Could you please describe the flashing process because i have been trying it for 2 days still no success.
Did you flashed vbmeta? & which one did you used ARM64 OR ARM64+GMS?
you cant and you dont need to flash vbmeta. before doing anything read the instructions carefully. first, mia2lite doesnt have any vbmeta partition so you cant flash it, secondly its written there that this partition is needed to remove avb from boot partition of some specific phone so you dont need it.
what you need is flash remove_verity zip or patch your boot.img with magisk disabling preserve avb.
masumrussell said:
you cant and you dont need to flash vbmeta. before doing anything read the instructions carefully. first, mia2lite doesnt have any vbmeta partition so you cant flash it, secondly its written there that this partition is needed to remove avb from boot partition of some specific phone so you dont need it.
what you need is flash remove_verity zip or patch your boot.img with magisk disabling preserve avb.
Click to expand...
Click to collapse
I still didn't get it, he says flash base means he is talking about stock or GSI & if GSI then how?
CherryFarmer8 said:
I still didn't get it, he says flash base means he is talking about stock or GSI & if GSI then how?
Click to expand...
Click to collapse
Flashing base means to flash stock firmware
In this case it's 10.0.3.0. as mentioned in the first post
capajga said:
Flashing base means to flash stock firmware
In this case it's 10.0.3.0. as mentioned in the first post
Click to expand...
Click to collapse
okay so in which step do i have to flash GSI?
CherryFarmer8 said:
okay so in which step do i have to flash GSI?
Click to expand...
Click to collapse
You can try it like this:
Gumka1977 said:
https://github.com/tkchn/daisyinstall Do it like here, but instead of system.zip in TWRP - install system. img !
Click to expand...
Click to collapse
Thanks to Gumka1977
capajga said:
You can try it like this:
Thanks to Gumka1977
Click to expand...
Click to collapse
And what gsi did you flash?
I hope you already know how to flash GSI on devices with dyamic partition already. If not then you can follow this guide: https://forum.xda-developers.com/t/...ynamic-super-partition.4256667/#post-85271987
If youre on stock before flashing GSI then dont "fastboot delete-logical-partition product" like other tutorials may suggest. Just flash the product image (fastboot flash product [insert img here]) attached below and it will get resized automatically as well, giving you plenty of space to flash your GSI.
If youve already flashed GSI before following this guide and have done "fastboot delete-logical-partition product" then just create product partition (fastboot create-logical-partition product [size]) and flash the img on product.
whichever course youve taken you can now flash magisk through twrp or patch the boot img and flash that.
Please note that this product image wasnt made by me and the credit for it goes to: @Allexwin50
tested on infinix zero 8 X687
Thanks for the tutorial, I will give it a try but have one question: you said to" create product partition and give size " I don't understand about size!
shjeanpy said:
Thanks for the tutorial, I will give it a try but have one question: you said to" create product partition and give size " I don't understand about size!
Click to expand...
Click to collapse
when you create partition you also need to specify its size, just add some number
kusti420 said:
when you create partition you also need to specify its size, just add some number
Click to expand...
Click to collapse
What size would you advise me please
shjeanpy said:
What size would you advise me please
Click to expand...
Click to collapse
idk, i used 400000000
Thank you very much for your great tutorial. it worked for me on my device.
Thanks a lot for putting this together. I was stuck for a day and a half trying to figure out how to flash Magisk with no product partition. Great work.
nickelnine said:
Thanks a lot for putting this together. I was stuck for a day and a half trying to figure out how to flash Magisk with no product partition. Great work.
Click to expand...
Click to collapse
and i was stuck for multiple months...
@kusti420 if I've flashed a GSI on to stock (apart from flashing vbmeta and TWRP) can I fastboot flash that product.img and then successfully TWRP flash magisk or patch with app (using Phh SU temporarily for root) ? is that enough ?
EDIT 1: thought I'd just see for myself, flashed the product_gsi.img and my phone (S20FE 5G) still booted. tried flashing magisk 21.4 zip from TWRP and got a bootloop. will check later if I can patch my boot.img and post.
Hey, where did you take this product_gsi.img? I think it does not work with Android 12, I wonder if it can be updated or something like that.
felipecassiors said:
Hey, where did you take this product_gsi.img? I think it does not work with Android 12, I wonder if it can be updated or something like that.
Click to expand...
Click to collapse
it was sent to me in telegram, where i also traced it back to @Allexwin50, afaik he made it. worked fine on android 10 and 11. asking him for img for a12 could be an option
Sir, When I Flashed any GSI rom A11 , any way to remove the standard superuser root from rom ? if some solution , please advise me , (my device use fastboot commands not use twrp)
gamal001 said:
Sir, When I Flashed any GSI rom A11 , any way to remove the standard superuser root from rom ? if some solution , please advise me , (my device use fastboot commands not use twrp)
Click to expand...
Click to collapse
idk wtf u mean by "standard superuser root" prolly phh su, if yes then there is definetly a way to get rid of that
Right, so what to do after installing the GSI like this. How to install Magisk? I don't have TWRP. Do I have to "securize" first? Help.
K1569GHENT said:
Right, so what to do after installing the GSI like this. How to install Magisk? I don't have TWRP. Do I have to "securize" first? Help.
Click to expand...
Click to collapse
maybe, cant remember by heart, dont have enough time to test it out myself
Working on Nippon Android Tiramisu SGSI on Pixel 3a, very nice
K1569GHENT said:
Right, so what to do after installing the GSI like this. How to install Magisk? I don't have TWRP. Do I have to "securize" first? Help.
Click to expand...
Click to collapse
Obtain a stock copy of your boot.img.
Patch it through the magisk app before you do your whole thing installing your chosen gsi.
Once you have the patched image, you can fastboot it using fastboot flash boot boot.img in cmd onto your gsi ROM.
Make sure to install the boot.img to both slots A and B. Then go back to your active slot.
ninjasinabag said:
Obtain a stock copy of your boot.img.
Patch it through the magisk app before you do your whole thing installing your chosen gsi.
Once you have the patched image, you can fastboot it using fastboot flash boot boot.img in cmd onto your gsi ROM.
Make sure to install the boot.img to both slots A and B. Then go back to your active slot.
Click to expand...
Click to collapse
he talked about removing phh-superuser
kusti420 said:
he talked about removing phh-superuser
Click to expand...
Click to collapse
It's locked to your boot image, so using 100% stock image removes superuser since it's no longer system as root.
kusti420 said:
I hope you already know how to flash GSI on devices with dyamic partition already. If not then you can follow this guide: https://forum.xda-developers.com/t/...ynamic-super-partition.4256667/#post-85271987
If youre on stock before flashing GSI then dont "fastboot delete-logical-partition product" like other tutorials may suggest. Just flash the product image (fastboot flash product [insert img here]) attached below and it will get resized automatically as well, giving you plenty of space to flash your GSI.
If youve already flashed GSI before following this guide and have done "fastboot delete-logical-partition product" then just create product partition (fastboot create-logical-partition product [size]) and flash the img on product.
whichever course youve taken you can now flash magisk through twrp or patch the boot img and flash that.
Please note that this product image wasnt made by me and the credit for it goes to: @Allexwin50
Click to expand...
Click to collapse
Hello kusti420
I had already deleted the product partition when I found your post.
The GSI was not cool.
I reflash the product partition and reflash the GSI, now it's good.
Thanks for the file and the tip.