[Solved] Bricked and can't write system - Huawei P9 Lite Questions & Answers

I erased everything in an attempt to unbrick it but that was a mistake. What I have tried and results:
-twrp recovery tried to install the latest stock firmware but got error with mounting system.
-fastboot flash update update.zip didn't solve it
-fastboot seperatly flashing each image, extracted by the update extractor tool. Result:
target reported max download size of 471859200 bytes
sending sparse 'system' 1/6 (451240 KB)...
OKAY [ 23.882s]
writing 'system' 1/6...
FAILED (remote: sparse flash write failure)
finished. total time: 23.958s​-fastboot -w to reformat and try again. Result:
wiping userdata...
Erase successful, but not automatically formatting.
Can't determine partition type.
FAILED (remote: Command not allowed)
erasing 'userdata'...
FAILED (remote: Command not allowed)
finished. total time: 0.012s​OEM is unlocked, I have tried updating from the SD and using the three buttons but I get the wrong format error. Downloaded the MM version as well but I get the incompatible error. Can't download from the erecovery or Hi-Suite. Help please

Have you tried flashing the original oeminfo and then installing with dload? Or maybe try fastboot update method

d0nefufe said:
Have you tried flashing the original oeminfo and then installing with dload? Or maybe try fastboot update method
Click to expand...
Click to collapse
Which original one though? I've been trying and downloaded any Full firmware I could find using a firmware finder, for my VNS-L31 but using the force update method in download so far all of them return an error: Incompatible with current version. I have also tried the fastboot update and separately flashing each file in the update.app . None work so far. I keep trying.

Badwolf9 said:
Which original one though? I've been trying and downloaded any Full firmware I could find using a firmware finder, for my VNS-L31 but using the force update method in download so far all of them return an error: Incompatible with current version. I have also tried the fastboot update and separately flashing each file in the update.app . None work so far. I keep trying.
Click to expand...
Click to collapse
If you're on Nougat, try flashing it's files through fastboot. It worked for me, MM system.img gave me an error, but nougat flashed fine.

I believe ur in nougat beta... Just flash oem info and flash again the nougat from there you can start again and downgrade peacefully

your bootloader is locked

Sh0m1 said:
If you're on Nougat, try flashing it's files through fastboot. It worked for me, MM system.img gave me an error, but nougat flashed fine.
Click to expand...
Click to collapse
Thank you! I followed the instructions here with a slight variation. Because trying to install the update.zip file always gave me errors I extracted the update.APP with the update extractor tool and flashed cache,system,boot with fastboot. Then I opened the custom recovery, installed the other zip file and continued as instructed.

mjz2cool said:
your bootloader is locked
Click to expand...
Click to collapse
No it wasn't. This was my first thought as well.

Badwolf9 said:
No it wasn't. This was my first thought as well.
Click to expand...
Click to collapse
how did you check if it was unlocked? if it says so in fastboot mode it can be incorrect, even when you relock the bootloader it still says unlocked

mjz2cool said:
how did you check if it was unlocked? if it says so in fastboot mode it can be incorrect, even when you relock the bootloader it still says unlocked
Click to expand...
Click to collapse
fastboot oem device-info
Also if it was locked I wouldn't be able to flash anything.

d0nefufe said:
Have you tried flashing the original oeminfo and then installing with dload? Or maybe try fastboot update method
Click to expand...
Click to collapse
where can I find the oeminfo file?

islandman75 said:
where can I find the oeminfo file?
Click to expand...
Click to collapse
This is the L21 - SingleSIM:
https://www.dropbox.com/s/97uad8vc3pwppnq/oeminfoORIGINAL.img?dl=0
And the L21 - DualSIM:
https://www.dropbox.com/s/fq99atzszg2sq1y/oeminfoDUAL.img?dl=0

Related

Blasted kingroot - bricked my phone?

Ahh, hind sight is a wonderful thing.
After trying to use kingroot to get root access, it failed. And a few days later after rebooting.
I'm now stuck at bootup with Start Up Failed.
hab check failed for boot
Failed to verify hab image boot
failed to validate boot image
I've now tried lot's of different things, over the last few hours.
RSDLite (show device brings no thing up)
Unlock bootloader (request key, but error regarding OEM unlock not being set - no access to now set it LOL)
Downloaded stock X_Play_UK_Retail_XT1562_LPD23.118-10_CFC.xml.zip, and tried using various guides on fastboot but keep getting remote failed.
I'm on stock recovery (obviously still locked).
Any thoughts, or hope from anyone?
Obviously, not sure what support Motorola would provide for what is essentially my own fault?
Have you tried manually flashing each bit of the stock firmware/image. That might help. There's a good guide here which I followed to unbrick my device. Just follow the instructions http://theunlockr.com/2015/09/22/how-to-unroot-the-motorola-moto-x-play/
Or try this one.
http://forum.xda-developers.com/showthread.php?t=2499926
Tried the first fastboot oem lock begin but get ... (althought my phone is locked already)
(bootloader) Not supported command in current status!
FAILED (remote failure)
finished. total time: 0.063s
So stepping to next command, I get:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash partition gpt.bin
(bootloader) has-slotartition: not found
target reported max download size of 268435456 bytes
sending 'partition' (32 KB)...
OKAY [ 0.166s]
writing 'partition'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 1.078s
sharebubbles said:
Tried the first fastboot oem lock begin but get ... (althought my phone is locked already)
(bootloader) Not supported command in current status!
FAILED (remote failure)
finished. total time: 0.063s
So stepping to next command, I get:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash partition gpt.bin
(bootloader) has-slotartition: not found
target reported max download size of 268435456 bytes
sending 'partition' (32 KB)...
OKAY [ 0.166s]
writing 'partition'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 1.078s
Click to expand...
Click to collapse
I think you need to unlock the bootloader and then start with the 'fastboot oem lock begin' command. You can't flash a system image with a locked bootloader. Let me know how it goes!
DTLblaze said:
I think you need to unlock the bootloader and then start with the 'fastboot oem lock begin' command. You can't flash a system image with a locked bootloader. Let me know how it goes!
Click to expand...
Click to collapse
I run the unlock command, with my unique key but I get ..
...
(bootloader) Check 'Allow OEM Unlock' in Developer Options.
FAILED (remote failure)
finished. total time: 0.013s
And since I can't get into the phone, I can't therefore check the "allow OEM unclock"
Have you tried any erase data commands or reset commands? Perhaps you could reset the phone so kingroot is un-installed and then try to turn on the phone. Short of that I'm stuck for ideas really, accept booting into 'fastboot and then erasing all data and factory reset in there. Let me know.
DTLblaze said:
Have you tried any erase data commands or reset commands? Perhaps you could reset the phone so kingroot is un-installed and then try to turn on the phone. Short of that I'm stuck for ideas really, accept booting into 'fastboot and then erasing all data and factory reset in there. Let me know.
Click to expand...
Click to collapse
I tried the wipe data/factory reset and wipe cache partition from the stock recovery.
And if I try from fastboot:-
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot erase userdata
(bootloader) has-slot:userdata: not found
erasing 'userdata'...
OKAY [ 0.196s]
finished. total time: 0.198s
And then a fastboot reboot.
Back to the now standard "start up failed"
And the
AP Fastboot Flash Mode (Secure)
hab check failed for boot
Failed to verify hab image boot
failed to validate boot image
ERROR: Failed to pass validation, backup to fastboot
Fastboot reason: Fall-through from normal boot mode
Sickaxis79 said:
Or try this one.
http://forum.xda-developers.com/showthread.php?t=2499926
Click to expand...
Click to collapse
Have downloaded, and tried that - but the crux appears to be the fact that my bootloader is locked and I can't access the OEM checkbox. And therefore the tool itself can't unlock or equally install TWRP.
Unless I'm missing something in it's usage.
sharebubbles said:
I tried the wipe data/factory reset and wipe cache partition from the stock recovery.
And if I try from fastboot:-
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot erase userdata
(bootloader) has-slot:userdata: not found
erasing 'userdata'...
OKAY [ 0.196s]
finished. total time: 0.198s
And then a fastboot reboot.
Back to the now standard "start up failed"
And the
AP Fastboot Flash Mode (Secure)
hab check failed for boot
Failed to verify hab image boot
failed to validate boot image
ERROR: Failed to pass validation, backup to fastboot
Fastboot reason: Fall-through from normal boot mode
Click to expand...
Click to collapse
That really does sound like you bricked the device. If you where on lollipop software you wouldn't have the issue with check bootloader OEM unlock. If it was me I would either contact Motorola or go to a repair shop and have a motd experienced person take a look at it.
Try this, not necessary for unlock bootloader
Recognized Contributor3,144 posts Thanks: 1,591
Quote:
Originally Posted by sheikh.sami17
but i have locked bootloader. can i flash stock firmware with locked bootloader?
YES you can flash stock Moto roms meant for your model and carrier only.
Also, Never attempt to downgrade.
In this page
http://forum.xda-developers.com/moto-x/moto-x-qa/q-how-to-flash-to-stock-firmware-t3041813
I edit and made one firmware autoflasher for my x play Indian version and flashed successfully . everybody should check sparsechunk files no in flash file of your extracted stock firmware and edit my autoflasher files according to number of sparsechunk files and flash your firmware. It is definitely safe and I flashed my firmware by this but use at your own risk .
https://mega.nz/#!aoETEL7b!6WUe8tXeh...HHohpfYf2duoLc
First you have to download your phone's correct firmware and extract in fastboot folder , and add my autoflasher and check your sparsechunk files number and make changes according to that in autoflasher then save ..Enter your phone in fastboot mode or in bootloader and not in stock recovery and run autoflasher.
IF YOU HAVE ANY DOUBT AT TAKING RISK , CONTACT Motorola AND MAKE EVERYTHING EASY.
sharebubbles said:
Have downloaded, and tried that - but the crux appears to be the fact that my bootloader is locked and I can't access the OEM checkbox. And therefore the tool itself can't unlock or equally install TWRP.
Unless I'm missing something in it's usage.
Click to expand...
Click to collapse
Strange. This is the tool I used to unlock my bootloader.
drmuruga said:
Try this, not necessary for unlock bootloader
Recognized Contributor3,144 posts Thanks: 1,591
Quote:
Originally Posted by sheikh.sami17
but i have locked bootloader. can i flash stock firmware with locked bootloader?
YES you can flash stock Moto roms meant for your model and carrier only.
Also, Never attempt to downgrade.
In this page
http://forum.xda-developers.com/moto-x/moto-x-qa/q-how-to-flash-to-stock-firmware-t3041813
I edit and made one firmware autoflasher for my x play Indian version and flashed successfully . everybody should check sparsechunk files no in flash file of your extracted stock firmware and edit my autoflasher files according to number of sparsechunk files and flash your firmware. It is definitely safe and I flashed my firmware by this but use at your own risk .
https://mega.nz/#!aoETEL7b!6WUe8tXeh...HHohpfYf2duoLc
First you have to download your phone's correct firmware and extract in fastboot folder , and add my autoflasher and check your sparsechunk files number and make changes according to that in autoflasher then save ..Enter your phone in fastboot mode or in bootloader and not in stock recovery and run autoflasher.
IF YOU HAVE ANY DOUBT AT TAKING RISK , CONTACT Motorola AND MAKE EVERYTHING EASY.
Click to expand...
Click to collapse
I've ben used the latest rom so far why trying to flash (and failing) when I look at recovery I have a LPD23.118-10 number that matches to an earlier 5.1.1 rom (I had been upgraded to 6.0.1 via OTA updates) - do I therefore take that LPD ID to mean that I should actually use the 5.1.1 rom - I'm in the UK, so I'm assuming I'd use the UK one rather than Europe (I'm looking at roms on https://github.com/motoxplay/stock).
Thanks
Dooh!!
Looking back at what I was doing yesterday, within the mix of downloading various roms - appears that I was actually using the LPD23.118-10 and NOT the latest.
I figured, I'd give it one last whirl using the latest not expecting much - and hey presto, it's worked. Just in the process of resetting it all up again.
Thanks for everyone who contributed, and a lesson learnt about always rechecking what you attempt (and not to try to root if you're not 100% sure of what I'm doing)
sharebubbles said:
Dooh!!
Looking back at what I was doing yesterday, within the mix of downloading various roms - appears that I was actually using the LPD23.118-10 and NOT the latest.
I figured, I'd give it one last whirl using the latest not expecting much - and hey presto, it's worked. Just in the process of resetting it all up again.
Thanks for everyone who contributed, and a lesson learnt about always rechecking what you attempt (and not to try to root if you're not 100% sure of what I'm doing)
Click to expand...
Click to collapse
And also never try kingroot.
sharebubbles said:
Dooh!!
Looking back at what I was doing yesterday, within the mix of downloading various roms - appears that I was actually using the LPD23.118-10 and NOT the latest.
I figured, I'd give it one last whirl using the latest not expecting much - and hey presto, it's worked. Just in the process of resetting it all up again.
Thanks for everyone who contributed, and a lesson learnt about always rechecking what you attempt (and not to try to root if you're not 100% sure of what I'm doing)
Click to expand...
Click to collapse
Most in the threads suggesting using rsdlite or manual flash/root and you decided to use kingroot,haha.
Welcome back.
Guys I have been searching EVERYWHERE on how to unbrick my moto x play, I used kingroot and it bricked, been a week and I TRIED everything. CAN ANYONE HELP PLEASE!!!!!!
---------- Post added at 05:26 AM ---------- Previous post was at 05:14 AM ----------
Guys I have been searching EVERYWHERE on how to unbrick my moto x play, I used kingroot and it bricked, been a week and I TRIED everything. CAN ANYONE HELP PLEASE!!!!!!
Tried restoring it, deleted everything and the phone is still on bootloader (LOCKED) and i dont even know how to fix it, I know nothing on how to root, friend suggested it, downloaded it, installed it, didnt work and then i restarted my phone and now its stuck on bootloader screen and the screen has the message "Start up failed: your device didnt start up successfully. Use the software repair assisstant on computer to repair your device. Connect your device to your computer to get the Software Repair Assistant." <- Downloaded it, tried it and it was stuck on 6% on repairing, left it over night and it was still on 6%.
ALSO under the message "AP Fastboot Flash Mode(Secure) is there)
Hai same problem for my moto x play ple.......s help contact.7708892303(WhatsApp no.)
pravin kkr said:
Hai same problem for my moto x play ple.......s help contact.7708892303(WhatsApp no.)
Click to expand...
Click to collapse
Download and flash this firmware
https://mega.nz/#!H5YlDCrD!T8tAAW7nHVS-erizRiqg5-Yp_p23hKParMjjHD4diQA credits @kumeipark
Use RSD lite to flash the firmware
http://rsdlite.com/rsd-lite-download/
Moto drivers
http://motorola-mobility-en-in.custhelp.com/app/answers/detail/a_id/88481
If you have problems installing device drivers using Windows 8.1 or Windows 10 follow this guide
https://www.youtube.com/watch?v=gmw86KplqmU
And don't post your contact no. in public forums for everyone to see.
what is the decryption key for the mega link
drmuruga said:
Try this, not necessary for unlock bootloader
Recognized Contributor3,144 posts Thanks: 1,591
Quote:
Originally Posted by sheikh.sami17
but i have locked bootloader. can i flash stock firmware with locked bootloader?
YES you can flash stock Moto roms meant for your model and carrier only.
Also, Never attempt to downgrade.
In this page
http://forum.xda-developers.com/moto-x/moto-x-qa/q-how-to-flash-to-stock-firmware-t3041813
I edit and made one firmware autoflasher for my x play Indian version and flashed successfully . everybody should check sparsechunk files no in flash file of your extracted stock firmware and edit my autoflasher files according to number of sparsechunk files and flash your firmware. It is definitely safe and I flashed my firmware by this but use at your own risk .
https://mega.nz/#!aoETEL7b!6WUe8tXeh...HHohpfYf2duoLc
First you have to download your phone's correct firmware and extract in fastboot folder , and add my autoflasher and check your sparsechunk files number and make changes according to that in autoflasher then save ..Enter your phone in fastboot mode or in bootloader and not in stock recovery and run autoflasher.
IF YOU HAVE ANY DOUBT AT TAKING RISK , CONTACT Motorola AND MAKE EVERYTHING EASY.
Click to expand...
Click to collapse
provide the decryption key

P9 Lite cannot flash stock firmware

I have a Huawei P9 lite. (VNS-L31 dual sim) . I tried to install medrom 3 and after flashing, phone didn't boot up. So I flashed b161 firmware again using 3 button method and phone booted up. Then I realized I couldn't add my google account. After searching on xda I found a method to fix that.(flashing oem info ). But after doing that, when the phone boots up after the huawei logo the error message which says "your device has been unlocked" has become red.( Usually it's yellow). And in about phone my model number has been changed to something like hi6250 or hi650.( Can't remember the exact thing). Then I tried to reflash my b161 firmware using 3 button menu and voila. It says incompatible version. I can't flash it. Then I replaced my build prop with my friend's phone's build prop. But unfortunately it has the B151 version. Though I have B161 version installed, my about phone says it has B151 version. And I can't flash stock firmware using twrp or dload method od any how. Please help
Nemeroz said:
I have a Huawei P9 lite. (VNS-L31 dual sim) . I tried to install medrom 3 and after flashing, phone didn't boot up. So I flashed b161 firmware again using 3 button method and phone booted up. Then I realized I couldn't add my google account. After searching on xda I found a method to fix that.(flashing oem info ). But after doing that, when the phone boots up after the huawei logo the error message which says "your device has been unlocked" has become red.( Usually it's yellow). And in about phone my model number has been changed to something like hi6250 or hi650.( Can't remember the exact thing). Then I tried to reflash my b161 firmware using 3 button menu and voila. It says incompatible version. I can't flash it. Then I replaced my build prop with my friend's phone's build prop. But unfortunately it has the B151 version. Though I have B161 version installed, my about phone says it has B151 version. And I can't flash stock firmware using twrp or dload method od any how. Please help
Click to expand...
Click to collapse
That's normal if the message is red, it means that the bootloader Will be relocked.
Now for the build prop, download b161 version, use huawei firmware extractor , extract boot.img system.img and cust.img
And by fastboot type :
fastboot flash system system.img
fastboot flash boot boot.img
fastboot flash cust cust.img
fastboot reboot
And voila, b161 is installed in your phone !
Sent from my HUAWEI VNS-L31 using XDA Labs
I can ont flash the boot.img. I get this error:
D:\Software_Tools\Multimedia\Handy-Taplet\Handy\Backup\161_entpackt>Fastboot flash boot boot.img
target reported max download size of 471859200 bytes
sending 'boot' (13998 KB)...
OKAY [ 0.300s]
writing 'boot'...
FAILED (remote: Command not allowed)
finished. total time: 0.322s
Schrotty35 said:
I can ont flash the boot.img. I get this error:
D:\Software_Tools\Multimedia\Handy-Taplet\Handy\Backup\161_entpackt>Fastboot flash boot boot.img
target reported max download size of 471859200 bytes
sending 'boot' (13998 KB)...
OKAY [ 0.300s]
writing 'boot'...
FAILED (remote: Command not allowed)
finished. total time: 0.322s
Click to expand...
Click to collapse
If fastboot say "FAILED (remote: Command not allowed)", its because your bootlaoder is locked, reunlock it !
In TWRP it says unable to mount Data :/
Ax3noX_ said:
If fastboot say "FAILED (remote: Command not allowed)", its because your bootlaoder is locked, reunlock it !
Click to expand...
Click to collapse
I noticed that in TWRP it says unable to mount data :/ What can i do now
I don't know what is "mount data", i cant help you with that ?
Ax3noX_ said:
I don't know what is "mount data", i cant help you with that
Click to expand...
Click to collapse
Its okay. Still looking for a help dude. Any help is highly appreciated :good:
Nemeroz said:
Its okay. Still looking for a help dude. Any help is highly appreciated :good:
Click to expand...
Click to collapse
Code:
fastboot oem unlock XXXXXX
fastboot flash recovery recovery_stock.img
Unable to read/mount data says your encryption key got changed by something, whatever. You need to Wipe Internal storage and flash twrp again ( I recomment matic`s ) Reboot to recovery again, if you got one, flash a flashable fw via twrp. I Dont know if the stock recovery Accepts a fully wiped intern storage, i guess not and it declines the update.app method.
In the best case for sure you recover an older backup to get the Same enc. Key back
WieserZ1C said:
Unable to read/mount data says your encryption key got changed by something, whatever. You need to Wipe Internal storage and flash twrp again ( I recomment matic`s ) Reboot to recovery again, if you got one, flash a flashable fw via twrp. I Dont know if the stock recovery Accepts a fully wiped intern storage, i guess not and it declines the update.app method.
In the best case for sure you recover an older backup to get the Same enc. Key back
Click to expand...
Click to collapse
Try to hold Vol+ and the power button and if you enter in Huawei recovery, select wipe data / Factory reset
Ax3noX_ said:
Try to hold Vol+ and the power button and if you enter in Huawei recovery, select wipe data / Factory reset
Click to expand...
Click to collapse
Tried that. But didnt work mate 😔
Nemeroz said:
Tried that. But didnt work mate 😔
Click to expand...
Click to collapse
Flash oeminfo (dowbload in the ultimate guide of nougat) and put the update.app of the marshmallow version in the dload folder then hold Vol+, vol- and power.
Its worked for me
Tell me if it work
(Sorry for my bad english, im french
I'd recommend using SP Flash tool. It's saved my ass multiple times.
Where you got the Scatter File for the p9 lite
Nantonix said:
I'd recommend using SP Flash tool. It's saved my ass multiple times.
Click to expand...
Click to collapse
Spflash tool is flash tool only for mtk devices... And p9 lite doesnt have a mtk soc !
---------- Post added at 08:47 PM ---------- Previous post was at 08:46 PM ----------
hanzox5 said:
Where you got the Scatter File for the p9 lite
Click to expand...
Click to collapse
It doesn't exist !
i wanted to convert the device to dual sim, so i tried to restore the backed-up partitions using meticulus' TWRP. But it says unable to mount /data every time i try to format it.
I know i made a big mistake, but that's how i learn..
this thread has worked for me
https://translate.google.co.uk/tran...m/showthread.php?t=1261335&edit-text=&act=url
Hello I went back the MN when startups is only then the logo after screen dark
please help me !!!
sorry for my english
pinhpongk said:
Hello I went back the MN when startups is only then the logo after screen dark
please help me !!!
sorry for my english
Click to expand...
Click to collapse
do a factory reset..if doesn work reflash stock marshmallow b160

MOTO X PLAY XT1562 Bricked

I accidentally bricked my xt1562 while attempting to flash a rom. I wiped the phone using twrp and when it rebooted it was stuck on the 'WARNING BOOTLOADER UNLOCKED' screen.
I attempted to flash the stock rom using adb but it shows the following error.
C:\Users\devya\Desktop\Fastboot+ADB\Win32>fastboot flash partition gpt.bin
sending 'partition' (32 KB)...
OKAY [ 0.005s]
writing 'partition'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.505s
PLEASE HELP!
can u paste the commands here to see them?
devyadav0399 said:
I accidentally bricked my xt1562 while attempting to flash a rom. I wiped the phone using twrp and when it rebooted it was stuck on the 'WARNING BOOTLOADER UNLOCKED' screen.
I attempted to flash the stock rom using adb but it shows the following error.
PLEASE HELP!
Click to expand...
Click to collapse
I'd advice you use the original image to flash for your country and device which was 5.1 via ADB following the steps described in the forum.
https://forum.xda-developers.com/mo...de-how-to-flash-factory-image-return-t3261486
Dio-Genes said:
I'd advice you use the original image to flash for your country and device which was 5.1 via ADB following the steps described in the forum.
https://forum.xda-developers.com/mo...de-how-to-flash-factory-image-return-t3261486
Click to expand...
Click to collapse
Thanks dude for the quick response. I'll get onto it.
if u flash the stock marshmallow firmware...u have to add sparsechunk 7,8 and 9 in the commands with the same way they appear...
bytheway...here is the latest with october patch yesterday new flashable rom zip...u only have to flash supersu after flashed rom.good luck.
https://forum.xda-developers.com/showthread.php?t=3533559
kos25k said:
if u flash the stock marshmallow firmware...u have to add sparsechunk 7,8 and 9 in the commands with the same way they appear...
bytheway...here is the latest with october patch yesterday new flashable rom zip...u only have to flash supersu after flashed rom.good luck.
https://forum.xda-developers.com/showthread.php?t=3533559
Click to expand...
Click to collapse
I tried that once before and got the same error message until I used the original firmware, 5.1 which was the one it was originally shipped with. That's why I gave that advice.
ok dude glad to hear.now from twrp i think u can flash latest MM flashable. (not sure through if u first have to flash 6.0 MM)

Screwed up phone while rolling back Android 7 - help?

So for some background, I was on EMUI 4.1 and successfully flashed to EMUI 5.
Then, I wanted to rollback so I flashed recovery again and stock firmware. I tried flashing with fastboot and didn't work. I tried using Huawei recovery 3-button method, no luck either.
Errors using fastboot flashing:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash system "F:\SYSTEM.img"
target reported max download size of 471859200 bytes
sending sparse 'system' 1/6 (445721 KB)...
OKAY [ 17.780s]
writing 'system' 1/6...
FAILED (remote: sparse flash write failure)
finished. total time: 17.822s
Click to expand...
Click to collapse
Error with 3-button method:
Software install failed!
Incompatibility with current version.
Please download the correct update package.
Click to expand...
Click to collapse
When I was booting into Revolution recovery, I could not mount SD card and some other partitions so maybe that has something to do with the 3-button method problem... Furthermore, I don't know how to check which version exactly my phone is, all I know is that it was VNS-L31.
Now I'm stuck with a phone that is constantly rebooting so how do I proceed?
First of all...
Please tell me you have a backup of your Nougat ROM. If yes, restore it.
I have failed to go back to MM several times like you before.
It really is a question of using the right files.
First, flash the OEMInfo that is provided here in the forums.
Second, flash the right firmware. This one is tricky. For me, ONLY VNS-L31 Version C150 worked. No other.
Flashing with fastboot always never works. It always gives an error on system. So you need to find a firmware that works with 3-button method.
Your task now is the get back to working Nougat, since you did something wrong.
Unlock BL, flash Nougat recovery with fastboot.
Then,
easiest is like I said restoring a backup.
If you don't have one, try flashing the Revolution ROM by BadWolf.
Schlengge said:
First of all...
Please tell me you have a backup of your Nougat ROM. If yes, restore it.
I have failed to go back to MM several times like you before.
It really is a question of using the right files.
First, flash the OEMInfo that is provided here in the forums.
Second, flash the right firmware. This one is tricky. For me, ONLY VNS-L31 Version C150 worked. No other.
Flashing with fastboot always never works. It always gives an error on system. So you need to find a firmware that works with 3-button method.
Your task now is the get back to working Nougat, since you did something wrong.
Unlock BL, flash Nougat recovery with fastboot.
Then,
easiest is like I said restoring a backup.
If you don't have one, try flashing the Revolution ROM by BadWolf.
Click to expand...
Click to collapse
Have just solved the problem with the steps from here.
From my understanding, it seems that I lost almost everything, device info, OEM info, recovery... So no technique was working.
The solution in brief was:
1. Go into bootloader to flash recovery (I used Revolution Recovery)
2. In recovery, flash OEM info.
3. Then used the 3-button method to install stock version for the appropriate model (which I could see from OEM info).
4. Unlocked bootloader, triggering a factory reset. (I was stuck in infinite boot before this point.)
As you say Schlengge, it is a matter of using the right files! Thanks. Problem solved.

Moto Z 8.0 Full firmware [stock][oreo][griffin]

Many thank @erfanoabdi for the link
https://androidfilehost.com/?fid=890278863836283516
extract ROM ,extract file attack ,put all to the same folder, (hold power + volume down to get into bootloader mode) and run file: retail_AS_800.bat ( no need to run commands)
Done.
Hey, thanks for the tool, just few questions, will this relock my device bootloader ? and am i taking the risk to hard brick it ? Do i need to have adb and fastboot installed ?
thanks for this tool and for your time
K1li4n said:
Hey, thanks for the tool, just few questions, will this relock my device bootloader ? and am i taking the risk to hard brick it ? Do i need to have adb and fastboot installed ?
thanks for this tool and for your time
Click to expand...
Click to collapse
No relock anything. No risk to hard brick. If you flash down to 711 and then OTA update,it will. No need adb and fastboot install. Install usb and motorola driver
thanks for the quick answer. no relock, so if something go wrong i would still be able to flash some custom and rsolve the issue , right ?
thuybang said:
Many thank @erfanoabdi for the link
https://androidfilehost.com/?fid=890278863836283516
extract ROM ,extract file attack ,put all to the same folder, (hold power + volume down to get into bootloader mode) and run file: retail_AS_800.bat ( no need to run commands)
Done.
Click to expand...
Click to collapse
Hi, at the end of the batch say
fastboot erase carrier
fastboot erase cache
fastboot erase userdata
fastboot erase DDR
So all data will be erased ?
BTW, I ran the process and the phone went back to encrypted mode again, TWRP is not working any more and root access is gone..Any way to revert back ?
K1li4n said:
thanks for the quick answer. no relock, so if something go wrong i would still be able to flash some custom and rsolve the issue , right ?
Click to expand...
Click to collapse
Yes,sure.
[email protected] said:
Hi, at the end of the batch say
fastboot erase carrier
fastboot erase cache
fastboot erase userdata
fastboot erase DDR
So all data will be erased ?
BTW, I ran the process and th phone went back to encrypted mode again
Click to expand...
Click to collapse
Yes,it will erese all.
thuybang said:
Yes,it will erese all.
Click to expand...
Click to collapse
And we lose custom recovery and root asscess
my phone reteu dual sim not retail can i flash this rom ?
t_assal said:
my phone reteu dual sim not retail can i flash this rom ?
Click to expand...
Click to collapse
If you unlockbootloader, i can say : yes.
Nice it works to me ,
I just wanted to know if now im stock with unlocked bootloader , so no updates ? Like security updates ?
lima002 said:
Nice it works to me ,
I just wanted to know if now im stock with unlocked bootloader , so no updates ? Like security updates ?
Click to expand...
Click to collapse
Unlock bootloader always get update as normal,guy. . Any update, security,system....
thuybang said:
Unlock bootloader always get update as normal,guy. . Any update, security,system....
Click to expand...
Click to collapse
Cool thanks
Thanx for this, updates working and all.. Only the wifi seems to be be working bad (no internet access, disconnecting) , although could be my connection..
Hi, can I flash 1650-05 retcn Android 7.0 with an unlocked bootloader on this firmware?
it should work on xt1650-03?
btw, my carrier is tefcl but i think that isn't important for flashing
thuybang said:
Many thank @erfanoabdi for the link
https://androidfilehost.com/?fid=890278863836283516
extract ROM ,extract file attack ,put all to the same folder, (hold power + volume down to get into bootloader mode) and run file: retail_AS_800.bat ( no need to run commands)
Done.
Click to expand...
Click to collapse
I try to flash it, but where is error on system.img_sparsechunk.14 flashing..
C:\adb-fastboot-latest\adb-fastboot-latest>fastboot flash system system.img_spar
sechunk.14
target reported max download size of 536870912 bytes
sending 'system' (151532 KB)...
OKAY [ 4.038s]
writing 'system'...
(bootloader) Invalid sparse image data
(bootloader) Failed to flash sparse image
FAILED (remote failure)
finished. total time: 4.786s
Click to expand...
Click to collapse
And error on erasing DDR
C:\adb-fastboot-latest\adb-fastboot-latest>fastboot erase DDR
erasing 'DDR'...
(bootloader) Permission denied
FAILED (remote failure)
finished. total time: 0.035s
Click to expand...
Click to collapse
Phone now in boot loop. Can't start, but goes to fastboot.
How to flash it correctly.
mike331967 said:
I try to flash it, but where is error on system.img_sparsechunk.14 flashing..
And error on erasing DDR
Phone now in boot loop. Can't start, but goes to fastboot.
How to flash it correctly.
Click to expand...
Click to collapse
Can you try flash by RSD lite 6.2.4sofware?
thuybang said:
Unlock bootloader always get update as normal,guy. . Any update, security,system....
Click to expand...
Click to collapse
i got notification about security update (patch may 2018) but error while instaling. any solution? please help.
Ceptoz said:
i got notification about security update (patch may 2018) but error while instaling. any solution? please help.
Click to expand...
Click to collapse
Same here.
Help!

Categories

Resources