[Q] Samsung Galaxy note 2 crashed and won't turn on - Galaxy Note II Q&A, Help & Troubleshooting

Yesterday, it just turned off while it was in idle mode. The red LED on to the right of 'Samsung' label flashes everytime I press the power button but doesn't turn on. I tried removing the battery, SIM and memory card however, again nothing happening.
also nothing happened when I plugged the charger nor USB cable.
can't also boot on recovery mode nor download mode.
I also tried JIG USB but nothing happened.
Any suggestions would be very much appreciated.

Give it to a service center
Sent From Samsung's Galaxy Note II Using Internet

Hi,
Is there any update about what happened to your phone? Hope this is not the beginning of the "Sudden Death Syndrome of Note 2"...

A similar thing happened to my phone yesterday. It just restarted for no reason when the battery was charged at about 45%. When atempting to restart it got stuck at the screen "Samsung Galaxy Note II GT-N7100". I removed the battery several times, left it charging overnight, but it didn't help. Still gets stuck there. Further more it would not enter recovery mode, but it does enter download mode. What to do? It's under warranty, but I suppose the service center will only open tomorrow.

nothing changed till now with my phone and I still searching for a solution as I dont have warranty.

If it gets into recovery then flash stock rom via odin
Sent From Samsung's Galaxy Note II Using Internet

long shot but you could try checking for dust or crap inside the usb/charge connection. maybe try cleaning it out anyway

I have the same problem!! have you found a solution yet?

engmarwan10 said:
Yesterday, it just turned off while it was in idle mode. The red LED on to the right of 'Samsung' label flashes everytime I press the power button but doesn't turn on. I tried removing the battery, SIM and memory card however, again nothing happening.
also nothing happened when I plugged the charger nor USB cable.
can't also boot on recovery mode nor download mode.
I also tried JIG USB but nothing happened.
Any suggestions would be very much appreciated.
Click to expand...
Click to collapse
Sounds like sudden death syndrome. I doubt there's much you can do but hand it to a service repair center. I think since the note 2 is under a year old you should still have a warranty by default from Samsung service center. Just register your device on their website. That's worth a short. I have it worse since I'm located offshore and if it happens to my note 2 Ill be completely out of luck for the next few months.
Sent from the Rabbit Hole

Galaxy Note 2 won't turn on.
My Note 2 was running perfectly fine ever since I got it. I was playing NFS Most Wanted and then my Note 2 said that the game had crashed. So, I tapped "Ok" on the little pop-up window, and then my Note 2 went back to the home screen. I later took it to my room to charge it because it was just about dead. I had it charging all night and then when I woke up in the morning I found it sitting on my window sill doing nothing. I tried to turn it on thinking that I had turned it off before I went to bed the night before. I then pressed the power button and saw a little red light flash in the upper right hand corner near the proximity and light sensor but nothing happened. The phone won't do anything now except for the little light thing. Plugging it in hasn't done much for me. I though that it was my phone's root access that was causing it to freak out. So I looked up a solution online. I found nothing. I can't get it fixed on warranty because it has root access. Any suggestions on where I could get it fixed or any things I could do at home? Please help. I have been stuck using an old flip phone for 2 or 3 weeks now!

Same Position
Same thing has happened to me. I've had the phone since its release and I've never had an issue with it until the last week.
I'd noticed that the phone would sometimes reboot on its own. This issue only began occurring this week. I'm not too sure if its related or not.
I don't know what happened, one minute it was working... the next I find it stuck at the "Samsung Galaxy Note N7001 screen". I tried pulling out battery and booting again, however I still couldn't get anywhere.
After returning home from work, I tried booting again. Interestingly it got as far as the "Samsung" logo this time; however it still did not start. I tried ONE more time, this time around it actually booted (Albeit slow) and got as far as the lock screen. However as soon as I tried to unlock the screen, it froze (I wasn't able to log back in again after that).
I've tried installing stock ROM using Odin v3.04 and v1.85 on 3 different machines and operating system versions. On each occasion I only get as far as below:
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N7100XXDLL7_N7100DBTDLL2_N7100XXDLK7_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> sboot.bin
<ID:0/003> NAND Write Start!!
<ID:0/003> Complete(Write) operation failed.
<ID:0/003> Added!!
<OSM> All threads completed. (succeed 0 / failed 1)
I've tried doing an emergency recovery using Samsung Kies, however Kies just freezes when it looks to be downloading the firmware. I really only tried this option as I've run out of roads to choose from.
As of right now, all I can do is boot into Download Mode. If I boot into normal mode, I only see the screen that says "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again.
Getting the phone repaired via warranty will also be tough due to the phone being rooted.
I'm out of ideas. Any help or ideas would be greatly appreciated. I'd do just about anything to get my Galaxy Note II up and running again. Ironically, the Galaxy Note II is probably the least I've modified of all my previous Android phones. It was still using original stock ROM, the only modification was the fact it was rooted. My original Galaxy Note got a real workout with ROMs etc. and is still going strong.

If you have can't reboot to recovery but can to download mode. And if it is stuck on galaxy note 2 screen woth red proximity led. Then it's an issue of sds. That means nothing but Samsung can help you. Also if you are unable to boot to download mode its still sds. If you have a counter raise then it would be difficult to claim warranty.
Sent from my GT-N7100 using xda app-developers app

UtkarshGupta said:
If you have a counter raise then it would be difficult to claim warranty.
Click to expand...
Click to collapse
The interesting thing is Download Mode no longer shows that my counter was at one.
It now only shows the following:
ODIN MODE
PRODUCT NAME:
CUSTOM BINARY: No
CURRENT BINARY Samsung Official
SYSTEM SETTINGS: Custom

FunkMonker said:
My Note 2 was running perfectly fine ever since I got it. I was playing NFS Most Wanted and then my Note 2 said that the game had crashed. So, I tapped "Ok" on the little pop-up window, and then my Note 2 went back to the home screen. I later took it to my room to charge it because it was just about dead. I had it charging all night and then when I woke up in the morning I found it sitting on my window sill doing nothing. I tried to turn it on thinking that I had turned it off before I went to bed the night before. I then pressed the power button and saw a little red light flash in the upper right hand corner near the proximity and light sensor but nothing happened. The phone won't do anything now except for the little light thing. Plugging it in hasn't done much for me. I though that it was my phone's root access that was causing it to freak out. So I looked up a solution online. I found nothing. I can't get it fixed on warranty because it has root access. Any suggestions on where I could get it fixed or any things I could do at home? Please help. I have been stuck using an old flip phone for 2 or 3 weeks now!
Click to expand...
Click to collapse
Don't worry about the root access. If it's SDS then you have the right to claim warranty on it.
Sent from the Rabbit Hole

Yeah but then again if they deny free repair which you are eligible to go sue them. They'd have to prove that your actions related to root were responsible for the damage.
Sent from my GT-N7100 using xda app-developers app

engmarwan10 said:
Yesterday, it just turned off while it was in idle mode. The red LED on to the right of 'Samsung' label flashes everytime I press the power button but doesn't turn on. I tried removing the battery, SIM and memory card however, again nothing happening.
also nothing happened when I plugged the charger nor USB cable.
can't also boot on recovery mode nor download mode.
I also tried JIG USB but nothing happened.
Any suggestions would be very much appreciated.
Click to expand...
Click to collapse
Hi,
I have the same problem with my Galaxy Note 2 T-Mobile. I exchanged for new one. After 3 days it was the same problem, so I exchanged it for third one. Next day after exchange the third phone does the same thing, won't turn on after idle mode about 4 times a day. I will get rid of Galaxy Note 2. I am sick of it. Maybe Galaxy S3 is a better option.

Lol you have been trolled.
Just update the firmware and you will be all well then.
Sent from my GT-N7100 using xda app-developers app

jaskula73 said:
Hi,
I have the same problem with my Galaxy Note 2 T-Mobile. I exchanged for new one. After 3 days it was the same problem, so I exchanged it for third one. Next day after exchange the third phone does the same thing, won't turn on after idle mode about 4 times a day. I will get rid of Galaxy Note 2. I am sick of it. Maybe Galaxy S3 is a better option.
Click to expand...
Click to collapse
When you get the replacement the first thing you should do is update it to the latest firmware. I dunno man from the looks of things it seems you've got a lot of bad karma going on, I certainly wouldn't want you anywhere near my phone lol.
Sent from the rabbit hole.

yes, it IS SDS 99% sure.. As it was said in other threads this is becoming really anoying and we should make a Sticked post with the most easy, clear and basic information to be sure that the new owners will not have this problem...
Anyone knows how to say that to the moderators of the forum? I think we MUST do that in order to help the new people
coming back to the thread you have to send to samsung ASAP
I'm really sorry for the people who had this issue it is a expensive phone which have been released with two big problems Exynos and SDS...
Hope someone could say the idea of the thread to the moderators!

UtkarshGupta said:
If you have can't reboot to recovery but can to download mode. And if it is stuck on galaxy note 2 screen woth red proximity led. Then it's an issue of sds. That means nothing but Samsung can help you. Also if you are unable to boot to download mode its still sds. If you have a counter raise then it would be difficult to claim warranty.
Sent from my GT-N7100 using xda app-developers app
Click to expand...
Click to collapse
SDS is slowing killing Note2 too as well? If SDS just send to Samsung for warranty. Even if its rooted Samsung will not find out coz device cannot boot up.

Related

bricked and cant get back to stock

so here's what happened.....
i rooted my note 2 a few days after i purchased it. everything was fine. the only reason i was tryng to get back to unrooted stock was because i was having issues with sms and needed to take the phone to sprint to have them look at it.
well i found and followed the instructions here- http://forum.xda-developers.com/showthread.php?t=2086769
everything was fine til i got home from an event in my city and realized that my phone wasnt charging no matter how long i left it on the charger.
so i downloaded odin3 v3.04 and tried to use lj1 firmware package to put the phone in the state it was when i pulled it out of the box.
well, i tried 3 times and it failed i believe at writing the system.
my battery is at 15% and have no way of charging it. oh, and when i try to turn the device on, the only thing that comes up on the screen is "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again." and i cant even get kies to install on my pc, dont know why it just keeps reinstalling the hotfix and never gets past that point.
what can i do to save my phone?
my sis inlaw has the same device i do and i might be able to use her battery if i have to.
EDIT: I cant believe it but i fixed my phone!!!!!!!!!!!
After alot of rewording my search criteria with the search function on this forum, i finally found this- http://forum.xda-developers.com/showthread.php?t=2241136
This was my salvation! and i did it with only 15% battery to work with.
Its because it wasn't bricked. If it had been actually bricked you wouldn't be able to do anything with it except hold papers in place
Sent from my SPH-L900 using Tapatalk 2
Sorry, soft bricked is what I was gettin at. Im from redneck central and we use one word for just about everything. My bad.
Sent from my SPH-L900 using xda premium
Lol. No worries.:beer:
Sent from my SPH-L900 using Tapatalk 2

Boot Looping with no other options

Hello all,
I hate to be posting in this sections but I am having a problem with one of my S3 (s). The phone all of a sudden started boot looping and will not stay on recovery or download mode for more than 5 seconds. It will not show the battery icon when plugged in or get past the 2nd Samsung icon. The phone was running MOAR 6.1 and was wiped before flashing and working perfectly for about a month. I am wanting to know what my options are as I have searched this forum and have not found a solution yet. Of course my 1 year warranty expired about 7 days ago which I was told when I was calling in to complain about the phone dropping calls and getting hot while charging.
The only thing I am concerned about is if I take it to a Sprint store the phone will get to download mode and shows "custom" in the binary field and flash count of 1 which I think will tell them I am on a custom rom....
Thanks in advance
I attempted to odin the phone back to stock but it restarted an 1/8th of the way through and now get the message: Firmware upgrade encountered an issue. Please select recovery mode in Klies and try again.
What does this mean exactly?
The phone is also powering up when the battery is being inserted and nothing being pressed??
Sounds like your power switch is bad. Mine had the same symptoms, local shop replaced it for $20 today and it works fine now. Not sure on the partial Odin flash.
Sent from my SPH-L710 using Tapatalk 2

Only see grey and white stripes and some other colored dots on screen when turned on

Yesterday, when I tried to use my note 2 in the middle of the day, I found the phone stuck at the Samsung galaxy logo. I took the battery out, then put it back. This time I won't even able to see the note 2 logo when trying to turn on the phone. All I have seen is a relative grey screen with white horizontal stripes parallel to each other and some dots in different colors randomly scattered on the screen. Tried to hold VOLUME + Home + Power, I was able to enter the warning screen and see the warning clearly. So I don't think it is something wrong with the screen. Installed odin on my PC, but it seems the phone is not detected by odin.
Questions:
1. Have I lost everything on my phone?
2. What can I do to fix the problem?
3. If I lost all the data and apps, how do I get all the apps back after I can restore/reinstall the android?
Thanks for any help in advance. And suggestions, helpful links are appreciated.
stanzauid said:
Yesterday, when I tried to use my note 2 in the middle of the day, I found the phone stuck at the Samsung galaxy logo. I took the battery out, then put it back. This time I won't even able to see the note 2 logo when trying to turn on the phone. All I have seen is a relative grey screen with white horizontal stripes parallel to each other and some dots in different colors randomly scattered on the screen. Tried to hold VOLUME + Home + Power, I was able to enter the warning screen and see the warning clearly. So I don't think it is something wrong with the screen. Installed odin on my PC, but it seems the phone is not detected by odin.
Questions:
1. Have I lost everything on my phone?
2. What can I do to fix the problem?
3. If I lost all the data and apps, how do I get all the apps back after I can restore/reinstall the android?
Thanks for any help in advance. And suggestions, helpful links are appreciated.
Click to expand...
Click to collapse
Is your phone Rooted?
Have you ever been able to see the phone with Odin?
What happens when you try to enter recovery?
Yes....
We need information...
Are you able to see the device storage while connected to PC ??
If yes....then your data can be saved...
Please tell us what rom....kernel....and other info....g
Sent from my NOTE 2.750...
Courtesy of our amazing developers...
me too
Hi, I am in the same boat here. Rooted SGH-i317 running Jedi x2 on T-Mobile. It froze one day while searching in chrome browser. I pulled the battery, and now it only boots to the same white screen, with squiggly horizontal lines, it never even gets to the Samsung logo. I can get into download mode, but not recovery. Kies won't recognize the device but Odin does. I have tried flashing the most current official at&t KitKat build and a couple others, but it fails with a "no pit file". When I try to repartition with the pit file it fails as well. Wtf!
Thanks for any suggestions.
guruvince said:
Hi, I am in the same boat here. Rooted SGH-i317 running Jedi x2 on T-Mobile. It froze one day while searching in chrome browser. I pulled the battery, and now it only boots to the same white screen, with squiggly horizontal lines, it never even gets to the Samsung logo. I can get into download mode, but not recovery. Kies won't recognize the device but Odin does. I have tried flashing the most current official at&t KitKat build and a couple others, but it fails with a "no pit file". When I try to repartition with the pit file it fails as well. Wtf!
Thanks for any suggestions.
Click to expand...
Click to collapse
Sounds like hardware failure.
creepyncrawly said:
Sounds like hardware failure.
Click to expand...
Click to collapse
That's too bad. I was going to give this to my kids to fool around with. I guess it's a mixed blessing since Tmob screwed up my insurance, and ended up giving me a $300 discount on a new Note4.

[Q] A sordid tale of Misery & Woe

[Rooting fail: Kernel not seandroid enforcing / Reflashing issue / knox counter]
Greetings all! I have been an avid lurking fan for quite some time and have gained great insights from this forum. So first, I would like to thank the community for being what it is. Second, I would like to apologize for the looming wall of text.
Now onto the show...
So I thought I was being smart when I got one of those cheap memory cards off ebay (generic 32GB). Why pay the extra for the brand name stuff when it was just a piece of plastic, right? Oh if I could only go back in time to slap myself (first of many well-deserved slappings).
So I plugged the card into the phone (T-Mobile Samsung Galaxy S4) and everything seemed to work just great. Then, being the incredibly intelligent person that I am, I moved (slap) all of my photos & music to the card. My gut was telling me to 'copy' them, but I was too smart to listen (slap), because I was being smart: I was backing up my valuable pictures to a solid-state memory card - and those things never fail, right? (SLAP) (no mention of dropbox or google drive please, I have already slapped myself once each for those) Again, everything seemed to work just great - for the first couple of days. Then suddenly, quick as a hotflash, the card was just not readable. Tried it in another phone, tried it in a card reader (apparenly even the generic adapters suck - I had to go and use one of my SanDisk-branded adapters) and the computer didn't even know it was there.
So I did some reading and thought to myself, "Self, those pictures should still be there unless the space was overwritten by something else, right?" Right? Then started the research on things that could dig up these things and after trying a couple (don't remember the names and can't check because the phone is now hosed, but I digress), none found anything.
Being the long-time lurker that I am, I searched this forum and found mention of a program called Diskdigger, however it required Root access (Dun Dun DUUUUUUUUN!) Yeah, I was always a bit squidgy about that. . . .but I REALLY wanted (and still want) to try and recover the pictures. 6-months worth of my heart-wrenchingly adorable kids.
. . .so lurker-me did more reading and found all sorts of threads here (and warnings) about how to root. So I downloaded Odin and installed Kies, and grabbed CWM and the rooting .zip file. Everything seemed to go just swimmingly until the final battery pull and subsequent reboot.
Then came the neverending Samsung Galaxy logo with the microprint message of death: Kernel is not seandroid enforcing
Wha-wha-WHAT? I didn't even know there was such a word, (I am referring to the whole 'seandroid' thing) and didn't know it needed to be enforced.
Back to lurker-based research. I found a couple of threads that talked about this issue and something about a Knox counter came up. Aaaah yes. Samsung Knox. So we finally meet even though I didn't set you up because I didn't like the sound of some of the things you wanted. I don't even remember what they were at this point. Anyway, apparently this protects some of the sensitive areas of the phone sort of like a baseball cup (if a phone had testicles). It also seems to have replaced the binary counter that everyone loves to reset with things like Triangleaway, and is causing this whole tangled mess (over and above my initial stupidity that is [slap])
ANYWAY, I found a thread here and started to participate, however it turned into something that started to look like a thread hijacking, so I figured I would move it into a posting of its own so that everyone can help me bask in the glory of my peny-wise and pound-foolishness.
Onto the current recovery efforts...
Based on the thread I almost hijacked (and others), apparently this issue could be solved by flashing back to the stock rom (although the binary/knox counter would still be tripped)
First I grabbed what I thought was a stock rom-tar-thingy (slap) and waited for it to download in all of its 1.5GB glory - but it wasn't a .tar file. It was a .7z file and Odin's PDA would have none of it. So I tried again with a different file. Again, it took forever (as things do with large files), and again it came up as one of those .7z files. So me being as incredibly intelligent as I am (double-slap), I figured I would game the system and just change the extension and make it a .tar file. (begin histerical laughter and a firm round of slapping)
I am sure you can guess what a rousing success that was.
Back to lurking. Lo & behold, I found more 1+GB files to download! I had no idea if I was v4.2.2 or 4.4.2, so I just grabbed 'em both. About a century later when they were done, I was ready to try again, although it occurred to me (yet another moment of brilliance) that reflashing back to stock would most likely kill the very pictures I had hoped to try and recover in the first place. *cue the sypathetic "aaaaawwww" from the audience* (come on, work with me here)
In any case, I took the first file (I figured I would start with the 4.2.2 file - mostly because the 4.4.2 file had not finished downloading at the time) and plugged it into Odin's PDA line, although I had no idea Odin was into Public Displays of Affection. So the first scary thing was when I set the PDA in Odin (v3.07) to the .md5 file, it apparently had to do a check of its own:
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> M919UVUAMDL_M919TMBAMDL_M919UVUAMDL_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..​...I say "scary" because it took a while and I was not prepared for it (I thought the program had locked-up). Then again I guess anything takes a while with a 2+GB file. :silly:
So I got the phone into download mode and clicked Start, then saw the following:
<ID:0/010> Added!!
<ID:0/010> Odin v.3 engine (ID:10)..
<ID:0/010> File analysis..
<ID:0/010> SetupConnection..
<ID:0/010> Initialzation..
<ID:0/010> Get PIT for mapping..
<ID:0/010> Firmware update start..
<ID:0/010> sbl2.mbn
<ID:0/010> NAND Write Start!!
<ID:0/010> sbl3.mbn
<ID:0/010> rpm.mbn
<ID:0/010> aboot.mbn
<ID:0/010> FAIL! (Auth)
<OSM> All threads completed. (succeed 0 / failed 1)​Based on that (and the big red "FAIL!" in the top left corner), I had the sneaking suspicion that the program was not quite as successful as I had hoped, so I unplugged the phone (the process had not been gong on for very long).
As soon as I unplugged the phone, I got that error saying there was some sort of problem with the firmware download and that I should use Kies to restore my phone. I thought "YAY! Let's let Samsung clean up my mess!!" But oh no... Kies wouldn't have anything to do with my (now) modified phone and said it was (now) not compatible.
So I tried the Odin thing again (still in process) and noticed what I thought was a graphical error of some sort under the "Do not turn off target !!!" message. I do believe that this is actually the initial tippy tip of a progress meter that is just moving at about the speed of congealed phlegm (again, as everything takes a long time with a 2+gb file).
So that is where I am for now. I figure I'll give this thing 30-40 min and see if this tippy-tip would-be progress meter becomes something a bit more profound. The problems that I have (above the obvious) at this point are:
Odin has marked this as a "FAIL!"
Odin's message box lists this as "All threads completed. (succeed 0 / failed 1)
Odin appears to not be doing anything at the moment and is waiting for my next move
The progress meter (wannabe) is not progressing
There is some microprint in the top left corner of my phone screen that reads:
(red text)ODIN MODE
(white text) PRODUCT NAME: SGH-919
CURRENT BINARY: Custom
SYSTEM STATUS: Official
KNOX KERNEL LOCK: 0X0
KNOX WARRANTY VOID: 0X1
CS8-CONFIG-LS8: 0X30 (not sure about the 8s - it is very hard-to-read)
(grey text)WRITE PROTECTION: Enable
eMMC BURST MODE: enable (not sure about the "eMMC", again hard-to-read; also interesting to see the lower-case e's here)
(red text)START [224 1440]
SW REV. CHECK FAIL : fused : 5 , Binary : 1​
My hopes are not high, but I will keep the faith for now to see if that progress meter grows up and makes something of itself in this world of ours. I am not sure if it is just my innately blind sense of optimism, however it seems that the tippy-tip has become a little larger in the time that it has taken to type this posting.
Then again, my marker may have just shifted. I guess we will just have to wait and see.
It is just barely 8am now and I think I need a beer already.
UPDATE: It has been about an hour since I have started that failed Odin reflash thing and that progress meter seems to have failed to live up to its name as there has been no progress. Thankfully the 4.4.2 file has finished its downloading journey and is now in the process of going through the unzipping circus that surrounds any soon-to-be 2+GB file.
Next steps are to run that through Odin and hope for a hail-mary pass. If that doesn't work, I am all out of thoughts (and energy) at this point. Makes me REALLY think I should have just paid the $40 to have one of those "guaranteed" programs do the rooting work for me.
Update: A not-so-happy moment
. . .and now it's time for another edition of "What the hell did that idiot do?"
So the 4.4.2 thing seemed to work. I never thought I would be so happy to hear that tell-tale TMobile "do-do-DEE-do". As it turned out, I must have been 4.2.2 because android started updating. Then checked the apps for compatibility. Then rebooted. Then sent me to the TMobile screen. Then apparently went out and got itself a sandwich as it left me there hanging.
I gave it a reasonable amount of time then determined it was stuck in some sort of error loop. I determined this because I noticed that about every 20-25 seconds or so, the phone would buzz every so quickly and stealthily. I noticed this and determined the buzz interval because I have nothing better to do and am out of steam.
So as I go and try to make a jovial pancake breakfast for those of my family who actually got sleep last night, I would truly appreciate any thoughts at this point.
Help me Obiwan kenobi, you're my only help. . .
When you get done with your slapapocalyps go to development section and download Shinysides NK2 firmware, load into Odin, connect your phone while in download mode and flash NK2 firmware and be done with your slapalanch..
Pp.
Do as above, and use 'cf-auto-root' to root the device. Its the same procedure as flashing the firmware with odin
Thank you to both PanchoPlanet and Serio22 for your responses! The problem with being a 5-year lurking veteran is that I have not yet crossed that magic 10-post threshold, so I can't access the development section just yet.
I will be cooking up a stir fry sunday night madness and then come back to find something on which I can post either something intelligent or insightful.
Serio22, is it safe to assume the cf-auto-root you mentioned is also in the development section? (my apologies for posting before searching - it has been a long day)
One more thing if I may. . . When it comes time to reset the counter, will triangleaway still work or is knox still going to get all up in my BBQ?
Here's Shinyside's link to his firmware thread http://forum.xda-developers.com/showthread.php?p=54155517 this was in general section.
And here's Chainfires CFautoroot http://forum.xda-developers.com/showthread.php?p=41797153 this was in original development.
Follow directions and read through thread for some insight for possible hangups.
And don't sweat Knox, it only comes into play while you still have warranty with Samsung ( 12 months ) once your warranty is up it doesn't matter.
Hopefully this will save you from any further slapattacks.
Enjoy your stir fry. And save us some BBQ.
Pp. :sly:
So I was impressed with that hosting site (Mega) - simple, elegant and fast.
Only problem is: Where the heck did it put the file? I did a search for filename and for filesize and couldn't find a thing. Am I as blind as I feel?
By the way, 10th post - I'm all good now!
Dandman808 said:
So I was impressed with that hosting site (Mega) - simple, elegant and fast.
Only problem is: Where the heck did it put the file? I did a search for filename and for filesize and couldn't find a thing. Am I as blind as I feel?
By the way, 10th post - I'm all good now!
Click to expand...
Click to collapse
At the end of the download a window should come up and ask where you want to save the file, if it didn't, you probably closed the tab too quickly so i would try again and wait for the window
serio22 said:
At the end of the download a window should come up and ask where you want to save the file, if it didn't, you probably closed the tab too quickly so i would try again and wait for the window
Click to expand...
Click to collapse
Thanks serio22 - you two are racking up some serious thank you button pushings. Serves me right for swatting away those annoying popups like a horse's tail on a hot summer day. Then again, I guess I am a bit of a horse's tail for getting myself into this predicament in the first place.
Is there an award somewhere for 'most downloads of ridiculously large files by a non-hacker'? If so, can I self-nominate?
On a different note, while the phone is out of warranty, I do have that monthly 'insurance' thing I pay for that replaces my phone if it ever malfunctions/stops working. Not expensive, only like 4 bucks a month with a $5 deductible. It has served me well as a cheaper alternative to paying for phone upgrades. (I have found that getting/using the most advanced handsets turns you into a paying beta tester, hence I am not what one would call an early adopter of cutting edge mobile phones). Anyway I think I just screwed the pooch on that thing. I'll save the whole 'how do I reset the knox thingy' research for once I am out of this pickle. So for now, back to waiting for the file to download... (think I have a black belt in filewaiting-fu, in the style of the Briqued Fone).
No pop-ups
For some reason, I just am not getting that popup (using firefox 37.0.1). I am going to try on a Mac to see if I get a different result.
Time to sit around like a lump on a pickle while this thing downloads for the third time now...
Oh - Em - Gee!
After the 4th attempt to download that big file, I finally was able to find it. There were no popups or any prompting to save. I just found it on the desktop of the iMac that finally did the trick
1st flash attempt didn't work (boot loop) = curling up to a cold beer & crying.
2nd flash attempt got me back to stock! Sing Hallelujah!
...and I noticed that I was back to where I was before. So I said to myself: Self, those pictures might still be there. After repeated flashings and other memory abuse, they just might still be there! (I may get 3 points for stupidity, but at least 1 point for tenacity)
So I tried the cf-auto-root and got back to my homescreen after a reboot. Quickly tried Diskdigger and couldn't get superuser rights. No SU app. Hmmm... must not have taken. So I tried again, only this time I remembered something I read in another thread where sometimes you have to flash without a reboot, remove the battery, then reconnect and reflash, then remove the battery, then reboot. Not sure why, but apparently in some cases that is what was needed.
...and that is exactly what I did.
Got back to my homescreen and SuperSU was there! So I lit up Disk digger and a SuperUser request came up!! Faster than you could say
OneOne was a horse.
TwoTwo was one too.
OneOne won one race.
TwoTwo won one too.​I lit up diskdigger and started the recovery.
Lo and behold, pictures started to come up! Of course, the very first to come up was a photo of my clothed . . .er. . . derriere from a butt-selfie I sent to my wife. What a way for the universe to greet my success.
Long and short of it is that I got SOME of my pictures back. All of my movies were torn to shreds though. Some were recovered in pieces (no audio, only 2-3 seconds of video), others were just unplayable. Still though, after multiple flashings and other such craziness, I managed to get some back. And I have a working phone. That is rooted.
I am not sure how many times I can say how awesome you guys are. Thank you SO much for all of your help and patience. CF will definitely be getting a donation from my neck of the fishbowl.
Good. Glad I was able to help.
Pp.
Nice! Well hopefully now you've learned your lesson. Never buy cheap memory cards, you get what you pay for. And even with a memory card, I still back everything up to a cloud cause you never know what's gonna happen, better safe than sorry
Ok so donation to chainfire sent - that guy deserves a beer.
If I ever want to go back to the land of Stock, will the latest version of Triangle Away reset the counter or am I now blessed with a rooted (knox-tripped) phone?
Not that I am complaining or anything, just curious...
Dandman808 said:
Ok so donation to chainfire sent - that guy deserves a beer.
If I ever want to go back to the land of Stock, will the latest version of Triangle Away reset the counter or am I now blessed with a rooted (knox-tripped) phone?
Not that I am complaining or anything, just curious...
Click to expand...
Click to collapse
Forever blessed
The audience groans as the OP dusts this thread off and crawls back for a fresh dose of why-am-I-still-awake...
I fell asleep playing a game. At least that is what my sin seemed to be. While waiting for my little one to fall asleep, I was fadoodling around (with an established game that has sucked-up more of my life than staring at pictures of Salma Hayek) and got bagged by the sandman. Meanwhile, the game ate my battery and the phone powered down. Next thing I know, I wake up (with a crimp in my neck for sleeping on the floor) to a dead phone.
Figuring that this was simply a case of a dead battery, I plugged it in, felt that quick bzzzzt, saw the "Samsung Galaxy S4" graphic, then the screen went black. ...it was the lack of a flashing LED that queued me into the fact that something was amiss. Well that and the fact that it wouldn't boot.
So I cracked open the case (nicely of course) and pulled the battery. When I put the battery in, I was greeted with that friendly bzzzt again (I do believe that is a technical term), saw the logo, then nothing. I kept the phone plugged in to give the battery time to charge a bit more and tried again - with the phone still plugged in. Same result.
So I tried power+volume down. Got the warning screen, then went black after about 3 seconds. Tried again and pressed 'volume up' to confirm, got the 'downloading' screen, then it went black.
I tried doing the same thing with the phone plugged in and couldn't even get a Logo splash. So I tried the impossible combo of a near simultaneous battery insert/volume down/power plug insert / volume up - and after succeeding at this death-defying feat, I got a black screen.
I am at a loss. What did I do? I am not even sure for what I should be slapping myself. The only thing I could think of was that I did recently update the SU binary (from within SU itself), but while that did happen within the past 24 hours, it was at least 18 hours ago, so I am not sure if that is the culprit.
Any thoughts? Is the fact that I can't seem to get anything onscreen or to download mode an indicator of a somehow newly-created high-tech brick?
With the addition of a home button press (I think), I was able to get the downloading screen up and on. I tried to get Odin to flash CF autoroot (download of stock ROM in progress), but couldn't get it to complete, so I rebooted the phone and I am back to a BBQ with no coals. I even at one point got that battery graphic to come on - you know the one where you plug in a phone that is turned off. Then the graphic froze and all I could hear was my daughter singing "Let it go.... Let it goooooo...."
I have tried:
Vol Down + power / Vol Down + Home + Power / Vol Down + Home
Warning screen came on, then screen turned off​
Home / Home + Power
Got the Samsung Galaxy S4 Splash Screen, then screen turned off​
Vol Down + Home + Power then Vol Up
Got to "Downloading" screen, then screen turned off​
If I tried any of the above while quickly inserting the charging cord, it made no difference other than I had to unplug the power cord before I could try anything again (otherwise nothing would happen at all)
Each time I get to the Downloading screen and get the plug inserted, a window will pop up and let me know the phone was detected - which would quickly disappear when the screen turns off. I have left the phone plugged in just in case it was charging anyway - doesn't seem to have made a difference.
At this point, I have been sitting so long that I have semi-permanent chair-prints in my backside. I gotta get up... I'll try again when the stock ROM finishes downloading... (a remote THANK YOU to ShinySide for maintaining those links!!)
I kept fiddling with different combinations above. At one point I got the battery graphic to work semi-consistently, so I tried a reboot and it took! I made sure everything that is important was backed-up. The battery was at 14% and charging (albeit slowly). Perhaps because I was backing things up and deleting things to clear space, or perhaps I was just paranoid.
The LED was on, so I tried to soft power-off. The screen turned off, but would not turn back on. I press & held the power button and got a bzzzt as if I turned it off. The battery charging animation was going on but the LED was on a steady red. I press & held the power button, got the brief Bzzt and the SG4 splash, then the screen turned off and I am back to where I was.
I have no idea what is going on - could it be a virus? I do have lookout installed (assuming that is worth the paper it isn't printed on)
I am at a loss...
I think it could be a battery problem. Do you have another battery to try?

[Q] need help with bricked galaxy note 2 (sph-l900)

Recently bought a bricked note 2 off my friend thinking i was going to fix it and was sadly mistaken! Everytime i try to put a new firmware on the phone it either A- goes through the whole process on odin, reboots at the end, the galaxy logo pops up, the screen flashes and just gets stuck at the charging screen frozen or B- fails in the first 5 seconds trying a different firmware and reboots itsself and goes back to the frozen charging screen. it will only turn only if i plug the phone in and really hate to see it sitting around not being used. I guess my friend was trying to root it and he hit the usb cord and It interrupted the download. is there anyway i can fix it and if so how? It would be much appreciated!
BigJohm216 said:
Recently bought a bricked note 2 off my friend thinking i was going to fix it and was sadly mistaken! Everytime i try to put a new firmware on the phone it either A- goes through the whole process on odin, reboots at the end, the galaxy logo pops up, the screen flashes and just gets stuck at the charging screen frozen or B- fails in the first 5 seconds trying a different firmware and reboots itsself and goes back to the frozen charging screen. it will only turn only if i plug the phone in and really hate to see it sitting around not being used. I guess my friend was trying to root it and he hit the usb cord and It interrupted the download. is there anyway i can fix it and if so how? It would be much appreciated!
Click to expand...
Click to collapse
Well if it only turns on while plugged in then one issue is bad battery. Now about the odin problem what version of odin and which tar file are you using?
Sent from my SPH-L900 using XDA Premium 4 mobile app

Categories

Resources