It's been a bad experience the past day and a half. I manage to successfully root my 3D but when I finally rebooted it kept bootlooping Everytime it managed to get to the hands free activation window. So after trying little things to fix it, I finally decided to back up and restore. When I restored and rebooted it just hung at the splash screen. Which basically meant there was no system data on it (thanx clockwork)<sarcasm. So I then decide to download a RUU from my girls hero (only internet available) but the downloads keep failing. By me being able to get into the bootloader I didnt make it a big deal and called it a night. When I awoke I saw that viperboy released a Rom so I downloaded on my girls hero, swapped the sd cards back and now it won't boot into the bootloader. I'm stuck and frustrated because it was just booting into hboot yesterday and I haven't touched it since then. So what do you guys think its a brick. Or can I do something to fix this.
if you can't get into hboot what does it do, fruit loops still? Maybe it gets far enough into the boot process that you can issue fastboot commands. I would try to make fastboot reboot into boot loader and flash the image via fastboot. Timing would likely be key to issue the command from your computer....and that is all predicated on fastboot being able to do what you have not--get into hboot.
Have you tried battery pull before trying to get into the bootloader?
EDIT: Yeah, I think it's fixable.
daneurysm said:
if you can't get into hboot what does it do, fruit loops still? Maybe it gets far enough into the boot process that you can issue fastboot commands. I would try to make fastboot reboot into boot loader and flash the image via fastboot. Timing would likely be key to issue the command from your computer....and that is all predicated on fastboot being able to do what you have not--get into hboot.
Have you tried battery pull before trying to get into the bootloader?
EDIT: Yeah, I think it's fixable.
Click to expand...
Click to collapse
It gets as far as the splash screen because remember I stated that clockwork tweeked out and didn't properly backup my system. So I had to download a Rom from another phone to flash but now it won't boot into bootloader. When I try to charge after a battery pull the light goes on then off. Then if you look closely enough you could see a a very soft red led blinking when holding the power button down. It turns on and goes to the splash but it won't boot into bootloader. I mean if it was bricked it wouldn't even come on.
Sent from my HERO200 using XDA App
r0cky0790 said:
It gets as far as the splash screen because remember I stated that clockwork tweeked out and didn't properly backup my system. So I had to download a Rom from another phone to flash but now it won't boot into bootloader. When I try to charge after a battery pull the light goes on then off. Then if you look closely enough you could see a a very soft red led blinking when holding the power button down. It turns on and goes to the splash but it won't boot into bootloader. I mean if it was bricked it wouldn't even come on.
Sent from my HERO200 using XDA App
Click to expand...
Click to collapse
have you tried wiping everything?
also, my phone sometimes does that weird soft blinking thing....just hold the volume down and do not let that go....press the power button, if it doesn't turn on or does the blinking thing (which only happens to me when plugged in or shortly after unplugging) press the power again, and again.....never letting up on the volume-down. It took me a while to figure that one out and it definitely kept me out of the bootloader for the first couple days I have the phone.
Wow, thanks that work like a charm. Dude I thought it was all over. I was just about to smash the screen and pay a deductible.
E
Sent from my HERO200 using XDA App
r0cky0790 said:
Wow, that work like a charm. Dude I thought it was all over. I was just about to smash the screen and pay a deductible.
Sent from my HERO200 using XDA App
Click to expand...
Click to collapse
No problem, glad to help.
Very hard to brick a device unless you are a complete moron and flash something not made for your phone.
Related
so I was trying to update the RUU when i did that i put a coustom rom too .. my htc booted up perfectly but ever time i touch an app it would just start shut down the phone when i was try to fix problem by just Using the new RUU i couldnt get in to hboot or turn on my phone
OK first your phone is not a brick. A brick is just that, a brick. It doesn't turn on at all.
Next did you allow the RUU to run fully? Meaning did you allow it to update the hboot, reboot and then finish the update?
Sent from my VIZIO tablet using xda premium
Sounds like it only ran the first set of updates. Run the RUU again and it will update everything else.
it wont turn on i check the battery with my dad's htc rezound i was trying to get back to hboot but phone wont turn on any help pls
Plug your phone in and remove the battery. Then boot into hboot.
Sent from my VIZIO tablet using xda premium
no luck it wont turn on
Did you try holding volume down while pressing power?
Sent from my ADR6425LVW using xda premium
Continue to hold volume down until it hits the boot screen. You shouldn't have to hold it that long, but it won't hurt.
Sent from my ADR6425LVW using xda premium
EmerikL said:
OK first your phone is not a brick. A brick is just that, a brick. It doesn't turn on at all.
Click to expand...
Click to collapse
I was just about to say that.
not bricked
It doesn't sound like you are bricked, just that the RUU didn't fully take. First, take your removable SD card and connect it to your computer. If you don't have a microSD card reader on your computer, hit radio-shack or something and get a usb microSD card adapter, costs like $10 and is a life saver. Now backup everything on your SD card and then wipe the card clean and just put the RUU on, renamed to PH98IMG.zip. Make sure that you didn't make it PH98IMG.zip.zip or it won't work. Next put the SD card back into the phone, hopefully you still have it locked, and when you boot it, it should update properly. Remember that it has to flash twice, the first time it like only updates the bootloader and radios or something, the second time (after it reboots) it will completely flash the rest of the RUU.
I hope that helps.
Oh and one more important thing, after you flash the RUU and you are sure it is working properly, delete the PH98IMG.zip from your external SD card. You really don't want it there after the phone has flashed and everything is working properly.
tcinfantino said:
If you don't have a microSD card reader on your computer, hit radio-shack or something and get a usb microSD card adapter, costs like $10 and is a life saver.
Click to expand...
Click to collapse
A micro SD reader is an Android hacker's best friend.
It has saved me many times!
thanks everyone but it wont turn on even if i'm holding the power & vol button down i even try cmd reboot not respond to my rezound i just going to get a new one... last thing i was trying to do before this happen i was trying to get the sd card out with out turning out the rezound so i pulled the battery slow to her i could get the sd card i pulled it out and the battery came out to after that it never power back on
cflo360 said:
thanks everyone but it wont turn on even if i'm holding the power & vol button down i even try cmd reboot not respond to my rezound i just going to get a new one... last thing i was trying to do before this happen i was trying to get the sd card out with out turning out the rezound so i pulled the battery slow to her i could get the sd card i pulled it out and the battery came out to after that it never power back on
Click to expand...
Click to collapse
Take the battery out and unplug it from the computer. Let it sit for a few minutes and chill out.
Then, put the battery back in and press volume down and power and keep holding until you see the screen turn on. Then you should be in hboot.
I had the SAME problem. I tried loading a rom that required the new RUU when I was on the outdated one. I simply downloaded the new RUU, renamed it, and went into HBOOT. I noticed that you need to run it 2 times, oddly enough. After that, I was golden.
A Brick is a Brick my friend, paperweight.
cflo360 said:
thanks everyone but it wont turn on even if i'm holding the power & vol button down i even try cmd reboot not respond to my rezound i just going to get a new one... last thing i was trying to do before this happen i was trying to get the sd card out with out turning out the rezound so i pulled the battery slow to her i could get the sd card i pulled it out and the battery came out to after that it never power back on
Click to expand...
Click to collapse
Seriously I have never had a phone not boot have you tryed using your dads battery and deffinetly let it sit for a half hour without a battery or plunged into anything then try it again mabey you do got a brick but I doubt it
Sent from my ADR6425LVW using XDA
mined might be bricked like yours
im not trying to hijack your thread just looking for help alright here is where i start. I'm running the new leak, just flashed BAMF 2.0 a day or 2 ago. i have been updating roms regularly without a problem. i tried to flash Sebastian 1782 OC kernel. When i did i got a main ver error. I went into Sebastian thread and was reading where other people had problems with the main ver error and i did what was said to do to fix it. They said to open the android text file in the kernel and change the main ver to the same this i was running and to change the hboot to what i was running. So i did that. flashed into recovery and flashed the kernel. It flashes and then heres where i get a problem. It says reboot to bootloader to complete. The phone shuts down and thats it. It wont turn on. It wont do anything. i have pulled the battery and left it out for a few minutes and put it back in but nothing. I tried to charge it and the amber led wont even light up. What went wrong? I need help. This absolutely blows
You do no have it plugged in right the only time i had this problem when it was
okay! so I have a S-on amaze 4g. Unlocked bootloader and have clock work recovery, Im also on tmobile. I was running Bulletproof's rom v2.5
so yesterday I was looking at some roms and I came accross mike 1986's android revolution ROM that was based on tmobile's sense 3.6 and android 4.0. I decided to ditch my current ROM and go for mike's ROM instead
Well last night I followed his instructions. Put the PH85IMG, Rom and Super wipe to my phone's SD card. I booted into bootloader and it loaded the PH85IMG but it didnt seem to have done anything so it loaded back to bootloader. I selected "Recovery" and booted into recovery. I deleted my files and cache using clockwork recovery. Then applied the Superwipe zip then installed the ROM. It said it installed the rom and then I proceeded to reboot my amaze 4g. Ok I rebooted my phone and it got stuck on the HTC screen for some quit time WITHOUT THE QUIETLY BRILLIANT. So i decided to redo this all over again. and again the same problem happened. stuck on the HTC logo. so I took out my batterys and went to bed since i wanted to get some shut eye
now this is where my problem comes from. When ever I turn on my phone it wont turn on! i wanted to boot into bootlader but when ever i press on the power button with the volume rocker down it wont start up. So i plug in my USB cable and the LED that indicates charging comes on. and my computer detects the phone... i click on the search capacitive button and the phone disconnects from my computer and it boots into the HTC screen and the screen turns blank
if anyone can help me please help.
come on 43 views and no help
Leave your phone in the charger overnight. See what happens in the morning.
hasoon2000 said:
Leave your phone in the charger overnight. See what happens in the morning.
Click to expand...
Click to collapse
i dont think thats going to work but ill give it a try
Just curious. What version of CWM was installed?
Sent from my HTC_Amaze_4G using Tapatalk 2
So you cant get the the phone to turn on, but u were able to turn it on when it was connected to the computer?
Sent from my NRGized amaze
Via XDA premium
Ok. First don't panic. Can you explain by "I clicked the capactive search button". Have you really try power it on without your computer?
Sent from my HTC_Amaze_4G using XDA
jp2dj1 said:
Ok. First don't panic. Can you explain by "I clicked the capactive search button". Have you really try power it on without your computer?
Sent from my HTC_Amaze_4G using XDA
Click to expand...
Click to collapse
what i mean by that is when i touch the search button (the magnifying glass icon on the far right) when its charging it would boot into the HTC screen then the screen would turn off
aj_2423 said:
So you cant get the the phone to turn on, but u were able to turn it on when it was connected to the computer?
Sent from my NRGized amaze
Via XDA premium
Click to expand...
Click to collapse
i cant get the phone to turn on when its connected to the computer or wall charger
i just noticed that my LED would blink when first charging then it boot into the HTC screen on its own then the screen would turn off or go blank. after that the LED wouldnt come on so i dont know if its still charging since the orange light isnt there
any more help it would be greatly appreciated
I tried the same rom yesterday and it failed for me also. I've seen quite a few fails on it. Mine didn't die like yours, mine just froze on the splash screen. I had to pull the battery and hboot and re install my recovery so I could restore my backup. Does anything happen if you pull the battery and try to get into bootloader?
jimczyz said:
I tried the same rom yesterday and it failed for me also. I've seen quite a few fails on it. Mine didn't die like yours, mine just froze on the splash screen. I had to pull the battery and hboot and re install my recovery so I could restore my backup. Does anything happen if you pull the battery and try to get into bootloader?
Click to expand...
Click to collapse
i cant even get my phone to get into hboot when i press down on the power and volume buttons.
it did work yesterday after i failed... but when i woke up today i cant even get into hboot for some reason.
You might have to get an external charger to charge your battery, or if you know anyone to swap batteries with to charge yours and try theirs to see if it's just a dead battery. Sounds like it might be.
Download the latest RUU for your phone. You said the computer detects the device see if the RUU will see it as well. Hoping that it does just run it and it will flash your phone back to stock stock and you may have to unlock and install clockwork again but if it works you'll have a working phone again good luck chief
Sent from my LG-P999 using Tapatalk 2
I believe the Rom u were trying to flash is for s-off only....I might be wrong though...
Sent from my HTC_Amaze_4G using XDA
If i recall, you were supposed to lock the bootloader before you placed the PH85.img, because it wouldn't recognize the file without it on an S-On device. Also, where you using Xboarder's Clockwork recovery touch? or an older version?
Try this and tell me what happens. Change your phone by your computer USB and turn it on by search button and "HOLD THE DOWN VOL BUTTON AT THE SAME TIME" try it a couple of times.
Sent from my HTC_Amaze_4G using XDA
I think it's a problem with the version of cwm installed, it won't charge the battery right if it dies all the way pull the battery then charge it for about 20 mins then battery pull again and charge for a minute or two and try and turn it on
Sent from my HTC_Amaze_4G using XDA
Thread Moved to Q&A. PM sent to OP.
Sent from my Galaxy Note i717, using XDA Premium.
You don't have to be a farmer to know what sh*t smells like.
Ok so Ive searched for help at phandroid, but, I think I might need some XDA help !
I repair phones at CPR loveland colorado.
Routine digitizer replacement on a Rezound. Turn the phone on. Everything looks great. HTC splash screen comes on nice and bright and then cuts out.
The phone is still on and booted into the Android OS. Its just that the LCD is out.
Replaced LCD and i got the same thing. Even tried changing digitizers. Nothing. LCD only stays on for 5 seconds after booting or in the Bootloader.
If I go into the bootloader, the LCD stays on. If i go into recovery it turns off again!
I have ADB/Fastboot set up. But when i use the command "adb devices" while in fastboot usb mode, nothing is shown. I have the latest HTC drivers and HTC SYNC turned off.
I've tried using the leaked ICS RUU through the sd card. It loaded the img and completed, but, still no LCD after boot.
After no luck, I unlocked the bootloader and flashed Amonra. Still, when i go into recovery, the LCD cuts out again. So I relocked the phone.
Phone is currently TAMPERED/RELOCKED.
If anyone has any ideas, please, throw them at me.
Thanks for reading my post guys. Again, any help would be great. Thanks for providing a great community here at XDA!
Synergy-7 said:
Ok so Ive searched for help at phandroid, but, I think I might need some XDA help !
I repair phones at CPR loveland colorado.
Routine digitizer replacement on a Rezound. Turn the phone on. Everything looks great. HTC splash screen comes on nice and bright and then cuts out.
The phone is still on and booted into the Android OS. Its just that the LCD is out.
Replaced LCD and i got the same thing. Even tried changing digitizers. Nothing. LCD only stays on for 5 seconds after booting or in the Bootloader.
If I go into the bootloader, the LCD stays on. If i go into recovery it turns off again!
I have ADB/Fastboot set up. But when i use the command "adb devices" while in fastboot usb mode, nothing is shown. I have the latest HTC drivers and HTC SYNC turned off.
I've tried using the leaked ICS RUU through the sd card. It loaded the img and completed, but, still no LCD after boot.
After no luck, I unlocked the bootloader and flashed Amonra. Still, when i go into recovery, the LCD cuts out again. So I relocked the phone.
Phone is currently TAMPERED/RELOCKED.
If anyone has any ideas, please, throw them at me.
Thanks for reading my post guys. Again, any help would be great. Thanks for providing a great community here at XDA!
Click to expand...
Click to collapse
just thinking out loud...would a messed up/blocked proximity sensor be involved. At what point in the boot process or even in recovery does the sensor become active?
Looks like bad hardware
Sent from my ADR6425LVW using Tapatalk 2
Yeah there is a problem that probably can't be easily fixed. The proximity sensor is a good thought tho might want to check that out
they proximity sensor should only kill the screen when an application such as the dialer calls upon it to do so. seeing as the screen works when you are booting and fails after boot, have you considered reflashing the phone back to factory?
Or doing a factory reset if u can wing it from hboot
Sent from my ADR6425LVW using xda premium
Kidney Poker said:
Or doing a factory reset if u can wing it from hboot
Sent from my ADR6425LVW using xda premium
Click to expand...
Click to collapse
Would an exe RUU process be able to run with his screen situation? Con could really provide some good info but I bothered him on gtalk all night the last two nights working on the venom stuff so I'm not messaging him right now lol.
Does the screen work in recovery?
con247 said:
Does the screen work in recovery?
Click to expand...
Click to collapse
Does not work in recovery.
I would love to flash a gingerbread ruu on it. Official.Signed. Any idea where I can find that?
Synergy-7 said:
Does not work in recovery.
I would love to flash a gingerbread ruu on it. Official.Signed. Any idea where I can find that?
Click to expand...
Click to collapse
I think these should do.
http://www.filefactory.com/f/c2e320ee1d5c7886/
So i did the HTC Dev unlock with s-on then installed the team win recovery. Tried to install CM10 with no luck. Installed what i thought was a stock ROM OMJ_EVO_LTE_4.0.3_ICS_Stock_Deodexed.zip
Long story short, been running like this for a few weeks till i can rap my head around this hboot, s-on better but been getting constant lag and occasional artifacts on screen. I also can't seam to get to hboot using the power and down volume button any more. I can get to recovery view titanium backup pro but if i use team win to boot to hboot, it appears to just power off.
Any advice?
Sent from my EVO using xda app-developers app
Connect to adb and in console type adb reboot bootloader. You can also use flash image gui to flash cm10 kernel, then go to recovery and flash ROM
This I shall try. Your advice is appreciated!
Sent from my EVO using xda app-developers app
My EVO doesn't seam to have the ability to get to the bootloader at this point I can run the windows rooter, boot to recovery and install the Rom mentioned in the op. Then root may or may not work....
The screen is constantly getting curupted. The desktop will not update until I touch it again. Major ***** there. Open an ap, doesn't open, touch glass again and app opens and I'm in setting or something else so I hit home key, nothing, hit again and I'm in widgets! Took me a half-hour just to get this posted. I type a word and about 5 secondslaterit spears. Using a process monitor it looks somewhat normal with nothing running in background killing the CPU or memory.
I'm wondering if my poker accepted an ota update. There was a notice in taskbar when this crap started. I think I need to figure out how to get this back to stock.
I'm running 1.13 and tried RUU 1.13 but that crapped out after the reboot. (bootloader again!)
Sent from my EVO using xda app-developers app
Update! I ran RegawMOD EVO 4G LTE Rooter and it completed the root process. I never saw the bootloader/fastboot screen. I can use adb reboot-bootloader to reboot it into bootloader. Again, I have no screen output, it is black. Not even a glow.
So I
Have a funtional Evo 4G LTE but
1) bootloader/fastboot can be accessed via CMD/ adb reboot-bootloader AND power+VOL down and will repond to commands via command line. No display output.
2) can get to twrp 2.2 recovery via adb reboot recovery twrp screen output corrupted and difficult to use.
3) I can get to the rom but screen input is one step behind. IE Power on, in sleep with screen off.... Hit power button, display is corrupted. Slide the unlock ring and I see the unlock screen, touch the area where msg icon is and i see the home screen. touch the area where the first txt thread is and see the default txt screen. Touch where the txt box is and see the thread but the keyboard doesn't show tho it is there... (That would explain the garbled post up above lol)
I'm getting pretty good at "blind" operating this thing but dang....
So at this time, I just flashed the boot image of meanrom via flash image gui because i got fastboot unrooted again as said at the begining of this post. Currently trying to install the rom via twrp. I think. It is currently displaying the swip to flash screen. The swip bar doesn't move so I am not 100% on this yet. Might need to try again.
Does anyone know how to get hboot info via fastboot command line? (I have no screen output as I said) I want to check to see what version I am dealing with. Last post quote:I'm wondering if my poker accepted an ota update. should have been I'm wondering if my pocket accepted an ota update.
Thanks in advance!
Im hoping someone else will chime in but in the meantime, search for diagnosis on your partions, worse case get your phone into bootloader mode and RUU. It looks to me like your partitions are screwed up.
Sent from my EVO using xda app-developers app
Dude, thanks for the input. The more I worked this cell the slower it got. I did get RUU 2.13 to stick to this phone after many other RUU and resetting attempt failures. Got it back to 'broken' stock and visited Sprint.
Tech guys said that the screen is fubar, replacement time. Got to send it back, need $35 please. The way they explained it, I would give them the phone and I would get a new one in the mail in about a week or two, After fighting this thing for a week I was not ready to hear that and kinda went off on them because they couldn't release store stock. I embarrassed myself by being a total asshole and walked out with my poo evo, Sorry guys.
Today, with a few wawa gift cards (they have good coffee) I went back and apologized for my indiscretions and they did an expedited return meaning that they send a new one and then I send the broken one back. Thanks Sprint and sorry again to the the guys for my temper.
MODS, This thread can be killed.
Thanks for the help folks.
I thought I'd done enough research into all this, but I guess maybe not.
I used Moonshine to s-off my Droid DNA and everything worked as described no problem. I then installed CWM and made a backup. I then went to install Viper on the phone using this guide.
I got to step 2 in this part of the process:
*WARNING* Although you don't have to, but if you do choose to use the recommended Step 3 which is found below, it will wipe all of your games and apps including saved game data and such. Don't worry all of your photos and music will be fine. Make sure to sync your contacts with your Google account**
1. Scroll down to -advanced and hit power, then do as follows
- wipe dalvik cache
-***go back***
2. Scroll down to -mounts and storage and hit power then:
-format system
-press your back key on the phone to go back
3. Scroll down to -wipe data/factory reset and hit the power button
"you can skip this process but it is a highly recommended one if you want less bugs in the ROM" (If you decide to skip make sure you you also -wipe cache partition which is in the same menu)
Click to expand...
Click to collapse
I was ready to do step 3 when I saw the warning above about syncing my contacts with my Google acount. This is where I did something really stupid. I rebooted the phone so I could sync those contacts. I thought I was alright because I had a backup if something went wrong.
However now my phone is stuck on the white HTC screen. I've tried to get into the bootloader to restore my backup by holding down the vol-down and power buttons, but it just goes back to the same white HTC screen.
Am I totally screwed here?
I had that problem once ,first how much battery did you have before maybe want to charge to full. Then hold power till lights flash and turns clear off. Then try power volume, it worked for me. Good luck
Sent from my HTC6435LVW using xda premium
LexStarwalker said:
I thought I'd done enough research into all this, but I guess maybe not.
I used Moonshine to s-off my Droid DNA and everything worked as described no problem. I then installed CWM and made a backup. I then went to install Viper on the phone using this guide.
I got to step 2 in this part of the process:
I was ready to do step 3 when I saw the warning above about syncing my contacts with my Google acount. This is where I did something really stupid. I rebooted the phone so I could sync those contacts. I thought I was alright because I had a backup if something went wrong.
However now my phone is stuck on the white HTC screen. I've tried to get into the bootloader to restore my backup by holding down the vol-down and power buttons, but it just goes back to the same white HTC screen.
Am I totally screwed here?
Click to expand...
Click to collapse
If the above post doesn't work see if adb devices recognizes it. If it does you should be able to get up and running again
Sent from my HTC6435LVW using xda premium
treneffi son
Thanks for the help guys!
It had around 56% battery I believe. I've been letting the phone charge for a few hours. Tried holding power till buttons flashed & then let it power off. Then I held power and down-volume, and I got the same white HTC screen.
When I run adb devices, this is what I get:
adb server is out of date. killing....
* daemon started successfully *
list of devices attached
C:\Users\Lex\Desktop
Click to expand...
Click to collapse
The device isn't listed...
Oh, another thing, don't know if this is useful... When I plugged in the phone to the computer, HTC Sync Manager came up with a pop up that says:
"Device locked.
Unable to recognize the device because the device is locked. Please unlock your device and then reconnect your device."
Click to expand...
Click to collapse
In stickies under development there is toolkit that works for me to get computer to see phone maybe will work for you , sorry just a idea
Sent from my HTC6435LVW using xda premium
---------- Post added at 03:07 AM ---------- Previous post was at 03:04 AM ----------
Also install his drivers good luck
Sent from my HTC6435LVW using xda premium
pennie57 said:
In stickies under development there is toolkit that works for me to get computer to see phone maybe will work for you , sorry just a idea
Sent from my HTC6435LVW using xda premium
---------- Post added at 03:07 AM ---------- Previous post was at 03:04 AM ----------
Also install his drivers good luck
Sent from my HTC6435LVW using xda premium
Click to expand...
Click to collapse
I'm open to any ideas at this point, because I'm lost as to what to do to fix this.
Is it this one? If not, can you tell me the title or give a link?
Thanks so much for your help!
EDIT: I downloaded the toolkit from the link I posted above, and tried everything in the kit. However they all resulted in a "device not found". Can anyone advise me? Is my phone bricked? If so, is there any recourse other than buying a new phone for $600?
Thanks for any light anyone can shed. It's much appreciated.
Did you look at this thread - http://forum.xda-developers.com/showthread.php?t=2038366 ?
Sent from my HTC6435LVW using Tapatalk 4 Beta
Thanks for pointing me to that thread, Ryan. I tried their advised solution, with no luck.
The problem is I can't get into CWM on my phone at all, just the white HTC screen, nothing else. And when I try "adb devices" the device isn't found. When I plug the phone in the computer tries to install a driver (and fails).
I did find this though, so if it's unfixable by me with help from you guys, at least there's hope.
LexStarwalker said:
Thanks for pointing me to that thread, Ryan. I tried their advised solution, with no luck.
The problem is I can't get into CWM on my phone at all, just the white HTC screen, nothing else. And when I try "adb devices" the device isn't found. When I plug the phone in the computer tries to install a driver (and fails).
I did find this though, so if it's unfixable by me with help from you guys, at least there's hope.
Click to expand...
Click to collapse
I dont think its bricked. If your computer is seeing it then something is working on the phone its just not showing up. I have had that problem before with cm10 it would stick at the animation screen and then after awhile my computer would see it.
Honestly i think its just a matter of finding the right thing to get it to go. I had to let my phone completely die before it would do anything. So you may try that before spending $60.
Good luck
I dont think your phone is bricked either, if it turns on that usually means there's still hope. However I think zarboz offers a free JTAG for XDA members if worse comes to worse.
I would recommend going on the irc and getting some live help.
Honestly I would turn it off for a while, then just keep trying and keep trying to get into fast boot. Can you still turn the phone off and get it to charge? You can also try plugging it into your charger, turning it on and off, unplugging it, turning it on and off, etc. I know that sounds weird but I've had weird situations like this with a few devices sometimes that type of just screwing around would eventually get it to work.
Sent from my DNA using Tapatalk 2
---------- Post added at 01:57 PM ---------- Previous post was at 01:53 PM ----------
Also, I know you probably already tried this several times, but try different cables and USB ports and see if you can get adb to see it.
Sent from my DNA using Tapatalk 2
Thanks for the help guys. I let the phone drain out last night, and I plugged it into the charger this morning. It does still charge, and I got it to start up. However, it goes to the same white HTC screen. As long as the phone has power, I can't even get it to stay off. The only way I can get it to turn off is to push both volume buttons and the power button at the same time and hold them down till the buttons flash. Then it will turn off, but a couple seconds later, it turns back on and goes to the white HTC screen. If I try to power off any other way--with just the power button or power button + vol-down button, the buttons will flash but it won't power off.
I even tried plugging the phone into every different USB port on my printer and executing "adb devices" and the phone never came up as a device. But my computer still tries (and fails) to install drivers when I plug the phone in, and HTC Sync loads and gives me the same error message.
I just had some limited success! I plugged the phone into my computer, and tried powering on again with power+vol-down, and the phone went into Fastboot. However, it's still not detected by "adb devices". What should I do?
Thanks for the help guys!
I guess you can't get to recovery in fastboot
Sent from my HTC6435LVW using xda premium
LexStarwalker said:
I just had some limited success! I plugged the phone into my computer, and tried powering on again with power+vol-down, and the phone went into Fastboot. However, it's still not detected by "adb devices". What should I do?
Thanks for the help guys!
Click to expand...
Click to collapse
If you got it into hboot(screen shows fastboot etc)then u r good. Fastboot uses fastboot not adb to flash things. First try going into fastboot at the hboot screen and hit power button on fastboot and recovery should.be there. Ifthat doesnt work then flash a new recovery. Fastboot flash recovery recovery.img. then use fastboot menu as above to enter recovery. Fastboot devices to verify connection.
Thanks so much for all the help guys! I was able to get into Fastboot and restore my backup I'd made, so I'm back up and running. I'm really glad I didn't brick my phone! I was really worried there for a while!