Develop Bugs

[Q] incredible wont turn on? charge light works though

Hi thanks for reading this & hopefully helping out. I'm new here! and this is my first post.
Prelude:
So - I got my htc incredible with verizon (preloaded froyo 2.2) 3 days ago. first thing i did was 'rooted' with unrevoked. then a couple days later i wanted to try my hand with roms using the ROM manager.
So heres what I did:
-I found a rom called google app under the folder skyraider and installed that, which led to a really weird booting loop thing that eventually went through.
-I realized I only added an add on on skyraider so i went back to rom manager added the whole thing and cleared the cached.
my phone wouldnt go past the white htc incredible boot.
i freaked so i read some forums, put PB31IMG.zip on a fat32 formatted sd card and let it load in HBOOT. bad move. I also think i went into adb and typed something like fastboot erase boot...
situation Now:
-My phone screen stays blank / black / dark no matter what I do (battery pull / volume down & power, e.t.c)
-LED orange charge light works when I plug the htc incredible into a power source (computer / outlet)
-When I push the power button the charge light goes away and it vibrates
-When I connect it to a computer and 'push the power button' it recognizes that there is a usb connected to it
-using cmd and typing 'adb devices' gets a blank list even though the computer says it recognizes that 'a usb device is attached'
-The android phone nor the sd card shows up in 'my computer'
help?:
all i want to do is a hard factory reset. i have no files i need or want to keep
i just want to get this phone up and running again
thanks for reading

update
so i followed these instructions:
"Pull out the battery and put it back in.
Press and hold volume down and birefly press power on.
Keep volume down pressed for 5 seconds, then release it.
Count 20 seconds, then press the power key briefly once more.
You should now be in fastboot.
Connect your phone to the USB port and it should list it self when you execute fastboot devices."
Although my screen is blank when i go into cmd and type:
"fastboot devices" - I get one device listed as fastboot
i figured i can
run RUU from here or something? (i may have the wrong file but...)
when i run: RUU_Incredible_C_Froyo_VERIZON_WWE_3.21.605.1_Radio_2.15.00.07.28_2k4k_NV_1.50_PRL58006_release_143351_signed.exe
i get an error saying: ERROR [170] USB CONNECTION ERROR
*even though it obviously is connected via usb....
anyways adb still doesnt list any devices but fastboot does?
weird?

htc sync
so i installed htc sync
and now 'adb devices'
shows my device as in recovery?
however htc sync is all greyed out
apparently i need to go make my phone 'usb debugging'?
anyone know how to do that without actually going through the phone?

fiiixed
fixed- if anyways wonder
just download htc sync, update the drivers,
load into fastboot, and RUU should work

i dunno why i got that pro, i upgrade mt incredible from 2.1 to 2.2 android and now the phone cant charge anymore ???
my phone's details (now)
android version
2.2
Baseband version
2.15.00.07.28
Kernel version
2.6.32.17-g9a2fc16
[email protected]#1
Build number
3.26.605.1 CL264707 realease-keys
Software number
3.26.605.1
Browser version
Webkit 3.1
PRI Version
1.28_002
PRL Version
58005
ERI Version
5
Someone pls help me to solve this pro,i should downgrade to android 2.1 or do something....???

This happened because "Google Apps" is an add-on, not a full ROM. You need a ROM to install the Google Apps package on.

frostincredible said:
This happened because "Google Apps" is an add-on, not a full ROM. You need a ROM to install the Google Apps package on.
Click to expand...
Click to collapse
can u tell me more details,im still not understand... google apps caused that problem???

HTC Desire Stuck on HTC logo - Recovery not Working - NOT SOLVED!!

Not sure what happened, but my Desire won't get past the logo boot screen any longer, and RECOVERY mode in HBOOT just reboots the phone (regardless whether the SD card is installed or not). I can get into FASTBOOT however. I tried communicating with the Desire via adb console on my Windows XP system (after ensuring that I have the latest version of HTC Sync installed). "adb" commands do not recognize the phone (error: device not found). "Fastboot" commands do recognize the phone. (The command "fastboot devices", gives me this in return: SH09ER801629). So I'm not sure if my USB drivers are okay with adb, but the fastboot success seems to suggest so. (Also, "MyHTC" shows up under "Android Devices" in Device Manager).
The phone was rooted with ClockWork Mod using UnRevoked, and had Teppic stock Froy v.2.10.405.2 initd as the OS. Originally, it had TELUS-branded Eclair. I've downloaded the TELUS Froyo RUU.exe, but don't know how to install it on the phone, if I can't access RECOVERY mode or adb console. I don't think I ever set up a Gold Card, to my recollection. Also, I've been out of the smartphone scene for 6 months, and did no mods, no flashes, no program installs to my phone in that time. So it's a mystery as to why this is happening. But the phone had been acting up lately, rebooting by itself during a call every so often.
HBOOT screen:
Bravo PVT-3 SHIP S-ON
HBOOT 0.83 0001
RADIO 5.10.05.30

Cyanoid said:
Not sure what happened, but my Desire won't get past the logo boot screen any longer, and RECOVERY mode in HBOOT just reboots the phone (regardless whether the SD card is installed or not). I can get into FASTBOOT however. I tried communicating with the Desire via adb console on my Windows XP system (after ensuring that I have the latest version of HTC Sync installed). "adb" commands do not recognize the phone (error: device not found). "Fastboot" commands do recognize the phone. (The command "fastboot devices", gives me this in return: SH09ER801629). So I'm not sure if my USB drivers are okay with adb, but the fastboot success seems to suggest so. (Also, "MyHTC" shows up under "Android Devices" in Device Manager).
The phone was rooted with ClockWork Mod using UnRevoked, and had Teppic stock Froy v.2.10.405.2 initd as the OS. Originally, it had TELUS-branded Eclair. I've downloaded the TELUS Froyo RUU.exe, but don't know how to install it on the phone, if I can't access RECOVERY mode or adb console. I don't think I ever set up a Gold Card, to my recollection. Also, I've been out of the smartphone scene for 6 months, and did no mods, no flashes, no program installs to my phone in that time. So it's a mystery as to why this is happening. But the phone had been acting up lately, rebooting by itself during a call every so often.
HBOOT screen:
Bravo PVT-3 SHIP S-ON
HBOOT 0.83 0001
RADIO 5.10.05.30
Click to expand...
Click to collapse
if i'm not mistaken you can run the ruu and it should see the device if connected to pc with fastboot loaded.
as for trying to get back without losing data i'm new to all this so no idea
if you had run ruu on the phone and it was wrong type (i.e gsm ruu on cdma phone or other way round) then that explains the lack of capability.

Thanks for the tip. I ran the Froyo TELUS RUU.exe (should be the right type, as I have a Telus phone). It wouldn't work (in both main HBOOT screen and FASTBOOT screen). Gave me an "error 170". It could not connect to the phone, despite that I'm on Windows XP, that it says "Android Bootloader Interface" in Windows Device Manager, that it says "HBOOT USB PLUG" on the HBOOT screen when connected via USB, and that I am able to issue FASTBOOT commands from the PC. But I can't issue adb commands, so it appears I can only "partially" communicate with the phone from the PC.
Should I try CLEAR STORAGE, or could that fully brick my phone?
On the HBOOT screen, these are the status messages that load:
Loading...[PB99DIAG.zip]
No Image!
Loading...[PB99DIAG.nbh]
No Image!
Loading...[PB99IMG.zip]
No Image!
Loading...[PB99DIMG.nbh]
No Image or wrong image!
waynestir said:
if i'm not mistaken you can run the ruu and it should see the device if connected to pc with fastboot loaded.
as for trying to get back without losing data i'm new to all this so no idea
if you had run ruu on the phone and it was wrong type (i.e gsm ruu on cdma phone or other way round) then that explains the lack of capability.
Click to expand...
Click to collapse

USB Brick
For me, it sounds like a typical usb brick :/ I hope you still have rooted ROM. Search through this forum for unbricking guide.

Put the ROM.zip from the RUU on your SDCard but name it PB99IMG.zip and then boot with volume down again to enter HBOOT, it should give you the option to flash your phone back to factory default then.

HTC Desire Stuck on HTC logo - Recovery not Working - SOLVED!!
madcr0w said:
Put the ROM.zip from the RUU on your SDCard but name it PB99IMG.zip and then boot with volume down again to enter HBOOT, it should give you the option to flash your phone back to factory default then.
Click to expand...
Click to collapse
Thanks! I just tried that on the advice of another poster on another forum (before reading your reply), and that's the one and only thing that worked!
Especially when, after the RUU.exe wouldn't install, RECOVERY mode wouldn't work, nor adb, nor HTC Sync. Yes, I've lost my root access, but small consideration, considering I haven't lost my $500 investment! I'm sticking with stock now, as I'd rather not risk having a brick in the future.
As for what went wrong, I can't say for sure. But considering it took months after I had installed a ROM or otherwise modified the phone for problems to show up, I'm guessing it was probably the overclocking heating the chips. Which led to eventual random reboots during phone calls, and the eventual freezing of the boot screen, and subsequent inability of HBOOT to load PB99IMG.ZIP.
xda rocks, thanks to you and all those who took the time to reply.

sorry for delayed responce. I'm sure you had already found a solution by now but in the off chance you didn't.
you have to load fastboot not hboot.
from a power off state hold back button and power on phone. this will load fastboot and ruu will find device when run.
Cyanoid said:
Thanks for the tip. I ran the Froyo TELUS RUU.exe (should be the right type, as I have a Telus phone). It wouldn't work (in both main HBOOT screen and FASTBOOT screen). Gave me an "error 170". It could not connect to the phone, despite that I'm on Windows XP, that it o Image!
Click to expand...
Click to collapse

Fastboot will only work in Fastboot. ADB will only work when phone is booted and USB Debugging is on.
I don't know that as fact, I only know it from personal experience.
Use Fastboot to flash a new ROM, or at least a new recovery image. If you can get into Fastboot, you 'should' be able to fix your phone.

expza said:
Fastboot will only work in Fastboot. ADB will only work when phone is booted and USB Debugging is on.
I don't know that as fact, I only know it from personal experience.
Use Fastboot to flash a new ROM, or at least a new recovery image. If you can get into Fastboot, you 'should' be able to fix your phone.
Click to expand...
Click to collapse
+1 There is a good guide to fastboot commands on the android wiki:
http://android-dls.com/wiki/index.php?title=Fastboot
Should be a case of wiping system, data, cache, then flashing recovery image. Then boot into that and restore a backup or flash a rom.

Cyanoid said:
Thanks! I just tried that on the advice of another poster on another forum (before reading your reply), and that's the one and only thing that worked!
Especially when, after the RUU.exe wouldn't install, RECOVERY mode wouldn't work, nor adb, nor HTC Sync. Yes, I've lost my root access, but small consideration, considering I haven't lost my $500 investment! I'm sticking with stock now, as I'd rather not risk having a brick in the future.
As for what went wrong, I can't say for sure. But considering it took months after I had installed a ROM or otherwise modified the phone for problems to show up, I'm guessing it was probably the overclocking heating the chips. Which led to eventual random reboots during phone calls, and the eventual freezing of the boot screen, and subsequent inability of HBOOT to load PB99IMG.ZIP.
xda rocks, thanks to you and all those who took the time to reply.
Click to expand...
Click to collapse
can u plz help me frm with post u solved ur probs....i m stuck too

1st Post, got my htc desire this morning and after researching for a long time already knew i wanted to root my device.I followed the instructions on this site.[HOWTO] Root Your Desire In 1 Click With UnrEVOked! *UPDATED 20/7* - xda-developers I used unrevoked3, and rooted the device. no trouble Ive backed up the device with titanium backup. Placed cyanogen onto the 4gb sd card which came with the phone.Power off the device. Rebooted whilst holding the volume down button. Got the options up. Navigated to recovery and selected it with the power button. The screen goes blank. The o2 screen comes up saying welcome and thats it, it freezes. I have to pull the battery out of the back in order to reset the device and then it starts up perfectly normal. Tried accessing recovery mode using the clockworkmod but i get the same result.All of the points on the link above were followed. Im pretty much right at the bottom! still researching the net for the answer but im now in need of additional

Does your phone get hot and overheated during the htc logo? It did so to me and it turned out to that my CPU had melted and overheated. Take it to your retailer and they will fix it for free because it's not your fault, it's the phone that overheated.

Try this:
-download this with ur pc and rename it a PB99IMG.zip (not PB99IMG.zip.zip ok?)
-then put it on the root of ur sdcard (not in some folder) through an sd card reader
-ensure the battery is charged much than 30%..better more
-with the phone off (remove battery and put again) press and HOLD the volume down key and press (still holding the volume down key) and hold the power button..hold both and wait to enter in the hboot
-there wait a bit, and it will ask to u if u want apply the update, select yes with the volume keys and confirm with power button

awayra said:
1st Post, got my htc desire this morning and after researching for a long time already knew i wanted to root my device.I followed the instructions on this site.[HOWTO] Root Your Desire In 1 Click With UnrEVOked! *UPDATED 20/7* - xda-developers I used unrevoked3, and rooted the device. no trouble Ive backed up the device with titanium backup. Placed cyanogen onto the 4gb sd card which came with the phone.Power off the device. Rebooted whilst holding the volume down button. Got the options up. Navigated to recovery and selected it with the power button. The screen goes blank. The o2 screen comes up saying welcome and thats it, it freezes. I have to pull the battery out of the back in order to reset the device and then it starts up perfectly normal. Tried accessing recovery mode using the clockworkmod but i get the same result.All of the points on the link above were followed. Im pretty much right at the bottom! still researching the net for the answer but im now in need of additional
Click to expand...
Click to collapse
Just go to my troubleshooting guide, you'll probably find an answer there.

Send it back for warranty repair.
Sent from my Motorola Startac running Atari 2600 software!

@nhrsak - you save me, thanks very much!!

Did you try getting s-off with Revolutionary?
I had problems when i was s-on, but when i s-offed, everything went fine.

Have you tried flashing recovery.img via AndroidFlasher(from XDA)?

[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] DHD almost dead - only vibra tones and led.

Hi!
Sorry for my English but i use my whole life only German
I have a big problem (specially for me):
When I speak using DHD a few dew sweat are on my LCD.
I saw that Volume + button doesn't work, and I want to reset my phone.
When I reset him, hi didnt work :/
If I want to start it normaly - only power button:
Hi give a three (3) vibra tones, and orange led blink all time.
If I want to start him with Volume - and start button:
Hi give five (5) vibra tones, and green led shine all time.
Any idees? I haved ROM: ARDH 5.1.17.
I don't know what too do.
Please help...
Ps. LCD is still black, i have no Idee - meybe is broken becouse i talk when i have sweat on my head?

Can you access the bootloader? Hold the volume-down button down when you power the phone on.
Sent from my HTC Desire HD using XDA Premium App

I have no idee. If I start phone with Volume - and power, He only do 5 vibra tones and green led is stil shining.
LCD is all the time black.

Could be the volume buttons acting up. You could try this:
- Turn the phone on to whatever state it boots up to
- Follow this guide until you have done point 7.
leith51 said:
7. Type: "adb reboot bootloader"
The adb reboot bootloader will take the device directly to fastboot And I can confirm that this method works also with non Sense roms.
Click to expand...
Click to collapse
You can skip this part:
leith51 said:
5.Download the radio you want to use from the links above .Then Drag and drop radio.img you have downloaded in to radio flash folder.
Click to expand...
Click to collapse
I'm not telling you to flash a radio, but this way you can get to the bootloader without using the phone.
Report back how it worked out.

Hmmm.
If I turn phone on and plug to the PC:
"adb reboot bootloader"
adb server is out of date. killing...
* daemon started successfully *
error: device not found
Click to expand...
Click to collapse
"adb devices"
List of devices attached
Click to expand...
Click to collapse
BUT!
If I take of battery, plug it again (battery) and I plug phone to the PC (PHONE IS OFF)
and if in command line:
adb devices
adb server is out of date. killing...
* daemon started successfully *
List of devices attached
HT0A8RX00397 recovery
Click to expand...
Click to collapse
adb reboot bootloader
nothing
When i write adb reboot bootloader, on command line is nothing and my phone give 3 vibra tones and orange led is blinking

What happens if you write:
adb reboot recovery
instead?
Sent from my HTC Desire HD using XDA App

Nothing, when I write adb reboot recovery:
Phone vibring 3 times and orange led blinking...

If I use android commander i can see all folders on the phone.
In "boot" folder i have any files.
DHD have a partitions? Maybe boot partition is dead?
Any idees how too repair phone using Android Commander?
Btw. If I doo this steps:
C:\Program Files\Android\android-sdk\tools>fastboot update PD98IMG.zip
Whoops: didn't find expected signature
read_central_directory_entry failed
Ř▼▓ôŇ˝»Č▲\►É┐Ý+╚⌂Áޡ┐Ý◄°´ŽÂĚ5♥~6BAN∟◄♫¸´↨!JJł(☺⌂■'
Click to expand...
Click to collapse

Try to download an RUU and that should probably fix it. All you do is plug your phone into the computer and the compuer does the rest. Search around for an RUU, there will be a guide in the thread.

I can't.
My PC see pheone when phone is plugged in OFF mode.
When I turn phone ON, PC can't find drivers for Qualcomm CDMA...
And when I turn phone ON MY PC doesn't see nothing
Automatically when I start RUU upgrade procedure, program tell me that He can't find device :/

is it possible that you used ROM Manager to partition your SD Card?
I'm asking because CWM/ROM Manager sometimes causes bricks on some devices.

I don't think so.
I only install new ARDH 5.1.17 ROM using EXT4 script.
That's all.
And +/- 2/3 weeks later my phone is dead...
Propably i send DHD tomorrow to the service. It is passible that service know about ARDH, root etc.?

S4 mini with broken screen, no more data after 'blind' reboots to recovery

Dear All!
(I already searched Google and xda - However, since my problem is rather specific, I may be using the wrong keywords to come up with a solution that is also applicable here; so also links are highly appreciated!)
I will give you the whole story in order not to skip anything important:
While hiking with my family I somehow managed to break my screen (LCD and Touch, as far as I could tell). However, the phone was still powered on, which i could tell from using the volume keys and hearing the normal sounds. Also the phone was ringing when called.
Unfortunately, USB Debugging wasn't activated, so I booted to recovery (some CWM, can't be more specific, sorry) via several tries. It was a bit tricky at first, but i managed to come up with a routine that would work (Holding VolUp+Home, then Power additionally; releasing the power button after the first vibration and then holding the other two for another 3-5 sec did the trick).
I then could gain usb debugging the way described in this thread: [Tool][Windows] Control a device with a broken screen. Now with touchscreen support!!
Using a Linux machine I then used adb commands (ls; cd; pull) to copy my mmssms.db; however I had to leave my workplace for a short while. Afterwards my device wasn't shown in adb devices, because it powered off for some reason.
Here comes the crucial part: At this point I mistakenly booted into Download Mode (and wasn't aware that I did it, cofused VolUp and VolDown - I couldn't see that, so I'm not 100% sure). I pulled out the battery at this point and rebooted into recovery.
Booting into recovery still works and "adb shell" -> "ls" shows the folders, however apart from the top level folders there are no more files/folders left (e.g. "ls mnt" gives "fuse secure shell"; "ls data" gives "media"; "ls data/media" doesn't return anything)
At this point I mainly want to get the contents of my internal sd (now no files are shown).
tl;dr: Broke screen; accidentially booted into Download Mode; Pulled out battery; Can't access my files/files gone in adb shell
Is there a way to recover the file structure? I still can get into recovery and use adb but the phone won't boot to CyanogenMod (I suppose it gives me a soft brick screen, but i can't confirm that as my screen is broken).
I really hope someone could point me in the right direction!
Lukas