150
submitted 1 year ago* (last edited 1 year ago) by d3Xt3r@lemmy.nz to c/android@lemdro.id
  • [MagiskBoot] Support extracting boot image from payload.bin
  • [MagiskBoot] Support cpio files containing character files
  • [MagiskBoot] Support listing cpio content
  • [MagiskBoot] Directly handle AVB 1.0 signing and verification without going through Java implementation
  • [Daemon] Make daemon socket a fixed path in MAGISKTMP
  • [resetprop] Support printing property context
  • [resetprop] Support only printing persistent properties from storage
  • [resetprop] Properly support setting persistent properties bypassing property_service
  • [MagiskSU] Support -g and -G options
  • [MagiskSU] Support switching mount namespace to PID with -t
  • [MagiskPolicy] Fix patching extended permissions
  • [MagiskPolicy] Support more syntax for extended permissions
  • [MagiskPolicy] Support printing out the loaded sepolicy rules
  • [App] Support patching boot image from ROM zips
  • [App] Properly preserve boot.img when patching Samsung firmware with init_boot.img
top 12 comments
sorted by: hot top controversial new old
[-] TWeaK@lemm.ee 15 points 1 year ago
  • [App] Support patching boot image from ROM zips

Sounds useful!

[-] JackGreenEarth@lemm.ee 8 points 1 year ago
  • [MagiskBoot] Support extracting boot image from payload.bin

Does this mean I can extract the boot image on an unroooted phone, to root it?

Unclear. To me, you get the payload.bin from roms you download, but that don't necessarily expose boot.img, but I don't see how there would be a way for magisk to find a payload.bin on your rom on its own, it's just another more convenient way of getting a boot.img.

[-] alphapuggle@programming.dev 3 points 1 year ago* (last edited 1 year ago)

I'm assuming this is for patching an ota file. Right now I download the factory image and patch the init_boot.img from that, and flash it after I download and flash the OTA. I guess this means I don't have to download both

[-] JackGreenEarth@lemm.ee 2 points 1 year ago

Where do you download the factory image from? I can't find it on the Motorola website, or any trusted source.

[-] alphapuggle@programming.dev 2 points 1 year ago

I've personally got a pixel, and Google makes the factory images freely available. If I remember right my old Motorola had a desktop updater app that you could install if you set the USB mode on your phone to something like "installer" or similar. I could grab OTA files from the cache on the updater.

This is for custom roms mainly. LineageOS for example gives you a payload.bin but not a boot.img.

[-] hottari@lemmy.ml 4 points 1 year ago

Good stuff. Can't wait for this to make its way to Lygisk release.

Didn't know Lygisk existed, thanks for mentioning it here.

[-] techgearwhips@lemmy.world 3 points 1 year ago

I could have really used that "support extracting boot image from payload.bin" back when I had my OnePlus 10T. Having to go to my dental was inconvenient.

[-] Ado@lemmy.world 3 points 1 year ago

I switched to iOS a couple of years ago, and the biggest thing I miss is Magisk. Glad to see it's still going strong, keep kicking ass

Nice, i hope Delta updates soon.

this post was submitted on 28 Aug 2023
150 points (98.1% liked)

Android

17601 readers
174 users here now

The new home of /r/Android on Lemmy and the Fediverse!

Android news, reviews, tips, and discussions about rooting, tutorials, and apps.

🔗Universal Link: !android@lemdro.id


💡Content Philosophy:

Content which benefits the community (news, rumours, and discussions) is generally allowed and is valued over content which benefits only the individual (technical questions, help buying/selling, rants, self-promotion, etc.) which will be removed if it's in violation of the rules.


Support, technical, or app related questions belong in: !askandroid@lemdro.id

For fresh communities, lemmy apps, and instance updates: !lemdroid@lemdro.id

💬Matrix Chat

💬Telegram channels / chats

📰Our communities below


Rules

  1. Stay on topic: All posts should be related to the Android OS or ecosystem.

  2. No support questions, recommendation requests, rants, or bug reports: Posts must benefit the community rather than the individual. Please post to !askandroid@lemdro.id.

  3. Describe images/videos, no memes: Please include a text description when sharing images or videos. Post memes to !androidmemes@lemdro.id.

  4. No self-promotion spam: Active community members can post their apps if they answer any questions in the comments. Please do not post links to your own website, YouTube, blog content, or communities.

  5. No reposts or rehosted content: Share only the original source of an article, unless it's not available in English or requires logging in (like Twitter). Avoid reposting the same topic from other sources.

  6. No editorializing titles: You can add the author or website's name if helpful, but keep article titles unchanged.

  7. No piracy or unverified APKs: Do not share links or direct people to pirated content or unverified APKs, which may contain malicious code.

  8. No unauthorized polls, bots, or giveaways: Do not create polls, use bots, or organize giveaways without first contacting mods for approval.

  9. No offensive or low-effort content: Don't post offensive or unhelpful content. Keep it civil and friendly!

  10. No affiliate links: Posting affiliate links is not allowed.

Quick Links

Our Communities

Lemmy App List

Chat and More


founded 1 year ago
MODERATORS