Database Users

FroYo Freezes fix

Use with 2.0.54 only, root is not yet available with 2.0.71
disclaimer: swap IS evil, you don't want it! Swap is a dirty workaround for crappy hardware (well somekind of) ... Don't complain if you put a swapfile on your internal memory (the 8 or 16GB flash disk) and it will stop working. Swap read and write like hell, so if you want to try it, please use an external disk, like usb, or better: micro SD. And of course i'm not responsible for anything ...
a) download http://hitme.resetbutton.de/priv/swapfiles.zip
b) unzip it somewhere on your PC
c) pick what you want ... i prepared a 128, 256 and 512MB swapfile in it. It might be smart to start with 256MB
d1) connect to your PC and use the dropdown area (on the Archos notification bar) to enable file transfers
d2) on my system the sd card is mounted on windows as "removable disk" .. the internal is A101IT, so if you have a sd card use "removable disk"
d3) transfer the file (the size you want, or all) to your Archos device, as i said: internal memory might be a bad idea, use a sd card
d4) on a windows system use the "safe remove hardware" or whatever it's called and unmount the disk form the archos. After that, on the archos at the orange Android screen: click the button
e) use z4root to root your device temporarily ( you can find it here: http://forum.xda-developers.com/showthread.php?t=833953 or google for z4root)
f) use the first option in z4root! a permanent root will not work (at the moment). If it's not working: enable USB debugging AND connect it to a PC
g) download a terminal if you haven't so far. Search in the market for "terminal emulator"
h) start the terminal and enter: su
at the first time you will get a request that you really want it. If you don't get it: root didn't work, happens sometimes. Power off your device and try again at e)
i) locate where you put your swapfile ... it should be /mnt/storage/sdcard, or if you don't have a sd card: /mnt/storage
j) go into the directory by typing: cd /mnt/storage/sdcard ... or cd /mnt/storage (without a sdcard)
you can list the content of the directory with: ls
k) type: swapon swap256
or the file you copied (swap128, swap256, swap512)
l) type: free
you should now see that you have swap memory
m) report back which file works best for you!
This will now work until you reboot your device. If you do: start again at e) .. of course you don't have to download z4root or the terminal again, so it's:
root with z4root
start terminal and enter su
goto the directory where the swapfile is (cd something)
swapon swap256 ( or whatever you used)
control with: free
done
WARNING: if you use a swapfile, which is described here, you can't use a usb connection to copy files without doing this:
start the terminal, enter: su
go to the directory where the file is ( cd /mnt/storage/sdcard or /mnt/storage) and do:
swapoff swap256 (or whatever you used)
This mini howto is for a swapFILE ... the advantage is that you don't have to make new partitions on your sdcard, but it might be a little bit slower than a swapPARTITION. If i have more time i will wikify this and extend it with the partition part ...
Credits go to http://forum.archosfans.com/viewtopic.php?f=74&t=42718

Is there any way to make that into a script that can be run during boot?
Also - you can download terminal emulator from Archos Aps and no root required.

impossible without perm root (we cannot modify root fs, so no chance for boot scripts...)
wait for SDE and custom roms

You can only use this while temp rooted (to use the command swapon), also, there should be NO reason why you should be rebooting anyway...

I tried this successfully in my Archos 101 but using the Internal Storage, not the SD card itself. I ran it for 3 hours straight opening very heavy stuff. It solves the stability issue, now my 101 doesn't hang when I open too much stuff.
My only concern is that the swap file operation may shorten the lifespan of the media because such media usually has a finite number or write operation cycles to it.

Just enabled a swap512 on a spare sdcard i had. Initial impressions is... WOW this thing flies! Apps are just popping open now with no lag and flicking screen to screen is almost instant. Will report back on the stability after I've had a chance to play with it but THANK YOU OP!!

Use a fairly good MicroSD card with it, high read/write cycles on it. It will last longer then.

Wow this worked great. My system is flying.
A put the 512 on an 8gb sd card.
I opened dolphin with 8 tabs, angry birds seasons paused after playing no problem. Then opened regular angry birds and played that with all others still running. No issue.
I also have music playing in the background.
I opened the my piano ap and played that with all others in the background.
Works just perfectly.
Here are my memory stats under free
used: 242148 free 2604
swap
used: 143652 free 380628

I'm going to try this too... once I got the archos rooted again... z4root isn't very reliable to be honest. Currently it's not working 90% of the time. But that's another issue in another thread.

Working fine too... I'm using launcher pro, started some apps, played angry birds seasons and yet no freeze.
Firefox beta was unusable without swap, now working like a charme. I'm checkin on Dolphin HD next.

Works great, put a 512swap on my 8 gb micro sd and no freezes anymore

Really Fix Freeze problem, it look smooth now...
Why ?

7895123 said:
Why ?
Click to expand...
Click to collapse
because it doesn't run out of memory.

Memory management isn't too good with our stock froyo because it doesn't end applications when it should.
Sent from my HTC Legend using XDA App

Thank you very much. I will try on my Archos 101IT

This will not work with the newest firmware as temp root no longer works. However, the improved CPU and memory management should compensate for that.

true. z4root closes unexpectedly (=crashes).
so far no freezes with new firmware

chulri said:
true. z4root closes unexpectedly (=crashes).
so far no freezes with new firmware
Click to expand...
Click to collapse
Not true. I'm on the latest firmware, running Z4Root temp rooted, and swapping 512. Not sure why it'd not working for you guys.
EDIT: I didn't see the latest posted in the forum. I'm still on 2.0.54, not the newest

I have already tried on microSD and found it work fine.
#free
total used free shared buffers
Mem: 244048 240692 3356 0 5260
Swap: 262136 0 262136
Total: 506184 240692 265492
Archos 101 - 16 GB + microSD 8 GB setCPU max: 1000 min 800

Did you upgrade from 2.0.54 or did you do a wipe/reflash?
aamon17 said:
Not true. I'm on the latest firmware, running Z4Root temp rooted, and swapping 512. Not sure why it'd not working for you guys.
Click to expand...
Click to collapse

[Q] Way to access mounted SD card through windows?

As the title suggest, looking to see if its possible to read/write to the mounted sd card while its plugged into the Iconia Tab from my Windows file manager.
about 4 months ago i found an old Sandisk sansa at work, no one claimed it so the manager in charge of lost and found gave it to me tonight. Its a fairly old model, but it had an 8gig Transcend micro sdhc in it. its loaded with nearly 7 gigs of music. Id like to back up the contents and then wipe the card.
Also, is there a way to test the cards read/write speeds from the tab? i saw Sd Tools but it only tries to speedtest the internal memory with no option for switching to the external_sd.
Or, am i going to have to buy one of those little card readers for USB slots?

@Grimcreaper - you could look at this method I posted back in July. It's simple and it works. But I'll be honest for simplicity I prefer using a usb card reader, I know it's a nuisance taking the sd card in and out but virtually nothing can go wrong while you are using it.
Try this simple method
For anyone who wants to see the contents of their sd card on their PC and be able to copy/transfer files from one to the other, why not give this a try, it is very simple and works for my A500.
Before you start you need your A500 to be rooted and you need "USB Mount All version 1.3" from the Market cost $1.99
(1) Have your PC switched on, don't connect your A500 yet but switch the A500 on.
(2) Run USB Mount All and you will see your sd card as a "Device" named "ext_sdcard".
(3) Press the tab "Mount" next to your ext_sdcard. You will see two messages "Mount has been granted Superuser permission" and "Device successfully mounted".
(4) Press the "Menu" tab in the top Right hand corner of the screen, this opens a small box entitled "Settings". Press on "Settings" and you get 3 options, make certain all 3 options are ticked, ticking them if they are not. (The important thing is to have "Mount on Bootup" ticked"). Press the Back Arrow twice to get back to Home Page or where ever you started from.
(5) Re-boot the A500 and after it is back running connect it to your PC using mini usb connector.
(6) Now check your PC and open Windows Explorer, you will find under your A500 Device most of the folder/directories that are in /mnt/sdcard (which isn't all that relevent to this) BUT importantly you will find a folder/directory entitled "ext_sdcard" which for those of you who noticed is the exact name that "USB Mount All" called your sd card.
(7) Now use Windows Explorer to copy and paste whatever you want into the "ext_sdcard" folder.
(8) Please note that when you start to copy files you will get up a warning box stating "Do you want to copy XXXXX to your device?". You are given 2 choices (1) No skip this file or (2) Yes.
(9) Put a tick in the box at the bottom Left and click on "Yes".
(10) When finished safely disconnect your A500 from your PC and re-boot your A500.
(11) After re-boot go back into "USB Mount All", chose top Right menu and settings box and remove the tick from the 3rd option "Mount on Bootup". Each time you are going to copy, move or delete files first of all put the tick back in the 3rd box and when you're done take it out.
Your Done. If you use any File Explorer to look at /mnt/external_sd you will see all the files residing on your sd card including those you've just copied

DroidExplorer

Just wait for or load one of the 3.2 based roms...

Thank you guys for your answers

Yes you can!
I'm using the virtuous galaxy room and it's under the storages file» sd» mmcblk1 and there you go. Way easier than pulling the card out every two seconds

@Grimcreaper - Further to what I originally posted, I have to apologise and endorse what "verdigny" posted. "DroidExplorer" is IMO the best and easiest way of achieving your goal. I must blame an early onset of Alzh or alternatively too many visits to the bottle for forgetting that I in fact have DroidExplorer on my PC and it does everything you want so easily. Back in July when I posted my screed I hadn't seen or downloaded DroidExplorer and that is why I worked out that painfully long and convoluted system.

Thanks again for more info would have responded sooner but ive been stuck working some killer hours right before my vacation kicks in.
Another question, anyone know how to test the speed of the micro sd card?
I found 1 app but it only works for phones i think as it only shows the tabs internal memory with no options for doing an external sd card source, cant remember what its called as i uninstalled it
trying to find out if its worth using on my tab or if its to slow.
Gonna edit this again, appearently i didnt fix it. BusyBox doesnt want to work on my tablet now. says its not rooted and wont install it. so im lost
Went into SU and had it "forget" the busybox installer, but its bringing up a lot of things it didnt the first time i installed it..
Is there anything to worry about with an install of busybox? is it easy to remove if i need to for updating the tablet or anything once i remove SU access? all of these warnings have me a bit scared since im a total noob with android devices but being able to access the sd card constantly through the tablet from windows would make things a lot easier

@Grimcreaper - can't help with sd card speed, a bit out of my league. As far as "BusyBox" is concerned may I make the following comments. I presume each of the following statements are true.....(1) you are using the stock/standard Rom and Kernel (2) you have rooted by using Iconia Root [ v1.1 or v1.2 or v1.3] (3) you are on Honeycomb 3.1 (4) you use "RootChecker" free from MktPlace (5) you used "BusyBox Installer" free from MktPlace.
I am not an expert but in your position my "path" would have been......(1) Root the A500 (2) Apply BusyBox Installer (3) Install RootChecker. Assuming Rooting goes ok you should have no problem installing BusyBox and then use RootChecker which in it's "Advanced" mode will confirm your Root was successful and will also confirm successful installation of BusyBox. By installing BusyBox, apart from anything else, you gain access to certain system/scripting/"linux type" commands such as 'cat' 'chmod' 'chown' 'clear' 'dd' 'egrep' 'ping' etc.etc.
If you need "Iconia Root" I can point you to the XDA page or can attach it to a followup post, but reading your post again I'm presuming you already have it. A small point, when it comes to updating OTA updates from Acer I found on the last update from 3.01 to 3.1 that after restoring certain "bloat" files I was able to update without uninstalling Root and at the conclusion of the update Root was still operative.
Hope I havn't missed your point and wasted your time with a load of drivel.
Quick addition - Do a search in Market for "software data cable" and look at the first 2 free apps. Haven't tried them myself but might interest you.

Checking out rootchecker now, everything else on the list is accurate.
According to rootchecker i am rooted, which i did using the iconia root 1.3 i believe some time ago to get the netflix stuff working by backing up replacing the libmonv file.
It also shows Busybox as correctly installed too, version 1.18.4

Grimcreaper said:
Another question, anyone know how to test the speed of the micro sd card?
Click to expand...
Click to collapse
find a pc program to download and check it.
here are a couple,
Crystal Disk Mark
or
HD Tach is a low level hardware benchmark for random access read/write storage devices such as hard drives, removable drives (ZIP/JAZZ), flash devices, and RAID arrays. HD Tach uses custom device drivers and other low level Windows interfaces to bypass as many layers of software as possible and get as close to the physical performance of the device possible.
The trial version of HD Tach measures the sequential read speed (at various points on the device), the random access speed, interface burst speed and CPU utilization of the drive. The registered version adds sequential write testing.

exFAT and NTFS drivers for Lenovo Yoga Tablet 2 - a solution!

I own Lenovo Yoga Tablet 2 830L, firmware "upgraded" to 830LC, rooted. I've tested the provided solution only on it, though it should work on other models, and maybe even on other devices.
I've built exFAT and ntfs-3g drivers from the most resent sources, and made a shell script, to auto-mount a microSD at the system start. Root and SuperSU are required. Currently, the installation is manual. The project is here:
https://github.com/Lurker00/Android-fs/releases
Please read the description I've written, at least "How to mount?" section, and, of course, the disclaimer.
Edit: Now it has a CWM/TWRP installation zip for easy use!

Lurker0 said:
I own Lenovo Yoga Tablet 2 830L, firmware "upgraded" to 830LC, rooted. I've tested the provided solution only on it, though it should work on other models, and maybe even on other devices.
I've built exFAT and ntfs-3g drivers from the most resent sources, and made a shell script, to auto-mount a microSD at the system start. Root and SuperSU are required. Currently, the installation is manual. The project is here:
https://github.com/Lurker00/Android-fs/releases
Please read the description I've written, at least "How to mount?" section, and, of course, the disclaimer.
Click to expand...
Click to collapse
Thanks a lot for putting effort into this! I haven't tried it yet, but I'd suggest to create an app/APK which installs the files necessary and which features some buttons for mounting and unmounting. A CWM package is not such a good idea due to the fact that we have only temporary CWM and hence installing would still be a bit painful. This app could be something like a Yoga tablet 2 toolkit, which could maybe even include my sharpness fix

I've created CWM/TWRP installation zip with exFAT and NTFS drivers, and mounting script. It can be downloaded from here:
https://github.com/Lurker00/Android-fs/releases
Now, if you have rooted your Lenovo Yoga Tablet 2 (any screen size), and have SuperSU installed, just download UPDATE-android-fs-1.0.1-install.zip, install the same way, and start using exFAT (strongly recommended!) or NTFS (not recommended!) microSD.
To safely unmount for hot unplug, use Android settings. For mount after hot plug, better to reboot your tablet.
Note: the microSD file system is checked before mounting, and, if errors are found, it is mounted as read-only. So, if you find out that you can't write to the microSD, safely remove it and check (allowing to fix errors) it under Windows. It is strongly recommended to check and fix under Windows, because both exFAT and NTFS are produced by Microsoft, and no open source software is able to correct the file system errors correctly!
I have Yoga Tablet 2 8''. But the installation zip contains binary files for a number of platforms, and may work on other Lenovo Android devices. Being manually installed, the drivers are confirmed to work on:
Lenovo Vibe Z2 Pro
Lenovo Vibe Z2
Lenovo S90
so I see no a reason why they will not work being installed via recovery console.

I almost thought my Yoga 2-850F is broken as it was impossible to mount or format any micro SD card. Even when I tried formatting the card with my android phone using various file systems (i.e. exfat, ext4 etc.), I would always get an error. Finally, just flashing the zip did the trick. Thanks for the script!

I've updated the drivers to version 1.0.2:
1. One more supolicy rule added to the mounting script. Without it, unmount from Android Settings didn't work.
I didn't put per-platform binaries this time, because the recovery zip contains them all.

I'm sorry for so frequent updates, but
exFAT/NTFS fuse drivers binaries for Android v1.0.3
The problem is that the original exFAT driver was designed to update the file system only at unmount events, but the current Android never unmounts microSD mounted not by Android's vold process Meaning, file system corruption may happen on a reboot or power off.
Version 1.0.2 partially addresses that issue, and is stable enough. Only freshly created directories can be damaged by a reboot, and only if there were no any file operations after that, i.e. a rare case. Version 1.0.3 ensures that the file system is kept consistent almost always. It can be damaged only by removing microSD card during write operation.
Nevertheless, I plan to make at least one more release, to keep microSD clean, when there are no pending writes. Also, I'd try to improve the write performance compared to 1.0.3, without a penalty of the file system consistency.

I just have released
exFAT/NTFS fuse drivers binaries for Android v1.0.4
and I can say I'm quite satisfied with both performance and robustness of the resulting exFAT driver (no changes were made to ntfs-3g). So, I believe, it is the final build for a while.

Worked perfect.
Tested and working perfect:
Tablet: Lenovo Yoga Tablet 2 Pro Android 4.4
Micro SD: Lexar 128GB (633x) Formatted to exFAT
I flashed it via temp recovery and did a reboot from recovery. Then shut down the tablet and put the exFAT card in. Booted up and not so much as a whisper. The system recognised and mounted the card without any problems.
Thanks again for your hard work.
Now to find a custom ROM. I think I've got more chance of finding rocking horse s**t than a ROM for my tablet though

Hello,
Thanks fort the work.
I have got a lenovo yoga tab 2 1050F updated tout lollipop and rooted.
Can you tell US if it is works with both KitKat ans lollipop?
Can you détail the installing methode?
Thanks in advance.

Kalachnikos said:
Hello,
Thanks fort the work.
I have got a lenovo yoga tab 2 1050F updated tout lollipop and rooted.
Can you tell US if it is works with both KitKat ans lollipop?
Can you détail the installing methode?
Thanks in advance.
Click to expand...
Click to collapse
I didn't upgrade to Lollipop myself, and I don't want to.
The driver and the mounting script are reported to work under Lollipop, but, for auto-mount on boot, they rely on /system/etc/install-recovery.sh script modified by SuperSU to launch with required privileges on system boot, which is not the case for Lollipop. It works flawlessly under Kitkat though.
You can find the detailed instructions at the github place from the link above. It's as easy as to root.

Hi,
Should this work on the Tab 2 A10-70, which has ARMv8 (Cortex-A53, MT8165 chipset)?
Looking for a sustainable solution to get exFAT working on that Lenovo device, it's a real let down it doesn't by default...
Many thanks !

You can try yourself...
There are binaries for all kinds of arm, including 64-bit. The mounting script won't work under Lollipop. But people with rooted devices and stright hands manage to make the drivers launched at right time with right options. I heard successful reports for very different devices.

Lurker0 said:
You can try yourself...
There are binaries for all kinds of arm, including 64-bit. The mounting script won't work under Lollipop. But people with rooted devices and stright hands manage to make the drivers launched at right time with right options. I heard successful reports for very different devices.
Click to expand...
Click to collapse
I'm still on kit-kat, and rooted. I've yet to install CWM/TWRP though, so that's the first step. I'm pretty limited on tech skills so that might be an issue, but I'll see how it goes ; if it's a simple zip flash then great, otherwise things may get too out of hands
If/when I get around to testing, I'll keep you posted - but in the meantime many thanks for the work on this!

Thank you for your work. It works with exfat microsd 64 go sandisk and my lenovo 1050F tablet under lollipop.
I don't know how android system works, sorry for newbie questions
I try to have my external SD mounted in R/W at launch time.
In superSU, i change the following parameter : activate su on starting to enable but it does not work.
I have read that /system/etc/install-recovery.sh is executed by super-su. I can see at the end of this shell /system/etc/install-recovery-2.sh is called but it does not mount the SD in R/W...
Any help is appreciated! Thank you.

Unfortunately, Lollipop has more protection, and it launches install-recovery.sh in a very restricted environment, not enough for the mounting script to work properly. And I don't know a way to launch my script at the boot time with required privileges under Lollipop. One of the reasons I don't want to "upgrade" my 830LC to 5.0.1!

I have a Lenovo yoga tablet 2 830LC, upgraded to Lollipop 5.0.1 recently. There are no proper root guides for the Lollipop version anywhere on the forum, and since I'm interested in rooting my device and also be able to write to the external sd card, I request you to guide me on this. I'm sorry if this isn't the proper thread for my request but would be appreciated much.

zach181 said:
Worked perfect.
Tested and working perfect:
Tablet: Lenovo Yoga Tablet 2 Pro Android 4.4
Micro SD: Lexar 128GB (633x) Formatted to exFAT
I flashed it via temp recovery and did a reboot from recovery. Then shut down the tablet and put the exFAT card in. Booted up and not so much as a whisper. The system recognised and mounted the card without any problems.
Thanks again for your hard work.
Now to find a custom ROM. I think I've got more chance of finding rocking horse s**t than a ROM for my tablet though
Click to expand...
Click to collapse
Hi.. i hv rooted and in that process flashed supersu thru temp recovery twrp... now iam not sure how to activate again twrp... any advise...thanks

Same way you did it when rooted. It is launched one time only.

mmlbbntr said:
Should this work on the Tab 2 A10-70, which has ARMv8 (Cortex-A53, MT8165 chipset)?
Looking for a sustainable solution to get exFAT working on that Lenovo device, it's a real let down it doesn't by default...
Click to expand...
Click to collapse
Yeah, it's a shame that Lenovo hasn't included exFAT support.
Read on...
Lurker0 said:
You can try yourself...
There are binaries for all kinds of arm, including 64-bit. The mounting script won't work under Lollipop. But people with rooted devices and stright hands manage to make the drivers launched at right time with right options. I heard successful reports for very different devices.
Click to expand...
Click to collapse
I love you, man! :good:
I just got your drivers to work on a Lenovo Tab 2 A10-70F running Android 5.0.1.
Yes, the install-recovery-2.sh mounting script doesn't work there, because it runs in a restrictive security context on Lollipop, if I've understood it correctly.
I flashed your update zip, noticed that it didn't work, then searched for some other options. I thought about init.d, but that isn't supported on this tablet either.
However, SuperSU, which I've already been using, offers a "su.d" mechanism, similar to init.d, and I used that to get it to run!
One needs to have SuperSU and busybox installed, and flash your update zip with a custom recovery (this one works for the Tab 2 A10-70, F & L).
Then create /system/su.d directory and move the /system/etc/install-recovery-2.sh script there. It can be named anything, I renamed it "/system/su.d/00mount_exfat_ntfs.sh".
I'm not too sure about the permissions, I used 755 for both the directory and the script.
In the SuperSU settings (accessible in the SuperSU app), the option "mount namespace separation" must be disabled.
I have a 64GB SanDisk Ultra microSDXC card, but for some reason it wouldn't want to work with exFAT on this tablet at first.
/dev/block/mmcblk1p1 did not show up while the card was inserted, only /dev/block/mmcblk1.
I formatted the card with NTFS, and that worked. I changed it back to exFAT, and then it finally did show up. Weird.
Anyway, would you recommend exFAT or NTFS, Lurker0?
I've used this card with NTFS on an older tablet, and it was rock solid, which I can't say about my experience with exFAT.
One minor caveat: the card isn't automatically mounted on insertion. Mounting requires another execution of the mounting script, either by rebooting or running "su -c /system/su.d/00mount_exfat_ntfs.sh".
Is there any way to make that automatic?
Thanks again.

Tzul said:
However, SuperSU, which I've already been using, offers a "su.d" mechanism, similar to init.d, and I used that to get it to run!
Click to expand...
Click to collapse
Thank you for finding! I'll read more and try to update my package.
Tzul said:
Anyway, would you recommend exFAT or NTFS, Lurker0?
Click to expand...
Click to collapse
NTFS is not flash-friendly, so I believe exFAT is better.
Tzul said:
Is there any way to make that automatic?
Click to expand...
Click to collapse
It requires to write an application to watch for system mount events and run that script. I'm lazy to do it

Transferring of Kodi Setup from PC to FireTV Stick

Hello everyone,
I am kind of new to Kodi and FireTV Stick but already fell deeply in love with all of it’s features. Last week I installed a MegaPack for Kodi which comes with all the repos and addons already installed. Really love it but I guess that this image I installed can be stripped down to reduce size and overall hardware needs.
The instructions to install the MegaPack required a 1 GB download and adbfire. In adbfire with the help of the restore button the whole extracted “MegaPack.zip” was copied to the FireTV Stick and everything worked fine.
Now yesterday I tried the following: I installed Kodi on my Laptop, installed the same MegPack (which in case of Windows just requires to copy all the folder to C:/Users/xxx/AppData/Roaming/Kodi) and made some changes. These changes I then copied again with the help of adbfire to the stick and voila it worked…
To keep it short my question is the following: Is my described procedure “good”? I really love the ease of setting up Kodi on the PC and push the files to the stick. With help of mouse and keyboard the setup process is much more convenient. I am just not sure if this might lead to technical problems. Anybody can tell me if I was lucky with my try yesterday or that this is a perfectly fine way to do it? The addons on Kodi for Windows and FireTV Stick are the same?
Thank you very much in advance and happy Kodiing

Thanks Anhaussner for the information!
Could please post the download link for the MegaPack for Kodi that you have installed?
I also would like to know how to install this MegaPack and on which folder you will have to copy all these files?

anhaussner said:
Hello everyone,
I am kind of new to Kodi and FireTV Stick but already fell deeply in love with all of it’s features. Last week I installed a MegaPack for Kodi which comes with all the repos and addons already installed. Really love it but I guess that this image I installed can be stripped down to reduce size and overall hardware needs.
The instructions to install the MegaPack required a 1 GB download and adbfire. In adbfire with the help of the restore button the whole extracted “MegaPack.zip” was copied to the FireTV Stick and everything worked fine.
Now yesterday I tried the following: I installed Kodi on my Laptop, installed the same MegPack (which in case of Windows just requires to copy all the folder to C:/Users/xxx/AppData/Roaming/Kodi) and made some changes. These changes I then copied again with the help of adbfire to the stick and voila it worked…
To keep it short my question is the following: Is my described procedure “good”? I really love the ease of setting up Kodi on the PC and push the files to the stick. With help of mouse and keyboard the setup process is much more convenient. I am just not sure if this might lead to technical problems. Anybody can tell me if I was lucky with my try yesterday or that this is a perfectly fine way to do it? The addons on Kodi for Windows and FireTV Stick are the same?
Thank you very much in advance and happy Kodiing
Click to expand...
Click to collapse
Only thing is that the two file systems are different, you need to change the file system on the fire stick, one of the maintenance programs can change it for you, download "The Community Portal" & goto mantenance/advance settings & then select "convert physical paths to special" this will fix the file system to Android from the Pc version. If you need to install this install it from File manager/add sources & type in- http://noobsandnerds.com/portal
then name it what ever you like & select ok, then install from zip, not go to programs & open it.
Hope this helps If so hit that like button

Ideally, I would install the build on the Fire Stick, tailor it to your requirements (stripping out the add-ons you don't want etc) and then performing a backup via ADBfire. You'll then have a build perfectly set up to restore to any new Fire Stick using only the "Restore" feature also in ADBFire. It would be the cleanest method to do it.
For example, I do the same for my builds. However, I applied the same restore to the Fire TV, and while most things worked some did not (and there shouldn't be that much variation between the Fire Stick and TV.)

QUESTION= Root so I can write Access to Removable drive?

Hi all. Only reason I am thinking of rooting my Shield TV is so I can write to my removable drives. From my understanding is that SDFix does not work with marshmallow. Is this correct? I Would love to access my non adoptable drive from my network. Or if rooted, can i also use FTP to read and write? Thank you.

robjbw said:
Hi all. Only reason I am thinking of rooting my Shield TV is so I can write to my removable drives. From my understanding is that SDFix does not work with marshmallow. Is this correct? I Would love to access my non adoptable drive from my network. Or if rooted, can i also use FTP to read and write? Thank you.
Click to expand...
Click to collapse
Hope this helps... looks like newest update on 1/18/17 (v5.0.1)
"Other Enhancements
*Added ability to write to attached USB or SD card storage."
forums.geforce.com/default/topic/988354/shield-tv/shield-experience-upgrade-5-01-feedback-thread-for-shield-2017-/

I assume you mean network access to the attached storage
SHIELD TV Gen. 2015
write access was, for me, only possible through root and a SMB/samba server.
Root via http://download.chainfire.eu/supersu from chainfire
SMB server via https://play.google.com/store/apps/details?id=com.icecoldapps.serversultimate + https://play.google.com/store/apps/details?id=com.icecoldapps.serversultimate.packb for a native SMB server, normally i use a FTP-server like https://play.google.com/store/apps/details?id=lutey.FTPServer but was not able to get it running on the shield
SHIELD TV Gen. 2017
As of 5.0 i was not able to write to the storage
Actual there is no way to root the 2017 and therefore no SMB server.
The bootloader was updated and ca be unlocked but does not allow to flash the recovery, even if it tells you so (fastboot).
Android 7 recognize a manipulation and reflashes the stock recovery
But i am not sure if 5.0.1 added the network write access storage feature.

robjbw said:
Hi all. Only reason I am thinking of rooting my Shield TV is so I can write to my removable drives. From my understanding is that SDFix does not work with marshmallow. Is this correct? I Would love to access my non adoptable drive from my network. Or if rooted, can i also use FTP to read and write? Thank you.
Click to expand...
Click to collapse
Assuming we're talking a 2017 Shield, I actually managed to access my non-adapted storage over FTP. Without root.
I have a 5TB external HDD hooked up to my Shield, and sideloaded an FTP app. I set my external HDD as root-folder for said app, and could both read/write to it (most recent software update, 5.0.1). I wanted easy management/streaming from my PC though, so I installed WebDrive so I could mount the FTP server as a local drive.
Works like a charm, can post a how-to if required.

Radnu said:
Works like a charm, can post a how-to if required.
Click to expand...
Click to collapse
Yes please!

twe69 said:
Yes please!
Click to expand...
Click to collapse
Updated: We still need FTP to write to an external, non-adopted storage. Viewing can be done over SMB though!
Alrighty then, here goes nothing, please do keep in mind the "fix" you'll find down below is a quick and dirty one. It will allow you to both read and write to your external storage over FTP, without actually needing to have root.
Requirements
1. Sideload Launcher by Chainfire
2. A file manager, preferably with cloud access. I prefer X-plore myself.
3. FTP Server by The Olive Tree (others may work, your mileage may vary).
4. Any FTP client to access your shiny new server.
Step 1
- Install the Sideload Launcher if you haven't done so yet, it will allow us to open APKs that weren't designed for AndroidTV. You can just grab it from the PlayStore.
Step 2
- We're going to need an APK from FTP Server. The easiest way so far seems to be to install it on another device (in my case, my trusty Note3), and "backup" the APK to your Google drive using X-plore as you can see *here*.
- After we've gotten the APK there, hop back to the Shield and open X-plore. Go to your Google drive and install the FTP Server we just put there.
Step 3
- Use the Sideload Launcher to open our FTP server and set it up. Tapping your D-pad "up" once gets us to the settings of the app. Open it, and scroll down till you're looking at something like *this*.
- Most of these settings are up to your own discretion, but I strongly advice to untick "anonymous login" and set a username/pw. The most important bit is to set the home-directory to your non-adapted HDD.
- Close the settings, and tap your D-pad "down" once. Click [ A ], and we should get a nice green icon saying we're up and running! Should be something like *this*.
- The app will "survive" Sleep-mode, but after a restart you'll have to toggle it on again.
Step 4
- Profit!
- You should be able to access your FTP server on your specified local port, and using WebDrive you can even access it easily on a PC. It'll look something like *this*.
- You can use your regular SMB share to view your files over your local network, the catch is that you'll need to use FTP to write to it.
Final note!
It looks like setting X-plore as "default handler" for the non-adapted storage makes it disconnect from your shield. Don't tick it!

I read that writing to the external usb HDD is now fixed in the latest update v5.0.2?
In which case enable the following Settings > Device > Storage & reset > SHIELD storage access > Over local network > On and map the drive to the laptop.
Is this correct? I need to test it out still.

twe69 said:
I read that writing to the external usb HDD is now fixed in the latest update v5.0.2?
In which case enable the following Settings > Device > Storage & reset > SHIELD storage access > Over local network > On and map the drive to the laptop.
Is this correct? I need to test it out still.
Click to expand...
Click to collapse
Don't think so yet. I *can* view and play it, but can't write to it. Screeny over here: imgur,com/ieuhlB0

Any one have luck with this yet? Really hoping to be able to write easy to the external storage.

candymann said:
Any one have luck with this yet? Really hoping to be able to write easy to the external storage.
Click to expand...
Click to collapse
As I explained above, you actually can write to it using FTP (non-adopted storage, no root required whatsoever). Currently I would just advice using the regular SMB share to view it on other devices (since you don't want to download anything before viewing).
I've edited the instructions to clarify.

Here is something I discovered. When you hook up a USB flash drive or HD, it creates some folders on that drive. Android nvidia shield(something like that)
The nvidia folder it creates is writable. I am using a flash drive as non adoptable to play ROMs on with emulators. On the root of the drive I had issues. But once I moved my ROMs folder inside the nvidia folder all was well. No my emulators can load the ROMs from the nvidia folder created on the drive and write the save files to the same folder the ROMs are located in.
Hope this helps. Only issue is that when u restart, you get the annoying pop up asking to adopt the drive. I just hit browse each time.. Because I don't want to adopt it.. I just want it to store files..
Android went plum retarded post kitkat with drives and SD cards and write permissions.. Its very annoying and makes me long for the good OK days where u could just insert something and do with it slas you please... In my opinion they have over complicated what should be a rather simple procedure.. But it looks like this is the direction they have choose..

adam_ky said:
Here is something I discovered. When you hook up a USB flash drive or HD, it creates some folders on that drive. Android nvidia shield(something like that)
The nvidia folder it creates is writable. I am using a flash drive as non adoptable to play ROMs on with emulators. On the root of the drive I had issues. But once I moved my ROMs folder inside the nvidia folder all was well. Now my emulators can load the ROMs from the nvidia folder created on the drive and write the save files to the same folder the ROMs are located in.
...
Click to expand...
Click to collapse
Checked this and the [\\SHIELD\ExternalStorage\NVIDIA_SHIELD] folder is writable over SMB indeed.
Now it's just a matter of whether or not you're willing to put up with the popup.

Hope that helps ya. The android folder is most likely writable as well.
I remember this work around when lollipop came out and apps were not built with the proper permissions. You could use the apps folder in android on the SD card to circumvent this.
But yea I'm good for now just using the shield folder on my flash drive... I do wish there was a way to remove the popup on boot asking to adopt storage though....
I'm beginning to loathe nougat....
The later android versions are hardly usable for me without the use of xposed.
Anyways, hope that trick helps you and anyone else

If you have root couldn't you just mount the drive as writeable using a file explorer? I'm interested in writing to a removable drive in general (don't care about network access specifically).

Any news here?
I am on Nvidia Shield 2017 with 8.0.1 rooted.
I can only READ my attached NAS (network storage).
But I want to get WRITE access too
The workaround with the NVIDIA_SHIELD folder did not work... And Apps like SDfix ends up in error ??!
I own two Shields and need them to write to my NAS.
Does anyone can help me how to get this working?
Both Shields are rooted
Anyone know, if THIS is still actual? (4 years old)
Thank u very much

Kamikaze01 said:
Any news here?
I am on Nvidia Shield 2017 with 8.0.1 rooted.
I can only READ my attached NAS (network storage).
But I want to get WRITE access too
The workaround with the NVIDIA_SHIELD folder did not work... And Apps like SDfix ends up in error ??!
I own two Shields and need them to write to my NAS.
Does anyone can help me how to get this working?
Both Shields are rooted
Anyone know, if THIS is still actual? (4 years old)
Thank u very much
Click to expand...
Click to collapse
Same setup as you. I have been searching everywhere on a way to do this and no luck.