Hey!
Im new to this forum but there seems to be a lot of experts here so i thought i'd try and see if anyone could help me!
Yesterday i put my desire to charge and after one hour i came back and it was showing the boot screen! The white background with the 3 green letters HTC! so i took out the battery and put it in again and restarted the phone but it only gets to that screen vibrates like 10 times and then hangs there! tried waiting for it for 30 min but nothing...
So then i tried to hard reset it and cleared the storage! but afterwards still the same!
Also when in "recovery mode" i sometimes see some green text flashing by for just a sec saying something like "warning...no image...."
Everything is in its original state, i havent rooted or reflashed it or anything... but i am willing to do so if it can solve my problems since warranty matters in my case will take ages!
The phones language is Swedish btw!
Can anyone help me?? its first now that u realize how much the phone means to you Miss my desire!
it sounds like the firmware is somehow corrupted. If you can boot the phone by pressing power and volume down, this will take you to the bootloader. From here you should be able to root the handset by following any number of threads here or on modaco!
Then I'd go Here and install this recovery. From then on you can choose a custom or stock rom to install.
You need to know though that rooting will void your warranty.
Have you also tried booting the phone normally with the SD card removed?
Hey there , to start off , Im pretty new to putting android and stuff on here haha. Well I finally got it to boot up android using Haret.exe , but then today I decided I wanted it fully on my system without windows...well heres the problem
I flashed the kaiser by holding the camera button and hiting the reset button...which worked fine. Well after I did that , I hit the reset button , and the AT&T symbol came up , then after a few seconds the Penguin Boot screen comes up and starts doing the weird script thing , then I hit the Dpad to install. When It come to the screen , I make sure that Both NAND things are bubbled off , then I go at it and hit install , and clear all data etc , then it goes to formatting. And after everything is complete I go to quit , then it does some more black screen script stuff and then it started booting the green weird logo ( not the android , the one for Froyo 2.2 ) and then after a few minuites it finally boots up. I then wait 10-15mins for it to finish everything once installed , and then I turn it off by battery pull ( and normal shutoff , ive tried both). then when I turned it back on , It STILL goes to the at&t logo , and repeats EVERYTHING above..please help ,I have tried everything here , and nothing seems to work.....ahhh im so confused haha.
Regards , Dread
What is the problem? Does it boot into android after that? It sounds like you are just describing what happens when android boots normally.
If it's the AT&T logo you don't like, search on this forum for splash screens, there are lots of replacements to choose from.
It boots into android after that , but when I turn it off , I have to go through the whole install screen agian and then it has all the same settings , its just very annoying
Are you pressing the D-pad and installing every time you boot? You only need to install it once....
The second time you turn it on, just don't press anything while it's booting, and it will go straight into android, with all your settings saved.
so why does it go to the weird boot text penguin screen? shouldnt android start up as soon as the phone boots? or is it supposed to be penguin screen , then android load screen?
it's not weird, all phone (and linux system) boot in this way.
Oh alright , Is there any way to make it into a bootlogo?
DreadCode said:
Oh alright , Is there any way to make it into a bootlogo?
Click to expand...
Click to collapse
Not at the moment, but right now the text screen is there to show that the phone is actively booting into Android. Once it gets to a certain point, the Android boot logo will start, and the text screen goes away.
I know it looks messy, but look at it this way. You're able to see just what the phone is doing during boot, and see that the phone is still booting and not freezing up and crashing.
He can make a splash screen, just not one to cover the kernel bootloader. I have one that got left over on ths phone after a modded wm6.5 rom. I keep it because it shows CPU, memory and ROM/radio verson in the 2nd splash.
Sent from my Not So Super Froyo using XDA App
I can put a boot image while the kernel initializes but the text will still overlap it due to framebuffer issues.
another way is set the output to a virtual terminal so is not visible.
So Today I changed my gfs lcd and the digitizer. Installed it fine, I make sure all the ribbons are properly connected and close up the phone. The phone turns on and shows the splash screen, seems like it's booting. I decide to use the latest RUU and see if that helps. A few reboots later i on the newest hboot, thing is it keeps happening, except now i can hear it boot (sprint boot anim). I battery pull a few times and I get it to boot. Touch screen works fine and all, tick Development and keep awake (because once it slept it wouldnt turn on again), mind you adb works while the splash is displayed and after the boot anim, adb also works when the screen is turned off and it wont wake up.
I just want a second opinion on if i should get another lcd screen. The one I installed didnt have the best reviews.
Thanks.
ps: i dont post alot because i know how to search, but i havent found anything on this exact issue.
Im slightly confused... so does it boot? or not? I am trying to make sense of what you wrote...
Try clearing the storage in hboot something may have corrupted during the process...
well it does boot you can hear the sprint boot animation, and i can also adb into it. getting into the bootloader works fine, booting into recovery or regular booting is the problem. Just displays the splash screen, but as I said I think it does boot into recovery/system because I have adb access.
edit: i just turned it on and it booted, but once put it to sleep the screen wont turn back on.
If it's not getting pay the splash something is stalling it... Did you try to run a logcat from adb? Do that and look for errors.
Sent from my PC36100 using xda premium
I was trying out using a keyboard with a cheap USB OTG cable, and all was good. Then all of the sudden the screen went buggy, where ever other line of pixels was shifted to the left or the right, almost like some sort of corrupted video file. It started to reboot itself, and it got to the black screen with the Google logo and then the screen fuzzed in the same way as before. It then starts to reboot and does the same thing over and over again. I find that I can get to the recovery screen with the scroll arrows. From there, if I tell it to reboot into recovery it goes back into the same Google logo bootloop. I then went back to the original recovery screen and I decide to try out adb to see if it works. Sure enough it does, and I unwisely start flashing a stock 4.2 bootloader image. However, while it is flashing the screen does the same fuzz thing and and stays fuzzed. Then it doesn't respond to anything. I take out the battery, and try to restart and with will not turn on at all, no vibration, no light from the screen, nothing. I tried a unbricking methods from there, and nothing can make it come back alive. Any ideas?
Additional info:
GSM tajkju
Bootloader unlocked
Running stock unrooted 4.2 that I flashed manually
Stock recovery
So, the phone works, but when it turns on, nothing displays at first, no logo or loading animation. but, once its fully tuned on, everything shows again. now, the real issue... I cant get into recovery mode, or anything to try and get it factory rest or flash new firmware on it to fix the issue, because the screen displays nothing when I'm trying to access recover menus. it just stays black until i disconnect the batter and let it turn back on normally all the way.... tried some research and did the usual black out issues... but nothing.
any help would be great thnx!