Database Info

[Help!] XT926 Mega Bricked

Everything is screwed for me. I can't even RSD back to stock. I can access TWRP, but can't wipe System or Data. Fastboot is just there and won't actually push anything. I already have a Moto X now, and I was talking about this issue about a week ago on the Android Development subcat, but I thought I would give it one last go on here to see if I can at least make it a backup.

kungpowchicken said:
Everything is screwed for me. I can't even RSD back to stock. I can access TWRP, but can't wipe System or Data. Fastboot is just there and won't actually push anything. I already have a Moto X now, and I was talking about this issue about a week ago on the Android Development subcat, but I thought I would give it one last go on here to see if I can at least make it a backup.
Click to expand...
Click to collapse
Maybe if you could give some more detail about what exactly you can and can't get the phone to do, what screens can be accessed, and what you did that lead to this condition, we could offer some advice.
Also, no offence to the devs, but twrp is the devil lol. Most issues I have had in the past have led back to it in one way or another, so I never use it. (Just my opinion)
Tappin G2 Style

I can get to the Fastboot screen, I can access TWRP, and I can get the phone to bootloop at the boot animation screen.
I can't push anything through ADB or Fastboot, I cannot mount data or system in TWRP or otherwise. RSD comes back failed every time with every single stock build I use.
Literally two weeks ago, I was in bed, watching TV, with the phone charging. I unlock it to see if I had any notifications, and it kept saying that Nova launcher FC'd. So logically, I rebooted my phone and that's when it started boot looping.
I did nothing to the phone for a couple of hours, it was on the official CM 10.2 11/9 build. I had that ROM running fine for at least 24 hours before it went FUBAR.

kungpowchicken said:
Everything is screwed for me. I can't even RSD back to stock. I can access TWRP, but can't wipe System or Data. Fastboot is just there and won't actually push anything. I already have a Moto X now, and I was talking about this issue about a week ago on the Android Development subcat, but I thought I would give it one last go on here to see if I can at least make it a backup.
Click to expand...
Click to collapse
Is it this problem?: http://forum.xda-developers.com/showpost.php?p=47558893&postcount=47
If so use this solution: http://forum.xda-developers.com/showpost.php?p=47716278&postcount=57

scoobaspeaz said:
Is it this problem?: http://forum.xda-developers.com/showpost.php?p=47558893&postcount=47
If so use this solution: http://forum.xda-developers.com/showpost.php?p=47716278&postcount=57
Click to expand...
Click to collapse
Nope, my status us unlocked: 3. But when I get home, I'll try the mfastboot instead if fastboot.

kungpowchicken said:
I can get to the Fastboot screen, I can access TWRP, and I can get the phone to bootloop at the boot animation screen.
I can't push anything through ADB or Fastboot, I cannot mount data or system in TWRP or otherwise. RSD comes back failed every time with every single stock build I use.
Literally two weeks ago, I was in bed, watching TV, with the phone charging. I unlock it to see if I had any notifications, and it kept saying that Nova launcher FC'd. So logically, I rebooted my phone and that's when it started boot looping.
I did nothing to the phone for a couple of hours, it was on the official CM 10.2 11/9 build. I had that ROM running fine for at least 24 hours before it went FUBAR.
Click to expand...
Click to collapse
i made a modified utility to fix the partition error but need someone to test it please. it should do the process previously suggested automatically through the script.
http://www.mediafire.com/download/987490ykl14j4t8/DROID_RAZR_HD_Utility_1.3.gpt_fix.rar
thanks

bweN diorD said:
i made a modified utility to fix the partition error but need someone to test it please. it should do the process previously suggested automatically through the script.
http://www.mediafire.com/download/987490ykl14j4t8/DROID_RAZR_HD_Utility_1.3.gpt_fix.rar
thanks
Click to expand...
Click to collapse
Testing now.
UPDATE: Still no go.

kungpowchicken said:
Testing now.
UPDATE: Still no go.
Click to expand...
Click to collapse
Well that sux.
Your problem is different than what I made this for but I was hoping it would work for you.
What did it do, fail all the way through?
When I tested it on my phone it reported flashing the partitions ok. There was actually extra text displayed while it was doing it that I didn't put into the script, that's how I knew it was working.
Tappin G2 Style

Failed all the way.

kungpowchicken said:
Failed all the way.
Click to expand...
Click to collapse
im running out of suggestions
if you havent tried to put stock recovery back on yet, how about we try that and see what happens.
if you dont know how to do it through adb, just grab the 1.34 utility from the dev forum, it will push it through fastboot.
something is obviously wrong with twrp, maybe we can fix that first.

I tried flashing even the stock Recovery manually and through the 1.34 utility. Always comes up failed. :sad:

Did you try the manual steps that I posted in my links?

i hope that works, but im doubtful.
the utility essentially flashes exactly as you would manually.
he doesnt have a partition issue, im guessing something is wack with the permissions.
if twrp somehow screwed up the permissions to read only, i believe even the partition file cant overwrite it. i could be wrong.

So I think it has something to do with the Permissions of one or more of the partitions. I just noticed it keeps saying Permissions Denied when I try to fastboot or mfastboot.

kungpowchicken said:
So I think it has something to do with the Permissions of one or more of the partitions. I just noticed it keeps saying Permissions Denied when I try to fastboot or mfastboot.
Click to expand...
Click to collapse
Are you sure you have the snapdragon fastboot? Can't hurt to reinstall it.
Sent from my MB886 using Tapatalk
Also have you tried flashing it manually? (fastboot flash system system.img, etc.)

penser said:
Are you sure you have the snapdragon fastboot? Can't hurt to reinstall it.
Sent from my MB886 using Tapatalk
Also have you tried flashing it manually? (fastboot flash system system.img, etc.)
Click to expand...
Click to collapse
he defiantly has the right fastboot, its in the utility that has been downloaded thousands of times.
if its write protected some how, its not going to flash no matter how you try it.
what i was wondering is if recovery can fix permissions that deep, not sure he said he tried that.

What do you mean with recovery?

kungpowchicken said:
What do you mean with recovery?
Click to expand...
Click to collapse
go into twrp, advanced (i think thats the right section) and look for a line that says "fix permissions" and do it.

Keeps saying it can't mount anything.

kungpowchicken said:
Keeps saying it can't mount anything.
Click to expand...
Click to collapse
thats what i figured would happen

[Q] Activation Problem - Boot Loop

So I sold an unopened, sealed Nexus 5 to someone last night and he's having a problem activating the device.
Here is his description of what happened:
"I popped in the SIM card, the loading proceeded as normally. It said it was activating and then a box popped up saying that "android is upgrading system files" or something like that. It restarted and went back to the language selection screen. I pressed English, next and then it went to the connect to wifi screen, froze and then restarted before I could even connect. Now it just loads on the boot"
I had him boot into recovery and do a factory reset, but the result is the same. I had him do a 2nd factory reset just be sure, but again, same result.
My thought is the system upgrade didn't happen correctly and not is corrupted.
What's the best course of action? Can I use the WugFresh toolkit to flash stock and unroot, or would I have to do it through ADB since the phone can't boot into the system?
I don't want to leave the buyer hanging, he seems like a nice guy, but I'm just not sure how to proceed?

Use ADB and flash the factory image for him.

Synyster06Gates said:
Use ADB and flash the factory image for him.
Click to expand...
Click to collapse
That's what I figured. I'm not super familiar with ADB but can figure it out I'm sure.

SeanPlunk said:
That's what I figured. I'm not super familiar with ADB but can figure it out I'm sure.
Click to expand...
Click to collapse
Easy walkthrough:
1) Install ADB drivers (You can do it with WUG Toolkit).
2) Reboot your device in Fastboot mode (Hold up/down volume and power)
3) Download the latest HAMMERHEAD image from google website.
4) Download the Google SDK (not needed, but you will need Fastboot.exe, so I would recommend downloading the whole thing)
5) Unzip the image (.tar or .tgz I think) to the location where Fastboot.exe is (all the files should be in the same directory, usually platform-tools)
6) Double-click on the flash-all.bat file from the unzipped .tar or .tgz folder, should install stock image on your phone (note that you might need the latest version of Java installed on your computer)
And you're done.
Hope it helped!

switchfo0t said:
Easy walkthrough:
1) Install ADB drivers (You can do it with WUG Toolkit).
2) Reboot your device in Fastboot mode (Hold up/down volume and power)
3) Download the latest HAMMERHEAD image from google website.
4) Download the Google SDK (not needed, but you will need Fastboot.exe, so I would recommend downloading the whole thing)
5) Unzip the image (.tar or .tgz I think) to the location where Fastboot.exe is (all the files should be in the same directory, usually platform-tools)
6) Double-click on the flash-all.bat file from the unzipped .tar or .tgz folder, should install stock image on your phone (note that you might need the latest version of Java installed on your computer)
And you're done.
Hope it helped!
Click to expand...
Click to collapse
Hello, I am the buyer of this Nexus device. I was able to successfully do these steps above, and reload the stock image for the Nexus 5. However, I am still running into issues.
WITH SIM:
I was able to get to the home screen after the initial setup, sent a few test text messages to my Google Voice number successfully, and browse on Chrome for a little bit before the device froze and restarted. After it restarted, I let it load up again, tried setting up my Google account on the device, then it froze again. All of the freezing happens within 3-5 minutes of using the phone.
So I decided to go into the bootloader, and do a factory wipe/cache wipe, and proceed without having the sim card in. I was able to get to the wifi selection screen, select my router, but as soon as the keyboard was suppose to pop up, the device froze and restarted. I am now just stuck on the welcome screen.
Any ideas now?
---------- Post added 29th November 2013 at 12:45 AM ---------- Previous post was 28th November 2013 at 11:56 PM ----------
Update: So I'm not sure what happened, but I ended up locking the device through Wug's Nexus Toolkit, inserted my sim card, and proceeded to set up the phone normally. So far everything has been working perfectly fine. I can receive/send texts, make and receive calls, and do normal functions with the phone without it locking up and restarting. Fingers crossed it'll stay like this.
Any idea on why this would've happened in the first place with the device?
---------- Post added at 01:38 AM ---------- Previous post was at 12:45 AM ----------
Update 2: Well, I noticed that it will randomly reboot every half hour or so it seems. It's kind of random, but I'm not sure what else could be causing these random reboots. The phone itself is working fine, but I just started experiencing random restarts.

Are you still on the stock rom or custom?

neomorphix said:
Are you still on the stock rom or custom?
Click to expand...
Click to collapse
Stock. I did the steps above and flashed the stock rom that I downloaded from Google's website.
---------- Post added at 01:49 AM ---------- Previous post was at 01:48 AM ----------
Jaybot said:
Stock. I did the steps above and flashed the stock rom that I downloaded from Google's website.
Click to expand...
Click to collapse
It was working fine earlier. I put it on the charger and got it to about 50%, used it for a little bit, then bam. It froze, and restarted all over again. I can use the phone maybe 5 - 10 minutes before it starts to recharge. Sometimes It'll automatically reboot after even unlocking the device.

I would do another factory reset and use it for a bit without any additional apps installed. If you are fully stock and locked with this happening I would think about possibly doing an RMA. Also just and FYI make sure you have the seller of your phone call and transfer the warrenty to you so if an RMA is needed you have the ability to do so.

neomorphix said:
I would do another factory reset and use it for a bit without any additional apps installed. If you are fully stock and locked with this happening I would think about possibly doing an RMA. Also just and FYI make sure you have the seller of your phone call and transfer the warrenty to you so if an RMA is needed you have the ability to do so.
Click to expand...
Click to collapse
I will try factory and cache wipe again, and see if that does anything with no apps or anything else installed, and go from there.

Jaybot said:
I will try factory and cache wipe again, and see if that does anything with no apps or anything else installed, and go from there.
Click to expand...
Click to collapse
Sorry its happening. With everything stock and no third party apps or mods there to cause it at least to me things start looking like something bigger might be wrong here.

neomorphix said:
Sorry its happening. With everything stock and no third party apps or mods there to cause it at least to me things start looking like something bigger might be wrong here.
Click to expand...
Click to collapse
I think so too. No go after another factory wipe/cache wipe. It reboots automatically after awhile. I haven't had this kind of issue before, so I'm not sure what is causing it.

Jaybot said:
I think so too. No go after another factory wipe/cache wipe. It reboots automatically after awhile. I haven't had this kind of issue before, so I'm not sure what is causing it.
Click to expand...
Click to collapse
Yeah im kindof at a loss here as well. I have had those issues before but they have always been due to something I have added thats messing things up. I am interested to see if anyone else has any ideas.

neomorphix said:
Yeah im kindof at a loss here as well. I have had those issues before but they have always been due to something I have added thats messing things up. I am interested to see if anyone else has any ideas.
Click to expand...
Click to collapse
I figured it would be a sim card issue since it was working for awhile without the sim, but I did the factory/cache thing without the sim card, signed on via wifi, but it still doesn't work. So I am seeing what my options are from here. Thanks for all the tips everyone.

Jaybot said:
I figured it would be a sim card issue since it was working for awhile without the sim, but I did the factory/cache thing without the sim card, signed on via wifi, but it still doesn't work. So I am seeing what my options are from here. Thanks for all the tips everyone.
Click to expand...
Click to collapse
For some reason I wasnt thinking of this earlier. Can you capture a logcat from the device after a reboot and post that here. Should help track down the problem.

neomorphix said:
For some reason I wasnt thinking of this earlier. Can you capture a logcat from the device after a reboot and post that here. Should help track down the problem.
Click to expand...
Click to collapse
I was going to try and do that earlier. I will try and do that now, but I can't even get past the bootscreen animation at this point. The 4 dots will do the animation, freeze, and just reboot.
I'll keep trying. But, I really think this is just a defective one. I had a white Nexus 5 a few weeks ago and didn't have any of these issues :crying:
Edit: My last restart the phone kept vibrating like crazy before restarting.

Jaybot said:
I was going to try and do that earlier. I will try and do that now, but I can't even get past the bootscreen animation at this point. The 4 dots will do the animation, freeze, and just reboot.
I'll keep trying. But, I really think this is just a defective one. I had a white Nexus 5 a few weeks ago and didn't have any of these issues :crying:
Edit: My last restart the phone kept vibrating like crazy before restarting.
Click to expand...
Click to collapse
Ok. This just sucks. But as with any mass produced product there is bound to be the ocasional issue.

neomorphix said:
For some reason I wasnt thinking of this earlier. Can you capture a logcat from the device after a reboot and post that here. Should help track down the problem.
Click to expand...
Click to collapse
Honestly it sounds like it's hardware related and time for RMA. OP If you do have ADB set up grab the last_kmsg right after the reboot.
Code:
adb pull /proc/last_kmsg
I doubt it will show any kernel panic but it's worth a shot.

theesotericone said:
Honestly it sounds like it's hardware related and time for RMA. OP If you do have ADB set up grab the last_kmsg right after the reboot.
Code:
adb pull /proc/last_kmsg
I doubt it will show any kernel panic but it's worth a shot.
Click to expand...
Click to collapse
From the sound of it he is now not even getting far enough to be able to pull it. I also think RMA is the best option here.

Jaybot said:
Edit: My last restart the phone kept vibrating like crazy before restarting.
Click to expand...
Click to collapse
neomorphix said:
From the sound of it he is now not even getting far enough to be able to pull it. I also think RMA is the best option here.
Click to expand...
Click to collapse
Just saw that. OP by your earlier symptoms I rules out a stuck power button. With the new info I'd look into it further. If the phone is just looping over and over it could be a stuck power button, Mash the power button repeatedly for a minute. Then try and reboot. A few other people have had this on the N5 already and it's a notorious issue on some Samsung phones.

neomorphix said:
I would do another factory reset and use it for a bit without any additional apps installed. If you are fully stock and locked with this happening I would think about possibly doing an RMA. Also just and FYI make sure you have the seller of your phone call and transfer the warrenty to you so if an RMA is needed you have the ability to do so.
Click to expand...
Click to collapse
If it comes to that, how do I go about transferring the warranty over?
I feel really bad, I just don't get it. I bought two of them, the other buyer hasn't had any problems. Both brand new, sealed, in the box. Go figure.

Added line to build.prop....now bricked?

So I wanted to wake up my nexus 5 with the volume buttons. Looking online I found that you could add code to your build.prop.. which I did.. then rebooted...
Now my phone does 'nothing'... When I press the power button it vibrates 2 times and nothing happens...
Help!.. Have no idea what i can do to get things running again
P.S. I've got Slimkat ROM running

S.Phrenic said:
So I wanted to wake up my nexus 5 with the volume buttons. Looking online I found that you could add code to your build.prop.. which I did.. then rebooted...
Now my phone does 'nothing'... When I press the power button it vibrates 2 times and nothing happens...
Help!.. Have no idea what i can do to get things running again
P.S. I've got Slimkat ROM running
Click to expand...
Click to collapse
Can you get into bootloader? Recovery?

Lethargy said:
Can you get into bootloader? Recovery?
Click to expand...
Click to collapse
Currently, nope... I'm trying.. I see that sometimes the screen is on... sometimes I see the Google Logo... but Can't fully figure out when that happens
[EDIT]YES!!!!!!!!! Got in.!!!!!!... *pfieuw*.. now what do i do?

Reflash the factory with the nexus root toolkit
Croc on Nexus 5 with Mahdi + ElementalX

Croc97 said:
Reflash the factory with the nexus root toolkit
Croc on Nexus 5 with Mahdi + ElementalX
Click to expand...
Click to collapse
Please don't use toolkits.

Croc97 said:
Reflash the factory with the nexus root toolkit
Croc on Nexus 5 with Mahdi + ElementalX
Click to expand...
Click to collapse
Don't exaclty know what you mean with that..
I've downloaded Kwongger's Nexus 5 All-In-One Toolkit , I hope that's what you meant. And then it says it's missing the hammerhead.image.zip... which I assume is the stockROM?.. If so, shouldn't I Reflash to Slimkat?
Sorry for being such a Noob. I've had Samsung for years and just switched to Nexus (bought it last week). Still need to learn my way around things

S.Phrenic said:
Don't exaclty know what you mean with that..
I've downloaded Kwongger's Nexus 5 All-In-One Toolkit , I hope that's what you meant. And then it says it's missing the hammerhead.image.zip... which I assume is the stockROM?.. If so, shouldn't I Reflash to Slimkat?
Sorry for being such a Noob. I've had Samsung for years and just switched to Nexus (bought it last week). Still need to learn my way around things
Click to expand...
Click to collapse
Read my reply to your PM and the 2nd link in my signature, then refer to the first link if you need

Lethargy said:
Read my reply to your PM and the 2nd link in my signature, then refer to the first link if you need
Click to expand...
Click to collapse
Let me start with, Thank you so much for your time
However, It seems like I'm unable to install the right drivers on my PC for my phone and adb doesn't detect my device (which is strange as CF-auto-root did see the device and worked fine)
I walked through multiple tutorials about installing drivers. Actually have windows detecting my phone fine (I see it in device manager) and I've reinstalled google USB drivers multiple times now, rebooting my PC and deleting drivers and reinstalling them
I've justed factory reset my phone, but that just got me to a Google logo stuck (which I read about in your link in your signature)..
Because adb doesn't detect my device I'm unable to pull build.prop... which means I feel stuck again.
Would you have a direction for me to go towards to continue my journey through Nexus5-Land?

S.Phrenic said:
Let me start with, Thank you so much for your time
However, It seems like I'm unable to install the right drivers on my PC for my phone and adb doesn't detect my device (which is strange as CF-auto-root did see the device and worked fine)
I walked through multiple tutorials about installing drivers. Actually have windows detecting my phone fine (I see it in device manager) and I've reinstalled google USB drivers multiple times now, rebooting my PC and deleting drivers and reinstalling them
I've justed factory reset my phone, but that just got me to a Google logo stuck (which I read about in your link in your signature)..
Because adb doesn't detect my device I'm unable to pull build.prop... which means I feel stuck again.
Would you have a direction for me to go towards to continue my journey through Nexus5-Land?
Click to expand...
Click to collapse
If you're using Windows 8, 8.1 or 8.1U1 you'll need to disable driver signature enforcement.
Try flashing the factory images in fastboot?

Could somebody not just make a flashable zip with the correct build.prop?
Failing that, just reflash the ROM.

Lethargy said:
If you're using Windows 8, 8.1 or 8.1U1 you'll need to disable driver signature enforcement.
Try flashing the factory images in fastboot?
Click to expand...
Click to collapse
It seems like it worked! Completly back to StockROM but the phone works again. Thank you so much for your time.
And you're right, I should learn to read and understand what I'm doing before I do anything with my phone. Sorry for the inconvenience and thank you for the help you've given.

S.Phrenic said:
It seems like it worked! Completly back to StockROM but the phone works again. Thank you so much for your time.
And you're right, I should learn to read and understand what I'm doing before I do anything with my phone. Sorry for the inconvenience and thank you for the help you've given.
Click to expand...
Click to collapse
Glad you got it worked out

S.Phrenic said:
It seems like it worked! Completly back to StockROM but the phone works again. Thank you so much for your time.
And you're right, I should learn to read and understand what I'm doing before I do anything with my phone. Sorry for the inconvenience and thank you for the help you've given.
Click to expand...
Click to collapse
Glad you got it sorted but, unless you couldn't boot into recovery, you didn't need to go back to stock.
Flashing the correct build.prop or ROM you were using should have sorted it out, without losing any data (you would have lost any system mods if you flashed the ROM again, though).
I'm only mentioning this in case somebody else searches and finds this thread for the same problem.
I've changed the build.prop loads of times on many devices and only once it went into a bootloop. Flashing a build.prop zip sorted it.

[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] Did my M8 self-destruct?

Yesterday afternoon at work, I rebooted by m8 (Verizon) and didn't realize there was a problem because I put it back in my pocket before it was fully booted. Next time I looked at it, I had no signal and digging deeper, I saw that the baseband is "Unknown" in settings and the IMEI is "U nkn own". I've tried the RUUs for 4.4.3 and 4.4.4 and can't get the phone to see the IMEI and baseband while booted but both show up fine in hboot/fastboot as shown in the attached pics in the next post. I was running the Viper rom when this happened.

Settings and command prompt pics showing problem

bb1981 said:
Yesterday afternoon at work, I rebooted by m8 (Verizon) and didn't realize there was a problem because I put it back in my pocket before it was fully booted. Next time I looked at it, I had no signal and digging deeper, I saw that the baseband is "Unknown" in settings and the IMEI is "U nkn own". I've tried the RUUs for 4.4.3 and 4.4.4 and can't get the phone to see the IMEI and baseband while booted but both show up fine in hboot/fastboot as shown in the attached pics in the next post. I was running the Viper rom when this happened.
Click to expand...
Click to collapse
bb1981 said:
Settings and command prompt pics showing problem
Click to expand...
Click to collapse
Do you always run it in airplane mode?
?

I didn't even realize that when I took the pics but without putting it into airplane mode, it would sit at the htc logo indefinitely until a few minutes pass and it reboots only to get stuck in that cycle unless I jump in and power off. I did forget to mention the reboots after a few minutes in the OP also in case that changes what the issue could be. This was coming off the 4.4.3 RUU and I had the same issue with 4.4.4 and also Sinless 3.5.5(?). It worked great before and I'm just hoping it isn't hardware failure.

bb1981 said:
I didn't even realize that when I took the pics but without putting it into airplane mode, it would sit at the htc logo indefinitely until a few minutes pass and it reboots only to get stuck in that cycle unless I jump in and power off. I did forget to mention the reboots after a few minutes in the OP also in case that changes what the issue could be. This was coming off the 4.4.3 RUU and I had the same issue with 4.4.4 and also Sinless 3.5.5(?). It worked great before and I'm just hoping it isn't hardware failure.
Click to expand...
Click to collapse
Which method did you use for the RUU? Exe or sd?

Initially, I used the exe version but when it have the version number it was going to upgrade to, it was unreadable. Going back to 4.4.3, I flashed the firmware through fastboot then ran the ruu off the sd card. That's also why the sd card is ejected in the first pic so I could get past hboot to make sure it completely powers off.

bb1981 said:
Initially, I used the exe version but when it have the version number it was going to upgrade to, it was unreadable. Going back to 4.4.3, I flashed the firmware through fastboot then ran the ruu off the sd card. That's also why the sd card is ejected in the first pic so I could get past hboot to make sure it completely powers off.
Click to expand...
Click to collapse
Did you try a factory reset from stock recovery/hboot yet?

I'll try that next. I just tried it but it seems like I don't have a recovery installed. Instead of saying recovery booting, it just bootloops.

just tried flashing stock recovery and got stuck in a bootloop again. Running the exe again to try 4.4.4 and still get the same unreadable upgrade version. The version that it's coming from has been right all the time, but the version it's going to I'm guessing should be 3.xxxxx instead of like the screenshot attached.

bb1981 said:
just tried flashing stock recovery and got stuck in a bootloop again. Running the exe again to try 4.4.4 and still get the same unreadable upgrade version. The version that it's coming from has been right all the time, but the version it's going to I'm guessing should be 3.xxxxx instead of like the screenshot attached.
Click to expand...
Click to collapse
That's fine man. It's not an encrypted rom so it doesn't read the plain text file correctly. It will flash what it's supposed to.

dottat said:
That's fine man. It's not an encrypted rom so it doesn't read the plain text file correctly. It will flash what it's supposed to.
Click to expand...
Click to collapse
That's a relief to see that. After I ran it I wasn't sure because it gets stuck on the setup splash screen (thinking it was something not reading correctly on my end and even tried running a second time right away) and I can't get past it at all without airplane mode. I'll have to keep working on it later and see what happens. Thank you for the replies and help, especially with the RUU files and hopefully I can get it figured out. :fingers-crossed::highfive:

bb1981 said:
That's a relief to see that. After I ran it I wasn't sure because it gets stuck on the setup splash screen (thinking it was something not reading correctly on my end and even tried running a second time right away) and I can't get past it at all without airplane mode. I'll have to keep working on it later and see what happens. Thank you for the replies and help, especially with the RUU files and hopefully I can get it figured out. :fingers-crossed::highfive:
Click to expand...
Click to collapse
Did you try flashing the newest twrp 2.8.0.3 recovery ?

Fyi 4.4.4 roms can take up to 20 mins to get to the initial set up screen you might want to hang in there.

Roefastford said:
Did you try flashing the newest twrp 2.8.0.3 recovery ?
Click to expand...
Click to collapse
Twrp does work although I haven't tried it this time just to see if I could try a factory reset to maybe get back my lost baseband and IMEI.
smeejaytee said:
Fyi 4.4.4 roms can take up to 20 mins to get to the initial set up screen you might want to hang in there.
Click to expand...
Click to collapse
I wish I could. The phone once booted will reboot itself after a few minutes.

Oh ok sorry that didn't help.

smeejaytee said:
Oh ok sorry that didn't help.
Click to expand...
Click to collapse
I apologize if the last reply was short and possibly coming across snippy...I was at work and didn't have longer to reply...I think I may have made some very sight progress but the phone still knows nothing about itself once booted. I flashed twrp then wiped system, data, cache and dalvik then proceeded to flash unsense 6 and the 4.4.4 insecure kernel which is recommended by the developer for this rom. It booted fine and on the just a sec screen (right after the language selection on aosp/gpe), I did the four corner tap to bypass setup, enabled dev options, then had it connected to my laptop collecting a logcat for when it rebooted to see if it could show someone who knows far more about android than I do what could be causing trouble. The only problem this time is it never did. Almost like taking a car into the mechanic and somehow it knows and doesn't misbehave.... In fact, I feel asleep for a short time and when I woke up again, the command prompt never changed indicating that it ran the whole time without a reboot. At that time, I powered off and called it a night. Is it possible for a partition to become corrupted causing this?

bb1981 said:
I apologize if the last reply was short and possibly coming across snippy...I was at work and didn't have longer to reply...I think I may have made some very sight progress but the phone still knows nothing about itself once booted. I flashed twrp then wiped system, data, cache and dalvik then proceeded to flash unsense 6 and the 4.4.4 insecure kernel which is recommended by the developer for this rom. It booted fine and on the just a sec screen (right after the language selection on aosp/gpe), I did the four corner tap to bypass setup, enabled dev options, then had it connected to my laptop collecting a logcat for when it rebooted to see if it could show someone who knows far more about android than I do what could be causing trouble. The only problem this time is it never did. Almost like taking a car into the mechanic and somehow it knows and doesn't misbehave.... In fact, I feel asleep for a short time and when I woke up again, the command prompt never changed indicating that it ran the whole time without a reboot. At that time, I powered off and called it a night. Is it possible for a partition to become corrupted causing this?
Click to expand...
Click to collapse
Partitions can get corrupted but as far as I'm aware the only way to fix it is with soff I'm not positive because there is an option in twrp to repair partitions also you may be able to use that without soff.

_)(_(45466_!!$$%[¥|[]®]«¥°]<<° xda app...why do I not have permission to post? [/rant]
I picked up a replacement gunmetal gray m8 on swappa and am considering putting the red one up on the boneyard there to give someone a chance to poke around with it. I was wondering if a partition that twrp doesn't have in the repair section like the one for radio/modem for instance could get damaged. The RUU should take care off any problems like that though so I'm officially stumped and haven't really had any extra time to do any troubleshooting.

bb1981 said:
_)(_(45466_!!$$%[¥|[]®]«¥°]
Weird quotes too...the app doesn't like you lol. If you are replacing it can you send me the broken one so I can better try to support this device?
Edit...I know you probably will get pm requests for that too. I'm all about unbricking HTC phones and I'm sure there's enough people around here to back that up between my ruu support and all.
Click to expand...
Click to collapse

dottat said:
bb1981 said:
_)(_(45466_!!$$%[¥|[]®]«¥°]
Weird quotes too...the app doesn't like you lol. If you are replacing it can you send me the broken one so I can better try to support this device?
Edit...I know you probably will get pm requests for that too. I'm all about unbricking HTC phones and I'm sure there's enough people around here to back that up between my ruu support and all.
Click to expand...
Click to collapse
I finally got wise and did a copy and paste after something like 5 times saying I didn't have permission lol....that sounds like a great idea. More (and better) support and understanding is always good.
Click to expand...
Click to collapse