yashsingh1/xdaforums huggingface dataset:
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
That has exactly the info I need. Thanks! The main issue is this: the ROM expects the partition files to be in:

/dev/block/platform/mtk-msdc.0/by-name/

but for some reason, my hardware detection code is creating them in:

/dev/block/platform/mtk-msdc.0/11230000.MSDC0/by-name/

Hopefully, that'll be an easy fix :) I'll take a look after work.

Unfortunately, yes.

The boot.img file has many pieces, but the two main parts of it are the kernel and the ramdisk. The ramdisk contains the programs and files that are needed to begin booting Android (or any other Linux OS). If you look at the root directory /, all the files beginning with "init" and also the "sbin" folder are part of the ramdisk. It usually looks something like this: https://dl.dropboxusercontent.com/u/486665/Screenshot from 2015-12-18 07-49-41.png

When you first turn on the phone and the kernel starts loading, the first thing it will do is run the /init program. init detects all the hardware, mounts all the partitions, and then loads the /init.*.rc files (at this point, the boot animation shows up). Patching a file causes this init program to be replaced with my "mbtool" program. mbtool handles the first two tasks of detecting the hardware and mounting the partitions for multiboot. mbtool then runs the original /init program to complete the boot process.

The "Update Ramdisk" function really means "update mbtool from inside the ramdisk to the latest version". In the case of the primary ROM where mbtool does not exist, it gets added into the ramdisk, just like what happens when you patch a file.
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Downloading now, will take a look at it after work :D
[Galaxy S 4 i9505 Original Android Development] TheDarkKnight:
Thank you so much [emoji4] [emoji5]
[Galaxy S 4 i9505 Original Android Development] AL_IRAQI:
[MENTION=4277844]chenxiaolong[/MENTION]

Hi, is it possible to add Zenfone 2 support ?

log files attached

if you want other info's or files i can provide it :)

Thanks :)
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
For the issue where the ramdisk update doesn't work, you can blame Google ;) My hardware detection code is based on Android's and Marshmallow changed the way that it works: https://android.googlesource.com/platform/system/core/+/1225a61^!/ If your primary ROM was running Android 6.0, it would work lol. I've compiled a new debug build here: https://snapshots.noobdev.io/misc/XDA/Salman A./Post8077/Android_GUI-debug.apk. Could you uninstall the old debug version (important!), install the new one, and try again? Let's hope it works! But if it doesn't, please use GetLogs when it autoreboots to recovery like before.

As for the Lenovo source code, they surprisingly open-sourced many things, but nothing related to our /proc/dumchar_info issue. :( Lets focus on fixing the ramdisk update issue first since will affect other ROMs too. Then we can come back to fix this. Otherwise, I get confused with too many things...
[Galaxy S 4 i9505 Original Android Development] RWOLUPO:
is there any chance to add nexus 5x?
[Galaxy S 4 i9505 Original Android Development] TheDarkKnight:
Thank you so much!!

It flawlessly this time!!

I've updated the ramdisk of both primary and the other ROM, and it works! Hurrah!

Thank you so much again. [emoji4] [emoji5]

I'm not vulnerable anymore, right?

That's disappointing. [emoji17] As you wish.. You are the dev [emoji2] It isn't entirely useless, is it?

I'll try installing another system.new.dat ROM and see its the problem this particular ROM.

EDIT: Just tried. No luck ? Same error.. Attaching recovery log though don't think that will help.

Also, one more thing. When I installed this ROM to extsd-slot 1, it's showing the name and image of my previous ROM (Androium) that was in that slot.. I used DualBootUtilities.zip to wipe it, and it didn't remove many things, so I deleted them manually.. Does this mean that the residual files of that ROM is still there?
[Galaxy S 4 i9505 Original Android Development] pvsgh:
Thanks Chen :)

Don't think it matters a lot, but there is small typo in the code:

// Samsung Galaxy Note 2

device = new Device();

device->setId("t0lte");

device->setCodenames({ "t0lte", "t0lteatt", "t0ltecan", "t0ltelgt",

/* "t0ltespr", */ "t0ltetmo", /* t0lteusc, */

"t0ltevzw" });

device->setName("Samsung Galaxy Note 3");

device->setBlockDevBaseDirs({ DWMMC_BASE_DIR });

device->setSystemBlockDevs({ DWMMC_SYSTEM, "/dev/block/mmcblk0p13" });

device->setCacheBlockDevs({ DWMMC_CACHE, "/dev/block/mmcblk0p12" });

device->setDataBlockDevs({ DWMMC_USERDATA, "/dev/block/mmcblk0p16" });

device->setBootBlockDevs({ DWMMC_BOOT, "/dev/block/mmcblk0p8" });

device->setRecoveryBlockDevs({ DWMMC_RECOVERY, "/dev/block/mmcblk0p9" });

device->setExtraBlockDevs({ DWMMC_RADIO });

devices.push_back(device);
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Thanks for both of the logs! It's does seem like the exact same issue I ran into on my S4 before. Try flashing this zip file (without patching): https://snapshots.noobdev.io/misc/selinux/internal_storage_set_media_data_file.zip It should set the files' SELinux types to one that your primary ROM likes. Your Lollipop ROM should hopefully have no trouble with it also.

(By the way, I think you might have reversed the names of the two log archives ;))
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Whoops, sorry about that! Fixed in 8.0.0.r2023.ge7dee09 :)
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
It sounds like it might not have flashed correctly. When you install a new ROM, it should already be switched to that ROM, so it's weird that it always boots to primary. Could you try flashing the patched ROM from recovery?

By the way, I saw in the logs that you tried to patch DualBootUtilities. That file should not be patched.
[Galaxy S 4 i9505 Original Android Development] pvsgh:
Looks like builds are failing in Jenkins.
[Galaxy S 4 i9505 Original Android Development] fmotta:
Yes it's flashed not correctly, confirmed.

Nothing changes installing from recovery. Always booting primary.

I didn't patch anything at all!!! I wouldn't even know how to do it!

Thanks for your help.
[Galaxy S 4 i9505 Original Android Development] karkasss:
Flashing your script then booted to Kitkat sub rom but no luck.

Internal memory on kitkat rom is still not mounted.

Or do I wipe and re-install kitkat rom after flashing your script?

I want to say that No access of internal memory means no mounted of internal memory.
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Done :) 8.0.0.r2024.g5d803fc
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Does the Nexus 5X have boot images/kernels with encryption disabled (not just the default setting of no password)? If so, please flash the GetLogs zip from https://snapshots.noobdev.io/ and send me the log file it creates in /sdcard/logs/. Thanks!
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
I took down my main server to upgrade to a 1TB drive and it looks like my second server is having some issues lol. I think I fixed it now, so let's see if the rebuild works :)
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
No, you don't need to reflash your KitKat ROM. I don't think that would make a difference. Are you familiar with using adb or the Terminal Emulator app (https://play.google.com/store/apps/details?id=jackpal.androidterm&hl=en)? Could you run the following command and paste the output here (or take a screenshot):

su -c 'ls -Zd /data/media/0'

Thanks!
[Galaxy S 4 i9505 Original Android Development] karkasss:
I can. Can I do this on Kitkat rom?
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Sure, you can do it from any ROM (or even from recovery).
[Galaxy S 4 i9505 Original Android Development] TheDarkKnight:
[MENTION=4277844]chenxiaolong[/MENTION] No more hopes on my issue? ?
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
That's right! As long as you're using the new build, you should be fine :)

It's not completely useless..., but it's not very useful for us either. I suspect ROM developers might find it useful as Lenovo published their changes and optimizations to things like bionic.

Hmm, the name an images are stored in /sdcard/MultiBoot/extsd-slot-1, so maybe those didn't get deleted. I recommend wiping from the app if possible because the AROMA DualBootUtilities doesn't work on any of my devices, so I have no way of testing it :)

I'm not giving up yet! I hate leaving issues unsolved lol. I'm just stumped right now, I have no idea what else I can try.
[Galaxy S 4 i9505 Original Android Development] AL_IRAQI:
Awesome, That was fast ?

I can't find my device in the list and the app couldn't get ROM info

Sent from my ZF²
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Oops, stupid mistake on my part! Should be fixed in 8.0.0.r2025.gbafb7c0 :)
[Galaxy S 4 i9505 Original Android Development] AL_IRAQI:
its okay buddy, z00a now available in the list but i still get error "Could not connet to mbtool"

i have to edit ramdisk manually ?
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Hmm, is root access enabled for the app? If so, could you send me the /sdcard/MultiBoot/daemon.log file? (If that file doesn't exist, we may have to do a logcat)
[Galaxy S 4 i9505 Original Android Development] AL_IRAQI:
yes its enabled, check attachments

i also included MultiBoot.log because i tried to flash cm13 from recovery and i got error

Edit:

cm updater-script & update-binary also attached

Edit 2:

i fixed recovery error by removing system verification lines for the script
[Galaxy S 4 i9505 Original Android Development] karkasss:
Output is attached.
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
To everyone:

I have removed 8.0.0.r2025.gbafb7c0 and 8.0.0.r2024.g5d803fc from my server. Please do

not

use these builds as they were compiled by my second server, which has a different signing key. If you already updated and can no longer switch ROMs, please downgrade to 8.0.0.r2020.gc298a0b. I will rebuild the latest version once my main server is back online tomorrow.

EDIT: Server is back online. 8.0.0.r2026.g301d2d0 and up are good.
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Thanks for the logs! The mbtool issue is caused by the issue in my previous post (which will be fixed tomorrow). Regarding the flashing issue, could you send me a like (EDIT: I meant link lol) to the CM13 ROM?
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Thanks! I'm confused as to why this isn't working. Can you also send me the boot.img files in /sdcard/MultiBoot for the two ROMs?

With a root file manager, are you able to see your files in /data/media/0? What about /sdcard?
[Galaxy S 4 i9505 Original Android Development] AL_IRAQI:
Thanks, ill wait for it :)

here you are cm13

i attached updater-script & update-binary from Stock ROM and Custom ROM based on stock
[Galaxy S 4 i9505 Original Android Development] karkasss:
Yes There are no problem both sdcards except last rom(named S5rom).

https://mega.nz/#!VgUxyKaB!yJAMjbcuseA6Md6mKDVc-UteyqVTPD7jfXRLkmAPqFQ
[Galaxy S 4 i9505 Original Android Development] fmotta:
Dear Chen since I am a stubborn kind of fella and I don't like not to be able to solve problems... I restarted from scratch my Zuk Z1. Unfortunately with no success.

I try to list what I found till now.

- primary rom CyanogenOs 5.1.1

- doubleboot version 2020

- tried to patch five different roms apparently with no problems

- when I try to flash the patched roms some of them clearly seems not to install (I always use data slot) and in data/multiboot/slot/system there is nothing

- a couple of patched roms install and in their respective dir system is present

- nevertheless after flashing from inside doubleboot when I go back to rom panel I got a spinning circle continuously and I have to quit the program.

- after relaunching it I only have primary rom

- if I reboot the phone and relaunch doubleboot I found also the data slot rom but if I try to switch to it the program says it cannot switch

- also updated ramdisk on primary with no effect

- flashing the patched roms from recovery has no different effect

-also installing dualboot utilities from recovery has no effect : it do not start at all

I got a new log and here it is.

Let me know if I have to try something different. I am an Apple and Microsoft beta tester and I suffer when I cannot help to fix problems!
[Galaxy S 4 i9505 Original Android Development] tomaasz:
hi [MENTION=4277844]chenxiaolong[/MENTION]

again thank you for your great patcher!

I can't find file: https://snapshots.noobdev.io/DualBootUtilities-8.0.0.r2025.gbafb7c0.zip
[Galaxy S 4 i9505 Original Android Development] sronweb:
Please, just read few posts above. http://xdaforums.com/showpost.php?p=64387068&postcount=8103
[Galaxy S 4 i9505 Original Android Development] whitenoyz:
Not able to flash any rom, can anyone help please? Screen shot attached

Enviado desde mi ONE A2003 mediante Tapatalk
[Galaxy S 4 i9505 Original Android Development] corncobman:
Read the message at the bottom. It says it was flashed successfully...
[Galaxy S 4 i9505 Original Android Development] fmotta:
It's the same problem I have. It SEEMS flashed successfully!
[Galaxy S 4 i9505 Original Android Development] yilun:
Hey xiaolong, mine says that ramdisk is not up to date, I'm on resurrection remix 5.5.9 ?
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
This should hopefully be fixed in 8.0.0.r2026.g301d2d0 :)
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
The story of my life haha. I'd rather skip sleeping than leave something unfixed or unfinished :)

The ROM's you were using (as least based on the logs) don't have very good installers. They were silently failing, but did not return an error code so they appeared to be flashed. 8.0.0.r2027.gfbc9b0c should fix the issue that was causing the failure.

The next time you run into the issue with the spinner circle, could you try quitting and opening the app again and then send me /sdcard/MultiBoot/daemon.log? (Without rebooting because the log gets overwritten)

Yeah, the AROMA installer (which DualBootUtilities uses) doesn't seem to work on newer devices. It hasn't seen any development since February of this year (https://github.com/amarullz/AROMA-Installer/commits/master). It doesn't work on any of my new devices either. Unfortunately, there's not much I can do about that. One needs to have a very deep understanding of framebuffers and graphics drivers to work on the AROMA code.
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Can you post the /sdcard/MultiBoot.log file here? Thanks!
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
The ramdisk update option is in the new ROM details screen :) If you update the ramdisk, it is equivalent to patching and flashing your current ROM with the latest version of the app.
[Galaxy S 4 i9505 Original Android Development] whitenoyz:
Thank you!!! I just wiped my phone again and installed everything, but the app won't work, when going to ROMS section demands root, I grant access and then says that could not connect to dbtool... I keep having the same problem all the time :(

Thanks so much for the app and if you can help me I would truly appreciate :D
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
I'm really not sure what else I can try for S5rom. I'm not seeing any other errors in the logs that could be related to this issue.
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Can you send me the /sdcard/MultiBoot/daemon.log file? Thanks!
[Galaxy S 4 i9505 Original Android Development] AL_IRAQI:
Thanks, this time everything works fine but cm13 didnt boot up :D

i installed it in /dual, logs attached 20151219.212659.tar

i restored main ROM kernel and it works fine

Edit:

i tried to use stock ROM as Secondary and it didn't boot up also, but this time it hangs at Device name

logs also attached 20151219.221753.tar

Edit 2:

this time i tried to update ramdisk for main ROM and it didnt boot up also

logs also attached 20151219.222630.tar
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
[MENTION=5207461]Salman A.[/MENTION]

I have some things for you to test :) I did some testing by flashing the CM ROM you linked to on my Galaxy S4 (anyone reading this, do not attempt!) and I managed to get rid of the /proc/dumchar_info error. If you wouldn't mind, I like you to test the debug build linked below like this:

Completely uninstall old app (both snapshot and debug if you have both).

Install new debug app and patch a ROM containing system.new.dat. Don't do any of the previous edits to updater-script.

Backup via TWRP. In this debug build, the ROM you install can directly access partitions, so there is a small chance it might wipe your /system partition.

Flash the patched ROM.

Save recovery.log either using DualBootUtilities or TWRP's built-in button

Debug build: https://snapshots.noobdev.io/misc/XDA/Salman A./Test1_Copy_All_Block_Devs/Android_GUI-debug.apk

Thanks!
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Thanks for all the logs! Unfortunately, the kernel log didn't get saved in any of those archives due to my mistake. Would you mind trying again with 8.0.0.r2033.gb66b8c9 and grabbing the logs the same way? There's no need to test all 3 scenarios, just whichever one is easiest for you.

EDIT: My home internet is slow right now. My server might not finish building and uploading 8.0.0.r2033.gb66b8c9 until an hour later.
[Galaxy S 4 i9505 Original Android Development] RWOLUPO:
Hey,

here is the log from nexus 5x

thx in advance
[Galaxy S 4 i9505 Original Android Development] AL_IRAQI:
ill get the logs from update ramdisk because installing and switching the ROM works fine

its okay :)

Do you need stock boot.img or link to kernel source ?
[Galaxy S 4 i9505 Original Android Development] TheDarkKnight:
Thank you so much for your hard work..

Here's the log. It still fails and gives the proc/dumchar_info error.. But you give me hope :o

P.S.: Laughed a lot when I saw this: [MultiBoot] On noes! You have an MTK device :D
[Galaxy S 4 i9505 Original Android Development] SamuelBegui:
Hello, I downloaded the most recent app and I'm trying to share my apps and data with my secondary ROM (On the ex_sd) however I can't seem to find anywhere a way to update mbtool. I remember on an older build updating mbtools (or ramdisk) was integrated in the dual boot app itself. Can anyone point me in the right direction? ( I did a search through the post to find if I can flash something and whatnot)
[Galaxy S 4 i9505 Original Android Development] yilun:
ROMS settings
[Galaxy S 4 i9505 Original Android Development] TheDarkKnight:
Check a few posts above. Chen has said it

It's inside each ROM's info (three-dot menu) at the bottom..
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Darn it... New build to try :) https://snapshots.noobdev.io/misc/XDA/Salman A./Test2_Copy_All_Devs/Android_GUI-debug.apk

:laugh: ;)
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Sounds good, thanks! If you could send me the boot.img, that would be great too. I mainly need to take a look at the ramdisk which usually is not part of the kernel source.
[Galaxy S 4 i9505 Original Android Development] SamuelBegui:
Sorry had just saw it :/ Thanks!

I also noticed (read through here as well) that CM13 has had issues with Ramdisk correct?
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Added support in version 8.0.0.r2034.ga54b805 :)
[Galaxy S 4 i9505 Original Android Development] TheDarkKnight:
Here's the new log.. It fails but shows a different error (hope :)): Bad file number
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
For any who has contributed to the code before, the device support code is now split into multiple files in libmbp/devices/ (https://github.com/chenxiaolong/DualBootPatcher/tree/master/libmbp/devices) instead of having everything in libmbp/patcherconfig.cpp. The compile time started increasing exponentially as support for more devices were added due to the way gcc/clang track variables. It got to the point where it was taking nearly 10 minutes to compile that file alone on the build server and that file has to be compiled 5 times (once for Android arm, arm64, x86, x86_64 and once for Windows). The last few builds took about 1:40 hours to build: https://jenkins.noobdev.io/job/DualBoot_Patcher/buildTimeTrend :D

EDIT: Actually, patcherconfig.cpp is compiled 9 times. Once for each architecture in the Android build and once for each architecture for the Windows build + once for the Windows GUI.
[Galaxy S 4 i9505 Original Android Development] AL_IRAQI:
Kernel size is different after updating ramdisk

Here you are

boot.img & logs
[Galaxy S 4 i9505 Original Android Development] 911-Future_Maker:
Hi [MENTION=4277844]chenxiaolong[/MENTION]. Today I tried something dangerous: I swapped storage of my primary rom via the "change default write disk" option in Settings. :D May be it's stupid because I have 4 Roms installed on my phone (3 on my extsd and the primary rom on internal). Now when the phone booted after swapping internal with extsd I was prepared for a real disaster: from apps not working anymore or missing to force closes everywhere and the most important - to find my multiboot setup broken. Then I was freaking amazed when I opened the dualboot app and successfully switched to one of my roms installed on extsd. WOW! How this could be? I expected some error when the app searches for boot.img in particular rom folder on internalsd but can't find it because it no longer exist. Does the app reads all the important info it needs from the /raw partition? This is my explanation why my multiboot setup survived through swapping storage. This is great. One thing that I can said is that I lost my custom pics for roms because they are now located in the multiboot dir on my "previous" internal sd. Is it safe to just copy paste these files and folders to the new multiboot dir where now a system.img files are only located? Or it will confuse the app and will become one big mess? What if I swap storage on one or all the other roms I have installed? Waiting for your answer dude and meanwhile enjoying your dualboot app as always. It really makes our phones 101% more functional. Thanks.

In my experience it's actually normal to find the new patched boot.img larger and not smaller than the old original boot.img. Did you tried switching the roms? It might just works. Sorry if you already said that, I don't have much time to read the prevous pages if the thread.
[Galaxy S 4 i9505 Original Android Development] tomaasz:
[MENTION=4277844]chenxiaolong[/MENTION]

Could you look why I can't launch my data-slot-1 rom ?

I have installed 2 roms

secondary (dual) TW 5.1.1

data-slot-1 TW 5.1.1

I haven't any problem with secondary, but data-slot-1 I launched only once, just after installation.

After this I switched to secondary and now I can't switch back to data-slot-1
[Galaxy S 4 i9505 Original Android Development] RWOLUPO:
thx! works fine :)
[Galaxy S 4 i9505 Original Android Development] 911-Future_Maker:
Indeed! Really no need for that large cache partition, even 1GB is huge. 500MB is fine.

Btw: Anyone with MTK phone tried the 2007 and 2024 builds?? Are the specific problems related to this cpu fixed or not? May be I'll be again the white mouse, heh.