yashsingh1/xdaforums huggingface dataset:
[Fire Android Development] Chewieez:
Hello,

first off, thank you so much for this tool and the tutorial. It took me a while, being a Mac guy, to get the adb and fastboot working on my old xp laptop. I finally figured that out and quickly gained root and blocked OTA updates.

After all that I tried to Remove Ads from lockscreen and the script ran but after it went into fastboot and I hit "any key", it gives me an error and says:

[*] removing ads now, then very quickly says "Error: Could not access the Package Manager. Is the system running?" It gives that error before the system has rebooted. Maybe the script isn't waiting long enough for the reboot to happen? I ran it twice and got the same error in the same manner. Any ideas?

I've also seen this error frequently while gaining root and OTA block: " 'timeout' is not recognized as an internal or external command, operable program or batch file."

Thanks!

Edit: I searched "offers" in titanium backup and froze the app and it looks like the lockscreen ads are gone.
[Fire Android Development] wulfie66:
you can also just install a custom rom ;)
[Fire Android Development] m00head:
I answered this question in another thread (here):
[Fire Android Development] wulfie66:
as m00rhead stated, it's easier to just enable root access in developer options
[Fire Android Development] mickyc59:
I am still scratching my head on this rooting

My device is showing up in my devices ,pc - driver updated to , Android Composite ADB , come out of there opened command prompt.

typed in : adb kill-server , Enter / then typed in : adb devices , Enter

I got / code Device in this order , so i presume everything is correct

Used supertool

1 amazon -Fire -5th - Gen root file

entered 7 root once open + Enter / entered 2 next 5.1.1 + Enter

Kindle went into fastboot black screen bottom corner / pressed enter to inject root files

Adb out of date killing

I am at a loss ?

The device is there and showing up in cmd , I have tried in the middle of the process to update drivers whilst in fastboot to see if this helped but that didn't work.

Still showing adb out of date kill server

Also tried unplugging kindle while in the process of root and plug back in again but that failed still cannot get past injecting files ?.

Any help cheers mike.
[Fire Android Development] platypoid:
Not sure if this is your issue but recently I had sort of same thing happen with an HTC phone - showed up in ADB but Fastboot wouldn't work. I did a lot of reading and found that ADB and Fastboot drivers are different. Just a thought - my Fire is due to be here soon so I can give it a try ! Hope you figure yours out soon.
[Fire Android Development] wulfie66:
sounds like you're using the old supertool, the 7 option is 'change stock launcher to nova launcher or back'

make sure you get the latest version from rootjunkysdl.com and choose option 1 to 'adb and fastboot driver install plus test'.

when you first run supertool, it should start adb and show your attached devices, as long as your serial is listed and it says 'device', you 'should' be g2g
[Fire Android Development] mickyc59:
Thanks for reply , platypoid

Its going into fastboot but / when press enter for injecting files to take it to next phase its adb out of date killing , driving me nuts , lol

;)
[Fire Android Development] DB126:
Generic guidance (never used the Supertool)

- boot to FireOS

- open Windows device manager

- tether device and observe which entries are added

- uninstall those devices

- disconnect tether

- boot into fastboot

- repeat steps 2-4

- untether and reboot both devices

- follow Supertool instructions; should install what it needs

Best practice:

- connect only to native usb ports on host; avoid hubs

- use only USB2 ports if possible; some older USB3 ports are flaky

- try a different USB cable (amazing how many times this works)

- 64-bit Win 8/10 can sometimes block (unsigned) driver installs; try a different host
[Fire Android Development] itsmerts:
switch launcher

I can't seem to find an answer to this. After using the tool (worked 100% on 5.1.1) i dont see an option to switch from nova launcher to google launcher. Can I replace the nova launcher apk in the apps folder with the ggole.apk? Any help is appreciated.

Thanks in advance.
[Fire Android Development] wulfie66:
make sure you have the latest version of the supertool from rootjunky's website, connect your fire tablet and ensure that adb is enabled and choose option 7 which says 'change stock launcher to nova launcher or back'
[Fire Android Development] supernaut25:
I actually want to switch back to the stock launcher and the SuperTool just won't complete the process. It keeps saying it can't find the file, even though I see it in the SuperTool folder, and even says it completes successfully. Kinda wish I had never switched it as I hate the way Android looks and wanted the Fire because it looked much cleaner.

What am I doing wrong here? I should note that when I originally rooted, my SD Card had not arrived in the mail, so I didn't have one in the tablet when I rooted with SuperTool.
[Fire Android Development] wulfie66:
if you actually open the supertool bat file in notepad, you can 'search' for 'nova' and you'll see the shell commands to use via adb to push the proper files and chmod them, etc. the script also backs up nova launcher to the sdcard, you can either change the path in the bat file or just comment that line out
[Fire Android Development] itsmerts:
launcher follow up ?

Thank you so much, Im going to try that. As a follow up question, will option 7 only allow the stock launcher and or nova launcher? I really want to try the google launcher.

Thanks again.
[Fire Android Development] jlv3:
I picked one of these up yesterday at Best Buy (5.0.1) and used rootjunky's SuperTool to successfully rooted it, blocked OTA, took off the lockscreen ads, installed the Play Store, and finally switched to Nova Launcher. It all went pretty easy!

Then I decided to switch back from Nova to Amazon's stock launcher. That's when things started to not work well. When it rebooted the table the last time, it got stuck just displaying "fire". I eventually powered off and rebooted to the bootloader (I could only adb sideload at that point). I read that I could get into fastboot by powering on with the factory cable, so I powered off and did that, but it didn't go to fastboot. This time it went to the "fire" screen and said "Installing the latest software". This took about 10 minutes and when it came up, it had no launcher -- but I could use the recent apps button to bring up any I'd previously run and from the nav bar I could open settings. I reran the SuperTool and had it reinstall the stock launcher (and I checked in Solid Explorer and via an adb shell that it was there). I let it reboot the table again and now it gets to the "fire" screen with "Unstalling the latest software", and gets to 100% on the progress bar, and then does nothing else. If I plug it in, "adb devices" does not list it.

(in case it matters: I blocked it on my firewall from getting Internet access)

So I'm stuck now. Any suggestions before I try to restore the rom via something like http://xdaforums.com/amazon-fire/general/unbrick-restore-stock-2015-amazon-fire-t3250639?

---------- Post added at 05:49 PM ---------- Previous post was at 05:42 PM ----------

FWIW, after about 15 minutes it does show up in 'adb devices' and I can get a shell. It is still on the "installing latest software" screen

shell@ford:/ $ cd /system/priv-app/com.amazon.firelauncher
cd /system/priv-app/com.amazon.firelauncher
shell@ford:/system/priv-app/com.amazon.firelauncher $ ls -l
ls -l
-rw-rw---- root root 6183467 2016-02-14 16:54 com.amazon.firelauncher.apk

Those permissions don't look right (they don't match what was in the bat file).
[Fire Android Development] jlv3:
I just reinstalled Nova and it's working again. I'll probably just leave it this way (the reason I was switching back was to try out the switch-to-Amazon launcher at http://xdaforums.com/fire-hd/general/fireos-4-5-x-root-quickly-switch-to-t3145613).
[Fire Android Development] ranagard:
searched through the threads and couldn't seem to find an answer. i followed the instructions but for some reason the default email app does not work/open. is this normal?
[Fire Android Development] platypoid:
Would not root - but found problem .

I had all kinds of problems getting this to root. First it would go to Fastboot but get stuck there. I think I finally installed the correct drivers for that. Then it would give me ADB server out of date killing message. After trying so many things I finally saw reference to HTC Sync Manager being a potential problem so I uninstalled that. I also updated Android SDK Platform tools because I had a copy of that on my computer. Between doing these two things the tool finally worked and did it's job just like that .

The crazy thing is that it would pass all the Tool number 1 driver tests but then would not work correctly . So after a couple hours I finally got the fix Hope it might help someone else save a lot of time !

( posted this on other thread by mistake but might help there too ! )
[Fire Android Development] tnowakow:
Is this still accurate? I just got a 5th gen in the mail and it updated OTA, can I run this or should I wait? Thanks all!
[Fire Android Development] sd_shadow:
what system version?
[Fire Android Development] wulfie66:
as long as it's no higher than fireOS 5.1.1, the supertool will work fine
[Fire Android Development] K.Fulcher:
I bought two of these 5th gen tablets. With one I was able to root and use flashfire to get CM running.... on the other I cannot get it to root. It keeps on showing me adb errors "Adb out of date killing ". Any ideas as I am at a loss. I have restarted , reinstalled drivers, installed the android sdk, tried different systems (all of my are win10 64bit). I am not sure what to try next.
[Fire Android Development] cyberjak:
will this work for the Kindle Fire HD 7 4th gen. just looking to get google play services/apps on don't want to try and replace bootloader and recovery if not required. just wanting a few games that need google play games and services to work and a few apps.
[Fire Android Development] wulfie66:
having multiple copies of adb.exe on your pc isn't always a good thing, especially if you have one in your paths and it's an older version. I ran into this with my Galaxy S3, once I removed all copies of adb.exe and installed just the latest, all my problems went away, YMMV
[Fire Android Development] asmad:
Pretty sure it's only for the 5th Gen fire.
[Fire Android Development] DB126:
If it worked for the HD 7 it would be posted in that forum.
[Fire Android Development] WLShafor:
I have a MacBook Pro will this work for me or will I need to use Windows?
[Fire Android Development] asmad:
Windows.
[Fire Android Development] WLShafor:
Is this for windows only or can I do this on my MacBook Pro?
[Fire Android Development] wulfie66:
I would use this instead, it does the same thing and works on all OSes, http://xdaforums.com/amazon-fire/general/root-playstore-busybox-optimize-flash-t3281804
[Fire Android Development] tnowakow:
Thanks all, it's on 5.1.1 OS so I'll go ahead and try rooting it later this week, i appreciate the quick response!
[Fire Android Development] harg0n:
Great tool. Thx.

If have installed SuperSU, blocked OTA Updates and installes Play store with it.

Now I felt like trying CM12.1, so I installed FlashFire 0.27 from the PlayStore. Before flashing it issues a warning... I am trying to flash but have changed /oem /vendor or /system and states the flash is likley to fail.

Im kinda lost there. Can you explain this to me? What should or can I do?
[Fire Android Development] wulfie66:
as far as I know, that's a standard warning. If you're still on 5.0.1, I'd use TWRP via fastboot, otherwise, continue on with flashfire
[Fire Android Development] harg0n:
I dont think its a standard warning, since it warns that FlashFire is likely to fail.

I am on 5.1.1 so TWRP is not an option.
[Fire Android Development] iyousif:
Many thanks for the wonderful tool. My Fire is kinda useful now! :)
[Fire Android Development] DB126:
I see you are active in the XDA FlashFire forum which is the best place to receive current information and support.
[Fire Android Development] rcrh:
I am stuck when trying to root my fire7. I'm on fireos 5.1.1. and had previously run your other tool to add the Google Play store (before an ota update to 5.1.1).

When any of the adb scripts reboot the tablet into fastboot mode the script just hangs says "waiting for device".

The screen on my tablet says "FASTBOOT mode..." with no number after it.

I have tried to update the fastboot driver but when I run that script it drops into fastboot mode and then the tablet doesn't show in my device manager. I am running windows 7.

I have also run the KindleDrivers.exe file. It completed fine.

Anything else I can try? I really want to get this rooted so that I can use FlashFire to install CM12.1

Thanks in advance.
[Fire Android Development] platypoid:
I think I went into files of Tool and found a Kindle driver folder and installed those drivers. Or else you need to go to Windows device manager and see what your fire is showing up as. I had a bit different problem where HTC Sync program was messing it up and it worked when I uninstalled that program.

good luck - took me a few hours to figure out how to get mine to go.

.
[Fire Android Development] rcrh:
I went into USB_DRIVER and ran KindleDrivers.exe. That seems to install the ADB driver.

In the device manager it shows as

Android Device/Android ADB Interface

Portable Devices/Fire

But when it goes into FASTBOOT that device disappears & I see mtx65 preloader
[Fire Android Development] wulfie66:
while it's still in fastboot mode, don't close the script, but open your device manager and look for a yellow triangle that should be your fire, right click it and choose 'update driver' and choose your adb driver from there, it should continue after that
[Fire Android Development] raven911:
Hello, I tried search the forum but found nothing conclusive on my issue; I used the supertool and installed Android Market. However, it seems seems like Google contacts is missing, as well as the Google account sync menu in settings. How could I get access to those? I am on 5.1.1 stock rom
[Fire Android Development] mt12345:
Thanks a lot. Works perfectly on Windows 7 x64, Fire OS 5.1.1

Which features would I lose after factory reset ?
[Fire Android Development] platypoid:
Root Junky just made a Youtube video explaining how to factory reset and what is lost or saved.

https://youtu.be/ZkNArXhJF8M
[Fire Android Development] mt12345:
My question is which features are altering the system partition.

I know root ota and nova will survive but google stuff looks like user apps so will it be lost?
[Fire Android Development] DB126:
Depends how each component was installed. Flashed items (those included in the GAaps package) are generally installed into the system partition and should survive a 'factory reset'. Items installed from the Play store or sideloaded are generally installed in the area that gets wiped. There are exceptions; don't view the above as absolute.
[Fire Android Development] mt12345:
I installed google play store using supertool and looks like the store, framework and services are on /data hence my question.
[Fire Android Development] DB126:
Supertool does not 'flash' content so most (if not all) installed items will be located on /data. A few apps (eg: SuperSU) have the ability to relocate themselves to system but these are the exception. I believe launchers also fall into this bucket.
[Fire Android Development] newinnov:
Hi, is there any way to integrate updates of system apps to system partition?
[Fire Android Development] mt12345:
I use Link2SD to do it:

Long press on app, INTEGRATE UPDATE INTO SYSTEM.

---------- Post added at 12:26 PM ---------- Previous post was at 12:16 PM ----------

Answering my own question:

I did factory reset and I lost google store.
[Fire Android Development] DB126:
As you migrate content keep an eye on free space in the system partition. Many a frustrating experience begins with a full system partition.
[Fire Android Development] gdroid666:
stupid question but once i flash a custom rom then i am safe from amazon OTA updates right? i mean i do not need to use the supertool again to lock OTA after i flash a custom rom?
[Fire Android Development] DB126:
Correct - Amazon OTA updates are only relevant when FireOS is the primary rom.
[Fire Android Development] newinnov:
When I did that (integrate update to system), those app disappeared after restart :(
[Fire Android Development] DB126:
As expected.
[Fire Android Development] rcrh:
I think I have my device rooted. I had been trying to do this with the device attached to a USB hub. I plugged it directly into the desktop and things ran much smoother. I'm going to stop future OTA updates and then move on to installing CM12.1.

Thanks Platypoid & wulfie66
[Fire Android Development] pfoneguy1:
[MENTION=4246643]Tomsgt[/MENTION]

Are you going to incorporate the latest version 0.27 of Flashfire in your SuperTool?
[Fire Android Development] Tomsgt:
just did that run option 9 and it will be updated to flashfire .27
[Fire Android Development] .amazon fire os:
Hey guys , I have a Mac and want to use the supertool for amazon kindle fire 7", 5th generation 5.1.1 ...so is there a supertool version which runs on Mac ...I yes then send the link....

Thnx!!
[Fire Android Development] DB126:
There is not. Could try VirtualBox or just find a friend w/Windows.
[Fire Android Development] mt12345:
basically it's a script so after some modifications should work on linux and mac?
[Fire Android Development] DB126:
Yes. Could execute the commands manually or adapt to a native osx script. Nothing canned that I am aware of.
[Fire Android Development] Tomsgt:
I have been meaning to make it into a mac and linux bash script but just havent gotten to it maybe one day
[Fire Android Development] Tomsgt:
just updated the supertool better check the change log in the OP
[Fire Android Development] Darkbyrd:
thanks a lot for this tool and your time, worked like a charm.
[Fire Android Development] Tomsgt:
just added a script for linux and mac please try it any report back thanks
[Fire Android Development] Mlokz:
Hi Im trying to use the mac tool and whenever I open it in terminal and type in Root i type in my password and then get.

sudo: files/./adbosx: command not found

sudo: files/./adbosx: command not found

[*] rebooting to bootloader

sudo: files/./adbosx: command not found
[Fire Android Development] Tomsgt:
on mac it might need to be sudo: files\./adbosx instead of sudo: files/./adbosx i am not sure i dont have a mac so its hard to test it
[Fire Android Development] Mlokz:
alright thanks, gonna try again ill probably just pull out the old windows pc i have lying around thanks a million!

decided to use a pc and it worked flawlessly no problems at all thanks!
[Fire Android Development] bovineyard:
Hello, I have been trying to install "cm-12.1-20151211-UNOFFICIAL-ford.zip" plus the Gapps with Flashfire 0.27, and I get the error in the photo below:

[IMG="Error screen"]https://dl.dropboxusercontent.com/u/22509950/IMG_20160308_055521.jpg[/IMG]

"Can't install this package on top of incompatible data. Please try another package or run a factory reset"

I am at a loss as what to do, I have followed all of the instructions I have found.
[Fire Android Development] DB126:
Have you factory reset?
[Fire Android Development] bovineyard:
[/COLOR]

Yes, in fact every time I have tried installing the rom, I also use the factory reset option in Flashfire, so it has been reset multiple times.
[Fire Android Development] DB126:
Do a factory reset from the device recovery menu.
[Fire Android Development] bovineyard:
I did that before I installed the first time. The problem is, I have to go back in after reset to reinstall flashfire to flash the rom.
[Fire Android Development] DB126:
Shouldn't matter that you had to restart FireOS to reinstall FlashFire after a reset. There's really two paths at this point: 1) continue to peel back the onion in an effort to determine why FlashFire is coughing up a hairball; or 2) reload FireOS to restore your device to an out-of-the-box state. RootJunky produced an excellent video outlining the process (here). Note there is always some risk flashing firmware (stock or otherwise). Be sure to following all instructions carefully.

Sorry for not having a better answer. To many variables to efficiently track down.
[Fire Android Development] bovineyard:
In fact I did sideload the factory image 5.1.1 that he had on his website. Booted into it just enough to root, install flashfire 0.27, added the cm 12.1 and Pico gapps that he had in his site, chose the wipe option. Exactly the way He showed to do it in his YouTube video. Stock rom loads and works fine, but cm doesn't.
[Fire Android Development] DB126:
Given this detail it appears CM is not going to work for you (won't hazard a guess why your device behaves differently from most others). There have been other issues with CM (notably flashing GAaps) that depreciate the value relative to other compatible roms imho. While it may have the appears of shotgun troubleshooting I suggest you try [MENTION=5749760]ggow[/MENTION]'s Fire Nexus ROM which has proven stable on several different platforms.

Good luck.

p.s. curious, did you try removing the SD card (if you have one installed) before running FlashFire? Very left field thought but easy enough to test. Building on recent reports of apps not installing/running correctly when a SD card was present.
[Fire Android Development] bovineyard:
Thanks for your help. I'll try those things.
[Fire Android Development] koda1789:
Root issues

Still trying to get root.

I go through the driver test and my PC sees the device in step one but when I move to the second step to verify fastboot, the screen on the device goes blank but it doesn't say fastboot in the corner.

Hitting enter on my PC reboots the device and in the Supertool display it says fastboot with a device number.

Tried to then root and get a failed message when it attempts to reboot the device into fastboot.

I've tried updating drivers multiple times and different variants and still stuck trying to get the device into fastboot.

Ideas?

Thanks!
[Fire Android Development] m00head:
I remember seeing this error when the /system partition hadn't been wiped first, so you may want to check that the /system partition was selected for wipe, and that the wipe option is moved ABOVE the firmware flash in Flashfire.
[Fire Android Development] bovineyard:
I just realized wipe needs to be dragged up to the top. Thanks.
[Fire Android Development] DB126:
- good suggestion by [MENTION=7252768]m00head[/MENTION] but be aware of the risk; once the system partition has been wiped the subsequent flash operation must succeed; if not you will likely have no functioning rom and have to sideload FireOS via the stock recovery menu

- make certain the wipe option is first (on top) when the system partition is selected; otherwise the rom you just flashed will be immediately wiped and you'll be in the same situation as above
[Fire Android Development] bovineyard:
Yes, been there, done that, on the sideloading. Thanks!
[Fire Android Development] Signor Rossi:
Any word on 5.1.2?

I understood root is not working with the current tool?

Gesendet von meinem OnePlus One
[Fire Android Development] sd_shadow:
try rootking

---------- Post added at 12:58 AM ---------- Previous post was at 12:57 AM ----------

new root methods can take Months to develop
[Fire Android Development] pfoneguy1:
So there is an update to 5.1.1 to 5.1.2 and 5.1.2 is not currently rootable? Are they shipping with 5.1.2 or is this a OTA update?
[Fire Android Development] sd_shadow:
seems to be an 5.1.2 update, root Unknown, doesn't seem to be shipping installed yet.