Database Develop

[Q] Newbie to Moto X/ Android - 4.4.2 issues

Hi All,
I'm lost, so hope you chaps can help.
Have just purchased a Verizon Moto X developer phone X1060 - its from the USA, I'm in Hong Kong and obviously not using a Verizone sim card - further, I'm a iMac user, so Android is new to say the least to me.
My MX is already "rooted" so want to upgrade to latest 4.4.2, obviously I have to do this via boot loader - big difficulties encountered having download all necessary files and cannot "hard" reboot as getting Andy with Red Triangle - I take it some issue with fast boot or whatever, but after 12 hours effort, absolutely stuck and getting annoyed.
So, time to hit boards and get expert advice me thinks?

I always used OTA updates, but I think that you have to unlock your bootloader, and/or, use RSD LITE like this:
http://forum.xda-developers.com/moto-x/general/guide-moto-x-return-to-100-stock-using-t2446515

Many thanks, but
djlucask said:
I always used OTA updates, but I think that you have to unlock your bootloader, and/or, use RSD LITE like this:
http://forum.xda-developers.com/moto-x/general/guide-moto-x-return-to-100-stock-using-t2446515
Click to expand...
Click to collapse
Thanks for your input, but as I have a developer Moto X from Verizone and am using it with a mobile provider in Hong Kong, I cannot do OTA update, hence struggling, and struggling because I'm on OSX 10.8 and an iMac, most guides being for PC - have managed to crack half the issue, but flashing ROM's is a big pain presently, particularly when using Terminal!

editor1 said:
Thanks for your input, but as I have a developer Moto X from Verizone and am using it with a mobile provider in Hong Kong, I cannot do OTA update, hence struggling, and struggling because I'm on OSX 10.8 and an iMac, most guides being for PC - have managed to crack half the issue, but flashing ROM's is a big pain presently, particularly when using Terminal!
Click to expand...
Click to collapse
Oh i forgot the iMac issue, I never saw tutorials for OSX, maybe the best choice here is to make an Windows VM, or an Linux, that way would be always easy to mod your phone.
Sorry I don't have any other possible solutions for this

Might be easier to read up on how to change the recovery to TWRP (make sure get version 2.7); sounds like you are on the stock recovery still since you get Andy w/ Red Triangle) then use TWRP to flash a rooted, updated rom from the development section. If you are already rooted (not just unlocked) then you can use an app like Recovery manager (?) to flash TWRP while booted into the regular android system.
Or, you can also flash all the update files from the Bootloader using Fastboot. I don't have a MAC, so I don't know if the Motorola Fastboot file is available for Mac though. If you can't use the Motorola fastboot, you will need to use fastboot to flash the TWRP recovery, and then flash the new ROM system image using a ROM zip file in TWRP recovery instead of Bootloader.
Just make sure you are in the Bootloader when you try and use fastboot, not in the Factory Recovery. I believe the Andy icon indicates you are in the Factory Recovery.
One other tip: when in bootloader, the "volume up" key is the "enter" key to select the option that is highlighted (not the power key like other Android devices I have used).
When you flash TWRP, DON"T reboot, instead, use the bootloader option to boot to recovery directly (without rebooting).
Once you have a custom recovery, and have root, you won't ever need to worry about working on a Mac instead of PC.

jasoraso said:
Might be easier to read up on how to change the recovery to TWRP (make sure get version 2.7); sounds like you are on the stock recovery still since you get Andy w/ Red Triangle) then use TWRP to flash a rooted, updated rom from the development section. If you are already rooted (not just unlocked) then you can use an app like Recovery manager (?) to flash TWRP while booted into the regular android system.
Or, you can also flash all the update files from the Bootloader using Fastboot. I don't have a MAC, so I don't know if the Motorola Fastboot file is available for Mac though. If you can't use the Motorola fastboot, you will need to use fastboot to flash the TWRP recovery, and then flash the new ROM system image using a ROM zip file in TWRP recovery instead of Bootloader.
Just make sure you are in the Bootloader when you try and use fastboot, not in the Factory Recovery. I believe the Andy icon indicates you are in the Factory Recovery.
One other tip: when in bootloader, the "volume up" key is the "enter" key to select the option that is highlighted (not the power key like other Android devices I have used).
When you flash TWRP, DON"T reboot, instead, use the bootloader option to boot to recovery directly (without rebooting).
Once you have a custom recovery, and have root, you won't ever need to worry about working on a Mac instead of PC.
Click to expand...
Click to collapse
Thanks for info, I've managed to setup fast boot, its the actual flashing of the ROM via Terminal that's confusing to say the least - basically, in Mac terminal necessary to change inputting details associated with rooting instructions found on PC - side of the equation, hence why I'm stuck. Would be easier to get someone with a PC laptop to lend a hand, most don't do custom jobs on Android though, so, will have to figure it out myself and then hopefully render help to others.

Republic Wireless Moto X Moto G Discount Code Link URL
$25 Republic Wireless credit at checkout with purchase of your phone using this discount link

editor1 said:
Thanks for info, I've managed to setup fast boot, its the actual flashing of the ROM via Terminal that's confusing to say the least - basically, in Mac terminal necessary to change inputting details associated with rooting instructions found on PC - side of the equation, hence why I'm stuck. Would be easier to get someone with a PC laptop to lend a hand, most don't do custom jobs on Android though, so, will have to figure it out myself and then hopefully render help to others.
Click to expand...
Click to collapse
Have you tried this?
Toolkit for Mac OS under development...
Sent from my XT1060 using Tapatalk 2

imparables said:
Have you tried this?
Toolkit for Mac OS under development...
Sent from my XT1060 using Tapatalk 2
Click to expand...
Click to collapse
Thanks for info, I've not tried Toolkit, or heard of it - any links to assist with this?
Basically, you are going to see more Mac users adopt Android over the coming months, and many like me suffer in an all OSX environment when playing about with PC-structured advice - shame I never adopted a duel boot system on my mac, but its always been for DTP, hence always happy with Adobe in Mac.

Now upgraded to 4.4.2
editor1 said:
Thanks for info, I've not tried Toolkit, or heard of it - any links to assist with this?
Basically, you are going to see more Mac users adopt Android over the coming months, and many like me suffer in an all OSX environment when playing about with PC-structured advice - shame I never adopted a duel boot system on my mac, but its always been for DTP, hence always happy with Adobe in Mac.
Click to expand...
Click to collapse
Thanks for the input, after two days of hell, I'm now fully upgraded to KitKat 4.4.2, my Moto X1060 Dev phone is working as it should be, I've unlocked it, am able to do side-loading, have TWRP installed - a bigger pain as caused a continually boot loop, erased, re-installed all from Moto and re-cracked it.
So it works, and I did all this on a iMac and in terminal, which I don't often use!
Not bad for someone fast approaching 50 - and yes, this is a kids game I'm afraid to say.

[Q] Need Help Unlocking Bootloader/Installing CM

I tried to unlock my bootloader, following various guides, and kept getting stuck on the "Download Mode !!!" part. I just want to install the latest stable version of Cyanogenmod on my phone since the stock ROM is being a real pain for me (very slow and unresponsive).
I have:
Android 4.1.2
Build Number: JZ054K
Software Version: AME-XXX
I read online that you need the Euro firmware to unlock the bootloader, can I flash the euro firmware and will it mess with my service? I'm confused as to how the firmware affects things since I've read conflicting information. I didn't flash my firmware a few hours before trying to unlock, so maybe that's the problem?

Seriously?
There aren't enough threads and guides for you to read already? Everything you need is already out there on this forum so why start another thread just because you are too lazy to search and read for yourself?

I have read around and have tried a number of guides a number of times. They haven't worked for me and I'm just wondering what i'm doing wrong. Even though all the information is out there, I don't have the experience to understand it apparently. I've spent hours trying to figure things out but i keep reading conflicting info and half-explained steps and now I'm just confused and would like a clear point in the right direction.
So, do i need to reflash the latest firmware, wait a few hours, then try again on a full charge? Or do i need a euro firmware? Which guide should i follow?
I've downloaded a few applications and driver packages and whatnot but if those could possibly conflict with each other and cause problems i could work with a fresh OS. I'm running OS X but i have linux VMs and friends with clean windows installs (mine is all sorts of messed up)

eatfoodnow said:
I tried to unlock my bootloader, following various guides, and kept getting stuck on the "Download Mode !!!" part. I just want to install the latest stable version of Cyanogenmod on my phone since the stock ROM is being a real pain for me (very slow and unresponsive).
I have:
Android 4.1.2
Build Number: JZ054K
Software Version: AME-XXX
I read online that you need the Euro firmware to unlock the bootloader, can I flash the euro firmware and will it mess with my service? I'm confused as to how the firmware affects things since I've read conflicting information. I didn't flash my firmware a few hours before trying to unlock, so maybe that's the problem?
Click to expand...
Click to collapse
It isn't a question of firmware, the phone needs to have an unlockable bootloader to be able to be, well, unlocked. Here is a list http://forum.xda-developers.com/showthread.php?t=2181581 of P880 bootloader versions. Follow the guide to check which BL your phone has.

Thats obsolete, all versions can be unlocked afaik, either with official method or by fuse editing. No need to keep sim card in,you just need proper drivers

Oh, OK, I didn't know that. But, even better, OP should not have any trouble, provided he follows the BL unlock guide here http://forum.xda-developers.com/showthread.php?t=2224020
Maybe his BL is already unlocked OR is relocked (meaning can't be unlocked anymore).

Its more likely that his drivers are messed up imo.
The fuse editing method should work for everyone, i recommend you give it a try

So the fuse method would be the "BL-unlock.bat" method on that bootloader unlock forum post? I've tried it before, but I'll try it again. The directions only say to run it, is there anything else I need? Now, since it's a .bat file I absolutely have to run it on Windows, right? Because if so I'll use a friend's computer instead of my windows installation.
What are the necessary installations before I run the file? How should I configure settings on my phone? (like what type of usb connection should it be)
There are a lot of things that people expect readers to know but I'm really not very knowledgeable about standard practices for phone stuff so I really need every step. Thanks for helping!

Since its.bat file, you can open it in text editor to see which commands it executes. I'd still recommend to do it on windows machine, other OSs may work but aren't tested.
You need abd & fastboot drivers, plus drivers for our device. It's been a while since I've done it, but afaik you can get proper device drivers via lg support tool.

Flying_Bear said:
Since its.bat file, you can open it in text editor to see which commands it executes. I'd still recommend to do it on windows machine, other OSs may work but aren't tested.
You need abd & fastboot drivers, plus drivers for our device. It's been a while since I've done it, but afaik you can get proper device drivers via lg support tool.
Click to expand...
Click to collapse
Also, correct me if i'm wrong I only had stock for 2hours, but also stock needs usb debugging to be enabled or adb won't work?

Yep, afaik usb debugging needs to be enabled

When you are fast enough, it is possible in charging mode wihle the carger animation is shown. But you have install adb driver very fast...

So I'm pretty sure I got the bootloader unlocked, I ran the .bat file and it went through everything until the part where it checks to see if my bootloader is unlocked, it just froze forever, so I closed it.
How should I go about checking?
Also, what would be my next step now for installing CM10.1.3? I tried to follow the guide on the cyanogenmod wiki (install_CM_for_p880) (I can't post links yet)
...but ran into problems with pushing it into root with adb. It said I didn't have permissions, so I googled some stuff, but just got myself confused.
Thanks for all the help btw!

eatfoodnow said:
So I'm pretty sure I got the bootloader unlocked, I ran the .bat file and it went through everything until the part where it checks to see if my bootloader is unlocked, it just froze forever, so I closed it.
How should I go about checking?
Also, what would be my next step now for installing CM10.1.3? I tried to follow the guide on the cyanogenmod wiki (install_CM_for_p880) (I can't post links yet)
...but ran into problems with pushing it into root with adb. It said I didn't have permissions, so I googled some stuff, but just got myself confused.
Thanks for all the help btw!
Click to expand...
Click to collapse
you can check your bl status by entering sw mode (phone off, hold vol+ and insert charger) or reeboting into bl (adb reboot oem-unlock)
to install cm steps are:
-install recovery (you can choose either cwm or twrp, it's more about looks than functions)
-download rom zip onto sd card
-install said zip from said recovery, there's no adb involved
Now my personal opinion, I really don't see the point in flashing 10.1, i would go staright for cm11 if i were you

Ok well I think I got things together more or less, eventually I tried to install CM10.1 with the ROM manager app. I forgot to select the options to wipe my data partitions and now I'm stuck in an endless boot loop every time I turn the phone on. I tried to boot from my backup using CWM which I made with the app prior to trying to install, and it gave me an error about an MD5 checksum failing, no matter what I tried. Should I do the factory reset/wipe option with CWM now? What's my best option.
Also why would you recommend CM11 over CM10.1? I don't want to have to deal with a nightly, all this phone stuff is a supreme headache to me.

eatfoodnow said:
Ok well I think I got things together more or less, eventually I tried to install CM10.1 with the ROM manager app. I forgot to select the options to wipe my data partitions and now I'm stuck in an endless boot loop every time I turn the phone on. I tried to boot from my backup using CWM which I made with the app prior to trying to install, and it gave me an error about an MD5 checksum failing, no matter what I tried. Should I do the factory reset/wipe option with CWM now? What's my best option.
Also why would you recommend CM11 over CM10.1? I don't want to have to deal with a nightly, all this phone stuff is a supreme headache to me.
Click to expand...
Click to collapse
Factory reset then get nandroid manager app and see if you can restore your stuff with that
CM11 is bugless atm and performance (imo) is way superior

So after a factory reset/data wipe, my phone just booted into CM10.1 and now that's working. And it looks like all of my stuff on the phone is still there (though of course apps aren't installed and whatnot, that wouldn't make sense). Thanks for all the help!
I tried to find a feature list or something to see what exactly is better about CM11, and found out that "stable" doesn't exactly mean stable for CM, and that it looks like a good idea to update, so I think I will try to update to that. Do you know anywhere that has an actual feature list to show me what CM11 does that CM10.1 doesn't?

How to Root my N6 w/o PC?

Hello XDA forums,
I really don't like the issue of trying to set the drivers of fastboot/google and so on....also all of these adb commands.
Is there a way to unlock bootloader & root by:
1) one of these "1 click" tools that do everything for the use? (such as "wugfresh Nexus Root Toolkit")
2) Just do everything by the phone? (if there is a possible to install some how a recovery such as twrp and than root by some app?)
Could anybody guide me through the steps, if needed?
Many thanks!

shabydog said:
Hello XDA forums,
I really don't like the issue of trying to set the drivers of fastboot/google and so on....also all of these adb commands.
Is there a way to unlock bootloader & root by:
1) one of these "1 click" tools that do everything for the use? (such as "wugfresh Nexus Root Toolkit")
2) Just do everything by the phone? (if there is a possible to install some how a recovery such as twrp and than root by some app?)
Could anybody guide me through the steps, if needed?
Many thanks!
Click to expand...
Click to collapse
AFAIK you will need a pc to 1)unlock your bootloader and 2)flash TWRP. After that the rest can be done locally. I also never used any toolkit. Making it easy is making it more dangerous IMHO.

Droidphilev said:
I also never used any toolkit. Making it easy is making it more dangerous IMHO.
Click to expand...
Click to collapse
Second that.
shabydog said:
2) Just do everything by the phone? (if there is a possible to install some how a recovery such as twrp and than root by some app?)
Click to expand...
Click to collapse
So at least once you need to connect your phone to a desktop computer. It can be practically running anything, within reason of course: Wiindows. Mac OSX, Linux (almost any distro).
You need to unlock your bootloader with one command, but a warning here: Unlocking the bootloader will erase everything from your phone..
Then you need to install a custom recovery, preferably TWRP. After that everything can be done from the phone itself. Well at least until you soft brick it somehow, then you'll might have to use the PC again.
Also two things:
1. No OTAs for rooted phones
2. Don't lock your bootloader if you want to mess with it, because with a locked bootloader, and Enable OEM Unlocking set to off, and without TWRP, if you soft brick it accidentally, you are boned.

Hello XDA forums,
I really don't like the issue of trying to set the drivers of fastboot/google and so on.
Is there a way to unlock bootloader & root by:
1) one of these "1 click" tools that do everything for the use?
2) Just do everything by the phone? (if there is a possible to install some how a recovery such as twrp and than root by some app?)
Could anybody guide me through the steps, if needed?
And i really prefer to do it on the device and not by ADB commands.
@istperson
I dont want to mess with th BL ... only for installing dev roms (or later then the stock with root).
Many thanks!

shabydog said:
@istperson
I dont want to mess with th BL ... only for installing dev roms (or later then the stock with root).
Many thanks!
Click to expand...
Click to collapse
Well, you still will have to unlock it, if you want root, or want to flash a custom recovery.
Sent from my Nexus 6 running cyosp using Tapatalk

shabydog said:
......I really don't like the issue of trying to set the drivers of fastboot/google and so on!
Click to expand...
Click to collapse
Than do not 'root' your phone.

hi xda.. i want to root my phone but dont want to touch it. is there a way to root my n6 without touching it? :silly:

simms22 said:
hi xda.. i want to root my phone but dont want to touch it. is there a way to root my n6 without touching it? :silly:
Click to expand...
Click to collapse
Ha ha, or I don't want my birthday to be on the day I was born every year ?

I can recommend the NTRT, the Nexus Telepathic Rooting Tools.

OK.
I want to do that with a toolkit, only bcs it install the drivers.
What Is the most recommended and easiest to use?
I do looking for the 1 click do all.
Does NTRT do that?
Thank you all.

we are eventually goung to have a "my n6 is bricked, how do i fix it with one click" thread here. seriously though, thats what happens when you use toolkits, but do no real research about modding your device.

Toolkits are fine if you first understand what they are doing. Otherwise it's like giving a hand grenade to a child to play with.
Sent from my Nexus 6 using Tapatalk

shabydog said:
Could anybody guide me through the steps, if needed?
Click to expand...
Click to collapse
<prev> step <next>

simms22 said:
seriously though, thats what happens when you use toolkits, but do no real research about modding your device.
Click to expand...
Click to collapse
I seriously belive that if a user know exactly for to chose and click - yes it could be great.
wtherrell said:
Toolkits are fine if you first understand what they are doing. Otherwise it's like giving a hand grenade to a child to play with.
Click to expand...
Click to collapse
It is fairly enough to read directions and slowly-slowly.
NLBeev said:
<prev> step <next>
Click to expand...
Click to collapse
Thanks!
==========================================================
Bottom line:
Guess many users completed the unlocking & rooting by this tool
Why not?

shabydog said:
I seriously belive that if a user know exactly for to chose and click - yes it could be great.
Click to expand...
Click to collapse
i agree with you. if there is somebody who knows the ins and outs already, a one click root would be great. and there will be. problem is that marshmallow just came out, and a few things have changed, like like yoe also need a custom kernel to have root on marshmallow.

shabydog said:
I seriously belive that if a user know exactly for to chose and click - yes it could be great.
It is fairly enough to read directions and slowly-slowly.
Bottom line:
Guess many users completed the unlocking & rooting by this tool
Why not?
Click to expand...
Click to collapse
There is a reason you're pushing this topic, and I'm quite sure it's because you would feel safer, if there was a tool that did the scary things instead of you. Well, there's no such tool. If you were willing to search XDA, you would find out that the first two weeks after Marshmallow came out were about people bricking their Nexus 6s with toolkits. Then the toolkit got updated and suddenly it knew that is has to flash a modified boot.img too for the root not to brick the phone. But for two weeks it didn't know, because it wasn't necessary for Lollipop. And it will only work until the next security update comes out. And that's once a month.
Meanwhile those who were willing to use the search function, and learned the five minute procedure, were able to update their rooted phones to the next security update and were able to root it as soon as the new modified boot image came out.
And this above is not something somebody will put in a help, or instructions for future updates.

Actually, this is my first time and I was able to do it pretty easily.
fastboot devices
fastboot oem unlock
my bootloader was unlocked within 30 seconds of turning it on.
then, you can easily root via CF Auto root. Just put it into fastboot then doubleclick on the windows, then root, etc....
or.............go into fastboot flash recovery twrpxxxx.img, then it always offers to run SuperSU, and you get custom recovery and root at the same time, etc......
actually the biggest pain is unlocking the bootloader. My Galaxy S4 already was unlocked, so all I did was use goomanager, flash TWRP which always offers to run SuperSU if you don't have it.
Pretty easy, I did unlock bootloader, root, and custom recovery in 10 min.
---------- Post added at 01:48 AM ---------- Previous post was at 01:44 AM ----------
............................Then I got sick of stock Google's ROM in 15 min and wiped it and put a custom ROM instead.

Thank you all so much...
@mikeprius
Thank you so much for the info'!
But, could you plz write more details? such as:
1. How did you installed the drivers? (from my expirience, many times the pc dosent install this easily).
I just need the Google oem driver and that's it?
2. When drivers was set - did you made anything in your phones settings? Which?
3. What did you had to do before pushing the files? (Like...put all the files in the same folder? *which files?)
4. And then entered to fastboot mode and typed in these commands in pc:
fastboot devices
fastboot oem unlock
Regarding your last sentence ("or...."):
If i just flash the recovery via fastbot mode I can enter to twrp recovery and it offers to flash the SuperSU?
Sounds to me the best option.
Thanks!

1. The drivers were set from a previous device, so I didn't have to set them, but they can be downloaded and set though.
2. You need to enable developer options and select OEM unlock and USB debugging.
3. I didn't push the files, I just had them on my computer and ran fastboot commands.
4. Those commands are to unlock the bootloader.
There are a lot of different ways to do the same thing (Root, custom recovery, unlock bootloader)
1. Run CF Auto Root on a locked bootloader. It will unlock it automatically (Chainfire has it set that way), root, then download Flashify app and flash the latest img of TWRP.
2. Run fastboot commands to manually unlock the bootloader, flash TWRP, then use TWRP's SuperSU which will root it.
3. Run fastboot commands to unlock bootloader, run CF Autoroot which will root and load SuperSU, then flash TWRP via Flashify or fastboot.
There are many different ways to do the same thing. I actually just googled youtube videos and watched them.
TWRP has SuperSU and root built in. TWRP knows if you don't have it and offers to load it for you.
I went the scenic route just because, but presumably you can achieve all (3) using Option #1 without having to deal with fastboot, adb, etc.....Chainfire's script runs automatically.

I realy try to help people but users that run into problems because of the usage of tookits (and innability to solve problems and/or even lack the most basic knowledge needed) should ask the toolkit dev. for support imo, and not boughter users that have invested time and effort to gain that knowledge to clean up their mess. Period

I've just gotten the phone and am confused as hell

(stock firmware)
1) How do I enter recovery mode? I need to install Xposed and I can't figure out how to boot into this.
2) Why is the advanced reboot disabled? I went through all of the developer options and it's just not there :-O

Root?
You did root your phone?

WalrusInAnus said:
(stock firmware)
1) How do I enter recovery mode? I need to install Xposed and I can't figure out how to boot into this.
2) Why is the advanced reboot disabled? I went through all of the developer options and it's just not there :-O
Click to expand...
Click to collapse
The XZ's are nothing like any Sony phone before. Sony have given developers the finger with this boot partition, You can't just Root you phone any more. Unlocking your phone destroys a partiton and the DRM keys are gone forever. The good news is that there's a fix that fools the phone into thinking the keys are still present.
Yes it's possible to load recovery and exposed. You need to unlock the phone first, then (retro)flash .75 firmware, as that is the only one that works with Xposed. Then I would use Xperiafix to mount TWRP and Magisk and the drm fix. Once Magisk is installed you can use the Xposed Magisk module.
It's a long complicated road compared to the old phones and having done it, I'd say the advantages are not worh the effort.

Oh ****, what the hell It's the only higher end compact phone out there, so there's no alternative for me.
I already unlocked the bootloader and now my camera is ****ed, and apparently it's impossible to relock it.
Unfortunately I don't understand anything you wrote in your post. I've dealt with Samsung phones until now and that's piss easy.
What does "mount twrp" mean? What is Magisk?
I managed to install TWRP but it asks for a password, so I think something went tits up there.

WalrusInAnus said:
I think something went tits up there.
Click to expand...
Click to collapse
Read the Xperiafix thread, this will help you find the drivers you need to connect to the phone via ADB. (Hint: Google ADB drivers). Geting the drivers to work with your phone is fiddly because a) Windows10 lies to you when it says it's installed the drivers and b) Windows then chooses the wrong drivers when you plug your phone (running twrp) in.
Buy Xperiafix. Yes there are free versions to be found but getting everything to work is fiddly as f*ck and I'm going to guess you want the easy option.
Install the drivers, follow instuctions on Xperiafix, easy.
Your TWRP is asking for the pin number you set to unlock your phone.

Confusion About Best Root Method For Fire 7 Tablet (9th generation)

Hello,
I recently purchased a Fire 7 tablet and have a question about rooting it. Currently my tablet has the following out of the box:
- Fire 7 (9th generation)
- Build number = 0002517050244
- Fire OS = 6.3.1.2
After reading many of the posts on XDA, I am confused how to do root. Here are the following posts that talk about root for the Fire 7:
- https://forum.xda-developers.com/amazon-fire/general/fireos-6-3-1-0-amazon-fire-7-2019-t3937209
- https://forum.xda-developers.com/am...ire-7-2019-mustang-unbrick-downgrade-t3944365
- https://forum.xda-developers.com/amazon-fire/development/unlock-fire-t3899860
- https://forum.xda-developers.com/an...atek-armv8-t3922213/post79626434#post79626434
Which is the best recommended method to root? I don't think I need to install a custom ROM, unless it turns out I need to install a de-bloated stock version.
Thanks in advance!

Software method here (good up to 6.3.1.2) and most recent.
https://forum.xda-developers.com/am...ire-7-2019-mustang-unbrick-downgrade-t3944365

Michajin said:
Software method here (good up to 6.3.1.2) and most recent.
https://forum.xda-developers.com/am...ire-7-2019-mustang-unbrick-downgrade-t3944365
Click to expand...
Click to collapse
Thank you... that's what I figured. I'll let everyone know my results.

After much tinkering around, I finally got it to root (or at least I think I did). A couple of things:
- How do I confirm whether I actually have root?
- After following the instructions, what should the next steps be? Should I upgrade the software OTA? I remember reading something about possibly disabling OTA, but I can't remember if this applies?

gil_happy said:
After much tinkering around, I finally got it to root (or at least I think I did). A couple of things:
- How do I confirm whether I actually have root?
- After following the instructions, what should the next steps be? Should I upgrade the software OTA? I remember reading something about possibly disabling OTA, but I can't remember if this applies?
Click to expand...
Click to collapse
Hi, any comments on this? Since my Wifi has been disabled the entire time, I don't want to enable it until I know whether I need to disable updates. I don't know if the Fire 7 will automatically try to do an update and break root, etc. Secondly, how do I tell if I have root (keeping in mind that Wifi is still disabled)?
Thanks!

gil_happy said:
Hi, any comments on this? Since my Wifi has been disabled the entire time, I don't want to enable it until I know whether I need to disable updates. I don't know if the Fire 7 will automatically try to do an update and break root, etc. Secondly, how do I tell if I have root (keeping in mind that Wifi is still disabled)?
Thanks!
Click to expand...
Click to collapse
Did you make it through both the bootrom-step and the fastboot-step? Can you boot into TWRP? I would recommend changing to lineage if android is your flavor. You can install a root checker, but if you followed the steps, you should have magisk installed (magisk is a root manager). What exactly are you looking to do with the tablet?

gil_happy said:
After much tinkering around, I finally got it to root (or at least I think I did). A couple of things:
- How do I confirm whether I actually have root?
- After following the instructions, what should the next steps be? Should I upgrade the software OTA? I remember reading something about possibly disabling OTA, but I can't remember if this applies?
Click to expand...
Click to collapse
Michajin said:
Did you make it through both the bootrom-step and the fastboot-step? Can you boot into TWRP? I would recommend changing to lineage if android is your flavor. You can install a root checker, but if you followed the steps, you should have magisk installed (magisk is a root manager). What exactly are you looking to do with the tablet?
Click to expand...
Click to collapse
Thanks so much for getting back to me. As far as making it through the bootrom-step and the fastboot-step, I think I successfully completed both steps as I can boot into TWRP (I assume booting in TWRP means successfully completing both steps?). A couple of things:
- As mentioned, I can boot into TWRP no problem. I can also see that Magisk is also installed (when I click on Magisk, it looks like it is attempting to access the Internet for updates).
- My Fire 7 currently has Fire OS = 6.3.1.2, but after what I think is the completed install, I still have not turned on the Wifi as I'm worried that something (including the OS) might auto-update and break something, e.g. root. That is why I was asking if OTA needs to be disabled?
- As far as my plans for my tablet, here is my original post (https://forum.xda-developers.com/amazon-fire/help/customize-fire-7-tablet-t4112223), but essentially we would like to use these for promotional purposes. To explain, I want to sent out a tablet to a potential client via mail, and when they power up the tablet, our logo will replace the Amazon / Fire logo (root is needed for that), then after it boots up, it boots right to a screen where there is a some type of product messaging (maybe with a graphic), and then a button that basically says 'press here to watch our video'. It really doesn't even need access to the internet.
Hopefully all of this makes sense?

gil_happy said:
Thanks so much for getting back to me. As far as making it through the bootrom-step and the fastboot-step, I think I successfully completed both steps as I can boot into TWRP (I assume booting in TWRP means successfully completing both steps?). A couple of things:
- As mentioned, I can boot into TWRP no problem. I can also see that Magisk is also installed (when I click on Magisk, it looks like it is attempting to access the Internet for updates).
- My Fire 7 currently has Fire OS = 6.3.1.2, but after what I think is the completed install, I still have not turned on the Wifi as I'm worried that something (including the OS) might auto-update and break something, e.g. root. That is why I was asking if OTA needs to be disabled?
- As far as my plans for my tablet, here is my original post (https://forum.xda-developers.com/amazon-fire/help/customize-fire-7-tablet-t4112223), but essentially we would like to use these for promotional purposes. To explain, I want to sent out a tablet to a potential client via mail, and when they power up the tablet, our logo will replace the Amazon / Fire logo (root is needed for that), then after it boots up, it boots right to a screen where there is a some type of product messaging (maybe with a graphic), and then a button that basically says 'press here to watch our video'. It really doesn't even need access to the internet.
Hopefully all of this makes sense?
Click to expand...
Click to collapse
You should be able to disable OTA with renaming this app,
/system/priv-app/DeviceSoftwareOTA/DeviceSoftwareOTA.apk
Also a package disabler will work.
I have had sucess with
adb shell
$ su
# pm disable com.amazon.device.software.ota
Or
#pm uninstall com.amazon.device.software.ota
There are a few ways...
Easy to check, do one of these OTA disables connect wifi, check for updates. If you see it downloading, turn wifi back off. If it just closes, or says error, then OTA's are disabled. You might lose root, if you take an udpate, but TWRP should be safe. Make a backup in twrp to go back to what you have now.

Michajin said:
You should be able to disable OTA with renaming this app,
/system/priv-app/DeviceSoftwareOTA/DeviceSoftwareOTA.apk
Also a package disabler will work.
I have had sucess with
adb shell
$ su
# pm disable com.amazon.device.software.ota
Or
#pm uninstall com.amazon.device.software.ota
There are a few ways...
Easy to check, do one of these OTA disables connect wifi, check for updates. If you see it downloading, turn wifi back off. If it just closes, or says error, then OTA's are disabled. You might lose root, if you take an udpate, but TWRP should be safe. Make a backup in twrp to go back to what you have now.
Click to expand...
Click to collapse
Thanks so much for this! I didn't see anything with the name *.software.ota in that directory. The closest thing I saw was com.amazon.device.sync and sync.sdk.internal. Of course now when I try to boot up my Fire after attempting to reboot it using the touch screen, now my tablet doesn't power up :-/ I was doing so many things trying to get into the shell, I don't fully know what I'm doing. However, when this happened last time, I need to open the tablet, disconnect the battery, and then do some of the shell commands.

gil_happy said:
Thanks so much for this! I didn't see anything with the name *.software.ota in that directory. The closest thing I saw was com.amazon.device.sync and sync.sdk.internal. Of course now when I try to boot up my Fire after attempting to reboot it using the touch screen, now my tablet doesn't power up :-/ I was doing so many things trying to get into the shell, I don't fully know what I'm doing. However, when this happened last time, I need to open the tablet, disconnect the battery, and then do some of the shell commands.
Click to expand...
Click to collapse
Well if you cant find the ota the re-rename method, dont rename the other ones. I have always used disable
adb pm disable com.amazon.device.software.ota
Did you make a back up prior to doing anything as i suggested? What kind of things were you doing to try to get in a shell?
"Make a backup in twrp to go back to what you have now."