Dear all,
am sorry maybe this has been already asked, I searched in the Pixel 3a forum but I didn't find the same question.
I enrolled to the Beta channel of updates (was because my Pixel was not updating since January!!) and I lost the root, as usual. I thought there were already solutions with Magisk on Beta 2 but I tried many and I always receive error strings.
I attempted to patch boot image with Magisk Canary to then being flashed by fastboot but I receive constantly the error: error verifying correct boot
Then I tried to flash TWRP to be able to flash Magik zip from there but it gives me another error as there was a problem to find the partition (I saw that fastboot was set on slot b and I wasn't able to change slot)
Then I tried to boot TWRP with fastboot receiving this error: Error verifying the received boot.img: Invalid Parameter
I would kindly ask if anybody has tried with success to root Android 11 Beta 2 on Pixel 3a to share the possible solutions.
Thank you
Danifeb
Edit:
In order to root I had to flash the patched boot image in the current slot with command fastboot flash boot_(slot) magisk_patched.img
I was previously just trying to send command flash boot without success..
Thank you
Related
I am unable to root my Redmi 6 Miui 11
I've followed youtube tutorials, read about this etc. but the thing is that I can't get this to wrok.
device model: redmi 6
miui global 11.0.3 | Stable 11.0.3.0 (PCGMIXM)
Android: 9 PPR1. 180610.011
ENABLED: USB debugging, USB debugging(Secutiry Settings), OEM unlocking
Unlocked the bootloader
tried latest and few older versions of TWRP for redmi 6 from the twrp.me - none of them worked as when I try to load into TWRP my screen goes all colors and depending on the version there might be a small light show of colors splashing.
Found this one to be working, from yt video - can't post link as a new user , (Although it says 6A) - never mind at least I've managed to load into TWRP.
When TWRP starts
it says: Mount Decrypt Data - since I do not have lock set I go to CANCEL
go to INSTALL -> says internal Storage (0MB), so I use SD card to install Magisk-v20.4.zip I confirm and see following errors:
Decrypt process ended with signal: 11
Failed to decrypt data.
Unable to decrypt with default password. You may need to preform Format Data.
then a bit later...
Unable to mount /data/media/TWRP/twrps_wzsx150
Is there any way I can bypass this issue? What should I do and what is the safest thing?
I am trying for 2 days to solve this issue but I am not sure what to do at this point.
If somebody know what should I do in order to root my device please tell me I will be grateful.
I've found the solution, the problem? I've not enough post to attach the boot img.
Go to the 4pda link of this post:
https://forum.xda-developers.com/showpost.php?p=80515805&postcount=2
Download the file "boot_11.0.3.0CN_R6_mgsk_202.img", flash the boot file with the command "fastboot flash boot boot_11.0.3.0CN_R6_mgsk_202.img", reboot, install the lastest magisk manager.
At this point you should have magisk 20.2 installed, only a problem, you can't update magisk
Don't do it!
Alex5532 said:
I've found the solution, the problem? I've not enough post to attach the boot img.
Go to the 4pda link of this post:
https://forum.xda-developers.com/showpost.php?p=80515805&postcount=2
Download the file "boot_11.0.3.0CN_R6_mgsk_202.img", flash the boot file with the command "fastboot flash boot boot_11.0.3.0CN_R6_mgsk_202.img", reboot, install the lastest magisk manager.
At this point you should have magisk 20.2 installed, only a problem, you can't update magisk
Click to expand...
Click to collapse
WARNING: Don't do it if you don't know what are you doing else your phone will be hard bricked and you need an authorized Xiaomi account to revive it.
We received a new 8t and proceeded to do root and unlock on it.
Here is my process and problem.
Unlocked bootloader.
Updated phone to recent version via OTA update.
Downloaded update via Oneplus website.
Extracted payload.bin VIA python.payload dumper.
Moved boot.img to phone and patched it with magisk (select and patch a file)
Moved patched image to PC and ran adb
Fastboot flash boot patched image name.img
rebooted , now its caught in bootloop.
Tried fastboot --set-active=a and it didnt make a difference.
When looking at adb devices it shows the attached phone as unauthorized.
Dont know if this helps
Can get into fastboot
You flashed the OS to the bootloader. Not sure how to help you, man. Maybe try the EDL Tool. That worked for me. Also, always install TWRP and flash magisk zip through TWRP. It's foolproof.
TWRP doesnt work with android 11 or the oneplus 8 as far as I know, last time I looked.
Did a tool and fixed the crashes and bootloop, then followed a youtube video and guide.
Found out I ended up doing a different OS version that didnt match.
eracet said:
TWRP doesnt work with android 11 or the oneplus 8 as far as I know, last time I looked.
Did a tool and fixed the crashes and bootloop, then followed a youtube video and guide.
Found out I ended up doing a different OS version that didnt match.
Click to expand...
Click to collapse
TWRP for the 8T works reasonably well. See https://forum.xda-developers.com/t/...recovery-project-8t-kebab-2021-09-04.4302449/
Hi guys,
I've crashed my OP9 due flash an older boot.img.
Today I updated to C61, flashed a patched C46 boot image for root.
Now the phone holds on at the OnePlus Start logo.
Has anyone an untouched boot.img from C61 Firmware?
I've installed the global Firmware, but I believe, it doesn't matter.
Thanks and regards!
[email protected] said:
Hi guys,
I've crashed my OP9 due flash an older boot.img.
Today I updated to C61, flashed a patched C46 boot image for root.
Now the phone holds on at the OnePlus Start logo.
Has anyone an untouched boot.img from C61 Firmware?
I've installed the global Firmware, but I believe, it doesn't matter.
Thanks and regards!
Click to expand...
Click to collapse
Search online I find it there 2
I'm searching for boot.img of EU version. Could you please share where you found yours?
Method confirmed to work for OnePlus 9 EU (LE2113) and OnePlus 9 Global (LE2115) - Enjoy!
Update rooted C.47 to C.61:
Open magisk, click 'Uninstall magisk'
Reboot
Updated via standard system update to C.61 . (At first it failed at 99% for me, but on second try it completed successfully). Alternatively: try the Oxygen updater to download the C.61 OTA incremental update.
Reboot
Easy way to root C.61:
Download the patched boot.img:
EU (LE2113 - Europe) from Mega
or Global (LE2115) from GDrive or Mega
Place the downloaded boot file in the same folder as your adb.
Open a terminal or command prompt in that folder and execute: "adb reboot bootloader"
Execute "fastboot boot .\C.61_boot_magisk_patched-25100_Bvj5U.img" to temporarily boot the patched boot file.
Download & install Magisk 25.1.
Open Magisk. If it indicates 'Installed Magisk: n/a', you're device was not correctly rooted. If it says 25.1, you can patch your boot to make the root stay:
Select 'Direct Install' and reboot.
Congrats!
DIY way:
All files here on a Mega folder if it helps you guys save time
Download C.61 OTA incremental update from the cellphone (both in-built system update and Oneplus Updater give the same download).
Use Payload dumper to extract the stock boot.img and copy it to your phone.
Download and install Magisk 25.1 on your phone, use 'Select and Patch a File' to patch the stock boot.img which creates magisk_patched-25100_4vi6c.img
Copy this file to your desktop and run the following commands to boot the patch:
boot in fastboot: "adb reboot bootloader" in terminal
temporarily boot the patched boot file: "fastboot boot .\magisk_patched-25100_4vi6c.img"
After reboot, open Magisk. If it indicates 'Installed Magisk: n/a', you're device was not correctly rooted. If it says 25.1, you can patch your boot to make the root stay:
Select 'Direct Install' and reboot.
Congrats!
(Optional) Way to extract your current boot file from a rooted phone:
Ensure you're rooted
Execute "adb reboot bootloader" on your pc
To check the current active boot partition execute "fastboot getvar all" on your pc and look for "(bootloader) current-slot:a" meaning you'll be using boot_a.img later on or "(bootloader) current-slot:b" for boot_b.img
Execute the following commands on your pc:
adb shell
su
dd if=/dev/block/bootdevice/by-name/boot_a of=/sdcard/Download/boot_a.img
dd if=/dev/block/bootdevice/by-name/boot_b of=/sdcard/Download/boot_b.img
exit
adb pull /sdcard/Download/boot_a.img boot_a.img
adb pull /sdcard/Download/boot_b.img boot_b.img
Whichever boot partition was active in step 3 is the one you want
xHalt said:
Same here. I can find boot.img for the OnePlus 9 Pro (EU) but not for the OnePlus 9 (EU).
I tried the payload dumper on the incremental update (instructions do tell you it doesn't work on incremental .zip, only on full .zip). I got the boot.img out of it and was able to patch with Magisk 25.1, but when booting it's not rooted yet.
All files here on a Mega folder if it helps you guys save time :
My phone: OnePlus 9 EU - LE2113
Issue I had: Couldn't update to C.61
I was on C.47, rooted with Magisk 25.1. Tried to update through the system pop-up as well as through the Oxygen Update to update to C.61. It kept failing at 21%.
Steps I took to update:
Uninstalled magisk
Updated via standard system update failed at 99%.
I retried with the Oxygen updater and now it succeeded to 100%
Rebooted
Issue: now I'm no longer rooted.
Steps I took to root again:
Downloaded C.61 OTA incremental update from the cellphone (both in-built system update and Oneplus Updater gave the same download).
Used Payload dumper to extract the stock boot.img and copied it to my phone.
Installed Magisk 25.1 on my phone, used 'Select and Patch a File' to patch the stock boot.img which created magisk_patched-25100_4vi6c.img
Copied this file to my desktop and ran the following commands to try and boot the patch:
boot in fastboot: "adb reboot bootloader" in terminal
termporarily boot the patched boot file: "fastboot boot .\magisk_patched-25100_4vi6c.img"
It takes a LONG time to boot, but eventually it does boot correctly.
Issue: however, Magisk is NOT installed and I'm not rooted yet.
I also tried to install TWRP recovery but keep getting the Qualcomm Crashdump Mode.
boot in fastboot: "adb reboot bootloader" in terminal
temporarily boot the TWRP recovery: "fastboot boot .\twrp-3.6.2_11-0-lemonadep.img" in terminal
Issue: Qualcomm Crashdump Mode pops up and is stuck there
Anyone able to figure the last step out?
Appreciated!
Click to expand...
Click to collapse
i am in a similar situation. my OP 9 (EU) is (still) on the c47 build with the latest magisk. I never updated to c48 but have now decided to give c61 a try. But iam not able to install the OTA, inbuild system is crashing @ 35%, even with the local install method and the loaded update from the oxygen updater, its still crashing. Today i uninstall magisk, flash the c47 stock boot.img and vendor_boot.img but it still crashing. After some research I tried to reset the phone. Device is now fully wiped, only the bootloader is unlocked. But i still got this crashes What did you do to install the update ? my next try is to use the MSN tool from this forum, but i'm afraid to brick my device.
I have extracted the original boot.img and vendor_boot.img from LE2115_11_C.61 using MsmDownloadTool (F8 > select the desired partitions > ReadBack) and uploaded to GoogleDrive.
My OP 9 EU version is on build C.48 (rooted with Magisk) and I also have the issue where the update crashes at 21%.
Did anyone already find a solution on how to upgrade to C.61 without data loss?
MrMagic said:
My OP 9 EU version is on build C.48 (rooted with Magisk) and I also have the issue where the update crashes at 21%.
Did anyone already find a solution on how to upgrade to C.61 without data loss?
Click to expand...
Click to collapse
I spent a few hours trying to solve the problem. no chance. I ended up using the msm tool. after that it was possible to update from C37 to C48 and finally to C61.
I just found this in the OP9 Root topic:
Root OnePlus 9
This is for Europe (11.2.2.2.LE25DA). If you are on Global, EU version works, but up to you. It appears for last year, unless you are from India, OnePlus doesn't care. It might be a while before a Full OTA update for Global is released, you'll...
forum.xda-developers.com
Apparently you can use the boot.img from the C.61 OP9 Pro build on the regular OP9.
I was finally able to go from c47 rooted to c61.
Now I have no root.
Any way to get it?
aldoc01 said:
I was finally able to go from c47 rooted to c61.
Now I have no root.
Any way to get it?
Click to expand...
Click to collapse
Try the updated instructions above. Can confirm it works now.
@xHalt Did you do anything else besides uninstalling Magisk to get the C.61 OTA update to install?
I am on C.48 and uninstalled Magisk, but I still cannot install the C.61 OTA. Tried both the standard system updater and Oxygen Updater.
Not sure why it's failing because it doesn't give any meaningful error message.
Is there a stock boot image I can flash to get past this error?
Daeril said:
I have extracted the original boot.img and vendor_boot.img from LE2115_11_C.61 using MsmDownloadTool (F8 > select the desired partitions > ReadBack) and uploaded to GoogleDrive.
Click to expand...
Click to collapse
Amazing, @Daeril ! Thank you. It works.
Updated the instructions for everyone.
MrMagic said:
@xHalt Did you do anything else besides uninstalling Magisk to get the C.61 OTA update to install?
I am on C.48 and uninstalled Magisk, but I still cannot install the C.61 OTA. Tried both the standard system updater and Oxygen Updater.
Not sure why it's failing because it doesn't give any meaningful error message.
Is there a stock boot image I can flash to get past this error?
Click to expand...
Click to collapse
I updated from C.47 and only had to reboot.
Try with the stock boot indeed: I included the stock boot for C.47 in the Mega folder or direct link here.
Alternatively: revert to C.47 first? Files also in the Mega folder.
aldoc01 said:
I was finally able to go from c47 rooted to c61.
Now I have no root.
Any way to get it?
Click to expand...
Click to collapse
Please see the updated instructions above and let me know if it works for you.
xHalt said:
Try with the stock boot indeed: I included the stock boot for C.47 in the Mega folder or direct link here.
Alternatively: revert to C.47 first? Files also in the Mega folder.
Click to expand...
Click to collapse
I tried with the stock boot already. Flashed it with fastboot, but didn't make any difference.
Do you know how I would go about reverting to C.47 without data loss? I have the ZIP file on my phone, but the updater says I cannot install it because the version is older than what I'm already running.
MrMagic said:
I tried with the stock boot already. Flashed it with fastboot, but didn't make any difference.
Do you know how I would go about reverting to C.47 without data loss? I have the ZIP file on my phone, but the updater says I cannot install it because the version is older than what I'm already running.
Click to expand...
Click to collapse
Only way is sadly with data loss/reset afaik.
xHalt said:
Please see the updated instructions above and let me know if it works for you.
Click to expand...
Click to collapse
working!!
thanks mate
HI all,
While attempting to update my Pixel 7 Pro (while retaining root, via the modified factory zip method where you root init_boot.img, then replace it in the factory zip, then run google's provided flash-all script) I've been encountering this issue when flash-all reached its last step of flashing the actual zip with the images via fastboot:
"fastboot: error: device requires partition vendor_kernel_boot which is not known to this version of fastboot"
This happens on both the new firmware as well as with the firmware I flashed through this method previously. New firmware after this causes a boot loop, while performing a flash of the old firmware results in the same error but at least gets me back into the system in the state it was in before attempting to upgrade.
Any idea why this is happening? I've ensured fastboot & adb are both up to date and attempted from both Windows and a Fedora laptop both to the same error. It's worth noting I installed the old (current) firmware previously through the same method successfully (before this) so not sure why it's decided to not work now....
Update: tried again via PixelFlasher and did not encounter the error so I guess if anyone else hits this issue and sees this post.... just use PixelFlasher(?????) No idea the why or how but seems to be good now.
Sounds like you were trying to flash in Fastboot mode rather than FastbootD.
Tomadock said:
Sounds like you were trying to flash in Fastboot mode rather than FastbootD.
Click to expand...
Click to collapse
Negative. I also thought that might be the issue and attempted it (the actual command it was running, not the entire script again since that would reboot to bootloader again) in FastbootD as well to the same result.
Sceleratis said:
HI all,
While attempting to update my Pixel 7 Pro (while retaining root, via the modified factory zip method where you root init_boot.img, then replace it in the factory zip, then run google's provided flash-all script) I've been encountering this issue when flash-all reached its last step of flashing the actual zip with the images via fastboot:
"fastboot: error: device requires partition vendor_kernel_boot which is not known to this version of fastboot"
This happens on both the new firmware as well as with the firmware I flashed through this method previously. New firmware after this causes a boot loop, while performing a flash of the old firmware results in the same error but at least gets me back into the system in the state it was in before attempting to upgrade.
Any idea why this is happening? I've ensured fastboot & adb are both up to date and attempted from both Windows and a Fedora laptop both to the same error. It's worth noting I installed the old (current) firmware previously through the same method successfully (before this) so not sure why it's decided to not work now....
Click to expand...
Click to collapse
i tried the latest version of "SDK Platform Tools"; it worked for me
Sceleratis said:
HI all,
While attempting to update my Pixel 7 Pro (while retaining root, via the modified factory zip method where you root init_boot.img, then replace it in the factory zip, then run google's provided flash-all script) I've been encountering this issue when flash-all reached its last step of flashing the actual zip with the images via fastboot:
"fastboot: error: device requires partition vendor_kernel_boot which is not known to this version of fastboot"
This happens on both the new firmware as well as with the firmware I flashed through this method previously. New firmware after this causes a boot loop, while performing a flash of the old firmware results in the same error but at least gets me back into the system in the state it was in before attempting to upgrade.
Any idea why this is happening? I've ensured fastboot & adb are both up to date and attempted from both Windows and a Fedora laptop both to the same error. It's worth noting I installed the old (current) firmware previously through the same method successfully (before this) so not sure why it's decided to not work now....
Click to expand...
Click to collapse
Literally error says everything....
You need latest platform tools that supports vendor _kernel_boot partition
Google added vendor kernel boot partition on P7 series that's been supported only on latest platform tools
Hi,
I've tried to flash a new magisk-boot img, following this guide, after downloading the signed flashable zip LE2113_11_F.75.
I've patched the boot.img with my magisk app, and after flashing it,my OnePlus 9 doesn't boot anymore.
I've got this error : QUALCOMM CrashDump Mode. dm-verity device corrupted. verity-ctr
I can't boot to TWRP, I tried a fastboot boot and a fastboot flash recovery, but I always get a Qualcomm dump error.
Can someone help me to fix this issue ?
Thanks !
this refrence might help-
Help needed! Qualcomm Crash dump after trying to reinstall magisk upon upgrade to Android 11
Hi, Lost root access after updating my OnePlus 6T to Android 11 a few days back, hence decided to flash magisk_patched image that I had created around 2 months back. Phone didn't like it ofcourse and gave me a QualComm Crash Dump error. After...
forum.xda-developers.com
"The update to [Insert Version Here] does not agree with Magisk which causes it to either fail to complete the update or to die at early boot depending on how bad things were messed up. You can reapply root once the update to [Insert Version Here] is finished though, so you can still have root.
In your case manually upgrading to [Insert Version Here], letting it finish the upgrade, and then installing Magisk again is your best bet, in which case you would either have to find something that understands the update format or manually extract the updated partitions from the payload, iirc"
Hi, thanks for your answer.
I've managed to gain access back to my phone, using the payload.bin from the signed flashable zip, and the fastboot enhance tool.
I've had to flash it on the a slot, as I have errors when trying to flash it on the b slot.
I've managed to boot on TWRP using this one for the encryption support.
I still got the dm-verify error when booting on the b slot, can't flash the payload.bin on it, can't backup it... I'm not sure if it's normal neither how to fix it, as even trying to fastboot flash boot crashes.
I've tried to flash the signed flashable zip in TWRP, and got this :
Flashing A/B zip to inactive slot : B
Step 1/2
Error applying update: 23 (ErrorCode:: kDownloadManifestParseError)
Updater process ended with ERROR: 1
Click to expand...
Click to collapse
AutruiP said:
Hi, thanks for your answer.
I've managed to gain access back to my phone, using the payload.bin from the signed flashable zip, and the fastboot enhance tool.
I've had to flash it on the a slot, as I have errors when trying to flash it on the b slot.
I've managed to boot on TWRP using this one for the encryption support.
I still got the dm-verify error when booting on the b slot, can't flash the payload.bin on it, can't backup it... I'm not sure if it's normal neither how to fix it, as even trying to fastboot flash boot crashes.
I've tried to flash the signed flashable zip in TWRP, and got this :
Click to expand...
Click to collapse
It's not a problem if one slot is broken, it will probably fix itself on the next update.
Hi, thanks for your answer.
The fact that you talked about the next update made me try to locally install the update with the signed flashable zip, using the system updater. It worked and fixed everything !
Thanks