Database Info

[Q] corrupt cache, can't format ext4

Last Friday I tried to flash android 5 lolipop to my Nexus 5. It froze in the erasing part.
Eventualy switched the phone off and on. There was a loop where you could only see the droid, even in recovery mode.
I got around that loop by flashing TWRP to the recovery partition.
Al recovery ROM's however all state that they can't mount /cache.
I formatted the hell out of it but sadly it didn't solve the problem.
So using adb shell I removed the cache partition, recreated it and formatted it.
So here is my partition table:
Code:
Number Start End Size File system Name Flags
1 524kB 67.6MB 67.1MB fat16 modem
2 67.6MB 68.7MB 1049kB sbl1
3 68.7MB 69.2MB 524kB rpm
4 69.2MB 69.7MB 524kB tz
5 69.7MB 70.3MB 524kB sdi
6 70.3MB 70.8MB 524kB aboot
7 70.8MB 72.9MB 2097kB pad
8 72.9MB 73.9MB 1049kB sbl1b
9 73.9MB 74.4MB 524kB tzb
10 74.4MB 75.0MB 524kB rpmb
11 75.0MB 75.5MB 524kB abootb
12 75.5MB 78.6MB 3146kB modemst1
13 78.6MB 81.8MB 3146kB modemst2
14 81.8MB 82.3MB 524kB metadata
15 82.3MB 99.1MB 16.8MB misc
16 99.1MB 116MB 16.8MB ext4 persist
17 116MB 119MB 3146kB imgdata
18 119MB 142MB 23.1MB laf
19 142MB 165MB 23.1MB boot
20 165MB 188MB 23.1MB recovery
21 188MB 191MB 3146kB fsg
22 191MB 192MB 524kB fsc
23 192MB 192MB 524kB ssd
24 192MB 193MB 524kB DDR
25 193MB 1267MB 1074MB ext4 system
26 1267MB 1298MB 31.5MB crypto
27 1298MB 2032MB 734MB cache
28 2032MB 15.8GB 13.7GB ext4 userdata
29 15.8GB 15.8GB 5632B grow
Notice the missing ext4 for partition 27. After deleting and recreating the partition I formatted it with the following command:
Code:
mke2fs -t ext4 /dev/block/mmcblk0p27
this resulted in:
Code:
mke2fs 1.41.14 (22-Dec-2010)
Filesystem label=
OS type: Linux
Block size=4096 (log=2)
Fragment size=4096 (log=2)
Stride=0 blocks, Stripe width=0 blocks
44832 inodes, 179200 blocks
8960 blocks (5.00%) reserved for the super user
First data block=0
Maximum filesystem blocks=184549376
6 block groups
32768 blocks per group, 32768 fragments per group
7472 inodes per group
Superblock backups stored on blocks:
32768, 98304, 163840
Writing inode tables: done
Creating journal (4096 blocks): done
Writing superblocks and filesystem accounting information: done
This filesystem will be automatically checked every 29 mounts or
180 days, whichever comes first. Use tune2fs -c or -i to override
So at this point I wanted to check the my partition table again, but this time i got an error message:
Code:
Error: /dev/block/mmcblk0: unrecognised disk label
Mounting results in:
Code:
mount /cache
mount: mounting /dev/block/platform/msm_sdcc.1/by-name/cache on /cache failed: Invalid argument
Did I make any mistakes here? I did not rooted the phone (yet). Is this necessary?
The re partitioning part comes from a guide here originally for the kindle.
Current status is that I re flashed stock droid 4.4.4. It starts, but all Google applications crash and I have no cellular network .
Guess they all depend on the cache directory.
Any help on making the cache partition work again would be much appreciated!

Oh jeez. I guess by now you know what you've done wrong. In case you don't, you should have just flashed the stock cache.img via fastboot as the very first step.
When you say you flashed stock, how?
What is the output of fastboot flash cache cache.img?
Sent from my Nexus 5 using Tapatalk

My bad! I should have mentioned that I had tried all the basic steps.
So I flashed the original cache.img many times. Because some say it takes more then 1 try to fix a corrupt cache.
Also tried a manual erase and a format of the cache partition.
Flashing the cache is somewhat strange, I have 2 variants. One is done in a heartbeat saying everything went well:
Code:
D:\Downloads\hammerhead 4.4.4\image-hammerhead-ktu84p>fastboot flash cache cache.img
erasing 'cache'...
OKAY [ 0.511s]
sending 'cache' (13348 KB)...
OKAY [ 0.627s]
writing 'cache'...
OKAY [ 1.026s]
finished. total time: 2.169s
And then if I run it again it gets stuck at erasing:
Code:
D:\Downloads\hammerhead 4.4.4\image-hammerhead-ktu84p>fastboot flash cache cache.img
erasing 'cache'...
I once left it overnight but the following morning it was still erasing...
All the time the result is the same. A phone with crashing apps and no cellular network.
To answer your other question. I used fastboot to do a flash-all from the stock image from Google (image-hammerhead-ktu84p (4.4.4)).
Also did the manual version where I manual erase the partitions and flash them.
After this I get a working 4.4.4 with the exception that all Google apps crash (including Play etc, so the basic needs) and I have no cellular network.
Resulting in a useless phone.

The first output looks normal. Try and get it to that stage again so there is a successful flash, then try And fix persist partition as that has similar symptoms. Guide linked in my signature
Sent from my Nexus 5 using Tapatalk

Thank you so much for your reply.
I followed this guide.
The repair did nothing so I entered:
Code:
make_ext4fs /dev/block/platform/msm_sdcc.1/by-name/persist
Since my dev/block/platform/msm_sdcc.1/by-name directory was empty is also did that same command for the cache:
Code:
make_ext4fs /dev/block/platform/msm_sdcc.1/by-name/cache
initially that looked like a good thing. The mounting error's where gone after i rebooted the phone.
But things took a turn for the worst. Where before i had a 50% chance on failing to erase the cache. I now have gained a 50% chance to fail at the writing stage.
Resulting in the device not being flash-able because there is more than one part that needs to be flashed.
Also, Philz is not usable. Although flashing states successful, It just won't boot into it. TWRP is the only thing that still works.
Did I do this myself by creating that cache bit? Or is corruption more likely?

Its hard to say. But I think it needs a professional repair now.
Sent from my Nexus 5 using Tapatalk

I'm afraid you are right.
From what I'm reading on the internet, I'm very unfortunate. It seems that in almost all cases you can recover from a flash that has gone south.
Anyway, I'll give it one or two more tries and if it fails I will look if I can claim it under warranty.
Can you answer one more question. Was it a mistake to enter:
Code:
make_ext4fs /dev/block/platform/msm_sdcc.1/by-name/cache
Could this break things even further?
Thank you for all your help. It is much appreciated.

Dujinga said:
I'm afraid you are right.
From what I'm reading on the internet, I'm very unfortunate. It seems that in almost all cases you can recover from a flash that has gone south.
Anyway, I'll give it one or two more tries and if it fails I will look if I can claim it under warranty.
Can you answer one more question. Was it a mistake to enter:
Code:
make_ext4fs /dev/block/platform/msm_sdcc.1/by-name/cache
Could this break things even further?
Thank you for all your help. It is much appreciated.
Click to expand...
Click to collapse
It cannot break things further. Have you tried dd zero out cache? If there is an I/O problem then that most certainly will break the dd command. You can also try to read back the cache partition with dd command to /data or to / if have enough space on / to confirm there are no I/O errors. If you havent find any I/O errors then I can imagine two things. Something got messed up in the gpt partition or the mmc is fauilty.

I'm a rookie, can you please explain how to "dd zero out" the cache?
P.S. I now have problems on other parts as well:
Code:
D:\Downloads\hammerhead 4.4.4>fastboot flash bootloader bootloader-hammerhead-hhz11k.img
sending 'bootloader' (2508 KB)...
OKAY [ 0.288s]
writing 'bootloader'...
FAILED (remote: flash write failure)
finished. total time: 43.476s

Dujinga said:
I'm a rookie, can you please explain how to "dd zero out" the cache?
P.S. I now have problems on other parts as well:
Code:
D:\Downloads\hammerhead 4.4.4>fastboot flash bootloader bootloader-hammerhead-hhz11k.img
sending 'bootloader' (2508 KB)...
OKAY [ 0.288s]
writing 'bootloader'...
FAILED (remote: flash write failure)
finished. total time: 43.476s
Click to expand...
Click to collapse
Code:
dd if=/dev/zero of=/dev/block/mmcblk0p27
Sent from my Nexus 5 using Tapatalk

Thank you for your reply. But running this command wil be a problem as it requiers Philz and ADB.
I can still flash Philz in the recovery, but it won't boot into the recovey afterwards
Guys, I want to thank you for all the help, but I'm giving up.
Gonna contact the supplier with the question how to resolve this issue.

Can't flash TWRP either?
What about
fastboot boot recovery.img
Where you don't flash but boot the recovery image from computer?
Sent from my Nexus 5 using Tapatalk

Dujinga said:
I'm a rookie, can you please explain how to "dd zero out" the cache?
P.S. I now have problems on other parts as well:
Code:
D:\Downloads\hammerhead 4.4.4>fastboot flash bootloader bootloader-hammerhead-hhz11k.img
sending 'bootloader' (2508 KB)...
OKAY [ 0.288s]
writing 'bootloader'...
FAILED (remote: flash write failure)
finished. total time: 43.476s
Click to expand...
Click to collapse
rootSU said:
Can't flash TWRP either?
What about
fastboot boot recovery.img
Where you don't flash but boot the recovery image from computer?
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Pretty sure "FAILED (remote: flash write failure)" error means that the emmc is hosed.
It's best you claim warranty/insurance.
-Sent from a Lollipop'd Hammerhead!

Ok, so I flashed Philz again (btw TWRP always kept working but that one has a strange shell (limited)).
This time instead of booting straight into recovery after I flashed it, I turned it off and on again.
Now I could get into Philz.
So I ran:
Code:
dd if=/dev/zero of=/dev/block/mmcblk0p27
Expecting it to fail, but this was the result:
Code:
dd: writing '/dev/block/mmcblk0p27': No space left on device
1433601+0 records in
1433600+0 records out
734003200 bytes (700.0MB) copied, 41.996465 seconds, 16.7MB/s
That seems OK to me
So I'm going to try a bit more. I already openend a case with the reseller though.
One way or another this will get resolved

I didn't see that error. Yes, hosed.
Sent from my Nexus 5 using Tapatalk

The first time always failes, if I rerun command after a fail it succeeds (or it says it does).
Anayway this happens to all sections, but I start with the bootloader. Can't mess much around there because without the bootloader you are defenatly toast
Code:
D:\Downloads\hammerhead 4.4.4>fastboot flash bootloader bootloader-hammerhead-hh
z11k.img
sending 'bootloader' (2508 KB)...
OKAY [ 0.287s]
writing 'bootloader'...
FAILED (remote: flash write failure)
finished. total time: 43.477s
D:\Downloads\hammerhead 4.4.4>fastboot flash bootloader bootloader-hammerhead-hh
z11k.img
sending 'bootloader' (2508 KB)...
OKAY [ 0.286s]
writing 'bootloader'...
OKAY [ 0.398s]
finished. total time: 0.692s
D:\Downloads\hammerhead 4.4.4>fastboot flash bootloader bootloader-hammerhead-hh
z11k.img
sending 'bootloader' (2508 KB)...
OKAY [ 0.287s]
writing 'bootloader'...
FAILED (remote: flash write failure)
finished. total time: 43.473s
D:\Downloads\hammerhead 4.4.4>fastboot flash bootloader bootloader-hammerhead-hh
z11k.img
sending 'bootloader' (2508 KB)...
OKAY [ 0.286s]
writing 'bootloader'...
OKAY [ 0.398s]
finished. total time: 0.692s
So I tried to get into Philz again, but it is FUBAR again. I give up ...... can't stand it ..... argggghh

Dujinga said:
The first time always failes, if I rerun command after a fail it succeeds (or it says it does).
Anayway this happens to all sections, but I start with the bootloader. Can't mess much around there because without the bootloader you are defenatly toast
Code:
D:\Downloads\hammerhead 4.4.4>fastboot flash bootloader bootloader-hammerhead-hh
z11k.img
sending 'bootloader' (2508 KB)...
OKAY [ 0.287s]
writing 'bootloader'...
FAILED (remote: flash write failure)
finished. total time: 43.477s
D:\Downloads\hammerhead 4.4.4>fastboot flash bootloader bootloader-hammerhead-hh
z11k.img
sending 'bootloader' (2508 KB)...
OKAY [ 0.286s]
writing 'bootloader'...
OKAY [ 0.398s]
finished. total time: 0.692s
D:\Downloads\hammerhead 4.4.4>fastboot flash bootloader bootloader-hammerhead-hh
z11k.img
sending 'bootloader' (2508 KB)...
OKAY [ 0.287s]
writing 'bootloader'...
FAILED (remote: flash write failure)
finished. total time: 43.473s
D:\Downloads\hammerhead 4.4.4>fastboot flash bootloader bootloader-hammerhead-hh
z11k.img
sending 'bootloader' (2508 KB)...
OKAY [ 0.286s]
writing 'bootloader'...
OKAY [ 0.398s]
finished. total time: 0.692s
So I tried to get into Philz again, but it is FUBAR again. I give up ...... can't stand it ..... argggghh
Click to expand...
Click to collapse
It's a wild goose chase mate. Do you even know what the error stands for? "Flash write failure" means the emmc is toast and hence nothing can be written on it. It's kinda become read only now. Even if the flash is successful, a quick reboot will roll everything back.
It's best you take it up with your seller and claim warranty. There;s nothing you can do.
Good luck!

I got the return instructions. Gonna mail it tommorow.
Once again a huge thanks to all of you guys. :good:

[NXT-L09]: Brick? Bootloop post App2SD modification

Huawei NXT-L09 (Messi Edition)
I was on EMUI 4.1, decided to root and install Link2SD, could not write to 2nd partition (Mount scripts) so I tried App2SD, after an error I tried on of the option to edit something in the system to possibly fix the mounting script issue.
Anyway, rebooting into bootloop and tried to flash one of the Stock Roms I found on the forums, started with L09-B321 Stock-Rooted. Got to the Booting... screen and it just sits there for hours. Probably messed up my attempting to place another rom L29-B180, same deal stuck on the text that says Booting...
Tried Italian Knife (Decrypted Boot), did not try unbrick as I cannot find the files that it requests (.img's)
I still have TWRP 3.0.2, Fastboot worked, Bootloader Unlocked.
Not sure how to proceed, I have no idea what version I was on.
Marshmallow
EMUI 4.1 (95% sure it was 4.1)
Open to recommendations, thanks!

Update: I thought I installed TWRP 3.0.2 (Name of the file I have), however UI in Recovery says TWRP Mate 8 v2.8.7.0

Can no longer boot into TWRP Recovery, it stays on booting now....
Followed this link:
http://forum.xda-developers.com/mate-8/general/unbrick-updating-to-b321-t3375934
Proceeded to Flashed the .img from the UPDATE.APP (Cust, Recovery, System and Boot) [I ripped with the Huawei Update Extractor] from a NXT-L09C636B170 stock rom found here: http://forum.xda-developers.com/mate-8/general/huawei-mate-8-stock-firmware-official-t3391727 via ItalianKnife (Unbrick option)
Everything went Okay, and phone has rebooted and still on : "...device has been unlocked..... Your device is booting now", will leave it on this screen overnight and see if by morning it loaded.

Additional Information:
Detecting phone :
selection :
manufacturer - Huawei phones
model - Auto detect (recommended)
Found Phone : HUAWEI NXT-L09
Model : Huawei phone in fastboot mode
IMEI : 86XXXXXXXXX7
Serial NR. : AXXXXXXXXXXX66
Firmware : NXT-L09C605B100
FB LockState: LOCKED
USER LockState: UNLOCKED
unlocked
Battery state: 2978mv

Solved - Sort of...
RECOVERED from Soft Brick with the DC_Phoenix software (EUR 15.00)
Only thing available to me before brick was Bootloader
No Recovery
No eRecovery (Huawei 3 button press or Vol Up for 3 seconds on Prompt
Maybe this helps someone, these are the files that were used, with this following Stock ROM:
NXT-L09C605B100 from the XDA Stock Rom post.
I erased IMEI, SN, Directories from Code.
Code:
Current version: NextL09C999B100
Extracting partitions
Cannot create extract directory: D:\X\DC_Phoenix\tmp\20160804_104858_UPDATE\
Extract files to directory: D:\X\Extracting partition: XLOADER OK
Extracting partition: FW_LPM3 OK
Extracting partition: FASTBOOT OK
Extracting partition: MODEMNVM_UPDATE OK
Extracting partition: TEEOS OK
Extracting partition: TRUSTFIRMWARE OK
Extracting partition: SENSORHUB OK
Extracting partition: FW_HIFI OK
Extracting partition: BOOT OK
Extracting partition: RECOVERY OK
Extracting partition: RECOVERY2 OK
Extracting partition: DTS OK
Extracting partition: MODEM OK
Extracting partition: MODEM_DSP OK
Extracting partition: 3RDMODEM OK
Extracting partition: SYSTEM OK
Extracting partition: CUST OK
Extracting partition: MODEM_DTB OK
Device found: AXXXXXXXXXXXXXXXX6
IMEI: 8XXXXXXXXXXXXXXXX7
Build number: :NXT-L09C605B100
Product model: HUAWEI NXT-L09
Writing XLOADER partition with file D:\X\DC_Phoenix\XLOADER.img
XLOADER partition UPDATE ...FAILED
Cannot get FBlock info from device
Activating backdoor: DONE
Writing XLOADER partition with file D:\X\DC_Phoenix\XLOADER.img
XLOADER partition UPDATE ...OK
Writing FW_LPM3 partition with file D:\UX\DC_Phoenix\FW_LPM3.img
FW_LPM3 partition UPDATE ...OK
Writing FASTBOOT partition with file D:\X\DC_Phoenix\FASTBOOT.img
FASTBOOT partition UPDATE ...OK
Writing MODEMNVM_UPDATE partition with file D:\X\MODEMNVM_UPDATE.img
MODEMNVM_UPDATE partition UPDATE ...OK
Writing TEEOS partition with file D:\X\DC_Phoenix\TEEOS.img
TEEOS partition UPDATE ...OK
Writing TRUSTFIRMWARE partition with file D:\X\DC_Phoenix\TRUSTFIRMWARE.img
TRUSTFIRMWARE partition UPDATE ...OK
Writing SENSORHUB partition with file D:\X\DC_Phoenix\SENSORHUB.img
SENSORHUB partition UPDATE ...OK
Writing FW_HIFI partition with file D:\X\DC_Phoenix\FW_HIFI.img
FW_HIFI partition UPDATE ...OK
Writing BOOT partition with file D:\X\DC_Phoenix\BOOT.img
BOOT partition UPDATE ...OK
Writing RECOVERY partition with file D:\X\DC_Phoenix\RECOVERY.img
RECOVERY partition UPDATE ...OK
Writing RECOVERY2 partition with file D:\X\DC_Phoenix\RECOVERY2.img
RECOVERY2 partition UPDATE ...OK
Writing DTS partition with file D:\X\DC_Phoenix\DTS.img
DTS partition UPDATE ...OK
Writing MODEM partition with file D:\X\DC_Phoenix\MODEM.img
MODEM partition UPDATE ...OK
Writing MODEM_DSP partition with file D:\X\DC_Phoenix\MODEM_DSP.img
MODEM_DSP partition UPDATE ...OK
Writing 3RDMODEM partition with file D:\X\DC_Phoenix\3RDMODEM.img
3RDMODEM partition UPDATE ...OK
Writing SYSTEM partition with file D:\X\DC_Phoenix\SYSTEM.img
SYSTEM partition UPDATE ...OK
Erasing CUST partition
Partition CUST erased
Writing CUST partition with file D:\X\DC_Phoenix\CUST.img
CUST partition UPDATE ...OK
Writing MODEM_DTB partition with file D:\X\DC_Phoenix\MODEM_DTB.img
MODEM_DTB partition UPDATE ...OK
Software written
8/4/2016 10:56:16 AM Writing device finished OK

Soft brick while attempting to root

I tried rooting my Pixel 3 - - OEM Unlock, bootloader unlocked, got into TWRP, but for some reason couldn't access any files on the system to install a zip. I tried wiping the file system to start from scratch and that didn't work. I then rebooted multiple times and fastbooted back into TWRP -- I had found a thread saying to change the file system type if you couldn't see the internal storage in TWRP -- I think that's where I went wrong. After I did that, I could no longer fastboot into TWRP. I tried downloading a factory image from google and fastbooting the recovery with no luck. I even tried the guide here : https://forum.xda-developers.com/pixel-3-xl/how-to/guide-progress-available-t3876849 to un-brick without success. I performed the erase commands "fastboot erase system_a
, fastboot erase system_b, fastboot erase boot_a, fastboot erase boot_b, fastboot reboot-bootloader then running the flash all command and the results below show and still unable to boot:
target reported max download size of 268435456 bytes
sending 'bootloader_a' (8493 KB)...
OKAY [ 0.308s]
writing 'bootloader_a'...
(bootloader) Flashing Pack version b1c1-0.1-5191736
(bootloader) Flashing partition table for Lun = 0
(bootloader) Flashing partition table for Lun = 1
(bootloader) Flashing partition table for Lun = 2
(bootloader) Flashing partition table for Lun = 4
(bootloader) Flashing partition table for Lun = 5
(bootloader) Flashing partition msadp_a
(bootloader) Flashing partition xbl_a
(bootloader) Flashing partition xbl_config_a
(bootloader) Flashing partition aop_a
(bootloader) Flashing partition tz_a
(bootloader) Flashing partition hyp_a
(bootloader) Flashing partition abl_a
(bootloader) Flashing partition keymaster_a
(bootloader) Flashing partition cmnlib_a
(bootloader) Flashing partition cmnlib64_a
(bootloader) Flashing partition devcfg_a
(bootloader) Flashing partition qupfw_a
(bootloader) Flashing partition storsec_a
(bootloader) Flashing partition logfs
OKAY [ 0.899s]
finished. total time: 1.208s
rebooting into bootloader...
OKAY [ 0.070s]
finished. total time: 0.072s
target reported max download size of 268435456 bytes
sending 'radio_a' (71132 KB)...
OKAY [ 1.907s]
writing 'radio_a'...
(bootloader) Flashing Pack version SSD:g845-00009-181130-B-5157073
(bootloader) Flashing partition modem_a
OKAY [ 0.482s]
finished. total time: 2.393s
rebooting into bootloader...
OKAY [ 0.070s]
finished. total time: 0.072s
extracting android-info.txt (0 MB) to RAM...
extracting boot.img (64 MB) to disk... took 0.376s
target reported max download size of 268435456 bytes
archive does not contain 'boot.sig'
archive does not contain 'boot_other.img'
extracting dtbo.img (8 MB) to disk... took 0.041s
archive does not contain 'dtbo.sig'
archive does not contain 'dt.img'
archive does not contain 'recovery.img'
extracting system.img (2189 MB) to disk... took 24.932s
archive does not contain 'system.sig'
extracting system_other.img (419 MB) to disk... took 4.880s
archive does not contain 'system.sig'
extracting vbmeta.img (0 MB) to disk... took 0.000s
archive does not contain 'vbmeta.sig'
extracting vendor.img (445 MB) to disk... took 5.342s
archive does not contain 'vendor.sig'
archive does not contain 'vendor_other.img'
wiping userdata...
Erase successful, but not automatically formatting.
File system type raw not supported.
--------------------------------------------
Bootloader Version...: b1c1-0.1-5191736
Baseband Version.....: g845-00009-181130-B-5157073
Serial Number........: 89DX08FVQ
--------------------------------------------
checking product...
OKAY [ 0.060s]
checking partition-exists...
FAILED (remote: variable not found)
finished. total time: 0.362s
Press any key to exit...
any advise would be greatly appreaciated.

cmorin543 said:
I tried rooting my Pixel 3 - - OEM Unlock, bootloader unlocked, got into TWRP, but for some reason couldn't access any files on the system to install a zip. I tried wiping the file system to start from scratch and that didn't work. I then rebooted multiple times and fastbooted back into TWRP -- I had found a thread saying to change the file system type if you couldn't see the internal storage in TWRP -- I think that's where I went wrong. After I did that, I could no longer fastboot into TWRP. I tried downloading a factory image from google and fastbooting the recovery with no luck. I even tried the guide here : https://forum.xda-developers.com/pixel-3-xl/how-to/guide-progress-available-t3876849 to un-brick without success. I performed the erase commands "fastboot erase system_a
, fastboot erase system_b, fastboot erase boot_a, fastboot erase boot_b, fastboot reboot-bootloader then running the flash all command and the results below show and still unable to boot:
target reported max download size of 268435456 bytes
sending 'bootloader_a' (8493 KB)...
OKAY [ 0.308s]
writing 'bootloader_a'...
(bootloader) Flashing Pack version b1c1-0.1-5191736
(bootloader) Flashing partition table for Lun = 0
(bootloader) Flashing partition table for Lun = 1
(bootloader) Flashing partition table for Lun = 2
(bootloader) Flashing partition table for Lun = 4
(bootloader) Flashing partition table for Lun = 5
(bootloader) Flashing partition msadp_a
(bootloader) Flashing partition xbl_a
(bootloader) Flashing partition xbl_config_a
(bootloader) Flashing partition aop_a
(bootloader) Flashing partition tz_a
(bootloader) Flashing partition hyp_a
(bootloader) Flashing partition abl_a
(bootloader) Flashing partition keymaster_a
(bootloader) Flashing partition cmnlib_a
(bootloader) Flashing partition cmnlib64_a
(bootloader) Flashing partition devcfg_a
(bootloader) Flashing partition qupfw_a
(bootloader) Flashing partition storsec_a
(bootloader) Flashing partition logfs
OKAY [ 0.899s]
finished. total time: 1.208s
rebooting into bootloader...
OKAY [ 0.070s]
finished. total time: 0.072s
target reported max download size of 268435456 bytes
sending 'radio_a' (71132 KB)...
OKAY [ 1.907s]
writing 'radio_a'...
(bootloader) Flashing Pack version SSD:g845-00009-181130-B-5157073
(bootloader) Flashing partition modem_a
OKAY [ 0.482s]
finished. total time: 2.393s
rebooting into bootloader...
OKAY [ 0.070s]
finished. total time: 0.072s
extracting android-info.txt (0 MB) to RAM...
extracting boot.img (64 MB) to disk... took 0.376s
target reported max download size of 268435456 bytes
archive does not contain 'boot.sig'
archive does not contain 'boot_other.img'
extracting dtbo.img (8 MB) to disk... took 0.041s
archive does not contain 'dtbo.sig'
archive does not contain 'dt.img'
archive does not contain 'recovery.img'
extracting system.img (2189 MB) to disk... took 24.932s
archive does not contain 'system.sig'
extracting system_other.img (419 MB) to disk... took 4.880s
archive does not contain 'system.sig'
extracting vbmeta.img (0 MB) to disk... took 0.000s
archive does not contain 'vbmeta.sig'
extracting vendor.img (445 MB) to disk... took 5.342s
archive does not contain 'vendor.sig'
archive does not contain 'vendor_other.img'
wiping userdata...
Erase successful, but not automatically formatting.
File system type raw not supported.
--------------------------------------------
Bootloader Version...: b1c1-0.1-5191736
Baseband Version.....: g845-00009-181130-B-5157073
Serial Number........: 89DX08FVQ
--------------------------------------------
checking product...
OKAY [ 0.060s]
checking partition-exists...
FAILED (remote: variable not found)
finished. total time: 0.362s
Press any key to exit...
any advise would be greatly appreaciated.
Click to expand...
Click to collapse
Hello,
I wonder ? do you have pixel 3 phone?
I see that you have the bootloader of the crossheath for the google pixel 3 XL installed.
bootloader-crosshatch-b1c1-0.1-5191736.img
Maybe you should download the google pixel 3 OTA or Factory.img.

That's so weird -- I used the blueline factory image from here: https://developers.google.com/android/images#blueline
I'll try it again though. Thanks for noticing that.

cmorin543 said:
That's so weird -- I used the blueline factory image from here: https://developers.google.com/android/images#blueline
I'll try it again though. Thanks for noticing that.
Click to expand...
Click to collapse
Succes, and let me know if you succeeded flashing.
9.0.0 (PQ2A.190405.003, Apr 2019) Link c12f40f0b189eb2daa80d029917bc9a8841da89cfcafa21b8f61b0d9f90826e7

Still no luck. I double checked and then redownloaded the .img file you referenced and it is the same as I tried and gives the same results.

I think you need to fastboot format userdata, but I have not used that command on this device. If it wont do it automatically you probably need to do it manually. Look into that option. There should have never been a need to mess with any of the file systems on this device.

cmorin543 said:
Still no luck. I double checked and then redownloaded the .img file you referenced and it is the same as I tried and gives the same results.
Click to expand...
Click to collapse
Strange, and if you download the factory image?
You can flash it in all in one tool or with ADB.
So try factory with flash_all .bat
Succes!!

wangdaning said:
I think you need to fastboot format userdata, but I have not used that command on this device. If it wont do it automatically you probably need to do it manually. Look into that option. There should have never been a need to mess with any of the file systems on this device.
Click to expand...
Click to collapse
I should've mentioned that I did do the format of userdata at one point and it didn't make a difference.
sakerhetz said:
Strange, and if you download the factory image?
You can flash it in all in one tool or with ADB.
So try factory with flash_all .bat
Succes!!
Click to expand...
Click to collapse
I tried using the flash_all.bat with no joy and I also tried using twrp (when I was actually able to boot into it) to sideload the OTA zip still with no joy.
I think I'm just going to contact Google and see what they can do -- the phone is technically still under warranty and I am still able to re-lock the bootloader... I appreciate the help.

Maybe try:
1) fastboot erase userdata
2) flash-all.bat
If no good:
1) fastboot erase userdata
2) fastboot format userdata
3) flash-all.bat
Everything will be gone, but already is from what you have said.

if you have downloaded the correct factory image as you mentioned then it should wipe out everything and fix your userdata even if its corrupt with flash.all bat script.
you could alternatively take a look at the detailed steps here just download the blueline img instead of crosshatch... https://forum.xda-developers.com/pixel-3-xl/how-to/guide-progress-available-t3876849
Steps are exactly the same.

SacredDeviL666 said:
if you have downloaded the correct factory image as you mentioned then it should wipe out everything and fix your userdata even if its corrupt with flash.all bat script.
you could alternatively take a look at the detailed steps here just download the blueline img instead of crosshatch... https://forum.xda-developers.com/pixel-3-xl/how-to/guide-progress-available-t3876849
Steps are exactly the same.
Click to expand...
Click to collapse
That link you provided is the guide I attempted to use when the flash_all.bat didn't work.

cmorin543 said:
That link you provided is the guide I attempted to use when the flash_all.bat didn't work.
Click to expand...
Click to collapse
Are you using the most recent ADB? I have had that exact missing variable error during a factory image flash and updating to the newest ADB fixed it for me.

pacman420 said:
Are you using the most recent ADB? I have had that exact missing variable error during a factory image flash and updating to the newest ADB fixed it for me.
Click to expand...
Click to collapse
I will double check that. Thanks!

cmorin543 said:
That link you provided is the guide I attempted to use when the flash_all.bat didn't work.
Click to expand...
Click to collapse
just to confirm.
a) you booted to bootloader using power + volume down key and then use volume down key to change it to bootloader and press power again (this reboots the bootloader)
b) while you are inside the ADB folder use shift + right click while you are inside the adb folder and then select the option -- open command window here.
c) considering that you have already connected your pixel to pc via usb type the command " fastboot devices " in the command prompt window to ensure that your device is detected.
d) once it has detected the device/s proceed to unzip the april factory image from https://dl.google.com/dl/android/aosp/blueline-pq2a.190405.003-factory-c12f40f0.zip in the same folder as ADB
e) Double click on flash.all bat file and let us know the result.
I am sure you might have followed above steps but just to make sure if everything is covered. as the above should actually fix all partition errors.

pacman420 said:
Are you using the most recent ADB? I have had that exact missing variable error during a factory image flash and updating to the newest ADB fixed it for me.
Click to expand...
Click to collapse
You are a genius -- apparently I did have the newest version of ADB in my downloads folder, but I was so used to using a specific directory with platform-tools for my old phone, I didn't realize it was an old version -- tried it with the newest version of ADB and it worked like a charm... too bad I already contacted google and they're sending me a new phone.. :-\
Thanks again for all your help guys.

Impossible to install any ROMs on Nexus 5

Hi Everybody
I have a Nexus 5 on which I installed different OSes (LineageOS, /e/, Ubuntu Touch). I had a lot of problems and now I'm trying to install a stock ROM but without success. Besides, I can't install anything on it anymore.
I downloaded 2 stock ROM => https://androidmtk.com/download-google-nexus-stock-rom-models
the 4.4 (KRT16M)
the 6.0.1 (MMB29Q)
Whatever the stock ROM used, here is the return of the script :
Code:
[email protected]:~/Bureau/Bureau_old/eelo_hammerhead/stock_rom/hammerhead-krt16m_4-4$ ./flash-all.sh
target didn't report max-download-size
sending 'bootloader' (2506 KB)...
OKAY [ 0.310s]
writing 'bootloader'...
OKAY [ 0.480s]
finished. total time: 0.790s
rebooting into bootloader...
OKAY [ 0.100s]
finished. total time: 0.150s
target didn't report max-download-size
sending 'radio' (42033 KB)...
OKAY [ 1.830s]
writing 'radio'...
OKAY [ 2.899s]
finished. total time: 4.729s
rebooting into bootloader...
OKAY [ 0.100s]
finished. total time: 0.150s
extracting android-info.txt (0 MB)...
extracting boot.img (8 MB)...
target didn't report max-download-size
archive does not contain 'boot.sig'
archive does not contain 'dtbo.img'
archive does not contain 'dt.img'
extracting recovery.img (8 MB)...
archive does not contain 'recovery.sig'
extracting system.img (676 MB)...
archive does not contain 'system.sig'
archive does not contain 'vbmeta.img'
archive does not contain 'vendor.img'
wiping userdata...
Couldn't parse erase-block-size '0x'.
Couldn't parse logical-block-size '0x'.
mke2fs 1.45.5 (07-Jan-2020)
/tmp/TemporaryFile-XjhxWS: Function de bibliothèque ext2 non implémentée lors de l'initialisation du superbloc
/usr/lib/android-sdk/platform-tools/mke2fs failed with status 1
mke2fs failed: 1
error: Cannot generate image for userdata
[email protected]:~/Bureau/Bureau_old/eelo_hammerhead/stock_rom/hammerhead-krt16m_4-4$
Could you help me to fix that phone ?

lool_lauris said:
Hi Everybody
I have a Nexus 5 on which I installed different OSes (LineageOS, /e/, Ubuntu Touch). I had a lot of problems and now I'm trying to install a stock ROM but without success. Besides, I can't install anything on it anymore.
I downloaded 2 stock ROM => https://androidmtk.com/download-google-nexus-stock-rom-models
the 4.4 (KRT16M)
the 6.0.1 (MMB29Q)
Whatever the stock ROM used, here is the return of the script :
Code:
[email protected]:~/Bureau/Bureau_old/eelo_hammerhead/stock_rom/hammerhead-krt16m_4-4$ ./flash-all.sh
target didn't report max-download-size
sending 'bootloader' (2506 KB)...
OKAY [ 0.310s]
writing 'bootloader'...
OKAY [ 0.480s]
finished. total time: 0.790s
rebooting into bootloader...
OKAY [ 0.100s]
finished. total time: 0.150s
target didn't report max-download-size
sending 'radio' (42033 KB)...
OKAY [ 1.830s]
writing 'radio'...
OKAY [ 2.899s]
finished. total time: 4.729s
rebooting into bootloader...
OKAY [ 0.100s]
finished. total time: 0.150s
extracting android-info.txt (0 MB)...
extracting boot.img (8 MB)...
target didn't report max-download-size
archive does not contain 'boot.sig'
archive does not contain 'dtbo.img'
archive does not contain 'dt.img'
extracting recovery.img (8 MB)...
archive does not contain 'recovery.sig'
extracting system.img (676 MB)...
archive does not contain 'system.sig'
archive does not contain 'vbmeta.img'
archive does not contain 'vendor.img'
wiping userdata...
Couldn't parse erase-block-size '0x'.
Couldn't parse logical-block-size '0x'.
mke2fs 1.45.5 (07-Jan-2020)
/tmp/TemporaryFile-XjhxWS: Function de bibliothèque ext2 non implémentée lors de l'initialisation du superbloc
/usr/lib/android-sdk/platform-tools/mke2fs failed with status 1
mke2fs failed: 1
error: Cannot generate image for userdata
[email protected]:~/Bureau/Bureau_old/eelo_hammerhead/stock_rom/hammerhead-krt16m_4-4$
Could you help me to fix that phone ?
Click to expand...
Click to collapse
Get the latest factory image from here... https://developers.google.com/android/images#hammerhead
You can use this guide to flash... https://forum.xda-developers.com/t/...rn-to-stock-unroot-save-your-nexus-5.2513701/

Lughnasadh said:
Get the latest factory image from here... https://developers.google.com/android/images#hammerhead
You can use this guide to flash... https://forum.xda-developers.com/t/...rn-to-stock-unroot-save-your-nexus-5.2513701/
Click to expand...
Click to collapse
Thank you for your reply and to try to help me.
What you mention, I've already done it. This is what is indicated between the code tags in my previous message.
The problem is indicated at the very bottom of the return of the comand line:
Code:
...
Couldn't parse erase-block-size '0x'.
Couldn't parse logical-block-size '0x'.
mke2fs 1.45.5 (07-Jan-2020)
/tmp/TemporaryFile-XjhxWS: Function de bibliothèque ext2 non implémentée lors de l'initialisation du superbloc
/usr/lib/android-sdk/platform-tools/mke2fs failed with status 1
mke2fs failed: 1
error: Cannot generate image for userdata
It seems that the organization of the partition is not correct. How to put this back in the studs?

lool_lauris said:
Thank you for your reply and to try to help me.
What you mention, I've already done it. This is what is indicated between the code tags in my previous message.
The problem is indicated at the very bottom of the return of the comand line:
Code:
...
Couldn't parse erase-block-size '0x'.
Couldn't parse logical-block-size '0x'.
mke2fs 1.45.5 (07-Jan-2020)
/tmp/TemporaryFile-XjhxWS: Function de bibliothèque ext2 non implémentée lors de l'initialisation du superbloc
/usr/lib/android-sdk/platform-tools/mke2fs failed with status 1
mke2fs failed: 1
error: Cannot generate image for userdata
It seems that the organization of the partition is not correct. How to put this back in the studs?
Click to expand...
Click to collapse
Not sure. Maybe try a factory reset or format data in TWRP?

There is something that prevents the writing of a rom (rom stock or other).
I managed to install a TWRP recovery but not the latest version, only 3.0.0-0.
When I'm under the recovery, I can use adb :
Code:
[email protected]:~/Bureau/Bureau_old/eelo_hammerhead$ wget http://iwf1.com/iwf-repo/parted.rar
--2021-01-31 19:17:30-- http://iwf1.com/iwf-repo/parted.rar
Résolution de iwf1.com (iwf1.com)… 2001:19f0:5:9cd:ad7b:2365:9457:e3cd, 45.63.15.195
Connexion à iwf1.com (iwf1.com)|2001:19f0:5:9cd:ad7b:2365:9457:e3cd|:80… connecté.
requête HTTP transmise, en attente de la réponse… 301 Moved Permanently
Emplacement : https://iwf1.com/iwf-repo/parted.rar [suivant]
--2021-01-31 19:17:30-- https://iwf1.com/iwf-repo/parted.rar
Connexion à iwf1.com (iwf1.com)|2001:19f0:5:9cd:ad7b:2365:9457:e3cd|:443… connecté.
requête HTTP transmise, en attente de la réponse… 200 OK
Taille : 158898 (155K) [application/x-rar-compressed]
Enregistre : «parted.rar.1»
parted.rar.1 100%[=======================>] 155,17K 727KB/s ds 0,2s
2021-01-31 19:17:31 (727 KB/s) - «parted.rar.1» enregistré [158898/158898]
[email protected]:~/Bureau/Bureau_old/eelo_hammerhead$ unrar e parted.rar
UNRAR 5.61 beta 1 freeware Copyright (c) 1993-2018 Alexander Roshal
Extracting from parted.rar
Would you like to replace the existing file parted
346680 bytes, modified on 2010-08-19 12:56
with a new one
346680 bytes, modified on 2010-08-19 12:56
[Y]es, [N]o, [A]ll, n[E]ver, [R]ename, [Q]uit n
No files to extract
[email protected]:~/Bureau/Bureau_old/eelo_hammerhead$ sudo adb push parted /
[sudo] Mot de passe de lool :
parted: 1 file pushed. 3.1 MB/s (346680 bytes in 0.107s)
[email protected]:~/Bureau/Bureau_old/eelo_hammerhead$ sudo adb shell
~ # chmod +x parted
~ # ./parted /dev/block/mmcblk0 p
Model: MMC SEM32G (sd/mmc)
Disk /dev/block/mmcblk0: 31.3GB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Number Start End Size File system Name Flags
1 524kB 67.6MB 67.1MB fat16 modem
2 67.6MB 68.7MB 1049kB sbl1
3 68.7MB 69.2MB 524kB rpm
4 69.2MB 69.7MB 524kB tz
5 69.7MB 70.3MB 524kB sdi
6 70.3MB 70.8MB 524kB aboot
7 70.8MB 72.9MB 2097kB pad
8 72.9MB 73.9MB 1049kB sbl1b
9 73.9MB 74.4MB 524kB tzb
10 74.4MB 75.0MB 524kB rpmb
11 75.0MB 75.5MB 524kB abootb
12 75.5MB 78.6MB 3146kB modemst1
13 78.6MB 81.8MB 3146kB modemst2
14 81.8MB 82.3MB 524kB metadata
15 82.3MB 99.1MB 16.8MB misc
16 99.1MB 116MB 16.8MB ext4 persist
17 116MB 119MB 3146kB imgdata
18 119MB 142MB 23.1MB laf
19 142MB 165MB 23.1MB boot
20 165MB 188MB 23.1MB recovery
21 188MB 191MB 3146kB fsg
22 191MB 192MB 524kB fsc
23 192MB 192MB 524kB ssd
24 192MB 193MB 524kB DDR
25 193MB 2291MB 2098MB ext4 system
26 2291MB 2322MB 31.0MB crypto
27 2322MB 3056MB 734MB ext4 cache
28 3056MB 31.3GB 28.2GB ext4 userdata
29 31.3GB 31.3GB 512B grow
~ # exit
[email protected]:~/Bureau/Bureau_old/eelo_hammerhead$
It seems that the partition 29 (grow) hasn't the good size : 512B instead of 5632B.
But probably this is not the only trouble...

I've been trying to bring a Nexus 5 back to life for quite a few months. Now I manage to reach the bootloader but I can't install any rom, either a stock rom or a custom rom.
I even have difficulties to install a recovery. For example for TRWP images ( https://eu.dl.twrp.me/hammerhead/ ) :
* possible to install an old twrp-2.8.7.1-hammerhead.img image and access it ;
* on the other hand if I install this image twrp-3.0.0-0-hammerhead.img I can access it but the phone shuts down as soon as I try to enter the menus.
* and for images of higher versions, nothing happens.
I think this phone has a partitioning problem. I followed this tutorial to try to go back to a standard partitioning or rather original partitioning but it is impossible to install twrp-3.3.1-HH-hammerhead.img.
So the only way to see what's going on via adb shell is to install this TRWP image twrp-2.8.7.1-hammerhead.img .
I tried to follow this : repartition method but it seems that it does not work out.
Could someone please help me to save this Nexus 5?

Try opening the flash-all.sh and remove the - w flag at the last line.

lool_lauris said:
[...] but it is impossible to install twrp-3.3.1-HH-hammerhead.img.
[...]
Click to expand...
Click to collapse
What do you mean by this exactly? Fastboot throwing errors? Please post the log

Unbrick Nairo / xt2075-3 / moto G5G plus after flashing LineageOS

Yesterday I wanted to flash my new Nairo / xt2075-3 / moto G5G plus with LineageOS. But unfortunately it doesn't boot anymore.
Only the EDL boot works. This blankfile works not:
https://mirrors.lolinet.com/firmware/motorola/nairo/blankflash/blankflash_nairo_from_QPNS30.37-Q3-42-51-2.zip
https://mirrors.lolinet.com/firmware/moto/nairo/blankflash/blankflash_nairo_from_QPNS30.37-Q3-42-51-2.zip
I downloaded a full TWRP backup (befor i bricket the device) and the latest stock ROM (using Motorola Rescuetool, but this requires fastboot)
This guide doesn't work either:
https://www.reddit.com/r/MotoG/comments/k73n66
I use the Image-Files from the Stock ROM this are the extrcted files:
27.05.2022 18:57 339968 abl.elf
27.05.2022 18:57 519296 aop.mbn
14.12.2020 02:09 35 blank-flash.bat
14.12.2020 02:09 38 blank-flash.sh
02.03.2022 15:59 13107456 bootloader.img
27.05.2022 18:50 708 default.xml
27.05.2022 18:57 126080 devcfg.mbn
02.03.2022 15:59 211712 gpt.bin
27.05.2022 18:57 519296 hyp.mbn
27.05.2022 18:50 134 index.xml
27.05.2022 18:57 519296 keymaster.mbn
27.05.2022 18:50 80 pkg.xml
27.05.2022 18:44 682968 programmer.elf
27.05.2022 18:57 257152 prov64.mbn
14.12.2020 02:09 181144 qboot
14.12.2020 02:09 229106 qboot.dll
14.12.2020 02:09 134292 qboot.exe
27.05.2022 18:57 76928 qupfw.elf
27.05.2022 19:03 7721216 singleimage.bin
31.10.2019 05:35 93624 star
31.10.2019 05:35 194682 star.exe
27.05.2022 18:57 126080 storsec.mbn
27.05.2022 18:50 4189312 tz.mbn
27.05.2022 18:50 2092160 uefi_sec.mbn
27.05.2022 18:57 4189312 xbl.elf
27.05.2022 18:57 126080 xbl_config.elf
Does somebody has any idea?

No ideas, also i never managed to get the moto downoad mode tool work

Iam now in Fastboot Mode, i hope i can boot twrp and i can flash my backup from stockfw or lineageos or the newest stock fw. What is the best way?
I use the blankflash from the racer, that phone has the same SM7250
(I have thw XT2075-3/nairo):
E:\Motorola_nairo\download\racer\blankflash_racer_RPD31.Q4U-39-26-17>.\qboot.exe blank-flash
< waiting for device >
Motorola qboot utility version 3.86
[ 0.000] Opening device: \\.\COM4
[ 0.031] Detecting device
[ 0.047] ...cpu.id = 286 (0x11e)
[ 0.047] ...cpu.sn = +++++++++
[ 0.054] Opening singleimage
[ 0.058] Loading package
[ 0.067] ...filename = pkg.xml
[ 0.070] Loading programmer
[ 0.073] ...filename = programmer.elf
[ 0.077] Sending programmer
[ 0.251] Handling things over to programmer
[ 0.251] Identifying CPU version
[ 0.251] Waiting for firehose to get ready
[ 3.314] ...SM_SAIPAN 2.0
[ 3.314] Determining target secure state
[ 3.329] ...secure = yes
[ 3.392] Configuring device...
[ 3.392] Skipping UFS provsioning as target is secure
[ 3.392] Configuring device...
[ 3.548] Flashing GPT...
[ 3.548] Flashing partition with gpt.bin
[ 3.548] Initializing storage
[ 3.626] ...blksz = 4096
[ 4.111] Re-initializing storage...
[ 4.111] Initializing storage
[ 4.548] Flashing bootloader...
[ 4.548] Wiping ddr
[ 4.579] Flashing abl_a with abl.elf
[ 4.626] Flashing aop_a with aop.mbn
[ 4.673] Flashing qupfw_a with qupfw.elf
[ 4.704] Flashing tz_a with tz.mbn
[ 4.939] Flashing hyp_a with hyp.mbn
[ 4.986] Flashing devcfg_a with devcfg.mbn
[ 5.017] Flashing keymaster_a with keymaster.mbn
[ 5.064] Flashing storsec_a with storsec.mbn
[ 5.095] Flashing uefisecapp_a with uefi_sec.mbn
[ 5.236] Flashing prov_a with prov64.mbn
[ 5.267] Flashing xbl_config_a with xbl_config.elf
[ 5.298] Flashing xbl_a with xbl.elf
[ 5.564] Rebooting to fastboot
[ 5.564] Total time: 5.564s

1.692 / 5.000
Hello, I was successful now I have a working phone again. But it didn't work with the Motorola Rescue Tool. I used this to download the latest firmware. Then I flashed this firmware with Fastboot and the script from (https://kfhost.net/flashfile):
fastboot getvar max-sparse-size
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash vbmeta vbmeta.img
fastboot flash radio radio.img
fastboot flash bluetooth BTFM.bin
fastboot flash dsp dspso.bin
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash dtbo dtbo.img
fastboot flash recovery recovery.img
fastboot flash super super.img_sparsechunk.0
fastboot flash super super.img_sparsechunk.1
fastboot flash super super.img_sparsechunk.2
fastboot flash super super.img_sparsechunk.3
fastboot flash super super.img_sparsechunk.4
fastboot flash super super.img_sparsechunk.5
fastboot flash super super.img_sparsechunk.6
fastboot flash super super.img_sparsechunk.7
fastboot flash super super.img_sparsechunk.8
fastboot erase carrier
fastboot erase userdata
fastboot erase metadata
fastboot erase ddr
fastboot oem fb_mode_clear
echo -----------------------------------------------------------------------------------------------
echo English - Process concluded!
echo Português - Processo concluído!
echo English - Press any key to restart the phone!
echo Português - Pressione qualquer tecla para reiniciar o celular!
echo -----------------------------------------------------------------------------------------------
pause
fastboot reboot
exit
I hope someone else can use it ;-).

Germanandroidplayer said:
Iam now in Fastboot Mode, i hope i can boot twrp and i can flash my backup from stockfw or lineageos or the newest stock fw. What is the best way?
I use the blankflash from the racer, that phone has the same SM7250
(I have thw XT2075-3/nairo):
E:\Motorola_nairo\download\racer\blankflash_racer_RPD31.Q4U-39-26-17>.\qboot.exe blank-flash
< waiting for device >
Motorola qboot utility version 3.86
[ 0.000] Opening device: \\.\COM4
[ 0.031] Detecting device
[ 0.047] ...cpu.id = 286 (0x11e)
[ 0.047] ...cpu.sn = +++++++++
[ 0.054] Opening singleimage
[ 0.058] Loading package
[ 0.067] ...filename = pkg.xml
[ 0.070] Loading programmer
[ 0.073] ...filename = programmer.elf
[ 0.077] Sending programmer
[ 0.251] Handling things over to programmer
[ 0.251] Identifying CPU version
[ 0.251] Waiting for firehose to get ready
[ 3.314] ...SM_SAIPAN 2.0
[ 3.314] Determining target secure state
[ 3.329] ...secure = yes
[ 3.392] Configuring device...
[ 3.392] Skipping UFS provsioning as target is secure
[ 3.392] Configuring device...
[ 3.548] Flashing GPT...
[ 3.548] Flashing partition with gpt.bin
[ 3.548] Initializing storage
[ 3.626] ...blksz = 4096
[ 4.111] Re-initializing storage...
[ 4.111] Initializing storage
[ 4.548] Flashing bootloader...
[ 4.548] Wiping ddr
[ 4.579] Flashing abl_a with abl.elf
[ 4.626] Flashing aop_a with aop.mbn
[ 4.673] Flashing qupfw_a with qupfw.elf
[ 4.704] Flashing tz_a with tz.mbn
[ 4.939] Flashing hyp_a with hyp.mbn
[ 4.986] Flashing devcfg_a with devcfg.mbn
[ 5.017] Flashing keymaster_a with keymaster.mbn
[ 5.064] Flashing storsec_a with storsec.mbn
[ 5.095] Flashing uefisecapp_a with uefi_sec.mbn
[ 5.236] Flashing prov_a with prov64.mbn
[ 5.267] Flashing xbl_config_a with xbl_config.elf
[ 5.298] Flashing xbl_a with xbl.elf
[ 5.564] Rebooting to fastboot
[ 5.564] Total time: 5.564s
Click to expand...
Click to collapse
Hey, can I ask you how did you manage to unbrick it? My phone doesn't get recognized via fastboot. It seems dead but when I connect it to the pc, it gets recognized as "Qualcomm HS-USB QDLoader 9008"

Ok I cannot believe it was so stupid, it didn't work because I had to long press power button + volume down while executing the blank flash file, as said in this post (I put the screenshot below)
{
"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"
}

OK, I hope your problem is solved and your phone is working again? It's been some time now. I don't remember having to hold down any keys. My problem with the blank flash file was that the signatures were probably wrong. So I grabbed an empty flash file from the other phone that has the same processor.

I have the same problem but with XT2075-5 (US retail).
Hard bricked it after flashing Lineage OS 19.1, which is Android 12. (Brick was not the fault of Lineage, I flashed the radio from the stock ROM and it bricked the device - very stupid - did this because the device did not work with Verizon after flashing Lineage, but obviously did not know wtf I was doing)
I have tried both of the blankflash files that are currently available on lolinet for nairo, uploaded on 7-20-2022, as well as "blankflash_nairo_from_QPNS30.37-Q3-42-51-2.zip" which I found on androidfilehost (https://androidfilehost.com/?fid=14655340768118479195)
All my attempts appear to be successful, and the device LED goes on for about 10 secs, then it turns off. The phone does not enter fastboot. I suspect the blankflash files are from an Android 11 stock ROM, and that I am now screwed.
If anyone else has this situation and figures it out, please share.

officerplonk said:
I have the same problem but with XT2075-5 (US retail).
Hard bricked it after flashing Lineage OS 19.1, which is Android 12. (Brick was not the fault of Lineage, I flashed the radio from the stock ROM and it bricked the device - very stupid - did this because the device did not work with Verizon after flashing Lineage, but obviously did not know wtf I was doing)
I have tried both of the blankflash files that are currently available on lolinet for nairo, uploaded on 7-20-2022, as well as "blankflash_nairo_from_QPNS30.37-Q3-42-51-2.zip" which I found on androidfilehost (https://androidfilehost.com/?fid=14655340768118479195)
All my attempts appear to be successful, and the device LED goes on for about 10 secs, then it turns off. The phone does not enter fastboot. I suspect the blankflash files are from an Android 11 stock ROM, and that I am now screwed.
If anyone else has this situation and figures it out, please share.
Click to expand...
Click to collapse
Hi,
Did you read my post from 05/29/2022?

officerplonk said:
I have the same problem but with XT2075-5 (US retail).
Hard bricked it after flashing Lineage OS 19.1, which is Android 12. (Brick was not the fault of Lineage, I flashed the radio from the stock ROM and it bricked the device - very stupid - did this because the device did not work with Verizon after flashing Lineage, but obviously did not know wtf I was doing)
I have tried both of the blankflash files that are currently available on lolinet for nairo, uploaded on 7-20-2022, as well as "blankflash_nairo_from_QPNS30.37-Q3-42-51-2.zip" which I found on androidfilehost (https://androidfilehost.com/?fid=14655340768118479195)
All my attempts appear to be successful, and the device LED goes on for about 10 secs, then it turns off. The phone does not enter fastboot. I suspect the blankflash files are from an Android 11 stock ROM, and that I am now screwed.
If anyone else has this situation and figures it out, please share.
Click to expand...
Click to collapse
I have the same problem with XT2075-3(GB retail with Android 11), I flashed the radio from the US stock ROM and it bricked the device after a restart... So this may not be caused by Android 12. I flashed US radio cause there's no 5G NR reception in China. 'All my attempts appear to be successful, and the device LED goes on for about 10 secs, then it turns off. The phone does not enter fastboot.' - That makes two of us. Now waiting for a solution, too.

Still cannot access fastboot, any one can provide the firehose file, please?

[email protected] said:
Still cannot access fastboot, any one can provide the firehose file, please?
Click to expand...
Click to collapse
See Post #3 and #4 or if this dont work #6

Here is the link again: https://mirrors.lolinet.com/firmware/motorola/nairo
This didn't work on my Nairo. I'm using this (see below) because Nairo and Racer should contain the same CPU/SOC.
lolinet mirrors - firmware, software, iso etc.
lolinet mirrors - powered by h5ai
mirrors.lolinet.com
After loading blankfile you have to create new partitons and flash the stock ROM
you can use the script from here (https://kfhost.net/flashfile). The Stock ROM you can get with the Motorola Rescue Tool.