Database Develop

[SOLVED] Stock 4.2.1 upgrade failed.

I've bought my son and daughter a nexus 7 each for Christmas.
His upgraded over the air fine, hers downloaded the firmware, rebooted and the installation started.
After a couple of minutes the Android fell over with a red exclamation mark.
I've tried forcing the upgrade and the same happened.
Any ideas how to upgrade her nexus 7?
Thanks

Fastboot mode is working ?
Sent from my GT-I9100 using xda premium

I've not tried it.
How do I try it?
Assuming it's ok, does that help with upgrading?
Any issue truing fast boot mode?

Any ideas? Or will it need replacing?

Factory reset and try again
Sent from my Nexus 7

I have the same problem.

Hey guys,
I made an account just to post this, however it was all done my G2 so I apologize for poor formatting and/or not completely clear instructions. This issue has kept me up for hours upon hours, and I finally figured out how to fix it. The issue apparently has something to do with the way the Nexus was formatted, prohibiting the update from working. Google/Asus support have been useless regarding the issue which is a very simple fix just requiring the user to reflash the N7 with a stock image. It has been confirmed working by not just me but other people on the reddit nexus 7 board. Here is what I did (copy/pasted from my reddit thread):
---------------------------------------------------------------------------------------------------------------------
There are two methods to fix this, an in depth method, and an easy and quick method. My first time I used the in depth, but I tested this with the easy method too so I'll just post that. I'm on a cell phone so I'm not going into the in depth method - I'm posting this so hopefully the other people like me who got this on Christmas won't have to return it.
----------------
For the quick and easy method, download Wug's toolkit here:
(google this, forums wont let me post links until I reach 10 posts)
Run the driver install guide, making sure to follow the parts about uninstalling previous drivers. Follow this to a T. Next, unlock your bootloader. Its painless and takes seconds. Next, go here and download your Nexus specific update.
(Find this on google developer site, you can google it too - forums wont let me post links - also make sure its 4.2.1)
Click on the "back to stock + unroot" -- we never rooted, but just do this. Select other/browse and browse to the image you downloaded. Flash this. You WILL fail on three files - it says something like recovery.sig failed - it will do it for two other .sig files. This is fine. Let it do its thing. A few minutes later your android will boot up. Log in, and go to settings. Click about tablet. Click on build number like 10 times, until it tells you developer options unlocked. Go into developer options and enable USB debugging. Now, go back to Wugs toolkit and lock the bootloader. There you have it, an updated nexus running stock everything, and locked so your warranty is not void.
----------------------------------------------------------------------------------------------------------------------------
This was a very sloppy guide put together on my cell phone. Any questions just post and I'll do my best to get back to you. Goodluck!

Hi.
Thanks for the reply.
Just wondering if there is an easier way to do this.
I'm not comfortable flashing a new device.
What was the suggestion about fast boot?
Thanks

albert_htc said:
Hi.
Thanks for the reply.
Just wondering if there is an easier way to do this.
I'm not comfortable flashing a new device.
What was the suggestion about fast boot?
Thanks
Click to expand...
Click to collapse
This is definitely the easiest way for you to fix your problems. The risk of your device becoming unusable is practically none. This is the beauty of nexus devices, Google provides official factory reset ROMs for you to flash in these sorts of situations. You can either use Wugs or mskip's tookit as advised to automate the process (fastboot commands used to flash the recovery image, fastboot commands are simply used to flash it to your device) or you can use fastboot to flash it yourself manually (still very easy)
I would 100% do this to fix your device. Don't be scared! This is the official way of fixing a nexus device when it doesn't function.

Thanks.
I'm trying this now.
I've uninstalled all previous drivers, and it's updated to an 'Android Phone -> Android Composite ADB Interface'
I've clicked the Reboot BootLoader Button.. and nothing happens on the tablet.
This was trying with the #3 driver option.
I'm now trying driver #2 !!

Another quick question...
Once all this is done, will I have issues with it in the future, or should this resolve future updates.?

albert_htc said:
Another quick question...
Once all this is done, will I have issues with it in the future, or should this resolve future updates.?
Click to expand...
Click to collapse
I'm not certain about the driver issues because I don't use Wug's toolkit, sorry!
However, when you get this completed, it should solve this problem in the future.

I've had to go with option 1 for the drivers..
but it's done and working
One thing I did have to do after unlocking the boot loader was reset up on the wifi and re enable USB debugging before I could continue.
all sorted thanks

albert_htc said:
Thanks.
I'm trying this now.
I've uninstalled all previous drivers, and it's updated to an 'Android Phone -> Android Composite ADB Interface'
I've clicked the Reboot BootLoader Button.. and nothing happens on the tablet.
This was trying with the #3 driver option.
I'm now trying driver #2 !!
Click to expand...
Click to collapse
Let us know how it comes out and if there's problems, exactly where you're hitting the problem. I will try to help you out and later today I could probably get on team viewer and help you figure the drivers out.
Sent from my Nexus 7 using Tapatalk HD

Hi CharliesTheMan..
It's working. Had to use option 1 for the drivers.. but its updated and working
Thanks

Glad it worked out!
Sent from my Nexus 7 using Tapatalk HD

[Q] KFHD (2012) rooted?

Hi Everyone:
I am attempting to root and install cm11 on my son's KFHD. I am a bit of a noob, but I have successfully rooted my nook color in the past and read MANY threads on how to root, but I'm kind of at a loss.
The problem is that I followed the thread on how to root and I had a bunch of trouble. I finally was able to get through the steps, but the command box closed before the KFHD rebooted successfully. In an attempt to "fix" it, I restored the device to factory settings. It seems to be working just fine with stock os, but there is a superuser app which has requested access to apps.
I downloaded an app from Mobile1 to check that there is root access and the app indicates that I do indeed have root access. Should I go ahead and try to install a rom?
I would like to root it because my son is using it for school and is having a hard time adjusting to the stock os. (Which I hate, too).
Thank you so much!!!!
-NDH

1. Super User is the app that lets apps have access to root. (easy way of understanding it)
2. You need to Install Twrp and 2nd bootlander before installing the rom.
go to this video and follow the directions carefully. http://www.youtube.com/watch?v=a1bLCuQN0-U
3.Go to this video to install cm 11 rom for 2012 version. http://www.youtube.com/watch?v=0ODVX_EYaVY
4. once intalled new rom go to settings-about tablet-cyanogenmod updates and then update to latest version. IMPORTANT

thank you
Thank you for the advice. I appreciate it.
I've run into a new problem today, however. The device powered itself off and won't reboot at all. (It had a full charge). So I am off to do some research on how to fix this problem. UGH.
-NDH

ndharvey said:
Thank you for the advice. I appreciate it.
I've run into a new problem today, however. The device powered itself off and won't reboot at all. (It had a full charge). So I am off to do some research on how to fix this problem. UGH.
-NDH
Click to expand...
Click to collapse
Did you flash anything before this happened?

nope
SafinWasi said:
Did you flash anything before this happened?
Click to expand...
Click to collapse
I didn't flash anything - just tried to root. After several hours of trying lots of fixes and googling like crazy, I was able to get the device to turn on. My WIN7 laptop was not recognizing the KFHD. I tried a different usb port on my laptop and it installed all of teh drivers and recognized the device.
I did go ahead and order a fastboot cable - and I'm glad I did. The day after I got the KFHD working again, it turned itself off again and would not reboot.
I spent several hours today trying to understand fastboot and how to use the cable and a few minutes ago, I was able to restore a system image and get it back to stock. I am waiting for it to charge up a bit and then I'll set it up again. I think it worked because there are no apps or anything installed as of now.
All I really want to do is have access to the Play Store and install an alternate launcher, so it looks and feels comfortable for my kid. He's had the kindle for almost a year, but doesn't feel very comfortable using it and its something he needs to use at school (where I can't help him). Once its charged up, I will re-root - following directions very closely!!!!!
Thanks for your help!
NDH

ndharvey said:
I didn't flash anything - just tried to root. After several hours of trying lots of fixes and googling like crazy, I was able to get the device to turn on. My WIN7 laptop was not recognizing the KFHD. I tried a different usb port on my laptop and it installed all of teh drivers and recognized the device.
I did go ahead and order a fastboot cable - and I'm glad I did. The day after I got the KFHD working again, it turned itself off again and would not reboot.
I spent several hours today trying to understand fastboot and how to use the cable and a few minutes ago, I was able to restore a system image and get it back to stock. I am waiting for it to charge up a bit and then I'll set it up again. I think it worked because there are no apps or anything installed as of now.
All I really want to do is have access to the Play Store and install an alternate launcher, so it looks and feels comfortable for my kid. He's had the kindle for almost a year, but doesn't feel very comfortable using it and its something he needs to use at school (where I can't help him). Once its charged up, I will re-root - following directions very closely!!!!!
Thanks for your help!
NDH
Click to expand...
Click to collapse
I would recommend you to install a custom ROM like CyanogenMod. Trust me,you'll love it. AOSP is much better than Amazon OS.

[GUIDE] How to root Salaxy Tab S2 T817T

How to Root Samsung Tab S2 T817T (Step-By-Step Guide)
Obligatory notices
This procedure is only for the Samsung Tab S2 SM-T817T
Performing any of the operations in this post risks bricking your device
Performing any of the operations in this post will irreversibly void your warranty
Performing any of the operations in this post will irreversibly trip Knox and make it unusable for Samsung Pay (and any other features which require Knox)
I am not using a SIM card with my device, so I have no idea how this procedure will impact that functionality. People on the XDA thread (forum.xda-developers.com/tab-s2/help/sm-t817t-root-t3206079) where I pieced together these instructions from suggested that the SIM card still works for mobile data. UPDATE: Later in this thread people have confirmed that mobile data DOES work after rooting. Yay!
Introduction
OK, so a brief story of how/why I was forced to figure this method out. I found a listing on eBay for the Samsung Tab S2 T810N, paid $300 for it and received it into my impatient hands. Without checking the specific version of the tab I push right into the rooting procedure I had thoroughly researched for the T810N. Suddenly my tablet is in a bootloop and I am panicking that it is ruined. In the recovery mode I see that I have the T817T. Anger towards the seller aside, I frantically research how to recover the T817T. There is virtually no documentation for this procedure, so I am forced to mix-and-match. After about 5 hours, the tablet is finally up, running, and rooted!
TL;DR - verify your model number before attempting root
Files
All the files can be found here (drive.google.com/folderview?id=0BxPb6XhrMsaoa01zdjVUVWMzQWs&usp=sharing). Let me explain what each file is:
T817TUVS2AOL1_T817TTMB2AOL1_TMB.zip (drive.google.com/file/d/0BxPb6XhrMsaoeGpmbnRoeFA5MUU/view?usp=sharing) - This is an Android 5.1.1 image for Samsung Tab S2 T817T. You may not even need this, but just in case. If you use this, unzip the file to get the .md5 file!
SAMSUNG_USB_Driver_for_Mobile_Phones_v1.5.51.0.exe (drive.google.com/file/d/0BxPb6XhrMsaoc09qNm41OFhKLWc/view?usp=sharing) - Necessary Windows drivers for Samsung devices. Install this!
Odin3_v3.10.6.zip (drive.google.com/file/d/0BxPb6XhrMsaoLWtkek9UYWZGNGM/view?usp=sharing) - A flashing tool for Windows. Unzip these files!
twrp_2.8.7.1_LL_5.1.1_t810.tar (drive.google.com/file/d/0BxPb6XhrMsaoN0N6V3JzX290aGc/view?usp=sharing) - This is a custom recovery tool for Android. Although designed for the T810 series, it does work on the T817T. Do not untar these files!
Tab_S2_t817T_boot.zip (drive.google.com/file/d/0BxPb6XhrMsaob0hyME0zV2EtSnc/view?usp=sharing) - A custom bootloader for the T817T which is required to root. Do not unzip these files!
BETA-SuperSU-v2.52.zip (drive.google.com/file/d/0BxPb6XhrMsaoNk9uWkxRZ0wwTE0/view?usp=sharing) - A newer version of SuperSu which works on the T817T. Do not unzip these files!
Preparation
Download all the files above. Install, unzip, and untar (or not) as instructed.
Settings -> About device - Verify that you have the SM-T817T
Settings -> About device - Verify that you are running Android 5.1.1
Backup all your files, contacts, apps, etc.
Verify that your device has at least 80% charge
Rooting Procedure
(OPTIONAL) Flash Android 5.1.1 image. This step is not necessarily required. If you are running Android 5.1.1, then you should be fine. However, this is what I had to do, since I got into a bootloop by not checking my version number first (yes, stupid me). Further, if you have any errors or issues below you absolutely will need to perform this step to recover and restart the rooting procedure. Anyway:
Turn off your tablet
Boot into 'download mode' by holding POWER + VOLUME DOWN + HOME. Verify by pressing VOLUME UP
Run program Odin3 v3.10.7.exe
Plug your device to the computer with a USB cable
Verify that Odin message window states "<ID:#/###> Added!!"
Click the "AP" button in Odin and select T817TUVS2AOL1_T817TTMB2AOL1_T817TUVS2AOL1_HOME.tar.md5 file
Press "Start" button and wait for Green "PASS" message to appear. This will take a long time since this is a large file
Your device will automatically reboot
Perform basic setup procedures on Android so that you can access the Settings menu
From this point onward your must perform every step in the exact order as stated. Not doing so seriously risks putting your device into a bootloop or bricking it. You should be able to recover from that, but still...
Enable developer options:
Settings -> About device - click on "Build number" like 10 times until "Developer options" are enabled and button is added to Settings menu
Settings -> Developer options - enable:
Developer options - ON
OEM unlock - ON
USB debugging - ON
Flash TWRP recovery software:
Turn off your tablet
Boot into 'download mode' by holding POWER + VOLUME DOWN + HOME. Verify by pressing VOLUME UP
Run program Odin3 v3.10.7.exe
Plug your device to the computer with a USB cable
Verify that Odin message window states "<ID:#/###> Added!!"
Click the "AP" button in Odin and select twrp_2.8.7.1_LL_5.1.1_t810.tar (drive.google.com/file/d/0BxPb6XhrMsaoN0N6V3JzX290aGc/view?usp=sharing) file
Press "Start" button and wait for Green "PASS" message to appear
Your device will automatically reboot, verify that the tablet boots properly
Copy bootloader and SuperSu to tablet:
With your tablet on, attach it to your computer with a USB cable
Navigate to the root directory of the tablet storage
Copy Tab_S2_t817T_boot.zip (drive.google.com/file/d/0BxPb6XhrMsaob0hyME0zV2EtSnc/view?usp=sharing) and BETA-SuperSU-v2.52.zip (drive.google.com/file/d/0BxPb6XhrMsaoNk9uWkxRZ0wwTE0/view?usp=sharing) files to the root directory
Detach tablet from your computer
Flash custom bootloader with TWRP:
Turn off your tablet
Boot into 'recovery mode' by holding POWER + VOLUME UP + HOME
Select "Install"
Select Tab_S2_t817T_boot.zip and click "Install"
Verify install with slider
STOP HERE!!! READ THE NEXT STEPS CAREFULLY!!!
TWRP will now offer to install SuperSu for you. DON'T DO IT!! Doing this will cause your tablet to bootloop because it is not the right version of SuperSu
Decline the SuperSu installation and restart your tablet
Verify that the tablet boots properly
REPEAT "Flash TWRP recovery software:" instructions. This is a necessary step. Without it your tablet will go into a bootloop and you will need to start the root procedure over. Weird, I know. Just do it.
Flash SuperSu with TWRP:
Turn off your tablet
Boot into 'recovery mode' by holding POWER + VOLUME UP + HOME
Select "Install"
Select BETA-SuperSU-v2.52.zip and click "Install"
Verify install with slider
Reboot the tablet
DONE! Assuming your tablet boots properly your should now be rooted and see the SuperSu app installed on your tablet.
Recovery
If you need to recover from some error you will need to start over completely. Use the Android 5.1.1 image file T817TUVS2AOL1_T817TTMB2AOL1_TMB.zip (same as above) to perform this. You can also use this Android image to restore the device to an unrooted version. This will not restore your warranty or Knox.
Extras
To get rid of the pesky KNOX security notification which will persist, use a program like ROM Toolbox Lite (play.google.com/store/apps/details?id=com.jrummy.liberty.toolbox&hl=en). In the App Manager select the following apps and 'freeze' them:
SecurityLogAgent 4.1.4 (this one is critical to freeze!)
KNOX 2.3.0
KNOX 2.3.1
KNOX II 2.3.0
KNOX SetupWizardClient 2.3.0
KnoxFolderContainer 2.4.0
To get rid of the "No SIM card inserted" notification (if you aren't using a SIM card) use the build.Prop Editor in ROM Toolbox Lite. Add the following entry:
Property Name: ro.config.donot_nosim
Property Value: 1
Conclusions
I put this guide together for people who are having trouble finding a simple and easy-to-follow guide for rooting the T817T. Hopefully this can save you a number of frustrating and worrisome hours (not that rooting your Android device is ever a calm undertaking).
Please let me know if there are any errors in the procedure or if you have any suggestions regarding the steps or presentation of the material. Enjoy being a super-user!
Original content: blog.mchristian.co/blogs/post/How-to-Root-Samsung-Tab-S2-T817T/

phduhblog said:
Long time user, first time poster.
First off, let me say, THANK YOU XDA! You guys have been a crazy valuable resource over the years.
However, with regard to the T817T, the documentation is lacking severely. I have created a comprehensive step by step guide to rooting the T817T. Unfortunately, as a first time poster, I cannot post links or anything like that so...if somebody could fix that I would appreciate it. I spent a long time formatting the posting and adding file download links with the XDA formatter so that it wouldn't look like I was link whoring to my blog, just to be told to **** off... . Seeing as that's not possible, here is the url to my blog with the rooting instructions:
blog.mchristian.co/blogs/post/How-to-Root-Samsung-Tab-S2-T817T
Click to expand...
Click to collapse
http://blog.mchristian.co/blogs/post/How-to-Root-Samsung-Tab-S2-T817T
Thanks my friend
Edit: Completely professional and well done how to.. written just the way I like it, fantastic!! I think you should just edit your first post and paste all this in here on XDA... and ill be happy to carry your url link for you.

Complete text of the GUIDE
Edited and posted it above. Good luck with the rooting. Thanks!

An excellent guide. I'd spent the last few hours reading post after post gathering the correct information for the T817T specifically. I had come to the same basic conclusion as your guide states but its great to have some confirmation! I have a few differences in my install process than you did though. I did things in this order:
Enable developer options:
Copy bootloader and SuperSu to tablet:
THEN
Flash TWRP recovery software:
and between 6 and 7
Uncheck AutoReboot in the Options tab
7. Press "Start" button and wait for Green "PASS" message to appear
8. Use Power+VolumeDown+Home to reboot from bootloader and AS SOON as the screen goes black slide your finger from VolumeDown to VolumeUp
This should boot you into TWRP
Flash custom bootloader with TWRP:
after 4:
press "add another zip" and select the SuperSU zip as well.
5. Verify install with slider
6. Reboot
Done
By booting directly into TWRP the stock recovery doesn't have a chance to overwrite it. It won't need to be flashed a second time. You can also flash the kernel (...boot.zip) and SuperSU zip in the same pass. Saves a couple steps.
Either way I can confirm this works and all of the files are correct!
Thanks again for organizing all of this and making this great guide!

patrioticparadox said:
An excellent guide. I'd spent the last few hours reading post after post gathering the correct information for the T817T specifically. I had come to the same basic conclusion as your guide states but its great to have some confirmation! I have a few differences in my install process than you did though. I did things in this order:
Enable developer options:
Copy bootloader and SuperSu to tablet:
THEN
Flash TWRP recovery software:
and between 6 and 7
Uncheck AutoReboot in the Options tab
7. Press "Start" button and wait for Green "PASS" message to appear
8. Use Power+VolumeDown+Home to reboot from bootloader and AS SOON as the screen goes black slide your finger from VolumeDown to VolumeUp
This should boot you into TWRP
Flash custom bootloader with TWRP:
after 4:
press "add another zip" and select the SuperSU zip as well.
5. Verify install with slider
6. Reboot
Done
By booting directly into TWRP the stock recovery doesn't have a chance to overwrite it. It won't need to be flashed a second time. You can also flash the kernel (...boot.zip) and SuperSU zip in the same pass. Saves a couple steps.
Either way I can confirm this works and all of the files are correct!
Thanks again for organizing all of this and making this great guide!
Click to expand...
Click to collapse
I'm glad you have figured out another way! This is turning into what a proper thread on rooting should look like
I had actually tried the non-auto-reboot from Odin method too, but couldn't time the change to VOLUME UP correctly. After a couple times I just gave up and tried things the long way around. Never thought to flash the zip files in the same TWRP session though. I generally like doing things the long way around and getting confirmation that things still work after each and every step. Whatever works though!
Thanks for the reply

phduhblog said:
I'm glad you have figured out another way! This is turning into what a proper thread on rooting should look like
Click to expand...
Click to collapse
Indeed it is.
Are your volume buttons functioning properly after this? Just noticed yesterday mine aren't adjusting the volume.

patrioticparadox said:
Indeed it is.
Are your volume buttons functioning properly after this? Just noticed yesterday mine aren't adjusting the volume.
Click to expand...
Click to collapse
Hmmm, odd. Sorry to hear that. Yes, mine work just fine.

Turns out my volume buttons are fuctioning just fine. I think I just pressed it wrong and didn't have a minute to double check it at the time.

patrioticparadox said:
Turns out my volume buttons are fuctioning just fine. I think I just pressed it wrong and didn't have a minute to double check it at the time.
Click to expand...
Click to collapse
Whew! I'm glad to hear that. Now people can root their T817T without concern!

Yep! Been using this for two weeks now and no problems!

Can anyone confirm that the mobile internet still work when you have a SIM card in? Thanks.

phduhblog said:
Can anyone confirm that the mobile internet still work when you have a SIM card in? Thanks.
Click to expand...
Click to collapse
SIM does not work-- just restored back to stock.. going to wait a little bit before re-rooting.

androidcues said:
SIM does not work-- just restored back to stock.. going to wait a little bit before re-rooting.
Click to expand...
Click to collapse
Hmmm. Well that's good to know at least. Thanks for the update!
Also I'm glad you were able to revert to stock and get it working.

Yeah... Ive fully unrooted and gone back to samsung for a bit.. wont be long because I automatically gravitate back to CM. hehe.
vibration doesnt work on CM... that was a big thing because i rely on tactile vibration for notifications.... (i am deaf so.. the noisy parts are useless ?)
but anyway... taking a moment to thank you again for your writeup...i really needed that...soon after i read your blog i was rooted and rocking!
But Samsung sucks bro... i cant stand all these ****ty apps on my tablet so maybe I'll come back sooner.
0x1
Sent from my Nexus 5X using XDA Premium HD app

androidcues said:
Yeah... Ive fully unrooted and gone back to samsung for a bit.. wont be long because I automatically gravitate back to CM. hehe.
vibration doesnt work on CM... that was a big thing because i rely on tactile vibration for notifications.... (i am deaf so.. the noisy parts are useless )
but anyway... taking a moment to thank you again for your writeup...i really needed that...soon after i read your blog i was rooted and rocking!
But Samsung sucks bro... i cant stand all these ****ty apps on my tablet so maybe I'll come back sooner.
0x1
Sent from my Nexus 5X using XDA Premium HD app
Click to expand...
Click to collapse
Yep, I can definitely see why vibration notifications would be important for you!
As much as I dislike bloatware, from any company, Samsung just makes the most powerful tablets/phones. My best solution is to root and disable all the bloatware.
I'm glad the guide was well received and it seems to work for people.

My mobile data and SIM functions all work fine. Not sure why yours didn't

patrioticparadox said:
My mobile data and SIM functions all work fine. Not sure why yours didn't
Click to expand...
Click to collapse
Awesome! That is weird it didn't work for the other guy. Did you flash the provided Android version first or just go straight into the rooting? Thanks for the update!

phduhblog said:
Awesome! That is weird it didn't work for the other guy. Did you flash the provided Android version first or just go straight into the rooting? Thanks for the update!
Click to expand...
Click to collapse
Sorry for the late reply. I Odined the latest firmware to reset everything to a stock base before then flashing as your steps suggest (with the noted exceptions from my first post). My mobile data has worked flawlessly and I have had zero SIM related issues. In fact, I have had no issues what-so-ever. (I did think I had an issue with my volume rocker not working but that was user error. I have my tablet in a case of sorts and was not pressing hard enough). @phduhblog and @androidcues are you both still experiencing mobile data and SIM issues as of now?

patrioticparadox said:
Sorry for the late reply. I Odined the latest firmware to reset everything to a stock base before then flashing as your steps suggest (with the noted exceptions from my first post). My mobile data has worked flawlessly and I have had zero SIM related issues. In fact, I have had no issues what-so-ever. (I did think I had an issue with my volume rocker not working but that was user error. I have my tablet in a case of sorts and was not pressing hard enough). @phduhblog and @androidcues are you both still experiencing mobile data and SIM issues as of now?
Click to expand...
Click to collapse
Wording changed! Thanks for the update.

One question pls. I have the T817V tab 9.7 w/OEM bootloader option button. Is any of this available to use for my tab? TWRP recovery maybe? Any files? Any reply is appreciated. Novice seeking knowledge. Thank you so much.

Samsung Galaxy Note 3 Sm-n900a best rooting option?? Need current info.

Hello guys and Gals, this will be my first time posting so please bear with me. I have been trying to find the best option to root my Samsung Galaxy Note 3 Sm-n900a for a while now, seems to be one of the harder phones to root... this will be my first time attempting to root a device, so I want to make sure I do everything correctly. I have watched multiple videos and read a lot of threads on the subject but it is hard to find anything that is current and has the proper links to be files needed. if anybody has a good step-by-step walkthrough or video and the time to help me I would greatly appreciate it, if you do respond to the thread please dumb it down I am still learning terminology. I am determined to get this done come hell or high water. so if anybody has a good step-by-step walkthrough or video and the time to help me I would greatly appreciate it. Thank you for helping me put a nail in this coffin i I have been trying to do this far too long.

I just did this over the course of hours. I can't say I'm pleased with any of the explanations on xda-developers or found by Google. Unfortunately, writing up a good, full explanation is beyond me right now.
I did this from the Android 5.0.1? Lollipop "OC3" version (seen as the last 3 characters of the "Baseband version" under Settings -> General -> About device). Apparently this version cannot be rooted, however, you can downgrade your version of Android to one that you can root: Android 4.4.2 KitKat ("N900AUCUCNC2"). Apparently you can do something to stay rooted while manually updating to Android 5.0 Lollipop "OC1," but updating to the current AT&T version "OC3" revokes your root access.
I followed the process listed at https://forum.xda-developers.com/note-3-att/general/root-att-note-3-android-5-0-t3318130/post65467618, but if you are satisfied with having rooted Kitkat 4.4.2, you don't need to do steps 11 and 12. If you want the more recent Android 5.0 OC1, then do steps 11 & 12.
One thing I can do is help you understand some of the things I never saw explained. In the list of instructions you will see some programs you will need. A brief summary of each:
Odin - A program that runs on Windows that will manage some low-level aspects of your phone over a connected USB cable. It is used to install an OS (Kitkat 4.4.2 in this example) after your phone has been Wiped from the boot loader menu (gotten to by turning your phone on holding down VolumeUp + Home buttons). It is nice to have a MicroSD card onto which you can move various things before wiping the phone. (You never need to wipe your MicroSD card. Make sure you don't wipe it when using the Wipe feature in SafeStrap).
Towelroot - This is actual program that roots your phone using a known problem in the phone. After running the program, tap the only button there is to do it. I think this is a safe operation—as in, I think it will tell you if it can't rather than scrozzle your OS.
SuperSU - A program that manages which apps on your phone have root access. After it is installed, when you run a newly installed program that requires root access, SuperSU will pop up a dialog asking you if you want to grant it root access. I saw no indication you can get by without it, even if you don't need to "manage" app root access.
SafeStrap - This is a program that does various things, most importantly installing other operating systems that you previously loaded onto your phone as a file and then letting you choose which one you want to boot to whenever your phone boots up. It installs like a normal program, however from within the program you can "Install Recovery" or "Uninstall Recovery." "Recovery" is a bit of software it inserts into the phone boot process. While booting, if you want to use that software, you tap "Recovery" in the lower left. Tap "Continue" if you just want to boot with the currently active OS (chosen from within the Recovery software under the "Boot" options). With Recovery, you create a new slot for an OS, MAKE IT THE ACTIVE OS, Wipe it (Advanced, NOT format), then can back up a menu and install an OS from your MicroSD card. The purpose of all these shenanigans is so you don't have to lose your working Android install while installing something else.
Titanium Backup - A software backup program that requires root access to work. It also has a ton of other features loosely related to backing up. It is the simplest way to prevent AT&T from updating your version of Android to the unrooted current version. Having said that, it is anything but simple because of the user interface. You might investigate alternative methods for preventing auto-updating.
Be aware that whatever software (e.g., file manager) you use to hunt down files and folders on your phone is probably not going to be showing you everything. There are hundreds of programs that your phone uses, some of which are hidden. Titanium Backup does appear to be capable of showing a true full list of apps (including system apps). This is pertinent, because the AT&T Software Update program is hidden very well.
Potential costs:
$10-20 US approximately for a MicroSD card. There's fast ones that are in that price range. Google for reviews.
$5.99 for Titanium Backup from the Google Play store.

GregJ7 said:
I just did this over the course of hours. I can't say I'm pleased with any of the explanations on xda-developers or found by Google. Unfortunately, writing up a good, full explanation is beyond me right now.
I did this from the Android 5.0.1? Lollipop "OC3" version (seen as the last 3 characters of the "Baseband version" under Settings -> General -> About device). Apparently this version cannot be rooted, however, you can downgrade your version of Android to one that you can root: Android 4.4.2 KitKat ("N900AUCUCNC2"). Apparently you can do something to stay rooted while manually updating to Android 5.0 Lollipop "OC1," but updating to the current AT&T version "OC3" revokes your root access.
I followed the process listed at https://forum.xda-developers.com/no...att-note-3-android-5-0-t3318130/post65467618, but if you are satisfied with having rooted Kitkat 4.4.2, you don't need to do steps 11 and 12. If you want the more recent Android 5.0 OC1, then do steps 11 & 12.
One thing I can do is help you understand some of the things I never saw explained. In the list of instructions you will see some programs you will need. A brief summary of each:
Odin - A program that runs on Windows that will manage some low-level aspects of your phone over a connected USB cable. It is used to install an OS (Kitkat 4.4.2 in this example) after your phone has been Wiped from the boot loader menu (gotten to by turning your phone on holding down VolumeUp + Home buttons). It is nice to have a MicroSD card onto which you can move various things before wiping the phone. (You never need to wipe your MicroSD card. Make sure you don't wipe it when using the Wipe feature in SafeStrap).
Towelroot - This is actual program that roots your phone using a known problem in the phone. After running the program, tap the only button there is to do it. I think this is a safe operation—as in, I think it will tell you if it can't rather than scrozzle your OS.
SuperSU - A program that manages which apps on your phone have root access. After it is installed, when you run a newly installed program that requires root access, SuperSU will pop up a dialog asking you if you want to grant it root access. I saw no indication you can get by without it, even if you don't need to "manage" app root access.
SafeStrap - This is a program that does various things, most importantly installing other operating systems that you previously loaded onto your phone as a file and then letting you choose which one you want to boot to whenever your phone boots up. It installs like a normal program, however from within the program you can "Install Recovery" or "Uninstall Recovery." "Recovery" is a bit of software it inserts into the phone boot process. While booting, if you want to use that software, you tap "Recovery" in the lower left. Tap "Continue" if you just want to boot with the currently active OS (chosen from within the Recovery software under the "Boot" options). With Recovery, you create a new slot for an OS, MAKE IT THE ACTIVE OS, Wipe it (Advanced, NOT format), then can back up a menu and install an OS from your MicroSD card. The purpose of all these shenanigans is so you don't have to lose your working Android install while installing something else.
Titanium Backup - A software backup program that requires root access to work. It also has a ton of other features loosely related to backing up. It is the simplest way to prevent AT&T from updating your version of Android to the unrooted current version. Having said that, it is anything but simple because of the user interface. You might investigate alternative methods for preventing auto-updating.
Be aware that whatever software (e.g., file manager) you use to hunt down files and folders on your phone is probably not going to be showing you everything. There are hundreds of programs that your phone uses, some of which are hidden. Titanium Backup does appear to be capable of showing a true full list of apps (including system apps). This is pertinent, because the AT&T Software Update program is hidden very well.
Potential costs:
$10-20 US approximately for a MicroSD card. There's fast ones that are in that price range. Google for reviews.
$5.99 for Titanium Backup from the Google Play store.
Click to expand...
Click to collapse
Life got pretty busy there for a minute... I was able to get Titanium Backup I have had a good SD card for a while now safestrap SuperSU towelroot everything that I need. But this being my first time and not really ever using the software, it's giving me a little bit of anxiety. Before trying process the root I had a couple of questions that I definitely would like to get a solid answer on they might sound stupid but I'd rather sound stupid then not have a phone and ask lol. Okay how about we know I have a Note 3 SM n910a AT&T original carrier swapped over to Metro PCS I'm on one of their $50 plans which I think is unlimited everything but no tether so I have been using PDA and foxfi tethering from my phone to my computer... my roommate has a hotspot but he is rarely home. I need to know if it is possible to complete the root in that situation also the person from the thread that you sent me to confused me as far as making sure you have the ROM pre-downloaded. It just confused me I'm to the point I want to have somebody jump on TeamViewer with me and just make sure I don't screw up too bad.. I did go look at them custom robs as well if anybody would like to share their favorites or what they think is a good easy ROM to be able to play around with it and not mess it up too bad I would love any suggestions from anybody

XxLightxX said:
Life got pretty busy there for a minute... I was able to get Titanium Backup I have had a good SD card for a while now safestrap SuperSU towelroot everything that I need. But this being my first time and not really ever using the software, it's giving me a little bit of anxiety. Before trying process the root I had a couple of questions that I definitely would like to get a solid answer on they might sound stupid but I'd rather sound stupid then not have a phone and ask lol. Okay how about we know I have a Note 3 SM n910a AT&T original carrier swapped over to Metro PCS I'm on one of their $50 plans which I think is unlimited everything but no tether so I have been using PDA and foxfi tethering from my phone to my computer... my roommate has a hotspot but he is rarely home. I need to know if it is possible to complete the root in that situation also the person from the thread that you sent me to confused me as far as making sure you have the ROM pre-downloaded. It just confused me I'm to the point I want to have somebody jump on TeamViewer with me and just make sure I don't screw up too bad.. I did go look at them custom robs as well if anybody would like to share their favorites or what they think is a good easy ROM to be able to play around with it and not mess it up too bad I would love any suggestions from anybody
Click to expand...
Click to collapse
I just ended up stayin on kk rooted on mine. Everytime i goto lolipop i brick it. Its almost a hassle to try. I would odin the kk firmware and use towel root. Install xposed and some root apps. If ures is anything like mine dont debloat it. I debloat lightly. And next reboot get all kinds of spen and other force closes. The note 3 in general seem unstable. But i need to restore m8ne back stock now as its keeps force closing. I will be starting mine over for the 100th time it feels like. Dont let my ramblings discourage you. It is a awsome device and having a lgg5 iphone 5 and a few others my note 3s outer glass is destroyed. Got it like that. I would take the note 3 over the rest if i could get it to run rite more than 2 or 3 days at a time. Ive. Always set all my devices the same way. Debloated them the same but this one is really touchy.... Im on here a lot if u gots any ?s just hollar at me.

If you're still interested in an easy way to root, use Wondershare Dr Phone. It worked for me on stock OC1 and then the just used Flashfire to flash whatever I wanted.

Question How do you run an ADB command on a bootlooping device?

I have uninstalled a system app that I shouldn't have (something to do with network conectivity according to the recovery log) and everything was fine until I updated my device. I hadn't restarted it since removing the system app but after tyhe update it will no longer go past the Samsung galaxy logo. I remember doing something similar to either this device or another and I remember that I was abler to get into the system enough to be able to reinstall the neccessary app and fix the problem. However, this time I cannot get into adb at all. adb won't show any devices when in recovery, download mode, or at any of the three stages of the boot screen. I have tried wiping the cache and everything but factory resetting it as I have data that I can't lose. Any help would be appreciated whether getting adb install-existing to work or to pull important files off of the device before a reset. The device runs android 12 not rooted.

(...)
Go back via odin to the original firmware including the correct BIT.
(...)

Flash in Odin using home CSC file, simple

You only need to run ADB in Windows PC terminal or DOS mode in order to Odin flash firmware. No need to run ADB commands in the phone.
Just be sure that you install the "Samsung ADB Driver" into your PC before
you try Odin flashing firmware.
Just be sure you download the proper firmware for your phone.
Good luck, have a great day and have fun!

Thank you to all the help, but eventually I got into the phone. For anyone who may encounter a similar problem in the future:
After the phone reboots enough, it resets all preinstalled apps and removes any user installed ones and goes into safe mode. From here, the phone goes through the initial setup screens but all data is still intact, just not apps. Concerningly, it doesn't ask for you to enter your password, it just puts you on the homescreen, which seems bad from a privacy perspective as any samsung repair tech can easily cause the phone to boot loop. From here, you can back up anything important and factory reset. There is no way to exit safe mode once you've gotten this far.
I don't remember why odin didn't work, it may have been that I couldn't get the firmware to download as Samsung likes to change that stuff all the time or it may not have reinstalled the system app neccessary.
I should've been more clear in the original post but I have not flashed any unofficial firmware just the U1 firmware to remove carrier bloat, but that was way before this occurred. In case it wasn't clear, the problem happened because through
Code:
adb shell uninstall --user 0 package.name
an important system app was removed (something network related) which caused android to crash when trying to start the service. In short: be careful what you remove when using adb and, for all you forum members: read the whole post instead of jumping to conclusions about the user's mistake and if it isn't clear, ask for more details. Again, thank you to all the helpful comments even if they didn't end up working.

ZenDeveloper said:
Thank you to all the help, but eventually I got into the phone. For anyone who may encounter a similar problem in the future:
After the phone reboots enough, it resets all preinstalled apps and removes any user installed ones and goes into safe mode.
Click to expand...
Click to collapse
May I ask how long it took to "reboot enough"? I'm having issue updating to Android 13. It got into boot loop (the 2nd time actually. I mentioned about it in another thread a few weeks ago. Today I decided to try again). Anyway I am wondering if there's anyway I don't need to reset the whole thing. What you described interested me.
Thanks

hatoxda said:
May I ask how long it took to "reboot enough"? I'm having issue updating to Android 13. It got into boot loop (the 2nd time actually. I mentioned about it in another thread a few weeks ago. Today I decided to try again). Anyway I am wondering if there's anyway I don't need to reset the whole thing. What you described interested me.
Thanks
Click to expand...
Click to collapse
Sorry for the late reply,
I don't know how many times it needs to reboot to go into safe mode but it seemed like quite a bit maybe 20-30 times possibly like 100. But once it does it'll go through the initial setup screens and let you in without a password. It's very important to backup everything on your device before you mess with any system apps or update especially if you've previously messed with system apps. I however don't use google hence I didn't have a backup of anything and needed to get it off before hand.
It could also be possible that Samsung removed this back door in android 13 and just the act of trying to update it gets rid of it. I don't know I'm just throwing around ideas.

Rule #1 - if a OS is fast, stable and fulfilling its mission, let it be! Firmware upgrades/updates can and do break Samsung's.