Develop Bugs

Fixing a bootloader-bricked Galaxy S3 using an SD card (Qualcomm SGS3 variants)

This thread is dedicated to booting Qualcomm Snapdragon-based Samsung Galaxy S3 models from an SD card.
As I understand it, this only works because the Snapdragon boot ROM (NOT the bootloader, which resides on the eMMC - this is part of the CPU) has a fallback mode which reads the bootloader from an SD card if the eMMC fails. To date, the only devices I am aware of that have this fallback mode are the Snapdragon Galaxy S3 models designed for use in the US. As such, this will not work on international/Exynos based phones.
The process of preparing an SD card for this is fairly simple. All that is needed is a working, rooted phone and an empty SD card.
The dumps at the end of this post were obtained by various people using a variant of the following command:
Code:
busybox dd if=/dev/block/mmcblk0 of=/sdcard/backup.bin bs=1M count=70
Depending on the device, you may need more than 70MB, but on the Sprint Galaxy S3, the first 70MB of the eMMC contains everything needed for download mode without including identifying information in the dump, like the EFS partition for example.
If you are absolutely certain your SD card is empty, you can change the dd command to "of=/dev/block/mmblk1" to write the eMMC backup image directly to the SD card instead of to a file. Be very careful working with dd! mmcblk0 is the eMMC and mmcblk1 is the external SD card.
This should be obvious, but cross-device dumps will not work! This is the main reason so many people are finding themselves in need of this guide!
Use common sense - do your research and don't cross-flash, especially between US and international ROMs!
If your model is not listed there, search the forums or ask someone to make a dump for you.
Please note: if your phone model is not listed here, that doesn't mean this method won't work - however, I would appreciate it if everyone would do their research instead of bombarding me with private messages.
I hope this helps! Flash wisely!
For posterity, this is the content of the OP that led me to discover the SD boot mode by accident:
I am trying to fix a 16GB Sprint Samsung Galaxy S3 that went through a rooting process and failed, leaving download mode and most other recovery options inaccessible.
I don't have a USB download mode jig or JTAG equipment, but I noticed it's recognized as "05c6:9008 Qualcomm, Inc. Gobi Wireless Modem (QDL mode)" when connected to a Linux computer.
From what I've read, not many people have gotten it out of this mode, however, I've found guides that imply the NAND/eMMC is writable in this mode with qdload.pl. None of the files I've seen want to be flashed with this tool - the generic, unsigned 8960_msimage.mbn/MPRG8960.hex files to get it into EMMC USB storage mode don't execute/stay intact after flashing, so I'm guessing they failed the signature check.
Is anyone willing to dump the partition table/bootloader from their working 16GB Sprint SGS3 for me?
Code:
dd if=/dev/block/mmcblk0 of=/sdcard/backup.bin bs=1048576 count=70
I unfortunately don't know what stages of the bootloader were corrupted, and I'm not sure what address to flash aboot to, if that's even possible with qdload.
Downloads:
Sprint SPH-L710: http://www.mediafire.com/download/231uhy6l80jx74n/debrick_sph_l710.img.xz (Thanks @CNexus!)
AT&T SGH-i747: http://d-h.st/iEy (Thanks @Android_Geeek!)
T-Mobile SGH-T999: http://www.mediafire.com/download/grgyera66w0rt25/debrick_SGH-T999.img (Thanks @Techlyfe!)

Sure, gimme a sec.
EDIT: You know you can find these in the firmware zips freezes has in his thread, right?

CNexus said:
Sure, gimme a sec.
EDIT: You know you can find these in the firmware zips freezes has in his thread, right?
Click to expand...
Click to collapse
I've been looking around for stock firmware packages and couldn't find them. I'll look a little harder...
EDIT: This? sbl1.mbn? Downloading it, but I'll be pretty disappointed if it doesn't work after using ~700MB...

Top of this thread you will find all the latest MD4 stuff
http://forum.xda-developers.com/showthread.php?p=32176586
Sent from the future via Tapatalk 4

No, the firmware zips, not the ROMs
And yes. The bootloaders are there, they're smaller, like 20~ MB
Grab the one that says "MD4 firmware/modem/baseband"
EDIT: This thread may be useful, it's a different device but the board is the same (MSM8960).

CNexus said:
No, the firmware zips, not the ROMs
And yes. The bootloaders are there, they're smaller, like 20~ MB
Grab the one that says "MD4 firmware/modem/baseband"
Click to expand...
Click to collapse
Found it, thanks. Unfortunately, flashing the SBL didn't fix it.
What address does aboot get flashed to? Can someone post the partition table so I can figure out the offset?

Here are two more links that give more technical information on the MSM8960 bootloaders.
Here
http://forum.xda-developers.com/showthread.php?t=1856327
And here
http://forum.xda-developers.com/showthread.php?t=1769411
You should be able to find most everything you need there.

CNexus said:
Here are two more links that give more technical information on the MSM8960 bootloaders.
Here
http://forum.xda-developers.com/showthread.php?t=1856327
And here
http://forum.xda-developers.com/showthread.php?t=1769411
You should be able to find most everything you need there.
Click to expand...
Click to collapse
I've been over those threads multiple times and I still don't know what address to plug into qdload to flash aboot (mmcblk0p5).
parted /dev/block/mmcblk0 might help.

Ok, I was just trying to help.
Code:
Disk /dev/block/mmcblk0: 15.8GB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Number Start End Size File system Name Flags
1 4194kB 67.1MB 62.9MB modem
2 67.1MB 67.2MB 131kB sbl1
3 67.2MB 67.5MB 262kB sbl2
4 67.5MB 68.0MB 524kB sbl3
5 68.0MB 70.1MB 2097kB aboot
6 70.1MB 70.6MB 524kB rpm

CNexus said:
Ok, I was just trying to help.
Code:
Disk /dev/block/mmcblk0: 15.8GB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Number Start End Size File system Name Flags
1 4194kB 67.1MB 62.9MB modem
2 67.1MB 67.2MB 131kB sbl1
3 67.2MB 67.5MB 262kB sbl2
4 67.5MB 68.0MB 524kB sbl3
5 68.0MB 70.1MB 2097kB aboot
6 70.1MB 70.6MB 524kB rpm
Click to expand...
Click to collapse
Thanks! Sorry I'm being so demanding - you have no obligation to help me, after all.
Could I trouble you for the size in bytes? Again, thanks for the help!
Edit: This is probably asking too much, but it would be immensely helpful:
"dd if=/dev/block/mmcblk0 of=/sdcard/backup.bin bs=1M count=70"

gTan64 said:
"dd if=/dev/block/mmcblk0 of=/sdcard/backup.bin bs=1M count=70"
Click to expand...
Click to collapse
Anyone with a rooted SGS3 willing to do this? I don't know what got messed up or how - the guy who gave this phone to me just said it wouldn't reboot after one of the steps in the rooting process - but flashing that backup with qdload could be a good method of fixing bricked phones without JTAG!
In the spirit of sharing, if I manage to fix it, I'll be doing an Ubuntu "port" (building a bootloader/kernel for desktop Linux distros, not Ubuntu Touch), hopefully with Freedreno drivers too.

Sorry, couldn't get the size in bytes or else I would have posted that instead of the MB
Here's the output of dd
http://db.tt/nvwsj4e5

CNexus said:
Sorry, couldn't get the size in bytes or else I would have posted that instead of the MB
Here's the output of dd
http://db.tt/nvwsj4e5
Click to expand...
Click to collapse
It's supposed to be the first 70MB of the eMMC chip, containing the partition table, the 64MB firmware partition, the three bootloader stages, and aboot. Unless I gave the wrong command or you changed it, 70 bytes isn't going to be much help

gTan64 said:
It's supposed to be the first 70MB of the eMMC chip, containing the partition table, the 64MB firmware partition, the three bootloader stages, and aboot. Unless I gave the wrong command or you changed it, 70 bytes isn't going to be much help
Click to expand...
Click to collapse
I know, but that is the output, I was surprised as well

CNexus said:
I know, but that is the output, I was surprised as well
Click to expand...
Click to collapse
I'm guessing the version of dd on your phone is a stripped down version that doesn't recognize suffixes.
dd if=/dev/block/mmcblk0 of=/sdcard/backup.bin bs=1024 count=71680

gTan64 said:
It's supposed to be the first 70MB of the eMMC chip, containing the partition table, the 64MB firmware partition, the three bootloader stages, and aboot. Unless I gave the wrong command or you changed it, 70 bytes isn't going to be much help
Click to expand...
Click to collapse
I know, but that is the output, I was surprised as well
EDIT: dd would not accept "MB" for some reason, so I just wrote out the number of bytes. Here's the file
http://d-h.st/G3l
Md5sum: 12ca987274d905865a337d687f9e2a73

CNexus said:
I know, but that is the output, I was surprised as well
EDIT: dd would not accept "MB" for some reason, so I just wrote out the number of bytes. Here's the file
http://d-h.st/G3l
Md5sum: 12ca987274d905865a337d687f9e2a73
Click to expand...
Click to collapse
I miscalculated - it should have been 70.6MB - but I was able to find the aboot offset, so it's okay!
Huge thanks! Flashing now!

gTan64 said:
I miscalculated - it should have been 70.6MB - but I was able to find the aboot offset, so it's okay!
Huge thanks! Flashing now!
Click to expand...
Click to collapse
After the process failed for the umpteenth time, I concluded qdload only loads code into RAM and executes it - of course, in this case, it wasn't executing the backup. It seems I need an alternative method of accessing the eMMC.
The aboot/appsbl address I used was incorrect, so I still need to figure out where it's supposed to be loaded in RAM.
This doesn't appear to be common knowledge, unfortunately. Looks like I may have to JTAG it after all...

gTan64 said:
Looks like I may have to JTAG it after all...
Click to expand...
Click to collapse
I am happy to eat those words! I was able to get CNexus's backup onto an SD card (fixing the rpm, tz, and boot.img partitions that weren't part of the backup) and it booted that with no trouble! I'm currently in download mode flashing a stock ROM! Yay!!!
Thanks CNexus for the eMMC dump! I'll be posting a fixed dd image for an SD card soon for anyone who wants it. No more JTAG!

gTan64 said:
I am happy to eat those words! I was able to get CNexus's backup onto an SD card (fixing the rpm, tz, and boot.img partitions that weren't part of the backup) and it booted that with no trouble! I'm currently in download mode flashing a stock ROM! Yay!!!
Thanks CNexus for the eMMC dump! I'll be posting a fixed dd image for an SD card soon for anyone who wants it. No more JTAG!
Click to expand...
Click to collapse
HOLY GEEZ. AWESOME SAUCE. Please post a thread in development outlining your process so we can get it stickied !!
Also, PM me a Dropbox link to it or something and I'll mirror everywhere lol :thumbup::beer::beer:
This is actually great. Do you happen to know how the phone was initially bricked?
The Thanks button is just to avoid "THANKS" posts in threads. Nothing more. Don't defeat the purpose of why it was introduced.

Bricked firmware, Help.

Hello. I was bricked my sm-p605, so I played enough. Can someone make full backup, I mean full - dd if=/dev/block/mmcblk0pxx /sdcard or so, I think I need all partitions, it doesn't mater what version of ROM, Please help me to fix it, Odin does not work, usb does't work to, I think I can flash it via twrp using "send terminal command" function with dd if=system.img of /dev/block/mmcblk0p23. And if you can please make files as partition names like dd if=/dev/block/mmcblk0p23 of=/sdcard(or so)/mmcblk0p23 or jus 0p23. Actually Odin does work, but I can't flash original firmware, I getting errors with sbl1.mbn. Sorry for my bad english and thanks.
I think I need repartition my device using right pit file, so do anyone know where can I get it?

Tautvaldas said:
Hello. I was bricked my sm-p605, so I played enough. Can someone make full backup, I mean full - dd if=/dev/block/mmcblk0pxx /sdcard or so, I think I need all partitions, it doesn't mater what version of ROM, Please help me to fix it, Odin does not work, usb does't work to, I think I can flash it via twrp using "send terminal command" function with dd if=system.img of /dev/block/mmcblk0p23. And if you can please make files as partition names like dd if=/dev/block/mmcblk0p23 of=/sdcard(or so)/mmcblk0p23 or jus 0p23. Actually Odin does work, but I can't flash original firmware, I getting errors with sbl1.mbn. Sorry for my bad english and thanks.
I think I need repartition my device using right pit file, so do anyone know where can I get it?
Click to expand...
Click to collapse
I need all packages except:
/dev/block/mmcblk0p23 \system
/dev/block/mmcblk0p26 \data
/dev/block/mmcblk0p14 \recovery
/dev/block/mmcblk0p15 /boot
So I think I need:
/dev/block/mmcblk0p10
/dev/block/mmcblk0p11
/dev/block/mmcblk0p12
/dev/block/mmcblk0p13
/dev/block/mmcblk0p14
/dev/block/mmcblk0p15
/dev/block/mmcblk0p16
/dev/block/mmcblk0p17
/dev/block/mmcblk0p18
/dev/block/mmcblk0p19
/dev/block/mmcblk0p20
/dev/block/mmcblk0p21
/dev/block/mmcblk0p22
Please anyone help.

Can you not get your P605 to show up when you connect to Odin? Here is what I would do:
1. Try a different USB port
2. Try a different USB cable
3. Try a different pc
I see no reason why you should not be able to recover your tablet.
Download your firmware from here:
You just need to register to be able to download.
http://www.sammobile.com/firmwares/

[Q&A] [MOD][NOV 21] MultiROM v30

Q&A for [MOD][NOV 21] MultiROM v30
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for [MOD][NOV 21] MultiROM v30. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!

Kernel: does not have kexec-hardboot patch
Guys, help me, please, solve the problem. I updated to Android 5.0.1 and now the program writes to me: "Kernel: does not have kexec-hardboot patch". There is a patch for 5.0.1?

FalseTrue said:
Guys, help me, please, solve the problem. I updated to Android 5.0.1 and now the program writes to me: "Kernel: does not have kexec-hardboot patch". There is a patch for 5.0.1?
Click to expand...
Click to collapse
You need a kernel with kaxec hardboot patch. Try elemental x. Or see if there is a stock one with the patch.

madbat99 said:
You need a kernel with kaxec hardboot patch. Try elemental x. Or see if there is a stock one with the patch.
Click to expand...
Click to collapse
Thanks for the reply. And how fast is usually a new version of the patch will released?

FalseTrue said:
Thanks for the reply. And how fast is usually a new version of the patch will released?
Click to expand...
Click to collapse
As soon as a new stock kernel comes out, someone usually immediately makes one with kaxec

Thanks you
madbat99 said:
As soon as a new stock kernel comes out, someone usually immediately makes one with kaxec
Click to expand...
Click to collapse
Thank you very much for your answer. Thought so.

Error MultiROM mr_update A0001
Hi, I have a big problem...
I have a 1+1 with cm11s 44S in primary ROM. I use MultiROM for testing new ROM's... I have AK35 cm12 kernel
I have installed 5 or 6 custom ROM cm12, without problem..
since lastest Rom's of multiple Dev, I can't install new version of their rom...
Exemple: I can install LiquidSmooth v4.0.0 of 21/11/2014... but i can't install the version of 27/11/2014 and newer..
Other custom ROM have same problem..
Install doesn't work because this problem: E:Error executing updater binary in zip '/tmp/mr_update.zip'
It comes only with newer versions..
Only AICP and Euphoria ROM are good and want to install...in their newer version
Installing ROM LS-LP-v4.0-2014-12-06-liqu...
Creating folders and images for type 1
Flashing ZIP file /sdcard/Download/LS-LP-v4.0-2014-12-06-liquid_bacon.zip
ROM: LS-LP-v4.0-2014-12-06-liqu
Preparing ZIP file...
rm: can't remove '/tmp/mr_update.zip': No such file or directory
Copying ZIP to /tmp...
updating: META-INF/com/google/android/updater-script
zip warning: Local Entry CRC does not match CD: META-INF/com/google/android/updater-script
(deflated 74%)
Changing mounts to ROM LS-LP-v4.0-2014-12-06-liqu...
I:Mount: Unable to find partition for path '/data'
I:Backup folder set to '/realdata/media/0/TWRP/BACKUPS/5e7b4ef6'
I:mount '/realdata/media/0' '/sdcard' process ended with RC=0
Irocessing '/data_t'
I:Created '/data_t' folder.
Irocessing '/system'
Irocessing '/cache'
I:Recreating /cache/recovery folder.
Partition Logs:
/modem | /dev/block/mmcblk0p1 | Size: 64MB
Flags: IsPresent
Primary_Block_Device: /dev/block/mmcblk0p1
Display_Name: modem
Storage_Name: modem
Backup_Path: /modem
Backup_Name: modem
Backup_Display_Name: modem
Storage_Path: /modem
Current_File_System: emmc
Fstab_File_System: emmc
Backup_Method: dd
/sbl1 | /dev/block/mmcblk0p2 | Size: 0MB
Flags: IsPresent
Primary_Block_Device: /dev/block/mmcblk0p2
Display_Name: sbl1
Storage_Name: sbl1
Backup_Path: /sbl1
Backup_Name: sbl1
Backup_Display_Name: sbl1
Storage_Path: /sbl1
Current_File_System: emmc
Fstab_File_System: emmc
Backup_Method: dd
/rpm | /dev/block/mmcblk0p6 | Size: 0MB
Flags: IsPresent
Primary_Block_Device: /dev/block/mmcblk0p6
Display_Name: rpm
Storage_Name: rpm
Backup_Path: /rpm
Backup_Name: rpm
Backup_Display_Name: rpm
Storage_Path: /rpm
Current_File_System: emmc
Fstab_File_System: emmc
Backup_Method: dd
/tz | /dev/block/mmcblk0p8 | Size: 0MB
Flags: IsPresent
Primary_Block_Device: /dev/block/mmcblk0p8
Display_Name: tz
Storage_Name: tz
Backup_Path: /tz
Backup_Name: tz
Backup_Display_Name: tz
Storage_Path: /tz
Current_File_System: emmc
Fstab_File_System: emmc
Backup_Method: dd
/modem_st1 | /dev/block/mmcblk0p10 | Size: 1MB
Flags: IsPresent
Primary_Block_Device: /dev/block/mmcblk0p10
Display_Name: modem_st1
Storage_Name: modem_st1
Backup_Path: /modem_st1
Backup_Name: modem_st1
Backup_Display_Name: modem_st1
Storage_Path: /modem_st1
Current_File_System: emmc
Fstab_File_System: emmc
Backup_Method: dd
/modem_st2 | /dev/block/mmcblk0p11 | Size: 1MB
Flags: IsPresent
Primary_Block_Device: /dev/block/mmcblk0p11
Display_Name: modem_st2
Storage_Name: modem_st2
Backup_Path: /modem_st2
Backup_Name: modem_st2
Backup_Display_Name: modem_st2
Storage_Path: /modem_st2
Current_File_System: emmc
Fstab_File_System: emmc
Backup_Method: dd
/static_nv_bk | /dev/block/mmcblk0p13 | Size: 10MB
Flags: IsPresent
Primary_Block_Device: /dev/block/mmcblk0p13
Display_Name: static_nv_bk
Storage_Name: static_nv_bk
Backup_Path: /static_nv_bk
Backup_Name: static_nv_bk
Backup_Display_Name: static_nv_bk
Storage_Path: /static_nv_bk
Current_File_System: emmc
Fstab_File_System: emmc
Backup_Method: dd
/oppodycnvbk | /dev/block/mmcblk0p12 | Size: 10MB
Flags: IsPresent
Primary_Block_Device: /dev/block/mmcblk0p12
Display_Name: oppodycnvbk
Storage_Name: oppodycnvbk
Backup_Path: /oppodycnvbk
Backup_Name: oppodycnvbk
Backup_Display_Name: oppodycnvbk
Storage_Path: /oppodycnvbk
Current_File_System: emmc
Fstab_File_System: emmc
Backup_Method: dd
/aboot | /dev/block/mmcblk0p5 | Size: 1MB
Flags: IsPresent
Primary_Block_Device: /dev/block/mmcblk0p5
Display_Name: aboot
Storage_Name: aboot
Backup_Path: /aboot
Backup_Name: aboot
Backup_Display_Name: aboot
Storage_Path: /aboot
Current_File_System: emmc
Fstab_File_System: emmc
Backup_Method: dd
/boot | /dev/block/mmcblk0p7 | Size: 16MB
Flags: Can_Be_Backed_Up IsPresent
Primary_Block_Device: /dev/block/mmcblk0p7
Display_Name: Boot
Storage_Name: boot
Backup_Path: /boot
Backup_Name: boot
Backup_Display_Name: Boot
Storage_Path: /boot
Current_File_System: emmc
Fstab_File_System: emmc
Backup_Method: dd
/realdata | /dev/block/mmcblk0p28 | Size: 56189MB Used: 1710MB Free: 39907MB Backup Size: 1710MB
Flags: Can_Be_Mounted Can_Be_Wiped Wipe_During_Factory_Reset Wipe_Available_in_GUI IsPresent Can_Be_Encrypted Has_Data_Media Can_Encrypt_Backup Use_Userdata_Encryption Is_Storage Is_Settings_Storage
Symlink_Path: /realdata/media/0
Symlink_Mount_Point: /sdcard
Primary_Block_Device: /dev/block/mmcblk0p28
Display_Name: Realdata
Storage_Name: Internal Storage
Backup_Path: /data
Backup_Name: data
Backup_Display_Name: Data
Storage_Path: /realdata/media/0
Current_File_System: ext4
Fstab_File_System: ext4
Backup_Method: files
/misc | /dev/block/mmcblk0p21 | Size: 1MB
Flags: IsPresent
Primary_Block_Device: /dev/block/mmcblk0p21
Display_Name: misc
Storage_Name: misc
Backup_Path: /misc
Backup_Name: misc
Backup_Display_Name: misc
Storage_Path: /misc
Current_File_System: emmc
Fstab_File_System: emmc
Backup_Method: dd
/recovery | /dev/block/mmcblk0p17 | Size: 16MB
Flags: IsPresent
Primary_Block_Device: /dev/block/mmcblk0p17
Display_Name: Recovery
Storage_Name: recovery
Backup_Path: /recovery
Backup_Name: recovery
Backup_Display_Name: Recovery
Storage_Path: /recovery
Current_File_System: emmc
Fstab_File_System: emmc
Backup_Method: dd
/logo | /dev/block/mmcblk0p22 | Size: 16MB
Flags: IsPresent
Primary_Block_Device: /dev/block/mmcblk0p22
Display_Name: logo
Storage_Name: logo
Backup_Path: /logo
Backup_Name: logo
Backup_Display_Name: logo
Storage_Path: /logo
Current_File_System: emmc
Fstab_File_System: emmc
Backup_Method: dd
/reserve4 | /dev/block/mmcblk0p27 | Size: 64MB
Flags: IsPresent
Primary_Block_Device: /dev/block/mmcblk0p27
Display_Name: reserve4
Storage_Name: reserve4
Backup_Path: /reserve4
Backup_Name: reserve4
Backup_Display_Name: reserve4
Storage_Path: /reserve4
Current_File_System: emmc
Fstab_File_System: emmc
Backup_Method: dd
/data | /realdata/media/0/multirom/roms/LS-LP-v4.0-2014-12-06-liqu/data | Size: 0MB Used: 0MB Free: 0MB Backup Size: 0MB
Flags: Can_Be_Mounted Can_Be_Wiped Use_Rm_Rf Can_Be_Backed_Up IsPresent Ignore_Blkid
Primary_Block_Device: /realdata/media/0/multirom/roms/LS-LP-v4.0-2014-12-06-liqu/data
Display_Name: Data
Storage_Name: data_t
Backup_Path: /data
Backup_Name: data
Backup_Display_Name: Data
Storage_Path: /data_t
Current_File_System: ext4
Fstab_File_System: ext4
Bind_Of: /realdata
Backup_Method: files
/system | /realdata/media/0/multirom/roms/LS-LP-v4.0-2014-12-06-liqu/system | Size: 0MB Used: 0MB Free: 0MB Backup Size: 0MB
Flags: Can_Be_Mounted Can_Be_Wiped Use_Rm_Rf Can_Be_Backed_Up Wipe_Available_in_GUI IsPresent Ignore_Blkid
Primary_Block_Device: /realdata/media/0/multirom/roms/LS-LP-v4.0-2014-12-06-liqu/system
Display_Name: System
Storage_Name: System
Backup_Path: /system
Backup_Name: system
Backup_Display_Name: System
Storage_Path: /system
Current_File_System: ext4
Fstab_File_System: ext4
Bind_Of: /realdata
Backup_Method: files
/cache | /realdata/media/0/multirom/roms/LS-LP-v4.0-2014-12-06-liqu/cache | Size: 0MB Used: 0MB Free: 0MB Backup Size: 0MB
Flags: Can_Be_Mounted Can_Be_Wiped Use_Rm_Rf Can_Be_Backed_Up Wipe_During_Factory_Reset Wipe_Available_in_GUI IsPresent Ignore_Blkid
Primary_Block_Device: /realdata/media/0/multirom/roms/LS-LP-v4.0-2014-12-06-liqu/cache
Display_Name: Cache
Storage_Name: Cache
Backup_Path: /cache
Backup_Name: cache
Backup_Display_Name: Cache
Storage_Path: /cache
Current_File_System: ext4
Fstab_File_System: ext4
Bind_Of: /realdata
Backup_Method: files
I:Running cmd "dd if="/dev/block/mmcblk0p7" of="/realdata/media/0/multirom/roms/LS-LP-v4.0-2014-12-06-liqu/boot.img""
32768+0 records in
32768+0 records out
16777216 bytes (16.0MB) copied, 0.786623 seconds, 20.3MB/s
Current boot sector was used as base for fake boot.img!
I:Running cmd "echo '/dev/block/mmcblk0p7' > /tmp/mrom_fakebootpart"
I:Running cmd "mv "/dev/block/mmcblk0p7" "/dev/block/mmcblk0p7-orig""
I:Running cmd "ln -s "/realdata/media/0/multirom/roms/LS-LP-v4.0-2014-12-06-liqu/boot.img" "/dev/block/mmcblk0p7""
ZIP uses block updates
Creating system.img...
I:Creating image with cmd: make_ext4fs -l 1333M -a "/system" -S /file_contexts "/realdata/media/0/multirom/system.img"
Creating filesystem with parameters:
Size: 1397751808
Block size: 4096
Blocks per group: 32768
Inodes per group: 7760
Inode size: 256
Journal blocks: 5332
Label:
Blocks: 341248
Block groups: 11
Reserved block group size: 87
Created filesystem with 11/85360 inodes and 11226/341248 blocks
I:Running cmd "losetup "/dev/block/loop0" "/realdata/media/0/multirom/system.img""
I:Running cmd "mv "/dev/block/mmcblk0p14" "/dev/block/mmcblk0p14-orig" && ln -s "/dev/block/loop0" "/dev/block/mmcblk0p14""
I:Running cmd "rm "/realdata/media/0/multirom/system.img""
I:Running cmd "echo "/dev/block/mmcblk0p14" > /tmp/mrom_fakesyspart"
Installing '/tmp/mr_update.zip'...
Checking for MD5 file...
Skipping MD5 check: no MD5 file found
I:Zip contains SELinux file_contexts file in its root. Extracting to /file_contexts
I:Legacy property environment initialized.
line 2 col 6: syntax error, unexpected ENDIF, expecting $end
line 12 col 5: syntax error, unexpected ELSE, expecting $end
line 17 col 6: syntax error, unexpected ENDIF, expecting $end
3 parse errors
I:Legacy property environment disabled.
E:Error executing updater binary in zip '/tmp/mr_update.zip'
rm: can't remove 'META-INF/com/google/android': No such file or directory
Failed to install ZIP!
I:Running cmd "busybox umount -d /tmpsystem"
umount: can't umount /tmpsystem: No such file or directory
I:Running cmd "rm "/dev/block/mmcblk0p14""
I:Running cmd "mv "/dev/block/mmcblk0p14"-orig "/dev/block/mmcblk0p14""
I:Running cmd "rm "/dev/block/mmcblk0p7""
I:Running cmd "mv "/dev/block/mmcblk0p7"-orig "/dev/block/mmcblk0p7""
Restoring mounts...
umount: can't umount /realdata: Device or resource busy
umount: can't umount /system: Invalid argument
umount: can't umount /data: Invalid argument
umount: can't umount /cache: Invalid argument
umount: can't umount /sdcard: Invalid argument
umount: can't umount /realdata: Device or resource busy
umount: can't umount /system: Invalid argument
umount: can't umount /data: Invalid argument
umount: can't umount /cache: Invalid argument
umount: can't umount /sdcard: Invalid argument
umount: can't umount /realdata: Device or resource busy
umount: can't umount /system: Invalid argument
umount: can't umount /data: Invalid argument
umount: can't umount /cache: Invalid argument
umount: can't umount /sdcard: Invalid argument
umount: can't umount /realdata: Device or resource busy
umount: can't umount /system: Invalid argument
umount: can't umount /data: Invalid argument
umount: can't umount /cache: Invalid argument
umount: can't umount /sdcard: Invalid argument
umount: can't umount /realdata: Device or resource busy
umount: can't umount /system: Invalid argument
umount: can't umount /data: Invalid argument
umount: can't umount /cache: Invalid argument
umount: can't umount /sdcard: Invalid argument
umount: can't umount /realdata: Device or resource busy
umount: can't umount /system: Invalid argument
umount: can't umount /data: Invalid argument
umount: can't umount /cache: Invalid argument
umount: can't umount /sdcard: Invalid argument
umount: can't umount /realdata: Device or resource busy
umount: can't umount /system: Invalid argument
umount: can't umount /data: Invalid argument
umount: can't umount /cache: Invalid argument
umount: can't umount /sdcard: Invalid argument
umount: can't umount /realdata: Device or resource busy
umount: can't umount /system: Invalid argument
umount: can't umount /data: Invalid argument
umount: can't umount /cache: Invalid argument
umount: can't umount /sdcard: Invalid argument
umount: can't umount /realdata: Device or resource busy
umount: can't umount /system: Invalid argument
umount: can't umount /data: Invalid argument
umount: can't umount /cache: Invalid argument
umount: can't umount /sdcard: Invalid argument
umount: can't umount /realdata: Device or resource busy
umount: can't umount /system: Invalid argument
umount: can't umount /data: Invalid argument
umount: can't umount /cache: Invalid argument
umount: can't umount /sdcard: Invalid argument
umount: can't umount /realdata: Device or resource busy
losetup: /dev/block/loop1: No such device or address
losetup: /dev/block/loop2: No such device or address
losetup: /dev/block/loop3: No such device or address
losetup: /dev/block/loop4: No such device or address
losetup: /dev/block/loop5: No such device or address
losetup: /dev/block/loop6: No such device or address
losetup: /dev/block/loop7: No such device or address
Iartition /realdata is mounted during TWPartitionManager:op_Context()
Updating partition details...
I:mount '/data/media/0' '/sdcard' process ended with RC=0
Iata backup size is 1710MB, free: 39893MB.
...done
I:Unable to find storage partition '/realdata/media/0'.
I:mount '/data/media/0' '/sdcard' process ended with RC=0
I:Backup folder set to '/data/media/0/TWRP/BACKUPS/5e7b4ef6'
Erasing incomplete ROM...
I:Set page: 'action_complete'
I:Set page: 'clear_vars'
I:Set page: 'multirom_add'
I:Set page: 'main'
I:Set page: 'clear_vars'
I:Set page: 'main2'
I:Set page: 'advanced'
I:Set page: 'confirm_action'
I:Set page: 'action_page'
I:Copying file /tmp/recovery.log to /data/media/0/recovery.log
Click to expand...
Click to collapse
Sorry for my very very bad English.
Pleaaase! HELP me!
Thanks for regarding!

Wifi stops working after install
I've tried 3 separate times to install multirom and each time it installs fine but once installed my wifi is automatically turned off. I go into settings and try to turn it back on, and it says it's turning it on but then it sits indefinitely without ever actually turning it back on. I'm using a Nexus 7 (2013) with 5.0.1 Any ideas?

Losing wifi
Everytime I install Multirom, I seem to lose wifi -- the indicator won't light up when I press it, and though I can slide the button to the right on the Wi-Fi Settings page,
This Nexus 7 arrived yesterday & I wasted little time trying to get Multirom on it, basically with the intent of booting Ubuntu. I'm not exactly a hacker, but I have managed to root my Nexus 4, so I'm not completely useless.
Twice now I've done this with the same result:
1. Successfully gain root with the device using Chainfire's "one-click script."
2. Use the MultiROM Manager app to do its stuff, which it successfully completes.
3. Reboot.
The reboot process completes successfully as far as I can tell, and everything seems to work, except wifi.

So here's my problem: I really want to install Multirom, but I can't unless it's rooted. As far as I can tell, the easiest way to root the device is flashing Chainfire's rom, but apparently doing so kills wifi. I guess I could proceed to install Multirom at that point and then install a different rooted rom but that's a little complicated, especially since I'm afraid of bricking in my ignorance.
Is there a simpler way for me to proceed? Or am I missing something.
Please note I am on Ubuntu only so cannot use Wug's windows thing.

Okay, so I used a buddy's Windows machine to root the N7 with Wugfresh's toolkit. Got home and used the Multirom Manager app to install, and watched it reboot and then add the kexec patch. I rebooted, and now have lost wifi, so I don't know what to do next. Did I miss a step somewhere? Should I copy a third-party rom and flash that?

So, let me try again: is this a known issue? It's the second time I've lost wifi after installing Multirom using the app. after rooting -- first with Chainfire's rom and then using Wugfresh's toolkit. I'm pretty sure I followed directions to the letter. Is there a fix I can try?

More information just in case: this is a Nexus 7 (2013), brand new
Android version 5.0.1
Kernel version
3.4..0-g20f5923
[email protected] #66
Wed Sep 25 22:02:11 CEST 2013
Build number LRX22C
Glad to provide more information if needed.

Hello All,
I am currently running multirom v30 on my 2013 Nexus 7.
Edit: I have an extfat formatted usb stick. I installed a cm12 nightly to the usb drive via multirom. When it boots the rom now hangs on the Google screen while the light on the usb drive flashes slowly. I am currently at a loss at what to do. Any and all help is appreciated!!!

ray field said:
More information just in case: this is a Nexus 7 (2013), brand new
Android version 5.0.1
Kernel version
3.4..0-g20f5923
[email protected] #66
Wed Sep 25 22:02:11 CEST 2013
Build number LRX22C
Glad to provide more information if needed.
Click to expand...
Click to collapse
Don't think it related to multirom. I have all the same as you and WiFi is fine. Have you tried forgetting that network and retyping the password? Make sure frequency is set to auto. WiFi is fine on multirom on nexus 7(2013) 5.0.1.

Calendar and book reader
I have been playing with multirom since I got my nexus 7 (2013). I installed it first thing. I installed several roms and I was wondering if there were any way to synch my calendar and my book reader across the roms. Calendar especially.

I'm running Paranoid 4.6 Beta 6 with patched Franco Kernel r17 as primary and want to flash latest CM 12 nightly as secondary. I followed the steps to add the custom ROM but when I flash the zip file it says something like "error executing binary file /tmp/mr_update.zip" What I'm trying to do is not possible? Should I try another CM 12 nightly? Is there any other good custom rom based on lollipop and compatible with multiROM that you could recommend?
BTW, my device is a Nexus 7 2013 (flo)

problems with my 3 rom in nexus 7 2013
Hello and thanks for any help. + sorry for my bad english.
I have nexus 7 2013 with sim and i just install multirom and flashed the second rom without any problems. The first rom is the original 4.4.4 and the second is ubuntu touch. I download kali linux for nexus 7 2013 and flash it from TWRP as new rom. It has installed successfuly but i gut an error trying to boot to that rom. Im attaching picture with the screen when it got the error.
Can some one help plz?
Cheers

The Latest Multirom v30 Seems Unstable
Hi all, I 'm a Multirom user. since I found I can`t boot into AICP rom after it`s ota update, I backed up and erased everything. Then I downloaded google`s factory image and runned flash-all.bat file smoothly. After that, I did: boot system (seccess) and reboot into bootloader --> flash twrp_multirom_20150115.img --> install kernel_*_501.zip&&multirom_v30.zip --> add previous rom backups --> reboot system ,till now,everything seems OK . I can boot into any of the secondary roms.
Ａ．But Problems happened after I renamed the secondary roms in the recovery, like "bckp--DATE--AICP“ ->"AICP", "bckp--DATE--CM_Games" -> "CM_Games". It tends to boot into the PRIMARY ROM when I tap the First SECONDARY ROM ;when I tap other secondary roms , it stuck at Google Logo. If I give the Secondary ROMs long-names back , it can boot into the 1st secondary rom , stuck at Google Logo if I tap other Secondary rom I backed up before.
Ｂ．Besides, after I installed firefox_OS_1.3.zip,CM_20150125.zip,AICP_20150125.zip individually as secondary rom ,I failed booting into them. １.Firefox_OS:stuck at Google Logo,２.CM&&AICP:stopped at boot animation.(I am bored to and don`t try the "swap" option or rename)
Anyone who knows any temp solution(s) about those bugs?Should I upload the log file?
It seems that the short-name bug exits for a long time. Anyway , thanks for your multirom @Tasssadar !
Sorry for my bad English.

running X applications in Xmir in Ubuntu Touch
Finally I figured out a way to run X applications in Ubuntu Touch using clues from here:
www dot youtube dot com/watch?v=XfMLzlki9XE
www dot phoronix dot com/scan.php?page=news_item&px=Ubuntu-Unity-8-Pre-MWC-Demo
1. Install Ubuntu Touch Vivid Proposed via MultiROM
2. Increase the disk image size for Ubuntu
3. boot Ubuntu
4. enable developer mode
5. connect via adb
6. mount image writable
Code:
mount / -o rw,remount
touch /userdata/.writable_image # to keep rw after reboots
7. install Xmir
Code:
wget 'https://launchpad.net/~mlankhorst/+archive/ubuntu/ppa//+files/xserver-xorg-xmir_1.17.1-0ubuntu1%7Eppa1%2Bsa7_armhf.deb'
wget 'https://launchpad.net/~mlankhorst/+archive/ubuntu/ppa//+files/xserver-xorg-core_1.17.1-0ubuntu1~ppa1+sa7_armhf.deb'
wget 'https://launchpad.net/~mlankhorst/+archive/ubuntu/ppa//+files/xserver-common_1.17.1-0ubuntu1%7Eppa1%2Bsa7_all.deb'
dpkg --install *.deb
8. place a script like this in your home
Code:
#!/bin/bash
DISPLAY=:1
Xmir $DISPLAY
sleep 1
xeyes
9. make it executable
Code:
[email protected]:~$ chmod +x test.sh
10. place a file like this in ~/.local/share/applications/test.desktop
Code:
[Desktop Entry]
Name=Test
Type=Application
Terminal=false
Icon=/usr/lib/arm-linux-gnueabihf/qt5/qml/Ubuntu/Components/Themes/Ambiance/artwork/[email protected]
X-Ubuntu-Touch=true
Exec=/home/phablet/test.sh
11. pull down on the "Apps" home screen in Ubuntu Touch, now you should see the Test icon appear
12. launch Test and see xeyes appear
It seems to work with all applications I tried so far (xeyes, xterm, icewm, libreoffice-writer). A keyboard plugged in via USB OTG works ok, touch works, external mouse kinda works. The mouse cursor doesnt show, so that makes for awkward usage, also xeyes only seems to register the position upon click, not upon moving around.

OnePlus3 (A3003), problems with upgrading / installing Lineage 14.1 20170511

Phone: OnePlusThree (msm8996) / A3003
Bootloader: Unlocked
DM-Verity: "Fixed" (i.e. don't get any warnings anymore)
OS: Ubuntu 16.04 w. working adb/fastboot from Google's "platform-tools"
Lineage version: Lineage 14.1 20170511 Nightly
TWRP version: 3.1.0.0
Also tried with:
OnePlus recovery tool: recovery_op3.img
OxygenOS: OnePlus 3 OxygenOS Open Beta 15
Other packages:
Root: addonsu-arm64-signed.zip (170126)
OpenGAApps: Arm 64, 7.1, Pico (170514)
Hi!
Had a working installation of Lineage 14.1 with a build from late April and wanted to update to the latest version.
Made a nandroid backup via TWRP and backed up via Titanium Backup. However I have ran into massive problems trying to get Lineage to work again.
I won't take up a lot of space here (and I honestly dont remember all the steps) by going into detail what I have done but here is my current setup:
Flashed OnePlus recovery tool, made a complete wipe (apps and everything) and then used adb sideload to sideload the official latest Oxygen build (Open Beta 15).
It reports everything went OK and I reboot into system. I get to enter my PIN and the OnePlus setup starts, select a fresh install and it boots into the OS as normal.
Enable USB-debugging and then boot into flashboot to flash TWRP. The flash reports OK. I shut down the phone and then start it into recovery using "volume down + power".
TWRP boots successfully. I swipe to allow modifications to the "system"-partition and push Lineage, OpenGAApps and addonsu to /sdcard/.
Advanced wipe > System, data, cache. No errors.
Install > Queue the .zips after one another, first Lineage then OpenGAApps and then addonsu > swipe.
"Patching system image unconditionally" and then it stalls around 80% or so. I still see the "blue animation" so it seems to be working / processing but I've tried to leave it as it is for hours and nothing else happens. I remember when it used to work and then it never got stuck on any step but executed all the installations one after each other.
Have I missed anything or doing something wrong? Not an expert in flashing roms but its a really annoying issue, haven't been able (since I want to be able to use Lineage, stock Oxygen seems to work but need to be able to get root and restore my Titanium Backup) my phone for around a week.
Any help is appreciated, if you need any logs etc. then I'll be happy to upload them.
Best Regards - TheSwede86

TheSwede86 said:
Phone: OnePlusThree (msm8996) / A3003
Bootloader: Unlocked
DM-Verity: "Fixed" (i.e. don't get any warnings anymore)
OS: Ubuntu 16.04 w. working adb/fastboot from Google's "platform-tools"
Lineage version: Lineage 14.1 20170511 Nightly
TWRP version: 3.1.0.0
Also tried with:
OnePlus recovery tool: recovery_op3.img
OxygenOS: OnePlus 3 OxygenOS Open Beta 15
Other packages:
Root: addonsu-arm64-signed.zip (170126)
OpenGAApps: Arm 64, 7.1, Pico (170514)
Hi!
Had a working installation of Lineage 14.1 with a build from late April and wanted to update to the latest version.
Made a nandroid backup via TWRP and backed up via Titanium Backup. However I have ran into massive problems trying to get Lineage to work again.
I won't take up a lot of space here (and I honestly dont remember all the steps) by going into detail what I have done but here is my current setup:
Flashed OnePlus recovery tool, made a complete wipe (apps and everything) and then used adb sideload to sideload the official latest Oxygen build (Open Beta 15).
It reports everything went OK and I reboot into system. I get to enter my PIN and the OnePlus setup starts, select a fresh install and it boots into the OS as normal.
Enable USB-debugging and then boot into flashboot to flash TWRP. The flash reports OK. I shut down the phone and then start it into recovery using "volume down + power".
TWRP boots successfully. I swipe to allow modifications to the "system"-partition and push Lineage, OpenGAApps and addonsu to /sdcard/.
Advanced wipe > System, data, cache. No errors.
Install > Queue the .zips after one another, first Lineage then OpenGAApps and then addonsu > swipe.
"Patching system image unconditionally" and then it stalls around 80% or so. I still see the "blue animation" so it seems to be working / processing but I've tried to leave it as it is for hours and nothing else happens. I remember when it used to work and then it never got stuck on any step but executed all the installations one after each other.
Have I missed anything or doing something wrong? Not an expert in flashing roms but its a really annoying issue, haven't been able (since I want to be able to use Lineage, stock Oxygen seems to work but need to be able to get root and restore my Titanium Backup) my phone for around a week.
Any help is appreciated, if you need any logs etc. then I'll be happy to upload them.
Best Regards - TheSwede86
Click to expand...
Click to collapse
Someone had a similar problem where the flash stuck at about 50%, it turned out TWRP didn't have enough space to unpack the ROM but doesn't give any indication. How much space do you have available? Deleting some files to create more space fixed the issue.

IronRoo said:
Someone had a similar problem where the flash stuck at about 50%, it turned out TWRP didn't have enough space to unpack the ROM but doesn't give any indication. How much space do you have available? Deleting some files to create more space fixed the issue.
Click to expand...
Click to collapse
What I think is weird is that when I flashed the official OnePlus Recovery I did a complete wipe before sideloading their official rom and when booting into TWRP I did the usual "system+data+cache"-wipe.
So space shouldn't be an issue.
However when I rebooted into recovery I got "Failed to mount '/system' (Invalid argument)".
I copied the logs from TWRP and please see them attached here and as you say "/system" seems to be have no space whatsoever allocated?
Code:
/system | /dev/block/sde20 | [B]Size: 0MB Used: 0MB Free: 0MB Backup Size: 0MB[/B]
Flags: Can_Be_Mounted Can_Be_Wiped Can_Be_Backed_Up Wipe_Available_in_GUI IsPresent
Primary_Block_Device: /dev/block/sde20
Display_Name: System
Storage_Name: System
Backup_Path: /system
Backup_Name: system
Backup_Display_Name: System
Storage_Path: /system
Current_File_System: ext4
Fstab_File_System: ext4
Backup_Method: files
Edit:
Quite interesting, if I use OnePlus official recovery and sideload the latest official build and then flash TWRP I get this when extracting the logs:
Code:
/system | /dev/block/sde20 | [B]Size: 2868MB Used: 2507MB Free: 360MB Backup Size: 2507MB[/B]
Flags: Can_Be_Mounted Can_Be_Wiped Can_Be_Backed_Up Wipe_Available_in_GUI IsPresent
Primary_Block_Device: /dev/block/sde20
Display_Name: System
Storage_Name: System
Backup_Path: /system
Backup_Name: system
Backup_Display_Name: System
Storage_Path: /system
Current_File_System: ext4
Fstab_File_System: ext4
Backup_Method: files
Even if I go about doing Wipe > Advanced Wipe > System, Cache and Data and then dump the logs again I get the same results.
The same if I use "Use rm -rf instead of formatting". Now as a newbie in this I guess it does not successfully wipe my "/system" partition even though I don't get any errors and there are no error handling if there is insufficient space in TWRP so it just hangs indefinitely? How can I go about formatting "/system" so I can install Lineage and why come the stock Oxygen OS works (via adb sideload)?

Please help its a request.

Hi friends,
I lost imei on my moto g5 because I had installed oreo 8.1 rome on it.
while I was trying to fix the imei on its stock rom that I had flash after flashing oreo 8.1.
I thought dhob -> /dev/block/mmcblk0p20
and hob -> /dev/block/mmcblk0p19 are the two files that contain all the data of IMEI and network.
so I searched on web and foun these two files of some other moto device. I went ahead and flashed these two files onto my file. which actually didn't resolve the issue. but gave me some more issue. now after doing this fingerprint stoped working.
Then I went ahead and ran fastboot clear all command from the cmd in fast boot thinking that it might remove these two file that I have flashed. but by doing that I lost wifi as well.
now the situation is this that there is no imei on my moto g5, wifi is not working, finger print senser is not working.
so finally i relocked the boot loader and thought maybe I will take it to service center and they will fix it. but they found that it is out of warranty and asked for money which is 80% cost of the mobile phone. actually they are telling me to replace the mother board.
I know there should be someone on XDA who can actually help me. I understand I have messed it real bad. But I really need this phone.
so this is my final request to all XDA members and all DEV's out there please help me.
According to my knowledge I will need the back up of some files from a working moto G5 cedric, That I can flash to my moto g5 cedric:
here are the files that I need:
aboot -> /dev/block/mmcblk0p4
abootBackup -> /dev/block/mmcblk0p11
dhob -> /dev/block/mmcblk0p20
fsc -> /dev/block/mmcblk0p22
fsg -> /dev/block/mmcblk0p21
hob -> /dev/block/mmcblk0p19
misc -> /dev/block/mmcblk0p30
modem -> /dev/block/mmcblk0p1
modemst1 -> /dev/block/mmcblk0p17
modemst2 -> /dev/block/mmcblk0p18
persist -> /dev/block/mmcblk0p29
rpm -> /dev/block/mmcblk0p5
Here is the script to take the back up:
This one is for about. please make the changes accordingly to take the backup for others:
adb shell su -c "dd if=/dev/block/mmcblk0p4 of=/sdcard/mmcblk0p4.img"
you will have to use this script on fastboot in cmd. while your phone is turned on and first you will have to give fastboot root access.
Again This is a request someone please please please help.....:crying::crying::crying:
If you need any help in taking backup please reply I will surely help with that.
Requirements:
- Device has to be rooted, with USB debugging enabled.
- Motorola fastboot (see attachment).
- ADB installed, minimal or the full ADK.
You can search the forum to find how to meet these requirements or for the terms described in this post beginning here:
http://forum.xda-developers.com/show....php?t=2558638

Weirdly when I backed up the /dev/mmcblk0p29 persist partition it was 8MB, meanwhile when I backed up the /dev/block/bootdevice/by-name/persist it was 32MB