Database Info

[Q] I have problems with updating lollipop 5.0 in my Nexus 4.

So, my phone was stuck in No Command bootloop. I’ve done the power+volume up and had cleared cache and even done a factory reset. Those did nothing and my phone is still in stuck No Command loop. I think I’ve made it even worse by trying to Flash Recovery and Reboot options in the Nexus Tool Kit because my phone won’t even get to the No Command screen. It just turns on and turns off after Google comes on. Currently it stuck in that loop and only stops once the battery is completely drained. Also i have tried using power + volume up and it doesn't help . Please help

vigneshkumargv said:
So, my phone was stuck in No Command bootloop. I’ve done the power+volume up and had cleared cache and even done a factory reset. Those did nothing and my phone is still in stuck No Command loop. I think I’ve made it even worse by trying to Flash Recovery and Reboot options in the Nexus Tool Kit because my phone won’t even get to the No Command screen. It just turns on and turns off after Google comes on. Currently it stuck in that loop and only stops once the battery is completely drained. Also i have tried using power + volume up and it doesn't help . Please help
Click to expand...
Click to collapse
As you've upgraded to lollipop ?? You came from a custom rom ?? Enters the bootloader?

vigneshkumargv said:
So, my phone was stuck in No Command bootloop. I’ve done the power+volume up and had cleared cache and even done a factory reset. Those did nothing and my phone is still in stuck No Command loop. I think I’ve made it even worse by trying to Flash Recovery and Reboot options in the Nexus Tool Kit because my phone won’t even get to the No Command screen. It just turns on and turns off after Google comes on. Currently it stuck in that loop and only stops once the battery is completely drained. Also i have tried using power + volume up and it doesn't help . Please help
Click to expand...
Click to collapse
with wugfresh nexus root toolkit click on the button "soft-bricked"(flash stock + unroot) or something like that to restore the phone. After that try another time to unlock and root with a custom recovery (for example twrp).
When nexus root toolkit installing the original lollipop rom, look the "dos window" to see if the software shows errors, because sometimes the process ends without a real restore.
If you have other problems, please post a screenshot.

Fenix46 said:
As you've upgraded to lollipop ?? You came from a custom rom ?? Enters the bootloader?
Click to expand...
Click to collapse
Yes I was using a custom rom, but I not even reached the step where a was supposed to use the rom, I was steel still cleaning the divece.
Here is a photo from the screen I'm stuck in:
eeee.... I'll find a wint to send the photo to this forum ^^" wait

[Completed] Secure Booting Unsuccessful error

Folks, I have seen some threads on here so I will understand that you will probably hate me but seriously none of those did well for me. So that's why I am creating mine. As an owner of LG G2 mini I had been closely focusing on CM12 progress re lollipop that InvaderJohn was working on. There was a camera overexposure issue so I tried to use some working lib files and vendor/lib files and created a flashable file for TWRP recovery. I screwed it up as upong the flash my phone with CM12 didn't boot up. I wasn't able to get into recover thru adb so I pressed volume down and middle button and got myself into factory mode. I did factory reset and was in TWRP recovery again. Good. Then I reflashed the phone and there was an error saying that secure booting unsuccessful. I have LG Flashtools and tot file with dll for my LG D620fr on my laptop. This method I used once when getting the phone bricked and it worked and I was able to install stock 4.4.2 ROM. But this time... not sure why but the tot flash got stuck with 94% and while the phone was supposed to get restarted it didn't and the message above of the secure etc. popped up. I am able to get into my TWRP recovery (weird) but nothing else. I suspect I got my bootloader locked. Is there any way how to figure this out, please? I was trying the fastboot method but my phone is unrecognizeable. Any help is much appreciated.

enzo_cz said:
Folks, I have seen some threads on here so I will understand that you will probably hate me but seriously none of those did well for me. So that's why I am creating mine. As an owner of LG G2 mini I had been closely focusing on CM12 progress re lollipop that InvaderJohn was working on. There was a camera overexposure issue so I tried to use some working lib files and vendor/lib files and created a flashable file for TWRP recovery. I screwed it up as upong the flash my phone with CM12 didn't boot up. I wasn't able to get into recover thru adb so I pressed volume down and middle button and got myself into factory mode. I did factory reset and was in TWRP recovery again. Good. Then I reflashed the phone and there was an error saying that secure booting unsuccessful. I have LG Flashtools and tot file with dll for my LG D620fr on my laptop. This method I used once when getting the phone bricked and it worked and I was able to install stock 4.4.2 ROM. But this time... not sure why but the tot flash got stuck with 94% and while the phone was supposed to get restarted it didn't and the message above of the secure etc. popped up. I am able to get into my TWRP recovery (weird) but nothing else. I suspect I got my bootloader locked. Is there any way how to figure this out, please? I was trying the fastboot method but my phone is unrecognizeable. Any help is much appreciated.
Click to expand...
Click to collapse
Sounds like the bootloader is locked.
Check this thread: How to check for locked bootloader? ... but it's for the LG G3.
Best place to ask is the G2 Mini Q&A, Help & Troubleshooting.

Thread closed and thank you.

Stuck in "Warning Bootlaoder is Unlocked" Loop and Need Help

I have looked at multiple guides on this and other sites, googled and tried stuff and I cannot resolve this problem. Hopefully I am posting in the right place.
I took the jump and unlocked the bootloader on my Moto G first generation, XT1034 successfully. I flashed TWRP 2.8.60.xt1034.zip with adb and this was successful. Then I flashed Super SU 4.6 Update and that was successful. I got into trouble I guess when I tried to flash Cyanogenmod 12.1 nightly. I used TWRP to flash via install. The flash had an error, which unfortunately I didn't write down. I believe it was something to do with a partition. However, it looked like the flash failed. At this point and for hours I have been trying to fix the "Warning Bootloader Unlocked Loop I am stuck in.
I have been able to get into the phone and flash via adb commands. I've tried several commands suggest to fix this that I have found in forums. I have tried flashing several recoveries including an older TWRP per the method in this thread, a clockworkmod - and the original 2.8.6.0.xt1034. When I get into the phone bootloader which is available, I have not been able to access any options in recovery. Pushing the power button on recovery leads to a blank screen sometimes followed by a recovery starting or a Motorola Logo starting up and a couple times a recovery. TWRP has started a couple times, but never gets past the intro screen, where it locks up. clockworkmod (clockworkmod-6.0.4.7-falcon.img started once after flashing through adb and gave me flash options. I tried to sideload, didn't understand, went back and the recovery locked up. These recoveries no longer load at all.
Through all of this the "Warning Bootloader Unlocked" logo screen comes up after plugging into the computer (Windows 8.1).
Example, I open the phone bootloader by waiting for the phone screen to go from the "Warning Bootloader Unlocked" screen to blank - it cycles from logo to blank. If I'm quick the phone and hard boot the phone will boot into bootloader. I connect to the laptop through USB. When I toggle to recovery and hit the power button the screen goes blank, the Motorola Logo pops up, goes blank and then the "Warning Bootloader Unlocked" appears. The Laptop then seems to connect and disconnect as the Warning screen comes on and turns off.
The factory selection just goes to a blank screen.
I would really appreciate some advice on how to get the phone back to a state in which I can work with it and try again. It is very difficult wading through all of the information out there. I've learned a lot through this issue, but can't take it any further.
Thanks, Jeff

Solved - Stuck in "Warning Bootloader Is Unlocked" Loop
This resolution took many hours to figure out, but I finally got there with this guide - http://forum.xda-developers.com/showthread.php?t=2542219, this thread - http://forum.xda-developers.com/showthread.php?p=54855457#post54855457 and this thread - http://forum.xda-developers.com/gen...e-firmware-t3042687/post59139823#post59139823.
I tried RSD Lite on different computers and USB cables I could not get the device recognized. So I ended up with the MfastbootV2 method to reload stock firmware, which I found on the firmware thread above - this was big, as my phone is with Wind Mobile in Canada and the link is the right one. The only thing I picked up from a different website was to use a computer with USB 2 ports. This is what I did, but I don't know one way or the other if USB 2 was needed. .
Can't thank you hard working guys enough for the time you take to put these threads together. I'm back up and running. As a bonus, after a big clean up in the process, my phone is running fast again.
Thanks everyone.

Nexus 5 us Stuck in Bootloop - Nothing Works and cant unlock The Phone.

Hi all,
I have a Nexus 5 that I bought second hand. It powers up but is stuck in a bootloop. The Google Logo appears and it starts to load but it does not progress. I can get in to boot loader and I have tried to do a factory reset but it it still stays in the boot loop. I have tried to install the new factory software using the Nexus Root Toolkit but nothing. The Phone is also locked and I cant unlock the phone so the Nexus Root Toolkit wont allow me to try to flash the stock image? I am at the end of my knowledge base as I have tried almost all the normal methods to unbrick and fix the boot loop. The Phone can access the boot loader. When I try to unlock the phone using the Nexus Root Toolkit, it unlocks it but does not write the data and it becomes unresponsive! I have no idea if USB developer is on in settings as I have never got in to the Android operating system as I cant get past the bootloop.
Your help and suggestions would be most helpful as I am now at an end of my abilities until I am further educated about how to resolve the issue.
Res

I haven't tried this myself (no need), but since you seem to have nothing to lose give it a go. It's official Google, and comes with instructions.
https://developers.google.com/android/nexus/ota#instructions

Does the fastboot oem unlock command work?

Do you have all the correct usb and adb drivers installed??
First off, I suggest doing some reading up on adb and fastboot. Then manually flash factory images first and try to boot the phone completely.
The links @dahawthorne will help a lot.
Then try the command that @audit13 mentioned.

[HELP] OPO can't boot into fastboot/recovery. Stuck at boot logo

Hello.
First of all, i'm sorry if this question have been asked before. Believe me, i've tried searching even through Google's 2nd page but still no luck in finding answer.
I had a OPO 64GB version. It was working fine until i decided to do ROM update. My previous working ROM is "CM13-20160812-somethingsomething-SNAPSHOT.zip". It is rooted with Xposed installed
I tried to update it using TWRP. the update is "CM13-20161216-somethingsomething-SNAPSHOT.zip". It got stuck at "Patching system image unconditianally"(probably wrong spelling there) for more than one hour. So, i decided to force reboot it and it is now stuck at boot logo(not bootanimation)
Thing is, i cant get it into fastboot, nor recovery. it just stuck there and i've tried to Power Cycle but still no result. I tried to plug it into my computer and it does detect it in "Device Manager" under "Portable Devices" with name "A0001".
I wonder if it soft brick or hard brick. I'm asking brilliant mind in here, if there's a way to restore it. I just revived it from broken screen since 2016(talk about bad luck) and i don't want to completely replace as the device is still in good condition.
Also, if there's no other choice then i had no other way than to follow this guide here, which completely unbrick my phone(also losing me 30+ apps)
http://www.androidbrick.com/unbrick-oneplus-one-two-3-3t-qualcomm-hs-usb-qdloader-9008/
or
http://forum.xda-developers.com/oneplus-one/help/guide-unbrick-oneplus-one-t3013732

Nevermind. i got it to work by installing QPST driver. for some reason it enable adb at boot logo(yes at boot logo). got into recovery and recover my system partition(which is broken).
I ask the mod to delete this thread. Thank you