Database Info

[GUIDE] How to extract system files from stock firmware

First of all: Tools to be used in this guide were developed by user And_pda from Russian 4pda.ru forum. So all credits must go to And_pda
The original thread (in Russian) is here. Actually the original thread is about several tools to works with different images for different phones. But we will talk only about Moto G.
The guide will describe how to extract all files from system partition from stock firmware. The tools works under Windows (I personally tested them on Win 7).
If you unzip any stock firmware (for instance RETAIL-GB_4.4.2_KLB20.9-1.10-1.9_cid7_CFC_1FF_v5_SVC.xml.zip) you will find 3 files, which represents system partition: system.img_sparsechunk.0, system.img_sparsechunk.1 and system.img_sparsechunk.2.
There are two steps to be performed to get system file extracted.
Step 1 - it will convert 3 files (system.img_sparsechunk.0, 1, 2) into temporary file system_motog.img:
1. Download RKwinToolsMod_v2_8.rar and extract it.
Lets assume that it is extracted to D:\RKwinToolsMod_v2_8. If not you have to modify ConvertMotoG.bat file located in Scripts folder.
You have to edit the string set wf=D:\RKwinToolsMod_v2_8\Cygwin\ according to path where you extracted archive.
2. Copy ConvertMotoG.bat to the folder where stock firmware is unzipped (i.e. where system.img_sparsechunk.0, system.img_sparsechunk.1 and system.img_sparsechunk.2 are lockated)
3. Run CMD and "cd" to the folder where where stock firmware is unzipped
4. In CMD run ConvertMotoG.bat. File system_motog.img will be created.
Step 2 - it will extract all files and folders from system_motog.img:
1. Download ImgExtractor_1_3_4.rar and extract it.
2. Create directory System in the folder where system_motog.img is located;
3. Copy ImgExtractor.exe into the folder where system_motog.img is located;
4. Run CMD and "cd" to the folder where system_motog.img is located
5. In CMD run the following: ImgExtractor system_motog.img System
After ImgExtractor finished you will have all system files and folders in System directory.
That's all
PS. ImgExtractor also can extract modem firmware (NON-HLOS.bin)

Thanks for this. I was looking for a method to do this not too long ago and had no luck.....Thanks again!
Sent from my Moto G using XDA Premium 4 mobile app

romuloxiii said:
Thanks for this. I was looking for a method to do this not too long ago and had no luck.....Thanks again!
Sent from my Moto G using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Anyone made a working CWM installer yet of a ROM that I can tweak like in the old pixelrom days ?
I have a ROM ready and some init.d startup scripts but my installer script is lacking and needing lots of work.

i double clicked the convertmotog.bat but nothing happened

Confirmed working here. Make sure you set path in the copied batch file and followed all steps of the instructions.
Sent from my XT1032 using Tapatalk

wildestpixel said:
Confirmed working here. Make sure you set path in the copied batch file and followed all steps of the instructions.
Sent from my XT1032 using Tapatalk
Click to expand...
Click to collapse
i get this and nothing more, am i suppose to wait or anything?
Create system_motog.img Please wait...
Press any key to continue . . .

Working here too. Thanks a lot for the guide!! :good:

Nandeh said:
Working here too. Thanks a lot for the guide!! :good:
Click to expand...
Click to collapse
for some reason i cannot use the convertmotog.bat can you send me the unpacked file?

gwiqu said:
for some reason i cannot use the convertmotog.bat can you send me the unpacked file?
Click to expand...
Click to collapse
Here we go. Simply delete the last file extension .txt

My question hopefully someone knows how to recreate sparsechunks from system. IMG ?
Sent from my Nexus 7 using Tapatalk

wildestpixel said:
My question hopefully someone knows how to recreate sparsechunks from system. IMG ?
Sent from my Nexus 7 using Tapatalk
Click to expand...
Click to collapse
Why not just simply redownload the firmware zip? I think that recreate sparsechunk parts won't be easy...

Nandeh said:
Why not just simply redownload the firmware zip? I think that recreate sparsechunk parts won't be easy...
Click to expand...
Click to collapse
That's not what I'm trying to achieve. I wanted to make a fastboot flashable ROM with root and busybox.
Sent from my Nexus 7 using Tapatalk

wildestpixel said:
That's not what I'm trying to achieve. I wanted to make a fastboot flashable ROM with root and busybox.
Sent from my Nexus 7 using Tapatalk
Click to expand...
Click to collapse
Ok, then you don't need to divide the system.img into parts, you can flash it directly with fastboot:
fastboot flash system system.img

Nandeh said:
Ok, then you don't need to divide the system.img into parts, you can flash it directly with fastboot:
fastboot flash system system.img
Click to expand...
Click to collapse
If it were that easy I would have done it! File system limits flash chunks to c. 512MB so sparsechunks are required.
Sent from my Nexus 7 using Tapatalk

wildestpixel said:
My question hopefully someone knows how to recreate sparsechunks from system. IMG ?
Click to expand...
Click to collapse
I have asked tools developer about recreating sparsechunks - he is not going to make such tool.
Another point. If your bootloader is locked you will not able to flash recreated sparsechunks.
wildestpixel said:
If it were that easy I would have done it! File system limits flash chunks to c. 512MB so sparsechunks are required.
Click to expand...
Click to collapse
There are following fastboot options:
-P enable parallel loading for multi-flash if there is no enough memory on host to load whole image
-S <size>[K|M|G] automatically sparse files greater than size. 0 to disable
Have you tried it to flash not divided system.img ?

Hi, I have problem with "Step 1"...
When I run ConvertMotoG.bat, it does nothing
Windows 8.1 x64

Ja_som said:
Hi, I have problem with "Step 1"...
When I run ConvertMotoG.bat, it does nothing
Windows 8.1 x64
Click to expand...
Click to collapse
hard to tell from the screenshot, but my guess is you need to rename your sparsechunk files. if they are named system.img_sparsechunk1 you need to change them to system.img_sparsechunk.1 for the BAT file to work.
make sure to rename each file: system.img_sparsechunk.1 system.img_sparsechunk.2 system.img_sparsechunk.3 ... etc
hope that helps/works

cedarknoll said:
hard to tell from the screenshot, but my guess is you need to rename your sparsechunk files. if they are named system.img_sparsechunk1 you need to change them to system.img_sparsechunk.1 for the BAT file to work.
make sure to rename each file: system.img_sparsechunk.1 system.img_sparsechunk.2 system.img_sparsechunk.3 ... etc
hope that helps/works
Click to expand...
Click to collapse
Thank you, now is everything OK

cedarknoll said:
hard to tell from the screenshot, but my guess is you need to rename your sparsechunk files. if they are named system.img_sparsechunk1 you need to change them to system.img_sparsechunk.1 for the BAT file to work.
make sure to rename each file: system.img_sparsechunk.1 system.img_sparsechunk.2 system.img_sparsechunk.3 ... etc
hope that helps/works
Click to expand...
Click to collapse
I was just going to post it as i figured it out, but nice find though, if i had read it it would've saved a lot of time hahaha
And btw thanks a lot to the OP, really useful

cedarknoll said:
hard to tell from the screenshot, but my guess is you need to rename your sparsechunk files. if they are named system.img_sparsechunk1 you need to change them to system.img_sparsechunk.1 for the BAT file to work.
make sure to rename each file: system.img_sparsechunk.1 system.img_sparsechunk.2 system.img_sparsechunk.3 ... etc
hope that helps/works
Click to expand...
Click to collapse
i get this
D:\RK\Scripts>ConvertMotoG.bat
Create system_motog.img Please wait...
'D:\RK\Cygwinsparse2img' is not recognized as an internal or external command,
operable program or batch file.
'D:\RK\Cygwinsparse2img' is not recognized as an internal or external command,
operable program or batch file.
'D:\RK\Cygwinsparse2img' is not recognized as an internal or external command,
operable program or batch file.
Press any key to continue . . .
what do i do?
edit: nvm i got it

Problem with flashing /system

Hello all.
I erased system partition in asus fonepad7 me175cg dual sim with fastboot erase system
now i cant flash it.
i tried:
fastboot flash system system.zip before erasing /data errors:invalid argument after erasing /data errors: file exists
fastboot flash update system.zip errors: unable to rename file /cache/update.zip: cross-device linkE:unable to write fi
E:unable to write file: /cache/update.zip
fastboot flash system firmware.zip errors: E:zlib memory/data/corruption error failed:File exists
fastboot flash update firmware.zip
and i renamed the system.zip to img, erros like zip.
(i made system.zip from firmware downloaded from asus)
(the firmware is in this link)
when i turn my device on, it loops on intel logo.
what i do now?
surry for bad english
__________________________________________________ _________-
I dont like sex with non-partner. because i think it makes me like animals

......
is there any way?
Which file exists?
Which partition i should erase for delete exist file?
__________________________________________________ _________
I dont like sex with non-partner. because i think it makes me like animals

[HELP] Read-only filesystem? e2fsck fails as the Moto G is F2FS. Help please!

After an unfortunate restart yesterday from a misbehaving app, my phone has decided that the whole of the userdata partition is going to be read-only. At the very least, it's stopping me, fastboot, adb, and even the home launcher (when it boots) from running anything. Here's a video of the crash: http://youtu.be/8orBg5ivxsQ?t=1m3s
Now I've spent hours trawling through the various threads, and the ones that has got me closest to anything useful has been this one:
XDA Nexus 5 - [HOWTO][GUIDE] Repairing corrupted /data partition
Now the commands work well, and I have a list of the Moto G (16gb version) superblocks here:
/dev/block/platform/msm_sdcc.1/by-name/system on /system type ext4 (rw,seclabel,relatime,data=ordered)
/dev/block/platform/msm_sdcc.1/by-name/userdata on /data type f2fs (rw,seclabel,relatime,background_gc=on,discard,user_xattr,inline_xattr,acl,errors=recover,active_logs=6)
/dev/block/platform/msm_sdcc.1/by-name/cache on /cache type ext4 (rw,seclabel,relatime,noauto_da_alloc,data=writeback)
/dev/block/platform/msm_sdcc.1/by-name/fsg on /fsg type ext4 (rw,seclabel,nodev,noatime,nodiratime)
/dev/block/platform/msm_sdcc.1/by-name/modem on /firmware type ext4 (rw,seclabel,nodev,noatime,nodiratime,data=ordered)
/dev/block/platform/msm_sdcc.1/by-name/persist on /persist type ext4 (rw,seclabel,nodev,noatime,nodiratime,data=ordered)​
Running e2fsk works on all but the userdata superblock, which is the one I cannot write to. It fails with the message
The superblock could not be read or does not describe a correct ext2 filesystem. If the device is valid and it really contains an ext2 filesystem (and not swap or ufs or something else), then the superblock is corrupt, and you might try running e2fsck with an alternate superblock: e2fsck -b 8193 <device>​
Clearly I can't e2fsck the f2fs partition (and I have no fsck), does anyone have any suggestions?
----​
Tried and failed:
Nandroid restore (none found and can't write a new one to storage)
ADB Shell reading/deleting anythign from /data/media/0/
fasboot flash *anything*
mfastboot flash *anything*

Enter Bootloader screen (power on with vol down held)
Option (1) - Try flashing the gpt.bin included in the Motorola Firmware Image. Fastboot command:
fastboot flash partition gpt.bin​
Option (2) - Flash the entire firmware image by following this tutorial:
http://forum.xda-developers.com/showthread.php?t=2542219​
NB. fastboot erase userdata - will wipe all photos, music etc. Linux and some versions of windows will give you access to ADB in Custom Recovery. From there you can backup photos / internal storage by running the command: adb pull /sdcard/ C:/motog/
Tell me what model you have and I can link you to the Motorola Firmware Image.

Thanks.
Running Option (1) gives me the messages "(bootloader) Preflash verification failed" and "FAILED (remote failure)" in cmd, and the error version downgraded for primary_gpt on the phone screen. I have also attempted Option 2, but again that apparently has no effect. Even flashing a different recovery image (CWM, TWRP, Stock) does not change anything.
Even something simple like running a nandroid backup command fails through recovery- hence me thinking that the partition has gone read-only.
The model is a 16gb UK XT1032.

You need to use a 4.4.4 firmware image. See the FAQ regarding 'Preflash verification failed.'
Retail UK 4.4.4:
http://forum.xda-developers.com/showthread.php?p=54872143

I downloaded the firmware file (you're correct, I was probably previously using a 4.3 image) and tried to flash it using both fastboot and mfastboot.
Despite both methods giving no errors, it has absolutely no effect on the recovery, or once the phone boots (still the same wallpaper that I can see through the lockscreen before I unlock it and everything crashes).
Here's a video of it crashing, just for reference (note that xposed is clearly installed, but flashing the 'remove xposed' zip also does nothing): http://youtu.be/8orBg5ivxsQ

Are you using fastboot or mfastboot? What commands have you used? Do the 'flash system system.img' commands actually match the filenames of the firmware you have downloaded?

I have tried both actually. Here's the log from using mfastboot but it's the same for both. No errors reported in cmd or on the phone, but it doesn't make any actual changes to anything. Bizarre.
{
"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"
}

Fastboot is not user-friendly because it is meant for use by engineers. You will not be given helpful error messages. Please see this related post about the danger of misusing fastboot: http://forum.xda-developers.com/showpost.php?p=56123415&postcount=23
Try all three versions of fastboot in this zip: https://www.androidfilehost.com/?fid=23578570567719065
To be clear, here is the full list of required Fastboot commands:
mfastboot flash partition gpt.bin
mfastboot flash motoboot motoboot.img
mfastboot flash logo logo.bin
mfastboot flash boot boot.img
mfastboot flash recovery recovery.img
mfastboot flash system system.img_sparsechunk.0
mfastboot flash system system.img_sparsechunk.1
mfastboot flash system system.img_sparsechunk.2
mfastboot flash modem NON-HLOS.bin
mfastboot erase modemst1
mfastboot erase modemst2
mfastboot flash fsg fsg.mbn
mfastboot erase cache
mfastboot erase userdata​
NB. Are system.img_sparsechunk.0 / .1 / .2 the actual file-names? Some firmware images include a forth sparsechunk.

I have not knowingly run fastboot erase all (I didn't know that was a command actually, perhaps for the best).
I can confirm that the commands I am running are exactly as you suggest, and with all the correct files. I have written three different .bat files not that I can run from from the command line, using fastboot, mfastboot and fastboot-moto-windows.
No luck unfortunately, despite the positive messages from cmd and the bootloader.

Have you tried converting 'userdata' to ext4 and back to f2fs in custom recovery?
TWRP > Wipe > Advanced > Repair > select 'data' - then choose repair
Afterwards reflash sparsechunks if necessary.

I'm using Philz custom recovery, but I have found a similar option.
I have tried turning on the f2fs <-> ext4 option in Custom Recovery Options and run it on /data and /data/media.
Selecting etx4 the first time, no effect.
Selecting f2fs the second time, no effect.
(despite both times it saying it had succeeded)

Silently said:
I'm using Philz custom recovery, but I have found a similar option.
I have tried turning on the f2fs <-> ext4 option in Custom Recovery Options and run it on /data and /data/media.
Selecting etx4 the first time, no effect.
Selecting f2fs the second time, no effect.
(despite both times it saying it had succeeded)
Click to expand...
Click to collapse
hi
I have my moto g doing the exact same thing as yours in your video I cant even flash a custom recovery to mine if I flash anything it says its completed but its done nothing completely read-only your the only person ive found on the net with the same problem as me.
Have you got any where with your G?
thanks

Skinpipe said:
hi
Have you got any where with your G?
thanks
Click to expand...
Click to collapse
No luck, I'm afraid.

Silently said:
No luck, I'm afraid.
Click to expand...
Click to collapse
I have same issue. Hard reset/ wiped many times but it goes back to same screen. Ask same password (I know password) but when I type password it keep on crashing on each and every program. Also when I do repair file system it just keep on repairing. Any help??

talkways said:
Also when I do repair file system it just keep on repairing. Any help??
Click to expand...
Click to collapse
From what I understand, the actual memory of the phone has become corrupted (a bit like when a memory stick formats itself as RAW) and there's no way to fix it.

If memory is corrupted, it should not load Android operating system at all. :S
Any more advices??

Silently said:
From what I understand, the actual memory of the phone has become corrupted (a bit like when a memory stick formats itself as RAW) and there's no way to fix it.
Click to expand...
Click to collapse
I've exactly the same problem with my XT1032 4.4.4. No solution yet

talkways said:
If memory is corrupted, it should not load Android operating system at all. :S
Click to expand...
Click to collapse
Well that's a damn good point. I assume it is something to do with the block structure of the underlying file system then, and it is something there which is preventing disk writes.

Good. We figured out the problem. Any solution??
I have tried many recoveries but it goes to standard recovery. Only way to go to custom recovery is boot via command fastboot boot recovery.img.
Device bootloader is unlocked.

Hi, anyone fixed the problem? This happened to my wife's phone few days ago.
Bootloader unlocked
Recovery TWRP
rom Paranoid (based on 4.4.4 android)
please help

[Q] TF300T TWRP bootloop. Return to stock?

Any help would be greatly appreciated. I recently flashed the new TRWP using fastboot. Went fine. I then tried to wipe and flash the newest version of KatKiss. I thought it also went fine but after reboot, it bootloops TWRP. I can tell the tablet to boot Android, but it just hangs. Then when I try to boot back into TWRP, it starts the bootloop all over again. Here is what it's doing during bootloop.
Running OpenRecoveryScript
E:Could not mount /data and unable to find crypto footer.
E:Unable to mount '/data'
E:Unable to recreate /data/media folder.
Updating partition details...
E:Unable to mount '/data'
...done
E:Unable to mount storage.
E:Unable to mount /data/media during GUI startup.
Full SELinux support is present.
E:Unable to mount /data/media/TWRP/.twrps when trying to read settings file.
Processing AOSP recovery commands...
E:Unable to mount '/data'
-- Wiping DATA Partition...
Formatting Cache using make_ext4fs function.
After about 1 minute it will follow with...
E:Unable to mount '/data'
-- Data Partition Wipe Complete!
Done processing script file
It will then reboot within 3 seconds after displaying the last line, and begin it all over again.
I'm hoping someone can tell me what options I have at this point. Would I be able to return to stock using fastboot and ASUS's blob from their website? Again, any help is greatly appreciated!

Solved.
I had already figured on buying a new tablet regardless, so I figured I'd go ahead and try to recover using fastboot. It did work. I noticed this post had a few views, and on the chance there were other people having the same issue, I'll post how I did it. I recommend using Windows 7 for this.
Download the appropriate firmware from ASUS's website. (WW, US, CN, JP etc...) Unzip the file twice until you have the META-INF folder and blob file. I placed both of these into a folder named "TF300t" directly on the C drive.
Install your device drivers, I used the Google SDK drivers.
Boot into fastboot.
Run these commands...
fastboot erase system
fastboot erase recovery
fastboot erase userdata
fastboot erase boot
fastboot erase misc
fastboot erase cache
fastboot -i 0x0B05 flash system c:\TF300t\blob (Again, this is where I saved my blob file.)
You should see something along these lines, when flashing your system...
C:\>fastboot -i 0x0B05 flash system c:\TF300t\blob
erasing 'system'...
OKAY [ 1.665s]
sending 'system' (800931 KB)...
OKAY [142.128s]
writing 'system'...
OKAY [155.462s]
finished. total time: 299.255s
When it's finished, run the last command...
fastboot -i 0x0B05 reboot
From this point, you should be booted back into stock.

Recreate the partition
anim0sity said:
I had already figured on buying a new tablet regardless, so I figured I'd go ahead and try to recover using fastboot. It did work. I noticed this post had a few views, and on the chance there were other people having the same issue, I'll post how I did it. I recommend using Windows 7 for this.
Download the appropriate firmware from ASUS's website. (WW, US, CN, JP etc...) Unzip the file twice until you have the META-INF folder and blob file. I placed both of these into a folder named "TF300t" directly on the C drive.
Install your device drivers, I used the Google SDK drivers.
Boot into fastboot.
Run these commands...
fastboot erase system
fastboot erase recovery
fastboot erase userdata
fastboot erase boot
fastboot erase misc
fastboot erase cache
fastboot -i 0x0B05 flash system c:\TF300t\blob (Again, this is where I saved my blob file.)
You should see something along these lines, when flashing your system...
C:\>fastboot -i 0x0B05 flash system c:\TF300t\blob
erasing 'system'...
OKAY [ 1.665s]
sending 'system' (800931 KB)...
OKAY [142.128s]
writing 'system'...
OKAY [155.462s]
finished. total time: 299.255s
When it's finished, run the last command...
fastboot -i 0x0B05 reboot
From this point, you should be booted back into stock.
Click to expand...
Click to collapse
anim0sity
What happened if you dont have the blob???
I had a tab, i complete erase all the partition and i cannot install any app, always had error 963
How i can recreate all the partition of my tablet?
It running android 5 lollipop
Regards,

Shouldn't be any reason you don't have the blob file. You can download it straight from ASUS's website. When you download it, it comes in a zip file. You have to extract it twice. So unzip the original zip file downloaded, then unzip the file you get from unzipping the original. From there, you should have the blob file needed to flash your tablet back to stock using fast boot / sdk tools.
Sent from my SAMSUNG-SGH-I317 using XDA Free mobile app

anim0sity said:
Shouldn't be any reason you don't have the blob file. You can download it straight from ASUS's website. When you download it, it comes in a zip file. You have to extract it twice. So unzip the original zip file downloaded, then unzip the file you get from unzipping the original. From there, you should have the blob file needed to flash your tablet back to stock using fast boot / sdk tools.
Sent from my SAMSUNG-SGH-I317 using XDA Free mobile app
Click to expand...
Click to collapse
Hi Anim0sity
I downloaded the package and starting doit the process
H:\android-sdk\platform-tools>fastboot devices
015d15b4fc481208 fastboot
H:\android-sdk\platform-tools>fastboot erase system
_
Now is hanging here what i can do it??
Thanks

successful
Hi
After many tries and plug the usb cable in the back of my tower i successful install the firmware
Regards,

HI to rstore to stock using twrp, is it as simple as downloading the file to the tablet, unziping once then flashing the resulting file, or is it a bit more difficult than that?

Bootloop and can't access to TWRP

Hello !
Well, after long research and testing some solutions, I create this post because I'm stuck at one point.
So, after a wipe in the fasboot mode, my TF700 get stuck into a bootloop with no access to recovery (The more I can have is 5 second with the TWRP splashscreen before rebooting). The ROM that was installed on my tablet is Cromi-kk.
I followed this help thread : http://forum.xda-developers.com/transformer-tf300t/help/guide-t2854495 and I'm stuck at the last point
Code:
fastboot -i 0x0B05 flash system boot.blob
Here is what it said on my computer :
Code:
[email protected]:~$ sudo fastboot -i 0x0B05 flash system boot.blob
erasing 'system'...
OKAY [ 2.355s]
sending 'system' (800927 KB)...
but nothing is moving on the computer, and the tablet is still displaying the fastboot screen...
So I really don't know what to do now, I hope one of you can have a solution
Thank you in advance !

Heck! I cannot believe this went undetected for so long!!! @lj50036
Hey Josh, have a look at this and make the edit! LMAO
@nhibel: Assuming you are trying to flash the stock blob in fastboot and you extracted the stock rom zip twice and put the file called just "blob" into your fastboot folder, the command to flash the stock blob is
Code:
fastboot -i 0x0B05 flash system blob
Nothing is happening because fastboot cannot find a file named boot.blob. Which makes sense since it does not exist. Unless you unpacked the blob.....

I don't think it's because of that. On the help thread it is said to rename the blob file into boot.blob, what I've did ^^
I tried again with renaming the file to blob, but it's the same, nothing is happening :/
Code:
[email protected]:~$ sudo fastboot -i 0x0B05 flash system blob
[sudo] Mot de passe de camille*:
erasing 'system'...
OKAY [ 2.431s]
sending 'system' (800927 KB)...

Maybe you can try the BUSTER99 way to access your bootloader.
http://forum.xda-developers.com/showthread.php?t=2179759&page=6
This was ones the sollution for my TF700T.
Good luck.
Scenic-3

nhibel said:
I don't think it's because of that. On the help thread it is said to rename the blob file into boot.blob, what I've did ^^
I tried again with renaming the file to blob, but it's the same, nothing is happening :/
Code:
[email protected]:~$ sudo fastboot -i 0x0B05 flash system blob
[sudo] Mot de passe de camille*:
erasing 'system'...
OKAY [ 2.431s]
sending 'system' (800927 KB)...
Click to expand...
Click to collapse
Show me a screenshot of your fastboot folder with "show extensions" enabled and make sure the blob is not named blob.blob.
I probably would start from scratch: Delete all blobs from the fastboot directory, extract the blob from Asus firmware, drag it "as is" into fastboot directory and use the fastboot flash system blob command

Here is some good news !
At first, I was trying to flash the blob from a Linux computer, but it wasn't working. So I tried again from another computer, which running on Windows 10. Again, it didn't work, exactly the same than on the Linux computer.
Finally, I tried something else. When I was looking for solutions at the beggining of my problem, I've dowloaded a twrp.blob, but I was unable to flash it at this time. I just tried again, and thank of the help of the help thread, I finally succeeded to flash TWRP (I had to try 2 times before the flash succeeded), and I should be able now to flash a rom !
Well, I lost everything that was on my device, but it works !
Thank you so much for spending some time to help me !

berndblb said:
Heck! I cannot believe this went undetected for so long!!! @lj50036
Hey Josh, have a look at this and make the edit! LMAO
@nhibel: Assuming you are trying to flash the stock blob in fastboot and you extracted the stock rom zip twice and put the file called just "blob" into your fastboot folder, the command to flash the stock blob is
Code:
fastboot -i 0x0B05 flash system blob
Nothing is happening because fastboot cannot find a file named boot.blob. Which makes sense since it does not exist. Unless you unpacked the blob.....
Click to expand...
Click to collapse
I am confused ??
Thx Josh

So was I. Never mind. Didn't realise you instructed to rename the blob... @[email protected]
Sent from my K00C using Tapatalk