Develop Bugs

[N2E][1.0][1.0.1] TouchNooter 1.6.24

This will officially not work for 1.1
What it does:
Enables ADB via uRamdisk
Installs su and Superuser.apk
Installs Busybox
Installs Button Savior
Installs Go Launcher
Installs NookColor Tools (To Enable Non-Market Installs)
Installs Gapps (Gmail, Market, Youtube, Others)
System Files that get Modified:
/system/build.prop - Enabling Google Check In
packages.xml - Allows Gapps to install properly.
framework.jar - Should allow a proper Android ID to generate.
Changes:
June 24, 2011 -
Removed: Multitouch Permission
Added: Modified framework.jar
June 22, 2011 - Fixed: Script not running at boot.
June 20, 2011 - Initial Release
Before you begin:
You must already have a registered Nook Simple Touch
You must have a Gmail/Youtube linked Account. IF you used a Gmail account for B&N Registration you should use that one for this process.
You must either have dd (Linux) or WinImage (Windows) software.
You must have an external microSDCard reader or this will not work. Do NOT use the Nook Simple Touch.
You must have enough intelligence to follow instructions.
Let's get started:
Download TouchNooter from here: touchnooter-1-6-24.zip
Linux: Unzip and use dd if=touchnooter-1-6-24.img of=/dev/sdcard
Windows: Unzip and use WinImage to "Restore Virtual Hard Disk Image" to your SDcard.
Windows Alternative: https://launchpad.net/win32-image-writer/+download
Power off your Nook Simple Touch.
Insert TouchNooter SDcard into your Nook Simple Touch.
Power on your Nook Simple Touch.
You should see the screen "Rooted Forever".
It will boot like normal and you should be asked to select a launcher now. (If not use Button Savior to go home. This will bring up the launcher chooser.)
That was the hard part, now to the simple stuff.
Upon boot unlock your screen.
At the Android Welcome Screen skip Sign In.
Enable Location Services when given the option.
Connect to Wifi and launch Youtube from Go Launcher's App Drawer (Or the App Drawer of your Choice).
Click the Menu button (The right one in the middle of the status bar).
Select "My Channel" and Login using your Gmail Account.
Exit Youtube and Launch Gmail from "Extras".
Sync your Gmail Account and Exit. (If it fails to sync that is fine.)
Open up Market and Accept Terms and Service.
If you made it this far your nook should be successfully Rooted. Go Download an App to make sure.
Enable Non-Market Installs by running the NookColor Tools App.
If your Youtube fails to launch Uninstall and Reinstall Youtube from /data/app
Go to Settings > Device Info > SdCard > UnMount > Format
Thanks To:
Arnold Snarb - modified framework.jar
nemith - helping me figure out getting it to run at boot.
JesusFreke - For getting root.
MrMuffin - For the original Market Hack that we're using.
Currently Working On: TouchNooter 1.11.x

I've probably screwed up, but perhaps not too badly. Tried to follow all the steps and got the system files copied to media, and then to replace the main system files, but there I got confused. I ended up rebooting without attempting to install the youtube app, which I didn't find in the download. Even now, a lot looks like it is working, but I can't even attempt to sign in to google cause I can't get a keyboard to come up to allow me to enter my user name and password. Is there any help for me, or am I a total dunce needing to start over? thanks!
EDIT: I see I am screwed -- no keyboard is coming up for me anywhere. I guess I can go through a major reset but if anyone has a suggestion to just get the keyboard back I will appreciate it.
EDIT2: Well I got past that, simply chose multitouch keyboard instead of Gingerbread in NookColor Tools.
EDIT3: But now I am stuck again as I can't sign in to a google account... says can't establish a reliable data connection to the server, even though my wifi is fine. But at least at the moment everything else is fine, though the keyboard isn't working very well (but it does work; lots of ghosting)

An .img file is being uploaded for TouchNooter 1.6.20 It'll do all the copy and edit stuff, the only thing it can't do is create an android ID.
In the "GappsAndMore" there was some keyboards which were from the NC it was just a raw pull from AN. This is more refined with things that could cause issues removed. (Like Keyboards, Framework.jars from the NC, etc.)

william1853 said:
I've probably screwed up, but perhaps not too badly. Tried to follow all the steps and got the system files copied to media, and then to replace the main system files, but there I got confused. I ended up rebooting without attempting to install the youtube app, which I didn't find in the download. Even now, a lot looks like it is working, but I can't even attempt to sign in to google cause I can't get a keyboard to come up to allow me to enter my user name and password. Is there any help for me, or am I a total dunce needing to start over? thanks!
EDIT: I see I am screwed -- no keyboard is coming up for me anywhere. I guess I can go through a major reset but if anyone has a suggestion to just get the keyboard back I will appreciate it.
EDIT2: Well I got past that, simply chose multitouch keyboard instead of Gingerbread in NookColor Tools.
EDIT3: But now I am stuck again as I can't sign in to a google account... says can't establish a reliable data connection to the server, even though my wifi is fine. But at least at the moment everything else is fine, though the keyboard isn't working very well (but it does work; lots of ghosting)
Click to expand...
Click to collapse
I'd suggest a wipe and running TouchNooter... GappsAndMore had Keyboards and stuff in it and removed the stock keyboard =\

is a wipe in the nook touch holding down the power for 20 seconds?

No you need to do a complete wipe by triggering recovery, but I don't know how to trigger recovery yet.

oh well the perils of early adoption. I'll follow the thread with anticipation!

william1853 said:
oh well the perils of early adoption. I'll follow the thread with anticipation!
Click to expand...
Click to collapse
You could try 8 failed boots. Basically you power it on and then power it off before it fully boots. Do that 8 times and it might trigger recovery.

Confirmed this works great. I'm going to find a fix for the calendar.

GabrialDestruir said:
You could try 8 failed boots. Basically you power it on and then power it off before it fully boots. Do that 8 times and it might trigger recovery.
Click to expand...
Click to collapse
Recovery is holding the power button for 20+ seconds it will trigger recovery

xboxexpert said:
Recovery is holding the power button for 20+ seconds it will trigger recovery
Click to expand...
Click to collapse
Really? Is that from when it's off?

GabrialDestruir said:
Really? Is that from when it's off?
Click to expand...
Click to collapse
Not sure I have yet to try it but someone in the other thread said he called BN and they told him that and he did it.

xboxexpert said:
Not sure I have yet to try it but someone in the other thread said he called BN and they told him that and he did it.
Click to expand...
Click to collapse
I tried it and all I could get was it turning on and off

TouchNooter 1.6.20
This doesn't seem to work for me at all... I tried restoring the backup image and starting from scratch and it still will not work. I tried enabling Google Apps manually and it won't work for me either.
I think I'm done, if the 7th time wasn't the charm then I'm giving up for now...

MystaWright said:
This doesn't seem to work for me at all... I tried restoring the backup image and starting from scratch and it still will not work. I tried enabling Google Apps manually and it won't work for me either.
I think I'm done, if the 7th time wasn't the charm then I'm giving up for now...
Click to expand...
Click to collapse
I ran this on my Nook Touch and it worked just fine. Are you getting the "Rooted Forever" boot screen?

GabrialDestruir said:
I tried it and all I could get was it turning on and off
Click to expand...
Click to collapse
Didn't work for me either. 8 interrupted boots did.

i'm getting the rooted forever screen and then it just goes to the default stock home
any thoughts?
GabrialDestruir said:
I ran this on my Nook Touch and it worked just fine. Are you getting the "Rooted Forever" boot screen?
Click to expand...
Click to collapse

Same problem here... tried to return EVERYTHING to stock too.
yugoliang said:
i'm getting the rooted forever screen and then it just goes to the default stock home
any thoughts?
Click to expand...
Click to collapse
I did a reset of the device back to the out of the box experience, registered with my BN account, shut down and followed the directions to the letter. I had no luck at all. It just shows the Rooted Forever screen, then boots normally is if nothing happened.

Sorry Guys and Gals. Entirely my fault. It seems a combination of my own forgetfulness and bad scripting (I forgot proper codes and methods used in AN) caused this just to do nothing. I'm uploading a version as I'm typing this and will remove "BROKEN" from the title when it's up.

Still broken. init.rc isn't running it's script properly.
Script can be ran manually with:
Code:
adb shell sh /sdcard/nooter/tmp/scripts/Nooter
Will be working on getting it to trigger properly

[N2E] Flash back to clean stock ROM

*Note: By using this method you don't have to worry about re-imaging with someone else's nook rom and overwriting your mac address and serial # with someone else's.
There are two parts to the re-flash, you must do both in this order
1. Re-imaging the PROGRAM portion of the nook.
2. Re-imaging the data portion of the nook.
Part one: Re-image the Nook Touch /system partition
Your nook must already be properly rooted for this to work. Install adb on your PC if you don't have it already. Prep your nook by installing "adb wireless" from the app store and run the app. (if you don't know how to use adb, google it)
Run the "adb wireless" app on your nook and press the "big button" and take note of your nooks ip address.
We now can connect the nook through the adb shell and manually change the BootCnt file so that the boot count is 8. This avoids the pain of manually interrupting the boot process 8 times.
connect to your nook by typing "adb connect (nook ip)" from your pc
Once you have connected to your nook, use the following commands:
adb shell
echo -n -e "\x08\x00\x00\x00" > /rom/devconf/BootCnt
reboot
Thats it for part one. Your nook will reboot and start the re-imaging process. Let it finish and reboot again.
Part two: Re-imaging the data portion of the nook
1. Go to Settings
2. Select "Device Info" under the top "Device Settings" section
3. Select "Erase & Deregister Device"
4. Select the "Erase & Deregister Device" button
5. Select the "Reset Nook" button
A Deregistration message will appear and the nook will reboot.
Upon reset a Clearing data message will appear
This may take a few minutes. The nook will reboot again once complete.
Thats it! Smell that Fresh clean stock nook!
I must give credit to nookdevs dot com. They posted this process for unrooting the nook color. The process is exactly the same for the nook touch. I am a noob on this board so I can't post links yet. I have verified this process works. I had to unroot my nook to get the Shop to work again. Hope this helps. Good luck!

Is it normal for the nook to at the very end of the process bar ? What do I do ? Did I screw it ? I am afraid to try powering it off ?

Please edit your question. I don't understand what you are asking.
Thanks

vacano said:
Is it normal for the nook to at the very end of the process bar ? What do I do ? Did I screw it ? I am afraid to try powering it off ?
Click to expand...
Click to collapse
Are you asking if it is safe to turn off the nook while the progress bar is still visible? Did the progress bar freeze? Please provide more information, I don't understand your question.

Yes. It froze at the very end
Here I have attached a picture as well.
http://forum.xda-developers.com/showthread.php?p=15880635#post15880635

vacano said:
Yes. It froze at the very end
Here I have attached a picture as well.
http://forum.xda-developers.com/showthread.php?p=15880635#post15880635
Click to expand...
Click to collapse
I would just power it down. There is nothing else you can do in that state. How long did you wait?

I'm having trouble getting the Market app to find the adb wireless app...any idea if there's a direct way to install it? Thanks!

coolkatz321 said:
I'm having trouble getting the Market app to find the adb wireless app...any idea if there's a direct way to install it? Thanks!
Click to expand...
Click to collapse
If you rooted with TouchNooter than you shoud have the ADB packages installed. Using the ADB wireless makes things easier, however you can run ADB over usb. Just google "ADB over USB nook" and you will see the link for the nookdevs forum. It gives the instructions for windows, mac, and linux.
I would post the links, but I can't as of yet because I am a noob. One more post should get me to 8.

coolkatz321 said:
I'm having trouble getting the Market app to find the adb wireless app...any idea if there's a direct way to install it? Thanks!
Click to expand...
Click to collapse
Oh yeah... I almost forgot...try this first... There is a known problem where you can't search in the android market. Just go to amazon and get the amazon android market instead. That is what I did.. and if all else falls...you can use the ADB over usb.

J.Harmon said:
Oh yeah... I almost forgot...try this first... There is a known problem where you can't search in the android market. Just go to amazon and get the amazon android market instead. That is what I did.. and if all else falls...you can use the ADB over usb.
Click to expand...
Click to collapse
How did you get the Amazon market?! My Nook simply does not want to play nice.

coolkatz321 said:
How did you get the Amazon market?! My Nook simply does not want to play nice.
Click to expand...
Click to collapse
open up your browser on your nook and go to:
http://www.appbrain.com/app/siir.es.adbWireless
appbrain.com will probably have you set up an account before you can download it.
google is your friend.

My Unroot Method
Maybe this will work for you all too. It worked really well for me (but this is assuming you don't have the 1.0.1 update):
1 - Turn nook off and turn on pushing power button than 2 bottom buttons.
2 - Press home twice to clear data
3 - Login as normal and then go to Settings and Erase and DeRegister your Nook
4 - When nook comes back up login and register nook as normal
5 - Download http://su.barnesandnoble.com/nook/n...Dpomf5qvKtTeXxjxcgaa2cS/nook_1_0_1_update.zip and put it on the root of your nook (not SD card)
6 - Let nook apply the update
7 - That should be it.
I deregistered it after that. Rebooted. Reset. Rebooted. Every time came up stock for me to register.

Kohr-Ah said:
Maybe this will work for you all too. It worked really well for me (but this is assuming you don't have the 1.0.1 update):
1 - Turn nook off and turn on pushing power button than 2 bottom buttons.
2 - Press home twice to clear data
3 - Login as normal and then go to Settings and Erase and DeRegister your Nook
4 - When nook comes back up login and register nook as normal
5 - Download http://su.barnesandnoble.com/nook/n...Dpomf5qvKtTeXxjxcgaa2cS/nook_1_0_1_update.zip and put it on the root of your nook (not SD card)
6 - Let nook apply the update
7 - That should be it.
I deregistered it after that. Rebooted. Reset. Rebooted. Every time came up stock for me to register.
Click to expand...
Click to collapse
Thanks! This method has worked best for me.

Now that you upgraded to the 1.01 update, will this method still work?
Have you tried it?

I have not yet as I haven't tried rerooting it again.
Sent from my HTC Sensation 4G using XDA App

[DEV] Backtrack 5 on T-mobile SGS2 3/5/2012 (NEED KERNEL DEVS!!!)

DISCLAIMER:
I am not responsible for you bricking your device.
BOTTOM LINE
WHAT IS BACKTRACK?
Ok ladies and gentlemen. I guess I should have started with this. But, as another poster stated, if you don't know what Backtrack is, then you don't need this. But, I have to clarify some misconceptions as well. No one has stated correctly what Backtrack is. Backtrack is more than a tool to crack wifi passwords. Its an entire security distro. It it literally packed with thousands of tools to do everything a security tester or "hacker" needs. It is packed with metasploit (google it), sslstrip, nmap,wireshark, just to name a few. Why would they make an entire linux distro just to hack wifi routers? If you have questions, just ask.
Now with that out of the way. Backtrack runs on an image that is never mounted to your system. Nothing is replaced. It is basically a side load which can be turned on or off whenever you want while the phone is on. There is no flashing involved what-so-ever. It is so easy a caveman can do it.
This is a persistant version.
Finally on our device. Everything is fully functional with the exception of using anything that involves packet injection and setting your adapter to monitor mode (yes, this means you cannot crack WEP/WPA yet). The concept is just that we have to modify the wifi adapter driver to accept monitor mode as well as allowing packet injection. Everything else works perfectly.
NEEDED APPS
7zip PC ONLY
Terminal Emulator (Free)
AndroidVNC (Free)
(Optional)
Tasker (Paid)
NOTE: You will need approximately 3.5GB of free space on your internal SDcard (not the removable SD Card at /sdcard/external_sd/)
FOLLOW THESE DIRECTIONS SPECIFICALLY
INITIAL SETUP (only needs to be completed once)
1. Create a folder called "bt" on the base of your Internal sdcard (directory should look like it does below:
/sdcard/bt
2. Download the following scripts and put them directly to the new "bt" folder you just created. The directory should look like it does below:
bt
installbt.sh
startbt
stopbt
/sdcard/bt/bt
/sdcard/bt/installbt.sh
/sdcard/bt/startbt
/sdcard/bt/stopbt
3. Download this version of busybox for temp use and put it in the following directory shown below (you may need Root Explorer to change permissions to create the directory tree and upload the file):
busybox
/data/local/tmp/bt/busybox
NOTE: /data/local/ should already be there as well as tmp. You will have to create the "bt" folder in that tree. You must have the directory tree and file shown exactally as shown: /data/local/tmp/bt/busybox . If you don't, you can't complain to me why you are getting errors.
4. After you verify that those 5 files are in that directory, then you can proceed to downloading the bt.img file below and put it in the "bt" directory as shown below:
Update
Download each of these and use 7zip to extract the bt.img from them.
bt.7z.001
bt.7z.002
bt.7z.003
bt.7z.004
bt.7z.005
bt.7z.006
bt.7z.007
bt.7z.008
bt.7z.009
bt.7z.010
NOTE: these files total approximately 3.3GB
Extract on your PC and upload to:
/sdcard/bt/bt.img
5. After you have completed the above steps, reboot your phone and re-verify all the above files are in their correct directories:
/sdcard/bt/bt.img
/sdcard/bt/bt
/sdcard/bt/installbt.sh
/sdcard/bt/startbt
/sdcard/bt/stopbt
/data/local/tmp/bt/busybox
6. Open Terminal Emulator and type the following commands. If you recieve any errors then the above steps were not completed correctly, so go back to setp 1.
$ su
# cd sdcard
# cd bt
# sh installbt.sh
# startbt
# bt
7. At this point you have installed Backtrack and have a Backtrack 5 shell.
8. Now the good part. To open the GUI of Backtrack, enter the following command:
# ui
9. Nothing? Be patient. Look at the output and take note of the number "X" located at "localhost:X" from the X desktop line of the output. The VNC server is running at port 5900 so you must add "X" to get the new server port for Backtrack, ie. X=1, then 5900 + 1 would give you 5901 as the new server port.
10. Open AndroidVNC and enter the following info:
Nickname: whatever you want
Password: 12345678
Address: 127.0.0.1
Port: whatever you got from your little math problem above
Username: leave blank
Change Color Format to 24-bit color (4 bpp)
11. Now all you have to do is connect after you have created the connection.
START EACH TIME
1. Open Terminal Emulator and type the following commands.
$ su
# cd sdcard
# cd bt
# startbt
# bt
# ui
2. Open up AndroidVNC and connect to the privously created connection.
SHUTDOWN
1. Tap the settings softkey and tap disconnect (to disconnect you from the VNC server).
2. In Terminal Emulator, type the following commands:
[email protected]: # killui
[email protected]: # exit
# stopbt
# exit
# exit
3. This will close it all out for you, but to ensure a full shutdown, reboot your phone.
Thats all!!!!
Optional Automation
If you have Tasker, then you can add some automation that will automatically execute the Terminal commands and open AndroidVNC.
Download the following file and put it in the following directory which should look like this after it is added:
bt.prj.xml
/sdcard/Tasker/tasks/bt.prj.xml
Then open Tasker. Then go to Settings > Preferences > UI and uncheck "Beginner Mode" and touch the gree checkmark.
Now under the buttons across the top (Profiles, Tasks, Scenes, Variables), you will see a very faint arrow pointing down. Touch and drag down and a tab(s) will be seen across the top. touch and hole the tab with the house. Touch "Import". A "Project File Select" window will pop up. If the file does not show up, then touch the back arrow, and click on the "tasks" folder. Then click on the file "bt". Then a tab at the top will be created that is labled "bt". At the bottom right of the app, make sure that the button says "on". Now exit out of the app. Go to your favorite screen and long click the screen. Next, add a widget, the touch tasker. A window will pop up with alot of entries. Go to the bottom and find "bt on" and touch it. After that, another window will pop up. At this point you could just click the green checkmark and be done. But another thing you can do (optional) is touch the button to add an icon, then check the green checkmark.
Now you will have an icon on your screen that will automatically boot up backtrack and bring you straight to the UI. The next step you want to do is have an icon that will turn it off. To do this, Go to your favorite screen and long click the screen. Next, add a widget, the touch tasker. A window will pop up with alot of entries. Go to the bottom and find "bt off" and touch it. After that, another window will pop up. At this point you could just click the green checkmark and be done. But another thing you can do (optional) is touch the button to add an icon, then check the green checkmark.
Now you will have an on and off button for Backtrack!!!
Please thank me if you like this and donate if it helped you!!!
If you are also a DEV that would like to help on modifying the wifi drivers to allow injection and adding monitoring, please contact me ASAP.

Very awesome !! Can't wait for monitor mode working !
Ty and im following this thread intently
Sent from my SGH-T989 using xda premium

No problem. Im trying to work on it but honestly. I may need some serious DEV helpers to mod the drivers.

Good work man thank u
Sent from my SGH-T989 using Tapatalk

Could this essentially help me in helping my neighbor remember his wifi password
Sent from my SGH-T989 using xda premium

im rly sry but what is this for something for wifi?

Sorry I know this is going to sound noobish, what is this used for? Why would I want it?
Dfjcisnv

If you don't know what this is for then you don't need it lol
Sent from my SGH-T989 using xda premium

Thank you, both of you. I admit after I hit submit I went and googled backtrack. While I guess its a cool party trick, in my opinion of course, I wouldn't have any use for this. Its cool that it is working and the effort the OP put into this, so I apologize if this is taken in the wrong context.
On the other hand, im looking to run Ubuntu on this phone and hook it up to my TV, using a Bluetooth keyboard and utilize the full functionality of this device.
Dfjcisnv

slightly off topic but I have Back Track 5 and a wireless router capable of packet injection. I have no idea how to install the drivers for it on my computer. I read through the instructions but its very complicated anyone familiar with doing this could you pm me?

This is something I can use and appreciate your work. Unfortunately, the links are down.
Thanks in advance
Sent from my SGH-T989 using xda premium

I just a notification from the host saying that I violated their bandwidth restriction and disabled the link permanently. Can anyone help me out with a host that will allow a 3.26GB file for hosting?
Sent from my SGH-T989 using xda premium

OP updated!!!!
Sent from my SGH-T989 using xda premium

When someone gets it running on their device, please let me know what you think. Also add anything that you would think is benefitial.

Could this methods be used loosely to "flash" other Linux distros?
Sent from my SGH-T989 using XDA App

Yes if that distro offered an ARM version of their distro. Then you just need to write a couple scripts to launch the .img file.
Sent from my SGH-T989 using xda premium

Some of you are PM'img me questions about something now working and they are all due to file downloads. Not to sound like an a$$hole, but go back to the directions and follow the directions specifically. Re-download the files and try it again.

YES! you rock!

mrgman421 said:
YES! you rock!
Click to expand...
Click to collapse
Thanks. Just need a little help with the drivers to complete my mission.
Sent from my SGH-T989 using xda premium

Very very awesome!

[GUIDE] New Fire Phone with FireOS and Google Apps - A Start-to-Finish Walkthrough

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 debugging​Installing 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!

Need Help: Unblocking/Rooting of Remote Control JR 28x (Android 4.0.3)

hi Guys,
i have some questions here and i seriously need your help.
I'm a RC-Model enthusiast and i own a Remote Control Transmitter manufactured by JR Japan.
This RC Transmitter is operated by an Android System (4.0.3).
http://www.jrpropo.com/english/propo/28x/
Unfortunately JR Japan has gone bancrupcy and so the production and support for the 28x is gone and no further development will be done.
The mayor point is:
I'd like to hack this thing... meaning first:
- get root access
- do a full rom backup
- install SuperSu App or anything else like that
- activate Bluetooth (disabled by factory)
- reverse engenieer the apps any modify them if possible. every app seems to control some registers on another board (main RF-Board). so for example there is an app called "subtrim". With this app you can modify the neutral pulse which is send to the receiver via the RF board.
- so i got adb access and shell already and tried some things.
- can install various apps and download the installed apps
but without root everything else is worthless.
so the speciality is:
there seems to be a Texas Instruments Board inside. I researched this one AM335X-EVM-SK (http://processors.wiki.ti.com/index.php/AM335X_EVM-SK_Android_Devkit_Guide) --> system info
On this Board/the Components Android 4.0.3 is runnig.
I Figured out that there isn't a normal bootloader because you can't boot into bootloader via ADB Shell.
I'm scared about using the "standard" root apps/methods, because i think the special Mainboard and Booting method isn't compatible to anything else compareable in the "Mobile-World".
--> soloution?
--> what further infos do we need?
another thing is the bluetooth activation
if you enter the following comands @ via ADB Shell, you can try to get Bluetooth enabled - but there isn't an option to click "yes" on the display, when the system asks for the permission to enable BT. only some display thatr bluetooth can be enabled, but nothing else happens. Normal BT activiation isn't in the settings menu!
Code:
adb shell am start -a android.bluetooth.adapter.action.REQUEST_ENABLE
Code:
adb shell am start -a android.bluetooth.adapter.action.REQUEST_DISCOVERABLE
so i think bluetooth is inactivated somewhere deep inside the kernel. and without root access .... you know what i mean.
if i install the superSu ap, it doesn't work because the device isn't rooted.
it would be very great if someone can help me and tell me what things we can do, to hack this thing.
I'm not a developer (yet) but i have some serious interest to get inside and learn how the things work here.
Thank you so far guys
regards