Develop Bugs

***Emergency Thread*** Here To Help!

I have created this thread for all you SG-SIII Noobs & Senior Members!
The purpose of this thread is to limit the number of (sometimes useless) threads, that are created over a simple problem that can easily be solved by READING OR SEARCHING.
This is the Emergency thread!
*Did you run into a problem and need quick assistance?
*Do you have a question or concern about your SG-SIII device?
Don't panic just ask here and I or WE THE SG-SIII COMMUNITY will gladly help!

In case of emergency!

Okay I guess I'll be the first to post.
About an hour ago my phone shut off at 26% battery (16gb galaxy S3 running CM10.1 nightly 01/16). As I went to turn it back on it will boot into the CM splash screen spin a few times and just shut off. I attempted to charge it, and turn it back on but same thing. After that an attempt to get into CWM, which I was able to get in and it shut off while I was in it. I also tried putting the phone in download mode and about the same time frame it took for the other attempts resulted in a shut down.
Any advice? Or am I stuck doing a warranty exchange?

Rayman0625 said:
Okay I guess I'll be the first to post.
About an hour ago my phone shut off at 26% battery (16gb galaxy S3 running CM10.1 nightly 01/16). As I went to turn it back on it will boot into the CM splash screen spin a few times and just shut off. I attempted to charge it, and turn it back on but same thing. After that an attempt to get into CWM, which I was able to get in and it shut off while I was in it. I also tried putting the phone in download mode and about the same time frame it took for the other attempts resulted in a shut down.
Any advice? Or am I stuck doing a warranty exchange?
Click to expand...
Click to collapse
Sounds like its your battery not a hardware problem. Leave it overnight or a couple hours charging and if it indeed boots up its your battery.
If it doesn't then flash stock and test it if the same result then call up that Warranty. I've seen this same issue with other devices where the battery dies at 50%+ and usually replacing the battery fixes the problem. Test your battery for overheating or swollen.
Sent from my HTC One S using Tapatalk 2

...Awesome... said:
Sounds like its your battery not a hardware problem. Leave it overnight or a couple hours charging and if it indeed boots up its your battery.
If it doesn't then flash stock and test it if the same result then call up that Warranty. I've seen this same issue with other devices where the battery dies at 50%+ and usually replacing the battery fixes the problem. Test your battery for overheating or swollen.
Sent from my HTC One S using Tapatalk 2
Click to expand...
Click to collapse
The battery isnt swollen, thats one of the things I checked also. I thought it might be that, the only other option I have is to try a different battery. The good thing is I work in a tmobile store so im gonna give that a shot tomorrow.

Sv: ***Emergency Thread*** Here To Help!
Can you start it without battery connected to the wall charger? If so try wipe cache. Or after reflash ROM.
Sent from my LG-P990 using xda app-developers app

lintz said:
Can you start it without battery connected to the wall charger? If so try wipe cache. Or after reflash ROM.
Sent from my LG-P990 using xda app-developers app
Click to expand...
Click to collapse
Phone wont boot without the battery in, and with it in I cant stay in recovery without with rebooting.

Rayman0625 said:
The battery isnt swollen, thats one of the things I checked also. I thought it might be that, the only other option I have is to try a different battery. The good thing is I work in a tmobile store so im gonna give that a shot tomorrow.
Click to expand...
Click to collapse
Even better then lol just test it out at work. I'm about 80% its your battery specially if you OV/UC.

I have the t-mobile US t999.
Last night I was having an odd issue with the networking dropping. I've had the phone for about a month, modded since day 1 with a CM10 variation of a rom (sorry, I forget the exact rom). I had no issues whatsoever up until this point. After a few restarts thinking maybe it was a fluke issue with the network, or network signal in my room, the phone forced itself into emergency call mode only. I couldn't get it to come out.
So I decided I was going to odin on a stock rom as I could get it into download mode, that went through successfully. When the phone boots, I get the android taking off (Tmobile 4g) logo. Then the white samsung logo, and it doesn't go beyond this. I know this can take long so I left it there for about an hour, nothing. The phone also displays a blue led the entire time it's hanging as well.
Also worth noting, when I attempt to boot into recovery it just vibrates over and over.
Not sure what my next steps should be. Any help would be greatly appreciated.

heartspains88 said:
I have the t-mobile US t999.
Last night I was having an odd issue with the networking dropping. I've had the phone for about a month, modded since day 1 with a CM10 variation of a rom (sorry, I forget the exact rom). I had no issues whatsoever up until this point. After a few restarts thinking maybe it was a fluke issue with the network, or network signal in my room, the phone forced itself into emergency call mode only. I couldn't get it to come out.
So I decided I was going to odin on a stock rom as I could get it into download mode, that went through successfully. When the phone boots, I get the android taking off (Tmobile 4g) logo. Then the white samsung logo, and it doesn't go beyond this. I know this can take long so I left it there for about an hour, nothing. The phone also displays a blue led the entire time it's hanging as well.
Also worth noting, when I attempt to boot into recovery it just vibrates over and over.
Not sure what my next steps should be. Any help would be greatly appreciated.
Click to expand...
Click to collapse
after you odin, you need to wipe data/ factory reset to boot. If you can't get into recovery ( Power, Home Button, and Volume Up), then try reflashing your stock image in Odin and check your MD5 sum, so you can rule out a bad download

Thanks for the reply, I'm re-downloading the stock rom now to verify it's integrity and do a new flash. I cannot get into recovery, so we will see after the new flash. Pleading ignorance on one subject, how would I go about checking the MD5 sum to verify the file has no issues?
Additionally I did try to Odin recovery and still could not boot into it, this was however before attempting to re-download and flash a stock rom again.
**Edit//Update** Re-downloaded and flashed stock rom, was able to get into recovery and wipe, booted up fine.

Wow.. great idea for a thread and THANK YOU!!
Perfect timing too cause i need a little help please.
I am not new to android but new to samsung (WOW, didnt realize it would be so different from HTC ont he rooting and flashing side of things).
Long story short. I have a tmo s3. Bought it today and wanted to root. phone was working perfectly as it shoudl on stock rom unrooted. I downloaded the tool kit v7, used that to root adn install TWRP and rebooted into the stock rom that is now rooted. Still everything working perfect.
Here is what i did next and where the issues start.
Downloaded Synergy r290, went to recovery.
Wiped Cache, Dalvik, Data, and System (made a backup first)
flashed the rom and rebooted to system
However, nothing ever happened. I see the samsung logo, then all goes black and nothing happens (left it there for 10min)
I cant seem to get back into recovery holding vol up, home and power either and have no adb access to use that. I AM able to get into download mode which i know i can fix my problem here with odin, but i am just not sure what to flash and where.
Is there an easier way??
Thanks in advance for any help!

frettfreak said:
Wow.. great idea for a thread and THANK YOU!!
Perfect timing too cause i need a little help please.
I am not new to android but new to samsung (WOW, didnt realize it would be so different from HTC ont he rooting and flashing side of things).
Long story short. I have a tmo s3. Bought it today and wanted to root. phone was working perfectly as it shoudl on stock rom unrooted. I downloaded the tool kit v7, used that to root adn install TWRP and rebooted into the stock rom that is now rooted. Still everything working perfect.
Here is what i did next and where the issues start.
Downloaded Synergy r290, went to recovery.
Wiped Cache, Dalvik, Data, and System (made a backup first)
flashed the rom and rebooted to system
However, nothing ever happened. I see the samsung logo, then all goes black and nothing happens (left it there for 10min)
I cant seem to get back into recovery holding vol up, home and power either and have no adb access to use that. I AM able to get into download mode which i know i can fix my problem here with odin, but i am just not sure what to flash and where.
Is there an easier way??
Thanks in advance for any help!
Click to expand...
Click to collapse
If you absolutely can't get into recovery to restore your backup..
Flash the UVDLJA root66 file in this thread http://forum.xda-developers.com/showthread.php?t=1949687 via odin. You will have the latest UVDLJA JB update, and will be rooted. From there, install goo manager from the play store to flash TWRP.
After that you're all set to flash whatever you want (just make sure it's for the Tmobile s3).
Sent from my SGH-T999 using Tapatalk 2

Towle said:
If you absolutely can't get into recovery to restore your backup..
Flash the UVDLJA root66 file in this thread http://forum.xda-developers.com/showthread.php?t=1949687 via odin. You will have the latest UVDLJA JB update, and will be rooted. From there, install goo manager from the play store to flash TWRP.
After that you're all set to flash whatever you want (just make sure it's for the Tmobile s3).
Sent from my SGH-T999 using Tapatalk 2
Click to expand...
Click to collapse
Ok, easy enough, but do i put that in the PDA field in Odin or phone?
This sounds MUCh easier than what i thought i would have to do.. thanks a ton!

frettfreak said:
Ok, easy enough, but do i put that in the PDA field in Odin or phone?
This sounds MUCh easier than what i thought i would have to do.. thanks a ton!
Click to expand...
Click to collapse
Just upload the file to PDA and hit start. Make sure to let it finish completely, once the phone reboots, it's done.
Sent from my SGH-T999 using Tapatalk 2

Flashing stock with Odin can take up to ten minutes its normal like the man said above just let it do its thing

Towle said:
Just upload the file to PDA and hit start. Make sure to let it finish completely, once the phone reboots, it's done.
Sent from my SGH-T999 using Tapatalk 2
Click to expand...
Click to collapse
Worked great! Thanks!!

http://forum.xda-developers.com/showthread.php?t=2113883
Let's see if you have any solution for me?

Weird problem. When I set kernel frequencies on my phone, they at some point get locked at the maximum frequency. This has happened every time I flash a new ROM or kernel, and I'm worried that it will soon start to affect the battery. I'm using the msmdvcs governor on both kernels that I've tried (stock and faux)

ohshootrawr said:
Weird problem. When I set kernel frequencies on my phone, they at some point get locked at the maximum frequency. This has happened every time I flash a new ROM or kernel, and I'm worried that it will soon start to affect the battery. I'm using the msmdvcs governor on both kernels that I've tried (stock and faux)
Click to expand...
Click to collapse
Do u happened to have apps that control frequency like setcpu etc? They might be conflicting each other
Sent from my HTC One S using Tapatalk 2

an unseen before problem with HOX- phone dies when usb pulled off

Hi and firstly. thanks for your help!!
A friend gave me his hox for a repair after he tried putting in a new rom the wrong way...
so ive managed to put the rom he wanted (revolution hd 22) and the phone is now working ok...
calls, data, heavy apps... all works fine.
UNLESS- and thats the awkward part- unless you plug the usb data\charging cable out.
once the usb is out- the phone freezes for 30 seconds> reboots >than works fine for 30 seconds and than freezes whole over again
-this can happen until battery dies.
ive tried putting a new RUU
ive tried different kernels
ive tried wiping anything with fastboot or from the recovery
also tried TWRP and CWM- altough it dosnt even seems to be related
ive tried locking, unlocking, clearing fastboots cache... and NOTHING...
Now, the most weird thing, is when the phone is in recovery mode- it works on battery just fine!!
it can install my roms and kernels ok!
problem only occours when system goes up- than it will work only if its connected.
because of that- i can tell this isnt a hardware problem, and there must be a solution
does anyone has a clue with my issue please?

pazush said:
Hi and firstly. thanks for your help!!
A friend gave me his hox for a repair after he tried putting in a new rom the wrong way...
so ive managed to put the rom he wanted (revolution hd 22) and the phone is now working ok...
calls, data, heavy apps... all works fine.
UNLESS- and thats the awkward part- unless you plug the usb data\charging cable out.
once the usb is out- the phone freezes for 30 seconds> reboots >than works fine for 30 seconds and than freezes whole over again
-this can happen until battery dies.
ive tried putting a new RUU
ive tried different kernels
ive tried wiping anything with fastboot or from the recovery
also tried TWRP and CWM- altough it dosnt even seems to be related
ive tried locking, unlocking, clearing fastboots cache... and NOTHING...
Now, the most weird thing, is when the phone is in recovery mode- it works on battery just fine!!
it can install my roms and kernels ok!
problem only occours when system goes up- than it will work only if its connected.
because of that- i can tell this isnt a hardware problem, and there must be a solution
does anyone has a clue with my issue please?
Click to expand...
Click to collapse
try a custom kernel...if that doesn't wprk just go into a store or so and ask there what could the issue...if it wasn't there when he had the stock rom on it than he had a really bad flash and it is maybe rom or mainboard problem in some way

Sounds like a power issue. I think its hardware

Yep its maybe HW problem but why he can charge then in Recovery Mode
Solution:Your friend could charge in Recovery Mode and then boot up to the Rom
or you could try another ROM (your last hope ?)

Hey, thanks for helping,
There is no problem with charging it...
Problem is it cant work on battery
Only recovery works with bat power.
When using rom on bat- it freezes.
Edit: oh and one more thing, the phone is almost brand new, it has been used for only one week and worked ok. Until my friend took it to a store here for adding other lang...
Sent from my GT-I9300 using xda app-developers app

Recovery mode is taking less battery power then if you are using it with a rom booted up... Maybe the battery is now broken or the connectors are bad or so...
And what do you mean with adding other lang?
Gesendet von meinem HTC One X mit Tapatalk 2

One-X-master said:
Recovery mode is taking less battery power then if you are using it with a rom booted up... Maybe the battery is now broken or the connectors are bad or so...
And what do you mean with adding other lang?
Gesendet von meinem HTC One X mit Tapatalk 2
Click to expand...
Click to collapse
i thought about it, but i think installing a new rom via recovery is taking more power
than just staring at the regular booted screen while its on idle
30 seconds of staring- freeze and than reboot...
i just cant figure how its a hardware issue, the device is almost new... how is it possible that im the first one meeting this issue?
and i ment my friend wanted to add another os language that didnt come stock (rom change)

pazush said:
i thought about it, but i think installing a new rom via recovery is taking more power
than just staring at the regular booted screen while its on idle
30 seconds of staring- freeze and than reboot...
i just cant figure how its a hardware issue, the device is almost new... how is it possible that im the first one meeting this issue?
and i ment my friend wanted to add another os language that didnt come stock (rom change)
Click to expand...
Click to collapse
try a complete full wipe ...wipe system, data, dalvik-cache and cache...and before maybe try factory reset from bootloader and be sure to save all content from sdcard to pc ...if that doesn't help try the complete full wipe ...if that doesn't help it's an hardware issue and he maybe pulled the caable wrong out or so or i really don't know...

One-X-master said:
try a complete full wipe ...wipe system, data, dalvik-cache and cache...and before maybe try factory reset from bootloader and be sure to save all content from sdcard to pc ...if that doesn't help try the complete full wipe ...if that doesn't help it's an hardware issue and he maybe pulled the caable wrong out or so or i really don't know...
Click to expand...
Click to collapse
hey, ive done that already.
whats the deepest way to rewrite the onex's software?
i tried ruu, is there anything other i dont know?

pazush said:
hey, ive done that already.
whats the deepest way to rewrite the onex's software?
i tried ruu, is there anything other i dont know?
Click to expand...
Click to collapse
Go into a store or ask and say you have this problem or your friend have to go and if he ask if you unlocked say yes but this problem was even on stock therefore you flashed a custom Rom because you thought it will fix it...
Gesendet von meinem HTC One X mit Tapatalk 2

Thank you for trying to help again,
But it isnt resonable to determine the phone mainboard is dead, all signs shows its software...
If it helps, the hox makes a long beep, or drawing stripes on the screen sometimes before it restarts, the other times it just freezes.
Sent from my GT-I9300 using xda app-developers app

pazush said:
Thank you for trying to help again,
But it isnt resonable to determine the phone mainboard is dead, all signs shows its software...
If it helps, the hox makes a long beep, or drawing stripes on the screen sometimes before it restarts, the other times it just freezes.
Sent from my GT-I9300 using xda app-developers app
Click to expand...
Click to collapse
Flash completely another Rom...and also other kernel...some ppl had those issues too but it was problem with mainboard maybe its the mainboard problem...
Gesendet von meinem HTC One X mit Tapatalk 2

Phone constantly reboots and not able to format

Hey guys I have a weird problem. When i turn on the phone, it reboots itself after several second. When i take a photo or make a backup with titanium backup at that time, all data goes away after a reboot. I tried doing a factory reset and i tried to format all the data partition and it is no good. I am really frustrated because i cannot use my phone for more than a week and i cannot afford a new phone right now. Hope you guys can help me.
Cheers

karakalem said:
Hey guys I have a weird problem. When i turn on the phone, it reboots itself after several second. When i take a photo or make a backup with titanium backup at that time, all data goes away after a reboot. I tried doing a factory reset and i tried to format all the data partition and it is no good. I am really frustrated because i cannot use my phone for more than a week and i cannot afford a new phone right now. Hope you guys can help me.
Cheers
Click to expand...
Click to collapse
First try to flash stock via fastboot. If that fails try to lock your bootloader with fastboot with this command: fastboot oem lock. If it has no effect your emmc is fried..
Sent from my Galaxy Nexus using XDA Premium HD app

mrgnex said:
First try to flash stock via fastboot. If that fails try to lock your bootloader with fastboot with this command: fastboot oem lock. If it has no effect your emmc is fried..
Sent from my Galaxy Nexus using XDA Premium HD app
Click to expand...
Click to collapse
I tried flashing stock system.img and it gets stuck in writing system

karakalem said:
I tried flashing stock system.img and it gets stuck in writing system
Click to expand...
Click to collapse
I waited a little bit longer and everything went well. I rebooted and the phone booted into my old custom rom with all my apps installed. I even got the same sms from 10days ago again like it is the first time. I played with it a little bit and it made a popping sound with instant bright screen and rebooted itself again. I think this is definitely a hardware issue what are your opinions?

karakalem said:
I waited a little bit longer and everything went well. I rebooted and the phone booted into my old custom rom with all my apps installed. I even got the same sms from 10days ago again like it is the first time. I played with it a little bit and it made a popping sound with instant bright screen and rebooted itself again. I think this is definitely a hardware issue what are your opinions?
Click to expand...
Click to collapse
Use the flash-all.bat.. If that doesn't work execute this command: fastboot oem lock. If your bootloader isn't locked your emmc is fried.
Sent from my Galaxy Nexus using XDA Premium HD app

mrgnex said:
Use the flash-all.bat.. If that doesn't work execute this command: fastboot oem lock. If your bootloader isn't locked your emmc is fried.
Sent from my Galaxy Nexus using XDA Premium HD app
Click to expand...
Click to collapse
I tried flash-all.bat and it didn't worked. Then I tried to lock the bootloader. It was a success, I even tried to unlock it and it said are you sure bla bla bla. I clicked no and rebooted and it booted to my same old friggin ROM!! I rebooted into the fastboot and it says unlocked again. I think that my phones emmc chip locked itself in a particular state and it doesnt allow any changes to be made on it. What should I do next? Is emmc repairable or should i start to searching for a new phone?

karakalem said:
I tried flash-all.bat and it didn't worked. Then I tried to lock the bootloader. It was a success, I even tried to unlock it and it said are you sure bla bla bla. I clicked no and rebooted and it booted to my same old friggin ROM!! I rebooted into the fastboot and it says unlocked again. I think that my phones emmc chip locked itself in a particular state and it doesnt allow any changes to be made on it. What should I do next? Is emmc repairable or should i start to searching for a new phone?
Click to expand...
Click to collapse
I have the exact same issue.
The phone shut itself down at some random point - if it is being charged or on a laptop it seems to be a bit more stable.
When it reboots, it goes into the status from the day it first happened. It asks to update apps again and even though they are updated, the next time the phone starts, it happens all over. If I delete an app, it will be there again after reboot/relaunch.
All the settings remain the same.
My phone is currently unlocked but not rooted and runs stock 4.3. I tried to flash stock 4.3 again and even 4.2 - later I tried Cyanogen. I use CWM to format /data, /system, /sdcard, deleted cache and devlink cache multiple times.
Each time it boot, it remains the same background, settings, and so on....

Bumping it up - really hope that someone has an idea what I could try to fix this...

Tomfk said:
Bumping it up - really hope that someone has an idea what I could try to fix this...
Click to expand...
Click to collapse
I gave it to warranty and they said the eMMC chip is broken. They are going to fix it soon. But I already got myself an LG g2 so it does not matter anymore lol. Try the warranty and good luck.

karakalem said:
I gave it to warranty and they said the eMMC chip is broken. They are going to fix it soon. But I already got myself an LG g2 so it does not matter anymore lol. Try the warranty and good luck.
Click to expand...
Click to collapse
How much did you pay for a new emmc? (i've the same problem )

lo97 said:
How much did you pay for a new emmc? (i've the same problem )
Click to expand...
Click to collapse
It's dollar equivalent is about 50$. Normally they didn't accept my phone to warranty but I know a guy, who knows a guy who knows another guy that works in Samsung Turkey so I got that worked out:laugh:

Root issue/ unbootable

I found my phone dead this morning and tried plugging it in. The screen reacted by showing a loading battery logo that seems to have froze. I booted into recovery and tried to factory reset but it shows that nothing is mounted. When trying to boot out of recovery it doesn't get past the galaxy note II screen. I've attached a picture of each screen I mentioned.
Prior to this, I was experiencing root issues. Titanium backup reported that I has a outdated binary I believe. I tried updating through super user but I would get an error. My phone has also been experiencing terrible battery life which I assumed was a kernel or rom issue, though it's clear that it wasn't. Regardless, I was running the beanstalk rom if anyone wanted to know.
Any help is appreciated, thanks.
Edit: 1:34
Sorry the rest of the photos didn't upload, I will upload them later.
Sent from my SAMSUNG-SGH-I957 using XDA Premium 4 mobile app

MzzSarahx3 said:
I found my phone dead this morning and tried plugging it in. The screen reacted by showing a loading battery logo that seems to have froze. I booted into recovery and tried to factory reset but it shows that nothing is mounted. When trying to boot out of recovery it doesn't get past the galaxy note II screen. I've attached a picture of each screen I mentioned.
Prior to this, I was experiencing root issues. Titanium backup reported that I has a outdated binary I believe. I tried updating through super user but I would get an error. My phone has also been experiencing terrible battery life which I assumed was a kernel or rom issue, though it's clear that it wasn't. Regardless, I was running the beanstalk rom if anyone wanted to know.
Any help is appreciated, thanks.
Sent from my SAMSUNG-SGH-I957 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Have you tried using a different battery? Is the battery a samsung stock battery? Is the battery physically flat or is it swollen? Have you done a battery pull and then attempted to boot the phone? If you have a external charger, fully charge the battery (unless the battery is swollen or damaged).
You might also boot into recovery and try charging from there. Recovery has it's own kernel and it is not altered much from what I can tell. I use twrp and it shows when the battery is charging. I'd use twrp 2.6.3.x as it is proven while 2.7.0.0 is freshly released.
Can you boot into recovery and pull a Nandroid? If so, do so. If recovery is stable (and you have adequate battery charge) try to flash a T889 TW rom and see if a stock kernel and firmware will allow the battery to charge.
Hastily spouted for your befuddlement

MzzSarahx3 said:
I found my phone dead this morning and tried plugging it in. The screen reacted by showing a loading battery logo that seems to have froze. I booted into recovery and tried to factory reset but it shows that nothing is mounted. When trying to boot out of recovery it doesn't get past the galaxy note II screen. I've attached a picture of each screen I mentioned.
Prior to this, I was experiencing root issues. Titanium backup reported that I has a outdated binary I believe. I tried updating through super user but I would get an error. My phone has also been experiencing terrible battery life which I assumed was a kernel or rom issue, though it's clear that it wasn't. Regardless, I was running the beanstalk rom if anyone wanted to know.
Any help is appreciated, thanks.
Sent from my SAMSUNG-SGH-I957 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Check your device's battery with other one . I think your old battery makes all the trouble .
Or Just make sure if your device got virus infection . That may also cause this same problem . Better idea is contact your device's dealer . They can fix your device .
Click :thumbup: button if this answer is helped you
Sent from my GT-S7562 using XDA Premium 4 mobile app

Nvm...edited

I'm here to report that my phone is most likely bricked. I tried installing different roms and kernels through my external sd card but none of them would boot. Out of pure stupidity, I flashed a different recovery on my phone and from there I probably killed all chances of saving my phone. It is now unable to boot into recovery and unable to be recognized by ODIN.
Any further suggestions are again appreciated.

MzzSarahx3 said:
I'm here to report that my phone is most likely bricked. I tried installing different roms and kernels through my external sd card but none of them would boot. Out of pure stupidity, I flashed a different recovery on my phone and from there I probably killed all chances of saving my phone. It is now unable to boot into recovery and unable to be recognized by ODIN.
Any further suggestions are again appreciated.
Click to expand...
Click to collapse
Does your phone boot in to download mode ?

ciphercodes said:
Does your phone boot in to download mode ?
Click to expand...
Click to collapse
Yes it does go into download mode but isn't recognized by Odin.

MzzSarahx3 said:
Yes it does go into download mode but isn't recognized by Odin.
Click to expand...
Click to collapse
If you get ODIN working then the device can be recovered by flashing back to stock.
1) Did ODIN work for your device before this issue ?
2) Did you already try updating drivers, different cable etc etc.
How about Heimdall, check if it recognizes your phone.

ciphercodes said:
If you get ODIN working then the device can be recovered by flashing back to stock.
1) Did ODIN work for your device before this issue ?
2) Did you already try updating drivers, different cable etc etc.
How about Heimdall, check if it recognizes your phone.
Click to expand...
Click to collapse
This sounds strangely similar too what happened with my phone. Worked fine and then next day dead.
By any chance did you install Jedi Rom? That was the Rom i was using before mine died.

nollington said:
This sounds strangely similar too what happened with my phone. Worked fine and then next day dead.
By any chance did you install Jedi Rom? That was the Rom i was using before mine died.
Click to expand...
Click to collapse
I have used the Jedi Rom but I was using the beanstalk rom. The symptoms sound a lot like sudden death syndrome but my phone was sent in and fixed for that.
To be exact about Odin and Heimdall does recognize my phone but trying to install anything will give u this error : "device not accessible."

MzzSarahx3 said:
I found my phone dead this morning and tried plugging it in. The screen reacted by showing a loading battery logo that seems to have froze. I booted into recovery and tried to factory reset but it shows that nothing is mounted. When trying to boot out of recovery it doesn't get past the galaxy note II screen. I've attached a picture of each screen I mentioned.
Prior to this, I was experiencing root issues. Titanium backup reported that I has a outdated binary I believe. I tried updating through super user but I would get an error. My phone has also been experiencing terrible battery life which I assumed was a kernel or rom issue, though it's clear that it wasn't. Regardless, I was running the beanstalk rom if anyone wanted to know.
Any help is appreciated, thanks.
Edit: 1:34
Sorry the rest of the photos didn't upload, I will upload them later.
Sent from my SAMSUNG-SGH-I957 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I had the same problem. I used Odin and re flashed my phone. Try installing a new rom or the same one
---------- Post added at 06:01 AM ---------- Previous post was at 05:49 AM ----------
I had the same problem. try using ODIN and Re flash or re flash your ROM maybe use a new ROM

stuck in boot loop?

A few days ago my wife's phone crashed, when we started it back up again all that came up was the samsung logo and phone name and then it stays like that.
I can enter download mode and recovery mode although in recover mode I get red writing saying :
failed to load/mount efs
system etc..
I have tried wiping cache, I have tried delete data/factory reset - but it brings up similar error failed to mount/load/find various things like sys/efs etc..
I tried loading in the .md5 firmware through Odin but it FAILS every time - something about NAND
At the moment I'm out of ideas, Could anyone guide me in the right direction to fix the phone?
The phone has not been altered in anyway, I haven't rooted it or done anything custom to it.
Thanks, John

Sounds like a memory failure.
Sent from my ONE A2003 using Tapatalk

probably the SDS, which is caused by faulty eMMC. If your phone is older than 2 years there is a great chance that it is affected

htc6500uk said:
Sounds like a memory failure.
Sent from my ONE A2003 using Tapatalk
Click to expand...
Click to collapse
yaro666 said:
probably the SDS, which is caused by faulty eMMC. If your phone is older than 2 years there is a great chance that it is affected
Click to expand...
Click to collapse
Is there any ways of checking either of the problems? Is it a costly repair?
Thanks for the replies so far!