Trouble installing Magisk on the November Android update - Google Pixel 5 Questions & Answers

Reposting here (from the Magisk forum) on the advice of a Senior Moderator.
I have a Pixel 5 and two days ago now I updated from redfin-2110-rq3a.211001.001-factory-23f4cec2 to redfin-2111-sp1a.211105.004-factory-749e8f9f (yes the Aus version), i.e. from the October version to the November version.
All went well until I tried to root the device using Magisk - something I've done *many* times. The trouble is that after I flashed the patched boot.img, the device would not boot - it started to for a few seconds and then went back into fastboot mode.
I've tried a few times but always the same result.
And it seems that you cannot rollback to the October release - the flash-all.sh completes OK but the subsequent boot hangs.
BTW (1): I'm still using the canary channel, is this still necessary?
BTW (2): I also posted in the github Magisk issues page and that issue was promptly closed with the comment "format data". Really?!
Help.

Curiouser and curiouser: this works
adb reboot bootloader
fastboot boot redfin-2111_boot_magisk_patched.img

gone_bush said:
Reposting here (from the Magisk forum) on the advice of a Senior Moderator.
I have a Pixel 5 and two days ago now I updated from redfin-2110-rq3a.211001.001-factory-23f4cec2 to redfin-2111-sp1a.211105.004-factory-749e8f9f (yes the Aus version), i.e. from the October version to the November version.
All went well until I tried to root the device using Magisk - something I've done *many* times. The trouble is that after I flashed the patched boot.img, the device would not boot - it started to for a few seconds and then went back into fastboot mode.
I've tried a few times but always the same result.
And it seems that you cannot rollback to the October release - the flash-all.sh completes OK but the subsequent boot hangs.
BTW (1): I'm still using the canary channel, is this still necessary?
BTW (2): I also posted in the github Magisk issues page and that issue was promptly closed with the comment "format data". Really?!
Help.
Click to expand...
Click to collapse
Sorry, but you are going to have to wipe your phone here. On the next updates you won't have to following these instructions.
Get the vbmeta.img from the factory image (the same place you got the boot.img) and put it into your fastboot folder.
In bootloader/fastboot enter:
fastboot flash --disable-verity --disable-verification vbmeta vbmeta.img
Then enter:
fastboot -w (<---this wipes your phone)
Then flash the patched boot image as you normally would and reboot.
In the future for updates, download both the ota.zip and the factory image. Pull the boot.img from the factory image and patch it. Pull the vbmeta.img and put it into your fastboot folder with the patched boot.img. Sideload the OTA and when the flash is done, boot to bootloader using the volume/power buttons on your phone from recovery (you'll be there to sideload the ota.zip) IF YOU BOOT TO /SYSTEM YOU'LL HAVE TO WIPE AGAIN!
Flash the vbmeta.img with fastboot flash --disable-verity --disable-verification vbmeta vbmeta.img, then flash the patched boot.img and reboot. You won't have to wipe again as long as you don't boot to /system and don't forget to flash the vbmeta.img with disabling verity and verification.

xunholyx said:
Sorry, but you are going to have to wipe your phone here. On the next updates you won't have to following these instructions.
Get the vbmeta.img from the factory image (the same place you got the boot.img) and put it into your fastboot folder.
In bootloader/fastboot enter:
fastboot flash --disable-verity --disable-verification vbmeta vbmeta.img
Then enter:
fastboot -w (<---this wipes your phone)
Then flash the patched boot image as you normally would and reboot.
In the future for updates, download both the ota.zip and the factory image. Pull the boot.img from the factory image and patch it. Pull the vbmeta.img and put it into your fastboot folder with the patched boot.img. Sideload the OTA and when the flash is done, boot to bootloader using the volume/power buttons on your phone from recovery (you'll be there to sideload the ota.zip) IF YOU BOOT TO /SYSTEM YOU'LL HAVE TO WIPE AGAIN!
Flash the vbmeta.img with fastboot flash --disable-verity --disable-verification vbmeta vbmeta.img, then flash the patched boot.img and reboot. You won't have to wipe again as long as you don't boot to /system and don't forget to flash the vbmeta.img with disabling verity and verification.
Click to expand...
Click to collapse
Thank you for your reply. Some questions:
1) What's changed that required a wipe? (Let's face it, it's a MAJOR PITA! Thankfully, I do use TitaniumBackup )
2) You state "download both the ota.zip and the factory image" - what's the difference?
3) Re "Pull the vbmeta.img" - in the current instance, is that from the November file (SP1A.211105.004), if not, from where?
4) Do I have this right for future updates?
* Unpack the downloaded file and put the boot.img and vbmeta.img files in a safe place
* Sideload the update by
adb reboot recovery
Apply update from ADB
adb sideload <ota-update.zip>
* Use volume buttons to boot into bootloader (booting into system will mean I'll have to do another wipe!)
* fastboot flash --disable-verity --disable-verification vbmeta vbmeta.img
* flash patched boot.img
* boot
5) Re using Magisk to patch the boot.img: can, say, the November boot.img be patched whilst the phone is running the October update?
Yeah, I know, answering my questions is all you've got to do with your life

1: verified boot is needed in Android 12. Patching the boot.img breaks the signature from Google
2: after flashing the factory image in fastboot you're promoted to press any key to continue, which boots the phone to system iirc (I could be mistaken ~ it's been over a year since I flashed a factory image). You can boot to bootloader from recovery after you sideload the OTA.
3: yes. From the update you are applying.
4: I guess.... Place the vbmeta.img in your fastboot folder the same as the patched boot.img (at least that's where I always put the patched boot.img). Put the pulled boot.img wherever you like to transfer it to your phone from to patch. The rest after that part is correct.
5: yes
EDIT: (Sorry I forgot to use the reply button)

xunholyx said:
1: verified boot is needed in Android 12. Patching the boot.img breaks the signature from Google
2: after flashing the factory image in fastboot you're promoted to press any key to continue, which boots the phone to system iirc (I could be mistaken ~ it's been over a year since I flashed a factory image). You can boot to bootloader from recovery after you sideload the OTA.
3: yes. From the update you are applying.
4: I guess.... Place the vbmeta.img in your fastboot folder the same as the patched boot.img (at least that's where I always put the patched boot.img). Put the pulled boot.img wherever you like to transfer it to your phone from to patch. The rest after that part is correct.
5: yes
EDIT: (Sorry I forgot to use the reply button)
Click to expand...
Click to collapse
Thank you for yor replies and time - much appreciated!

Related

My nexus will not flash correctly

Hello guys, ive been generally lucky in the sense that i have had no issues...until now.
I have tried installing the most recent updates (7.0, and now 7.1.1) and i continue to get this error through cmd. It does not seem to want to flash anything, and i have gotten it to flash, root, and twrp, but it still acted funky. Today, trying to remedy the situation, i attempted to flash the new 7.1.1 update, and return to stock (to later return to power user) but it is still doing it.
It says Bootloader: has-slot (not found), and a couple other things. When i try to flash individual pieces, it does not retain it. when i try to flash the flashall.bat, it flashes but does not flash everything, it will say the stuff has transferred 0 and skips it as it looks like. I cannot get my bootloader off the october one, and i have looked everywhere i can to try to fix this.. please help, its driving me mad. I will be happy to provide any information needed.
Thanks Community! You rock!
Have you tried a different USB cable? A different computer? How about a different USB AND a different computer? I think this would be a good place to start.
Can i ask you why this would matter? My usb seems to work fine, and my computer had no issues before this... i can still perform different actions, and my phone is showing up as ADB and Fastboot.
If it's not pc or usb cable related you can try to flash latest factory image step by step via fastboot without your simcard
Well, you might want to post the complete output of your flashing attempt, but if the bootloader slot isn't found, that's usually a sign of a hardware problem. Hopefully I'm wrong, but until we see more from you, I simply don't have an answer for you.
Ive tried to fastboot everything individually, and it refuses to take. I tried the flashall, same thing. I used NRT and it partially worked, but has sorta the same error. I will be flashing again and providing screenshots right now. I was able to get into a rom, root, twrp but i still cannot update all of those core things (bootloader, radio, and such) Thank you guys for the help. Much needed.
Here is the attempt to just flash the bootloader, i have tried from a different location but this is directly in Platform-Tools of the SDK. As you can also see, it does register under fastboot...
Try to flash radio and bootloader via twrp
https://forum.xda-developers.com/ne...-nexus-6-recovery-flashable-fastboot-t3066052
Did you try without simcard?
coremania said:
Try to flash radio and bootloader via twrp
https://forum.xda-developers.com/ne...-nexus-6-recovery-flashable-fastboot-t3066052
Did you try without simcard?
Click to expand...
Click to collapse
yes i have, i only do it with the simcard removed. Now whats weird is it says my bootloader is on 72.01, but my cmd clearly tells me its not working correctly...
coremania said:
Try to flash radio and bootloader via twrp
https://forum.xda-developers.com/ne...-nexus-6-recovery-flashable-fastboot-t3066052
Did you try without simcard?
Click to expand...
Click to collapse
I just tried what you suggest, and im not sure if it worked. It said everything wrote (on twrp) but it was very quickly done. I feel it did the same thing as CMD did.
You could try using the correct Fastboot command...
fastboot flash bootloader bootloader.img
The command is fastboot flash <partition> <image>
Your screenshot says only "fastboot flash image" but doesn't state the partition you're trying to load, hence "unknown partition".
And since we're on the subject, perhaps a repetition of the procedure I used to use before the full OTA days might be useful to you and other people.
Preparation.
- Take a TWRP backup and save it on your PC.
- Download factory image (https://developers.google.com/android/nexus/images#shamu) and unzip all files, including the zip within the zip. Rename the *.img files to the names below. Copy all of them to the same folder as your ADB/fastboot executables.
- Download the relevant TWRP and rename to twrp.img - also put in ADB/fastboot folder.
- Copy SuperSU to device (if root wanted).
- Set USB debugging in Developer options & attach to your PC.
- Open a CMD window, navigate to your ADB folder, and check connectivity with "adb devices". If it's ok, copy & paste each command below into the CMD window and run them - the only lengthy one is the system.img.
1. adb reboot bootloader
2. fastboot flash bootloader bootloader.img
3. fastboot reboot-bootloader
4. fastboot flash radio radio.img
5. fastboot reboot-bootloader
6. fastboot erase system
7. fastboot flash system system.img
8. fastboot erase boot
9. fastboot flash boot boot.img
10. fastboot erase cache
11. fastboot flash cache cache.img
12. fastboot reboot-bootloader
13. fastboot flash recovery twrp.img
14. From bootloader boot to TWRP and reflash superSu
dahawthorne said:
You could try using the correct Fastboot command...
fastboot flash bootloader bootloader.img
The command is fastboot flash <partition> <image>
Your screenshot says only "fastboot flash image" but doesn't state the partition you're trying to load, hence "unknown partition".
And since we're on the subject, perhaps a repetition of the procedure I used to use before the full OTA days might be useful to you and other people.
Preparation.
- Take a TWRP backup and save it on your PC.
- Download factory image (https://developers.google.com/android/nexus/images#shamu) and unzip all files, including the zip within the zip. Rename the *.img files to the names below. Copy all of them to the same folder as your ADB/fastboot executables.
- Download the relevant TWRP and rename to twrp.img - also put in ADB/fastboot folder.
- Copy SuperSU to device (if root wanted).
- Set USB debugging in Developer options & attach to your PC.
- Open a CMD window, navigate to your ADB folder, and check connectivity with "adb devices". If it's ok, copy & paste each command below into the CMD window and run them - the only lengthy one is the system.img.
1. adb reboot bootloader
2. fastboot flash bootloader bootloader.img
3. fastboot reboot-bootloader
4. fastboot flash radio radio.img
5. fastboot reboot-bootloader
6. fastboot erase system
7. fastboot flash system system.img
8. fastboot erase boot
9. fastboot flash boot boot.img
10. fastboot erase cache
11. fastboot flash cache cache.img
12. fastboot reboot-bootloader
13. fastboot flash recovery twrp.img
14. From bootloader boot to TWRP and reflash superSu
Click to expand...
Click to collapse
hahahaha well that could surely be the issue :silly:, but the one thing im wondering is why it wouldnt work through NRT, and i also "successfully" sideloaded the ota... Gonna try this now and hopefully it works! I shall report back when finished
dahawthorne said:
You could try using the correct Fastboot command...
fastboot flash bootloader bootloader.img
The command is fastboot flash <partition> <image>
Your screenshot says only "fastboot flash image" but doesn't state the partition you're trying to load, hence "unknown partition".
And since we're on the subject, perhaps a repetition of the procedure I used to use before the full OTA days might be useful to you and other people.
Preparation.
- Take a TWRP backup and save it on your PC.
- Download factory image (https://developers.google.com/android/nexus/images#shamu) and unzip all files, including the zip within the zip. Rename the *.img files to the names below. Copy all of them to the same folder as your ADB/fastboot executables.
- Download the relevant TWRP and rename to twrp.img - also put in ADB/fastboot folder.
- Copy SuperSU to device (if root wanted).
- Set USB debugging in Developer options & attach to your PC.
- Open a CMD window, navigate to your ADB folder, and check connectivity with "adb devices". If it's ok, copy & paste each command below into the CMD window and run them - the only lengthy one is the system.img.
1. adb reboot bootloader
2. fastboot flash bootloader bootloader.img
3. fastboot reboot-bootloader
4. fastboot flash radio radio.img
5. fastboot reboot-bootloader
6. fastboot erase system
7. fastboot flash system system.img
8. fastboot erase boot
9. fastboot flash boot boot.img
10. fastboot erase cache
11. fastboot flash cache cache.img
12. fastboot reboot-bootloader
13. fastboot flash recovery twrp.img
14. From bootloader boot to TWRP and reflash superSu
Click to expand...
Click to collapse
Unfortunately, it did not work. Now google app keeps crashing. Phone is extremely buggy.
Calko2882 said:
Unfortunately, it did not work. Now google app keeps crashing. Phone is extremely buggy.
Click to expand...
Click to collapse
Can you give a bit more detail? So the phone is crashing, but is it now on the version that you wanted to have (7.0, 7.1.1)? There is rarely such a thing as "too much information".
dahawthorne said:
Can you give a bit more detail? So the phone is crashing, but is it now on the version that you wanted to have (7.0, 7.1.1)? There is rarely such a thing as "too much information".
Click to expand...
Click to collapse
Ok, so what happens is that it says i am on 7.1.1 with i guess the related info, but it does not load in properly as you can see with the screenshots. I start up the initial setup, and i can get through most of it fine, but some areas *permissions* are all blotchy. like i can toggle them on to submit data but i cant see what it is exactly im agreeing to. Then i start the phone, Google App automatically crashes, along side system ui. When i updated them, it seemed to fix the problem. But the issue is, i am not receiving phone calls and texts until possibly days later, and when i send texts it says "sending" and proceeds to spam the hell outta whoever its going to (sends literally 30+ texts). When i call someone, my phones Do Not Disturb mode gets enabled, and then nicely cuts out my audio. I can turn this feature off when im in the call, but sometimes it will then glitch the phone app, and i cannot essentially "hangup". My phone also now dies at 9%, where it had not previously (when i was on other rom / older stock) This all started after i updated to the october patch, and i noticed in december that i didnt have the december patch / update. I went to install it, and the same exact thing occurred. Ive attempted a rescue ota, and a sideload ota, and now this stuff as well, but i fear the worst for my phone. Let me know if i need to add anything else
Strephon may be right in suggesting a hardware fault, but equally it may just be that your phone is now somehow corrupted. My only suggestion is that you nuke it - factory reset, TWRP, wipe everything again in TWRP, and then try installing from fresh using the 7.1.1 full (not OTA) image and the instructions I posted earlier. If it still doesn't work I'm out of ideas, but there are people with far greater experience here than I have, so don't give up. It's too nice a device to just write off.
Calko2882 said:
When i call someone, my phones Do Not Disturb mode gets enabled
Click to expand...
Click to collapse
That's a new feature of 7.1.1. So you won't have to listen to notifications while on the phone. It's disabled as soon as the phone call is over.
dahawthorne said:
Strephon may be right in suggesting a hardware fault...
Click to expand...
Click to collapse
I hope I'm wrong.

[GUIDE][GSI] Flashing GSI's with TWRP Fixes and Workarounds

Follow these easy steps
Makes sure you have the GSI image on your sdcard before starting this, if your coming from lineage OS backup your data!
1.Unlock Bootloader
2. Boot into bootloader, check your slot if on B switch to A and vice versa.(fastboot set_active a/b) or you can stay in your current active slot up to you.
3.Download twrp and flash it (fastboot flash boot boot.img)
4.Boot back into boot loader and run "fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img" link with b11 vbeta.img
5.Boot into twrp,Format data or in bootloader run this command "fastboot format userdata" to get rid if encryption else gsi wont boot then, go to "install" navigate to your sdcard where you place the gsi , look for 'select image" then flash your gsi.
6.To flash gapps(skip if the gsi includes them) if your using a aosp gsi go to twrp then go into /wipe/advanced wipe/ select system on the options then "repair or change file system" then press on "resize file system" this will resize your system partiton back to 3.X gigs and allow you to flash gapps.
7.Then reboot to system
8. Your gsi "should" boot
Downloads:
http://www.mediafire.com/folder/ha8j5crsdmbmx/ZTE_Axon_10_pro_stuff
https://forum.xda-developers.com/pr...bled-device-development/gsi-havoc-os-t3930030 Havoc OS the gsi ive been using for some weeks.
Fixes and WorkArounds
Volte Fix for GSi
Install the volt-ims.apk as you would normally install an apk, download here http://www.mediafire.com/file/l0x88jx5zxyknhh/volte-ims.apk/file
For root( magisk) and twrp flash http://www.mediafire.com/file/de8tccz7gr93831/twrp-magisked-los-boot.img/file
To pass SafetyNet flash this http://www.mediafire.com/file/867xncq865vvtct/Universal-safetynet-fix-v3.zip/file
Also I created a template for what works on phhusson Treble experiments wiki:
https://github.com/phhusson/treble_experimentations/wiki/ZTE-Axon-10-Pro
CREDITS:
Unjustifieddev for his work on lineage, and the boot.img im using.
All the gsi creators
Screenshots of Havoc OS gsi running on my zte axon 10:
Android Q Gsi works too
you can also use the zte android 9 stock kernel and vendor
That all is great news.....bravooo
Any issues with the havoc gsi?
blcistheking said:
Any issues with the havoc gsi?
Click to expand...
Click to collapse
Only the Fingerprint is broken
noobstyle1337 said:
Only the Fingerprint is broken
Click to expand...
Click to collapse
its only broken if you have a a2020g, works fine if you have a a2020u, current los kernel is missing a2020g fingerprint firmware from what i can gather.
Bliss 12.7 Android 10 gsi on a2020u.
rafyvitto said:
Follow these easy steps
4.Boot back into boot loader and run "fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img" link with b11 vbeta.img
==
Click to expand...
Click to collapse
whenever i try this i just get
"fastboot: unknown option -- disable-verity"
Mr. DR. Professor Electro said:
whenever i try this i just get
"fastboot: unknown option -- disable-verity"
Click to expand...
Click to collapse
Skip that step not needed, just flahs the disable encryption zip file in twrp to disable encryption.
i have bootloader unlocked ive wiped everything even flashed disable encryption but whenever i try to install the zip for lineage 17 i get an "error installing zip file' am i doing something wrong?
honestly i cant even flash any rom zip i have i just get error 1s , i even wipe data/format before flashing am i doing something wrong am i supposed to be on a or b while doing this or what
Futility's Forgotten Soldier said:
i have bootloader unlocked ive wiped everything even flashed disable encryption but whenever i try to install the zip for lineage 17 i get an "error installing zip file' am i doing something wrong?
Click to expand...
Click to collapse
Lineage 17 is very broken right now, i would suggest flashing bliss 2.7 gsi, check my telegram channel for more info.
cant escape bootloop hell and error 255
rafyvitto said:
Follow these easy steps
Makes sure you have the GSI image on your sdcard before starting this, if your coming from lineage OS backup your data!
1.Unlock Bootloader
2. Boot into bootloader, check your slot if on B switch to A and vice versa.(fastboot set_active a/b) or you can stay in your current active slot up to you.
3.Download twrp and flash it (fastboot flash boot boot.img)
4.Boot back into boot loader and run "fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img" link with b11 vbeta.img
5.Boot into twrp,Format data or in bootloader run this command "fastboot format userdata" to get rid if encryption else gsi wont boot then, go to "install" navigate to your sdcard where you place the gsi , look for 'select image" then flash your gsi.
6.To flash gapps(skip if the gsi includes them) if your using a aosp gsi go to twrp then go into /wipe/advanced wipe/ select system on the options then "repair or change file system" then press on "resize file system" this will resize your system partiton back to 3.X gigs and allow you to flash gapps.
7.Then reboot to system
8. Your gsi "should" boot
Downloads:
http://www.mediafire.com/folder/ha8j5crsdmbmx/ZTE_Axon_10_pro_stuff
https://forum.xda-developers.com/pr...bled-device-development/gsi-havoc-os-t3930030 Havoc OS the gsi ive been using for some weeks.
Fixes and WorkArounds
Volte Fix for GSi
Install the volt-ims.apk as you would normally install an apk, download here http://www.mediafire.com/file/l0x88jx5zxyknhh/volte-ims.apk/file
For root( magisk) and twrp flash http://www.mediafire.com/file/de8tccz7gr93831/twrp-magisked-los-boot.img/file
To pass SafetyNet flash this http://www.mediafire.com/file/867xncq865vvtct/Universal-safetynet-fix-v3.zip/file
Also I created a template for what works on phhusson Treble experiments wiki:
https://github.com/phhusson/treble_experimentations/wiki/ZTE-Axon-10-Pro
CREDITS:
Unjustifieddev for his work on lineage, and the boot.img im using.
All the gsi creators
Click to expand...
Click to collapse
rafyvitto said:
Lineage 17 is very broken right now, i would suggest flashing bliss 2.7 gsi, check my telegram channel for more info.
Click to expand...
Click to collapse
having trouble
Steps I followed:
(bootloader been unlocked but double checked to be sure)
Started from LineageOS 16 clean flashed based
booted rom made sure Debug was enable in settings did nothing else
booted to bootloader
>fastboot set_active a
>fastboot boot "D:\Android\Flash\Recovery.img"
In Recovery:
Installed Twrp zip
install zip DisableForcedEncryption.zip
-reboot bootloader
>fastboot flash vbmeta "C:\Users\chris\Downloads\ZTE_Flash\vbmeta.img"
>fastboot format userdata
boot to recovery:
Installed GSI Image of Havoc OS to System image
Flashing system image......
simg2ing '/sdcard1/Havoc-OS-v2.9-20190914-phhgsi_arm64_ab-offical.img' 'dev/block/bootdevice/by-name/system_a'process
ended with ERROR: 255
got creative because nothing i was doing was fixing the problem so i went into fast boot and
>fastboot flash system "location/of/Havoc.img"
now no longer can acess the recovery not even but fastboot boot img command and back in a bootloop hell
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot boot "D:\Android\Flash\Recovery.img"
downloading 'boot.img'...
OKAY [ 0.605s]
booting...
FAILED (remote: Failed to load/authenticate boot image: Load Error)
finished. total time: 0.640s
also i have no way to return to the original 10 pro rom whenever i flash it via the EDL tool with one of the US edl
Zips you provided i have boot loop but it gives me enough so i can have bootloader mode accessible but i have to rerun
the bootloader unlock. but flashing Lineage 16 seems to be the only thing to make my phone functional without giving it boot loop hell
ill try do it with bliss later but if there's anywhere i went wrong or how to solve the 255 let me know i really want to try out one of those GSIs
but im running on the US rom and using the TWRP for my pro from the fourms so i just really confused here idk if i could possibly give you anymore details
ok update i got it working
1. the 255 i fixed by
"
Reboot into recovery, TWRP
Go to the terminal in "Advanced"
Type cd /system to change the path to the system folder
Type rm addon.d to remove the addon file
Type exit to quit from the terminal
Now back to TWRP home, try backup/restore again, it should works.
Further adjustment: do check the use rm -f to format disk settings of TWRP, to make sure TWRP won't mess up the filesystem."
secondly what was ruining me was a big dumb mistake on my part you HAVE to do " --disable-verity --disable-verification flash vbmeta vbmeta.img" with the latest ADB tool kit I was using minimal adb and fastboot then got it to work
In step 5,i can not boot into TWRP and phone displays ZTE crashdump mode.
Please help.
Thanks.
Edit: I fixed it and can flashed this rom but it has some bugs.

[STOCK][FASTBOOT][Root] Revive bootloop with Fastboot Flashable Images, RealMe 5 Pro(IN)

I tried to root this phone, and got bootloop. The screen only showed "Realme", vanished, and showed this again. I can only boot to BOOTLOADER.
I tried Flash Tool. Download the ".ofp" file from google. Didn't work. As it only supports Realme older than RM5P. No use.
Tried to use MSM Tools. Difficult. As it is only supposed to be used by Oppo/Realme service centers and needs passwords. So, MSM is out of the way.
Then, I remember, the easiest thing that can be done is flashing through FASTBOOT with fastboot img files. Sadly, I tried to seach google, in vain. Just found one kind person offered a complete set of files. But it was old. Still in Android 9. How could I revive my phone and update it?
Then I found a thread about TWRP by @BabluS It could flash OZIP files. That's it. So, my plan is :
Download official OTA Ozip file from Realme site (Software update site... Indonesia). The name is like RMX1971EX_11_OTA_xxx.ozip (will show if you click "download"). Put it in external SD.
Flash the BabluS TWRP. Wipe dalvic, cache, data, system. Back to boot bootloader
Flash the fastboot files one by one (and the phone gets the old Realme version.)
- boot.img
- dtbo.img
- system.img
- vbmeta.img
- vendor.img
Update the phone to the current version through TWRP (Click Install. Click Storage (?), choose ext sdcard, find the OZIP file).
Wipe data through TWRP again .... It worked...!
Note:
When unlocking, in-deep-test, one has to wait for 15 minutes. Processing... Please wait... I tried several times, waiting for hours, in vain. Then tried to click "verify". Looked like it was Reviewed already.
Get the fastboot files through this link.
The boot.img contains stock recovery!
Get the BabluS TWRP here.
Error flash:
- "Invalid sparse file format at header magic". Just ignore the error. Wait for 5 minutes or more until is is finished.
Big thanks to @BabluS and @acervenky for your great work ....
good
...Thanks man...
could you please write the flash commands down ?
Cz I don't know the pertition name for dtbo.img file and vbmeta.img file
(<Fastboot flash ??? dtbo.img>)
Mehedi Hassan 09 said:
...Thanks man...
could you please write the flash commands down ?
Cz I don't know the pertition name for dtbo.img file and vbmeta.img file
(<Fastboot flash ??? dtbo.img>)
Click to expand...
Click to collapse
It is probably the same name
So the command for dtbo.img would be: fastboot flash dtbo dbto.img
same for vbmeta.img

Question How I can root realme 8 5g

I submitted on ( in deep tool ) still application approved
Can I open bootloader now ?
I need rom for my device and all file to root it
V ( RMX3241_11_A.15 )
do you still want to root smartphone?
Please don't root , useless as no custom ROM is available or you might brick your device
I have rooted my smartphone, on realme 8 5G
Rzk09 said:
I have rooted my smartphone, on realme 8 5G
Click to expand...
Click to collapse
Hello, can you tell me how you got root access, thanks
frenon76 said:
Hello, can you tell me how you got root access, thanks
Click to expand...
Click to collapse
has your device been unlocked bootloader?
Not yet, I'm working on it
frenon76 said:
Not yet, I'm working on it
Click to expand...
Click to collapse
what version of the firmware build is on your device?
RMX3241VF_11_A_23
frenon76 said:
RMX3241VF_11_A_23
Click to expand...
Click to collapse
Global or India?
Global
frenon76 said:
Global
Click to expand...
Click to collapse
if you have unlocked your device, follow these steps
1.donwload boot.img and vbmeta.img, if your firmware version is A.23 global version you can download it in Attachments
2. Patch the boot.img that you downloaded earlier in the magisk manager, when it's finished you can change the name to "boot.img" to make it easier to patch
3. Copy the boot.img patch to your laptop/PC in "adb and fastboot" folder, together with vbmeta.img (don't patch the vbmeta.img file in magisk manager)
4. turn on usb debugging option
5. enter fastboot mode (turn off your device and hold vol up and power)
6. if you have entered fastboot, plug your devices into your laptop/pc and type in adb "fastboot devices" (make sure your devices are connected)
7. And now start patching the boot.img file that you patched earlier and disable boot verification (vbmeta.img)
8. Ok,Patch the boot.img file with the command "fastboot flash boot boot.img"
9. and finally disable vbmeta copy this command "fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img"
10. and restart your device
I hope this can help you
Muchas gracias, voy a intentar
Rzk09 said:
if you have unlocked your device, follow these steps
1.donwload boot.img and vbmeta.img, if your firmware version is A.23 global version you can download it in Attachments
2. Patch the boot.img that you downloaded earlier in the magisk manager, when it's finished you can change the name to "boot.img" to make it easier to patch
3. Copy the boot.img patch to your laptop/PC in "adb and fastboot" folder, together with vbmeta.img (don't patch the vbmeta.img file in magisk manager)
4. turn on usb debugging option
5. enter fastboot mode (turn off your device and hold vol up and power)
6. if you have entered fastboot, plug your devices into your laptop/pc and type in adb "fastboot devices" (make sure your devices are connected)
7. And now start patching the boot.img file that you patched earlier and disable boot verification (vbmeta.img)
8. Ok,Patch the boot.img file with the command "fastboot flash boot boot.img"
9. and finally disable vbmeta copy this command "fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img"
10. and restart your device
I hope this can help you
Click to expand...
Click to collapse
HELP, I did this on my phone (realme 8 5g global) and now the system does not turn on as something is recovery (TWRP) and fastboot works normally
this is my main and the only relatively new phone so please help
PS sorry for mistakes, I'm from Poland and I'm writing through a translator
Rzk09 said:
if you have unlocked your device, follow these steps
1.donwload boot.img and vbmeta.img, if your firmware version is A.23 global version you can download it in Attachments
2. Patch the boot.img that you downloaded earlier in the magisk manager, when it's finished you can change the name to "boot.img" to make it easier to patch
3. Copy the boot.img patch to your laptop/PC in "adb and fastboot" folder, together with vbmeta.img (don't patch the vbmeta.img file in magisk manager)
4. turn on usb debugging option
5. enter fastboot mode (turn off your device and hold vol up and power)
6. if you have entered fastboot, plug your devices into your laptop/pc and type in adb "fastboot devices" (make sure your devices are connected)
7. And now start patching the boot.img file that you patched earlier and disable boot verification (vbmeta.img)
8. Ok,Patch the boot.img file with the command "fastboot flash boot boot.img"
9. and finally disable vbmeta copy this command "fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img"
10. and restart your device
I hope this can help you
Click to expand...
Click to collapse
bro please i need your help i'am on A24 Global version version do u have boot.img of this version if not please give me link of A23 global version full rom thank u
mantap, how to downgrade into RMX3241VF_11_A_23? ada no wa or youtube or ig?.. thank u, terima kasih
Rzk09 said:
I have rooted my smartphone, on realme 8 5G
Click to expand...
Click to collapse
Vbmat.img and boot.img for RMX3241_11_A.16 please
Rzk09 said:
if you have unlocked your device, follow these steps
1.donwload boot.img and vbmeta.img, if your firmware version is A.23 global version you can download it in Attachments
2. Patch the boot.img that you downloaded earlier in the magisk manager, when it's finished you can change the name to "boot.img" to make it easier to patch
3. Copy the boot.img patch to your laptop/PC in "adb and fastboot" folder, together with vbmeta.img (don't patch the vbmeta.img file in magisk manager)
4. turn on usb debugging option
5. enter fastboot mode (turn off your device and hold vol up and power)
6. if you have entered fastboot, plug your devices into your laptop/pc and type in adb "fastboot devices" (make sure your devices are connected)
7. And now start patching the boot.img file that you patched earlier and disable boot verification (vbmeta.img)
8. Ok,Patch the boot.img file with the command "fastboot flash boot boot.img"
9. and finally disable vbmeta copy this command "fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img"
10. and restart your device
I hope this can help you
Click to expand...
Click to collapse
Can you send me the attachments for RMX3241_11_C.04 this android version?
Rooted Realme 8 5G to fix unknown IMEI but in the end I know that unknown baseband is the major problem, and no custom ROM for RMX3241.
Stock firmware: RMX3241_11_A.26
Magisk 25.2
Root Tool: MTKClient (GitHub) with Brom/Edl Mode since I got no fastboot
For MTKClient, you'll need to install "MediaTek CDC driver 1.0.8" and manually add legacy hardware in device manager "MediaTek USB PORT" and other thing that you need in the github link.
Root method just same as fastboot method, patch your boot.img with Magisk app and flash patched boot.img + vbmeta.img or using MTKClient flash the patched boot.img and vbmeta.img.empty included in MTKClient.
Where to get your stock boot.img vbmeta.img? Use MTKClient or MTKMETAUTILITY to dump it from your phone. Dump the whole img except userdata to backup just incase....
If somehow the root fail after like 1h bootloop at logo, just reflash with stock boot vbmeta. So keep in mind to backup your stock img file.
I also have TWRP as recovery flashed using MTKClient but no custom ROM?

Official instructions don't say that you need to get vbmeta.img

I followed the official instructions you can find here.
My device has a boot ramdisk so I grabbed the boot.img as requested by the instructions. I also checked if it has a separate vbmeta partition and it does.
I followed all steps in section "Patching Images", but when I get to the line saying
(Optional) If your device has a separate vbmeta partition, you can patch the vbmeta partition with command:
Bash:
fastboot flash vbmeta --disable-verity --disable-verification vbmeta.img
Click to expand...
Click to collapse
I don't know from where I was supposed to get vbmeta.img. The instructions never mentioned getting vbmeta.img. Maybe it doesn't matter because the step is optional, and it says "you can patch the vbmeta partition", not "you should" or "you must".
When extracting boot.img from my phone's firmware I also got vbmeta.img, but I don't know if I should flash it as it is, or if I should have Magisk patch it first. Anyway I skipped that optional step and Magisk works, but it would be nice if the instructions were more clear.
I also don't know if the fact that Magisk works despite me skipping that step has anything to do with the fact that before installing Magisk I had dirty flashed LineageOS 19 over LineageOS 18.1, where I had already installed Magisk some months ago by flashing the apk from recovery. The reason I had to reinstall Magisk is that after the upgrade to LOS 19 apps with root permissions would complain about not having root permissions, and the Magisk app would say Magisk was not installed.
Ludoboii said:
Code:
fastboot flash vbmeta --disable-verity --disable-verification vbmeta.img
Click to expand...
Click to collapse
The vbmeta.img that they are talking about is the original vbmeta that you copied.
Of course, you need to be rooted or using a ROM bootloader to copy that.
That's a bit of a Catch 22.
That command just alters byte 0x7b from 0x00 to 0x03.
That's the flags.
The minimal vbmeta.img is 256 bytes with the correct header and 0x03 at 0x7b
I just tried this:
Code:
C:\>fastboot erase vbmeta
C:\>fastboot flash vbmeta vbmeta_empty.img
C:\>fastboot reboot
This worked fine for me. No guarantees for you. You don't need to erase, I just wanted to make sure.
I believe that the vbmeta is normally verified in the init process in the boot image.
Since Magisk has a custom init it probably just ignores vbmeta.
If you went to flash a modified boot image that had a stock init this would make a difference.

Categories

Resources