Database Info

Help: Wipe+Root

Hi all.
How can I wipe my Nexus 5 so it is a plain Kit Kat 4.4.2 (like the day I received it) and just root it? it's currently in 4.4.2 and rooted, but with a lot of stuf in it too. My main concern is how to wipe once it's rooted, and how to reroot.
For those who like to read, a little more info:
I have a Nexus 5 which received 2 days ago. I come from an iPhone 5S, so... pretty newbie...
I unlocked the bootloader and rooted the device after unboxing, and have been using it since. Problems are:
1. I just found out about CWM and its capabilities, and I intend to use the backups a lot.
2. I kind of ****ed up with a couple of apps I regret installing.
3. After a backup I just did today, it asked to whether or not fix the recovery (or something like that). Selected YES, nothing happened. It then asked to fix the root... said YES and screwed it completely. I had to put SuperSu in the phone as a ZIP and manually install it again to recover my root access. It kind of looks "dirty" now, lol.
Anyways, I'd like to make a whole device backup from CWM with Kit Kat out of the box, no extra apps installed. Just rooted. Then install all my stuff, sync contacts and so on, and make another backup.
That's why I want to erase the device and have it all clean (just rooted).
Thanks!

Start here http://forum.xda-developers.com/showthread.php?p=47156064
Then go here
http://forum.xda-developers.com/showthread.php?p=47025283

jd1639 said:
Start here http://forum.xda-developers.com/showthread.php?p=47156064
Then go here
http://forum.xda-developers.com/showthread.php?p=47025283
Click to expand...
Click to collapse
Thanks! Can link 2 be replaced with just running CF-Auto-Root? That's what I used the first time and worked great.

rwed said:
Thanks! Can link 2 be replaced with just running CF-Auto-Root? That's what I used the first time and worked great.
Click to expand...
Click to collapse
It can, but I'd recommend you do it per the link.

jd1639 said:
It can, but I'd recommend you do it per the link.
Click to expand...
Click to collapse
Mmm. OK. And why? (Just curious at this point)

rwed said:
Mmm. OK. And why? (Just curious at this point)
Click to expand...
Click to collapse
Because the 2nd method furnishes you with knowledge and experience to help you understand and learn things that cf auto root "automates" for you. Using our recommended method, you will have a head start in knowing how to do things you may need to do to recover your device from various scenarios.
...for example, had you used that method last time - applying logic and knowledge, you may not have created this thread
Sent from my Nexus 5 using Tapatalk

rootSU said:
...for example, had you used that method last time - applying logic and knowledge, you may not have created this thread
Click to expand...
Click to collapse
lol OK. Thanks guys.
I come from iOS after several years. Please bear that in mind.

We're just offering you the benefit of our collective experience. Some of us have been doing this for years so please understand - we're not giving you grief. We have your best interests in mind
Sent from my Nexus 5 using Tapatalk

rootSU said:
We're just offering you the benefit of our collective experience. Some of us have been doing this for years so please understand - we're not giving you grief. We have your best interests in mind
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Oh please, I know. I was just hiding my ignorance under the iOS carpet.
Will give a read to both links tomorrow. Will definitely do link1 on friday if I find the time, and will then consider either doing link2 or going the CF-Auto-Root way.
I'll let you know how this all ends.
Again, thanks!

Update:
Followed steps in link1. Everything went fine.
Gave a deep read to link2. Found it understandable and easy to do and follow, but decided to go the CF-Auto-Root way just because I had done it before and worked nicely...
Everything OK. Something weird happened -again- though. After the clean restore and root, I installed CWM and proceeded to make a backup of the plain system. After it, it asked to fix root again. I had previously said YES, which lead to a broken root, so I said NO this time. Same thing happened!! I lost root and had to manually install SuperSu 1.93 from ZIP in CWM... Why does this happen?
Anyways, I have another question. If one day I decide to restore from this backup I just made, will it be exactly as doing a complete restore following link1?
Thanks!
jd1639 said:
Start here http://forum.xda-developers.com/showthread.php?p=47156064
Then go here
http://forum.xda-developers.com/showthread.php?p=47025283
Click to expand...
Click to collapse
rootSU said:
Because the 2nd method furnishes you with knowledge and experience to help you understand and learn things that cf auto root "automates" for you. Using our recommended method, you will have a head start in knowing how to do things you may need to do to recover your device from various scenarios.
...for example, had you used that method last time - applying logic and knowledge, you may not have created this thread
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse

Stop using cwm... use twrp or philz which can turn the nag off.
Sent from my Nexus 5 using Tapatalk

rwed said:
Update:
Followed steps in link1. Everything went fine.
Gave a deep read to link2. Found it understandable and easy to do and follow, but decided to go the CF-Auto-Root way just because I had done it before and worked nicely...
Everything OK. Something weird happened -again- though. After the clean restore and root, I installed CWM and proceeded to make a backup of the plain system. After it, it asked to fix root again. I had previously said YES, which lead to a broken root, so I said NO this time. Same thing happened!! I lost root and had to manually install SuperSu 1.93 from ZIP in CWM... Why does this happen?
Anyways, I have another question. If one day I decide to restore from this backup I just made, will it be exactly as doing a complete restore following link1?
Thanks!
Click to expand...
Click to collapse
Flash this in cwm http://d-h.st/YpG. It'll put twrp on

Oh damn it... Really? OK, a couple of quick questions:
1. Did reinstalling SuperSu leave junk in the file system?
2. Will flashing TWRP leave anything either?
My OCD would probably make me restore again if the answer to any of those questions is yes.
rootSU said:
Stop using cwm... use twrp or philz which can turn the nag off.
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
jd1639 said:
Flash this in cwm http://d-h.st/YpG. It'll put twrp on
Click to expand...
Click to collapse

rwed said:
Oh damn it... Really? OK, a couple of quick questions:
1. Did reinstalling SuperSu leave junk in the file system?
2. Will flashing TWRP leave anything either?
My OCD would probably make me restore again if the answer to any of those questions is yes.
Click to expand...
Click to collapse
No to both your questions.

jd1639 said:
No to both your questions.
Click to expand...
Click to collapse
Thank you very much!
I just saw that TWRP is in version 5.7.3 in the Play Store. Any reason why you linked to 2.6.3.4? I'm asking because I guess it'll update as soon as I boot. Right?

rwed said:
Thank you very much!
I just saw that TWRP is in version 5.7.3 in the Play Store. Any reason why you linked to 2.6.3.4? I'm asking because I guess it'll update as soon as I boot. Right?
Click to expand...
Click to collapse
Not for the nexus 5. I think you're looking at cwm.

jd1639 said:
Not for the nexus 5. I think you're looking at cwm.
Click to expand...
Click to collapse
I saw it here: https://play.google.com/store/apps/details?id=com.jmz.soft.twrpmanager

rwed said:
I saw it here: https://play.google.com/store/apps/details?id=com.jmz.soft.twrpmanager
Click to expand...
Click to collapse
I just looked at it. I'm not sure what that is. The file I linked you to is the latest image from goo.im which is the official twrp depository.

jd1639 said:
I just looked at it. I'm not sure what that is. The file I linked you to is the latest image from goo.im which is the official twrp depository.
Click to expand...
Click to collapse
I'll just install your file, specially if you can't even tell what that thing I linked is. Thank you jd. :good:

rwed said:
Thank you very much!
I just saw that TWRP is in version 5.7.3 in the Play Store. Any reason why you linked to 2.6.3.4? I'm asking because I guess it'll update as soon as I boot. Right?
Click to expand...
Click to collapse
That's the twrp manager. Different things. One is an app and one is a recovery
Sent from my Nexus 5

[Q] I made a stupid mistake. I formated data and now I don't have any OS.

Hello, today I decided to unlock, root my phone. I also decided to install new rom. And everything went fine but befor installing I insted Factory reset I formated data. I don't know what I was thinking. It may be that I was using TWRP Touch for a first time. Can somebody help me get back to at least to Stock if it is possible. Is it possible to connect phone in TWRP to transfer data from computer to it?

BombasMirko said:
Hello, today I decided to unlock, root my phone. I also decided to install new rom. And everything went fine but befor installing I insted Factory reset I formated data. I don't know what I was thinking. It may be that I was using TWRP Touch for a first time. Can somebody help me get back to at least to Stock if it is possible. Is it possible to connect phone in TWRP to transfer data from computer to it?
Click to expand...
Click to collapse
Does mount usb work on twrp? If so you can copy a rom zip to your device. If not than use search here on xda or google you probably need to unroot again and restore with a factory image.

ttl1982 said:
Does mount usb work on twrp? If so you can copy a rom zip to your device. If not than use search here on xda or google you probably need to unroot again and restore with a factory image.
Click to expand...
Click to collapse
Moutning doesn't work.
I found this: http://forum.xda-developers.com/google-nexus-5/general/tutorial-how-to-flash-factory-image-t2513701
Will this work for me? I was never in this situation before.

You can either use adb to push a ROM zip to your phone, or just flash the stock images to your phone. http://forum.xda-developers.com/showthread.php?t=2513701
[TUTORIAL] How to flash a factory image | Return to stock | Unroot/SAVE your Nexus 5
Sent from my Nexus 5

Follow this tutorial right here. It'll completely fix EVERYTHING that you are describing.
http://forum.xda-developers.com/google-nexus-5/general/tutorial-how-to-flash-factory-image-t2513701
You'll need the Android SDK for that tutorial, also. Also a brain.
What OS is your PC on?

pyrogoggles said:
Follow this tutorial right here. It'll completely fix EVERYTHING that you are describing.
http://forum.xda-developers.com/google-nexus-5/general/tutorial-how-to-flash-factory-image-t2513701
You'll need the Android SDK for that tutorial, also. Also a brain.
What OS is your PC on?
Click to expand...
Click to collapse
Either Xubuntu or Windows 8.1. What is prefered? Xubuntu probably because you don't need drivers.

BombasMirko said:
Either Xubuntu or Windows 8.1. What is prefered? Xubuntu probably because you don't need drivers.
Click to expand...
Click to collapse
You should use Windows 8.1 for this tutorial. It's aimed towards Windows and the command prompt. Followed word by word, that is, for Windows.
Hope this tutorial fixes it!

pyrogoggles said:
You should use Windows 8.1 for this tutorial. It's aimed towards Windows and the command prompt. Followed word by word, that is, for Windows.
Hope this tutorial fixes it!
Click to expand...
Click to collapse
It wen't just fine. Thank you guys. I was really scared that it will be like long, risky and difficult process. Thanks again.

BombasMirko said:
It wen't just fine. Thank you guys. I was really scared that it will be like long, risky and difficult process. Thanks again.
Click to expand...
Click to collapse
Virtually every member here has gotten themselves into a situation that they weren't sure they would be able to fix. It happens to all of us. It's Android initiation

BombasMirko said:
It wen't just fine. Thank you guys. I was really scared that it will be like long, risky and difficult process. Thanks again.
Click to expand...
Click to collapse
Lol its happened to me so many times that I end up doing it now on purpose just to clean the phone 100% before flashing a new ROM.
Sent from my Nexus 5 using Tapatalk

justinisloco said:
Lol its happened to me so many times that I end up doing it now on purpose just to clean the phone 100% before flashing a new ROM.
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Lol I thought I was the only one who does this
Sent from my HAMMERHEAD

Aerowinder said:
Virtually every member here has gotten themselves into a situation that they weren't sure they would be able to fix. It happens to all of us. It's Android initiation
Click to expand...
Click to collapse
Yeah and this is actually the best school to learn new things. Now I know that it is not that bad at all

[Q] Phone hard bricked after unlocking bootloader

So it seems I've really put myself into a bad spot, here.
I recently rooted my phone (Verizon S3) using towelroot, which seemed to work exceedingly well, so I decided to try to make a NANDroid backup using ClockworkMod. I installed ROM Manager, set that up, and chose the "restart in Clockwork recovery mode option", which didn't work. I soon realized I forgot to unlock my bootloader so, at the recommendation of a few sites, used EZ-Unlock to try to do that. The app reported that it was successful, so I tried restarting my phone in Clockwork recovery mode again. To my utter horror, my phone did not turn on, and has not turned on since.
When I say that it doesn't turn on, I mean that it gives me no audio, vibrational, or visual feedback, almost like there's no battery in the phone. I've pulled the battery and also attempted to do the fix outlined in a video, but to no avail. (I would post the link if the forum allowed me to. The title of the video is "Unbrick hard bricked Verizon Galaxy S3 running 4.3 Jelly Bean")
Feel free to scold me all you like for my irresponsibility and stupidity, it's probably deserved. Any help will be hugely appreciated, though! Thank you so much!
Edit: I guess I should mention that this is my first time doing this sort of thing to an Android device. However, I do like to think I "know my way around", as they say. (although I guess not enough to avoid messing things up!)

Velovix said:
So it seems I've really put myself into a bad spot, here.
I recently rooted my phone (Verizon S3) using towelroot, which seemed to work exceedingly well, so I decided to try to make a NANDroid backup using ClockworkMod. I installed ROM Manager, set that up, and chose the "restart in Clockwork recovery mode option", which didn't work. I soon realized I forgot to unlock my bootloader so, at the recommendation of a few sites, used EZ-Unlock to try to do that. The app reported that it was successful, so I tried restarting my phone in Clockwork recovery mode again. To my utter horror, my phone did not turn on, and has not turned on since.
When I say that it doesn't turn on, I mean that it gives me no audio, vibrational, or visual feedback, almost like there's no battery in the phone. I've pulled the battery and also attempted to do the fix outlined in a video, but to no avail. (I would post the link if the forum allowed me to. The title of the video is "Unbrick hard bricked Verizon Galaxy S3 running 4.3 Jelly Bean")
Feel free to scold me all you like for my irresponsibility and stupidity, it's probably deserved. Any help will be hugely appreciated, though! Thank you so much!
Edit: I guess I should mention that this is my first time doing this sort of thing to an Android device. However, I do like to think I "know my way around", as they say. (although I guess not enough to avoid messing things up!)
Click to expand...
Click to collapse
You need to report your post so it can be moved to the Verizon s3 forums where you can get help for your problem.

Darke5tShad0w said:
You need to report your post so it can be moved to the Verizon s3 forums where you can get help for your problem.
Click to expand...
Click to collapse
Oh, my mistake. I'll do that right away. Thank you!

Velovix said:
Oh, my mistake. I'll do that right away. Thank you!
Click to expand...
Click to collapse
No problems. This is the forum for the International version and we don't have locked bootloaders so you will have more chance in there than you will here.

can you get the phone to go in to download mode? that power+home+vol down

Timothy08 said:
can you get the phone to go in to download mode? that power+home+vol down
Click to expand...
Click to collapse
No, unfortunately, I cannot. I hope I'm not already out of luck.

Velovix said:
No, unfortunately, I cannot. I hope I'm not already out of luck.
Click to expand...
Click to collapse
Was your phone on android 4.3 before you tried to unlock bootloader? If so, that isn't good.

sjpritch25 said:
Was your phone on android 4.3 before you tried to unlock bootloader? If so, that isn't good.
Click to expand...
Click to collapse
Uhh, yes, it was.. Any suggestions?

Velovix said:
Uhh, yes, it was.. Any suggestions?
Click to expand...
Click to collapse
Maybe try looking at the unbrick thread in the q&a?

Velovix said:
Uhh, yes, it was.. Any suggestions?
Click to expand...
Click to collapse
Do what the guy above suggested. Oh just so you know when you are on 4.3 you can not unlock your bootloader. Only root. Also once on 4.3 you can not downgrade to any earlier firmware versions. You can thank Verizon for that.
Sent from my SCH-I535 using Tapatalk

YevOmega said:
Maybe try looking at the unbrick thread in the q&a?
Click to expand...
Click to collapse
If you're referring to "[GUIDE] Debrick your bricked SCH-I535! [BOOTLOADER/HARDBRICK]", I have tried that a few times. I guess I could give it a few more shots if that's my only option.

Sandman-007 said:
Do what the guy above suggested. Oh just so you know when you are on 4.3 you can not unlock your bootloader. Only root. Also once on 4.3 you can not downgrade to any earlier firmware versions. You can thank Verizon for that.
Sent from my SCH-I535 using Tapatalk
Click to expand...
Click to collapse
That's awful. I guess I was looking at a guide for a non-Verzion phone. Thank you for the information, though.

So, if I understand my situation, I guess the question now is: How can I lock my bootloader back up while it's hardbricked, correct?

Velovix said:
So, if I understand my situation, I guess the question now is: How can I lock my bootloader back up while it's hardbricked, correct?
Click to expand...
Click to collapse
No. Your only focus is on getting the phone to boot back up. The only method that we have to do so is the bootloader/hardbrick thread by SpryroDazee posted at the top of our Q/A section.

SlimSnoopOS said:
No. Your only focus is on getting the phone to boot back up. The only method that we have to do so is the bootloader/hardbrick thread by SpryroDazee posted at the top of our Q/A section.
Click to expand...
Click to collapse
Alright, I'll see what I can do. Thanks for the help!

Velovix said:
Alright, I'll see what I can do. Thanks for the help!
Click to expand...
Click to collapse
http://mobiletechvideos.mybigcommerce.com/samsung-galaxy-s-iii-s3-bootloader-downgrade-service/
This might help. Try mobile tech videos. they can Jtag and downgrade for you.

IMEI Unknown

Hi guys! I've looked all around and tried the fixes that people recommended, which is basically going back to stock.
So this is what happened to my brother's phone:
Was using the phone and all a sudden the phone freezes (He was on Android L) and he rebooted it. After rebooting, the phone went into bootloop. He downloaded some program that supposedly fixes softbrick and bootloop (by flashing stock ROM) Nexus Root Toolkit v1.8.7.
The phone was fixed.. Kinda.. He couldn't get any cell signal. Turns out his baseband and IMEI read unknown. He has the box the phone came in, to we know the physical IMEI number.
Is there a fix for this? I've tried this thread http://forum.xda-developers.com/google-nexus-5/help/lost-imei-please-help-t2529103 but it didn't work.
Any ideas?

You_got_owned123 said:
Hi guys! I've looked all around and tried the fixes that people recommended, which is basically going back to stock.
So this is what happened to my brother's phone:
Was using the phone and all a sudden the phone freezes (He was on Android L) and he rebooted it. After rebooting, the phone went into bootloop. He downloaded some program that supposedly fixes softbrick and bootloop (by flashing stock ROM) Nexus Root Toolkit v1.8.7.
The phone was fixed.. Kinda.. He couldn't get any cell signal. Turns out his baseband and IMEI read unknown. He has the box the phone came in, to we know the physical IMEI number.
Is there a fix for this? I've tried this thread http://forum.xda-developers.com/google-nexus-5/help/lost-imei-please-help-t2529103 but it didn't work.
Any ideas?
Click to expand...
Click to collapse
Try to run the "fastboot earease cache" command in fastboot. Read the sticky thread in the general forum.

bitdomo said:
Try to run the "fastboot earease cache" command in fastboot. Read the sticky thread in the general forum.
Click to expand...
Click to collapse
Sad to say, I've already tried that.. Even tried to flash stock cache image.

You_got_owned123 said:
Sad to say, I've already tried that.. Even tried to flash stock cache image.
Click to expand...
Click to collapse
Also you said the baseband is unknown. Have you tried to reflash the radio/modem image?

bitdomo said:
Also you said the baseband is unknown. Have you tried to reflash the radio/modem image?
Click to expand...
Click to collapse
I've flashed radio, but modem I have not. I'll have to try that!

You_got_owned123 said:
I've flashed radio, but modem I have not. I'll have to try that!
Click to expand...
Click to collapse
It's the same thing!
restore fully to stock using LG Flashtool. See if that fixes...

rootSU said:
It's the same thing!
restore fully to stock using LG Flashtool. See if that fixes...
Click to expand...
Click to collapse
Can you by any chance give me a link? Did a quick Google search and didn't find anything official.

You_got_owned123 said:
Can you by any chance give me a link? Did a quick Google search and didn't find anything official.
Click to expand...
Click to collapse
See my signature
Sent from my Nexus 5 using Tapatalk

You_got_owned123 said:
Can you by any chance give me a link? Did a quick Google search and didn't find anything official.
Click to expand...
Click to collapse
Or check my signature.
Someone calls it modem and someone calls it radio.

rootSU said:
See my signature
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Hey! I was reading on a thread where you helped someone fix their phone!
Did a stock flash do it for them? I got the factory images and ran the flash-all scrip and still nothing.

You_got_owned123 said:
Hey! I was reading on a thread where you helped someone fix their phone!
Did a stock flash do it for them? I got the factory images and ran the flash-all scrip and still nothing.
Click to expand...
Click to collapse
I help a lot of people. I cannot pick out individual instances.
Use LG flashtool
Sent from my Nexus 5 using Tapatalk

You_got_owned123 said:
Hey! I was reading on a thread where you helped someone fix their phone!
Did a stock flash do it for them? I got the factory images and ran the flash-all scrip and still nothing.
Click to expand...
Click to collapse
Also check if wifi mac address is changing after each reboot. Corrupted persist partition can cause problems like that and also other things like crasing apps
Check out my thread about it http://forum.xda-developers.com/google-nexus-5/general/guide-to-fix-persist-partition-t2821576. It worths a try. If it does not help then you have to buy a new motherboard or claim your warranty if you have any.

bitdomo said:
Also check if wifi mac address is changing after each reboot. Corrupted persist partition can cause problems like that and also other things like crasing apps
Check out my thread about it http://forum.xda-developers.com/google-nexus-5/general/guide-to-fix-persist-partition-t2821576. It worths a try. If it does not help then you have to buy a new motherboard or claim your warranty if you have any.
Click to expand...
Click to collapse
Perist will not mount. I hasn't seen factory image for persist partition.

You_got_owned123 said:
Perist will not mount. I hasn't seen factory image for persist partition.
Click to expand...
Click to collapse
Because there arent any. It is unique for every device like efs.

bitdomo said:
Because there arent any. It is unique for every device like efs.
Click to expand...
Click to collapse
So is that a problem?

You_got_owned123 said:
So is that a problem?
Click to expand...
Click to collapse
If you see that /persist cannot be mounted then it could be.

bitdomo said:
If you see that /persist cannot be mounted then it could be.
Click to expand...
Click to collapse
I tried wiping cache and then it gave me a bunch or partitions that were errors. With persist being one of them. After a while, I was able to clear cache with no errors.

You_got_owned123 said:
I tried wiping cache and then it gave me a bunch or partitions that were errors. With persist being one of them. After a while, I was able to clear cache with no errors.
Click to expand...
Click to collapse
Then it is up to you what are you going to do with the persist partition. You will lose nothing but time by formating the persist partition. If it not fix your problem then you have to buy a new motherboard for the phone to make phone calls either way because you dont have any efs backup.

bitdomo said:
Then it is up to you what are you going to do with the persist partition. You will lose nothing but time by formating the persist partition. If it not fix your problem then you have to buy a new motherboard for the phone to make phone calls either way because you dont have any efs backup.
Click to expand...
Click to collapse
Persist was the problem. Fixed that partition and was golden. Thank you so much all of you. Took 3 hours. So much Google.

You_got_owned123 said:
Persist was the problem. Fixed that partition and was golden. Thank you so much all of you. Took 3 hours. So much Google.
Click to expand...
Click to collapse
It would be nice if you would post how did you solve your issue. Some will learn and it could help others having the same issue.

nexus 5 ROM corruption

My phone randomly shut off and then I when I turn it back on. the infinite boot logo appear. I installed clockworld. tried to reformat everything and reinstall stock image and still nothing.

Need more info. What does still nothing mean? Flashing the stock images failed?
Sent from my Nexus 5 using Tapatalk

See here for a possible (probable) solution
http://forum.xda-developers.com/google-nexus-5/help/nexus-5-stuck-boot-loop-lollipop-t3098632

ldubs said:
Need more info. What does still nothing mean? Flashing the stock images failed?
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Sorry I should of added more information.
I followed the guide that google gives to flash the ROM using the original stock image cant post link since I am a new member
it failed still having the endless boot animation.,
also my problem is I didnt had usd debugging enabled. So its make hard to use some of the ADB Commands

Google's guide (flashing the zip file) often fails, not sure why. Look in my guide for a better way to do this. Though if you have a persist partition corrupted, flashing Lollipop will not help. You will still not be able to boot. See my guide. Good luck!

eross said:
Google's guide (flashing the zip file) often fails, not sure why. Look in my guide for a better way to do this. Though if you have a persist partition corrupted, flashing Lollipop will not help. You will still not be able to boot. See my guide. Good luck!
Click to expand...
Click to collapse
(when I do ADB devices. Dosent display my device. I was able to do everything from the guide I am at the part where I have to fix the partition persit) NVM ABOUT THAT

eross said:
See here for a possible (probable) solution
http://forum.xda-developers.com/google-nexus-5/help/nexus-5-stuck-boot-loop-lollipop-t3098632
Click to expand...
Click to collapse
it worked thanks!!! I was about to send it to LG

darthzash said:
it worked thanks!!! I was about to send it to LG
Click to expand...
Click to collapse
Great!