Ok, I have a friend who won a Fire 7 running FireOS 5.4.0.1 from a raffle and wanted a bit less Amazon and a bit more Google, so through reading various threads, the following is the best I could do for him:
1. Download and Install Amazon Kindle/Fire drivers from Amazon Dev site: https://s3.amazonaws.com/android-sdk-manager/redist/kindle_fire_usb_driver.zip
2. Download Fire 7th Generation OS 5.4.0.0 from https://fireos-tablet-src.s3.amazon...Uqo/update-kindle-55.5.7.9_user_579225620.bin
3. Download Updated Fire Utility (includes ADB + other tools): https://forum.xda-developers.com/amazon-fire/general/amazon-fire-utility-tool-bloat-removal-t3641151
3. Boot into recovery (Volume Down + Power at the same time), then select update over ADB with volume + enter
4. Using Fire Utility adb, sideload 5.4.0.0 using the command "adb sideload update-kindle-55.5.7.9_user_579225620.bin"
5. Use Updated Fire Utility to Remove Amazon OTA, Remove Lockscreen ads, Remove Preloaded apps, and Install Google Services.
6. Optionally, also use Updated Fire Utility to Switch the Default Launcher to Nova Launcher.
Hopefully this will help someone new.
thanks, it will... but can I ask why you need to downgrade to 5.4.0.0 from 5.4.0.1 and isnt the Fire 7 on 5.6.0.0 now? Not got one but curious to know what I could do with one if I did get one...
EDIT: I see, the Fire Utility (debloat etc) only works on 5.4.0.0 ... and there is ONE report we can downgrade from 5.6.0.0 (not seen 5.6.0.1 report)
Methanoid said:
thanks, it will... but can I ask why you need to downgrade to 5.4.0.0 from 5.4.0.1 and isnt the Fire 7 on 5.6.0.0 now? Not got one but curious to know what I could do with one if I did get one...
EDIT: I see, the Fire Utility (debloat etc) only works on 5.4.0.0 ... and there is ONE report we can downgrade from 5.6.0.0 (not seen 5.6.0.1 report)
Click to expand...
Click to collapse
Typically, the earlier you can roll a device back to, the better chance of someone finding a vulnerability before it's patched by the developer. I wouldn't get your hopes up, for someone finding that vulnerability in 5.4.0.0 and up, but ya never know.
I just received my Fire 7 shipped with 5.4.0.0 in an orange box.
To do the first start with WLAN I put my mobile into Tethering with GSM only. Connected with the Phone via WLAN the login worked and I switched off the Tethering before the update was loaded and restarted the Fire -> My device is still on 5.4.0.0
May be this works for others as well. I now will try to run the top 5 and 6.
I'm wondering whether I can avoid a later update to a current version.
Is this for the HD8 (8" screen)? I just got it, trying to do it right BEFORE letting it connect to wifi... so dont even know my OS version.
blueblur1986 said:
Ok, I have a friend who won a Fire 7 running FireOS 5.4.0.1 from a raffle and wanted a bit less Amazon and a bit more Google, so through reading various threads, the following is the best I could do for him:
1. Download and Install Amazon Kindle/Fire drivers from Amazon Dev site: https://s3.amazonaws.com/android-sdk-manager/redist/kindle_fire_usb_driver.zip
2. Download Fire 7th Generation OS 5.4.0.0 from https://fireos-tablet-src.s3.amazon...Uqo/update-kindle-55.5.7.9_user_579225620.bin
3. Download Updated Fire Utility (includes ADB + other tools): https://forum.xda-developers.com/amazon-fire/general/amazon-fire-utility-tool-bloat-removal-t3641151
3. Boot into recovery (Volume Down + Power at the same time), then select update over ADB with volume + enter
4. Using Fire Utility adb, sideload 5.4.0.0 using the command "adb sideload update-kindle-55.5.7.9_user_579225620.bin"
5. Use Updated Fire Utility to Remove Amazon OTA, Remove Lockscreen ads, Remove Preloaded apps, and Install Google Services.
6. Optionally, also use Updated Fire Utility to Switch the Default Launcher to Nova Launcher.
Hopefully this will help someone new.
Click to expand...
Click to collapse
Just to confirm, I've just done this on a 5.6.0.1 7th gen Fire (UK amazon bought) with no issues.
I'd already installed the google parts & linked my google account, & switched to Nova using Hijack, all which stayed after the downgrade (I didnt factory reset first). I did switch the internet access off on my router when I rebooted after the adb sideload downgrade step just in case it found an upgrade before I got the Fire Utility Tool connected to switch off OTA updates using that, which may be worth doing in all cases.
My Fire is now probably close to twice as fast as before now, staggering improvement.
I get unknown device KFAUWI when I connect a Fire 7 7th gen to a pc in recovery mode. ADB does not list the device. I also get unknown device MT65xx preloader when I connect in normal mode but is able to connect through adb.
Confirmed to work on US Fire 7 (7th-gen) w/5.6.0.0 as well!
FoxForceFive said:
Just to confirm, I've just done this on a 5.6.0.1 7th gen Fire (UK amazon bought) with no issues.
I'd already installed the google parts & linked my google account, & switched to Nova using Hijack, all which stayed after the downgrade (I didnt factory reset first). I did switch the internet access off on my router when I rebooted after the adb sideload downgrade step just in case it found an upgrade before I got the Fire Utility Tool connected to switch off OTA updates using that, which may be worth doing in all cases.
My Fire is now probably close to twice as fast as before now, staggering improvement.
Click to expand...
Click to collapse
ADDITIONAL USE CASE/CONFIRMATION: Just did this on a 5.6.0.0 7th-gen Fire 7 (US).
My only issue was that adb didn't "see" the device when it was in recovery mode (i.e. just before the adb sideload). The device self-identified as KFAUWI, and Windows 7 couldn't find a device driver for that ID. I went into Device Manager and manually applied the "Android Composite ADB Device" driver, and all was well from there on out.
Yes, the device seems almost twice as fast.
Many thanks!
---------- Post added at 04:47 PM ---------- Previous post was at 04:44 PM ----------
digicube123 said:
I get unknown device KFAUWI when I connect a Fire 7 7th gen to a pc in recovery mode. ADB does not list the device. I also get unknown device MT65xx preloader when I connect in normal mode but is able to connect through adb.
Click to expand...
Click to collapse
I got hit by this as well.
If you're running Windows, you should be able to open Device Manager (with the device connected in recovery mode) and find the KFAUWI device - you can then manually apply the "Android Composite ADB Interface" driver.
Once I did this, I was able to follow the remaining instructions with no problems. (My device is a US Fire 7, 7th-gen, was running 5.6.0.0)
I was able to remove the ads for free, so I guess I no longer need to do this since this is not a jailbreak.
digicube123 said:
I was able to remove the ads for free, so I guess I no longer need to do this since this is not a jailbreak.
Click to expand...
Click to collapse
There's no need to to do it, but it dramatically improves the performance.
Gmail and Kindle Books app
Can anyone who has downgraded and debloated confirm that:
1) Can you reinstall the Kindle Book reader app from Google Play and get it to work?
Currently, on 5.6.0.0, if you let Google Play update the Amazon Kindle Book app, it quits working:
https://forum.xda-developers.com/hd8-hd10/general/kindle-book-reader-force-closes-t3705821
2) Can you get Google Gmail (or the Google Inbox app) to work on it? Currently those apps fail on 5.6.0.0 (maybe due to Amazon blocking them vs not enough permissions):
https://forum.xda-developers.com/hd8-hd10/help/google-mail-app-crashes-time-update-t3594701
Thanks!
Google Fire 7" gen7
blueblur1986 said:
Ok, I have a friend who won a Fire 7 running FireOS 5.4.0.1 from a raffle and wanted a bit less Amazon and a bit more Google, so through reading various threads, the following is the best I could do for him:
1. Download and Install Amazon Kindle/Fire drivers from Amazon Dev site: https://s3.amazonaws.com/android-sdk-manager/redist/kindle_fire_usb_driver.zip
2. Download Fire 7th Generation OS 5.4.0.0 from https://fireos-tablet-src.s3.amazon...Uqo/update-kindle-55.5.7.9_user_579225620.bin
3. Download Updated Fire Utility (includes ADB + other tools): https://forum.xda-developers.com/amazon-fire/general/amazon-fire-utility-tool-bloat-removal-t3641151
3. Boot into recovery (Volume Down + Power at the same time), then select update over ADB with volume + enter
4. Using Fire Utility adb, sideload 5.4.0.0 using the command "adb sideload update-kindle-55.5.7.9_user_579225620.bin"
5. Use Updated Fire Utility to Remove Amazon OTA, Remove Lockscreen ads, Remove Preloaded apps, and Install Google Services.
6. Optionally, also use Updated Fire Utility to Switch the Default Launcher to Nova Launcher.
Hopefully this will help someone new.
Click to expand...
Click to collapse
Thanks to you I now have a great Google Fire 7" gen7 !!! :good: :good:
wcarlson40 said:
Can anyone who has downgraded and debloated confirm that:
1) Can you reinstall the Kindle Book reader app from Google Play and get it to work?
Currently, on 5.6.0.0, if you let Google Play update the Amazon Kindle Book app, it quits working:
https://forum.xda-developers.com/hd8-hd10/general/kindle-book-reader-force-closes-t3705821
2) Can you get Google Gmail (or the Google Inbox app) to work on it? Currently those apps fail on 5.6.0.0 (maybe due to Amazon blocking them vs not enough permissions):
https://forum.xda-developers.com/hd8-hd10/help/google-mail-app-crashes-time-update-t3594701
Thanks!
Click to expand...
Click to collapse
Th kindle app is still there, I found it listed on es file Explorer but it on start, just hangs on 'syncing account'.
I'm sure there'd be a way to fix this (& the alexa app which also won't start at all), but I don't know it.
Gmail works fine once you manage to get it stay open long enough to get settings & disable 'auto download images in emails'.
The kindle & alexa app not working are annoying me, but this device was almost unusable before I debloated it so I'll live without them if I need to.
FoxForceFive said:
Th kindle app is still there, I found it listed on es file Explorer but it on start, just hangs on 'syncing account'.
I'm sure there'd be a way to fix this (& the alexa app which also won't start at all), but I don't know it.
Gmail works fine once you manage to get it stay open long enough to get settings & disable 'auto download images in emails'.
The kindle & alexa app not working are annoying me, but this device was almost unusable before I debloated it so I'll live without them if I need to.
Click to expand...
Click to collapse
Both issues are likely a consequence of over aggressive "debloating". The processes doesn't actually uninstall apps/services; it neutralizes them while leaving the component installed. That effectively blocks any future updates/replacements regardless of source.
The solution is a factory reset followed by less aggressive debloating that leaves the Alexa and Kindle apps (plus any supporting services) alone.
wcarlson40 said:
Can anyone who has downgraded and debloated confirm that:
1) Can you reinstall the Kindle Book reader app from Google Play and get it to work?
Currently, on 5.6.0.0, if you let Google Play update the Amazon Kindle Book app, it quits working:
https://forum.xda-developers.com/hd8-hd10/general/kindle-book-reader-force-closes-t3705821
2) Can you get Google Gmail (or the Google Inbox app) to work on it? Currently those apps fail on 5.6.0.0 (maybe due to Amazon blocking them vs not enough permissions):
https://forum.xda-developers.com/hd8-hd10/help/google-mail-app-crashes-time-update-t3594701
Thanks!
Click to expand...
Click to collapse
I edited the .bat file option 3 to the attached image. It allows Kindle, amazon video, magazines(news stand) to work and doesn't debloat those. In case you wanted a slightly different option. Just right click the bat file and select edit.
Need some help please....
I am trying to run the utility on my Fire 7 Gen 7.
I was able to get the software rolled back to 5.4.0 successfully.
When I try to run anything in the utility, I get an error that "The system cannot find the path specified".
I saw the other posts regarding the driver and updating it.
I have tried several drivers since this did not work.
I deleted them all, then reinstalled the drivers in the link above.
I still get the same error.
Any suggestions?
I am fairly new to the Android world (I'm an iOS guy but have done plenty of programming and am used to working on command prompts, etc.).
I have searched and spent several hours on this now, so it's time to wave the white flag and ask for help.
Thanks!
Edit the batch file to put your path in. I did that. There are many ways to fix that. Or run from DOS prompt? Dunno all. Edit worked for me.
Sent from my Redmi Note 4 using Tapatalk
FoxForceFive said:
Just to confirm, I've just done this on a 5.6.0.1 7th gen Fire (UK amazon bought) with no issues.
I'd already installed the google parts & linked my google account, & switched to Nova using Hijack, all which stayed after the downgrade (I didnt factory reset first). I did switch the internet access off on my router when I rebooted after the adb sideload downgrade step just in case it found an upgrade before I got the Fire Utility Tool connected to switch off OTA updates using that, which may be worth doing in all cases.
My Fire is now probably close to twice as fast as before now, staggering improvement.
Click to expand...
Click to collapse
On the forum link it says it's patched. Did you just use ADB on the 5.6 and ran it anyway and it worked? Trying to save some hassle from downgrading. Thanks.
MrDarkness96 said:
On the forum link it says it's patched. Did you just use ADB on the 5.6 and ran it anyway and it worked? Trying to save some hassle from downgrading. Thanks.
Click to expand...
Click to collapse
Unless Amazon reverted changes introduced in FireOS 5.4.0.1 the underlying command(s) used by the script to 'disable' system apps no longer work. To date I have only seen one claim of success on FireOS 5.6.0.1. The poster may have been referencing unprotected apps which would still be removed.
Installed it today successfully, thank you! Works like a charm
Related
I bought my KF a week ago, on the basis that I would be able to root it seeing the variety of threads of successful roots. I bought the Non-HD 2nd Gen. My issue is that whilst my computer is able to recognise the Kindle Fire, ADB devices show nothing connected (Yes, the KF is in debug mode in Settings). I have installed the correct ADB drivers countless times, I have even tried to do it on 3 different computers, and none of them are able to recognise the KF in ADB. (BTW, I have been doing the QemuRoot method.)
I was wondering if you are able to post any suggestions? I have tried it on Windows 7 32bit and Windows XP 32bit. Thank you.
According to the Amazon ADB Guide...
Windows users only: If you previously connected your device to your computer without first enabling ADB, you will need to force a re-installation of the driver. See the Known Issues section for instructions on how to remove and re-install the device driver.
Click to expand...
Click to collapse
This was my initial issue.
So I did the uninstall according to their steps.. then enabled ADB on the KF.
Then plugged it back in and it shows KF as an unknown device.
Then I got the Kindle Fire HD 8.9 drivers from the Android SDK and install them. Now my KF is seen by ADB.
I've attached a link to the drivers
http://www.4shared.com/zip/rCjyzqfy/Kindle_Fire_HD_89_ADB_drivers.html
Thanks
This was my initial issue.
So I did the uninstall according to their steps.. then enabled ADB on the KF.
Then plugged it back in and it shows KF as an unknown device.
Then I got the Kindle Fire HD 8.9 drivers from the Android SDK and install them. Now my KF is seen by ADB.
Click to expand...
Click to collapse
Thanks for the link to the Amazon page. I did uninstall the drivers the way Amazon reccommends, and install the 8.9 drivers, that didn't work. So I downloaded the android SDK, and used the Kindle drivers which came alond with the SDK, and that finally worked. The odd thing is that ADB now recognises my device as ADB, but device manager doesn't, but that's not a problem, at least now I'm rooted on 10.2.1. (Wifi is off on my Kindle, so I do not get an OTA update to 10.2.3)
Since you still have 10.2.1 can you pull some system images for us who have 10.2.3 and lost root?
Sent from my Galaxy Nexus using xda app-developers app
Since you still have 10.2.1 can you pull some system images for us who have 10.2.3 and lost root?
Click to expand...
Click to collapse
Yes, I could do that. I'd need detailed explanation on how to do it though, as I'm not experienced when it comes to Android.
I sent you a pm. If you have root and adb it should be straight forward.
Sent from my Galaxy Nexus using xda app-developers app
Hello everyone,
It appears I somehow lost root access on my Kindle Fire HD after it ran out of power, and I had to charge and turn it on again like a reboot. I don't mind re-rooting if it'll fix the problem, but I don't want to have to do this every time I forget to charge my Kindle Fire HD. Is there some way to avoid this kind of situation altogether? Would installing a custom ROM guarantee this won't happen again?
Or, maybe I didn't root it right the first time? This was the guide I followed to root my Kindle Fire HD the first time:
http://forum.xda-developers.com/showthread.php?t=2069117
More info, maybe it'll help:
I have rooted my Kindle Fire HD about 4 months ago, and I have put in the following root-required things: I have added Google Play app store, Gmail, Go Launcher EX. I have disabled the Amazon ad lock-screen with No Lock, and I use a custom-background lock-screen with Go Locker.
Last weekend, I left my Kindle Fire HD unused for a long time, and its battery ran out completely. Now, as I have charged it and opened it (essentially rebooted it), I find these conflicting results:
- The Amazon ad lock-screen appeared. (No Lock failed.)
- Then, my custom lock-screen appeared. (Go Locker still kinda works? So I try to run Go Locker from Apps listing, but it just tells me to download Go Launcher EX.)
EDIT: Manually rebooted again, now my custom lock-screen doesn't appear at all.
- Then, the the Kindle Fire HD Default launcher appeared! Ughh!
- I tried to manually open Go Launcher EX, but it doesn't appear in the Apps listing under the Kindle Fire HD Default launcher.
- Gmail doesn't work. It closes instantly.
- I still have the "Superuser" app under Apps listing.
- According to Root Check Basic (installed back when I first rooted): "Sorry! This device does not have proper root access."
- Using ES File Explorer, I navigate to /system/xbin/, and I do not see a "su" file there.
Amazon issued a new update (7.3.0) to their Kindle Fire's. I think your kindle was automatically updated to 7.3.0, and, therefore, you lost root. Just check the version of your Kindle software. If that was the problem, you can disable update services on your kindle for future times.
ursus101 said:
Amazon issued a new update (7.3.0) to their Kindle Fire's. I think your kindle was automatically updated to 7.3.0, and, therefore, you lost root. Just check the version of your Kindle software. If that was the problem, you can disable update services on your kindle for future times.
Click to expand...
Click to collapse
Ahhh, it did get updated it version 7.3.0. But when I rooted several months ago, I also turned off the OTA updates, following this guide:
http://forum.xda-developers.com/showthread.php?t=2086450
So, was the above guide incorrect? Or do I need to do something else to make sure I don't get any more system updates that would mess up a rooted Kindle Fire HD?
Lvmobs said:
Ahhh, it did get updated it version 7.3.0. But when I rooted several months ago, I also turned off the OTA updates, following this guide:
http://forum.xda-developers.com/showthread.php?t=2086450
So, was the above guide incorrect? Or do I need to do something else to make sure I don't get any more system updates that would mess up a rooted Kindle Fire HD?
Click to expand...
Click to collapse
I have the same problem with 7.3.0. I have turned of OTA but can't get it rooted. I get a error "can't find file su".
Lvmobs said:
Ahhh, it did get updated it version 7.3.0. But when I rooted several months ago, I also turned off the OTA updates, following this guide:
http://forum.xda-developers.com/showthread.php?t=2086450
So, was the above guide incorrect? Or do I need to do something else to make sure I don't get any more system updates that would mess up a rooted Kindle Fire HD?
Click to expand...
Click to collapse
I have never disabled the OTA updates, actually. That's how I lost my root after the recent 7.3.0 update Re-rooting 7.3.0 was so easy so I did not bother to do this even after I lost root. Maybe that will change in the future.
---------- Post added at 09:23 PM ---------- Previous post was at 09:19 PM ----------
fldennis said:
I have the same problem with 7.3.0. I have turned of OTA but can't get it rooted. I get a error "can't find file su".
Click to expand...
Click to collapse
I used these instructions. I did not do steps 5-7 as it was mentioned here.
Hi guys, same problem here. Is there anything I can do now? Can I root the 7.3.0? Thanks.
hi I have just followed the method to root my kindle fire hd running 7.3.0. i followed the manual guide.
i have also just installed vending, gplay and phonesky. Play is working fine. Also moved the marketintentproxy to the sdcard from system/app.
Here are my issues:
1. How to i disable OTA updates that amazon push out? Guide says to "open Kindle Fire First Aide - Select Option 14 to Disable OTA" cant find this?!?! maybe me.. long day..
2. When I rooted, I didn't restore my kindle to factory settings so I am still left with the apps I downloaded from amazon. Will these be ok to use still? Assume I won't gt updates for them?
3.During the rooting process I chose to restore my kindle but didn't enter the encryption passsword above. Does this matter?
Last thing is to do with ROMs. I have only ever rooted android handsets that requires booting into recovery and you can then flash a rom. Is the kindle completely different to this an the only was you replace amazon's awful interface is by installing and using Go Launcher?
Also, is this the latest link to get flash on a browser such as dolphin?
https://dl.dropbox.com/u/54456659/fe...ndroid-arm.apk
Thanks in advance!
I used the Kindle Fire Aid utility and it appeared to have worked fine. Which Binary V # do you have downloaded? It is definitely number 14.
Hi,
Brand new to this site so no idea what I'm doing but I'll explain my problem, and I am a bit of a n00b when it comes to technical speak so bear with me!
Rooted my Kindle Fire HD 7" to get the Playstore and to disable the ads
Working well, but then I decided to get rid of automatic updates as whenever one came along, all my hard work was erased
Now I feel my Kindle is running slowly and I want to un-root all the work I did, and get it back to the way it was
I have performed a factory reset (probably a massive mistake!) and attempted to un-root it. But whenever I go on my Bin4ry program, and click to unroot, it says "Error: Device not found"
It comes up when I go into My Computer, and I have installed all necessary drivers, and enabled ADB...
I have tried to install the latest update for the Kindle Fire HD from the Amazon site as some people have said that worked, but I assume because I disabled automatic updates, it didn't work.
I am using Windows 7
I have a Kindle Fire HD 7"
So how can I unroot it? Please help me!
hana7x said:
Hi,
Brand new to this site so no idea what I'm doing but I'll explain my problem, and I am a bit of a n00b when it comes to technical speak so bear with me!
Rooted my Kindle Fire HD 7" to get the Playstore and to disable the ads
Working well, but then I decided to get rid of automatic updates as whenever one came along, all my hard work was erased
Now I feel my Kindle is running slowly and I want to un-root all the work I did, and get it back to the way it was
I have performed a factory reset (probably a massive mistake!) and attempted to un-root it. But whenever I go on my Bin4ry program, and click to unroot, it says "Error: Device not found"
It comes up when I go into My Computer, and I have installed all necessary drivers, and enabled ADB...
I have tried to install the latest update for the Kindle Fire HD from the Amazon site as some people have said that worked, but I assume because I disabled automatic updates, it didn't work.
I am using Windows 7
I have a Kindle Fire HD 7"
So how can I unroot it? Please help me!
Click to expand...
Click to collapse
Use KFFA http://forum.xda-developers.com/showthread.php?t=2096888 You can do about anything from that tool. Just don't try to install TWRP or 2nd bootloader from there.
Try this dude
https://www.youtube.com/watch?v=k-8lTMLCGfE&feature=youtube_gdata_player
Sent from my SAMSUNG-SGH-T989 using Tapatalk 2
Try this...
hana7x said:
Hi,
Brand new to this site so no idea what I'm doing but I'll explain my problem, and I am a bit of a n00b when it comes to technical speak so bear with me!
Rooted my Kindle Fire HD 7" to get the Playstore and to disable the ads
Working well, but then I decided to get rid of automatic updates as whenever one came along, all my hard work was erased
Now I feel my Kindle is running slowly and I want to un-root all the work I did, and get it back to the way it was
I have performed a factory reset (probably a massive mistake!) and attempted to un-root it. But whenever I go on my Bin4ry program, and click to unroot, it says "Error: Device not found"
It comes up when I go into My Computer, and I have installed all necessary drivers, and enabled ADB...
I have tried to install the latest update for the Kindle Fire HD from the Amazon site as some people have said that worked, but I assume because I disabled automatic updates, it didn't work.
I am using Windows 7
I have a Kindle Fire HD 7"
So how can I unroot it? Please help me!
Click to expand...
Click to collapse
Many Superuser apps include the 'unroot' function in their settings. If the one you installed doesn't have the setting, just install supersu or CWM's Superuser app from the market, boot it up, let it take over the su and then use that app to unroot. (Choose "Install", Do Not Choose "Recovery Install"! ;p)
The fact your Kindle Fire isn't recognized by your bin4ry tool is maybe because of your factory reset resetting the Debug over USB setting in your settings. Re-enabling that will probably make it visible again to Bin4ry, since Bin4ry uses ADB (Android Debugging Bridge).
Grtz,
~ Nephatiu
found this old kindle recently, Kindle Fire HD 7 2nd Gen, and i remember I had previously done some work with rooting and flashing but I'm not sure what I had done with it. I cant access the bootloader via buttons on startup so I may have broken something but it boots up and can browse the web and download apps from the amazon app store. I seem to have attemted to get the play store but either failed or it stopped working over time.
whats the best way to move forward with updating it? can I just flash a new rom?