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:

[Q] Help Debricking.. Force Flash?

I'm trying to un-softbrick my Nexus 7 (2013) WiFi with Nexus Root Toolkit v1.8.0.
Im getting an error,
Code:
checking product...
FAILED
Device product is 'flo'.
Update requires 'grouper'.
I think that I need to set the option to force the image, but the warning of permanent brickification worries me. I know that this is a Nexus 7 (2013) Wifi, so I should be able to use the KOT49H image (or any of the images in the 2013-WiFi section), from the factory images page without concern, right?
I'm not allowd to post links yet, but this is the site with the Google images: developers.google.com/android/nexus/images#razor

dwooderson said:
I'm trying to un-softbrick my Nexus 7 (2013) WiFi with Nexus Root Toolkit v1.8.0.
Im getting an error,
Code:
checking product...
FAILED
Device product is 'flo'.
Update requires 'grouper'.
I think that I need to set the option to force the image, but the warning of permanent brickification worries me. I know that this is a Nexus 7 (2013) Wifi, so I should be able to use the KOT49H image (or any of the images in the 2013-WiFi section), from the factory images page without concern, right?
I'm not allowd to post links yet, but this is the site with the Google images: developers.google.com/android/nexus/images#razor
Click to expand...
Click to collapse
I think you might have Nexus 7 (2012) selected instead of Nexus 7 v2, and yes force flashing grouper image to your 2013 will ruin your day.
You want the selection in Wugs to look like this:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
, which will flash this: https://dl.google.com/dl/android/aosp/razor-kot49h-factory-ebb4918e.tgz (this image is the factory image for the Nexus 7 2013 WiFi, aka FLO aka razor.)
You DO NOT want the selection in Wugs to look like this:

mdamaged said:
I think you might have Nexus 7 (2012)
Click to expand...
Click to collapse
Thank you for your help!
I can't believe I did that, how embarrassing! The log (below) makes it look like the operation was successful, but the tablet still won't boot. It sits on the Google logo (with an unlocked padlock icon) forever. I tried both Start and Recovery multiple times with 30 mins between just in case.
Any ideas of what to try next?
Code:
Flash Stock + Unroot...
------------------------------------------------------------------
sending 'bootloader' (3911 KB)...
OKAY [ 0.141s]
writing 'bootloader'...
OKAY [ 1.446s]
finished. total time: 1.587s
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.....: none
Serial Number........: xxxxxxxx
--------------------------------------------
checking product...
OKAY [ 0.003s]
checking version-bootloader...
OKAY [ 0.004s]
sending 'boot' (7018 KB)...
OKAY [ 0.238s]
writing 'boot'...
OKAY [ 0.435s]
sending 'recovery' (7564 KB)...
OKAY [ 0.257s]
writing 'recovery'...
OKAY [ 0.404s]
erasing 'system'...
OKAY [ 0.509s]
sending 'system' (717936 KB)...
OKAY [ 29.847s]
writing 'system'...
OKAY [ 38.148s]
erasing 'userdata'...
OKAY [ 8.056s]
formatting 'userdata' partition...
Creating filesystem with parameters:
Size: 13346254848
Block size: 4096
Blocks per group: 32768
Inodes per group: 8160
Inode size: 256
Journal blocks: 32768
Label:
Blocks: 3258363
Block groups: 100
Reserved block group size: 799
Created filesystem with 11/816000 inodes and 91981/3258363 blocks
sending 'userdata' (137202 KB)...
writing 'userdata'...
OKAY [ 15.096s]
erasing 'cache'...
OKAY [ 0.394s]
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.180s]
rebooting...
finished. total time: 94.593s
Booting up your freshly flashed stock device...
------------------------------------------------------------------
Wait for your device to finish booting up...
- It may appear to be boot looping; just wait...
- It could take 5-10 minutes; please be patient...
When its finally booted back up, please remember
to re-enable USB debugging if you plan on using
the toolkit to perform other operations.
NOTE: If this process was too quick and your device
is still in bootloader mode, then flashing stock may
have failed or been incomplete. Simply check the
log above: if you notice it skipped steps because it
didn't meet certain requirements, like the bootloader
or baseband version, then consider enabling 'Force Flash'
mode in the toolkits options menu and trying the
'Flash Stock + Unroot' processs again. Cheers.
Press any key to exit...

dwooderson said:
Thank you for your help!
I can't believe I did that, how embarrassing! The log (below) makes it look like the operation was successful, but the tablet still won't boot. It sits on the Google logo (with an unlocked padlock icon) forever. I tried both Start and Recovery multiple times with 30 mins between just in case.
Any ideas of what to try next?
Code:
Flash Stock + Unroot...
------------------------------------------------------------------
sending 'bootloader' (3911 KB)...
OKAY [ 0.141s]
writing 'bootloader'...
OKAY [ 1.446s]
finished. total time: 1.587s
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.....: none
Serial Number........: xxxxxxxx
--------------------------------------------
checking product...
OKAY [ 0.003s]
checking version-bootloader...
OKAY [ 0.004s]
sending 'boot' (7018 KB)...
OKAY [ 0.238s]
writing 'boot'...
OKAY [ 0.435s]
sending 'recovery' (7564 KB)...
OKAY [ 0.257s]
writing 'recovery'...
OKAY [ 0.404s]
erasing 'system'...
OKAY [ 0.509s]
sending 'system' (717936 KB)...
OKAY [ 29.847s]
writing 'system'...
OKAY [ 38.148s]
erasing 'userdata'...
OKAY [ 8.056s]
formatting 'userdata' partition...
Creating filesystem with parameters:
Size: 13346254848
Block size: 4096
Blocks per group: 32768
Inodes per group: 8160
Inode size: 256
Journal blocks: 32768
Label:
Blocks: 3258363
Block groups: 100
Reserved block group size: 799
Created filesystem with 11/816000 inodes and 91981/3258363 blocks
sending 'userdata' (137202 KB)...
writing 'userdata'...
OKAY [ 15.096s]
erasing 'cache'...
OKAY [ 0.394s]
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.180s]
rebooting...
finished. total time: 94.593s
Booting up your freshly flashed stock device...
------------------------------------------------------------------
Wait for your device to finish booting up...
- It may appear to be boot looping; just wait...
- It could take 5-10 minutes; please be patient...
When its finally booted back up, please remember
to re-enable USB debugging if you plan on using
the toolkit to perform other operations.
NOTE: If this process was too quick and your device
is still in bootloader mode, then flashing stock may
have failed or been incomplete. Simply check the
log above: if you notice it skipped steps because it
didn't meet certain requirements, like the bootloader
or baseband version, then consider enabling 'Force Flash'
mode in the toolkits options menu and trying the
'Flash Stock + Unroot' processs again. Cheers.
Press any key to exit...
Click to expand...
Click to collapse
Try the flash stock + unroot again with force (make sure you have the Nexus 7 v2 one selected first) as per his instructions, if it still does not boot, post to Wugs thread, maybe he'll know.

mdamaged, you have provided excellent and helpful info in many threads. IMO, you're one of the reasons that XDA is great.
Sent from my DROID RAZR HD using xda app-developers app

Jhall8 said:
mdamaged, you have provided excellent and helpful info in many threads. IMO, you're one of the reasons that XDA is great.
Sent from my DROID RAZR HD using xda app-developers app
Click to expand...
Click to collapse
I appreciate those words.

Do you have a custom recovery? TWRP? when I first got my nexus being so unused to not having an SD card I accidentally wiped everything including my system storage everything even the backups. It wouldn't even let me get to recovery it just sat at the logo forever like ur saying. I managed to get it to the bootloader (which was unlocked by the way still) with the key combo, used the volume navigation to get to the recovery option. It booted after a bit to my amazement. Then luckily I had a USB OTG adapter so I downloaded a new ROM put it on the USB Drive, mounted it in TWRP, then was able to flash it and skipped stock and save it from its infinite bootloop. though obviously you should probably use the factory image. Idk this would obviously require an OTG USB adapter.. They are cheap and could get one expedited if need be I suppose.
Just thought I'd mention that cuz I was surprised it worked out for me. And if u managed to get to the custom recovery flash at any point in the past it should work for you too.
Sent from my Nexus 5 using XDA Premium 4 mobile app

File System type RAW not supported

I have had no luck trying to use flash-all.bat when going to the Nov factory img...
everything seems to go well until the end where it says "Erase successful, but not automatically formatting. File system type raw not supported"
Any ideas here? i cannot get my P3XL to boot past bootloader...

I would hash check the factory image and/or download it again, and make sure your ADB/fastboot/platform tools are on the most current version.

MrGimpGrumble said:
I have had no luck trying to use flash-all.bat when going to the Nov factory img...
everything seems to go well until the end where it says "Erase successful, but not automatically formatting. File system type raw not supported"
Any ideas here? i cannot get my P3XL to boot past bootloader...
Click to expand...
Click to collapse
Go here [Guide] Pixel 3 XL Android 9.0 (Pie) Unlock/Root/Install Images/Kernels/Recovery + by Homeboy76 do #4 then #8 if you want root. Also, Prerequisites has a link to download SDK Platform tools r28.0.1

fury683 said:
I would hash check the factory image and/or download it again, and make sure your ADB/fastboot/platform tools are on the most current version.
Click to expand...
Click to collapse
Yes, i meant to delete the thread, I actually checked and had to update adb etc..
Thanks!

I know, old thread, but it came up in Google so in case others are looking for an answer to this problem:
# fastboot format system
fastboot: error: Formatting is not supported for file system with type 'raw'.
Try this:
Code:
# fastboot format:ext4 system
Warning: system_a type is raw, but ext4 was requested for formatting.
mke2fs 1.46.2 (28-Feb-2021)
Creating filesystem with 518763 4k blocks and 129792 inodes
Filesystem UUID: 525d9f76-1882-4beb-8da0-848509af4188
Superblock backups stored on blocks:
32768, 98304, 163840, 229376, 294912
Allocating group tables: done
Writing inode tables: done
Creating journal (8192 blocks): done
Writing superblocks and filesystem accounting information: done
Sending 'system_a' (92 KB) OKAY [ 0.003s]
Writing 'system_a' OKAY [ 0.070s]
Finished. Total time: 0.583s

Hey! Can you please update me about solution if you get any

Um... Read my previous post carefully... It is the solution, of at least, it worked for me.

KJ7LNW said:
I know, old thread, but it came up in Google so in case others are looking for an answer to this problem:
# fastboot format system
fastboot: error: Formatting is not supported for file system with type 'raw'.
Try this:
Code:
# fastboot format:ext4 system
Warning: system_a type is raw, but ext4 was requested for formatting.
mke2fs 1.46.2 (28-Feb-2021)
Creating filesystem with 518763 4k blocks and 129792 inodes
Filesystem UUID: 525d9f76-1882-4beb-8da0-848509af4188
Superblock backups stored on blocks:
32768, 98304, 163840, 229376, 294912
Allocating group tables: done
Writing inode tables: done
Creating journal (8192 blocks): done
Writing superblocks and filesystem accounting information: done
Sending 'system_a' (92 KB) OKAY [ 0.003s]
Writing 'system_a' OKAY [ 0.070s]
Finished. Total time: 0.583s
Click to expand...
Click to collapse
When I tried this, it says FAILED (remote: Invalid partition)

Nexus 7 will not start anymore

My problem is that my Nexus 7 will not start anymore. It will still display a startup screen, but then it will not continue. Also, I'm still in the boot loader, but can not flash the Recovery TWRP, because apparently the device is not recognized. Also in the Recovery TWRP I can not start, it will then hang synonymous.
Had actually installed CyanogenMod 14.1 and ran for some time with it
What options do I have left?

JuergenRaab said:
My problem is that my Nexus 7 will not start anymore. It will still display a startup screen, but then it will not continue. Also, I'm still in the boot loader, but can not flash the Recovery TWRP, because apparently the device is not recognized. Also in the Recovery TWRP I can not start, it will then hang synonymous.
Had actually installed CyanogenMod 14.1 and ran for some time with it
What options do I have left?
Click to expand...
Click to collapse
I dont know if it work for you. I'm stuck in bootloader menu when i try to resize the partition... it still does not work for me
but try Nexus Root Toolkit 2.1.9
it work for me. whenever i screw up, i put stock back

flash write failure
Flash Stock + Unroot [WugFresh Development]
------------------------------------------------------------------
target didn't report max-download-size
sending 'bootloader' (3915 KB)...
OKAY [ 0.129s]
writing 'bootloader'...
FAILED (remote: flash write failure)
finished. total time: 90.780s
rebooting into bootloader...
OKAY [ 0.007s]
finished. total time: 0.008s
target didn't report max-download-size
sending 'boot' (7422 KB)...
OKAY [ 0.239s]
writing 'boot'...
FAILED (remote: flash write failure)
finished. total time: 90.059s
target didn't report max-download-size
erasing 'cache'...
FAILED (remote: failed to erase partition)
finished. total time: 0.017s
target didn't report max-download-size
sending 'recovery' (8166 KB)...
OKAY [ 0.264s]
writing 'recovery'...
FAILED (remote: flash write failure)
finished. total time: 0.278s
target didn't report max-download-size
erasing 'system'...
FAILED (remote: failed to erase partition)
finished. total time: 0.017s
Creating filesystem with parameters:
Size: 28521246720
Block size: 4096
Blocks per group: 32768
Inodes per group: 8176
Inode size: 256
Journal blocks: 32768
Label:
Blocks: 6963195
Block groups: 213
Reserved block group size: 1024
Created filesystem with 11/1741488 inodes and 153337/6963195 blocks
target didn't report max-download-size
erasing 'userdata'...
FAILED (remote: failed to erase partition)
finished. total time: 0.015s
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
target didn't report max-download-size
erasing 'cache'...
FAILED (remote: failed to erase partition)
finished. total time: 0.014s
rebooting...
finished. total time: 0.006s

[Need Help] Nexus 7 Keeps rebooting on the Google Logo after Stock Flash

Hi Guys,
I'm having troubles with my Nexus 7 Wifi Tablet. Tablet was working just fine, but wanted to update to Lineage Custom. I've done the following steps
Unlock FastBoot and Install TWRP
I was under the impression that Tablet need to be root to install Magisk, so I downloaded SuperSU 2.82 and installed via TWRP. When then I attempted to install Magisk, I got a failure and realized SuperSU might be the issue.
At this point Tablet was fully functional. So I decided to Flash it to Stock to start over and be able to install Magisk and no SuperSU. That's when trouble started.
I downloaded the image from Google's developers Page.
It was an old verion, 4.3 instead of 6.0.1.
I flashed the 4.3 one using the flass-all.sh without notice and from that point the tablet never boot back, keeps on the Google Logo. No erros on the Flash though.
I downloaded the 6.0.1 version and flash again. Same thing.
So I Tried flashing each img instead of the flash-all. All went good with the exception of userdata.img
Sending 'data' (136890 KB) OKAY [ 4.749s]
Writing 'data' FAILED (remote: 'partition table doesn't exist')
fastboot: error: Command failed
Again, everything else was good. Boot, System, cache, recovery. All were OKAY.
ADB Devices - does not display the device
ADB Fastboot - shows the serial number and says fastboot.
Tried to format Data and cache, but Nothing. Recovery Mode shows the android with a red exaclamation and then reboots after a while. No errors.
Can someone help me to understand how I can flash it to boot properly?
Thanks!
Maxi.

Here's the output when running flash-all.sh
Sending 'bootloader' (3915 KB) OKAY [ 0.129s]
Writing 'bootloader' OKAY [ 1.462s]
Finished. Total time: 1.616s
Rebooting into bootloader OKAY [ 0.006s]
Finished. Total time: 0.006s
--------------------------------------------
Bootloader Version...: FLO-04.08
Baseband Version.....: none
Serial Number........: 08f0a038
--------------------------------------------
extracting android-info.txt (0 MB) to RAM...
Checking 'product' OKAY [ 0.002s]
Checking 'version-bootloader' OKAY [ 0.004s]
extracting boot.img (7 MB) to disk... took 0.030s
archive does not contain 'boot.sig'
Sending 'boot' (7422 KB) OKAY [ 0.238s]
Writing 'boot' OKAY [ 0.457s]
archive does not contain 'dtbo.img'
archive does not contain 'dt.img'
extracting recovery.img (7 MB) to disk... took 0.027s
archive does not contain 'recovery.sig'
Sending 'recovery' (8166 KB) OKAY [ 0.262s]
Writing 'recovery' OKAY [ 0.317s]
archive does not contain 'vbmeta.img'
archive does not contain 'vbmeta_system.img'
archive does not contain 'super_empty.img'
archive does not contain 'odm.img'
archive does not contain 'product.img'
extracting system.img (823 MB) to disk... took 5.537s
archive does not contain 'system.sig'
Sending 'system' (843549 KB) OKAY [ 29.000s]
Writing 'system' OKAY [ 40.367s]
archive does not contain 'system_ext.img'
archive does not contain 'vendor.img'
Erasing 'userdata' OKAY [ 1.268s]
mke2fs 1.44.4 (18-Aug-2018)
Creating filesystem with 3186683 4k blocks and 798112 inodes
Filesystem UUID: da066dda-5c66-4c7a-877d-5961cf7603aa
Superblock backups stored on blocks:
32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632, 2654208
Allocating group tables: done
Writing inode tables: done
Creating journal (16384 blocks): done
Writing superblocks and filesystem accounting information: done
Sending 'userdata' (3236 KB) OKAY [ 0.108s]
Writing 'userdata' OKAY [ 0.146s]
Erasing 'cache' OKAY [ 0.073s]
mke2fs 1.44.4 (18-Aug-2018)
Creating filesystem with 143360 4k blocks and 35840 inodes
Filesystem UUID: 34a82459-286a-44e9-89dc-bf893c44ffe6
Superblock backups stored on blocks:
32768, 98304
Allocating group tables: done
Writing inode tables: done
Creating journal (4096 blocks): done
Writing superblocks and filesystem accounting information: done
Sending 'cache' (208 KB) OKAY [ 0.012s]
Writing 'cache' OKAY [ 0.050s]
Rebooting OKAY [ 0.005s]
Finished. Total time: 78.216s

Success 80%
I have the same issue so i follow these steps
1) flash the old rom like 4.4 with unlocked Bootloader
2)relock the bootloader
3)boot up
If you want to update to android 6 just unlock bootloader again and flash the stock rom from google
---------- Post added at 12:25 PM ---------- Previous post was at 12:10 PM ----------
https://forum.xda-developers.com/showthread.php?t=2381582