Related
Hello guys,
I'm trying to downgrade my Moto X Play XT1563, I found a tutorial on the Internet using the fastboot for such a feat. From what I saw, many people use this tutorial to upgrade or simply go back to what it was before "flash".
But in the first command line, when I type in CMD, an error appears:
> fastboot flash partition gpt.bin
target reported max download size of 268435456 byte
sending 'partition' (32 KB)...
OKAY [ 0.006s]
writing 'partition'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.485s
The tutorial is for this purpose doubt
1) Extract the Fastboot / ADB and images (zip ROM), extract the two zip's to a folder of your choice
2) Restart your phone mode 'Bootloader' (Turn off the cell and then press the volume button (minus) and (power for 2 seconds) and then release the power.)
It would be interesting to have activated in the "Developer options" the option "Allow OEM Unlock"
3) Now the CMD, enter the commands:
NOTE: system.img_sparsechunk may contain name or number, so check if you have only modify the hour.
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 modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot reboot
fastboot erase userdata
fastboot reboot
I wonder if someone could help me solve this case, please.
You're lucky that it failed. It's totally okay.
Don't flash the Partition Table - gpt.bin and skip the bootloader.
It's not recommended to do so and there are even threads in this sub forum to warn people.
See: http://forum.xda-developers.com/moto-x-play/general/reminder-how-to-downgrade-6-0-to-5-1-1-t3267253
It can lead to bricking your device.
So just skip fastboot flash partition gpt.bin and fastboot flash bootloader bootloader.img, do everything else.
THANKS!
Wardenn said:
You're lucky that it failed. It's totally okay.
Don't flash the Partition Table - gpt.bin and skip the bootloader.
It's not recommended to do so and there are even threads in this sub forum to warn people.
See: http://forum.xda-developers.com/moto-x-play/general/reminder-how-to-downgrade-6-0-to-5-1-1-t3267253
It can lead to bricking your device.
So just skip fastboot flash partition gpt.bin and fastboot flash bootloader bootloader.img, do everything else.
Click to expand...
Click to collapse
Man you are the ****ing best! You save my phone. Thank you very much! I was so stressed! THANKSSSS!
Hi, friends. Sorry, but my english is bad.
I tell you, I flash my firmware stock XT1575 6.0, but failed to be carried out correctly. Motorola have installed the drivers, as should be. I tried to flash with RSD Lite 6.2.4, and using commands in both made the same mistake at the same stage flashing. This is the error:
C:\Users\Lisandro\Desktop\platform-tools>fastboot flash modem NON-HLOS.bin
target reported max download size of 536870912 bytes
sending 'modem' (41686 KB)...
OKAY [ 1.041s]
writing 'modem'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 1.059s
Bootloader is unlocked.
I'm from Argentina, I tried a SIM Personal and working properly, test it with a SIM Claro AR and does not work, try registar network and tells me: "The selected network (Claro AR) is not available".
From already thank you very much.
I hope to resolve this soon.
Regards!
Lisandro4m41 said:
Hi, friends. Sorry, but my english is bad.
I tell you, I flash my firmware stock XT1575 6.0, but failed to be carried out correctly. Motorola have installed the drivers, as should be. I tried to flash with RSD Lite 6.2.4, and using commands in both made the same mistake at the same stage flashing. This is the error:
C:\Users\Lisandro\Desktop\platform-tools>fastboot flash modem NON-HLOS.bin
target reported max download size of 536870912 bytes
sending 'modem' (41686 KB)...
OKAY [ 1.041s]
writing 'modem'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 1.059s
Bootloader is unlocked.
I'm from Argentina, I tried a SIM Personal and working properly, test it with a SIM Claro AR and does not work, try registar network and tells me: "The selected network (Claro AR) is not available".
From already thank you very much.
I hope to resolve this soon.
Regards!
Click to expand...
Click to collapse
Modem flash fails frequently, repeat the command until it returns OK (may take 2 or 3 times) then continue. Make sure to follow all the steps in order, the order is important.
acejavelin said:
Modem flash fails frequently, repeat the command until it returns OK (may take 2 or 3 times) then continue. Make sure to follow all the steps in order, the order is important.
Click to expand...
Click to collapse
Ok, thanks. I'll keep trying. Do you think that these commands are properly sorted?
fastboot oem fb_mode_set oem
fastboot flash partition gpt.bin
fastboot flash motoboot motoboot.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 modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot erase customize
fastboot erase clogo
fastboot oem fb_mode_clear
Lisandro4m41 said:
Ok, thanks. I'll keep trying. Do you think that these commands are properly sorted?
fastboot oem fb_mode_set oem
fastboot flash partition gpt.bin
fastboot flash motoboot motoboot.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 modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot erase customize
fastboot erase clogo
fastboot oem fb_mode_clear
Click to expand...
Click to collapse
Depends on the firmware you are using.. according to Moto that isn't the right process, but using the latest MXPE firmware from here it appears correct. It is best to look in the firmware ZIP and find the flashfile.xml file and follow that, open it in a reasonable XML capable editor (not Notepad, but Notepad++ works well) and you can see the exact process step by step.
In looking at the file, pay attention to the steps with "operation" in them, those are the fastboot commands.
acejavelin said:
Depends on the firmware you are using.. according to Moto that isn't the right process, but using the latest MXPE firmware from here it appears correct. It is best to look in the firmware ZIP and find the flashfile.xml file and follow that, open it in a reasonable XML capable editor (not Notepad, but Notepad++ works well) and you can see the exact process step by step.
In looking at the file, pay attention to the steps with "operation" in them, those are the fastboot commands.
Click to expand...
Click to collapse
Thanks! Right now I'm downloading the firmware of the Motorola official page. I hope it works. Thanks again!
I downloaded the firmware from the official website, but I can not install it, how I go about flashing?
Lisandro4m41 said:
I downloaded the firmware from the official website, but I can not install it, how I go about flashing?
Click to expand...
Click to collapse
Where is it failing?
Sent from my Motorola XT1575 using XDA Labs
acejavelin said:
Where is it failing?
Sent from my Motorola XT1575 using XDA Labs
Click to expand...
Click to collapse
I do not know from where to start installing, to decompress the RAR I downloaded, unzip a file I can not open. Basically, once you downloaded the firmware from the Motorola, how do I install it?
Lisandro4m41 said:
I do not know from where to start installing, to decompress the RAR I downloaded, unzip a file I can not open. Basically, once you downloaded the firmware from the Motorola, how do I install it?
Click to expand...
Click to collapse
It is a .gz file, you extract it like a ZIP/RAR file with a tool like 7-Zip.
The file from Moto is rather old, the one I linked above ( http://forum.xda-developers.com/showpost.php?p=67343754&postcount=171 ) is the current release.
You flash it like you stated earlier.
acejavelin said:
It is a .gz file, you extract it like a ZIP/RAR file with a tool like 7-Zip.
The file from Moto is rather old, the one I linked above ( http://forum.xda-developers.com/showpost.php?p=67343754&postcount=171 ) is the current release.
You flash it like you stated earlier.
Click to expand...
Click to collapse
Yes, I unzipped the .gz file. I managed to get the folder with the files, but following the commands of the Motorola, I pulled the same mistake when creating the thread. You are downloading the most current version. Still I do not understand what the error:
(Bootloader) failed validation Preflash
FAILED (remote failure)
What is the cause of that?
Lisandro4m41 said:
Yes, I unzipped the .gz file. I managed to get the folder with the files, but following the commands of the Motorola, I pulled the same mistake when creating the thread. You are downloading the most current version. Still I do not understand what the error:
(Bootloader) failed validation Preflash
FAILED (remote failure)
What is the cause of that?
Click to expand...
Click to collapse
Usually it means either the bootloader is still locked (which we know your's is unlocked) or the file is incorrect for your device. Sometimes it's a random error, try erasing the modemst1 and modemst2 first, then flash NON-HLOS.bin a time or two until it gives and OK and continue from there like normal.
I have not retested flash, but I solved my problem. The problem was that the phone was locked in Claro AR. No relation to the Bootloader error, but got what I wanted haha. Thanks for your time.
Greetings from Argentina.
It seems that
Code:
fastboot flashing unlock
and
Code:
fastboot flashing unlock_critical
are the same command.
I've tried wiping all data, using MsmDownloadTool and re-doing every steps, but there's only two options: Unlock or Lock Bootloader.
I want flash some images into some critical partitions, it always says Flashing is not allowed for Critical Partitions. Has anyone succeed unlocking the Critical Partitions on OnePlus 6T?
vungsung said:
It seems that
Code:
fastboot flashing unlock
and
Code:
fastboot flashing unlock_critical
are the same command.
I've tried wiping all data, using MsmDownloadTool and re-doing every steps, but there's only two options: Unlock or Lock Bootloader.
I want flash some images into some critical partitions, it always says Flashing is not allowed for Critical Partitions. Has anyone succeed unlocking the Critical Partitions on OnePlus 6T?
Click to expand...
Click to collapse
You cannot flash critical the 6T.
You need to dd directly to the media.
What are you wanting to flash to a critical partition.
tech_head said:
You cannot flash critical the 6T.
You need to dd directly to the media.
What are you wanting to flash to a critical partition.
Click to expand...
Click to collapse
Is there any up-to-dated NetHunter kernal for Oneplus6T?
vungsung said:
I'm trying to flash NetHunter kernel: https://forum.xda-developers.com/oneplus-6t/development/oneplus6-6t-nethunter-kernel-t3900105, which lead me to a github page: https://github.com/johanlike/Oneplus6-or-6T-Nethunter-Kernel. I followed the tutorial in the github page. They say you have to flash patched imgaes list in https://github.com/johanlike/Oneplus6-or-6T-Nethunter-Kernel/blob/master/flash.bat. I run flash.bat, and saw the errors.
Click to expand...
Click to collapse
When I flash ElementalX the boot image is patched via the install.
On this phone, if you have a patched boot image it's not a critical partition.
fastboot flash boot_a/b boot.img (the boot_a/b is for which partition you are flashing).
tech_head said:
When I flash ElementalX the boot image is patched via the install.
On this phone, if you have a patched boot image it's not a critical partition.
fastboot flash boot_a/b boot.img (the boot_a/b is for which partition you are flashing).
Click to expand...
Click to collapse
I don't get it. I do have to flash boot.img, which is not critical, AND below, that some of them are critical.
Code:
fastboot erase boot_a
fastboot erase boot_b
fastboot erase system_a
fastboot erase system_b
fastboot erase radio
fastboot erase radio_a
fastboot erase radio_b
fastboot erase recovery
fastboot erase recovery_a
fastboot erase recovery_b
fastboot erase userdata
fastboot erase userdata_a
fastboot erase userdata_b
fastboot flash abl_a abl.img
fastboot flash aop_a aop.img
fastboot flash bluetooth_a bluetooth.img
fastboot flash boot_a boot.img
fastboot flash cmnlib64_a cmnlib64.img
fastboot flash cmnlib_a cmnlib.img
fastboot flash devcfg_a devcfg.img
fastboot flash dsp_a dsp.img
fastboot flash dtbo_a dtbo.img
fastboot flash fw_4j1ed_a fw_4j1ed.img
fastboot flash fw_4u1ea_a fw_4u1ea.img
fastboot flash hyp_a hyp.img
fastboot flash keymaster_a keymaster.img
fastboot flash LOGO_a LOGO.img
fastboot flash modem_a modem.img
fastboot flash oem_stanvbk_a oem_stanvbk.img
fastboot flash qupfw_a qupfw.img
fastboot flash storsec_b storsec.img
fastboot flash system_a system.img
fastboot flash tz_a tz.img
fastboot flash vbmeta_a vbmeta.img
fastboot flash vendor_a vendor.img
fastboot flash xbl_config_a xbl_config.img
fastboot flash xbl_a xbl.img
fastboot flash abl_b abl.img
fastboot flash aop_b aop.img
fastboot flash bluetooth_b bluetooth.img
fastboot flash boot_b boot.img
fastboot flash cmnlib64_b cmnlib64.img
fastboot flash cmnlib_b cmnlib.img
fastboot flash devcfg_b devcfg.img
fastboot flash dsp_b dsp.img
fastboot flash dtbo_b dtbo.img
fastboot flash fw_4j1ed_b fw_4j1ed.img
fastboot flash fw_4u1ea_b fw_4u1ea.img
fastboot flash hyp_b hyp.img
fastboot flash keymaster_b keymaster.img
fastboot flash LOGO_b LOGO.img
fastboot flash modem_b modem.img
fastboot flash oem_stanvbk_b oem_stanvbk.img
fastboot flash qupfw_b qupfw.img
fastboot flash storsec_b storsec.img
fastboot flash system_b system.img
fastboot flash tz_b tz.img
fastboot flash vbmeta_b vbmeta.img
fastboot flash vendor_b vendor.img
fastboot flash xbl_config_b xbl_config.img
fastboot flash xbl_b xbl.img
Or it won't boot...
vungsung said:
I don't get it. I do have to flash boot.img, which is not critical, AND below, that some of them are critical.
Code:
fastboot erase boot_a
fastboot erase boot_b
fastboot erase system_a
fastboot erase system_b
fastboot erase radio
fastboot erase radio_a
fastboot erase radio_b
fastboot erase recovery
fastboot erase recovery_a
fastboot erase recovery_b
fastboot erase userdata
fastboot erase userdata_a
fastboot erase userdata_b
fastboot flash abl_a abl.img
fastboot flash aop_a aop.img
fastboot flash bluetooth_a bluetooth.img
fastboot flash boot_a boot.img
fastboot flash cmnlib64_a cmnlib64.img
fastboot flash cmnlib_a cmnlib.img
fastboot flash devcfg_a devcfg.img
fastboot flash dsp_a dsp.img
fastboot flash dtbo_a dtbo.img
fastboot flash fw_4j1ed_a fw_4j1ed.img
fastboot flash fw_4u1ea_a fw_4u1ea.img
fastboot flash hyp_a hyp.img
fastboot flash keymaster_a keymaster.img
fastboot flash LOGO_a LOGO.img
fastboot flash modem_a modem.img
fastboot flash oem_stanvbk_a oem_stanvbk.img
fastboot flash qupfw_a qupfw.img
fastboot flash storsec_b storsec.img
fastboot flash system_a system.img
fastboot flash tz_a tz.img
fastboot flash vbmeta_a vbmeta.img
fastboot flash vendor_a vendor.img
fastboot flash xbl_config_a xbl_config.img
fastboot flash xbl_a xbl.img
fastboot flash abl_b abl.img
fastboot flash aop_b aop.img
fastboot flash bluetooth_b bluetooth.img
fastboot flash boot_b boot.img
fastboot flash cmnlib64_b cmnlib64.img
fastboot flash cmnlib_b cmnlib.img
fastboot flash devcfg_b devcfg.img
fastboot flash dsp_b dsp.img
fastboot flash dtbo_b dtbo.img
fastboot flash fw_4j1ed_b fw_4j1ed.img
fastboot flash fw_4u1ea_b fw_4u1ea.img
fastboot flash hyp_b hyp.img
fastboot flash keymaster_b keymaster.img
fastboot flash LOGO_b LOGO.img
fastboot flash modem_b modem.img
fastboot flash oem_stanvbk_b oem_stanvbk.img
fastboot flash qupfw_b qupfw.img
fastboot flash storsec_b storsec.img
fastboot flash system_b system.img
fastboot flash tz_b tz.img
fastboot flash vbmeta_b vbmeta.img
fastboot flash vendor_b vendor.img
fastboot flash xbl_config_b xbl_config.img
fastboot flash xbl_b xbl.img
Or it won't boot...
Click to expand...
Click to collapse
That is a complete wipe and install.
If you are only installing a kernel and NOT a ROM then that is not correct.
tech_head said:
That is a complete wipe and install.
If you are only installing a kernel and NOT a ROM then that is not correct.
Click to expand...
Click to collapse
I know the correct steps to install kernels or ROMS. The problem is I tried to install OOS official ROM, and install the Nethunter kernel, the kernel won't work at all. So I have to install the patched ROM by flash the patched images inside the ROM one-by-one and then install kernel.
vungsung said:
I know the correct steps to install kernels or ROMS. The problem is I tried to install OOS official ROM, and install the Nethunter kernel, the kernel won't work at all. So I have to install the patched ROM by flash the patched images inside the ROM one-by-one and then install kernel.
Click to expand...
Click to collapse
You indicated you were trying to flash a kernel which is why I said that. Had you said you were trying to flash a complete ROM then I would have said something else.
tech_head said:
You indicated you were trying to flash a kernel which is why I said that. Had you said you were trying to flash a complete ROM then I would have said something else.
Click to expand...
Click to collapse
Sorry, I didn't mean to make you misunderstood. For those find this thread with the same problem, I'd say trying to flash OOS by normal way. Thanks for your help, tech_head!
i am using china global oneplus 8. I have unlocked bootloader but i cannot unlock critical partition . i have tried with this code: fastboot flashing unlock_critical
But it is not working ..please help me to unlock critical partition. My phone is bricked....
sadatkabir55 said:
i am using china global oneplus 8. I have unlocked bootloader but i cannot unlock critical partition . i have tried with this code: fastboot flashing unlock_critical
But it is not working ..please help me to unlock critical partition. My phone is bricked....
Click to expand...
Click to collapse
Wrong thread there Glenda. This is the 6T forum.
I got same problem how to fix this???????
vungsung said:
I'm trying to flash NetHunter kernel: https://forum.xda-developers.com/oneplus-6t/development/oneplus6-6t-nethunter-kernel-t3900105, which lead me to a github page: https://github.com/johanlike/Oneplus6-or-6T-Nethunter-Kernel. I followed the tutorial in the github page. They say you have to flash patched imgaes list in https://github.com/johanlike/Oneplus6-or-6T-Nethunter-Kernel/blob/master/flash.bat. I run flash.bat, and saw the errors.
Click to expand...
Click to collapse
That's a pretty old version of that kernel. Here's the up to date version, and you can flash it from recovery without any issues
http://www.mediafire.com/file/fue9i4pzbcp4x6w/NHKernel.zip/file
Jfoster1234 said:
That's a pretty old version of that kernel. Here's the up to date version, and you can flash it from recovery without any issues
http://www.mediafire.com/file/fue9i4pzbcp4x6w/NHKernel.zip/file
Click to expand...
Click to collapse
Alright, thank you for the resource!
have you fixed already bro?
sadatkabir55 said:
i am using china global oneplus 8. I have unlocked bootloader but i cannot unlock critical partition . i have tried with this code: fastboot flashing unlock_critical
But it is not working ..please help me to unlock critical partition. My phone is bricked....
Click to expand...
Click to collapse
have you fixed?
sadatkabir55 said:
i am using china global oneplus 8. I have unlocked bootloader but i cannot unlock critical partition . i have tried with this code: fastboot flashing unlock_critical
But it is not working ..please help me to unlock critical partition. My phone is bricked....
Click to expand...
Click to collapse
gazitonmoy said:
have you fixed?
Click to expand...
Click to collapse
[CLOSED] Same here, no Idea what to do? Phone bricked and dead. PLEASE HELP US, GUYS
--
EDIT: *lol - I did a "oem lock" and a "oem unlock" again... and suddenly my device behaves as expected again, without needing to "flash-all.bat". Perhaps sometimes I will understand this stuff... :/
tech_head said:
You cannot flash critical the 6T.
You need to dd directly to the media.
What are you wanting to flash to a critical partition.
Click to expand...
Click to collapse
What does "dd" stand for?
Did you solve this? I have the same issue. Oneplus 8 Pro, got it and installed LineageOS right away which worked, but just wasn't useable, lots of gps stuff not working. So, I wanted to restore the factory ROM. I followed this:
How to Create Fastboot-flashable Factory Image for Any OnePlus Phone
Learn how to create a factory image for any OnePlus phone and flash it using Fastboot. Useful for restoring stock OxygenOS software and unbricking.
www.thecustomdroid.com
Ran through everything fine as far as I could tell the first time, but it wouldn't boot, just kept going back to fastboot.
So, I tried to re-do the steps but upon trying to go through them again, as soon as I get to about the 5th command where I reboot before continuing to flash, it reboots with a Qualcom crash screen. I can still power off and get to fastboot, but if I try to continue the flash steps i get this same error on any of them.
PLEASE HELP! I just got this phone and paid a ton I am going to loose it if I bricked it already.
UPDATE: Forget this. I didn't solve it, but I did manage to at least restore A rom.
tech_head said:
You cannot flash critical the 6T.
You need to dd directly to the media.
What are you wanting to flash to a critical partition.
Click to expand...
Click to collapse
may i know how? i want to flash persist.im for oneplus6t
sorry to post the same old ask for help. im on PPOS29.114-16-7-2
I unlocked because I thought there would be more to do if I did. then noticed not much going on. id like to get security updates without all the trouble . ive noticed people having problems with relocking. I just would like the right way laid out for me and I will give it a shot. also when you say enter the commands in for fastboot do I copy from text editor and do it or do then one at a time. lot of commands
I appreciate all help
thanks
millede74 said:
sorry to post the same old ask for help. im on PPOS29.114-16-7-2
I unlocked because I thought there would be more to do if I did. then noticed not much going on. id like to get security updates without all the trouble . ive noticed people having problems with relocking. I just would like the right way laid out for me and I will give it a shot. also when you say enter the commands in for fastboot do I copy from text editor and do it or do then one at a time. lot of commands
I appreciate all help
thanks
Click to expand...
Click to collapse
You can script them if you know how to make one. Otherwise enter them one at a time. You only need to flash this once so if you do them once each it doesn't take a long time.
Code:
fastboot getvar max-sparse-size
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
fastboot erase modemst1
fastboot erase modemst2
fastboot flash dsp adspso.bin
fastboot flash dtbo dtbo.img
fastboot flash logo logo.bin
fastboot flash boot boot.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 system_b system_b.img_sparsechunk.0
fastboot flash system_b system_b.img_sparsechunk.1
fastboot flash system_b system_b.img_sparsechunk.2
fastboot flash vendor vendor.img_sparsechunk.0
fastboot flash vendor vendor.img_sparsechunk.1
fastboot flash vendor vendor.img_sparsechunk.2
fastboot flash oem oem.img
fastboot flash oem_b oem_other.img
fastboot erase userdata
fastboot erase DDR
fastboot oem fb_mode_clear
then
Code:
fastboot oem lock
you may have to repeat this last lock command until it works. I had to do it 4-5 times.
I really appreciate the help. Thanks. Do I need to put boot image or 29.114-16-7-2 extract file in tools folder and do this?
millede74 said:
I really appreciate the help. Thanks. Do I need to put boot image or 29.114-16-7-2 extract file in tools folder and do this?
Click to expand...
Click to collapse
fastboot needs to be in the folder with the 29.114-16-7-2 files.
Thanks
Note that you need to run the fastboot oem lock command a few times in the beginning (before you flash) and after you flash a few more times for this to completely work!
Did like said and pretty much everything after fb_mode_set said command failed
Didn't do nothing to phone I can tell. I stopped after trying bootloader
What's wrong
millede74 said:
Did like said and pretty much everything after fb_mode_set said command failed
Didn't do nothing to phone I can tell. I stopped after trying bootloader
What's wrong
Click to expand...
Click to collapse
Do them one at a time and post the results of each command here so we can see.
Sorry won't be able to try again till tomorrow. One question. If I run lmsa what will it do if I use rescue after downloading system image?
millede74 said:
Sorry won't be able to try again till tomorrow. One question. If I run lmsa what will it do if I use rescue after downloading system image?
Click to expand...
Click to collapse
It does the same thing as the commands above. The process is just automated.
This is what i get when running
ptn107 said:
It does the same thing as the commands above. The process is just automated.
Click to expand...
Click to collapse
C:\ProgramData\LMSA\Download\RomFiles>fastboot dev
ZY225FR3QL fastboot
C:\ProgramData\LMSA\Download\RomFiles>fastboot oem
mmand erases all user data.
(bootloader) Please re-run this command to continu
OKAY [ 0.014s]
Finished. Total time: 0.020s
C:\ProgramData\LMSA\Download\RomFiles>fastboot oem
oid images now
(bootloader) Then re-run this command to lock
OKAY [ 0.018s]
Finished. Total time: 0.024s
C:\ProgramData\LMSA\Download\RomFiles>fastboot oem lock
(bootloader) Still require signed boot.img
OKAY [ 0.009s]
Finished. Total time: 0.014s
C:\ProgramData\LMSA\Download\RomFiles>fastboot oem lock
(bootloader) Still require signed boot.img
OKAY [ 0.009s]
Finished. Total time: 0.015s
C:\ProgramData\LMSA\Download\RomFiles>fastboot oem lock
(bootloader) Still require signed boot.img
OKAY [ 0.008s]
Finished. Total time: 0.015s
C:\ProgramData\LMSA\Download\RomFiles>fastboot oem lock
(bootloader) Still require signed boot.img
OKAY [ 0.010s]
Finished. Total time: 0.016s
C:\ProgramData\LMSA\Download\RomFiles>fastboot getvar max-sparse-size
max-sparse-size: 268435456
Finished. Total time: 0.006s
C:\ProgramData\LMSA\Download\RomFiles>fastboot oem fb_mode_set
OKAY [ 0.005s]
Finished. Total time: 0.011s
C:\ProgramData\LMSA\Download\RomFiles>fastboot flash partition gpt.bin
fastboot: error: cannot load 'gpt.bin': No such file or directory
C:\ProgramData\LMSA\Download\RomFiles>fastboot flash bootloader bootloader.img
fastboot: error: cannot load 'bootloader.img': No such file or directory
C:\ProgramData\LMSA\Download\RomFiles>fastboot flash modem NON-HLOS.bin
fastboot: error: Failed to identify current slot
C:\ProgramData\LMSA\Download\RomFiles>fastboot flash fsg fsg.mbn
fastboot: error: Failed to identify current slot
C:\ProgramData\LMSA\Download\RomFiles>
Correct me if I'm wrong but doesn't lmsa download the firmware as a zip file in C:\ProgramData\LMSA\Download\RomFiles ? If that's the case you need to make sure the files are extracted before running commands.
Dear friends,
Some time ago there were report about a serious vulnerability in the Snapdragon devices firmware, which have affected multiple users.
As a user of a Lineage OS I can not install the vendor updates, because in this case I will need to re flash all the device twice (once with Oxygen OS and second time back with Lineage OS). To fix this problem I used to extract the individual BLOBS and flash them to the phone.
I have downloaded the latest version of the Oxygen OS and extracted the payload.bin. This file contains all the BLOBs and meta data used to flash the original operation system. The blobs can be easily recovered by using the extract_android_ota_payload from cyxx script and instructions from the corresponding readme file.
Create the virtual environment with the only dependency of extract_android_ota_payload - protobuf:
Code:
pip3 install virtualenv --user
virtualenv proto_env
source proto_env/bin/activate
pip install -U protobuf
Then extract BLOBS:
Code:
python /path/to/extract_android_ota_payload.py path/to/payload.bin output_dir
Create the script to flash all the BLOBs to the phone and save it to flasher.sh
Code:
#!/bin/bash
fastboot flash abl_a abl.img
fastboot flash abl_b abl.img
fastboot flash aop_a aop.img
fastboot flash aop_b aop.img
fastboot flash bluetooth_a bluetooth.img
fastboot flash bluetooth_b bluetooth.img
fastboot flash cmnlib64_a cmnlib64.img
fastboot flash cmnlib64_b cmnlib64.img
fastboot flash cmnlib_a cmnlib.img
fastboot flash cmnlib_b cmnlib.img
fastboot flash devcfg_a devcfg.img
fastboot flash devcfg_b devcfg.img
fastboot flash dsp_a dsp.img
fastboot flash dsp_b dsp.img
fastboot flash fw_4j1ed_a fw_4j1ed.img
fastboot flash fw_4j1ed_b fw_4j1ed.img
fastboot flash fw_4u1ea_a fw_4u1ea.img
fastboot flash fw_4u1ea_b fw_4u1ea.img
fastboot flash hyp_a hyp.img
fastboot flash hyp_b hyp.img
fastboot flash india_a india.img
fastboot flash india_b india.img
fastboot flash keymaster_a keymaster.img
fastboot flash keymaster_b keymaster.img
fastboot flash LOGO_a LOGO.img
fastboot flash LOGO_b LOGO.img
fastboot flash modem_a modem.img
fastboot flash modem_b modem.img
fastboot flash oem_stanvbk oem_stanvbk.img
fastboot flash qupfw_a qupfw.img
fastboot flash qupfw_b qupfw.img
fastboot flash reserve_a reserve.img
fastboot flash reserve_b reserve.img
fastboot flash storsec_a storsec.img
fastboot flash storsec_b storsec.img
echo "\"Invalid sparse file format at header magic\" is not an error you need only to wait"
fastboot flash tz_a tz.img
fastboot flash tz_b tz.img
fastboot flash vendor_a vendor.img
fastboot flash vendor_b vendor.img
fastboot flash xbl_config_a xbl_config.img
fastboot flash xbl_config_b xbl_config.img
fastboot flash xbl_a xbl.img
fastboot flash xbl_b xbl.img
exit 0
Reboot the phone to fastboot mode and flash:
Code:
# Check that we see the device:
flastboot devices
./flasher.sh
This script has successfully updated all the non lineage OS partitions (which are boot.img, dtbo.img, system.img and vbmeta.img).
Though the Trust utility is happy, saying that all the updates were applied successfully, I still have seen several errors, updating the critical sections: keymaster, tz, xbl_config and xbl. I think that Trust only check the vendor partition and does not check others.
Did anybody encountered this kind of problems? Is it critical to update ALL the partitions?