ive tried many lovely roms on my dream, but all but one have horrific battery life, the one exception is gingeryoshi 1.1 with the new farmatito kernel, so i figured i could just install it to my preferred rom and id be away, however it seems not so simple as all that
first i tried installing it to the cos-ds image i was running at the time, it simply killed that stone dead, wouldnt boot past the boot anim. so i decided to test it on my current fave rom, beatmod 2.2, i did and it booted and seemed to run fast and reasonably problem free until it came to installing an apk i had on my sd card, where i found that it wouldnt read the card at all, it said no card inserted and on pulling and reinserting it displays damaged SD card and often causes many force closes on other running processes, so what is it that i need to change to get it working, it seems close enough that itll just need some tweaks so if someone could point me in the right direction id be grateful, just a "read this, this and this" and some links is plenty (the info may well be on here already but digging it out can be a nightmare and i havent got that far on my own yet, its a BIG forum)
so what exactly are you trying to figure out? how to fix your sd card or how to get the kernel working? your sd card may have actually just died because believe it or not those things dont last as long as you think.. thore more times you copy things on and off them the quicker they die.. but as far as the kernel problem im not sure exactly how it all works i usually get the recommended kernel for rom... usually on the post with the rom link
no the sd card is fine, its any sd card when used in beatmod with that kernel, so getting the kernel working, what i want is a rom thats a little faster than the somewhat sluggish gingeryoshi but is compatible with the farmatito kernel which solves my short battery woes
ive actually even tried cos-ds and used their recommended farmatito kernel but even then it still leaves me stuck at the g1 boot screen. infact as yet beatmod is the only rom i have got to boot at all with a different kernel than the one that comes with the rom. im not sure if its something that im doing or possibly that the g1 is on its way out, its just refused to use the backup i made before testing the greenromproject rom (which also didnt boot, again stuck at the g1 screen) as the md5 check failed and what with it being picky about which backups it will and which it wont boot anyway im beginning to suspect there may be more to it than a software complaint
and now that ive finished typing i look over at my phone to still see that big g1 glaring at me, none of my current backups now work ah well try a fresh install i guess
Related
I recently got a hd2 off of craigs list for a steal, and the ONLY reason why I got it is to run android on it. But I am having problems getting a android rom to boot, and getting one stable. I have double checked all of my intructions to the T, and I am coming down to two reasons why I cant get mine to work properly.
1. sd card problems, Do I really need a class 6 card? Right now it hangs where the linux boot says, creating a new data store.. it just counts down from 99 very slowly.....
2. I did buy the phone used. so one of my battery prongs on the phone is off set a tad. loose a little. will that affect my android loading?
I have tried to search long and hard before I made this post, but honestly THERE IS ALOT OF INFORMATION TO READ THRU and i justget confused.
if anyone can shed some light on these two questions, i will appreciate it.
You don't really need a class 6. I'm using a class 4 just fine and there are many people who've said the stock 16gb card works. I would suggest pulling all files you want saved off the card and do a fresh reformat to fat32. Then move your files back over and download the version of Android you want to run.
Are you using a stock or custom Rom?
Have your tried different radios?
Have you tried a different build of Android?
All of these variables come into play. Can you provide some more info about your setup? Thanks and good luck. I hope the reformat solves your problems.
Sent from my HTC HD2 via XDA App
I am using the latest energy froyostone rom with his custom wm rom for android. I have only flashed one radio, the one that went with a chucky rom gtx.
the wm rom boots up no problem, i always reformat when I try to flash a new rom, I always wipe the sd card before I try.
Now I need a working phone, so I have my sim in my vibrant when I flash, does that make a problem?
I really cant think of anything else that I have tried. I have gotten a couple of rom's to boot up with android, but when I reboot and install my sim card, the phone will freeze upon wm boot up, and sometimes load android again but goesinto a boot loop within 5 minutes. I am really looking for a good wm /android combo, if I get it running stable the first time, I probably wont flash again until some major breakthru happens.
Edit# switched sd cards. got it to load up one time, then tried to reboot and put my sim card in, phone goes into a boot loop before I can finish set up.
Now it is taking me forever just to boot up to WM
I am experienceing freezes on start up, freezes once WM boots up.
thanks for your advice
I'm assuming you have hacked with hspl.
Check the pins on the battery and try not to pull the battery out as those pins are really fragile. If one is bent it and shorts it puts the phone in a continuous boot loop, not a big deal just straighten the pin out and you should be fine.
I'm using the latest mattcfroyo sense rom ver 16 and had a similar issue where the linux boot would just freeze past a certain point. There is a modified zimage that was posted that completely solved that problem, again an easy fix, just swap out the old for the new. But I have to admit spending about a half day messing with this to get it to work, at one point I almost thought about moving back to wimo - after that nightmare thought I dug in and found the fix.
ok, another update, and thanks for the advice, I took my simcard out, and it booted up android fine, its been up for 10 minutes , no problem.
Are there any sim card issues I need to know about? Should I head to tmobile and get a new one>?
I think I am really close, and I thank you two for tryng to help.
It couldn't hurt to get a new sim. There could be a corruption on your card causing the boot loop.
*Edit: head to any TMO corporate store and they will give you a new sim for free.
Send from my HTC HD2 via XDA app
Devin5277 said:
I recently got a hd2 off of craigs list for a steal, and the ONLY reason why I got it is to run android on it. But I am having problems getting a android rom to boot, and getting one stable. I have double checked all of my intructions to the T, and I am coming down to two reasons why I cant get mine to work properly.
1. sd card problems, Do I really need a class 6 card? Right now it hangs where the linux boot says, creating a new data store.. it just counts down from 99 very slowly.....
2. I did buy the phone used. so one of my battery prongs on the phone is off set a tad. loose a little. will that affect my android loading?
I have tried to search long and hard before I made this post, but honestly THERE IS ALOT OF INFORMATION TO READ THRU and i justget confused.
if anyone can shed some light on these two questions, i will appreciate it.
Click to expand...
Click to collapse
try this simplified step by step guide:
Devin5277 said:
I recently got a hd2 off of craigs list for a steal, and the ONLY reason why I got it is to run android on it. But I am having problems getting a android rom to boot, and getting one stable. I have double checked all of my intructions to the T, and I am coming down to two reasons why I cant get mine to work properly.
1. sd card problems, Do I really need a class 6 card? Right now it hangs where the linux boot says, creating a new data store.. it just counts down from 99 very slowly.....
2. I did buy the phone used. so one of my battery prongs on the phone is off set a tad. loose a little. will that affect my android loading?
I have tried to search long and hard before I made this post, but honestly THERE IS ALOT OF INFORMATION TO READ THRU and i justget confused.
if anyone can shed some light on these two questions, i will appreciate it.
Click to expand...
Click to collapse
I used a cheap 4GB Micro-SD card and it seems okay. I think its recommended just to have a fast card to improve performance. The best thing to do is to try a different build. Ensure you did the following steps:
1. Flash HSPL(2 or 3, I personally used 3)
2. Flash a Windows Mobile ROM(I am using a barebone version of Energy by NRG28)
3. Flash a radio(Version 2.08.# or higher, i'm personally using 2.12.#)
4. Flash a build of Android(Any is fine, i'm personally using Darkstones Froyo 2.1 but try a few)
5. Take SD Card out, launch into Energy, insert SD Card, use file explorer to go SDCARD\Android\ and launch CLRAD.exe(Wont show anything but press a few times to make sure) and launch HaRAT.exe, wait until you get into Android(may take some time on the building data store text) then restart phone by doing step 5 again
^ don't think i've missed anything
******Edit******
Didn't see your post about SIM card until i posted this, try a free Pay as you Go sim or another spare SIM you may have, or maybe put SIM in when Androids loaded?
i would also look into starting from scratch , like going back to stock rom and working your way back up
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.
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.
Hello..a friend of mine gave me a HD2 to fix, said it can't load anything. As I own a HD2, I took it just to see what's wrong. I own an Asian HD2, and everything is fine, I tried various ROMs..both Android and WinPhone, settled at Hyperdroid. Anyway, I have no idea where the heck the other HD2 is from, neither my friend has.
So, the phone had nothing in it and was stuck at the HTC logo, so I loaded into bootloader and saw HSPL 3.03. Then I changed it to 2.08 in order to install MIUI android. Then I installed MAGLDR. The issue occured when I went to install CWM. I loaded the 150M partition at USB Flasher, it was doing all fine until it became stuck at "reset now...!". So I just took the battery off, and tried to load into AD recovery. While it loads to 1, then it shows "fatal hit" error. I tried a lot of times including task 29, but it persists. Was the phone bricked from earlier ? Something like heating issues I assume. Anyway, I tried to install my phones stock WinMo rom to it from SD but it also gives error like failed, not allow etc. The both phone looks the same, under the battery hood of my phone, it's written HTC HD2 T5858. On the other one, nothing. Rest visuals are same.
So is there any way I can bring this anonymous HD2 to life ? I think it's almost dead but still if there's any way you people can come up with. I'm using a 2GB Sandisk MicroSD and the phone's S/N is HT01CNW04979 ; if that helps to sort out the phone's identity. Your help is much appreciated. Thanks
http://forum.xda-developers.com/showthread.php?t=1520439
this is a thread I created 3 days ago....me, another user, and now you...
our hd2s are going to diee D: stop joking, I (and toher guys) think that is hardware related....like in my case....but I don't really know what's the problem, just guessing....take a look to my post
True that. Only the difference is, it's happening to me during clockwork recovery installation. And I don't know where the heck is the phone from so that I can load custom WinMo lol. My own HD2 is doing just fine by the way.
http://imageshack.us/photo/my-images/263/87604378.jpg/
http://imageshack.us/photo/my-images/412/59177201.jpg/
Well this one's a doozy of sorts, I'll try to be brief but any advice or assistance is welcome. Got a TMOUS HD2 on Saturday, it "worked" for a bit of time with the stock WinMo6.5 on it (no, I didn't care to look at the version, etc) and after having it for a few minutes to verify everything from a hardware perspective was working, I set out to do the usual process to get Android on it. I just wanted to get a CM7.2 build on it, preferably the actual CM7.2 and not a more customized ROM.
I have done the following:
- HSPL 2.08 - check, successful (as noted on the bootloader screen), done using HSPL4
- Task29 - check, successful (as far as I can tell), done from bootloader (VolDown+Power, Task29 provided by doloop single exe)
- Radio installed: 2.15.50.14 TMOUS (yes, it's the TMOUS version), check, successful (as far as I can tell), done from HD2Toolkit 4.2.0.1
- MAGLDR 1.1.3, check, successful, done from bootloader (DFT_LEO_MAGLDR113_DAF installer)
Now, at that point it was basically blank, obviously, so I decided to try and get CWM installed and that's when everything seems to have gone wrong. I get the FATAL HIT1 errors, it won't get past that. I read a post in the hundreds if not thousands I've been reading over where someone suggested when that error comes up, do the VolUp+VolDown+Power and do the reset - it only takes a half second since the device is already blank but some people reported in posts that it seemed to fix the FATAL HIT1 error and got CWM to actually load.
Didn't help in my situation. So I decided to start over at that point and flash the stock TMOUS 2.13.531.1 nbh (downloaded direct from T-Mobile, extension changed to zip, RUU_signed.nbh extracted to microSD card and renamed to leoimg.nbh) and attempting to do it from the bootloader.
At this point that aspect starts to work but it gets to about 8% (the same place it gets when using the actual T-Mobile ROMUpdateUtility method in Windows) and then dies. But the difference with using the microSD card method is that it tells me the following:
RADIO_V2 - RSA FAIL
in big red letters so I'm suspecting there's something going on with the radio that's just not kosher with the installer. I'm not sure how to proceed at this point - I'd like to get the HD2 functional again, preferably getting the stable CM7.2 ROM on it (not a big huge fan of ICS and JB is simply not my choice right now on the HD).
Problem is I don't know how to proceed at this point. If I can get it back to the stock WM6.5 that's fine for the time being so the device works, then I'll see what's going on with getting Android on it later, but I figure I'd rather ask a question or two, or three, before sitting here flashing radio after radio not being sure just what's going on and how best to get this issue resolved.
As noted, any advice or suggestions is welcome. I'm still trying various things at this time, including figuring out which radio to fall back to and test but, it's not going well so far.
loads of threads about this, my name for it is 'stuck radio' but it can also affect the spl too. Basically, there is corruption somewhere in the first area of nand, where the spl and radio live. whether thats software corruption (pray that it is, you may just stand a chance) or hardware corruption, you can't tell. the fact that magldr flashed would suggest its not as critical as normal, , some people get rsa radio fail and nothing at all works, no task 29, changing spl doesnt work, nothung at all. Often something seems to work (hspl gives success, for instance) but nothing actually changes after reboot.
So, first thing to try is - phone into a baggie, baggie into freezer, 20 / 30 mins later get it out, and real quick get the sd card in there already with the tmous stock rom as leoimg.nbh on there, and straight into bootloader, , see if it flashes past the radio section (the radio is flashed at roughly 6 - 10%, thats why you;re hanging at 8%, , 8% or 9% are the main reported percentages , lower % seems to involve the spl more (as you would expect, it is the first thing to be flashed)
There have been a few successes using teh freezer trick, and also a few more where JTAG has fixed it, but as often as not it never gets fixed.
failing that, see if you can flash a custom winmo 6.5 rom, because although the radio is failing to flash, it may still be in working order, and since custom roms dont include a radio, it may well flash, giving you at least a partially working phone.
Yah, the more I dig into it the more it's obvious there's an issue with the radio (like, duh ). I'm attempting to flash that Dutty's Leo Sense 2.5 that I saw mentioned in several posts by people that said they had success getting the device working at least to some degree - I grabbed the ROM, extracted the contents, copied the nbh to the microSD card, renamed it to leoimg.nbh, and at the moment it's just crossing the 50% point so, that is some progress at least (probably because it doesn't have a radio as you stated).
Will see what happens, but it is frustrating to appear to be able to do everything but actually get the radio flashed. HSPL flashes work after the reboot, Task29 always works (or appears to), MAGLDR only gives me issues when I try to get into AD Recovery from time to time, and so on. The usual HD2 issues I suppose.
This is my 5th HD2 and I'd like to get it working just like the others I've owned - none of them had anything like this much difficulty with getting Android (or anything at all) working properly so, maybe my luck ran out when I decided to get this one, who knows.
While I normally always find the TMOUS version of the HD2 here in pawn shops in Vegas, in the past week there have been 4 or 5 international unbranded models that popped up but, I avoid 'em since I believe the TMOUS variant is the better choice. Got this one for $75 and swapped a decent battery from one of the international ones when the clerk wasn't looking.
So much for that idea, either way (from microSD card or from Custom_RUU) the Dutty's ROM just hangs at the white/pink "stick together" screen and does nothing else. I then attempted to do a regular install of the stock TMOUS ROM again, no dice.
Geez... this stuff sucks sometimes.
Still hoping, of course.
ah thats a shame. the only other thing that comes to mind is seeing one or two threads with teh same problem where the poster simply tried again and again with the various versions of the (correct!) stock rom, and suddenly it flashed, and once teh radio was replaced it all worked again. I would have thought though that if it were going to do that, the freezer trick would also have worked.
I'd definitely try the three released stock tmous roms, , 2.10, 2.13 and 3.14, anbd perhaps some of the lower ones, too, , , see the 't mobile test & stock roms' thread in the tmous section DO NOT flash the first few, since the first one will brick it, and the next two or three have manufacturing spls, which can prove dificult to remove. (Not that you have anything to lose.)
flash from sd card., no point messing with the .exe, , more likely to work from sd card.
Heres a thought, , , forget the internal nand completely, , set up an ext4 partition, and then using sd card based recovery, flash an android rom using nativeSD. So long as magldr can be succesfully pointed at an sd card folder, you needn't use teh nand at all.
Dammit, no luck with any SD or NativeSD either. It simply won't ever get past the GO GO GO! event, no matter what I do. Tried several different recoveries (accessed from MAGLDR) and every time they just stick at GO GO GO! and never do anything past that. It DOES note the SD card is there, MAGLDR can access it to load the kernel, but it always ends up stuck at GO GO GO! and that's that. I was thinking if I could just get some type of recovery loaded (TWRP, CWM, I don't care) then perhaps I could do something more but, it's just a NO GO GO GO!
I did find that leodiag.nbh thing and gave that a shot, the diagnostic portion won't start because of the radio timing out (go figure, with the bad radio flash) so that won't even run, and the reset function doesn't either as it only sees the microSD card and still won't work.
It's like I feel like I'm missing one single thing that could turn it all around but, I'm tired of messing with it. Found the suggestion to hold in the reset button (mine is white, never seen a yellow or red one so...) and then turn the power on but it never does a reboot no matter how long I wait with the reset button still depressed.
Guess it's just not gonna happen this time...
yea unfortunately that's very often the way these turn out. the radio is blocking flashes from happening, and android from loading.
Do make sure you've given the freezer trick a good chance before you give up, i've read threads where the flash suddenly took after several attempts, (however in all fairness, if the freezer trick does help, it is usually indicative of hardware overheating problems anyway)
Well, against my better judgment but having enough experience (read: decades) with consumer electronics I figure the freezer thing - since it does actually work with hard drives in some situations - couldn't hurt.
Sure enough, after only about 2 minutes in the freezer (laying on some frozen food) I gave the SD update a shot and sure enough it finished, and after taking it out of the freezer a few minutes later, it booted into Windows Mobile just fine but, of course, then comes the letdown.
It froze up (not literally in terms of temperature), rebooted, then rebooted again before it got back into Windows Mobile, then on the 3rd reboot it just stopped and was stuck at the "stick together" screen where it simply won't get past.
So, obviously this one is suffering from the overheating issue, and I don't have access to an SMD oven or a proper heat gun (not that I'm going to go that far to revive it), so it's on craigslist for sale as-is presently. Funny thing is I've had 23 people respond for it since I know and they know and we here at XDA know all about how popular the HD2 is, even one like this one with potential good parts for use in some other one.
Let's hope someone actually shows up with cash, could use it for bills.
Thanks for the information, sam.
By the way would someone have a spare volume button ?
Sent from my HTC HD2 using xda app-developers app