Related
Hello folks,
On a fine day when I was disabling the airport mode, I realised the phone is hung as both the home screens - Aviate and Google were not responding. So I forced switched off the phone by holding down the power key for 15-20 seconds. The phone booted in fast boot mode and since then its not starting up.
Note - I never enabled USB debugging (developer mode) in this phone, so ADB will not work and I did not select "Allow OEM Unlock" - obviously I was not hoping this kind of unprovoked crash/bricking.
I am on Mac OS X with USB drivers installed for the device. I have access to a Windows Machine also, in case any of the suggested solutions work with windows tools.
Here is what I have tried so far after reading various threads in xdaDevelopers. Please note I have tried mfastboot on windows as well and have the same output -
(1.) Tried unlocking the phone as mentioned in the Motorola website and elsewhere in the forum. I get an error
Code:
$ ./fastboot oem get_unlock_data
...
(bootloader) Failed to get unlock data, please try again!
FAILED (remote failure)
finished. total time: 0.105s
The phone is unlockable with a cid of 0x007
Code:
$ fastboot getvar all
......
(bootloader) cid: 0x0007
......
(2.) Downloaded the MotoE stock firmware from here and followed the "How to flash Stock Firmware". All the commands are failing, below is the output.
Code:
$ fastboot devices -l
TA38500WHO fastboot usb:1D110000
$ fastboot oem fb_mode_set
...
FAILED (remote failure)
finished. total time: 0.023s
$ fastboot flash partition gpt.bin
target reported max download size of 268435456 bytes
sending 'partition' (32 KB)...
OKAY [ 0.098s]
writing 'partition'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.548s
$ fastboot flash bootloader bootloader.imgtarget reported max download size of 268435456 bytes
sending 'bootloader' (2410 KB)...
OKAY [ 0.155s]
writing 'bootloader'...
(bootloader) flashing sbl1 ...
(bootloader) Failed to erase partition
(bootloader) Failed to flash sbl1
FAILED (remote failure)
finished. total time: 1.391s
$ fastboot flash logo logo.bin
target reported max download size of 268435456 bytes
sending 'logo' (679 KB)...
OKAY [ 0.137s]
writing 'logo'...
(bootloader) Failed to erase partition
(bootloader) Failed to flash partition logo
FAILED (remote failure)
finished. total time: 0.245s
$ fastboot flash logo logo.bin
target reported max download size of 268435456 bytes
sending 'logo' (679 KB)...
OKAY [ 0.175s]
writing 'logo'...
(bootloader) Failed to erase partition
(bootloader) Failed to flash partition logo
FAILED (remote failure)
finished. total time: 0.282s
$ fastboot flash recovery recovery.img
target reported max download size of 268435456 bytes
sending 'recovery' (32752 KB)...
OKAY [ 1.108s]
writing 'recovery'...
(bootloader) Failed to erase partition
(bootloader) Failed to flash partition recovery
FAILED (remote failure)
finished. total time: 1.803s
$ fastboot flash recovery recovery.img
target reported max download size of 268435456 bytes
sending 'recovery' (32752 KB)...
OKAY [ 1.251s]
writing 'recovery'...
(bootloader) Failed to erase partition
(bootloader) Failed to flash partition recovery
FAILED (remote failure)
finished. total time: 1.947s
$ fastboot flash system system.img_sparsechunk.0
target reported max download size of 268435456 bytes
sending 'system' (262143 KB)...
OKAY [ 8.315s]
writing 'system'...
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 8.847s
$ fastboot flash system system.img_sparsechunk.1
target reported max download size of 268435456 bytes
sending 'system' (262141 KB)...
OKAY [ 8.331s]
writing 'system'...
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 8.427s
$ fastboot flash system system.img_sparsechunk.2
target reported max download size of 268435456 bytes
sending 'system' (262141 KB)...
OKAY [ 8.335s]
writing 'system'...
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 8.453s
$ fastboot flash system system.img_sparsechunk.3
target reported max download size of 268435456 bytes
sending 'system' (256116 KB)...
OKAY [ 8.120s]
writing 'system'...
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 8.229s
$ fastboot flash system system.img_sparsechunk.4
target reported max download size of 268435456 bytes
sending 'system' (240640 KB)...
OKAY [ 7.653s]
writing 'system'...
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 7.764s
$ fastboot flash system system.img_sparsechunk.5
target reported max download size of 268435456 bytes
sending 'system' (124212 KB)...
OKAY [ 3.977s]
writing 'system'...
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 4.064s
$ fastboot flash modem NON-HLOS.bin
target reported max download size of 268435456 bytes
sending 'modem' (54616 KB)...
OKAY [ 1.789s]
writing 'modem'...
(bootloader) Failed to erase partition
FAILED (remote failure)
finished. total time: 1.908s
$ fastboot flash modem NON-HLOS.bin
target reported max download size of 268435456 bytes
sending 'modem' (54616 KB)...
OKAY [ 1.846s]
writing 'modem'...
(bootloader) Failed to erase partition
FAILED (remote failure)
finished. total time: 1.925s
$ fastboot erase modemst1
erasing 'modemst1'...
(bootloader) Failed to erase partition
FAILED (remote failure)
finished. total time: 0.126s
$ fastboot erase modemst2
erasing 'modemst2'...
(bootloader) Failed to erase partition
FAILED (remote failure)
finished. total time: 0.173s
$ fastboot flash fsg fsg.mbn
target reported max download size of 268435456 bytes
sending 'fsg' (1518 KB)...
OKAY [ 0.143s]
writing 'fsg'...
(bootloader) Failed to erase partition
(bootloader) Failed to flash partition fsg
FAILED (remote failure)
finished. total time: 0.247s
$ fastboot flash fsg fsg.mbn
target reported max download size of 268435456 bytes
sending 'fsg' (1518 KB)...
OKAY [ 0.189s]
writing 'fsg'...
(bootloader) Failed to erase partition
(bootloader) Failed to flash partition fsg
FAILED (remote failure)
finished. total time: 0.293s
$ fastboot erase cache
erasing 'cache'...
(bootloader) Failed to erase partition
FAILED (remote failure)
finished. total time: 0.167s
$ fastboot erase userdata
erasing 'userdata'...
(bootloader) Failed to erase partition
FAILED (remote failure)
finished. total time: 0.146s
$ fastboot erase customize
erasing 'customize'...
(bootloader) Invalid partition name customize
FAILED (remote failure)
finished. total time: 0.049s
$ fastboot oem fb_mode_clear
...
FAILED (remote failure)
finished. total time: 0.023s
Any help in recovering the phone will be appreciated.
If you can get in to recovery from bootloader maybe try factory reset
When I select factory reset or recovery I got thrown to the fast boot prompt back. I checked the Bootloader logs in the fastboot mode which says - "failed to validate boot image. Boot up failed"
The same problem on 1528 after flashing stock rom!!? somebody can help us??
the firmware xt1528 have 6 files system.img_sparsechunk, and in the instruction -5, thats why phone cant start.....may be 1521 ? Look in unzipped folder with firmware how much files youve got?
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-!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
Romik80 said:
the firmware xt1528 have 6 files system.img_sparsechunk, and in the instruction -5, thats why phone cant start.....may be 1521 ? Look in unzipped folder with firmware how much files youve got?
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-!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
Click to expand...
Click to collapse
It has 6 with me. There are errors / failures at every stage of flashing. That's what I am not able to understand.
ajitabhpandey said:
It has 6 with me. There are errors / failures at every stage of flashing. That's what I am not able to understand.
Click to expand...
Click to collapse
does it being flashed successfully?
sounds like it isn't therefor not booting up
according to the "log" you're not unlocked, therefore it fails
Tools to unbrick the device!
ajitabhpandey said:
Any help in recovering the phone will be appreciated.
Click to expand...
Click to collapse
Do take a look at this link:http://forum.xda-developers.com/general/rooting-roms/motorola-usb-drivers-rsd-lite-firmware-t3042687
I have the same problem even though my bootloader is unlocked. My phone decided to reboot one fine day and subsequently have been stuck at the bootloader. All the commands are accompanied in the log by "failed to validate abc image" where abc=boot,system,recovery etc.
Since my moto e is unlocked, I can't even RMA to Motorola for warranty :/
what were you running ?
what were you flashing ?
bootloader was locked when the problem occurred ?
Hey,
In the fastboot mode navigate to factory mode and then keep pressing the power button fast about 20-30 times till it boots into the os. Now u can access developer options and unlock the boot loader. Once the boot loader is unlocked u can flash the same rom again.......
I installed unofficial cm13 on my xt1521 everything good as of now .. i dont like the boot animation really worse.... so if any solution ?? pls do.... btw how to flash that i tried via twrp but no changes ...
kumaranwade said:
I installed unofficial cm13 on my xt1521 everything good as of now .. i dont like the boot animation really worse.... so if any solution ?? pls do.... btw how to flash that i tried via twrp but no changes ...
Click to expand...
Click to collapse
Install a theme with an alternate boot animation.
Sent from my SAMSUNG-SM-G920A using Tapatalk
pls anyone help me
my moto e 2015 does not boot up its failed and show this message in fastboot mode "failed to validated boot imagae BOOT UP FAILED"
Gautamgzb2 said:
pls anyone help me
my moto e 2015 does not boot up its failed and show this message in fastboot mode "failed to validated boot imagae BOOT UP FAILED"
Click to expand...
Click to collapse
There is already multiple threads for this matter pls dont create new ones.
I posted a solution just now here: http://forum.xda-developers.com/moto-e-2015/help/helpppppppppppppppppppppp-moto-e-2nd-t3378460
Check it out.
ayush rao said:
There is already multiple threads for this matter pls dont create new ones.
I posted a solution just now here: http://forum.xda-developers.com/moto-e-2015/help/helpppppppppppppppppppppp-moto-e-2nd-t3378460
Check it out.
Click to expand...
Click to collapse
sorry bro.......
but i have 3g model not 4g
and your old thread is for 4g model
Gautamgzb2 said:
sorry bro.......
but i have 3g model not 4g
and your old thread is for 4g model
Click to expand...
Click to collapse
It doesn't matter only the ROM file is different but the steps to restore is completely the same.
ayush rao said:
It doesn't matter only the ROM file is different but the steps to restore is completely the same.
Click to expand...
Click to collapse
but bro..
i have no flash file for this model can you help me
my phone details here..
ap fastboot flashmode(s)
51.01 sha 7518d9b 2015-01-20 12.26.36
product/variant otus xt1506 8gb p3
cpu msm8212 cs
emmc 8gb micron rv-06 pv=12 ty=17
dram 1024mb elpida s4 sdram die=4gb
device is locked
Gautamgzb2 said:
but bro..
i have no flash file for this model can you help me
my phone details here..
ap fastboot flashmode(s)
51.01 sha 7518d9b 2015-01-20 12.26.36
product/variant otus xt1506 8gb p3
cpu msm8212 cs
emmc 8gb micron rv-06 pv=12 ty=17
dram 1024mb elpida s4 sdram die=4gb
device is locked
Click to expand...
Click to collapse
flash your mobile fully with the latest official os available for ur device !! becoz I bought my mobile in the same condition from a seller in Olx ! I flashed 5.0.2 but by device stuck again in bootloader menu so I flashed 5.1.1 on my device and it booted up becoz that was the latest firmware which was available for my surnia(4g model) at that time ! and don't flash older versions ! It won't help ! Make sure you flash exact firmware for your phone and all sparsechunk files then only your device will boot up for sure !!
If it doesn't boot up keep bootloader options in factory mode and press power button for 10 - 25 times !!! I think this will help !!!
---------- Post added at 01:47 PM ---------- Previous post was at 01:02 PM ----------
try this
http://www.filefactory.com/file/kss..._LPC23.13-56_cid7_subsidy-DEFAULT_CFC.xml.zip
kesavvel said:
flash your mobile fully with the latest official os available for ur device !! becoz I bought my mobile in the same condition from a seller in Olx ! I flashed 5.0.2 but by device stuck again in bootloader menu so I flashed 5.1.1 on my device and it booted up becoz that was the latest firmware which was available for my surnia(4g model) at that time ! and don't flash older versions ! It won't help ! Make sure you flash exact firmware for your phone and all sparsechunk files then only your device will boot up for sure !!
If it doesn't boot up keep bootloader options in factory mode and press power button for 10 - 25 times !!! I think this will help !!!
---------- Post added at 01:47 PM ---------- Previous post was at 01:02 PM ----------
try this
http://www.filefactory.com/file/kss..._LPC23.13-56_cid7_subsidy-DEFAULT_CFC.xml.zip
Click to expand...
Click to collapse
thanks bro...
i will to flash
Gautamgzb2 said:
thanks bro...
i will to flash
Click to expand...
Click to collapse
You are welcome ! Happy Flashing ![emoji4]
Sent from my XT1521 using Tapatalk
Gautamgzb2 said:
thanks bro...
i will to flash
Click to expand...
Click to collapse
bro..
this link is not woring plz update this or give me a new link
Gautamgzb2 said:
bro..
this link is not woring plz update this or give me a new link
Click to expand...
Click to collapse
here is a screenshot
Gautamgzb2 said:
here is a screenshot
Click to expand...
Click to collapse
no yesterday it worked you better copy the file name exactly from the link and search it in google ! becoz i searched in all file factory storages and moto firmware center , this is the only link I can find!! mega storage links are not opening !!
Gautamgzb2 said:
bro..
this link is not woring plz update this or give me a new link
Click to expand...
Click to collapse
no the link is working
Gautamgzb2 said:
bro..
this link is not woring plz update this or give me a new link
Click to expand...
Click to collapse
its working
try this link ! but it is not opening for me check if it works for you !!! Its a MEGA link folder
https://mega.nz/#F!mlAC0QCa!V4sIvngRZqnLZhtFERPhSQ
kesavvel said:
try this link ! but it is not opening for me check if it works for you !!! Its a MEGA link folder
https://mega.nz/#F!mlAC0QCa!V4sIvngRZqnLZhtFERPhSQ
Click to expand...
Click to collapse
when i flash the mobile i have a problem below are error
C:\Program Files\Minimal ADB and Fastboot>"C:\Program Files\Minimal ADB and Fast
boot\new.bat"
C:\Program Files\Minimal ADB and Fastboot>fastboot.exe flash partition gpt.bin
(bootloader) has-slotartition: not found
target reported max download size of 299892736 bytes
sending 'partition' (32 KB)...
OKAY [ 0.030s]
writing 'partition'...
(bootloader) This may take a few seconds, if a
(bootloader) different partition table is being
(bootloader) flashed since we need to backup
(bootloader) and restore a few partitions
(bootloader) Flashing primary GPT image...
(bootloader) Failed to write primary GPT.
(bootloader) Failed to program partition table
FAILED (remote failure)
finished. total time: 5.500s
C:\Program Files\Minimal ADB and Fastboot>fastboot.exe flash motoboot motoboot.i
mg
(bootloader) has-slot:motoboot: not found
target reported max download size of 299892736 bytes
sending 'motoboot' (1663 KB)...
OKAY [ 0.110s]
writing 'motoboot'...
(bootloader) flashing tz ...
(bootloader) Failed to erase partition
(bootloader) Failed to flash tz
FAILED (remote failure)
finished. total time: 6.440s
C:\Program Files\Minimal ADB and Fastboot>fastboot.exe flash logo logo.bin
(bootloader) has-slot:logo: not found
target reported max download size of 299892736 bytes
sending 'logo' (527 KB)...
OKAY [ 0.100s]
writing 'logo'...
(bootloader) Failed to erase partition
(bootloader) Failed to flash partition logo
FAILED (remote failure)
finished. total time: 5.140s
C:\Program Files\Minimal ADB and Fastboot>fastboot.exe flash boot boot.img
(bootloader) has-slot:boot: not found
target reported max download size of 299892736 bytes
sending 'boot' (10200 KB)...
OKAY [ 0.420s]
writing 'boot'...
(bootloader) Failed to erase partition
(bootloader) Failed to flash partition boot
FAILED (remote failure)
finished. total time: 5.990s
C:\Program Files\Minimal ADB and Fastboot>fastboot.exe flash recovery recovery.i
mg
(bootloader) has-slot:recovery: not found
target reported max download size of 299892736 bytes
sending 'recovery' (10280 KB)...
OKAY [ 0.420s]
writing 'recovery'...
(bootloader) Failed to erase partition
(bootloader) Failed to flash partition recovery
FAILED (remote failure)
finished. total time: 5.999s
C:\Program Files\Minimal ADB and Fastboot>fastboot.exe flash system system.img_s
parsechunk.0
(bootloader) has-slot:system: not found
target reported max download size of 299892736 bytes
sending 'system' (262142 KB)...
OKAY [ 9.310s]
writing 'system'...
(bootloader) Failed to erase partition
FAILED (remote failure)
finished. total time: 33.551s
C:\Program Files\Minimal ADB and Fastboot>fastboot.exe flash system system.img_s
parsechunk.1
(bootloader) has-slot:system: not found
target reported max download size of 299892736 bytes
sending 'system' (233386 KB)...
OKAY [ 7.996s]
writing 'system'...
(bootloader) Failed to flash sparse image
FAILED (remote failure)
finished. total time: 16.140s
C:\Program Files\Minimal ADB and Fastboot>fastboot.exe flash system system.img_s
parsechunk.2
(bootloader) has-slot:system: not found
target reported max download size of 299892736 bytes
sending 'system' (261362 KB)...
OKAY [ 8.561s]
writing 'system'...
(bootloader) Failed to flash sparse image
FAILED (remote failure)
finished. total time: 17.036s
C:\Program Files\Minimal ADB and Fastboot>fastboot.exe flash system system.img_s
parsechunk.3
(bootloader) has-slot:system: not found
target reported max download size of 299892736 bytes
sending 'system' (262096 KB)...
OKAY [ 8.697s]
writing 'system'...
(bootloader) Failed to flash sparse image
FAILED (remote failure)
finished. total time: 17.240s
C:\Program Files\Minimal ADB and Fastboot>fastboot.exe flash system system.img_s
parsechunk.4
(bootloader) has-slot:system: not found
target reported max download size of 299892736 bytes
sending 'system' (261765 KB)...
OKAY [ 8.482s]
writing 'system'...
(bootloader) Failed to flash sparse image
FAILED (remote failure)
finished. total time: 17.055s
C:\Program Files\Minimal ADB and Fastboot>fastboot.exe flash system system.img_s
parsechunk.5
(bootloader) has-slot:system: not found
target reported max download size of 299892736 bytes
sending 'system' (251801 KB)...
OKAY [ 8.587s]
writing 'system'...
(bootloader) Failed to flash sparse image
FAILED (remote failure)
finished. total time: 16.931s
C:\Program Files\Minimal ADB and Fastboot>fastboot.exe flash modem NON-HLOS.bin
(bootloader) has-slot:modem: not found
target reported max download size of 299892736 bytes
sending 'modem' (46240 KB)...
OKAY [ 1.616s]
writing 'modem'...
(bootloader) Failed to erase partition
(bootloader) Failed to flash partition modem
FAILED (remote failure)
finished. total time: 6.651s
C:\Program Files\Minimal ADB and Fastboot>fastboot.exe flash fsg fsg.mbn
(bootloader) has-slot:fsg: not found
target reported max download size of 299892736 bytes
sending 'fsg' (650 KB)...
OKAY [ 0.070s]
writing 'fsg'...
(bootloader) Failed to erase partition
(bootloader) Failed to flash partition fsg
FAILED (remote failure)
finished. total time: 5.123s
C:\Program Files\Minimal ADB and Fastboot>fastboot.exe erase cache
(bootloader) has-slot:cache: not found
erasing 'cache'...
(bootloader) Failed to erase partition
FAILED (remote failure)
finished. total time: 5.075s
C:\Program Files\Minimal ADB and Fastboot>fastboot.exe erase userdata
(bootloader) has-slot:userdata: not found
erasing 'userdata'...
(bootloader) Failed to erase partition
FAILED (remote failure)
finished. total time: 5.077s
C:\Program Files\Minimal ADB and Fastboot>fastboot.exe reboot
rebooting...
finished. total time: 0.040s
C:\Program Files\Minimal ADB and Fastboot>pause
Press any key to continue . . .
Terminate batch job (Y/N)?
C:\Program Files\Minimal ADB and Fastboot>
are they the exact commands !! for your model and is your model number correct which you mentioned !???
kesavvel said:
are they the exact commands !! for your model and is your model number correct which you mentioned !???
Click to expand...
Click to collapse
yes bro command is ryt and my model no. is also ryt
Gautamgzb2 said:
yes bro command is ryt and my model no. is also ryt
Click to expand...
Click to collapse
THEN IT SHUD WORK !!! I dono why it didn't !!! I will try to sort it out for you ! did you check the general and trouble shooting treads for this !! I saw in a thread this firmware will work for this model , that's why I gave you the link and ppl had replied yes it works I dono why it didn't work for you !!!
kesavvel said:
THEN IT SHUD WORK !!! I dono why it didn't !!! I will try to sort it out for you ! did you check the general and trouble shooting treads for this !! I saw in a thread this firmware will work for this model , that's why I gave you the link and ppl had replied yes it works I dono why it didn't work for you !!!
Click to expand...
Click to collapse
i think my mobile have a hardware problem ......
are yo know about hardware????????
No but I don't think so ! The service centers may have the correct firmware give to them they will flash it for you
Sent from my XT1521 using Tapatalk
Stuck in "Your device has been unlocked and can't be trusted. […] ID: bad key"
I wanted to root the device but I now I have a device that doesn't boot anymore.
What I've done so far wasn't this much:
unlocked bootloader (fastboot oem get_unlock_data and fastboot oem unlock)
flashed TWRP (fastboot flash recovery twrp-3.0.2-0-griffin.img)
I bootet into the system, downloaded Magisk because I was going to root the device. I bootet into Recovery / TWRP and saw that I wasn't able to find the download folder where I downloaded Magisk. I rebootet and since then I can't boot into the system again.
Fastboot and recovery are possible tough. When I'm trying to boot regulary the device is stuck in:
Code:
Your device has been unlocked and can't be trusted.
To learn more, visit:
motorola.com/unlockbootloader
ID: bad key
Your device will boot in 5 seconds.
It looks pretty much like this except the ID ('N/A' in the image but 'bad key' on my mobile).
But it never boots. Before TWRP the screen appears as well but at least it is booting into TWRP.
Clearing cache didn't help neither.
Any idea what could help?
PS: I changed the clock in TWRP to 24h format but I guess this should brake anything — right?
PPS: I also tried to flash some official image (XT1650-03_GRIFFIN_RETEU-EMEA_6.0.1_MPL24.246-17_cid50_subsidy-DEFAULT_regulatory-03_CFC_EMEA) I found here somewhere but it failed with an error message that it won't downgrade security and therefore not flash. Perhaps because I upgraded to Android 7 when I got the mobile?
PPPS: I found a thread on another board with the same problem but no solution
hackepeterbroetchen said:
I wanted to root the device but I now I have a device that doesn't boot anymore.
What I've done so far wasn't this much:
unlocked bootloader (fastboot oem get_unlock_data and fastboot oem unlock)
flashed TWRP (fastboot flash recovery twrp-3.0.2-0-griffin.img)
I bootet into the system, downloaded Magisk because I was going to root the device. I bootet into Recovery / TWRP and saw that I wasn't able to find the download folder where I downloaded Magisk. I rebootet and since then I can't boot into the system again.
Fastboot and recovery are possible tough. When I'm trying to boot regulary the device is stuck in:
Code:
Your device has been unlocked and can't be trusted.
To learn more, visit:
motorola.com/unlockbootloader
ID: bad key
Your device will boot in 5 seconds.
It looks pretty much like this except the ID ('N/A' in the image but 'bad key' on my mobile).
But it never boots. Before TWRP the screen appears as well but at least it is booting into TWRP.
Clearing cache didn't help neither.
Any idea what could help?
PS: I changed the clock in TWRP to 24h format but I guess this should brake anything — right?
PPS: I also tried to flash some official image (XT1650-03_GRIFFIN_RETEU-EMEA_6.0.1_MPL24.246-17_cid50_subsidy-DEFAULT_regulatory-03_CFC_EMEA) I found here somewhere but it failed with an error message that it won't downgrade security and therefore not flash. Perhaps because I upgraded to Android 7 when I got the mobile?
PPPS: I found a thread on another board with the same problem but no solution
Click to expand...
Click to collapse
Had the same issue and figured it out:
https://forum.xda-developers.com/showpost.php?p=72005245&postcount=185
doree said:
Had the same issue and figured it out:
https://forum.xda-developers.com/showpost.php?p=72005245&postcount=185
Click to expand...
Click to collapse
But I didn't flash another rom yet at all. I just flashed TWRP recovery image so far. Are you sure that you had the same issue?
hackepeterbroetchen said:
But I didn't flash another rom yet at all. I just flashed TWRP recovery image so far. Are you sure that you had the same issue?
Click to expand...
Click to collapse
I wouldn't reply if I wasn't.
You should have rebooted the device after unlocking the device, because it gets wiped after the process. Since you flashed TWRP right after unlocking it, you left the device wiped, therefore there's no system to gain access to. That's the reason you're stuck.
Hm Im stuck at the same screen. My question is just, how can I flash the Rom if the phones not booting and I dont get the Zip on the phone? Recovery and Bootloader works, but no system start. And unfortunately your link only shows 404: https://firmware.center/firmware/Motorola/Moto Z/Stock/XT1650-03/
Thanks for you help!
(Found this link tho: https://mirrors.lolinet.com/firmware/moto/addison/official/RETBR/)
Ah, I think I understand. So now I should flash the stock image again and redo the things (but with rebooting between the steps) - is that correct?
In that case I just need a flashable image. As I wrote in the PS of the first post I tried to flash the original stock rom but I didn't work.
And I can't find an image for (the PHP script complaints about wrong parameters):
• Model: XT1650
• Software-Version: Blur_Version.25.221.12.griffin.re
• Carrier: reteu
doree said:
Had the same issue and figured it out:
https://forum.xda-developers.com/showpost.php?p=72005245&postcount=185
Click to expand...
Click to collapse
doree said:
I wouldn't reply if I wasn't.
You should have rebooted the device after unlocking the device, because it gets wiped after the process. Since you flashed TWRP right after unlocking it, you left the device wiped, therefore there's no system to gain access to. That's the reason you're stuck.
Click to expand...
Click to collapse
And if I want to sideload it says Invaild zip file Format in recovery and
Code:
C:\adb>adb sideload xt1635.zip
loading: 'xt1635.zip'
error: device '(null)' not found
C:\adb>adb sideload xt1635.zip
Total xfer: 0.00x
in cmd. :S
nighteeeeeY said:
Hm Im stuck at the same screen. My question is just, how can I flash the Rom if the phones not booting and I dont get the Zip on the phone? Recovery and Bootloader works, but no system start. And unfortunately your link only shows 404: https://firmware.center/firmware/Motorola/Moto Z/Stock/XT1650-03/
Thanks for you help!
(Found this link tho: https://mirrors.lolinet.com/firmware/moto/addison/official/RETBR/)
Click to expand...
Click to collapse
It shows 404 because the Site ran out of Traffic. The Info is on the frontpage. Do NOT flash the stuff you posted, because it's for a different model.
hackepeterbroetchen said:
Ah, I think I understand. So now I should flash the stock image again and redo the things (but with rebooting between the steps) - is that correct?
In that case I just need a flashable image. As I wrote in the PS of the first post I tried to flash the original stock rom but I didn't work.
And I can't find an image for (the PHP script complaints about wrong parameters):
• Model: XT1650
• Software-Version: Blur_Version.25.221.12.griffin.re
• Carrier: reteu
Click to expand...
Click to collapse
Yep, you can't flash the Image, because you already updated your Bootloader to 7.0 Nougat. Therefore a flash attempt of the Image you mentioned will fail. It only works with a 6.0 Bootloader, since it's an 6.0 Stock Image.
nighteeeeeY said:
And if I want to sideload it says Invaild zip file Format in recovery and
Code:
C:\adb>adb sideload xt1635.zip
loading: 'xt1635.zip'
error: device '(null)' not found
C:\adb>adb sideload xt1635.zip
Total xfer: 0.00x
in cmd. :S
Click to expand...
Click to collapse
You need to Install ADB, boot into the Bootloader, unpack the Image I mentioned and execute the fastboot command I mentioned in the othet Post.
// Wait a sec. I will repack the stock image and will add the needed Stuff for you all.
hackepeterbroetchen said:
Ah, I think I understand. So now I should flash the stock image again and redo the things (but with rebooting between the steps) - is that correct?
In that case I just need a flashable image. As I wrote in the PS of the first post I tried to flash the original stock rom but I didn't work.
And I can't find an image for (the PHP script complaints about wrong parameters):
• Model: XT1650
• Software-Version: Blur_Version.25.221.12.griffin.re
• Carrier: reteu
Click to expand...
Click to collapse
You didn't account for the line break... It should read something like "Blur_Version.25.221.12.griffin.retail.en.US". However, you have to submit the version that currently runs on your phone - and the server will give you the next update! For the version you provided, there is no update.
You may want to try this:
backup everything you can via TWRP...
boot into bootloader (fastboot)
restore 6.0.1 image [a] via fastboot, see batch file below (the nougat bootloader doesn't let you boot it, but fastboot hopefully doesn't prevent flashing it..)
The nougat bootloader prevents downgrading itself and will cause that fastboot line to fail. Leave it in anyway. If the script breaks or anything, remove the line from the script and retry.
Code:
echo off
fastboot getvar max-sparse-size
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
fastboot erase modemst1
fastboot erase modemst2
fastboot flash bluetooth BTFM.bin
fastboot flash dsp adspso.bin
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot flash system system.img_sparsechunk.8
fastboot flash system system.img_sparsechunk.9
fastboot flash system system.img_sparsechunk.10
fastboot flash system system.img_sparsechunk.11
fastboot flash system system.img_sparsechunk.12
fastboot flash system system.img_sparsechunk.13
fastboot flash system system.img_sparsechunk.14
fastboot flash system system.img_sparsechunk.15
fastboot flash system system.img_sparsechunk.16
fastboot flash oem oem.img
REM fastboot erase carrier
fastboot oem fb_mode_clear
directly boot into (stock) recovery, do not try to boot the system
press and hold down power, then press volume-up, release volume-up, then power.
select 'Apply update from ADB'
sideload nougat update from PC console: "fastboot sideload Blur_Version.25.11.14.griffin.retail.en.US.zip"
[*] Wipe data/factory reset, Wipe cache partition, Power off
[*] reboot
Please report back how it all worked out for you...
[a] XT1650-03_GRIFFIN_RETEU-EMEA_6.0.1_MPL24.246-17_cid50_subsidy-DEFAULT_regulatory-03_CFC_EMEA.xml.zip
OTA: Blur_Version.(24.21.46 --> 25.11.14).griffin.retail.en.US
Okay guys, do the following:
1) Download the Stock Image here and extract the archive to a folder of your choice: https://mirrors.lolinet.com/firmwar...ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
2) Download the Fastboot and Batch-File archive from here and extract it into the Stock Image folder: https://www.sendspace.com/file/1rm4cj
3) Shutdown your phone and then push the VOL- and Power-Button at the same time. You should now enter the Bootloader.
4) Connect your phone to the computer (USB)
5) Open up the command prompt and go the folder where you extracted the Stock Image and Fastboot files to
6) Type _FLASH.bat and ignore all error messages you will possibly see
7) Wait till the phone boots up with the Motorola Splashscreen
That's how I revived my device.
doree said:
2) Download the Fastboot and Batch-File archive from here and extract it into the Stock Image folder: https://mega.nz/fm/hqplTQJS
Click to expand...
Click to collapse
It says "No Data". Do I do something wrong? Just created an account.
I have created this batch from your previous post on the other thread:
Code:
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
fastboot erase modemst1
fastboot erase modemst2
fastboot flash bluetooth BTFM.bin
fastboot flash dsp adspso.bin
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot flash system system.img_sparsechunk.8
fastboot flash system system.img_sparsechunk.9
fastboot flash system system.img_sparsechunk.10
fastboot flash system system.img_sparsechunk.11
fastboot flash system system.img_sparsechunk.12
fastboot flash system system.img_sparsechunk.13
fastboot flash oem oem.img
fastboot erase cache
fastboot erase userdata
fastboot erase customize
fastboot erase clogo
fastboot erase ddr
fastboot reboot
Is this correct? Or the one @benzinerwin just posted?
Code:
echo off
fastboot getvar max-sparse-size
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
fastboot erase modemst1
fastboot erase modemst2
fastboot flash bluetooth BTFM.bin
fastboot flash dsp adspso.bin
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot flash system system.img_sparsechunk.8
fastboot flash system system.img_sparsechunk.9
fastboot flash system system.img_sparsechunk.10
fastboot flash system system.img_sparsechunk.11
fastboot flash system system.img_sparsechunk.12
fastboot flash system system.img_sparsechunk.13
fastboot flash system system.img_sparsechunk.14
fastboot flash system system.img_sparsechunk.15
fastboot flash system system.img_sparsechunk.16
fastboot flash oem oem.img
REM fastboot erase carrier
fastboot oem fb_mode_clear
nighteeeeeY said:
It says "No Data". Do I do something wrong? Just created an account.
I have created this batch from your previous post on the other thread:
Code:
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
fastboot erase modemst1
fastboot erase modemst2
fastboot flash bluetooth BTFM.bin
fastboot flash dsp adspso.bin
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot flash system system.img_sparsechunk.8
fastboot flash system system.img_sparsechunk.9
fastboot flash system system.img_sparsechunk.10
fastboot flash system system.img_sparsechunk.11
fastboot flash system system.img_sparsechunk.12
fastboot flash system system.img_sparsechunk.13
fastboot flash oem oem.img
fastboot erase cache
fastboot erase userdata
fastboot erase customize
fastboot erase clogo
fastboot erase ddr
fastboot reboot
Is this correct? Or the one @benzinerwin just posted?
Code:
echo off
fastboot getvar max-sparse-size
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
fastboot erase modemst1
fastboot erase modemst2
fastboot flash bluetooth BTFM.bin
fastboot flash dsp adspso.bin
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot flash system system.img_sparsechunk.8
fastboot flash system system.img_sparsechunk.9
fastboot flash system system.img_sparsechunk.10
fastboot flash system system.img_sparsechunk.11
fastboot flash system system.img_sparsechunk.12
fastboot flash system system.img_sparsechunk.13
fastboot flash system system.img_sparsechunk.14
fastboot flash system system.img_sparsechunk.15
fastboot flash system system.img_sparsechunk.16
fastboot flash oem oem.img
REM fastboot erase carrier
fastboot oem fb_mode_clear
Click to expand...
Click to collapse
Use this link instead: https://www.sendspace.com/file/1rm4cj
My method is a different approach than benzinerwin's. Use the method you feel comfortable with.
Phew! Thanks. Worked out perfectly.
benzinerwin said:
You didn't account for the line break... It should read something like "Blur_Version.25.221.12.griffin.retail.en.US".
Click to expand...
Click to collapse
I really didn't see that
benzinerwin said:
You may want to try this:
backup everything you can via TWRP...
boot into bootloader (fastboot)
restore 6.0.1 image [a] via fastboot, see batch file below (the nougat bootloader doesn't let you boot it, but fastboot hopefully doesn't prevent flashing it..)
Click to expand...
Click to collapse
I'm getting errors with it (@benzinerwin method)
Code:
(bootloader) Validating 'gpt.default.xml'
(bootloader) Security version downgrade
(bootloader) Image primary_gpt failed validation
(bootloader) Preflash validation failed
(bootloader) Security version downgrade
(bootloader) Image primary_gpt failed validation
(bootloader) Preflash validation failed
(bootloader) Security version downgrade
(bootloader) Image primary_gpt failed validation
(bootloader) Preflash validation failed
(bootloader) Security version downgrade
(bootloader) Image primary_gpt failed validation
(bootloader) Preflash validation failed
(bootloader) Cancelling 'gpt.default.xml'
FAILED (remote failure)
finished. total time: 0.142s
target reported max download size of 536870912 bytes
sending 'bootloader' (7076 KB)...
OKAY [ 0.030s]
writing 'bootloader'...
(bootloader) Validating 'bootloader.default.xml'
(bootloader) Security version downgrade
(bootloader) Image hyp failed validation
(bootloader) Preflash validation failed
(bootloader) Image tz failed validation
(bootloader) Preflash validation failed
(bootloader) Image devcfg failed validation
(bootloader) Preflash validation failed
(bootloader) Cancelling 'bootloader.default.xml'
FAILED (remote failure)
finished. total time: 0.202s
doree said:
Okay guys, do the following:
3) Shutdown your phone and then push the VOL+ and Power-Button at the same time. You should now enter the Bootloader.
Click to expand...
Click to collapse
VOL+ or VOL-? Somehow I entered a boot loop with VOL+…
hackepeterbroetchen said:
I really didn't see that
I'm getting errors with it (@benzinerwin method)
Click to expand...
Click to collapse
When rolling back the bootloader is not allowed, then also writing an older GPT will be prevented. Sorry, I missed that.
However, writing a retail image for a different country seems to work - the phone keepts its 'reteu' setting (I just tried it for a different reason).
That makes things a lot easier: just flash the RETxx nougat image as @doree discribed and you should be fine!
VOL+ or VOL-? Somehow I entered a boot loop with VOL+…
Click to expand...
Click to collapse
Maybe that worked in the old days With current bootloader versions only VOL- & power works. But that only gets you into the fastboot mode, from which you can launch recovery...
hackepeterbroetchen said:
I really didn't see that
I'm getting errors with it (@benzinerwin method)
Code:
(bootloader) Validating 'gpt.default.xml'
(bootloader) Security version downgrade
(bootloader) Image primary_gpt failed validation
(bootloader) Preflash validation failed
(bootloader) Security version downgrade
(bootloader) Image primary_gpt failed validation
(bootloader) Preflash validation failed
(bootloader) Security version downgrade
(bootloader) Image primary_gpt failed validation
(bootloader) Preflash validation failed
(bootloader) Security version downgrade
(bootloader) Image primary_gpt failed validation
(bootloader) Preflash validation failed
(bootloader) Cancelling 'gpt.default.xml'
FAILED (remote failure)
finished. total time: 0.142s
target reported max download size of 536870912 bytes
sending 'bootloader' (7076 KB)...
OKAY [ 0.030s]
writing 'bootloader'...
(bootloader) Validating 'bootloader.default.xml'
(bootloader) Security version downgrade
(bootloader) Image hyp failed validation
(bootloader) Preflash validation failed
(bootloader) Image tz failed validation
(bootloader) Preflash validation failed
(bootloader) Image devcfg failed validation
(bootloader) Preflash validation failed
(bootloader) Cancelling 'bootloader.default.xml'
FAILED (remote failure)
finished. total time: 0.202s
VOL+ or VOL-? Somehow I entered a boot loop with VOL+…
Click to expand...
Click to collapse
Sorry, I meant VOL-. Typed it in a hurry!
So I tried XT1635-02_ADDISON_RETBR_MPNS24.104-44-10_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC now and it fails on different files:
Code:
target reported max download size of 536870912 bytes
sending 'partition' (45 KB)...
OKAY [ 0.035s]
writing 'partition'...
(bootloader) no suitable package!
FAILED (remote failure)
finished. total time: 0.052s
target reported max download size of 536870912 bytes
sending 'bootloader' (5115 KB)...
OKAY [ 0.048s]
writing 'bootloader'...
(bootloader) no suitable package!
FAILED (remote failure)
finished. total time: 0.061s
target reported max download size of 536870912 bytes
sending 'modem' (73570 KB)...
OKAY [ 0.269s]
writing 'modem'...
OKAY [ 1.035s]
finished. total time: 1.304s
target reported max download size of 536870912 bytes
sending 'fsg' (1976 KB)...
OKAY [ 0.051s]
writing 'fsg'...
OKAY [ 0.369s]
finished. total time: 0.420s
erasing 'modemst1'...
OKAY [ 0.193s]
finished. total time: 0.193s
erasing 'modemst2'...
OKAY [ 0.188s]
finished. total time: 0.188s
error: cannot load 'BTFM.bin'
target reported max download size of 536870912 bytes
sending 'dsp' (16384 KB)...
OKAY [ 0.075s]
writing 'dsp'...
OKAY [ 0.467s]
finished. total time: 0.542s
target reported max download size of 536870912 bytes
sending 'logo' (2533 KB)...
OKAY [ 0.054s]
writing 'logo'...
OKAY [ 0.377s]
finished. total time: 0.432s
target reported max download size of 536870912 bytes
sending 'boot' (16384 KB)...
OKAY [ 0.094s]
writing 'boot'...
(bootloader) Image not signed or corrupt
OKAY [ 0.467s]
finished. total time: 0.561s
target reported max download size of 536870912 bytes
sending 'recovery' (16484 KB)...
OKAY [ 0.083s]
writing 'recovery'...
(bootloader) Image not signed or corrupt
OKAY [ 0.468s]
finished. total time: 0.552s
target reported max download size of 536870912 bytes
sending 'system' (257311 KB)...
OKAY [ 0.966s]
writing 'system'...
OKAY [ 2.764s]
finished. total time: 3.730s
target reported max download size of 536870912 bytes
sending 'system' (261378 KB)...
OKAY [ 1.035s]
writing 'system'...
OKAY [ 1.873s]
finished. total time: 2.908s
target reported max download size of 536870912 bytes
sending 'system' (251415 KB)...
OKAY [ 0.986s]
writing 'system'...
OKAY [ 1.867s]
finished. total time: 2.853s
target reported max download size of 536870912 bytes
sending 'system' (255815 KB)...
OKAY [ 0.959s]
writing 'system'...
OKAY [ 1.936s]
finished. total time: 2.895s
target reported max download size of 536870912 bytes
sending 'system' (255582 KB)...
OKAY [ 0.935s]
writing 'system'...
OKAY [ 1.938s]
finished. total time: 2.873s
target reported max download size of 536870912 bytes
sending 'system' (257857 KB)...
OKAY [ 0.966s]
writing 'system'...
OKAY [ 1.775s]
finished. total time: 2.741s
target reported max download size of 536870912 bytes
sending 'system' (260164 KB)...
OKAY [ 1.016s]
writing 'system'...
OKAY [ 1.750s]
finished. total time: 2.766s
target reported max download size of 536870912 bytes
sending 'system' (253309 KB)...
OKAY [ 0.992s]
writing 'system'...
OKAY [ 1.919s]
finished. total time: 2.911s
target reported max download size of 536870912 bytes
sending 'system' (256398 KB)...
OKAY [ 1.061s]
writing 'system'...
OKAY [ 1.805s]
finished. total time: 2.866s
target reported max download size of 536870912 bytes
sending 'system' (262140 KB)...
OKAY [ 1.066s]
writing 'system'...
OKAY [ 1.779s]
finished. total time: 2.845s
target reported max download size of 536870912 bytes
sending 'system' (147418 KB)...
OKAY [ 0.628s]
writing 'system'...
OKAY [ 1.079s]
finished. total time: 1.706s
error: cannot load 'system.img_sparsechunk.11'
error: cannot load 'system.img_sparsechunk.12'
error: cannot load 'system.img_sparsechunk.13'
target reported max download size of 536870912 bytes
sending 'oem' (105020 KB)...
OKAY [ 0.454s]
writing 'oem'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.477s
erasing 'cache'...
OKAY [ 0.379s]
finished. total time: 0.379s
erasing 'userdata'...
OKAY [ 1.957s]
finished. total time: 1.957s
erasing 'customize'...
OKAY [ 0.365s]
finished. total time: 0.365s
erasing 'clogo'...
(bootloader) Permission denied
FAILED (remote failure)
finished. total time: 0.029s
erasing 'ddr'...
OKAY [ 0.312s]
finished. total time: 0.312s
rebooting...
finished. total time: 0.903s
These were the commands I ran (these are the ones @doree linked)
Code:
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
fastboot erase modemst1
fastboot erase modemst2
fastboot flash bluetooth BTFM.bin
fastboot flash dsp adspso.bin
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot flash system system.img_sparsechunk.8
fastboot flash system system.img_sparsechunk.9
fastboot flash system system.img_sparsechunk.10
fastboot flash system system.img_sparsechunk.11
fastboot flash system system.img_sparsechunk.12
fastboot flash system system.img_sparsechunk.13
fastboot flash oem oem.img
fastboot erase cache
fastboot erase userdata
fastboot erase customize
fastboot erase clogo
fastboot erase ddr
fastboot reboot
Is it because the image is XT1635-02 instead XT1650-03?
EDIT:
I did flash it this way now anyway (I probably shouldn't have done this, sorry) but reboot failed now and moves directly to fastboot with the following error message:
Code:
Start Up Failed:
Your device didn't start up successfully.
Use the Software Repair Assistant on computer to repair your device.
Connect your device to your computer to get the Software Repair Assistant.
EDIT 2:
I tried ADDISON_NPNS25.137-24-1-4_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC with Android 7 now with the same effect. I guess I am missing something here?
PS: I absolutely appreciate your help and it's impressive how fast you answer. Thank you very much for this.
hackepeterbroetchen said:
So I tried XT1635-02_ADDISON_RETBR_MPNS24.104-44-10_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC now and it fails on different files:
Code:
target reported max download size of 536870912 bytes
sending 'partition' (45 KB)...
OKAY [ 0.035s]
writing 'partition'...
(bootloader) no suitable package!
FAILED (remote failure)
finished. total time: 0.052s
target reported max download size of 536870912 bytes
sending 'bootloader' (5115 KB)...
OKAY [ 0.048s]
writing 'bootloader'...
(bootloader) no suitable package!
FAILED (remote failure)
finished. total time: 0.061s
target reported max download size of 536870912 bytes
sending 'modem' (73570 KB)...
OKAY [ 0.269s]
writing 'modem'...
OKAY [ 1.035s]
finished. total time: 1.304s
target reported max download size of 536870912 bytes
sending 'fsg' (1976 KB)...
OKAY [ 0.051s]
writing 'fsg'...
OKAY [ 0.369s]
finished. total time: 0.420s
erasing 'modemst1'...
OKAY [ 0.193s]
finished. total time: 0.193s
erasing 'modemst2'...
OKAY [ 0.188s]
finished. total time: 0.188s
error: cannot load 'BTFM.bin'
target reported max download size of 536870912 bytes
sending 'dsp' (16384 KB)...
OKAY [ 0.075s]
writing 'dsp'...
OKAY [ 0.467s]
finished. total time: 0.542s
target reported max download size of 536870912 bytes
sending 'logo' (2533 KB)...
OKAY [ 0.054s]
writing 'logo'...
OKAY [ 0.377s]
finished. total time: 0.432s
target reported max download size of 536870912 bytes
sending 'boot' (16384 KB)...
OKAY [ 0.094s]
writing 'boot'...
(bootloader) Image not signed or corrupt
OKAY [ 0.467s]
finished. total time: 0.561s
target reported max download size of 536870912 bytes
sending 'recovery' (16484 KB)...
OKAY [ 0.083s]
writing 'recovery'...
(bootloader) Image not signed or corrupt
OKAY [ 0.468s]
finished. total time: 0.552s
target reported max download size of 536870912 bytes
sending 'system' (257311 KB)...
OKAY [ 0.966s]
writing 'system'...
OKAY [ 2.764s]
finished. total time: 3.730s
target reported max download size of 536870912 bytes
sending 'system' (261378 KB)...
OKAY [ 1.035s]
writing 'system'...
OKAY [ 1.873s]
finished. total time: 2.908s
target reported max download size of 536870912 bytes
sending 'system' (251415 KB)...
OKAY [ 0.986s]
writing 'system'...
OKAY [ 1.867s]
finished. total time: 2.853s
target reported max download size of 536870912 bytes
sending 'system' (255815 KB)...
OKAY [ 0.959s]
writing 'system'...
OKAY [ 1.936s]
finished. total time: 2.895s
target reported max download size of 536870912 bytes
sending 'system' (255582 KB)...
OKAY [ 0.935s]
writing 'system'...
OKAY [ 1.938s]
finished. total time: 2.873s
target reported max download size of 536870912 bytes
sending 'system' (257857 KB)...
OKAY [ 0.966s]
writing 'system'...
OKAY [ 1.775s]
finished. total time: 2.741s
target reported max download size of 536870912 bytes
sending 'system' (260164 KB)...
OKAY [ 1.016s]
writing 'system'...
OKAY [ 1.750s]
finished. total time: 2.766s
target reported max download size of 536870912 bytes
sending 'system' (253309 KB)...
OKAY [ 0.992s]
writing 'system'...
OKAY [ 1.919s]
finished. total time: 2.911s
target reported max download size of 536870912 bytes
sending 'system' (256398 KB)...
OKAY [ 1.061s]
writing 'system'...
OKAY [ 1.805s]
finished. total time: 2.866s
target reported max download size of 536870912 bytes
sending 'system' (262140 KB)...
OKAY [ 1.066s]
writing 'system'...
OKAY [ 1.779s]
finished. total time: 2.845s
target reported max download size of 536870912 bytes
sending 'system' (147418 KB)...
OKAY [ 0.628s]
writing 'system'...
OKAY [ 1.079s]
finished. total time: 1.706s
error: cannot load 'system.img_sparsechunk.11'
error: cannot load 'system.img_sparsechunk.12'
error: cannot load 'system.img_sparsechunk.13'
target reported max download size of 536870912 bytes
sending 'oem' (105020 KB)...
OKAY [ 0.454s]
writing 'oem'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.477s
erasing 'cache'...
OKAY [ 0.379s]
finished. total time: 0.379s
erasing 'userdata'...
OKAY [ 1.957s]
finished. total time: 1.957s
erasing 'customize'...
OKAY [ 0.365s]
finished. total time: 0.365s
erasing 'clogo'...
(bootloader) Permission denied
FAILED (remote failure)
finished. total time: 0.029s
erasing 'ddr'...
OKAY [ 0.312s]
finished. total time: 0.312s
rebooting...
finished. total time: 0.903s
These were the commands I ran (these are the ones @doree linked)
Code:
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
fastboot erase modemst1
fastboot erase modemst2
fastboot flash bluetooth BTFM.bin
fastboot flash dsp adspso.bin
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot flash system system.img_sparsechunk.8
fastboot flash system system.img_sparsechunk.9
fastboot flash system system.img_sparsechunk.10
fastboot flash system system.img_sparsechunk.11
fastboot flash system system.img_sparsechunk.12
fastboot flash system system.img_sparsechunk.13
fastboot flash oem oem.img
fastboot erase cache
fastboot erase userdata
fastboot erase customize
fastboot erase clogo
fastboot erase ddr
fastboot reboot
Is it because the image is XT1635-02 instead XT1650-03?
EDIT:
I did flash it this way now anyway (I probably shouldn't have done this, sorry) but reboot failed now and moves directly to fastboot with the following error message:
Code:
Start Up Failed:
Your device didn't start up successfully.
Use the Software Repair Assistant on computer to repair your device.
Connect your device to your computer to get the Software Repair Assistant.
EDIT 2:
I tried ADDISON_NPNS25.137-24-1-4_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC with Android 7 now with the same effect. I guess I am missing something here?
PS: I absolutely appreciate your help and it's impressive how fast you answer. Thank you very much for this.
Click to expand...
Click to collapse
Where are you getting this links from? My post cleary leads to:
https://mirrors.lolinet.com/firmwar...ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
You are trying to flash an Image for a whole different Device (Moto Z Play).
Moto Z Play = XT-1635 Addison
Moto Z = XT-1650 Griffin
doree said:
Where are you getting this links from? My post cleary leads to:
https://mirrors.lolinet.com/firmwar...ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
You are trying to flash an Image for a whole different Device (Moto Z Play).
Moto Z Play = XT-1635 Addison
Moto Z = XT-1650 Griffin
Click to expand...
Click to collapse
Oh boy! I guess this happened because I skipped coffee today
@doree the mobile is booting again. I guess I owe you a beer. Thank you so much!
I guess it isn't possible to go back to the EU rom again for now?
However, now TWRP and root!
Can you recommend any root system for using it with the stock rom?
hackepeterbroetchen said:
Oh boy! I guess this happened because I skipped coffee today
@doree the mobile is booting again. I guess owe you a beer. Thank you so much!
Click to expand...
Click to collapse
Glad I could help
I guess it isn't possible to go back to the EU rom again for now?
Click to expand...
Click to collapse
RETBR is pretty much the same as the "regular" RETEU Rom, since it uses the same Softwarechannel (Settings/About/Softwarechannel). You'll get the same Updates as everyone else in Germany/Europe.
However, now TWRP and root!
Can you recommend any root system for using it with the stock rom?
Click to expand...
Click to collapse
What do you exactly mean with "root system"?
hey there...
I own a moto z2 force running the latest version it supports - Android 9 Pie.
I have unlocked the bootloader of my phone...
When i was trying to install a custom recovery(TWRP), I faced the isuue of Invalid partition name recovery.
I have already cleared the stock recovery.
Please help me!!!
(bootloader) is-logical:recovery: not found
Sending 'recovery' (34224 KB)
OKAY [ 1.288s]
Writing 'recovery'
(bootloader) Invalid partition name
recovery FAILED (remote: '') fastboot: error: Command failed
Thanks in advance....
have you try typing recovery.img instead of recovery?
ineedroot69 said:
have you try typing recovery.img instead of recovery?
Click to expand...
Click to collapse
Thanks for the reply
did you mean
original with extension - recovery.img
new(as per suggestion) - recovery.img.img
because i had already tried recovery.img.. if you want me to try the second one, please do reply.
sksmi2002 said:
hey there...
I own a moto z2 force running the latest version it supports - Android 9 Pie.
I have unlocked the bootloader of my phone...
When i was trying to install a custom recovery(TWRP), I faced the isuue of Invalid partition name recovery.
I have already cleared the stock recovery.
Please help me!!!
(bootloader) is-logical:recovery: not found
Sending 'recovery' (34224 KB)
OKAY [ 1.288s]
Writing 'recovery'
(bootloader) Invalid partition name
recovery FAILED (remote: '') fastboot: error: Command failed
Thanks in advance....
Click to expand...
Click to collapse
Are you using this version?
https://forum.xda-developers.com/z2-force/development/twrp-3-1-1-0-moto-z2-force-nash-t3687421
Sent from my mata using XDA Labs
---------- Post added at 07:18 PM ---------- Previous post was at 07:13 PM ----------
Also see
https://forum.xda-developers.com/z2-force/how-to/guides-bootloader-twrp-custom-roms-root-t3805737.
Sent from my mata using XDA Labs
Looks like the x2 force has 2 system partition s
Try switching active partition then flash twrp
Sent from my mata using XDA Labs
sd_shadow said:
Looks like the x2 force has 2 system partition s
Try switching active partition then flash twrp
Sent from my mata using XDA Labs
Click to expand...
Click to collapse
please can you get me a guide on how to do so...
sksmi2002 said:
please can you get me a guide on how to do so...
Click to expand...
Click to collapse
Setting up and Using adb.exe and fastboot.exe https://forum.xda-developers.com/android/general/index-links-setting-using-adb-fastboot-t3495167
Sent from my Cosmo_Communicator using XDA Labs
I have same problem can you look?
Code:
[email protected]:~/Documents/Phone/ANDROID/MOTOROLA/Moto Z2 Force/TWRP$ fastboot flash recovery twrp-3.3.0-0-nash.img
(bootloader) is-logical:recovery: not found
Sending 'recovery' (30428 KB) OKAY [ 0.896s]
Writing 'recovery' (bootloader) Invalid partition name recovery
FAILED (remote: '')
fastboot: error: Command failed
[email protected]:~/Documents/Phone/ANDROID/MOTOROLA/Moto Z2 Force/TWRP$ fastboot flash recovery twrp-installer-3.3.1-0-nash.zip
(bootloader) is-logical:recovery: not found
Sending 'recovery' (17744 KB) OKAY [ 0.513s]
Writing 'recovery' (bootloader) Invalid partition name recovery
FAILED (remote: '')
fastboot: error: Command failed
[email protected]:~/Documents/Phone/ANDROID/MOTOROLA/Moto Z2 Force/TWRP$ fastboot getvar current-slot
current-slot: _b
Finished. Total time: 0.000s
[email protected]:~/Documents/Phone/ANDROID/MOTOROLA/Moto Z2 Force/TWRP$ fastboot flash boot_b twrp-3.3.0-0-nash.img
(bootloader) is-logical:boot_b: not found
Sending 'boot_b' (30428 KB) OKAY [ 0.865s]
Writing 'boot_b' OKAY [ 0.278s]
Finished. Total time: 1.145s
[email protected]:~/Documents/Phone/ANDROID/MOTOROLA/Moto Z2 Force/TWRP$ fastboot --set-active=a
Setting current slot to 'a' OKAY [ 0.238s]
Finished. Total time: 0.238s
[email protected]:~/Documents/Phone/ANDROID/MOTOROLA/Moto Z2 Force/TWRP$ fastboot flash boot_a twrp-3.3.0-0-nash.img
(bootloader) is-logical:boot_a: not found
Sending 'boot_a' (30428 KB) OKAY [ 0.836s]
Writing 'boot_a' OKAY [ 0.281s]
Finished. Total time: 1.118s
[email protected]:~/Documents/Phone/ANDROID/MOTOROLA/Moto Z2 Force/TWRP$ fastboot flash recovery twrp-3.3.0-0-nash.img
(bootloader) is-logical:recovery: not found
Sending 'recovery' (30428 KB) OKAY [ 0.855s]
Writing 'recovery' (bootloader) Invalid partition name recovery
FAILED (remote: '')
fastboot: error: Command failed
[email protected]:~/Documents/Phone/ANDROID/MOTOROLA/Moto Z2 Force/TWRP$ fastboot flash recovery twrp-installer-3.3.1-0-nash.zip
(bootloader) is-logical:recovery: not found
Sending 'recovery' (17744 KB) OKAY [ 0.490s]
Writing 'recovery' (bootloader) Invalid partition name recovery
FAILED (remote: '')
fastboot: error: Command failed
sd_shadow said:
Setting up and Using adb.exe and fastboot.exe https://forum.xda-developers.com/android/general/index-links-setting-using-adb-fastboot-t3495167
Sent from my Cosmo_Communicator using XDA Labs
Click to expand...
Click to collapse
@sd_shadow
---------- Post added at 10:39 AM ---------- Previous post was at 10:28 AM ----------
I can't flash recovery but I boot in it and this is how I use TWRP.
Hi,
Can someone please help me with fix of my P20 lite dual?
I try to fix it for 50 hours in total, I downloaded about 150Gb of files ☹
The begining of my problem started from full working state one day, next morning I got error "your device has failed verification and may not work properly"
Phone was running stock ANE-LX1 9.1.0 C432 E6R1P7
Factory reset and cache wipe did not help.
Any attempt to SD or USB update via recovery failed, always got "Install failed"
So I tried flashing file update.app using MRT from some higher version of stock sw in fastboot, then in stock recovery, later in TWRP.
No luck, phone was in fastboot mode only or bootloops.
Then I found huawei flash tool IDT 2.0.0.9 and factory board sw 1.0.0.40 using test point (HUAWEI COM 1.0)
With this one the phone fully boots in factory firmware, but phone info says model HAT, has bootlogo ASCEND and android logo , IMEIs in menu are OK.
So how the hell can I get it back to official stock state with ANE-LX1 in "About phone"?
Any attempt of flashing ANE-LX1 sw from menu or stock recovery gives me Flash failed message.
From what I found, I probably need 3 file firmware FullOtaMF for HwOta tool, but nowhere can be found.
Or is there some easy way to flash to official ?
Or did I messed up some system files that need to be fixed?
PS: while flashing hundred of files I found one TWRP version, that can change BL lock code, so I changed it to 111111111111111 for easier unlock in future attempts.
Can be this a problem? (I hope not)
Thank you for any ideas !
hdano said:
From what I found, I probably need 3 file firmware FullOtaMF for HwOta tool, but nowhere can be found.
Click to expand...
Click to collapse
HwOTA will won't help you - it cannot identify the device in this state...
(model HAT, EMUI 4.1, Marshmallow, RAM 2.1GB )
In fastboot mode run commands:
fastboot oem get-build-number
fastboot oem get-product-model
fastboot getvar vendorcountry
fastboot oem oeminforead-CUSTOM_VERSION
fastboot oem oeminforead-SYSTEM_VERSION
and post the results.
-Alf- said:
HwOTA will won't help you - it cannot identify the device in this state...
(model HAT, EMUI 4.1, Marshmallow, RAM 2.1GB )
In fastboot mode run commands:
fastboot oem get-build-number
fastboot oem get-product-model
fastboot getvar vendorcountry
fastboot oem oeminforead-CUSTOM_VERSION
fastboot oem oeminforead-SYSTEM_VERSION
and post the results.
Click to expand...
Click to collapse
C:\adb>fastboot oem get-build-number
...
(bootloader) :ANE-BD 1.0.0.40(log)
OKAY [ 0.011s]
finished. total time: 0.013s
C:\adb>
C:\adb>fastboot oem get-product-model
...
(bootloader) ANE
OKAY [ 0.011s]
finished. total time: 0.013s
C:\adb>
C:\adb>fastboot getvar vendorcountry
getvar:vendorcountry FAILED (remote: cannot get vendorcountry in oeminfo)
finished. total time: 0.022s
C:\adb>
C:\adb>fastboot oem oeminforead-CUSTOM_VERSION
...
FAILED (remote: The reason of failed input oem_nv_item error!)
finished. total time: 0.018s
C:\adb>
C:\adb>fastboot oem oeminforead-SYSTEM_VERSION
...
FAILED (remote: Read oeminfo failed!)
finished. total time: 0.021s
hdano said:
any ideas
Click to expand...
Click to collapse
maybe the following will help you:
- Download TWRP Service ROM oeminfo and
Recovery_ramdisk for Oreo
- Unpack Service ROM package, find dload folder and transfer it to the SD card WITHOUT UNPACKING IT.
- Also copy to the SD card downloaded recovery_ramdisk oeminfo file and TWRP
- Install TWRP over eRecovery (only read the principle, not download links)
- boot into TWRP , select Install image , find oeminfo file, mark 'oeminfo' and flash it.
- Go back to the main TWRP's menu, select Reboot and Turn off.
- Use three button combo and try to install Service ROM .
Note: you do everything at your own risk, I hope that's clear
Hi Alf,
thanks for reply,
worked like a charm !
Phone booted in official rom, was working well.
But..
If I try to download OTA update from menu, it shows me update to ANE-LX1 8.0.0.174(C432)-FULL size 2.92GB ,
but after downloading phone shows install error.
I did factory reset and cache clear, same result, can not install.
So I downloaded to SD card latest sw Huawei P20 Lite ( Nova 3e ) ANE-L21 ANE-L01 hw eu Anne-L01 9.1.0.370(C432E7R1P7T8) Firmware EMUI9.1.0 05014YXU [androidhost.ru].zip
but verify goes 5% then 6% then back to 5%, then 6% then shows "install failed"
After attempt to update by *#*#2846579#*#* from menu, phone did the same, 5% 6% 5% 6% "install failed", but after reboot I have attached photo error :-(
Now not booting again, stuck in this error.
So how can I update to some new sw ?
Do I have to use some special version to go higher?
Or is it some other problem?
BTW, fastboot shows now Phone Locked and FRP locked, but I did not add any google account yet :-O
hdano said:
BTW, fastboot shows now Phone Locked and FRP locked, but I did not add any google account yet
Click to expand...
Click to collapse
Yes, service ROM lock the bootloader , it's normal.
hdano said:
FRP locked,
Click to expand...
Click to collapse
You can unlock FRP manually in Developer options - "Enable OEM unlock".
Run again fastboot commands and post results.
C:\adb>fastboot oem get-build-number
...
(bootloader) :ANE-LX1 8.0.0.126(C432)
OKAY [ 0.011s]
finished. total time: 0.012s
C:\adb>fastboot oem get-product-model
...
(bootloader) ANE-LX1
OKAY [ 0.009s]
finished. total time: 0.010s
C:\adb>fastboot getvar vendorcountry
vendorcountry: hw/eu
finished. total time: 0.010s
C:\adb>fastboot oem oeminforead-CUSTOM_VERSION
...
FAILED (remote: Read oeminfo failed!)
finished. total time: 0.020s
C:\adb>fastboot oem oeminforead-SYSTEM_VERSION
...
(bootloader) :ANE-LX1 8.0.0.126(C432)
OKAY [ 0.012s]
finished. total time: 0.013s
hdano said:
C:\adb>fastboot oem get-build-number
...
(bootloader) :ANE-LX1 8.0.0.126(C432)
OKAY [ 0.011s]
finished. total time: 0.012s
C:\adb>fastboot oem get-product-model
...
(bootloader) ANE-LX1
OKAY [ 0.009s]
finished. total time: 0.010s
C:\adb>fastboot getvar vendorcountry
vendorcountry: hw/eu
finished. total time: 0.010s
C:\adb>fastboot oem oeminforead-CUSTOM_VERSION
...
FAILED (remote: Read oeminfo failed!)
finished. total time: 0.020s
C:\adb>fastboot oem oeminforead-SYSTEM_VERSION
...
(bootloader) :ANE-LX1 8.0.0.126(C432)
OKAY [ 0.012s]
finished. total time: 0.013s
Click to expand...
Click to collapse
Okay, now boot into eRecovery (not Recovery) and select option Download latest version and recovery.
This ***** sucks :-(
hdano said:
This ***** sucks
Click to expand...
Click to collapse
Try to install .174 Service ROM via dload method.
If you get Install failed error again, then you need unlock bootloader (if it's possible) and flash some partitions in fastboot.
You can use this tutorial . Use downloaded .174 ROM. Extract and flash
- kernel
-ramdisk
- recovery_ramdisk
- system
- cust
Note: cust.img can be found in update_ane-L21_hw_eu
Reboot and turn off the phone, then flash .174 Service ROM or try update via eRecovery.
C:\adb>fastboot flash kernel KERNEL.IMG
target reported max download size of 471859200 bytes
sending 'kernel' (24576 KB)...
OKAY [ 0.893s]
writing 'kernel'...
OKAY [ 0.388s]
finished. total time: 1.286s
C:\adb>fastboot flash ramdisk RAMDISK.IMG
target reported max download size of 471859200 bytes
sending 'ramdisk' (16384 KB)...
OKAY [ 0.602s]
writing 'ramdisk'...
OKAY [ 0.075s]
finished. total time: 0.681s
C:\adb>fastboot flash recovery_ramdisk RECOVERY_RAMDIS.IMG
target reported max download size of 471859200 bytes
sending 'recovery_ramdisk' (32768 KB)...
OKAY [ 1.208s]
writing 'recovery_ramdisk'...
OKAY [ 0.169s]
finished. total time: 1.381s
C:\adb>fastboot flash system SYSTEM.IMG
target reported max download size of 471859200 bytes
sending sparse 'system' 1/8 (460799 KB)...
OKAY [ 19.946s]
writing 'system' 1/8...
OKAY [ 3.866s]
sending sparse 'system' 2/8 (424020 KB)...
OKAY [ 17.042s]
writing 'system' 2/8...
OKAY [ 2.164s]
sending sparse 'system' 3/8 (458375 KB)...
OKAY [ 18.384s]
writing 'system' 3/8...
OKAY [ 2.219s]
sending sparse 'system' 4/8 (460418 KB)...
OKAY [ 18.557s]
writing 'system' 4/8...
OKAY [ 2.213s]
sending sparse 'system' 5/8 (425536 KB)...
OKAY [ 17.164s]
writing 'system' 5/8...
OKAY [ 2.157s]
sending sparse 'system' 6/8 (457971 KB)...
OKAY [ 19.231s]
writing 'system' 6/8...
OKAY [ 2.855s]
sending sparse 'system' 7/8 (460016 KB)...
OKAY [ 19.003s]
writing 'system' 7/8...
OKAY [ 3.147s]
sending sparse 'system' 8/8 (192362 KB)...
OKAY [ 7.791s]
writing 'system' 8/8...
OKAY [ 1.015s]
finished. total time: 156.792s
C:\adb>fastboot flash cust CUST.IMG
target reported max download size of 471859200 bytes
sending 'cust' (139283 KB)...
OKAY [ 5.096s]
writing 'cust'...
OKAY [ 0.794s]
finished. total time: 5.894s
C:\adb>fastboot reboot
rebooting...
Now the only I can get is this, no way to get in eRecovery
hdano said:
Now the only I can get is this, no way to get in eRecovery
Click to expand...
Click to collapse
Chinese??? Wow...
As I said before,
-Alf- said:
turn off the phone, then flash .174 Service ROM
Click to expand...
Click to collapse
Have you tried bro?
-Alf- said:
Chinese??? Wow...
As I said before,
Have you tried bro?
Click to expand...
Click to collapse
how? I can not get in eRecovery, only that chinese recovery or what it is....
hdano said:
how? I can not get in eRecovery, only that chinese recovery or what it is....
Click to expand...
Click to collapse
Service ROM has nothing to do with eRecovery.
As the bootloader got locked, I had to do the whole procedure again,
Board sw 1.0.0.39 , and
-Alf- said:
Download TWRP Service ROM oeminfo and
Recovery_ramdisk for Oreo
- Unpack Service ROM package, find dload folder and transfer it to the SD card WITHOUT UNPACKING IT.
- Also copy to the SD card downloaded recovery_ramdisk oeminfo file and TWRP
- Install TWRP over eRecovery (only read the principle, not download links)
- boot into TWRP , select Install image , find oeminfo file, mark 'oeminfo' and flash it.
- Go back to the main TWRP's menu, select Reboot and Turn off.
- Use three button combo and try to install Service ROM .
Click to expand...
Click to collapse
But I can not get it to work state, 3 button combo always fails.
Can I just simply flash all needed files by fastboot ot TWRP ?
What are all the necessary files for phone to boot up?
- kernel
-ramdisk
- recovery_ramdisk
- system
- cust
what else?
Can I just simply flash some custom ROM that will boot up after TWRP flash ?
BTW, why it should not be possible to directly flash erecovery from fastboot?
For me worked..
C:\adb>fastboot flash erecovery_ramdisk TWRP-oreo-smart.img
target reported max download size of 471859200 bytes
sending 'erecovery_ramdisk' (24790 KB)...
OKAY [ 0.660s]
writing 'erecovery_ramdisk'...
OKAY [ 0.128s]
finished. total time: 0.796s
hdano said:
what else?
Click to expand...
Click to collapse
Nothing.
But keep in mind, that "writing OKAY" does not mean that the file is actually installed (it is too long story to tell why...).
hdano said:
BTW, why it should not be possible to directly flash erecovery from fastboot?
For me worked..
Click to expand...
Click to collapse
Running working stock firmware it's impossible.
hdano said:
Hi,
Can someone please help me with fix of my P20 lite dual?
I try to fix it for 50 hours in total, I downloaded about 150Gb of files ☹
The begining of my problem started from full working state one day, next morning I got error "your device has failed verification and may not work properly"
Phone was running stock ANE-LX1 9.1.0 C432 E6R1P7
Factory reset and cache wipe did not help.
Any attempt to SD or USB update via recovery failed, always got "Install failed"
So I tried flashing file update.app using MRT from some higher version of stock sw in fastboot, then in stock recovery, later in TWRP.
No luck, phone was in fastboot mode only or bootloops.
Then I found huawei flash tool IDT 2.0.0.9 and factory board sw 1.0.0.40 using test point (HUAWEI COM 1.0)
With this one the phone fully boots in factory firmware, but phone info says model HAT, has bootlogo ASCEND and android logo , IMEIs in menu are OK.
So how the hell can I get it back to official stock state with ANE-LX1 in "About phone"?
Any attempt of flashing ANE-LX1 sw from menu or stock recovery gives me Flash failed message.
From what I found, I probably need 3 file firmware FullOtaMF for HwOta tool, but nowhere can be found.
Or is there some easy way to flash to official ?
Or did I messed up some system files that need to be fixed?
PS: while flashing hundred of files I found one TWRP version, that can change BL lock code, so I changed it to 111111111111111 for easier unlock in future attempts.
Can be this a problem? (I hope not)
Thank you for any ideas !
Click to expand...
Click to collapse
I’ve exactly the same as your issue.
But I’ve no service and dual iemis are right!
What could be the problem, did you solve yours?
Or even were you having same no service issue while you were on this case?
My device originally is nova 3e ANE l-LX1 c185 dual sim and flashed oeminfo for c185 by editing the oeminfo for c432 and by using oeminfo tools.
Also using howta8 to change oeminfo.
It was changed ok to c185 but still no service and software not installed.
I used build 160 because it’s the only have 3 files, it was installed from hisuite document/hisuite/rom folder