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.
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've got a HD2 just to try wp7. After some careful reading manages to install, and it was booting and used the basic features for couple of hours without any issues, until i wanted to try out maps,,,, The HD2 got stuck and went to a boot loop.
After checking so much for the one and a half day (I'm so tired and sleepy) i'm sick of this phone. I ve seen many posts regarding this issue, but no one seem to post a clear answer that rectifies the issue. Yes i've tried task 29 and gone back to wm 6.5 as well. Anything else i'm missing here.
If i keep the battery off for about 10 mins or so then it boots up properly, but not all the time. I cannot use any most of the features, only texting and calling. If anything else is launched (IE, People, A/C config...) goes back to the boot loop. WTF
Pls guys help me. well i'm a complete nOOb for this and sorry for the long post.
I am by no means an expert here, but have you tried a different SD card? When I first flashed my HD2, when WP7 was first available for it, my SD card was incompatible and it was constantly rebooting. Some SD cards are incompatible with WP7, even the ones that originally shipped with the HD2.
I know how you feel... that's exactly what happened to me. OMCA1A's right, Try a new SD Card and you should be good to go.
Which method you use ? Zune or 1 shot install
Did you have wp7 on hd2 before trying to install This rom? Was the sd card working?
Did you unlock/ reformat sd card or install straight over?
as already mentioned it can be the SD card and is most likely the SD card in your case, how you install it, cabs or zune or whatever doesnt make the slightest difference, anyone using any card that is not certified to work with WP7 stands the risk of running in to the restart issue.
it might not happen today, it might not be next month or even year, but potentially the restart issue can rear its head when xx% of storage space free is hit
i say xx because it could be anything from 1 -100.
Peronally i find that dumping a few hundred meg of music on gets past these dodgy areas, like just now, if i remove 12MB of data from my device it will start restarting, i can replicate this, if i do a reflash i have to install at least 200MB of music before doing anything, 600MB on top of that i get more restarts so dumped another 200MB of music, installed navigon, restart issues, install 50MB of music all fine again, that its a pain in the arse but its workable, it just means i have a lot of music i will never listen too on my device
Sorry I seriously gave up on my HD2 and was using my sisters old LG phone (Sucked big time ) Yes OMAC1A I have tried 4 different SD cards, so I doubt it’s the SD card.
Moschino02 What do u mean by Zune or one shot install ? I installed the normal way here are the steps I did.
Did task29
Installed latest radio
Installed MAGLDR
Then the wp7 ROM bu running a DWI.exe
Well after I got tired I did install it over and over and over. Yes the cards were working fine on my x10i
dazza9075 The SD I used was empty.
Also guys like I mentioned I only cannot use any of the smart phone features, if I get in to maps or IE or any other task which consumes a lot of CPU, it happens.
I will try one more SD card cos u guys insist and if it doesn’t I’m seriously gonna sell it off for scrap if u want let me know it’s gonna be dirt cheap I can’t tolerate this anymore.
Also one more thing guys, i've tried android as well, a 2.2 desire ROM and a MIUI ROM. Some times it gets stuck on start up it self or on the initial setup. That to me doesn't sound like a SD card issue.
Also it overheats
You tried with Sandisk class 4\6 SD cards, right? Cuz those are the only ones that have a decent chance of working.
Overheating of the HD2 is a common problem, saw many of these phones being sold on ebay with that problem...
I have the same problem... Still trying to fix it... But I know the problem comes when the phone tries to access the SD card (sandisk).
zeus09 said:
Moschino02 What do u mean by Zune or one shot install ? I installed the normal way here are the steps I did.
Did task29
Installed latest radio
Installed MAGLDR
Then the wp7 ROM bu running a DWI.exe
Click to expand...
Click to collapse
So after you install wp7 rom by running dwi.exe ( you mean v2native rom, right?)
What did you do? Did zune find updates to mango? Or did you install mango by sending cabs? What version are you on?
Moschino02 - Yes it says,
Name: HTC HD7 T9292
OS Version: 7.0.7392.0
Also i have tried other ROM as well, did not have any luck. Even at this very moment it goes through a boot loop. Just tried accessing HTC hub and it went off.
After installing sometimes it reboots or i have to manually do it by removing the battery or a by a soft reset. Yes zune finds updates but i cant update. When the rebooting point comes it never reboots to the OS just goes to a boot loop. *@#^&%$
I have used the following,
Verbatim 2GB micro SD
Unbranded 8 GB Micro SDHC
Kingmax 2GB Micro SD
Sandisk 4GB Micro SD
and none of them worked.
jinge - I dont think so. Initially i thought the same. And i removed my SD card to see but the problems kept continuing.
IF its a SD card incompatibility issue the HD2 should work fine with android. It boots only up to the initial start up screen doesn't go beyond that. MIUI is the closest i got but that too gave problems.
I'm seriously sick of the hd2 guys and i hate it i wish i could show it to you'll.
This has to be a hardware fault. IS IT ????????
Ok, I have run this install method 2x today http://forum.xda-developers.com/showthread.php?t=1000957&highlight=verygreen+sd+bootable *VeryGreen*
Now, I am not new to rooting but haven't been keeping up with my nook as I passed it on. Went from CM7 stable to MIUI couldnt' stand the market issues and didn't want ot deal with removing the up dater..blah blah blah ok enough of that
I have followed the instructions and was have booted CM fine but each time I look at my SD card I only have the one partition. Should I be partitioning it myself before doing the steps metitioned or should the install make the partions for me then I just write the FAT or FAT32 (<---top of my head) myself post install.
I wanted a dual boot but figured I would wait for CM9 to come out and wanted to test the SD install. Also, the system seems laggy and I would attribute that to the card i'm using but was also wondering if maybe it was from the partitions? I believe the card is only showing 120 mb used and 14 unused.
Thanks, for any help I have been working on this for 3 days different scenerios and used searches but I get so many dated threads.
~D
If you are using windows you will only see the first partition.
Sent from space
That would be why, hadn't thought about that but was going to into partitioning i myself this evening in linux either would have seen this or been worse for the wear. Thanks, seems it's still not running as smooth and I am thinking it' the card, I'll just got with old faithful for now and work on it more after NYE have a trip coming up and would rather have it in state I know works.
Cheers
See attached photo.
WM 6 is working great. I have the SD card correctly formatted to FAT32 and EXT4, but after launching HARET from 4EXTRecovery folder, it launches but there's few errors and it won't let me install Android because of those errors. Can you help me please?
I've spent many hours on forums and can't find any solution. Thank you
What have you all tried so far on trying to get it to work?
paulhauth25 said:
What have you all tried so far on trying to get it to work?
Click to expand...
Click to collapse
I tried different SD cards...And I tried different versions of the Mini formatting toolfor windows. In the End I gave up. But today I decided to try WP7 installed on NAND. But didn't like it. It wouldn't even connect to my wifi. Just kept asking for a password.
So after that I decided to try Android again, but install it to NAND. I used HTC HD Tool and installed "NexusHD2-KitKat-CM11.0_V4.7.zip". Installation went without problems. After the install it rebooted and now it's stuck on black screen with green HTC logo. It's been about 20 minuted already.... Will wait a bit more and see. If it doesn't work, I would like to try another Android rom installed to NAND. Is there any newer than "NexusHD2-KitKat-CM11.0_V4.7.zip", with everything working? Or should I jsut go back to WM 6.5? Thank you
Whats the advantage of SD Card over NAND? Is it just about useable space?
Not here to help but nice to see yours actually working, mine is just a fancy paperweight rn