I've checked the other threads for solutions and I've tried many different things today but my phone still doesn't work, so I guess I should make a thread and ask you guys directly.
Ok, so my phone stopped working last night. It was running stock everything. Only upgraded to Froyo through Kies Mini a long time ago. Anyway, when I powered up the phone, it gets to the Galaxy S logo and then the screen dies. It's technically still on, since the four keys light up when I tap the screen. I took the battery out for a bit and put it back in, same thing. Logn story short, I tried to odin it back to stock JFD this morning and it didn't change anything. The screen goes to black right after the logos. Then I tried Eugene's Vibrant_Full_Froydin_AND_2E_Recovery_+SD_Fixed. It sorta worked. By that I mean, the phone loads up the OS and I got the home screen, but now it doesn't recognize the internal SD card. In fact, the notification gives me "Blank Internal SD card." In the Settings area, the phone storage read as either unavailable or 0.0 space. I tried to odin back to stock but then it gets stuck on Galaxy S logo again. I've tried this back and forth multiple times and it's still the same. Either it gets stuck on the logo or it doesn't recognize the internal sd card. I've tried it with repartition on and repartition off, but no difference.
So, are there any trick to fixing this? Thanks in advance!
Could you post the links to the files you are flashing? Honestly ODIN should have fixed it.
kawika said:
Could you post the links to the files you are flashing? Honestly ODIN should have fixed it.
Click to expand...
Click to collapse
Hi. I got the stock JVD from the Noob Guide (http://forum.xda-developers.com/showthread.php?t=849028). I followed the steps there to flash to stock through ODIN and I got the black screen/lighted buttons. Then I downloaded and flashed it with the one that came with the toolbox (http://forum.xda-developers.com/showthread.php?t=954509). same thing, black screen with lighted buttons. I also tried Eugene's ROMs (Eugene_SD+2E_JK2_Froyo - http://www.multiupload.com/12QAKU043I and the Froyo ~That does not Brick! - http://www.4shared.com/file/dJiyRz3v/EUGENE373_SamsungS_Froyo_PDA.html). Both links are from Eugene's forum page.
The only "success" I have so far is using Eugene_SD+2E_JK2_Froyo, but whenever it's loaded, I always get the "Blank internal sd card" notification and the phone storage is shown as unavailable. :\
Bump. I'm still trying to get this phone to work. :\
Give the following a try..
http://forum.xda-developers.com/showthread.php?t=1230059
Alex9090 said:
Give the following a try..
http://forum.xda-developers.com/showthread.php?t=1230059
Click to expand...
Click to collapse
Didn't quite work for me unfortunately.
1. When it's in recovery mode, I can't get adb to connect. I can only do it when it's loaded up.
2. When I tried to do print in parted, I get this error
Error: /dev/block/mmcblk0: unrecognised disk label
Click to expand...
Click to collapse
.
Do you have external card in the phone? First try taking it out and then reboot without it and see what happens. If that doesn't do anything..try the cleaning and repartitioning method posted by Br1ck'd ..
I have posted about it in several threads, including my own, so I figured I would finally put it in a central location. This is my FTDNB method for starting with a fresh, clean phone, without any ghosts of roms past popping up to cause you issues.
Download this first, and flash through Odin with your standard 512 pit file
http://eb-productions.proboards.com/...splay&thread=8
Then when it reboots to the recovery screen, pull your battery, reinsert it and boot up to dl mode, and flash the following, with your same pit file, and selecting repartition in Odin this second flash only:
http://eb-productions.proboards.com/...splay&thread=3
The first link there is Eugene's Froyo That Does Not Brick, but it doesnt work that well as a driver. As an eraser its great though! The second link is the Froyo JK2 leak, with fixed recovery and already rooted. If the first one didnt, the second flash will definitely put you back on Froyo bootloaders.
Thats my whole secret to keeping a clean phone and wiping out any ghosts. You can proceed from there in your desired direction (back to ZD or GZ preferrably) in a safe manner. Its always worked for me to clear up any oddness, and literally takes 15 minutes tops once you have the files downloaded.
Click to expand...
Click to collapse
I've tried that before. Eugene's Vibrant_Full_Froydin_AND_2E_Recovery_+SD_Fixed (Froyo JK2 leak) is the one that lets me load the system all the way through (better than running stock JVF which only gets me to the logo and then gets stuck). The internal sd card problem remains however. I get the "Blank internal sd card" notification. The phone can't function properly.
EDIT: I finally got the external sd card to work. Is there any program for me to fix my internal sd through my external sd card?
I'm having similar problems. Flashed back to stock Froyo using Heimdall (Mac only here), everything seemed fine, but when it all came back to life, I have no service and my Internal SD card is blank and cannot be reformatted.
It won't mount in the recovery tools, and so unable to format.
Any thoughts on how to restore functionality??
Bump. I'm still trying to get my phone working again. Thanks in advance!
If it just "happend" one day, then you're looking at a hardware failure. Flashing firmware can only make it worse.
xoxo1001 said:
I've checked the other threads for solutions and I've tried many different things today but my phone still doesn't work, so I guess I should make a thread and ask you guys directly.
Ok, so my phone stopped working last night. It was running stock everything. Only upgraded to Froyo through Kies Mini a long time ago. Anyway, when I powered up the phone, it gets to the Galaxy S logo and then the screen dies. It's technically still on, since the four keys light up when I tap the screen. I took the battery out for a bit and put it back in, same thing. Logn story short, I tried to odin it back to stock JFD this morning and it didn't change anything. The screen goes to black right after the logos. Then I tried Eugene's Vibrant_Full_Froydin_AND_2E_Recovery_+SD_Fixed. It sorta worked. By that I mean, the phone loads up the OS and I got the home screen, but now it doesn't recognize the internal SD card. In fact, the notification gives me "Blank Internal SD card." In the Settings area, the phone storage read as either unavailable or 0.0 space. I tried to odin back to stock but then it gets stuck on Galaxy S logo again. I've tried this back and forth multiple times and it's still the same. Either it gets stuck on the logo or it doesn't recognize the internal sd card. I've tried it with repartition on and repartition off, but no difference.
So, are there any trick to fixing this? Thanks in advance!
Click to expand...
Click to collapse
'I had a similar problem but later learned tht the SD card was actually damaged some how during flashing'
so try using a new SD card and Odin back to stock
I was running Bionix 1.31 on my Vibrant, everything was wonderful! Smooth speed, GPS working great and everything, so I decided to flash DoW14 kernel v1.1.1 HD so I could have voodoo color, sound and BLN. First few weeks phone was working great! Then started to act strangely… sometimes it rebooted or turned off by itself and no matter what earphones I plugged to listen to some music, randomly stopped playing just as if I unplugged the headphones. Then two weeks ago I was using my phone and I put it in my pocket… when I pulled it out to use it again, it was off. Turned it on and it was stuck on the booting screen, after like 10 minutes I realized it was soft-bricked. I can get to download mode, though, so I used AIO Toolbox and flashed back to stock with Odin, flash was successful but when I turned my phone on shortly after the Vibrant screen it rebooted and did the same over and over again. Tried to flash back to stock a few times now and I get the same.
I ended up hard-bricking the phone, so I took it to a guy with a Riffbox and even after restoring the bootloader and all, he's getting the exact same problem.
Your help is very much appreciated!
Sounds like either the battery is dying or the phone.
Update for the OP: After having the bootloader restored and flashing stock with Odin, I get the (data wipe failed) error and after the Vibrant Screen shows up, the phone turns off.
Already tried flashing Eugene's FTDB and it boots me into recovery, I use adb reboot and after the Galaxy S screen the screen turns off and the soft-buttons stay lit but doesn't boot. Flashed back to stock and I get the same data wipe error.
There is a video on youtube of a guy with the same problem, I wanted to share it here but xda wouldn't let me since I don't post much around here.
Your help is much appreciated.
Hello, i currently own a HTC EVO 3D GSM, fully rooted and S-OFF'd.
I'm running stock rom, without any major modifications.
Earlier today i was doing a nandroid backup, just before wanting to try out LeeDroid ROM. The nandroid went through just fine, then i rebooted the phone on to do a titanium backup & sync to my dropbox.
Now i used my app "Hot Reboot" to simply do a reboot into bootloader.
The app didn't work (dont know why), so i closed it down and did a manual shut down and then battery pull.
When i put the battery in, and tried to boot the phone into bootloader, it didn't start.
I tried to do a normal boot, didn't start.
I tried to plug it into my charger. The light didn't turn on.
I removed the back cover, removed battery, SIM card, SD card and tried to get rid of any possible dust (i was kind of panicing here).
Put it all back in, same result.
I tried switching SD card to my old stock 8gb sdc4 sandisk. This time it finallly booted and everything worked like before.
I turned the phone off, and replaced the 8gb SD card with my 32gb SD card. Now this also worked fine.
I have no idea how or why this happened, but if anyone could shed some light on why/how it happened? Maybe i could avoid it happening again, because i was kinda freaking out when i thought i had a possible brick.
- Moon
Continuum Brick?
I have been reading since 2pm today. I'm lost in threads and advice about a bricked phone. I have a Continuum that shows a fuzzy screen. I can't see to get a download mode. The options are off or pixelated/fuzz screen. Is soldering still required? I was attempting to use CWM. I am not sure bad cable or what but it went down hill. My Win7 PC shows 0bytes free on the Continuum. I apolgize if this is the wrong area for my questions. I successfully rooted an Epic and a Kyocera Echo without too much trouble. I appreciate any thoughts, comments, and suggestions. Thanks in advance!!
This is my sister's phone so I may not be alive in the morning j/k
Today I have downloaded Ubuntu, Android SDK, One Click Unbrick, Resurrection, Java, and a host of other Android related files. I was SO sure all my clicking would bring me back to stock.
Ok, so I wanted Ice Cream Sandwich on my Samsung Galaxy S Vibrant SGH-T959.
I found a Youtube video and eventually installed the passion ICS rom on my phone successfully. Then, I inserted my external sd card and took it back out with out unmounting it. This made my phone want to wipe all my (internal) sdcard data. So stupidly, I did. Luckily I have a recent backup. But then I did a reboot, and it said that the encryption failed and I needed to reset my phone. I complied. Then it would only go into the mod recovery screen, since I had no rom to reinstall (my sdcard wouldn't mount for some odd reason, even after I tried repeatedly). So I decided to start over. I used odin to revert it to what it came like. I unplugged it because it got stuck at cache.rfs and soft-bricked it. Luckily I know how to fix this so I got it back into odin, and I got it to work until it would have a blue reset box in the top left corner, and it said I removed my device. My phone then tried to reboot. It showed the vibrant screen, then crashed and showed the little swirl thing that it does before it shows the green charging battery, it would show that, then show that with the battery in the background, then crash and start again, never getting to the green battery. I tried unplugging it and booting it that way... it went to the vibrant screen and crashed yet again. Also can't get it to display the pink animation. I tried the odin thing again just to get the same result. I tried to boot into recovery mode and it won't even do that. It wont show the terminal thing to save its life. Any ideas? I can get it to the download screen. Any hope? (sorry for the in-depth story, but I thought it might help someone pinpoint what was wrong) I am sporting windows xp. Losing data isn't a problem for either my internal sdcard or external sdcard seeing as I have complete backups on my computer.
Thanks!
Help Please!
UPDATED!
I just tried again and it showed the terminal thing for the first time since I used odin. It will now show the green battery screen, it went into terminal and looked like it was doing stuff and it said that the data wipe failed. Boot Pattern still the same, goes to the vibrant screen and then crashes.
UPDATED YET AGAIN!
It will now go into recovery.
AND AGAIN
Now after I wiped it etc. in recovery mode and rebooted and now it just shows the vibrant screen and crashes over and over on its own.
here's a work around fix
http://forum.xda-developers.com/showthread.php?t=1580902&highlight=encryption
Not-Working Links, noncompaitibility with windows xp it doesn't restore to 2.1
So I tried that a bit ago and the pit file link to download doesn't work. So I used the default one for the vibrant. Didn't successfully run 2.1. Still same problem. Oh, and also, the whole command prompt open in that folder doesn't work on xp, only windows 7 or vista, I found a fix, but still it doesn't recognize adb as a command that is acceptable or whatever.
Thanks, but any other help?
I try Odin and when my phone shows data formatting..... it says data wipe failed afterwards. I think this is the problem.
blu422 said:
So I tried that a bit ago and the pit file link to download doesn't work. So I used the default one for the vibrant. Didn't successfully run 2.1. Still same problem. Oh, and also, the whole command prompt open in that folder doesn't work on xp, only windows 7 or vista, I found a fix, but still it doesn't recognize adb as a command that is acceptable or whatever.
Thanks, but any other help?
I try Odin and when my phone shows data formatting..... it says data wipe failed afterwards. I think this is the problem.
Click to expand...
Click to collapse
Looking back... I didn't know what adb was and now that I have the android SDK installed I'm sure I would be able to fix. Too bad I sold it for an insanely low price. Ugh.
Galaxy S3 T999 rooted and flashed more than daily.
Well, my problems with recoveries are sorta of a jokle by now, but I still feel compeled to share my experiences so maybe anyone can tell me what the hell is happening on my phone....
So as I said some time ago, I experienced problems with the PhilZ recovery, which I solved swapping to CWM version 6.0.3.2. The problem was the infinite bootloop of the Samsung Galaxy GT-I9300 logo, the black screen, which did not allow me to access to the recovery. But inmediatly after flashing to the old CWM the problem was gone away. Also, in a case of a possible kernel panic due to doing some stuff with Xposed modules CWM was the only recovery I could get access into.
Now, the problem is the following. Yesterday I installed the CWM Touch version 6.0.4.7, which I got from this thread http://forum.xda-developers.com/showthread.php?t=2052091. After installing it everything was normal. However, after one hour or so the phone screen wouldnt turn off when I pressed the Power Button. In fact the Power Menu appeared, but the screen, as I said, dindt get to sleep mode. To top that, after freezing for a second the phone suddenly turned off, and then get to the infamous black screen with the model logo looping and looping.
Fortunately, after pressing Volume Up+Menu+Power I could get to the Recovery, but not after quite some seconds pressing these three buttons. And in some times it would not get me to the recovery, but instead completely rebooting the phone and working again. Just to, in half an hour, freezing and looping again and again and again.
This problem happened to me with virtually every ROM I installed, being Neat ROM, Archi, and even CM11 from Temasek. Nothing would solve that problem. The only remedy I had was a temporary one, which consisted on uninstalling and reinstalling again the kernel (I used boeffla) and the problem would not disappear that way. Also, when wiping data, for some weird reason it gave an error message while wiping the /preload partition, in the Mounts and Storage menu.
Until I got home today, and then flashed through Odin the old CWM Touch version 6.0.3.2, that finally stopped the problems. I tested it by pressing the Power buton again and again and it hadnt redirected me to the black bootloop screen. Seriously, I am wakelocking my phone on an intensive basis and nothing has happened for now, and I think it probably wont happen again. Maybe it takes three seconds, maybe the Power Menu displays again, but no bootloop again.
So I ask to you, what is happening on my phone that it wont run recoveries younger than my old 6.0.3.2
IMPORTANT EDIT: THE PROBLEMS ARE NOT SOLVED YET
Some hours ago, I was chatting using Whatsapp while charging the phone on an USB charger, when it suddenly suffered the black screen bootloop again. This time was unexpected, since I was using the CWM Touch 6.0.3.2, the one supposed to work fine. So for now I feel completely finished. My phone is officialy into a unsolvable problem.
But, thinking about it, there were some things that might help you:
-This time I did not uninstall and reflash the kernel: When I got to the recovery menu, I just selected "reboot", as such, without flashing anything else, and the phone then worked as fine, booting into the ROM bootanimation screen (this time the Neat ROM bootanimation). So basically a manual reboot through Recovery got me out of this. Also, I kept using the phone until now and there werent more problems, at least for now.
-As far as I can recall, these problems started some weeks ago, when I accidentally formated the internal SDcard. I was using PhilZ Touch Recovery and flashing a ROM as usual, when I selected without knowledge the option "Format /data and /data/media (sdcard)" in the Mounts and Storage menu. I did this after doing the usual Full Wipe before flashing an new ROM, and after that I had to turn off the phone in order to insert a ROM in the external SD card to flash it through the recovery to make the phone working again. But when I wanted to get back to the recovery, I couldnt. I had to flash CWM 6.0.3.2 because it was the only recovery that let me access to the recovery menu-the already installed PhilZ wont allow me to access to the recovery menu. So in CWM I got to the External SD card and flashed a Neat ROM, and got the phone working again. And after that I reflashed PhilZ. But since then the phone started to experiment these freezes, reboots and bootloops. One happened to me when in College, and couldnt get out of it because PhilZ wont respond to the Manual Recovery command. I had to wait to get home, to reflash the CWM 6.0.3.2 recovery through Odin because that Recovery was the only responding. And in that moment it did well, and didnt have more reboot problems. Until I flashed 6.0.4.7, which is why I am here.
-Lastly, about the reason I trust in CWM 6.0.3.2: Some time ago, when flashing Blackbox ROM 2.0.2, I downloaded the Gravity Box module from Xposed, and installed it alongside with other modules, which, supposedly, caused a kernel panic problem that sent my phone into the dreaded black bootloop again. I was using PhilZ recovery, and as you may expect now, I couldnt get access to it, so I flashed the CWM 6.0.3.2 recovery, which let me access to a recovery. I too flashed TWRP, but it accessed for one second to the recovery menu, and then faded away, returning to the bootloop logo screen. So basically PhilZ and TWRP failed me during that kernel panic problem, while CWM stood the problem. And thats why I turn to this recovery when everything else fails.
And thats why I am troubled now, because this recovery is showing signs of failure
Try cwm 6.0.4.4 as I've used this for all sorts of Roms and have no problems
andrewwright said:
Try cwm 6.0.4.4 as I've used this for all sorts of Roms and have no problems
Click to expand...
Click to collapse
I used 6.0.4.7 and I had the problems previously described....I mean, I used a more updated version than the one you propose. Do you believe its gonna work better?
And thats why I will stick to 6.0.3.2 until someone tells me whats happening. If an updated version of 6.0.4.4 gives me problems...well, go imagine.
I can confirm that 6.0.4.4 works. I Also tested it for nandroid bk up and restore and it works. I have flashed the latest tw 4.3 and the old 4.1.2 and aokp/cm/aosp 4.4.2 and all flashes with no errors. I have 6.0.4.7 but not tested it this is why I said to you to use 6.0.4.4
Only thing I haven't tested is adb.
andrewwright said:
I can confirm that 6.0.4.4 works. I Also tested it for nandroid bk up and restore and it works. I have flashed the latest tw 4.3 and the old 4.1.2 and aokp/cm/aosp 4.4.2 and all flashes with no errors. I have 6.0.4.7 but not tested it this is why I said to you to use 6.0.4.4
Only thing I haven't tested is adb.
Click to expand...
Click to collapse
Interesting. And where do I get the 6.0.4.4? I dont see it neither in the new CWM thread nor in the old one.
Look down
here. zip so just flash in recovery
andrewwright said:
here. zip so just flash in recovery
Click to expand...
Click to collapse
I apreciate your help, but now some new problems have emerged, and I need more help, because maybe I might have a corrupted partition or such, who knows.
With this quote, I too try to bump the thread, in order to gain more attention to my new problems
If anyone is interested, please look the OP, as it has been edited to describe the new problems.
Best thing to do now is go bk to stock firmware with Odin and see if any problems persist. Totally stock for a few days.
andrewwright said:
Best thing to do now is go bk to stock firmware with Odin and see if any problems persist. Totally stock for a few days.
Click to expand...
Click to collapse
I will try that in a few weeks, I am a bit busy by now to test anything...
Fortunately, the CWM 6.0.3.2, while not infallible, works better than the other recoveries...today I only had one bootloop problem, solved by simply rebooting from the recovery....I can keep it for one week or two, it doesnt worry me for now.
Also, there is a guide to reflash stock? Sometimes I reflashed stock, but it kept bootlooping on the Samsung animation...probably because I didnt know how to wipe data while reflashing stock. Thats a little problem I have with reflashing stock, any help is appreciated.
Odin wipes the phone while flashing. What rom are you on? Custom
Well, I have to bump this post again because I am having the same problems again.
I am using CWM 6.0.3.2 as my current recovery. Today, I was browsing the Facebook app when I pressed the Power Button. Then, a lag of 2 seconds happened, the Power Menu displayed on screen, and the phone got into the black boot screen again. But this time I could not get to the recovery. Whenever I pressed Volume up+Power+Menu there appeared a black screen featuring the CWM logo and then it returned again to the black boot screen again. So what I did was to remove the battery, then eject the Exterior SD Card (A Lexar, 32 gb) and put again the battery in its place. The phone started all normal again, and when I put again the SD Card it continued to work normally.
So, what do you think its happening? Not even my old recovery, the one which works better for me, is reliable anymore. Could this be a component of my phone failing? Particulary the emmc chip? Or its not a hardware problem? Should I sent the phone to reparation?
How much data do you have on ext sd? Maybe phone is scanning ext sd and if alot of data is there that maybe the cause of the reboots. Try a different sd for a few days or none at all. See if you have the problem.
andrewwright said:
How much data do you have on ext sd? Maybe phone is scanning ext sd and if alot of data is there that maybe the cause of the reboots. Try a different sd for a few days or none at all. See if you have the problem.
Click to expand...
Click to collapse
I have almost 29 gb on the sd, but I had that data since the very first day I bought the card....thats more than one year ago. And I started having the problems since february of this year....
The problem has not reappeared. But what I still have is an insane battery consumption. See, I use apps like Facebook and Twitter, but I too use Greenify to hibernate them. It even drains too much battery by using the web browser. And I repeat, those problems trace back to February...which is the month when I accidentaly formatted the internal SD Card...
One year old + battery using Facebook and twitter and all the rest of them very power hungry apps are no good for battery life. Greenify uses battery, people forget that too. Remove all the apps above and test. Also if anything formatting int SD will speed up the phone not slow it down. It get rid if all the bit left over from ROMs/Recovery's/kernel's. Formatting int sd is good for the phone once in a while. Just remember to back up data first
andrewwright said:
One year old + battery using Facebook and twitter and all the rest of them very power hungry apps are no good for battery life. Greenify uses battery, people forget that too. Remove all the apps above and test. Also if anything formatting int SD will speed up the phone not slow it down. It get rid if all the bit left over from ROMs/Recovery's/kernel's. Formatting int sd is good for the phone once in a while. Just remember to back up data first
Click to expand...
Click to collapse
Thanks! Whenever I can, I will try those tips for battery saving.
But what still puzzles me is the "Sudden reboot problem". It vaguely happens, but when it does I am basically screwed, and each time the reboots seems to get worse from recovering....Also, the reboot problems started after formatting the int sd card for first time. And, after that, I remember that, when I wiped data for installing a new ROM, it gave me "(E: unknown volume for path [/sd-ext])" or, something similar. Does this help you for identifying my problem?
OK, now I am royally screwed
I have suffered another sudden bootloop problem, and this time, even by removing the ext SD Card, phone doesnt restarts. Also, I cant access to the Recovery Menu. It does appear for a while and then fades away. But the worst part is that I cannot get into the Download Menu. When I get to the select screen, when I cant choose between Continue and Cancel, the Volume buttons doesnt work. I can not get into Continue button. And then it restarts.
So this time I can not even access to the Download Menu.
I am using the same ROM as before: Neat ROM 6.7 with CWM Touch 6.0.3.2 and Boeffla Kernel
I dont know if I can even send the phone to repair, as seen that I may have the Binary Counter...and I cant even access to Download.
Please, really, help me to get out of this, so I can factory reset this.
Take the battery out then hold buttons for download mode and while holding these buttons put the battery back in and pray mate. Not being able to get into download/recovery mode as you know is really not good. Maybe a jig to force it to download mode.
andrewwright said:
Take the battery out then hold buttons for download mode and while holding these buttons put the battery back in and pray mate. Not being able to get into download/recovery mode as you know is really not good. Maybe a jig to force it to download mode.
Click to expand...
Click to collapse
I did that, and I got into the Download Menu. But the menu was frozen as usual. I could not access to the Odin Menu. It didnt matter which option I chosed, since both of them didnt work and the menu would still be frozen, and then restarting the phone a few seconds later. I mean, I got to the screen where you can choose to get to Download Mode or to restart the phone, and it still was a stuck screen, no matter what I chose, the options did not work, and then the phone restarted again.
And I have no jig next to me. So, I am screwed. For real.
Im going to take it to the store where I bought it, which is near where I live...To see if they can do something. Otherwise...I think I will throw away this phone. Its been almost 2 years, and recently it started to fail, probably because of a crappy emmc chip...that store sells the Moto G, which is great, since I dont plan to waste a lot of money on a new phone, watching how this has ended.
And it sucks that I can not recover the data in the Internal SD