Last night I unlocked the boot loader and rooted my Nexus 7. Today I installed Stick Mount and plugged in a 500GB WD external hard drive. The drive powered up fine and Stick Mount appeared to mount it successfully. What confused me was unmounting it. When I selected unmount, it came up still listing the drive as an active mount. I was expecting it to say no devices or something like that if it unmounted. To make things easier, I selected a 4GB Kingston flash drive. I formatted it to EXT4 on my Ubuntu 12.04 laptop and then utilized that on my Nexus 7. The same thing happened. It appeared to not unmount, but each time I selected unmount it just said active mounts with the device listed.
I explored it via Astro File Manager. As expected I saw a folder that populated in /sdcard/usbstorage/sda1. Okay, fine. But explain this to me. How is it that when I put files on the flash drive on my laptop, then mount it on the N7, it doesn't show up? Likewise, if I add files to it, then plug it in the laptop, the N7 files I added don't show up, yet the files I originally added on the laptop do?
AKA:
Files added to the 4GB flash drive via N7 are only accessible when plugged into the N7.
Files added to the 4GB flash drive via laptop are only accessible when plugged into the laptop.
I do not see the laptop files when plugged into the N7, and I do not see the N7 files when plugged into the laptop. It's as if each device is handling its own bit of storage yet it's the same exact flash drive... so how is this possible?
Likewise, does the tablet do any sort of caching? When I saw that the flash drive wasn't unmounting as I expected, I simply pulled the flash drive out of the tablet. To my surprise, I was still able to successfully create new directories on it. I was also able to launch jpg images (of course, ones that I originally copied to the flash drive from my N7) and view them accordingly. How is this possible if the device in question was not mounted?
Thinking it may be permissions related, I plugged in the flash drive to my laptop and issued a chmod -R 777 to it (allowing owner, group, and all others to have full read/write/access). I figured I'd open the permissions wide and see what happens, then throttle them back if necessary. But even when I 777'd the drive, the same behavior took place.
I have no doubt Stick Mount is fantastic based on the magnitude of positive reviews and discussion I've heard, but what is it that I'm doing wrong? Can anybody explain the behavior I'm seeing?
So after some tinkering around, it seems like it's an issue with the file system. ext3 and ext4 do not show the contents of the flash drive, even if I 777 them recursively from my Linux system. HOWEVER, FAT32 works perfectly.
But.. I really don't want to use FAT32 due to the 4GB limitation. I thought I heard countless times ext3 and ext4 worked fine??
First off completely wrong section..
Anyway you can use NTFS file system & try motleys kernel.
fOmey said:
First off completely wrong section..
Anyway you can use NTFS file system & try motleys kernel.
Click to expand...
Click to collapse
My apologies. Stick mount = apps, and this is themes and apps, hence my assumption this would be acceptable.
NTFS is all well and good, but I really don't see the point in using it. I use Linux on almost everything at home, and Android being heavily Linux based suggests there's no reason for EXT not to work... especially when other users are reporting it works fine.
Can anybody utilizing EXT based file systems comment?
JaSauders said:
My apologies. Stick mount = apps, and this is themes and apps, hence my assumption this would be acceptable.
Click to expand...
Click to collapse
By that logic, we wouldn't even have a Q&A section. What are you ever going to have a questions about other than themes, apps, accessories, android development, or "general android"? The point isn't whether or not it COULD fit in this section. The point is what section does it best fit in? For questions about ANYTHING, the post always goes in Q&A.
Have you tried the usb otg helper app rather than stickmount? http://forum.xda-developers.com/showthread.php?t=1588940 install v4 see if that helps, i found that i had to uninstall stickmount to get it to work with my ntfs thumbdrive, it may help you out with ext im not sure, but it works wonders with read/writing to ntfs...
MWBehr said:
By that logic, we wouldn't even have a Q&A section. What are you ever going to have a questions about other than themes, apps, accessories, android development, or "general android"? The point isn't whether or not it COULD fit in this section. The point is what section does it best fit in? For questions about ANYTHING, the post always goes in Q&A.
Click to expand...
Click to collapse
Hey, mods can move it as necessary. Until then, I apologize that what seemed like logical thinking caused such a tiff with some users here. It'll be all right. :good:
_DrG_ said:
Have you tried the usb otg helper app rather than stickmount? http://forum.xda-developers.com/showthread.php?t=1588940 install v4 see if that helps, i found that i had to uninstall stickmount to get it to work with my ntfs thumbdrive, it may help you out with ext im not sure, but it works wonders with read/writing to ntfs...
Click to expand...
Click to collapse
Hm okay. I was not aware. Appreciate the helpful response! I'll take a look at it.
Well I kept tinkering with it this evening but I didn't really get anywhere. I did manage to copy some files to the Ext4 flash drive with what seemed to be without issue. I was able to view the files just fine on the tablet. However I wasn't able to unmount the drive. Each time I selected it I just got continual messages listing the active mounts. I ended up getting frustrated and pulled the flash drive since it wasn't un mounting anyway. What was weird is it still had files listed in the directory... I assume they were cached somehow. It was acting as if it was still plugged in. Hmm...
Well, it sounds like fat32 is as good as it (sadly) gets... no?
JaSauders said:
Well, it sounds like fat32 is as good as it (sadly) gets... no?
Click to expand...
Click to collapse
or...
fOmey said:
Anyway you can use NTFS file system & try motleys kernel.
Click to expand...
Click to collapse
Sent from my Nexus 7 using xda app-developers app
kboya said:
or...
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
http://forum.xda-developers.com/showpost.php?p=28122498&postcount=107
*head explodes*
JaSauders said:
Well I kept tinkering with it this evening but I didn't really get anywhere. I did manage to copy some files to the Ext4 flash drive with what seemed to be without issue. I was able to view the files just fine on the tablet. However I wasn't able to unmount the drive. Each time I selected it I just got continual messages listing the active mounts. I ended up getting frustrated and pulled the flash drive since it wasn't un mounting anyway. What was weird is it still had files listed in the directory... I assume they were cached somehow. It was acting as if it was still plugged in. Hmm...
Well, it sounds like fat32 is as good as it (sadly) gets... no?
Click to expand...
Click to collapse
As soon as I read your post I was going to recommend USB OTG Helper but _DrG_ beat me to it.
Anyway, I have had times where, even with USB OTG Helper, I would unmount the drive but it would still show up. The only way I could fix it was to reboot. And after that, things usually work better. And I recommend you delete Stickmount, because it's trash, and use USB OTG Helper. It is much better, because it supports read and write of NTFS drives, where stickmount only mounted NTFS read only.
mvmacd said:
As soon as I read your post I was going to recommend USB OTG Helper but _DrG_ beat me to it.
Anyway, I have had times where, even with USB OTG Helper, I would unmount the drive but it would still show up. The only way I could fix it was to reboot. And after that, things usually work better. And I recommend you delete Stickmount, because it's trash, and use USB OTG Helper. It is much better, because it supports read and write of NTFS drives, where stickmount only mounted NTFS read only.
Click to expand...
Click to collapse
It has NTFS read/write support? Why does it only say NTFS read support available? Likewise, it says BusyBox not found, but BusyBox is installed....
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
JaSauders said:
It has NTFS read/write support? Why does it only say NTFS read support available? Likewise, it says BusyBox not found, but BusyBox is installed....
Click to expand...
Click to collapse
Hm, that's strange. And about "NTFS read support available" I don't remember if it says that on mine, [it's upstairs and I don't feel like running up there this second] but I am pretty sure it does. I believe the reason it's not working is busybox isn't being found..
I'm not sure why it can't find busybox, what location did you install it to?
I installed mine to /system/xbin/, and not /system/bin/
Anyway if you can't get it to work, I'm sure the dev would be glad to troubleshoot it if you send the debug info [From the menu of the app].
All I can say is it's the only possible way, so far , [including ROMs] that I've found that lets me write to NTFS, and it works greaet for me, so it's an important app for me.
Can you format it as ext2? I'm not as up to speed on Linux as I should be so I'm asking more out of curiosity than anything else.
Sent from my SGH-T959V using xda app-developers app
putsometrebleinit said:
Can you format it as ext2? I'm not as up to speed on Linux as I should be so I'm asking more out of curiosity than anything else.
Sent from my SGH-T959V using xda app-developers app
Click to expand...
Click to collapse
Tried that, no dice either.
mvmacd said:
Hm, that's strange. And about "NTFS read support available" I don't remember if it says that on mine, [it's upstairs and I don't feel like running up there this second] but I am pretty sure it does. I believe the reason it's not working is busybox isn't being found..
I'm not sure why it can't find busybox, what location did you install it to?
I installed mine to /system/xbin/, and not /system/bin/
Anyway if you can't get it to work, I'm sure the dev would be glad to troubleshoot it if you send the debug info [From the menu of the app].
All I can say is it's the only possible way, so far , [including ROMs] that I've found that lets me write to NTFS, and it works greaet for me, so it's an important app for me.
Click to expand...
Click to collapse
Uhh.. no idea. I just kind of clicked install, and it did its thing. I didn't do anything out of the ordinary.
Related
I was wondering if anyone is interested in beta testing this app. It will scan for all usb drives attached and give you a list to mount or unmount. It supports ext2, ext3, ext4, fat32 and ntfs.
The app will support up to 50 devices, i'm not sure how many the tablet can handle though.
* Requires root and busybox.
EDIT: APK updated on May 29, 2011 12:39 PM CST (v1.1 beta 2)
EDIT: APK updated on Jun 2, 2011 07:54 PM CST (v1.1 RC1)
This looks and sounds interesting
Sent from my A500 using Tapatalk
its said: unparseable date and then nothing worked...had to restart...always crashes....not working for my device
Eek..that doesn't sound good. As soon as it launches before you get any layout or toast Messages?
Edit: ah..bet its a locale issue. Let me research it when I get back home. I was about to starve myself while coding this.
Sent from my A500 using Tapatalk
Euclid's Brother said:
Eek..that doesn't sound good. As soon as it launches before you get any layout or toast Messages?
Edit: ah..bet its a locale issue. Let me research it when I get back home. I was about to starve myself while coding this.
Sent from my A500 using Tapatalk
Click to expand...
Click to collapse
...just installed it, started it...then it crashes....
@GeneralSmart. I just updated a new apk to the OP, please try it and see if works.
Once HC3.1 comes around, it should auto-detect plug/unplug and I can do an auto-mount option. Also thinking about adding an option to mount to the drive label instead of device id. (ie. /mnt/MyDrive instead of /mnt/sda1).
This may work on other devices too (Xoom, Asus), but I don't have any to test. I wonder if i can root a xoom at bestbuy.. lol
Works now...thank you for your work! (could been my fault cause i had no busybox installed, sry)
schweet.................
B'dazz man. Imma start using this to change some files in the system partition. THANKS MAN!
OK, when I connect a 16GB thumb drive it is detected
/dev/block/sda1 (/mnt/usbOTG) Type: fat32 Size: 14.9G Label: B041-B354
When I tried my 250G Passport it doesn't recognize it. My Xoom hasn't been able to recognize it at all.
Also, when the thumb drive was connected, I selected unmount all (in order to safely remove it) and it temporarily messed something up in my file system. i had lines overwritten in ES File Explorer saying "SD card is not mounted" but my external sdcard was still mounted.
Anyway, that's the extent of my beta testing so far. I don't know if my explanation was clear, so ask any questions, and I'll try to answer. I would like some way of mounting the Passport, if possible.
okantomi said:
OK, when I connect a 16GB thumb drive it is detected
/dev/block/sda1 (/mnt/usbOTG) Type: fat32 Size: 14.9G Label: B041-B354
Click to expand...
Click to collapse
When it picked it up, was it already mounted? Or did you have to click mount and this you got the line above? That looks like an Android auto-mount and you should have still had a "Mount" button next to it. Clicking it should have changed the mount point to /mnt/sda1 (or something like it). Where then it would be mounted on both paths (at least that's how it works on acer). Then unmounting should change it back to (/mnt/usbOTG), which can't be manually unmounted for some reason (again, that's how it works on Acer).
okantomi said:
When I tried my 250G Passport it doesn't recognize it. My Xoom hasn't been able to recognize it at all.
Click to expand...
Click to collapse
Can you check if the drive type is Basic or Dynamic in the windows drive manager (see screenshot http://screencast.com/t/EZwRgotf)
I havn't tested a Dynamic drive, so not sure if Android has the drivers to handle it. If it's Basic, then something else is going on.
okantomi said:
Also, when the thumb drive was connected, I selected unmount all (in order to safely remove it) and it temporarily messed something up in my file system. i had lines overwritten in ES File Explorer saying "SD card is not mounted" but my external sdcard was still mounted.
Click to expand...
Click to collapse
Did it mess up the filesystem on the USB drive? like currupt files or the FAT? It sounds like ES File Explorer may have just freaked out because an mount dissappeared that it was currently browsing. I'll download ES File Explorer and play with it and see if I can duplicate the results here.
Thanks!
Euclid's Brother said:
Once HC3.1 comes around, it should auto-detect plug/unplug and I can do an auto-mount option. Also thinking about adding an option to mount to the drive label instead of device id. (ie. /mnt/MyDrive instead of /mnt/sda1).
This may work on other devices too (Xoom, Asus), but I don't have any to test. I wonder if i can root a xoom at bestbuy.. lol
Click to expand...
Click to collapse
For the brief time that I had the Asus TF... it auto detect the USB/MicroUSB...etc plus when you click ( lower right )...it also gave the option to unmount too.
Thanks for this app... I've been wondering why we do not have the unmount option with our A500... seems pulling a usb device out without unmounting first is a recipe for corrupted files and defect device at a later point in time...etc
Works great for me, first try. Pretty frickin' sweet. Good work, sir!
i guess im the first to try multiple devices on here? it works great, sees all devices attached. great work! now my hub can go with me and my tablet when im on the go
Works fine in my Iconia, but needs to install BusyBox older version of 1.18.0.
Crash about 30% of time.
One question, will it work on Xoom?
satawat.thongsawat said:
One question, will it work on Xoom?
Click to expand...
Click to collapse
What exactly does this do?
Sent from my A500 using XDA Premium App
@ satawat
I'll check that out. I think the new version info of busy box just came out yesterday. Ill try to find out what's causing the problem.
Sent from my A500 using Tapatalk
@ satawat
Yes, it does. At least two ppl have tried it on the zoom successfully.
Sent from my A500 using Tapatalk
Hello all,
I'm getting prepared to upload my Alpha 2 port of Bodhi Linux for our Iconia. The thread for the original release is here. In the next few days, I'll be uploading the files to my server, writing up guides, and taking any questions. I highly recommend installing a GNU/Linux distribution before even attempting this. Using Linux in a VirtualBox *should* work, but I can't promise that. As usual, if this product bricks your device, it's not my fault. By attempting to use this release, you agree that it is not my fault. The same goes for instantaneous combustion, natural disasters, and acts of God.
New Features:
New recovery.img compiled using the Iconia, not at x86 processor (dunno if this means anything)
The ability to download, compile, and install the kernel/modules right from the device, no computer needed (after initial installation).
mkbootimg and mkbootfs
Scripts to automate grabbing the files needed for WiFi to work
Untested (May work, but I didn't have time to play with):
Bluetooth
Sound
3D acceleration
Here are the links needed to get started (not done yet):
[Guide] Installing Bodhi Linux onto the Iconia
[Guide] Compiling/Installing your own kernel!
[Download] Bodhi Linux for Iconia
[Download] recovery.img
[Download] Kernel Source
Screenshot
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I'd like to thank everyone who made Alpha 2 possible, including all kernel devs, etc. I'd also like to thank Jeff over at the Bodhi Linux forums.
Please ask as many questions as you'd like, even before Alpha 2 is released.
UPDATE:
The image is now up. Use gparted to partition your micro sd as follows: at least 1.5 GB (i think, it could be more) as the first partition, ext4 format. Name that partition "bodhi". Partition 2: atleast 128 MB, fat32 format. When done, mount partitions. Extract the bodhi tarball to the root of your card. Do it like this:
sudo su
cd /media/bodhi/
tar -jxvf /home/name/bodhi_alpha2.tar.bz2
Then type in ls, you should see etc , home, and the like. If you see a folder, you did it wrong.
Copy recovery.img to the 2nd partition. In Acer Recovery Installer, flash it using this custom image. Copy your nvram.txt to the card as well. Reboot into recovery. Enter the terminal. Type in setupwifi . This will copy nvram.txt to the correct place. I'll be writing up some official guides to get this working. BTW, what do you guys think of Plasma Active Two?
UPDATE (23 / 02 / 2012) : Bodhi will be on the backburner for a while. I've school stuff to do, and will be playing around with the leaked ICS.
It is very good
- Have you tested backlight regulating?
- Can you patch the kernel to overclock tegra?
Do you still need an 8 gig micro sd card for this? you mentioned something in alpha 1 about that being fixed in later versions. I really want to try this on an old 4 gb sd card so hopefully that might be enough
Great work btw! keep it up!
loband_ml said:
It is very good
- Have you tested backlight regulating?
- Can you patch the kernel to overclock tegra?
Click to expand...
Click to collapse
I have not tested backlight regulating yet.
I'm not too good at kernel patching, but anyone who wants to play with the kernel will just have to type in "getkernel" and it will dl & unpack it.
Thanks for your interest!
chaosking121 said:
Do you still need an 8 gig micro sd card for this? you mentioned something in alpha 1 about that being fixed in later versions. I really want to try this on an old 4 gb sd card so hopefully that might be enough
Great work btw! keep it up!
Click to expand...
Click to collapse
It may work on a 4GB, I'm going to be doing some testing w/ one today. The current 8GB I'm using is only Class 4, and Bodhi works pretty well on this older card of mine.
I'm sounding repetitive, but thanks for your interest as well! At first, I didn't think anybody would care about this too much.
When can we expect the required files to be uploaded? (an estimated day perhaps?). And do USB peripherals work (e.g keyboard/mouse) and camera work? And do you think either eclipse or netbeans IDE will work when installed?
Will this work with any Linux distribution?
I was wondering if your Linux recovery kernel will work with other rootfs images like ubuntu or kde or backtrack?
newbkilla said:
When can we expect the required files to be uploaded? (an estimated day perhaps?). And do USB peripherals work (e.g keyboard/mouse) and camera work? And do you think either eclipse or netbeans IDE will work when installed?
Click to expand...
Click to collapse
It should be up tomorrow, but my ISP sucks. I'll try getting it up. I've noticed that usb keyboards and mice do work. The apple mouse doesn't, but that's probably just a kernel module I didn't compile. I'll get that in the next version, or you could compile your own, which is very fun to do (seriously, on of my favourite hobbies.) No clue on the cameras, haven't tested. Eclipse / Netbeans may work, you'll have to test and post the results, please.
chrisnave1 said:
I was wondering if your Linux recovery kernel will work with other rootfs images like ubuntu or kde or backtrack?
Click to expand...
Click to collapse
Yes, it works with Ubuntu. I'm pretty sure you could load kde up on the bodhi image, log out, then select it as your sessions. It may be slow. I recommend taking a look at the Plasma Active 2 interface, built by the KDE folks. It's pretty sweet. I've just got done downloading backtrack, and it may work. Not sure, either.
backtrack
could you possibly upload a backtrack raw image for our iconia... would love it, would also entice me to donating hehe
chrisnave1 said:
could you possibly upload a backtrack raw image for our iconia... would love it, would also entice me to donating hehe
Click to expand...
Click to collapse
GEEZ! I upload one or two distro ports and now YOU want ME to work on ANOTHER one?!?
Lol, jk. I love backtrack, of course I'll work on it.
Also, can you include the florence keyboard into the rootfs in the next releases?
I have troubles with it`s compiling (becouse i am noob)
I look forward to)
wow thanks much I am still an infant when it comes to compiling kernels or even rootfs image lol... I I was able to get aitcrack-ng but not gerix yet cannot find good repository for bt5 to add
So, I now have the images up on the site. The next day or so I'll be working on an in-depth tutorial. I'll also post a tutorial for downloading / compiling the sources straight from the device.
and can not install on internal memory?
dimon2242 said:
and can not install on internal memory?
Click to expand...
Click to collapse
With the current kernel, no. I stay away from that for now, to prevent bricking. You can compile a kernel using the source to aim at the internal card. This is not reccomended, and I take no responsibility for anything done.
Backtrack anytime!
I'm interested for Backtrack for sure.
This website might be helpful for backtrack:
http://roms.tiamat-dev.com/tiamat_xoom/backtrack-5-with-aircrack-for-motorola-xoom/
It seems possible to use USB wireless adapter and drivers with the Xoom, I am in the office for too long this week and I'm starting to look at that very closely.
Running an RTL8187 monitor on backtrack on Iconia A500 might be something that could be done...
djxtabay said:
I'm interested for Backtrack for sure.
This website might be helpful for backtrack:
http://roms.tiamat-dev.com/tiamat_xoom/backtrack-5-with-aircrack-for-motorola-xoom/
It seems possible to use USB wireless adapter and drivers with the Xoom, I am in the office for too long this week and I'm starting to look at that very closely.
Running an RTL8187 monitor on backtrack on Iconia A500 might be something that could be done...
Click to expand...
Click to collapse
Thanks for the link. You see, we don't have to worry about making Android compatible drivers. On the Iconia, my kernels don't boot under chroot. They load themselves, then point at any chosen partition. Simply compile the needed driver in the kernel, flash it, (or just load the module), and go from there.
i had in mind internal SD card)
dimon2242 said:
i had in mind internal SD card)
Click to expand...
Click to collapse
I'll compile you a special kernel to boot to internal memory. Which partition (mmcblk0px) do you want it to boot to? I cannot verify it will work. It may brick your device. I am not responsible for anything that may happen.
I type debian and debian for username and password and I recieve the following error message:
"GDM could not write to your authorization file. This could mean that you are out of disk space or that your home directory could not be opened for writing. In any case, it is not possible to log in. Please contact your system administrator."
/edit to add image taken on my phone.
Hi All,
Here is 2.4.81 firmware for SDE enabled devices.
I did two versions:
- squashfs, in this one, system is read-only, you can't add/remove stock apps and edit system files. Files are compressed so it takes less storage space than ext3, it should be also slower than ext3.
- ext3, system is read/write and should be quicker. Be careful if you modify system files though. No ext4 for the moment as source code for the kernel is not available and ext4 is not enabled in stock kernel.
To install it:
(Pictures are from G9 A101 but menus are similar)
0) You must have SDE installed. If you didn't do it already, check there instructions on how to do it.
1) Extract zip file content
2) Copy android_2.4.81.squashfs (or android_2.4.81.ext3) to internal storage root.
3) Reboot
4) On boot menu, select "Recovery system"
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
5) Select "developer edition menu"
6) Select "flash kernel and initramfs"
6) A drive should appear on your PC, copy zImage and initramfs.cpio.gz to it.
7) Select OK, the kernel should flash.
8) Select OK to reboot and maintain vol+ pressed. Boot menu should appear after reboot.
9) Select SDE in boot menu, you should be rooted and SuperUser functional.
Download rooted 2.4.81 on squashfs here.
Download rooted 2.4.81 on ext3 here.
Cheers,
LeTama
*reserved*
Hey letama,
it seems you're cracking everything you got at hand
So how about the OS on this devices... is it still Froyo?
Extracting and grepping the included kernel gives:
Code:
Linux version 2.6.29-omap1 ([email protected]) (gcc version 4.4.1 (GCC) ) #1 PREEMPT Mon Dec 5 13:58:23 CET 2011
EDIT:
Not sure, seems to be recovery kernel
Waiting for letama's reply...
So what did they change here... better hardware specs of course.
So did they use 512MB RAM?
Screen resolution also increased, right?
What's the actual kernel version?
Congratulations for your new toy!!
Cheers,
scholbert
scholbert said:
it seems you're cracking everything you got at hand
So how about the OS on this devices... is it still Froyo?
Click to expand...
Click to collapse
Well, now it's easy as I know where to look and wrote my tools.
So what did they change here... better hardware specs of course.
So did they use 512MB RAM?
Screen resolution also increased, right?
What's the actual kernel version?
Click to expand...
Click to collapse
512 MB of ram yes, a quite nice 1024x600 screen, and charging through usb which was one of my main grip with ram.
And yes, it's a 2.6.29 as expected to match froyo. Unfortunately no kernel source and too lazy to backport panel and touchscreen from .35 knowing that gingerbread should come soon.
Congratulations for your new toy!!
Click to expand...
Click to collapse
Thanks! Was lucky to get it at a low price, it's a nice upgrade that didn't cost too much. I really like 7", easier to work with it and laptop in the train, my main hack time . Next will be asus I presume if they arrive here, but until then...
Hi,
I have a A70b and i have the Developer menu active. However i put the rooted build (i have tried both) and did all the instructions...but well i try to boot into developer edition the devices stays freeze on "Archos" boot logo.
Any ideias on what could be the problem?
Thanks
scalaneo said:
Hi,
I have a A70b and i have the Developer menu active. However i put the rooted build (i have tried both) and did all the instructions...but well i try to boot into developer edition the devices stays freeze on "Archos" boot logo.
Any ideias on what could be the problem?
Click to expand...
Click to collapse
Hi scalaneo,
Kernel did get flashed properly ?
You're sure the ext4 or squashfs file is at root of internal storage ?
It's not hard drive model, right ?
Hi,
Yes it´s hard drive 250gb model. Developer Menu is ok and the i copied the file to root yes.
scalaneo said:
Hi,
Yes it´s hard drive 250gb model. Developer Menu is ok and the i copied the file to root yes.
Click to expand...
Click to collapse
Ok, that's why, I was not aware that HD model was out already when I did it, I mounts SD internal storage only. I'll take a look to see how I can detect HD and mount it.
Thanks Letama!
Can you try to flash this kernel and let me know ?
It should mount hd instead of sd.
Hi,
I have tested it and i get same result. :-(
It flashes kernel but then i get´s freeze at boot screen.
Grrr!
Ok, if you don't mind, could you try this one ? It should display two debug screens, could you show me the result (picture or write it here ?)
First Screen:
Product name is A70HDD (A70H2)
Second Screen:
Product name: [A70H2]
Thanks
scalaneo said:
First Screen:
Product name is A70HDD (A70H2)
Second Screen:
Product name: [A70H2]
Thanks
Click to expand...
Click to collapse
Ok, so detection is good.
On second screen, nothing is displayed under the "Product Name: [A70H2]" ?
If nothing is there, mount didn't work.
Can you try the one attached ? And if not better, give me the result of "adb shell mount" on regular boot?
Sorry for the trial and errors
Hi again,
Menu 1 and Menu 2 photos attached:
After i can boot into Developer mode. But i always get the hdd as "Damaged internal storage". Internal storage problem. Please reboot.
It seems that i cannot access the hard drive somehow. Could it be because the build was done to work on SD card and not the internal HDD?
Many thanks for your support on this mate.
scalaneo said:
Hi again,
Menu 1 and Menu 2 photos attached:
After i can boot into Developer mode. But i always get the hdd as "Damaged internal storage". Internal storage problem. Please reboot.
It seems that i cannot access the hard drive somehow. Could it be because the build was done to work on SD card and not the internal HDD?
Many thanks for your support on this mate.
Click to expand...
Click to collapse
Hum, ok.
So mount worked, Android starts and you get this message just after?
I have no idea why, build should be the same between SD and HD as far as I know. The only thing I do differently from stock is that I mount the internal storage at the beginning to be able to access the ext4 file, but I do it in a separate directory than normal mount location to avoid interaction.
I'll take a look if I can find something.
Hi,
Thanks again for your help.
Well yes...this happens after the boot. Everything works fine but i cannot access the files or anything in HDD.
Also...everytime i try to access aplications that were installed in HHD it gives me an error saying that cannot find sd/.
I think that it assumes sd as default and not hdd. Also this is ext3 and not ext4, but i don´t think it will affect here.
Thanks again for the help.
scalaneo said:
Hi,
Thanks again for your help.
Well yes...this happens after the boot. Everything works fine but i cannot access the files or anything in HDD.
Also...everytime i try to access aplications that were installed in HHD it gives me an error saying that cannot find sd/.
I think that it assumes sd as default and not hdd. Also this is ext3 and not ext4, but i don´t think it will affect here.
Thanks again for the help.
Click to expand...
Click to collapse
Oh, ok so it boots fine but only hd is not accessible.
Could you give me the result of "adb shell mount" on both working stock and not working rooted build ?
letama said:
Could you give me the result of "adb shell mount" on both working stock and not working rooted build ?
Click to expand...
Click to collapse
And I was thinking... Could you also do "adb pull /mnt/system/androidmerged.squashfs.secure" and "adb pull /mnt/rawfs/init" (while rooted),and upload files somewhere (multiupload.com or something else) ? Maybe I could pinpoint differences.
Thanks,
LeTama
Hi,
Sorry for the delay. I have been really busy does days.
I have attached the adb shell mount.
About the other ones that you wanted me to try it says for both that "does not exist".
Thanks again
Hi, I recently purchased this acer a500 and I had no idea it was a demo unit. I cant return it and I am new with andriod based products. Please help. I know my build is Acer_A500_1.109.02_PA_DEMO and my android version is 3.0.1 Thank you for your help
Happy to help but whats the problem with yr 'demo' unit?
Sent from my GT-I9300 using Tapatalk
dibb_nz said:
Happy to help but whats the problem with yr 'demo' unit?
Sent from my GT-I9300 using Tapatalk
Click to expand...
Click to collapse
Demo units have a special limited rom. He will need to run a full rom on it.
Moscow Desire said:
Demo units have a special limited rom. He will need to run a full rom on it.
Click to expand...
Click to collapse
Yeh but he doesnt mention whether he wants to flash a custom or whether its bricked. And if it's a demo can u flash it as per normal M?
Sent from my GT-I9300 using Tapatalk
dibb_nz said:
Yeh but he doesnt mention whether he wants to flash a custom or whether its bricked. And if it's a demo can u flash it as per normal M?
Sent from my GT-I9300 using Tapatalk
Click to expand...
Click to collapse
Yep. I would suggest 2 things. Get the uid, then flash a full update rom to 3.2. Then ota it to ics. Am mobile now, so you get the ball maverick!
Those demo roms are missing half the stuff. Not sure whether he has ext sd card access. Might have to euu him. Hence uid.
Moscow Desire said:
Yep. I would suggest 2 things. Get the uid, then flash a full update rom to 3.2. Then ota it to ics. Am mobile now, so you get the ball maverick!
Those demo roms are missing half the stuff. Not sure whether he has ext sd card access. Might have to euu him. Hence uid.
Click to expand...
Click to collapse
Ahh cool, ok then, guess we'll w8 till he gets back to us, cheers M!!
Sent from my GT-I9300 using Tapatalk
reply
Hi, thank you all for your replies I am still having a hard time fully understanding everything like I said I am new to android. What I do know is it doesnt have google play which is my main concern. Kernel version 2.6.36.3 if that helps anyone its not bricked, I wouldnt mind flashing it if that would fix the problem and make it like a normal tablet version. Whats a UID? Where do I find it? Thanks again for your help
thebrews1986 said:
Hi, thank you all for your replies I am still having a hard time fully understanding everything like I said I am new to android. What I do know is it doesnt have google play which is my main concern. Kernel version 2.6.36.3 if that helps anyone its not bricked, I wouldnt mind flashing it if that would fix the problem and make it like a normal tablet version. Whats a UID? Where do I find it? Thanks again for your help
Click to expand...
Click to collapse
Well we will try and keep things simple for you, which isn't easy with this particular android device but the very first thing you should do is to retrieve your CPUID. This is imperative. If anything ever goes wrong this CPUID is needed to help you unbrick.
First we need to set up your PC to be able to communicate with your tab, so we need some drivers. This whole process works best with win7/vista/xp so if you are doing this on win8 you may have some issues. In saying that, if you're a Linux user, then thats even better, so please say if you are we can bypass a heap of stuff!!!
Head over to Acer Support and download the Acer drivers here Run the .exe to install
Download the usb drivers from here extract to a folder on your PC (desktop).
Once your drivers are installed check they are installed correctly.
1. Grab your micro usb cable and hook your tab to your PC (u should hear windows make the new hardware connected sound. Then you should see the 'new hardware wizard' attemp to install the Acer Drivers. Hopefully everything should install correctly.
2. Now on to test the usb/adb drivers. The files you extracted to your desktop. We aren't going to do anything as such with these, they just need to be on your system somewhere.
So, when you are ready.....right click the extracted folder (hold down shift key at the same time) You should see the context menu with an option to
"Open command window here..."
3. When the command opens type the following with no quote marks:
"adb devices" and then press enter.
4. You should see "List of devices attached....and a series of numbers/letters here like this:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
this is your magical CPUID! and it should have 15 characters - write this number down and guard it with your life!!!
5. If you don't see this window, it means your PC does not 'see' your tab.
Try a different micro usb cable and make sure the cable is firmly connected, try a different usb port on your PC.
Well, thats your first lesson of the day
Once the drivers are setup correctly, we can move on to getting your tab upgraded into some ICS/Jellybean goodness!
Good luck with lesson 1, ya got any probs or u don't understand something, just ask
dibb
Can all this be done on a mac? If not its fine I can borrow a friends laptop.
thebrews1986 said:
Can all this be done on a mac? If not its fine I can borrow a friends laptop.
Click to expand...
Click to collapse
Not that I am aware of. Gonna need a PC with windows XP or 7. Mainly because most of the apps we use are windows based. And I wouldn't trust a windows emulator. Also, acer drivers install is windows based.
Do you have access to your external SD card? Will need to know.
The demo unit is the same as a regular 500. All the same hardware. The difference is the ROM they install. If you have access to your external SD card, it will make the process a little easier. Basically just put a full update rom on it, and reboot it via recovery.
But.... UID number we must have, just in case things go south as dibb said.
So check access to external sd card. You can do this by going to Settings>Storage and check.
Don't worry, we've done a couple of demo units in the past.
Mac's.....pffffttttt.....
MD
NEWS FLASH
I told you we have dealt with Demo units in the past.
Go to;
http://forum.xda-developers.com/showthread.php?t=1410802&highlight=demo
You;ll need to read the posts....
Install the old Iconiaroot apk
Install Acer Recovery and let it install a CWM (custom recovery). Probably the oldest version.
After it's done, Flash a version 3.1 ROM
Let it OTA all the way to ICS
This of course is just another option. This is the old original way before version 3.2.
MD
storage
external sd card says total unavailable. and under available it says unavailable.
Is the SD card mounted and formatted?
thebrews1986 said:
external sd card says total unavailable. and under available it says unavailable.
Click to expand...
Click to collapse
Well, that figures..demo unit... EUU time.
Basically, you are going to need a windows PC with the acer drivers installed. The whole process will take about an hour, so make sure your tablet is charged fully.
Get the following files;
1. http://forum.xda-developers.com/showthread.php?t=1816560 scroll down to the EUU, and click the box "show content". Select the torrentz file. Yes, it's torrentz, so you will need a torrentz app installed on the PC. If you don't want to deal with torrentz, let me know, and I'll check my drives nd see if I have the package.
2. go here;
http://forum.xda-developers.com/showthread.php?t=1624645
Go to the bottom, and download the "usbdeview". There are 2. 1 for 32 bit windows, and 1 for 64 bit windows.
Extract both of those above packages to a folder on your pc.
Now, make sure on your tablet, you have USB Debugging set to ON (look in your System Settings, as I can't remember exactly where on HC 3.0). Connect yer tablet to PC and make sure you have no errors. If everything is good, unplug, and plug it back in a few times just to be sure.
Now, with tab connected, run the USBdeview app you extracted. Should give you a long set of numbers and letters. Write them down, or save in Notepad. This is your UID. You can close the app
Next, with tab still connected, run the EUU executable you extracted. Just follow the steps exactly as they say. This may take awhile. It'll probably ask for that UID number at some point.
When it's all finished, you should have to restart the tab, and the first boot will be somewhat long (10+ minutes or so). But it should boot into a fully working 3.0 HC. Which is crap by the way . You'll need to OTA, or contact us for advice.
Good luck.
MD
tried to download the files using utorrent and it didnt download. Is there an easier way of doing this?
thebrews1986 said:
tried to download the files using utorrent and it didnt download. Is there an easier way of doing this?
Click to expand...
Click to collapse
try this EUU it will upgrade you to HC3.2.1 - its pre-rooted and will give you a custom recovery as well. Theres a readme with instructions included in the zip. As with any EUU you will need your cpuid to use it but usbdeview is also in there.
while you are waiting for this to download try rooting your current rom with this then install this .apk and you will be able to install a custom recovery. Once you are in recovery, the main screen will display yr cpuid too.
Hey guys,
I have an issue with my Moto X Pure edition, 32 GB XT1575. Nothing wrong with the phone, I adore this phone because with the unlocked bootloader and root, this phone is a dream. No decent roms for it, I was really hoping for a sweet CyanogenMod rom but no joy. Does not matter, with Xposed, Nova Launcher Pro, and root, I get all I want.
The issue is file access, especially large files that I need or want to copy from phone to PC or USB drive. I installed the Motorola Device Manager which gave me the drivers I need to access the phone and run adb and fastboot commands. The problem is, when I want to remove a TWRP backup which are pretty darned big folders, approximately 11 GB in size, I cannot just "Plug in a USB cable, tap PTP mode, and then copy or move files in either direction, for either internal or external sd cards. The moment I copy and try to paste, or drag and drop, both Windows Explorer windows disappear. Poof, gone! I am now on Windows 10 Pro x64 but prior to the MS upgrade, I had the very same issues with Windows 7 Ultimate x64 so it is not the operating system of the PC. Developer mode is enabled. I will show you some pictures in PTP mode.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I just don't get it. Ever since Lollipop and then this phone and Marshmallow, I cannot use USB to quickly transfer files at all. I can use a WiFi file manger and try to use that to copy the folder over to the PC, but at a whopping 11 GB, the operation estimates a 1.5 hour transfer time and it never finishes. I can grab big files like this by shutting down the phone, removing the sd card and using a card reader to make file transfers quick and painless. But that is a pain in itself, shutting down the phone, finding the small tool to open the card drawer, being careful not to lose the SIM card, removing the sdcard for the card reader, and all this in reverse just to turn my phone on again.
There must be a better way or better drivers. Yes I have tried AirDroid and it works, but same deal, huge transfer over WiFi, takes forever and probably will not finish. How do you guys transfer large or numerous files to and from the Moto X Pure? Suggestions? Please?
EDIT:
Supposedly you can plug a USB drive into this phone for temporary storage. Now I have never done this since I do not have a USB cable that has a micro phone plug on one end. I just ordered a USB to USB adapter so I can connect my phone's data cord to a standard USB cable to connect to a portable USB drive. If that were to show up in /Settings/Sorage & USB/ then maybe I could copy the file with some sort of impressive speed to the external USB drive, then plug that into PC for offloading. Have not tried it, have any of you done this? It would probably be the ONLY way to get large files to/from the internal sdcard since it cannot be put in a card reader.
EDIT 2:
I turned off the USB Debugging and had no trouble transferring files at all. First I tried a file, internal card, no problem. Then a file ext card, no problem. Then since I was on a roll, one of the TWRP backup folders on the ext card. Poof, Explorer closed. Maybe too many files or too big in that folder? I tried to copy the TitaniumBackup folder over to PC which is chock full of files, lots of them. The transfer started while determining the time this transfer would take, then the transfer began.
Back to TWRP because those backups I want to copy off in the event I might need them, for a little while, anyway, rather than just delete them. This time I used EX file Explorer to zip up my earliest backup and the archiving as a zip file began. Since this is an 11 GB folder the estimated time was over an hour. I will let it run and create the zip, then see if I can transfer the zip file over. If it works, I have my answer. It seems there is something funny about the TWRP backup folders. The one on the internal card cannot be accessed by any means, including root, if Android is running. Boot to recovery and the internal card TWRP folder and files are totally accessible.
Looks like you found an answer to your original problem, but I wanted to comment that there are exceptional ROMs out there for the Moto X, but not all roms are on XDA. A search for dysfunctional roms might yield a hidden gem, rom wise. ????
acejavelin said:
Looks like you found an answer to your original problem, but I wanted to comment that there are exceptional ROMs out there for the Moto X, but not all roms are on XDA. A search for dysfunctional roms might yield a hidden gem, rom wise. ????
Click to expand...
Click to collapse
If there are any good roms out there for the Moto X Pure Edition, I cannot find them. The new launcher plus xposed has given me a lot of freedom with the phone, but NO improvement to USB file copying. Any tips would help. Thanks!
Ohmster said:
If there are any good roms out there for the Moto X Pure Edition, I cannot find them. The new launcher plus xposed has given me a lot of freedom with the phone, but NO improvement to USB file copying. Any tips would help. Thanks!
Click to expand...
Click to collapse
Really? What have you tried?
BrokenOS
Dirty Unicorns
AICP
Exodus
Resurrection Remix
Tesla
Orion
Mokee
And that's just a place to start, in no particular order.
acejavelin said:
Really? What have you tried?
BrokenOS
Dirty Unicorns
AICP
Exodus
Resurrection Remix
Tesla
Orion
Mokee
And that's just a place to start, in no particular order.
Click to expand...
Click to collapse
Thank you!
I have heard of them, did research on some of them, and have friends with the exact same phone who have tried some of them. Mostly Mokee and maybe Dirty Unicorns. They have since reverted back to rooted stock with Nova Prime Launcher and Xposed, the setup I am using. I think the issue is that although these may be fine roms, in each situation, there was some aspect of the original phone or features that became not usable. I cannot give you details as it was some time ago. The stock setup works fine for me with root, launcher, and xposed. I see no improvement for USB file transfers and a new rom to achieve it, if you can at all. Even if it did improve the USB file transfer, an entire new rom to get there is a high price to pay, especially if the new rom could not power all of the features on the phone.
I do not want to argue about it, this is just my opinion based on the facts I could get. But I asked for some roms and you did deliver. Thank you very much! :good:
Ohmster said:
Thank you!
I have heard of them, did research on some of them, and have friends with the exact same phone who have tried some of them. Mostly Mokee and maybe Dirty Unicorns. They have since reverted back to rooted stock with Nova Prime Launcher and Xposed, the setup I am using. I think the issue is that although these may be fine roms, in each situation, there was some aspect of the original phone or features that became not usable. I cannot give you details as it was some time ago. The stock setup works fine for me with root, launcher, and xposed. I see no improvement for USB file transfers and a new rom to achieve it, if you can at all. Even if it did improve the USB file transfer, an entire new rom to get there is a high price to pay, especially if the new rom could not power all of the features on the phone.
I do not want to argue about it, this is just my opinion based on the facts I could get. But I asked for some roms and you did deliver. Thank you very much! :good:
Click to expand...
Click to collapse
ROMs are easy... Always backup in TWRP before flashing, you can always restore. If you want to test some ROMs, remember to backup to external storage (SD card) as the biggest mistake is backing up to internal storage and then wiping it for the new ROM.
You lose 2 things in general, Moto Display... Ambient Display is a poor substitute, and battery life. Moto may do many things poorly but they know how to optimize a ROM to a device for optimal battery usage and custom ROMs struggle to get near the runtime of stock, although it's better than it used to be.
To be honest, I went back to stock too... Pure stock, no root or Xposed, but I still use Nova Launcher Prime.
I don't tell you that a 3rd party will fix your issue, in fact I doubt it will, but the cost isn't as high as you thing if it works. If it doesn't, restore to stock and move on.