Problem occurred after I flashed with 9.3.1 Global Beta, which ended with "flash system error", unlocked BL and flashed in fastboot mode. Since then the bootloop begins.
I have access to:
Fastboot
Recovery (both TWRP 3.2.3.0 and Stock Recovery 3.0)
EDL - unauthorized (not test point)
My phone has Unlocked Bootloader officially, using the Mi-Unlock after waiting for 15 days.
It's less than a month old, never dropped it. I disabled Driver Signature Enforcement when flashing. I have the phone correctly recognized when in fastboot, EDL and recovery mode by my PC.
I have tried:
Flashing 10.2.2.0 Global in fastboot mode with MiFlash, finished without error
Flashing 9.3.1 Global Beta in fastboot mode with MiFlash, finished without error
Changing USB Port and cables
Flashing 10.2.2.0 Global in TWRP, finished with error Failed to mount '/persist' (invalid argument)
Flashing 9.3.1 Global Beta in TWRP, finished with error Failed to mount '/persist' (invalid argument)
Flashing in TWRP, putting the zip file thru adb push command
Flashing in TWRP, putting the zip file thru MicroSD Card
Erasing/Flashing persist.img thru adb command, with "error:FAILED (remote: Flashing is not allowed for Controlled Partitions"
Using "fastboot erase system" before flashing
Note: While in TWRP, even when I just boot into it, if I click the 3 lines at the bottom right (the opposite of the "back" button), it shows TWRP log and it would have:
Updating partitions (in white color)
Failed to mount '/persist' (invalid argument) (in red color)
The main problem now that makes me confused, is that the fact it flashed successfully without error in MiFlash, but then it bootloops. It doesn't reboot itself, just after the Mi logo with "Unlocked" on the bottom, then it changed to Mi logo with loading animation below with the white dots, then it stays like that..
Please help.. :'(
Related
Hello there,
after booting up the phone (Android 5.0.2), the screen turs black (with backlight), becomes warm over time and reboots, no input possible.
I've read almost any post about that problem but nothing helped. I dont know how that problem happened, nothing unusual happened.
At first, i tried booting into bootloader and used there
- Normal Bootup -> booting up with same problem
- factory -> booting up with same problem
- recovery -> "bootup failed"
- barcodes -> Showing barcodes with Informatios (IMEI, Model No. ...)
- QCOM -> booting up with same problem
- BP Tools -> booting up with same problem
So i successfully unlocked the phone (Code 3, warranty was already over) to install the stock recovery -> Success, booting in recovery displaying "no Command". (waiting and then press power and vol. up get me into recovery). Then, i tried to install custom recovery (TWRP and CWM), the log on Phone says "mismatched partition size" but no errors, CMD says OK [...] OK.
Booting in Recovery -> "No Command" no matter what recovery i had flashed.
Booting an recovery out of CMD with "fastboot boot recovery.img" works for twrp-2.8.7.0.-falcon_GPE.img.
Doing "Factory reset with swipe" gives:
Updating Partition details...
E: unable to stat '/data/data/com.google.android.gms/sharedprefs/checkin.xml' other errors concerning '/data/data/com.cleanmaster.mguard[...]'
E: unable to open '/cache/recovery/.version'
MTP Enabled
but it has done factory reset. Trying to mount and send a custom firmware to SD results in error, device not responding.
Formatting data has failed with same errors as above (E: unable to ... '/data/data/[...])
The folder cant removed due to:
E:rm -rf "/data/data/com.cleanmaster.mguard" process ended with ERROR=1
Next, i tried to flash the Stock firmware (im from Germany, it was an O2-Promo with Google play) "XT1032_FALCON-O2DE_5.0.2_LXB22.46-28.1_1_cid7_CFC_1FF.xml.zip" with fastboot and mfastboot.V2. No errors from CMD, log on Phone wrote sometimes in purple "Image Size too big", but no errors. Wipe user and wipe cache, then reboot, no success.
I've tried many other firmware versions (EU and DE only, Lollipop and KitKat) step by step for each instruction with fastboot, also no success.
It seems that the write operations take no effect, even erasing partitions like recovery only displays on CMD
erasing 'recovery'...
(bootloader) Erase allowed in unlocked state
OKAY [ 0.031s]
finished. total time: 0.031s
without any effect, stock ercovery remains there, but the phone is unlocked. Now i dont know how to move on anymore, after working on the phone for 7 Hours.
Can you, the experts on XDA, help me? If needed, i can post more informations...
EDIT: It seems to be a hardware error caused by internal SDcard. Ordered a new phone, thread can be closed.
I'm having some issues installing/flashing twrp on my Nexus 5. I have been trying to fastboot twrp but it doesn't work, it says it's successful but I don't have twrp. (know what I mean?) I then tried to sideload Superuser so then I can download twrp manager or flashify and install it through either one, but when I do I get an error saying:
E: failed to verify whole-file signature
E: signature verification failed
Installation aborted.
I am out of options. I do have my bootloader unlocked if that matters.
After flashing twrp, are you booting directly into recovery from fastboot?
You can boot directly into TWRP without flashing it, with
Code:
fastboot boot <your image>.img
Does that make any difference?
Hi,
I have Moto G (XT1032) with Optimized Stock Rom 5.1 from this topic. It was alright couple of months, but today I woke up with my softbricked phone
It's stuck on Warning Bootloader unlocked, TWRP can't access any folder (although he see folder structure, so i guess it's good sign? :crying: ), all Internal Storage is displayed as 0MB, if I try to do anything I always get
Code:
"Failed to unmount '/system' /* /data etc. */ (Invalid Argument)"
Adb recognize device, but as unauthorized, when I start ADB sideload feature in TWRP, phone is recognized as sideloaded, but when i try to push rom it's say error: closed.
Can I somehow fix this phone, or is it permanent eMMC damage?
You have to give to Wipe/Format Data and Reboot/Recovery. Later go to wipe/avanced wipe and select: Dalvik/ART, cache, data and system.
cristiansuarezg7 said:
You have to give to Wipe/Format Data and Reboot/Recovery
Click to expand...
Click to collapse
I already tried it. I got spam of error Failed to unmount... and mkfs.f2fs error: "E:Unknown MTP message type: 1"
And Reboot/Recovery just shutdown phone, I have to get to recovery thru Fastboot (Power and Vol down).
Fikoblin said:
Hi,
I have Moto G (XT1032) with Optimized Stock Rom 5.1 from this topic. It was alright couple of months, but today I woke up with my softbricked phone
It's stuck on Warning Bootloader unlocked, TWRP can't access any folder (although he see folder structure, so i guess it's good sign? :crying: ), all Internal Storage is displayed as 0MB, if I try to do anything I always get
Code:
"Failed to unmount '/system' /* /data etc. */ (Invalid Argument)"
Adb recognize device, but as unauthorized, when I start ADB sideload feature in TWRP, phone is recognized as sideloaded, but when i try to push rom it's say error: closed.
Can I somehow fix this phone, or is it permanent eMMC damage?
Click to expand...
Click to collapse
Have you tried flashing unoptimized factory fimware through fastboot? To do this, enter fastboot mode and then flash the factory firmware for your device from here.
Do you have TWRP or Stock recovery?
Professor Gibbins said:
Have you tried flashing unoptimized factory fimware through fastboot? To do this, enter fastboot mode and then flash the factory firmware for your device from here.
Click to expand...
Click to collapse
Yes, I got error, like on this video:
Code:
(bootloader) Flashing primary GPT image...
(bootloader) Failed to write primary GPT.
(bootloader) Failed to program partition table
FAILED (remote failure)
finished. total time: 15.209s
cristiansuarezg7 said:
Do you have TWRP or Stock recovery?
Click to expand...
Click to collapse
TWRP
Hmm... Possibly an issue with drivers, or incorrect factory firmware. Also, have you tried skipping GPT and motoboot.img?
I was applying update using cyanogen recovery but it failed showing can not mount E:/cache (Invalid argument) so someone told me to flash using fastboot so I downloaded fastboot package and flash tools and kept in same folder and double clicked flash-all.bat ,it started flashing and after the procedure get over and command promt automatically closed but the device again stucked on boot logo . I am in deep trouble now don't know what to do ?can Anyone help me
same problem
s.ravi said:
I was applying update using cyanogen recovery but it failed showing can not mount E:/cache (Invalid argument) so someone told me to flash using fastboot so I downloaded fastboot package and flash tools and kept in same folder and double clicked flash-all.bat ,it started flashing and after the procedure get over and command promt automatically closed but the device again stucked on boot logo . I am in deep trouble now don't know what to do ?can Anyone help me
Click to expand...
Click to collapse
same problem is occuring with me. done complete flashing procedure but still it is stuck on YU logo??? what to do please help...
try to flash zip using twrp 3.0.2.0
My phone:
Huawei Mate 8 NXT-L29C636 (Last update was b193)
Output of DC-Unlocker (now):
Found Phone : HUAWEI NXT-L29
Model : Huawei phone in fastboot mode
IMEI : ***************
Serial NR. : QHC0216313******
Firmware : NXT-C900B192
FB LockState: LOCKED
USER LockState: UNLOCKED
unlocked
Click to expand...
Click to collapse
My story:
I couldn't get any update from Settings>Update. My phone was EMUI4 (Android 6). I wanted to EMUI5 (Android 7). So I used firmware finder in phone(I mean, it's not windows app, it was android app). I thought me to need to install it version by version. So first, I selected b202 (there was it after b198) and I used to proxy to install. The phone downloaded the firmware and rebooted itself. When installing (It was %2), rebooted again. And now my phone is boot-looping.
Detail:
I can install TWRP or stock recovery via Multi-Tool 8. Also fastboot is working.
Note:
-Stock recovery dosen't install update.app from sd-card. Because (vol-)+(vol+)+power dosen't run the installer. The recovery is opening when I click those keys.
-Stock recovery dosen't have "download&install" option. Ability options: "Reboot system now", "Wipe Data/factory reset", "Wipe cache partitions". ("Wipe Data/factory reset" dosen't work.)
-Also I tried this guide. But I have error thats:
"Failed to mount '/3rdmodem' (Invalid argument)"
"Failed to mount '/cust' (Invalid argument)"
"Failed to mount '/data' (Invalid argument)"
"Unable to mount storage"
-TWRP says that "No OS Installed!"
Multi-Tool 8 Unbrick Outputs:
20:30:53: All images are found, everything is ready for the unbricking process.
20:30:55: Unbricking started. Your computer may freezes during the process.
20:30:55: flash boot "C:\Users\samed\Desktop\huawei\bicak\Unbrick\boot.img"
20:30:56: The Boot image is flashing successfully
20:30:56: flash system "C:\Users\samed\Desktop\huawei\bicak\Unbrick\system.img"
20:32:15: The System image is flashing successfully
20:32:15: flash cust "C:\Users\samed\Desktop\huawei\bicak\Unbrick\cust.img"
20:32:22: The Cust image is flashing successfully
20:32:22: flash recovery "C:\Users\samed\Desktop\huawei\bicak\Unbrick\recovery.img"
20:32:24: The Recovery image is flashing successfully
20:32:24: flash userdata "C:\Users\samed\Desktop\huawei\bicak\Unbrick\userdata.img"
20:32:29: target reported max download size of 471859200 bytes
sending 'userdata' (155193 KB)...
OKAY [ 3.425s]
writing 'userdata'...
OKAY [ 1.219s]
finished. total time: 4.644s
20:32:29: Error#1
20:32:29: Completed
20:32:29: Something went wrong (((
Click to expand...
Click to collapse
So, I don't know what I will do. DC-Phoenix is not free. But if it will be fix, I can buy.
Just give me any idea. I need to help.
- UPDATE -
I haven't access TWRP or stock recovery anymore. Because I tried to restore old backup (from another Mate8 L29 user) and now I getting this errors:
After logo I'm getting this error:
RESCUE MODE
Attention!
Please update system again.
Error!
Func NO : 8 (hifi image)
Error NO : 1 (security verify failed!)
Click to expand...
Click to collapse
I'm still start fastboot.
bro if you able to access fastboot mode so its easy you can do anything whatever you want,
see my case,...
https://forum.xda-developers.com/mate-8/help/flash-wrong-file-device-unknown-t3746905
Mr Hassan said:
bro if you able to access fastboot mode so its easy you can do anything whatever you want,
see my case,...
https://forum.xda-developers.com/mate-8/help/flash-wrong-file-device-unknown-t3746905
Click to expand...
Click to collapse
No you are wrong, I can access fastboot but the phone dosen't let me do anything. For example, now I getting hifi error. I'm trying this: "fastboot hifi FW_HIFI.img" or "fastboot erase hifi" and the phone is responding: "FAILED (remote: Command not allowed)".
My phone is unlocked! But I can't do anything whatever I want.
download the uni android tool crack and flash the update.app via fastboot,
Mr Hassan said:
download the uni android tool crack and flash the update.app via fastboot,
Click to expand...
Click to collapse
Alot tools (aka, Uni-Android Tools) need to access phone via ADB. In fact, if I can connect the phone via adb or COMport, I can do everything.
So if you know how to do "flash the update.app via fastboot", tell me please. But I don't think do it with basic tools.
bro, i,m also talk about fastboot mode flash, yes its possible, you can download UAT crack , goto huwei section, select huawei flasher, select update.app file, hold VOL _ connect power cable its must be in fastboot mode, now Press start flash, thats it