Related
ugh, here we go:
I am running cyanogenmod 4.04 with the latest recovery. I have the hard spl. I am not themed. I am using auto apps2sd with partions.
Soooo, this was working well until I had to take out my sd card for something. As soon as I did, the whole phone froze up, so I restarted. The first 'alert noise' that usually occurs after startup happpened at the end of the android screen. After this I was bombarded by a HELLUVA lotta force closes. I mean, all over the place. In these was included advanced launcher which I had my home set as as default. They would all loop, and I couldn't do anything. Oddly enough, the notification bar was still working, and I was able to view and answer an email!
My question is as follows:
1: what did I do wrong
2: what can I do to fix it.
-
For several reasons, I would really like to avoid wiping at the moment, so if there are any alternatives, I'd appreciate it.
1) took out sd card
2) fix_permissions in recovery
evilkorn said:
1) took out sd card
2) fix_permissions in recovery
Click to expand...
Click to collapse
Then I can put it back in and reboot?
EDIT: I did the above and nothing interesting happened.
It might be worth noting, however, that I rebooted without the sd card, installed ahome lite, and then didn't set a default home. I was able to use 'home' with the sd card in, and that works fine, as well as the apks packaged in cm (dialer, gmail, alarm clock ect.)
So basically it's like this with Apps2SD... say you are running Windows on your desktop, but you have all your programs installed to an external hard drive, you have a whole lot of programs up and running (not to mention you have your pagefile split across your drives - dalvik-cache), and you rip that external hard drive off. What do you expect to happen? Major system failure.
When you are running Apps2SD, the only time it is safe to remove your SD card is when the phone is NOT booted or booting. Meaning, it has to be off or in either the bootloader or recovery modes.
You may have to format the EXT partition of your SD card, wipe, and reflash your ROM.
daveid said:
So basically it's like this with Apps2SD... say you are running Windows on your desktop, but you have all your programs installed to an external hard drive, you have a whole lot of programs up and running (not to mention you have your pagefile split across your drives - dalvik-cache), and you rip that external hard drive off. What do you expect to happen? Major system failure.
When you are running Apps2SD, the only time it is safe to remove your SD card is when the phone is NOT booted or booting. Meaning, it has to be off or in either the bootloader or recovery modes.
You may have to format the EXT partition of your SD card, wipe, and reflash your ROM.
Click to expand...
Click to collapse
****.....let me see if I an access my sd card with this adapter, hold on.
ugh, put the card in and reboot into recovery and go to the console and type 'fix_permissions', you have to have cyan recovery or use the one with more options like the RA, link in sig, i think there is even an option for it and you don't have to type it in console.
I have updated ClockworkMod Recovery for the G Tablet to support the internal SD card a bit better.
There is now an advanced option to partition the internal SD card. This can come in handy when the internal partitions get hosed (which seems to happen on occasion with this device). To keep it close to stock you can select a 2048MB Data Partition and the remaining ~13GB will go to the internal SD card. You also have an option to format the internal SD card space as well as mount it as /emmc. You can still format the external SD card using the existing advanced option.
This recovery still uses the external SD card as its primary mount for actions (install ROM, backup, restore, etc.). However, the recovery is configured to “fall back” to the internal SD card for these actions if (and only if) there is no external SD card available to be mounted.
As always, credit to Koush for creating ClockworkMod Recovery in the first place.
----------------------
This is the current BETA release of the CyanogenMod 6.1 port for the G Tablet. There are still several issues, but it is far enough along that I use it as my daily system. Please review issues and post new ones as needed at the Issues page linked below. Feel free to leave feedback in the forum, but I may not be able to follow up on it. The best option is to catch me in #tegratab on Freenode IRC.
CyanogenMod 6.1 Beta4
CyanogenMod 6.1 Beta4 - MD5
ClockworkMod Recovery
My site: bekit.net post
gapps does work, but I probably should not release that here. Just make sure it is the MDPI variety and has an update-binary compatible with tegra.
*Note:
This version now matches the standards for SD card mounting on devices with both internal and external SD card space. This means that the external SD card slot now mounts to /mnt/sdcard (symlink /sdcard) and the internal space mounts to /mnt/emmc (symlink /emmc). The device properly recognizes the internal vs. external space and allows proper unmounting and handling of the external SD card. This also means that some apps (if they were coded poorly) will not recognize the internal SD space as available SD card space and will require you ti insert an external SD card. I will see if I can do something about the default apps (read: camera) that have this problem; other apps will need to be fixed by the developers.
Changelog:
CM6.1 Beta4:
Updated SD mappings for internal/external SD space to match standards (see note above)
Using latest available source from the CyanogenMod repo
Updated kernel to latest G Tablet version (still waiting on source so we can build our own)
Updated to the lasted drivers available for the G Tablet
Included updated libGLESv2 from nvidia (Angry Birds!)
Proper setup of CPU values - this allows the folio Flash APK to install properly
Matched fingerprint and device settings to latest G Tablet values
ClockworkMod Recovery 2.5.1.3 (2010.12.11):
Added options for managing the internal SD card
Using latest available source from the CyanogenMod repo
ClockworkMod Recovery 2.5.1.2 (2010.11.24):
Updated SD mappings to match standards (see note above)
Using latest available source from the CyanogenMod repo
Enjoy!
-Brint (bekit)
Nice may try it on one of the other g tabs I picked up today.
Thanks for all the work
Happy Thanksgiving to you too!!! and I will enjoy this for desert.
Works like a charm! We all love you! Now wish this damn camera would work right >_<
Awesome, Thank you for putting this together!
Do you know if it addresses the slowdown problem that was present in cmb2? (After using it for a while,browsing etc would slow down till you did a reset)
As usual amazing work. Everything is rock steady. Only things I added were Spare Parts to maximize some apps and a certain keyboard replacement that starts with S.
titanium backup is not seeing my internal sd card, is this a known issue? also i'm unable to mount sd or external sd to computer, the window closes when i try to. the rom seems to run smoothly though.
Thank you Bekit!
First time posting here in ages. Is there a trick to getting the audio working? No audio here, except for a freak accident. Not sure how or why it started working out of the blue, rebooted now it's gone again.
happy turkey day!
Crimton said:
titanium backup is not seeing my internal sd card, is this a known issue? also i'm unable to mount sd or external sd to computer, the window closes when i try to. the rom seems to run smoothly though.
Click to expand...
Click to collapse
Same here and Kobo wants /mnt/sdcard. I've uninstalled both and re-installed in case something changed with beta4 that they'd cached but it didn't change anything. I've found the Titanium Backup official support site (www.legendroid.com/forumdisplay.php?27-Titanium-Backup-Official-Support) but haven't done through it yet ... turkey'd almost ready so it may be a while. Folks out east (or north or anywhere that this isn't a holiday) may wanna check in there.
EDIT: Meant to thank you, bekit, for your work on this. Sorry, was distracted by the smell of nearly done turkey!
No SD card here as well. Do I need to install the newest recovery?
Will be kinda hard to download anything.
Thanks for this update! As with all releases, I will try this one out as well. It's great to have choices in firmware, and at this stage, these firmwares are really-REALLY nice.
Happy Thanksgiving to you, too!!!
puppyfarts said:
Thank you Bekit!
First time posting here in ages. Is there a trick to getting the audio working? No audio here, except for a freak accident, not sure how or why it started working out of the blue.
happy turkey day!
Click to expand...
Click to collapse
Try plugging/unplugging the headphones, has worked for me in the past.
Turbo4V said:
Try plugging/unplugging the headphones, has worked for me in the past.
Click to expand...
Click to collapse
Mind=BLOWN! Thanks!
I can't get the recovery installed. Can I get an update.zip?
I can't install anything from the market. I keep getting not enough room on card? I have internal card selected in CM settings.
I tried installing this, making sure to put on the new clockwork and clearing user data, and when I was all done and went to reboot I got "magic value mismatch" no matter what I did. I was able to get into nvrecovery but flashing the old clockwork wouldn't fix it. I finally gave up and flashed the stock image to get going again, blowing away my internal SD titanium backups. Not a huge loss, but if anyone else is thinking about trying this, copy anything important off the internal SD just in case.
*edit*
Whoops, scratch that, apparently the nvrecovery stock image install doesn't wipe the SD, everything was there when I was done and flashed Clockwork again.
This is running well and I am seeing very smooth scrolling in the browser. That has been my biggest complaint with the gtablet.
Spaztik said:
I tried installing this, making sure to put on the new clockwork and clearing user data, and when I was all done and went to reboot I got "magic value mismatch" no matter what I did. I was able to get into nvrecovery but flashing the old clockwork wouldn't fix it. I finally gave up and flashed the stock image to get going again, blowing away my internal SD titanium backups. Not a huge loss, but if anyone else is thinking about trying this, copy anything important off the internal SD just in case.
*edit*
Whoops, scratch that, apparently the nvrecovery stock image install doesn't wipe the SD, everything was there when I was done and flashed Clockwork again.
Click to expand...
Click to collapse
Same thing happened to me. "magic value mismatch" It's not to magic, lol. Off to NVflash I go. (lost everything).
flashed new cwm 2.5.1.2, then flashed beta4... mismatch lameness
anyone figure this out yet?
puppyfarts said:
Thank you Bekit!
First time posting here in ages. Is there a trick to getting the audio working? No audio here, except for a freak accident. Not sure how or why it started working out of the blue, rebooted now it's gone again.
happy turkey day!
Click to expand...
Click to collapse
Try pluging in headphones and then take them out.
Had the same exact problem.
(Oops... missed the fact that it was already answered!)
Thank you SO much! This is finally a usable ROM for this hardware-rich unit.
I have two questions:
1. Can anyone compile/provide a tun.ko file for this kernel? I would like to use VPN Connections on this device.
2. Is anyone else experiencing odd slowdowns after the device wakes up? When I first boot the device works smoothly. After the device is off and then turned back on, I sometimes experience an unbelievably laggy performance...
Thanks in advace!
I've gone through 3 nook colors by now because the recharger cable continuously breaks and best buy refuses to simply replace the cable and instead replaces the ENTIRE SYSTEM (I guess it makes sense from their point of view), so I'm pretty experienced when it comes to rooting and un-rooting/factory resetting the nook, and when I received my latest one I decided to try a dual boot after being slightly impressed by the 1.4 update and enticed by the numerous comics now available on the nook store.
I used this method manually rooting the nook after repartitioning the internal data to the pre-blue dot packages, and finally booted up my old backup through a CWM flashable sd card, then unmounting the sd card while in CWM and then mounting my data SD card. Everything was working really well, and I was very pleased with my nook and it's improved performance and accessibility to the much better stock reading software, while still being able to access kindle and other games
But then, after leaving it alone for a couple of days, i booted it up to play some fruit ninja, and suddenly my nook was unable to read the sd card. It said the card needed to be formatted, and that unreadable file types were found, and oddly enough the stock OS said this as well. Then after a couple of reboots, it could read the SD card just fine. But then, many apps started either freezing on boot, or immediately closing on startup. I tried to boot into CWM recovery, but I kept getting an installation failed screen, and after flashing CWM i was finally able to boot into it just fine.
My only problem now is occasionally apps will again close or freeze, and occasionally the system will reboot by itself or simply force shutdown. Also, it says that my 8gb data SD card has no free space which conflicts with my 385 mb when I plug it into my computer. I'm a little confused.
If anyone could help with my app problems, that would be much appreciated.
Also, Can someone explain the differences between the Internal Storage, /mnt/emmc, and /mnt/usbdisk. I'm confused on what their purpose is considering their different data, and where the dual boot roms are stored.
Thanks and Cheers
-Meaty
You have mentioned about "dual boot".
What is the other ROM you are running now?
What is your uSD brand?
[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.
Hi everyone,
I have a S5 klte with Samsung SD card formatted as Internal Storage.
Yesterday, I thought I will update my Slim rom 0.6 to the newest version 1.3. After flashing the rom, wiping cache and dalvik cache phone stuck on boot animation. Now, the stupid thing I've done was to push "Fix permissions" in TWRP recovery. After that, I was able to boot my phone, but it lacked most of the apps which were installed previously, none of the google services would work, I could see all the pictures/videos in my gallery, however. When I tried to backup those to my PC, I could see only a small part of it. Tried flashing previous rom, different gaps, wiping cache - nothing.
Then, I thought, I will do a regular wipe, since I didn't cared much about lost apps. From the experience I knew, that wiping does not touch media stored in internal storage. So I wiped my phone and restarted (with old slim 0.6 flashed before).
Now the phone works great, but there is HUGE problem. All internal storage is gone including pictures and videos and Samsung card, which was formatted as internal storage, now says "Unsupported card" and asks me to format it either to external or internal.
What could I do? Is there any way to "re-link" the internal card so that I could see its contents? Or I should use some file recovery software and see what I can get?
Thank you in advance for the help!
Did you try popping out your SD card out of your phone and using an SD card reader to get data off it onto a pc
Sent from my iPhone 4s using Tapatalk I also own a g900v
Well, I am using Mac for the moment, so when I try to connect sd card to it the notification pops up, that drive is not accessible, or something similar.
Tomorrow I will be able to try it on PC, but I believe nothing will change. The biggest problem is that sd card is formatted as internal storage and linked with phone's internal storage. I do not know these inner mechanics, but I believe that I need to somehow recreate that link.
Hmm your probably right good luck trying to fix it
Sent from my iPhone 4s using Tapatalk I also own a g900v
Sadly, there is not much of info due to complexity of this issue. Still waiting for at least some hints what should I do...
UPDATE: PC does not respond to the sd card at all, there is no sound, no drive, nothing.