Hi, I wonder if you can help.
I have a Samsung Galaxy S3 GT-i9300 White 16GB, purchased in the UK for T-Mobile.
Some time ago I unlocked it to accommodate a Virgin Sim.
It has never been rooted, always running Stock Rom.
Just recently, on powering up, it reached the "Samsung Galaxy S III GT-I9300" splash screen and got no further.
Initially, I couldn't get to Recovery Mode, but could access Download Mode, so I flashed Stock Recovery. From here I attempted to "wipe data/factory reset", and received a barrage of errors, some of which are below:
Error mounting /data
E: format _volume: make_extf4fs failed on /dev/block/mmcblk0p8
E: Can't mount /cache/recovery/log
E: Can't open /cache/recovery/log
I have read and executed a string of methods from other threads on this forum, and some Youtube videos, in an attempt to get it working again. This included using ADB, on some of the mmcblk0p directories, but have failed to get the phone back in working order, stock would be ideal.
Currently I have ClockworkMod Recovery v6.0.4.7 installed, but can change that again if need be.
I'm not precious about any of the data on the phone. I have a Mac and Jodin, and do have access to a PC and Odin, but only at work. Any help and guidance would be greatly appreciated. Should you require further info from me please do ask.
Thanks... Calhoon
Flash a stock rom via odin before you knacker it completely.
The problem is the recovery partition as that loads everything to start the os and it is complaining that it can't find cache. That means one of 2 things. Either the recovery partition is borked and needs fixing or the nand itself has died. You will only find out by flashing a stock rom, preferably the same as what was already on it but if you don't know then go for the latest. Make sure you get a single package and not the 4 individual parts.
shivadow said:
Flash a stock rom via odin before you knacker it completely.
The problem is the recovery partition as that loads everything to start the os and it is complaining that it can't find cache. That means one of 2 things. Either the recovery partition is borked and needs fixing or the nand itself has died. You will only find out by flashing a stock rom, preferably the same as what was already on it but if you don't know then go for the latest. Make sure you get a single package and not the 4 individual parts.
Click to expand...
Click to collapse
Thanks shivadow,
Really appreciate your guidance here.
Gonna try and give you as much info as I can here. I followed your suggestion above.
Using on Windows 10, ODIN V1.85, which had Auto Reboot and F.Reset Time ticked.
I set the phone in Download Mode, (Power Button+Home+Volume Down), and connected to the PC via USB.
The screen before you press Volume Up to enter Download mode shows a yellow triangle with an exclamation mark.
Download Mode shows Custom Binary Download: Yes (7 counts)
Odin shows status: yellow 0:[COM3] <ID:0/003>Added!!
To the PDA section I added this md5 file : I9300XXUGML2_I9300TMUGML2_I9300BVUGML1_HOME.tar.md5
which I'd extracted from TMU-I9300XXUGML2-20140325171933.zip, which I believe is 4.3 Jellybean for the UK T-Mobile handset.
I chose this as although now unlocked, this handset was originally a T-Mobile phone.
On Odin, I then pressed Start. A blue progress bar is shown on the phone.
This reaches its end and Odin reports Success.
The phone rebooted, I held the Recovery button config, Power Button, Home and Volume Up.
Initially I see the Android image with the blue icon, then it switches to the Android on its back with the red icon.
Once in Recovery the phone reports:
E: failed to mount / efs (No such file or directory)
E: failed to mount /cache
E: failed to mount/data
E: failed to mount/data/log/recovery_log.txt
E: failed to mount/system
E: failed to mount/cache recovery/log
can't open /cache recovery/log
Can't mount cache/recovery/last_log
Can't open cache/recovery/last_log
Can't mount /cache/recovery/last install
Can't open cache/recovery/last install
I then selected Wipe Data/Factory Reset, and the phone responds with:
Wiping data
Formatting /data
E: format_volume: make_extf4fs failed on /dev/block/mmcblk0p12
Formatting /cache
E:format_volume: make_extf4fs failed on /dev/block/mmcblk0p8
Data wipe complete
E:failed to mount /cache (Block device required)
can't mount /cache recovery/log
can't open /cache recovery/log
etc
This is the cycle I've basically been stuck in whilst attempting to recover this phone.
Any more advice would be greatly appreciated, and should you require further details from me, be it more in depth or not, please don't hesitate to ask.
Many thanks already.... Calhoon. :good:
Looks like the internal memory chip may be damaged.
You could take it to a cell shop to see if it can be force flashed using something like at Octopus Box.
audit13 said:
Looks like the internal memory chip may be damaged.
You could take it to a cell shop to see if it can be force flashed using something like at Octopus Box.
Click to expand...
Click to collapse
Hi, thanks for the reply and advice.
Would you mind letting me know what is it that told you the internal memory chip may be damaged?
And if anyone else out there has an opinion I'd be please to hear it out.
Thanks.. Calhoon
Partitions that cannot be mounted by stock recovery is an indication of a memory problem. It could be that all partitions need to be re-created or the memory chip is damaged.
A failed memory chip on cellphones is not uncommon.
audit13 said:
Partitions that cannot be mounted by stock recovery is an indication of a memory problem. It could be that all partitions need to be re-created or the memory chip is damaged.
A failed memory chip on cellphones is not uncommon.
Click to expand...
Click to collapse
Apart from visiting a cell shop and asking them to force flash it, is there any way that you know where I could recreate the partitions myself?
Thanks again... Calhoon:good:
Dead phone. You can try flashing the original recovery on its own but if it fails to flash or fails to boot afterwards you can safely assume it us a dead phone with no way to recover it. Not even Samsung can do it. The only option is replace the motherboard.
Related
My wife's father in Taiwan received a Viewpad 7e as a gift. One of his son's immediately tried to hack it and get the android market going and the unit is boot looping now. My wife brought it back here to me to try and fix it.
I've gotten a factory TW rom from someone who works at VS and I put the zip file in the root of the SD card and followed the instructions to hold the power and volume up keys.
It goes into recovery mode ("Android System Recovery <3e>") and then I get the following messages at the bottom:
Recovery System version for VS v1.9
boot flag = 1
enter OTA update mode.
E:Can't find update package
E:Can't find update package
Update error.
Then choosing "Apply update from /sdcard" results in the following:
E:Unkown volume for path [/sdcard]
Wipe data/factory reset gives the following:
-- Wiping data...
Formatting /data...
E:format_volume: fs_type "ext3" unsupported
Formatting /cache...
E:format_volume: fs_type "ext3" unsupported
Data wipe complete
I have no idea what my brother-in-law did, but does this make any sense to anyone? Is there any way for me to get this factory rom back on there?
re
Hello,
Did you have the same problem or was it resolved ?
Because i did the same and my viewpad always reboots on viewsonic
I installed the firmware found on viewsonic's site but while it's loading it's written :
E:Can't open/tmp/userdata.zip (No such file or directory)
But for the rest it's ok
What's the matter
I bought this tablet 4 months ago but the problem is I rooted it so I can't send it on repair
Have you got some ideas !!!
http://pastebin.com/jYga2RmJ
Trying to regain root.
Good evening,
I'm currently having this problem on CWM 6.0.4.5, after I went to "wipe cache partition" (to install a ROM)
E: Can't mount /cache/recovery/log
E: Can't open /cache/recovery/log
E: Can't mount /cache/recovery/last_log
E: Can't open /cache/recovery/last_log
Some iterations of the error add a line on the top that says E: Can't mount /cache/recovery/command
The error consists in the device locked on recovery screen. If I try to reinstall the custom ROM, it installs but don't boot. Try to install the default ROM and it does not even load.
A palliative solution I found was:
- Reboot in download (not through CWM recovery, it wont identify the phone. Turn off on advanced at CWM then vol down + home + power, then volume up)
- Reinstall CWM recovery 6.0.4.5
- ???
- Profit
That seemed to make the phone start. Sadly, it still appears that yellow alert sign during the boot. At the moment I'm waiting the battery build up a little so I can try reinstall the original firmware through Odin but I do not know for sure if it will resolve the problem.
I'm creating this thread because although the internet is full of threads like this one, no one seems to solve the problem (mostly ask you to download some specific phone content, leaving our beloved i8552 behind), also are very confusing and well, overall non-resolving.
If anyone had some problems like this one or know how to fix the issue, please share with us! It'll help a lot of people.
(btw I'm scared sh#tless to reboot the phone!)
Best regards,
lakf
lakf said:
Sadly, it still appears that yellow alert sign during the boot.
Click to expand...
Click to collapse
This happens because you flashed CWM. It won't be a major problem for daily use.
Also, I already gave you an suggestion through PM.
Found solution
As my fellow countryman said through PM, a simple solution was to reinstall the original rom with Odin.
Be aware that if you go in advanced at cwm and reboot as download mode (it calls bootloader if I recall) it won't work, you'll have to turn off the device and enter download mode normally! So, as simple as it seems to be the solution, it works.
TL;DR Version:
1) DON'T PANIC
2) Turn off the device
3) Turn on with volume down and home button pressed
4) Download your device firmware here at sam mobile
5) Install it through PDA button on Odin
6) Rejoice that you did not bricked your phone.. This time.
Hi everyone,
I've been trying quite a lot of things until now to fix my phone, but it seems that I can't get it right.
My phone (Galaxy S3 Gt-9300) was running on Cyanogen 13 until now.
Somehow the battery started to have problems and my phone rebooted quite often, and would sometime get stuck at boot.
Then the battery inflated, and the phone couldn't turn on anymore.
So i bought a new battery, but now I'm stuck on booting screen.
I have tried to wipe data/ factory reset via the clokworkMod recovery .
But the /data and /efs cannot be mounted. So impossible to wipe them out.
I have tried to install the firmware using ODIN, but it somehow always gets stuck when trying to retrieve the PIT (i have tried 3-4 different ODIN version, multiple cable and computer)
If I install a zip from sideload, i get errors too :
"could not detect filesystem for /dev/block/mmcblk0p9"
"could not detect filesystem for /dev/block/mmcblk0p12: assuming ext4
mount: failed to mount /dev/block/mmcblk0p12 at /data: invalid argument
unmount of /data failed : no such volume
detected filesystem ext4 for /dev/block/mmcblk0p9"
Script succeeded result was [0.200000]
Basically the only thing that this achieved was changing the logo of the boot (but still stuck)
I fear that the internal memory was damaged during a bad shutdown.
What can I do ? Remapping the internal memory might be an option but since I don't have a readable /efs I don't know if this would work.
Thanks for the help
Your only option is the rescue firmware in general forum with pit. If this won't flash then your emmc chip is damaged.
So if the emmc chip is dead, it's game over ?
Have you tried an official cwm recovery from the official website?
Sent from a stolen phone!
Whatever rom I use, it cannot finish.
Either it's the official one or not.
Odin cannot complete the job. It usually get stuck at PIT.
Woke up to my phone unresponsive so I removed the battery and tried to power up, but was stuck in a bootloop for more than 5 minutes. Rinse repeat. Nothing. So I boot into TWRP and try to factory reset but "
E: Could not mount /data and unable to find crypto footer.
E: Unable to mount '/data'
etc
---
Comes up. I am unable to wipe, flash, anything. I have tried both LG flash tools but they both fail. KDZ method says its complete but still stuck in bootloop. TOT simply fails to wipe.
I am unable to take my phone to Verizon as well because the boot-up image is Blisspop so they would know that I have rooted my device. In order for me to use Edge to get a new phone I have to trade this one in in working order, which now I can't.
Any help would be greatly appreciated as I've been working at this for the last 6 hours. I am thinking that it is an internal storage issue but like I said I am unable to take it into Verizon to attempt a warranty exchange.
INFO:
LG G3 VS985
BlissPop ROM - 06/22
Sirrometan said:
Woke up to my phone unresponsive so I removed the battery and tried to power up, but was stuck in a bootloop for more than 5 minutes. Rinse repeat. Nothing. So I boot into TWRP and try to factory reset but "
E: Could not mount /data and unable to find crypto footer.
E: Unable to mount '/data'
etc
---
Comes up. I am unable to wipe, flash, anything. I have tried both LG flash tools but they both fail. KDZ method says its complete but still stuck in bootloop. TOT simply fails to wipe.
I am unable to take my phone to Verizon as well because the boot-up image is Blisspop so they would know that I have rooted my device. In order for me to use Edge to get a new phone I have to trade this one in in working order, which now I can't.
Any help would be greatly appreciated as I've been working at this for the last 6 hours. I am thinking that it is an internal storage issue but like I said I am unable to take it into Verizon to attempt a warranty exchange.
INFO:
LG G3 VS985
BlissPop ROM - 06/22
Click to expand...
Click to collapse
I'm at the same spot with this in regards to the crypto footer issue...did you ever get this fixed?
Samsung Galaxy S2 SGH-i777 in infinite boot loop.
When I turn on the phone it proceeds past the Samsung logo screen and after a while ends up at the AT&T Rethink Possible screen where it proceeds to reload that screen over and over again in what appears to be an infinite loop.
When I hold down Vol Up & Vol Down and Power, the phone displays the Samsung logo, appears to power cycle and display the Samsung logo again and appears to enter recovery mode. When the phone enters recovery mode, it displays a number of error/status messages as follows:
E:failed to mount /cache (Unknown error: 0)
E:Can't mount /cache/recovery/command
-- Copying media files...
E:failed to mount /cache (Unknown error: 0)
E:copy_cache_media:Can't mount /cache
your storage not prepared yet, please use UI menu for format and reboot actions.
Meida files copy failed.
# MANUAL MODE #
-- Updating application...
E:failed to mount /data (Unknown error: 0)
E:install_application_for_customer:Can't mount /data
your storage not prepared yet, please use UI menu for format and reboot actions.
copy application failed.
-- Appling Multi-CSC...
Installing Multi-CSC
Can't access to '/system/csc/ATT/system/'.
Successfully applied multi-CSC
E:failed to mount /cache (Unknown error: 0)
E:Can't mount /cache/recovery/recovery_kernel_log
E:copy_kernel_file :: Can't open /cache/recovery/recovery_kernel_log
E:failed to mount /cache (Unknow error: 0)
E:Can't mount /cache/reocvery/log
E:Can't open /cache/recovery/log
E:failed to mount /cache (Unknown error: 0)
E:Can't mount /cache/recovery/last_log
E:Can't open /cache/recovery/last_log
E:failed to mount /cache (Unknown error: 0)
The above messages don't display at once but seem to display after a few presses of the Vol Up button.
After the error messages have all displayed, I see the following at the top of the screen:
Android system recovery <3e>
Enter: Power Key. Select : Vol UP / Vol Down
reboot system now
apply update from sdcard
wipe data/factory reset
wipe cache parition
BUT even though I can use the Vol buttons to navigate the choices, pressing the power button has no affect to select them.
At the moment, I would just like to get back to a working phone. I have attempted to use Odin to flash the UCKH7 stock rom that I found in this post: http://forum.xda-developers.com/showthread.php?t=1286432. It indicates that it does so successfully but it doesn't change my phone situation.
Because I saw the errors about the various partitions I also though maybe I should try re-partitioning with a PIT file. This was probably not a good idea but I was not aware at the time that it may have been a bad decision.
What should I try to fix this situation and get my phone working again?
Thanks!
I'm assuming you are able to boot the phone into download mode, since you flashed Entropy's UCKH7. I suspect that you have memory corruption, and not memory damage. That old UCKH7 from that thread contains only the system and kernel, and not the other files you need to do a full install, so I'm not surprised it didn't boot.
If you flashed the UCKH7 pit file, it probably didn't do any damage, but it would not clear the corruption by itself.
The first thing I would try is to flash a full stock distribution in Odin, without pit, and see if that clears the problem. You can find the files you need in the Download Repository. See the link in my signature. I would suggest flashing the latest stock firmware full distribution, which is I777UCMD8 (Android 4.1.2 Jelly Bean). It's the next to last item at the bottom of the page. The original UCKH7 Full stock distribution is there also under the heading I777UCKH7-CL503881 Stock Binaries.
If the above does not resolve the issue, all is not lost. Post your results back here and I wil post how to clear the corruption. Good luck.
FIXED!
Yes. You assumed correctly. I suspected (or maybe it was hoped) that it was just memory corruption and not damaged but couldn't find what to do.
After following your advice of downloading the latest stock firmware full distribution and using Odin to flash it.
After flashing and booting, I kept getting stuck at the AT&T logo screen. I booted back into recovery mode and saw that it was still unable to mount the /data partition and it didn't seem to let me wipe the /data partition. I then went through a series of reboots and even re-flashed again. Finally, I entered recovery and got distracted. When I came back to the phone, I discovered I was able to get the power button to select the Wipe Data Partition. I wiped data and cache and then I re-flashed one more time.
After this my phone finally booted all the way.
Thank you so much for your help. It is really appreciated.