Hello,
i am just thinking i bricked my Galaxy Nexus.
But first i will describe what happened:
My device was running fine with 4.3 Cyanonogenmod Nighlty builds for a few days but yesterday in the car the device suddenly was stuck in a bootloop.
After arriving home i tried to fix that by removing the battery and give it a few minutes.
But my device was stuck in a bootloop after that.
I tried to reflash ROM and RADIO few times but nothing helped.
I was in TWRP Recovery and wanted to get CWM just to rescue some files via USB before flashing stock ROM.
So i got the toolkit and tried to flash a recovery and the script told me all worked, but there seems not to be any recovery on the device anymore.
When i boot into bootloader and select Recovery i am just getting the battery symbol and nothing more happens.
I flashed a stock ROM via toolkit without wiping userdata but this did not help, too.
Now i am stuck with a device that does not seem to have a recovery and does not boot behind the Google Logo.
Also the device only reacts to the power button anymore when on external power via USB wire, not on battery.
Any suggestions how to continue or just rescue my files from the "sdcard" ?
myxor said:
Hello,
i am just thinking i bricked my Galaxy Nexus.
But first i will describe what happened:
My device was running fine with 4.3 Cyanonogenmod Nighlty builds for a few days but yesterday in the car the device suddenly was stuck in a bootloop.
After arriving home i tried to fix that by removing the battery and give it a few minutes.
But my device was stuck in a bootloop after that.
I tried to reflash ROM and RADIO few times but nothing helped.
I was in TWRP Recovery and wanted to get CWM just to rescue some files via USB before flashing stock ROM.
So i got the toolkit and tried to flash a recovery and the script told me all worked, but there seems not to be any recovery on the device anymore.
When i boot into bootloader and select Recovery i am just getting the battery symbol and nothing more happens.
I flashed a stock ROM via toolkit without wiping userdata but this did not help, too.
Now i am stuck with a device that does not seem to have a recovery and does not boot behind the Google Logo.
Also the device only reacts to the power button anymore when on external power via USB wire, not on battery.
Any suggestions how to continue or just rescue my files from the "sdcard" ?
Click to expand...
Click to collapse
Drop the toolkit, learn how to do it proper or stop flashing stuff before you hurt your device.
beekay201 said:
Drop the toolkit, learn how to it proper or stop flashing stuff before you hurt your device.
Click to expand...
Click to collapse
I guess it's already to late
I just tried to install the CWM Recovery via fastboot
D:\gn\adt-bundle-windows-x86_64
sending 'recovery' (6214 KB)...
OKAY [ 0.631s]
writing 'recovery'...
OKAY [ 0.759s]
finished. total time: 1.392s
D:\gn\adt-bundle-windows-x86_64
rebooting into bootloader...
OKAY [ 0.007s]
finished. total time: 0.007s
Click to expand...
Click to collapse
But when i select Recovery from the bootloader menu i only get the charging battery icon.
Anything i can do?
I've never had a similar experience so but from reading several similar topics I will suggest that you flash a factory image. Not a STOCK ROM, but the actual factory image. It *should* re-lock the boot loader and default you to complete stock.Your files will be gone but assuming the files aren't overwritten you can still recover them per the instructions on this thread. As others have suggested, lay off the toolkit. Without it, you will be absolutely sure as to what is going on with your phone. Read, read, read, read before doing anything you're unfamiliar with.
iLeopard said:
I've never had a similar experience so but from reading several similar topics I will suggest that you flash a factory image. Not a STOCK ROM, but the actual factory image. It *should* re-lock the boot loader and default you to complete stock.Your files will be gone but assuming the files aren't overwritten you can still recover them per the instructions on this thread. As others have suggested, lay off the toolkit. Without it, you will be absolutely sure as to what is going on with your phone. Read, read, read, read before doing anything you're unfamiliar with.
Click to expand...
Click to collapse
Thank you for your advices but the results are not what i hoped for:
After flashing the factory image from https://developers.google.com/android/nexus/images#instructions with the following output:
Code:
sending 'bootloader' (2308 KB)...
OKAY [ 0.236s]
writing 'bootloader'...
OKAY [ 0.605s]
finished. total time: 0.841s
rebooting into bootloader...
OKAY [ 0.007s]
finished. total time: 0.009s
< waiting for device >
sending 'radio' (12288 KB)...
OKAY [ 1.233s]
writing 'radio'...
OKAY [ 2.590s]
finished. total time: 3.824s
rebooting into bootloader...
OKAY [ 0.007s]
finished. total time: 0.007s
< waiting for device >
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
--------------------------------------------
Bootloader Version...: PRIMEMD04
Baseband Version.....: I9250XXLJ1
Serial Number........: XXXXXXXXXXXXXXXX (censored by author)
--------------------------------------------
checking product...
OKAY [ 0.006s]
checking version-bootloader...
OKAY [ 0.008s]
checking version-baseband...
OKAY [ 0.007s]
sending 'boot' (4376 KB)...
OKAY [ 0.438s]
writing 'boot'...
OKAY [ 0.380s]
sending 'recovery' (4924 KB)...
OKAY [ 0.497s]
writing 'recovery'...
OKAY [ 0.761s]
erasing 'system'...
OKAY [ 0.013s]
sending 'system' (474180 KB)...
OKAY [ 46.800s]
writing 'system'...
OKAY [ 47.830s]
erasing 'userdata'...
OKAY [ 0.550s]
formatting 'userdata' partition...
Creating filesystem with parameters:
Size: 14539534336
Block size: 4096
Blocks per group: 32768
Inodes per group: 8144
Inode size: 256
Journal blocks: 32768
Label:
Blocks: 3549691
Block groups: 109
Reserved block group size: 871
Created filesystem with 11/887696 inodes and 97200/3549691 blocks
sending 'userdata' (137559 KB)...
writing 'userdata'...
OKAY [ 25.975s]
erasing 'cache'...
OKAY [ 0.015s]
formatting 'cache' partition...
Creating filesystem with parameters:
Size: 452984832
Block size: 4096
Blocks per group: 32768
Inodes per group: 6912
Inode size: 256
Journal blocks: 1728
Label:
Blocks: 110592
Block groups: 4
Reserved block group size: 31
Created filesystem with 11/27648 inodes and 3566/110592 blocks
sending 'cache' (8832 KB)...
writing 'cache'...
OKAY [ 3.136s]
rebooting...
finished. total time: 126.458s
Press any key to exit...
the device is stuck in the Google Logo now for about 10 Minutes and nothing is happening :crying:
Was this issued using flash-all.bat?
Sent from my Galaxy Nexus using xda app-developers app
myxor said:
Thank you for your advices but the results are not what i hoped for:
After flashing the factory image from https://developers.google.com/android/nexus/images#instructions with the following output:
Code:
sending 'bootloader' (2308 KB)...
OKAY [ 0.236s]
writing 'bootloader'...
OKAY [ 0.605s]
finished. total time: 0.841s
rebooting into bootloader...
OKAY [ 0.007s]
finished. total time: 0.009s
< waiting for device >
sending 'radio' (12288 KB)...
OKAY [ 1.233s]
writing 'radio'...
OKAY [ 2.590s]
finished. total time: 3.824s
rebooting into bootloader...
OKAY [ 0.007s]
finished. total time: 0.007s
< waiting for device >
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
--------------------------------------------
Bootloader Version...: PRIMEMD04
Baseband Version.....: I9250XXLJ1
Serial Number........: XXXXXXXXXXXXXXXX (censored by author)
--------------------------------------------
checking product...
OKAY [ 0.006s]
checking version-bootloader...
OKAY [ 0.008s]
checking version-baseband...
OKAY [ 0.007s]
sending 'boot' (4376 KB)...
OKAY [ 0.438s]
writing 'boot'...
OKAY [ 0.380s]
sending 'recovery' (4924 KB)...
OKAY [ 0.497s]
writing 'recovery'...
OKAY [ 0.761s]
erasing 'system'...
OKAY [ 0.013s]
sending 'system' (474180 KB)...
OKAY [ 46.800s]
writing 'system'...
OKAY [ 47.830s]
erasing 'userdata'...
OKAY [ 0.550s]
formatting 'userdata' partition...
Creating filesystem with parameters:
Size: 14539534336
Block size: 4096
Blocks per group: 32768
Inodes per group: 8144
Inode size: 256
Journal blocks: 32768
Label:
Blocks: 3549691
Block groups: 109
Reserved block group size: 871
Created filesystem with 11/887696 inodes and 97200/3549691 blocks
sending 'userdata' (137559 KB)...
writing 'userdata'...
OKAY [ 25.975s]
erasing 'cache'...
OKAY [ 0.015s]
formatting 'cache' partition...
Creating filesystem with parameters:
Size: 452984832
Block size: 4096
Blocks per group: 32768
Inodes per group: 6912
Inode size: 256
Journal blocks: 1728
Label:
Blocks: 110592
Block groups: 4
Reserved block group size: 31
Created filesystem with 11/27648 inodes and 3566/110592 blocks
sending 'cache' (8832 KB)...
writing 'cache'...
OKAY [ 3.136s]
rebooting...
finished. total time: 126.458s
Press any key to exit...
the device is stuck in the Google Logo now for about 10 Minutes and nothing is happening :crying:
Click to expand...
Click to collapse
4.3 first bootup times is much slower than previous versions. Let it boot until it reboots itself or something. If after 45min it still going at it, I think you have two options:
- my first suggestion is to return to the bootloader, and follow this thread's first post. No need to reflash bootloader or radio, as far as I can tell, nothing's wrong with those two. Erase, then format all the remaining partitions.
Code:
fastboot erase partition_name
fastboot format partition_name
Flash all the remaining partitions: boot, recovery (a custom recovery if you'd like, beware of 4.3 changes - not sure all the custom recoveries have updated accordingly, check dev section), system, userdata, cache.
Code:
fastboot flash partition /path/to/filename.img
- my second suggestion is that you search of a way to enable adbd, to see whats going on. That might require some extra steps, such as editing init.rc i believe.
Anyways, if you return to the bootloader, and try to
Code:
fastboot boot /path/to/cwm_or_twrp.img
What does it do? Can you use your custom recovery now?
beekay201 said:
4.3 first bootup times is much slower than previous versions. Let it boot until it reboots itself or something. If after 45min it still going at it, I think you have two options:
- my first suggestion is to return to the bootloader, and follow this thread's first post. No need to reflash bootloader or radio, as far as I can tell, nothing's wrong with those two. Erase, then format all the remaining partitions.
Code:
fastboot erase partition_name
fastboot format partition_name
Flash all the remaining partitions: boot, recovery (a custom recovery if you'd like, beware of 4.3 changes - not sure all the custom recoveries have updated accordingly, check dev section), system, userdata, cache.
Code:
fastboot flash partition /path/to/filename.img
- my second suggestion is that you search of a way to enable adbd, to see whats going on. That might require some extra steps, such as editing init.rc i believe.
Anyways, if you return to the bootloader, and try to
Code:
fastboot boot /path/to/cwm_or_twrp.img
What does it do? Can you use your custom recovery now?
Click to expand...
Click to collapse
I ran through the linked post and erased + formated all possible partitions.
Is it normal that o can not format some partitions like the recovery partition?
Code:
>fastboot format recovery
formatting 'recovery' partition...
Formatting is not supported for filesystem with type 'raw'.
FAILED ()
finished. total time: 0.009s
After that i flashed the partitions once by once per
Code:
fastboot flash partitions /path/file.img
with the files from the factory image.
Sadly no boot possible.
Then i tried to boot my recovery by
Code:
fastboot boot /path/to/cwm_or_twrp.img
but it happens the same as before:
after selecting to boot into recovery from fastboot mode the google logo appears for a few seconds then the screens goes black and returns with the battery charging symbol.
After turning the phone off and booting again into fastboot mode i can read in red letters: "FASTBOOT MODE - NO BOOT OR RECOVERY IMG".
This stays the same after flashing a recovery image via fastboot :crying:
myxor said:
I ran through the linked post and erased + formated all possible partitions.
Is it normal that o can not format some partitions like the recovery partition?
Code:
>fastboot format recovery
formatting 'recovery' partition...
Formatting is not supported for filesystem with type 'raw'.
FAILED ()
finished. total time: 0.009s
After that i flashed the partitions once by once per
Code:
fastboot flash partitions /path/file.img
with the files from the factory image.
Sadly no boot possible.
Then i tried to boot my recovery by
Code:
fastboot boot /path/to/cwm_or_twrp.img
but it happens the same as before:
after selecting to boot into recovery from fastboot mode the google logo appears for a few seconds then the screens goes black and returns with the battery charging symbol.
After turning the phone off and booting again into fastboot mode i can read in red letters: "FASTBOOT MODE - NO BOOT OR RECOVERY IMG".
This stays the same after flashing a recovery image via fastboot :crying:
Click to expand...
Click to collapse
Use omapflash to restore your bootloader. See this thread's post with useful links. http://forum.xda-developers.com/showthread.php?t=1812959
I sent in the device to the repair and got it back a few days ago.
Some "broken parts" were changed and i got a new battery.
Now my Galaxy Nexus works again like a charm
Don't really know what parts were broken but it seemed that it was a hardware failure.
Thanks to everyone who helped! :good:
Related
First i`m sorry for my english. Now i going to course but this is level low A2
Hello guys, i have a problem. Afer installed Paranoid rom to my Nexus 2013 WiFi. Computer doesent see my tablet. So i installed Linux Mint and now my computer see tablet but only in Fastboot. I will return to stock, but i can only use fastboot. WUG doesnt work because ADB dosent work.
So my question is How i can make return to stock with fastboot
wnuczus said:
First i`m sorry for my english. Now i going to course but this is level low A2
Hello guys, i have a problem. Afer installed Paranoid rom to my Nexus 2013 WiFi. Computer doesent see my tablet. So i installed Linux Mint and now my computer see tablet but only in Fastboot. I will return to stock, but i can only use fastboot. WUG doesnt work because ADB dosent work.
So my question is How i can make return to stock with fastboot
Click to expand...
Click to collapse
Download the factory image for your device:
https://developers.google.com/android/nexus/images
Extracts the files
Open the folder in a terminal
Run the flash-all.sh file
Sent from my Nexus 7 using Tapatalk
---------- Post added at 06:12 PM ---------- Previous post was at 06:08 PM ----------
http://m.youtube.com/watch?v=mkT089qv1vs&desktop_uri=/watch?v=mkT089qv1vs. I didn' see the video but it should be ok
Sent from my Nexus 7 using Tapatalk
thanks you thanks you thanks you
now working
Code:
[email protected] ~/Pobrane $ sh flash-all.sh
sending 'bootloader' (3911 KB)...
OKAY [ 0.129s]
writing 'bootloader'...
OKAY [ 1.753s]
finished. total time: 1.882s
rebooting into bootloader...
OKAY [ 0.006s]
finished. total time: 0.006s
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
--------------------------------------------
Bootloader Version...: FLO-03.15
Baseband Version.....: none
Serial Number........: 05ef7863
--------------------------------------------
checking product...
OKAY [ 0.003s]
checking version-bootloader...
OKAY [ 0.004s]
sending 'boot' (6880 KB)...
OKAY [ 0.221s]
writing 'boot'...
OKAY [ 0.399s]
sending 'recovery' (7424 KB)...
OKAY [ 0.238s]
writing 'recovery'...
OKAY [ 0.413s]
erasing 'system'...
OKAY [ 0.568s]
sending 'system' (603447 KB)...
OKAY [ 18.909s]
writing 'system'...
OKAY [ 39.959s]
erasing 'userdata'...
OKAY [ 17.748s]
formatting 'userdata' partition...
Creating filesystem with parameters:
Size: 13342060544
Block size: 4096
Blocks per group: 32768
Inodes per group: 8144
Inode size: 256
Journal blocks: 32768
Label:
Blocks: 3257339
Block groups: 100
Reserved block group size: 799
Created filesystem with 11/814400 inodes and 91881/3257339 blocks
sending 'userdata' (137198 KB)...
writing 'userdata'...
OKAY [ 12.826s]
erasing 'cache'...
OKAY [ 0.069s]
formatting 'cache' partition...
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
sending 'cache' (10984 KB)...
writing 'cache'...
OKAY [ 0.990s]
rebooting...
finished. total time: 92.366s
log is ok?
All ok
Sent from my Nexus 7 using Tapatalk
Hey fellaz!
I messed up woth my n7 2013 lte.
I am getting error message "not enough space" trying to flash system via fastboot.
I could flash bootloader & radio only.
I tried to restore to stock manually (via fastboot) and using Nexus Toolkit ...
flash-all.bat doesn't work as well
How to fix?
P.s. Can't share more detailed info (log) as I'm not at my pc now.
LOCKDOC_UA said:
Hey fellaz!
I messed up woth my n7 2013 lte.
I am getting error message "not enough space" trying to flash system via fastboot.
I could flash bootloader & radio only.
I tried to restore to stock manually (via fastboot) and using Nexus Toolkit ...
flash-all.bat doesn't work as well
How to fix?
P.s. Can't share more detailed info (log) as I'm not at my pc now.
Click to expand...
Click to collapse
Check the drive containing the temp directory on your PC to make sure it isn't full.
sfhub said:
Check the drive containing the temp directory on your PC to make sure it isn't full.
Click to expand...
Click to collapse
18Gigs free. Looks pretty enough
LOCKDOC_UA said:
18Gigs free. Looks pretty enough
Click to expand...
Click to collapse
Boot into recovery, do wipe data/factory reset, then try the factory image again
sfhub said:
Boot into recovery, do wipe data/factory reset, then try the factory image again
Click to expand...
Click to collapse
I couldn't boot into recovery even after I flashed it via fastboot. Tablet boots up into bootloader mode directly. Doesn't metter if I press vol up+power or enter Recovery from bootloader mode.
But anyway I will try again once I come back home.
hi, i got this weird problem with my galaxy nexus, after i turn it on, after 10-15 second everything crash and it reboot itself.
so, the problem is, no matter what i flash, i always got that system with all my app installed, i tryed manually from adb, with toolkit, formatting data, system, cache, nothing, i always got that system with all my apps, i tried, in that 10-15 seconds, to unistall some app, but after the reboot the app is still there. i can't install a custom recovery, i can't install any other rom, please someone help me because i have no idea on what to do
also, i think i have some problem with the folder data, since i can't even flash a recovery (tryed philz, cwm,twpr) i manage to boot philz, then boot aroma file manager from a usb with otg, i've tried to delete some app in "data/app"
then tried to restart, the app are still there, i also deleted all my photo and download folder, refreshed from aroma and the folder was empty, rebooted the phone and all my photo and download was there(yes, always in that 15 second of time before the phone reboot itself)
another try, after all of this(i tried to flash a stock rom, it take almost 1 hour and i got no error)
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot devices
014E054A18005017 fastboot
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash bootloader C:\Use
rs\Zed\Downloads\takju-jwr66y-factory-5104ab1d\takju-jwr66y\bootloader-maguro-pr
imemd04.img
sending 'bootloader' (2308 KB)...
OKAY [ 0.226s]
writing 'bootloader'...
OKAY [ 7.934s]
finished. total time: 8.162s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.008s]
finished. total time: 0.009s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash radio C:\Users\Ze
d\Downloads\takju-jwr66y-factory-5104ab1d\takju-jwr66y\radio-maguro-i9250xxlj1.i
mg
sending 'radio' (12288 KB)...
OKAY [ 1.174s]
writing 'radio'...
OKAY [ 4.357s]
finished. total time: 5.535s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.007s]
finished. total time: 0.008s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot -w update C:\Users\Zed\
Downloads\takju-jwr66y-factory-5104ab1d\takju-jwr66y\image-takju-jwr66y.zip
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
archive does not contain 'vendor.img'
Creating filesystem with parameters:
Size: 14539534336
Block size: 4096
Blocks per group: 32768
Inodes per group: 8144
Inode size: 256
Journal blocks: 32768
Label:
Blocks: 3549691
Block groups: 109
Reserved block group size: 871
Created filesystem with 11/887696 inodes and 97200/3549691 blocks
Creating filesystem with parameters:
Size: 452984832
Block size: 4096
Blocks per group: 32768
Inodes per group: 6912
Inode size: 256
Journal blocks: 1728
Label:
Blocks: 110592
Block groups: 4
Reserved block group size: 31
Created filesystem with 11/27648 inodes and 3566/110592 blocks
--------------------------------------------
Bootloader Version...: PRIMEMD04
Baseband Version.....: I9250XXLJ1
Serial Number........: 014E054A18005017
--------------------------------------------
checking product...
OKAY [ 0.006s]
checking version-bootloader...
OKAY [ 0.010s]
checking version-baseband...
OKAY [ 0.009s]
sending 'boot' (4376 KB)...
OKAY [ 0.422s]
writing 'boot'...
OKAY [ 2.541s]
sending 'recovery' (4924 KB)...
OKAY [ 0.474s]
writing 'recovery'...
OKAY [ 4.513s]
erasing 'system'...
OKAY [ 0.009s]
sending 'system' (479248 KB)...
OKAY [ 45.132s]
writing 'system'...
OKAY [1613.721s]
erasing 'userdata'...
OKAY [ 0.034s]
sending 'userdata' (137559 KB)...
OKAY [ 12.945s]
writing 'userdata'...
OKAY [243.805s]
erasing 'cache'...
OKAY [ 0.008s]
sending 'cache' (8832 KB)...
OKAY [ 0.839s]
writing 'cache'...
OKAY [ 14.468s]
rebooting...
finished. total time: 1938.998s
C:\Program Files (x86)\Minimal ADB and Fastboot>
------------------------------------------------------------------------------------------------
i reboot my phone, and ALL my previous app, settings, launcher is still there, like nothing happen, and of course i still got the same error, after like 15 seconds the phone reboot
Sounds like memory problem to me. Eventually you will need to change the motherboard on your GNex
Sent from my RCT6573W23
AdmiralulNipples said:
Sounds like memory problem to me. Eventually you will need to change the motherboard on your GNex
Sent from my RCT6573W23
Click to expand...
Click to collapse
yeah after reading lots of thread i was thinking about that, not worth to change the motherboard
Well my GNex experienced some problems 2 weeks ago. I found a second hand motherboard for like 20$ online. The phone works like a charm
Sent from my RCT6573W23
AdmiralulNipples said:
Well my GNex experienced some problems 2 weeks ago. I found a second hand motherboard for like 20$ online. The phone works like a charm
Sent from my RCT6573W23
Click to expand...
Click to collapse
nice! i'm gonna try to look if i found one then
need help unbricking my pixel xl.
i downloaded the factory image from google and ran the flashall.bat but it keeps failing.
target reported max download size of 536870912 bytes
sending 'bootloadera' (32820 KB)...
OKAY [ 0.770s]
writing 'bootloadera'...
(bootloader) Valid bootloader version.
OKAY [ 1.038s]
finished. total time: 1.812s
rebooting into bootloader...
FAILED (command write failed (Unknown error))
finished. total time: 5.009s
target reported max download size of 536870912 bytes
sending 'radioa' (57048 KB)...
OKAY [ 1.302s]
writing 'radioa'...
OKAY [ 0.897s]
finished. total time: 2.201s
rebooting into bootloader...
OKAY [ 0.014s]
finished. total time: 0.016s
< waiting for any device >
target reported max download size of 536870912 bytes
archive does not contain 'boot.sig'
archive does not contain 'recovery.img'
archive does not contain 'system.sig'
archive does not contain 'vendor.sig'
wiping userdata...
Creating filesystem with parameters:
Size: 122633060352
Block size: 4096
Blocks per group: 32768
Inodes per group: 8192
Inode size: 256
Journal blocks: 32768
Label:
Blocks: 29939712
Block groups: 914
Reserved block group size: 1024
Created filesystem with 11/7487488 inodes and 518062/29939712 blocks
--------------------------------------------
Bootloader Version...: 8996-012001-1608281716
Baseband Version.....: 8996-012511-1609191801
Serial Number........: HT69D0200852
--------------------------------------------
checking product...
OKAY [ 0.050s]
checking version-bootloader...
OKAY [ 0.049s]
checking version-baseband...
OKAY [ 0.048s]
sending 'boota' (26481 KB)...
OKAY [ 0.641s]
writing 'boota'...
(bootloader) Flashing active slot "_a"
FAILED (remote: partition [boota] doesn't exist)
finished. total time: 1.097s
Press any key to exit...
I had the same problem. You need to extract everything within the file you downloaded for the factory in same directory(there should be another zip in there)... and then flash everything individually like the flash all file would do. So flash bootloader... Radio... (Reboot bootloader after this****)... And then flash everything else individually.. then try and start phone
I thought I read that you need the latest SDK in order for flash-all to work. I ran into issues like this when trying to restore my Pixel C to stock. As mentioned, flashing each image separately will work as well.
Shacocka said:
I had the same problem. You need to extract everything within the file you downloaded for the factory in same directory(there should be another zip in there)... and then flash everything individually like the flash all file would do. So flash bootloader... Radio... (Reboot bootloader after this****)... And then flash everything else individually.. then try and start phone
Click to expand...
Click to collapse
What he said
Mike02z said:
I thought I read that you need the latest SDK in order for flash-all to work. I ran into issues like this when trying to restore my Pixel C to stock. As mentioned, flashing each image separately will work as well.
Click to expand...
Click to collapse
I have old sdk and still can flash. You just have to do each step manually.
SDK platform-tools 25 is required for fastboot to automatically recognize a partition being used as the default partition. It is the only version of fastboot that can handle the Pixel partition layout using "fastboot flash update.zip" or any flash scripts which rely on this automated process.
Hey all,
I recently got a Pixel 2 XL, and decided to unlock bootloader, and install Resurrection Remix. All went ok, until I got back a message stating, the stock images were incorrect. So, I decided to just go back to stock, and go back to it later. Well, I got the factory images from Google.
Im using Ubuntu 18.04. Within terminal I used ./flash-all.sh It kept coming back as, "Fastboot too old".
if ! grep -q dtbo.sig $(which fastboot); then
echo "fastboot too old"
exit 1
fi
fastboot flash bootloader bootloader-taimen-tmz12bb.img
fastboot reboot-bootloader
sleep 5
fastboot flash radio radio-taimen-g8998-00202-1802061358.img
fastboot reboot-bootloader
sleep 5
So, I removed the first bit of script, and it starts to download. But, it doesnt appear to download correctly. Still on RR when I restart? Heres the script that comes back:
target reported max download size of 536870912 bytes
sending 'bootloaderb' (36344 KB)...
OKAY [ 1.025s]
writing 'bootloaderb'...
OKAY [ 0.374s]
finished. total time: 1.399s
rebooting into bootloader...
OKAY [ 0.000s]
finished. total time: 0.201s
target reported max download size of 536870912 bytes
sending 'radiob' (60412 KB)...
OKAY [ 1.768s]
writing 'radiob'...
OKAY [ 0.588s]
finished. total time: 2.356s
rebooting into bootloader...
OKAY [ 0.000s]
finished. total time: 0.201s
target reported max download size of 536870912 bytes
archive does not contain 'boot.sig'
archive does not contain 'recovery.img'
archive does not contain 'system.sig'
archive does not contain 'vendor.sig'
wiping userdata...
Creating filesystem with parameters:
Size: 56946044928
Block size: 4096
Blocks per group: 32768
Inodes per group: 8192
Inode size: 256
Journal blocks: 32768
Label:
Blocks: 13902843
Block groups: 425
Reserved block group size: 1024
Created filesystem with 11/3481600 inodes and 264598/13902843 blocks
--------------------------------------------
Bootloader Version...: TMZ12bb
Baseband Version.....: g8998-00202-1802061358
Serial Number........: 712KPAE1212112
--------------------------------------------
checking product...
OKAY [ 0.000s]
checking version-bootloader...
OKAY [ 0.000s]
checking version-baseband...
OKAY [ 0.000s]
sending 'bootb' (40960 KB)...
OKAY [ 1.315s]
writing 'bootb'...
FAILED (remote: No such partition.)
finished. total time: 1.320s
I have never really run into this on a Google device. If anyone out there has any insight for me, id really appreciate it. Ill buy a beer to anyone who can help me out.
You could've just ignored that. It doesn't interfere with the device. Just reflash how you normally do then if you get that message again just flash the vendor image.
Sent from my SM-G965U using Tapatalk
Well, after much research, and experimenting, I found that using the oldest image, from Sept 2017, fixed my issue. This whole time I was using the newest April image. Defiantly different with the a & b partition. That threw me off. But, all is well in Pixel land now.
I just received my Android 10 update and after the update when it asked to reboot I tapped reboot and now it has been stuck in a continuous bootloop. My phone was not rooted or modded in any way. I was able to boot into the recovery selection menu but cant go into the actual recovery (it just says "no item" when I select recovery).
Any help/suggestions?
You can reflash the ROM using the full OTA package, as is stated by Google in https://developers.google.com/android/ota : This page contains full OTA update packages that allow you to restore your Nexus or Pixel device's original factory firmware. You will find these files useful if you have experienced a failure to take an OTA. This has the same effect as flashing the corresponding factory image, but without the need to wipe the device or unlock the bootloader." You also have in that page instructions of the whole process.
All you need to do is reboot into recovery, enter adb sideload mode from whitin it and send the zip OTA file using your PC and adb. Download QP1A.190711.020 version under Pixel 2 XL.
In order to boot into recovery, when you see the Android robot with the "no item" message keep pressed the power button and then short-press volume up until the recovery options show up.
It after that it's still failing, just format within recovery or flash the full firmware stock package.
fdgd1998 said:
You can reflash the ROM using the full OTA package, as is stated by Google in https://developers.google.com/android/ota : This page contains full OTA update packages that allow you to restore your Nexus or Pixel device's original factory firmware. You will find these files useful if you have experienced a failure to take an OTA. This has the same effect as flashing the corresponding factory image, but without the need to wipe the device or unlock the bootloader." You also have in that page instructions of the whole process.
All you need to do is reboot into recovery, enter adb sideload mode from whitin it and send the zip OTA file using your PC and adb. Download QP1A.190711.020 version under Pixel 2 XL.
In order to boot into recovery, when you see the Android robot with the "no item" message keep pressed the power button and then short-press volume up until the recovery options show up.
It after that it's still failing, just format within recovery or flash the full firmware stock package.
Click to expand...
Click to collapse
thank you for the helpful reply
i had already started the process and have already downloaded all the files
but i cant unlock the bootloader as it says in the tutorial
am i doing something wrong? or is there any way to flash without unlocking the bootloader?
Edit: I dont have the "oem unlock" option turned on.
PLZ HELP
areebiqbal said:
thank you for the helpful reply
i had already started the process and have already downloaded all the files
but i cant unlock the bootloader as it says in the tutorial
am i doing something wrong? or is there any way to flash without unlocking the bootloader?
Edit: I dont have the "oem unlock" option turned on.
PLZ HELP
Click to expand...
Click to collapse
Are you flashing the OTA or the full firmware? For the OTA bootloader unlock isn't necessary.
And in the instructions are stated the opposite, you must have misread it.
fdgd1998 said:
Are you flashing the OTA or the full firmware? For the OTA bootloader unlock isn't necessary.
And in the instructions are stated the opposite, you must have misread it.
Click to expand...
Click to collapse
hi, so luckily i had oem unlocking checked before this happened, but after the october update ive been stuck in bootloop.
ive tried both sideloading the ota in recovery, and also full firmware flash via fastboot.
after several attempts at both, i can't seem to access the recovery and bootloop persists.
any ideas?
[pixel sailfish never been rooted]
ku81na said:
hi, so luckily i had oem unlocking checked before this happened, but after the october update ive been stuck in bootloop.
ive tried both sideloading the ota in recovery, and also full firmware flash via fastboot.
after several attempts at both, i can't seem to access the recovery and bootloop persists.
any ideas?
[pixel sailfish never been rooted]
Click to expand...
Click to collapse
Have you looked into the Dueces recovery scrip?
https://forum.xda-developers.com/pi...ol-deuces-bootloop-recovery-flashing-t3704761
no dice. appreciate the suggestion though
ku81na said:
no dice. appreciate the suggestion though
Click to expand...
Click to collapse
if you can confirm a couple things for me....
Are you actually getting into the recovery, but not seeing any "items"; because in stock recovery, you just see a broken/dead android image, and only get selections revealed/not-hidden but holding the volume-up & power button at the same time momentarily.
But, then again, you claim that you have attempted to "sideload the ota in recovery", so I imagine you already did this…but then, again again, you don’t describe what “error” or outcome actually happened and it could possibly be that, when you attempted, you just couldn’t or didn’t know how to get into the stock recovery…
Also, the recovery resides in the boot partition; I suggest you download the Full Factory image file (from the Google Developers site), extract it until you can find the boot.img, then manually flash it to overwrite and maybe fix the boot & recovery; to further explain, copy the extracted “boot.img” file to platform-tools folder where adb and fastboot reside, then run the command “fastboot flash boot boot.img” – although, if the flash-all is successfully executed, it would be doing this anyways…..
Which brings me to my next thing…if you could edit the “flash-all.bat” file and remove the word “exit” at the end – and for that matter, if you wish to save your data, remove the -w as well – and if you could please copy the output/log of you running the flash-all; usually this resolves everything & it all, so maybe it’s here that something is going wrong…
And running Deuce’s famous rescue script has saved/recovered countless people and their device (taimen)…it definitely is a good idea to attempt it…
But, then again, this is assuming that you made sure to run (and successfully execute) the fastboot command “fastboot flashing unlock” and/or (depending on your bootloader version) “fastboot flashing unlock_critical”.
Good luck, hopefully you can get back to me/us on some of this stuff, and hopefully all this ends up being helpful…
simplepinoi177 said:
if you can confirm a couple things for me....
Are you actually getting into the recovery, but not seeing any "items"; because in stock recovery, you just see a broken/dead android image, and only get selections revealed/not-hidden but holding the volume-up & power button at the same time momentarily.
But, then again, you claim that you have attempted to "sideload the ota in recovery", so I imagine you already did this…but then, again again, you don’t describe what “error” or outcome actually happened and it could possibly be that, when you attempted, you just couldn’t or didn’t know how to get into the stock recovery…
Also, the recovery resides in the boot partition; I suggest you download the Full Factory image file (from the Google Developers site), extract it until you can find the boot.img, then manually flash it to overwrite and maybe fix the boot & recovery; to further explain, copy the extracted “boot.img” file to platform-tools folder where adb and fastboot reside, then run the command “fastboot flash boot boot.img” – although, if the flash-all is successfully executed, it would be doing this anyways…..
Which brings me to my next thing…if you could edit the “flash-all.bat” file and remove the word “exit” at the end – and for that matter, if you wish to save your data, remove the -w as well – and if you could please copy the output/log of you running the flash-all; usually this resolves everything & it all, so maybe it’s here that something is going wrong…
And running Deuce’s famous rescue script has saved/recovered countless people and their device (taimen)…it definitely is a good idea to attempt it…
But, then again, this is assuming that you made sure to run (and successfully execute) the fastboot command “fastboot flashing unlock” and/or (depending on your bootloader version) “fastboot flashing unlock_critical”.
Good luck, hopefully you can get back to me/us on some of this stuff, and hopefully all this ends up being helpful…
Click to expand...
Click to collapse
yes i've tried everything you've suggested (flashing boot separately/removing exit from flash-all/running deuces script), however i haven't been able to access the recovery since i last messaged so i haven't been able to retry an ota flash from recovery. (the screen is all black and a green line of fuzz blinks across the middle of the screen when holding power and volume up) i did however get into it successfully once, and when i did there were no errors at all.
the strange thing is there are no errors when flashing either. it just does not get passed "Google" without rebooting. i just tried another flash-all after flashing unlock & unlock_critical so here is the full log in case im missing something:
target reported max download size of 536870912 bytes
sending 'bootloader_b' (32480 KB)...
OKAY [ 0.847s]
writing 'bootloader_b'...
(bootloader) Valid bootloader version.
(bootloader) Flashing active slot "_b"
(bootloader) Flashing active slot "_b"
OKAY [ 4.107s]
finished. total time: 4.965s
rebooting into bootloader...
OKAY [ 0.046s]
finished. total time: 0.051s
target reported max download size of 536870912 bytes
sending 'radio_b' (57156 KB)...
OKAY [ 1.434s]
writing 'radio_b'...
OKAY [ 0.458s]
finished. total time: 1.903s
rebooting into bootloader...
OKAY [ 0.050s]
finished. total time: 0.055s
target reported max download size of 536870912 bytes
archive does not contain 'boot.sig'
archive does not contain 'boot_other.img'
archive does not contain 'recovery.img'
archive does not contain 'system.sig'
archive does not contain 'system.sig'
archive does not contain 'vendor.sig'
archive does not contain 'vendor_other.img'
wiping userdata...
Creating filesystem with parameters:
Size: 26663190528
Block size: 4096
Blocks per group: 32768
Inodes per group: 8192
Inode size: 256
Journal blocks: 32768
Label:
Blocks: 6509568
Block groups: 199
Reserved block group size: 1024
Created filesystem with 11/1630208 inodes and 146354/6509568 blocks
--------------------------------------------
Bootloader Version...: 8996-012001-1908071822
Baseband Version.....: 8996-130361-1905270421
Serial Number........: FXXXXXXXXXXX
--------------------------------------------
checking product...
OKAY [ 0.050s]
checking version-bootloader...
OKAY [ 0.046s]
checking version-baseband...
OKAY [ 0.046s]
sending 'boot_b' (30793 KB)...
OKAY [ 0.797s]
writing 'boot_b'...
OKAY [ 0.294s]
erasing 'system_b'...
OKAY [ 0.316s]
sending sparse 'system_b' 1/4 (524284 KB)...
OKAY [ 13.692s]
writing 'system_b' 1/4...
OKAY [ 3.460s]
sending sparse 'system_b' 2/4 (524284 KB)...
OKAY [ 13.802s]
writing 'system_b' 2/4...
OKAY [ 3.481s]
sending sparse 'system_b' 3/4 (524284 KB)...
OKAY [ 13.816s]
writing 'system_b' 3/4...
OKAY [ 3.451s]
sending sparse 'system_b' 4/4 (461052 KB)...
OKAY [ 11.950s]
writing 'system_b' 4/4...
OKAY [ 3.087s]
erasing 'system_a'...
OKAY [ 0.246s]
sending 'system_a' (298348 KB)...
OKAY [ 7.005s]
writing 'system_a'...
OKAY [ 2.036s]
erasing 'vendor_b'...
OKAY [ 0.112s]
sending 'vendor_b' (259272 KB)...
OKAY [ 6.400s]
writing 'vendor_b'...
OKAY [ 1.747s]
Setting current slot to 'b'...
OKAY [ 0.081s]
erasing 'userdata'...
OKAY [ 1.853s]
sending 'userdata' (138957 KB)...
OKAY [ 3.089s]
writing 'userdata'...
OKAY [ 1.293s]
rebooting...
finished. total time: 92.497s
Press any key to exit...
ku81na said:
yes i've tried everything you've suggested (flashing boot separately/removing exit from flash-all/running deuces script), however i haven't been able to access the recovery since i last messaged so i haven't been able to retry an ota flash from recovery. (the screen is all black and a green line of fuzz blinks across the middle of the screen when holding power and volume up) i did however get into it successfully once, and when i did there were no errors at all.
the strange thing is there are no errors when flashing either. it just does not get passed "Google" without rebooting. i just tried another flash-all after flashing unlock & unlock_critical so here is the full log in case im missing something:
target reported max download size of 536870912 bytes
sending 'bootloader_b' (32480 KB)...
OKAY [ 0.847s]
writing 'bootloader_b'...
(bootloader) Valid bootloader version.
(bootloader) Flashing active slot "_b"
(bootloader) Flashing active slot "_b"
OKAY [ 4.107s]
finished. total time: 4.965s
rebooting into bootloader...
OKAY [ 0.046s]
finished. total time: 0.051s
target reported max download size of 536870912 bytes
sending 'radio_b' (57156 KB)...
OKAY [ 1.434s]
writing 'radio_b'...
OKAY [ 0.458s]
finished. total time: 1.903s
rebooting into bootloader...
OKAY [ 0.050s]
finished. total time: 0.055s
target reported max download size of 536870912 bytes
archive does not contain 'boot.sig'
archive does not contain 'boot_other.img'
archive does not contain 'recovery.img'
archive does not contain 'system.sig'
archive does not contain 'system.sig'
archive does not contain 'vendor.sig'
archive does not contain 'vendor_other.img'
wiping userdata...
Creating filesystem with parameters:
Size: 26663190528
Block size: 4096
Blocks per group: 32768
Inodes per group: 8192
Inode size: 256
Journal blocks: 32768
Label:
Blocks: 6509568
Block groups: 199
Reserved block group size: 1024
Created filesystem with 11/1630208 inodes and 146354/6509568 blocks
--------------------------------------------
Bootloader Version...: 8996-012001-1908071822
Baseband Version.....: 8996-130361-1905270421
Serial Number........: FXXXXXXXXXXX
--------------------------------------------
checking product...
OKAY [ 0.050s]
checking version-bootloader...
OKAY [ 0.046s]
checking version-baseband...
OKAY [ 0.046s]
sending 'boot_b' (30793 KB)...
OKAY [ 0.797s]
writing 'boot_b'...
OKAY [ 0.294s]
erasing 'system_b'...
OKAY [ 0.316s]
sending sparse 'system_b' 1/4 (524284 KB)...
OKAY [ 13.692s]
writing 'system_b' 1/4...
OKAY [ 3.460s]
sending sparse 'system_b' 2/4 (524284 KB)...
OKAY [ 13.802s]
writing 'system_b' 2/4...
OKAY [ 3.481s]
sending sparse 'system_b' 3/4 (524284 KB)...
OKAY [ 13.816s]
writing 'system_b' 3/4...
OKAY [ 3.451s]
sending sparse 'system_b' 4/4 (461052 KB)...
OKAY [ 11.950s]
writing 'system_b' 4/4...
OKAY [ 3.087s]
erasing 'system_a'...
OKAY [ 0.246s]
sending 'system_a' (298348 KB)...
OKAY [ 7.005s]
writing 'system_a'...
OKAY [ 2.036s]
erasing 'vendor_b'...
OKAY [ 0.112s]
sending 'vendor_b' (259272 KB)...
OKAY [ 6.400s]
writing 'vendor_b'...
OKAY [ 1.747s]
Setting current slot to 'b'...
OKAY [ 0.081s]
erasing 'userdata'...
OKAY [ 1.853s]
sending 'userdata' (138957 KB)...
OKAY [ 3.089s]
writing 'userdata'...
OKAY [ 1.293s]
rebooting...
finished. total time: 92.497s
Press any key to exit..
.
Click to expand...
Click to collapse
Curious....
I would suggest you try Deuce's script -- again, it has assisted and recovered countless taimens. And, if that doesn't help, I would suggest you try temporarily booting into TWRP custom recovery. If you do not know how to do that, download the TWRP .img file from twrp.me (you'll have to direct yourself to the Google Pixel 2 XL [taimen] section), put it where you put the flash-all and other image files, then run the fastboot command "fastboot boot twrp.img" (replace "twrp.img" with the actual filename of the twrp image file). There you can erase/format the system and/or other partitions, or even "repair" the filesystem! You can also run adb commands, so you might have some luck and be able to install/flash an OTA image file as well....
Good luck and hope this helps...!