Hi folks, my HD2 just went south. whenever I try and boot the phone it just sits at the CLK loading screen, I can access it with fasboot, but not ADB. I have tried to re-flash recovery, and to boot it from files on my PC, but it then just stops at 'cmdline:'. No matter what button combination I try it just goes to the CLK screen, even hard reset.
Does anyone have any idea how to get past this ?
have you installed CWM or any rom on the phone ?
Yeah, I have CWM & CM7 nightlies. I can still flash recovery as fastboot works at this stage, but I cant get the phone to boot to any other stage, ie the rainbow screen. I am actually begining to think that I have a hardware issue, possibly relating to the button cable or so.
stuck on cLk loadning screen
UbuntuBhoy said:
Yeah, I have CWM & CM7 nightlies. I can still flash recovery as fastboot works at this stage, but I cant get the phone to boot to any other stage, ie the rainbow screen. I am actually begining to think that I have a hardware issue, possibly relating to the button cable or so.
Click to expand...
Click to collapse
this my 3th phone with the same issue. never got a good answer.
Related
Hey you guys
I recently installed amon ra's recovery v. 1.7 on my magic 32a (radio 6.3.5 something) after I rooted my phone, of course.
Now, I thought that with the new recovery I would be easily able to flash a custom rom onto my magic. This was however not so easy, because the recovery behaves in a very weird way. Whenever I tell it to flash a new rom from a .zip image, or wipe the phone, or anything, it just reboots my magic and thats it. Also, the recovery happens to freeze quite regularly when I don't act very quickly. E.g. when I boot into recovery mode and don't touch the phone for the first 5 seconds, it wont respond any longer.
So, I'm probably doing something wrong here. I would appreciate any help from anyone. (and btw, i have the official android 1.5 sense rom installed on my magic, os I cant use rom manager either, since it only supports android 1.6 upwards.)
Look at the root guide in my signature..
Do step 0, 1, 2, 5 and 7 only.
It should flash the recovery partition one more time.
Hopefully it will fix your problem :0)
mumilover said:
Look at the root guide in my signature..
Do step 0, 1, 2, 5 and 7 only.
It should flash the recovery partition one more time.
Hopefully it will fix your problem :0)
Click to expand...
Click to collapse
hey, thanks for the quick response. I still have a few questions though, since I am quite a newb. So when I type all of those commands into cmd, doesnt my device need to be connected to the computer somehow? I read somewhere earlier that I simply connect it using the "mount" funtion, the problem is that that doesnt seem to work anymore for my magic, because after I hit "mount" it simply goes back to "usb connected" without acutally mounting. So ..how do I connect the device to the PC while entering the commands?
ok... my bad..
Try to read the ENTIRE guide... then do the steps i mentioned above :0)
Don't mount it... just connected... but again.. read the guide.
thanks a lot
I didnt use your method to flash the image, but the hero recovery works way better than the one I had before. I managed to flash a rom now. So happy ;D
ok i think i just did a bad mistake
i installed rom manager after i had flashed an android 2.1 rom on my magic. THen i told it to flash some rom from my sd card and also wipe some data, or something. Now my magic gets stuck on the magic bootscreen, like it keeps looping. Did i brick my phone ..or is there a way to fix this? please help me, (
most likely is that the rom you flashed doesn't have a compatible kernel for your phone.
Just boot into recovery and flash a rom that is compatible.
cant boot into recovery ..it just keeps looping
Then you will need to boot into fastboot and reflash a working recovery.
Clockwork has issues flashing the clockwork recovery sometimes.
to boot into fastboot i need to hold power and back, right? ..that doesnt work either. again, it just keeps looping.
so, guys ..did i brick my phonne..?? :S
da robat said:
to boot into fastboot i need to hold power and back, right? ..that doesnt work either. again, it just keeps looping.
Click to expand...
Click to collapse
you're probably not doing it right. you should still be able to get into recovery or fastboot and install a different recovery. i'm using RA-magic+v1.7.0.1 recovery it has bugs but pretty stable.
so what am i doing wrong??
just realized when i connect the phone to my pc over usb and then boot it, it connects to the pc for a second or less and then disconnects again. Dont know if this helps anyhow.
pull battery, put battery back in. hold back and push power.
Should be good.
tried that like 50 times. phone just keeps looping ..like, it restart over and over again.
What you have is what hundreds before you had when they used Rom manager.
The system will not boot into anything.
My advice is to never use Rom manager for 32A device.
The fix:
Keep pushing the back button while the system reboots... just mash the **** out of it..
I helped out someone before you, and he did it for over an hour or so...
It's a timing issue...
Good luck
haha ..so is there still hope?
cheers for all the answers ;D
i do have one question though, actually.
Shall i just press the back button continuously ...while it keeps looping, or should i rather restart the device after each loop and hold the back button?
just mash the back button.
Hi guys,
I recently tried to flash a rom on my phone and when the process was done, all I got was a black screen.
Fastboot still works and I can flash euro roms like on the tutorias fine but the phone simply wont boot.
I can go into emergency mode to flash in it in KDZ, the flashing works fine but still, the phone only displays a black screen.
When I press the power button it vibrates, the PC recognizes the device fine, so I know the phone isnt bricked, I just cant get it to display anything on the screen! please help!
Which rom did you try ?
Using swiftdroid RC4 2.0, but I found out what the problem was. Since on flashboot factory reset was in German, "reset und wipe" or something like that, I did not check it. Reflashed it and it is now working, the only problem is taht tehre are no boot animations whatsoever. only a black screen between pressing the button and going into android. any fix for that?
thank you for the replies!
EDIT: Also, by going into reboot > Recovery, nothing is displayed. this only happens on boot. I flashed originally with Euro+fast.kdz, and that is when this problem begun.
Flash this boot.img
and for the recovery, ace you installed??
I installed CWM for recovery, if that is what you asked.
Going to try to flash it and let you know, hope it does break anything
EDIT: nothing. No boot images. Going to leave it alone until I need it for something. I use an X10 mini, I just bought this phone for testing. Not liking the resistive screen!
you tried to flash an X10 with Rc4 ?
No, I have an X10 which is my default phone, I boght this optimus for testing, I flashed RC4 on the optimus, not the mini. not that stupid
You're not the only one with this problem, this will fix it.
http://forum.xda-developers.com/showpost.php?p=10238074&postcount=41
Did you tried with another ROM ?
Yep, follow this... since I can't post links, I can't help......
Hello,
I am trying to load the Sensation XL ROM onto an HD2
I followed this guide to get CLK/Fastboot ADB going:
http://forum.xda-developers.com/showthread.php?t=1402975
the Wipe and everything went fine; the HSPL was set to 2.08
I got to the point where it tells me "fastboot: processing commands", I run the CLK install recovery, and everything shows that it went okay, so when I wait for it to reboot and hold home, it shows a bunch of text and the last line says "cmdline:no_console_suspend=1" and it reboots in a loop, but if i touch nothing as it is booting, it returns back into fast boot.
The fastboot shows that it is flashing everything ok, and there are no errors when I go to load CWM, but it reboots before CWM loads or whatever. I actually got into it once after many tries, but restarted and cant get back into it.
CLK Ver: 1.4.0.1
Recovery Ver: 5.0.2.6
Toolkit Ver: 4.2.0.1
Now the power button will not work, and the END CALL + VOL DOWN will not bring up the "serial" or "usb". What should I do? Since I have fastboot going, I just need to know what to do to get CWM working.. Thanks!
:EDIT:
I noticed it is telling me after fooling around:
ERROR: Cannot read boot image header
ERROR: Could not do normal boot. Reverting to fastboot mode.
is the recovery borked?
Try reflashing the clockworkmod recovery with the HD2 toolkit.
Based on your story I can't really tell where you went wrong.
About the end call button not working, it could be a hardware failure,
most HD2's are about 2 years old. Maybe the flex cable thats connected to your hardware buttons is a bit crooked.
Also CLK has the ability to charge when turned off, you can check this by looking at the orange LED next to the earpiece.
If it's in Offmode Charging it won't respond to any hardware buttons, could be that was the problem..
Anyway, hope i've been of help
TyIsOwned said:
Hello,
I am trying to load the Sensation XL ROM onto an HD2
I followed this guide to get CLK/Fastboot ADB going:
http://forum.xda-developers.com/showthread.php?t=1402975
the Wipe and everything went fine; the HSPL was set to 2.08
I got to the point where it tells me "fastboot: processing commands", I run the CLK install recovery, and everything shows that it went okay, so when I wait for it to reboot and hold home, it shows a bunch of text and the last line says "cmdline:no_console_suspend=1" and it reboots in a loop, but if i touch nothing as it is booting, it returns back into fast boot.
The fastboot shows that it is flashing everything ok, and there are no errors when I go to load CWM, but it reboots before CWM loads or whatever. I actually got into it once after many tries, but restarted and cant get back into it.
CLK Ver: 1.4.0.1
Recovery Ver: 5.0.2.6
Toolkit Ver: 4.2.0.1
Now the power button will not work, and the END CALL + VOL DOWN will not bring up the "serial" or "usb". What should I do? Since I have fastboot going, I just need to know what to do to get CWM working.. Thanks!
:EDIT:
I noticed it is telling me after fooling around:
ERROR: Cannot read boot image header
ERROR: Could not do normal boot. Reverting to fastboot mode.
is the recovery borked?
Click to expand...
Click to collapse
NRG is an xl rom, have you tried that?
Sent from my Dell Streak 7 using xda premium
So I have a Mytouch 4G and its stuck in Fastboot... Okay no problem. Flashed RUU Exe still wont turn on. Flashed RUU zip still won turn on. Unlocked Bootloader and flashed recovery and ROM still no go. Everytime I turnit on it goes straight to Fastboot. Only way to turn on is in fastboot wait 30 seconds and navigate to Hboot. In Hboot go to CWM in CWM reboot system now and everything works. I just have to do those 3 steps to turn it on. Has anyone else had this problem? And is there a fix?
addictedhacks said:
So I have a Mytouch 4G and its stuck in Fastboot... Okay no problem. Flashed RUU Exe still wont turn on. Flashed RUU zip still won turn on. Unlocked Bootloader and flashed recovery and ROM still no go. Everytime I turnit on it goes straight to Fastboot. Only way to turn on is in fastboot wait 30 seconds and navigate to Hboot. In Hboot go to CWM in CWM reboot system now and everything works. I just have to do those 3 steps to turn it on. Has anyone else had this problem? And is there a fix?
Click to expand...
Click to collapse
it sounds like it is a recovery issue or a sticking volume button on the side..(just a guess) try pushing it up and down (wiggling it) if still an issue.Try flashing a different recovery such as 4EXT instead of CWM and see if that make a difference you can find it here http://www.4ext.net/ it is just something to try in case your recovery image is corrupted be careful ! let me know if it fixes your problem
[email protected] said:
it sounds like it is a recovery issue .Try flashing a different recovery such as 4EXT instead of CWM and see if that make a difference you can find it here http://www.4ext.net/ it is just something to try in case your recovery image is corrupted be careful ! let me know if it fixes your problem
Click to expand...
Click to collapse
It was actually stock and never rooted when I had this issue. The recovery was stock and still had the issue. It was when I installed CWM and a ROM that I was able to get it on, but I have to do those 3 steps.
Clean your USB port, check if any of the keys (trackpad?) is stuck. If you boot to fastboot and not to HBOOT - it means the VolDown key isn't the culprit, but maybe there is a key combination that is causing boot directly to fastboot, or maybe there' something in USB (dirt caused some high impedance connection between some lines) that causes your phone to boot to fastboot.
addictedhacks said:
It was actually stock and never rooted when I had this issue. The recovery was stock and still had the issue. It was when I installed CWM and a ROM that I was able to get it on, but I have to do those 3 steps.
Click to expand...
Click to collapse
did you check the volume button does it seem flakey when you use it ?I was editing my reply when you responded sorry?I was in the process of revising my answer up ⇑ ⇑
[email protected] said:
did you check the volume button does it seem flakey when you use it ?I was editing my reply when you responded sorry?I was in the process of revising my answer up ⇑ ⇑
Click to expand...
Click to collapse
I thought that the Vol Down button might have been stuck as well but its not. All the buttons are fine and the usb port is clean.
addictedhacks said:
I thought that the Vol Down button might have been stuck as well but its not. All the buttons are fine and the usb port is clean.
Click to expand...
Click to collapse
thats definitely a tough one sorry i couldnt help!!be patient hopefully someone will come along an offer some better advice!!!
I've been rooted for quite some time now, was always using axiom, today I decided to try something new, I flashed via twrp ROM and gapps, twrp said no root, installed superuser? I swiped yes, phone booted to Google screen, but now is the stupid part,
Keeps boot looping there, absolutely no boot loader when trying to boot into it, computer won't read device, just says android with a yellow exclamation mark and says the drivers are incorrect or something, I cannot fast boot because of this, when trying to enter boot loader it just gores to Google screen goes black then flashes red light,
Is this fixable? Will JTAG work maybe (last resort), anybody who has the time to help will be my hero haha, I work in a few hours so I won't be back until the afternoon, but please anyone!
Oh and phone isnt unresponsive, still vibrates, still charges and still boots google logo,
Just remeber i cant flash stock img files due to not being abke to use fastboot:/ unless there is a way to get the computer to read my phone
Thanks in advanced to people who reply,
joshracine1 said:
I've been rooted for quite some time now, was always using axiom, today I decided to try something new, I flashed via twrp ROM and gapps, twrp said no root, installed superuser? I swiped yes, phone booted to Google screen, but now is the stupid part,
Keeps boot looping there, absolutely no boot loader when trying to boot into it, computer won't read device, just says android with a yellow exclamation mark and says the drivers are incorrect or something, I cannot fast boot because of this, when trying to enter boot loader it just gores to Google screen goes black then flashes red light,
Is this fixable? Will JTAG work maybe (last resort), anybody who has the time to help will be my hero haha, I work in a few hours so I won't be back until the afternoon, but please anyone!
Oh and phone isnt unresponsive, still vibrates, still charges and still boots google logo,
Just remeber i cant flash stock img files due to not being abke to use fastboot:/ unless there is a way to get the computer to read my phone
Thanks in advanced to people who reply,
Click to expand...
Click to collapse
It happned with me too when its reboot to google logo before that press vol down and power button to get into bootloader