Database Info

[Q] Stuck in bootloop.

Hi everyone.
I have the following problem with a Nexus 5: During an update, the system crashed. The phone is now stuck in an endless bootloop, trying to install the update. When left long enough, the update screens eventually come up, but you are immediately blasted with a ton of errors and no matter what you do, you are unable to complete the update. This, however, is not the problem.
I have tried various utilities in order to flash the phone back to factory settings. I have made use of Unified Android ToolKit, as well as Nexus Root Toolkit, but a problem with the phone itself is preventing me from flashing it and the problem is as follows: I can access the phone via USB, as well as the bootloader, but when I unlock the bootloader to start the flashing, it immediately locks itself again and I'm unable to start the flash process.
I've searched for other instances in which the bootloader won't unlock, but I can't find any information. Is there perhaps a hardware problem preventing me from unlocking the bootloader or can someone help me find a solution to this problem?

Mystical_Titan said:
I've searched for other instances in which the bootloader won't unlock, but I can't find any information. Is there perhaps a hardware problem preventing me from unlocking the bootloader or can someone help me find a solution to this problem?
Click to expand...
Click to collapse
If the lock state reverts on a reboot, 99 times out of 100, it means the internal memory has an issue. RMA.

rootSU said:
If the lock state reverts on a reboot, 99 times out of 100, it means the internal memory has an issue. RMA.
Click to expand...
Click to collapse
Thanks for the fast response. :good:

Mystical_Titan said:
Thanks for the fast response. :good:
Click to expand...
Click to collapse
No probs. Sounds like the update got stuck at the bootloader flash and corrupted. It's probably not a fatal NAND issue, rather corrupt partition or two but it usually means sending it in.
You can try the LG flashtool as a last resort before doing so though, as you never know...
You can find a link to it in the sticky thread in my signature. Best to stay away from actual "toolkits" though and either use fastboot manually or LG flash tool, although fastboot probably cant help you here - just saying for future ref...

Mystical_Titan said:
Hi everyone.
I have the following problem with a Nexus 5: During an update, the system crashed. The phone is now stuck in an endless bootloop, trying to install the update. When left long enough, the update screens eventually come up, but you are immediately blasted with a ton of errors and no matter what you do, you are unable to complete the update. This, however, is not the problem.
I have tried various utilities in order to flash the phone back to factory settings. I have made use of Unified Android ToolKit, as well as Nexus Root Toolkit, but a problem with the phone itself is preventing me from flashing it and the problem is as follows: I can access the phone via USB, as well as the bootloader, but when I unlock the bootloader to start the flashing, it immediately locks itself again and I'm unable to start the flash process.
I've searched for other instances in which the bootloader won't unlock, but I can't find any information. Is there perhaps a hardware problem preventing me from unlocking the bootloader or can someone help me find a solution to this problem?
Click to expand...
Click to collapse
happened to me while installing the new SNAPSHOT version of Cyanogenmod, I wiped everything and reflashed it and it works

BruKnowsBest said:
happened to me while installing the new SNAPSHOT version of Cyanogenmod, I wiped everything and reflashed it and it works
Click to expand...
Click to collapse
Can anyone suggest some steps for me to try before I RMA the phone? Although, being unable to unlock the bootloader probably limits my options.

Mystical_Titan said:
Can anyone suggest some steps for me to try before I RMA the phone? Although, being unable to unlock the bootloader probably limits my options.
Click to expand...
Click to collapse
I was stuck in the boot animation and when it opened there was a lot of system errors and it would reboot by itself over and over again.
what fixed it was to do a wipe cache and dalvik and reinstall it

BruKnowsBest said:
I was stuck in the boot animation and when it opened there was a lot of system errors and it would reboot by itself over and over again.
what fixed it was to do a wipe cache and dalvik and reinstall it
Click to expand...
Click to collapse
I tried the 'wipe cache' as well, but it returns a bunch of errors as well. I'm starting to think the NAND is screwed. What is dalvik?

Mystical_Titan said:
I tried the 'wipe cache' as well, but it returns a bunch of errors as well. I'm starting to think the NAND is screwed. What is dalvik?
Click to expand...
Click to collapse
Dalvik cannot break your bootloader. Your only option was use lg flashtool and if that failed, RMA. Let's not get false hopes and waste time not doing this.
Sent from my Nexus 5 using Tapatalk

rootSU said:
Dalvik cannot break your bootloader. Your only option was use lg flashtool and if that failed, RMA. Let's not get false hopes and waste time not doing this.
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
I completely forgot that you mentioned the LG Flashtool, I feel like such an idiot. I'll try that tomorrow as a last resort.

No worries
Sent from my Nexus 5 using Tapatalk

rootSU said:
Dalvik cannot break your bootloader. Your only option was use lg flashtool and if that failed, RMA. Let's not get false hopes and waste time not doing this.
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
i thought about LG FLASHTOOL but decided to try reinstaling the rom cuz i had no other option since i forgot to leave a backup rom on the device. So I did it as if I was installing a brand new rom Wiped dalvik, cache and system then reflashed the rom and then the gapps. Even tho it was the same ROM file I had a different outcome. It's working fine now but I did go back to the nightlies after it started working again just to be safe.
Now... people may have a different outcome when trying to solve this issue but this actually worked for me after having a minor heart-attack thinking I was gonna lose all my stuff

BruKnowsBest said:
i thought about LG FLASHTOOL but decided to try reinstaling the rom cuz i had no other option since i forgot to leave a backup rom on the device. So I did it as if I was installing a brand new rom Wiped dalvik, cache and system then reflashed the rom and then the gapps. Even tho it was the same ROM file I had a different outcome. It's working fine now but I did go back to the nightlies after it started working again just to be safe.
Now... people may have a different outcome when trying to solve this issue but this actually worked for me after having a minor heart-attack thinking I was gonna lose all my stuff
Click to expand...
Click to collapse
Yes, but your issue is different to the OP's. His bootloader lock state reverts whenever he changes it. This is a pretty much "fatal" issue. What you did cannot help him unfortunately.

rootSU said:
Yes, but your issue is different to the OP's. His bootloader lock state reverts whenever he changes it. This is a pretty much "fatal" issue. What you did cannot help him unfortunately.
Click to expand...
Click to collapse
oh ok, I misunderstood

rootSU said:
No worries
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
It speaks about a KDZ file. What is it and where would I find it?

Mystical_Titan said:
It speaks about a KDZ file. What is it and where would I find it?
Click to expand...
Click to collapse
Not sure, never used it. Are you following the Nexus 5 LG Flash tool guide? If not, have a look. You can get to it via my signature

rootSU said:
Not sure, never used it. Are you following the Nexus 5 LG Flash tool guide? If not, have a look. You can get to it via my signature
Click to expand...
Click to collapse
Well, that's that. This phone is done.

Yup. RMA
Sent from my Nexus 5 using Tapatalk

[Q] It's been 4 days and I still can't fix this bootloop!

Okay I had an L rom for about a month maybe less. Then Friday night, it just turns off and now all I see is flying colors.
In the ask any question thread I asked and some really awesome dudes were trying to help me but all of their solutions were in vain.
I used method 1 and 2 of the return to stock.
I made sure I followed EVERY step. Still nothing, it's been trying to boot for far far too long.
I really need my phone, and I'm not sure what else to do. I can't jump because I'm broke and that tamper flag is up.
Can someone help me? I have teamveiwer if it helps.
Also I should say I get several errors I think, like no recovery.sig or boot.sig when I clearly just flashed them.
Why do I get these errors? Is nobody else having the same problem as me? I'm getting really frustrated and to anyone who helps me solve my problem will get my oatmeal raisin cookie recipe (Not kidding, that's serious).
Please somebody help me. Ill be constantly refreshing this page so if you have any questions I will answer them.

Have you booted into the bootloader and used a Google bat file to flash the device completely clean?
Sent from my Android 5.0 Nexus 5

Yes

Follow http://forum.xda-developers.com/showthread.php?t=2513701
Download "15 second adb installer" if you're having issues with adb or fastboot commands
Ignore the .sig errors
Worst case scenario flash each file one by one if flash all.bat doesn't work
Post up what happens after you run flash all.bat too

Have you tried flashing the KitKat factory images instead of Lollipop?

RaggleFraggles said:
Yes
Click to expand...
Click to collapse
Then you must have corrupt hardware, can you not send it back to Google for fix/replacement?
Sent from my Android 5.0 Nexus 5

Either the op fixed the phone and is now celebrating by getting very drunk, or he smashed his phone out of frustration and doesn't care anymore lol.
Either way he's not refreshing this page constantly like he said

I didn't get the insurance or the warranty or nothing

No its still broken but I end up having to help my friend cause he car broke down all day.

No I didn't really want kitkat again, I really wanted to keep L. Ill try it when I can though.

I did both ways, flash all and flash manually but neither worked.

RaggleFraggles said:
No I didn't really want kitkat again, I really wanted to keep L. Ill try it when I can though.
Click to expand...
Click to collapse
Whether you want it or not, try flashing KitKat just to see if it will boot

jsgraphicart said:
Whether you want it or not, try flashing KitKat just to see if it will boot
Click to expand...
Click to collapse
Downloading it now

RaggleFraggles said:
Downloading it now
Click to expand...
Click to collapse
Any luck?

Neither worked in what sense? What happens when u flash? Errors? We can't really help much unless u give us info to go on lol
Sent From Bacon

Someone got to find a fix for this

[Q] Error with OTA update on Stock Android

So I'm running completely stock, never rooted Android 5.0 on my Nexus 5. I got the 5.0.1 update today and when I go to install, it gives me the dead android pic with "error". Anybody else having the same issue? Also, would me enabling developer options have anything to do with it?
P.S. Already cleared my cache partition and it's still giving me the error.

Oh sweet jesus, how many more threads like this we going to have.
You modified /system in some way. Read one of the million threads already here on the forum with similar problem.

beekay201 said:
Oh sweet jesus, how many more threads like this we going to have.
You modified /system in some way. Read one of the million threads already here on the forum with similar problem.
Click to expand...
Click to collapse
or just give it out so we noobs can easily be guided?

beekay201 said:
Oh sweet jesus, how many more threads like this we going to have.
You modified /system in some way. Read one of the million threads already here on the forum with similar problem.
Click to expand...
Click to collapse
Except, like I said, I didn't. I did not root or unlock the bootloader or play around with the phone at all, strictly for this reason. I didn't want to go through the struggle of factory resetting my device every now and then. The closest thing to "modifying" the phone was me unlocking developer settings and I was asking if that could have something to do with it.
Every other thread on the forums has to do with people rooting so no, it's not like one of the millions of other threads.

Describe more.

The best way to update is by flashing the factory image in fastboot, i don`t trust/hate OTA`s personaly

I updated from kitkat to Lollipop with no issues from the OTA update. That was really recent and I haven't changed anything having to do with the system since then. Yet the 5.0.1 update is giving me the error message.
I'm trying to avoid doing a factory reset as that was the main reason that I've kept the phone completely stock. I figured not rooting the phone would let me update in peace and, since it's a nexus, it's been enough to handle my needs without any customization.

kubus908 said:
I updated from kitkat to Lollipop with no issues from the OTA update. That was really recent and I haven't changed anything having to do with the system since then. Yet the 5.0.1 update is giving me the error message.
I'm trying to avoid doing a factory reset as that was the main reason that I've kept the phone completely stock. I figured not rooting the phone would let me update in peace and, since it's a nexus, it's been enough to handle my needs without any customization.
Click to expand...
Click to collapse
Is your bootloader unlocked? I don't know why the ota isn't working but something must have changed on your device
Sent from my Nexus 9 using XDA Free mobile app

jd1639 said:
Is your bootloader unlocked? I don't know why the ota isn't working but something must have changed on your device
Sent from my Nexus 9 using XDA Free mobile app
Click to expand...
Click to collapse
Just double checked and nope, bootloader is locked. Yeah :/ I was trying to see if it's an issue with anybody else on completely stock devices. So far mine is a no go, even though the 5.0 update worked flawlessly. Why would the 5.0 update go through, yet the 5.0.1 believes the system has been modified..?

kubus908 said:
Just double checked and nope, bootloader is locked. Yeah :/ I was trying to see if it's an issue with anybody else on completely stock devices. So far mine is a no go, even though the 5.0 update worked flawlessly. Why would the 5.0 update go through, yet the 5.0.1 believes the system has been modified..?
Click to expand...
Click to collapse
Well, there's a way to get the ota but it is going to be tedious. It involves rooting with towelroot, then using bootunlocker from the play store. That'll allow you to unlock the bootloader without wiping your device. Then you'll need to flash the system, boot, and recovery image with fastboot from the 5.0 factory image. Then do the ota.
Sent from my Nexus 9 using XDA Free mobile app

jd1639 said:
Well, there's a way to get the ota but it is going to be tedious. It involves rooting with towelroot, then using bootunlocker from the play store. That'll allow you to unlock the bootloader without wiping your device. Then you'll need to flash the system, boot, and recovery image with fastboot from the 5.0 factory image. Then do the ota.
Sent from my Nexus 9 using XDA Free mobile app
Click to expand...
Click to collapse
May as well skip the ota if you're going to go through this process.
---------- Post added at 07:06 PM ---------- Previous post was at 07:05 PM ----------
digitLIX said:
or just give it out so we noobs can easily be guided?
Click to expand...
Click to collapse
Or wait for the next time the question is asked.
Should be any minute now.

Thanks! I may just wait until the next update and see if there's a chance it'll work. Or I may just have to do a fresh new install which I am not looking forward to at all Lol. But thank you for your help!

Uhhhh, ok. So I'm not exactly sure what happened. I figured I'd give the OTA another try because why not...and it worked I noticed it downloaded a bigger file too, 30ish mb as opposed to the 13mb OTA that would give me an error. Not sure if I got sent a wrong update file or what, but if your issue comes close to what I experienced, just keep trying the OTA update. I'm also on T-Mobile (phone bought directly from T-Mobile) in case that makes any difference.

Bluetooth issues after long term flashing addiction

So I've searched and haven't found anything similar to what I'm experiencing.
Verizon M8, S-OFF, flash more than once a day sometimes. I recently had the 4G LTE issue that required I return back to stock recovery to fix nv partition through factory reset.
Since then, I've noticed that my bluetooth connects just fine to my uConnect for audio, but not phone functionality. It doesn't seem to be an issue with my ROM because I've tried multiple and experience the same issue, and a friends iPhone paired without issue.
Is it possible theres another partition that I screwed up?
Please let me know if I left out any vital information..
Thanks guys!

Have you tried reflashing your firmware?

cntryby429 said:
Have you tried reflashing your firmware?
Click to expand...
Click to collapse
I did, through the fastboot process and hboot as well.

How about a different one? There's digital high's, aer0's, and I think one from the sundream's srom thread. Not to mention any fixes that may come from our new update rolling out now.

cntryby429 said:
How about a different one? There's digital high's, aer0's, and I think one from the sundream's srom thread. Not to mention any fixes that may come from our new update rolling out now.
Click to expand...
Click to collapse
I'm going to try are0s again but through the fastboot method. I'll post back here soon.
Thanks

I also understand it's recommended to flash it twice in fastboot.

cntryby429 said:
I also understand it's recommended to flash it twice in fastboot.
Click to expand...
Click to collapse
Fixed! I'm not sure if reflashing the aero firmware fixed it or deleting the audio device on my head unit before pairing again did. This could have just been a major brain fart.

Glad you're back on track either way.

Flashfire forcecloses.

I downloaded the Flashfire apk in hopes I'd be able to flash from my phone without recovery and every time I try going into the app, it instantly force closes. Has this happened to anyone else?

It's probably because your bootloader is unlocked.
Honestly though I haven't heard of this.
I'm assuming you have the latest version and that you are rooted correct?
Has it worked at all on your setup?
Have you tried factory resetting, installing, and trying?
Maybe this might help someone who is more capable of helping than I am.
Sent from my SM-G920V using Tapatalk

twiz0r said:
It's probably because your bootloader is unlocked.
Honestly though I haven't heard of this.
I'm assuming you have the latest version and that you are rooted correct?
Has it worked at all on your setup?
Have you tried factory resetting, installing, and trying?
Maybe this might help someone who is more capable of helping than I am.
Sent from my SM-G920V using Tapatalk
Click to expand...
Click to collapse
Have the latest version and I'm rooted. I've tried multiple times. Ah, I guess I'll just continue trying.

No issue with stock rooted.

No good. I knew one of the last 3 updates had a force close issue on 64 bit fixed. Was hoping it was that easy. Hopefully someone else will pop in for ya
Sent from my SM-G920V using Tapatalk

twiz0r said:
No good. I knew one of the last 3 updates had a force close issue on 64 bit fixed. Was hoping it was that easy. Hopefully someone else will pop in for ya
Sent from my SM-G920V using Tapatalk
Click to expand...
Click to collapse
Thanks

twiz0r said:
It's probably because your bootloader is unlocked.
Honestly though I haven't heard of this.
I'm assuming you have the latest version and that you are rooted correct?
Has it worked at all on your setup?
Have you tried factory resetting, installing, and trying?
Maybe this might help someone who is more capable of helping than I am.
Sent from my SM-G920V using Tapatalk
Click to expand...
Click to collapse
My supposed "unlocked bootloader." Ha! You got me laughing.

deliberate.dev said:
My supposed "unlocked bootloader." Ha! You got me laughing.
Click to expand...
Click to collapse
I had to throw that in there on ya. Sorry
I'm not always an @$$hole I swear

twiz0r said:
I had to throw that in there on ya. Sorry
I'm not always an @$$hole I swear
Click to expand...
Click to collapse
Good to know.

deliberate.dev said:
I downloaded the Flashfire apk in hopes I'd be able to flash from my phone without recovery and every time I try going into the app, it instantly force closes. Has this happened to anyone else?
Click to expand...
Click to collapse
There is one thing you might try. Delete the app. Go to your root folder data/data and delete the eu.chainfire.flash folder. Download and install the app again and see if it works.

Tulsadiver said:
There is one thing you might try. Delete the app. Go to your root folder data/data and delete the eu.chainfire.flash folder. Download and install the app again and see if it works.
Click to expand...
Click to collapse
Tried your suggestion, still doesn't work. Oh well, I'll just have to wait til something else comes along that'll let me flash.

deliberate.dev said:
I downloaded the Flashfire apk in hopes I'd be able to flash from my phone without recovery and every time I try going into the app, it instantly force closes. Has this happened to anyone else?
Click to expand...
Click to collapse
Where did you download the apk from?
What version is it?
When you say it "force closes", are you getting an error message?
Sent from my NCC-1701 using Tapatalk.

Finally got it working... then I go and upgrade my phone last night. Can't even use it til a new root method comes out.

deliberate.dev said:
Finally got it working... then I go and upgrade my phone last night. Can't even use it til a new root method comes out.
Click to expand...
Click to collapse
how did you get it working?

jonthn41 said:
how did you get it working?
Click to expand...
Click to collapse
setting your time to the year 2013
cant be connected to the internet

AlphaDroidzer said:
setting your time to the year 2013
cant be connected to the internet
Click to expand...
Click to collapse
why 2013 ? because thats when the device had its last software update?.. im trying to figure out how to get flashfire working on my tablet

jonthn41 said:
why 2013 ? because thats when the device had its last software update?.. im trying to figure out how to get flashfire working on my tablet
Click to expand...
Click to collapse
from what I gathered on google....
Devs stop supporting free version
if you dont want it to crash then buy pro