Me and my best friend both have Kindle Fires now. I rooted & flashed the latest MIUI onto both of them successfully over the past week, so we're running the latest version available. What we've found is that when we both try to attach to his wireless router, they seem to disrupt each other or confused the router and eventually our wifi goes bye-bye on our Kindles. When just one of us is trying to attach to his router, it goes through fine & seems to stay connected well without any issue.
Can anyone offer any recommendations on how to perhaps customize the wifi connection on either the Fire or the wifi router to try and resolve this issue?
Thanks much for your help in advance! Please ask any questions if I left out any details that could help : ]
Does MIUI have the MAC address problem? That'd be the first place I'd check. THen I'd check the router and see exactly what they're trying to do. My thoughts:
Either they have the same MAC, same name, or are vying for the same IP.
http://forum.xda-developers.com/showthread.php?t=1406845
Thanks for the feedback, guys! And thank for that related thread link! I reviewed that post and I have to admit, I'm a lil lost with where to start or what to do with that. I have a feeling both devices may be running the same MAC address, but I'm in the process of confirming that today. I also tried forcing a static IP on the Fire when connecting, but that didn't seem to resolve the problem.
Anyone have any, dare I say, more simple instructions for how I might go about altering my devices MAC address with MIUI? I'm not sure that the information in that post is fully applicable to the MIUI rom, so I'm hesitant to begin trying to give it a go, and plus, I might need something a little more noob-friendly... I could use a little more handle-holding with this, as I'm fairly fresh to rooting & flashing ROMs (but fairly computer literate).
look at post #24 in the linked thread - seems to be a easier solution
Oh, thanks! ... That does look much more manageable Now to just figure out where to get the file from the stock ROM and replace it. I did a backup of my stock stuff via TWRP prior to flashing MIUI, so does anyone know where I can locate this file from the stock amazon ROM after I've completed a backup of stock via TWRP?
I then assume that after locating the stock version of the file, that I would just replace the file in the root directory/system/bin right on the Kindle when it's attached to my PC via USB.
Yah.. I'm a noob, but trying! : \
Stock file I need to find: /system/bin/wlan_loader
there is one attached 2 or 3 posts after #24 - that should do it for your needs
Great! Thanks again!!!
This part of the post gets me a little lost. I assume I need to purchase & download Root Explorer ($3.99 in Market). As for performing the same thing this person did, I'm not quite sure how to go about doing that. One question I have is: Is Root Explorer absolutely necessary to perform this file replacement? It seems a little more involved than just simply replacing the file on the device while it is plugged in to my PC via USB.
I used root explorer, mounted as r/w, made a copy of the original JIC, overwrote the existing file within /system/bin and modified the permissions to appear as the original (rwxr-xr-x) rebooted leaving the system as r/w
Sure enough mac address is the same as when I was in 6.1 Kindle Fire OS.
Click to expand...
Click to collapse
Specifically, here are the things I'm not 100% clear on:
1) 'mounted as r/w' - I assume this means mounting as read/write; is this performed via Root Explorer?
2) 'made a copy of the original JIC' - I do not understand what is meant by 'JIC'
3) Can file permission changes as described above be performed in Root Explorer?
I greatly appreciate any insight! This appears to be the solution to my problem, not it's just a matter of execution on my part. Thanks, guys!
would use file explorer from the market - no cost and does the same
if you activate "root explorer" and "mount as root" in the settings all at the bottom
here the link:
https://market.android.com/details?id=com.estrongs.android.pop&feature=search_result#?t=W251bGwsMSwyLDEsImNvbS5lc3Ryb25ncy5hbmRyb2lkLnBvcCJd
1) 'mounted as r/w' - I assume this means mounting as read/write; is this performed via Root Explorer?
Click to expand...
Click to collapse
file explorer does this with the above settings automatically
2) 'made a copy of the original JIC' - I do not understand what is meant by 'JIC'
Click to expand...
Click to collapse
would mean he means the file to exchange
3) Can file permission changes as described above be performed in Root Explorer?
Click to expand...
Click to collapse
you can also do with file explorer - long tap on file - properties - change permission
Awesome - b63 - you're excellent
Ummmm... But I have to ask a really stupid question. I can't seem to find the /system directory on my Fire. I already had ES File Explorer... and I'm in it now, and I can only look around on my SD card it seems... Is the /system directory on the main internal storage of the device, or on the 'SD card?' Any help in finding this directory on my device would be appreciated! Sorry for the nooby questions n such
are the root settings made in the settings of es ?
then you can set your start directory to / somewhere in the settings
or simply go one directory up
when you are on / then you see the system directory like all the others (sdcard also)
OK... I'M SO CLOSE!
I got up to the root directory ( / ) and found the /system/bin directory... I have the new (well, old stock version) wlan_loader file from the linked thread that I downloaded on my Kindle on the SDCard ready to overwrite the existing file.
I definitely have Root Explorer on in ES File Explorer - it prompted me to allow and I did every time it asked. I then tried to copy the stock version of the file over my current version in /system/bin, but it said that the copy failed. I then went and tried to delete the existing file in /system/bin, but it said something like 'this file cannot be deleted' I'm not sure what is keeping the file locked. Do I need to modify the permissions of the file to be writable or something?
I hard-pressed on the file and tried to play around with it, but the only close option I have is 'Properties,' which didn't seem to allow me to change anything about the file though. So, I'm stuck : \ Help!?
OK, I got it! I didn't flip the 'Mount /, /system as writable option after switching on Root Explorer :\ My bad! But I was able to overlay the file now Let's test my MAC address now after rebooting.
looks promising ...
GET-R-DONE!
Yahoo! I got it!
I rebooted and everything seems to be functioning just fine - I'm connected to Wifi like normal, no big deal... AND, my MAC address is totally different than what it was before, so I think this did the trick!
Now to test it concurrently with my best friend's Kindle to ensure we can sit on the same network / router together. If it doesn't work, then I'll look to replace his wlan_loader file as well
Thanks for all your persistent assistance b63! I really appreciate it : ]
Was fun, and I learned a lot : ]
but take care if you change his one as well not to end up with the same mac again ...
and as allways - glad to help ...
please mark the subject of the topic (edit first post) with [Solved]
Related
HI Guys,
Maybe somewhat can help me out here, in my attempt to update my Acer A500, I may have in a kind of way bricked my phone. I attempted to replace wpa_supplicant file as per some of the instructions, needless to say the update failed and me in my pure genius figure I would simply factory reset and reboot. Which I ended up doing, the problem now is that the WIFI does not turn on and my tab has been unrooted, I no longer have any file explorer app on the phone and I can't download anything. Does anybody know how I can gain access to the root files so that I may revert back the old file, or somehow install an apk file from the mini sdcard or even get access to the internet via bluetooth or USB. Anything would be helpful.
FYI - I am trying to gain access to my root files using Android SDK, but I've always had problems getting any of my pc to find any of the android stuff when plugged in.
Ph0tin0 said:
HI Guys,
Maybe somewhat can help me out here, in my attempt to update my Acer A500, I may have in a kind of way bricked my phone. I attempted to replace wpa_supplicant file as per some of the instructions, needless to say the update failed and me in my pure genius figure I would simply factory reset and reboot. Which I ended up doing, the problem now is that the WIFI does not turn on and my tab has been unrooted, I no longer have any file explorer app on the phone and I can't download anything. Does anybody know how I can gain access to the root files so that I may revert back the old file, or somehow install an apk file from the mini sdcard or even get access to the internet via bluetooth or USB. Anything would be helpful.
FYI - I am trying to gain access to my root files using Android SDK, but I've always had problems getting any of my pc to find any of the android stuff when plugged in.
Click to expand...
Click to collapse
I was in this court just yesterday, swearing up and down for some reason.
You'll need the root explorer apk, gingerbreak apk and the original wpa_supplicant file posted all over XDA.
Download and install Android SDK. It will also make you download the Java SDK too before you install the Android one. Start installing the Android SDK. It will seem like it's going to take forever, but you really only need what's in the folders 2 minutes in.
Go into the program files folder where the SDK stuff is and rip the 3 ADB files out and place them in their own folder. Mine were in: c:\program files\android\android-sdk\platform-tools\
I took the 3 files out and placed them in c:\and\
Place the apks in the c:\and\ folder
Make sure the driver files are installed from the Acer website.
Make sure USB bugging and apps from outside sources are enabled in settings on the tab.
Plug the tab into the PC via USB.
Open up the command prompt and go to the c:\and\ folder
then type
adb install c:\and\rootexplorer.apk
ENTER
then
adb install c:\and\gingerbreak-v1.20.apk
ENTER
The apps should be now installed on the tab.
Then just transfer the wpa_supplicant file over and you're right where you need to be.
Make sure you change the permissions on the wpa_supplicant file like you did the first time (enable everything read/write/etc etc) by holding on the wpa_supplicant file that you paste.
rorytmeadows said:
Open up the command prompt and go to the c:\and\ folder
then type
adb install c:\and\rootexplorer.apk
ENTER
then
adb install c:\and\gingerbreak-v1.20.apk
ENTER
The apps should be now installed on the tab.
Then just transfer the wpa_supplicant file over and you're right where you need to be.
Make sure you change the permissions on the wpa_supplicant file like you did the first time (enable everything read/write/etc etc) by holding on the wpa_supplicant file that you paste.
Click to expand...
Click to collapse
You are my new hero, all this time I've been trying to get Android ADK to recognize my tablet, but to no success. All I had to do was run ADB, which Ironically I had done, but only to see if it recognizes my unit. I was not aware I can install apps with it.
I'm not worthy... I'm not worthy
A million thank you's, now to try and get 3.1 installed and hopefully Googel/android was smart enough to put in a stock file explorer.
Not working wifi hardware
Somewhat similar to what happened to this guy. But to be specific, I am using an acer a500 originally on a rooted ics 4.0.3, i remember using lucky patcher and using the custom patch on adobe flash player then i saw an update regarding busybox and superSU...i was able to install the busybox updater but not the superSU since i remembered i already had superuser. I opened superuser and then it updated...from then on...I lost my wifi...at start it was still there but it can't connect. also, i lost my root because i no longer am able to use titanium backup. double checking it, i downloaded a root checker and it displayed not properly rooted. seeing this, i thought it's been a long time since i've updated my rom so i might as well upgrade everything...my bootloader, kernel, rom. So i first degraded it by flashing to the full package stock HC 3.1 ROM (it had an old HC 3.1 bootloader). Then i noticed i can no longer turn on my wifi and use my old apps...I flashed it back to a NON-rooted stock ics 4.0.3 thinking it might fix it...but it did not. HELP please...
NOTE: These instructions may be outdated. If you've installed a recent ROM, the cifs drivers are probably built in, and you should be able to use Cifsmanager as long as the "Load cifs module" option is checked.
These are my notes for mounting a remote Windows share on my Kindle Fire. Note that this also works with CM7.
Why do this? My usage example is so I don't have to manually copy comics down to the Kindle for reading with Perfect Viewer. I can read them directly via Wifi on my Kindle. It's also a lot easier to manage the files on the PC.
Root is required
CifsManager Free
https://market.android.com/details?id=ws.plattner.cifsmanager&hl=en
Drivers
http://forum.xda-developers.com/showthread.php?t=1396960
Big thanks to riverzhou for providing these files!
Steps
1. Install root if necessary - find another guide for this
2. Ensure a proper share is available from PC
3. Install CifsManager - note, not available on Amazon appstore, so will have to install from Android Market, or side load
4. Copy drivers to /sdcard/cifs
5. CifsManager
Load cifs module -> checked
Load via insmod -> checked
Path to cifs.ko: /sdcard/cifs/slow-work.ko:/sdcard/cifs/cifs.ko
Use IP for share, like this: 192.168.15.100/sharename
Create folder on sdcard for mount point, like /sdcard/comics
Ectoplasmic said:
These are my notes for mounting a remote Windows share on my Kindle Fire. I have it working, and will tidy up the steps as time passes.
Why do this? My usage example is so I don't have to manually copy comics down to the Kindle for reading with Perfect Viewer. I can read them directly via Wifi on my Kindle. It's also a lot easier to manage the files on the PC.
Root is required
CifsManager Free
https://market.android.com/details?id=ws.plattner.cifsmanager&hl=en
Drivers
http://forum.xda-developers.com/showthread.php?t=1396960
Big thanks to riverzhou for providing these files!
Steps
1. Install root if necessary - find another guide for this
2. Ensure a proper share is available from PC
3. Install CifsManager - note, not available on Amazon appstore, so will have to install from Android Market, or side load
4. Copy drivers to /sdcard/cifs
5. CifsManager
Load cifs module -> checked
Load via insmod -> checked
Path to cifs.ko: /sdcard/cifs/slow-work.ko:/sdcard/cifs/cifs.ko
Use IP for share, like this: 192.168.15.100/sharename
Create folder on sdcard for mount point, like /sdcard/comics
Click to expand...
Click to collapse
Worked out pretty good for me! Thanks
I just tried this... worked well for me as well.
Nice, now if only I can get rooted again after the 6.2.1 update, I'll be able to follow my own guide again
Can someone explain how to set up the computer side of this? I got the Fire side working (I think), but I'm not sure how to get a remote share working under Windows.
brian112358: it really depends on your version of windows.
Ectoplasmic: You're Awesome. You just single handedly gave my kfire 2TB of resources while on my home network.
brian112358 said:
Can someone explain how to set up the computer side of this? I got the Fire side working (I think), but I'm not sure how to get a remote share working under Windows.
Click to expand...
Click to collapse
I was having problems with my Windows shared folder as well. After trying all kinds of variations on my path name I eventually started from scratch, but instead of manually entering my mount paths I let CifsManager do it for me. Then everything worked as it should, even though my manual entries were exactly the same as the automated ones. Go figure.
Anyway, I'm on a 32-bit Windows 7. First, find the folder you want to share and Right-Click>Properties>Sharing>Advanced Sharing>Check the Share this Folder box>Ok. Take note of the name. (Mine was "Downloads")
The share path for my folder is now:
192.168.1.101/Downloads
In CifsManager I followed the OP's instructions for setting the driver paths, but I did not create a folder for the mount point on the KF. Instead, I set Mount point prefix to: /mnt/sdcard/cifs. I then added a New Share Path and only entered the following:
Share Path: 192.168.1.101/Downloads
*Tap on Mount Point field and it should auto fill
That's it. CifsManager then created a new folder: /mnt/sdcard/cifs/Downloads. I do not have a password login for my pc so I left user as "guest" and password blank. Works perfectly now. Like I said, everything was exactly the same as my manual entries, but for some reason it works now
Hope that helps.
golucky said:
brian112358: it really depends on your version of windows.
Ectoplasmic: You're Awesome. You just single handedly gave my kfire 2TB of resources while on my home network.
Click to expand...
Click to collapse
Glad it's working. I also noticed a little better Wifi performance since the 6.2.1 update, at least with this app.
This is really handy to have. Saves a lot of trouble copying files to the Kindle. This is the sort of thing that needs to be baked into custom roms.
Followed the steps in the OP. Only thing is I'm still getting the same errors that I got before adding the drivers provided.
if I use the IP of the share I get : Mounting the share has failed with an error. mount: No such device or address. (I can browse to the IP/path with ESFE)
if I use the network name I get: Mounting the share has failed with an error. mount: Invalid argument.
I tried to insmod the cifs.ko via terminal and it threw an error code there too. "Exec format error"
I'm running NRG's ICS CM9 ROM 6/23 with Hashcode's 3.x kernel (dated Jun 8 in About tablet info)
Edit: or could it be the drivers just don't like the 3.x kernel. Leaning towards that after a little more reading.
ProfEngr said:
Followed the steps in the OP. Only thing is I'm still getting the same errors that I got before adding the drivers provided.
if I use the IP of the share I get : Mounting the share has failed with an error. mount: No such device or address. (I can browse to the IP/path with ESFE)
if I use the network name I get: Mounting the share has failed with an error. mount: Invalid argument.
I tried to insmod the cifs.ko via terminal and it threw an error code there too. "Exec format error"
I'm running NRG's ICS CM9 ROM 6/23 with Hashcode's 3.x kernel (dated Jun 8 in About tablet info)
Edit: or could it be the drivers just don't like the 3.x kernel. Leaning towards that after a little more reading.
Click to expand...
Click to collapse
I just installed cifs from the market. Did not bother with the drivers and cifs connected with my server the first time. I am on twa's job ROM.
ghost_og said:
I was having problems with my Windows shared folder as well. After trying all kinds of variations on my path name I eventually started from scratch, but instead of manually entering my mount paths I let CifsManager do it for me. Then everything worked as it should, even though my manual entries were exactly the same as the automated ones. Go figure.
Anyway, I'm on a 32-bit Windows 7. First, find the folder you want to share and Right-Click>Properties>Sharing>Advanced Sharing>Check the Share this Folder box>Ok. Take note of the name. (Mine was "Downloads")
The share path for my folder is now:
192.168.1.101/Downloads
In CifsManager I followed the OP's instructions for setting the driver paths, but I did not create a folder for the mount point on the KF. Instead, I set Mount point prefix to: /mnt/sdcard/cifs. I then added a New Share Path and only entered the following:
Share Path: 192.168.1.101/Downloads
*Tap on Mount Point field and it should auto fill
That's it. CifsManager then created a new folder: /mnt/sdcard/cifs/Downloads. I do not have a password login for my pc so I left user as "guest" and password blank. Works perfectly now. Like I said, everything was exactly the same as my manual entries, but for some reason it works now
Hope that helps.
Click to expand...
Click to collapse
Hi -
I set mine up just like this ... and it did indeed create the mount point /mnt/sdcard0/cifs/comic. I get the little green circle on CifsManager ..BUT.. when I click on the mount, CifsManager gives me this error: This feature depends on an installed file manager (astro/estrongs).
I do have Astro installed, and also Perfect Viewer (comic reader). I can navigate to /mnt/sdcard0/cifs/comic via root-manager and I see my comics, but can't load them. If I try to load them via any other method (while cifs mounted) I get file not found.
What could be the problem please ??
Thanks
Not sure if this will help anyone. I just came back to this thread thinking I needed the syntax for installing the drivers. Turns out I didn't.
Every relatively modern ROM I've installed (CM9, CM10) has not needed drivers, either on my KF, or my Samsung. However, I found it necessary to ensure "Load cifs module" is checked in the CifsManager settings.
Also, if you're using PerfectViewer, something I didn't know for quite a while is that you can actually browse and read from network shares directly from the app. Use the "open file" method and not the bookshelf, change from Local to Lan and go from there.
I still like to use CifsManager for various reasons
Hi,
If your like me and you have had some problems with android market on your Kindle Fire (yes,I got one for christmas and its already rooted ) by following a guide with Vending.apk and though you can browse the market, it is stuck on Starting Download, I have found a solution to the problem... All you need to do is get a new file:bit.ly/tlWjSn
This file is simply an updated version to the Vendor.apk other tutorials provide.
All you do is the following(presuming you have rooted, got root explorer and GO launcher):
1.Copy the file to kindle at an easy to access location.
2.Long-Hold the file and tap move.
3.Navigate to / then system then app.
4.Set it to R/W mount (top left)
5.Paste the file.
6.Set the permissions like all other files(tick first 2 in first row, first 1 in second row and first 1 in third row then tap ok)
7.Reboot the device
8.Go onto GO launcher and add it to the screen (tap the list thing bottom middle of the screen,then tap Add. then select Application followed by Market)
9.Done! Enjoy!
Not sure if I should start a new thread or not.
I'm rooted and have SU. I have confirmed this by running Titainium Backup.
Market stopped working after the latest Kindle update. After I re-rooted, I tried re-installing vender.apk, but it still crashes upon launching it. Also, I am running Go Launcher EX.
When I browse folders while connected to a computer (using Win7), the system folder is hidden.
I never installed Root Explorer on the Fire. Is there a way for me to download and install it directly, or will I need to side load it? I assume if it's in the Market I'll need to side load.
leebo said:
Not sure if I should start a new thread or not.
I'm rooted and have SU. I have confirmed this by running Titainium Backup.
Market stopped working after the latest Kindle update. After I re-rooted, I tried re-installing vender.apk, but it still crashes upon launching it. Also, I am running Go Launcher EX.
When I browse folders while connected to a computer (using Win7), the system folder is hidden.
I never installed Root Explorer on the Fire. Is there a way for me to download and install it directly, or will I need to side load it? I assume if it's in the Market I'll need to side load.
Click to expand...
Click to collapse
Unfortunately you will as far as I know, but for $3.99, it is VERY useful when rooting or installing app's. market.android.com/details?id=com.speedsoftware.rootexplorer&hl=en
Check it out. If you run into anymore problems feel free to PM me as it's easier
Hello guys, I have a little question related to market app that maybe has been already answered so I won't start a new thread.
I have my KF with 6.2.1 rooted and with the full android market installed (EX launcher and so on).
Usually the market works fine, but I always get errors ( process com.android.vending has stopped unexpectedly) and consequent force closes even if I can download stuff and apps. Basically, it happens whenever the market takes an action.
Is it a known issue or ir it "normal" ?
Thank you all in advance.
For me, I am having problems copying the Vending.apk to /system/app folder. I follow the steps in that tutorial but when I paste the.apk in the folder nothing happens. Help??
Got it rooted last night, and I'm using file expert since my cheap ass doesn't want to buy root explorer.
sengokubattosai said:
For me, I am having problems copying the Vending.apk to /system/app folder. I follow the steps in that tutorial but when I paste the.apk in the folder nothing happens. Help??
Got it rooted last night, and I'm using file expert since my cheap ass doesn't want to buy root explorer.
Click to expand...
Click to collapse
I'm afraid that without Root Explorer you can't change the /system/app folder permissions from R/O to R/W, therefore you can't paste anything in that folder.
Chiwaz said:
I'm afraid that without Root Explorer you can't change the /system/app folder permissions from R/O to R/W, therefore you can't paste anything in that folder.
Click to expand...
Click to collapse
File expert gives you that option too though.
if ur rooted but it wont paste or read and write in root explorer then ur su wasnt pushed properly in ur root process! When i rooted my kindle i deleted my old su and did the whole root process from scratch when i got the new root process. The whole thing went smooth and su showed up in apps when done but it wasnt totally rooted as i couldnt read or write in root explorer. Jcase told me that when the adb command for pushing the su wasnt done right thats what happens. he fixed it for me, great guy.
that was me though
I don't think I have seen any mention of this idea yet. Sorry if I missed it...
In a recent thread about the 6.2.2 update and people wanting to prevent it, I thought I read that someone saw the file show up in the update directory. I'm assuming this means the same 'kindleupdates' directory you could manually drop the update into -- but if not, the idea is the same. Why not just take some step to prevent access to this directory?
The exact step to take would depend on how smart the developers were about dealing with problems in the update process
The easiest step would be to chmod 555 it. But of course if the update process is running as root it is under no requirement to honor those permissions! (My experience in the unix world tells me that about half the time, programs running as root do honor the permissions even though technically root overrides them).
Another easy step would be to delete it altogether. But they probably thought of that (if it's /mnt/sdcard/kindleupdates where someone could easily accidentally delete it) and recreate it if it's missing.
One trick that is often done is to replace the directory with a file. Some programmers do not think to check this kind of condition - they see there is something there, but they get an error opening it as a directory, and they just declare it's an error.
A more subtle trick would be to replace the directory with a symlink that points to a read-only directory (such as /system). In this case, they could open it as a directory, and just fail to write there. The programmer probably would not have thought to check whether it's a link vs. a real directory. One possible gotcha is if you point to /system, and /system is r/w, then the update could screw something up under /system. So maybe mount /system r/w, mkdir /system/kindleupdates, remount /system r/o, then link the update dir to /system/kindleupdates.
And finally, I don't know if Android has any kind of loopback filesystem capability, but loopback-mounting something read/only on that directory would certainly fake the OS into thinking there was a directory there; it would definitely be read/only, and I don't think they would ever think to check whether there is actually some filesystem mounted there! (and if there was, all you need is an app that constantly accesses some file you put there, which would make it busy so that it couldn't be unmounted).
The first method won't work because the sdcard partition is fat32 and doesn't accept unix permissions.
it downloads to the /cache folder - this folder is also used for other things like market downloads, logs from twrp and i don't know what else
btw. there are a lot of threads about this from the 6.2.1 update
make a short search for "prevent ota update" - you'll have a lot to read ...
well, i just deregistered my kindle acount and i'm still in 6.2.1...
b63 said:
it downloads to the /cache folder - this folder is also used for other things like market downloads, logs from twrp and i don't know what else
Click to expand...
Click to collapse
Ah, that makes this less practical. Still, perhaps when the next update comes out I can try a variation on this but it requires the filename to be known.
If the update is downloaded as a single file to /cache, which is named the same as the file you can manually grab, then someone who hasn't gotten 6.2.2 (and is not averse to this failing) can try this in a root shell:
mkdir /cache/update-kindle-6.2.2_D01E_3205220.bin
mkdir /cache/update-kindle-6.2.2_D01E_3205220.bin/blah
The purpose here is to put something unremovable in the way of the file it wants to download. Most likely if the update sees something with the existing name there it would probably want to blow it away (after determining it's incomplete) - and since any update there would normally be a regular file, they probably would do nothing more complicated than a simple unlink syscall to delete it before re-downloading. However, since it's a directory with something in it, that unlink will fail. In actuality, making the subdirectory (second command above) should be unnecessary because the unlink should not work for directories; there's a special rmdir syscall for them.
btw. there are a lot of threads about this from the 6.2.1 update
make a short search for "prevent ota update" - you'll have a lot to read ...
Click to expand...
Click to collapse
I did read a lot of that last time and I don't think I actually saw a definitively successful method. If there is one it should be stickied
My interest in this is a little different from most of you guys - I have very limited satellite internet and I don't like these unscheduled 185-meg downloads so I want to be able to update only when I want mostly to control that. This kind of means looking for the least-intrusive way to accomplish this.
/cache/update-kindle-6.2.2_D01E_3205220.bin is exactly where it downloads
if you find a way to even prevent the download, that would be greatly appreciated
Unfortunately I already got the update so I can't try it this time.
at least you could try your method with a dummy file of an other name and try to overwrite it with adb - if you can't overwrite it there's a good chance
I think I'm about the only one who prevented 6.2.1. I did it by constantly checking the cache folder. Found the update by chance and deleted it before it updated. Waited over a week for it to come back. Never did. An app that watched the cache folder for the updates and then moved/deleted them would work fine
Sent from my SGH-I897 using xda premium
jcase already work a way around this automatic OTA update, so when FIREMOD is ready to replace burrito I think we will have no more problem with this OTA issue. (you can find jcase announcement in the kindle developer section)
Heres what I have done to prevent this.
1) Droidwall (white list only the apps you want to allow internet access)
2) Removed "otacerts.zip" from /system/etc/security/otacerts.zip.
3) I removed "OTASilentInstall.apk" /system/app
4) Installed this 6.2.2 based Rom http://forum.xda-developers.com/showthread.php?t=1439916
Hopefully this eliminates the OTA. I had my Fire rooted on 6.2.1 with twrp and it OTA'd on its own, broke root and twrp. So I rerooted with burritoroot2 and installed CWM based recovery.
Hi!
I'm trying to enable Ad Hoc mode on an Acer A500 running OTA ICS. I installed the Acer USB drivers; rooted it with blackthund3r_ICS_Root 6.0; checked it with Root Checker Basic; installed ADB on my Win7 PC; and checked that "ADB devices" reponds with a device ID; and obtained the WPA_supplicant file mentioned in this thread: http://forum.xda-developers.com/showthread.php?t=1625962
Every time I try to copy the new WPA_supplicant file to /system/bin, it fails. Also, copying WPA_supplicant with Root Explorer fails, even with the partition mounted RW.
Help! What am I missing?
TIA.
tlyonstlyons said:
Hi!
I'm trying to enable Ad Hoc mode on an Acer A500 running OTA ICS. I installed the Acer USB drivers; rooted it with blackthund3r_ICS_Root 6.0; checked it with Root Checker Basic; installed ADB on my Win7 PC; and checked that "ADB devices" reponds with a device ID; and obtained the WPA_supplicant file mentioned in this thread: http://forum.xda-developers.com/showthread.php?t=1625962
Every time I try to copy the new WPA_supplicant file to /system/bin, it fails. Also, copying WPA_supplicant with Root Explorer fails, even with the partition mounted RW.
Help! What am I missing?TIA.
Click to expand...
Click to collapse
You're not missing anything. The root method, does not give you true 100% System R-W access. Not with the stock bootloader. What you can try,
Copy your wpa file to the internal memory (remember where it is) (also long press and select copy)
Then run the included app "a500 Remounter" and select the System R-W option. (this was installed when you rooted) Then quickly go to your file manager, and set /System to R-W and try to paste your wpa file there.
You;ll have to play with this to get it going. Might have to do it a couple of times. This was a big pain, as I had to be very quick when doing things, as the R-W went away quickly.
I know you tried this a couple of times, but try it again. Also, make sure you;re using his version6 root app. It's a little better.
It's the reason why I moved to the ver3 hacked bootloader&kernel combo.
Your R-W usually goes away after you close the file manager app.
Hurray!
Thank you Moscow Desire. Being quick seems to have done the trick.
But here's a tip for others: Es File Explorer, in spite of claiming otherwise, doesn't seem to allow changing file permissions.
tlyonstlyons said:
Thank you Moscow Desire. Being quick seems to have done the trick.
But here's a tip for others: Es File Explorer, in spite of claiming otherwise, doesn't seem to allow changing file permissions.
Click to expand...
Click to collapse
Yeah, another one that doesn't work well with the stock bootloader/root method is File Explorer HD. It just plain refuses. (hadn't used ES FE in a long time, so completely forgot about that one). Root Explorer is a little more reliable.
Glad you got it changed.
Also, when I was running stock and ver2 bootloader, I noticed I had to run the root program again to get R-W. Doesn't hurt anything, just had to run it again. But with ver3 bootloader w/altered boot.img, no problems. All explorer programs seem to work like they should.
Moscow Desire said:
Yeah, another one that doesn't work well with the stock bootloader/root method is File Explorer HD. It just plain refuses. (hadn't used ES FE in a long time, so completely forgot about that one). Root Explorer is a little more reliable.
Glad you got it changed.
Also, when I was running stock and ver2 bootloader, I noticed I had to run the root program again to get R-W. Doesn't hurt anything, just had to run it again. But with ver3 bootloader w/altered boot.img, no problems. All explorer programs seem to work like they should.
Click to expand...
Click to collapse
Hmm I'd never had to rush to get remounted rw and having to press it in root explorer is a bug in RE. If you remount rw from cold THEN load Root Explorer it will show /system as already mounted rw
Sent from my Iconia A500 using Tapatalk 2
blackthund3r said:
Hmm I'd never had to rush to get remounted rw and having to press it in root explorer is a bug in RE. If you remount rw from cold THEN load Root Explorer it will show /system as already mounted rw
Sent from my Iconia A500 using Tapatalk 2
Click to expand...
Click to collapse
Maybe on some systems it does. I brought this up a few weeks ago. Maybe it's tablet specific.
After a week or so, the Remounter failed to change System to R-W. It claimed it did, but Root explorer still showed R-O. You couldn't change it. No other changes were made to the OS.
Ver6 did the same under ver2 bootloader with stock kernel. You had to be quick to do the changes, as the other user said. It's not a fluke.
Other known oddities,,,
File Explored HD would not recognize it. Failed to change System to R-W, Updating to Ver3 BL and kernel fixed this.
Of course it's a damn fine tool. It works well for most people. And we're thankful you take a part in development. Wish more would get involved.