Help: endless Launcher force close loop - Kindle Fire General

Short story: I installed LauncherPro, rebooted, unlocked screen, was presented with the option to choose the stock Fire launcher or LauncherPro, I set as default and chose LauncherPro (mistake: I checked set as default, and i should know better than to ever trust an untested launcher this way) Well, it force closes, repeatedly, and I can not access anything to change the default back to kindleFire launcher, because all i can do is keep hitting the force close option over and over, or reboot and force close over and over. Basically, I cant get past the lock screen to do anything because of the endless force close loop.
How can i fix this? (hopefully i dont have to "unbrick" as per instructions here: http://forum.xda-developers.com/showthread.php?t=1356257)
Long story: I just rooted my new Kindle Fire as per instructions from http://www.kindlefirewire.com/
and installed android market apk files via command prompt "push" command. However, in order to access my android market install, the next instruction was to install the GoLauncher, and here is where problems were unforeseen (as per kindlefirewire instructions). GoLauncher does not show up in an amazon market search for those who have only the kindle device registered. So I had to go to the launcher website to get the .apk. Well, I prefer LauncherPro on my phone so I opted to DL and use LauncherPro instead of GoLauncher.

fixed!
Nevermind; I fixed it!!
see ya'll later!!!! (just kidding -- i hate when ppl say they fixed it and dont say how)
Here is what I did: I pushed the GoLauncher.apk file the same way I pushed the android market apk files and rebooted... this forced a new launcher to install and therefore the default launcher was unset, allowing me to once again choose my launcher of choice.
It's amazing how much a newbie can learn on his first root!
Instructions for "push"ing reposted from KindleFireWire's website:
adb remount
adb push c:\market\GoogleFeedback.apk /system/app/GoogleFeedback.apk
adb push c:\market\GoogleServicesFramework.apk /system/app/GoogleServicesFramework.apk
adb push c:\market\Vending.apk /system/app/Vending.apk
adb reboot

Nice save man. Good work.
Sent from my Kindle Fire using Tapatalk

Related

[Q] I need help with Ice cream Sandwich loop

I updated my new kindle fire, then rootet it successfully.
After that i installed the Ice Cream Sandwich 4.0 and made it the default launcher.
But this failed, when i now start the kindle fire i get caught into the loop of this error:
! Sorry
The application Ice Cream Sandwich 4.0 (process androd.process.acore) has stopped unexpectedly. Please try again. [Button: force close]
Which i can press, and then the loop starts again.
I am a noob, so please how do i get rid of this launcher ? I could need a reset or factory default or whatever, but the normal ways dont work, because i cant reach them anymore. Any Ideas how to fix this ?
/edit: I have access to my device with adb shell. so i think i can somehow change the default launcher, if someone tells me which file to change because i have no idea which is the right.
You need to figure out what the package name is "adb shell pm list packages" without quotes. Once you figure out what the package name is you can "adb uninstall name.of.package"
Hard reset it with power button.
Guide - How to hard reset Kindle Fire?
Fyi.....I just tried the hold power for 20 seconds hard reset, and it doesn't work......
Sent from my Kindle Fire using Tapatalk
I've had this problem with a different launcher and posted my solution here : http://forum.xda-developers.com/showthread.php?t=1361138
... don't worry... you can fix it... all you need to do is install another launcher or uninstall the ICS launcher... and you may be wondering how you can do that if you can't get to a usable screen.
You can still install/uninstall apps using the adb service you used while rooting. FoxDog66 mentioned how to do this if you know the package name. In my case, I could not find out the package name of the offending package, so what I did was install another launcher via the same method I installed my google apps to the sys/apps folder. with another launcher installed, I get a choice again which launcher should run when turning on.
I suggest you try foxdog's suggestion first, but if you can not find the package name then get another launcher.apk install file like GOlauncher or ADW Launcher and push or install that app the way you see google apps being pushed via the following method:
Download GOlauncher http://61.145.124.93/soft/3GHeart/golauncher/v2.68/go_launcher_ex_v2.68.apk
now make it a system app:
adb remount
adb push c:\androidApps\go_launcher_ex_v2.68.apk /system/app/go_launcher_ex_v2.68.apk
adb reboot
After reboot you should be able to choose your launcher of choice. Don't make anything default until you know you like it!!!
Now that GO Launcher just installed via my method makes it a system app. You can't uninstall system apps in the normal way, so use a program like Titanium Backup to make that pushed launcher app a NON-system app (moves it and makes it easy to uninstall the way other apps do). Titanium Backup is just a great program to have if rooted.
Good Luck.
how to uninstall buggy launcher which is set to default
Thanks for helping me.
Yes thats exactly my problem and i am now trying to follow your instructions.
The hardware reset works, but it will not get rid of the launcher.
So i try to find out the right application name to uninstall it. But *blush* i have not idea which is the right name and i dont want to uninstall something randomly.
I have some very basic skills with linux which i uses 10 years ago or so, so i am able to make a list which i attached here.
OK, i am now trying to do this:
adb remount
adb push c:\androidApps\go_launcher_ex_v2.68.apk /system/app/go_launcher_ex_v2.68.apk
adb reboot
but "adb remount" gives me back a
remount failed: Operation not permitted
I need to look closer how to install and uninstall packages now.
/edit: what i can do is:
adb shell
$
su
#
so this looks like to me that i am superuser. I also see the file system, and i can do some stuff with this shell, but its very limited because this shell is different from the shells i knew long time ago.
/edit:
ok, found something:
i am in the file system in
/data/app
here i have 3 apk:
net.adisasta.androxplorer-1.apk
mobi.SyndicateApps.ICSv2-1.apk
mobi.SyndicateApps.ICS-1.apk
and i think this is the package i installed.
/last edit:
OK folks. SUCCESS..
I just did adb uninstall mobi.SyndicateApps.ICSv2 and i immidiatly got success and got rid of the fail launcher.
VERY NICE and a warm THANK YOU for helping me.
I think i will try more now -- hehe.
Just tasted some blood now. Probably i will be soon here with the next problem. But i really appriciate your help. Hopefull soon i will be more into it and be able to help other noobs, too.
Also if someone needs german help because of language barrier, i can help translating.
Best Regards
Usurpine
Glad you got it fixed
A few tips.... adb remount just remount's the system partition read-write which isn't needed unless the app is installed to /system/app (it also does not work. It does work with doomlord's kernel, i think because of the insecure ramdisk)
The "./" part of your command just means to run in the current directory, if you have fastboot or adb in path then you don't need that part and you can also run the commands from any directory. if you don't have them in path then you would need to have what you wanted to flash, boot, whatever in the same directory as fastboot/adb. To check if something is in path (let's say fastboot) you can type "which fastboot" and it will either tell you where it is (something like ~/Android-sdk/platform-tools/fastboot) or it will say, couldn't find fastboot and it will list out a bunch of directories.
One last thing, you can chain commands together with "&&" so say i want to "fastboot boot newboot.img" i would plug my kindle in, press the disconnect button that pops up on the kindle then type in terminal "adb reboot && fastboot boot newboot.img" if/when the first command runs successfully then it will run the second command. If it does not run successful, it won't run the second command. Also, for me, adb reboot takes a few seconds to work and fastboot waits for the device for a few seconds also.
Hope this is useful, I'm not always good at explaining things. I'm also not a Linux pro lol these are just a few things i have learned that are pretty useful
Well, this is useful. Basically you are talking about how to work with linux. Once i understood that inside my kindle there is just a typical linux i can take one of my old linux books and use any command (like the && and other stuff).
I am not a pro with linux (forgot almost everything) but now i know how to look after it and be able (limited) to use it after some testing.
That said, i now was able to do a lot of funny stuff with my kindle, i installed tons of applications just to look how it works (and it works great) and uninstalled them after that.
Now i can watch movies, listen music, play games and can do almost everything what you normally cannot do with a kindle due to amazons restrictions.
What i want to know is how i can extend the linux inside my kindle so it is using a shell which can do even more stuff, like a ksh (korn shell) or something. A shell with commands like i can find in a "normal" linux installation. Is that possible ?
And how about installing a more linux like grafical userinterface ? Or use the kindle as a normal linux pc, just for fun ?
Ummm..... Have you looked at busybox? It is possible to port command line tools to Android. I've seen things like cURL and lynx that worked. Porting and compiling is a little out of my league (wish it wasn't lol, I'd like a updated cURL binary with https support) i know bash scripts work, I've written a few and "run-parts" (part of busybox) will run a directory of scripts.
You should get into (or look into) custom Android development and/or kernel development. There is a lot that can be done
Help, im a real newbie
usurpine said:
I updated my new kindle fire, then rootet it successfully.
After that i installed the Ice Cream Sandwich 4.0 and made it the default launcher.
But this failed, when i now start the kindle fire i get caught into the loop of this error:
! Sorry
The application Ice Cream Sandwich 4.0 (process androd.process.acore) has stopped unexpectedly. Please try again. [Button: force close]
Which i can press, and then the loop starts again.
I am a noob, so please how do i get rid of this launcher ? I could need a reset or factory default or whatever, but the normal ways dont work, because i cant reach them anymore. Any Ideas how to fix this ?
/edit: I have access to my device with adb shell. so i think i can somehow change the default launcher, if someone tells me which file to change because i have no idea which is the right.
Click to expand...
Click to collapse
Please help me, I really have no experience and I followed a link that made it look very easy to install the ICS Launcher. Now I keep getting that same page and it's driving me up the wall.
I have tried the adb so I can uninstall the faulty apk myself but my mac wont detect it even though it still mounts.
Iv done the adb devices but the list is empty.
Please help me in a very easy way to understand.

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

Go launcher working!!

New method.
I have figured out a safer way to install a custom launcher. Your device still needs to be rooted.
1- Download the launcher of your choice from the Play Store.
2- With a file manager of your choice navigate to data/app folder, this will have all the apk's you've downloaded from the Play Store. (the name of the apk will look different ie: nova launcher is named "com.teslacoilsw.launcher.apk" )
3- Move launcher apk to system/app folder install or reboot(the permissions should already be set to rw-r--r-- so no need to change them)
Personally I like using Rom Toolbox Pro/Lite(can be found in play store, i bought the pro version for more options), I have no affiliation but this app is great and you should check it out. It has every different tool for root users you can think of. In the App Manager section if you long press on any app there is an option to "convert to system app", no moving, cut/paste, or installing.
This should help avoid getting some screwed up apk file from an alternate source and messing up your device.
As always try at your own RISK.
I would recommend checking out this thread before messing around with your device:
http://forum.xda-developers.com/show....php?t=1930656
Can you specify which version of Go Launcher you used and where you obtained the apk from?
After having a near-brick experience attempting to install Go Launcher on my original Kindle Fire last year, I'd like to try it with something known to work.
Thanks in advance.
WillysJeepMan said:
Can you specify which version of Go Launcher you used and where you obtained the apk from?
After having a near-brick experience attempting to install Go Launcher on my original Kindle Fire last year, I'd like to try it with something known to work.
Thanks in advance.
Click to expand...
Click to collapse
I just googled go launcher ex apk. Dont think its ok to specify exactly which site i used(3rd maybe..) but I downloaded v3.13.
I completely feel ya, try at your own risk but definitely worked with mine.
I didn't need to restart but I can confirm go launcher and Nova are working. I'm sure any launcher will
Well maybe some of these other launchers are better but all I want is the android look to tell the truth with icons so ADW Launcher EX without rooting is fine by me to get away from the carousel.
Works great. Thank you.
robertc88 said:
Well maybe some of these other launchers are better but all I want is the android look to tell the truth with icons so ADW Launcher EX without rooting is fine by me to get away from the carousel.
Click to expand...
Click to collapse
For me its not even about which launcher is better they all have pros and cons, but i personally like to use my home button. With this process you can set the launcher as default. Not be bounced back to the stock launcher every time you use the home button and have to reload a custom launcher. Too much of a hassle for me and takes away from the experience.
This method also worked with Go Launcher HD, it looks better then then regular Go Launcher imho.
migjr415 said:
This method also worked with Go Launcher HD, it looks better then then regular Go Launcher imho.
Click to expand...
Click to collapse
It does i agree, but is there a way to hide the notification bar and action bar on hd version?
I didn't find the way to hide NAV bar. All works perfect with Go launcher HD. I am sure that nobody want to try removing NAV bar, cause it is a high risk of breaking your KFHD. Auto-hide in this case would be great, but i can't understand when NAV bar hides. I suppose it hides when there is in exit button, or return button in running apk. IMHO.
How do you change permission on a non rooted device. I downloaded the go launcher hd all v1.17. I tried rebooting and nothing. Can I do this on a stock fire. If so can you provide a step by step. I tried moving the apk to system/apps but says the apk cannot be moved. Thanks
Sent from my Kindle Fire HD using Tapatalk.
Melodycd said:
I didn't find the way to hide NAV bar. All works perfect with Go launcher HD. I am sure that nobody want to try removing NAV bar, cause it is a high risk of breaking your KFHD. Auto-hide in this case would be great, but i can't understand when NAV bar hides. I suppose it hides when there is in exit button, or return button in running apk. IMHO.
Click to expand...
Click to collapse
There is a setting in go launcher ex that allows you to hide nav and notification bars, the little tab is still visible at the bottom or side of screen so you can open them with ease. Gives the tablet a full screen. I love the look of the hd version but would rather have the full screen, wish the would put this option on the hd version
petes67bird said:
How do you change permission on a non rooted device. I downloaded the go launcher hd all v1.17. I tried rebooting and nothing. Can I do this on a stock fire. If so can you provide a step by step. I tried moving the apk to system/apps but says the apk cannot be moved. Thanks
Sent from my Kindle Fire HD using Tapatalk.
Click to expand...
Click to collapse
you cannot change permissions of system files or anything about them unless the device is rooted. This keeps the average person from screwing up there device.
Lockscreen?
Guys, have any of you had luck with the lockscreen for GoLauncher? I tried GoLocker and i had to go through the original Amazon Kindle Fire HD lockscreen and then to the GoLauncher Lockscreen. SO, basically, i had two lockscreens going on at once. Is there a fix for this?
klass
caponea6 said:
Guys, have any of you had luck with the lockscreen for GoLauncher? I tried GoLocker and i had to go through the original Amazon Kindle Fire HD lockscreen and then to the GoLauncher Lockscreen. SO, basically, i had two lockscreens going on at once. Is there a fix for this?
Click to expand...
Click to collapse
Happens with the KF 1st gen also but I never bothered with it. Might want to look into the KF 1st gen and see if anyone found a way around it.
onemeila said:
To get go launcher ex working on the KFHD I took these steps.(On rooted device)
1- download the Go launcher ex.apk from a third party (from play store will not work)
3- change permissions to rw-r--r--
2- using a file manager find the apk and move to system/app folder.
4- reboot the device.
When it reboots there should be a message saying "kindle is upgrading".
Then it should prompt you to pick which launcher you want to use.
If you did not get the latest version you can now go to play store and update.
I assume this will work for other launchers though i have not tried it.
Finally I feel like im using more of an android interface(at least until someone figures out this bootloader problem and i can flash cm10)
I just downloaded go launcher hd and did not change permissions, still worked. Could someone tell me if this is necessary. I just copied the permissions of the stock launcher when i loaded the ex version so i assumed it was necessary they were the same
Click to expand...
Click to collapse
I did step by step like you, but after restarted my KFHD freezing at KF logo, please help me to fix it.
First question, did you install this app in the /system/app folder, AFTER you placed it in there? You must install the launcher after it is placed and permissions are changed. It appears you may have a soft brick if that KFHD isnt booting at all.
caponea6 said:
First question, did you install this app in the /system/app folder, AFTER you placed it in there? You must install the launcher after it is placed and permissions are changed. It appears you may have a soft brick if that KFHD isnt booting at all.
Click to expand...
Click to collapse
yup, i copied it to /system/app folder,changed permission then installed from there,but when i restarted my KF, it just stop at logo kindle fire.so have any way to fix it?
probb said:
yup, i copied it to /system/app folder,changed permission then installed from there,but when i restarted my KF, it just stop at logo kindle fire.so have any way to fix it?
Click to expand...
Click to collapse
WELP! That doesn't seem like a great scenario to be in. If this was me, I would connect it to my PC and pray that while you're stuck in that logo limbo it would still give you connectivity. I would then go into the /system/app through your PC (on your KFHD directory) and physically remove the launcher files. Then try a restart.

[FireOS 5.x + ROOT] Quickly switch to Amazon UI and back:

Update2: Updated and tested under Lollipop (Sept 2015 FireOS 5.0.1 version for Fire HD 7 2014 [5.2.2u2], and should work with Fire 7 2015)
Given that a Fire tablet with Amazon experience is a terrible thing to waste, these are scripts to switch from and to Amazon launcher both under FireOS 4.5.x and Lollipop. Along with the launcher this disables a lot of battery sucking Amazon apps (the enabling script revives all of this goodness back).
The key stuff in scripts is the launcher block/unblock. I block other apps too because some of them seem to wake up a lot ("Wakelock detector" tells me this), so why not make them less obnoxious when you are not running Amazon experience ...
Naturally, you do need ROOT (how to root FireOS is a subject of other guides).
I assume you have Nova Launcher or free Google Now Launcher (on Lollipop installed as a system app in order to have Widgets working). If your Amazon launcher apk file is renamed, rename it back (verify that you do have the proper /system/priv-app/com.amazon.firelauncher/com.amazon.firelauncher.apk ). Do make sure that you have an alternative launcher (besides the stock Amazon one !!!). Also, make sure that your adb is authorized in order to enable you to unblock the Amazon launcher in case you get the permanent Fire logo.
Go ahead install Gscript ( https://bitbucket.org/Equidamoid/gscript/downloads ). Copy either fire_on_off.zip (for FireOS 4.5.x), or fire_on_off_511b.zip (for FireOS 5.x - Lollipop) to /sdcard/gscript, and unzip scripts right in there. In "Gscript", tap the 3 dots at the bottom right corner, tap "Add script", tap "Load File", tap root required, first choose the disabling script, then repeat for the enabling script. All set.
In Nova, long tap on an empty area, it'll offer to create Shortcut. Choose Gscript/"Kindle block". Repeat for "Kindle unblock".
Then in "Nova", tap "Kindle unblock". It'll get you into Kindle Launcher, at which point you have 100% Amazon experience. Once you do your thing, and want to go back, launch/switch to "Nova", and tap "Kindle block". At this point you are back to more stock like Android.
To give proper credit, this approach was proposed by DoLooper ( http://forum.xda-developers.com/showpost.php?p=61089153&postcount=29 , and some good suggestions in a reply to this post) .
bibikalka said:
So why not switch quickly to and away from stock Amazon UI ?
Click to expand...
Click to collapse
Thanks for the post and the scripts! The shortcut makes it so easy to switch between launchers, and blocking the other packages is a great idea.
In case it's not obvious to casual reader, this lets you run any adb shell command(s) from a homescreen shortcut (and scripts that do other things, too, of course). Here are a few related tips:
Launcher: This works with any launcher that allows shortcuts on the homescreen
Gscript: I suggest using this Gscript app instead of getting it from play store. Play store version is older and less stable, and I don't think it closes after running the shortcut.
Adding the scripts (alternate method): Create a folder named "gscript" in sdcard and put bibikalka's scripts in there. Then in Gscript app, tap (3-dot) menu button, "Add script," "Load file" and the scripts will be listed.
Edit scripts from Gscript: Long press on the script name and choose Edit.
People using Freetime should edit the scripts and delete lines for amazon.kindle.kso and Tahoe. Blocking these causes bootloop.
I'm on 4.5.3 root with Google play, does it Worth upgrading ?
This works with any Fire OS; don't need 4.5.4, just have to be rooted. If you use the Amazon launcher occasionally, try this.
DoLooper said:
This works with any Fire OS; don't need 4.5.4, just have to be rooted. If you use the Amazon launcher occasionally, try this.
Click to expand...
Click to collapse
Has anyone made a version of this for Lollipop ???
bibikalka said:
Has anyone made a version of this for Lollipop ???
Click to expand...
Click to collapse
Not I. (Kinda puts the lie to that old post, eh?)
Commands for developers preview:
pm disable com.android.launcher
pm enable com.android.launcher
am start -n com.android.launcher/com.android.launcher2.Launcher
5.2.2u2 enable/disable = pm disable com.amazon.firelauncher
I can guess start is:
am start -n com.amazon.firelauncher/com.amazon.firelauncher.Launcher
. . . but I can't test cuz I don't have a custom launcher right now. Maybe someone else can test this ??? If not, I'll figure it out in next few days. (You're still on 4.5.5?!)
DoLooper said:
Not I. (Kinda puts the lie to that old post, eh?)
Commands for developers preview:
pm disable com.android.launcher
pm enable com.android.launcher
am start -n com.android.launcher/com.android.launcher2.Launcher
5.2.2u2 enable/disable = pm disable com.amazon.firelauncher
I can guess start is:
am start -n com.amazon.firelauncher/com.amazon.firelauncher.Launcher
. . . but I can't test cuz I don't have a custom launcher right now. Maybe someone else can test this ??? If not, I'll figure it out in next few days. (You're still on 4.5.5?!)
Click to expand...
Click to collapse
OK, thanks! I just got a 5th gen Fire 7 for a present, and will play with it to see how this blocking works on Lollipop.
bibikalka said:
OK, thanks! I just got a 5th gen Fire 7 for a present, and will play with it to see how this blocking works on Lollipop.
Click to expand...
Click to collapse
It works "interestingly." Played with it today to update the block sys app post. Start command:
am start -n com.amazon.firelauncher/.Launcher
Couple interesting (to me) things:
Disable:
- If you only have one alternate launcher, disabling firelauncher immediately takes you to alternate. (But maybe it did this before. I've always had multi alt launchers.)
Enable:
- You stay on alt launcher, but tapping Home icon takes you to Fire launcher (even with multi alt launchers installed).
- Enable and switch = same as before: run enable and then run start
Updated and tested for Lollipop. Thanks to DoLooper for the suggestions!
bibikalka said:
Updated and tested for Lollipop. Thanks to DoLooper for the suggestions!
Click to expand...
Click to collapse
I want to give this a try on my Fire HD7 and have only been using the Amazon launcher to this point. What is the preferred Android launcher most of you use and do you go with the free launcher or purchase a particular one? I see a couple varieties of Nova at the Play Store and have to assume the purchased one does not have ads, so thought I would ask your preferences before giving it a try. Thanks in advance for any advice you provide...
I enjoy the Nova Prime(paid app) no ads lots to customize
phfoneman said:
I want to give this a try on my Fire HD7 and have only been using the Amazon launcher to this point. What is the preferred Android launcher most of you use and do you go with the free launcher or purchase a particular one? I see a couple varieties of Nova at the Play Store and have to assume the purchased one does not have ads, so thought I would ask your preferences before giving it a try. Thanks in advance for any advice you provide...
Click to expand...
Click to collapse
What don't you try the free Google Now launcher ? Once you see how this works, perhaps you'll try Nova.
In case you overdo launcher switching and end up with no working launcher, just remember you can always save the day with these commands in adb (as long as keep the amazon launcher intact, and just block it via "pm disable" as the script above does it):
pm enable com.amazon.firelauncher
am start -n com.amazon.firelauncher/com.amazon.firelauncher.Launcher
Hi all, I have run kindle_block_5_1.sh and then reboot device. I am stack with "Fire" logo at the boot. I have access to ADB, but could not receive root access in adb shell. Can anyone advice me? How can I revert changes after that script back?
Thanks in advance
Yevgen.A said:
Hi all, I have run kindle_block_5_1.sh and then reboot device. I am stack with "Fire" logo at the boot. I have access to ADB, but could not receive root access in adb shell. Can anyone advice me? How can I revert changes after that script back?
Thanks in advance
Click to expand...
Click to collapse
No need to answer, easily fixed my problem by factory reset in recovery
Yevgen.A said:
Hi all, I have run kindle_block_5_1.sh and then reboot device. I am stack with "Fire" logo at the boot. I have access to ADB, but could not receive root access in adb shell. Can anyone advice me? How can I revert changes after that script back?
Thanks in advance
Click to expand...
Click to collapse
Yevgen.A said:
No need to answer, easily fixed my problem by factory reset in recovery
Click to expand...
Click to collapse
Rookie mistake No launcher present, no adb authorized ! But I've added some messages to the original post to mention this issue.
I can't get Nova to create a Gscript shortcut at all. I press the Gscript disable option and it dumps me back to the Amazon launcher.

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

Categories

Resources