View Single Post
Old 08-12-2021, 09:43 PM   #37
Renate
Wizard
Renate ought to be getting tired of karma fortunes by now.Renate ought to be getting tired of karma fortunes by now.Renate ought to be getting tired of karma fortunes by now.Renate ought to be getting tired of karma fortunes by now.Renate ought to be getting tired of karma fortunes by now.Renate ought to be getting tired of karma fortunes by now.Renate ought to be getting tired of karma fortunes by now.Renate ought to be getting tired of karma fortunes by now.Renate ought to be getting tired of karma fortunes by now.Renate ought to be getting tired of karma fortunes by now.Renate ought to be getting tired of karma fortunes by now.
 
Posts: 2,562
Karma: 11672405
Join Date: Feb 2012
Device: Nook NST, Glow2, 3, 4, '21, Kobo Aura2, Poke3, Poke5
Quote:
Originally Posted by mergen3107 View Post
So could you please outline how should I safely unpack it and build again?
Being obtuse, I use my own tools.
Look for imgutil.exe (in sig)

I've already seen the problem in recovery, it's prop.default, persist.sys.usb.config=none
But there seems to be a bigger problem getting a (unmodified) recovery image to boot over fastboot.
It seems to just default to booting the regular system image.
Code:
$ reboot bootloader
C:\>fastboot boot part09
I'm not sure what's going on. I can fb boot a modified system (w/o ramdisk), a magisk (w ramdisk).

Quote:
Originally Posted by mergen3107 View Post
(I miss lsblk, which is not present in Android, AFAIK)
Have you tried zerostat (in sig)?
Code:
C:\>adb push zerostat /data/local/tmp
C:\>adb shell
$ cd /data/local/tmp
$ chmod 755 zerostat
$ su
# ./zerostat
Renate is offline   Reply With Quote