Magisk on G7 Play XT1952-4 Installed Succesfully
(Just a heads up. I have never posted to XDA before but have lurked on here for years. I don't have enough posts to post it in the Dev section. So I apologize if my post format is bad. But I will do my best. Hopefully I am not reporting old news, I've been waiting a few months to finally get Magisk to work on this phone.)
I do not take responsibility if you brick your phone doing this. So do it at your own risk.
Google Drive folder link with all files at the bottom of this post with screenshots as well
Install:
Firmware used during this is PPY29.105_160 (Firmware included in GDrive folder)
BOOTLOADER HAS TO BE UNLOCKED ON YOUR PHONE
I suggest you to backup and factory reset your phone before doing this.
If you're already on this firmware, then I have placed both the stock boot.img and the magisk_patched.img separate as well so you don't have to unzip the full firmware. I haven't tried this with other models of this phone or firmwares. Upgrade to this firmware if on an older version. Multiple ways to do so I'm sure you can figure it out
Copy the boot.img to your phones storage
Install Magisk Manager 7.3.4 aka 239 (APK in GDrive folder). Make sure all 3 options are checked in advanced settings in Magisk. Click install on Magisk and patch the file and locate it on your phone.
Place the patched.img in your ADB folder. Reboot into fastboot. I used CMD in Windows so I ran the following "fastboot flash boot magisk_patched.img"
Toggle up to Boot Recovery
Please Note. When I did the following. For some reason I was unable to get to the stock recovery after doing this. If I remove modules and reboot the phone Magisk is "not installed" however if you reboot the phone and go into Fastboot mode and then select the option of boot to recovery, it boots the phone normal with magisk enabled??? :confused. Eh at this point I'm just glad to have Magisk installed on this phone finally lol. I'm sure you can find the answer in the Magisk in Recovery section here
Magisk should be installed now after booting up. Check Magisk Manager to verify.
Notes:
I tried to install one module just to verify it wasn't a fluke and I was able to do so successfully
Once again I apologize if this post is unorganized or anything. Running on little sleep
I will do my best to answer any questions you might have from my experience when I am able to.
GOOGLE DRIVE FOLDER LINK
Nice work OP. Well written guide. Clear and concise.
i need some help i tried this method and ended up loosing baseband idk what i did wrong i have a retail varient , tried flashing stock rom multiple times do we have a persist.img to get the phone booting again ? twrp wont even boot i get the failed to many links error to see if wiping the phone that way would make it boot i flashed to both banks i have the XT195-4 varian
Use rsd lite to flash full rom it will reset your phone then enable usb debugging so you can reboot to fastboot then follow the instructions
Linuxassassin said:
Use rsd lite to flash full rom it will reset your phone then enable usb debugging so you can reboot to fastboot then follow the instructions
Click to expand...
Click to collapse
Thank you I managed to create a flash.bat with revived the phone I can confirm working on retail varient firmware 138
Ok this is a bit odd. Managed to get magisk installed. Rebooted and magisk is no longer installed. Figured I would have to reboot recovery again. Now whenever I go to boot recovery in the bootloader it just falls back to the bootloader.
The recovery option in magisk will not stick either it seems
Edit: Not sure what happened. I reflashed the stock firmware for my device, went through the steps again, and now magisk seems to have stuck. I do have to boot to recovery, but that was to be expected according to the documentation.
Oh Viper4Android, how I have missed thee
Edit 2: It appears the reboot to recovery option in magisk is what is breaking my install. As long as I do not try to reboot to recovery from anything outside of the bootloader, magisk sticks. Not sure what the cause for this is, but for now it is best to stay away from those options in Magisk
Edit 3: Not sure what the issue is, but after some tinkering, and a reboot, booting recovery to get magisk loaded does not work. Reboot to recovery takes me straight to the bootloader. If I click start the phone boots without magisk, and if I hold the button combo I get the stock recovery, but magisk appears to be gone
Please help
I flash wrong boot so I reflashed the entire firmware then patched the boot.img of the firmware I just flashed, all ok.
I flashed the patched boot image and toggled volume key to recovery but have no options there, so have to start phone by holding power button.
When phone boots up magisk is not installed. This is killing me so close yet...
P.s I omitted erase user data and erase DDR and phone is exactly as I left it ?
moochermick said:
Please help
I flash wrong boot so I reflashed the entire firmware then patched the boot.img of the firmware I just flashed, all ok.
I flashed the patched boot image and toggled volume key to recovery but have no options there, so have to start phone by holding power button.
When phone boots up magisk is not installed. This is killing me so close yet...
P.s I omitted erase user data and erase DDR and phone is exactly as I left it
Click to expand...
Click to collapse
your missing a step , what worked for me , since i updated my phone manually and now im on slot_a flash both banks with the magisk_patched.img and you wont have that problem , if your on slot_b flash slot_a as well , and it should work , fastboot getvar all to see what slot is bootable
@thenatti
Thanks I will give that ago.
thenatti said:
your missing a step , what worked for me , since i updated my phone manually and now im on slot_a flash both banks with the magisk_patched.img and you wont have that problem , if your on slot_b flash slot_a as well , and it should work , fastboot getvar all to see what slot is bootable
Click to expand...
Click to collapse
I have flashed the patched boot to both banks and still magisk not installed, what's all this talk about booting from recovery, I can't do anything from recovery except hold the power button to restart the phone.
Any further suggestions?
Ok here's what worked...
Reflashed all firmware and restarted phone,
Flashed patched boot.img and in fastboot on pc "fastboot continue" phone rebooted.
Back into fastboot on phone and selected "recovery" phone rebooted and Magisk installed.???
Many many thanks to op and everyone involved.
Can anyone make a video with installation of Magisk on this device, PLEASE!! Will be more easy..
I am thinking my original problem is with Magisk itself. For some reason I randomly lose root after a restart, and booting recovery just goes straight back to the bootloader. It hasnt happened to me again, but it happened twice yesterday.
I am usually good a bug tracking, but I have been unable to narrow this down to a specific thing.
Anyway.... today things are working great.
moochermick said:
Ok here's what worked...
Reflashed all firmware and restarted phone,
Flashed patched boot.img and in fastboot on pc "fastboot continue" phone rebooted.
Back into fastboot on phone and selected "recovery" phone rebooted and Magisk installed.
Many many thanks to op and everyone involved.
Click to expand...
Click to collapse
Can you bring me your steps for install Magisk on your device with variant that you have, please?
I would suggest for people having trouble with getting magisk installed
A few things to note
No will need to boot into fastboot then use volume keys to
Select recovery option Everytime you boot or you won't be rooted
Stay on the beta of magisk cause stable is not ready for our device
If you brick use rsd lite with latest firmware
Thats on https://mirrors.lolinet.com/firmware/moto/channel/official/
How to boot in fastboot is volume up and power key
When you flash firmware via rsd lite it will factory reset your phone
Then after that setup your phone but don't connect to WiFi or do
Just enable developer options
USB debugging
Plug phone into PC
If you don't have the us varient of the phone get the firmware for your phone
transfer the boot.img from your firmware to your phone
install magisk manager from the original post
Then follow the instructions to install magisk
ALSO MAKE SURE YOUR BOOTLOADER IS UNLOCKED
Or you will brick your phone
Hope that helps
I have had a successful install pretty stable been running great for I think 3days now
Mods I installed
Viper4android
Energized
Edxposed needs riru core to work
Gravitybox for pie requires edxposed
Anyone have the boot.img for firmware
PPYS29.105-134-2
---------- Post added at 10:50 PM ---------- Previous post was at 10:44 PM ----------
Linuxassassin said:
I have had a successful install pretty stable been running great for I think 3days now
Mods I installed
Viper4android
Energized
Edxposed needs riru core to work
Gravitybox for pie requires edxposed
Click to expand...
Click to collapse
How you could flash the modules?
thx
Linuxassassin said:
I would suggest for people having trouble with getting magisk installed
A few things to note
No will need to boot into fastboot then use volume keys to
Select recovery option Everytime you boot or you won't be rooted
Stay on the beta of magisk cause stable is not ready for our device
If you brick use rsd lite with latest firmware
Thats on
How to boot in fastboot is volume up and power key
When you flash firmware via rsd lite it will factory reset your phone
Bro thank you so much rsd lite unbricked my device!
Then after that setup your phone but don't connect to WiFi or do
Just enable developer options
USB debugging
Plug phone into PC
If you don't have the us varient of the phone get the firmware for your phone
transfer the boot.img from your firmware to your phone
install magisk manager from the original post
Then follow the instructions to install magisk
ALSO MAKE SURE YOUR BOOTLOADER IS UNLOCKED
Or you will brick your phone
Hope that helps
Click to expand...
Click to collapse
Bro thank you so much rsd lite unbricked my device!
Fdraco10 said:
Anyone have the boot.img for firmware
PPYS29.105-134-2
---------- Post added at 10:50 PM ---------- Previous post was at 10:44 PM ----------
How you could flash the modules?
Click to expand...
Click to collapse
You search riru core in modules
Install that reboot to recovery
Flash edxposed
Funfact gsi won't flash on a phone till we get unofficial twrp
So I use gravitybox for pie hence my power menu
Related
First of all the guide i took it from @Vedrick by searching here in XDA. I just opened this post because i found his guide with a little bit hardness and its easier now for ya.
Well lets start. FIRST Back up all your data.
I was on the latest version of CLT-L29 Huawei p20 pro 6/128 9.0.0.195(C432E5R1P9) if you try it on another version let me know
As always, if you do this it's at your own risk.
PREREQUIREMENTS:
Watch my video on youtube that made to help you guys
1) ADB, Fastboot and Drivers
2)Patched boot image
3) A pc of course.
4) Make sure your phone is not bootloop and working
5)Enable Debugging and OEM unlocking from dev options
This is how i got root on EMUI 9 without TWRP recovery
1 - I Flashed Get your phone on fastboot mode FIRST MAKE SURE YOUR PHONE HAS UNLOCKED BOOTLOADER (download it, and move it on your adb folder-default is on C: drive) (press SHIFT button and right click on the adb folder->select open here PowerShell) type the command fastboot flash recovery_ramdisk patched_boot.img
2-Reboot phone, install Magisk manager last apk from google , go into settings, and change the update channel to custom: )COPY AND PASTE THIS LINKhttps://raw.githubusercontent.com/topjohnwu/magisk_files/master/canary_builds/release.json, go back to the Magisk home screen and hit install, download the odd Magisk file.zip file.
3-Reboot phone, press and hold the volume up key if it goes to ERecovery then reboot again and keep pressing like the video.
4-Open Magisk app, install the zip, then patch, and install the downloaded Magisk.zip file if it says direct install(recommender choose this should say this)
5-Reboot phone, press and hold the volume up key and your phone should boot just fine.(like i said above and like i show the video)
6-Open Magisk, install, select direct install option. and reboot.
Note:
1 - Now your phone will reboot into the recovery every time on its own, which is a good thing, you no longer need to hold the volume up key every time you reboot, it does it for you. This means no TWRP.
2 - In order to apps root access for the first time you need to have Magisk open, or you wont get prompted for approval. Then the app will have permanent root access.
3- You can enter fastboot mode from connecting your phone to pc and open adb as i say above and type adb reboot bootloader OR by turn off your phone, press the down button volume and after 3 secs connect the cable on your pc DONT LEAVE THE DOWN BUTTON
Usefull Commands: If you cannot enter bootloader mode ( IS NEEDED ) type this command on the adb , but first connect your phone with your PC/LAPTOP adb reboot bootloader
IF you have any questions fell free to comment bellow. Also i am gonna try some things to flash twrp and have it for ever because @Vedrick i think couldnt flash twrp recovery
Hi,
thanks a lot taking time for this guide but there are 2 things that I think are confusing :
FIRST - Once you have flashed recovery_ramdisk partition with the patched_boot.img file through fastboot , and you reboot holding up volume button, the phone boots. But after installing latest magisk manager, even without changing the update channel adress, phone is already rooted and you can add modules, etc...
SECOND - when following the guide step by step, part 4 is a problem because it finds new version and asks tout update. And when you do, the guide says install then to patch the tout install the downloaded file.
That part ils not clear as you do not tell what file to patch at this state....
If you could clear that part it would be perfect.
deltaman83 said:
Hi,
thanks a lot taking time for this guide but there are 2 things that I think are confusing :
FIRST - Once you have flashed recovery_ramdisk partition with the patched_boot.img file through fastboot , and you reboot holding up volume button, the phone boots. But after installing latest magisk manager, even without changing the update channel adress, phone is already rooted and you can add modules, etc...
SECOND - when following the guide step by step, part 4 is a problem because it finds new version and asks tout update. And when you do, the guide says install then to patch the tout install the downloaded file.
That part ils not clear as you do not tell what file to patch at this state....
If you could clear that part it would be perfect.
Click to expand...
Click to collapse
i am gonna check it now because my phone was bricked and i cant root now
deltaman83 said:
Hi,
thanks a lot taking time for this guide but there are 2 things that I think are confusing :
FIRST - Once you have flashed recovery_ramdisk partition with the patched_boot.img file through fastboot , and you reboot holding up volume button, the phone boots. But after installing latest magisk manager, even without changing the update channel adress, phone is already rooted and you can add modules, etc...
SECOND - when following the guide step by step, part 4 is a problem because it finds new version and asks tout update. And when you do, the guide says install then to patch the tout install the downloaded file.
That part ils not clear as you do not tell what file to patch at this state....
If you could clear that part it would be perfect.
Click to expand...
Click to collapse
ok i did manage to root it again. you need to unlock your bl and press the volume up button. i edited the post
I did first time as just flashing fastboot recovery_ramdisk with patched_boot.img was enough when opening magisk manager.
Updating was the issue. SO i downloaded the original recovery_ramdisk 195 , and used that file to patch with the latest version downloaded. Then I flashed in fastboot the new patched_boot.img and all was good to latest version.
deltaman83 said:
I did first time as just flashing fastboot recovery_ramdisk with patched_boot.img was enough when opening magisk manager.
Updating was the issue. SO i downloaded the original recovery_ramdisk 195 , and used that file to patch with the latest version downloaded. Then I flashed in fastboot the new patched_boot.img and all was good to latest version.
Click to expand...
Click to collapse
why to download another patch i dont get it.
plus see my signature
Because with yours i was not on latest magisk. Now i can update each time there's a new version by patching the original recovery_ramdisk and flashing the patched_boot.img on fastboot.
I'm curently on 18.2-e05cdc83 (18104)
deltaman83 said:
Because with yours i was not on latest magisk. Now i can update each time there's a new version by patching the original recovery_ramdisk and flashing the patched_boot.img on fastboot.
I'm curently on 18.2-e05cdc83 (18104)
Click to expand...
Click to collapse
i have the same version as you. the problem is 1) you cant have twrp recovery 2) when you open a app that needs root you have to open magisk app first otherwise the permissions will fail
unfortunately no twrp recovery ...
You're right I noticed that
deltaman83 said:
unfortunately no twrp recovery ...
You're right I noticed that
Click to expand...
Click to collapse
do no try to flash twrp it bricked my device.,
Join my telegram group dude
Thanks a lot but i don't have enough time....see m'y number of posts by there lol...same on Facebook etc (f..k I'm already late for work....?).
Regards
Hi all, this method will work on my device? thanks!
P20 PRO
model: CLT-L09
Build: 9.0.0.163 (C432E5R1P9patch01) GPU Turbo
EMUI: 9.0.0
Android 9
Evasi0n3r said:
Hi all, this method will work on my device? thanks!
P20 PRO
model: CLT-L09
Build: 9.0.0.163 (C432E5R1P9patch01) GPU Turbo
EMUI: 9.0.0
Android 9
Click to expand...
Click to collapse
Hello yes sir.
Please check my signature and join my telegram
Watch my video on youtube that made to help you guys https://youtu.be/AB6wwBTfKEc
Hi. Thank you.
I did it in firmware 9.0.0.191 and worked fine.
gvflavio said:
Hi. Thank you.
I did it in firmware 9.0.0.191 and worked fine.
Click to expand...
Click to collapse
np if u want press the thanks button. also join my telegram group see the link in my signature bellow this post.
John
You are genius. Thanks working great p20 pro 9.0.0.191c605
Every time I flash the patched_boot.img and restart with volume up into recovery I have a bootloop. I have CLT-L09 pie 9.0.0.1.9.5 with the custom link for magisk. The only way to get out of the loop is to reflash the stock recovery_ramdis.img. But after flashing stock recovery, magisk has no root any more...
Any suggestions why I only get the bootloop after reflashing the patched_boot.img?
Thanks a lot!
mauritz1972 said:
You are genius. Thanks working great p20 pro 9.0.0.191c605
Click to expand...
Click to collapse
Do you have a problem when you try to pull down the quick setting touching the right or left corner of the screen?
That happens to me when I rooted it.
I need to unlock bootloader with some key, or can i just follow the guide?
I installed the Stable Android 10 on my GM1910 via TWRP, totally forgetting about maintaining root and TWRP.
So how do I bring back TWRP and root?
fastboot boot doesn't seem to work, I managed to pull the boot.img and patch it with Magisk from another device but flashing it through fastboot ends up in an endless bootanimation.
Could anyone help me? here's a link of the boot.img i pulled, it works if you flash it without magisk patching it.
Link: https://drive.google.com/file/d/1O8lF1UDwwu0zT8ro5Q1gKKfdxF-HGPEW/view?usp=sharing
(Almost) exactly the same here. I tired flashing a patched boot.img, it actually boots - but magisk manager gets stuck on the splash screen and some apps, including chrome, won't start. Trying to boot TWRP results in the phone getting stuck on the "fastboot mode" screen.
My only solution would be to downgrade, root, keep the upgrade this time. But because my ISP is doing some maintenance work I don't have wifi - and restoring my phone through mobile data does not seem to work correctly.
EDIT: In fastboot, neither bootloader version nor baseband version are show, product name is "msmnile". Has this always been that way?
EDIT 2, solution:
I extracted the boot.img from the device, and patched it using magisk on the same phone:
https://drive.google.com/file/d/1-Gf-6iXSFuYT5xDR-mnLKANvkXUHal9e/view?usp=sharing
Run this command in fastboot so you know which is the CURRENT active slot :
Code:
fastboot getvar current-slot
Run this command so you can flash the correct slot :
Code:
fastboot flash boot_X magisk_patched.img
replace X with the a or b from the command before.
:good:
dmj0shu4 said:
I installed the Stable Android 10 on my GM1910 via TWRP, totally forgetting about maintaining root and TWRP.
So how do I bring back TWRP and root?
fastboot boot doesn't seem to work, I managed to pull the boot.img and patch it with Magisk from another device but flashing it through fastboot ends up in an endless bootanimation.
Could anyone help me? here's a link of the boot.img i pulled, it works if you flash it without magisk patching it.
Link: https://drive.google.com/file/d/1O8lF1UDwwu0zT8ro5Q1gKKfdxF-HGPEW/view?usp=sharing
Click to expand...
Click to collapse
Hi sorry to hear that you got this problem and hopefully it gets fixed. I have another question: does that mean using TWRP to completely clean the device then installing Android 10 via zip will remove TWRP and fastboot everything? Does that mean after installing, everything will be refreshed like a box opened phone?
dmj0shu4 said:
I installed the Stable Android 10 on my GM1910 via TWRP, totally forgetting about maintaining root and TWRP.
So how do I bring back TWRP and root?
fastboot boot doesn't seem to work, I managed to pull the boot.img and patch it with Magisk from another device but flashing it through fastboot ends up in an endless bootanimation.
Could anyone help me? here's a link of the boot.img i pulled, it works if you flash it without magisk patching it.
Link: https://drive.google.com/file/d/1O8lF1UDwwu0zT8ro5Q1gKKfdxF-HGPEW/view?usp=sharing
Click to expand...
Click to collapse
If you have an endless boot animation you might be trying to boot from the wrong slot, try using the fastboot set_active command to change slot, then restart
h0l said:
Run this command in fastboot so you know which is the CURRENT active slot :
Run this command so you can flash the correct slot : replace X with the a or b from the command before.
:good:
Click to expand...
Click to collapse
I got a bit confused.
If the current slot is boot_a, i flash it in boot_b or am I supposed to flash on the one that isn't the current slot?
djsubterrain said:
If you have an endless boot animation you might be trying to boot from the wrong slot, try using the fastboot set_active command to change slot, then restart
Click to expand...
Click to collapse
Which is the default active slot? Is it okay to use either of the 2?
dmj0shu4 said:
Which is the default active slot? Is it okay to use either of the 2?
Click to expand...
Click to collapse
Either one should work if the rom and the rooted boot image is on it (If you are rooting). That's why you should install using TWRP, if you look in the reboot menu it will show you the active slot.
djsubterrain said:
Either one should work if the rom and the rooted boot image is on it (If you are rooting). That's why you should install using TWRP, if you look in the reboot menu it will show you the active slot.
Click to expand...
Click to collapse
I would've used TWRP but it won't let me boot into it
fastboot boot [recovery.img] does not seem to work for android 10, atleast on my case
dmjoshu4 said:
I got a bit confused.
If the current slot is boot_a, i flash it in boot_b or am I supposed to flash on the one that isn't the current slot?
Click to expand...
Click to collapse
You are supposed to flash it in the one that IS the active one. Because you do want to root the slot that you'll be booting.
does that mean using TWRP to completely clean the device then installing Android 10 via zip will remove TWRP and fastboot everything? I.e. everything will be refreshed like a box opened phone?
gh279760559 said:
does that mean using TWRP to completely clean the device then installing Android 10 via zip will remove TWRP and fastboot everything? I.e. everything will be refreshed like a box opened phone?
Click to expand...
Click to collapse
not everything, just twrp and root will be gone if you restarted without installing magisk to the inactive slot
h0l said:
(Almost) exactly the same here. I tired flashing a patched boot.img, it actually boots - but magisk manager gets stuck on the splash screen and some apps, including chrome, won't start. Trying to boot TWRP results in the phone getting stuck on the "fastboot mode" screen.
My only solution would be to downgrade, root, keep the upgrade this time. But because my ISP is doing some maintenance work I don't have wifi - and restoring my phone through mobile data does not seem to work correctly.
EDIT: In fastboot, neither bootloader version nor baseband version are show, product name is "msmnile". Has this always been that way?
EDIT 2, solution:
I extracted the boot.img from the device, and patched it using magisk on the same phone:
https://drive.google.com/file/d/1-Gf-6iXSFuYT5xDR-mnLKANvkXUHal9e/view?usp=sharing
Run this command in fastboot so you know which is the CURRENT active slot :
Code:
fastboot getvar current-slot
Run this command so you can flash the correct slot :
Code:
fastboot flash boot_X magisk_patched.img
replace X with the a or b from the command before.
:good:
Click to expand...
Click to collapse
dude, thanks for this, i was banging my head against a wall trying to get root to work. I used your patched boot img and i had the version mismatch, but i local updated my android and it has root!
dmj0shu4 said:
I would've used TWRP but it won't let me boot into it
fastboot boot [recovery.img] does not seem to work for android 10, atleast on my case
Click to expand...
Click to collapse
I have not been able to boot TWRP either in fastboot mode - got stuck at "OnePlus Logo FastBoot" black screen.
Hi guys.. can you post the steps in rooting android 10??
I've already had bootloader unlocked.
Do i need to.follow the steps intended for android 9??
Like
1. Install TWRP via fastboot.. (2files)
2. Reboot to twrp.
3. Flash magisk via twrp??
Is that it?? If so. Then after reading this thread.. some of. You mentioned about boot. Img?? Patched?? What's that supposed to mean?? Sir??
Thanks. Any advice is highly appreciated..
---------- Post added at 08:30 AM ---------- Previous post was at 08:28 AM ----------
And by the way..
Im on Gm1910 model. Global rom. Gm21AA build.. if that info would matter.. i dont actually need the root on android 9. Coz parallel app is working.. but now in android 10. It isnt working.. so.i need to root to grant su to game guardian.. thanks..
MigbyPie said:
I have not been able to boot TWRP either in fastboot mode - got stuck at "OnePlus Logo FastBoot" black screen.
Click to expand...
Click to collapse
Same.
I've read that Q/10 is different and you can't install TWRP like that anymore. Supposedly you need to use the MSM tool or the all-in-one tool but I've tried both of those and still can't boot to TWRP.
E30Nova said:
Same.
I've read that Q/10 is different and you can't install TWRP like that anymore. Supposedly you need to use the MSM tool or the all-in-one tool but I've tried both of those and still can't boot to TWRP.
Click to expand...
Click to collapse
Hopefully there will be a solution. I had tried to update from Pie to Q10 while staying rooted and it didn't work. So I had to wipe the whole device and decided to wait for a smoother root method for my device. If you have any other ideas about rooting Q10 let me know. Thank you
h0l said:
(Almost) exactly the same here. I tired flashing a patched boot.img, it actually boots - but magisk manager gets stuck on the splash screen and some apps, including chrome, won't start. Trying to boot TWRP results in the phone getting stuck on the "fastboot mode" screen.
My only solution would be to downgrade, root, keep the upgrade this time. But because my ISP is doing some maintenance work I don't have wifi - and restoring my phone through mobile data does not seem to work correctly.
EDIT: In fastboot, neither bootloader version nor baseband version are show, product name is "msmnile". Has this always been that way?
EDIT 2, solution:
I extracted the boot.img from the device, and patched it using magisk on the same phone:
https://drive.google.com/file/d/1-Gf-6iXSFuYT5xDR-mnLKANvkXUHal9e/view?usp=sharing
Run this command in fastboot so you know which is the CURRENT active slot :
Code:
fastboot getvar current-slot
Run this command so you can flash the correct slot :
Code:
fastboot flash boot_X magisk_patched.img
replace X with the a or b from the command before.
:good:
Click to expand...
Click to collapse
You saved my life! Thank you!
But how do we get twrp now? Is there any way?
Me too. Use tool all in one but it doesnt work. Stuck at "waiting twrp boots".
Any help, thanks.
Same here any Solution?
Sent from my GM1911 using Tapatalk
---------- Post added at 08:14 AM ---------- Previous post was at 08:14 AM ----------
Stuck at Fastboot booting when flashed img and also zip
Sent from my GM1911 using Tapatalk
I updated my phone to 10 last night, followed the same guide as I have for every other update but this time I lost root for some reason.
I still have TWRP recovery on there but it can't read internal storage so I can't flash Magisk.
I tried changing file system to ext 2 then back to 4 and then repairing it as I read elsewhere and this wiped the phone obviously but internal storage seemed to be working until I set the phone up again, downloaded Magisk, rebooted to recovery and I'm back where I started, internal storage showing as 0mb in TWRP.
Any ideas how to fix?
Hi there just incase someone else who had problems [like me]
who is hesitant or looking for a guide on how to install Blu_Spark TWRP and Root the device.
The guide below will work 99.9% of the time. just follow the instructions carefully
Necessary Files:
Install OnePlus 6 Driver
Install Fastboot Drivers
TWRP Image
Magisk 20.1
twrp-3.3.1-x_blu_spark_v9.107_op6
Stock boot image thanks [URL="https://forum.xda-developers.com/member.php?u=6994095" @Akhil701[/URL]
Step 1: [dont do this if you have installed ADB and Fastboot already]
Install Oneplus 6, ADB and Fastboot Drivers from the link above
* Reboot PC after installing
Step 2:
Put
Code:
Stock Boot Image [boot.img]
twrp-3.3.1-x_blu_spark_v9.107_op6.zip and
Magisk-v20.1.zip
on your internal storage
Also Put
Code:
twrp-3.3.1-11-enchilada-Q-mauronofrio.img
on your desktop
Step 3: Reboot device in fastboot/bootloader mode
Step 4: Connect Device to PC Via USB Cable
Step 5: On your desktop Press Shift Right Click then click the [Open Command Prompt Here]
Step 6: on the CMD Windows Type
Code:
fastboot devices
Press enter and see if your device shows up.
Step 7: type in the CMD Window
Code:
fastboot flash boot twrp-3.3.1-11-enchilada-Q-mauronofrio.img
press enter then after that on your phone screen use volume up or down button to reboot to recovery
Step 8:
Once you have the TWRP Screen
flash the stock boot image [boot.img] in boot partition [DO NOT Reboot!]
now go back and flash the Blu_Spark TWRP and then reboot to recovery
Step 9: Rooting
Flash Magisk 20.1.zip then reboot to system.
Thats it! no data will be wiped as long as your bootloader is already unlocked.
thanks to
@Funk Wizard for the initial instruction on how to install twrp and root
@eng.stk for the Blu_Spark TWRP
@mauronofrio for the initial TWRP Image
@Akhil701 for the stock boot.img
@remewer for inspiration to build this guide.
Patched boot.img or why we need the boot image after flashing OOS10 via local update?
Sh0X31 said:
Patched boot.img or why we need the boot image after flashing OOS10 via local update?
Click to expand...
Click to collapse
im not sure about that also. im just hesitant to skip that step. it might break something. thats why i added that step on this guide
Thnx, this was a very easy walkthrough.
Only thing I want to say is that not everyone knows how to flash the 'boot.img' through TWRP. Maybe you can explain that in more detail.
no patched boot.img you need
1. connect your OP6 to PC
2. flash TWRP (from mauronofrio) by fastboot from PC
3. reboot from fastboot to recovery
4. in TWRP flash stock img OOS, don´t reboot
5. in TWRP flash TWRP (blu_spark 9.107)
6- reboot to TWRP to another slot
7. in TWRP flash Magisk 20.1
8. reboot to system
I have noticed this too, probably they have changed somehow the system, even fastboot boot doesn't work anymore....
I had to install magisk via boot.img patching
Functionally on OOS 10.0.1 OP6 ?
So I was unable to flash the new OTA through twrp running on my rooted OP6.
As such, I opted to install the new OTA through the "local install" option.
That worked great. Settings area all the same. Bootloader still unlocked (I double checked).
Drivers are all installed on my Windows 10 PC.
However, no matter what I attempt to flash from command prompt I always get:
FAILED (remote: unkown command)
Does anyone know of a solution yet?
I have been reinstalling drivers and rebooting my PC with no luck thus far.
Any ideas?
Thanks in advance.
Update:
Whelp now that it is upgraded to Android 10 (and was wiped of all data when I locked and then unlocked the bootloader again) it will not allow me to downgrade back to Andriod 9 through the local upgrade option and since I can not get fastboot to accept any commands I am stuck now in Andriod 10 without the ability to change anything at the moment.
Brisky86 said:
So I was unable to flash the new OTA through twrp running on my rooted OP6.
As such, I opted to install the new OTA through the "local install" option.
That worked great. Settings area all the same. Bootloader still unlocked (I double checked).
Drivers are all installed on my Windows 10 PC.
However, no matter what I attempt to flash from command prompt I always get:
FAILED (remote: unkown command)
Does anyone know of a solution yet?
I have been reinstalling drivers and rebooting my PC with no luck thus far.
Any ideas?
Thanks in advance.
Update:
Whelp now that it is upgraded to Android 10 (and was wiped of all data when I locked and then unlocked the bootloader again) it will not allow me to downgrade back to Andriod 9 through the local upgrade option and since I can not get fastboot to accept any commands I am stuck now in Andriod 10 without the ability to change anything at the moment.
Click to expand...
Click to collapse
i knew it while reading but thanks to the screenshot you provided you saved me from sounding "user error" once again and piss of so many who prefer to blame things and others LOL
in short, wrong command, it's fastboot flash boot <image name>
BTW and since i'm already at it, if anyone has a Mac runniing 10.15 "Catalina" and fastboot is working from terminal, i'd like to learn how he/she's done it
just came to my mind to ask here since i have to use windows 10 under parallels desktop to fastboot flash my android stuff at the moment and of course that's just an "Emergency" choice for me, everyone using both platforms will understand
magnamentis said:
i knew it while reading but thanks to the screenshot you provided you saved me from sounding "user error" once again and piss of so many who prefer to blame things and others LOL
in short, wrong command, it's fastboot flash boot <image name>
BTW and since i'm already at it, if anyone has a Mac runniing 10.15 "Catalina" and fastboot is working from terminal, i'd like to learn how he/she's done it
just came to my mind to ask here since i have to use windows 10 under parallels desktop to fastboot flash my android stuff at the moment and of course that's just an "Emergency" choice for me, everyone using both platforms will understand
Click to expand...
Click to collapse
Wow. Okay.
This is becoming a comedy of errors on my part.
Oh boy now I am getting Qualcom flashdump messages...
Huh now it is just booting normal but not letting me get into the new recovery flash...
I got it all fixed.
Thank you everyone for your help and patience with my posts.
Does 10.0.1 still have the ability to do screen-off gestures for music? I like 10 but on my wife's 7t, either she didn't turn them on, our it didn't have them so I'm curious if there same thing is happening with this? I also noticed on her 7t, constant data problems when's switching from WiFi to data. Sometimes data won't come back and only a reboot solves. I know it's a bug on OOS 10 on 7t but wondering if it's a device specific bug or an Android 10 bug? Anyone having op6 issues with data not coming back when switching from WiFi?
WIFI problem solved!
Below OOS 10.0.1 back inTWRP
Wipe: cache, system and vendor
Flash OOS 10
Flash boot img
Flash TWRP
Flash Magisk
Reboot system
Reboot recovery
Flash OOS 10.0.1
Flash boot img
Flash TWRP
Flash Magisk
Reboot system
Wifi works
After rooting 10.0.1 with magisk 20.1 mobile network is gone. no sim pin, no metwork. after unroot everything is fine
Hello Mates,
i updated my rooted oneplus 6 from 10 to 10.01 and after that use this method to root again. But there is a Problem now: My WiFi doesnt work? I cant activate it.
Do anybody know how i can fix that Problem?
Thank you in Advance
Best Regards
Coktail
As above. No wifi, no sound. What's going on?
Coktail said:
Hello Mates,
i updated my rooted oneplus 6 from 10 to 10.01 and after that use this method to root again. But there is a Problem now: My WiFi doesnt work? I cant activate it.
Do anybody know how i can fix that Problem?
Thank you in Advance
Best Regards
Coktail
Click to expand...
Click to collapse
cubic25 said:
As above. No wifi, no sound. What's going on?
Click to expand...
Click to collapse
Look 2 posts up...
ryanallaire said:
Look 2 posts up...
Click to expand...
Click to collapse
Unroot doesn't work for me. Still no wifi and audio.
Hi guys, sorry to resurrect this thread. I did everything in the correct order using 10.0.3.0 and after step 8 (reboot after flashing blu_spark) my phone gets stuck on blu_spark splash screen without any option to boot into twrp. Normal boot results in bootloop... Any ideas? Do I need to use different versions of twrp.img and .zip?
dynamode said:
Hi there just incase someone else who had problems [like me]
who is hesitant or looking for a guide on how to install Blu_Spark TWRP and Root the device.
The guide below will work 99.9% of the time. just follow the instructions carefully
@Funk Wizard for the initial instruction on how to install twrp and root
@eng.stk for the Blu_Spark TWRP
@mauronofrio for the initial TWRP Image
@Akhil701 for the stock boot.img
@remewer for inspiration to build this guide.
Click to expand...
Click to collapse
Hello.
I´m on 10.3.0 op6, I followed all the steps and when i finish the step 8 and reboot, i stuck on the recovery message. I repeat all the steps flashing clean rom and always have the same problem.....
Can someone help me? Because i don´t know another way for installing magisc....
Thanks!!!
loggstar said:
Hi guys, sorry to resurrect this thread. I did everything in the correct order using 10.0.3.0 and after step 8 (reboot after flashing blu_spark) my phone gets stuck on blu_spark splash screen without any option to boot into twrp. Normal boot results in bootloop... Any ideas? Do I need to use different versions of twrp.img and .zip?
Click to expand...
Click to collapse
I am in exactly the same position here.
Followed all the steps and am now stuck on the blu_spark boot screen for the past 15 minutes
May 2020 QQ2A.200501.001.B2 "CORAL" Magisk-Patched Boot Img [+UPDATE/KEEP ROOT GUIDE]
Another month, another update. I'll keep churning out these patched / stock file uploads and easy noob-friendly update guides while guinea pigging the updates, so long as my area is still on lockdown and I'm not back to work yet, lol.
I've also installed and tested / verified that Kirisakura 4.2.0 is working great with this month's patch so far.
Also have EdXposed Canary 0.5.0.0 (4548) YAHFA installed. SafetyNet still passing as of now.
Magisk v20.4 Patched Boot Image: https://www.androidfilehost.com/?fid=4349826312261796392
Factory Untouched Boot Image: https://www.androidfilehost.com/?fid=4349826312261796399
THESE FILES ARE FOR 10.0.0 (QQ2A.200501.001.B2, May 2020, All carriers except TW) ONLY! PLEASE ONLY FLASH IF YOU KNOW WHAT YOU'RE DOING!
If these files and/or guides are helpful, please drop a thanks and let me know. =)
EASY UPDATE / SEAMLESS KEEP-ROOT UPDATE PROCESS (using a PC - a very intuitive, effective, and relatively safe method).
** You can only follow this guide exactly if coming from build QQ2A.200405.005, Apr 2020. But the general idea is the same for other builds, you just need the correct files for your device.
coral-qq2a.200405.005-factory-dtbo.img: https://www.androidfilehost.com/?fid=4349826312261796390
coral-qq2a.200405.005-factory-boot.img: https://www.androidfilehost.com/?fid=4349826312261796391
May 2020 sideload OTA zip: https://dl.google.com/dl/android/aosp/coral-ota-qq2a.200501.001.b2-8309f363.zip
I DID NOT BOOT BACK INTO O/S UNTIL ALL STEPS WERE COMPLETED - I DID THIS TO ENSURE EVERYTHING WOULD BOOT BACK UP WITH MAGISK / EDXPOSED ALL RUNNING PROPERLY RIGHT AWAY
1. boot into bootloader
----------------
** I was on custom kernel, so I needed to flash BOTH the stock boot and dtbo images
2. fastboot flash boot coral-qq2a.200405.005-factory-boot.img
3. fastboot flash dtbo coral-qq2a.200405.005-factory-dtbo.img
......* these steps to restore stock recovery; dtbo.img also necessary for some kernel installations
-----------------
4. use volume keys to change selection to boot to Recovery Mode
......- when you reach the android symbol with No Command, hold power button, tap volume up, in case you've forgotten
5. choose option "Apply update from ADB"
6. adb sideload coral-ota-qq2a.200501.001.b2-8309f363.zip
7. Once the OTA sideload is done, Reboot to bootloader (you'll also notice it's now on the other slot after OTA flashed)
8. fastboot flash boot coral-qq2a.200501.001.b2-magisk_patched-20.4.img
9. done, start the phone
(Optional - Flash custom kernel. If you had a custom kernel, you need to re-flash it. I've only personally tested with Kirisakura though.)
This was a 100% seamless update that required no additional / re-setup of any of my Magisk or EdXposed setups. All of the factory files can be found here https://developers.google.com/android/images. boot.img and dtbo.img are in their corresponding full Factory Image zips, and the ota zip is under Full OTA Images.
EDIT: Issues after updating?
If you end up unable to boot or bootlooping afterwards, you most likely have a module that isn't playing nice with the new build. There are 2 main things you can do:
1. Flash the new factory untouched boot image. You will of course lose root, and all modules will be disabled. However, it should at least get you able to boot back up quickly if you're in a bind.
2. I would recommend checking Tulsadiver's thread: https://forum.xda-developers.com/pixel-4-xl/how-to/magisk-modules-disabler-booting-magisk-t3990557
Instead of reverting to stock boot image, fastboot boot (NOT FLASH) Tulsadiver's boot image. This will boot your phone in Magisk Core-Only Mode, with all modules disabled but root retained. From here you can open Magisk Manager and disable suspect modules. Before rebooting, go to Magisk Manager's settings and disable Magisk Core-Only Mode. Once you disable the incompatible module, the phone should boot back up.
Worked like a charm, just like previous months. 3 minutes total once the factory image was downloaded. (I edit the flash-all and remove the -w) Thanks a bunch!
Perfect method. Thank you.
[email protected] said:
perfect method. Thank you.
Click to expand...
Click to collapse
hi good day...
With this method can i activate motionsense and always leave it active?
I belong to a country where the factory does not come active and i would like to have it, only i have read that every time the telephone is re-enabled.
In advance thanks for the help.
I just used this Magisk file and after it boots up past the G logo - All i get is a black screen. the only thing that I can do is hold the power button and reboot to same result. I had to revert to factory boot to restore with no root. What am I missing? PS I just used step 8 and 9...
I am on the May update already///
aaronc_98 said:
I just used this Magisk file and after it boots up past the G logo - All i get is a black screen. the only thing that I can do is hold the power button and reboot to same result. I had to revert to factory boot to restore with no root. What am I missing? PS I just used step 8 and 9...
I am on the May update already///
Click to expand...
Click to collapse
It seems some of your previously installed modules/mods (using systemui) are interfering with the new update. I had the same issue a while back and eventually had to remove all Magisk modules and start afresh.
sidhaarthm said:
It seems some of your previously installed modules/mods (using systemui) are interfering with the new update. I had the same issue a while back and eventually had to remove all Magisk modules and start afresh.
Click to expand...
Click to collapse
That is the thing though. I was not rooted and I had uninstalled Magisk for the last several months. So now I wanted to root again, and followed steps 8 and 9 after installing Mag Manager. Could the sysemui mods you are referring to be from many months ago before when I uninstalled Magisk/
aaronc_98 said:
That is the thing though. I was not rooted and I had uninstalled Magisk for the last several months. So now I wanted to root again, and followed steps 8 and 9 after installing Mag Manager. Could the sysemui mods you are referring to be from many months ago before when I uninstalled Magisk/
Click to expand...
Click to collapse
Its' hard to say without knowing what is/was installed bud. In my case I had some mods that changed accent colours, fonts and clock positions etc. I learnt the hard way and always made sure that I remove such modules before upgrading. I just upgraded from April to May OTA and it all seems to have gone down well. Root restored, Face Unlock working and Kirisakura 4.5 flashed
sidhaarthm said:
Its' hard to say without knowing what is/was installed bud. In my case I had some mods that changed accent colours, fonts and clock positions etc. I learnt the hard way and always made sure that I remove such modules before upgrading. I just upgraded from April to May OTA and it all seems to have gone down well. Root restored, Face Unlock working and Kirisakura 4.5 flashed
Click to expand...
Click to collapse
Ok - does anyone have any idea hot to solve this problem given the situation? I also did the May OTA recently with no issues. would I need to download the whole factory image to solve? Any other ideas?
I just tried to install the patched img again with the same results - black screen
Thank you in advance for any help!
aaronc_98 said:
Ok - does anyone have any idea hot to solve this problem given the situation? I also did the May OTA recently with no issues. would I need to download the whole factory image to solve? Any other ideas?
I just tried to install the patched img again with the same results - black screen
Thank you in advance for any help!
Click to expand...
Click to collapse
Yes, hang on, let me find the steps I took to fix.
---------- Post added at 10:36 PM ---------- Previous post was at 10:32 PM ----------
aaronc_98 said:
Ok - does anyone have any idea hot to solve this problem given the situation? I also did the May OTA recently with no issues. would I need to download the whole factory image to solve? Any other ideas?
I just tried to install the patched img again with the same results - black screen
Thank you in advance for any help!
Click to expand...
Click to collapse
Look at this post - https://forum.xda-developers.com/showpost.php?p=81926759&postcount=46
I had success following these instructions. There's some other posts I found on XDA where users had similar issue - this is the only way without having to fully wipe and restore.
Hope it helps!:good:
aaronc_98 said:
Ok - does anyone have any idea hot to solve this problem given the situation? I also did the May OTA recently with no issues. would I need to download the whole factory image to solve? Any other ideas?
I just tried to install the patched img again with the same results - black screen
Thank you in advance for any help!
Click to expand...
Click to collapse
Just curious, but are you fastbooting the patched.img via power shell or command prompt? And, are your platform-tools up to date, and are you using a USB A to C cable?
Badger50 said:
Just curious, but are you fastbooting the patched.img via power shell or command prompt? And, are your platform-tools up to date, and are you using a USB A to C cable?
Click to expand...
Click to collapse
Fastbooting from command prompt
Platform tools downloaded yesterday
Yes on the USB cable
---------- Post added at 10:42 PM ---------- Previous post was at 10:41 PM ----------
sidhaarthm said:
Yes, hang on, let me find the steps I took to fix.
---------- Post added at 10:36 PM ---------- Previous post was at 10:32 PM ----------
Look at this post - https://forum.xda-developers.com/showpost.php?p=81926759&postcount=46
I had success following these instructions. There's some other posts I found on XDA where users had similar issue - this is the only way without having to fully wipe and restore.
Hope it helps!:good:
Click to expand...
Click to collapse
Unfortunatey, it does not look like it is working for me, when I open an abd shell and then type su nothing happens. What is supposed to happen? The curorsor just move down to the next line.
This is of course after fastbooting the patched img and have the system ui crash (black screen)
Try booting in Magisk Core-Only mode. If it boots, it probably was an old module causing the issue. Then you can open Magisk Manager and try disabling modules until you find the problematic one, and remove it.
See this thread for more info: https://forum.xda-developers.com/pixel-4-xl/how-to/magisk-modules-disabler-booting-magisk-t3990557
I haven't had to boot into Magisk core mode yet on this device so I can't help you much. But according to Tulsadiver (OP of that thread), I believe he said the April boot image works fine for May (see pg 13).
Good luck!
i5lee8bit said:
Try booting in Magisk Core-Only mode. If it boots, it probably was an old module causing the issue. Then you can open Magisk Manager and try disabling modules until you find the problematic one, and remove it.
See this thread for more info: https://forum.xda-developers.com/pixel-4-xl/how-to/magisk-modules-disabler-booting-magisk-t3990557
I haven't had to boot into Magisk core mode yet on this device so I can't help you much. But according to Tulsadiver (OP of that thread), I believe he said the April boot image works fine for May (see pg 13).
Good luck!
Click to expand...
Click to collapse
Unfortunately, I dont think that i can do this since it says you must be rooted for either method. The problem is that I am not rooted and have not been for some time, but now i am trying to root via magisk...
aaronc_98 said:
Unfortunately, I dont think that i can do this since it says you must be rooted for either method. The problem is that I am not rooted and have not been for some time, but now i am trying to root via magisk...
Click to expand...
Click to collapse
Try flashing the May Magisk patched boot image (which will root the phone), then fastboot boot image-new.img (NOT FLASH), the image Tulsadiver shares in his OP: https://androidfilehost.com/?fid=4349826312261766039 - don't worry the device says Pixel XL in AFH - he probably just uploaded it to an old folder of his. It's definitely the 4 XL core only boot image.
This should start up your phone rooted, but with all modules disabled.
Edit: also, I'm pretty sure he's referring to needing root in order to follow his processes and use those methods to generate the core-only boot image itself. However, he provides the bootable image for you luckily. Either way, I would still flash the May Magisk patched boot image first, otherwise when you reboot after booting core mode it'll just boot back into the existing boot file (in your case, stock). Also, I just tested for you, and that image-new.img works perfectly fine. I just tried it on my phone and it booted into core mode, exactly as if I did it through Magisk Manager. I also didn't need to use the additional script or delete the .disable_magisk file in the /cache folder - all I needed to do was uncheck core only mode in Magisk Manager. YMMV. I would also recommend installing Magisk Manager .apk before any of this to make your life easier.
So for you:
1. Install Magisk Manager if you haven't already - https://github.com/topjohnwu/Magisk/releases/tag/manager-v7.5.1
2. Reboot into bootloader
3. fastboot flash boot coral-qq2a.200501.001.b2-magisk_patched-20.4.img
4. fastboot boot image-new.img
5. Hopefully the O/S loads, open Magisk Manager, disable offending modules.
6. In Magisk Manager, go to settings and uncheck "Magisk Core Only Mode" option.
7. Reboot.
i5lee8bit said:
Try flashing the May Magisk patched boot image (which will root the phone), then fastboot boot image-new.img (NOT FLASH), the image Tulsadiver shares in his OP: https://androidfilehost.com/?fid=4349826312261766039 - don't worry the device says Pixel XL in AFH - he probably just uploaded it to an old folder of his. It's definitely the 4 XL core only boot image.
This should start up your phone rooted, but with all modules disabled.
Edit: also, I'm pretty sure he's referring to needing root in order to follow his processes and use those methods to generate the core-only boot image itself. However, he provides the bootable image for you luckily. Either way, I would still flash the May Magisk patched boot image first, otherwise when you reboot after booting core mode it'll just boot back into the existing boot file (in your case, stock). Also, I just tested for you, and that image-new.img works perfectly fine. I just tried it on my phone and it booted into core mode, exactly as if I did it through Magisk Manager. I also didn't need to use the additional script or delete the .disable_magisk file in the /cache folder - all I needed to do was uncheck core only mode in Magisk Manager. YMMV. I would also recommend installing Magisk Manager .apk before any of this to make your life easier.
So for you:
1. Install Magisk Manager if you haven't already - https://github.com/topjohnwu/Magisk/releases/tag/manager-v7.5.1
2. Reboot into bootloader
3. fastboot flash boot coral-qq2a.200501.001.b2-magisk_patched-20.4.img
4. fastboot boot image-new.img
5. Hopefully the O/S loads, open Magisk Manager, disable offending modules.
6. In Magisk Manager, go to settings and uncheck "Magisk Core Only Mode" option.
7. Reboot.
Click to expand...
Click to collapse
Thank you! You are my hero! Thank you for taking the time to explain this- everything is working as expected
aaronc_98 said:
Thank you! You are my hero! Thank you for taking the time to explain this- everything is working as expected
Click to expand...
Click to collapse
Glad it worked out for you. Make sure you thank Tulsadiver for his work too, his core-only guide is totally clutch
I'm gonna edit the OP for some basic steps in case of errors. Thanks for keeping us posted.
i5lee8bit said:
Another month, another update. I'll keep churning out these patched / stock file uploads and easy noob-friendly update guides while guinea pigging the updates, so long as my area is still on lockdown and I'm not back to work yet, lol.
Click to expand...
Click to collapse
Thanks for the patched kernel. I usually patch the kernel before I flash the update so I can boot with a patched kernel after the update. I was distracted and forgot. You saved me bunch of extra work!
Little hint from a Xperia 5 User.
use: fastboot --set-active=b
To change to the B System and repeat the Steps for the Kernel flashing. Magisk likes that to survive OTA Updates.
use: fastboot --set-active=a
To change back to the Primary System and boot up. Install Magisk Manager and You are good to go! System Images are flashing in both Slots without the need to do that. But Kernels have to be flashed in both Slots if they are changed. Figured that out by inspecting some Zips who are Magisk and Kernel related.
BR
---------- Post added at 16:44 ---------- Previous post was at 16:43 ----------
Little hint from a Xperia 5 User.
use: fastboot --set-active=b
To change to the B System and repeat the Steps for the Kernel flashing. Magisk likes that to survive OTA Updates.
use: fastboot --set-active=a
To change back to the Primary System and boot up. Install Magisk Manager and You are good to go! System Images are flashing in both Slots without the need to do that. But Kernels have to be flashed in both Slots if they are changed. Figured that out by inspecting some Zips who are Magisk and Kernel related.
BR
It was posted about 2 hours ago on Asus website, here is the direct link: https://dlcdnets.asus.com/pub/ASUS/...300-2304-user.zip?model=rog phone 5 （zs673ks）
I just updated and phone runs smooth, no data loss during upgrade, magisk and lsposed works.
MarekPietrzak said:
It was posted about 2 hours ago on Asus website, here is the direct link: https://dlcdnets.asus.com/pub/ASUS/ZenFone/ZS673KS/UL-ASUS_I005_1-ASUS-33.0210.0210.200-1.1.300-2304-user.zip?model=rog phone 5 （zs673ks）
I just updated and phone runs smooth, no data loss during upgrade, magisk and lsposed works.
Click to expand...
Click to collapse
hey Marek, i was on android 12, i flashed twrp recovery then i relocked the bootloader!
so i was stuck in bootloader infinity loop, then i downgraded my phone to an very old firmware it is begin with 18 and ends with .raw archive format and mine was beginn 31 and ends wtih zip archive format (it has payload.bin) inside.
so i get failed flashing manuelly the last update of android 12 also the last update (android 13). OTA can nothing getting. what should i do now if you don't mind!?
Edit: the phone doesnt charging and loops now at logo
Hello, you should incrementally update from your version by downloading each upgrade package from Asus site which is newer then your current version and flash them one by one. Or you can find the newest package which you are able to install and repeat this procedure until you can flash the newest Android 13 package. Your current old firmware cannot unpack newest package so you need update by steps.
Check this post: https://forum.xda-developers.com/t/warning-read-before-locking-bootloader.4327977/post-87808387
Other method (untested): Extract latest payload.bin and flash all partitions to inactive slot than change it to active using fastboot
rami88436 said:
hey Marek, i was on android 12, i flashed twrp recovery then i relocked the bootloader!
so i was stuck in bootloader infinity loop, then i downgraded my phone to an very old firmware it is begin with 18 and ends with .raw archive format and mine was beginn 31 and ends wtih zip archive format (it has payload.bin) inside.
so i get failed flashing manuelly the last update of android 12 also the last update (android 13). OTA can nothing getting. what should i do now if you don't mind!?
Edit: the phone doesnt charging and loops now at logo
Click to expand...
Click to collapse
MarekPietrzak said:
Hello, you should incrementally update from your version by downloading each upgrade package from Asus site which is newer then your current version and flash them one by one. Or you can find the newest package which you are able to install and repeat this procedure until you can flash the newest Android 13 package. Your current old firmware cannot unpack newest package so you need update by steps.
Check this post: https://forum.xda-developers.com/t/warning-read-before-locking-bootloader.4327977/post-87808387
Other method (untested): Extract latest payload.bin and flash all partitions to inactive slot than change it to active using fastboot
Click to expand...
Click to collapse
MarekPietrzak said:
Hello, you should incrementally update from your version by downloading each upgrade package from Asus site which is newer then your current version and flash them one by one. Or you can find the newest package which you are able to install and repeat this procedure until you can flash the newest Android 13 package. Your current old firmware cannot unpack newest package so you need update by steps.
Check this post: https://forum.xda-developers.com/t/warning-read-before-locking-bootloader.4327977/post-87808387
Other method (untested): Extract latest payload.bin and flash all partitions to inactive slot than change it to active using fastboot
Click to expand...
Click to collapse
hey, Thanks for replay, i am facing now another messeges.
1- the phone does not charging at all
2- when i plug in into chrage its reboot again and again.
3- the bootloader is open, but when i try to flash any files through bootloader i get:
FAILED (Status read failed (Too many links))
or
FAILED (remote: 'Warning: battery's capacity is very low
to recovery mode i am unable to go there
i tried boot or flash the twrp.img also only boot.img also flash_raw_and_wipe_data.cmd
nothing helps me!!!
Hello, can you try to keep phone on charger for a few hours? Maybe it will charge enough to enter recovery mode. You should never flash twrp by fastboot on a/b devices as they don't have recovery partition. Please restore stock boot.img extracted from payload.bin and after this try booting into fastbootD, not fastboot and then attempt flashing complete firmware package (raw). To boot into fastbootD, keep holding volume keys, when you see a bootloader screen use volume keys to select option "recovery mode". You should now enter stock recovery. Ussing vol keys select option "enter fastboot". You should be now in fastbootD. This is possible only with boot.img without twrp installed as fastbootD is a part of stock recovery, magisk is fine.
Remember to perform all flashing operations with usb port on the left side, the bottom one does not work in bootloader. And make sure you are using latest adb/fastboot binaries, these from popular auto-installers are usually outdated and may cause errors during flashing.
MarekPietrzak said:
Hello, can you try to keep phone on charger for a few hours? Maybe it will charge enough to enter recovery mode. You should never flash twrp by fastboot on a/b devices as they don't have recovery partition. Please restore stock boot.img extracted from payload.bin and after this try booting into fastbootD, not fastboot and then attempt flashing complete firmware package (raw). To boot into fastbootD, keep holding volume keys, when you see a bootloader screen use volume keys to select option "recovery mode". You should now enter stock recovery. Ussing vol keys select option "enter fastboot". You should be now in fastbootD. This is possible only with boot.img without twrp installed as fastbootD is a part of stock recovery, magisk is fine.
Remember to perform all flashing operations with usb port on the left side, the bottom one does not work in bootloader. And make sure you are using latest adb/fastboot binaries, these from popular auto-installers are usually outdated and may cause errors during flashing.
Click to expand...
Click to collapse
I've tried leaving it on overnight and it never charges, there's even no charging lights.
Yesterday I tried flashing via Bugjeager and it didn't work either (betwenn to android devices)
Although the bootloader is unlocked, it gives me a Not Allowed In Lock State message!
the current version of the installed firmware is that old that i flashed WW_ZS673KS_18.0810.2101.95_M2.13.24.9-ASUS_1.1.46_Phone-user.raw, it is non extractable so i cant get the boot.img of it!
I am attaching here the matching boot.img for your 2101.95 firmware. Your phone boots to bootloader as I can see on the video but cannot enter recovery as you have corrupted your boot partition. Can you pm me output of fastboot getvar all command? Please do not post it publicly as it may contain private data such as serial numbers. Good luck!
Are you sure that you have unlocked bootloader? I understand that you have relocked your bootloader and since then your phone never booted into working system. It is not possible to unlock bl with fastboot, only with asus app which requires working Android system
MarekPietrzak said:
I am attaching here the matching boot.img for your 2101.95 firmware. Your phone boots to bootloader as I can see on the video but cannot enter recovery as you have corrupted your boot partition. Can you pm me output of fastboot getvar all command? Please do not post it publicly as it may contain private data such as serial numbers. Good luck!
Are you sure that you have unlocked bootloader? I understand that you have relocked your bootloader and since then your phone never booted into working system. It is not possible to unlock bl with fastboot, only with asus app which requires working Android system
Click to expand...
Click to collapse
wow you are alive haha i thought you not gonna answer me again. ok just 1 second
rami88436 said:
wow you are alive haha i thought you not gonna answer me again. ok just 1 second
Click to expand...
Click to collapse
Sometimes I can be a bit slow to respond as I am on the university during day. Hopefully your issue seems to be possible to be solved just by flashing raw firmware and wiping data partition.
so i was rooted on 12 when update was done i did the usual and hit "later" went into magisk did thr ota to keep root once it booted i was stuck on logo forever, so i flashed original boot.img and booted up good with no root. so then i patched boot in magisk and flashed it and stuck on logo again unless i flash original boot.img. this never happened before. how did you keep root?
rami88436 said:
hey Marek, i was on android 12, i flashed twrp recovery then i relocked the bootloader!
so i was stuck in bootloader infinity loop, then i downgraded my phone to an very old firmware it is begin with 18 and ends with .raw archive format and mine was beginn 31 and ends wtih zip archive format (it has payload.bin) inside.
so i get failed flashing manuelly the last update of android 12 also the last update (android 13). OTA can nothing getting. what should i do now if you don't mind!?
Edit: the phone doesnt charging and loops now at logo
Click to expand...
Click to collapse
if youre still stuck, try to fastboot flash raw firmware and reroot and re update again. twrp only works for me with the magisk twrp installer but then you'll have to re flash patched image as it will remove root
chairman011 said:
so i was rooted on 12 when update was done i did the usual and hit "later" went into magisk did thr ota to keep root once it booted i was stuck on logo forever, so i flashed original boot.img and booted up good with no root. so then i patched boot in magisk and flashed it and stuck on logo again unless i flash original boot.img. this never happened before. how did you keep root?
Click to expand...
Click to collapse
try root your phone through kirnal su
chairman011 said:
if youre still stuck, try to fastboot flash raw firmware and reroot and re update again. twrp only works for me with the magisk twrp installer but then you'll have to re flash patched image as it will remove root
Click to expand...
Click to collapse
hahaha, the owner of this thread had helps me a lot but no way and yesterday i have been lost my imei and isn and the rest.., that was because i tried using miflash.
I did it in the same way as you, just after OTA i installed magisk to inactive slot and rebooted. Maybe you have some incompatible magisk modules which caused bootloop on A13.
chairman011 said:
so i was rooted on 12 when update was done i did the usual and hit "later" went into magisk did thr ota to keep root once it booted i was stuck on logo forever, so i flashed original boot.img and booted up good with no root. so then i patched boot in magisk and flashed it and stuck on logo again unless i flash original boot.img. this never happened before. how did you keep root?
Click to expand...
Click to collapse
MarekPietrzak said:
I did it in the same way as you, just after OTA i installed magisk to inactive slot and rebooted. Maybe you have some incompatible magisk modules which caused bootloop on A13.
Click to expand...
Click to collapse
Oh ok ok makes sense. I had curl module installed. I loved android 13 but I'ma stay on 12 cause the modified read/write script only works on Android 12 and 11 and I need it to uninstall bloatware. Disabling them isn't good enough for me lol I gotta uninstall them completely. I can only do that if system is read/write and this script flashed through two works great to have read/write system. Thank you though
rami88436 said:
hahaha, the owner of this thread had helps me a lot but no way and yesterday i have been lost my imei and isn and the rest.., that was because i tried using miflash.
Click to expand...
Click to collapse
Oh ok ok makes sense. Usually when I face a brick problem I just flash raw firmware fastboot
Actually you can debloat fully systemless, just create magisk module which replaces bloatware directories with empty folders. Or even better use this: https://forum.xda-developers.com/t/module-terminal-debloater-v17-3-2-debloat-systemlessly.3584163/
It is an automated way to make packages fully disappear without remounting system as rw. This module replaces them with empty folders, just like in the manual solution. The packages disappear from system completely and if you install any debloated app from play store or apk it will be installed as user (non-system) app.
chairman011 said:
Oh ok ok makes sense. I had curl module installed. I loved android 13 but I'ma stay on 12 cause the modified read/write script only works on Android 12 and 11 and I need it to uninstall bloatware. Disabling them isn't good enough for me lol I gotta uninstall them completely. I can only do that if system is read/write and this script flashed through two works great to have read/write system. Thank you though
Click to expand...
Click to collapse
MarekPietrzak said:
Actually you can debloat fully systemless, just create magisk module which replaces bloatware directories with empty folders. Or even better use this: https://forum.xda-developers.com/t/module-terminal-debloater-v17-3-2-debloat-systemlessly.3584163/
It is an automated way to make packages fully disappear without remounting system as rw. This module replaces them with empty folders, just like in the manual solution. The packages disappear from system completely and if you install any debloated app from play store or apk it will be installed as user (non-system) app.
Click to expand...
Click to collapse
Oh wow thank you man I'll give it a shot.
I found a gui-based app on github to systemlessly debloat, it is easier to use than this script I posted link to. Here is the link: https://github.com/sunilpaulmathew/De-Bloater
Does anyone have the full RAW firmware, flashed via fastboot? Thank you all
ThienAn2023 said:
Does anyone have the full RAW firmware, flashed via fastboot? Thank you all
Click to expand...
Click to collapse
Mod. edit: private link removed. alecxs