yashsingh1/xdaforums huggingface dataset:
[Galaxy S 4 i9505 Original Android Development] afaword:
please give me a solution, why can not boot in the rom 2, I've been following the way here but it does not work, I Xiami device redmi note 3 pro:crying:
[Galaxy S 4 i9505 Original Android Development] 911-Future_Maker:
No. First it's highly unusual to have that big system.img image. I have two phones and the size is 2.5GB on the one and 1.8GB on the other. Let's say your system.img is 2.5GB then you only have to ensure you have the available free space on the extsd only. You don't need that free space on internal also. I was unclear in my previous post, it's not actually decompressing the system.img, the files in /raw/images/extsd-slot-xx are showing the actual system folder and it's size for the corresponding rom in /extsd/Multiboot/extsd-slot-xx. It's also on the extsd and don't need additional space. Usually the actual size of the system folder is from 700MB to 2GB more or less. So, nobody can say how much will be the size of the system.img on your phone, but in our example if it's 2.5GB like mine and you have 2.6GB free on the extsd you're good to go. The only space you need on internal is for the /data partition of the extsd roms. In my experience the average size a extsd-slot rom needs on internal is from 450MB to 1.2GB. Having in mind that the less than 350MB free space on internal triggers the "storage space running out" warning you'll need ~700MB-1.55GB free on internal. Of course these numbers may vary depending on the rom. So the minimal space requirements for extsd-slot rom with a 2.5GB system image are:

-2.6GB on extsd

-700MB-1.55GB on internal

Running a rom from an extsd-slot is extremely useful saving space on your phone. If you install the same rom to internal assuming the real size of the system is 1.5GB you'll need around 2.2GB-3.05GB free on internal.
[Galaxy S 4 i9505 Original Android Development] Eleo:
Yesterday I had only a primary TW ROM. Then I installed dualboot and flashed two more TW ROMs into extsd slot 1 and 2 but didnt boot to them. Returned to primary TW ROM, and I had ~10GB free space in sdcard (in extsd card I had 30GB free space). Then I booted into extsd slot 1 and observed that I have only 4GB free space in extsd and ~10GB of "system data" that cannot be emptied or moved (checked by using diskusage app). I thought maybe if I boot back to primary ROM, that "system data" would shrink to 2-3GB again, but it was still.same 10GB. Then I booted into slot 2 of extsd (last TW ROM) and I couldnt backup my user apps because I only had 300MB free space in sdcard and "system data" now expanded to 20GB.

Then I backed up primary ROM to extsd card from dual boot app and wiped it. Then I had only 10GB "system data". And then out of curiosity I backed up slot 1 extsd ROM to extsd card and wiped it too. Now I got 1.4GB "system data" only. Is it possible in any case that even if the ROMs were placed into extsd ROMs in multiboot they take 10GB of data per each of them? Because I thought that the files would be stored in extsd card (and I still have ~10GB free space available there) and didnt think it will take that much space in sdcard.

I am sorry for reposting same post in 1 day but I really want to get to know the principle to be able to use it. Because this way it makes impossible to use more than 2 TW ROMs in a device with only 32GB sdcard even though extsd has plenty of free space.
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Can you post the full log? Looks like it's expecting /cache to be already mounted instead of mounting /cache itself.
[Galaxy S 4 i9505 Original Android Development] Mike0505:
[MENTION=4277844]chenxiaolong[/MENTION]

After removed file sugessted by [MENTION=7311728]asterix14[/MENTION] flashing miui 6.11.24 works from in app flashing , :)

after that also tryed Resurection remix from http://xdaforums.com/mi-max/development/rom-resurrection-remix-t3507372 ,also works from in app flashing :)

switching rom works, patching kernel works, :D

Thanks a lot [MENTION=4277844]chenxiaolong[/MENTION], thanks [MENTION=7311728]asterix14[/MENTION]

log attached
[Galaxy S 4 i9505 Original Android Development] rifle007:
This line in updater-script MIUI

Log and miui_update file attached
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Sorry to have you keep flashing things over and over. Can you try again with the latest build (9.1.0.r0.g6e3c82c) from https://dbp.noobdev.io and grab the logs when it autoreboots using the latest GetLogs zip (20161128-1)?

I found a bug that prevents the kernel log from being saved properly and the new versions mentioned above should fix that.
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
When you're booted to Android or recovery, are you able to manually mount /firmware?

mkdir -p /firmware
mount -t ext4 /dev/block/bootdevice/by-name/modem /firmware

If that doesn't work, what about after a repair of the modem partition?

e2fsck /dev/block/bootdevice/by-name/modem

I really can't think of anything else that might cause the problem.
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Could you also try what I mentioned in my post here? http://xdaforums.com/showpost.php?p=69840853&postcount=10446

There was a bug that prevented the kernel log from being saved in older versions.
[Galaxy S 4 i9505 Original Android Development] DIXES:
Does phh's hidesu still pass SafetyNet on dualbooted rom? I would like to try it. Thanks.
[Galaxy S 4 i9505 Original Android Development] gc_geforce:
No worries, I will try this and see what happens and forward the logs.:good:

chenxiaolong, How do I get the log from the patcher as it was able to patch the rom zip file but failed trying to flash it with 9.1.0.r0.g6e3c82c, when it was verifying it gave an error -1

This is GREAT! so I could not install the zip file via the patcher APP 9.1.0.r0.g6e3c82c, BUT I rebooted into recovery and tried flashing the new patched zip in TWRP and reboot, and it worked!!! it is booting into the newly installed ROM from EXTSD on my G900W8 S5. I am not sure what is wrong why it errors out trying to verify the zip in the patcher app. Also I noticed that when in the TW ROM from EXTSD it thinks the I have a corrupted SD Card. is this because the ROM is booted from the SD CARD?
[Galaxy S 4 i9505 Original Android Development] ewangw:
[MENTION=4277844]chenxiaolong[/MENTION],

First off, thanks for all your help in troubleshooting this issue.

I ran the commands in term. emulator and in TWRP and I got a message that the device or resource is busy in each case. When I loaded AICP 12.1, I had to sideload it as my main ROM, but /firmware did fail at first until I wiped my cache. Once I wiped cache it loaded, including /firmware, with no problem. Not sure why that works.

Currently, I have AICP12.1 in primary and CM14.1 and CypherOS sitting in my data slot. To get the SIM working, I just copied my firmware folder from AICP to the other Nougat ROMS and that seems to do it. I'm cool with this workaround until something can be figured out.
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Thanks for the logs! Can you give this test build a try and see if it resolves the issue? https://github.com/chenxiaolong/DualBootPatcher/pull/315
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Great! Glad you got it working! Can you post a screenshot of where you're seeing "error -1"?

The external SD showing as corrupted is caused by tripping a security feature in the TW kernels. It only happens when booting from an extsd-slot. At the moment, the only way to fix that is to use a custom kernel that has the security feature disabled.
[Galaxy S 4 i9505 Original Android Development] rifle007:
In this test build the problem still exist ApplyParsedPerms: removexattr of /cache/miui_update to 0 failed: Operation not supported on transport endpointscript aborted: set_metadata: some changes failed
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Can you post the MultiBoot.log file?
[Galaxy S 4 i9505 Original Android Development] rifle007:
Of course
[Galaxy S 4 i9505 Original Android Development] gc_geforce:
I will change the kernel, easy fix, here is the screen shot it did not say error - 1 this time
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Thanks for the logs! Sorry, I made a super dumb typo in the code and made it unmount /cache instead of mounting it. There's a new test build available at: https://github.com/chenxiaolong/DualBootPatcher/pull/315
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Since you have it working, it's not really a rush, but when you have some time, would you mind updating the app to 9.1.0.r13.g3d9b503 and trying again? You don't have to repatch or flash anything. Just add a zip to the in-app flasher so the verify zip process runs. It will create a new log file at /sdcard/MultiBoot/logs/verify-zip.log. Thanks!
[Galaxy S 4 i9505 Original Android Development] gc_geforce:
I can do this tonight for you!
[Galaxy S 4 i9505 Original Android Development] rifle007:
Still same and when i added mount option in updater-script MIUI it can flash with succesfully

sorry i use the patched zip from old app, now its work
[Galaxy S 4 i9505 Original Android Development] gc_geforce:
Here is the log for you, and 9.1.0.r13.g3d9b503 did the same as my first screenshot of when the verify fails.
[Galaxy S 4 i9505 Original Android Development] nicesoni_ash:
My phone doesn't go back to recovery but shuts off completely so here is the log with new getlogs zip and the rom was flashed using latest version.
[Galaxy S 4 i9505 Original Android Development] gc_geforce:
I tried to update my kernel in the extsd rom I have installed with a patched kernel zip. But it failed . screenshot attached
[Galaxy S 4 i9505 Original Android Development] Mike0505:
This build not work. At app startup on roms getting message : this device codename helium is not recognized :confused: , so switched back to this : https://github.com/chenxiaolong/DualBootPatcher/pull/309

Thank You !
[Galaxy S 4 i9505 Original Android Development] 911-Future_Maker:
9.1.0 builds are live, hell yeah. :p Thanks [MENTION=4277844]chenxiaolong[/MENTION].

---------- Post added at 09:14 ---------- Previous post was at 09:09 ----------

Every time I see this error I'm in-app flashing. When trying the zip in recovery it flashed successfully. Not really a problem of the patcher, but it's more like rom dependable issue.
[Galaxy S 4 i9505 Original Android Development] rifle007:
With build 9.1.0 r11 i can flash MIUI succesfully, i tried two MIUI rom and no problem. Thanks [MENTION=4277844]chenxiaolong[/MENTION] i think its fixed.. ?
[Galaxy S 4 i9505 Original Android Development] 911-Future_Maker:
[MENTION=4598795]Eleo[/MENTION] Strange storage issue, seems related to TW ROMs. Chen is working hard fixing the things up for the new TW 7.0. Can you look what's going on in the /raw dir? Find the path for the /system and /data partitions for both extsd roms and report their size. They are located in:

/raw/images/extsd-slot-xx
/raw/data/multiboot/extsd-slot-xx

Could you also tell me the size of the system.img images in /extsd/Multiboot/extsd-slot-xx?
[Galaxy S 4 i9505 Original Android Development] Eleo:
Ok. I wiped the primary and extsd slot 1 to save up some space in sdcard. Right now I only have extsd slot 2 active and only 2.5GB is used by system data. Will try backing up present ROM, then restore the previous s7edge port from recovery then will try installing dualboot and restoring dualboot backup from external sd to have primary and extsd slot. And will boot to extsd slot ROM to know how much space I have filled with system data and also look at the directories you pointed out.

Thanks
[Galaxy S 4 i9505 Original Android Development] tomaasz:
Hi,

Thanks for great tool

Could you check in my log why after I "set kernel" (with info "Successfully set the kernel") again and again I revive tip "The kernel has not yet been set for the current ROM. Would you like to set the kernel now?" ?

And after using "Update ramdisk" I always receive communicate "Failed to update ramdisk" ?

My device is S5 SM-G900F klte

TWRP 3.0.2-0

Rom: TW 6.0.1 DarkLord N7 V 4.5 by [MENTION=247572]ufo[/MENTION] (I've added line ro.patcher.device=klte)

with [KERNEL] [SM-G900F] [Samsung Stock M/LP] Boeffla-Kernel v	2.4

?
[Galaxy S 4 i9505 Original Android Development] Eleo:
Right now with only extsd slot 2 ROM in my phone I have 2.25GB in /extsd/Multiboot/extsd-slot-2. Other slots are empty folders since I wiped them. The zip file of ROM is 1.5GB. I will try one more ROM in extsd slot 1 and report back
[Galaxy S 4 i9505 Original Android Development] Yumiko87:
I have question. I already backup the system data cache boot image for my data slot 2 but when I go back my primary rom after wipe there is no option to restore it. How is he the problem?

Whats wrong with it?
[Galaxy S 4 i9505 Original Android Development] kopitalk:
You should ask what's wrong with you. Or am I hallucinating?
[Galaxy S 4 i9505 Original Android Development] majee12:
Does it work on note 4?

---------- Post added at 04:43 PM ---------- Previous post was at 04:34 PM ----------

Am new here, and when try flashing the utility zip or patching the rom zip I downloaded. The app actually opens the zip file when I tap on the zip. OK I got it guys sorry for the haste post.
[Galaxy S 4 i9505 Original Android Development] Eleo:
Ok. I flashed another TW ROM into extsd slot 1. Now I have extsd slot 1 and 2 and no other ROM installed. I have booted to extsd slot 1 so that it is too active.

When I had only one ROM in extsd I had ~2.5GB space filled with system data, but now it is 11.4GB again (attachment 1).

You can see all the mentioned folders in attachmets

I checked the system.img files in extsd, they are 2.3GB each. But this space of extra 9GB in sdcard is driving me crazy. I havent yet installed my user apps, that is why I have 9GB free space available. Once they are installed the free space will decrease to 3-4GB. One thing I dont understand, if these data are stored in sdcard already that make up that much space, the only difference between selecting data vs extsd slots is the system image files that are only 2.3GB?

Last screenshot is the sdcard disk usage from the other ROM (extsd slot 2 ROM)

Thanks in advance.

P.S. When I installed the extsd slot 1 ROM+kernel+addons in recovery, before rebooting to system from recovery right after shifting to extsd slot 1 from dualboot utilities zip, there was a message in recovery window saying:

"Error there is no space to write recovery log

Error there is no splace to write last recovery log" maybe not same as this but smth like that...
[Galaxy S 4 i9505 Original Android Development] majee12:
this is how it end nothing happened anymore. Probably my primary rom isn't helping. Will try it later and try to see where the problem is from.
[Galaxy S 4 i9505 Original Android Development] 911-Future_Maker:
So you mean the patcher is hanging at that stage? The shot is showing the rom is being installed. You should wait. Anyway the picture itself is not much of help, if it hangs you should provide a log.
[Galaxy S 4 i9505 Original Android Development] 911-Future_Maker:
[MENTION=4598795]Eleo[/MENTION] Ok, thanks for the screenshots! I see no problem in /extsd/Multiboot. The thing is you have more than 5GB in extsd-slot-2 used by apps and probably around 2GB for the dalvik cache folder, seems too much to me! :D You must have very long list of apps on that rom. All this space is on internal, only the system is on extsd. That's why when you boot the extsd-slot-1 rom also you're running out of space. 2 roms and no space left,... bro here I have 8 roms, 6 of which are on extsd-slot. I have 1.5GB free on internal which is only 16GB. Around 4.3GB data for apps and their apks moved on the 2nd ext4 partition of my extsd with the Apps2sd. That's why I keep using this app otherwise I won't be able to have so much roms installed.

These TW roms are heavy.
[Galaxy S 4 i9505 Original Android Development] Eleo:
Well, I have ~160 user apps and none of them are in microsd. And I was planning to do the same in extsd-slot-1. But it would be the same it seems. I have sandisk extreme 64GB microsd (I bought that because it was one of the fastest when I was buying). Would it be enough to run some apps (at least the apps that I seldom use, not the ones that I frequently use)? I store all the music and movies in my microsd and they run with no problem in apps. I cleaned all the recocery backups + dual boot backups from microsd (21GB) and have plenty of space there. So if I move some apps (apks) by app2sd (I dont know anything about ex4 partition but I will read about it) I would have more space in sdcard right?
[Galaxy S 4 i9505 Original Android Development] Eleo:
I get this error in app2sd. I should change the file system right? And while changing file system it will wipe everything in external... Do you have suggestion for that? Which file system do you use? [MENTION=5048731]911-Future_Maker[/MENTION] I formatted the external sd from app2sd but forgot that both my roms are there:o. So I flashed a new rom from recovery as default (primary) and will try to check the app2sd soon.
[Galaxy S 4 i9505 Original Android Development] Tmobilefan906:
I had same issue with tw too. But I found a way. I installed a tw rom as my primary, and added RR and tems rom in slot 1 and 2. Works fine. Occasionally on normal reboot of tw rom, it will hang...I just restore a back up.

---------- Post added at 08:45 PM ---------- Previous post was at 08:42 PM ----------

That looks promising. Maybe I can flash a tw rom as primary, then do a data slot then rest ext...have u had any hangs on reboots?
[Galaxy S 4 i9505 Original Android Development] MisiekDP:
Do you use a last version of DualBoot Patcher?
[Galaxy S 4 i9505 Original Android Development] kopitalk:
Just to report another success story of backing up a rom (which is a TW 6.0) in data-slot and restoring it as primary :good:

http://xdaforums.com/galaxy-note-3/themes-apps/guide-dual-boot-note-3-t3091764/post69851323
[Galaxy S 4 i9505 Original Android Development] Tmobilefan906:
Both versions do it
[Galaxy S 4 i9505 Original Android Development] MisiekDP:
Try with the newest version and attach logs (if you will have a problem).
[Galaxy S 4 i9505 Original Android Development] Tmobilefan906:
The newer version doesn't work good for me.
[Galaxy S 4 i9505 Original Android Development] kopitalk:
Then none will.
[Galaxy S 4 i9505 Original Android Development] Tmobilefan906:
Maybe 8.0 will. I didn't say it didn't work...it just sometimes loops on reboot when im on a data slot.
[Galaxy S 4 i9505 Original Android Development] MisiekDP:
So install the newest version, try to boot ROM and attach logs from booting. We need to check where is the problem.
[Galaxy S 4 i9505 Original Android Development] whymoo:
Please add support for LeEco (LeTV) Le Max 2.
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Thanks! I'm able to reproduce the issue now. I'll look into it.
[Galaxy S 4 i9505 Original Android Development] gc_geforce:
That is great! Thanks, this patcher had come along way, I used this on my S4 a year ago, and now I see how many devices is supported including my s5.
[Galaxy S 4 i9505 Original Android Development] shadowcliffs:
Never mind
[Galaxy S 4 i9505 Original Android Development] Yumiko87:
9.0 beta test version seems to be good. Just have some search on it you will know which one it suitable for you.

---------- Post added at 05:30 AM ---------- Previous post was at 05:27 AM ----------

If you are in trouble do in some case:

Try this version:
[Galaxy S 4 i9505 Original Android Development] 911-Future_Maker:
For sure, any good class 10 card is fine. Apps2SD is the successor of Link2SD. Basically creates a symlink between the /data/app/-xx, data/data/-xx and so on and moves the data, even moves the obb for any app you wish. You can move the dalvik cache too, but I don't recommend that, because it's slowing down the phone by a huge margin. I must tell you that your boot time will become slightly longer, because even being a fast extsd it's still slower than the internal storage.

---------- Post added at 11:10 ---------- Previous post was at 11:06 ----------

Well this is not exactly an error, it just warns you if you wish to use the FolderMount option you'll have problems. :D This is different than linking the apps apjs and their data to extsd. I'm using ext4 FS. I created the partition on PC, but formatting via the app itself should work fine.
[Galaxy S 4 i9505 Original Android Development] Eleo:
Actually right after changing the file system, the phone rebooted and bootlooped by vibrating 5 times before each boot (it didn't show samsung logo). So I assumed that it somehow changed/damaged the dualboot files or system images. I flashed n7 port to primary and will flash an s7edge port to extsd. Will try to do same as yours to save space (I will at most have 3 ROMs though :D).

Thanks for your kind helps :good:
[Galaxy S 4 i9505 Original Android Development] 911-Future_Maker:
Wait, are you sure you formatted the 2nd partition in ext4? Well the FS doesn't really matter, it failed to boot probably because you wiped the rom itself as you said. Or it refused to boot after you flashed the primary? Force update the ramdisk for the rom and make sure you're creating the mount script in Apps2SD choosing the right FS. Thankfully to be incredible debugging skills of [MENTION=4277844]chenxiaolong[/MENTION] and me reporting issues and logs currently most of the bugs using a multi partitioned extsd were fixed.
[Galaxy S 4 i9505 Original Android Development] Eleo:
I wiped primary long time ago. I had only extsd slot 2. Then I flashed extsd slot 1 to show the used space by system data. And then I changed FS of extsd by add2sd app.

It seems that I didnt get that 2nd partition part. Should I do some steps before openning app2sd?

Right now I have only primary and will add extad slots as soon as I understand how to move app files to extsd
[Galaxy S 4 i9505 Original Android Development] 911-Future_Maker:
Hi, I'm not sure you're asking me. :D I think you were talking to [MENTION=4598795]Eleo[/MENTION]. I don't have any problems with my current multiboot setup. Be careful running multiple TW ROMs, from what I'm seeing they love eating the storage of your phone. :p

---------- Post added at 11:34 ---------- Previous post was at 11:30 ----------

To clear the things out, now you have 2 partitions on your extsd? ext4 and fat32 or exfat may be? Really I don't trust the app formatting my card, do it in PC if you can. Assuming you have a single partition, you must create new Primary ext4 partiton with a size you like. I did that using Minitool Partition Wizard, Paragon also works.

---------- Post added at 11:45 ---------- Previous post was at 11:34 ----------

Yes, I know that feeling. Really this is my favorite app on my phone. I think I can't live without it. lol Someone help me! :D

---------- Post added at 12:00 ---------- Previous post was at 11:45 ----------

[MENTION=4277844]chenxiaolong[/MENTION] Is it supposed I'm able to flash ota updates containing a patch boot.img.p file or it's just failing on me? It installs fine, but no changes to the system.
[Galaxy S 4 i9505 Original Android Development] Eleo:
Now I have only primary TW ROM. Because after changing FS it couldnt boot to any extsd dual boot ROMs, I just flashed a ROM by old way using recovery (which is my primary ROM right now). I'm looking at those PC apps right now, will try to create a new ext4 partition on my micosd.
[Galaxy S 4 i9505 Original Android Development] 911-Future_Maker:
Still can't believe that two TW roms will fill 32gb internal storage.:silly:

But the facts are talking by itself, well you also have many user apps.