Develop Bugs

[Q] Desire Z doesnt boot even in a recovery

After full discharging my htc dz doesnt boot up.
1) when i'm trying normal boot it turns off after 3 seconds, when i see htc logo.
2) when i'm trying to get in recovery - it's turns off after 3 seconds.
3) when i'm in fastboot - it seems to work ok.
i've triend to re-flash hboot and recovery, now i can boot in recovery, but device still turn's off after 1 second in recovery mode.
any suggestions how can i fix it?

...i started a thread in the general section, with things you could try if you stuck at htc screen. Have a look, maybe one of this options work for you.
Sent from my HTC Desire Z using XDA App

I would plug it in to charge while switched off, and leave it to charge for several hours before trying to boot it up.
Sent from my Desire Z running CM7.

steviewevie said:
I would plug it in to charge while switched off, and leave it to charge for several hours before trying to boot it up.
Sent from my Desire Z running CM7.
Click to expand...
Click to collapse
it doesnt helped.

[Q] Phone stuck on boot collective rom

First off a little background I downloaded and installed the collective rom from the dev section earlier today and was absolutely loving it. I went into the over the air settings, and downloaded the avengers theme bc I thought it would make a cool edition to show my nephew ( loves the avengers) upon rebooting after successfully flashing I get the avengers A boot logo but it just sits there flashing, and the phone never boots. After waiting a solid 15 minutes for it to boot I held down the power button to power down the phone, and now I can not get it into recovery to reinstall the rom, or install a backup that I made. Clockwork will not come up for some reason, and whenever I try to boot the phone again it gets stuck on the avengers A??? What should I do? What did I do wrong? Thanks in advance
P.S. whenever I plug the phone in it does bring up the battery icon that shows that it is charging, and it will also allow me into download mode.
-Garrett

hino8229 said:
First off a little background I downloaded and installed the collective rom from the dev section earlier today and was absolutely loving it. I went into the over the air settings, and downloaded the avengers theme bc I thought it would make a cool edition to show my nephew ( loves the avengers) upon rebooting after successfully flashing I get the avengers A boot logo but it just sits there flashing, and the phone never boots. After waiting a solid 15 minutes for it to boot I held down the power button to power down the phone, and now I can not get it into recovery to reinstall the rom, or install a backup that I made. Clockwork will not come up for some reason, and whenever I try to boot the phone again it gets stuck on the avengers A??? What should I do? What did I do wrong? Thanks in advance
P.S. whenever I plug the phone in it does bring up the battery icon that shows that it is charging, and it will also allow me into download mode.
-Garrett[/QUOTEf
that is rather wierd. i also use the collective rom its great! but was the avengers theme a flashable theme? or one from theme choooser... if it was flashabble are you sure you did it to the right device.. honestly if i were you and there were no way going into recovery i would unroot and reroot and install ur custom recovery again and restore ur collective rom before this problem happened...
Click to expand...
Click to collapse

Thank you for the quick response. Yes I am sure it was a flashable theme, if you are running the collective rom and go to the over the air settings there are themes you can download, and the instructions just say to reboot into recovery, flash the theme, then reboot. after doing that I am now experiencing these problems.
A little more info. Sorry bear with me I'm a noob. whenever I try to reboot (not recovery) it says samsung first then it say samsung galaxy s3 like normal then the next screen is the avengers A and this is where it gets stuck. When I try to reboot into recovery all i get is the first black screen with samsung and then after that the phone turns off and the battery icon comes back up. I don't get the second samsung galaxy s3 screen where you are supposed to release the power button, it just dies and goes to the battery logo.

hino8229 said:
Thank you for the quick response. Yes I am sure it was a flashable theme, if you are running the collective rom and go to the over the air settings there are themes you can download, and the instructions just say to reboot into recovery, flash the theme, then reboot. after doing that I am now experiencing these problems.
A little more info. Sorry bear with me I'm a noob. whenever I try to reboot (not recovery) it says samsung first then it say samsung galaxy s3 like normal then the next screen is the avengers A and this is where it gets stuck. When I try to reboot into recovery all i get is the first black screen with samsung and then after that the phone turns off and the battery icon comes back up. I don't get the second samsung galaxy s3 screen where you are supposed to release the power button, it just dies and goes to the battery logo.
Click to expand...
Click to collapse
Since you can go to download mode i assume odin should still recognize your device. If I were you I'd odin unroot...reroot....restore your old collective rom...cuz u wanna stay orange

[Q] Can't access my phone after failed ROM update

Hi Guys
So, not so long ago I got my first Android phone, after i just bought nexus 7 and fell completely head over heels in love with this OS.
so when i got my HTC One V and saw the OS i was pretty disapointed, and decided to update the ROM.
i used this "w.w.w.android.gs/update-gsm-htc-one-v-aokp-jelly-bean" guide and everything went fine, until i rebooted to recovery.
Then i get this image of my phone and 2 green arrows pointing in a circle (didn't know how to say this ) and then that disappears and another screen with an image of a phone, and a red triangle and an exclamation mark inside of the triangle. and then the phone rebooted and showed the white HTC screen and red text underneath saying "this build belongs to HTC......" and then it resets but always shows the same screen.
I tried doing a Factory reset in Bootloader, but it always shows that HTC screen and red text.
i don't know what to do, i hope you guys have some answers, i certainly don't

This happened to me before too.. try to turn it on. If you made a backup like your supposed to and haven't flashed a kernal hold power until it stops blinking then hold vol down and then go into recovery and wipe data/facreset and wipe cache/dalvik and then install your backup and reboot.
Sent from my HTC One V using xda app-developers app
---------- Post added at 03:42 AM ---------- Previous post was at 03:36 AM ----------
I think it was because you don't have a recovery. I don't think you flashed it properly try again. That was my problem :thumbup:
I think
Sent from my HTC One V using xda app-developers app

Krizzikagl said:
Hi Guys
So, not so long ago I got my first Android phone, after i just bought nexus 7 and fell completely head over heels in love with this OS.
so when i got my HTC One V and saw the OS i was pretty disapointed, and decided to update the ROM.
i used this "w.w.w.android.gs/update-gsm-htc-one-v-aokp-jelly-bean" guide and everything went fine, until i rebooted to recovery.
Then i get this image of my phone and 2 green arrows pointing in a circle (didn't know how to say this ) and then that disappears and another screen with an image of a phone, and a red triangle and an exclamation mark inside of the triangle. and then the phone rebooted and showed the white HTC screen and red text underneath saying "this build belongs to HTC......" and then it resets but always shows the same screen.
I tried doing a Factory reset in Bootloader, but it always shows that HTC screen and red text.
i don't know what to do, i hope you guys have some answers, i certainly don't
Click to expand...
Click to collapse
when the red triangle appears with exclamation mark hold the volume up button with the power button ...................if u can get through than hit thanks....

Please ask all questions in Q&A. Thread moved there.

Dude u have not flashed a Custom recovery.... after the red triangle appears, press vol up+ power then u will enter stock recovery...u need to flash a custom recovery like Clockworkmod...the screen with red letters is normal...it shows that u are entering the recovery....or that u have flashed custom firmware or a custom kernel...hope i helped...
Sent from my One V using xda app-developers app

update
okay guys, i installed cwm 6.0.1.5 and tried it again, and everything went fine.but after the reboot, the screen goes black, and then just shows the white HTC screen and red text, and then just goes black again, and then White HTC screen and keeps switching i've been without a phone for 2 days now, and it's killing me

Krizzikagl said:
okay guys, i installed cwm 6.0.1.5 and tried it again, and everything went fine.but after the reboot, the screen goes black, and then just shows the white HTC screen and red text, and then just goes black again, and then White HTC screen and keeps switching i've been without a phone for 2 days now, and it's killing me
Click to expand...
Click to collapse
download a cm10 primou ROM/gapps/ to your sd card then downlad the boot.IMG on your computer. Go into recovery andflash gapps and the ROM.. then hold power and when it goes off hold down and you should go into boot loader. Then select fast boot. Go onto your computer and go to the cmd prmpt and type fastboot flash boot boot.IMG and them reboot. Depending on the kernel/boot.IMG you may need to flash the zip for it too.
Sent from my HTC One V using xda app-developers app

thanks guys
Thank you XxlemonxX i gave up on that AOKP build, and went for CM10 just finished flashing it as you posted this
now everything works as planned, I'm such a sucker for Jelly Bean

Krizzikagl said:
Thank you XxlemonxX i gave up on that AOKP build, and went for CM10 just finished flashing it as you posted this
now everything works as planned, I'm such a sucker for Jelly Bean
Click to expand...
Click to collapse
Welcome glad I could help
Sent from my HTC One V using xda app-developers app

[Q] SG3 T999 boot logo, but blank after that

My T-Mobile SG3 T999 has a blank/black screen after the "Samsung Galaxy S3" boot logo pops up. This happened after messing around on Pimp my Rom and I rebooted to implement some tweaks. Consequently the result mentioned now occurs. I can however get it into download mode and factory reset mode, so I know it's not completely gone. I tried to simply reflash my root software or whatever, that I had successfully done. It went through Odin and said pass, but still I have the black screen. Is there any advice for this situation? I am hoping to have more options or perhaps a guide for unbricking. I am downloading the stock rom for my phone, and will try to flash that, but I'm not really sure how that would fix it.
Any help would be very much appreciated!!

Can you boot into recovery? (Take battery put of phone, put battery back in, hold volume up, home button and power button until you feel the phone vibrate and you see blue text)
Does cwm show up (grey background) or stock recovery (black background)?
Sent from my SGH-T999 using XDA Premium 4 mobile app

Boot stock recovery AFTER Odin flash and factory reset. Then try again.
Sent from my SCH-I535 using Tapatalk 4

Recent Unroot back to Stock Lolipop first boot

So I unrooted my 5.02 and relocked the bootloader. I've been waiting for the first boot for about 10 mins now. It is on the mulit-colored dots swirling around the center of the screen (I guess the boot animation).
Anyone know how long the first boot is supposed to take?

It always takes ages first boot

tonyt3rry said:
It always takes ages first boot
Click to expand...
Click to collapse
Thanks. It finally got going.
Sent from my HTC One_M8 using XDA Free mobile app

I've thought the exact same thing and times and reset it loads of times then forgot to and come back to a nice welcome boot

Why did you relock the bootloader? It serves no purpose other than to wipe all your data when you want root again.