Database Develop

Retore Kindle to factory

I have a 7" kindle fire HD. When I first got it I rooted it with QemuRoot. I wasn't too worried about doing much, I just added halo launcher and the play store. Everything was good until the launcher quit working. To make a long story short, I had lost root and got it back via Bin4ry. Once again, was lazy and just installed the launcher and went about life.
I lost root again, restored it with Bin4ry and disable updates using KFFA. The launcher works, but I can't get it to be the home button default and there is a lot of junk on there from when I had a freetime membership for my kid.
I would like to reset the device to factory and start over, what do I need to do? Looking at KFFA options 3,4 or 22 look like they would apply, I just wanted to find out what is the preferred method to accomplish this without screwing anything up.

Zuggel said:
I have a 7" kindle fire HD. When I first got it I rooted it with QemuRoot. I wasn't too worried about doing much, I just added halo launcher and the play store. Everything was good until the launcher quit working. To make a long story short, I had lost root and got it back via Bin4ry. Once again, was lazy and just installed the launcher and went about life.
I lost root again, restored it with Bin4ry and disable updates using KFFA. The launcher works, but I can't get it to be the home button default and there is a lot of junk on there from when I had a freetime membership for my kid.
I would like to reset the device to factory and start over, what do I need to do? Looking at KFFA options 3,4 or 22 look like they would apply, I just wanted to find out what is the preferred method to accomplish this without screwing anything up.
Click to expand...
Click to collapse
Either 3 or 4 will work. If you don't remove OTA updates, the Kindle will get an updated pushed onto it and your root will break every time when the Kindle updates. So make sure to remove OTA updates using KFFA as well.

LinearEquation said:
Either 3 or 4 will work. If you don't remove OTA updates, the Kindle will get an updated pushed onto it and your root will break every time when the Kindle updates. So make sure to remove OTA updates using KFFA as well.
Click to expand...
Click to collapse
So I ended up using option 4 and a factory cable, for some reason it would not boot into fast mode via regular usb cable in KFFF. When it got done rebooting, I got a message asking if I wanted to use kindle or holo launcher (which I had previously installed).
That bit confused my, i thought that it would also have been deleted during the restore process?!!? Holo launcher & locker are installed and appears fully functional. Like i said before I would like to get this back to factory and start over. Superuser is on there also, did I forget a step or is there something additional that I need to do? I do not see any other apps other than what it came with.
It did take me to the set up process like on a new kindle.

Sounds like all it did was wipe the data folder. It has to go into fastboot to restore it to stock, if it doesn't want to do it during the process in kffa you can always use a mobile terminal on the kindle itself and type
Code:
su -c "reboot bootloader"
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app

Zuggel said:
So I ended up using option 4 and a factory cable, for some reason it would not boot into fast mode via regular usb cable in KFFF. When it got done rebooting, I got a message asking if I wanted to use kindle or holo launcher (which I had previously installed).
That bit confused my, i thought that it would also have been deleted during the restore process?!!? Holo launcher & locker are installed and appears fully functional. Like i said before I would like to get this back to factory and start over. Superuser is on there also, did I forget a step or is there something additional that I need to do? I do not see any other apps other than what it came with.
It did take me to the set up process like on a new kindle.
Click to expand...
Click to collapse
Did you use KFFA with a factory cord or a fastboot? When using KFFA, it is best to use a fastboot cord. Booting it into fastboot from USB can be done but I found it did not happen as often using KFFA. You can also use this tool here http://forum.xda-developers.com/showthread.php?t=1951254 and he has a video at the bottom of this page http://androidcowboy.com/2013/06/how-to-return-kindle-fire-hd-to-stock/
You can also try your steps again and try number 3.

stunts513 said:
Sounds like all it did was wipe the data folder. It has to go into fastboot to restore it to stock, if it doesn't want to do it during the process in kffa you can always use a mobile terminal on the kindle itself and type
Code:
su -c "reboot bootloader"
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
Click to expand...
Click to collapse
It was in fastboot, I used a factory cable to do so before I started KFFA. The screen said "fastboot kindle" or something to that effect.
LinearEquation said:
Did you use KFFA with a factory cord or a fastboot? When using KFFA, it is best to use a fastboot cord. Booting it into fastboot from USB can be done but I found it did not happen as often using KFFA. You can also use this tool here http://forum.xda-developers.com/showthread.php?t=1951254 and he has a video at the bottom of this page http://androidcowboy.com/2013/06/how-to-return-kindle-fire-hd-to-stock/
You can also try your steps again and try number 3.
Click to expand...
Click to collapse
That was my thought, to try it again, I just like to get other thoughts and opinions from those who are much more knowledgeable about andoid operating systems than myself. I will try another wipe tomorrow (option 3) and see if it has the desired effect.

LinearEquation said:
Did you use KFFA with a factory cord or a fastboot? When using KFFA, it is best to use a fastboot cord. Booting it into fastboot from USB can be done but I found it did not happen as often using KFFA. You can also use this tool here http://forum.xda-developers.com/showthread.php?t=1951254 and he has a video at the bottom of this page http://androidcowboy.com/2013/06/how-to-return-kindle-fire-hd-to-stock/
You can also try your steps again and try number 3.
Click to expand...
Click to collapse
I tried option 3 twice with the same results. I am downloading KFHD and will give that a go tomorrow.

Zuggel said:
I tried option 3 twice with the same results. I am downloading KFHD and will give that a go tomorrow.
Click to expand...
Click to collapse
KFHD?

LinearEquation said:
http://forum.xda-developers.com/showthread.php?t=1951254 and he has a video at the bottom of this page http://androidcowboy.com/2013/06/how-to-return-kindle-fire-hd-to-stock/
Click to expand...
Click to collapse
LinearEquation said:
KFHD?
Click to expand...
Click to collapse
The link you gave me, that was the file name for the tool.

Zuggel said:
The link you gave me, that was the file name for the tool.
Click to expand...
Click to collapse
Oh gotcha. Yea, that's a System.img Restore Tool. Same idea as KFFA but a different method.

LinearEquation said:
KFHD?
Click to expand...
Click to collapse
Correct.

Zuggel said:
I tried option 3 twice with the same results. I am downloading KFHD and will give that a go tomorrow.
Click to expand...
Click to collapse
I tried to run the script myself and see exactly what you are talking about. I left a comment in Chris's thread. I'm sure he will give us the skinny on it.

Zuggel said:
I have a 7" kindle fire HD. When I first got it I rooted it with QemuRoot. I wasn't too worried about doing much, I just added halo launcher and the play store. Everything was good until the launcher quit working. To make a long story short, I had lost root and got it back via Bin4ry. Once again, was lazy and just installed the launcher and went about life.
Click to expand...
Click to collapse
OK, so here is how I worked it tonight. KFFA is a great utility but something hiccuped today. So here is the work around I just did.
First thing is root is needed for the restore utility to work. So root using this http://forum.xda-developers.com/showthread.php?t=2351201
Now you can restore to 7.2.3 and root (all one process) using KFHD System.img Restore. Choose the "KFHD_SRT_v1.3.0- 7.2.3 (separate option for restoring factory recovery)" download here http://forum.xda-developers.com/showthread.php?t=1951254 This will root your tablet and give you a couple Gapps and Play Store.
Then use KFFA to "Disable Amazon OTA updates." Make sure to look for a Super User request right after you click to proceed so the process suceeds.
Now you can proceed with using the installed Play Store or installing a 2nd bootloadr/custom rom
This is the process that worked for me. Make sure you give the restore tool plenty of time to work. It can be done by booting your KFHD into fastboot by using fastboot commands or a factory cable. Here is a video concerning the restore tool listed https://www.youtube.com/watch?v=k-8lTMLCGfE

LinearEquation said:
KFHD?
Click to expand...
Click to collapse
LinearEquation said:
OK, so here is how I worked it tonight. KFFA is a great utility but something hiccuped today. So here is the work around I just did.
First thing is root is needed for the restore utility to work. So root using this http://forum.xda-developers.com/showthread.php?t=2351201
Now you can restore to 7.2.3 and root (all one process) using KFHD System.img Restore. Choose the "KFHD_SRT_v1.3.0- 7.2.3 (separate option for restoring factory recovery)" download here http://forum.xda-developers.com/showthread.php?t=1951254 This will root your tablet and give you a couple Gapps and Play Store.
Then use KFFA to "Disable Amazon OTA updates." Make sure to look for a Super User request right after you click to proceed so the process suceeds.
Now you can proceed with using the installed Play Store or installing a 2nd bootloadr/custom rom
This is the process that worked for me. Make sure you give the restore tool plenty of time to work. It can be done by booting your KFHD into fastboot by using fastboot commands or a factory cable. Here is a video concerning the restore tool listed https://www.youtube.com/watch?v=k-8lTMLCGfE
Click to expand...
Click to collapse
I didn't need to root, I have a factory cable (assuming that was why I needed root to get into fastboot?!?). I tried KFHD_SRT_v1.3.5- 7.3.0 and it worked fine, except for some reason I could not turn on wireless. I am trying it again to see if it works out better for me. If not, I will try version 1.3.0

Zuggel said:
I didn't need to root, I have a factory cable (assuming that was why I needed root to get into fastboot?!?). I tried KFHD_SRT_v1.3.5- 7.3.0 and it worked fine, except for some reason I could not turn on wireless. I am trying it again to see if it works out better for me. If not, I will try version 1.3.0
Click to expand...
Click to collapse
You need root to use the restore tool, not get into fastboot, like I stated. If you are not rooted, you can not use the restore tool listed. Use the USB cord to root and the fastboot cord to restore. The fastboot cord to restore to 7.2.3 so you have a matching boot.IMG. Then when flashing a 2nd bootloader and custom rom, you will most likely not bootloop or get a red screen.
I don't mind helping but you should read the help I offer before disregarding. I never BS anyone one here. I really suggest you read some topics on this or you might end up with a paper weight.
Sent from my Kindle Fire HD 7 running 4.3 Paranoid Android using xda app-developers app
---------- Post added at 01:49 AM ---------- Previous post was at 01:46 AM ----------
LinearEquation said:
You need root to use the restore tool, not get into fastboot, like I stated. If you are not rooted, you can not use the restore tool listed. Use the USB cord to root and the fastboot cord to restore to 7.2.3 so you have a matching boot.IMG. Then when flashing a 2nd bootloader and custom rom, you will most likely not bootloop or get a red screen.
I don't mind helping but you should read the help I offer before disregarding. Or at least research some threads on here. I never BS anyone one. I really suggest you read some topics on this or you might end up with a paper weight.
Sent from my Kindle Fire HD 7 running 4.3 Paranoid Android using xda app-developers app
Click to expand...
Click to collapse
Sent from my Kindle Fire HD 7 running 4.3 Paranoid Android using xda app-developers app

LinearEquation said:
You need root to use the restore tool, not get into fastboot, like I stated. If you are not rooted, you can not use the restore tool listed. Use the USB cord to root and the fastboot cord to restore. The fastboot cord to restore to 7.2.3 so you have a matching boot.IMG. Then when flashing a 2nd bootloader and custom rom, you will most likely not bootloop or get a red screen.
I don't mind helping but you should read the help I offer before disregarding. I never BS anyone one here. I really suggest you read some topics on this or you might end up with a paper weight.
Sent from my Kindle Fire HD 7 running 4.3 Paranoid Android using xda app-developers app
---------- Post added at 01:49 AM ---------- Previous post was at 01:46 AM ----------
Sent from my Kindle Fire HD 7 running 4.3 Paranoid Android using xda app-developers app
Click to expand...
Click to collapse
When I restored using KFHD, the image was already rooted, or so the title stated. When I replied I had already done what i replied about before I read your suggested route. It's still not right, so I am following your route and hoping the kids sleep long enough for me to finish it in one sitting!!

LinearEquation said:
OK, so here is how I worked it tonight. KFFA is a great utility but something hiccuped today. So here is the work around I just did.
First thing is root is needed for the restore utility to work. So root using this http://forum.xda-developers.com/showthread.php?t=2351201
Now you can restore to 7.2.3 and root (all one process) using KFHD System.img Restore. Choose the "KFHD_SRT_v1.3.0- 7.2.3 (separate option for restoring factory recovery)" download here http://forum.xda-developers.com/showthread.php?t=1951254 This will root your tablet and give you a couple Gapps and Play Store.
Then use KFFA to "Disable Amazon OTA updates." Make sure to look for a Super User request right after you click to proceed so the process suceeds.
Now you can proceed with using the installed Play Store or installing a 2nd bootloadr/custom rom
This is the process that worked for me. Make sure you give the restore tool plenty of time to work. It can be done by booting your KFHD into fastboot by using fastboot commands or a factory cable. Here is a video concerning the restore tool listed https://www.youtube.com/watch?v=k-8lTMLCGfE
Click to expand...
Click to collapse
When I used Bin4ry, it added a second version of superuser to it (not sure if that is important or not), then I chose option 1 (Restore factory rooted with SuperSU) in KFHD. I now have a red triangle asking me to reboot or reset..

I ran option 1 with KFHD 1.3.5, back to working at least, only one version of superuser and the wireless is working. So far so good, and almost out of time right now.

Zuggel said:
When I used Bin4ry, it added a second version of superuser to it (not sure if that is important or not), then I chose option 1 (Restore factory rooted with SuperSU) in KFHD. I now have a red triangle asking me to reboot or reset..
Click to expand...
Click to collapse
You did something wrong. Your lucky you only got a red triangle and not a red screen. You need to restore again. When you are done, before exiting, clear the CASHE and data (think this is option 3 but confirm). You should already have root so use KFHD_SRT_v1.3.0- 7.2.3 (separate option for restoring factory recovery.)
Always make sure ADB and allowing apps from unknown sources is turned on on your tablet. I always turn my tablet to never sleep or an hour so it stays away and turn the brightness up on the screen when modding. Every tool you use, reconfirm the settings are the same.

LinearEquation said:
You did something wrong. Your lucky you only got a red triangle and not a red screen. You need to restore again. When you are done, before exiting, clear the CASHE and data (think this is option 3 but confirm). You should already have root so use KFHD_SRT_v1.3.0- 7.2.3 (separate option for restoring factory recovery.)
Always make sure ADB and allowing apps from unknown sources is turned on on your tablet. I always turn my tablet to never sleep or an hour so it stays away and turn the brightness up on the screen when modding. Every tool you use, reconfirm the settings are the same.
Click to expand...
Click to collapse
It seems to be working great now. Updates disable, holo launcher installed and no more freeze ups (part of why I wanted to redo it). Thank you very much LinearEquation for your help once again. Now my 2 year old can go back to watching youtube and learning educational gem like saying WTF over and over (yes, mom loved that one..of course it was my fault).
Another reason why I wanted to restore it was that I had a freetime membership for a while, a ton of apps and books were downloaded but when the membership was canceled the apps remained it just said "you don't own this" when you tried to use it...very frustrating to a young kid.

[Q] Kindle Fire HD 2013 Version Bricked - Need Help

Hey, I recently rooted my Kindle Fire HD and everything was working great, until I installed an Xposed tweak that caused my Kindle to start boot looping and then thereafter I went ahead and screwed it up even worse - by messing with various fastboot methods to get it working again. Yeah... I should have just left it as it was, I know...
I've read about how there are signature checks whenever the Kindle boots up which I'm assuming I don't have anymore. So, I'm curious if there is anyway to come back from this? From what I've read, if I had backed up the partitions, technically I should have been able to restore them - but unfortunately here we are.
I've also downloaded the latest update from Amazon 'update-kindle-11.3.1.0_user_310084920' and after converting it to a zip file, there is a 'boot.img' and a 'recovery.img' which I would assume would have the signatures already within them, but no system.img. Is there anyway for someone to create an exact backup of that file, or is that not possible right now without a second bootloader?
I'm honestly really unsure of what to do here, I've tried a myriad of different approaches and still it looks like this is a bad brick... However I do hope someone out there has a solution, I'd love to get this device working again.
Oh and what happens whenever I start it up, is that I just get the Amazon Kindle Fire Logo (Pure White), without any changes. It doesn't turn gold with the animation or anything.

Hyperiunn said:
Hey, I recently rooted my Kindle Fire HD and everything was working great, until I installed an Xposed tweak that caused my Kindle to start boot looping and then thereafter I went ahead and screwed it up even worse - by messing with various fastboot methods to get it working again. Yeah... I should have just left it as it was, I know...
I've read about how there are signature checks whenever the Kindle boots up which I'm assuming I don't have anymore. So, I'm curious if there is anyway to come back from this? From what I've read, if I had backed up the partitions, technically I should have been able to restore them - but unfortunately here we are.
I've also downloaded the latest update from Amazon 'update-kindle-11.3.1.0_user_310084920' and after converting it to a zip file, there is a 'boot.img' and a 'recovery.img' which I would assume would have the signatures already within them, but no system.img. Is there anyway for someone to create an exact backup of that file, or is that not possible right now without a second bootloader?
I'm honestly really unsure of what to do here, I've tried a myriad of different approaches and still it looks like this is a bad brick... However I do hope someone out there has a solution, I'd love to get this device working again.
Oh and what happens whenever I start it up, is that I just get the Amazon Kindle Fire Logo (Pure White), without any changes. It doesn't turn gold with the animation or anything.
Click to expand...
Click to collapse
The 2013 Kindle Fire HD is not setup for Xposed yet. There is no bootloader access yet therefore there is no way to recover yet. You have two options at this point. Wait until there is a bootloader exploit or contact Amazon for an exchange.
The only things available are root, remove OTA updates and remove lock screen ads. Even Google Play is only for window shopping at the moment.
Sent from my Nexus 7 Flo running Odex SinLess ROM 4.4.2 with ElementalX kernel using XDA Premium 4 mobile app

LinearEquation said:
The 2013 Kindle Fire HD is not setup for Xposed yet. There is no bootloader access yet therefore there is no way to recover yet. You have two options at this point. Wait until there is a bootloader exploit or contact Amazon for an exchange.
The only things available are root, remove OTA updates and remove lock screen ads. Even Google Play is only for window shopping at the moment.
Sent from my Nexus 7 Flo running Odex SinLess ROM 4.4.2 with ElementalX kernel using XDA Premium 4 mobile app
Click to expand...
Click to collapse
For anyone wondering, xposed actually works perfectly with a good number of modules, but don't install Xthemeengine, that'll cause the bootloop.

Fastboot
As long as you can boot into fastboot-mode nothing is lost. (if you can't -> buy a fastboot-cable. it is much cheaper than a new Kindle. They cost about 15$).
I used this useful tool. It just flashes the old system, boot and recovery on your Kindle. (all files are included in the downloadable zip file).
This tool was very useful for me and saved my Kindle very often (I am a real flashoholic...). Maybe there is something like this for the new 2013 KFHD too?

Gamingmayr said:
As long as you can boot into fastboot-mode nothing is lost. (if you can't -> buy a fastboot-cable. it is much cheaper than a new Kindle. They cost about 15$).
I used this useful tool. It just flashes the old system, boot and recovery on your Kindle. (all files are included in the downloadable zip file).
This tool was very useful for me and saved my Kindle very often (I am a real flashoholic...). Maybe there is something like this for the new 2013 KFHD too?
Click to expand...
Click to collapse
Nah nothing so far for the 2013 unfortunately. I don't think there's been much interest in this model as of yet.

Hyperiunn said:
Nah nothing so far for the 2013 unfortunately. I don't think there's been much interest in this model as of yet.
Click to expand...
Click to collapse
I've been interested. Unfortunately, my mother won't let me touch her new 2013 Fire HD. Still, if you can find someone who's rooted and not bricked, maybe they could backup their boot, system, and recovery .imgs for you and post them for you. And since they're already rooted, you would be too (someone correct me if I'm wrong). If I could get a temporary root or find a way to remove root later I would back them up for you.
The system restore tool for the 2012 Fire HD flashes the boot, recovery, and system partitions. Theoretically, the same tool would work, but only if you replaced the .img files with the ones for the 2013 Fire HD.

Gamingmayr said:
As long as you can boot into fastboot-mode nothing is lost. (if you can't -> buy a fastboot-cable. it is much cheaper than a new Kindle. They cost about 15$).
I used this useful tool. It just flashes the old system, boot and recovery on your Kindle. (all files are included in the downloadable zip file).
This tool was very useful for me and saved my Kindle very often (I am a real flashoholic...). Maybe there is something like this for the new 2013 KFHD too?
Click to expand...
Click to collapse
There is no confirmation that a fastboot cord even works with the 2013 model nor are the stock images available yet. The 2012 KFHD and the 2013 KFHD do not use the same images.
---------- Post added at 11:28 PM ---------- Previous post was at 11:26 PM ----------
Hyperiunn said:
For anyone wondering, xposed actually works perfectly with a good number of modules, but don't install Xthemeengine, that'll cause the bootloop.
Click to expand...
Click to collapse
It won't work on the 2013 Kindle fire HD yet though. Since that is the topic here I guess that narrows it down to this tablet not all the others don't it.

Fastboot cable works just fine with the one I have.

[Q] Kindle Fire HD - Lost Root After 7.4.6 to 7.4.8 Update - Any Advice?

Ok, so I'm a noob when it comes to this stuff, but I have managed to root my Kindle Fire HD 7" and I installed the Google play store, so I was happy thus far. Yesterday I lost root and couldn't figure out why. Today I noticed that my Kindle had done an update from 7.4.6 to 7.4.8 and I'm wondering if this is why I lost root? If so, how can I fix this to get my Kindle back into root? Like I said, I'm a noob and don't want to screw up my Kindle messing around with stuff when I don't have a clue. Any advice would be of great help, thanks in advance.
Oh yeah, I should add this information: I get this pop up from Superuser, "There is no SU binary installed and Superuser can not install it. This is a problem"

Yea when it updates it clears the system partition where the su binary is stored, you need to reroot it. Never heard of a 7.4.8 update, but if it is a new one and you can reroot it then you can just downgrade it with kindle fire first aid by sticking it into fastboot with a simple "adb reboot bootloader", think kffa will do it for you though.
Sent from my Amazon Kindle Fire HD using Tapatalk

masterndentske
stunts513 said:
Yea when it updates it clears the system partition where the su binary is stored, you need to reroot it. Never heard of a 7.4.8 update, but if it is a new one and you can reroot it then you can just downgrade it with kindle fire first aid by sticking it into fastboot with a simple "adb reboot bootloader", think kffa will do it for you though.
Sent from my Amazon Kindle Fire HD using Tapatalk
Click to expand...
Click to collapse
" Never heard of a 7.4.8 update, but if it is a new one and you can reroot it " Hmmmm, the way you worded that makes me feel like I might be stepping into uncharted territory if I try to root it again and I don't like the thought of that. I'll think about it and maybe give it a try tomorrow after I get some sleep and my head is clear. Thanks for the advice, I really appreciate it.

cautiousone said:
" Never heard of a 7.4.8 update, but if it is a new one and you can reroot it " Hmmmm, the way you worded that makes me feel like I might be stepping into uncharted territory if I try to root it again and I don't like the thought of that. I'll think about it and maybe give it a try tomorrow after I get some sleep and my head is clear. Thanks for the advice, I really appreciate it.
Click to expand...
Click to collapse
I had the same problem starting yesterday. My Kindle upgraded to 7.4.8 and any app requiring root stopped working, namely Google Play Store, SuperUser, ... I used KFFirstAide to re-root the Kindle and all is working so far.

blackeyeX2 said:
I had the same problem starting yesterday. My Kindle upgraded to 7.4.8 and any app requiring root stopped working, namely Google Play Store, SuperUser, ... I used KFFirstAide to re-root the Kindle and all is working so far.
Click to expand...
Click to collapse
:good: Awesome, thanks for passing that on to me, I'm going to give it a go and see what happens. I'll post a status update later today after I've had a chance to thoroughly test it.

:victory: Well I got it to root again and reinstalled google play with no issues to report, all went well. So is there a way to stop Amazon from updating my Kindle in the future? Now, the next task is to get a second boot loader on it, although I don't have a fastboot cable, so I'm kinda chicken, hahaha. But I'm feeling confident now, so maybe I'll give it a shot tonight. Wish me luck... A big thanks for the help, I guess I just needed some reassurance on re-rooting the thing and I'm happy.

Just make sure you downgrade the bootloader first, if you don't use the fireflash method then I recommend making sure to check the md5sum of the bootloader before downgrading it so you don't end up with a paperweight.
Sent from my Amazon Kindle Fire HD using Tapatalk

I'm having this issue also. Same update, same loss of SU + Play store.
I can't get my kindle to root like before though. It says it was successful but my fire becomes extremely laggy, no icons appear, where the navigation swipe is there are slightly darker vertical lines and the only way I've fixed it is by factory restore.
How are you rerooting???
I can't remember how I rooted in the first place, I only remember that I had massive issues getting GP store on and used this KFFA which is what I'm now using to reroot.
http://forum.xda-developers.com/showthread.php?t=2069329
Any suggestions would be massively appreciated

kindle fire hd 7.4.8
same thing happen to me so I tried getting adb to work witch it didn't that well, so I downloaded the update .bin file from amazon and edited it useing winRAR just added SuperSU to /system/app then changed a few things in kindle first aid then used a fastboot cable to upload the custom update so my kindle is running v7.4.9 witch I changed it to because it didn't work any other way. i'll make a video

dEADwEIRD said:
I'm having this issue also. Same update, same loss of SU + Play store.
I can't get my kindle to root like before though. It says it was successful but my fire becomes extremely laggy, no icons appear, where the navigation swipe is there are slightly darker vertical lines and the only way I've fixed it is by factory restore.
How are you rerooting???
I can't remember how I rooted in the first place, I only remember that I had massive issues getting GP store on and used this KFFA which is what I'm now using to reroot.
http://forum.xda-developers.com/showthread.php?t=2069329
Any suggestions would be massively appreciated
Click to expand...
Click to collapse
I just followed the same steps as I did the first time I rooted it, I used KFFA. But this time around some of the actions described didn't happen, like Superuser didn't ask for permission as it did the first go around and a few other little things, but I just took it slow and easy and it came out working fine. Also I used KFFA to install GP, it also skipped a few actions, but I just have it a little extra time to do its thing and it works perfectly. I saw a fix for the laggy screen and icons issue somewhere, I think it's in KFFA? I would have to double check that when I get home to be certain.

stunts513 said:
Just make sure you downgrade the bootloader first, if you don't use the fireflash method then I recommend making sure to check the md5sum of the bootloader before downgrading it so you don't end up with a paperweight.
Sent from my Amazon Kindle Fire HD using Tapatalk
Click to expand...
Click to collapse
Thanks for the heads up on that, I've held off on doing it until I have more time to research it. I like to feel somewhat comfortable going into it and not totally freaked out. Thanks again, you guys are great around here.

Sorted.
I rooted using The Bin4ry Method and using KFFA to bring all the other systems back on line.

is anyone having problems with ADB and fastboot on 7.4.8?
Because I tried rooting using KFFA that didn't work I kept getting errors so I tried using fastboot to flash the recovery using this code
Code:
fastboot flash recovery recovery.img
I get "device not found" or when it dose work i get "failed to flash" (something like that) but i have the adb drivers installed would there be different ones for 7.4.8? When I type
Code:
fastboot device
it finds the device it just dosn't work when I want to flash
and only half the adb commands work

You have to have it with a special parameter telling it what the kindles vendor id is so it should look like this...:
Code:
fastboot -i 0x1949 flash recovery recovery.IMG
Try that.
Sent from my Amazon Kindle Fire HD using Tapatalk

"... I used KFFirstAide to re-root the Kindle and all is working so far."
I tried using bin4ry's root, which is how I originally rooted my kindle, but it did not work.
I am pleased to say that KFFirstAide was able to restore root.
Thank you xda for pointing me in the right direction!

stunts513 said:
You have to have it with a special parameter telling it what the kindles vendor id is so it should look like this...:
Code:
fastboot -i 0x1949 flash recovery recovery.IMG
Try that.
Sent from my Amazon Kindle Fire HD using Tapatalk
Click to expand...
Click to collapse
Thank you!!! i got root access by flashing with twrp recovery witch you can get more info at
http://forum.xda-developers.com/showthread.php?t=2128848
on my other kindle i used Bin4ry root witch work but i had to turn off adb/usb debugging and turn it back on during the process because it wouldn't find the device if i didn't
you can download Bin4ry here
http://forum.xda-developers.com/showthread.php?t=1886460

gregcavaretta said:
on my other kindle i used Bin4ry root witch work but i had to turn off adb/usb debugging and turn it back on during the process because it wouldn't find the device if i didn't
Click to expand...
Click to collapse
Thank's, KFFA not recovered and Bin4ry work only after turn off adb / usb debugging
Ciao dal Max

gregcavaretta said:
Thank you!!! i got root access by flashing with twrp recovery witch i downloaded at
http://teamw.in/project/twrp2/79
on my other kindle i used Bin4ry root witch work but i had to turn off adb/usb debugging and turn it back on during the process because it wouldn't find the device if i didn't
you can download Bin4ry here
http://forum.xda-developers.com/showthread.php?t=1886460
Click to expand...
Click to collapse
wtf????? that was a twrp image for the kf1, that should have broken more than it fixed on a kfhd.

Holy ****!!! Your kindle works after flashing the recovery IMG that was for the kf1???
Sent from my Kindle Fire HD 7 running PAC-man

wire55 said:
Holy ****!!! Your kindle works after flashing the recovery IMG that was for the kf1???
Sent from my Kindle Fire HD 7 running PAC-man
Click to expand...
Click to collapse
stunts513 said:
wtf????? that was a twrp image for the kf1, that should have broken more than it fixed on a kfhd.
Click to expand...
Click to collapse
I posted the Wrong link i'm truly sorry if you messed up your kindle fire

Have the exploits been patched?

Right now the fire tablet is $35 on Amazon for black Friday. I've been following this device waiting for a sale, but some of the information I'm reading here is confusing... I'm wondering if Amazon has updated and patched the Fire tablet to block all exploits, or can TWRP and still CM be installed even on the latest versions?

TWRP needs to be manually booted from a computer using fastboot, since the boot loader is locked. But yes, the device can be rooted, and custom roms can still be installed! The unofficial cm12.1 works great!
Sent from my iPhone using Tapatalk

mrlaugh01 said:
TWRP needs to be manually booted from a computer using fastboot, since the boot loader is locked. But yes, the device can be rooted, and custom roms can still be installed! The unofficial cm12.1 works great!
Sent from my iPhone using Tapatalk
Click to expand...
Click to collapse
Thank you!

Yeah I wasn't planning on giving these out till Christmas but I may root them and flash cm 12.1 to prevent updates from Amazon blocking or patching the system.
Sent from my SM-N910T3 using Tapatalk

naruto.ninjakid said:
Yeah I wasn't planning on giving these out till Christmas but I may root them and flash cm 12.1 to prevent updates from Amazon blocking or patching the system.
Sent from my SM-N910T3 using Tapatalk
Click to expand...
Click to collapse
You don't have to worry about Amazon updates, as you don't even sign into WiFi when booting it up the first time. You just select the language, click "continue setup later", and enable adb. Then you are good to go with fast booting and flashing CM. I got one for my brother and thought about opening it and flashing CM beforehand, but it will look nicer if he opens a sealed tablet. I thought it would also be better to have him sign in to his Google account right away and see if there are any issues after flashing.

natedawg187 said:
You don't have to worry about Amazon updates, as you don't even sign into WiFi when booting it up the first time. You just select the language, click "continue setup later", and enable adb. Then you are good to go with fast booting and flashing CM. I got one for my brother and thought about opening it and flashing CM beforehand, but it will look nicer if he opens a sealed tablet. I thought it would also be better to have him sign in to his Google account right away and see if there are any issues after flashing.
Click to expand...
Click to collapse
Thanks that's good to know.
Sent from my SM-N910T3 using Tapatalk

Amazon Appstore Network Error

Quick backstory; I rooted my 5th Gen 7" Fire a loooong time ago, with I believe a version of Rootjunky's supertool. Removed auto OS updates, all that good stuff. Accordingly, I cannot access the OS info via System Updates (tapping it gives a blank screen for a moment, then goes back to the main settings screen). I have Google Play & services installed.
So, I tried today to use the Amazon Appstore, and I'm getting a "Network Unreachable" error right when the app launches. I can't use any functions of the store. I'm thinking it's maybe because the app is such a relatively old version, Amazon's network is giving it grief, but I don't know for certain.
Like I said, I can't see for sure what OS version I have, but it has to be one of the first iterations of 5.something.
If anyone has run into this, or has any suggestions to get the appstore working again, I'm all ears. I did a factory reset, both from in the OS and from the Amazon recovery (complete with wiping cache), with no luck. Thanks in advance for any help.

scooter1979 said:
Quick backstory; I rooted my 5th Gen 7" Fire a loooong time ago, with I believe a version of Rootjunky's supertool. Removed auto OS updates, all that good stuff. Accordingly, I cannot access the OS info via System Updates (tapping it gives a blank screen for a moment, then goes back to the main settings screen). I have Google Play & services installed.
So, I tried today to use the Amazon Appstore, and I'm getting a "Network Unreachable" error right when the app launches. I can't use any functions of the store. I'm thinking it's maybe because the app is such a relatively old version, Amazon's network is giving it grief, but I don't know for certain.
Like I said, I can't see for sure what OS version I have, but it has to be one of the first iterations of 5.something.
If anyone has run into this, or has any suggestions to get the appstore working again, I'm all ears. I did a factory reset, both from in the OS and from the Amazon recovery (complete with wiping cache), with no luck. Thanks in advance for any help.
Click to expand...
Click to collapse
Have you checked the clock? Sometimes, if the time is off, my store will break. Other than that, I'd recommend you download EZ File explorer, google form the most up to date amazon store apk, uninstall yours and give it a fresh install, especially if you feel out of date is the problem.
I'd also recommend you download a custom rom and flashfire and see if you can't fix that OS info problem, especially since you've already wiped all your data anyway.

elementalcobalt said:
Have you checked the clock? Sometimes, if the time is off, my store will break. Other than that, I'd recommend you download EZ File explorer, google form the most up to date amazon store apk, uninstall yours and give it a fresh install, especially if you feel out of date is the problem.
I'd also recommend you download a custom rom and flashfire and see if you can't fix that OS info problem, especially since you've already wiped all your data anyway.
Click to expand...
Click to collapse
This won't work:
- the version of Amazon's app store is different on FireOS; I don't believe it's available for download
- I did not see the OP had wiped his data; the OS info problem is related to blocking OTA updates
---------- Post added 02-12-2017 at 12:12 AM ---------- Previous post was 02-11-2017 at 11:56 PM ----------
scooter1979 said:
Quick backstory; I rooted my 5th Gen 7" Fire a loooong time ago, with I believe a version of Rootjunky's supertool. Removed auto OS updates, all that good stuff. Accordingly, I cannot access the OS info via System Updates (tapping it gives a blank screen for a moment, then goes back to the main settings screen). I have Google Play & services installed.
So, I tried today to use the Amazon Appstore, and I'm getting a "Network Unreachable" error right when the app launches. I can't use any functions of the store. I'm thinking it's maybe because the app is such a relatively old version, Amazon's network is giving it grief, but I don't know for certain.
Like I said, I can't see for sure what OS version I have, but it has to be one of the first iterations of 5.something.
If anyone has run into this, or has any suggestions to get the appstore working again, I'm all ears. I did a factory reset, both from in the OS and from the Amazon recovery (complete with wiping cache), with no luck. Thanks in advance for any help.
Click to expand...
Click to collapse
Best solution is to install a custom ROM; however you seem satisfied with FireOS.
Next best solution IMO is to reload FireOS (which includes Amazon's app store) but you will probably want to stick with version 5.0.1 if that's what is currently installed. Obvious problem is you can't determine that through normal means. Have to be careful here; if you attempt to reload 5.0.1 and your device is currently on 5.1.x or above it will brick. You would also need to reroot, reblock OTA updates, etc. In short, everything you did before. With no guarantee it will fix your original problem (although I think it will).
One way to test for 5.0.1 is to see if it will boot TWRP. However, that can be messy if you are unfamiliar with fastboot and/or have never established a connection with the device in question.
@steve8x8 - I seem to recall you wrote a tool that can query current component/system levels. Thoughts?
p.s. You could also go with FireOS 5.3.1 which is the last build that can be rooted at present. No brick risk as 5.3.1 is >= the current version of FireOS on the device.

elementalcobalt said:
Have you checked the clock? Sometimes, if the time is off, my store will break. Other than that, I'd recommend you download EZ File explorer, google form the most up to date amazon store apk, uninstall yours and give it a fresh install, especially if you feel out of date is the problem.
I'd also recommend you download a custom rom and flashfire and see if you can't fix that OS info problem, especially since you've already wiped all your data anyway.
Click to expand...
Click to collapse
It's not the clock, that's as it should be.
Davey126 said:
This won't work:
- the version of Amazon's app store is different on FireOS; I don't believe it's available for download
- I did not see the OP had wiped his data; the OS info problem is related to blocking OTA updates
---------- Post added 02-12-2017 at 12:12 AM ---------- Previous post was 02-11-2017 at 11:56 PM ----------
Best solution is to install a custom ROM; however you seem satisfied with FireOS.
Next best solution IMO is to reload FireOS (which includes Amazon's app store) but you will probably want to stick with version 5.0.1 if that's what is currently installed. Obvious problem is you can't determine that through normal means. Have to be careful here; if you attempt to reload 5.0.1 and your device is currently on 5.1.x or above it will brick. You would also need to reroot, reblock OTA updates, etc. In short, everything you did before. With no guarantee it will fix your original problem (although I think it will).
One way to test for 5.0.1 is to see if it will boot TWRP. However, that can be messy if you are unfamiliar with fastboot and/or have never established a connection with the device in question.
@steve8x8 - I seem to recall you wrote a tool that can query current component/system levels. Thoughts?
p.s. You could also go with FireOS 5.3.1 which is the last build that can be rooted at present. No brick risk as 5.3.1 is >= the current version of FireOS on the device.
Click to expand...
Click to collapse
You are correct, I am happy with the FireOS.
I've played in fastboot before, and given EXACT instructions, I can regurgitate results, but it's not my native tongue. I don't know if the appstore version is locked to the OS version, but according to Appstore Settings under the manage Amazon apps section, I'm rocking release-9.1011.5.1.39.0_2000145010, last updated 2/12/15. Any way to link that with OS version?
If no more info can be gleaned from my device, either from the appstore version or something steve8x8 may have, I may just load 5.3.1 on and run from there. Kinda rather not, but I'd kinda rather not not have appstore access.

scooter1979 said:
... I've played in fastboot before, and given EXACT instructions, I can regurgitate results, but it's not my native tongue. I don't know if the appstore version is locked to the OS version, but according to Appstore Settings under the manage Amazon apps section, I'm rocking release-9.1011.5.1.39.0_2000145010, last updated 2/12/15. Any way to link that with OS version?
If no more info can be gleaned from my device, either from the appstore version or something steve8x8 may have, I may just load 5.3.1 on and run from there. Kinda rather not, but I'd kinda rather not not have appstore access.
Click to expand...
Click to collapse
To my knowledge there is no direct correlation of appstore version to FireOS version. Obviously there's a range but we'd need a 1-1 match to draw a comfortable conclusion.
You can test TWRP bootability by following the guidance in this post. If TWRP boots you can safely sideload FireOS 5.0.1 from here using instructions in this thread (posts #1 and #2). That said, if you have no intention of every installing a custom ROM there really isn't any advantage to retaining an older bootloader. If that's the case might as well sideload FireOS 5.3.1. Be aware there is no going back if you take this step.

Davey126 said:
To my knowledge there is no direct correlation of appstore version to FireOS version. Obviously there's a range but we'd need a 1-1 match to draw a comfortable conclusion.
You can test TWRP bootability by following the guidance in this post. If TWRP boots you can safely sideload FireOS 5.0.1 from here using instructions in this thread (posts #1 and #2). That said, if you have no intention of every installing a custom ROM there really isn't any advantage to retaining an older bootloader. If that's the case might as well sideload FireOS 5.3.1. Be aware there is no going back if you take this step.
Click to expand...
Click to collapse
Ahhhh nuts. I'm getting "FAILED (remote: unknown command)" return on my Win7 machine trying to boot TWRP, and just simple USB transmission OK output on the device. Looks like I'm over 5.0.1.
Guess it's 5.3.1 for me. I'm assuming I can just follow the directions from sd_shadow's unbrick stock recovery ADB sideload thread, yes? Thanks for all of your help, I really appreciate it.

There's a guide to find bootloader version: https://forum.xda-developers.com/amazon-fire/development/identify-bootloader-version-t3424634
Sent from my Amazon Fire using XDA Labs
---------- Post added at 06:01 AM ---------- Previous post was at 05:59 AM ----------
scooter1979 said:
Ahhhh nuts. I'm getting "FAILED (remote: unknown command)" return on my Win7 machine trying to boot TWRP, and just simple USB transmission OK output on the device. Looks like I'm over 5.0.1.
Guess it's 5.3.1 for me. I'm assuming I can just follow the directions from sd_shadow's unbrick stock recovery ADB sideload thread, yes? Thanks for all of your help, I really appreciate it.
Click to expand...
Click to collapse
Just be sure that you don't accidentally update. Don't connect to WiFi until you have KingRoot, and be sure not to let the os update finish downloading. Once you connect, it will start. Some tips I found on how to avoid updates:
Davey126 said:
- use Kingroot 4.92 or lower; avoid v5.x (nearly impossible to remove)
- partial OTA update files are erased each time the device reboots
- KingRoot reboots frequently
- find a slow AP (library, coffee shop, etc) to thoddle the pace of downloads
- enable WiFi only after KingRoot starts and kill it when run completes
- force reboot device if KingRoot hangs for a prolonged period
- you may have to repeat the process multiple times
- there are trickier approaches (eg: IP/domain blocking) with variable results; the above playbook has worked well for most
- good luck
Click to expand...
Click to collapse
Sent from my Amazon Fire using XDA Labs

PorygonZRocks said:
Just be sure that you don't accidentally update. Don't connect to WiFi until you have KingRoot, and be sure not to let the os update finish downloading. Once you connect, it will start. Some tips I found on how to avoid updates:
s
Click to expand...
Click to collapse
Along with not hooking up wifi immediately, I was thinking of using rootjunky's supertool for root & update blocking, as the tool says it's now compatible with 5.3.1. Should be good enough, as long as I don't connect to a network until ALL of the supertool fun is done (I hope).

scooter1979 said:
Along with not hooking up wifi immediately, I was thinking of using rootjunky's supertool for root & update blocking, as the tool says it's now compatible with 5.3.1. Should be good enough, as long as I don't connect to a network until ALL of the supertool fun is done (I hope).
Click to expand...
Click to collapse
You need WiFi to root. That's why you need to be careful, since update starts quickly. Here's the thread the quote was from: https://forum.xda-developers.com/amazon-fire/help/dilemma-t3545062
If you can block the domains linked to in that thread, that'll help. It's not necessary, but it's a good idea.
EDIT: here's the post with them:
HughJeffner said:
Using stock 5.3.1 fresh install here are the domain names used in the update process:
softwareupdates.amazon.com
amzdigital-a.akamaihd.net
The first one is the actual update check, blocking DNS lookup of this domain effectively disabled auto-updates for me YMMV
The second domain name is where the firmware is actually downloaded from (not verified but seems probable). Note that this could change depending on how the update check is implemented.
I recommend blocking DNS resolution of softwareupdates.amazon.com if practical in your situation
Click to expand...
Click to collapse
Sent from my Amazon Fire using XDA Labs

PorygonZRocks said:
You need WiFi to root. That's why you need to be careful, since update starts quickly. Here's the thread the quote was from: https://forum.xda-developers.com/amazon-fire/help/dilemma-t3545062
If you can block the domains linked to in that thread, that'll help. It's not necessary, but it's a good idea.
Click to expand...
Click to collapse
Ohhhhh, I didn't realize Kingroot needs internet access... Besides that, I saw in the tool's changelogs that it even removes Kingroot & puts the normal supersu in the system, so I thought everything was more or less a "normal" rooting procedure. Whoops. Thank you, I'll be DNS blocking before anything.

scooter1979 said:
Ohhhhh, I didn't realize Kingroot needs internet access... Besides that, I saw in the tool's changelogs that it even removes Kingroot & puts the normal supersu in the system, so I thought everything was more or less a "normal" rooting procedure. Whoops. Thank you, I'll be DNS blocking before anything.
Click to expand...
Click to collapse
It removes KingRoot after using it to root. AFAIK, KingRoot is the only thing that can root these tablets. Personally, I'd recommend finding your bootloader version and flashing that, but it's just a personal preference, and has no practical difference unless you have 5.0.x, which you don't. I just like having oldest I can in case a downgrade method is ever found.
Also I may have an updated appstore apk from my brother's 5.3.2.1 tablet, let me check.
EDIT: Nope, I don't. I do, however, have an (old) apk from the Amazon website. See if installing this version helps. Just out of curiosity, could you attach the apk from your current appstore? I'm wondering if it will install on Fire Nexus. The UI looks much better than the version I have downloaded.
Sent from my Amazon Fire using XDA Labs

PorygonZRocks said:
Just out of curiosity, could you attach the apk from your current appstore? I'm wondering if it will install on Fire Nexus. The UI looks much better than the version I have downloaded.
Sent from my Amazon Fire using XDA Labs
Click to expand...
Click to collapse
I'll be happy to if you give me the path, or even the full name of the apk so I can search via root explorer.

scooter1979 said:
I'll be happy to if you give me the path.
Click to expand...
Click to collapse
If you have a file manager, search /system/app and /system/priv-app for com.amazon. venezia. Or, use an app like titanium backup to back it up.
It's taking forever to upload the apk I'm using, so here's the link if you want to test if it works: https://www.amazon.com/appstore_android_app
If not, I think you will need to reflash, unfortunately.
Sent from my Amazon Fire using XDA Labs

PorygonZRocks said:
There's a guide to find bootloader version: https://forum.xda-developers.com/amazon-fire/development/identify-bootloader-version-t3424634
Click to expand...
Click to collapse
Used this method, I'm on 5.1.1 (5.4.1_112720 5.1.1). Dagnabbit, missed it by that much.

scooter1979 said:
Used this method, I'm on 5.1.1 (5.4.1_112720 5.1.1). Dagnabbit, missed it by that much.
Click to expand...
Click to collapse
Then I'd recommend flashing 5.1.1. Like I said, if a downgrade method is found, it will probably be for older versions. Plus it's harder to brick, since only one or two versions are below it.
Sent from my Amazon Fire using XDA Labs

PorygonZRocks said:
It's taking forever to upload the apk I'm using, so here's the link if you want to test if it works: https://www.amazon.com/appstore_android_app
If not, I think you will need to reflash, unfortunately.
Sent from my Amazon Fire using XDA Labs
Click to expand...
Click to collapse
No go. Got a "Application Not Installed" error.
PorygonZRocks said:
Then I'd recommend flashing 5.1.1. Like I said, if a downgrade method is found, it will probably be for older versions. Plus it's harder to brick, since only one or two versions are below it.
Sent from my Amazon Fire using XDA Labs
Click to expand...
Click to collapse
The thing there is, if the issue is indeed related to the age of the appstore, which doesn't look like it has been updated since the OS was, sideloading the same version would put me in the same boat I'm in now. If I drop 5.3.1 on there, that should fix me, assuming the age of the store is the underlying issue. Unless there's something I'm missing.

Ok, my venezia is attached.

scooter1979 said:
No go. Got a "Application Not Installed" error.
The thing there is, if the issue is indeed related to the age of the appstore, which doesn't look like it has been updated since the OS was, sideloading the same version would put me in the same boat I'm in now. If I drop 5.3.1 on there, that should fix me, assuming the age of the store is the underlying issue. Unless there's something I'm missing.
Click to expand...
Click to collapse
A while back, I found a tutorial on how to upgrade system, but keep bootloader the same. Let me look...
Also, if it isn't the age of the app store, it has no effect. You could also try Amazon Underground app. It has a different package name, so it will install alongside the Appstore you have. This way, you can see if it has to do with the store or if it's just not working.
EDIT: Having trouble finding the link. I think what it was is you can download an update file, rename it from *.bin to *.zip, extract system.img, put it on the device, flash it, root, and disable ota immediately. I'll keep looking.
Sent from my Amazon Fire using XDA Labs

Umm, you guys?...
Ya wanna hear something wacky? Just for the fart of it, I ran the apk I just uploaded on my own device, and, um, the store works now. Zero problems. Connects just fine.
Now don't I feel like a horse's patoot?
Well, if nothing else, I learned what DNS to block if I upgrade to 5.3.1, how to check my bootloader via hex editor, and to rely on the kindness of strangers to fall bassackwards into an easy solution. Yeesh.

scooter1979 said:
Ya wanna hear something wacky? Just for the fart of it, I ran the apk I just uploaded on my own device, and, um, the store works now. Zero problems. Connects just fine.
Now don't I feel like a horse's patoot?
Well, if nothing else, I learned what DNS to block if I upgrade to 5.3.1, how to check my bootloader via hex editor, and to rely on the kindness of strangers to fall bassackwards into an easy solution. Yeesh.
Click to expand...
Click to collapse
Oh. Well, I found the thread, if you want. It gives instructions for FlashFire as well.
https://forum.xda-developers.com/amazon-fire/general/howto-install-fireos-5-1-1-root-gapps-t3265594
Sent from my Amazon Fire using XDA Labs
---------- Post added at 07:37 AM ---------- Previous post was at 07:32 AM ----------
scooter1979 said:
Ok, my venezia is attached.
Click to expand...
Click to collapse
Was there a .odex in the folder, and/or a lib folder? If so, could you also upload that? If not, then it appears it will not work. Shame. Thanks for the apk.
Sent from my Amazon Fire using XDA Labs