(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.
Related
I just tried to load a new rom on to my phone. I used twrp to do a factory reset and now it wont turn on, at all. I wont even get to the splash screen. I've tried removing the battery and then turning on, no luck. I've also tried holding the keys to get into recovery mode, nothing works!!
Please tell me its not a brick!
which rom where you running
which rom are you trying to load
kingskater said:
I just tried to load a new rom on to my phone. I used twrp to do a factory reset and now it wont turn on, at all. I wont even get to the splash screen. I've tried removing the battery and then turning on, no luck. I've also tried holding the keys to get into recovery mode, nothing works!!
Please tell me its not a brick!
Click to expand...
Click to collapse
It really helps to know what ROM you were flashing, what method you used to flash, i/e ODIN flash then TWRP wipe, or TWRP zip install and wipe.
I would highly bet that you flashed an incompatible ROM, that was meant for another version of the S III, which would cause you to be in this current state. Which best case scenario you take it back to AT&T and tell them you were in the middle of using KIES to upgrade to the new OFFICIAL Jellybean, and your computer froze during the install, after which your phone never turned back on.
Second case scenario, you call up Samsung and get an RMA from them, wait 2-4 weeks and get your phone back, often times not having to pay the "fee" for repairing it.
Worst case scenario, you have a nice shiny new beer coaster. In which case you could mail to me and I could use it as such, as I am currently out of coasters.
Try using Odin to fix
1. Download Odin and stock ROM rooted
2. Put phone in Download mode (not recovery) by pressing and holding Vol Down + Home + Power
3. Open Odin on computer and load the ROM
4. Hit Start
Refer to the following thread for a more in-depth guide:
http://forum.xda-developers.com/showthread.php?t=1739426
I got it fixed. I had to pay some kid to JTAG repair it.
Hi XDA Forums,
I have a problem with my Note 2 for some reason.
Let me explain you what is wrong with my Note 2
I was sitting down and watching a movie, my phone was right next to me, The phone randomly turned off and after couple of second it had turned back on. It had showed the first every screen when you turn it on "Samsung Galaxy Note 2 N7100". Now from there it keeps on looping the same screen over and over again.
I had done some research before opening this thread, I saw that some people said I should try factory resetting it from the recovery mode, I then tried going on the recovery mode, it was not successful, it had showed me the same "Samsung Galaxy Note 2 N7100" screen and then repeated to boot loop it self again, I tried going on the recovery a couple of times but it didn't let me go on it.
Next I had then downloaded the 4.1.2 Official Firmware from SamMobile to flash it to stock again, I had then tried going on the Download Mode, It goes to the screen for Download Mode, but when I try pressing up to continue from the warning message it had then rebooted it itself and made it self stuck on the screen again.
Basically, my phone is stuck on boot loop, It does not let me access the recovery mode and it also does not let me access download mode.
ROM Using: Tigra_RomV3 4.3 Based ROM
Kernel Used: The Kernel which comes with the ROM or Stock, I didn't change the kernel myself.
If there is a internal problem does that mean I wont get help from the Warranty because the phone was rooted?
hello,
just try to use the jig, it should work...
use it so your phone will be in download mode, then flash your rom
Do you NANDROID backup? Maybe you may restore it by custom recovery.
Second, remove the battery first for a while and retry to access the RECOVERY and DOWNLOAD mode. If not, try the suggestion up there.
I've got a Galaxy Tab P5210 that's stuck in a constant boot loop. I flashed it with the correct stock firmware from SamMobile using Odin, but it fails to boot properly. It automatically boots to the stock recovery screen, but the problem is it will instantly reboot as soon as it reaches this screen. I see the dead android with the red triangle and exclamation point for just a second, and it instantly reboots. Is that normal? I don't think that's normal. From what I've been reading, this screen is supposed to stay there until you push the volume keys to bring up a menu, but it reboots so fast that I don't have a chance to even push anything.
I've tried flashing it with other recovery images. I tried using CWM, and it almost worked. With that, as soon as the tablet booted, I'd see the CWM splash screen, and it would instantly reboot. Similarly to how it's booting now but with stock recovery.
I'd like to point out that I've never messed with anything like this before. I work in a computer/small electronic repair shop and a customer brought it to me. She ended up getting into stock recovery and a friend of hers did some serious damage in there which prevented it from booting properly. Normally we don't mess with things like this but, with it being how it was, I figured there was no way I could make it even worse than it already is by working on it. I thought if I flashed the original stock firmware back to it, it would fix it, but that looks like a no-go since it's still booting the same way it was when she first brought it to me.
Is this thing completely broken or is there still hope for it?
No - it should be recoverable. However - any data will most likely be lost.
When you flash with Odin, make sure only F. Reset Time is checked. Use Odin 3.07. Make sure again that firmware is correct before you flash. After it flashes, power off and then on again
Latest KK firmware for the US version of the 5210 is P5210UEU0CNK1_P5210XAR0CNK1_HOME.TAR
Good luck. If you're trying to root, then there are threads in the 10.1 Dev section that should help
M,
this firmware was always my goto for device recovery/restoration https://www.androidfilehost.com/?fid=23060877490005046
posted by user chpettit , flash with odin 3.07
m
OKAstro said:
No - it should be recoverable. However - any data will most likely be lost.
When you flash with Odin, make sure only F. Reset Time is checked. Use Odin 3.07. Make sure again that firmware is correct before you flash. After it flashes, power off and then on again
Latest KK firmware for the US version of the 5210 is P5210UEU0CNK1_P5210XAR0CNK1_HOME.TAR
Good luck. If you're trying to root, then there are threads in the 10.1 Dev section that should help
Click to expand...
Click to collapse
Not interested in rooting, just wanna get the stock firmware back on. Maintaining data isn't a necessity, the customer just wants it back in working order. I tried using that firmware, but I had Auto-Reboot checked.
EDIT
Yeah, it's still doing the same thing. When I first boot it up post-firmware flash I see an Android with a loading bar underneath it, and then it reboots. When it boots again, I see the same Android and then it suddenly changes to the dead one with the red triangle. Maybe I'm just doing something wrong here with the button presses following the flash?
EDIT2
It looks to me like the stock recovery image is just broken, since the tablet just automatically reboots the instant it attempts to load it up. Flashing a new firmware replaces that though, so I don't know how or why it would even be corrupted. Odin reports no errors, so I don't know what's going on. And every guide I'm reading with fixing bootloops all say "go into stock recovery and clear the cache", but I can't even boot into stock recovery. It's like it's not even there. And I know it's not a power button issue causing it to shut down, I can power the device off fully with it, and it will stay off until I press it again. I'm banging my head against the desk here.
What if you flashed a TWRP recovery in Odin. Then if that's successful, boot into recovery and wipe/format everything except ext SD, Then try the ODIN flash again with filr your stock tar
I'm having the same problem and that didn't work for me. It shows the twrp splash screen and reboots. I'm looking for the .pit file it has to be the recovery partition right?
Sent from my LG-D851 using Tapatalk
NoteII Randomly stuck in a bootloop with no access to recovery
I looked for two days around the web for fixes to this, tried flashing everything from roms (if i understand it correctly it's like a phone OS), through custom recoveries (the things that show up after the up/home/power button combo) and even a kernel. I know that I honestly shouldn't have done that without the full knowledge of what I did, but at 3AM I didn't think much. I think i even tried using PIT, but it got stuck and didn't go through.
Okay, specifics:
One day I pick up my phone and notice the big white letters - " (...) note II" etc, standard bootloop. Kinda surprising since I didn't do anything to the phone, but It had some problems before like deleting like 4-5 apps randomly once, or an icon or two disappearing. I tried the obvious method of recovery mode and clearing caches and such, but it didn't work:
after the button combination it briefly showed the "teamwin" blue logo of my recovery i used to have for like 2 years, and then it goes black, and the white letters show up again. Only the download mode shows up. Odin detects the phone and when i flashed a stock rom and some recoveries on it, odin said they "passed", but no change ensued, the recovery still showed teamwin's, even after flashing clockwork recovery, or whatever it's called. I basically accomplished nothing, and I need to know what to do specifically to fix the phone, without bricking it even more. can you guys point me in the right direction, or maybe try to diagnose the problem? Thanks.
-no recovery
-recovery flashing doesn't change anything
-download mode works, odin detects the phone
I've got the impression that you're trying to make two steps in one. I suggest to flash firmware through Odin, reboot, setup and then make wipes and factory reset in stock recovery. Then flash the custom recovery through Odin and all should be fine again.
Reminder: Don't flash firmware beneath your current bootloader version.
I am having an issue getting my phone to turn on. I have been running the original Lollipop version, OB7 I believe, rooted via CF-Root, with TWRP recovery installed via Flashify but with the original kernel. I have done no other updates to the phone since then. I have been having some issues with some odd hardware behavior (not recognizing the HD card and the Sim card, not charging correctly, not appearing on the computer when I plug it in), so I decided I wanted to bring my phone back to the Sprint store. Before doing that, I decided to restore stock recovery and unroot the phone before bringing it in so I have no issues with it. So I used flashify to install the stock recovery. However, when I go into recovery mode I can get into recovery, but when I do, I have the "DM-verity verification failed" on the screen as well as recovery options. I read that may be due to still being rooted, so I went into SuperuserSU and unrooted the phone. I then rebooted. The phone when rebooting in the normal mode gets stuck on the Sprint Spark screen. I can get into recovery mode (still getting the DM verity message) and I can still get into download mode, and when I do, I can recognize the phone in Odin. The Kies/Smart Switch program does not recognize the phone. I went into recovery and tried doing a factory reset, and I still get stuck on the Sprint Spark screen. I have heard that after a factory reset you can be stuck on the Sprint Spark for a while, but it has been over 15 minutes. I assume I need some kind of stock ROM (OB7?) to install via Odin? Does that sound right? I'd appreciate suggestions, I am obviously concerned as I cannot get my phone started at the moment.
Yes, if OB7 is your bootloader, power down, boot into download mode and flash the OB7 stock tar, let it auto reboot and go through the setup wizard. Look for the tar in Sprint Note 4 general forum.
If you're not sure what your bootloader is, you could flash CF Auto root and see if it boots and verify the bootloader with Phone Info app.
https://play.google.com/store/apps/details?id=org.vndnguyen.phoneinfo
Not sure why you're taking the phone to Sprint but usually the factory reset and Odin flash will fix it unless it's hardware failure.
Sent from my SM-N910P using Tapatalk
Thanks for the verification. Downloading the Tar now. My phone was definitely on OB7.