Related
I just bought a nook simple touch and i want to start playing with it, but, before i do this, i want to make sure i have a backup for it.
My problem is that i am unable to see the hidden partiton (the large one). I use ubuntu linux, but i also tried looking for it on windows, following the instructions from this link.
the df -h output is:
Code:
[email protected]:~$ sudo df -h
Filesystem Size Used Avail Use% Mounted on
/dev/sda5 21G 8.1G 12G 42% /
udev 3.8G 12K 3.8G 1% /dev
tmpfs 1.6G 1.2M 1.6G 1% /run
none 5.0M 8.0K 5.0M 1% /run/lock
none 3.8G 684K 3.8G 1% /run/shm
/dev/sda1 100M 28M 73M 28% /media/winboot
/dev/sda2 52G 50G 1.4G 98% /media/Windows
/dev/sda7 189G 178G 1.7G 100% /media/alex
/dev/sda6 31G 16G 14G 53% /home
/home/burfee/.Private
31G 16G 14G 53% /home/burfee
/dev/sdb 237M 82M 156M 35% /media/NOOK
and of course, when i create the image using dd, it looks like this:
Code:
[email protected]:~$ dd if=/dev/sdb of=my_nook_bk.img bs=1M
239+1 records in
239+1 records out
251641856 bytes (252 MB) copied, 15.2308 s, 16.5 MB/s
on windows, also, Roadkil's free DiskImager also sees just this small partition.
there probably is some protection b&n set on the device, but couldn't find any post related to this issue.
my model number is BNRV300
What options do i have?
Use Roadkil - backup the physical disk not the partition - this will of course depend on the number of drives you have - on my laptop it is disk 1 1.86G
as i said, roadkill doesn't see that partition either
Are you booting from a sdcard with noogie (is rooted forever written on the screen)?
If you just boot normally you can only access the media partition and the sdcard.
oh, so this is it... no, i didn't boot with noogie. i booted it normaly. seems like i missed that step. will try with noogie. many thanks!
L.E.: i just figured out why i missed that step - the nookdevs.com site is down so the link didn't work. any reliable source to get that image?
Thanks
@up, right here http://dl.dropbox.com/u/17432768/noogie.zip
ok, i created it. does this look ok to you?
Code:
[email protected]:~$ fdisk -l my_nook_bk.img
Disk my_nook_bk.img: 1962 MB, 1962934272 bytes
128 heads, 32 sectors/track, 936 cylinders, total 3833856 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x00000000
Device Boot Start End Blocks Id System
my_nook_bk.img1 * 32 155647 77808 c W95 FAT32 (LBA)
my_nook_bk.img2 155648 188415 16384 c W95 FAT32 (LBA)
my_nook_bk.img3 188416 577535 194560 83 Linux
my_nook_bk.img4 577536 3792895 1607680 5 Extended
my_nook_bk.img5 577568 1167359 294896 83 Linux
my_nook_bk.img6 1167392 1658879 245744 c W95 FAT32 (LBA)
my_nook_bk.img7 1658912 2150399 245744 83 Linux
my_nook_bk.img8 2150432 3792895 821232 83 Linux
Looks ok.
Happy hacking
ok, so i was a bit skeptical about the image because i encountered some problems while doing it so i started over.
i'm having some problems with dd when i'm writing the images. before writing the noogie image using dd in linux, my microsd looks ok in gparted (with fat32 filesystem)
After doing this:
Code:
[email protected]:~/Nook/Nook-touch-rootkit$ sudo dd of=/dev/mmcblk0p1 if=noogie.img
155648+0 records in
155648+0 records out
79691776 bytes (80 MB) copied, 35.8831 s, 2.2 MB/s
it shows unknown for file system and cannot be mounted anymore...
the image i used before (to get the output from the previous posts was created on windows with roadkil, but now that doesn't work either.
microsd is class 4
what could be wrong? if i write other images to the disk everything is ok, but the images to root the nook do not work.
afaik the noogie image is in superfloppy format (no partition table, only the filesystem) and thats why gparted doesn't recognizes it.
But the sd-card with the noogie image on it should be mountable on windows and linux (its fat32).
Maybe you could try an other cardreader.
this is very weird... i managed to write the image to the card using "ImageWriter" (aplication for linux) which i think runs the same code i run in the terminal... i don't get what's wrong...
because if i'm doing something wrong i can't be sure that my backup image is ok.
L.E.: my image is ok, just tested it after messing up the rooting process
I think your problem is, that you should write the noogie image to /dev/mmcblk0 and not to /dev/mmcblk0p1 (on the sd-card, NOT on the nook itself).
Question how do I write the noogie image to the SD card with windows??
As said already I looked at the backup thread as said by previous poster but the link is not working.
I did get the noogie image from the other link provided but how do I copy/write the image to the SD card in windows.
Thnx in advance
Edit:
I think I found something in an other thread, they use this program (win32diskimager) to write a .img to a SD card. Will try this one out.
I used this program win32diskimager to write noogie.img to sdcard in the following manner:
- Select noogie.img as "Image File"'
- Select SD card as device
- Click the button "Write"
Then I waited untill it was finished. Put SD card in Nook Touch, started up the Nook, but no screen with "Rooted Forever" showed up and if I continued with the next step, trying to make a copy of the the Nook partition with Roadkils DiskImager then I could not see the 1.82GB partition of the Nook.
Can someone help me on the way.
I started the Nook but did not yet finish registration before I tryed the above. I was in the middle of registration, but decided to make a backup first, so switched off the Nook and did what I described above (my idea was that after the backup of my Nook to skip the registration, as described somewhere else and then root the Nook).
Hope someone could give me some answers.
Edit:
Indeed when I skipped the registration and again booted from the SD card previously made with the noogie.img I got the "rooted forever" screen and I was able to make a backup of my Nook partition. Thnx a lot everyone for making such nice descriptions, OK now try to root it.....
pow3rflow3r said:
I used this program win32diskimager to write noogie.img to sdcard in the following manner:
- Select noogie.img as "Image File"'
- Select SD card as device
- Click the button "Write"
Then I waited untill it was finished. Put SD card in Nook Touch, started up the Nook, but no screen with "Rooted Forever" showed up and if I continued with the next step, trying to make a copy of the the Nook partition with Roadkils DiskImager then I could not see the 1.82GB partition of the Nook.
Can someone help me on the way.
I started the Nook but did not yet finish registration before I tryed the above. I was in the middle of registration, but decided to make a backup first, so switched off the Nook and did what I described above (my idea was that after the backup of my Nook to skip the registration, as described somewhere else and then root the Nook).
Hope someone could give me some answers.
Edit:
Indeed when I skipped the registration and again booted from the SD card previously made with the noogie.img I got the "rooted forever" screen and I was able to make a backup of my Nook partition. Thnx a lot everyone for making such nice descriptions, OK now try to root it.....
Click to expand...
Click to collapse
CAn you please expand on how you got the nook to boot from the SD card (any special key presses?) I managed to write the noogie image on to an SD card. Inserted the card in the nook. Powered it down and then back up again, but didn't see any option to boot from the card. Not sure If I've missed something here.
Thanks in advance
arvindar_n said:
CAn you please expand on how you got the nook to boot from the SD card (any special key presses?)
Click to expand...
Click to collapse
If the img file is written correctly to the SD-Card the nook will boot from the SD-Card. No need to press anything.
I cannot get noogie image working too. Have the img "burned" to SD card. Tried 2 different cards 4GB class6 and 8GB class10.
Tried to power on connected or disconnected from PC, Nook just starts up normally and then claims SD is not recognized and should be formatted.
Any ideas?
lluf said:
I cannot get noogie image working too. Have the img "burned" to SD card. Tried 2 different cards 4GB class6 and 8GB class10.
Tried to power on connected or disconnected from PC, Nook just starts up normally and then claims SD is not recognized and should be formatted.
Any ideas?
Click to expand...
Click to collapse
It's quite simple really, the Noogie.img weren't correctly written onto your SD card.
There can be several reasons for this, but most likely it's your card reader.
I.E. the built in card reader on my old HP Pavilion doesn't support raw access in a proper way and I had to buy an external card reader for it to work.
Hey I'm having a similar challenge as arvindar_n...
I just got a new nook simple touch and am looking to back it up.
Doing a google search lead me to the Backup/Restore N2E post.
The instructions say to:
1. Boot nook with noogie.img : (the "Rooted Forever" screen) and connect to your computer via USB.
2. Use DiskImager to copy your Nook partition to a file, being sure to select "Physical Disk" in the drop down list.
Step 1 seemed to work, I used winimage and wrote nookie.img onto a sd card
I put the sd card in the nook, let it reboot and was greeted with the "Rooted Forever" screen but it just sits there...not sure if that's the first problem.
Step 2, using DiskImager, I'm suppose to select Physical Disk. The challenge I'm having is there are 0-7 Physical Disks! My confusion is that none of the sizes are the 1.82 partition I'm reading about. I can see a 239.98 and 120.08 but no other physical drive besides my regular disk drive.
Please advise!
When I plug my ereader (Sony PRS-350) into my USB port, and mount the external USB, it only mounts the first partition, which contains the Sony Reader software. Is there a way to make it mount the second partition instead, or as well, as the first. The second partition contains all your books, pictures, etc, so would be the only one you would care to see anyway, & would just blow off the first partition to recover wasted space if I knew how.
When I was on HC Thor rom 14.2 I was able to mount both parts of my Samsung 2.5" external HDD - first part was Fat32 and second NTFS. Now on Stock rooted ICS it can see only Fat32 part. So I think custom ICS rom will be solution
if you are rooted you can use drive mount from market
its free
Ext4 / NTFS MicroSd & Usb Mounting -v2.3 (fat32 UMS) MTP/UMS Switching/ CM9/10 info
Hi,
i have developed an App, EzyMount - that pretty much takes care of mounting & utilising ext4 / ntfs storage properly. So no need to be limited to 4gb file size restrictions anymore !!
Updated info for CM9 / CM10 builds
****************************************************************
It seems that CM9 /CM10 changes the default mount point for external sdcards
For ntfs partition only sdcard
Change the default mount point to: /storage/sdcard1
Then try mounting here it should work ok and be picked up automatically by other Apps as well.
If you have two partitions:
1st Partition would be vfat then this should get auto mounted to /storage/sdcard1
2nd Partition (ntfs) : change the mount point to: /storage/sdcard0/extStorages1
Then try mounting here it should be ok
*****************************************************************
Version 2.3 Update
Universal Mass Storage Mode support for 7.7 tabs also most other devices.
Auto MTP/UMS Switching
When you select either MTP Mode or UMS Mode, the App will automatically switch your device into these respective USB transfer method.
It is also possible to use UMS mode for any external MicroSd card, fat32, Ext4 or NTFS formatted.
For ext4 / ntfs this is taken care of by the App
For fat32 external sd cards (these are mounted automatically by Android)
Create a new Mount Point which is the folder location of your external MicroSd card.
For example, on Galaxy 7.7 devices - this will be /mnt/sdcard/extStorages/SdCard.
For Galaxy S3 devices - this will be /mnt/extSdCard
For other devices this is typically, /mnt/sdcard/external_sd
In the partition setting put: /dev/block/mmcblk1p1
Once you have created this mount point, just select "UMS Mode".
After you have finished copying files to or from your PC, it is important to "safely eject your usb device from your PC".
Important too - Finally, disable "UMS Mode" by it pressing again.
You can switch back to MTP by selcting "MTP Mode".
(If MTP does not become active straight away (Android being slow too pick up the change)- you may need to Go to : Settings > Storage > USB PC connection & toggle between Media Device (MTP) & Camera PTP. So Android re-starts MTP. However, it should work without this step)
*****************************************************************
Version 2.1 update
1) New Sliding UI.
2) Ability to mount up to 10 devices / partitions.
Just create a new Mount Point for each device / partition you need to mount.
To create a new Mount Point:
Just slide the UI to the "mount another drive or partition". Then just use select a mount option as per usual to create a new mount point and mount at the same time. Or you can press the "microsd info" "usb drive info" to create a new Mount Point.
3) Works with ICS update
Just ignore "ICS warning messages" - when it comes to ntfs usb devices.
*****************************************************************
Version 1.7 update
1) Quite a few new features added:
NTFS / Ext4 MTP Modes - this allows you to easily switch between "normal mode" and MTP mode.
MTP mode is used for transferring files to PC.
Usage Example:
Personally, I have a 32 gb sd card
the First partion on it is an exFat 4 gb partition. This is picked up the tab and mounted as normal to the location of /mnt/sdcard/extStorages/SdCard
I can use this for my cwm backups etc, other files etc - system running as normal.
This 4gb partition will show up in windows via MTP.
The problem:
I also have a 28GB Ext4 second partition on the Card , this could be an NTFS partition too.
I want this too show up in windows so I can transfer (br rips etc) but it wont as the my first fat32 partiion is shown up instead.
By using NTFS MTP Mode or Ext4 MTP Mode - the App will automatically "switch" the partitions so the larger NTFS or EXT4 mode shows up in windows.
Once done then you can disable NTFS / EXT4 MTP MODE and the device will go back to normal as it were.
(the MTP folder location is set to work already for 7.7 devices and similiar. For other devices this needs to be adjusted. It is normally the default folder loaction of where the external SD card is mounted by the phone.)
UMS Mode - universal mass storage mode.
Although the 7.7 does not have ums mode (MTP is being standardised on ics devices and above) but there a lot of devices than can only use ums mode for transferring file to PC.
I have added a ums mode. Which basically makes your micro sd partitions available on pc. (suitable for non MTP devices)
You do not need to "turn on usb mass storage mode" just select "ums mode" from the APP and it will do it for you.
Also - in windows ext4 partitions are not recognised but ntfs one are off course. In linux both should be available. (one of the benefits of MTP)
Comaptibility Mode
Is for those users whose mounting of micro sd cards might fail for some reason. This mode tries a bit more thorough to mount your micro sd drives.
Better Error Messages
I have added a lot of better error messages that the de facto "error mounting " message
It should provide the reason why things might not be mounting.
I hope this helps some with issues and pm if you have any other issues or things you think might be useful to add.
( I will get round to updating the website with the added features soon)
*****************************************************************
version update 1.6
1) Fixed slight issue with Auto Ext4 permission handling.
2) Also changed the default mount folders of NTFS or Ext4 microsd card to the /sdcard/extStorages/SdCard
This should mean now MTP will see the card in windows properly and you can access them as you would normally. (I think this has caused some confusion - i had left this generic for other users on different devices)
(This means for other devices you should specify the folder in the "location" settings which is normally seen by windows MTP - i.e when you use a fat32 microsd)
I hope this has resolved some issues people might have been having.
version update 1.5
1) Modified labelling on some settings to make it clearer.
2) Mounting usb devices has been slightly tweaked to care of multiple partitions.
version update 1.4
Following on from your recommendations.
1) Mounting MicroSd Ext4 or Ntfs now automatically takes care of you partitions so you do not need to specify them.
This should make it much simpler to mount your microsd cards.
2) Usb Mounting widget should be compatible for all home screen launchers. (touchwiz, adwlauncher etc.)
************************************************************************************************************************************************************************************************************
please remember to unmount usb / microsd devices before ejecting - For usb devices you use the 1-click usb mount/umnount home screen widget for this or from within the App
************************************************************************************************************************************************************************************************************
There have been a few issues regarding using external Usb formatted Ntfs or Ntfs microsd drives. Also I wanted to use an internal micro sd Ext4 partition for large movies (1080p hi-def/bluray etc) or just keep them on an external Ext4 usb disk. Having looked at other solutions, there didn't seem like one that just "worked" or the way I wanted it to do so.
Using Ext4 over Ntfs is native to linux/android and it consumes less cpu than using ntfs. But you cant simply mount an ext4 device and start using it like a regular file system as the file permission are not properly created by Android. I also still needed to have Ntfs read/write support on occassions.
You can use any cheap otg usb cable found on ebay etc. (The same cables as used for 10" galaxy tab devices for example).
As I used the 7.7 as one of my development device so it is pretty suited for our tabs & similiar tablets i.e 7.0+ etc, but is more than generic enough to work on other devices.
The App provides all the necessary features and customization options so you don't need to worry about file formats, file size limitations or file permissions again !!
There are more tips on how to best use the app on my website. If you have any comments good or bad please let me know so I can improve the App.
Cheers.
Need help in mounting microSD as Mass Storage
I don't understand Settings Guide on your website. I downloaded your app but it isn't working for me and I get Partition error every time I try to mount. What should be my partition and what should be the location? I simply want to mount my NTFS microSD card as mass storage which is usually at /extstorages/SDcard/. I did root my device last night and I also installed busybox v1.19 few minutes ago. What am I doing wrong?
Same here, says "Check your partitions". Why do *I* have to worry about partitions? Can't it just work?
Using rooted Tab 7.7.
Asad_Khan said:
I don't understand Settings Guide on your website. I downloaded your app but it isn't working for me and I get Partition error every time I try to mount. What should be my partition and what should be the location? I simply want to mount my NTFS microSD card as mass storage which is usually at /extstorages/SDcard/. I did root my device last night and I also installed busybox v1.19 few minutes ago. What am I doing wrong?
Click to expand...
Click to collapse
belyj said:
Same here, says "Check your partitions". Why do *I* have to worry about partitions? Can't it just work?
Using rooted Tab 7.7.
Click to expand...
Click to collapse
Hi guys,
The default partition of your microsd card is typically:
/dev/block/mmcblk1p1
1) If you have only one partition - so you will put the following in the partition setting:
So for example an NTFS only formated microsd card :
/dev/block/mmcblk1p1
And the same would go for an Ext4 formatted only card:
/dev/block/mmcblk1p1
2) If you have two partitions then typically you will have:
/dev/block/mmcblk1p1
/dev/block/mmcblk1p2
And so on ..
(you can always check for these from a terminal/adb shell)
As these partitions are same for your microsd, you can set them once and forget them about afterwards. I don't try automatically choose these partitions for you and this depends on your partitioning scheme more than anything.
For Usb devices the App will automatically try mounting your usb partitions as these are likely to change more often then not.
Typically, I would recommend the following:
If you have a large 32gb / 64 gb microsd card
Create The first partition as fat32 - maybe 4gb.
This partition will be /dev/block/mmcblk1p1
The tab will automatically mount this first partition & you can use things like cwm recovery for backup as normal.
(Also you wont see an unsupported file system icon in your status bar.)
Then create a second large partition (ext4 or ntfs) :
This partition will be /dev/block/mmcblk1p2
So set this as your Ntfs partition or ext4 partition.
Once you can mount you microsd ok - then you can set it to automount boot.
So need to mess with the settings after that.
Hope this helps and please let me know.
Cheers.
Still MTP connection
Thank you for your explanation. I've can now mount/unmount SD card but when I connect it computer it starts MTP connection and still shows under my computer as a portable device rather than a Mass Storage. Also if I connect it to my computer first it would still ask me to restart the MTP connect when I click mount SDcard and again it shows as a portable device. Changing debugging settings won't help either.
Partition /dev/block/mmcblk1p1
Location /mnt/sdcard/extStorages/SdCard
Asad_Khan said:
Thank you for your explanation. I've can now mount/unmount SD card but when I connect it computer it starts MTP connection and still shows under my computer as a portable device rather than a Mass Storage. Also if I connect it to my computer first it would still ask me to restart the MTP connect when I click mount SDcard and again it shows as a portable device. Changing debugging settings won't help either.
Partition /dev/block/mmcblk1p1
Location /mnt/sdcard/extStorages/SdCard
Click to expand...
Click to collapse
I just tried this. If you click on the "portable device" in windows it shows up as tablet. You can copy files to where you mounted the sd card.
It should work fine.
For me I leave set pretty much as default. As I have the first partition on my sdcard as an exfat / fat32. Then I have an ext4 or Ntfs Partition. This way you tab will behave exactly as normal. But The App should be fine regardless of whatever partitions you have.
Please try this and let me know.
(Also I will look to be adding an auto mounting microsd feature in the next few updates if there is some demand for this. Plus any other features people might suggest in the meanwhile )
Cheers.
To those who have installed EzyMount,
I have updated the microsd mounting feature so it should automatically mount the correct partition for you.
You dont have to manually change the partition settings anymore.
Having said that if there is a particular partition on your microsd you want to mount, then put that in the settings. The app will first try to mount that partition, then try to mount the other partitions if the first mount was not successful.
Also i would suggest setting the mount point folder (location option in settings) to /sdcard/SOME_FOLDER
& not /ext/extStorages/SdCard. which is where the tab mount would mount the microsd card.
Let me know how it goes with the update.
Hope this helps.
cheers.
Hi buddy.
I am totally confused as to how this works.
I went through the info at your website, but I still cannot get this to work.
I have tried only USB flash memory with an OTG USB adapter, both EXT4 and NTFS. I just get an error that says: Error Mounting USB Drive. I can tell that it seems to try, because the activity LED on the drive will flash when I click Mount.
I am using a Samsung Note (i717), so I am not sure if that is the problem. I am only rooted, but the kernel and software is stock 2.3. The phone has both internal memory (called USB Storage by the system) and an sd card; could the app be confused by the various memory locations?
I don't have a spare microsd to format as NTFS, otherwise I would try that.
Any ideas on what I should try? I am a little confused by the settings... they seem to be in many locations, so I am not sure what things to change.
Thanks!
G8351427 said:
Hi buddy.
I am totally confused as to how this works.
I went through the info at your website, but I still cannot get this to work.
I have tried only USB flash memory with an OTG USB adapter, both EXT4 and NTFS. I just get an error that says: Error Mounting USB Drive. I can tell that it seems to try, because the activity LED on the drive will flash when I click Mount.
I am using a Samsung Note (i717), so I am not sure if that is the problem. I am only rooted, but the kernel and software is stock 2.3. The phone has both internal memory (called USB Storage by the system) and an sd card; could the app be confused by the various memory locations?
I don't have a spare microsd to format as NTFS, otherwise I would try that.
Any ideas on what I should try? I am a little confused by the settings... they seem to be in many locations, so I am not sure what things to change.
Thanks!
Click to expand...
Click to collapse
Hi,
I have slightly updated the labelling in the App so should a bit less confusing
You shouldn't really need to change anything.
Partition - refers to the actual "physical" location of your drive as sen by the Androis OS / kernel but this is taken care of automatically so you dont need to specify this. Although you can still specify a partition and that will be mounted.
(You can see the list of your partitions by doing ls /dev/block/* for a command prompt for example)
Location - is where your microsd or usb device will be mounted. Basically the folder loaction on your device where you can see its files / folder contents etc.
The other option refer to the various features - such as auto mounting at boot, auto fixing ext4 permissions, auto usb mounting. If you dont need them you can disable them.
So hopefully we can narrow down the issue.
Do you have busybox,superuser installed ok?
I am not sure what the actual "Usb Storage" on the note is. Maybe there is a variation in the labelling but it should be resolvable.
If you can get me the output from your device from an adb shell or connectbot for example of the following commands:
# mount
and
# df -h
These should help me figure out what might be going on.
(i'll see If i can get my hands on a galaxy note - or have a look at some of the dev stuff in the meanwhile)
Cheers.
Hi. I also heve this problem with Galaxy Note (unable to mount USB drive with one NTFS partition).
Please describe how can i help you to figure out the issue step by step.
Thenks.
-=galex=- said:
Hi. I also heve this problem with Galaxy Note (unable to mount USB drive with one NTFS partition).
Please describe how can i help you to figure out the issue step by step.
Thenks.
Click to expand...
Click to collapse
No problems - been busy with some other work.
So far the App has been installed on the note more tham any other device so seems to be working for some.
A lot of problems are being caused by some users not unmounting the usb device after mounting it for the first time. Which confuses things. I will be releasing an update that takes care of this and possibly a self diagnostics checker that should help in identifying some potential problems.
Also android / linux can be somewhat particular about ntfs so best run a drive check in windows first. Or even better can you try another newly formatted ntfs usb device and see if that works.
I will pm you once i get the chance.
Thanks.
-=galex=- said:
Hi. I also heve this problem with Galaxy Note (unable to mount USB drive with one NTFS partition).
Please describe how can i help you to figure out the issue step by step.
Thenks.
Click to expand...
Click to collapse
I have sent you a pm. Also i have been looking at some of the note dev threads so should have a solution for you I think.
Cheers.
Hi All,
Updated the App to version 1.7.
Check the first post.
Cheers.
This is working great for my 64GB microsd as NTFS. The main problem i have (rather an annoyance) is there is now a constant notification about a "Blank SD card" in the notifications shade.
Does anyone know how to supress this, as it is very annoying to keep seeing it.
rEVOLVE said:
This is working great for my 64GB microsd as NTFS. The main problem i have (rather an annoyance) is there is now a constant notification about a "Blank SD card" in the notifications shade.
Does anyone know how to supress this, as it is very annoying to keep seeing it.
Click to expand...
Click to collapse
You could use the solution ezynow mentions in the first post. Create a small fat32 partition at the start of the SD card, this will also be accessible by things like recovery. Then use the rest of the card as NTFS.
I should apologize for not seeing that tip in the OP. I'll have to wait till i've got some time to repartition the card - any suggestions of what size to make the small one?
Only other problem I see is that the "mount at boot" option doesn't seem to work and I still have to go to the app to enable this.
Trouble with Ext4 MTP
I'm using a 32GB external sd card with a very small 8MB fat32 partition followed by an ext4 partition using the remainder of sdcard. Using Ezymount 1.9, I have been able to mount/bootmount my ext4 partition nicely. Where I'm still struggling is to get the ext4 partition to be accessible when the phone is USB attached to my Linux pc. When the USB cable is attached, I see the phone's internal sd and fat32 partition. When the EXT4 MTP option is enabled, still the fat32 partition is mounted on my pc. I've experimented with UMS and Compatibility modes, but the behavior remains the same.
On my SGS2, the default mount location for the fat32 partition is /mnt/sdcard/external_sd. I created /mnt/sdcard/external_sd_ext4. My external sdcard appears as /dev/block/cyasblkdevblk0, with the fat32 partition as p1 and ext4 as p2. I've configured Ezymount for ext4 with /dev/block/cyasblkdevblk0p2 with a location of /mnt/sdcard/external_sd_ext4. I've tried a number of points for the MTP location, but the resulting behavior remains the same.
Can you help me to get the ext4 partition accessible from my pc when attached via USB?
Thanks
GalaxyQuest99 said:
I'm using a 32GB external sd card with a very small 8MB fat32 partition followed by an ext4 partition using the remainder of sdcard. Using Ezymount 1.9, I have been able to mount/bootmount my ext4 partition nicely. Where I'm still struggling is to get the ext4 partition to be accessible when the phone is USB attached to my Linux pc. When the USB cable is attached, I see the phone's internal sd and fat32 partition. When the EXT4 MTP option is enabled, still the fat32 partition is mounted on my pc. I've experimented with UMS and Compatibility modes, but the behavior remains the same.
On my SGS2, the default mount location for the fat32 partition is /mnt/sdcard/external_sd. I created /mnt/sdcard/external_sd_ext4. My external sdcard appears as /dev/block/cyasblkdevblk0, with the fat32 partition as p1 and ext4 as p2. I've configured Ezymount for ext4 with /dev/block/cyasblkdevblk0p2 with a location of /mnt/sdcard/external_sd_ext4. I've tried a number of points for the MTP location, but the resulting behavior remains the same.
Can you help me to get the ext4 partition accessible from my pc when attached via USB?
J
Thanks
Click to expand...
Click to collapse
Hi GalaxyQuest99,
Could you please run the diagnostics report and send it to me. Hopefully, it is a configuration issue.
What phone/tablet are you using & Also what linux os are you running so i can repoduce the issue.
I am also working on some major new features - so version 2.0 is in the works
Thanks.
Diagnostic?
ezynow said:
Hi GalaxyQuest99,
Could you please run the diagnostics report and send it to me. Hopefully, it is a configuration issue.
What phone/tablet are you using & Also what linux os are you running so i can repoduce the issue.
I am also working on some major new features - so version 2.0 is in the works
Thanks.
Click to expand...
Click to collapse
I have a Samsung Galaxy S2. I use Ubuntu 12.04 LTS. I ran the diagnostics, but don't where to find the report.
Thanks
GalaxyQuest99 said:
I have a Samsung Galaxy S2. I use Ubuntu 12.04 LTS. I ran the diagnostics, but don't where to find the report.
Thanks
Click to expand...
Click to collapse
Hi,
There should be a report generated under /sdcard/ezymount_test.txt.
Could you email it to [email protected].
If there isnt a report then email me at this address too so i can you send you an updated version of the app if needed.
Will setup ubuntu and test this also.
Cheers.
Here is a full guide I wrote for those who need it, but the quick version is to mount your external storage using StickMount and then navigate to "External Storage -> USBStorage -> sda1" from within XBMC. Files show up and play smoothly.
fireTVnews.com said:
Here is a full guide I wrote for those who need it, but the quick version is to mount your external storage using StickMount and then navigate to "External Storage -> USBStorage -> sda1" from within XBMC. Files show up and play smoothly.
Click to expand...
Click to collapse
I have used stickmount in the past (actually purchased it) and this is what I was waiting for. As long as storgae can be mounted, it will be selectable in not only XBMC, but emulators, etc. Now I can buy the FireTV Thanks for confirming!
Is there automount? When plugging in a usb to my nexus 7 with stickmount installed it automounts the usb drive.
154
garvani said:
Is there automount? When plugging in a usb to my nexus 7 with stickmount installed it automounts the usb drive.
Click to expand...
Click to collapse
No, it does not automount. You have to manually mount the drive from within StickMount.
fireTVnews.com said:
No, it does not automount. You have to manually mount the drive from within StickMount.
Click to expand...
Click to collapse
I gathered that from your instructions.
The question was more as to why there isn't automount. Will have to investigate that as it seems backwards that my 2 year old copy of stickmount will automount whereas this one doesn't, having to perform all those steps is a bit annoying every time you plug in a usb drive..
Thanks for the write up though.
garvani said:
I gathered that from your instructions.
The question was more as to why there isn't automount. Will have to investigate that as it seems backwards that my 2 year old copy of stickmount will automount whereas this one doesn't, having to perform all those steps is a bit annoying every time you plug in a usb drive..
Thanks for the write up though.
Click to expand...
Click to collapse
I don't think it's an issue with SickMount not having the feature. I've tried 2 other USB mounting apps, both explicitly advertise auto mounting. While they both were able to mount the USB drive, neither of them auto mounted.
As for manual mounting being annoying, all you really need to do is load StickMount and click "Mount". The drive gets mounted to the same place, so all your apps (including XBMC) only need to be setup once.
fireTVnews.com said:
I don't think it's an issue with SickMount not having the feature. I've tried 2 other USB mounting apps, both explicitly advertise auto mounting. While they both were able to mount the USB drive, neither of them auto mounted.
Click to expand...
Click to collapse
All that is needed is a script to run in the background and look for the event. The firetv already detects the drive correctly on connection, look in dmesg and you will see something like below when I plugged in a usb hard drive.
Code:
sb 4-1: new high-speed USB device number 3 using msm_hsusb_host
usb 4-1: New USB device found, idVendor=14cd, idProduct=6116
usb 4-1: New USB device strings: Mfr=1, Product=3, SerialNumber=2
usb 4-1: Product: USB Mass Storage Device
usb 4-1: Manufacturer: Generic
usb 4-1: SerialNumber: 116AC2101219
scsi0 : usb-storage 4-1:1.0
scsi 0:0:0:0: Direct-Access Mass Storage Device PQ: 0 ANSI: 0
sd 0:0:0:0: [sda] 156301486 512-byte logical blocks: (80.0 GB/74.5 GiB)
sd 0:0:0:0: Attached scsi generic sg0 type 0
sd 0:0:0:0: [sda] Write Protect is off
sd 0:0:0:0: [sda] Mode Sense: 03 00 00 00
sd 0:0:0:0: [sda] No Caching mode page present
sd 0:0:0:0: [sda] Assuming drive cache: write through
sd 0:0:0:0: [sda] No Caching mode page present
sd 0:0:0:0: [sda] Assuming drive cache: write through
sda: sda1
sd 0:0:0:0: [sda] No Caching mode page present
sd 0:0:0:0: [sda] Assuming drive cache: write through
sd 0:0:0:0: [sda] Attached SCSI disk
Empty folder
All I get with stickmount on my external drive is an empty folder, which I assume has something to do with it having EXT3? I tried a usb-stick with ntfs, and it worked. Or am I missing something?
treqie said:
All I get with stickmount on my external drive is an empty folder, which I assume has something to do with it having EXT3? I tried a usb-stick with ntfs, and it worked. Or am I missing something?
Click to expand...
Click to collapse
Also, I mounted this manually, which works. So I thought I could put this into vold.fstab and ditch stickmount, but when saving, it says the system is read only?
treqie said:
Also, I mounted this manually, which works. So I thought I could put this into vold.fstab and ditch stickmount, but when saving, it says the system is read only?
Click to expand...
Click to collapse
Yes you need to remount the system with write access...
Code:
su
mount -o rw,remount /dev/block/platform/msm_sdcc.1/by-name/system /system
Check if it was mounted in read-write mode (rw):
Code:
mount | grep system
Should return
Code:
/dev/block/platform/msm_sdcc.1/by-name/system /system ext4 rw,relatime,data=ordered 0 0
Now go make your changes then once done remount it as read-only again:
Code:
mount -o ro,remount /dev/block/stl12 /system
roligov said:
Yes you need to remount the system with write access...
Code:
su
mount -o rw,remount /dev/block/platform/msm_sdcc.1/by-name/system /system
Check if it was mounted in read-write mode (rw):
Code:
mount | grep system
Should return
Code:
/dev/block/platform/msm_sdcc.1/by-name/system /system ext4 rw,relatime,data=ordered 0 0
Now go make your changes then once done remount it as read-only again:
Code:
mount -o ro,remount /dev/block/stl12 /system
Click to expand...
Click to collapse
Yes, I just figured that out. But I'm stuck with how it should be in vold.fstab.
Code:
dev_mount usbdisk /storage/usbdisk auto /devices/platform/msm_hsusb_host.0
That's what I found when googling, but that doesn't work. Not sure if there's anything specific to firetv, that should be changed.
Works for me - no changes
Strange - Stickmount(free ver) auto-mounts on my FTV with notification.
Using autopilot to start SPMC.
[email protected] said:
Strange - Stickmount(free ver) auto-mounts on my FTV with notification.
Using autopilot to start SPMC.
Click to expand...
Click to collapse
Also using ext3?
treqie said:
Also using ext3?
Click to expand...
Click to collapse
NO -
It's a 32GB Transcend with fat32.
It auto-mounts on boot-up, but not when plugged in.
[email protected] said:
NO -
It's a 32GB Transcend with fat32.
It auto-mounts on boot-up, but not when plugged in.
Click to expand...
Click to collapse
I guess it must have a problem with ext3 then.
Has anybody had success with downloading apps and games directly to the usb mount? Is it possible yet to substitute the usb slot for the main storage on the box?
Sent from my iPhone using Tapatalk
Where to download stickmiount
Where do I get it the apk safe and free?
Esso1001 said:
Has anybody had success with downloading apps and games directly to the usb mount? Is it possible yet to substitute the usb slot for the main storage on the box?
Click to expand...
Click to collapse
I'm wondering this as well .
TriOptimum said:
I'm wondering this as well .
Click to expand...
Click to collapse
Pretty sure that will require a custom kernel, i know on my phone i had to use a kernel that had extsd swap support to swap my sd card with internal storage.
Sent from my SCH-I605 using XDA Premium 4 mobile app
Hemorrdroid said:
Pretty sure that will require a custom kernel, i know on my phone i had to use a kernel that had extsd swap support to swap my sd card with internal storage.
Sent from my SCH-I605 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Wouldn't it be possible to use the android equivalent of a symlink to do this? I thought I recalled doing this on phones that didn't support installing apps to external storage awhile back.
My search-fu seems to be lacking but I can't locate information on resizing the partition of an external disk.
I have a shield 2019 pro. I had been using a 128gb San Disk Extreme Pro USB drive and decided to upgrade to a Samsung PSSD T7 1TB drive. I successfully DD'd an image file and copied it to the new drive without issue. The Shield works just fine with the new SDD, but now I can't figure out how to resize the partition.
I saw the post here about someone successfully doing the same, but they didn't give any real details. I'm a Linux user and figured they used standard tools to resize, but Neither GParted or Gnome-Disks seem to know how to handle the Android partition.
Are there any guides around for this, or is it even possible?
Thanks!