Related
Well, i'm a noob to this forum, and to doing ANY rooting/flashing. There, thats out in the open XD
Heres the specs:
CM7 7.0.3 Stable
Nook Color (Blue Dot)
ADW Launcher
Onto the issue! I have searched ENDLESSLY for a solution to this, but have come up short. Nearly everytime I power off/on or reboot the Nook, all my widgets show "Problem Loading Widget". The ONLY way to get them running again is deleting and replacing them again on the screen.
Let me explain some things I have done and hopefully we can figure this out. I am assuming, that it may be due to me performing this - http://forum.xda-developers.com/showthread.php?t=1034939. Basically what that does is take the unused eMMC from the NC and tag it as the SDCard. The reason for doing that is because I don't have any ACTUAL decent sized SD cards and figured why not use the 5GB thats avail and unused on the Nook, and "simulate" it as being a 5GB SD card for apps and whatever else.
Nearly every post I have read says it has to do with having the apps for the widgets on the SD Card. Well, they're not, they're on internal memory. AND, if I do move them to my "simulated" SD Card, they don't even come up in the widget list, so that clears that option.
Also, since I had a Blue Dot Nook, I performed this - http://forum.xda-developers.com/showthread.php?t=1094371 and partitioned to the old style NC.
I have tried and tried to find out where the apps, if stored "internally", actually are. I cannot for the life of me find them, other than the default Google Apps in /system/app, as well as the ones I have downloaded on the "simulated" SD card under /mnt/asec & /mnt/sdcard/android.secure.
Also, when I plug the NC into my PC, I see whatever is on my "simulated" 5GB SD card (which is really the eMMC of the device). Is it possible to view the root of the device at all to see ALL the files/folders on it?
If someone can solve this, I will be eternally grateful, in a totally non gay way atleast. THANKS!
Hey there....
I'm new to the NookColor and rooting/flashing Android devices, too (though, I did run Linux on my Palm Tungsten T3, back in the day). I probably only partially understand your woes, but it seems to me that your problem stems from the faking microSD thing. Maybe it's not so much that Android wants to put something in the SD, as much as it's confused, when it probes for orthodoxy. I understand the want to use the internal memory, instead of buying a mSD, honestly.
Again, I'm totally new to this, but reading your post and many other posts in the last 48 hours, I think I might have a valid solution: start over. If I were you, I'd do the following, which, incidentally, is very much what I'm in the process of doing, too. I'm starting from "blue dot" scratch with two mSD's (2GB & 8GB) in-hand, though. By the way, and if it's any help to you, I bought my Class 4 SanDisk 8GB mSD at Office Depot yesterday for around $15 (on sale?).
1. Buy a microSD card.
2. Image the card with ClockworkMod.
3. Install TitaniumBackup Free.
4. Backup all of your apps/stuff to the microSD card with TitaniumBackup.
5. Save an image of your current setup with ClockworkMod (booting from mSD, backing up to mSD)
6. Repartition to the old (pre-"blue-dot") scheme, again, using the first mrm3.net link below as a guide.
7. Install the latest CM7 Nightly for "encore"...
8. Save an image of your current setup with ClockworkMod (booting from mSD, backing up to mSD)
9. Install TitaniumBackup Free.
10. Restore all of your apps to the microSD card with TitaniumBackup.
(Of course, I'm assuming a lot of things... I guess I'm just thinking aloud... Maybe some of this is of some use to you. Good luck!)
-v
p.s.... I had a few links I was going to share, but I'm not allowed to share external links until after my 8th post (and I understand why that's a rule)... lol..
There seems to be plenty of threads about these things around here. I just don't have them right now..
Thank you vulariter! It'd be great if when you finish getting everything set up, letting me know how it works out for you. I know people have been having some pretty weird things happening with the blue dot Nooks. Appreciate the info.
I"m happy to report that my internal CM7 Nightly install went well. I chose to go with a 2 GB apps / 4 GB media internal partitioning scheme. I like breathing room, on both sides..lol.. I also like doing things the difficult way, sometimes.. (just being honest)...
Minus the unnecessary convolution of my rooting the stock OS, 50+ complex character WPA2 key, static IP WIFI network, and email address fiasco, here's basically what I did. Again, I'd love to share the external links, but I don't think it will let me do so.
Oh, and always check MD5 sums on the files you download, wherever possible. Corruption in these files will surely eat your Nook alive, at least a little. lol.. Yes, be very scared of that.
Also, don't forget to backup your ClockworkMod backups to a better medium than the microSD card. I used 7zip to archive them on my laptop's internal drive. A cloud backup of them would probably be better (e.g. Dropbox). Just remember, you're putting potentially personal info out there, wherever you put these backups.
Thanks to all the people who figured this stuff out (see the links / websites below, to give them credit).
Bought a NookColor at my local B&N. (I later read about the "blue dot" thing and realized mine had the "blue dot" on the back of the box.)
SIDE NOTE: My understanding is that the "blue dot" signifies only a few important things. 1. a 5 GB apps / 1 GB media partitioning scheme... 2. U-Boot 1.2, with the "Read Forever" logo..... 3. Maybe an unlocking of a few more cylinders (about 250 MB)??? I've only read a little on this..... 4. Maybe a different chip revision or two, inside.
Bought a SanDisk Class 4 (class 6 would have been better) 8GB microSD card.
Located my microSD to SD adapter, which is a priceless item to me.
Located my USB many-in-one card reader, because my Lenovo R61's internal SD reader is unstable.
Located my 2GB class ? microSD card, which I once used in my old LG env2.
Connected my USB card reader to my laptop.
Inserted the 2GB mSD into my USB card reader.
Copied all of my old music, etc, on my 2GB microSD to a directory on my laptop for posterity.
Downloaded the latest version of Win32DiskImager. (Link 1)
Downloaded the latest version of ClockworkMod 2GB SD image. (Link 1)
Imaged my 2GB mSD with the ClockworkMod image.
Created "clockworkmod" and "clockworkmod\backup" directories, inside of the 2 GB mSD (whose disk label is now "boot").
Downloaded the "Custom: 2GB for Apps and 4GB for Media" partitioning file from mrm3.net and placed it in the root directory of my 2 GB mSD.
Downloaded the "Mandatory Data Format File" from mrm3.net and placed it in the root directory of my 2 GB mSD.
Downloaded the latest CM7 "encore" Nightly from cyanogenmod.com and placed it in the root directory of my 2 GB mSD.
Downloaded the latest "encore" Gapps from mrm3.net and placed it in the root directory of my 2 GB mSD.
Confirmed my Gmail and Youtube accounts were linked. This is also the same address which I'm using for my B&N account.
SIDE NOTE: I had to change my B&N account's non-Gmail email address to align my email addresses. I think this may have caused a problem with my obtained-at-Nook-purchase B&N Membership Card, because it no longer works... (I've contacted them about it...and their answer is unsatisfactory. Beware!)
Unboxed my NookColor and began charging it, via the wall plug.
Booted my stock NookColor, signed into my WIFI network and registered my device to my Gmail email address.
Played around with the stock OS and Nook apps, because I'll probably never ever see them again.. The Crossword game was awesome! I didn't allow myself to become attached to their reading apps, to be honest..lol.. (I would have probably been attached, had I not been proactive in my "hacking".)
Powered off my NookColor.
Inserted the 2 GB mSD into my NookColor.
Booted my NookColor into ClockworkMod.
Saved a backup of the stock system to the "backup" directory I created earlier.
Followed the instructions at mrm3.net to repartition my NookColor (rebooting, as directed).
Removed the 2 GB mSD card.
Rebooted again, allowing the Nook to recover from the repartitioning. I did not reregister the device in this step. I just waited for the woman's face to appear and shut it down.
Inserted the 2 GB mSD card.
Booted my NookColor into ClockworkMod.
Saved a backup of the NEWLY PARTITIONED stock system to the "backup" directory I created earlier.
I followed the mrm3.net CM7 Nook Nightlies instructions, but I'll paraphrase here. (Definitely seek this article out, and don't take my word for it.)
Still in ClockworkMod, I reformatted the "data", "system",and "cache"partitions.
Used "install from zip" to install "cm_encore_full-xx.zip"
Used "install from zip" to install "Nook_Color_Google_Apps.zip"
This may be a good time to obtain another backup, if you're paranoid. I did not and wasn't...
Removed the 2 GB mSD card.
Rebooted again, allowing CM7 to do its thing.
Signed into my WIFI network, using the menus.
Signed into the Google Market, selecting all of the Gapps, when prompted. (I figure I can uninstall them, if I find them totally useless.) (e.g. Facebook
app, since I quit it..lol)
Inserted my 8 GB mSD card in the NookColor for the first time and formatted it, from within CM7. I could have made a Win32DiskImage image of the 2 GB ClockworkMod mSD, wiped it out and formatted it for general use, but I like having my own data (media files / apps) separate from my "live recovery environment(s)." Point being, I could have gotten by with just a single mSD card, as tiny as 2 GB and the cheapest class, but I splurged, because I want to keep some music and things on tap, wherever I go.
Rejoiced in the open source goodness.
This would another good time to obtain another backup. I should go do that right now..
Please keep in mind that I might be taking some things for granted. My mind has been altered by being a *NIX System Administrator...
Good luck and let me know if you have any questions.
-v
Great stuff V! So this is what I have decided to do. I will keep my current system until the next stable version of CM is released. Once that happens, i'll go ahead and repartition, reformat, and of course reinstall following all of the proper procedures that i'm too lazy to write out here.
The only other issue I was having with my Nook is that it wasnt recognizing when an SD card was plugged in. I thought it may have been CM7, so I flashed back to the stock OS, and it still wouldnt recognize it plugged in. However, if I have the SD card plugged in, and reboot, it shows the SD card mounted fine. I need to do a check to make sure I can read/write to it, but i'm assuming it will be no problem if it sees it fine. If I were to remove the card, it would not say that the card is unplugged, so theres no instant feedback; it requires a reboot every time to notice if the card is plugged in or not. For me, all I need is it to be recognized and be accessible, as its not like I am going to be taking it out all the time, it will be in there pretty much for good.
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.
[Q] Chronic "Unexpected Lack of Boot Partition on the SD card! Please Report"
Hi,
First let me say - YES, i have searched all of the forums here (and a number of other sites) and seem to have tried almost every option.
I have Chronic "Unexpected Lack of Boot Partition on the SD card! Please Report" problems. The farthest I get guaranteed is the cyanogenmod boot and menu (if I try and bring it up). I'm simply trying to get the SD card with cm7 to boot reliably and not eventually loose the boot partition.
Off and on since spring I was able to burn a CM7 image (verygreen's size agnostic, and one or two others I have since lost track of) to a SD card; have had it boot to cm7 and it work for awhile - but then eventual degraded into the no partition found error. the majority of the time it just doesn't work and results in that annoying purple black screen.
When it does work, it only works for awhile and then the boot partition can't be found; a few very small 3 of times - if I copied a new update it woke back up ad worked for a couple of reboots then lost the partition again.
Anybody got time to take pity on my melted brain and take a few guesses?
Clearly I'm not only missing something - but as things have gotten worse, am now missing more (if that is possible) as I'm going backwards to see why it no longer works at all.
At this point wrong has happened so often, I'm just lost on what even worked way back when I started.
I'm trying to backtrack to where it at least worked a little for a few days...but noob world is decaying into worse world.
I tried a couple of other, older processes and a multiboot menu one that seemed promising (plus could handle the new naming conventions for 7.2 CM7); but that one never even got past the missing boot partition.
I have tried approx 10 2gb SDCards, Sandisk, Kingston, Unknown; Class 4 and mixed.
I have tried 3 8GB SD Cards, Sandisk, class 4
I have tried 1 16gb SD Card, Sandisk, class 4
I have tried a Vivitar Micro SD Card Reader
I have tried the micro SD card Adapters in a laptop, and then in a sandisk USB adapter.
I even tried doing it all using the Nook color via a USB cable.
I even tried leaving the nook color off and connecting the USB cable to the PC to initiate a boot.
Using Windskimager
Using SD formatter
Have formatted Full erase and overwrite.
Tried leaving partition size alone
Tried partition resizing up to 250mb
Tried cm7 zip alone and with gapps
WinXP on 2 desktops and a laptop
It sounds like you have run the gamut of attempted resolutions.
That message is part of the verygreen partitioning script that runs every time the verygreen recovery is run. So, that means the normal boot kernel for CM7 is not loading.
The way the verygreen SD should operate is it starts with uImage and uRamdisk on the boot partition. Those are verygreen's recovery files. The first time it is booted, it looks at your emmc to be sure it is a nook. Then it looks at the SD to see if it has been partitioned yet. If it is not, it partitions it into those partitions necessary for installing ROMs. After partitioning, it looks for a zip to install. If it does not find one, it shuts down and the next time it boots it does the same thing until it finds the first ROM zip to install. If it finds one, it installs it. The first time it installs a ROM, it renames those uImage and uRamdisk verygreen files to uRecImg and uRecRam and they become the verygreen recovery files. And it installs new uImage and uRamdisk files from the zip to become your CM kernel and ramdisk. These are what normally will load in the future to start CM.
Now, with the disk partitioned and CM installed, ordinarily, after the cyanomod logo comes up, it boots by default to CM via the uImage and uRamdisk files. If you intercede with the boot menu and tell it to boot to SD recovery, it looks for uRecImg and uRecRam to load the verygreen recovery. If that is loaded, the verygreen script does all its checking again, it verifies that emmc is a nook, then tries to verify if the SD is partitioned. If it is, it looks for a new zip to install. If, in checking to see if it is partitioned, it cannot find partition 1, it gives that message that has been bugging you.
So I see two things that are happening to you.
First, it is booting to the verygreen recovery first instead of CM. That could be due to a recovery bootloop happening. Look at my tips thread linked in my signature to see an explanation as to what that is and how to possibly get out of it.
Second, after it boots to the verygreen recovery, it does its checking and cannot find partition 1 of the SD and gives you that message.
What I cannot understand is, if you have no partition 1 on your SD, how is it booting to the verygreen recovery?
What you have not told us is what you have on emmc. Stock? Does it boot properly without the SD installed? Or does it go to stock recovery?
After this happens to you again, take the card out and put it in the PC. Tell us what you see. What files are there? Maybe look at it with Mini-Tool Partition Manager and see what partitions it reports.
leapinlar said:
What you have not told us is what you have on emmc. Stock? Does it boot properly without the SD installed? Or does it go to stock recovery?
Click to expand...
Click to collapse
Ditto on that - especially as it boots happily to that error message time after time after the green cyanomod screen appears and I can also do the menu trick to get it to go into recovery.
Just as a clarifier: A number of times it tried to do the install (text flowing by) and at the end claims it can't find the boot partition - odd (unless I have less of an idea of what I am doing than I think) as isn't all that running from that partition? A fairly even number of times it doesn't even run the install and just errors out right up front.
Once in a great while it all works, and I'm good for a few days - but eventually upon rebooting to get it back to normal (either by menu choice or by pulling the sd card) - all I get is that lack of partition again.
leapinlar said:
What you have not told us is what you have on emmc. Stock? Does it boot properly without the SD installed? Or does it go to stock recovery?
Click to expand...
Click to collapse
Yes with the SD card out it boots to stock, although a few time what looked like the CWMod menu came up after I shut down and started up without the SD card installed. Maybe only 2 or 3 times out of WAY to many boots to stock so the kids could read their books while I went to work.
I have even tried resetting the nook to factory on the off chance I did something dumb while mucking about to cause that.
leapinlar said:
After this happens to you again, take the card out and put it in the PC. Tell us what you see. What files are there? Maybe look at it with Mini-Tool Partition Manager and see what partitions it reports.
Click to expand...
Click to collapse
Will do so later tonight and will read the notes in your signature as well.
I saw something go by about the boot partition having to start at the 63 block or something - I can't believe ALL my SDcard adapters / writers are bad, but could the nook reader be screwy? Anyway to do a real test? I've been using the Easeus Partition Manager, but will try the Mini-Tool Partition Manager.
Thanks for the step by step explanation of exactly what happens in the process so I can again get a handle on what it's all doing. That all makes sense to what it looks like it tries to do. Deeply appreciate the time!.
You know, I am beginning to suspect something is wrong with your card reader built into the nook. Some sort of intermittent thing like a pin not making a good connection to the card. Put an ordinary SD in it and see if your stock can consistently read it.
Is your unit still under warranty? You might want to explore seeing if you can get it replaced.
Your downloaded verygreen image might be corrupted. Have you tried re-downloading it?
Sent from my NookColor using xda app-developers app
leapinlar said:
You know, I am beginning to suspect something is wrong with your card reader built into the nook. Some sort of intermittent thing like a pin not making a good connection to the card. Put an ordinary SD in it and see if your stock can consistently read it.
Is your unit still under warranty? You might want to explore seeing if you can get it replaced.
Click to expand...
Click to collapse
I had thought of that too - at stock it seems to have no problems reading consistently; I've done surface tests using partition manager - but haven't located any real other options of hard testing like once done for hard drives.
Plus the fact that sometimes, it will work for days before it craps out.
j8048188 said:
Your downloaded verygreen image might be corrupted. Have you tried re-downloading it?
Sent from my NookColor using xda app-developers app
Click to expand...
Click to collapse
A number of times - I went through and wiped all my downloads for the latest try.
Okay So As I mentioned I went back and wiped everything I had downloaded and restarted (again).
Current status is it's working BUT:
suspiciously too easy this time, worked first shot
- (having said that, I've had looking stupid and asking suddenly means it all starts working - so if it's that I'm good with this)
I've only rebooted into CM7, not back to stock at any time
Have not removed the SD card
I've not had time to load up the apps I like, just the kids games
- (sometimes I think it's the more wanted, the less reliable)
Obviously because I haven't removed the SD card, i haven't been able to retry things enough to recreate the other problems of boots right, yet can't find the partition when it really counts.
Changes (listing stupid things too, just because):
-Went back to my sandisk class 4 16gb HC card
-changed USB adapter back to sandisk one, using a sandisk micro to SD adapter that specifically says sdhc (although I think that is really just marketing
-Formatted the SD in the Nook x2, and did not use SDformatter
-Looked at the partition on the card with MiniTool not Easeus partition manager
-There is a step in verygreen's where you pop the card out and reconnect to the PC BEFORE adding the cm zip, made sure to do that - but could swear I had done it before.
Full painful boring steps that SO far has gotten it past the first stage of creation (again the full test is when I boot into stock a few times, or remove the SDcard for anything, or load my really wanted apps on the android side):
--Also note my lack of class 4 Sandisk cards, I only had one after all. BUT I have had this all work to this point with the 16gb only to have it go south.--
Painful details is so I can catch what is really worthwhile different as even WHEN I get it to work, I'm going back to try all the other cards because it worked so oddly and failed so oddly and differently - but that's just me.
> The 2GBs are:
6 Sandisk SD, don't see any class Rating
2 no brand SD, don't see any class Rating
1 Kingston SD, don't see any class Rating
> The 8gb are SDHC "Adata" Class 4 SDHC
> The 16gb is a Sandisk Class 4 SDHC
Using the 16GB Sandisk Class 4
--------------------------------
> Nook booted to stock
Inserted SD Card
Unmounted
Formatted sucessfully
unmounted and removed
> Put in Red SD / SDHC Adapter
Put in Sandisk MicroMate SDHC to USB Adapter
Put in Front USB spot
> Mounted as E Drive
E Drive shows standard Nook Folders:
.amdroid_secure
B&N Downloads
LOST.DIR
My files
> MiniTool Partition Wizard
Surface test = all good.
>Write the image on your SD card
Used Win 32 Disk Imager
After done with writing, eject and then re-insert the uSD card into your computer.
Two Partitions - 118 and 14.72gb
>Copied to card:
update-cm-7.1.0-encore-signed.zip
Installed correctly
configured wireless
Rebooted = OK
Rebooted = OK
>Turned off
Removed SD Card
Put in Red SD / SDHC Adapter
Put in Sandisk MicroMate SDHC to USB Adapter
Put in Front USB spot
copied gapps
>Boot into Recovery
Gapps installed
> boot
all good
did all set ups like before
added apps (7 games for kids)
rebooted twice
started using
added one app I really like (newshog)
Listening for drumming... nothing so far (Dr. Who reference)
I'm going to go the weekend before rebooting to stock as I can do some adding, and rebooting to android.
Maybe backup the droid side this time around.
THEN the death tests on Monday
-thanks for listening_
p.s. - Yes, I still suspect the card reader somewhat as REMOVING may be where it breaks down.
However, once or twice when I had the Unexpected lack of boot partition error - I was able to bring it back by doing a CM7 update via recovery, despite it refusing to find the boot partiton immediately previously - of course that means the SDcard was removed and reinserted. Most time reinsertion = no help.
You do not need to remove the SD to test booting to emmc. Just press and hold the n button during the boot until the boot menu comes up. Then select emmc/normal and boot. It will boot to stock. The only problem with doing that is now your SD boot partition is 'sdcard'. But should work for testing stock.
leapinlar said:
You do not need to remove the SD to test booting to emmc. Just press and hold the n button during the boot until the boot menu comes up. Then select emmc/normal and boot. It will boot to stock. The only problem with doing that is now your SD boot partition is 'sdcard'. But should work for testing stock.
Click to expand...
Click to collapse
Yes, I know - but it's two separate tests to see which one caused the problem.
Turns out that neither was needed - it was easier to create; my son simply turned it off (not a reboot cycle as I had been doing which worked).
When it was turned on, it no longer boots - it goes straight to BSOD (actually deep purple).
Booting into recovery gets me:
Penguin Logo
rcS!
Populating /dev using udev: done
Initializing random number generator.... done.
modprobe: chdir(2.6.32.9): No such file or directory
Starting Network...
Detected Standard B&N nook layout, emmc first
Error! Unexpected lack of boot partition on the SDCARD!
Please Report!
Poweroff when ready
Since I'm till held to the noob reposting limit of once every 5 minutes and the captha I can barely read - I'll post MiniTool result in about 5 minutes. I'll link a screen capture if i can here.
I tried to boot per menu to the EMMC stock; Clockworkmod Recovery v3.2.0.1 came up. I know I did emmc and what ever the second default is (which should be normal) - I'm pretty sure it was normal.
I offed it and did the same and confirmed it was the default; THIS time it came up Nook stock.
Is there some way I installed something to the stock NOOK and didn't remove it when I restored to factory? The other day I did the restore from that same clockworkmod screen NOT from the stock Nook environment.
I'm wondering if I somehow created my own monster way back when I first started this and was playing in the android environment.
I just edited what I wrote a few seconds ago. The reason it went to emmc recovery is because the recovery flag was not reset when that SD Recovery told you that error. Did you read my tips about recovery bootloops? When you exited 3.2.0.1, it cleared the flag and booted normally.
I still suspect hardware issues.
Just for Ha, Ha's I hooked the Nook via USB to the PC.
G Drive "Removable Disk G" (wants a disk to be inserted)
E Drive "MyNookColor" ( Lots of what I assume to be standard Nook folders.
See my edit above.
Attachement # 1 SD Card from Mycomputer:
Attachment # 2 MiniTool View of SD Card
Boot Partition
Properties using Minitool Partition Wizard (attached):
Used
Partition Info
File System Info
Surface Test of Boot Partition:
Perfect - so no picture.
This is SO aggravating - I almost would accept just knowing why rebooting wrecks something if I knew WHAT).
leapinlar said:
I just edited what I wrote a few seconds ago. The reason it went to emmc recovery is because the recovery flag was not reset when that SD Recovery told you that error. Did you read my tips about recovery bootloops? When you exited 3.2.0.1, it cleared the flag and booted normally.
I still suspect hardware issues.
Click to expand...
Click to collapse
Sorry, apparently not closely enough - got lots of time again.
....didn't expect that anyone would be watching, was busy posting pictures so I could go away and read and think...
Probably is hardware - wish I had some way to vigorously test that, I get that basic use in Nook Stock doesn't really prove everything is good.
Plus I bought refurbished and I have to go dig up the warranty, it was months ago, so not too hopeful and boxes long gone. Don't know how nice B&N is, free replacement charger and cord is one thing - whole another refurb unit is different if I can't show stock SD card reading is an issue, not sure how much they check, but I don't think they care about CM7 off a SDcard not working!
Everything looks perfect on that card. All the right files, partition sizes, etc. You have stock on emmc, CWM 3.2.0.1 on emmc recovery.
I still suspect hardware issues. Powering off makes card semi-unreadable. Can still boot to it but when checking for partition information on SD fails.
If you registered your nook, the serial number is all you need. Refurbished usually have a one year warranty. Mine did. Just tell them card reading is intermittent. Which it is. They are pretty generous. You still have stock on there.
Edit: Try just an ordinary SD and power off, reboot, and repeat many times and in between check card reading ability.
leapinlar said:
Everything looks perfect on that card. All the right files, partition sizes, etc. You have stock on emmc, CWM 3.2.0.1 on emmc recovery.
I still suspect hardware issues. Powering off makes card semi-unreadable. Can still boot to it but when checking for partition information on SD fails.
Click to expand...
Click to collapse
Yup, it's really the only thing that hasn't been able to be changed through all of this.
I've mostly gotten these results - I've managed to make it worse as I redid things and apparently got sloppy. But when going back to methodically following instructions I have what I had months ago. I had hoped buying other cards would make it at least act differently.
Thanks for all of the reviews and double checking, at least I now it's not something obvious (but wasn't obvious to me) that I missed along the way!
I'll have to call B&N and see how strict they are and if they take the "It just has trouble reading any SD card consecutively".
Now where was that review of the Nexxus 7.... and I wonder how all the tablet prices are going to drop especially for the Galaxy Tab. Buying is not as fun but I am completely beat with modding failures.
We are too fast with each other. Lol. See my edit above.
When the Samsung Galaxy S5 (SM-G900F) received official Android 6.0.1, I have manually installed that firmware on my device. Within few weeks ago it shows that my microSD card (64GB) corrupted. At that time if i connect to the PC I can access the SD card without any error. When I tap on "fix it" it format the SD and again it shows the exact same issue.
If I connect this sd card to a PC or a another Android device (runs ICS), these devices are not detect any error. Then I rebooted my S5 into a safe mode and again it shows that issue. However, this issue will fix if I reset the phone. After few days left it again appear that error.
So how do I fix this matter?
My wifes phone has the same issue.
Non rooted phone - 100% stock. Never messed with it.
After the MM update the sdcard just says corrupted.
As soon as a photo is stored or if google play music downloads a track to it it is corrupted.
Really annoying.
Going to try a full wipe now but I'm glad it's not just her phone. I thought the SD card had died and we haven't had it long.
Looks like it's something samsung have done.
Tried formatting the SDCard with a PC?
My SDCard is the same one I've had since I got the phone, through KitKat > Lollipop > MarshMallow, and has never been wiped or formatted, still got the very first photo I ever took with the phone on it
ownjoouk said:
My wifes phone has the same issue.
Non rooted phone - 100% stock. Never messed with it.
After the MM update the sdcard just says corrupted.
As soon as a photo is stored or if google play music downloads a track to it it is corrupted.
Really annoying.
Going to try a full wipe now but I'm glad it's not just her phone. I thought the SD card had died and we haven't had it long.
Looks like it's something samsung have done.
Click to expand...
Click to collapse
No need to wipe SD. Connect that SD to a PC and copy all the files.
*Detection* said:
Tried formatting the SDCard with a PC?
My SDCard is the same one I've had since I got the phone, through KitKat > Lollipop > MarshMallow, and has never been wiped or formatted, still got the very first photo I ever took with the phone on it
Click to expand...
Click to collapse
I think this issue caused by some sort of app or its a firmware issue.
Yeah it's been formatted. I did pop it into a pc to try and save everything but it demanded a wipe.
So I did.
It worked for a little bit and corrupted again. Now when I pit it in the pc it struggles to read it and the phone won't "fix it" either.
Tried to wipe it in a few different programs but it appears the card is corrupted.
It's a 64gb Samsung card. Only had it since January this year. Bought brand new from amazon.
I have another in my note 3 and that is still perfect.
The only saving grace is that Google photos had all the photos synced.
So i'm going to email Samsung about it as there has been no issues with the card until the moment the MM update hit.
ownjoouk said:
Yeah it's been formatted. I did pop it into a pc to try and save everything but it demanded a wipe.
So I did.
It worked for a little bit and corrupted again. Now when I pit it in the pc it struggles to read it and the phone won't "fix it" either.
Tried to wipe it in a few different programs but it appears the card is corrupted.
It's a 64gb Samsung card. Only had it since January this year. Bought brand new from amazon.
I have another in my note 3 and that is still perfect.
The only saving grace is that Google photos had all the photos synced.
So i'm going to email Samsung about it as there has been no issues with the card until the moment the MM update hit.
Click to expand...
Click to collapse
Try MiniTool Partition Wizard
Delete all partitions on the card > create new primary partition > Format to FAT32
MiniTool Partition Wizard free
https://www.partitionwizard.com/free-partition-manager.html
Used that to repair SDCards and USB drives a few times
You can also do it manually with elevated CMD: (Hit enter after each)
------------
diskpart
list disk
select disk x (x = being the disk number of your USB drive/card)
clean
create partition primary
active
format fs=fat32 quick
assign
exit
--------------
Try the card again
*Detection* said:
Try MiniTool Partition Wizard
Delete all partitions on the card > create new primary partition > Format to FAT32
MiniTool Partition Wizard free
https://www.partitionwizard.com/free-partition-manager.html
Used that to repair SDCards and USB drives a few times
You can also do it manually with elevated CMD: (Hit enter after each)
------------
diskpart
list disk
select disk x (x = being the disk number of your USB drive/card)
clean
create partition primary
active
format fs=fat32 quick
assign
exit
--------------
Try the card again
Click to expand...
Click to collapse
Already tried diskpart. No dice.
Just tried MiniTool Partition Manager. Still nothing. It lets you delete the partition and then creates a new partition instantly.
It has however now loaded in windows and shows 4 android folders but even after a delete on the partition and create new it makes no changes to the card.
It also wont let me add anything. Almost as if it is locked to read only.
So thanks for the advice as I can now see the card in windows "sort of". It's really slow though. But I can't put anything on it or wipe it or do anything with it really!
Windows 10 also says there are errors and when you let it error check it just stops responding.
ownjoouk said:
Already tried diskpart. No dice.
Just tried MiniTool Partition Manager. Still nothing. It lets you delete the partition and then creates a new partition instantly.
It has however now loaded in windows and shows 4 android folders but even after a delete on the partition and create new it makes no changes to the card.
It also wont let me add anything. Almost as if it is locked to read only.
So thanks for the advice as I can now see the card in windows "sort of". It's really slow though. But I can't put anything on it or wipe it or do anything with it really!
Windows 10 also says there are errors and when you let it error check it just stops responding.
Click to expand...
Click to collapse
If it still shows android folders on it, then none of the partition commands you've used, nor minitool have done anything, as you'll know, deleting all partitions on a disk completely wipes it
With MiniTool, it works a weird way, you have to basically tell it what you want to do, all steps, and then hit apply at the top, once you hit apply, it then performs the steps it looked like you had already done manually
EDIT - Just a thought, a live Linux CD/DVD/USB might have more luck, Linux doesn't care about permissions etc
*Detection* said:
If it still shows android folders on it, then none of the partition commands you've used, nor minitool have done anything, as you'll know, deleting all partitions on a disk completely wipes it
With MiniTool, it works a weird way, you have to basically tell it what you want to do, all steps, and then hit apply at the top, once you hit apply, it then performs the steps it looked like you had already done manually
EDIT - Just a thought, a live Linux CD/DVD/USB might have more luck, Linux doesn't care about permissions etc
Click to expand...
Click to collapse
I see... I have used Partition Magic in the past and if I recall you had to do this back in the old version. Completely forgot.
I've done that and it's trying to do it. It's going very sloooooooow. But it is getting further than diskpart did!
Will update when it decides to finish.
Good luck, might find it takes a few runs to undo whatever the phone/droid did to it
Unless of course it is physically damaged, but I've not had any problems with MM and my SD
EDIT - Found this from way back in 2010 in my repair folder, "Pen drive repair"
Code:
https://mega.nz/#!XdAW2R5I!sSVna0O4av5rnkTPpGuh_bkXatZpcfmr6X-R-3yjrzw
I tend to keep random programs that have fixed something difficult in the past, and put them in that repair folder, worth a shot
*Detection* said:
Good luck, might find it takes a few runs to undo whatever the phone/droid did to it
Unless of course it is physically damaged, but I've not had any problems with MM and my SD
EDIT - Found this from way back in 2010 in my repair folder, "Pen drive repair"
Code:
https://mega.nz/#!XdAW2R5I!sSVna0O4av5rnkTPpGuh_bkXatZpcfmr6X-R-3yjrzw
I tend to keep random programs that have fixed something difficult in the past, and put them in that repair folder, worth a shot
Click to expand...
Click to collapse
Will take a look at that tomorrow.
It formatted the card but as soon as it finished and mounted it Windows popped up and said there was a problem and it needed scanning.
Once it opened there were still 4 android folders on it....
Annoying.
Yea very, well it's definitely not deleting the partitions if it's still got all the old folders on it
Running the tool as Admin?
It does sound like it's physically damaged, but I thought that about a 16GB flash drive I had, and another 8GB I'd left in a tub on my desk for years because it was dead, then I used diskpart and repaired both of them the same day, and since then, minitool has fixed them
Tell you what you could try, Win32DiskImager, grab any image, say a Raspberry Pi image, and use Win32DiskImager to write the image to the card, I think that uses disk/device rather than partitions to write to, so it should overwrite absolutely everything
Then you can use Minitool to wipe and format back to FAT32 (Hopefully)
*Detection* said:
Yea very, well it's definitely not deleting the partitions if it's still got all the old folders on it
Running the tool as Admin?
It does sound like it's physically damaged, but I thought that about a 16GB flash drive I had, and another 8GB I'd left in a tub on my desk for years because it was dead, then I used diskpart and repaired both of them the same day, and since then, minitool has fixed them
Tell you what you could try, Win32DiskImager, grab any image, say a Raspberry Pi image, and use Win32DiskImager to write the image to the card, I think that uses disk/device rather than partitions to write to, so it should overwrite absolutely everything
Then you can use Minitool to wipe and format back to FAT32 (Hopefully)
Click to expand...
Click to collapse
The trouble with that is I can't write anything to it. It gives an i/o error ever time I try.
I'm tired now so i'm going to head to bed but tomorrow when I have a fresher head i'll take another look.
Will let you know how I go on. Will try that other tool you suggested.
The way Win32DiskImager writes to the disk is different to how Windows tries to write to it, basically like burning an ISO, vs copying files to a DVD
Yea, get some shut-eye, things are usually much simpler after a good nights sleep
Hi, i lost a kingstom 9GB after take out this card from a Samsung. I formatted, and after a few days , i disvovered, that card was set to be encrypted inside the phone, if someone takes out, and formats without unencrypt, on 2 or 3 cycles mor, the card will die, or lock, io root, i never found a solution for this, in my case, the card was locked, (ro), without any error in the partition.
Sent from my XT687 using XDA Premium 4 mobile app
---------- Post added at 11:33 PM ---------- Previous post was at 11:08 PM ----------
Sorry, i wrote wrong, is 8Gb, was the second sdcard lost by me, the first, was a 2Gb used on a nokia e7, that, after format this card the card was locked (ro) at all on all type of sdcard reader , usb, pc. The name, i found, is Cyclic Redundance Error, (formatted without unencrypt the filesystem)
Sent from my XT687 using XDA Premium 4 mobile app
*Detection* said:
The way Win32DiskImager writes to the disk is different to how Windows tries to write to it, basically like burning an ISO, vs copying files to a DVD
Yea, get some shut-eye, things are usually much simpler after a good nights sleep
Click to expand...
Click to collapse
Pen Drive Repair does nothing. Can't even find it.
Tried it another 2 times in MiniTool but still goes through all the motions but returns with the same four folder on the card.
I did a surface test and it found no errors. So reading it is fine. It's the writing to it where it fails.
EDIT: What I have just noticed is MiniTool states:
Capacity 59.64 Used 59.64 Unused 0B
So the card thinks it's full but there is nothing on it.
EDIT 2: And now in MiniTool is just says BadDisk. Looks like it is completely dead.
Well, there's nothing to lose by trying Win32 DI, unlikely to work,. but might as well try before writing it off
*Detection* said:
Well, there's nothing to lose by trying Win32 DI, unlikely to work,. but might as well try before writing it off
Click to expand...
Click to collapse
Gave it a shot. It wont even let me pick it as a device. Windows has stopped adding it to the "My Computer" list also.
I've wasted enough time with it. Only bought it in January this year so I've emailed Samsung both about the warranty on it and also that there is a possibility the upgrade to MM caused it on the S5.
It seems to have happened to the OP and me so I thought I would mention it to them in case.
tl;dr
The card is tested and good (results below), the card reader is good (tested by reinstalling 5.7.4).
So few other people are having this issue, what is going on with my phone?
--
I've read and read, but no matter what I try, I can't get my SD card to work.
Here's the details of how, and what, I installed on my Sprint S5.
I'm coming from Resurrection Remix 5.7.4 MM, (where the SD card worked fine, but did have a few issues with the camera (used open camera instead) and some post reboot oddness (shortcuts disappearing)).
I first formatted card using the windows software sdformatter to FAT32
copied files to SD card using a card reader plugged into PC.
Files copied
RR-N-v5.8.2-20170304-kltespr-Official.zip
open_gapps-arm-7.1-micro-20170327.zip
UPDATE-SuperSU-v2.79-20161211114519.zip
TWRP 3.X
wiped dalvik/cache/system/data
then factory reset
added files to zip queue, Rom, then Gapps, then SU
Flashed
Phone boots fine, initial set up completes.
Tried a reinstall of apps using Ti Pro, but it failed, so started again and used google apps restore during boot. Issues with many apps. So started again, with a "fresh start" option during set up.
I took a few pictures.
I can view them immediately after taking, by pressing the previously taken image image inside the camera app.
Open default Gallery and get the error "No storage. No external storage available."
I installed a+ gallery and it is able to open the images just fine.
Default Files app can browse the SD card.
Aldiko will not download books, as it thinks there is no SD card installed
I've tried (and checking each time)
formatting in card as internal, then back to portable in phone.
Clearing the data/cache for the apps giving errors.
factory resetting
Wiping and formatting the card (on PC to FAT32), and starting again (several times).
Started from scratch again, with a brand new Sandisk card
Tried ZepherOS Zephyr-N Version (Viserion-6.1) Android 7.0
Wiping cache/dalvik only and rebooting
Same "No storage..." error, every time.
I tried ZephrOS. Right after install there is no file manager, but if I click the default app "downloads", I can navigate to the camera folder, then to the image. When I click on it, it opens the image, but still shows the same error "no storage..." even though I'm looking at the image behind the error window. :/
I'm running H2testw, but don't expect an issue, as the same error was on the previous card and the brand new card.
Can I go from 7.0/7.1 to a stock ROM without issues, if so which one?
Update:
SD card test result
Test finished without errors.
You can now delete the test files *.h2w or verify them again.
Writing speed: 7.15 MByte/s
Reading speed: 15.7 MByte/s
H2testw v1.4
UPDATE #2:
I started fresh with a new install of RR 5.7.4 and the card does still have issues with some apps, but is working fine with others. Open camera works fine, and the gallery access the correct card in this ROM. Aldiko still fails as it's trying to download to /sdcard
Most apps are looking for /sdcard but I have /sdcard1
If it helps, it appears sdcard is symlinking to /storage/self/primary
Anyone able to help?
permissions issue? have you gone into the apps mgmt and set the permissions manually?
youdoofus said:
permissions issue? have you gone into the apps mgmt and set the permissions manually?
Click to expand...
Click to collapse
Thanks for the reply. Yes, settings>apps>settings>App permissions>Storage is turned on.
Aldiko, for example, is looking for /sdcard but it doesn't exist. I'm thinking a symlink might fix the issue? But am not familiar enough with Android under the hood, to know what other issues that might cause.
syco123 said:
Thanks for the reply. Yes, settings>apps>settings>App permissions>Storage is turned on.
Aldiko, for example, is looking for /sdcard but it doesn't exist. I'm thinking a symlink might fix the issue? But am not familiar enough with Android under the hood, to know what other issues that might cause.
Click to expand...
Click to collapse
im not familiar enough with the under the hood stuff to know what else coul be the issue either, @AthieN, Mr. guru thoughts?
youdoofus said:
im not familiar enough with the under the hood stuff to know what else coul be the issue either, @AthieN, Mr. guru thoughts?
Click to expand...
Click to collapse
What file system is the card formatted in? Try ext4 or exFAT.
AthieN said:
What file system is the card formatted in? Try ext4 or exFAT.
Click to expand...
Click to collapse
FAT32 this was recommend in most places I read. I thinks it's a paths issue. I'm not sure the format would make a difference to that, right?
syco123 said:
FAT32 this was recommend in most places I read. I thinks it's a paths issue. I'm not sure the format would make a difference to that, right?
Click to expand...
Click to collapse
A fresh install would resolve any path issues. The device can't read the card, which means that it's formatted incorrectly or is incompatible. How did you format it originally? On a computer? Go into the storage menu, and if it's detected, then try using the native Android option to reformat it. Back up your stuff first.
If that fails, try formatting it in recovery.
AthieN said:
A fresh install would resolve any path issues. The device can't read the card, which means that it's formatted incorrectly or is incompatible. How did you format it originally? On a computer? Go into the storage menu, and if it's detected, then try using the native Android option to reformat it. Back up your stuff first.
If that fails, try formatting it in recovery.
Click to expand...
Click to collapse
thanks for chiming in sir! your help is always appreciated
AthieN said:
A fresh install would resolve any path issues. The device can't read the card, which means that it's formatted incorrectly or is incompatible. How did you format it originally? On a computer? Go into the storage menu, and if it's detected, then try using the native Android option to reformat it. Back up your stuff first.
If that fails, try formatting it in recovery.
Click to expand...
Click to collapse
Thanks, I know the OP was long, but I hoped the details of what I'd already tried would be appreciated. I did several fresh installs trying to fix, and formatted every which way I could in phone and on a PC. Nothing has worked.
I've kind of given up on this and have decided to switch to Verizon. Sprint sucks so bad, after 10 years I've finally had enough, so I have to replace the phone anyway.
If you know of a decent phone to get, I'm looking for a recommendation in this thread, https://forum.xda-developers.com/android/help/switching-to-verizon-200-phone-t3588790
Thanks for your attention to my issue. Sorry it's left unresolved. I run my own business and just can't spend this much time fixing my phone.