I have unlocked bootloader. And flash the official recovery to get Naugat OTA but after updating. I am seeing "ID : bad key " instead of "ID : N/A" which is written in previous version of OS.
Any one know what it really meant.?
Try to boot in qcom or bp tools mode via menu fastboot, then restart the device. In my case, at the restart it shows "ID: N/A" Again. Another Theory is that you can get the "N/A" message after a hard reset o format data vía TWRP. I do both with the same results. Maybe a encryption mismatch.
GuzXT said:
Try to boot in qcom or bp tools mode via menu fastboot, then restart the device. In my case, at the restart it shows "ID: N/A" Again. Another Theory is that you can get the "N/A" message after a hard reset o format data vía TWRP. I do both with the same results. Maybe a encryption mismatch.
Click to expand...
Click to collapse
I tried but still it shows bad key.. but it's ok until my device boots in system succesfully
.
GuzXT said:
Try to boot in qcom or bp tools mode via menu fastboot, then restart the device. In my case, at the restart it shows "ID: N/A" Again. Another Theory is that you can get the "N/A" message after a hard reset o format data vía TWRP. I do both with the same results. Maybe a encryption mismatch.
Click to expand...
Click to collapse
Has the same ID: N / A
unlocked bootloader on Android 7
Any ideas ?
S3V3N said:
Has the same ID: N / A
unlocked bootloader on Android 7
Any ideas ?
Click to expand...
Click to collapse
Pretty sure everyone has this with an unlocked bootloader.
ok thx
xxBrun0xx said:
Pretty sure everyone has this with an unlocked bootloader.
Click to expand...
Click to collapse
definitely not.
Am facing same problem. Bad boot image.. Looking for stock boot image
kdagia said:
Am facing same problem. Bad boot image.. Looking for stock boot image
Click to expand...
Click to collapse
did you find the solution iused twrp and i had no problem after installing the Russian ROM im getting this message
kdagia said:
Am facing same problem. Bad boot image.. Looking for stock boot image
Click to expand...
Click to collapse
Do you mean bad boot image in the sense of it won't boot or just the warning screen every time you boot. If its the second one you can fix it (almost) completely by flashing a modified logo.bin. I got those in my signature second thread if you are searching for that. Would be strange if your boot image couldn't boot up.
G4liant said:
Do you mean bad boot image in the sense of it won't boot or just the warning screen every time you boot. If its the second one you can fix it (almost) completely by flashing a modified logo.bin. I got those in my signature second thread if you are searching for that. Would be strange if your boot image couldn't boot up.
Click to expand...
Click to collapse
I mean 'bad key' instead of showing "N/A"
kdagia said:
I mean 'bad key' instead of showing "N/A"
Click to expand...
Click to collapse
You need to flash modified logo.bin ...That's it
Same, and cant seem to flash at all
I'm having the same trouble here.
The main problem is that it seems to be related to the impossibility to flash again or install new rom on the device.
When i try to follow the typical procedures on cmd, i get messages like:
>> writing 'partition'...
>> (bootloader) Security version downgrade
>> (bootloader) Image primary_gpt failed validation
>> (bootloader) Preflash validation failed
>> FAILED (remote failure)
And then I can't seem to move on to another rom (and relocking the device, as I wish to do after all this).
(when i said typical procedures is that i found on many places, such as the motorola official website, https :// motorola-global-portal.custhelp.com/app/standalone/bootloader/recovery-images#)
FLASH AND RELOCK YOUR DEVICE
After downloading the image for your device:
Make sure you have a Moto Pure Edition or a Developer Edition device.
Make sure you download the corresponding recovery image from the above portal.
To flash, put the phone in fastboot mode:
1. Power OFF your device
2. Then Power ON + Volume Down
Alternatively, you can reboot into fastboot mode if you have adb...adb reboot bootloader.
Next flash the images using fastboot:
$ fastboot flash partition gpt.bin
$ fastboot flash motoboot motoboot.img
$ fastboot reboot-bootloader
$ fastboot flash logo logo.bin
$ fastboot flash boot boot.img
$ fastboot flash recovery recovery.img
$ fastboot flash system system.img
$ fastboot flash modem NON-HLOS.bin
$ fastboot erase modemst1
$ fastboot erase modemst2
$ fastboot flash fsg fsg.mbn
$ fastboot reboot
You also have the option to erase all the data on your device with
$ fastboot erase userdata
$ fastboot erase cache
After performing this sequence, you can relock your device with
$ fastboot oem lock
[email protected] said:
I'm having the same trouble here.
The main problem is that it seems to be related to the impossibility to flash again or install new rom on the device.
When i try to follow the typical procedures on cmd, i get messages like:
>> writing 'partition'...
>> (bootloader) Security version downgrade
>> (bootloader) Image primary_gpt failed validation
>> (bootloader) Preflash validation failed
>> FAILED (remote failure)
And then I can't seem to move on to another rom (and relocking the device, as I wish to do after all this).
(when i said typical procedures is that i found on many places, such as the motorola official website, https :// motorola-global-portal.custhelp.com/app/standalone/bootloader/recovery-images#)
FLASH AND RELOCK YOUR DEVICE
After downloading the image for your device:
Make sure you have a Moto Pure Edition or a Developer Edition device.
Make sure you download the corresponding recovery image from the above portal.
To flash, put the phone in fastboot mode:
1. Power OFF your device
2. Then Power ON + Volume Down
Alternatively, you can reboot into fastboot mode if you have adb...adb reboot bootloader.
Next flash the images using fastboot:
$ fastboot flash partition gpt.bin
$ fastboot flash motoboot motoboot.img
$ fastboot reboot-bootloader
$ fastboot flash logo logo.bin
$ fastboot flash boot boot.img
$ fastboot flash recovery recovery.img
$ fastboot flash system system.img
$ fastboot flash modem NON-HLOS.bin
$ fastboot erase modemst1
$ fastboot erase modemst2
$ fastboot flash fsg fsg.mbn
$ fastboot reboot
You also have the option to erase all the data on your device with
$ fastboot erase userdata
$ fastboot erase cache
After performing this sequence, you can relock your device with
$ fastboot oem lock
Click to expand...
Click to collapse
I have exactly the same problem, has it been able to solve it?
How to solve it?
Same problem here
Can do nothing, phone always boots to fastboot no matter what I do/flash. It also states ID: bad key.
thoros1179 said:
Same problem here
Can do nothing, phone always boots to fastboot no matter what I do/flash. It also states ID: bad key.
Click to expand...
Click to collapse
Try typing "fastboot oem fb_mode_clear" inside the bootloader.
Related
Flashing to stock Android NPD90G from TWRP error: "remote: unsupported command"
Fixed flashing error "remote: unsupported command" when flashing a Pixel C back to stock
I used TWRP and SuperSU to root and modify the buildprops to enable and get an early look at the windowing in Android N beta on my Pixel C release 5 ahead of time.
When Release 5 NPD90G was available I decided to flash back to stock from Developer Preview 4 NPD56N rooted with SuperSU and flashed with TWRP. I like root - I run Ubuntu and Win 7. I don't mind running a rooted device if it doesn't have all my work and financial data. When the final N release is out, the Pixel C will become my work machine. It's almost there.
I'm naturally paranoid. I change my long passwords frequently and use 2 factor authentication for everything. So if I can, I'll take a stock release. See my instructions for wiping Android devices: How to wipe an Android Phone: the paranoid editon
I could not flash the NPD90G stock bootloader because of an error "remote: unsupported command"
Here's how I fixed it.
Updated the SDK manager including SDK Tools and USB drivers.
With the Pixel C in recovery mode, {hold the power key and volume down}
In TWRP mount System and reboot to recovery
>ADB Shell.
From ADB Shell I ran
>fwtool vbnv write dev_boot_fastboot_full_cap 1 to reenable Fast boot.
Then I changed from TWRP to Fastboot mode {power button plus hold the volume up button}
>fastboot erase userdata
>fastboot erase boot
>fastboot erase cache
>fastboot erase recovery
>fastboot erase system
See Note 1. Below
>fastboot flash bootloader bootloader-dragon-google_smaug.7900.27.0.img
>fastboot reboot-bootloader
>fastboot flash bootloader bootloader-dragon-google_smaug.7900.27.0.img
>fastboot reboot-bootloader
Note 1.
The first time through I flashed the following line items which resulted in the resting robot Andi. I don't think I needed to do this, but if the above instructions don't work, run the following before continuing for {flash bootloader bootloader-dragon-google_smaug.7900.27.0.img}
>flash bootloader bootloader-dragon-google_smaug.7900.27.0.img
>fastboot reboot-bootloader
>fastboot reboot-bootloader
>fastboot flash system system.img
>fastboot flash boot boot.img
>fastboot flash recovery recovery.img
>fastboot flash cache cache.img
Twrp can't flash
The problem is that I can't boot into the twrp because when i try to flash it the answer is failed unsupported remote command
Tugio said:
The problem is that I can't boot into the twrp because when i try to flash it the answer is failed unsupported remote command
Click to expand...
Click to collapse
When in fastboot mode, use:
Code:
fastboot boot twrp-local-file-on-computer.img
DanBUK said:
When in fastboot mode, use:
Click to expand...
Click to collapse
It's nice of you to help a fellow XDA user. But I suspect he's already solved his problem of three months ago.....
Hi guys
I have the same problem:
- the bootloader is unlocked (Coreboot menu says so)
- fastboot says "secure: yes" but "unlocked: yes" too
- "fastboot flashing get_unlock_ability" returns "1"
- "fastboot flashing unlock" says that the bootloader is already unlocked
But I have no recovery and if I try to fastboot boot recovery.img it fails with signature verification error
Can I do something to unbrick the device?
Regards
lllopa said:
Hi guys
I have the same problem:
- the bootloader is unlocked (Coreboot menu says so)
- fastboot says "secure: yes" but "unlocked: yes" too
- "fastboot flashing get_unlock_ability" returns "1"
- "fastboot flashing unlock" says that the bootloader is already unlocked
But I have no recovery and if I try to fastboot boot recovery.img it fails with signature verification error
Can I do something to unbrick the device?
Regards
Click to expand...
Click to collapse
My solution is very simple:
fastboot flashing lock
fastboot flashing unlock
fastboot reboot
And now let it boot.... and wait.
After the (failed) reboot check again: Now you can write all partitions... worked with my Pixel C
Make sure you have the latest version of fastboot and adb. I get these errors almost every month if I don't update.
https://developer.android.com/studio/releases/platform-tools.html
@stevep2007, thank you so much! I've been dealing with this "remote: unsupported command" nonsense for days now after trying to revert back to an older Oreo version of Lineage. This did the trick!
How can I solve the problem when my Pixel C is not unlocked? My Pixel made an update and after installing the Update I got the green little man. Now I have no Chance to activate USB debugging etc. Its also not possible to install twrp.img
How can I go to ADB shell with locked bootloader? Or isn't it possible?
Fastboot devices shows me my tablet. ADB devices also show my tablet with "sideload".
But every try to flash my Pixel fails. I alway get the message .... remote: unknown command.......fastboot error: command failed
flash-all.bat showes that all "*.img are missing" error: command failed... unknown command etc.......
So any idea to get my Pixel working again? ADB shell would make it I think. But how with locked bootloader.
_Arne_ said:
My solution is very simple:
fastboot flashing lock
fastboot flashing unlock
fastboot reboot
And now let it boot.... and wait.
After the (failed) reboot check again: Now you can write all partitions... worked with my Pixel C
Click to expand...
Click to collapse
This did it for me!! Thanks much. I also updated platform-tools at the same time, who knows which did it
_Arne_ said:
My solution is very simple:
fastboot flashing lock
fastboot flashing unlock
fastboot reboot
And now let it boot.... and wait.
After the (failed) reboot check again: Now you can write all partitions... worked with my Pixel C
Click to expand...
Click to collapse
In the scenario described by @llopa this solution does not work.
In that scenario there are no solutions
bernardomarx said:
In the scenario described by @llopa this solution does not work.
In that scenario there are no solutions
Click to expand...
Click to collapse
Sorry replied incorrectly
Hi All,
Good day.
Need some help regarding the error I encounter when flashing raw file. The fastboot in my ZF2 text also turns to red which I guess there's something wrong with my zf2. Also when trying to use XFSTK downloader, I get error also. Kindly refer to the images below. Hoping someone could help me regarding this. Thank you so much.
Btw, my phone is currently on Stucked Asus Logo.
Can u boot into stock recovery?
yakub234go said:
Can u boot into stock recovery?
Click to expand...
Click to collapse
Always looping in error and Installing update when I enter recovery mode.
pinuno said:
Always looping in error and Installing update when I enter recovery mode.
Click to expand...
Click to collapse
very first of all stay away from xfst if you are able to go into fastboot
download raw firmware. after that i will tell you commands you have to run step by step
I already have raw file but when I try to flash the raw file via Asus Flashtool, I alway get GPT command failed error.
pinuno said:
I already have raw file but when I try to flash the raw file via Asus Flashtool, I alway get GPT command failed error.
Click to expand...
Click to collapse
just go to fastboot and run following commands. don't use flash tool.
1. fastboot devices ( see if it is recognized: else plug out usb and plugin again)
fastboot oem unlock
2. fastboot oem erase_osip_header
3. fastboot oem erase_token
4. fastboot oem start_partitioning
5. fastboot flash /tmp/partition.tbl partition.tbl
6. fastboot oem partition /tmp/partition.tbl
7. fastboot erase system
8. fastboot erase cache
9. fastboot erase data
10. fastboot erase APD
11. fastboot erase ADF
12. fastboot oem wipe splashscreen
13. fastboot oem stop_partitioning
14. fastboot flash fastboot droidboot_sign.bin
15. fastboot flash token PROD_BOM_Full.bin
16. fastboot flash ifwi ifwi-prod.bin
17. fastboot flash splashscreen splash_sign.bin
18. fastboot flash boot boot_sign.bin
19. fastboot flash recovery recovery_sign.bin
20. fastboot flash APD APD.img
21. fastboot flash system system.img
22. fastboot reboot
first boot may take long time. so have patience
GPT = Grand Partition Table
Beyond my knowledge unfortunately .
Keeping an eye on this thread to see if theres a fix .
Can you describe how you got into this state ?
pinuno said:
I already have raw file but when I try to flash the raw file via Asus Flashtool, I alway get GPT command failed error.
Click to expand...
Click to collapse
Maybe the file u r flashing is corrupt
pinuno said:
I already have raw file but when I try to flash the raw file via Asus Flashtool, I alway get GPT command failed error.
Click to expand...
Click to collapse
check your personal message folder
Im getting error when try to run 6. fastboot oem partition /tmp/partition.tbl which is GPT command failed error.
Also fastboot oem unlock is unknown command, need on help on this. Thanks,
pinuno said:
Im getting error when try to run 6. fastboot oem partition /tmp/partition.tbl which is GPT command failed error.
Also fastboot oem unlock is unknown command, need on help on this. Thanks,
Click to expand...
Click to collapse
Hi,
The same problem is occurring in my ze551ml.
I am in great trouble.
Does anyone know the solution?
ygwstr said:
Hi,
The same problem is occurring in my ze551ml.
I am in great trouble.
Does anyone know the solution?
Click to expand...
Click to collapse
flash raw with commands method. run all the commands even if some of them fails. see section how to flash raw without AFT.
https://forum.xda-developers.com/zenfone2/help/thead-bricked-phone-updating-to-mm-tips-t3452785
sukhwant717 said:
flash raw with commands method. run all the commands even if some of them fails. see section how to flash raw without AFT.
https://forum.xda-developers.com/zenfone2/help/thead-bricked-phone-updating-to-mm-tips-t3452785
Click to expand...
Click to collapse
Hi
Following the instructions, i changed "2.20.40.194" raw file to zip file and unzipped.
Then, i typed the following command in Commandprompt.
Failed at number 5 and 14, error indication wrote below.
but I typed 1 to 21.
1. fastboot devices
2. fastboot oem erase_osip_header
3. fastboot oem start_partitioning
4. fastboot flash /tmp/partition.tbl partition.tbl
5. fastboot oem partition /tmp/partition.tbl
failed remote gpt command failed
6. fastboot erase system
7. fastboot erase cache
8. fastboot erase data
9. fastboot erase APD
10. fastboot erase ADF
11. fastboot oem wipe splashscreen
12. fastboot oem stop_partitioning
13. fastboot flash splashscreen splash_sign.bin
14. fastboot flash token MFG_BOM_Full.bin
failed remote tee_token_write() call failed return=0xcab1200d
15. fastboot flash ifwi ifwi-prod.bin
16. fastboot flash boot boot_sign.bin
17. fastboot flash recovery recovery_sign.bin
18. fastboot flash fastboot droidboot_sign.bin
19. fastboot flash APD APD.img
20. fastboot flash system system.img
21. fastboot reboot
However, the loading state at startup is not fixed.
I waited for two hours, but the start screen remained loading.
ygwstr said:
Hi
Following the instructions, i changed "2.20.40.194" raw file to zip file and unzipped.
Then, i typed the following command in Commandprompt.
Failed at number 5 and 14, error indication wrote below.
but I typed 1 to 21.
1. fastboot devices
2. fastboot oem erase_osip_header
3. fastboot oem start_partitioning
4. fastboot flash /tmp/partition.tbl partition.tbl
5. fastboot oem partition /tmp/partition.tbl
failed remote gpt command failed
6. fastboot erase system
7. fastboot erase cache
8. fastboot erase data
9. fastboot erase APD
10. fastboot erase ADF
11. fastboot oem wipe splashscreen
12. fastboot oem stop_partitioning
13. fastboot flash splashscreen splash_sign.bin
14. fastboot flash token MFG_BOM_Full.bin
failed remote tee_token_write() call failed return=0xcab1200d
15. fastboot flash ifwi ifwi-prod.bin
16. fastboot flash boot boot_sign.bin
17. fastboot flash recovery recovery_sign.bin
18. fastboot flash fastboot droidboot_sign.bin
19. fastboot flash APD APD.img
20. fastboot flash system system.img
21. fastboot reboot
However, the loading state at startup is not fixed.
I waited for two hours, but the start screen remained loading.
Click to expand...
Click to collapse
no way to fix until you have UFI box or any other emmc repair box
sukhwant717 said:
no way to fix until you have UFI box or any other emmc repair box
Click to expand...
Click to collapse
Oh, what a thing.
In other words, my device really become a bricked?
If I get UFI BOX it means that I may be able to repair it.
But UFI BOX is very expensive for me.
sukhwant717 thanks for answering my question.
ygwstr said:
Oh, what a thing.
In other words, my device really become a bricked?
If I get UFI BOX it means that I may be able to repair it.
But UFI BOX is very expensive for me.
sukhwant717 thanks for answering my question.
Click to expand...
Click to collapse
absolutely that is for professional repair shops. i am still working on the issue for alternatives. will revert back once i get it worked
sukhwant717 said:
absolutely that is for professional repair shops. i am still working on the issue for alternatives. will revert back once i get it worked
Click to expand...
Click to collapse
Thank you
I hope you find another solution to this problem.
sukhwant717 said:
no way to fix until you have UFI box or any other emmc repair box
Click to expand...
Click to collapse
Hi, i have the same problem.
Is there a solution, now?
Thanks
Note :
Do not erase/flash Bootloader file preloader.img or preloader.bin
fastboot erase preloader
fastboot flash preloader preloader.img
Do not erase/flash partition table file pgpt.img/gpt.img or pgpt.bin/gpt.bin
fastboot erase pgpt or gpt
fastboot flash pgpt or gpt pgpt.img or gpt.img
About :
With this guide you will restore stock firmware and re-lock your device bootloader.This guide is from Moto E4 Mediatek variant SKU XT1760 but can work with any Moto E4 Variant. Just grab the partition info and partition name in fastboot mode with fastboot command "fastboot getvar all". But this step isn't necessary if you take backup with miracle tool. It will dump whole firmware in scatter format. So, no need to worry if you have a different variant of Moto E4
This guide will give you the following :
PHP:
<bootloader> : warranty (YES)
<bootloader> : unlocked (NO)
<bootloader> : secure (YES)
>> device unlocked (we cannot remove this warning !)
Requirement :
• Place all the firmware files here:
C:\Program Files\Minimal ADB and Fastboot\HERE
• A laptop/Desktop
• Unlocked Bootloader
• Enabled USB Debugging
• Moto E4 Any Variant
• USB Cable
• Minimal Adb & Fastboot Tool
• Miracle Tool
• Adb & Fastboot Commands
Step 1 : Boot into bootloader mode
Switch off your device
Hold power button and volume down button
When you see START release buttons
This is fastboot mode
Step 2 : Reboot into bootloader
Note : i recommended you to use a laptop than that of desktop. For continuous power supply. Fully charge your laptop battery.
Connect with USB Cable
Open fastboot command window
Type fastboot command:
PHP:
fastboot reboot bootloader
Now your device in fastboot mode
--- Do not disconnect ---
Step 3 : Flashing stock factory images
Type these fastboot commands:
Erasing partitions first
if you have a different variant of Moto E4, just write all the partitions name except bootloader(preloader) in a text file and replace them with the below partition names.
PHP:
fastboot erase boot
fastboot erase efuse
fastboot erase expdb
fastboot erase flashinfo
fastboot erase frp
fastboot erase hw
fastboot erase keystore
fastboot erase lk
fastboot erase logo
fastboot erase metadata
fastboot erase nvdata
fastboot erase nvram
fastboot erase oem
fastboot erase oemkeystore
fastboot erase otp
fastboot erase para
fastboot erase persist
fastboot erase proinfo
fastboot erase protect1
fastboot erase protect2
fastboot erase recovery
fastboot erase seccfg
fastboot erase secro
fastboot erase tee1
fastboot erase tee2
fastboot erase utags
fastboot erase system
fastboot erase userdata
--- Do not disconnect ---
Now flash stock factory images
PHP:
fastboot flash boot boot.img
fastboot flash efuse efuse.img
fastboot flash expdb expdb.img
fastboot flash flashinfo flashinfo.img
fastboot flash frp frp.img
fastboot flash hw hw.img
fastboot flash keystore keystore.img
fastboot flash lk lk.img
fastboot flash logo logo.img
fastboot flash metadata metadata.img
fastboot flash nvdata nvdata.img
fastboot flash nvram nvram.img
fastboot flash oem oem.img
fastboot flash oemkeystore oemkeystore.img
fastboot flash otp otp.img
fastboot flash para para.img
fastboot flash persist persist.img
fastboot flash proinfo proinfo.img
fastboot flash protect1 protect1.img
fastboot flash protect2 protect2.img
fastboot flash recovery recovery.img
fastboot flash seccfg seccfg.img
fastboot flash secro secro.img
fastboot flash tee1 tee1.img
fastboot flash tee2 tee2.img
fastboot flash utags utags.img
fastboot flash system system.img
--- Do not disconnect ---
Step 4 : Re-lock bootloader
Type this fastboot command
PHP:
fastboot oem lock
Hit volume up button
Again type fastboot command
PHP:
fastboot reboot
Step 5 : Fix for system image sparse chunk
Used only when fastboot command failed to write system in system partition else when you see "sparse chunk error" wait for 10 minutes. you will see 1/20 or something operations. if not or command ended up with chunk error than use this command.Use this fastboot command:
PHP:
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 system.img_sparsechunk.10
fastboot flash system system.img_sparsechunk.11
fastboot flash system system.img_sparsechunk.12
fastboot flash system system.img_sparsechunk.13
fastboot flash system system.img_sparsechunk.14
fastboot flash system system.img_sparsechunk.15
fastboot flash system system.img_sparsechunk.16
fastboot flash system system.img_sparsechunk.17
fastboot flash system system.img_sparsechunk.18
fastboot flash system system.img_sparsechunk.19
fastboot flash system system.img_sparsechunk.20
Step 6 : Do not use this fastboot command
PHP:
fastboot erase preloader
This will wipe bootloader from bootloader partition and your device ended up with permanent Hard brick.
Step 7 : Fix for bootloader(fastboot) drivers
if your device isn't recognized in fastboot mode, Download USB Drivers from below attachment. Select manually "android_winusb.inf" file while updating driver software.
Download Link :
https://drive.google.com/file/d/0B0Oo-yXGY-zUMG1XRG52dFZpV1k/view
Step 8 : How to dump stock firmware
Thread link below:
https://forum.xda-developers.com/moto-e4/how-to/how-to-backup-stock-rom-moto-e4-variants-t3654976
Guide to fix boot_dataerr in miracle tool if it failed to dump stock rom
Look at the log window in miracle tool there in driver part you will see MTK preloader USB COM PORT#7. We don't need Preloader driver right now, we need MTK Android DA USB COM PORT#7. The solution is update your device driver software to fix this problem else you won't able to dump firmware in scatter format also we don't have official factory images. This is the only method to revert on purely unrooted stock firmware.
Step 9 : Minimal Adb & Fastboot download link
https://androidmtk.com/download-minimal-adb-and-fastboot-tool
This is my last thread in Moto E4 forum and i won't support this device anymore.
Does this work for all variants?
andMego said:
Does this work for all variants?
Click to expand...
Click to collapse
yes, work with all variants.
already mentioned in OP.
kartik verma said:
This is my last thread in Moto E4 forum and i won't support this device anymore.
Click to expand...
Click to collapse
After you came here and cluttered the forum with a crap load of pointless threads and posts? I love it! Thanks.
amarc78 said:
After you came here and cluttered the forum with a crap load of pointless threads and posts? I love it! Thanks.
Click to expand...
Click to collapse
pointless threads and posts
so my posts are useless. sorry if my posts aren't fit into your expectation.
kartik verma said:
pointless threads and posts
so my posts are useless. sorry if my posts aren't fit into your expectation.
Click to expand...
Click to collapse
Personally I'm very thankful for this post, as I couldn't figure out how to do it myself. I was able to reflash stock and lock the bootloader but it wouldn't boot since it always said it was modified, so I just returned my previous e4 with the bootloader unlocked and the noverify thing flashed.
my phone refuses to verify boot.img
KyleBryant said:
my phone refuses to verify boot.img
Click to expand...
Click to collapse
will it asks for boot.sig or anything else. let me know
I figured it out
KyleBryant said:
I figured it out
Click to expand...
Click to collapse
How?
Motorola doesn't release verified boot images. The reason it wouldn't boot for me is because I forgot to flash the no verity file lol
KyleBryant said:
Motorola doesn't release verified boot images. The reason it wouldn't boot for me is because I forgot to flash the no verity file lol
Click to expand...
Click to collapse
How do I lock the bootloader and get it to verify the boot image?
No idea
andMego said:
How do I lock the bootloader and get it to verify the boot image?
Click to expand...
Click to collapse
fastboot oem lock (relock the bootloader)
their is nothing to do with boot image. verification is for system if you changed something and didn't disable verity " MOUNT FLAG /system ro wait,verify" your device ain't gonna boot into system.
dm-verity can be disabled by two ways either remove "verify" or change the default.prop values "ro.secure=0".
kartik verma said:
fastboot oem lock (relock the bootloader)
their is nothing to do with boot image. verification is for system if you changed something and didn't disable verity " MOUNT FLAG /system ro wait,verify" your device ain't gonna boot into system.
dm-verity can be disabled by two ways either remove "verify" or change the default.prop values "ro.secure=0".
Click to expand...
Click to collapse
Before I returned my other e4 I flashed the stock images with rsdlite and then did fastboot oem lock but then the phone wouldn't boot since it said it was modified so I had to unlock the bootloader again and flash the noverify thing in TWRP. How should I have done it to be able to return the phone with the bootloader locked?
andMego said:
Before I returned my other e4 I flashed the stock images with rsdlite and then did fastboot oem lock but then the phone wouldn't boot since it said it was modified so I had to unlock the bootloader again and flash the noverify thing in TWRP. How should I have done it to be able to return the phone with the bootloader locked?
Click to expand...
Click to collapse
" it said it was modified"
First of all remove all the changes you have done in system else if you don't know where you have done changes wipe system partition and reflash system image in system partition.
don't flash gpt.img, pgpt.img, bootloader.img in fastboot mode also do not erase data in fastboot mode "fastboot erase userdata". your device must be charged upto 80% if you want your device boot after a clean flash.
as i am also facing over discharged problem.
kartik verma said:
" it said it was modified"
First of all remove all the changes you have done in system else if you don't know where you have done changes wipe system partition and reflash system image in system partition.
don't flash gpt.img, pgpt.img, bootloader.img in fastboot mode also do not erase data in fastboot mode "fastboot erase userdata". your device must be charged upto 80% if you want your device boot after a clean flash.
as i am also facing over discharged problem.
Click to expand...
Click to collapse
Kartik dude tell me if this is possible....
To roll back I flash unmodified stock boot image and flash stock recovery through fastboot - reboot system - reset -relock bootloader.....can I able to do this?
drganbds said:
Kartik dude tell me if this is possible....
To roll back I flash unmodified stock boot image and flash stock recovery through fastboot - reboot system - reset -relock bootloader.....can I able to do this?
Click to expand...
Click to collapse
follow this method :
erase partitions only if you have factory images
fastboot erase recovery
fastboot flash recovery recovery.img
fastboot erase boot
fastboot flash boot boot.img
erase system if you done changes in system partition. if not leave this step
fastboot erase system
fastboot flash system system.img
kartik verma said:
follow this method :
erase partitions only if you have factory images
fastboot erase recovery
fastboot flash recovery recovery.img
fastboot erase boot
fastboot flash boot boot.img
erase system if you done changes in system partition. if not leave this step
fastboot erase system
fastboot flash system system.img
Click to expand...
Click to collapse
Excellent then do me a favour buddy I need stock recovery and unmodified boot images of Moto e4 mediatek variant.
drganbds said:
Excellent then do me a favour buddy I need stock recovery and unmodified boot images of Moto e4 mediatek variant.
Click to expand...
Click to collapse
i will upload official factory images when i get free time
friends, how are you?
It's the following .. I have a serious problem with my Moto G5.
When he went to do the update for Oreo he gave a problem ... Of which I can not leave.
It starts in fastboot mode or attempts to initialize Android but stops on screen (M) as picture.
The bootloader is locked, I tried to unlock by cmd and put the key sent by the motorola, signaled as if it worked and continues as (oem_locked).
I do not have root, my bootloader is locked, and I can not access recovery despite entering fastboot mode.
I tried installing several roms by adb, but I could not succeed with any (Always giving FAILED REMOTE).
Yesterday until it managed to enter the initial configuration of the android (where it places the wifi) but then restarted and never again.
I've tried everything a little bit, and I could not succeed with anything.
Help me, please, I do not know what else to do!
Thank you
:confuso:
You have a few options
The first is just wipe the phone and see if it boots
You can do this by putting the phone in bootloader mode (as per your screenshot) by holding Vol down & power button
Then in cmd/terminal window where you have fastboot on your pc type
fastboot erase userdata
Note this will delete everything on internal storage!
Then select the boot normally from bootloader menu
Another option is to flash the entire firmware via fastboot
You will need firmware which is the same or newer than what you currently have
You don't need an unlocked bootloader to flash stock firmware via fastboot
Note fastboot is different from adb - adb won't work in fastboot mode!
.....
My friend, I made the process using the rom of https://forum.xda-developers.com/g5/how-to/official-oreo-8-1-0-opp28-85-16-t3849244 except that excluding the (fastboot flash partition gpt.bin and
fastboot flash bootloader bootloader.img).
Similarly, the screen continues with the motorola logo, does not advance to android, recovery when I select and tighten the power, stay on the motorola screen and back to the fastboot.
The result of the process is this in the image
TheFixItMan said:
You have a few options
The first is just wipe the phone and see if it boots
You can do this by putting the phone in bootloader mode (as per your screenshot) by holding Vol down & power button
Then in cmd/terminal window where you have fastboot on your pc type
fastboot erase userdata
Note this will delete everything on internal storage!
Then select the boot normally from bootloader menu
Another option is to flash the entire firmware via fastboot
You will need firmware which is the same or newer than what you currently have
You don't need an unlocked bootloader to flash stock firmware via fastboot
Note fastboot is different from adb - adb won't work in fastboot mode!
Click to expand...
Click to collapse
sonmota said:
My friend, I made the process using the rom of https://forum.xda-developers.com/g5/how-to/official-oreo-8-1-0-opp28-85-16-t3849244 except that excluding the (fastboot flash partition gpt.bin and
fastboot flash bootloader bootloader.img).
Similarly, the screen continues with the motorola logo, does not advance to android, recovery when I select and tighten the power, stay on the motorola screen and back to the fastboot.
The result of the process is this in the image
Click to expand...
Click to collapse
You need to flash the ENTIRE stock firmware and it MUST be the same or newer than the version already on the phone
Plus you missed sparsechunk0
You got pre-flash validation errors as you are either using the wrong firmware or haven't flash the entire firmware from start to finish
Note if you flash wrong firmware you could potentially hard brick your device
Code:
fastboot oem fb_mode_set
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 dsp adspso.bin
fastboot flash oem oem.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 oem fb_mode_clear
fastboot reboot
....
I'm from Brazil and from what I've been observing the ROM would be with the same bases as this one from the link.
I refined the process using the command lines you posted and "FAILED REMOTE" is repeated in some lines.
Would not it be some case of partitioning the corrupted system?
Follow the pictures below.
TheFixItMan said:
You need to flash the ENTIRE stock firmware and it MUST be the same or newer than the version already on the phone
Plus you missed sparsechunk0
You got pre-flash validation errors as you are either using the wrong firmware or haven't flash the entire firmware from start to finish
Note if you flash wrong firmware you could potentially hard brick your device
Code:
fastboot oem fb_mode_set
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 dsp adspso.bin
fastboot flash oem oem.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 oem fb_mode_clear
fastboot reboot
Click to expand...
Click to collapse
sonmota said:
I'm from Brazil and from what I've been observing the ROM would be with the same bases as this one from the link.
I refined the process using the command lines you posted and "FAILED REMOTE" is repeated in some lines.
Would not it be some case of partitioning the corrupted system?
Follow the pictures below.
Click to expand...
Click to collapse
Gpt failed because the firmware you are trying to flash is older than what is currently on your phone
Gpt is needed to repartition your phone and must be flashed along with the bootloader
You will need to download firmware which is equal to or newer than what is already on your phone
I saw there was an October update in the ROM. I will try here in the community this ROM and try to blink and bring the result here ..
friend .. I followed the rom .. I did the whole process (without FAILED) but when it starts up it gets frozen in the Motorola logo.
Any tips on what it might be?
TheFixItMan said:
Gpt failed because the firmware you are trying to flash is older than what is currently on your phone
Gpt is needed to repartition your phone and must be flashed along with the bootloader
You will need to download firmware which is equal to or newer than what is already on your phone
Click to expand...
Click to collapse
sonmota said:
friend .. I followed the rom .. I did the whole process (without FAILED) but when it starts up it gets frozen in the Motorola logo.
Any tips on what it might be?
Click to expand...
Click to collapse
As long as everything flashed correctly and the entire firmware had no errors I'd go into stock recovery and perform a factory reset
Hold Vol down & power button
At bootloader menu use volume keys to navigate to recovery and press power button to select
At the Android screen with no command push and hold power button then with power button held then press Vol up
You are now in recovery mode
Use Vol keys with goto wipe data/factory reset & power button to select
If the rom doesn't boot after that chances are you didn't flash the firmware correctly or there was an error in flashing it due to the wrong firmware used
I can not get into recovery. Would not it be a problem with the motherboard?
TheFixItMan said:
As long as everything flashed correctly and the entire firmware had no errors I'd go into stock recovery and perform a factory reset
Hold Vol down & power button
At bootloader menu use volume keys to navigate to recovery and press power button to select
At the Android screen with no command push and hold power button then with power button held then press Vol up
You are now in recovery mode
Use Vol keys with goto wipe data/factory reset & power button to select
If the rom doesn't boot after that chances are you didn't flash the firmware correctly or there was an error in flashing it due to the wrong firmware used
Click to expand...
Click to collapse
sonmota said:
I can not get into recovery. Would not it be a problem with the motherboard?
Click to expand...
Click to collapse
Could well be
As long as gpt flashed successfully without giving a downgrade warning which will call it to fail then the recovery part of the firmware should flash and you should have access to recovery mode via entering recovery from bootloader then holding power button and volume up at the picture of the android screen
It could be a motherboard issue but since you have no problem getting into bootloader it's more likely a firmware issue/user error
I've been disappointed with some of the firmware here, like Lineage and Arrow. Havoc has been my favorite, but when we transitioned from Havoc Android 10 (3.*) to Android 11 (4.*) I have lost LTE every morning, which means no texts, no data, no phone calls. I have to power down and up and who knows when I'd lose LTE again.
Also with TWRP I could not slide the unock, and trying to select files the screen mapping is all wrong, meaning I'd touch a file at the bottom and a file toward the top would be selected. I don't know why the problems were because no one has ever been able to communicate the structure and framework of Android coherently. It seems that most just know parts of it intuitively, not the whole intellectually.
So I have to resort to Stock. I thought maybe installing Stock then Havoc 4.8 would solve the LTE problem, but when doing that Havoc's boot just circles around forever.
So without further adieu here is how to install Stock on your Moto G Power. Mine is US T-Mobile on an XT2041-4.
Get the firmware here: https://mirrors.lolinet.com/firmware/moto/sofia/official/
I hit RETUS and RETUS_10 for Retail US Android 10. If you have a different carrier or nation try and decipher which is right for you. Use 10 as Beetle says below. (as of Jan, 2022, Havoc 4.12)
Unzip this file into its own directory and you will get a series of images and .xml files. Boot your phone into fastboot mode by turning it off, then hold {VolDown}{Power} at the same time to go into fastboot mode. In this case you do -not- then reboot into fastbootd mode! Just leave it like this and connect to your computer.
Code:
# fastboot devices
... should give you something like
Code:
ZY227VX6NG fastboot
Good, your computer sees the phone.
Go into the firmware directory. A key file here is flashfile.xml. This tells you exactly how these image files must be applied to the phone and in what order. I'll show below the files and procedure for my phone, but yours may be different so refer to that flashfile for your firmware.
The first file to flash is important. It sets up the partitions on the phone properly:
Code:
# fastboot flash partition gpt.bin
Now just work your way down flashfile. Here's mine:
Code:
# fastboot flash bootloader bootloader.img
# fastboot flash vbmeta vbmeta.img
# fastboot flash radio radio.img
# fastboot flash bluetooth BTFM.bin
# fastboot flash dsp dspso.bin
# fastboot flash logo logo.bin
# fastboot flash boot boot.img
# fastboot flash dtbo dtbo.img
# fastboot flash recovery recovery.img
# fastboot flash super super.img_sparsechunk.0
# fastboot flash super super.img_sparsechunk.1
# fastboot flash super super.img_sparsechunk.2
# fastboot flash super super.img_sparsechunk.3
# fastboot flash super super.img_sparsechunk.4
# fastboot flash super super.img_sparsechunk.5
# fastboot flash super super.img_sparsechunk.6
# fastboot flash super super.img_sparsechunk.7
# fastboot flash super super.img_sparsechunk.8
# fastboot flash super super.img_sparsechunk.9
# fastboot flash super super.img_sparsechunk.10
# fastboot flash super super.img_sparsechunk.11
# fastboot flash super super.img_sparsechunk.12
# fastboot flash super super.img_sparsechunk.13
# fastboot flash super super.img_sparsechunk.14
# fastboot flash super super.img_sparsechunk.15
# fastboot erase carrier
# fastboot erase userdata
# fastboot erase metadata
# fastboot erase ddr
# fastboot oem fb_mode_clear
And that's it. Reboot. It will take a while the first time so don't interrupt it. You're back to stock.
If you were trying to flash havoc over android 11 firmware, it wont work. These roms need android 10 as a base.
Ah, that explains it. I think Havoc is the best, but 4.6 and 4.8 reliably drop LTE for me mornings. It's caused business problems.
I now find that it's impossible to tear G**gle out of Stock, so that's out for me. Maybe Arrow or something.
What carrier do you have? I'm getting ready to put maybe Havoc or Linage on this phone, but need to know what to watch out for.
It seems to be like Android 11 is a common denominator in a lot of the issues I've seen people having. That's why I have no intention of even moving to a custom rom based on 11 for a good while. I'll be staying at Lineage 17 or Havoc 3 until I have no other choice. There's nothing in 11 I need or want, and that will probably be true for 12 and 13 and so on. As for de-googling Android, that's likely going to just get harder and harder with each version.
I seem to be the only one having problems with Android 11 afaict. Haven't seen anyone else posting issues. Decided it's something about my phone, but laying down 11 stock reset everything. I just can't run Havoc anymore.
I highly recommend Havoc 3.*.
I wonder whether laying down Android 10 would fix my issues with Havoc 4.*?
I went back to stock for the same reason as OP. As far as de-googling, it's a chore to get it to a point where I feel a bit comfortable turning wi-fi on, but I'm not very comfortable. Basically I disable all google stuff, including the play store, prevent the google apps installed post-setup, remove permissions from play services, turn off networking for it and everything else, go through settings to disable 'functions' , I use the keepass2android app's keyboard, install a different sms app, keep contacts to device, and firewall everything - I don't allow much networking functionality at all. Of course, I'm rooted., I also use app manager to disable trackers and disable "0" which is 'rough' location for all apps, system included - I eneble it for weather. I use aurora and f-droid for apps, but, mostly just reinstall from dumps. Also, I don't use a lot of apps and for my feng shui, the device (and my edge) works well. I'm likely leaving out a bunch of little tweaks that I do, apologies.
I use nextcloud, adaway, sms backup and restore, acalendar+, fx, firefox focus or bromite, pi-hole is on my LAN. ON my edge, with lineage (17) and tweaked 'my way', I feel reasonably safe. On my g power with stock, tweaked, I feel a little naked. Whereas I'm not shy, I am private. My g power mostly stays turned off kept in a drawer in my office.
I've been running CrDroid (google-free) v7.7 (android 11) with good results. I have data turned off on this screenshot, but have used it in limited amounts (my current plan allows only 1G per month). BTW, I'm on Red Pocket GSMA (ATT).
So I've cleared the decks by laying down Stock Android 10, then installing Havoc 4.8.
If I lose data tomorrow morning I will have to use another firmware, although I'm confident.
+1 on aCalendar+ and its beautiful widget, and add CalendarNotifications for nice popup.
I use SuperBackups to back up apps and call logs to SD card, and also AppBackupRestore just to be sure. Everything on the SD card was preserved during all these latest calisthenics, thankfully, including after the fastboot erases.
I've set up a Davical server at home for calendar and contacts sync, and on the phone DAVx5 to communicate with it. It's a faff to set up, but such a joy to know my calendars and contacts are always synced with home, once set up. (Thunderbird+Lightning for now, maybe soon Kontact)
The phone does all internet access through a WireGuard tunnel to home WG server virtual machine (interface: inWG), and then out the outWG interface to come out appearing that I'm in Switzerland or Spain, using AzireVPN service.
For Android firewall I use the fine AFWall+ and its little on/off widget, and for apps I always try F-Droid first then APKPure. Browser is Vivaldi. To transfer files with LAN I connect with wifi then use SSHDroid as SSH server on the phone and sshfs on the server to mount the phone. (SSHDroid is worrisomely getting old)
Also I use Nova as desktop renderer. I have 5 phone desktops and it takes me a day to rebuild everything with the standard Havoc desktop (Shady Launcher), no offense SkullShady. Nova lets you back up and restore all settings, including complete desktops setup, which is such a pleasure.
G**gle-less. G**gle-free. Sans G**gle. In my Postfix server I kick back all gmail messages with, "THANK YOU FOR SENDING THIS, BUT GMAIL IS CONSIDERED A SECURITY PROBLEM. PLEASE RE-SEND FROM ANOTHER ACCOUNT."
Good sign - I have data this morning.
Deleted. Thank you.
Worked like a charm. Followed this guide, then ran fastboot oem lock, to prepare a phone to give away. Thank you.
I extracted the files straight to my platform-tools folder to simplify.
Quantumstate said:
Good sign - I have data this morning.
Click to expand...
Click to collapse
Remember me? I still have my Sofia, but it's running stock A11 and Nova Launcher 6.2.9 rather that 7x which screws with my Android widgets. So, I've set the Play Store not to auto update apps to keep 6.2.9. This setup is OK, but I'd rather root it, install TWRP, and an updateable/upgradeable custom ROM. Can you offer some step-by-step guidance?
Thanks
jhford said:
Remember me? I still have my Sofia, but it's running stock A11 and Nova Launcher 6.2.9 rather that 7x which screws with my Android widgets. So, I've set the Play Store not to auto update apps to keep 6.2.9. This setup is OK, but I'd rather root it, install TWRP, and an updateable/upgradeable custom ROM. Can you offer some step-by-step guidance?
Thanks
Click to expand...
Click to collapse
Sure I remember you. I just did an install of beetle84's last version of Havoc as above, and as per the directions in his thread, it's worked ever since. Only glitch is I lose mobile data every morning, but just power down and reboot.
I'm afraid of this version as I tried and tried but could not make it work. Phone was down for days.
Beetle84 said:
If you were trying to flash havoc over android 11 firmware, it wont work. These roms need android 10 as a base.
Click to expand...
Click to collapse
I'm researching if I can flash XT2041-4_SOFIA_RETUS_10_QPMS30.80-109-5_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip onto my unrooted Android 11 phone, an XT2041-4 that was Android 10 but now Android 11.
I'm not familiar with havoc so I'm curious what you mean. Is that image flashable to my phone or am I wanting to flash havoc over android 11 firmware?
I followed the steps in the oP and bricked my device. I didn't unlock the bootloader so if you follow the tutorial above be sure to unlock the bootloader before wiping the partition.
If anyone knows how to recover from that point I'd appreciate any help. I have the unlock code but I didn't enable unlocking the bootloader before wiping the partition as I didn't know I needed to do that so I hosed myself.
powershift said:
I followed the steps in the oP and bricked my device. I didn't unlock the bootloader so if you follow the tutorial above be sure to unlock the bootloader before wiping the partition.
If anyone knows how to recover from that point I'd appreciate any help. I have the unlock code but I didn't enable unlocking the bootloader before wiping the partition as I didn't know I needed to do that so I hosed myself.
Click to expand...
Click to collapse
Are you still able to boot to the bootloader menu using hardware keys? You should be able to continue unlocking it regardless of what you wiped. Either way that shouldn't stop you from being able to flash the stock rom.
What exactly are you stuck on now?
TaZeR369 said:
Are you still able to boot to the bootloader menu using hardware keys? You should be able to continue unlocking it regardless of what you wiped. Either way that shouldn't stop you from being able to flash the stock rom.
What exactly are you stuck on now?
Click to expand...
Click to collapse
It wouldn't unlock in fastboot. What I did was I downloaded Android 11 and flashed it, then did the boot loader unlock.
But when applying stock Android 10 w/out errors during the flash, on boot the blue Motorola splash screen shows, it acts like it is booting then it reboots and the blue screen goes away and comes back. It will do that boot loop all day. I had to revert back to Android 11, but at least the phone boots now although I'd still like to get Android 10 on there as I'm not at all a fan of V11.
powershift said:
It wouldn't unlock in fastboot. What I did was I downloaded Android 11 and flashed it, then did the boot loader unlock.
But when applying stock Android 10 w/out errors during the flash, on boot the blue Motorola splash screen shows, it acts like it is booting then it reboots and the blue screen goes away and comes back. It will do that boot loop all day. I had to revert back to Android 11, but at least the phone boots now although I'd still like to get Android 10 on there as I'm not at all a fan of V11.
Click to expand...
Click to collapse
I think maybe you should try to flash stock android 10 image again. It's the kind of error that happened to me when I missed a step or forgot a command and looking over your post I think there is something missing or added that shouldn't be there. Also don't flash anything like magisk or twrp along with it, wait until the first boot for anything more.
Heres whats always worked for me (same model phone):
fastboot getvar max-sparse-size
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash vbmeta vbmeta.img
fastboot flash radio radio.img
fastboot flash bluetooth BTFM.bin
fastboot flash dsp dspso.bin
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash dtbo dtbo.img
fastboot flash recovery recovery.img
fastboot flash super super.img_sparsechunk.0
fastboot flash super super.img_sparsechunk.1
fastboot flash super super.img_sparsechunk.2
fastboot flash super super.img_sparsechunk.3
fastboot flash super super.img_sparsechunk.4
fastboot flash super super.img_sparsechunk.5
fastboot flash super super.img_sparsechunk.6
fastboot flash super super.img_sparsechunk.7
fastboot flash super super.img_sparsechunk.8
fastboot flash super super.img_sparsechunk.9
fastboot flash super super.img_sparsechunk.10
fastboot flash super super.img_sparsechunk.11
fastboot flash super super.img_sparsechunk.12
fastboot flash super super.img_sparsechunk.13
fastboot flash super super.img_sparsechunk.14
fastboot flash super super.img_sparsechunk.15
fastboot erase carrier
fastboot erase userdata
fastboot erase metadata
fastboot erase ddr
fastboot oem fb_mode_clear
fastboot reboot
TaZeR369 said:
I think maybe you should try to flash stock android 10 image again. It's the kind of error that happened to me when I missed a step or forgot a command and looking over your post I think there is something missing or added that shouldn't be there. Also don't flash anything like magisk or twrp along with it, wait until the first boot for anything more.
Heres whats always worked for me (same model phone):
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash vbmeta vbmeta.img
fastboot flash radio radio.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash dtbo dtbo.img
fastboot flash recovery recovery.img
fastboot flash super super.img_sparsechunk.0
fastboot flash super super.img_sparsechunk.1
fastboot flash super super.img_sparsechunk.2
fastboot flash super super.img_sparsechunk.3
fastboot flash super super.img_sparsechunk.4
fastboot flash super super.img_sparsechunk.5
fastboot flash super super.img_sparsechunk.6
fastboot flash super super.img_sparsechunk.7
fastboot flash super super.img_sparsechunk.8
fastboot flash super super.img_sparsechunk.9
fastboot flash super super.img_sparsechunk.10
fastboot flash super super.img_sparsechunk.11
fastboot flash super super.img_sparsechunk.12
fastboot flash super super.img_sparsechunk.13
fastboot flash super super.img_sparsechunk.14
fastboot flash super super.img_sparsechunk.15
fastboot erase userdata
fastboot erase ddr
fastboot flash dsp dspso.bin
fastboot oem fb_mode_clear
fastboot reboot
Click to expand...
Click to collapse
That is what my script looks like with one exception, I can't run the flash bootloader bootloader.img successfully because it fails validation. All other steps succeed. Did you have Android 11 bootloader on there and put the Android 10 bootloader back?
In addition to those steps, I tried fastboot getvar max-sparse-size before all others and still no joy. I think the Android 11 bootloader doesn't boot Android 10 and I don't know how to reflash it back to the old bootloader even while unlocked.
Code:
[email protected]:~/android$ sudo /home/anon/android/platform-tools/fastboot oem unlock 2T4ETJZNOSHSA324GL6G
(bootloader) Bootloader is unlocked!
OKAY [ 15.676s]
Finished. Total time: 15.676s
[email protected]:~/android$
[email protected]:~/android/moto_stock_android10$ sudo /home/anon/android/platform-tools/fastboot flash bootloader bootloader.img
Sending 'bootloader' (14204 KB) OKAY [ 0.557s]
Writing 'bootloader' (bootloader) Validating 'bootloader.default.xml'
(bootloader) Preflash validation failed
(bootloader) Preflash validation failed
(bootloader) Cancelling 'bootloader.default.xml'
FAILED (remote: '')
fastboot: error: Command failed
[email protected]:~/android/moto_stock_android10$
powershift said:
That is what my script looks like with one exception, I can't run the flash bootloader bootloader.img successfully because it fails validation. All other steps succeed. Did you have Android 11 bootloader on there and put the Android 10 bootloader back?
In addition to those steps, I tried fastboot getvar max-sparse-size before all others and still no joy. I think the Android 11 bootloader doesn't boot Android 10 and I don't know how to reflash it back to the old bootloader even while unlocked.
Code:
[email protected]:~/android$ sudo /home/anon/android/platform-tools/fastboot oem unlock 2T4ETJZNOSHSA324GL6G
(bootloader) Bootloader is unlocked!
OKAY [ 15.676s]
Finished. Total time: 15.676s
[email protected]:~/android$
[email protected]:~/android/moto_stock_android10$ sudo /home/anon/android/platform-tools/fastboot flash bootloader bootloader.img
Sending 'bootloader' (14204 KB) OKAY [ 0.557s]
Writing 'bootloader' (bootloader) Validating 'bootloader.default.xml'
(bootloader) Preflash validation failed
(bootloader) Preflash validation failed
(bootloader) Cancelling 'bootloader.default.xml'
FAILED (remote: '')
fastboot: error: Command failed
[email protected]:~/android/moto_stock_android10$
Click to expand...
Click to collapse
It does flash back, I've done it a few times, I didn't have any difficulty. You said you unlocked the bootloader before, but you seem to be entering the code to unlock it again each time you try to flash or? Because once its unlocked you shouldn't be needing to do oem unlock anymore, unless you've locked it again. Also what distro are you using and adb package?
There may be some verification problem here if something is not fully unlocked for some reason, so just to clarify the first time you flashed android 10 over 11 you also had the bootloader failed error, or is this now on the second try?
Perhaps if all else fails can try to change to the next active slot like b, and try to flash there in case something maybe the partition table got screwed up somehow (at the start) "fastboot set_active b", cold booting with a twrp image may be able to fix it in that case.
I mean unless there is some kind of new protection in the lastest versions of 11 that i dont know about...? Maybe as a last resort reflash android 11 but the first version after 10, and then try to downgrade from that? I dunno man sorry... some stuff to think about...