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
Related
Ok, so I searched high and low and saw nothing about anyone who couldn't get there GS3 to boot at all . . .
So My rogers I747M was succesfully rooted with Odin root not trip. And then i flashed It with the generic rooted jelly bean ROM. Successful again everything seemed fine. So i was confident in shooting for CM10(even though ive had troubles in the past) And i put the zip. in the sd and booted into CWM recovery and did a factory reset, cache and dalvik. Went to install CM10 from sd and it gave me error 7. so i reboot device and loaded into the stock rooted jellybean again to try and put another fill in the SD. Tried booting into recovery again. Now nothing at all, I have tried pulling the battery, even for hours. And then button combos..Nothing. Leaving cord in with battery out,button combos,battery in...Nothing
I'm afraid of the worst ATM, i had the unbrickable Captivate before this with my JIG and all, I'd did this to that phone, but the JIG saved me.
So the phone doesn't boot and you can't enter recovery?
The error 7 was cause by you not having the latest version of cwm.
Now for the brick part: try pulling out the battery, put it back and do the button com to enter recovery , old it for like ten seconds. Then plug it to your computer to see if Odin dectects it.
Once you tried it give me some feedback and I will check for further help. But if you are sure you didn't flash a wrong ROM for your device or a wrong kernel. The error 7 shouldn't have bricked your phone
Sent from my SGH-I747 using xda app-developers app
liltitiz said:
So the phone doesn't boot and you can't enter recovery?
The error 7 was cause by you not having the latest version of cwm.
Now for the brick part: try pulling out the battery, put it back and do the button com to enter recovery , old it for like ten seconds. Then plug it to your computer to see if Odin dectects it.
Once you tried it give me some feedback and I will check for further help. But if you are sure you didn't flash a wrong ROM for your device or a wrong kernel. The error 7 shouldn't have bricked your phone
Sent from my SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
Still No luck, whenever i try to plug it in the computer, it just gives me three quick "DUH_DUH_DUH"s as is to tell me the computer failed to recognize. I'm afraid i may have to take it back to rogers, it's not two weeks old yet so perhaps ill get away with defective, i wonder if they deem that sort of thing in store or at the depot. Because i know they wont get it too boot there, so if they did it in store perhaps ill just get an exchange
Yeah go ahead with the replacement they will not check into it. Worst case scenario, they will fix it and send it back to you
Sent from my SGH-I747 using xda app-developers app
And luckily i woke up early this morning with confidence that I could spill some crazy story that made it sound like it overheated and died, and now I've got a new one, best be careful with this, i think im going to stay away from CM10, its killed 2 phones of mine lol, I believe any answer i will get will say that it was a user error thanks anyway !!!
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.
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
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
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??