Related
Hi folks,
I've tried two different builds (a hero and donut with the proper flash for the resolution) and two different microsd cards in my vogue, but I can't get either of them to boot. They usually lock up somewhere around "copying rootfs to nand" or "copying systemfs to nand".
I've read and re-read through a ton of posts on here, and I think I'm following the directions exactly, but nothing has worked so far. I'm hoping someone here can offer up some suggestions on why I can't seem to get this going.
For the record I've been running nfsfan's roms for the last few months without any hitch.
Thanks for any info.
Shado
Just an update, I reinstalled winmo 6.5, and thats working fine. So I decided to take the sensehero build and run it under haret, and that works perfectly.
Hopefully someone here will have some idea as to why it crashes writing to nand...
had size microsd card are you using?
Its the 512mb microsd that came with my vogue....
Assuming you've followed all the guides and have all of the files on your card etc you may just have one of the incompatible phones. Several people have reported these issues as well. Only fix would be for someone to send one to DZO so as he can determine what the hardware change is that's causing the issue.
shadoslayer said:
Its the 512mb microsd that came with my vogue....
Click to expand...
Click to collapse
thats odd....ill look into it.
I've love to send my phone, but then I'd have to use rabbit ears and a tinfoil hat to get my calls
I can take it apart to give some info on the internal components if that would help, or if there is anything I can run/do to provide any sort of debug information. Please let me know.
At this point the only thing I can say after flashing and booting a few dozen times is that it is something related to reading/writing/mounting the SD card. I also found another 256mb microsd and tried that with the same result (so I've ruled out the card). The majority of the time it just hangs on writing to nand, but occasionally it will segfault in that same area of the boot sequence and sometimes it will just hang mounting the sd card right shortly after it initializes bluetooth.
Cheers
Shado
shadoslayer said:
I've love to send my phone, but then I'd have to use rabbit ears and a tinfoil hat to get my calls
I can take it apart to give some info on the internal components if that would help, or if there is anything I can run/do to provide any sort of debug information. Please let me know.
At this point the only thing I can say after flashing and booting a few dozen times is that it is something related to reading/writing/mounting the SD card. I also found another 256mb microsd and tried that with the same result (so I've ruled out the card). The majority of the time it just hangs on writing to nand, but occasionally it will segfault in that same area of the boot sequence and sometimes it will just hang mounting the sd card right shortly after it initializes bluetooth.
Cheers
Shado
Click to expand...
Click to collapse
well mind breaking down what you did to where it got stuck, as in each step beforehand.
I am having the same problem as well. It has to be hardware in my phone. I've tried the two different methods of flashing and both freeze up in linux when it is trying to flash. I've also tried two different micro sd cards and the same result happened on both. I flash windows mobile roms no problem.
gigermunit said:
well mind breaking down what you did to where it got stuck, as in each step beforehand.
Click to expand...
Click to collapse
Sure.
(keep in mind the phone is already unlocked, so I'll skip all the unlocking stuff)
1) Downloaded Sensehero from http://forum.xda-developers.com/showthread.php?t=603028 and also grabbed the hero.user.conf from that thread as well
2) Formatted the 512mb microsd in win 7. I did a full format (not quick format) and used fat32 (I also tried formatting fat)
3) Copied everything that came with Sensehero to the root of the sd (data.img, datafstonand, rootfs.img, rootfstonand, system.sqsh, systemfstonand), created a conf folder and copied the hero.user.conf there.
4) Ejected the SD card in Windows, popped it into my vogue.
5) Grabbed voguimg-320x480-17-12-09.nbh, renamed it to RUU_signed.nbh and flashed it (also tried VOGUIMG.NBH and flashing from sd). When I flashed from Windows, I put the phone in bootloader mode first.
6) After flashing, the phone restarted, and the kernel started its thing. The first time it locked up on writing rootfs to nand (it got to 4% I believe and locked up), I went to bed, so I know it wasn't because I didn't wait long enough.
After that, it was pretty much just a combination of resetting and popping the battery out and back in to restart it. Sometimes it would progress past writing rootfs and get to systemfs or datafs but it would always fail at some percentage along the way. Sometimes after just hitting the reset button (the little one on the bottom of the phone) it would freeze trying to mount the SD card. In ALL cases though, it made it to that point - it would never crash, segfault, etc. before it got to the SD card part of the kernel.
Also, thinking it might be something with Sensehero, I tried the Donut ASOP build from http://forum.xda-developers.com/showthread.php?t=591104 along with voguimg-240x320-17-12-09.nbh. Exact same result.
The only thing I haven't tried is using any of the voguimg's with earlier dates, but I'm not sure what has changed between the different revisions that would make any difference. If you think I should, I can try those other builds to see what happens.
Hope this helps, let me know if you need any more info!
Cheers
Shado
BTW When I get home later tonight, I'll reflash and write out exactly what it says during the kernel loading process (or try to take a picture).
shadoslayer said:
BTW When I get home later tonight, I'll reflash and write out exactly what it says during the kernel loading process (or try to take a picture).
Click to expand...
Click to collapse
I've done that, it doesn't help dzo said. Usually it processes further than it shows on the screen. I've pmed dzo and offered to send him my phone since I'm only a few towns away.
shadoslayer said:
Sure.
(keep in mind the phone is already unlocked, so I'll skip all the unlocking stuff)
1) Downloaded Sensehero from http://forum.xda-developers.com/showthread.php?t=603028 and also grabbed the hero.user.conf from that thread as well
2) Formatted the 512mb microsd in win 7. I did a full format (not quick format) and used fat32 (I also tried formatting fat)
3) Copied everything that came with Sensehero to the root of the sd (data.img, datafstonand, rootfs.img, rootfstonand, system.sqsh, systemfstonand), created a conf folder and copied the hero.user.conf there.
4) Ejected the SD card in Windows, popped it into my vogue.
5) Grabbed voguimg-320x480-17-12-09.nbh, renamed it to RUU_signed.nbh and flashed it (also tried VOGUIMG.NBH and flashing from sd). When I flashed from Windows, I put the phone in bootloader mode first.
6) After flashing, the phone restarted, and the kernel started its thing. The first time it locked up on writing rootfs to nand (it got to 4% I believe and locked up), I went to bed, so I know it wasn't because I didn't wait long enough.
After that, it was pretty much just a combination of resetting and popping the battery out and back in to restart it. Sometimes it would progress past writing rootfs and get to systemfs or datafs but it would always fail at some percentage along the way. Sometimes after just hitting the reset button (the little one on the bottom of the phone) it would freeze trying to mount the SD card. In ALL cases though, it made it to that point - it would never crash, segfault, etc. before it got to the SD card part of the kernel.
Also, thinking it might be something with Sensehero, I tried the Donut ASOP build from http://forum.xda-developers.com/showthread.php?t=591104 along with voguimg-240x320-17-12-09.nbh. Exact same result.
The only thing I haven't tried is using any of the voguimg's with earlier dates, but I'm not sure what has changed between the different revisions that would make any difference. If you think I should, I can try those other builds to see what happens.
Hope this helps, let me know if you need any more info!
Cheers
Shado
Click to expand...
Click to collapse
wow....im speak less, i don't know what the problem could be.
Well, thanks for trying to help out giger. Hopefully with Scizzle's phone dzo can discover whats causing our vogues to act up and we can finally get droid running from nand. And if anyone comes up with anything, I have no problem testing, so drop me a pm.
Thanks everyone!
I have very similar problems as reported here when trying to do this with one of the latest Hero builds. After many resets (due to lockups during the NAND writing process), I am able to get past the writing to get to the Hero/HTC animation screens, but if I'm lucky enough to get that far, it will lockup sometime during those as well.
Back to HaRET for me I guess.
Flashed some day´s ago WP7 but I reverted to WINMO again... and when I try to put an Android Built on it won´t boot...
I get a cmd lines, kernel something and it get the HTC screen and it get stuck in it... Tryied lot´s of diferent sd builds but the result is the same.
I already formated my sd, tried in other WINMO rom´s and other sd and the result is the same!
I have HSPL 1.66
I have the last radio
I have the same as always and previously the the Android worked fine...
Strange!!!
HELP
Please
You said you formatted your SD card, but did you repartition it? When WP7 is installed it consumes all but 200 MB of your SD card so if you try to reformat it, you will only have 200 MB free unless you repartition it.
Did you say you tried other SD cards? Also, are you running Android from the SD card via Haret from Windows Mobile? Or, are you running a NAND Android ROM?
Digital Outcast said:
You said you formatted your SD card, but did you repartition it? When WP7 is installed it consumes all but 200 MB of your SD card so if you try to reformat it, you will only have 200 MB free unless you repartition it.
Did you say you tried other SD cards? Also, are you running Android from the SD card via Haret from Windows Mobile? Or, are you running a NAND Android ROM?
Click to expand...
Click to collapse
1- Sure i repartitioned it at full size... wipe de partition, and format a new primary partition in fat32.
2- Android SD via Haret.
Thanks
Do you have Android SDK installed, so that you can run logcat and see what's happening?
Digital Outcast said:
Do you have Android SDK installed, so that you can run logcat and see what's happening?
Click to expand...
Click to collapse
Nope, don´t know how
Dont think it´s a problem with the Android SD builds, I tryed some diferent and the problem keeps there...
The problem must be with WP7, but now all is the same as before but Android don´t boot and I need Android but don´t want to but NAND on it right away because I like WINMO still...
Please help, I´m not the only one with this problem...
I get a cmd, black screen and some text, the last is...
"jumping to kernel (custom)"
And them it crashes on the green HTC BOOT SCREEN.
lrbpereira said:
Dont think it´s a problem with the Android SD builds, I tryed some diferent and the problem keeps there...
The problem must be with WP7, but now all is the same as before but Android don´t boot and I need Android but don´t want to but NAND on it right away because I like WINMO still...
Please help, I´m not the only one with this problem...
I get a cmd, black screen and some text, the last is...
"jumping to kernel (custom)"
And them it crashes on the green HTC BOOT SCREEN.
Click to expand...
Click to collapse
Try Task 29 via bootloader, flash stock HTC ROM, Reformat SD card on PC and then again on WinMo. Transfer files while in WinMo on SD card or via SDcard adapter, and try booting Android again.
Did you by any chance transfer files on SD card while in Magldr if so the files may be corrupted (known issue) which may explain the problem with kernel not booting up.
Hope this helps.
Sorry for hijacking but nobody will reply in my thread and I'm becoming impatient lol. Can anybody help me?
Hey guys. I'm currently running this ROM, I've been using it for a few days and have had no problems but today, when I turned the phone off and turned it back on, it took ages to turn back on. Then when it did it all looked them same but was kept freezing etc., then up in the notification bar it said "SD Card Removed Unexpectedly" then my phone went crazy with FC's.
So I took out the battery and restarted the phone. Then, it would turn on and go to the lock screen but then it would reboot and be at a continuius* boot loop of the HTC 'Quietly Brilliant' screen.
So then I took out the battery again, this time I took out the SD card too and booted up and my phone was normal again. Obviously with no phone storage though as there was SD card in. Then after I just skipped the setup I put my SD card back in to my phone and went to the music player and all my saved songs on my SD card played. But no internal storage (I have the SD card partitioned with a 1GB Ext3 partition). Then with the SD card in knowing it still works I rebooted again, only to come back to the HTC screen again.
So basically, how can I fix this?
If I'm going to need to format my SD card is there a way I can backup what's in the Ext3 partition?
Thanks,
L.
despy1989 said:
Try Task 29 via bootloader, flash stock HTC ROM, Reformat SD card on PC and then again on WinMo. Transfer files while in WinMo on SD card or via SDcard adapter, and try booting Android again.
Did you by any chance transfer files on SD card while in Magldr if so the files may be corrupted (known issue) which may explain the problem with kernel not booting up.
Hope this helps.
Click to expand...
Click to collapse
Tryed that all...
Formated my sd on a sd reader -> Fat 32
Task 29 + radio 2.15 -> original htc 1.66 rom -> task 29 + radio 2.15 -> duttys 14
My Android simply won´t boot...
Tryed on other sd card the problem is the same...
lrbpereira said:
Tryed that all...
Formated my sd on a sd reader -> Fat 32
Task 29 + radio 2.15 -> original htc 1.66 rom -> task 29 + radio 2.15 -> duttys 14
My Android simply won´t boot...
Tryed on other sd card the problem is the same...
Click to expand...
Click to collapse
lrbpereira - I'm the guy that posted having the same results as you in your other thread (this one seems to be getting all the action, though). Just curious, which ROM are you trying? I've been trying Warrenbread's, but I'm thinking about trying another just to give it a shot.
koz said:
lrbpereira - I'm the guy that posted having the same results as you in your other thread (this one seems to be getting all the action, though). Just curious, which ROM are you trying? I've been trying Warrenbread's, but I'm thinking about trying another just to give it a shot.
Click to expand...
Click to collapse
Hi, i´m on Dutty´s 14 PTG. I tryed Energy and the result was the same...
I think it´s someting that WP7 installed on the phone memory... Don´t know why task29 don´t resolve it... But I can´t put the Android SD working...
And it´s seams that this is a problem that isn´t only mine... you - koz - have it too...
lrbpereira said:
Hi, i´m on Dutty´s 14 PTG. I tryed Energy and the result was the same...
I think it´s someting that WP7 installed on the phone memory... Don´t know why task29 don´t resolve it... But I can´t put the Android SD working...
And it´s seams that this is a problem that isn´t only mine... you - koz - have it too...
Click to expand...
Click to collapse
Sorry, I should have been a bit more clear - I was curious what Android ROM you were trying to run from SD. Have you found a solution to this yet? Did you try flashing back to a stock ROM, then HSPL & then try an android rom from SD? I'm considering giving this a shot, but I haven't had the time lately.
EDIT: I resolved my issue by reformatting the SD again (I've done it multiple times & multiple ways). This way worked for me. First, back up everything you want to keep from your SD card onto your PC. Download this & install on your PC: http://download.cnet.com/Partition-...62200.html?part=dl-6285158&subj=dl&tag=button . With SD card in the phone, connect to the PC in USB mass storage mode. Start Partion Wizard and format the card to FAT32 at 32kb and as a primary drive. After that, drag-n-drop your flavor of Android onto your SD and boot it up. Hope it works for you.
EDIT 2: After getting android running, I reinstalled all my files/folders back onto the SD card, however, this broke android again (I couldn't get it to boot from SD). So I tried turning it into airplane mode while running windows mobile - and it worked. I can now boot to android from SD as long as I first turn on airplane mode. So, I don't know if the above reformatting was part of it. If someone gives this a try, it might be good to turn on airplane mode and try to boot before attempting the above formatting info. Please post results if you try it and I'll try to edit the above.
Just flashed [EU/TMOUS][CWR] imilka's HD Sense Series v2.0 1.84[D2EXT][K:rafpigna 1.7 OC] on my hd2 which is an EU one. Had partitioned my 16GB sd card using MiniTool Partition Wizard, making 2 partitions i.e. about 11GB FAT32 and almost 4GB EXT2, both primary. Just copied the zip file of the ROM on my sd card and ran it through AD Recovery (400mb setup one, which is recommended with this ROM). Everything went smooth but after the installation, even if i run the browser i get the message: Storage Full..you dont have enough free space remaining in your phone's storage, whereas in Settings, SD&phone storage my Internal phone storage shows 3.52GB available. I also cannot install any new apps due to this problem.
Any help would be much appreciated.
its suggested not to use larger than 2gb ext partition
Had a same problem with my favorite Hyperdroid. After flashing i could not even receive any sms becaus they were rejected because of no space. And i did not have anything weired installed... I solved it by completly formatting again and tnen the whole prodcedure again.. Sorry but that was the only way that helped me;-) But actually i could not solve the prob itselve...
Thanks for your reply. Yes, mine is the same problem, can't even receive emails or browse the internet, the message keeps showing up. I'm ready to repeat the whole process by formmatting my sd card, but I have some simple questions (might sound a little naive as i'm new to flashing android):
1- Do I need to make only 2 partitions? Fat32 and an ext partitions?
2- Do I need to keep any other files on any of these partitions except the ROM before I start flashing through Recovery?
3- Do you also suggest, like Richy99 does, to keep the ext up to 2GB only?
just discovered answers to the above questions. Repeated the whole precess, repartitioned my sd card (this time 2gb ext), and finally got rid of that storage full message. There's a lag though...seems to be slow on my hd2. Moreover, I cant uninstall the apps that came with this. The uninstall button remains grey.
sameerfarooqi said:
just discovered answers to the above questions. Repeated the whole precess, repartitioned my sd card (this time 2gb ext), and finally got rid of that storage full message. There's a lag though...seems to be slow on my hd2. Moreover, I cant uninstall the apps that came with this. The uninstall button remains grey.
Click to expand...
Click to collapse
i would use ext3 or 4 if i were you
sameerfarooqi said:
just discovered answers to the above questions. Repeated the whole precess, repartitioned my sd card (this time 2gb ext), and finally got rid of that storage full message. There's a lag though...seems to be slow on my hd2. Moreover, I cant uninstall the apps that came with this. The uninstall button remains grey.
Click to expand...
Click to collapse
a) Use 1GB ext, NOT 2GB.
b) Lag is beacuse its a DHD rom, you need to wait for all the apps to sync or wait for OS to settle down. Let everything sync and then do a few reboots and wait some hours. Once everything has settled lag should be gone.
c) If you want to remove stuff use "System App Remover" from market.
d) Read your roms instructions properly.
[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.
Ok, here's my case laid out. I've searched the forum to death, so I'm pretty sure what I have here is a head scratcher so I'm hoping someone can help me out.
I bought a used HD2 off craigslist. It came with WP7.5. When I plugged in the data cable (i.e. USB cable), I didn't get a prompt for mounting to SD card. I installed Zune and got all the drivers (going through the MS troubleshooting list), and the phone was able to mount to Zune with only 200 mb. No problem, right? This error is common. I find out that if I use an SD Formatter, I can clear the card, which is 16gb, back to it's original state by mounting the card through MAGDLR.
After restarting the phone, I still couldn't get more storage than the allotted 200 mb, except it had decreased to ~150 mb. My phone was filling up quickly. I researched that, under WP7+, there should be a "connections" option under settings for mounting the SD card through the cable, so I thought "Hey, maybe it's because this flash of WP is missing something." so I reflashed my HD2 to stock rom using a guide.
While as a stock HD2 (T-mobile), I had now 600 mb of space on the phone to use, but I noticed that the HD2 still wasn't sensing my card. Bad card, maybe? So I tried an 8 gb I had, a 2 gb I had, and a 32 gb I KNOW works from my tablet (and still works on my tablet). I decided maybe it was the ROM's fault, so I decided to flash android on it, since I'm used to android from my other phones.
So I follow Jayce's guide and put on the proper HSPL, MAGDLR, the right Radio, and CWM to flash a new android ROM and banish my problems once and for all.
PROBLEM, I'm stuck here because (dope!) even MAGDLR and CWM DO NOT SENSE MY CARD(S). Now I'm stuck and I don't know what to do. Is there a way to get it running at the very least? I know the microSD slot is pretty much the most reliable piece on the phone, so I don't think it's broken.... but maybe it is?
So either a) somebody help me get the phone running with any ROM or b) somebody help me figure out how to get the SD cards working.
Sh*t out of ideas here.
[edit] OK! I FLASHED IT USING THE OL' HOLD DOWN THE "DOWN VOLUME BUTTON AND FLASH THE STOCK" Could still really use help with the SD card sensing thing though....
it wouldn't be the first bad sd card slot reported here, so, reliable it may be, break proof it isn't.
samsamuel said:
it wouldn't be the first bad sd card slot reported here, so, reliable it may be, break proof it isn't.
Click to expand...
Click to collapse
Okay, following what has to be my 5th reformat of the same card, it worked!!!!! I quickly installed android on it. I'm not taking that card out anymore. It'll stay inside
xubii said:
Okay, following what has to be my 5th reformat of the same card, it worked!!!!! I quickly installed android on it. I'm not taking that card out anymore. It'll stay inside
Click to expand...
Click to collapse
I had a bad SDCard too, it doesn't work in recovery but does in the ROM... I think you should really think about replacing your card. Flash memory has a limited amount of writes, so I wouldn't be surprised if you lose your data or find it unusable one day.