Hi everyone, couldn't find anything relevant on the internet and the forum about the rollback problem, there is any way to install custons ROMs with that anabled? since i bought my moto g8 power mid last year i never could install any custom rom because of that, fastboot always give me anti-rollbakc warning and won't flash some partitons so it always ended up bootlooping and i go back to stock, there is any way to disable that feature? or bypass, how can i solve this problem?
Below is the fastboot log of what usually happens.
Code:
writing 'vbmeta_a'...
(bootloader) WARNING: vbmeta_a anti rollback downgrade, 10 vs 14
OKAY [ 0.007s]
finished. total time: 0.017s
Here are the full version of the previous log i posted, i was trying to install the HavocOS via fastboot
Code:
C:\Users\henri\Documents\Minimal ADB and Fastboot>fastboot flash boot boot.img
target reported max download size of 805261312 bytes
sending 'boot_a' (65536 KB)...
OKAY [ 1.519s]
writing 'boot_a'...
OKAY [ 1.058s]
finished. total time: 2.579s
C:\Users\henri\Documents\Minimal ADB and Fastboot>fastboot flash product product.img
target reported max download size of 805261312 bytes
sending sparse 'product_a' 1/3 (720896 KB)...
OKAY [ 17.117s]
writing 'product_a' 1/3...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 17.121s
C:\Users\henri\Documents\Minimal ADB and Fastboot>fastboot flash system system.img
target reported max download size of 805261312 bytes
sending sparse 'system_a' 1/2 (720896 KB)...
OKAY [ 17.125s]
writing 'system_a' 1/2...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 17.129s
C:\Users\henri\Documents\Minimal ADB and Fastboot>fastboot flash vbmeta vbmeta.img
target reported max download size of 805261312 bytes
sending 'vbmeta_a' (4 KB)...
OKAY [ 0.009s]
writing 'vbmeta_a'...
(bootloader) WARNING: vbmeta_a anti rollback downgrade, 0 vs 14
OKAY [ 0.011s]
finished. total time: 0.020s
You definitely are in fastboot d? Not just the bootloader?
When you are flashing the inages, if you have a green robot and some text down the bottom, that is fastboot/bootloader.
Fastboot d is different, you will definitely know if you are in fastboot d.
Beetle84 said:
You definitely are in fastboot d? Not just the bootloader?
When you are flashing the inages, if you have a green robot and some text down the bottom, that is fastboot/bootloader.
Fastboot d is different, you will definitely know if you are in fastboot d.
Click to expand...
Click to collapse
That was on bootloader, i searched about the fastboot d but couldn't find any explanation/tutorial how to enter it, i tried the command fastboot reboot fastboot but it gives unknown fastboot target, can you help me?
Fastboot reboot fastboot is the correct way from the bootloader.
You need to update your platform tools.
Also you need to be on android 10 for these roms to boot.
One of the guys helped me out with this earlier. After you've unlocked your boot loader and if your on android 11.
Use rescue & smart assistant to backup your stock rom, it will tell you what kind it is too....
Then go download the android 10 stock version.
Then use moto tools by vache and load the android 10 stock rom into it. Just follow the directions and place it in bootloader.
after that flash whatever puppy of your choosing. Also I'd advise against flashing twrp just boot it. Also if you do use twrp, make sure you don't reboot from side B! you will brick your device....
Beetle84 said:
Fastboot reboot fastboot is the correct way from the bootloader.
You need to update your platform tools.
Also you need to be on android 10 for these roms to boot.
Click to expand...
Click to collapse
That solved all the problem i was facing, thanks
revengesrage said:
One of the guys helped me out with this earlier. After you've unlocked your boot loader and if your on android 11.
Use rescue & smart assistant to backup your stock rom, it will tell you what kind it is too....
Then go download the android 10 stock version.
Then use moto tools by vache and load the android 10 stock rom into it. Just follow the directions and place it in bootloader.
after that flash whatever puppy of your choosing. Also I'd advise against flashing twrp just boot it. Also if you do use twrp, make sure you don't reboot from side B! you will brick your device....
Click to expand...
Click to collapse
Thansk for the tips, it is really important to set the partitions, i was struggling a lot to boot system since twrp redirected things to side B while A was set, i don't know why but now everthing is running flawlessly
Related
Stuck in "Your device has been unlocked and can't be trusted. […] ID: bad key"
I wanted to root the device but I now I have a device that doesn't boot anymore.
What I've done so far wasn't this much:
unlocked bootloader (fastboot oem get_unlock_data and fastboot oem unlock)
flashed TWRP (fastboot flash recovery twrp-3.0.2-0-griffin.img)
I bootet into the system, downloaded Magisk because I was going to root the device. I bootet into Recovery / TWRP and saw that I wasn't able to find the download folder where I downloaded Magisk. I rebootet and since then I can't boot into the system again.
Fastboot and recovery are possible tough. When I'm trying to boot regulary the device is stuck in:
Code:
Your device has been unlocked and can't be trusted.
To learn more, visit:
motorola.com/unlockbootloader
ID: bad key
Your device will boot in 5 seconds.
It looks pretty much like this except the ID ('N/A' in the image but 'bad key' on my mobile).
But it never boots. Before TWRP the screen appears as well but at least it is booting into TWRP.
Clearing cache didn't help neither.
Any idea what could help?
PS: I changed the clock in TWRP to 24h format but I guess this should brake anything — right?
PPS: I also tried to flash some official image (XT1650-03_GRIFFIN_RETEU-EMEA_6.0.1_MPL24.246-17_cid50_subsidy-DEFAULT_regulatory-03_CFC_EMEA) I found here somewhere but it failed with an error message that it won't downgrade security and therefore not flash. Perhaps because I upgraded to Android 7 when I got the mobile?
PPPS: I found a thread on another board with the same problem but no solution
hackepeterbroetchen said:
I wanted to root the device but I now I have a device that doesn't boot anymore.
What I've done so far wasn't this much:
unlocked bootloader (fastboot oem get_unlock_data and fastboot oem unlock)
flashed TWRP (fastboot flash recovery twrp-3.0.2-0-griffin.img)
I bootet into the system, downloaded Magisk because I was going to root the device. I bootet into Recovery / TWRP and saw that I wasn't able to find the download folder where I downloaded Magisk. I rebootet and since then I can't boot into the system again.
Fastboot and recovery are possible tough. When I'm trying to boot regulary the device is stuck in:
Code:
Your device has been unlocked and can't be trusted.
To learn more, visit:
motorola.com/unlockbootloader
ID: bad key
Your device will boot in 5 seconds.
It looks pretty much like this except the ID ('N/A' in the image but 'bad key' on my mobile).
But it never boots. Before TWRP the screen appears as well but at least it is booting into TWRP.
Clearing cache didn't help neither.
Any idea what could help?
PS: I changed the clock in TWRP to 24h format but I guess this should brake anything — right?
PPS: I also tried to flash some official image (XT1650-03_GRIFFIN_RETEU-EMEA_6.0.1_MPL24.246-17_cid50_subsidy-DEFAULT_regulatory-03_CFC_EMEA) I found here somewhere but it failed with an error message that it won't downgrade security and therefore not flash. Perhaps because I upgraded to Android 7 when I got the mobile?
PPPS: I found a thread on another board with the same problem but no solution
Click to expand...
Click to collapse
Had the same issue and figured it out:
https://forum.xda-developers.com/showpost.php?p=72005245&postcount=185
doree said:
Had the same issue and figured it out:
https://forum.xda-developers.com/showpost.php?p=72005245&postcount=185
Click to expand...
Click to collapse
But I didn't flash another rom yet at all. I just flashed TWRP recovery image so far. Are you sure that you had the same issue?
hackepeterbroetchen said:
But I didn't flash another rom yet at all. I just flashed TWRP recovery image so far. Are you sure that you had the same issue?
Click to expand...
Click to collapse
I wouldn't reply if I wasn't.
You should have rebooted the device after unlocking the device, because it gets wiped after the process. Since you flashed TWRP right after unlocking it, you left the device wiped, therefore there's no system to gain access to. That's the reason you're stuck.
Hm Im stuck at the same screen. My question is just, how can I flash the Rom if the phones not booting and I dont get the Zip on the phone? Recovery and Bootloader works, but no system start. And unfortunately your link only shows 404: https://firmware.center/firmware/Motorola/Moto Z/Stock/XT1650-03/
Thanks for you help!
(Found this link tho: https://mirrors.lolinet.com/firmware/moto/addison/official/RETBR/)
Ah, I think I understand. So now I should flash the stock image again and redo the things (but with rebooting between the steps) - is that correct?
In that case I just need a flashable image. As I wrote in the PS of the first post I tried to flash the original stock rom but I didn't work.
And I can't find an image for (the PHP script complaints about wrong parameters):
• Model: XT1650
• Software-Version: Blur_Version.25.221.12.griffin.re
• Carrier: reteu
doree said:
Had the same issue and figured it out:
https://forum.xda-developers.com/showpost.php?p=72005245&postcount=185
Click to expand...
Click to collapse
doree said:
I wouldn't reply if I wasn't.
You should have rebooted the device after unlocking the device, because it gets wiped after the process. Since you flashed TWRP right after unlocking it, you left the device wiped, therefore there's no system to gain access to. That's the reason you're stuck.
Click to expand...
Click to collapse
And if I want to sideload it says Invaild zip file Format in recovery and
Code:
C:\adb>adb sideload xt1635.zip
loading: 'xt1635.zip'
error: device '(null)' not found
C:\adb>adb sideload xt1635.zip
Total xfer: 0.00x
in cmd. :S
nighteeeeeY said:
Hm Im stuck at the same screen. My question is just, how can I flash the Rom if the phones not booting and I dont get the Zip on the phone? Recovery and Bootloader works, but no system start. And unfortunately your link only shows 404: https://firmware.center/firmware/Motorola/Moto Z/Stock/XT1650-03/
Thanks for you help!
(Found this link tho: https://mirrors.lolinet.com/firmware/moto/addison/official/RETBR/)
Click to expand...
Click to collapse
It shows 404 because the Site ran out of Traffic. The Info is on the frontpage. Do NOT flash the stuff you posted, because it's for a different model.
hackepeterbroetchen said:
Ah, I think I understand. So now I should flash the stock image again and redo the things (but with rebooting between the steps) - is that correct?
In that case I just need a flashable image. As I wrote in the PS of the first post I tried to flash the original stock rom but I didn't work.
And I can't find an image for (the PHP script complaints about wrong parameters):
• Model: XT1650
• Software-Version: Blur_Version.25.221.12.griffin.re
• Carrier: reteu
Click to expand...
Click to collapse
Yep, you can't flash the Image, because you already updated your Bootloader to 7.0 Nougat. Therefore a flash attempt of the Image you mentioned will fail. It only works with a 6.0 Bootloader, since it's an 6.0 Stock Image.
nighteeeeeY said:
And if I want to sideload it says Invaild zip file Format in recovery and
Code:
C:\adb>adb sideload xt1635.zip
loading: 'xt1635.zip'
error: device '(null)' not found
C:\adb>adb sideload xt1635.zip
Total xfer: 0.00x
in cmd. :S
Click to expand...
Click to collapse
You need to Install ADB, boot into the Bootloader, unpack the Image I mentioned and execute the fastboot command I mentioned in the othet Post.
// Wait a sec. I will repack the stock image and will add the needed Stuff for you all.
hackepeterbroetchen said:
Ah, I think I understand. So now I should flash the stock image again and redo the things (but with rebooting between the steps) - is that correct?
In that case I just need a flashable image. As I wrote in the PS of the first post I tried to flash the original stock rom but I didn't work.
And I can't find an image for (the PHP script complaints about wrong parameters):
• Model: XT1650
• Software-Version: Blur_Version.25.221.12.griffin.re
• Carrier: reteu
Click to expand...
Click to collapse
You didn't account for the line break... It should read something like "Blur_Version.25.221.12.griffin.retail.en.US". However, you have to submit the version that currently runs on your phone - and the server will give you the next update! For the version you provided, there is no update.
You may want to try this:
backup everything you can via TWRP...
boot into bootloader (fastboot)
restore 6.0.1 image [a] via fastboot, see batch file below (the nougat bootloader doesn't let you boot it, but fastboot hopefully doesn't prevent flashing it..)
The nougat bootloader prevents downgrading itself and will cause that fastboot line to fail. Leave it in anyway. If the script breaks or anything, remove the line from the script and retry.
Code:
echo off
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 bluetooth BTFM.bin
fastboot flash dsp adspso.bin
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot flash system system.img_sparsechunk.8
fastboot flash system system.img_sparsechunk.9
fastboot flash 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 oem oem.img
REM fastboot erase carrier
fastboot oem fb_mode_clear
directly boot into (stock) recovery, do not try to boot the system
press and hold down power, then press volume-up, release volume-up, then power.
select 'Apply update from ADB'
sideload nougat update from PC console: "fastboot sideload Blur_Version.25.11.14.griffin.retail.en.US.zip"
[*] Wipe data/factory reset, Wipe cache partition, Power off
[*] reboot
Please report back how it all worked out for you...
[a] XT1650-03_GRIFFIN_RETEU-EMEA_6.0.1_MPL24.246-17_cid50_subsidy-DEFAULT_regulatory-03_CFC_EMEA.xml.zip
OTA: Blur_Version.(24.21.46 --> 25.11.14).griffin.retail.en.US
Okay guys, do the following:
1) Download the Stock Image here and extract the archive to a folder of your choice: https://mirrors.lolinet.com/firmwar...ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
2) Download the Fastboot and Batch-File archive from here and extract it into the Stock Image folder: https://www.sendspace.com/file/1rm4cj
3) Shutdown your phone and then push the VOL- and Power-Button at the same time. You should now enter the Bootloader.
4) Connect your phone to the computer (USB)
5) Open up the command prompt and go the folder where you extracted the Stock Image and Fastboot files to
6) Type _FLASH.bat and ignore all error messages you will possibly see
7) Wait till the phone boots up with the Motorola Splashscreen
That's how I revived my device.
doree said:
2) Download the Fastboot and Batch-File archive from here and extract it into the Stock Image folder: https://mega.nz/fm/hqplTQJS
Click to expand...
Click to collapse
It says "No Data". Do I do something wrong? Just created an account.
I have created this batch from your previous post on the other thread:
Code:
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 bluetooth BTFM.bin
fastboot flash dsp adspso.bin
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot flash system system.img_sparsechunk.8
fastboot flash system system.img_sparsechunk.9
fastboot flash 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 oem oem.img
fastboot erase cache
fastboot erase userdata
fastboot erase customize
fastboot erase clogo
fastboot erase ddr
fastboot reboot
Is this correct? Or the one @benzinerwin just posted?
Code:
echo off
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 bluetooth BTFM.bin
fastboot flash dsp adspso.bin
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot flash system system.img_sparsechunk.8
fastboot flash system system.img_sparsechunk.9
fastboot flash 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 oem oem.img
REM fastboot erase carrier
fastboot oem fb_mode_clear
nighteeeeeY said:
It says "No Data". Do I do something wrong? Just created an account.
I have created this batch from your previous post on the other thread:
Code:
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 bluetooth BTFM.bin
fastboot flash dsp adspso.bin
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot flash system system.img_sparsechunk.8
fastboot flash system system.img_sparsechunk.9
fastboot flash 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 oem oem.img
fastboot erase cache
fastboot erase userdata
fastboot erase customize
fastboot erase clogo
fastboot erase ddr
fastboot reboot
Is this correct? Or the one @benzinerwin just posted?
Code:
echo off
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 bluetooth BTFM.bin
fastboot flash dsp adspso.bin
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot flash system system.img_sparsechunk.8
fastboot flash system system.img_sparsechunk.9
fastboot flash 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 oem oem.img
REM fastboot erase carrier
fastboot oem fb_mode_clear
Click to expand...
Click to collapse
Use this link instead: https://www.sendspace.com/file/1rm4cj
My method is a different approach than benzinerwin's. Use the method you feel comfortable with.
Phew! Thanks. Worked out perfectly.
benzinerwin said:
You didn't account for the line break... It should read something like "Blur_Version.25.221.12.griffin.retail.en.US".
Click to expand...
Click to collapse
I really didn't see that
benzinerwin said:
You may want to try this:
backup everything you can via TWRP...
boot into bootloader (fastboot)
restore 6.0.1 image [a] via fastboot, see batch file below (the nougat bootloader doesn't let you boot it, but fastboot hopefully doesn't prevent flashing it..)
Click to expand...
Click to collapse
I'm getting errors with it (@benzinerwin method)
Code:
(bootloader) Validating 'gpt.default.xml'
(bootloader) Security version downgrade
(bootloader) Image primary_gpt failed validation
(bootloader) Preflash validation failed
(bootloader) Security version downgrade
(bootloader) Image primary_gpt failed validation
(bootloader) Preflash validation failed
(bootloader) Security version downgrade
(bootloader) Image primary_gpt failed validation
(bootloader) Preflash validation failed
(bootloader) Security version downgrade
(bootloader) Image primary_gpt failed validation
(bootloader) Preflash validation failed
(bootloader) Cancelling 'gpt.default.xml'
FAILED (remote failure)
finished. total time: 0.142s
target reported max download size of 536870912 bytes
sending 'bootloader' (7076 KB)...
OKAY [ 0.030s]
writing 'bootloader'...
(bootloader) Validating 'bootloader.default.xml'
(bootloader) Security version downgrade
(bootloader) Image hyp failed validation
(bootloader) Preflash validation failed
(bootloader) Image tz failed validation
(bootloader) Preflash validation failed
(bootloader) Image devcfg failed validation
(bootloader) Preflash validation failed
(bootloader) Cancelling 'bootloader.default.xml'
FAILED (remote failure)
finished. total time: 0.202s
doree said:
Okay guys, do the following:
3) Shutdown your phone and then push the VOL+ and Power-Button at the same time. You should now enter the Bootloader.
Click to expand...
Click to collapse
VOL+ or VOL-? Somehow I entered a boot loop with VOL+…
hackepeterbroetchen said:
I really didn't see that
I'm getting errors with it (@benzinerwin method)
Click to expand...
Click to collapse
When rolling back the bootloader is not allowed, then also writing an older GPT will be prevented. Sorry, I missed that.
However, writing a retail image for a different country seems to work - the phone keepts its 'reteu' setting (I just tried it for a different reason).
That makes things a lot easier: just flash the RETxx nougat image as @doree discribed and you should be fine!
VOL+ or VOL-? Somehow I entered a boot loop with VOL+…
Click to expand...
Click to collapse
Maybe that worked in the old days With current bootloader versions only VOL- & power works. But that only gets you into the fastboot mode, from which you can launch recovery...
hackepeterbroetchen said:
I really didn't see that
I'm getting errors with it (@benzinerwin method)
Code:
(bootloader) Validating 'gpt.default.xml'
(bootloader) Security version downgrade
(bootloader) Image primary_gpt failed validation
(bootloader) Preflash validation failed
(bootloader) Security version downgrade
(bootloader) Image primary_gpt failed validation
(bootloader) Preflash validation failed
(bootloader) Security version downgrade
(bootloader) Image primary_gpt failed validation
(bootloader) Preflash validation failed
(bootloader) Security version downgrade
(bootloader) Image primary_gpt failed validation
(bootloader) Preflash validation failed
(bootloader) Cancelling 'gpt.default.xml'
FAILED (remote failure)
finished. total time: 0.142s
target reported max download size of 536870912 bytes
sending 'bootloader' (7076 KB)...
OKAY [ 0.030s]
writing 'bootloader'...
(bootloader) Validating 'bootloader.default.xml'
(bootloader) Security version downgrade
(bootloader) Image hyp failed validation
(bootloader) Preflash validation failed
(bootloader) Image tz failed validation
(bootloader) Preflash validation failed
(bootloader) Image devcfg failed validation
(bootloader) Preflash validation failed
(bootloader) Cancelling 'bootloader.default.xml'
FAILED (remote failure)
finished. total time: 0.202s
VOL+ or VOL-? Somehow I entered a boot loop with VOL+…
Click to expand...
Click to collapse
Sorry, I meant VOL-. Typed it in a hurry!
So I tried XT1635-02_ADDISON_RETBR_MPNS24.104-44-10_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC now and it fails on different files:
Code:
target reported max download size of 536870912 bytes
sending 'partition' (45 KB)...
OKAY [ 0.035s]
writing 'partition'...
(bootloader) no suitable package!
FAILED (remote failure)
finished. total time: 0.052s
target reported max download size of 536870912 bytes
sending 'bootloader' (5115 KB)...
OKAY [ 0.048s]
writing 'bootloader'...
(bootloader) no suitable package!
FAILED (remote failure)
finished. total time: 0.061s
target reported max download size of 536870912 bytes
sending 'modem' (73570 KB)...
OKAY [ 0.269s]
writing 'modem'...
OKAY [ 1.035s]
finished. total time: 1.304s
target reported max download size of 536870912 bytes
sending 'fsg' (1976 KB)...
OKAY [ 0.051s]
writing 'fsg'...
OKAY [ 0.369s]
finished. total time: 0.420s
erasing 'modemst1'...
OKAY [ 0.193s]
finished. total time: 0.193s
erasing 'modemst2'...
OKAY [ 0.188s]
finished. total time: 0.188s
error: cannot load 'BTFM.bin'
target reported max download size of 536870912 bytes
sending 'dsp' (16384 KB)...
OKAY [ 0.075s]
writing 'dsp'...
OKAY [ 0.467s]
finished. total time: 0.542s
target reported max download size of 536870912 bytes
sending 'logo' (2533 KB)...
OKAY [ 0.054s]
writing 'logo'...
OKAY [ 0.377s]
finished. total time: 0.432s
target reported max download size of 536870912 bytes
sending 'boot' (16384 KB)...
OKAY [ 0.094s]
writing 'boot'...
(bootloader) Image not signed or corrupt
OKAY [ 0.467s]
finished. total time: 0.561s
target reported max download size of 536870912 bytes
sending 'recovery' (16484 KB)...
OKAY [ 0.083s]
writing 'recovery'...
(bootloader) Image not signed or corrupt
OKAY [ 0.468s]
finished. total time: 0.552s
target reported max download size of 536870912 bytes
sending 'system' (257311 KB)...
OKAY [ 0.966s]
writing 'system'...
OKAY [ 2.764s]
finished. total time: 3.730s
target reported max download size of 536870912 bytes
sending 'system' (261378 KB)...
OKAY [ 1.035s]
writing 'system'...
OKAY [ 1.873s]
finished. total time: 2.908s
target reported max download size of 536870912 bytes
sending 'system' (251415 KB)...
OKAY [ 0.986s]
writing 'system'...
OKAY [ 1.867s]
finished. total time: 2.853s
target reported max download size of 536870912 bytes
sending 'system' (255815 KB)...
OKAY [ 0.959s]
writing 'system'...
OKAY [ 1.936s]
finished. total time: 2.895s
target reported max download size of 536870912 bytes
sending 'system' (255582 KB)...
OKAY [ 0.935s]
writing 'system'...
OKAY [ 1.938s]
finished. total time: 2.873s
target reported max download size of 536870912 bytes
sending 'system' (257857 KB)...
OKAY [ 0.966s]
writing 'system'...
OKAY [ 1.775s]
finished. total time: 2.741s
target reported max download size of 536870912 bytes
sending 'system' (260164 KB)...
OKAY [ 1.016s]
writing 'system'...
OKAY [ 1.750s]
finished. total time: 2.766s
target reported max download size of 536870912 bytes
sending 'system' (253309 KB)...
OKAY [ 0.992s]
writing 'system'...
OKAY [ 1.919s]
finished. total time: 2.911s
target reported max download size of 536870912 bytes
sending 'system' (256398 KB)...
OKAY [ 1.061s]
writing 'system'...
OKAY [ 1.805s]
finished. total time: 2.866s
target reported max download size of 536870912 bytes
sending 'system' (262140 KB)...
OKAY [ 1.066s]
writing 'system'...
OKAY [ 1.779s]
finished. total time: 2.845s
target reported max download size of 536870912 bytes
sending 'system' (147418 KB)...
OKAY [ 0.628s]
writing 'system'...
OKAY [ 1.079s]
finished. total time: 1.706s
error: cannot load 'system.img_sparsechunk.11'
error: cannot load 'system.img_sparsechunk.12'
error: cannot load 'system.img_sparsechunk.13'
target reported max download size of 536870912 bytes
sending 'oem' (105020 KB)...
OKAY [ 0.454s]
writing 'oem'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.477s
erasing 'cache'...
OKAY [ 0.379s]
finished. total time: 0.379s
erasing 'userdata'...
OKAY [ 1.957s]
finished. total time: 1.957s
erasing 'customize'...
OKAY [ 0.365s]
finished. total time: 0.365s
erasing 'clogo'...
(bootloader) Permission denied
FAILED (remote failure)
finished. total time: 0.029s
erasing 'ddr'...
OKAY [ 0.312s]
finished. total time: 0.312s
rebooting...
finished. total time: 0.903s
These were the commands I ran (these are the ones @doree linked)
Code:
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 bluetooth BTFM.bin
fastboot flash dsp adspso.bin
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot flash system system.img_sparsechunk.8
fastboot flash system system.img_sparsechunk.9
fastboot flash 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 oem oem.img
fastboot erase cache
fastboot erase userdata
fastboot erase customize
fastboot erase clogo
fastboot erase ddr
fastboot reboot
Is it because the image is XT1635-02 instead XT1650-03?
EDIT:
I did flash it this way now anyway (I probably shouldn't have done this, sorry) but reboot failed now and moves directly to fastboot with the following error message:
Code:
Start Up Failed:
Your device didn't start up successfully.
Use the Software Repair Assistant on computer to repair your device.
Connect your device to your computer to get the Software Repair Assistant.
EDIT 2:
I tried ADDISON_NPNS25.137-24-1-4_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC with Android 7 now with the same effect. I guess I am missing something here?
PS: I absolutely appreciate your help and it's impressive how fast you answer. Thank you very much for this.
hackepeterbroetchen said:
So I tried XT1635-02_ADDISON_RETBR_MPNS24.104-44-10_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC now and it fails on different files:
Code:
target reported max download size of 536870912 bytes
sending 'partition' (45 KB)...
OKAY [ 0.035s]
writing 'partition'...
(bootloader) no suitable package!
FAILED (remote failure)
finished. total time: 0.052s
target reported max download size of 536870912 bytes
sending 'bootloader' (5115 KB)...
OKAY [ 0.048s]
writing 'bootloader'...
(bootloader) no suitable package!
FAILED (remote failure)
finished. total time: 0.061s
target reported max download size of 536870912 bytes
sending 'modem' (73570 KB)...
OKAY [ 0.269s]
writing 'modem'...
OKAY [ 1.035s]
finished. total time: 1.304s
target reported max download size of 536870912 bytes
sending 'fsg' (1976 KB)...
OKAY [ 0.051s]
writing 'fsg'...
OKAY [ 0.369s]
finished. total time: 0.420s
erasing 'modemst1'...
OKAY [ 0.193s]
finished. total time: 0.193s
erasing 'modemst2'...
OKAY [ 0.188s]
finished. total time: 0.188s
error: cannot load 'BTFM.bin'
target reported max download size of 536870912 bytes
sending 'dsp' (16384 KB)...
OKAY [ 0.075s]
writing 'dsp'...
OKAY [ 0.467s]
finished. total time: 0.542s
target reported max download size of 536870912 bytes
sending 'logo' (2533 KB)...
OKAY [ 0.054s]
writing 'logo'...
OKAY [ 0.377s]
finished. total time: 0.432s
target reported max download size of 536870912 bytes
sending 'boot' (16384 KB)...
OKAY [ 0.094s]
writing 'boot'...
(bootloader) Image not signed or corrupt
OKAY [ 0.467s]
finished. total time: 0.561s
target reported max download size of 536870912 bytes
sending 'recovery' (16484 KB)...
OKAY [ 0.083s]
writing 'recovery'...
(bootloader) Image not signed or corrupt
OKAY [ 0.468s]
finished. total time: 0.552s
target reported max download size of 536870912 bytes
sending 'system' (257311 KB)...
OKAY [ 0.966s]
writing 'system'...
OKAY [ 2.764s]
finished. total time: 3.730s
target reported max download size of 536870912 bytes
sending 'system' (261378 KB)...
OKAY [ 1.035s]
writing 'system'...
OKAY [ 1.873s]
finished. total time: 2.908s
target reported max download size of 536870912 bytes
sending 'system' (251415 KB)...
OKAY [ 0.986s]
writing 'system'...
OKAY [ 1.867s]
finished. total time: 2.853s
target reported max download size of 536870912 bytes
sending 'system' (255815 KB)...
OKAY [ 0.959s]
writing 'system'...
OKAY [ 1.936s]
finished. total time: 2.895s
target reported max download size of 536870912 bytes
sending 'system' (255582 KB)...
OKAY [ 0.935s]
writing 'system'...
OKAY [ 1.938s]
finished. total time: 2.873s
target reported max download size of 536870912 bytes
sending 'system' (257857 KB)...
OKAY [ 0.966s]
writing 'system'...
OKAY [ 1.775s]
finished. total time: 2.741s
target reported max download size of 536870912 bytes
sending 'system' (260164 KB)...
OKAY [ 1.016s]
writing 'system'...
OKAY [ 1.750s]
finished. total time: 2.766s
target reported max download size of 536870912 bytes
sending 'system' (253309 KB)...
OKAY [ 0.992s]
writing 'system'...
OKAY [ 1.919s]
finished. total time: 2.911s
target reported max download size of 536870912 bytes
sending 'system' (256398 KB)...
OKAY [ 1.061s]
writing 'system'...
OKAY [ 1.805s]
finished. total time: 2.866s
target reported max download size of 536870912 bytes
sending 'system' (262140 KB)...
OKAY [ 1.066s]
writing 'system'...
OKAY [ 1.779s]
finished. total time: 2.845s
target reported max download size of 536870912 bytes
sending 'system' (147418 KB)...
OKAY [ 0.628s]
writing 'system'...
OKAY [ 1.079s]
finished. total time: 1.706s
error: cannot load 'system.img_sparsechunk.11'
error: cannot load 'system.img_sparsechunk.12'
error: cannot load 'system.img_sparsechunk.13'
target reported max download size of 536870912 bytes
sending 'oem' (105020 KB)...
OKAY [ 0.454s]
writing 'oem'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.477s
erasing 'cache'...
OKAY [ 0.379s]
finished. total time: 0.379s
erasing 'userdata'...
OKAY [ 1.957s]
finished. total time: 1.957s
erasing 'customize'...
OKAY [ 0.365s]
finished. total time: 0.365s
erasing 'clogo'...
(bootloader) Permission denied
FAILED (remote failure)
finished. total time: 0.029s
erasing 'ddr'...
OKAY [ 0.312s]
finished. total time: 0.312s
rebooting...
finished. total time: 0.903s
These were the commands I ran (these are the ones @doree linked)
Code:
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 bluetooth BTFM.bin
fastboot flash dsp adspso.bin
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot flash system system.img_sparsechunk.8
fastboot flash system system.img_sparsechunk.9
fastboot flash 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 oem oem.img
fastboot erase cache
fastboot erase userdata
fastboot erase customize
fastboot erase clogo
fastboot erase ddr
fastboot reboot
Is it because the image is XT1635-02 instead XT1650-03?
EDIT:
I did flash it this way now anyway (I probably shouldn't have done this, sorry) but reboot failed now and moves directly to fastboot with the following error message:
Code:
Start Up Failed:
Your device didn't start up successfully.
Use the Software Repair Assistant on computer to repair your device.
Connect your device to your computer to get the Software Repair Assistant.
EDIT 2:
I tried ADDISON_NPNS25.137-24-1-4_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC with Android 7 now with the same effect. I guess I am missing something here?
PS: I absolutely appreciate your help and it's impressive how fast you answer. Thank you very much for this.
Click to expand...
Click to collapse
Where are you getting this links from? My post cleary leads to:
https://mirrors.lolinet.com/firmwar...ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
You are trying to flash an Image for a whole different Device (Moto Z Play).
Moto Z Play = XT-1635 Addison
Moto Z = XT-1650 Griffin
doree said:
Where are you getting this links from? My post cleary leads to:
https://mirrors.lolinet.com/firmwar...ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
You are trying to flash an Image for a whole different Device (Moto Z Play).
Moto Z Play = XT-1635 Addison
Moto Z = XT-1650 Griffin
Click to expand...
Click to collapse
Oh boy! I guess this happened because I skipped coffee today
@doree the mobile is booting again. I guess I owe you a beer. Thank you so much!
I guess it isn't possible to go back to the EU rom again for now?
However, now TWRP and root!
Can you recommend any root system for using it with the stock rom?
hackepeterbroetchen said:
Oh boy! I guess this happened because I skipped coffee today
@doree the mobile is booting again. I guess owe you a beer. Thank you so much!
Click to expand...
Click to collapse
Glad I could help
I guess it isn't possible to go back to the EU rom again for now?
Click to expand...
Click to collapse
RETBR is pretty much the same as the "regular" RETEU Rom, since it uses the same Softwarechannel (Settings/About/Softwarechannel). You'll get the same Updates as everyone else in Germany/Europe.
However, now TWRP and root!
Can you recommend any root system for using it with the stock rom?
Click to expand...
Click to collapse
What do you exactly mean with "root system"?
My model is XT1710-09 of Tim Italia with single sim, but it has also been tested in a dual sim model.
This tutorial explains how to get back from LineageOS to stock firmware without losing the IMEI. You should always make a copy of the IMEI in TWPR.
How does it work:
You have to be in a modified rom.
1- You have to download this firmware with the February 2018 patch: https://androidfilehost.com/?fid=962187416754466195
2- Install adb minimal fastboot: https://forum.xda-developers.com/sho....php?t=2317790
3- After installing adb minimal fastboot, go to the location of the ADB installation and paste all the files extracted from the downloaded firmware there.
4- Copy all the commands of this thread in the cmd window, press enter and wait.
Commands:
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 flash dsp adspso.bin
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 oem oem.img
fastboot erase carrier
fastboot erase cache
fastboot erase userdata
fastboot erase DDR
fastboot oem fb_mode_clear
fastboot oem lock
fastboot oem lock
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 boot boot.img
fastboot oem lock
These are the results that I have obtained
For US variant XT1710-01 https://forum.xda-developers.com/showpost.php?p=76192627&postcount=18
That way is way i used to return to stockOS on another devices
I just followed the steps above on my XT1710-01 unlocked US Retail and it appears to have worked. I got the normal blue/red splash screen and I have data/IMEI. I booted into bootloader and oem_locked + software status: official is there Thanks brother!
julesism said:
I just followed the steps above on my XT1710-01 unlocked US Retail and it appears to have worked. I got the normal blue/red splash screen and I have data/IMEI. I booted into bootloader and oem_locked + software status: official is there Thanks brother!
Click to expand...
Click to collapse
What I'm anxious to know is if the phone will get the OTA´s
julesism said:
I just followed the steps above on my XT1710-01 unlocked US Retail and it appears to have worked. I got the normal blue/red splash screen and I have data/IMEI. I booted into bootloader and oem_locked + software status: official is there Thanks brother!
Click to expand...
Click to collapse
I was going to try this on my XT1710-01 (Canada retail) on the weekend. Thanks for confirming!
While this get me back to the stock Moto ROM, it did not lock my bootloader.
Got the dreaded "Image signed with key bad key" message during various times during using the fastboot commands and my bootloader remains unlocked.
XT1710-01 (Canada Retail)
I think you should try it again I went thru the process posted in another thread by rajatgupta1998 and ended up exactly where you are now. I manually flashed a modified boot.img via adb to get the blue/red splash screen back although some text was still visible including bad key message.
When this topic was created, I decided to give it one more try. I had so may files unzipped from previous zips/flashes etc., I decided to make a clean adb folder with nothing but this zip/files extracted in it. Low and behold, it worked for me. I believe once, maybe twice the process stopped and I had to manually copy/paste the next command. Maybe something was missed.
Here's hoping this fixes my NFC issue
TravellingGuy said:
While this get me back to the stock Moto ROM, it did not lock my bootloader.
Got the dreaded "Image signed with key bad key" message during various times during using the fastboot commands and my bootloader remains unlocked.
XT1710-01 (Canada Retail)
Click to expand...
Click to collapse
This happened to me because I did not install the latest firmware. It is because the bootloader is more recent than the firmware you are trying to install. When putting the firmware of February 2018 I have been able to close the bootloader three times, after returning several times to lineageOS.
julesism said:
I think you should try it again I went thru the process posted in another thread by rajatgupta1998 and ended up exactly where you are now. I manually flashed a modified boot.img via adb to get the blue/red splash screen back although some text was still visible including bad key message.
When this topic was created, I decided to give it one more try. I had so may files unzipped from previous zips/flashes etc., I decided to make a clean adb folder with nothing but this zip/files extracted in it. Low and behold, it worked for me. I believe once, maybe twice the process stopped and I had to manually copy/paste the next command. Maybe something was missed.
Click to expand...
Click to collapse
I actually did try it twice that evening and the same thing happened both times. That was also from a fresh folder.
Kacike27 said:
This happened to me because I did not install the latest firmware. It is because the bootloader is more recent than the firmware you are trying to install. When putting the firmware of February 2018 I have been able to close the bootloader three times, after returning several times to lineageOS.
Click to expand...
Click to collapse
So, I was on LineageOS when I followed your process. Your process includes steps to flash the bootloader and the firmware, which *should* mean the bootloader is the same version as the corresponding firmware (i.e. I didn't skip in any steps in the process that may have allowed a more recent bootloader to remain on my device).
I see from this post (a different, older device, but could very still be relevant), (s)he says
"Make sure you have a fastboot flashable official stock image signed to work with your carrier and region before re-locking the bootloader. Currently running the official firmware is not enough."
Click to expand...
Click to collapse
I wonder if it's also dependent on carrier and/or region. I'm in Canada, maybe there is a slightly modified bootlader for us Canucks or a different bootloader depending on the carrier or purchase location.
Use mfastboot to flash the files instead of fastboot ...check google for difference
I found many ROM for our Albus here:
https://firmware.center/firmware/Motorola/Moto Z2 Play/Stock/
But can't classify them.
My albus is XT 1710-09 in VietNam, so which file is of mine ?
Can you block the bootloader but it did not get Official in the part software status, was Modified got how to make official again?
HeltonMax said:
Can you block the bootloader but it did not get Official in the part software status, was Modified got how to make official again?
Click to expand...
Click to collapse
In my case, software status shows Official with bootloader unlocked.
method in this thread doesn't help me relock bootloader. I think I flash not correct fw for my local. But I cant find anywhere
Working very well in XT710-06 thanks bro.
Working fine on xt-710-07 also (Brazilian unlocked).
The only bug is the NFC is gone. Anyone has a workaround for this?
ogabriel said:
Working fine on xt-710-07 also (Brazilian unlocked).
The only bug is the NFC is gone. Anyone has a workaround for this?
Click to expand...
Click to collapse
I just experienced this after returning to stock from LineageOS, and there was no way I was going to settle for it.
I followed the instructions only omitting the lock and reboot commands.
Flashed TWRP, (twice to be sure), rebooted into recovery, then restored my EFS, Data, and logo. (I think 'Data' is optional, I just didn't want to start over), NFC now works fine again.
I think you always need to restore your EFS.
However, the first time I tried just restoring EFS, after boot/setup, and that didn't work. so I think you have to do it prior to boot.
i imagine you could follow instructions completely, immediately booting into bootloader then use TWRP "Boot" instead of "flash", if your end game is to relock bootloader.
I successfully locked my US variant using following method
Hello,
I can confirm that using following sequence I was able to successfully lock my US variant without loosing IMEI (EFS Partition)
Here is the Stock file I used:
Retail US Stock (ALBUS_C) (ALBUS_NA_CUST) XT1710-01
https://androidfilehost.com/?fid=890129502657596522
Those on Retail channel can perhaps use following stock file
Retail Stock (ALBUS)
https://androidfilehost.com/?fid=890129502657596046
I used mfastbootv2 for my bootloader locking (Google it, easy to find)
Here is the sequence I followed:
Phase-1 (Factory Flashing)
======
mfastboot flash partition gpt.bin
mfastboot flash bootloader bootloader.img
mfastboot flash modem NON-HLOS.bin
mfastboot flash fsg fsg.mbn
mfastboot flash dsp adspso.bin
mfastboot flash logo logo.bin
mfastboot flash boot boot.img
mfastboot flash recovery recovery.img
mfastboot flash system system.img_sparsechunk.0
mfastboot flash system system.img_sparsechunk.1
mfastboot flash system system.img_sparsechunk.2
mfastboot flash system system.img_sparsechunk.3
mfastboot flash system system.img_sparsechunk.4
mfastboot flash system system.img_sparsechunk.5
mfastboot flash system system.img_sparsechunk.6
mfastboot flash oem oem.img
mfastboot erase cache
mfastboot erase userdata
mfastboot erase carrier
mfastboot erase DDR
mfastboot reboot
<<Please note mfastboot erase modemst1 and mfastboot erase modemst2 commands are not being used in the above sequence>>
After reboot I wanted my phone to fully bootup upto "Welcome" screen to ensure I've LTE connectivity with my cellular provider and my IMEI is intact
Once verified, I rebooted the phone into the bootloader,
-While your phone is completely switched off, Hold <Power + Vol Down> button for few seconds to boot phone into the bootloader
Phase-2 (OEM Bootloader Locking)
======
mfastboot oem lock
mfastboot oem lock
mfastboot flash oem oem.img
mfastboot flash system system.img_sparsechunk.0
mfastboot flash system system.img_sparsechunk.1
mfastboot flash system system.img_sparsechunk.2
mfastboot flash system system.img_sparsechunk.3
mfastboot flash system system.img_sparsechunk.4
mfastboot flash system system.img_sparsechunk.5
mfastboot flash system system.img_sparsechunk.6
mfastboot flash system system.img_sparsechunk.7
mfastboot flash boot boot.img
mfastboot oem lock
Following is the final message I got
mfastboot oem lock
...
(bootloader) Lock complete! Flash signed images after reboot if needed
OKAY [ 0.148s]
finished. total time: 0.152s
My phone automatically rebooted once the above sequence was completed
Give it a try at your risk - Best of Luck!!
sevenstar75 said:
Hello,
I can confirm that using following sequence I was able to successfully lock my US variant without loosing IMEI (EFS Partition)
Here is the Stock file I used:
Retail US Stock (ALBUS_C) (ALBUS_NA_CUST) XT1710-01
https://androidfilehost.com/?fid=890129502657596522
Those on Retail channel can perhaps use following stock file
Retail Stock (ALBUS)
https://androidfilehost.com/?fid=890129502657596046
I used mfastbootv2 for my bootloader locking (Google it, easy to find)
<...snip...>
Following is the final message I got
mfastboot oem lock
...
(bootloader) Lock complete! Flash signed images after reboot if needed
OKAY [ 0.148s]
finished. total time: 0.152s
My phone automatically rebooted once the above sequence was completed
Give it a try at your risk - Best of Luck!!
Click to expand...
Click to collapse
I really do appreciate all you guys out there posting your steps to get back to stock and lock the bootloader.
I've literally tried every possible combination of fastboot, mfastboot, mfastbootv2, and all the different variants of ROMs posted. Haha, but it *always* fails for me.
Two things I notice, and I'm not sure if you guys see these or not.
One is that I always "get the (bootloader) Image signed with key bad key" message when I try to flash the boot.img. I'm not sure if that's something you guys get as well?
The other thing is I always see the "(bootloader) Check 'Allow OEM Unlock' in Android Settings > Developer" message when I run the lock command. @sevenstar75, I notice in your final oem lock command, you don't see this. This makes me think that this is what is different for me. In my developer settings, the OEM Lock toggle is disabled, with a message to the effect of "Bootloader is already unlocked", and I can't change the toggle. This makes sense, as my bootloader IS unlocked, but why don't you see/get that message as well, I wonder?
Here is some sample output of what I'm doing and seeing:
Code:
fastboot oem lock
...
(bootloader) WARNING: This command erases all user data.
(bootloader) Please re-run this command to continue.
OKAY [ 0.002s]
finished. total time: 0.002s
fastboot oem lock
...
(bootloader) Check 'Allow OEM Unlock' in Android Settings > Developer
(bootloader) Options
OKAY [ 0.002s]
finished. total time: 0.002s
fastboot flash oem oem.img
target max-sparse-size: 256MB
sending 'oem' (232923 KB)...
OKAY [ 6.020s]
writing 'oem'...
OKAY [ 3.161s]
finished. total time: 9.181s
fastboot flash system system.img_sparsechunk.0
target max-sparse-size: 256MB
Sparse-Flash is enabled!
sending sparse 'system' (262142 KB)...
OKAY [ 6.856s]
writing 'system'...
OKAY [ 4.225s]
sending sparse 'system' (259055 KB)...
OKAY [ 6.732s]
writing 'system'...
OKAY [ 3.632s]
finished. total time: 21.444s
fastboot flash system system.img_sparsechunk.1
target max-sparse-size: 256MB
Sparse-Flash is enabled!
sending sparse 'system' (245604 KB)...
OKAY [ 6.441s]
writing 'system'...
OKAY [ 3.479s]
sending sparse 'system' (240099 KB)...
OKAY [ 6.273s]
writing 'system'...
OKAY [ 3.105s]
sending sparse 'system' (30320 KB)...
OKAY [ 0.800s]
writing 'system'...
OKAY [ 0.414s]
finished. total time: 20.512s
fastboot flash system system.img_sparsechunk.2
target max-sparse-size: 256MB
Sparse-Flash is enabled!
sending sparse 'system' (255375 KB)...
OKAY [ 6.686s]
writing 'system'...
OKAY [ 3.752s]
sending sparse 'system' (258527 KB)...
OKAY [ 6.836s]
writing 'system'...
OKAY [ 4.416s]
finished. total time: 21.690s
fastboot flash system system.img_sparsechunk.3
target max-sparse-size: 256MB
Sparse-Flash is enabled!
sending sparse 'system' (262140 KB)...
OKAY [ 7.145s]
writing 'system'...
OKAY [ 3.449s]
sending sparse 'system' (258973 KB)...
OKAY [ 6.839s]
writing 'system'...
OKAY [ 3.405s]
finished. total time: 20.838s
fastboot flash system system.img_sparsechunk.4
target max-sparse-size: 256MB
Sparse-Flash is enabled!
sending sparse 'system' (261624 KB)...
OKAY [ 6.844s]
writing 'system'...
OKAY [ 3.589s]
sending sparse 'system' (258473 KB)...
OKAY [ 7.094s]
writing 'system'...
OKAY [ 3.587s]
finished. total time: 21.113s
fastboot flash system system.img_sparsechunk.5
target max-sparse-size: 256MB
Sparse-Flash is enabled!
sending sparse 'system' (253898 KB)...
OKAY [ 6.661s]
writing 'system'...
OKAY [ 3.451s]
sending sparse 'system' (262134 KB)...
OKAY [ 6.944s]
writing 'system'...
OKAY [ 4.081s]
sending sparse 'system' (8244 KB)...
OKAY [ 0.231s]
writing 'system'...
OKAY [ 0.160s]
finished. total time: 21.527s
fastboot flash system system.img_sparsechunk.6
target max-sparse-size: 256MB
sending 'system' (252681 KB)...
OKAY [ 6.432s]
writing 'system'...
OKAY [ 3.292s]
finished. total time: 9.725s
fastboot flash boot boot.img
target max-sparse-size: 256MB
sending 'boot' (16384 KB)...
OKAY [ 0.448s]
writing 'boot'...
(bootloader) Image signed with key bad key
OKAY [ 0.458s]
finished. total time: 0.906s
fastboot oem lock
...
(bootloader) Check 'Allow OEM Unlock' in Android Settings > Developer
(bootloader) Options
OKAY [ 0.002s]
finished. total time: 0.002s
Hi,
1) What is your variant? I mean XT1710-?? Is that RetUS software channel?
2) Did you toggle Allow OEM Unlocking to "ON" before unlocking your phone?
3) While that toggle currently grayed out, is the toggle - ON or OFF?
Hi there, so I've just bricked my RNE_L21 when trying to flash system image from Pixel Experience.
I wan't to flash stock recovery images to make it work again but it stops me at all of the recovery images (ramdisk, vendor, etc.):
target reported max download size of 471859200 bytes
sending 'ERECOVERY_KERNEL' (24576 KB)...
OKAY [ 0.725s]
writing 'ERECOVERY_KERNEL'...
FAILED (remote: Command not allowed)
finished. total time: 0.745s
Bootloader is fully unlocked and i have all fastboot and ADB drivers updated, TWRP installed
Please help, thanks
Phone: Oneplus 3T
Recovery: TWRP 3.3.0-1
OS: LOS 16.0
Flashed a bad emmc_appsboot.mbn and now my phone loops as soon as it gets to the 1+ logo.
Cannot get into recovery.
Can get into fastboot.
Bootloader has been unlocked for years. After getting the "not allowed" error, I did a "fastboot oem unlock" again, successfully.
Code:
$ fastboot flashing get_unlock_ability
(bootloader) get_unlock_ability: 1
$ fastboot flashing unlock
(bootloader) Device already : unlocked!
$ fastboot flashing unlock_critical
(bootloader) Device already : unlocked!
$ fastboot flash recovery twrp-3.3.0-1-oneplus3.img
target reported max download size of 440401920 bytes
erasing 'recovery'...
OKAY [ 0.010s]
sending 'recovery' (27405 KB)...
OKAY [ 0.721s]
writing 'recovery'...
OKAY [ 0.199s]
finished. total time: 0.930s
$ fastboot flash aboot firmware-update/emmc_appsboot.mbn
target reported max download size of 440401920 bytes
sending 'aboot' (1584 KB)...
OKAY [ 0.062s]
writing 'aboot'...
FAILED (remote: Partition flashing is not allowed)
finished. total time: 0.082s
$ fastboot flash devcfg firmware-update/devcfg.mbn
target reported max download size of 440401920 bytes
sending 'devcfg' (50 KB)...
OKAY [ 0.038s]
writing 'devcfg'...
FAILED (remote: Partition flashing is not allowed)
Every partition other than recovery gives the "not allowed" error. And flashing the recovery doesn't help.
I'm stumped. I haven't been able to find any other reports online of the same problem, only people with locked bootloaders getting that error.
I know about EDL and I've been working on that angle, but getting fastboot flashing working would be easier.
Ideas? Suggestions?
Hi,
Can someone please help me with fix of my P20 lite dual?
I try to fix it for 50 hours in total, I downloaded about 150Gb of files ☹
The begining of my problem started from full working state one day, next morning I got error "your device has failed verification and may not work properly"
Phone was running stock ANE-LX1 9.1.0 C432 E6R1P7
Factory reset and cache wipe did not help.
Any attempt to SD or USB update via recovery failed, always got "Install failed"
So I tried flashing file update.app using MRT from some higher version of stock sw in fastboot, then in stock recovery, later in TWRP.
No luck, phone was in fastboot mode only or bootloops.
Then I found huawei flash tool IDT 2.0.0.9 and factory board sw 1.0.0.40 using test point (HUAWEI COM 1.0)
With this one the phone fully boots in factory firmware, but phone info says model HAT, has bootlogo ASCEND and android logo , IMEIs in menu are OK.
So how the hell can I get it back to official stock state with ANE-LX1 in "About phone"?
Any attempt of flashing ANE-LX1 sw from menu or stock recovery gives me Flash failed message.
From what I found, I probably need 3 file firmware FullOtaMF for HwOta tool, but nowhere can be found.
Or is there some easy way to flash to official ?
Or did I messed up some system files that need to be fixed?
PS: while flashing hundred of files I found one TWRP version, that can change BL lock code, so I changed it to 111111111111111 for easier unlock in future attempts.
Can be this a problem? (I hope not)
Thank you for any ideas !
hdano said:
From what I found, I probably need 3 file firmware FullOtaMF for HwOta tool, but nowhere can be found.
Click to expand...
Click to collapse
HwOTA will won't help you - it cannot identify the device in this state...
(model HAT, EMUI 4.1, Marshmallow, RAM 2.1GB )
In fastboot mode run commands:
fastboot oem get-build-number
fastboot oem get-product-model
fastboot getvar vendorcountry
fastboot oem oeminforead-CUSTOM_VERSION
fastboot oem oeminforead-SYSTEM_VERSION
and post the results.
-Alf- said:
HwOTA will won't help you - it cannot identify the device in this state...
(model HAT, EMUI 4.1, Marshmallow, RAM 2.1GB )
In fastboot mode run commands:
fastboot oem get-build-number
fastboot oem get-product-model
fastboot getvar vendorcountry
fastboot oem oeminforead-CUSTOM_VERSION
fastboot oem oeminforead-SYSTEM_VERSION
and post the results.
Click to expand...
Click to collapse
C:\adb>fastboot oem get-build-number
...
(bootloader) :ANE-BD 1.0.0.40(log)
OKAY [ 0.011s]
finished. total time: 0.013s
C:\adb>
C:\adb>fastboot oem get-product-model
...
(bootloader) ANE
OKAY [ 0.011s]
finished. total time: 0.013s
C:\adb>
C:\adb>fastboot getvar vendorcountry
getvar:vendorcountry FAILED (remote: cannot get vendorcountry in oeminfo)
finished. total time: 0.022s
C:\adb>
C:\adb>fastboot oem oeminforead-CUSTOM_VERSION
...
FAILED (remote: The reason of failed input oem_nv_item error!)
finished. total time: 0.018s
C:\adb>
C:\adb>fastboot oem oeminforead-SYSTEM_VERSION
...
FAILED (remote: Read oeminfo failed!)
finished. total time: 0.021s
hdano said:
any ideas
Click to expand...
Click to collapse
maybe the following will help you:
- Download TWRP Service ROM oeminfo and
Recovery_ramdisk for Oreo
- Unpack Service ROM package, find dload folder and transfer it to the SD card WITHOUT UNPACKING IT.
- Also copy to the SD card downloaded recovery_ramdisk oeminfo file and TWRP
- Install TWRP over eRecovery (only read the principle, not download links)
- boot into TWRP , select Install image , find oeminfo file, mark 'oeminfo' and flash it.
- Go back to the main TWRP's menu, select Reboot and Turn off.
- Use three button combo and try to install Service ROM .
Note: you do everything at your own risk, I hope that's clear
Hi Alf,
thanks for reply,
worked like a charm !
Phone booted in official rom, was working well.
But..
If I try to download OTA update from menu, it shows me update to ANE-LX1 8.0.0.174(C432)-FULL size 2.92GB ,
but after downloading phone shows install error.
I did factory reset and cache clear, same result, can not install.
So I downloaded to SD card latest sw Huawei P20 Lite ( Nova 3e ) ANE-L21 ANE-L01 hw eu Anne-L01 9.1.0.370(C432E7R1P7T8) Firmware EMUI9.1.0 05014YXU [androidhost.ru].zip
but verify goes 5% then 6% then back to 5%, then 6% then shows "install failed"
After attempt to update by *#*#2846579#*#* from menu, phone did the same, 5% 6% 5% 6% "install failed", but after reboot I have attached photo error :-(
Now not booting again, stuck in this error.
So how can I update to some new sw ?
Do I have to use some special version to go higher?
Or is it some other problem?
BTW, fastboot shows now Phone Locked and FRP locked, but I did not add any google account yet :-O
hdano said:
BTW, fastboot shows now Phone Locked and FRP locked, but I did not add any google account yet
Click to expand...
Click to collapse
Yes, service ROM lock the bootloader , it's normal.
hdano said:
FRP locked,
Click to expand...
Click to collapse
You can unlock FRP manually in Developer options - "Enable OEM unlock".
Run again fastboot commands and post results.
C:\adb>fastboot oem get-build-number
...
(bootloader) :ANE-LX1 8.0.0.126(C432)
OKAY [ 0.011s]
finished. total time: 0.012s
C:\adb>fastboot oem get-product-model
...
(bootloader) ANE-LX1
OKAY [ 0.009s]
finished. total time: 0.010s
C:\adb>fastboot getvar vendorcountry
vendorcountry: hw/eu
finished. total time: 0.010s
C:\adb>fastboot oem oeminforead-CUSTOM_VERSION
...
FAILED (remote: Read oeminfo failed!)
finished. total time: 0.020s
C:\adb>fastboot oem oeminforead-SYSTEM_VERSION
...
(bootloader) :ANE-LX1 8.0.0.126(C432)
OKAY [ 0.012s]
finished. total time: 0.013s
hdano said:
C:\adb>fastboot oem get-build-number
...
(bootloader) :ANE-LX1 8.0.0.126(C432)
OKAY [ 0.011s]
finished. total time: 0.012s
C:\adb>fastboot oem get-product-model
...
(bootloader) ANE-LX1
OKAY [ 0.009s]
finished. total time: 0.010s
C:\adb>fastboot getvar vendorcountry
vendorcountry: hw/eu
finished. total time: 0.010s
C:\adb>fastboot oem oeminforead-CUSTOM_VERSION
...
FAILED (remote: Read oeminfo failed!)
finished. total time: 0.020s
C:\adb>fastboot oem oeminforead-SYSTEM_VERSION
...
(bootloader) :ANE-LX1 8.0.0.126(C432)
OKAY [ 0.012s]
finished. total time: 0.013s
Click to expand...
Click to collapse
Okay, now boot into eRecovery (not Recovery) and select option Download latest version and recovery.
This ***** sucks :-(
hdano said:
This ***** sucks
Click to expand...
Click to collapse
Try to install .174 Service ROM via dload method.
If you get Install failed error again, then you need unlock bootloader (if it's possible) and flash some partitions in fastboot.
You can use this tutorial . Use downloaded .174 ROM. Extract and flash
- kernel
-ramdisk
- recovery_ramdisk
- system
- cust
Note: cust.img can be found in update_ane-L21_hw_eu
Reboot and turn off the phone, then flash .174 Service ROM or try update via eRecovery.
C:\adb>fastboot flash kernel KERNEL.IMG
target reported max download size of 471859200 bytes
sending 'kernel' (24576 KB)...
OKAY [ 0.893s]
writing 'kernel'...
OKAY [ 0.388s]
finished. total time: 1.286s
C:\adb>fastboot flash ramdisk RAMDISK.IMG
target reported max download size of 471859200 bytes
sending 'ramdisk' (16384 KB)...
OKAY [ 0.602s]
writing 'ramdisk'...
OKAY [ 0.075s]
finished. total time: 0.681s
C:\adb>fastboot flash recovery_ramdisk RECOVERY_RAMDIS.IMG
target reported max download size of 471859200 bytes
sending 'recovery_ramdisk' (32768 KB)...
OKAY [ 1.208s]
writing 'recovery_ramdisk'...
OKAY [ 0.169s]
finished. total time: 1.381s
C:\adb>fastboot flash system SYSTEM.IMG
target reported max download size of 471859200 bytes
sending sparse 'system' 1/8 (460799 KB)...
OKAY [ 19.946s]
writing 'system' 1/8...
OKAY [ 3.866s]
sending sparse 'system' 2/8 (424020 KB)...
OKAY [ 17.042s]
writing 'system' 2/8...
OKAY [ 2.164s]
sending sparse 'system' 3/8 (458375 KB)...
OKAY [ 18.384s]
writing 'system' 3/8...
OKAY [ 2.219s]
sending sparse 'system' 4/8 (460418 KB)...
OKAY [ 18.557s]
writing 'system' 4/8...
OKAY [ 2.213s]
sending sparse 'system' 5/8 (425536 KB)...
OKAY [ 17.164s]
writing 'system' 5/8...
OKAY [ 2.157s]
sending sparse 'system' 6/8 (457971 KB)...
OKAY [ 19.231s]
writing 'system' 6/8...
OKAY [ 2.855s]
sending sparse 'system' 7/8 (460016 KB)...
OKAY [ 19.003s]
writing 'system' 7/8...
OKAY [ 3.147s]
sending sparse 'system' 8/8 (192362 KB)...
OKAY [ 7.791s]
writing 'system' 8/8...
OKAY [ 1.015s]
finished. total time: 156.792s
C:\adb>fastboot flash cust CUST.IMG
target reported max download size of 471859200 bytes
sending 'cust' (139283 KB)...
OKAY [ 5.096s]
writing 'cust'...
OKAY [ 0.794s]
finished. total time: 5.894s
C:\adb>fastboot reboot
rebooting...
Now the only I can get is this, no way to get in eRecovery
hdano said:
Now the only I can get is this, no way to get in eRecovery
Click to expand...
Click to collapse
Chinese??? Wow...
As I said before,
-Alf- said:
turn off the phone, then flash .174 Service ROM
Click to expand...
Click to collapse
Have you tried bro?
-Alf- said:
Chinese??? Wow...
As I said before,
Have you tried bro?
Click to expand...
Click to collapse
how? I can not get in eRecovery, only that chinese recovery or what it is....
hdano said:
how? I can not get in eRecovery, only that chinese recovery or what it is....
Click to expand...
Click to collapse
Service ROM has nothing to do with eRecovery.
As the bootloader got locked, I had to do the whole procedure again,
Board sw 1.0.0.39 , and
-Alf- said:
Download TWRP Service ROM oeminfo and
Recovery_ramdisk for Oreo
- Unpack Service ROM package, find dload folder and transfer it to the SD card WITHOUT UNPACKING IT.
- Also copy to the SD card downloaded recovery_ramdisk oeminfo file and TWRP
- Install TWRP over eRecovery (only read the principle, not download links)
- boot into TWRP , select Install image , find oeminfo file, mark 'oeminfo' and flash it.
- Go back to the main TWRP's menu, select Reboot and Turn off.
- Use three button combo and try to install Service ROM .
Click to expand...
Click to collapse
But I can not get it to work state, 3 button combo always fails.
Can I just simply flash all needed files by fastboot ot TWRP ?
What are all the necessary files for phone to boot up?
- kernel
-ramdisk
- recovery_ramdisk
- system
- cust
what else?
Can I just simply flash some custom ROM that will boot up after TWRP flash ?
BTW, why it should not be possible to directly flash erecovery from fastboot?
For me worked..
C:\adb>fastboot flash erecovery_ramdisk TWRP-oreo-smart.img
target reported max download size of 471859200 bytes
sending 'erecovery_ramdisk' (24790 KB)...
OKAY [ 0.660s]
writing 'erecovery_ramdisk'...
OKAY [ 0.128s]
finished. total time: 0.796s
hdano said:
what else?
Click to expand...
Click to collapse
Nothing.
But keep in mind, that "writing OKAY" does not mean that the file is actually installed (it is too long story to tell why...).
hdano said:
BTW, why it should not be possible to directly flash erecovery from fastboot?
For me worked..
Click to expand...
Click to collapse
Running working stock firmware it's impossible.
hdano said:
Hi,
Can someone please help me with fix of my P20 lite dual?
I try to fix it for 50 hours in total, I downloaded about 150Gb of files ☹
The begining of my problem started from full working state one day, next morning I got error "your device has failed verification and may not work properly"
Phone was running stock ANE-LX1 9.1.0 C432 E6R1P7
Factory reset and cache wipe did not help.
Any attempt to SD or USB update via recovery failed, always got "Install failed"
So I tried flashing file update.app using MRT from some higher version of stock sw in fastboot, then in stock recovery, later in TWRP.
No luck, phone was in fastboot mode only or bootloops.
Then I found huawei flash tool IDT 2.0.0.9 and factory board sw 1.0.0.40 using test point (HUAWEI COM 1.0)
With this one the phone fully boots in factory firmware, but phone info says model HAT, has bootlogo ASCEND and android logo , IMEIs in menu are OK.
So how the hell can I get it back to official stock state with ANE-LX1 in "About phone"?
Any attempt of flashing ANE-LX1 sw from menu or stock recovery gives me Flash failed message.
From what I found, I probably need 3 file firmware FullOtaMF for HwOta tool, but nowhere can be found.
Or is there some easy way to flash to official ?
Or did I messed up some system files that need to be fixed?
PS: while flashing hundred of files I found one TWRP version, that can change BL lock code, so I changed it to 111111111111111 for easier unlock in future attempts.
Can be this a problem? (I hope not)
Thank you for any ideas !
Click to expand...
Click to collapse
I’ve exactly the same as your issue.
But I’ve no service and dual iemis are right!
What could be the problem, did you solve yours?
Or even were you having same no service issue while you were on this case?
My device originally is nova 3e ANE l-LX1 c185 dual sim and flashed oeminfo for c185 by editing the oeminfo for c432 and by using oeminfo tools.
Also using howta8 to change oeminfo.
It was changed ok to c185 but still no service and software not installed.
I used build 160 because it’s the only have 3 files, it was installed from hisuite document/hisuite/rom folder