Develop Bugs

[Q] Stuck on boot after unroot

Sorry for posting a new thread but I want to make sure I am heading in the right direction. I bought a Galaxy S3 yesterday that was rooted. I want to put it back to stock ROM. I downloaded Odin and the ATT Stock ROM's. Everything went ok and passed without fail, but my phone is stuck on boot. Googling around I found a how to where I could run CWM Recovery, but it seems like this is for rooted devices stuck at boot. I am looking to go back to stock. Will this work or is there something else I am missing? Thanks and I will begin searching on the forum for help.
Edit: My phone does go into dowload mode.

MiamiE said:
Sorry for posting a new thread but I want to make sure I am heading in the right direction. I bought a Galaxy S3 yesterday that was rooted. I want to put it back to stock ROM. I downloaded Odin and the ATT Stock ROM's. Everything went ok and passed without fail, but my phone is stuck on boot. Googling around I found a how to where I could run CWM Recovery, but it seems like this is for rooted devices stuck at boot. I am looking to go back to stock. Will this work or is there something else I am missing? Thanks and I will begin searching on the forum for help.
Edit: My phone does go into dowload mode.
Click to expand...
Click to collapse
so dont worry you'll be fine as long as your able to go to download mode your phone is good
Heres how to restore to stock: http://www.youtube.com/watch?v=ypmqJbZqOaU
If you wanna root it again like a boss heres the link for that too:http://www.youtube.com/watch?v=XoEVDgjTTdg

Great. Thanks for that link. I actually found that video and was looking for the drivers. I noticed the one he linked if for Sprint. My phone is ATT though. I clicked on the ATT link a little further down in his description where it says AT&T USA. I am assuming this is the correct file to install right? Now is that the TAR file or the drivers? He didnt post an AT&T link for one of those.

factory reset
Sent from my SGH-I317M

It wont let me get into factory reset either. I hold power up, power and home and it goes to...
Firmware upgrade encountered and issue. Please select recovery mode in Kies and try again. I cant get into Kies because Kies doesnt connect to the device

Ok I followed QBkings video and everything worked fine and passed but I am still stuck on the Samsung screen. I know he mentioned factory reset but he did it once he was already into the actual phone. Mine wont get in.

You guys are all beasts! Thanks a million for the help. Factory reset finally worked! My phone didnt reset by itself though.

Well I see you must have been able to fix your phone!
It must be like the Atrix 2, but instead of FXZ restoration w/ RSD Lite, you use TAR files and Odin

MiamiE said:
You guys are all beasts! Thanks a million for the help. Factory reset finally worked! My phone didnt reset by itself though.
Click to expand...
Click to collapse
Just remember some time all u need is to reset
Sent from my SGH-I317M

twanskys204 said:
Just remember some time all u need is to reset
Sent from my SGH-I317M
Click to expand...
Click to collapse
Wow! Love the XDA forum. For hours I had the stuck @ Samsung logo after returning to stock on my ATT gNote 2. Bullseye, factory reset did the trick. Thank you guys, totally awesome support here.

Xda....all of us love the thanks button ; p
Sent from my SAMSUNG-SGH-I317 using xda premium

The same thing happened to me today.
I flashed a rooted ics stock, one that came with cwm. It was still stuck on the logo until I went onto cwm and factory reseted. Now it works again.
Sent from my SGH-I747M using xda app-developers app

how do you factory reset if youre stuck on the boot screen?
i just unrooted or whatever and its stuck at the samsung screen

mainguy21 said:
how do you factory reset if youre stuck on the boot screen?
i just unrooted or whatever and its stuck at the samsung screen
Click to expand...
Click to collapse
Boot into recovery. Vol up + home + power. When your device vibrates and you see the blue text in the top left corner of the screen, release just the power button.
Wipe data/factory reset and wipe cache

[Q] Need some help

Hey guys,
I was running a stock version of android 4.2, rooted etc. Last night there was a message in my notification toggle which said i had to update.
So i clicked the message, installed the update but i think the update was corrupt or something. The update was 840kb or so.
I dont really remember what i clicked because it was late in the evening etc. Now my nexus will just show the splash screen and nothing more.
PC doesnt recognise it when i connect it.
Does anyone have an idea of how i could fix this? Would be really appreciated.
Thanks
Edit: i cant get into clockworkmod recovery too but i can get into odin mode

Nicodevries said:
Hey guys,
I was running a stock version of android 4.2, rooted etc. Last night there was a message in my notification toggle which said i had to update.
So i clicked the message, installed the update but i think the update was corrupt or something. The update was 840kb or so.
I dont really remember what i clicked because it was late in the evening etc. Now my nexus will just show the splash screen and nothing more.
PC doesnt recognise it when i connect it.
Does anyone have an idea of how i could fix this? Would be really appreciated.
Thanks
Edit: i cant get into clockworkmod recovery too but i can get into odin mode
Click to expand...
Click to collapse
you shouldn't update if you're not running stock (stock recovery, stock kernel, etc), i guess that what messed your system up.
is fastboot working for you? if so, you could flash the stock image from there. i think that's the only way since recovery doesn't working for you.
good luck.

ntstatis said:
you shouldn't update if you're not running stock (stock recovery, stock kernel, etc), i guess that what messed your system up.
is fastboot working for you? if so, you could flash the stock image from there. i think that's the only way since recovery doesn't working for you.
good luck.
Click to expand...
Click to collapse
Thank you for your reply.
Yes i can go into fastboot mode, the lock state still says unlocked.
The only thing is, i can only see the big green arrow with start in it. If i press my up and down volume buttons nothing happens.
Edit: i tried rooting and installing cwm recovery using nexus root toolkit, but it says my drivers are not installed. Any idea's of how i could do that now?
EDIT2: i am able to get into cwm recovery now. But i am not able to restore anything while i did make a backup

Stop using toolkits...
And use the guide stickied here or in my sig.

Nicodevries said:
Thank you for your reply.
Yes i can go into fastboot mode, the lock state still says unlocked.
The only thing is, i can only see the big green arrow with start in it. If i press my up and down volume buttons nothing happens.
Edit: i tried rooting and installing cwm recoverie using nexus root toolkit, but it says my drivers are not installed. Any idea's of how i could do that now?
Click to expand...
Click to collapse
you should flash the stock image first and you can go wherever you want from there.
i don't use the toolkit, i prefer manual much more convenient for me.
anyway, this guide http://forum.xda-developers.com/showthread.php?t=1626895 or http://forum.xda-developers.com/showthread.php?t=1529058 should help you flashing the stock image.

man o man, took me 4 hours but i did it.
Thanks both for the replies!

[Q] Samsung t989 Galaxy S II - Bootloop HELP please :(

I downloaded the Jedi Mind Trick JB 2 ROM and installed it via clocwork mod recovery .. That went fine but it took me a few days to realize I didnt have a working video camera anymore on my phone.. so I thought to flash a stock ROOTed rom instead...
Then I found this threat about an updated version of Jedi Mind Trick's ROM labled JB 3.. So I wiped as much as I could in recovery and chose to format all the options it gave me in recover , Format system , data , cache , emms(or something) .. and now when I boot the phone , it shows the first flash screen , and the samsung logo starts to shimmer then it reboots back to the splash screen and repeats this process everal times before just going black and sitting there..
So I've successfully bootlooped my phone doing this..
MY PROBLEM -- I don't know how to charge my phone or connect to it to install anything else..
Is this a serious problem? How can I charge my phone to continue troubleshooting it? It still has some battery to try some things but I don't know how to hook it up to transfer any other roms to it via USB cable and PC in it's current state..
I'm very computer savvy but I'm trying to learn this phone modding stuff and I realy hope I didn't brick my phone in this process.
Can someone please help me out here? I'll be on the forums religiously until I figure this out.
What should I start doing first??
Any help would be greatly appreciated!! Thanks!

still working at it
I think I'm at the point of having to use ODIN to flash a new rom since i cannot simply copy this rom to the sdcard to use clockwork to flash it .. Am I correct on this ?
For some reason this rom I found (should be stock rooted tmobile gSII rom) does not want to open from ODIN's PDA button cause its in .zip and not .tar or anything... I'm not sure how to flash this rom with ODIN ( I'm not even 100% sure this is how its supposed to go) Any suggestions ?

phew
UPDATE - So I managed to research enough to find out that there is no way to flash a CUSTOM rom with ODIN.. SO I had to download a stock (presumably rooted) t-mobile rom and flash THAT ...
Now I'm back up with a rooted rom and will begin re-installing clockwork and then my custom deodexed rooted rom afterward.
Thanks for all who almost kinda tried to care to reply in this past 2 hours =) -- As previously mentioned.. I am a nerd.. I just suck at phone modding. Haha
So , looks like I'm in the clear now and don't need any more support on this particular topic yet.

zarklon said:
UPDATE - So I managed to research enough to find out that there is no way to flash a CUSTOM rom with ODIN.. SO I had to download a stock (presumably rooted) t-mobile rom and flash THAT ...
Now I'm back up with a rooted rom and will begin re-installing clockwork and then my custom deodexed rooted rom afterward.
Thanks for all who almost kinda tried to care to reply in this past 2 hours =) -- As previously mentioned.. I am a nerd.. I just suck at phone modding. Haha
So , looks like I'm in the clear now and don't need any more support on this particular topic yet.
Click to expand...
Click to collapse
Is this true? Through a recommendation (haven't done anything to my phone from rooting/flashing KANGSJUGGERNAUT2 years ago), I tried to flash CM10 and ended up with a bootloop myself. Tried flashing through ODIN but it kept crashing; does anyone know why?
Afterward, I tried to reflash it through CWM and from then on bootloops into a installation process that never completes.
For some reason my CWM turned super slow, freezes/hangs and reboots after a few minutes.
I gave the phone to a friend who does this stuff on the regular but he said my initial flash wasn't complete cause in download mode says I'm still running official? No clue.
I was told this via email/chat: "No luck, it won't even boot anymore, I think I'll just bring it back tmrw morn
10:43 PM
Sorry I'm at a wedding (yea I know random) I left my phone with coat check
OK I've narrowed down the reason but not the solution, you had an AOKP based ROM which fundamentally is based on CyanogenMod, but it wasn't correctly flashed as the phone still thought it has factory ROMs still running
11:10 PM
Clockworkmod(even though it was working before) wasn't accessing the partitions of the phone correctly so it wasn't properly wiping or flashing properly.
11:12 PM
So basically from the first time you flashed cwm it didn't flash properly then the next time you flashed using the new recovery it didn't flash anything it was supposed to do itself properly , so basically it was a chain of events in addition to a bad boot loader, that's why it never went to recovery or download mode correctly
11:13 PM
That's something that had to do with the way the phone was built meaning you may of had a bad bootloader from the very begin and are now feeling the synptoms
Basically, and I would hate to be the reason or partially the reason you have a dead phone, basically it was a matter of coincedencr that it happened as this could of happened at anytime, once you have a bad boot loader its pretty much down hill from there"
Any helpful insight as how I can rectify this? is my phone truly dead? Sorry about the quoted format, it was copied and pasted.

If I were in your boat, I'd use Odin and flash the stock 4.1.2 ROM.
Sent from my Nexus 7 using Tapatalk 4 Beta

tronmech said:
If I were in your boat, I'd use Odin and flash the stock 4.1.2 ROM.
Sent from my Nexus 7 using Tapatalk 4 Beta
Click to expand...
Click to collapse
The phone won't turn on, unable to go into recovery and download mode; plugged in usb (hear connection beep but pressing power button plays disconnect button) to no avail. What can I do to unbrick?
Stock 4.1.2? Possible over a hardbricked T989 with old 2.3.6?

JahJahLoO said:
The phone won't turn on, unable to go into recovery and download mode; plugged in usb (hear connection beep but pressing power button plays disconnect button) to no avail. What can I do to unbrick?
Stock 4.1.2? Possible over a hardbricked T989 with old 2.3.6?
Click to expand...
Click to collapse
sorry but i have to assume that you are not doing the 3 button recovery or download mode right.
Pull battery, put battery back in, hold power button & Vol +/- untill you see SAMSUNG on the screen ---> let go off power button(keep holding
Vol +/- button) .....u will see recovery. (assuming you did flash cwm before).
Let me know.
hit thanks.

sam.balia1012 said:
sorry but i have to assume that you are not doing the 3 button recovery or download mode right.
Pull battery, put battery back in, hold power button & Vol +/- untill you see SAMSUNG on the screen ---> let go off power button(keep holding
Vol +/- button) .....u will see recovery. (assuming you did flash cwm before).
Let me know.
hit thanks.
Click to expand...
Click to collapse
I believe I am doing it correct, I have been entering recovery and download mode many times, right before I soft bricked it.
And sorry, no, I've tried many times, many methods and my phone is confirmed as entirely hard bricked.
SUPAR SAD, but thank you!

dont give up
JahJahLoO said:
I believe I am doing it correct, I have been entering recovery and download mode many times, right before I soft bricked it.
And sorry, no, I've tried many times, many methods and my phone is confirmed as entirely hard bricked.
SUPAR SAD, but thank you!
Click to expand...
Click to collapse
you can try using adb and put the phone in dl mode.
sometimes its as easy as pull battery and wait awhile (20 min or more) and try again.
if you've exhausted all possibilities, you can use a jig to force a dl mode.
let me know

sam.balia1012 said:
you can try using adb and put the phone in dl mode.
sometimes its as easy as pull battery and wait awhile (20 min or more) and try again.
if you've exhausted all possibilities, you can use a jig to force a dl mode.
let me know
Click to expand...
Click to collapse
I don't know what adb is, or how to use it; I have, however seen my friend RDP to my desktop and do something and used the term 'adb' in his attempt to code through the phone.
I've done that battery waiting period, for nearly an hour and still no result.
After doing some researching, I have found that many people have stated a USB JIG would not be applicable to a 'hard bricked' phone. I really wanted to try as it looked like the most, simple and inexpensive solution.

JahJahLoO said:
I don't know what adb is, or how to use it; I have, however seen my friend RDP to my desktop and do something and used the term 'adb' in his attempt to code through the phone.
I've done that battery waiting period, for nearly an hour and still no result.
After doing some researching, I have found that many people have stated a USB JIG would not be applicable to a 'hard bricked' phone. I really wanted to try as it looked like the most, simple and inexpensive solution.
Click to expand...
Click to collapse
If you know for a fact that you bricked your s2, maybe wrong rom or kernel that u flashed by accident then.....
contact these guys.... http://brickedmyphone.com/contact-me/
good like and click thanks if you agree.

sam.balia1012 said:
If you know for a fact that you bricked your s2, maybe wrong rom or kernel that u flashed by accident then.....
contact these guys.... http://brickedmyphone.com/contact-me/
good like and click thanks if you agree.
Click to expand...
Click to collapse
Lols, you're really fishing for them "Thanks"; you got it buddy. Very swift responses. :cyclops:
Anyway, I'm still searching the net for anymore possible solutions.
Thanks.

JahJahLoO said:
Lols, you're really fishing for them "Thanks"; you got it buddy. Very swift responses. :cyclops:
Anyway, I'm still searching the net for anymore possible solutions.
Thanks.
Click to expand...
Click to collapse
fishing for them ???????
what the hell does that even mean? it seems that brick did hit u in the head!!!

sam.balia1012 said:
fishing for them ???????
what the hell does that even mean? it seems that brick did hit u in the head!!!
Click to expand...
Click to collapse
It might as well have... :crying:

S3 won't boot up, gray battery icon

Hello there,
I just rooted and flashed a custom recovery to my S3 today. Afterwards, I installed CyanogenMod through the CWM recovery and rebooted, however,after the reboot the device powered off completely. Now when I try to turn on the device I get a grey battery icon with a static circle on it, and it does not proceed any further. I cannot access recovery mode or even get to the Samsung loading screen. Plugging the device into the wall charger doesn't seem to be doing anything as it has been 'charging' for over 30 minutes and still does not power on. I've been scouring the net for hours looking for answers, but the few people who seem to have the same problem have not found any sort of resolution. There are all sorts of tricks people are suggesting such as putting your battery in and plugging the cable in, vice versa..etc but nothing seems to work. The phone was working just fine and the battery still had a good 30-40% charge when this happened. Does anyone know what the issue could be? I cannot even get it serviced because I had JUST rooted/custom recovery'd it when this happened, so just my luck with that. If anyone could help me it would mean a lot. Thank you for reading.
Regards,
Mike

Cryceratops said:
Hello there,
I just rooted and flashed a custom recovery to my S3 today. Afterwards, I installed CyanogenMod through the CWM recovery and rebooted, however,after the reboot the device powered off completely. Now when I try to turn on the device I get a grey battery icon with a static circle on it, and it does not proceed any further. I cannot access recovery mode or even get to the Samsung loading screen. Plugging the device into the wall charger doesn't seem to be doing anything as it has been 'charging' for over 30 minutes and still does not power on. I've been scouring the net for hours looking for answers, but the few people who seem to have the same problem have not found any sort of resolution. There are all sorts of tricks people are suggesting such as putting your battery in and plugging the cable in, vice versa..etc but nothing seems to work. The phone was working just fine and the battery still had a good 30-40% charge when this happened. Does anyone know what the issue could be? I cannot even get it serviced because I had JUST rooted/custom recovery'd it when this happened, so just my luck with that. If anyone could help me it would mean a lot. Thank you for reading.
Regards,
Mike
Click to expand...
Click to collapse
Copy and paste the name of the zip that you downloaded and flashed for me so I can better determine what you did bud, I don't want to say hard brick because this could be battery cells going bad coincidentally

Danvdh said:
Copy and paste the name of the zip that you downloaded and flashed for me so I can better determine what you did bud, I don't want to say hard brick because this could be battery cells going bad coincidentally
Click to expand...
Click to collapse
Hello there,
Thanks for the reply. I followed the instructions as per this thread:
http://forum.xda-developers.com/showthread.php?t=2179330
The CWM mod version I got from following Step 2 of that guide, which led me to this: http://www.epiccm.org/2012/06/cwm-recovery-on-all-sgs3-lte-variants.html
Afterwards, everything seemed to be working fine, so I grabbed a copy of the official CM latest nightly for my device, wiped/factory reset, and installed the ROM + gapps. After I reboot, the phone shut off, and this has been going on since. I am able to get into download mode, as I have just discovered, but I cannot get into recovery mode or turn the phone on past this mysterious grey battery icon.
Thanks for your time,
-Mike

Cryceratops said:
Hello there,
Thanks for the reply. I followed the instructions as per this thread:
http://forum.xda-developers.com/showthread.php?t=2179330
The CWM mod version I got from following Step 2 of that guide, which led me to this: http://www.epiccm.org/2012/06/cwm-recovery-on-all-sgs3-lte-variants.html
Afterwards, everything seemed to be working fine, so I grabbed a copy of the official CM latest nightly for my device, wiped/factory reset, and installed the ROM + gapps. After I reboot, the phone shut off, and this has been going on since. I am able to get into download mode, as I have just discovered, but I cannot get into recovery mode or turn the phone on past this mysterious grey battery icon.
Thanks for your time,
-Mike
Click to expand...
Click to collapse
kk download you're stock firmware and flash it in odin, something went wrong my friend so you're going to have to start over
stock roms are here http://forum.xda-developers.com/showthread.php?t=1968625
the good news is download mode = soft brick so you are in luck! My guess is the ROM was corrupt or just a very horrible flash =/

Danvdh said:
kk download you're stock firmware and flash it in odin, something went wrong my friend so you're going to have to start over
stock roms are here http://forum.xda-developers.com/showthread.php?t=1968625
the good news is download mode = soft brick so you are in luck! My guess is the ROM was corrupt or just a very horrible flash =/
Click to expand...
Click to collapse
Thanks very much! I was able to use the stock firmware in conjunction with Odin to get myself back up and running!
Now the issue remains, is there any way to install CM 10~ on this device? I cannot find a proper version of CWM aside from the 'universal' one which I mentioned above, however, if I try and flash any version of CM using that recovery, it gives me a Status 7 error, which people say is due to an old recovery version. Any idea as to where I can find a working (new) version of CWM for this device?
Kind Regards,
Mike

All up to dates CWM are there:
http://www.clockworkmod.com/rommanager
Sent from my SAMSUNG-SGH-I747 using XDA Premium 4 mobile app
---------- Post added at 10:38 PM ---------- Previous post was at 10:34 PM ----------
And here show to install it:
http://forum.xda-developers.com/wiki/ClockworkMod_Recovery
Sent from my SAMSUNG-SGH-I747 using XDA Premium 4 mobile app

I've solved the issue. Thanks for all the help.
The problem was that apparently I had an outdated bootloader which wasn't compatible with newer versions of CM and CWM. I installed the new bootloader from a thread here in the S3 forums and then flashed a new version of CWM and managed to get CM running.
I'm having new, unrelated issues now, but I'm sure I will be able to solve those.
Thanks again

[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??