Database Develop

How to Install Project Fi OTA???

OK ... Dumb Question(s) - How do I update to the current Project Fi Build LVY48E?
- I have downloaded the posted Zip File (LVY48E from LVY48C - https://android.googleapis.com/packa...rblock-fix.zip)
- Does this affect the LVY48C Radios? - Prior instructions said to just flash the system image if the radios were not changed but this is not a factory image .zip file? - It looks like the update mainly affects the system but there is a boot.img.p patch that concerns me?
I am rooted, unlocked, decrypted (Stock Rom w/Hells Core Kernel), and have TWRP recovery installed and I don't want to lose any data, get encrypted, change the bootloader or lose my custom recovery.
Any help is appreciated

Here's the process I went through
1) Back a TWRP backup of your current system
2) Download the official LVY48C factory image from Google
3) Extract all the files out the factory image
4) Using fastboot flash system, recovery and boot with the factory image ones
5) Reboot into recovery which is the stock recovery
6) While in the stock recovery hold down the power button and tap the volume up button
7) Select apply update from USB or sideload mode
8) On your computer run adb sideload <name of ota>
9) Reboot back into the bootloader and flash TWRP again
I recommend simply waiting though until the factory image for LVY48E is posted by Google as it will be a much simpler process

Thanks for the information ... I thought I might be able to rename the zip to update.zip and sideload it through twrp. You are defintely right about the factory image, I can just pull the system image and flash that. I wonder if they will release a factory image since it was just a system patch?

Deckard_9732 said:
Thanks for the information ... I thought I might be able to rename the zip to update.zip and sideload it through twrp. You are defintely right about the factory image, I can just pull the system image and flash that. I wonder if they will release a factory image since it was just a system patch?
Click to expand...
Click to collapse
They've already posted the factory images for the standard build and the T-Mobile build so I imagine that they'll release the Fi one soon.

FYI, an OTA needs to be flashed from a stock recovery AND must be 100% stock rom and kernel...

samstudent said:
They've already posted the factory images for the standard build and the T-Mobile build so I imagine that they'll release the Fi one soon.
Click to expand...
Click to collapse
Its out now

Haven't been able to update since LMY48I. Trying to get on Marshmallow now.

Okay, I haven't been able to update since LMY48I. Back then I was on stock recovery. Re-locking bootloader and all but still was not able to take OTA (always came up with dead android guy with "Error"). I'll skip the (probably) irrelevant stuff since then and give you the current situation:
Currently unlocked, rooted, with custom recovery. Still on LMY48I. I can't take OTAs obviously, and have tried flashing OTA updates manually with no luck and have tried flashing the entire Marshmallow image and that will not work either (sideload or flashing from internal storage in recovery). Sideload comes up with Closed error (device DOES show up in device list and I can do other things). Flashing from within recovery just says "Failed".
Please help me get to Marshamallow!
Edit: On Project Fi by the way.
Edit 2: Also, I've tried the flash-all script.

Now it says the device is corrupted when I boot up. I can still access recovery. Any help walking me through getting all of the correct firmware and latest build on would be much appreciated.
Thank you.
Edit: Looks like i'm good. I flashed each .img individually. I'm super curious why flash-all, sideload, and flashing from device wouldn't work though.

altvisionx said:
......./I flashed each .img individually. I'm super curious why flash-all, sideload, and flashing from device wouldn't work though.
Click to expand...
Click to collapse
Flashall.bat stops; only m-bootloader and m-radio are flash. Google's fault. You did the right thing by extracting the images and fasbiot flash them.

You cannot sideload the full factory image or flash from storage. Only fastboot

And just to clarify, you can't take an OTA (sideloading or otherwise) if your phone is rooted, have a custom recovery or a custom kernel (or any other modification to the system). The state of the bootloader (locked or unlocked) does not affect the ability to take an OTA update.

Cannot update 7.1.1 OTA (help needed)

So I've received an OTA notification that will NOT go away for the last 3 days.
I'm currently on N6F27E build (June 5th build)
I download the update & it reboots to TWRP & then does nothing...
I've tried using twrp's sideload mode, but that too does nothing...
So I need to know where to get the latest stock recovery.img & how to flash it, so I can update everything.
Additional info:
- unlocked bootloader
- stock / no-root

To take an OTA you must be on stock, as you probably have guessed by now. Download a system image from Google, extract it, and inside will be a recovery image you can flash. An easier way to go here would be to simply download the latest system image and flash everything but the recovery image using fastboot commands.

Strephon Alkhalikoi said:
To take an OTA you must be on stock, as you probably have guessed by now. Download a system image from Google, extract it, and inside will be a recovery image you can flash. An easier way to go here would be to simply download the latest system image and flash everything but the recovery image using fastboot commands.
Click to expand...
Click to collapse
Thank you for the help.
I have had no issues flashing OTA's until last month...
Then something messed up. Idk...
Now they're forcing the OTA...

You're likely having issues because Google is offering Android 7.1.1 again via OTA and you're likely still on 7.0. Thus flashing a stock image via fastboot is likely a better bet than the OTA, even though doing so will wipe data.

Can I install Android 9 (Nov. patch) over 8.1.0 Unlocked bootloader?

Hi! So a little while ago I unlocked my bootloader, rooted my device, enabled camera2api and installed gcam and modules. Is there any way I can go back to the original 8.1.0 in order to get the OTA updates and get the November patch that comes with andoid 9? Then unlock the bootloader again, enable camera2api and install gcam and modules?
I soft bricked my phone in my first attempt to unlock the bootloader so I decided to ask here for help first

mirunaa said:
Hi! So a little while ago I unlocked my bootloader, rooted my device, enabled camera2api and installed gcam and modules. Is there any way I can go back to the original 8.1.0 in order to get the OTA updates and get the November patch that comes with andoid 9? Then unlock the bootloader again, enable camera2api and install gcam and modules?
I soft bricked my phone in my first attempt to unlock the bootloader so I decided to ask here for help first
Click to expand...
Click to collapse
You don't need to lock bootloader to get OTA updates. Keep it unlocked if you want to get back to stock android.
First uninstall all the Magisk modules you've downloaded. Then flash stock boot.img and system.img (If you've edited build.prop without adb shell). After this you'll be on stock android and you'll get OTA updates.

Where do I find stock boot.img and system.img?
Also, will my phone factory reset after this procedure?

mirunacont said:
Where do I find stock boot.img and system.img?
Also, will my phone factory reset after this procedure?
Click to expand...
Click to collapse
Which version of Oreo are you on? Tell me the build number.
And your phone won't factory reset after this.
---------- Post added at 07:31 PM ---------- Previous post was at 07:23 PM ----------
[email protected] said:
Which version of Oreo are you on? Tell me the build number.
And your phone won't factory reset after this.
Click to expand...
Click to collapse
Download this - https://android.googleapis.com/pack.../f9b27203a7d6dd2c6709f238d9953c6d4e18c04b.zip
Then extract the files and then find the boot.img and system.img. Flash the images from fastboot using -
Code:
fastboot flash boot_a boot.img
fastboot flash boot_b boot.img
fastboot flash system_a system.img
fastboot flash system_b system.img

Extract the Images & Flash Them Individually
you have to flash the system images individually. This method takes some extra work, but it can be used to un-root, update, or un-brick your device without losing existing data.
Start by extracting any additional archives from the factory images package. Sometimes, factory images packages can contain a series of three or four nested archives, so make sure to unzip all of them. From there, copy all of the image files to the main platform-tools folder—in other words, don't leave them in any sub-folders. From here, there are two images that you can get rid of: cache.img and userdata.img. These are the images that will overwrite your data and cache with blank space, so if you don't flash them, your existing data will remain intact.
Of the remaining images, six make up the core elements of Android: boot, bootloader, radio, recovery, system, and vendor.
The boot image contains the kernel, so if you just want to get rid of a custom kernel that's causing issues with your device, you only have to flash this one. To do that, type the following command into the ADB shell window:
fastboot flash boot <boot image file name>.img
Next is the bootloader image—this is the the interface that you're using to flash images with Fastboot commands. So to update your bootloader, type:
fastboot flash bootloader <bootloader image file name>.img
Once you've done that, you should reload the bootloader so that you can continue flashing images on the newer version. To do that, type:
fastboot reboot-bootloader
After that, we have the radio image. This one controls connectivity on your device, so if you're having problems with Wi-Fi or mobile data, or if you just want to update your radio, type:
fastboot flash radio <radio image file name>.img
Then there's recovery. This is something you may or may not want to flash, depending on the modifications you've made. For example, if you've installed TWRP custom recovery, flashing this image will overwrite your modification and replace it with the stock recovery interface. So if you're just updating your modded device, you should skip this one. Otherwise, if you plan to keep your phone stock and want the newer version of stock recovery, type:
fastboot flash recovery <recovery file name>.img
Next up is the big one: The system image. This one contains all of the files that make up the actual Android OS. As such, it's the most essential part of any update.
However you may not be updating your phone. You may just be re-flashing the stock firmware to recover from a soft brick. If this is the case, the system image is often the only image you need to flash in order to fix everything, because it contains the entirety of Android. In other words, if you flash this image and nothing else, it will undo any changes you made with root access and put everything back the way it was.
So as a cure-all in most soft brick situations, or as a method for getting the core part of an Android update, type:
fastboot flash system <system file name>.img
Finally, there's the vendor image. This is only present on newer phones, so don't worry if it's not in your factory images package. But if it's there, it contains a few important files, so type the following line to get this partition updated:
fastboot flash vendor <vendor file name>.img
After you've sent any or all of the above commands, you'll be ready to restart your device and boot into Android. To do that, type:
fastboot reboot.
At this point, your device should be fully updated, or if you were trying to recover from a soft brick, it should be running flawlessly.

Hello everyone
Please i'm in France and would like to upgrade to Pie
When i try nby updater no update appear
i'm on 8.1 with Nov Sec Patch

Nexus 6 stuck in a bootloop on restarting after doing a Factory Image flash

I factory reset my Nexus 6 and unlocked the bootloader to flash the factory images. I flashed these images - lrx21o, mra58k and n6f27m. My phone gets stuck in a bootloop when I restart it. I am able to flash images. But the bootloop on the restart renders the phone useless because there is a battery issue and I need to keep the phone connected to a power source 24/7 when I am using it and even when I'm not.
What could be the issue? How to solve it?
Thanks!

Try formatting data:
fastboot format userdata
This will erase all your files, so make sure to backup first.
I am not sure that it will help, but it is one thing to try.
You can also test if it makes a difference if you remove the sim card.

This usually happens when you are not flashing the latest factory image. Try flashing the latest factory image for Shamu from Google factory image site. And you should be fine. Never flash previous version images if you device was already updated to the latest version, this could be the problem