[Q] LeeDrOiD V3.3.3-Port-R5 USB Issues. - Desire Q&A, Help & Troubleshooting

[Q] LeeDrOiD V3.3.3-Port-R5 USB Issues. - Desire Q&A, Help & Troubleshooting

Yes, this is one n00b 1st. post... but bare with me, as I (think) I have done all the right things.
The Issue:
I flashed the LeeDrOiD HD V3.3.3-Port-R5 A2SD++ to a HTC Desire (Bravo, Root, S-off, Full Wipe).
It is fast and seems to work really well, but there is one major problem: The phone do not recognized USB connection.
I plug the AC charger in, and it takes 2-5 min for the phone to start charging, and the phone seems to think of it as USB charging, not AC...
Plucking the phone to the PC gives error form windows about "unknown USB device", and the phone newer seems to register the PC: It just go to USB charging, after 2-5 min.
The first flashing of the LeeDroid rom caused a USB Brick, that FastBoot "rebootRUU" and "enableqxdm 0" fixed.
Don't know if that have anything to say.
Yes, I guess n00b problem, and I guess all is explained 117 times.
But please... point me to the right threads.

You have what's known as a USB brick. Basically, you had two problems. Your first was that your phone did not recognise that there was an SD card inserted, you have now fixed that. Unfortunately however you do now have a USB brick, which gives exactly the problems you describe. Do some searching on the forum, there's several threads explaining how to fix this.

try this thread
http://forum.xda-developers.com/showthread.php?t=691639&highlight=usb+brick

Thanks a bunch!
I vent to that same thread earlier, when the SD card did not work, but did not find a fix fore it there.
It is all starting to make sense now.
I'l try flowing the guide and, and see if I can make it on my own again.
Thanks Again.

Both SD and USB Un-Bricked now.
Happy Happy!
Thanks.

I've been there and done it. I had EXACTLY the same issues as yourself and on fixing the SD card issue I thought brilliant, "I am legend".... It was only after trying to connect the phone to the PC that I discovered I was not. I was only half way to fixing my problems. I did however make a text file detailing what I did in case it ever happened again and here it is (you will need an image file however which can be got from the thread linked above) :-
============================================
To gain access to SD card:
Put phone into fastboot mode (back button + power)
In CMD, go to dir C:\Android\android-sdk\Tools
Type: path C:\Android\android-sdk\Platform-tools)
Input "fastboot oem enableqxdm 0"
Before trying the stuff below, try to run this command first - fastboot oem eraseconfig
I had already done the below which didn't work then running that it suddenly did work so try it first, if no joy do the below and if still no joy then try the command again.
ALSO FOUND THIS TO TRY -
So I download the HTC hboot stock partition, flashing through fastboot command, and do 'fastboot flash misc mtd0.img' reboot... and ta...da ... my USB connection fix, Bluetooth is working too, testing with some other rom, and all fine ...
AND -
1.download recovery *.img file.
2.put it in androidsdk\tools folder.
3.boot in to fastboot by pressing back button and power button together.
4.run :-
fastboot flash recovery *.img
===================================================
EDIT: Ah you fixed it whilst I was replying (was on a phone call). Nice one fella.

Related

(SOLVED) Just another USB brick...

I ****ed up my phone somehow and I don't know how to fix it. I was going to install a new Rom, was wiping data and went to partition my SD card to try A2SD. I couldn't do it in clockwork recovery so I thought I'll connect the phone to my PC and run Paul's recovery from r5 rooting method. The problem was that somehow both recovery's were running and I'm not sure what I pressed but now my phone can't recognize the SD card, nor can the PC recognize the phone when I connect it. The Rom can boot up, but somehow it's not working properly, I can't make/receive calls but for example WiFi works. I guess its not bricked since Android launches but I have no idea how to fix what I messed up. Somebody please help me

Your device is usb bricked, search for usb brick in the development, this can be easily fixed.

Thanks, I found it, but I'm stuck at step 1: "Enable the SD Card functionality. Boot your phone in FASTBOOT mode (back + power), and enter this command: 'fastboot oem enableqxdm 0' . This will re-enable your SD card."
Where should I enter that command ? Thanks.
EDIT: I fixed it ! Thank you so much. I knew it will be easy to fix just I couldn't think clearly and forgot about the USB bricking issue

[Q] PLEASE HELP!!!!!!! i think i bricked my Evo

My Evo won't charge unless it is turned off. When the phone is on, the usb won't give me any mode option. Phone doesn't see the sdcard. PC won't see the phone. I have usb debugging checked. Device manager gives me three qualcomm CDMA Technologies and can't find drivers. Everything on the phone works except for apps using the sdcard. The phone says "SD Card removed" at the top left of the pulldown bar. With the vol down and power the phone will read the PC36IMG.zip of the sdcard and load and run it. After rebooting it still doesn't recognize the sdcard. I followed all steps in this previous thread:..............................................................................................................................................................................................................
These fixes require the Android SDK and very basic ADB knowledge. You can copy and paste for most.
Make sure in device manager the driver for fastboot is installed (Win 7 downloads them automatically)
For USB fix
Download the flash_image & mtd-eng.img attached, unzip them and put them on the SD card before starting
SD Card Fix
Press & hold vol down and power on the phone
Select fastboot by pressing the power button
ADB commands
fastboot oem enableqxdm 0
fastboot reboot
That should fix your SD card not being detected........................................................................................................................................................................................................................................................................................................................
i get all the way to to Command Prompt and enter the correct dir where my ADB and Fastboot are, then i proceed to type fastboot oem enableqxdm 0. Then it says waiting for device. Help please! Im stuck.

slbyrd said:
My Evo won't charge unless it is turned off. When the phone is on, the usb won't give me any mode option. Phone doesn't see the sdcard. PC won't see the phone. I have usb debugging checked. Device manager gives me three qualcomm CDMA Technologies and can't find drivers. Everything on the phone works except for apps using the sdcard. The phone says "SD Card removed" at the top left of the pulldown bar. With the vol down and power the phone will read the PC36IMG.zip of the sdcard and load and run it. After rebooting it still doesn't recognize the sdcard. I followed all steps in this previous thread:..............................................................................................................................................................................................................
These fixes require the Android SDK and very basic ADB knowledge. You can copy and paste for most.
Make sure in device manager the driver for fastboot is installed (Win 7 downloads them automatically)
For USB fix
Download the flash_image & mtd-eng.img attached, unzip them and put them on the SD card before starting
SD Card Fix
Press & hold vol down and power on the phone
Select fastboot by pressing the power button
ADB commands
fastboot oem enableqxdm 0
fastboot reboot
That should fix your SD card not being detected........................................................................................................................................................................................................................................................................................................................
i get all the way to to Command Prompt and enter the correct dir where my ADB and Fastboot are, then i proceed to type fastboot oem enableqxdm 0. Then it says waiting for device. Help please! Im stuck.
Click to expand...
Click to collapse
Have you tried to flash back to stock rom?

hmm...argh!!
thanks for responding. I just finished to an unroot. My phone does boot up fine now and there is no more "sd card removed" error, but my phone still doesn't see my sd card. And it keeps on powering down and then vibrating 5 times, then the led indicator flashes green and i cant restart my phone without pulling the battery and replacing it. I have a card reader on my pc (im running vista). The pc reads it just fine. ???

sl22857 said:
thanks for responding. I just finished to an unroot. My phone does boot up fine now and there is no more "sd card removed" error, but my phone still doesn't see my sd card. And it keeps on powering down and then vibrating 5 times, then the led indicator flashes green and i cant restart my phone without pulling the battery and replacing it. I have a card reader on my pc (im running vista). The pc reads it just fine. ???
Click to expand...
Click to collapse
Hmm, that is strange. So your pc reads the contents of the card just fine, and when you run a 'disk check' on the sd card, it turns up no errors? What were you doing on the phone when this first started, or was it out of the blue? So since your Evo doesn't see the sd card, then formatting it using the phone isn't an option I presume? What about formatting it using windows (fat32), then putting it in the phone, is that something you tried already?
As far as the phone vibrating 5 times and then you get the blinkng led, i believe that is the phone kicking itself into diagnostic mode. I'm not really clear as to what exactly that is, or why it would be happening, but I am sure that it is in diagnostic mode at that time. So you said you unrooted it, and you're currently on stock, s-off ROM right now? Do you still get the same error when you try the fix that you were initially trying to execute?

And i cant flash any ROM's due to the fact that my computer wont recognize my phone, therefore i cant access the ADB Shell. This is so frustrating!!!

i was in the process of flashing a rom and thats when the problems started. I haven't tried formatting the SD Card. I dont see how that would help me, because i can access the card and its contents just fine but my phone wont recognize there being an sd card in the phone. It seems to be a trifecta of evil!!! LOL 1.) PC doesn't see the phone 2.) Phone doesn't see sd card 3.) i can't flash anything because i can do nothing in the ADB Shell. I initially went the Unrevoked3 route of rooting and then i went the way of flashing the PC36IMG file that you put on the root of the sd card and then renaming it. The guy in this thread seemed to have the same exact issue and he figured it out. I dont know what im doing wrong.
Originally Posted by airauto View Post
Ok thanks, I finally got it all working. After a week of learning about ADB, Terminal and Fastboot commands not to mention the structure of the Evo file system, charging, usb and sdcard are all working thanks to everyone contributing to the forum.

well i thought i did an unroot but it still says SHIP S-on???

i am formatting the sd card now. what do i do once its done formatting? I've been at this for 22hours now and my brain is officially fried!!

sl22857 said:
i am formatting the sd card now. what do i do once its done formatting? I've been at this for 22hours now and my brain is officially fried!!
Click to expand...
Click to collapse
Once you format it, before you put anything else on the card, I would put it back in the Evo, and see if it will recognize it, totally fresh from the format. If that still fails, then I'm out of ideas. I'm sorry, hopefully someone else can offer some advice if that still doesn't work. I would consider dropping by sprint for some service if you can't get it handled.
Is it still giving you the 5 vibrates? And also, if it says s-on, you are unrooted, Forgive my previous typo.

thanks. i'll let you know what it does after the format. hopefully this works. (fingers crossed)

sl22857 said:
thanks. i'll let you know what it does after the format. hopefully this works. (fingers crossed)
Click to expand...
Click to collapse
Good luck dude. I hope that works for ya, I'll do another quick search and see what I come up with.
Also, did you try this again? After you unrooted? Same results as before, "waiting for device?"
These fixes require the Android SDK and very basic ADB knowledge. You can copy and paste for most.
Make sure in device manager the driver for fastboot is installed (Win 7 downloads them automatically)
For USB fix
Download the flash_image & mtd-eng.img attached, unzip them and put them on the SD card before starting
SD Card Fix
Press & hold vol down and power on the phone
Select fastboot by pressing the power button
ADB commands
fastboot oem enableqxdm 0
fastboot reboot
That should fix your SD card not being detected

okay i figured out the sd card issue. too bad i didnt see this thread before i formatted.
"alright, it is done. i was putting it in recovery mode for the sd card, and i should have just stopped at fastboot and not put it in recovery. thanks all of you. you knew what you were speaking about, i just didnt follow the instructions correctly" (posted by airauto)
now my phone recognizes my sd card. whew. one down. thanks for your help anyways.

got the sdcard to be seen by the Evo but now its still rebooting after about two minutes and then vibrates 5 times. ?????

sl22857 said:
okay i figured out the sd card issue. too bad i didnt see this thread before i formatted.
"alright, it is done. i was putting it in recovery mode for the sd card, and i should have just stopped at fastboot and not put it in recovery. thanks all of you. you knew what you were speaking about, i just didnt follow the instructions correctly" (posted by airauto)
now my phone recognizes my sd card. whew. one down. thanks for your help anyways.
Click to expand...
Click to collapse
Glad you got that figured out. Didn't you backup your sd card to your pc before you formatted? Just copy everything back over to the card.

sl22857 said:
got the sdcard to be seen by the Evo but now its still rebooting after about two minutes and then vibrates 5 times. ?????
Click to expand...
Click to collapse
Wish I could help you on that, but any thread I've ever seen where people were having that problem, where it vibrates 5 times then goes black and the led blinks, the only resolution I ever saw (and I could be wrong, I'd do a search on google about that, quite a bit of stuff on there) was replacing the phone. I'm not sure of the cause of that. If there is a fix for it, xda and google should have it somewhere though. (but I still think replacing is the option for you)

[Q] Did I brick my desire?

Hi.
I was recently experiencing some problems with my desire and I believe that I might have rushed into bricking it.
I woke up the day of the bricking. I had just installed the newest version of GingerVillain (version 2.4). My phone had run out of power the day before so I started recharging it. After it had charged for a couple of hours I went to the market to update some apps. During the update my phone suddently rebooted. I thought that it was nothing and went back to the market and continued updating. A few minutes later it rebooted agian. It kept on rebooting with less and less time in between after each attempt until it chose to reboot at the splash screen continuesly.
This is when I thought of starting the phone in recovery and do a NAND restore. As I tried to enter the recovery mode the phone froze at a black screen. I pulled out the battery and retried a couple of times without success.
I read a little on the internet about ADB and tried doing some stuff but I kept on getting errors when running commands in the tools directory. At this point I was getting desperate because I needed the phone to work as I was expecting an important call. I tried flashing a new RUU (through the installer on my PC) while the phone was in fastboot (but without using any ADB and CMD stuff). After this installation almost had finished I got an error saying that the version of the rom wasn't the right one for my phone and the phone shut off.
Since then I haven't been able to boot it into bootloader or even boot it at all. Whenever I hold down power + volume down nothing happends and if I try only pressing the power button the phone vibrates and other than that nothing else happends. Not even the screen turns on.
I since then set up ADB and got it working. I then tried to see if the phone was still able to fastboot through the following commands:
Code:
adb devices
and
Code:
fastboot devices
but found that this was not the case.
Whenever the battery is in the phone though, the bottom of the phone starts to get warm, a little like it's actually using the battery to perform some actions or something. I was also able to recharge it through my computer.
I really need a phone and as it seems I have got my hands on a spare one, but only for a limited time. I'm really thinking of handing it in to the HTC Concept Store so they can send it to the repair department and hopefully get it back as fast as possible.

Its seems.. S-LCD Brick
try This
http://forum.xda-developers.com/showthread.php?t=748498
or
http://forum.xda-developers.com/showthread.php?t=831734

Ohh dude! I BELIEVE YOU MIGHT JUST HAVE SAVED MY LIFE! TY! TY! TY! TY!
My stationary just killed itself because of the hot weather and a little bit too much work. If I was going to hand in my phone and they couldn't repair it since I had "destroyed" it, I would be forced to buy a new one, and with that I wouldn't be able to afford new components for my stationary.
I will get right on with trying this method as soon as I get home and then I will give feedback asap. It will probably be the most fun "digging in the dark" I will ever do if it turns out to work.
I was almost sure I had killed my beautiful phone, and with it only being a couple of months old that would have been a pain in the ass.
Once again TY so much!!

I have been at this for almost 4 hours now and still no result. I believe the guides could have been more noob friendly. I've been to hell and back reading all the kinds of guides out there to get it all to work and now I'm tired and believe I won't be able to fix this, or atleast doesn't have the capacity to keep on trying.
I pretty much believe that I had this SLCD-brick, but trying out different RUU's is killing me inside and stealing my time. I'd rather just hand in the phone and recieve it as it was from the beginning again to start all over.
Trying to repair a smartphone with a blackscreen is is not something I have the capacity to do. Besides I have my recently deseased stationary computer to take care of as well.
I do have a goldcard, pushed the PB99IMG.zip file to my /sdcard/ through adb and tried starting up fastboot and do as described here.
But somehow I did not find any changes to the problem and the guide itself was wierdly written although the only guide I could find on this problem.
But now I'm giving up. I seriously just hope they will repair my device at no cost.
Regards,
Me

Man.. what happen when you connect your mobile to PC.. is it showing android device and under that bootloader interface.. dont lose hope... lets try some steps...
connect your mobile to PC and see in your device manager.. can you see android.. if yes than your driver are installed...
than remove the phone from pc.. take out the battery.. and put back battery.. and start by volume down and power.. and than after 10 sec just press power button again.. and connect to pc again... and cehck device manager.. and you should see the same if not.. than install your adb driver.
Point is.. install ADB driver.. when you are on hboot screen.. as well fastboot screen..
Than your RUU will detect your phone.

Well I tried all the steps for this. I can see the phone when booting it with the following combos:
Code:
1: Volume down + Power
2: Power
1: Volume down + Power
2: Volume down
3: Power
When using the first method I should as far as I can understand myself enter fastboot and the other one is recovery. Even when running the fastboot devices / adb devices commands in ADB it tells me what state my devices in, that is either fastboot or recovery. So that's for certain.
I tried running the following RUU when I had connected my device with fastboot:
RUU_Bravo_Froyo_HTC_WWE_2.09.405.8_Radio_32.43.00.32U_5.09.00.20_release_140022_signed.exe
The RUU found my device and I ended up with a 140 Error. I read in some guide that this error could be to blame of different windows drivers so I tried grabbing the rom.zip from the RUU (from Temp folder) and renamed it to PB99IMG.zip and put it on the phone. As I couldn't get access to my SD card since I can't see what's on my screen in fastboot and recovery mode I used:
Code:
adb push PB99IMG.zip /sdcard/
with the PB99IMG.zip placed in my tools folder for the transfer. It completed and now the PB99IMG.zip should be placed on the root of my sdcard.
As a notice I live in Denmark and the above RUU should as far as I can understand be the one I need and should as well be SLCD compatible.
When I try to trace the steps in the "not able to see your screen guide" placed here I get none of the desired outcomes:
http://forum.xda-developers.com/showthread.php?t=880268
I find the guide a little but confusing though. When to use the right commands to trace through a black screen fastboot/recovery and stuff isn't really "noob"-friendly.
When I tried using the following command I didn't get the desired result either:
Code:
fastboot oem gencheckpt
Which should return a HTC_<number> that could tell me whether my phone is branded or not, but instead resulted in an error. As far as I can remember I did make my sdcard a goldcard when I rooted my phone, without knowing whether I would need it, so this number should be irrelevant. So I kept on going at this point.
I have basicly tried everything that I can find guides for and have traced all the steps in detail as far as I understand the guides anyhow. I feel like at a dead end. I am having doubtsg whether the PB99IMG.zip is run when I boot my phone.
Having a clean slate (but still the PB99IMG.zip on the sdcard I have now tried the following:
Code:
Volume down + Power
Windows reported a connected Android 1.0 device and the Android Bootloader Interface.
Power once more (should now be in fastboot)
fastboot devices
confirmed the above, but using ADB devices only return a result if the phone is in recovery mode
So far so good..
I'll give this one more day which will be when I return home at 17:00 today. Then I'll head to tech support at my HTC Store.

Good.. i think you should try this RUU
http://shipped-roms.com/download.ph...9.00.32U_5.11.05.27_release_151783_signed.exe
As error 140 is for wrong bootloader.. so try this RUU.. n try to run RUU from PC rather than putting PB99IMG into sd..

jhonybravo4u said:
Good.. i think you should try this RUU
http://shipped-roms.com/download.ph...9.00.32U_5.11.05.27_release_151783_signed.exe
As error 140 is for wrong bootloader.. so try this RUU.. n try to run RUU from PC rather than putting PB99IMG into sd..
Click to expand...
Click to collapse
Okay. I'll try this and should I run it while in recovery like I did with the other one?
Does it matter if my SD card is out of the phone?
EDIT 1:
I tried with the sdcard out of the phone and with the RUU installed through windows. I now see a HTC Logo on the screen.. and an installing bar below the logo.. Seems like you were my divine interception mate.. ty a lot. I will write once the installation is done.. whether or not it succeeds.
EDIT 2:
My phone is now working. Booted with HTC Sense and a pin code request. Currently setting it up.
I guess I should now be able to re-root it again and get back to the state I was in before I SLCD-bricked it.. or what?
And in what way do I easiest remove that PM99IMG.zip file from the sdcard..? I booted my phone without the sdcard in it to avoid it running the PM99IMG.zip file..
One little question more.. I don't have any phone signal.. could this be to blame for the radio? I can connect to wifi though.. or can I simply run that other RUU I used earlier with the bootloader error to get back my signal?
So happy right now..
EDIT 3:
Nvm. I tried shutting down the phone, put in the sdcard, boot it up again. I found that the ADB push command on that PM99IMG.zip file didn't work. The file wasn't there.. and I suddently got back my signal. Only question is, can I now re-root it again and get back to my previous state without any problems?

Yes Ofcourse you can re root it.. with Unrevoked rooting wont be a big problem... and as soon as you root... just take a nandroid backup from it and be safe..
Enjoy the victory you earned... .. ;-)

[Q][SOLVED] Rooted Desire NOT CHARGING and NOT CONNECTING TO PC

For solution see this
Hi guys...I've got Problem...
This is What it is and what I've Tried so far...
I've posted this Problem at may places but didn't got results..
That's why I am ceating a new Thread..Also there is no Q & A Thread for this..which have good info
Here is What i tried.. and still the NOT CHARGING/LATE CHARGING and HEAVY BATTERY DRAIN PROBLEM..
1. Firstly I had runnymede from seb15 AiOv2.2 installed..Working Perfectly..
(See my signature for my phone's every single detail)
2. I used 4ext recovery..(before cwm).. I go to the recovery.. took backup..done perfectly..
Than rebooted.."STUCKED ON BOOTSCREEN"
"I pulled out the battery ..
Restarted with power+volume down button..
4ext recovery started after long delay..
msg:
"Error mounting your sdcard
Please check your sdcard's fat32 partition for errors"
"Error mounting your sdcard
Please check your sdcard's fat32 partition for errors"
2times...
at the table it is showing as
sacard fat32(fs) null(size) B(Free)....
I removed sd card..
repartitioned by gpartedlive..
my sdcard is 8gb sandisk..partition are 1gb ext4...remaining fat32(Both Primary)
Reinserted sd card..
again rebooted in recovery..
again same message"
This was the starting of the problem..
Now Waht i did is
1.connected to PC and in cmd typed this
adb devices
fastboot flash recovery recoveryCWM.img
fastboot reboot-bootloader
fastboot erase cache
fastboot oem enableqxdm 0
and sussefully done..
2. In fastboot
again first step and added
fastboot eraseconfig
rebooted..
3. got SD card mounted
4. Flashed CynogenMod7.1.0(Worked perfectly..even the battery was charging good...everything Normal)
5. I rewiped everything and flashed runnymede AiOv2.2 again..
Here the problem started of Battery Drain and Not Charging.
6. The Battery was NOT charging firstly...Than started charging 5mins after plugged in..
7. Charging is 1% per 15mins..(Which was almost10% per 15mins)
8. Battery Drain almost 10% in just 15mins..
Now to solve this I searched xda and googled.. foind something and did following..
reflsahed the hboot.
By first downgrading and than upgrading to cm7r2..
3.In fastboot Reflashed recovery CWM 2.5.0.7 than upgraded to 4.xxxx(ext4 and 3 supportable)
Again installed runnymede AiOv2.2 again..SAME RESULTS..
Tried Revolution v2.0 ... SAME RESULTS(the Battery thing..explained above)
Now what you guys suggest me to do NOW... to get my desire in NORMAL CONDITIONS
Huge Thanks for "ckpv5" for the guidence for solving "ERROR IN MOUNTING SDCARD"
and lot more people on xda which i searched threads..
I again NEED HELP!!!
One more thing ...
The time I was re flashing the hboot.... I pulled out the battery..the phone was connected with USB... Kit was still on...by the power from USB only...means the power was not going through battery but directly....
Can this be the cause of late charging problem....and the battery drain...
it happened with your phone???? That you forgot to pull out the USB simultaneously pulled the battery out....
By the way I've tried changing kennels... No luck stool the same problem
Thanks for your kind help

tried a different battery? only logical explanation...
have you tried charging the phone while switched off? what happens then?
also if this is a software issue did you make sure to do a full wipe before you flashed a new ROM? (from mounts 7 storage)

bortak said:
tried a different battery? only logical explanation...
have you tried charging the phone while switched off? what happens then?
also if this is a software issue did you make sure to do a full wipe before you flashed a new ROM? (from mounts 7 storage)
Click to expand...
Click to collapse
I've tried it charging in switch off mode..but.. same result..
Try changing the ROM.. same Result... as u can see above I've tried almost everything....

dont expect any1 to help of you write post the way you just did.
well what happens seems to me like:
-you had USB brick (batt drain, charging issues, no USB connectivity)
-you fixed it with 'fastboot oem enable qxdm 0' and 'fastboot oem eraseconfig'
-you flashed a (corrupted?) rom file again, and got USB bricked once again.
so just do fastboot cmds once again and you should be good.
however if i didnt understand you correctly, blame yourself for it, cause i dont feel like reading the 1st post ever again.
over and out.

dzumagos said:
over and out.
Click to expand...
Click to collapse
What this means is "call me back and don't call me" LOL

Does Bluetooth work (ie. stay on)? If not then it's a USB brick. And I'm with dzumardgos, I almost didn't bother spending some of my hard earned time on you.
Note also that loss of access and repair of the SD card issue is something completely different to charging and PC connectivity issues (USB brick).

Will see you soon with the solution.
Sent from my HTC Desire using XDA App

What are the possibilities that a ROM can be corrupted..Please mention..
By the way I was using this ROM(the v2.2) from i think 10 days..
Is it possible that a ROM which is corrupted would do this after that much time period..

[Q] Bricked help... Zero sign of life from tablet after trying many recovery threads.

I killed my KFHD8.9 by some naughty fastboot command.. Had twrp and some older CM rom (around 6 months old) but everything was buggy so I was trying to update when I did something I shouldn't have apparently (I think the last command was a fastboot command before everything died bc I was getting errors in recovery when trying to install the new CM rom from a zip file). Now, the kindle won't boot up, no screen, nothing. It just heats up if you connect it to charge is all I can tell.
I downloaded everything per instructions in several recovery threads but after any fastboot command nothing happens it just stays at "< Waiting for device >" prompt. Also, 'adb devices' doesn't report anything connected. All my other devices connect fine and I had fastboot and adb working on this kfhd too. I have also pressed the power button for 30s to make sure the kindle is off prior to connecting for fastboot command...
Can this be fixed? Sorry if this has been answered anywhere, but I have spent the last week sifting through every thread I could find. Thanks!

If it is not being detected by the PC at all as soon as you plug it in while off then you are going to need a soldering iron and a sdcard reader to fix it.

It is not being detected and the screen shows nothing at all..
Suppose I get my hands on the soldering iron and sdcard reader.. Can you recommend a link to good instructions on what to do? Would like to see what combination of surgery and black magic I will have to try in order to resurrect my tablet.. Thanks!

I can but I have to find the thread.
Edit: use the pinout on this http://forum.xda-developers.com/showthread.php?t=2581124
Plus the instructions for this: http://forum.xda-developers.com/showthread.php?t=2415870
Then substitute the files you flash with the ones for the 8.9" model, please don't plug it into windows and accidentally wipe the internal storage partitions, it won't be fun to fix.

Thanks for the links! That looks pretty intense though.. Will let you know if and how it goes..

Develop Bugs

welcome