Verizon Pixel stuck in bootloop. Please help. - Google Pixel Questions & Answers

Hey guys. I really messed up. I was running 7.1 from launch, and have had the systemless root basically since the beginning. I attempted to mount /system as /r/rw (for the stupidest reason) and my phone booted into a "no command" bootloop. Is there any hope for me? I can access recovery (I think). I can get into adb and fastboot and get the device recognized by the computer.
I will donate, buy coffee, anything for some love. Thank you so much for your time!

junkshot9112 said:
Hey guys. I really messed up. I was running 7.1 from launch, and have had the systemless root basically since the beginning. I attempted to mount /system as /r/rw (for the stupidest reason) and my phone booted into a "no command" bootloop. Is there any hope for me? I can access recovery (I think). I can get into adb and fastboot and get the device recognized by the computer.
I will donate, buy coffee, anything for some love. Thank you so much for your time!
Click to expand...
Click to collapse
Well if you have an unlocked bootloader you can simple flash the stock images.

NBreunig3 said:
Well if you have an unlocked bootloader you can simple flash the stock images.
Click to expand...
Click to collapse
Thank you so much for the reply. I think I could even do a factory reset from recovery, but I'm not sure. I'm pretty new at this. I was really hoping there may be a way I could backup my data first, or even fix the issue, as I'm pretty sure I know what happened. I think my permissions are set wrong, but I could be entirely wrong. I found this guide that sounds like my issue, but it is for a different device. I've tried adapting it to the best of my ability, but I can't get the phone in ADB mode from recovery. http://www.gizbeat.com/2103/how-to-change-file-permissions-through-adb/

Wouldn't hurt to try knowing you can also just flash stock images.

NBreunig3 said:
Wouldn't hurt to try knowing you can also just flash stock images.
Click to expand...
Click to collapse
Can you point me in the direction of someone who may be able to help me do just that? I've tried just about all I can think to do. I really am new at this and feel I am in over my head. I really appreciate any and all help and would gladly donate to this site or any individual user who is able to help me solve my problems (I hope it isn't against your rules to say things like that).
Thanks again.

This site straight from Google has all the files and instructions. https://developers.google.com/android/images
Follow directions but don't lock bootloader.

NBreunig3 said:
This site straight from Google has all the files and instructions. https://developers.google.com/android/images
Follow directions but don't lock bootloader.
Click to expand...
Click to collapse
Sorry, I was unclear, that was my fault. I believe I know how to flash stock images. That is something I have done since the OG Droid. I was asking if you may know anyone who may be able to help me attempt to backup my data, reset my permissions, or even get the phone into ADB mode before I resort to losing everything. Again, apologies for being unclear.

No worries. I would just look online and possibly post another thread here or just wait for replies.

Flash the stock image but remove the -w from the script to keep from losing data. Search around here for instructions. It's been described a zillion times.

cntryby429 said:
Flash the stock image but remove the -w from the script to keep from losing data. Search around here for instructions. It's been described a zillion times.
Click to expand...
Click to collapse
Is this what is referred to as a "dirty flash"?

junkshot9112 said:
Is this what is referred to as a "dirty flash"?
Click to expand...
Click to collapse
I suppose one could think of it that way but it really isn't. Everything other than data will be wiped and flashed. It'll all be new with the exception of your data partition. Removing the w allows you to keep all your apps and their settings in tact. The rest will all be new though. It can't hurt to try it. If it doesn't fix your problem (which it should) you can always run it again and wipe data along with everything else.

robocuff said:
I suppose one could think of it that way but it really isn't. Everything other than data will be wiped and flashed. It'll all be new with the exception of your data partition. Removing the w allows you to keep all your apps and their settings in tact. The rest will all be new though. It can't hurt to try it. If it doesn't fix your problem (which it should) you can always run it again and wipe data along with everything else.
Click to expand...
Click to collapse
I was successful. Thank you so much. What can I do for you to show thanks?

junkshot9112 said:
Is this what is referred to as a "dirty flash"?
Click to expand...
Click to collapse
Yes. But in reality it is not much different than taking an OTA. That never wipes data. I only clean flash if I am having issues after a dirty flash and I can't remember the last time that happened.
Sent from my Pixel XL using XDA Labs

junkshot9112 said:
I was successful. Thank you so much. What can I do for you to show thanks?
Click to expand...
Click to collapse
Your thanks is more than enough.?

Related

Issues with Video on Cory's Unofficial Cyanogen

Sorry my first post is a plea for help, but here we are.
I flashed the latest (2013-5-10) version of ..Cory..'s unofficial Cyanogenmod this morning and I'm having issues with video, including my camera viewfinder. Both Youtube and my camera lag to the point of uselessness, though audio on videos plays just fine.
Also sometimes my desktop icons stick around when I pull up the recent apps or notification drawer.
Has anyone else experienced either one of these? I'd post this in the thread for the ROM, but I need to hit my post count first.
And lest I sound ungrateful, big thanks to ..Cory.. for keeping things moving forward while the official version is on hiatus!
greategress said:
Sorry my first post is a plea for help, but here we are.
I flashed the latest (2013-5-10) version of ..Cory..'s unofficial Cyanogenmod this morning and I'm having issues with video, including my camera viewfinder. Both Youtube and my camera lag to the point of uselessness, though audio on videos plays just fine.
Also sometimes my desktop icons stick around when I pull up the recent apps or notification drawer.
Has anyone else experienced either one of these? I'd post this in the thread for the ROM, but I need to hit my post count first.
And lest I sound ungrateful, big thanks to ..Cory.. for keeping things moving forward while the official version is on hiatus!
Click to expand...
Click to collapse
So I tried disabling HW in dev settings, and that seems to work for now. Still curious if anyone else has run into this issue.
greategress said:
So I tried disabling HW in dev settings, and that seems to work for now. Still curious if anyone else has run into this issue.
Click to expand...
Click to collapse
Not that I could see on my end. But I did do a factory reset in TWRP first before I flashed?
imutau said:
Not that I could see on my end. But I did do a factory reset in TWRP first before I flashed?
Click to expand...
Click to collapse
So did I, unfortunately. Might have to just try it again this weekend and see if that works. :fingers-crossed:
greategress said:
So did I, unfortunately. Might have to just try it again this weekend and see if that works. :fingers-crossed:
Click to expand...
Click to collapse
Check MD5 of your ROM, make sure it matches up if you haven't.
Also, If you haven't done so, try fastboot erase cache prior to wiping and flashing.
exad said:
Check MD5 of your ROM, make sure it matches up if you haven't.
Also, If you haven't done so, try fastboot erase cache prior to wiping and flashing.
Click to expand...
Click to collapse
Thanks for the advice, exad! I'll try to fastboot erase cache step this weekend. Didn't do it this time because I thought I didn't have to use fastboot now that I have S-OFF.
greategress said:
Thanks for the advice, exad! I'll try to fastboot erase cache step this weekend. Didn't do it this time because I thought I didn't have to use fastboot now that I have S-OFF.
Click to expand...
Click to collapse
That command clears the cache for fastboot and recovery, this will ensure that recovery is properly wiping your partitions so be sure to do it before wiping and flashing your rom.
exad said:
That command clears the cache for fastboot and recovery, this will ensure that recovery is properly wiping your partitions so be sure to do it before wiping and flashing your rom.
Click to expand...
Click to collapse
Do you know a decent guide that includes this step? None of the ones I used previously included this step. I get this is an ADB command, but I try to avoid using ADB directly as much as possible due to noobness. Not sure what state my phone has to be in to use the command, etc.
greategress said:
Do you know a decent guide that includes this step? None of the ones I used previously included this step. I get this is an ADB command, but I try to avoid using ADB directly as much as possible due to noobness. Not sure what state my phone has to be in to use the command, etc.
Click to expand...
Click to collapse
There are no guides because it's assumed that you are familiar with ADB and fastboot if you are on this forum.
fastboot and adb don't rely on states.
fastboot is a tool for pushing and pulling information/files to and from your phone while in bootloader
ADB is a tool that allows you to access your phone via a command line shell interface.
If this is confusing to you, why would you root your phone? And I'm not trying to be rude, this isn't an iphone jailbreak, rooting is COMPLETELY different and can be dangerous if you don't understand. Avoiding adb and fastboot does not make it any less dangerous either.
exad said:
There are no guides because it's assumed that you are familiar with ADB and fastboot if you are on this forum.
fastboot and adb don't rely on states.
fastboot is a tool for pushing and pulling information/files to and from your phone while in bootloader
ADB is a tool that allows you to access your phone via a command line shell interface.
If this is confusing to you, why would you root your phone? And I'm not trying to be rude, this isn't an iphone jailbreak, rooting is COMPLETELY different and can be dangerous if you don't understand. Avoiding adb and fastboot does not make it any less dangerous either.
Click to expand...
Click to collapse
I considered not asking for advice, but then I thought "Naw, he's already here. I'm sure he won't mind." My apologies for forcing you to deal with my inexperience.
I used the word "state" incorrectly, not remembering at the time it had a specific programming meaning. You still managed to answer my question, though, pointing out my phone needs to be in the bootloader. You also cleared up that fastboot is its own tool rather than just a command used in ADB. Thank you for both those things. I'll figure it out from here.
As for why I'd want to root my phone? Who wouldn't? I don't want to be stuck with whatever AT&T thinks is good enough. I'm sorry if I'm making this club less exclusive, but if people here are going to hack together all this great stuff and give it away for free, I'm going to take advantage of that.
greategress said:
I considered not asking for advice, but then I thought "Naw, he's already here. I'm sure he won't mind." My apologies for forcing you to deal with my inexperience.
I used the word "state" incorrectly, not remembering at the time it had a specific programming meaning. You still managed to answer my question, though, pointing out my phone needs to be in the bootloader. You also cleared up that fastboot is its own tool rather than just a command used in ADB. Thank you for both those things. I'll figure it out from here.
As for why I'd want to root my phone? Who wouldn't? I don't want to be stuck with whatever AT&T thinks is good enough. I'm sorry if I'm making this club less exclusive, but if people here are going to hack together all this great stuff and give it away for free, I'm going to take advantage of that.
Click to expand...
Click to collapse
You're misunderstanding, the exclusivity of this site makes no difference to me, I want everyone to be able to root and do cool things with their phones, hell, it's your phone, you bought it, own it, you should be able to do whatever you want with it. You didn't need me to tell you what fasboot and adb are. They're well documented tools with help manuals included. Even a quick google search would tell you everything you need to know about them and more.
You chose to ignore them and hope it won't affect you that you're not understanding what you're doing to your phone. You ask in here hoping for the quick and lazy way to accomplish your task without taking the time to learn what you're doing. I love helping people that's why I'm here posting every day. but you're taking advantage of my good nature and not trying to help yourself by reading, learning and understanding what you're doing.
I wish you luck and I don't want to discourage you for asking for help here when you need it, but please take the time to help yourself first.
Same issue
I have the same issue with Youtube in landscape mode. I've noticed others have run into it as well.
exad said:
You're misunderstanding, the exclusivity of this site makes no difference to me, I want everyone to be able to root and do cool things with their phones, hell, it's your phone, you bought it, own it, you should be able to do whatever you want with it. You didn't need me to tell you what fasboot and adb are. They're well documented tools with help manuals included. Even a quick google search would tell you everything you need to know about them and more.
You chose to ignore them and hope it won't affect you that you're not understanding what you're doing to your phone. You ask in here hoping for the quick and lazy way to accomplish your task without taking the time to learn what you're doing. I love helping people that's why I'm here posting every day. but you're taking advantage of my good nature and not trying to help yourself by reading, learning and understanding what you're doing.
I wish you luck and I don't want to discourage you for asking for help here when you need it, but please take the time to help yourself first.
Click to expand...
Click to collapse
*sigh* You're right. I'm sorry for getting snappy. Just not used to being the guy who doesn't know what he's doing, y'know?
Anyway, I sincerely appreciate the help, exad. And I doubly appreciate the reminder that I need to turn to Google before I come begging to you guys.
nlyang said:
I have the same issue with Youtube in landscape mode. I've noticed others have run into it as well.
Click to expand...
Click to collapse
Hmm. Heard anything about how to fix it?
greategress said:
Hmm. Heard anything about how to fix it?
Click to expand...
Click to collapse
Have you tried flashing a different kernel? Like jacob.b2 or oc-vm-linaro?
exad said:
Have you tried flashing a different kernel? Like jacob.b2 or oc-vm-linaro?
Click to expand...
Click to collapse
I actually just got done following your original advice about clearing the cache via fastboot. Did that, then re-flashed the ROM and everything seems to be working. Thanks again for the help (and tough love )!
greategress said:
I actually just got done following your original advice about clearing the cache via fastboot. Did that, then re-flashed the ROM and everything seems to be working. Thanks again for the help (and tough love )!
Click to expand...
Click to collapse
Anytime friend!
the only thing that worked for me...
greategress said:
Hmm. Heard anything about how to fix it?
Click to expand...
Click to collapse
i tried erasing the cache via fastboot before the wipe+flash, but unfortunately I still had the issue. the only temp fix that works for me so far is disabling HW overlays in the developer options.
You could also try another kernel.
Sent from my One X using xda app-developers app
exad said:
You could also try another kernel.
Sent from my One X using xda app-developers app
Click to expand...
Click to collapse
Any kernel you'd recommend over the others? You mentioned the jacob.b2 and oc-vm-linaro before. Like one more than the other?

[Q] How do I get an Android L developer's preview?

Hi, I read that anyone with a developer's account can access the developers' preview build of Android L, that was supposed to be available today, I have a developer's account (to upload apps to the market) but I don't see any build of android L, is this the required account? or is there any other type of account required? thanks!
saman0suke1 said:
Hi, I read that anyone with a developer's account can access the developers' preview build of Android L, that was supposed to be available today, I have a developer's account (to upload apps to the market) but I don't see any build of android L, is this the required account? or is there any other type of account required? thanks!
Click to expand...
Click to collapse
it will be here when its released, as of yet it is not released
http://developer.android.com/index.html
keep refreshing the page like the rest of us
saman0suke1 said:
Hi, I read that anyone with a developer's account can access the developers' preview build of Android L, that was supposed to be available today, I have a developer's account (to upload apps to the market) but I don't see any build of android L, is this the required account? or is there any other type of account required? thanks!
Click to expand...
Click to collapse
I guess it'll be available in a few hours.
I guess they just haven't released it, yet.
Don't forget their different timezone.
Thank you all, maybe I'm getting too desperate I just wanted to confirm that my account is the right one, I'll be refreshing until it appears, thanks again!
EDIT: I believe being rooted would not be a problem at the moment of the installation, right? I know that I'll lose root after that, but as long as the actual installation does not give me problems, it's fine.
saman0suke1 said:
Thank you all, maybe I'm getting too desperate I just wanted to confirm that my account is the right one, I'll be refreshing until it appears, thanks again!
EDIT: I believe being rooted would not be a problem at the moment of the installation, right? I know that I'll lose root after that, but as long as the actual installation does not give me problems, it's fine.
Click to expand...
Click to collapse
Considering that the images will have to be flashed through fastboot, you'll probably lose root and everything else on data/system partitions (unless they don't wipe it, but I think it does).
saman0suke1 said:
Thank you all, maybe I'm getting too desperate I just wanted to confirm that my account is the right one, I'll be refreshing until it appears, thanks again!
EDIT: I believe being rooted would not be a problem at the moment of the installation, right? I know that I'll lose root after that, but as long as the actual installation does not give me problems, it's fine.
Click to expand...
Click to collapse
maybe it will be problem to root new androi L cause I've read somwhere that there is a lot of security updates and also samsung knox in new android so we will see if it will be able to root
saman0suke1 said:
Thank you all, maybe I'm getting too desperate I just wanted to confirm that my account is the right one, I'll be refreshing until it appears, thanks again!
EDIT: I believe being rooted would not be a problem at the moment of the installation, right? I know that I'll lose root after that, but as long as the actual installation does not give me problems, it's fine.
Click to expand...
Click to collapse
if it's a factory image it'll wipe the whole phone and root probably wont work until its updated to support L
MidnightDevil said:
Considering that the images will have to be flashed through fastboot, you'll probably lose root and everything else on data/system partitions (unless they don't wipe it, but I think it does).
Click to expand...
Click to collapse
That's fine, I believe that flash through fastboot does not include a total wipe including camera folder and all that right? never done it that way, better be prepared. Thanks!
saman0suke1 said:
That's fine, I believe that flash through fastboot does not include a total wipe including camera folder and all that right? never done it that way, better be prepared. Thanks!
Click to expand...
Click to collapse
As long as you don't flash the userdata.img, all /sdcard data will be fine. You don't have to flash userdata.img to bump android versions! System, boot would do just fine (and bootloader if they bump it as well)
Or you could just wait till a flashable zip is posted. Someone will have one up within hours of release.
Roxas598 said:
if it's a factory image it'll wipe the whole phone and root probably wont work until its updated to support L
Click to expand...
Click to collapse
Whole phone means photos, and any kind of files? I prefer to ask so I make a backup first :S , never done it this way, thanks!
saman0suke1 said:
Whole phone means photos, and any kind of files? I prefer to ask so I make a backup first :S , never done it this way, thanks!
Click to expand...
Click to collapse
Read my previous post.
saman0suke1 said:
Whole phone means photos, and any kind of files? I prefer to ask so I make a backup first :S , never done it this way, thanks!
Click to expand...
Click to collapse
Yep every single thing on the phone will be gone so backup everything you need
saman0suke1 said:
That's fine, I believe that flash through fastboot does not include a total wipe including camera folder and all that right? never done it that way, better be prepared. Thanks!
Click to expand...
Click to collapse
You'll lost everything... Photos,data file...
vin4yak said:
As long as you don't flash the userdata.img, all /sdcard data will be fine. You don't have to flash userdata.img to bump android versions! System, boot would do just fine (and bootloader if they bump it as well)
Click to expand...
Click to collapse
Unless they changed the folder structure like they did a few releases ago - if they did, best to do a clean install.
I'm backing up right now just in case.
Don't wanna mess with the installation script by flashing some things and not others (although there would be virtually no risk by flashing system and boot partition), but better safe than sorry, after all, we can just shove everything back when finished
Consider ir a backup routine, and you'll have an updated bk
jj14 said:
Unless they changed the folder structure like they did a few releases ago - if they did, best to do a clean install.
Click to expand...
Click to collapse
That's an entirely different scenario. Each and everyone of us would need to wipe clean if that happens but usually a system and boot flash would do just fine
The N5 has been my FIRST of many, many, many Android phones and even Windows Pocket PC phones that I haven't felt the need to unlock/root etc. Everything has just worked great on it and I have always been able to do everything I wanted to do from this phone. I have been so satisfied with the phone that it has kept me away from XDA for a while. Don't know if that is a good thing or bad, lol. I used to be on this site for hours every single day and now I feel like I am light years behind in rooting. HA!
L has me interested though and I am contemplating unlocking my bootloader for it which just becomes a PITA with losing your data and adding things back and all that great stuff that takes so much of your time. Then if things suck you have to flash back to something else and the never ending process continues. The N5 has gotten me so much time back in my life but I feel like it might demand some of my time back to it. Oh I hate this stuff!!!!
I think I'll make a backup, just in case, as someone said previously, I would prefer to make a clean installation if it's needed and use the image provided by Google.
Thanks!

[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

7.1.2 Upgrade Help

Hey guys. I think I, pretty familiar with what I need to do, but I haven't done it before. Currently I'm on the FEBRUARY security update (7.1.1) and have root. I am hoping to upgrade to 7.1.2 without losing any of my personal data and apps. I am weary to try flash fire, so could someone more experienced help me out?
I know I need to download the full OTA image and flash it and remove some -W flag, but I don't want to brick my device or lose my data, so I'll let you guys steer me. Thanks in advance, by the way!
P.S. I never fully installed TWRP.
Every time, I download the full factory image and flash via flash fire.
Everything is good, except losing twrp, but i do not mind. root still available
bush911 said:
Every time, I download the full factory image and flash via flash fire.
Everything is good, except losing twrp, but i do not mind. root still available
Click to expand...
Click to collapse
I have tried to stay away from flash fire because I know a couple buddies who soft-bricked by using it.
xxbilxx said:
Hey guys. I think I, pretty familiar with what I need to do, but I haven't done it before. Currently I'm on the FEBRUARY security update (7.1.1) and have root. I am hoping to upgrade to 7.1.2 without losing any of my personal data and apps. I am weary to try flash fire, so could someone more experienced help me out?
I know I need to download the full OTA image and flash it and remove some -W flag, but I don't want to brick my device or lose my data, so I'll let you guys steer me. Thanks in advance, by the way!
P.S. I never fully installed TWRP.
Click to expand...
Click to collapse
Second post in the thread below. Just get the 7.1.2 image.
https://forum.xda-developers.com/pixel/help/stupidly-bootloop-help-t3554242/page2
TonikJDK said:
Second post in the thread below. Just get the 7.1.2 image.
https://forum.xda-developers.com/pixel/help/stupidly-bootloop-help-t3554242/page2
Click to expand...
Click to collapse
I don't have to sideload the March security patch first?
xxbilxx said:
I don't have to sideload the March security patch first?
Click to expand...
Click to collapse
No you don't, because my way is flashing the whole 7.1.2 image, except data (reminder, remove the -w from flash-all.bat).
TonikJDK said:
No you don't, because my way is flashing the whole 7.1.2 image, except data (reminder, remove the -w from flash-all.bat).
Click to expand...
Click to collapse
Alright thanks dude. Which version of 7.1.2 should I get. I know some are made for different carriers but I'm in the U.S. and have a Google Store Pixel (non-XL) and using it on Verizon prepaid. I assume that should grab N2G47E, but I just want to be sure.
The other 7.1.2 is for Dutch Telecom? I just don't want to flash the wrong one on lol.
xxbilxx said:
Alright thanks dude. Which version of 7.1.2 should I get. I know some are made for different carriers but I'm in the U.S. and have a Google Store Pixel (non-XL) and using it on Verizon prepaid. I assume that should grab N2G47E, but I just want to be sure.
The other 7.1.2 is for Dutch Telecom? I just don't want to flash the wrong one on lol.
Click to expand...
Click to collapse
Correct, you want N2G47E.
TonikJDK said:
Correct, you want N2G47E.
Click to expand...
Click to collapse
After, I can just root like normal? I haven't had to do this yet, so that's why I'm asking all these questions. Sorry if I'm being nooby!
xxbilxx said:
After, I can just root like normal? I haven't had to do this yet, so that's why I'm asking all these questions. Sorry if I'm being nooby!
Click to expand...
Click to collapse
No problem at all. Second to the last post in the same thread I linked you to before. It all still works fine on 7.1.2. Did all of this myself yesterday afternoon.
Sideload did not work, used flash-all.bat deleted out the -w. When the device booted up it automatically wiped everything anyways
Download the OTA, Flash it from TWRP, reflash twrp and reboot
mikeprius said:
Sideload did not work, used flash-all.bat deleted out the -w. When the device booted up it automatically wiped everything anyways
Click to expand...
Click to collapse
Did you save the file after you edited it? Take a look at the flashall you used and see if the -w is still in there. Willing to bet it is. I've done this for every update since November. Never had a problem. The only thing I can think of that would cause your data to get wiped is that you didn't save the changes after you edited it.
robocuff said:
Did you save the file after you edited it? Take a look at the flashall you used and see if the -w is still in there. Willing to bet it is. I've done this for every update since November. Never had a problem. The only thing I can think of that would cause your data to get wiped is that you didn't save the changes after you edited it.
Click to expand...
Click to collapse
yeah saved it. There was only one section that had the w- and it was right before the update image. I can try it again at some point later on but that's what I did. I tried to sideload adb the OTA first which does not wipe data but kept getting an error saying device not found and emulator.
robocuff said:
Did you save the file after you edited it? Take a look at the flashall you used and see if the -w is still in there. Willing to bet it is. I've done this for every update since November. Never had a problem. The only thing I can think of that would cause your data to get wiped is that you didn't save the changes after you edited it.
Click to expand...
Click to collapse
Your instructions worked perfectly for me. I'm nor sure what setup the other guy had, but I did make sure I removed the -w like 20 times.
Juli112 said:
Download the OTA, Flash it from TWRP, reflash twrp and reboot
Click to expand...
Click to collapse
are you on the latest twrp rc2 or rc1?
Has anyone received the update ota on a stock google pixel XL for verizon. Mine keeps telling me I am current?

Tried to update, now stuck. Failed to mount data

Is someone able to help me? I messed up in a big way. Long story short, I cannot seem to get the DATA partition back on my phone. I did read the part about encryption but was so excited I (Yes, confirmed dummy) was thinking that it meant android encryption and not simply lockscreen/password.
My passcode is correct, but the data is corrupted. I cannot repair the Data partition, nor can select it in TWRP. My computer no longer recognizes the phone. My backup somewhat works but not really, since the data part of the backup can't be installed.
Any suggestions would be greatly appreciated. I read the entire thread and thought I was prepared but nope. Or do I need to go phone shopping?
Peeptastic said:
Is someone able to help me? I messed up in a big way. Long story short, I cannot seem to get the DATA partition back on my phone. I did read the part about encryption but was so excited I (Yes, confirmed dummy) was thinking that it meant android encryption and not simply lockscreen/password.
My passcode is correct, but the data is corrupted. I cannot repair the Data partition, nor can select it in TWRP. My computer no longer recognizes the phone. My backup somewhat works but not really, since the data part of the backup can't be installed.
Any suggestions would be greatly appreciated. I read the entire thread and thought I was prepared but nope. Or do I need to go phone shopping?
Click to expand...
Click to collapse
So why not just download the correct ruu for your phone ,,, flash that in download mode and start over ? Or has that been tried already?
It has not been tried. I didn't know what to do. I will try that, thank you. Any other tips or steps? Again, thank you!
Peeptastic said:
It has not been tried. I didn't know what to do. I will try that, thank you. Any other tips or steps? Again, thank you!
Click to expand...
Click to collapse
Its pretty straight foward, load the correct ruu on the root of your sd card , rename it to 2pzcimg.zip , boot phone to download mode , press the up volume key when prompted and thats it. hth,, good luck,
Thanks! That worked and it was super super easy.
Peeptastic said:
Thanks! That worked and it was super super easy.
Click to expand...
Click to collapse
Glad I could help

Categories

Resources