Database Users

Motoactv

Just curious if anyone is willing to tackle this little gagdet. It needs some fine tuning and possibly a voodoo sound app would be awesome. It lacks the loudness like most android phones.

It looks interesting, but I would not personally buy it. It does not have enough features for me to use it over my phone.
Sent from my XT862 using XDA App

Well I purchased one and with the help of the other thread about the apk i was able to sync to my epic with all features including the calls/missed calls and acuweather. This was with the corded headset. I have no real reason to get the wireless. The only real problem that i have right now is the sound level of the player. Its very frustrating to have to use a program to up the db level in every song i put on it. It running some kind of android platform so someone has to have some ideas.

Well, it looks like someone has listened... I didn't see a thread anywhere else, so I'll post it here, some one has rooted the motoactv. the story, along with a link to a how to is available, just google it. I was gonna post a link, but I can't.

The Motoactv runs gingerbread. CWM has gained root on it and installed Google apps. It has a decent chip and ram for a small device. The bootloader isn't locked. More and more smart watches and wearable computers will be coming out. I'd like to see a custom launcher for this size screen as QCIF+ ain't exactly great for a lot of launchers. A custom rom that remapped the hardware buttons would be nice as well.
Cheers,
-M
XDA member since 2007

Hi People
I just rooted the MotoACTV with the tutorial provided by Wade, the guy that rooted the watch. But I am having problems installing the ggole apps on it. The guide does not explain very well how to install the gogle apps. I managed to install several apk via adb commands and they work ok. But I am missing the market and every default google ape. Can someone explain how to do this? I already downloaded google apps zip file from cynogen web page.

rdavidowski said:
Hi People
I just rooted the MotoACTV with the tutorial provided by Wade, the guy that rooted the watch. But I am having problems installing the ggole apps on it. The guide does not explain very well how to install the gogle apps. I managed to install several apk via adb commands and they work ok. But I am missing the market and every default google ape. Can someone explain how to do this? I already downloaded google apps zip file from cynogen web page.
Click to expand...
Click to collapse
There are libraries in the unzipped file that need to be installed with the adb push command to get maps to work. The market needs a bunch of crap to work. You should push all the apk (except car home if you don't want it) once you have those over, restart and you download the rest of the apps from market.
Cheers,
-M
XDA member since 2007

This sounds intriguing can you run RunKeeper on the rooted device. I have the motoactv and love it for running but RunKeeper in my opinion is the best running app. Im anxious to hear more about this.

Thanks Dragon, but one more question before I keep trying this market stuff. Do I do the adb push command to the same exact directories as the zip has. Like for example: the zip file that I downloaded was for CM7 and it includes a lot more directories than simply the app directory. Do I have to push every single directory the zip has and create the ones that are missing within the watch. Can you please explain more in detail if possible. Thanks again for the help as this is the only thing I am missing from this "the market".

rdavidowski said:
Do I have to push every single directory the zip has and create the ones that are missing within the watch. Can you please explain more in detail if possible. Thanks again for the help as this is the only thing I am missing from this "the market".
Click to expand...
Click to collapse
So, once unzipped you will see "META-INF" and "system" folders.
Inside "system" you will see:
app
etc
framework
lib
inside "app" you will see:
*CarHomeGoogle.apk
*FOTAKill.apk
GenieWidget.apk
Google Maps 5.12.0.apk
GoogleBackupTransport.apk
GoogleCalendarSyncAdapter.apk
GoogleContactsSyncAdapter.apk
GoogleFeedback.apk
GooglePartnerSetup.apk
GoogleQuickSearchBox.apk
GoogleServicesFramework.apk
*LatinImeTutorial.apk
MarketUpdater.apk
MediaUploader.apk
NetworkLocation.apk
OneTimeInitializer.apk
*Talk.apk
Vending.apk
(*not really needed on MotoACTV but won't hurt to install)
I am doing this from a Mac using terminal, it has been a richard year since I have used CLI with windows but for Linux the commands will be the same ("dragon$" is just my terminal prompt).
dragon$ adb push ~/Desktop/gapps/system/app/Vending.apk /system/app
dragon$ adb push ~/Desktop/gapps/system/etc/permissions/features.xml /system/etc/permissions/
So, you see I have pushed the files to the corresponding directories that the files are found in the unzipped folders.
I cannot remember if adb push defaults to parent owner and permissions but if not you will have to change them to root/root and RW-R--R--

I followed CMW's guide to root mine, too.
dragon_76 said:
I'd like to see a custom launcher for this size screen as QCIF+ ain't exactly great for a lot of launchers. A custom rom that remapped the hardware buttons would be nice as well.
Click to expand...
Click to collapse
A full custom would be great (but not needed for remapping hardware keys); Motorola's UI is really quite nice for the screen size, but won't show custom apps. Instead of the fake Honeycomb one, I prefer to use Zeam (with the launcher and grid set to 3x3 icons) -- I just think it works much better, without overlapping icons and so on.
To get a shortcut to the wifi access point settings in zeam, press and hold in a blank area, and go to "add", then "shortcuts", then "settings", then "settings" again. This "settings" is the hidden wifi one.
I also remapped "Start" to menu fairly easily by modifying they G2-keypad.kl file under keylayout; nosit1 was able to do the same with music to home. The people in #motoactv on freenode.net are very helpful, including CMW.
More information on that:
/system/usr/keylayout/G2-keypad.kl
Change this line:
key 220 FITNESS WAKE_DROPPED
to this:
key 220 MENU WAKE_DROPPED
On a separate note, you'll want to backup your userdata partition, too. Otherwise, it can get corrupted and make the file loop at the motorola logo:
dd if=/dev/block/userdata of=/sdcard/userdata.img bs=1024
adb pull /sdcard/userdata.img userdata.img
Even when restoring that, there are a ton of force closes from com.motorola.gault.activity; you have to get past them to a custom launcher to factory reset.

@dragon_76
Does anything need to be done with the META_INF folder? I'm attempting to get Market working on my Motoactv but I'm still getting a Google Services Framework force close. I pushed over the gapps from CM6 (the ones under HDPI). Not sure if those were the right ones.
I think I need to factory reset and start over from the beginning. :/

MinionOfEckerd said:
@dragon_76
Does anything need to be done with the META_INF folder? I'm attempting to get Market working on my Motoactv but I'm still getting a Google Services Framework force close. I pushed over the gapps from CM6 (the ones under HDPI). Not sure if those were the right ones.
I think I need to factory reset and start over from the beginning. :/
Click to expand...
Click to collapse
No, that folder is for recovery mode installers.
Amazon app store works perfectly if you can't get Market to work. It takes a fair amount of trial and error with apps to find ones that are functional.
I can't recommend enough installing grafitti pro. I have it from Amazon FAOTD.
I have superuser.apk installed and I had to push my preferences from /data/data/ on my phone to my watch so as to autorespond "yes" to root requests and no notifications because the UI is a fixed size window.
After doing that I installed button saviour and my purchased key for the pro features to have only home and menu onscreen. (Button saviour needs root permission).
I use golauncher ex with 3x3 home screen and the notification bar hidden. I wish I could remove the dock but oh well.
Android is going into more types of devices, I wish Google would push scalable graphics. I am however very impressed with the amount of apps that work usably on a QCIF+ screen (Netflix!)
I also like the main launcher and if I could access an app like AltDrawer from it I would not have another home replacement installed. I will tear apart Launcher2.apk soon and see if there is a way to customize it.
Sent from my MB860 using xda premium

Okay so last night I attempted to root my motoactv but my adb for some reason say it cannot load the root.img, I had the same problem where it's couldn't load the recovery.img for my photon when attempting to apply CWM or twerp recovery. Fastboot devices definitely sees both my devices (no I didn't do them are same time, and the files needed are in the same file location as instructed) and I can even Fastboot reboot and have that work. Any ideas or suggestions?? Any help would be appreciated.

moonzbabysh said:
Okay so last night I attempted to root my motoactv but my adb for some reason say it cannot load the root.img, I had the same problem where it's couldn't load the recovery.img for my photon when attempting to apply CWM or twerp recovery. Fastboot devices definitely sees both my devices (no I didn't do them are same time, and the files needed are in the same file location as instructed) and I can even Fastboot reboot and have that work. Any ideas or suggestions?? Any help would be appreciated.
Click to expand...
Click to collapse
Try downloading a new root image. Also try switching USB ports.
Sent from my MB860 using xda premium

dragon_76 said:
No, that folder is for recovery mode installers.
I have superuser.apk installed and I had to push my preferences from /data/data/ on my phone to my watch so as to autorespond "yes" to root requests and no notifications because the UI is a fixed size window.
After doing that I installed button saviour and my purchased key for the pro features to have only home and menu onscreen. (Button saviour needs root permission).
I use golauncher ex with 3x3 home screen and the notification bar hidden. I wish I could remove the dock but oh well.
I also like the main launcher and if I could access an app like AltDrawer from it I would not have another home replacement installed. I will tear apart Launcher2.apk soon and see if there is a way to customize it.
Sent from my MB860 using xda premium
Click to expand...
Click to collapse
Thanks, wasn't sure about the META-INF folder. Going to try installing button saviour. How did you "push" preferences from your phone to the watch? I have root/su on my Xperia Play so I should have the files there to push?
Did you personally get the Google Apps working?
EDIT: Everything is forceclosing on me. :/ Installed the Stock Browser from my XP but that's forceclosing as well. Attempted to change the permissions of the applications but either it didn't work or it didn't help.

I couldn't figure out how to push preferences, but I was able to tell Superuser to allow all apps after remapping Start to Menu, then just doing Superuser > Menu > preferences. You could always do this to get Superuser working, get Button Savior working, and then revert it back.
(I made a step by step on Pastebin, but if you use Oneroot, it might do all this for you: http://pastebin.com/AZRemesV )

ldrn said:
I couldn't figure out how to push preferences, but I was able to tell Superuser to allow all apps after remapping Start to Menu, then just doing Superuser > Menu > preferences. You could always do this to get Superuser working, get Button Savior working, and then revert it back.
(I made a step by step on Pastebin, but if you use Oneroot, it might do all this for you: http://pastebin.com/AZRemesV )
Click to expand...
Click to collapse
Thanks a lot. Just did a factory reset, figure I'll start from scratch. Did you get the Google Apps working after Superuser was configured? What Browser are you using? (Dolphin was forceclosing for me every time I went to type.)
EDIT: Got Superuser working, did the keyboard hack to make Start=Menu. Anybody know what button Music is mapped to in the configuration?
Going to fiddle around some more w/ Google Apps. Anybody have a walkthrough of installing the apps? IE Which ones you must do, don't have to do and what to do to get it working.
EDIT: It was WAKEkey 378. It was set to "MEDIA" so I changed it to "HOME". Works perfectly!

Hanging at the Red Moto Logo
Followed the instructions and had it working rooted, etc. Was going to change out the launcher. And obviously did something wrong. Now it just just hangs at the Red Moto logo. Can get it to power off and can still get it to the fastboot mode. Have tried reflashing the system and userdata, wiping the user data, etc. Any suggestion on what to try next?

ts937km said:
Followed the instructions and had it working rooted, etc. Was going to change out the launcher. And obviously did something wrong. Now it just just hangs at the Red Moto logo. Can get it to power off and can still get it to the fastboot mode. Have tried reflashing the system and userdata, wiping the user data, etc. Any suggestion on what to try next?
Click to expand...
Click to collapse
Join our IRC at irc.freenode.com #motoactv
We have been working on this for a while. We are planning on working on a thread for this.
Currently I have Spotify and Sportstrack Pro running well. I'll start to compile a list of working applications.
If you're stuck in a boot loop, you'll need the userdata partition image. I'll edit my post with it once I'm on my computer.
Sent from my Galaxy Nexus using Tapatalk

qemu.hw.mainkeys=1 works for everyone EXCEPT ME

Ever since getting my Razr Maxx HD (XT926) three months ago I've been trying to get rid of the Navigation Bar on the bottom of the screen. I use Button Savior so I'm fine with having the NavBar controls disappear.
Among the most reliable remedies seemed to be upgrading to 4.1.2, at which point many people said that you could simply add the line "qemu.hw.mainkeys=1" to the end of your build.prop file in /system, reboot, and *poof* the NavBar would be gone. My phone, which I bought used, was running a leaked 4.1.1 so, once root for OTA 4.1.2 was discovered, I downgraded to 4.0.4, did the updates to that, then took the OTA upgrade to 4.1.1 (no problem), then took the OTA upgrade to 4.1.2 (no problem). So now I had the latest JB version offered for Verizon XT926 in the US. I know that I'd wiped data at least once along the way. The SafeStrap installation that I used to have was gone, as I expected. I assumed that my phone was as stock as it could be and thus ready for the build.prop edit.
I used the new procedure to root my XT926. At that point all I did was to download and install Root Explorer (needed to do the build.prop edit) and Button Savior (needed for navigation once NavBar was gone). In Root Explorer I navigated to /system, made it R/W, opened build.prop in the stock text editor, added qemu.hw.mainkeys=1 at the end, saved (which backed up the older version as expected), and rebooted.
The first thing I get when my phone boots up is the "SystemUI has crashed" error message. My NavBar is gone but so is my System Bar (a/k/a Notification Bar), which I need and want to be visible. I've read a TON about this and I'm pretty sure I've followed the instructions. Why is this not working for me?
I am just not smart enough to decompile and edit my framework-res.apk file (or whatever the name is) so I'm stuck trying to make the build.prop edit work. What could I be doing wrong?
(also, if I use one of the apps like FullScreen or BottomBar they produce the EXACT SAME result -- SystemUI crashes, NavBar disappears but so does System Bar).

cant help
it works for me as experted

Are you positive you entered it correctly?
Sent from my JokerMATRIX HD MAXX

deeje00 said:
Are you positive you entered it correctly?
Sent from my JokerMATRIX HD MAXX
Click to expand...
Click to collapse
He also tried an app which writes the line to the build.prop and got same results.
AFAIK I had crashes on ICS but since I'm on JB 4.1.2 I never had any issues...
Sent from my XT925 using xda app-developers app

Yes, the edit is entered correctly. I've checked that more times than you can imagine. And I've tried nearly every variation that's been suggested anywhere: with spaces before and after the "=", adding the line ending with "0" first then rebooting then changing the end to "1" then rebooting, putting an empty line at the end of build.prop before adding the edit. No change. Is there any history of an app interfering with this edit? I don't have anything exotic installed I don't think but I use a third party launcher (Go Launcher EX) and then a variety of apps, mostly audio/video, social media and a few basic games. I believe that changes to build.prop take place "below" that kind of activity, though, right? And besides, I made the edit before I installed any of that stuff. I may try a hard reset or something like that but if this works for everyone else then I must just be missing something.

I have had the exact same issue and done the same troubleshooting...sucks!

did you happen to check file properties after you saved, i remember back in the early days of Android if you edited a file, you had to change the properties back to the defaults, not sure if that is still the case, but worth a look.

It can't be done on any stock via build.prop only, and framework edits require a deodexed rom.
I recommend you install CM10 or 10.1. If you prefer safestrap over CWM, then you can use CM10, but without a camera. Fullscreen toggle works perfectly, and I'm able to use PDroid : )

I suppose I should be glad that at least *one* other person is having this problem. Means it's slightly less likely that I'm just incompetent.
As for changing file properties, I didn't change any properties to do the edit other than making /system "RW" in order to be able to edit the file. Could someone tell me what the default values are for build.prop? The most recent edit I've made always shows up correctly when I go back into build.prop, by the way, so I know I'm actually changing the file.
If a rooted stock 4.1.2 can't hide the NavBar with a build.prop edit then this is the first I've read about it, and I've read just about everything that I can find on this subject (including translations of non-English discussions, just in case I could get a new lead from them). Not saying that's not true, just not consistent with what I've read so far.
I'd love to install a CM ROM on my XT926. I've admired Cyanogenmod since I first started fiddling with my Nook Color some years ago. Their crew does some spectacular work. But -- no camera? No Bluetooth? Sometimes wifi or phone call problems? That's too much lost functionality for me. If those remaining few obstacles are someday overcome I'll be all over it though.
ONE LAST QUESTION -- I assumed that, if I "scrubbed" my phone down to the lowest level possible (wipe cache, wipe dalvic, wipe data) I would eliminate whatever weird impediment I have to getting the build.prop edit to work. Is there something else I can do to wipe the phone even MORE thoroughly?

The permissions are RW-R-R, I have had the issue with stock and custom roms (running Foot Through the Floor right now). I wasn't surprised when it didn't work with stock (silly Moto) and I was a little surprised when it didn't work with and of the custom roms I tried, I have no doubt it would work in CM.

I tried it out, it works but you need to reboot after edit, I hot booted and nothing changed, full reboot and it works. hope it helps you.

Just in case this makes the difference, can you tell me what distinguishes a "hot boot" from a "full reboot"?

Having issues myself. Have 4.1.2 rooted, RAZR HD. Added the line above to build . prop with "=0" first shutdown, started back up. Then changed to "=1" saved, shutdown and started back up. System UI FC's.
Wonder if it matters what launcher is being used. I am on GO Launcher. I say this since on home screen I see the GO Launcher menu show up just below bottom of my wallpaper but behind it. I can swipe up to bring up full menu but it is weird how it comes up in background on its own.
Anyone get it to work with GO Launcher?
Sent from my DROID RAZR HD using xda app-developers app
---------- Post added at 10:56 AM ---------- Previous post was at 10:54 AM ----------
Oh and does it matter where in build.prop the line goes? I just added to bottom. Thx.
Sent from my DROID RAZR HD using xda app-developers app
---------- Post added at 11:29 AM ---------- Previous post was at 10:56 AM ----------
lesdense said:
Yes, the edit is entered correctly. I've checked that more times than you can imagine. And I've tried nearly every variation that's been suggested anywhere: with spaces before and after the "=", adding the line ending with "0" first then rebooting then changing the end to "1" then rebooting, putting an empty line at the end of build.prop before adding the edit. No change. Is there any history of an app interfering with this edit? I don't have anything exotic installed I don't think but I use a third party launcher (Go Launcher EX) and then a variety of apps, mostly audio/video, social media and a few basic games. I believe that changes to build.prop take place "below" that kind of activity, though, right? And besides, I made the edit before I installed any of that stuff. I may try a hard reset or something like that but if this works for everyone else then I must just be missing something.
Click to expand...
Click to collapse
I just noticed this (missed it first scan through) that you use Go Launcher as well. I do also and am having same issue. I am going to try switching to Apex, Nova or other to see if that is the culprit. If so, I can most likely get used to another custom launcher to gain the extra space.
BUT if anyone doesn't have issues AND is using Go Launcher, please let us know so we can rule that out.
Thanks

I use nova pro and have the issues.
Sent from a non-apple device.

coolloser said:
I use nova pro and have the issues.
Sent from a non-apple device.
Click to expand...
Click to collapse
I just tried Apex Launcher and had same FC issue. So guess it isn't specific to any of the launchers (was a long shot anyway). This is just really weird. Some folks swear they have it running on stock 4.1.2 (OTA update) rooted, but many of us have the same and can't get it to work.
I saw one thread where someone mentioned you needed to make sure everything is stock, meaning using TB to unfreeze anything you had frozen, and then give it a go. Problem is I'll want to refreeze much of that bloatware from VZW so not sure if that helps or not.
So frustrating......

At this stage in the trail and error I wonder what other variables could be the key. It's not the version (4.1.2). It's not launcher (problems with Go, Apex and Nova plus the stock launcher). Making everything stock didn't help me -- I flashed a brand new version of 4.1.2, installed ONLY Button Savior (for navigation) and Root Explorer (to edit build.prop). Same problems as usual. I assume it's not the rooting utility as I believe only one exists.
OK, how about some weirder ideas. Has everyone done the build.prop edit with Root Explorer? Maybe there's a flaw in that tool. I just tried editing the build.prop to put IN the qemu.hw.mainkeys=1 line, then temporarily suspended root with VooDoo, then rebooted to see if it would behave if it thought it wasn't rooted. Same result. Maybe the guy saying you can't make this work on rooted stock ROMs was right Still, I'll keep looking, and sharing.

lesdense said:
At this stage in the trail and error I wonder what other variables could be the key. It's not the version (4.1.2). It's not launcher (problems with Go, Apex and Nova plus the stock launcher). Making everything stock didn't help me -- I flashed a brand new version of 4.1.2, installed ONLY Button Savior (for navigation) and Root Explorer (to edit build.prop). Same problems as usual. I assume it's not the rooting utility as I believe only one exists.
OK, how about some weirder ideas. Has everyone done the build.prop edit with Root Explorer? Maybe there's a flaw in that tool. I just tried editing the build.prop to put IN the qemu.hw.mainkeys=1 line, then temporarily suspended root with VooDoo, then rebooted to see if it would behave if it thought it wasn't rooted. Same result. Maybe the guy saying you can't make this work on rooted stock ROMs was right Still, I'll keep looking, and sharing.
Click to expand...
Click to collapse
Root Explorer is what I used.
For the other guy having trouble, it hasn't been mentioned yet; did you set the owner and group for the file to root? If the file was ever stored on the sdcard or pushed there then moved, those permissions might make a difference as well. Its a good security measure in the case that it isn't relevant in any case... don't want a wild website writing to your build.prop file, for example.

PantsDownJedi said:
Root Explorer is what I used.
For the other guy having trouble, it hasn't been mentioned yet; did you set the owner and group for the file to root? If the file was ever stored on the sdcard or pushed there then moved, those permissions might make a difference as well. Its a good security measure in the case that it isn't relevant in any case... don't want a wild website writing to your build.prop file, for example.
Click to expand...
Click to collapse
I used ES File Explorer (and then you have to use Root Explorer menu option to set r/w prior to opening build.prop).
Regarding the rest of the post above. Not sure what the question is. I never did anything to the build.prop file other than set ES File Explorer to r/w on everything, then edited the build.prop file, saved, checked to ensure it was edited right, then rebooted. So the 'file' has never been anywhere other than in /system. When I check the properties on the build.prop file I see rw- r-- r-- (this the same whether or not /system is set to RW or just RO). I believe these are correct (default) settings, but let me know if that is not correct.
Anyone out there that has this working on Stock 4.1.2 it would be nice to know more (i.e. is 4.1.2 the OTA or leaked version, did they use motochopper root method (only one I thought), persmissions on file, where did they place the qemu line in the file, etc, etc).
---------- Post added at 11:33 AM ---------- Previous post was at 11:21 AM ----------
PantsDownJedi said:
Root Explorer is what I used.
For the other guy having trouble, it hasn't been mentioned yet; did you set the owner and group for the file to root? If the file was ever stored on the sdcard or pushed there then moved, those permissions might make a difference as well. Its a good security measure in the case that it isn't relevant in any case... don't want a wild website writing to your build.prop file, for example.
Click to expand...
Click to collapse
BTW... anyone look into testing the framework-res.apk option? Sounds in-depth and much more work (not to mention chance of screwing things up). It would be new to me to decompile, etc, etc, but am not scared to try, just thought I would ask if anyone else already has. Also, not sure if that option is for the 4.1.2 OTA version (verizon in my case).
Thanks.

surfmly said:
I used ES File Explorer (and then you have to use Root Explorer menu option to set r/w prior to opening build.prop).
Regarding the rest of the post above. Not sure what the question is. I never did anything to the build.prop file other than set ES File Explorer to r/w on everything, then edited the build.prop file, saved, checked to ensure it was edited right, then rebooted. So the 'file' has never been anywhere other than in /system. When I check the properties on the build.prop file I see rw- r-- r-- (this the same whether or not /system is set to RW or just RO). I believe these are correct (default) settings, but let me know if that is not correct.
Anyone out there that has this working on Stock 4.1.2 it would be nice to know more (i.e. is 4.1.2 the OTA or leaked version, did they use motochopper root method (only one I thought), persmissions on file, where did they place the qemu line in the file, etc, etc).
---------- Post added at 11:33 AM ---------- Previous post was at 11:21 AM ----------
BTW... anyone look into testing the framework-res.apk option? Sounds in-depth and much more work (not to mention chance of screwing things up). It would be new to me to decompile, etc, etc, but am not scared to try, just thought I would ask if anyone else already has. Also, not sure if that option is for the 4.1.2 OTA version (verizon in my case).
Thanks.
Click to expand...
Click to collapse
I was kind of just pulling at straws, and trying to answer two posts at the same time, sorry for the confusion. My habit, especially before unlocking the bootloader, is to push things to the sdcard then moving them and setting the right permissions and assingining the correct group and user.
As you've explained things, I don't know why it shouldn't work. Mine is a 4.1.2 OTA. It was originally rooted before upgrading and using Voodoo root keeper but between that and Supersu paid version I was able to reinsert root again after a factory reset, which was a stroke of luck as others lost it. I don't think it would matter which root method is used but I could be wrong; esentially its just allowing us to access the build.prop file to edit at all. I don't remember if I had modified the build.prop before or after the reset. I know that it was working both before and after I unlocked the bootloader though. As for the placement of the line, I put it at the end. I also, out of habit, hit enter for a new line for this type of thing. Afterwards, though, there is now new things that Pimp My Rom has inserted (Some of the tweaks in that package are old and I'd advise people to stick with close to stock as possible when using it unless they know what those lines mean; and there's some build.prop myths still floating around XDA that are not good ones, one of which I know Pimp My Rom uses and looks pretty apealing to select). So, now I have some stuff after it. If there were other things added to your build.prop, then perhaps moving the line to the end of where the default configuration ended... grabbing at straws again with this last sentance but in the lack of information I'm just trying to be helpful
Perhaps if people also with this problem, in addition to answering your question about the root method they used, also posted which carrier branding they had it might reveal something, or rule it out. <-Put that in bold for you

I am VZW with Nova Pro, and I get the systemUI FC as well. After much research, I haven't heard of too many people with PHONES that have been successful in this hack, so I tried it on my GTab 2, and same thing.
After spending entirely too much time looking into this, I purchased Full!Screen+, set the apps that I wanted full screen, and I'm set (oddly enough, this didn't work on my GTab, so I also purchased Hide Bar for that device. I prefer FullScreen+ because the truth is, there's only certain apps that I care about being full screen (Netflix, games, youtube...).
The biggest problem with FS+ is that it hides the notifications. Honestly, I don't really care about that either when I'm doing one of these other activities. After all, we have a notification light.

Changing Launcher?

I bought one of these for my mom hoping it wouldn't be so well locked down. Has anyone managed to change their launcher from the default Amazon(Ad-laden) launcher? Sideloaded Nova but no dice there.

While Nova runs fine you can't replace the amazon launcher. I believe it was possible on pre 5.1.1 fire OS. Until we get root we'll just have make do.

If you're interested in changing the default firelauncher without rooting your device, please take a quick peak at my thread discussing the possibilties.
http://forum.xda-developers.com/hd8...zon-fire-hd-8-10-remove-firelauncher-t3286646
If you are currently rooted, which as of today is not possible on HD 8 & HD 10, you simply delete the com.amazon.firelauncher.apk in /system/priv-apps/com.amazon.firelauncher/, you will need to boot into fastboot and remount the system as rw if I am correct.
I hope this helps . Again, please check my thread for non-root information, it is currently unfinished.

Here is an updated tutorial on how to change the default launcher without rooting!
http://forum.xda-developers.com/hd8-hd10/general/tut-remove-default-launcher-amazon-fire-t3288192
Edit: Found a second method that is even better!

nyln said:
Here is an updated tutorial on how to change the default launcher without rooting!
http://forum.xda-developers.com/hd8-hd10/general/tut-remove-default-launcher-amazon-fire-t3288192
Click to expand...
Click to collapse
while you're method may work, it's far from optimal.
it's not possible to just rename another launcher and replace the FireOs launcher? i suppose that would be too easy.
if it were my tablet, i'd be more inclined to play around with it. unfortunately, my mom is content enough with it how it is, though i can see it being a beast and would **** around more if it were mine.
hopefully root comes soon. unfortunately, i can't help work towards it.
when all of that is said and done, i'll build a rom and kernel for it, np.

technope said:
while you're method may work, it's far from optimal.
it's not possible to just rename another launcher and replace the FireOs launcher? i suppose that would be too easy.
if it were my tablet, i'd be more inclined to play around with it. unfortunately, my mom is content enough with it how it is, though i can see it being a beast and would **** around more if it were mine.
hopefully root comes soon. unfortunately, i can't help work towards it.
when all of that is said and done, i'll build a rom and kernel for it, np.
Click to expand...
Click to collapse
I found a new method that actually works very very well, just run this in adb shell:
Code:
#!/bin/bash
am monitor | while read -r line; do
if [[ $line == *"firelauncher"* ]]
then
[B]am start com.newlauncher.launcher[/B]
fi
done

nyln said:
I found a new method that actually works very very well, just run this in adb shell:
Code:
#!/bin/bash
am monitor | while read -r line; do
if [[ $line == *"firelauncher"* ]]
then
[B]am start com.newlauncher.launcher[/B]
fi
done
Click to expand...
Click to collapse
Little bash script like that. I'll give it a try when I have time. Sleek enough, and if effective it's great.

technope said:
Little bash script like that. I'll give it a try when I have time. Sleek enough, and if effective it's great.
Click to expand...
Click to collapse
The only downside to the script is when you press the home button, there is a delay of 500ms or so, you see the firelauncher for that time.
It is not nohup or anything so it will stop working when you close adb shell (easy to do yourself, but I am preoccupied at the moment).

Why not root?
So I was actually able to ROOT my kindle fire hd 8 with the kingroot method.
After installing the apk.
Loaded it up let it try to find a root solution and it will not but you can try rooting with the other method and it WORKED for me. Never been so happy!
So after that I loaded adb shell in command prompt and typed "su" to see if I had root and it WORKED again, so I am even more happier!
Now after typing in "su" into command prompt I then typed in,
Code:
pm disable com.amazon.firelauncher
and it was successful..
NOTE: you must have another launcher installed before you do this! I had GOLauncher.
The End <3
P.S. I had installed the necessary files from rootjunky's "Amazon Fire Tablet Tool" or also known as installing google play store method..
Any questions hit me up, I have rebooted and still have root and things intact. Haven't had any problems as of yet. WOOT for ROOT

kanderson88 said:
So I was actually able to ROOT my kindle fire hd 8 with the kingroot method.
After installing the apk.
Loaded it up let it try to find a root solution and it will not but you can try rooting with the other method and it WORKED for me. Never been so happy!
So after that I loaded adb shell in command prompt and typed "su" to see if I had root and it WORKED again, so I am even more happier!
Now after typing in "su" into command prompt I then typed in,
Code:
pm disable com.amazon.firelauncher
and it was successful..
NOTE: you must have another launcher installed before you do this! I had GOLauncher.
The End <3
P.S. I had installed the necessary files from rootjunky's "Amazon Fire Tablet Tool" or also known as installing google play store method..
Any questions hit me up, I have rebooted and still have root and things intact. Haven't had any problems as of yet. WOOT for ROOT
Click to expand...
Click to collapse
After messing around the go launcher ex is a little buggy. I might try another, currently trying to figure out how to get widgets to work and once I do ill let you know the system file.
Any ideas what I should add to the fire os? Current goal is widgets

So after doing some research I believe it won't be possible on the fire cause the system files are missing. From what I've seen I feel like the new 5 the gen tablets are all the same, can't confirm it yet but if so you should be able to follow the instruction given on the kindle 7 5th gen able about booting up into twrp or cm and installing a new Rom. I'm not sure if I want to do this though. Adw launcher feels empty without widgets though
---------- Post added at 10:39 AM ---------- Previous post was at 10:37 AM ----------
kanderson88 said:
So after doing some research I believe it won't be possible on the fire cause the system files are missing. From what I've seen I feel like the new 5 the gen tablets are all the same, can't confirm it yet but if so you should be able to follow the instruction given on the kindle 7 5th gen able about booting up into twrp or cm and installing a new Rom. I'm not sure if I want to do this though. Adw launcher feels empty without widgets though
Click to expand...
Click to collapse
But do not follow my advice unless you know what your doing. Always back up everything.

kanderson88 said:
After messing around the go launcher ex is a little buggy. I might try another, currently trying to figure out how to get widgets to work and once I do ill let you know the system file.
Any ideas what I should add to the fire os? Current goal is widgets
Click to expand...
Click to collapse
I can confirm that with the latest KingRoot apk on my HD8 (5th Generation) the rooting worked. As a launcher I had before Nova and Google Now via Play Store installed. I prefer the Google Now Launcher. The Home button, the Wallpaper and the Widgets are working. Thanks for the hot rooting tip.

schr01 said:
I can confirm that with the latest KingRoot apk on my HD8 (5th Generation) the rooting worked. As a launcher I had before Nova and Google Now via Play Store installed. I prefer the Google Now Launcher. The Home button, the Wallpaper and the Widgets are working. Thanks for the hot rooting tip.
Click to expand...
Click to collapse
Does your google play store actually work? I can get it to load but once the front page is loaded, I can't search or get anything else to load on google play. It's just a continuous load. Could you let me know what framework you have. Also I cant get widgets to work on mine. Have Adw and cant get google now to work. If you can I think you should make a posts on the HD 8 and 10 thread letting us know what you did to get where you are now. Anyways I'm going to message you in a lil bit.

So I got google launcher installed and moved it to system app and now widgets work. Only problem I'm facing now is getting google play to stay working. Sometimes log me out or just stops loading traffic to the app. Any ideas? I've uninstalled it and reinstalled it but still no.

kanderson88 said:
So I got google launcher installed and moved it to system app and now widgets work. Only problem I'm facing now is getting google play to stay working. Sometimes log me out or just stops loading traffic to the app. Any ideas? I've uninstalled it and reinstalled it but still no.
Click to expand...
Click to collapse
I had in the past the same problems. After I had uninstalled the complet apk's and reinstalled the following apk's:
Google Account Manager_4.0.3-239410.apk,
Google Play services_4.0.34 (924341-38).apk,
Google Services Framework 4.0.4-338691.apk ,
and
Google Play Store 4.4.21.apk,
I had no trouble. The Google Play Store worked now fine on my HD8 with firmware 5.1.1.
Remark: You can download the apk' from this link: https://drive.google.com/file/d/0B3yLoupCwoyrSzJEMHc3UTkzam8/edit?pref=2&pli=1

schr01 said:
I had in the past the same problems. After I had uninstalled the complet apk's and reinstalled the following apk's:
Google Account Manager_4.0.3-239410.apk,
Google Play services_4.0.34 (924341-38).apk,
Google Services Framework 4.0.4-338691.apk ,
and
Google Play Store 4.4.21.apk,
I had no trouble. The Google Play Store worked now fine on my HD8 with firmware 5.1.1.
Remark: You can download the apk' from this link: https://drive.google.com/file/d/0B3yLoupCwoyrSzJEMHc3UTkzam8/edit?pref=2&pli=1
Click to expand...
Click to collapse
Thanks. I'm gonna have to try this once I get off work. Thank you again

kanderson88 said:
After messing around the go launcher ex is a little buggy. I might try another, currently trying to figure out how to get widgets to work and once I do ill let you know the system file.
Any ideas what I should add to the fire os? Current goal is widgets
Click to expand...
Click to collapse
Please try nova.

schr01 said:
I had in the past the same problems. After I had uninstalled the complet apk's and reinstalled the following apk's:
Google Account Manager_4.0.3-239410.apk,
Google Play services_4.0.34 (924341-38).apk,
Google Services Framework 4.0.4-338691.apk ,
and
Google Play Store 4.4.21.apk,
I had no trouble. The Google Play Store worked now fine on my HD8 with firmware 5.1.1.
Remark: You can download the apk' from this link: https://drive.google.com/file/d/0B3yLoupCwoyrSzJEMHc3UTkzam8/edit?pref=2&pli=1
Click to expand...
Click to collapse
Thanks for supplying the APKs. This should help me as right now infos are jumbled all across this forum and need to be cleaned up a bit.
I'd love to do a nice/clean .bin people can flash after the dust has settled. Hopefully without kingroot. Wish I knew the kingroot devs.

Also, everyone needs to slow down. We have root in a way, but we need to make sure everyone is on the same page. Don't let this forum become a mess.
Right now, it is a huge mess.. The original root thread is smart to post on and maybe the tips and tricks thread. Stop spreading things out too much. We need it all in one place, really

technope said:
Also, everyone needs to slow down. We have root in a way, but we need to make sure everyone is on the same page. Don't let this forum become a mess.
Right now, it is a huge mess.. The original root thread is smart to post on and maybe the tips and tricks thread. Stop spreading things out too much. We need it all in one place, really
Click to expand...
Click to collapse
Yeah sorry I'm trying my best to clean up my thread a little and easy to read as much as possible. Also I figured out how to fix google play if it isn't working. Look at tips,Tricks, and the Root thread if anyone is wondering.

[TOOLS Fire HD 6&7 ] Rooting, Gapps, Launchers, Block OTA & Ads + More

Download the latest tools from the AFH link near end of post. It includes the changes in the attached "jobs" zip. You only need "jobs" if you downloaded the tools before May 11
EDIT May 29: Playstore is currently unreliable. Until updated, use the workaround here.
UPDATE May 17: Install Other Launcher and Install Kingroot tools may not complete if Windows username has spaces. I'll fix in next update. Until then, if your username has spaces, use this fix.
Here are tools for the 2014 Fire HD 6 and 7. A little late, I know, but some of you who still troll the forums may find them handy. Download the tools from AFH link, extract and run RUNME.bat.
IF YOU PLAN TO ROOT, TURN OFF WIFI NOW!
Tested working on OS 5.1.2.1 and below, except:
- Current Kingroot can't root 5.1.2.1. You need to downgrade. See "ROOT OS 5.1.2", below.
- OS 4: Only OTA blocking is implemented in the Block/Unblock jobs. [5/13/16 UPDATE: Also, Play Store isn't working on OS 4.
.. I probably won't fix it unless there's some demand. Try the video guide here. OS 4 users, also see post #11 for useful info about custom launchers.]
THE TOOLS
Install Play Store
Install Nova Launcher to /priv-app [root]
Install Other Launcher to /priv-app [root]
Uninstall priv-app Launchers [root]
Install Apps
Block/Unblock: OTA, ADS, AMAZON LAUNCHER, APPSTORE, AMAZON SEARCH [root]
Root Checker
Device Info
Root Tools
Install Kingroot ~ Root ~ Block OTA
Replace Kingroot with SuperSU [root]
DESCRIPTIONS
Before running a job, look here for any tips and instructions. This info is also in the readme.txt in the zip​
INSTALL PLAY STORE - Like it says. Works on both rooted and unrooted OS 5. Not for OS 4. EDIT May 29: Playstore is currently unreliable. Until updated, use the workaround here.
INSTALL NOVA LAUNCHER - Installs Nova to /system/priv-app so widgets work. If you just rooted, make this your first custom launcher. You can replace it or add a different one later.
INSTALL OTHER LAUNCHER Installs the launcher app in user_launcher folder to priv-app. Get the apk for the launcher you want (from apkmirror.com for example) and put it into the folder and run the job. EDIT 5/16/2016: Filenames must end with ".apk" No spaces allowed; replace with "_". (The tool will find spaces and pause while while you fix.)
HOW TO INSTALL GOOGLE NOW (also in Readme.txt):
It's much easier to install Google Now if Amazon is blocked, and you need a custom launcher to do that.
1. If you don't have a custom launcher installed, use Install Nova tool (installs Nova and blocks Amazon)
If you have a custom launcher, block Amazon so your custom launcher is running.
2. Get Google Now (small) from apkmirror.com, e.g., put into user_launcher folder and run Install Other Launcher job.
You'll boot to your "other" launcher
3. Run Google Now in app drawer and:
If prompted to Update Google App (Get it from Google Play), do it.
If prompted that other launcher is default, tap link to go to Amazon Settings. In Apps & Games>Manage all Applications: Swipe to All, scroll to your other launcher, tap it and see if "Launch by Default" is on. If yes, Clear Defaults. If no, go to your launcher settings and see if you can turn off default there.
Some launchers don't give up their default easily. If pressing home key doesn't show "Select Home App" after doing the above, run Block/Unblock tool and switch to Amazon. Then block Amazon again. After restart, press home key and you'll get "Select Home App" and be able to choose Google Now.
UNINSTALL LAUNCHERS - Uninstalls and deletes everything associated with a launcher installed to /priv-app. If multiple, prompts you to choose the one to uninstall.
INSTALL APPS - Installs all the apps in the user_apps folder. Put the apks into the folder and run the job. Filenames must end with ".apk" No spaces allowed; replace with "_". (The tool will find spaces and pause while while you fix.) Don't install a launcher with this; use one of the launcher tools.
BLOCK/UNBLOCK - OTA, ADS, AMAZON LAUNCHER, APPSTORE, AMAZON SEARCH
Except for OTA, these work only on rooted OS 5. OTA does a soft block on unrooted OS 4, hard block on rooted.
OTA: Disables update packages and renames DeviceSoftwareOTA.apk for a "hard" block. Unblock reverses it.
ADS: Blocks/unblocks the lockscreen ads.
AMAZON LAUNCHER: Block disables the stock launcher (Amazon UI) and the Appstore, which forces the home key to use your custom launcher. Unblock switches you to Amazon. Checks for custom launcher before disabling Amazon. Black screen with multiple custom launchers: If you haven't set a default launcher, disabling Amazon will boot to black screen. (System doesn't know which launcher to use.) Press home key (circle at bottom) for launcher choices. TIP: To easily switch between your launcher and Amazon, use @bibikalka's guide here to set up "one-tap switching" from launcher home screen.
APPSTORE: Blocks the appstore so in-app links take you to the Play Store (instead of throwing that stupid Appstore prompt). Amazon complains bitterly if you run this from Amazon UI, so use it at your custom launcher or just use the Amazon launcher block.
AMAZON SEARCH: If you have Google Search installed, blocking Amazon Search makes your launcher search bar use Google instead of Amazon shopping.
DEVICE INFO - Just some specs that I find interesting. Lazy man's way to find out which tablet is plugged in, OS it's running, whether rooted . . .
INSTALL KINGROOT, ROOT, BLOCK OTA - Installs Kingroot, prompts you through rooting and blocks OTA updates.
- Installs kingroot v.4.8.5 by default.
- You can skip installation if Kingroot already installed
- You can install a later version if available: Check for new versions here: http://forum.xda-developers.com/android/apps-games/one-click-root-tool-android-2-x-5-0-t3107461
ROOTING AND UPDATES: An update file can download while you're rooting. The Kingroot tool prevents it from installing as soon as you press Enter to tell the tool you're rooted. Then it looks for any downloaded file and if it finds one it tells you where it is and prompts you to delete.
Amazon says that updates install when the the device is not being used, but be aware that on OS 5 there's some risk. To minimize the risk, never leave the tablet idle while rooting. Just keep running Kingroot until root is successful and then press Enter to block installation of any download. (These instructions are in the tool.) To eliminate all risk, you can downgrade and root OS 4.5.3. On OS 4 the tool blocks update installation before rooting. (There's no way to do this on OS 5.) From OS 4.5.3, you upgrade with root in TWRP per bibikalka's root Tut.
True story: Kingroot once rebooted 5 times and told me "Root Failed" 3 times before finally succeeding. An update had downloaded to /cache, but the kingroot tool successfully blocked installation and found the file, which I deleted. So, although it's possible you could get upgraded, as long as you keep the tablet busy trying to root and then press Enter as soon as you're rooted, it's very unlikely.
REPLACE KINGROOT WITH SUPERSU - Installs W0lfDroid's sh script and prompts you through using it to replace Kingroot.
I reviewed and tested the script and it does (only) what it says: Removes all Kingroot (except Purify app, which tool uninstalls) and installs SuperSU. The tool uses SuperSU v. 2.4.6 for OS 5 (known working on OS 5.1.2) and SuperSU v. 2.4.9 for OS 4 (because 2.4.6 didn't seem to work).
FULL DISCLOSURE: I lost root one time after running this on OS 4. I think the problem was SuperSU 2.4.6 and that's why I changed it. I've tested many times and this only happened once, but you should know it happened. AFAIK W0lfDroid script is still the best free tool for the job.
ERRORS: Script was written to remove Kingroot from multiple android versions, so it tries to remove Kingroot files that don't exist on Lollipop. THIS PRODUCES LOTS OF ERRORS. THAT'S OK. I left in all commands so it will work on OS 4, too.
USE THIS SOON AFTER ROOTING. W0lfDroid's script should work fine even with root apps installed, but all I know for sure is it runs quick and easy on a "fresh" system.
ADB Sideload
There's an adb-sideload job in the jobs folder. I didn't put it on the menu because it uses commands that may not run on some systems. Also, if you know what you're doing, it's probably faster to manually sideload an update. If someone wants to try it, put the update bin file into adb_sideload folder and run sideload.bat.​WINDOWS TESTING: Script was tested on English-language versions of Win 7 Pro and Home. Some testing on Win 10. (Thanks @SpaceBananas!) There's nothing that can hurt your tablet, but there may be kinks to work out based on Windows version. Hope a tester will work with me to help make the tools accessible to everyone. Thanks!
ADB DRIVERS REQUIRED: Try the guide in first link below. If problems, try the second.
Guide: http://forum.xda-developers.com/fir...ivers-fire-t3189000/post62561840#post62561840
Other options: http://forum.xda-developers.com/showpost.php?p=63072252&postcount=2
ROOT OS 5.1.2
IF YOU PLAN TO ROOT, TURN OFF WIFI NOW!
ROOT GUIDE: Follow this guide to use Kingroot and the root tools to set up your tablet.
At this time, Kingroot can only root OS 5.1.2 (February 2016) and below.
You can downgrade OS 5.1.2.1 (March 2016) to 5.1.2 and root, as explained in Root Guide, but this is an exception!
In general, never downgrade in order to use Kingroot. It's the fastest way to a brick!
You may be able to safely downgrade a higher OS to OS 4.5.3, root, and then upgrade in TWRP per @bibikalka's root Tut. Before trying this on an OS later than 5.1.2.1, make sure the tutorial says it's safe.
DOWNLOAD THE TOOLS FROM AFH ➔ . FireHD_TOOLS v 1.2
Update as of 5/11/16
➔ If you got the tools before the update, just replace the jobs folder in FIREHD_TOOLS with the one in attached "jobs_v1.x.zip"
Change Log
5/11/2016 - v1.2: Updated sideload.bat. (Missed the Find/Findstr fixes.)
5/10/2016 - v1.1: Fixed "No such file or directory" and "Permission denied" errors for users with *nix Find command installed
.

Nice Work!

@DoLooper - Magnum Opus, no less !
Why version 0.1 ??? The first release - solid 1.0 !!!

Updated. See OP.
Guys, I could use some feedback. Tools are getting downloaded a lot. Anybody using them? Are they helpful? Problems? Wishes? Anything? Thanks!
.

Updated again <sigh>. Sideload tool didn't get updated in v1.1. Apologies to those who downloaded the jobs zip.

DoLooper said:
Updated. See OP.
Guys, I could use some feedback. Tools are getting downloaded a lot. Anybody using them? Are they helpful? Problems? Wishes? Anything? Thanks!
.
Click to expand...
Click to collapse
Thanks DoLooper.
I tried these tools on my Fire HD 7 running 4.5.5.1 rooted with KingRoot.
I was able to use the script to successfully switch from KingRoot to SuperSU as well as to install Nova Launcher.
However, I had issues with the script elsewhere.
The play store seemed to install okay and it let me put in my google account info. After that, things went down hill. I was able to open the Play Store app without it crashing, but I just kept getting the "Error retrieving information from server. [RH-01]" message . I tried numerous things to correct this, but nothing seemed to work. In the end, I downgraded to 4.5.5, wiped data, cache and dalvik, and then flashed gapps via TWRP. This worked out, so all is good now.
I also had trouble with blocking the default launcher. Nova seemed to install okay, but the default launcher still worked and was a constant nag with each press of the home button. I fixed this by freezing the default launcher via Titanium Backup.
I don't know if these issues are particular to 4.5.5.1, or if I'm just unlucky. Regardless, I still appreciate your effort for putting this together. :good:
I'm currently trying to get wallpapers and widgets to work on the Nova launcher with no success. I tried the fixes intended for earlier Kindle models and (not surprisingly), they didn't work. Specifically, I tried Stunt's Wallpaper Fix and Kindlefree from the app store.
Any ideas where I should look for guidance on making Wallpapers and Widgets work?
Thanks again!

notorious.dds said:
Thanks DoLooper.
I tried these tools on my Fire HD 7 running 4.5.5.1 rooted with KingRoot.
I was able to use the script to successfully switch from KingRoot to SuperSU as well as to install Nova Launcher.
However, I had issues with the script elsewhere.
The play store seemed to install okay and it let me put in my google account info. After that, things went down hill. I was able to open the Play Store app without it crashing, but I just kept getting the "Error retrieving information from server. [RH-01]" message . I tried numerous things to correct this, but nothing seemed to work. In the end, I downgraded to 4.5.5, wiped data, cache and dalvik, and then flashed gapps via TWRP. This worked out, so all is good now.
I also had trouble with blocking the default launcher. Nova seemed to install okay, but the default launcher still worked and was a constant nag with each press of the home button. I fixed this by freezing the default launcher via Titanium Backup.
I don't know if these issues are particular to 4.5.5.1, or if I'm just unlucky. Regardless, I still appreciate your effort for putting this together. :good:
I'm currently trying to get wallpapers and widgets to work on the Nova launcher with no success. I tried the fixes intended for earlier Kindle models and (not surprisingly), they didn't work. Specifically, I tried Stunt's Wallpaper Fix and Kindlefree from the app store.
Any ideas where I should look for guidance on making Wallpapers and Widgets work?
Click to expand...
Click to collapse
Thanks for feedback. Tools apparently need work for OS 4.5.5.1. I tested pretty well on 4.5.3 and 4.5.5, but not 4.5.5.1. There may be some peculiarity there.
- The play store error has been reported on some 2015 Fires (using a different tool, but same method to install). It's unclear why it happens on some devices and not others, and they haven't found a fix, but it may be an OS 4 issue on the Fire HDs. I'll look into it.
- Nova & stock launchers: The block on stock launcher didn't work because it isn't implemented for OS 4. As mentioned at top of OP, only OTA block is available for OS 4. I'll need to add it in an update. Hadn't thought about need for it when using the Nova tool.
Would you please look in /system/priv-app folder and see if com.teslacoil.launcher.apk is at the bottom of directory? If so, are perms set to rw- r-- r--? Let me know and we'll proceed from there to get you widgets. Thanks.

DoLooper said:
Thanks for feedback. Tools apparently need work for OS 4.5.5.1. I tested pretty well on 4.5.3 and 4.5.5, but not 4.5.5.1. There may be some peculiarity there.
- The play store error has been reported on some 2015 Fires (using a different tool, but same method to install). It's unclear why it happens on some devices and not others, and they haven't found a fix, but it may be an OS 4 issue on the Fire HDs. I'll look into it.
- Nova & stock launchers: The block on stock launcher didn't work because it isn't implemented for OS 4. As mentioned at top of OP, only OTA block is available for OS 4. I'll need to add it in an update. Hadn't thought about need for it when using the Nova tool.
Would you please look in /system/priv-app folder and see if com.teslacoil.launcher.apk is at the bottom of directory? If so, are perms set to rw- r-- r--? Let me know and we'll proceed from there to get you widgets. Thanks.
Click to expand...
Click to collapse
Thanks for the help!
I found the com.teslacoilsw.launcher-1.apk file, but it's in my /data/app folder... and it is chmod'ed to 644.
Also, I did successfully install the AppWidgetPicker.apk and LiveWallpapersPicker.apk files to /system/app using the "kindlefree" app, but I think that about all the app did. These files are also chmod'ed to 644.

notorious.dds said:
Thanks for the help!
I found the com.teslacoilsw.launcher-1.apk file, but it's in my /data/app folder... and it is chmod'ed to 644.
Also, I did successfully install the AppWidgetPicker.apk and LiveWallpapersPicker.apk files to /system/app using the "kindlefree" app, but I think that about all the app did. These files are also chmod'ed to 644.
Click to expand...
Click to collapse
I've been using OS 5 for too long! Forgot you can't get wallpaper on OS 4 without fussing. It's unclear from your post: Did the pickers get wallpaper to work? This is the way we did it back when we always booted twrp and installed xposed: http://forum.xda-developers.com/fire-hd/general/how-to-wallpaper-custom-launcher-t3123009
As to widgets: What I meant is, you should have /system/priv-app/com.teslacoil.launcher_4.2.2.apk. Do you? I just retested this on 4.5.3. Nova (com.teslacoil.launcher_4.2.2.apk) got copied there and chmod'ed to 644 as it should and widgets are working fine.
No wallpaper is a bad problem, though, and no tool can fix it--unless that LiveWallpapersPicker DID work. Let me know. And let me know about /system/priv-app/com.teslacoil.launcher_4.2.2.apk.
BTW, how come you want to stay on OS 4?

DoLooper said:
I've been using OS 5 for too long! Forgot you can't get wallpaper on OS 4 without fussing. It's unclear from your post: Did the pickers get wallpaper to work?
Click to expand...
Click to collapse
Nope.
DoLooper said:
This is the way we did it back when we always booted twrp and installed xposed: http://forum.xda-developers.com/fire-hd/general/how-to-wallpaper-custom-launcher-t3123009
Click to expand...
Click to collapse
I think I tried that to no avail, but I can't remember exactly which module I used.
DoLooper said:
As to widgets: What I meant is, you should have /system/priv-app/com.teslacoil.launcher_4.2.2.apk. Do you? I just retested this on 4.5.3. Nova (com.teslacoil.launcher_4.2.2.apk) got copied there and chmod'ed to 644 as it should and widgets are working fine.
Click to expand...
Click to collapse
I think I ended up installing Nova via the app store so that's why it wasn't on the system partition. However, my widgets seemed to work when I checked again. I have no idea why they wouldn't work when I first tried them. I did end up creating two simple scripts via the "Scripter" app that would enable and disable the stock launcher. I put them as widgets on the nova desktop allowing for single click toggling of the stock launcher.
DoLooper said:
No wallpaper is a bad problem, though, and no tool can fix it--unless that LiveWallpapersPicker DID work. Let me know. And let me know about /system/priv-app/com.teslacoil.launcher_4.2.2.apk.
Click to expand...
Click to collapse
No, nothing seemed to fix the wallpaper... always black. Am understanding this correctly that the wallpaper works on this thing if I load Lollipop?
DoLooper said:
BTW, how come you want to stay on OS 4?
Click to expand...
Click to collapse
I didn't want to fiddle around with change the bootloaders every time I wanted into TWRP. At this point, it doesn't matter anyway... I hard bricked the device by flashing the 5.2.0 stock recovery last night
The post about using this to revert to stock should be edited or removed. It's bad.
The only reason I was trying to revert to stock was that I ended up getting into a situation where the stock launcher would continue looping back to the Welcome/select language screen. I wiped cache, data, and dalvik and reflashed the 4.5.5 rom which didn't fix it. I even tried that same approach including a wipe of system... same result. I was quite surprised to see the problem continue even after wiping everything. At that point I figured I go back to full stock and start over... BAD IDEA.
Anyway, I ordered a new one and it should be here tomorrow. I'm now curious if it's possible to recover the bricked device via the UART port on the motherboard. We'll see.:fingers-crossed::fingers-crossed:

notorious.dds said:
. . .
I think I ended up installing Nova via the app store so that's why it wasn't on the system partition. However, my widgets seemed to work when I checked again. I have no idea why they wouldn't work when I first tried them. I did end up creating two simple scripts via the "Scripter" app that would enable and disable the stock launcher. I put them as widgets on the nova desktop allowing for single click toggling of the stock launcher.
No, nothing seemed to fix the wallpaper... always black. Am understanding this correctly that the wallpaper works on this thing if I load Lollipop?
I didn't want to fiddle around with change the bootloaders every time I wanted into TWRP. At this point, it doesn't matter anyway... I hard bricked the device by flashing the 5.2.0 stock recovery last night
The post about using this to revert to stock should be edited or removed. It's bad.
The only reason I was trying to revert to stock was that I ended up getting into a situation where the stock launcher would continue looping back to the Welcome/select language screen. I wiped cache, data, and dalvik and reflashed the 4.5.5 rom which didn't fix it. I even tried that same approach including a wipe of system... same result. I was quite surprised to see the problem continue even after wiping everything. At that point I figured I go back to full stock and start over... BAD IDEA.
Anyway, I ordered a new one and it should be here tomorrow. I'm now curious if it's possible to recover the bricked device via the UART port on the motherboard. We'll see.:fingers-crossed::fingers-crossed:
Click to expand...
Click to collapse
Sorry to hear about the brick. Good thing Amazon is patient with us.
Yes, wallpaper works fine on OS 5. [For others who read this, on OS 4 the only way to get wallpaper is with Xposed (installed in TWRP) and the kindleBG module in the link I posted above. And BTW, although the tools don't block OS 4 Amazon launcher ATM, it can be done manually. Commands are here.]
Thanks for your input. Play store didn't work for me either this time, despite earlier success. Everything else except the launcher block (and other non-OTA blocks) does work, so for now I'm just going to edit post and see if there's any other interest in play store on OS 4. (I trust you'll get OS 5 on replacement or will want to update to it.)
As to TWRP: Once tablet is set up, booting TWRP isn't needed much except for upgrading. and bibikalka gives us lots of options for doing it.
Let us know if anything comes of UART port tests. You'd be the hero of the community!

Workaround for Windows username with spaces
The Install Other Launcher and Install Kingroot jobs may not complete if your Windows username has spaces in it. I'll fix this in next update. Meanwhile here's the workaround:
1. Right-click RUNME.bat and choose Edit. [file opens in Notepad]
2. Add a blank line under :: Set paths and run menu.
3. Type: SET "username=abc"
4. Make sure this section of RUNME looks like below and then save and close Notepad
Code:
:: Set paths and run menu.
SET "username=abc"
SET "main=%CD%\"
SET "jobsdir=%main%jobs\"
[remaining code]
This changes the username only for the tools. The rest of Windows continues to use the real username.

I'm getting ready to update. Please let me know if you found any problems.

Used the tool on my Fire HD 6 (4th Gen) running a Rooted OS 5.1.2.1 to install a new launcher and block OTA's, ads, fire launcher, appstore, and Amazon search. Everything worked without issue! Thanks for the awesome and simple to use tool! Tablet is now almost pure Android. Great work!!!
Sidenote: Used bibikalka's TUT (http://forum.xda-developers.com/fire-hd/general/how-to-upgrade-to-lollipop-root-gapps-t3163950) on my Fire HD 6 that was currently running Fire OS 4.5.3 with TWRP Recovery to obtain a Rooted Fire OS 5.1.2.1..

I adb'd the 5.1.2 upgrade to my slab this way.
$ adb push update-kindle-20.5.4.2_user_542168620.bin /sdcard/
3047 KB/s (663908627 bytes in 212.722s)
My OS is FIRE OS 5.1.2 Build Date March 31, 2016 1:37 AM.
I tried and got an error to the effect, "cannot upgrade because the upgrade you are trying is older than the one you have".
So I'm probably running an even later version of 5.1.2 where they blocked that loophole.
I'm just going to by a cheap Chinese slab and root that.

wallywallywally said:
I adb'd the 5.1.2 upgrade to my slab this way.
$ adb push update-kindle-20.5.4.2_user_542168620.bin /sdcard/
3047 KB/s (663908627 bytes in 212.722s)
My OS is FIRE OS 5.1.2 Build Date March 31, 2016 1:37 AM.
I tried and got an error to the effect, "cannot upgrade because the upgrade you are trying is older than the one you have".
So I'm probably running an even later version of 5.1.2 where they blocked that loophole.
I'm just going to by a cheap Chinese slab and root that.
Click to expand...
Click to collapse
use adb sideload in Stock recovery
Sent from my KFFOWI using XDA Labs

sd_shadow said:
use adb sideload in Stock recovery
Sent from my KFFOWI using XDA Labs
Click to expand...
Click to collapse
Yuh, I used sideload AND IT WORKED!!
I also have a fire 5th generation. Does the same procedure work for that, assuming I use the proper 5.1.2 for that device: https://kindle-fire-updates.s3.amaz...ate-kindle-global-37.5.4.2_user_542168620.bin

wallywallywally said:
Yuh, I used sideload AND IT WORKED!!
I also have a fire 5th generation. Does the same procedure work for that, assuming I use the proper 5.1.2 for that device: https://kindle-fire-updates.s3.amaz...ate-kindle-global-37.5.4.2_user_542168620.bin
Click to expand...
Click to collapse
yes
Sent from my KFFOWI using XDA Labs

Confirmed, this procedure worked for Fire (5th generation), however the amazon update file is different (see a few posts back)

I just got a fire HD 6 (4th Gen) with the 4.5.2 OS.
Everything I see talks about 4.5.3 and later. I have not turned on wifi, so basically in a holding pattern for now. I want to root/twrp and maybe a custom rom.
Can some give me advice on the best path to take? Should I upgrade then root? Or root then upgrade? Any advice is appreciated.

FireTV-Settings 3.0 Mod Root works on Tank and Mantis without Amazon Launcher

!! deprecated !!

0815hoffi said:
FireTV-Settings 3.0 Mod Root works on Tank and Mantis without Amazon Launcher
based on https://github.com/rainman74/FireTV-Settings/releases
install as normal APK.
Root is needed.
NewSettingsGerRoot.apk = German
NewSettingsEngRoot.apk = English
FireTV-SettingsGer.zip = Android Studio Zip German
FireTV-SettingsEng.zip = Android Studio Zip English
Feel free to customize it for whatever works best for you! ...
Click to expand...
Click to collapse
Ok so the apk file is unnecessary with root since the zip is in charge of that correct? This is actually interesting considering that the Amazon Launcher being disabled with root therefore losing functionality to accessing settings unless you were to use adb commands.
Edit: the apk was supposed to be installed, works 100%

Skel40 said:
Ok so the apk file is unnecessary with root since the zip is in charge of that correct? This is actually interesting considering that the Amazon Launcher being disabled with root therefore losing functionality to accessing settings unless you were to use adb commands.
Edit: the apk was supposed to be installed, works 100%
Click to expand...
Click to collapse
Questions...
So does the Zip need to be flashed?
Then install the APK?
Is the Amazon launcher disable by doing this, or do I have to disable that myself?
Can you easily remove it?

The Zip file is for customize.
SourceCode for Android Studio.
You must disable it .

OK so disable
com.amazon.tv.launcher
?
1. install APK
2. Flash zip ( for customize if you want)
3. disable launcher
The zip, what does it modify and how do you go back?
Sorry for the questions, just want to know what to expect if i have an issue...

Install other Launcher.
For mantis maybe you need FTVLaunchX to start the alternate Launcher.
#adb shell pm disable com.amazon.tv.launcher
Install apk to access the settings without amazon Launcher.
The Zip the SourceCode to build apk.
I hope it is understandable now

Thanks bro, this works perfect with ATV Launcher 0.1.2 now i can access amazon built-in apps on 4k stick.

Thanks for this.
Couple of queries:
Lots of icons on my custom launcher. But all start off at sleep. Is this normal? If so why so many icons?
The command to disable the amazon launcher is not working and I do have root. Any ideas?
Edit: Not to worry about the above. I found a new version that gives me just the one icon
Also found the instructions to delete the amazon launcher so that is good.
Only problem that some might have is installing new apps from the amazon marketplace (or whatever they call it).
Any ideas about how to do this?

Use this Version.
https://forum.xda-developers.com/showpost.php?p=82368799&postcount=1
Amazon Market is not working.
You must sideload the apps.
Also you can push the apps over the Amazon Website to your Stick.
App Updates should be installed automatic.

0815hoffi said:
Use this Version.
https://forum.xda-developers.com/showpost.php?p=82368799&postcount=1
Click to expand...
Click to collapse
Thanks for that.
I manage a lot of these sticks. Most I know the Amazon accounts for so will use the web site to push to them if they request new apps.
I will ask for the other account details but if they wont provide them I will send them to the website to install themselves if they want new apps.
It seems Amazon pushed out a new prime Video app today (or I was told about it today) that asks it you want to install it.
Was told it no longer works with this setup if it is installed. Was fine yesterday and no prompt to update then.
Might be a problem with the Prime Video app in general and not this setup, but all my sticks are running these fixes now.
Just tested on one and it is true. Trying to open Prime Video does nothing. Tried both the icons for it (one never worked but now both do not).
Will see if I can roll it back (once I find the original apk).
Thanks for this. So nice not to see the Amazon Launcher at all now.