Develop Bugs

[N2E] Knowledge Base

This Thread is outdated!
I will update it soon!
Thanks for your understanding
Hello everybody,
as there is no sub-forum for the new nook simple touch (help to get one),
all information are split on several posts in the nook color forum.
I want to create a central thread which list all the knowledge and work that is already done.
The most solutions are NOT my work!
I will link to the post and add the author,
please thank them for their work.
Basics
Update
There is an update for the nook touch!
(not recommended for now)
Checkout the discussion: Nook STR update 1.0.1
Screen Refresh
To avoid ghosting you can easily refresh the screen by pressing the n button twice (open and close default launcher).
Hidden back "button"
You can easily go back by swiping in the middle of the topbar from right to left.
(You may need this in stock apps / settings, after getting root you get 2 buttons for menu and back on this area)
Hidden Browser
you can access a browser by typing in an url into the searchbox,
but the browser doesn't work well...
liliputing.com nook touch browser (no root)
Backup
Backup/Restore N2E by jocala
Windows HowTo is on the second post
Factory Reset / Recovery
[TOOL] nookRestore { Nook Touch - Factory restore | recovery } by ros87
B&N - nook Support
Rooting:
Please take the time and get a backup of your nook!
nookdevs.com NookTouch Rooting (linux, mac, windows)
JesusFreak of nookdevs make all this possible!
Here you can find his original guide.
TouchNooter (linux, mac, windows)
GabrialDestruir said:
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)
Click to expand...
Click to collapse
Root & Setup Script Kit (windows only)
xboxexpert said:
Full Superuser Access
Updates are permanently blocked!
Unknown sources Enabled (install non-Market applications)
adb debugging is active [mostly for developers]
Ability to replace the Authors ****ty pictures
Ability to remap the left buttons to Menu & Back
Market Installed & Working! Login to YouTube with your GMAIL!
Software Included:
AdFree (Block those nasty ad's) [Wi-Fi needed]
Button Savior (Displays Softkeys)
gTab simi Clock (really awesome clock for your desktop)
Kindle (read your Kindle books on Nook, lol) [Wi-Fi needed]
LauncherPro (default launcher instead of Nook base launcher)
Superuser (provides a list of applications that use superuser access)
Click to expand...
Click to collapse
Advanced:
(need root)
adb
WiFi
by default you can only use wifi to connect to your nook!
Please consider that anyone in your network can connect to your nook!
This is a serious security problem!
mycr0ft modified the uRamdisk to disable adb over wifi by default! (not tested)
Code:
adb connect [I]NOOK-IP[/I]
USB
xor_ uploaded a uramdisk with adb usb enabled
and traycold has found drivers for windows (thanks to cceerrtt)
xboxexpert modified the adb usb driver to work with the n2e. (not tested yet!)
[GUIDE] ADB Workshop and Guide for everyone
Remapping Hardware Buttons
n Button
[MOD+APP][11Oct11] Configurable "n", "reading now", "RecentDialog" + Activity Picker!
XorZone said:
Features of mod
* Will return stock android go to home by short press of "n" button and recent apps dialog on long press (Configurable)
* All B&N quicknav buttons configurable, it even loads apps icons (after reboot)
* Reading now" button configurable
* NOTE: Installation of the jars w/o conf will have stock B&N effect + recent apps
Features of application
* Implements Activity Picker, so any app (i.e. Launcher Pro) can use "Shourtcuts" dialog that B&N removed.
* Configuration UI for above mod
* (In future) Configuration UI for page buttons
Click to expand...
Click to collapse
Page-Turn Buttons
The main thread is from xboxexpert,
the user aruangra shows how to map the keys to volume up/down so you can use it for scrolling in some applications
Softbutton
Softbuttons can add little buttons to your user interface which simulate the normal android buttons (Home, Back, etc.),
Button Savior is working very well.
OMGWTF_BBQ modded it for the eInk Display.
Market & gapps
If you have already rooted and want to enable the market by yourself you can use the tutorial on nookdevs from the nook color. GabrialDestruir have tested this and confirmend its working.
Additionally i have written down some steps to activate it by using resources of the touchnooter script.
GabrialDestruir updated his script, i dont know if my tutorial still works
AFTER you get the market working you can
update the market and gapps
or, just update the market.
This will fix the market search too
Language / Locale Settings
If you live outside of the USA and managed to get a nook,
there are a few steps to customize the system to your locale / regional enviroment.
To change the system language and the keyboard you can look here:
customize language
Timezone and 24:00 Clock can be set on the default settings menu
(On first-start-setup you can only choose US-Timezones)
Landscape / Screen Rotation
[APP] Orientation Switch by XorZone
on LauncherPro you have to enable Auto-Rotation (thanks to densets)
AdHoc WiFi
If you want to connect to an AdHoc WiFi you can checkout a fix for the nook color:
[FIX] AdHoc Wifi support on the NC! thanks to markmc87 & jago25_98
Misc:
Wallpapers
OMGWTF_BBQ made some nice wallpapers
The Wallpaper from the Video by OMGWTF_BBQ
Michael.Rose made a pencil sketch of it
Videos
XDA-User OMGWTF_BBQ upload a Nook2 Root Tour on youtube
JesusFreak's proof his working root with Angry Birds on Nook Touch
The Nook Touch has a Web Browser - No Root Required!
Gizmo - Nook Simple Touch Reader
B&N The All-New NOOK Guided Tour
App info
✔ Kindle, Kobo, txtr, Aldiko, Moon+, FBReader
ryanpl write together a list of supported apps
OMGWTF_BBQ Root Tour Video
You can try all other apps for Android 2.1
NOT WORKING:
xda-developers (some threads shows a blank page)
Pulse News (crash after initial screen)
(version from nook color market is working)
Skype (freeze on login screen)
Tricorder (system freeze)
Hardware/Software specs
Icehawk78 posted some system information on request.
stock-kernel:
MystaWright said:
VERSION = 2 | PATCHLEVEL = 66 | SUBLEVEL = 29
(2.6.29-omap1)
Click to expand...
Click to collapse
Links:
New Nook 2 eInk Reader Announced! Available for Preorder
Nook Touch Root Guide is OUT.
[REQUEST] B&N Nook Simple Touch forum
[N2E] Nook 2nd Edition Touch - Root
[N2E] Nook 2nd Edition Touch - Development
[N2E] TouchNooter 1.6.24
[NST] Root/Market & Setup Script Kit
[N2E] Nook Touch - App Support for Hardware Buttons
[N2E] Recovery & Source for Nook Touch
[N2E] Nook Touch n-button mapping
[N2E] modified framework.jar
Backup/Restore N2E
[NC]/[N2E] Warning!
Nook STR update 1.0.1
[APP] Orientation Switch
[MOD+APP][11Oct11] Configurable "n", "reading now", "RecentDialog" + Activity Picker!
[TOOL] nookRestore { Nook Touch - Factory restore | recovery }
[N2E] Nook ADB over USB on linux.
Nook Touch kernel hacking
[FIX] AdHoc Wifi support on the NC!
[Q] [POLL] Do we need NST specific launcher? If Y - how should it look like?
nookdevs.com NookTouch Rooting
ReviewHorizon.com Root Guide
Mike Cane's xBlog - Nook Touch Rooting: June 27th News
IRC: #nookdevs @freenode
B&N All-New NOOK Porduct Website
B&N nook Support
THANKS TO ALL OF YOU!
If i forget something or got something wrong, please feel free to complete this thread!

... reserved ...

First
Sent from my SPH-D700 using XDA App

What's the consensus as to the best launcher to use...
I currently use ADW, which seems to work ok. Biggest complaint is I can't see the text on the settings menus...

I prefer a white backgounnd. So ADW seems to be an only option. I am using ADW EX.

updated the fist post,
thanks to DenisTheMenace for the info about adb usb drivers,
the mod/person who made this stickie,
and again all of you
Xhorder said:
What's the consensus as to the best launcher to use...
I currently use ADW, which seems to work ok. Biggest complaint is I can't see the text on the settings menus...
Click to expand...
Click to collapse
iam using ADW too,
i like it more than Go Launcher or LauncherPro
but when i tried them i recognized some empty settings menus too,
so i dont think its the launcher that shows the settings menus without text...

rev0l said:
so i dont think its the launcher that shows the settings menus without text...
Click to expand...
Click to collapse
It's not without test, the test is white on white background, that's why we don't see anything.

I got pulse to work, I used the pulse from the nook apps shop.

mkenney12 wrote me a pm.
he wants that everybody consider the consequences of using a rooted nook touch.
its definitely a point that everyone has to keep on mind!
rmkenney12 said:
Hi,
I'm not sure who to send this to in the xda-dev
community, but noticed that you were maintaining
the KB articles for the Nook Touch root. I tried
posting to the touchnooter dev thread, but I don't
have the requisite 10 messages, so I couldn't even
thank them.
I've been able to root my N2E with the
touchnooter root: the most recent 1.6.24. I'm
extremely happy with the results, but am having a
major concern that doesn't appear to be getting
proper coverage in that or other roots. (I initially
tried the noogie root with lesser results).
<Rant On>
IE, adb wireless/wifi access.
Nobody seems to be expounding on the fact that
it's an enormous freaking barn-door-size gaping
hole in the security of the N2E(or doing anything
to eliminate it). You yourself mention it in
passing in your KB article, but only give it a single
line.
Essentially, once these things are rooted, they
are -enormously- vulnerable if they are taken out
into the public, either at a Barnes&Noble store,
or at any other hotspot. All it takes is for a hacker
sitting there at that hotspot with a laptop, scanning
all of the IP's in that subnet for IP's that respond
to the adb port, and they can do a simple
#adb install MyFavBotController.apk
or somesuch thing. If adb pukes on them(IE, it's a
non-rooted Nook), then they just keep scanning.
Unless you're sharp and see the notification tab
popping up, you may never notice it. They can
install any freaking thing they want on your Nook.
Evetually you've got hundreds or thousands of
infected Nooks running bots, or some other fun
little thing(s) implanted on them.
Everybody seems to be incredibly happy about how
easy it makes their experimentation, and all of the
root developers seem to be focused on making sure
that adb wireless is enabled, either in the startup
scripting or even in the uRamdisk as with the
touchnooter root.
Sure, you can install the adbWireless app from the
market, and it will turn off adbWireless, but:
a) when you initially run the adbWireless app, it
doesn't even properly report that the adb wifi
function is on. It reports it as off, even though
it's actually still responding to adb connects.
So now you have to remember to turn it on,
and then back off. That does work(for a little
while).
b) it's not permanent with some roots, like the
touchnooter. I disable adb wifi with the
adbWireless app, it's off, and everything is nice
and safe? if I put my N2E through a power
cycle, guess what. It's been turned right back
on again. That's completely whacked.
1) For one thing, as an older person I may
forget to use adbWireless to keep turning
adb wifi off after power-cycles. Over and
over and over again.
2) Even if you remember, there's a window of
access during power-up that's about 30-60
seconds long before you'll be able to run
adbWireless to shut things down. A hacker
could do a lot of damage to your Nook in
that time.
3) I have heard rumors of Nooks turning
turning themselves back on after being
powered off. So now you could be in a
hotspot, your Nook could turn itself on in
your knapsack without you even knowing,
and the hacker sitting there has all the
time in the world to beat on your poor little
Nook.
It's BONEHEADED. adb Wifi should NOT EVER be
automatically turned on by the bootstrap. NEVER.
If developers of these roots want to make it easy for
the users or other devs using them, then simply
bundle the adbWireless application along with
SuperUser, Yahoo, and the other apk's they've
included in their root distro's.
Let the -users- decide when and where it's safe for
them to use adb Wifi. Devels are NOT doing them a
service by forcing adb Wifi on them, or encouraging
them to use it under dangerous circumstances.
</Rant Off>
Sorry, but I have a rooted Nook that I'd like to take
outside the confines of my home. Unfortunately,
I don't dare to now. So yah, I'm feeling cranky :-(
rev0l. -please- pass this on to any developers
you might have contacts with.
Thank you!
= Glucosaurus
Click to expand...
Click to collapse
i dont know if someone can disable the access over adb by default...
may you can use apps like tasker or automate it to disable wifi when your accesspoint is not in range or start the adbwifi app while connecting to a public wifi.

Xhorder said:
What's the consensus as to the best launcher to use...
I currently use ADW, which seems to work ok. Biggest complaint is I can't see the text on the settings menus...
Click to expand...
Click to collapse
I love Zeam.

I think that the best way to avoid the wireless adb security hole would be to enable adb over usb and disable adb wireless if it is possible.
I have read on irc someone (maybe JesusFreke) saying that we just have to do something like modifying adb or doing something else (I don't remember very well)

I'm also trying to find out how to adb with usb. In particular I'm looking to get my N2E to connect to my iPhone running MyWi 4.0. I've read that the nookdevs Ad-Hoc_WiFi wpa_supplicant file for the NC will work with the N2E, but I haven't found a way to connect with USB and I'm too scared to try it over wifi in case it goes wrong and I won't be able to connect with adb over wifi to fix it. Any help would be much appreciated.
Edit :
Managed to get ad-hoc wifi working by pushing the fixed wpa_supplicant.adhocfix file to the /system/bin/ folder with adb over wifi.
Then, I switched the wifi off on the N2E and opened terminal emulator and did the following :
Code:
su
adb shell mount -o rw,remount -t ext2 /dev/block/mmcblk0p5 /system
mount
cd /system/bin
mv wpa_supplicant wpa_supplicant.old */make backup of original wpa_supplicant file/*
mv wpa_supplicant.adhocfix wpa_supplicant
chmod 755 /system/bin/wpa_supplicant
exit
I am now able to connect to my iPhone's MyWi hotspot.
For security when connecting to a public hotspot, I have installed the ttxapps wifi adb app from the android market and turned off adb over wifi, meaning I can toggle it on only when I wish to connect on my home network.

does anyone have system restore image?

another pm from a user that cant post
J.Harmon said:
I figured out how to get a full factory "re-image" of my nook touch.
I followed the instructions for the nook color here:
Method two: Set the Boot counter to 8 by typing
http://nookdevs.com/Flash_back_to_clean_stock_ROM
I rooted my nook touch using touchnooter. Loaded up the amazon app store and played around for a while. But I found after I rooted the nook that the nook store didn't work any more. So i wanted to get back to factory state. I then installed the wireless adb app. I logged in to my nook using my linux pc and followed the above directions. After the re-image you have to do a data reset by going in and restoring to factory settings in the nook itself.
As soon as I gave the reboot command it started the re-image as seen in this link:
https://lh3.googleusercontent.com/-p...2E_Restore.JPG
I'm sending you this message because I'm a "noob" and can't post in the developer forums. So if you wouldn't mind reposting for the others to use.
Click to expand...
Click to collapse

Was anybody else able to get to "Restoring Factory Image..." dialog?
It happened to me after 20+ resets, I was just searching for bricked N2E solution and kept on pressing the button... I would like to know how to replicate this again

i tried it with the 8 times boot failure method, it brings up the factroy reset screen, but it does not the reall factory reset, root and some other stuff were still n the nook after this "factory reset" don't know..
and don't tried (or even read) the method from the pm...
too busy at the moment :/

Inspired by rmkenney12 (and rev0l), I updated the uRamdisk file from TouchNooter 1.6.24 so that adb over wi-fi does not run at boot.
Disclaimer: Don't try this unless you know how to restore your nook in case it does not work.
To install the new uRamdisk:
Unzip the attached file somewhere, then...
Code:
adb connect <nook>
adb shell mkdir /cache/boot
adb shell mount -o rw -t vfat /dev/block/mmcblk0p1 /cache/boot
adb push <path>/uRamdisk /cache/boot
adb reboot
Cross your fingers and hope it works.
You will also want to download an app to turn adb on and off. Search market for 'wifi adb'.
P.S. Does anyone know specifically what needs to be changed in the uRamdisk to enable adb over usb?

This guide isn't working for me. It says that after you create a noogie sd card, just pop it in, start the nook and it will mount the 7 partitions....
What 7 partitions? They never show for me. When I start the nook with the card inside it mounts the "boot" partition which is 64.8 out of 74.7 megabytes.
That's it. That's all I see. Inside of this partition are the files that were contained in the noogie image.

ibex333 said:
This guide isn't working for me. It says that after you create a noogie sd card, just pop it in, start the nook and it will mount the 7 partitions....
What 7 partitions? They never show for me. When I start the nook with the card inside it mounts the "boot" partition which is 64.8 out of 74.7 megabytes.
That's it. That's all I see. Inside of this partition are the files that were contained in the noogie image.
Click to expand...
Click to collapse
wrong thread?
which guide do you mean?
anyway, i don't know if windows can recognize all partitions...
download a live cd linux and try again

Ok... This is on windows 7. I dont know how to use Linux.
I am trying to root the Nook STR and using the guide provided here. It just gets stuck at the rooted forever screen, and the rest is as described in previous post.

[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

[ROM][CM7] Defy Pro XT560 Support Thread

This is a support thread for the ROM posted here.
http://forum.xda-developers.com/showthread.php?p=49394355
* It is very important to clear factory data/cache after installing the CM7 rom.
* If your stuck on the android boot screen, connect usb and do a logcat to see what it is crashing on.
* The battery_charger has been replaced in this build as a safety backup to get into bootmenu. Anytime the phone is powered off and then plugged in it will boot to bootmenu instead of the charging screen.

* It is very important to clear factory data/cache after installing the CM7 rom.
Click to expand...
Click to collapse
I make all wipe data/cache and even Dalvik cache before and after install CM7 - but I stuck on the android boot screen.
But note: I made all wipes from CWM, because stock recovery is not works on my phone (only green robot and yellow triangle and that's all - nothing key works, only pull battery helps).
* If your stuck on the android boot screen, connect usb and do a logcat to see what it is crashing on.
Click to expand...
Click to collapse
How can I make this (run logcat)?
Thanks for the advices.

Im not sure the clear data/cache works right in CWM. I have not tested it. To access the menu in the stock recovery hit the Home key.
To output a logcat open a command prompt and run "adb logcat"
If you want to output it to a file use "adb logcat > filename.txt"

so there is some querrys:
- torch app does not work as a flashlight, while it stay in status bar and even task killer wont help
- led notification light does not work at all, i guess there is no app for that and original is missing
- it wont unlock sim card, or lock it while it's unlocked. message is "incorrect pin". previously unlocked on other phone sim works fine. pin correct.
- the reboot menu list wont operate with joystick, only touch.
- both cameras wont work in skype, when forced induce crash.
- dev tools options become a force close
- voice dialer started by long press call button opens in wrong screen orientation and does not work. it work if started from all apps.
- superuser does not ask about allowing su permissions, there is no app listed as allowed su perm. while all super su apps works fine as usual.
- yandex maps app issue. rendering map result is quite not what it should be

I did it! Thanks for stock recovery main key (Home) .
And now some my notes (first, I use Russian language and CM7 has it).
- torch app doesn't work - this right for me too;
- about led - not work too;
- about sim - not check this yet;
- the reboot menu OPERATE for me with D-Pad;
- I don't use Skype;
- dev tools work in full for me;
- all correct about voice dialer;
- it's right too;
- don't install yandex maps yet.

wifi is not work

clxer said:
wifi is not work
Click to expand...
Click to collapse
was't been working for me too, but first reboot solved it
a lot of apps that uses the hardware gpu does not work properly, i guess this is same as camera driver problem and it can't be resolved till motorola releases it freely(only if)
also i am having issue with call ringtone - it rings for fraction of a second and then goes silent

I missed some egl librarires in the build, copying the attached files to /system/lib/egl should correct some of the graphic issues.
retr13 said:
was't been working for me too, but first reboot solved it
a lot of apps that uses the hardware gpu does not work properly, i guess this is same as camera driver problem and it can't be resolved till motorola releases it freely(only if)
also i am having issue with call ringtone - it rings for fraction of a second and then goes silent
Click to expand...
Click to collapse

superdave said:
I missed some egl librarires in the build, copying the attached files to /system/lib/egl should correct some of the graphic issues.
Click to expand...
Click to collapse
antutu now running, mx harddecoding on the other hand dont
yandex. maps still weird

Good Job, and thank you
By the way, Pls tell me how to root defy pro.
I had tried many tools but both fail.

jimway said:
By the way, Pls tell me how to root defy pro.
I had tried many tools but both fail.
Click to expand...
Click to collapse
With poot.apk
http: / / ofimatica-programacion[dot]blogspot[dot]com/2014/02/rootear-telefonos-android-sin-necesidad[dot]html

Any updates?
edit- specifically, does CM7 fix the poor bluetooth A2DP quality of the stock ROM?
Sent from my XT560 using xda app-developers app

Problems using Blank Store

Hi folks,
I'm trying to keep my Fairphone free of googleApps (because, you know, $reasons), but as usual it's not that easy.
I am struggeling to get NoGApps working. First of all: kudos to @MaR-V-iN - I don't have a paypal account, but I could invite you for a Kölsch next time I'm in the area.
Can anybody review my steps and possibly describe how to get it running properly?
0. installed OI File Manager (to be able to access the internal partition)
1.1. downloaded μg v1.3.2 (NetworkLocation.apg)
1.2. ( tried to copy to /system/app/NetworkLocation.apk - to no avail: "... could not be copied")
1.3. installed NetworkLocation, allowed access in XPrivacy popup, rebooted.
1.4. downloaded cells-world.db, renamed to cells.db, moved it to /sdcard/.nogapps/cells.db
1.5 tried to find any sign of the application. (Found nothing.)
Sadly, Network location does not show up, anywhere. Am I looking in the wrong places?
2.1. downloaded Blank Store 0.6.6 (BlankStore.apk)
2.2. (renamed it to com.android.vending.apk, tried to copy it to /system/app/com.android.vending.apk - no success.)
2.3. renamed again, installed BlankStore.apk, allowed access in XPrivacy popups, rebooted.
2.4. downloaded android-checkin-1.0.jar and bla.bat, copied them to the location of java.exe, generated an android ID.
2.5. went to menu [Settings]{Accounts}
2.5.1 entered (dedicated...) google credentials and android ID,
2.5.2 entered slightly changed credentials that @DSoundso mentioned (SDK should be 17, I think. I also used a German carrier's MCC-MNC).
2.5.3 rebooted.
2.6 opened BlankStore: yay, I can search it. But I can't install any app: it crashes constantly.
I should mention that the Account settings were gone several times, so the BlankStore would close immediately. I had to re-enter them, and tried also exactly the credentials @DSoundso mentioned in the NOGAPPS thread.
I can't "sync" the account under [Settings]{Accounts}{Sync}. It just "says Sync is OFF", "sync now" does not seem to work.
I logged into the google account on a desktop PC, and no devices show up. ("No active devices").
So, the next steps are unfinished:
3.1. downloaded Maps API v1 (nogapps-maps.zip)
3.2. tried to download via Blank store: BusyBox, TWRP, TitaniumBackup. (BlankStore crashes.)
...to be continued?
Can anybody walk me through?
Or at least single out any errors I made above?

Hey, did you have a look at the XDA-Wiki section about installing the Blank Store? Following this step-by-step should hopefully install the Blank Store
I am too avoiding the Google Apps and also installed the maps successfully (didn't try NetworkLocation yet) and your problems with "could not be copied" sound like a problem with the user rights.. I'm not sure how your file manager works but the with the Android SDK (see above link) and the right commands it should work.
As far as the crashes of the Blank Store are concerned: at first mine also didn't start and crashed, which was caused by the missing Store account but as it sounds yours IS starting but then not really functioning, right? :|

arghwhymustiregister said:
Hey, did you have a look at the XDA-Wiki section [...] As far as the crashes of the Blank Store are concerned: at first mine also didn't start and crashed, which was caused by the missing Store account but as it sounds yours IS starting but then not really functioning, right? :|
Click to expand...
Click to collapse
Thanks, I gave that a try yesterday. 1.7 gb download, what a mess... But solved the problem: it was a rights issue. I was under the impression that the OI File Manager had superuser rights. I was wrong. Got BlankStore working now, but it crashes still quite often on download.
I'm still not sure what to make of it. As I said, it *seemd* to be working before as well, but *no* download was finished. Now, *some* finish their dl, and if they don't I get an error notification (was missing before).
However, whenever I try to load a paid app, the BankStore crashes instantly.
I tried to read the whole NOGAPPS thread and realised: it only works for free apps. And I already redeemed a gift card at the Play Store to buy a paid Titanium Backup version. ****e, I'm stupid. :silly:
Still, it would be nice if it would not crash, or at least tell me it would crash when trying to load a paid app.
Also, I still can't see any active device when logging into the account on the web. Any ideas there? Is that supposed to be like this?
(Funny enough, I *can* see which apps I downloaded through BlankStore.)
arghwhymustiregister said:
also installed the maps successfully (didn't try NetworkLocation yet)
Click to expand...
Click to collapse
It seems both are not working properly for me. OSMAnd can find it's position by GPS. Offi is working, but can not find a location (GPS turned on). Also in Offi Stations, 'Acquiring location' never gets finished. The map stays blank in landscape mode. I would very much appreciate it if you would report your status here: if you can get it to work, how - and if not, what $reasons do you assume?

The permissions are not the problem. /system has to be mounted writable.
Sent from my FP1 using xda app-developers app

permissions for Offi / Maps Api access?
elchi1234 said:
The permissions are not the problem. /system has to be mounted writable.
Click to expand...
Click to collapse
Thanks for pointing that out, @elchi1234. I'm not used to work on linux-like systems, but I'm eager to learn.
However, I assume this could have something to do with permissions:
boondiordna said:
Offi is working, but can not find a location (GPS turned on). Also in Offi Stations, 'Acquiring location' never gets finished. The map stays blank in landscape mode.
Click to expand...
Click to collapse
I tried to figure out why Offi is not showing any map. It seems like it's trying to DL / access map tiles and not getting access, which sometimes even causes crashes:
Code:
W/MapsAPI ( 5201): MapTileDownloader: Problem downloading MapTile: /17/65535/65535 HTTP response: HTTP/1.1 403 Forbidden
According to the crash report, this happens with every tile the app is trying to access.
Did I mess up somehere?

Nice to hear that the Blank Store is now working for you.
Hm, that problem with Öffi sounds familiar to me - I seem to recall that I had these problems too.. since you could install those Apps it looks like your installation of the map files was succesful. I think you should try the GPS fix mentioned here. It really helps A LOT (or did you already do that..?)
Report back!

Well, the MapsAPI seems to be installed correctly. (It was never working for me, too. I use it for that apps that require it but don't really need it.)
I would guess that there is a change in the API of the webserver that MapsAPI doesn't know about.

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