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
Related
Greetings everyone. Reader for a while, but this is my first post, and unfortunately it's because I'm quite sure I should be preparing a burial plot for my phone unless someone can help.
Here's the situation:
I installed the Cyanogen Mod beta on my Vibrant and it was pretty cool, but I couldn't get passed the gps and video recording (I was warned, I know, but I wanted to try it anyway). This was not the first rom I had flashed, and was familiar with CWM and ODIN, so this was not a problem for me. I wanted to have something working so I decided to go back to the DeOdexed JL5 rom, which I was running before, so I went into ODIN to restore back to stock before flashing, and it hung up after clicking repartition. I pulled the battery on my phone, and when I went to put it into Download mode again, it wouldn't go into it. Hell, it wouldn't do anything.
How totally screwed am I?
the phone won't turn on?
try plugging first the usb then hold the volume buttons then put back the battery.
That would put it in Download mode. It won't go into that.
you can't put it into download mode?
Nope... =/
sharkethicx said:
Nope... =/
Click to expand...
Click to collapse
did u take the sim and ex sd card out, than repeat?
ZachLL88 said:
did u take the sim and ex sd card out, than repeat?
Click to expand...
Click to collapse
Yeah. Always did before I tried putting it in download mode out of some (probably irrational) fear that they would get wiped as well
There have been a handful of others recently who have had their vibrants in the state where they aren't booting, aren't even showing a charging icon when plugged in. Persistence is the key. The steps posted by iynfynity do work, even from your current state, according to the individuals who have found themselves in the same state lately, no power, phone doesn't respond to anything. You can find these posts around these forums here at xda. Keep trying, if you get frustrated, walk away for a little bit and try again later.
-Remove battery and all cards, have odin open, files loaded and ready to go.
-Plug in usb, holding both volume, pop the battery in
Again, persistence is the key, and a little patience doesn't hurt either.
I can vouch for that... I always used the 3 button combo and had this happen. I tried everything. I even have a replacement sitting here still in the box not opened. I tried 1 more time with just pulling the battery sim and sd card out, plugging in the usb to pc, held down just the volume buttons, plugged in usb to phone, put the battery in and right to download mode.
I'm keeping my old phone and sending the replacement back..This one just won't die... : )
Thank you, you lovely gentlemen. Persistence and patience was key. I'd pretty much given up all hope on it once I plugged it in and it wouldn't even pop up with the battery charge indicator.
I wish I was more patient because I already bought a Captivate, rooted, unlocked, ROMed it. Oh well at least now I have a backup phone.
Glad you got it back up at least. Hopefully your captivate wont start shutting itself off when your battery gets below 85%, as many others are plagued with, if it does though, you have your backup.
Ginger Clone's of the World Unite! Via the XDA App
did it worked?
Sent from my SGH-T959 using XDA App
iynfynity said:
did it worked?
Sent from my SGH-T959 using XDA App
Click to expand...
Click to collapse
Yes it did =) and for now, I'm using my Captivate as my PMP. I loaded my music on there and I'll keep my games on there as well to save room on my Vibrant. Guess I got the Galaxy Player early
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.
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.
I'm running a rooted tb with thundershed 1.5. My phone was plugged in charging and everything was fine until I unplugged it. It then did a quick reboot into the htc screen, and now it will not stop rebooting.
I am able to get into the HBOOT menu, but I cannot access recovery. I have no idea what to do now as I cannot access my sd card via my phone.
Any ideas? I dont want to start having to use my storm again....
You need to download and flash the recovery in fastboot.
Sent from my ADR6400L using Tapatalk
Never, ever leave a PG015img.zip file in the root folder of your SD card
hallstevenson said:
Never, ever leave a PG015img.zip file in the root folder of your SD card
Click to expand...
Click to collapse
Yea and what he said
Sent from my ADR6400L using Tapatalk
so my tb finally **** the bed. For some reason whenever it was charging and I unplugged, it would constantly bootloop. And yesterday I couldnt even get it to hold a charge. Finally I was fedup and brought it to verizon.
Because I had cracked my screen prior to this incident, they would not be able to issue a warranty replacement regardless if it was from the screen or not. Luckily I pay for the insurion replacement (I usually go through 3 of each phone model) and ordered a replacement.
but this time I pulled a fast one. I switched my phone make on the asurion website hoping it would work.
Today I received a brand new rezound, complete in box with charger, new battery, 16gb sd card, and headphones.
I win
Hello everyone,
I seem to be facing a singular issue, but I imagine it is much my fault, and just wanted a confirmation from those more experienced with the device...
I bought an Incredible 4G from eBay, that already had the a copy of Avatar on it, I believe almost the latest update. So when I confirmed the device worked after charging the battery, I flashed the latest copy of Avatar and the JB Gapps, and everything seemed hunkydory.
So, after that, I put in my old SIM, deactivated as I was using a non-4g device, and put it in the Incredible 4G. I started the activation process on the phone, following prompts to reboot the phone (Note: I did not know about CM10.1's issue regarding activation at the time, so one of the possible problems.)
After seemingly failing to activate after the first reboot, I "tried again" and it went down for another reboot. And it stayed down. Completely. I cannot get the phone to start, after charging the battery separately, cannot get into bootloader, nothing. I get QHSUSB_DLOAD when plugged into a computer using USB, but that's it.
A few notes: first time I started up, the screen went to recovery. I didn't think that was an issue; I factory reset from there, and rebooted into Avatar. Second issue: I used ROM updater on the phone to download and install the recovery, as I imagined that there was an automatic checksum done in the process (perhaps it was imagined?), and so when it went to flash, it had some issue, which didn't seem like a problem with the download, and I went through flashing it normally through recovery. Sorry I can't provide more details on that, but everything seemed to work all right after rebooting.
Finally, and this may be irrelevant, I put a 64GB SDXC card in the phone, I had already realized that it could not natively support exFAT, and so left the card in the device until the next time I could boot to recovery to partition it, and went through the activation process with the card inserted and not recognized.
So, I imagine that I have a hard brick, but can't tell if it's completely my fault, because it bricked in a peculiar fashion, at least from what I can tell, as no one seems to have encountered a similar issue after searching for the last 5 days.
If there's any hope for recovery, I would really appreciate some help regarding the device. I'm willing to provide some more info if necessary, and I'd like to find out sooner rather than later if it's a lost cause.
Thanks for any help you guys can give. XDA devs are awesome.
Quite the predicament. Just to clarify, have you tried the following?
1) Remove that super-big MicroSD
2) Remove SIM
3) Remove battery and wait a few minutes; also press the power button while phone is off
4) Only re-inserting the battery, hold vol-down and then hold power until screen comes on (then release power but keep holding vol-down)
I have tried them all; no SIM or SD card has been in there since the issue started. I hadn't tried pushing the power button while the battery was out, but it doesn't seem to change anything. So far, no reaction whatsoever even when holding power + vol down for a few minutes.
ChiqOmar said:
I have tried them all; no SIM or SD card has been in there since the issue started. I hadn't tried pushing the power button while the battery was out, but it doesn't seem to change anything. So far, no reaction whatsoever even when holding power + vol down for a few minutes.
Click to expand...
Click to collapse
Looks like you have a very hard to solve brick, I would like to help, have you tried using fastboot, I mean connected to pc and on that screen issue a fastboot command, also upload a picture of it please since this is new kind of brick, also I found this, our device is supported,
http://unlimited.io/qhsusbdload.htm
Sent from my ADR6410LVW using xda app-developers app
jose51197 said:
Looks like you have a very hard to solve brick, I would like to help, have you tried using fastboot, I mean connected to pc and on that screen issue a fastboot command, also upload a picture of it please since this is new kind of brick, also I found this, our device is supported,
http://unlimited.io/qhsusbdload.htm
Sent from my ADR6410LVW using xda app-developers app
Click to expand...
Click to collapse
You can't do fastboot if you can't reach the bootloader, and I've been assured the unlimited.io tool will not help for DLOAD resulting from non-racun related procedures.
Reading forum posts about QHSUSB_DLOAD suggest either jtag is necessary (which might not be worth it considering the phone can be purchased for $150 on ebay) or some strange strokes of luck after letting the phone sit for a bit. ChiqOmar, sorry I don't have great advice; do all the reading you can about QHSUSB_DLOAD mode.
jose51197 said:
Looks like you have a very hard to solve brick, I would like to help, have you tried using fastboot, I mean connected to pc and on that screen issue a fastboot command, also upload a picture of it please since this is new kind of brick, also I found this, our device is supported,
http://unlimited.io/qhsusbdload.htm
Sent from my ADR6410LVW using xda app-developers app
Click to expand...
Click to collapse
yes sounds like he is stuck in QSHUSB_DLOAD mode, but i don't know if the resolutiion on unlimited.io will help him or not.they say it's not supported for other reasons other than from running their exploit. it might work though.
mdmower said:
You can't do fastboot if you can't reach the bootloader, and I've been assured the unlimited.io tool will not help for DLOAD resulting from non-racun related procedures.
Reading forum posts about QHSUSB_DLOAD suggest either jtag is necessary (which might not be worth it considering the phone can be purchased for $150 on ebay) or some strange strokes of luck after letting the phone sit for a bit. ChiqOmar, sorry I don't have great advice; do all the reading you can about QHSUSB_DLOAD mode.
Click to expand...
Click to collapse
Maybe port HTC unbricking project to our device, and try to help him using it, since he can't do nothing about it right now, ChiqOmar, you ok with testing it ?, btw download ubuntu connect phone and see if the partitions get mounted, btw looks like you need to flash hboot from that mode, that's all then ruu, I have all the tools to do it if you want to
Sent from my ADR6410LVW using xda app-developers app
mdmower said:
You can't do fastboot if you can't reach the bootloader, and I've been assured the unlimited.io tool will not help for DLOAD resulting from non-racun related procedures.
Reading forum posts about QHSUSB_DLOAD suggest either jtag is necessary (which might not be worth it considering the phone can be purchased for $150 on ebay) or some strange strokes of luck after letting the phone sit for a bit. ChiqOmar, sorry I don't have great advice; do all the reading you can about QHSUSB_DLOAD mode.
Click to expand...
Click to collapse
i was able to bring my rezound back after a hard brick with a hex edited hboot that went bad with this tool but ported for rezound. its worth a try?
Thanks for the help everyone. Yes, although it states quite clearly that the Unlimited.io tool is only meant for devices bricked using their tool, I tried it anyway; obviously, nothing changed.
Though JTAG sounds interesting, I have no idea how to get started with that...nor do I really know if I want to travel down that route just now.
The HTC Unbricking Project sounds promising, but also no idea how to get started as it has not been ported for our device. The partitions don't get mounted in Ubuntu, as I connected it to the computer to use the Unlimited.io tool.
Finally, regarding the nature of the brick itself, I really wish I could pinpoint the issue better to help others if a similar issue happens in the future.
I am actually waiting on a battery, (ordered before I got the phone) and so will try that to see if anything changes.
Thanks again everyone. I've got a feeling I might have to write this one off pretty soon.
ChiqOmar said:
Hello everyone,
I seem to be facing a singular issue, but I imagine it is much my fault, and just wanted a confirmation from those more experienced with the device...
I bought an Incredible 4G from eBay, that already had the a copy of Avatar on it, I believe almost the latest update. So when I confirmed the device worked after charging the battery, I flashed the latest copy of Avatar and the JB Gapps, and everything seemed hunkydory.
So, after that, I put in my old SIM, deactivated as I was using a non-4g device, and put it in the Incredible 4G. I started the activation process on the phone, following prompts to reboot the phone (Note: I did not know about CM10.1's issue regarding activation at the time, so one of the possible problems.)
After seemingly failing to activate after the first reboot, I "tried again" and it went down for another reboot. And it stayed down. Completely. I cannot get the phone to start, after charging the battery separately, cannot get into bootloader, nothing. I get QHSUSB_DLOAD when plugged into a computer using USB, but that's it.
A few notes: first time I started up, the screen went to recovery. I didn't think that was an issue; I factory reset from there, and rebooted into Avatar. Second issue: I used ROM updater on the phone to download and install the recovery, as I imagined that there was an automatic checksum done in the process (perhaps it was imagined?), and so when it went to flash, it had some issue, which didn't seem like a problem with the download, and I went through flashing it normally through recovery. Sorry I can't provide more details on that, but everything seemed to work all right after rebooting.
Finally, and this may be irrelevant, I put a 64GB SDXC card in the phone, I had already realized that it could not natively support exFAT, and so left the card in the device until the next time I could boot to recovery to partition it, and went through the activation process with the card inserted and not recognized.
So, I imagine that I have a hard brick, but can't tell if it's completely my fault, because it bricked in a peculiar fashion, at least from what I can tell, as no one seems to have encountered a similar issue after searching for the last 5 days.
If there's any hope for recovery, I would really appreciate some help regarding the device. I'm willing to provide some more info if necessary, and I'd like to find out sooner rather than later if it's a lost cause.
Thanks for any help you guys can give. XDA devs are awesome.
Click to expand...
Click to collapse
Just got same issue, though for me I installed avatar rom, then rebooted at some point, but instead it hard bricked, can't charge pull battery out/in boot back up removed sim sd card didn't help me either. Any progress yet, or help?
Ill try to get a working htc unbriking Project soon for you guys to try, both please use ubuntu and have a working USB cable, I'm gonna try to reinstall hboot, also have teamviewr installed, also please tell me if you guys are supercid, also no usb 3.0 cable or port please
Sent from my ADR6410LVW using xda app-developers app
Some Information
jose51197 said:
Ill try to get a working htc unbriking Project soon for you guys to try, both please use ubuntu and have a working USB cable, I'm gonna try to reinstall hboot, also have teamviewr installed, also please tell me if you guys are supercid, also no usb 3.0 cable or port please
Sent from my ADR6410LVW using xda app-developers app
Click to expand...
Click to collapse
I'm on Ubuntu 13.04 64 Bit, I have a usb cable, Anker Battery Expert separate battery charger. And my Phone is S-OFF DirtyRacun Currently still hard bricked (Not by the Racun though) don't have any 3.0's, i have a onn usb cable and the stock, I also have a Ubuntu 12.04.2 LTS 32 Bit Live DVD. Battery Charging using a battery pack charger. Won't charge through USB
OldNut5 said:
I'm on Ubuntu 13.04 64 Bit, I have a usb cable, Anker Battery Expert separate battery charger. And my Phone is S-OFF DirtyRacun Currently still hard bricked (Not by the Racun though) don't have any 3.0's, i have a onn usb cable and the stock, I also have a Ubuntu 12.04.2 LTS 32 Bit Live DVD.
Click to expand...
Click to collapse
pm me with gtalk email and ill see what i can do, also install teamviewr
OldNut5 said:
I'm on Ubuntu 13.04 64 Bit, I have a usb cable, Anker Battery Expert separate battery charger. And my Phone is S-OFF DirtyRacun Currently still hard bricked (Not by the Racun though) don't have any 3.0's, i have a onn usb cable and the stock, I also have a Ubuntu 12.04.2 LTS 32 Bit Live DVD. Battery Charging using a battery pack charger. Won't charge through USB
Click to expand...
Click to collapse
I lost my first Dinc 4G LTE after I installed CM10.1, was working great for a while and just blinked off, never to recover. No charge light, no response to power button. I also had an aftermarket battery (Hyperion), but it would get so hot charging I replaced it with an OEM HTC battery. I think that damaged the phone.
Since I work with analog electronics, I assume something in the power path physically burned out. I never tried to talk to it via USB, but just cabling it to a computer generates no response.
I went back to the Stock RUU.zip from the unlimited.io site to get the firmware update. During the update it just sort of died. Now I can't get it to charge or get into the bootloader. Help! Please!:crying: