I have gone to the Captivate and left my g1 sitting for a few months. Now I want to hand the G1 down to a friend, but I can't get the phone the recognize the sd card, in regular mode or recovery mode. Anyone know a way I can debug and flash a rome kinda like the ODIN program for my Captivate? The rom I have last on it was a beta with no soft keyboard...
wakeupkeo said:
I have gone to the Captivate and left my g1 sitting for a few months. Now I want to hand the G1 down to a friend, but I can't get the phone the recognize the sd card, in regular mode or recovery mode. Anyone know a way I can debug and flash a rome kinda like the ODIN program for my Captivate? The rom I have last on it was a beta with no soft keyboard...
Click to expand...
Click to collapse
you wont be able to use your phone without sd.
you can add a softkeyboard via adb.
flashing roms is not possible wo sd card afaik. maybe im wrong but i dont think so.
try another sdcard
I was able to install a soft keyboard, thanks for the advice! New sd card didn't work, but anyone know if this sd error may be a simple hardware fix
OK so heres my story of what happened to my Captivate. I plan on getting an SIII sometime in the next couple of weeks, but it would be nice to get my Captivate up and running again in case I need it sometime in the future.
So I was running CM9 on my phone, not sure which build, not sure if it matters. Phone was still in my pocket when I went swimming. Left it in a bag of rice, and it booted up. I got the message that said Encryption failed...reset phone or whatever. I figured it would just format it and didnt know that it would lead to more problems. So based on what I have read on the site, now my internal SD is fried im assuming. Now I tried following some guides for using an external SD card but I couldnt get it to partition from ClockworkMod, and I couldnt get into download mode for a few days because something probably got messed up internally from water damage. I managed to get into download mode today and tried running an Odin One-Click to see if it would help at all. Now my phone brings up the AT&T World Phone screen, then shuts off as soon as the screen normally transitions into the next step of the boot process.
So thats my story. I just want to know if anyone knows if this is still a problem with the SD card or if my phone is completely beyond repair. Thanks a lot to anyone that tries to help
You got hit by the EU (encryption unsuccessful) bug. From what I hear not a whole lot you can do now except try this. http://forum.xda-developers.com/showthread.php?t=1447303
There are a couple other threads in the dev section about this as well.
robm1911 said:
You got hit by the EU (encryption unsuccessful) bug. From what I hear not a whole lot you can do now except try this. http://forum.xda-developers.com/showthread.php?t=1447303
There are a couple other threads in the dev section about this as well.
Click to expand...
Click to collapse
Ya that was the guide I tried but my external SD card wont partition, at least not through clockworkmod. When i press the button to partition, the partition process is instant, and i know it just has to skip it because there is no way it would partition that fast.
You could always pay to have jtag performed. It will overwrite all the screwed up stuff and fix the problem.
mrhaley30705 said:
You could always pay to have jtag performed. It will overwrite all the screwed up stuff and fix the problem.
Click to expand...
Click to collapse
I think with the EU bug its just trashed. JTAG won't even fix it. There are a few stories of them coming back to life on their own, but no promises.
Hi we offer a work around re-map to have the partitions run on you external sdcard. Pm me if you need any help with this.
Sent from my GT-I9300 using xda premium
My Cappy internal memory jus went dead on me the other day.
I was texting, it froze all of a sudden and then bootloop.
I got into CWM but couldn't restore any backups as I was unable to access the internal memory from CWM.
I was on Slimbean when this happened.
I onc click odin back to stock 2.1..placed the update.zip on the external sd..ran update package from 3e Recovery..got into CWM and installed Cyanogen, then flashed slimbean again..phone boots with external sd, if I remove this it keeps boot looping..
When it boots normal with the external sd in..I can't access the internal memory, it doesn't even show up in the phone.
Any help please..
thanks in advance
vaan1988 said:
My Cappy internal memory jus went dead on me the other day.
I was texting, it froze all of a sudden and then bootloop.
I got into CWM but couldn't restore any backups as I was unable to access the internal memory from CWM.
I was on Slimbean when this happened.
I onc click odin back to stock 2.1..placed the update.zip on the external sd..ran update package from 3e Recovery..got into CWM and installed Cyanogen, then flashed slimbean again..phone boots with external sd, if I remove this it keeps boot looping..
When it boots normal with the external sd in..I can't access the internal memory, it doesn't even show up in the phone.
Any help please..
thanks in advance
Click to expand...
Click to collapse
Sorry but not much can be done, sounds like your internal sd is gone :/
I was really hoping there would be a fix by now..Ive read the other threads and there doesn't seem like this will ever be resolved..well done Samsung
Tnx for ur reply
No software fix for hardware problems. Things brake sometimes. >3 years lifetime is actually good for a cellphone.
Its a hardware problem, yours internal memory is gone. On the other hand, this is a perfect opportunity to experiment with ICS/JB roms XD
Tnx for ur replies
but I read on a thread that this was a software problem..but no one couldn't get it fixed..
Three years is not such a long time for a phone..this phone has its fair share of issues..looking at you speakers..
tnx anyway for the contributions..btw the wolfson chip keeps me holding on to this phone
There is only one major issue with this phone and it's GPS performance. Yes, some people have issues with buttons, speaker, memory, screen, etc... again, it's an portable electronic device and all portable devices show their age at some point of use. Also, many issues are user related. Phones get wet, full of dust, dropped, beaten, flashed endless times, etc. Every complaint thread deals with the result only, but very few with the cause.
Dude dnt get me wrong, I actually love this device, this is my 3rd cappy
and ure right abt the age of the device and age and stuff, causes and all..ure 100% correct
which device would you recommend with a similar sound signature to the captivate
First, let it be known that I'm an idiot. I'm not new to the scene but I did some really noobish things and I've really screwed myself into a corner. So, first the background info. I have a Samsung Galaxy S Captivate, on Rogers (Canada), and I was running CM 10.2 (if I remember correctly). I set an alarm at night and woke up the next day to a recovery loop. I tried a number of ways to recover and reflash and one by one they failed, and piece by piece, I unmounted, erased and formatted everything (I know, I know). So I've got to an interesting point and I'm not sure what to do next as most method seem inaccessible. So, here's the list of broken things (that originally worked but I broke):
- No recovery/no ability to boot to recovery. All attempts cycle a boot loop.
- no internal sdcard. Can't see it or mount it. I've tricked my phone into thinking the external is the internal. This however, means I can't download anything or even copy anything to my phone. No cloud or internet files.
- no usb. I can connect and it recognizes it, but there's no sdcard (so it thinks) so there's no connection made.
- no download mode. Here's where it gets funny. I managed to flash a stock kernel with odin (YAY!) but I flashed an AT&T version and guess what? No download mode anymore. I've tried numerous combinations. I haven't yet tried a jig which is what I'm assuming everyone will say I have to do. I have no idea what I'm doing from there.
- almost unusable phone. I can't even make calls as the SIM is meant for Rogers, not AT&T
- my bank account. I'm short on cash so I can't just go and buy a new fancy phone even though I really, really want to.
I seem to be the prime example of what not to do and I brought it all upon myself. However, I've heard that as long as the phone turns on, there's hope. My goal is to get back to a CM firmware (or something else if you hate it) and maybe recover from the damage I've caused. So, am I screwed?
tl;dr Everything is broken and I'm stupid and desperate. :good:
Jig... to get into Download mode.
Then flash an Odin Stock firmware for Rogers here... http://forum.xda-developers.com/showthread.php?p=18371028 Post #4.
But not sure how that will work out for ya since ur internal memory is messed up.
---------- Post added at 12:18 PM ---------- Previous post was at 12:08 PM ----------
If all fails and u don't mind spending some money when ya can...check out mobiletechvideos.com for the repair.
I think the main problem here is failed internal memory. At one point the system lost the access to internal memory -> reboot -> can't read data -> reboot, etc. This is why you found the phone in a bootloop that morning. Android 4.3 (CM10.2) is still in beta, but it's not the cause of the failure. No software fix for a hardware problem, unfortunately. I know some people use external SD as internal, but I never needed to study this workaround.
Val D. said:
I think the main problem here is failed internal memory. At one point the system lost the access to internal memory -> reboot -> can't read data -> reboot, etc. This is why you found the phone in a bootloop that morning. Android 4.3 (CM10.2) is still in beta, but it's not the cause of the failure. No software fix for a hardware problem, unfortunately. I know some people use external SD as internal, but I never needed to study this workaround.
Click to expand...
Click to collapse
It's using the external as the internal right now. If I remove the external and try to boot, it will show the boot logo and shut down. Seems like the jig is the next step.
I have seem to have found the issue and solution to this problem that many of us have been experiencing. If you have encountered issues like myself, there is a thread dedicated to the description of this problem; MAJOR LAG, RANDOM REBOOTS, the phone won't boot up and goes into a screen where you read:
----Mmc_failed failed boot---
After searching for about a month, it seems to be an internal SD issue. Many have reported to having these issues after they root, others upgrading to the non reversible DOK2 FIRMWARE. Others were stock with out root and had this issue as well.
**THE PARTITION OF THE INTERNAL SD CARD IS CORRUPTED**
Could be corrupted files, that stick to the phone EVEN AFTER ODIN FLASHING STOCK MANY TIMES.
(I Odin 5 times back to back to fix and the partition was still corrupted)
People thought "well, if Odin doesn't work, it's a hardware issue" I thought that myself, and it was not.
My friends, I have found something that has worked for me and would like to share with you guys. I hope this fixes your device like it did mine. I've been so close to throwing this Note 4 against the wall, running it over with my car, or smashing it with a hammer. I had no way to return my device as many have suggested to do because I left T-mobile a while back. Plus, rooting my phone voided my warranty. Yada, yada, yada, let's get into it.
*Since the internal partition to the SD card is messing up, we need to repair it.
**In order for this to work, you will need to be ROOTED.
*Download an app called "AParted SD Card Partition." Hope I don't violate any rules, but here is the link to it on Google Play.
https://play.google.com/store/apps/details?id=com.sylkat.AParted
Once the app gains root access, you will be brought to the main screen. Click the tab that says tools. Once that screen pops up, you will see
Part 1 FS: fat32 . Size 31914 MB
Part 2
Part 3
Part 4
Please note that the size to Part 1 may be a different number. That is what mine read.
*You will now click Part 1
*After doing so, at the bottom where it says create, click it and replace it with REPAIR.
*Hit apply, and you're all set.
*Turn off phone, pull battery out for 10 seconds, as well as external SD card and Sim. (They hold small amounts of electric current which may prevent the phone to do a proper boot) I usually hold both volume buttons, power button, home button, and pull the s spen out for 10 seconds simultaneously, then put it all back together and boot up.
*******Also, I used the app to delete the partition, and creating it again to avoid problems from a faulty repair. So if you want to do that, click Part 1. Instead of repair, click delete. Once done, click Part 1 again, then click create. Hit the Fat32, and start it. Once it's created, you shouldn't have issues. In case you're worried, pictures and videos will not be erased.******
I HAVE NO AFFILIATION WITH THE DEVELOPER, BUT HE SAVED MY DEVICE WITH THIS APP. PLEASE, PLEASE, PLEASE DON'T FORGET TO THANK HIM AND HIT THE LIKE BUTTON IF THIS WORKED FOR YOU AS WELL. LEAVE COMMENTS AND QUESTIONS BELOW, AND IF YOU SEE PEOPLE TALKING ABOUT THE PROBLEM IN OTHER THREADS, RE- DIRECT THEM TO THIS THREAD.
This is what I got when repairing the partition. You should have a message as well.
um... if they can't start up the device, how are they going to download it from the play store and install to run it? Thanks!
Are you able to go into DOWNLOAD MODE AND FLASH FIRMWARE? I had the Mmc_failed screen and my phone would not turn on until I took everything out the phone; battery, both cards and s pen, then hold all the buttons down.
Try this to reboot like I described up at top.
Turn the phone off. Pull the battery out, s pen out, SD card and SIM CARD.
PRESS AND HOLD ALL HARDWARE BUTTONS FOR 10 SECONDS WITH EVERYTHING OUT THE PHONE. I CLICK ALL THE BUTTONS SEVERAL TIMES TO GET ANY ELECTRIC CURRENT OUT THE PHONE. IT WON'T BOOT UP IF YOU DON'T DO THAT. I'm assuming it messes with the boot up process. Anyways, Re assemble and boot. When I was having this mmc_failed crap, it would take several times doing these steps so that the phone could boot. Don't get frustrated and try again until it boots up. Sometimes it would sit on the NOTE 4 screen, other times it would boot up to the Android logo with the mmc_failed screen. It takes several attempts since the PARTITIONS TO THE SD CARD ARE CORRUPTED. IF YOU ARE ABLE TO ODIN FLASH FIRMWARE, FLASH THE FIRMWARE TO HELP YOU BOOT UP. FLASH TWRP, THEN ROM, then you will have root.
If you still get the mmc_ boot after repairing it, erase the partition, and create it again. I updated the guide on top on how to do that. Haven't had a single hiccup or Mmc_failed bs since then. Good luck guys.
Please report back if it worked for you.
I will try this as soon as I can. The t-mobile store I went to was unhelpful and only wanted to sell me a new phone, even though I've only had the phone for 1 yr and 1 week. The problems started 2 weeks ago. Thank you for giving me hope.
Sent from my SM-N910T using Tapatalk
mtran1977 said:
I will try this as soon as I can. The t-mobile store I went to was unhelpful and only wanted to sell me a new phone, even though I've only had the phone for 1 yr and 1 week. The problems started 2 weeks ago. Thank you for giving me hope.
Sent from my SM-N910T using Tapatalk
Click to expand...
Click to collapse
No problem. Save everything important from your sd card and formatt it. That also helps. Try booting up your phone without your sd card. You know what mmc is? An sd card. Google it. Ive seen corrupt sd cards prevent phones from booting up.
Now I can't turn on the phone to fix like you. This morrning I'n in stock DOK2 and have all of error like you. I flash TWRP and flash cook rom, hope can fix like you. But after flash TWRP succesfull, I'm flash cook rom but the phone turn off and can't turn on. when it turn on, it go in to download mode and notice MMcC read fail. I try many time but it still like that. I use odin to load DOK2 Stock firwame but it FAIL. try many time still FAIL
now I don;t know anything need to do to save my phone. lol
What does it fix??
I tried using this application and the first partition that came up was a 61240 Mb partition. I thought it has to be my external SD card. Then i pulled out the external sd card and ran this application again. This time it did not find any partition.
Is this what its suppose to do? If not can you post a screenshot of your partition list.
Thanks
thiennvbk said:
Now I can't turn on the phone to fix like you. This morrning I'n in stock DOK2 and have all of error like you. I flash TWRP and flash cook rom, hope can fix like you. But after flash TWRP succesfull, I'm flash cook rom but the phone turn off and can't turn on. when it turn on, it go in to download mode and notice MMcC read fail. I try many time but it still like that. I use odin to load DOK2 Stock firwame but it FAIL. try many time still FAIL
now I don;t know anything need to do to save my phone. lol
Click to expand...
Click to collapse
After flashing TWRP AND THE COOKED ROM, TURN OFF THE PHONE. TAKE THE BATTERY OUT....SIM CARD OUT...TAKE THE SD CARD OUT AND THE S PEN PUT.
THEN WITH ALL THAT OUT, PRESS AND HOLD POWER FOR 20 SECONDS. THEN TRY TURNING ON THE PHONE. HAD THE SAME ISSUE AND IT TURNED ON AFTER A FEW TRIES.
U may need tp try to do that a few times until you get it to power on.
This is Kinda confusing, we are talking about the INTERNAL STORAGE here, Right? If so, How on earth an App can Format the Internal Storage while its being used obviously by the OS itself? and How can it NOT erase any Media files? It seems very unrealistic approach? unless we boot the system using external boot device then wipe the affected partition, think "Ultimate Boot CD" or "Hiren" for Windows.
What you are saying is like this: Boot Windows laptop/Desktop normally, then Format C: from within Windows !!!
I know you mentioned REPAIR PARTITION, that would/might be OKAY, but to Re-Create the Partition of the MMC (Internal Storage), this sounds crazy, and not even doable.
Please Shed some more lights into this !
It does not fix internal SD
Willy318is said:
This is Kinda confusing, we are talking about the INTERNAL STORAGE here, Right? If so, How on earth an App can Format the Internal Storage while its being used obviously by the OS itself? and How can it NOT erase any Media files? It seems very unrealistic approach? unless we boot the system using external boot device then wipe the affected partition, think "Ultimate Boot CD" or "Hiren" for Windows.
What you are saying is like this: Boot Windows laptop/Desktop normally, then Format C: from within Windows !!!
I know you mentioned REPAIR PARTITION, that would/might be OKAY, but to Re-Create the Partition of the MMC (Internal Storage), this sounds crazy, and not even doable.
Please Shed some more lights into this !
Click to expand...
Click to collapse
If you take out the external SD card, the app does not detect any partition. So this means that we are never fixing the internal memory, just the external one.
rajatkuthiala said:
If you take out the external SD card, the app does not detect any partition. So this means that we are never fixing the internal memory, just the external one.
Click to expand...
Click to collapse
So all of this lengthy post and RED Promises are all BS?
I thought so !
Willy318is said:
So all of this lengthy post and RED Promises are all BS?
I thought so !
Click to expand...
Click to collapse
I am still waiting @notufatjesus to reply.
---------- Post added at 03:09 PM ---------- Previous post was at 02:37 PM ----------
I was wondering, could this issue be related to eMMC like they had on earlier galaxy series. These symptoms are pretty much similar.
created new thread with real solution
Ashwin Prabhunerurkar said:
created new thread with real solution
Click to expand...
Click to collapse
I have the same problem and also hope have a way to repair this error. Now very difficult to use the phone.lol
Mine works fine
@dannygoround
My hopes went up then got nuked as I read the comments lol