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 well i was using android on my phone with out flashing any thing r doing any thing to my phone. and ways i now used HSPL and flashed my phone and now when i try and run android it loads like four lines and then stops.. any ideas?
It would probably be a good idea to copy your android build (and anything else) off of your SD card, format it in your computer via a card reader to FAT32, and try just putting your android build back on (without a data.img) to see if it successfully boots. I have had this happen with a friends HD2 and this was the only way I found to solve it.
If this stage works, you can put your original data.img back on and it should boot back exactly as you had it before.
I hope someone else can give you a less laborious answer but that was the only one I found that worked.
Reno_79 said:
It would probably be a good idea to copy your android build (and anything else) off of your SD card, format it in your computer via a card reader to FAT32, and try just putting your android build back on (without a data.img) to see if it successfully boots. I have had this happen with a friends HD2 and this was the only way I found to solve it.
If this stage works, you can put your original data.img back on and it should boot back exactly as you had it before.
I hope someone else can give you a less laborious answer but that was the only one I found that worked.
Click to expand...
Click to collapse
thanks i give it a shot
I have this problem every time i turn of my phone or restart it, no matter what Android version is on it.
All Android versions boot without problem for the first time, It took me about 10minutes or so, I set up everything, spend hours on it and than if i want to switch back to WM, I can forget about it. Just can't boot Android for the second time, it gets to the black-screen-green-htc and go on like this forever.
I though it may be in SD card (I had 2Gb), so i bough new one few days ago (4Gb). I installed MDJ Froyo and it worked fine until I decided to restart phone in order to switch back to WM. Again, Android can't boot...
To get it working, I have to delete all android files, copy new one and start again for the first time...
This is really frustrating, and I can't keep my phone running forever without shutting down or restarting so does anyone have any solution for this problem?
Thank you,
Mario
EIDT: I tried every possible solution in this thread http://forum.xda-developers.com/showthread.php?t=854182 and nothing works
It happens sometimes, when it happens to me I just take out the battery and reboot and it starts normaly.
Secondly is you android folder on the root of you sd?
SD/ANDOID
Aren't you suppose to copy files from Android folder to SDcard root folder, so that HARET AND CLRCAD are on root folder, not like SD/Android/Haret.exe?
no the android folder has to be on the root of the SD
so it looks like SD\ANDROID (and in android haret...)
I have the same problem. I have tried different droid versions, and they work the first time, but if I restart the phone, I have to delete the droid rom and reinstall it again because it stays on the HTC screen for hours. I have it on the root of sd card.
What has worked for me a few times is instead of using the bootloader I go to explorer and manually click on haret......usually works.. and also check your startup.txt to make sure it points to the root folder Android while using the bootloader.
Increase the SD card size to 8 GB
Try increasing your SD card size to 8 GB, I am using 8 GB and it works well.
I've followed the dual boot tut and wp7 is working fine, I marked the wp7 partition as primary. I used services to point to android build dir, Im using Copes build which i read works with magldr without any modification. My issue is that when I choose to boot ad sd from magldr i get to GO GO GO! and it just sits there... I let it go for 30 mins.
I thought maybe i needed to add a data.img to it so i dl'd a 1gb data.img and placed it in the android root... still no luck.
inside copes build was a folder that said magldr with instructions to swap out the startup and the rootfs.img.... no go still stuck at GO GO GO!
WTH am i doing wrong? Any help would be greatly appreciated... wp7 boots fine off the nand, just cant get into droid....
EDIT:recopied copes droid/cynogen build back to sd left the 1gb data.img which was fresh on there and got past the GO GO GO! but now im stuck at the HTC logo for 30 mins and no signs of life...
oh and i reverted from 2.15 to 2.12 radio because of reported longer battery life, as far as ive read this is compatible with copes build. Any ideas why im stuck at the htc splash?
Bump!
I got passed the htc logo and I get passed cm7 splash but the phone freezes at the setup wizard... sometimes I get passed being asked to complete action using com.android.provision or Setup wizard, but it will quickly freeze. touchscreen is non responsive and i have to pull the battery.
Ive reformatted several times and recopied the build no luck do you think if i change the data.img from 1gb to a lower size it will not freeze? has anyone had this issue before?
I tried to do the same thing you did and I gave up. I was using Darkstone's super ram build and WP7 works perfectly on NAND but it will no boot android. Sorry I can be no help. Just to let you know that Super ram froyo is having the same issues if you chose to do another build.
i finally got the gingerbread/cm7 from cope working! I had to swap out the startup txt and the root file from the the magldr folder. the first time i tried this it didnt work because I believe there was a corrupted file from copying the droid build to the sd using magldr's 4. Usb mass storage option.
I Got gingerbread/cm7 working and installed but I cannot use the marketlace to dl apps I get a message saying your application will be downloaded... or something of that nature. When I go to my apps and try to manually install them they kick to the top and never start. They quickly drop back down to the list of apps with an uninstalled status.
I have the apn setup and im connected to wifi. Im once again at a loss....
there is a thread on here that will tell you how to mount your img and edit a string to allow darkstone to work! search in android developement for booting android with magldr...
so i tried almost all the builds for magldr and a couple that i found zimage or intrd files for and nothing works.
Well the superRam froyo worked once after 4 tries and never worked again.
I even task 29'd my phone and installed a fresh magldr 1.3.
they are all booting to the htc screen or equivalent and staying there.
for some reason some of them wont even drag to my sd card. I waited over an hour on one of them and it was only half way with no progression.
the last one i tried was skinnyevo and it took over an hour to load onto my sdcard. then when it was done, niether my phone or my computer would recognize my card. only thing that would read it is easeus partition manager through mass storage in magldr.
Are some of the files corrupt or what. does anyone else have problems like these.
I want to have wp7 and an android build able to boot. wp7 for show mostly.
and i cant let my phone win. it really erks me.
I even loaded an android nand recovery through cw and tried to drag my files over using that.
I also tried to drag them to the fat32 partitioned half of my sdcard with wp7 on it, and nothing.
You shouldn't use magldr mass storage to transfer files... it's known to corrupt the files. Take card out and use card reader.
Also, most sd android builds need a modified init.rc file to work with magldr. There's a thread about it in the android sd section. I have most builds working good, so if there's a specific build you want, pm me and I'll see if I have it work and send you my copy.
I don't think you can use clockwork recovery when you have wp7 on NAND... clockwork is only for nand android. There are threads in the sd android section about dual-booting and getting sd builds to work with magldr. There are also a few recent builds that will work as is with magldr.
I was actually using either android or CW to transfer files. Ive never had any issues with them. my sdcard reader is broken.
I was able to erase and reformat my card so its working again.
I might give it a try again. Hopefully my head doesnt explode.
Are there any Builds that are known to have a high success rate for magldr.
Oh and by init.rc did you meen initrd.gz thats the only custom file ive downloaded and seen in the android folders. Maybe i have the wrong ones.
Maybe ill try with my 4g card. its the same brand though.
darkkeycliq said:
I was actually using either android or CW to transfer files. Ive never had any issues with them. my sdcard reader is broken.
Click to expand...
Click to collapse
The same has happened to me, various NAND build corrupted my data on card and once I tried to use that card in a reader the reader then broke and didnt work on any cards or any systems. Thsi has happened to 3 now.
darkkeycliq said:
I was actually using either android or CW to transfer files. Ive never had any issues with them. my sdcard reader is broken.
I was able to erase and reformat my card so its working again.
I might give it a try again. Hopefully my head doesnt explode.
Are there any Builds that are known to have a high success rate for magldr.
Oh and by init.rc did you meen initrd.gz thats the only custom file ive downloaded and seen in the android folders. Maybe i have the wrong ones.
Maybe ill try with my 4g card. its the same brand though.
Click to expand...
Click to collapse
I have most sd builds working great with magldr... pm me with what builds you'd like if you want to try one of my edited builds. I've edited and gotten most of the sd builds from dec til now to work fine.