Related
Hi,
I am new to all this flashing etc . . . Anyway, i have installed Android 2.1 and followed all the neccessary steps. However, when i power my phone on it goes through 3 boot up screens then hangs on a black screen saying HTC, it has been like this for 20 minutes.
Should it take this logn and i am over reacting, or is there something else i need to do?
Cheers
Dan
dcorker said:
Hi,
I am new to all this flashing etc . . . Anyway, i have installed Android 2.1 and followed all the neccessary steps. However, when i power my phone on it goes through 3 boot up screens then hangs on a black screen saying HTC, it has been like this for 20 minutes.
Should it take this logn and i am over reacting, or is there something else i need to do?
Cheers
Dan
Click to expand...
Click to collapse
if it really has been 20 mins or more, then take the battery out (and back in) and reboot and see if that works.
Then get back to us on what happens.
Hi, thanks for the quick reply, i ahve tried what you said 3 times, and no luck, this time it has been hanging about 9 minutes.
Open ddms (if the android tools is in your path), and/or post a logcat
What ROM did you try installing?
Im installing Villain 5.2.
And the rest of what you said comletely boggled my mind, i didnt understand a word of it lol.
I have just wiped and reinstalled the ROM, i have powered it on, currently been hanging 2 minutes.
Have you tried booting without the memory card in?
paulrgod said:
Have you tried booting without the memory card in?
Click to expand...
Click to collapse
yes try this one!
Did you remember to wipe the device before you applied the rom ?
etherez said:
Did you remember to wipe the device before you applied the rom ?
Click to expand...
Click to collapse
Probably not...
Try that and get back to us.
Thanks for your help guys, i didnt wipe.!!!
All fix now haha
No problem
Ok so my GF's incredible was working just fine, had been with the same rom for a month with no problems.
One hour ago, it just rebooted out of nowhere. Now, it wont boot to rom, it boots to hboot, try recovery and it shows CWM for 1 second and reboots again, tried factory reset, or clear storage, and it reboots and the same as CWM, it shows 1 second and reboots.
It seems like if everytime it loads the kernel, any kernel, recovery or rom one it reboots.
Any thoughts? Oh, also, I flashed the "build-3.26.605.1-release-152016-baseband-2.15.00.07.28-hboot-0.92.0000_PB31IMG.zip" file it flashed fine, rebooted and again with the bootloop. It just shows the white Incredible screen and reboots!
Any suggestions are appriciated
pmcnano said:
Ok so my GF's incredible was working just fine, had been with the same rom for a month with no problems.
One hour ago, it just rebooted out of nowhere. Now, it wont boot to rom, it boots to hboot, try recovery and it shows CWM for 1 second and reboots again, tried factory reset, or clear storage, and it reboots and the same as CWM, it shows 1 second and reboots.
It seems like if everytime it loads the kernel, any kernel, recovery or rom one it reboots.
Any thoughts? Oh, also, I flashed the "build-3.26.605.1-release-152016-baseband-2.15.00.07.28-hboot-0.92.0000_PB31IMG.zip" file it flashed fine, rebooted and again with the bootloop. It just shows the white Incredible screen and reboots!
Any suggestions are appriciated
Click to expand...
Click to collapse
when you say it shows the white screen and it reboots..... what do you mean be the white splash screen always shows up first then it boots.... are you saying it bootloops [which means it starts the whole process over again]? and im asuming you flashed an RUU Through hboot..... how long did you let it try and boot because it takes awhile after flashing back to stock...... give me a liittl more info and i might be able to help.....
Yea the white splash screen that always shows up. IT reboots and it goes to the white splash screen again, and again...In fact wait me a second i will take a video of everything! But, yea after flashing the RUU it does exactly the same, in fact I just flashed the RUU again via fastboot and the same. I will record it anyway, one second.
Lol, and on my evo Qik is force closing, nice! Well, Sorry couldnt record but yea,
normalboot-->white inc screen-->black screen--->reboot
voldownboot---hboot--->recovery--->recovery screen --1sec-->reboot
I'd try to RUU back to stock and re-root.
Sent from my ADR6300 using XDA Premium App
like I said, done the RUU didnt work. !
pmcnano said:
Yea the white splash screen that always shows up. IT reboots and it goes to the white splash screen again, and again...In fact wait me a second i will take a video of everything! But, yea after flashing the RUU it does exactly the same, in fact I just flashed the RUU again via fastboot and the same. I will record it anyway, one second.
Lol, and on my evo Qik is force closing, nice! Well, Sorry couldnt record but yea,
normalboot-->white inc screen-->black screen--->reboot
voldownboot---hboot--->recovery--->recovery screen --1sec-->reboot
Click to expand...
Click to collapse
are you positive the ruu flashed..... when it loaded up did it ask you if you want to update vol + and then it flashes stuff for about 5 mins until it finialy says its done and asks you if you want to reboot....
yep! I did, I even flashed it via fastboot again, same thing happens :S
pmcnano said:
yep! I did, I even flashed it via fastboot again, same thing happens :S
Click to expand...
Click to collapse
Bro it sounds like hardware problem to me.... the only other thing i can think of is to try and get into recovery with adb and try to wipe do a wipe and see what happens.... but if that dont work doug piston is the best around at getting the incredible restored ill give you link to his site if you cant get him tonight he'll answer in the morning
http://dougpiston.com/
you can also talk to him at Droid Forums good luck let me know what it was please and hit that thanks button if i helped
haha yes you did, I really think its a HW problem too
Hey bro let me know what you figure out so I can help people in the future
Sent from my Incredible using XDA App
Ok, finally had a chance to actually read your thread. Looks like you've tried just about everything I suggested via twitter already.
Oddly enough I had someone from this forum contact me about a similar situation about a week ago. If I remember correctly we tried everything and came to the same reboot. He fixed it though we weren't sure on the full solution show I'll discribe what he did and you can give it a shot.
Flash the RUU through Hboot one more time, once it is complete it will ask if you would like to reboot, select no. Once it gets back into hboot pull the battery wait a minute and re-insert the battery leave the device plugged in and powered off for about an hour. Come back and try to reboot.
Like I said I have no clue on how this method recovered the device but it did. It makes no logical sense to me but its worth a shot.
Thanks for all your help doug, Will try in a sec, was playing soccer!
Will let you know from twitter
doug piston said:
Ok, finally had a chance to actually read your thread. Looks like you've tried just about everything I suggested via twitter already.
Oddly enough I had someone from this forum contact me about a similar situation about a week ago. If I remember correctly we tried everything and came to the same reboot. He fixed it though we weren't sure on the full solution show I'll discribe what he did and you can give it a shot.
Flash the RUU through Hboot one more time, once it is complete it will ask if you would like to reboot, select no. Once it gets back into hboot pull the battery wait a minute and re-insert the battery leave the device plugged in and powered off for about an hour. Come back and try to reboot.
Like I said I have no clue on how this method recovered the device but it did. It makes no logical sense to me but its worth a shot.
Click to expand...
Click to collapse
Stuck in a similiar situation. I tried the above instruction and the device booted. I still do not have a working recovery .Tried to root several times but my device will only boot cleanly once and I have to pull the battery and wait atleast ten minutes but nothing works where can I find instructions on wiping thru adb
I think that the nand is ****ed up or i dont know D: mine didnt boot
I tried flashing my phone to this ROM
http://forum.xda-developers.com/showthread.php?t=1246682
and after the clockwork part, I rebooted my phone and then the part where it seems that the ROM i flashed is loading, my phone hanged-up(animation stopped), after a few minutes of observing it. I removed the battery and tried to boot-up my phone again. I have also tried plugging it to my wall charger to see if it's responding.. the problem now is it's not booting up or anything as if it's dead I think it's now Bricked
also, I think it's because I did not do a Full /data /cache wipe
need help ASAP. Thanks in advance
Are you able to get into your hboot or recovery? If not hope you know someone with jtag
Sent from my HTC Vision using xda premium
You should boot into hboot by pulling the battery, reinserting it, and holding the volume up key and power buttonat the same time. From there you cna access clockworkmod recovery by clicking on recovery. From there you have a few options. 1) You can restore from a backup if you made one. 2) You can reflash the rom. 3) You can install a different rom. Please let me know if you get it unbricked. I assure you i can help.
Sent from my HTC Desire Z using xda premium
l337m45732 said:
You should ..
Click to expand...
Click to collapse
Yery good advice, just one remark:
Booting into HBOOT is <Volume Down> and <Power>
Catherall
P.S. The thread for flashing the ROM advices:
Warnings - must read:
1) ....
2) Full /data /cache wipe is mandatory before moving to EliteMod, even from CM7! Not kidding!
...
catherall said:
Yery good advice, just one remark:
Booting into HBOOT is <Volume Down> and <Power>
Catherall
P.S. The thread for flashing the ROM advices:
Warnings - must read:
1) ....
2) Full /data /cache wipe is mandatory before moving to EliteMod, even from CM7! Not kidding!
...
Click to expand...
Click to collapse
Yea, I wish people would read.. sigh... though even without a data wipe im pretty sure a brick is highly unlikely
How long did you actually wait before pulling the battery? Sometimes it can take up to 5, 10 minutes to fully boot up depending on the rom.
Check if phone is booting after ROM installation
tarroyo said:
How long did you actually wait before pulling the battery? Sometimes it can take up to 5, 10 minutes to fully boot up depending on the rom.
Click to expand...
Click to collapse
It really depends on the ROM. A small ROM like CyanogenMod 7.1 boots up in about 1 minute on my HTC Desire S.
Installation of CyanogenMod 9 with some modifications needed about 10 minutes.
However, you can check if you phone is still doing something using adb logcat.
I assume that you know how to use adb on your computer. Connect your phone before you boot the first time after installing a new ROM.
Boot the phone and wait until the kernel has mounted system and passed control to the Android system contained in the ROM. That takes about 10 seconds.
Then use the commandadb logcat to see what your phone is doing.
More verbose logcat is returned using adb logcat *:V
As long as logcat returns something you phone is booting. Even similar looking entries can be different, just be patient.
As your phone is booting it is establishing new processes.
As soon as the phone's sh (shell) is available you can connect to it using:
adb shell
Then get a list of currently running processes, that is updated every 10 seconds, with the following command:
while :; do clear; ps; sleep 10; done
Best regards,
Catherall
Hello folks,
this morning i wanted to check the watch on my phone and noticed it was very slow. As i am on a cm 11 nightly, i decided to reboot.
The phone shut down correctly but didnt come up afterwards, the screen stayed black. About 4 minutes later, the "HTC quietly brilliant" logo appears. About another 1-2 min. the cyanogenmod boot screen appears. I can repeat that behaviour every time. same with boot to recovery or fastboot. After booting up completely, the phone usage appears to be normal excep the display brightness sensor is not working automatically.
Please note that i am on the same nightly for about 10 days now without any issues except a few reboots. I didn't change anything in the last days, same setup, same usage.
I wiped the caches, installed newest nightly, nothing changed. i cant logcat during boot because adb devices says no device attached.
does anybody has any idea what i can do? i am afraid it seems to be some kind of hardware failure...?
regards,
In fastboot use
Fastboot erase cache
and also backup apps and messages and wipe everything expect battery stats and sd card I had that problem too
big noob said:
In fastboot use
Fastboot erase cache
and also backup apps and messages and wipe everything expect battery stats and sd card I had that problem too
Click to expand...
Click to collapse
Thanks for your answer. Unfortunately, as i anticipated, it did not work. I factory resetted the phone and erased all caches (not via fastboot but cwm, i guess it does the same).
I don't think it is a ROM problem as there are no issues when android is booting but at the, i will call it POST (the htc quietly brilliant logo )of the phone.
I think the proximity sensor/brightness sensor is defective and the phone recognizes it during the "POST" and runs in some kind of timeout and then starts booting.
Can somebody confirm a phone does have something like a hardware check before booting the OS?
Kind regards,
two_handed said:
Thanks for your answer. Unfortunately, as i anticipated, it did not work. I factory resetted the phone and erased all caches (not via fastboot but cwm, i guess it does the same).
I don't think it is a ROM problem as there are no issues when android is booting but at the, i will call it POST (the htc quietly brilliant logo )of the phone.
I think the proximity sensor/brightness sensor is defective and the phone recognizes it during the "POST" and runs in some kind of timeout and then starts booting.
Can somebody confirm a phone does have something like a hardware check before booting the OS?
Kind regards,
Click to expand...
Click to collapse
Are you tryed with diferent rom? I think it is not a problem if your prox sensor not working!!!
Thant said:
Are you tryed with diferent rom? I think it is not a problem if your prox sensor not working!!!
Click to expand...
Click to collapse
No, i did not try a different ROM. Why should i? it worked with CM11 before without any issues...
two_handed said:
No, i did not try a different ROM. Why should i? it worked with CM11 before without any issues...
Click to expand...
Click to collapse
Obviously, it is ROM's problem. Because it is nightly. Although I have installed nightly too, one from 23 feb. And I have no problems. By the way, snapshot built l built is released now and I'm gonna try it today.
Sent from my One X using xda app-developers app
Timofey_K said:
Obviously, it is ROM's problem. Because it is nightly. Although I have installed nightly too, one from 23 feb. And I have no problems. By the way, snapshot built l built is released now and I'm gonna try it today.
Sent from my One X using xda app-developers app
Click to expand...
Click to collapse
Still i really don't think it is a ROM problem. I just noticed that the phone even in fastboot behaves REALLY slow (changing the menu with volume buttons takes 1-2 minutes). And fastboot definately is independent from the ROM.
Anyways, i am just downloading CM 10.2 stable realease and flash it just to be sure.
Yep, as i thougth, still black screen for 4 minutes until the HTC quietly brilliant logo appears.
Guess it's faulty hardware then... Would be nice if someone could confirm my assumption that there is some kind of POST before the ROM is loaded.
regards
two_handed said:
Yep, as i thougth, still black screen for 4 minutes until the HTC quietly brilliant logo appears.
Guess it's faulty hardware then... Would be nice if someone could confirm my assumption that there is some kind of POST before the ROM is loaded.
regards
Click to expand...
Click to collapse
Try to flash sense rom like ARHD it is close to stock and see what will heppend then if it is the same it is hardware if not is problem it CM
hi all and happy new year. im having trouble getting my sisters phone to boot up it wont boot past htc one screen. I have tried wipping cache and factory reset in stock recovery it goes to android is upgrading but when it gets to finishing boot it hangs there constantly. I an a sony man so have no experiance with htc. I have read a few threads and am still unsure about the prosess of flashing stock. It is stocked and locked and a uk device any help would be apreciated thanks
gavster26 said:
hi all and happy new year. im having trouble getting my sisters phone to boot up it wont boot past htc one screen. I have tried wipping cache and factory reset in stock recovery it goes to android is upgrading but when it gets to finishing boot it hangs there constantly. I an a sony man so have no experiance with htc. I have read a few threads and am still unsure about the prosess of flashing stock. It is stocked and locked and a uk device any help would be apreciated thanks
Click to expand...
Click to collapse
Post the output of fastboot getvar all after removing serialno and imei
Someone will guide you with those info
Sent from my HTC M8 using XDA Labs
ahmed.ismael said:
Post the output of fastboot getvar all after removing serialno and imei
Someone will guide you with those info
Sent from my HTC M8 using XDA Labs
Click to expand...
Click to collapse
Here it is
gavster26 said:
Here it is
Click to expand...
Click to collapse
i didn't see any RUU for your device ( maybe there is but i didn't see it )
You can restore a stock TWRP backup from this thread
https://forum.xda-developers.com/htc-one-m8/help/tutorial-how-to-stock-stock-twrp-t3086860
choose by version main ( 6.13.206.5 ) from post #3 and follow the instruction from OP
Sent from my HTC M8 using XDA Labs
gavster26 said:
Here it is
Click to expand...
Click to collapse
You have to wait a long time for bootup. Even after white HTC screen which can take a few minutes, it will optimise 165 or so apps on MM 6.0, and 265 or so in Lollipop 5.0, depending what you have. Try going away for a half hour while it boots.
Another thing you might try is when it goes on hanging in the 'finishing boot' for a long time so that you think it has completed optimizing of the apps, (wait 20 minutes some apps take minutes to optimize, and there are as I said over 160 at least) , turn it off again by holding the power button for 15-30 seconds or however long it takes to get it to power off. Then restart again it may come on.
*if the power off alone doesnt shut it off, power off+vol down should.
Can the bootloader is locked bro so don't think that would work
kruc Ire said:
You have to wait a long time for bootup. Even after white HTC screen which can take a few minutes, it will optimise 165 or so apps on MM 6.0, and 265 or so in Lollipop 5.0, depending what you have. Try going away for a half hour while it boots.
Another thing you might try is when it goes on hanging in the 'finishing boot' for a long time so that you think it has completed optimizing of the apps, (wait 20 minutes some apps take minutes to optimize, and there are as I said over 160 at least) , turn it off again by holding the power button for 15-30 seconds or however long it takes to get it to power off. Then restart again it may come on.
*if the power off alone doesnt shut it off, power off+vol down should.
Click to expand...
Click to collapse
Tried all that mate. When I hard reboot it (power vol+) it stays stuck at htc one screen left it for 30min or so and still no boot. I tried to logcat while its booting but it won't logcat either. I really need the stock rom but unable to find it I have tried a few zips but got error wrong footer
You need a ruu but unfortunately ruu is not available (afaik).
Worth a try ... flash htc signed firmware fw_6.13.206.5 that you can get from same link above on post #5.
Most important is too see whether the firmware can be successfully installed with no error. If there is error, I'm afraid that will be hardware.
ckpv5 said:
You need a ruu but unfortunately ruu is not available (afaik).
Worth a try ... flash htc signed firmware fw_6.13.206.5 that you can get from same link above on post #5.
Most important is too see whether the firmware can be successfully installed with no error. If there is error, I'm afraid that will be hardware.
Click to expand...
Click to collapse
which link mate. can the boot loader be unlock in this state
Link on post #4 above or directly here : https://forum.xda-developers.com/showpost.php?p=60218734&postcount=5
Not so sure whether can be unlocked but you can try.
You need to get the unlock code from www.htcdev.com to unlock bootloader.
Good luck and good night .. gotta go now.