OMG - i bricked my three.co.uk phone. - Lenovo P2 Questions & Answers

I have searched and searched but cannot find anywhere that tells me what these messages mean in fastboot.
Example:
(bootloader) has-slot:bootloader: not found
(bootloader) is-logical:bootloader: not found
Please help.
Thank you.

Did you do something before this happened?

LOL, yes, I completely fecked it up.
I have got the recovery back now, but when I try to flash a stock image,
1. Obviously will not flash the bootloader cos it is now unlocked. So I deleted the bits in the bat file that try to flash the bootloader so that the rest can complete.
2. Now will only get to various Systemchunks and then hangs, having installed previous system chunks ok.
Seems to get to here and then hangs.
Executing ".\Windows\fastboot.exe -s SERIALNUMBER flash system systemchunk10.img"
target max-download-size: 512MB
sending 'system' (262143 KB)...
I though about erasing system, butbut the I now get this message bootloader message.
fastboot erase system
(bootloader) has-slot:system: not found
Erasing 'system' OKAY [ 0.025s]
Finished. Total time: 0.062s
So, I had to go to Qualcomm fix, and I have lineage 16 on it now, but I have lost my IMEI's
Thanks for reading.

myjess said:
LOL, yes, I completely fecked it up.
I have got the recovery back now, but when I try to flash a stock image,
1. Obviously will not flash the bootloader cos it is now unlocked. So I deleted the bits in the bat file that try to flash the bootloader so that the rest can complete.
2. Now will only get to various Systemchunks and then hangs, having installed previous system chunks ok.
Seems to get to here and then hangs.
Executing ".\Windows\fastboot.exe -s SERIALNUMBER flash system systemchunk10.img"
target max-download-size: 512MB
sending 'system' (262143 KB)...
I though about erasing system, butbut the I now get this message bootloader message.
fastboot erase system
(bootloader) has-slot:system: not found
Erasing 'system' OKAY [ 0.025s]
Finished. Total time: 0.062s
So, I had to go to Qualcomm fix, and I have lineage 16 on it now, but I have lost my IMEI's
Thanks for reading.
Click to expand...
Click to collapse
probably u just delete system image file

Is ok, got it all working again.
Thanks.

Related

TWRP - Failed to mount '/firmware' (invalid argument)

I rooted my Moto Z Play but I think I screwed up since I can´t no longer flash anything.
The TWRP is working fine (i guess) but when I try to install a ROM I get the following message:
"Failed to mount '/firmware' (invalid argument)"
I tried everything but can´t get it working properly.
Prior to this error I think I tried a diferent version of PAC-MAN and ended up with this situation.
Any sugestions?
Thanx in advance!
gocks said:
I rooted my Moto Z Play but I think I screwed up since I can´t no longer flash anything.
The TWRP is working fine (i guess) but when I try to install a ROM I get the following message:
"Failed to mount '/firmware' (invalid argument)"
I tried everything but can´t get it working properly.
Prior to this error I think I tried a diferent version of PAC-MAN and ended up with this situation.
Any sugestions?
Thanx in advance!
Click to expand...
Click to collapse
As far as I know no one has built PAC ROM for moto z play. My guess is TWRP just saved you from bricking your phone. Better make sure you're trying to flash a ROM build for MZP.
dandrumheller said:
As far as I know no one has built PAC ROM for moto z play. My guess is TWRP just saved you from bricking your phone. Better make sure you're trying to flash a ROM build for MZP.
Click to expand...
Click to collapse
C´mon guys, give me a break, I´m not a tech savy or something like that, just a regular lawyer.
Since I didn´t break my MZP what do I have to do to get it working again??
gocks said:
C´mon guys, give me a break, I´m not a tech savy or something like that, just a regular lawyer.
Since I didn´t break my MZP what do I have to do to get it working again??
Click to expand...
Click to collapse
Flash the correct ROM, in the updater script it checks your phone version prior to flashing the ROM.
Go to the development threads and find yourself moto z play specific ROM and flash
Sent from my XT1635-02 using XDA-Developers Legacy app
flashallthetime said:
Flash the correct ROM, in the updater script it checks your phone version prior to flashing the ROM.
Go to the development threads and find yourself moto z play specific ROM and flash
Sent from my XT1635-02 using
Click to expand...
Click to collapse
I´ve already tried the specific ROM from 3 diferent sources but the problem persists. I´ve tried the custon one and other ROMs but the same erros keeps showing.
gocks said:
I´ve already tried the specific ROM from 3 diferent sources but the problem persists. I´ve tried the custon one and other ROMs but the same erros keeps showing.
Click to expand...
Click to collapse
Does the phone boot to the stock ROM?
You may want flash the specific firmware for your phone.
Sent from my XT1635-02 using XDA-Developers Legacy app
flashallthetime said:
Does the phone boot to the stock ROM?
You may want flash the specific firmware for your phone.
Sent from my XT1635-02 using XDA-Developers Legacy app
Click to expand...
Click to collapse
It does not boot to the stock ROM.
Just flashed the Nagout that you uploaded on another thread. It install but when I do the swipe after flashing the same error appears and the phone don´t boot. The error always appear after the "Updating partition details...." message.
After the installation I got this message:
Moto Z Play Nougat Installed
script suceeded: result was [Moto z P`lay Nougat Installed]
Updating partition details...
Failed to mount '/firmware' (invalid argument)
....done
Then I wiped the cache/dalvik and this occurs:
Formating Cache using make_ext4gs....
Updating partition details....
Failed to mount '/firmware' (invalid argument)
....done
Wiping Dalvil Cache Directories...
Cleaned: /data/dalvik-cache...
--Dalvik Cache Directories Wipe Complete!
Updating partition details...
Failed to mount '/firmware' (invalid argument)
....done
And when I reboot the system twrp ask to install a su wich I don´t install, the system reboot and after the message warning that my device is unlocked it goes to a dark screen and nothing happens.
AP Fastboot Flash Mode (Secure), is that correct?
Thanks again.
gocks said:
It does not boot to the stock ROM.
Just flashed the Nagout that you uploaded on another thread. It install but when I do the swipe after flashing the same error appears and the phone don´t boot. The error always appear after the "Updating partition details...." message.
After the installation I got this message:
Moto Z Play Nougat Installed
script suceeded: result was [Moto z P`lay Nougat Installed]
Updating partition details...
Failed to mount '/firmware' (invalid argument)
....done
Then I wiped the cache/dalvik and this occurs:
Formating Cache using make_ext4gs....
Updating partition details....
Failed to mount '/firmware' (invalid argument)
....done
Wiping Dalvil Cache Directories...
Cleaned: /data/dalvik-cache...
--Dalvik Cache Directories Wipe Complete!
Updating partition details...
Failed to mount '/firmware' (invalid argument)
....done
And when I reboot the system twrp ask to install a su wich I don´t install, the system reboot and after the message warning that my device is unlocked it goes to a dark screen and nothing happens.
AP Fastboot Flash Mode (Secure), is that correct?
Thanks again.
Click to expand...
Click to collapse
Download your firmware and flash in fastboot. Flash only the 10 sparsechunks,recovery, OEM.img and boot.img and erase user data.
Sent from my XT1635-02 using XDA-Developers Legacy app
flashallthetime said:
Download your firmware and flash in fastboot. Flash only the 10 sparsechunks,recovery, OEM.img and boot.img and erase user data.
Sent from my XT1635-02 using XDA-Developers Legacy app
Click to expand...
Click to collapse
Dont know how to flash oem.img. It´s just fastboot oem unlock? If it is it gave me back invalid boot state.
Are the others commands and the order something like that:
fastboot flash system system.img_sparechunk.0 till 10
fastboot flash recovery recovery.img
IDK what´s the OEM.img command
fastboot flash boot boot.img
fastboot erase userdata
Thank you so much again!
gocks said:
Dont know how to flash oem.img. It´s just fastboot oem unlock? If it is it gave me back invalid boot state.
Are the others commands and the order something like that:
fastboot flash system system.img_sparechunk.0 till 10
fastboot flash recovery recovery.img
IDK what´s the OEM.img command
fastboot flash boot boot.img
fastboot erase userdata
Thank you so much again!
Click to expand...
Click to collapse
This is the commands
Fastboot flash recovery recovery.img
Fastboot flash boot boot.img
Fastboot flash system system.img_sparsechunk.0
Fastboot flash system system.img_sparsechunk.1
Repeat all 10 sparsechunks
fastboot flash oem oem.img
Fastboot erase userdata
Fastboot reboot
Sent from my XT1635-02 using XDA-Developers Legacy app
flashallthetime said:
This is the commands
Fastboot flash recovery recovery.img
Fastboot flash boot boot.img
Fastboot flash system system.img_sparsechunk.0
Fastboot flash system system.img_sparsechunk.1
Repeat all 10 sparsechunks
fastboot flash oem oem.img
Fastboot erase userdata
Fastboot reboot
Sent from my XT1635-02 using XDA-Developers Legacy app
Click to expand...
Click to collapse
Did exactly what you told me and this happened:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash recovery recovery.img
target reported max download size of 536870912 bytes
sending 'recovery' (16484 KB)...
OKAY [ 0.371s]
writing 'recovery'...
(bootloader) Image not signed or corrupt
OKAY [ 0.312s]
finished. total time: 0.683s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash boot boot.img
target reported max download size of 536870912 bytes
sending 'boot' (10820 KB)...
OKAY [ 0.235s]
writing 'boot'...
(bootloader) Image not signed or corrupt
OKAY [ 0.235s]
finished. total time: 0.501s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash system system.img
_sparsechunk.0
target reported max download size of 536870912 bytes
sending 'system' (257307 KB)...
OKAY [ 5.493s]
writing 'system'...
OKAY [ 3.985s]
finished. total time: 9.478s
The othes lines seems to be ok, but the phone continue stucked on the "Your device has been unlock...." and don´t reboot.
Downloaded another custom ROM (ADDISON_RETBR_6.0.1_MPNS24.104-44-7)
Unzipped into Minimal ADB and Fastboot folder
Openned Fastboot
Loaded bootloader and connected USB
>fastboot flash recovery recovery.img
target reported max download size of 536870912 bytes
sending 'recovery' (16484 KB)...
OKAY [ 0.376s]
writing 'recovery'...
(bootloader) Image not signed or corrupt
OKAY [ 0.312s]
finished. total time: 0.704s
>fastboot flash boot boot.img
target reported max download size of 536870912 bytes
sending 'boot' (16384 KB)...
OKAY [ 0.375s]
writing 'boot'...
(bootloader) Image not signed or corrupt
OKAY [ 0.296s]
finished. total time: 0.672s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash system system.img
_sparsechunk.0
target reported max download size of 536870912 bytes
sending 'system' (257311 KB)...
OKAY [ 5.505s]
writing 'system'...
OKAY [ 3.971s]
finished. total time: 9.477s
>fastboot flash oem oem.img
target reported max download size of 536870912 bytes
sending 'oem' (105020 KB)...
OKAY [ 2.245s]
writing 'oem'...
OKAY [ 1.439s]
finished. total time: 3.688s
>fastboot erase userdata
erasing 'userdata'...
OKAY [ 0.151s]
finished. total time: 0.154s
>fastboot reboot
rebooting...
And nothing happens again after the reboot.
When I try to boot to recovery it gives me a "no command" screen with a "no command" message and just it.
Flashed the recovey.img from twrp and it is working ok.
My bootloader:
AP Fastboot Flash Mode (Secure) => in red
BL: C0.14 (sha-9325e5f, 2016-07-11 16:32:03)
Baseband: <not found>
Product/Variant: addison XT1635-02 32GB P7
Serial number: xxxxxxxxx
CPU: xxxxxx
eMNC: xxxxxx
DRAW: xxxxxxxxx
Console: [NULL]: null
Battery: OK
flashing_unlocked
Software status: Modified
Transfer Mode: USB Connected
Trying now ROM XT1635-02_ADDISON_RETBR_MPNS24.104-44-10_cid50_
Any clue? Thanx again.
gocks said:
Downloaded another custom ROM (ADDISON_RETBR_6.0.1_MPNS24.104-44-7)
Unzipped into Minimal ADB and Fastboot folder
Openned Fastboot
Loaded bootloader and connected USB
>fastboot flash recovery recovery.img
target reported max download size of 536870912 bytes
sending 'recovery' (16484 KB)...
OKAY [ 0.376s]
writing 'recovery'...
(bootloader) Image not signed or corrupt
OKAY [ 0.312s]
finished. total time: 0.704s
>fastboot flash boot boot.img
target reported max download size of 536870912 bytes
sending 'boot' (16384 KB)...
OKAY [ 0.375s]
writing 'boot'...
(bootloader) Image not signed or corrupt
OKAY [ 0.296s]
finished. total time: 0.672s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash system system.img
_sparsechunk.0
target reported max download size of 536870912 bytes
sending 'system' (257311 KB)...
OKAY [ 5.505s]
writing 'system'...
OKAY [ 3.971s]
finished. total time: 9.477s
>fastboot flash oem oem.img
target reported max download size of 536870912 bytes
sending 'oem' (105020 KB)...
OKAY [ 2.245s]
writing 'oem'...
OKAY [ 1.439s]
finished. total time: 3.688s
>fastboot erase userdata
erasing 'userdata'...
OKAY [ 0.151s]
finished. total time: 0.154s
>fastboot reboot
rebooting...
And nothing happens again after the reboot.
When I try to boot to recovery it gives me a "no command" screen with a "no command" message and just it.
Flashed the recovey.img from twrp and it is working ok.
My bootloader:
AP Fastboot Flash Mode (Secure) => in red
BL: C0.14 (sha-9325e5f, 2016-07-11 16:32:03)
Baseband: <not found>
Product/Variant: addison XT1635-02 32GB P7
Serial number: xxxxxxxxx
CPU: xxxxxx
eMNC: xxxxxx
DRAW: xxxxxxxxx
Console: [NULL]: null
Battery: OK
flashing_unlocked
Software status: Modified
Transfer Mode: USB Connected
Trying now ROM XT1635-02_ADDISON_RETBR_MPNS24.104-44-10_cid50_
Any clue? Thanx again.
Click to expand...
Click to collapse
You flashed all the sparsechunks from 0 to 10?
The stock recovery has a dead Andy robot, so that flashed.
Did you flash the boot.img?
Sent from my XT1635-02 using XDA-Developers Legacy app
flashallthetime said:
You flashed all the sparsechunks from 0 to 10?
The stock recovery has a dead Andy robot, so that flashed.
Did you flash the boot.img?
Sent from my XT1635-02 using XDA-Developers Legacy app
Click to expand...
Click to collapse
Yep, exactly the way you told me to do.
ADDISON_RETBR_6.0.1_MPNS24.104-44-7 has a corrupted file, but it didn´t work with the ADDISON_RETBR_MPNS24.104-44-10_cid50_ too.
Will try another one. And thanx again.
gocks said:
Yep, exactly the way you told me to do.
ADDISON_RETBR_6.0.1_MPNS24.104-44-7 has a corrupted file, but it didn´t work with the ADDISON_RETBR_MPNS24.104-44-10_cid50_ too.
Will try another one. And thanx again.
Click to expand...
Click to collapse
Obviously the pacman rom screwed up your partition, normally every rom will check if you're flashing a rom to a specific device.
I don't think flashing any other firmware will help cause it's all the same from one carrier to another.
I think you may need to flash the entire firmware package but it MUST BE YOUR SPECIFIC FIRMWARE PACKAGE otherwise you'll really be bricked.
I'm pulling at straws
flashallthetime said:
Obviously the pacman rom screwed up your partition, normally every rom will check if you're flashing a rom to a specific device.
I don't think flashing any other firmware will help cause it's all the same from one carrier to another.
I think you may need to flash the entire firmware package but it MUST BE YOUR SPECIFIC FIRMWARE PACKAGE otherwise you'll really be bricked.
I'm pulling at straws
Click to expand...
Click to collapse
Don´t say the word brick, please!!!
What I have to do to know what is my specific firmware?
gocks said:
Don´t say the word brick, please!!!
What I have to do to know what is my specific firmware?
Click to expand...
Click to collapse
Which carrier are you with?
And don't sue me if things get worse
flashallthetime said:
Which carrier are you with?
And don't sue me if things get worse
Click to expand...
Click to collapse
Vivo, its a brazilian one.
Relax, if my phone bricks I wont sue you because my wife will kill me first!
I flashed TWRP recovery.img and found that I have diferent kinds of partitions, is it corret?
/data is f2fs
/cach /system /persist ext4
/efs1 emmc
/external_sd and usb-otg vfat
gocks said:
I flashed TWRP recovery.img and found that I have diferent kinds of partitions, is it corret?
/data is f2fs
/cach /system /persist ext4
/efs1 emmc
/external_sd and usb-otg vfat
Click to expand...
Click to collapse
Yes and it seems like you can't right to the system and or data partitions. There's more partitions but they're locked or hidden
Try to format your data in TWRP
and wipe system

Phone may be done for please help

so I downloaded a rom the new xperience rom for moto z play and I used it and liked it but wanted to use a different rom well their recovery replaced my twrp so I went to settings and factory reset and now I cant get out of fastboot mode everytime I try it says "start up failed your device didn't start up successfully use the storage repair assistant on computer to repair your device" I think it completely wiped everything my whole sysem I cant even get into twrp so I'm trying to flash twrp and use the back up I have saved on my computer but I get this
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash recovery twrp.img
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:recovery: not found
target reported max download size of 536870912 bytes
sending 'recovery' (23420 KB)...
OKAY [ 0.506s]
writing 'recovery'...
(bootloader) Image size exeeded partition limits
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.530s
PLEASE HELP!!!!!!!!!!!
Addison xt1635-02
This is gonna sound stupid. But after you fastboot TWRP, did you try starting ur phone into bootloader, and going to recovery? I thought TWRP wouldn't install at first but it was there all along when I used the English version.

Stuck on TWRP after accidental factory reset

I was about to manually install the lineageOS update, but I accidentally swiped factory restore. Is there anyway I can get the update file online? I tried starting from the top by wiping everything and reinstalling the rom but it only boots me into TWRP. I also tried restoring backup files but is also boots me into TWRP. I am stuck.
PS: I tried the "fastboot continue" method but it boots me into TWRP.
reboot to fastboot mode. flash stock bootloader and recovery. reboot in stock recovery and then factory reset device and sideload firmware. alternatively you can flash raw firmware manually
sukhwant717 said:
reboot to fastboot mode. flash stock bootloader and recovery. reboot in stock recovery and then factory reset device and sideload firmware. alternatively you can flash raw firmware manually
Click to expand...
Click to collapse
Thank you for your response, Sir. I really appreciate it. Where do I get the stock bootloader and recovery, and how do I flash them? On the alternative method, do you mean I should install the stock rom? I'm sorry. I'm really not good at this; I'm just good at following tutorials. Is this what you're suggesting me to do? (XDA is now allowing me to write outside links. But here is the title of the tutorial from Asus Zentalk)
"[Experience Sharing] How to Relock Bootloader on ZenFone 2(ZE551ML ONLY)"
I have made a backup before I intalled the Lineage OS custom Rom. Can I use that instead of downloading new files, because the internet here is really bad. My problem is how I am going to install it. I tried restoring it but I keep on coming back to the TWRP.
Edit: I am now downloading the stock boot.img and recovery.img. I will be flashing them with ADB the ADB tool. Is this what you want to tell me? Then I will reboot in stock recovery, select factory reset and sideload firmware. I honestly don't get the "sideload firmware" part but can I use the one that I have backed up? How?
lemuelermita said:
Thank you for your response, Sir. I really appreciate it. Where do I get the stock bootloader and recovery, and how do I flash them? On the alternative method, do you mean I should install the stock rom? I'm sorry. I'm really not good at this; I'm just good at following tutorials. Is this what you're suggesting me to do? (XDA is now allowing me to write outside links. But here is the title of the tutorial from Asus Zentalk)
"[Experience Sharing] How to Relock Bootloader on ZenFone 2(ZE551ML ONLY)"
I have made a backup before I intalled the Lineage OS custom Rom. Can I use that instead of downloading new files, because the internet here is really bad. My problem is how I am going to install it. I tried restoring it but I keep on coming back to the TWRP.
Edit: I am now downloading the stock boot.img and recovery.img. I will be flashing them with ADB the ADB tool. Is this what you want to tell me? Then I will reboot in stock recovery, select factory reset and sideload firmware. I honestly don't get the "sideload firmware" part but can I use the one that I have backed up? How?
Click to expand...
Click to collapse
the backup you made you can flash only via twrp. if you have backup simply install it in twrp. but if still bootloops then you have to download firmware either from asus website or raw firmware from any other source. first try to flash backup in twrp. if you are unable to get into system them report back here. i will send you link to download raw firmware and instructions how to flash
sukhwant717 said:
the backup you made you can flash only via twrp. if you have backup simply install it in twrp. but if still bootloops then you have to download firmware either from asus website or raw firmware from any other source. first try to flash backup in twrp. if you are unable to get into system them report back here. i will send you link to download raw firmware and instructions how to flash
Click to expand...
Click to collapse
I tried to flash the backup but still no luck. Yes, please. Thank you very much!
I'm currently downloading the "CleanSTOCK-MM.223-v3.8[STABLE][Z00A]-6 May". I hope this will fix the problem. Do you think this will work 100%? I am afraid that it will boot again to TWRP after installing another rom. Which do you think is more efficient, installing a new rom or installing raw firmware?
lemuelermita said:
I tried to flash the backup but still no luck. Yes, please. Thank you very much!
I'm currently downloading the "CleanSTOCK-MM.223-v3.8[STABLE][Z00A]-6 May". I hope this will fix the problem. Do you think this will work 100%? I am afraid that it will boot again to TWRP after installing another rom. Which do you think is more efficient, installing a new rom or installing raw firmware?
Click to expand...
Click to collapse
raw is definitely best option. are you able to mount data and cache partition in TWRP
sukhwant717 said:
raw is definitely best option. are you able to mount data and cache partition in TWRP
Click to expand...
Click to collapse
I haven't tried that yet. How do I do that? Can you send me the links and instructions needed?
sukhwant717 said:
raw is definitely best option. are you able to mount data and cache partition in TWRP
Click to expand...
Click to collapse
Defensively smartest guy about phones in the world!!! ahaha <3
lemuelermita said:
I haven't tried that yet. How do I do that? Can you send me the links and instructions needed?
Click to expand...
Click to collapse
go to the following guide. see the section flash firmware without AFT and follow the instructions. keep in mind run each and every command even if any of them fails.
https://forum.xda-developers.com/zenfone2/help/thead-bricked-phone-updating-to-mm-tips-t3452785
sukhwant717 said:
go to the following guide. see the section flash firmware without AFT and follow the instructions. keep in mind run each and every command even if any of them fails.
https://forum.xda-developers.com/zenfone2/help/thead-bricked-phone-updating-to-mm-tips-t3452785
Click to expand...
Click to collapse
Thank you very much, Sir! I will give you an update soon.
lemuelermita said:
Thank you very much, Sir! I will give you an update soon.
Click to expand...
Click to collapse
Followed the instructions on the link but my phone boots up on a blinking screen with an android saying "Error". The command prompt failed at steps 4,5, and 11.
C:\Users\Lemuel\Documents\RESTOCK>fastboot devices
F5AZFG14A156 fastboot
C:\Users\Lemuel\Documents\RESTOCK>fastboot oem erase_osip_header
...
OKAY [ 0.217s]
finished. total time: 0.219s
C:\Users\Lemuel\Documents\RESTOCK>fastboot oem start_partitioning
...
(bootloader) Start partitioning
OKAY [ 0.228s]
finished. total time: 0.231s
C:\Users\Lemuel\Documents\RESTOCK>fastboot flash /tmp/partition.tbl partition.tbl
target reported max download size of 536870912 bytes
sending '/tmp/partition.tbl' (2 KB)...
OKAY [ 0.194s]
writing '/tmp/partition.tbl'...
FAILED (remote: not allowed to flash this partition)
finished. total time: 0.384s
C:\Users\Lemuel\Documents\RESTOCK>fastboot flash /tmp/partition.tbl partition.tbl
target reported max download size of 536870912 bytes
sending '/tmp/partition.tbl' (2 KB)...
OKAY [ 0.205s]
writing '/tmp/partition.tbl'...
FAILED (remote: not allowed to flash this partition)
finished. total time: 0.394s
C:\Users\Lemuel\Documents\RESTOCK>fastboot oem partition /tmp/partition.tbl
...
FAILED (remote: unknown OEM command)
finished. total time: 0.127s
C:\Users\Lemuel\Documents\RESTOCK>fastboot erase system
******** Did you mean to fastboot format this ext4 partition?
erasing 'system'...
OKAY [ 0.560s]
finished. total time: 0.561s
C:\Users\Lemuel\Documents\RESTOCK>fastboot erase cache
******** Did you mean to fastboot format this ext4 partition?
erasing 'cache'...
OKAY [ 0.232s]
finished. total time: 0.234s
C:\Users\Lemuel\Documents\RESTOCK>fastboot erase data
******** Did you mean to fastboot format this ext4 partition?
erasing 'data'...
OKAY [ 1.447s]
finished. total time: 1.448s
C:\Users\Lemuel\Documents\RESTOCK>fastboot erase APD
******** Did you mean to fastboot format this ext4 partition?
erasing 'APD'...
OKAY [ 0.290s]
finished. total time: 0.294s
C:\Users\Lemuel\Documents\RESTOCK>fastboot erase ADF
******** Did you mean to fastboot format this ext4 partition?
erasing 'ADF'...
OKAY [ 0.232s]
finished. total time: 0.234s
C:\Users\Lemuel\Documents\RESTOCK>fastboot oem wipe splashscreen
...
FAILED (remote: unknown OEM command)
finished. total time: 0.127s
C:\Users\Lemuel\Documents\RESTOCK>fastboot oem stop_partitioning
...
(bootloader) Stop partitioning
OKAY [ 0.210s]
finished. total time: 0.212s
C:\Users\Lemuel\Documents\RESTOCK>fastboot flash splashscreen splash_sign.bin
target reported max download size of 536870912 bytes
sending 'splashscreen' (270 KB)...
OKAY [ 0.192s]
writing 'splashscreen'...
OKAY [ 0.236s]
finished. total time: 0.431s
C:\Users\Lemuel\Documents\RESTOCK>fastboot flash token MFG_BOM_Full.bin
target reported max download size of 536870912 bytes
sending 'token' (3 KB)...
OKAY [ 0.194s]
writing 'token'...
OKAY [ 0.370s]
finished. total time: 0.566s
C:\Users\Lemuel\Documents\RESTOCK>fastboot flash ifwi ifwi-prod.bin
target reported max download size of 536870912 bytes
sending 'ifwi' (4096 KB)...
OKAY [ 0.294s]
writing 'ifwi'...
OKAY [ 1.027s]
finished. total time: 1.326s
C:\Users\Lemuel\Documents\RESTOCK>fastboot flash boot boot_sign.bin
target reported max download size of 536870912 bytes
sending 'boot' (11870 KB)...
OKAY [ 0.531s]
writing 'boot'...
OKAY [ 0.648s]
finished. total time: 1.182s
C:\Users\Lemuel\Documents\RESTOCK>fastboot flash recovery recovery_sign.bin
target reported max download size of 536870912 bytes
sending 'recovery' (11882 KB)...
OKAY [ 0.520s]
writing 'recovery'...
OKAY [ 0.636s]
finished. total time: 1.163s
C:\Users\Lemuel\Documents\RESTOCK>fastboot flash fastboot droidboot_sign.bin
target reported max download size of 536870912 bytes
sending 'fastboot' (14824 KB)...
OKAY [ 0.558s]
writing 'fastboot'...
OKAY [ 0.739s]
finished. total time: 1.302s
C:\Users\Lemuel\Documents\RESTOCK>fastboot flash APD APD.img
target reported max download size of 536870912 bytes
erasing 'APD'...
OKAY [ 0.204s]
sending 'APD' (183963 KB)...
OKAY [ 4.927s]
writing 'APD'...
OKAY [ 0.912s]
finished. total time: 6.049s
C:\Users\Lemuel\Documents\RESTOCK>fastboot flash system system.img
target reported max download size of 536870912 bytes
erasing 'system'...
OKAY [ 0.233s]
sending sparse 'system' 1/5 (518551 KB)...
OKAY [ 27.274s]
writing 'system' 1/5...
OKAY [ 5.563s]
sending sparse 'system' 2/5 (523662 KB)...
OKAY [ 22.886s]
writing 'system' 2/5...
OKAY [ 6.964s]
sending sparse 'system' 3/5 (520607 KB)...
OKAY [ 24.630s]
writing 'system' 3/5...
OKAY [ 8.077s]
sending sparse 'system' 4/5 (500735 KB)...
OKAY [ 23.704s]
writing 'system' 4/5...
OKAY [ 7.983s]
sending sparse 'system' 5/5 (188368 KB)...
OKAY [ 8.849s]
writing 'system' 5/5...
OKAY [ 1.187s]
finished. total time: 137.827s
C:\Users\Lemuel\Documents\RESTOCK>
C:\Users\Lemuel\Documents\RESTOCK>
C:\Users\Lemuel\Documents\RESTOCK>fastboot reboot
rebooting...
finished. total time: 0.126s
lemuelermita said:
Thank you very much, Sir! I will give you an update soon.
Click to expand...
Click to collapse
The command prompt failed at steps 4,5, and 11. It only boots in a blinking screen with an android saying, "Error". Tried it again for the second time but still boots in same screen. I tried to manually boot up the phone without the commands and worked. Thank you very much!
lemuelermita said:
The command prompt failed at steps 4,5, and 11. It only boots in a blinking screen with an android saying, "Error". Tried it again for the second time but still boots in same screen. I tried to manually boot up the phone without the commands and worked. Thank you very much!
Click to expand...
Click to collapse
hmm good to know device working again. strongly recommend you to perform a factory reset even device working perfectly.

Can't flash TWRP - remote failure (SOLVED)

Hi guys!
I hope you can help me, since I've looked everywhere but can only find people with similar but not the exact same problem.
I tried flashing TWRP in order to migrate to a custom ROM. I am currently running official 7.1.1.
When I try to flash twrp (tried several versions) the command window shows me this:
c:\adb>fastboot flash recovery twrp.img
target max-sparse-size: 256MB
sending 'recovery' (14522 KB)...
OKAY [ 0.049s]
writing 'recovery'...
(bootloader) Image recovery failed validation
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.068s
I tried using Moto fastboot as well but with the same result. I'd really appreciate your help. Please note, that I am not a pro like most you guys so I might have follow-up questions
Are you sure you flashed the right image? And that your bootloader is unlocked?
And what happens if you use
Code:
fastboot boot twrp.img
?
Artim_96 said:
Are you sure you flashed the right image? And that your bootloader is unlocked?
And what happens if you use
Code:
fastboot boot twrp.img
?
Click to expand...
Click to collapse
Yes, I am sure that I am using the right image. I tried several, always checked that they were for addison.
I also unlocked the bootloader in developer options - although now that you mention it: in the fastboot screen it still says oem_locked. So maybe that is the problem?
c:\adb>fastboot boot twrp.img
downloading 'boot.img'...
OKAY [ 0.047s]
booting...
(bootloader) permission denied!
FAILED (remote failure)
finished. total time: 0.054s
Okay, I managed to unlock the bootloader with the unlock key I got from Motorola.
Now when I try to flash it says:
c:\adb>fastboot flash recovery twrp.img
target max-sparse-size: 256MB
sending 'recovery' (14522 KB)...
OKAY [ 0.049s]
writing 'recovery'...
(bootloader) Image not signed or corrupt
OKAY [ 0.280s]
finished. total time: 0.330s
Come ooooon
ischariot_pasadelski said:
Are you sure you flashed the right image? And that your bootloader is unlocked?
And what happens if you use
Yes, I am sure that I am using the right image. I tried several, always checked that they were for addison.
I also unlocked the bootloader in developer options - although now that you mention it: in the fastboot screen it still says oem_locked. So maybe that is the problem?
c:\adb>fastboot boot twrp.img
downloading 'boot.img'...
OKAY [ 0.047s]
booting...
(bootloader) permission denied!
FAILED (remote failure)
finished. total time: 0.054s
Click to expand...
Click to collapse
Oh Jesus... Bootloader unlock is not just the option in Dev settings. Google it, you'll find a website from Motorola that guides you through the process and provides you with everything necessary
Yes, I did that by now as I said in the post before. Sorry, but I'm a beginner
Now it says that the image is not signed or corrupt. IDK what to do anymore.
Booting in TWRP works but when flashing Lineage from SD card I get the error:
recv error on unevent
and
failed to mount data.
I wiped everything using TWRP and I also tried to use another version of TWRP, so a corrupted file can't be the problem.
I figured it out.
I had to restore the file system by only checking the "System" box when wiping with TPWR - just in case anybody else has the same problems.
So a factory data reset solve the problem? Having your first issue with moto e5 cricket and you can't unlock three bootloader
Artim_96 said:
Oh Jesus... Bootloader unlock is not just the option in Dev settings. Google it, you'll find a website from Motorola that guides you through the process and provides you with everything necessary
Click to expand...
Click to collapse
well, i had it unlocked via the settingsbutton and after read this here , via the website where you can get the 20 bits code, but it is the same result with a code that is the same as the adb devices code, just as before! Only thing that is changed is a warning when you starts the phone up.
ischariot_pasadelski said:
Yes, I did that by now as I said in the post before. Sorry, but I'm a beginner
Now it says that the image is not signed or corrupt. IDK what to do anymore.
Booting in TWRP works but when flashing Lineage from SD card I get the error:
recv error on unevent
and
failed to mount data.
I wiped everything using TWRP and I also tried to use another version of TWRP, so a corrupted file can't be the problem.
Click to expand...
Click to collapse
Can you tell me how you got the phone twrped, pls?

XT1670 revert to stock issue

SOLVED I will make a topic about it https://forum.xda-developers.com/g5/help/how-to-revert-moto-g5-xt1670-to-stock-t4183425
Hello, how are you all over there? I here in trouble with this XT1670. I have installed several roms but now i want to go back to the official one, but it dont lock the bootloader.
Tried the following command (twice) to lock the bootloader: fastboot oem lock
And i get the following result:
Code:
(bootloader) Flash valid Android images now
(bootloader) Then re-run this command to lock
OKAY [ 0.016s]
finished. total time: 0.016s
Now i use the following command: fastboot flash boot boot.img
And the following was obtained:
Code:
target reported max download size of 535822336 bytes
sending 'boot' (16384 KB) ...
OKAY [0.545s]
writing 'boot' ...
(bootloader) Security version downgrade
(bootloader) Image boot failed validation
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.747s
I have already tried several. Boot, gpt, oem with official rom. All showing the error "Security version downgrade"
I also tried Lenovo's Rescue & Smart app, but it says the SKU is wrong and doesn't recognize the mobile phone.
I don't know how to continue. I could put an official rom, but when you restart the phone the bootloader appears. It only starts when press start.
Not only does that happen. Every so often, the phone turns itself off and remains in the bootloader. And then when you start up, bug reports pop up to share with who knows what.
I do not know what to do. You are the experts.
Ty in advance

Categories

Resources