Develop Bugs

stuck at Samsung Logo Note 2 ATT

Stuck on the samsung logo.
The battery drained dead, and I waited until I got home to charge it. I plugged it in and the grey battery popped up and a loading wheel, but it froze.
Now it doesn't turn on. I switched batteries and it goes to the samsung logo and sits there. I tried VolUP+VolDown+HOME+Power and All the other button combos and still nothing just goes to samsung screen and reboots, then I notice the led light flashes red very faintly and once quickly then the logo comes back up.
Any ideas?

Did you root or install custom recovery?

kirkla79 said:
Did you root or install custom recovery?
Click to expand...
Click to collapse
No I haven't tried to do anything of the sort. I just got this phone when it got released, and haven't explored that much with it yet. It just suddenly doesn't work after the battery drained dead.

I would just go back from where you bought it a get it exchanged then.

kirkla79 said:
I would just go back from where you bought it a get it exchanged then.
Click to expand...
Click to collapse
Yeah I'm just going to hate to lose everything because I couldn't do a backup...
Sucks.

Root install recovery and clear cashe partition and dalvik cashe. Use stock rom image with SU injected and do not wipe. Or exchange and loose everything
Sent from my SAMSUNG-SGH-I317 using XDA Premium HD app

My girlfriend drained her battery until the phone shut off. Had to leave it on the charger for almost an hour before it would boot. I thought it should boot as soon as I plugged it in but that's not the case. Try letting it sit and charge for awhile.

jethro650 said:
My girlfriend drained her battery until the phone shut off. Had to leave it on the charger for almost an hour before it would boot. I thought it should boot as soon as I plugged it in but that's not the case. Try letting it sit and charge for awhile.
Click to expand...
Click to collapse
I left it on the charger for almost 3 hours. And nothing, not even the loading icon over the battery would disappear.
Could someone point me in the right direction for rooting etc... as the user described above?

PrestigeA said:
I left it on the charger for almost 3 hours. And nothing, not even the loading icon over the battery would disappear.
Could someone point me in the right direction for rooting etc... as the user described above?
Click to expand...
Click to collapse
Not sure your going to be able to root with a non-booting phone. Here are a couple links about rooting
Chainfire's method you need download mode
mrRobinson's root injected stock Roms, also need download mode
Good luck hope one of these works for you.

Just my $0.02 worth.
My suggestion is make sure you are using the original, Samsung battery. Let it charge for 8 - 10 hours. Take it off the charger, remove the battery from the phone, wait several minutes; then replace the battery and try to boot.
If that doesn't restore, I'd take it back to the store from which you purchased it, and see if a new, oem battery will let it boot. The store should try to do everything they can to help, short of replacing the phone. But it may just be your phone has gone bad -- in which case rooting isn't going to help...
Good luck.
PrestigeA said:
I left it on the charger for almost 3 hours. And nothing, not even the loading icon over the battery would disappear.
Could someone point me in the right direction for rooting etc... as the user described above?
Click to expand...
Click to collapse

Intall CWM with odin then reboot in recovery and install stock rooted .zip or stock based ROM. Its called a dirty install. You can do this by placing the .zip in a microSD then install from external in CWM. You will end up with all your old crap but the .zip will replace your corrupted files. I recommend you save everthing as soon as it boots and yhen do a clean install of whatever ROM you want even if its stock.
Sent from my SAMSUNG-SGH-I317 using XDA Premium HD app

reinstalled stock ROM, stuck on logo
I recently got an AT&T note 2. I rooted and installed cwm recovery. I tried installing Android Revolution HD 5.0 after running their superwipe script. Everything went smoothly except the SIM was not recognized. I couldn't get it to work so I tried 2 other ROMs and I had the same issue. I decided to go back to stock and wait for Cyanogen to release a ROM.
The issue I am having now is that the stock ROM downloaded from http://forum.xda-developers.com/showthread.php?t=2004650 and another stock ROM (KIES_HOME_I317UCALJ2_I317ATTALJ2_215287_REV04_user_low_ship.tar) won't boot. I can successfully push them to the phone from Odin, but then they reboot and get stuck on the Samsung logo. The phone doesn't give any error messages, no strange leds on, no reboots, it just sits there with the Samsung logo pulsing. I can still boot into the download mode (vol down, home, power).
Any advice on how to get to a functoning ROM? At this point I don't care if it is stock or custom, I just need something that works. Any help would be greatly appreciated!

cdt710 said:
I recently got an AT&T note 2. I rooted and installed cwm recovery. I tried installing Android Revolution HD 5.0 after running their superwipe script. Everything went smoothly except the SIM was not recognized. I couldn't get it to work so I tried 2 other ROMs and I had the same issue. I decided to go back to stock and wait for Cyanogen to release a ROM.
The issue I am having now is that the stock ROM downloaded from http://forum.xda-developers.com/showthread.php?t=2004650 and another stock ROM (KIES_HOME_I317UCALJ2_I317ATTALJ2_215287_REV04_user_low_ship.tar) won't boot. I can successfully push them to the phone from Odin, but then they reboot and get stuck on the Samsung logo. The phone doesn't give any error messages, no strange leds on, no reboots, it just sits there with the Samsung logo pulsing. I can still boot into the download mode (vol down, home, power).
Any advice on how to get to a functoning ROM? At this point I don't care if it is stock or custom, I just need something that works. Any help would be greatly appreciated!
Click to expand...
Click to collapse
You should only flash ROMs from the "AT&T Galaxy Note II Android Development" section. I think Revolution HD is not an AT&T ROM, I don't know about the other ROMs you flashed (as you didn't say what they where). Those ROMs probably flash a non AT&T compatible radio on you phone. You should read and re-read and make sure you know what to do and what ROM can can flash before you start flashing.
Do you have a custom recovery installed, CWM or TWRP? Have you tried using a different computer and different cable?
Maybe try flashing the AT&T modem and them a correct ROM and see if that helps. Honestly, I'm not sure how to help you beyond that.
Good luck...

Back up and running
RojasTKD said:
You should only flash ROMs from the "AT&T Galaxy Note II Android Development" section. I think Revolution HD is not an AT&T ROM, I don't know about the other ROMs you flashed (as you didn't say what they where). Those ROMs probably flash a non AT&T compatible radio on you phone. You should read and re-read and make sure you know what to do and what ROM can can flash before you start flashing.
Do you have a custom recovery installed, CWM or TWRP? Have you tried using a different computer and different cable?
Maybe try flashing the AT&T modem and them a correct ROM and see if that helps. Honestly, I'm not sure how to help you beyond that.
Good luck...
Click to expand...
Click to collapse
I was able to get into the cwm recovery and load a new ROM onto the external SD card, then install it. I went with the Jedi ROM this time and it worked. I think you are correct that I was using ROMs for the wrong version of the phone. Everything is up and running and I have full functionality. Thanks for the tip!

cdt710 said:
I was able to get into the cwm recovery and load a new ROM onto the external SD card, then install it. I went with the Jedi ROM this time and it worked. I think you are correct that I was using ROMs for the wrong version of the phone. Everything is up and running and I have full functionality. Thanks for the tip!
Click to expand...
Click to collapse
Excellent, glad you were able to get it working.
Enjoy!

cdt710 said:
I was able to get into the cwm recovery and load a new ROM onto the external SD card, then install it. I went with the Jedi ROM this time and it worked. I think you are correct that I was using ROMs for the wrong version of the phone. Everything is up and running and I have full functionality. Thanks for the tip!
Click to expand...
Click to collapse
get yourself a jig dude, if you were really stuck you could have just put that badboy in and it would take you to dl mode, from there you could have odin'd yourself anywhere you wanted to. A thought for next time you get yourself into a situation you think isn't recoverable.
if you are a in a bloop you can usually get to recovery and from there sort yourself out. I know you are ok now, but this may still help someone else.
A jig is like a condom... protection even if you think you don't need it, you should prolly use it.

***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

At&t gn2 hard bricked??

I upgraded to 4.3 stock. Then rooted, then upgraded to 4.4.2 custom.
Then decide to get back to 4.3. By a mistake i restored in ODIN to 4.1.1 (stupid me)
After restore, phone won't boot. Actually I cannot do anything......except for going into download mode, where I got "knox warranty void:1". And that is it! Nothing else can be done........i cannot even boot into recovery............
Any help??? Or should i toss it against the wall??

http://forum.xda-developers.com/showthread.php?t=2581321
HOW-TO Downgrade from 4.3 OFFICIAL MK6 to LJ2 4.1.1
Did you thank your Developer today?

Jspex said:
http://forum.xda-developers.com/showthread.php?t=2581321
HOW-TO Downgrade from 4.3 OFFICIAL MK6 to LJ2 4.1.1
Did you thank your Developer today?
Click to expand...
Click to collapse
TY!! I did that already..........and STILL cannot boot into recovery AFTER this.... any idea???

Your profile says Verizon. This stuff is for at&t.
But you can reinstall TWRP if you can get in download mode.

rangercaptain said:
Your profile says Verizon. This stuff is for at&t.
But you can reinstall TWRP if you can get in download mode.
Click to expand...
Click to collapse
VERIZON?? Oops!! That was years ago.....forgot to change it. Sorry.
And yes, i did install recovery via odin. But i cannot boot into recovery.....

Home+volume up and hold in power until you see first screen, then let go of power but contine to hold in home+volume up until you see TWRP screen.
Otherwise, use "adb reboot recovery" command.

rangercaptain said:
Home+volume up and hold in power until you see first screen, then let go of power but contine to hold in home+volume up until you see TWRP screen.
Otherwise, use "adb reboot recovery" command.
Click to expand...
Click to collapse
Unfortunately, device list is empty.... got drivers installed.

Powered usb port stock cable correct pc directory?

rangercaptain said:
Powered usb port stock cable correct pc directory?
Click to expand...
Click to collapse
Yup.

Mine is doing the exact same thing. Wont show up in adb and wont boot in recovery, but can get in download, flashed twrp through odin and still cant get into recovery

There is some procedure that forces recovery that involves taking out the battery at a certain point during bootup, but I don't know it. Maybe start a new question thread about that?

Try flashing the 4.1.1 firmware from sammobile. it is the older of the 2 from att and it does not show a version number on the Sammobile site. Then flash root/cwm all through odin. Then do the battery pull trick to recovery. You may need the root and custom recovery to get the rest to work right.
Did you thank your Developer today?

Jspex said:
Try flashing the 4.1.1 firmware from sammobile. it is the older of the 2 from att and it does not show a version number on the Sammobile site. Then flash root/cwm all through odin. Then do the battery pull trick to recovery. You may need the root and custom recovery to get the rest to work right.
Did you thank your Developer today?
Click to expand...
Click to collapse
Done that, NO luck.

When you pull the battery does it boot automatically into download mode? Or do you have to power the device up yourself?
Also have you tried to odin a root injected 4.1.1 fw yet? You may have to dig through the dev section but I know they are there.
Have you tried flashing the leak 4.3 yet? http://forum.xda-developers.com/showthread.php?t=2496292
JSS15J.I317UCUBMJ4 (Android 4.3)
Really at this point I'm spit balling.
Did you thank your Developer today?

Jspex said:
When you pull the battery does it boot automatically into download mode? Or do you have to power the device up yourself?
Also have you tried to odin a root injected 4.1.1 fw yet? You may have to dig through the dev section but I know they are there.
Have you tried flashing the leak 4.3 yet? http://forum.xda-developers.com/showthread.php?t=2496292
JSS15J.I317UCUBMJ4 (Android 4.3)
Really at this point I'm spit balling.
Did you thank your Developer today?
Click to expand...
Click to collapse
After battery pull out, I have power it back on. (power-home-vol/up - Galaxy Note II screen, and sits there. power-home-vol/down - download screen)
Tried 4.1.1 in odin, tried 4.1.2 as well, and rooted it in odin right away, all went OK, passed, but after battery pull out, still didn't go beyond Galaxy Note II screen.
Tried 4.3 in odin, but at the end, got "failed" result.
Damn.............for some reason, i know this has something to do with bootloader. I am not "android" guy, but rather PC computer freak... ......if i only know how to completely reformat entire storage space, and start from the scratch.....but unfortunately, this is not a hard drive....

fuzio1963 said:
After battery pull out, I have power it back on. (power-home-vol/up - Galaxy Note II screen, and sits there. power-home-vol/down - download screen)
Tried 4.1.1 in odin, tried 4.1.2 as well, and rooted it in odin right away, all went OK, passed, but after battery pull out, still didn't go beyond Galaxy Note II screen.
Tried 4.3 in odin, but at the end, got "failed" result.
Click to expand...
Click to collapse
Just for me try this: flash 4.1.1 and as soon as the device reboots pull the battery. Dont let it get a chance to do anything. Then boot it into download mode and flash the chainfire superuser with Stock recovery built in. That can be found a in the stickey how to revery to stock thread in this exact forum. Then on reboot after flash pull the battery and let it sit for 5 min, no less. Then try to boot into recovery. If you can get into stock recovery there is hope.
I know you may have tried this already but please try it one last time for me. Keep in mind you should pull the phone Off the usb as soon as the odin flashs are done. Pulling the battery while it is still plugged in wont cut the power the way you need it to in order to reboot properly. Also if you have an external sd card in pull that sucker out as well. Sd cards can hang things up sometimes.
Like I said spitballing here. If all else fails maybe you can talk a dev into wrapping a rom into an odinable .tar file and try to force a rom on it.
Did you thank your Developer today?

Jspex said:
Just for me try this: flash 4.1.1 and as soon as the device reboots pull the battery. Dont let it get a chance to do anything. Then boot it into download mode and flash the chainfire superuser with Stock recovery built in. That can be found a in the stickey how to revery to stock thread in this exact forum. Then on reboot after flash pull the battery and let it sit for 5 min, no less. Then try to boot into recovery. If you can get into stock recovery there is hope.
I know you may have tried this already but please try it one last time for me. Keep in mind you should pull the phone Off the usb as soon as the odin flashs are done. Pulling the battery while it is still plugged in wont cut the power the way you need it to in order to reboot properly. Also if you have an external sd card in pull that sucker out as well. Sd cards can hang things up sometimes.
Like I said spitballing here. If all else fails maybe you can talk a dev into wrapping a rom into an odinable .tar file and try to force a rom on it.
Did you thank your Developer today?
Click to expand...
Click to collapse
Stand by..........will do this right now.

Cool, let us know if this actually worked. This seems to be a problem for 1/2 the people that try the revert to 4.1.1 method.
Did you thank your Developer today?

Jspex said:
Cool, let us know if this actually worked. This seems to be a problem for 1/2 the people that try the revert to 4.1.1 method.
Did you thank your Developer today?
Click to expand...
Click to collapse
Sent you a PM.

fuzio1963 said:
Sent you a PM.
Click to expand...
Click to collapse
Seems like i didnt get it and im not seeing the one I just sent you in my outbox. You can email me [email protected] or if you irc I'm always in #jedi on coldfront.net
Did you thank your Developer today?

[Q] Galaxy Note 2 i317 Won’t Boot After Update

Issue
1. Phone won’t boot beyond the Samsung Logo.
2. It won’t boot into recovery (download mode works).
3. Can flash rom using Odin but phone still won't boot.
Type of Phone
Type: AT&T Samsung Galaxy Note 2
Model: i317
Ownership: Bought in Nov 2012 brand new. Warranty is up but it is insured through AT&T.
History: Rooted and then un-rooted and returned to stock in January 2014.
Actions leading up to Issue
Updated to Samsung’s newest firmware Android 4.3 but didn’t like it. I rooted my phone and tried a custom rom but wasn’t happy. Un-rooted by flashing original stock rom via Odin 3.07. Worked great and I was back in business. But then the phone went through an update and never booted back up.
Detail
I’ve rooted all my other phones but never felt the need to root this one until I updated to Samsung’s new Android 4.3. I wasn’t happy with the decreased battery life and poor performance. So I used the method at http://forum.xda-developers.com/showthread.php?t=2004650 to root my phone using “root66_ATT_I317UCALJ2.tar.md5” with Odin 3.07 and it worked. I then tried a custom Cyanogen Mod rom but it still left something to be desired.
After more research I flashed the original stock rom “KIES_HOME_I317UCALJ2_I317ATTALJ2_215287_REV04_user_low_ship.tar.md5” via Odin 3.07 and my phone worked beautifully, at least for a day. Then I started getting the AT&T update window for Android 4.3 and the only way to get rid of it was to pull my battery. It was happening so much that I couldn’t even make a phone call. Out of pure frustration I decided to accept the update.
After the update installed it rebooted and never made it past the Samsung logo. So I figured I would just go into recovery and perform a factory reset as well as wipe the cache. The problem here is that it won’t boot into recovery. Only download mode works. I’m also seeing a red LED which I’ve read is a sign of SDS.
I’ve tried re-flashing the original stock rom again. Every time I do I get the green “Pass” display but my phone still won’t boot. The binary count is now at 21 since I’ve tried flashing so many times. I’ve been working on this and researching for 3 weeks. I’ve never had an issue that I couldn’t resolve when it comes to any of my past phones but this is beyond my skill or understanding. I also tried Samsung keys but it says my device is not supported.
Short of digging a hole in my back yard and burying it, is there anything I can do to fix this?
(Note) My wife has the same phone and also didn’t like the update so I flashed the same original stock rom to her phone via Odin and it has been working just fine. Only difference is I never rooted hers. I should have gone that route with mine.

Have you tried flashing, via Odin, just a custom recovery?
If that works, you may be able to follow this guide, starting at post #2.
http://forum.xda-developers.com/showthread.php?t=2618447
If that doesn't work, it is possible you have an emmc issue.... Your symptoms are similar to what others have reported here recently. You might be able to get a repair covered if you can get them to look past the custom counter ... You are running stock firmware... Maybe kies tripped the counter... Stranger things have happened...
Sent from my SAMSUNG-SGH-I317 using XDA Premium 4 mobile app

Zen Arcade said:
Have you tried flashing, via Odin, just a custom recovery?
If that works, you may be able to follow this guide, starting at post #2.
http://forum.xda-developers.com/showthread.php?t=2618447
If that doesn't work, it is possible you have an emmc issue.... Your symptoms are similar to what others have reported here recently. You might be able to get a repair covered if you can get them to look past the custom counter ... You are running stock firmware... Maybe kies tripped the counter... Stranger things have happened...
Sent from my SAMSUNG-SGH-I317 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Thanks I'll give it a try. I had thought about it but was afraid to mess things up even more. Is there one that you would recommend?

josh3josh3 said:
Thanks I'll give it a try. I had thought about it but was afraid to mess things up even more. Is there one that you would recommend?
Click to expand...
Click to collapse
Here's the link to TWRP (you want the Odin link toward the bottom):
http://teamw.in/project/twrp2/124
Here's the direct link to the latest philz cwm (you want the md5 file):
http://goo.im/devs/philz_touch/CWM_Advanced_Edition/t0lteatt
I prefer philz, but you will likely need TWRP to follow the dicksteele guide. You should also track down a CWM flashable recovery package for MH3 recovery to flash back should you need to return the phone for repairs. You can get this by following the i317 link in my sig.
If flashing this in Odin doesn't work that would tend to support the emmc fail scenario. (i.e. you flash it, Odin behaves as if it flashed ok, you power off, attempt to boot recovery with home-VolUp-power and it still doesn't boot). If it does boot recovery, you can try the guide as I mentioned before. Good luck!

Zen Arcade said:
Have you tried flashing, via Odin, just a custom recovery?
If that works, you may be able to follow this guide, starting at post #2.
http://forum.xda-developers.com/showthread.php?t=2618447
If that doesn't work, it is possible you have an emmc issue.... Your symptoms are similar to what others have reported here recently. You might be able to get a repair covered if you can get them to look past the custom counter ... You are running stock firmware... Maybe kies tripped the counter... Stranger things have happened...
Sent from my SAMSUNG-SGH-I317 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I tried each of those just now and they both flashed fine however there is no change. I guess before I break out the shovel I'll try to see if AT&T will fix it since I do pay for the insurance. Thanks for the help that was good stuff. I wish it could have worked.

josh3josh3 said:
I tried each of those just now and they both flashed fine however there is no change. I guess before I break out the shovel I'll try to see if AT&T will fix it since I do pay for the insurance. Thanks for the help that was good stuff. I wish it could have worked.
Click to expand...
Click to collapse
if you have nothing else to lose, can you try flashing the boot loader on this link
http://d-h.st/Krs from this thread
http://forum.xda-developers.com/showthread.php?t=2589891
then try one of the official odin package or this:http://d-h.st/DGZ

So, there appear to be many people who see this update as a bad joke. Like me.
I had a thread a couple days ago about how to kill the notification from att
Without root. Nothing can be done as far as ive heard/seen. Im a bit confused
About needing a battery pull to remove pp note, I have been just reboot and it
Goes away until next data use/net access. When my 8 hrs is up I turn data on
(Data off as 8hrs expires) and immediately get note and then I hit home- get
another 8 hrs. Im sorry to hear they wore you down with the note- im going to
fight and resist for the duration. And keep stock. Its a game now!
R, john

qkster said:
if you have nothing else to lose, can you try flashing the boot loader on this link
http://d-h.st/Krs from this thread
http://forum.xda-developers.com/showthread.php?t=2589891
then try one of the official odin package or this:http://d-h.st/DGZ
Click to expand...
Click to collapse
Tried it and it failed to flash. Now I have the yellow triangle. At least its something different. Still no good though. Reflashed stock rom and I'm back to the Samsung logo. Was worth a shot. Thanks.

Try param and tz package mentioned in post #3 here.... Might be something
http://forum.xda-developers.com/showthread.php?t=2596256
Sent from my SAMSUNG-SGH-I317 using XDA Premium 4 mobile app

josh3josh3 said:
Tried it and it failed to flash. Now I have the yellow triangle. At least its something different. Still no good though. Reflashed stock rom and I'm back to the Samsung logo. Was worth a shot. Thanks.
Click to expand...
Click to collapse
You flashed LJ2 Stock ROM from ODIN?
And you are back to the Samsung Logo that flashing/pulsing blue???
If so .....
Pull the battery and let the phone sit for a few seconds, pop the battery in and boot into stock recovery (HOLD VOL UP+HOME+POWER) and do a FACTORY RESET then reboot.
I had to do the same thing an hour ago....

dicksteele said:
You flashed LJ2 Stock ROM from ODIN?
And you are back to the Samsung Logo that flashing/pulsing blue???
If so .....
Pull the battery and let the phone sit for a few seconds, pop the battery in and boot into stock recovery (HOLD VOL UP+HOME+POWER) and do a FACTORY RESET then reboot.
I had to do the same thing an hour ago....
Click to expand...
Click to collapse
Have tried that many times with no luck. Wish it were that simple.

josh3josh3 said:
Have tried that many times with no luck. Wish it were that simple.
Click to expand...
Click to collapse
Have you tried this yet ?
http://forum.xda-developers.com/showpost.php?p=49826416&postcount=9

Zen Arcade said:
Try param and tz package mentioned in post #3 here.... Might be something
http://forum.xda-developers.com/showthread.php?t=2596256
Sent from my SAMSUNG-SGH-I317 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I can't believed it worked. Flashed this and suddenly I have recovery. Then I re-flashed the original stock rom, did a reset and wiped the cache and I'm back up and running. Brilliant I say. Genius! Thank you for the great post and thanks everyone for your help. Seems like there should be a like button or something so that you get credit but I don't see one. This was my first time ever posting on any forum so I'm a little ignorant.

josh3josh3 said:
I can't believed it worked. Flashed this and suddenly I have recovery. Then I re-flashed the original stock rom, did a reset and wiped the cache and I'm back up and running. Brilliant I say. Genius! Thank you for the great post and thanks everyone for your help. Seems like there should be a like button or something so that you get credit but I don't see one. This was my first time ever posting on any forum so I'm a little ignorant.
Click to expand...
Click to collapse
That would be the Thanks button by the Quote...
OUTSTANDING !!!
Glad you're back among the living.
This will get you back to 4.1.2
http://forum.xda-developers.com/showpost.php?p=49616718&postcount=2
EDIT:
I just did this and it worked perfectly .....
I'm actually doing that step right now also. I flashed back to stock testing the ATT update server.
EDIT #2:
At this step when the phone reboots the script will run. When it completes you want to boot to system. The next prompt will be do you want to install ROOT. If you do the swipe it will install ROOT, there is a DO NOT INSTALL button on the middle of the screen. Just a heads up, don't know if you are turning your phone back in or not now.
- Second step is:
You will need to download TWRP 2.6.3.1 and flash it in ODIN.
http://goo.im/devs/OpenRecovery/t0lt...lteatt.img.tar
This is necessary for an openrecovery script to run that is stored in the /cache directory from the update.
- Put your Note 2 in Download Mode.
- Open ODIN, put openrecovery-twrp-2.6.3.1-t0lteatt.img.tar in PDA slot. Click Start and let the phone reset.
- Your phone will reboot in TWRP. If not, pull battery and enter recovery mode boot into TWRP recovery (HOLD VOL UP+HOME+POWER). The script will run by itself.

sgh-i317 EFS seems like its gone
could anybody help me out with my note 2. ive tried just about everything i can think of. im getting pretty desperate. i can get everything to work fine (recovery,download mode,) but something is keeping it from booting up to the main screen, it will just hand at the boot animation, or the att logo. in twrp it tells me failed to mount efs. ive looked around in the file folders and its like it got wiped out? im not sure how though. could that be why its not booting up?
any ideas??

[Q] Rooted: Factory Reset: STUCK

Hello to everyone. This is my first adventure. I've read until my eyes have bleed but still haven't figured out a solution to my problem so I will ask scaringly...
I have a AT&T Samsung Note II SGH-I317 rooted.
My phone is currently stuck on "Samsung GALAXY Note II" screen after I did a factory reset.
Initially this worked but as I was setting everything back up, I received a ota system update. And it gave me a failure to upgrade error, try again in kies. Kies will not recognize my phone because it's stuck. I've done the hold up volume + home then power a hundred times but it won't let me go into recovery. I've read of everyones success but I'm still stuck! I used stock roms from at least 5 different sources but none have fully recovered my phone. It does however PASS in odin 3.07 and 3.09.
What other options have I missed? Please help....

poochieturner said:
Hello to everyone. This is my first adventure. I've read until my eyes have bleed but still haven't figured out a solution to my problem so I will ask scaringly...
I have a AT&T Samsung Note II SGH-I317 rooted.
My phone is currently stuck on "Samsung GALAXY Note II" screen after I did a factory reset.
Initially this worked but as I was setting everything back up, I received a ota system update. And it gave me a failure to upgrade error, try again in kies. Kies will not recognize my phone because it's stuck. I've done the hold up volume + home then power a hundred times but it won't let me go into recovery. I've read of everyones success but I'm still stuck! I used stock roms from at least 5 different sources but none have fully recovered my phone. It does however PASS in odin 3.07 and 3.09.
What other options have I missed? Please help....
Click to expand...
Click to collapse
Weird, ODIN should usually work without issue. Are you using the custom recovery or a stock recovery? You should be able to flash a new recovery with ODIN I believe.

Are you using the factory USB charging cable? Knock-off cables cause odin and kies errors.

Reply
They were all stock recovery. As I mentioned before, the first time I done it, it worked fine but once I received the update from at&t I've not been able to duplicate that process without get stuck. I can access download and that's it.
Yes, I'm using the usb that came with my phone. ODIN recognizes my phone immediately.

poochieturner said:
They were all stock recovery. As I mentioned before, the first time I done it, it worked fine but once I received the update from at&t I've not been able to duplicate that process without get stuck. I can access download and that's it.
Yes, I'm using the usb that came with my phone. ODIN recognizes my phone immediately.
Click to expand...
Click to collapse
I'm having this same exact problem under very similar circumstances. Has anyone found a solution?

Thanks Man
hylander2126 said:
I'm having this same exact problem under very similar circumstances. Has anyone found a solution?
Click to expand...
Click to collapse
Followed your post and got mine working also.. Bootloader did it! Thanks...