Nook HD+ Rebooting (SOD) Issue - Potential Fix Suggestion (Needs Implemented) - Nook HD, HD+ Android Development

Okay, we need to try fix the Nook HD+ rebooting issue.
Some users say its wifi not being able to restart and some say its the sdcard i/o read write issues.
I'm not sure exactly what it is but the sd card can definitely cause issues.
I think the best way to go is not use the sd card at all except for the initial bootloader bypass.
This means once you are in android any i/o errors to the sd card will not cause cm10 to reboot.
If you have just /system on the sdcard then this can help a bit however i/o errors could still cause the system to reboot as the /system partition is on the sd card.
Additionally as a side effect this also means we can swap sd cards in and out inside android without any rebooting. Say you have 2 16gb and have movies on both. You can access both content.
This should work although I am not sure how hard it is.
The partitions would be on sd card and we would have to get cyanoboot to boot from these emmc partitions instead of sdcard.
For rom updates we could write directly to this system partition on emmc.
I think this is the best end result. Though I am not sure if its as easy to get to at the moment.
If it was easier to get rid of the stock nook os on emmc and install cm10 in its place then this is not too much of a loss as I don't feel the nook os is really needed for anything. This is just an alternative.
Although I think if we definitely take the sd card out of the equation it will help greatly with a lot of issues.

sorrowuk said:
Okay, we need to try fix the Nook HD+ rebooting issue.
Some users say its wifi not being able to restart and some say its the sdcard i/o read write issues.
I'm not sure exactly what it is but the sd card can definitely cause issues.
I think the best way to go is not use the sd card at all except for the initial bootloader bypass.
This means once you are in android any i/o errors to the sd card will not cause cm10 to reboot.
If you have just /system on the sdcard then this can help a bit however i/o errors could still cause the system to reboot as the /system partition is on the sd card.
Additionally as a side effect this also means we can swap sd cards in and out inside android without any rebooting. Say you have 2 16gb and have movies on both. You can access both content.
This should work although I am not sure how hard it is.
The partitions would be on sd card and we would have to get cyanoboot to boot from these emmc partitions instead of sdcard.
For rom updates we could write directly to this system partition on emmc.
I think this is the best end result. Though I am not sure if its as easy to get to at the moment.
If it was easier to get rid of the stock nook os on emmc and install cm10 in its place then this is not too much of a loss as I don't feel the nook os is really needed for anything. This is just an alternative.
Although I think if we definitely take the sd card out of the equation it will help greatly with a lot of issues.
Click to expand...
Click to collapse
Edit, decided not to comment after all. For those that read my earlier comment, forgive me, I was being sarcastic.
Sent from my Nook HD+ running CM10 on SD

leapinlar said:
Edit, decided not to comment after all. For those that read my earlier comment, forgive me, I was being sarcastic.
Sent from my Nook HD+ running CM10 on SD
Click to expand...
Click to collapse
leapinlar i read this earlier comment and i can say that sometime and on some situations sarcasm is very good, There was nothing bad. It just opened more viewing angles (i talk about myself).

leapinlar said:
Edit, decided not to comment after all. For those that read my earlier comment, forgive me, I was being sarcastic.
Sent from my Nook HD+ running CM10 on SD
Click to expand...
Click to collapse
For those that may have missed it, I sort of implemented this option. It is a hybrid install that puts /data on internal memory. It indeed does reduce the reboot issue due to the SD. See the link in my signature.
Sent from my Nook HD+ running CM10 on Hybrid SD

leapinlar said:
For those that may have missed it, I sort of implemented this option. It is a hybrid install that puts /data on internal memory. It indeed does reduce the reboot issue due to the SD. See the link in my signature.
Sent from my Nook HD+ running CM10 on Hybrid SD
Click to expand...
Click to collapse
Nice work

Related

partitioning internal sd

hey everyone. so if i partition the internal sd card what exactly am i doing? from what i understand, the g2x has 8gb onboard, 1.5 of that is for apps, and 5 goes to user data. the rest i assume is for android?
so if i create a 2gb partition on the internal sd, what am i changing and what does it do to the rest of the space? do i need to create the other partitions in windows later and format them?
168 views and no replies? anyone??
Ok, let me try to explain this one...
In three words, Don't Do It!!!
Your internal sd card is pretty much just that, it's a storage card built onto the phone itself. Now it is already partitioned, and allot!
Not only does this one physical card hold your "internal sd card" contents but it also holds your ROM, cache, all your apps, and even your recovery!
Even though it looks like these are separate drives they are all one physical card, your internal sd card.
Now if you try to add to this mix of partitions on this internal card you run the VERY HIGH risk of messing up the lines and sizes of these partitions. Many things in Android assume that some of these are a certain size or at a certain place, and if you mess with it all hell brakes lose!
Now people sometimes partition the external sd card because they want 2 different file types, like half fat32 (like a normal sd card) and half ext4/3 for apps it use in Linux.
Hope this helps!!!
Sent from my LG-P999 using Tapatalk
ok, well then i guess my question is more along the lines of why do we have that option in CWM Recovery and if i create a 2gb partition what happens? does it change the default 1.5gb partition so you have more room for apps?
dodgefan67 said:
ok, well then i guess my question is more along the lines of why do we have that option in CWM Recovery and if i create a 2gb partition what happens? does it change the default 1.5gb partition so you have more room for apps?
Click to expand...
Click to collapse
I'm honestly not sure, I've only ever messed with these partitions manually when unbricking my phone. So if you do it, you have a fairly good chance of bricking the phone, but i don't know how Android will react.
Sent from my LG-P999 using Tapatalk
thanks, i was just curious, since CWM gives us the option, but ive never done it and until i can find a good reason to i probably won't even mess with it
but it just seems kind of bad having 5gb on the internal card going to waste, i have backups to my external sd, all my data is there too, so i probably won't even touch that 5gb...
Just be glad it's not the other way around
Ill take too much space over not enough any day!
Sent from my LG-P999 using Tapatalk
well true, but still would like to know exactly what happens if you choose to run that in CWM Recovery
seek and ye shall find
found a guide for CWM and from what i see that option puts a partition on your external sd card so it can be used to install apps on IF the rom supports that. it says it does wipe everything else off the card though so you need to make a backup. you can also put a swap partition on it as well
looks like it does not touch the internal sd card phone memory which is what i thought it did
http://www.addictivetips.com/mobile...-and-how-to-use-it-on-android-complete-guide/

Large MicroSD troubles

I was previously using a UHC-1 speed 64GB MicroSD card in the MicroSD card slot on my TF101. This worked great in ASUS stock ICS, and also ASUS stock ICS w/ Guevor kernels. I decided to try out a few JB builds. So far, every JB build, and combination of kernels that I have tried does not allow me to read this card. I can read a smaller 4GB card just fine. Even if I put it in an adapter and stick it in the dock SD card slot, it still won't read. After verifying that I could still read it on my PC, I even reformatted the card as exFat from a PC, and that still yielded no success in reading it on the TF101.
To date, I've tried the official CM10 nightlies and EOS3 (with KAT 1.0.1 and Harmony JB kernel). None of these combinations, on any of the revisions (I tried back-dated versions also) seem to work with the card. It shows it present, but it can't mount it.
Anybody care to throw a stab at what may be going wrong?
I searched around a bit, and nobody has stated any such problems. (That or my google-fu is lacking)
I would hate to have to go back to ICS after going through all this trouble.
(Yes, I wiped, and wiped, and wiped, and wiped again. I even cleaned the entire user data section as well as everything else, I even reflashed things from scratch from the PC).
Sent from my Transformer TF101 using Tapatalk 2
ryocoon said:
I was previously using a UHC-1 speed 64GB MicroSD card in the MicroSD card slot on my TF101. This worked great in ASUS stock ICS, and also ASUS stock ICS w/ Guevor kernels. I decided to try out a few JB builds. So far, every JB build, and combination of kernels that I have tried does not allow me to read this card. I can read a smaller 4GB card just fine. Even if I put it in an adapter and stick it in the dock SD card slot, it still won't read. After verifying that I could still read it on my PC, I even reformatted the card as exFat from a PC, and that still yielded no success in reading it on the TF101.
To date, I've tried the official CM10 nightlies and EOS3 (with KAT 1.0.1 and Harmony JB kernel). None of these combinations, on any of the revisions (I tried back-dated versions also) seem to work with the card. It shows it present, but it can't mount it.
Anybody care to throw a stab at what may be going wrong?
I searched around a bit, and nobody has stated any such problems. (That or my google-fu is lacking)
I would hate to have to go back to ICS after going through all this trouble.
(Yes, I wiped, and wiped, and wiped, and wiped again. I even cleaned the entire user data section as well as everything else, I even reflashed things from scratch from the PC).
Sent from my Transformer TF101 using Tapatalk 2
Click to expand...
Click to collapse
I think it has to be fat32 formatted to be seen, at least in recovery. I believe the JB ROMs are currently unable to read NTFS, not sure about exFat.
sidneyk said:
I think it has to be fat32 formatted to be seen, at least in recovery. I believe the JB ROMs are currently unable to read NTFS, not sure about exFat.
Click to expand...
Click to collapse
Yeah you're usually safe just sticking with FAT32.
But if you get too frustrated at that SD card, I'd be glad to take it off your hands for you, haha.
ryocoon said:
I was previously using a UHC-1 speed 64GB MicroSD card in the MicroSD card slot on my TF101. This worked great in ASUS stock ICS, and also ASUS stock ICS w/ Guevor kernels. I decided to try out a few JB builds. So far, every JB build, and combination of kernels that I have tried does not allow me to read this card. I can read a smaller 4GB card just fine. Even if I put it in an adapter and stick it in the dock SD card slot, it still won't read. After verifying that I could still read it on my PC, I even reformatted the card as exFat from a PC, and that still yielded no success in reading it on the TF101.
To date, I've tried the official CM10 nightlies and EOS3 (with KAT 1.0.1 and Harmony JB kernel). None of these combinations, on any of the revisions (I tried back-dated versions also) seem to work with the card. It shows it present, but it can't mount it.
Anybody care to throw a stab at what may be going wrong?
I searched around a bit, and nobody has stated any such problems. (That or my google-fu is lacking)
I would hate to have to go back to ICS after going through all this trouble.
(Yes, I wiped, and wiped, and wiped, and wiped again. I even cleaned the entire user data section as well as everything else, I even reflashed things from scratch from the PC).
Sent from my Transformer TF101 using Tapatalk 2
Click to expand...
Click to collapse
Did you ever get a solution? I just got a 64gb UHS-1 card and am having all types of problems with accessing it. I am using KatKiss 4.3_029. I started getting no access to write access errors in TB, and copying files to it would just stop and say the disk might be full. I reformatted it exFAT using the SDFormatter tool on a PC, and wrote many fles to it on PC with no problems, but on ANdroid am seeing 0 byte files and all kinds of weirdness. I fixed permissions, I Edited the platform.xml file's WRITE_EXTERNAL_STORAGE permission. Before doing the exFAT format, I had tried formatting in TWRP. None of these things fixed my problem. I even have the problems when installed in the dock in an SDCArd adapter.
Does anybody have any other ideas?
I formatted my 64GB card as vfat within Linux and I think I did it while it was in my card reader front panel. Now I have 63GB of storage that works in twrp and 4.4.2.
Sent from my SM-N900T using XDA Premium HD app
bradysd4 said:
Did you ever get a solution? I just got a 64gb UHS-1 card and am having all types of problems with accessing it. I am using KatKiss 4.3_029. I started getting no access to write access errors in TB, and copying files to it would just stop and say the disk might be full. I reformatted it exFAT using the SDFormatter tool on a PC, and wrote many fles to it on PC with no problems, but on ANdroid am seeing 0 byte files and all kinds of weirdness. I fixed permissions, I Edited the platform.xml file's WRITE_EXTERNAL_STORAGE permission. Before doing the exFAT format, I had tried formatting in TWRP. None of these things fixed my problem. I even have the problems when installed in the dock in an SDCArd adapter.
Does anybody have any other ideas?
Click to expand...
Click to collapse
I eventually switched over to KatKiss on my TF101, but I also now use a TF701. exFAT, in general, does not work for auto-mount. Mostly due to licensing restrictions and stupidity like that for the core of the OS. You can format a 64GB card as FAT32, but you need a special tool to do it, as Windows won't let you format anything over 2GB as FAT32, and instead switches to vFAT/exFAT or NTFS, which are... less compatible and will not auto-mount. Now, I would have to go back and look at my TF101 device, but I lost the MicroSD from it (which was sad, as it had tons of pictures from a DSLR I took during a trip that not all had been cloud backed-up when I lost it). So more recent KatKiss kernels/ROMs may be able to auto-mount exFAT or vFAT along with older FAT32. NTFS will never auto-mount it seems (at least not as read/write), but can be mounted read/write if you have the right kernel or tool combination.
Also, I've never had the formatter in either CWM or TWRP work properly since the days of the OG Droid (Motorola Milestone A855).
ryocoon said:
I eventually switched over to KatKiss on my TF101, but I also now use a TF701. exFAT, in general, does not work for auto-mount. Mostly due to licensing restrictions and stupidity like that for the core of the OS. You can format a 64GB card as FAT32, but you need a special tool to do it, as Windows won't let you format anything over 2GB as FAT32, and instead switches to vFAT/exFAT or NTFS, which are... less compatible and will not auto-mount. Now, I would have to go back and look at my TF101 device, but I lost the MicroSD from it (which was sad, as it had tons of pictures from a DSLR I took during a trip that not all had been cloud backed-up when I lost it). So more recent KatKiss kernels/ROMs may be able to auto-mount exFAT or vFAT along with older FAT32. NTFS will never auto-mount it seems (at least not as read/write), but can be mounted read/write if you have the right kernel or tool combination.
Also, I've never had the formatter in either CWM or TWRP work properly since the days of the OG Droid (Motorola Milestone A855).
Click to expand...
Click to collapse
OK, I reformatted to FAT32 last night using Easus disk partition software on Windows, re-copied a bunch of files to it, but haven't had a chance to test it yet. I couldn't get mini-tool partition software (which others had mentioned using) to work on Win8.1. If that doesn't fix it, I may try to get it replaced by mfg.
UPDATE: It seems like that (reformat with easus to FAT32) fixed it. No problems today. Yay! Back to 64gb MicroSD.
bradysd4 said:
OK, I reformatted to FAT32 last night using Easus disk partition software on Windows, re-copied a bunch of files to it, but haven't had a chance to test it yet. I couldn't get mini-tool partition software (which others had mentioned using) to work on Win8.1. If that doesn't fix it, I may try to get it replaced by mfg.
Click to expand...
Click to collapse
I didn't use any partition manager software (if I was on linux, possibly, but I'm rockin' the Win 8.1 on my box at the moment, other systems in storage). I used a command line tool for formatting FAT32, it is GPL and such. Located at http://www.ridgecrop.demon.co.uk/fat32format.htm .
It seemed to work pretty well, but you have to decipher the command line options a bit.

Can't copy files to the SD card

I have tried using ES file explorer, the Asus file manager, and FX file explorer. I get a copy failed message every time I try to copy a file to the removable SD card.
Anyone else have this issue?
You can't know your limits until you exceed them.
duckredbeard said:
I have tried using ES file explorer, the Asus file manager, and FX file explorer. I get a copy failed message every time I try to copy a file to the removable SD card.
Anyone else have this issue?
You can't know your limits until you exceed them.
Click to expand...
Click to collapse
Have you tried to reformat the card with fat32?
I just did. Seems I'm only having issues with the 32 GB size cards. Acting like they are read only. Can't find such a setting anywhere. Is there another format that should work?
You can't know your limits until you exceed them.
duckredbeard said:
I just did. Seems I'm only having issues with the 32 GB size cards. Acting like they are read only. Can't find such a setting anywhere. Is there another format that should work?
You can't know your limits until you exceed them.
Click to expand...
Click to collapse
Have you tried with the latest kernel (JB version .25) and what make and model of your sdcard? just wonder if compability issue and are we talking about Micro sdcard or full size sdcard? On the full size there is a little switch on the side to block writting to the card.
I'm only having issues when I'm using the tablet to copy files. I'm on CleanROM Inheritance. I don't recall if I had this issue with the stock rom. Sometime tonight I will make a backup of my current and then flash to stock rom. Since I'm talking about the removable SD card, it could only be the micro SD that is installed in the tablet. There is no switch on that card.
Sent from my HTC PH39100 using xda app-developers app
I think flashing the _that nodpi kernel should resolved your issue, give it a try.
Sent from my ASUS Transformer Pad TF700T using xda premium
Link to said kernel?
You can't know your limits until you exceed them.
duckredbeard said:
Link to said kernel?
You can't know your limits until you exceed them.
Click to expand...
Click to collapse
download this http://d-h.st/M6j then flash with twrp, during the install pick _that_nodpi_stock kernel.
That did it. Did it replace the overclock kernal I selected when I flashed CROMI 3.2?
Sent from my HTC PH39100 using xda app-developers app
duckredbeard said:
That did it. Did it replace the overclock kernal I selected when I flashed CROMI 3.2?
Sent from my HTC PH39100 using xda app-developers app
Click to expand...
Click to collapse
Yes, it replaced what ever kernel you selected during cleanrom installation. Since it stock kernel, you can no longer Overclock.
Is there another kernel that can be the fix and still give us over clock?
You can't know your limits until you exceed them.
duckredbeard said:
Is there another kernel that can be the fix and still give us over clock?
You can't know your limits until you exceed them.
Click to expand...
Click to collapse
Sorry but nope, I believe as soon as Asus release source code, _that is going to make an OC version for this and it's going to be awsome. For now we just have to wait.
Similar Problem With A Samsung Micro SD Card
duckredbeard said:
That did it. Did it replace the overclock kernal I selected when I flashed CROMI 3.2?
Sent from my HTC PH39100 using xda app-developers app
Click to expand...
Click to collapse
Hi.
I'm having a problem with my Samsung Micro SDXC I (Class 10) card. I've been messing abut with it for days now, formatting, re-formatting in exFAT, FAT32, NTFS but the problem persists; whenever I try to copy data across to the card, the first time the card is inserted, it starts to copy, sometimes even up to 1.5Gb of data but often much less, but then gives me a 'Write Error' or 'I/O Error' message & stops working. Sometimes it also deletes other data on the card when the error occurs. then, until I unmount the card again, it barely functions at all!
A big factor in buyinh this tablet, unlocking, then rooting it was so that I'd have an awesome, small, tablet that had loads of storage & could be transported around very easily. If I can't get the cards to work with it, that's a big part of it's usefulness to me down the drain.
I tried to download the kernal that was mentioned above the message of yours that I'm replying to but the file has been moved. Do you still have it?.......or know how I can resolve my problem without it?
Any help would be much appreciated.
Thanks.
dan5001 said:
Hi.
I'm having a problem with my Samsung Micro SDXC I (Class 10) card. I've been messing abut with it for days now, formatting, re-formatting in exFAT, FAT32, NTFS but the problem persists; whenever I try to copy data across to the card, the first time the card is inserted, it starts to copy, sometimes even up to 1.5Gb of data but often much less, but then gives me a 'Write Error' or 'I/O Error' message & stops working. Sometimes it also deletes other data on the card when the error occurs. then, until I unmount the card again, it barely functions at all!
A big factor in buyinh this tablet, unlocking, then rooting it was so that I'd have an awesome, small, tablet that had loads of storage & could be transported around very easily. If I can't get the cards to work with it, that's a big part of it's usefulness to me down the drain.
I tried to download the kernal that was mentioned above the message of yours that I'm replying to but the file has been moved. Do you still have it?.......or know how I can resolve my problem without it?
Any help would be much appreciated.
Thanks.
Click to expand...
Click to collapse
You don't say which rom or firmware you are currently using. Without knowing that I wouldn't go blindly flashing kernels that are nearly a year old
It could be that your card is actually damaged as I can copy files just fine on mine. I'm using a SanDisk Ultra uhs-1.
ROM & Firmware
sbdags said:
You don't say which rom or firmware you are currently using. Without knowing that I wouldn't go blindly flashing kernels that are nearly a year old
It could be that your card is actually damaged as I can copy files just fine on mine. I'm using a SanDisk Ultra uhs-1.
Click to expand...
Click to collapse
Hi sbdags,
Roger that
I'm not bad with most things tecchie but whilst I know which ROM I'm using, I'm not sure what the firmware is.
I recently updated to CROMI-X 5.2.2 from an earlier version in the hope that that might include an update or something that would solve my SD card problem.......it didn't
With regard to 'Firmware', I'm not sure where that's listed on the tablet but in the 'About' tab in my settings, it says:
Android Version - 4.2.1
Kernal Version - 3.1.10-g215ae8bf [email protected] # 1
Build Number - TF700 CHROMI-X 5.2.2 - 10.6.1.27.5 WW DEODEX
Pad EC Version - PAD-EC20T-0216
MobileDock Version - DOCK-EC20N-0207
I hope the firmware information you need is in there somewhere?
The card I bought is the latest 64Gb Samsung Micro SDXC Pro UHS-1 (Class 10) with write speeds of 20Mb/s & 70Mb transfer speed. I had read the formums & was torn between this card & the SanDisk 64Gb Ultra Micro SDXC (Class 10), the two-tone red/grey version, presumably like the one you're using but the Samsung was faster & at the time I bought it, the Samsungwas almost £15 cheaper. Since they were both reported to work, I opted for the Samsung card; maybe that was a bad decision?
I've just ordered the SanDisk 64Gb card, in the hope that that one will work because as i said, it really would be a shame if I can't make use of the extended storage that the SD crads give.
Do you use your SanDisk card in Micro SD form in the tablet or SD form in the dock.....or both......& have you got them formatted to exFAT or some other format?
Thanks again for your attention.
dan5001 said:
Hi sbdags,
Roger that
I'm not bad with most things tecchie but whilst I know which ROM I'm using, I'm not sure what the firmware is.
I recently updated to CROMI-X 5.2.2 from an earlier version in the hope that that might include an update or something that would solve my SD card problem.......it didn't
With regard to 'Firmware', I'm not sure where that's listed on the tablet but in the 'About' tab in my settings, it says:
Android Version - 4.2.1
Kernal Version - 3.1.10-g215ae8bf [email protected] # 1
Build Number - TF700 CHROMI-X 5.2.2 - 10.6.1.27.5 WW DEODEX
Pad EC Version - PAD-EC20T-0216
MobileDock Version - DOCK-EC20N-0207
I hope the firmware information you need is in there somewhere?
The card I bought is the latest 64Gb Samsung Micro SDXC Pro UHS-1 (Class 10) with write speeds of 20Mb/s & 70Mb transfer speed. I had read the formums & was torn between this card & the SanDisk 64Gb Ultra Micro SDXC (Class 10), the two-tone red/grey version, presumably like the one you're using but the Samsung was faster & at the time I bought it, the Samsungwas almost £15 cheaper. Since they were both reported to work, I opted for the Samsung card; maybe that was a bad decision?
I've just ordered the SanDisk 64Gb card, in the hope that that one will work because as i said, it really would be a shame if I can't make use of the extended storage that the SD crads give.
Do you use your SanDisk card in Micro SD form in the tablet or SD form in the dock.....or both......& have you got them formatted to exFAT or some other format?
Thanks again for your attention.
Click to expand...
Click to collapse
Well the ROM is mine so you are all good there. Lol. I only use fat32 as that is how the cards come.
Are you copying the files in esfileexplorer? Are they single files? Total size?
File Sizes
sbdags said:
Well the ROM is mine so you are all good there. Lol. I only use fat32 as that is how the cards come.
Are you copying the files in esfileexplorer? Are they single files? Total size?
Click to expand...
Click to collapse
Hi sbdags.
I've tried using both the File Explorer that was included with CHROMI-X & another one from the Play Store that I use on my phone called Astro; the same thing happens with both. As I say, the card seemed okay to begin with but all I had put on it was my Nandroid & Titanium backups (approx. 2Gb total with lots of small files included). The problems started when I tried to copy a season of a TV series onto the card to free up space on the internal SD card. It started off okay & I wasn't expecting any problems but then approx 1.5Gb, I got an I/O write error & then all the problems I described in my first post.
As an aside, the card performed best when formatted to FAT32 but according to the SD Card Association, SDXC cards come formatted as exFAT, so that's how it's currently formatted; I thought if that's how it came & it initially worked okay, maybe that would solve the issue. Again, I was wrong!
So, I'll format it back to FAT32 again but as I've already had it in that format, I wouldn't anticipate any change to the card's behaviour.
The 64Gb SanDisk card should be here in a few days, so I'll be able to report on whether that one works or not then.
Did you have to re-format yours when you first got it or are the SD Card Association talking nonsense? Oh, & you didn't say whether you're able to use your cards in both micro form in the pad &/or full-size form in the dock? Also, was the Firmware information you asked for in that mass of stuff I listed. If not, where do I find it, so I know for the next time you ask
Thanks again
dan5001 said:
Hi sbdags.
I've tried using both the File Explorer that was included with CHROMI-X & another one from the Play Store that I use on my phone called Astro; the same thing happens with both. As I say, the card seemed okay to begin with but all I had put on it was my Nandroid & Titanium backups (approx. 2Gb total with lots of small files included). The problems started when I tried to copy a season of a TV series onto the card to free up space on the internal SD card. It started off okay & I wasn't expecting any problems but then approx 1.5Gb, I got an I/O write error & then all the problems I described in my first post.
As an aside, the card performed best when formatted to FAT32 but according to the SD Card Association, SDXC cards come formatted as exFAT, so that's how it's currently formatted; I thought if that's how it came & it initially worked okay, maybe that would solve the issue. Again, I was wrong!
So, I'll format it back to FAT32 again but as I've already had it in that format, I wouldn't anticipate any change to the card's behaviour.
The 64Gb SanDisk card should be here in a few days, so I'll be able to report on whether that one works or not then.
Did you have to re-format yours when you first got it or are the SD Card Association talking nonsense? Oh, & you didn't say whether you're able to use your cards in both micro form in the pad &/or full-size form in the dock? Also, was the Firmware information you asked for in that mass of stuff I listed. If not, where do I find it, so I know for the next time you ask
Thanks again
Click to expand...
Click to collapse
I've never tried my card in the dock to be honest. Both my cards; 32GB and 64GB are SanDisk, I am not sure now what they cam in but I am using fat32 as I formatted them myself.
As for the stuff you posted I just wanted to know the rom and bootloader version. So CROMi-X 5.2.2 on 10.6.1.14.10 would have ben enough. Maybe the kernel helps too. In your case you are using the stock kernel. You may get better results on thatv4 kernel?
SD Cards & Kernels
sbdags said:
I've never tried my card in the dock to be honest. Both my cards; 32GB and 64GB are SanDisk, I am not sure now what they cam in but I am using fat32 as I formatted them myself.
As for the stuff you posted I just wanted to know the rom and bootloader version. So CROMi-X 5.2.2 on 10.6.1.14.10 would have ben enough. Maybe the kernel helps too. In your case you are using the stock kernel. You may get better results on thatv4 kernel?
Click to expand...
Click to collapse
Cheers.
So, I think I've grasped that the kernel is similar to the BIOS on a PC; is that correct?
When you say that I may get better results using _that's v.4 kernel, what improvements are you thinking I might see?
dan5001 said:
So, I think I've grasped that the kernel is similar to the BIOS on a PC; is that correct?
Click to expand...
Click to collapse
Not really, the kernel is ... the kernel. The core of the operating system. Under Windows it's ntoskrnl.exe.
You could compare the bootloader with the PC BIOS - its main function (nowadays) is to start the operating system.

SD card problem

Hey guys!
I have strange problem, see I have 2 sd cards, one inside my htc hd 2 (gb) and one in tf300. I just reflashed rom back to CROMI (I have tried hydro by seanz) and tablet cant load my sdcard.
Its kinda weird because, when Im in TWRP, I can see the sd card and files on it. The card works without any problems on my htc and on my laptop. I have tried to format it to FAT32, exFAT and tablet cant load it. I have tried to put sd card from my htc to tablet and this one runs pretty much normally.
Well, if one card wasnt 4gigs, and the other one 32gigs I would just swap them and be done, but this is strange and Im not sure why its behaving like this.
Does anyone have some tip? Thanks
QQboss said:
Hey guys!
I have strange problem, see I have 2 sd cards, one inside my htc hd 2 (gb) and one in tf300. I just reflashed rom back to CROMI (I have tried hydro by seanz) and tablet cant load my sdcard.
Its kinda weird because, when Im in TWRP, I can see the sd card and files on it. The card works without any problems on my htc and on my laptop. I have tried to format it to FAT32, exFAT and tablet cant load it. I have tried to put sd card from my htc to tablet and this one runs pretty much normally.
Well, if one card wasnt 4gigs, and the other one 32gigs I would just swap them and be done, but this is strange and Im not sure why its behaving like this.
Does anyone have some tip? Thanks
Click to expand...
Click to collapse
you didnt happen to remove any system app apks did you? i removed a bunch once and experienced same issue.
However if you didnt remove any system apps. Then i would first suggest using minitool partition wizard and format the SD card FAT32 as a primary partition. Then use windows to format it exFAT (its better to use but TWRP and CWM dont see the sd card then) but its worth it cause then you can store files greater than 4 gb on the SD card. Or just stick with FAT32 to eaches own lol.
If still a no go, try flashing the ROM again.
hey mate thanks for replying no Im sure I didnt remove any system apks. Im not sure where was the problem, but I did restore my backup and now everything is fine as usual. Since it was really simple to solve this issue, I apologize that I didnt try this before I posted, but it never ocured to me that this issue could be solved by reflash since different sd card was runing without flaw.
Anyway thank you for participating and for your time :angel:
+1 elesbb's post!
Note:
Using an sdcard in another unit can cause strange issues including not being able to boot.
Even going from rom to rom can sometimes cause problems with leftover files.
Format as suggested in pc and use in one unit only unless you reformat.
QQboss said:
hey mate thanks for replying no Im sure I didnt remove any system apks. Im not sure where was the problem, but I did restore my backup and now everything is fine as usual. Since it was really simple to solve this issue, I apologize that I didnt try this before I posted, but it never ocured to me that this issue could be solved by reflash since different sd card was runing without flaw.
Anyway thank you for participating and for your time :angel:
Click to expand...
Click to collapse
No problem! Glad it's working! Bit I do wanna say the new twrp 2.4.1.0 DOES support exFAT format now!! Sweetness!
Sent from my ASUS Transformer Pad TF300T using Tapatalk 2

[Q] SD Card Not Writeable?

It seems that my SD card is not writable when inserted. Is this true? I tried to create a new folder on it with root explorer (I am not rooted though) and it said that my device needs to be rooted in order to accomplish that task.
Any ideas?
Jonn
Did you try something like es file explorer? I would try that.
That didn't work either. It says "operation failed".
I actually noticed that it wasn't working playing act raiser and it wasn't saving my position. Moving the ROM to internal storage worked. I then tried to create a folder.
Sent from my Nexus 7 using Tapatalk 2
Huh. Just tried a different SD card and that one worked. Weird.
Sent from my Nexus 7 using Tapatalk 2
I spoke too soon. After removing the sdcard that worked and putting it back in, it no longer is writeable.
Sent from my Nexus 7 using Tapatalk 2
It works again if I pull the card out, restart the shield and put the card back in. Perhaps something up with the mounting process?
It appears that once a card is mounted, if it is removed and re-inserted, it remounts as read only.
Jonn
Sent from my Nexus 7 using Tapatalk 2
It looks like sdcard mounting is messed up. I can't get any of the sdcards i have tried to mount.
Did you go into settings and actually click unmount before removing the SD Card? Many linux systems (android is linux) will mount devices which werent safely removed in read only mode for some bizarre reason.
I tried that as well. It still doesn't work.
Sent from my Nexus 7 using Tapatalk 2
jonnberg said:
It seems that my SD card is not writable when inserted. Is this true? I tried to create a new folder on it with root explorer (I am not rooted though) and it said that my device needs to be rooted in order to accomplish that task.
Any ideas?
Jonn
Click to expand...
Click to collapse
when you go to storage under settings, under sd card does it show total space for card. if not maybe you have to format it to NTFS first. thats what I had to do with my new card. also said to do so on shield guide
evobunny said:
when you go to storage under settings, under sd card does it show total space for card. if not maybe you have to format it to NTFS first. thats what I had to do with my new card. also said to do so on shield guide
Click to expand...
Click to collapse
I did not read the destructions. The destructions have useful information? Where may i find these destructions? I assumed fat32 so that is what my sd is formatted to.
chevyowner said:
I did not read the destructions. The destructions have useful information? Where may i find these destructions? I assumed fat32 so that is what my sd is formatted to.
Click to expand...
Click to collapse
sorry i cant post link yet cause im new to forum. but go there, (shield.nvidia.com/user-guide/sd-card) user guide said to format it to NTFS
Would has added this sooner, but I lost my sdcard reader.
Formatting it NTFS worked.
Still wont mount, but now i at least get the option to mount.
evobunny said:
when you go to storage under settings, under sd card does it show total space for card. if not maybe you have to format it to NTFS first. thats what I had to do with my new card. also said to do so on shield guide
Click to expand...
Click to collapse
Yes, I formatted it to NTFS before I inserted it. It shows the total space and space available, it just doesn't allow anything to be written to it. I can take it out and put it in a PC and it works correctly. I also have another SD card that I tried and it worked for a few minutes, but I haven't been able to get it to keep working.
Jonn
jonnberg said:
Yes, I formatted it to NTFS before I inserted it. It shows the total space and space available, it just doesn't allow anything to be written to it. I can take it out and put it in a PC and it works correctly. I also have another SD card that I tried and it worked for a few minutes, but I haven't been able to get it to keep working.
Jonn
Click to expand...
Click to collapse
sorry I dont know what else to tell you, i first had the same problem like yall when I stuck in a brand new card. nothing I downloaded would go on to card. and it didnt show the amount of space left under the storage menu. Then i found out it need to be formated to NTFS. Once i did that everything started downloaded and showing up on card.
jonnberg said:
Yes, I formatted it to NTFS before I inserted it. It shows the total space and space available, it just doesn't allow anything to be written to it. I can take it out and put it in a PC and it works correctly. I also have another SD card that I tried and it worked for a few minutes, but I haven't been able to get it to keep working.
Jonn
Click to expand...
Click to collapse
The only memory card I have gotten working (about 1 minute ago) is 512MB and formatted fat32
The card i want to us is a 16gb microsdhc formatted fat32 when this memory card is in my shield it knows it has a memory card but says it has no partitions on it.
I am running testdisk on the sd card and it found 9 partitoins. I will try and clean that up.
To be honest, I've never tried SD card support on the device. So I can't say one way or another. But I'll be looking at it soon enough since I got my first build of CWM for SHIELD waiting for me to debug in the other room once the kids go to bed.
I just tried two different 8GB class 10 transcend cards, an 8GB class 2 generic card and a 256mb sandisk card. I put each card in and copied a file from internal storage to it. Then I removed each of the cards without unmounting and put them back in and proceeded to copy a file to the card again. Every time it worked successfully. I do not even know what format they are in and didn't format them before testing. And, maybe the issue didn't show up because I didn't give it enough time. I am not sure.
Also, I know this is probably a really dumb question but the micro sd slot is spring loaded. You are pushing it in until you hear a good solid click right?
issues
Having issues of my own.
Bought a 64gb sandisk SDXC card for shield. It worked 100% fine in my SGS3 formated for exFat. But not in the shield...
It seems to work somewhat when formated for NTFS. But the file path is really messed up and 1/2 my apps cant see the SD card because of this. It something like (root/storage/sdcard1/....)
2 apps that are basically usless right now due to this are Power amp & FPse.
Android doesn't normally support either exFat or NTFS. The shield may include support for them but if I had a shield I would steer clear anyway and go with what android definitely trusts in FAT32.
Hopefully NVidia will do a firmware update to sort these problems though

Categories

Resources