My vogue locks up after I open Haret and click run. It gets stuck as soon as the progress bar under Booting linux fills up. I have a sandisk 16gb card with 1.05 gb free. I'm currently running NFSFANs latest 6.5 rom. Any tips?
am i the only one who experienced this problem?
check your zimage, it should be named "zimage" and nothing more. You could also try to redownload the zimage as it may be corrupted
na it still just freezes. do i have to let it sit a while?
Do you happen to have a data.img already on the SD? I ran into this problem last night for the first time, and it seemed I had kept my data.img from an old build (I was changing builds from Ion to Donut) and as soon as I deleted the old data.img it fired up successfully.
i deleted it but i get the same result. would u mind describing how u setup android on ur sd.card?
I would think the problem is with the zimage, as it doesn't even boot the kernel. Try downloading haret again ...
Same problem here, anyone know a solution , thanks.
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.
it seems that every time i install a new andro build i get more and more issues.
im running chunkyrom with 2.12.50 radio
my first rom was froyostone 1 it ran perfect no issues at all
i installed the HDfroyo and started having the typical andro issues
then i tried mattc leo and it was overall great build but i had even more issues and not as stable as froyostone1
2 days ago installed froyostone 2 and having a very unpleasant experience with it crashing restarting lagging thewifi and mms and lock screen lagging etc.
note that first froyostone was installed on a card that i didnt even touch.
all the files from blackberry phone were still on it i only ran an error check in windows.
for mattc i completely cleared out the sd card formatted and ran an error check.
and started having issues.
is formatting under PC windows and formatting from winmo makes any difference?
im puzzled why im having more and more issues,
it almost seems like the winmo keeps getting more and more corrupted by the android builds or something like that..
HaRET closes WinMo and modules completely then starts Android... so dont think so..
Anyway a dev can give u a good insight and help you better.
Good Luck
fuzzysig said:
it seems that every time i install a new andro build i get more and more issues.
im running chunkyrom with 2.12.50 radio
my first rom was froyostone 1 it ran perfect no issues at all
i installed the HDfroyo and started having the typical andro issues
then i tried mattc leo and it was overall great build but i had even more issues and not as stable as froyostone1
2 days ago installed froyostone 2 and having a very unpleasant experience with it crashing restarting lagging thewifi and mms and lock screen lagging etc.
note that first froyostone was installed on a card that i didnt even touch.
all the files from blackberry phone were still on it i only ran an error check in windows.
for mattc i completely cleared out the sd card formatted and ran an error check.
and started having issues.
is formatting under PC windows and formatting from winmo makes any difference?
im puzzled why im having more and more issues,
it almost seems like the winmo keeps getting more and more corrupted by the android builds or something like that..
Click to expand...
Click to collapse
I think that you will find that the only references to past builds will be on the actual SD card used, which is why a complete format of that card is recommended. On the root of the card will be folders created by your Android installation, some begin with a full-stop, e.g.: .Mail, .footprints, but there are others that do not follow that convention. If you do not want to do a complete format of the SD card, you may want to do a screen shot of the card prior to install, so that you can compare before and after, then before a new subsequent Android installation, delete the new files and folders created.
Some people are experiencing the problems you describe with this PPP version, but the Dev was aware of this and has posted a fix,so it may be better for you to try the RMNET rootfs. Hope this helps.
_____________________
O2 HD2
Artemis Rom 31.5 WWE
Radio 2.10.50.19.2
FroyoStone Sense - V2(PPP)
HD2 T9193 Australia
512Kb Flash Memory
SPL-2.08.HSPL CotullaHSPL
ROM Energy Leo 29007 Sense 2.5 Jan 24
Radio 2.15.50.14
Over last few days, have download several SD builds of Android.
I Copy the android folder to root of SD card
I start the phone in Windows Mobile
I run CLRCAD
I run HARET
I get the grey window about starting/booting (cant remember exact, head spinning)
then get black screen with small writing
then get HTC splash screen and thats it.
each build I have tried, have left at boot screen from 60 to 90 minutes.
Now, 6 months ago with earlier version of Energy ROM, and different radio, I could load earlier version of SD Android.
Today I had a friend around, with an older radio and the same earlier version of energy rom that I used to have, and still no go on his.
What is happening (or not).
Do I need to have an EXT2/2/4 partition on my SD Card?
Something more simple??
Ideally, I wanted to try a Desire HD Sense ROM.
Have tried
CopesHD2GingCyan7Release1
Core_Droid_HD_V0.4_Release_Version
mattcleofroyo1.8
MDJ_FroYo_HD_v._4.6_MDJ_S78.0
NexusHD2-FRG83D_V1.8_(Froyo 2.2.1)
SuperRAM_FroYo_V1.5
Moby58 said:
HD2 T9193 Australia
512Kb Flash Memory
SPL-2.08.HSPL CotullaHSPL
ROM Energy Leo 29007 Sense 2.5 Jan 24
Radio 2.15.50.14
Over last few days, have download several SD builds of Android.
I Copy the android folder to root of SD card
I start the phone in Windows Mobile
I run CLRCAD
I run HARET
I get the grey window about starting/booting (cant remember exact, head spinning)
then get black screen with small writing
then get HTC splash screen and thats it.
each build I have tried, have left at boot screen from 60 to 90 minutes.
Now, 6 months ago with earlier version of Energy ROM, and different radio, I could load earlier version of SD Android.
Today I had a friend around, with an older radio and the same earlier version of energy rom that I used to have, and still no go on his.
What is happening (or not).
Do I need to have an EXT2/2/4 partition on my SD Card?
Something more simple??
Ideally, I wanted to try a Desire HD Sense ROM.
Have tried
CopesHD2GingCyan7Release1
Core_Droid_HD_V0.4_Release_Version
mattcleofroyo1.8
MDJ_FroYo_HD_v._4.6_MDJ_S78.0
NexusHD2-FRG83D_V1.8_(Froyo 2.2.1)
SuperRAM_FroYo_V1.5
Click to expand...
Click to collapse
Have you tried putting a blank data.img file on the sd card before the boot?
If not try that, they are usually available from the first post in the builds thread.
A few I tried wouldn't boot the first time unless I put that file in there.
I'm guessing it won't help, because some (if not all) of those builds can create a blank one for you, but it won't hurt to try.
This is the one from MDJ's 4.6 build you have tried. The link is from his thread. Extract the file using 7zip and stick it in the android folder.
http://www.multiupload.com/BJ2FXF9IRM
There's no need for partitioning or any kind of fancy stuff for running a simple WinMo6.5/Android dualboot. I suppose formatting your SD card (do it in WinMo, seems to be more effective) should solve your problems.
@MattOG: The data.img helps shortening the first boot time, I've never heard it actually fixes problems?
MattOG said:
Have you tried putting a blank data.img file on the sd card before the boot?
If not try that, they are usually available from the first post in the builds thread.
A few I tried wouldn't boot the first time unless I put that file in there.
I'm guessing it won't help, because some (if not all) of those builds can create a blank one for you, but it won't hurt to try.
This is the one from MDJ's 4.6 build you have tried. The link is from his thread. Extract the file using 7zip and stick it in the android folder.
http://www.multiupload.com/BJ2FXF9IRM
Click to expand...
Click to collapse
Thanks, tried the blank data.img, both the 512Mb and 1Gig.... no go
MattOG said:
Have you tried putting a blank data.img file on the sd card before the boot?
If not try that, they are usually available from the first post in the builds thread.
A few I tried wouldn't boot the first time unless I put that file in there.
I'm guessing it won't help, because some (if not all) of those builds can create a blank one for you, but it won't hurt to try.
This is the one from MDJ's 4.6 build you have tried. The link is from his thread. Extract the file using 7zip and stick it in the android folder.
http://www.multiupload.com/BJ2FXF9IRM
Click to expand...
Click to collapse
Why
do
you
write
like
this?
You do have enough free space on your card for it to create the data.img right??
conantroutman said:
You do have enough free space on your card for it to create the data.img right??
Click to expand...
Click to collapse
Hope so, 8gig card with just the android folder
ok thats not it then........
The only thing I can think to suggest is to try a different WM ROM... see if you can find the energy rom you used before from the energy archives....
It's my thought process. Did I offend your eyes?
Sent from my HD2 NANDroid using XDA App
conantroutman said:
ok thats not it then........
The only thing I can think to suggest is to try a different WM ROM... see if you can find the energy rom you used before from the energy archives....
Click to expand...
Click to collapse
Tried that with the mate's HD2, as it has the same, older energy rom that I used before
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...
I'm new to this, is it normal to take hours for a rom to first inatall?
How long is normal?
JMG01 said:
I'm new to this, is it normal to take hours for a rom to first inatall?
How long is normal?
Click to expand...
Click to collapse
for me:
normal time to flash HSPL is about 1 minute
normal time to flash a radio is about 20 seconds
normal time to flash a full custom ROM is about 1 minute
after the flash the first boot/setup can take a few minutes.
the longest you should ever have to wait is first boot on an Android SD build with no existing data.img, which can take like 20 minutes, other than that you should not be waiting "hours" for anything.
What should I see...?
Thanks for the reply, I still struggle.
I'm trying to install AmeriCanAndroid. It's my first time at this.
Win 6.5 is clean installed. SD card is formatted FAT32.
Android folder in SD card.
Run clrcad.exe and haret.exe
clrcad.exe does not appear to do anything when run, I assume this is correct.
haret.exe loads, then black screen with approx 9 lines of tiny text.
What next??? Do I just wait??? It just stays like that!
JMG01 said:
Thanks for the reply, I still struggle.
I'm trying to install AmeriCanAndroid. It's my first time at this.
Win 6.5 is clean installed. SD card is formatted FAT32.
Android folder in SD card.
Run clrcad.exe and haret.exe
clrcad.exe does not appear to do anything when run, I assume this is correct.
haret.exe loads, then black screen with approx 9 lines of tiny text.
What next??? Do I just wait??? It just stays like that!
Click to expand...
Click to collapse
Yes you are doing it correctly. You just have to wait for the Android Os to boot after yo touch on haret. Also when you touch on clcad you will see nothing as this just enables the sound in Android. If it does not bring up the Android lock screen after the max of 15 to 20 minutes than pull the battery cover and press the reset button on the back of the HD2. I suggest you try download and try a diferent Android SD build as that one probably has some kind of issue.
Still trying...
Thanks for the reply.
Some roms mention editing the config.sys file and some mention downloading a data.img file. Are these steps needed for all roms?
So far I have not done anything with these, I have just followed the instructions for AmeriCanAndroid which does not mention these. I have tried several builds of AmeriCanAndroid which looks like the most popular rom, so I don't think the rom is wrong, I just feel I am missing something.
JMG01 said:
Thanks for the reply.
Some roms mention editing the config.sys file and some mention downloading a data.img file. Are these steps needed for all roms?
So far I have not done anything with these, I have just followed the instructions for AmeriCanAndroid which does not mention these. I have tried several builds of AmeriCanAndroid which looks like the most popular rom, so I don't think the rom is wrong, I just feel I am missing something.
Click to expand...
Click to collapse
Ok give me a detailed list of what you have done, or as best you can so I can review it and I will try to see if I can see what you are doing wrong if you are doing something wrong that is.
So far
Win 6.5 is clean installed from software choice. SD card is formatted in the phone by win 6.5.
Downloaded AmeriCanAndroid to PC.
Unzipped
coppied the Android folder to the SD card.
Run clrcad.exe
Run haret.exe
Stuck on black screen with approx 9 lines of tiny text.
Removed battery when bored of black screen (anything from 30 mins - 4 hours).
Can't find a reset button on the back of the HD2.
Tried several times, with the last 3 builds of AmeriCanAndroid.
I have NOT - done anything with any config.sys file or data.img file.
NB my windows 6.5 is in Norwegian.
JMG01 said:
Win 6.5 is clean installed from software choice. SD card is formatted in the phone by win 6.5.
Downloaded AmeriCanAndroid to PC.
Unzipped
coppied the Android folder to the SD card.
Run clrcad.exe
Run haret.exe
Stuck on black screen with approx 9 lines of tiny text.
Removed battery when bored of black screen (anything from 30 mins - 4 hours).
Can't find a reset button on the back of the HD2.
Tried several times, with the last 3 builds of AmeriCanAndroid.
I have NOT - done anything with any config.sys file or data.img file.
NB my windows 6.5 is in Norwegian.
Click to expand...
Click to collapse
Sorry for the lag between post got busy doing some stuff. Yoiu should not have to mess with the config.sys or data.img file as this is the first boot of Android. Do this look at your SD card and see if it has any files that the Android created on it when booting as it has to create several files on the first boot. If it is then look for the config.sys and data.img files and remove them and try to boot Android again. If it is no files on your SD card then make a backup of your SD card and reformat it again but use the Panisonic formatting tool as they say it works better.
lol sorry just saw you're using haret.
make sure you are using the correct rootfs.img, also maybe try another build.
also, which winmo6.5 ROM and which radio are you on, it makes a difference. You need an updated radio like 2.15.50 or so, really anything above 2.12.50 works well.
THANKS
It works!
My win 6.5 rom was old, so I updated to the last HTC one. Android then had no problems to install on the sdcard.
Many many thanks,