Hi,
I unlocked original htc bootloader from htcdev and it went through fine without any issues (I didn't root). Later i downloaded trickdroid v3.0 & tweak pkgs from http://trickdroid.org/category/desire-hd/ and followed the instructions listed there. In the first attempt i installed rom, but without rebooting into new rom i applied tweak as well and then rebooted. I just got white screen with htc logo and it remained there for quite some time. Sensing i might have done something wrong i booted into recovery, wiped data/cache, reinstalled rom again and rebooted (without applying the tweak pkg). However even in this case all i see is white screen with logo and it's been like this for more than 20 mins.
My question therefore is - is this normal for it to be in this mode for such a long time, how long it usually takes to finish?
My concern - did i brick my phone and is there any way i can flash another rom that might work or go back to stock to be on the safe side.
Any help/advice highly appreciated. Hoping someone can help me out.
Thanks in advance.
Related
Hi guys, reasonable newbie here. My Galaxy S2 has stopped displaying anything after the initial logo. In fact it seems to turn the phone off as you can make repeated attempts to boot it within a few seconds.
I started by flashing an insecure sgs2 kernel from this site with odin, then used s2root.
I then played around with rom managed but found it wouldn't boot into clockworkmod (orange exclamation mark in a white triangle every time) I booted into it manually and started trying to flash cm7 which I had downloaded earlier.
I wiped the data etc and flashed the cm7 zip (plus the google apps zip). Rebooted and got into cm7 with everything seeming fine.
Next I thought I should probably flash back to the stock version of the insecure kernel. I rebooted the phone but got distracted and didn't start it up in download mode, I looked just in time to see the normal logo (with the yellow insecure triangle) and then nothing....just blank.
I tried rebooting afew times and nothing, even after yanking the battery. Then I tried getting back into clockworkmod to reflash cm7. Nope, same thing happens.
I can still get back into download mode but nothing I flash makes the slighest difference. Tried reflashing clockworkmod, insecure and stock kernels of various versions but I'm stuck.
This is almost a new phone and I can't believe I've already killed it I would be so grateful for any tips, I've included as much info as I can think of from the top of my head but I will do my best to answer anything you gurus might need.
Again, very grateful for any help...I don't want to have to explain to Orange how I've managed to brick this after 4 days
Ok after trying over and over again to get into recovery mode, it booted into the original (3e) recovery. I've just flash cwmod to it again and have just flash cm7.
After reading some posts about cyanogenmod sometimes not flashing correctly first time, I did it twice (and it did indeed take longer the second time) and twice for google apps.
Next I'll try to get back to the stock kernel. This is where it went wrong before but i'll cross my fingers.
Edit: Well, multiple reboots didn't cause a problem but flashing the stock kernel back does kill the handset again. I'm sure this stuff is all obvious to those with experience I guess I'll have to sit with an insecure kernel and the yellow triangle for the forseeable future. On a side note, s2root doesn't see the phone connected with cm7 (yes usb debugging was turned on). I'm hoping that it is pre-rooted but I haven't tested that yet.
Hi,
I will prefix this (as there are a few people around with this problem who can get into recovery mode) with the fact that holding down Vol- on boot is not getting me to the recovery / bootloader screen.
I have a rooted HTC Desire S (rooted it nearly a year ago, so info about the hboot etc is a distant memory).
Anyhoo, I decided to have a play about with one of the ICS roms but it was a bit buggy and the camera drivers still aren't working for video so I decided to go back to Endymion V3.4 - http://forum.xda-developers.com/showthread.php?t=1310845
I did a full wipe, installed base rom, installed optional addons and then upgraded to 3.4 - booted fine into the OS so set about getting my system set up the way I like it.
I noticed that endy came with a theme installer so clicked on one of them to have a look, it asked for root, said it was installed and would need to reboot to take effect...
SO
the problem is, it now won't boot and is stuck on the white HTC boot screen.
Holding vol+/- and power buttons reset it but it just ends up back hanging on the boot screen.
Have tried pulling battery and trying again.
Holding Volume Down when powering up is no longer doing anything
So, I either need a saviour to point me in the direction of a fix.. or a kindly sould to break it to me gently when they tell me my phone has gone to the USB Dock in the sky..
Any help will be greatly appreciated.
Thanks
update:
After pulling battery again, pulling out sim and sd cards, booting with vol- held down, i got into recovery. Am going to try and flash a different rom after doing a full wipe, I'll update once it's done but any insights in the meanwhile will still be appreciated
Sorted, cleared the thing out, stuck reaper CM rom on it, rebooted and everything is peachy for now.
Thanks me
Curious if anyone knows why this might have happened?
because you didnt flash the addon zip which was released alongside endymon and then tried to use the addons,it does say on the screen do not use these unless you have installed the addons
I've had my phone rooted with CM10.1 since I got it back in December and last week I was messing around with the new nightlies but because of the all the constant reboots and freezes I decided to go back to an earlier verson of CM10.1.
Now my phone will not boot up and stays in the CM loading screen, I tried to get into recovery but I just feel a vibration and the screen stays dark although sometimes it just goes straight to the boot screen and then stays there.
Have I messed up my phone permanently? Any help will be greatly appreciated (I'm desperate). Thank you very much
Edit: I can get into Odin.
Edit2: After a lot of trial and error I managed to get into recovery, wiped data and reflashed CM, thankfully it worked. Although no one responded thank you.
this is my first htc and so far i am missing my samsung and motos
the phone is now completely non responsive and is stalled at the HTC boot screen with the text "this build is for development purposes only " i have the verizon htc one m8 ive tried removing the sd and sim holding power holding volume and power nothing makes a difference.
rooted with s off twrp is my custom recovery
started by putting slimrom on for a change of pace i had horrible signal strength and decided to try another rom somewhere in the process of flashing venom one my sd lost its backups the phone had stayed on the same screen for a while but eventually booted to a stable seeming venom rom and had 3g but no 4g service i ended up rebooting the phone today around 11 am and its been in this loop / screen since. i let the battery die down and was able to get to recovery and searched for my back ups but they were gone i ended up rebooting and now am stuck on the same screen as before. even after trying to enter recovery twrp it goes back to htc and not twrp
i tried every combination of buttons the few times and have drained the battery twice and now it just boots to this screen and is non responsive. hope that i can manage to find a way to push something to it or enter recovery and go back to stock using ruu's
anyone with input or advice would be a blessing at this point id be happy to make a donation for any useful help / anything to get me out of this screen even so i can push another rom or ruu to get me to stock
im afraid ive ruined a perfectly awesome phone
update got back to twrp and tried to re flash the venom one rom after full wipe but used their option for "stock" install said 100% and sucessful but upon the reboot is now seems to be stuck in the same screen.
got into the recover after battery died re flashed venom
after about 15 minutes on the htc screen it went to set up ....still very buggy more so than last time the phone was actually working but it is at least from what i can tell working ... going to try to get back to square one somehow
screen wont turn on and acts very buggy only time it stays on is holding power and gives reboot options... i done f ' ed this phone up.
How long are you waiting after I restarts when the install is finished? It will take a long time on that first boot. I have seen them take more than 5 minutes and if you interrupt it it can cause problems.
I've had some previous experience with custom roms on my old Nexus 6P and thought I would try the same for my mate 9. Unfortunately I've discovered the Mate 9 is not as easy to install custom roms as I thought.
I've tried several things throughout the day and I feel I've accidently overwritten things I shouldn't have but can't remember everything I've done.
It is an Optus branded phone so I believe at the start of the day I had some version of L09C34. I currently have an unlocked boot loader and TWRP installed and would like to flash back to the stock firmware, but seem to be unable to do so. The boot loader is unlocked and when I try flashing extracted parts from fastboot, the phone will reboot, reboot again and sit at erecovery. Unfortunately while I can connect to wifi, no packages are found for recovery.
Additionally I now get this lovely colourful screen in lieu of the logo on initial boot.
Any help would be appreciated.
Okay, so I've managed to unbrick it and install a version of L09C432 and get it working again - thank you to various threads on XDA. I think what I noticed was that someone else had tried the C432 firmware on a C33 model and it worked. Without being able to get hold of the C34 firmware, I tried to flash nougat originally and it worked.
This morning, I've noticed I still have an issue where the touchscreen won't work when the phone is cold (i.e I can't click anything and can't turn alarms off). If I reboot the phone to recovery it's fine, so it leads me to believe its an OS thing. Also, if I give it a few minutes in my pocket, or holding my palm on the screen it then responds. This is the issue I tried to resolve by resetting and trying a different rom but seems I haven't been successful.
Finally, when I first turn the phone on and the screen lights up I see a green background with one blue and one red box. Any ideas what I have messed up there and how to fix it? I'm not too concerned, but it would be a nicety.
Just providing updates in case anyone comes a long with similar issues.
I have now fixed the strange coloured screen on initial power on. I've found the oeminfo for the C432 firmware on another XDA thread and took a backup of what was currently there, restored the C432 version and rebooted. I was presented with the eRecovery and no TWRP. Quick check in fastboot mode showed the phone relocked. I unlocked it again and it booted no issues, however was unsure if the custom rom was still installed as I was presented with the option of an OTA update. Initially my sim card was not recognised, so I had to remove and reinstall it but so far so good.
I've just reflashed my custom rom and will see how I go.
The only potential issue I have outstanding is my touchscreen not working either first thing in the morning, or when the phone is cold - i.e I've gone to the gym and left it sitting in the locker for 2 hours and I can't use the touchscreen when I come back. I can unlock it fine with the finger print reader and the phsyical buttons respond but touches on the screen won't. If the phone is left alone for a few minutes the screen shuts off and turns back on approx every 5 seconds until it becomes responsive. Has anyone seen anything like this before? My googling hasn't lead me to anything helpful.