I have tried multiple times to install TWRP and every time it seems to get overwritten by stock recovery. I've tried everything I can find online. After successfully flashing recovery.img and sending command "fastboot reboot recovery" or command "fastboot reboot 'recovery.img'" it flashes orange for a fraction of a second then vibrates a second time and shows boot logo screen with orange state warning, then either boots to stock recovery, or it boots to the home screen. One person said he was running into the same issue as I was and was only successful by deleting all the partitions on the device and reflashing it. He doesn't remember the steps he used and I would like to avoid even trying to do that anyway.
My only goal is to obtain root on my device, even if I'm using AOSP, as long as it's AOSP Android 10 v222, however I'm having issues trying to build a version of AOSP for this device without being able to find the binaries for it.
With all that being said, my question is if anyone who has the Blu Bold N1 running with the Android 10 update and working TWRP installed could please dump the rom and send it to me or upload it for me somewhere. There is no way I can dump the rom of my own device because I cannot get TWRP to successfully boot, and Blu does not host the Android 10 iso for this phone anywhere.
Alternatively, if someone could find the binaries for this device or knows how to find them, I could successfully build my image of AOSP and obtain root that way. I would rather be on the stock android that comes with the phone, but if I can't root it then I don't care to move to something else.
On an unrelated note, this is the first time I've ever posted on this forum and I apologize if anything I'm asking for or saying goes against the guidelines.
Hey, I pulled the Android 10 OTA. Can that b of help ?
greeneyez15o said:
Hey, I pulled the Android 10 OTA. Can that b of help ?
Click to expand...
Click to collapse
YESS! I've been using this phone without root for months now, you'd be a lifesaver if you could show me where I can download it.
greeneyez15o said:
Hey, I pulled the Android 10 OTA. Can that b of help ?
Click to expand...
Click to collapse
Sorry, I am the original poster of this thread, "emooverlord" I guess I signed in with my Facebook when I posted this and signed in with my email this time on accident.
emooverlord said:
Sorry, I am the original poster of this thread, "emooverlord" I guess I signed in with my Facebook when I posted this and signed in with my email this time on accident.
Click to expand...
Click to collapse
Ugh...sorry I don't have it anymore. I was annoyed I couldn't get it rooted.
greeneyez15o said:
Ugh...sorry I don't have it anymore. I was annoyed I couldn't get it rooted.
Click to expand...
Click to collapse
I can't seem to get TWRP on it at all, with the boot img or the rom would it not work with magisk?
The 3 files attached are:
boot.bin: The contents of the original 'boot' partition.
boot-stripped.bin: Patched with an empty vbmeta image, to allow custom ROM flashing and the like. Generated by:
Code:
cp boot.bin boot-stripped.bin
avbtool erase_footer --image boot-stripped.bin
avbtool append_vbmeta_image --image boot-stripped.bin --partition-size 33554432 --vbmeta_image /path/to/google-empty-vbmeta.img
boot-magisk.img: Pre-patched with Magisk 23 Canary (23016).
These are all from the November 2021 security patch of A10 on the Bold N1.
Also: you can extract everything off of the live device with https://github.com/bkerler/mtkclient:
Code:
python ./mtk rl <path to backup>
will give you a dump of all of the partitions on the device. (Since 'userdata' is encrypted and the last one, when it gets there, just hit ctrl-C when it gets there and you'll have everything out of the backup.)
irony_delerium said:
These are all from the November 2021 security patch of A10 on the Bold N1.
Click to expand...
Click to collapse
Any idea where I can get the Nov security patch? I'm stuck on Feb update.
GMSS75 said:
Any idea where I can get the Nov security patch? I'm stuck on Feb update.
Click to expand...
Click to collapse
Not off the top of my head. Mine updated to the November SP pretty quickly after turning it on the first time.
irony_delerium said:
Not off the top of my head. Mine updated to the November SP pretty quickly after turning it on the first time.
Click to expand...
Click to collapse
Ok thanks, I can't disable dm-verity, how do you patch vbmeta in the boot image?
GMSS75 said:
Ok thanks, I can't disable dm-verity, how do you patch vbmeta in the bootee image?
Click to expand...
Click to collapse
I used avbtool on the stock image. Check how I created boot-stripped.bin.
Related
Anybody had the November update yet. :laugh:
And anyone with unlocked bootloader have Pie october update ?
Keep the jokes coming
Almost got it, but it went too quickly.
For sure, I'll get it next time
I am getting 80 hours of screen on time. It's powered by nuclear reactor and it's a secret project of Juho Sarvikos.
k3dar7 said:
And anyone with unlocked bootloader have Pie october update ?
Click to expand...
Click to collapse
I have installed the Pie october update with a unlocked bootloader.
To get rid of the sideload error I have repacked the Pie september boot.img to change the 0001 into 00WW. I can't post link for the moment but if anyone is interested by the repacked boot.img pm me.
TomThePhysicist said:
I have installed the Pie october update with a unlocked bootloader.
To get rid of the sideload error I have repacked the Pie september boot.img to change the 0001 into 00WW. I can't post link for the moment but if anyone is interested by the repacked boot.img pm me.
Click to expand...
Click to collapse
Thanx for tip! I do repack myself, before i try find 0001 on */*prop* in booted system(and not found), not try find in boot.img(where this really is)
TomThePhysicist said:
I have installed the Pie october update with a unlocked bootloader.
To get rid of the sideload error I have repacked the Pie september boot.img to change the 0001 into 00WW. I can't post link for the moment but if anyone is interested by the repacked boot.img pm me.
Click to expand...
Click to collapse
i have repacked Pie september boot.img, in adb sideload is gone 0001 error, but still not finish, show "Error applying update: 20 (ErrorCode:: kDownloadStateInitializationError)"
first i try change 0001 to 00WW in default.prop and prop.default, second also in adbd and recovery binary...
repack using "Android_boot_image_editor"
k3dar7 said:
i have repacked Pie september boot.img, in adb sideload is gone 0001 error, but still not finish, show "Error applying update: 20 (ErrorCode:: kDownloadStateInitializationError)"
first i try change 0001 to 00WW in default.prop and prop.default, second also in adbd and recovery binary...
repack using "Android_boot_image_editor"
Click to expand...
Click to collapse
You need to have an unrooted system in order to make the update.
I think the error 20 is caused by a difference between the sha256 sum of your system and the expected one from the installer.
I have reinstalled the Pie september update prior to the october one and everything worked fine.
I have already got Android 9.1 with great new features:
1. Nokia camera has become better than Pixel 3, my friend wants my Nokia 7 Plus in exchange for his Pixel the new camera even features X-ray mode where you can see what's behind a wall, it uses Wifi and Radio signals to see what's behind a wall.
2. It works so flawlessly that even Fortnite is supported on this new build
3. Bootloader comes unlocked by default now, it's so open that now you will need to file a petition to close it.
TomThePhysicist said:
You need to have an unrooted system in order to make the update.
I think the error 20 is caused by a difference between the sha256 sum of your system and the expected one from the installer.
I have reinstalled the Pie september update prior to the october one and everything worked fine.
Click to expand...
Click to collapse
i know unrooted, i have complety uninstall magisk from magisk manager...
What you mean "reinstall" ? if i try sideload pie september then show same error, if try after change slot then show timestamp error
k3dar7 said:
i know unrooted, i have complety uninstall magisk from magisk manager...
What you mean "reinstall" ? if i try sideload pie september then show same error, if try after change slot then show timestamp error
Click to expand...
Click to collapse
If you have the september update installed on the active slot you will normally always get a timestamp error when trying to sideload it again.
To get rid of the timestamp error, simply flash an anterior boot image with fastboot (I have used a boot image from the last Pie public beta update).
To sum up:
Flash an anterior boot image (to the september Pie update) with fastboot and reboot to recovery (I always flash both slots).
Sideload the september Pie update and reboot to bootloader.
Flash a repacked September boot image with 0001 changed into 00WW in default.prop and prop.default (pm me if you need a working boot image) and reboot to recovery.
Sideload the october pie update and reboot to system.
TomThePhysicist said:
[...]To get rid of the timestamp error, simply flash an anterior boot image with fastboot (I have used a boot image from the last Pie public beta update)[...]
Click to expand...
Click to collapse
thanks, this do a trick, now i have Pie October installed
k3dar7 said:
thanks, this do a trick, now i have Pie October installed
Click to expand...
Click to collapse
So, if this is true then a thread which started out as a bit of a joke has actually been more useful that HMD support?
Having a Nokia phone really doesn't stop amazing me.
divvykev said:
So, if this is true then a thread which started out as a bit of a joke has actually been more useful that HMD support?
Having a Nokia phone really doesn't stop amazing me.
Click to expand...
Click to collapse
yes, is true
anyway, really thanks for your jokes thread i before some day from despair try contact HMD support... try tips as update without 4g enabled, update without sim inserted, update in safe mode, ended with tips wait for november update, maybe be full ota
k3dar7 said:
thanks, this do a trick, now i have Pie October installed
Click to expand...
Click to collapse
You're welcome, I'm glad I could help.
shailendra1993 said:
I have already got Android 9.1 with great new features:
1. Nokia camera has become better than Pixel 3, my friend wants my Nokia 7 Plus in exchange for his Pixel the new camera even features X-ray mode where you can see what's behind a wall, it uses Wifi and Radio signals to see what's behind a wall.
2. It works so flawlessly that even Fortnite is supported on this new build
3. Bootloader comes unlocked by default now, it's so open that now you will need to file a petition to close it.
Click to expand...
Click to collapse
Ha ha,this is funny,you made my day
https://developers.google.com/android/ota
I've update via adb.
Swiping via Soli seems much improved for me when using the music player.
What is the best way to do the OTA with Magisk root and custom kernel installed? It has been a very long time since I have rooted a phone and did any OTA.
ExcuseTheN00b said:
What is the best way to do the OTA with Magisk root and custom kernel installed? It has been a very long time since I have rooted a phone and did any OTA.
Click to expand...
Click to collapse
I followed the below steps. This is assuming you are already rooted on October patch level and want to maintain root.
1) Downloaded the factory images for the Nov update (https://developers.google.com/android/images) to the PC.
2) Extracted the zip file (make sure to extract the zip file inside the first one. That zip contains the .img file which we will need in step 4 ).
3) Edited the flash_all.bat file to remove '-w' parameter so that the data is not wiped.
4) Copied the 'boot.img' to the phone and used magisk manager to patch the boot file (https://topjohnwu.github.io/Magisk/install.html#boot-image-patching).
Copied the patched 'magisk_patched.img' from the phone to the PC.
NOTE: I also disabled all magisk modules before the next steps. This is just to ensure that custom module don't mess up the update (have seen this with the Oneplus 7 PRO android 10 update when i had that device)
5) Reboot phone into bootloder and connect to PC
6) Flashed the update by running the flash_all.bat file (make sure to remove the '-w' parameter before flashing so that DATA is not wiped). I did run into issue where the vendor.img failed at flashing but a change of USB cable fixed that (I have seen this issue before. some cables just don't work in fastboot/adb).
7) Once the flashing completes the phone reboots and does some update after booting up.
8) Again reboot into bootloader. Flash the boot with the 'magisk_patched.img' that was copied in step 4.
Code:
fastboot flash boot magisk_patched.img
I always flash it on both the a & b partitions by using below command.
Code:
fastboot flash boot_a magisk_patched.img
fastboot flash boot_b magisk_patched.img
9) Reboot the phone. At this point you have ROOT with Magisk and your custom kernel would be gone since stock/patched boot.img would have replaced it. You can re-flash your kernel (make sure the kernel has been updated for the November security update). Also at this point you can enable any modules that you may have disabled before the update.
I got november update now from ota..
Does anyone know why the Pixel 4 has 3 update files? Is there a specific version need for a specific carrier or something?
These are all Nov 2019 Factory/OTA update files for the Pixel 4.
QD1A.190821.007.A3
QD1A.190821.014
QD1A.190821.014.C2
---------- Post added at 09:23 AM ---------- Previous post was at 09:21 AM ----------
meek2100 said:
Does anyone know why the Pixel 4 has 3 update files? Is there a specific version need for a specific carrier or something?
These are all Nov 2019 Factory/OTA update files for the Pixel 4.
QD1A.190821.007.A3
QD1A.190821.014
QD1A.190821.014.C2
Click to expand...
Click to collapse
Actually I just found the answer here: https://support.google.com/pixelphone/thread/18553639?hl=en
Pixel 4 (XL):
US (ATT & Verizon): QD1A.190821.014.C2
US (TMobile, Sprint, Google Fi) & UK carriers: QD1A.190821.014
All other carriers (AU/JP/CA/TW/US): QD1A.190821.007.A3
ExcuseTheN00b said:
What is the best way to do the OTA with Magisk root and custom kernel installed? It has been a very long time since I have rooted a phone and did any OTA.
Click to expand...
Click to collapse
The post above (post #3) that says to use the factory image isn't wrong, but it isn't the easiest method either.
You can side-load the OTA image. You can do this on a phone with a locked or unlocked bootloader and you don't need to modify any files to prevent it from wiping the phone. It's just like the OTA update and will not wipe the phone.
You can find the files and directions directly from Google. https://developers.google.com/android/ota
Once the update is done, you will need to reroot the phone using the standard modified boot image method and then reflash your custom kernel (after making sure it has been updated to the latest OTA version). Just be aware that while the actual flashing time is much shorter than taking the OTA normally, it may have to optimize all of the apps during the initial boot. Unfortunately it doesn't give you any indication this is going on (unlike during a normal OTA update) and therefore people tend to get impatient and reboot during the initial boot. Don't do this. Just be patient and let the phone do it's thing. My phone took about 20 minutes to boot initially after side-loading the Nov update because I have a decent number of apps that it had to optimize.
Oops, nevermind. fixed
How do I get into bootloader mode? I can get into fastboot mode fine. But when I execute the command 'fastboot flashing unlock' the command prompt just shows waiting for device.
Spookymyo said:
How do I get into bootloader mode? I can get into fastboot mode fine. But when I execute the command 'fastboot flashing unlock' the command prompt just shows waiting for device.
Click to expand...
Click to collapse
Instructions here
https://developers.google.com/android/ota
Anyone experiencing "improved camera quality" that was listed in the change log? What are we looking for specifically?
xxaarraa said:
Anyone experiencing "improved camera quality" that was listed in the change log? What are we looking for specifically?
Click to expand...
Click to collapse
Pure speculation on my part, but I wonder if Google didn't tweak the auto-white balance due to the complaints about how the phone handled white balance in pictures with a predominantly red color.
Apparently Google killed the manual update your phone function again. At least on my pixel 4. Seemed to happen to me all the time on the pixel 3 too. Anyone else have the same issues?
Sent from my Pixel 4 using Tapatalk
BubbaGumprc said:
Apparently Google killed the manual update your phone function again. At least on my pixel 4. Seemed to happen to me all the time on the pixel 3 too. Anyone else have the same issues?
Click to expand...
Click to collapse
I had the same issue, the check update function did not work on my P4. It was working great on my P3.
Ugh! I got antsy and manually flashed the November factory image and now my face unlock is completely broken. I've tried rebooting, deleting face data + creating a new one in different lighting environments 5+ times now. No matter what I do the phone will not recognize my face anymore. It was working flawlessly on the October patch.
Now I'm afraid broken face unlock is one of the reasons Google delayed the role out of the November patch. Not a happy camper right now.
EDIT: I had to revert back to the October patch (full wipe) to get face unlock working again.
sn0warmy said:
Ugh! I got antsy and manually flashed the November factory image and now my face unlock is completely broken. I've tried rebooting, deleting face data + creating a new one in different lighting environments 5+ times now. No matter what I do the phone will not recognize my face anymore. It was working flawlessly on the October patch.
Now I'm afraid broken face unlock is one of the reasons Google delayed the role out of the November patch. Not a happy camper right now.
EDIT: I had to revert back to the October patch (full wipe) to get face unlock working again.
Click to expand...
Click to collapse
that's, odd, i updated to november, and my phone is spot on, I've yet to face an issue, or if i have i havent even noticed
sn0warmy said:
Ugh! I got antsy and manually flashed the November factory image and now my face unlock is completely broken. I've tried rebooting, deleting face data + creating a new one in different lighting environments 5+ times now. No matter what I do the phone will not recognize my face anymore. It was working flawlessly on the October patch.
Now I'm afraid broken face unlock is one of the reasons Google delayed the role out of the November patch. Not a happy camper right now.
EDIT: I had to revert back to the October patch (full wipe) to get face unlock working again.
Click to expand...
Click to collapse
Make sure you picked the correct image for your phone variant.
My phone came with build 007, installed a different one and it broke the face unlock. Installing back 007 restored it.
Im on November and face unlock works just fine
Does this undo the tweak to get Google pay to work with magisk? Or will we have to re do it?
ahsank128 said:
that's, odd, i updated to november, and my phone is spot on, I've yet to face an issue, or if i have i havent even noticed
Click to expand...
Click to collapse
hm... When I flashed the November image I did full wipe. Mybe this time I'll try without wipe and see if it retains proper face unlock from the October image.
thehartk said:
Make sure you picked the correct image for your phone variant.
My phone came with build 007, installed a different one and it broke the face unlock. Installing back 007 restored it.
Im on November and face unlock works just fine
Click to expand...
Click to collapse
Yeah, I was on 10.0.0 (QD1A.190821.007, Oct 2019) before clean flashing 10.0.0 (QD1A.190821.014, Nov 2019). I'm now back on 10.0.0 (QD1A.190821.007, Oct 2019) to get face unlock working again.
I wonder if I should be flashing 10.0.0 (QD1A.190821.007.A3, Nov 2019), instead? That ".A3" is giving me pause though.
Google really needs to label/identify these factory images better like they used to with (unlocked US) or (verizon) etc.. This is confusing.
sn0warmy said:
Google really needs to label/identify these factory images better like they used to with (unlocked US) or (verizon) etc.. This is confusing.
Click to expand...
Click to collapse
Look here: https://support.google.com/pixelphone/thread/18742521?hl=en
sn0warmy said:
hm... When I flashed the November image I did full wipe. Mybe this time I'll try without wipe and see if it retains proper face unlock from the October image.
Yeah, I was on 10.0.0 (QD1A.190821.007, Oct 2019) before clean flashing 10.0.0 (QD1A.190821.014, Nov 2019). I'm now back on 10.0.0 (QD1A.190821.007, Oct 2019) to get face unlock working again.
I wonder if I should be flashing 10.0.0 (QD1A.190821.007.A3, Nov 2019), instead? That ".A3" is giving me pause though.
Google really needs to label/identify these factory images better like they used to with (unlocked US) or (verizon) etc.. This is confusing.
Click to expand...
Click to collapse
Yes flash the .007.A3 if you were on the .007 before. I went through the same problems with the .014 too but .007.A3 fixed it.
Pixel 4 "FLAME" March 2020 QQ2A.200305.003 boot.img - Stock and Magisk v20.4 Patched
Hey all, I just updated my wife's P4 to Magisk 20.4 as of yesterday and have had no issues so far on the new version (nor on my P4XL). Here are the stock and recently newly updated Magisk patched (v20.4) boot images. I couldn't direct install the update on either of the phones via Magisk Manager, so I figured I would share these images.
Stock March 2020 boot image: https://www.androidfilehost.com/?fid=4349826312261757144
Magisk Patched (v20.4) March 2020 boot image: https://www.androidfilehost.com/?fid=4349826312261757143
Remember, these are ONLY for those on QQ2A.200305.003 firmware already. Don't flash if you don't know what you're doing.
Hey i5lee8bit,
Thanks for posting the p4 OTA boot files. worked perfectly. I have a p4xl as well. How do I extract the boot image from the device? I can not find the new boot image online from google or anything.
Which method did you use to flash? I've tried it a few different ways and they don't work. I'm thinking on factory resetting and trying again but I don't want to do if I don't have to. I've had no problem rooting my pixel 4 on any of the other updates but for some reason I can't root the March update. It looks like things flash fine but when the phone reboots it gets to a black screen and just stays there. I know it can take a while during app optimization so I let it set over night. Still on a black screen the next morning.
falawefulwaffle said:
Hey i5lee8bit,
Thanks for posting the p4 OTA boot files. worked perfectly. I have a p4xl as well. How do I extract the boot image from the device? I can not find the new boot image online from google or anything.
Click to expand...
Click to collapse
I'm not sure, I just grab them from the factory images (https://developers.google.com/android/images#coral). If it's not there, I wouldn't know. I came from years of HTC devices, but even then we either used TWRP or RUU decryption tool / firmware zips. Not sure if there's a way to extract directly from the device using dd or adb commands, but even then that was done using TWRP. Not sure if there's an alternate method; I'm not the right person to ask either, sorry. Tulsadiver's thread that I linked to for the other guy mentions a boot.img extractor, but I've never used it.
But if the boot file I provided worked perfectly for you, I would assume that means you are using the USA Unlocked model, and it should be available on the developers.google.com link I posted.
Spookymyo said:
Which method did you use to flash? I've tried it a few different ways and they don't work. I'm thinking on factory resetting and trying again but I don't want to do if I don't have to. I've had no problem rooting my pixel 4 on any of the other updates but for some reason I can't root the March update. It looks like things flash fine but when the phone reboots it gets to a black screen and just stays there. I know it can take a while during app optimization so I let it set over night. Still on a black screen the next morning.
Click to expand...
Click to collapse
From bootloader, just the simple fastboot flash boot name_of_boot_image.img
It sounds like you OTA'd to the March build? And you previously had it Magisk rooted on a prior firmware version? It could be a module not playing nice. Maybe try booting into Magisk Core mode, see Tulsadiver's thread: https://forum.xda-developers.com/pixel-4/how-to/magisk-modules-disabler-booting-magisk-t3991739
Sorry for the delayed responses btw. Quarantine + work + school + new baby = wtf.
i5lee8bit said:
I'm not sure, I just grab them from the factory images (https://developers.google.com/android/images#coral). If it's not there, I wouldn't know. I came from years of HTC devices, but even then we either used TWRP or RUU decryption tool / firmware zips. Not sure if there's a way to extract directly from the device using dd or adb commands, but even then that was done using TWRP. Not sure if there's an alternate method; I'm not the right person to ask either, sorry. Tulsadiver's thread that I linked to for the other guy mentions a boot.img extractor, but I've never used it.
But if the boot file I provided worked perfectly for you, I would assume that means you are using the USA Unlocked model, and it should be available on the developers.google.com link I posted.
From bootloader, just the simple fastboot flash boot name_of_boot_image.img
It sounds like you OTA'd to the March build? And you previously had it Magisk rooted on a prior firmware version? It could be a module not playing nice. Maybe try booting into Magisk Core mode, see Tulsadiver's thread: https://forum.xda-developers.com/pixel-4/how-to/magisk-modules-disabler-booting-magisk-t3991739
Sorry for the delayed responses btw. Quarantine + work + school + new baby = wtf.
Click to expand...
Click to collapse
Thanks for the reply. I ended up getting it to work using the "payload_dumper-win64" method i found in another thread to extract the boot.img from the payload.bin file. Turns out the OTA file was online from google.
To updatePixel 4 xl with "coral-ota-qq2a.200305.003-3b25765d" MAach update OTA software:
- uninstalled Magisk
-updated software
-reinstalled magisk
-patched the boot img from payload.bin
-pushed modified boot to device
-Done
Everything seems to be working well. I got to use python for the first time, so that was kind of fun. I was a flashing machine back around the galaxy s4.
I got root working. Spent so much time trying different things and all I had to do was factory reset my phone. There must have been some file or module interfering with the process. Once I reset my phone the root process went without error. ?*
May 2020 QQ2A.200501.001.B2 "FLAME" 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=4349826312261796525
Factory Untouched Boot Image: https://www.androidfilehost.com/?fid=4349826312261796524
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.
flame-qq2a.200405.005-factory-dtbo.img: https://www.androidfilehost.com/?fid=4349826312261796522
flame-qq2a.200405.005-factory-boot.img: https://www.androidfilehost.com/?fid=4349826312261763724
May 2020 sideload OTA zip: https://dl.google.com/dl/android/aosp/flame-ota-qq2a.200501.001.b2-46940f66.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 flame-qq2a.200405.005-factory-boot.img
3. fastboot flash dtbo flame-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 flame-ota-qq2a.200501.001.b2-46940f66.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 flame-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.
Thank you for making this so convenient!
ahalol said:
Thank you for making this so convenient!
Click to expand...
Click to collapse
:highfive:
You can thank my wife for going with the P4 instead of P4XL . Now gives me 2 phones to keep up with, although they're basically identical in process. Might as well share with yall over on this board, which seems to get a little less love and attention. But we're definitely lovin the switch to Pixels. Awesome camera too, which is great because we just had our first child 4 months ago and these phones take amazing photos. And this is coming from 2 phones that already had great cameras (HTC U11 and U12+)! I love taking photos when he's sleeping using Night Sight mode. He's so adorable, it comes out so clean, and there's just something about that sleepy ambience .
i just saw on my google news feed that the May patch just started dropping to our devices. i go check XDA and this post is already here. wow that was fast haha! went perfectly smoothly just like last month, thanks so much!!
Why not update the OTA via Magisk, or is this only for those which devices is not able to download OTA:s?
Currently, I have rooted with Magisk, still waiting for OTA update notification in my device...
Should i restore images in Magisk and/or disable any modules or just let 'er rip?!
Vantskruv said:
Why not update the OTA via Magisk, or is this only for those which devices is not able to download OTA:s?
Currently, I have rooted with Magisk, still waiting for OTA update notification in my device...
Click to expand...
Click to collapse
redeyss said:
Should i restore images in Magisk and/or disable any modules or just let 'er rip?!
Click to expand...
Click to collapse
@Vantskruv: FYI, you won't get the OTA update notification because you're modified right now. You can restore the boot image in Magisk first and wait for the OTA notification (what you're thinking of is something like this: https://forum.xda-developers.com/pixel-4-xl/how-to/guide-update-retain-root-t4003839). But from what I understand, it's pretty hit or miss. Apparently it's hit or miss even on complete bone stock anyway lol. The method I outlined just works nice and reliably even when rooted and modded.
@redeyss: Restoring the stock boot image in Magisk Manager is similar to the method linked above, and then taking the OTA the normal way. But if you flashed a custom kernel, keep it mind it won't restore the dtbo partition (not sure if it's necessary with that method tbh). You shouldn't need to restore images in Magisk, nor diable any modules. When you flash the factory April boot and dtbo images, it's doing the same thing as restoring the images through Magisk (plus dtbo). Just let er rip, and if you have any issues, you can always flash the new unmodified factory boot image, which will essentially disable Magisk, and then work from there. It's a very safe method. =)
edit: also in the event of bootloop, this is a great thread to read and understand: https://forum.xda-developers.com/pixel-4/how-to/magisk-modules-disabler-booting-magisk-t3991739
Thank you @i5lee8bit for your answer. Luckily I have restrained myself yesterday to update, thought I where in the Pixel 4XL thread, while this is for the Pixel 4. :laugh:
I am just curious, do any of you expert guys/girls know why this is happening, that OTA updates is not pushed on rooted phones?
Do Google have algorithms that temporarily bans systems which is rooted?
Or is it so simple that some type of fingerprint is changed when rooted, so Google update services does not recognise the device, and not pushing OTA:s?
Sorry for the questions, no need to answer them. It was a long time ago I rooted Android:s, and I have forgot many things.
I think I will try to manually update everything, even though there are more steps included, just to learn how to do it.
https://www.youtube.com/watch?v=kZY8qiz2SZ0
Vantskruv said:
Thank you @i5lee8bit for your answer. Luckily I have restrained myself yesterday to update, thought I where in the Pixel 4XL thread, while this is for the Pixel 4. :laugh:
I am just curious, do any of you expert guys/girls know why this is happening, that OTA updates is not pushed on rooted phones?
Do Google have algorithms that temporarily bans systems which is rooted?
Or is it so simple that some type of fingerprint is changed when rooted, so Google update services does not recognise the device, and not pushing OTA:s?
Sorry for the questions, no need to answer them. It was a long time ago I rooted Android:s, and I have forgot many things.
I think I will try to manually update everything, even though there are more steps included, just to learn how to do it.
https://www.youtube.com/watch?v=kZY8qiz2SZ0
Click to expand...
Click to collapse
No worries, the process for the 4XL is the exact same, but good catch; you definitely need to use the correct files for the device. I actually posted a similar thread with the relevant 4XL files over on that forum.
Not sure exactly the mechanism used to prevent the normal OTA, but probably just checks for a modified boot partition. In any case, the normal factory OTA if I understand correctly relies in part on factory recovery commands at some point, and a modified boot partition won't be able to use them. In fact, try booting to recovery with the modified boot partition flashed and you'll notice it can't load recovery. I may be wrong about the exact reason though. But think about it: even if we had TWRP, the factory OTA mechanism can't make use of it. Even if the OTA popped up while rooted, it probably wouldn't be able to do it, or worse, cause a failure and corruption. I would dare say we're fortunate they prevent factory OTA when running modified.
Anyway, there are a lot of complicated guides out there, and that's why I wanted to share my method. I didn't need to do any further research and it's very intuitively sound. Steps 2+3 essentially restore stock boot and therefore recovery (and dtbo), the rest pretty much follows a standard OTA sideload, and then it's structured in such a way that you're flashing the new Magisk patched boot image before even starting the phone back up. Making it a seamless, keep-root easy upgrade.
Wow ..... what an easy, elegant way to get my Coral device updated while keeping root. Followed the OP process, but used these commands instead to get the June 2020 security update:
- fastboot flash boot coral-qq3a.200605.001-factory-boot.img
- fastboot flash dtbo coral-qq3a.200605.001-factory-dtbo.img
- adb sideload coral-ota-qq3a.200605.001-3b5bb1bd.zip
- fastboot flash boot coral-qq3a.200605.001-magisk_patched-20.4.img
Thanks, @i5lee8bit . Well done. :good:
does anyone have a thread to point me to that is a step by step guide for setting up ADB and how to flash? I did everything a year ago but now I just factory reset and am stuck in boot loop, can't remember all the commands and everything.
in_dmand said:
does anyone have a thread to point me to that is a step by step guide for setting up ADB and how to flash? I did everything a year ago but now I just factory reset and am stuck in boot loop, can't remember all the commands and everything.
Click to expand...
Click to collapse
Did you fix the issue?
Hi, I have decided to gather boot images and magisk patched images to one thread for now. I will try to edit this thread to be up-to-date. You can let me know what could you want next or if anything is wrong etc.
Stock boot.img files (direct links):
EU NE2213_11_A.12
Stock boot.img - link
EU NE2213_11_A.10
Stock boot.img - link
Magisk patched boot.img are here a file that can be downloaded (I am using magisk canary usually, but in Magisk, you can change the channel from the canary to stable etc.) - names as the versions come.
Below this there are those magisk patched files which you just flash (or boot and then flash directly from the Magisk app) via fastboot
Reserved
Don't you need to patch vendor_boot.img as well like OnePlus 9 pro ?
HessNL said:
Don't you need to patch vendor_boot.img as well like OnePlus 9 pro ?
Click to expand...
Click to collapse
Apparently not. I have patched that stock boot via magisk, then via fastboot boot <patchedimage.img> booted (and also tested if it actually boots) and when it booted, via magisk app I did "Direct install (recommended)", rebooted and done.
Oh okay you had a temporary boot we that's good to know well it works that's the most important thing ain't it
Noob question I been on locked bootloader for years so haven't been in the root scene, but I have US model NE2215 I'm guessing I need to wait for the firmware to be available to get the boot img? Did I just got my phone too early? Already oem unlocked now just waiting for twrp and root info. I always wanted a OnePlus phone because the community is big, but doesn't seem like much people upgraded from 9 pro.
HessNL said:
Oh okay you had a temporary boot we that's good to know well it works that's the most important thing ain't it
Click to expand...
Click to collapse
Yes, because this is probably and currently the most secure option to root it as we haven't got twrp available yet.
BuBbLeFIZzY said:
Noob question I been on locked bootloader for years so haven't been in the root scene, but I have US model NE2215 I'm guessing I need to wait for the firmware to be available to get the boot img? Did I just got my phone too early? Already oem unlocked now just waiting for twrp and root info. I always wanted a OnePlus phone because the community is big, but doesn't seem like much people upgraded from 9 pro.
Click to expand...
Click to collapse
That's not that you have it early. The phone itself is early in spite of rooting and doing things like rooting, custom recoveries, ROMs etc. I currently can't find boot img for your model, but once I do, I will post it here for you with patched one.
Thank you kouzelnik3 for this thread !
I was going to dl original firmware and patch it myself but found your thread in time with all ready to flash
Rooted OP10 pro done, now i can't wait to see some TWRP and roms in the future
fozzy056 said:
Thank you kouzelnik3 for this thread !
I was going to dl original firmware and patch it myself but found your thread in time with all ready to flash
Rooted OP10 pro done, now i can't wait to see some TWRP and roms in the future
Click to expand...
Click to collapse
You're really welcome, I wanted to unite those currently quite hard rooting stuff!
And yes, I can't wait to see twrp too!
Is there a known stock boot.img of the NE2215_11_A.10? I assume I shouldn't use the 2213_11_A.10.
GeekMcLeod said:
Is there a known stock boot.img of the NE2215_11_A.10? I assume I shouldn't use the 2213_11_A.10.
Click to expand...
Click to collapse
Not yet unfortunately. Or I don't know about it yet. :/
kouzelnik3 said:
Not yet unfortunately. Or I don't know about it yet. :/
Click to expand...
Click to collapse
Yeah.. I googled a lot last night once I got my phone trying to find it to root it. I need me that extra bit of customization.
Is there a way I can get it from my phone?
what am i doing wrong here rooted for 7+ years and some reason can't get this working.
Just moved over from ColorOS to Oxygen - when i try to flash the boot.img (patched one) all i get is this
Johnstan725 said:
what am i doing wrong here rooted for 7+ years and some reason can't get this working.
Just moved over from ColorOS to Oxygen - when i try to flash the boot.img (patched one) all i get is this
Click to expand...
Click to collapse
Ignore me but for anyone else that tries looks like i had to reboot bootloader and flash the img via bootloader...
thought it's normally flashed via fastboot?! weird phone
Johnstan725 said:
Ignore me but for anyone else that tries looks like i had to reboot bootloader and flash the img via bootloader...
thought it's normally flashed via fastboot?! weird phone
Click to expand...
Click to collapse
You should wipe the phone and start all over or else you won't be able to take ota updates. Never flash the patched boot image since you bypass the magisk backup feature. You have to wait for the full update package to update if you flash the boot. Ppl have previously had update issues after flashing.
g96818 said:
You should wipe the phone and start all over or else you won't be able to take ota updates. Never flash the patched boot image since you bypass the magisk backup feature. You have to wait for the full update package to update if you flash the boot. Ppl have previously had update issues after flashing.
Click to expand...
Click to collapse
Wiped the phone already, what difference would it make if i remove root or flash stock boot then flash ota and reflash boot?
Johnstan725 said:
Wiped the phone already, what difference would it make if i remove root or flash stock boot then flash ota and reflash boot?
Click to expand...
Click to collapse
Not sure what else magisk does during the backup process, but doing what you’re describing didn’t work for users on 8T and they usually ended up soft bricking. Everyone who flashed it vice installing from magisk app had to wait for op to post the full rom or for someone to post a repacked fastboot rom to update.
You do what you need to do, I’m just giving you some experience and recommendations since you just wiped and flashed the boot.
g96818 said:
Not sure what else magisk does during the backup process, but doing what you’re describing didn’t work for users on 8T and they usually ended up soft bricking. Everyone who flashed it vice installing from magisk app had to wait for op to post the full rom or for someone to post a repacked fastboot rom to update.
You do what you need to do, I’m just giving you some experience and recommendations since you just wiped and flashed the boot.
Click to expand...
Click to collapse
Interesting.
I moved over from ColorOS to oxygen OS, wiped the device then just booted a patched boot img, and installed direct.
I assume I flash ota and go onto magisk and do inactive slot? Where does the issue lie what method should I have gone down?
Johnstan725 said:
Interesting.
I moved over from ColorOS to oxygen OS, wiped the device then just booted a patched boot img, and installed direct.
I assume I flash ota and go onto magisk and do inactive slot? Where does the issue lie what method should I have gone down?
Click to expand...
Click to collapse
Hmmm. Well you should be fine if you patched the boot and let magisk do the install. I only suggested wiping since you said you flashed the img from the bootloader.
You might run into the same problem I have with the 9RT. I too upgraded from color to oos and couldn’t update at all, even though I rooted from the magisk app. I had to wait for someone to make a fastboot rom. I had no problems updating color following my method, but not oos after switching. Hopefully that’s not the case for you.