Never knew this day would dawn on me, but I have no idea what to do right now
My phone boots in to fastboot just fine
- but, when i try to flash a boot.img or adb devices, they say waiting for device and blank
However, when i was in my system and i adb devices, my device serial showed up.
I really wanted to flash faux004b4, so i tried countless times trying to flash the boot.img in fastboot using different cables, but to no avail. This has never happened, in my 2 months of owning and flashing this device.
I know the steps to what I should be doing. But I just cant believe fastboot wont recognize the device.. ( in fastboot usb of course)
NOW...so i went into recovery, with viper X and faux004b3 installed, and formatted data, system and cache, hoping to resolve the problem, but no, it doesnt boot now..FML, so i tried relashing faux004b3 modules, and still doesnt work. Tried fastboot, nope, still says waiting for device.
SO, can anyone please help a senior member out, in saving my phone, and getting everything back in order.
BTW: Before, in fastboot, I was able to switch between fastboot and hboot while plugged in. But right now, I can only unplug my phone to get back to hboot. Maybe something here is the problem? I have no idea
PROBLEM RESOLVE: reinstalled htc drivers, and things worked themselves out. Sorry for adding one more thread to this place, but this could act as useful to many others who may face similar issues.
Related
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... .. ;-)
I've been running Cyanogenmod 9 for a couple of months, but decided to restore to stock so I can try out ICS and the new version of sense. I tried this a while ago but got stuck when when phone wasn't recognised via USB when connected to my laptop. Fastboot would change to Fastboot USB when plugged in, but the phone wasn't picked up. However, on this occasion I was able to restore Cyanogenmod without problems.
I tried this again yesterday with the same result regarding the USB connection, but when I restored Cyanogenmod it now just hangs on the boot screen and won't go further. Prior to this, when I ran the restore function in Clockworkmod, the phone would hang on the HTC splash screen with the beats audio logo on it. I did manage to get the phone to boot into recovery, but rather than the usual menu option I had a message something like "checking SD card..." and then nothing.
I am not sure where to go from here. The only thing I am wondering is if I tried to do this with the battery being too low, and the installation has failed because of this. I do want to go back to the stock OS, but not sure how to go about resolving the USB issue.
UPDATE
Partially solved the problem, in that I've managed to reinstall the cyanogenmod. Still stuck with lack of USB connectivity though.
Wrong section.....
Do you have the Fastboot files all in the same folder and do you have the HTC Sync drivers installed? You need that set up correctly to get a fastboot USB connection.
My suggestion is to simply "fastboot oem lock"
Then flash corresponding RUU to your current HBOOT. You can find out which RUU you need by typing "fastboot getvar version-main"
Hey There,
I'm sort of at my wits end with this issue.
I think I know what I've done wrong. I went to flash a new 10.2 rom, along with Gapps to my original Kindle Fire. However, I forgot to factory reset (more like I started it and then felt like it was taking way too long, so I skipped that step). Anyways, I flash the new roms and reboot the device. Now I'm stuck at the revolving Cyanogen logo (off center and going off the screen).
I forgot to install FireFireFire before any of this (yeah, two dumb things so far). So now when I connect the device to my computer, it shows up as this in KFU:
ADB Status: Online
Boot Status: Unknown
When I try to set fastboot via ADB command prompt commands, it says it can see the device, but can't do anything because it is "offline"
Meanwhile reinstalling drivers does nothing,
rebooting the device while KFU is < waiting for device > does nothing,
changing USB slots does nothing.
Device doesn't show up as connected right away via my PC, either. It takes until the CM logo is running before my PC notices it is there.
I've heard I'll need to buy a fast boot cable and that will instantly fix the device by getting me into TWRP again, but if I can fix this locally I would love to hear a method that doesn't involve waiting weeks for a cable to ship to me.
Thanks in advance!
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..
I was completely braindead doing too many things at once.
I was running the russion-bear stock-based rom with twrp.
Got to reading about the MM update, downloaded it, dropped it in the root folder without really thinking, and the phone rebooted and loaded twrp and then tried to install. I had to step away for a while, when I came back, the phone was black, and nothing fired up.
All I get is the double buzz when I hit the power button. No screen, nothing.
What is the best way for me to fix it?
Try plug it into your pc, fastboot devices to see if it is in fastboot or not. If yes, download the mm bootloader upgrade script and run it (find it somewhere on xda, like AICP thread). If no, use xFSTK and AFT http://forum.xda-developers.com/zenfone2/help/thead-bricked-phone-updating-to-mm-tips-t3452785
Thanks. Fastboot devices didn't show anything. However, I was able to use the intel moorefield soc utility to get back into fastboot and then reflash the phone. On a whim, I skipped the fastboot flash data and did all the other steps, and it's all working fine and I don't seem to have lost anything.
But now I'm fully stock, so the marshmallow update should apply, which I'm trying next.