Alternative Launcher + Backup Launcher - Fire General

Thanks to @jkchr1s for the steps
I have also attached a backup com.amazonfire launcher just incase soeone messes up.
Working Launcher replacement thanks to @diegocr and @Awesomeslayerg ! Here's the steps:
See @diegocr post at http://forum.xda-developers.com/show...8&postcount=23 and download "boot-firelauncher.img"
Enable USB debugging
Install your launcher of choice!
On your computer, run
Code:
adb reboot bootloader
Once your tablet reboots in to fastboot, run on your computer (if you are not in the same directory as boot-firelauncher.img, put the full path):
Code:
fastboot boot boot-firelauncher.img
Tablet will reboot
Once booted open an adb shell:
Code:
adb shell
To back up the existing app, run:
Code:
cp /system/priv-app/com.amazon.firelauncher/com.amazon.firelauncher.apk /sdcard/Download/com.amazon.firelauncher.apk
Then nuke it!
Code:
rm /system/priv-app/com.amazon.firelauncher/com.amazon.firelauncher.apk
Now, run to restart your device:
Code:
reboot
Confirmed working on my tablet with FireOS 5.0.1.
Enjoy!
If you mess up and your fire dosent have a launcher then download the apk file and adb sideload it once your at the lock screen.

Just wanted to mention can keep the Fire launcher installed without having it forced as default. Follow the above then using a file manager go to where you made a copy of the apk file and install it. It will install and can be used and selected as home or not via the usual home method.

You sir deserve a medal sir! You just saved me 15 € for Netflix and chilling.

or just use Titanium Backup with Pro Key, to Freeze the app

Someone care to explain a bit more? Does this allow us to select a new launcher within system settings making the home button select this launcher?

ruokblah said:
Someone care to explain a bit more? Does this allow us to select a new launcher within system settings making the home button select this launcher?
Click to expand...
Click to collapse
yes
Sent from my KFFOWI using XDA One

After removing the default launcher, I moved to Nova launcher and lost access to all the apps I had saved to my SD card via the system settings. Does this have something to do with the firelauncher? Is there a way to re-enable sd card read/write access?

shiz0id said:
After removing the default launcher, I moved to Nova launcher and lost access to all the apps I had saved to my SD card via the system settings. Does this have something to do with the firelauncher?
Click to expand...
Click to collapse
shouldn't, did you remove other amazon apps?

sd_shadow said:
shouldn't, did you remove other amazon apps?
Click to expand...
Click to collapse
nope, just the FireLauncher, the apps are grayed out in nova, if that means anything.

shiz0id said:
nope, just the FireLauncher, the apps are grayed out in nova, if that means anything.
Click to expand...
Click to collapse
Apps on sd card working fine with Google now launcher
Sent from my KFFOWI using Tapatalk

sd_shadow said:
Apps on sd card working fine with Google now launcher
Sent from my KFFOWI using Tapatalk
Click to expand...
Click to collapse
fixed after forcing a restart of nova, appears to be some kind of issue with the app itself
On another note, do you know any way to re-enable sd card write access?

shiz0id said:
fixed after forcing a restart of nova, appears to be some kind of issue with the app itself
On another note, do you know any way to re-enable sd card write access?
Click to expand...
Click to collapse
https://play.google.com/store/apps/details?id=nextapp.sdfix
Sent from my KFFOWI using Tapatalk

Awesomeslayerg said:
Thanks to @jkchr1s for the steps
I have also attached a backup com.amazonfire launcher just incase soeone messes up.
Working Launcher replacement thanks to @diegocr and @Awesomeslayerg ! Here's the steps:
See @diegocr post at http://forum.xda-developers.com/show...8&postcount=23 and download "boot-firelauncher.img"
Enable USB debugging
Install your launcher of choice!
On your computer, run
Code:
adb reboot bootloader
Once your tablet reboots in to fastboot, run on your computer (if you are not in the same directory as boot-firelauncher.img, put the full path):
Code:
fastboot boot boot-firelauncher.img
Tablet will reboot
Once booted open an adb shell:
Code:
adb shell
To back up the existing app, run:
Code:
cp /system/priv-app/com.amazon.firelauncher/com.amazon.firelauncher.apk /sdcard/Download/com.amazon.firelauncher.apk
Then nuke it!
Code:
rm /system/priv-app/com.amazon.firelauncher/com.amazon.firelauncher.apk
Now, run to restart your device:
Code:
reboot
Confirmed working on my tablet with FireOS 5.0.1.
Enjoy!
If you mess up and your fire dosent have a launcher then download the apk file and adb sideload it once your at the lock screen.
Click to expand...
Click to collapse
I found it was easier to download a 2nd launcher (google now/apex/nova) after I gained root access, then backup the com.amazon.firelauncher in the system/priv-app folder to my SD card or outside the priv-app folder using es file browser. Delete the com.amazon.firelauncher folder inside priv-app, restart the tablet then I was asked on reboot to confirm the default launcher.
Thought it may help someone out who doesn't fancy running the commands.
Cheers as this forum has helped me a lot, much appreciated for all the hard working devs!

Awesomeslayerg said:
Thanks to @jkchr1s for the steps
I have also attached a backup com.amazonfire launcher just incase soeone messes up.
Working Launcher replacement thanks to @diegocr and @Awesomeslayerg ! Here's the steps:
See @diegocr post at http://forum.xda-developers.com/show...8&postcount=23 and download "boot-firelauncher.img"
Enable USB debugging
Install your launcher of choice!
On your computer, run
Code:
adb reboot bootloader
Once your tablet reboots in to fastboot, run on your computer (if you are not in the same directory as boot-firelauncher.img, put the full path):
Code:
fastboot boot boot-firelauncher.img
Tablet will reboot
Once booted open an adb shell:
Code:
adb shell
To back up the existing app, run:
Code:
cp /system/priv-app/com.amazon.firelauncher/com.amazon.firelauncher.apk /sdcard/Download/com.amazon.firelauncher.apk
Then nuke it!
Code:
rm /system/priv-app/com.amazon.firelauncher/com.amazon.firelauncher.apk
Now, run to restart your device:
Code:
reboot
Confirmed working on my tablet with FireOS 5.0.1.
Enjoy!
If you mess up and your fire dosent have a launcher then download the apk file and adb sideload it once your at the lock screen.
Click to expand...
Click to collapse
Could the "boot-firelauncher.img" also be used for the Fire HD 10?

Black Hawk90 said:
Could the "boot-firelauncher.img" also be used for the Fire HD 10?
Click to expand...
Click to collapse
Yes, see [Root] Amazon Fire HD 8 & 10 (5th Gen 2015) for details

Anyone noticed that you cant pin widgets to the startscreen?
Everytime i try, it redirects me to the Amazon-Settings app und the widget isnt pinned.
This happens when the widgets are larger than 1x1

*Igel* said:
Anyone noticed that you cant pin widgets to the startscreen?
Everytime i try, it redirects me to the Amazon-Settings app und the widget isnt pinned.
This happens when the widgets are larger than 1x1
Click to expand...
Click to collapse
Widgets are working for me with Now launcher

*Igel* said:
Anyone noticed that you cant pin widgets to the startscreen?
Everytime i try, it redirects me to the Amazon-Settings app und the widget isnt pinned.
This happens when the widgets are larger than 1x1
Click to expand...
Click to collapse
Convert the launcher to a system app.

csolanol said:
Convert the launcher to a system app.
Click to expand...
Click to collapse
How would I convert it to a system app?

I've found https://play.google.com/store/apps/details?id=de.j4velin.systemappmover&hl=en which works good.
Moved my new apex launcher to system map, reboot was required, then widgets worked with apex launcher which hadn't worked before.

Related

The Viewsonic G Tablet Super Thread (w/Market, Gmail, and Maps!)

I've tried this twice already with a factory reset in between each try, and it's worked both times!
Attached is a bunch of files you will need to make this work.
Download the attached Zip file and extrat the contents to your desktop
Mount your G and upload the "G Tablet" folder to your G's internal SD card
Using AndRootFile or any other file manager that supports root access, mount as R/W, and copy the contents of G Tablet\permissions to System\etc\permissions.
Copy the contents of G Tablet\framework to System\Framework
Copy the contents of G Tablet\lib to System\lib
Copy all the APK's found inside G Tablet\APK into your system\app folder.
Install them in this order:
GoogleServicesFramework.apk
OneTimeInitializer.apk
SetupWizard.apk
Talk.apk
Vending.apk
Gmail.apk
Maps.apk
Make sure you remount it as R/O when you're done!
Restart your G, Connect to Wifi, then launch Market.
Follow the standard Google Account setup procedure and enjoy your newly installed Market.
PROOF THAT IT WORKS (the guide might be broken at some point though, see explanation below): http://www.youtube.com/watch?v=3dm2Kax8RQM
Someone please test this and let me know if you have any problems. Factory resetting doesn't delete any files I might have moved into the system folder so I might be missing something in this guide.
Feel free to donate to my beer fund if this helped you
Copying the following over from my thread over at Overclock.net (best computer enthusiast community, ever!)
Guides:
Setting Up ADB:
The ADB drivers do not recognize the Tegra hardware by default. You need to modify the USB inf file in order for it to recognize it and install the proper hardware.
Go to the usb_driver folder inside your Android SDK folder
Open up android_winusb.inf
Add the following under [Google.NTx86] and save (or if you prefer, download my pre-modified android_winusb.inf attached to the bottom of this post, and replace your existing android_winusb.inf with mine).
Code:
;NVIDIA Tegra
%SingleAdbInterface% = USB_Install, USB\VID_0955&PID_7000
%CompositeAdbInterface% = USB_Install, USB\VID_0955&PID_7100&MI_01
If you are running a 64 bit version of Windows, you need to add that code to the [Google.NTamd64] section as well.
Next, open a command prompt and type
Code:
echo 0x955 >> "%USERPROFILE%\.android\adb_usb.ini"
On your G, go to Settings -> Applications -> Development, and check "USB Debugging"
Plug in your USB cable, it will tell you that some drivers were not installed. That's okay! Point it to your usb_driver folder and it'll install the proper drivers.
Make sure ADB is working by opening a command prompt, navigating to your android sdk "tools" folder, and typing
Code:
adb devices
You should see a bunch of numbers if everything is set up correctly.
Click to expand...
Click to collapse
Rooting:
You need to have ADB fully working before proceeding. The easiest way to root is by using CLShortFuse's SuperOneClick. If you can spare the money, consider donating a buck or two to his beer fund
Connect your G and make sure USB debugging is enabled/ADB is working.
Extract the contents of SuperOneClickv1.5.2-ShortFuse.zip to a folder of your choice.
Run SuperOneClick.exe and click on Root. Wait for the process to finish, and you're rooted! Easy as pie.
Click to expand...
Click to collapse
Installing Launcher Pro/ADW:
It's actually really easy.
Download the Launcher Pro APK from here: http://www.launcherpro.com/apk/LauncherPro-0.8.1.1.apk
Connect your G and move the Launcher APK over to your Tablet's internal/external SD card.
Using whatever file manager you prefer (on your G), execute the Launcher Pro APK and install it.
Upon completion, hit the Home button and choose LauncherPro as your default launcher.
Reboot and feel the speed!
Click to expand...
Click to collapse
Fixes:
Wifi Fix:
If your Wifi "errors" upon enabling, try one of the following methods
Method 1:
Reboot. Seriously, it fixes the problem a large portion of the time.
Click to expand...
Click to collapse
Method 2:
Download Wefi from here: http://www.wefi.com/download/android/
Install the APK on your G.
Run WeFi, hit the menu button (button between back and home), and hit Settings
Make sure Automatic Startup is checked. Click on "Wi-Fi on WeFi start" and choose "Always Turn On"
Restart your G and pray.
Click to expand...
Click to collapse
Method 3: Master Reset (you will lose all your apps)
Go to settings -> Security and do a Factory Wipe.
This works only SOMETIMES, but is not a guaranteed fix, so only use this as a last ditch resort
Click to expand...
Click to collapse
nicely done, sir
Awesome job. OCN FTW
Fantastic.. worked like a champ!
Thanks!
Where did you find the USB drivers to mount the device?
Can i also include the contacts, mail, and calendar gapps?
mattmanion said:
Where did you find the USB drivers to mount the device?
Click to expand...
Click to collapse
By mounting I mean connect the USB cable, then under the Notification Icon, Tap "USB Connected, Select to copy files to/from your computer"
insight3fl said:
Can i also include the contacts, mail, and calendar gapps?
Click to expand...
Click to collapse
Go for it, let us know what you find
r34p3rex said:
By mounting I mean connect the USB cable, then under the Notification Icon, Tap "USB Connected, Select to copy files to/from your computer"
Click to expand...
Click to collapse
Do you know if there is a tutorial out there for installing the Root Explorer or Astro file manager on this thing? Sorry, I'm a newbie.
VERY NICE WORK!
FYI I reposted this on the slatedroid.com forum gave you credit and linked back to this thread. If you don't want it on there let me know and I will take it down.
by the way.. All I did to get this working was install the apk's in order and reboot. I do have a problem .. I can't find some apps on the market.. for example winamp doesnt show up..just the winamp 3rd party app.
Anyone else?
Does anyone know why live wallpapers aren't available?
tri0xinn said:
by the way.. All I did to get this working was install the apk's in order and reboot. I do have a problem .. I can't find some apps on the market.. for example winamp doesnt show up..just the winamp 3rd party app.
Anyone else?
Click to expand...
Click to collapse
I will look into that. The most likely reason is the lack of a unique Android ID.
does the regular nullsoft winamp show up for you?
great work man. Just saw the video.
I'm still trying to get adb access. First thing I did was modded the usb files but not the 64bit cuz I didn't see it. Guess I didn't look hard enough. Modded the 32bit one and added the Nvidia tegra info. Then tried adb and the oneclickroot and it didn't work. I then went in and found the amd64 area and added the lines to that portion of the usb.ini file also.
I don't have adb working to root. I'm on Win 7 64bit. any idea's. Then I'll try your guide.
xguntherc said:
great work man. Just saw the video.
I'm still trying to get adb access. First thing I did was modded the usb files but not the 64bit cuz I didn't see it. Guess I didn't look hard enough. Modded the 32bit one and added the Nvidia tegra info. Then tried adb and the oneclickroot and it didn't work. I then went in and found the amd64 area and added the lines to that portion of the usb.ini file also.
I don't have adb working to root. I'm on Win 7 64bit. any idea's. Then I'll try your guide.
Click to expand...
Click to collapse
Gunth you want me to help over Teamviewer?
My files are in place, but the APK files are not "installing" on boot and the tablet sets up normaly and gmail app is not there. I have tried going back in and changing R/O in root explorer, but still not go.. what am I missing? Can these files be pushed to the tablet via adb or do you have to use root explorer? Seems I had the same problem when I did this with my Odroid T.. I tried root explorer but ended up pushing with adb.
Thanks for your work on this
hmmm... it says "install"... I need to launch them from explorer and actualy "install" them? then reboot?
insight3fl said:
My files are in place, but the APK files are not "installing" on boot and the tablet sets up normaly and gmail app is not there. I have tried going back in and changing R/O in root explorer, but still not go.. what am I missing? Can these files be pushed to the tablet via adb or do you have to use root explorer? Seems I had the same problem when I did this with my Odroid T.. I tried root explorer but ended up pushing with adb.
Thanks for your work on this
hmmm... it says "install"... I need to launch them from explorer and actualy "install" them? then reboot?
Click to expand...
Click to collapse
You need to run each APK manually through Root Explorer (or any package installer of your choice). Placing them there does not do anything
xguntherc said:
great work man. Just saw the video.
I'm still trying to get adb access. First thing I did was modded the usb files but not the 64bit cuz I didn't see it. Guess I didn't look hard enough. Modded the 32bit one and added the Nvidia tegra info. Then tried adb and the oneclickroot and it didn't work. I then went in and found the amd64 area and added the lines to that portion of the usb.ini file also.
I don't have adb working to root. I'm on Win 7 64bit. any idea's. Then I'll try your guide.
Click to expand...
Click to collapse
I'm having the same issue Gunth so when you get it working let me know
Just finished up installing the apks. Got a problem though. Now my home and search buttons don't work. Also lost Airplane mode when powering off.
*EDIT* Just watched your video. I don't think that's a finicky button. I think this hack causes the problem.
*EDIT 2* Just did a reset. Home button and search work again. So, it's got to be the hack.
Doc

Custom launcher on S7 Slim

For all of you having problem with unresponsive touchscreen after installing alternative launcher on your S7 Slim...
I found out that during boot touchscreen is disabled and official Huawei Launcher enables it, so if you install alternative launcher, touchscreen remains disabled after reboot.
First of all, you have to root you S7 Slim (I've done it using following article http://android-dls.com/wiki/index.php?title=HOWTO:_Unpack,_Edit,_and_Re-Pack_Boot_Images, just set ro.secure=0 in default.prop and add --base 0x20000000 to mkbootimg command-line). Then, copy file /system/etc/bluetooth_power.sh to your hard disk (adb pull /system/etc/bluetooth_power.sh c:\). Edit that file (c:\bluetooth_power.sh) using Notepad++ and add following lines:
echo 1 > /sys/cap_touchscreen/boot_complete
echo 1 > /sys/cap_touchscreen/state
Then, remount /system partiton read-write (adb remount), and copy that file back (adb push c:\bluetooth_power.sh /system/etc/).
Reboot, and now you can install any launcher you like!
I installed adw launcher ex on my s7 tablet and now my touch screen wont work. I've tried to connect it to my PC to root but my PC isn't seeing the device. I don't think its set on debugging mode. Is there anyway to fix this or is it hopeless.
Edit: nevermind I returned it to best buy.
Sent from my Desire HD using xda premium
I've root with gingerbreak and I've root explorer. I'll just edit bluetooth_power.sh with root explorer editing tools and add those code, right?
Sent from my IDEOS S7 Slim using XDA App
shishko said:
For all of you having problem with unresponsive touchscreen after installing alternative launcher on your S7 Slim...
I found out that during boot touchscreen is disabled and official Huawei Launcher enables it, so if you install alternative launcher, touchscreen remains disabled after reboot.
First of all, you have to root you S7 Slim (I've done it using following article http://android-dls.com/wiki/index.php?title=HOWTO:_Unpack,_Edit,_and_Re-Pack_Boot_Images, just set ro.secure=0 in default.prop and add --base 0x20000000 to mkbootimg command-line). Then, copy file /system/etc/bluetooth_power.sh to your hard disk (adb pull /system/etc/bluetooth_power.sh c:\). Edit that file (c:\bluetooth_power.sh) using Notepad++ and add following lines:
echo 1 > /sys/cap_touchscreen/boot_complete
echo 1 > /sys/cap_touchscreen/state
Then, remount /system partiton read-write (adb remount), and copy that file back (adb push c:\bluetooth_power.sh /system/etc/).
Reboot, and now you can install any launcher you like!
Click to expand...
Click to collapse
Wow thanks shisko, it works!
My steps a bit different:
1. Root with gingerbreak.
2. Edit bluetooth_power.sh with root explorer.
3. Add those code. Save and exit.
4. Reboot.
5. Add custom launcher.
Sent from my IDEOS S7 Slim using Tapatalk
Here is the evidence, custom launcher GO Launcher EX works on my HIS7 Slim (CDMA)
#!/system/bin/sh
#
# added by h00131430
#
echo 0 > /sys/class/rfkill/rfkill0/state
echo 1 > /sys/cap_touchscreen/boot_complete
echo 1 > /sys/cap_touchscreen/state
Download file
http://www.multiupload.com/MKBGQUC10X
Worked for me.
glpro said:
Download file
http://www.multiupload.com/MKBGQUC10X
Click to expand...
Click to collapse
Link is dead, could you post another, please?
wheeqo said:
Wow thanks shisko, it works!
My steps a bit different:
1. Root with gingerbreak.
2. Edit bluetooth_power.sh with root explorer.
3. Add those code. Save and exit.
4. Reboot.
5. Add custom launcher.
Sent from my IDEOS S7 Slim using Tapatalk
Click to expand...
Click to collapse
Confirmed, working. I installed Zeam straight to portrait view, and no orientation bug anymore. Cheers!
huawei slim
who can make a better huawei s7 slim rom?
beenhow said:
who can make a better huawei s7 slim rom?
Click to expand...
Click to collapse
1. Tri-zet (Tried and works great) androidtablets.net
2. Zmey Mod (Still running) on ndroidtablets.net
3. Pirate 2.0 by Satec in this forum (Not sure this will run on my s7 105 and too lazy to flash this at the moment cos the ROM i using now is stable enough)
Tri Zet works great!
darkic said:
Tri Zet works great!
Click to expand...
Click to collapse
CM9 , CM10 , paranoid works great , too

[HOWTO] Remove/disable boot up startup sound from HTC One

Hi all,
Couldn't find this info for this handset specifically, so thanks to Jayshah's howto for the HTC Desire in this post (H/T to him!) I found the equivalent location in the HTC One filesystem for the startup sound audio file.
So then, if, like me, you strongly dislike the HTC "Quietly brilliant" boot sound, here's two different methods to disable it entirely. You could also extend these to replace the sound with one of your own.
1. Alter the xml file that references the sound file
Pre-requisites:
Handset is rooted
Root-enabled file manager app installed (e.g. Total Commander)
Howto steps:
Detailed in this post later in the thread.
2. Remove/hide the startup sound file
Pre-requisites:
Handset is rooted and has a custom recovery partition (e.g. TWRP or CWM)
ADB install and working on desktop computer
Howto steps:
1. Put your phone into recovery
2. Open adb shell
3. Mount /system
4. Change directory to /system/customize/resource
5. Rename or delete HTC_Sense5_Boot.mp3
Code:
mount /system
cd /system/customize/resource
mv HTC_Sense5_Boot.mp3 HTC_Sense5_Boot_mp3.disabled
As noted by Jayshah, you could install Silent Boot from the Play store, but why add something else eating processor cycles when this solution is guaranteed and requires no additional code?
Thanks for this, worked a charm and didn't need to S-OFF!
Helpful! thank you very much bro.
Helpful! thank you very much bro.
dr_diem said:
Hi all,
Couldn't find this info for this handset specifically, so thanks to Jayshah's howto for the HTC Desire in this post (H/T to him!) I found the equivalent location in the HTC One filesystem for the startup sound audio file.
So then, if, like me, you strongly dislike the HTC "Quietly brilliant" boot sound, here's how to disable it entirely:
Pre-requisites:
Handset is rooted
Put your phone into recovery
Get a working adb shell
1. Mount /system
2. change directory to /system/customize/resource
3. rename or delete HTC_Sense5_Boot.mp3
Code:
mount /system
cd /system/customize/resource
mv HTC_Sense5_Boot.mp3 HTC_Sense5_Boot_mp3.disabled
As noted by Jayshah, you could install Silent Boot from the Play store, but why add something else eating processor cycles when this solution is guaranteed and requires no additional code?
Click to expand...
Click to collapse
Brilliant thank you. Will do this soon.
dr_diem said:
Hi all,
Couldn't find this info for this handset specifically, so thanks to Jayshah's howto for the HTC Desire in this post (H/T to him!) I found the equivalent location in the HTC One filesystem for the startup sound audio file.
So then, if, like me, you strongly dislike the HTC "Quietly brilliant" boot sound, here's how to disable it entirely:
Pre-requisites:
Handset is rooted
Put your phone into recovery
Get a working adb shell
1. Mount /system
2. change directory to /system/customize/resource
3. rename or delete HTC_Sense5_Boot.mp3
Code:
mount /system
cd /system/customize/resource
mv HTC_Sense5_Boot.mp3 HTC_Sense5_Boot_mp3.disabled
As noted by Jayshah, you could install Silent Boot from the Play store, but why add something else eating processor cycles when this solution is guaranteed and requires no additional code?
Click to expand...
Click to collapse
"Get a working adb shell" meaning what? Having a working fastboot? could you please explain?
M_Shaaban said:
"Get a working adb shell" meaning what? Having a working fastboot? could you please explain?
Click to expand...
Click to collapse
Do some searching here on the forums - adb stands for Android Desktop Bridge and is freely downloadable as part of the Android SDK. It enables you to access your Android device in various ways from your desktop computer. adb shell is a way to open an interactive shell (a 'command prompt') on the Android device. There are howtos on these forums (and indeed all over the 'net) that'll explain how to get ADB set up for your desktop OS.
Ian
dr_diem said:
Do some searching here on the forums - adb stands for Android Desktop Bridge and is freely downloadable as part of the Android SDK. It enables you to access your Android device in various ways from your desktop computer. adb shell is a way to open an interactive shell (a 'command prompt') on the Android device. There are howtos on these forums (and indeed all over the 'net) that'll explain how to get ADB set up for your desktop OS.
Ian
Click to expand...
Click to collapse
I did do that and I could reboot to recovery by entering command "adb reboot recovery" but then when I enter adb shell, it says device not found. What should I do? Could there be a quick video tutorial on how to do so?
M_Shaaban said:
I did do that and I could reboot to recovery by entering command "adb reboot recovery" but then when I enter adb shell, it says device not found. What should I do? Could there be a quick video tutorial on how to do so?
Click to expand...
Click to collapse
Oh okay you're probably almost there. I couldn't say exactly what's causing that message (I see the same myself from time to time by rebooting the phone usually solves the problem). Try booting the phone normally and seeing whether adb shell works when the phone is in it's normal interactive usable state. If that works then you could Google on 'adb shell not working in recovery mode' or somesuch, but you need to confirm that it works at all first of all.
dr_diem said:
Oh okay you're probably almost there. I couldn't say exactly what's causing that message (I see the same myself from time to time by rebooting the phone usually solves the problem). Try booting the phone normally and seeing whether adb shell works when the phone is in it's normal interactive usable state. If that works then you could Google on 'adb shell not working in recovery mode' or somesuch, but you need to confirm that it works at all first of all.
Click to expand...
Click to collapse
OK will try and do that. Thanks!
Sent from my HTC One using XDA Premium 4 mobile app
---------- Post added 16th December 2013 at 12:00 AM ---------- Previous post was 15th December 2013 at 11:35 PM ----------
dr_diem said:
Oh okay you're probably almost there. I couldn't say exactly what's causing that message (I see the same myself from time to time by rebooting the phone usually solves the problem). Try booting the phone normally and seeing whether adb shell works when the phone is in it's normal interactive usable state. If that works then you could Google on 'adb shell not working in recovery mode' or somesuch, but you need to confirm that it works at all first of all.
Click to expand...
Click to collapse
@dr_diem adb shell works fine with phone is on. Now time to find a solution to be working on recovery. My phone is rooted but I flashed stock recovery back after rooting. Is that OK? Or must it be done via custom recovery? Did it do it via stock or custom recovery? Also my Windows is 8.1 but I can access fastboot (commands and all) without a problem. On stock recovery >adb shell > device not found!
M_Shaaban said:
OK will try and do that. Thanks!
Sent from my HTC One using XDA Premium 4 mobile app
---------- Post added 16th December 2013 at 12:00 AM ---------- Previous post was 15th December 2013 at 11:35 PM ----------
@dr_diem adb shell works fine with phone is on. Now time to find a solution to be working on recovery. My phone is rooted but I flashed stock recovery back after rooting. Is that OK? Or must it be done via custom recovery? Did it do it via stock or custom recovery? Also my Windows is 8.1 but I can access fastboot (commands and all) without a problem. On stock recovery >adb shell > device not found!
Click to expand...
Click to collapse
I've just done some quick Googling and indeed yes a custom recovery is required to use adb whilst in recovery (according to this page that seems pretty sure of itself). Apologies that my howto didn't make that clear (that being because I didn't know about the requirement at the time!); I'll update it in that regard now.
Ian
dr_diem said:
I've just done some quick Googling and indeed yes a custom recovery is required to use adb whilst in recovery (according to this page that seems pretty sure of itself). Apologies that my howto didn't make that clear (that being because I didn't know about the requirement at the time!); I'll update it in that regard now.
Ian
Click to expand...
Click to collapse
I flashed CWM custom recovery and still adb device is not found! What could be the problem here?
M_Shaaban said:
I flashed CWM custom recovery and still adb device is not found! What could be the problem here?
Click to expand...
Click to collapse
I'm sorry but I am out of ideas on this I can only suggest you do some extended web and/or xda-developers searching to learn reasons for this error. I'm quite sure you'll find the answer given the size of our community; please do post back here when you find it.
Good luck!
Ian
M_Shaaban said:
I flashed CWM custom recovery and still adb device is not found! What could be the problem here?
Click to expand...
Click to collapse
Since this guide requires root anyway, I'm going to assume you already have Root access. If so, just install a root file manager (I like Root Browser), navigate to /system/customize/resource, and rename HTC_Sense5_Boot.mp3 to anything else. As long as it's not called HTC_Sense5_Boot.mp3, it won't play. Save and reboot. If you'd like to disable it altogether, navigate to /system/customize/resource/CID and open default.xml. Find:
Code:
<BootConfiguration>
<BootAnimation animation="/system/customize/resource/att_bootup_one.zip" audio="/system/customize/resource/HTC_Sense5_Boot.mp3"/>
</BootConfiguration>
and remove the last part so it looks like this:
Code:
<BootConfiguration>
<BootAnimation animation="/system/customize/resource/att_bootup_one.zip" />
</BootConfiguration>
Now save and reboot.
homeslice976 said:
Since this guide requires root anyway, I'm going to assume you already have Root access. If so, just install a root file manager (I like Root Browser), navigate to /system/customize/resource, and rename HTC_Sense5_Boot.mp3 to anything else. As long as it's not called HTC_Sense5_Boot.mp3, it won't play. Save and reboot. If you'd like to disable it altogether, navigate to /system/customize/resource/CID and open default.xml. Find:
Code:
<BootConfiguration>
<BootAnimation animation="/system/customize/resource/att_bootup_one.zip" audio="/system/customize/resource/HTC_Sense5_Boot.mp3"/>
</BootConfiguration>
and remove the last part so it looks like this:
Code:
<BootConfiguration>
<BootAnimation animation="/system/customize/resource/att_bootup_one.zip" />
</BootConfiguration>
Now save and reboot.
Click to expand...
Click to collapse
I used Root Browser. I edited the XML file and worked like a charm. But seems like it's taking a bit longer to boot, could editing boot configuration cause this?
Sent from my HTC One using XDA Premium 4 mobile app
M_Shaaban said:
I used Root Browser. I edited the XML file and worked like a charm. But seems like it's taking a bit longer to boot, could editing boot configuration cause this?
Sent from my HTC One using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I certainly wouldn't think so. I've been disabling bootsounds this way since my Inspire
homeslice976 said:
I certainly wouldn't think so. I've been disabling bootsounds this way since my Inspire
Click to expand...
Click to collapse
Ah OK. Thanks a lot anyway
Sent from my HTC One using XDA Premium 4 mobile app
Hi, I tried to change this with root explorer. First i renamed the audio file. But it was restored after reboot. Then i changed in the xml file. same here restored? wtf? Have just got the latest sense 6 if that can have something to do with Thierry.
Edit: worked from recovery. But still, strange that root explorer didn't work?
You saved me. I was going crazy ... all tips I could find were for Android 2, or were turning sound off at shutdown => does not work after crash.
Thankss
Thnaks for the info
Do I need to be S-OFF to perform that?
Because when I restarted my phone after edition of the XML config file the changes we gone. Original file remains.

[TUT] Easily remove Amazon's firelauncher and use any launcher (NO ROOT 5.x.x)

Source code to an alpha tool in Python-QT, if you guys are python savvy show some love <3
https://bitbucket.org/dylanmulrooney/android-launcher/src
In this thread you will finally be able to remove Amazon's terrifying FireLauncher for good, and replace it with your choice of a launcher.
Prerequisites:
Install ADB
Install Nova Launcher / launcher of choice
BACKUP YOUR FIRELAUNCHER.APK
You do not need to corrupt the firelauncher as I have, but it eats system resources and I never want to see it pop up. I have attached a modified version of the firelauncher APK. You will need to download and install it as an update via ADB.
(this is optional, you wont have any launcher after doing this! backup your old APK!!)
Code:
adb install -r -d com.amazon.firelauncher.apk
... as you can now see this will -r reinstall and -d downgrade the launcher, causing it to crash and never open.
Now we need to run a single line of ADB code every time you reboot your device:
Code:
adb shell
Code:
nohup logcat -c; logcat | grep --line-buffered 'flg=0x10200000 cmp=com.amazon.firelauncher/.Launcher' | while read line; do am start com.teslacoilsw.launcher/.NovaLauncher; done &
Code:
exit
This is designed (in combination with destroying firelauncher) to allow you to set any launcher, by default I have it set to am start Nova Launcher.
Once you paste that line of code in adb, you can unplug your device and use it with your new custom launcher!
Please feel free to contact me for detailed instructions!
Cautiously optimistic. Waiting for field evidence before recommending. As always reputations are earned.
First I'd love to thank you for your continuing support to give more launcher choices to the Amazon Fire.
Where can I find and back up the original fire launcher? So if, in the future, we want the fire launcher back, we just install the backup? Any script to run to undo?
About this "Now we need to run a single line of ADB code every time you reboot your device:".
So it cannot be automatically executed?
while trying to adb intall the apk, it shows error: https://www.dropbox.com/s/syyggde0ie7sf4t/Screenshot 2016-09-24 21.58.03.png?dl=0
UPDATE: I got it installed now. The issue above because I ran adb shell first. Anyway, it doesn't seem to shut down the Fire Launcher as I can still see briefly when pressing Home button; and it doesn't allow to set another launcher as default beside Nova. (Fire HD 10 - 5.3.1)
Let's say we want to set a different default launcher to this one: https://play.google.com/store/apps/details?id=com.citc.asap&hl=en
What should we type? Can you try with the above launcher cz' it cannot be launched till it's set as default?
FYI, as we cannot root this 5.3.1, so using the above launcher 'ASAP Launcher' will be awesome as it has built-in widgets. One more is Arrow Launcher by Microsoft.
The other one is Buzz Launcher: https://play.google.com/store/apps/details?id=com.buzzpia.aqua.launcher&hl=en
it's pretty heavy with built-in widgets and themes.
---------- Post added at 03:58 PM ---------- Previous post was at 03:01 PM ----------
I used your previous code from another post for Windows manually: http://forum.xda-developers.com/ama...-remove-default-launcher-amazon-fire-t3288310 , and it allowed to select any installed launcher as default, the issue it doesn't stick when restarted:
Code:
while :
do
kill $!
sleep 1 & pm install -r -d "/system/priv-app/com.amazon.firelauncher/com.amazon.firelauncher.apk" & sleep 20; kill $!
kill $!
done &
exit
#press enter now
ttcontributor said:
First I'd love to thank you for your continuing support to give more launcher choices to the Amazon Fire.
Where can I find and back up the original fire launcher? So if, in the future, we want the fire launcher back, we just install the backup? Any script to run to undo?
About this "Now we need to run a single line of ADB code every time you reboot your device:".
So it cannot be automatically executed?
Click to expand...
Click to collapse
I do not have a working firelauncher, and honestly I do not want it. That step is optional and the only purpose of removing it is so I never accidentally see it for a second.
I am still working on improving this, please feel free to request features!
Yes, it can be automated just not easily.. You would need to install an app and then paste the command in the apps etc. I never reboot my device so it's not a priority for me. Let me know if you have any ideas. It works flawlessly right now, speeds up the tablet.
ttcontributor said:
while trying to adb intall the apk, it shows error: https://www.dropbox.com/s/syyggde0ie7sf4t/Screenshot 2016-09-24 21.58.03.png?dl=0
UPDATE: I got it installed now. The issue above because I ran adb shell first. Anyway, it doesn't seem to shut down the Fire Launcher as I can still see briefly when pressing Home button; and it doesn't allow to set another launcher as default beside Nova. (Fire HD 10 - 5.3.1)
Let's say we want to set a different default launcher to this one: https://play.google.com/store/apps/details?id=com.citc.asap&hl=en
What should we type? Can you try with the above launcher cz' it cannot be launched till it's set as default?
FYI, as we cannot root this 5.3.1, so using the above launcher 'ASAP Launcher' will be awesome as it has built-in widgets. One more is Arrow Launcher by Microsoft.
The other one is Buzz Launcher: https://play.google.com/store/apps/details?id=com.buzzpia.aqua.launcher&hl=en
it's pretty heavy with built-in widgets and themes.
---------- Post added at 03:58 PM ---------- Previous post was at 03:01 PM ----------
I used your previous code from another post for Windows manually: http://forum.xda-developers.com/ama...-remove-default-launcher-amazon-fire-t3288310 , and it allowed to select any installed launcher as default, the issue it doesn't stick when restarted:
Code:
while :
do
kill $!
sleep 1 & pm install -r -d "/system/priv-app/com.amazon.firelauncher/com.amazon.firelauncher.apk" & sleep 20; kill $!
kill $!
done &
exit
#press enter now
Click to expand...
Click to collapse
I love you for being so helpful in the development of this project. You simply change the code to whatever launcher you want, you just need the package name/activity. I also think it would be wise to reboot when running the command since two instances may cause glitches without killing the nohup process.
I will make a tool that simplifies your life, drag and drop launcher of choice apk and it'll set it as default & remove amazon ****ware.
I have released the source code to my alpha project, should work cross platform (need testers who know Python!)
https://bitbucket.org/dylanmulrooney/android-launcher/src
nyln said:
I love you for being so helpful in the development of this project. You simply change the code to whatever launcher you want, you just need the package name/activity. I also think it would be wise to reboot when running the command since two instances may cause glitches without killing the nohup process.
I will make a tool that simplifies your life, drag and drop launcher of choice apk and it'll set it as default & remove amazon ****ware.
Click to expand...
Click to collapse
Great, after reboot and re-run the command I didn't notice the Fire Launcher no more when pressing home, but sometime just a blank screen breifly before going to the set launcher. And it's a wonderful news for "drag and drop launcher of choice apk and it'll set it as default & remove amazon****ware"
FYI, currently I'm combining your method by 1# install your attached .apk to corrupt the Fire Launcher, and #2 use the previous code above to be able to select any launcher installed. It's better because it can detect a new launcher installed from PlayStore and provide the option to select it as default: https://goo.gl/photos/qQzohRJNMEifCkyw6
ttcontributor said:
Great, after reboot and re-run the command I didn't notice the Fire Launcher no more when pressing home, but sometime just a blank screen breifly before going to the set launcher. And it's a wonderful news for "drag and drop launcher of choice apk and it'll set it as default & remove amazon****ware"
FYI, currently I'm combining your method by 1# install your attached .apk to corrupt the Fire Launcher, and #2 use the previous code above to be able to select any launcher installed. It's better because it can detect a new launcher installed from PlayStore and provide the option to select it as default: https://goo.gl/photos/qQzohRJNMEifCkyw6
Click to expand...
Click to collapse
Very interesting. I finished a rough alpha version of drag and drop, I posted the source code but no compiled binaries yet. I will make an option to select the launcher of your choice.
Give me the app name and I'll write a special code for you since nova sucks
nyln said:
Very interesting. I finished a rough alpha version of drag and drop, I posted the source code but no compiled binaries yet. I will make an option to select the launcher of your choice.
Give me the app name and I'll write a special code for you since nova sucks
Click to expand...
Click to collapse
Nova is good if rooted. In this case, ASAP Launcher is unbeatable: https://play.google.com/store/apps/details?id=com.citc.asap&hl=en
OR EVEN BETTER > TOTAL LAUNCHER: https://play.google.com/store/apps/details?id=com.ss.launcher2
nohup logcat -c; logcat | grep --line-buffered 'flg=0x10200000 cmp=com.amazon.firelauncher/.Launcher' | while read line; do am start com.citc.asap; done &
nyln said:
nohup logcat -c; logcat | grep --line-buffered 'flg=0x10200000 cmp=com.amazon.firelauncher/.Launcher' | while read line; do am start com.citc.asap; done &
Click to expand...
Click to collapse
Awesome.
I have been testing a lot of launchers to find one that is customizable with widgets without root, and found Total Launcher: https://play.google.com/store/apps/details?id=com.ss.launcher2
Now settling for this as it has internal / built-in widgets which can be added to Fire OS WITHOUT root and converting the launcher to system app. What is the package code for this one then?
UPDATE:
Code:
nohup logcat -c; logcat | grep --line-buffered 'flg=0x10200000 cmp=com.amazon.firelauncher/.Launcher' | while read line; do am start com.ss.launcher2; done &
It'd be completed if it can be autorun after system restart of packed to an app to tricker this in Amazon Fire itself.
ttcontributor said:
Awesome.
I have been testing a lot of launchers to find one that is customizable with widgets without root, and found Total Launcher: https://play.google.com/store/apps/details?id=com.ss.launcher2
Now settling for this as it has internal / built-in widgets which can be added to Fire OS WITHOUT root and converting the launcher to system app. What is the package code for this one then?
UPDATE:
Code:
nohup logcat -c; logcat | grep --line-buffered 'flg=0x10200000 cmp=com.amazon.firelauncher/.Launcher' | while read line; do am start com.ss.launcher2; done &
It'd be completed if it can be autorun after system restart of packed to an app to tricker this in Amazon Fire itself.
Click to expand...
Click to collapse
I may have a temporary workaround for auto restart. I just don't see how this makes or brakes it. You can paste that command in Terminal Emulator if you don't want to use a computer on reboot.
nyln said:
I may have a temporary workaround for auto restart. I just don't see how this makes or brakes it. You can paste that command in Terminal Emulator if you don't want to use a computer on reboot.
Click to expand...
Click to collapse
Think it depends on the user. For many launching Terminal Emulator and pasting in a command is a PiTA that offsets the benefit of a custom launcher. Technical enthusiasts don't mind so much but they are the minority of the Fire user community ime - even on XDA.
nyln said:
I may have a temporary workaround for auto restart. I just don't see how this makes or brakes it. You can paste that command in Terminal Emulator if you don't want to use a computer on reboot.
Click to expand...
Click to collapse
Well, at least we don't need to rely on the computer no more! And it will be a set-it-and-forget-it if we input the command to the Terminal Emulator to auto execute?
And about the ppl using Fire OS, there are still many out there. Once they know it can be customized to their liking, they will pop up!
ttcontributor said:
And about the ppl using Fire OS, there are still many out there. Once they know it can be customized to their liking, they will pop up!
Click to expand...
Click to collapse
FireOS is a solid alternative to more 'traditional' Android presentations once ads, bloat and other Amazon cruft is tamed. The ability to toggle launchers on non-rooted devices will be welcome by many if it can be made largely transparent once implemented.
Thanks for your feedback guys. I am working on an update that will simplify your lives.
nyln said:
Thanks for your feedback guys. I am working on an update that will simplify your lives.
Click to expand...
Click to collapse
Which code can I paste to the Terminal Emulator to not use the pc then? Then we can have the Emulator auto run the script when reboot?
Back to Firelauncher
nyln said:
Source code to an alpha tool in Python-QT, if you guys are python savvy show some love <3
https://bitbucket.org/dylanmulrooney/android-launcher/src
In this thread you will finally be able to remove Amazon's terrifying FireLauncher for good, and replace it with your choice of a launcher.
Prerequisites:
Install ADB
Install Nova Launcher / launcher of choice
BACKUP YOUR FIRELAUNCHER.APK
You do not need to corrupt the firelauncher as I have, but it eats system resources and I never want to see it pop up. I have attached a modified version of the firelauncher APK. You will need to download and install it as an update via ADB.
(this is optional, you wont have any launcher after doing this! backup your old APK!!)
Code:
adb install -r -d com.amazon.firelauncher.apk
... as you can now see this will -r reinstall and -d downgrade the launcher, causing it to crash and never open.
Now we need to run a single line of ADB code every time you reboot your device:
Code:
adb shell
Code:
nohup logcat -c; logcat | grep --line-buffered 'flg=0x10200000 cmp=com.amazon.firelauncher/.Launcher' | while read line; do am start com.teslacoilsw.launcher/.NovaLauncher; done &
Code:
exit
This is designed (in combination with destroying firelauncher) to allow you to set any launcher, by default I have it set to am start Nova Launcher.
Once you paste that line of code in adb, you can unplug your device and use it with your new custom launcher!
Please feel free to contact me for detailed instructions!
Click to expand...
Click to collapse
How do I revert back to Firelauncher?
imblogr said:
How do I revert back to Firelauncher?
Click to expand...
Click to collapse
Recommend you reload FireOS via stock recovery as it is not clear how to fully revert the changes. Sure, you could read through the instructions and figure it out...starting from scratch will probably be quicker with better outcomes. The OP has not posted for awhile; not sure he/she is still around.

FireHD 10 rooted, issues with Nova launcher as replacement of firelauncher

I've been trying to get novalauncher to replace the firelauncher, and I can do so with launcher hijak, but to make it native, I just can't get it working. Im skilled in unix, but I'm new to android, and dealing with tablet/phone android systems.
Is there a specific set of instructions as to how to do this including moving the files to /system/app or /system/priv-app?
Some oddities I'm seeing.
First and foremost the names are a bit odd instead of com.teslacoilsw.launcher I see com.teslacoilsw.launcher-1. Maybe this is normal.
Posts reference just copying the apk from /data/app as if its a single file. For whatever reason, it appears as a folder both in ES File Browser, and the adb shell, with base.apk and a lib folder (which is empty). I have moved the entire folder from /data/app to /system/app or /system/priv-app, and changed the permissions on it to 744 with and without changing the perms on the base.apk IN the folder...but it simply doesn't work.
My goal is to replace the firelauncher with nova, as I like it much more, and I was trying to eliminate the "flicker" from the hijak solution.
I just did it yesterday by moving entire folder com.testlacoilsw.launcher-1 from /data/app to /system/priv-app, all folders 755(need execute to cd, that's what I always do with my unix folders, not sure if that's needed in this case), and the apk to 644. I am able to add widgets and swipe left to get google now in Nova, firelaucher disabled, no hijacklauncher.
freealta said:
I just did it yesterday by moving entire folder com.testlacoilsw.launcher-1 from /data/app to /system/priv-app, all folders 755(need execute to cd, that's what I always do with my unix folders, not sure if that's needed in this case), and the apk to 644. I am able to add widgets and swipe left to get google now in Nova, firelaucher disabled, no hijacklauncher.
Click to expand...
Click to collapse
How did you get it to be the launcher app that runs when the user logs in?
pm enable com.testlacoilsw.launcher and pm disable x.firelauncher?
cuilidh said:
How did you get it to be the launcher app that runs when the user logs in?
pm enable com.testlacoilsw.launcher and pm disable x.firelauncher?
Click to expand...
Click to collapse
I set Nova as the default launcher in Nova, it prompts you to do that when you get into Nova Settings, then pm disable com.amazon.firelauncher.
cuilidh said:
How did you get it to be the launcher app that runs when the user logs in?
pm enable com.testlacoilsw.launcher and pm disable x.firelauncher?
Click to expand...
Click to collapse
It must have been permissions, because now it appears to work. I haven't tried any widgets...and swipe left doesnt bring up google now, but at least the launcher is working.
Im going to try the step that gives nova privs...although I thought putting an app in /system/priv-app did that.
Download the attached file, rename it from .txt to .sh and place into the internal storage on the tablet then run:
Code:
adb shell appwidget grantbind --package com.teslacoilsw.launcher --user 0
This will get your widgets working
cuilidh said:
It must have been permissions, because now it appears to work. I haven't tried any widgets...and swipe left doesnt bring up google now, but at least the launcher is working.
Im going to try the step that gives nova privs...although I thought putting an app in /system/priv-app did that.
Click to expand...
Click to collapse
Make sure to install Google from the play store in order for swipe left to work, installing play store doesn't include Google. If you installed Nova correctly as a system app, widgets will work without doing anything else.
freealta said:
Make sure to install Google from the play store in order for swipe left to work, installing play store doesn't include Google. If you installed Nova correctly as a system app, widgets will work without doing anything else.
Click to expand...
Click to collapse
Yep, this was it.
What else should I be installing from the google store to get the best functionality? I'm entirely new to android.

Categories

Resources