This is my wife's Note 10.1 wifi tablet (GT-N8013). It had been running a CyanogenMod ROM for quite a while - 13.x I think. Last week she brought it to me saying it does not start up anymore. After power up it goes to the CyanogenMod startup logo and stays there indefinitely. It has (or had I can't tell now...) TWRP 2.8.6 on it but booting into recovery mode results in the TWRP splash screen showing for a few seconds and then it resets/reboots and hangs and boots to OS and hangs again. Tried putting a newer TWRP on it (3.0.2.0) but booting into recovery is no different. It does start into download mode and seems to function correctly there but I cannot get anything to boot on it. I have a quite old download of jellybean which is official from Samsung (I think) from 2013 but that is not working via ODIN either. Firmware seems to not be available via sammobile anymore for this one. I am about ready to give up on it since it is more than 5 years old. Any thoughts on resurrecting it?
Read identical fail to boot multiple posts .
Last firmware was Sept 2015 4.1.2
listed on samsung-updates and sammobile and updato.com
Related
Ok so I have tried on another thread that kind of went dry mainly cause I was MIA....but now I am back and have done some more reading up and think it is safe to say rooting and trying customer ROM's is not for me...lol I pretty much messed up a new Galaxy Tab 2 7' brand new only after a few weeks trying to root it. I had another thread link below:
http://forum.xda-developers.com/showthread.php?t=1834368&page=2
But I did not get anything to work right. At this point I am really just looking to get the tablet working. I don't really care what firmware rooted or unrooted...i just want to be able to use it....do some more research and and maybe join the rooting community again when I get a Galaxy S3.
I'd appreciate any help. I am pretty stuck right now!
Go into Download mode "power" plus "down volume", then up volume. Use ODIN to load this:
http://forum.xda-developers.com/showthread.php?t=1645295
ODIN
http://forum.xda-developers.com/attachment.php?attachmentid=581913...
You will need driver from Samsung Keis install for P3113
http://www.samsung.com/us/support/owners/product/GT-P3113TSYXAR
FYI - I needed to load CMOC10-Kernel to get my tab to stop boot looping when I flashed JB AOKP
bark777 said:
Go into Download mode "power" plus "down volume", then up volume. Use ODIN to load this:
http://forum.xda-developers.com/showthread.php?t=1645295
ODIN
http://forum.xda-developers.com/attachment.php?attachmentid=581913...
You will need driver from Samsung Keis install for P3113
http://www.samsung.com/us/support/owners/product/GT-P3113TSYXAR
FYI - I needed to load CMOC10-Kernel to get my tab to stop boot looping when I flashed JB AOKP
Click to expand...
Click to collapse
Worked like a charm....you made it simple! Thanks!
Continous boot loop on tab 2 p3113
My problems are kind of different from all the others I have read. Yes it is similar that it boot loops. But mine freezes at different areas in boot mode. This is driving me crazy and I am spending way too much time and effort trying to fix it. Hopefully you can help.
I don't really know for sure if the android os was 4.1.1 or 4.1.2 or some other rom but it did state in download mode that it was original and not custom rom.
I received this tab from ebay and it is new never used, but somehow whoever had it probably tried to flash it and now I received it with a continuous loop. They stated that it stuck in SAMSUNG logo. I found it true but it also stuck other places as well. I did do a reset first before I attempted to flash it.
I did the Odin flashing.I found the 4.2.2 xar file HOME_XAR_P3113UEUCMK3_1978026_REV04_user_low_ship.tar.md5 and did according to instructions. But that didn't work. It did boot into android but it didn't stay there very long and rebooted itself. I couldn't stay more than 20-30 seconds and it would reboot itself or freeze at various places in android. I also hard reset it. Still same thing. It would also freeze on the first samsung logo tab 2 screen and also at the blue circle with samsung logo. It was different every time. I would have to hold down the on button until it rebooted. It also stalls or freezes during Android upgrading... Optimizing app at various number stages sometimes it goes thru that and then to the next phase of installing apps then it freezes again. I cannot get it to work if I try to upgrade via wireless upgrade to samsung. it will freeze even before it downloads the upgrade file.
I then flashed back to the original xar file P3113UECLK7_P3113XACCLK7_XAC which is 4.1.1 That worked a little better, but it freezes and also the sound chatters when it freezes on bootup you know, when the samsung sound comes on then the blue circle.
Finally I tried to recover or flash from the recovery mode using the upgrade from a sdcard. using the original 4.1.1 xar file. It hewlped a little but still doing the continuous boot loop at different stages but it gets to the Android is upgrading... more often. It freezes always now.
So I don't know what else to do. You mentioned a CMOC10-Kernel to load, how does one go about doing that and what are the steps.
Thanks in return if you can suggest things.
Wayne
Hello
About three days ago I went to turn on my N8000 and it got stuck in the "Samsung GALAXY Note 10.1" logo. At first I thought it was updating something or just taking longer to start, but after one day I realized that it wasn't going to start at all. So I tried to do a factory reboot but found out that the tablet won't boot into the bootloader (Power + vol up), it just kept going into the galaxy logo. It can, however, boot into download mode, so I started checking on the page what could solve my problem. I tried installing the CWM recovery using ODIN 1.85, the flash was successfull but the device will still not boot into recovery mode. After that I read that installing a stock firmware could solve the issue, so I downloaded the Kit Kat version and flashed it, rebooted but nothing. I found some topic that a guy had to use a .pit file along the kit kat firmware, did that too and nothing.
So here I am stuck with my tablet bricked and without knowing what else to do, so I was hoping to get some help from you guys.
Thanks in advice!
Greetings everyone,
I decided to post my problem with my phone after searching the entire internet for similar problem but with no luck. Anyway I used to play around with my Samsung j7 pro for 2 years, I managed to flash twrp and thus many other custom roms, until last week when I recklessly flashed a sboot.img.tar file through Odin in order to fix cellular network in a rom I flashed earlier, this alone bricked my phone refusing to get past the Samsung logo, so like I do always, I tried to restore my phone by flashing the stock firmware (9.0) which I always keep on my PC, but surprise, the phone refuses to go through the process and gives me this error:
sw rev check fail bootloader device -1 binary 6
(same with 8.0 and 7.0 firmware)
I searched the internet for same error but with no luck, because I understand it's a mismatch between device bootloader current version and the firmware bootloader's, that they should be the same or higher, meaning you can't downgrade, I get that! but I never seen device with negative figure (-1) what that's supposed to mean? my device bootloader used to be on 6, how did it managed to jump to minus one ?
then I tried to flash TWRP to see if I could flash a rom and get around it, so I did, but when booting into recovery the screen goes black, I thought first the phone turned off, but not really, because TWRP seems to work with screen completely black, I knew that because I accidentally touch the screen and I sense vibration, I managed to reboot the phone via twrp just by guessing the buttons location (screen always black) in order to prove that TWRP is working with screen off. I tried to flash multiple TWRP versions but the same problem, no screen just touch, by the way there is nothing wrong with display hardware because it shows Samsung logo at start and also can boot into download mode just fine.
I hope someone could help me overcome this big of an issue, because I tried everything.
Hi All,
I'm enjoying my first rooted phone for some months now. It's a s8+ with android 12.
But today out of nowhere my phone crashed and now i'm stuck on the teamwin logo page (3.5.2_9-0)
What i've tried:
Using odin again to install the exact same version from my downloads folder again. But this doesn't do a thing
Install a new twrp version from it's website. But then the samsung s8+ logo comes up, and the phone seems to restart immediately and ends in a loop.
I have no clue what to do and trying to search what i have to do but can't find anything but what i've done already.
This is my first rooted phone, so a bit of a noob.
edit: i've tried other versions, but it seems that only 3.5.2_9-0 gets through the samsung logo, but not further then the teamwin logo)n
And in can still enter download mode.
The logo seems to go away for a second every minute
At the moment i followed this tutorial (in januari)
My phone was 4 years old, i guess i'll buy a new one. Perhaps someone can tell me if i can reach my files. Most is backupped correctly but my signal (messenger) backup seems to be backuped to my phone itself instead of the SD card
I've rooted my phone a couple days ago, successfully.
I decided to install TWRP on it today, and after Odin succeeded, I'm now stuck in a bootloop with only the first Samsug logo.
Whatever I do, fresh restart, safe mode, download mode, etc, it always shows the first logo and powers off right after.
any help? I really need it!
Samsung A22 5G
Model: SM-A226B
Region: VDF
Android 11 + One UI 3.1
Rooted with Magisk 24.3
Edit: FIXED!
Add: the phone randomly boots on its own, doing the exact same thing
It does not show the power off charging screen either.
I've noticed, whenever the phone is connected to Win10, Windows will very regularly (2 seconds) note that it's connected, with 1 second later disconnecting
FIX: I managed to get the phone into download mode, as I noticed the usb connected for a little time. from here, I tried to boot stock firmware on it, but kept failing at super.img.
as I kept trying, I found out that only the Official AP kept hanging and failing at super.img, but my magisk patched version... that worked! I also uploaded CSC, so I now have a blank new rooted phone
How to get out of annoying Samsung bootloop
lebigmac said:
How to get out of annoying Samsung bootloop
Click to expand...
Click to collapse
I got into download mode (considering bootloader is unlocked) and put new Android files on my phone (Odin3 program, AP file)