I have a nexus one running a stock 2.2 FRF91 that is rooted with via universal androot. When the update for 2.2.1 notification hit my phone I downloaded it by mistake. I did not install it but the files are still on the phone along with the update icon in my notification bar. When I go to it I now only have the option to restart on install. Not the other options like install later.
Does anybody know how to get rid of the downloaded files and make that notification basically go away. Back to the do you want to download and install this update one? I figured it would require finding the files via a file browser and deleting them. I looked around real quick to see if I could find what and where it downloaded but was not sure what was what. I did not want to delete the wrong thing.
I would really like to get rid of this icon in the notification bar if possible.
Try rebooting using quickboot. It'll give you 2-3 days of being free from the notification. It beats hitting "install later" every 10 mins. Its been working for me so far
Sent from my Nexus One using Tapatalk
Thanks but I am past that point. I do not have that option. When I open the bar I get that its downloaded and verified and all that stuff. Only option is to restart and install.
Well as I entered my last post the notication popped up on the screen and I hit install later. But I still have the icon in the status bar. That was not there before today but I got the update push a couple of days ago. After reading another thread on the site it seems like others have the same issue
instruction
albundy2010,
1. apply update (recovery doesn't apply it, and delete update from /cache)
2. open rootexplorer, go to /system/ , find file "check", edit 1 to 0
3. open /system/build.prop , edit
ro.build.id to frg83G
version realise to 2.2.2
build host to android-test-20.mtv.corp.google
description passion user 2.2.1 to 2.2.2
save and reboot, enjoy
Go find and download FOTAkill
Sent from my Nexus One using XDA App
Better yet, just install the OTA, and then root afterwards. No big deal. Should take all of 2 mins.
This is a very old thread fellas. Let it die.
Sent from my Nexus One using XDA App
Related
For almost a full day I tried undoing the hack with adb shell in order to install the beta update. You must have your Atrix Rooted and have SuperUser Okay lets start.
1) Check if you have WebtopModBackup in /mmt/sdcard (if not then dl)
2) Download from the market Super Manager https://market.android.com/details?id=gpc.myweb.hinet.net.TaskManager
3) Open Super Manager and go to settings "Enable ROOT function" give SuperUser permission
4) Go back to Super Manager and click on "File Explorer"
5) Locate "WebtopModBackup" once in their you should see 6 files.
6) hold down on the first one (one by one) and select "rename"
7) Erase .bak from all 6 files
8) Check all six files and click "Copy" (its the 3 icon on the bottom looks like 2 papers on top of each other)
9) Once you do that click on "Back up level folder" 3 times (You should be on "/" section
10) Go down to System (folder) (it will ask you 3 options R/w, read only, and so on.. Select R/W then go to "app"
11) Under "apps" (/system/app) Paste the files you copied! The 5th icon on the bottom (looks like a clipboard)
12) You will notice "force close over and over" This is normal" All you have to do from here on is turn off the phone. Lock the phone and hold the power button and click on "shut off"
Your all done! download the update and enjoy.
Note: You will lose SuperUser and Root Acc
Mine failed
Edit: Wrong thread sorry
This is helpful.
After the update are we able to add the hack back in?
Sent from my MB860 using XDA App
At this time their is no way to root. Sideloading still works tho.
This would help immensely if I had the original files. If someone could email me the apk files and the codex files, I'd be grateful.
[email protected]
Sent from my MB860 using XDA App
Ok, I may not need the APKs but I do need the odex files if possible.
im just doing this. results to follow. I assume you meant .BAK and not .DAK
Thanks I replace it.
It all worked perfectly. Many thanks. I will try to put the mod back. I meant to copy the modded files before replacing them but forgot!
Sent from my MB860 using XDA App
I tried to run the webtop mod again. Put the software on the phone but didn't install it.
Sent from my MB860 using XDA App
The Mod wont work on the new update. Has this write up helped anyone?
I heard the new update is out. Is this true?
LLuisLA said:
For almost a full day I tried undoing the hack with adb shell in order to install the beta update. You must have your Atrix Rooted and have SuperUser Okay lets start.
1) Check if you have WebtopModBackup in /mmt/sdcard (if not then dl)
2) Download from the market Super Manager
3) Open Super Manager and go to settings "Enable ROOT function" give SuperUser permission
4) Go back to Super Manager and click on "File Explorer"
5) Locate "WebtopModBackup" once in their you should see 6 files.
6) hold down on the first one (one by one) and select "rename"
7) Erase .bak from all 6 files
8) Check all six files and click "Copy" (its the 3 icon on the bottom looks like 2 papers on top of each other)
9) Once you do that click on "Back up level folder" 3 times (You should be on "/" section
10) Go down to System (folder) (it will ask you 3 options R/w, read only, and so on.. Select R/W then go to "app"
11) Under "apps" (/system/app) Paste the files you copied! The 5th icon on the bottom (looks like a clipboard)
12) You will notice "force close over and over" This is normal" All you have to do from here on is turn off the phone. Lock the phone and hold the power button and click on "shut off"
Your all done! download the update and enjoy.
Note: You will lose SuperUser and Root Acc
Click to expand...
Click to collapse
WebtopModBackup... Where do I get that if I didn't do any back ups?
After doing this i still had trouble doing the update. I hooked up the phone to see if the webtop mod still existed. Webtop didnt work but I also didnt get any notifications when connecting to hdmi, not even for the media center app. Has anyone confirmed hdmi still works?
webtopmodbackup isnt on my device is there anywhere i can DL this from
I also dont have webtopmodbackup, anywhere that I can DL it from?
anyone? i want to download the update and this is killing me
I can confirm the instructions work fine and I've successfully updated. Unfortunately, I performed the process before I realized anyone might be missing the files or I could have upped them for you all...
webtopmodbackup..if you dont have it..can be put on the phone if you just redo the webtop mod
Unable to launch webtop mode w/hdmi... Any ideas?
I found how for the X2 but the instructions dont work for the Revolution.
Anyone know the way to stop it?
Thanks
Using root explorer goto /system/lib/libdme_main and add .bak to the end of it. You will keep bluetooth and no more update. Make sure you do NOT mess with anything else!
Sent from my VS910 4G using xda premium
I deleted that file (adding.bak sounds much better) and it has gone away, just like mtmichaelson said.
Sweet thank. Ya on my droid 2 i stopped a bunch of stuff and just did the .bak so if i need it later i can just change it back.
Thanks
Just to double check, this works on revo phone.
When I acess file it has .so file type do I change .so to bak?
I just added .bak after the .so
Sent from my VS910 4G using XDA Premium App
Revolt - LTE
I'm not sure if this is related, but I noticed that after I flashed Revolt 1.3, I never see the "LTE" symbol in my notification bar. I'm in an LTE area, so I know it's available--does that mean my phone isn't running LTE anymore or is the symbol just not showing up on this ROM? I apologize in advance if this is a ridiculously misguided question--I'm new here and learning as I go.
By the way, mtmichaelson--I said this before and I'll say it again--awesome ROM! Thanks again for your hard work.
mtmichaelson said:
Using root explorer goto /system/lib/libdme_main and add .bak to the end of it. You will keep bluetooth and no more update. Make sure you do NOT mess with anything else!
Sent from my VS910 4G using xda premium
Click to expand...
Click to collapse
will this also work for the updated Revolution (2.2.2)?
Thanks in advance
ally3447 said:
will this also work for the updated Revolution (2.2.2)?
Thanks in advance
Click to expand...
Click to collapse
Yes it does
Sent from my VS910 4G using xda premium
mtmichaelson said:
Yes it does
Sent from my VS910 4G using xda premium
Click to expand...
Click to collapse
So, right now it is a .so file. Do I just add .bak to it, or change it from .so to .bak?
(Just want to be extra sure.)
Also,I would like to root my phone. I found a way that someone rooted theirs with their 2.2.2. Do you think I should root first, then change the file so it doesn't update? Or does it matter?
by the way, Here is the root I found(sorry it's a bit long):
"How to root your OTA Updated Revo:
This method requires you to downgrade your phone back to the V4 stock version. As of now, there seems to be no root process for the V6 update. This method has worked for me and I am also on a custom ROM that has been said to have some, if not most of the V6 updates included without the bloatware.
Step One:
- Be sure to get the following files:
---- LG VZW_United_WHQL_v1.2.0.exe
---- LGAndroidDriver_Ver_1.0_All.exe
---- LGNPST_Store_Lab-1.zip
---- VS910.dll (required to use LGNPST_Store_Lab-1.zip)
---- VS910ZV4_04.S4_04.P58008.R5.user.tot
---- RevoToolkit-1.0.apk (This is untested by me but supposed to provide an easier method to install CWM mod vs the ADB method)
---- SuperOneClickv2.1.1-ShortFuse (Includes the needed ADB program)
---- rageagainstthecage-arm5.bin (The exploit needed to root revo, not necessarily found with SuperOneCLick)
---- RevoltRom1.3.zip (This is optional, but recommended to speed up your revo and also to comply with the original topic of this thread. It 'seems' to stop the OTA from 'trying' the update since it includes updated features. NOTE that I said 'seems'... Other things I did may be the actual result I haven't seen the OTA try to install...
Ok, so to start, you will want to be sure that you have the drivers on your computer (I'm using windows 7 x64), so that is what this method has proven to work on by me.
Be sure to install:
- LG VZW_United_WHQL_v1.2.0.exe
- LGAndroidDriver_Ver_1.0_All.exe
Both may not be required, but I have both installed and things worked.
Then you will need to install:
- LGNPST_Store_Lab-1.zip
- VS910.dll (This is just copied into the folder LGNPST/Models. My install put the LGNPST program in C:\LG Electronics, not c:\Program Files (x68)... )
- You will run the LGNPST program, select the VS910.dll via Menu: File --> Select DLL.
- Then, in the bottom right of the LGNPST program, select BIN File (folder icon) to load the 'bin'.
--- This will require you to enter *.* in order to find the .tot file. Don't worry, this .tot file is what you need in the LGNPST Program.
- Once loaded and your phone is connected and recognized (Phone must be in 'Internet USB Mode'), hit the Start Button. This will begin the process of restoring your phone back to V4.
After that has completed, which takes a while, you will then need the SuperClick program to root.
- Copy, or verify, the rageagainstthecage-arm5.bin file is located in the Exploits folder where you extraced SuperOneClick.
- Run SuperOneClick, Select the exploit pull down (which defaults to 'auto') and select the rageagainstthecage option.
- Press the Root button and let it do its thing.
--- If it fails, this is what I had to do.. Reboot your phone. While it is rebooting, have the SuperOneClick program ready and waiting for you to hit Root again. As soon as the LG Logo becomes animated, hit Root and let it try again (While it is rebooting). This seemed to get the read/write options to work, where failed. This possibly is part of the update that is sticking around to stop you from rooting. So, try a few times. If/when succeeded, move on to the next steps if you wish to have some of the update 'fixes' without the update and a faster custom ROM...
To install a ROM, you need to have CWM installed.
Two methods to doing so seem to exist:
- The method I used was at this link: [RELEASE][6-14-2011] CWM Ported to the Revolution 4G! - xda-developers
Follow that and you should have a backup original image and the new image to get CWM to work to install custom ROMs
- The OTHER method, which is UNTESTED by me, is to use a simple tool called RevoToolKit, which is and APK file that runs directly on your phone. If it works, which others seem to say it does, this would be the most simple form of installing CWM to your phone. Be aware that this app is small, but uses a downloader to install CWM, so you want to make sure you have a good internet connection or data connection...
After that, you will want to follow the directions for CWM (ClockWorkMod) at this link:
- [Rom][8-17-11]Revolt Rom 1.3 - xda-developers
After all that, you should have a rooted Revo AFTER you managed to do the update.
I included links to some instructions in order to shorten up this post and not 'copy' someone else's methods and be sure that you can give the credit to them. The only credit I deserve for this is a complete step-by-step, in one place procedure to get you back or to root your Revo if you did the update.
In time, I am sure that there will be a simpler way to root the OTA Update, but until then, this is working for me and hope that this helps clear up some issues for others that find it tough to get back to root after the OTA Update."
It then has the file links, but I cannot post them since I am a newb.
Thanks again!
I don't see a way for you to change the file from .so to .so.bak without having root as far a rooting you only have to downgrade if your phone its v6 if out is running v4 all you need to do is root it
Sent from my VS910 4G using xda premium
Is there a way to do this without buying root explorer? I have bloat freezer so is there anything I can just freeze?
Thank You
*EDIT* just bought root explorer for $.99 through Amazon Appstore for those who still need it.
I'm on V4 and rooted back from V6 but it does not let me rename due to it being a read only file? sooo how do I add the bak? opened it with root explorer and it requested superuser privileges and I ok'ed it but when I go to /system/lib/libdme_main.so and try to rename it, it won't let me.
Sleepykat said:
I'm on V4 and rooted back from V6 but it does not let me rename due to it being a read only file? sooo how do I add the bak? opened it with root explorer and it requested superuser privileges and I ok'ed it but when I go to /system/lib/libdme_main.so and try to rename it, it won't let me.
Click to expand...
Click to collapse
On the top right of root explorer is a "Mount R/W" button. Click that and it should let you make changes to the system.
Hope it helps
"Home-Less and Iconic"
Thanks a bunch . That worked! I had pushed it at the system level. Didn't pay attention that I had to do it at the folder I'm in.
Sleepykat said:
Thanks a bunch . That worked! I had pushed it at the system level. Didn't pay attention that I had to do it at the folder I'm in.
Click to expand...
Click to collapse
Glad to help.
"Home-Less and Iconic"
My Droid 3 is rooted and I received the OTA notification. It downloads fine, reboots the phone, and begins to update. About 1/3 the way to update, the Android turns into an Exclamation point and reboots. Once back to home screen I get an Update Failed error.
Here is what I did so far:
-Defrosted all apps then rebooted
-Restored all system apps with Pete's One Click Root
-Pulled Battery for 5 min
-Factory Reset Phone
After each of these steps I tried to install the update and same thing. Will not get past 1/3. Any suggestions?
u need to rsd the swu.zip in order to get the update
OK, where can I get the swu.zip?
lacesout said:
OK, where can I get the swu.zip?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1255198
here u will find it along with rsdlite n adb fastboot. (make sure U read all that b4 U do it)
mrcastillo said:
http://forum.xda-developers.com/showthread.php?t=1255198
here u will find it along with rsdlite n adb fastboot. (make sure U read all that b4 U do it)
Click to expand...
Click to collapse
Thank you, this work!
lacesout said:
My Droid 3 is rooted and I received the OTA notification. It downloads fine, reboots the phone, and begins to update. About 1/3 the way to update, the Android turns into an Exclamation point and reboots. Once back to home screen I get an Update Failed error.
Here is what I did so far:
-Defrosted all apps then rebooted
-Restored all system apps with Pete's One Click Root
-Pulled Battery for 5 min
-Factory Reset Phone
After each of these steps I tried to install the update and same thing. Will not get past 1/3. Any suggestions?
Click to expand...
Click to collapse
lacesout, had the same experience. Used one-click method to root, then used psouza4's bloat script to remove, then restore apps when the update became available. These were my only mods. Went to /system/app and all app's are back with the proper apk extension. Update downloads fine, then hangs at 1/4 to 1/3 of install. Anyone else with similar experience or thoughts as to what's hanging the OTA install?
If you used the script to re-bloat the system, use root explorer and double check all the ".bak"s were removed. I don't remember which one, but I remember there was a file or two the script skipped over.
Also, if you did a nandroid before debloating, you can restore it, then go get the update. (The second option is what worked for me).
Sent from my DROID3 using XDA App
nu2droid said:
If you used the script to re-bloat the system, use root explorer and double check all the ".bak"s were removed. I don't remember which one, but I remember there was a file or two the script skipped over.
Also, if you did a nandroid before debloating, you can restore it, then go get the update. (The second option is what worked for me).
Sent from my DROID3 using XDA App
Click to expand...
Click to collapse
Thanks for the reply and the tip on root explorer, it's an elegant tool, more intuitive to use than the freeware apps.
All the file extensions in /system/app are either .apk or .odex with the exception of Fota.apk.bak, and Fota.odex.bak. As the first time I heard of nandroid was your post, I unfortunately didn't use it, so I don't know if these were the extensions before I used psouza's bloat removal script. Fota was not on the list of scripts to remove/rename in his original post.
As Fota is the "firmware over the air" app, it is suspicious that it's the only one with a .bak ext. I am using root explorer to rename both, removing the .bak, and then will attempt another update.
Success! "Your phone has been upgraded to 5.6.890.en US version". Have lost root, at least for the moment. Will deal with that tomorrow. Last thing to do before going to bed is find the "Thanks" button. Thanks for setting me on the right path. P.
Unable to root after OTA to .890
One click root not longer works. After clicking "run_to_root_your_droid3.sh" on PC (Ubuntu 10.04) I get no prompts on screen, but phone does reboot twice. No su privileges after boot. Busybox is installed in /system/xbin and there is nothing I can do about it as I can't mount r/w. Using Root Explorer and Script Manager as tools.
I realize I'm going to have to increase my learning curve here. Would appreciate any links to relative threads on this topic, or suggestions on what to try next (I have searched, but need some direction).
When an OTA update becomes available, there is a recurrent notification prompting to upgrade.
The below method tricks the OS into thinking that it is already at the latest version, in effect stopping the update notification from appearing.
I am not responsible for anything you do with your device.
Pre-requisite
Device must be rooted
Steps
Download FOTAKill apk
Put the apk in "/system/app"
Set proper file permissions (644, or rw-r--r--) for the apk
Clear "/cache" (e.g. boot into CWM and clear cache)
Reboot
Check "Settings > About tablet > System updates" and it should show "up to date" now.
Note that after rebooting there may still be a notification to update, after clearing no further notification will appear.
Rollback
To re-enable OTA update notification, delete the apk and reboot!
iamelton said:
lately since Android 4.2 OTA update became available for my device, there was a recurrent update notification prompting me to update..
as i dont want to upgrade yet due to app incompatibility issues not being resolved, i asked for help and was given a solution after searching and reading some posts..
it worked for me and i would like to share it here as i found that there were other users looking for a solution like i did..
ur device needs to be rooted to follow the steps below..
steps:
(1) download FOTAKill (firmware over-the-air kill) apk
(2) put the apk in "/system/app" with a file explorer
(3) set proper file permissions (644) for the apk
(4) clear "/cache" (i booted into CWM and cleared cache there)
(5) reboot
(6) check "Settings > About tablet > System updates".. should tell you "up to date" now..
note that after rebooting i still got a notification on update, but after clearing it there was no further notification since then..
Click to expand...
Click to collapse
Thanks,worked great, I didn't even need to clear the cache. On reboot, it said updating.... I panicked for a second, but it only reported for a coupe of seconds, then once booted, it said update available. I cleared the message and now the update has gone! In about phone - system update it reports upto date
Worked great, better than messing around with Google services framework.
Another possibility to get rid of OTA updates reminders on 4.1.2:
In the file "/system/build.prop" find the string starting "ro.build.fingerprint" and after symbol "=" add the following "google/nakasi/grouper:4.2/JOP40C/XXXXXX:user/release-keys"
Instead of XXXXXX place the figures from the string "ro.build.version.incremental"
Make the nandroid backup prior to this.
For editing file use Root Explorer.
After editing - reboot and connect to the Internet - the reminding should stop.
OR... download Autorun manager from the Play store and disable the following in Services( must enable system settings in preferences)
Receiver com.google.android.gsf.update.SystemUpdateService
Requires root access
wilx said:
Thanks,worked great, I didn't even need to clear the cache. On reboot, it said updating.... I panicked for a second, but it only reported for a coupe of seconds, then once booted, it said update available. I cleared the message and now the update has gone! In about phone - system update it reports upto date
Click to expand...
Click to collapse
Same here thank you iamelton!
andro54 said:
Same here thank you iamelton!
Click to expand...
Click to collapse
Same here didn't need to clear cache. The whole thing took about 30 seconds.
Thank you
Sent from my Nexus 7 using xda app-developers app
the clear cache part is for those who might have already downloaded the update package file (which is about 80MB) by the ota service.. it removes this file and frees up some cache space..
What does FOTAkill actually do to your system?
Sent from my Nexus 7 using Tapatalk 2
ExploreMN said:
What does FOTAkill actually do to your system?
Click to expand...
Click to collapse
That's a GREAT question.
iamelton do you know the specifics? It would also be interesting to know what permission if any are effected with this method.
Sent from my Nexus 7 using xda app-developers app
sorry but i have no idea what it actually does to the system, apart from the obvious function of stopping the OTA service..
from this page, it requires the following permissions..
Code:
android.permission.RECEIVE_BOOT_COMPLETED
com.google.android.providers.gsf.permission.WRITE_GSERVICES
com.google.android.providers.gsf.permission.READ_GSERVICES
It worked. I follwed your insttrucction. I made file permission to 755 instead. Is there any different? I already had 4.2 but not that one with multi user. I think the update will partition the SDcard, but maybe it already did from 4.1.2 to 4.2 with sdcard0 and emulated. That iswhat I already have. But not the multiuser. I was wondering if it will also block update 4.3 4.4 etc? ??
Sent from my Nexus 7 using xda app-developers app.
datorprofessor said:
It worked. I follwed your insttrucction. I made file permission to 755 instead. Is there any different? I already had 4.2 but not that one with multi user. I think the update will partition the SDcard, but maybe it already did from 4.1.2 to 4.2 with sdcard0 and emulated. That iswhat I already have. But not the multiuser. I was wondering if it will also block update 4.3 4.4 etc? ??
Sent from my Nexus 7 using xda app-developers app.
Click to expand...
Click to collapse
afaik it should stop any future OTA updates regardless of android versions..
and granting permission 755 is more than the needed 644, but that does no harm..
i thought 4.2 was the version with multi-user support, but then im not on 4.2 yet so cant tell much about it..
What Google did with OTG / Stickmount / DirectoryBind on 4.2 was a real buzz kill, so I don't want it now
either. I'm not going to hold my breath on this, but I'm hoping that some future update might allow real
data sharing on a USB stick, so I might eventually want to do an update. My question is this:
If I install FOTAKill to stop the notices etc, will uninstalling it allow me to update again?
Sent from my Nexus 7 using xda app-developers app
gelhack said:
What Google did with OTG / Stickmount / DirectoryBind on 4.2 was a real buzz kill, so I don't want it now
either. I'm not going to hold my breath on this, but I'm hoping that some future update might allow real
data sharing on a USB stick, so I might eventually want to do an update. My question is this:
If I install FOTAKill to stop the notices etc, will uninstalling it allow me to update again?
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
i think removing the apk from /system/app/ should allow OTA notifications to show again, though i have not tried it yet..
btw, we have the same reason as why not to upgrade..
I used this from other thread, forgot where it is.
"Install Autostarts app.
Go to "After Startup"
Scroll down until you see "Google Services Framework"
There should be several of them. For me it was the third one. Touch it and read the bottom of the popup to find out. It will say "Receiver com.google.android.gsf.update.SystemUpdateService. ....(you get the point)
Disable it. Done..."
Peaceful on 4.1.2.
There's another alternative way that I used that worked:
In the file "/system/build.prop" find the string starting "ro.build.fingerprint" and after symbol "=" add the following "google/nakasi/grouper:4.2/JOP40C/XXXXXX:user/release-keys"
Instead of XXXXXX place the figures from the string "ro.build.version.incremental"
Make the nandroid backup prior to this.
For editing file use Root Explorer.
After editing - reboot and connect to the Internet - the reminding should stop.
helloterence said:
There's another alternative way that I used that worked:
In the file "/system/build.prop" find the string starting "ro.build.fingerprint" and after symbol "=" add the following "google/nakasi/grouper:4.2/JOP40C/XXXXXX:user/release-keys"
Instead of XXXXXX place the figures from the string "ro.build.version.incremental"
Make the nandroid backup prior to this.
For editing file use Root Explorer.
After editing - reboot and connect to the Internet - the reminding should stop.
Click to expand...
Click to collapse
thx for ur method..
i suspect this method only applies to the OTA of android 4.2, which means future OTA alerts of, say, 4.2.1 will pop up again..
iamelton said:
thx for ur method..
i suspect this method only applies to the OTA of android 4.2, which means future OTA alerts of, say, 4.2.1 will pop up again..
Click to expand...
Click to collapse
Nope. I'm still on 4.1.2 and haven't gotten any notification about 4.2.1.
I'm assuming that updates to 4.2 and 4.2.1 are incremental, and as such you couldn't install or get a notification for 4.2.1 until you installed 4.2. So any method that stopped 4.2 notices would also stop 4.2.1 notices.
Sent from my Nexus 7 using xda app-developers app
Hi. I followed the directions off amazon website for manual update but it doesn't work and their instructions are by "corporate standards" lol. I am running 11.3.1.0_user_310084920 and I just downloaded update-kindle-7.4.8_D025_4849020.bin the latest from the amazon website.
Amazons website didn't say anything about a specific folder to put the update into it just said put it into the main drive folder. so I looked it up and there is supposed to be a folder called "kindleupdates" <hopefully case sensitive like this. I just created the folder on the drive and put the .bin into it then i went to the device menu and selected system updates then I click check now cause that is the only option available. after it runs it says last updated failed with a retry button now. when i click the retry button it doesnt work at all just flashes the text of last update failed.
I did this without creating the kindleupdates folder and also with it. nothing happens. and it only wants to connect to wifi if it is disconnected.
adb is working with my device fine if there is anything else i can do. I didn't push the file with adb though, i used gmtp to transfer the file and it is there.
for right this second i am just wanting to get this thing back to full stock since I have it rooted and i have multiple small issues with it like the status bar gone and chaning the build.prop for it doesn't work then work with anything else after since I have uninstalled to many system apps.
i dont have a fastboot cable but i seen and heard from stunts that it may not be needed because of buffer size.
i also unrooted this tablet and factory reset it and all to try the update as well. the root exploit is nice and quick lol
thanks to anyones help
You don't have the right version for your Kf. If you try to flash v7.x.x over your 11.x.x you will brick it.
Sent from my SCH-I545 using XDA Free mobile app
This is the page you need to download the update from.
http://www.amazon.com/gp/help/customer/display.html?nodeId=201357170
Sent from my SAMSUNG-SGH-I337 using XDA Premium 4 mobile app
Thanks guys can't believe I overlooked version but once I downloaded the other version it did the same thing. Grand pc Google page showed how to add it and that's the way I went. Successful. Now like new gonna watch closer what I do with root