Database Users

MX4 bootloop brick after trying to update I firmware on A phone

SOLVED:
Hi,
I just bricked my MX4 after trying to update system image from 4.5.6 to 4.5.7 using this guide:
Extract I version update.zip
use sdat2img to create system image
dd system image to system partition on live phone and reboot.
I used the same procedure successfully before, x-updating 4.5.4A ti I then updating to 4.5.6I.
After updating to 4.5.7, the phone goes into an infinite loop of Meizu splash screen, Flyme balloon, reboot.
I can enter fastboot and official recovery, but can't flash any partition from fastboot.
The bootloader is still locked.
Does anyone have any advice for unbricking?
Update:
The bootloop suddenly froze up for long enough for me to use adb to push an update.zip to the "sdcard" root. Have now flashed 4.2.8A from recovery and booted the phone.
As I had to clear all data I will unlock bootloader before trying anything else.

Try do flash 4.2.8.2 with uboot.img modded (to reunlock bootloader) and reboot fastboot and tell me

bobslesbricoleurs said:
Try do flash 4.2.8.2 with uboot.img modded (to reunlock bootloader) and reboot fastboot and tell me
Click to expand...
Click to collapse
Hi,
I managed to push 4.2.8.2 to sdcard then do a normal recovery reflash.
Have now successfully unlocked using the .apk method.
Now I need to find out if I can use that unlocked bootloader to flash recent "I" firmwares, or if I can only flash the unfinished cyanogen (would like to wait 'til that's a bit more polished before using it.
Anyway. Happy to have my phone back!

Maybe that newest 4.5.7I need a new kernel so you'll need to update to 4.5.7A before flashing system.img or you can flash directly 4.5.7I but you'll need to use fastboot flash boot boot.img
If a rom/firmware needs a specific kernel it'll bootloop if you don't flash it

Can I flash 4.5.7 I now that I have unlocked bootloader and custom recovery? If I understand the unlock threads correctly, I think I will relock the bootloader, or even brick if I try to flash the complete update.zip. Can I flash system and boot partitions using fastboot?

Fully BRICKED.
Now I FULLY bricked it (no more recovery).
Had successfully upgraded to 4.5.7 "I" and was installing super su for full root, before disabling update, but had forgotten that I still had official 4.2.8 rom as update.zip on "sdcard" root.
rebooted to TWRP recovery for full su install and recovery found the update.zip and flashed it.
Result: Bootloop, No recovery, locked fastboot, no possibility to flash anything.
Aaargh!

Where do I find a 4.2.8 recovery.img for this phone?
Maybe there's a possibility doing a fastboot boot recovery.img ???
NOPE:
[email protected]:/home/marius/Downloads# fastboot boot recovery.img
downloading 'boot.img'...
OKAY [ 0.662s]
booting...
FAILED (remote: unknown command)

Fixed with large hammer! Goodbye Meizu!
Learnincurve said:
Where do I find a 4.2.8 recovery.img for this phone?
Maybe there's a possibility doing a fastboot boot recovery.img ???
NOPE:
[email protected]:/home/marius/Downloads# fastboot boot recovery.img
downloading 'boot.img'...
OKAY [ 0.662s]
booting...
FAILED (remote: unknown command)
Click to expand...
Click to collapse
Fixed with large hammer! Goodbye Meizu!

fastboot boot recovery.img isn't a command at all... It's fastboot flash recovery C:/path/to/recovery.img

HTC Desire 820s , No Bootloader

Is this real ? i really cant access boot loader , just the recovery with the no command screen
can you confirm ??
if so then what i think that this device is already dead

It has a fasboot mode, for now I can only access it via adb (adb reboot bootloader). It shows a black screen with fastboot mode at the bottom.
It also has a stock recovery mode, shows 'no command' but can be activated by pressing power button.
After you've activated it:
Vol+ to select
Vol- navigate down
Power to go back

Adb No devices found , idk why my Laptop doesn't detect my desire 820s

wil try now just installed htc sync manager

okay it worked and i went to fastboot mode , when i give a cmd order it says waiting for device
eg..... fastboot oem info

Same here
fastboot oem unlock
FAILED (remote: unknown command)
fastboot oem get_identifier_token
FAILED (remote: unknown command)
any idea ?

Nc.netcat said:
Same here
fastboot oem unlock
FAILED (remote: unknown command)
fastboot oem get_identifier_token
FAILED (remote: unknown command)
any idea ?
Click to expand...
Click to collapse
Mediatek Htc devices do not need bootloader unlocking, you can flash anything from fastboot mode
---------- Post added at 04:16 PM ---------- Previous post was at 04:10 PM ----------
Mohamed Yaser said:
Is this real ? i really cant access boot loader , just the recovery with the no command screen
can you confirm ??
if so then what i think that this device is already dead
Click to expand...
Click to collapse
You are right, Mediatek HTC devices dont have bootloader. Infact mediatek htc phones can be flashed with SP Flash tool just like micromax phones. I know this is true for htc 816g.

sziraqui said:
Mediatek Htc devices do not need bootloader unlocking, you can flash anything from fastboot mode
.
Click to expand...
Click to collapse
hhmm
fastboot flash recovery recovery.img => partition 'recovery' not support flash

but flashing recovery with SP flash tool will work for sure.
1. Put your custom recovery in the firmware folder,
2. del stock recovery.img,
3. rename your custom recovery as recovery.img,
4. load scatter file,
5. uncheck everything except recovery
6. click download and then connect your powered off phone to pc while holding vol down
someone Please confirm if this works with 820s, without worrying about bootloader

sziraqui said:
but flashing recovery with SP flash tool will work for sure.
1. Put your custom recovery in the firmware folder,
2. del stock recovery.img,
3. rename your custom recovery as recovery.img,
4. load scatter file,
5. uncheck everything except recovery
6. click download and then connect your powered off phone to pc while holding vol down
someone Please confirm if this works with 820s, without worrying about bootloader
Click to expand...
Click to collapse
It works. How about flashing a RUU?

Gibz97 said:
It works. How about flashing a RUU?
Click to expand...
Click to collapse
Can mention on which device you have checked it, does it has locked bootloder (if exists)?
RUU in mediatek? i dont think mediatek phones have RUU, (try "fastboot oem rebootRUU" to check)
But if it does, you can extract rom.zip from the RUU THEN EXTRACT system.img, boot.img and recovery.img
Then keep copy this to your firmware folder (containg scatter file)
load scatter file
Uncheck everything except system,boot and recovery in sp flash tool
Click download and connect your powered off device to pc holding vol down

sziraqui said:
Can mention on which device you have checked it, does it has locked bootloder (if exists)?
RUU in mediatek? i dont think mediatek phones have RUU, (try "fastboot oem rebootRUU" to check)
But if it does, you can extract rom.zip from the RUU THEN EXTRACT system.img, boot.img and recovery.img
Then keep copy this to your firmware folder (containg scatter file)
load scatter file
Uncheck everything except system,boot and recovery in sp flash tool
Click download and connect your powered off device to pc holding vol down
Click to expand...
Click to collapse
I've done that but the phone usually cannot boot into the system.
BTW I am on Kitkat 4.4.4 without Sense and I want to flash Lollipop 5.0.2 Sense 7.
The RUU is from a Taiwanese variant 820ys which runs Lollipop 5.0.2 and Sense 7 out of the box, same models(htc_a50ml_dtul)
The problem is that the Kitkat Firmware has smaller partitions compared to the lollipop one. An example is the Kitkat system partition which is about 1.4Gbs while Lollipop has about 4.9Gbs, so I cannot flash with the same scatter file.
So I edit the scatter file to inflate the partitions in order to accommodate the big Lollipop files (sytem.img,recovery.img and boot.img) and perform firmware upgrade.
What could be stopping it from booting? Is it due the fact that the Lollipop boot and recovery are verified? Thanks in advance
Screenshots for Kitkat and Lollipop firmware files below

Gibz97 said:
I've done that but the phone usually cannot boot into the system.
BTW I am on Kitkat 4.4.4 without Sense and I want to flash Lollipop 5.0.2 Sense 7.
The RUU is from a Taiwanese variant 820ys which runs Lollipop 5.0.2 and Sense 7 out of the box, same models(htc_a50ml_dtul)
The problem is that the Kitkat Firmware has smaller partitions compared to the lollipop one. An example is the Kitkat system partition which is about 1.4Gbs while Lollipop has about 4.9Gbs, so I cannot flash with the same scatter file.
So I edit the scatter file to inflate the partitions in order to accommodate the big Lollipop files (sytem.img,recovery.img and boot.img) and perform firmware upgrade.
What could be stopping it from booting? Is it due the fact that the Lollipop boot and recovery are verified? Thanks in advance
Screenshots for Kitkat and Lollipop firmware files below
Click to expand...
Click to collapse
well this question will take the thread off topic. I would request you to create a new thread regarding this issue under "q&a,help and troubleshooting". Chances of your problem getting solved are higher if you do so. I will post my views regarding your issue in that thread. And i apologize to OP, because i only started answering questions irrelevant to his thread.

i totally accept off topics if they are helpful

sziraqui said:
but flashing recovery with SP flash tool will work for sure.
1. Put your custom recovery in the firmware folder,
2. del stock recovery.img,
3. rename your custom recovery as recovery.img,
4. load scatter file,
5. uncheck everything except recovery
6. click download and then connect your powered off phone to pc while holding vol down
someone Please confirm if this works with 820s, without worrying about bootloader
Click to expand...
Click to collapse
Hi.
It worked, but pressing Vol UP, not down. Anyway i've installed Recovery but when i try to access it from bootloader the device stopped me tellig that is for Android developers. I think that is because at the top of bootloader screen it tell "LOCKED". Any solution?

htc desire 820 softbrick not connecting with fastboot

[Help] No more bootloader after full ASUS-ROM reinstallation

Hi,
After rooting my ZE500KL doing some stupid operations (like breaking gapps with Titanium backup), I decided to make a full factory reinitialisation with UL-ASUS_Z00E-WW-12.8.5.106-user.zip..
That's work fine, but I can't boot to bootloader any more with power+sound key combination or adb reboot bootloader: boot never finalize.
Information: The recovery boot correctly.
Anyone can help me ?

Try flash .156
It updated bootloader, so it should fix your problem.
After that, you can downgrade to .118 if you want (best version for rooting, imho)

Go to this http://forum.xda-developers.com/zenfone-2-laser/general/wip-finding-to-root-ze500kl-t3223797
and download Original boot.img and Official recovery then use ADB to flash your bootloader
-adb device
-adb reboot bootloader
-fastboot devices
-fastboot flash boot boot.img
-fastboot flash OfficialRecovery.img
-fastboot boot boot.img
try it.

A2017G How to relock Bootloader to original mode.

Hi,
is it possible to relock the bootloader to original factory mode.

fastboot oem lock (will erase userdata)
Also you should restore the fbop partition: /dev/block/bootdevice/by-name/fbop
For more reference see:
https://forum.xda-developers.com/axon-7/help/lock-unlocked-bootloader-t3444044
https://forum.xda-developers.com/showpost.php?p=68738854&postcount=100
Also please don't open a thread to a question that has already been answered several times.

After i unlocked bootloader my phone now is recognized as A2017U. When i relock it will it then recognized as original A2017G ?

I am interested in a tutorial about going back to stock for G model

The procedure for the g model is no different than the U model except you have to revert the bootloader (fbop partition) because the european model is quite restricted.
For making a tutorial I would need to know exactly what you modified.
There are already good step by step guides in this forum. All I could offer you are my backup files for the recovery and bootloader for the 2017G with update B08.

Bomberus said:
The procedure for the g model is no different than the U model except you have to revert the bootloader (fbop partition) because the european model is quite restricted.
For making a tutorial I would need to know exactly what you modified.
There are already good step by step guides in this forum. All I could offer you are my backup files for the recovery and bootloader for the 2017G with update B08.
Click to expand...
Click to collapse
At the moment i am on B09 rooted but I installed it via TWRP using DrakenFx's tutorial from here : https://forum.xda-developers.com/showpost.php?p=68873485&postcount=3
Futhermore when I unlocked the bootloader I was on B03 and I saved the aboot.img and fbop_lock.img .
Now I would like to go back to fully stock to prepare for the android N update.
I would highly appreciate it if you could offer me some directions for this matter.

Never tried this method (so I take no responsibility) but in order to receive ota you need an unmodified system with locked bootloader.
To lock your bootloader:
First backup all your apps, data and internal sdcard !
Connect your phone to a PC and start adb:
Type: "adb reboot bootloader"
Phone will restart: (if you are on linux, run fastboot with root permission)
Type: "fastboot oem device-info" (just to check things)
"fastboot oem lock" (will lock your bootloader)
According to DrakenFX you should have the stock recovery already installed. So you can flash a sd card upgrade from ZTE "http://www.ztedevice.com/support/detail?id=98CEB24F9FFD433EA99EC424163149A6" (to bring you back to stock)
If you still have TWRP use DrakenFX files to flash your system back to stock, but this time do not flash supersu.
You should be good to go and just have to wait for ZTE to release the update and apply it via the updater UI.
BTW this is my fastboot oem device-info output:
(bootloader) Device tampered: false
(bootloader) Device unlocked: true
(bootloader) Device critical unlocked: false
(bootloader) Charger screen enabled: true
(bootloader) Display panel:
OKAY [ 0.059s]
finished. total time: 0.059s
Click to expand...
Click to collapse

dodo34 said:
Hi,
is it possible to relock the bootloader to original factory mode.
Click to expand...
Click to collapse
You mind my asking the reason WHY you want to Relock?
If is cuz the N update , I'll rather keep it unlock base on @lokissmile thread and I'm 100% sure I'll be releasing N TWRP Flashable Zips for all variants when N is available.

i have G model and flashed the aboot of the U modell.
How to flash back now the aboot of the G modell back ?

Any help for the G modell ?

dodo34 said:
Any help for the G modell ?
Click to expand...
Click to collapse
as far my understanding the G model have factory images right? just download the one you were using and flash it using custom recovery.

LifeSupportZ said:
as far my understanding the G model have factory images right? just download the one you were using and flash it using custom recovery.
Click to expand...
Click to collapse
@dodo34
This is correct, the full image should be the one that contains both the emmc_appsboot.mbn (this is your aboot or bootloader partition) and the fastboot.img (the fbop or fastboot command partition) as well as recovery.img. This will set everything back to stock in one swoop. Otherwise you have to reflash the signed (tenfars) TWRP to flash back the fastboot image and then falsh back stock, since regular TWRP will either not be there anymore or will not run since BL is locked now
P.S, you can leave the fastboot alone for the purposes of OTA, no update so far hes checked on it and i am not sure if there is a G package with it since it has not changed from release, so as long as the image you flash has the bootloader and recover you should be good for N
P.S.2 Actually I see a little catch 22 here. If you lock the BL first, then you will not be able to run TWRP or boot into system if it was modified. You would need to flash the "signed" version of TWRP or flash stock recovery before locking the BL. Stock would be preferable since it can flash the factory package withouht modifications. If using TWRP i think you have to change updater-script to remove a .... and i just found another catch 22. The updater-script will look for product name P996A04 and if yours shows as 2017U the it will report back P996A01 so you will have to have a signed TWRP on there no matter what. Either to flash the backed up aboot fbop and recovery and then flash the full factory package through stock recovery or mod the updater-script and remove the assert line and flash the whole thing with TWRP. What do you get in TWRP shel when you run this "getprop ro.product.model"

peramikic said:
@dodo34
This is correct, the full image should be the one that contains both the emmc_appsboot.mbn (this is your aboot or bootloader partition) and the fastboot.img (the fbop or fastboot command partition) as well as recovery.img. This will set everything back to stock in one swoop. Otherwise you have to reflash the signed (tenfars) TWRP to flash back the fastboot image and then falsh back stock, since regular TWRP will either not be there anymore or will not run since BL is locked now
P.S, you can leave the fastboot alone for the purposes of OTA, no update so far hes checked on it and i am not sure if there is a G package with it since it has not changed from release, so as long as the image you flash has the bootloader and recover you should be good for N
P.S.2 Actually I see a little catch 22 here. If you lock the BL first, then you will not be able to run TWRP or boot into system if it was modified. You would need to flash the "signed" version of TWRP or flash stock recovery before locking the BL. Stock would be preferable since it can flash the factory package withouht modifications. If using TWRP i think you have to change updater-script to remove a .... and i just found another catch 22. The updater-script will look for product name P996A04 and if yours shows as 2017U the it will report back P996A01 so you will have to have a signed TWRP on there no matter what. Either to flash the backed up aboot fbop and recovery and then flash the full factory package through stock recovery or mod the updater-script and remove the assert line and flash the whole thing with TWRP. What do you get in TWRP shel when you run this "getprop ro.product.model"
Click to expand...
Click to collapse
if he mod the updater_script from official zte update to make it flash friendly, this is what i'll do,
* Mod updater script and remove aboot and recovery for now
* flash new zip without file mention above
* boot to bootloader while having custom recovery
* lock back the bootloader
* boot to custom recovery and perform " format data "
* create a flashable zip with stock aboot and recovery
* flash new zip with aboot and recovery
* reboot to recovery and check if boot to stock recovery and while in there perform a factory reset
i know is a lot of steps but, seems like is the way to go to get everything back in place without zte noticing anything.

Now i am on B06.
I put update.zip B08 and select update. But it boots to TWRP recovery and update fails.

@dodo34 If you are trying to restore from the OS system update you need to reflash your stock recovery for it to work properly. Wait for someone to confirm what I just said, but that's how it worked for me.

how can i flash my original recovery. what is the command for cmd ?

Please help restoring back original recovery.

dodo34 said:
Please help restoring back original recovery.
Click to expand...
Click to collapse
rczrider said:
Putting Your Axon 7 Back to Stock
If you want to revert back to stock and re-lock your bootloader (eg. sending the phone in for warranty work or are selling it), you should be able to do that using the steps below. It worked for me, anyway, exactly as written below.
Copy everything off your internal storage that you don't want to lose. If you're not rooted (so already stock, but with unlocked bootloader), skip to step 6 below. Otherwise, continue.
Grab the "StockSystem" zip for your variant from this thread and place on your microSD card: http://forum.xda-developers.com/axon-7/development/rom-guide-updates-to-stock-files-via-t3469484
Reboot into TWRP and wipe system, data, dalvik, and cache
Flash the StockSystem zip and power off (doing so will restore stock boot but does not appear to restore recovery)
Boot into EDL mode and flash stock recovery only: http://forum.xda-developers.com/axon-7/development/wip-axon-7-root-bootloader-unlokced-t3441204
Power off the phone, plug from computer, and then boot into stock recovery (hold Vol+ and press Pwr, continue holding Vol+ until recovery comes up)
Select "Wipe data / factory reset" and then "Yes"
After that finishes, select "Reboot to bootloader"
Plug in your phone into your computer and do: fastboot oem lock (see second post if this doesn't work and says <waiting for device>)
Your phone will reboot and should have been totally wiped (including internal storage) by doing the above
This should leave you with a stock, locked, and unrooted phone that can take OTAs. Note: it's possible (in fact, likely) that an OTA could break the ability to unlock your bootloader and gain root again, so be careful about going back to stock if you think you'll want to unlock/root later on!
If you need any stock files for B20 or B27 (stock recovery for re-locking, for example), you can get them here: http://forum.xda-developers.com/axon-7/development/untouched-b20-boot-recovery-files-t3443818
Click to expand...
Click to collapse
Try this guide from newbie unlock thread.

I get this error.
C:\Users\Intel\Downloads\Axon7\ADB>axon7tool -r
Usage:
axon7tool -r <boot|recovery|gpt> ...
axon7tool -w <boot|recovery>
C:\Users\Intel\Downloads\Axon7\ADB>axon7tool -r recovery
Connecting to device...
S: failed to read command
S: Failed to receive hello
terminate called after throwing an instance of 'std::runtime_error'
what(): error: Unknown error
This application has requested the Runtime to terminate it in an unusual way.
Please contact the application's support team for more information.

what i did.
Flashed Draken TWRP System Image B06
Flashed Draken TWRP Stcok Recovery B06
Flashed full update.zip B08
Now my phone is recognized as A2017G on the PC
But when i reboot the phone i get a message that the phone is unlocked and not trusted ?
why ?

[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.