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.
Related
(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.
I had to resolve to making a thread because google isn't helping... And I've looked through everything.
I was running Hurricane rom v6 and I wanted to upgrade to the latest version, so I went ahead and tried to install the mj5 bootloader. I followed all the instrcutions but something didn't seem right... Right after the flashing process in Odin finished, my phone rebooted into the recovery (CWM PhilzTouch) instead of rebooting to the OS. I went to check if the new bootloader was installed and I don't think it was, because it didn't say KNOX WARRANTY VOID as it was supposed to, according to the instructions.
So I tried it again a few times and eventually what happened is that I got the "go into Kies and do the emergency recovery etc" which I did, a few times, unsuccessfully. It failed every time. So I uninstalled Kies, went back to Odin, tried to a few other ports, and finally it finished the flashing process successfully.
Now I can get into both recovery and download mode, but when I try to reboot the phone, the Galaxy Note 2 logo shows up, after that the screen goes black and then the phone vibrates every two seconds until i remove the battery.
I tried going back to recovery and then factory reset the phone but still the same thing happens. Now I'm downloading the stock firmware from samsung to try to flash that since I can still get to download mode but it's going to take an hour and until then I wanted to ask if the vibrating behavior was normal or it indicated a more serious problem. In all fairness I haven't tried installing the new version of the Hurricane rom after I tried flashing the new bootloader, but I figured that as long as I don't know that I have the new bootloader for sure I'd rather skip that step.
Any ideas?
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
Hi folks,
I'd appreciate some assistance in identifying the problem with my sm-p605. The color balance (RGB) on it went all bonkers. Red was alright, but the green and blue were almost completely faded. When I booted into download mode the colors were right, so I figured it's gotta be a software problem. I tried re-installing the firmware, first through Kies, but it got disconnected in the process, so I found stock firmware on sammobile and flashed it with Odin with a PASS. After that, the device would get stuck in a boot loop with "recovery booting....." written in the top left corner whether I tried to boot it normally or in recovery mode. But the download mode still worked so I tried flashing a custom recovery. I don't know if a device needs to be priorly rooted for that, but I flashed CF Auto Root and TWRP both with a PASS. After that, the device still wouldn't boot into recovery mode. It would say "recovery is not seandroid enforced". I tried several supposedly compatible versions of the recovery with the same result. But now it does boot normally into the OS except none of the things I flashed stuck. It's still the same non altered system it was before I did anything with it, even though I re-installed stock firmware twice now, second time even with Kies. So what's going on?
I took a screenshot of the app drawer after all this, and the colors are alright when viewed on a computer screen, so it might be a hardware issue after all, although I don't have a definite conclusion since capturing and displaying aren't the same part of the OS. There are other issues with it being non responsive when I'm trying to wake it up. I still want a fresh ROM so I can know for sure and I'm not able to install one, be it custom or stock. Any ideas?
I'll try to be clearer. Current ROM I have is stock 4.4.2, but it's barely usable, so I wan't a fresh one. I cannot get into recovery mode. If I flash stock firmware, I cannot boot into either the OS or recovery. If I flash custom recovery on top of that I still can't boot into it, but I can boot into the OS, which reverts itself like I never flashed fresh stock. So I'm stuck with what seems to be a corrupt OS with no way of installing a new one. Is there something I can try?
If you can flash a custom recovery. Boot into it and try factory reset. Either that or try a custom ROM if any are available (font have tablet)
Sent from my LG-D850 using XDA Free mobile app
Factory reset was the first thing I tried, I wish it had been that simple. I can flash a custom recovery, but I can't boot into it. The only thing it acomplishes is breaking the bootloop from stock recovery, so I can boot back into the OS, which stays the same no matter if I flashed new stock (it boots up already user configured). To install custom ROM I need custom recovery, unless there are some methods of installing that don't require flashing from storage.
Hello everyone,
My phone (S4 mini GT-I9195) decided all of a sudden to stop working. I couldn't boot it, charge it, nothing but a black screen. After some research on the world wide web, I came to the conclusion that it might be "bricked", as the cool kids call it. I came upon a guide on this website that seemed promising: https://forum.xda-developers.com/showthread.php?t=2600869
I followed the instructions, found a debrick.img corresponding to my GT-I9195, put it on a sd card and managed to boot the phone.
Next was entering Download mode and flash with a stock firmware via Odin (v3.09). I used a 4.4.2 firmware I found on Sammobile (I9195XXUCNK4_I9195QXZCOA1_XEF) corresponding to my region and phone.
Everything went fine with Odin, I waited until it said "PASS!" and rebooted the phone.
The next step was to enter Recovery mode, and that's where I have a problem. I use the combination "Volume up + Home + Power" to enter it, it vibrates once, shows me the Samsung logo (+ model) with "Recovery booting...." written in blue on the top left corner, I release all the buttons, and after a few seconds, it goes to a black screen, it vibrates twice and reboot on the Samsung logo, but without the "Recovery booting..." message on top left corner. After that, it enters a bootloop that only ends when I remove the battery.
So, I can never enter the recovery mode (I tried multiple times, with different methods, such as releasing only the power button, but to no avail) and cannot complete the debrick guide. I tried different stock firmwares but always with the same result.
Did I do something wrong? What can I do differently to enter recovery mode? Should I prepare the funeral for my phone?
Thank you in advance for your answers.
You should try flashing cwm with odin, then formating your system partition, if you can externally put a rom on your memory card then do so, after that install that rom on your phone, if that doesn't work then try flashing your stock firmware after you had done everything...Of course I don't know if any of this will work because I haven't run into a issue like this before, though one time my recovery was blocked and flashing cwm on it fixed it, instead of flashing stock firmware I went for cyanogenmod (now lineage os) so it might work for you, who knows.
Well, first of all, thank you for your leads.
Secondly, as you suggested, I tried flashing with Odin, with CMW (6.0.4.6 and 6.0.5.1). It went smoothly in Download mode, I get the green PASS!, but just as before, when it reboots in Recovery mode, it doesn't go beyond the blue "Recovery booting...." step, instead, the dreaded bootloop begins.
I also tried flashing with TWRP (3.0.2.0), but unfortunately no change...
And without any custom recovery, I cannot try the lineage os.
I'm begining to feel the end ^^
paupiette said:
Well, first of all, thank you for your leads.
Secondly, as you suggested, I tried flashing with Odin, with CMW (6.0.4.6 and 6.0.5.1). It went smoothly in Download mode, I get the green PASS!, but just as before, when it reboots in Recovery mode, it doesn't go beyond the blue "Recovery booting...." step, instead, the dreaded bootloop begins.
I also tried flashing with TWRP (3.0.2.0), but unfortunately no change...
And without any custom recovery, I cannot try the lineage os.
I'm begining to feel the end ^^
Click to expand...
Click to collapse
I have TWRP on my mini. When I first flashed TWRP (3.0.2.1) via Odin, I had to manually boot into recovery by holding VolUp+Home+Power as soon as I see PASS!, BEFORE the phone automatically reboots.
I have to try this a couple times to get TWRP to stick. From what I read, if you let the phone boot automatically after flashing from Odin, it will automatically overwrite the new flash with stock Samsung recover (which is bad in your case.) So you have to interrupt this by a manual reboot before the phone does its thing. If you are successful, you should boot directly into TWRP on the manual reboot. From then on TWRP will overwrite the stock recovery and you will be good to go.
I find the timing of this manual reboot a bit tricky on the phone. Do it too soon, and the TWRP was not flashed, a second too late, and the phone boots to stock. I had to try that a few times to get it right. Basically, be ready with the buttons and press it the instant you see PASS! So maybe you can try flashing TWRP again before giving up.
I have encountered the same problems today. After waking up, my phone (S4 Mini) told me an update (17 MB) was available. Happy about still getting updates, I started the process and the telephone rebooted. When returning ten minutes later it was all dark and wouldn't respond to any button combination. After working through a lot of threads and forums, trying to fix the problem, I managed to get a debrick image for the phone as well as the right firmware from Sammobile (which is astonishingly the same one that paupiette uses, though I'm from Germany, but the phone seems to have a French regional code).
At first I wasn't able to get to the Download Mode, instead my phone always told me this while denying my attempts to flash it:
BOOTE RECOVERY MODE
CHECK BOOT PARTITIONS..
COPY FROM T-FLASH..
BOOT RECOVERY..
WRITE 139008 sectors..
FLASH WRITE FAILURE
ddi: mmc_read failed
ODIN MODE
PRODUCT NAME: GT-I9195
CURRENT BINARY: Samsung Official
SYSTEM STATUS: Custom
KNOX KERNEL LOCK: 0x0
KNOX WARRANTY VOID: 0x0
CSB-CONFIG-LSB: 0x30
BOOTLOADER RPSWREV: 2
WRITE PROTECTION: Enable
Nothing seemed to work and some other topics on different forums blamed the internal flash chip (eMMC) to be the cause for all the trouble. I gave up on my phone, loosening the skrews on the back to get a look on the board. Before ripping apart the last bits, I tried to start the Download Mode one more time, so I put in the battery and hold the three buttons. Et voilà - the phone came up with that white booting screen. It was looping this process over and over as paupiette had allready described. I managed to start the Download Mode and flash with Odin3 (v3.12). A green "PASS!" told be, it worked until it began to enter the loop of rebooting again unable to enter the Recovery Menu.
So close but yet so far away from what I want.
Any new ideas or suggestions?