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?
Related
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.?
Hi guys,
i have a pixel and i want to enrrol to the beta program, i just done the process but it seams that update is not arriving, its posible that verizon pixels can't enroll to beta program?
http://www.droid-life.com/2017/01/30/android-7-1-2-beta-download-update-nexus-pixel/
Regards
You can download the full image here
I dont have oem unlocked. I can sideloade it?
Yea even i didn't get it. I guess it not for the verizon phones.
Can anyone who has upgraded to 7.1.2 let us know if it appears stable enough for a daily driver and have they noticed any differences ? Thank you.....
Another locked bootloader VZW customer here who enrolled and is waiting for OTA. I think we'll get it, just have to wait for OTA's to start. Google let us enroll, and we seem to have gotten updates from Google and not VZW so far. I think it'll just take a day or 2 to start rolling.
I installed 7.1.2 briefly. No changes that I noticed besides radio and boot IMG. Seemed stable enough for daily, I went back to PN because of substratum.
I am a non VZW pixel user (Koodo - Canada) and have not received the OTA after signing up yesterday. They note that it may take 24 hours and looks like it's going to for me.
k.s.deviate said:
I installed 7.1.2 briefly. No changes that I noticed besides radio and boot IMG. Seemed stable enough for daily, I went back to PN because of substratum.
Click to expand...
Click to collapse
I know that the bootloader is what loads the Android filesystem to the boot image, I wonder if it can somehow be manipulated to unlock and root since you mention that the boot image is different? Does anyone know? Thanks
Just about 24 hours of enrollment here on my VZW Pixel with no OTA yet. Google support confirmed my device was eligible... Has ANYONE, regardless of carrier, received a beta OTA?
farfromovin said:
Just about 24 hours of enrollment here on my VZW Pixel with no OTA yet. Google support confirmed my device was eligible... Has ANYONE, regardless of carrier, received a beta OTA?
Click to expand...
Click to collapse
Signed up yesterday for both my Pixel (VZW sim) and Pixel XL (Project Fi sim) both bought direct from Google. Pixel XL rec'd update almost immediately not yet on Pixel so far.
If anyone gets the OTA, please pull and post it. OTA's can be flashed in TWRP, followed by a re-flash of TWRP to keep custom recovery. I'm too lazy to download the full firmware, edit it, and flash with a computer.
Sent from my Pixel using Tapatalk
joshw0000 said:
If anyone gets the OTA, please pull and post it. OTA's can be flashed in TWRP, followed by a re-flash of TWRP to keep custom recovery. I'm too lazy to download the full firmware, edit it, and flash with a computer.
Click to expand...
Click to collapse
The edit you mention. Is that just removing the -w command from the flash all script. Or is there more involved in updating from a factory image?
murryrulz said:
The edit you mention. Is that just removing the -w command from the flash all script. Or is there more involved in updating from a factory image?
Click to expand...
Click to collapse
Nope it's exactly that. Just remove -w so it doesn't wipe the device. It's how I update my Pixel and 5X since I'm impatient waiting for OTAs.
murryrulz said:
The edit you mention. Is that just removing the -w command from the flash all script. Or is there more involved in updating from a factory image?
Click to expand...
Click to collapse
Correct. And for some reason the flash-all.bat never works for me. It fails towards the end of the flash. I have to run it through one of those tool kits for it to accept it.
Flashing the OTA in TWRP is a smaller download, quicker, no PC, and it consistently works for me.
Like I said, I'm lazy lol.
Sent from my Pixel using Tapatalk
joshw0000 said:
Correct. And for some reason the flash-all.bat never works for me. It fails towards the end of the flash. I have to run it through one of those tool kits for it to accept it.
Flashing the OTA in TWRP is a smaller download, quicker, no PC, and it consistently works for me.
Like I said, I'm lazy lol.
Click to expand...
Click to collapse
I had the same problem a long time ago. Turns out I was using an old version of fastboot. Once I updated it I had no problem with the flashall.bat
OTA hasn't rolled for the pixel yet, likely "soon", my guess is today or tomorrow at the latest since XL has gone out. I am on project FI and got the pixel through the play store fyi
murryrulz said:
I had the same problem a long time ago. Turns out I was using an old version of fastboot. Once I updated it I had no problem with the flashall.bat
Click to expand...
Click to collapse
I've tried updating mine but that doesn't seem to help. I spent a considerable amount of time working on it one day with no luck. Mine is installed so that it'll work from any directory (I don't have to put my files in the same directory). I even tried putting the new adb/fastboot in the same folder as the flash-all.bat with the same results.
Sent from my Pixel using Tapatalk
I am also in the waiting for the OTA camp and use an unlocked Verizon Pixel and PIxel XL. I have had better luck using the TWRP sideload method and it installing to the other slot with each subsequent sideload appears to me a more consistent way to keep everything updated in the same way that the system OTA works.
joshw0000 said:
I've tried updating mine but that doesn't seem to help. I spent a considerable amount of time working on it one day with no luck. Mine is installed so that it'll work from any directory (I don't have to put my files in the same directory). I even tried putting the new adb/fastboot in the same folder as the flash-all.bat with the same results.
Sent from my Pixel using Tapatalk
Click to expand...
Click to collapse
Get rid of windows, use Linux, no messing around with anything, it just works ?
-------- runs -----_ducks_---- runs ----
Sent from my Pixel using XDA-Developers Legacy app
So I was away from my computer when the January Security update came out so Im on the December update.
I would like to know can I just jump straight to the Feb update when its available or do I need to do Jan first then Feb?
im unlocked, rooted, ex kernel, google store phone. thanks.
You can just jump.
my phone is on the latest 8.1 april ota.
after the update the phone freezes when placing and recieving phone calls
is it possible to "downgrade" to the previous ota the one from march to test the phone app or will it break the phone
i googled the hell out of this but only found people flashing later releases and not previous ones
thanks
kidhudi said:
my phone is on the latest 8.1 april ota.
after the update the phone freezes when placing and recieving phone calls
is it possible to "downgrade" to the previous ota the one from march to test the phone app or will it break the phone
i googled the hell out of this but only found people flashing later releases and not previous ones
thanks
Click to expand...
Click to collapse
I think downgrading via OTA it's quite impossible.
You have to wipe and flash the full factory image.
damn it thats what i was afraid of.
thanks
kidhudi said:
damn it thats what i was afraid of.
thanks
Click to expand...
Click to collapse
You should've have to wipe. Just flash the full image but remove the -w from the flash all bat file. That saves data and settings. But backup to be sure.
TonikJDK said:
You should've have to wipe. Just flash the full image but remove the -w from the flash all bat file. That saves data and settings. But backup to be sure.
Click to expand...
Click to collapse
i got the verizon varient. it seems i cant oem unlock the device.
i searched all day and cant find a technique that works so flashing the stock image is a no go apparently.
life was so much easier with my nexus 6.
damn verizon.
kidhudi said:
i got the verizon varient. it seems i cant oem unlock the device.
i searched all day and cant find a technique that works so flashing the stock image is a no go apparently.
life was so much easier with my nexus 6.
damn verizon.
Click to expand...
Click to collapse
Time to start clearing data on the dialer related apps, or reset the phone. I am hopeful that will help you. If it was soley update related the forum would be blowing up with complaints.
Now did something go wrong with your update... I'll buy that.
i just assumed it was the april security update it started acting up around the same time. i thought maybe a crappy download
i already did a few factory resets. tried third party dialers. everything i could think of.
what really sucks is i am 3 months out of the 1 year google warranty. so i am pretty much screwed.
thanks for your help bro
i will try to sideload the latest ota.. if it is still jacked up then it is probably hardware related
what sucks is i am still paying it off and it is virtually unusable lol.. at least i can text
Hey guys,
So I've been out of the rooting/unlocking field for a while and kind of forget some of the basic rules.
So my Verizon Pixel was unlocked and rooted immediately after I got it.
It has NOT been updated in any way since then.
I am still on Android 7.1 and the November Security Patch. I figure its time to update now that oreo is out.
Heres the question:
Do I have to flash back to stock before updating? Or can I just flash the OTA update through TWRP? I figure I would have to reflash the recovery and root possibly I'm just not sure which way I should go about it. Also, would doing this wipe my data?
Any help would be greatly appreciated.
Thanks!
Bump
Po1soNNN said:
Bump
Click to expand...
Click to collapse
It would probably be easier to just flash the full factory image using the .bat script it comes packaged with. You could try removing the -w to retain data but I wouldn't count on it booting smoothly with the version jumps you're performing. If it doesn't work, just flash it again with the -w in place and you'll be good to go although you'll have to set everything up and you should make sure anything crucial is backed up somewhere.
Know that the "O" twrp and root flashing instructions are a little different from the Nougat days.
I rooted my phone last week because I wanted to use substratum to theme my notifications. Since then, I've run into a bunch of frustrating problems.
Current Model: OnePlus 7 Pro 12GB version, build xXx_NoLimits_7.7 on OOS 9.5.11-GM21AB
Problems:
Phone used to be 9.5.11-GM21AA but now it's 9.5.11-GM21AB - does this affect anything?
Substratum hasn't worked in stock+root, and 2 different ROMs I've tried
Favourite app of mine doesn't work properly and I think it's because I'm on build 9.5.11 and not 9.5.10
How I messed it up: Started by rooting and trying to install Renovate ICE Rom, installed the wrong file which converted me to 9.5.5-GM21AB. Then I updated to 9.5.11 but it remained AB. I tried several times to unroot, roll back and get to 9.5.10AA but it always kept itself at 9.5.11AB. Sometimes my wifi would break. I currently have xXx NoLimits Rom installed.
Desired outcome: I want to unroot and roll back to 9.5.10-GM21AA stock
Any help is greatly appreciated. Thank you!
MSM tool should fix it.
virtyx said:
MSM tool should fix it.
Click to expand...
Click to collapse
+1
virtyx said:
MSM tool should fix it.
Click to expand...
Click to collapse
zams85 said:
+1
Click to expand...
Click to collapse
Thanks, that was super easy. MSM automatically rolled back my phone to 9.5.3.GM21AA.
I have one more question - if I want to update it to 9.5.10GM21AA, how would I do that? If I update through the system, it will take me to 9.5.11, which I do not want. If the process is easier if I'm rooted, I already did that. To top it off, my substratum is working now after I reset my phone to how it is now. All I need is to update it to 9.5.10 and I would be sooooooo happy .
Thanks in advance!
bmcmr said:
Thanks, that was super easy. MSM automatically rolled back my phone to 9.5.3.GM21AA.
I have one more question - if I want to update it to 9.5.10GM21AA, how would I do that? If I update through the system, it will take me to 9.5.11, which I do not want. If the process is easier if I'm rooted, I already did that. To top it off, my substratum is working now after I reset my phone to how it is now. All I need is to update it to 9.5.10 and I would be sooooooo happy .
Thanks in advance!
Click to expand...
Click to collapse
Just download the full zip for 9510 and update via system update
virtyx said:
Just download the full zip for 9510 and update via system update
Click to expand...
Click to collapse
Thanks for your reply! I thought as much. Can you clarify if these steps are right?
Go to https://androidfilehost.com/?w=files&flid=294300
Download the one I want (9.5.10AA)
Move the file to my phone's internal storage
Update via Local Upgrade
Is this correct? Will I still have root after I do this?
bmcmr said:
Thanks for your reply! I thought as much. Can you clarify if these steps are right?
Go to https://androidfilehost.com/?w=files&flid=294300
Download the one I want (9.5.10AA)
Move the file to my phone's internal storage
Update via Local Upgrade
Is this correct? Will I still have root after I do this?
Click to expand...
Click to collapse
Correct
You will unrooted after the upgrade as itll flash completely stock.
Just re-roof after it and your good to go!
Hey @virtyx I copied the exact zip file I downloaded into my root directory for Local Upgrade but it wasn't recognized. I then tried to just flash the zip through TWRP but it said it was an "Invalid zip file format".
Do you know what I'm doing wrong?
bmcmr said:
Hey @virtyx I copied the exact zip file I downloaded into my root directory for Local Upgrade but it wasn't recognized. I then tried to just flash the zip through TWRP but it said it was an "Invalid zip file format".
Do you know what I'm doing wrong?
Click to expand...
Click to collapse
Strange
Try downloading the update again maybe it got corrupt during the download.
Make sure it's from OP website too
Whats wrong with .10 ? .11 borked or something?
virtyx said:
Strange
Try downloading the update again maybe it got corrupt during the download.
Make sure it's from OP website too
Click to expand...
Click to collapse
I got 9.5.9 from the OP forums and it worked! Everything is exactly how I want it now. Thanks for your help!
sarni84 said:
Whats wrong with .10 ? .11 borked or something?
Click to expand...
Click to collapse
For my purposes, 9.5.9 and 9.5.10 are good. 9.5.11 reverted something with the brightness and so I don't want to use it.
I found a zip from the OP site for 9.5.9 so I was able to update to that one and since I got root/substratum to work without issue, I'm happy to stay at this build. In my eyes, my phone is absolutely perfect now and I am extremely happy. The only thing I would change is the size but that has nothing to do with the software/OS. Thanks for everybody's help!
bmcmr said:
I got 9.5.9 from the OP forums and it worked! Everything is exactly how I want it now. Thanks for your help!
For my purposes, 9.5.9 and 9.5.10 are good. 9.5.11 reverted something with the brightness and so I don't want to use it.
I found a zip from the OP site for 9.5.9 so I was able to update to that one and since I got root/substratum to work without issue, I'm happy to stay at this build. In my eyes, my phone is absolutely perfect now and I am extremely happy. The only thing I would change is the size but that has nothing to do with the software/OS. Thanks for everybody's help!
Click to expand...
Click to collapse
I don't blame you, 9511 isn't as smooth as 9510.
also noticed 9510 had better battery life.
I might roll back myself