Database Develop

[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.

[Q] Where can I find documentation?

OK, kind of a strange question but . . .
My daughter sent me this phone cause she got it as a freebie from TMobile and it came with the stock Gingerbread / bloatware configuration on it. I immediately Googled some info on how to root it, installed ClockworkMod and CM 11 and have been pretty happy.
Now I want to install the latest CM12 build. I grabbed the TWRP tool and the CM12 built and am ready to go, but first I would like to understand what I can safely delete and what features Google duplicates that CM provides. For example, I have three launchers on my phone (Trebuchet, Nova, and Google) and I am sure that is one, maybe two, too many. Ditto picture and sound apps.
I am not averse to actually reading documentation, but can somebody point me to a tutorial site where I can educate myself and do some reading. I prefer a skinny configuration that only has the stuff I need but I need a little guidance before I start nuking away.
Also, since I flashed this phone within hours of receiving it in the mail I never backed up anything in Gingerbread before the flash. I assume that I will have to reinstall all my apps and data after I flash to CM12 or is there a way to just flash the OS and leave the rest untouched?

Unable to enter Custom Recovery, Galaxy Pro 10.1 SM-T520 .Help Please, dead Robot

Hi all,
I have been hammering away at this one, and putting it on the back-burner, but now, it is really getting to me. Samsung Galaxy Tab Pro 10.1 SM-T520
It has been rooted with ODIN, and shows no problem, (things seem much easier now, as I have re-jigged lots of my old phones using so many more tools, I am not an expert, but can read and search without too much problems) I was very careful to choose the correct file, CF-Auto-Root-picassowifi-picassowifixx-smt520.zip, I have rechecked this step several times, as most of the instructions I found ODIN device ID:COM box should become yellow, when on newer versions it is blue I think, I wondered if I was going mad,
Root Checker Root access granted, all fine. I have Root access. n.
Installed CWM ,latest recovery for a Pro 10.1 wifi, recovery 6.0.3.1 Titanium backup-ed, all ready to go and Reboot and flash a new ROM.. No joy. .. Installed TWRP , same.
When it re-starts it ,shows the galaxy logo, flashes off, then back on, and then fails. Android dead with a red warning , standard recovery KOT49H.T520XXUANAE, all I can do is the usual options:apply update. The only thing I haven't tried is to just wipe all the data. I have a backup of my apps with Titanium Backup on the SD card,I am not that bothered really about much other data if its a pain. I just want control of my device and to try a new ,cleaner ROM(SMT520_GraveD_V3.0)
This has been bothering me for ages, I have read so many posts so am now getting really frustrated I have bought triangle away app. today although I think I sorted that issue early on anyway , but just in case...
Super SU seemed to have vanished so that is back installed
I think I searched and found the Mount/system issue and looked into an issue that lead me to the .system folder, but it is hidden, so I could not find the file it related to. I dont have the specifics to hand as I checked it out at work. I wondered if it is because I have ES file manager, not ASTRO as it said in some of the posts I found.but sure this is a red herring.
I have tried everything..I have a Mac at home and PC at work, I have tried ADB and can see &restart the device etc... so I am connected, first I got the error that it didn't recognise the sideload command. Read up on ADB , looked at the help etc. sideload isn't there as a command, very confusing. But I think I got there one I figured out paths, as of course they are different on a Mac, and possibly more so as I have 2 drives in it, which often confuses me ..grr.
I can of course get into the bootloader, with ON+VOL -, it tells me so far the system is : Official and Knox Warranty Void: 1 which I think is fine, but a chap at work suspected this, but after lots of threads I gather this is normal..
Sorry if long, just thought I should be as clear as possible. I have not really come across such an awkward issue as this , my HTC One was a breeze:crying:
*edit* Just worked out through trial and error, that to use the sideboot command I had to select send via ADB and now with the path /Desktop/SMT520_GraveD_V3.0.zip I was able to send the file but with the following messgae : E:footer is wrong and E:signature verification failed, twice.. So some progress
Thanks !

Just to say after being up waay too long on this, I discovered there is a newer firmware T520XXUANI1_T520BTUANI1_BTU which I may aswell upgrade to first, but of course I cannot do this OTA now As it recognises the device is 'tampered with' *sigh* so gun and games with Odin for Mac tonight, or JODIN3 , just to get the firmware upgrade(which seems to be a jungle of fake download links). before a Rom without bloatware..
I am also not completely clear why, as from another thread about KNOX, as I am basically running stock , without custom recovery.. According to this thread , but I am getting a bit confused now
http://forum.xda-developers.com/gal...neral/knox-warranty-void1-otas-t2996067/page2
Click to expand...
Click to collapse
however this is another story from the ROM install. Apologies

Well. No replies, but I did eventually solve this. Hopefully this can help someone. I am a tinkerer, but I really nearly gave up on this..But this was a cheap second hand tablet ( my first) and I want to see what it can do before I test drive one on my mother who is having nightmares with every Windows laptop I give her!
Once I got to a PC , I had access to Odin3, although it is not available online (apparently to Mac) I could not get it to work due to Java issues (JOdin3 online - brilliant idea but no joy for me so far)
I had the Rom I wanted ( GraveDigger- SMT520_GraveD_V3.0.zip ), the firmware update (T520XXUAOD2_T520BTUAOB1_BTU.zip(i think)) and the unlock file (CF-Auto-Root-picassowifi-picassowifixx-smt520.zip) , non of which I could install in any way , due to being locked out of using a custom Rom bootloader!
At this point I factory reset and cleared the cache( as that is the only options in the basic bootloader!) I also has ADB on the PC so attempted to install the files this way (after messing about using some software to produce the .tar and .md5 files needed for Odin. I tried everything to get this into proper 'bootloader mode' all from scrach again, including trying the adb oem unlockbootloader command, which I would never get to work as I could not get there!
With Odin, I was also again able to flash the firmware update, eventually, and of course had to unlock again. I was curious if I could now use the OTA update, and could not. At some point, in repeating this process( as I think it hung up several times and needed a hard reboot) I had at this point fully wiped the device as I know that is another reason to have glitches and an unstable ROM later.
I think I then tried to check and although T520XXUAOD2 seems to still be the firmware, at some point I managed to get online ( I think some superuser app which I have had to try several may have notified me that KNOX was reset:laugh:When I go to About>Software update it said I had the latest update! Good news!
At this point I had installed both CWM and TWRP again , and thought I would try TWRP.I had tried CWM and the same problem, like a double flash of the Samsung Logo , so I know it had reset !!
THIS TIME I used TWRP ( I thought of trying CWM touch, but its either paid, or I would have to find and ABD the file over I guess) , I managed to re-apply the Root file, Root checker confirmed this , as it had throughout this ordeal!, although apart from ACCESS GRANTED I dont really know what the rest means..Anyway although picassowifi , was still in Device name on TWRP I chose an earlier recovery version to install.- twp-2.7.0.0-picassowifi.img. When I re-booted, I was able to get the TWRP recover image, and install the ROM, I cannot remember if I re-rooted as I was so elated.
I had a few , freezing moments, reinstalling most of my apps through Titanium Backup, I think I just tried to reinstall everything which of was unnecessary, after a hard reset, all seems fine. I checked and the TWRP recovery seems to have stuck. I am not entirely sure how to check about the firmware , but for now I feel this is progress.
Good Luck if anyone found this any use.
Just to add, when you search this ( and probably many other models) you seem to get so many sites, offering exactly the same unlock information, in exactly the same way, many of the downloads seem to take you to many weird and wonderful places. So I tended to look here for downloads if possible. But I had to join SamMobile (which seems a useful site for the firmware upgrade) and trawl all over and assume similarities between other Samsung devices to fully check I was not being an idiot. But this was very odd and I could not find any posts or other workarounds that I did not try. But this new ROM feels lovely and smooth so far, and I now want to look into this tablet further

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.

Marshmallow 6.0.1 Missing ADB Capability?

I am running CyanogenMod version 13.0-20160127-UNOFFICAL-ovation ( Marshmallow 6.01) on my Nook HD Plus. I am mostly pretty happy with it. I made a backup of it and tried a couple of other images on my device, all the while intending to go back to my original installation. When I got ready to go back to it, I wiped everything using TWRP Recovery ( on an external SD card) , because I didn't want any "leftover" stuff from the other images on the installation. I was under the impression that TWRP backed up the user data, photos etc. I found that was not the case. ( Not really a big problem at this time.) In order to prevent this from happening in the future, I attempted to use adb to my PC to back up my user data (media, etc). I could not get it to work.... tried with another HD Plus ( with Marshmallow flashed overtop Jelly Bean... it worked fine. The PC is not seeing the Nook ( the first one). I looked on the internet and discovered that adb had been left out of Marshmallow by Google. I found a zip by Osm0sis on XDA that was supposed to address this omission, but it did not correct the problem. Can anyone help me with this? Thanks.

Same Problem
I am having the same problem as fire1951. I am also running Android 6.0.1 and cannot communicate with my computer using adb. I had no problem with this on previous versions of android (Jellybean)..... same device -- same computer. Was this capability left out of 6.01? I get conflicting information on this forum and the internet in general. Surely there's a flashable zip or some method to get this function back. Has no one else experienced this problem and possibly found a fix? Please help if you know a way to correct this.

Juan1002, I found out how to enable and access adb on 6.0.1. Since no one else seems to have this problem, I will pm you the procedure.