Hello,
I have rooted my tablet a few weeks ago and installed cm11
I got a notification for a update and updated it today and now my tab pro 8.4 doesn't work anymore.
It is starting up and when i unlock the screen i get an error message and than it restarts.
It does this everytime.
I have searched for unrooting it but can not find the stock firmware etc.
Can anyone please help me!
Thanks,
Gunnar
gwien said:
Hello,
I have rooted my tablet a few weeks ago and installed cm11
I got a notification for a update and updated it today and now my tab pro 8.4 doesn't work anymore.
It is starting up and when i unlock the screen i get an error message and than it restarts.
It does this everytime.
I have searched for unrooting it but can not find the stock firmware etc.
Can anyone please help me!
Thanks,
Gunnar
Click to expand...
Click to collapse
Was this a couple of days ago or so? There was a day when someone broke every CM device. If not, you can always try a factory reset first.
If you have a backup, restore it and then install the latest nightly.
If you don't have a backup, well, now you know why you should have made one... Download the latest nightly on your computer and do one of:
* adb push it to your device
* adb side load it
* put it on a USB disk and use a usb-otg cable
And install it. If that doesn't work, factory reset it.
I did not use my tab for a few days and i connected it today with the wifi and got the notification for a update which i installed.
2 weeks ago i did a factory reset already because i wanted to go back to stock firmware so i guess i don't have a back up anymore?
I am new to rooting etc so i don't exactly know how everything works but i know i have made backups with titanium back up and TWRP etc.
I just did a factory reset with TWRP and thank god it is functioning normally again.
Thanks for your quick responding!
I still want to go back to stock firmware so does anyone know where i can get the stock firmware?
I am from the Netherlands so i don't know if i need another firmware than someone from another country.
Thanks,
Gunnar
Related
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!
Reposted in the correct forum
Afternoon everyone, I was hoping someone could assist with this problem, I have a Galaxy Tab 3 7" wifi only, I was running everything as stock inc 4.1.2 firmware, then I was prompted for an upgrade to 4.4.2, I stupidly did this without reading up ! I use to run the Tomtom software on my tab, used it everyday for work, now since the upgrade the tab will not find a GPS signal, no matter how long I leave it, after a few hours of reading and trying different things, cache cleared, reinstalled the app, restore to stock twice (still on 4.4.2) Im at a loss. I have read once its upto 4.4.2 it cannot go back to 4.1.2 as the boot loader is locked ? I am currently downloading a clean instal from Samobile of 4.4.2 to see if that will fix it, installed via Odin 3.10.6.
If anyone has cured a similar problem or can point me in the right direction I would be most grateful
Thanks
John
sort of fixed
Couldn't seem able to find a fix for this problem I had a dabble with my Tablet, installed TWRP, backed up the 4.4.2 stock ROM, found and installed the ROM by Jon Wesley Tranchida - uber cool ROM btw - fantastic boot logo's :good: but alas, the Tablet would still not run the GPS with Tomtom. So I took a risk and found a Stock 4.1.2 ROM from here http://stockroms.webs.com/downloads deleted everything and started again, Installed the 4.1.2 Ultimate ROM, installed Tomtom again and YES, everything works okay :highfive: I really miss all the addons though that were included in the ROM by Jon Wesley Tranchida. I still don't understand why Tomtom won't see GPS or the tablet wont access the GPS on 4.4.2, after 10 hours of reading up.. Although I did read it could be some thing to do with the baseband ? its beyond me lol
Tab s t705 singapore updated to hong kong lolipop 5.0.2.
Been using it for a month without problems till suddenly started freezing in certain situations.till now i think its isolated to charging!
Device rooted supersu/twrp.
Ive read about it on internet couldnt find aolution and happened to other tab s (800..700..etc) no solution found and some said linked to lollipop but ive used it a while before anything happened.
What i did and did NOT work.
1.with without sim/
2. Delete cashe/dalvik and wipe to factory
3, restore a previous backup twrp where the issue want there
4. Installed other rom ..blissrom
5.flashed seperal kernels and updated twrp to latest for tab s
6.using other charger
Can be hardware? What can go wrong? Maybe from a drop something happened?
It keeps freezing with wtever last on screen. Lockscreen/app opened/home screen..mostly on lockscreen as it seems to happen a while after starting charging.
Please help this problem is driving me crazy since i lose all my work when it happens and im on stock rooted lolipop rom
Anyone ??
No1
8.4 models have been known to have problems with the battery connector which causes issues. There is a video on YouTube for the fix.
i think its solved !
rolled back to stock 4.4.2 od3 that came with the tab s. rooted backup.
i dont know what app/update/root/kernel might cause it but seems it was actually from lollipop and confirmed now !
AND SEEMS TO WORK BACK NORMALLY NOW !
I doubt it's lollipop itself but more a rogue app if that is the case.
I would make a backup of your current system with flashfire then reinstall lollipop and see if it happens again.
If it does restore your flashfire backup.
Hey, guys. Hopefully one of you can help me. I've been having problems with my Galaxy tab 3 (Sprint version) all damn day and I figured I'd ask for help before I utterly destroy it.
So, I've been trying to restore the tablet to factory and nothing I do is working. It was rooted in the past but it was all undone before it was given to me a couple of years ago.
Anyway, I've downloaded the stock os from here, sammobile, and another source, but no matter which I use I seem to run into the same issues. (All flashed with odin 3.12)
1.) When resetting the tablet to factory before or after flashing, I almost constantly seem to get the message, "process system isn't responding."
2.) Keyboard seems unresponsive.
3.) Wifi doesn't seem to stay on, doesn't even let me get to where I can scan for signals.
Any help would be highly appreciated.
Sorry!
Can't help just because I don't own a T217S but I own a T210 instead!
They are two different models!
So yeah!
Good luck with what you are doing!
Cheers,
Diamond26
I have the same problem - Process system isn't responding Do you want to close it? I can't reply because the touch screen isn't working now. Anyone know what I should do?
What rom do you have on now?
Hello, just installed lineageos 17 on my galaxy tab s3 and everything seems ok except for one thing. When i open chrome and is about to write or search something the app just crashes, when i pick a saved bookmark everything works fine. Tested with firefox and no problems there just with chrome. Has anyone got any idea what could cause this? Rgs from Sweden
Continues, back to stock
I have a t820 and thought i should try lineage os 17.1. Said and done, flashed the files tablet booted no problems. After a couple of days i thought i liked to go back to stock. Downloaded the latest official fw and started flashing via odin but here is where the problem starts. Odin does not finish the flashing, i have tried many different files and version but same problem. So i thought i will flash lineage again but now the tablet gets to the boot screen but no further. Does anybody have any idea how i shall proceed? Many thanks in advance!
Continues
I managed to install lineageos again but would really like to go back to stock, i have downloaded stock rom from 3 different locations but odin wont flash the whole process, still no fault messages in odin. Does anybody have any idea what could cause this?
Solved
A reinstalled computer and another cable solved the problem!