I recently flashed a Pacman 4.3 ROM and today decided to restore my phone back to my stock/rooted Nandroid file that I made beforehand. Used CWM and, after it said the restore was completed, I went to reboot and have been unable to get past the "Samsung Galaxy Note II" bootscreen. It'll go to that screen for a bit and then the entire screen will go black, requiring me to take out and reinsert the battery to do anything else. I can get it into recovery mode and download mode and have tried using factory resets, cache clears, and Odin to try and reset everything back to the original stock firmware, but so far nothing has worked. Every time, I wind up looking at the "Samsung Galaxy Note II" screen for a bit and then the entire screen shuts off.
Can this phone be saved or am I SOL?
Edit: If I take the battery out and put it back in and don't try to turn on the phone, I can plug my phone into my charger and I get a visual on the screen saying the battery is charging and the LED lights up red. For what it's worth.
cptcliche said:
I recently flashed a Pacman 4.3 ROM and today decided to restore my phone back to my stock/rooted Nandroid file that I made beforehand. Used CWM and, after it said the restore was completed, I went to reboot and have been unable to get past the "Samsung Galaxy Note II" bootscreen. It'll go to that screen for a bit and then the entire screen will go black, requiring me to take out and reinsert the battery to do anything else. I can get it into recovery mode and download mode and have tried using factory resets, cache clears, and Odin to try and reset everything back to the original stock firmware, but so far nothing has worked. Every time, I wind up looking at the "Samsung Galaxy Note II" screen for a bit and then the entire screen shuts off.
Can this phone be saved or am I SOL?
Edit: If I take the battery out and put it back in and don't try to turn on the phone, I can plug my phone into my charger and I get a visual on the screen saying the battery is charging and the LED lights up red. For what it's worth.
Click to expand...
Click to collapse
This is gonna sound like a long shot, but are you sure your battery has juice? I had something very similar to what happened to you on a tablet I owned. I thought the device was messed up, but it was just really low on battery somehow. Left it sitting on the charger for a few hours and it came back.
cptcliche said:
I recently flashed a Pacman 4.3 ROM and today decided to restore my phone back to my stock/rooted Nandroid file that I made beforehand. Used CWM and, after it said the restore was completed, I went to reboot and have been unable to get past the "Samsung Galaxy Note II" bootscreen. It'll go to that screen for a bit and then the entire screen will go black, requiring me to take out and reinsert the battery to do anything else. I can get it into recovery mode and download mode and have tried using factory resets, cache clears, and Odin to try and reset everything back to the original stock firmware, but so far nothing has worked. Every time, I wind up looking at the "Samsung Galaxy Note II" screen for a bit and then the entire screen shuts off.
Can this phone be saved or am I SOL?
Edit: If I take the battery out and put it back in and don't try to turn on the phone, I can plug my phone into my charger and I get a visual on the screen saying the battery is charging and the LED lights up red. For what it's worth.
Click to expand...
Click to collapse
Charge up phone....
Try this.
http://forum.xda-developers.com/showthread.php?t=2618447
Thanks for the help guys, I managed to fix it. What I did was download the stock ROM file from here: (can't post the URL for some reason) and then opened Odin, put it in the PDA slot, put my phone into Download Mode, connected it to my computer, and ran it. Phone rebooted back to a factory reset version.
The link I used is from a site called "Stockroms" and, after typing stockroms, add the following to the URL: .net/file/GalaxyNote2/SGH-I317/I317UCAMA4_I317ATTAMA4_ATT.zip
cptcliche said:
Thanks for the help guys, I managed to fix it. What I did was download the stock ROM file from here: (can't post the URL for some reason) and then opened Odin, put it in the PDA slot, put my phone into Download Mode, connected it to my computer, and ran it. Phone rebooted back to a factory reset version.
The link I used is from a site called "Stockroms" and, after typing stockroms, add the following to the URL: .net/file/GalaxyNote2/SGH-I317/I317UCAMA4_I317ATTAMA4_ATT.zip
Click to expand...
Click to collapse
Excellent. Congrats
Sent from my SAMSUNG-SGH-I317 using XDA Premium 4 mobile app
Related
Hello, this is kind of a long story but.......I was in clockworkmod recovery looking to restore back to a backed up rom. I saw a backup titled, 2000-01-01.00.00.16/. I didn't remember a backup that had that named and it said it was from the year 2000. Out of curiosity I decided to backup to it. Then It got stuck or what appeared to be stuck on "checking md5 sum". After ten minutes I pulled the battery thinking it hadn't even started restoring. When I put the battery back in I got the charging battery icon with a cloud and a thermometer, assuming this meant that the phone was to hot I felt the back and it wasn't hot at all. I tried to power the phone off but each time I turned it back on I got the same icon. Finally I tried plugging it in. Then the icon went away and the booted into clockworkmod. So then I restored to the Unnamed rom and the led notification light wouldn't go off. Then every time I turn the phone off I get the thermometer icon and have to plug it in. On top of that my computer won't recognize the phone. I want to use Odin to go back to stock but since the computer won't recognize it I'm stuck with a phone full of problems. Any suggestion?
First backups can't contains signs /&%*+# etc...
Second.. can you get to recovery?
Sent from my SPH-D710 using XDA Premium App
omg .. i THINK YOU BRICKED YOUR PHONE!!
But not to worry, most likely it's an easy fix. Reboot phone a couple times, MAKE SURE DRIVERS & EVERYTHING are INSTALLED FIRST, open ODIN with proper .TAR file, .PIT NOT needed. Only Auto Reboot box should be checked, then plug in to pc. Wait for phone to connect and hit start. BE PATIENT. If it doesn't work try booting into CMW, holding POWER and VOL UP buttons. Hope this helps!
Thanks everyone for the help. I ended up downloading mobile odin from the market, and then flashing the stock unrooted EK02.tar file. I still had the same problems and figured it was a hardware problem. So I took it into my local sprint store and they took one look and it and ordered me knew for free, no questions asked!
I tried flashing the Zeus kernel using CWM, but I failed to realize the kernel was for the Verizon S3. When I restarted after flashing, it displayed the Samsung logo for a split second and then went to a black screen. The screen was on, but it only showed black. At this point I passed out, and when I woke up it was still on the black screen. I pulled the battery and tried to restart, and got the same black screen. Then I tried every way I know of (except using a jig) to get into download mode to no avail. Now when I turn it on, it vibrates once, flashes the logo, and then the screen shuts off and is useless. I think there's a solid chance I've ruined it this time, but if anybody has any suggestions they would be greatly appreciated. Thanks!
Put the phone in dl mode. It's possible the screen will be black and you can't actually see it's in dl mode. Plug into your computer. Odin flash a stock Rom.
The fact that it's doing something means it is not completely ruined. It just may be harder to restore to working order.
Also, take a look at this thread
http://forum.xda-developers.com/showthread.php?t=1746665
(Originally posted this in the wrong forum, so I am reposting here.)
I have the Galaxy Note II with T-Mobile.
Some background: It was running Android 4.1.2. I rooted my phone once, about two weeks ago, just so I could take an image of it in case of an update issue. (I think the software was called nandroid.) Once I took the backup, I unrooted it again.
Since then, doing the Software Update check under settings never returned any results. It would just keep checking until I clicked cancel.
Anyway, when T-Mobile released the 4.3 update Monday morning, I tried updating to it using the Kies software on my PC (by connecting it through the USB cable). It got up to about 60% installation and then just hung for over an hour. So I unplugged the phone, re-plugged it back in, and then attempted the emergency firmware recovery through Kies. It went through this and got upto 76% installation and then just hung again for another hour. I again unplugged it to re-try the emergency recovery again, but every time I connected the phone, Kies would not detect it again. I re-seated the battery, rebooted my computer, uninstalled and reinstalled Kies, but Kies would not detect my phone again.
I am/was running the stock rom, but my phone won't even boot into it's normal screen. Any time I turn it again, i see the screen--"there were errors during firmware upgrade. try emergency recovery in Kies."
I can't even figure out a way to get to a screen where I can install the image I took using Nandroid a few weeks ago.
Any help or advice anyone can provide would be extremely appreciated!
Use Odin to fix it.
If you can put your phone into download mode then it should be 'saveable' ..
Double0EK said:
Use Odin to fix it.
If you can put your phone into download mode then it should be 'saveable' ..
Click to expand...
Click to collapse
I am able to put it into download mode. When I follow the instructions I found for Odin, the process seems to go smoothly. However, once my phone reboots, it stays on the "Samsung Galaxy Note II" screen (with the black background). I've left it like that for over 30 minutes, and it just stays on that screen.
Should there be another step I should be following?
diggeryo said:
I am able to put it into download mode. When I follow the instructions I found for Odin, the process seems to go smoothly. However, once my phone reboots, it stays on the "Samsung Galaxy Note II" screen (with the black background). I've left it like that for over 30 minutes, and it just stays on that screen.
Should there be another step I should be following?
Click to expand...
Click to collapse
Try installing SuperSU from Playstore
It has an option of doing a FULL UNROOT
I am sure that will help.
If not then install Rom Manager from PS
Through RomManager reboot in Recovery
1.) Wipe device 3x times
2.) Wipe cache 3x times
3.) Under advance you will Find Dalvik Cache -- wipe that 3x times
[MENTION=522570 [MENTION=1065870 [user=1879310]@@@@[/user][/MENTION]@@[/MENTION]@@
But more importantly why would you want 4.3 stock anyway?
Install TWRP Recovery or ClockWorkMod recovery and install/Flash CM1 (Cyagonemod) or any other custom roms 4.4.x kitkat
Nothing is really working for me.
I can't boot into normal mode. I am able to get into "download" mode, but whenever I try to load an image using the Odin software (both a stock image and a Cyagonemod image), it starts to load the image, but just hangs a certain percent of the way through.
I also can't get to that screen where it gives you the text based options to wipe your device, cache, etc.
I've tried loading both TWRP recovery and ClockWorkMod recovery (through Odin), and though it seems to load properly (Odin says "Pass"), when the phone reboots, it goes to the "Samsumg Galaxy Note II" screen (the one with white text on a black background), and just stays there.
I've gotten T-Mobile to agree to send me a new phone. But if I can't get into any of the items I mention above, how can I make sure my old device is wiped before sending it back to them?
Just do this un root with chain fire root away app.
Then use triangle away app.
Then find 4.1.2 MB1 stock Odin tar. The complete package .
Odin to stock .
Reboot and then update via Ota.
You have to un root first and also have to triangle away which removes flash counter in Odin.
System modified status will not allow Ota.
That's the best suggestion I have
Sent from my SGH-T889 using xda app-developers app
diggeryo said:
Nothing is really working for me.
I can't boot into normal mode. I am able to get into "download" mode, but whenever I try to load an image using the Odin software (both a stock image and a Cyagonemod image), it starts to load the image, but just hangs a certain percent of the way through.
I also can't get to that screen where it gives you the text based options to wipe your device, cache, etc.
I've tried loading both TWRP recovery and ClockWorkMod recovery (through Odin), and though it seems to load properly (Odin says "Pass"), when the phone reboots, it goes to the "Samsumg Galaxy Note II" screen (the one with white text on a black background), and just stays there.
I've gotten T-Mobile to agree to send me a new phone. But if I can't get into any of the items I mention above, how can I make sure my old device is wiped before sending it back to them?
Click to expand...
Click to collapse
have you tried booting into recovery? after you load the custom recovery with odin and it reboots, pull the battery put it back, then hold vol up + home and then + power. hold all 3 until recovery. try a factory reset and reboot.
Sent from my SGH-T889 using XDA Premium 4 mobile app
wolfpack612 said:
have you tried booting into recovery? after you load the custom recovery with odin and it reboots, pull the battery put it back, then hold vol up + home and then + power. hold all 3 until recovery. try a factory reset and reboot.
Click to expand...
Click to collapse
I have. It brings me to the same screen with the Samsung Galaxy Note II text on the black background and just stays there.
So, in summary, I can get into download mode (vol down+home+power), but it seems nothing else.
Try factory settings the phone through stock recovery and then check your phone status. It should say 'normal' but if it says 'modified,' download Triangle away and run the tracking setting (it'll make your phone say normal so you can download the OTA). Given you're on tmobile and your phone is the T889 model, check for software updates and install the OTA. Your phone will take a bit and will probably be stuck on the T-Mobile 4G boot screen for several minutes (it's normal). This should work.
Didn't find anything similar on here so I had to post. My T999 no longer boots except for a vibrate when the battery is removed and re-inserted. Occasionally it will get to the CM boot logo and then the screen goes off. If I time the button presses right, I get to the Download screen but before I can hit the Up button to confirm download mode the screen shuts off. This happened all of a sudden yesterday, the last activity being to shut off the Alarm. Tried charging but it will not get past the initial battery icon before the screen goes off. Tried replacing the battery but that didn't help. I also tried to follow the debrick instructions but it didn't help. I was running Vanir AOSP 4.4.4 with no issues until yesterday. The device does not register when connected to the PC using USB and the charger LED does not light up when plugged into charger/PC. My feeling is that something went wrong with the boot but I am unable to get into any usable screen to do anything. I had managed to brick a Samsung Vibrant before but I didn't have to struggle as much to debrick and ODIN back to stock. Any help would be greatly appreciated, I'm now without a phone .
Mine is also acting like that. It wont boot to any rom even stock ones. But i noticed that if i connect my charger it will boot to the homescreen. Sounds like a battery issue right? I also thought that but when i go to recovery, it did not shutdown after leaving it for a couple of minutes. I'm also baffled why it wont boot. I'll try to borrow other battery to test if it still the same.
maelstromm said:
Didn't find anything similar on here so I had to post. My T999 no longer boots except for a vibrate when the battery is removed and re-inserted. Occasionally it will get to the CM boot logo and then the screen goes off. If I time the button presses right, I get to the Download screen but before I can hit the Up button to confirm download mode the screen shuts off. This happened all of a sudden yesterday, the last activity being to shut off the Alarm. Tried charging but it will not get past the initial battery icon before the screen goes off. Tried replacing the battery but that didn't help. I also tried to follow the debrick instructions but it didn't help. I was running Vanir AOSP 4.4.4 with no issues until yesterday. The device does not register when connected to the PC using USB and the charger LED does not light up when plugged into charger/PC. My feeling is that something went wrong with the boot but I am unable to get into any usable screen to do anything. I had managed to brick a Samsung Vibrant before but I didn't have to struggle as much to debrick and ODIN back to stock. Any help would be greatly appreciated, I'm now without a phone .
Click to expand...
Click to collapse
Remove battery snd put back in. Does the device try to turn on by itself? If so you probably have a bad power button.
LarsonJayz said:
Mine is also acting like that. It wont boot to any rom even stock ones. But i noticed that if i connect my charger it will boot to the homescreen. Sounds like a battery issue right? I also thought that but when i go to recovery, it did not shutdown after leaving it for a couple of minutes. I'm also baffled why it wont boot. I'll try to borrow other battery to test if it still the same.
Click to expand...
Click to collapse
Boot download mode and flash stock or root66 firmware with Odin. (You may need to factory reset too)
DocHoliday77 said:
Boot download mode and flash stock or root66 firmware with Odin. (You may need to factory reset too)
Click to expand...
Click to collapse
Done this using root66 but still the same. Now my phone went to worse. It wont get past the S3 logo in the boot screen and just shuts down followed by a vibrate. But if i connect my charger, it will continue and run as normal. My suspect might be a bad battery but the thing is it doesn't auto shutdown when is download mode or in recovery mode. Will try to borrow other battery and update if this fixes the problem.
This is pretty strange. Woke up to my phone with the Galaxy s3 boot logo. And it wouldn't go past it. Tried flashing different backups I had but none of them let me go past the boot logo. Flashed CM10 since my version of TWRP recovery is so old that it can't flash anything higher up, and it goes past the boot logo finally after 2 hours then goes to the cyanogen boot logo but doesn't go past that. I'm going to try with ODIN tonight.
Seems very strange that there are others that had this happen to them to. My phone has never done this before, and it happened randomly.
What does it mean if my phone doesn't boot past the logo with an odin to root66 file?
Edit: Nevermind seems to have worked... for now.
Edit 2: Okay so now it's stuck in an infinite loop where it boots past the logo, shows the android mascot then does an android is upgrading app 1 of 169 then goes back all over again. This is fun! Can anyone help?
Edit 3: Okay so I had to do a factory reset. Got it working now. Starting to get sick of the things I have to do to get updated firmware. Samsung needs to get their crap together!
LarsonJayz said:
Done this using root66 but still the same. Now my phone went to worse. It wont get past the S3 logo in the boot screen and just shuts down followed by a vibrate. But if i connect my charger, it will continue and run as normal. My suspect might be a bad battery but the thing is it doesn't auto shutdown when is download mode or in recovery mode. Will try to borrow other battery and update if this fixes the problem.
Click to expand...
Click to collapse
Hopefully its just the battery.
Download mode may work because of how the battery reports to the os. If its going bad and reporting incorrectly that its low, it may trigger a shutdown. Whereas in download mode the os isn't running so its not reading the battery info the same way. Just a guess.
crazexr7 said:
What does it mean if my phone doesn't boot past the logo with an odin to root66 file?
Edit: Nevermind seems to have worked... for now.
Edit 2: Okay so now it's stuck in an infinite loop where it boots past the logo, shows the android mascot then does an android is upgrading app 1 of 169 then goes back all over again. This is fun! Can anyone help?
Edit 3: Okay so I had to do a factory reset. Got it working now. Starting to get sick of the things I have to do to get updated firmware. Samsung needs to get their crap together!
Click to expand...
Click to collapse
Just for future reference, factory resetting solves about 98% of boot hangs.
Still for both of you, id take this as a sign that you should make sure your backups are up to date. If something is failing you'll be glad you did!
DocHoliday77 said:
Just for future reference, factory resetting solves about 98% of boot hangs.
Still for both of you, id take this as a sign that you should make sure your backups are up to date. If something is failing you'll be glad you did!
Click to expand...
Click to collapse
Yeah factory reset unfortunately didn't work for me when I needed it before I had to ODIN to root66. But I was able to do a nandroid after I couldn't get it to boot and extract my sms from Titanium backup. What an awesome app, super thankful to that dev for making it.
DocHoliday77 said:
Hopefully its just the battery.
Download mode may work because of how the battery reports to the os. If its going bad and reporting incorrectly that its low, it may trigger a shutdown. Whereas in download mode the os isn't running so its not reading the battery info the same way. Just a guess.
Click to expand...
Click to collapse
Turns out it was the battery sir. I've tested it with another battery from 2 different phones and it worked fine. While the phone i tested with the defective battery didn't event get passed the samsung logo. I've suspected it might be having the low voltage causing the phone to shut down.
Anyways, after that i bought a new battery immediately and everything seems ok. thanks for the reply doc.
DocHoliday77 said:
Remove battery snd put back in. Does the device try to turn on by itself? If so you probably have a bad power button.
Click to expand...
Click to collapse
I can confirm that it is likely a bad power button, I have tried everything including dismantling it and seeing if I could dislodge any dirt that may be causing the problem but it didn't work. Looks like I have to find a local repair shop or ebay to get it resolved. Anyone recommend a good place to get this fixed. Funds are limited
Im not sure exactly how difficult the repair is most people seem so do it themselves and have given indications that its pretty easy. You can find the part online for a few bucks.
I was playing pokemon go and I got a facebook messenger message, and my phone just crashed and started boot looping at the Galaxy note ii screen. I tried going into the recovery and deleting the cache and factory resetting it, tried flashing it with ODIN, and nothing seems to be fixing it. I've tried flashing it to the stock rom too, but that seemed to make things worse? Now half the time when I try and turn it on it it wont turn on unless I plug it in or remove and put back the battery, when I try charging it when it's off it turns on and I can see the battery screen, but it freezes either when loading or when the animation plays. There's no red light and I'm not even sure it's charging.
I can get to the CWM menu and the recovery menu, I did have the Nandroid backup files but it seems like I mistakenly deleted it, so that's an option. I tried flashing it with different firmwares and it doesn't seem to make a difference. The first time I flash it it usually goes to the T-Mobile splash screen, which plays the little animation and sound but stays at that screen. Any Ideas?
I tried reflashing it another few times and now I actually got into the setup screen and got to the home screen. It charges somewhat normally but it still boot loops when I start it. When I plug the charger in when it's looping it boots fully and I got to the point where I installed an update. Not I'm stuck in a loop on the T-mobile splash
Try a new battery.
Bell-wether said:
I was playing pokemon go and I got a facebook messenger message, and my phone just crashed and started boot looping at the Galaxy note ii screen. I tried going into the recovery and deleting the cache and factory resetting it, tried flashing it with ODIN, and nothing seems to be fixing it. I've tried flashing it to the stock rom too, but that seemed to make things worse? Now half the time when I try and turn it on it it wont turn on unless I plug it in or remove and put back the battery, when I try charging it when it's off it turns on and I can see the battery screen, but it freezes either when loading or when the animation plays. There's no red light and I'm not even sure it's charging.
I can get to the CWM menu and the recovery menu, I did have the Nandroid backup files but it seems like I mistakenly deleted it, so that's an option. I tried flashing it with different firmwares and it doesn't seem to make a difference. The first time I flash it it usually goes to the T-Mobile splash screen, which plays the little animation and sound but stays at that screen. Any Ideas?
Click to expand...
Click to collapse
Did you try Samsung Kies' emergency recovery option yet?