Database Users

Moto Downgrade Utility

** View the making of moto downgrade tool at https://youtu.be/xaJKx9Vqdjc ***
Please like and subscribe to my youtube channel to encourage me to create more tools for the members of xda ! I really really appreciate it
Moto Downgrade Tool is a tool that I have quickly created to SAFELY downgrade android marshmallow to android lollipop on the XT1541 model.
You need Python 3.5 installed to run this program !!
make sure your phone is plugged into your pc and in fastboot mode when you start the tool.
INSTALL MOTO DRIVERS BEFORE USING THE TOOL !!!!
ADB and Fastboot is included in the downgrade tool.
Please comment if you have any issues ! This tool has been tested a few times by myself on my phone. , so it is guaranteed to be able to function correctly !
XDA:DevDB Information
Moto Downgrade Utility, Tool/Utility for the Moto G 2015
Contributors
therealduff1
Version Information
Status: Stable
Current Stable Version: 1.0
Created 2016-03-02
Last Updated 2016-03-02

Keep going on Master!
Sorry for the off topic questions
I'm searching a Rom with multi window feature + floating windows apps like last Sammy's roms for XT1541 do you know any?
Currently using last Resurrection Remix from Vatsal that have multi window but not floating windows
One off topic more:
I have XT1541 European version obtained in Spain but I'm using it in Argentina and my mobile connection (4g) its very slow
I have to change the modem or something else?
Thanks a lot mate!
Enviado desde mi XT1541 mediante Tapatalk

fedez said:
Keep going on Master!
Sorry for the off topic questions
I'm searching a Rom with multi window feature + floating windows apps like last Sammy's roms for XT1541 do you know any?
Currently using last Resurrection Remix from Vatsal that have multi window but not floating windows
One off topic more:
I have XT1541 European version obtained in Spain but I'm using it in Argentina and my mobile connection (4g) its very slow
I have to change the modem or something else?
Thanks a lot mate!
Enviado desde mi XT1541 mediante Tapatalk
Click to expand...
Click to collapse
No need to be sorry for off topic questions !
About the rom , i am not to sure about finding a rom with floating windows , but i would like that aswell !
Also , about using a european device in a different location, this is probably due to different network bands. I would NOT reccomend you flash another models modem, as this could hard brick your phone .
I foyu have any other questions, dont hesitate to ask !

I want to downgrade from stock mm(not rooted) to LP, possible?

arun356y said:
I want to downgrade from stock mm(not rooted) to LP, possible?
Click to expand...
Click to collapse
Using my tool , yes ! . Remember not to accept ota tho

How are you doing the downgrade without having the bootloader unlocked???
Also, is this flashing EVERYTHING, including the bootloader and partition table, or is this just a tool to perform the "normal" downgrade of flashing a factory firmware image and skipping gpt.bin and bootloader.img?

therealduff1 said:
Using my tool , yes ! . Remember not to accept ota tho
Click to expand...
Click to collapse
not to accept ota, why? if in future I want to update then?

acejavelin said:
How are you doing the downgrade without having the bootloader unlocked???
Also, is this flashing EVERYTHING, including the bootloader and partition table, or is this just a tool to perform the "normal" downgrade of flashing a factory firmware image and skipping gpt.bin and bootloader.img?
Click to expand...
Click to collapse
This tool flashes SIGNED images, which means it does not need bootloader unlock. Also , it skips gpt.bin and bootloader.img . It is a normal downgrade, but i made this tool for people who dont want to risk bricking their phones typing the wrong command or accidentally flashing gpt.bin or bootloader.img

therealduff1 said:
This tool flashes SIGNED images, which means it does not need bootloader unlock. Also , it skips gpt.bin and bootloader.img . It is a normal downgrade, but i made this tool for people who dont want to risk bricking their phones typing the wrong command or accidentally flashing gpt.bin or bootloader.img
Click to expand...
Click to collapse
So if I use fastboot and flash a lp I just need to skip those 2 files right?

Downgrading from Rooted Stock MM
I have the XT1541 rooted on stock MM, can i downgrade to stock lollipop without bricking the phone ?
I also flashed the squid kernel r15b (latest)

BurningKoala said:
So if I use fastboot and flash a lp I just need to skip those 2 files right?
Click to expand...
Click to collapse
No need to use fastboot if you trust my programming . but yes , skip gpt.bin and bootloader.IMG and you will be fine my program automatically does that

Hello does my xt1541 need to be unlocked and rooted for this tool to work and downgrade from mm to lollipop?

Agiofws said:
Hello does my xt1541 need to be unlocked and rooted for this tool to work and downgrade from mm to lollipop?
Click to expand...
Click to collapse
No root needed !

Luigi_Manga said:
Ok then, I'll try tonight, does this work whit every rom despite the different number of sparsechunks?
Sent from my MotoG3 using Tapatalk
Click to expand...
Click to collapse
Yes it should work perfectly

Didn't work, still on the crappy 6.0
Partition table has been skipped!
Bootloader has been skipped!
target reported max download size of 268435456 bytes
sending 'logo' (917 KB)...
OKAY [ 0.040s]
writing 'logo'...
OKAY [ 0.071s]
finished. total time: 0.114s
boot logo has been flashed
target reported max download size of 268435456 bytes
sending 'boot' (16384 KB)...
OKAY [ 0.649s]
writing 'boot'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 1.183s
boot.img has been flashed
target reported max download size of 268435456 bytes
sending 'recovery' (16484 KB)...
OKAY [ 0.651s]
writing 'recovery'...
OKAY [ 0.961s]
finished. total time: 1.616s
Stock lollipop recovery has now been flashed
target reported max download size of 268435456 bytes
sending 'system' (262140 KB)...
OKAY [ 10.071s]
writing 'system'...
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 10.515s
System part 1 has been flashed
target reported max download size of 268435456 bytes
sending 'system' (262143 KB)...
OKAY [ 10.079s]
writing 'system'...
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 10.124s
System part 2 has been flashed
target reported max download size of 268435456 bytes
sending 'system' (232632 KB)...
OKAY [ 8.988s]
writing 'system'...
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 9.060s
System part 3 has been flashed
target reported max download size of 268435456 bytes
sending 'system' (233355 KB)...
OKAY [ 8.971s]
writing 'system'...
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 9.014s
System part 4 has been flashed
target reported max download size of 268435456 bytes
sending 'system' (257122 KB)...
OKAY [ 9.884s]
writing 'system'...
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 9.927s
System part 5 has been flashed
target reported max download size of 268435456 bytes
sending 'system' (236089 KB)...
OKAY [ 9.090s]
writing 'system'...
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 9.124s
System part 7 has been flashed
system partitions successfully flashed
target reported max download size of 268435456 bytes
sending 'modem' (36940 KB)...
OKAY [ 1.423s]
writing 'modem'...
OKAY [ 0.994s]
finished. total time: 2.423s
Flashed Mobile Data Connection Chip Data
erasing 'modemst1'...
OKAY [ 0.019s]
finished. total time: 0.021s
erasing 'modemst2'...
OKAY [ 0.014s]
finished. total time: 0.015s
Old data erased
target reported max download size of 268435456 bytes
sending 'fsg' (2031 KB)...
OKAY [ 0.083s]
writing 'fsg'...
OKAY [ 0.083s]
finished. total time: 0.169s
Flashed FSG
erasing 'cache'...
OKAY [ 0.019s]
finished. total time: 0.021s
cache erased
erasing 'userdata'...
OKAY [ 0.199s]
finished. total time: 0.201s
userdata partition formatted
rebooting...
finished. total time: 0.006s
flash finished
***PLEASE READ BELOW***
YOU MUST NOT ACCEPT ANY OTA UPDATES ON YOUR PHONE WHILE IT IS RUNNING LOLLIPOP
OR YOU ARE RISKING A HARD BRICK DUE TO UPGRADING THE BOOTLOADER WHICH IS AT A DI
FFERENT VERSION
THAN EXPECTED
and thats all !
enjoy lollipop again!
Press any key to continue . . .
Click to expand...
Click to collapse

Sorry for the noob question but does the bootloader have to be unlocked?

BurningKoala said:
Didn't work, still on the crappy 6.0
Click to expand...
Click to collapse
Agiofws said:
Sorry for the noob question but does the bootloader have to be unlocked?
Click to expand...
Click to collapse
Downgrade using fastboot it's not possible without unlocked bootloader, that's why I think it didn't work.

coolizard said:
Downgrade using fastboot it's not possible without unlocked bootloader, that's why I think it didn't work.
Click to expand...
Click to collapse
I flashed mine using a locked bootloader

BurningKoala said:
Didn't work, still on the crappy 6.0
Click to expand...
Click to collapse
Ok right , this is a problem with the image, not my program . Are you flashing the correct image for your phone ?

therealduff1 said:
Ok right , this is a problem with the image, not my program . Are you flashing the correct image for your phone ?
Click to expand...
Click to collapse
Yes, I flashed the xt1541 vodafone EU that was on my phone (now I'm on vodafone 6.0), did you think that it's better I flash the no brand eu version?
edit: same errors with the retail eu

Can't flash TWRP with unlocked bootloader

Hiii,
I've read many threads but didn't find my answer, I have an unlocked bootloader but can't flash TWRP recovery.
Tried many different versions but all tries give me an "remote: image verification error"
Device is fastboot mode:
C:\Temp>fastboot devices -l
4<serial hidden>7 fastboot
Bootloader unlocked with official unlock code:
C:\Temp>fastboot oem get-bootinfo
...
(bootloader) unlocked
OKAY [ 0.006s]
finished. total time: 0.007s
Flash TWRP (failed) and flash STOCK (success):
C:\TEMP>fastboot flash recovery recovery_twrp.img
target reported max download size of 471859200 bytes
sending 'recovery' (28928 KB)...
OKAY [ 0.617s]
writing 'recovery'...
FAILED (remote: image verification error)
finished. total time: 0.634s
C:\TEMP>fastboot flash recovery recovery_stock.img
target reported max download size of 471859200 bytes
sending 'recovery' (32960 KB)...
OKAY [ 0.701s]
writing 'recovery'...
OKAY [ 1.102s]
finished. total time: 1.805s
Any ideas... what can I do/ what should try?
Thx!
Strange is when I :
C:\Temp>fastboot oem get-lockstate
...
(bootloader) locked
OKAY [ 0.004s]
finished. total time: 0.005s
it say's it's locked, but when I try to unlock with correct code, it gives a message wrong password, so it's unlocked :|

roelprincen said:
Hiii,
I've read many threads but didn't find my answer, I have an unlocked bootloader but can't flash TWRP recovery.
Tried many different versions but all tries give me an "remote: image verification error"
Device is fastboot mode:
C:\Temp>fastboot devices -l
4<serial hidden>7 fastboot
Bootloader unlocked with official unlock code:
C:\Temp>fastboot oem get-bootinfo
...
(bootloader) unlocked
OKAY [ 0.006s]
finished. total time: 0.007s
Flash TWRP (failed) and flash STOCK (success):
C:\TEMP>fastboot flash recovery recovery_twrp.img
target reported max download size of 471859200 bytes
sending 'recovery' (28928 KB)...
OKAY [ 0.617s]
writing 'recovery'...
FAILED (remote: image verification error)
finished. total time: 0.634s
C:\TEMP>fastboot flash recovery recovery_stock.img
target reported max download size of 471859200 bytes
sending 'recovery' (32960 KB)...
OKAY [ 0.701s]
writing 'recovery'...
OKAY [ 1.102s]
finished. total time: 1.805s
Any ideas... what can I do/ what should try?
Thx!
Strange is when I :
C:\Temp>fastboot oem get-lockstate
...
(bootloader) locked
OKAY [ 0.004s]
finished. total time: 0.005s
it say's it's locked, but when I try to unlock with correct code, it gives a message wrong password, so it's unlocked :|
Click to expand...
Click to collapse
same with me ?

Try to relock and then unlock. I've had this problem too after downgrade to mm by official Huawei rollback package. Then phone and other tools shows than phone is unlocked and it was unable to flash recovery.

if it says wrong password it means you got the wrong password. it will say it's already unlocked if you try unlocking it while it's unlocked

My phone was unlocked with Potato v2.0.1, with working TWRP, rooted etc...
I solved this problem that arose after unsuccesfully install custom Rom, restore backup of stock rom, install update through dload and many many other attempts at improvement of my smartphone :-( No more time again!!!
Probably installing update through Dload will relock bootloader, but in the fastboot mode it says bootloader still unlocked.
Before I did all this, I had an original stock rom.
1: Relock bootloader with PotatoNV v2.0.1 (You need to open case and connect tespoint by wire - look on Youtube, i´ve find it there, also you need "Huawei testpoint drivers")
2: Factory reset
3: Install any update stock rom with Dload (Vol up + Vol down + power)
4: Factory reset
5: Developer options-turn on OEM unlock and USB debbuging
6:Unlock bootloader with PotatoNV v2.0.1 - keep password generated by Potato
7:Multitool 8 for Huawei - in the bootloader state unlock bootloader again - use password generated by Potato
8:Multitool 8 for huawei - install TWRP - it says "Succesfully installed" - TWRP works, root is possible. Yeah!!!
May be this is not right way to solve this, but for me it workś..

Fastboot Drivers

Hello guys,
I know this question is very common but I have looked many posts and couldn't find any that solved my problem.
I am trying to flash the stock moto X pure edition (xt1575) again in my device. The trouble starts because fastboot doesn't work.
I already installed Motorola device manager (2.5.4) and booted windows without driver signature enforcement.
I tried adb-setup-1.4.3.exe and installing android SDK, but still get same trouble.
The phone works and get normally funcional when android is loaded, but no responde in fastboot screen!
I am using windows 10.15063.296 (creators update). When I open device manager, now I see "Motorola adb device" with an exclamation.

A lot of windows, especially windows 10, users seem to struggle with drivers. I use Linux and never have any problems.
Maybe you could give this a try. https://www.xda-developers.com/forget-windows-use-linux-is-a-usb-bootable-distro-for-your-android-recovery-needs-xda-spotlight/

jason2678 said:
A lot of windows, especially windows 10, users seem to struggle with drivers. I use Linux and never have any problems.
Maybe you could give this a try. https://www.xda-developers.com/forg...or-your-android-recovery-needs-xda-spotlight/
Click to expand...
Click to collapse
Thanks. After hours trying, I could get fastboot working.
The issue now is that I got "preflash failed" when trying the officially image available.
Enviado de meu XT1575 usando Tapatalk

Belotto said:
Thanks. After hours trying, I could get fastboot working.
The issue now is that I got "preflash failed" when trying the officially image available.
Enviado de meu XT1575 usando Tapatalk
Click to expand...
Click to collapse
Just on bootloader and gpt.bin, or everything?
That happens when you try to downgrade the partition table, but usually as long as you flash all the other parts successfully it works. Keep a close eye on the output when you flash modem; it tends to fail on the first try.

https://forum.xda-developers.com/showthread.php?t=2588979
This is the one... I had this on my window's 10. I upgraded to creators update and i doubted that this might not work but it did work for me

jason2678 said:
Just on bootloader and gpt.bin, or everything?
That happens when you try to downgrade the partition table, but usually as long as you flash all the other parts successfully it works. Keep a close eye on the output when you flash modem; it tends to fail on the first try.
Click to expand...
Click to collapse
I really wasn´t successful...
PS C:\Android\sdk\platform-tools\CLARK_RETUS_MPH24.49-18_18_retus_US> adb reboot-bootloader
PS C:\Android\sdk\platform-tools\CLARK_RETUS_MPH24.49-18_18_retus_US> fastboot flash partition gpt.bin
target reported max download size of 536870912 bytes
sending 'partition' (32 KB)...
OKAY [ 0.016s]
writing 'partition'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.370s
PS C:\Android\sdk\platform-tools\CLARK_RETUS_MPH24.49-18_18_retus_US> fastboot flash motoboot motoboot.img
error: cannot load 'motoboot.img'
PS C:\Android\sdk\platform-tools\CLARK_RETUS_MPH24.49-18_18_retus_US> fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.000s]
finished. total time: 0.000s
PS C:\Android\sdk\platform-tools\CLARK_RETUS_MPH24.49-18_18_retus_US> fastboot flash logo logo.bin
target reported max download size of 536870912 bytes
sending 'logo' (3687 KB)...
OKAY [ 0.137s]
writing 'logo'...
OKAY [ 0.200s]
finished. total time: 0.337s
PS C:\Android\sdk\platform-tools\CLARK_RETUS_MPH24.49-18_18_retus_US> fastboot flash boot boot.img
target reported max download size of 536870912 bytes
sending 'boot' (40960 KB)...
OKAY [ 1.518s]
writing 'boot'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 1.888s
PS C:\Android\sdk\platform-tools\CLARK_RETUS_MPH24.49-18_18_retus_US> fastboot flash recovery recovery.img
target reported max download size of 536870912 bytes
sending 'recovery' (41040 KB)...
OKAY [ 1.534s]
writing 'recovery'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 1.887s
PS C:\Android\sdk\platform-tools\CLARK_RETUS_MPH24.49-18_18_retus_US> fastboot flash system system.img
target reported max download size of 536870912 bytes
sending sparse 'system' (509631 KB)...
OKAY [ 17.857s]
writing 'system'...
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 18.357s
PS C:\Android\sdk\platform-tools\CLARK_RETUS_MPH24.49-18_18_retus_US> fastboot reboot
rebooting...
finished. total time: 0.016s
PS C:\Android\sdk\platform-tools\CLARK_RETUS_MPH24.49-18_18_retus_US> fastboot erase userdata
erasing 'userdata'...
OKAY [ 6.423s]
finished. total time: 6.423s
PS C:\Android\sdk\platform-tools\CLARK_RETUS_MPH24.49-18_18_retus_US> fastboot erase cache
erasing 'cache'...
OKAY [ 0.031s]
finished. total time: 0.031s
PS C:\Android\sdk\platform-tools\CLARK_RETUS_MPH24.49-18_18_retus_US> fastboot oem lock
...
(bootloader) Please run fastboot oem lock begin first!
OKAY [ 0.015s]
finished. total time: 0.015s
PS C:\Android\sdk\platform-tools\CLARK_RETUS_MPH24.49-18_18_retus_US> fastboot oem lock begin
...
(bootloader) Not supported command in current status!
FAILED (remote failure)
finished. total time: 0.017s
PS C:\Android\sdk\platform-tools\CLARK_RETUS_MPH24.49-18_18_retus_US> fastboot oem lock
...
(bootloader) Please run fastboot oem lock begin first!
OKAY [ 0.000s]
finished. total time: 0.000s
PS C:\Android\sdk\platform-tools\CLARK_RETUS_MPH24.49-18_18_retus_US>

jason2678 said:
Just on bootloader and gpt.bin, or everything?
That happens when you try to downgrade the partition table, but usually as long as you flash all the other parts successfully it works. Keep a close eye on the output when you flash modem; it tends to fail on the first try.
Click to expand...
Click to collapse
Sagar_1401 said:
https://forum.xda-developers.com/showthread.php?t=2588979
This is the one... I had this on my window's 10. I upgraded to creators update and i doubted that this might not work but it did work for me
Click to expand...
Click to collapse
I have tried it before... wasn't working but i realized that i needed to push "allow oem unlock" and "usb debugging" buttons ... LOL.

Help Huawei p8 lite Bricked and infinite boot-loop and only access to fastboot mode

hi guys i have found on my hand a huawei p8 lite in an infinite boot-loop and cant access to any thing only fastboot but the problem that the bootloader is locked and i have no way to unlock it and when i try to flash anything with fastboot i get this error
target max-download-size: 450MB
sending 'boot' (21706 KB)...
OKAY [ 0.469s]
writing 'boot'...
FAILED (remote: Command not allowed)
finished. total time: 0.484s
target max-download-size: 450MB
sending 'recovery' (34280 KB)...
OKAY [ 0.750s]
writing 'recovery'...
FAILED (remote: Command not allowed)
finished. total time: 0.750s
target max-download-size: 450MB
sending 'cust' (218981 KB)...
OKAY [ 4.710s]
writing 'cust'...
FAILED (remote: Command not allowed)
finished. total time: 4.726s
target max-download-size: 450MB
Sparse-Flash is enabled!
sending sparse 'system' (460798 KB)...
OKAY [ 10.479s]
writing 'system'...
FAILED (remote: Command not allowed)
finished. total time: 10.479s
i tried to unlock the bootloader at https://emui.huawei.com/en/plugin/unlock/detail but i have no Product ID no serial number and no product number and it been a hell of tow days i calculated the product id with the huawei generator and the website tells me the imei is wrong try the second imei and i dont have anyone have an idea how to unbricke it cant flash i tried every possible firmware and i cant enter update mode with sdcard:crying::crying::crying:

AnonDz said:
hi guys i have found on my hand a huawei p8 lite in an infinite boot-loop and cant access to any thing only fastboot but the problem that the bootloader is locked and i have no way to unlock it and when i try to flash anything with fastboot i get this error
target max-download-size: 450MB
sending 'boot' (21706 KB)...
OKAY [ 0.469s]
writing 'boot'...
FAILED (remote: Command not allowed)
finished. total time: 0.484s
target max-download-size: 450MB
sending 'recovery' (34280 KB)...
OKAY [ 0.750s]
writing 'recovery'...
FAILED (remote: Command not allowed)
finished. total time: 0.750s
target max-download-size: 450MB
sending 'cust' (218981 KB)...
OKAY [ 4.710s]
writing 'cust'...
FAILED (remote: Command not allowed)
finished. total time: 4.726s
target max-download-size: 450MB
Sparse-Flash is enabled!
sending sparse 'system' (460798 KB)...
OKAY [ 10.479s]
writing 'system'...
FAILED (remote: Command not allowed)
finished. total time: 10.479s
i tried to unlock the bootloader at https://emui.huawei.com/en/plugin/unlock/detail but i have no Product ID no serial number and no product number and it been a hell of tow days i calculated the product id with the huawei generator and the website tells me the imei is wrong try the second imei and i dont have anyone have an idea how to unbricke it cant flash i tried every possible firmware and i cant enter update mode with sdcard:crying::crying::crying:
Click to expand...
Click to collapse
Hold volume up while connected to PC......You should enter eRecovery....From there download firmware and install

no way to connect it i tried
and when i try to get the unlock code to the bootloader in the website it gives me this error
Please make sure the verification code and model number are correct. If your device has multiple IMEIs or MEIDs, please try another IMEI or MEID.

AnonDz said:
no way to connect it i tried
and when i try to get the unlock code to the bootloader in the website it gives me this error
Please make sure the verification code and model number are correct. If your device has multiple IMEIs or MEIDs, please try another IMEI or MEID.
Click to expand...
Click to collapse
I didn't say anything about unlock bootloader....
Just holds power and volume up button while connected to PC.......
BTW how did you end up in boot loop ?

and i just add that i couldn't unlock the bootloader and i already told you that i have access onlyn to fastboot and rescue mode bro

do you think i will be here if i could enter the recovery update

The only thing I can think of is to install Hisuite to a windows PC and try the recovery option in hi suite
---------- Post added at 08:43 PM ---------- Previous post was at 08:40 PM ----------
Oh another thing did you register your phone to a google account?
If you did log into Google dashboard and expand the Android section it will list all of your devices and the imei so you should be able to use that to unlock the bootloader

AnonDz said:
no way to connect it i tried
and when i try to get the unlock code to the bootloader in the website it gives me this error
Please make sure the verification code and model number are correct. If your device has multiple IMEIs or MEIDs, please try another IMEI or MEID.
Click to expand...
Click to collapse
I have unlock my bootloader using this video tutorial give a try

cristi.blidariu said:
I have unlock my bootloader using this video tutorial give a try
Click to expand...
Click to collapse
I already tried this method and yet nothing

ndg_2000 said:
The only thing I can think of is to install Hisuite to a windows PC and try the recovery option in hi suite
---------- Post added at 08:43 PM ---------- Previous post was at 08:40 PM ----------
Oh another thing did you register your phone to a google account?
If you did log into Google dashboard and expand the Android section it will list all of your devices and the imei so you should be able to use that to unlock the bootloader
Click to expand...
Click to collapse
And no I got the phone in this state so no I didn't connect it to my google account

Ok i searched for ways to find an IMEI number and found couple of ways...
1) Look under/in the sim tray. It may be there (I didn't check this out)
2) Find the IMEI/MEID using Google Dashboard. This is Google's control center that can be accessed from any computer with a web browser. You will need to log in with the Google account associated with your Android phone.You can access Google Dashboard by visiting www.google.com/settings/dashboard Expand the "Android" section by clicking the "Android" heading.Locate your phone in the list. If you have multiple devices associated with your account, all of the devices will be displayed. Find the device that you are trying to retrieve the IMEI/MEID number for. (This works)
3) At last, you can try to remove the back case and remove the battery. This can help you in 2 ways. Firstly, there should be IMEI code present under the battery. Secondly, this may cause you to get out of bootloop

P9 lite L31 Europe Hard Bricked

Hi,
I have a p9 lite VNS-L31 Europe Model.
I have Phone Unlocked and FRP Unlocked.
The problem is that i can no loger boot the device.I tried using the toolkit found here on the server,but it doesn't recognize it anymore.
I tried using cmd fastboot devices. It shows there but i cannot give any command.
"
C:\Users\Nick>fastboot flash system C:\Users\Nick\Desktop\p9\system.img
< waiting for device >
target reported max download size of 471859200 bytes
sending sparse 'system' (451240 KB)...
OKAY [ 15.605s]
writing 'system'...
FAILED (remote: Command not allowed)
finished. total time: 15.619s
"
C:\Users\Nick>fastboot oem get-bootinfo
...
(bootloader) unlocked
OKAY [ 0.000s]
finished. total time: 0.000s
"
I have downloaded a full version.
How can i fix my device ?

Delete...

NickBond said:
Hi,
I have a p9 lite VNS-L31 Europe Model.
I have Phone Unlocked and FRP Unlocked.
The problem is that i can no loger boot the device.I tried using the toolkit found here on the server,but it doesn't recognize it anymore.
I tried using cmd fastboot devices. It shows there but i cannot give any command.
"
C:\Users\Nick>fastboot flash system C:\Users\Nick\Desktop\p9\system.img
< waiting for device >
target reported max download size of 471859200 bytes
sending sparse 'system' (451240 KB)...
OKAY [ 15.605s]
writing 'system'...
FAILED (remote: Command not allowed)
finished. total time: 15.619s
"
C:\Users\Nick>fastboot oem get-bootinfo
...
(bootloader) unlocked
OKAY [ 0.000s]
finished. total time: 0.000s
"
I have downloaded a full version.
How can i fix my device ?
Click to expand...
Click to collapse
Unlock your smartphone again.

JustChris20 said:
Unlock your smartphone again.
Click to expand...
Click to collapse
How ?

Fixed it
Hei
I managed to fixed it by dload with nrd90m test-keys with an SD Card.Then power up with the power and volum + and - .
It works now.