I used the hack kit to try and root my htc inspire. Now all my phone will do is start to boot. It will display the htc logo and the a black fog animation will appear and my screen will turn black. I can still get into the bootloader but I can't seem to do anything else. I also went the IRC section and tried to get some help but all the guy would do is call me a liar and wouldn't help. If I need proof of this I took screen shots of the conversation to prove that I wasn't receiving any help. That is why I am posting this thread to hopefully get my phone working again. Thanks for any help in advanced.
DWSXxRageQuitxX said:
I used the hack kit to try and root my htc inspire. Now all my phone will do is start to boot. It will display the htc logo and the a black fog animation will appear and my screen will turn black. I can still get into the bootloader but I can't seem to do anything else. I also went the IRC section and tried to get some help but all the guy would do is call me a liar and wouldn't help. If I need proof of this I took screen shots of the conversation to prove that I wasn't receiving any help. That is why I am posting this thread to hopefully get my phone working again. Thanks for any help in advanced.
Click to expand...
Click to collapse
You are probably having drivers problems. Try fixing that and rerun the hack kit from the black screen. If not the best is to make a livecd (ubuntu). All that is in the manual...
Ok. If you had read all of the effen manually carefully, you would know what to do.
But since your here. Run the hack kit again. And i dont know that you have driver problems. Same thing happened to me when j hacked my inspire on Ubuntu
Yea. Just plug your phone in, and re run the hack kit.
You should've educated yourself before you began messing with rooting and messing with the software on your phone. While its rare, bricking DOES happen and we can't help you after that. Educate yourself, and read the EFFING MANUAL. Good luck
HTC_Phone said:
Yea. Just plug your phone in, and re run the hack kit.
You should've educated yourself before you began messing with rooting and messing with the software on your phone. While its rare, bricking DOES happen and we can't help you after that. Educate yourself, and read the EFFING MANUAL. Good luck
Click to expand...
Click to collapse
Actually the phone is not bricked. If it was bricked he should thow it away. The Kit couldn´t finish due to drivers issues. He should sort that out and then rerun...He should have checked connectivity before starting..as you said it is all in the manual....
He never said it was bricked..
You could just send the phone to me jkjk rerun the kit it happened to me and it now works perfect <3
Sent from my Inspire 4G using xda premium
HTCinspiration said:
He never said it was bricked..
Click to expand...
Click to collapse
HTC sorry I read bull**** and that is what I answered!! I was at the office and made a quick reply...just one thing to add, the phones bricked that I have seen until now, were never consequence of the Hack Kit but their users...
Issue has been resolved.
I have already fixed my problem. After many of hours playing around with my phone I was able to get it back to factory settings. The reason that the root messed up is that I had a bad sd card to make a gold image. I used a new 1 gb sd card that I had laying around and was able to achieve root without any issues. Thanks for all the responses.
Related
My sensation went off last night and wont come back on, no charging light no screen etc...
the only thing is usb does kinda pick it up as QHSUSB_DLOAD with no drivers to install, any ideas?
edit: never mind i now know this is bricked and a jtag needs doing....
Help! Same problem
I have no power to the device. Tmobile sent me a new sensation but i would like to try and fix the old one before i send it back, only have 5 more days.
Its not the battery or the sd since they both work fine in new phone.
Windows reads the same thing when on usb. No drivers. No power No nothing????
Can anyone help please or am i done for?
anarchyuk said:
My sensation went off last night and wont come back on, no charging light no screen etc...
the only thing is usb does kinda pick it up as QHSUSB_DLOAD with no drivers to install, any ideas?
edit: never mind i now know this is bricked and a jtag needs doing....
Click to expand...
Click to collapse
Could you explain what you did to cause this? I really hope you were messing with things other than what most people have done, otherwise, this could be a real problem for the rest of us.
Matt
Yes i would also like toknow what You did please
Sent from my HTC Sensation 4G using XDA Premium App
mrg02d said:
Could you explain what you did to cause this? I really hope you were messing with things other than what most people have done, otherwise, this could be a real problem for the rest of us.
Matt
Click to expand...
Click to collapse
+1
10Char
If you did brick there is a thred in the dev's that can and will show you how to unbrick and you can shop and decide on witch Rom you won't to go with look at it this way you have the best of both worlds good luck
Sent from my HTC Sensation 4G using XDA App
Had an issue today similar to yours, unlocked the bootloader today and kept the stock rom. Tonight I started deleting the bloatware, mainly using root explorer, no issues really. Used titanium backup to "force remove by exploit" I think its called. Did that and phone went black, tried powering back on, pulled battery etc, nada.
Ended up plugging device to usb charger and booted into bootloader, rebooted from there and its fine.
I ran into this tonight. See this thread:
http://forum.xda-developers.com/showthread.php?t=1198585
Short story -- Clockwork Recovery is bugged and won't charge the phone. Your battery level is too low to power on, so you need to use another method to get some power into it.
I did this:
http://dl.dropbox.com/u/15034469/tmp/recovery_fail.jpg
And yeah it's a lame problem.
Ahh, so this is not really a bricked phone, but a case of CWM dead battery! Good to know, as its an "easy" fix then. I was afraid that the phone, simply S-off and perm rooted, had somehow crashed permanently.
Matt
Straight Bricked
For me its not the battery, when tmobile sent me a new sensation i used my old battery, sdcard and sim and the battery still had around a 75% charge. I cant boot from usb i cant do anything. Its completely dead.
As for what i did?
I had been flashing multiple roms and kernels for 2 weeks. Overclocking, undervloting bla bla. No issues a wipe and flash couldnt take care of. I think i did a wipe and flash of a new rom and thats it. Dead. Wish i could remember exactly what it was. I guess im gonna mail it back since i have a new one and probably get charged full retail if they see its s-off and root.
blackstarnino said:
I had been flashing multiple roms and kernels for 2 weeks. Overclocking, undervloting bla bla. No issues a wipe and flash couldnt take care of. I think i did a wipe and flash of a new rom and thats it. Dead. Wish i could remember exactly what it was. I guess im gonna mail it back since i have a new one and probably get charged full retail if they see its s-off and root.
Click to expand...
Click to collapse
Ahh..So it wasnt the silly CWM ordeal then. That sucks!
Try to pinpoint what you were doing right before this happened. Were you wiping something? (what were you wiping) Were you flashing a ROM? (What were to flashing)
Try to provide more details, as I am sure some of the devs here will be looking to jump all over it shortly.
EDIT: Were to making sure to check that the ROM you were flashing was meant for your version of the phone as well as the files not corrupted? I know it sounds silly, but its something to rule out.
Matt
happened to me too on two batteries. I believe that it is due to overclocking the cpu. because the battery stats are calibrated for a slower CPU speed, it drains it past the failsafe point to pure failure. CWM will recognize CPU for the given ROM. i flashed back to S-ON and regular RUU 1.29 and charging my batteries again for the correct CPU + battery stats. wish me best of luck
Wow, am i that stupid
Not positive but i think i figured out what i did. Something really stupid.
I think i flashed: [Desire] InsertCoin CM7/STOCK 1.1.0
So am i fully bricked?
Gotta put the phone in the mail tomorrow.
Do you think they will see that its s-off or if its (truly) bricked can they not?
Nino
blackstarnino said:
Not positive but i think i figured out what i did. Something really stupid.
I think i flashed: [Desire] InsertCoin CM7/STOCK 1.1.0
So am i fully bricked?
Gotta put the phone in the mail tomorrow.
Do you think they will see that its s-off or if its (truly) bricked can they not?
Nino
Click to expand...
Click to collapse
They'll know....
actually... having worked in a few cell phone repair / refurbish facilities... i can tell you that they won't even look. they just plug the phone up to their bench and it overides everything and does a fresh flash. from there they just replace plastics to make it look like a brand new phone. if they are unable to flash it at the bench, they replace internals. so relax... no one will know or care what you did to it. these places get thousands of phones a day. and each tech at the bench has a quota to get through.
Thanks for your feedback guys. Shipping it off now...
Still cant believe it. Still have my n1 from launch day and it took everything i could throw at it. Still kicking like a beast. **** my g1 is still running cm4 i think lol.
anarchyuk said:
My sensation went off last night and wont come back on, no charging light no screen etc...
the only thing is usb does kinda pick it up as QHSUSB_DLOAD with no drivers to install, any ideas?
edit: never mind i now know this is bricked and a jtag needs doing....
Click to expand...
Click to collapse
I'm in the same situation. This sucks. I tried to get back S-ON. Did you receive a new phone?
So you flashed a desire ROM.... Well no ****...
Sent from my Transformer TF101 using xda premium
This is going to be long!
If anyone has insight to this would be appreciated
Precursor: I am on CM9 nightly (7-27-12) with 6.0.1.0 non touch recovery (NS4G)
So last night I go to open my opera web browser and it would flash like it would open and instant close (no error message). I say OK thats weird and decide to reboot. Upon rebooted I am greeted with never ending amount of FC's from every app and service imaginable. I again say OK EXTREMELY weird and decide its time to restore my backup from yesterday.
I reboot in recovery and what do I get greeted with? Unable to mount /sdcard! Long story short after scouring google for about an hour I find that if I do a fastboot oem lock/unlock I should get back up and running. Thankfully that works and I install the newest 7/31 CM9 nightly.
I wake up today without my phone alarm going off when it should. Weird huh? I go to open the clock and get a FC from the clock application. Reboot and it works just fine. OK weird again.
Go to work and leave my phone on the counter to help a customer. I come back to the desk and my phone is in recovery mode? Uhhh what? I reboot the phone and it says "encryption unsuccessful" and the phone needs to wipe data and reboot to continue use...
I decide WTF why not, not like I can use it. At this point I'm worried though. The phone reboots to recovery and I guess does a data wipe (takes 3-5 mins) and reboots. Now I am stuck on the CM9 bootscreen and won't go past.
I have some ideas as to get the phone (hopefully) back up and running. Just curious what this sounds like to anyone more knowledgeable then me (especially the part where it tried to encrypt my phone without me touching it!)
Any thoughts or help is appreciated!
Edit: I tried copying files to sdcard from recovery using mount usb storage. The files copy over and as soon as I leave the mount menu and go to install the zip files WHICH I SAW ON THE SDCARD they ARE NOT THERE anymore.
Edit2: It still lets me install the CM9 7/31 nightly which I had saved on the phone yesterday. Even after wiping everything and reinstalling the ROM I can't get past the CM9 bootscreen
Edit3: Tried fastboot, odin, nothing works. Even after odin I still get the CM9 boot screen. Pretty sure something is messed up to the point of I need a new phone. FML!
YESS!!!
YES I WANT ATTENTION.
I Have exactly the same. Mother of smartphones Somebody help us!
Its the internal Memory thats messed up yes, But Please somebody fix this Bullcrap. We don't have the knowledge but I will gladly donate to you who fixes it!
I just bought a brand new screen for my phone and I don't freaking want to buy a new Phone At the moment, So if you find a way to help us then let us know since that could be lifesaving right now.
Pretty sure I've given up. Everything I've tried has failed... looks like it might be gnex time.
NYYFan325 said:
Pretty sure I've given up. Everything I've tried has failed... looks like it might be gnex time.
Click to expand...
Click to collapse
Have you tried just going back to the stock rom/recovery/bootloader with the samsung application?
ronnygunz said:
Have you tried just going back to the stock rom/recovery/bootloader with the samsung application?
Click to expand...
Click to collapse
I would Love to get an link to that. if it helps us out i'd sh1t goldbricks. seriously.
Moonystorm said:
I would Love to get an link to that. if it helps us out i'd sh1t goldbricks. seriously.
Click to expand...
Click to collapse
I couldn't post the link because I have less than 10 posts here so I pm'd you. At least I hope I did. Let me know if you didn't get it.
Can you send me the PM as well. I know of the tool you are referring to but can't seem to find it anymore
NYYFan325 said:
Can you send me the PM as well. I know of the tool you are referring to but can't seem to find it anymore
Click to expand...
Click to collapse
I tried to send it, I hope it worked but it doesn't show up in my sent messages so I am in the dark.
Stock ROM. All the way back to Gingerbread.
http://forum.xda-developers.com/showthread.php?t=1572307
Well nothing officially works
The samsung simple dl tool just says "error" when I hit "start download" nearly immediately. Now I have no recovery or anything. Going to sprint right after I get out of work to get a gnex
NYYFan325 said:
Well nothing officially works
The samsung simple dl tool just says "error" when I hit "start download" nearly immediately. Now I have no recovery or anything. Going to sprint right after I get out of work to get a gnex
Click to expand...
Click to collapse
Ugh... I'm sorry people Who will get to our problem. Paid samsung services can Help. Nothing else. I be a smart guy and do like NYYFan here and get a galaxy nexus. thank You everyone for help. i set up 48hours for anybody to help me or i get a new device. Might sound rude but its a choice i made.
-Moon
I HAD THIS SAME EXACT PROBLEM
Temporary solution: heat the phone up with a hair blow dryer. get it hot but not so hot that it melts things. it will be able to boot up and work. I used this method so i could copy my sd card to my computer and wipe everything off
Permanent solution: turn your phone in for repair. there is no remedy to fixing this. apparently the circuit board or chip is bad and you can't fix it.
Luckily I had best buy black tie protection and I am waiting on my new replacement phone.
NicholasQ said:
I HAD THIS SAME EXACT PROBLEM
Temporary solution: heat the phone up with a hair blow dryer. get it hot but not so hot that it melts things. it will be able to boot up and work. I used this method so i could copy my sd card to my computer and wipe everything off
Permanent solution: turn your phone in for repair. there is no remedy to fixing this. apparently the circuit board or chip is bad and you can't fix it.
Luckily I had best buy black tie protection and I am waiting on my new replacement phone.
Click to expand...
Click to collapse
I work in a computer repair shop and going by that solution...sounds like a problem I may be able to repair using a similar method as some of the board-level repairs I do pretty often...anyone want to send me a dead lab rat? Lol
Sent from my Nexus S 4G using xda premium
Xaelius said:
I work in a computer repair shop and going by that solution...sounds like a problem I may be able to repair using a similar method as some of the board-level repairs I do pretty often...anyone want to send me a dead lab rat? Lol
Sent from my Nexus S 4G using xda premium
Click to expand...
Click to collapse
You can have mine lol x) And Yep i fix computers for friends and so on their friends and this sounds like Nvidia was behind the chip... xD
It wouldn't matter who actually makes a chip if the heating it up is a temporary fix. That is a OEM issue. Basically think xbox360 rrod with the warped boards the solder melting/failing and the chips get loose etc.
Unless heating up failed flash storage temporarily makes it work. Which I doubt is the case but don't actually know. Brings back memories of putting failing HDD drives in the freezer though.
Well this is my official goodbye to the Nexus S forums (not like anyone cares haha). Just got my shiny new Galaxy Nexus. Have a great night everyone and happy modding!
NYYFan325 said:
Well this is my official goodbye to the Nexus S forums (not like anyone cares haha). Just got my shiny new Galaxy Nexus. Have a great night everyone and happy modding!
Click to expand...
Click to collapse
Ugh. Congraz. xD
Try Adam outler unbrickable mod for nexus s
Sent from my Nexus S 4G using xda premium
http://forum.xda-developers.com/showthread.php?t=1397393
Sent from my Nexus S 4G using xda premium
Unfortunately that is good only if software screwed up your phone. In my case and I'm sure others when it is hardware failure, that won't work :\
Was playing with my ATT One X, got root happy with it today, flashed an international ROM because I didn't read like I should have, got QHSUSB_DLOAD'd, phone won't turn on, no lights, just makes the USB noise when I plug it into the computer, blah blah blah, same old story. Spent all day reading threads from other people that have had the same issue here, and since I was on 2.20, it appears as if I'm pretty much FUBAR until some wizard much smarter than I figures out another linux hack to fix it. It sucks, I'm stupid, I know, but it's not my main device so I'm not hitting the panic button just yet. What I'm wondering is tho, is there a way to access my internal memory, even if I have to take apart the device? I've used the phone as a camera a lot so I've got a lot of pictures and some videos I'd like to get back. Is this possible with how bricked my HOX is? If not I guess I'll just have to wait until someone gets the QHSUSB_DLOAD fix working with 2.20.
Thanks!
Weston
Yep no way as of now sorry :/
a box of kittens said:
Yep no way as of now sorry :/
Click to expand...
Click to collapse
Bummer. Guess I'll just have to cross my fingers and hope someone makes a fix for it with 2.20.
Thanks tho,
Weston
Google mobile tech videos they are the only ones with a working jtag for our phone right now only thing is u gotta send it to them
http://youtu.be/yjGTP-AmEtA
Try this and see if it works for you:
http://forum.xda-developers.com/showthread.php?t=1966850
Otherwise you can call HTC and have them check the warranty. I had the same error and called them, they honored the warranty on it. I sent it in, and they sent it back all fixed up. It was a very easy process and HTC CS reps were very very nice.
If it isn't under warranty still go with what xstokerx said and send it in for jtag repair. That's about your only other option.
Here is my thread, it may help you.
http://forum.xda-developers.com/showthread.php?t=2071358&highlight=wip
Okay, before I get started, I am no noob when it comes to adb, linux, qpst, and htc phones. That being said, I was recently making and flashing several splash screens for my AT&T one x. unfortunately, I made a typo whle "dd" pushing the last one to my phone. In the typo I sent the splash screen to blk0p4 instead of 0p14, so when I typed in "adb reboot" my phone shut down, and never came back up. It now shows as QHSUSB_DLOAD in windows. I've spent countless hours searching xda, android central, and various other sites for a possible fix. I've tried the unbricking project, Jet method, and everything else I can find. The device shows up in linux, but my partitions do not show. So basically what I'm looking for is anyone with any fresh ideas on how to get it back to life. My warranty is void, as my phone is disassembled right now, so the battery didn't die while stuck in this mode. I'm really hoping I can escape this without sending my phone into jtag service. Anyone with any ideas to help? If I'm not around on XDA, you can usually always get me on gtalk @ [email protected]. Hopefully someone with more knowledge than I, can help me get my phone back in working order.
It sounds like you're on hboot 1.14? p4 is the extended partition table, but I assume you know that. You're in the same boat as people who flashed Tegra 3 roms.
AFAIK, there is no fix for that sort of brick short of jtag. A lot of smart people have been working on it without success.
iElvis said:
It sounds like you're on hboot 1.14? p4 is the extended partition table, but I assume you know that. You're in the same boat as people who flashed Tegra 3 roms.
AFAIK, there is no fix for that sort of brick short of jtag. A lot of smart people have been working on it without success.
Click to expand...
Click to collapse
yes, the phone came to me with hboot 1.14. And the only thing I knew about 0p4, was that I had to hex edit it to htcdev unlock, before s-off. Everything keeps pointing to jtag being the only option to fix my phone.
Correct. Jtag is the only way you would be able to revive your device.
Sent from my HTC One X using xda premium
Myrder said:
Correct. Jtag is the only way you would be able to revive your device.
Sent from my HTC One X using xda premium
Click to expand...
Click to collapse
kind of figured that. I've searched everywhere trying to find another fix. Looks like I'll be paying $65 to send my phone in for jtag...
Mods can delete this thread if you wish.
Well I've finally done it. Hard brinked my phone. wont turn on wont flash any notification lights at me. no response at all. Tried to get back to stock through RUUing, definitely did something wrong. because now the only thing that hints my phone has any life in it, is the small connection sound when hooked up to usb to my computer. Just the sound though. No actual picture of device connected in "My Computer", and nothing on the phone comes up.
Im hopping there is still hope out there but I think it's lost. *que in Star wars quote.
any ideas?
korext said:
Well I've finally done it. Hard brinked my phone. wont turn on wont flash any notification lights at me. no response at all. Tried to get back to stock through RUUing, definitely did something wrong. because now the only thing that hints my phone has any life in it, is the small connection sound when hooked up to usb to my computer. Just the sound though. No actual picture of device connected in "My Computer", and nothing on the phone comes up.
Im hopping there is still hope out there but I think it's lost. *que in Star wars quote.
any ideas?
Click to expand...
Click to collapse
I'v research a bit and havn't found anything too promising, so if there has been any updates on un-bricking phones in the last few months, it'd be great to know..
First I'm going to kindly ask that you change the title of this topic.
Second I'm going to ask what you did prior to the phone becoming unresponsive ie. What ruu?
Third some details about your phone as in is it s-off what hboot do you have.
XDA Moderator
Did you try to run the 3.18 Ruu with s-on and superCID? If you did, jtag or replacement are your options.
Sent from my evita
RollTribe said:
Did you try to run the 3.18 Ruu with s-on and superCID? If you did, jtag or replacement are your options.
Sent from my evita
Click to expand...
Click to collapse
i just made the same mistake the other day.. its being sent into repair right now. im just hoping they have no way to tell HOW the phone got bricked and my warranty isn't void.. here's the link to my thread maybe some helpful info for the OP http://forum.xda-developers.com/showthread.php?t=2393960
but as RollTribe said.. only way to fix it is JTAG or replace motherboard lol.