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!
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
Unlocked bootloader with no problems.
When I try to boot into recovery with ""it says "fastboot flash boot twrp-3.4.0-0-evert.img" it says :
fastboot: error: Failed to identify current slot
When I run "fastboot flash boot_a twrp-3.4.0-0-evert.img" it says:
(bootloader) max-download-si: not found
fastboot: error: Couldn't parse partition size '0x'.
When I run "fastboot flash boot_b twrp-3.4.0-0-evert.img" it says:
(bootloader) is-logical:boot: not found
fastboot: error: cannot get boot partition size
That's not the correct way to do it.
Use this: fastboot boot <name of twrp file>.img
E10110111 said:
Unlocked bootloader with no problems.
When I try to boot into recovery with ""it says "fastboot flash boot twrp-3.4.0-0-evert.img" it says :
fastboot: error: Failed to identify current slot
When I run "fastboot flash boot_a twrp-3.4.0-0-evert.img" it says:
(bootloader) max-download-si: not found
fastboot: error: Couldn't parse partition size '0x'.
When I run "fastboot flash boot_b twrp-3.4.0-0-evert.img" it says:
(bootloader) is-logical:boot: not found
fastboot: error: cannot get boot partition size
Click to expand...
Click to collapse
First of all you should reboot your device once after doing any changes.
Hi Guys
I bricked my phone because I did something wrong. I need help.
I have a rooted Moto g7 (river) running android pie.
I decided to upgrade it to android 10.
1. I downloaded the latest android 10 version from:
lolinet mirrors - firmware, software, iso etc.
lolinet mirrors - powered by h5ai
mirrors.lolinet.com
2. created new C:\adb2021 folder in laptop
obtained latest adb/fastboot from
https://developer.android.com/studio/releases/platform-tools
unziped the zip contents into the new C:\adb2021
3. Connected by cable and turned on phone
4. In a CMD prompt on W10 went to in C:\adb2021
5. adb reboot bootloader
was successful
6. I then ran
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 boot boot.img
fastboot flash dtbo dtbo.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 carrier
fastboot erase DDR
fastboot flash logo logo.bin
patched_boot.img
fastboot reboot
Problem:
The phone rebooted but is stuck on the
"your device has been unlocked and can't be trusted" screen.
Rebooting just brings me back to this same screen.
I can get to the Android Recovery screens but don't know what to do there.
The fastboot commands I listed above were originally designed for installing android 9. I now see I should have included fastboot flash system system.img_sparsechunk.10
When in the recovery screen "Flastboot Flash mode" I tried to issue from the laptop
C:\ADB2021>adb reboot bootloader
I get
error: no devices/emulators found
Please help. This is my main phone.
How do I recover?
Thanks.
I tried factory reset. And then reboot but it still only goes to the "this device is unlocked....." and stays there.
I really need help.
Hello experts, i'm diving directly into main problem. My phone directly powered off when i using phone. when i try to open, stuck on android one logo.
i tried to flash new rom via MiFlash. But its giving strange errors.
Also i tried to format data via twrp, but it stucks after i swipe. i tried also wipe system,dalvik, cache, but same thing happened. stucking after i swipe.
I think phone bricked.
Today i tried to flash all img files via fastboot like this;
Code:
fastboot erase boot_a
fastboot flash modem_a modem.img
fastboot flash modem_b modem.img
fastboot flash sbl1 sbl1.img
fastboot flash sbl1bak sbl1.img
fastboot flash rpm rpm.img
fastboot flash rpmbak rpm.img
fastboot flash tz tz.img
fastboot flash tzbak tz.img
fastboot flash devcfg devcfg.img
fastboot flash devcfgbak devcfg.img
fastboot flash dsp dsp.img
fastboot flash sec sec.dat
fastboot flash splash splash.img
fastboot flash misc misc.img
fastboot flash aboot emmc_appsboot.mbn
fastboot flash abootbak emmc_appsboot.mbn
fastboot flash boot_a boot.img
fastboot flash boot_b boot.img
fastboot flash system_a system.img
fastboot flash system_b system_other.img
fastboot flash lksecapp lksecapp.img
fastboot flash lksecappbak lksecapp.img
fastboot flash cmnlib cmnlib.img
fastboot flash cmnlibbak cmnlib.img
fastboot flash cmnlib64 cmnlib64.img
fastboot flash cmnlib64bak cmnlib64.img
fastboot flash keymaster keymaster.img
fastboot flash keymasterbak keymaster.img
fastboot flash userdata userdata.img
fastboot set_active a
fastboot reboot
I moved my tissot images to adb folder and started.
But after i tried whole codes in powershell with copy paste, giving "(command write failed (Invalid argument))" error in 2nd img file. Thats really interesting. first img file transfered succesfully but 2nd one is giving error.
And i decided to flash step by step, aand BUM. i dont getting any error while flashing step by step. But if i try to flash for example 2 img file, its giving error.
I moved forward like this until system.img file give me error again.
Code:
fastboot flash system_a system.img
target reported max download size of 534773760 bytes
erasing 'system_a'...
OKAY [ 0.096s]
sending sparse 'system_a' 1/5 (522236 KB)...
OKAY [ 11.986s]
writing 'system_a' 1/5...
OKAY [ 3.926s]
sending sparse 'system_a' 2/5 (521866 KB)...
FAILED (command write failed (Invalid argument))
finished. total time: 16.308s
I flashed all img files except system.img and system_other.img. only this 2 files giving error.
And i realized that 2 file sizes are big and fastboot trying to parse files while flashing. 1st parsed file transfering succesfully but after it goes to 2nd parsed file its giving "(command write failed (Invalid argument))" error. My fastboot has some strange problem about 2nd flash code lines. I dont know why.
What can i do to flash this 2 system img file via fastboot?
my problem solved after i break apart my phone. no need help now.