I've had my Kindle Fire for some time now and used it quite as bit stock.
I just recently rooted it for the second time and enjoying the heck out of the freedom it gives you.
When my KF was stock, I never, ever go to an OTA update for my KF. I always had to got to the Amazon site and download the updates and then install them.
Is this normal or something unusual? Also, if it's not normal, then is my rooted KF going to get the new 6.3 OTA sooner or later?
If you hit the 'Sync' button on the quick settings bar on the stock ROM, it forces the OTA update to download and install.
Sent from my Kindle Fire using Tapatalk
Related
Hi if we freeze the OTA Silent Install will it stop the ora did anyone try?
Sent from my Kindle Fire using xda premium
Proven to not work
krelvinaz said:
Proven to not work
Click to expand...
Click to collapse
How can it not work if it freezes or if we remove the file?
Sent from my Kindle Fire using xda premium
You can remove the file, change the file, Freeze it, remove it's permissions whatever you want, but it will NOT stop an OTA update because the process that does the update creates a new one when it it needs it.
Proven Fail!
ref:
http://forum.xda-developers.com/showthread.php?t=1401073
samomamo said:
How can it not work if it freezes or if we remove the file?
Sent from my Kindle Fire using xda premium
Click to expand...
Click to collapse
Because that app is only a tool used by the app in charge of the whole upgrade process and it appears to get reinstalled from scratch during that process if it has been moved or removed
Thank you guy's for the info.
Sent from my Kindle Fire using xda premium
What if we are not registered to Amazons account? Becouse wen I wanted to get the ota I registered ans clicked on sync to get the ota. Maybe the registration has something to do with it?
Sent from my Kindle Fire using xda premium
just root ur phone and install cm7 or try droid wall that may block it but we dont have a update to check
I bought mine when it was on 6.0.0 and installed Root Uninstaller, backed up otasilentupdate.apk and then deleted it. After that no more updates. I guess experience varies, just sharing my ways. (btw i didn't register cuz im not in the US).
because u didnt register is why u didnt get the update
We have found out that when ur registered and u try to freeze the the silent update or rename it, it still updates no matter what. I hear droid wall stops the update but not sure
samomamo said:
What if we are not registered to Amazons account? Becouse wen I wanted to get the ota I registered ans clicked on sync to get the ota. Maybe the registration has something to do with it?
Sent from my Kindle Fire using xda premium
Click to expand...
Click to collapse
Probably. I had de-registered my Kindle prior to the 6.2.1 update and I did not get the update, even though it was out for a few days and my wifi was on / tablet was being extensively used during those days.
I did get the 6.2 update before I de-registered. So almost certainly, the de-registration helped.
here is my experience:
kf was and is registered
removed /system/etc/security/otacerts.zip -> update downloaded but did not install -> was automatically deleted from cache folder after failed attempt to install
installed "nfx-update-kindle-6.2.1" -> http://forum.xda-developers.com/showthread.php?t=1407852
6.2.1 is much more responsive than older version
b.t.w. root method for 6.2.1 is available:
http://forum.xda-developers.com/showthread.php?t=1399889
It seems to me that when an individual registers amazon uses that mac address for sending the update.... I could be wrong so please do not think that I am saying this is entirely true but, if all of these methods are confirmed as not working such as freexzing,removing apps, etc... then there has to be somesort of way that amazon is still able to update to your fire...
OK. So I restored back to the stock Kindle Fire rom. After I did that, it restarted like 3 times and now it's unrooted. I'm pretty sure it didn't update itself. But I'm not sure.
Also, Kindle Fire Utility won't detect my kindle, so I can't use that to reroot. What would be the easiest way to root it again? I don't want to go through the hell that I experienced last time aha.
thanks
If you figured out how to root it the first time you should be able to do it again all the tools are located in the Developer section go do some reading and do it.
zack_droid said:
OK. So I restored back to the stock Kindle Fire rom. After I did that, it restarted like 3 times and now it's unrooted. I'm pretty sure it didn't update itself. But I'm not sure.
Also, Kindle Fire Utility won't detect my kindle, so I can't use that to reroot. What would be the easiest way to root it again? I don't want to go through the hell that I experienced last time aha.
thanks
Click to expand...
Click to collapse
Use BurritoRoot3 to root and get FFF.
Then try to get KFU working to install TWRP.
Actually I'm having a very similar problem. My Kindle Fire automagically unrooted and now it isn't being recognized in any adb at all. I'm even using Ubuntu Linux right now and "adb devices" doesn't recognize my KF.
Before unrooting, my Kindle Fire had stock rom with no recovery. Just rooted to have access to default android market. I don't know what to do right now.
Also remember to make the Market.app a system app using Titanium Backup
I used burrito for the last two updates before 6.3 but for the 6.3. All i used was the Kindle Fire Utilty 0.9.4 for this update
I have never installed TWRP. I don't seem to need it. I don't know if this method would work if you have the TWRP installed
This has got to be one of the fastest ways to root the 6.3 kindle update
Downloaded the new Kindle Fire Utility 0.9.4. Got rooted in about 2 minutes with no trouble at all.
First click on - install_drivers.bat first
Then plug in the Kindle Fire and then click on - run.bat
Then a menu will popup Choose number 2 option - Install Permanent Root with Superuser.
Then choose option 6 (Extras) to re install the market and google apps
when you do option 2 you will see "installing TWRP ..." somewhere
so if you do option 2 with kfu twrp and fff will be installed
I continue to have driver issues with KFU. I suppose because I rooted my Galaxy Nexus using Wug's Toolkit my PC continues to see my Kindle as a Samsung device. Now I'm waiting for Kindle Water to be updated to root 6.3, b/c ADB does see my Kindle just fine on my Mac.
So OP, you don't have ABD installed at your, you are simply using the KFU?
I did the temp root after the first update to get the Google Market and other apps, but haven't since. Thinking I would like to update those apps assuming the KFU has the latest version of G+, Gmail, etc.
jocampbe said:
I continue to have driver issues with KFU. I suppose because I rooted my Galaxy Nexus using Wug's Toolkit my PC continues to see my Kindle as a Samsung device. Now I'm waiting for Kindle Water to be updated to root 6.3, b/c ADB does see my Kindle just fine on my Mac.
Click to expand...
Click to collapse
I had a similar issue. I installed the 'naked Samsung driver' in order to get adb to work with my GNex, and it causes the kindle to not work properly with adb. Had to uninstall those drivers from device manager in order for the new drivers to install properly. After that, all went well.
KFU was able to put TWRP on my Kindle, but rooting and gapps did not work, with permissions errors in the KFU text. Instead, I just used TWRP to install the rooted 6.3 rom, that worked like a charm.
Do I have to install FFF?
Sent from my Kindle Fire using Tapatalk
Hey, i need and what to root from scrath my kindle fire 6.3 can, and im new at rooting devices, can someone help me on how to do it step by step
Hi everyone this is my first thread here so let me know if this helps or if its in the wrong place, etc. The Bin4ry - http://forum.xda-developers.com/show....php?t=1886460 method works even on the new 10.3 firmware upgrade from amazon. The one-click w/o fastboot, they use an app installed directly on the kindle, solution for installing the 2nd bootloader and recovery, provided by fmkilo here http://forum.xda-developers.com/showthread.php?t=2106463 works on the rooted Kindle Fire 2 (original) as well. Hope this helps. I was unable to pull up the fastboot menu on my kindle fire and so I decided to try this method and it worked like a charm. You may have to uninstall and reinstall the app (it didn't work the first time for me, but it did the second time I installed it).
KamexxTheWolf said:
Hi everyone this is my first thread here so let me know if this helps or if its in the wrong place, etc. The Bin4ry - http://forum.xda-developers.com/show....php?t=1886460 method works even on the new 10.3 firmware upgrade from amazon. The one-click w/o fastboot, they use an app installed directly on the kindle, solution for installing the 2nd bootloader and recovery, provided by fmkilo here http://forum.xda-developers.com/showthread.php?t=2106463 works on the rooted Kindle Fire 2 (original) as well. Hope this helps. I was unable to pull up the fastboot menu on my kindle fire and so I decided to try this method and it worked like a charm. You may have to uninstall and reinstall the app (it didn't work the first time for me, but it did the second time I installed it).
Click to expand...
Click to collapse
So the 2nd bootloader exploit stil exists even in the 10.3 bootloader?
Sent from my Amazon Kindle Fire2 using Tapatalk HD
Yes to the best of my knowledge. The exploit is still there because I did not flash back to an older firmware or anything.
Sent from my LT30at using xda app-developers app
I had my KF2 rooted but when the OTA 10.4.3 installed, I lost root. Does anyone know how to root the KF2 on version 10.4.3?
Hi,
I tried rooting my Kindle Fire because I hate the built in things and I wanted the play store.
Anyway, I tried rooting it with Quem and during it the screen went off and restarted the kindle. Now when I go on the kindle it's unbearingly laggy and the 'Kindle Fire' bootup logo keeps flashing. Most of the time when I try to go to the settings after about 5 minutes of lag the screen just goes black.
Anyway I can just reset it so it's like brand new?
CharlieShawx said:
Hi,
I tried rooting my Kindle Fire because I hate the built in things and I wanted the play store.
Anyway, I tried rooting it with Quem and during it the screen went off and restarted the kindle. Now when I go on the kindle it's unbearingly laggy and the 'Kindle Fire' bootup logo keeps flashing. Most of the time when I try to go to the settings after about 5 minutes of lag the screen just goes black.
Anyway I can just reset it so it's like brand new?
Click to expand...
Click to collapse
Oh, the joys of rooting the Fire. Don't worry about the severe lag. Just keep running the root tool again. If you can, try to use Bin4ry's root method here. It may fare better for you.
I bet he needs to delete the local.prop on the data partition, think that's the name of the file. That would get rid of the lag atleast.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
stunts513 said:
I bet he needs to delete the local.prop on the data partition, think that's the name of the file. That would get rid of the lag atleast.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
Click to expand...
Click to collapse
Everytime I rooted my Kindle I had to put up with this issue. I wish I had thought of that. It was such a pain in the but to work with. I could achieve root by running the exploit again and again, but still. It can be done, but it takes patience.
KFFirst Aide there is a tool to fix this, i had this problem earlier today.
CharlieShawx said:
Hi,
I tried rooting my Kindle Fire because I hate the built in things and I wanted the play store.
Anyway, I tried rooting it with Quem and during it the screen went off and restarted the kindle. Now when I go on the kindle it's unbearingly laggy and the 'Kindle Fire' bootup logo keeps flashing. Most of the time when I try to go to the settings after about 5 minutes of lag the screen just goes black.
Anyway I can just reset it so it's like brand new?
Click to expand...
Click to collapse
You can try to use the Bin4ry root method.I used it and had no problem.