Database Users

ZTE Open constantly restarts

Hi:
I did root my phone, and I installed ClockwordMOD following the steps in this website:
pof [dot] eslack [dot] org/2013/07/05/zte-open-firefoxos-phone-root-and-first-impressions/
This I did from 1.0.0B02 version can be downloaded from ZTE page. Later, I installed another ROM I downloaded from ZTE page, in this case, a ROM TME Spain.
With this version I started to have problems, so I tried to return to the previous version using the Recovery and could not. I was wrong.
Nor could re-root the phone, so I could not install CWM.
Fastboot not working, because when I was trying to make something out this error:
fastboot flash recovery recovery-clockwork-6.0.3.3-
roamer2.img
sending 'recovery' (5712 KB) ...
OKAY [0.487s]
writing 'recovery' ...
FAILED (status read failed (No such device))
finished. Total time: 5.824s
Unable to use fastboot or ADB, I had only the option of using the update.zip offering this site:
firefox [dot] ztems [dot] com
After updating correctly, restarting the phone everything seemed normal, but not passed the animated fox, and restarted again.
With version 1.1 installed FirefoxOS, the phone started to have problems.
Sometimes when unblocked the screen to put the code, pressing the numbers and did not write anything. I had to repeatedly press the power button for it to work.
The same was true at times when trying to access the applications. The touch did not work well at all or sometimes it was deemed.
Now when I try to update using any ROM from Recovery (which incidentally now says Android Recovery), I get the error:
E: failed to Verify whole-file signature
:crying:

elav said:
Hi:
E: failed to Verify whole-file signature
:crying:
Click to expand...
Click to collapse
Apply this update from your stock(android) recovery. It'll work!
update_signed.zip

LinuxHolic said:
Apply this update from your stock(android) recovery. It'll work!
Click to expand...
Click to collapse
Thanks. I try!!

nexus 7 wont react while flashing in fastboot

hello,
today i downloaded the Android 5.0 Image from Google and wanted to flash it.
i extraced the tgz file and flashed the boot.img and system.img via fastboot.
so far so good. i reboot the tabelt and it has a bootloop.
so i used the flash-all.bat included in the tgz file but it wont flash it (didnt copied the error message)
so i tried flashing 4.4.4. but when i flash anything it wont work (fastboot flash recovery recovery.img for example)
i tried differend usb ports and with fastboot devices it shows my device.i tried rebooting the laptop and the tablet. no changes
example
Code:
C:\Users\xxx\Desktop\nakasi-lrx21p>fastboot flash recovery recovery.img
sending 'recovery' (5682 KB)...
after 20 min of waiting nothing changes.
my setup:
a laptop with windows 8.1
all drivers installt
original nexus 7 usb cable
drivers are working fine. i often flashed something on the n7 and my m7 bevor on this laptop

Code:
C:\Users\xxx\Desktop\nakasi-lrx21p>fastboot flash boot boot.img
sending 'boot' (5146 KB)...
FAILED (command write failed (Invalid argument))
finished. total time: 0.001s
thats a error message i get when something more happens then "sending 'xxx' (xxx kb)

Code:
FAILED (data transfer failure (Too many links))
finished. total time: 85.114s

now i managed to flash recovery (TWRP)
but i cant do anything there. in the pc its not listet (adb devices) and in the log of TWRP it says
Code:
E:Unable to mount '/data'
E:Unable to mount '/system'
E:Unable to mount '/cache'
E:Unable to mount '/data'

now i got in TWRP (changing to Clockworkmod Recovery doesnt change anything) and got to Wipe-> Advanced
there i tried to repair the partions . doesnt works. but if i format it that works and could be mounted again. (in system i have to format it in an different file format and back to ext4)
so now i flashed the rom (stock 5.0 from google) and it boots... waiting whats coming next....

etsch said:
now i got in TWRP (changing to Clockworkmod Recovery doesnt change anything) and got to Wipe-> Advanced
there i tried to repair the partions . doesnt works. but if i format it that works and could be mounted again. (in system i have to format it in an different file format and back to ext4)
so now i flashed the rom (stock 5.0 from google) and it boots... waiting whats coming next....
Click to expand...
Click to collapse
i have the same problem how did you format it and did it fix the problem

do you have TWRP ?
you go to wipe-> advanced
there you can choose which repair and format.
ive formated one by one and then it shows the size after formating.
now my tablet booted into android (i think its ugly) but iam afraid going in the recovery

Need help, tried to flash and now NP stuck at Google boot screen with unlock icon

Hello,
I'll start off by apologizing for being a noob. I tried to follow the instructions found here but somehow I got stuck in a state where my NP won't boot up. It is stuck at the Google black screen with an unlock icon. I tried to flash the 2.1 Lollirock rom and now i'm stuck in this state.
I have the NP plugged in and can get to the bootloader screen but I can't seem to figure out how to fix this. I downloaded the boot.img and system.img files from the Lollirock XDA page.
Steps I did:
At the bootloader page -
1) fastboot oem unlock (twice)
2) the bootloader screen then said it was unlocked
3) flashboot boot boot.img
4) flashboot flash system system.img
5) flashboot -w
Everything was successful with no errors so I put enabled Normal Boot in the bootloader and it just sits at the Google screen for about a minute and loops.
I tried to download fugu-lmy48n-factory-3b9d8638.tgz from the nexus stock image page and tried flashboot flash system fugu-lmy48n-factory-3b9d8638.tgz and got the error:
< waiting for device >
target reported max download size of 536870912 bytes
erasing 'system'...
OKAY [ 1.223s]
sending 'system' (457721 KB)...
OKAY [ 16.014s]
writing 'system'...
FAILED (remote: flash_cmds error!
)
finished. total time: 18.417s
I unzipped the TGZ file and tried with the TAR file and got the same error.
Then I flashed CM Recovery and that worked and I can get into CM Recovery thinking I can just update with the CM12.1 rom. The problem is that I don't have the zip on the device's sd card so I had to push from ADB by doing -
ADB sideload cm-12.1-20150520-UNOFFICIAL-fugu.zip
and it starts and goes for about 46% and stops with CM Recovery stating:
E: Failed to verify whole-file signature
E: signature verification failed
Installation aborted.
I googled this and people said to turn off signature verification since most roms are signed but I can't find any instructions on how to do that....
I also found an OTA zip of 6.0 and when updating from CM via ADB sideload, it gives me the error:
E: Error in /sideload/package.zip
(Status 7)
So that's where I'm at....not sure what to do next so any help you guys can provide would GREATLY be apprciated. Thanks!!!

Disregard, I think I got it figured out. I guess I was in stock recover and not in CM Recovery. Flashed CM Recovery again and I was able to flash CM12.1. RIght now it's sitting at the loading screen with the happy blue android face.

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.