Galaxy Note 10.1 SM-P600 Reboot Loop - Galaxy Note 10.1 (2014 Edition) Q&A, Help & Troubl

Hi All,
Having some issues with my Galaxy Note 10.1 which I've had for quite a while now. It's rooted but with Android 5.0 stock rom and a custom kernel.
Just now (like 20mins ago) I tried to enable Adblock plus app, the app said it can't automatically change the settings - even though SuperSU was installed and had no issues with it previously. So like all things thought I'd give it a reboot that ought to clear it out. That didn't work, so tried clearing cache (Dalvik/ART/Cache), Still no joy.
I'm a s/w engineer, but not and android/bootloader expert, so I've tried to grab the dmesg and boot logs which I've attached, I've got some stuff on the internal SD (app data) which I'd like to keep, hence I'm not going for the full wipe.
Please take a look at the logs and see if you can determine how to fix this issue, my initial thoughts were there are some issues with the flash storage (bad sectors/partition table?), if I could grab the image and dd the image again I'd be OK - but I don't know much about about android boot loader/kernel etc so can't say.

Ok it has been fixed by wiping data - but I've lost my data and installed apps!
Is there anyway to find out which file/app is causing the boot loop so I can restore data, delete the offending file?

Well, I shall give a bump to this topic, with a little more info. Though probably not really useful.
First I had stock 5.1.1 deodex pre root etc ROM that, after I tried to insert a nano sim card (mine is a 601 3G model) that got stuck, it entered on a bootloop, I had to open it, take the sim card out, and it was still on a boot loop. Tried to install another image, still bootloop, tried to reinstall the original one I had, still bootloop, wiped data, worked fine.
Then almost 2 weeks later, everything worked fine, went to watch a video, the sound was mute, tried to turn it on but everything looked fine, decided to restart because it would probably fix the problem. Got a bootloop. Wiped the data, everything was fine again.
Now, a little more than 2 weeks later, seems like the wifi is not working, thought all my other devices are, guess it's the same problem, decided to restart it, and bootloop again. I'm currently trying to update my TWRP, and gonna try a different ROM, and wait to see if something like that happens, until then, I wonder what could be happening... I remembered an Asus Device that I had that had different firmware versions for 4.4 and 4.1, so if I tried to flash a 4.4 on a 4.1 firmware it wouldn't work, and for downgrade, the same problem happened, and wondered if Samsung has some difference between versions 4 and 5.

ssj4maiko Let me know if you find a more stable rom - I went back to pretty much stock, but with root as I wanted to use all the Samsung apps, but this constant random bootloops are annoying!

Related

weirdest bug ever? ET resets to how it was on certain day(like movie groundhog day)

Ok so i have one of the weirdest bugs ever.
Background:
I was running stock rooted rom w/out cwm for about a week. (i had rooted using cwm then installed superuser and then flashed a stock kernel over that so i was rooted, but stock.)
On October 4th i realized that any playlist i made in the music app were dissapearing after a reboot. While troubleshooting that, i realized that ANY changes i made to the phone (Installing apps, downloading files, text message and phone logs) would be erased after a reboot. Furthermore, any files i delete form internal sd reappear after a reboot.
Every time i reboot my phone it goes to the exact configuration it was on October 3rd. The phone still makes calls, uses web, texts, has the apps that were installed prior to oct 3rd etc... just it resets to that every time i reboot.
Things ive tried to fix it:
I have tried using Odin to go to flash a stock kernel, cwm kernel, and countless other kernels. The Odin flash goes through like normal, and it says success and the phone reboots; however, in about phone the kernel is the same and the config of the phone is still Oct 3rd. So that means that even though the odin says it flashed successfully, there is nothing actually being flashed.
Since i am stock i have also tried doing a factory reset and wiping cache through the stock android recovery, again these act like they have done the restore, but when the phone boots it is still in oct 3rd configuration.
I have just ordered a usb jig today, should have it by friday and i will update to see how that works.
I have posted this thread for informational purposes. I dont think anyone else has this problem, or what has caused this problem. It might very well be some user error on my part. Just posting this in case someone else encounters this in the future.
If you have any ideas/suggestion on how to fix this please let me know.
I know that i can just take to sprint and get exchanged but i first want to try to see if i can fix on my own, and since the phone still functions to make calls, texts and everything else its not a super major problem, except that any new stuff i add to my phone disappears.

[Q] Updated to 4.3, now GApps continuously force closes

I went through from 4.1.1 to 4.1.2, no problems, phone ran fine after update. Then went to 4.3, same thing. The phone was running fine so I booted back into recovery and removed Knox as well as manually rerooted by flashing SuperSU. Rebooted after that and still no problems, phone was running great. I then make a backup so I have a restore point of stock 4.3, rooted, and without Knox. I then go on and try to flash Dandroid and get a status 7 error and the phone was acting up after I rebooted.
At this point I go back to my backup and simply restore it and reboot again. The phone boots up, so that's a good thing. The problem is the GApps will not run and it continuously has a pop-up notification. The phone is rendered unusable like this. I got lucky once and was able to try and launch ROM Manager to see if fixing permissions would work, but it also closed. I tried flashing a 4.3 GApps package with no success and even tried reflashing the 4.3 update but got a status 6 error.
I'm at a loss here, does anyone have any ideas on this?
Not sure if this will help much, but even when plugged in via USB my computer will not recognize the device. The S3 states that it is connected and it does show up in Device Manager, it just won't show up as any kind of readable memory.
Trying to ADB sideload a rooted stock 4.3 ROM now. Any advice at all would be a help.
EDIT: I took a video (https://www.youtube.com/watch?v=tJ-eaQ_9mVI) of the problem so everyone can see what I'm talking about and I also found a fix.
I'm not sure what was causing it, but after a solid day of researching it online the closest thing I got was resetting app preferences and also trying to clear any data of Google apps. This seemed to sometimes slow the popups down for me or create a longer gap before they just came right back in full force. So, going off that small success I had managed to navigate my way over to Settings -> Accounts -> Backup and reset -> Factory data reset and ran that. The first boot after that took a very long time, I'd say a solid twenty minutes but it did work. No more error and everything has been going smooth for me since. A restore of apps with Titanium Backup also did not bring the problem back up again, so the device seems to be good as new again.
I apologize if any of these is out of line, I just thought I would follow up with a solution in case anyone else has this problem and can't seem to fix it. Maybe this will help them.

[Q] Can't turn wifi on. Tried with 5.1 and 4.4.4

I should mention that this phone is not mine and it was brought to me to fix. It could not get past the samsung bootup animation screen.
So I installed TWRP 2.8.6.0 and wiped everything. Then the first rom I flashed was [ROM][5.1.1][AOSPA] ParanoidAndroid 5.1 (5/21/2015) Then flashed gapps 5-22-15 from euroskank/banks. I wiped dalvik & cache (Is this necessary?) and rebooted.
The intro screen did not let me skip the wifi connecting part (I thought it was a bug in that version) and it told me to turn on wi-fi to connect.
So I tried the same thing with the version before that and it let me skip. After that I managed to turn it on once? But it the phone crashed and soft rebooted.
I tried other 5.1 roms and the wifi doesn't work still. It doesn't let me turn it on. Same with 4.4.4 with cm11. Also, the Wi-Fi MAC address says unavailable. Don't think that's supposed to happen?
Does anyone have a fix?
Edit: I took out the SIM card to see if that did anything. Then all of a sudden the grayed out On button turned blue and wifi networks appeared... But I couldn't do anything else since it made me restart. It stopped working after a reboot :/ Tried it several more times and couldn't get it to do the same thing..
stevenx37 said:
I should mention that this phone is not mine and it was brought to me to fix. It could not get past the samsung bootup animation screen.
So I installed TWRP 2.8.6.0 and wiped everything. Then the first rom I flashed was [ROM][5.1.1][AOSPA] ParanoidAndroid 5.1 (5/21/2015) Then flashed gapps 5-22-15 from euroskank/banks. I wiped dalvik & cache (Is this necessary?) and rebooted.
The intro screen did not let me skip the wifi connecting part (I thought it was a bug in that version) and it told me to turn on wi-fi to connect.
So I tried the same thing with the version before that and it let me skip. After that I managed to turn it on once? But it the phone crashed and soft rebooted.
I tried other 5.1 roms and the wifi doesn't work still. It doesn't let me turn it on. Same with 4.4.4 with cm11. Also, the Wi-Fi MAC address says unavailable. Don't think that's supposed to happen?
Does anyone have a fix?
Edit: I took out the SIM card to see if that did anything. Then all of a sudden the grayed out On button turned blue and wifi networks appeared... But I couldn't do anything else since it made me restart. It stopped working after a reboot :/ Tried it several more times and couldn't get it to do the same thing..
Click to expand...
Click to collapse
Hope you had read the posts, it should had said the Rom is not "stable"
If your friend are going use their phone for daily driver, then I recommend you not have the 5.1 Roms for now because it's not really suitable for that right now.....
I'm not sure the CM11 you have flashed is unoffical or is offical. Offical onces are still work in progress and have most of the things broke (I think)
Here is a Kitkat Rom for SGH-T989
If your friend really wanted to have a Lollipop running on his/her phone, then I will recommend this one. Make sure you read the instruction CAREFULLY if you do wanted to install this one since it's a bit complicated with it's "virtual partition"
Or, if you wanted it to be just stock. Odin it back to normal, here is a instruction (with video too).
This is all the possible way to fix your friend's phone that I can think of, if you have encounter any error or have anymore question, feel free to reply :fingers-crossed::good::highfive:
P.S: yes, wiping dalvik & cache is a way to prevent any error caused by another old Rom if you decided to flash a new one. It's a good way to prevent error during Rom flash process
Thanks! I'll try the 4.4.4 rom you sent me. I'll post an update when I get to it.
Uh and about the 5.1 you linked. For the virtual repartition part in his post, I couldn't open the phone's internal storage on the computer after formatting it to ext4. So I'm confused about that step.
stevenx37 said:
Thanks! I'll try the 4.4.4 rom you sent me. I'll post an update when I get to it.
Uh and about the 5.1 you linked. For the virtual repartition part in his post, I couldn't open the phone's internal storage on the computer after formatting it to ext4. So I'm confused about that step.
Click to expand...
Click to collapse
For the virtual partition, it's best for you to have it on the External SD card. Since TWRP transporting file to Internal Storage after that seems bugged (not working)

Note 2 DN3 Problem

Hello,
I had on my Note 2 t0ltecan Dn3V5 and it started to restart ever so often and my youtube app dissapeared and woudnt work. So I tried to wipe the data and it didnt work, from many TWRP versions and Philz recovery. Then i used Odin to install a stock rom, which then finally everything worked and I then tried to restore my Dn3.
Everything worked except my Action Memo which stopped working so I did the procedure again. Samething, so I tried installing Dn3V5 rom instead of restore. It didnt work because it kept saying bad zip, I tried TWRP 2.8+, 2.7.1, 2.6.3, 2.6.1, 2.5 and Philz. Only 2.5 worked but it woudnt boot after the graphic logo. Then i tried again and the same thing. So i restored again and this time it either doesnt boot after graphic logo or I get IMS Framework problem.
What should I do, restore Stock or DN4?? What could my problem be?
UPDATE:
I used odin again to install stock kernel again, this si the farthest I have got with it booting and not restarting. It is still doing that, sometimes more than others, but I have disabled 5 apps, one google play services and the other google chrome. So far so good, nothing has happened but I will have to experiment more.
I have been formating it many times and closing and opening it by taking out battery, will that affect my phone?
UPDATE 2:
I found the problem, I used my bros Note 2 battery and everything ran fine. My original battery died so I had bought a second hand battery. The whole time (for 2 months) it was causing me problems but I did not realize. After ripping the sticker off the battery I figured out it says 2000mAh on the inside XD.

T800: Can't complete boot when using 7.x.x roms

I had the latest 6.0.1 samsung rom (CPK2) which was giving me problems with freezing. So I am trying to upgrade to an 7.x.x rom, either RR, AIPC, or Lineage. But none of these roms allow the T800 boot to get beyond the initial splash logo screen. I am using latest TWRP, 3.1.1 to wipe and install rom. I am not getting any install errors. Boot loader is confirmed as CPK2.
FYI, I am able to get back to the samsung rom by reflashing it with Odin.
Update 1: In the final attempt of upgrading I installed the official 6.0.1 fw which boots fine unlike the aforementioned alternatives (very strange). However, lock ups and now screen blanking more frequent. This time wiped everything including storage. It looks more like a hardware issue but I wonder if this could be malware even after wiping everything. I will have to take this in for repair but have little hope of solving this problem.
mach281 said:
I had the latest 6.0.1 samsung rom (CPK2) which was giving me problems with freezing. So I am trying to upgrade to an 7.x.x rom, either RR, AIPC, or Lineage.
Update 1: In the final attempt of upgrading I installed the official 6.0.1 fw which boots fine unlike the aforementioned alternatives (very strange). However, lock ups and now screen blanking more frequent. This time wiped everything including storage. It looks more like a hardware issue but I wonder if this could be malware even after wiping everything. I will have to take this in for repair but have little hope of solving this problem.
Click to expand...
Click to collapse
My wife has the US Cellular 10.5 variant (T807R4). It was freezing so frequently it had become almost unusable for anything but watching videos. Rooting and disabling most of the Samsung apps did not fix the problem. I wiped the system with TWRP only to discover that none of the custom ROMs would work on this model. I downloaded and flashed the stock Samsung MM firmware (and it sat on the opening splash screen for at least 15 minutes before it finally booted up) and for the hour I used it after setting it up, I had no problems. I had previously cleared the cache with Titanium Backup and that also seemed to be a temporary fix. My conclusion is that something is happening when the cache fills up that causes the freezes but I'll need more data to say that for sure.
Just an update: I was going to have the hardware looked at so I wiped everything including the storage. But when I took it to the shop and was asked to demonstrate the freezing the tablet wouldn't. So I took it back and it was running OK until a couple weeks later when the same problems reared there heads.
Somehow I managed to get a 7.1.2 installed and the T800 is running great...so far. I'll post back if the freezing starts again.
mach281 said:
Just an update: I was going to have the hardware looked at so I wiped everything including the storage. But when I took it to the shop and was asked to demonstrate the freezing the tablet wouldn't. So I took it back and it was running OK until a couple weeks later when the same problems reared there heads.
Somehow I managed to get a 7.1.2 installed and the T800 is running great...so far. I'll post back if the freezing starts again.
Click to expand...
Click to collapse
Please explain the steps to install 7.1.2 (and which ROM you used) and update on the freezing issue. Most of the freezing issues I have read about seem to be on LTE variants (SM-T807x) so I was about to buy a wifi only (T800) tablet, thinking that would be a solution to the problem. If that's not the case, then I shouldn't waste my money.
The instructions for installing a non-stock ROM are on the dev's host page in Tab s forums. I first tried Resurrection Remix and now am on LineageOS. It was only after I wiped the internal storage area that I was able to get past the 7.x.x boot screens.
I found the stock rom 6.0.1 freezing issue persistent. I believe the problems started for me with XAR H4 and really picked up with K2 (roms supplied by sammobile). The tablet would frequently just freeze while working in an app: the screen and hardware buttons would not respond at all. Never had that problem with Android 5. The only thing I was able to do to unfreeze it was to reboot into download mode then restart the OS from there. I sometimes found that if I left it frozen overnight it would unfreeze itself by morning.

Categories

Resources