Looks like there is a new update coming.
https://9to5google.com/2016/12/05/android-7-1-1-update-ota-nexus-pixel-december/
Interesting that it is coming to Verizon pixels but no factory images from Google yet. Curious to see if both models will always have the same updates or if sometimes Verizon models will have specific ones.
Edit: Guessing this is just the January security update.
So do you think it will go to Google sold models on the Verizon network? That's what I have and when I got the phone it immediately updated to Verizon firmware, then Dec seemed like a unified update and I got that. Just had phone check for updates and I have none.
Sent from my Pixel XL using Tapatalk
ahent said:
So do you think it will go to Google sold models on the Verizon network? That's what I have and when I got the phone it immediately updated to Verizon firmware, then Dec seemed like a unified update and I got that. Just had phone check for updates and I have none.
Sent from my Pixel XL using Tapatalk
Click to expand...
Click to collapse
You'll get updates based on SIM.
Don't take it, if you even have a choice!
Ker~Man said:
Don't take it, if you even have a choice!
Click to expand...
Click to collapse
Why not? Isn't one of the benefits of the Pixel the monthly security updates?
JU57US said:
Why not? Isn't one of the benefits of the Pixel the monthly security updates?
Click to expand...
Click to collapse
Rumor is that the next Verizon OTA will make the devices bootloader permanently unlockable. If the doesn't bother you, then have at it!
Ker~Man said:
Rumor is that the next Verizon OTA will make the devices bootloader permanently unlockable. If the doesn't bother you, then have at it!
Click to expand...
Click to collapse
I may be missing something, but didn't that already happen with the Dec 5 update to 7.1.1?
Ker~Man said:
Rumor is that the next Verizon OTA will make the devices bootloader permanently unlockable. If the doesn't bother you, then have at it!
Click to expand...
Click to collapse
Yea you are a little behind. That update was released the beginning of the month. It was the 7.1.1 update. So if you get a phone from Verizon and it shipped with 7.1.1 or you let it update right away.. then you can't unlock it.
Droidlife did a story on this. http://www.droid-life.com/2016/12/27/pixel-xl-android-update-nmf26u/
Sent from my Pixel XL using Tapatalk
JU57US said:
I may be missing something, but didn't that already happen with the Dec 5 update to 7.1.1?
Click to expand...
Click to collapse
It did yes, you're correct.
I've already unlocked my bootloader, is it safe to update or do I need to stay on 7.1?
game_guy said:
I've already unlocked my bootloader, is it safe to update or do I need to stay on 7.1?
Click to expand...
Click to collapse
It's safe, just don't relock.
Sent from my Pixel XL
Rydah805 said:
It's safe, just don't relock.
Sent from my Pixel XL
Click to expand...
Click to collapse
Thanks man, one more question I forgot to include in my first post, do i need to re-root or will it stick?
game_guy said:
Thanks man, one more question I forgot to include in my first post, do i need to re-root or will it stick?
Click to expand...
Click to collapse
I believe reroot
Sent from my Pixel XL
Rydah805 said:
I believe reroot
Sent from my Pixel XL
Click to expand...
Click to collapse
im on 7.1 unlocked bl... rooted w/ twrp/supersu method... vzn pixel xl
to confirm - if i flash 7.1.1 NMF26U, then:
a) bl will NOT get relocked unless i enter the fastboot cmd to do so (which i dont plan to);
b) i will have to AND will be able to reroot using twrp/supersu method; and
c) i will lose all my data unless i delete the "-w" from the flash-all bat (which, unfortunately, i cant do for wutever reason)
much thx in advance, and thx to all for the hard work
peterlee928 said:
im on 7.1 unlocked bl... rooted w/ twrp/supersu method... vzn pixel xl
to confirm - if i flash 7.1.1 NMF26U, then:
a) bl will NOT get relocked unless i enter the fastboot cmd to do so (which i dont plan to);
b) i will have to AND will be able to reroot using twrp/supersu method; and
c) i will lose all my data unless i delete the "-w" from the flash-all bat (which, unfortunately, i cant do for wutever reason)
much thx in advance, and thx to all for the hard work
Click to expand...
Click to collapse
A) correct, your bootloader will not relock unless you command it to.
B) Correct, you will have to, and will be able to, reroot with whatever the current rooting procedure is
C)Correct, if you use the flash-all.bat without removing -w you will lose your data. You could extract all the images from the factory image zip and individually flash them and not lose your data
neilrl79 said:
A) correct, your bootloader will not relock unless you command it to.
B) Correct, you will have to, and will be able to, reroot with whatever the current rooting procedure is
C)Correct, if you use the flash-all.bat without removing -w you will lose your data. You could extract all the images from the factory image zip and individually flash them and not lose your data
Click to expand...
Click to collapse
much thx neilrl
quick follow up on (c) - how do i go abt this process? id prefer to not lose my data and not go thru the tibu restore process
peterlee928 said:
much thx neilrl
quick follow up on (c) - how do i go abt this process? id prefer to not lose my data and not go thru the tibu restore process
Click to expand...
Click to collapse
I use note ++ but I'm on Windows. Just right click the file after u un zip it and click edit with note++, remove -w and then you can just double click on the flash all bat file and it will install
peterlee928 said:
much thx neilrl
quick follow up on (c) - how do i go abt this process? id prefer to not lose my data and not go thru the tibu restore process
Click to expand...
Click to collapse
You could do this....
mac796 said:
I use note ++ but I'm on Windows. Just right click the file after u un zip it and click edit with note++, remove -w and then you can just double click on the flash all bat file and it will install
Click to expand...
Click to collapse
Or....
extract all of the images from the factory image zip( right click on the file and hit extract), make sure they are in same location as Fastboot
Then run through he commands...
Fastboot flash bootloader (name of file).IMG
Fastboot reboot bootloader
Fastboot flash radio radio.img
Fastboot flash boot boot.img
Fastboot flash system system.img
I'm sure a quick search would get you some more in depth instructions than I'm giving but it's a really simple process.
Also if you do it by Fastboot flashing the images manually, just skip flashing the recovery image and you'll still have TWRP installed for rerooting.
neilrl79 said:
You could do this....
Or....
extract all of the images from the factory image zip( right click on the file and hit extract), make sure they are in same location as Fastboot
Then run through he commands...
Fastboot flash bootloader (name of file).IMG
Fastboot reboot bootloader
Fastboot flash radio radio.img
Fastboot flash boot boot.img
Fastboot flash system system.img
I'm sure a quick search would get you some more in depth instructions than I'm giving but it's a really simple process.
Also if you do it by Fastboot flashing the images manually, just skip flashing the recovery image and you'll still have TWRP installed for rerooting.
Click to expand...
Click to collapse
There isn't a recovery image anymore, it's part of boot image now
Related
What is the most common/recommended method of unrooting back to android jelly bean 4.2.2? There are so many ways/apps out there mskip, supersu ect..
thank you.
J. Clarkson said:
What is the most common/recommended method of unrooting back to android jelly bean 4.2.2? There are so many ways/apps out there mskip, supersu ect..
thank you.
Click to expand...
Click to collapse
Flashing the stock image with fastboot. http://forum.xda-developers.com/showthread.php?t=2010312
El Daddy said:
Flashing the stock image with fastboot. http://forum.xda-developers.com/showthread.php?t=2010312
Click to expand...
Click to collapse
Any other alternatives this one looks far too complicated for me?
El Daddy said:
Flashing the stock image with fastboot. http://forum.xda-developers.com/showthread.php?t=2010312
Click to expand...
Click to collapse
As that's what you've recommended, I'll just try and do it that way. Hopefully this works, the person who is selling it to me says that his friend rooted the phone for him but he can't put it back for me but his offering a good price about £200. So I'll buy it and use this fastboot with the Factory Image "occam" for Nexus 4 4.2.2 (JDQ39) and hopfully, it should be back to normal again. I want the phones software to be just as it came out of the box. Will I need to do anything else?
Also, could you explain to me what the 'radio' is please? Never heard of this, I suppose the 'flash' is the image that I download from here https://developers.google.com/android/nexus/images, then what is 'radio?
5) Flash the bootloader: fastboot flash bootloader bootloader-mako-makoz10o.img (or whatever the name of the bootloader image that you downloaded).
7) Flash the radio: fastboot flash radio radio-mako-m9615a-cefwmazm-2.0.1700.48.img (or whatever the name is of the radio image that you downloaded).
J. Clarkson said:
As that's what you've recommended, I'll just try and do it that way. Hopefully this works, the person who is selling it to me says that his friend rooted the phone for him but he can't put it back for me but his offering a good price about £200. So I'll buy it and use this fastboot with the Factory Image "occam" for Nexus 4 4.2.2 (JDQ39) and hopfully, it should be back to normal again. I want the phones software to be just as it came out of the box. Will I need to do anything else?
Also, could you explain to me what the 'radio' is please? Never heard of this, I suppose the 'flash' is the image that I download from here https://developers.google.com/android/nexus/images, then what is 'radio?
5) Flash the bootloader: fastboot flash bootloader bootloader-mako-makoz10o.img (or whatever the name of the bootloader image that you downloaded).
7) Flash the radio: fastboot flash radio radio-mako-m9615a-cefwmazm-2.0.1700.48.img (or whatever the name is of the radio image that you downloaded).
Click to expand...
Click to collapse
Once you unzip all the .zips in the factory image that you download you will see all the .IMG files. You will have system.img, radio.img, userdata.img and your boot.img and bootloader.img. Just do exactly what the instructions say and you will see that it is very easy. And its better to learn how to do this on your own and not use a tool kit.
Sent from my Nexus 4 using xda premium
lyall29 said:
Once you unzip all the .zips in the factory image that you download you will see all the .IMG files. You will have system.img, radio.img, userdata.img and your boot.img and bootloader.img. Just do exactly what the instructions say and you will see that it is very easy. And its better to learn how to do this on your own and not use a tool kit.
Sent from my Nexus 4 using xda premium
Click to expand...
Click to collapse
Thanks mate, I'll try and take extra care and read n follow carefully, don't want to mess up here. After I have unrooted my Nexus 4, what else will I need to do to make as if it came out of the new box in terms of software ect..?
You will probably have to re install the google applications you would like; but besides those you will not need to install any additional software/apps.
beefynick said:
You will probably have to re install the google applications you would like; but besides those you will not need to install any additional software/apps.
Click to expand...
Click to collapse
Any idea which Google applications these maybe?
Chrome hopefully comes preinstalled after this unrooting process, I'm assuming the same with Google Now. It's just a case of unrooting and using the image from https://developers.google.com/android/nexus/images#occam then locking the bootloader?
Does anyone know why there is only 1 image for this phone? Usually you have many others for all networks, like T-Mobile UK ect..
After you flash the factory image, the phone will be just as it would be if you bought it from Google play. All of the Google apps will be on the phone at start up.
Once you are finished flashing the phone back to stock, reboot back into the bootloader and type, "fastboot oem lock" to re-lock the bootloader. There really is no reason to relock the bootloader. As long as you have the stock recovery, you will receive ota updates from Google.
Sent from my Nexus 4 using xda premium
lyall29 said:
After you flash the factory image, the phone will be just as it would be if you bought it from Google play. All of the Google apps will be on the phone at start up.
Once you are finished flashing the phone back to stock, reboot back into the bootloader and type, "fastboot oem lock" to re-lock the bootloader. There really is no reason to relock the bootloader. As long as you have the stock recovery, you will receive ota updates from Google.
Sent from my Nexus 4 using xda premium
Click to expand...
Click to collapse
The last part confused me, as long as I have the 'stock recovery'? That means as long as I have flashed to the factory image downloaded from Google I will receive updates from Google?
Are there any advantages/disadvantages in performance and other things from locking/not locking the bootloader? I will be keeping the original software and won't be installing custom roms ect.. just installing updates for android from Google and that's it.
J. Clarkson said:
The last part confused me, as long as I have the 'stock recovery'? That means as long as I have flashed to the factory image downloaded from Google I will receive updates from Google?
Are there any advantages/disadvantages in performance and other things from locking/not locking the bootloader? I will be keeping the original software and won't be installing custom roms ect.. just installing updates for android from Google and that's it.
Click to expand...
Click to collapse
The only thing is that if one day you decide that you want to root, you will have to re-unlock the bootloader and this will wipe all data on your phone. But if you never plan to root then you can lock it
Sent from my Nexus 4 using xda premium
lyall29 said:
The only thing is that if one day you decide that you want to root, you will have to re-unlock the bootloader and this will wipe all data on your phone. But if you never plan to root then you can lock it
Sent from my Nexus 4 using xda premium
Click to expand...
Click to collapse
And when the phone comes brand new from Google, the bootloader comes locked, right? I think I might just lock it, I will need to wipe this phone anyway.
Yes, when you get the phone new the bootloader is locked. There will be no performance loss or gain from having the bootloader locked or unlocked.
Do you have fast boot and adb set up on your computer?
Sent from my Nexus 4 using xda premium
Hi this is my first post and i hope its in the correct place and all
My nexus 7 (2013) is stuck in an android update circle where it constantly fails.
I tried to so the update to jss15q 4.3 using sideload where got so close but it said "signature verification failed" why could that be and can i stop it needing a verification?
I then tried to do it using fastboot and got so close again but got
:checking version-bootloader failed"
:device version-bootloader is "flo-03.05"
:Update requires "flo-03.14"
is there a way to correct either of them?
I am not rooted and i have downloaded the jss15q from developers google themselves (and i have debugging enabled)
Thanks for any help
Joe
Do you have the LTE version of the nexus or the WiFi version?
Guhrasoh said:
Do you have the LTE version of the nexus or the WiFi version?
Click to expand...
Click to collapse
I have the wifi only version.
joeyt90 said:
I have the wifi only version.
Click to expand...
Click to collapse
Follow this thread: http://forum.xda-developers.com/showthread.php?t=2382051 to unlock the bootloader (your data on the device will be lost). Make sure you reboot the device at least once after unlocking and before you do anything else with it!
After that you can flash or boot TWRP and try to install the update with TWRP, if that fails you can flash a full factory image (the above thread contains all the information needed).
Guhrasoh said:
Follow this thread: http://forum.xda-developers.com/showthread.php?t=2382051 to unlock the bootloader (your data on the device will be lost). Make sure you reboot the device at least once after unlocking and before you do anything else with it!
After that you can flash or boot TWRP and try to install the update with TWRP, if that fails you can flash a full factory image (the above thread contains all the information needed).
Click to expand...
Click to collapse
What exactaly do i have to do on that page to be able to continue the methods i am trying to use? If i just unlock the bootloader willi be able to update the boot loader from version-bootloader "flo-03.05" to "flo-03.14" then download jss14q using fast boot or is it not that easy?
Thanks again
P.S I dont want to root yet and Is it possible to just update the bootloader without unlock bootloader or do you have to unlock before you can update?
Thanks
If you want to use fastboot and the factory images you need to be unlocked.
Which file did you feed it when you "sideloaded" it? It needs to be the OTA file.
sfhub said:
If you want to use fastboot and the factory images you need to be unlocked.
Which file did you feed it when you "sideloaded" it? It needs to be the OTA file.
Click to expand...
Click to collapse
Hi I used the image from Google developers for nexus which was a zip file. Where could get the ota file from.
By unlocking do you mean just unlocking boot loader?
Thanks Joe
joeyt90 said:
Hi I used the image from Google developers for nexus which was a zip file. Where could get the ota file from.
By unlocking do you mean just unlocking boot loader?
Click to expand...
Click to collapse
Yes, bootloader must be unlocked to use the factory image restore.
As to the zip file, the zip file from the google developer site is a factory image. It is not meant to be sideloaded, only used in fastboot-style restores.
If you want to go the sideload route, what you want is the appropriate OTA zip (JWR66N->JSS15Q, JSS15J->JSS15Q), which you can get in the download section of this thread:
http://forum.xda-developers.com/showthread.php?t=2415497
If you'd rather do the factory image to JSS15Q, then I suggest you unlock the bootloader and use this post:
http://forum.xda-developers.com/showthread.php?p=44888268#post44888268
Personally, I'd go the factory image restore route, it is less hassle.
sfhub said:
Yes, bootloader must be unlocked to use the factory image restore.
As to the zip file, the zip file from the google developer site is a factory image. It is not meant to be sideloaded, only used in fastboot-style restores.
If you want to go the sideload route, what you want is the appropriate OTA zip (JWR66N->JSS15Q, JSS15J->JSS15Q), which you can get in the download section of this thread:
http://forum.xda-developers.com/showthread.php?t=2415497
If you'd rather do the factory image to JSS15Q, then I suggest you unlock the bootloader and use this post:
http://forum.xda-developers.com/showthread.php?p=44888268#post44888268
Personally, I'd go the factory image restore route, it is less hassle.
Click to expand...
Click to collapse
PERFECT!!!
Thank you so much to everyone who helped me on here my device is now running 4.3 version jss15q and what a difference from jwr66n.
I used the Unlock bootloader and then use factory images and it worked a treat!!
Again i cannot thank you enough i called google and the people who suplied my nexus and they both said they didnt know!!
WAHOO!!!:good::good::good::laugh::laugh:
I have a rooted 6P running the stock rom on the February security update with a bunch of Xposed modules and the Franco kernel. I know I won't get OTAs this way. Can I just flash the March security patch (MMB29V) and do nothing else? Or do I have to wipe data or factory reset? Do I have to do anything with the Franco kernel?
For the future, what would I need to do to flash Android N when it comes out on my rooted phone? Thanks a bunch!
Soundtallica said:
I have a rooted 6P running the stock rom on the February security update with a bunch of Xposed modules and the Franco kernel. I know I won't get OTAs this way. Can I just flash the March security patch (MMB29V) and do nothing else? Or do I have to wipe data or factory reset? Do I have to do anything with the Franco kernel?
For the future, what would I need to do to flash Android N when it comes out on my rooted phone? Thanks a bunch!
Click to expand...
Click to collapse
Most likely you cannot. An OTA update will do a check on your system and see that you have modified things and terminate install. You can leave your data alone but you will have to flash your boot and system partitions with the factory image
Sent from my Nexus 6P using Tapatalk
funnel71 said:
Most likely you cannot. An OTA update will do a check on your system and see that you have modified things and terminate install. You can leave your data alone but you will have to flash your boot and system partitions with the factory image
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
I know OTA updates are impossible, so I plan to flash the factory image from the Google developers website via fastboot. Does that change anything?
Soundtallica said:
I know OTA updates are impossible, so I plan to flash the factory image from the Google developers website via fastboot. Does that change anything?
Click to expand...
Click to collapse
Don't flash the entire factory image or you will lose data. / only the boot and system images to their respective partitions. Once you complete that you can Flash the OTA update zip file and you will still have your data you can extract the boot and system images from the main factory image you download from Google using WinRAR
Sent from my Nexus 6P using Tapatalk
funnel71 said:
Don't flash the entire factory image or you will lose data. / only the boot and system images to their respective partitions. Once you complete that you can Flash the OTA update zip file and you will still have your data you can extract the boot and system images from the main factory image you download from Google using WinRAR
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
It's easier to just flash all of the images (except userdata) top to update, rather than flashing two and then messing around with OTA.
So is there anyway to flash the update without losing my data/apps??
Thanks!
cattel said:
So is there anyway to flash the update without losing my data/apps??
Thanks!
Click to expand...
Click to collapse
http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928
Heisenberg said:
http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928
Click to expand...
Click to collapse
Thank you very much!
Enviado de meu Nexus 6P usando Tapatalk
Step 9, right @Heisenberg ?
joooe said:
Step 9, right @Heisenberg ?
Click to expand...
Click to collapse
Yep. Probably would be a good idea to wipe data and the caches in TWRP first.
i used fastboot to install march update on my nexus 6p but now when trying to install twrp through fastboot it during writing it says permission denied. why is this?
mystertom said:
i used fastboot to install march update on my nexus 6p but now when trying to install twrp through fastboot it during writing it says permission denied. why is this?
Click to expand...
Click to collapse
Can you provide a screenshot of your attemp to flash the recovery? Also you might want to try opening the command prompt as administrator, right click on the command window in start menu and select open as administrator.
Heisenberg said:
Yep. Probably would be a good idea to wipe data and the caches in TWRP first.
Click to expand...
Click to collapse
Not at all a good idea @Heisenberg, as I just experienced. We were talking about keeping the apps and system as it was. Just wiped data and got an hardreset.
Clear cache only.
joooe said:
Not at all a good idea @Heisenberg, as I just experienced. We were talking about keeping the apps and system as it was. Just wiped data and got an hardreset.
Clear cache only.
Click to expand...
Click to collapse
Where did you say that? I know that wiping data will remove apps, but it's the right way to go about it to ensure no problems occur.
cattel said:
So is there anyway to flash the update without losing my data/apps??
Thanks!
Click to expand...
Click to collapse
It all went after this post.
But no problem.
joooe said:
It all went after this post.
But no problem.
Click to expand...
Click to collapse
Surely you were aware that wiping data was going to remove your apps? So all you needed to do was back them up first and restore them after you flashed. Apologies if I should have made that clear in my previous posts.
No problem. It was my stupid mistake.:good:
fastboot flash bootloader bootloader-angler-angler-02.45.img
fastboot reboot-bootloader
sleep 5
fastboot flash radio radio-angler-angler-02.50.img
fastboot reboot-bootloader
sleep 5
fastboot update image-angler-mmb29v.zip
Normally in the last line there is an option "-w" this wipes the data.
Don't do that and modify the script so the option is gone, like I did.
Uh, my phone just downloaded a system update of some sort, but I haven't installed it. Is this supposed to happen on a phone that's rooted and on the stock ROM? Can I install it safely or should I still flash the factory image instead?
And @Heisenberg, in your guide do you type in all the fastboot commands at once or do you do it line by line? Thanks again, your guide is super useful for rooting noobs like me :thumbup:
Soundtallica said:
Uh, my phone just downloaded a system update of some sort, but I haven't installed it. Is this supposed to happen on a phone that's rooted and on the stock ROM? Can I install it safely or should I still flash the factory image instead?
And @Heisenberg, in your guide do you type in all the fastboot commands at once or do you do it line by line? Thanks again, your guide is super useful for rooting noobs like me :thumbup:
Click to expand...
Click to collapse
Don't install it, it'll fail, you must flash the factory images. Each command is entered individually (press enter key to send the command), wait for flash to finish then enter the next command.
Hey guys,
This afternoon I tried to change my file system fo f2fs, I failed and got into bootloop. Follow some instructions, I flash the factory image (I was using stock 7.1.1 Feb and EX Kernel before trying f2fs) but I still face the bootloop. As I know this is a softbrick, because I can still boot into bootloader and flash recovery. But no matter how I try (flash stock, flash rom cook, flash older stock)...my 6P is still in the bootloop. I check in the TWRP that my phone is still in ext4, not f2fs anymore.
I really need some advice to wake him up. Really appreciate your help.
In all honesty bro, I never noticed much difference if any with ext4 vs f2fs. On another note, what kernel and ROM did you flash with f2fs? The the version that supports f2fs gives bootloops when you flash a custom kernel with that recovery. Try flashing the official version of recovery, reboot, then ROM and kernel if you wish and try again.
Sent from my Nexus 6P using XDA-Developers Legacy app
nhatminhng said:
Hey guys, I really need some advice to wake him up. Really appreciate your help.
Click to expand...
Click to collapse
Fastboot format your partitions and use flash-all.bat with a stock Google image.
nhatminhng said:
Hey guys,
This afternoon I tried to change my file system fo f2fs, I failed and got into bootloop. Follow some instructions, I flash the factory image (I was using stock 7.1.1 Feb and EX Kernel before trying f2fs) but I still face the bootloop. As I know this is a softbrick, because I can still boot into bootloader and flash recovery. But no matter how I try (flash stock, flash rom cook, flash older stock)...my 6P is still in the bootloop. I check in the TWRP that my phone is still in ext4, not f2fs anymore.
I really need some advice to wake him up. Really appreciate your help.
Click to expand...
Click to collapse
Why do you still have TWRP if you flashed stock? You need to flash the complete stock image including the stock recovery.
MidnightDevil said:
In all honesty bro, I never noticed much difference if any with ext4 vs f2fs. On another note, what kernel and ROM did you flash with f2fs? The the version that supports f2fs gives bootloops when you flash a custom kernel with that recovery. Try flashing the official version of recovery, reboot, then ROM and kernel if you wish and try again.
Sent from my Nexus 6P using XDA-Developers Legacy app
Click to expand...
Click to collapse
jhs39 said:
Why do you still have TWRP if you flashed stock? You need to flash the complete stock image including the stock recovery.
Click to expand...
Click to collapse
v12xke said:
Fastboot format your partitions and use flash-all.bat with a stock Google image.
Click to expand...
Click to collapse
Thanks guys for helping. I fixed it.
I always flashed the stock image step by step followed by heisenberg, and never use the flash-all.bat just because I dont understand how to run it. However a guy in the f2fs told me to add in some steps
fastboot format system
fastboot format userdata
fastboot format cache
Click to expand...
Click to collapse
And it works. It seems like the step by step way is not clear enough. Any guys can tell me how to run the flash-all.bat please? When I run it always said fastboot is not etc...
nhatminhng said:
Thanks guys for helping. I fixed it. I always flashed the stock image step by step followed by heisenberg, and never use the flash-all.bat just because I dont understand how to run it. However a guy in the f2fs told me to add in some steps And it works. It seems like the step by step way is not clear enough. Any guys can tell me how to run the flash-all.bat please? When I run it always said fastboot is not etc...
Click to expand...
Click to collapse
It's a good sign you formatted and received no errors in fastboot. Google provides instructions for flash-all.bat on the same page you download the images from. https://developers.google.com/android/images
If you are not comfortable using the command window in Windows, you could also use a toolkit like Wugfresh's NRT or Skipsoft's Toolkit to automate the whole process.
v12xke said:
It's a good sign you formatted and received no errors in fastboot. Google provides instructions for flash-all.bat on the same page you download the images from. https://developers.google.com/android/images
If you are not comfortable using the command window in Windows, you could also use a toolkit like Wugfresh's NRT or Skipsoft's Toolkit to automate the whole process.
Click to expand...
Click to collapse
Yes sir of course I read it. But I dont understand this step.
Open a terminal and navigate to the unzipped system image directory.
Click to expand...
Click to collapse
Is it I open the fastboot cmd, use cd command to navigate to that directory? I already tried but failed to run :'( Although I have fixed it but I want to know just in case the next time. Thanks.
nhatminhng said:
Yes sir of course I read it. But I dont understand this step.
Is it I open the fastboot cmd, use cd command to navigate to that directory? I already tried but failed to run :'( Although I have fixed it but I want to know just in case the next time. Thanks.
Click to expand...
Click to collapse
Hi... Here's a pretty good detailed process on how to unlock/flash, etc...
https://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928/page549
Also, before using any toolkit, I suggest using manual commands and getting comfortable with it. At least, you learn exactly what command do what! Simply pressing a button in a program may result in a bricked device. Plus with command line you learn something. :good:
@nhatminhng How did you get your phone fixed? is your phone unlocked?
tjchuot287 said:
@nhatminhng How did you get your phone fixed? is your phone unlocked?
Click to expand...
Click to collapse
What do you mean "unlocked"? The bootloader is unlocked and I can flash recovery too. I use the command line in heisenberg thread and flash my phone to stock. Add in some more steps I mentioned above. Boom. It's back again.
nhatminhng said:
What do you mean "unlocked"? The bootloader is unlocked and I can flash recovery too. I use the command line in heisenberg thread and flash my phone to stock. Add in some more steps I mentioned above. Boom. It's back again.
Click to expand...
Click to collapse
@nhatminhng oh, im sorry, i mean unlocked bootloader. So my bootloader is locked, it still doesnt have any solutions yet.
tjchuot287 said:
@nhatminhng oh, im sorry, i mean unlocked bootloader. So my bootloader is locked, it still doesnt have any solutions yet.
Click to expand...
Click to collapse
Do you have access to recovery or just boot loader?
Sent from my Nexus 6P using XDA-Developers Legacy app
CyberpodS2 said:
Do you have access to recovery or just boot loader?
Sent from my Nexus 6P using XDA-Developers Legacy app
Click to expand...
Click to collapse
Yes i can. I tried to sideload multiple version of OTA but all have failed.
tjchuot287 said:
Yes i can. I tried to sideload multiple version of OTA but all have failed.
Click to expand...
Click to collapse
I'm guessing you've already tried a factory reset from the stock recovery. Because your bootloader is locked you are limited to sideloading OTA's. And yes, sideloading an older or equal version OTA will fail. You can try a newer revision OTA when available. The 7.1.2 beta may come out before the March security update.
v12xke said:
I'm guessing you've already tried a factory reset from the stock recovery. Because your bootloader is locked you are limited to sideloading OTA's. And yes, sideloading an older or equal version OTA will fail. You can try a newer revision OTA when available. The 7.1.2 beta may come out before the March security update.
Click to expand...
Click to collapse
Good point. It didn't occur to me that equal version would fail. Folks need to unlock their boot loaders! Lol
Sent from my Nexus 6P using XDA-Developers Legacy app
CyberpodS2 said:
Good point. It didn't occur to me that equal version would fail. Folks need to unlock their boot loaders! Lol
Click to expand...
Click to collapse
I agree. Unless you absolutely cannot live without Android Pay or Wallet, work phone, etc., there is no reason to not unlock the bootloader as a safeguard. Of course it's no guarantee, but you just have a whole lot more tools at your disposal when SHTF, including restoring a recent backup or flashing a complete stock image. The initial pain of losing your data can be largely mitigated by pulling it off first, and eventually you even forget about the boot nag screen.
v12xke said:
I agree. Unless you absolutely cannot live without Android Pay or Wallet, work phone, etc., there is no reason to not unlock the bootloader as a safeguard. Of course it's no guarantee, but you just have a whole lot more tools at your disposal when SHTF, including restoring a recent backup or flashing a complete stock image. The initial pain of losing your data can be largely mitigated by pulling it off first, and eventually you even forget about the boot nag screen.
Click to expand...
Click to collapse
Now i have unlocked bootloader but the phone keep restart and stuck at logo again. i followed @Heisenberg thread but same result.
Oneplus 8 Fastboot ROMs
DOWNLOADS:
https://www.androidfilehost.com/?w=files&flid=326825
Mirror:
Current version: IN2011_11_C.21_202205172355
PASSWORD: XDA2021 or XDA2022 (newest files)
infected_ said:
Made this little project using the script from @mauronofrio FASTBOOT ROMs to return OP8 to latest OOS, since I was always having issues doing so, and always ended up using the unbrick tool for OP8.
Enjoy! If you have any issues, just let me know using a post.
Regards.
Current FASTBOOT ROM 11.0.5.5 download link:
AFH Server:
OP8 OOS 11.0.5.5 FASTBOOT ROM
OP8 OOS 11.0.5.5 MAGISK PATCHED BOOT.IMG
Click to expand...
Click to collapse
I have a T-Mobile device, which I converted to Global and finally installed a custom ROM. For any updates, I have to follow the same route - go back to T-Mobile, then global and then any other ROM. Can I use this utility to go back directly to Global from custom or would I still need to first flash T-Mobile ROM?
sjgoel said:
I have a T-Mobile device, which I converted to Global and finally installed a custom ROM. For any updates, I have to follow the same route - go back to T-Mobile, then global and then any other ROM. Can I use this utility to go back directly to Global from custom or would I still need to first flash T-Mobile ROM?
Click to expand...
Click to collapse
Technically, this process would be the same as a conversion. Just see if you need to backup any other extra partition, like persist.img or other.
Regards.
thank you so much for this, ive been stuck or soft bricked for the last 4 days and this might just be my out.
Hi, thanks for this! Now I have a question, I have latest OOS with Magisk, but since upgrade to 11 i have System UI crashes and serious lags and freeze, I did 4 factory resets and its still there, I want to reflash all from 0, can I use this?
Thank you very much for the contribution
nikola1970 said:
Hi, thanks for this! Now I have a question, I have latest OOS with Magisk, but since upgrade to 11 i have System UI crashes and serious lags and freeze, I did 4 factory resets and its still there, I want to reflash all from 0, can I use this?
Click to expand...
Click to collapse
try reflashing on both slots.
infected_ said:
try reflashing on both slots.
Click to expand...
Click to collapse
Ok, so first I need to flash slot a, and right after that i am gonna flash b slot? Thanks man
showing my ignorance...where is the flash-all.bat script? Is that somewhere in this thread?
gloster2 said:
showing my ignorance...where is the flash-all.bat script? Is that somewhere in this t
Click to expand...
Click to collapse
There's a self extracting file (*.exe) inside the zip file. Have you run it, and checked the extracted files?
infected_ said:
There's a self extracting file (*.exe) inside the zip file. Have you run it, and checked the extracted files?
Click to expand...
Click to collapse
Thanks -- I didn't notice it was an executable. I think I'm ready to go, but just checking. Here's what I've done so far with my T-Mobile version OnePlus 8:
1. completed process to unlock the bootloader (unlocked phone, got token, applied token)
2. set up fastboot in a directory on my Windows PC
3. ran the self-extraction on OnePlus8Oxygen_15.E.35_OTA_0350_all_2103221815-FASTBOOT
Now I'm going to run flash-all.bat. Before I do that, do I need to back up any files, e.g. modem files? Thanks!
gloster2 said:
Thanks -- I didn't notice it was an executable. I think I'm ready to go, but just checking. Here's what I've done so far with my T-Mobile version OnePlus 8:
1. completed process to unlock the bootloader (unlocked phone, got token, applied token)
2. set up fastboot in a directory on my Windows PC
3. ran the self-extraction on OnePlus8Oxygen_15.E.35_OTA_0350_all_2103221815-FASTBOOT
Now I'm going to run flash-all.bat. Before I do that, do I need to back up any files, e.g. modem files? Thanks!
Click to expand...
Click to collapse
backup persist.img and modem.img just in case, and you should be ok to go.
PS: i'm going to upload the fastboot rom without the self extracting method to be easier for users.
Deleted
@infected_ Considering that I am coming from an unlocked bootloader, will this method re-lock the bootloader and is this carrier-branded compatible?
rodken said:
@infected_ Considering that I am coming from an unlocked bootloader, will this method re-lock the bootloader and is this carrier-branded compatible?
Click to expand...
Click to collapse
No, it won't relock the bootloader
infected_ said:
No, it won't relock the bootloader
Click to expand...
Click to collapse
Safe to use for Verizon OP8 5G UW or is this a method to go Global from a carrier-branded version?
infected_ said:
backup persist.img and modem.img just in case, and you should be ok to go.
PS: i'm going to upload the fastboot rom without the self extracting method to be easier for users.
Click to expand...
Click to collapse
sorry for another simple question; I haven't done system level things with Android in a long time. Where are instructions on how to backup those files? I did a little searching, but haven't found anything that works yet.
gloster2 said:
sorry for another simple question; I haven't done system level things with Android in a long time. Where are instructions on how to backup those files? I did a little searching, but haven't found anything that works yet.
Click to expand...
Click to collapse
There is an app for that.
rodken said:
There is an app for that.
Click to expand...
Click to collapse
Thanks! Now I realize that even though I have an unlocked bootloader, I don't have root access. Now I have to figure out how to get that. Sigh.
And...I see much conflicting information on how to root my bootloader unlocked T-Mobile version OnePlus 8. Any advice/pointers to info on the best/easiest way to root it?