Database Users

[Q] XT905 can't flash rom (system)

Hi all!
Tried to unstall Ubuntu Touch and failed
I have Ubuntu 13.10 desktop, so I use android-tools-adb android-tools-fastboot from ppahablet-team/tools
While trying to install Ubuntu touch I f* up boot, recovery and system partitions
Code:
fastboot flash recovery saucy-preinstalled-recovery-armel+grouper.img
fastboot flash boot saucy-preinstalled-boot-armhf+grouper.img
fastboot flash system saucy-preinstalled-system-armel+grouper.img
I've found 98.21.7.XT905.Retail.en.AU zip-file and flashed boot_signed and recovery_signed. Recovery mode started working after that.
But the large file such as system_signed fails to flash with
Invalid sparse file format at header magi (if fastboot is used)
or
writing 'system'... INFOProtocol error (if moto-fastboot is used)
My attempt to use recovery mode (stock or CWM) failed too.
CWM says:
Can't partition non-vfat: datamedia
Can't format unknown volume: /emmc
Any ideas?

nonneg said:
Hi all!
Tried to unstall Ubuntu Touch and failed
I have Ubuntu 13.10 desktop, so I use android-tools-adb android-tools-fastboot from ppahablet-team/tools
While trying to install Ubuntu touch I f* up boot, recovery and system partitions
Code:
fastboot flash recovery saucy-preinstalled-recovery-armel+grouper.img
fastboot flash boot saucy-preinstalled-boot-armhf+grouper.img
fastboot flash system saucy-preinstalled-system-armel+grouper.img
I've found 98.21.7.XT905.Retail.en.AU zip-file and flashed boot_signed and recovery_signed. Recovery mode started working after that.
But the large file such as system_signed fails to flash with
Invalid sparse file format at header magi (if fastboot is used)
or
writing 'system'... INFOProtocol error (if moto-fastboot is used)
My attempt to use recovery mode (stock or CWM) failed too.
CWM says:
Can't partition non-vfat: datamedia
Can't format unknown volume: /emmc
Any ideas?
Click to expand...
Click to collapse
I cannot tell what you need to do but I may be able to tell what you may have done wrong if you post much more info.
Your eventual savior may need it.
The about phone data & such.
I guess you cannot use RSD lite.

Solved
I've found in my junk-box a half-alive notebook with WinXp, then istalled
RSDLite 6.1.5
Motorola_End_User_Driver_Installation_6.2.0.msi
and flashed this ROM via homemade factory cable:
9.8.2Q_SMUIRD-7_SEMEAUnlk_USAXT90501TLSTRAE1019.0R_SMJBLTEAURETAIL_P008_A014_S1FF_fb.xml
Everything okay now :good:
Guess Motorola has some proprietary issues with fastboot, so linux programs doesn't work properly.

Unable to format in TWRP

When I try to wipe internal it says
Code:
Wiping internal storage -- /data/media...
Error opening: '/data/media' (No such file or directory)
When I try to format instead - I get even more errors:
Code:
Formatting Data using make_ext4fs...
Failed to mount '/data' (Device or resource busy)
Failed to mount '/data' (Device or resource busy)
Unable to recreate /data/media folder.
You may need to reboot recovery to be able to use /data again.
Updating partition details...
Failed to mount '/data' (Device or resource busy)
...done
Is this because of encryption? And if so - this is weird because I never encrypted my device. I currently have no OS and just trying to unsoftbrick my phone.

specialk00 said:
...Is this because of encryption? And if so - this is weird because I never encrypted my device. I currently have no OS and just trying to unsoftbrick my phone.
Click to expand...
Click to collapse
Use fastboot and make sure you are using the latest binaries. Format system, userdata and cache. Upon booting for the first time, the 6P automatically defaults to encryption- unless you intervene and stop it from doing so.

v12xke said:
Use fastboot and make sure you are using the latest binaries. Format system, userdata and cache. Upon booting for the first time, the 6P automatically defaults to encryption- unless you intervene and stop it from doing so.
Click to expand...
Click to collapse
Yep, I just fixed it somehow, I think it was related to MTP in TWRP. However now I'm stuck with a different issue. No matter what I flash in fastboot - I get
Code:
C:\Users\Nexusflip\AppData\Local\Android\sdk\platform-tools>fastboot flash recovery D:\Downloads\angler\twrp-3.1.1-0-angler.img
target didn't report max-download-size
sending 'recovery' (16948 KB)...
FAILED (command write failed (No error))
finished. total time: 0.003s
I always get this weird "No error" thing.

specialk00 said:
Yep, I just fixed it somehow, I think it was related to MTP in TWRP. However now I'm stuck with a different issue. No matter what I flash in fastboot - I get
Click to expand...
Click to collapse
Are you sure you are using the latest binaries? Hash checked the TWRP file? Put TWRP img in your fastboot folder? Format/erase recovery partition?

v12xke said:
Are you sure you are using the latest binaries? Hash checked the TWRP file? Put TWRP img in your fastboot folder? Format/erase recovery partition?
Click to expand...
Click to collapse
Yes I'm using the latest binaries - I got them via Android SDK and updated everything. I checked the ones you linked and they are exactly the same.
Regarding the hash check - this has nothing to do with the file being corrupted. This happens with ANY file I try to flash.
I tried putting the TWRP img in my fastboot folder and the results are the same.
Erasing the recovery partition gives the same error.
Code:
C:\Users\username\AppData\Local\Android\sdk\platform-tools>fastboot erase recovery
erasing 'recovery'...
FAILED (command write failed (No error))
finished. total time: 0.009s

specialk00 said:
Yes I'm using the latest binaries - I got them via Android SDK and updated everything. I checked the ones you linked and they are exactly the same. Regarding the hash check - this has nothing to do with the file being corrupted. This happens with ANY file I try to flash. I tried putting the TWRP img in my fastboot folder and the results are the same. Erasing the recovery partition gives the same error.
Click to expand...
Click to collapse
Were you able to successfully fastboot format userdata, system and cache with no errors? Did you get the same error using format as you did erase recovery? Is your phone bootlooping ? If yes, then your phone may have the BLOD. There are a few instances of users still having access to recovery mode, but not being able to flash anything. If you flash a full stock image with flash-all.bat, it finishes but the phone still loops then you likely have the BLOD.

v12xke said:
Were you able to successfully fastboot format userdata, system and cache with no errors? Did you get the same error using format as you did erase recovery? Is your phone bootlooping ? If yes, then your phone may have the BLOD. There are a few instances of users still having access to recovery mode, but not being able to flash anything. If you flash a full stock image with flash-all.bat, it finishes but the phone still loops then you likely have the BLOD.
Click to expand...
Click to collapse
I tried minimal adb & fastboot (bit older version) and got this.
Code:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash recovery twrp-3.1.1-0-angler.img
target didn't report max-download-size
sending 'recovery' (16948 KB)...
FAILED (command write failed (Unknown error))
finished. total time: 0.007s
Then I tried another old version of fastboot - got one from july 2016 (23.0.1) and nothing happened when executing flash or format commands.
Then I tried normal, latest fastboot and both (new & old) versions of fastboot gave me this error.
Code:
C:\Users\Nexusflip\AppData\Local\Android\sdk\platform-tools>fastboot erase userdata
erasing 'userdata'...
FAILED (command write failed (No error))
finished. total time: 0.023s
Then I tried to format (instead of erase)
Code:
C:\Users\Nexusflip\AppData\Local\Android\sdk\platform-tools>fastboot format userdata
FAILED (command write failed (No error))
I don't know if my phone is bootlooping because I don't have OS installed and my internal storage is squeaky clean. All this crap didn't just start out of nowhere - I flashed 8.0.0 dev preview 2 images through TWRP. I know I'm not the brightest. When I launch flash-all.bat it's just blank and does nothing at all.

specialk00 said:
I don't know if my phone is bootlooping because I don't have OS installed and my internal storage is squeaky clean. All this crap didn't just start out of nowhere - I flashed 8.0.0 dev preview 2 images through TWRP. I know I'm not the brightest. When I launch flash-all.bat it's just blank and does nothing at all.
Click to expand...
Click to collapse
It sounds to me like your internal storage (memory) is bad. Bottom line is that if you can't format your basic partitions successfully, you will not be able to flash a full ROM. If you don't believe your memory is bad, you can search the 6P forums for the Qualcomm Flash Image Loader (QFIL) & EDL mode. There is a rescue binary for the 6P floating around that some people have been successful in using restoring corrupt partitions, presumably because it works at the hardware level.

v12xke said:
It sounds to me like your internal storage (memory) is bad. Bottom line is that if you can't format your basic partitions successfully, you will not be able to flash a full ROM. If you don't believe your memory is bad, you can search the 6P forums for the Qualcomm Flash Image Loader (QFIL) & EDL mode. There is a rescue binary for the 6P floating around that some people have been successful in using restoring corrupt partitions, presumably because it works at the hardware level.
Click to expand...
Click to collapse
What should I do from now on? I have no idea what to do. The device has been bricked for 24 hours now.
This is the closest I've found to my problem. Also on a Nexus 6P. https://forum.xda-developers.com/nexus-6p/help/zip-file-signature-verification-error-t3561054
I tried adb reboot edl and it says error: closed. So not even that works.

specialk00 said:
What should I do from now on? I have no idea what to do. The device has been bricked for 24 hours now. This is the closest I've found to my problem. Also on a Nexus 6P. https://forum.xda-developers.com/nexus-6p/help/zip-file-signature-verification-error-t3561054
I tried adb reboot edl and it says error: closed. So not even that works.
Click to expand...
Click to collapse
Stock fastboot does not support boot to EDL. You need a modified fastboot, BUT getting to EDL mode won't help you until you have all the proper tools and 6P specific files. I don't want to get your hopes up. I think your device is not recoverable due to a hardware issue (bad memory). If you are looking for a learning project to keep you busy with very little hope of success, keep digging. If you need a working phone, you need to buy another one, or a 6P replacement motherboard from a screen damaged parts phone. Unfortunately, there have been many onboard memory failures on the 6P.

I fixed the problem. It turned out to be a faulty USB-C to USB-A cable. The only problems were with file transfer-related commands. I then tried transferring a 1 kb file, then 1 mb (failed) then 200kb, then 300kb (failed). So it turns out the cable is ****ty. Wow. And nothing is corrupted. I'm typing this from my phone now.

HELP! MLA-TL10 bricked/bootlooped?!

I tried to update stock phone via Firmware Finder from B170 to B360. Downloaded fine and asked for restart. Phone said it was updating but froze at 5% and restarted by itself and bootlooping.
Holding Vol+ and power on leads to "EMUI installing update..." screen, then "Software install failed!" with only option to
Reboot system now
Rebooting takes phone to Huawei eRecovery with options
Download latest version and recovery
Reboot
Shutdown
Download and recovery ends with "Getting package info from server" which eventually fails
I can enter Fastboot & Rescue Mode, but phone is LOCKED (in green text) so cannot flash
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash recovery recovery.img
target reported max download size of 532676608 bytes
sending 'recovery' (41787 KB)...
OKAY [ 1.471s]
writing 'recovery'...
FAILED (remote: Command not allowed)
finished. total time: 1.487s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash boot boot.img
target reported max download size of 532676608 bytes
sending 'boot' (33249 KB)...
OKAY [ 1.166s]
writing 'boot'...
FAILED (remote: Command not allowed)
finished. total time: 1.197s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash system system.img
target reported max download size of 532676608 bytes
erasing 'system'...
FAILED (remote: Command not allowed)
finished. total time: 0.016s
Click to expand...
Click to collapse
Also, the phone is not being recognized by HiSuite latest version (8.0.1.302), and not supported by HiSuite System Recovery!
I've been reading through these forums and Googling but nothing is helping! :crying: Phone is out of warranty as it's a hand-me-down. Are paid options like DC unlocker the only way?

Anyone? Or is this phone too outdated now?

I managed to get microSD card for phone but still having troubles. I put UPDATE.APP into dload folder on root of microSD and boot with three button press but installation gets stuck and fails at 42%. I've tried with all FullOTA-MF roms from Firmware Finder, no success.

if your bootloader is unlocked see this post: https://forum.xda-developers.com/showpost.php?p=74624117&postcount=2

zaabolla said:
if your bootloader is unlocked see this post: https://forum.xda-developers.com/showpost.php?p=74624117&postcount=2
Click to expand...
Click to collapse
It was locked (getting the 14 day message before) but I tried to unlock again through the EMUI website and it worked!
So I successfully flashed TWRP 3.0.3.0. but I cannot install zips, encountering this error for all versions B360, B358, B356, and B170.
Code:
Installing zip file '/external_sd/dload/update.zip'
Checking for MD5 file...
Skipping MD5 check: no MD5 file found
mountencrypt: failed to mount /data: No such file or directory
Removing unneeded files...
Patching system files...
Removing empty directorys...
Unpacking new files...
add link type file...
write radio image...
error:oemsbl version write error!
check_write_data_to_partition,write data error
[COLOR="Red"]E:unknown command [errno][/COLOR]
update_huawei_pkg_from_ota_zip: update package from zip failed
[COLOR="red"]Updater process ended with ERROR: 7
Error installing zip file 'external_sd/dload/update.zip[/COLOR]
Updating partition details...
...done
I tried the steps in that post above but there are issues when copying the contents to the device as process hangs at file system.ext4.win000, saying 3 minutes remaining forever, eventually stopping the process itself.
Any further steps? I feel like I am one step closer to unbricking this device though.

i don't know what are you doing like that
flashing official rom is with original recovery not with TWRP recovery
with TWRP you can flash only custom roms like lineage, or restore backup rom
---------- Post added at 12:58 PM ---------- Previous post was at 12:56 PM ----------
and copy backup files to an sdcard with PC, and try the new TWRP

Oh, hmm, silly me then
Anyway, the restore worked fine when put on microSD card. Reboot failed stating an error in Chinese text (don't know what it says), and keeps rebooting into TWRP.
System not booting anyway so flashed LineageOS.zip but during the process, log showed "failed to mount /product (invalid argument)". Reboot phone and it's stuck on Lineage OS boot animation for over 30 minutes
Updated TWRP to latest 3.1.1-0

Changed the filesystem to f2fs and the TWRP backup in that post booted! Everything seems to be working except the phone is branded as CAN.
Flashing any version of stock MLA-TL10 firmware with stock recovery still fails at 42% just like before though. And flashing Lineage OS still hangs on boot animation like before as well.
I think I'll just leave the phone as is in stock Android 6.0, at least it's useable now

Flashed TWRP 3.1.1-0. The log says Failed to mount /product (invalid argument). Never had this error before but everything seems to be working fine.
Just got an idea, if anyone can kindly provide a TWRP backup I can try restoring to that.

i am trying to restore twrp backup but there's a problem
Failed to mount /product (invalid argument).
Failed to mount /cust (invalid argument).
and there's no file name cust and product in offical firmware update.app and any other i had try 3 or 4 firmware's but didnt find any file name in update.app using huawei firmware extractor can you guys please help me out? my phone is stuck on bootloader unlocked option power button for continue col up button for ercovery
my bootloaders are unlocked
---------- Post added at 05:32 PM ---------- Previous post was at 05:32 PM ----------
i am trying to restore twrp backup but there's a problem
Failed to mount /product (invalid argument).
Failed to mount /cust (invalid argument).
and there's no file name cust and product in offical firmware update.app and any other i had try 3 or 4 firmware's but didnt find any file name in update.app using huawei firmware extractor can you guys please help me out? my phone is stuck on bootloader unlocked option power button for continue col up button for ercovery
my bootloaders are unlocked

P9 Lite Brick. Failed to mount vendor and product.

I bicked my P9 Lite and need some help with it. The main problem is, that I "accidentally" wiped my vendor and product partitions using TWRP and now I can't fix them anymore. Of course I created no recovery files before... I try to give you as much information as I can:
I have a european P9 Lite L31.
I think VNS-L31C432B130 but im not shure, because fastboot getvar returns just:
Code:
>fastboot oem gevar modelid
...
FAILED (remote: Command not allowed)
finished. total time: 0.008s
I also tried to flash the volumes from a Update.zip (I decompressed using HuaweiUpdateExtractor) via fastboot, but I get the following messages:
Code:
>fastboot flash product product.img
target reported max download size of 471859200 bytes
sending 'product' (112112 KB)...
OKAY [ 3.867s]
writing 'product'...
FAILED (remote: Command not allowed)
finished. total time: 3.889s
However flashing other images (like system or recovery) works.
I also tried to restore my phone by creating a ./dload directory on my sd-card containing the update.app (and other files from the zip) using the original recovery function. However this stops at 5% before my phone reboots.
Trying to repair the partitions by using TWRP > Wipe > Advanced Wipe > [Product/Vendor] > Repair or Change File System had also no success.
Clicking the repair-button gives the following output:
Code:
Updating parition details...
Failed to mount '/ventor' (Invalid argument)
Failed to mount '/product' (Invalid argument)
...done
Full SELinux support is present.
MTP Enabled
Repairing Product using e2fsck...
/sbin/e2fsck -fp process ended with ERROR: 16
Unable to repair Product
Trying to reformat a partition or installing a new OS also fails with the "Failed to mount /[vendor/product]" message.
I am using this Update.zip:
Huawei P9 Lite B382/B383 Nougat Update
(not allowed to post a link)
I really home you guys can help me...

Don't use B382/383 files if you have B130..

Same Problem
I have exactly the same Problem; exept my P9lite doesn't have the ability to "UPTAT.APP" anymore - caused of the stupid ish erecovery.
Did you find a solution?
I would be glad to hear a reply tnx

tmato12 said:
I have exactly the same Problem; exept my P9lite doesn't have the ability to "UPTAT.APP" anymore - caused of the stupid ish erecovery.
Did you find a solution?
I would be glad to hear a reply tnx
Click to expand...
Click to collapse
More info about your phone and FW version pls. Have you TWRP on board? What says bootloader about Phone/FRP ?

bozka1 said:
More info about your phone and FW version pls. Have you TWRP on board? What says bootloader about Phone/FRP ?
Click to expand...
Click to collapse
I have the Huawei p9 lite VNS-L31 with TWRP installed and accesable
it is in following state:
PHONE unlocked
FRP Unlock
but i cant fastboot anymore and this error appears:
Failed to mount '/vendor' (Invalid argument)
Failed to mount '/product' (Invalid argument)

use the dload method via an external sdcard

Hi. I'm french. Have you resolved the problem ?

I'm atleast 51% sure that a flash of Service Repair ROM would fix that... But... Does such a ROM for MM exist?
Maybe the latest one (B381) will work...
Ofcourse flashing product and other partitions won't work. They get installed/updated through the UPDATE.APP (I think that also EliteROM is also doing that). They contain what model is the phone, how should everything be working and etc.

No OS - P9 Lite VNS-L31

(Premise: my primary language it's not english, sorry for mistakes)
Hi guys, some weekend's ago, i tried to relock bootloader (i followed a tutorial), here the problems started...
The bootloader was successful locked, but, i got this message error:
"Data partition damaged ... (i don't remember all)" i decided to unlock the bootloader, reinstall twrp and flash a stock ROM, but, when i try to flash, i got this message error in twrp:
"Failed to mount '/vendor' (Invalid Argument)
Failed to mount '/product' (Invalid Argument) "
I tried to use the tool Huawei update extractor, but when i try to flash system i get:
"target reported max download size of 471859200 bytes
sending sparse 'system' (451240 KB)...
OKAY [ 18.046s]
writing 'system'...
FAILED (remote: sparse flash write failure)
finished. total time: 18.077s"
Thanks in advance...

Did you 'format data' before flashing ?
You should try to install via fastboot the stock recovery then use the dload folder method. That may fixe your problem.

Nathoufresh said:
Did you 'format data' before flashing ?
You should try to install via fastboot the stock recovery then use the dload folder method. That may fixe your problem.
Click to expand...
Click to collapse
I tried to install the recovery stock, but, when i try to go in, he stuck in "Your Device is booting now".

Gianpi612 said:
I tried to install the recovery stock, but, when i try to go in, he stuck in "Your Device is booting now".
Click to expand...
Click to collapse
And Can you install TWRP instead offre stock?

Nathoufresh said:
And Can you install TWRP instead offre stock?
Click to expand...
Click to collapse
Yes

Is your device a VNS-L31 3Gb of RAM?