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.
Related
Hi,
so yeah... I got two fatal problems that completely block me from doing anything on my phone.
It started when suddenly my phone's screen turned black, and after a restart it keeps taking me to a screen when it asks for a password to decrypt my data, blocking me from reaching my phone.
So I wanted to recover the phone to fix it, but when i enter fastboot and choose recovery, after a few seconds it shows a picture of the android logo with an exclamation mark on it, and I cannot get into the recovery screen.
Each problem prevents me from fixing the other one, any ideas of how can I save my phone?
Download a custom recovery for crespo. Get your phone into fastmode mode and flash the recovery image.
Code:
fastboot flash recovery recovery-clockwork-5.0.2.0-crespo.img
Then select recovery in fastboot menu.
Encrypt problem is reported in this thread earlier. You may have to do a full wipe and flash a new ROM.
I downloaded the google factory image, but when i run fastboot -w update image-soju-jzo54k.zip (tried two different ones), it fails when trying to write to the system partition (FAILED remote: Write fail).
the other partitions work, but something prevents me from updating the system partition no matter what zip i use, tried many.
any ideas?
Please provide complete log messages shown on PC and phone.
Which phone did you have? soju is for i9020t, and sojua for i9020a.
Try to format data/cache/system via clockworkmod recovery first.
_android_ said:
Please provide complete log messages shown on PC and phone.
Which phone did you have? soju is for i9020t, and sojua for i9020a.
Try to format data/cache/system via clockworkmod recovery first.
Click to expand...
Click to collapse
I wasn't able to find the exact model of my phone, but since soju failed flashing and sojua succeeded, i assume it's i9020a.
Anyway, I tried to format data/cache/system via cwm recovery, and after system succeeded, the phone starts "restoring data...", and after a few minutes it stops with the message "Can't mount /data!"
perhaps the reason i he can't mount/restore /data is the reason I'm getting the encryption problem in first place, is there any way around it?
loliori said:
I wasn't able to find the exact model of my phone, but since soju failed flashing and sojua succeeded, i assume it's i9020a.
Anyway, I tried to format data/cache/system via cwm recovery, and after system succeeded, the phone starts "restoring data...", and after a few minutes it stops with the message "Can't mount /data!"
perhaps the reason i he can't mount/restore /data is the reason I'm getting the encryption problem in first place, is there any way around it?
Click to expand...
Click to collapse
Model is printed on IMEI sticker at back of phone under battery.
Format data/cache/system before flashing sojua image. Skip format system if giving problem.
Code:
fastboot -w update image-sojua-jzo54k.zip
Or try running the batch file as is, and it will update bootloader and radio to latest version as well.
flash-all.bat or flash-all.sh (linux)
_android_ said:
Model is printed on IMEI sticker at back of phone under battery.
Format data/cache/system before flashing sojua image. Skip format system if giving problem.
Code:
fastboot -w update image-sojua-jzo54k.zip
Or try running the batch file as is, and it will update bootloader and radio to latest version as well.
flash-all.bat or flash-all.sh (linux)
Click to expand...
Click to collapse
ok so soju is the right one for me.
I followed your instructions and now, and it fails writing the system image, the cmd window pretty much looks like that:
checking product...
OKAY
...
... (more ok checks)
sending 'boot'
OKAY
more OK sendings
sending 'system'
OKAY
writing 'system'
FAILED (remote: Write Fail)
I also tried using the batch file and although the window closes before i can see if any error happened, i get the same "FAILWrite Fail" error in my fastboot screen status, so I assume the same problem occurs.
What about formatting system partition via cwm? Failed too?
no, formatting system partition works. every partition format works, but i still can't update through fastboot.
It might be worth mentioning that I cannot even erase partitions on fastboot (fastboot -w fails, fastboot erase userdata, fastboot erase system etc fails, giving me a FAILED remote: erase fail error)
loliori said:
no, formatting system partition works. every partition format works, but i still can't update through fastboot.
It might be worth mentioning that I cannot even erase partitions on fastboot (fastboot -w fails, fastboot erase userdata, fastboot erase system etc fails, giving me a FAILED remote: erase fail error)
Click to expand...
Click to collapse
How about flashing a new ROM say CM10.0 + gapps-jb-20121011 via CWM?
_android_ said:
How about flashing a new ROM say CM10.0 + gapps-jb-20121011 via CWM?
Click to expand...
Click to collapse
flashing gapps seems to finish but when i flash CM i'm not sure wether it was installed correctly. it just says
finding update package...
opening update package...
installing update...
and then goes back to the cwm recovery menu, as if it finished.
anyway, i tried rebooting after flashing both and my device gets stuck right after starting, i get the google logo and then the screen just turns black and seems to process forever, and nothing happens afterwards, it's just a black screen.
loliori said:
flashing gapps seems to finish but when i flash CM i'm not sure wether it was installed correctly. it just says
finding update package...
opening update package...
installing update...
and then goes back to the cwm recovery menu, as if it finished.
anyway, i tried rebooting after flashing both and my device gets stuck right after starting, i get the google logo and then the screen just turns black and seems to process forever, and nothing happens afterwards, it's just a black screen.
Click to expand...
Click to collapse
You should Install CM then gapps.
_android_ said:
You should Install CM then gapps.
Click to expand...
Click to collapse
yeah I flashed CM and then gapps.
Interestingly tho, none of the google factory images manages to flash through CWM. they just say update failed without any informative error, while CM and gapps seem to succeed flashing
loliori said:
yeah I flashed CM and then gapps.
Interestingly tho, none of the google factory images manages to flash through CWM. they just say update failed without any informative error, while CM and gapps seem to succeed flashing
Click to expand...
Click to collapse
Google factory images are only flashable via fastboot. But there may be CWMed (cooked) versions available in XDA.
It seems like no matter what rom i flash, it either gets stuck while the phone is loading, or the phone loads and i get this "type password to decrypt" window.
Is there a way to like hard-format my phone, or a way to fix my fastboot flashing problems?
Hi there,
thanks to this forum I was able to flash several HTC phones sucessfully, but today I got perfectly stranded.
The original android version (jelly bean) of the Acer A700 was 4.1.1.
The plan was to get root access and put on CyanogenMod cm-10.1.0-RC5-a700.zip
Here is what I did:
- unlock the booloader (fastboot oem unlock)
- getting root access using easyroot.bat
I checked root access via "rootchecker" and everything appeared to be fine.
- Installing ClockWorkMod Recovery
- Under "recovery" I selected the A700 and also flashed the touch version of CWM
I opened up CWM and selected "reboot into recovery"
The A700 did was it was told and I got the usual CWM menue and could see the
desired cm-10.1.0-RC5 on my SD card
So far I was impressed how simple everything went and carried on flashing the CM10.1.
Before I did so I made a backup of the actual ROM on my SD card, then I selected
"wipe cache" an started the flashing process from the SD card.
Everything went fine and after a short time the rotating CyanogenMod Logo appeared.
However, the logo keeps on spinning an nothing else happens any more (20+ minutes)
I powered off the device and tried it again with the same result.
I also tried to press [power] + [vol -] to boot into recovery.
Letting go the [power] button and keeping the [vol-] button pressed after the device
vibrates for the first time brings up only "bootloader version JB365b3d3 (unlock mode)"
but the second line "loading recovery kernel image" does not appear anymore
In other words pressing the keys will show no difference to a normal start procedure.
When I connect the A400 with my PC and type in "adb devices" I get its number but the comment "offline"
In short, I have no idea what I could have done wrong nor how to access the device again
Is there someone out who can help me? - Thanks a lot in advance!
Comming from stock ROM, You must do Factory Reset / Wipe ALL to boot properly CM 10.1
About ADB, you must upgrade your Android SDK/ADB tools to the latest version, ADB changed a little with Android 4.2.2
With adb working, you can launch
adb reboot recovery
It should work, then make factory reset, and try to boot
Thanks a lot for the very fats response ... to be honest I thought, questions like mine are unlikely to be answered (oh no, not another dung-head who bricked his device)
However, I downloaded the latest adb version (dated 2013-05-22) and tried it again, but without success.
I can apply [pwr] + [vol-] ... [lock] to bring it into fastboot download mode.
At least the A700 shows the following lines:
Bootloader: Version JB-652b3d3 (unlock mode)
Bootloader: Version JB-652b3d3 (unlock mode) Starting Fastboot USB download protocol
Having achies this I tried to re-flash the initilally installed but now missing CWM
fastboot flash recovery root/recovery-clockwork-touch-6.0.2.3-a700.img
sending 'recovery' (5018 KB)...
OKAY[ 1. 326s]
wriiting 'recovery' ...
OKAY[ 1.154s]
finished. total time: 2.480s
fastboot erase cache
*** Did you mean to fastboot format this partition?
erasing 'cache'...
OKAY[ 0. 406s]
finished. total time: 0.406s
fastboot reboot
rebooting ...
finished. total time: 0.016s
Having done this I expected the CWM to be again on the A700, but when I start with [pwr] + [vol-] the A700 still does not boot into recovery.
Again I get this:
Bootloader: Version JB-652b3d3 (unlock mode)
followed by the nevern ending spinning CM10.1 logo ...
Without the adb running I'm pretty hopeless ... does a factory reset change anything at this stage?
You can try
fastboot boot root/recovery-clockwork-touch-6.0.2.3-a700.img
to go in recovery
and then in CWM
wipe all/factory reset
flash CM 10.1 again
flash gapps
reboot
We are ariborne, Sir!
Ereasing all partitions and flashing CWM again did the trick
fastboot erase boot
fastboot erase cache
fastboot erase recovery
fastboot erase system
fastboot erase userdata
fastboot flash recovery recovery-clockwork-6.0.2.3-a700.img
To be honest I don't understand why could not boot into recovery before?!
However all appears to be fine again!
Thanks a lot!
same problem
Hello, i have the same problem. I tried to flash CM with CWM but I didnt factory reset so my device is stuck. And i dont know anything about Sdk and Adb, can someone please explain to me how to do it
P.S: my bootloader was already unlocked so im very new to skd bull****, i dont know anything
2 hours I'm looking for a solution and this thead save my life
thanks for advises
the way I took is by the erasing all and fastboot boot recovery.img and after I install the last CM11 by the sdcard slot
Thanks a lot I can go to sleep
:good::good:
:angel:
Hello,
I have a HUAWEI Ascend Mate 7 that is very slow and I would like to factory reset it. For some reason, the factory reset button in the settings did not work, so I tried to go into recovery mode to wipe the data. However, going into bootloader only yielded a screen that said "FASTBOOT&RESCUE MODE" and "Please connect USB to your computer and open HiSuite" and had no other options. I also tried powering up the phone while holding POWER + Volume Up, but it then hangs on the Huawei logo. Recovery mode is inaccessible.
After that, I wanted to use adb and fastboot to flash a recovery. However, trying to do "fastboot flash" or "fastboot erase" gives me the error "FAILED (remote: Flash write failure)" or "FAILED (remote: Command not allowed)". I have not been able to flash any type of recovery image. I also tried "adb shell recovery --wipe_data" to wipe the data, but it gives me the error "/system/bin/sh: recovery not found", meaning that there is no recovery.
On boot, the phone hangs on the Huawei logo and does not start.
Could someone please help?
Thank you!
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
Dear community. I screwed up.
I purchased my new OP7P and in all my excitement, logically, the first thing I went to do was to unlock the bootloader, install TWRP and root it, which I did successfully because I am pretty familiar with this on multiple phones. Long story short, here's what I did, and where my problem lies:
1. Went to install the Havoc Custom ROM by following their installation instructions, went ahead and booted to TWRP recovery
2. As instructed, wiped dalvik and /data
3. Flashed Havoc ROM and here is the part where I was supposed to flash TWRP installer
4. Forgot to reflash TWRP installer and rebooted to the now nonexisting recovery. - getting the dead android icon with the message "NO COMMAND"
5. After holding VOLUP + POWER managed to turn it off and then turn it on again with just POWER to be greeted with a message warning me that I am in a bootloop
and that I have two options; to try again or to "reset to factory settings", which I did, which booted me into the HavocOS.
The main problem here is that for some reason whenever I try to repeat the TWRP installation process using fastboot, by entering "fastboot boot twrp.img", it gives me the following error:
downloading 'boot.img'...
OKAY [ 1.340s]
booting...
FAILED (remote: unknown command)
finished. total time: 1.343s
I have tried this on both Linux & Windows, same deal. The TWRP website has mentioned that if this happens I need root, but how do I root my phone without TWRP or "fastboot boot", and how do I install TWRP on the OP7P without livebooting TWRP?
Any help at all is truly appreciated. Thanks guys.
Download the MSM tool here and restore your phone. I've never used it but it gets everyone out of a brick.
I've used this tool a few times and it has gotten me out of a jam, just be sure to download the correct version for your phone. AFA your fastboot error, I got that until I let the OTA update to 9.5.11, then it worked again. https://forum.xda-developers.com/oneplus-7-pro/development/tool-tool-one-driversunlocktwrpfactory-t3930862
x3lade said:
The main problem here is that for some reason whenever I try to repeat the TWRP installation process using fastboot, by entering "fastboot boot twrp.img", it gives me the following error:
downloading 'boot.img'...
OKAY [ 1.340s]
booting...
FAILED (remote: unknown command)
finished. total time: 1.343s
Click to expand...
Click to collapse
Try to fastboot boot the TWRP build -70 from here: https://forum.xda-developers.com/on...nt/recovery-unofficial-twrp-recovery-t3931322
It fixes the problem with "fastboot boot" not working on the official Android Q update. Not sure why that would apply to your case (custom ROM after already successfully installing TWRP). But it's very easy to try, and certainly can't hurt. And the error message you are getting is exactly the same as the official Android Q problem.