Related
Hello All,
I am a noob and recently learned how to root, unlock or re-partition, install blackrose etc but using your blogs and wikicynogemod.
I am trying to update my phone to Texas ICS using blog by OP- http://forum.xda-developers.com/showthread.php?t=1366897
I was able to reach till the step mentioned below :
i.e.
fastboot flash hboot hboot_brcrust_220-10-206-ICS.nb0
fastboot reboot-bootloader
fastboot -w
and now my phone shows TexasICS on the second line that mans it flashed correctly.
I downloaded the tar file "Evervolv-Perdo-2.2.0a6" but I am clueless about the next steps.
1. To build Evervol --> How and where as repo command doesnt work on my computer undert android sdk directory
2. tar xjf --> I am using windows 7 and hence no tar on my laptop.Meanwhile I am downloading the zip file also and see if unzip works.
But I am curious where to run these commands- either on cmd prompt under android-sdk directory or the phone emulator.
And interestingly, android-sdk dont have unzip/tar command and I have no access to phone now, its not booting.
Also I cant login to my phone now, when I boot it, its stuck at the Nexus One startup logo, not going further, so I believe I can't put anything in the SD card now.
Kindly help as my phone is not accessible now and I am kind of handicapped because of that
FYI : Recently I upgraded the phone to 2.3.7 using Cynogenmod, clock recovery.
you might have lost ur recovery
so fastboot any preffered recovery.img . put .zip in sd and flash it
or you can fastboot system.img, boot.img n recovery.img
Sent from my Nexus One using Tapatalk
If you have a custom recovery like clockworkmod just turn on your device holding trackball or something (I don't remember exactly) and you'll be in recovery or fastboot. Anyway, go to recovery and restore your nand backup. After that you can keep trying (or read below).
If you don't have a backup you can insert the SD card directly into the computer and copy the Evervolv latest version (.ZIP). Then go to recovery and wipe data & cache then install the zip from sd card.
You don't need to pay attention to the building Evervolv part of the post as it's not needed for the install. Don't forget to flash gapps later if you want to.
Sorry for my English and I hope this helps as I'm a bit noob also
Sent from my GT-P7510 using xda app-developers app
flash recovery
Flash recovery by
booting in fastboot
fastboot flash recovery recoveryNAME.img
then reboot to recovery u will get recovery the flash ICS.zip rom
Note:I'm going to assume you have the Fastboot and ADB Drivers installed and the boot loader is unlocked!
Why is this here?
This thread is made to help new users install the developers preview through what I think is the fastest way and safest way too through the command prompt on Windows.
Responsibility!
If your device becomes bricked, makes toast for you, and anything else I did not mention its simply not my fault since you took it upon your self to do this method.
Credits!Thanks Google for this lovely Operating System. Thank you Chain Fire for providing this method to root Android Lollipop and for your app and boot.img too! Thanks to LG for manufacturing this great device to use and enjoy stock Android. Finally, big thanks to TWRP for providing us with this recovery!
The Steps!Step 1: Download the Lollipop preview HERE, extract it and open the folder with all the image files along with the radio and bootloader image too.
Step 2: Drop all the images to your folder that contains the ADB and Fastboot files
Step 3: Open the folder that contains the ADB and Fastboot files
Step 4: Hold the shift key and right click and click "Open command window here"
Caution! Make sure you back up everything before you begin the process if not its not my fault you forgot to back up.
Step 5: Make sure your device is in fastboot and connected. We are going to replace the boot loader for a newer one. Please make sure the boot loader image name first before we began because i'm just going to use boot loader as a example the real file name will be different. Type the command shown below.
Code:
fastboot flash bootloader bootloader.img
Step 6: Now we are going to flash the Radio as also stated above be sure to check the image name before we flash.
Code:
fastboot flash radio radio.img
Step 7: Now we are going to flash userdata. This part you don't have to worry about the file name you can just copy and paste the command but, I would double check.
Code:
fastboot flash userdata userdata.img
Step 8: Now going to flash boot or the kernel just as step 8 and here from out I will let you know when you have to worry about the file name again.
Code:
fastboot flash boot boot.img
Step 9: Now were flashing the system files.
Code:
fastboot flash system system.img
Step 10: Now were flashing the a custom recovery (twrp for this example) so we can install the SuperSU files later. You can get the recovery image HERE and rename it "Trecovery" and place it to the same folder. After flashing it go to the recovery and from there reboot it.
Code:
fastboot flash recovery Trecovey.img
Yay! We got Android Lollipop now we have to root it.Step 1: Let Andriod Lollipop boot up and go download SuperSu on your device by going to Chainfire SuperSU thread and click on his installable zip link and download SuperSU 2.14 or above. On your computer download his modified boot image HERE and rename it Rboot.img and move it your folder where the ADB and Fastboot files are.
Step 2: On your computer go to fastboot again on your phone and type the code in below.
Code:
fastboot flash boot Rboot.img
Step 3: Go to recovery and install the SuperSU zip as usual, reboot, and that's it. Enjoy!
reserved
Trecovery.img
Thanks for your work. Unfortunately, we already have a sticky thread on flashing images and rooting: http://forum.xda-developers.com/google-nexus-5/general/tutorial-how-to-flash-factory-image-t2513701
The method to flash and root lollipop is no different than any other version.
Because we don't want multiple threads with the some information I will close this thread
Thanks.
Hello everybody, for serveral months i saw several people asking help to back to stock ROM
here we finally have a guide that saved me and can save you!
Requirements:
Windows operative system
Multi Tool
OFFICIAL stock rom (in this guide i'll use B370 for H60-L04) Download
and the most important thing Huawei Update Extractor! Download
and let's go!
First of all open HUE (Huawei Update Extractor) and after selected UPDATE.APP file, extract system.img , boot.img , cust.img, recovery.img that we will flash on the phone, and put them in the folder where adb and fastboot are installed (in this case we use the multi tool directory).
now open cmd or command prompt and move on multi tool directory (cd C:\\Users\NAME bla bla bla\DIRECTORY TO MULTI TOOL)
now plug in your phone and enable Debug USB and type:
Code:
adb.exe devices (to control if your device is online, if not grant the permission on the phone)
adb.exe reboot bootloader
Now we flash all the files with fastboot
the order of commands doesn't matter
(MAKE SURE THAT YOU HAVE SYSTEM, BOOT, RECOVERY AND CUST .img ON THE MAIN FOLDER!)
Code:
fastboot.exe flash boot BOOT.img
fastboot.exe flash recovery RECOVERY.img
fastboot.exe flash cust CUST.img
fastboot.exe flash system SYSTEM.img
than reboot into recovery by doing
fastboot.exe reboot and holding only VOLUME UP button
than do all the wipe (cache and data) than reboot system
Easy right? :laugh:
TheTigerDeveloper said:
Hello everybody, for serveral months i saw several people asking help to back to stock ROM
here we finally have a guide that saved me and can save you!
Requirements:
Windows operative system
Multi Tool
OFFICIAL stock rom (in this guide i'll use B370 for H60-L04) Download
and the most important thing Huawei Update Extractor! Download
and let's go!
First of all open HUE (Huawei Update Extractor) and after selected UPDATE.APP file, extract system.img , boot.img , cust.img, recovery.img that we will flash on the phone, and put them in the folder where adb and fastboot are installed (in this case we use the multi tool directory).
now open cmd or command prompt and move on multi tool directory (cd C:\\Users\NAME bla bla bla\DIRECTORY TO MULTI TOOL)
now plug in your phone and enable Debug USB and type:
Code:
adb.exe devices (to control if your device is online, if not grant the permission on the phone)
adb.exe reboot bootloader
Now we flash all the files with fastboot
the order of commands doesn't matter
(MAKE SURE THAT YOU HAVE SYSTEM, BOOT, RECOVERY AND CUST .img ON THE MAIN FOLDER!)
Code:
fastboot.exe flash boot BOOT.img
fastboot.exe flash recovery RECOVERY.img
fastboot.exe flash cust CUST.img
fastboot.exe flash system SYSTEM.img
than reboot into recovery by doing
fastboot.exe reboot and holding only VOLUME UP button
than do all the wipe (cache and data) than reboot system
Easy right? :laugh:
Click to expand...
Click to collapse
Thanks for the guide! I used to follow the same procedure too but another alternative is to use multi-tool and use the unbrick option and follow the instructions. It super noob friendly:highfive:
shubham1120 said:
Thanks for the guide! I used to follow the same procedure too but another alternative is to use multi-tool and use the unbrick option and follow the instructions. It super noob friendly:highfive:
Click to expand...
Click to collapse
i know, but with this one any type of user can follow the guide (especially linux user)
my phone keep restarting, i have try this method, no works, helpppppppp
it stuck on honor logo
Hi Guys,
i got the same problem here with my H60-L12
After flashing Beta Lollipop 5.1.1 i tried to go back to 4.4.4.
Now it's stuck in bootloop and now it keeps flashing the honor logo.
Tried to unbrick it with Multi-Tool and different stock roms but i cant get into recovery or the 3 button install method, only thing working is fastboot mode.
Any suggestions?
Thank you!!
ok, now i'm desperate.
Got different Stock Roms (4.4 5.8.1;4.4 B119;4.4 B310; 4.4 B316, tried TWRP in different versions, even tried to reinstall fastboot drivers , same problem on Windows 10 and 7.
Only think working is Fastboot&Rescue Mode (White Screen, Phone UNLOCKED), but only when plugged in on PC with USB cable.
When plugged in charger, it just reboots and reboots i can't switch to Recovery or Fastboot mode and doesn't even charge the phone.
Maybe someone got any idea, did i use wrong stock roms? Do i have to use Rollback/Revert versions?
Any way to back to stock rom without unlock bootloader?
I've made a horrible mistake.
I was on 5.9.16, tried to downgrade by flashing system, recovery, cust and crc.
Unfortunately I've done it with B316, which is 4.4.4, so i got this annoying bootloop, in which i can't access recovery, bootloader or use the 3 buttons method.
It seems as if the phone tries to forcefully boot into system ignoring everything I do.
I tried draining the battery to turn it off, which worked, but when i charged it it tried to system boot as soon as there's enough battery.
Any ideas?
and where can I find update.app?
This worked for me! I switched from CM11 to the stable 5.1.1 release using your guide. Flashed B370 and then did a local update for the stable lollipop rom. Thanks a ton.
i need help
I extract listed file and open cmd.
I was able to reboot into bootloader.
I writing "fastboot.exe flash boot BOOT.img" and here is the result:
target reported max download size of 471859200 bytes
sending 'boot' (7754 KB)...
OKAY [ 0.810s]
writing 'boot'...
FAILED (remote: Command not allowed)
finished. total time: 0.820s
Whats now?
I have rooted H60-L04 with cyanogenmod 11-20150822 KitKat
Thanks
Michal
yeah, very easy guide
i did to my H60-L04 CM11
thanks for sharing
error
target reported max download size of 471859200 bytes
sending 'boot' (7754 KB)...
OKAY [ 0.810s]
writing 'boot'...
FAILED (remote: Command not allowed)
finished. total time: 0.820s
i couldnot flash stock recovery because of the fail command not alowed,
i couldnot flash stock recovery because of the fail command not alowed,
Thank you so much! Now my phone is bricked... How about not sharing ur help when u don't know what could happen?
My phone shows Rescue Mode
Attention! Please update system again!
Error!
FuncNo (FUNC_BOOT_KERNEL)
Error NO: 2
i couldnot flash stock recovery because of the fail command not alowed,
i couldnot flash stock recovery because of the fail command not alowed,
thalaraj1992 said:
i couldnot flash stock recovery because of the fail command not alowed,
Click to expand...
Click to collapse
are you on a boot loop?
make sure your device is recognized by your computer.
download universal-adb-driver for windows and install
Things are changing with the advent of project treble and seamless updates. OnePlus will no longer release ROMs flashable via recovery (either stock or twrp) because is no more needed. The updates will be done on the slot not used for example if you are using slot a the update will be installed on slot b and the slot b will be set as default. If you brick and you are in bootloop how you can restore the rom? You can't with Stock ROM you have, because the zip can be only installed via Update Engine, so what can you do? Flash a stock rom via fastboot. I have extracted all images from the stock zip and i have made a new zip with the Fastboot ROM with a flash-all.bat included. This will work only if your bootloader is unlocked. This will erase all your data and will wipe your internal storage.
HOW TO FLASH
This version is only for not branded devices
Download the zip;
Unpack the zip in a folder;
Reboot the OnePlus 6T in fastboot mode (Power and volume-);
Connect the OnePlus 6T to PC;
Run flash-all.bat flasher you need;
Wait until the process end;
The phone will automatically reboot.
FLASHER ADVANCED GUIDE
flash-all-partitions-fastboot.bat : this .bat will flash all possible partitions through fastboot (Except persist) , there are some criticals partitions that can't be flashed through fastboot;
flash-only-persist.bat : this .bat will flash only persist partition in fastboot mode (This is good for people that have problems with sensor);
flash-all-partitions-recovery-criticals.bat : this .bat will boot the twrp and will flash criticals partitions, use this carefully;
flash-system-boot-vendor.bat : this .bat is the same of older flash-all.bat and so it will flash only vendor, system and boot;
flash-all-partitions.bat : this .bat will run flash-all-partitions-fastboot.bat , then flash-only-persist.bat and then flash-all-partitions-recovery-criticals.bat .
Now usually the one needed is only the first "flash-all-partitions-fastboot.bat" but if you are badly bricked i recommend to use flash-all-partitions.bat .
DOWNLOAD
All roms on AFH: https://www.androidfilehost.com/?w=files&flid=284914
All roms on Sourceforge: https://sourceforge.net/projects/fastbootroms/files/OnePlus 6T
BRANDED PHONE
GUIDE: https://forum.xda-developers.com/on...-t-mobile-oneplus-6t-to-t3865966/post78131430
T-Mobile OnePlus 6T Internationa ROM: https://www.androidfilehost.com/?fid=11410963190603845445
MANUAL FLASH: Windows - OSX - Linux
If you want to manual flash these roms these are the commands (you need to extract images.zip before proceed)
Fastboot Partitions:
Code:
fastboot flash aop_a aop.img
fastboot flash aop_b aop.img
fastboot flash bluetooth_a bluetooth.img
fastboot flash bluetooth_b bluetooth.img
fastboot flash boot_a boot.img
fastboot flash boot_b boot.img
fastboot flash dsp_a dsp.img
fastboot flash dsp_b dsp.img
fastboot flash dtbo_a dtbo.img
fastboot flash dtbo_b dtbo.img
fastboot flash fw_4j1ed_a fw_4j1ed.img
fastboot flash fw_4j1ed_b fw_4j1ed.img
fastboot flash fw_4u1ea_a fw_4u1ea.img
fastboot flash fw_4u1ea_b fw_4u1ea.img
fastboot flash modem_a modem.img
fastboot flash modem_b modem.img
fastboot flash oem_stanvbk oem_stanvbk.img
fastboot flash qupfw_a qupfw.img
fastboot flash qupfw_b qupfw.img
fastboot flash storsec_a storsec.img
fastboot flash storsec_b storsec.img
fastboot flash system_a system.img
fastboot flash system_b system.img
fastboot flash vbmeta_a vbmeta.img
fastboot flash vbmeta_b vbmeta.img
fastboot flash vendor_a vendor.img
fastboot flash vendor_b vendor.img
fastboot flash LOGO_a LOGO.img
fastboot flash LOGO_b LOGO.img
If you need also persist partition, this is the command:
Code:
fastboot flash persist persist.img
Criticals Partitions, for these you need to boot the TWRP:
Code:
fastboot boot TWRP.img
When you are in TWRP you need to run these commands to push and flash all criticals partitions:
Code:
adb push abl.img /sdcard/abl.img
adb shell dd if=/sdcard/abl.img of=/dev/block/bootdevice/by-name/abl_a
adb shell dd if=/sdcard/abl.img of=/dev/block/bootdevice/by-name/abl_b
adb push cmnlib.img /sdcard/cmnlib.img
adb shell dd if=/sdcard/cmnlib.img of=/dev/block/bootdevice/by-name/cmnlib_a
adb shell dd if=/sdcard/cmnlib.img of=/dev/block/bootdevice/by-name/cmnlib_b
adb push cmnlib64.img /sdcard/cmnlib64.img
adb shell dd if=/sdcard/cmnlib64.img of=/dev/block/bootdevice/by-name/cmnlib64_a
adb shell dd if=/sdcard/cmnlib64.img of=/dev/block/bootdevice/by-name/cmnlib64_b
adb push devcfg.img /sdcard/devcfg.img
adb shell dd if=/sdcard/devcfg.img of=/dev/block/bootdevice/by-name/devcfg_a
adb shell dd if=/sdcard/devcfg.img of=/dev/block/bootdevice/by-name/devcfg_b
adb push hyp.img /sdcard/hyp.img
adb shell dd if=/sdcard/hyp.img of=/dev/block/bootdevice/by-name/hyp_a
adb shell dd if=/sdcard/hyp.img of=/dev/block/bootdevice/by-name/hyp_b
adb push keymaster.img /sdcard/keymaster.img
adb shell dd if=/sdcard/keymaster.img of=/dev/block/bootdevice/by-name/keymaster_a
adb shell dd if=/sdcard/keymaster.img of=/dev/block/bootdevice/by-name/keymaster_b
adb push xbl.img /sdcard/xbl.img
adb shell dd if=/sdcard/xbl.img of=/dev/block/bootdevice/by-name/xbl_a
adb shell dd if=/sdcard/xbl.img of=/dev/block/bootdevice/by-name/xbl_b
adb push xbl_config.img /sdcard/xbl_config.img
adb shell dd if=/sdcard/xbl_config.img of=/dev/block/bootdevice/by-name/xbl_config_a
adb shell dd if=/sdcard/xbl_config.img of=/dev/block/bootdevice/by-name/xbl_config_b
REMEMBER
"Invalid sparce file format at header magic" is not an error, you need to wait a bit when you see that string, just wait.
These ROMs can't be used to update or downgrade your phone but just to restore your phone, so don't use them to come back to oreo or to update from oreo to pie.
If you want to rebrand your phone from HydrogenOS to OxygenOS you can follow this guide: Rebrand Guide
If you want you can use also my tool to flash Factory Images, unlock bootloader, flash twrp or to understand if the device is recognized: https://toolaio.tk/
Thanks to @SaiBork for first time tested
If you got some problems like write error or no partition, check this: https://forum.xda-developers.com/showpost.php?p=76658555&postcount=34
Thanks to @Dark Nightmare for T-Mobile Rom Version
DONATE LINK
If you want to support this and others my projects please consider making a donation, thanks.
If you are unable to use pools or moneybox, you can also make a normal donation, all private donations will be added in the moneybox:
Thanks Mister :good:
Great work, thx
This is great work. Thanks!
If anyone has the T-Mobile firmware or OTA captured, please post it.
Would it be wise to extract the zip to the 6T prior to rooting just in case something goes wrong?
shizat63 said:
Would it be wise to extract the zip to the 6T prior to rooting just in case something goes wrong?
Click to expand...
Click to collapse
This fastboot rom are completely stock rom, not modified
mauronofrio said:
This fastboot rom are completely stock rom, not modified
Click to expand...
Click to collapse
Right.
So before rooting the device, would it be good to copy the images from this zip to a dir on the 6T in case something goes wrong with the rooting process? For example if Magisk or TWRP mess something up, and the 6T is in a bootloop.
Or are the images in the zip only for flashing from your PC to the 6T? So it would be of no use to have the images sitting on the 6T as a backup.
Hello. after flashing with flash-all.bat, my 6T just boots to the bootloader unlocked warning and stays there. I don't know what to do next.
EDIT: Nevermind, after trying again it worked.
shizat63 said:
Right.
So before rooting the device, would it be good to copy the images from this zip to a dir on the 6T in case something goes wrong with the rooting process? For example if Magisk or TWRP mess something up, and the 6T is in a bootloop.
Or are the images in the zip only for flashing from your PC to the 6T? So it would be of no use to have the images sitting on the 6T as a backup.
Click to expand...
Click to collapse
Actually there is not a twrp that support decryption so if you also have the images on the phone you can't flash it in twrp mode. At this moment these roms can be only flashed through fastboot with a pc
Seoyoon said:
Hello. after flashing with flash-all.bat, my 6T just boots to the bootloader unlocked warning and stays there. I don't know what to do next.
EDIT: Nevermind, after trying again it worked.
Click to expand...
Click to collapse
Perfect:good:
thank you thank you thank you OP! Nearly bricked my phone while trying to install root (something got messed up with TWRP) and I couldn't even get out of bootloader into recovery. I just got my phone a few hours ago, that would have been sad
nhshah7 said:
thank you thank you thank you OP! Nearly bricked my phone while trying to install root (something got messed up with TWRP) and I couldn't even get out of bootloader into recovery. I just got my phone a few hours ago, that would have been sad
Click to expand...
Click to collapse
Perfect:good:
If you want to support this and others my projects please consider making a donation, thanks.
After using flash-all.bat I'm getting the "Your device is corrupt" red error message on boot. I can skip by pressing power twice and phone boots normally.
I see people with 6 had to use MSM download tool to get rid of the error.
Is there any solution for 6T?
nhshah7 said:
thank you thank you thank you OP! Nearly bricked my phone while trying to install root (something got messed up with TWRP) and I couldn't even get out of bootloader into recovery. I just got my phone a few hours ago, that would have been sad
Click to expand...
Click to collapse
Just for the sake of your sanity in the future, if you can get to bootloader and device files are available, you can always get it up and running. I learned that very quickly way back in the day
iaTa said:
After using flash-all.bat I'm getting the "Your device is corrupt" red error message on boot. I can skip by pressing power twice and phone boots normally.
I see people with 6 had to use MSM download tool to get rid of the error.
Is there any solution for 6T?
Click to expand...
Click to collapse
Only msm tool i think
Well same situation here got boot loop trying to root then after install using flashall.bat now I can't get a VOLTE and now I complete lost signal but when I swap my sim card to sim slot 2 everything work...kinda weir but does anyone know how to fix it?
_BГ@ckθut said:
Well same situation here got boot loop trying to root then after install using flashall.bat now I can't get a VOLTE and now I complete lost signal but when I swap my sim card to sim slot 2 everything work...kinda weir but does anyone know how to fix it?
Click to expand...
Click to collapse
Did you have a branded version?
mauronofrio said:
Did you have a branded version?
Click to expand...
Click to collapse
Oh I has unlock one from on plus website and use it on Verizon...is that what u mean...sorry I'm new to OP device
Edit: I try to do fastboot flash modem A and B also factory reset but seem not work...
_BГ@ckθut said:
Oh I has unlock one from on plus website and use it on Verizon...is that what u mean...sorry I'm new to OP device
Click to expand...
Click to collapse
Branded version are different, they have a particoular partitions for volte, i think the only.method to solve your problem is to find another person with the same branded device and make a partitions backup that you can restore
mauronofrio said:
Branded version are different, they have a particoular partitions for volte, i think the only.method to solve your problem is to find another person with the same branded device and make a partitions backup that you can restore
Click to expand...
Click to collapse
So how do I make that? Do I need provide any information or anything?
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!