Ah you meant the dtb
1 Like
Np. Since I flashed custom firmware, my serial shows as 0123456789ABCDEF.
1 Like
I guess I could clean it up a bit and explain it better. Will put yours in.
Nice. You are correct about dtb - my mistake to confuse it initially with dtbo.
1 Like
Switched 
Happy you got your phone working the way you want, you are no fun to fight with (it never started). I was at the ready.
1 Like
@sh7411usa you seem to know what you are doing with this TWRP business.
Want to try making out of v3 boot? We have the below but it won’t boot to system.
stock_3.0.2_boot
I don’t have a V3 device, so somebody else is going to have to test it. That being said, lets get this clear. V3 TWRP wont boot to system, but TWRP is working.
The stock, obviously, will boot to system, but obviously again, does not have TWRP. You want a hybrid that does boot to system, but also has TWRP.
Try this. I used the same process I did for the other one. This contains the kernel from the stock, and the ramdisk, including TWRP, from the TWRP boot. IF (big IF) the boot issue was related to the kernel - it should be fixed. If it was something else, it most likely will still be there. Anyone with a V3 can try it out and let us know. (I hope they fully understand the risks of flashing unverified FW files…)
You are saying just take the kernel from the new 3rd f21) and dump it in 1.1.1 boot?
I also don’t have the device
Yeah. I took the kernel from the stock boot and repacked the twrp boot using the new kernel, the old ramdisk, and old dtb. Same thing I did for the “6.1.3 NEW” twrp. I took the “NEW” (V2) kernel from the boot, and repacked 1.1.1 twrp boot using the new kernel, the old ramdisk, and old dtb.
Ah. I dunno if the old dtb will be good
Where is TWRP, just the ramdisk?
Yup. its too complicated (not to say impossible, just time consuming) to extract twrp from the ramdisk, that’s why I used the whole ramdisk. As for the dtb, my understanding is that this is not the device tree used by the system - that lives in the dtbo partition. This is a local copy of the device tree used specifically by the recovery and “special”/fallback boot modes. It doesn’t need to be perfect because these modes do not use most of the hardware (no telephony, many do not use audio, etc.). We already know that TWRP is functioning using this dtb - touch, screen, vibration, fash, etc. The system should boot using the device tree from the dtbo partition. Case in point: My (confirmed working) V2 TWRP. It also uses dtb from V1. However, the rom uses dtbo partition from V2 - so system boots with audio.
1 Like
Thanks
You can try a manual port. Here are my notes, before from before I took the shortcut to copy the whole ramdisk.
TWRP Manual Port Notesmagiskboot unpack boot_twrp.imgmagiskboot unpack boot_stock.img\\\*\\\*ramdisk.cpio can be edited or extracted using 7zipif extracted on windows, do not repack! will lose symlinks and unix permissions. Use wsl or cygwin to modify.use windows extraction for reference only.In the ramdisk:
/system/bin
recovery (twrp binary)
adbd (allows using adb in recovery)
me.twrp.twrpapp.apk (twrp app for in recovery installation. not necessary, but why not?)
/twres (twrp resources - whole dir)
/system/etc
recovery.fstab (partition map for recovery)
twrp.flags (attribute flags)
ld.config.txt - make sure its the same
/system/lib64
(make sure all binaries from twrp are present here)
/ (root)
init.recovery.mt6761.rc (loads touchscreen and vibration drivers)
init.recovery.hlthchrg.rc (manages battery icon in recovery)
init.recovery.ldconfig.rc (linker - tells recovery where libs [*.so] files are)
init.recovery.service.rc (starts twrp background services, like adbd, etc)
init.recovery.usb.rc (manages usb connection to pc while in recovery)
Most of these .rc scripts will be the same, make sure any differences are updated, stock to match twrp.
safely ignore these files from root:
twrp_ramdisk-timestamp
ramdisk-files.txt
ramdisk-files.sha256sum
magiskboot repack boot_stock.img
DON’T FORGET TO MIRROR LINUX PERMISSIONS WHEN COPYING FILES IN WINDOWS!!
1 Like
Hello all,
my Qin is currently disassembled to allow it to dry after accidentally setting it down in a cup of liquid.
I remember once seeing someone saying that they glued the keys down , and that it improved typing abilities.
Can anyone confirm if this works?
And what the process was, type of glue, How much Etc.
Any other tips would be greatly appreciated too.
Thank you very much
Thank you for responding.
If I’m understanding correctly they’re saying to put the glue only to harden it but not to actually glue anything?
1 Like
Has anyone here ever tried this?
No idea, I just remembered seeing it on discord.
I think so.
Thanks this really worked!
I ended up not glueing but rather using a very thin plastic.
Like a business card sleeve.
(I actually used the sleeve from the Adirei HaTorah USB.)
2 Likes
i tried the boot image from @sh7411usa for new qins twrp and root and it just bootloops and not twrp at all. so well have to keep trying
1 Like