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.
i was just trying out andftp (unsure if this was the reason, but it was the last thing i did) off the marketplace and couldnt get it to stay connected. decided to end that and reboot, phone started back up saying sd card not found and the notice asks me to "format cancel"
just put the sdcard in my pc and its showing everything on the card so i'm backing it up. have been using it no problem for the past 20days so its not the format of the card or anything. once i'm done backing up i figure i'll reformat the card and see how that goes but couldnt find anything searching the forums. anyone had this problem or possibly why it started doing this after a restart of the phone?
psylink said:
i was just trying out andftp (unsure if this was the reason, but it was the last thing i did) off the marketplace and couldnt get it to stay connected. decided to end that and reboot, phone started back up saying sd card not found and the notice asks me to "format cancel"
just put the sdcard in my pc and its showing everything on the card so i'm backing it up. have been using it no problem for the past 20days so its not the format of the card or anything. once i'm done backing up i figure i'll reformat the card and see how that goes but couldnt find anything searching the forums. anyone had this problem or possibly why it started doing this after a restart of the phone?
Click to expand...
Click to collapse
I had this issue when I had my CLIQ. This was the beginning of my SD card dying. I hope its not what yours is doing, but just was similar to what happened to mine before it died on me all together.
i just got it roughly 20 days ago, hope its not
I've had a similar problem with my SD card. I could read the files just fine on a pc - albeit a manuell fsck found errors which could not be corrected even after several passes.
After reformating the card it now works fine again. This happend about two weeks ago.
after backup and reformat it still wouldnt read in phone, tried putting files back on also. finally booted phone up without a sdcard in, rebooted with it in and it recognized it. stock, not rooted, hopefully doesn't happen again
hey im a little new to droids. i have rooted my mytouch 4g and was installing iced glacier for the rom and it was successful. but now get an error message saying sd card read only. any ideas o how to fix?
Can you still access the sdcard rw through recovery?
BTW, make sure you post questions in the q&a section. I'm sure when a mod sees this they will tell you the same and move the thread.
My MyGlacier 4G MINE!!!
Had same issue, card probably had a sector corrupt. Plug into pc and right click select check card for errors and fix. It will say it found and fixed errors, you will be good after that. Thats what I get when I buy a 8gb class 6 card for $7.99
Sent from my HTC Glacier using Tapatalk
i had to pull everything off of it onto my computer then reformat the sd card then put everything back on it. i guess i had a corrupt file on it
I was in the process of pulling, reformatting, etc. But, as Johnowa stated, the option to "scan and fix", which I usually ignore, popped up, I thought, "Why not?", and it actually fixed the problem. As was mentioned, it was likely a bad sector. Hope this helps.
As the others have said, see if you can "scan and fix" or pull everything off it and reformat it. BTW, its Android. Droid is Verizons line of Android phones.
Kienz said:
I was in the process of pulling, reformatting, etc. But, as Johnowa stated, the option to "scan and fix", which I usually ignore, popped up, I thought, "Why not?", and it actually fixed the problem. As was mentioned, it was likely a bad sector. Hope this helps.
Click to expand...
Click to collapse
I would add one thing here.
Make sure you copy everything off the card BEFORE you "scan and fix" I had done that before without loosing anything. This time (on a 16 GB card I had used in another device previously), after it did the scan and fix, it generated a very long list of bad sectors, etc. and the result was an effective loss of most of the contents.
After the "fix", I reformatted and copied everything back without a problem.
Also... is this when its plugged in? I have noticed that mine likes to go into DISK MODE everytime I plug in the USB to charge. After I chnaged that in settings, I found my cable is slightly bad because if it moves the wrong direction, it pops it into disk mode again.
my apologies for posting in the wrong section i wont let it happen again. so ive tried pluging the phone into the pc to clear or format and my pc wont recognize it tried uninstalling the driver and reinstalling it and tried removing it ftom the phone and putting it in a reader directly into pc and still nothing. most likley i will go buy another today. i can access format sd card from clockwork mod but it stood idle for about 10 minutes saying formatting sd card is that normal i just removed the battery and stopped it
tbigtone210 said:
my apologies for posting in the wrong section i wont let it happen again. so ive tried pluging the phone into the pc to clear or format and my pc wont recognize it tried uninstalling the driver and reinstalling it and tried removing it ftom the phone and putting it in a reader directly into pc and still nothing. most likley i will go buy another today. i can access format sd card from clockwork mod but it stood idle for about 10 minutes saying formatting sd card is that normal i just removed the battery and stopped it
Click to expand...
Click to collapse
Sounds like you got a lemon. If this is the one you got with the phone I would call t-mo.
just got off the phone with tmobile they are gonna credit the cost of a new sd card to my account due to htc has no parts available. thanks guys for all the help. Happy Holidays!!
Please post questions in Q&A section.
Ok, I've been reading the forum until my eyes are popping out. I can not find my situation. So please forgive but I've been searching.
Bought a NC for my daughter for the purpose of Rooting it using the SD method. I followed the routine install last Monday:
1. Using WinImage, I burned the Size-agnostic SD Card image on the SDcard (Transcend 8GB Class 6 SDHC) using my HTC Incredible as my card reader.
2. Downloaded cm_encore_full-131.zip and moved it to the card.
3. Installed the SD card and bam! Everything was working and I was happy as hell!
4. I went through the process and got gapps-gb-20110307-signed.zip installed and I was working away downloading apps and stuff.
5. Downloaded update-CM7-dalingrin-OC-sd-063011.zip and got that loaded and our NC was flying high. And since we have the right kernel, downloaded Nook Tweaks and we can use a case with a USB keyboard with no issues playing Angrybirds and everything. LOVING IT!
I was happy as hell cause I wanted to be done in my limited time before tomorrow because my daughter is staying with my mom and this will give her something to do.
THEN today after powering it off. I powered it back on again and the following happened:
1. It appears to attempt boot from the SD card.
2. The green Cyannogen logo comes up and under it it says "loading..."
3. However, instead of the Android on the surfboard coming up like before, it will boot up to the stock Android with the N splash screen first then to the stock interface???
I tried several times powering it on and off to see if it was just a glitch but it still did it. Soooo, I redid the whole process again. But once I tried to boot from the SD card with CM7 loaded, the same thing happens. Green logo, loading..., then back to the NC stock OS.
I tried downloading the image a few times to make sure it wasn't corrupt and reburned the img on the SD card, tried booting it again and still the same results. (I did this whole process at least 5 times!)
Sorry for the long read but I am frustrated and disappointed that i will have to tell my girl that it's not working like it was earlier. Can someone give me any advice to try? Or what can I possibly doing wrong? I'm beyond my skill sets at this point. The only thing that I can find on the forum is that it maybe the Transcend SD card but it worked find for three days. Can it really suck that bad after 3 days? I only have tomorrow to work it during the day so If I have to I'll go to Costco and get a Scandisk over there as some have mentioned, I will. But if there is something someone can tell me to try, please let me know.
Thanks in advance!
You are probably on the right track with getting a new SD card. One of two things happened: the SD card failed during the initial "burn-in" period or the Nook's reader slot did. The card is thebmore likely point of failure.
If the problem persists with a new card, get your Nook back to B&N for warranty replacement. Just don't let them have your SD cards an you won't lose all your work
P.S. Yes, ANYthing electronic can "suck that bad after just 3 days". If an electronic component is going to fail, it will either be DOA (and even cursory quality control will catch it) or it will fail shortly after being placed in regular service (burn-in). If it survives the first 60 to 100 hours of use, it will PROBABLY last for years.
Thanks DiDGR8!
I hear you on the electronic part. I was also really tired when I posted. I guess I just didn't want to believe that the card was the issue or rather could be the issue specially when I can read the card from my phone and read it from the NC in the stock interface. It had to be something I did or forgot to do. But I've seen stranger things happen. LOL Things can break.
As soon as I can, I will run out and get a new (Scandisk) card and I hope that it resolves the issue. I hope it is not the NC's reader slot because I hate going through the "returning process" plus we have to leave tonight.
I'll post my results as soon as I can today.
I often not to believe the uSD card itself is the problem but I guess this time, I believe it.
I have the same card as yours (Transcend 8GB class 6), testing random read/write small block and the result were about 0.08 (meaning bad). Sure enough, running CM7 off it last few days then I got ton of FC errors. I now then boot CM7 from eMMC and use the card as an external storage, the card still gives me some problems.
Try Sandisk and keep yours fingers crossed.
Well at least I'm not alone. Thanks votinh!
I wanted to avoid running it from eMMC so that if i wanted to I can do the warranty thing.
Well, I got me a Scandisk 4Gb Class 4 this morning in addition to a card reader/writer to eliminate my phone as a card reader.
Followed the steps and still the same thing. However, I did noticed this time some I/O errors come up during the installation process.
So, I let it go to stock so i can test my phoness SD card (Scandisk 2GB) and it worked just fine. So, I'm really stumped now.
I'm going to try flashing it again a couple of more times. I can go to B&N and tell them it is not working but if i show them it does work reading my phone's SD card. unless i just push them for an exchange.
OK, tried the the latest stable and now the Driod comes up and it is in a loop. I abandoned that all together. Need to stay focused.
So, I went through the process again using #133 on my Scandisk 4GB and tried to boot with it. Same results again Green logo, loading..., then back to the NC stock OS.
However, this time I was able to take a pic of the screen so I can copy what I saw when I saw I/O errors during the installation. So at one point I got:
end_request: I/O error, dev mmcblkl, sector, <insert number>: this flashed down the screen quite a bit
also
JB2: DetectedIO errors while flushing file data on mmcblk1p2-8
Ok so I went back to the Transcend card and did #132 but using my new reader. This time it seem to install clean. When I powered it back up, this time str8 to the "Read Forever" splash screen and back to stock. Weird.
So, I redid the 4GB card again and got the I/O errors again same thing the "Read Forever" splash screen and agian back to stock. It's like it's telling me to go F*** myself.
At this point, I'm thinking its the NC reader reading off the card itself. I tried 2 brand new cards, dif brand, dif reader/writers, multiple downloads of the img and installers...I don't know what to say. I should just root it to eMMC but if i'm having trouble with the SD method and I go eMMC and that messes up I won't be able to return it on Warrenty. What am I doing wrong? Can anyone give me anything else, I'm desperate and ready to fling it out the window. LOL
LOL I love the way I'm bumping my own thread here.
So, I went to B&N and got me a new replacement NC without any hassles.
I ran through the routine from scratch with CM7 #133 (which I believe has the OC kernel in it) on my new Scandisk 4GB Class 4 without the gapps.zip just to take it one step at a time.
I powered it on and prayed to the CM7 gods. I see the same I/O errors on the install and I also saw chown: cannot access '/tmp/backuptool.sh' : No such file or directory which I've seen before as well. However, this time the droid came up refreshing itself in a continuous loop. Like when I tried the stable version earlier. I did this twice and the same results.
At this point I'm thinking it maybe the WinImage. I'm using Winimage V 8.50? So, I downloaded Win32disk imager to give it a try and using my phone as the reader again because that was the last known combo. Again, the same errors. Then the Logo, loading…, this time blank screen…crickets…
I’m out of ideas…I had a clean install once on Monday worked fine until yesterday and I can’t do a damn thing.
Different SD cards, 2 brand new NCs, different readers, multiple downloads of image, installer, etc. Two dif imagers as well…Someone please tell me you are missing a step or doing something working because this does not make any sense… Booting in recovery mode maybe?
The only idea I have is a longshot. When you were getting the looping bootanimation (the blue Andy on a skateboard), or the "crickets"; how long did you wait before aborting the boot?
I have seen it take a LOT longer in those steps than I ever remembered (or thought reasonable). I'm talking 5 or 10 minutes.
It has something to do with recreating internal partitions and the dalvik cache (IIRC). It's been so long since I booted off the SD card, I'm not really sure what is supposed to happen that way.
Sorry that I can't offer more than "just let the first boot take all the time it wants".
It's all good. I understand.
So, Truth be told I think the first time with the "stable" image I let it go for 3 rotations before I said jumped ship. As I type now, I tried going back to #128 and it's doing it again. Andy has done skated across it at least 20 times...21... I'll let it run for a bit since you say that while I research the recovering to stock in emmc in case I decide to chuck it up and go emmc. This is driving me crazy. I would guess that emmc maybe more stable than running it from an SDcard.
You have got to be s***ing me. So I staied persistant and used my 8GB Transcend card again. This time it installed clean (I was taking pictures so I can read the damn thing) and booted clean. WEIRD!!!
I'm going to see if I can get my Scandisk to do the same.
I have seen mention that using the latest winimage is not a good idea, something about it not working right.
Version 8.1 is the usual recommendation.
I have been using the dualboot image racks11479 put together, and i've burned it with winimage a handful of times without issue, but always used winimage 8.1
Not sure if that's your issue, as i've never forayed into the realm of recent nightlies, but it could be a contributing factor.
Win32Disk Imager works perfect for me, even on win7 x64 and winimage would write, but the disk wouldn't boot.
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.