Database Develop

Help with moto x

I tried to manually flash back to stock 4.4.2 (so I can upgrade to 4.4.3) on my moto x but whenever I type the command "mfastboot flash system system.img" I get "invalid sparse image chunk count. The rest of the commands worked. Now my phone is stuck in the unlocked bootloader screen and I don't know what else to do. Help please?

Try the latest mfastboot see if it helps
Sent from my XT1053 using XDA Free mobile app

serophia said:
Try the latest mfastboot see if it helps
Sent from my XT1053 using XDA Free mobile app
Click to expand...
Click to collapse
Where would I get the latest version?

http://mark.cdmaforums.com/X-STUFF/mfastboot-442.zip

KidJoe said:
http://mark.cdmaforums.com/X-STUFF/mfastboot-442.zip
Click to expand...
Click to collapse
Thanks for the link. I used it and I still got the same error.

Make sure you are using the system.img from the correct firmware. Below is a link to the Moto model firmwares. Download the right one, unzip the files until you get to the .img files and use that system.img.
Motorola Firmwares

I've used different zip extractors and it always says the system.img file is broken. =O!
Thanks for the help guys! Appreciated

n0obpr0 said:
I've used different zip extractors and it always says the system.img file is broken. =O!
Thanks for the help guys! Appreciated
Click to expand...
Click to collapse
Try the steps listed in this post:
http://forum.xda-developers.com/showpost.php?p=53228057&postcount=148
Basically, the idea here is to flash gpt (partition) and motoboot ONLY, then reboot back into bootloader. Then it should allow you to flash the rest of the items without error. Let us know if it works for you.

samwathegreat said:
Try the steps listed in this post:
http://forum.xda-developers.com/showpost.php?p=53228057&postcount=148
Basically, the idea here is to flash gpt (partition) and motoboot ONLY, then reboot back into bootloader. Then it should allow you to flash the rest of the items without error. Let us know if it works for you.
Click to expand...
Click to collapse
I followed the steps but I still get the same error. In CMD window I get:
mfastboot flash system system.img
(bootloader) Variable not supported!
target max-download-size: 768MB
sending 'system' (57163 KB)...
OKAY [ 3.868s]
writing 'system'...
(bootloader) Sparse image is malformatted
FAILED (remote failure)
finished. total time: 6.680s

n0obpr0 said:
I followed the steps but I still get the same error. In CMD window I get:
mfastboot flash system system.img
(bootloader) Variable not supported!
target max-download-size: 768MB
sending 'system' (57163 KB)...
OKAY [ 3.868s]
writing 'system'...
(bootloader) Sparse image is malformatted
FAILED (remote failure)
finished. total time: 6.680s
Click to expand...
Click to collapse
And we have your answer. 57MB is WAY too small for a system partition....it is indeed 'malformatted'/corrupt.
Two possibilities:
1. Either your download of the SBF somehow got corrupted. If so, re-download the entire SBF, and do the steps in the post I linked.
2. You are trying to flash the system.img from the OTA for some reason?? The images contained in the official OTA don't contain the entire system - just an incremental update to the existing system. If this is the case, ditch that idea, and download the official SBF from here:
http://sbf.droid-developers.org/phone.php?device=0

samwathegreat said:
And we have your answer. 57MB is WAY too small for a system partition....it is indeed 'malformatted'/corrupt.
Two possibilities:
1. Either your download of the SBF somehow got corrupted. If so, re-download the entire SBF, and do the steps in the post I linked.
2. You are trying to flash the system.img from the OTA for some reason?? The images contained in the official OTA don't contain the entire system - just an incremental update to the existing system. If this is the case, ditch that idea, and download the official SBF from here:
http://sbf.droid-developers.org/phone.php?device=0
Click to expand...
Click to collapse
That's what I thought. I actually downloaded the SBF from the link you provided. When I open the zip file, system.img is 873,450,540. I'm gonna download it from my laptop.
Edit: Thank you!!! I downloaded the file in my laptop and extracted the file and I had the right size this time. I flashed it and it worked =) Thank you everybody! Y'all made my day =)

n0obpr0 said:
That's what I thought. I actually downloaded the SBF from the link you provided. When I open the zip file, system.img is 873,450,540. I'm gonna download it from my laptop.
Edit: Thank you!!! I downloaded the file in my laptop and extracted the file and I had the right size this time. I flashed it and it worked =) Thank you everybody! Y'all made my day =)
Click to expand...
Click to collapse
That's what were here for to help others xD
Sent from my XT1053 using XDA Free mobile app

[GUIDE] Back to Stock ROM (the sure method)

Hello everybody, for serveral months i saw several people asking help to back to stock ROM
here we finally have a guide that saved me and can save you!
Requirements:
Windows operative system
Multi Tool
OFFICIAL stock rom (in this guide i'll use B370 for H60-L04) Download
and the most important thing Huawei Update Extractor! Download
and let's go!
First of all open HUE (Huawei Update Extractor) and after selected UPDATE.APP file, extract system.img , boot.img , cust.img, recovery.img that we will flash on the phone, and put them in the folder where adb and fastboot are installed (in this case we use the multi tool directory).
now open cmd or command prompt and move on multi tool directory (cd C:\\Users\NAME bla bla bla\DIRECTORY TO MULTI TOOL)
now plug in your phone and enable Debug USB and type:
Code:
adb.exe devices (to control if your device is online, if not grant the permission on the phone)
adb.exe reboot bootloader
Now we flash all the files with fastboot
the order of commands doesn't matter
(MAKE SURE THAT YOU HAVE SYSTEM, BOOT, RECOVERY AND CUST .img ON THE MAIN FOLDER!)
Code:
fastboot.exe flash boot BOOT.img
fastboot.exe flash recovery RECOVERY.img
fastboot.exe flash cust CUST.img
fastboot.exe flash system SYSTEM.img
than reboot into recovery by doing
fastboot.exe reboot and holding only VOLUME UP button
than do all the wipe (cache and data) than reboot system
Easy right? :laugh:

TheTigerDeveloper said:
Hello everybody, for serveral months i saw several people asking help to back to stock ROM
here we finally have a guide that saved me and can save you!
Requirements:
Windows operative system
Multi Tool
OFFICIAL stock rom (in this guide i'll use B370 for H60-L04) Download
and the most important thing Huawei Update Extractor! Download
and let's go!
First of all open HUE (Huawei Update Extractor) and after selected UPDATE.APP file, extract system.img , boot.img , cust.img, recovery.img that we will flash on the phone, and put them in the folder where adb and fastboot are installed (in this case we use the multi tool directory).
now open cmd or command prompt and move on multi tool directory (cd C:\\Users\NAME bla bla bla\DIRECTORY TO MULTI TOOL)
now plug in your phone and enable Debug USB and type:
Code:
adb.exe devices (to control if your device is online, if not grant the permission on the phone)
adb.exe reboot bootloader
Now we flash all the files with fastboot
the order of commands doesn't matter
(MAKE SURE THAT YOU HAVE SYSTEM, BOOT, RECOVERY AND CUST .img ON THE MAIN FOLDER!)
Code:
fastboot.exe flash boot BOOT.img
fastboot.exe flash recovery RECOVERY.img
fastboot.exe flash cust CUST.img
fastboot.exe flash system SYSTEM.img
than reboot into recovery by doing
fastboot.exe reboot and holding only VOLUME UP button
than do all the wipe (cache and data) than reboot system
Easy right? :laugh:
Click to expand...
Click to collapse
Thanks for the guide! I used to follow the same procedure too but another alternative is to use multi-tool and use the unbrick option and follow the instructions. It super noob friendly:highfive:

shubham1120 said:
Thanks for the guide! I used to follow the same procedure too but another alternative is to use multi-tool and use the unbrick option and follow the instructions. It super noob friendly:highfive:
Click to expand...
Click to collapse
i know, but with this one any type of user can follow the guide (especially linux user)

my phone keep restarting, i have try this method, no works, helpppppppp
it stuck on honor logo

Hi Guys,
i got the same problem here with my H60-L12
After flashing Beta Lollipop 5.1.1 i tried to go back to 4.4.4.
Now it's stuck in bootloop and now it keeps flashing the honor logo.
Tried to unbrick it with Multi-Tool and different stock roms but i cant get into recovery or the 3 button install method, only thing working is fastboot mode.
Any suggestions?
Thank you!!

ok, now i'm desperate.
Got different Stock Roms (4.4 5.8.1;4.4 B119;4.4 B310; 4.4 B316, tried TWRP in different versions, even tried to reinstall fastboot drivers , same problem on Windows 10 and 7.
Only think working is Fastboot&Rescue Mode (White Screen, Phone UNLOCKED), but only when plugged in on PC with USB cable.
When plugged in charger, it just reboots and reboots i can't switch to Recovery or Fastboot mode and doesn't even charge the phone.
Maybe someone got any idea, did i use wrong stock roms? Do i have to use Rollback/Revert versions?

Any way to back to stock rom without unlock bootloader?

I've made a horrible mistake.
I was on 5.9.16, tried to downgrade by flashing system, recovery, cust and crc.
Unfortunately I've done it with B316, which is 4.4.4, so i got this annoying bootloop, in which i can't access recovery, bootloader or use the 3 buttons method.
It seems as if the phone tries to forcefully boot into system ignoring everything I do.
I tried draining the battery to turn it off, which worked, but when i charged it it tried to system boot as soon as there's enough battery.
Any ideas?

and where can I find update.app?

This worked for me! I switched from CM11 to the stable 5.1.1 release using your guide. Flashed B370 and then did a local update for the stable lollipop rom. Thanks a ton.

i need help
I extract listed file and open cmd.
I was able to reboot into bootloader.
I writing "fastboot.exe flash boot BOOT.img" and here is the result:
target reported max download size of 471859200 bytes
sending 'boot' (7754 KB)...
OKAY [ 0.810s]
writing 'boot'...
FAILED (remote: Command not allowed)
finished. total time: 0.820s
Whats now?
I have rooted H60-L04 with cyanogenmod 11-20150822 KitKat
Thanks
Michal

yeah, very easy guide
i did to my H60-L04 CM11
thanks for sharing

error
target reported max download size of 471859200 bytes
sending 'boot' (7754 KB)...
OKAY [ 0.810s]
writing 'boot'...
FAILED (remote: Command not allowed)
finished. total time: 0.820s

i couldnot flash stock recovery because of the fail command not alowed,

i couldnot flash stock recovery because of the fail command not alowed,

Thank you so much! Now my phone is bricked... How about not sharing ur help when u don't know what could happen?

My phone shows Rescue Mode
Attention! Please update system again!
Error!
FuncNo (FUNC_BOOT_KERNEL)
Error NO: 2

i couldnot flash stock recovery because of the fail command not alowed,

i couldnot flash stock recovery because of the fail command not alowed,

thalaraj1992 said:
i couldnot flash stock recovery because of the fail command not alowed,
Click to expand...
Click to collapse
are you on a boot loop?
make sure your device is recognized by your computer.
download universal-adb-driver for windows and install

Flashing 5.1 to XT1053 not working

I have requested the stock 5.1 file from motorola and it comes with everything to flash it on the phone via fastboot which also comes in the file. I know what im doing but for some reason everytime i get to flashing the system file it says this?
$ fastboot flash system system.img
sending 'system' (1404896 KB)...
(bootloader) Data size exceeds download buffer
FAILED (remote failure)
Does anybody have a clue i cant get a system img on my phone and I kinda need my phone

Shafty6 said:
I have requested the stock 5.1 file from motorola and it comes with everything to flash it on the phone via fastboot which also comes in the file. I know what im doing but for some reason everytime i get to flashing the system file it says this?
$ fastboot flash system system.img
sending 'system' (1404896 KB)...
(bootloader) Data size exceeds download buffer
FAILED (remote failure)
Does anybody have a clue i cant get a system img on my phone and I kinda need my phone
Click to expand...
Click to collapse
have you tried mfastboot, its modified version of fastboot for larger files
Download mfastboot-v2.zip

hugh a said:
have you tried mfastboot, its modified version of fastboot for larger files
Download mfastboot-v2.zip
Click to expand...
Click to collapse
When I requested the system image for 5.1 it came with fastboot in it everything is from motorola. Why would they not include a fastboot that can load a file that large?
Also i got the mfastboot v2 and it would not work as a fastboot, then i renamed it as fastboot and still will not load the system.img

Shafty6 said:
When I requested the system image for 5.1 it came with fastboot in it everything is from motorola. Why would they not include a fastboot that can load a file that large?
Also i got the mfastboot v2 and it would not work as a fastboot, then i renamed it as fastboot and still will not load the system.img
Click to expand...
Click to collapse
Make sure that the fastboot which is running is the one included with the moto download, and not the one from the Android SDK...
In other words, for Windows PC's, if the Android SDK Platform Tools folder is in the path, often its fastboot will be used instead of the one included in the moto download.
Try renaming the one which came in the moto download as mfastboot.exe, and running it that way, by typing mfastboot.....

KidJoe said:
Make sure that the fastboot which is running is the one included with the moto download, and not the one from the Android SDK...
In other words, for Windows PC's, if the Android SDK Platform Tools folder is in the path, often its fastboot will be used instead of the one included in the moto download.
Try renaming the one which came in the moto download as mfastboot.exe, and running it that way, by typing mfastboot.....
Click to expand...
Click to collapse
Im using mac because its much easier than windows, and ive used the fastboot that comes with everything to fast and everything works perfect till I try system.img

how to get NVME file (bootloader code) unofficially

If uou dont know what you are doing,dont ask me
i will try to explain as far as i can.but dont ask stupid questions
-------------- Responsibility for your bricks I do not take over. Everyone does at their own peril and risk .--------------
Click to expand...
Click to collapse
Download this
1) Install the driver for the phone (download);
2) Install a special driver, find it in the Unlock_BootLoader \ Driver for Winwos \ DriverSetup.exe folder;
3) It is necessary to unwind the phone, remove the cover;
4) Open application and press start
5) Test point and connect the phone
6) it will start flashing then stop the proces in betwin the flash
7) wait for 30 sec your device will be in temporary unlocked bootloader mode
8) then flash TWRP (link ) by this command
Code:
fastboot flash recovery_ramdisk XXXXX.img
fastboot flash erecovery_ramdisk xxxxx.img
9) Done. Now you have TWRP_Mod installed in the Recovery section.
10) Then within twrp open adb connect phone to pc
11)type
Code:
adb shell
rm data -r
12)restart device
13) then type
Code:
adb pull /dev/block/sdd4
14) alternatively you can take nvme backup from twrp if u can extract that
you have the NVME file
Reference of nvme

Code: JH3KZQA0XD7G2KOZ
File from unlocked by the code phone is attached
Now somebody should look through binary code I guess trying to find the code or something pattern

S0bes said:
Code: JH3KZQA0XD7G2KOZ
File from unlocked by the code phone is attached
Now somebody should look through binary code I guess trying to find the code or something pattern
Click to expand...
Click to collapse
Remove the attachment. Dont nake it public. Its harmful
Check the refence try if that work

rajit said:
Remove the attachment. Dont nake it public. Its harmful
Is this twrp backup? Or u pulled via adb?
Click to expand...
Click to collapse
It's not mine and have been already published on 4pda for someone to find the spot in img file
I don't know how it had been pulled. I guess the person bought the code, unlocked the phone and made twrp backup

S0bes said:
Code: JH3KZQA0XD7G2KOZ
File from unlocked by the code phone is attached
Now somebody should look through binary code I guess trying to find the code or something pattern
Click to expand...
Click to collapse
An idea: How about backing up your nvme, then flashing this nvme and unlock the bootloader using this code, then restoring your backup

mehdi554 said:
An idea: How about backing up your nvme, then flashing this nvme and unlock the bootloader using this code, then restoring your backup
Click to expand...
Click to collapse
The img has been taken from another huawei device. not honor play

@rajit have you tried to force unlock boot? Without code just editing nvme file?
https://forum.xda-developers.com/9-lite/how-to/unlock-bootloader-code-t3859685 - step 5

please help me !
please help me !
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash recovery_ramdisk TWRP_Mod.img
target reported max download size of 471859200 bytes
sending 'recovery_ramdisk' (23542 KB)...
OKAY [ 0.700s]
writing 'recovery_ramdisk'...
FAILED (remote: Command not allowed)
finished. total time: 0.712s

Where is the test point?
And can i flash magisk file after unlocked bootloader temporar?

mohad2399 said:
please help me !
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash recovery_ramdisk TWRP_Mod.img
target reported max download size of 471859200 bytes
sending 'recovery_ramdisk' (23542 KB)...
OKAY [ 0.700s]
writing 'recovery_ramdisk'...
FAILED (remote: Command not allowed)
finished. total time: 0.712s
Click to expand...
Click to collapse
Do you connect the test point??

What's the point of unlocking bootloader if there aren't custom rom for this device yet

devilyuri said:
What's the point of unlocking bootloader if there aren't custom rom for this device yet
Click to expand...
Click to collapse
Custom rom isnt issue if you know how to what! Besides who asked you to take some interest here??
You can ignore! :fingers-crossed:

then how did this end? anyone managed to root using nvme honor play COR-L29 EMUI 9.1 ????

rajit said:
If uou dont know what you are doing,dont ask me
i will try to explain as far as i can.but dont ask stupid questions
Download this
1) Install the driver for the phone (download);
2) Install a special driver, find it in the Unlock_BootLoader \ Driver for Winwos \ DriverSetup.exe folder;
3) It is necessary to unwind the phone, remove the cover;
4) Open application and press start
5) Test point and connect the phone
6) it will start flashing then stop the proces in betwin the flash
7) wait for 30 sec your device will be in temporary unlocked bootloader mode
8) then flash TWRP (link ) by this command
9) Done. Now you have TWRP_Mod installed in the Recovery section.
10) Then within twrp open adb connect phone to pc
11)type
12)restart device
13) then type
14) alternatively you can take nvme backup from twrp if u can extract that
you have the NVME file
Reference of nvme
Click to expand...
Click to collapse
This is really work ?

[/COLOR]
Neverhopless said:
This is really work ?
Click to expand...
Click to collapse
It works but there's no code inside nvme

This method works on Emui 9 ?

What do you mean by "Unwind the phone"?

I have made a simple windows program to help parse a file to possibly find an unlock code.
You simply put exe with the file in the same dirrectory and run.
The program will ask for the file name to parse and then will show any character sequences that follow the pattern rules:
*Length >=16
* A-Z, a-z, 0-9 symbols
See pic example
In case of missing MSVCR120.dll error install https://www.microsoft.com/en-US/download/details.aspx?id=40784
.cpp file is just a source code

Can you fix the tools ?. Google Drive is not available

Link not working

cant patch Zip file.

Hi,
When I download I cant find it on my downloads. I have to go into my files app then I can find the zip there. And when I try patch it, it says "unknown image format". Therefore the installation fails.
How can I fix this. I also haven't been able to install TWRP.
thanks

What zip file? Do you mean the Magisk installation zip? You can't use that unless you're already rooted (and then you need to install it from the modules section of the Manager) or through TWRP. But if you're already rooted it's easier to just do a direct install from the Manager anyway.
The patch file option in the Manager is for a boot or recovery image (depending on what device you have, see the installation instructions).

twrp
thanks for your reply.
Im also having trouble with installing twrp. I have unlocked the bootloader on my huawei p8 lite 2017 and have downloaded all the tools and flash img needed to flash it. However when use command " fastboot flash recovery twrp-3.4.0-0-prague.img" it says:
Sending 'recovery' (13458 KB) OKAY [ 0.532s]
Writing 'recovery' OKAY [ 0.340s]
Finished. Total time: 0.909s
then when I use " fastboot boot twrp-3.4.0-0-prague.img" it says
Sending 'boot.img' (13458 KB) OKAY [ 0.500s]
Booting FAILED (remote: 'Command not allowed')
fastboot: error: Command failed
How can i fix this. Thanks in advance.

The recovery seems to have installed correctly, so instead of running the command to boot the image, try just using the option directly in the bootloader (usually navigated to by using the volume keys) to boot into recovery.

Didgeridoohan said:
The recovery seems to have installed correctly, so instead of running the command to boot the image, try just using the option directly in the bootloader (usually navigated to by using the volume keys) to boot into recovery.
Click to expand...
Click to collapse
Hi,
When i boot into recover I get another error which is as follows:
ERROR MODE
ATTENTION!
PLEASE UPDATE SYSTEM AGAIN
(Green android bot image)
ERROR!
Func NO : 11 (recovery image)
Error NO : 2(load failed!)
Thanks

You need to take this to your device's forum. That's the best way to get help with stuff like this...
Judging by this thread, you're using the wrong command:
https://forum.xda-developers.com/p8...nt/recovery-twrp-huawei-p8-lite-2017-t4113153