I flashed HSPL3 on my HD2..and flashed a radio on there also..then i did all of the necessary steps (ie. downloading Android rom, copy to root of SD, click CLRCAD, then HARET.exe..after that it goes to a black screen with about 5 lines of VERY SMALL text..and then it goes to HTC logo screen & gets stuck there forever until i do a battery pull..i've installed various radios on my HD2 for experimentation, still does the same thing..help please??
FYI, Please post questions in the Q&A Forum as per mskip's Sticky http://forum.xda-developers.com/showthread.php?t=713942
Most Android builds do take 15-20mins to boot up the first time (they have to create the data.img file). Your best bet is to check there isn't a data.img file in the Android folder or on the root of your SD card, if there is, delete it. Then try booting again. Once it gets to the HTC logo screen, leave it and go get a a good book or something . My HD2 took about 20mins to boot up the first time, after that, it takes about 20-30 seconds.
Alternativly you can download precreated "data.img"s but you need to make sure they're OK to use with your chosen Android build.
If that doesn't work, check here for more info.
Dave
P.S. Mods, please can someone move this to the appropriate forum. Ta.
verify your android path in startup.txt you'll find the mistake
I'm sorry, i realized that after i posted the thread up, i apologize. I did everything stated in the thread, and still having the same problem. I switched SD cards, formatted them, same problem. I've tried over 5 android builds, no change.
First boot can take a wail, and did you placed also the img file (the 512mb or the 1Gb) on your SD?
When you boot up WinMo, don't enter the PinCode.
Then you should be able to start Android.
The first startup it is hard to stay tuned
Try to start, put your Phone on the desk and get back after 30 Minutes, then everything should be fine...
maybe try a different radio?
caseyman4285 said:
maybe try a different radio?
Click to expand...
Click to collapse
He is has troubles with android first boot up. Radio has nothing to do with it.
P.S Try this rom , it's goddamn amazing in terms of stability and preformance:
http://miuiandroid.com/community/threads/archived-miui-versions-hd2-gb.16553/
Related
hey guys i need help i had android on my htc hd2 before but i deleted the folder out of my sd memory card and now i try to root android on my sd card and i have an error it would just boot to the logo HTC i try different rom and im running radio 2.14 could someone help me please i also reformat my sd card many time same thing still happening please help me out
I occasionaly get the same thing when trying a new WM rom. If you don't mind flashing your phone then do a task29 which you can find in some custom ruu programs to completely wipe the phone. then when you want to install the WM rom, unplug from usb, switch off.
Then press and hold volume down key and power button. You will boot into recovery mode. You can then install the fresh WM rom. Once installed copy the android folder back to the root of your SD card and boot up! I know its a long way and that you'll lose all data but it'll get your phone back up and running with any luck.
Mikeanywhere.
kkk imma try that to see if it works
same thing still happening i also try another sd card and im still having the same issue as before
dude, learn to use some punctuation. your post really just becomes blah blah blah
you are booting into windows just fine and booting android is the problem, or you can't get your phone to work at all?
if you're phone don't work, its a big issue that i'm not gonna touch. if its just android that isn't booting, just download a new version and go from there
+1 download a new build or another copy of the one you were using before....
if you dont let a build load properly during the first boot then it can corrupt some files I think.
I could be wrong but Im sure I read that somewhere.......
installed the hspl, updated to the radio rom to 2.14.50.04 and using desirebuild_v 5
starts normally with the dissolved numbers and the penguin guy but then just goes on forever about the battery percentage. just a bunch of numbers and batt: 52%
batt: 51%
ect. for pretty much ever
is there something that ive missed?
chrisman99 said:
installed the hspl, updated to the radio rom to 2.14.50.04 and using desirebuild_v 5
starts normally with the dissolved numbers and the penguin guy but then just goes on forever about the battery percentage. just a bunch of numbers and batt: 52%
batt: 51%
ect. for pretty much ever
is there something that ive missed?
Click to expand...
Click to collapse
Try this:
You seem to have WinMo and a compatible radio.
1. Format your SDCard with FAT32 (backup your data first) (what kind of card do you use? (size and class))
2. Copy your android to your SD card (read the installation guide of the chef, not all Android Builds runs from /Storage Card/Android)
3. Run CLRCAD.exe (or something like this) and then Haret.exe.
4. Be patient, it will take a few minutes at the first boot.
5. if you complete the setup process reboot and then you can do what ever you want
tried that same thing.
just repeats the same 5 lines or something over and over
i have a small question, i successfully booted to android, question is when i need to reboot my phone i cannot lunch android again , can you help me ?
chrisman99 said:
tried that same thing.
just repeats the same 5 lines or something over and over
Click to expand...
Click to collapse
Ok... We try some other things
What HD2 do you have?! 512MB or 1024MB?
Which Radio do you use?
Which Android ROM?
Radio 2.12.50 has a better current cosumption for me. Maybe you try this radio, too
What you need to realise is that when we say "wait a few minutes" we mean up to and including 15... It can seem that the HD2 has frozen but wait long enough and it will boot into android, 1st it has to set up your card the way it likes with a (generally) 1Gb image file. This takes a little while to do.
Patience grasshopper......
Sorry for this not being directly related but it seems like a resonable place to ask my question. So ive flashed tons of winmo roms but just now starting to try android. I flashed nrgz's bare bones rom for android. and the only android that I can get to load is the one that nrgz posted himself a month or to ago. I have tried 3-4 different builds after and it starts linux but only for a second than either goes to an htc screen frozen. or a bright blue screen frozen. Ive tried everything that ive read about. I have reformatted my sd card twice. ive tried 3 different sd cards. ive tried a different roms. Nothing works. I like nrgz andoid ROM that he has with a froyostone build of android but it is VERY unstable and I cant get it to run for more than 10 minutes without freezing and want to try something alittle more stable. ANYBODY know what else i can try. thanks.
sorry i just figured it out. Im AN IDIOT> i thought that i had to see linux run all the way through like with nrgz. but apparently the htc screen is good. MY BAD>
safeburn said:
i have a small question, i successfully booted to android, question is when i need to reboot my phone i cannot lunch android again , can you help me ?
Click to expand...
Click to collapse
Follow my guide and never have to use winmo again.....
http://leoandroid.com/viewtopic.php?f=51&t=182
If you need to boot back into android you need to launch haret.exe. If you press on it and it does nothing then press and hold on it to get some options. If open is not in the options you can either download total commander to open the file or download EBL 2.1 and install it. Both of these apps are winmo apps. I found them online.
it turned out that it was due to the files been in the android folder and not direct onto the sd card which was a bit annoying cos thats originally how i had it before i read somewhere people put it in an android folder so did this to keep it organised.
still have a few errors tho and sleeping and dying so was gonna try the froyostone 3.2. this seriously wont but tho. blue screen straight onto black with green htc and left for ages with no luck. any tips on that one?
also im using rom version 1.66.405.2 if that would cause any issue?
tried froyostone 3.1 and got that to boot but still a bit hit and miss. also when it sleeps for long periods overnight its dies. is this normal or is there anyway to fix it?
AMCJUNGLE said:
Follow my guide and never have to use winmo again.....
http://leoandroid.com/viewtopic.php?f=51&t=182
If you need to boot back into android you need to launch haret.exe. If you press on it and it does nothing then press and hold on it to get some options. If open is not in the options you can either download total commander to open the file or download EBL 2.1 and install it. Both of these apps are winmo apps. I found them online.
Click to expand...
Click to collapse
Thank you very much , i will try this...
different builds seem to just not work for some people....
its all about trial and error.......
i went through about 6 different builds before finding one that 90% stable.....
its this one.....
OK well I have trying my best as a noob to research for 2 days not in and out on how to fix my issue
My friend tried rooting my phone and to install a different rom. I am on 2.1 and unfortunately I got the phone used with 2.1 already on it so I don't know if it was a leaked or legit 2.1 rom, and I am learning as I go here to fix this issue as I have never new how to do this stuff nor have I ever done it.
Where I am at now:
only thing that happens when I hit power is the phone "vibrates then stays on the 3 skateboard screen" or press "volume down + power" and it goes to the Hboot screen. I go into recovery and it goes to clockworkmod and from there after trying to install any roms from the sd card it says on the last 3 lines
"E:Failure at line 9:
copy_dir PACKAGE:system SYSTEM:
Installation aborted.
and every time I go back or power up to the Hboot screen it does not have any "update bar" (I guess if this was done right as I read on other threads there should be some type of update bar) on the right corner or any other options "for me to select" accept:
FASTBOOT
RECOVERY
CLEAR STORAGE
SIMLOCK
and then with some other info above the Hboot highlighted in blue
I have tried formatting the sd card a bunch of times, I did the clearing of the "wipe data, wipe cache partition, wipe dalvikcache" as I read to do over my reading, but I see that if I go under any restore options under clockwork, no files are found for me to back up too so I am seeing he did not back up any of my info, I also have tried using 2 different ds cards.
So more less it looks like my options are to get this fixed from the only place my phone will boot to with options and thats when I press volume + and power so I guess loading whatever I need to my sd card>>if thats an option or am I screwed, I have seen many tutorials but none of them start where my particular position is stuck at in Hboot. this is my only phone and I had to buy a prepaid which is just about out of minutes, I put an add on craigslist trying to get someone I will pay to fix my issue but no luck, please I need help and I will pay u somehow to guide me through this of my exact issue, I was trying to get to rom 2.3 but if it's easier to get back to 2.1 rom then so be it.
PLEASE!~~
Please HELP!
Cheeva316 said:
Please HELP!
Click to expand...
Click to collapse
Got a solution in the making for you, just give me about 30 minutes.
Edit: Maybe 45 minutes lol, sorry i'm testing this before I have you do it to see if it works.
Ok download the following files:
http://www.mediafire.com/?njwqa7axwzyaqgb
http://www.mediafire.com/?f69cl8dc747h0l9
http://www.mediafire.com/?xg8nnqs177xggx4
http://www.mediafire.com/?qxpi5wsx5lzbhbo
http://www.mediafire.com/?4tg67hck7vh1xxs
Edit: Flash the "rootme.zip" first then follow the rest.
Now what you need to do first is extract the "nandroid" file to somewhere you can easily find it.
Now take the folder called "nandroid" along with all the other zip files you downloaded and place them on your sd card. Put your sd card in your phone and power on with volume down+end. Press volume up. Use the trackball to select "Backup/Restore". Use the trackball again to select "Nand Restore". Use it again to select "HT9BGHG01402". Use it again to select "BDS-20110125-0901". Let the restore run, then power off your phone. Turn your phone back on with just the power button, let it run (might even take up to 10 minutes for the phone to start up). Let me know if the phone boots up or not after about 10-15 minutes. This should work and if it does then we can go from there, even to getting you 2.3 if you want.
You might be asking, what the hell is he having me do ? Here's what i'm doing. I made a nandroid backup a few months ago of when I had kaosfroyov39 which is a 2.2 rom. I am going to have you flash MY backup to YOUR phone which when done right, CAN work. Anyway, let me know what happens and remember to give the phone about 10-15 minutes to boot all the way.
Cheeva316 said:
"E:Failure at line 9:
copy_dir PACKAGE:system SYSTEM:
Installation aborted.
Click to expand...
Click to collapse
( Another phone on the precipice of being ruined by someone's cobbled-together "clockwork" recovery. )
If the /system flash memory partition got corrupted in a way that left a lot of pages marked as bad pages, then the /system partition will be "short", and only small ROMs will successfully load into it, if at all. That might be the cause of the above error messages.
But - because you are using Clockwork, there is really no way to know if that is the case, or if you simply have a whole bunch of corrupted ROM files on your SD card. That's because Clockwork does not verify ROM files before it starts flashing them - which allows total garbage to be flashed to the phone. (That's why Clockwork should never be used by newbs).
Here's what I would suggest you do.
- Make sure you are keeping the phone well charged. (Leaving the phone in HBOOT mode will discharge the battery quickly, even if it is plugged in to the charger, BTW).
- Report the exact bootloader version you have - probably 1.47.0000 or 1.49.0000, but it could be something other. Please be precise.
- With the power off, eject the SD card out of the slot and see if you can boot into the normal HBOOT menu with no SD card in the slot. Report your result.
- Boot into the recovery menu and tell us what version # of the recovery you have. If you can determine the details of how your friend attempted to root the phone, that might be pertinent. Again - precise details are valuable; vague hand-waving not so much.
- The Amon_RA recovery has a mode ("USB-MS toggle") which allows you to mount the SD card to the PC. Does your "Clockwork" recovery have this feature, or are you able to put files onto the micro-SD card using a media slot on a PC?
- Be aware that one or two people that were in situations that are very close to what you described ended up bricking their phones because they went from where you are now to attempting to use either a PB00IMG.ZIP ROM, or an RUU utility. Their phones went from bootable (in the way that yours is now) to bricks in that process.
What I would suggest you do at the moment is to find the SMALLEST Eris** ROM you can find, get it onto your SD card, verify that you didn't corrupt it, and then perform a "wipe data/factory reset" in your recovery and attempt to install it. If you get the same errors as above, then you should definitely NOT try to do a PB00IMG.ZIP or RUU installation. (The current gingerbread ROMs (e.g. GSB v1.4) are pretty small - they only use about 65% of the /system partition.)
I have a flashable "repair" file which might be applicable. It is not a "ROM" per se - it uses some low-level MTD (flash memory) repair techniques, and also flashes into place the original Amon_RA (v1.6.2) recovery, instead of whatever p.o.s. "Clockwork" recovery you currently have on the phone; but I regard it as something which should only be used as a last resort. But - without some more details and testing on your part, I don't feel comfortable about posting it up.
Let me know.
**PS I wanted to ask one more question - this is an Eris we are talking about, right? (I note you were posting in the Hero CDMA forum not so long ago).
Well I want to thank you for replying with such info but it seems that the recovery image file that I reinstalled on the phone was bad cause when it was updating the bar was going up but as it was going through each item it was updating.. I noticed "bootloader in red letters" with I believe saying "error" next to it and then same on another item it tried updating then the phone powered off and now it's dead, tried everything, no charging light comes on, computer (2 different computers) wont reconize it, it's doing nothing at all, I will try to get my hands on another battery but I am broke, but I doubt it's the battery cause I heard with a bootloader error (or damaged) then the phone won't boot up or do anything so I guess the phone is scrap for parts which sucks cause now my friend who started this deal killed my only phone me n my family had, another lesson learned...time to try n sell some stuff on craigslist..damn
Yes it's a Droid Eris...or was! damnnnn...
Again thank you for your help very much appreciated...
Wish I would of read this part before I let my friend re-load the "PB00IMG.ZIP" cause thats exactly what he loaded and then it started the process what I jus described above..f***k!
Be aware that one or two people that were in situations that are very close to what you described ended up bricking their phones because they went from where you are now to attempting to use either a PB00IMG.ZIP ROM, or an RUU utility. Their phones went from bootable (in the way that yours is now) to bricks in that process.
Cheeva316 said:
Wish I would of read this part before I let my friend re-load the "PB00IMG.ZIP" cause thats exactly what he loaded and then it started the process what I jus described above..f***k!
Be aware that one or two people that were in situations that are very close to what you described ended up bricking their phones because they went from where you are now to attempting to use either a PB00IMG.ZIP ROM, or an RUU utility. Their phones went from bootable (in the way that yours is now) to bricks in that process.
Click to expand...
Click to collapse
Well, I am very sorry that this happened to you and my advice to you didn't reach you in time. From the details that you added, I am pretty sure that you indeed have a hard brick.
BUT - the death of your Eris can still help others avoid the same fate. If you can reconstruct the rooting process you went through,
[SIZE=+2]PLEASE LET US KNOW EXACTLY WHAT ROOTING METHOD YOU USED[/SIZE] - and then we can wave people away from it.
When I say exactly, I mean extremely specific: do you still have the download file that you used? If so, push it up to an uploader site and give a link to it. (I think you mentioned unrevoked or something). Do you still have the exact link you used to download that rooting software? Was it Unrevoked? Z4root?
bftb0
I will tomorrow as I saved all the files on my laptop n I am on my pc now, but will do try my best as I am a newb to this phone stuff
Did you try what I suggested or is it too late ?
phone wont do anything so cant do nothing...
Did you find out any more details about the rooting method you used?
might be a couple more days till I can get to it, my laptop is messing up now...all the saved info was on it
Hello guyz,
I followed the guide form here, after 3 days of struggle finally it generated cm-10.1-20130802-UNOFFICIAL-shooter.zip file in the output directory. And then I flashed it to my evo but it just switching off a few seconds after htc logo.
I have uploaded zipped file which consists of all the files generated in this process, if any person have any idea on how to fix it please help me.
Download from here
Edit: Today I have flashed along with pre-compiled raring-preinstalled-phablet-armhf.zip, now the device is not switching off but stays at black screen with LEDs on.
should this be here as it's not complete..
johnnyboi1994 said:
should this be here as it's not complete..
Click to expand...
Click to collapse
I felt same as you while posting this thread, but as porting of ROMs comes under development category I opened up a new thread under development forum. I think any ROM which works or not should be under development forum to get help from devs to get issues fixed.
If any moderator feel that it is inappropriate to post this thread here, please kindly move it to the correct location.
Thank you.
There is no bootanimation for Ubuntu. It boots the splash screen, then it goes to a black screen for awhile on my N7. The black screen is the boot animation screen more or less. And it depends on what build you try. One day it boots, the other day it jumps me back to the multirom screen. I'm sure it would infinitely reboot if I wasn't multirom-ing. I'm dual booting using THIS method, therefor it doesn't wipe everything and I can bounce back to a more stable android. Ubuntu will be kick ass when it hits hard. I can already see a bunch of benefits.
If we wait for more time does it display any UI? What might preventing the device from successful boot? Did it ever made to its desktop?
BTW thank you for your link, I'll try to dual-boot along with android.
rapol.goutham said:
If we wait for more time does it display any UI? What might preventing the device from successful boot? Did it ever made to its desktop?
BTW thank you for your link, I'll try to dual-boot along with android.
Click to expand...
Click to collapse
Not sure for this phone, try it? The N7 booted up. My phones hanging on to it's last breath, I'm not gonna push it anymore then I have too. Ubuntu runs off the normal android kernel, not an Ubuntu version. So I'd say kernel would have a lot to do with it working or not. The .img files they have are bootloaders, so that may be an issue. Although the ubuntu boot img isn't needed, the android one works.The version I got to work was the "saucy" July 27th or 28th build, haven't tried anything after that. That specified dual boot only works for some Nexus devices. Can't remember how long it took to boot, I'd assume as long as any normal initial boot of a rom. I would go to another forum where it has been ported, and ask/read hard there. Good luck.
Ok guys so, I had installed badadroid but after reading around the internet about how certain ROM was faster I decided I would try it, I flashed the uninstall zip in the badadroid thread and followed the instructions on the blog of that certain developer HOWEVER at one point I'm asked to flash a new FOTA and bootfiles with multiloader, I did that but at some point I messed up, now my phone boots up to this screen and sometimes to the recovery provided by the other ROM, following the steps to install that ROM and rebooting doesn't help at all and I keep getting stuck in this screen, my phone shuts down automatically a few seconds later and multiloader doesn't recognize it.
I still have hope because, when plugged in, it boots past this screen and into said recovery, however it seems like Bada was wiped during this process and I can't find a way to go back now (I only found out this happened right after I had already done this)
Is there any way to force it into download mode? I need my phone
Thanks
EDIT: Managed to get into download, will see what I can do, I guess I can work things out now, you can close the thread
Also, sorry for the bad image quality, I took that with my laptop's camera
Fidelator said:
Ok guys so, I had installed badadroid but after reading around the internet about how certain ROM was faster I decided I would try it, I flashed the uninstall zip in the badadroid thread and followed the instructions on the blog of that certain developer HOWEVER at one point I'm asked to flash a new FOTA and bootfiles with multiloader, I did that but at some point I messed up, now my phone boots up to this screen and sometimes to the recovery provided by the other ROM, following the steps to install that ROM and rebooting doesn't help at all and I keep getting stuck in this screen, my phone shuts down automatically a few seconds later and multiloader doesn't recognize it.
I still have hope because, when plugged in, it boots past this screen and into said recovery, however it seems like Bada was wiped during this process and I can't find a way to go back now (I only found out this happened right after I had already done this)
Is there any way to force it into download mode? I need my phone
Thanks
EDIT: Managed to get into download, will see what I can do, I guess I can work things out now, you can close the thread
Also, sorry for the bad image quality, I took that with my laptop's camera
Click to expand...
Click to collapse
In any case, don't worry, you can't break wave so easilly.
This Fota have default boot to android and not bada, and if you installed Nand bada is indeed dead.
But you still can flash full bada with Multiloader and you still can install Android with this fota/bootfiles, just make sure to follow installation procedure of your rom (by the way, this fota is compatible with ALL roms)