Hey,
A friend gave me his Galaxy S after another friend of him got it into this following state (I'm not sure what exactly he did or tried to do):
The phone is stuck in a boot loop, sometimes it shows the first frame of the boot animation for a second before booting again. When I start it in recovery mode (Android System Recovery (3e)) I get this error messages:
Code:
-- Copying media files...
E:failed to mount /sdcard (File exists)
E:copy_dbdata_media:can't mount /sdcard
your storage not prepared yet. please use UI menu
for format and reboot actions
The phone does not have an SD card in it.
After reflashing with the same firmware as original, I get these errors:
Code:
-- Copying media files...
E:failed to mount /sdcard (File exists)
E:copy_dbdata_media:can't mount /sdcard
your storage not prepared yet. please use UI menu
for format and reboot actions
meida files copy failed.
-- Wiping data...
Formatting /data...
E:format_volume: rfs format failed on /dev/block/mmcblk0p2
Formatting /dbdata...
Formatting /cache...
Deleting Meta Data
Data wipe failed.
I've tried flashing different firmwares too, including rooted ones, and the results were the same except for a case where the first error was about not being about to mount mmcblk0p1 instead of sdcard, and another case where another firmware cause the phone to appear to boot, but after a minute or too it got stuck on a black screen and stopped responding.
I followed many different guides on how to fix similar problems, but none of them actually worked.
Please help, thanks a loooot in advance.
http://forum.xda-developers.com/showthread.php?t=1134975
Maybe it will help?
Thanks for the reply. Solutions 1-3 are irrelevant, as I can get into download mode, but even after flashing, any version, the problem is still there. I tried solution 4 (dbdata flash), but it doesn't solve anything. Are there any other partitions I can flash and might be able to solve this?
Ok, next thread
http://forum.xda-developers.com/showthread.php?t=1069867
Maybe here is solution?
Tried flashing the files there and no luck, still the same error. =/
I sent Faria, who said he has tools for solving this problem in that topic a PM, hopefully he'll share his tools with the community.
Meanwhile, I don't mind trying different solutions.
I also noticed something – if I keep the phone in the boot loop for a long time, it will eventually get to either a loop of the carrier boot animation (Which normally doesn't loop), or actually boot for one time. (When it booted I tried to power it off and see if it would boot again normally, and it didn't =/)
i have this kind of error few months ago, what i do was, flash pit file only with repartition, then flash pda, phone & csc.... agn flash this dbdata.rfs file, should fix the issue.
Just tried it, no luck, exactly the same error as before. =/
ops... sorry to heard that, at least it work for me but too bad not for u.....
I have the exact same error message and problem . Really hope someone can find a fix for this because I've spent hours and hours
Yep, EXACTLY same problem as OP and NO fixes for me yet. Tried everything from this thread and other threads. Let's see who's the real king of knowledge who can fix this.
any luck with this issue?
In my case it was solved by Click, but as in thread: for some people it works with repartition, while for some - without.
Or, try it Here I'd pay attention to page 2, Darky's resurrection... maybe looking for newer version at Darkyrom.
spamtrash said:
In my case it was solved by Click, but as in thread: for some people it works with repartition, while for some - without.
Or, try it Here I'd pay attention to page 2, Darky's resurrection... maybe looking for newer version at Darkyrom.
Click to expand...
Click to collapse
thank you spamtrash.
i tried all this various methods. i was able to boot into android but after reboot, it never got into android anymore. stuck in boot loops. ill try Darky's resurrection now, its the last option i havent tried yet. i cant believe there are no scripts or smth to fix and rebuild file system in such cases.
ambrozic said:
thank you spamtrash.
i tried all this various methods. i was able to boot into android but after reboot, it never got into android anymore. stuck in boot loops. ill try Darky's resurrection now, its the last option i havent tried yet. i cant believe there are no scripts or smth to fix and rebuild file system in such cases.
Click to expand...
Click to collapse
Any Luck????????
I'd be interested with results as well. As last hope, you can try http://forum.xda-developers.com/showthread.php?t=1330491 this one, but it requires hardware mod...
Sent from tam-tam drum
any update or fix?
Someone found any fix for this?
Yep!
Hi guys!
Yep - probably I found the solution. One month ago I have bought i9000 with this problem (as broken). Finally I managed to start that SGS and even install ICS on it. The problem is (as I suppose) that internal flash memory is broken and You have to move /data partition to external SD card. So some flashes, some changes in files and repartitioning of SD card does the thing.
Currenty I am in the middle of preparing a tutorial to be pushed on YT to show how I managed to solve the problem. Stay tuned
Best regards
this is a hope.. =)=)=) please send me a tutorial. thanks
Ready
So.
Finally I had some time to add voice recording to my movie and volia - is ready.
I hope it will help at least somehow.
I am not sure if this manual will help in Your case(s), but it might be at least a hint
Best regards
Fteller.
^ So, umm, where's the link for your YT video? Thanks.
Hi - I've started receiving a bunch of errors on my phone indicating a lot of processes are failing. Have tried resetting app preferences after searching through a lot of forums but these problems still persisted. Factory reset didn't help either. I'm bootloader unlocked and rooted so thought I'd flash a new ROM via RSDLite. I am unable to do this either. I receive the error "Failed flashing process. 1/12 flash gpt "gpt_signed" -> Phone returned FAIL.." (see attached screenshot). On the phone itself I see the following:
E: Can't read /dev/block/misc
(I/O error)
E: Failed to get BOX sync msg from MISC
Fastboot Reason: Reboot to bootloader
fastboot: max download size: 100Mb
USB connected
Getvar max-download-size
Downloading ...
Flashing gpt ...
E: re-partition failed: Device or resource busy
Fastboot command failed
I fear this means I have a corrupted internal SD card so no way to fix... however I'm no expert on this. Any idea how to fix please?
Thanks,
UPDATE
Without any further tinkering on my part the phone is no longer able to boot up. It's now alternating between the "intel inside" logo and motorola logo. Also feels pretty warm. I'm kind of giving up on the device and have ordered a new phone already. If anyone has a quick fix to revive it then feel free to let me know else will use it as a nice paperweight. Thanks.
Hi,
I have a problem with my Moto G 2014 XT1068 which is described in topic: forums.androidcentral.com/moto-g-2013/391289-something-seriously-wrong-my-moto-g.html#post3668518
I can't do these steps, because dialog window shows up all the time, and i cant go further.
I have disabled usb debugging option and can't disable ART runtime.
First of all "Factory" in bootloader doesn't work. Wipe and factory reset via stock recovery has no effect; old android remains, the same using TWRP:
"E:Unable to open 'cache/recovery/.version' but ends successfully
and PHilz.
I've tried to flash many roms using many recoveries( TWRP - few versions up to 2.8.5 because 2.8.6 has display flickering bug, few Philz, and few others that also flicker) and fastboot and msfastboot(both on linux).
When i flash via fastboot or mfastboot using xml.zip roms everything looks ok, there are no errors, but flashing has no effect - I have still old ROM with old issue.
When i flash via different recoveries always some errors appears. For example flashing latest CM 12.1 nightly
via TWRP i get:
"E:Error executing updater binary in zip '/sideload/package.zip'
or via stock recovery (ADB sideload) get:
"(...)
Verifying update package...
E:Failed to verify whole-file signature
E:signature verification failed
Installation aborted."
Partition erase in fastboot despite "OKAY" message in CLI has no effect. As i understand this should remove all files from partitions.
This problem showed up when i discharged battery to 0% and turned on the phone.
Have you any ideas what should i try more?
Thanks in advance.
Hi,
I've tried other things to back my phone to life, like turn on usb debugging or even delete files, all via adb shell in recovery, but it is impossible. In TWRP or PhilzTouch I remount partitions with rw privileges, it look like I'm able modifying files via vi and cat to check results but when remount one more time old files still exist, so it is like there is some buffer? (maybe some security lock?), when try rm -rf files it shows up that i can't delete because it read only... (but mount says rw). After remount partitions with rw privileges wipe /data in twrp ended successfully but has no effect.
Do you know why everything looks ok, but it is not? Of course android boots up but is useless and after few minutes phone turns off.
i have the exact same problem with xt1064 that shuts off after bootanimation, all flashing and wiping look ok, but stuck in same result.
i read in some threads it's due to corrupt partitions and there's no solution yet to this problem, i hope this is not true, please share if you make any progress, i will do the same. best of luck.
Sounds like you both have a failed eMMC. If that is the case, and I'm certain it is, there is nothing that can be done to "save" or "restore" your devices.
Sent from my XT1031
hi, maybe any1 has already found a solution?
dihcar said:
i have the exact same problem with xt1064 that shuts off after bootanimation, all flashing and wiping look ok, but stuck in same result.
i read in some threads it's due to corrupt partitions and there's no solution yet to this problem, i hope this is not true, please share if you make any progress, i will do the same. best of luck.
Click to expand...
Click to collapse
I have exactly the same issue with my XT1063. Reading a lot for a solution, traying all without success.
Hopping someone can help us!
My KFHD7 - Tate (PVT-08) has some trouble in the last time.
It stucks in a boot loop with the yellow Kindle logo.
I am able to reflash boot, bootloader and recovery via fastboot.
Then I normally was able to flash a system image after run recovery and can run this system once.
But after a reboot the bootloop exists again.
Now i'm able to start TWRP with the procedure described above.
The partitions cache, userdata and system always appear with 0kb. So I change the file system and change it back afterwards. Then the partition size is correct again and I can flash.
This time, however, I can no longer access the system partition.
If I try to change the file system I get the error message:
Code:
Failed to mount '/system' (Invalid argument)
Error changing file system.
A repair of the file system also fails:
Code:
Repairing system using e2fsck
/sbin/e2fsck -fp /dev/block/mmcblk0p11 process ended with ERROR: 8
Unable to repair system.
I suspect therefore (with my modest knowledge) problems with the partition table.
Maybe someone can upload me a flashable gpt.bin or something.
Or is a completely different method more suitable?
Many thanks in advance.
I have a working Tate. What exactly do you need? gpt.bin means nothing to me.
I can connect and provide a dd of something if you say precisely what you need.
In your position, I would first be asking how your partition table could have been altered. What do you suspect you may have done to change it? Unless you know you could have damaged it you may need to look elsewhere before possibly doing more damage by screwing around with the partition table.
Code:
Failed to mount '/system' (Invalid argument)
Error changing file system.
start by posting what you used as a command. No one can tell from the error what you did right/wrong
BTW how did you root the device, what version of Tate was it running before you did that?
First of all, thank you for someone's interest in the thread after such a long time.
Because of your question how to read out the gpt.bin I did some more research.
Now I actually managed to deblock the tablet!
For this I used the KFHD System.img Restore Tool. After that the problems with the system partition disappeared.
The thread is therefore solved for me and may help others in the same situation.
Thank you very much for your support!
Sylvan86 said:
First of all, thank you for someone's interest in the thread after such a long time.
Because of your question how to read out the gpt.bin I did some more research.
Now I actually managed to deblock the tablet!
For this I used the KFHD System.img Restore Tool. After that the problems with the system partition disappeared.
Thank you very much for your support!
Click to expand...
Click to collapse
I'm very pleased that my reply stimulated you to look again and got you a fixed tablet. The amount of support we get for these older tablets here seems less than minimal.
I have rooted mine but have not managed to install a recovery or fully regain control yet. I'll look at that tool you used. Do you know what Tate version you were running before , was it "up to date" ( ie sync'ed since 2014 ? ) . Mine has 7.5.1 and that seems to cut off a lot of options.
One thing I'm stuck on is booting into "recovery" mode. I have read that it is vol-up during boot but this does not seem to change anything for me, It just boots normally. If I do vol-down, I get "safe mode" but that's not much help.
Thanks for the link. I had looked at the before but was not sure if it applied to these devices, so did not want to risk it. It worked fine. One thing it forgets to tell you is to disable OTA updates. The first time I gave it wifi access it shot off without so much as a please and thank you and updated me back to 7.5.1 . So first thing to do is to kill updates:
Code:
su
cd /system/etc/security/
mv otacerts.zip otacerts.notazip
Hi guys !
I tried to install Lineage OS 17.1 on my Xperia Z3 compact and everything went well until I installed the openGapps (before reboot like tutorial said). I'm now stuck on the recovery screen where this message appears :
"Can't load Android system. Your data may be corrupt".
as well as the following error:
"E: Failed to bind mount /mtn/staging/emulated/media/0 to /storage/emulated: No such file directory"
I can "Try again" or "Factory Data reset" but neither option works! In both cases I'm stuck here again. I can't even turn off the phone or reboot via adb shell either since it is now recognized as "unauthorized".
I read a lot of topics but I have not find an answer.
Can it be an hard brick ? Please help. Thx
Try reinstalling stock ROM using Flashtool.