Related
As many PDA2k users might have noticed by now, a file named BtTrayLog.txt found in the main directory on the device keeps expanding endlessly and thus eats every bit of memory you might have. There is no setting that you can change to solve this nor does deleting this file keeps it from popping back again.
I found a temporary solution and it has been working perfectly for the last few days. You can replicate my solution by following these steps:
1) Turn your Bluetooth on.
2) Start your "File Explorer" on your device and go to the main folder "My Device".
3) You will find a file named BtTrayLog.txt (when I first discovered this file it was 32 MB big!). Delete this file.
4) Close your File Explorer and wait for a few minutes.
5) Start your File Explorer again and you will find the same file again, although this time it should be very small (the smallest I could get it was 866 B only.)
6) Click and hold on it until the submenu appears and then select "Properties".
7) Check the "Read only" box and click "Ok".
Voila! The file will remain but its size will not change. The solution is a little primitive but it will spare you the effort of having to delete the file every couple of days. I list it here for the benefit of other users until CD fixes this issue in its upcoming ROM upgrade, whenever that may arrive.
I am looking for help. I am a noob and I rooted my phone and it all went well. I froze apps that others had frozen. I tried to be very cautious but I froze LGSetupWizard with titanium backup and then did a hard reset. My phone now starts up with the setup wizard and when it gets to the end it states that the application (process com.android.LGSetupWizard) stopped unexpectedly then it loops back to the beggining. I have actually been able to access my email and the net from the notification dropdown. I am lost as what to do. Is my phone bricked? Is it possible to simply put the application back into the phone somehow? I have access to the files that I froze through titanium back up on my computer as they were on the sd card. I would really appreciate any help
Can't you just skip out of the wizard before it gets to the end? Or choose to not go through it at all?
Try the factory reset and see if that helps... Just guessing though ?
How
The start-up wizard started automatically after the reset. I have tried to get out of it but when I "exit" it brings up the same error message. I read a post on another phone where you could opt out of it by pushing a few buttons in a certain sequence but it did not work. How would I do a factory reset as is? Any ideas? Thank You!!
Can you get debug mode running (possibly by connecting to your computer, selecting the computer usb connection, and then long holding the line in notification center or something)? If so, you might be able to push the backed up .apk with adb and get it reinstalled.
Explanation
I really apprecitate your post. I am sorry I am a noob and I am not sure what you mean by "long holding the line in notification center". I will download ADB and research how to use it. Thank You!!
If you can make adb working, then you can use 'adb uninstall' the TB, or use 'adb shell' login to phone, su, then delete TB app or data
TB?
Thank you for your post, what is TB?
I must be a real idiot. I found out after the fact that if you select any other option than PC software on the USB connection mode it disables debugging mode. I have ADB but it is not recognizing the phone because it is not in debugging mode. Is there any other way to activate debugging mode besides Settings -> Applications -> Development -> USB debugging?
Please Help!
TB means TitaniumBackup.
Another way to enter adb:
If you have cwm recovery installed, pls continue see following steps:
1. Enter CWM Recovery mode.
2. Then connect your phone to computer
3. enter "adb devices"
D:\android-sdk-windows\platform-tools>adb devices
List of devices attached
LGOxxxxxxxxx recovery
If you see above, then good, enter "adb shell" to login to your phone.
enter "id" to make sure you are root.
then:
cd /data/app
ls -l *Titanium*
#you should see something like com.keramidas.TitaniumBackup.apk
#then enter:
mv com.keramidas.TitaniumBackup*.apk TitaniumBackup.abc
Above cmd will make the app executable file invalid extension, which should disable the TB app. (I didn't try, but I guess it should disable the app)
HTH,
xordos
CWM Recovery
I don't have CWM recovery, I tried to research it and I could not find the LG nitro in the list for clockwork mod, should I use one of the optimus models? I rooted with superoneclick. If I froze the file in TB would uninstalling TB unfreeze it? I have actuall been able to use mail, messaging, and the phone when someone else calls or emails me and I have been able to access settings for each of these specific areas but I have not been able to access settings for the debugging.
Thank You!!
USB debugging on how do I push the files?
I have ADB running and I am in debugging mode. I still have root. How and where would I push the file onto the device.
Thank you!!
Resolved
My issue has been resolved. Thanks for the help!
problem fixed
hello .
If you still have the problem with the lg phone , there is a very easyyyyyy solution .
I had the same problem ; i deleted Lg home because i was using go launcher home , then one day i just moved go launcher on the sd card . That was the problem , i hard reset my phone 20 time , but still in the end of the reset process i was receving that error , the process stoped .
Ok , once you have reached the error " setup wizard process stop " , press the close button . Than press the 3d menu button . You will go into 3d menu , there click 3d games and accesories . Launch the game asphat 3d. The game will be installed . After you launch the game , there is a small button in the game , in the top left corner , similar with an earth , named info . Click that button , than click the twiter button . Now you will launch the internet browser and you problem it's fixed. Once the internet it's opened , go to google com , and search for any launcher . By example seach go launcher , find it , download it , install it . When you want to install it a windows asking about some security settings will open . It;s the settings menu of the phone . Here you can can allow to install application that dosen't come from play store , or you can just enable usb debuging ( and of course with usb debuggin enabled ,you can easly update or downgrade your phone using the lg official software ) .
Good luck .
hey man, how did you fix this problem? i have the same deal right now. thanks
gave up. flashed kdz
Hello all
A little bit of background info:
I have owned my Desire for over 2 years now & recently decided to s-off/root/flash (primarily to gain some memory space- the only real short coming of the Desire in my opinion).
I went from stock Gingerbread 2.3.7 to Cyanogenmod 7.1 & so have taken my first step into a larger world!
In that world I encountered problems - no signal, no gps, no bluetooth, radio flashing etc. - all of which I managed to find solutions for by reading the excellent resources of xda-developers.
So having collated the enormous & varying wealth of info & getting my Desire fully functional - I wanted to give something back.
It's not much (though I haven't seen it anywhere as a solution?), but it may help someone somewhere :fingers-crossed:
## If you just want to cut to the chase- the procedure that worked for me is at the end of the post! ##
About my phone:
Android version 2.3.7
Cyanogenmod version 7.1.0
Baseband Version 32.56.00.32u_5.17.05.23
Kernel Version 2.6.37.6-cyanogenmod-geb50077
As stated, gps & signal were fixed with a simple radio flash from 5..11.05.14 - 5.17.05.23
but bluetooth remained unable to connect. My 2 devices were in the list showing as 'Paired but not connected'
Clicking on them they would say 'connecting' but that process would end with no error or message & no connection made.
The only long press option on them was 'unpair' - so no option to delete & try again.
I then found a potential fix which is I assume is fairly well known BUT I could not get it to run:
SOLUTION (copied from external site)
I ran the Terminal app and entered
'su'
(App requests root permissions, grant them). Then I went to the device's bluetooth settings with
'cd /data/misc/bluetoothd'
(Note the 'd' at the end). There I found a directory named by the bluetooth chip's ID, in my case '38:E7:B8:45:21:a4'. I renamed this directory
'mv 3* hidden'
Turned bluetooth off and back on and could use bluetooth again.
Every time I ran the terminal I could get su to work, with permissions granted as confirmed in the toast message that would pop up- BUT whenever I typed 'cd /data/misc/bluetoothd' I only ever got 'Permission Denied'.
All the fix posts I read about this pointed towards root & su permissions not working correctly but mine certainly were. I had tried all the usual fixes of un-applying/re-applying SU permissions, root etc.
I also tried the same commands through adb, all with the same result.
It then occurred to me that the Terminal was only changing a folder property so I used 'ROM Toolbox Pro' -> 'Root Browser' to find the folder in question ('38:E7:B8:45:21:a4' in my case).
It became apparent that the path given in the 'fix' was incorrect (for my Desire GSM at least).
The folder I was looking for was actually in 'd/data/bluetoothd' - so the 'permission denied' error was because the path was incorrect, not that SU permissions were not granted!
Before I actually tried that correct path though- I noticed that to make files hidden the '.' (full stop) prefix is added to the start of the file or folder name.
I used Root Browser to long-press on the '38:E7:B8:45:21:a4' folder & then 'rename' from the menu - making the folder name '.38:E7:B8:45:21:a4' (note the full stop at the start.)
I then re-enabled bluetooth - this time noticing that both my paired devices were no longer there (this is good!). I made the Desire discoverable then did a scan...success!
Both my devices paired & connected exactly as they should. I now notice in Root Browser that the file structure has also changed with there being no 'bluetoothd' folder at all.
I also imagine that entering the correct folder path in terminal or adb would produce the same results, though I cannot confirm this as the procedure described had already worked for me.
So, long story short:
1. Make sure bluetooth is turned OFF then open Rom Toolbox Pro -> Root Browser (or any root browser with su permissions I guess?)
2. Navigate to the folder d/data/bluetoothd/38:E7:B8:45:21:a4 (#Note: your '38:E7:B8:45:21:a4' folder will probably be named differently)
3. Long press on the '38:E7:B8:45:21:a4' folder. (or whatever yours is called)
4. From the pop up menu - select 'Rename'
5. Add a full stop '.' at the beginning of the folder name Eg '.38:E7:B8:45:21:a4' (Keep the rest of the name as it was)
6. Turn on Bluetooth - in 'Bluetooth settings' make your device discoverable & note that if any paired devices were present, they should now be gone from the list.
7. Scan for bluetooth devices, obviously making sure they are also switched on & discoverable! (if it doesn't automatically)
8. Your devices should now show up, ask to pair, ask for pin numbers if needed & then connect automatically.
If this has been covered elsewhere please accept my apologies, & delete the post if it's deemed as clutter- I was merely trying to help
Dog909 said:
Hello all
A little bit of background info:
I have owned my Desire for over 2 years now & recently decided to s-off/root/flash (primarily to gain some memory space- the only real short coming of the Desire in my opinion).
I went from stock Gingerbread 2.3.7 to Cyanogenmod 7.1 & so have taken my first step into a larger world!
In that world I encountered problems - no signal, no gps, no bluetooth, radio flashing etc. - all of which I managed to find solutions for by reading the excellent resources of xda-developers.
So having collated the enormous & varying wealth of info & getting my Desire fully functional - I wanted to give something back.
It's not much (though I haven't seen it anywhere as a solution?), but it may help someone somewhere :fingers-crossed:
## If you just want to cut to the chase- the procedure that worked for me is at the end of the post! ##
About my phone:
Android version 2.3.7
Cyanogenmod version 7.1.0
Baseband Version 32.56.00.32u_5.17.05.23
Kernel Version 2.6.37.6-cyanogenmod-geb50077
As stated, gps & signal were fixed with a simple radio flash from 5..11.05.14 - 5.17.05.23
but bluetooth remained unable to connect. My 2 devices were in the list showing as 'Paired but not connected'
Clicking on them they would say 'connecting' but that process would end with no error or message & no connection made.
The only long press option on them was 'unpair' - so no option to delete & try again.
I then found a potential fix which is I assume is fairly well known BUT I could not get it to run:
SOLUTION (copied from external site)
I ran the Terminal app and entered
'su'
(App requests root permissions, grant them). Then I went to the device's bluetooth settings with
'cd /data/misc/bluetoothd'
(Note the 'd' at the end). There I found a directory named by the bluetooth chip's ID, in my case '38:E7:B8:45:21:a4'. I renamed this directory
'mv 3* hidden'
Turned bluetooth off and back on and could use bluetooth again.
Every time I ran the terminal I could get su to work, with permissions granted as confirmed in the toast message that would pop up- BUT whenever I typed 'cd /data/misc/bluetoothd' I only ever got 'Permission Denied'.
All the fix posts I read about this pointed towards root & su permissions not working correctly but mine certainly were. I had tried all the usual fixes of un-applying/re-applying SU permissions, root etc.
I also tried the same commands through adb, all with the same result.
It then occurred to me that the Terminal was only changing a folder property so I used 'ROM Toolbox Pro' -> 'Root Browser' to find the folder in question ('38:E7:B8:45:21:a4' in my case).
It became apparent that the path given in the 'fix' was incorrect (for my Desire GSM at least).
The folder I was looking for was actually in 'd/data/bluetoothd' - so the 'permission denied' error was because the path was incorrect, not that SU permissions were not granted!
Before I actually tried that correct path though- I noticed that to make files hidden the '.' (full stop) prefix is added to the start of the file or folder name.
I used Root Browser to long-press on the '38:E7:B8:45:21:a4' folder & then 'rename' from the menu - making the folder name '.38:E7:B8:45:21:a4' (note the full stop at the start.)
I then re-enabled bluetooth - this time noticing that both my paired devices were no longer there (this is good!). I made the Desire discoverable then did a scan...success!
Both my devices paired & connected exactly as they should. I now notice in Root Browser that the file structure has also changed with there being no 'bluetoothd' folder at all.
I also imagine that entering the correct folder path in terminal or adb would produce the same results, though I cannot confirm this as the procedure described had already worked for me.
So, long story short:
1. Make sure bluetooth is turned OFF then open Rom Toolbox Pro -> Root Browser (or any root browser with su permissions I guess?)
2. Navigate to the folder d/data/bluetoothd/38:E7:B8:45:21:a4 (#Note: your '38:E7:B8:45:21:a4' folder will probably be named differently)
3. Long press on the '38:E7:B8:45:21:a4' folder. (or whatever yours is called)
4. From the pop up menu - select 'Rename'
5. Add a full stop '.' at the beginning of the folder name Eg '.38:E7:B8:45:21:a4' (Keep the rest of the name as it was)
6. Turn on Bluetooth - in 'Bluetooth settings' make your device discoverable & note that if any paired devices were present, they should now be gone from the list.
7. Scan for bluetooth devices, obviously making sure they are also switched on & discoverable! (if it doesn't automatically)
8. Your devices should now show up, ask to pair, ask for pin numbers if needed & then connect automatically.
If this has been covered elsewhere please accept my apologies, & delete the post if it's deemed as clutter- I was merely trying to help
Click to expand...
Click to collapse
I can't find folder *data* in folder *d*. I have a separate folder *data*. There is a folder named *bluetooth* in folder *d*. It also didn't work for me.
I just got a Fire Phone via the Ebay sale, and like many others, I wanted to set it up with Google Apps. I also wanted to keep the working camera and NFC, so I decided to stick with FireOS. Doing that took a lot of searching, and flipping through multiple threads. It can get a little confusing. So I've collected all the steps here to help others (and myself, in case I need to do this again in the future, when I inevitably break something while tinkering). I've written this from the perspective of someone who has purchased a brand new Fire Phone from a third-party seller.
PLEASE NOTE: Much of this is the work/discoveries of other forum members. I'll link out to the original posts whenever possible. Please thank those people accordingly!
1. When you first start up your phone, connect to WiFi, and let it go through the upgrade process to 4.6.4. Now is the time to register your phone with Amazon (by signing in with your Amazon account). You want that year of Prime, don't you?
2. SIM Unlock the phone (if you aren't using AT&T). It's easy!
a. Use a paperclip to pop out the SIM tray
b. Insert a non-AT&T nano-sized SIM card. (Mine came with an AT&T SIM in it. You can't use this card to SIM unlock)
c. A window should pop up, prompting you to enter the code that is on your box. Enter it.
d. Done!
3. Open Settings>Applications & Parental Controls>Prevent non-Amazon app installation. Turn App Installation to ON
4. Make sure ADB is set up on your computer. (this is an easy guide to follow if you don't already have it: http://lifehacker.com/the-easiest-way-to-install-androids-adb-and-fastboot-to-1586992378 )
5. Download the following file to your desktop computer:
GSM Unlocked Firmware (this is a 1.2gb file) (http://forum.xda-developers.com/showpost.php?p=62768812&postcount=2). Rename this update.bin, and put it into the folder where ADB is installed.Now we get our hands dirty:
6. If you are using Windows (I'm not), follow the directions that @Bingo Bronson posted here: http://forum.xda-developers.com/showpost.php?p=62768812&postcount=2. @DePingus also has an illustrated guide for ADB on Windows here: http://forum.xda-developers.com/showpost.php?p=62844581&postcount=14
6a. If you aren't using Windows, you can follow my steps (the same, just without all the Android SDK stuff, assuming you installed ADB in step #4)
a. Connect your phone to your PC & boot into recovery: When the phone is off, hold PWR + VOL. UP until the recovery screen appears
b. From the list, choose "Apply update from ADB"
c. In the command prompt, enter the following:
Code:
adb sideload path/to/update.bin
d. It should take a few minutes. When it's done, reboot your phone
NOTE: If for some reason this isn't working for you, @jack9955 has posted steps on how to downgrade via Safestrap here.
7. Open Settings>Device>Get Info About Your Fire Phone. Your current version will be listed under Software Version, and it should now be 4.6.3
At this point, you may need to repeat step 3. I didn't, but it's worth checking.
8. Open the Amazon app store (one last time) and download ES File Explorer.
9. In the Silk Browser, open up the following links and download the files:
KingRoot (http://forum.xda-developers.com/fire-phone/help/root-4-6-3-t3173322)
Updated Google Play Store files: (http://forum.xda-developers.com/fire-phone/general/google-play-store-4-6-1-version-4-apks-t3098592)
10. Open ES File Explorer, navigate to Download, and install KingRoot. Follow the directions to achieve root.
11a. At this point, some people like to remove KingRoot (out of security concerns) and replace it with SuperSu. I haven't done that yet, but you can follow the directions from @najoor here: http://forum.xda-developers.com/fire-phone/general/root-fire-phone-supersu-t3105546
12. Open ES File Explorer, navigate to Download, and unzip play.zip. Be sure to install the apks contained in the play.zip folder in the proper order (Thanks to @escape75 for these files)
1) Google Account Manager 4.4.2 (940549)
2) Google Services Framework 4.4.2 (940549)
3) Google Play Services 7.8.99 (2134222-036) - Updated
4) Google Play Store 5.8.8 - Updated
13. After installing, I rebooted into recovery again, and wiped the cache partition. I don't know if you need to, but engaging in good housekeeping is never bad.
14. You should have a Play Store icon in your app drawer now. Click it to open, and holy crap!! It works. Plug in your google account details.
Now it's time to keep Amazon from wrecking all your hard work. Steps 15 or 15a will block OTA updates of the OS.
15. Go to Settings>Applications & Parental Controls>Manage Applications. Click Filter By and select All. Find each of the files listed below, click it, and then click the "Disable" button on the next screen. Repeat for the other three files. (thanks @Bingo Bronson)
Amazon Device Client
DCP Platform Contracts
System Update
System Update (yes, there are two different files named system update. Freeze/Disable both)
15a. If you'd rather, you can do like I did, and use Titanium Backup Pro to freeze the above files.
16. Don't like the Launcher? Neither do I. I followed these directions to change out my launcher: http://spinyourfire.com/fire-phone-tips-and-tricks/fire-phone-launcher/ I use Home Switch from the Play Store. It will allow you to set your new launcher.
If you decide to use a new launcher, here's some info (courtesy @Bingo Bronson) which may help:
1. Settings>Display>Show Status Bar allows you to turn on the Status Bar at the top of the screen. This will help some launchers display properly.
2. Miss your NavBar / want some way other than Amazon gestures to navigate your phone? Try installing Ultimate Dynamic NavBar or Pie Controls.
NOTE: The new launcher will disable Tilt Left/Right on your home screen. In Amazon apps, the gesture will still work.
17. To sync your contacts/calendars/etc, go to Settings>My Accounts>Manage Email Accounts and add your Google account info.
a. Select that account, check sync calendar and sync contacts.
b. Set Inbox Check Frequency to manual.
c. In Email Settings, set everything to off, then click email notification settings, and set all of those to off.
BEWARE: HERE BE DRAGONS
Hi. Are you new to phone hacking? Then you should probably stop reading here. Following any of the links or info could (pretty easily) lead to bricking your phone. I won't even mess with most of this stuff, I'm just providing links for intrepid explorers who know what they are getting into, and are willing to risk it. SERIOUSLY, TURN AROUND HERE!
Seriously, you did all that work, and now you want to risk breaking it? Well yeah, me too. So let's cover our asses.
Backing Up with SafeStrap
First, let's back up what you've done. @ggow (to whom we all owe a debt of gratitude) has gifted us with SafeStrap, which allows us to boot into a version of TWRP recovery. From there, you can install his CM11 or SlimKat Roms, or use the backup feature, which is what we are about to do.
1. Install Safestrap from here http://forum.xda-developers.com/fire-phone/development/recovery-safestrap-v4-0-1-t3149888. In ggow's directions, it talks about 4.6.1, but I can confirm it works properly on 4.6.3.
2. Once you have booted into Safestrap, Click Backup and then back it up! (it took about ten minutes for me)
3. Of course, a backup won't do you any good if you don't have multiple redundancies. So plug your phone into your computer, open up a terminal/CMD prompt, and enter the following:
Code:
adb start-server
then
Code:
adb pull /sdcard/TWRP/ /path/to/your/backup/folder
after that runs for a while, you should see a message that says something along the lines of "12 files pulled. 0 files skipped"
Good! Now we are backed up, and we can start breaking stuff.
Turn on USB Debugging
1. Go to Settings>Device>Get info about your Fire
2. Tap "Model Number" seven or eight times, until the "Developer Options" button appears at the bottom of the list
3. Tap "Developer Options" and enable USB debuggingInstalling Xposed Framework
Xposed Framework allows you to install different modules that can change the look, feel and operation of your phone. Xposed works best on Vanilla Android, but we can definitely put it to good use here. Lifehacker has a great overview on Xposed. I'll just give you the basics here.
What you'll need: Root
1. On your phone, visit http://repo.xposed.info/module/de.robv.android.xposed.installer. Scroll down to the bottom of the page and click Show Older versions. You want the APK for version 2.6.1 (the most recent stable version)
2. After downloading, navigate to your Downloads folder and install the Xposed Apk.
3. Open Xposed and click Framework. It will show you that Xposed is currently inactive. Tap the install/update button.
4. Once installed, you must reboot your phone for Xposed to work.Congrats! Now with Xposed, you can really start customizing your phone. Check the forums...there is tons to discover and lots of people who know far more than I about how to use it. Just remember that a lot of the cosmetic stuff might not work on a Fire Phone. The modules I use are: ACDisplay, Amplify (paid version), AppOppsXposed, GravityBox, Greenify (paid version), PowerNap.
Installing a custom Lock Screen
Many of us on Android are used to custom lock screens, and haven't been thrilled with the Amazon Lock Screen. Through some trial and error, I've discovered how to swap out the Amazon Lock Screen for my lock screen of choice, ACDisplay. I haven't tried this with other 3rd party lock screens. Try following (and contributing to) this lockscreen thread to see any developments on other lock screens.
What you need: Xposed, Root, ES File Explorer (or another file explorer with root access)
1. Install ACDisplay (I sideloaded the APK, but it seems to work from the Play Store)
2. Open ES File Explorer, tap the hamburger menu, scroll down to Tools, and turn on Root Explorer
3. find the installed apk (com.achep.acdisplay-1.apk) in /data/app
4. rename it LockScreen.apk and move it to /system/priv-app/
5. Reboot
6. Open up AC Display and grant it access to Accessibility Settings and Notifications
7. In ACDisplay>Settings>Lockscreen move the slider to On and make sure that "Enable when no notifications" is ticked
8. Open Xposed and activate the ACDisplay module.
9. Reboot
10. I don't know if you need to, but I went to Settings>Lock Screen> Turn on Notifications... and made sure that notifications were off.
The Xposed integration seems to be the key. Now, when I reboot my phone, I'll get the original Amazon Lock Screen once (sometimes) and then ACDisplay pops up from that point on. Apparently, if you want a pin/password on the lock screen, you can still use the security features of the OS lockscreen.
Launchers with Widgets
One of the problems with custom launchers is that widgets don't seem to work on the Fire Phone. But @hmoobguy and @DePingus have figured out how to beat that in this thread. Just like with the lock screen, you'll have to move some files.
What you need: Root, ES File Explorer (or another file explorer with root access)
1. Install your launcher from the Play Store.
1a. If you haven't already, visit the Play Store on your desktop, look at the page for the launcher you just installed, and take note of what comes after 'id=' in the URL. That's the file name you'll search for.
2. Open ES File Explorer, tap the hamburger menu, scroll down to Tools, and turn on Root Explorer
3. find the installed apk for your launcher of choice in /data/app by searching for what came after 'id=' in step 1a.
4. move it to /system/priv-app/
5. Reboot
Note: you can also use Titanium to convert your launcher of choice into a system app.
Other Stuff
@Bingo Bronson has a ridiculously extensive list of Fire OS apps that can be disabled/frozen or deleted. Use at your own risk: http://forum.xda-developers.com/fire-phone/general/complete-app-list-replace-remove-t3132008
Hopefully this is helpful to others. I can add information as I go if new info (and new annoyances) come to light. Please let me know if there is anything I missed!
Thanks man! That's a good list there!
I gathered much of the information you have posted there last night and I have it at 4.6.3 with Google Play and a custom launcher.
My next challenge is a single lock screen. I have yet to actually root it however.
Which seems it will be required to get any further with the lock screen deal based off what I've read thus far.
Cheers!
"curious what adds the extra slide lock, is it the adding of a different Launcher or Home Switch? Even when using the FirePhone launcher again it remains."
Natet2003 said:
"curious what adds the extra slide lock, is it the adding of a different Launcher or Home Switch? Even when using the FirePhone launcher again it remains."
Click to expand...
Click to collapse
I'm not quite sure what you mean here. I'm messing with the lock screen myself, haven't quite got it figured out yet. I use AC Display, and have been trying to freeze various apps listed in the App List post (at the bottom of the walkthrough under "HERE BE DRAGONS"). I can shut off the Amazon lock screen, but for some reason, my lock screen only works every other time. If I let it sit for a while and then unlock it, I just get the woven graphite background and nothing else. I have to turn off the screen, turn it back on again, and then my lock screen will work. I'm assuming it has something to do with the system putting the app to sleep.
Natet2003 said:
My next challenge is a single lock screen. I have yet to actually root it however.
Which seems it will be required to get any further with the lock screen deal based off what I've read thus far.
Click to expand...
Click to collapse
This thread has info on changing the lockscreen.
http://forum.xda-developers.com/fire-phone/help/fire-phone-lock-screen-t2982798/page5
You do need root. Install the new lockscreen (many people were using Next Lock Screen). Use a root file explorer to delete /system/priv-app/LockScreen.apk (make a backup first). Then move whatevernewlockscreen.apk from /data/app to /system/priv-app, rename it to LockScreen.apk and reboot.
I was having issues with the alarm clock and then I screwed up all the lockscreens. I gave up trying to fix my mess and just took the opportunity to install 4.6.3. That fixed all my issues and put me back to the stock crappy lockscreen, which I'm still running.
munkymack said:
I'm not quite sure what you mean here. I'm messing with the lock screen myself, haven't quite got it figured out yet. I use AC Display, and have been trying to freeze various apps listed in the App List post (at the bottom of the walkthrough under "HERE BE DRAGONS"). I can shut off the Amazon lock screen, but for some reason, my lock screen only works every other time. If I let it sit for a while and then unlock it, I just get the woven graphite background and nothing else. I have to turn off the screen, turn it back on again, and then my lock screen will work. I'm assuming it has something to do with the system putting the app to sleep.
Click to expand...
Click to collapse
I think I found what it was. I had "C Launcher" installed. It does an iPhone styled sliding lock screen that even when I swapped to another Launcher the lock screen kept activating. (So I had two screens to bypass) When I had experimented with GO Locker it added yet another screen to those so 3 screens!
So once I've removed CLauncher and GO Locker I've not just have a single screen, which is FireOS default lock screen.
Great instructions, well consolidated--thanks!!
Questions: 1. What's the reason you went through all the updates, all the way to 4.6.4 and then downgraded to 4.6.3. Could you just not have installed 4.6.3 from the beginning? 2. Also, why version 4.6.3? Is that the version on which google play works the best?--the reason I ask is because I too have read so many posts on this site and I have come to perceive that Google play still does not work perfectly on any of the versions!. Hopefully my perception is wrong and I can proceed with your consolidated instructions. Can you please post updates as the days go by on how its all working. Thanks.
dannyol said:
Questions: 1. What's the reason you went through all the updates, all the way to 4.6.4 and then downgraded to 4.6.3. Could you just not have installed 4.6.3 from the beginning? 2. Also, why version 4.6.3? Is that the version on which google play works the best?--the reason I ask is because I too have read so many posts on this site and I have come to perceive that Google play still does not work perfectly on any of the versions!
Click to expand...
Click to collapse
I went to 4.6.4 simply because my phone automatically updated from 3.5.0>4.6.1>4.6.4 when I connected it to wifi, and the directions I'd found showed how to downgrade from 4.6.4 (which is AT&T specific) to 4.6.3 (gsm unlocked).
The reason I chose to downgrade is because Play store doesn't work on 4.6.4...it keeps breaking. On 4.6.3, that's not the case (so far); Play Store (and even more important, Play Services, which is necessary for most Google apps) is working exactly like it should be. Might it break in the future? Yeah, probably. But if / when it does, I'll try and update the post (assuming that a fix gets found).
DePingus said:
This thread has info on changing the lockscreen.
http://forum.xda-developers.com/fire-phone/help/fire-phone-lock-screen-t2982798/page5
You do need root. Install the new lockscreen (many people were using Next Lock Screen). Use a root file explorer to delete /system/priv-app/LockScreen.apk (make a backup first). Then move whatevernewlockscreen.apk from /data/app to /system/priv-app, rename it to LockScreen.apk and reboot.
Click to expand...
Click to collapse
Just a heads up, DePingus and I have been discussing this on the linked thread, and the above instructions DO NOT work. LockScreen.apk does not exist in /system/priv-app/ on 4.6.3. At this point in time, there is not a way to completely replace the Amazon lock screen with a custom lock screen.
This is a good guide.
Just FYI, you don't have to enable USB debugging to root with KingRoot. And, more importantly, you don't have to be rooted or enable USB debugging to install 4.6.3, Google Play Services, or alternate launchers. Instead of adb push, you can just copy the apks over using your favorite method (USB, OneDrive, direct download) and then run to install. Come to think of it, you probably should move rooting and USB debugging into the "here be dragons" section.
Is it safe to update the play store when it asks?
MrPaulAR said:
Is it safe to update the play store when it asks?
Click to expand...
Click to collapse
Yes, as far as we know (for v. 4.6.3) Play Store can be updated and will still work, same with Play services.
New fire phone with version 3.5-rooted and now at a stand-still
Bingo Bronson said:
Yes, as far as we know (for v. 4.6.3) Play Store can be updated and will still work, same with Play services.
Click to expand...
Click to collapse
I too got my new fire phone on ebay. The fire phone has version 3.5. I read that it was a rootable version, so I proceeded to root the phone via towelroot . I have supersu installed also. I have verified root via an app and the phone is now successfully rooted. Now I am puzzled as to what I should do with the fire phone with version 3.5 and am at a stand-still!!.
Questions:
1. Can I update to version 4.6.3 from here without loosing root?
2. Will updating to version 4.6.3 in its present rooted condition cause any harm (i.e bricking) ?
4. If I need to remove root and supersu in-order to update the phone to version 4.6.3, how do I do that?
3. The reason for these questions is because I am assuming that I need to update to version 4.6.3 to install google apps.
Can you help me proceed along from this standstill that I find myself in!
Thanks
dannyol said:
I too got my new fire phone on ebay. The fire phone has version 3.5. I read that it was a rootable version, so I proceeded to root the phone via towelroot . I have supersu installed also. I have verified root via an app and the phone is now successfully rooted. Now I am puzzled as to what I should do with the fire phone with version 3.5 and am at a stand-still!!.
Questions:
1. Can I update to version 4.6.3 from here without loosing root?
2. Will updating to version 4.6.3 in its present rooted condition cause any harm (i.e bricking) ?
4. If I need to remove root and supersu in-order to update the phone to version 4.6.3, how do I do that?
3. The reason for these questions is because I am assuming that I need to update to version 4.6.3 to install google apps.
Can you help me proceed along from this standstill that I find myself in!
Thanks
Click to expand...
Click to collapse
I did the same thing when I first got mine, so I understand where you are coming from. After reading around on the forum, I saw that 4.6.3 could work with Play Store / Services, so I just did a straight up OS update. I didn't unroot or anything, and suffered no problems. My phone updated from 3.5 to 4.6.1, and then to 4.6.4. From that point, I downgraded to 4.6.3 and then proceeded with the steps in the guide.
As far as I can tell, you WILL lose root in the update, but you can use Kingroot to re-apply root.
Will this work on a Fire tablet? Would I just not run the GSM unlocked firmware part?
Thanks
jimbobalu said:
Will this work on a Fire tablet? Would I just not run the GSM unlocked firmware part?
Thanks
Click to expand...
Click to collapse
I have absolutely no idea. If it does work, let me know. I've got one of the new $50 fire tablets coming at the end of the month.
DePingus said:
Just FYI, you don't have to enable USB debugging to root with KingRoot. And, more importantly, you don't have to be rooted or enable USB debugging to install 4.6.3, Google Play Services, or alternate launchers. Instead of adb push, you can just copy the apks over using your favorite method (USB, OneDrive, direct download) and then run to install. Come to think of it, you probably should move rooting and USB debugging into the "here be dragons" section.
Click to expand...
Click to collapse
That's a good point. I've been doing this long enough that rooting is something I do without a second thought, but for beginners, it opens up the door to a host of problems. I'll do a reorganization next time it's slow around the office.
Thank you for the step-by-step guide. It was incredibly helpful and everything worked...expect for downgrading to 4.6.3. It may be because I'm on a Mac, but nothing I tried seemed to work. That is until I found this website that worked to perfection. Hopefully anyone else on a Mac finds it useful as well.
And apparently because I'm a new user, I can't post URL's, so here's the closest I can get you
seo-michael.co.uk/how-to-setup-adb-on-os-x
This phone is dirty cheap now.
i might grab one of these . here in Europe
cheers
Be sure and check the LTE bands before you do. You may not be able use high speed data there.
EDIT: I looked at the work in your signature. I'm pretty sure you know exactly what you are doing / getting yourself into if you do pick one up. I'm just trying to be super newbie friendly over here, hence my response.
Osufever said:
Thank you for the step-by-step guide. It was incredibly helpful and everything worked...expect for downgrading to 4.6.3. It may be because I'm on a Mac, but nothing I tried seemed to work. That is until I found this website that worked to perfection. Hopefully anyone else on a Mac finds it useful as well.
Click to expand...
Click to collapse
Yeah, ADB is different on every system, and can be a pain in the ass to set up. The Lifehacker article I linked should cover everything, but if Mac users want to delve a little deeper, then the link you followed is a good way to go. I'm glad you were able to get things working!
Having a problem with V4A on build .139. I am rooted, have Busybox free installed, and bought SELinux.
I use the stock music app, because I don't know how to sideload the info for other programs. Total newb here, first time rooting. Anyways, as I start the music app, V4A is not active, and I have to go to the EQ settings, then it starts. Then after about 5 min., playing with screen off, it shuts off. I have tried both Normal and Compatible FX settings, Compatible renders the driver useless. I have V4A set to force start, but that does nothing, and I've installed the latest version 3 times now, doing a driver removal, reboot, app removal reboot, redownload, re-install, setup etc. It still happens. Is there something I'm doing wrong. I've disabled the "Music FX" app that comes with the phone that is the basic EQ on the phone, so that's not interfering. I don't know what it could be. Does anyone else have this problem, and how did you solve it?
Much appreciated for the responses.
Check if you are using the Asus auto start manager, allow viper and uncheck cleanup in suspend option.
harpreet.s said:
Check if you are using the Asus auto start manager, allow viper and uncheck cleanup in suspend option.
Click to expand...
Click to collapse
I am using Asus auto start. I did what you said, and I'm running a test now. It would usually run for about 15 min, then shut off. So, I'm doing the 15 min. test, then I'll try the music app shutdown and restart, and see if your suggestion worked. I hope so, it's been driving me nuts all day.:good:
I know, it drove me crazy too. What i did was change something in the "audio.conf" file. You have to erase some lines.
With this, android uses viper audio for everything.
for the audio conf thing look in the sticky posts, thats where i found it
lkzshg said:
I know, it drove me crazy too. What i did was change something in the "audio.conf" file. You have to erase some lines.
With this, android uses viper audio for everything.
for the audio conf thing look in the sticky posts, thats where i found it
Click to expand...
Click to collapse
Well, the 15 min. thing worked out. It seems to run no problem now. But when I shut the music player off, and restart it, I have to Force Stop V4A, then go into the EQ of the music player, then it kicks in.
I'll look for the "audio.conf" file, but how do I implement it, or write it on the phone. I'm not a user of ADB, and frankly, using developer tools scares me, as this is my first time rooting a phone. So, something straightforward would be great.
ZMan2k2 said:
Well, the 15 min. thing worked out. It seems to run no problem now. But when I shut the music player off, and restart it, I have to Force Stop V4A, then go into the EQ of the music player, then it kicks in.
I'll look for the "audio.conf" file, but how do I implement it, or write it on the phone. I'm not a user of ADB, and frankly, using developer tools scares me, as this is my first time rooting a phone. So, something straightforward would be great.
Click to expand...
Click to collapse
Just checked it: the file name is audio_policy.conf on /system/etc/.
Its the 7.2 on this post:
http://forum.xda-developers.com/zenfone2/general/asus-zenfone-2-flashing-recovery-mode-t3096596
I used a file explorer like "ES File explorer". Just edited the audio_policy.conf to erase the lines of it using the text editor. I dont remember which text editor i used though, i think it was the one built into the es file explorer.
By doing this i dont have to restart V4A anymore. I use spotify app, but i think its the same thing.
just remember to do a backup if anything.
lkzshg said:
Just checked it: the file name is audio_policy.conf on /system/etc/.
Its the 7.2 on this post:
http://forum.xda-developers.com/zenfone2/general/asus-zenfone-2-flashing-recovery-mode-t3096596
I used a file explorer like "ES File explorer". Just edited the audio_policy.conf to erase the lines of it using the text editor. I dont remember which text editor i used though, i think it was the one built into the es file explorer.
By doing this i dont have to restart V4A anymore. I use spotify app, but i think its the same thing.
just remember to do a backup if anything.
Click to expand...
Click to collapse
Grrrrrr. I downloaded ES File Explorer, but it won't let me erase the lines of code you showed me. It just keeps telling me there's an error. Even though I gave it root access and all, it still won't do anything.
Download Root Browser and set audio_policy.conf rw-rw---
Enviado desde mi ASUS_Z00AD mediante Tapatalk
carloshq said:
Download Root Browser and set audio_policy.conf rw-rw---
Enviado desde mi ASUS_Z00AD mediante Tapatalk
Click to expand...
Click to collapse
Root Browser won't let me edit permissions.
nvm. Didn't give it root access.
Okay, I screwed up. I changed the audio_effects.conf file permissions to rw-rw---, and now I have no sound. What's the correct sequence for that file?
ZMan2k2 said:
Okay, I screwed up. I changed the audio_effects.conf file permissions to rw-rw---, and now I have no sound. What's the correct sequence for that file?
Click to expand...
Click to collapse
I have it on rw- r-- r--
Thanks!
Just checked it: the file name is audio_policy.conf on /system/etc/.
Its the 7.2 on this post:
http://forum.xda-developers.com/zenf...-mode-t3096596
I used a file explorer like "ES File explorer". Just edited the audio_policy.conf to erase the lines of it using the text editor. I dont remember which text editor i used though, i think it was the one built into the es file explorer.
By doing this i dont have to restart V4A anymore. I use spotify app, but i think its the same thing.
just remember to do a backup if anything./QUOTE]
Okay, now im trying to get PowerAmp working, and I've done everything suggested, and V4A refuses to start in it. It would be nice to get it going, as I can use the bluetooth connection in my truck, and I'm sick of the gaps in playback and other failings of the stock player. I've shut down the EQ and tone controls and limiter in PowerAmp, and activated the Music tweaks part of the app. If I long press on it, V4A comes up, but it's not working. Any help would be appreciated.
Click to expand...
Click to collapse