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] phone does not wake from lockscreen or boot from recovery

I have a rooted (S-OFF) Droid Incredible running CM7. Just yesterday it started to get very laggy. I decided to reboot, which it did. However, upon reboot it failed to recognize the SD card. The phone then timed-out to the lockscreen, and I could not get it to wake up. Ocassionally, when pressing the power button, the 4 capacative touch buttons will light up & give feedback, but the screen remains off.
I started it into HBOOT & attempted to boot from Recovery, but it simply looped back to the main menu. It also briefly flashed a screen with green text stating "No Image!" in a number of directories. (This screen lasted for less than a second, so it is hard to recall exactly what it said).
I rebooted normally and was able to operate a few apps, but the SD card remained unrecognized. Once it timed-out to the lockscreen, I was back to the unresponsiveness. All I can do is remove the battery & reboot, but I get the same results every time.
Any help or guidance you may be able to provide is GREATLY appreciated!!

First i would reformat the sdcard fat32 with your pc. Then i would reflash cwm recovery thru hboot http://dinc.does-it.net/Recoveries/CWM_5.0.2.0/PB31IMG.zip, and then wipe everything in the mounts and storrage menu. Then restore a known good backup or flash a fresh rom. If that dosent fix it i would do an ruu.

Stuck at Google logo screen

So, it's been a fun couple of days.
I was 'tabling' away, as usual, and my tablet suddenly reboots (if it matters, I was just opening FPSE, as I'd done dozens of times before; Skype was on background; every other process was finished). 'Ok', I thought, 'that's weird'. When the tablet's done rebooting, the lockscreen shows up, and when I try to unlock it, the scren just freezes. Couldn't turn off the screen, nothing. So, I force a shutdown by pressing the power button.
When I try to turn it on again, it just stays stuck at the Google logo screen. I tried going in through recovery, but the result is the same. Select recovery, Google logo shows up, little android with exclamation point doesn't.
I tried formating through fastboot -w, but the process just keeps endlessly deleting, while doing nothing at all. I have to quit command line, shut down tablet or unplug the USB cable with a command line message showing up (I once left it while I went for a coffee; two hours of deleting nothing at all). Same thing with trying to unlock bootloader to maybe going to recovery after flahsing a custom recovery.
I don't mind losing everything I had. All pictures are recuperable and the rest is either in the cloud or in my phone/PC. The most annoying thing would be to set up the whole thing again, wich is no trouble at all (that and going through PvZ2 and TD Bloons 5 from the start :crying: ).
I was using Android 4.4 (KRT16S), everything stock.
Is it bricked, soft-bricked, did the aliens get it? I am e-mailing with someone from the store I bought it from, hoping for a solution or (worst case scenario) RMA, but I would rather solve this without having to.

Try flashing system.img, recovery.img, and boot.img, by hand.
Your emmc likely got corrupted

How do I do that with a locked bootloader and no access to recovery? Is it possible?

[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.

Problem with booting G4

Hello, I would like to first tell you the story my LG G4 has gone through and then I tell you the error.
So, at first my phone was working absolutely properly. I accidentally deleted some pictures and to do a recovery, I had to root it. And rooting would be useful for later so why not do it?
So I first unlocked the bootloader through the code from the LG site. After unlocking, the phone reset (because it would be just too good to make some memory changes and nothing more.) But allright. Then I was ready to root. I just booted the phone, everything was fine. I unlocked the developer mode and opened ADB. I rebooted to recovery through
Code:
adb reboot recovery
I was expecting to see some menu with buttons (but that would be just too good). However, I saw just android with a red triangle in the middle. Nothing more. No response to buttons, nothing.
So I thought. Allright, let's boot into recovery using hardware buttons (vol down + power) at startup. Unfortunatelly, it seemed like there is no such mode System just normally booted (and that was just after bootloader unlocking. Recovery mode goodbye.).
I tried to send commands to the phone using diagnostic port. Unfortunately, it responded by FAIL to every command.
I reboot to bootloader and booted an image: "boot-em.img" (from here: google: how-to-root-lg-g4-on-android-6-0-marshmallow-20a20b-firmware. I'm a newbie here. thx for understanding.)
After that the console uploaded the image and booted successfully. Then, however, system started to boot up and was endlessly booting (LG boot animation) till the battery was critical.
I was able to access the EMI number through volume-down button and volume-up button pressed simultaneously.
I was also able to access some factory-reset dialog by holding volume-down and pressing power-button several times. I choosed to reset everything and then accepted it with one more 'are you sure dialog'. System rebooted and was stucked in the LG boot animation.
Then I got to download mode, since recovery mode was lost in hell. Through LG-UP I flashed the original KDZ firmware and everything got back to normal, but recovery mode was still inaccessible through the hardware buttons. I got through the process of setting everything up, getting developer, rebooting to bootloader and I booted TWRP.
TWRP loaded and it responded to double-tap on screen to wake it up. I just checked the menus and let the phone sleep.
After several hours I went back to the phone and double-tapped on display. Nothing. Phone was not responding. I pressed the power button and the phone restarted (I think. It either restarted into the system or was not responding to power button.)
So I got to the system and again rebooted to the TWRP (through fast-boot). I tried to back-up one partition to the disk. During the process phone had turned the display off. So I double tapped. Nothing. I removed the SD card and the phone woke, saying that back-up process was not able to complete. Suddenly it stopped responding to double-tap. It woke up through an interrupt. I re-inserted the card, successfully backed-up the partition to the SD-card and I left the phone laying on the bed plugged in the charger. It stayed that way for 4 hours or so, doing nothing. All of a sudden, a yellow screen was there, (and that's a screen of absolute death that was never supposed to come. Little I knew.) saying that an unexpected critical error happened and to do a memory dump, insert a cable, set up some communication (I don't remember what it was, didn't take a picture of it.) and it could send the memory dump to PC or somewhere. I thought to myself. So, the application is not so stable after all. It said that to reboot just press the power button or something.
And now the problem comes:
The first start: Bootloader booted, LG animation went on and finished. The starting up apps dialog came rolling. Then, system restarted.
The restart: Bootloader booted, LG animation went on and freezed. Then, the phone restarted.
Second restart: The same thing as the first one.
Fourth restart up till now: Bootloader tries to boot and restarts before the LG animation.
I got to download mode and it restarted even there. After re-inserting the batterry I can sometimes get to the Firmware Update window and communicate. There I flashed the official firmware again.
No success, as if I didn't even do it. It restarts before the animation.
Can I do anything with the phone? Hopefully I can. No hardware problem occured (except for a situation where the error could fry the wires inside the mighty System On Chip.)
For the software state I cannot even tell but I might say it's cooked just wrong. That's why I came here.
I know I did some pretty stupid steps. But the error was not done by me. It worked fine and after the yellow screen which came by itself, it just (some bad words).
Thanks for replies.
Phone: LG-G4 H815, European market

Solution
So, I was looking around and believe it or not, this problem disconnected the pins on the motherboard's snapdragon 808.
I think this happened: The device, although it was heated many times during its life, it withstood that so far.
However, a longer run of the TWRP had finished it off. Memory got disconnected while running and it threw a yellow-screen.
Pins got disconnected and from then on it was just a standard common LG bootloop issue.
The continuous process of dying (First it partially loaded, then only animation, then nothing) is explained by this fact that the pins were so-so there and a couple of reboots just got it totaled.
Temporary fix:
Pre-heated the memory chip to 250°C using Hot-Air gun. After 18 seconds at this temperature I pressed the memory on top of the snapdragon down to the board while cooling.
Then I added a little metal square on the metal part that is covering the system on chip. This part is over the SOC where before there was just some tape.
This can work for several days in sleep mode or a couple of 'heat-demanding' operations on the phone.
Permanent solution should be to reball the memory chip on the snapdragon. That's my next step.