Database Info

[HOWTO] Enable init.d on stock *rooted* Desire roms

If you are like me and you like your stock Desire rom, you rooted it using unrEVOked or some other methods, you made some custom adjustment to it and you really don't want to load a fully fledged 3rd party rom but still, you'd like to tweak it a little bit more, you'll quickly realize that you are going to need a working init.d system in order to start custom scripts on boot.
This thread will try to explain how to add init.d support to your rom, without needing to flash a new rom and wipe everything, we're just going to flash a new boot.img.
Requirements
Rooted HTC Desire
New modified boot.img, supported firmware versions: 2.10.405.2, 2.29.405.2/5, check your firmware version here: (Settings -> About Phone -> Software information -> Software number)
Download this one: View attachment boot_2.10.405.2.zip if your "Software number" is: 2.10.405.2
Download this one: View attachment boot_2.29.405.2_5.zip if your "Software number" is: 2.29.405.2 or 2.29.405.5
Make sure you download the one matching your "Software number", the wrong one will cause boot loops and weird behaviors.
ADB shell access
flash_image binary, usually provided by unrEVOked under /data/local/flash_image but if you don't have grab it here: View attachment flash_image.zip
busybox correctly installed under /system/xbin
HOW-TO
NOTE: if your Desire is not S-OFF (meaning you can't write to the /system directory), you'll need to do the whole procedure in recovery mode.
Do a nandroid backup, this in order to save your current boot.img, and also because it's never a bad idea
Make sure the nandroid backup went ok
Check your exact firmware version (Settings -> About Phone -> Software information -> Software number) and download the corresponding modified boot.img
Copy and unzip the downloaded boot.img to your sdcard or wherever you like it
Obtain adb shell access, become root (su) and wipe the existing boot image with:
Code:
cat /dev/zero > /dev/mtd/mtd2
ignore the "write: No space left on device", it's normal.
Flash the new boot image:
Code:
flash_image boot /sdcard/boot.img
where "/sdcard/boot.img" is the path where you copied the downloaded boot.img
Remount the /system partition read-write if you're not in recovery mode:
Code:
mount -o remount,rw /system
or mount it if you are in recovery mode:
Code:
mount /system
Create the init.d directory where all the custom boot scripts will be executed:
Code:
mkdir /system/etc/init.d
and set permissions:
Code:
chmod 755 /system/etc/init.d
Important: unzip and copy the View attachment 99complete.zip script to the newly created /system/etc/init.d/99complete, set permissions:
Code:
chmod 755 /system/etc/init.d/99complete
and ownership:
Code:
chown root.shell /system/etc/init.d/99complete
Failure to do so will cause a boot loops.
Cross your fingers and reboot! If anything goes wrong you can always boot into recovery and fix errors or you can restore the nandroid backup (you can just restore the boot.img if you don't want to do a full restore).
From now on, every script you put inside /system/etc/init.d will be executed at boot before almost any other initializations. Make sure you set the correct permissions to your scripts (i.e. 755).
Thanks to: teppic74 for providing stock roms with init.d support (thread) where I extracted the boot images.

Technical explanation
The provided boot.img are the original HTC provided boot.img with the init.rc script modified to stop the init process until the cm.filesystem.ready property is set to 1:
Code:
start sysinit
on property:cm.filesystem.ready=1
class_start default
where the sysinit service is the service in charge of starting all the scripts inside /etc/init.d:
Code:
# Execute files in /etc/init.d before booting
service sysinit /system/bin/logwrapper /system/xbin/busybox run-parts /system/etc/init.d
disabled
oneshot
and the last of this script, 99completed, only sets that property to 1 so the normal system boot can continue:
Code:
#!/system/bin/sh
sync;
setprop cm.filesystem.ready 1;
of course changing init.rc is only possible by flashing a new boot.img with init.rc modified inside the ramdisk because that file, even if you can see it under / will be overwritten at every boot.
Another small modification of the new boot.img is the default.prop, in which rc.secure is set to 0 allowing to gain direct access through "adb shell"

Sounds great
Thx for your work!
So if I get that right, it's the same as if we'd flash teppic74 ROM, and nandrestoring everything except system & boot?
Just our stock ROM with init.d support?
Does that also mean we could flash the optional mods from teppic74 thread like a2sd?
Ty again!

Puenos said:
Sounds great
Does that also mean we could flash the optional mods from teppic74 thread like a2sd?
Ty again!
Click to expand...
Click to collapse
Well you could but effectively all you need is an apps2sd+ script and you can adb push it to the correct location. /system/etc/init.d

Really? I would have tried flashing either a2sd provided in teppic74's thread or even a2sd script by DT? last I would have compared to firerat's script. But if all you need to do is pushing via adb.. Is there a script out for a2sd especially for stock/sense? (like kali advised using firerat with CM?)
Thank you

Not sure to be honest, I haven't used sense for a long time. But assume if the one teppic uses on his, works - it should work for you too.

I'm just using Sense because of it's Mail-widget, haha
But I guess I'll just give it a try then, will report back, when I've managed so set everything up without having my phone exploding, hehe
But thank you very much

exactly this boot.img will just enable init.d support, no need to flash a new system.img but you just need to create the init.d directory and put the 99complete script, after that you can install any mod you like, also the ones provided in teppic74's thread.
You can also try data2whatever by melethron (that's what I'm using), just make sure you have busybox correctly installed.
hope you enjoy it and happy new year!

well I hv software number 2.11.832.3 so what I hv to do...?

r3vb07inf said:
well I hv software number 2.11.832.3 so what I hv to do...?
Click to expand...
Click to collapse
unfortunately I don't have a boot.img for that software number, you'll need to manually extract your boot.img, modify a file (init.rc) and reflash it, if you don't know how to do it I can try to do it for you but I'll need a download link for your original firmware version

You could make a universal (froyo) update zip using Koush's AnyKernel installer, then you're able to update the ramdisk only and add the init.d folder/script. Thats how i did it for CM7.

worstenbrood said:
You could make a universal (froyo) update zip using Koush's AnyKernel installer, then you're able to update the ramdisk only and add the init.d folder/script. Thats how i did it for CM7.
Click to expand...
Click to collapse
interesting, an update script that can extract the boot.img, unpack, change files, repack it and reflash it...is it safe? I may think about building an update.zip this way but I'm pretty scared by how safe it can be to automatically mess with a boot.img..
EDIT: one problem of this is that the init.rc needs to be extracted and modified, but it may be different from one firmware and another

moebius83 said:
interesting, an update script that can extract the boot.img, unpack, change files, repack it and reflash it...is it safe? I may think about building an update.zip this way but I'm pretty scared by how safe it can be to automatically mess with a boot.img..
EDIT: one problem of this is that the init.rc needs to be extracted and modified, but it may be different from one firmware and another
Click to expand...
Click to collapse
Should be the same between all froyo rom's. Check this update zip, it's for gingerbread tho, you have to replace the ramdisk-new.gz with a froyo one (with edited init.rc offcourse). It also contains /system/etc/init.d/99complete.
Edit: Don't be scared, everyone who releases custom kernels uses this method. The other way around then, keep the original ramdisk and merge it with the new kernel.

Hello there
Really appreciate all your efforts
Kindaa feeling real dumb in comparison! lol
Anyways
My Desire specs :
2.2
2.32.415.3
Baseband 32.49.00.32U_5.11.05.27
Now this has built in arabic enabled support and that is the main reason I would like to keep it
Am yet to run into a custom ROM that would provide that without having to downgrade my version
Also, had a lotta fun trying to root, just couldn't root, up untill a few days back when unrevoked came out with thier new 3.3 version
I noticed you had only two software versions from which to start...
So what about my case? could you please help this newbie along?!!

docnasef said:
Hello there
Really appreciate all your efforts
Kindaa feeling real dumb in comparison! lol
Anyways
My Desire specs :
2.2
2.32.415.3
Baseband 32.49.00.32U_5.11.05.27
Now this has built in arabic enabled support and that is the main reason I would like to keep it
Am yet to run into a custom ROM that would provide that without having to downgrade my version
Also, had a lotta fun trying to root, just couldn't root, up untill a few days back when unrevoked came out with thier new 3.3 version
I noticed you had only two software versions from which to start...
So what about my case? could you please help this newbie along?!!
Click to expand...
Click to collapse
Same thing happens to me. My spec:
2.2
2.13.707.1
32.44.00.32U
Can you help as well? Or where or how (from RUU) can I find the ramdisk-new.gz as worstenbrood's mention.

mumu_li said:
Same thing happens to me. My spec:
2.2
2.13.707.1
32.44.00.32U
Can you help as well? Or where or how (from RUU) can I find the ramdisk-new.gz as worstenbrood's mention.
Click to expand...
Click to collapse
Thanks "worstenbrood" then I can extract boot.img from stock rom. Based on the guide, I made a new boot.img. But with this new boot.img, the phone hangs at the first screen(waiting at least for 15 mins). I don't know why. I also did as worstenbrood suggest and the system boot loopless.
Can somebody help?
I attached my boot.img (original and modified) for your information.

mumu_li said:
Thanks "worstenbrood" then I can extract boot.img from stock rom. Based on the guide, I made a new boot.img. But with this new boot.img, the phone hangs at the first screen(waiting at least for 15 mins). I don't know why. I also did as worstenbrood suggest and the system boot loopless.
Can somebody help?
I attached my boot.img (original and modified) for your information.
Click to expand...
Click to collapse
did you create the /system/etc/init.d directory and the 99complete file with the correct permissions? as noted on the OP this is needed because that file will tell the boot process to continue, otherwise you'll be stuck at the boot screen
EDIT: also, do you have busybox installed under /system/xbin?

docnasef said:
Hello there
Really appreciate all your efforts
Kindaa feeling real dumb in comparison! lol
Anyways
My Desire specs :
2.2
2.32.415.3
Baseband 32.49.00.32U_5.11.05.27
Now this has built in arabic enabled support and that is the main reason I would like to keep it
Am yet to run into a custom ROM that would provide that without having to downgrade my version
Also, had a lotta fun trying to root, just couldn't root, up untill a few days back when unrevoked came out with thier new 3.3 version
I noticed you had only two software versions from which to start...
So what about my case? could you please help this newbie along?!!
Click to expand...
Click to collapse
@ moebius83
If you could help, I would really appreciate it...
Please take into consideration That I am more or less android dumb!
I attached the url for my original RUU if that helps?
http://www.mediafire.com/?ih3lbbm7yfag7d2
Would REALLY appreciate your help.
Thanks m8!

mumu_li said:
Thanks "worstenbrood" then I can extract boot.img from stock rom. Based on the guide, I made a new boot.img. But with this new boot.img, the phone hangs at the first screen(waiting at least for 15 mins). I don't know why. I also did as worstenbrood suggest and the system boot loopless.
Can somebody help?
I attached my boot.img (original and modified) for your information.
Click to expand...
Click to collapse
i created a update.zip which replaces the ramdisk only and add /system/etc/init.d/99complete. It should work for every froyo release.

worstenbrood said:
i created a update.zip which replaces the ramdisk only and add /system/etc/init.d/99complete. It should work for every froyo release.
Click to expand...
Click to collapse
great job, I was just going to make the same update.zip, you were faster, I'll link it on the OP, thanks again!

[Q] Xoom Loading Custome Kernel

I have a xoom wifi with android 3.2 on it. Kernel [email protected] #1
I'm rooted and my bootloader is unlocked. I downloaded the Timate kernel (Tiamat-Kernel-2.0.0-Katana-stockgpu.zip) and loaded it with clockwork recovery. I saw anykernel run when I applied the zip. But after I reboot the xoom still has the same kernel version on it.
Did I miss a step somewhere? How does it keep loading the stock kernel after I load the new one? The only thing I can think of is that there is a failsafe mode that loads the "last good" kernel if the current one fails.

njdevi11 said:
I have a xoom wifi with android 3.2 on it. Kernel [email protected] #1
I'm rooted and my bootloader is unlocked. I downloaded the Timate kernel (Tiamat-Kernel-2.0.0-Katana-stockgpu.zip) and loaded it with clockwork recovery. I saw anykernel run when I applied the zip. But after I reboot the xoom still has the same kernel version on it.
Did I miss a step somewhere? How does it keep loading the stock kernel after I load the new one? The only thing I can think of is that there is a failsafe mode that loads the "last good" kernel if the current one fails.
Click to expand...
Click to collapse
Do a manual Flash from recovery. or - Upgrade to ICS with -Download the EOS ICS 1.0.0 (good stable ROM/kernel)
http://forum.xda-developers.com/showthread.php?t=1484770

SOLVED:
So for whatever reason I absolutely CAN NOT get an anykernel zip to work for me and i've tried it on a few devices (xoom, nexus s, atrix, nook off the top of my head). Here is what I had to do to get my own kernel on the xoom:
(1) make a backup with CWM, and copy the boot.img to my computer.
(2) extract boot.img with unpack-bootimg.pl
(3) this gives me the boot-img-ramdisk.cpio.gz file and boot.img-kernel.gz
If you want to recpio because you changed the ramdisk/added ko's run:
cd boot.img-ramdisk/
find . | cpio -o -H newc | gzip > ../bootimg-ramdisk.cpio.gz
cd ..
(4) use command:
mkbootimg --cmdline 'androidboot.carrier=wifi-only product_type=w' --kernel zImage --ramdisk boot.img-ramdisk.cpio.gz -o boot-new.img --base 0x30000000 --pagesize 4096
adb reboot bootloader
fastboot flash boot boot-new.img

Adendium:
I figured out what the command= should be by opening a working boot-img in a hex/text editor (vi) and just copied what should be in there. That seems to do that trick for the last few devices i've tried compiling kernels for. All the "tutorials" on the internet I've seen get really sketchy when it comes to actually repacking a kernel and there is a lot of bad or just lazy information that's outdated or copied about one device for another that doesn't actually work like that.

Single Click bootable kernel update maker script for galaxy-y

Hi
I am posting the scripts and tools i am using in my galaxy-y
this tool can produce a kernelUpdate.zip which can be used in recovery mode to flash new kernel in the device from the bare kernel 'zImage' produced from kernel compiling
This will automatically create boot.img and make a 'update.zip' like package from it
Instructions:
*Extract the zip
*place your zImage in the folder
*just run the file file "mkKernelUpdate.sh"
If any error occurs look in to the scriptss.......
I hope this will be help full to you all
-Thanks.....

Wow this is great... Thanks man...

harish2704 said:
this tool can produce a kernelUpdate.zip which can be used in recovery mode to flash new kernel
Click to expand...
Click to collapse
wow ! pretty awesome. you mean those update.zip can be run from stock Android system recov rather than CWM. makes it a bit simpler for some dudes ...

just to clarify this is different from faqbly script right?
this one can be used on stock recovery?
can anyone verify?

Its nice man

zeusseuz said:
just to clarify this is different from faqbly script right?
Click to expand...
Click to collapse
ya different ball game altogether !

Let me clarify....
By the word "recovery mode" I mean the recovery mode we see when pressing 'Vol+' + power +home at boot time FOR A FRESH GALAXY-Y Hand set
I never used other recovery modes
I use this method to flash kernel from my ubuntu linux
Any one knows any othe alternatives to odin????
Not heimdal its not suppoted for our device
No need to say or PRSS thanks.just look my new thread and help me if you can
Click to expand...
Click to collapse

harish2704 said:
Any one knows any othe alternatives to odin????
Click to expand...
Click to collapse
well an alternative to odin is dd, when used after bmlunlock
flashing comes down to dd if= of= when unlocked.
no need for PC & cable ...
CWM is an improved recovery mode with better scripts and stuff. in merruks kernel, when in recov, you have root shell access. does add flexibility ...

also Heimdall recently expanded it's list of supported devices.
it's Windows "zadig" libUSB driver works with SGY too
the amount of work required to get Heimdall working on SGY should be limited.

mai77 said:
also Heimdall recently expanded it's list of supported devices.
it's Windows "zadig" libUSB driver works with SGY too
the amount of work required to get Heimdall working on SGY should be limited.
Click to expand...
Click to collapse
You mean Heimdall now supports SGY?????
Have you tested with linux??

Heimdall does not support SGY yet.
but the libUSB 'zadig' drivers work with the SGY (in Windows)
this reduces the effort it takes to get SGY supported by Heimdall

success report ?
harish2704 said:
this tool can produce a kernelUpdate.zip which can be used in recovery mode to flash new kernel in the device from the bare kernel 'zImage' produced from kernel compiling.
This will automatically create boot.img and make a 'update.zip' like package from it.
Instructions:
* Extract the attached zip
* place your zImage in the folder
* just run the file file "mkKernelUpdate.sh"
Click to expand...
Click to collapse
essentially, make boot image is run
./mkbootimg --kernel ${cwd}/zImage --ramdisk ${cwd}/original_boot.img-ramdisk.gz --base 0x81600000 --kernelMD5 ${kernMd5} -o boot.img
(...)
java -classpath testsign.jar testsign foo.zip KernelUpdate.zip
(...)
mv KernelUpdate.zip KernelUpdate_${tstamp}.zip
so any changes in kernel source or ramdisk init.rc or whatever gives you the ready made boot.img flasher
seemingly the script is fully working on SGY. any reports ?

[Q] Compiling Kernel

Hi All,
I take notes with my Tab2, and sometimes the Default behaviour of the Touchscreen annoys me.
So i decided to recompile the kernel with 3 lines of code added. When done i replaced the zImage in the boot.img of the kkboot stock zip and flashed it trough clockworkmod.
Then i got stuck, my tablet gets stuck inside a boot loop (only the logo comes up, and then reboots after 3 seconds).
The kernel compilation was done by:
- Download Ubuntu, follow the guide on Andriod to setup a build enviorment
- Download Doomlord's toolchain
- Download source from Samsung Open Source
- Adjust code
- Compile using samsungs instructions
How can i resolve this?

http://forum.xda-developers.com/showthread.php?t=1859227 Use Sourcery G++ Lite 2010q1-202 as per Samsung instruction.

ketut.kumajaya said:
http://forum.xda-developers.com/showthread.php?t=1859227 Use Sourcery G++ Lite 2010q1-202 as per Samsung instruction.
Click to expand...
Click to collapse
So, retry compiling with Codesourcery. What parameters do i need to pass to mkbootimg?

Plis man do oc kernel to 1,4 ghz for g tab 7

gieltjev said:
So, retry compiling with Codesourcery. What parameters do i need to pass to mkbootimg?
Click to expand...
Click to collapse
I have my own script base on http://forum.xda-developers.com/showthread.php?t=1241005

ketut.kumajaya said:
I have my own script base on http://forum.xda-developers.com/showthread.php?t=1241005
Click to expand...
Click to collapse
So i downloaded "arm-2010q1-202-arm-none-linux-gnueabi-i686-pc-linux-gnu.tar.bz2" and your toolkit.
First i extracted the boot.img from "kkboot-0.4.2-core-jb-p51xx.zip", extracted the boot.img and made a new one including my zImage. then using zip replaced boot.img with the new boot.img.
This time the booting takes around 6 seconds, but still resetting.
dawidex444 said:
Plis man do oc kernel to 1,4 ghz for g tab 7
Click to expand...
Click to collapse
If the result is positive i will share my adjustments here so that the real cooks can bake a decent kernel

gieltjev said:
So i downloaded "arm-2010q1-202-arm-none-linux-gnueabi-i686-pc-linux-gnu.tar.bz2" and your toolkit.
First i extracted the boot.img from "kkboot-0.4.2-core-jb-p51xx.zip", extracted the boot.img and made a new one including my zImage. then using zip replaced boot.img with the new boot.img.
This time the booting takes around 6 seconds, but still resetting.
If the result is positive i will share my adjustments here so that the real cooks can bake a decent kernel
Click to expand...
Click to collapse
So what "adb shell dmesg" output?
EDIT: Incompatible PVR kernel module, disable MODVERSION and add "-blackhawk" string to LOCALVERSION in your kernel config file or you can extract my config file from "/proc/config.gz" by "insmod /system/lib/modules/configs.ko".

ketut.kumajaya said:
So what "adb shell dmesg" output?
EDIT: Incompatible PVR kernel module, disable MODVERSION and add "-blackhawk" string to LOCALVERSION in your kernel config file or you can extract my config file from "/proc/config.gz" by "insmod /system/lib/modules/configs.ko".
Click to expand...
Click to collapse
Wow, how did you find that out?
So i set, CONF_MODVERSION=n, LOCALVERSION='-blackhawk'
Let's recompile
EDIT: Recompiled, added into the CORE kkboot image. Still resetting. while the logo shows i cannot execute "adb shell dmesg". If executed from CWM it adb shell dmesg works.

Code:
$ cp android_espresso10_omap4430_r02_user_blackhawk_defconfig.txt kernel/arch/arm/configs/android_espresso10_omap4430_r02_user_blackhawk_defconfig
$ cd kernel
$ make mrproper
$ make ARCH=arm android_espresso10_omap4430_r02_user_blackhawk_defconfig
$ make -j4 ARCH=arm

ketut.kumajaya said:
Code:
$ cp android_espresso10_omap4430_r02_user_blackhawk_defconfig.txt kernel/arch/arm/configs/android_espresso10_omap4430_r02_user_blackhawk_defconfig
$ cd kernel
$ make mrproper
$ make ARCH=arm android_espresso10_omap4430_r02_user_blackhawk_defconfig
$ make -j4 ARCH=arm
Click to expand...
Click to collapse
Ok, that works! i've got my own kernel running on the device. Now i will continue getting the fix to work.

gieltjev said:
Ok, that works! i've got my own kernel running on the device. Now i will continue getting the fix to work.
Click to expand...
Click to collapse
Congratulations :good:

gieltjev said:
First i extracted the boot.img from "kkboot-0.4.2-core-jb-p51xx.zip", extracted the boot.img and made a new one including my zImage. then using zip replaced boot.img with the new boot.img.
Click to expand...
Click to collapse
What you've done is exactly what I'm trying to do now.
But I'm stuck in unpacking boot.img in kk-boot.
Which unpack/repack tool did you use? Can you plz share them?

Question Bootloader Unlocked Warning

Has anybody figured out how to get rid of the Bootloader Unlocked warning when booting this phone? It certainly slows down the booting process.

I haven't figured it out yet. To be honest I've been trying to figure out what apps are safe to uninstall and a custom ROM or how to update to Android 12. But I'll definitely let you know if I figure a way out.

dfreedom834 said:
I haven't figured it out yet. To be honest I've been trying to figure out what apps are safe to uninstall and a custom ROM or how to update to Android 12. But I'll definitely let you know if I figure a way out.
Click to expand...
Click to collapse
I have been trying to build TWRP for this device. I am very close, but the mkbootimg command script is issuing a bad argument and I have been unable to trace it down so far.
Code:
[100% 4/4] Target boot image: /mnt/audio/android/twrp/out/target/product/minsk/boot.img
FAILED: /android/twrp/out/target/product/minsk/boot.img
/bin/bash -c "(/android/twrp/out/host/linux-x86/bin/mkbootimg --kernel /mnt/audio/android/twrp/out/target/product/minsk/kernel --ramdisk /android/twrp/out/target/product/minsk/ramdisk.img --base 0x00000000 --pagesize 4096 --cmdline \"console=ttyMSM0,115200n8 androidboot.hardware
=qcom androidboot.console=ttyMSM0 androidboot.memcg=1 lpm_levels.sleep_disabled=1 video=vfb:640x400,bpp=32,memsize=3072000 msm_rtb.filter=0x237 servic
e_locator.enable=1 swiotlb=1 androidboot.usbcontroller=a600000.dwc3 earlycon=msm_geni_serial,0x880000 loop.max_part=7 printk.devkmsg=on androidboot.ha
b.csv=10 androidboot.hab.product=minsk androidboot.hab.cid=50 firmware_class.path=/vendor/firmware_mnt/image buildvariant=user buildvariant=eng\" --os
_version 16.1.0 --os_patch_level 2099-12-31 --ramdisk_offset 0x01000000 --tags_offset 0x00000100 --dtb device/motorola/minsk/prebuilt/dtb.img --header
_version 2 --output /mnt/audio/android/twrp/out/target/product/minsk/boot.img ) && (true )"
mkbootimg: error: unrecognized arguments: --dtb device/motorola/minsk/prebuilt/dtb.img
ninja: build stopped: subcommand failed.
15:01:24 ninja failed with: exit status 1
So the --dtb should be --recovery_dtbo I believe. Not sure where this command is being generated in order to fix it.

I was running into problems like that I factor rest it and turned it off. Where did you compile the boot.img from? And ya it would work better if it was trying to go to the right path. I had to find a boot.img from one of the over seas ones I kept getting it were it would root but the screen did respond.

lexridge said:
So the --dtb should be --recovery_dtbo I believe. Not sure where this command is being generated in order to fix it.
Click to expand...
Click to collapse
I could be wrong but the recovery I'm using (orange fox) does use a kernel_dtb. So it seems your recovery image kernel doesn't have the right path to the dtb binary it needs. Try searching the build directory for any _dtb/.dtb and rename accordingly. I'd you need to alter the dtb from a related SoC there are tools for unpacking and modifying those.
The recovery and boot ones would be similar I imagine since those files are a map of the device's hardware.

dfreedom834 said:
I was running into problems like that I factor rest it and turned it off. Where did you compile the boot.img from? And ya it would work better if it was trying to go to the right path. I had to find a boot.img from one of the over seas ones I kept getting it were it would root but the screen did respond.
Click to expand...
Click to collapse
I took the boot.img from the full device A11 factory image.
MINSK_RETUS_11_RPCS31.Q2-109-16-2_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
I used the same one to create my magisk boot.img as well. I used dumpyara to build the device tree using the above file for my source which seemed to work properly. No errors in other words.

elrod16 said:
I could be wrong but the recovery I'm using (orange fox) does use a kernel_dtb. So it seems your recovery image kernel doesn't have the right path to the dtb binary it needs. Try searching the build directory for any _dtb/.dtb and rename accordingly. I'd you need to alter the dtb from a related SoC there are tools for unpacking and modifying those.
The recovery and boot ones would be similar I imagine since those files are a map of the device's hardware.
Click to expand...
Click to collapse
I have a dtbo directory containing these files:
Code:
00_kernel
01_dtbdump_amxbr.dtb
02_dtbdump_amxbr.dtb
03_dtbdump_amxbr.dtb
04_dtbdump_amxbr.dtb
05_dtbdump_amxbr.dtb
I also have a dtb.img in the root of the device tree. I will copy it to dtbo.img and see what happens. Thanks for the hint.

lexridge said:
I have a dtbo directory containing these files:
Code:
00_kernel
01_dtbdump_amxbr.dtb
02_dtbdump_amxbr.dtb
03_dtbdump_amxbr.dtb
04_dtbdump_amxbr.dtb
05_dtbdump_amxbr.dtb
I also have a dtb.img in the root of the device tree. I will copy it to dtbo.img and see what happens. Thanks for the hint.
Click to expand...
Click to collapse
I think dtb.img probably has all of the dtb files compiled together

elrod16 said:
I think dtb.img probably has all of the dtb files compiled together
Click to expand...
Click to collapse
That is my thought as well.

lexridge said:
That is my thought as well.
Click to expand...
Click to collapse
I just recently had to deal with all this crap because I didn't know GPD changed which revision of the mediatek SoC they used in the GPD XD while keeping the serial numbers the same. Flashed my old one's backup on it and half the cores were stuck offlined when it booted up. Ended up having to get ahold of the stock kernel for that board revision and patch in the correct dtb for that SoC.
I don't have links but some of the sites that delve into generic Linux kernel porting have tools for decompiling kernel_dtb files to an editable form that you can then recompile if you do have device/driver issues. Also the magisk module for enabling TWRP sdcard storage backups has some Android arm64 native binaries in it that can help with tearing apart kernel/recovery images. (They both are technically kernel images, just one boots a minimal OS).
Edit: I think any dtbo files would be individual compiled object files that get linked into the final dtb image.
Edit 2: I just saw your other comment above. Congrats, that sounds like a viable (and probably long term stable) way you found.

On another topic, I have been trying to mount /system as r/w (thru adb). It appears /system is not actually a mount point but under a different mount point. Any idea what that might be? Doing a cat on /proc/mounts yeilds a crapload of mounts, with many belonging to magisk, but no /system.

I know its been 4 month since last activity, but has there been any progress on this?

There does not seem to have been much progress on this, but I read somewhere recently that the G Stylus (2021) was either the most popular or best-selling Moto phone in 2021. Who knows if that is exactly true, but if it is indeed so popular, here's to hoping that some capable developers will take an interest in it eventually!

Several folks have mentioned that loading a GSI (Generic System Image) should be possible, but I have not had any extended downtime myself to be able to try this. But if you do, you can find some guidance for the 2020 version of the G Stylus at:
https://forum.xda-developers.com/t/...ic-system-image-on-the-moto-g-stylus.4131199/