Related
Problem:
Can't seems to be able to restore my phone using clockwork 3.0.2.4 or when trying to do a fastboot restore through the android SDK.
Error:
When I try to restore the system or the data via clockwork on the phone i get "error formatting /system!" or "error formatting /data!"
I also tried to do this:
fastboot flash userdata data.img
fastboot flash system system.img
fastboot flash boot boot.img
fastboot reboot
I get the following error:
sending 'userdata'
FAILED (remote: data lenght is too large)
I also tried this via the adb shell
flash_image system system.img
Can't read device: "/dev/block/mmcblk0"
Error in reading mbr!
failed with error: -1
Question
Is it because there is a problem with the MBR that i can not write the system or data files? Is there a way to fix the MBR?
Any suggestions or information would be greatly appreciated!
What I have
Mytouch 4g
T-Mobile
Clockwork 3.0.24
After doing a little more digging I found that some people had luck with putting the PD15IMG.zip in the root directory of the SDcard. This will restore the phone back to factory default when holding the volume down and power button at the same time.
I went ahead and tried this and when trying to restore it I get a FAIL-PU, FAIL-PU FAIL-PU when loading for bootloader down to system.
Anyone have any other recommendations of what I can try? Seems like I might have a expensive paper weight on my hands
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?
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.
Hello,
I had Resurrection Remix Android 7.1.2 installed in my Mi4i. The apps were suddendly crashing (was getting app crashed alert) and thought to reboot the phone once.
Once I tried to reboot abnormality started showing up.
Tried flashing the Resurrection Remix again but it stuck at the boot animation screen.
Then tried flashing the official MIUI developer rom and it worked.
Again tried with RR but it did not boot up.
After trying a couple of times, none of the roms did boot up.
After some research found in TWRP logs that it is unable to mount system, cache, dalvik cache etc.
Also I could see that the space/memory is displayed as 0MB.
Some forums said to format the file system as ext4 and even the format failed saying it is unable to mount.
Now whenever I start the phone to goes to the fastboot screen.
The interesting point is that I tried flashing manually the developer rom and it said it falshed successfully.
But i still see the twrp as my recovery and not the stock recovery after flasing.
Also tried manually flashing the recovery like "fastboot flash recovery recovery.img" and did not find any errors still the stock recovery was not flashed instead the twrp remained as the recovery even after successful flash.
I am stuck with my phone now and not sure how to proceed.
Any help regarding this would really be helpful.
Help me to recover my phone please. :crying:
Thanks.
So have you format all of your data including internal data from TWRP ? Is it show some error like "unmount /data" types N how you flash rom manually means you tried of ADB slide load ??
Mukulkathuria008 said:
So have you format all of your data including internal data from TWRP ? Is it show some error like "unmount /data" types N how you flash rom manually means you tried of ADB slide load ??
Click to expand...
Click to collapse
1. Tried formating the partitions from TWRP.. Failed with error message saying cant mount
2. Hence thought TWRP was broken.. Tried flashing twrp again from fastboot as follows :
Code:
fastboot flash recovery recovery.img
Fastboot flashed successfully(got OKAY response in terminal).
3. Rebooted into recovery and tried formatting partitions again. Still got the same error saying cant mount partitions.
4. Thought to flash stock recovery. Had miui fastboot room. Picked up recovery.img from it and flashed from fastboot as follows :
Code:
fastboot flash recovery recovery.img
5. Surprisingly when I rebooted into recovery, the custom recovery was still twrp.. The stock recovery didn't got flashed.
6. To crosscheck, I directly booted the stock recovery fastboot boot recovery.img. But nothing boots up.. Gets stuck at the distorted fastboot screen (Attaching screenshot if possible).
Probal Basak said:
1. Tried formating the partitions from TWRP.. Failed with error message saying cant mount
2. Hence thought TWRP was broken.. Tried flashing twrp again from fastboot as follows :
Code:
fastboot flash recovery recovery.img
Fastboot flashed successfully(got OKAY response in terminal).
3. Rebooted into recovery and tried formatting partitions again. Still got the same error saying cant mount partitions.
4. Thought to flash stock recovery. Had miui fastboot room. Picked up recovery.img from it and flashed from fastboot as follows :
Code:
fastboot flash recovery recovery.img
5. Surprisingly when I rebooted into recovery, the custom recovery was still twrp.. The stock recovery didn't got flashed.
6. To crosscheck, I directly booted the stock recovery fastboot boot recovery.img. But nothing boots up.. Gets stuck at the distorted fastboot screen (Attaching screenshot if possible).
Click to expand...
Click to collapse
Try to flash TWRP v3.2.1.0 you can download from link below:
https://dl.twrp.me/ferrari/twrp-3.2.1-0-ferrari.img.html
And Advance Wipe And change the file format to ex4 and wipe all the data try ROM try flash ROM link below through OTG:
https://forum.xda-developers.com/mi-4i/development/unofficial-dotos-v1-2-t3726924
that surely solve your all problems :fingers-crossed:
Mukulkathuria008 said:
Try to flash TWRP v3.2.1.0 you can download from link below:
https://dl.twrp.me/ferrari/twrp-3.2.1-0-ferrari.img.html
And Advance Wipe And change the file format to ex4 and wipe all the data try ROM try flash ROM link below through OTG:
https://forum.xda-developers.com/mi-4i/development/unofficial-dotos-v1-2-t3726924
that surely solve your all problems :fingers-crossed:
Click to expand...
Click to collapse
Tried formating to ext4.. But nothing happened.. Still getting mount error.
Attaching pics below.
Attachment 1 : Advanced Wipe -> Wipe
Attachment 2 : Advanced Wipe -> Change File System -> /system -> ext4
I have also tried this
Code:
fastboot getvar all
Output:
Code:
all:
finished. total time: 0.001s
Any comments what may have gone wrong?
fix file system. or maybe emmc died
Hello guys I need some help. I'm stuck in fastboot mode with no recovery or OS too l, let me retrace my steps.
I had my px3 rooted on stock but I was bored with stock and tried to flash bootleggers rom and followed instructions to wipe "everything" but internal storage, so I did including storage under internal storage and flashed the ROM and twrp with it. After it just rebooted back to recovery every time I tried normal boot. (I'm assuming I F'd up by wiping storage). So I googled what to do about looping recovery and one suggestion was to factory reset so I did; I can no longer access recovery. I've tried flashing factory image, flashing the twrp zip, trying to boot straight to twrp, I can't get to adb sideload and it says "no valid slot to boot" on fastboot screen any suggestions?
Got another on fastboot, "error booting boot.img"
Does your PC recognize the phone in Fastboot mode? I would try flashing the full factory image again. Ensure you have the latest platform tools and the correct firmware for your device.
fury683 said:
Does your PC recognize the phone in Fastboot mode? I would try flashing the full factory image again. Ensure you have the latest platform tools and the correct firmware for your device.
Click to expand...
Click to collapse
Yes it does and I've got everything from twrp .zip and .IMG, factory images and ota zip.
I did make progress just now and switched to slot B and got TWRP to show up:laugh: might just sideload OTA and pretend this never happened
Update, adb sideload taking too long to start
wergrun said:
Yes it does and I've got everything from twrp .zip and .IMG, factory images and ota zip.
I did make progress just now and switched to slot B and got TWRP to show up:laugh: might just sideload OTA and pretend this never happened
Update, adb sideload taking too long to start
Click to expand...
Click to collapse
You need to get back to fastboot, and run the flash all bat file from the full factory image.
TonikJDK said:
You need to get back to fastboot, and run the flash all bat file from the full factory image.
Click to expand...
Click to collapse
I tried that but I keeps giving me an error, I'll post it when I get the chance
Problem SOLVED! used video by MaowDroid "Pixel 2 (XL): Un-root and return to stock using factory images"
fury683 said:
Does your PC recognize the phone in Fastboot mode? I would try flashing the full factory image again. Ensure you have the latest platform tools and the correct firmware for your device.
Click to expand...
Click to collapse
I have the same issue, except my computer will not recognize the device in fastboot. I tried two different computers, Windows 10 and laptop running Linux.
wergrun said:
Problem SOLVED! used video by MaowDroid "Pixel 2 (XL): Un-root and return to stock using factory images"
Click to expand...
Click to collapse
Followed the video, but I get an error:
'FAILED (remote: Failed to write to partition Not Found)'
I've tried: bootloader, bootloader_a, bootloader_b and bootloader_other and get the same error.
I'm stuck....
SS823 said:
Followed the video, but I get an error:
'FAILED (remote: Failed to write to partition Not Found)'
I've tried: bootloader, bootloader_a, bootloader_b and bootloader_other and get the same error.
I'm stuck....
Click to expand...
Click to collapse
I did get that too but it was because I forgot to put a space after "bootloader_a ", are you Stuck at around the 9 minute steps?
Yes, right around the end at 9 minutes. Everything works fine - bootloader, radio, etc. When I get to the end of the img zip file I get this message:
checking product...
OKAY [ 0.060s]
checking partition-exists...
FAILED (remote: variable not found)
finished. total time: 0.360s
I am at a loss.