Someone at Google's mess the links. Here are the correct ones...
NEXUS 5 hammerhead:
https://dl.google.com/dl/android/aosp/hammerhead-kot49h-factory-02006b99.tgz
NEXUS 7 2013 razor:
https://dl.google.com/dl/android/aosp/razor-kot49h-factory-ebb4918e.tgz
NEXUS 7 2013 razorg
https://dl.google.com/dl/android/aosp/razorg-kot49h-factory-49789b24.tgz
NEXUS 4 occam:
https://dl.google.com/dl/android/aosp/occam-kot49h-factory-02e344de.tgz
NEXUS 10 mantaray:
https://dl.google.com/dl/android/aosp/mantaray-kot49h-factory-174ba74f.tgz
NEXUS 7 2012 nakasi:
https://dl.google.com/dl/android/aosp/nakasi-kot49h-factory-5e9db5e1.tgz
NEXUS 7 2012 nakasig:
https://dl.google.com/dl/android/aosp/nakasig-kot49h-factory-83d93b5f.tgz
How did u found the correct links?
btw, downloading, THANKS
C4SCA said:
How did u found the correct links?
btw, downloading, THANKS
Click to expand...
Click to collapse
The last 8 chars of the link really are the first 8 chars of the SHA-1 Checksum (that is correct).
You rock man! Thanks!
Does google release odex versions ?
Sent from my SM-N900T using Tapatalk
alleyezondisromo said:
Does google release odex versions ?
Sent from my SM-N900T using Tapatalk
Click to expand...
Click to collapse
Yes, these images are odexed.
thanks [email protected]!!!!
flashing!
Thanks pal. really needed this.
Thanks! Was just about to flash my phone when I realized the links on Google's website doesn't work!
Sfkn2 said:
Thanks! Was just about to flash my phone when I realized the links on Google's website doesn't work!
Click to expand...
Click to collapse
lol me too...I was all excited, then I realized I just get a 404 error. I actually thought they just hadn't finished uploading the images and jumped the gun posting links. Glad I saw this thread!!
Thank you. I downloaded Android SDK, copied the dll's and fastboot/adb from the platform-tools folder to C:\windows\syswow64\ and then extracted the occam-kot49h tgz and modified the flash-all.bat as to remove the "-w" (wipe) command from the fastboot update command and then I threw my phone into fastboot mode and opened up a command prompt and ran that flash-all.bat, upgraded from 4.4 to 4.4.2 seamlessly with no data loss. Of course I did lose root as expected and I suppose I should have removed/commented out the flashboot radio command line so I could have kept LTE, oh well I'll fix that later. Thanks again.
hi thanx for the links
after downloading i had this error:
Code:
[email protected]:~/occam-kot49h$ sudo sh flash-all.sh
sending 'bootloader' (2203 KB)...
OKAY [ 0.104s]
writing 'bootloader'...
OKAY [ 0.766s]
finished. total time: 0.869s
rebooting into bootloader...
OKAY [ 0.001s]
finished. total time: 0.001s
sending 'radio' (45537 KB)...
OKAY [ 2.128s]
writing 'radio'...
OKAY [ 2.805s]
finished. total time: 4.934s
rebooting into bootloader...
OKAY [ 0.001s]
finished. total time: 0.001s
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
--------------------------------------------
Bootloader Version...: MAKOZ30d
Baseband Version.....: M9615A-CEFWMAZM-2.0.1700.98
Serial Number........: 0216337d9153f835
--------------------------------------------
checking product...
OKAY [ 0.002s]
checking version-bootloader...
OKAY [ 0.002s]
checking version-baseband...
OKAY [ 0.002s]
sending 'boot' (6340 KB)...
OKAY [ 0.301s]
writing 'boot'...
OKAY [ 0.334s]
sending 'recovery' (6888 KB)...
OKAY [ 0.344s]
writing 'recovery'...
OKAY [ 0.392s]
erasing 'system'...
OKAY [ 0.716s]
sending 'system' (713960 KB)...
OKAY [ 33.568s]
writing 'system'...
FAILED (remote: Unknown chunk type)
finished. total time: 47.589s
i need some help
(BTW i executed the flash-all.sh script after deleting the "-w" option and deleting userdata.img)
activexda said:
i need some help
(BTW i executed the flash-all.sh script after deleting the "-w" option and deleting userdata.img)
Click to expand...
Click to collapse
Are you using the latest SDK? That error usually means that the version of the fatsboot command isn't one liked by the bootloader.
VivaErBetis said:
Are you using the latest SDK? That error usually means that the version of the fatsboot command isn't one liked by the bootloader.
Click to expand...
Click to collapse
ok i will download the "SDK Tools Only" package, thats all what i need right?
activexda said:
ok i will download the "SDK Tools Only" package, thats all what i need right?
Click to expand...
Click to collapse
Yes, and inside it the latest “platform tools“.
VivaErBetis said:
Yes, and inside it the latest “platform tools“.
Click to expand...
Click to collapse
ok, after trying with latest sdk i still have the same problem
is there anybody managed to install the factory image?
Maybe you messed up the script.
gm007 said:
Maybe you messed up the script.
Click to expand...
Click to collapse
i don't think so
script:
Code:
#!/bin/sh
# Copyright 2012 The Android Open Source Project
#
# Licensed under the Apache License, Version 2.0 (the "License");
# you may not use this file except in compliance with the License.
# You may obtain a copy of the License at
#
# http://www.apache.org/licenses/LICENSE-2.0
#
# Unless required by applicable law or agreed to in writing, software
# distributed under the License is distributed on an "AS IS" BASIS,
# WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
# See the License for the specific language governing permissions and
# limitations under the License.
fastboot flash bootloader bootloader-mako-makoz30d.img
fastboot reboot-bootloader
sleep 5
fastboot flash radio radio-mako-m9615a-cefwmazm-2.0.1700.98.img
fastboot reboot-bootloader
sleep 5
fastboot update image-occam-kot49h.zip
Maybe download the file again.
activexda said:
i need some help
(BTW i executed the flash-all.sh script after deleting the "-w" option and deleting userdata.img)
Click to expand...
Click to collapse
gm007 said:
Maybe download the file again.
Click to expand...
Click to collapse
I would definitely download the file again. Did you check the MD5 sum?
Related
Your bootloader must be unlocked to use this. If your bootloader is not already unlocked, unlocking it will wipe your data and this method is not recommended.
This is a modified factory image that will not erase your user data or custom recovery. This can be used even if you’re rooted and with modified system files, xposed framework, or custom recovery. Once installed you will lose root, just flash supersu in your custom recovery. Xposed should still be on your device so just go into the app and re-install it. For any modified system files, you will have to re-modify those.
This is intended for those on the stock rom, rooted, and with a custom recovery. It’ll work if you have a custom rom but will put the stock system on.
I am not responsible for anything you do to your device so flash at your own risk. Always backup before doing any significant changes to your device. I would recommend off your device in case something happens
.
To use, download the modified factory image here http://www.androidfilehost.com/?fid=23578570567717696 Use 7-zip or winrar to extract the files.
Mirror https://mega.co.nz/#!oIohmY7a!ZsTx49c150KlXyfc6igm2RH9J1PMtfJlj2J8y3219Qs
Supersu by chainfire can be found here, CWM / TWRP / MobileODIN installable ZIP: http://download.chainfire.eu/supersu
Boot into the bootloader. From a cmd window opened where the flash-all file is just type flash-all. You can use shift, right click on the hammerhead-ktu84p-Modified folder to open a command window in the correct folder.
You can also just double click on the flash-all.bat
This is tested on a windows machine; however it should work on a Mac too, flash the flash-all.sh.
jd1639 said:
Your bootloader must be unlocked to use this. If your bootloader is not already unlocked, unlocking it will wipe your data and this method is not recommended.
This is a modified factory image that will not erase your user data or custom recovery. This can be used even if you’re rooted and with modified system files, xposed framework, or custom recovery. Once installed you will lose root, just flash supersu in your custom recovery. Xposed should still be on your device so just go into the app and re-install it. For any modified system files, you will have to re-modify those.
This is intended for those on the stock rom, rooted, and with a custom recovery. It’ll work if you have a custom rom but will put the stock system on.
I am not responsible for anything you do to your device so flash at your own risk. Always backup before doing any significant changes to your device. I would recommend off your device in case something happens
.
To use, download the modified factory image here http://d-h.st/yMl Use 7-zip or winrar to extract the files.
Mirror coming
Supersu by chainfire can be found here, CWM / TWRP / MobileODIN installable ZIP: http://download.chainfire.eu/supersu
Boot into the bootloader. From a cmd window opened where the flash-all file is just type flash-all. You can use shift, right click on the hammerhead-ktu84p-Modified folder to open a command window in the correct folder.
You can also just double click on the flash-all.bat
This is tested on a windows machine; however it should work on a Mac too, flash the flash-all.sh.
Click to expand...
Click to collapse
omg as usual thanks a lot
update: issues with minimal adb with windows 8.1 right now using 15 seconds ADB Installer v1.3
C:\Users\eilegz\adb>flash-all.bat
sending 'bootloader' (2508 KB)...
OKAY [ 0.313s]
writing 'bootloader'...
OKAY [ 0.484s]
finished. total time: 0.797s
rebooting into bootloader...
OKAY [ 0.047s]
finished. total time: 0.047s
sending 'radio' (45409 KB)...
OKAY [ 2.063s]
writing 'radio'...
OKAY [ 3.133s]
finished. total time: 5.196s
rebooting into bootloader...
OKAY [ 0.047s]
finished. total time: 0.047s
archive does not contain 'boot.sig'
archive does not contain 'recovery.img'
archive does not contain 'system.sig'
--------------------------------------------
Bootloader Version...: HHZ11k
Baseband Version.....: M8974A-2.0.50.1.16
Serial Number........: 0407b84a215be2a3
--------------------------------------------
checking product...
OKAY [ 0.109s]
checking version-bootloader...
OKAY [ 0.094s]
checking version-baseband...
OKAY [ 0.109s]
sending 'boot' (8700 KB)...
OKAY [ 0.547s]
writing 'boot'...
OKAY [ 0.734s]
erasing 'system'...
OKAY [ 1.143s]
sending 'system' (721400 KB)...
OKAY [ 26.376s]
writing 'system'...
OKAY [ 50.008s]
rebooting...
finished. total time: 79.667s
Press any key to exit...
hopefully everything works
Works great!
Thanks for this easy method it worked like a charm!
Thanks once again one of the easiest if not the easiest way to update!
Awesome! Thanks, dude.
Sent from my Nexus 5 using Tapatalk
Will this work with 4.4.2?
used it on a mac and worked like a charm.
Worked perfect once again. Thank you
That was a little too easy.
Can someone make a flashable updateable zip through twrp. I'm not familiar with flashing though cmd in Windows.
Cheers
is it possible to extract the 1.16 radio and flash seperately or will need to ota to 4.4.4? having horrendous signal issues and need to see if 1.16 will improve that
bosna110 said:
is it possible to extract the 1.16 radio and flash seperately or will need to ota to 4.4.4? having horrendous signal issues and need to see if 1.16 will improve that
Click to expand...
Click to collapse
Get the .zip here:
http://downloads.codefi.re/autoprime/LG/Nexus_5/Modems
jonneepuh said:
Can someone make a flashable updateable zip through twrp. I'm not familiar with flashing though cmd in Windows.
Cheers
Click to expand...
Click to collapse
The OTA? It's here:
http://forum.xda-developers.com/showpost.php?p=53534137&postcount=1891
You sir, are a legend
Grazie, amico.
Wakamatsu said:
Get the .zip here:
http://downloads.codefi.re/autoprime/LG/Nexus_5/Modems
Click to expand...
Click to collapse
Is there a difference radio for the Nexus 5 D820 or the Nexus 5 D821 (Europe and US) version??
wietse1988 said:
Is there a difference radio for the Nexus 5 D820 or the Nexus 5 D821 (Europe and US) version??
Click to expand...
Click to collapse
No, read the OP of the modem thread. Same checksums.
For Mac do you have to change the flash-all.sh putting in it ./ in front of every fastboot command? Is that right?
Thank you.
That was easy Thanks for this. and Kudos for getting this out so quickly.
Direct download link:
https://dl.google.com/dl/android/aosp/occam-lmy47o-factory-cae68e81.tgz
md5sum: 293a98009cfbcb5d398c05302a86ee8c
sha1sum: cae68e81d5a1758f92b77520f829400da205111f
Goggle's Factory Images page:
https://developers.google.com/android/nexus/images
Tip for those upgrading without flashing via factory image. After you flash cache.img boot into your custom recovery of choice and wipe the cache partition. Otherwise you're going to be stuck on the lollipop circles for a long time. This is specific to nexus 4.
Sent from my Nexus 7 using Tapatalk
How can i root it ?
Virtxer said:
How can i root it ?
Click to expand...
Click to collapse
You're kidding right?
Yep
Hopefully someone will make a flashable stock rom based off of the images
Sent from my Nexus 4 using XDA Free mobile app
Zehlek said:
Hopefully someone will make a flashable stock rom based off of the images
Sent from my Nexus 4 using XDA Free mobile app
Click to expand...
Click to collapse
Hi there, long time no see
I was gonna do a flashable version but my pc was acting up again so i'll see if I can do it tomorrow after work if someone else doesn't do it by then :good:
does only me have problem with - remote partition table doesn't exist,when try to install twrp,or this is a comon isue?
i install stock image(unzip it with 7z),install with flash all. everything pass ok. when i turn on usb debuging and try to install twrp with fastboot i get this error.
i try to install stock image manuallu with fastboot. in that case i must to do a factory resset when boot,or phone will stuck with boot. also this pass ok,but fasboot cant install only twrp. old version,new,same error. fastboot recognize nexus,commands working,
Zehlek said:
Hopefully someone will make a flashable stock rom based off of the images
Sent from my Nexus 4 using XDA Free mobile app
Click to expand...
Click to collapse
I'm using the latest Simple AOSP for Nexus 4 (Android 5.1.0), which was built today, with the LMY47O binary file, no random reboot so far.
Here is everything you need: http://chromloop.com/2015/04/how-to-install-android-5-1-lollipop-custom-rom-nexus-4/
5.0.1 (LRX22C) factory to 5.1.0 (LMY47O) factory
My bootloader was already un-locked. Hold the volume down key and hit the power button to power on the phone into fastboot mode.
Windows 7
Front USB 2.0 ports
7-zip
[TOOL]Updated ADB (version 1.0.32) and Fastboot [16-OCT-14]
http://forum.xda-developers.com/htc-one/general/tool-updated-adb-version-1-0-32-fastboot-t2932160
extract - fastboot_adb(1.0.32)_071114_r21.rar
extract - occam-lmy47o-factory-cae68e81.tgz
extract - occam-lmy47o-factory-cae68e81.tar
Move all of the files into the fastboot_adb(1.0.32)_071114_r21 folder.
Open the folder. Hold down the shift key and right click. Click on "open command windows here"
type in: flash-all.bat or fl and hit the tab key.
FAIL:
C:\Users\test\Desktop\fastboot_adb(1.0.32)_071114_r21>flash-all.bat
< waiting for device >
sending 'bootloader' (2264 KB)...
OKAY [ 0.094s]
writing 'bootloader'...
OKAY [ 0.281s]
finished. total time: 0.374s
rebooting into bootloader...
OKAY [ 0.000s]
finished. total time: 0.000s
< waiting for device >
sending 'radio' (45537 KB)...
OKAY [ 1.560s]
writing 'radio'...
OKAY [ 2.480s]
finished. total time: 4.040s
rebooting into bootloader...
OKAY [ 0.000s]
finished. total time: 0.000s
< waiting for device >
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
failed to allocate 854497332 bytes
error: update package missing system.img
Press any key to exit...
Extract image-occam-lmy47o.zip into the fastboot_adb(1.0.32)_071114_r21 folder.
Run the following commands.
There is no need to update the bootloader and modem. You can see on the screen the current bootloader and modem build were updates from the last step.
Commands found via http://forum.xda-developers.com/nexus-4/general/how-to-how-to-flash-factory-image-t2010312
fastboot flash recovery recovery.img
fastboot flash boot boot.img
fastboot flash system system.img ***took apx 8 mins before seeing anything being written to the screen and phone.***
fastboot flash boot boot.img
fastboot flash recovery recovery.img *** don't do this if you have TWRP installed ***
fastboot format cache
fastboot reboot
C:\Users\test\Desktop\fastboot_adb(1.0.32)_071114_r21>fastboot flash recovery recovery.img
sending 'recovery' (6956 KB)...
OKAY [ 0.234s]
writing 'recovery'...
OKAY [ 0.390s]
finished. total time: 0.624s
C:\Users\test\Desktop\fastboot_adb(1.0.32)_071114_r21>fastboot flash boot boot.img
sending 'boot' (6394 KB)...
OKAY [ 0.250s]
writing 'boot'...
OKAY [ 0.374s]
finished. total time: 0.624s
C:\Users\test\Desktop\fastboot_adb(1.0.32)_071114_r21>fastboot flash system system.img
erasing 'system'...
OKAY [ 0.827s]
sending 'system' (834470 KB)...
OKAY [ 50.747s]
writing 'system'...
OKAY [ 46.519s]
finished. total time: 98.140s
C:\Users\test\Desktop\fastboot_adb(1.0.32)_071114_r21>fastboot flash boot boot.img
sending 'boot' (6394 KB)...
OKAY [ 0.250s]
writing 'boot'...
OKAY [ 0.374s]
finished. total time: 0.624s
C:\Users\test\Desktop\fastboot_adb(1.0.32)_071114_r21>fastboot flash recovery recovery.img
sending 'recovery' (6956 KB)...
OKAY [ 0.265s]
writing 'recovery'...
OKAY [ 0.374s]
finished. total time: 0.640s
C:\Users\test\Desktop\fastboot_adb(1.0.32)_071114_r21>fastboot format cache
Creating filesystem with parameters:
Size: 587202560
Block size: 4096
Blocks per group: 32768
Inodes per group: 7168
Inode size: 256
Journal blocks: 2240
Label:
Blocks: 143360
Block groups: 5
Reserved block group size: 39
Created filesystem with 11/35840 inodes and 4616/143360 blocks
erasing 'cache'...
OKAY [ 0.078s]
sending 'cache' (10984 KB)...
OKAY [ 0.437s]
writing 'cache'...
OKAY [ 0.608s]
finished. total time: 1.139s
C:\Users\test\Desktop\fastboot_adb(1.0.32)_071114_r21>fastboot reboot
rebooting...
finished. total time: -0.000s
It took apx 11 mins to boot up. It was optimizing the 100+ apps. All my apps and config settings were there.
Optional....
I powered off and when back into fastboot mode to flash TWRP so I can create a backup image.
http://dl.twrp.me/mako/
fastboot flash recovery twrp-2.8.6.0-mako.img
Use the arrow keys to reboot into recovery mode to boot into TWRP. Do not boot into the system.
Ok, managed to get my laptop working again. Rom is uploading, will post a link to the thread when done :good:
EDIT: Thread link: http://forum.xda-developers.com/nexus-4/development/rom-stock-flashable-rom-t3084656
If you get ANY Errors during Updating via the flash-all script - try to update ADB itself. I was using an old version and got errors until i downloaded and used a new ADB version.
Where is the 5.1.1?
Mirkoitalia said:
Where is the 5.1.1?
Click to expand...
Click to collapse
I don't know. When did you see it last?
Hey,guys! I uesd fastboot to flash system,but it failed
code:
target max-sparse-size: 256MB
sending 'system' (256598 KB)...
OKAY [ 8.040s]
writing 'system'...
(bootloader) Failed to flash sparse image
FAILED (remote failure)
finished. total time: 18.249s
anyone can help me please?
YOUNG MAN. said:
Hey,guys! I uesd fastboot to flash system,but it failed
code:
target max-sparse-size: 256MB
sending 'system' (256598 KB)...
OKAY [ 8.040s]
writing 'system'...
(bootloader) Failed to flash sparse image
FAILED (remote failure)
finished. total time: 18.249s
anyone can help me please?
Click to expand...
Click to collapse
Try to use the mfastboot, because the system.img is to big to use the normal fastboot
libnijunior said:
Try to use the mfastboot, because the system.img is to big to use the normal fastboot
Click to expand...
Click to collapse
it failed too
code
target reported max download size of 536870912 bytes
sending 'system' (256089 KB)...
OKAY [ 8.035s]
writing 'system'...
(bootloader) Failed to flash sparse image
FAILED (remote failure)
finished. total time: 13.062s
and sometimes it shows
target reported max download size of 536870912 bytes
sending 'system' (256598 KB)...
OKAY [ 8.046s]
writing 'system'...
(bootloader) Failed to erase partition
FAILED (remote failure)
finished. total time: 13.224s
YOUNG MAN. said:
it failed too
code
target reported max download size of 536870912 bytes
sending 'system' (256089 KB)...
OKAY [ 8.035s]
writing 'system'...
(bootloader) Failed to flash sparse image
FAILED (remote failure)
finished. total time: 13.062s
and sometimes it shows
target reported max download size of 536870912 bytes
sending 'system' (256598 KB)...
OKAY [ 8.046s]
writing 'system'...
(bootloader) Failed to erase partition
FAILED (remote failure)
finished. total time: 13.224s
Click to expand...
Click to collapse
What version of boot loader do you have? If you already flashed the boot loader of 5.0.2 and you are trying to flash older system images that error appears.
juliospinoza said:
What version of boot loader do you have? If you already flashed the boot loader of 5.0.2 and you are trying to flash older system images that error appears.
Click to expand...
Click to collapse
I Just bought this phone yesterday and it was 5.0 when i got it. Then i updated to 5.1 and the BL version is 60.14 now . I tried to back to 5.0 so it showed this error.
Do you have any way to solve this problem? My phone is bootloop now.
Thanx
YOUNG MAN. said:
I Just bought this phone yesterday and it was 5.0 when i got it. Then i updated to 5.1 and the BL version is 60.14 now . I tried to back to 5.0 so it showed this error.
Do you have any way to solve this problem? My phone is bootloop now.
Thanx
Click to expand...
Click to collapse
you really shouldn't downgrade unless you know what you are doing.
Is the bootloader unlocked? Can you get into bootloader mode?
JulesJam said:
you really shouldn't downgrade unless you know what you are doing.
Is the bootloader unlocked? Can you get into bootloader mode?
Click to expand...
Click to collapse
Yes,it is unlocked and i can get into fastboot mode .Is that bootlodader mode?
YOUNG MAN. said:
Yes,it is unlocked and i can get into fastboot mode .Is that bootlodader mode?
Click to expand...
Click to collapse
Yes, they are synonyms. I would install Motorola Device Manager to your PC and let it attempt to repair your phone.
https://motorola-global-portal.custhelp.com/app/answers/detail/a_id/88481
If it doesn't repair your phone, post back here.
YOUNG MAN. said:
Yes,it is unlocked and i can get into fastboot mode .Is that bootlodader mode?
Click to expand...
Click to collapse
I installed Motorola Device Manager, what should i do next?
JulesJam said:
you really shouldn't downgrade unless you know what you are doing.
Is the bootloader unlocked? Can you get into bootloader mode?
Click to expand...
Click to collapse
I installed Motorola Device Manager and tried again, it still did't work.
code:
C:\Users\Alan\Desktop\ccc>fastboot flash system F:\XT1095\system.img_sparsechunk
.0
target max-sparse-size: 256MB
sending 'system' (256598 KB)...
OKAY [ 8.047s]
writing 'system'...
(bootloader) Failed to erase partition
FAILED (remote failure)
finished. total time: 13.217s
YOUNG MAN. said:
I installed Motorola Device Manager and tried again, it still did't work.
Click to expand...
Click to collapse
Did it detect your device at all? Did it try to repair it?
YOUNG MAN. said:
C:\Users\Alan\Desktop\ccc>fastboot flash system F:\XT1095\system.img_sparsechunk
.0
target max-sparse-size: 256MB
sending 'system' (256598 KB)...
OKAY [ 8.047s]
writing 'system'...
(bootloader) Failed to erase partition
FAILED (remote failure)
finished. total time: 13.217s
Click to expand...
Click to collapse
If you are only trying to flash small sparsechunks, have you tried flashing using the latest version of fastboot from Root Junky's site?
http://rootjunkysdl.com/?device=Adb Fastboot Files
Go into developer options and enable OEM unlocking. Then try it.
Edit: Forgot you said you were bootlooped. Can you install the 5.1 image again?
Sent from my XT1095
JulesJam said:
Did it detect your device at all? Did it try to repair it?
If you are only trying to flash small sparsechunks, have you tried flashing using the latest version of fastboot from Root Junky's site?
Click to expand...
Click to collapse
NO,It not detect my phone,it just search new software when i open it.
And I tried the latest version of fastboot,still failed
YOUNG MAN. said:
NO,It not detect my phone,it just search new software when i open it.
And I tried the latest version of fastboot,still failed
Click to expand...
Click to collapse
Did you try RSDLite?
JulesJam said:
Did you try RSDLite?
Click to expand...
Click to collapse
it can't detect my phone
YOUNG MAN. said:
it can't detect my phone
Click to expand...
Click to collapse
When you are in recovery, what does
adb devices
show you? Of course when you open the cmd window you have to navigate to a folder where adb.exe and the other required files are stored in order to use adb commands.
JulesJam said:
When you are in recovery, what does
adb devices
show you? Of course when you open the cmd window you have to navigate to a folder where adb.exe and the other required files are stored in order to use adb commands.
Click to expand...
Click to collapse
it shows View attachment 3294009
but in fastboot mode it shows View attachment 3294012
and my recovery is TWRP 2.8.60
YOUNG MAN. said:
it shows View attachment 3294009
but in fastboot mode it shows View attachment 3294012
and my recovery is TWRP 2.8.60
Click to expand...
Click to collapse
No I mean, connect your phone to your PC when you are in TWRP. Then open a command window. Then navigate to where adb.exe is stored - i.e, at the command prompt type in cd c:\[fill in the directory where adb.exe is stored]
then when you are at the proper directory, at the command prompt in the command window type:
adb devices
then hit enter.
It should return the serial number of your device.
JulesJam said:
No I mean, connect your phone to your PC when you are in TWRP. Then open a command window. Then navigate to where adb.exe is stored - i.e, at the command prompt type in cd c:\[fill in the directory where adb.exe is stored]
then when you are at the proper directory, at the command prompt in the command window type:
adb devices
then hit enter.
It should return the serial number of your device.
Click to expand...
Click to collapse
it shows this:
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
device
dustin_b said:
Go into developer options and enable OEM unlocking. Then try it.
Edit: Forgot you said you were bootlooped. Can you install the 5.1 image again?
Sent from my XT1095
Click to expand...
Click to collapse
NO,my recovery is TWRP now ,and I can't flash the original recovery ,it failed.
I have been doing this for a while but I am relatively new to Android and specifically to Nexus 6 so bear with me. If the question has already been asked, answered or discussed, I apologize but a quick search didn't reveal anything so here I am. Also please refrain from unkind and snarky comments, just be professional and helpful please.
My question has to do with the Factory Images from Google, such as 5.1.0 (LMY47I) available direct from Google Developers. Are these files considered "at root"? or do they need to be rooted still? And if they need to be rooted, can they be rooted BEFORE the flashing?
Thank you in advance.
GuardianUSMC said:
I have been doing this for a while but I am relatively new to Android and specifically to Nexus 6 so bear with me. If the question has already been asked, answered or discussed, I apologize but a quick search didn't reveal anything so here I am. Also please refrain from unkind and snarky comments, just be professional and helpful please.
My question has to do with the Factory Images from Google, such as 5.1.0 (LMY47I) available direct from Google Developers. Are these files considered "at root"? or do they need to be rooted still? And if they need to be rooted, can they be rooted BEFORE the flashing?
Thank you in advance.
Click to expand...
Click to collapse
No, you cannot ad root to the image before flashing.
Best/easiest way to root is:
- Enable usb debugging and enable OEM UNLOCK in developer options
- Unlock the bootloader in fastboot with cmd command: fastboot oem unlock
- Flash the latest factory image in fastboot/bootloader mode. You have too flash the img`s seperately.
- Then flash or boot into TWRP and flash the latest superSU.zip and reboot
- Install BusyBox from Play and you`re all set.
gee2012 said:
No, you cannot ad root to the image before flashing.
Click to expand...
Click to collapse
Well that's unfortunate. So the factory images provided directly by Google are NOT at root already either?
Best/easiest way to root is:
- Enable usb debugging and enable OEM UNLOCK in developer options
- Unlock the bootloader in fastboot with cmd command: fastboot oem unlock
- Flash the latest factory image in fastboot/bootloader mode. You have too flash the img`s seperately.
- Then flash or boot into TWRP and flash the latest superSU.zip and reboot
- Install BusyBox from Play and you`re all set.
Click to expand...
Click to collapse
Thank you, I apologize for not including this information earlier but I currently have an unlocked OEM (did that before I rooted the phone) but since the OTA will not install and frankly I have always been a fan of clean install over upgrade and patch, so decided to just go ahead and flash the latest image. But I figured this time to research and see if I can do some prep to make it go smoother and quicker.
Thank you for the steps but I do have one question about what you said. You say flash or boot into TWRP, since that is not installed by default images, that means grab it of the TWRP page, which I was looking at earlier, and then flash that so I can do SU. The default recovery doesn't allow you to flash the SU? I just hate too add too many unnecessary things if I can do it with what's there. Which brings me to the busybox, is it necessary and if so, for what exactly? I have never actually found myself face to face with it for anything.
Thank you again for the response, I appreciate it.
GuardianUSMC said:
Well that's unfortunate. So the factory images provided directly by Google are NOT at root already either?
Thank you, I apologize for not including this information earlier but I currently have an unlocked OEM (did that before I rooted the phone) but since the OTA will not install and frankly I have always been a fan of clean install over upgrade and patch, so decided to just go ahead and flash the latest image. But I figured this time to research and see if I can do some prep to make it go smoother and quicker.
Thank you for the steps but I do have one question about what you said. You say flash or boot into TWRP, since that is not installed by default images, that means grab it of the TWRP page, which I was looking at earlier, and then flash that so I can do SU. The default recovery doesn't allow you to flash the SU? I just hate too add too many unnecessary things if I can do it with what's there. Which brings me to the busybox, is it necessary and if so, for what exactly? I have never actually found myself face to face with it for anything.
Thank you again for the response, I appreciate it.
Click to expand...
Click to collapse
Just place TWRP in the fastboot/platform-tools folder, reboot into fastboot and in cmd type : fastboot boot name-recovery.img. Now you can flash the superSU.zip and still keep stock recovery. You can`t flash custom files with the stock recovery no.
gee2012 said:
Just place TWRP in the fastboot/platform-tools folder, reboot into fastboot and in cmd type : fastboot boot name-recovery.img. Now you can flash the superSU.zip and still keep stock recovery. You can`t flash custom files with the stock recovery no.
Click to expand...
Click to collapse
Got it, thank you very much for your assistance.
Too bad the Factory Images from Google are not already rooted.
GuardianUSMC said:
So the factory images provided directly by Google are NOT at root already either?
Click to expand...
Click to collapse
Hi,
We're getting mixed up with terminology here. The images are not AT root, but also are NOT rooted. These mean different things so I want to elaborate on that for you.
The android kernel is linux based, which means that the terminology and device structure are loaned from that technology. Root in linux terms, means the root of the device. This is if you imagine the file structure of a computer using directories, the very top-most directory in the structure that every other directory sits within, is called root.
So for example on a linux machine you will have the root directory:
/
Within root, you will have other directories such as:
/bin
/etc
/usr
See here for more information:
http://www.thegeekstuff.com/2010/09/linux-file-system-structure/
So root is kind of like the C:\ drive on a Windows PC. Everything to do with the OS and User directories are within there.
Your Android device is the same, however, /bin, /etc (etc) are not at the root of the device. They sit within the system partition, which sits within root. so /system/bin, /system/etc. When you flash a factory image, it flashes the images to /system, /cache, /userdata (and a few other places) where as the root of the device remains largely untouched.
Now in order to access these root directories, you must have a superuser account (su) and the process for achieving this on android is called "rooting". If you succeed in this process, you have "rooted" or have "root" which is sort of incorrect and leads to confusion.
I know this isn't too related to your question, but I wanted to clarify it in case you weren't sure - based on the phrasing of your question.
@rootSU,
Excellent mini tutorial. I wish this could be stickied on the General roll up thread. Thank you very much.
rootSU said:
Hi,
We're getting mixed up with terminology here. The images are not AT root, but also are NOT rooted. These mean different things so I want to elaborate on that for you.
Click to expand...
Click to collapse
I appreciate that and forgive me I know I used the terms interchangeably and that's my bad.
The android kernel is linux based, which means that the terminology and device structure are loaned from that technology. Root in linux terms, means the root of the device. This is if you imagine the file structure of a computer using directories, the very top-most directory in the structure that every other directory sits within, is called root.
Click to expand...
Click to collapse
yes I am familiar with that and I was using the term to mean having root privileges, again my bad.
Now in order to access these root directories, you must have a superuser account (su) and the process for achieving this on android is called "rooting". If you succeed in this process, you have "rooted" or have "root" which is sort of incorrect and leads to confusion.
Click to expand...
Click to collapse
Understood, I have done that and my device is currently rooted. I was more looking into making an image that is already rooted, to borrow a term from Windows, slipstream the root functionality pre-flashing. I was told not going to happen, that's fine. Although when I had my HTC Evo 4G, I had pre-rooted images that I had created with the bloat removed and I was flashing them with root functionality out of the box, but that's another story, I guess Nexus 6 is a different animal and dealing with Lollipop probably more difficult than Gingerbread.
I know this isn't too related to your question, but I wanted to clarify it in case you weren't sure - based on the phrasing of your question.
Click to expand...
Click to collapse
No but I appreciate you taking the time, thank you.
Right now mostly I am frustrated with the fact that the factory images provided by google will not flash right and keep *****ing about missing .sig files. I have tried flashing them individually by taking the root, system, recovery images out of the zip file and doing them individually as been suggested all over the place but no luck there there, keeps *****ing about the partitions instead, makes no sense. The bootloader and radio images go through without a hitch but the rest is just a mess.
Just to share, I am trying to flash the factory image that I mentioned in my original post, so I won't repost it. Here is what did so far to no avail, so any assistance would be greatly appreciated:
I issue the command adb reboot bootloader and it successful reboots the phone into the bootloader
Extracting the folder shamu-lmy47i containing the following files:
bootloader-shamu-moto-apq8084-71.08.img
flash-all.bat
flash-all.sh
flash-base.sh
image-shamu-lmy47i.zip
radio-shamu-d4.0-9625-02.95.img
Opening the batch file you see the following (I have removed the copyright header for sake of brevity)
Code:
PATH=%PATH%;"%SYSTEMROOT%\System32"
fastboot flash bootloader bootloader-shamu-moto-apq8084-71.08.img
fastboot reboot-bootloader
ping -n 5 127.0.0.1 >nul
fastboot flash radio radio-shamu-d4.0-9625-02.95.img
fastboot reboot-bootloader
ping -n 5 127.0.0.1 >nul
fastboot -w update image-shamu-lmy47i.zip
echo Press any key to exit...
pause >nul
exit
Since the only thing I want to add to this is root, I add this after the image update:
Code:
fastboot boot CF-Auto-Root-shamu-shamu-nexus6.img
So we let it rip and this is the resulting output:
Code:
C:\Users\Major\Desktop\shamu-lmy47i>flash-all.bat
target reported max download size of 536870912 bytes
sending 'bootloader' (3807 KB)...
OKAY [ 0.123s]
writing 'bootloader'...
(bootloader) flashing partition ...
(bootloader) This may take a few seconds if a
(bootloader) different partition table is being
(bootloader) flashed since we need to backup
(bootloader) and restore a few partitions
(bootloader) Flashing primary GPT image...
(bootloader) Flashing backup GPT image...
(bootloader) flashing aboot ...
(bootloader) flashing sbl1 ...
(bootloader) flashing rpm ...
(bootloader) flashing tz ...
(bootloader) flashing sdi ...
(bootloader) flashing logo ...
OKAY [ 0.548s]
finished. total time: 0.674s
rebooting into bootloader...
OKAY [ 0.002s]
finished. total time: 0.003s
target reported max download size of 536870912 bytes
sending 'radio' (85422 KB)...
OKAY [ 2.720s]
writing 'radio'...
(bootloader) flashing modem ...
(bootloader) flashing mdm1m9kefs1 ...
(bootloader) flashing mdm1m9kefs2 ...
(bootloader) flashing mdm1m9kefs3 ...
(bootloader) flashing versions ...
OKAY [ 1.102s]
finished. total time: 3.824s
rebooting into bootloader...
OKAY [ 0.002s]
finished. total time: 0.003s
target reported max download size of 536870912 bytes
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
failed to allocate 1778160592 bytes
error: update package missing system.img
downloading 'boot.img'...
OKAY [ 0.393s]
booting...
OKAY [ 0.024s]
finished. total time: 0.419s
Press any key to exit...
As we can see, bootloader image flashes just fine
The radio image flashes just fine
System image on the other hand does not update complaining about missing .sig files:
fastboot -w update image-shamu-lmy47i.zip said:
target reported max download size of 536870912 bytes
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
failed to allocate 1778160592 bytes
error: update package missing system.img
Click to expand...
Click to collapse
The files inside this system zip are:
android-info.txt
boot.img
cache.img
recovery.img
system.img
userdata.img
Ironically the SuperSU image flashes just fine and reboots the phone
I am frustrated by the fact that the system image update step fails and nothing out there explains why? I have even tried to extract each of those images from the zip file and flashing them individually using the fastboot flashall but getting the same error as well as other errors.
Can anyone lend an assist on this and help me figure out how to overcome that hurdle PLEASE?
Follow method 2 here:
http://forum.xda-developers.com/showthread.php?t=2954008
Do not use flashall.
Also, please provide more information on the errors. That matters.
Evolution_Freak said:
Follow method 2 here:
http://forum.xda-developers.com/showthread.php?t=2954008
Do not use flashall.
Also, please provide more information on the errors. That matters.
Click to expand...
Click to collapse
I did provide everything step by step the only thing I didn't provide was the errors on the individual images that are within the update zip file. Which I suppose is my bad:
Code:
(bootloader) Motoboot: Unknown partition name
(bootloader) Preflash validation failed
and I have tried flashall last because documentation states it will do boot, recovery and system but I have also done them using individual commands too. But more on that after I take a look at what you posted in the link. Stay tuned. Thank you.
Alright, good news, it worked and thank you for pointing to the resource that allowed me to figure out why I was getting the partition errors, now I know.
I modified the batch file as follows:
Code:
PATH=%PATH%;"%SYSTEMROOT%\System32"
adb reboot bootloader
fastboot flash bootloader bootloader-shamu-moto-apq8084-71.08.img
fastboot reboot-bootloader
fastboot flash radio radio-shamu-d4.0-9625-02.95.img
fastboot reboot-bootloader
fastboot flash system system.img
fastboot flash userdata userdata.img
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot erase cache
fastboot flash cache cache.img
fastboot reboot-bootloader
fastboot boot CF-Auto-Root-shamu-shamu-nexus6.img
echo Press any key to exit...
pause >nul
exit
it went through the whole process and here is the resulting output:
Code:
C:\Users\Major\Desktop\shamu-lmy47i>flash-all.bat
< waiting for device >
target reported max download size of 536870912 bytes
sending 'bootloader' (3807 KB)...
OKAY [ 0.123s]
writing 'bootloader'...
(bootloader) flashing partition ...
(bootloader) This may take a few seconds if a
(bootloader) different partition table is being
(bootloader) flashed since we need to backup
(bootloader) and restore a few partitions
(bootloader) Flashing primary GPT image...
(bootloader) Flashing backup GPT image...
(bootloader) flashing aboot ...
(bootloader) flashing sbl1 ...
(bootloader) flashing rpm ...
(bootloader) flashing tz ...
(bootloader) flashing sdi ...
(bootloader) flashing logo ...
OKAY [ 0.508s]
finished. total time: 0.632s
rebooting into bootloader...
OKAY [ 0.002s]
finished. total time: 0.002s
< waiting for device >
target reported max download size of 536870912 bytes
sending 'radio' (85422 KB)...
OKAY [ 2.722s]
writing 'radio'...
(bootloader) flashing modem ...
(bootloader) flashing mdm1m9kefs1 ...
(bootloader) flashing mdm1m9kefs2 ...
(bootloader) flashing mdm1m9kefs3 ...
(bootloader) flashing versions ...
OKAY [ 1.110s]
finished. total time: 3.834s
rebooting into bootloader...
OKAY [ 0.002s]
finished. total time: 0.003s
< waiting for device >
target reported max download size of 536870912 bytes
sending sparse 'system' (522196 KB)...
OKAY [ 22.442s]
writing 'system'...
OKAY [ 7.691s]
sending sparse 'system' (510114 KB)...
OKAY [ 21.723s]
writing 'system'...
OKAY [ 6.674s]
sending sparse 'system' (514997 KB)...
OKAY [ 21.128s]
writing 'system'...
OKAY [ 7.778s]
sending sparse 'system' (189177 KB)...
OKAY [ 7.652s]
writing 'system'...
OKAY [ 2.328s]
finished. total time: 97.428s
target reported max download size of 536870912 bytes
erasing 'userdata'...
OKAY [ 11.844s]
sending 'userdata' (138868 KB)...
OKAY [ 4.518s]
writing 'userdata'...
OKAY [ 1.949s]
finished. total time: 18.315s
target reported max download size of 536870912 bytes
sending 'boot' (7681 KB)...
OKAY [ 0.247s]
writing 'boot'...
OKAY [ 0.110s]
finished. total time: 0.359s
target reported max download size of 536870912 bytes
sending 'recovery' (8273 KB)...
OKAY [ 0.266s]
writing 'recovery'...
OKAY [ 0.116s]
finished. total time: 0.384s
******** Did you mean to fastboot format this partition?
erasing 'cache'...
OKAY [ 0.045s]
finished. total time: 0.046s
target reported max download size of 536870912 bytes
erasing 'cache'...
OKAY [ 0.013s]
sending 'cache' (6248 KB)...
OKAY [ 0.204s]
writing 'cache'...
OKAY [ 0.097s]
finished. total time: 0.318s
rebooting into bootloader...
OKAY [ 0.002s]
finished. total time: 0.003s
< waiting for device >
downloading 'boot.img'...
OKAY [ 0.399s]
booting...
OKAY [ 0.035s]
finished. total time: 0.436s
Thank you for everyone's input and assistance here, you rock.
When trying to update I get the following error. I have attempted multiple updates thinking maybe I had to do some incremental ones before doing the most recent. rq1a.201205.008.zip is the oldest one that fails and all the more recent ones do also.
Code:
C:\platform-tools>flash-all
Sending 'bootloader' (8825 KB) OKAY [ 0.044s]
Writing 'bootloader' FAILED (remote: 'No such file or directory')
fastboot: error: Command failed
Rebooting into bootloader OKAY [ 0.001s]
Finished. Total time: 0.004s
< waiting for any device >
Sending 'radio_b' (82692 KB) OKAY [ 0.458s]
Writing 'radio_b' (bootloader) Flashing Pack version SSD:g8150-00075-201008-B-6891495
(bootloader) Flashing partition modem_b
OKAY [ 0.607s]
Finished. Total time: 1.634s
Rebooting into bootloader OKAY [ 0.041s]
Finished. Total time: 0.053s
--------------------------------------------
Bootloader Version...: c2f2-0.3-6648663
Baseband Version.....: g8150-00075-201008-B-6891495
Serial Number........: xxxxxxxxxxxxxxx
--------------------------------------------
extracting android-info.txt (0 MB) to RAM...
Checking 'product' OKAY [ 0.062s]
Checking 'version-bootloader' FAILED
Device version-bootloader is 'c2f2-0.3-6648663'.
Update requires 'c2f2-0.3-6863466'.
fastboot: error: requirements not met!
Press any key to exit...
sabindaman said:
When trying to update I get the following error. I have attempted multiple updates thinking maybe I had to do some incremental ones before doing the most recent. rq1a.201205.008.zip is the oldest one that fails and all the more recent ones do also.
Code:
C:\platform-tools>flash-all
Sending 'bootloader' (8825 KB) OKAY [ 0.044s]
Writing 'bootloader' FAILED (remote: 'No such file or directory')
fastboot: error: Command failed
Rebooting into bootloader OKAY [ 0.001s]
Finished. Total time: 0.004s
< waiting for any device >
Sending 'radio_b' (82692 KB) OKAY [ 0.458s]
Writing 'radio_b' (bootloader) Flashing Pack version SSD:g8150-00075-201008-B-6891495
(bootloader) Flashing partition modem_b
OKAY [ 0.607s]
Finished. Total time: 1.634s
Rebooting into bootloader OKAY [ 0.041s]
Finished. Total time: 0.053s
--------------------------------------------
Bootloader Version...: c2f2-0.3-6648663
Baseband Version.....: g8150-00075-201008-B-6891495
Serial Number........: xxxxxxxxxxxxxxx
--------------------------------------------
extracting android-info.txt (0 MB) to RAM...
Checking 'product' OKAY [ 0.062s]
Checking 'version-bootloader' FAILED
Device version-bootloader is 'c2f2-0.3-6648663'.
Update requires 'c2f2-0.3-6863466'.
fastboot: error: requirements not met!
Press any key to exit...
Click to expand...
Click to collapse
Are these the files in your platform tools? (These are from Jan. 2021 factory image). Also, are your platform tools up to date?
Lughnasadh said:
Are these the files in your platform tools? (These are from Jan. 2021 factory image). Also, are your platform tools up to date?
Click to expand...
Click to collapse
Yeah. they are all in there. I've done 3 other updates successfully and not had any issues. But when I try the January one or the previous 2 updates they all fail to flash the bootloader at the beginning and give me the same error about the bootloader version later on and abort the update.
platform tools is r30.0.5 which is most current as far as I can find
sabindaman said:
Yeah. they are all in there. I've done 3 other updates successfully and not had any issues. But when I try the January one or the previous 2 updates they all fail to flash the bootloader at the beginning and give me the same error about the bootloader version later on and abort the update.
platform tools is r30.0.5 which is most current as far as I can find
Click to expand...
Click to collapse
Do, are you saying you are on October update?
Jan, Dec, Nov don't install?
Tulsadiver said:
Do, are you saying you are on October update?
Jan, Dec, Nov don't install?
Click to expand...
Click to collapse
RP1A.201105.002 is the version I am running and most recent one that would successfully install.
sabindaman said:
RP1A.201105.002 is the version I am running and most recent one that would successfully install.
Click to expand...
Click to collapse
Have you tried installing your bootloader manually?
fastboot flash bootloader bootloader-coral-c2f2-0.3-6863466.img
Tulsadiver said:
Have you tried installing your bootloader manually?
fastboot flash bootloader bootloader-coral-c2f2-0.3-6863466.img
Click to expand...
Click to collapse
No luck
I don't know if it matters but on fastboot it has secure boot: yes while on the bootloader it has device state as unlocked
Code:
C:\platform-tools>fastboot flash bootloader bootloader-coral-c2f2-0.3-6863466.img
Sending 'bootloader' (8825 KB) OKAY [ 0.053s]
Writing 'bootloader' FAILED (remote: 'No such file or directory')
fastboot: error: Command failed
C:\platform-tools>
sabindaman said:
No luck
I don't know if it matters but on fastboot it has secure boot: yes while on the bootloader it has device state as unlocked
Code:
C:\platform-tools>fastboot flash bootloader bootloader-coral-c2f2-0.3-6863466.img
Sending 'bootloader' (8825 KB) OKAY [ 0.053s]
Writing 'bootloader' FAILED (remote: 'No such file or directory')
fastboot: error: Command failed
C:\platform-tools>
Click to expand...
Click to collapse
Have you tried settings/system/system update?
Maybe change slot to "a" and try it there?
Just throwing some things out there.
Tulsadiver said:
Have you tried settings/system/system update?
Maybe change slot to "a" and try it there?
Just throwing some things out there.
Click to expand...
Click to collapse
Well after a few days of checking system update it finally decided the December update existed and it would download it. At which put it into the most recent bootloader version. Thanks for help.
sabindaman said:
Well after a few days of checking system update it finally decided the December update existed and it would download it. At which put it into the most recent bootloader version. Thanks for help.
Click to expand...
Click to collapse
Great!
sabindaman said:
When trying to update I get the following error. I have attempted multiple updates thinking maybe I had to do some incremental ones before doing the most recent. rq1a.201205.008.zip is the oldest one that fails and all the more recent ones do also.
Code:
C:\platform-tools>flash-all
Sending 'bootloader' (8825 KB) OKAY [ 0.044s]
Writing 'bootloader' FAILED (remote: 'No such file or directory')
fastboot: error: Command failed
Rebooting into bootloader OKAY [ 0.001s]
Finished. Total time: 0.004s
< waiting for any device >
Sending 'radio_b' (82692 KB) OKAY [ 0.458s]
Writing 'radio_b' (bootloader) Flashing Pack version SSD:g8150-00075-201008-B-6891495
(bootloader) Flashing partition modem_b
OKAY [ 0.607s]
Finished. Total time: 1.634s
Rebooting into bootloader OKAY [ 0.041s]
Finished. Total time: 0.053s
--------------------------------------------
Bootloader Version...: c2f2-0.3-6648663
Baseband Version.....: g8150-00075-201008-B-6891495
Serial Number........: xxxxxxxxxxxxxxx
--------------------------------------------
extracting android-info.txt (0 MB) to RAM...
Checking 'product' OKAY [ 0.062s]
Checking 'version-bootloader' FAILED
Device version-bootloader is 'c2f2-0.3-6648663'.
Update requires 'c2f2-0.3-6863466'.
fastboot: error: requirements not met!
Press any key to exit...
Click to expand...
Click to collapse
Your bootloader is locked.
Here are a few commands to solve this problem. All you have to do is unlock the bootloader and after that you can flash your Google Pixel phone with any version.
1. https://download.highonandroid.com/file/Tools
download fastboot.zip
extract and open Command Prompt to this folder (Ctrl+Shift+right click mous button)
2.
To unlock the bootloader and enable partitions to be reflashed, run the
"fastboot flashing unlock" command (without quotes) on the device.
3. And running the "fastboot flashing unlock" command (without quotes) but requires the user to press a physical button on the device.That is ALLL. Francuz Barajevo
I had my bootloader unlocked and I still had the same issue.
The solution? Simply run the script again. When you get this error, the phone will be on the fastboot screen. Just run the script again and this time it will flash the new bootloader, reboot itself and then continue the process.
Good luck!
(for me, this happened on a Pixel 4a, while flashing the 2021 September update)
Lughnasadh said:
Are these the files in your platform tools? (These are from Jan. 2021 factory image). Also, are your platform tools up to date?
Click to expand...
Click to collapse
I don't have them. Where can I find them?
N-Gage4ever said:
I don't have them. Where can I find them?
Click to expand...
Click to collapse
Factory images
Platform Tools