So I am having a problem with my Samsung Galaxy note 2. It was originally with AT&T until the contract had ended so I decided to use T-Mobile instead. I had to downgrade my firmware from 4.3 to unlock because ATT refused to unlock it. Anywho, it was working fine until it started getting this Samsung (ATT) update kept popping up repeatedly and accidentally I pressed for it to apparently download and I didn't realize it until the last minute. My phone began to restart and it got stuck on the "Samsung Galaxy Note 2" boot screen.
To make a long story shorter than what it already is, I tried everything to fix this I could possibly think of. From trying to go back to stock firmware, enter recovery mode (which it will not let me enter) and nothing will work. I am scared I am not going to be able to find a solution, as I've did research and attempts for over 8 hours today, so I'm somewhat on the edge. If anyone could help, it'd be much appreciated! I am also sorry if this type of thread has been posted, it's just I have tried everything on other threads and websites an can't seem to find a solution. Maybe I am doing something wrong, or just can't find the right stuff
Flash (in Odin) the tz-param file linked in post #2 here....
http://forum.xda-developers.com/showthread.php?t=2618447
That should allow the ota update to complete and allow phone to boot or at least get you recovery mode and allow you to wipe cache - assuming there are artifacts from the ota.
Sent from my SAMSUNG-SGH-I317 using XDA Premium 4 mobile app
Thankyou!
Thankyou so much! It worked wonderfully!
Related
So, at the risk of posting too much info (instead of not enough) I'm going to start at the beginning:
I rooted my wife's S3 and loaded TWRP and Paranoid Android. It ran fine, but there was a camera issue, so she wanted me to restore it to the stock ROM. I did this (to 4.1, I believe, whatever was out in August). Again, it ran fine and I was planning to restore the root access, but did not.
Later, it was dropped in Hibachi sauce (not sure this is relevant, but in case) and we put it immediately in rice. It worked fine, other than the touch screen intermittently ceasing to receive touch commands.
When the updated ROM came from Samsung, my wife installed the update and the phone continued to work fine, other than the screen issue.
She was tired of the issue and decided to sell it to buy an iPhone (shudder) so she did a factory reset. This is where the issues began (I included the previous steps as I'm not sure which may have caused the current issue).
Upon the factory reset, the phone would only boot to the beginning of the AT&T logo loading. I thought it may be something she could fix through Kies and suggested she try that, so she did. The phone would then boot to a screen in Odin mode that says "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again." We did this and there was no help.
I can get it to boot into recovery (the default one now) and have tried to reflash that and the stock ROM that I did previously and only can get two actions: either the freeze at the AT&T logo (if I use Odin to flash the ROM) or the above message in Odin mode (after trying to fix from Kies).
I'm not sure what to do at this point and would appreciate any and all help you guys can provide. I've lurked around and learned quite a bit to flash my ROM and my wife's from you guys, so I'm really hoping I can learn more from this.
Thanks in advance!
Fearborn said:
So, at the risk of posting too much info (instead of not enough) I'm going to start at the beginning:
I rooted my wife's S3 and loaded TWRP and Paranoid Android. It ran fine, but there was a camera issue, so she wanted me to restore it to the stock ROM. I did this (to 4.1, I believe, whatever was out in August). Again, it ran fine and I was planning to restore the root access, but did not.
Later, it was dropped in Hibachi sauce (not sure this is relevant, but in case) and we put it immediately in rice. It worked fine, other than the touch screen intermittently ceasing to receive touch commands.
When the updated ROM came from Samsung, my wife installed the update and the phone continued to work fine, other than the screen issue.
She was tired of the issue and decided to sell it to buy an iPhone (shudder) so she did a factory reset. This is where the issues began (I included the previous steps as I'm not sure which may have caused the current issue).
Upon the factory reset, the phone would only boot to the beginning of the AT&T logo loading. I thought it may be something she could fix through Kies and suggested she try that, so she did. The phone would then boot to a screen in Odin mode that says "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again." We did this and there was no help.
I can get it to boot into recovery (the default one now) and have tried to reflash that and the stock ROM that I did previously and only can get two actions: either the freeze at the AT&T logo (if I use Odin to flash the ROM) or the above message in Odin mode (after trying to fix from Kies).
I'm not sure what to do at this point and would appreciate any and all help you guys can provide. I've lurked around and learned quite a bit to flash my ROM and my wife's from you guys, so I'm really hoping I can learn more from this.
Thanks in advance!
Click to expand...
Click to collapse
So is it stuck on the AT&T Logo? Or Samsung Logo?
UnknownTroll1 said:
So is it stuck on the AT&T Logo? Or Samsung Logo?
Click to expand...
Click to collapse
It was the AT&T logo, it's currently the Odin. If I flash it again with the stock ROM, it'll be the AT&T logo again, but it doesn't completely load the AT&T logo. The Samsung one loads and then the AT&T starts to load, but doesn't finish playing.
Anyone?
Yes, Odin to stock unrooted, then go ahead and factory reset by holding volume up + home button on first boot. Done.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
jblparisi said:
Yes, Odin to stock unrooted, then go ahead and factory reset by holding volume up + home button on first boot. Done.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
If this works (I'll try it when I get home) I will be so grateful! BTW, do you happen to have a decent link to a stock ROM? If not, I'll Google it tonight.
So I have an Att Note 2, which is bricked or soft bricked. I am a very rookie Android guy when it comes to modifying or hacking. I did root my Note 2 with Cyanogenmod. However, I missed S Note and the use of my S Pen so I researched a bit to get back to stock with the use of Odin and stock roms found on the net. I was successful, and actually amazed it worked. Long story short, a few days after that, an OTA update hit my phone, didn't even think about it and began the download. The phone downloaded the update, and rebooted to complete the install. The problem is, during reboot, the phone got stuck on the "Samsung Galaxy Note II" screen. I researched a bit online, and everyone said get to recovery mode and do a few things. Problem is, I can't get into recovery mode, I can only get the screen described above, and the download screen, THAT IS ALL. Looked a bit more online and attempted to flash various stock roms with Odin. Some were successful, Odin passed, and the phone would get stuck on the Note II screen again, and would not boot into recovery mode, same issue with only being able to access download mode. The unsuccessful flash attempts got me to screen informing me that Kies needs to be used to update my firmware. Kies showed a recovery code, which was downloaded, but unsuccessful. It would download all the way, but at the end of install, it would fail. Funny thing is it would work enough to get me back to the ability to get into download mode. I just want my Note 2 working again. Is there any way to wipe my phone completely clean, and start over? Or is there any way to even re-root it, or flash any sort of rom on there, just so I can use the damn thing? I need some help by you pros out there ! Please!
titostats said:
So I have an Att Note 2, which is bricked or soft bricked. I am a very rookie Android guy when it comes to modifying or hacking. I did root my Note 2 with Cyanogenmod. However, I missed S Note and the use of my S Pen so I researched a bit to get back to stock with the use of Odin and stock roms found on the net. I was successful, and actually amazed it worked. Long story short, a few days after that, an OTA update hit my phone, didn't even think about it and began the download. The phone downloaded the update, and rebooted to complete the install. The problem is, during reboot, the phone got stuck on the "Samsung Galaxy Note II" screen. I researched a bit online, and everyone said get to recovery mode and do a few things. Problem is, I can't get into recovery mode, I can only get the screen described above, and the download screen, THAT IS ALL. Looked a bit more online and attempted to flash various stock roms with Odin. Some were successful, Odin passed, and the phone would get stuck on the Note II screen again, and would not boot into recovery mode, same issue with only being able to access download mode. The unsuccessful flash attempts got me to screen informing me that Kies needs to be used to update my firmware. Kies showed a recovery code, which was downloaded, but unsuccessful. It would download all the way, but at the end of install, it would fail. Funny thing is it would work enough to get me back to the ability to get into download mode. I just want my Note 2 working again. Is there any way to wipe my phone completely clean, and start over? Or is there any way to even re-root it, or flash any sort of rom on there, just so I can use the damn thing? I need some help by you pros out there ! Please!
Click to expand...
Click to collapse
Download the latest kies from the samsung website.. and then open tools and then firmware update and initialization.. pull out the battery and type the model number and serial number kies asks.. follow the instructions.. your phone will be fine..
Sent from my GT-N7100
titostats said:
So I have an Att Note 2, which is bricked or soft bricked. I am a very rookie Android guy when it comes to modifying or hacking. I did root my Note 2 with Cyanogenmod. However, I missed S Note and the use of my S Pen so I researched a bit to get back to stock with the use of Odin and stock roms found on the net. I was successful, and actually amazed it worked. Long story short, a few days after that, an OTA update hit my phone, didn't even think about it and began the download. The phone downloaded the update, and rebooted to complete the install. The problem is, during reboot, the phone got stuck on the "Samsung Galaxy Note II" screen. I researched a bit online, and everyone said get to recovery mode and do a few things. Problem is, I can't get into recovery mode, I can only get the screen described above, and the download screen, THAT IS ALL. Looked a bit more online and attempted to flash various stock roms with Odin. Some were successful, Odin passed, and the phone would get stuck on the Note II screen again, and would not boot into recovery mode, same issue with only being able to access download mode. The unsuccessful flash attempts got me to screen informing me that Kies needs to be used to update my firmware. Kies showed a recovery code, which was downloaded, but unsuccessful. It would download all the way, but at the end of install, it would fail. Funny thing is it would work enough to get me back to the ability to get into download mode. I just want my Note 2 working again. Is there any way to wipe my phone completely clean, and start over? Or is there any way to even re-root it, or flash any sort of rom on there, just so I can use the damn thing? I need some help by you pros out there ! Please!
Click to expand...
Click to collapse
Try flashing a recovery for ur device with Odin, not a ROM, just flash twrp recovery with Odin, after u flash the recovery u will be able to access recovery and flash a stock ROM through twrp. I think what happened to u is when u flashed the update it tried to right over the unlocked bootloader which caused the soft brick, try flashing the recovery for ur device and if that doesn't work try the above posters way...
Sent from my Nexus 5 using XDA Premium 4 mobile app
Device: Samsung Galaxy Note 8.0 WiFi Tablet ((GT-N5110))
-+-+-+-+-+-+-+-
Last night I started to attempt to return my GT-N5110 to the complete Stock ROM and everything however after spending HOURS looking for the Stock ROM files, I decided to try downloading the ROM directly from the Note 8.0 Toolkit. After it finished downloading and I installed it via ODIN like the toolkit asked, I tried to turn my tablet on and now it won't boot past the Samsung logo boot screen.
If someone could please give me the URL of the correct files needed as well as to a walk-through webpage so that I can fix this annoying problem and get my Note 8 up and running again, I'd greatly appreciate it.
Unfortunately I have been unable to find anything that even looks like it could work on my GT-N5110 on here so I have been rather hesitant to try using the stock files for a different model of the Note 8.0 rather than whichever is needed for the WiFi model. I've finally thrown in the towel and am asking someone, ANYONE, for some help.
Thanks guys!
you can get mostly all of stock firmware on sammobile.com
http://www.sammobile.com/firmwares/2/
Update
I downloaded the firmware from that site and followed the instructions that were provided with the firmware download however I'm still stuck at the Samsung boot screen. I tried leaving it alone for a while since I know that after installing a gapps file, the first boot may take a little bit but it stays on the same screen.
There has to be something I'm missing because I've never had this much trouble with any of my devices before. I thought to try an Emergency Firmware Restoration using Kies but my tablet doesnt show as being connected in Kies.
Anyone know what I'm unknowingly doing wrong?
Get into stock recovery and factory reset, should clear up the being stuck at Samsung boot.
CKrzacz said:
Get into stock recovery and factory reset, should clear up the being stuck at Samsung boot.
Click to expand...
Click to collapse
+1
CKrzacz said:
Get into stock recovery and factory reset, should clear up the being stuck at Samsung boot.
Click to expand...
Click to collapse
^^^^^This^^^^^
OR
Check this post out, http://forum.xda-developers.com/showthread.php?t=2289441 if CKrzacz's tip didn't work.
Where to start...
First, as a disclaimer, I may use language or terms that sound noobish. I have rooted and run custom ROMs on several devices in the past, however generally when I get a ROM I like I stick with it, so I'm not constantly tinkering. I've done my best to search and find solutions so please go easy on me.
17 days ago I was running stock 4.3 on my SGNII when the battery died. Upon charging I found I was stuck in bootloop and had a bad /efs mount. I searched and searched and spent around 15 hours trying this and that but to no avail. I finally threw my hands in the air and got ahold of Josh at mobiletechvideos and he was able to fix the efs mount issue. However, he left me in factory mode which required me to root to get out of, and once I did this I was unable to activate data on my carrier (Ting). I was so happy to have my phone "back" though that I used it like this for 4 or 5 days. I could get on wifi and I could call and send text messages. I had been off the grid so this felt like something I'd fix fully later.
Well I kept reading and found "fix" after "fix", flashed this and that and still no dice. FINALLY, last night, I found this thread: http://forum.xda-developers.com/show....php?t=2086769 which helped immensely. I was able to get TWRP flashed by unchecking the "auto-reboot" option in Odin and pulling the battery after the update took, and via TWRP I was able to install the ROM. I booted up, the device activated, I was running 4.1.2, I made and received some calls, the birds were chirping, the air was sweet...
I had struggled for so long and I had finally achieved success! Then, for seemingly no reason at all, I accepted an OTA update which bricked my Note2. Devastation.
The current state of things...
* Cannot get past the initial "Samsung Galaxy Note 2" screen
* Cannot boot into recovery
* I CAN get into dl mode,
* but, I CANNOT successfully flash anything. TWRP will flash like it took, but upon reboot I'm not able to boot into it. I'm also able to flash a ROM but it fails when it gets to sbin, and upon rebooting I'm greeted by the screen "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again."
When I try to use Kies it doesn't find the device. I've installed all of the most recent drivers and I'm running Kies as administrator. I select Tools > Emergency Firmware Recovery, THEN connect my device as instructed.
I'm at the apex of frustration. I beg thee to help!!
I have roughly the same situation. Was rooted and on an MK4 rom, battery ran down super fast yesterday and when charged, only get splash screen and slowly flashing blue light. I can get into Philz recovery but no matter what I try, no dice. Also can get into DL mode, but haven't been able to get anywhere. What the heck happened?
Well i bought another phone because of this problem of unknown baseband and 0 for everything in settings which didnt allow me to connect to sprint. Now when that happen it put me in safe mode . and i couldn't find a fix for months i ended up getting a lg g2 and let my note 2 collect dust. Well I'm using my note 2 and its up in running . my partition was messed up . if you have this issue which it sound like i can help. My phone was running fine then rebooted on its own and rebooted on safe mode with no signal
Sent from my SGH-M919 using XDA Premium 4 mobile app
hi,
so i just got my s6 edge for sprint shipped to me (it wasn't activated to any service when i got it). here is the order of events i took:
1) tried to activate my service, but there was a delay in porting the #
2) while waiting for them to port it, i rooted it, installed twrp and a rom (this was when it was on 5.0.2)
3) they called and said they were ready to port, but the new rom didn't have the activation software in it. so i stalled them and said i would call back. i then reverted back to stock using odin.
4) got the number ported and was fine using the phone at that point.
5) this is where the day turned bad...... i didn't realize that coincidentally today, a new firmware was released to 5.1.1 and the phone auto-updated to it while i wasn't looking
6) i went to go re-root it using the same 5.02 root and now my phone is stuck. it's sitting on the "Samsung Galaxy S6 Edge, Powered by Android" screen and in the top left in red it says "RECOVERY IS NOT SEANDROID ENFORCING"
7) i tried to restore it back to the stock using odin, but it errored in the download mode (i don't remember the error off hand)
i can get into download mode, and that's about it. i had to let the phone's battery die on it's own to turn it off (this phone gets super hot, btw)
so i guess what i need to know is how to restore back to factory default again, now that it thinks it's on 5.1.1. is there any hope?
I'm in the same boat as you, I think the only hope is to wait until the firmware is available to download and install it via Odin. Let me know if you've had any luck getting it up and running again. I had to switch back to my old phone for the time being.
bbacon said:
I'm in the same boat as you, I think the only hope is to wait until the firmware is available to download and install it via Odin. Let me know if you've had any luck getting it up and running again. I had to switch back to my old phone for the time being.
Click to expand...
Click to collapse
check this post, download the tar and flash it in odin. it worked for my phone!
http://forum.xda-developers.com/showpost.php?p=61650724&postcount=142
it got me into a recovery image that worked and i was able to factory reset in there. my phone is booting properly now. (after it reboots when done, it took a bit on the first title screen to do anything, just be patient)
Thanks man, that worked great. Although I found out in the process of trying to fix it the past few days, I must have flashed a non-compatible kernel because once it boots the touch screen is unresponsive. I guess I'll have to wait until the firmware download is available after all. Thanks again for the help though