Hey everyone! I think I just found the best bang for the buck tablet that has some great root development going on. I recently destroyed the display my Galaxy S4 which I had rooted and working quite well for the longest time. I only used the device to game (Clash of Clans rooted with Xmod) and mostly on Wifi. I think the Kindle would be a great replacement and probably at 1/8 of the cost of a another phone or tablet.
2 quick questions before I buy..
1. If I were to buy one today, what are the chances of it not coming with 5.1.2?
2. Once I have rooted my device, how well does Xmodgames and Clash work together? This is more of a questions for my gamers out there.. any suggestions appreciated
I just got mine today and it came with 5.0.0 on it. The moment I connected it to wifi it started to download a new patch, so I disconnected immediately. Now I'm just wondering what I should do next, but at least I still just have 5.0.0 on it
Use the SuperTool to block the OTA updates before you connect the Fire to the internet! Then you are free to root, flash new OS etc.
It all depends what you want to do with it, but if you want to install a custom rom, this is one option:
http://forum.xda-developers.com/amazon-fire/help/tip-buying-fire-powered-want-to-install-t3277552
nemof said:
I just got mine today and it came with 5.0.0 on it.
Click to expand...
Click to collapse
Where did you buy it from?
blueberry.sky said:
Where did you buy it from?
Click to expand...
Click to collapse
I bought it from Amazon. During it's initial setup I connected it to wireless and then it said it was going to update. I was worried about it updating to 5.1.2, so I actually reset the tablet before it could complete the update. Then turned the wireless off.
What I found though was that kingroot wouldn't work. So I let the first update complete once, and it updated to 5.1.1, and said it was now ready to update to 5.1.2. That's the point where I ran rootjunky's supertool and disabled OTA updates and the system update screen. This effectively killed the 5.1.2 update, even though it had already downloaded in the background and just needed me to restart the tablet. I then went ahead and installed google apps and the various other things noted in the tips and tricks thread.
ymmv, I kind of bodged my install. Widget's don't work, but I believe that may be a problem with Fire OS for which there is no easy fix
That's weird, bought mine at the start of March, from Amazon, got here with 5.1.1.
So chances are there is no 5.1.2 currently, probably they are just getting rid of old stock but maybe soon in a couple months 5.1.2 will be loaded on all of them, so better "act now".
nemof said:
I bought it from Amazon. During it's initial setup I connected it to wireless and then it said it was going to update. I was worried about it updating to 5.1.2, so I actually reset the tablet before it could complete the update. Then turned the wireless off.
What I found though was that kingroot wouldn't work. So I let the first update complete once, and it updated to 5.1.1, and said it was now ready to update to 5.1.2. That's the point where I ran rootjunky's supertool and disabled OTA updates and the system update screen. This effectively killed the 5.1.2 update, even though it had already downloaded in the background and just needed me to restart the tablet. I then went ahead and installed google apps and the various other things noted in the tips and tricks thread.
ymmv, I kind of bodged my install. Widget's don't work, but I believe that may be a problem with Fire OS for which there is no easy fix
Click to expand...
Click to collapse
if it was on 5.0.X just needed to boot into fastboot mode and boot twrp with fastboot.exe
Sent from my KFFOWI using XDA Labs
Just got my Amazon Fire tablet from Amazon.com today. It had 5.1.1 installed on it.
Related
Since Thursday morning I have been having issues with my Droid Bionic after Verizon did the OTA update to Android 4.0.4 System version 6.7.246.
The initial problem was that after the OTA installed my phone was bricked. After many attempts to bring it back and my bosses being rather unhappy that I no longer had a phone I went through the warranty/insurance and they sent me a new phone the next day. Now I of course need to root it. I have tried all the Razor's Edge based roots I could find on both a 32 and 64 bit Win 7 system with the latest drivers as found on the Motorola website. The Razor's Edge systems (ADB.exe specifically) don't seem to find my device so they don't move forward (Figured that out by copying out the individual commands from the Batch file to see where it stops). I just tried downloading and using the Motofail on these forums and after downloading it says that it won't run on my system.
Has anyone else been having these kind of issues when you updated OTA or have been trying to root? I do know when I talked to Verizon the rep had said she had already covered two calls about odd behavior after the update. I find it very funny though that I haven't had such issues when I upgraded my Nook Color to ICS.
TheWeezel said:
Since Thursday morning I have been having issues with my Droid Bionic after Verizon did the OTA update to Android 4.0.4 System version 6.7.246.
The initial problem was that after the OTA installed my phone was bricked. After many attempts to bring it back and my bosses being rather unhappy that I no longer had a phone I went through the warranty/insurance and they sent me a new phone the next day. Now I of course need to root it. I have tried all the Razor's Edge based roots I could find on both a 32 and 64 bit Win 7 system with the latest drivers as found on the Motorola website. The Razor's Edge systems (ADB.exe specifically) don't seem to find my device so they don't move forward (Figured that out by copying out the individual commands from the Batch file to see where it stops). I just tried downloading and using the Motofail on these forums and after downloading it says that it won't run on my system.
Has anyone else been having these kind of issues when you updated OTA or have been trying to root? I do know when I talked to Verizon the rep had said she had already covered two calls about odd behavior after the update. I find it very funny though that I haven't had such issues when I upgraded my Nook Color to ICS.
Click to expand...
Click to collapse
Have you tried this http://www.droidrzr.com/index.php/topic/4730-samurihls-house-of-bionic-faq/. It should work.
Sent from my Redtide Bionic
Obsidian_soul said:
Have you tried this droidrzr.com/index.php/topic/4730-samurihls-house-of-bionic-faq. It should work.
Sent from my Redtide Bionic
Click to expand...
Click to collapse
Ok I just want to make sure I am on the right page. The House of Bionic method will push out an update to 246 which already includes root access? Rereading my previous post I realize I may not have made it clear that with the replacement phone the OTA update did work so I am on 246.
I could not get Razor's Edge to work on my new laptop(W7 64bit) but Motofail worked perfectly. Have you tried it?
.::Bleh::.
PerfectlyFlawed said:
I could not get Razor's Edge to work on my new laptop(W7 64bit) but Motofail worked perfectly. Have you tried it?
.::Bleh::.
Click to expand...
Click to collapse
Not yet. I know I had issues downloading it and when I tried to run it I was informed that it wouldn't run on my computer but that was only on the 32 bit computer so I have yet to head back home and try on a 64bit. Also I am not 100% sure of a good download location, I seem to remember hitting a lot of incorrect ones including one from the developer that said it was a defunct method.
As I said for this rooting my luck has been a whole lot of bad.
I downloaded from the Motofail thread.
http://forum.xda-developers.com/showthread.php?p=22542129
Here is the link to the download
https://docs.google.com/file/d/0B26Hj6_2TMNTOXE5UTdUeEk0dGc/preview?pli=1
.::Bleh::.
This worked great for me. Had to update the moto drivers first then downloaded and ran the motofail-ics. I have been searching the forums here and other areas. Never realized how much I was spoiled with root until the ics ota took it from me! =( lol. Thank you all for the postings, comments, and feed back. It help to make re-rooting loads easier for me!¡!¡ :thumbup:
Sent from my DROID BIONIC using xda premium
Bionic after updates goes back to previous owners account
Hello, not sure if I'm posting in the correct place but I need some help. I purchased my bionic on ebay about a year ago. My service is through pageplus. After receiving updates the phone reverts back to the previous owners info and will not work for me. I then have to have it flashed, which has been done 4 times now. Last night was the most recent. Everything is working for me fine but when I look at about phone and status its still showing the previous owners phone no. and min. but when dial the program codes it shows my no and min. Can I fix this and how can I get it to stop reverting back..
lisabd said:
Hello, not sure if I'm posting in the correct place but I need some help. I purchased my bionic on ebay about a year ago. My service is through pageplus. After receiving updates the phone reverts back to the previous owners info and will not work for me. I then have to have it flashed, which has been done 4 times now. Last night was the most recent. Everything is working for me fine but when I look at about phone and status its still showing the previous owners phone no. and min. but when dial the program codes it shows my no and min. Can I fix this and how can I get it to stop reverting back..
Click to expand...
Click to collapse
I am so sorry to read that this is happening. I am not 100% sure but it sounds to me like the phone was never de-registered after it was activated with your current service. I would think that doing a system restore back to stock and then going through the motions of re-registering the phone to your account and service provider may work. The only other thing I am able to think of is that it may have been rooted to the original owner and they never un-rooted it and de-registered prior to selling it.
Hope this gives a better idea or maybe some one else whom knows more then I will respond.
Gl,
Cheers ....
So initially I was having trouble getting it to re-root with qemu, and eventually I did however get it rooted again. I have root access and everything is fine other than the fact that I can no longer open the Google play store. I have uninstalled, rebooted, reinstalled. Im getting irritated, I have followed these boards since September without needing to ask for help but also never had an issue with my kindle fire hd 7'' up until that last sabotaging that amazon decided to do. Perhaps someone with the same problem can benefit also if we can figure it out because I noticed someone with a similar issue but didn't want to hijack the thread. Thanks in advance :good:
I have had my Kindle Fire rooted and working for 3 years. Just recently I installed the updated GooglePlay Services and keeps crashing no matter what. I even tried downgrading but keeps crashing.
I haven't updated the fire OS as I blocked updates, could be that a problem? I have read around that it's the new play services but if that's the case why doesn't an old version work?
Re: Kindle Fire HD GoogleServices Crashing
Hi.
I don't have a solution exactly. But I actually had the same problem. I rooted my Kindle Fire HD a couple years ago as well and have had no issues until now. Like you I had a lot of problems with Google Services. I tried a few different tacks unsuccessfully (updating, downgrading various Google Framework files etc.).
Ultimately, one day the device crashed and prompted a Factory Recovery Screen.
Fortunately, recovery proceeded with Superuser still intact. I haven't connected device to WiFi yet. Right now I'm trying to get my PC to recognize the Fire HD again, but I'm having some trouble. I still have Kindle Fire Utility and various ADB drivers etc. but I haven't gotten it to work again (yet). I know that newer versions of the software development kits have different requirements (serial numbers). But I'm a bit hazy still and I've just picked up this project again.
Annoyingly, Control Panel shows Kindle Fire in the device list as an ADB interface, but my (outmoded?) Kindle Fire Utility doesn't show it, nor does it even show the device as a USB storage......Strangely Android File Transfer on my Mac still works.
Right now the device boots runs Apex launcher and looks like stock Android. Previously, it ran all Google products relatively seamlessly (with some hiccups now and then). I never got rid of the Kindle OS, just rooted it and had launchers sit on top. And for a good couple years Google apps ran on it (and they auto-updated too). The main OS itself, though wasn't being updated and I suspect this is the reason why current versions of Google Services couldn't function any longer.
Hopefully, I should at least be able to sideload apps again, if not get all Google Apps working again.
Good luck with your efforts!
Update: several re-installs and reboots later, ADB utilities on my PC work and I can view/mod the drive of the device. I got old versions of Google Play to work, but any attempt at using Google Play Services results in a crash. Other apps, ex. Netflix are totally fine, micro-HDMI to TV still works beautifully. So it doesn't seem like the Kindle OS needs updating, if its easier to leave it intact---I'm still on the fence about installing a new ROM. Regardless, I continue to be impressed with the quality of the hardware Amazon uses....
I used the SuperTool method to root and block OTA. My daughter loves playing Pokemon Go, and since the tablet is rooted now it won't work. I have been told installing Magisk is the best way to get around it. In order to do this I think I need a custom recovery and I need to unroot as Magisk roots when you install it. I'm just worrying that it may not be compatible with the Fire and I don't want to brick it. I am on 5.1.2 bootloader, so I guess I need to install FlashFire then try to install Magisk?
There is no tutorial on how to do this specifically for the Fire, so I'm tempted not to touch it and just tell her she is out of luck.
slickdaddy96 said:
I used the SuperTool method to root and block OTA. My daughter loves playing Pokemon Go, and since the tablet is rooted now it won't work. I have been told installing Magisk is the best way to get around it. In order to do this I think I need a custom recovery and I need to unroot as Magisk roots when you install it. I'm just worrying that it may not be compatible with the Fire and I don't want to brick it. I am on 5.1.2 bootloader, so I guess I need to install FlashFire then try to install Magisk?
There is no tutorial on how to do this specifically for the Fire, so I'm tempted not to touch it and just tell her she is out of luck.
Click to expand...
Click to collapse
I would go with your gut (just say 'no'). Magisk may or may not know how to root a 5th gen Fire and FlashFire is not a custom recovery. Initial sniff tests detect a foul odor. In addition, the device lacks a physical GPS chip which makes playing the game a challenge. You can go with 'mock' locations but that's a hassle and takes the fun out IMHO.
Davey126 said:
I would go with your gut (just say 'no'). Magisk may or may not know how to root a 5th gen Fire and FlashFire is not a custom recovery. Initial sniff tests detect a foul odor. In addition, the device lacks a physical GPS chip which makes playing the game a challenge. You can go with 'mock' locations but that's a hassle and takes the fun out IMHO.
Click to expand...
Click to collapse
The weird thing is that the app works on it and is downloadable as compatible. I didn't think it had a GPS chip, but I can't figure out how it knows she is walking, but it does around the house and around the yard while she is on wifi. That one has still baffled me, but not enough to care to find out how it is still working.
slickdaddy96 said:
The weird thing is that the app works on it and is downloadable as compatible. I didn't think it had a GPS chip, but I can't figure out how it knows she is walking, but it does around the house and around the yard while she is on wifi. That one has still baffled me, but not enough to care to find out how it is still working.
Click to expand...
Click to collapse
Google Location Services 'maps' AP (WiFi) locations and does a pretty decent job approximating current location based on signal strength. Results are even better in AP dense areas like neighborhoods, apartment complexes, etc.
I've got this nice fresh tablet ready to be rooted and it's sitting on 5.3.1.0. I've removed it's ability to connect to wi-fi to prevent it from updating, of course disabling wi-fi.
I'm concerned where the status is now on what to use and how to go about properly using it? The last time I've tried this method, I bricked my tablet. Yes, I tried rolling back a 5.3.2.0 tablet to 5.1 and it got hard bricked. So, lesson learned there as to what no to do.
I'd like to avoid the same fate with this one. I'm thinking I'd like to have CyanogenMod on it or perhaps Kingroot. Something where I don't have to tolerate Amazon's horrendous ads, it's bad appstore and it's horrible Silk browser. Anything would do, really.
I've gotten RootJunky's tool to flash the tablet for either of the options above. I know how to go about it's process, but I'd like to know what I can get specifically with 5.3.1.0.
BBM7720 said:
I've got this nice fresh tablet ready to be rooted and it's sitting on 5.3.1.0. I've removed it's ability to connect to wi-fi to prevent it from updating, of course disabling wi-fi.
I'm concerned where the status is now on what to use and how to go about properly using it? The last time I've tried this method, I bricked my tablet. Yes, I tried rolling back a 5.3.2.0 tablet to 5.1 and it got hard bricked. So, lesson learned there as to what no to do.
I'd like to avoid the same fate with this one. I'm thinking I'd like to have CyanogenMod on it or perhaps Kingroot. Something where I don't have to tolerate Amazon's horrendous ads, it's bad appstore and it's horrible Silk browser. Anything would do, really.
I've gotten RootJunky's tool to flash the tablet for either of the options above. I know how to go about it's process, but I'd like to know what I can get specifically with 5.3.1.0.
Click to expand...
Click to collapse
FireOS 5.3.1.0 is rootable which, with the proper advance preparation, permits flashing any custom ROM for this device. At present only one is actively/fully supported: Fire Nexus. CyanogenMod 12.1 (CM 12.1) has been discontinued. Keep reading through the forums to get an idea what needs to be done. Might start with the index: https://forum.xda-developers.com/amazon-fire/general/index-amazon-fire-2015-t3210485