Related
As the topic
Wysłane z mojego XT1650 przy użyciu Tapatalka
[email protected] said:
As the topic
Wysłane z mojego XT1650 przy użyciu Tapatalka
Click to expand...
Click to collapse
There's probably guides on it around here, maybe in the general section.
Curious why though? And if the Z is like the X, it won't return to "locked" state, it will go to "relocked." I don't know that for a fact, but that's how the X is. So it won't help for warranty, plus they already know you unlocked if you used their site. And not sure apps looking for a locked bootloader will accept "relocked." But that's purely a guess.
BTW, of its like other devices, you lock it using fastboot.
With command "fastboot oem lock"
the instruction for lock the boot of moto z
Darth said:
There's probably guides on it around here, maybe in the general section.
Curious why though? And if the Z is like the X, it won't return to "locked" state, it will go to "relocked." I don't know that for a fact, but that's how the X is. So it won't help for warranty, plus they already know you unlocked if you used their site. And not sure apps looking for a locked bootloader will accept "relocked." But that's purely a guess.
BTW, of its like other devices, you lock it using fastboot.
With command "fastboot oem lock"
Click to expand...
Click to collapse
hi for you can lock the bootloader i locked od the my moto z and i can help you
first need the rom with the you want to relock your phone if is the stock is so much better
don´t care if you have the ota nougat update installed, i locked my phone next of intall de nougat via ota update
flash twrp wipe the system of the phone in advance
next you have to rund the next comand
fastboot oem lock
fastboot oem lock
fastboot flash boot boot.img
fastboot flash recovery recovery.img
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 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 oem lock
wait and thats all your phone restart with your boot locked
Made a batch file (edited from evogp autoscript file for moto z play) for relocking. worked with my flashing 25.86--17-3-4 on my retus. Make sure you update it with the amount of sparsechunks you have
phone shows as oem_locked but with modified software (probably wrong firmware or something on mine since i manually flash nougat on it from other software channels)
https://drive.google.com/open?id=0By5BhZqSOZAESk1PYXZ3dnZFYXM
taphius said:
Made a batch file (edited from evogp autoscript file for moto z play) for relocking. worked with my flashing 25.86--17-3-4 on my retus. Make sure you update it with the amount of sparsechunks you have
phone shows as oem_locked but with modified software (probably wrong firmware or something on mine since i manually flash nougat on it from other software channels)
https://drive.google.com/open?id=0By5BhZqSOZAESk1PYXZ3dnZFYXM
Click to expand...
Click to collapse
If I understand you correctly, this flashes the original firmware. How did you get your modified ROM on the phone then?
7bob said:
If I understand you correctly, this flashes the original firmware. How did you get your modified ROM on the phone then?
Click to expand...
Click to collapse
It flashes whatever firmware is in the folder with it. I'm on a stock room but bootloader shows as custom software. Probably due to flashing retmx or retbr before
That doesn't seem to work, I can't even flash the original boot.img:
Code:
~ $ fastboot flash boot boot.img
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:boot: not found
target reported max download size of 536870912 bytes
sending 'boot' (32768 KB)...
OKAY [ 0.110s]
writing 'boot'...
(bootloader) Security version downgrade
(bootloader) Image boot failed validation
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.598s
boot.img and recovery.img are not signed by Motorola. So there is atm no way to (re)lock the Bootloader
kaliberx said:
boot.img and recovery.img are not signed by Motorola. So there is atm no way to (re)lock the Bootloader
Click to expand...
Click to collapse
I used the script to relock my own bootloader.
He looks like he is trying to flash an older boot image. Try a newer one.
I'll throw what exactly I did in a few once I get time, I updated to 25.86-17-3-4 flashing everything from evogps script first, then ran my relock
used this to flash everything per evogps script
@Echo off
ECHO.
ECHO. Script by @evogp ...
ECHO.
ECHO.
ECHO. Flashing Bootloader and more...
ECHO.
mfastboot flash partition gpt.bin
mfastboot flash bootloader bootloader.img
mfastboot flash dsp adspso.bin
mfastboot flash logo logo.bin
mfastboot flash boot boot.img
mfastboot flash recovery recovery.img
ECHO.
ECHO. Flashing System ...
ECHO.
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 system system.img_sparsechunk.8
mfastboot flash system system.img_sparsechunk.9
mfastboot flash system system.img_sparsechunk.10
mfastboot flash system system.img_sparsechunk.11
mfastboot flash system system.img_sparsechunk.12
mfastboot flash system system.img_sparsechunk.13
mfastboot flash system system.img_sparsechunk.14
mfastboot flash system system.img_sparsechunk.15
mfastboot flash system system.img_sparsechunk.16
mfastboot flash oem oem.img
ECHO.
ECHO. Wipe Cache and Data ...
ECHO.
mfastboot erase carrier
mfastboot erase cache
mfastboot erase userdata
mfastboot erase DDR
mfastboot oem fb_mode_clear
ECHO.
ECHO. Installation Complete!
ECHO.
PAUSE
mfastboot reboot
EXIT /b 0
then used my relock script after to lock bootloader.
Again, and it is said many Times here in the Moto Z Forums :
impossible to lock, because firmware-images are all NOT singed by Motorola, to be exact : boot.img and recovery.img.
https://mobilesupport.lenovo.com/us/en/solution/MS91987
Well and these signed Images, arent in the Wild. Only Lenovo/Motorola has them, here :
https://motorola-global-portal.cust...edirect/standalone/bootloader/recovery-images
but only for some Devices, and there is no Moto Z yet in the List. So the only Way is to send it in to get it relocked correctly, and they maybe will charge you for the Process/Service.
kaliberx said:
Again, and it is said many Times here in the Moto Z Forums :
impossible to lock, because firmware-images are all NOT singed by Motorola, to be exact : boot.img and recovery.img.
https://mobilesupport.lenovo.com/us/en/solution/MS91987
Well and these signed Images, arent in the Wild. Only Lenovo/Motorola has them, here :
https://motorola-global-portal.cust...edirect/standalone/bootloader/recovery-images
but only for some Devices, and there is no Moto Z yet in the List. So the only Way is to send it in to get it relocked correctly, and they maybe will charge you for the Process/Service.
Click to expand...
Click to collapse
It most definitely works for my Moto Z, uploading a video shortly of it. Able to add a CC to android pay so apparently passed safety check
Skip to 8 minutes or so, thats when it relocks and reboots, no unlocked bootloader warning etc.
pardon the error in the center, had to rename mfastboot as fastboot in the script and fuggered it.
https://streamable.com/ye735
taphius said:
It most definitely works for my Moto Z, uploading a video shortly of it. Able to add a CC to android pay so apparently passed safety check
Skip to 8 minutes or so, thats when it relocks and reboots, no unlocked bootloader warning etc.
pardon the error in the center, had to rename mfastboot as fastboot in the script and fuggered it.
https://streamable.com/ye735
Click to expand...
Click to collapse
And the current status of phone
taphius said:
It most definitely works for my Moto Z, uploading a video shortly of it. Able to add a CC to android pay so apparently passed safety check
Skip to 8 minutes or so, thats when it relocks and reboots, no unlocked bootloader warning etc.
pardon the error in the center, had to rename mfastboot as fastboot in the script and fuggered it.
https://streamable.com/ye735
Click to expand...
Click to collapse
Well I'll be damned... Cool
OK Taphus then do go a bit deeper into your Specs :
What was the Devices Retxx before you unlocked, and which firmware RetXX used you to relock the bootloader ?
I was RETEU (Germany) before, but because there is only a 6.01 Image, it isnt possible to flash with Nougat Bootloader.
SO i used and tried RETBR, RETMX and RETLA, got all onto the latest Security Patchlevel, but i didnt got the Bootloader locked at all.
And here Moto says that only they can do it.
kaliberx said:
OK Taphus then do go a bit deeper into your Specs :
What was the Devices Retxx before you unlocked, and which firmware RetXX used you to relock the bootloader ?
I was RETEU (Germany) before, but because there is only a 6.01 Image, it isnt possible to flash with Nougat Bootloader.
SO i used and tried RETBR, RETMX and RETLA, got all onto the latest Security Patchlevel, but i didnt got the Bootloader locked at all.
And here Moto says that only they can do it.
Click to expand...
Click to collapse
retus, flashed XT1650-03_GRIFFIN_7.0_NPLS25.86-17-3-4_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml in the video.
I flashed retmx/retca or whatever was the way to get nougat on the US model before it released for us as well.
taphius said:
retus, flashed XT1650-03_GRIFFIN_7.0_NPLS25.86-17-3-4_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml in the video.
I flashed retmx/retca or whatever was the way to get nougat on the US model before it released for us as well.
Click to expand...
Click to collapse
Yes and thats it : The Image checks the Device, if it's on the same Retail-Channel (Thats why you're on the RetEU-Software-Channel, even if you flash a RetMX Image).
So if the Retail-Channel of the Image differs from the Channel on the Device : Bad Key, GPT wont flash and Bootloader Lock not possible, until you send it in to Motorola or Motorola releases a Image for your Channel.
So i have to correct myself : Images are signed, but only for the RET-Channel of your Device.
Could you please extract and post your bootloader.img? I am in version 91.05 and it does not allow boot.img to flash as the boot.img has bad key or no key. I am able to flash outside fastboot oem lock command, but if I issue a oem lock command, my version of bootloader is not allowing me to flash boot image.
edit: I got the bootloader but everything else flashes but the gpt bin, and hence I am unable to flash boot.img..
anilisanil said:
Could you please extract and post your bootloader.img? I am in version 91.05 and it does not allow boot.img to flash as the boot.img has bad key or no key. I am able to flash outside fastboot oem lock command, but if I issue a oem lock command, my version of bootloader is not allowing me to flash boot image.
edit: I got the bootloader but everything else flashes but the gpt bin, and hence I am unable to flash boot.img..
Click to expand...
Click to collapse
my boot img was from the firmware file i used.
I re-locked it using this method , it worked but after getting it up and running I did an OTA update and bricked my device. Once I get it back on , can I still use fastboot to load the ROM?
guys, help please, where do I get signed boot image ?
Hi,
I unlocked my bootloader and installed LineageOS on my Moto Z.
For security reasons, I wanted to re-lock my bootloader using
Code:
fastboot oem lock
. When doing so, I got this warning:
Code:
~ $ fastboot oem lock
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
...
(bootloader) WARNING: This command erases all user data.
(bootloader) Please re-run this command to continue.
OKAY [ 0.000s]
finished. total time: 0.000s
I was wondering if locking the bootloader would really wipe all user data. Has anyone tried and can confirm that?
Thanks,
Bob
Yes it will wipe all of your data.
Sent from my XT1650-03 using Tapatalk
Somcom3X said:
Yes it will wipe all of your data.
Click to expand...
Click to collapse
Thank you for your quick reply. Did you try it?
And is there some other way to lock the bootloader, without wiping data?
7bob said:
Thank you for your quick reply. Did you try it?
And is there some other way to lock the bootloader, without wiping data?
Click to expand...
Click to collapse
Yes, I have unlocked multiple bootloaders [emoji6]
No, there is no other way as of now.
Sent from my XT1650-03 using Tapatalk
Somcom3X said:
Yes, I have unlocked multiple bootloaders [emoji6]
Click to expand...
Click to collapse
Just to make sure, I'm talking about LOCKING the bootloader, not unlocking!
7bob said:
Just to make sure, I'm talking about LOCKING the bootloader, not unlocking!
Click to expand...
Click to collapse
When you lock your bootloader, it should not effect your data at all. Whenever you unlock it, it will wipe your data.
Sent from my XT1650-03 using Tapatalk
Somcom3X said:
When you lock your bootloader, it should not effect your data at all. Whenever you unlock it, it will wipe your data.
Click to expand...
Click to collapse
Are you sure about that? I was getting the warning like quoted in the first post, so I'm hesitant to try it out.
7bob said:
Are you sure about that? I was getting the warning like quoted in the first post, so I'm hesitant to try it out.
Click to expand...
Click to collapse
Well... It looks like they changed it. It appears I misread your first post. As the warning states, it will likely wipe your data. Sorry about that.
Sent from my XT1650-03 using Tapatalk
7bob said:
Are you sure about that? I was getting the warning like quoted in the first post, so I'm hesitant to try it out.
Click to expand...
Click to collapse
Did you lock your bootloader yet?
Sent from my XT1650 using Tapatalk
how to lock of the bootloader
7bob said:
Hi,
I unlocked my bootloader and installed LineageOS on my Moto Z.
For security reasons, I wanted to re-lock my bootloader using
Code:
fastboot oem lock
. When doing so, I got this warning:
Code:
~ $ fastboot oem lock
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
...
(bootloader) WARNING: This command erases all user data.
(bootloader) Please re-run this command to continue.
OKAY [ 0.000s]
finished. total time: 0.000s
I was wondering if locking the bootloader would really wipe all user data. Has anyone tried and can confirm that?
Thanks,
Bob
Click to expand...
Click to collapse
hi for you can lock the bootloader i locked od the my moto z and i can help you
first need the rom with the you want to relock your phone if is the stock is so much better
don´t care if you have the ota nougat update installed, i locked my phone next of intall de nougat via ota update
flash twrp wipe the system of the phone in advance
next you have to rund the next comand
fastboot oem lock
fastboot oem lock
fastboot flash boot boot.img
fastboot flash recovery recovery.img
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 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 oem lock
wait and thats all your phone restart with your boot locked
PiousInquisitor said:
Did you lock your bootloader yet?
Click to expand...
Click to collapse
No.
oxido_pank said:
hi for you can lock the bootloader i locked od the my moto z and i can help you
first need the rom with the you want to relock your phone if is the stock is so much better
don´t care if you have the ota nougat update installed, i locked my phone next of intall de nougat via ota update
flash twrp wipe the system of the phone in advance
Click to expand...
Click to collapse
Thanks for the hints, but will that process wipe user data?
7bob said:
No.
Thanks for the hints, but will that process wipe user data?
Click to expand...
Click to collapse
Yeah because you make a flash of system
I Ever Say make a backup of the files that you need first
Next of flash restore all files and this all, but before make a hard reset of your phone
Nice day
I tried today, but I didn't succeed:
Code:
~ $ fastboot oem lock
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
...
(bootloader) WARNING: This command erases all user data.
(bootloader) Please re-run this command to continue.
OKAY [ 0.000s]
finished. total time: 0.000s
~ $ fastboot oem lock
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
...
(bootloader) Flash valid Android images now
(bootloader) Then re-run this command to lock
OKAY [ 0.001s]
finished. total time: 0.001s
~ $ fastboot oem lock
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
...
(bootloader) Still require signed boot.img
OKAY [ 0.000s]
finished. total time: 0.001s
So it seems that I cannot lock the bootloader by just executing fastboot oem lock two or three times. At least nothing was wiped after executing the commands.
7bob said:
I tried today, but I didn't succeed:
Code:
~ $ fastboot oem lock
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
...
(bootloader) WARNING: This command erases all user data.
(bootloader) Please re-run this command to continue.
OKAY [ 0.000s]
finished. total time: 0.000s
~ $ fastboot oem lock
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
...
(bootloader) Flash valid Android images now
(bootloader) Then re-run this command to lock
OKAY [ 0.001s]
finished. total time: 0.001s
~ $ fastboot oem lock
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
...
(bootloader) Still require signed boot.img
OKAY [ 0.000s]
finished. total time: 0.001s
So it seems that I cannot lock the bootloader by just executing fastboot oem lock two or three times. At least nothing was wiped after executing the commands.
Click to expand...
Click to collapse
It doesn't let you lock the bootloader with a "bad" (i.e. non-stock) kernel or special partitions (e.g. oem) etc. But you're lucky: if it had relocked the bootloader in the current setup you could have easily 'bricked' your phone. Instead, it checks the signatures of various components first and only if it finds valid (stock-rom)-signatures, the lock comes back on.
If you still want to put the lock on, flash a valid stock-rom (version: like the most recent stock rom version your phone has ever seen, or newer. The bootloader doesn't allow downgrading).
You can do it all at once or step by step: gpt.bin first, then boot.img, recovery.img .... check puttin on the lock... Then it'll complain what else it wants you to flash next.. and so on. In the end, the bootloader will be locked and there is no immediate sign that it was ever unlocked.
benzinerwin said:
[...]
If you still want to put the lock on, flash a valid stock-rom (version: like the most recent stock rom version your phone has ever seen, or newer. The bootloader doesn't allow downgrading).
[...]
Click to expand...
Click to collapse
This would be the exact problem of most of the people here including myself, when trying to relock the bootloader.
I'm using the reteu variant of 1650-03 and am unable to get a stock ROM which is working with "fasboot oem lock begin".
Tried the "XT1650-03_GRIFFIN_RETBR_NPL25.86-30_cid50_subsidy-DEFAULT_regulatory-DEFAULT" as this seems to be te latest available. Unfortunately, this ROM seems to be too old, cause before unlocking/rooting etc I updated to latest april OTA...
Getting this:
Code:
(bootloader) Security version downgrade
(bootloader) Image boot failed validation
(bootloader) Preflash validation failed
FAILED (remote failure)
sp4rt4n-i17 said:
This would be the exact problem of most of the people here including myself, when trying to relock the bootloader.
I'm using the reteu variant of 1650-03 and am unable to get a stock ROM which is working with "fasboot oem lock begin".
Tried the "XT1650-03_GRIFFIN_RETBR_NPL25.86-30_cid50_subsidy-DEFAULT_regulatory-DEFAULT" as this seems to be te latest available. Unfortunately, this ROM seems to be too old, cause before unlocking/rooting etc I updated to latest april OTA...
Getting this:
Code:
(bootloader) Security version downgrade
(bootloader) Image boot failed validation
(bootloader) Preflash validation failed
FAILED (remote failure)
Click to expand...
Click to collapse
Ok, you're right, the error message clearly states that the NPL25.86-30 package is "too old"...
Which was the most recent version of Nougat you had on your phone?
What ist the current bootloader version (e.g. BL 91.05)?
benzinerwin said:
Ok, you're right, the error message clearly states that the NPL25.86-30 package is "too old"...
Which was the most recent version of Nougat you had on your phone?
What ist the current bootloader version (e.g. BL 91.05)?
Click to expand...
Click to collapse
Version was NPLS25.86-30-12 and BL is 91.05
sp4rt4n-i17 said:
Version was NPLS25.86-30-12 and BL is 91.05
Click to expand...
Click to collapse
Hm, and now you're trying to restore the RETBR-NPL25.86-30 image that's causing the error messages?
From what it looks like, I'd assume that you updated e.g. via OTA to even more recent versions...
If not, did you make sure that you actually unpacked the right zip file, you opened a dos window and changed into the folder of this unpacked archive, have fastboot.exe within your path or copied it into the unpacked folder..
You may try this RETMX image as an alternative: https://moto.shreps.fr/Moto Z (grif...ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
Either flash all at once and the lock the bootloader... (be aware: you're losing all userdata)
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 oem lock
fastboot oem lock
Or do only the required steps, e.g.
Code:
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot oem lock
fastboot oem lock
then ... if it moans about boot.img ...
Code:
fastboot flash boot boot.img
fastboot oem lock
fastboot oem lock
it probably dislikes the current oem partition...
Code:
fastboot flash oem oem.img
fastboot oem lock
fastboot oem lock
and so on...
Best would be to flash everything and then lock the bootloader...
But just start with flashing the gpt.bin & bootloader.img and report back how that worked...
benzinerwin said:
Hm, and now you're trying to restore the RETBR-NPL25.86-30 image that's causing the error messages?
From what it looks like, I'd assume that you updated e.g. via OTA to even more recent versions...
If not, did you make sure that you actually unpacked the right zip file, you opened a dos window and changed into the folder of this unpacked archive, have fastboot.exe within your path or copied it into the unpacked folder..
You may try this RETMX image as an alternative: https://moto.shreps.fr/Moto Z (grif...ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
Either flash all at once and the lock the bootloader... (be aware: you're losing all userdata)
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 oem lock
fastboot oem lock
Or do only the required steps, e.g.
Code:
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot oem lock
fastboot oem lock
then ... if it moans about boot.img ...
Code:
fastboot flash boot boot.img
fastboot oem lock
fastboot oem lock
it probably dislikes the current oem partition...
Code:
fastboot flash oem oem.img
fastboot oem lock
fastboot oem lock
and so on...
Best would be to flash everything and then lock the bootloader...
But just start with flashing the gpt.bin & bootloader.img and report back how that worked...
Click to expand...
Click to collapse
Flashing (via fastboot) the NPL25.86-30 without trying to relock the BL is no problem, did this several times (on other devices too )
You're right -like I wrote before - I've updated the device via OTA to latest april patch and I think that could cause the problem with relocking.
Other problem could be that one really need to use a (latest/Nougat) RETEU stock ROM for relocking RETEU device. I do not really know IF there is a diference between RETBR/RETMX and RETEU stock ROMs, as obviosly RETBR is working with my RETEU device and softwarechannel in "About device" is showing "reteu", but for relocking it could be necessary to use a stock RETEU ROM.
As I'm having TWRP installed, the loss of all data is no problem, and I will try what you suggested.
Final thought on this:
Solution could be just waiting for an up-to-date RETEU stock ROM with latest patchlevel or at least one which is above april (for now) and then try to relock BL with flashing this one.
I'm not in the situation that I really need a locked BL, but for research and in case of reselling the device, a solution for this problem would be great to know.
benzinerwin said:
Hm, and now you're trying to restore the RETBR-NPL25.86-30 image that's causing the error messages?
From what it looks like, I'd assume that you updated e.g. via OTA to even more recent versions...
If not, did you make sure that you actually unpacked the right zip file, you opened a dos window and changed into the folder of this unpacked archive, have fastboot.exe within your path or copied it into the unpacked folder..
You may try this RETMX image as an alternative: https://moto.shreps.fr/Moto Z (grif...ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
Either flash all at once and the lock the bootloader... (be aware: you're losing all userdata)
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 oem lock
fastboot oem lock
Or do only the required steps, e.g.
Code:
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot oem lock
fastboot oem lock
then ... if it moans about boot.img ...
Code:
fastboot flash boot boot.img
fastboot oem lock
fastboot oem lock
it probably dislikes the current oem partition...
Code:
fastboot flash oem oem.img
fastboot oem lock
fastboot oem lock
and so on...
Best would be to flash everything and then lock the bootloader...
But just start with flashing the gpt.bin & bootloader.img and report back how that worked...
Click to expand...
Click to collapse
It says ''still required signed boot.img''
Guess we don't have that yet :crying:
Very recently, I unlocked my bootloader and installed Lineage 14.1 on EU Moto Z retail version bought from Germany. I would now like to go back to the stock firmware that came with the phone.
I tried to download the following rom https://forum.xda-developers.com/moto-z/development/moto-z-official-firmware-downloads-t3449837 and tried to flash each component separately using the fastboot command.
But everytime I try to flash gpt.bin :
Code:
fastboot flash partition gpt.bin
I get an error:
Code:
sending 'partition' (32 KB)...
OKAY [ 0.059s]
writing 'partition'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.474s
I was wondering if there's a more consistent way to flash the stock rom back? A guide somewhere would be really helpful. I tried searching everywhere but didn't have any luck.
Spaniard89 said:
Very recently, I unlocked my bootloader and installed Lineage 14.1 on EU Moto Z retail version bought from Germany. I would now like to go back to the stock firmware that came with the phone.
I tried to download the following rom https://forum.xda-developers.com/moto-z/development/moto-z-official-firmware-downloads-t3449837 and tried to flash each component separately using the fastboot command.
But everytime I try to flash gpt.bin :
Code:
fastboot flash partition gpt.bin
I get an error:
Code:
sending 'partition' (32 KB)...
OKAY [ 0.059s]
writing 'partition'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.474s
I was wondering if there's a more consistent way to flash the stock rom back? A guide somewhere would be really helpful. I tried searching everywhere but didn't have any luck.
Click to expand...
Click to collapse
First of all, you have to use an Android 7 Image, most recent should be RETBR.
I was in the same situation, there is no need for flashing gpt.bin, the other files will work.
Your BL is more up-to-date than the most recent image and I think another problem is that it isn't RETEU...this will cause the error, however, it will work and you will get softwarechannel "reteu".
Only flaw will be, that you're unable to relock the BL.
Hope this helps.
PN me, if you want more information in german.
Gesendet von meinem XT1650 mit Tapatalk
sp4rt4n-i17 said:
First of all, you have to use an Android 7 Image, most recent should be RETBR.
I was in the same situation, there is no need for flashing gpt.bin, the other files will work.
Your BL is more up-to-date than the most recent image and I think another problem is that it isn't RETEU...this will cause the error, however, it will work and you will get softwarechannel "reteu".
Only flaw will be, that you're unable to relock the BL.
Hope this helps.
PN me, if you want more information in german.
Gesendet von meinem XT1650 mit Tapatalk
Click to expand...
Click to collapse
Thanks a lot for the info, where can I find the Android 7 image for moto Z? and what would be the steps in this case? Should I just install the zip file via twrp?
Spaniard89 said:
Thanks a lot for the info, where can I find the Android 7 image for moto Z? and what would be the steps in this case? Should I just install the zip file via twrp?
Click to expand...
Click to collapse
take a look here
and choose "XT1650-03_GRIFFIN_RETBR_NPL25.86-30_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip"
you have to flash it via fastboot ... btw: TWRP will be gone after flashing, this is 'cause you will flash the original recovery (you will need this for OTA anyway)
steps would be:
0. download files, obviously
1. install motorola device manager, which should include fastboot drivers
2. install minimal adb&fastboot
3. extract files from zip and put them in the same directory as fastboot.exe (should be "C:\Program Files (x86)\Minimal ADB and Fastboot")
3. boot phone into fastboot mode (power off, power on while holding power+volume down, then choose "fastboot mode")
4. flash via fastboot:
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 oem oem.img
fastboot erase cache
fastboot erase userdata
fastboot erase customize
fastboot erase clogo
fastboot erase ddr (don't know if this is nessecary)
fastboot reboot
5. profit?
if you need TWRP after this process: you could just "boot it" via "fastboot boot twrp.img" without installing it
sp4rt4n-i17 said:
take a look here
and choose "XT1650-03_GRIFFIN_RETBR_NPL25.86-30_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip"
you have to flash it via fastboot ... btw: TWRP will be gone after flashing, this is 'cause you will flash the original recovery (you will need this for OTA anyway)
steps would be:
0. download files, obviously
1. install motorola device manager, which should include fastboot drivers
2. install minimal adb&fastboot
3. extract files from zip and put them in the same directory as fastboot.exe (should be "C:\Program Files (x86)\Minimal ADB and Fastboot")
3. boot phone into fastboot mode (power off, power on while holding power+volume down, then choose "fastboot mode")
4. flash via fastboot:
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 oem oem.img
fastboot erase cache
fastboot erase userdata
fastboot erase customize
fastboot erase clogo
fastboot erase ddr (don't know if this is nessecary)
fastboot reboot
5. profit?
if you need TWRP after this process: you could just "boot it" via "fastboot boot twrp.img" without installing it
Click to expand...
Click to collapse
Thanks you very much. I am sure this will help a lot of other people out there.
It was already discussed into oblivion ...
https://forum.xda-developers.com/showpost.php?p=72008543&postcount=187
I saw that this is an old post but it did not helped me with my moto Z. I had android 8.0 installed on my moto Z and wifi was not working at all, bluetooth and wifi were disabled whole time, and phone frozed 30 sec after startup.
Following instruction from this post I installed android 7 on phone. Now phone is not freezing anymore but wifi and BT are still disabled. Can someone help me to choose correct ROM from this link? How to choose the one I need? I need something for Europe and to be Android 6.
Galera pra quem ainda nao conseguiu a rom do moto z play / droid ou / z2 eu recomendo pegar a rom no site da motorola .. tem 3 opçao la de rom ,,
Hi everyone.
Yesterday I unlocked the bootloader of my P20 Lite through DC-Unlocked (paid 4 euro) and I rooted it by flashing a patched ramdisk. It was on android 8 because I had to roll back the version to allow DC-Unlocker to get the bootloader code. Anyways, I wanted to upgrade to android 9.0 again but I ran into a major issue. Like an idiot, I tried flashing the update through the TWRP, and so now the phone is hard bricked.
On boot, I get the ERROR MODE screen which gives
Code:
Func NO: 10(recovery image)
Error No: 2(load failed!)
I tried flashing every single .img possible from the UPDATE.APP, but that doesn't do the trick. One thing that I've noticed is that the RAMDISK partition seems to have vanished, because when I try to flash it through fastboot, it gives me
Code:
FAILED (remote: partition length get error)
So I don't actually know how to flash the boot partitions, which is probably the culprit of the issue. I can only flash KERNEL.img but not RAMDISK.IMG.
Oh, and also, as you may have guessed, I can't even boot in recovery anymore.
Now I'm trying to download a FULLOTA-MF which, they say, should unbrick the phone via forced DLOAD method.
Anyone had this experience? Thanks in advance.
andreasaracino said:
Hi everyone.
Yesterday I unlocked the bootloader of my P20 Lite through DC-Unlocked (paid 4 euro) and I rooted it by flashing a patched ramdisk. It was on android 8 because I had to roll back the version to allow DC-Unlocker to get the bootloader code. Anyways, I wanted to upgrade to android 9.0 again but I ran into a major issue. Like an idiot, I tried flashing the update through the TWRP, and so now the phone is hard bricked.
On boot, I get the ERROR MODE screen which gives
Code:
Func NO: 10(recovery image)
Error No: 2(load failed!)
I tried flashing every single .img possible from the UPDATE.APP, but that doesn't do the trick. One thing that I've noticed is that the RAMDISK partition seems to have vanished, because when I try to flash it through fastboot, it gives me
Code:
FAILED (remote: partition length get error)
So I don't actually know how to flash the boot partitions, which is probably the culprit of the issue. I can only flash KERNEL.img but not RAMDISK.IMG.
Oh, and also, as you may have guessed, I can't even boot in recovery anymore.
Now I'm trying to download a FULLOTA-MF which, they say, should unbrick the phone via forced DLOAD method.
Anyone had this experience? Thanks in advance.
Click to expand...
Click to collapse
Hello,
- 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:
Hello,
- 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
Hi, thanks for your fast answer!
fastboot oem get-build-number
Code:
(bootloader) :System 8.0.0.046(09B8)
OKAY [ 0.012s]
finished. total time: 0.012s
fastboot oem get-product-model
Code:
(bootloader) ANE-LX1
OKAY [ 0.011s]
finished. total time: 0.011s
fastboot getvar vendorcountry
Code:
vendorcountry: ti/it
finished. total time: 0.012s
fastboot oem oeminforead-CUSTOM_VERSION
Code:
FAILED (remote: Read oeminfo failed!)
finished. total time: 0.019s
fastboot oem oeminforead-SYSTEM_VERSION
Code:
(bootloader) :ANE-LX1 8.0.0.151(C55)
OKAY [ 0.013s]
finished. total time: 0.014s
I don't know why but the CUSTOM_VERSION reading failed...
according to the results from the fastboot you have a branded phone, maybe a single sim?
Good news is that you are still on A8, bad news is "ti/it ".
Try this :
- Download and flash stock recovery_ramdisk for Oreo
recovery_ramdisk
Use command
fastboot flash recovery_ramdisk (file_name).img
Then try boot into recovery and let me know, thanks.
What is (was) your region in your phone build number ? (for example C432, C10, C185...)
-Alf- said:
What is (was) your region in your phone build number ? (for example C432, C10, C185...)
Click to expand...
Click to collapse
I think it's C55 , correct me if I'm wrong...
-Alf- said:
according to the results from the fastboot you have a branded phone, maybe a single sim?
Good news is that you are still on A8, bad news is "ti/it ".
Try this :
- Download and flash stock recovery_ramdisk for Oreo
recovery_ramdisk
Use command
fastboot flash recovery_ramdisk (file_name).img
Then try boot into recovery and let me know, thanks.
Click to expand...
Click to collapse
I tried, but doesn't work at all...
-Alf- said:
I think it's C55 , correct me if I'm wrong...
Click to expand...
Click to collapse
Yeah, it is C55. I don't know what to do anymore
andreasaracino said:
I tried, but doesn't work at all...
Yeah, it is C55. I don't know what to do anymore
Click to expand...
Click to collapse
recovery_ramdisk installing using command fastboot flash recovery_ramdisk etc.
was unsuccessful?
Have you tried boot into eRecovery? There's an option in eRecovery "Download latest ....."
andreasaracino said:
Hi everyone.
Yesterday I unlocked the bootloader of my P20 Lite through DC-Unlocked (paid 4 euro) and I rooted it by flashing a patched ramdisk. It was on android 8 because I had to roll back the version to allow DC-Unlocker to get the bootloader code. Anyways, I wanted to upgrade to android 9.0 again but I ran into a major issue. Like an idiot, I tried flashing the update through the TWRP, and so now the phone is hard bricked.
On boot, I get the ERROR MODE screen which gives
Code:
Func NO: 10(recovery image)
Error No: 2(load failed!)
I tried flashing every single .img possible from the UPDATE.APP, but that doesn't do the trick. One thing that I've noticed is that the RAMDISK partition seems to have vanished, because when I try to flash it through fastboot, it gives me
Code:
FAILED (remote: partition length get error)
So I don't actually know how to flash the boot partitions, which is probably the culprit of the issue. I can only flash KERNEL.img but not RAMDISK.IMG.
Oh, and also, as you may have guessed, I can't even boot in recovery anymore.
Now I'm trying to download a FULLOTA-MF which, they say, should unbrick the phone via forced DLOAD method.
Anyone had this experience? Thanks in advance.
Click to expand...
Click to collapse
I did this once to my kiwi (5x) then it went totally blank when i tried flashing an Huawei related system flashing tool. Do not try that.
-Alf- said:
recovery_ramdisk installing using command fastboot flash recovery_ramdisk etc.
was unsuccessful?
Have you tried boot into eRecovery? There's an option in eRecovery "Download latest ....."
Click to expand...
Click to collapse
I can't manage to boot in eRecovery, I always get the Func No error...
But the flashing was successful, only it doesn't fix the issue with the recovery.
andreasaracino said:
I can't manage to boot in eRecovery, I always get the Func No error...
But the flashing was successful, only it doesn't fix the issue with the recovery.
Click to expand...
Click to collapse
Okay, try this way out...
- download Service ROM
- unpack, extract from UPDATE.APP files:
CUST.img, RAMDISK.img, SYSTEM.img , RECOVERY_RAMDISK.img using Huawei update extractor, and flash .img files through fastboot. (CUST.img can be found in second UPDATE.APP (update_sd_ANE-L01_hw......zip) folder.
-Alf- said:
Okay, try this way out...
- download Service ROM
- unpack, extract from UPDATE.APP files:
CUST.img, RAMDISK.img, SYSTEM.img , RECOVERY_RAMDISK.img using Huawei update extractor, and flash .img files through fastboot. (CUST.img can be found in second UPDATE.APP (update_sd_ANE-L01_hw......zip) folder.
Click to expand...
Click to collapse
Thank you very much Alf for your time, but I finally managed to unbrick the phone by dloading the FULLOTA-MF of which I wrote about in OP.
andreasaracino said:
Now I'm trying to download a FULLOTA-MF which, they say, should unbrick the phone via forced DLOAD method.
Click to expand...
Click to collapse
andreasaracino said:
Thank you very much Alf for your time, but I finally managed to unbrick the phone by dloading the FULLOTA-MF of which I wrote about in OP.
Click to expand...
Click to collapse
then it is not FULLOTA-MF but Service ROM, bro ...okay, it doesn't matter now.
Hello guys...
So, without going too much into details of how I idiotically f-ed up pretty much everything... I just want to say that I've already lost about 12 hours reading through the forum trying to solve the problem and to understand how everything works, and by what I understood... I bricked the phone?
Firstly, I managed to unlock the bootloader with the HCU Client (Phone unlocked, FRP unlocked). At some points I've managed to boot into TWRP's, but I flashed them without understanding that I should have installed the recommended ones by the guys on this forum instead of the official one, with which I wiped System and Data partition.
I've tried hard but never managed to boot any of the Custom ROMs available, especially the LineageOS 16 which I wanted but later on, through a specific TWRP which gave an error information that it's meant for Hisilicon, and not for Kirin SoC...
I also had no idea when I was booting into recovery, and when into erecovery, because I flashed TWRP over both of them... I have really no idea what was the last thing to happen, but now it seems as if I can't boot into eRecovery anymore, and whatever I try flashing to the recovery_ramdisk over Fastboot, I just always get the same error when trying to boot into recovery
Error! Func NO : 11 (recovery image)
Error NO : 2 (load failed!)
Now I'm also having an issue because my battery has drained and it doesn't seem to turn on without it being connected to the charger or a PC.
Is there anything that I can do to make it work with any Custom ROM?
returnedinformation said:
I've managed to boot into TWRP's, but I flashed them without understanding that I should have installed the recommended ones by the guys on this forum instead of the official one, with which I wiped System and Data partition.
Click to expand...
Click to collapse
This is the result of some people posting nonsense here.
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:
This is the result of some people posting nonsense here.
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
> fastboot oem get-build-number
(bootloader) :ANE-LX1 8.0.0.126(C432)
> fastboot oem get-product-model
(bootloader) ANE-LX1
> fastboot getvar vendorcountry
vendorcountry: hw/eu
> fastboot oem oeminforead-CUSTOM_VERSION
FAILED (remote: 'The reason of failed input oem_nv_item error!')
fastboot: error: Command failed
> fastboot oem oeminforead-SYSTEM_VERSION
(bootloader) :ANE-LX1 9.1.0.132(C432E5R1P7)
-Alf- said:
This is the result of some people posting nonsense here.
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
Click to expand...
Click to collapse
Alf is right:
Gather info about your phone with the fastboot commands -Alf- provided.
Using this info, find TWRP that 100% supports your phone. TWRP that is recommended in the "p20 lite basics" thread on XDA.
Start phone in fastboot mode. Use the fastboot boot twrp.img command to TEMPORARILY boot into TWRP (twrp.img must be in the same folder as fastboot.exe)
If TWRP hangs, reboot, try another TWRP
Once you are in TWRP, perform wipe and advanced wipe to clean up EVERY PARTITION (except sdcard) that you've messed up in the internal memory.
wipe data again to enable USB file transfer
Find a ROM for your phone. USE THE INFO FROM STEP 1 to figure out if the rom is REALLY for your model AND hardware revision of the phone. Pay attention to the device serial number and codename! ROMS developers use device codenames to indicate what model is compatible and what isnt. Huawei p20 lite has a total of 7(!!!) hardware revisions, and ROMS for each are different and likely NOT cross-compatible, which means if you install the wrong one, you will end up with a brick or a bootloop.
While TWRP is still on, Transfer ROM.zip to the phone.
In TWRP, use "Install" option to flash the ROM.
DO NOT FLASH TWRP PERMANENTLY! LET THE STOCK RECOVERY BE. FLASHING TWRP TO A/B (DUAL SLOT) DEVICES WILL 99% RESULT IN A BOOTLOOP. MOST MODERN DEVICES ARE A/B.
Flash Gapps if you need.
Reboot. Will take longer to start on the first boot.
Totesnochill said:
Alf is right:
Gather info about your phone with the fastboot commands -Alf- provided.
Using this info, find TWRP that 100% supports your phone.
Start phone in fastboot mode. Use the fastboot boot twrp.img command to TEMPORARILY boot into TWRP (twrp.img must be in the same folder as fastboot.exe)
If TWRP hangs, reboot, try another TWRP
Once you are in TWRP, perform wipe and advanced wipe to clean up EVERY PARTITION (except sdcard) that you've messed up in the internal memory.
wipe data again to enable USB file transfer
Find a ROM for your phone. USE THE INFO FROM STEP 1 to figure out if the rom is REALLY for your model AND hardware revision of the phone. Pay attention to the device serial number and codename! ROMS developers use device codenames to indicate what model is compatible and what isnt. Huawei p20 lite has a total of 7(!!!) hardware revisions, and ROMS for each are different and likely NOT cross-compatible, which means if you install the wrong one, you will end up with a brick or a bootloop.
While TWRP is still on, Transfer ROM.zip to the phone.
In TWRP, use "Install" option to flash the ROM.
DO NOT FLASH TWRP PERMANENTLY! LET THE STOCK RECOVERY BE. FLASHING TWRP TO A/B (DUAL SLOT) DEVICES WILL 99% RESULT IN A BOOTLOOP. MOST MODERN DEVICES ARE A/B.
Flash Gapps if you need.
Reboot. Will take longer to start on the first boot.
Click to expand...
Click to collapse
As I said before
-Alf- said:
some people posting nonsense here.
Click to expand...
Click to collapse
Totesnochill said:
Alf is right:
Gather info about your phone with the fastboot commands -Alf- provided.
Using this info, find TWRP that 100% supports your phone. TWRP that is recommended in the "p20 lite basics" thread on XDA.
Start phone in fastboot mode. Use the fastboot boot twrp.img command to TEMPORARILY boot into TWRP (twrp.img must be in the same folder as fastboot.exe)
If TWRP hangs, reboot, try another TWRP
Once you are in TWRP, perform wipe and advanced wipe to clean up EVERY PARTITION (except sdcard) that you've messed up in the internal memory.
wipe data again to enable USB file transfer
Find a ROM for your phone. USE THE INFO FROM STEP 1 to figure out if the rom is REALLY for your model AND hardware revision of the phone. Pay attention to the device serial number and codename! ROMS developers use device codenames to indicate what model is compatible and what isnt. Huawei p20 lite has a total of 7(!!!) hardware revisions, and ROMS for each are different and likely NOT cross-compatible, which means if you install the wrong one, you will end up with a brick or a bootloop.
While TWRP is still on, Transfer ROM.zip to the phone.
In TWRP, use "Install" option to flash the ROM.
DO NOT FLASH TWRP PERMANENTLY! LET THE STOCK RECOVERY BE. FLASHING TWRP TO A/B (DUAL SLOT) DEVICES WILL 99% RESULT IN A BOOTLOOP. MOST MODERN DEVICES ARE A/B.
Flash Gapps if you need.
Reboot. Will take longer to start on the first boot.
Click to expand...
Click to collapse
Sorry, but I'm already stuck at step 3:
PS C:\adb> fastboot boot twrp.img
Sending 'boot.img' (15652 KB) OKAY [ 0.411s]
Booting FAILED (remote: 'Command not allowed')
fastboot: error: Command failed
returnedinformation said:
Sorry, but I'm already stuck at step 3:
PS C:\adb> fastboot boot twrp.img
Sending 'boot.img' (15652 KB) OKAY [ 0.411s]
Booting FAILED (remote: 'Command not allowed')
fastboot: error: Command failed
Click to expand...
Click to collapse
I see. Some phones have this issue. where bootloader will not allow the "boot" command. Can be for a number of reasons:
1. Bootloader isnt "fully" unlocked, please check with the unlocking guide/service provider (if unlock was a paid service)
2. Bootloader is in "retail" mode, not a "service" mode. Some manufacturers do not intend for bootloader to be unlocked, and ship the devices with a restricted "retail" version that blocks certain commands.
also, why is your fastboot sending the "boot.img" while the command had " twrp img" as a payload?
I take it the bootloader still lets you use the "flash" command? If true, flash TWRP temporarily by "fastboot flash boot twrp.img", restart teh phone using the recovery menu keycombo
returnedinformation said:
> fastboot oem get-build-number
(bootloader) :ANE-LX1 8.0.0.126(C432)
> fastboot oem get-product-model
(bootloader) ANE-LX1
> fastboot getvar vendorcountry
vendorcountry: hw/eu
> fastboot oem oeminforead-CUSTOM_VERSION
FAILED (remote: 'The reason of failed input oem_nv_item error!')
fastboot: error: Command failed
> fastboot oem oeminforead-SYSTEM_VERSION
(bootloader) :ANE-LX1 9.1.0.132(C432E5R1P7)
Click to expand...
Click to collapse
you've mixed apples and oranges nicely .
Try this way out, using HuRupdater
Guide
Downloand TWRP
Here
Totesnochill said:
Some phones have this issue. where bootloader will not allow the "boot" command. Can be for a number of reasons
Click to expand...
Click to collapse
No, there is only one reason - on Huawei devices we do not have a "boot" partition since Android 7.
-Alf- said:
you've mixed apples and oranges nicely .
Try this way out, using HuRupdater
Guide
Downloand TWRP
Here
Click to expand...
Click to collapse
Thank you, I've put them in blender and set it to "lightspeed" mode
I'm sorry, but flashing that TWRP gives me the exact error I've been getting before when trying to boot into Recovery... the fact that the phone can't charge also gives some headache to actually even try to boot into the recovery. I just can't get into.
Edit: The furthest I can get to is that recovery error message.
hi there..was reading about your problem..i'm not sure if the same rules apply to all or most phones with regards to flashing twrp or using fastboot..i'm assuming that they do.
So, are you able to boot into fastboot and/or recovery?
if no to recovery, i guess it may be the wrong twrp, i hope you can at least boot into fastboot without any issues.
Personally i had a xiaomi poco f2 pro 6/128 and then i bought another same model phone but 8/256 from a fellow who almost bricked his phone..it was just blinking, when i restarted the phone, it went straight into blinking whenever i tried to boot into recovery, and it wouldnt boot into system anyway cos there was nothing there. so i figured it was stuck in recovery loop.
i was fortunate that i was able to hook up to it using my pc...then using command prompt, i was able to switch to fastboot mode..then i tried downloading and flashing different twrps, over 10 different twrps, and finally one worked..then it was smooth sailing from then on..and presto, that became my daily use phone.
returnedinformation said:
Thank you, I've put them in blender and set it to "lightspeed" mode
I'm sorry, but flashing that TWRP gives me the exact error I've been getting before when trying to boot into Recovery... the fact that the phone can't charge also gives some headache to actually even try to boot into the recovery. I just can't get into.
Edit: The furthest I can get to is that recovery error message.
Click to expand...
Click to collapse
Can you boot into eRecovery (into TWRP installee over eRecovery)? If so, try to flash eRecovery_ramdisk.img in TWRP,
download Here for EMUI 9.1
or Here for 8.0 (I'm not sure what is your current version).
In eRecovery mode you can charge the phone ( charging should also work in TWRP which is installed instead of eRecovery).
flashgordon65 said:
hi there..was reading about your problem..i'm not sure if the same rules apply to all or most phones with regards to flashing twrp or using fastboot..i'm assuming that they do.
So, are you able to boot into fastboot and/or recovery?
if no to recovery, i guess it may be the wrong twrp, i hope you can at least boot into fastboot without any issues.
Click to expand...
Click to collapse
-Alf- said:
Can you boot into eRecovery (into TWRP installee over eRecovery)? If so, try to flash eRecovery_ramdisk.img in TWRP,
download Here for EMUI 9.1
or Here for 8.0 (I'm not sure what is your current version).
In eRecovery mode you can charge the phone ( charging should also work in TWRP which is installed instead of eRecovery).
Click to expand...
Click to collapse
I can boot to the Fastboot, but unfortunately I can't boot to either recovery or erecovery... When trying to boot to the recovery by holding the power+volume up button until I see the "Your device has been unlocked" warning message + 2 seconds (which is when I see the recovery error message), or when trying to boot while plugged into USB also holding the power+volume up button just leaves me at "Your device is booting now...." forever
returnedinformation said:
I can boot to the Fastboot, but unfortunately I can't boot to either recovery or erecovery... When trying to boot to the recovery by holding the power+volume up button until I see the "Your device has been unlocked" warning message + 2 seconds (which is when I see the recovery error message), or when trying to boot while plugged into USB also holding the power+volume up button just leaves me at "Your device is booting now...." forever
Click to expand...
Click to collapse
doesn't look good bro, try the following :
in fastboot mode run commands
fastboot erase user data
fastboot reboot
-Alf- said:
doesn't look good bro, try the following :
in fastboot mode run commands
fastboot erase user data
fastboot reboot
Click to expand...
Click to collapse
PS C:\adb> fastboot erase user data
Erasing 'user' FAILED (remote: 'Command not allowed')
fastboot: error: Command failed
returnedinformation said:
PS C:\adb> fastboot erase user data
Erasing 'user' FAILED (remote: 'Command not allowed')
fastboot: error: Command failed
Click to expand...
Click to collapse
Sorry!
fastboot erase userdata
PS C:\adb> fastboot erase userdata
Erasing 'userdata' (bootloader) success to erase cryypt info in oeminfo
OKAY [ 0.215s]
Finished. Total time: 0.236s
PS C:\adb> fastboot reboot
Rebooting OKAY [ 0.024s]
Finished. Total time: 0.024s
Okay, what can I do now? I've tried flashing twrp right after that but solely rebooting get's me stuck at "Your device is booting now...", and trying to boot to recovery gives me the same error again
returnedinformation said:
PS C:\adb> fastboot erase userdata
Erasing 'userdata' (bootloader) success to erase cryypt info in oeminfo
OKAY [ 0.215s]
Finished. Total time: 0.236s
PS C:\adb> fastboot reboot
Rebooting OKAY [ 0.024s]
Finished. Total time: 0.024s
Okay, what can I do now? I've tried flashing twrp right after that but solely rebooting get's me stuck at "Your device is booting now...", and trying to boot to recovery gives me the same error again
Click to expand...
Click to collapse
Download stock Recovery Oreo
Link
Flash it in fastboot
fastboot flash recovery_ramdisk RECOVERY_RAMDISK-ANE-8.0.img
- fastboot reboot
Then try to boot into Recovery.
What exactly did you do after unlocking your phone? Did you upgrade back to A9? If so, then flash recovery_ramdisk A9
Download here
-Alf- said:
Download stock Recovery Oreo
Link
Flash it in fastboot
fastboot flash recovery_ramdisk RECOVERY_RAMDISK-ANE-8.0.img
- fastboot reboot
Then try to boot into Recovery.
What exactly did you do after unlocking your phone? Did you upgrade back to A9? If so, then flash recovery_ramdisk A9
Download here
Click to expand...
Click to collapse
I've tried both, they give me the same error.
After I flash the recovery I can't really reboot straight into recovery because of the issue with the battery... somehow I gotta hold the Volume UP key, while catching exact moment when I can unplug USB after the low battery status page passes, and before Huawei logo appears...
After unlocking the phone I flashed TWRP over either recovery or erecovery (idk anymore)... then I probably installed Pixel Experience 13 ROM (https://github.com/ponces/treble_build_pe/releases)
And after that... I tried too many things I can't even remember anymore.
returnedinformation said:
then I probably installed Pixel Experience 13 ROM
Click to expand...
Click to collapse
Under EMUI 8 ??? Which TWRP?