Database Users

[Q] Did I brick my Nexus 4?

Hi,
Last night i was playing with my N4 (with some root applications) and an app asked for a reboot. I just pressed yes so that the phone will reboot (I have done this earlier without any issues). Suddenly the device doesn't boot up. My N4 is stuck at a black screen. While trying to boot up, the Google logo appears and then a black screen. It doesn't advance to the 'X' logo. I'm running on stock, rooted phone (used N4 toolkit by Wugfresh to root).
I'm able to boot into recovery although. I tried all the possible means, wiped cache, dalvik cache, did a factory reset, backed up the system and tried to restore the same. Nothing happened.
Then i tried the "Back to Stock" option in the N4 toolkit and chose the option "Soft-brick/Bootloop" to recover my N4. These are what happened:
Downloaded the 4.2.2 image from Google servers and tried to flash in the device with prior instruction from the toolkit. Everything went fine until the flashing process. In the last step the CMD window opens up saying it is unrooting and flashing stock and immediately it'll bring up a complete message saying the flashing is complete and to wait until the device boots up. But nothing happens again.
I tried the automatic flashing and on the downloading window it saying download failed and hash checks failed meaning its not downloading.
I searched all the possible threads in a day to find a similar problem but in vain. I'm not a noob but i'm too lazy . But i would do anything to bring my N4 back to life. Anyone please show me a direction.
In short:
Status: Soft-Bricked (guess so), black screen after Google logo
Version: Stock 4.2.2 (rooted+busybox+supersu+twrp)
Able to boot to recovering: Yes, bootable to recovery and bootloader.
Tried Nexus toolkit recovery: Yes but in vain.
Gave up: No and never, I'm searching and searching for answers and I'm worried if I'll end up in a hard brick. :crying:
Guys, please help.
Thank You!
Aghil

I'm just taking a wild guess here - I'm not responsible if anything bad happens, and you might want to wait to someone else seconds my suggestion in any case (although I can't imagine things getting worse as long as you flash N4 stuff). But have you tried flashing a new boot.img/reset kernel from recovery or via fastboot/toolkit?

ameinild said:
I'm just taking a wild guess here - I'm not responsible if anything bad happens, and you might want to wait to someone else seconds my suggestion in any case (although I can't imagine things getting worse as long as you flash N4 stuff). But have you tried flashing a new boot.img/reset kernel from recovery or via fastboot/toolkit?
Click to expand...
Click to collapse
Err...nope I haven't tried any and will wait until someone seconds you. Meanwhile I have wiped off the ROM through the option in recovery. Still will I be able to do what you said? Also if could direct me to a "how-to" thread would be great. Just that I don't wanna mess up again.

Also, is there a way to transfer a ROM to N4 through fastboot? So that I can install the ROM through TWRP.

aghilvr said:
Err...nope I haven't tried any and will wait until someone seconds you. Meanwhile I have wiped off the ROM through the option in recovery. Still will I be able to do what you said? Also if could direct me to a "how-to" thread would be great. Just that I don't wanna mess up again.
Click to expand...
Click to collapse
No, my suggestion would require that the ROM is still on the phone, so you should restore your ROM prior to my suggestion. And I'm by no means an expert (therefore the disclaimer), but I *think* that since it's a bootup problem, it could be solved by flashing a new boot.img (which is essentially flashing a new kernel to the system).
But yeah, let's see if others think this might help, haven't researched it, is at work right now. Just throwing in a suggestion, that's all...
Also, is there a way to transfer a ROM to N4 through fastboot? So that I can install the ROM through TWRP.
Click to expand...
Click to collapse
I *think* (again, I'm totally not sure about this, as I haven't tried it) that you can sideload a ROM via zip file from recovery, but since I haven't tried it I'm not sure - can anybody confirm???
EDIT: Chromium's suggestion is better, by pushing the ROM.zip to the device and flashing from recovery (check md5 first, just in case).

aghilvr said:
Also, is there a way to transfer a ROM to N4 through fastboot? So that I can install the ROM through TWRP.
Click to expand...
Click to collapse
Yes there is. Your nexus is not bricked and this is why you shouldnt use toolkits to do things. This is honestly an extremely easy and simple fix. Use adb to push a rom onto the n4.
Code:
adb push \path\to\rom.zip /sdcard
Boot into recovery, do a full wipe, and flash the rom.

You said you downloaded the Google images.
Just boot your phone into the bootloader and run the flashall.bat that is in the Google image folder.
Note this will probably fully wipe you're phone in the process
Sent from my Nexus 4 using xda app-developers app

try this it may help u this toolkit is damn easy to use :
http://forum.xda-developers.com/showthread.php?t=1995688

Okay, thanks guys. I'm on it. Will let you know when I'm done.

That same thing happened to me once. I had to extract the google file and look for the 4 img files(bootloader, system, userdata, recovery) and flash them with toolkit manually and it fixed it, but it erased everything on my sd

I tried to load the file "occam-jdq39-factory-345dc199.tar" into my phone using the ADB sideload feature in the toolkit. I don't have the SDK installed hence I depended the tool again. But now the tool only loads .zip file and not .tar as the one that i downloaded. Am I doing it right?

aghilvr said:
I tried to load the file "occam-jdq39-factory-345dc199.tar" into my phone using the ADB sideload feature in the toolkit. I don't have the SDK installed hence I depended the tool again. But now the tool only loads .zip file and not .tar as the one that i downloaded. Am I doing it right?
Click to expand...
Click to collapse
K if you have a custom recovery installed, there isnt much you need to do to fix the issue.
First setup adb/fastboot by reading this
Then boot the phone into recovery, and plug it into the computer. Open a new command prompt window and use adb like this:
Code:
adb push \path\to\rom.zip /sdcard
Then you can unplug the phone. From recovery go to the install menu, find the rom that you just pushed, and flash it.

chromium96 said:
K if you have a custom recovery installed, there isnt much you need to do to fix the issue.
First setup adb/fastboot by reading this
Then boot the phone into recovery, and plug it into the computer. Open a new command prompt window and use adb like this:
Code:
adb push \path\to\rom.zip /sdcard
Then you can unplug the phone. From recovery go to the install menu, find the rom that you just pushed, and flash it.
Click to expand...
Click to collapse
Okay, installing the SDK. And the command saying "rom.zip", the file that I have is like "rom.tar". Does it matter? I downloaded the rom from here https://developers.google.com/android/nexus/images

aghilvr said:
Okay, installing the SDK. And the command saying "rom.zip", the file that I have is like "rom.tar". Does it matter? I downloaded the rom from here https://developers.google.com/android/nexus/images
Click to expand...
Click to collapse
No the tar wont work through recovery. You should download a rom from here or here.
If you want to flash the stock rom through recovery you can download it here.

chromium96 said:
No the tar wont work through recovery. You should download a rom from here or here.
If you want to flash the stock rom through recovery you can download it here.
Click to expand...
Click to collapse
Oh that's why it didn't work all the time
Thanks chromium :fingers-crossed:

Hey thanks guys, my device is back to normal. Chromium a special thanks for you for helping me out. See you guys with my next problem/queris!

[Q] Please help... D800 flashed to D802

So I am not sure what I did, but I was just trying to flash the Grievous ROM earlier and it would not work, just kept going to a black screen on start up even though I didn't get any errors when installing. I retardedly forgot to make a backup so I have nothing to go back to. I tried to go into download mode to restore through the LG tool, and amazingly somehow it now says my phone is a D802.
I can still get into recovery and download mode and haven't seen fastboot yet, but I can't get my computer to recognize my phone in adb or sideload while in the recovery menu... Not sure what to do. It sucks that this phone doesn't have removable SD.
Anyone got any ideas? I've looked through other threads of people who have had this problem and luckily(I think) I still haven't got to fastboot. I was thinking if I can just get the stock files on there I can flash it in TWRP without having to even use the LG Flashtool, but I am at a loss for how to get the stock ROM on my phone.
WHAT DO I DO?

Install the kernel for the d800. To hey your phone to be recognized in recovery you will need the proper drivers, try pdanet. Drivers
Sent from my LG-D800 using Tapatalk

Okay I successfully got adb to work in the TWRP menu with the pdanet drivers, and I pushed the stock rom .zip to my phone but it won't let me flash it. Where do I get just the stock kernel?

Nevermind, got the ATT stock rooted rom from scotts site to push and install, which still gave me a black screen but afterwards but made download mode work, so got it back to stock! YAY!

[Q] Flashing back to 4.2.2

Hey guys, Hopefully somebody can help me here.
Basically i flashed & rooted my D802 to 4.4.2 using this method > http://forum.xda-developers.com/showthread.php?t=2680789
All was running fine however somewhere along the line something has messed up! I tried to boot into recovery and now im hit with "Secure Booting Error! Cause : boot certification verify" instead of TWRP!
Ive tried to use this method > http://forum.xda-developers.com/showthread.php?t=2625044 to flash back to stock and unroot BUT when i get to step 5. of method 1. instead of asking to to Select Country & Language it starts the LGMobile Support Tool and the tool tells me i have the latest available software for my device.
The phone is running fine and i can get into download mode.
Thanks in advance for any help.

Anybody got any ideas?

OK ive managed to boot into recovery(TWRP v2.6.3.3)I was gonna try to push a new ROM to my device via ADB sideload, When i select the ADB sideload feature TWRP just gets stuck on "Starting ADB sideload feature..." and sideload wont start!
Anybody got any ideas?
Thanks.

ATOJAR said:
Hey guys, Hopefully somebody can help me here.
Basically i flashed & rooted my D802 to 4.4.2 using this method > http://forum.xda-developers.com/showthread.php?t=2680789
All was running fine however somewhere along the line something has messed up! I tried to boot into recovery and now im hit with "Secure Booting Error! Cause : boot certification verify" instead of TWRP!
Ive tried to use this method > http://forum.xda-developers.com/showthread.php?t=2625044 to flash back to stock and unroot BUT when i get to step 5. of method 1. instead of asking to to Select Country & Language it starts the LGMobile Support Tool and the tool tells me i have the latest available software for my device.
The phone is running fine and i can get into download mode.
Thanks in advance for any help.
Click to expand...
Click to collapse
The ROM you flashed is from my thread. I'm not sure why you think custom recovery remains available? Unless I've missed something else you did. It is overwritten by the stock ROM when flashed. Hence I clearly stated that custom recovery will no longer be available.
I don't know what "messed up" with the ROM?
I suggest you revisit the page you used and try the alternative method if you really fell the need to downgrade...

Well after 5 house of messing around i managed to ADB push CM11 too my device, Boot the phone then connect to my PC then re-flash 4.4.2 & root using this method > http://forum.xda-developers.com/showthread.php?t=2680789
Think ill just stick to 4.4.2 lol.

ATOJAR said:
Well after 5 house of messing around i managed to ADB push CM11 too my device, Boot the phone then connect to my PC then re-flash 4.4.2 & root using this method > http://forum.xda-developers.com/showthread.php?t=2680789
Think ill just stick to 4.4.2 lol.
Click to expand...
Click to collapse
Yes, that's my ROM...
Sent from my LG-D802 using XDA Premium 4 mobile app

rooting and TWRP update problem

hello all.
im using a G2 D800 AT&T, and since i have a tethering problem which i was assured would be fixed if i installed a new ROM.
so i went ahead with a guide for cloudyg3 rom, rooted using towelroot and verified with root checker, all is well.
installed TWRP with freegee- the TWRP version was 2.6.3.3 and i was told i needed to upgrade it to at least 2.7.1.. thats where problems started.
i couldnt for the life of me upgrade it to any version, 2.7.1 or higher, and TWRP showed a loki.sh problem. thought maybe unrooting and starting the process all over would fix it so i deleted all my apps, then unrooted with supersu.
tried to root with towelroot and no go. immediately after trying to root, root chekcer gave me a "device is not rooted" answer (before there was no problem), and the device reboots just after im trying to remove towelroot from the task manager (center button).
did i mess up my phone so it cant root? is there a way to check that\ other root methods?
please help

Try other methods like ioroot and if still not working flash a new kdz via download mode and reroot with some method. And btw you can easily update twrp by flashing just a zip but don't forget to restart the recovery after flashing and restore defaults under setting. And next time try autorec
Sent from my GT-N8010 using XDA Free mobile app

Use autorec
_____________________________________Read more write less and be smart

Krenol said:
Try other methods like ioroot and if still not working flash a new kdz via download mode and reroot with some method. And btw you can easily update twrp by flashing just a zip but don't forget to restart the recovery after flashing and restore defaults under setting. And next time try autorec
Sent from my GT-N8010 using XDA Free mobile app
Click to expand...
Click to collapse
How Do i go about installing ioroot? Didnt see a apk file or nothing

Ioroot works via computer
Sent from my GT-N8010 using XDA Free mobile app

first, thanks for your help.
second, i got the device rooted and all, installed TWRP through freegee and downloaded newer version (2.7.1),
and when i booted the device into TWRP mode and tried updating to 2.7.1. , THE SAME THING HAPPEND AS BEFORE-
i just cant update the twrp to more than 2.6.3.3., no matter what version i try (2.7.1 or higher).
getting error message of: assert failed: run_program (temp\loki.sh)
error executing updater binary in zip \sdcard
error flasing zip \sdcard\download\...
updating partition details.
and getting two options: wipe chache\ dalvik, and reboot system.
this happend to me with EVERY TWRP UPDATE I TRY...
and from my understanding i must update twrp to more than 2.6.3.3 before trying to flash new roms.
thats the problem i had before as well, device simply wouldnt update to more than 2.6.3.3
thanks...

I rooted with towelroot then used AutoRec (link) to install TWRP on mine then updated to 2.8.3.1 from blastagator (link) via the older TWRP I installed.

WTF...PROBLEM
i installed autorec, clicked okay and got into the twrp boot recovery mode again, and tried to instal new version with same failed result (pictures added).
but then, i clicked on reboot, device rebooted, BUT DIDNT BOOT BACK TO NORMAL SCREEN.
now the screen is black with a green\blue led that keeps flashing and wont stop.
computer recognizes the device when connected with a USB.
WTF?

shaul123 said:
WTF...PROBLEM
i installed autorec, clicked okay and got into the twrp boot recovery mode again, and tried to instal new version with same failed result (pictures added).
but then, i clicked on reboot, device rebooted, BUT DIDNT BOOT BACK TO NORMAL SCREEN.
now the screen is black with a green\blue led that keeps flashing and wont stop.
computer recognizes the device when connected with a USB.
WTF?
Click to expand...
Click to collapse
Try push a recovery img via adb

Krenol said:
Try push a recovery img via adb
Click to expand...
Click to collapse
can you try to expand a little bit? im new at this
okay so it doesnt even recognize the phone as MTP....
what happend?
the led doesnt stop flashing green tho

shaul123 said:
can you try to expand a little bit? im new at this
okay so it doesnt even recognize the phone as MTP....
what happend?
the led doesnt stop flashing green tho
Click to expand...
Click to collapse
can you enter download mode?

Krenol said:
can you enter download mode?
Click to expand...
Click to collapse
cant do ANYTHING.
screen is black and the led is flashing green and blue nonstop.
tried turning it on or pressing the volume down+power button but nothing (i added a picture). computer wont recognize the phone either.
when i try to call the phone is off
please help
the phone seemed to be in twrp 2.7.0 although it showed me a failed result

I'm not very sure but maybe its was something from the freegee app... you should't have any loki error
So your screen its COMPLETELY black?.. even you hold the power button or something it didnt show anything on screen?...at least if you hold the power button the led stops to flash?

UPDATE
so after i did hard factory reset i am in boot recovery mode, with a twrp version of 2.7.0.0
still cant get past the LG logo (LED keeps flashing) but at least i can be in recovery mode.
computer recognizes that the phone is connected with USB but cant get it to appear as MTP
thanks
i read up and i THINK im in a boot loop.
maybe i was really stupid- are you suppose to use autorec only on kitkat devices and nothing else? my device is 4.2.2.

Yea, I'm on the same boat. I was on 10b (4.2.2) tried using freegee. Freegee said it didn't support my device went to auto rec. Auto rec managed to flash trwp made the backup then was told to reboot the phone. Then I got the same black screen with the blue green led. I plugged in he phone to the computer and pressed volume up and the power button and I got the hard reset option. I confirmed the hard and now I have rebooted into twrp.
Word of the wise: once in trwp don't restore your backup. It doesn't work. See other thread on this.
Sent from my VS980 4G using Tapatalk

Soft brick / bootloader acces urgent help please.

I installed a custom rom, decided I wanted to go back to stock by restoring from TWRP, now in bootloop. I can boot into recovery and bootloader via the phone but my PC does not recognise that it is connected via bootloader. Is there a way I can rescue my device?
I have build B29M, and noticed there is a zip version of another build on this forum which I could have installed through TWRP, but would that make things worse?
Thanks for any advice..

Stupid question probably, as you've already installed a custom ROM, but you do have the fastboot drivers installed on your PC?

Yes it all worked before, I think it's because the phone must have defaulted back to not being in Debugging mode, and I can't access the OS to enable this mode.

leicablue said:
Yes it all worked before, I think it's because the phone must have defaulted back to not being in Debugging mode, and I can't access the OS to enable this mode.
Click to expand...
Click to collapse
Well, if you can reach recovery, flash another custom ROM to get the phone usable, then flash back to stock, looking at points 11 and 12.

I managed to fix it, for anyone who may encounter similar issue in the future...I tried restore again from TWRP but this time did not select Vendor Image, only Vendor.

I have this same problem, my PC doesn't see the phone when I go to bootloader and I can't fastboot at all. I can use my phone regularly copy files over. I already flashed to a new ROM from cataclysm to purenexus but still can't fastboot.
Sent from my Nexus 6P using Tapatalk