Database Users

Yet Another Bootloop Thread

Hello,
So I decided to unlock and root my Pure today. Originally I was going to flash Lineage, but I later decided not to. Anyway, I was following the instructions here.
So I unlocked and installed TWRP succesfully. Then I decided to root. And that's where I screwed up.
Following these instructions, I now have a phone that won't boot past the "M" logo. Apparently my mistake was not using the current SU version.
I have been Googling for an hour now, but almost every solution I've come across has involved plugging the phone into the computer. My issue is that my computer isn't recognizing the phone when I plug it in, so my knowledge of how to fix this is limited (and my expertise in this topic was minimal to begin with...). I can get to recovery mode, and have tried a factory reset. No dice. I also put the latest official factory image from Motorola on the SD card, but when I went to install it, it wouldn't show up.
As you can tell I am quite stuck here. I haven't tried to root a phone since my Incredible back in the day. Any help would be greatly appreciated.
Thanks!

Did you use TWRP to make a nandroid backup before attempting to root? If so, just restore it.
If not, you're going to have to either fastboot flash it back to stock. More info in the firmware thread.
Or you could give a custom rom, or this TWRP flashable stock rom a try. I've never used the TWRP flashable stock rom, but it might be an easy way out of your predicament if you aren't comfortable and familiar with fastboot and want to stay stock.
For future rooting attempts of the stock rom I'd recommend Magisk. It always works systemless, so there's no need to force it to install systemless like SuperSU. Just flash the zip in recovery and install the Magisk manager from the Play Store and you're rooted. No more soft bricks.

jason2678 said:
Did you use TWRP to make a nandroid backup before attempting to root? If so, just restore it.
If not, you're going to have to either fastboot flash it back to stock. More info in the firmware thread.
Or you could give a custom rom, or this TWRP flashable stock rom a try. I've never used the TWRP flashable stock rom, but it might be an easy way out of your predicament if you aren't comfortable and familiar with fastboot and want to stay stock.
For future rooting attempts of the stock rom I'd recommend Magisk. It always works systemless, so there's no need to force it to install systemless like SuperSU. Just flash the zip in recovery and install the Magisk manager from the Play Store and you're rooted. No more soft bricks.
Click to expand...
Click to collapse
Ok, first, thanks for the response.
I think somehow I didn't actually install TWRP. Not sure how.
I followed that thread link and tried everything, but to no avail. Maybe I was doing it wrong? I did this:
- Downloaded everything under "6.0 MPH24.49-18 FIRMWARE"
- Put it on my SD card
- Booted into recovery
- Selected Install from SD Card
And there was nothing listed. I tried the same with the "6.0 MPH24.49-18-3 FIRMWARE".
I also did the "AutoFlashFirmwareScript", but I'm assuming that didn't work since I can't turn on USB Debugging. Is there a possibility I somehow wiped the entire OS and there isn't anything to boot into?

bootloopohgod said:
Ok, first, thanks for the response.
I think somehow I didn't actually install TWRP. Not sure how.
I followed that thread link and tried everything, but to no avail. Maybe I was doing it wrong? I did this:
- Downloaded everything under "6.0 MPH24.49-18 FIRMWARE"
- Put it on my SD card
- Booted into recovery
- Selected Install from SD Card
And there was nothing listed. I tried the same with the "6.0 MPH24.49-18-3 FIRMWARE".
I also did the "AutoFlashFirmwareScript", but I'm assuming that didn't work since I can't turn on USB Debugging. Is there a possibility I somehow wiped the entire OS and there isn't anything to boot into?
Click to expand...
Click to collapse
okay so you are wrong here..
firmware needs to be flashed via fastboot they are not available in flashable zips they are .xml file.. you need to follow the instructions given here
https://forum.xda-developers.com/moto-x-style/development/firmware-moto-x-style-pure-stock-t3272486
or if you want latest firmware of any version of style or pure
download from here
https://firmware.center/firmware/Motorola/
and follow the same instructions given in the first link
hope this helps

Sagar_1401 said:
okay so you are wrong here..
firmware needs to be flashed via fastboot they are not available in flashable zips they are .xml file.. you need to follow the instructions given here
https://forum.xda-developers.com/moto-x-style/development/firmware-moto-x-style-pure-stock-t3272486
or if you want latest firmware of any version of style or pure
download from here
https://firmware.center/firmware/Motorola/
and follow the same instructions given in the first link
hope this helps
Click to expand...
Click to collapse
This definitely seems helpful, but when I tried it gave me a bunch of Failures.
For "fastboot flash partition gpt.bin":
Code:
fastboot flash partition gpt.bin
target reported max download size of 536870912 bytes
sending 'partition' (32 KB)...
OKAY [ 0.006s]
writing 'partition'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.382s
And then a Failure for every command from "fastboot flash boot boot.img" to "fastboot flash system system.img_sparsechunk.8" (the build I used doesn't have sparsechunk 9 or else I'd assume that would have been a failure as well). It is encouraging to know I can at least somewhat communicate with the phone, for some reason yesterday I couldn't even do that.

bootloopohgod said:
This definitely seems helpful, but when I tried it gave me a bunch of Failures.
For "fastboot flash partition gpt.bin":
Code:
fastboot flash partition gpt.bin
target reported max download size of 536870912 bytes
sending 'partition' (32 KB)...
OKAY [ 0.006s]
writing 'partition'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.382s
And then a Failure for every command from "fastboot flash boot boot.img" to "fastboot flash system system.img_sparsechunk.8" (the build I used doesn't have sparsechunk 9 or else I'd assume that would have been a failure as well). It is encouraging to know I can at least somewhat communicate with the phone, for some reason yesterday I couldn't even do that.
Click to expand...
Click to collapse
ignore that partition error
fastboot oem lock begin
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot flash system system.img_sparsechunk.8
fastboot flash system system.img_sparsechunk.9
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot oem lock
fastboot reboot
make sure
while flashing NON-HLOS.bin you might get error
dont worry
when you reach that step do type it again when you see that error and it'll successful flash the NON-HLOS.bin which is your main step for your modem
im sure this will 100% work
edit: all the files have different no of system system.img_sparsechunk
if you are flashin sept patch it should have 8 i assume but if you just type system system.img_sparsechunk.9 it'll say file not found u won't encounter any error by that

can only get into fastboot or TWRP

I am trying to flash Lineage OS, and from TWRP it appears to flash but now this Storm Kipper will not boot into Lineage.
From TWRP if I select power off it goes straight into Fastboot.
From Fastboot:-
Start: reboots and goes straight into fastboot
Restart bootloader: reboots and goes straight into fastboot
Power off: reboots and goes straight into fastboot
Recovery mode: goes to Team Win Recovery Project 3.1.0-0
I have a number of lineage-14.1-2017xxyy-nightly-kipper-signed.zip on a microSD card, and I have checked the SHA256 hashes and they match the ones on the website
Another oddity is that if I try and flash open_gapps it says wrong architecture, I have tried arm and arm64 and it makes no difference.
I have tried using the repair feature on System, Data and Cache and it seems to complete without issues but lineage still won't boot.
Can anyone advise? thanks

also I just tried the ADB sideload feature in TWRP (just to rule out the microSD card)
it appeared to work with a progress bar and at the end said "script succeeded", but when you select reboot it says "No OS installed! Are you sure you wish to reboot?"

ok people.
If I extract the boot.img from the LineageOS zip file and flash that using fastboot is that likely to make things better or worse?

Did you have success? I have the same problem...

Possible solution found!
dieselnutjob said:
ok people.
If I extract the boot.img from the LineageOS zip file and flash that using fastboot is that likely to make things better or worse?
Click to expand...
Click to collapse
I got my wf storm up and running again!
Look here -> reddit-forum for LineageOS

android_paul said:
I got my wf storm up and running again!
Look here -> reddit-forum for LineageOS
Click to expand...
Click to collapse
Thank you for this. I now also have Lineage 14.1 working.
The back button still doesn't illuminate though. I'm not sure if it's a bug or a hardware fault.
Anyway, as per the reddit post.
Download cm-13.1.5-ZNH2KAS7EC-kipper (fastboot).zip
unpack the zip file into a new folder
follow these instructions (I am using Linux)
Code:
cd ~/cm-13.1.5-ZNH2KAS7EC-kipper-fastboot/
fastboot flash aboot emmc_appsboot.mbn
fastboot erase DDR
fastboot flash sbl1 sbl1.mbn
fastboot flash tz tz.mbn
fastboot flash hyp hyp.mbn
fastboot flash rpm rpm.mbn
fastboot flash modem NON-HLOS.bin
fastboot flash cache cache.img
fastboot erase splash
fastboot flash splash splash.img
fastboot flash system system.img
fastboot flash recovery recovery.img
fastboot flash boot boot.img
fastboot reboot
This got it back to a working CM13.1
From here I went to bootloader mode and had a play with CM Recovery but didn't get on with it.
So I flashed on TWRP+3.1.0-0.img again.
This time it wouldn't pick up the microSD card, but adb sideload worked and that is how I installed lineage, su and gapps.
Thanks again.

Now that Lineage 14.1 is on TWRP can now see the microSD card.

dieselnutjob said:
...
The back button still doesn't illuminate though. I'm not sure if it's a bug or a hardware fault.
Click to expand...
Click to collapse
My led of the back button is off too. I'm afraid, it's a hardware issue. If my phone gets cold (using as a navigation tool on bike in winter....), the led begins to shine - until it's warm again. So this looks like an electrical (dis)connection problem.
There are bigger problems to imagine.

Can't flash twrp to Wileyfox Storm!
I can't install twrp of my Wileyfox Storm (I've tried several times)!
* I've unlocked the bootloader.
* I change to the directory where the twrp image is stored.
* I do <adb reboot bootloader>
* I do <fastboot flash recovery ./twrp-3.2.1-0-kipper-20180110.img>
I then get the message:
target reported max download size of 268435456 bytes
sending 'recovery' (26676 KB)...
OKAY [ 0.923s]
writing 'recovery'...
OKAY [ 0.339s]
finished. total time: 1.262s
* I then do <fastboot reboot>
The phone then reboots OK, but if I try to reboot to recovery I just get the 'vanilla' boot menu.
I'd be grateful for any help, please.
Jim

Phone stucks in fastboot

Hi guys,
i was on Miui Global 10.xxxx (dont know exactly)
bootloader was unlocked.
Rollback protection target was 1
my recovery was Orangefox recovery (https://forum.xda-developers.com/mi-9t/development/official-orangefox-recovery-project-t4037899)
I have made a full backup of all partitions before.
I wanted to flash Miui 11.0.4.0 global to flash a custom rom.
First i flashed recovery and installed the recovery.zip.
That worked fine.
Then i wanted to flash Miui 11.0.4.0 with this instructions for a clean flash:
1. If you're coming from another ROM or need to perform a clean flash:
Boot into Recovery
Wipe Data/Cache/System
Flash vendor/firmware (Global 11.0.4.0 recommended)
Flash ROM
(Optional) Flash Gapps (not included!)
(Optional) Flash the latest Magisk
Reboot
Enjoy
This instructions are from here: https://forum.xda-developers.com/mi-9t/development/rom-stagos-t4072637
So, i was in recovery, and deleted data, cache and system.
Then i restarted the phone to go to recovery, but that didnt work.
It stucked in bootloop.
I now reinstalled Adb and fastboot, and erased recovery and System partition.
There were much errors in time due old adb and fastboot version etc....
But now iam at this point here again.
wait for your answers how to continue.....
It looks like just flashing or booting recovery is not possible without system partition.

It's now too late and sorry I don't want to risk to give you the wrong instructions how to unbrick
But for the others to avoid similar brick:
1) You say you were on Global MIUI 10 and you wanted to update to MIUI 11.
If so, why didn't you simply update by OTA?
2) If for some reason you were not able to apply OTA, but if you were really on Global (not on custom ROM, Indian ROM or so) and wanted to update also to Global (not switching to EU weekly or so), then you shouldn't wipe anything
You had to flash the stock Recovery back, to download the Global recovery/zip package you wanted to update to, and to force update from System Update: (so called Local Update):
https://c.mi.com/oc/miuidownload/detail?guide=1
Now, once you wiped things and bricked, I don't know but you could check the Fastboot method:
https://c.mi.com/oc/miuidownload/detail?guide=2
If reading from mobile phone, force Desktop site in browser for the two links anove

1. When you make format data, than reboot in twrp again
2.when boot second time, wipe data, dalvick, cache, system...and flash new rom.
If you wipe system partition and reboot in twrp again without system, you get fastboot.

zgfg said:
It's now too late and sorry I don't want to risk to give you the wrong instructions how to unbrick
But for the others to avoid similar brick:
1) You say you were on Global MIUI 10 and you wanted to update to MIUI 11.
If so, why didn't you simply update by OTA?
2) If for some reason you were not able to apply OTA, but if you were really on Global (not on custom ROM, Indian ROM or so) and wanted to update also to Global (not switching to EU weekly or so), then you shouldn't wipe anything
You had to flash the stock Recovery back, to download the Global recovery/zip package you wanted to update to, and to force update from System Update: (so called Local Update):
https://c.mi.com/oc/miuidownload/detail?guide=1
Now, once you wiped things and bricked, I don't know but you could check the Fastboot method:
https://c.mi.com/oc/miuidownload/detail?guide=2
If reading from mobile phone, force Desktop site in browser for the two links anove
Click to expand...
Click to collapse
Sooo....after hours of reading with errors over errors and fixing, it still doesnt work.
First i tried to flash everything via mi flashtool.
There was an error: Antirollbackcheck Error.
https://www.reddit.com/r/Xiaomi/comments/d0xmbp/what_on_earth_is_miflash_antirollback_check_error/
https://xiaomi.eu/community/threads...nd-flashing-recovery-fails-please-help.51349/
To fix this i had to move the Tool and the rom into my C hard drive next to program etc folders...
Then i editet the flashall.bat file and removed the rollbackcheck lines.
Now after doing this, it flashed for 100 seconds, and then there was this error: Failed to flash dtbo.img
sooo....Then i tried to flash the dtbo.img and all the other ones via Minimal adb and fastboot.
https://forum.xda-developers.com/mi-9t/help/flash-stuck-fastboot-soft-brick-t3962662/page3
And this didnt work for me too. Everytime if i try to flash dtbo.img, this error comes:
target didnt report max-download-size
sending dtbo (32768KB)....
FAILED (command write failed (no error))
finished.
Now everything is like before....

Flash twrp and boot in twrp. After phone boot in twrp, make format data. After format, make reboot to recovery.
When booot in twrp, wipe data, dalvick, cache, system , copy Miroom to internal and flash ROM.
Use this twrp...
https://app.box.com/s/8lkfbft44vldtt0y8kwhe6un87b5ebzx
And this rom.
https://sourceforge.net/projects/mi...edmiK20_MIUI_20.3.26_MiRoom_10.0.zip/download
Sent from my MI 9T using Tapatalk

Kidence said:
Flash twrp and boot in twrp. After phone boot in twrp, make format data. After format, make reboot to recovery.
When booot in twrp, wipe data, dalvick, cache, system , copy Miroom to internal and flash ROM.
Use this twrp...
https://app.box.com/s/8lkfbft44vldtt0y8kwhe6un87b5ebzx
And this rom.
https://sourceforge.net/projects/mi...edmiK20_MIUI_20.3.26_MiRoom_10.0.zip/download
Sent from my MI 9T using Tapatalk
Click to expand...
Click to collapse
C:\Minimal ADB and Fastboot>fastboot flash recovery twrp-3.3.1-12-davinci-mauronofrio.img
target reported max download size of 805306368 bytes
sending 'recovery' (65536 KB)...
OKAY [ 1.914s]
writing 'recovery'...
OKAY [ 0.151s]
finished. total time: 2.065s
C:\Minimal ADB and Fastboot>fastboot boot recovery
error: cannot load 'recovery': No such file or directory
C:\Minimal ADB and Fastboot>fastboot boot twrp-3.3.1-12-davinci-mauronofrio.img
downloading 'boot.img'...
OKAY [ 1.891s]
booting...
FAILED (remote: Failed to load/authenticate boot image: Load Error)
finished. total time: 1.900s

When you flash recovery, hold volume up and type in adb
fastboot reboot
After that, phone will be boot in twrp
Sent from my MI 9T using Tapatalk

FINALLY it worked YES
FIRST: The Story for everybody who has the same problem like me:
Device: Xiaomi Mi 9T
Firmware: MIUI 10 GLOBAL
Antirollbackprotectioncounter: 1
Bootloader: Unlocked
Story:
At the beginning, everything was working, but i wanted to install a custom rom (STAGOS)
For this step, i had to Update my Miui firmware on 11.0.4.0.
But this step didnt work so well via device OTA (error), then i decided to install it via custom recovery.
I still had the stock recovery on my device, so i went in fastboot mode, and installed Orangefox recovery via ADB and Fastboot on Windows. That worked without problems.
In Orangefox, i wiped as sayed in instructions data, cache and System. then i rebooted.
But before realised that was the wrong way, i stucked in fastboot.
No tools helped. ADB and Fastboot didnt work as seen in screenshots.
I tried everything via fastboot....
fastboot flash recovery XXX.img
fastboot boot XXXX.img
Fastboot format.....etc
But NOTHING worked. Everytime there were the following errors:
Target didnt report Max download size
Error: Cannot load recovery
No such file or directory
Error: Download size is higher that allowed
Failed to load boot image (Load error)
Command write failed (no error)
and some other ones too.....
It looked like, some flashes worked and some not. Sometimes it worked, sometimes not.
After some new tries it just showed via the command: Fastboot devices
????????? fastboot
That problem has been solved. Just unplug the device and wait for 10 minutes until it shuts down automatically.
If that doesnt work, you can try to replug it to pc some times again.
It looked like replugging and using different USB Port (one user solved the problem via USB 2.0) helps to get a better connection and prevent errors.
Then i tried some tools, for example android all in one tool, but no one worked.
After this, i reinstalled the driver and installed MI Flash tool (https://mi-globe.com/download-xiaomi-mi-flash-tool-all-versions/)
It looks like there are some mi flash tools around here which are not working right, but THIS one worked for me.
After installing, i connected my device, choosed the fastboot firmware (.tgz), unpacked it and choosed the right location in mi Flash tool.
Firmware files are find here: https://c.mi.com/oc/miuidownload/detail?guide=2
(You should check you Antirollback counter before to avoid a brick. Here you find some informations: https://www.xda-developers.com/xiaomi-anti-rollback-protection-brick-phone/)
DONT FORGET TO CHOOSE IN THE RIGHT DOWN CORNER: CLEAN ALL !!! (normally, clean all and lock is choosen, but that bricks your device)
After doing this, i started flashing, but there was an error: Antirollbackcheck error.
I solved it via moving the mi flashtool directly into my C hard drive, and deleted some lines in the flashall.bat, as seen in post history here.
Then....it worked for some seconds longer, but than: Error: Failed to flash dtbo.img
So i tried it via ADB and Fastboot. But nothing changed.
Then i tried flashing via mi Flash tool again, and this time the following error comes: Failed to flash system.img.
After this is thought: hmmm....something is very wrong with this device....lets try again, after a device restart.
So i tried again, let it running for ~360 seconds, and IT WORKED!
At the End: there was the following error: Error: Not catch checkpoint.
But this error (you can also see in a screenshot) it not necessary.
This is the result of removing some lines in flashall.bat.
After this my phone successfully booted im Miui 11.

[ROM][STOCK][FASTBOOT][OP8] Stock Fastboot ROMs for OnePlus 8

Things are changing with the advent of project treble and seamless updates. OnePlus will no longer release ROMs flashable via recovery (either stock) 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 8 in fastboot-bootloader mode (Power and volume + and volume-);
Connect the OnePlus 8 to PC;
Run flash-all.bat flasher you need;
Wait until the process end;
The phone will automatically reboot.
DOWNLOAD
All roms on Sourceforge: https://sourceforge.net/projects/fastbootroms/files/OnePlus 8
BRANDED PHONE
For now branded device are not supported
MANUAL FLASH: Windows - OSX - Linux
If you want to manual flash these roms these are the commands (You need the latest sdk platform tools, you can find it here
Is reccomended to format data or the rom cannot boot:
Code:
fastboot -w
Others Commands to flash a fastboot rom
Code:
fastboot flash aop aop.img
fastboot flash bluetooth bluetooth.img
fastboot flash boot boot.img
fastboot flash dsp dsp.img
fastboot flash dtbo dtbo.img
fastboot flash LOGO LOGO.img
fastboot flash modem modem.img
fastboot flash oem_stanvbk oem_stanvbk.img
fastboot flash qupfw qupfw.img
fastboot flash storsec storsec.img
fastboot flash multiimgoem multiimgoem.img
fastboot flash uefisecapp uefisecapp.img
fastboot flash recovery recovery.img
fastboot --disable-verity flash vbmeta vbmeta.img
fastboot --disable-verity flash vbmeta_system vbmeta_system.img
fastboot flash opproduct opproduct.img
fastboot reboot fastboot
fastboot flash system system.img
fastboot flash vendor vendor.img
fastboot flash product product.img
fastboot reboot
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.
If the device automatically reboot in Stock Recovery mode don't reboot it and wait the flash end.
These ROMs can't be used to update or downgrade your phone but just to restore your phone.
If the rom seems doesn't start go in recovery stock and follow this guideline: English -> Wipe data and cache -> Erase everything.
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/
If you got some problems like write error or no partition, check this: https://forum.xda-developers.com/showpost.php?p=76658555&postcount=34
DONATE LINK
If you want to support this and others my projects please consider making a donation, thanks.
​

Branded devices is for example a Chinese version with HydrogenOS to which OxigenOS has been installed? If so, how can a branded device be recovered?
Thanks

Hi guys, i'm here again to ask for your support, actually with android 10 Google introduced a lot of changing, from dynamic partitions to the new keymaster 4 encryption/decryption. Teamwin is working hard to update TWRP but they will still take some time. Currently some things already work but there are difficulties in bringing them to the OnePlus 8/8 Pro, for example decryption already works but creates some problems on the OnePlus devices. That's why I decided to create a Paypal moneybox to be able to bring you the latest updates in the shortest time possible. As I have previously done, I assure you of a support of at least 2 years (within the limits of my possibilities). In addition to the TWRP I will improve the fastboot roms and add OnePlus 8/8 Pro to my TOOL ALL IN ONE (and maybe I will also bring the RevengeOS). By getting hold of a OnePlus 8 or 8 Pro I will also be able to improve the TWRP for OnePlus 7T and 7T Pro.
OnePlus 8/8 Pro PayPal MoneyBox: https://www.paypal.com/pools/c/8pfrIOL3Qa
If you are unable to participate in the PayPal moneybox, you can make a normal donation (perhaps specifying that it is for the moneybox), however all private donations that I will receive for this or other projects will be included in the moneybox.
Private PayPal Donations: https://www.paypal.me/MauronofrioTool

Why after flash it, it boot up to Qualcomm crashdump mode and how to fix?

sakun-ice said:
Branded devices is for example a Chinese version with HydrogenOS to which OxigenOS has been installed? If so, how can a branded device be recovered?
Thanks
Click to expand...
Click to collapse
I think unbranded devices mean the device bought from T-Mobile or Verizon. Nothing to do with chinese versiion flash oxygenOS, if I'm not wrong.

Can't seem to get this to work. I'm trying to flash a stock rom for my OnePlus 8 after bricking it during a rooting process.
The device' bootloader is obviously unlocked and i can get the phone into Fastboot mode and connected to my PC.
The only issue is when i execute the flash-all.bat file, it can't seem to flash any of the files and gives an error consisting of the message "FAILED (remote: 'Flashing is not allowed for Critical Partitions').
What to do guys? Can anyone help me out.

Does anyone know where to find mobile oneplus 8 5g tmobile from mine is bricked I had same error as post above

KJStar said:
Can't seem to get this to work. I'm trying to flash a stock rom for my OnePlus 8 after bricking it during a rooting process.
The device' bootloader is obviously unlocked and i can get the phone into Fastboot mode and connected to my PC.
The only issue is when i execute the flash-all.bat file, it can't seem to flash any of the files and gives an error consisting of the message "FAILED (remote: 'Flashing is not allowed for Critical Partitions').
What to do guys? Can anyone help me out.
Click to expand...
Click to collapse
Try to flash fastboot rom with "tool all in one),It worked for me.

I needed modem I forgot to fastboot reboot fastboot guy in post 6 that's all you need to do is reboot fastboot then flash all I was looking for different file

Never mind I fixed it by downloading ota and going to system updates in settings because fastboot won't flash to modem right

I am having issues flashing. flashing not allowed on critical partition. please help I tried to use the large address aware program but nothing has changed.

bluemoel said:
I am having issues flashing. flashing not allowed on critical partition. please help I tried to use the large address aware program but nothing has changed.
Click to expand...
Click to collapse
Make sure your on the latest update: 10.5.8

mauronofrio said:
Things are changing with the advent of project treble and seamless updates. OnePlus will no longer release ROMs flashable via recovery (either stock) 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 8 in fastboot-bootloader mode (Power and volume + and volume-);
Connect the OnePlus 8 to PC;
Run flash-all.bat flasher you need;
Wait until the process end;
The phone will automatically reboot.
DOWNLOAD
All roms on Sourceforge: https://sourceforge.net/projects/fastbootroms/files/OnePlus 8
BRANDED PHONE
For now branded device are not supported
MANUAL FLASH: Windows - OSX - Linux
If you want to manual flash these roms these are the commands (You need the latest sdk platform tools, you can find it here
Is reccomended to format data or the rom cannot boot:
Code:
fastboot -w
Others Commands to flash a fastboot rom
Code:
fastboot flash aop aop.img
fastboot flash bluetooth bluetooth.img
fastboot flash boot boot.img
fastboot flash dsp dsp.img
fastboot flash dtbo dtbo.img
fastboot flash LOGO LOGO.img
fastboot flash modem modem.img
fastboot flash oem_stanvbk oem_stanvbk.img
fastboot flash qupfw qupfw.img
fastboot flash storsec storsec.img
fastboot flash multiimgoem multiimgoem.img
fastboot flash uefisecapp uefisecapp.img
fastboot flash recovery recovery.img
fastboot --disable-verity flash vbmeta vbmeta.img
fastboot --disable-verity flash vbmeta_system vbmeta_system.img
fastboot flash opproduct opproduct.img
fastboot reboot fastboot
fastboot flash system system.img
fastboot flash vendor vendor.img
fastboot flash product product.img
fastboot reboot
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.
If the device automatically reboot in Stock Recovery mode don't reboot it and wait the flash end.
These ROMs can't be used to update or downgrade your phone but just to restore your phone.
If the rom seems doesn't start go in recovery stock and follow this guideline: English -> Wipe data and cache -> Erase everything.
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/
If you got some problems like write error or no partition, check this: https://forum.xda-developers.com/showpost.php?p=76658555&postcount=34
DONATE LINK
If you want to support this and others my projects please consider making a donation, thanks.
​
Click to expand...
Click to collapse
Hi, do you know if patching with local update a Oxygen OS Europe release from a Global release may cause problems to the fingerprint? I have a IN2010 with the Global OxygenOS but I would like to switch to the European versione becasue I live in Italy like you

Why not flash reserve.img?

nnyd said:
Why not flash reserve.img?
Click to expand...
Click to collapse
Because it is placed in userdata and not in a dedicated partition

I have an issue trying to flash on fastboot. It's says I can't flash on critical partitions. Yes I know alot of people are saying that but what I haven't seen is this:
This is my problem:
Fastboot get device-info
(Bootloader) device unlocked:true
(Bootloader) device critical unlock: false
(Bootloader) charger screen enabled: true
I have already tried "fastboot flashing unlock_critical"
It says bootloader already unlocked. I then re lock bootloader which I know is not a good idea( reflash stock with msm tool) and it lock then I try unlock critical command again and it still says device critical unlock: false

i need help please ..
i tried this method not the latest version i tried the 10.5.4 global
so it gave me all failed and error to foramt and others
then it restart my phone to show me crashdump
what should i do ?
should i use latest version ?
i hope you replay fast .. thank you

Alucardo1 said:
i tried this method not the latest version i tried the 10.5.4 global
so it gave me all failed and error to foramt and others
then it restart my phone to show me crashdump
what should i do ?
should i use latest version ?
i hope you replay fast .. thank you
Click to expand...
Click to collapse
Try again with 10.5.7. When it reboot to recovery, let it continue to run till it reboots on its own.

Unbrick from fastboot method
I hope I can help someone since I spent the whole night trying various methods to unbrick my Oneplus 8 and only this one worked for me JUST FOR INTERNATIONAL VERSION
You must have the drivers installed (Adb & Fastboot)
You must have your phone with the bootloader unlocked
1.- Download the file
2.-Unzip it
inside you will find Flash-all.bat
3.-Enter Fastboot mode
4.-Double click on the Flash-all.bat command
5.-It will direct you to the recovery, select the English language and restart in fastboot mode so that the process continues, wait for it to finish flashing everything and ready, the phone restarts on the latest version
https://mega.nz/folder/8tpUSSrR#7wH4NX_ccr2a6Ub8LXpsEA
Donate Link to support my work
https://paypal.me/pakomorales?locale.x=es_XC

cannot relock bootloader on oneplus 8
bro thanks for fastboot room for oneplus 8,i flash your fastboot room 10.5.9 everthing ok,but i relocked to boot loader it the phone be correpted. what should i do ,
please help me.

having some trouble flashing the magisk patched image

(edit: is my device bricked? it won't load Android now, but is in fastboot
also should i have updated Android first?
i'm thinking of keeping it stock at this point, or maybe finish rooting if possible.)
copied below is what i put in Command Prompt
and then tried downloading adb and fastboot again
i downloaded a fresh factory image for my version
and followed these instructions
How to root the Google Pixel 4 or Pixel 4 XL with Magisk
Looking to root your Google Pixel 4 or Pixel 4 XL? Here's how to unlock the bootloader and root the latest 2019 Pixel smartphones!
www.xda-developers.com
here's what i did:
fastboot flash boot "C:\path\magisk_patched-25200_NVE3j.img"
target reported max download size of 268435456 bytes
sending 'boot' (65536 KB)...
OKAY [ 2.199s]
writing 'boot'...
FAILED (remote: Failed to write to partition Not Found)
finished. total time: 2.348s
adb reboot bootloader
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
error: device '(null)' not found
C:\adb>
C:\adb>fastboot reboot fastboot
usage: fastboot [ <option> ] <command>
commands:
then i got the latest platform-tools, because i had installed some other ADB and Fastboot from XDA in an installer with some Google Drivers.
fastboot flash boot "C:\path\magisk_patched-25200_NVE3j.img"
Sending 'boot_a' (65536 KB) OKAY [ 2.355s]
Writing 'boot_a' (bootloader) Image missing OS version
OKAY [ 0.424s]
Finished. Total time: 3.129s
I also downloaded drivers from Google but i'm not sure how to install the DLL file until the device is out of Fastboot?
I tried using the menu to boot to Recovery. Didn't work.
In Device Manager, should i select Android Bootloader Interface to update to this driver?
Or wait until i can select it as a normal Android device after if it's possible to boot it normally?
And what about the website Flash.Android.com? could that get me to stock safely? but not rooted.

Sanman99 said:
copied below is what i put in Command Prompt
and then tried downloading adb and fastboot again
i downloaded a fresh factory image for my version
and followed these instructions
How to root the Google Pixel 4 or Pixel 4 XL with Magisk
Looking to root your Google Pixel 4 or Pixel 4 XL? Here's how to unlock the bootloader and root the latest 2019 Pixel smartphones!
www.xda-developers.com
here's what i did:
fastboot flash boot "C:\path\magisk_patched-25200_NVE3j.img"
target reported max download size of 268435456 bytes
sending 'boot' (65536 KB)...
OKAY [ 2.199s]
writing 'boot'...
FAILED (remote: Failed to write to partition Not Found)
finished. total time: 2.348s
Click to expand...
Click to collapse
If the next thing you did was
Sanman99 said:
adb reboot bootloader
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
error: device '(null)' not found
Click to expand...
Click to collapse
then ADB wasn't running. Use fastboot devices to ensure your PC sees your phone before flashing
Sanman99 said:
C:\adb>
C:\adb>fastboot reboot fastboot
usage: fastboot [ <option> ] <command>
commands:
Click to expand...
Click to collapse
Correct syntax is adb reboot fastboot/bootloader/recovery
The way it works is like this:
Code:
<tool> <command> <instruction> <options>
where:
<tool> is what you are instructing to send the command to the device: ADB for Android system or recovery, fastboot for bootloader or fastbootd
<command> is what you want the device to do, i.e.: devices / reboot / flash / boot / erase / etc:
devices tells the tool to display connected ADB devices
reboot tells the device to reboot, can provide instruction for what mode you want it to reboot into, example: adb [B]reboot [/B]bootloader
flash can only be used in fastboot, tells the bootloader to flash the specified partition with the specified image, example: fastboot [B]flash [/B]boot <path to boot image
boot tells bootloader to immediately load the specified image without flashing, example: fastboot [B]boot [/B]TWRP.img
erase tells the bootloader to wipe the device; if no partition is specified, this will wipe user data. Use with extreme caution. Example: fastboot [B]erase [/B]data
<instruction> is the details for the command you're giving: adb reboot bootloader, fastboot flash boot <path to image>, fastboot boot <path to image>
<options> include details that may be necessary for various operations, example: fastboot update image-redfin-buildnumber.zip -w --skip-reboot --slot=all --force (this tells the bootloader to update using the specified update package, to wipe data, to not automatically reboot when done flashing, to flash both slots, and to ignore any baseband/bootloader requirements
<option> and <command> can be switched, for example: fastboot --skip-reboot --slot=all --force -w update image-redfin-buildnumber.zip
Sanman99 said:
then i got the latest platform-tools, because i had installed some other ADB and Fastboot from XDA in an installer with some Google Drivers.
fastboot flash boot "C:\path\magisk_patched-25200_NVE3j.img"
Sending 'boot_a' (65536 KB) OKAY [ 2.355s]
Writing 'boot_a' (bootloader) Image missing OS version
OKAY [ 0.424s]
Finished. Total time: 3.129s
Click to expand...
Click to collapse
It's always important to make sure you're using the latest ADB platform tools.
What happened after you successfully flashed the patched image?

V0latyle said:
If the next thing you did was
then ADB wasn't running. Use fastboot devices to ensure your PC sees your phone before flashing
Correct syntax is adb reboot fastboot/bootloader/recovery
The way it works is like this:
Code:
<tool> <command> <instruction> <options>
where:
<tool> is what you are instructing to send the command to the device: ADB for Android system or recovery, fastboot for bootloader or fastbootd
<command> is what you want the device to do, i.e.: devices / reboot / flash / boot / erase / etc:
devices tells the tool to display connected ADB devices
reboot tells the device to reboot, can provide instruction for what mode you want it to reboot into, example: adb [B]reboot [/B]bootloader
flash can only be used in fastboot, tells the bootloader to flash the specified partition with the specified image, example: fastboot [B]flash [/B]boot <path to boot image
boot tells bootloader to immediately load the specified image without flashing, example: fastboot [B]boot [/B]TWRP.img
erase tells the bootloader to wipe the device; if no partition is specified, this will wipe user data. Use with extreme caution. Example: fastboot [B]erase [/B]data
<instruction> is the details for the command you're giving: adb reboot bootloader, fastboot flash boot <path to image>, fastboot boot <path to image>
<options> include details that may be necessary for various operations, example: fastboot update image-redfin-buildnumber.zip -w --skip-reboot --slot=all --force (this tells the bootloader to update using the specified update package, to wipe data, to not automatically reboot when done flashing, to flash both slots, and to ignore any baseband/bootloader requirements
<option> and <command> can be switched, for example: fastboot --skip-reboot --slot=all --force -w update image-redfin-buildnumber.zip
It's always important to make sure you're using the latest ADB platform tools.
What happened after you successfully flashed the patched image?
Click to expand...
Click to collapse
thanks for the quick reply
and extensive yet clear
Yes i did: Fastboot Devices
and it shows the serial number
So when i tried flashing
It didn't flash though, did it? Does that look like it flashed?
When it took 2 or 3 seconds for a 64megabyte file from my computer, isn't on the phone itself.
And said: Image missing OS version
I checked online and other users have the same problem.
I'm stuck in Fastboot. I'm downloading Android SDK Studio and updated the USB Driver again.
I can't get into Recovery or the OS.
Enter reason: error boot prepare
when trying Recovery
I'm wondering if I should get GrapheneOS or if LineageOS is up to date on Pixel 4. I might not want to tinker as much anymore. I still might use the usual apps, but at least utilize root.
Should i be using a different USB cable/cord maybe?
I don't know if I have an OEM USB-c.

Sanman99 said:
thanks for the quick reply
and extensive yet clear
Yes i did: Fastboot Devices
and it shows the serial number
So when i tried flashing
It didn't flash though, did it? Does that look like it flashed?
Click to expand...
Click to collapse
When it says OKAY, that means it successfully flashed.
Sanman99 said:
When it took 2 or 3 seconds for a 64megabyte file from my computer, isn't on the phone itself.
And said: Image missing OS version
I checked online and other users have the same problem.
Click to expand...
Click to collapse
What version of Magisk are you using and where did you download it from?
You are using boot.img, not bootloader.img, right?
You're using the correct firmware for your phone (flame)?
Sanman99 said:
I'm stuck in Fastboot. I'm downloading Android SDK Studio and updated the USB Driver again.
I can't get into Recovery or the OS.
Enter reason: error boot prepare
when trying Recovery
Click to expand...
Click to collapse
It's starting to sound like you might be using the wrong image. Try reflashing the stock boot image (unpatched).
Sanman99 said:
I'm wondering if I should get GrapheneOS or if LineageOS is up to date on Pixel 4. I might not want to tinker as much anymore. I still might use the usual apps, but at least utilize root.
Click to expand...
Click to collapse
One step at a time, I think fixing this should be pretty easy.
Sanman99 said:
Should i be using a different USB cable/cord maybe?
I don't know if I have an OEM USB-c.
Click to expand...
Click to collapse
It's worth a try. Are you using a USB A to C cable, or just C to C? If you're using a C to C cable, try using A to C.
Also, I don't know if you've noticed, but I do have a guide for rooting your device here. Check out the "Initial Root" section to make sure you're doing everything right.

V0latyle said:
When it says OKAY, that means it successfully flashed.
What version of Magisk are you using and where did you download it from?
You are using boot.img, not bootloader.img, right?
You're using the correct firmware for your phone (flame)?
It's starting to sound like you might be using the wrong image. Try reflashing the stock boot image (unpatched).
One step at a time, I think fixing this should be pretty easy.
It's worth a try. Are you using a USB A to C cable, or just C to C? If you're using a C to C cable, try using A to C.
Also, I don't know if you've noticed, but I do have a guide for rooting your device here. Check out the "Initial Root" section to make sure you're doing everything right.
Click to expand...
Click to collapse
tried the (unpatched) factory boot image now
with a different USB cable (both are USB-A to USB-C)
C:\path>fastboot flash boot "C:\path\oriole-tp1a.221005.002-factory-f28b656e\oriole-tp1a.221005.002\image-oriole-tp1a.221005.002\boot.img"
Sending 'boot_a' (65536 KB) OKAY [ 1.627s]
Writing 'boot_a' (bootloader) Image missing OS version
OKAY [ 0.506s]
Finished. Total time: 2.465s
Yes i followed the steps
Here is what i originally did
Yes i downloaded a Magisk apk from the guide I mentioned which links to Github
and i updated the app after opening it
then patched the Boot.img and copied to my computer
I'm reading your thread now, which directed to this
[GUIDE] Pixel 4 "flame": Unlock Bootloader, Update, Root, Pass SafetyNet
If you are looking for my guide on a different Pixel, find it here: Pixel 3 Pixel 3XL Pixel 3a Pixel 3aXL Pixel 4XL Pixel 4a Pixel 4a (5G) Pixel 5 Pixel 5a Pixel 6 Pixel 6 Pro For best results, use the latest stable Magisk release. Discussion...
forum.xda-developers.com
Yes i downloaded the correct Factory image
I had enabled USB Debugging
and
yep i did the
fastboot flashing unlock
and this is where the problem happened
(well unrelated, i didn't rename the patched-boot.img)
fastboot flash boot <drag and drop master root.img here>
as i copied the output...it took like 2 seconds and gave that message saying something about the OS version
and i can't get ADB working...
Should I have used the PixelFlasher tool?
I don't know what went wrong or what to do now. As I said, some others have had this same error.
i just tried again with fastboot from the SDK directory
C:\Users\path\AppData\Local\Android\Sdk\platform-tools>fastboot flash boot "C:\Users\path\Downloads\oriole-tp1a.221005.002-factory-f28b656e\oriole-tp1a.221005.002\image-oriole-tp1a.221005.002\boot.img"
Sending 'boot_a' (65536 KB) OKAY [ 1.617s]
Writing 'boot_a' (bootloader) Image missing OS version
OKAY [ 0.491s]
Finished. Total time: 2.457s

It's hard to say exactly where you're going wrong. Did you mess with vbmeta at all? You should get no error messages when flashing the original boot image.
Have you tried to boot even after getting the error message?
Pixel Flasher is useful, but it's very important that you understand how everything works under the hood, because the tool just automates what we'd otherwise have to manually do, and the tool can't necessary fix problems.

V0latyle said:
It's hard to say exactly where you're going wrong. Did you mess with vbmeta at all? You should get no error messages when flashing the original boot image.
Have you tried to boot even after getting the error message?
Pixel Flasher is useful, but it's very important that you understand how everything works under the hood, because the tool just automates what we'd otherwise have to manually do, and the tool can't necessary fix problems.
Click to expand...
Click to collapse
(edit: you were right. it wasn't the right Flame image at all. it was Oriole.)
i don't know what vbmeta is.
I can't boot into anything but fastboot.
If I go on the Flash.Android.com website, should i flash to Android 12?
wait...what if it wasn't a Pixel 4 image
is there another that has tp1a.221005.002 ?
how can i check which one this is?
i know you said check if it says Flame
i know i was in the list for Pixel 4 flame when i was about to download
but i typed Ctrl+F and to search the right code
this is what i downloaded
https://dl.google.com/dl/android/aosp/oriole-tp1a.221005.002-factory-f28b656e.zip
---
ok.... here's Flame
https://dl.google.com/dl/android/aosp/flame-tp1a.221005.002-factory-f91d46b5.zip
so i just have to flash the Boot.img from this
and then patch it again, right?

Sanman99 said:
(edit: you were right. it wasn't the right Flame image at all. it was Oriole.)
Click to expand...
Click to collapse
Yeah, that's a pretty common problem.
Sanman99 said:
i don't know what vbmeta is.
Click to expand...
Click to collapse
Don't worry about it
Sanman99 said:
I can't boot into anything but fastboot.
Click to expand...
Click to collapse
Do you mean bootloader? What do you see on the screen? Any error message at the bottom?
Sanman99 said:
If I go on the Flash.Android.com website, should i flash to Android 12?
Click to expand...
Click to collapse
Just update to the latest version, if you haven't already.
Sanman99 said:
wait...what if it wasn't a Pixel 4 image
is there another that has tp1a.221005.002 ?
Click to expand...
Click to collapse
Yes - since the Pixel 3, Google has started using what are called common system images, where the core system build is exactly the same across the entire range of phones. That makes updates much easier, because instead of having to rebuild firmware every month with the source Android update, they can just update the system image, while device specific partitions such as /product, /system_ext, /vendor_boot etc can be updated periodically.
The downside to this is that the updates can be confusing...because the build number is almost exactly the same for every phone, from the Pixel 7 all the way down through the Pixel 4a (since the 4 / 4XL are no longer supported)
As an example, the latest 4a build number is TQ1A.230105.001, and it's exactly the same for the 4a 5g, 5, 5a, and 6a. The Pixel 6, and 6 Pro are TQ1A.230105.002, and the 7 / 7 Pro are TQ1A.230105.001.A2. So there's minor differences there but for the most part the system images are very similar.
Sanman99 said:
how can i check which one this is?
i know you said check if it says Flame
Click to expand...
Click to collapse
As long as it's for the Pixel 4 (flame) it should be OK. The factory images are named in this fashion: device-buildnumber-factory-hash.zip, so yours should be flame-TP1A.221005.002-factory-f91d46b5.zip
Sanman99 said:
i know i was in the list for Pixel 4 flame when i was about to download
but i typed Ctrl+F and to search the right code
this is what i downloaded
https://dl.google.com/dl/android/aosp/oriole-tp1a.221005.002-factory-f28b656e.zip
Click to expand...
Click to collapse
Yeah that's the wrong one
Sanman99 said:
ok.... here's Flame
https://dl.google.com/dl/android/aosp/flame-tp1a.221005.002-factory-f91d46b5.zip
Click to expand...
Click to collapse
Yep
Sanman99 said:
so i just have to flash the Boot.img from this
Click to expand...
Click to collapse
Yes. Just to make absolutely sure we are on the same page, when you download the file, you'll have the original zip (using barbet for my wife's phone as an example)
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Extract this to its own folder, which will have another folder inside it with the bootloader image, radio image, scripts, and the system update:
Extract the "image-sunfish.tp1a.221005.002.zip" to its own folder:
In this folder will be the various images for the system update; the one you need is boot.img:
To get running again without root, just flash this:
fastboot flash boot <drag and drop the boot.img here>
Sanman99 said:
and then patch it again, right?
Click to expand...
Click to collapse
Yep...once you're booted into Android, copy the same boot.img to your phone, making sure to delete any old ones, then patch it in Magisk, copy the magisk-patched_25200-xxxxx.img back to your PC, then flash it the same way you did the boot image.

V0latyle said:
Yeah, that's a pretty common problem.
Don't worry about it
Do you mean bootloader? What do you see on the screen? Any error message at the bottom?
Just update to the latest version, if you haven't already.
Yes - since the Pixel 3, Google has started using what are called common system images, where the core system build is exactly the same across the entire range of phones. That makes updates much easier, because instead of having to rebuild firmware every month with the source Android update, they can just update the system image, while device specific partitions such as /product, /system_ext, /vendor_boot etc can be updated periodically.
The downside to this is that the updates can be confusing...because the build number is almost exactly the same for every phone, from the Pixel 7 all the way down through the Pixel 4a (since the 4 / 4XL are no longer supported)
As an example, the latest 4a build number is TQ1A.230105.001, and it's exactly the same for the 4a 5g, 5, 5a, and 6a. The Pixel 6, and 6 Pro are TQ1A.230105.002, and the 7 / 7 Pro are TQ1A.230105.001.A2. So there's minor differences there but for the most part the system images are very similar.
As long as it's for the Pixel 4 (flame) it should be OK. The factory images are named in this fashion: device-buildnumber-factory-hash.zip, so yours should be flame-TP1A.221005.002-factory-f91d46b5.zip
Yeah that's the wrong one
Yep
Yes. Just to make absolutely sure we are on the same page, when you download the file, you'll have the original zip (using barbet for my wife's phone as an example)
View attachment 5812273
Extract this to its own folder, which will have another folder inside it with the bootloader image, radio image, scripts, and the system update:
View attachment 5812283
Extract the "image-sunfish.tp1a.221005.002.zip" to its own folder:
View attachment 5812285
In this folder will be the various images for the system update; the one you need is boot.img:
View attachment 5812289
To get running again without root, just flash this:
fastboot flash boot <drag and drop the boot.img here>
Yep...once you're booted into Android, copy the same boot.img to your phone, making sure to delete any old ones, then patch it in Magisk, copy the magisk-patched_25200-xxxxx.img back to your PC, then flash it the same way you did the boot image.
Click to expand...
Click to collapse
yeah yeah sorry i didn't reply
and thanks so much for the explanation
i was busy setting up my phone
but realized GrapheneOS isn't supposed to have root anyways
so now i have to decide if I want a custom ROM or just Stock with root, or maybe GrapheneOS and whether to put Google services on it and a bunch of apps defeating its purpose in some ways
flashing the phone went very smoothly. Then i put GrapheneOS on it.
if you have any advice about which ROM to do, i'd appreciate it
lots of features are built into Stock now anyways
in that case, i'd just reflash the Magisk patched boot image and then lock the bootloader in settings again?
or i have to reinstall Stock entirely
maybe Android Flash Tool and not that Flash.Android.com
i've done this for multiple phones over the years but i guess i've never understood it thoroughly
i can check for a guide....(and follow it carefully lol)
awesome help. this saved me a bit of stress today.

Never ever lock the bootloader unless everything is 100% bone stock. Not even a patched image. If anything is modified, locking the bootloader will prevent the device from booting Android, and it may not be possible to unlock it again. I'll have more for you on ROMs in the morning, specifically GSIs.

V0latyle said:
Never ever lock the bootloader unless everything is 100% bone stock. Not even a patched image. If anything is modified, locking the bootloader will prevent the device from booting Android, and it may not be possible to unlock it again. I'll have more for you on ROMs in the morning, specifically GSIs.
Click to expand...
Click to collapse
Or I think I got that confused with the Settings menu OEM Unlock
Not the fastboot command.
I just did whatever the GrapheneOS instructions said.

Sanman99 said:
Or I think I got that confused with the Settings menu OEM Unlock
Not the fastboot command.
I just did whatever the GrapheneOS instructions said.
Click to expand...
Click to collapse
Well, GrapheneOS sets a custom root of trust, so as long as nothing is modified, you can relock the bootloader. You won't be able to have root, though. I generally advise against locking the bootloader unless you're on bone stock firmware.
As for ROMs, I don't have a lot of experience with custom ROMs, especially not in the past 6 years or so. My daily is a Pixel 5, and I'm pretty happy with the OEM firmware. I do have a Samsung tablet that I'm running an AOSP Developer Preview GSI on; I had tried LineageOS first, didn't like it that much, then figured out how to install a GSI. The Pixel 3 and newer should be Project Treble compliant, so you could potentially use a GSI if you wanted.
By the way, GSI = Generic System Image. The idea is that it can run on almost any device, utilizing the stock kernel, and does not require porting or any other customizations to get it to run on other devices.