Hi there,
i try to install factory image on my nexus 6P 8.0.0 (OPR6.170623.017, Sep 2017) with the adb commands, everthing works ok but after turn on the device, the logo of starting android is moves and moves and moves and no start of the system, in the previus version it works correct, there is something on these version that makes it wrong?
secondly, i think i will downgrade to 8.0.0 (OPR6.170623.013, Aug 2017, Not for TMO/USCC/Fi), there is option to upgrade using flashfire ? if so, which version i need to download full ota image or factory image for that?
thank you
update:
so i managed to install factory image 8.0.0 (OPR6.170623.017, Sep 2017) , but when i go to settings under updates still there is update of 991MB - it's very strange.
also i need to know about the flash fire which version i need to security updates full ota image or factory image for that?
thank you
Been answered already.
The latest is 019 and after 017 you will get that OTA of 019.
wizardwiz said:
Been answered already.
The latest is 019 and after 017 you will get that OTA of 019.
Click to expand...
Click to collapse
and where i can find these to download? it's not on the developer site,
also i have another questions
thank you
You can get the 019 OTA (991Mb) file here
https://forum.xda-developers.com/sho...&postcount=282
It is weird that people get 019 OTA update of 991Mb after updating to 017. I do agree on that.
wizardwiz said:
You can get the 019 OTA (991Mb) file here
https://forum.xda-developers.com/sho...&postcount=282
It is weird that people get 019 OTA update of 991Mb after updating to 017. I do agree on that.
Click to expand...
Click to collapse
i got 404 page, but i found it and install it now everything is ok.
so about the flash fire which version i need for the security updates full ota image or factory image for that?
and what to sign over the app to save the data and the root and the twrp recovery?
thanks
I7210I said:
i got 404 page, but i found it and install it now everything is ok.
so about the flash fire which version i need for the security updates full ota image or factory image for that?
and what to sign over the app to save the data and the root and the twrp recovery?
thanks
Click to expand...
Click to collapse
New link
https://forum.xda-developers.com/showpost.php?p=73762462&postcount=282
I used the 019 OTA and flashed it after unrooting, and reverted to factory recovery. Kept ElementalX kernel and it worked like charm.
ok and for next updates, what to sign with the flashfire?and what to choose to download full ota image or factory image for that?
I7210I said:
ok and for next updates, what to sign with the flashfire?and what to choose to download full ota image or factory image for that?
Click to expand...
Click to collapse
I have always avoided OTA's and used the full Google image. They are usually available at the same time. I only select Boot, System & Vendor. It works every time without fail. It's never not worked across multiple Nexus devices. If there is a new bootloader or radio (modem) which is rare, I drop down to fastboot and flash those manually. FF is a Godsend for someone like me who has Nexus devices and updates monthly with security updates. My .02 cents.
v12xke said:
I have always avoided OTA's and used the full Google image. They are usually available at the same time. I only select Boot, System & Vendor. It works every time without fail. It's never not worked across multiple Nexus devices. If there is a new bootloader or radio (modem) which is rare, I drop down to fastboot and flash those manually. FF is a Godsend for someone like me who has Nexus devices and updates monthly with security updates. My .02 cents.
Click to expand...
Click to collapse
i assume you don't have TWRP?
I7210I said:
i assume you don't have TWRP?
Click to expand...
Click to collapse
Yes, I use TWRP. It is always preserved using FF.
so you need to preserve the recovery, isn't it?
I7210I said:
so you need to preserve the recovery, isn't it?
Click to expand...
Click to collapse
haha. yes, you use (select) the preserve recovery option. It makes a copy of your recovery partition (TWRP) so you don't lose your custom recovery. There is a FAQ on using FF here. Best of luck to you.
Thank you
Related
Nexus Security Bulletin - January 2016
Download the Factory Images
MMB29P for Nexus 5x
westernmg said:
Nexus Security Bulletin - January 2016
Download the Factory Images
MMB29P for Nexus 5x
Click to expand...
Click to collapse
Has someone captured the ota?
Nice find thanks
Now just need the modified boot.img for this newest build.
Does anyone can tell me if this month update restores the baseband menu (#*#*4636*#*#)with all the bands options?
Thank you!
it seems you need to this tread:
http://forum.xda-developers.com/nexus-5x/help/baseband-error-china-t3238867
good luck!
ns2israel said:
it seems you need to this tread:
http://forum.xda-developers.com/nexus-5x/help/baseband-error-china-t3238867
good luck!
Click to expand...
Click to collapse
Thanks!
I actually successfully followed this method and manage to get this right again. I was just curious because I read on the google forums that this bug will be solved in a next update and was curious to know if it has been indeed addressed in this build.
Travisdroidx2 said:
Now just need the modified boot.img for this newest build.
Click to expand...
Click to collapse
Actually since SuperSU 2.60 you don't need to worry about boot.img. Depends on your config though. Check out the thread below.
http://forum.xda-developers.com/showpost.php?p=64161125&postcount=3
Got the OTA just now. Any chance it might fix the wifi problems I started getting with last month's update? Or does it strictly contain only boring security fixes?
Can you post a link to OTA
bg1906 said:
Actually since SuperSU 2.60 you don't need to worry about boot.img. Depends on your config though. Check out the thread below.
http://forum.xda-developers.com/showpost.php?p=64161125&postcount=3
Click to expand...
Click to collapse
I did see that after. However, I prefer system root still at this time. But I did see where you can run some commands to make the systemless to be system root.
So I'm on the elementalX kernel, TWRP recovery, and rooted (stock) rom. Can i take the OTA that's prompting my phone without it overwriting any of that? I see that the OTA is only 11.4MB so I would assume that at most it would break ROOT.
Thanks in advance!
Tomyk89 said:
So I'm on the elementalX kernel, TWRP recovery, and rooted (stock) rom. Can i take the OTA that's prompting my phone without it overwriting any of that? I see that the OTA is only 11.4MB so I would assume that at most it would break ROOT.
Thanks in advance!
Click to expand...
Click to collapse
I don't think its even possible to update with a custom recovery.
Tomyk89 said:
So I'm on the elementalX kernel, TWRP recovery, and rooted (stock) rom. Can i take the OTA that's prompting my phone without it overwriting any of that? I see that the OTA is only 11.4MB so I would assume that at most it would break ROOT.
Thanks in advance!
Click to expand...
Click to collapse
ulxerker said:
I don't think its even possible to update with a custom recovery.
Click to expand...
Click to collapse
I have the latest TWRP recovery and I'm rooted and running ElementalX kernel. I updated yesterday successfully.
Download the factory image and extract boot.img, system.img, and vendor.img. Nothing changed in the bootloader or radio with this update, so you do not need those.
Then, run the following:
adb reboot bootloader
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash vendor vendor.img
Then reboot into TWRP and flash SuperSu again.
Then wipe cache/dalvik and reboot into system.
Sent from my Nexus 5X using Tapatalk
Hey folks,
Has the OTA URL been made intentionally harder to capture? I got the OTA noon Jan 6th and immediately dumped logcat, but despite the log covering the entire morning there was no URL in there. The log seemed to reflect that the OTA has already been downloaded over WiFi previously, and the phone's UI simply gave the option to install, not to download.
Am I missing something here, or is the only way to capture now to be intercepting traffic and manually running an update check regularly in hopes you get lucky?
I feel like the Android update model is getting even worse, not better. Now not only do Google not publish the OTA links, enthusiasts have a hard time supporting the community too.
dmudd said:
I have the latest TWRP recovery and I'm rooted and running ElementalX kernel. I updated yesterday successfully.
Download the factory image and extract boot.img, system.img, and vendor.img. Nothing changed in the bootloader or radio with this update, so you do not need those.
Then, run the following:
adb reboot bootloader
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash vendor vendor.img
Then reboot into TWRP and flash SuperSu again.
Then wipe cache/dalvik and reboot into system.
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse
You rock! I'll do this when I get home.
Tomyk89 said:
You rock! I'll do this when I get home.
Click to expand...
Click to collapse
No problem! Also, when I rebooted into system, my phone bootlooped once but didn't again after that. And you will also have to reflash the EX kernel.
Just FYI, I got all of this information from flar2 over in the EX kernel thread from this post.
tigid said:
Hey folks,
Has the OTA URL been made intentionally harder to capture? I got the OTA noon Jan 6th and immediately dumped logcat, but despite the log covering the entire morning there was no URL in there. The log seemed to reflect that the OTA has already been downloaded over WiFi previously, and the phone's UI simply gave the option to install, not to download.
Am I missing something here, or is the only way to capture now to be intercepting traffic and manually running an update check regularly in hopes you get lucky?
I feel like the Android update model is getting even worse, not better. Now not only do Google not publish the OTA links, enthusiasts have a hard time supporting the community too.
Click to expand...
Click to collapse
I didn't know there was a URL for the OTA and that it might show up in the logcat. Otherwise I would've checked for it. And doesn't logcat clear after each reboot? It would mean you would need to have adb ready and dump the log right after you start the download, but before the reboot which might be automatic. I know I've seen some logcat related stuff under dev options - at least for a longer buffer, not sure if you can make it persist across reboots.
I had not rebooted yet, the log covered from before 2AM that morning until noon when I received the notification. Unless the download occurred over ten hours before I was notified I would have expected to see the URL in the log.
Wow I have an update popped up!
Normally I have to manually do it!
Sent from my Nexus 5X using XDA Free mobile app
I was wondering how i can get the new update for the march update. I just unlocked my bootloader and got TWRP. My current OS is the stock android with the february security update.
Im tried flashing the OTA but it keeps failing. Im used to the TWRP on the oneplus two and im confused on how to get the newest update.
Please help me. Thank you
LifeOfNexus said:
I was wondering how i can get the new update for the march update. I just unlocked my bootloader and got TWRP. My current OS is the stock android with the february security update.
Im tried flashing the OTA but it keeps failing. Im used to the TWRP on the oneplus two and im confused on how to get the newest update.
Please help me. Thank you
Click to expand...
Click to collapse
You can't flash an OTA with TWRP. You need to flash the factory images with fastboot, it's all in my guide:
http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928
Heisenberg said:
You can't flash an OTA with TWRP. You need to flash the factory images with fastboot, it's all in my guide:
http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928
Click to expand...
Click to collapse
but is this going to delete data and applications
sunandoghosh said:
but is this going to delete data and applications
Click to expand...
Click to collapse
No if you read the guide carefully. It states how to flash everything WITHOUT losing any data or applications.
Heisenberg said:
You can't flash an OTA with TWRP. You need to flash the factory images with fastboot, it's all in my guide:
http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928
Click to expand...
Click to collapse
This guy has lots of great advise. I always see him giving great advise all over XDA. fastboot and adb are the icing on the cake for nexus devices. ?
Sent from my Nexus 6P using Tapatalk
sunandoghosh said:
but is this going to delete data and applications
Click to expand...
Click to collapse
No it doesn't, did you read my guide at all? It probably isn't the best idea to be giving out false information.
Has anybody tried to update with this app? https://play.google.com/store/apps/details?id=eu.chainfire.flash&hl=nl I would like know if this works good.
I'm in the same boat as OP
Should I flash MMB29V or MHC19I and do I need to update my twrp ?
I'm on stock MMB29Q with ROOT with twrp 3.0.0.0
Thanks guys any help would be super appreciated
David522d said:
I'm in the same boat as OP
Should I flash MMB29V or MHC19I and do I need to update my twrp ?
I'm on stock MMB29Q with ROOT with twrp 3.0.0.0
Thanks guys any help would be super appreciated
Click to expand...
Click to collapse
Go for the latest, which is MHC19I, you'll need to update to TWRP 3.0.0-1 though.
Heisenberg said:
Go for the latest, which is MHC19I, you'll need to update to TWRP 3.0.0-1 though.
Click to expand...
Click to collapse
Do I flash the newest twrp or does that go thru fastboot as well?
And is there any radio or bootloader that I need to update as well?
Thanks!
David522d said:
Do I flash the newest twrp or does that go thru fastboot as well?
And is there any radio or bootloader that I need to update as well?
Thanks!
Click to expand...
Click to collapse
All through fastboot, the radio and bootloader will be updated when you flash the factory images.
wietse1988 said:
Has anybody tried to update with this app? https://play.google.com/store/apps/details?id=eu.chainfire.flash&hl=nl I would like know if this works good.
Click to expand...
Click to collapse
I used FlashFire to update to March security patch; Only flashed
boot
system
vendor
Worked perfectly.
dratsablive said:
I used FlashFire to update to March security patch; Only flashed
boot
system
vendor
Worked perfectly.
Click to expand...
Click to collapse
Did you update your twrp prior?
I'll probably just do the fastboot method. But if this easier. Easier is always better
David522d said:
Did you update your twrp prior?
I'll probably just do the fastboot method. But if this easier. Easier is always better
Click to expand...
Click to collapse
I had to update TWRP afterwards.
I Flashed twrp and then did the newest factory image and kept my custom recovery and now it started up in a boot-loop
Please someone help me!
Edit
I cleared the cache in recovery and it booted
Why am I getting a "Your Device is Corrupt. It can't be trusted and may not work properly."
I tried to install the official OTA update on my Nexus 6P using Flashfire. I got an error message stating that the new OTA was older than the developer build I am already running so it wouldn't flash. Am I missing something here? Did anybody else have this problem?
Download full factory image and try flashing that with FlashFire, you don't lose your data and make sure to untick the recovery option
If I untick the recovery option does that mean I lose root and my custom recovery?
jhs39 said:
If I untick the recovery option does that mean I lose root and my custom recovery?
Click to expand...
Click to collapse
I was on dp2. Downloaded the whole ROM and used flash fire to flash. Didn't untick anything. After flashed, lost viper mod but other apps remained, including root. I did a factory reset, started from scratch, updated apps and flashed super su zip. Didn't lose twrp.
tropical cactus said:
I was on dp2. Downloaded the whole ROM and used flash fire to flash. Didn't untick anything. After flashed, lost viper mod but other apps remained, including root. I did a factory reset, started from scratch, updated apps and flashed super su zip. Didn't lose twrp.
Click to expand...
Click to collapse
Is there anything that makes the new update worth all that trouble?
jhs39 said:
Is there anything that makes the new update worth all that trouble?
Click to expand...
Click to collapse
The Dec security patch. Everything else is the same as dp2 and no beta tester logo at boot up.
tropical cactus said:
I was on dp2. Downloaded the whole ROM and used flash fire to flash. Didn't untick anything. After flashed, lost viper mod but other apps remained, including root. I did a factory reset, started from scratch, updated apps and flashed super su zip. Didn't lose twrp.
Click to expand...
Click to collapse
I was on DP2 and used the factory image but only flashed boot, system and vendor. No problems so far.
Sent from my Pixel XL using XDA-Developers mobile app
tropical cactus said:
The Dec security patch. Everything else is the same as dp2 and no beta tester logo at boot up.
Click to expand...
Click to collapse
Thanks for the info.. Will probably just wait for the IT'S then.. dB2 seems perfectly stable to me.
Joe
dratsablive said:
I was on DP2 and used the factory image but only flashed boot, system and vendor. No problems so far.
Click to expand...
Click to collapse
Do you notice any changes from DP2?
Joe
jhs39 said:
Do you notice any changes from DP2?
Joe
Click to expand...
Click to collapse
Performance wise no.
The latest April 2018 OTA update Google pushes to my Nexus 6P is only 38.7mb.
Since my phone is rooted, it won't work and I have to download the full factory image, while OTA image being 899mb and smaller than the full image, then TWRP sideload, then re-flash twrp and re-root with Magisk.
My question is, is there any way to download the 38.7mb (assuming it works) and sideload that instead?
Further, is there any way to do the adb and fastboot stuff without a PC (my PC is slow, even in Linux with all the latest update), maybe with another phone or tablet?
Another problem just came up, TWRP can't verify the 899mb OTA image and failed.
I downloaded and flashed the 899mb OTA file twice, both failed.
Anyone has the same problem?
Guess I have to download the full image and extract files and flash.
mm6ff8 said:
Another problem just came up, TWRP can't verify the 899mb OTA image and failed.
I downloaded and flashed the 899mb OTA file twice, both failed.
Anyone has the same problem?
Guess I have to download the full image and extract files and flash.
Click to expand...
Click to collapse
You can't OTA when your using custom recovery. However I've heard if people using flashfire but have never tried. With Google backup doing such a great back up now just clean wipe and start from scratch. We use too just use superXe was completely stock based and updated frequently but the developer is really busy .
While I've never tried this, and you could cause problems with your device (Make a full nandroid!), you could try flashing stock recovery from the full image, then flashing normally from within the OS.
After flash is successful, flash back to TWRP..
Exodusche said:
You can't OTA when your using custom recovery. However I've heard if people using flashfire but have never tried. With Google backup doing such a great back up now just clean wipe and start from scratch. We use too just use superXe was completely stock based and updated frequently but the developer is really busy .
Click to expand...
Click to collapse
I have successfully done TRWP's "adb sideload" March 2018 OTA image .
But this April 2018 OTA just didn't work.
Wiltron said:
While I've never tried this, and you could cause problems with your device (Make a full nandroid!), you could try flashing stock recovery from the full image, then flashing normally from within the OS.
After flash is successful, flash back to TWRP..
Click to expand...
Click to collapse
Most, if not all, rooted Nexus manual update tutorials tell us to flash recovery stock recovery image, then flash custom recovery.
But I don't see why, and I've almost always skip this step without any problem, since Nexus 4.
But you're definitely right about making a full nandroid part.
mm6ff8 said:
I have successfully done TRWP's "adb sideload" March 2018 OTA image .
But this April 2018 OTA just didn't work.
Click to expand...
Click to collapse
That's great glad you got it sorted. And even better news SuperXe was updated for April! ?
Hey guys,
I recently reverted to Stock Nougat anticipating the Oreo rollout. I'm currently on NPNS25.137-93-14 and when the system tries to install NPNS25.137-93-18, my phone reboots to recovery and shows the android symbol with "Error!" displayed on the screen. In the recovery log, it says:
Code:
E3002: Package expects build thumbprint of 7.0/NPNS25.137-93-18/4:user/release-keys
or 7.0/NPNS25.137-93-14/16:user/release-keys; this device has 7.0/NPNS25.137-93-10/12:user/release-keys
Anyone have any idea how to resolve this error so I can install the OTA?
Thanks in advance!
You're currently on 93-10, so there is another update to go to 93-14 first, before this one will work.
NZedPred said:
You're currently on 93-10, so there is another update to go to 93-14 first, before this one will work.
Click to expand...
Click to collapse
It says 93-14. The problem is it seems the Recovery img is for 93-10 and didn't get updated when the 93-14 update was applied. It seems I need a recovery with the 93-14 keys
willclein said:
It says 93-14. The problem is it seems the Recovery img is for 93-10 and didn't get updated when the 93-14 update was applied. It seems I need a recovery with the 93-14 keys
Click to expand...
Click to collapse
The OTA for 93-10 to 93-14 doen't update the recovery, I just checked. It may be that dm-verity is used to update the recovery, if it is updated at all...
How exactly did you get back to 93-14 in the first place?
NZedPred said:
The OTA for 93-10 to 93-14 doen't update the recovery, I just checked. It may be that dm-verity is used to update the recovery, if it is updated at all...
How exactly did you get back to 93-14 in the first place?
Click to expand...
Click to collapse
Sorry for the delay in responding. I started at 35-5 and applied each update through the System Update dialog in the OS. They all applied fine up until this one.
willclein said:
Sorry for the delay in responding. I started at 35-5 and applied each update through the System Update dialog in the OS. They all applied fine up until this one.
Click to expand...
Click to collapse
You may be able to apply the ota that goes from 93-10 to 93-14 again. I've never tried this, so would be 'do at your own risk'.
I've been storing the OTAs here:
https://www.dropbox.com/sh/9sr0t1b93db829h/AAAXkrYGsEFHWMVi5bgw8Uvla?dl=0
NZedPred said:
You may be able to apply the ota that goes from 93-10 to 93-14 again. I've never tried this, so would be 'do at your own risk'.
I've been storing the OTAs here:
https://www.dropbox.com/sh/9sr0t1b93db829h/AAAXkrYGsEFHWMVi5bgw8Uvla?dl=0
Click to expand...
Click to collapse
Yeah I actually downloaded that and was going to try that but wanted to see if anyone else had other ideas first. I'll take a backup and try this and report back. Thanks!