It seems that Magisk is more complicated to install now. I did flash the latest version as a zip, as I have always done, but I understand that method is deprecated and suppose it might break or otherwise go way in the future.
The whole process of getting one's boot.img seems complicated for people who are not seasoned ROM developers. Of course I understand there are instructions one can read and learn how to get the boot.img, etc., but given that one has to have a ROM .zip to install the ROM, couldn't an option for Magisk be to extract the boot.img from the ROM .zip if that's what the user has on hand?
Shred00 said:
It seems that Magisk is more complicated to install now. I did flash the latest version as a zip, as I have always done, but I understand that method is deprecated and suppose it might break or otherwise go way in the future.
The whole process of getting one's boot.img seems complicated for people who are not seasoned ROM developers. Of course I understand there are instructions one can read and learn how to get the boot.img, etc., but given that one has to have a ROM .zip to install the ROM, couldn't an option for Magisk be to extract the boot.img from the ROM .zip if that's what the user has on hand?
Click to expand...
Click to collapse
The zip method still works fine for most devices, i still use it on my Pixel 2XL
Download the latest magisk-xxxx.apk, make a copy and rename it to magisk-xxxx.zip, flash via custom recovery
Or
If on Windows 64 Bit, you can use this payload dumper (which doesnt require Python to be installed) to extract the img files, including boot.img, doesnt get any easier:
payload_dumper-win64.zip | Tool by geminids14 for Utilities
Extract payload.bin in xiaomi weekly build zip for MI A1
androidfilehost.com
I still use the zip method as it requires less fiddly steps
73sydney said:
The zip method still works fine for most devices, i still use it on my Pixel 2XL
Click to expand...
Click to collapse
I flashed it on my Oneplus6 (A/B device) running LineageOS 18.1 with TWRP and it worked, but it did not survive an OTA update, which I guess is topjohnwu/Magisk#3820. I was wondering if that not surviving an OTA update was one of the reasons ZIP flashing is being deprecated.
73sydney said:
If on Windows 64 Bit,
Click to expand...
Click to collapse
Not. Am on Linux.
73sydney said:
you can use this payload dumper (which doesnt require Python to be installed) to extract the img files, including boot.img, doesnt get any easier:
payload_dumper-win64.zip | Tool by geminids14 for Utilities
Extract payload.bin in xiaomi weekly build zip for MI A1
androidfilehost.com
I still use the zip method as it requires less fiddly steps
Click to expand...
Click to collapse
Understood. And I understand the palaver one needs to go through to use the boot.img patching once one has a ROM ZIP. It just seems that that is all something that could be baked into the Magisk Manager to make the whole process a bit less of an ordeal.
where can download boot.img
I downloaded the rom for A8+ from: https://www.sammobile.com/samsung/g...e/SM-A730F/BRI/download/A730FXXU7CUI2/1583269
but after unzipping, I don't see the boot.img file.
YT_iceice said:
where can download boot.img
I downloaded the rom for A8+ from: https://www.sammobile.com/samsung/g...e/SM-A730F/BRI/download/A730FXXU7CUI2/1583269
but after unzipping, I don't see the boot.img file.
Click to expand...
Click to collapse
For installing Magisk, you should patch the whole AP.
For detailed instructions visit the Magisk website with good documentation.
If you still want the boot.img .... then unzip the AP by first removing .gz.
Ok
serach for a Payload dumper
Ive been searching for ages and still havent found how to install twrp on my a33, is it even possible? Im trying to root my a33 with magisk but i need twrp. Im stuck and i dont know what to do
I've rooted through Odin by following this post https://forum.xda-developers.com/t/are-these-rooting-guides-for-the-samsung-a33-5g-good.4475163/ but I'm waiting for TWRP to install custom rom too...
ive rooted my phone with magisk by using odin and a patched ap file by magisk, i installed my official software back because magisk kind of slowed down my devices, but now im waiting for twrp so i can install lineage os
Is TWRP the onl way to install lineage OS?
yes i guess
Dryfty said:
ive rooted my phone with magisk by using odin and a patched ap file by magisk, i installed my official software back because magisk kind of slowed down my devices, but now im waiting for twrp so i can install lineage os
Click to expand...
Click to collapse
how do you want to install Lineage OS? There is still not version of Lineage for A33
you can only get lineage on a33 if you have twrp but a33 doesnt "support" twrp
Dryfty said:
you can only get lineage on a33 if you have twrp but a33 doesnt "support" twrp
Click to expand...
Click to collapse
there is an experimental version of TWRP working, I am using it
Arcangel3 said:
there is an experimental version of TWRP working, I am using it
Click to expand...
Click to collapse
on the a33? can you explain how to install it
Dryfty said:
on the a33? can you explain how to install it
Click to expand...
Click to collapse
attached to you here. Bear in mind it is experimental, but it might work
EDIT: deleting it because it is unstable version, a stable version will be released soon by @Zillion (no pressure )
Arcangel3 said:
attached to you here. Bear in mind it is experimental, but it might work
Click to expand...
Click to collapse
Hey, thanks for sharing! Could you say what's the best custom ROM for this device for the moment? Or where is the list of ROMs? thanks!
vovaxxxx said:
Hey, thanks for sharing! Could you say what's the best custom ROM for this device for the moment? Or where is the list of ROMs? thanks!
Click to expand...
Click to collapse
there is none yet.
But some poeple said that stock ROM for A33 is good enough to not need a custom ROM.
Arcangel3 said:
attached to you here. Bear in mind it is experimental, but it might work
Click to expand...
Click to collapse
Give credits to the guy that made it
Zillion said:
Give credits to the guy that made it
Click to expand...
Click to collapse
I am not sure who made it, was it you? hehe
Dryfty said:
Ive been searching for ages and still havent found how to install twrp on my a33, is it even possible? Im trying to root my a33 with magisk but i need twrp. Im stuck and i dont know what to do
Click to expand...
Click to collapse
bro try this way to root
I want to root my A12 but it not work for my phone.please send me a latest version for A127FXXU7BVI1 isBaseband version
I want to root my A12 but it not work for my phone.please send me a latest version for A127FXXU7BVI1 isBaseband version
forum.xda-developers.com
Arcangel3 said:
I am not sure who made it, was it you? hehe
Click to expand...
Click to collapse
Yup, it got its reasons to not be released.
Zillion said:
Yup, it got its reasons to not be released.
Click to expand...
Click to collapse
should I delete it?
Do we have any better version now?
@Zillion any progress with a relesable version???
Arcangel3 said:
@Zillion any progress with a relesable version???
Click to expand...
Click to collapse
I don't own A33 and I don't know how to make any progress on this :c
I managed to get the Lineage OS "Light" GSI version by AndyYan https://forum.xda-developers.com/t/gsi-13-lineageos-20-light.4509315/ and it works well, but the process to install it is pretty involved and if you do anything wrong, you can easily soft-brick your phone. This process should also work for other gsi roms
First Download the Latest Version of Lineage OS "Light", of which the download link can be found in the thread above or here https://sourceforge.net/projects/andyyan-gsi/files/lineage-20-light/ (There are three versions, vS "Vanilla with Superuser installed" vN "Non-SU Vanilla" and gN "Non-SU with GApps") If you want root, I suggest choosing one of the Non-SU versions and patching the stock AP tar with Magisk before starting this process as the Superuser version provides you a generic superuser app and installing magisk with it greets you with a abnormal state message every time you launch the Magisk Manager.
Second: Unpack the downloaded tar file using 7zip if on windows or with the tar command on linux, and then rename the unpacked .img file to system.img
Third: Get the stock firmware for your device using samloader or some other Samsung firmware downloader and unpack the archive file you get to a directory
Fourth: Unpack the AP tar file, you should get a bunch of files in .img.lz4 format.
Fifth: Find the super.img.lz4 file and decompress it using https://github.com/lz4/lz4/releases and this command
Code:
lz4.exe -d super.img.lz4 super.img
From this point onwards you are better off on linux (I've only tested this on Ubuntu WSL so far), if you're on windows 10+, I suggest enabling Windows Subsystem for Linux and downloading and running the Ubuntu distro from the Microsoft store, you can google how to do that.
Sixth: Within Linux (Ubuntu in my case), install the "android-platform-system-core" package using your preferred package manager (I know that package is available on Ubuntu, but I haven't researched whether any other linux distro has that package available). The main thing we want from that package is the shell script "simg2img" as the super.img is currently sparsed (compressed using the Android Sparse image format).
Seventh: If you already did the steps so far in Linux, just go to whatever directory you have the super.img stored, otherwise if you did everything in windows and have a Ubuntu WSL distro ready, you can copy the super.img directly into the ubuntu distro by going into file explorer and scrolling all the way to the bottom of the navigation pane till you see Linux, of which you can expand to find a Ubuntu network share folder, expand that and drag and drop the super.img into your root folder, as well as the system.img file (renamed gsi rom file).
Eighth: Unsparse the super.img using the command:
Code:
simg2img super.img *whatever*.img
This will give you a raw disk image of super.img that's about 9-10 gb. You can name the output file to whatever you want as long as you can discern which img is which, in fact after running the command you can delete the original as you no longer need it.
From here is where the process gets a bit tricky and I fully recommend reading through this guide: https://forum.xda-developers.com/t/...are-binary-3-may.4053065/page-4#post-82241115
Ignore the fact that the thread is for the Galaxy a51 as the steps work for the a33 as well. When you get to the point where you've unpacked the Super.img, copy the GSI system.img over the stock one.
Now the part that can easily cause you to mess up is that when repacking super.img, you have to get the size of each file, including the unsparsed super.img and input the size in bytes of each file in place of what is given in the long command used to repack the image. The numbers you have to change are as follows:
--device super:4294967296 (Change to the file size of super.img)
--group main:4293513600 (Calculate the sum of the size of each of the .img files that were contained in the super.img, minus product.img as that's not needed)
--partition vendor:readonly:342155264:main (Change to the byte size of your vendor.img, same goes for system, odm and vendor_dlkm. Not sure if vendor_dlkm is required as it's not shown in the guide, but just to be safe, I'd recommend adding that in the same format as shown above for vendor just change vendor to vendor_dlkm)
File sizes can be acquired using the command:
Code:
ls -l
Another thing to note is that all of the file sizes must be divisible by 512 as that's the block size the img uses, if they all are, then you're good to go, if one or more aren't you're probably dealing with a corrupt file or that one of the img files is sparsed or compressed in some way. Once you've confirmed the file sizes are good, run the command. You can ignore the "Invalid sparse file format at header magic" message as it doesn't seem to mean anything bad for the process. You don't have to worry if the sparsed image file size is divisible by 512 as it more than like won't be evenly divisible as the file is compressed now.
Once that's done you can take the new modified super.img (make sure it's named that) out of the linux distro and back to windows.
Recompress the super.img back into super.img.lz4 using the command:
Code:
lz4.exe -B6 --content-size super.img super.img.lz4
Now package the super.img.lz4 file with all of the other files from the AP back into a tar file, I suggest using the tar-md5-script-tool.zip from this thread https://forum.xda-developers.com/t/...sing-odin-without-twrp-phh-lineageos.4114435/
At this point, you can skip to step 24 on that guide and continue from there to install the custom rom, just remember to use super.img.lz4 instead of system.img.ext4.lz4, also ignore the .ext4 part, I think that's a device specific thing and the a33 from what I know doesn't have that.
Once you're done and you've booted up after flashing with ODIN, you should be greeted with the lovely Lineage OS Boot Screen
Bare in mind this is a barebones rom and many features may not work as intended since it's an unofficial build of Lineage OS and is intended to work with many devices without too many issues.
Working GSI TAB A8 SM-X200
BUGS: i don't know you tell me?
Instructions:
From OEM stock firmware with root installed
Download the DSU Loader by VegaBobo make sure to download release.apk.
once installed open the app click Select a GSI File to be installed.
once that's done it will ask you to select a folder on where you want it to be installed to for this i just created a folder called gsi in the main directory
then once i have created the folder select the .xz or .gz or .img
and then after that make sure you change your userdata size to around 18gb or 20 if you want space for some apps!
and for the last bit all you have to click on is install gsi via DSU and from there it will do its work
Also make sure your running firmware: X200XXU1AVG1
Remember this gsi is only temp and will not replace your main android system
Downloads:
GSI ROMS: https://github.com/phhusson/treble_experimentations/wiki/Generic-System-Image-(GSI)-list
Official GSI from google: https://developer.android.com/topic/generic-system-image/releases
DSU Downloader: https://github.com/VegaBobo/DSU-Sideloader
Credits to :https://github.com/VegaBobo
I'd love to use this but the A8 and it's tiny storage space prevents DSU from even being installed
kevinco1 said:
I'd love to use this but the A8 and it's tiny storage space prevents DSU from even being installed
Click to expand...
Click to collapse
rip
Should I use ARM64 or ARM64 binder ROM?
You have to be running X200XXU1AVG1 in order to get DSU to work? Just upgraded to Android 12...
Wich android 13 gsi work?
How did you get DSU to work on this device? The storage limitations have always prevented me from using this method
which gsi should i use for tab a8(ARM64+GMS or ARM64) ?
thaovd1712 said:
which gsi should i use for tab a8(ARM64+GMS or ARM64) ?
Click to expand...
Click to collapse
If you want the google services, you need GMS.
WackyHacky1 said:
rip
Click to expand...
Click to collapse
can you downgrade from stock 12 to gsi 11?
So, after wandering for a while at another forum, i found something that might be interesting since this guide is meant to create cusrom for the X3 GT which using same dimensity family as rn105g/m3pro5g
This article is not for complete beginners, but for those with some experience in compiling AOSP!
If you want to build custom ROM for POCO X3 GT for yourself
Follow the instructions on the AOSP website to set up your workstation or server. You know how to do that, right?
first, clone this repo git clone https://github.com/ShivamKumarJha/android_tools
, You need it to get some of the binaries you need
then, download the MIUI V13.0.4.0.SKPMIXM .I recommend this version because it has a corresponding version of the Fastboot package available for flashing
executing ./android_tools/setup.sh
to initialize the environment
executing ./android_tools/tools/rom_extract.sh
to dump the downloaded OTA MIUI package
After a few minutes, you can get a fully unpacked OTA update in the dump directory. Copy the "kernel" and "dtb" binaries from the boot directory to the base/Global directory in your clone chopin-prebuilts directory and rename the "kernel" to "Image.gz". Rename "dtb" to "dtb.img" (as in the China directory), and don't forget to copy dtbo.img to base/Global
then, use extractor.sh in the newly added Firmware_extractor directory in the tools directory to unpack the MIUI OTA package and mirror it to an empty directory you have created to get vendor.img and copy it to chopin-prebuilts/vendor/Global
Finally, modify USE_CN_AGPS := true
in the last line of aosp_choping.mk to IS_GLOBAL := true
Don't forget to comment out vendor.camera.aux.packagelist
in common/private/property_contexts
in the sepolicy directory of some custom ROMs,it will trigger the bootloop of the device!
Finally, you just need to use the aosp_choping.mk target and you're done
Just asking, this may be quite useful
Source : https://t.me/PocoX3GTglobalupdates
Chopin have dimensity 1000, camelliam 700. Do you u think could be compatible? All gsi stock port of x3 gt i tried dont boot, but maybe is a gsi issue
wetito said:
Chopin have dimensity 1000, camelliam 700. Do you u think could be compatible? All gsi stock port of x3 gt i tried dont boot, but maybe is a gsi issue
Click to expand...
Click to collapse
Of course not, what i meant is instead using the chopin rom use the cammelian rom for getting the required prebuilt kernel and dtb
there's a mindos made forx3 nfc (is the same of gt?)... this is a very good rom. try to port could be interesting
wetito said:
there's a mindos made forx3 nfc (is the same of gt?)... this is a very good rom. try to port could be interesting
Click to expand...
Click to collapse
I guess they're not the same since x3 nfc using Snapdragon, also what is mindos? First time heard about it :/
GrandEsquiRE said:
I guess they're not the same since x3 nfc using Snapdragon, also what is mindos? First time heard about it :/
Click to expand...
Click to collapse
It's true not the same, it's a shame