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
Related
I am not new to the concept of rooting and loading a custom rom. This is the 3rd android phone that I have bothered with. However it is the first one I have had to use Odin to root or push files to.
I have used CarpeNoctem's writeup on how to root and utkanos' CWMR port writeup. Ofter verifying I had root, I decided I would try out Carpe's OsiMood. No problem right? Here is where I am wondering what if anything went wrong on the previous steps.
I made a back up ofter finally getting it to recovery mode, and when I tried flashing the new rom, it would not complete the process.
As it sits, when I choose recovery from CWM it reboots to the android with triangle screen(see attached video). What concerns me is the lack of fluidity into the recovery, the fact that it loads in only after the battery is removed and the phone is turned back on and lastly that I cannot flash a new rom.
It appears as though I need more posts to add my link for youtube.
Please add standard youtube weblink before this to watch the video.
/watch?v=qpQyQB1aozs
What would you recommend my first action be?
Thanks,
Steve
This also quite unfortunate for ROM manager, "somewhat", not working fully for the Glide (yet). I can't really go into 3e/CWM recovery with the app, but manually (volume down + power/lock button) has no problems. This also happens on my Captivate (SGH-I896/7), I need to restart the device for a second time to boot into recovery. As per your flashing issues, you might need to mount /system manually and then flash the ROM, when it fails, try and try again, always happens to me from stock rogers ROM. Also, if you have Titanium Backup, it now supports reboot device features (recovery and hard reboot)
Thanks for your insight. I tried volume down and power before but when I saw the samsung logo pop up I figured it wouldn't work.
I will try flashing again and report back. Thanks again.
-Steve
Tried flashing again, worked great. If only the glide had more support. Lol.
Currently running OsiMood.
Sent from my SAMSUNG-SGH-I927R using Tapatalk
gabby131 said:
This also quite unfortunate for ROM manager, "somewhat", not working fully for the Glide (yet). I can't really go into 3e/CWM recovery with the app, but manually (volume down + power/lock button) has no problems. This also happens on my Captivate (SGH-I896/7), I need to restart the device for a second time to boot into recovery. As per your flashing issues, you might need to mount /system manually and then flash the ROM, when it fails, try and try again, always happens to me from stock rogers ROM. Also, if you have Titanium Backup, it now supports reboot device features (recovery and hard reboot)
Click to expand...
Click to collapse
My glide does not boot. I can get into Download Mode. I can NOT get into de recovery mode. I think my NAND is corrupted.
How can I mount the /system partition? Because I flashed too many roms with ODIN, but nothing, still not booting, I get stuck in the samsung logo.
Use Odin to reflash recovery,you backups should still be there unless like you say maybe they got corrupted as well,but its worth a shot.
Here is a link to the latest,with instructions:
http://forum.xda-developers.com/showthread.php?p=34479219#post34479219
Kodiack99 said:
Use Odin to reflash recovery,you backups should still be there unless like you say maybe they got corrupted as well,but its worth a shot.
Here is a link to the latest,with instructions:
http://forum.xda-developers.com/showthread.php?p=34479219#post34479219
Click to expand...
Click to collapse
I've already flashed the stock recovery, the CWM, a lot of kernels, even I tried to flash the kernel and bootloader of the Galaxy S II, but nothing.
I'm starting to think that maybe is a hardware problem. Hope not, but I'm not moving foward.
If you havent already,pull out the sim and sd card.
Reboot your pc and download a fresh up to date Odin.
So when you flash it says it successful and then just doesnt boot?
I had a boot loop once ,had me stumped and it turned out to be my sd card was poached and caused the loop.
Kodiack99 said:
If you havent already,pull out the sim and sd card.
Reboot your pc and download a fresh up to date Odin.
So when you flash it says it successful and then just doesnt boot?
Click to expand...
Click to collapse
Exactly... It goes all over the process bar, says succesfull, the phone turns off, and nothing. The phone not even restart itself, I have to remove the battery, put it back again, and then it turns on, but just to show me the samsung logo.
I've used the ODIN version 1.85 and the new one 3.04. But nothing. This is so frustating.
---------- Post added at 04:23 AM ---------- Previous post was at 04:04 AM ----------
I've opened a thread with all the symptoms of my bricked phone:
http://forum.xda-developers.com/showthread.php?t=2035742
Please, tell me there is a solution...
There are one alternative to boot
1. Shut down and then restart phone in recovery mode. For the Samsung Captivate Glide, this required pressing the power, volume down and home keys all at the same time.
2. The initial screen which appears gives you a choice of loading a replacement OS (volume up) or entering recovery mode (volume down). Note you have to hold the volume down key for several seconds before the recovery mode menu appears.
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.
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.
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?
I did a search and maybe not correctly but I did not find my particular problem.
So I have stock root66 rom flashed with odin 3.11 on my phone goes into boot loop.
I flashed twrp 3.1.1-0 with odin and I can go into recovery but as soon as I select any rom (OCT-N-WEEKLY-20170811-1427-d2tmo) it starts to do something and just reboots the phone and back into the boot loop. I reboots to fast for me to even figure out what it says on the phone.
Has anyone else experienced this? Battery is charged to 80%+
edit: tried CWM same symptoms reboots right away. Only thing I can flash with is odin otherwise with any recovery reboots right away. I was able to flash a modem with twrp and that works but no roms work.
update 2: I finally was able to get root66 installed. Gets to the set up part. Once I finish the setup the phone turned off on its own. It never turns on on its own so leads me to believe the power button isnot stuck but why does it turn off on its own? I turned back on and goes into bootloop.
The power button may be stuck in the "pressed" position.
Have you tried TWRP 2.87? You're sure you are flashing the correct TWRP version for the phone?
audit13 said:
The power button may be stuck in the "pressed" position.
Have you tried TWRP 2.87? You're sure you are flashing the correct TWRP version for the phone?
Click to expand...
Click to collapse
Thanks for the reply. I have tried 6.0.1.2_CWM_Touch-recovery-image & twrp-3.0.2-0-d2tmo.img but not 2.87.
However, as I stated above I was able to flash a modem but just not flash any roms which is weird.
If the power button pressed and the phone reboots when i pull the battery and put back in wouldn't the phone turn back on? I'm just finding it odd the phone keeps rebooting but when I pull the battery and put back in it doesnt turn on automatically.
update: So 2.8.6 twrp worked which is odd installing as we speak phone has not rebooted yet so lets see how it does once rom is flashed. I did odin root66 and after that installed it kept rebooting so fingers crossed this works. Using OCT-N-WEEKLY-20170811-1427-d2tmo hopefully this works
so after the flash seems to just back to the bootloop. I'm still not convinced my power button is stuck since it doesnt auto turn on and during the whole process of flashing it didnt reboot on its own only after the flash. Any ideas?
Literally gets to the samsung galaxy siii logo and reboots right away.
Try flashing the latest stock ROM, not a rooted stock ROM.
audit13 said:
Try flashing the latest stock ROM, not a rooted stock ROM.
Click to expand...
Click to collapse
same bootloop. Gets to the tmobile animation and then reboots.
It's possible that the memory chip is damaged. You could take it to a repair shop and have it flashed via jtag.