Develop Bugs

[Q] Bricked phone?

I was playing with my splash screen and boot animation, and I changed the PB31IMG file on my sd card to a custom splash image. I went to hboot (.92 i think) and it gave me the error "no image found" or something like that. I turned off the phone, and tried to boot up into hboot again by holding volume down+power. As soon as I did, my phone vibrated maybe four times and stayed at a black screen. I can't turn the phone on now, or boot into recovery. Has this happened to anyone else? More importantly, does anyone know how to fix it?
Just to add more information (Im really not sure what's relevant), I was running virtuous 2.6 with hydra #1, 2.15 radio. Also, the image error happened before when I was trying out a different splash screen. That time I deleted the file and re-transfered it my sd card. Hboot was able to recognize it as a splash screen when I rebooted it that time. I'm not sure, but my phone might have booted into clockwork recovery after hboot checked the img file.
One other thing that might be a problem was that I might've been running low on battery. I didn't check, but it was the end of the day and I'm usually almost dead by the time I charge it again.

Never mind.
(Unrevoked forever wiki)
When I try to get into Fastboot by pressing VOLUME UP and booting the phone, my phone instead buzzes three times and acts dead. What happened?
The S-OFF update also enables Qualcomm Diagnostics mode on your phone, which is entered by doing what you just did. You can exit this mode (and boot normally) by removing the battery and USB cable.

[Q] HTC Wildfire problem after root/custom rom

Oke, so i have a problem with my HTC Wildfire. I decided to root it today and put cyanogenmod 7 on it. I found a guide on how to do this, followed it and it all worked fine.
When CM7 was running, I didn't really like the experience. It seemed slow and too buggy for my liking. Therefore i wanted to recover the previous state my phone was in. To do this, i tried to recover the back-up i had made with rom-manager.
However, the recovery didn't work. It said it did, but then the phone just freezed on the standard boot screen (showing the green HTC letters) Since then I haven't been able to get past this.
I tried recovering again from the bootloader; i've tried the factory reset; i've tried an RUU thing i found from froyo, and the result has always been the same. Nothing. The recovery and factory reset were reported to have been successful, but after it i still couldn't get past the boot screen. The RUU thing didn't work, it shows an 'unknown error' ([155])
So, does anyone know how i can fix this? At this point i don't really care what is my UI, whether it's the stock android; sense; or some ROM. As long as i can use my phone again.
Any help would be very much appreciated!

Flash a custom ROM (Any, Cyanogenmod 7 , or Sense) again via Clockworkmod. Follow this post (Ignore the parts where it says to backup apps and stuff)
http://forum.xda-developers.com/showpost.php?p=8926457&postcount=4

Problem is that i would need the CM7 files on my sd card. And right now i wouldn't know how to access it. I can't do it with my phone, since my laptop doesn't recognize the sd card when the phone hasn't powered up. And i don't have card reader for a micro sd card.
The last time i installed the rom, i did it with rom-manager, and didn't download any files myself (only via the app)

Boot into Clockworkmod Recovery (The procedure is given in the post I linked above. Press Vol Down + Power, Navigate to Recovery, Press Power Button..... and so on). Once it's done, connect your Wildfire to your laptop, then browse to "Mounts and Storage" in Clockworkmod, and select "Mount USB Storage". Now, you will be able to access your SDCard normally as it was before.

It's working! Many thanks!

[Q] Is this Hardware death?

EDIT: I got past the original issue. Please see post #4 instead,
I'm trying to determine if my hardware has gone bunk or whether it's repairable system errors.
_____________________________________________________
Original post:
Hi guys,
I see several recent posts about similar topics but I can't begin to troubleshoot because I can't get past the bootloader.
Here are my specs from the bootloader screen:
INCREDIBLEC XC SHIP S-OFF
HBOOT-0.92.0000
MICROP-0417
TOUCH PANEL-ATMELC03_16ac
RADIO-2.15.10.07.07
Jul 23, 2010, 18:06:51
I use ClockworkMod recovery, but I can't remember the last ROM I had installed, it might have been MIUI 2.3.2.
___________
When I try to start the phone normally it just hangs at the first white "htc Incredible" screen. Tried without an SD card inserted: same behavior.
If I boot into hboot instead and try to launch Recovery, it goes to the white "htc Incredible" screen and hangs indefinitely, whether SD card is in or out.
If instead, from hboot, I try to Factory Reset, it goes to the white "htc Incredible" screen and hangs indefinitely, whether SD card is in or out.
At this point I can't get past the white "htc Incredible" screen no matter what I do.
____________
I issued the "oem enableqxdm 0" command through fastboot to ensure the SD card could be mounted, then took a fresh SD card and loaded the Stock_inc_4.08.605.15 image from dinc.does-it.net and flashed it in hboot. It loaded the image, went to "Parsing…" for a few seconds, then reset to the main hboot screen (not sure if that means it was successful). Still the same outcome: stuck on the first white "htc Incredible" screen, whether simply powering on, launching recovery, or trying to factory reset.
The phone had some previous issues I can describe if anyone thinks it would help (bootlooping unless I held the phone in the freezer long enough to launch AnTuTu and underclock the CPU way down, suggesting a heat issue).
Really I would just like to get some data off of a few saved Nandroids, if I can get the phone working again as a toy for tinkering with that would just be a bonus.
Can anyone tell what my problem is?

Sounds like your recovery is borked somehow. Try fastboot flashing your recovery again (I recommend latest TWRP), and start over.

PonsAsinorem said:
Sounds like your recovery is borked somehow. Try fastboot flashing your recovery again (I recommend latest TWRP), and start over.
Click to expand...
Click to collapse
Thanks for the reply.
I tried flashing the stock recovery image (4.08.605.2) through fastboot but I kept getting the "FAILED (remote: not allowed)". I was able to load it as a .zip through the bootloader though. After rebooting and entering recovery through hboot the recovery partition would flash open, then immediately restart to the white "htc Incredible" screen again where it would hang as long as I let it.
I did notice it was getting really hot just sitting at that white screen so I popped it in the freezer to cool off for a minute. When I opened the freezer a minute later BOOM it's sitting at the home screen, fully booted. Keeping the phone in the freezer, I've since been able to reflash CWM 5.0.2.0 recovery and load my saved Nandroids. As soon as the phone is out of the freezer for 1-2 minutes it does and goes back to the white "htc Incredible" screen and either hangs or bootloops.
So right now I'm running back and forth between the freezer and the charger trying to load each of about a dozen Nandroids, backup my photos, call and sms logs, and move on to the next one. Seems like this method will at least allow me to get my saved data out of the Nandroid backups even if it takes all night.
Two questions:
1) It seems like the phone has a hardware overheating issue. After rescuing my data, I'll probably try to load an undervolted/underclocked kernel to see if it will stay alive under a reduced load...any input on the best choice for such a ROM & kernel?
2) To access my nandroid backups, do I need to load them on to this specific phone? Is there a runtime environment or can BlueStacks or something allow me to virtually load a nandroid backup from my dinc for purposes of getting the data off?
Thanks again.

Here's the situation now:
EDIT: phone went in the trash, life is less stressful.

[Q] Stock HTC One M8 Won't Boot

Would love some help, please. I have a completely stock HTC One M8 for Sprint. Last night I plugged in the phone to the AC charger (still had ~70% charge) and went to sleep. This morning the charge indicator was green as usual, but pressing the power button did nothing. Unplugged the phone from the charger and the LED remained green.
Tried press-hold power button for 10 seconds: no effect.
Tried press-hold power button and volume down. Select HBOOT, then RECOVERY. The phone vibrates and shows me the skateboarding androids, then reverts to the FASTBOOT menu.
Tried press-hold power button and volume down. Select HBOOT, then FACTORY RESET. The phone vibrates and shows me the skateboarding androids, then reverts to the FASTBOOT menu.
Tried requesting an Unlock_code.bin from HTCDev, then use fastboot to flash that. I see the transfer bar on my phone for an instant, but otherwise the display does not change. Still indicates *** LOCKED *** even though the fastboot command returned "OKAY".
Tried using abd.exe to list devices - none listed. Though fastboot.exe does return my serial number.
:fingers-crossed: Tried pres-hold power+volUP+volDWN for 2 minutes. Phone booted as normal, I swiped my unlock on the touchscreen, HTC Sync saw my phone, then the screen went black and I couldn't get it to boot. Sorry I did not notice what charge level the battery was in the GUI for the ~10 seconds the phone was on.
S-On
HBOOT-3.16.0.0000
RADIO-INVALID_VER_INFO
OpenDWP-INVALID_VER_INFO
OS-1.54.651.8

update - still won't boot, but ...
Update: still won't boot, but now I can get recover mode to run. Tried wiping cache partition and rebooting. Now it boots to the HTC (android) logo, then the Sprint animation plays, then the HTC One animation plays, though the audio portion only plays for the 1st second and cuts off suddenly. Then it just hangs there forever. I left it for an hour at that point just to make sure it wasn't booting really slowly.
Any way to boot from something on an SD card so that I can at least get my userdata partition backed up?

astaples said:
Update: still won't boot, but now I can get recover mode to run. Tried wiping cache partition and rebooting. Now it boots to the HTC (android) logo, then the Sprint animation plays, then the HTC One animation plays, though the audio portion only plays for the 1st second and cuts off suddenly. Then it just hangs there forever. I left it for an hour at that point just to make sure it wasn't booting really slowly.
Any way to boot from something on an SD card so that I can at least get my userdata partition backed up?
Click to expand...
Click to collapse
Sorry to say this, but all your data is gone since you factory reset from bootloader, that always wipe your phone. What recovery you had when you pressed it, if it was custom like trwp your internal sd is more likely corrupted. The easier option to get the phone back to working state is to run ruu if there is any for Sprint.

tominozh said:
...all your data is gone since you factory reset from bootloader, that always wipe your phone. What recovery you had when you pressed it, if it was custom like trwp your internal sd is more likely corrupted.
Click to expand...
Click to collapse
Thanks for the reply. Actually I listed my attempted fixes in order... i.e. I was able to get the phone to boot once for a few seconds - long enough to see my personal home screen and photos - after I had clicked on that factory reset option.
I have a theory. The RAM is bad. That would explain why sometimes it will partly boot and then get stuck, other times it will get stuck in a bootloop to the fastboot menu, and other times (only one time so far) it will completely boot. Also, if I go to the RAMDUMP option, at the bottom of that screen it shows mostly non-ASCII characters and vibrates every ~5 seconds. If I go to IMAGE CRC, it sometimes instantly shows 0x0 next to each device, other times takes a while to calculate believable values for each, and other times won't display anything and freezes.
Think that's plausible? Suppose there is any way to boot from sdcard and retrieve my userdata partition? I did not have a sdcard in when this originally happened, so all my family photos are in userdata and I haven't backed up since my 4-year old's birthday party last weekend.

Any way to get my userdata off this phone, or do an in place upgrade without hosing m
Anyone? Help?

One M9 Major Issue with Internal Storage

A little background on the issue:
I had my phone on the charger for awhile, saw it at 100% so I unplugged it, put it into my pocket, and thought nothing of it. Next time I pull it out of my pocket(about 4-5 minutes later), I find that my phone has restarted itself and won't boot whatsoever. I then tried to boot into recovery to see what was what, and found I couldn't do that either(using vol up+power). I found out that the only way to get into my recovery is to plug into the pc, then use vol up+power(?????). After getting into the recovery, I found that every time I boot into it I'm greeted by a message saying "Keep system read only?", with option below to swipe to allow modifications. It doesn't seem to matter which I choose as neither do anything. I look at my drives and see that my internal storage is listed as 0MB. I then tried restoring a Nandroid backup I made a month previous, but I was greeted with a log saying the phone failed to mount literally everything, followed by "invalid arguement" after every line(would post logs but my phone is currently stuck in a loop in an ruu). This happens with anything I try to do in TWRP(running 3.0.0.0), whether I try to change the filesytems to FAT or try flashing a new ROM(seemed to open fine with Aroma installer, but gets stuck writing to /data). After exhausting everything I knew to try and everything on the Interwebs, I resorted to trying an RUU. It opened fine, recognized my device fine, but is now stuck doing the same process over and over(currently at 46 min). I'm running ViperOne 3.5 with an unlocked bootloader and S-on. I'm currently at a loss of what to do, and would appreciate any and all help. :3

Corrupt nand I think.. It cant find any partitions.
Beamed in by telepathy.

Any ideas on a solution?