Database Users

Is my Nexus 4 bricked or irreperably broken?

Hello people,
I have a German Nexus 4 and it gets stuck in bootloop whenever I turn the power on.
I've had issues with the phone since the last few months - i.e. random reboots, random program crashes.
But recently I tried to root it in order to install the Android L developer preview. It was during the booting process, when my Nexus crashed and it has been unable to boot ever since.
When I push all three buttons (power + 2 volume rocker buttons) simultaneously, I get the fastboot screen.
Choosing the following options has these effects:
Start --> phone tries to boot but gets stuck in bootloop forever and ever
Restart bootloader --> restarts the fastboot screen
Recovery mode --> phone shows the robot with an opened belly and a red warning sign (see photograph)*
Power Off --> turns the power off
Also, it is NOT detected or recognized by my Macbook when I connect the Nexus via USB cable. So it's impossible for me to access the phone via my Macbook.
*This is the screen shown when I try to go into Recovery mode in fastboot:
[can't upload outside link to image]
So this leaves me with no options as I never get further than the 4 turning circles forever and ever.
Is my Nexus 4 broken or is there still a chance to unbrick it? (I have a MacBook, so Windows programs won't work for me)

Of course it's not possible to recognize it when OS is not running.
Download WugFresh toolkit, ADB drivers (Universal) and the factory image. Enter fastboot, connect USB and flash the image

Your phone is not hardbricked, because it boots into the bootloader.
It might be recovered if you can access it with fastboot.
Try uninstalling all related drivers and install the Naked Universal Driver.

Thanks for your replies!
Unfortunately, the programs you mentionned don't work on my Mac (they seem to be Windows-only).
Also, how can I install stuff on my Nexus? Since it is not recognized by my MacBook, I can't load any files onto my Nexus.
And since any command on the fastboot screen only leads to the phone powered off, restart of the fastboot screen or the mentionned bootloop, I cannot perform any actions on the Nexus ...

Go to a friend with Windows.

Problem solved!
Somehow after the 1000th bootloop I finally reached the screen where I could wipe the phone.
And then it finally booted! Now all the data are lost and it's like a new phone, but at least it's working again!

How long was the boot loop? Was it the new boot animation from L?
Because when you flash L, the first boot up may take up to 15 minutes, leading you into thinking it's a boot loop.

[HELP] DemiGod Crash Handler : Kernal Crash (Can access recovery)

Phone Model: AT&T LG G2 (D800)
Recovery: Custom TWRP Recovery
ROM: CM12 Official ROM
My phone was working fine from last 3-4 months, until today it restarted and got stuck on 'LG' logo, I left it for some time and it shows the demigod green screen of death with option to access download mode and restart.
What I already did!
1) Full hard reset, I can access the TWRP.
2) Flashed the ROM again.
Current Situation!
Stuck on LG logo from last 10mins.
Thanks in advance.
Edit #1: Reflashed the same ROM (CM12) and it booted into the language selection page, freezes and restarted. Stuck on black screen, I turned it off by pressing the power button for 10-15 secs. I kept it in a freezer for 10-15secs and turned it on, same happened.
Edit #2 I flashed a stock based ROM through TWRP, it was going fine but it froze in between, I waited for some time and it went black. I waited for 1 hr and it was still black so I hold the power button and restarted the phone.
Now its showing "Secure Boot Error" which remains for some secs and a black screen comes, I can't open TWRP, Download mode is accessible but after 2 secs into download mode, secure boot error comes. Whenever I try to connect it to Windows PC(I installed all the required drivers and all) it starting popping up drives(with option to format) which never stops until I remove the USB cable.

Hi!
In this thread someone posted a solution.
jazibzps said:
Steps to perform.
1. While in critical error screen you have an option to press volume up button to boot into download mode( although it will not boot to download mode) but still press volume up button so your Pc can detect your phone.
2. Now flash a kdz file of your lg g2 with flash tool. ( you can google for it to download flash file for your lg g2 and how to flash it with lg flass tool.)
3. When you will try to flash it will fail..
4. Now power off your phone by pressing power button.
5. Now boot to download mode and flash the correct kdz with lg flash tool and u r good to go..
To acess download mode power off your phone immediately press volume up button and while keep pressing it and plug in usb cable and you will be in download mode
I performed all this on lg g2 d801 but i hope u can try it on other varients as well. As i was scared of short circut method and srk tool didn't help..
Click to expand...
Click to collapse
For informations about LGs flashtool etc. please check out the G2-Index-Thread.

Jan Philipp said:
Hi!
In this thread someone posted a solution.
For informations about LGs flashtool etc. please check out the G2-Index-Thread.
Click to expand...
Click to collapse
Thanks for replying.
My case is a bit different now, I reflashed the same ROM(CM12) and it successfully booted, worked for 10 secs and it was frozen, restarted automatically, stuck on LG Logo.
I notice that there's some heat issue, I kept it in freezer for 10 secs, rebooted it, it booted till language selection page and freeze after 10-15secs.
Also the link is for DemiGod Critical Crash, mine is DemiGod Kernel Crash.

Updated!!
First post updated, please check the current situation before posting anything.

I don't have a computer or laptop to connect it to so how can I fix it?

[SM-G900F] Device reboots 3 seconds after display goes off

Device was working fine until OTA update to 6.0.1 (MMB29M.G900FXXU1CQDA). It wouldn't boot past the Samsung logo.
I downloaded that same firmware (and the one before) and flashed it via Odin 3.12.7, however situation remained the same.
Flashed TWRP 2.8.7.0 and then PhoenixROM 15.0 and device booted fine. However it would always reboot after display stays off for 3 seconds.
Flashed TWRP 3.1.0-1 and then LineageOS 14.1-20170802 and device booted fine again. The reboot problem remained the same.
The reboot problem is NOT present while device is connected to a PC, however it is present while connected to an AC wall socket.
Each time the display goes off the device stays off for 15 seconds before booting again.
Anyone got similar experience, any advice?

eqagunn said:
Device was working fine until OTA update to 6.0.1 (MMB29M.G900FXXU1CQDA). It wouldn't boot past the Samsung logo.
I downloaded that same firmware (and the one before) and flashed it via Odin 3.12.7, however situation remained the same.
Flashed TWRP 2.8.7.0 and then PhoenixROM 15.0 and device booted fine. However it would always reboot after display stays off for 3 seconds.
Flashed TWRP 3.1.0-1 and then LineageOS 14.1-20170802 and device booted fine again. The reboot problem remained the same.
The reboot problem is NOT present while device is connected to a PC, however it is present while connected to an AC wall socket.
Each time the display goes off the device stays off for 15 seconds before booting again.
Anyone got similar experience, any advice?
Click to expand...
Click to collapse
Flash stock lollipop and report back.

godkingofcanada said:
Flash stock lollipop and report back.
Click to expand...
Click to collapse
Did. Same case as with Marshmallow.
However there has been further issues, seems the phone can't be saved.
After flashing Lolipop the phone wouldn't boot via power button, but instead I need to boot it to Download mode and hit cancel.
This however makes it go to Recovery mode. Trying to boot the system from Recovery makes it power off.
Tried flashing TWRP back and when I enter it, the device keeps choosing random options rapidly, as if it's constantly detecting touch across the screen.
Therefore I'm no longer able to flash LineageOS back.
Gave up on the device in the end, seems to be defective.

eqagunn said:
Did. Same case as with Marshmallow.
However there has been further issues, seems the phone can't be saved.
After flashing Lolipop the phone wouldn't boot via power button, but instead I need to boot it to Download mode and hit cancel.
This however makes it go to Recovery mode. Trying to boot the system from Recovery makes it power off.
Tried flashing TWRP back and when I enter it, the device keeps choosing random options rapidly, as if it's constantly detecting touch across the screen.
Therefore I'm no longer able to flash LineageOS back.
Gave up on the device in the end, seems to be defective.
Click to expand...
Click to collapse
It sounds like the touch screen is going wonky. Or the mobo has an issue. You could get it diagnosed at a shop reasonably cheap

Stuck in logo after flashing stock. Can't boot into recovery. PC doesn't recognize.

So, I rooted and tried flashing the stock ROM (from Sammobile, same country, same exact model [SM-G950F], I already had the stock ROM and had never flashed anything else to the phone other than root, June security update, my phone had July's) to see if I could fix a problem that couldn't be fixed with any other method I had tried.
Everything in Odin seemed to go well, I got the PASS green box at the end. But then the phone couldn't go pass the Samsung logo when booting up. I left it quite a few minutes, before trying to boot into recovery mode and wiping data. Only to realize that I couldn't boot into recovery mode. In fact, I can't even turn the phone off. No combination of hardware keys works other than power button + bixby + vol down, to get into download mode. But that's of no use, because when I plug my phone into my PC (with the same cable and port I used before to root and flash the firmware into it) it is not recognized by Odin or the PC.
It just has the Samsung logo flashing slowly over and over because I can't turn the device off. By the time the battery dies out I'll most likely have the logo burnt into the display.
I also haven't been able to find any help online. Everyone's suggestion is “boot into recovery and wipe data”, but I can't do that.
Is my phone gone for good?

Le Pro 3 - Stuck in a bootloop recovery mode and fastboot not working.

Hi guys,
After googling it I tried booting it in recovery and fastboot mode but none of them work, when I try to boot in those 2 modes I get a screen with "recovery mode" written for 5 secs then it goes back to the normal boot screen and then turns off and starts to bootloop again the only way I could stop it from boot looping was by pressing the power button + the + and - buttons, so yeah if you guys have any idea how I could fix this or how I could recuperate my data please help, also it started bootlooping during the night while it was charging it was very hot when I took it, last thing when I try to go and charge it there is not indicator that it's charging.
Thanks in advance for your help !
much love
Mathias.

Kind of the same issue here.
Yesterday, I was using my phone while it was charging (low battery), and suddenly : freeze then power off and stuck into a bootloop.
It did it all the night until no battery, now when I plug it the charging Led is not lighting, and stuck in a bootloop.
Tried to flash TWRP vi fastboot mode : success but impossible to boot into recovery mode, as you described.
Affraid of the battery has died...

Flashed wrong orange state zip
Same to mine, my device was x651 and i flashed an orange state zip file intended for le 2 x620 without wipe and after flashing it from recovery , I rebooted the device, now its powering on and off on a dead screen and only long vibrates, how can we fix this? Please help

Not sure if this will help, but I ended up with a perpetual boot loop on the phone and wrote it off as broken and got a new one....a year later, I plugged it in to see if it would even power on so I could trade it in and VOILA, it boots up! What the hell? So my suggestion is maybe to let the battery run ALL the way down and then a long charge first.