Hello all.
I got my hands on very interesting phone, if I flash any GB ROM including stock, phone may or may not start boot looping (can't get past first screen). Now the interesting thing is that after 3-20 attempts it boots and then works perfectly (app install, taking pictures etc.) until it again gets rebooted or turned off.
If I install ICS ROM's on start-up I get Encryption unsuccessful screen and then again it takes 3-20 reboots to get the phone working. No need to do factory resets etc. Now I am no guru on Samsung HW and Android but my guess is that on boot android fails to mount /data and /emmc partition. Now I understand that this can be caused by either Corrupted partition or hardware failure. The interesting thing is that I cannot call my partitions corrupt - as I don't loose any data and I cannot call it a hardware failure - as after phone boots I can access all storage space. Tired repartitioning using Odin/Heimdall and only trick that seems to work is using External SD card as "internal".
Any ideas what this wonder is?
just search encryption unsuccessful bug on vibrant....and you will find TONS of information about it.....take your time and read it.....and btw you will be unable to access your internal sd( 16gb mem) anymore...
Related
Hi there. I've had my Galaxy S for nearly 2 years now, foolishly enough, I decided to play around with it. I managed to root it (not sure what firmware I was on, more than likely Froyo) and OC'd the phone, nothing more. After I bricked the phone (no download mode) the next day I managed to get the phone into DL mode and fixed it. However, I think that the SD card (or at least the partition tables or some other kind of information on it) is kaput. The errors I get are as follows:
- Bootlooping, whether it be a fresh flash or a rom i've left it with for a bit
- Turning off unexpectedly and then bootlooping
- Format errors: Can't mount /dev/block/mmcblk0p1 (no such file or directory), E:copy_dbdata_media:Can't mount sdcard your storage not prepared yet, please use ui menu for format and reboot actions.
I've flashed various roms, gingerbread, froyo, stock, custom ics/jellybean roms to see if it changes anything but nothing. I've tried factory resets, hard resets, formatting, and nothing seems to be able to remedy these formatting issues. If there's anything that might be able to fix my phone, I thank you in advance
hello!
i have an i9000 that produces this error after flashing stock. and is stuck on a boot loop.
i believe* the internal SD is damaged.
i think there was a good (and understandable) guide on how to make the phone running from the external SD card (using ADB to swap the lines in /etc/vold.fstab)
tried to search for it but with no luck.
made me think maybe i was wrong and this wasn't covered? found hacks swapping the Internal & external storage, but they assume the phone is working, and doesn't contain detailed explanation. with all the info here it should be possible to run it from the external SD without a problem.
* reasons that makes me believe the internal SD is damaged is that just before the phone got stuck on boot loop, all apps / photos were erased on every reboot, until it stopped loading up.
plus, i already tried all the flashing stock, wiping data, complete SD card format and flashing .pit.... basically everything i found, and it didn't work.
Necromancer3 said:
hello!
i have an i9000 that produces this error after flashing stock. and is stuck on a boot loop.
i believe* the internal SD is damaged.
i think there was a good (and understandable) guide on how to make the phone running from the external SD card (using ADB to swap the lines in /etc/vold.fstab)
tried to search for it but with no luck.
made me think maybe i was wrong and this wasn't covered? found hacks swapping the Internal & external storage, but they assume the phone is working, and doesn't contain detailed explanation. with all the info here it should be possible to run it from the external SD without a problem.
* reasons that makes me believe the internal SD is damaged is that just before the phone got stuck on boot loop, all apps / photos were erased on every reboot, until it stopped loading up.
plus, i already tried all the flashing stock, wiping data, complete SD card format and flashing .pit.... basically everything i found, and it didn't work.
Click to expand...
Click to collapse
I got this one as well but in my case this happened when I was flashing from stock 2.3.6 to CM9. I found on the net that I should flash twice. I tried and it resolved the issue. Hope it helps.
Necromancer3 said:
hello!
i have an i9000 that produces this error after flashing stock. and is stuck on a boot loop.
i believe* the internal SD is damaged.
i think there was a good (and understandable) guide on how to make the phone running from the external SD card (using ADB to swap the lines in /etc/vold.fstab)
tried to search for it but with no luck.
made me think maybe i was wrong and this wasn't covered? found hacks swapping the Internal & external storage, but they assume the phone is working, and doesn't contain detailed explanation. with all the info here it should be possible to run it from the external SD without a problem.
* reasons that makes me believe the internal SD is damaged is that just before the phone got stuck on boot loop, all apps / photos were erased on every reboot, until it stopped loading up.
plus, i already tried all the flashing stock, wiping data, complete SD card format and flashing .pit.... basically everything i found, and it didn't work.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=984140 <- FLash that as a PDA using odin after u flashed stock.
thanks for trying, but that didn't work.
Up until a few weeks ago, my N1 worked fine. Rooted, CM7.
Then I got lots of FCs and decided to re-flash CM7.
It worked fine for a week or so until last night. It was fine before I fell asleep but dead next morning.
I can VOL.DN + POWER on and switch between FASTBOOT and BOOTLOADER/HBOOT
I can boot into ClockworkMod recovery.
Booting CM7 presents coloured X; then a blank screen (it may be off) and sometimes I get softkeys lit or flash once. Usually N1 vibrates slightly every 5 seconds or so. Only way out of this is to remove battery.
I have a very recent backup. but it or any of it's img files have MD5 errors.
So, either this image is bad, or perhaps I have a RAM error that also prevents phone booting?
Is there a log file I could look at (I can connect using adb)?
Is there a way to test RAM? Is there a PASSDIAG.ZIP or PASSDIAG.NBH image I could try?
I also tried re-flashing CM7 - no change.
Any other ideas?
Did you try to use another SD card to use in your device? It could be a SD card failure and is easier to fix than a RAM failure. I also remember reading in other threads that a SIM failure could make reboots and freezes in these devices
I had a similar problem in my Nexus One with the original ROM, but in my case I think that the failure was in some corrupted file in the system partition.
Doubt SD card nor SIM is issue
Same defect when SD card and/or SIM removed (except I can not attempt a restore with SD card removed).
So I don't think either is at fault.
SD card mounts fine when USB connected to a linux laptop under FASTBOOT (I think I did this) or RECOVERY.
Mine have a like problem, i only do a full wipe and start without SD and it worked
Hello,
I've owned a Samsung Galaxy S for about 2 years and it recently started to give me problems. Before having the problems I'm going to describe I never rooted or flashed this phone.
It started a few months ago when I restarted my phone, it went to the initial screen with the "Galaxy S / GT-I9000" white text and instead of going to the next screen it just went black and returned to the same screen. I was afraid it would endlessly loop like this, but it didn't. After around 5 minutes it was able to start the phone like usual (I did nothing that could have fixed it, I just kept watching it while it looped and suddenly it didn't loop). After that, with the phone turned on, everything worked just fine.
This problem didn't go away, everytime I restarted my phone it would just sit there looping for what seemed to be a random amount of time (from 4-5 minutes to about an hour) until it was able to turn on. So I decided to try to fix this problem.
I don't know much about smartphones so my first idea was to try and reset the phone to factory settings (In Settings->Privacy if I recall correctly). I did this a few days ago and I guess it didn't help much, since when it restarted after the reset it kept trying to boot for more than an hour before I just removed the battery and came online looking for solutions.
The first solution I encoutered (on this forums) was this one: http://forum.xda-developers.com/showthread.php?t=2247484
I followed it and flashed the Semaphore .tar file in my phone. After that, booting in recovery mode would lead me to the CWM Recovery v6.0.1 menu where I was supposed to Partition the SD Card (That's what I understood from that thread).but the problem was that i couldnt even mount the /sdcard folder. (Nor the /data and /emmc folders). At this time I was only following the instructions and didn't really understand much of what was happening so I skipped to the next step, Install the firmware (I9000XXJVU_I9000OXAJVU_OXA.zip).
So this time I placed the pit file and the 3 other files that were inside the .zip I mentioned above in Odin and flashed my phone. This proccess went OK and after the phone rebooted it seemed to be installing something and gave me an error: "Failed to mount /sdcard (File exists)" (I actually found a picture in this forum with the exact same screen.
Now I was totally lost and "without" a phone, and it was actually really late and I needed to sleep. So I tried to repeat the previous steps, I returned to CWM but it still couldn't mount the /sdcard so I couldnt format or partition it. I cleared the cache and tried to install the firmware again. This time, surprisingly, it worked! After the flash the phone rebooted and was able to boot into android in the first try.
I used the phone for about a day thinking all the problems were gone but they weren't. The following day I rebooted the phone and found myself back in the boot loop. It went eventually turned on after around 15 mins but I realized I was back at the starting point.
So this time I tried another solution, since I thought the problem was in the sdcard i used SDFormatter (in Windows) and, with the phone USB connected to my laptop, I formatted the internal sd_card (I found this solution in another topic, also in this forums). After this I turned the phone off and when I tried to boot it I was back to the loop, I didn't feel like waiting so I just went back to the first solution (this time with the internal sdcard formated) and it made a difference, this time I was able to mount the /sdcard in the CWM recovery menu and was also able to partition it (according to the instructions from the solution I posted). When the partition was done I tried to flash the firmware and it worked perfectly, It booted and I was able to use it, but it wasn't detecting the internal storage, it only had the system storage (In Settings->SD card...). I found this really weird and was about to reboot the phone when it simply crashed and rebooted (It happened when i tried to turn on Wi-fi). Obviously I ended up on the boot loop again.
So now I've returned to the CWM Recovery and I can't mount /sdcard, /data and /emmc. I tried to flash the firmware I was using but now I get the same error I was getting before and trying it again doesn't seem to work (I guess I was really lucky before). I've checked the log and this is what happens when i try to mount those folders (I don't know much about Android so I don't know if this is useful):
W:failed to mount /dev/block/mmvblk0p1 (No such file or directory)
Error mounting /sdcard!
W:failed to mount /dev/block/mmvblk0p2 (No such file or directory)
Error mounting /data!
W:failed to mount /dev/block/mmvblk1p1 (No such file or directory)
Error mounting /emmc!
I've been searching for another people with similar problems and it has led me to believe that the internal sdcard is dead, but I don't know. If it was dead it probably wouldnt boot at all but in my case it just takes a while (sometimes a "long while") to boot, I can't confirm if it boots now since I can't even install the new firmware. The solution I found for these people was to use an external sdcard and divide it into 2 partitions etc, I can try to do that but first I wanted to know if there is another way to come back from this problem? Is the internal sdcard the problem?
Thanks for reading
TL;DR: Phone used to be stuck at boot loop before turning on (took from 5 minutes to 1 hour), I tried to fix it, Formated internal sdcard using SDFormatter, seemed to be working fine but phone crashed and was back on boot loop, now I am on CWM Recovery and can't mount /sdcard,/data,/emmc. I don't know what is the problem.
EDIT: I just turned my phone off and started it again in recovery mode and surprise! now I can mount the /sdcard, I dont know why this happens. One moment I am in CWM Recovery and can't mount it, I turn it off and back on and now I can.
shams94 said:
I turn it off and back on and now I can.
Click to expand...
Click to collapse
basically, your internal SD card may need some re soldering, and only professional technicians can do it or internal SD card may be failing look here about embedded SD card
Check this out! Links to useful Guides and " Banned " Documentaries
Thanks for the reply!
I followed the links on your signature and followed some guides to partition my external sdcard and use it to run the phone and it worked! I got my Galaxy S back, atleast for now (even upgraded from 2.3.6 to 4.0.3).
If anyone finds this and has the same problem my solution was this post. It even has a video showing some of the steps.
Again, thanks for your reply, without it i probably wouldn't have found the solution
So after having my trusty Vivid as my main device since March 2012, I think it may have met it's end. Randomly the day before yesterday it rebooted on me, then just kept rebooting.. Only way I could get it to boot up was to dirty flash a CM11 over whatever I had before, couldn't remember if it was CM or PAC. Got it booted up but some things didn't seem to be working right so I did a clean install and upon wiping noticed a message that said "unable to mount emmc" and I didn't think too much of it. I continued flashing gapps and supersu and was able to get the phone to boot and work but certain things didn't work right so I proceeded to wipe and flash again but this time I also noticed that my Internal Storage of my Vivid now reads as 0MB and my external SD is reading as 58254MB or whatever as it's a 64GB. I am having the same exact issue as the guy here http://forum.xda-developers.com/showthread.php?t=2576897 but my issue is resolved the same way as him. I go to TWRP and I mount as USB but nothing ever appears in My Computer or even Disk Management. I'm relatively certain the internal storage is fried. I even tried relocking my bootloader so I can return to stock, but neither fastboot or adb can detect my device while it's in the bootloader... and it says "fastboot usb" on my Vivid, but it also says "eMMC-boot" at the very top.
Now, if this were the case, how I do I still have about 4GB available for flashing ROMs onto? sdcard0 has no directories and is not found by any file explorers or disk management software that I know of. Somehow I'm still able to flash ROMs, receive calls and texts, and use most of the general functions of my phone except those requiring internal storage (like Titanium Backup).
Does anyone have any tips or advice? Should I try doing any of this from a linux machine or will it not make any difference? What phone should I upgrade to if I can't resolve this issue, because I'm not going to be dealing with it for very long?
Any input is greatly appreciated.