Related
Hi guys
I'm having some extremely irritating problems with my A500. It doesn't detect any external sd card I've tried so far. It says external sd is unavailable under storage in settings and the external_sd folder is empty in root/mnt. I've tried 3 different cards so far with no success. Anyone have a any advice for me on how to mount the card? I think the problem might be that it doesn't get mounted when I insert it. I can't root because the GingerBreak mod that's been posted needs an external card to work. So maybe some advice on how to root some other way? Then I can try restore a stock image and see what happens.
I had to insert mine and then reboot the tablet for mine to show inside of a file manager.
Sent from my A500 using XDA Premium App
lawmangrant said:
I had to insert mine and then reboot the tablet for mine to show inside of a file manager.
Sent from my A500 using XDA Premium App
Click to expand...
Click to collapse
Hey, thanks for the tip. I forgot to add it to my original post. I've tried rebooting with all 3 of the cards I have. I'm starting to think it's a hardware problem...
Have the cards you're testing been formatted NTFS or FAT32? If NTFS they probably won't work without some help.
The stock device only deals with FAT32 mSD cards; I haven't tried the NTFSMount app from the Dev forum on an NTFS-formatted card yet, only USB devices.
Vereynn said:
Have the cards you're testing been formatted NTFS or FAT32? If NTFS they probably won't work without some help.
The stock device only deals with FAT32 mSD cards; I haven't tried the NTFSMount app from the Dev forum on an NTFS-formatted card yet, only USB devices.
Click to expand...
Click to collapse
Hey. I've formatted the cards multiple times, to FAT32 every time. Might try exFAT tomorrow just to see what happens.
exFAT didn't work. Not that I expected it to, lol. Maybe the GingerBreak apk can be modified to use the usb storage instead of the external sd. Any idea where I can get the source code to take a look at?
If you've tried multiple cards, all FAT32 and all work on other devices, I'd return the tablet while you can, sounds like a hardware problem indeed
Slight problem with the returning, lol. I live in South Africa and ordered my tab from the USA since my own country is so backwards. I don't really mind not having an external sd card, I just wanna root again since almost all the apps I use need root. I'm considering returning, even if it's gonna take a lot of effort, time and money...
EDIT - Another reason I can't return it (and this is a horrible thing) is that SuperUser Permissions is still installed. The recent update made me lose root. So I'm kinda stuck with this app that's proof that I voided my warranty. The only way to get rid of SuperUser is to use some apps that all need root. To get root I need the external sd to work. To get that to work I need to send it for repairs. A very messed up situation
I'm almost positive that it's a hardware issue now. Even when I try to do an update.zip from recovery mode it can't find the file even though it's on the card. Let's hope they don't see the SuperUser app when I return it...
I thought about maybe waiting for Acer to release an update that will unlock the bootloader. But since the SD card slot isn't working I won't be able to install the update. That so much depends on one little slot amazes me. If you wanna know what the single point of failure for an Android device is, look no further.
I know some android tabs came out without external SD card support. I live in the uk and have a 32GB version and the SD card worked out the box. Maybe you have to wait for an update. Just my 2c though. You won't need an external SD to receive OTA updates though.
Sent from my A500
Here's an image of what recovery mode says when I select Install Update from external source. Seems the system can't mount the card. Sigh
I like that message at the end.... "Install from sdcard complete."
You had rooted before the update, which means it had to have seen the sdcard then. So it's unlikely that the hardware just went bad. Are the sdcards your trying of different sizes, classes, and/or manufacturer?
I'd go with the same sdcard you used when you rooted before and reformat it using the HP USB Format tool. Selecting fat32, of course. And don't select quick format. See if that helps. Sorry if I missed somethiing relevent above.
Here's the link to the HP first tool. http://download.cnet.com/HP-USB-Disk-Storage-Format-Tool/3000-2094_4-10974082.html
Sent from my A500 using Tapatalk
Lol, the "fake it till you make it" strategy. Fail Google.
I've tried it with the original SD and two other ones. My guess is some app tried to mount the external SD in /mnt/sdcard and messed up some associations or dependencies or something.
I'm amazed. After everything I've tried it suddenly worked. I was busy in settings and accidentally selected storage. And there it was in all its glory... A working external sd card! I'm rooted again, backed up and ready to roll!
To anyone finding this thread hoping for answers for a similar problem: It was a hardware problem indeed. I fixed it myself by opening the tab and bending the MicroSD slot's pins back into place.
Hello first I want to say a big THANK YOU to everyone that has put time and effort into making the Nookie what it is today....but I have a noob question.
I recently got a 16gb micro SD and can successfully get the 0.6.8 Nookie to run on my nook color, my problems start when I try to "recover" my other 13gb's. Before I get burned and tossed aside I have checked
http://forum.xda-developers.com/showthread.php?t=922324&page=92
http://forum.xda-developers.com/showthread.php?t=883175&highlight=partition&page=103
and about 5 other pages and they all say the same thing..use EASEUS, grab the slide bar and voila. It appears to work but when I install it in the NC it either becomes very unstable or just boots to the NC as if the SD card was not there.
Anyone have any ideas?
Jeep_Lover said:
Hello first I want to say a big THANK YOU to everyone that has put time and effort into making the Nookie what it is today....but I have a noob question.
I recently got a 16gb micro SD and can successfully get the 0.6.8 Nookie to run on my nook color, my problems start when I try to "recover" my other 13gb's. Before I get burned and tossed aside I have checked
http://forum.xda-developers.com/showthread.php?t=922324&page=92
http://forum.xda-developers.com/showthread.php?t=883175&highlight=partition&page=103
and about 5 other pages and they all say the same thing..use EASEUS, grab the slide bar and voila. It appears to work but when I install it in the NC it either becomes very unstable or just boots to the NC as if the SD card was not there.
Anyone have any ideas?
Click to expand...
Click to collapse
I use Lexar Bootit ....a free utility...to format and flip the bit that says its a removeable drive, then your windows pc drive management can see and format it as full capacity fat32.
Hey thanks for the tip, unfortunately it won't work. I forgot to mention that I followed this tutorial ..... and updated my driver (saved my original Windows just in case) to a hitachi driver and now I can switch my SD memory card forth "removable" to "logical" and back when needed. Once I get it as a logical drive I was EASEUS to increase the size of partition 4 (SD Card)..but again no dice!!!
Seeing that I am a noob I can't post the link to the tutorial but I'll say it worked like a charm and when I want to go back to the original I just need to "roll back" the driver.
Well, a couple of things:
Are you using a Sandisk card? Sandisk class 2 and 4 cards have been found much more stable than most others for running a ROM from SD, and problems with SD installs often go back to the card.
Any particular reason you went with Nookie Froyo? It has pretty much fallen out of use since the NC's stock OS was updated to Froyo in May. If you want an SD install, there's a simpler, size-agnostic method for CM7, which is also a more robust and capable OS and a more advanced version of Android (Gingerbread 2.3.4 rather than Froyo 2.2). I would recommend CM7.1 RC1, or if you're adventurous, Nightly 136.
Taosaur said:
Well, a couple of things:
Are you using a Sandisk card? Sandisk class 2 and 4 cards have been found much more stable than most others for running a ROM from SD, and problems with SD installs often go back to the card.
Any particular reason you went with Nookie Froyo? It has pretty much fallen out of use since the NC's stock OS was updated to Froyo in May. If you want an SD install, there's a simpler, size-agnostic method for CM7, which is also a more robust and capable OS and a more advanced version of Android (Gingerbread 2.3.4 rather than Froyo 2.2). I would recommend CM7.1 RC1, or if you're adventurous, Nightly 136.
Click to expand...
Click to collapse
Thanks for the info unfortunately I am using a 16gb PNY, class 4 and at $15 I couldn't pass it up...looks like I should have done some more reading first. Really I have no clue why I am using the Nookie, my wife said said that was the one she wanted. I think she just likes saying "Nookie", but I'll give the CM7 a go and see what trouble I can get into.
thanks again...
Taosaur...I was able to get the CM7 mod up and running in no time flat. Now the wife wants me to see if I can get bluetooth working.
You said "I was able to get the CM7 mod up and running ...." so I assume you got your problem fixed. That's good.
About bluetooth.
1. Turn off Wifi
2. Power off NC
3. Power on NC
4. Turn on bluetooth
5. Turn on wifi
votinh said:
You said "I was able to get the CM7 mod up and running ...." so I assume you got your problem fixed. That's good.
About bluetooth.
1. Turn off Wifi
2. Power off NC
3. Power on NC
4. Turn on bluetooth
5. Turn on wifi
Click to expand...
Click to collapse
Yep, I had to do the above the first time I turned on bluetooth, but haven't had any trouble toggling it on and off since then. Just open notifications (that broken-circle-and-arrow button on the status bar) and you have toggles there for Wifi, bluetooth, and a couple other things.
@ Taosaur,
I've seen your signature indicate you are running nb136, any change or improvement (both slightly and/or significant) over the previous ones?
Jeep_Lover said:
Thanks for the info unfortunately I am using a 16gb PNY, class 4 and at $15 I couldn't pass it up...looks like I should have done some more reading first. Really I have no clue why I am using the Nookie, my wife said said that was the one she wanted. I think she just likes saying "Nookie", but I'll give the CM7 a go and see what trouble I can get into.
thanks again...
Click to expand...
Click to collapse
Damn! My wife never says "nookie".
votinh said:
@ Taosaur,
I've seen your signature indicate you are running nb136, any change or improvement (both slightly and/or significant) over the previous ones?
Click to expand...
Click to collapse
I haven't done much but read and browse a little since I flashed it, but I haven't noticed any difference from 7.1 RC1, which wasn't really any different from Nightly 102 I had before that. I mostly just flashed this time for the integrated OC/Tweaks kernel, without the video/lag problems that were reported in 132-134.
Thanks for an update, m8
maybe someone can help me, i'm about to loose my mind here trying to figure this out. i'm using a Sandisk class 4 16gb card running CM7 with the OC kernal.Did all of this using the size agnostic install method. everything is working fine but i can't for the life of me figure out how to access the rest of the space on my SD, when i insert the sd card into my PC it just shows up as the 115mb partition. i've tried using EASeus, the lexar bootit, and some other partition tool with no luck. with Easeus i select the 13gb FAT32 partition and make it active and thats it right? does it need to be logical? and which partition am i resizing?
Dr. Light said:
maybe someone can help me, i'm about to loose my mind here trying to figure this out. i'm using a Sandisk class 4 16gb card running CM7 with the OC kernal.Did all of this using the size agnostic install method. everything is working fine but i can't for the life of me figure out how to access the rest of the space on my SD, when i insert the sd card into my PC it just shows up as the 115mb partition. i've tried using EASeus, the lexar bootit, and some other partition tool with no luck. with Easeus i select the 13gb FAT32 partition and make it active and thats it right? does it need to be logical? and which partition am i resizing?
Click to expand...
Click to collapse
None of the above. Windows will only recognize the first partition on a SD card, and when you make a SD bootable, that first partition will be the boot partition. To access the larger storage partition, connect your NC with CM7 running to the PC over USB. Open notifications on the NC, tap through "USB connected" to the USB screen, and "Turn on USB storage." Windows will now detect two storage drives, NookColor (the system partition, where apps install) and SDcard (the large storage partition).
The only time you'll want to remove the card from the NC and plug it into your PC is when you want to put on a new cm...zip update file to flash a new ROM.
I used the size agnostic install method with a 16gb PNY calss 4 SD and after all the steps were completed I was showing 13.8gb free for my SD card when I looked at in on the NC. Not believing my eyes I pulled it out and looked at it with EASUS and it showed partition 4 as 13.8gb (utilizing all the cards remaining space). I then downloaded a few things and added a few books for my wife and the space shrank to 13.4gb. As stated above your computer wont show it.
In short have you looked on the NC under "Storage" (I think that is were I found it) and verified you don't have the full capacity already?
Also there is another method I needed to use when I was messing with an earlier version (Nookie) that allowed me to see an SD card as a "Local Device" so windows would let me see all partitions on the hard drive. I can't post a link until I have more posts but email me and I can send you the link if interested.
Taosaur said:
None of the above. Windows will only recognize the first partition on a SD card, and when you make a SD bootable, that first partition will be the boot partition. To access the larger storage partition, connect your NC with CM7 running to the PC over USB. Open notifications on the NC, tap through "USB connected" to the USB screen, and "Turn on USB storage." Windows will now detect two storage drives, NookColor (the system partition, where apps install) and SDcard (the large storage partition).
The only time you'll want to remove the card from the NC and plug it into your PC is when you want to put on a new cm...zip update file to flash a new ROM.
Click to expand...
Click to collapse
thanks, well that got me some where. i connected nook to PC, turn on storage mode and it shows E/F drive. click either one and it says "Please insert disk into removable disk E/F" so then i turn off debugging and the nook color internal memory pops up as drive F, while clicking on drive E gives me the same error as above. any ideas? btw i'm on Windows 7 64bit, do i need any kind of special drivers or anything?
It is because windows will only allow you to manipulate the first partition on an SD card...even if it "sees" the other partition as another card it will not do anything with it. EASEUS will show you all the partitions on the SD.
The only way I got Windows to see all the partitions and do anything with them was to change my driver via the "Hitachi fix" If you google Hitachi driver SD card you will find it. I used this site and even though it is long it did exactly as advertised and now I install this driver when I need to format just the partition of an SD card and then "roll back" the driver when I'm done. It tricks windows into thinking it is a local device instead of removable. www/1src/com\forums\showthread.php?t=133718
change / to .
\ = /
I can't post a link as I'm still a noob...
Jeep_Lover said:
It is because windows will only allow you to manipulate the first partition on an SD card...even if it "sees" the other partition as another card it will not do anything with it. EASEUS will show you all the partitions on the SD.
Click to expand...
Click to collapse
S/he really doesn't need Windows to do anything with those other partitions--I suspect messing with them was where s/he went wrong in the first place.
Dr. Light said:
thanks, well that got me some where. i connected nook to PC, turn on storage mode and it shows E/F drive. click either one and it says "Please insert disk into removable disk E/F" so then i turn off debugging and the nook color internal memory pops up as drive F, while clicking on drive E gives me the same error as above. any ideas? btw i'm on Windows 7 64bit, do i need any kind of special drivers or anything?
Click to expand...
Click to collapse
I suggest you start over, because you probably damaged your install when you were messing with the partitions earlier. I'm also using Win7x64, and no, I didn't need any special drivers. Delete all partitions except "SDcard" in EASEUS, expand that partition to the whole card, then write verygreen's image to the card again and re-install. At that point, you should be able to access storage over USB from CM7 without turning off debugging or taking any other special steps other than "Turn on USB storage."
Taosaur said:
S/he really doesn't need Windows to do anything with those other partitions--I suspect messing with them was where s/he went wrong in the first place.
I suggest you start over, because you probably damaged your install when you were messing with the partitions earlier. I'm also using Win7x64, and no, I didn't need any special drivers. Delete all partitions except "SDcard" in EASEUS, expand that partition to the whole card, then write verygreen's image to the card again and re-install. At that point, you should be able to access storage over USB from CM7 without turning off debugging or taking any other special steps other than "Turn on USB storage."
Click to expand...
Click to collapse
alright i'll give it a shot when i get home from work. is the verygreen image the same one found in the CM7 size agnostic SD thread?
"http://crimea.edu/~green/nook/generic-sdcard-v1.3.img.gz"
and when i delete all partitions except for "SDCARD" do i need to make that partition logical or active or anything?
again thanks for your help.
Dr. Light said:
alright i'll give it a shot when i get home from work. is the verygreen image the same one found in the CM7 size agnostic SD thread?
"http://crimea.edu/~green/nook/generic-sdcard-v1.3.img.gz"
Click to expand...
Click to collapse
Yep, verygreen is the author of that thread and image.
Dr. Light said:
and when i delete all partitions except for "SDCARD" do i need to make that partition logical or active or anything?
Click to expand...
Click to collapse
No, in fact you might be able to write the image without messing around in EASEUS at all--I'm just not sure if WinImage (or whatever) would write to the whole card or just one partition. I know if you tried to format it, Windows would only format the boot partition.
Hi,
I'm trying to keep up with the thread on the development forumm but theres to mach going on there.
Can someone please explain what's that they are saying that the rom is locking the sd card and the tonight there will be another rom?
What all this about? whats the difference between the current rom and the new one?
Thanks
it locks the sd card meaning the sd can no longer be used as a regular sd card and will only work on a windows phone 7 device
yeah, at the moment, you have two choices
use the V1 ROM and be able to upgrade your ROM, you can install android still, you can not upgrade to 7712 / 7720 AND have access to your SD card UNLESS you lock the SD card
the second choice is use V2 ROM, this will lock your SD card from the start and enable updates to be much easier
Locking the SD card means that it can not be used at all on another device, Currently there isnt any software that can format the protected portion of the card, some hardware devices can format it, Some Nokia phones, some camera
Locking is actually very useful unless you want android on the same SD card
If you do want to use Android as well then get a second SD card and pop it in when you want to use it.
WP7 its self CAN clear a protected SD card but it will keep it protected, so you can reflash new WP7 ROMS with protected SD cards without any issues at all, but it will always be protected unless you use a Nokia type device.
You can also format a locked card using your wm6.5 on hd2;-)
Sent from my Schubert using XDA Windows Phone 7 App
Thank you all!
pakure said:
You can also format a locked card using your wm6.5 on hd2;-)
Sent from my Schubert using XDA Windows Phone 7 App
Click to expand...
Click to collapse
Not much use when you've got wp7 on it hey (unless you have 2 hd2's of course )
pakure said:
You can also format a locked card using your wm6.5 on hd2;-)
Sent from my Schubert using XDA Windows Phone 7 App
Click to expand...
Click to collapse
No, it cannot. It says it is damaged on my topaz.
A buggered up partition table can be fixed with a propper format which is what 99% of people say "fixes" a broken card.
However, a "Protected" Card can not be formatted in this way, im have a chat with the SD association at the moment to see whats what, so far it is a software limitation on the PC that is stopping us clearing that data, in short if someone writes a program to do it, it will do it, the question is how!
can you guys see the partition on a PC partition app but not modify it? Or can you not even see the partition?
orangekid said:
can you guys see the partition on a PC partition app but not modify it? Or can you not even see the partition?
Click to expand...
Click to collapse
if a SD card has been locked its essentially unreadable in anything but the device that it was locked in, if you plug a locked (protected) SD card in a PC it will be detected in device manager but windows will not beable to access it, the SD association is a bit vague in their replys but apparently some OSs are able to format a protected card, MS isnt one of them unless there is undocumented flags that can be used at the command prompt, the best bet is probably Linux, I hate using Linux as a desktop but i do have it running as a VM server so i might give that a try a bit later
The funny thing is, its not complicated to do it (apparently) its just no one has really used the protected feature set of the SD standard
Also, (apparently, some SD cards use the protected area to store information other than the encryption key for the whole card, apparently this information might be used in read /write operations on the card, clearing the protected area to remove the SD card lock might have a negative impact on the cards performance.
pakure said:
You can also format a locked card using your wm6.5 on hd2;-)
Sent from my Schubert using XDA Windows Phone 7 App
Click to expand...
Click to collapse
Sorry, but it is confirmed. Windows Mobile 6.5 can not. Apparently Ubuntu does, I am testing!
dazza9075 said:
if a SD card has been locked its essentially unreadable in anything but the device that it was locked in, if you plug a locked (protected) SD card in a PC it will be detected in device manager but windows will not beable to access it, the SD association is a bit vague in their replys but apparently some OSs are able to format a protected card, MS isnt one of them unless there is undocumented flags that can be used at the command prompt, the best bet is probably Linux, I hate using Linux as a desktop but i do have it running as a VM server so i might give that a try a bit later
The funny thing is, its not complicated to do it (apparently) its just no one has really used the protected feature set of the SD standard
Also, (apparently, some SD cards use the protected area to store information other than the encryption key for the whole card, apparently this information might be used in read /write operations on the card, clearing the protected area to remove the SD card lock might have a negative impact on the cards performance.
Click to expand...
Click to collapse
Interesting. I did a few experiments and a whole heap of reading about this yesterday (Osx doesnt recognise the card either btw):
The card became locked during the update process from 7712 to 7720 during one of the many hard resets i did whilst installing the cabs (the sd fix cab was the last cab i installed). My mistake was not bothering to change the language from its default (English USA to English UK) so it would appear the card is also not only locked to a particular device but its language also.
One could test this by inserting the card, hard resetting and choosing USA as its language, however, it took 4 hours to get the device working to 7720 so im not doing that just yet; so i tried something else.
I put the encrypted card into my hd2, entered magldr and cleared the partition using services. I then entered usb mass storage and connected the device to my PC (win 7 x64). Whilst the card was not recognised in "my computer", if you look in camera&scanners in control panel, you will see magldr is recognised as a mass storage device but the device drivers for this fail to install properly. This is probably due to the "unknown" partition taking up the full capacity of the micro sd card and why it is not recognised by the PC hence it cannot be used for storage.
Unfortunately this also means no partition software will recognise the card, nor is it recognised in any digi camera, even after allegedly clearing the partitions via magldr.
I then had a thought would a nokia emulator work in unlocking the card? to which i havent researched any further as yet.
**EDIT** Apparently someone has decrypted and formatted a card using Ubuntu, im off to download and try it
**EDIT 2** not having much luck with ubuntu either, card not recognised........
same here, ubuntu disk manager (11.04 32-bit) shows sd card but 2.2 TB and can't format the drive or volume (i tried the same to clear mbr using magldr), ubuntu is not working
WEll, they havent been much further use, all they say is that is perfectly possible to do with software, the APIs have been there for years, its just that no one has ever really paid much attention to it, with the exception of Sat-Navs, professional Music gear etc.
Ive not had a chance to play with Linux yet but i would imagin that you need to think lower level than partition / MBR levels
From what i can gather from their cryptic responses is that when a SD card is setup to use the Secure feature, the device creates a key in the secure section, only that device can then access that section, the storage space on the card is then encrypted using that key, there is no way short of cracking the key to get access to either the secure section or the storage section. However, when you use an OS or Utility that makes use of the Secure protected area its possible to clear it, this would clear all the data obviously off the card, even disk analysers wouldnt be able to see it as it would still be encrypted.
What is concerning is that the Manufacturers have grown used to this special area and use it, apparently this area is used for IO operations, (probably some kind of cache or superfetch) this speeds things up by predicting what you are going to access next
What concerning is, if you have a class 10 device that as we all ready know uses methods to speed up sequential speeds to get that class rating, IF we manage to clear that protected area will the card be effected in terms of speed, conversly, could it improve random access speeds (WP7 essential) if its not farting around trying to predict sequential IO ops!
dazza9075 said:
yeah, at the moment, you have two choices
use the V1 ROM and be able to upgrade your ROM, you can install android still, you can not upgrade to 7712 / 7720 AND have access to your SD card UNLESS you lock the SD card
Click to expand...
Click to collapse
Of course you can update!
I am using V1 and have the 7720 build
has anyone been able to (in windows or linux) copy the partition on the card without modifying or formatting or anything? Just copying the partition to another card?
orangekid said:
has anyone been able to (in windows or linux) copy the partition on the card without modifying or formatting or anything? Just copying the partition to another card?
Click to expand...
Click to collapse
Nope, the card is not recognised, im working on it.
timmymarsh said:
Nope, the card is not recognised, im working on it.
Click to expand...
Click to collapse
I'm going to try as well. If we can just get a recognition/copy to work, then we can do dual-boot again. There has to be some way to copy the entire partition.
Finalforce1111 said:
Of course you can update!
I am using V1 and have the 7720 build
Click to expand...
Click to collapse
read it again,
note the big "AND"
you can not dual boot Mango 7712/7720 and android on V1
you can not dual boot at all with V2
you cant copy encrypted partitions, it doesnt work that way, its not like making a encrypted folder, its on a much lower level than that, its either encrypted or its not, you either have Mango or you have Nodo AND android
I still cant get the Protected SD formatted, im wondering if its reliant on the card reader supporting those commands.....
Mm the secret I think is gaining access to the hidden part of the card that contains the encryption key. I'm still working on Ubuntu and have a lead to follow up on.
Your right about the droid dual boot, this isn't my intention so others shouldn't get their hopes up ;-)
Sent from my HD2 Mango 7720 using XDA Windows Phone 7 App
I just picked up a Xoom last week and have been messing with it since and ran into a problem.
I have put in two different SD cards into the top slot and none of them are showing up when browsing with File Manager HD. When I go into Settings->Storage, under SD card it is greyed out and says insert an SD card for mounting.
I don't mind wiping the card, but how do I get the Xoom to recognize the card?
Have u formated it to fat 32?
Sent from my GT-I9100 using XDA App
I just took it out of my phone and tried to stick it in.
The card works fine on my phone and on my Gtab.
I haven't rooted it either.
Ok, so now under SD Card it lets me select Mount SD Card, but nothing happens. Why is it so hard to use this feature?
snowwhite007 said:
Have u formated it to fat 32?
Sent from my GT-I9100 using XDA App
Click to expand...
Click to collapse
wow, this sucks monkey balls.
my gtablet running an HC ROM, which doesn't even support HC, can have access to the SD card fine and is changeable between my phone/camera/pc, but for it to work with the XOOM has to be formatted to FAT32. Also, I can't write to it unless I root.
what's the point of the SD card then?
Mine worked straight from a card I had in a LG EnV Touch. I don't know what the deal is. Has your XOOM just come back from the upgrade or is it the WiFi version?
Sent from my DROID2 using xda premium
couchmonkey said:
wow, this sucks monkey balls.
my gtablet running an HC ROM, which doesn't even support HC, can have access to the SD card fine and is changeable between my phone/camera/pc, but for it to work with the XOOM has to be formatted to FAT32. Also, I can't write to it unless I root.
what's the point of the SD card then?
Click to expand...
Click to collapse
Without root, you can access music, video, pdfs other files from your micro sdcard...up to 32GB, which adds lots of storage. There is no apps-to-sd in Honeycomb, but if you root, you can have R/W access to the micro sdcard and save your nandroids to it, TB backups, write files to it, etc. When you root, you'll find the micro sdcard at mnt/external1, on same directory level as sdcard (32GB internal storage) and mnt/usbOTG. Xoom uses micro sdcard for media storage/playback in non-rooted state and that's fine. But if you root you have a hell of a lot more features. that's our reward for the work (pain) of rooting.
okantomi said:
Without root, you can access music, video, pdfs other files from your micro sdcard...up to 32GB, which adds lots of storage. There is no apps-to-sd in Honeycomb, but if you root, you can have R/W access to the micro sdcard and save your nandroids to it, TB backups, write files to it, etc. When you root, you'll find the micro sdcard at mnt/external1, on same directory level as sdcard (32GB internal storage) and mnt/usbOTG. Xoom uses micro sdcard for media storage/playback in non-rooted state and that's fine. But if you root you have a hell of a lot more features. that's our reward for the work (pain) of rooting.
Click to expand...
Click to collapse
so I'm trying to figure out the best way to root.
which way is it?
couchmonkey said:
so I'm trying to figure out the best way to root.
which way is it?
Click to expand...
Click to collapse
This is the best way I know: http://forum.xda-developers.com/showthread.php?t=1249798
It can seem pretty daunting but we all did it, some have done it multiple times, and so can you.
In the first section where it talks about setting up adb on your pc, there's a link to an alternate approach to setting up the files. It's supposed to give you just the files needed for rooting and nothing more. I never tried it but you could if you want to...may save a step or two.
Anyway, this guide should have everything you need.
Take your time, print out the instructions and read them carefully. The Xoom was made to be rooted, it's just a complex device, so there's no 'one click' magic.
Hey Guys,
I asked @kokotas to help me figure out a way to make a Patch to extend the Internal Memory as for me, due to the size of the high-end Applications and Games, is too limited 16GB, 11,70GB available only, on our Z1.
So my first Idea was to sacrifice 16Gb Internal Memory and use 64GB External SD Memory formatted in EXT4 where all the Data will be stored.
To do so we have to understand few thing and how is the structure of the Z1 Kernel is made and try to extract "ramdisk.cpio" where we can edit "init.rc" and change the line "/data mount"
As for the kernel "Autopsy" we used @krabappel2548 kernel build, I hope he is fine with that.
From what we know, the recovery is injected in the boot.img and this makes things more complicated.
Are all kernels built in this way? Even the stock ones?
Also, is there a specific rule in the way of naming the included ramdisks?
I attached a picture to make things more clear.
Any help will be appreciate.
eclyptos said:
Hey Guys,
I asked @kokotas to help me figure out a way to make a Patch to extend the Internal Memory as for me, due to the size of the high-end Applications and Games, is too limited 16GB, 11,70GB available only, on our Z1.
So my first Idea was to sacrifice 16Gb Internal Memory and use 64GB External SD Memory formatted in EXT4 where all the Data will be stored.
To do so we have to understand few thing and how is the structure of the Z1 Kernel is made and try to extract "ramdisk.cpio" where we can edit "init.rc" and change the line "/data mount"
As for the kernel "Autopsy" we used @krabappel2548 kernel build, I hope he is fine with that.
From what we know, the recovery is injected in the boot.img and this makes things more complicated.
Are all kernels built in this way? Even the stock ones?
Also, is there a specific rule in the way of naming the included ramdisks?
I attached a picture to make things more clear.
Any help will be appreciate.
Click to expand...
Click to collapse
1. Sony doesn't have a recovery partition in their phones hence developers add the recovery in the ramdisk. Also stock sony kernels doesn't have a recovery included by default only bootloader/flashmode.
2. You can't adjust the 16gb internal partition without diving deeply into the bootloader. The NAND partition profiles are hardcoded in the bootloader so modifying even just a little bit of info in the partition of the NAND would brick your device. The only way I could possibly suggest to try is hijacking the fstab and ramdisk to unmount the internal storage and mount the external storage on init. But if your issue is only about disk space I suggest you leave the internal storage and just symlink the obb folder instead of hijacking the whole internal storage. And BTW the disk IO of the internal storage is worlds apart compared to your microsd card no matter what class it is so it would be very unefficient if you use your microSD card as internal. IMHO reading the dalvik-cache 1 by 1 on startup would be pretty slow! Same goes for reading the byte code of an app once you open it.
Riyal said:
1. Sony doesn't have a recovery partition in their phones hence developers add the recovery in the ramdisk. Also stock sony kernels doesn't have a recovery included by default only bootloader/flashmode.
Click to expand...
Click to collapse
We know that. If there will be a Partition for recovery it will be much more easy and safe. That why we also used a Kernel with recovery implemented.
Riyal said:
2. You can't adjust the 16gb internal partition without diving deeply into the bootloader. The NAND partition profiles are hardcoded in the bootloader so modifying even just a little bit of info in the partition of the NAND would brick your device.
Click to expand...
Click to collapse
We trying and this is the risk of everybody who flashing a Custom Kernel.
Riyal said:
The only way I could possibly suggest to try is hijacking the fstab and ramdisk to unmount the internal storage and mount the external storage on init. But if your issue is only about disk space I suggest you leave the internal storage and just symlink the obb folder instead of hijacking the whole internal storage.
Click to expand...
Click to collapse
Maybe not the whole internal storage but implement the external SD with the internal?
Riyal said:
And BTW the disk IO of the internal storage is worlds apart compared to your microsd card no matter what class it is so it would be very unefficient if you use your microSD card as internal. IMHO reading the dalvik-cache 1 by 1 on startup would be pretty slow! Same goes for reading the byte code of an app once you open it.
Click to expand...
Click to collapse
I know the difference between Internal and External Storage. Yes the internal bandwidth is higher but like I said is worth the sacrifice, or try. Best solution will be System and Apk on Internal and link the SD to use there all Data. This is more efficient that a third Apps like Link2sd or kind of. BTW, I don't think it will be so slow but we have to try. The idea have to be made to improve what next.
So we need more Ideas, do you have any?
We know that. If there will be a Partition for recovery it will be much more easy and safe. That why we also used a Kernel with recovery implemented.
We trying and this is the risk of everybody who flashing a Custom Kernel.
A: This isn't about risk this is a fact. Once you successfully manage to alter the partition table of the built in NAND you're sure to get a hard brick from doing this.
Maybe not the whole internal storage but implement the external SD with the internal?
A: Implementing internal storage with external to support it is possible but limited. Like I said you could symlink the obb and Android folder to the external storage. That way you can allocate some of the storage space to data, dalvik etc. and the data files to the external SD which uses the most resources.
Hmm, changing the partition table has been successfully done on the xperia T
http://forum.xda-developers.com/showthread.php?t=2147997
I am not an expert here, but is this what you are talking about,
What benefit would this give a user?
Sent from my C6903 using xda app-developers app
gregbradley said:
I am not an expert here,
Click to expand...
Click to collapse
Me either, @kokotas is the Master here and all thanks should go to him for help me with this, actually the picture is of his work.
gregbradley said:
Hmm, changing the partition table has been successfully done on the xperia T
http://forum.xda-developers.com/showthread.php?t=2147997
Click to expand...
Click to collapse
We do not try to repartitioning the Sony Z1 internal memory to get a recovery bootable from different partition, which still a very good idea to develop for Z1. We try to mount the External SD instead of the Internal to expand the storage for the Z1, and here we need a patch. If kind of patch like that will really work, with some help, anyone just will format the SD in EXT4 and use what like he like, 32/64GB.
So we will be glad even to involve more "Programmers" to help us make it true.
So any way to let this work?
Jay794 said:
What benefit would this give a user?
Click to expand...
Click to collapse
Expand storage. You will be able to format a 64GB, micro SD in 2 Partitions and use 32GB by the System and 32GB like a normal SD, for example, and it will be managed by the system and not by Apps. So instead of 11,70GB you will have 30GB in System.
Surely this will just make accessing the SD card data really slow? Even with a class 10 running games off the SD card would be laggy as hell
Sent from my C6903 using xda app-developers app
Jay794 said:
Surely this will just make accessing the SD card data really slow? Even with a class 10 running games off the SD card would be laggy as hell
Click to expand...
Click to collapse
Thank you for your Opinion. Is not your problem.
Expert Request Please..
Can someone who know more than me just have a look on the attachment and answer few question, unanswered form post 1.
..for Z1
1) Are all kernels built in this way? Even the stock ones?
2) Also, is there a specific rule in the way of naming the included ramdisks?
3) Do all kernels use the sbin folder?
4) Is ramdisk.cpio the default name used in all kernels
Hey, I support the idea, I just don't see how useful it will be
Sent from my C6903 using xda app-developers app
gregbradley said:
Hmm, changing the partition table has been successfully done on the xperia T
http://forum.xda-developers.com/showthread.php?t=2147997
I am not an expert here, but is this what you are talking about,
Click to expand...
Click to collapse
Yes it is possible but not easy... I'm pretty sure the dev that made that had a hard time before he successfully got it. Also I'm pretty sure he has a JTAG box so in case his phone got hard bricked he can easily fix it again. Also IMHO that was already patched by sony on the latest s1boot so I'm sure it's alot harder than before.
Riyal said:
Yes it is possible but not easy... I'm pretty sure the dev that made that had a hard time before he successfully got it. Also I'm pretty sure he has a JTAG box so in case his phone got hard bricked he can easily fix it again. Also IMHO that was already patched by sony on the latest s1boot so I'm sure it's alot harder than before.
Click to expand...
Click to collapse
Yes, he did brick his Xperia T a few times, and the LK kernel was never really taken up because of the risks.
But it does show that it was possible to change the partition table.
As for on the xperia Z1, I don't know
gregbradley said:
Yes, he did brick his Xperia T a few times
Click to expand...
Click to collapse
I can do that.
Only problem with having the SD used all the time for system files is the risk of corruption and or a failed card.
Saying that I had it on the S3 and it worked brilliantly, was a relatively simple script which required init'd support from a custom kernel.
In all fairness, after using folder mount the worries i've had with my internal memory have gone, i'm always over 10GB of space with several really big games installed which would easily take over the whole internal memory.
dladz said:
Only problem with having the SD used all the time for system files is the risk of corruption and or a failed card.
Click to expand...
Click to collapse
Here you sound like Google.
dladz said:
Saying that I had it on the S3 and it worked brilliantly, was a relatively simple script which required init'd support from a custom kernel.
Click to expand...
Click to collapse
I had it on HD2 as well and never had any issues and I had full control of my device, this is what also we looking at, no restrictions and no storage limit on a high-end device. I will be glad to see 64GB recognized as my System Storage instead using Apps on Apps like the Mount Folder.
I play Most Wanted, of curse a bit slow, on mine HD2 so if we get this work we will have 40mb/s in writing and reading, instead of 70mb/s in internal, due to the limitation of the slot. I think even with a kind of transfare like that you will never see any slow down of the performance on your device.
Some Smart One will say now to me "Why then you don't go back to HTC". That's the point! Imagine have Z1 with such a Development and full control of you device.
At last it's a choice of the user if he want apply that patch or not, but I think if this will be possible many will be happy, but like I can see, we don't have much support due to the risk and any Developer will not take this in consideration, or maybe will, but apparently not now.
eclyptos said:
Here you sound like Google.
I had it on HD2 as well and never had any issues and I had full control of my device, this is what also we looking at, no restrictions and no storage limit on a high-end device. I will be glad to see 64GB recognized as my System Storage instead using Apps on Apps like the Mount Folder.
I play Most Wanted, of curse a bit slow, on mine HD2 so if we get this work we will have 40mb/s in writing and reading, instead of 70mb/s in internal, due to the limitation of the slot. I think even with a kind of transfare like that you will never see any slow down of the performance on your device.
Some Smart One will say now to me "Why then you don't go back to HTC". That's the point! Imagine have Z1 with such a Development and full control of you device.
At last it's a choice of the user if he want apply that patch or not, but I think if this will be possible many will be happy, but like I can see, we don't have much support due to the risk and any Developer will not take this in consideration, or maybe will, but apparently not now.
Click to expand...
Click to collapse
I actually probably will be going back to HTC after this phone. Doubt it'll be the M8, although i do like it, the camera is sup par though and i've come accustomed to a decent picture.
dladz said:
I actually probably will be going back to HTC after this phone. Doubt it'll be the M8, although i do like it, the camera is sup par though and i've come accustomed to a decent picture.
Click to expand...
Click to collapse
I know, I try to don't give up on it too but to much to deal with. The camera is good but I was disappointed anyway. So I was thinking about 64GB HTC One, or wait for the next release and I will finally be fine. For the moment I try to deal with Z1, I hope somewhere we will have 64GB system storage , this maybe will change my mind, everything is possible.
eclyptos said:
I know, I try to don't give up on it too but to much to deal with. The camera is good but I was disappointed anyway. So I was thinking about 64GB HTC One, or wait for the next release and I will finally be fine. For the moment I try to deal with Z1, I hope somewhere we will have 64GB system storage , this maybe will change my mind, everything is possible.
Click to expand...
Click to collapse
Have you used folder mount before? It really is a great app and i've not needed the larger internal storage since using it.