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.
First off if moderators think this is pointless please move or delete thread!
I've noticed in the many threads for all these android builds people asking about , why I can't install apps like angry birds or such, and many people have answered to unmount and mount after install, well it was brought to my attention today that some people think that because android is running off the sd card , if they unmount something bad will happen, well nothing will happen and it does what everybody says, it will let you install such apps.
Unmount sd card , install, and remount sd card
So here's a fix that ARTO found for anyone not being able to unmount sd card to install apps, thanks ARTO!
Originally Posted by graffitilost
1.you have to down load the terminal emulator from market place
2.open it and type "su" and press enter. allow super user access to it (mine kept freezing so i backed out and re started it. You will need to type "su" again and a window should pop up )
3. then if anything was done right you should see a "#" sign were your about to type the next line.
4.then type "mkdir /data/sd" make sure there is a space between the mkdir and the first /.
5.if everything worked right then nothing should happen except it moves to a fresh line in the emulator .
if you did everything right you should be able to go into settings and unmount your sdcard from there.
hope this helps some people i was going insane trying to figure this one out took me about a week to figure it out.
FYI, I've tried to unmount SD card from settings menu in every Android build I've tested but I still can't get this to work, I still get Application Not Installed...
And when I check the setting again, the unmount SD card setting that was previously greyed out is selectable again...so it doesn't unmount
My response to that is the same lazy ass people that can do a simple search to figure it out, are the same ones who dont read a damn thing on the first page of every thread and just download, then ask questions later to something that is answered in first page.
fmedrano1977 said:
My response to that is the same lazy ass people that can do a simple search to figure it out, are the same ones who dont read a damn thing on the first page of every thread and just download, then ask questions later to something that is answered in first page.
Click to expand...
Click to collapse
Well MY response to that is perhaps you shouldn't ASSUME that just because I'm asking a question it automatically means that I don't read threads when in actual fact I DO and haven't come across a solution that WORKS.
Do YOU have a WORKING solution for this problem?
ARE you going to post a WORKING solution to this thread for this problem? No, I didn't think so.
harpss1ngh said:
FYI, I've tried to unmount SD card from settings menu in every Android build I've tested but I still can't get this to work, I still get Application Not Installed...
And when I check the setting again, the unmount SD card setting that was previously greyed out is selectable again...so it doesn't unmount
Click to expand...
Click to collapse
I don't know what build you're using but I've always been able to unmount sd.
fmedrano1977 said:
My response to that is the same lazy ass people that can do a simple search to figure it out, are the same ones who dont read a damn thing on the first page of every thread and just download, then ask questions later to something that is answered in first page.
Click to expand...
Click to collapse
I totally agree, and I posted this hoping for builders to add the info to their threads. I searched to see what I found in the matter , but only threads of builds come up, and some people are too lazy to search within a thread.
harpss1ngh said:
Well MY response to that is perhaps you shouldn't ASSUME that just because I'm asking a question it automatically means that I don't read threads when in actual fact I DO and haven't come across a solution that WORKS.
Do YOU have a WORKING solution for this problem?
ARE you going to post a WORKING solution to this thread for this problem? No, I didn't think so.
Click to expand...
Click to collapse
I don't know of any other working solution, since unmounting the sd card has worked and I've always been able to install angry birds and any other app.
harpss1ngh said:
FYI, I've tried to unmount SD card from settings menu in every Android build I've tested but I still can't get this to work, I still get Application Not Installed...
And when I check the setting again, the unmount SD card setting that was previously greyed out is selectable again...so it doesn't unmount
Click to expand...
Click to collapse
I have tried most of the android builds available. And never once had an issue with unmounting the storage card.
When you select unmount storage card there is nothing that should be greyed out. You should get a response about the card unmounting and it is ready for safe removal. (Although we can't really remove it) You should also see notification in your task bar. The setting then changes to Mount storage card.
So if you can't unmount your card then look to see what might be different with everyone else. Maybe try a different storage card. Also don't have your phone connected to your pc when trying to unmount.
Agoattamer said:
I have tried most of the android builds available. And never once had an issue with unmounting the storage card.
When you select unmount storage card there is nothing that should be greyed out. You should get a response about the card unmounting and it is ready for safe removal. (Although we can't really remove it) You should also see notification in your task bar. The setting then changes to Mount storage card.
So if you can't unmount your card then look to see what might be different with everyone else. Maybe try a different storage card. Also don't have your phone connected to your pc when trying to unmount.
Click to expand...
Click to collapse
I have this problem too, I can't unmount the storage card, when I click on unmount, it appears to work but it revert back at the initial button "unmount sd card" and there are no notifications. I have no idea whats cause this. what I can say is that I use titanium backup pro for restoring my apps, maybe it has something to do with it...
edit : Found the fix !
http://forum.xda-developers.com/showpost.php?p=8710979&postcount=23
Arto said:
I have this problem too, I can't unmount the storage card, when I click on unmount, it appears to work but it revert back at the initial button "unmount sd card" and there are no notifications. I have no idea whats cause this. what I can say is that I use titanium backup pro for restoring my apps, maybe it has something to do with it...
edit : Found the fix !
http://forum.xda-developers.com/showpost.php?p=8710979&postcount=23
Click to expand...
Click to collapse
thanks for the find Arto! I added it to the first post.
Please how do I reverse the "read and write permission" which I granted to root browser to some apps like app installer and Google play store.
I can't install anything on my phone again
It says "cannot mount operation as read and write"
PLEASE help me
Ok I have a Patriot Micro SD Card (16 GB Class 4) that the tablet does not read.
It does not show as External, or removable or nothing. I put it on my laptop and I can see it just fine.
I deleted everything from it and formatted it for FAT32 and still nothing. Anyone knows y this is happening?
I think its a problem with Thor's rom. I had the same problem and ended up restoring my previous rom because of Thor's rom not accessing the micro sd card.
Use ES File Manager to see the sd card. I found it under favourites (star icon) along the top. Thats wher I find the usb as well.
I am not running Thor's rom anymore but I read in his forums you need to rename External SD to Removable or something like that and then the rom will see it.
cruise350 said:
I am not running Thor's rom anymore but I read in his forums you need to rename External SD to Removable or something like that and then the rom will see it.
Click to expand...
Click to collapse
?????????WTF????
Post a link please, as I never had an issue, so please...
Maybe it was an app that needed a different naming convention.
marcos.lennis said:
Ok I have a Patriot Micro SD Card (16 GB Class 4) that the tablet does not read.
It does not show as External, or removable or nothing. I put it on my laptop and I can see it just fine.
I deleted everything from it and formatted it for FAT32 and still nothing. Anyone knows y this is happening?
Click to expand...
Click to collapse
Some custom ROMs mount their SDCards in a different manner than stock.
Some will be mnt/sdcard, some will be mnt/external sdcard, some will just be /sdcard.
Look for it, because it's there. I only played with that ROM for a few short minutes, but IIRC it's not mounted in the same place as Stock 3.2.
It's not mounted same as in stock HC. And I believe it's labeled as microSD. Don't have my tab on me to confirm, but yeah... had issues trying to find it at first too.
/removable/microSD
shaun298 said:
/removable/microSD
Click to expand...
Click to collapse
There ya go! Thanks Shaun, I knew it was a funky one, just couldn't remember where
does anyone know how to change this as it renders some apps unusable that don't have the ability to redirect to custom path. We should be able to change the mount as name right?
rhtb4theeyeblnks said:
does anyone know how to change this as it renders some apps unusable that don't have the ability to redirect to custom path. We should be able to change the mount as name right?
Click to expand...
Click to collapse
Why don't you go on tegraowners.com and post in Thors thread and he can probably answer your question.
cruise350 said:
Why don't you go on tegraowners.com and post in Thors thread and he can probably answer your question.
Click to expand...
Click to collapse
Considering what I know about linux, I thought someone here in xdaDEV might know where to put something along the lines of "mount --bind olddirectory newdirectory" line. It doesn't do any good for this forum to receive posts to solution that are related directly to development on a forum dedicated to specific devices. Perhaps you might be right and I would get better answers on setting mount names on TOforum and not here at xda-developers.
rhtb4theeyeblnks said:
Considering what I know about linux, I thought someone here in xdaDEV might know where to put something along the lines of "mount --bind olddirectory newdirectory" line. It doesn't do any good for this forum to receive posts to solution that are related directly to development on a forum dedicated to specific devices. Perhaps you might be right and I would get better answers on setting mount names on TOforum and not here at xda-developers.
Click to expand...
Click to collapse
It's nothing to do with that, and everything to do with Thor's ROM's not being a allowed on here, and discussion of them is generally frowned upon as flamewars usually ensue.
If you need support on one of his ROMs, then his site is where you have to go.
I do know it is kind of odd how sdcard is internal room?
and everything that you plug in is removable/ *
It confused my titanium backup to back up on device at first. had to change directory. I should probably check how recovery is backing up.
Then here is a another non thor thought. I have been experimenting with modifying the /etc/vold.fstab and chaing "dev_mount microsd /Removable/MicroSD" to "dev_mount microsd /mnt/externalsd"
From what I have read here in xda, I need to create that folder before hand at "/mnt/externalsd" using root explorer and changing permissions in "/mnt" "/ect" AND the file itself "/ect/vold.fstab" I have gotten vold to stick after reboot but not "/mnt/externalsd" I also think "drive mount" is interfering and setting mounts and would like to know where I might be able to find those settings. Any constructive non-redirectional thoughts are appreciated. I think Im on the right path but I know I'm missing something.
I had been using a 16GB external SD card on my phone and it had been working fine. I decided to swap it out for an 8GB card and now my phone doesn't even see that the card is installed. When I try to mount the card using the storage settings, it tells me that it's preparing the SD card and then it doesn't do anything else.
I've tried reformatting the card, reinstalling CM9, purging both cache and Dalvik. Nothing seems to help. The card works perfectly on my PC. What should I do to get the card to work on my phone?
What happens if you put the 16 back in? Does it mount or does it fall into the same behavior as the 8? So your file explore won't see the emmc or it is just that settings->storage doesn't see it?
Just so we are clear (and I assume you know this b/c you are running nightlies) but I have to ask, you know that External_SD is now the emmc? Sorry.
Thank you for your help. When I put the 16GB back in it acts the same way now. When I browse to the emmc folder with Root Explorer, it shows it as being empty, even though I have the SD Card installed. For some reason, it's just not mounting any of them at all. Very weird.
Did you unmount it before you took it out initially? Maybe try putting it in and rebooting and see if it mounts. Or try rebooting w/o it and them putting it in to see if it remounts. Gotta be something simple cause those are always the hardest to find.
I would suggest a few options then.
1. Post something in the CM9 thread and maybe someone will know a little more about it and possibly some code that you might type in the re-mount it. I have an idea what it would be but I am not running CM9 now, so not sure I can do it ad-hoc.
2. If you can see your internal, then maybe make a nandroid and Odin back to stock 2.1, then reinstall. (but your OP says that you already did that, hmm.)
3. There was a mount fix floating around somewhere on Euphoria or Passion maybe Slim or AOKP. That was mainly for mounting to PC.
See what Faultexception thinks, since he is maintaining the CM9 ROM.
I did unmount it before removing it. I've tried all of the steps you've suggested and even posted on the CM9 thread. Hopefully someone on there has dealt with this before. Thanks for your help. I appreciate it.
I too is having the exact issue, have tried all the above and still nothing.
Haha been having this issue on ics passion for months.. ive just ggotten over it.
My 8gb doesnt work but my exact same model/brand 4gb does.. nothint i can do will fix it.
ive tried secure formatting to every fs imaginable and several other things
Sent from a cell tower to the XDA server to you.
I've tried to do a search for this but can't find it. I'm such a complete novice I may have run across it and not even known I did. I tried to make a bootable SD to be able to use the google app store. I've seen so many instructions now I don't even know where the first one I used is. I think I used CM7 (my Nook Color is version 1.4.1...don't know if that matters). So far, nothing I've done has added the shopping cart but first things first.
Evidently I must have really screwed things up because the cyanogenmod is now on my nook instead of the SD card (which explains why I had so many problems when I tried to redo it). The first thread I found doing a google search was this one: http://forum.xda-developers.com/showthread.php?t=931720&highlight=restore+to+stock.
After reading through it on the last page someone posted that it was a very old thread and to go here: http://forum.xda-developers.com/showthread.php?p=25354258#post25354258 and go down to 15A. But, having the technical skills of a pencil eraser, I can't even figure out which software to download, let alone how to accomplish the restoration. I actually managed to jailbreak my iphone but that was just a matter of downloading software and running it. This doesn't appear to be as simple.
I did manage to find all the files required by the first thread to do the restore, but then I got to this: Select "Restore virtual hard disk image" from the "Disk" menu. My winimage doesn't say that. I am using a new SD card so perhaps that's why. It's at that point that I read all the way through the thread to discover that method? or the firmware? was obsolete.
All I really want is to know which file(s) to download and, if possible, a link to instructions a 5 year old could follow. If I knew a 6th grader I'd just ask them because I'm pretty sure this is hard wired into their DNA. I'm 53 so that's probably half my problem. I can usually figure these things out but this has me completely stumped.
Thanks so much for your time.
You probably used ROM Manager and told it to install CWM and update to a new ROM. The problem is, ROM Manager only works on internal memory installations, not SD installations, so it installed CM to internal memory.
Don't use that old thread to flash stock back on to internal memory, even if you did find the files.
And age is not an excuse for not learning, I'm 68.
Go to my thread referenced above and download the stock 1.4.3 zip file from A15. It is linked in the text of A15.
Make a bootable CWM SD. Use that to flash the stock ROM. Download the file CWM-6.0.1.2-bootable_SD.zip and extract it somewhere on your PC. You should end up with approximately a 300MB .img file. Burn that image to your SD using Win32diskimager per the directions quoted here:
To use Win32DiskImager, find it on the web (here, it's free) and install it on your Windows PC. Open it (be sure to run it as administrator) and select the drive (device) that has your card reader with your SD inserted. Then in the image file box put the location where you have the extracted img file. Then when everything is set right, click on the write button. A warning will pop up asking if you want to proceed. When you have verified that you are going to write to the correct device, click on Yes. (One user overwrote their external USB hard drive by not verifying first). If you get an error message about access denied, it means you are looking at the drive with Windows Explorer. Close Windows Explorer and try again. In fact, it is a good idea to close all unnecessary windows when burning, even your browser.
Click to expand...
Click to collapse
Once the SD is burned, temporarily remove the SD from the PC and then reinsert in your PC. Then copy the Stock zip you downloaded earlier to the SD. Insert the SD into your Nook and boot. Once CWM appears, use the volume up/down keys to move the cursor and highlight "Install zip from SD". Then use the n key to activate it. Select the zip you copied to the SD. Go ahead and flash it.
When it is complete, take the SD out and boot. It should boot to stock.
Sent from my Nook HD+ running CM10.1 on emmc.
leapinlar said:
You probably used ROM Manager and told it to install CWM and update to a new ROM. The problem is, ROM Manager only works on internal memory installations, not SD installations.
Don't use that old thread to flash stock back on to internal memory, even if you did find the files.
And age is not an excuse for not learning, I'm 68.
Go to my thread referenced above and download the zip file from A15. It is linked in the text of A15.
Make a bootable CWM SD. Use that to flash the stock ROM. Download the file CWM-5.5.0.4-bootable_SD.zip and extract it somewhere on your PC. You should end up with approximately a 200MB .img file. Burn that image to your SD using Win32diskimager per the directions quoted here:
Once the SD is burned, temporarily remove the SD from the PC and then reinsert in your PC. Then copy the Stock zip you downloaded earlier to the SD. Insert the SD into your Nook and boot. Once CWM appears, use the volume up/down keys to move the cursor and highlight "Install zip from SD". Then use the n key to activate it. Select the zip you copied to the SD. Go ahead and flash it.
When it is complete, take the SD out and boot. It should boot to stock.
Sent from my Nook HD+ running CM10.1 on emmc.
Click to expand...
Click to collapse
Thank you, I'll try again! It's not that I don't want to learn. I'm asking because I trying to learn. I think I've probably confused myself by reading too much on too many websites and it takes me a little while to figure out technical things. I do appreciate the help. I probably just need to take some deep breaths and clear my brain so I can start over. I just want to make sure I don't really mess it up to the point it's completely unrepairable.
DelilahM said:
Thank you, I'll try again! It's not that I don't want to learn. I'm asking because I trying to learn. I think I've probably confused myself by reading too much on too many websites and it takes me a little while to figure out technical things. I do appreciate the help. I probably just need to take some deep breaths and clear my brain so I can start over. I just want to make sure I don't really mess it up to the point it's completely unrepairable.
Click to expand...
Click to collapse
Notice I changed which CWM you should download. Use 6.0.1.2, it works better for stock.
leapinlar said:
Notice I changed which CWM you should download. Use 6.0.1.2, it works better for stock.
Click to expand...
Click to collapse
Oh, thank you, thank you, thank you!!! It works perfectly!
Sorry to be a bother, I don't know whether this is related. Everything loaded perfectly and it looks just as it did when I first turned it on but now every time I try to use the keyboard, it pops up for probably less than a second and then goes back down. I've tried to "catch" it to see if I could get a letter/digit each time to try and put in but it just goes up and down, up and down. I tried doing the set up with the boot disk in because I know nook reads the sd card first but that didn't help.
However, the version I originally had on the nook color was 1.4.1. Would it make a difference if I used the 1.4.3 instead?
Thanks
DelilahM said:
Sorry to be a bother, I don't know whether this is related. Everything loaded perfectly and it looks just as it did when I first turned it on but now every time I try to use the keyboard, it pops up for probably less than a second and then goes back down. I've tried to "catch" it to see if I could get a letter/digit each time to try and put in but it just goes up and down, up and down. I tried doing the set up with the boot disk in because I know nook reads the sd card first but that didn't help.
However, the version I originally had on the nook color was 1.4.1. Would it make a difference if I used the 1.4.3 instead?
Thanks
Click to expand...
Click to collapse
Did you follow the instructions in the thread where you were supposed to flash a format zip? I forgot to add that in the above instructions. It is not to late to do it. Boot to CWM and flash the format zip and boot back to stock and re-register again. That may be the cause of the keyboard problem.
And being 1.4.3 should make no difference.
Sent from my Nook HD+ running CM10.1 on emmc.
leapinlar said:
Did you follow the instructions in the thread where you were supposed to flash a format zip? I forgot to add that in the above instructions. It is not to late to do it. Boot to CWM and flash the format zip and boot back to stock and re-register again. That may be the cause of the keyboard problem.
And being 1.4.3 should make no difference.
Sent from my Nook HD+ running CM10.1 on emmc.
Click to expand...
Click to collapse
Yes. Installed that as well. However, I did notice when I put the sd card in my computer a few times windows said "disk might be corrupt do you want to continue?" So that might be the problem. I'll go into town tomorrow and get a new one to see if that makes a difference.
Well, I got a new SD card and it's still doing the same thing, the keyboard just goes up and down, up and down so I don't know what to do now.
Cindie
fix it?
Did you ever get it fixed? I did (probably) the exact same thing as you did (installed flashable ROM in eMMC), and it took me hours to get it straightened out
Although I can't say for sure... since I wasn't really taking notes with what I was trying... I think what eventually got me going was using a different bootable (step 1), b/c my microsd card was an off brand (lexar 8gb).
What I did was...
1) made bootable SD card with [generic-sdcard-v1.3-CM7-9-10-larger-Rev5.zip] rather than "so&so size gb card CWR.img"
2) added [nookcolor_1_4_3_signed.zip]
Before I got it to work properly, I had various types of failures-
stuck at "n" screen,
wifi wouldnt work (so I didnt get past nook first start-up process),
appeared to work ok but screen would flash all the time (your keyboard problem)
Eventually I got it sorted, and through all this trial and error, was able to properly put CM10 on sd card whilst leaving nook "original". Lol.
*I'm a newbie at this stuff so please make corrections if I jacked my post up! This was a few days ago and I'm at work... so I can't reference my home 'puter