Database Users

KindleFire Partitions error? [Still not fixed]

When I flashed a kernel I did boot boot.img first and it worked so I did flash boot boot.img with fastboot. Well that didn't work. So I just got the other boot.img for cm7 and tryed to do that. Well I got this error:
C:\adb>fastboot flash boot boot.img
sending 'boot' (3196 KB)... OKAY [ 0.875s]
writing 'boot'... FAILED (remote: partition does not exist)
finished. total time: 0.885s
When a wipe is issued:
C:\adb>fastboot -w
erasing 'userdata'... FAILED (remote: : partition doesn't exist)
finished. total time: 0.002s
I am in fastboot but I can not get into twrp2 because when I hold down the power button to enter recovery it just turns amber and just hangs. I do have some mmcblk0pXX .img's if it helps.

I think I'm having the same problem. When I try to boot the bootnew.img for intersectRaven's kernel, it hangs at the FIREFIREFIRE yellow triangle with an amber light. No fastboot commands will take me out of it. If it makes a difference, I installed the custom WiFi driver.

Thats the exact same thing is for me.

TyHi said:
Thats the exact same thing is for me.
Click to expand...
Click to collapse
I guess we're in the same boat then. I think my problem came from booting the kernel up, then installing the custom wifi driver, then trying to boot it up again.

When I flashed a kernel I did boot boot.img first and it worked so I did flash boot boot.img with fastboot. Well that didn't work. So I just got the other boot.img for cm7 and tryed to do that. Well I got this error:
C:\adb>fastboot flash boot boot.img
sending 'boot' (3196 KB)... OKAY [ 0.875s]
writing 'boot'... FAILED (remote: partition does not exist)
finished. total time: 0.885s
I am in fastboot but I can not get into twrp2 because when I hold down the power button to enter recovery it just turns amber and just hangs. I do have some mmcblk0pXX .img's if it helps.
Click to expand...
Click to collapse
Did you follow precisely the commands given here? It sounds like you did, but I just wanted to make sure. I was going to suggest you reset the bootmode to 4000. Have you already tried that?

rwphwp said:
Did you follow precisely the commands given here? It sounds like you did, but I just wanted to make sure. I was going to suggest you reset the bootmode to 4000. Have you already tried that?
Click to expand...
Click to collapse
Since apparently the OP and I have the same problem, yes I tried that. The command "fastboot -i 0x1949 oem idme bootmode 4000" doesn't work for me. It just boots into fastboot again.

I read someplace when I rooted 6.2.1 with perhaps a Burrito Root prog. The recommended order to get CM7 and TWRP . Is to go - in this order. Root, then TWRP AND lastly update.zip to sdcard for install of CM7. I made space avail. for TWRP'S Backup ( STRONGLY RECOMMEND ) BACKUP. ======which saved me a few times already on a couple frozen boots. Cause I experiment with various launchers, I think.

Yes I have. It just hangs on the yellow boot with a green light.

Smmoph said:
I read someplace when I rooted 6.2.1 with perhaps a Burrito Root prog. The recommended order to get CM7 and TWRP . Is to go - in this order. Root, then TWRP AND lastly update.zip to sdcard for install of CM7. I made space avail. for TWRP'S Backup ( STRONGLY RECOMMEND ) BACKUP. ======which saved me a few times already on a couple frozen boots. Cause I experiment with various launchers, I think.
Click to expand...
Click to collapse
The thing is that I cant even root it. It is just stuck it at boot screen for FIREFIREFIRE v1.0.

Smmoph said:
I read someplace when I rooted 6.2.1 with perhaps a Burrito Root prog. The recommended order to get CM7 and TWRP . Is to go - in this order. Root, then TWRP AND lastly update.zip to sdcard for install of CM7. I made space avail. for TWRP'S Backup ( STRONGLY RECOMMEND ) BACKUP. ======which saved me a few times already on a couple frozen boots. Cause I experiment with various launchers, I think.
Click to expand...
Click to collapse
I suck at pushing buttons on forums now (hence the accidental thank), but I'm not really trying to install CM7.

Have you tried the hard reset? Hold power button for app. 18 seconds till screen goes totally dark, then press power bttn on again, once.

Yes I have many times.

I can suggest changing the driver on usb in pc or rebboot pc after uninstall and the change it . But I wanted to show a procedure. win utility 7 gave me the necc. usb driver v. 6 did not have.

TyHi said:
Yes I have. It just hangs on the yellow boot with a green light.
Click to expand...
Click to collapse
Gotcha. Any luck with this method?

There was also A kindlefire utility v.? with an option in red for "factory reset" on the device, perhaps.

rwphwp said:
Gotcha. Any luck with this method?
Click to expand...
Click to collapse
Yes I have. Can't even do adb push. When I get into adb with using boot boot.img from cm7. I get, exec /system/bin/sh' failed no file or directory.

I would not give in, but try to stay calm with all methods to reclaim functionality. I started with rootwiki and Jayce Ooi's And Burrito in order to stay clear of CMD console cause I was not even recognised till Win_usb drivers eventually fell in place. Saw some stuff about editing path's also. Reading alot helped.

I'd join IRC and see what we can accomplish there. You all are all over the place, and some of you aren't even bricked at all.

Vashypooh said:
I'd join IRC and see what we can accomplish there. You all are all over the place, and some of you aren't even bricked at all.
Click to expand...
Click to collapse
I was in there all day, and I never got a working solution.

TheMagicPancake said:
I was in there all day, and I never got a working solution.
Click to expand...
Click to collapse
Join there ~12:45-1am EST, ill be available to help then.

Android 4.3 image errors

Hey guys, I'm currently trying to flash back to the new 4.3 factory image that I downloaded from Google, however, it all goes fine, I flashed the bootloader, flashed the radio and it all says it has been updated properly, then when I try and flash the system.img files and boot.img files they just say no such file or directory exists and stops, meaning the phone is unusable at the moment until I flash something.
Anyone know why this is happening?
BTW I'm using a mac.
Issue fixed, see below!
************************************************************************************************
Ok guys, the problem was solved in an odd way!
I got annoyed with the flashing errors, and flashed the old kernel and radio I was using with my Illusion rom which thankfully got me back to that even though I had lost all of my data (backed up though).
For anyone having this problem and wants to unroot to go back to 4.3 or is trying to flash the legit 4.3 rom from Google and then maybe unroot or just use the 4.3 rom direct from Google...
DOWNLOAD THE LEAKED 4.3 ROM AND FLASH USING STANDARD CWM METHOD.
DOWNLOAD THE .84/.83 KERNEL AND FLASH THIS AS WELL.
After this I got the legitimate OTA update which was only 3.4mb and it even fixed root so I am now back to complete stock, locked bootloader and no root!
Hope this helps
Click to expand...
Click to collapse

Easiest way of flashing the system image is to just use the flash-all script included in the TGZ - just extract it out and run it when the phone is connected in fastboot mode. Personally, I do the following:
1. Extract the entire TGZ (including the update.zip)
2. Move all the IMG files into one folder
3. Rename them to easy names, e.g. bootloader, radio, system, userdata, boot, recovery, etc.
4. Flash them all in turn, rebooting the bootloader each time
5. Once all done, erase/format the cache (fastboot erase cache and fastboot format cache)
6. Boot into recovery and clear cache again and then do a factory reset (this makes sure the unit see all the internal memory)
7. Reboot the phone
Should all work now

siravarice said:
Hey guys, I'm currently trying to flash back to the new 4.3 factory image that I downloaded from Google, however, it all goes fine, I flashed the bootloader, flashed the radio and it all says it has been updated properly, then when I try and flash the system.img files and boot.img files they just say no such file or directory exists and stops, meaning the phone is unusable at the moment until I flash something.
Anyone know why this is happening?
BTW I'm using a mac.
Click to expand...
Click to collapse
Maybe you have corrupted files? Retry the download from google and unpack all with 7zip.
I did that yesterday and all works fine.
4.3 (JWR66V)
https://dl.google.com/dl/android/aosp/occam-jwr66v-factory-08d2b697.tgz
7zip
http://www.7-zip.de/
[HOW-TO] How to flash a factory image / return to stock / unlock / root #
http://forum.xda-developers.com/showthread.php?t=2010312

EddyOS said:
Easiest way of flashing the system image is to just use the flash-all script included in the TGZ - just extract it out and run it when the phone is connected in fastboot mode
Click to expand...
Click to collapse
How would I do that on a mac? I tried typing:
./fastboot flash flash-all.bat
but do I need to use the .sh version?

info.brandenburg said:
Maybe you have corrupted files? Retry the download from google and unpack all with 7zip.
I did that yesterday and all works fine.
Click to expand...
Click to collapse
Did that, same thing happened. I tried flashing the entire .zip and then I tried separately and it still didn't work.

Ok so I know it is just the system.img file that doesn't work, as all the other files have just flashed fine! Going to re-download and see if that helps.

siravarice said:
How would I do that on a mac? I tried typing:
./fastboot flash flash-all.bat
but do I need to use the .sh version?
Click to expand...
Click to collapse
You just run the script, you don't flash it. It's a batch file which then does all the fastboot commands. You also use flash-all.sh as you don't have Windows

EddyOS said:
You just run the script, you don't flash it. It's a batch file which then does all the fastboot commands. You also use flash-all.sh as you don't have Windows
Click to expand...
Click to collapse
Still doesn't work.
I used: bash flash-al.sh
And it just said fastboot not found in certain lines for the command and did nothing. I thought it fixed itself when I swapped USB ports but when it got to the system.img it just gave me the same error again. It flashes everything else ok but not this file, it's the third time I have downloaded it and now I have no way to get it back to being useable as when I press start it just gives me a black screen
HELP PLEASE!

I would but I use Windows and it's all fine. Might be worth downloading the factory image again, checking the md5 and trying to flash the system image again

EddyOS said:
I would but I use Windows and it's all fine. Might be worth downloading the factory image again, checking the md5 and trying to flash the system image again
Click to expand...
Click to collapse
Im trying to install some Samsung Android Drivers on my old laptop but the thing is so slow it's basically impossible to work from now
I've redownloaded the files, I don't know how to check the MD5Sum though. Still nothing doing. I get this error:
checking product... OKAY
checking version-bootloader... OKAY
checking version-baseband... OKAY
sending 'boot' (6166 KB)... OKAY
writing 'boot'... OKAY
sending 'recovery' (6664 KB)... OKAY
writing 'recovery'... OKAY
sending 'system' (531281 KB)... ERROR: usb_write failed with status e00002be
FAILED (data transfer failure (No such file or directory))
edue3e4:4.2unrootnexus4 Simon$
It really doesn't want to write the system.img file, or maybe it doesn't want to write to system?

What happens if you extract the system.img file and flash it via fastboot manually?
fastboot flash system system.img
I always use this guide if I forget:
efrant said:
D. Type in the commands into the command prompt
1) Make sure your computer recognizes your device by typing: fastboot devices
2) Unlock your bootloader (if you have not already done so): fastboot oem unlock
3) You will see a prompt on your device. This will wipe your entire device (including the /sdcard folder). Accept. Note: you use the volume keys to change the option and the power button to accept. You cannot use the touch screen.
4) Reboot by typing: fastboot reboot-bootloader
5) Flash the bootloader: fastboot flash bootloader bootloader-mako-makoz10o.img (or whatever the name of the bootloader image that you downloaded).
6) Reboot: fastboot reboot-bootloader
7) Flash the radio: fastboot flash radio radio-mako-m9615a-cefwmazm-2.0.1700.48.img (or whatever the name is of the radio image that you downloaded).
8) Reboot: fastboot reboot-bootloader
9) Flash the system partition: fastboot flash system system.img
10) Flash the data partition: fastboot flash userdata userdata.img Note: this command will wipe your device (including /sdcard), EVEN if your bootloader is already unlocked. See note 2 below.
11) Flash the kernel/ramdisk: fastboot flash boot boot.img
12) Flash the recovery partition: fastboot flash recovery recovery.img
13) Erase the cache partition: either a) fastboot erase cache OR b) fastboot format cache <<== the second option seems to work better for most people. Thanks joostburg.
14) Reboot: fastboot reboot
15) Done! The first boot will likely take quite a bit longer than you are used to, as Android builds the Dalvik cache.
Now you have a fully stock image on your device. The only thing that is different from out-of-the-box condition is that your bootloader is unlocked. See the notes section at the end of this post for information on re-locking the bootloader.
Note that some users indicate that they can't get past the X on boot. If this happens to you, reboot into the bootloader and select recovery. Then, when you see the Android with the red exclamation mark, hold power and press volume up to take you to the menu. Wipe cache. If that still doesn't work, boot back into recovery and do a factory reset.
If you have a 16GB device, and it now shows up as 8GB, reboot into recovery (hold power and press volume up when you are at the screen with the android and the red exclamation mark), and wipe cache. If that still doesn't work, boot back into recovery and do a factory reset. Or do this
Click to expand...
Click to collapse

EddyOS said:
What happens if you extract the system.img file and flash it via fastboot manually?
fastboot flash system system.img
I always use this guide if I forget:
Click to expand...
Click to collapse
That's exactly what I have been doing, I prefer doing it manually as I don't like using Toolkits and finding a good one for mac is hard enough.
It just says that it cannot send it because the file or directory does not exist, yet if I unplug the phone it does go back into my old rom I was using before that, even though I flashed a new radio and recovery.img, boot.img, user data.img, everything except system.img as it doesn't work

Something clearly wrong with the partition but no idea what...

I know right, I've gone back to the ROM I had previously and downloaded the leaked 4.3 rom and flashed it through flashify. If it works I will simply lock the bootloader again and it should be good to go!

i did the same way through nexus tool kit 2.0 n p.s i guess the file was corrupted that y it failed in the mid. ill try it again

Hmmy 4444 said:
i did the same way through nexus tool kit 2.0 n p.s i guess the file was corrupted that y it failed in the mid. ill try it again
Click to expand...
Click to collapse
Let me know if you get anywhere with it!

it worked.. jst copy the image n dont rename it n go to google nexus 4 toolkit folder n there u would see a folder named *put googlr factory image here* paste it there n before starting ur bootloader must be unlocked.. so thats that.. after that that open the nexus 4 toolkit n then click on number 9 whch says download extract + flash google factore stock rom n then after that type 2 whch says flash google factory image... n thats it. it will automatically flash it.... gv me thanks too
Sent from my Nexus 4 using xda app-developers app

Hi there, same issue with me on a mac
Plus can you tell me how you went back to the previous rom, my phone is unusable right now and i do have a nandroid backup so.

Have either of your tried to flash the 4.2.2 factory image? Would be interested to see if it works
Sent from my Nexus 4 using xda premium

EddyOS said:
Have either of your tried to flash the 4.2.2 factory image? Would be interested to see if it works
Sent from my Nexus 4 using xda premium
Click to expand...
Click to collapse
I dont mind, can you direct me towards a post where they show how to, i m not sure of all this and dont want to mess around with wrong files.
UPDATE: I tried and that works just fine. Rebooted to 4.2.1

Help - I'm stuck in a bootloop 4 circles !

Hi I just tried to flash Android 4.4.4 without wiping & losing root using Nexus Root Toolkit
as per this link trendblog.net/flash-android-4-4-4-without-wiping-and-loosing-root/
I had slimkat 4.4.4 and tried to put stock 4.4.4 on this
After success messages the toolkit told me to wait for it to boot up but I am stuck on the four circles.
I have no recovery !!!
What can i do ?

Stop using took kits. They're nothing but trouble. Flash the factory image in fastboot and start over
Sent from my SAMSUNG-SGH-I727 using XDA Free mobile app

Yes I know I've been foolish to use a kit
Please can you tell me what I need and the steps to do this ?

k500zm said:
Yes I know I've been foolish to use a kit
Please can you tell me what I need and the steps to do this ?
Click to expand...
Click to collapse
First Google 15 second adb install xda. That'll set up fastboot on your PC. Then download the factory image. Google nexus 4 factory image. Extract that using 7-zip or winrar. In there is a flash-all.bat. just double click it. It will wipe your device so backup off the device first
Sent from my SAMSUNG-SGH-I727 using XDA Free mobile app

k500zm said:
Yes I know I've been foolish to use a kit
Please can you tell me what I need and the steps to do this ?
Click to expand...
Click to collapse
Here is an excellent guide how to use fastboot:
http://forum.xda-developers.com/showthread.php?t=1907796
It is guide for Nexus 7, but the proceeding is just identic like with all other Nexus devices.
tetakpatalked from Nexus 7 flo

Thanks guys. I am in a bit of a panic here.
couple of questions
If my usb is connected will the nexus 4 take power from it so my battery will not drain completely ?
Also is it possible to get my files from the device before I wipe ?
I never used fastboot before - but I'm gonna learn fast now !

k500zm said:
Thanks guys. I am in a bit of a panic here.
couple of questions
If my usb is connected will the nexus 4 take power from it so my battery will not drain completely ?
Also is it possible to get my files from the device before I wipe ?
I never used fastboot before - but I'm gonna learn fast now !
Click to expand...
Click to collapse
You say you can't boot into recovery? That's going to be a problem retrieving data
Sent from my SAMSUNG-SGH-I727 using XDA Free mobile app

Is there no way to get cwm back on there ?

k500zm said:
Is there no way to get cwm back on there ?
Click to expand...
Click to collapse
Maybe, you'll need fastboot for that too. Download the latest image file from here. Rename it recovery
http://techerrata.com/browse/twrp2/mako
We'll go from there. You're going to learn a lot more than you bargained for
Sent from my SAMSUNG-SGH-I727 using XDA Free mobile app

k500zm said:
Thanks guys. I am in a bit of a panic here.
couple of questions
Click to expand...
Click to collapse
If my usb is connected will the nexus 4 take power from it so my battery will not drain completely ?
Click to expand...
Click to collapse
Correct, but I'm not sure for the bootloader mode. I don't own a N4. Rather charge your battery first, it should work.
Also is it possible to get my files from the device before I wipe ?
Click to expand...
Click to collapse
If you're lucky, ADB might work even in bootloop if USB debugging was enabled in the developer options. As you didn't wipe, there is a small chance ADB pull might work.
IMHO the best you can do is to flash any custom recovery like TWRP or PhilZ with fastboot. The recovery.img file must be saved in the same folder where fastboot.exe is.
I assume Google USB driver is properly installed?
Fastboot must work, check in the guide I posted link for in my first post here how to check that fastboot commands are working. If "fastboot devices" returns "(your N4 serial No) fastboot" and your custom recovery is saved in proper folder, enter in CMD:
Code:
fastboot erase recovery
fastboot flash recovery recovery.img
After that, enter recovery mode, there is another chance your ADB pull function might work. The phone should charge in recovery mode.
To install SlimKat again, format: system, data, cache, dalvik cache (TWRP) or choose factory reset and "clean to install new ROM" in PhilZ. Then flash ROM and Gapps, best with ADB sideload.
tetakpatalked from Nexus 7 flo

Ok I'm all ears and eager to learn
Ok downloaded - renamed to 'recovery.img'

k500zm said:
Ok I'm all ears and eager to learn
Ok downloaded - renamed to 'recovery.img'
Click to expand...
Click to collapse
Did you install fastboot with the 15 second adb install?
Sent from my SAMSUNG-SGH-I727 using XDA Free mobile app

I have installed Android SDK manager and the 15 sec drivers

I have android bootloader interface in my xp device manager

k500zm said:
I have installed Android SDK manager and the 15 sec drivers
Click to expand...
Click to collapse
OK, we'll try with that. Put your recovery image in the same folder as fastboot.exe. Open a command window in that folder, shift right mouse click in a open area in that folder
Plug your device into the USB port. Type
fastboot devices (return) in the cmd window
Is your device recognized? If it is then in the cmd window type
fastboot flash recovery recovery.img
Sent from my SAMSUNG-SGH-I727 using XDA Free mobile app

ok - this is what I got...
C:\adb>fastboot devices
fastboot
C:\adb>fastboot flash recovery recovery.img
sending 'recovery' (7928 KB)...
OKAY [ 0.250s]
writing 'recovery'...
OKAY [ 0.453s]
finished. total time: 0.703s
C:\adb>

Ok I have TWRP started on my device [ i use cwm though will my nandroid backup be compatible with twrp ?]

k500zm said:
ok - this is what I got...
C:\adb>fastboot devices
01...... fastboot
C:\adb>fastboot flash recovery recovery.img
sending 'recovery' (7928 KB)...
OKAY [ 0.250s]
writing 'recovery'...
OKAY [ 0.453s]
finished. total time: 0.703s
C:\adb>
Click to expand...
Click to collapse
That sounds excellent, mate! Now try to reboot into the recovery mode
BTW: it isn't recommended to write down your device's serial No in worldwide public forum, it is your privacy in fact. Best edit your post now and remove big part of it (I also did it im my quote of your post)
tetakpatalked from Nexus 7 flo

k500zm said:
Ok I have TWRP started on my device [ i use cwm though will my nandroid backup be compatible with twrp ?]
Click to expand...
Click to collapse
Good job. The nandroid won't be compatible. Let me see if I can find a cwm image. Now that you know how to use fastboot
Sent from my Nexus 5 using XDA Free mobile app

I have a nandroid backup from cwm just before i fcud up - is there any way to restore this ?
Thanks for your help so far geezers

Will not boot after root

So I followed the XDA guide on rooting. After getting back to the setup screen, I constantly got:
Unfortunately, the process com.google.process.gapps has stopped.
It was literally constant to the point where I could only type one letter at a time. Okay, so I tried factory reset via TWRP. No good. So I downloaded a factory image and tried to flash it, and now my phone sits at the Google/padlock screen forever.
What do I do? I still have fastboot and TWRP access. I'm not sure the images are completely copying to the Nexus when I try to put them directly on the phone. Using Google's image and flash-all command ends in:
writing 'system'...
FAILED (remote: unknown command)
I don't understand this. Please help me. I can't use my phone at all.

Are you unlocked? Can you fastboot flash?

I can, yes. I figured out at least part of my problem - the USB 3 port on my laptop is misbehaving somehow. The USB 2 port works. I was able to fastboot flash. It remains to be seen why I had the gapps issue originally...

May Images are up.

May images are available.

This one is interesting:
- Adjust Pixel XL charging behavior
Sounds like the possibly dangerous charging bug got finally fixed.

Does anyone have the incremental ota link?!

How to update please,
I'm on april Stock, download May OTA full but when i try to update it via sidloade in recovery i get TWRP
Must i delete TWRP or please how to update

ughhh!!! just updated to may but I still can't speed charging over my usb-c on my windows pc!!! I had until the march update!!

Just flashed the full factory image for May. (Removed the -w to retain data). Fastboot booted TWRP. Flashed Magisk. All went as expected. And I'm up and running May security update on my Google unlocked, rooted, Pixel XL. All root and Magisk hide functionality seem to be working as before.

moyses said:
How to update please,
I'm on april Stock, download May OTA full but when i try to update it via sidloade in recovery i get TWRP
Must i delete TWRP or please how to update
Click to expand...
Click to collapse
I don't understand. You have twrp and you tried flash over twrp and it failed?!
I flashed the full ota via twrp and it went just fine.

i ran into a weird problem. i tried flashing the may full factory image and got a write failure when the script was trying to write system_b 2/4. i tried several things like redownloading the zip and verifying the checksum, redownloading adb and fastboot from google, wiping data, and flashing to a different slot. nothing worked. i was able to reflash the april full factory image to both slots. i tried flashing the android p developer preview to both slots and that worked fine too. so now, i'm running android p.

Just try update to last security patches via TWRP and it work like a charm

altwu said:
i ran into a weird problem. i tried flashing the may full factory image and got a write failure when the script was trying to write system_b 2/4. i tried several things like redownloading the zip and verifying the checksum, redownloading adb and fastboot from google, wiping data, and flashing to a different slot. nothing worked. i was able to reflash the april full factory image to both slots. i tried flashing the android p developer preview to both slots and that worked fine too. so now, i'm running android p.
Click to expand...
Click to collapse
I had the exact same thing. Only thing that solved it was going to a different computer. First PC was Dell XPS 15 over a USB-C port. Had success on an older home built desktop with a USB 3.0 connection. Didn't have to wipe data in the end. What computer are you using? Connection?
This was the end of the log with failures:
writing 'system_b' 1/4...
OKAY [ 3.533s]
sending sparse 'system_b' 2/4 (524284 KB)...
FAILED (data write failure (Unknown error))
finished. total time: 31.655s
Press any key to exit...
Sent from my Pixel XL using Tapatalk

yearn2burn said:
I had the exact same thing. Only thing that solved it was going to a different computer. First PC was Dell XPS 15 over a USB-C port. Had success on an older home built desktop with a USB 3.0 connection. Didn't have to wipe data in the end. What computer are you using? Connection?
This was the end of the log with failures:
writing 'system_b' 1/4...
OKAY [ 3.533s]
sending sparse 'system_b' 2/4 (524284 KB)...
FAILED (data write failure (Unknown error))
finished. total time: 31.655s
Press any key to exit...
Sent from my Pixel XL using Tapatalk
Click to expand...
Click to collapse
that's the error i got. i'm using a dell precision 5510 laptop running windows 10 and i was flashing over a usb-c port when i got the error. good to know there's a workaround. thanks.

I cannot get past the Acknowledge button on Factory Images for Nexus and Pixel Devices website https://developers.google.com/android/images

OKAstro said:
I cannot get past the Acknowledge button on Factory Images for Nexus and Pixel Devices website https://developers.google.com/android/images
Click to expand...
Click to collapse
Same ? I'm stuck with very unstable Android P beta.

Klufenza said:
Same I'm stuck with very unstable Android P beta.
Click to expand...
Click to collapse
I've discovered Google is aware of this.
You can access the firmware if you go Incognito in Chrome, or is you use IE/Edge

OKAstro said:
I've discovered Google is aware of this.
You can access the firmware if you go Incognito in Chrome, or is you use IE/Edge
Click to expand...
Click to collapse
Welp, it worked. Thanks man

OKAstro said:
I've discovered Google is aware of this.
You can access the firmware if you go Incognito in Chrome, or is you use IE/Edge
Click to expand...
Click to collapse
Cheers mate.

How and what do you have to flash in twrp to get May images up to date?
Sent from my marlin using XDA Labs

jurington said:
How and what do you have to flash in twrp to get May images up to date?
Click to expand...
Click to collapse
You can only flash them in bootloader mode I think.