Stuck on HTC quietly brilliant screen. Help Please - Hero, G2 Touch Q&A, Help & Troubleshooting

My hero wasnt being recognised by my computer via usb, so i searched the internet for a fix, and it was suggested that i press back and home, and then the power button. This wiped something, not entirely sure what, but now all it does it get stuck at the quietly brilliant screen
Any ideas on how to fix this?

This same thing happened to me when I installed a ROM but forgot to wipe phone or whatever first.

I am not specialist and better dont listen to me.I have my phone for about a week now and i just did my first rooting and ROMing,but i think that its some corrupted data between cache and new ROM.If its so,you have nothing to worry about.Go Safe Boot and then go wipe->wipe cache or something like that.But again i say you better wait for more xped users to answer.I don't wanna cause you more trouble.

go to recovery menu, go through all wipe options available, then flash the rom again, then reboot. if it still doesn't work try booting without your sdcard inserted.

Yaaaaay, its working again, i just did a wipe of the sd: ext and it worked
Thanks!
Another point, does anyone know how to fix usb device not recognised?

Related

[Q] Stuck in Boot screen!

Im going to lose my mind! I've searched and read and found no real answer..... Is there anyway that I can get my phone out of the boot screen?
Ive downloaded and rooted before and never had a prblm! I download this certain Rom Lastnight and all of a sudden my phone is stuck on the boot screen! I've tried everything i can with it and no luck. Does anyone have some type of info on what i can do or is there no hope for my poor lil droid?
Please let me know!
Thanx in advance!
Have you tried a battery pull? Pop that out and back in, reboot into recovery and restore your nandroid back up. Should be fine from there...
What I do when this happens to me is pull the battery, wipe my phone, re-apply the rom, then reboot.
-If that does not work, then revert back to your nand backup.
Thanks for the ideas but I tried both of those actions first and got nothing in return. This sukks! I even tried to go back and load the PB00img zip tha i had and no go. I'm guessing that i Bricked this dam Phone!
Back to the Blackberry! Damn!
Do you think its possible that i can load a new Rom and try to boot the phone into recovery and flash that zip? The problem seems to be my boot screen! I've seen post with people with similar "situations" <--------lol (not From Jersey shore) and tried those methods and once again nothing.
Sucks that you are still having this issue. The next step I can think of would be if you have SDK set up then once it is stuck on the boot screen, run a logcat and post it here so someone that is smarter than I can figure out where you are running into problems at. You'll need to navigate to your SDK/tools folder (in the Command window of course...) and then once there just type in: adb logcat .
This will result in a myriad of crazy computer language stuff. Should be able to tell us something at least.
First, take a deep breath; your phone is not bricked. Far from it in fact.
Second, prove to yourself that it isn't bricked by booting it into the custom recovery:
Power it off, and then hold down Vol-Up (first) and the End (second); keep pressing both buttons until the three skating droids have appeared. The custom recovery menu should pop up about 10-12 seconds after that.
Third, download "some other certain ROM" (I get to be as vague as you are, right?) to your PC, and get it to the root folder of your SD card somehow. Look up "USB-MS toggle Amon_RA" if you don't already know what that is.
Fourth, flash that "some other certain ROM" and prove to yourself that your phone is not bricked, making sure that you perform a "Wipe data/factory reset" first before you flash the ROM.
Then, after you've shown yourself how it is possible to do these steps, go back and try to figure out why the other "certain ROM" doesn't work on it's first boot. Try popping out the SD card before you boot it to see if that is the trouble.
bftb0
@es0tericcha0s, Thanks for the response but instead of doing more harm to the phone i just took it to VZW, (Kinda) Explained what happen and they switched it out no prob.
@bftb0 lol Be as Vague as possible.... I didn't want to say any particular Rom for the simple fact that who ever did the Rom i'm sure worked hard at it, And evevn tho i'm not new at this, it could very possibly be my mistake somewhere in installing it! SO I choose to respect the XDA and The Dev But thanks for your awesome response! (no Sarcasm intended) lol

[Q] Device administrator mode + password problem.

Hi!
I try to tell my lovely story, let's hope someone can help me, because i am in a huge trouble.
Today i installed WIFIunlocker on my device, and unfortunately, i gave access to the device administrator right to the application, plus i set up a password. Using the app i realised this is not that iam looking for, so i decided to remove it. Tryed to uninstall it, but for the first try i got an error, later on i realised that i need to turn off the device administrator mode inside the app, everything is fine, i was able to unintall it. Now the nightmare starts...
After uninstalling the app, locking the screen then unlocking the phone, it asks for password. I was a bit surprised because i just removed the related app. Nvm, i just entered my "password", but it was wrong. Before the uninstall it worked, now, after the uninstall it doesn't. At this point i can't do anything with the phone, because iam stucked on the "password screen".
What i did today:
- started from Litening rom v2.0
- i was hopeless, so wiped data/factory reset, wiped cache + darvik cache, formated system+data+cache
- installed LeoMar v2.5
- After the boot the it still asked for the password, i removed the sim-card, and somehow was able to access the phone, but unfortunately it locked itself, the "password screen" popped up again.
- My last try was flashing stock KG6 rom then later on CF-Root, but now i can't boot the phone into recovery mode. Download still works.
- What happends when i try to boot it to recovery, the Samsung Galaxy S 2 title shows up, but after that immediately asking for the "password". Before this, the phone booted fully / i was able the access the recovery mode.
So my question is, what can i do now? How can i get rid of this "password screen?"
Youtube video
Same problem
But I switched off administrator mode before uninstalled
and i used only one password so it can not be wrong.
I think that the app is a joke or a prank?
DID you managed to fix that?
Well I managed to make my phone the same brick as yours.
What now.
Did g4rb4g3 = Garbage did in purpose?
I think using download mode to restore your efs partition backup will fix this since password and pin info is saved on it.
Volume DOWN + Home + Power.
Do you have a custom recovery?
Wipe everything. All of it. Flash a new rom. How the hell is this impossible to remove? Flashing a rom wipes all crap right? Wth..
---
Edit: Seems the app is known for this bug with many others. Mods should take the app down, it's killing devices, turning them unusable. If the dev can reproduce the problem or if someone smart enough could come up with a fix..
prodygee said:
Volume DOWN + Home + Power.
Do you have a custom recovery?
Wipe everything. All of it. Flash a new rom. How the hell is this impossible to remove? Flashing a rom wipes all crap right? Wth..
Click to expand...
Click to collapse
Wrong the password/pin is on the efs partition which is NEVER touched during flashes or wipes.
Or flash a AOSP rom like cm7 or MIUI since they don't use the efs partition for lock settings.
ANd i fixed it again from the brick
Just go to download mode
flush it with stock
after restart try to go to recovery it will ask you about the password
type anything as many timea as it will tell you that if you will try again it will wipe out your internall sd card
of course try once more it will wipe out your sd card and ask you again for password
type anything again and again and it will warn you again that if you try again it will wipe the internal sd card and after that you will see red info that your pass was changed to NULL
restart
and you are in and all is back to normall
mahatma said:
Well I managed to make my phone the same brick as yours.
What now.
Did g4rb4g3 = Garbage did in purpose?
Click to expand...
Click to collapse
You can blame him same as yourself. This story shows that you need to be really careful when you mess with your phone. This true from the developer side and from the user side. At least we have some information about this for the future and we can help people out.

[Q] Help... Stuck in recovery :(

So here is the deal, i went to flash a new ROM last night. I usually do everything on my phone as my computer does not normally recognize my USB for some reason, but anyways, i tried flashing last night and the flash failed. and i have no back ups nor can i plug in a USB and transfer anything to my "sd" portion of my phone because it does not work. Oh and when i go back to stock (Factory reset), when i try to boot into system. It just shoves me back into recovery mode, someone please help. I'm usually pretty good with this stuff and if i don't know a quick Google search is sufficient. But i have found nothing. This is my last resort.
FYI: I believe it failed because my recovery is an old version, I'm using team win recovery touch. not sure if that changes anything
Dylerium said:
So here is the deal, i went to flash a new ROM last night. I usually do everything on my phone as my computer does not normally recognize my USB for some reason, but anyways, i tried flashing last night and the flash failed. and i have no back ups nor can i plug in a USB and transfer anything to my "sd" portion of my phone because it does not work. Oh and when i go back to stock (Factory reset), when i try to boot into system. It just shoves me back into recovery mode, someone please help. I'm usually pretty good with this stuff and if i don't know a quick Google search is sufficient. But i have found nothing. This is my last resort.
FYI: I believe it failed because my recovery is an old version, I'm using team win recovery touch. not sure if that changes anything
Click to expand...
Click to collapse
Well u need to get something on the phone to flash. I suggest you work on the usb issue or get a micro sd reader.
Well the "sd" card is the integrated one i cant remove. And i have tried fixing the usb but nothings seems to remedy it. Very rarely i can get it to work but it will stop working the next time i try to plug it in. I have a ROM i can flash, but the recovery fails to flash it every single time, even after clean install. im fairly sure its my recovery that wont let me flash the rom but i also cant update that till i figure out how to at least get the phone to a homescreen. I honestly dont know much about odin but it looks like i may be able to try and flash it there, is this correct?

Starting to really hate EVOs, 2 Phones Bricked today

This started when my phone was acting out on Viper 4.0 rom and I figured I'd wipe it and start fresh, wiped the phone & ROM no longer booted, went to the forum to see if there is anything new to tryout & found dirty unicorn so I thought hey that's different (for me) let's give it a shot. Long story short the phone never came back until I relocked & used a factory RUU and it worked but phone was now locked & back to stock. Phone is S-Off by the way.
Today was a new day and I was determined to either get a new rom on my phone or go back to Viper 4.0, unlocked hboot & rooted the phone, installed the newest TWRP 2.8.01 and decided ok everything looks good let's see what happens, Dirty Unicorn requires that you copy ROM to internal storage then flash and this is where the first problem occurred; I couldn't mount internal storage so I thought meh I'll just boot the factory rom & connect as USB storage so I did that, back into recovery and somehow internal storage is not in either file manager or could I get to it from the install screen. I gave up & decided to go ahead & flash from Micro-SD which didn't work, tried to wipe & fail, tried to fix permissions and fail, every time I reboot it asked to reinstall supersu so I tried to flash the most recent zip I had and sure enough fail finally one of my zips worked and I hit reboot, that was the end of my phone.....
Right now - phone is completely blank, power does nothing, power+vol down does nothing, power+vol down+vol up does nothing. When I plug the phone into PC it shows up as QHSUSB_DLOAD RUU doesn't work and fastboot commands return nothing.
ummm what do I do?
oh & the second phone was a friend's phone that he gave up on gave to me to fix for him, of course that's bricked too but I have a feeling it'll come back maybe after the battery dies, haven't tried yet. But I need to get my own phone working so I can be back in business.
Whatever recommendations are welcome
Can't wait to go to Samsung lol this or something similar happens every time I try to switch or upgrade rom.
oceanisbleu said:
This started when my phone was acting out on Viper 4.0 rom and I figured I'd wipe it and start fresh, wiped the phone & ROM no longer booted, went to the forum to see if there is anything new to tryout & found dirty unicorn so I thought hey that's different (for me) let's give it a shot. Long story short the phone never came back until I relocked & used a factory RUU and it worked but phone was now locked & back to stock. Phone is S-Off by the way.
Today was a new day and I was determined to either get a new rom on my phone or go back to Viper 4.0, unlocked hboot & rooted the phone, installed the newest TWRP 2.8.01 and decided ok everything looks good let's see what happens, Dirty Unicorn requires that you copy ROM to internal storage then flash and this is where the first problem occurred; I couldn't mount internal storage so I thought meh I'll just boot the factory rom & connect as USB storage so I did that, back into recovery and somehow internal storage is not in either file manager or could I get to it from the install screen. I gave up & decided to go ahead & flash from Micro-SD which didn't work, tried to wipe & fail, tried to fix permissions and fail, every time I reboot it asked to reinstall supersu so I tried to flash the most recent zip I had and sure enough fail finally one of my zips worked and I hit reboot, that was the end of my phone.....
Right now - phone is completely blank, power does nothing, power+vol down does nothing, power+vol down+vol up does nothing. When I plug the phone into PC it shows up as QHSUSB_DLOAD RUU doesn't work and fastboot commands return nothing.
ummm what do I do?
oh & the second phone was a friend's phone that he gave up on gave to me to fix for him, of course that's bricked too but I have a feeling it'll come back maybe after the battery dies, haven't tried yet. But I need to get my own phone working so I can be back in business.
Whatever recommendations are welcome
Can't wait to go to Samsung lol this or something similar happens every time I try to switch or upgrade rom.
Click to expand...
Click to collapse
All of the things you mentioned are user error and have nothing to do with HTC or the phone itself. Now as far as an answer goes to try to get your phone working again, have you tried holding power for 60 seconds? MOD Edit: Unnecessary.
goliath714 said:
All of the things you mentioned are user error and have nothing to do with HTC or the phone itself. Now as far as an answer goes to try to get your phone working again, have you tried holding power for 60 seconds? MOD Edit: Unnecessary.
Click to expand...
Click to collapse
Yes of course I tried, the phone has been absolutely unresponsive. No amount of button holding is going to fix QHSUSB_DLOAD
Correct me if I'm wrong but http://forum.xda-developers.com/showthread.php?t=1948485 is the only known solution for QHSUSB_DLOAD due to firmware issue (I'm pretty sure this is what happened) or Jtag.
Here's the kicker, the files in that thread are no longer there so as it stands phone's just a Brick.
So for now I'm giving up on it and going samsung.
When I have the energy I may try working on the second one I have which turns out wasn't bricked instead the power button is unusable 90% of the time, but for now that's going to be left out of commission. Ultimately I need a backup because sprint techs seem to only operate on a 3 day basis when it comes to physical repairs therefore I plan to revive the second phone just to keep it as plan-b.
May all be user error but frankly what takes me minutes with a samsung seems to take days on the past couple of HTC phones I've had, so the ranting aspect of my post is merely in these regards and that only and out of frustration, this sucks because I'd take HTC build quality over samsung any day. I've been an HTC faithful since their first windows phone (5 years ago or so).
I know I have to fix the power button on the second phone but have any idea why it fails halfway through a factory RUU?
that's where I left off with it, it's S-On Unlocked running TWRP 2.8.0.1 I was trying to return it to full stock so I can have a go with facepalm S-Off procedure.
Did you relock the bootloader prior to attempting to run the RUU?
Magnum_Enforcer said:
Did you relock the bootloader prior to attempting to run the RUU?
Click to expand...
Click to collapse
out of 3 different RUUs I donwloaded only one worked, bootloader was relocked, ran RUU, Error 132 "Signature Error"
the one that did work the installer said finished, phone reboots but goes right back to bootloader where it says "Relocked" & "Security Warning" won't do anything else.

i717 will not boot Samsung logo stays on screen.

After years of great service my i717 will not boot. It shows Samsung, then this changes to a slightly fuzzy version of Samsung and just hangs there.
I am totally new to doing any modifications to phones.
I tried pressing vol up/dn then power and and it showed a screen about downloading a custom something but it didn't look like anything downloaded and this didn't help.
I then tried the genius method of just trying stuff!
I downloaded Odin 1.85.rar and cwm-i717-120305.tar.md5 and installed this as the pda option.
The phone still hangs at Samsung
But now when I hold vol up / dn and power I get a CWM-based Recovery v5.5.0.4 menu.
I put a sdcard in and chose the menu options to format the sd card, mount it and then do a back up to the sdcard.
It listed a lot of files and then rebooted.
When I mount the sd card in a PC it is blank.
I would like to recover my contacts from this phone if possible and I would like to get the phone working mostly so I can read NFC chips for some NFC development I am doing.
Please someone tell me what to do to get the phone to boot and a link to getting started information for someone totally new to phone modding.
Thanks.
What no one wants to help a total noob?
Was I too honest?
Would it have helped if I said I spent two whole days researching this?
About half of the problems with boot loop on i717 seemed to be caused by a stuck power button which obviously was not my problem.
ALL of the other suggestions I found were no help either.
So totally new to this I figured out I should download odgin, and this specific cwm file cwm-i717-120305.tar.md5 and install it with specific options.
I then tried to wipe the cache,
And wipe the dalvik cache,
both didn’t help.
I then tried to do a full back up to sd card.
It ACTED like it did the back up but the sd card when mounted on a PC was blank.
I then did a factory reset and now I have my good old ATT i717 note v1 working again!!
I would have liked to get my contacts but had no help.
This is all I really needed because now I have NXP Taginfo running reading nfc tags which my new J7 doesn’t do even though it says it has NFC support.
I would REALLY like to know why
1) CWM back up looks like it works but ends up with a blank SD card.
2) Boot HANG on second “fuzzy” "Samsung" screen, why is this and how to get a back up of contacts when CWM doesn’t back up.
3) ATT store “help” should have done a simple factory reset on the phone to avoid me having to buy a new phone. But they of course acted like I needed a new phone. This alone makes me want to switch.

Categories

Resources