Develop Bugs

[Q] Not booting anymore and no recovery

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:

How restore stock Fastboot

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.

[Q] black screen no boot animation yet fastboot still works?

I have a Nexus 7 LTE tablet, I recently did a Paranoid android update and everything went smooth. I performed my nandroid backup as I normally would. At some point during the day, my screen went black. I tried rebooting the tablet, but the screen was still black. The device appears to boot fine. I have no boot screen, I cannot enter TWRP or any other boot loader. The notification indicator light blinks and I was able to access the device via adb.
I decided to flash the default nexus 7 firmware using the official google files - 4.4.2 (KOT49H) assuming this would work as per the directions I read in similar threads.
My issue continunes. I still have a black screen. I can no longer access ADB. Fastboot on the other hand works just fine.
Here is the output of my last flash attempt.
Code:
./flash-all.sh
sending 'bootloader' (3911 KB)...
OKAY [ 0.129s]
writing 'bootloader'...
OKAY [ 1.355s]
finished. total time: 1.484s
rebooting into bootloader...
OKAY [ 0.007s]
finished. total time: 0.007s
sending 'radio' (76038 KB)...
OKAY [ 2.388s]
writing 'radio'...
OKAY [ 2.995s]
finished. total time: 5.383s
rebooting into bootloader...
OKAY [ 0.007s]
finished. total time: 0.007s
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
--------------------------------------------
Bootloader Version...: FLO-04.02
Baseband Version.....: DEB-Z00_2.42.0_1204
Serial Number........: 0*******
--------------------------------------------
checking product...
OKAY [ 0.003s]
checking version-bootloader...
OKAY [ 0.004s]
checking version-baseband...
OKAY [ 0.004s]
sending 'boot' (7018 KB)...
OKAY [ 0.268s]
writing 'boot'...
OKAY [ 0.348s]
sending 'recovery' (7566 KB)...
OKAY [ 0.283s]
writing 'recovery'...
OKAY [ 0.290s]
erasing 'system'...
OKAY [ 1.296s]
sending 'system' (730592 KB)...
OKAY [ 24.929s]
writing 'system'...
OKAY [ 32.060s]
erasing 'userdata'...
OKAY [ 25.211s]
formatting 'userdata' partition...
Creating filesystem with parameters:
Size: 28856791040
Block size: 4096
Blocks per group: 32768
Inodes per group: 8192
Inode size: 256
Journal blocks: 32768
Label:
Blocks: 7045115
Block groups: 215
Reserved block group size: 1024
Created filesystem with 11/1761280 inodes and 154578/7045115 blocks
sending 'userdata' (139085 KB)...
writing 'userdata'...
OKAY [ 12.329s]
erasing 'cache'...
OKAY [ 0.445s]
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.874s]
rebooting...
finished. total time: 98.361s
Even after a clean flash I still get a black screen and only fastboot is accessible.
What can I do to get rid of this black screen and get my tablet back in working condition?
Any help is appreciated.

I have the same issue, but I am stuck on google boot loop. I have tried going back to old factory roms, but still no good.
Have you tried using old factory roms? And were you able to go to recovery from bootloader? I can't even flashing stock recovery.

0wangj4 said:
Have you tried using old factory roms? And were you able to go to recovery from bootloader? I can't even flashing stock recovery.
Click to expand...
Click to collapse
I have no bootloader available as the screen is black. I can only access fastboot. I tried flashing the original google supplied firmware as well with no luck.

micemicerabies said:
I have no bootloader available as the screen is black. I can only access fastboot. I tried flashing the original google supplied firmware as well with no luck.
Click to expand...
Click to collapse
As I look at the script it looks like that was a very fast flash. Did you check the MD5 to make sure the file was not corrupted? Because it does not even look like anything flashed.
Edit: At best, maybe, the system flashed but boot and recovery were done in a couple seconds. I'd check the MD5 or reflash the images.
Sent from my Nexus 7 Flo running CM 11 4.4.2 with ElementalX Kernel using XDA Premium 4 mobile app

LinearEquation said:
As I look at the script it looks like that was a very fast flash. Did you check the MD5 to make sure the file was not corrupted? Because it does not even look like anything flashed.
Edit: At best, maybe, the system flashed but boot and recovery were done in a couple seconds. I'd check the MD5 or reflash the images
Click to expand...
Click to collapse
Code:
root[email protected]:/root/# md5sum razorg-kot49h-factory-49789b24.tgz && sha1sum razorg-kot49h-factory-49789b24.tgz
8e42ffe324a9109031dd4f9dd53fdc9a razorg-kot49h-factory-49789b24.tgz
49789b240cab9a8e91c1f5a3eb0b6be0b07b5732 razorg-kot49h-factory-49789b24.tgz
Correctly hashes against
MD5SUM = 8e42ffe324a9109031dd4f9dd53fdc9a
SHA1SUM = 49789b240cab9a8e91c1f5a3eb0b6be0b07b5732
For the 4.4.2 (KOT49H) Image (NOTE: The original flash that I showed the output for was for the later image 4.4.2_r2 (Verizon) (KVT49L)) In the past I have had more success with the KOT49H image and will continue testing using this image.
Here is the latest attempt at flashing using the flash-all.sh script
Code:
[email protected]:/root/razorg-kot49h-factory-49789b24/razorg-kot49h# ./flash-all.sh
sending 'bootloader' (3911 KB)...
OKAY [ 0.244s]
writing 'bootloader'...
OKAY [ 1.383s]
finished. total time: 1.627s
rebooting into bootloader...
OKAY [ 0.006s]
finished. total time: 0.006s
sending 'radio' (43830 KB)...
OKAY [ 2.666s]
writing 'radio'...
OKAY [ 1.748s]
finished. total time: 4.415s
rebooting into bootloader...
OKAY [ 0.005s]
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-04.02
Baseband Version.....: DEB-G00_2.37.0_1024
Serial Number........: 0*******
--------------------------------------------
checking product...
OKAY [ 0.003s]
checking version-bootloader...
OKAY [ 0.004s]
checking version-baseband...
OKAY [ 0.004s]
sending 'boot' (7018 KB)...
OKAY [ 0.424s]
writing 'boot'...
OKAY [ 0.369s]
sending 'recovery' (7566 KB)...
OKAY [ 0.456s]
writing 'recovery'...
OKAY [ 0.281s]
erasing 'system'...
OKAY [ 1.304s]
sending 'system' (721408 KB)...
OKAY [ 43.544s]
writing 'system'...
OKAY [ 30.515s]
erasing 'userdata'...
OKAY [ 22.401s]
formatting 'userdata' partition...
Creating filesystem with parameters:
Size: 28856791040
Block size: 4096
Blocks per group: 32768
Inodes per group: 8192
Inode size: 256
Journal blocks: 32768
Label:
Blocks: 7045115
Block groups: 215
Reserved block group size: 1024
Created filesystem with 11/1761280 inodes and 154578/7045115 blocks
sending 'userdata' (139085 KB)...
writing 'userdata'...
OKAY [ 14.458s]
erasing 'cache'...
OKAY [ 0.484s]
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 [ 1.179s]
rebooting...
finished. total time: 115.443s
I agree that these write speeds seem a little too quick
Sidenote: Before I tried this last flash I was able to confirm that the digitizer is functional. The devices appeared to boot into the factory image (screen was still black) I was some how able to get the accessibility options enabled so that the devices would speak out my actions. I did not complete this tutorial. This leads me to believe there is some more bizarre underlying screen issue. Possibly a loose cable?

Hopefully something here can help.
Code:
fastboot getvar all
(bootloader) version-bootloader: FLO-04.02
(bootloader) version-baseband: DEB-G00_2.25.1_0802
(bootloader) version-hardware: rev_e
(bootloader) version-cdma: N/A
(bootloader) variant: deb 32G
(bootloader) serialno: 0*******
(bootloader) product: deb
(bootloader) secure_boot: enabled
(bootloader) lock_state: unlocked
(bootloader) project: deb
(bootloader) off-mode-charge: yes
(bootloader) uart-on: no
(bootloader) partition-type:bootloader: emmc
(bootloader) partition-size:bootloader: 0x0000000000aee000
(bootloader) partition-type:recovery: emmc
(bootloader) partition-size:recovery: 0x0000000000a00000
(bootloader) partition-type:boot: emmc
(bootloader) partition-size:boot: 0x0000000001000000
(bootloader) partition-type:system: ext4
(bootloader) partition-size:system: 0x0000000034800000
(bootloader) partition-type:cache: ext4
(bootloader) partition-size:cache: 0x0000000023000000
(bootloader) partition-type:userdata: ext4
(bootloader) partition-size:userdata: 0x00000006b7ffbe00
all:
finished. total time: 0.026s

Asus RMA was not horrible
I want to close out this thread with some answers about my experience.
I requested an RMA from Asus and sent my device to get checked out or repaired by them. I was fearful that they would notice that I had tampered with the device. I removed the backing to check the battery, unlocking the bootloader and flashing 3rd party ROMs etc.
I ended up re-locking the bootloader since I had fastboot access and tested my luck. I bubble wrapped the devices as Asus said they do not supply padding or any packing material for return of the product.
I was able to check the RMA status page and saw that my tablet arrived in TX at the repair site. They did not update the status page for 3 days with no indication of what caused the issue. Finally the status was changed from < Received > to < Repair Complete >. I had to contact support as they did not supply me with a tracking number. They gave me the tracking details and I got my tablet back yesterday. Asus did not use any of my bubble wrap and the tablet was free floating in a barely reinforced cardboard box.
No explanation was given as to the cause of the failure, I got back the exact same back cover as well as the screen. So either they changed some internal part or flashed some part of the device that I am unaware of.
Anyone else who has a similar issue and needs to get an RMA I would recommend the following.
1. If you still have access to fastboot relock the bootloader. You can check using
Code:
fastboot getvar all
1. Take photos of the device and all physical imperfections so you have some recourse if someone breaks the screen
2. Bubble wrap the device tightly to ensure no damage occurs on the way to the repair site.
3. Tracking & Insurance is a must. If you can prove the screen broke due to USPS or whoever then at least you can get a new tablet with the insurance money. Don't cheap out, get the $250 or $350 worth. The whole cost of shipping should be less than $10 and is worth the piece of mind.
Finally I just updated my tablet to 4.4.3 as it was returned with 4.4.2. Here is what a successful flash looks like, as well as how long each part takes to flash. Compared to the previous flash times one can see the difference.
Code:
[email protected]:/Android/razorg-ktu84l-factory-9f9b9ef2/razorg-ktu84l# ./flash-all.sh
sending 'bootloader' (3911 KB)...
OKAY [ 0.227s]
writing 'bootloader'...
OKAY [ 1.285s]
finished. total time: 1.512s
rebooting into bootloader...
OKAY [ 0.006s]
finished. total time: 0.006s
sending 'radio' (76038 KB)...
OKAY [ 4.231s]
writing 'radio'...
OKAY [ 2.986s]
finished. total time: 7.217s
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-04.02
Baseband Version.....: DEB-Z00_2.42.0_1204
Serial Number........: 0*******
--------------------------------------------
checking product...
OKAY [ 0.003s]
checking version-bootloader...
OKAY [ 0.004s]
checking version-baseband...
OKAY [ 0.004s]
sending 'boot' (7050 KB)...
OKAY [ 0.408s]
writing 'boot'...
OKAY [ 0.335s]
sending 'recovery' (7600 KB)...
OKAY [ 0.432s]
writing 'recovery'...
OKAY [ 0.290s]
erasing 'system'...
OKAY [ 1.297s]
sending 'system' (740284 KB)...
OKAY [ 42.003s]
writing 'system'...
OKAY [ 32.278s]
erasing 'userdata'...
OKAY [ 21.615s]
formatting 'userdata' partition...
Creating filesystem with parameters:
Size: 28856791040
Block size: 4096
Blocks per group: 32768
Inodes per group: 8192
Inode size: 256
Journal blocks: 32768
Label:
Blocks: 7045115
Block groups: 215
Reserved block group size: 1024
Created filesystem with 11/1761280 inodes and 154578/7045115 blocks
sending 'userdata' (139085 KB)...
writing 'userdata'...
OKAY [ 13.308s]
erasing 'cache'...
OKAY [ 0.368s]
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 [ 1.145s]
rebooting...
finished. total time: 113.509s
My overall experience with the RMA process was great I did not have any of the nightmare problems that I read about on other forums.
Good luck to anyone going through this headache.

micemicerabies said:
I want to close out this thread with some answers about my experience.
I requested an RMA from Asus and sent my device to get checked out or repaired by them. I was fearful that they would notice that I had tampered with the device. I removed the backing to check the battery, unlocking the bootloader and flashing 3rd party ROMs etc.
I ended up re-locking the bootloader since I had fastboot access and tested my luck. I bubble wrapped the devices as Asus said they do not supply padding or any packing material for return of the product.
I was able to check the RMA status page and saw that my tablet arrived in TX at the repair site. They did not update the status page for 3 days with no indication of what caused the issue. Finally the status was changed from < Received > to < Repair Complete >. I had to contact support as they did not supply me with a tracking number. They gave me the tracking details and I got my tablet back yesterday. Asus did not use any of my bubble wrap and the tablet was free floating in a barely reinforced cardboard box.
No explanation was given as to the cause of the failure, I got back the exact same back cover as well as the screen. So either they changed some internal part or flashed some part of the device that I am unaware of.
Anyone else who has a similar issue and needs to get an RMA I would recommend the following.
1. If you still have access to fastboot relock the bootloader. You can check using
Code:
fastboot getvar all
1. Take photos of the device and all physical imperfections so you have some recourse if someone breaks the screen
2. Bubble wrap the device tightly to ensure no damage occurs on the way to the repair site.
3. Tracking & Insurance is a must. If you can prove the screen broke due to USPS or whoever then at least you can get a new tablet with the insurance money. Don't cheap out, get the $250 or $350 worth. The whole cost of shipping should be less than $10 and is worth the piece of mind.
Finally I just updated my tablet to 4.4.3 as it was returned with 4.4.2. Here is what a successful flash looks like, as well as how long each part takes to flash. Compared to the previous flash times one can see the difference.
Code:
[email protected]:/Android/razorg-ktu84l-factory-9f9b9ef2/razorg-ktu84l# ./flash-all.sh
sending 'bootloader' (3911 KB)...
OKAY [ 0.227s]
writing 'bootloader'...
OKAY [ 1.285s]
finished. total time: 1.512s
rebooting into bootloader...
OKAY [ 0.006s]
finished. total time: 0.006s
sending 'radio' (76038 KB)...
OKAY [ 4.231s]
writing 'radio'...
OKAY [ 2.986s]
finished. total time: 7.217s
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-04.02
Baseband Version.....: DEB-Z00_2.42.0_1204
Serial Number........: 0*******
--------------------------------------------
checking product...
OKAY [ 0.003s]
checking version-bootloader...
OKAY [ 0.004s]
checking version-baseband...
OKAY [ 0.004s]
sending 'boot' (7050 KB)...
OKAY [ 0.408s]
writing 'boot'...
OKAY [ 0.335s]
sending 'recovery' (7600 KB)...
OKAY [ 0.432s]
writing 'recovery'...
OKAY [ 0.290s]
erasing 'system'...
OKAY [ 1.297s]
sending 'system' (740284 KB)...
OKAY [ 42.003s]
writing 'system'...
OKAY [ 32.278s]
erasing 'userdata'...
OKAY [ 21.615s]
formatting 'userdata' partition...
Creating filesystem with parameters:
Size: 28856791040
Block size: 4096
Blocks per group: 32768
Inodes per group: 8192
Inode size: 256
Journal blocks: 32768
Label:
Blocks: 7045115
Block groups: 215
Reserved block group size: 1024
Created filesystem with 11/1761280 inodes and 154578/7045115 blocks
sending 'userdata' (139085 KB)...
writing 'userdata'...
OKAY [ 13.308s]
erasing 'cache'...
OKAY [ 0.368s]
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 [ 1.145s]
rebooting...
finished. total time: 113.509s
My overall experience with the RMA process was great I did not have any of the nightmare problems that I read about on other forums.
Good luck to anyone going through this headache.
Click to expand...
Click to collapse
Thanks for taking the time to update!

[Q] No change after flashing anything

I have a problem with my Galaxy Nexus maguro. I have successful flash ASOP rom but after few days i was no able to boot my device, it always do a bootloop.
I decide to come back to factory and i'm following this insctruction: https:/developers.google.com/android/nexus/images
Process goes fine without errors, but after reboot I continue to see ASOP... I try to flash other roms (Paranoid, FML) but no result... I try to format /system from recovery, but always ASOP (with bootloop).
Please help me!
This is my flashing log:
Code:
C:\yakju-jwr66y-factory-09207065\yakju-jwr66y>flash-all.bat
sending 'bootloader' (2308 KB)...
OKAY [ 0.309s]
writing 'bootloader'...
OKAY [ 7.938s]
finished. total time: 8.253s
rebooting into bootloader...
OKAY [ 0.010s]
finished. total time: 0.012s
< waiting for device >
sending 'radio' (12288 KB)...
OKAY [ 1.575s]
writing 'radio'...
OKAY [ 4.387s]
finished. total time: 5.966s
rebooting into bootloader...
OKAY [ 0.008s]
finished. total time: 0.009s
< waiting for device >
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
archive does not contain 'tos.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........: 014E281201010006
--------------------------------------------
checking product...
OKAY [ 0.006s]
checking version-bootloader...
OKAY [ 0.008s]
checking version-baseband...
OKAY [ 0.008s]
sending 'boot' (4376 KB)...
OKAY [ 0.570s]
writing 'boot'...
OKAY [ 2.537s]
sending 'recovery' (4924 KB)...
OKAY [ 0.645s]
writing 'recovery'...
OKAY [ 4.508s]
erasing 'system'...
OKAY [ 0.008s]
sending 'system' (474180 KB)...
OKAY [ 60.222s]
writing 'system'...
OKAY [1610.786s]
erasing 'userdata'...
OKAY [ 0.034s]
sending 'userdata' (137559 KB)...
OKAY [ 17.768s]
writing 'userdata'...
OKAY [243.699s]
erasing 'cache'...
OKAY [ 0.009s]
sending 'cache' (8832 KB)...
OKAY [ 1.134s]
writing 'cache'...
OKAY [ 14.461s]
rebooting...
finished. total time: 1956.473s
Press any key to exit...

Have you tried using "Nexus Root Toolkit"? http://www.wugfresh.com/nrt/

Running into a problem trying to go back to stock on Pixel 2 XL...

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.