Posted this in the Doc Bell thread as well. I've been running Doc's Bell JK3 rom for a while, starting with 1.0, I'm now on 1.2.
Lost my SD Card today after flashing K10E-500hz, was on K10C and also K9 before this. It flashed fine then I put the phone down and picked it back up 20 minutes later and the soft lights were glowing so I thought I had a message. The phone wouldn't respond so I rebooted it and instead of Launcher Pro, TW loaded and I was greated with a message saying the internal SD failed. I can't access anything, keeps force closing.
I still have clockwork recovery and download mode. I tried to flash JH2 with Odin but it won't even start. It's like it doesn't see the phone at all, even just in windows.
I need to get back to JH2 to take this back for warranty. Or is there other things I can try?
Thanks guys
edit: I noticed something weird. In CWR I can see the files on my SD card, but once booted it says no SD inserted.
http://forum.xda-developers.com/showthread.php?t=845708
This Topic Pinpoints your issue.
Related
I was running Phiremod on an sd card a couple of nights ago and something went terribly wrong with my NC. I tried to get into the program and it would boot all the way to the home screen and then just power off. I couldn't get it to boot into CM7 running on an sd card either. I searched these forums and others and although I returned the device to stock, repartitioned the boot, removed clockworkmod, reflashed the roms, reformatted the sd card (16gb), switched to an 8gb card and I don't know what all else (not necessarily in this order), I cannot run any roms other than Autonooter 3.0. It installs from an 8gb card with no problem and runs fine. But when I try to use my CM& nightly 37 from my other NC, no go; I reflashed Tablet Tweaks, HC V4, Nookie Froyo and tried them all, no go.
I could get Phiremod to load all the way to the home screen and then start powering off. CM7 comes up to a blank screen with the status bar and buttons at the bottom but also a status bar at the top that says Android system and then it powers off. I rooted the NC with Autonooter 3.0 and then tried to install Tablet Tweaks and got the same weird Android System status bar at the top and then it powered off.
Any ideas? I have been working on this for 48 hours and I got nothin'. I can't get ADB to work with just the NC running stock (I am no expert and might be doing something wrong).
First run autonooter and root it, then u can use rom manager to flash clockwork recovery to emmc. After that use either of the two to flash another rom to emmc.
Also were trying everything from sd card or were u flashing to emmc?
And i am not sure but ADB should work with rooted stock.
Thanks for the response. I will try flashing cwm to emmc tomorrow. I was trying everything on SD cards and emmc. I installed Tablet Tweaks to emmc with the weird result mentioned in the op. TT wouldn't run from an sd card or emmc: the NC just kept powering off as soon as it got to the home screen but before it finished loading up. I should be able to use adb now that I'm rooted. Silly me, couldn't get the device to be recognized running stock. I'll update on how things go and probably will still need help.
Ok, I just installed Clockwork and then using it I flashed Nookie Comb. The installation went fine, boot up went all the way through to the home screen and then the same thing as usual happened: the weird notification bar at the top that says Android System, the status bar with softkeys at the bottom, and immediate powering off.
I think I saw this weird notification bar once when I was rebooting the Nook before I used autonooter, so I think that something is wrong on the emmc level. I have returned to stock and looked at the information in Factory and it shows that I have been returned to 1.0.0. But after I go through with the registering process, I find that the device is on stock 1.1.0 without having to sideload the update. I don't see any notification that I have been updated to 1.0.1, which used to be the case before all this happened. I was trying to avoid messing with the stock rom (warranty) but it looks like I won't be able to do that unless I can figure out what happened here. If all else fails, I will just stick with autonooter, which works well for the purposes for which I use this NC. I do have a second NC that works just fine and can run roms off an sd card. Maybe I can take something off of it and put it on the other?
Any assistance is appreciated.
04/10/11 - 6:00 pm****As I said above, I searched high and low and I tried everything!, but still nothing has got me back to being able to run roms off sd cards yet. But I feel that I have made some progress. I was very disturbed about going from 1.0.0 to 1.1.0 without applying the sideload update so I decided to start all over again and restore the NC to stock. I found yet another thread and followed the instructions, except that I unknowingly used CWR 3.0.0.6 instead of CWR 3.0.0.5. So, instead of immediately rebooting into the stock hardware, I had to do a hardware reboot. This brought me back to 1.0.1 and I was able to install the sideload update. So stock rom seems to be back to normal. I took the CM7 rom I am running in my second NC and put the sd card in the trouble NC. It did boot up and completely loaded up the homescreen. This time no top notification bar, no Android System message, but yes, the little sd card icon showed up at the bottom although no message about a damaged card or sd card now removable showed up. But the screen was completely frozen and the device immediately turned off. There was no powering off notice or anything; it just went off and the screen went black. This is a 16 gb card. I am going to try with an 8 gb card now.
04/11/11 12:40 am**** Ok, I give up. I have succeeded in getting nowhere fast. I am thankful that I can run Autonooter 3.0 on it and use sd cards to load my files for using on the NC. I miss the froyo/honeycomb/cm7 experience on this NC but at least I get it on my second one. One good thing that came out of this: i can do the eight boot interrupt thing without a hitch!
Hi guys, my phone had the 10.1 darkys rom installed and all was well. a week later and the phone started to shut itself off randomly so i went back to factory and then reinstalled rom after flashing kernel ect. but my external sd card is not recognized..... so i think that this may have been the random reboot problem {had most apps on sd} so i took card out, put it in computer and no problems at all, all files were still on there and were all readable and writable..... so what could have caused this and how can i fix it? i have not had water get into the phone that i know of and this was the only thing i could think of...... any help appreciated!! p.s. i tried another working sd card and same problem. even when mounting to computer.... nothing.
It could be that your internal SD card is corrupted. If you can back everything up, then do so and I would flash a stock Froyo or Gingerbread rom to see if that fixes the problem.
If you still encounter issues, then your phone may have to visit a repair centre.
holdz said:
It could be that your internal SD card is corrupted. If you can back everything up, then do so and I would flash a stock Froyo or Gingerbread rom to see if that fixes the problem.
If you still encounter issues, then your phone may have to visit a repair centre.
Click to expand...
Click to collapse
The other problem i have encountered is when trying to install darkys rom again, but this time from internal sd, it goes through the motions but then when it reboots rom is not installed and my back and home button dont work, so i go back to what it was and that fixes it. ill try flashing back to bog stock and see if i can get my sd card back. will that remover cwm as well because if i take itback to shop i want that gone..... cheers
Flashing back to a stock rom will remove CWM and put you back on Samsung's Recovery 3e.
I was in the process of recovering my Captivate - that I had upgraded to Gingerbread - from a corrupted OS. I was able to factory reset back and get the phone running again. While on this forum and getting help resolving that issue, I thought I would see how stable the new 4.2's were. I was walking through the steps of the update and I had just finished flashing CWM with Odin and then it all fell apart.
<<< Noob alert>>> When reading the posts and the walk-throughs, I always read SD Card as the mini-SD card that you add to the phone - the external card. Therefore I put the new custom rom on the external SD.
I wiped the data and went to apply the new rom from zip, and (of course) I couldn't find it. After several tries, I realized my problem. However, my Captivate will not mount my external SD. It is the same one that was in the phone and has been working. I formatted it and checked it for errors - none - but the phone will not mount it. I cannot get access back to the internal SD memory to put the ROMs there - when I turn on the phone is gets to a black screen that says "Galaxy S sgh-1897" and sits there - and my computer does not recognize the phone when I plug it in to the USB.
What can I do? Do you have any ideas?
ktvanhorne said:
I was in the process of recovering my Captivate - that I had upgraded to Gingerbread - from a corrupted OS. I was able to factory reset back and get the phone running again. While on this forum and getting help resolving that issue, I thought I would see how stable the new 4.2's were. I was walking through the steps of the update and I had just finished flashing CWM with Odin and then it all fell apart.
<<< Noob alert>>> When reading the posts and the walk-throughs, I always read SD Card as the mini-SD card that you add to the phone - the external card. Therefore I put the new custom rom on the external SD.
I wiped the data and went to apply the new rom from zip, and (of course) I couldn't find it. After several tries, I realized my problem. However, my Captivate will not mount my external SD. It is the same one that was in the phone and has been working. I formatted it and checked it for errors - none - but the phone will not mount it. I cannot get access back to the internal SD memory to put the ROMs there - when I turn on the phone is gets to a black screen that says "Galaxy S sgh-1897" and sits there - and my computer does not recognize the phone when I plug it in to the USB.
What can I do? Do you have any ideas?
Click to expand...
Click to collapse
Here's a good start to get your pc to recognize your phone: http://forum.xda-developers.com/showthread.php?t=1953930
From there, flash Odin KK4 without bootloaders in download mode to get your phone back up. I believe to know the steps to flashing a custom ROM
GL!
got it going
Thanks, it's up and running, but I went back to speedmod and tried to update from SD - and it worked, but didn't like the ROM. I'm trying a different ROM to see what the issue is.
Thanks for the help.
ktvanhorne said:
Thanks, it's up and running, but I went back to speedmod and tried to update from SD - and it worked, but didn't like the ROM. I'm trying a different ROM to see what the issue is.
Thanks for the help.
Click to expand...
Click to collapse
You'll have to flash the ROM twice to get past the partition on JB coming from GB.
Sent from my SGH-I747 using xda app-developers app
Hey,
Been trying to reset the tab to factory defaults the tab does his mojo untill it reboots into android 2.3.6 and then everything is still on the internal SD card.
Then i went to hook it up on the pc tried manually deleting everything on the internal SD pc say's its done i look in the tab and its all still there.
Tried copy'ing files over to the SD card but does not wanne stay on it.
Ok now then i went on booting odin up and rooted it + cwm recovery on it it does it like a charm and works can boot into the recovery.
Now since i cant hold any roms on the internal sd card i went on using an external sd card put on cm 10.2 and gapps,
Installed the rom then reboots into a newer version of cwm and it tells me its not rooted.
ok fine i restarted the tab and went back into recovery then it was rooted.
Went on to install the cm 10.2 and gapps now its hanging at the cm logo on boot
So i went on to flash dbdata.rfs.tar wich normally gets me passed a bootloop.
This time however it dident work.
Anybody has any ideas i can still try to get it to work ?
I think its more of a lock on the internal SD card since it can't hold any files nor delete's anything but im not sure hopefully some1 with some more experience then me can help me further on this problem
Thx
Not locked. The internal SD chip is failing.
You will see many post that has symptoms such as: previous owner info cannot be removed. New data cannot be saved. Wiping failed.
My mind was vaguely thinking that but still hoping it wasent
I've never used a forum before, but I'm having a very tough time with my i897 captivate. Its previous owner left it in a box while software updates passed it by. When I came in possession of it, I used rooting, custom ROMs, and flashing to update it to more useful firmwares. I mainly stuck to CM 7, 9, and 10. Eventually I fell victim to that "ICS Encryption Unsuccessful" error and clicked reset, triggering a period of bootloop. I've since fixed the bootloop issue but I still can't get my phone to boot to any firmware. Over the past year, I've been trying all sorts of things to get my phone to work again and I don't know if I've made the problem worse or not. I can get my phone to boot the At&t screen, download mode, and whatever recovery kernel I'm on at the time, but nothing more. I don't even think I have a ROM installed anymore.
What I've tried:
several Odin One-clicks
Heimdall One-click unbrick
Partitioning my external sd card to act as an internal one
ADB sideload
ADB push and install zip from sd card
The errors I run into the most are the "can't mount sd card" ones when I'm trying to flash a custom ROM in recovery. I guess my internal sd is corrupted somehow? Is there a way for me to fix this mess?
asertap said:
I've never used a forum before, but I'm having a very tough time with my i897 captivate. Its previous owner left it in a box while software updates passed it by. When I came in possession of it, I used rooting, custom ROMs, and flashing to update it to more useful firmwares. I mainly stuck to CM 7, 9, and 10. Eventually I fell victim to that "ICS Encryption Unsuccessful" error and clicked reset, triggering a period of bootloop. I've since fixed the bootloop issue but I still can't get my phone to boot to any firmware. Over the past year, I've been trying all sorts of things to get my phone to work again and I don't know if I've made the problem worse or not. I can get my phone to boot the At&t screen, download mode, and whatever recovery kernel I'm on at the time, but nothing more. I don't even think I have a ROM installed anymore.
What I've tried:
several Odin One-clicks
Heimdall One-click unbrick
Partitioning my external sd card to act as an internal one
ADB sideload
ADB push and install zip from sd card
The errors I run into the most are the "can't mount sd card" ones when I'm trying to flash a custom ROM in recovery. I guess my internal sd is corrupted somehow? Is there a way for me to fix this mess?
Click to expand...
Click to collapse
sd card issues are usually due to kernel, have you tried flashing a custom one to boot in recovery?
If your internal is dying, partitioning an external sd should work but since it's still not fully booting, I feel like that's not the issue. I had that happen to mine, tried many Odin and Heimdall, when finally one Heimdall worked (after like 10-15 different attempts). Shortly after my internal died though.
So I would start by flashing a kernel with Odin 1.7, see if you can boot in recovery (always took me a few attempts to get it). From there you can flash a custom ROM (I always suggest GamerzROM for the cappy but really it's personal preference). Otherwise, your 2nd option is bashing your head on Odin/Heimdall one-clicks lol
PS.: Just came across this if all else fails: http://forum.xda-developers.com/showpost.php?p=61479845&postcount=58
I have this exact same issue... Thank god I'm not alone! I wondered what that stupid "encryption failed' message was all about.
So I've done just about everything the above has done, except the problem is I continue to get a boot loop. The ODIN one-clicks all boot loop. Ive been able to install a custom kernel and CWM, and surprisingly my internal storage is still accessible, but when I try to install the CM9 that's on there it freezes at "opening update package".
So, stuck between a rock and a hard place. I can't put any other ROM's on the internal storage because I have no way of accessing it. Therefore I have to rely on a ODIN one-click. All of which boot loop or just fail outright. Is there a way to access the internal storage without fully booting android?