Related
Hey all,
So I received a notification for a system update to 4.4.3, and I had survival mode in SuperSU checked, so I went ahead and followed the procedure. Turns off, then reboots into TWRP. From there I reboot again using the TWRP option, and it boots into android just fine. Notification is gone, still with root. But then I go to settings >> about to find that I'm still running on 4.4.2. Manually check for update, says there isn't one available. Give it a day or so and the notification comes up again. Repeat, and same thing. I'm stuck with the notification again.
So, how do I get rid of the notification, or more preferably, how to I update to 4.4.3 keeping the root? Thanks.
UnfriendlyTurtle said:
Hey all,
So I received a notification for a system update to 4.4.3, and I had survival mode in SuperSU checked, so I went ahead and followed the procedure. Turns off, then reboots into TWRP. From there I reboot again using the TWRP option, and it boots into android just fine. Notification is gone, still with root. But then I go to settings >> about to find that I'm still running on 4.4.2. Manually check for update, says there isn't one available. Give it a day or so and the notification comes up again. Repeat, and same thing. I'm stuck with the notification again.
So, how do I get rid of the notification, or more preferably, how to I update to 4.4.3 keeping the root? Thanks.
Click to expand...
Click to collapse
You can't update the "normal way" like that with a custom recovery. When you try to do that, it tries to boot into the stock recovery to update, but since you have a custom recovery, it will fail everytime if you do it that way. What you have to do is flash the OTA zip using TWRP. You can find the OTA zip in /cache on your device. Or you can just download the update zip from these forums.
UnfriendlyTurtle said:
Hey all,
So I received a notification for a system update to 4.4.3, and I had survival mode in SuperSU checked, so I went ahead and followed the procedure. Turns off, then reboots into TWRP. From there I reboot again using the TWRP option, and it boots into android just fine. Notification is gone, still with root. But then I go to settings >> about to find that I'm still running on 4.4.2. Manually check for update, says there isn't one available. Give it a day or so and the notification comes up again. Repeat, and same thing. I'm stuck with the notification again.
So, how do I get rid of the notification, or more preferably, how to I update to 4.4.3 keeping the root? Thanks.
Click to expand...
Click to collapse
Since 4.4.4 is out, just download the full firmware package from Google and flash system, boot. Only those two.
If you don't know how to do that, the Nexus 5 forums has some great stickies that are mostly relevant to this device.
charesa39 said:
You can't update the "normal way" like that with a custom recovery. When you try to do that, it tries to boot into the stock recovery to update, but since you have a custom recovery, it will fail everytime if you do it that way. What you have to do is flash the OTA zip using TWRP. You can find the OTA zip in /cache on your device. Or you can just download the update zip from these forums.
Click to expand...
Click to collapse
Right, thanks for the information. So I repeated and booted into TWRP again. Tapped 'Install', navigated to /cache, saw a couple of folders named 'back up', 'lost+found', and then a file name of a large string of letters followed by the recognisable "razor KTU70 from KOT49H", so I went ahead and flashed the latter, checking 'verify signature'. Runs through a few commands and in a few seconds comes back as failed, so I reboot into the OS.
Any ideas?
Aerowinder said:
Since 4.4.4 is out, just download the full firmware package from Google and flash system, boot. Only those two.
If you don't know how to do that, the Nexus 5 forums has some great stickies that are mostly relevant to this device.
Click to expand...
Click to collapse
I think I have an idea, but I'll check just to be sure. Thanks for the direction.
Exactly the same for me. Installing the ota sent me to my TWRP recovery. Reboot - > still in 4.4.2.
Reading this thread, I went to TWRP recovery, installed the update from cache and like you, it failed.
Any suggestions? Did your idea work?
Where do I find the 4.4.4 mentioned here and how do I flash it in TWRP? Is install the same as flash in TWRP?
Thanks.
Anderson2 said:
Exactly the same for me. Installing the ota sent me to my TWRP recovery. Reboot - > still in 4.4.2.
Reading this thread, I went to TWRP recovery, installed the update from cache and like you, it failed.
Any suggestions? Did your idea work?
Where do I find the 4.4.4 mentioned here and how do I flash it in TWRP? Is install the same as flash in TWRP?
Thanks.
Click to expand...
Click to collapse
If it fails look to see what the specific error is. It would help to know that. If you pulled it from your cache then I assume it was downloaded by itself and should be the correct OTA. I do NOT have the "Zip file signature verification." box checked or "Enable MD5 verification of backup files." but I am extremely careful to flash/install the correct files. The OTA installed fine for me two days ago using TWRP 2.7.1.0. The 4.4.4 mentioned earlier is the factory image. You will need adb and fastboot installed on your computer to flash the factory image or any image that is pulled from inside the factory image. Wug's toolkit will work also, I think, but I've never used any toolkits. Eventually there will be a stock 4.4.4 rom that you can flash/install in TWRP but I'm not aware of one right now.
You can take the normal updates with root and TWRP (I did), but a custom kernel will prevent them from installing.
I retried to install the downloaded ota file from cache, but this time I checked zip file verification and got the error message that zip verification failed.
File name was
df43279bcf6bb6a0ae403249c3e6f314d0a7eb77.signed-razor-KTU84L-from-KOT49H.df43279b.zip
So it seems the downloaded ota file may be corrupted. How do I get my Nexus 7 2013 to re-download a new one?
(The ota download for my Nexus 5 installed with no problems - but I think it didn't go through TWRP even though TWRP is installed there too).
Thanks
---------- Post added at 04:05 AM ---------- Previous post was at 03:59 AM ----------
Further
I renamed the ota file and in settings checked for system update and got a response that my system is upto date. But it is still 4.4.2.
Need to re-download the ota. How?
Changed the system date to 2 weeks earlier and succeeded in re-downloading the ota file.
So I retried installing it and it again took me to my TWRP recovery screen. I again installed the ota from cache and again the zip verification failed : 1
And the update failed again.
Still on 4.4.2
Did not change any system files as far as I know.
Need help.
Why don't you guys download the stock firmware from Google (link in my signature), and use fastboot to flash system.img, boot.img (DO NOT run the batch file)? If it's a lack of knowledge, all you need do is ask, and I or someone else would be happy to teach you how to use it (fastboot). If you're going to be modifying your Nexus device, you need to learn fastboot. You guys have got to learn the proper way to do things.
You've put forth so much effort to fix a system that is not meant for modified (rooted, customized) phones. You can't fix it, stop trying. Just do it the proper way. And do not use a toolkit. They don't teach you anything, they spoon-feed.
Aerowinder said:
Why don't you guys download the stock firmware from Google (link in my signature), and use fastboot to flash system.img, boot.img (DO NOT run the batch file)? If it's a lack of knowledge, all you need do is ask, and I or someone else would be happy to teach you how to use it (fastboot). If you're going to be modifying your Nexus device, you need to learn fastboot. You guys have got to learn the proper way to do things.
You've put forth so much effort to fix a system that is not meant for modified (rooted, customized) phones. You can't fix it, stop trying. Just do it the proper way. And do not use a toolkit. They don't teach you anything, they spoon-feed.
Click to expand...
Click to collapse
I don't use a toolkit and would be happy to flash the system.Img and boot.img but need instructions on how to do it. You said the stock firmware link is in your signature but it isn't.
I would like to skip 4.4.3 and go directly from 4.4.2 to 4.4.4. I'm talking about a nexus 7 2013 wifi.
So I need the following information to proceed .
1. The Link to download system.img and boot.img for the nexus 7 2013 wifi. Which files exactly?
2. I have fastboot and adb installed on my windows 7 laptop because I used them (once) to root but I don't remember how I used them that one time. How exactly do I use fastboot to flash 4.4.4 ?
3. I presume I will lose root. How do I regain it after the above.
Thank you.
Anderson2 said:
I don't use a toolkit and would be happy to flash the system.Img and boot.img but need instructions on how to do it. You said the stock firmware link is in your signature but it isn't.
I would like to skip 4.4.3 and go directly from 4.4.2 to 4.4.4. I'm talking about a nexus 7 2013 wifi.
So I need the following information to proceed .
1. The Link to download system.img and boot.img for the nexus 7 2013 wifi. Which files exactly?
2. I have fastboot and adb installed on my windows 7 laptop because I used them (once) to root but I don't remember how I used them that one time. How exactly do I use fastboot to flash 4.4.4 ?
3. I presume I will lose root. How do I regain it after the above.
Thank you.
Click to expand...
Click to collapse
1. The Google firmware link in my signature is the one you want. You say you have the 2013 wifi model, aka flo, aka razor. "Factory Images "razor" for Nexus 7 [2013] (Wi-Fi)" is the proper section for you. You want 4.4.4 (KTU84P), and that's at the bottom of the razor section. Click the link to download.
2. Download the most up to date ADB/Fastboot from the link in my signature (19.0.2 (API 19)). Don't extract it yet.
3. You will lose root. Download SuperSU from my signature. 2.00 is the current version. After you download that, you can put it on your device so you can flash it in recovery in a few minutes.
The firmware you downloaded is razor-ktu84p-factory-b1b2c0da.tgz. This is a compressed archive, and you will need to extract it. If you don't know how, 7-Zip should work.
So, you've extracted the files. Delete flash-all.bat, flash-all.sh, flash-base.sh (so you don't accidentally run them).
Now, all you have left is bootloader-flo-flo-04.02.img and image-razor-ktu84p.zip.
Extract image-razor-ktu84p.zip to the current directory, so you will now have bootloader-flo-flo-04.02.img, boot.img, cache.img, recovery.img, system.img, userdata.img, android-info.txt, image-razor-ktu84p.zip in your folder.
Delete userdata.img, flashing this on accident will wipe your data. Delete image-razor-ktu84p.zip, android-info.txt, cache.img, recovery.img (this is stock recovery, you want TWRP).
Now you have boot.img, bootloader-flo-flo-04.02.img, system.img.
Remember the ADB & Fastboot zip you downloaded from my signature? Extract it to the directory with bootloader-flo-flo-04.02.img, boot.img, system.img. All 4 files. This directory now contains 7 files.
Back out of the razor-ktu84p folder. Just one step back. Now, hold shift the right-click the razor-ktu84p folder. Select Open command window here.
Reboot your device to bootloader mode. Do so by shutting it down. Then while the power is off, hold volume down and press the power button. Release these buttons when you see the big green Android.
In your command window, type the command: fastboot devices
Your device with it's serial number should show up on the list. If it does not there is a problem and you need to stop here.
If the device shows up, let's update it.
fastboot flash bootloader bootloader-flo-flo-04.02.img
<wait for it to finish>
fastboot reboot-bootloader
<wait for it to reboot>
fastboot flash system system.img
<wait for it to finish>
fastboot flash boot boot.img
<wait for it to finish>
fasboot reboot-bootloader
Done with fastboot.
At this point, enter recovery (TWRP) and wipe cache and Dalvik under advanced wipe.
Remember the SuperSU you downloaded earlier and put on your device for later? Flash that now.
Reboot, all done. Most of this is just juggling files around. If you have any questions ask.
You are wonderful aerowinder. This is just what I needed to go ahead. Thank you so much.
About your signature, it doesn't show the links when viewed in my Tapatalk version, but I went to the Web view and got it from there. (just FYI if others ask about your links).
is it possible to just flash the system img in fastboot? It's still the same bootloader, not updated? Could I just flash the whole zip by sideloading in adb and TWRP? Just a lottle confused. Thanks!
droider137 said:
is it possible to just flash the system img in fastboot? It's still the same bootloader, not updated? Could I just flash the whole zip by sideloading in adb and TWRP? Just a lottle confused. Thanks!
Click to expand...
Click to collapse
If you were already on 4.4.3, all you need to do is fastboot flash system.img, that is correct.
No, you can't flash that firmware zip in recovery.
thanks
Hi Aerowinder
Thanks again for the excellent instructions. Everything went like clockwork until it didn't ?......
I got to the point where I issued the command fastboot devices which did show the tablet serial number. But my next command to flash the bootloader img gave me the error:
Cannot open 'bootloader-flo-flo-04.02.img
(I had copy pasted the command from your instructions).
The subdirectory below the command window contains that file (one of 7 files)
Sorry. What should I do?
In case you need the info, the device screen showed
Fastboot mode
Product name - flo
Variant - flo 32G
Hw version - rev_e
Bootloader version - flo-04.02
Carrier info = none
Serial number - xxxx
Signing - yes
Secure boot enabled
Lock state - unlocked
Thanks again.
Aerowinder, you are not only an expert but an excellent teacher. Your instructions above should be a sticky.
I'm all done. Everything is fine.
The problem I had above was a file path problem. Not sure why you told me to open the command window in the parent folder. When I opened it in the folder containing the seven files all your commands worked fine. (Except for your last one where you had a spelling mistake: fasboot instead of fastboot).
Thank you very much.
Hi, I was wondering if someone could make a stock img file of ww 2.13.40.13. I seem to get system errors with the pre-rooted version and it stops me from flashing back to stock with the downloaded stock files (they come as a zip file).
Even if you could send me in the right direction to make one myself, that would be helpful.
Fixed it without the image file.
Just to let others know how,
Connected via ADB and erased system, boot.img and droid_boot.img then reflashed WW versions... All working fine now but was a few hours of frustration and hair pulling... Honestly, I look like Lex Luthor...
Same problem but didn't understand your procedure
Thank you for your solution but I didn't understand
I had the same problem : I rooted my phone by flashing pre-rooted system.img. It worked but now I want to be able to update OTA. So I need to replace pre-rooted system.img with stock one.
Can you please explain how you "erased system, boot.img and droid_boot.img then reflashed WW versions"?
I tried the following : fastboot erase system, fastboot erase cache, and then adb sideload UL-Z00A-WW-2.13.40.13-user.zip with official firmware downloaded from asus.com. But now my phone is blocked on black boot screen "ASUS in search of incredible, powered by android". I can only boot to recovery. Can you repair my phone without wiping data? Thank you.
Not even any clue
So after hours of searches, the only solution I found was to flash a pre-rooted system.img back. My phone boots again normally.
But I don't have any solution to my first problem.
When I try to flash official firmware, I do:
1. In phone recovery menu : apply adb update
2. In PC terminal : adb sideload UL-Z00A-WW-2.13.40.13-user.zip
3. At around 52% transfer, error displayed on phone :
Can't install this package (Wed Apr 1 00:14:20 CST 2015) over newer build (Fri May 29 00:14:18 CST 2015)
E:Error in sideload/package.zip
(Status 7)
Installation aborted.
Has anyone succeeded in getting back to a stock system after flashing a pre-rooted one? I searched in many thread and did not found any solution.
remidem said:
So after hours of searches, the only solution I found was to flash a pre-rooted system.img back. My phone boots again normally.
But I don't have any solution to my first problem.
When I try to flash official firmware, I do:
1. In phone recovery menu : apply adb update
2. In PC terminal : adb sideload UL-Z00A-WW-2.13.40.13-user.zip
3. At around 52% transfer, error displayed on phone :
Can't install this package (Wed Apr 1 00:14:20 CST 2015) over newer build (Fri May 29 00:14:18 CST 2015)
E:Error in sideload/package.zip
(Status 7)
Installation aborted.
Has anyone succeeded in getting back to a stock system after flashing a pre-rooted one? I searched in many thread and did not found any solution.
Click to expand...
Click to collapse
Apparently you can unroot through supersu. This should then allow OTA updates...
Already tried
ultramag69 said:
Apparently you can unroot through supersu. This should then allow OTA updates...
Click to expand...
Click to collapse
No I already tried to unroot via supersu, I have the same issue. As said in thread
http://forum.xda-developers.com/zenfone2/general/asus-zenfone-2-flashing-recovery-mode-t3096596
"If you root via*METHOD 1*you can update SuperSu app as well as update binaries but*PLEASE DON'T apply any OTA updateas the phone*WILL GET STUCK IN A BOOTLOOP...Manually flash the firmware via adb..."
But it is not written how to revert METHOD 1 root.
remidem said:
No I already tried to unroot via supersu, I have the same issue. As said in thread
http://forum.xda-developers.com/zenfone2/general/asus-zenfone-2-flashing-recovery-mode-t3096596
"If you root via*METHOD 1*you can update SuperSu app as well as update binaries but*PLEASE DON'T apply any OTA updateas the phone*WILL GET STUCK IN A BOOTLOOP...Manually flash the firmware via adb..."
But it is not written how to revert METHOD 1 root.
Click to expand...
Click to collapse
From what I did, the pre-root.img was fine to OTA with as long as you don't update supersu... I flashed a pre-root.img on then applied the OTA through a 32gb or FAT32 formatted sd card and it worked fine, also took out root so you will need to put back in there if you want it....
Impossible to update with sdcard
ultramag69 said:
From what I did, the pre-root.img was fine to OTA with as long as you don't update supersu... I flashed a pre-root.img on then applied the OTA through a 32gb or FAT32 formatted sd card and it worked fine, also took out root so you will need to put back in there if you want it....
Click to expand...
Click to collapse
Thank you for your reply. I tried OTA update with sdcard:
1) In Settings/About/Software information, my current version is 2.13.40
2) I dowloaded, from http://forum.xda-developers.com/zenfone2/general/ota-links-stock-rom-t3093999 update from 2.13 to 2.14
3) Copied to external sd, in root folder, and renamed zip to MOFD_SDCARD.zip
4) Rebooted in recovery
5) Update failed. Here is my log:
Finding update package...
I:Update location: /sdcard/MOFD_SDUPDATE.zip
Opening update package...
E:file path:/sdcard/MOFD_SDUPDATE.zip
Installing update...
script aborted: Package expects build fingerprint of asus/WW_Z00A/Z00A:5.0/LRX21V/2.13.40.13_20150401_8390_user:user/release-keys or asus/WW_Z00A/Z00A:5.0/LRX21V/2.14.40.19_20150415_9660_user:user/release-keys; this device has asus/WW_Z00A/Z00A:5.0/LRX21V/2.18.40.12_20150529_9543_user:user/release-keys.
Package expects build fingerprint of asus/WW_Z00A/Z00A:5.0/LRX21V/2.13.40.13_20150401_8390_user:user/release-keys or asus/WW_Z00A/Z00A:5.0/LRX21V/2.14.40.19_20150415_9660_user:user/release-keys; this device has asus/WW_Z00A/Z00A:5.0/LRX21V/2.18.40.12_2015
E:Error in /sdcard/MOFD_SDUPDATE.zip
(Status 7)
SD Installation aborted.
This is because the version of system.img is 2.18 and the fimware version is 2.13.
Indeed I have 2 choices:
- override system with a system.img in version 2.13, but I cannot find any.
- try to apply OTA update 2.17 to 2.18 or 2.18 to 2.19 but it seems risky.
Finally I found!!! I think that a version of the firmware is tagged in system partition and another version (classically the same) is tagged in data partition (this is the one you see in Parameters -> About -> Firmware version). When I wanted to flash a firmware the same version as the one written in parameters (2.13), my phone refused to downgrade because the version of system was higher (2.18). So I had to format the system partition, apply update with official 2.18 firmware. And it worked! My phone was unrooted and I could apply method 3 root.
My issue occurred because I made the following:
1) bought a phone with a 2.13 firware
2) used it for months, applied OTA updates until 2.18
3) flashed a 2.18 pre-rooted system.img
4) used it for weeks until a made an update of supersu
5) my phone couldn't boot any more, so I wiped data (I could avoid that, if I knew!). It made a factory reset, ie get back firmware to 2.13, but system was still in 2.18
Here is the procedure to revert a phone flashed with a pre-rooted system.img (to sell it, send back to warranty, or root with another method):
1) Download official firmware from asus website in the same or higher version of your pre-rooted system.img. Do not rely on version in Parameters -> About -> Firmware version. Or simply download the latest version.
2) In your phone bootloader, enter the following commands with your PC:
fastboot erase system (I'm not sure it is necessary)
fastboot format system
3) With your phone, go into recovery menu, then to "Update with adb"
4) With your PC, go to the directory where you downloaded the firmware as zip, and enter the following command: adb sideload nom_du_fichier_teléchargé.zip
5) It takes about an hour
6) You can reboot
After that I used method 3 to root again, so that I can now OTA update exactly the same way I used to do before rooting. Moreover, I think I can update supersu as well.
tried this method, and it fails with a /sideload/package.zip error using the .18 zip. Trying to unlock as i took the .22 update... root works fine though
wrecklesswun said:
tried this method, and it fails with a /sideload/package.zip error using the .18 zip. Trying to unlock as i took the .22 update... root works fine though
Click to expand...
Click to collapse
Someone said you need to use fastboot to flash droidboot.img, boot.img, system.img and recovery.img to go back to an older version. Not sure if this works as I unlocked bootloader when I had the chance.
If you can't then you might have to wait for the "Official" unlock tool but ASUS will know and you will be out of warranty.
ultramag69 said:
Hi, I was wondering if someone could make a stock img file of ww 2.13.40.13. I seem to get system errors with the pre-rooted version and it stops me from flashing back to stock with the downloaded stock files (they come as a zip file).
Even if you could send me in the right direction to make one myself, that would be helpful.
Fixed it without the image file.
Just to let others know how,
Connected via ADB and erased system, boot.img and droid_boot.img then reflashed WW versions... All working fine now but was a few hours of frustration and hair pulling... Honestly, I look like Lex Luthor...
Click to expand...
Click to collapse
Can you please post the complete steps for the fix! Stuck here for hours, you wouldn't want to look let Lex Luthor
kamranyusuf said:
Can you please post the complete steps for the fix! Stuck here for hours, you wouldn't want to look let Lex Luthor
Click to expand...
Click to collapse
VERY IMPORTANT - Make sure you have checked the MD5 checksum on the boot, droid_boot and recovery image files as these are definitely needed to boot phone. If these are corrupt then you can brick your phone... You have been warned...
Download firmware from here-http://forum.xda-developers.com/zenfone2/orig-development/rom-pre-root-img-t3079590
It is pre-rooted but the other files needed are included in the folder.
2. Put phone in fastboot mode and erased droid_boot.img, boot.img, recovery.img and system.img using command "fastboot erase (put choice here)"
3. Flash the files I just erased back on using fast boot - "
fastboot flash recovery recovery.img
fastboot flash boot boot.img
fastboot flash fastboot droidboot.img
fastboot flash system system.img
This got me the pre-rooted 2.13.40.13. As the supersu has been inserted it is fine to use OTA to update, just make sure you don't update supersu before the OTA flash.
Good luck....
And may you retain a strand or 3 of hair like Homer Simpson....
My phone is the ASUS Zenfone 3 deluxe (zs550kl) model and its bricked only can enter fastboot or adb still but my os will not boot I tried going to asus website for stock firmware (UL-Z018-WW-11.40.71.37-user.zip) and stock kernel (ZS550KL_Kermel_11_40_71_37.zip). how do I install these to fix my phone unless there is a better way to make it boot. by the way im new to android I always had iphone jailbroken until last year I am android now but give me noob instructions for the how to. maybe I should add this I already have adb/fastboot installed and the commands for adb devices or fastboot devices when in fastboot mode both recognize my device so maybe my commands are wrong or something but I tried every way I could toinstill firmware and not sure what to flash kernel as the zip or the file unzipped please help thanks in advance. Not sure why this happened exactly but my bootloader is unlocked already but was never rooted so if there is another way to install another custom firmware besides stock I would like those instructions also thanks again
first off your phone is soft brick meaning all you have to do is flash the stock android software back onto your phone.
install to sd card -> boot into recovery (stock or twrp whatever you have works)
flash from sd
let it load (this will work if you have the correct files)
it will reboot and will work good as new again.
you shouldnt have to flash the kernal, just the UL-Z0 file.
That would have worked yesterday but im having another issue now basically instead of waiting for a response on here I went ahead and did other stuff now my recovery menu is not showing up so I cant install from sd now the only option I'm getting is fastboot so is there a way to fix the stock recovery option or even install a custom recovery which might be eaiser because my bootloader is already unlocked. I was going to try to flash stock recovery my self but not sure how exactly I know I use fastboot flash recovery (recovery file name in the folder) and I think it's .img but not sure so I think it will be either .zip or .img file type but not sure what it will be called if it's stock or custom and not sure where to find either. Last issue I'm not sure of is the actual files I downloaded from asus.com the firmware for my specific phone model not working when I try to flash it as the .zip file so my question is do you need to do something with it such as edit the script of something inside the zip of it and I also downloaded the kernel for my specific phone model from the Asus site and not sure if I needed it when flashing stock rom back to device or how to even flash it on the device please help if you can and I know some questions might be dumb to you but remember I'm a noob when it comes to Android recently left iPhone and I was a pro there every phone had a jailbreak and all types of stuff so I know I can get this just takes time I'm sure
I have this exact issue with a new Padfone Infinity A86... No access to stock recovery, only fast boot... But in my case I'm even unable to flash the recovery.img from a firmware package...
I'm wondering if you guys can help this person, maybe there is something in that solution for my Padfone
1: download the full firmware package
2: use sdat2img to convert the sparse system image to a regular one
3: use fastboot to flash the stock boot.img & the newly converted system.img
4: hoping you didn't flash the recovery partition, if you did, reflash the stock dump from the file in my Bootloader unlock thread via fastboot
5: reboot to recovery & do a factory reset
Read the documentation at each step, do your research, learn the process.
Hi guys, with Google releasing updates so frequently, I was wondering how do you guys keep up with all the new builds? From my understanding, you have to flash the new factory image (through twrp if possible?) so that you get the updated bootloader, radio etc in order to flash the most recent custom roms with the most up to date stock builds.
Is there an easier way rather than constantly wiping everything with each new build flash? I know with One Plus, you can just flash a firmware img file so that you don't have to download and flash such a large file. Does the Pixel have anything similiar?
ZeroSkylineX said:
Hi guys, with Google releasing updates so frequently, I was wondering how do you guys keep up with all the new builds? From my understanding, you have to flash the new factory image (through twrp if possible?) so that you get the updated bootloader, radio etc in order to flash the most recent custom roms with the most up to date stock builds.
Is there an easier way rather than constantly wiping everything with each new build flash? I know with One Plus, you can just flash a firmware img file so that you don't have to download and flash such a large file. Does the Pixel have anything similiar?
Click to expand...
Click to collapse
If I am on a custom ROM and want to update I usually download the latest firmware zip from google and extract the vendor.img and Flash it thru twrp after updating the custom ROM.
ZeroSkylineX said:
Hi guys, with Google releasing updates so frequently, I was wondering how do you guys keep up with all the new builds? From my understanding, you have to flash the new factory image (through twrp if possible?) so that you get the updated bootloader, radio etc in order to flash the most recent custom roms with the most up to date stock builds.
Is there an easier way rather than constantly wiping everything with each new build flash? I know with One Plus, you can just flash a firmware img file so that you don't have to download and flash such a large file. Does the Pixel have anything similiar?
Click to expand...
Click to collapse
Super easy. I'm assuming your bootloader is unlocked and your rooted or else you wouldn't be asking. Let's assume you are running the stock OS, you have TWRP recovery installed, you're rooted with Magisk, and maybe you also have a custom kernel installed. It's the first of the month and Google releases a new security patch. You cannot just take the OTA, nor can you just sideload the smaller OTA due to the custom recovery/root/other customizations. This is what you do, and this is what I do every month:
-Download the newly released FULL factory image from Google's site (NOT the smaller OTA package, the FULL image)
-Unzip the file, open it up, and inside there are multiple files and some zips. One file is a flash-all.bat (for Windows users) along with a flash-all.sh (for Linux/Mac users). Choose the file based on the OS you are using, open it up in a text editor and delete the -w part of the final command string. Be sure to save the file after doing this. This will eliminate the data wipe or essentially dirty flash the entire factory image without wiping your data.
-Reboot into Fastboot mode.
-Run the executable based on your OS. I use Linux, so I simply open a terminal within the files location and run the command "sudo ./flash-all.sh". For Windows you need to move the file to your platform tools folder then execute the flash-all.sh from within that folder as an administrator (double click it and authorize it). On Linux you need not move anything because Linux is ****ing awesome (assuming you have Android-Tools and Android-Udev installed).
-After you flash the entire image and the phone reboots, you simply reboot back into fastboot mode, fastboot boot TWRP, and re-root by flashing Magisk. Or you can fully install TWRP by fastboot booting TWRP, flashing TWRP, then flashing Magisk. If you're running a custom kernel do the same thing, but always flash Magisk last so it repacks the boot image properly.
-Boot back into the OS, and clear data on the Google Playstore. This will reset your Safetynet which was just set back to false after the new update and allow Magisk to continue to do it's thing and keep your device as being Safetynet certified.
-Done. It takes 10 min. and is very easy to do, but yes you do need to download the full 1.7gb FULL factory image. There are ways to do it with the smaller OTA file, but I'm not going to bother because it's useless and it's open to more problems, plus it takes longer and adds several more steps.
-If you are running a custom rom, the steps are a bit different, and in this case you can simply manually flash the desired partitions and eliminate the system image part of the flash. This still requires downloading the full factory image and manually updating the individual partitions that you want update (aka, bootloader, modem, tz, dtbo, etc). You do not run the flash-all script, rather you manually fastboot each partition you want updated. I run stock, so I'll leave these details out for someone else to chime in on. Essentially you are just going to manually flash the desired partitions to be current, but be prepared for breakage if the custom rom is not configured for the new partitions - like a new radio or bootloader.
annoyingduck said:
Super easy. I'm assuming your bootloader is unlocked and your rooted or else you wouldn't be asking. Let's assume you are running the stock OS, you have TWRP recovery installed, you're rooted with Magisk, and maybe you also have a custom kernel installed. It's the first of the month and Google releases a new security patch. You cannot just take the OTA, nor can you just sideload the smaller OTA due to the custom recovery/root/other customizations. This is what you do, and this is what I do every month:
-Download the newly released FULL factory image from Google's site (NOT the smaller OTA package, the FULL image)
-Unzip the file, open it up, and inside there are multiple files and some zips. One file is a flash-all.bat (for Windows users) along with a flash-all.sh (for Linux/Mac users). Choose the file based on the OS you are using, open it up in a text editor and delete the -w part of the final command string. Be sure to save the file after doing this. This will eliminate the data wipe or essentially dirty flash the entire factory image without wiping your data.
-Reboot into Fastboot mode.
-Run the executable based on your OS. I use Linux, so I simply open a terminal within the files location and run the command "sudo ./flash-all.sh". For Windows you need to move the file to your platform tools folder then execute the flash-all.sh from within that folder as an administrator (double click it and authorize it). On Linux you need not move anything because Linux is ****ing awesome (assuming you have Android-Tools and Android-Udev installed).
-After you flash the entire image and the phone reboots, you simply reboot back into fastboot mode, fastboot boot TWRP, and re-root by flashing Magisk. Or you can fully install TWRP by fastboot booting TWRP, flashing TWRP, then flashing Magisk. If you're running a custom kernel do the same thing, but always flash Magisk last so it repacks the boot image properly.
-Boot back into the OS, and clear data on the Google Playstore. This will reset your Safetynet which was just set back to false after the new update and allow Magisk to continue to do it's thing and keep your device as being Safetynet certified.
-Done. It takes 10 min. and is very easy to do, but yes you do need to download the full 1.7gb FULL factory image. There are ways to do it with the smaller OTA file, but I'm not going to bother because it's useless and it's open to more problems, plus it takes longer and adds several more steps.
-If you are running a custom rom, the steps are a bit different, and in this case you can simply manually flash the desired partitions and eliminate the system image part of the flash. This still requires downloading the full factory image and manually updating the individual partitions that you want update (aka, bootloader, modem, tz, dtbo, etc). You do not run the flash-all script, rather you manually fastboot each partition you want updated. I run stock, so I'll leave these details out for someone else to chime in on. Essentially you are just going to manually flash the desired partitions to be current, but be prepared for breakage if the custom rom is not configured for the new partitions - like a new radio or bootloader.
Click to expand...
Click to collapse
Wow this is such a phenomenal post, thank you very much for taking your time to write this! I never smacked that thank button so hard in my life.
I am new to this forum, but have an issue with my Pixel XL that I can't specifically identify, so here I go... I have a Google Pixel XL I purchased from Verizon when they first came out in 2016: (Not sure if the phone is specific to Verizon, was told Google would not let Verizon install thier own firmware). The phone has been pretty good to me. Although I dont think I have had issues with the microphone, Google Hangouts has always been buggy, slow, and crashed. I have kept up the updates, and recently updated to PIE. Google did recommend doing a factory reset over the years which I mistakingly never did due to laziness of not backing up my files. Well, yesterday the unthinkable happened.
While test calling my phone number from another phone, I tried to call Hangouts on my Pixel XL. The phone froze as it usually does. Like a moron I was inattentive and just tried to restart the phone. I got the screen of death that said, "Can't load Android system. Your data may be corrupt. If you continue to get this message, you may need to perform a factory reset and erase all user data stored on this device." I don't want to perform a reset, because I had backup OFF (mistake). It gives me the option to continue, or factory reset. I can't boot into safe mode, but I can go to the screen with the android guy laying on his back, (power button + volume down). Once I select recovery, I get the white screen with google logo, then wait... then I get into the screen with android guy laying on his back with red triangle and exclamation point... Then after holding (Power button then volume up) I can get into the screen with "Reboot system now" "Reboot to bootloader" "Apply update from ADB" "Apply update from SD card" "Wipe data/factory reset" "Mount/system" "View recovery logs" "Run graphics test" "Run locale test" "Power off".... I also downloaded all the files from developers.googledotcom: Factory images, Full OTA images, driver binaries(I think they are correct). Problem is developer mode/usb debugging was not selected at the time of the crash and I obviously cant get into the settings. I am just unclear about which sequence could possibly restore the corrupt file preventing the phone from booting? It seems like I have the necessary usb drivers working, and it seems like my laptop is communicating with my phone while in the command prompt.
I am not very experienced anymore, but I can follow instructions. I just refuse to give up and do a factory reset. I don't care about permanently bricking my phone as it is useless to me with my lost data... CAN ANYONE HELP?? I'm sure there are some forums on here which do explain what to do, but I have searched for a whole day and I cant seem to find a specific one...
RIP 9/11 victims:angel:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
kvas said:
I am new to this forum, but have an issue with my Pixel XL that I can't specifically identify, so here I go... I have a Google Pixel XL I purchased from Verizon when they first came out in 2016: (Not sure if the phone is specific to Verizon, was told Google would not let Verizon install thier own firmware). The phone has been pretty good to me. Although I dont think I have had issues with the microphone, Google Hangouts has always been buggy, slow, and crashed. I have kept up the updates, and recently updated to PIE. Google did recommend doing a factory reset over the years which I mistakingly never did due to laziness of not backing up my files. Well, yesterday the unthinkable happened.
While test calling my phone number from another phone, I tried to call Hangouts on my Pixel XL. The phone froze as it usually does. Like a moron I was inattentive and just tried to restart the phone. I got the screen of death that said, "Can't load Android system. Your data may be corrupt. If you continue to get this message, you may need to perform a factory reset and erase all user data stored on this device." I don't want to perform a reset, because I had backup OFF (mistake). It gives me the option to continue, or factory reset. I can't boot into safe mode, but I can go to the screen with the android guy laying on his back, (power button + volume down). Once I select recovery, I get the white screen with google logo, then wait... then I get into the screen with android guy laying on his back with red triangle and exclamation point... Then after holding (Power button then volume up) I can get into the screen with "Reboot system now" "Reboot to bootloader" "Apply update from ADB" "Apply update from SD card" "Wipe data/factory reset" "Mount/system" "View recovery logs" "Run graphics test" "Run locale test" "Power off".... I also downloaded all the files from developers.googledotcom: Factory images, Full OTA images, driver binaries(I think they are correct). Problem is developer mode/usb debugging was not selected at the time of the crash and I obviously cant get into the settings. I am just unclear about which sequence could possibly restore the corrupt file preventing the phone from booting? It seems like I have the necessary usb drivers working, and it seems like my laptop is communicating with my phone while in the command prompt.
I am not very experienced anymore, but I can follow instructions. I just refuse to give up and do a factory reset. I don't care about permanently bricking my phone as it is useless to me with my lost data... CAN ANYONE HELP?? I'm sure there are some forums on here which do explain what to do, but I have searched for a whole day and I cant seem to find a specific one...
RIP 9/11 victims:angel:
Click to expand...
Click to collapse
Pics wont appear in thread from hosting
Well if you can't get into your system, I'm not sure what choice you have other than to wipe and start again. If USB debugging is off, you can't even pull the files from the phone as far as I know.
I thought I came across a tutorial somewhere that allows USB debugging to be bypassed
Phalanx7621 said:
Well if you can't get into your system, I'm not sure what choice you have other than to wipe and start again. If USB debugging is off, you can't even pull the files from the phone as far as I know.
Click to expand...
Click to collapse
Is there an option to enable USB debugging mode in recovery or through ADB? I can't even remember if I had debugging mode enabled.... My device was shipped through Verizon in Oct 2016, so it is bootloader locked anyway... It seems to be communicating with my laptop in CMD adp sideload, but Im not 100% sure.
it sounds like you can boot into the bootloader and recovery, so you don't need to bother with enabling usb debugging. having usb debugging enabled applies only when the phone is running android. it doesn't affect the recovery or bootloader modes. to verify, boot into the bootloader with power + volume down. you should get the screen with the android guy on his back. connect your phone to a computer via usb, and then run "fastboot devices". fastboot should be in the same folder where adb is. if fastboot returns a device name, it sees your phone and you should be able to sideload a full ota and restore your system. follow step 5 in this guide. [Guide] Pixel XL Android 9.0 (Pie) Unlock/Root/Install Images/Kernels/Recovery
good luck!
Thanks for the reply!
altwu said:
it sounds like you can boot into the bootloader and recovery, so you don't need to bother with enabling usb debugging. having usb debugging enabled applies only when the phone is running android. it doesn't affect the recovery or bootloader modes. to verify, boot into the bootloader with power + volume down. you should get the screen with the android guy on his back. connect your phone to a computer via usb, and then run "fastboot devices". fastboot should be in the same folder where adb is. if fastboot returns a device name, it sees your phone and you should be able to sideload a full ota and restore your system. follow step 5 in this guide. [Guide] Pixel XL Android 9.0 (Pie) Unlock/Root/Install Images/Kernels/Recovery
good luck!
Click to expand...
Click to collapse
I read on another recovery thread for "soft bricked" Pixel XLs that it is possible to not wipe the data by modifying the batch file. To my understanding this involves going to the script and editing it by simply deleting "-w", and saving. Can anyone give me confirmation of this? I don't want to wipe my data, but I am also not clear about some instructions I saw on the Google developers site.... It explains how to apply the OTA through cmd prompt if you dont want to wipe data. Conflicts with some information in this forum. Which option is better? Can someone explain the difference? I know OTA means over the air, but why would Google say to apply this instead of the full factory image in sideload ADB. Since I have corrupt file warning preventing me from booting into the home screen I just want to know what the best option is...
kvas said:
I read on another recovery thread for "soft bricked" Pixel XLs that it is possible to not wipe the data by modifying the batch file. To my understanding this involves going to the script and editing it by simply deleting "-w", and saving. Can anyone give me confirmation of this? I don't want to wipe my data, but I am also not clear about some instructions I saw on the Google developers site.... It explains how to apply the OTA through cmd prompt if you dont want to wipe data. Conflicts with some information in this forum. Which option is better? Can someone explain the difference? I know OTA means over the air, but why would Google say to apply this instead of the full factory image in sideload ADB. Since I have corrupt file warning preventing me from booting into the home screen I just want to know what the best option is...
Click to expand...
Click to collapse
there are 2 methods to flash android to your phone.
flash the factory image. the factory image zip contains a script that takes care of the flashing. it's basically several fastboot commands. to prevent data from getting wiped, the script needs to be edited to remove the -w option from the last fastboot command. the instructions you've seen that mention this are ones for flashing a factory image. but your bootloader needs to be unlocked to do this. since yours isn't, this isn't an option for you.
flash the ota zip. this is done with an adb sideload command. according to google's ota page(http://developers.google.com/android/ota), "This has the same effect as flashing the corresponding factory image, but without the need to wipe the device or unlock the bootloader." unlike flashing a full factory image, no extra steps are needed to prevent data from getting wiped.
i don't think one option is better than the other. some people here prefer to flash the ota, others prefer to flash the full factory image. i've been going with the factory image route ever since nougat and i can confirm that the script edit needed to prevent a data wipe works. but for you, since your bootloader is locked, you have only one option and that's to flash an ota. the instructions for flashing an ota are on google's ota page that i gave a link to or in the guide i mentioned in my previous reply.
Yup, that explains it. I wasn't clear about the instructions of the OTA method because on the developers site for Google it both talks about sideloading and enabling usb debugging in the options menu. Since I can't access my setting because my phone is soft bricked I have to use sideloader through the ADB. What I am also not clear on is the OTA for my situation. I gathered that the OTA flash was for Pixels that wouldnt take and update in a non-soft bricked phone. At this point I have no choice but to try. I talked to someone at Google and he sat on the phone for over an hour and a half with me helping me research this method. (THANKS GOOGLE))). Although I read that after the last Pie update many peoples phones became bricked so at least it shows they care. I just hope the OTA flash is provisioned for a soft bricked device. But in this business I realize nothing is guaranteed. I just wish I could locate someone who tried this on thier device so they could give some pointers....
We can all agree, if your phone is bootloader LOCKED do not do a factory flash if attempting to retain any data. Editing the script (-W) will only work with a bootloader UNLOCKED device. Long live the Pixel
Now this just gets stranger and stranger... I tried loading the OTA file from sideloader. It reads my device just fine (adb devices)... but when I type adb sideloader <space> (filename) it says it cannot locate the file? I copied and pasted the file to the folder wehre adb.exe is. Cannot locate file, but device is located with no issues in the cmd. What am I doing wrong?
kvas said:
Now this just gets stranger and stranger... I tried loading the OTA file from sideloader. It reads my device just fine (adb devices)... but when I type adb sideloader <space> (filename) it says it cannot locate the file? I copied and pasted the file to the folder wehre adb.exe is. Cannot locate file, but device is located with no issues in the cmd. What am I doing wrong?
Click to expand...
Click to collapse
1) Is the Full OTA that you downloaded from Google in the same file directory on your computer as ADB.EXE?
2) Are you typing in the file name properly? Might be easier to rename it to something easier / shorter than the default that is downloaded from Google. (or you can drag/drop the file to your cmd window which will cut/paste the file name and proper path)
3) are you using proper syntax? Your sentence above says "adb sideloader <space> (filename)"....but the command is "adb sideload" (not sideloadER)
4) Within your command window, are you in the directory containing your adb.exe and ota.zip? Depending on how you launched the cmd window, you might need to change directory (cd) to the right path/folder...
from Google page:
Run the following command:
adb sideload ota_file.zip
where ota_file.zip is the name of the file you have downloaded and verified.
Good luck.
in addition to what @sb1893 suggested, did you download the correct ota zip file? the latest ota zip is marlin-ota-ppr2.180905.006.a1-34e91bd3.zip. ota zip files for the pixel xl start with marlin-ota. factory images have the word factory as part of the name. if the zip you downloaded has factory in the name and not ota, you have the wrong file. if you have the correct ota zip file, don't touch it. you don't need to unzip it. this zip file is what you will sideload. also verify that the checksum matches the value that google published.
i understand your confusion about enabling usb debugging. the instructions on the google ota page say to enable it but that's only just to be able to run the adb command to reboot into recovery. usb debugging only applies to when the phone is running android. it doesn't affect the recovery or bootloader modes. if your phone is in recovery or bootloader mode and you have the correct device drivers, your computer should be able to see your phone even if usb debugging is disabled. since you can't boot into android, you need an another way to get into recovery mode and that's with power + volume down to get to the bootloader and enter recovery from there.
altwu said:
in addition to what @sb1893 suggested, did you download the correct ota zip file? the latest ota zip is marlin-ota-ppr2.180905.006.a1-34e91bd3.zip. ota zip files for the pixel xl start with marlin-ota. factory images have the word factory as part of the name. if the zip you downloaded has factory in the name and not ota, you have the wrong file. if you have the correct ota zip file, don't touch it. you don't need to unzip it. this zip file is what you will sideload. also verify that the checksum matches the value that google published.
i understand your confusion about enabling usb debugging. the instructions on the google ota page say to enable it but that's only just to be able to run the adb command to reboot into recovery. usb debugging only applies to when the phone is running android. it doesn't affect the recovery or bootloader modes. if your phone is in recovery or bootloader mode and you have the correct device drivers, your computer should be able to see your phone even if usb debugging is disabled. since you can't boot into android, you need an another way to get into recovery mode and that's with power + volume down to get to the bootloader and enter recovery from there.
Click to expand...
Click to collapse
And one final thing I forgot to mention. Platform Tools had an update this month...so please make sure you have downloaded and are running the latest versions...
28.0.1 (September 2018) is the latest revision for the Platform tools SDK
sb1893 said:
1) Is the Full OTA that you downloaded from Google in the same file directory on your computer as ADB.EXE?
2) Are you typing in the file name properly? Might be easier to rename it to something easier / shorter than the default that is downloaded from Google. (or you can drag/drop the file to your cmd window which will cut/paste the file name and proper path)
3) are you using proper syntax? Your sentence above says "adb sideloader <space> (filename)"....but the command is "adb sideload" (not sideloadER)
4) Within your command window, are you in the directory containing your adb.exe and ota.zip? Depending on how you launched the cmd window, you might need to change directory (cd) to the right path/folder...
from Google page:
Run the following command:
adb sideload ota_file.zip
where ota_file.zip is the name of the file you have downloaded and verified.
Good luck.
Click to expand...
Click to collapse
altwu said:
in addition to what @sb1893 suggested, did you download the correct ota zip file? the latest ota zip is marlin-ota-ppr2.180905.006.a1-34e91bd3.zip. ota zip files for the pixel xl start with marlin-ota. factory images have the word factory as part of the name. if the zip you downloaded has factory in the name and not ota, you have the wrong file. if you have the correct ota zip file, don't touch it. you don't need to unzip it. this zip file is what you will sideload. also verify that the checksum matches the value that google published.
i understand your confusion about enabling usb debugging. the instructions on the google ota page say to enable it but that's only just to be able to run the adb command to reboot into recovery. usb debugging only applies to when the phone is running android. it doesn't affect the recovery or bootloader modes. if your phone is in recovery or bootloader mode and you have the correct device drivers, your computer should be able to see your phone even if usb debugging is disabled. since you can't boot into android, you need an another way to get into recovery mode and that's with power + volume down to get to the bootloader and enter recovery from there.
Click to expand...
Click to collapse
sb1893 said:
And one final thing I forgot to mention. Platform Tools had an update this month...so please make sure you have downloaded and are running the latest versions...
28.0.1 (September 2018) is the latest revision for the Platform tools SDK
Click to expand...
Click to collapse
You guys make the XDA community look good.
kudos to each of you.
Update: completed all necessary steps properly (also never actually typed command adb sideloadER before, was just a typo). I am getting a "protocol fault (no status)" when I hit enter. On my Pixel, it says "Must update to adb 1.0.32 or higher" So I located the file here on XDA. I downloaded the file and pasted in the same folder of all the other files. I found I was using the wrong path before. I will try again and see what happens. Still not sure if I extract these files.
UPDATE:
Phone took the sideload OTA just fine. Update was sucessful. Unfortunatley I still cant get into my home screen. It did not work. Still getting screen that says "Your data may be corrupt". We can safely say OTA flash will not fix this type of problem. I should have unlocked the bootloader right when I got the phone. Never again am I purchasing a Google product. Ever again. Time to get a Samsung note 9. I'm sorry, but if you pay 1000 dollars for a phone like I did barely 2 years ago it should not have this problem. Lesson learned: Backup your data to a cloud. Google is still a great company but thier phones are junk. I also had screen burn after less than 1 year, but I have that on my LG v10. Goodbye Pixel, forever.
kvas said:
Update: completed all necessary steps properly (also never actually typed command adb sideloadER before, was just a typo). I am getting a "protocol fault (no status)" when I hit enter. On my Pixel, it says "Must update to adb 1.0.32 or higher" So I located the file here on XDA. I downloaded the file and pasted in the same folder of all the other files. I found I was using the wrong path before. I will try again and see what happens. Still not sure if I extract these files.
UPDATE:
Phone took the sideload OTA just fine. Update was sucessful. Unfortunatley I still cant get into my home screen. It did not work. Still getting screen that says "Your data may be corrupt". We can safely say OTA flash will not fix this type of problem. I should have unlocked the bootloader right when I got the phone. Never again am I purchasing a Google product. Ever again. Time to get a Samsung note 9. I'm sorry, but if you pay 1000 dollars for a phone like I did barely 2 years ago it should not have this problem. Lesson learned: Backup your data to a cloud. Google is still a great company but thier phones are junk. I also had screen burn after less than 1 year, but I have that on my LG v10. Goodbye Pixel, forever.
Click to expand...
Click to collapse
Bummer - that stinks. Sounds like we are close. Out of curiousity - can you post the exact/full text (or a picture if you have a camera or second device) of that screen that shows "Your data may be corrupt"...the only "corrupt" message I am familiar with is from the Bootloader unlocked warning screen. So - want to see what specific error message you are getting.
Sorry again you weren't able to recover your device.
I tried to post a all the pictures I have taken, but the hosting site wont show them. Is there a better way to show the pics?
I just attach pics using the reply screen...Like this....
sb1893 said:
I just attach pics using the reply screen...Like this....
Click to expand...
Click to collapse
Hopefully this works... Google Pixel XL flashing OTA
kvas said:
Hopefully this works... Google Pixel XL flashing OTA
Click to expand...
Click to collapse
So you power up the device and it works on booting for a little while and then immediately drops you into that recovery screen? It doesn't give you a message when the boot fails before launching recovery?
Also - that OTA file looks to be the August 2018 OTA file, not September 2018 - which is what I thought you were trying to sideload...
I did end up flashing the latest OTA.. It let both of them install. I flashed the same one on my phone, then I flashed the newest on on the list of google developers site. PPR2. 180905.006.A1. That is what is has now. I am still stumped as to why it won't work. I'm sure it needs a full factory flash, but I cant do it because its locked. So even if I wanted to recover the files I can't. Even if I could recover the files somehow without further flashing the files would be encrypted and useless. I could either wait to see if another option is available in the future, or factory reset it losing all my precious files. Extremely frustrating. Also, Why didnt google send me a notice about the September update? I never updated this month. Probably why it froze while in Hangouts