[Q] Help! What have I done to my Pro 10.1 - Galaxy Tab Pro 12.2, 10.1, 8.4 Q&A, Help & Trouble

Here's the story. I purchased a factory refurb'd Tab Pro 10.1 (SM-T520NZKAXAR) on Woot a few weeks back. I live in Canada, but it is a USA tablet, if that matters. It came with a 90-day Samsung warranty. As soon as I got it, I started looking at custom ROMs. I have experience with custom ROMs on my HTC One m8 (and old m7), but not with any Samsung devices. I wish I had kept it stock for a few weeks first to check it out, but here we are.
I created a nandroid backup of the stock firmware, however I quickly deleted it during a wipe when flashing my first custom ROM, which was GraveD's v3.0. It seemed to go OK, but then it would start to freeze up and reboot on it's own. This seemed to happen mostly under load, and especially when trying to install apps from the Play store. I tried going back to the stock kernel, thinking that could be the problem. It stopped the crashing, but then wifi wouldn't work. So I could choose between having a tablet that crashes all the time, and has difficulty installing apps, or one without wifi. Both were basically useless.
I tried installing another custom ROM, GigaWatts Pro. Again, flashing seemed to go well, and the ROM also seemed to work very nicely for a couple of days. No random reboots, and wifi worked great. I spent a few days downloading all of my apps and getting things set up the way I like, when yesterday something went wrong. Perhaps the tablet lost its root (is that possible?). All of a sudden, apps are crashing all over the place (Unfortunately, [insert app name] has stopped). Titanium backup hangs at "Asking for root...". Installing apps is also difficult again. The tab doesn't reboot on it's own, but Play Services crashes constantly. Whenever I try to get into developer options, the Settings app crashes. I'm not even 100% sure USB debugging is enabled right now, although I'm still able to flash using ODIN.
I tried doing a factory reset and re-installing GigaWatts. Same problems. Tried making sure the root was OK. Same problems. I've tried using twrp 2.8.0.0 as well as 2.7.1.0 with no luck.
Right now, I've downloaded the stock firmware for Canada T520UEUANI1 4.4.2 (although the tab was bought from a USA site). I assume this also installs it's own Kernel. It shows Kernel version:
3.4.39-2776001
[email protected] #1
Mon Sep 15 17:44:40 KST 2014
I'm experiencing the same problems. Google Play Newsstand crashes every 10 minutes or so. Settings is almost useless. Installing apps is problematic.
Can anybody tell me if there's something I'm missing? Anything left to try? Does it sound like a hardware/ROM/kernel problem? If it's hardware, can I still utilize the Samsung warranty after trying to flash custom ROMs? I'm going to try to download another Cellular South stock ROM, but it seems like the problems are persisting regardless of which ROM i have installed, so I think it's something else (kernel or hardware-related).
Any help is GREATLY appreciated. My new tablet is basically useless, and I've run out of ideas.

Try this latest firmware since you mentioned your tablet is the XAR model the firmware should be cellular south (wifi)
http://www.sammobile.com/firmwares/download/39630/T520UEUANK1_T520XARANK1_XAR.zip/
If that doesn't help then it could just be a bad tablet .
(btw when you flashed a custom rom you probably tripped the hardware knox flag and voided any warranty it had, I guess you could play dumb if they ask and say it came like that since it was refurbished, and hope they still repair/replace it)

I just tried the USA cellular south firmware. Still experiencing the exact same issues. I'm completely out of ideas. Does anyone else have any ideas? Otherwise I'm going to have to try warranty service and hope for the best. Is there anything I can do to restore the Knox flag before I send it in?
Also, in download mode the tab is recognizing the system as custom. Is this normal after flashing a stock image?

So do a factory reset in recovery, and clear the cache also. Then load the cellular South file thru Odin. Then factory reset again. See if this clears your problems.

k8108 said:
So do a factory reset in recovery, and clear the cache also. Then load the cellular South file thru Odin. Then factory reset again. See if this clears your problems.
Click to expand...
Click to collapse
I've tried the Cellular South firmware to no avail. I'll be trying to warranty the tablet now. Fingers crossed!

Related

[Q] I am absolutely stumped, please help

Hi All, I come begging for help after exhausting all of my options and searches for similar issues.
I have a CDMA Galaxy Nexus Stock 4.0.2 but rooted (I installed CWM).
I woke up to my phone stuck in the boot loading screen; it just kept looping over and over. I shut off the phone restarted it and the phone was practically unuseable, it ran very very slow. Now I haven't done anything recently or installed any apps. The only app I installed was a modified MMS app (one of the Inverted Black ones), but that was 2 weeks ago and everything was running fine since then. (However since I'm not on a deodexed Rom, I knew there could be issues).
Well I of course switched back to the stock MMS app that I had manually backed up and that did not help. Now my phone would load, it would get to my homescreen, but it would then say something along, "service is not working, wait, close, or ok?" I'd hit wait and within 2 minutes my phone would automatically reboot and then go into a a sort-of bootloop (it would just show the boot.img and loop).
I then tried to restore two Nandroid back-ups (which were basically bone stock and made months ago) and both worked, except it would say secure.img not found or something like that. I was still able to boot up and use these back ups, but then within 5 minutes I would get the same error and then the phone would reboot.
After retrying them I decided to to just go bone stock and wipe and do a factory reset. This worked and everything seemed fine until I went to turn on wi-fi.
I would wait for wi-fi to turn on and eventually it would just quit and then reboot the phone. I did this 3 times in a row to confirm that it was indeed wi-fi causing these rebooting issues.
Now here's the thing, right now my phone is working as I have purposely tried not to touch the wi-fi (I need to use my phone) . Data, voice, mms/sms all work. But I literally have no idea why wi-fi would be causing my OS to go crazy?
My last resort is to flash the stock toro.img but I was hoping you guys could help me before I get to that point.
As of right now even though I did a data wipe/factory restore my phone is still rooted (rooted apps all work) and my bootloader is still unlocked. (I renamed the secure.bootloader file as per the instructions when using fastboot to load CWM).
Please help me troubleshoot this, Thanks guys.
I don't know if you have tried but maybe try flashing a rom after a data wipe
angelino0919 said:
I don't know if you have tried but maybe try flashing a rom after a data wipe
Click to expand...
Click to collapse
I'm thinking about doing this as well since I will probably have to flash back to stock. I just want to make sure I can get back to stock since I am still covered by warranty and insurance (assuming they do not check to see if my phone has an unlocked bootloader).
JayBeezy802 said:
I'm thinking about doing this as well since I will probably have to flash back to stock. I just want to make sure I can get back to stock since I am still covered by warranty and insurance (assuming they do not check to see if my phone has an unlocked bootloader).
Click to expand...
Click to collapse
Well you can always relock the bootloader. I doubt you will have to go back to stock though

Stock rom problem ... is there a fix?

Hi guys. I am stuck at an impasse here and I know someone here will be able to help.
My wife and I just bought two Samsung Galaxy 2 Epics (refurbished) from the retailer Glyde. I purchased from them because they are partnered with my new carrier, Ting.
My phone activated and ported my number with no issues. Everything works perfectly.
Her phone appeared to activate and then rebooted. It will not go past the Sprint 4G animated opening. I have rebooted, wiped cache, and done factory reset. Still ... 4G logo animation appears and the screen either goes black (appears to shut down) or it just stays on the 4G logo without moving on and then a few minutes later goes black. The phone worked fine before we tried to activate it. It logged in her gmail and connected to wifi.
I am able to get to recovery mode. I was probably going to root and cyanogenmod mine. In your opinion, would this type of action possibly correct the problem with her phone? Is it possible to root and flash the original stock rom in a situation like this? Would that even work seeing that factory reset did no good?
I have contacted Glyde and am waiting - they may or may not replace. If they do replace that is a 2-3 week turn-around. I would rather work some magic here, if possible.
Thoughts and help are appreciated!
Brian
You might have to Odin a stock rom most likely
? Powered By My Moga Pro ?
9/10 Times if you can Odin it, you can fix it. BUT, restoring to stock via Odin will break your flash.
Chances are your flash is already cracked up a little.
A simple cricket nv gen google search combined with Odin, drivers, and DFS Tool. You'll be able to get it back up and running smoothly.
And if your device was on a stock rooted ROM, and you have a custom recovery, then flash a 4.1.2 Custom touchwiz ROM. That way, no programming will be lost.
If you decide to flash an AOSP/AOKP ROM like Cyanogen you could possibly break your flash.
2 cents.
fixed
Would you guys believe it was the battery? It was. I swapped batteries and the other phone started doing the same thing. Battery replaced and problem solved. I guess I panicked, but it sure seemed like a software issue. Thanks for the advice.

[Q] Question RE Random Reboots and Freezing on stock 4.4.2

I have read around regarding this problem without luck, and hope that someone can advise if I have missed anything.
I used to use this phone and as I liked to tweak it was running a custom rom (think it was Wanams). Anyway I got an upgrade ages ago, and my wife carried on using the phone for a while. As she just needs a standard rom I recently decided to factory reset and use Odin to flash the newest stock rom (N7100XXUFNE1 - UK). This is when the problems started. Initially the Wifi wouldn't come on, but after factory resetting and using the Samsung Updater in Kies I finally managed to get Wifi back. Then, while setting it up and installing apps from the Play store it started freezing and had to be rebooted every 5 or 10 mins. Finally after doing this a couple of times, all the apps were installed and after leaving it to "settle" it seemed to be better. Now however, 2 or 3 times a day, when playing games or using other apps, it will just reboot.
What I have tried is:
* I have tried clearing cache through the stock recovery
* Tried a number of Factory Resets
* After reading about the SDS problem I have tried running the "dummy file generator" to fill the internal memory and this completes ok. I guess this means that although I have memory that is/was susceptible I applied the original SDS fix early enough with the custom rom that all the memory is still ok?
As I have the newest bootloader I can't downgrade that, but as I don't care about triggering Knox I was thinking of rooting and installing a custom rom to see if any of the other Kernels help?
Has anyone got any idea's what could be causing this and what I can do to fix it?
Thanks.

Random Restart Issues

I have been having issues with my Note3 ever since the kit kat update back in April. It worked flawlessly on Jelly Bean and I had no issues for over 3 months. I updated to kit kat via Kies with everything completely stock. Since then I get completely random reboots, it could happen when launching an app or even unlocking the screen, and it happens 2 or 3 times a day. So far I have tried 2 factory resets, clearing dalvik cache, and replacing the battery with an Anker replacement. I have tried turning off auto-updating of apps, and turning off wifi scanning. I have also tried running the phone with no apps installed. So far nothing has worked.
I have read several posts with people blaming the stock kernal for these reboots, but there is no definitive solution to this problem. I am looking for any and all help the community has to offer.
Some additional info:
Running latest stock rom- rooted via effortless method
Stock Recovery
Knox is still 0x0
No sd card in phone
Since you have no issues doing a factory reset, I recommend the following:
1.). Backup all the data you need
2.) Download the newest carrier available firmware for you from sammobile.com
3.) Flash via Odin
4.) Once finished and phone has rebooted, return to stock recovery and perform another data wipe
That will 100% fix your issues, sounds like maybe a corrupt system partition or libs
icenight89 said:
Since you have no issues doing a factory reset, I recommend the following:
1.). Backup all the data you need
2.) Download the newest carrier available firmware for you from sammobile.com
3.) Flash via Odin
4.) Once finished and phone has rebooted, return to stock recovery and perform another data wipe
That will 100% fix your issues, sounds like maybe a corrupt system partition or libs
Click to expand...
Click to collapse
Thanks, I'll give this a try. Last night I uninstalled a bunch of bloat ware with titanium backup to make sure it's still not an app issue. If it reboots again I'll reflash the firmware. Since I'll. Be flashing stock it shouldn't trip knox right?
No, latest firmware complete stock will not trip Knox, as long as you're either doing a parallel upgrade NF9 > NF9 or NB4 > NF9. A downgrade will either fail or trip.
For anyone reading this, i tried to reflash the stock nf9 kernal to see if that was the issue, but i got a restart about 4 hours later. I am going to reflash the firmware via odin and report back.
I am having this issue for a long time. i have done everything, and finally i gave up, as i think it is a hardware issue. what make me confuse is the problem start since the day i upgrade to kit-kat. with every firmware come out i have a new problem. the latest "NF9" my phone just hang and black screen untill i press the power button for 30 second, then will restart. what make crazy is that it shuts off at night, and when i woke up i miss the alarm.
I'm sad to report that the reflash didn't work. I reflashed the NF9 firmware using odin about 4 days ago and it was fine for awhile, but I got 2 reboots today. I'm not sure what is causing this, but I am still open to suggestions. I don't think its hardware related since it didn't do this before kitkat. I still have my samsung warranty until february I believe, so if worst comes to worst then ill have to send it in, but i'm not sure what they will do about it.
The only thing I havent tried is replacing the sim card. Could a sim card cause a reboot issue like this?
i have already done it, even the SD card, still same problem.
Is there some kind of log feature in android that logs crash events or errors somewhere so i can maybe figure out what the problem is?
by the way i think i have solve my problem by updating busybox and supersu. i had to install busybox to system/xbin. and since that day i haven't encounter any restart or freez. almost 2 week. i hope that fix your problem as well.
makki666 said:
by the way i think i have solve my problem by updating busybox and supersu. i had to install busybox to system/xbin. and since that day i haven't encounter any restart or freez. almost 2 week. i hope that fix your problem as well.
Click to expand...
Click to collapse
I do not have busybox installed, and SuperSU is up to date. Also, the restarts happen with or without root ie without SuperSU. I still dont think its an app problem.
Just an update for anyone reading this. I have installed SetCPU to manage cpu clock speeds. I have had it installed for about a week and have not had an update with my custom profiles. It seems the restarts occur when cpu speed is at about ~675MHz. Not sure if its hardware or software yet. Any help is appreciated!
Update. I sent my phone in to samsung for repair. It looks like they just reflashed the firmware. After having it up and running again for 15 minutes the phone rebooted again. I contacted samsung and they recommended sending it in again. I'm not sure if it's worth it to send in again or if i should break my warranty and flash a custom rom. Any suggestions are welcome!
I get restarts because the modem crashes... its a known issue apparently
gtharea said:
I get restarts because the modem crashes... its a known issue apparently
Click to expand...
Click to collapse
I cant believe its taken over a year for this issue to get fixed. Im almost positive its a software issue since it never happened on jelly bean. It's strange that not a lot of people have this problem though. A lot of people must have already flashed custom roms I may send it in again since I still have knox 0x0 and see if they do anything else besides reflash the firmware this time. If they only do a reflash again i will just flash a new rom and hopefully everything will be fixed
Final Update:
I sent my phone back to Samsung, apparently my issues were a hardware problem. This time they replaced the "PBA assembly" aka the mainboard. I have had the phone back for almost two weeks without a single restart. I believe my restart problems are over. I hope this information helps anyone with similar issues. I would recommend sending it to Samsung for warranty repair if you are still under warranty. :good:
_bhaves_ said:
Final Update:
I sent my phone back to Samsung, apparently my issues were a hardware problem. This time they replaced the "PBA assembly" aka the mainboard. I have had the phone back for almost two weeks without a single restart. I believe my restart problems are over. I hope this information helps anyone with similar issues. I would recommend sending it to Samsung for warranty repair if you are still under warranty. :good:
Click to expand...
Click to collapse
I had the same problem but already tripped knox so iffy on sending it in. Funny thing is I did the external sd write fix and the phone has not rebooted since, going on 3 days.
meoshe said:
I had the same problem but already tripped knox so iffy on sending it in. Funny thing is I did the external sd write fix and the phone has not rebooted since, going on 3 days.
Click to expand...
Click to collapse
I would get reboots even without an SD card put in the phone, so I don't think that would have helped me. I havent had a reboot since I've had the device back

Galaxy Note 10.1 SM-P600 Reboot Loop

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!

Categories

Resources