Hi all
I've just bought a Fire Tablet on Amazon day with the intention of rooting it and installing CM, but I am a newbie and there's so much information on here it's kind of overwhelming, and most of it has a lot of "if this, then that, or if you want to use that, do this" type guides, which for someones who doesn't really know what all the different methods and options are is really confusing!
So can someone please tell me the step by step process for doing it?
From what I've read I think I have to downgrade to 5.1.2 of the OS as I can't root on 5.1.4? Is that correct?
So do I have to root before I do that? Or do I downgrade first and then root, and then install the CM?
If someone can list each of the steps I need to take to get it from a fresh new 5th Gen Fire 7 to having all the Amazon rubbish off and having it running CM, then I can look for the guides for each step!
Thanks, I hope that makes sense!
:angel:
PS: I've already bricked one by trying to downgrade to 5.1.1 because that wasn't apparent until it was too late, replacement on its way!
Yeah, I read the same thing and I bought it on Prime day. When's the 5.14 tool going to come out? I know, beggars... I really think it's silly to have to downgrade and risk bricking it when normal root for those OS versions don't have such a concern.
Bob Boblaw said:
Hi all
I've just bought a Fire Tablet on Amazon day with the intention of rooting it and installing CM, but I am a newbie and there's so much information on here it's kind of overwhelming, and most of it has a lot of "if this, then that, or if you want to use that, do this" type guides, which for someones who doesn't really know what all the different methods and options are is really confusing!
So can someone please tell me the step by step process for doing it?
From what I've read I think I have to downgrade to 5.1.2 of the OS as I can't root on 5.1.4? Is that correct?
So do I have to root before I do that? Or do I downgrade first and then root, and then install the CM?
If someone can list each of the steps I need to take to get it from a fresh new 5th Gen Fire 7 to having all the Amazon rubbish off and having it running CM, then I can look for the guides for each step!
Thanks, I hope that makes sense!
:angel:
PS: I've already bricked one by trying to downgrade to 5.1.1 because that wasn't apparent until it was too late, replacement on its way!
Click to expand...
Click to collapse
I did the same thing, bought the tablet on prime day and was successfully able to root it and put the AOSP nexus rom
First things first make sure you have the 7-inch tablet for the following steps because apparently it only works with that specific model. Since this is my first post I can't post any links so sorry about that however, I have added the video title so that you can just google it and find the video.
Anything above fire os 5.1.2 ( that is 5.1.4, 5.1.3, 5.1.2.1) has to be downgraded to 5.1.2.
Also downgrading from 5.1.4 to 5.1.1 is going to give you a hard brick. I don't know how you didn't know that but it was clearly stated in the xda guide I was following
Basically you have to follow rootjunkys video and instead of using the file he uses in the video use the fire OS 5.1.2 file which is also available on his website.
Imortant: Do a factory reset before downgrading. I did not do that and the rooting process did not work.
Video title: How to Firmware Restore or Unbrick your Amazon Fire 5th gen Tablet
After you have fire OS 5.1.2 follow the rooting process shown in another rootjunky video
Video title: How to root the Amazon Fire 5th gen 7in on Fire OS 5 1 2 SuperTool Mac linux and Windows
Note: He shows how to do the whole process while using mac but it can be done on windows awell and the windows files are already present. Instead of using the .sh file and opening the terminal double click the .bat file and follow along.
You can use his SuperTool to put the play store app and fire flash app.
Note: For some reason fire flash was not working properly for me by using the SuperTool, so I just installed it from the google play store.
Now you should have rooted fire OS 5.1.2 along with superSU. Now with the fire flash app and you can download any rom that you want to flash. Follow the steps in the video for instructions
Video title: Amazon Fire 5th gen AOSP Nexus rom install with Flash Fire app
Hope this helps.
All credit to rootjunky
erikthebikeman said:
Yeah, I read the same thing and I bought it on Prime day. When's the 5.14 tool going to come out? I know, beggars... I really think it's silly to have to downgrade and risk bricking it when normal root for those OS versions don't have such a concern.
Click to expand...
Click to collapse
It's not a matter of someone getting off their keister and whipping up a "tool" (presumably you are talking about root) that works with FireOS 5.1.4 or whatever the latest version is. Like many manufactures Amazon actively discourages rooting devices and attempt to block known exploits. It's a cat and mouse game. We may see a "tool" soon, much further down the road or never. Be happy you can root the device at all and be thankful for the individuals who unselfishly share their time and talents with the community.
Thanks nefarian.
The problem was that the guide I was referred to for getting CM onto it already assumed it had been rooted, and when I started googling and looking on the different guides on rootjunky there were so many coming from different angles but nothing giving the clear start to end steps for what I wanted to do, for a newbie it was very confusing. Plus in the guide I was following (a rootjunky one) he had an older version of the OS and the toolkit had different files/folders to what are in it now, so I guess at that time there was no mentioned of 5.1.4 and not being able to go back.
After thinking I needed to downgrade the OS I found the one for unbrinking and downgrading and did that fine to 5.1.2, but then when I tried the superkit it still said it was too new, so I tried to downgrade further, which is when I bricked it.
There was no mention of it on the video..... other than a bloody great overlay in the corner, which must have been added later on, and probably because I was tearing my hair out and getting confused I didn't spot it. That's my excuse anyway!
Thanks for your help, I'll have a go with the new one on Monday. So instead of trying to find an all in one guide, I need to find guide for the steps in this order;
1 - do a factory reset on the device (from the device settings, or do I need to do it in the bootloader settings?)
2 -downgrade to 5.1.2 (I should be able to do this now)
3 - root the device (and install supersu?)
4 - install CM
Then it should have full CM and none of the Amazon OS left.
I'm not missing any steps there am I?
Thanks again!
Bob Boblaw said:
Thanks nefarian.
The problem was that the guide I was referred to for getting CM onto it already assumed it had been rooted, and when I started googling and looking on the different guides on rootjunky there were so many coming from different angles but nothing giving the clear start to end steps for what I wanted to do, for a newbie it was very confusing. Plus in the guide I was following (a rootjunky one) he had an older version of the OS and the toolkit had different files/folders to what are in it now, so I guess at that time there was no mentioned of 5.1.4 and not being able to go back.
After thinking I needed to downgrade the OS I found the one for unbrinking and downgrading and did that fine to 5.1.2, but then when I tried the superkit it still said it was too new, so I tried to downgrade further, which is when I bricked it.
There was no mention of it on the video..... other than a bloody great overlay in the corner, which must have been added later on, and probably because I was tearing my hair out and getting confused I didn't spot it. That's my excuse anyway!
Thanks for your help, I'll have a go with the new one on Monday. So instead of trying to find an all in one guide, I need to find guide for the steps in this order;
1 - do a factory reset on the device (from the device settings, or do I need to do it in the bootloader settings?)
2 -downgrade to 5.1.2 (I should be able to do this now)
3 - root the device (and install supersu?)
4 - install CM
Then it should have full CM and none of the Amazon OS left.
I'm not missing any steps there am I?
Thanks again!
Click to expand...
Click to collapse
- no need for a factory reset at any point; offers no benefit for what you are trying to accomplish.
- installation of SuperSU (replacing Kinguser and related Kingroot cruft) after rooting is highly recommended prior to using FlashFire or any other tool that messes with the system partition. The SuperTool can facilitate this otherwise ugly task.
- if you are struggling with RootJunky videos you should give serious consideration to the challenges of installing a custom rom. It doesn't get any easier going forward.
Thanks. I managed to root my Nvidia Shield TV fine so I should be able to do it, I just needed to be clear of the full process from start to finish, and as I wasn't starting from the beginning of the process that made it more confusing. The rootjunky videos are great, but when someone is saying you can use this or that or do this or that it's putting choices and variables in to the mix so it's not a straighforward step by step, and when the kits and the webpages shown on the videos have changed since they were made, for someone trying to piece the info together it takes a bit more time.
Maybe I should point out that I didn't look on here initially when I started trying to do it, I basically saw the fire on offer mentioned on a forum I use and someone said yeah, it's easy to root and get CM on if, just user this video, with the link to a rootjunky YouTube video which didn't mention the prerequisite of already having downgraded the OS (why would it) so in hindsight I didn't start at the right place or have the best information.
After reading through some stuff on here (and that's over whelming for a first timer as there is so much stuff on here for many, many devices and platforms - even just finding the Amazon fire sub forum on an iPad wasn't easy!) I'm getting a better idea for attempt two.
I'll get there, and at least I know how to not brick it now! :good:
OK, so making progress. I have downgraded the new one fine, it now has 5.1.2 of the Fire OS.
I've used rootjunkys supertool to root the device with Kingmaker, which then installed SuperSU, and I finally uninstalled Kingmaker/Purity.
So I now have a rooted Fire, which is great. I have also installed the Google Play store, disabled OTA updates and removed ads from the lock screen. But I don't want the Amazon OS on it (pretty fugly isn't it!), so the next step, flashing it with CM.
What guide would be best for a Fire with 5.1.2 on it? When I look at the Rootjunkys guide for installing CM on the Fire (https://www.youtube.com/watch?v=4dwguHoxTvo&feature=youtu.be) the super tool kit does differ, and the one I downloaded from his link only has the tool for doing it for OS 5.0.1, so it won't let me boot into TWRP recovery. What would be the best tools/guide/method to use for installing CM onto a Fire with 5.1.2?
Thanks
Bob Boblaw said:
OK, so making progress. I have downgraded the new one fine, it now has 5.1.2 of the Fire OS.
I've used rootjunkys supertool to root the device with Kingmaker, which then installed SuperSU, and I finally uninstalled Kingmaker/Purity.
So I now have a rooted Fire, which is great. I have also installed the Google Play store, disabled OTA updates and removed ads from the lock screen. But I don't want the Amazon OS on it (pretty fugly isn't it!), so the next step, flashing it with CM.
What guide would be best for a Fire with 5.1.2 on it? When I look at the Rootjunkys guide for installing CM on the Fire (
&feature=youtu.be) the super tool kit does differ, and the one I downloaded from his link only has the tool for doing it for OS 5.0.1, so it won't let me boot into TWRP recovery. What would be the best tools/guide/method to use for installing CM onto a Fire with 5.1.2?
Thanks
Click to expand...
Click to collapse
- Kingroot/Purify, not Kingmaker/Purity
- I can't think of a better suite of guides than the videos produced by RootJunky
- use FlashFire 0.51 to install (flash) the rom of your choice
- OP for Nexus rom has video link and and basic FlashFire guidance
- get over the minor variations in the language/tools used to support this device between the making of videos and the latest release.
Bob Boblaw said:
OK, so making progress. I have downgraded the new one fine, it now has 5.1.2 of the Fire OS.
I've used rootjunkys supertool to root the device with Kingmaker, which then installed SuperSU, and I finally uninstalled Kingmaker/Purity.
So I now have a rooted Fire, which is great. I have also installed the Google Play store, disabled OTA updates and removed ads from the lock screen. But I don't want the Amazon OS on it (pretty fugly isn't it!), so the next step, flashing it with CM.
What guide would be best for a Fire with 5.1.2 on it? When I look at the Rootjunkys guide for installing CM on the Fire (https://www.youtube.com/watch?v=4dwguHoxTvo&feature=youtu.be) the super tool kit does differ, and the one I downloaded from his link only has the tool for doing it for OS 5.0.1, so it won't let me boot into TWRP recovery. What would be the best tools/guide/method to use for installing CM onto a Fire with 5.1.2?
Thanks
Click to expand...
Click to collapse
1. Get the CM rom and put it in the tablet from here: http://forum.xda-developers.com/amazon-fire/orig-development/rom-cm-12-1-2015-11-15-t3249416
2. Install FlashFire 0.51 from play store or use the SuperTool
3. Follow the video instructions and instead of the nexus rom use the CM rom you downloaded:
Thanks guys. All going well. CM12 is now installed using that Nexus guide. However, because he used Nexus the Play store was installed by default, which CM12 doesn't have.
Looking here - https://wiki.cyanogenmod.org/w/Google_Apps#Installation - I need to download Google Apps and install it, but which package for the Fire 7 5th gen? There are a number of variants to choose from. Looks like using twrp it would have been a pico one, but as it's a new OS a different one is needed?
So it's ARM device, Android 5.1 and Nano variant?
That gives me a zip file, but I can't work out how to install it. The videos I've found all have it as being installed as part of the OS installation via twrp. Should I have installed gapps when I installed the CM12.1 OS, or can I still install it later?
When I go into the boot menu the only install option is to apply update from ADB, wipe data/factory reset, wipe cache partition, reboot to bootloader or power down/reboot.
I tried to use apply update from ADB and did "adb sideload gapps-filename.zip" but it failed to complete the install and went back to the boot menu.
What do I need to do to get Play Store on there?
Thanks again
Bob Boblaw said:
Thanks guys. All going well. CM12 is now installed using that Nexus guide. However, because he used Nexus the Play store was installed by default, which CM12 doesn't have.
Looking here - https://wiki.cyanogenmod.org/w/Google_Apps#Installation - I need to download Google Apps and install it, but which package for the Fire 7 5th gen? There are a number of variants to choose from. Looks like using twrp it would have been a pico one, but as it's a new OS a different one is needed?
So it's ARM device, Android 5.1 and Nano variant?
That gives me a zip file, but I can't work out how to install it. The videos I've found all have it as being installed as part of the OS installation via twrp. Should I have installed gapps when I installed the CM12.1 OS, or can I still install it later?
When I go into the boot menu the only install option is to apply update from ADB, wipe data/factory reset, wipe cache partition, reboot to bootloader or power down/reboot.
I tried to use apply update from ADB and did "adb sideload gapps-filename.zip" but it failed to complete the install and went back to the boot menu.
What do I need to do to get Play Store on there?
Thanks again
Click to expand...
Click to collapse
Reinstall FlashFire 0.51 (here) on CM 12.1 then use it to flash the GAapps package. Agree with your selection: ARM/5.1/nano.
Ah, great, thank you, yep, that's got it on there.
Excellent! All modded and running very quickly! Thanks for the help guys, I appreciate the patience.
Not much space on these Fire's is there, it's already telling me it's low on space and I've only installed MediaMonkey!
Two more quick questions and I'll leave you alone....!
Is it possible to have the SD card to be used as combined storage? For example, my Shield TV lets me 'add' the SD card to the main storage so it sees it all as one instead of a second removable device, so can install apps on it, etc. If this possible with Cyanogenmod? (Not sure what you'd call that feature to search for it!) Thankfully the main reason I bought it was to help manage my music with MediaMonkey so I won't be installing lots on it, but if it is possible it would be useful.
Second, with regard to OS updates on CM, are they automated or do they need to be done manually (and, if so, with care?)
Thanks again!
Bob Boblaw said:
Two more quick questions and I'll leave you alone....!
Is it possible to have the SD card to be used as combined storage?
Second, with regard to OS updates on CM, are they automated or do they need to be done manually ...
Click to expand...
Click to collapse
Short answer: 'yes'. There are various approaches to utilizing SD cards for app installation/storage each with pros, cons and compromises. I highly recommend using a tool that leverages 'symbolic links' which is by far the most reliable method. An example is Link2SD which you can find in the Play Store.
All custom roms for this device are updated manually via FlaahFire or TWRP (if available). Instructions can usually be found in the OP.
@Bob Boblaw
did you open up the file manager and install the flashfire.apk? I am on the same problem you had on your post #11, but my problem I ran into now is flash fire says "root access could not be acquired" otherwise this would be a easy to do.
I think I might have to reinstall everything and start over. >_<
Yes, I copied it over via USB and installed it from the file manager. Do you have root enabled in the developer settings, I enabled it for adb and apps.
Bob Boblaw said:
Yes, I copied it over via USB and installed it from the file manager. Do you have root enabled in the developer settings, I enabled it for adb and apps.
Click to expand...
Click to collapse
Yes! Thank you, that is what I had missed plus I didn't reboot my device so took like 15mins trying to figure out why it wasn't still working.
Glad you got it working ! :good:
Great post guys!! I am getting ready to root my fire OS 5.1.4 and this helps me greatly! Been searching for a downgrade guide and this is it! Have one question is Cm only recovery program or is there a TWRP version for this ? I would think that lastest TWRP would work since its all android but have to ask .I like TWRP myself cause i have it on rooted tablets
thunderman98 said:
Great post guys!! I am getting ready to root my fire OS 5.1.4 and this helps me greatly! Been searching for a downgrade guide and this is it! Have one question is Cm only recovery program or is there a TWRP version for this ? I would think that lastest TWRP would work since its all android but have to ask .I like TWRP myself cause i have it on rooted tablets
Click to expand...
Click to collapse
You can not boot/install/use twrp on this device unless running FireOS 5.0.1 or lower. Nor can you rollback to any version below 5.1.2 without bricking the device. FlashFire is the tool of choice for installing roms and performing other maintenance tasks that are typically done in a custom recovery environment.
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.
Hi there
First post so apologies in advance for any noob questions.
So I bought a Nook HD+ back in 2013 since my techie mates both had one and I bought one for the ride. From memory we used Cyanogenmod and CM11 or CM 12 I think, and installed an Ovation image. Since then I might have attempted an install of an ovation image from 2016, but have not used it at all. I've recently found the Nook HD+ in my storage boxes and wanted to either flash to the latest version or reset to stock to sell the unit off. However it no longer seems to want to boot up. Can anyone advise why it's not working when it was happily working back in the day, given nothing's been touched of late?
I charged it up and switched it on but it doesn't make it past the loader screen. Any ideas on what I should do to get this working again? Kinda don't want to spend time reloading an image or stuffing around with it as I only plan on offloading it assuming it's working.
I've tried to clear all cache and dalvik and various attempts to reboot. No difference to the outcome - always ends back at the loader screen.
I get a "Root Access possibly lost" message from time to time when trying to reboot. Doesn’t make a difference whether I choose yes or no, it ultimately ends up on that loader screen.
I’ve also tried booting into TWRP but don’t see any options to revert back to stock.
Any thoughts?
Cheers
Ben
benobi37 said:
Hi there
First post so apologies in advance for any noob questions.
So I bought a Nook HD+ back in 2013 since my techie mates both had one and I bought one for the ride. From memory we used Cyanogenmod and CM11 or CM 12 I think, and installed an Ovation image. Since then I might have attempted an install of an ovation image from 2016, but have not used it at all. I've recently found the Nook HD+ in my storage boxes and wanted to either flash to the latest version or reset to stock to sell the unit off. However it no longer seems to want to boot up. Can anyone advise why it's not working when it was happily working back in the day, given nothing's been touched of late?
I charged it up and switched it on but it doesn't make it past the loader screen. Any ideas on what I should do to get this working again? Kinda don't want to spend time reloading an image or stuffing around with it as I only plan on offloading it assuming it's working.
I've tried to clear all cache and dalvik and various attempts to reboot. No difference to the outcome - always ends back at the loader screen.
I get a "Root Access possibly lost" message from time to time when trying to reboot. Doesn’t make a difference whether I choose yes or no, it ultimately ends up on that loader screen.
I’ve also tried booting into TWRP but don’t see any options to revert back to stock.
Any thoughts?
Cheers
Ben
Click to expand...
Click to collapse
Bumping my original post - can someone help please? Cheers, Ben
benobi37 said:
Hi there
First post so apologies in advance for any noob questions.
So I bought a Nook HD+ back in 2013 since my techie mates both had one and I bought one for the ride. From memory we used Cyanogenmod and CM11 or CM 12 I think, and installed an Ovation image. Since then I might have attempted an install of an ovation image from 2016, but have not used it at all. I've recently found the Nook HD+ in my storage boxes and wanted to either flash to the latest version or reset to stock to sell the unit off. However it no longer seems to want to boot up. Can anyone advise why it's not working when it was happily working back in the day, given nothing's been touched of late?
I charged it up and switched it on but it doesn't make it past the loader screen. Any ideas on what I should do to get this working again? Kinda don't want to spend time reloading an image or stuffing around with it as I only plan on offloading it assuming it's working.
I've tried to clear all cache and dalvik and various attempts to reboot. No difference to the outcome - always ends back at the loader screen.
I get a "Root Access possibly lost" message from time to time when trying to reboot. Doesn’t make a difference whether I choose yes or no, it ultimately ends up on that loader screen.
I’ve also tried booting into TWRP but don’t see any options to revert back to stock.
Any thoughts?
Cheers
Ben
Click to expand...
Click to collapse
Hey, one question, are you able to boot into TWRP? If so, you can flash any rom. Also, here is the link for installing stock rom again if you want. https://forum.xda-developers.com/nook-hd/development/stock-nook-hd-nook-hd-2-2-1-2018-update-t3840163 I personally haven't tested it though.
I have an old NVIDIA Shield Tablet K1 that has served me very well since I bought it back in 2016.
Recently it was getting filled up and started to slow down, so I bit the bullet and restored the last factory recovery image.
That went perfectly fine except for one problem. I had zipped up my files prior to the reimage. When I unzip them back to the tablet, they wind up with current dates. This really messes things up.
After doing some searching, it seems that this is a limitation of Android 7. I've read that dates are preserved when copying to internal storage only if the device is rooted on this version of Android.
After doing some searches on rooting, I stumbled upon Magisk. Upon reading the installation instructions at https://topjohnwu.github.io/Magisk/install.html, I came away thinking that it sounds too good to be true. The instructions make it seem like rooting my device will be relatively straight forward.
Can it really be this simple to root? Is un-rooting as simple as flashing the original boot.img? I really don't need to be rooted normally. So after I restore my files with their proper dates I'd be happy to un-root. Unless there is some great things I can do with root that I've never needed to do before.
This latest version of Magisk is very new (just about a week at the time of this writing) so I imagine there hasn't been a lot of use of it on an old device like the K1. But if anyone has any experiences using this new Magisk to root older devices, I'd like to hear about it.
In case any other Shield owner stumbles upon this thread, just a quick follow up to say that it was indeed as simple and straight forward as the Magisk install instructions seemed to indicate.
I successfully rooted the Shield and was able to copy back my files with dates intact.
Now off to see if there is anything else handy that I can do with root!
Can you explain it step by step. I ttied, but nothing happened. I had to put some commands through the console, but the device was not found...I have the driver and everything...
Pudah said:
I have an old NVIDIA Shield Tablet K1 that has served me very well since I bought it back in 2016.
Recently it was getting filled up and started to slow down, so I bit the bullet and restored the last factory recovery image.
That went perfectly fine except for one problem. I had zipped up my files prior to the reimage. When I unzip them back to the tablet, they wind up with current dates. This really messes things up.
After doing some searching, it seems that this is a limitation of Android 7. I've read that dates are preserved when copying to internal storage only if the device is rooted on this version of Android.
After doing some searches on rooting, I stumbled upon Magisk. Upon reading the installation instructions at https://topjohnwu.github.io/Magisk/install.html, I came away thinking that it sounds too good to be true. The instructions make it seem like rooting my device will be relatively straight forward.
Can it really be this simple to root? Is un-rooting as simple as flashing the original boot.img? I really don't need to be rooted normally. So after I restore my files with their proper dates I'd be happy to un-root. Unless there is some great things I can do with root that I've never needed to do before.
This latest version of Magisk is very new (just about a week at the time of this writing) so I imagine there hasn't been a lot of use of it on an old device like the K1. But if anyone has any experiences using this new Magisk to root older devices, I'd like to hear about it.
Click to expand...
Click to collapse
Can you explain it step by step. I ttied, but nothing happened. I had to put some commands through the console, but the device was not found...I have the driver and everything...