my android build wont go past the htc screen i have re formatted the sd card would i have to flash another win mo rom
i hate when people act like they dont want to help lol
It's not that noone wants to help. We see this question posted at least a dozen times a day and it's just obvious you've not searched. The first boot of Android (any build) takes a long time, up to half an hour depending on various things. Leave it, if it doesn't work after that long, then post back.
i left it go for 3 hours lol...i even went back to stock and went thru the whole flash process
Ok then write down your entire process to get an android build to the point where it's just sitting there on the HTC screen.
ok i flashed the hspl then radio then winmo rom (energy) then i downloaded the biffmod rom extracted the rom placed it all in the android folder went to the file explorer clrcad then haret and it jus sits there... it was working 1 rom ago and that malfunctioned so much i had 2 leave it and now no android build works
I am having the same problem, I have let the device cook for over an hour and drain the hell out of my battery and still no go? It all started with SkinnyEVO v1.7, and yes, I did try changing the kernel to no avail, then the other day I was going to give the Bluetopia build a whirl, same result. I have no problems booting SkinnyEVO v1.5 or Sense rEVOlution v2.3. These two work amazingly well on my device.
Does anyone have any ideas as to why certain builds have this problem and other builds do not? I am suspecting it is a kernel issue but I may be wrong in my suspicions. Please enlighten me if so.
Thanks ..... HTR
yea im tryna figure out myself
I had the same problem when I got my HD2...formatted sdcard with HD2. After this I got no more problems.
Related
Well before everyone attacks me with "try searching on forums" responses, i have done that already. So here is my problem. no matter what build i use i will occassionally get sod and have to remove the battery to power it back on. the button lights turn on like its going to power on but no matter how long i wait it wont come out of sleep.
I have all display settings turned off in windows mobile before i boot into android, and i have auto like turned off in both windows and android. I have auto rotate turned off, and screen time out set to 30 min, which actually fixed my problem for a while. it always seems to happen that something happens that i have to power off my phone, and as soon as i do that is when it starts acting up and i get sod. it takes a few tries of taking out the battery for the phone to stop getting sod but after a few days it seems to come back.
I have even tried reformatting my sd card and still had the problem. i have the stock 16 gig sd card it came with. i havent flashed anything on the phone because i dont want to risk screwing up, so you guys are my last resort because i have tried everything.
Time to try different sd card.
In both windows and android, Auto light is off and you manually set the display backlight?
Have you tried the hyperdroid 1.7 version??
Vaizard84 said:
i havent flashed anything on the phone because i dont want to risk screwing up, so you guys are my last resort because i have tried everything.
Click to expand...
Click to collapse
Im pretty sure this is ur problem. Lots of things go wrong with stock.
its not as hard as it seems. just follow the intructions for ur specific hd2.
(look in the usa hd2 forums) if ur a usa hd2 user. IM SURE ITS A STICKY.
IF U WANT TRY THE OFFICIAL UPDATE FROM T-MOBILE!
i have heard good things about it
Unfortunately you have no choice but to flash the HSPL, a custom rom, and a radio. these are easy. ive flashed my phone countless times. I've also flashed other peoples HD2's countless times. Even when the phone was in the middle of flashing and the power went out at my house it did not brick the phone.
If you want to run android as a daily driver (like I do) my best advice is to flash the following.
HSPL (duh lol) http://forum.xda-developers.com/showpost.php?p=6891358&postcount=1893
Radio version 2.12.50 http://www.megaupload.com/?d=9GU2FF3X
WinMo rom http://forum.xda-developers.com/showthread.php?t=734238
(click on the first 'ChuckyDroidRom' picture under downloads in the first post.
You will use this utility to flash the 3.
http://forum.xda-developers.com/showthread.php?t=575524
when/if you download the 3 items, create a folder on your desktop. Name it something simple. Then inside that folder create 3 folders. name them HSPL, Radio, WinMo Rom. extract the downloaded items to their respective folders.
with the customRUU utility. extract the file to each of the folders.
Then,
Flash the HSPL first, the radio second, then the winmo rom.
when finished with those use the format sd card app in windows mobile to format your sd card (the program is set to format to android specs)
then copy whatever android build you want to the sd card.
Enjoy!
if you have any questions you may feel free to PM me. I will be home all day and would not mind helping you.
wow that is a lot easier than i thought well so far its working really nice, i havent got any sod yet, keeping my fingers crossed lol. thanks everyone for the help!
Vaizard84 said:
wow that is a lot easier than i thought well so far its working really nice, i havent got any sod yet, keeping my fingers crossed lol. thanks everyone for the help!
Click to expand...
Click to collapse
Yeah I promise you it was your radio/rom version. I had the EXACT same problem and nothing fixed it until I flashed and updated my radio. sometimes you just have to bit the bullet and dive deep!
cheers on your fixed phone, and knock on wood for no more SOD!
If you do experience SOD again. I recommend a faster SD card. I was having issues with any build I was using. Up to date flashed radio and lite WM rom, my only cure was faster SD card. I went from the stock 16GB C2, to an 8GB C6 (17.99 from Amazon), and I have not experienced SOD anymore. I have issues where sometimes the screen will not come back on right away, and I have to wait a few seconds, but it never sleeps on me anymore.
Hi, this is my first post on this forum so first of all I would like to appolagise for all the things I've either just done wrong, or am about too....
I am trying to install android on to my phone, I am on the stock rom but have succsesfully installed HSPL3 and radio version 2.11.50.20.
I have tried a few builds of Android but allways have one of 2 results.
Once I've run clrcad followed by harlet, it tells me I'm booting to linux. The screen then goes black, it runs about 8 lines of code, stops there and changes to a black screen with a green HTC. Where it remains indefinatly.
A friend with anouther HD2 has android working fine on his device, and altho he has a custom rom he tells me its not essential, as ive read up on the potential risks I would rather stick with the stock but will change if thats whats causing the problem.
I would really appreciate some suggestions, thanks in advance for your time and help.
Peter
forgot to add, the second result is the screen going blue indefinatly, which I presume from my extensive knowledge.........lol is a blue screen of death
upgrade your radio, im on 2.12.50, and the newest is 2.15.50
also, try a modded windows mobile rom, i use standard energy with no issues.
also, make sure you only have that one android build on your SD card. and that it's a new build, not an ancient one. (check http://android.hd2roms.com/)
you shouldnt have any more issues.
Thanks for the advice, unfortunatly before seeing your post I uprgraded too chuckeys rom, not energy, but get the exact same error... Leads me to beleive the problem is elsewhere. Will keep trying tho hope its worth it.
Jai meme problme mon rom est miri hd2 v_18.0 wwe ? Radio 2.15.50.14 ?
Same problem here, tried to change my wm rom and didn't work. I'm looking tonight if I can find a solution...
A little disclaimer
I will not be for any damage that may be caused to your device, HSPL remove warranty so be carefull. Don't forget to have more than 50% of battery remaining before the process !
So, maybe here is the solution:
I've try again with differents roms, changing my wm rom etc. and nothing works.
But, at the end I've change my radio rom to Leo_RADIO_2.12.50.02_2 found here http://forum.xda-developers.com/showthread.php?t=611787
Then installed Chucky GTX Lite rom found here http://forum.xda-developers.com/showthread.php?t=618787
And to finish I've installed the bootloader and download MDJFroYoRevolution 1.4 with android 2.2
I've use the 512 Data img too (just unzip your MDJFroYoRevolution, take the 512 or 1Go file and put this file on your Android root.) isn't necessary but takes less time to work first time.
After that still not working so I managed to try to remove all files from my sd card (2Go only) and I put on ONLY MDJFroYoRevolution 1.4+512Mo Data img !
Then after 10mn~ it works !
I think the bug is only because sd card haven't enough space to create all files so the HTC logo stuck and no error message appear.
Don't forget to install the bootloader on your memory internal storage! and not the on the sd card!
Good luck everyone and I hope it will help.
ps: sorry for my english hope you understand anything
Having the same problem here. I've tried different versions of WM, different Android builds, updated the latest radio rom, all without success.
Strange thing is though that Android boots the first few times, but after resetting it more than about three times it gets stuck on the black screen with the HTC letters in the middle. The only way to get it running again is reformatting my SD card (8G). Only thing on it is the Mdeejay Froyo Sense v2.3 Clean...
Solution for the freeze screen after second boot
I put android not in the root directory but in a \Android directory on the SD CARD.
of course, I add set cmdline "rel_path=Android" in the Startup.txt file and now i can reboot my phone when i want.
Ghirt said:
Having the same problem here. I've tried different versions of WM, different Android builds, updated the latest radio rom, all without success.
Strange thing is though that Android boots the first few times, but after resetting it more than about three times it gets stuck on the black screen with the HTC letters in the middle. The only way to get it running again is reformatting my SD card (8G). Only thing on it is the Mdeejay Froyo Sense v2.3 Clean...
Click to expand...
Click to collapse
exactly the same issue here
ROM: Energy build 28244
Radio: 2.15.50.14
Android: MDJ FroYo Sense Clean v. 2.4
Having same issue.
Energy Rom
Just reformatted MS
Hspl 2.08
radio 2.15.50.4
htc desire android build
getting same green htc screen.
icemanscion said:
Energy Rom
Just reformatted MS
Hspl 2.08
radio 2.15.50.4
htc desire android build
getting same green htc screen.
Click to expand...
Click to collapse
Do you got this issue at the first boot or after few reboots as Ghirt and I have ?
peterbeer said:
Hi, this is my first post on this forum so first of all I would like to appolagise for all the things I've either just done wrong, or am about too....
I am trying to install android on to my phone, I am on the stock rom but have succsesfully installed HSPL3 and radio version 2.11.50.20.
I have tried a few builds of Android but allways have one of 2 results.
Once I've run clrcad followed by harlet, it tells me I'm booting to linux. The screen then goes black, it runs about 8 lines of code, stops there and changes to a black screen with a green HTC. Where it remains indefinatly.
A friend with anouther HD2 has android working fine on his device, and altho he has a custom rom he tells me its not essential, as ive read up on the potential risks I would rather stick with the stock but will change if thats whats causing the problem.
I would really appreciate some suggestions, thanks in advance for your time and hel
Peter
Click to expand...
Click to collapse
Always use the custom winmo Rom sugested by the Android Builder. Simple as. The myth of "Stock ROM will be sufficient" should end
Peter[/QUOTE]
Same problem!!
Ive updated my radio to: 2.15.50.14
tried 3 roms.
before installing radio - I had the Kernal problem.
and now I have the black screen with green htc.
has anyone found a solution?
is their something that im not doing?
thanks!
jigners said:
Always use the custom winmo Rom sugested by the Android Builder. Simple as. The myth of "Stock ROM will be sufficient" should end
Peter
Click to expand...
Click to collapse
[/QUOTE]
Not true. I've installed on a couple of peoples HD2's using the latest stock WWE rom with radio 2.15. It does work, and it works very well.
I'm not saying you shouldn't use custom roms, that is everyone's prerogative (as you can see from my sig I use VBN's rom and it's perfect for me).
Try to move a folder called Android from sd card to another folder or delete it and it should help. It worked in my case. Good luck!
has someone hear find an answer?
given up
I have tried many combos and radios and still stucked at green htc loading logo now i am just hoping for nand. strange thing its the volume down and end does not bring bootloader anymore.
I don't know if this has happened to anyone, as I haven't seen the problem I have anywhere else, but something strange started happening from yesterday(using Energy 2 ROM btw):
When I run Haret, That's it! It gets stuck when it attempts to load the kernel. I've messed around with the startup.txt and used a new data.img, with no results. And, everyone else in the threads of the ROMs I was trying said they worked perfectly... A little help would be appriciated!
yeah, I've been having the same problem too! Im also using the energy 2 rom and I've been trying different android builds. The only build that I've had work half way decent was the desire rom but once I power off the phone and try to get back into the desire rom it just gets stuck at the boot up screen. Im new at the whole flashing roms and modifying files thing so any advice at all would be very appreciated. Thanks.
peter768 said:
I don't know if this has happened to anyone, as I haven't seen the problem I have anywhere else, but something strange started happening from yesterday(using Energy 2 ROM btw):
When I run Haret, That's it! It gets stuck when it attempts to load the kernel. I've messed around with the startup.txt and used a new data.img, with no results. And, everyone else in the threads of the ROMs I was trying said they worked perfectly... A little help would be appriciated!
Click to expand...
Click to collapse
I ran into this: Check post #17
http://forum.xda-developers.com/showthread.php?p=9928830#post9928830
Hello folks, I appear to have gotten into bother during a rom flash. After successfully installing a MAGLDR nand rom via CWM, the first boot of said rom just gives me the frozen splash screen without animation and the boot does not complete. Happens the same with three different roms.
I suspected somewhere further back in the boot process was at fault so I reflashed a known working radio rom, but problem still persists.
Despite a LOT of reading I can't see much about freezes at this point in the boot process on MAGLDR roms.
Bits that work - HSPL rainbow boot screen happily comes up, Task 29 works, magldr reinstalls and works fine, CWM perfect. Installs roms from SD (freshly reformatted) and appears to be ready to go, until boot actually begins then... splash screen freeze.
I have redownloaded various versions of everything to ensure no issues with corrupt files. I have also used different SD cards and ensured freshly formatted FAT32.
If it helps anyone, I have previously used NDT CM7 12.1 for about a month with zero problems.
Any other less obvious stuff I'm missing?
I'm off to bed so will be approx 7 hours from post time when I start responding. In the meantime I've put MAGLDR 1.10 on the phone so at least it can charge!
Many thanks in advance for reading.
Replying to self with update:
Installed OzRom Winmo 6.5 via the tried and trusted CustomRUU method, and it appears to work perfectly. What is winmo doing that android nand roms don't? I assumed if there had been bad blocks on the nand the much larger windows mobile rom would have covered this, and thus failed on boot.
At least opens the door to using an SD build till I can troubleshoot. Odder and odder.
Forgive my ignorance, but if the CustomRUU flash method still works for me, are there any modern android roms that don't need MAGLDR or clk?
Again, many thanks.
drachers said:
Replying to self with update:
Installed OzRom Winmo 6.5 via the tried and trusted CustomRUU method, and it appears to work perfectly. What is winmo doing that android nand roms don't? I assumed if there had been bad blocks on the nand the much larger windows mobile rom would have covered this, and thus failed on boot.
At least opens the door to using an SD build till I can troubleshoot. Odder and odder.
Forgive my ignorance, but if the CustomRUU flash method still works for me, are there any modern android roms that don't need MAGLDR or clk?
Again, many thanks.
Click to expand...
Click to collapse
How long have you been leaving the ROM on the boot screen? A first install of an Android ROM can take anywhere up to and over 15 mins for first boot. I also remember one when installing a hyperdroid ROM I had to restart the phone once to get passed boot splash.
I'd recommend flashing a popular ROM, leaving it for 20 mins, restarting and leaving another 20 mins. What do you have to lose? Just remember magldr doesn't have charge while off capabilities!
Also check your partition sizes and layout (you have to edit flash.cfg for magldr builds, partition sizes depend on the rom you pick but will be specified in the ROM thread).
Thanks for the reply. Each time I left the rom on the boot screen for a good half hour, and in one case an hour. I have installed NDT 12.1 and the newer v16 successfully before, so I know what sort of timescales are involved. I also had a go at an earlier Typhoon build. Naturally I used only the recovery sizes specified in each rom's own thread, using versions of MAG/CWM specified there, and Task 29 beforehand.
I have an update to all this, however. Previously I said Winmo installed, but now it is bugging out to all hell. This might fit my "bad blocks in nand" hypothesis, perhaps the files covering the bad area are less critical than the ones in each android build, and Winmo just crosses its fingers and tries to boot anyway!
In any case, if I can get an SD android build running I'll cut my losses and stick with whatever works.
Cheers again, hopefully this random screed of info will help people. Seems to be if all else fails, try winmo.
Hey guys for the last couple months ive been using android 2.3 gingerbread on my tmobile Hd2 with no issue. Except one day, yeasterday it ran out of battery or something, and now for some reason the phone boots, goes past the first couple of screens until it goes to the red,green,yellow,blue lines that intersect and make an X. It just stays there and doesnt finish booting into the OS. I dont know if there any way to fix this, a problem with power, or that i have to install the stock windows 6.5 rom again. Either way, any help or linked tutorials would be greatly appreciated.
Oh and the kind of rom i used is NAND, its installed into the phone and not the sd card.
redsilentscope said:
Hey guys for the last couple months ive been using android 2.3 gingerbread on my tmobile Hd2 with no issue. Except one day, yeasterday it ran out of battery or something, and now for some reason the phone boots, goes past the first couple of screens until it goes to the red,green,yellow,blue lines that intersect and make an X. It just stays there and doesnt finish booting into the OS. I dont know if there any way to fix this, a problem with power, or that i have to install the stock windows 6.5 rom again. Either way, any help or linked tutorials would be greatly appreciated.
Click to expand...
Click to collapse
If you leave the phone on the charger, does it enter a bootloop or does it boot up to a certain point then freeze? If it's the latter I'm not really sure as to what I can do to help (there are solutions, I just don't really know any of them) but if it's the first then your battery is probably out of charge to the point where it can't boot far enough into the OS to be able to start charging. You'll have to cut open a USB cable and charge it manually, unfortunately.