yashsingh1/xdaforums huggingface dataset:
[HTC Excalibur] BigFellor:
Well, I am still having the same issue. Seems to only happen when I use resource heavy apps like IE or Windows Media (listen to the radio at work a lot now that I figure out how to, thanks to this site). But, if I press the Home key, and the lock the phone, I can unlock it and everything is fine. Oh well, I like STK, so I'll keep it.
[HTC Excalibur] jdoggraz:
Oh what issue... Oh and if you are using IE it is a memory hogger so that is the problem. I would suggest using opera mini... Download it HERE... And then run it through your phone, it is actually a java running program meaning that it will not hog a lot of memory. Plus it is a lot faster then IE... this should resolve the problem of having less memory... You should see the difference.
[HTC Excalibur] Ryanmo5:
Your right on there, i have ie and opera 8.65 on phone and both hog memory, opera mini is the best and lightning quick!
[HTC Excalibur] kikeman:
Thanks jdogg, its working fine really good
[HTC Excalibur] BigFellor:
See post #1

Ok, downloaded and tried Opera Mini. I like it. Takes some getting used to, but it is much quicker than IE. Now another question ... with IE, if I go to HERE and click on the "STREAM 20k mono" link, it automatically opens up Windows Media to play the radio station ( I get bored at work). Opera doesnt seem to know how to handle this, is there a way to set up opera to handle it right, or can I save this URL somehow in Windows Media? Thanks for the help guys
[HTC Excalibur] jdoggraz:
I wish I could help you but I am fairly new to opera as well, maybe someone will be willing to help. And I am glad that you like the Opera... Did you notice a difference especially in the memory of your phone as you are running opera.
[Android Q&A, Help & Troubleshooting] Prince Rabiul Islam:
I need twrp recovery file for Infinix note 5. There is a website named basketbuild.com, it doesn't respond. So I can't download from there.

Without pc, how to unlock bootloader on Infinix note 5?
[Android Q&A, Help & Troubleshooting] josephogaga:
Good day,pls I TWRP file in Infinix note 5(x604)
[Miscellaneous Android Development] bigrammy:
Yet Another great tool!! :highfive:

Thanks!
[Miscellaneous Android Development] munjeni:
I'm not one of those who make paid software and promote on xda, my work is always free. Even I'm always providing source code for free, source code of this tool is here -> https://github.com/munjeni/super_image_dumper , enjoy! ;)
[Miscellaneous Android Development] bigrammy:
You are the best and I and many others thank you for make life so easy for us. :highfive:

PS: I will send you a PM with something you may find interesting and useful. :fingers-crossed:
[Miscellaneous Android Development] paijoe88:
Can I make this tool for remake oem.sin?

I have fw Xperia docomo bundling,and many bloatware,so I wont to remake oem.sin and deleted any bloatware, can I?

??sorry my English por????
[Miscellaneous Android Development] munjeni:
No you can't. Tool is unpacker only, it extracts oem from super image but doesn't reconstruct it back to super image. Even there is no known tool to make valid sin back because of signature.
[Miscellaneous Android Development] munjeni:
Seems readonly partitions like oem, system, vendor...etc can be set to read-write mode via LP_PARTITION_ATTR overiding LpMetadataPartition.attributes 1 with 0. Anybody tried android version of this tool? E.g. dump block device e.g. /dev/block/bootdevice/super

RO flags (0x1), when it is set to 0x0 its RW mode, but header sha256 checksums of the LpMetadataGeometry and LpMetadataHeader also need to be modified in case we overvrite flags with RW mode!
[Miscellaneous Android Development] munjeni:
Removed fake pie binary and made new true pie 64 bit binary for android. With it you can dump your super partition on your own phone e.g.

adb push superunpack.arm64_pie /data/local/tmp

adb shell
su
cd /data/local/tmp
chmod 755 superunpack.arm64_pie
./superunpack.arm64_pie /dev/block/bootdevice/by-name/super

and whola all ext4 partitonins from your super partition is extracted to the /data/local/tmp folder. :)
[Miscellaneous Android Development] lebigmac:
bump. Any news regarding forcing system to be read/write in Android 10 ?

Thanks for your hard work @munjeni
[Miscellaneous Android Development] munjeni:
See post 8.

In most case if you change those byte vbmeta protection will do a bootloop, so I think no way to set it to force rw except if you unlock bootloader and disable vbmeta protection trought fastboot (more info -> https://xdaforums.com/t/tool-newflasher-xperia-command-line-flasher.3619426/post-84509179)
[Miscellaneous Android Development] lebigmac:
I replaced all 4 occurences of these three bytes in my super.img like you suggested and flashed it to my phone.

It didn't boot probably due to the invalid sha256 checksums as you predicted.

Which bytes I must hex edit in the extracted system.ext4 in order to make it rw? I was thinking maybe the shared_blocks feature?
[Miscellaneous Android Development] munjeni:
You should read this to get idea -> https://ext4.wiki.kernel.org/index.php/Ext4_Disk_Layout

TO be honest I never modified RO partitions. it can be probably done using parted, fsck and similar tools so you no need to do it by hexediting, try google a bit for idea I realy don't know
[Miscellaneous Android Development] lebigmac:
@munjeni thank you so much for writing this amazing superunpack tool!

Thanks to your program and thanks to another tutorial I was able to create an automated bash script that transforms all read only partitions inside super.img (system, vendor , product, etc...) into read write-able partitions again and then flash to device as a brand new super.img.

HERE is the link to new universal version
[Miscellaneous Android Development] bynarie:
Wow, this is pretty impressive my friend. Big props!! Just curious, what's the difference with "this" utility(superunpack) and the standard android lpunpack?
[Miscellaneous Android Development] munjeni:
Diferencie is that my tool not use any external dependencies so can be build easily as a static binary. Seccond diferencie is its easy to use, just drag and drop file to extract. I'm not tried lpunpack so I can't tell the exact diferencie, you tell me :)
[Miscellaneous Android Development] lebigmac:
lpunpack:

works with sparse files

creates .img files

gives zero text output so you don't know what's happening under the hood

extracts all partitions even the empty ones

Superunpack:

works with raw files

creates .ext4 files

gives lots of text info so you know exactly what's going on

only extracts the partitions that are not empty

These are the main differences that I noticed.
[Miscellaneous Android Development] BlazingKahn35:
Hey friend I get this error can you help me out?

[Novice alert]
[Miscellaneous Android Development] bynarie:
Nice !
[Miscellaneous Android Development] bynarie:
Good stuff, thank you!
[Miscellaneous Android Development] munjeni:
Version 15 is out!

Changelog:

- version 15 (08.05.2021) use libselinux to determine and set selinux to permissive mode instead of popening getenforce-setenforce tools since some devices might miss those tools
[Miscellaneous Android Development] Luix333:
Thanks for trying to help

I don't get anything back. It just goes through. (if I do it before "su" I get "Couldn't set enforcing status to '0': Permission denied"
[Miscellaneous Android Development] munjeni:
Try version 15 and let me know. Please post log from superrepack window!
[Miscellaneous Android Development] Luix333:
Thank you for your quick response!

I'm now getting "Unable to open /dev/block/bootdevice/by-name/super!"

when I adb pull /data/local/tmp/script.log, it seems to be an empty file. What method should I use to read it?

Thank you again for your awesome support!
[Miscellaneous Android Development] munjeni:
You must know the name of the super partition device, on Sony devices its /dev/block/bootdevice/by-name/super but on your phone seems diferent, ask somebody for SM-G980F
[Miscellaneous Android Development] Luix333:
Thanks! I figured the partition is /dev/block/by-name/super on my device.

I'm now getting this when I run ./superrepack /dev/block/by-name/super :

resize2fs 1.45.4 (23-Sep-2019)

/data/local/tmp/resize2fs: I/O error while trying to open /dev/block/loop27

e2fsck 1.45.4 (23-Sep-2019)

/data/local/tmp/e2fsck: I/O error while trying to open /dev/block/loop27

This is in the log file:

The superblock could not be read or does not describe a valid ext2/ext3/ext4

filesystem. If the device is valid and it really contains an ext2/ext3/ext4

filesystem (and not swap or ufs or something else), then the superblock

is corrupt, and you might try running e2fsck with an alternate superblock:

e2fsck -b 8193 <device>

or

e2fsck -b 32768 <device>
[Miscellaneous Android Development] munjeni:
Please post superrepack log fully otherwise I can't gues whats going on, I allready told you that in post 206
[Miscellaneous Android Development] Luix333:
I was able to fix my issue, but thank you very much for your help!!! Keep up the amazing work!
[Miscellaneous Android Development] munjeni:
What was issue?
[Miscellaneous Android Development] munjeni:
Do in mind if you have rw but filesystem is not repaired yet your device might not work as expected because of filesystem errors! Your script.log must not contain errors otherwise you are not done things right!!! Further question without log and I will not comment and waste my time, we allready spent hour on this without real workaround because you didn't follow post 206
[Miscellaneous Android Development] pandavova:
Hey @munjeni, here's my script.log and my cmd output window log! I did run it one time, but I didn't reflash my orig. super image after the failed v13 attempt.

Are there still some errors?

Man, my device is now stuck at the Sony log, not a bootloop, it's just stuck. I will wait for your answer before reflashing the orig. super image.

(zipped because the log is too large)
[Miscellaneous Android Development] yoshijulas:
Hi, i tried using the tool superrepack, but it stops here, i dont know what to do

dandelion:/data/local/tmp # /data/local/tmp/superrepack /dev/block/mmcblk0p38

/system/bin/sh: /data/local/tmp/superrepack: No such file or directory

I already chmod 755 ./superrepack and also chmod +x ./superrepack, still doesnt work

thanks
[Miscellaneous Android Development] munjeni:
rename superrepack.arm64_pie to superrepack first!
[Miscellaneous Android Development] munjeni:
You need to run tool many times (4 to 5 times) untill folowing error disapear:

clone_file: Could not allocate block in ext2 filesystem

This is figured out in version 14 and up. If you used earlier versions and it failed you probably need to reflash your rom because your filesystem is not repaired yet its corupt. So reinstall rom, run latest version and carefully read main window of the tool so when all errors disapear than simply take a look inside script.log to make surre no error there too and you are done.
[Miscellaneous Android Development] yoshijulas:
I already did that, i have the superrepack file, with that exactly name, but still, i get that error
[Miscellaneous Android Development] bobbyp1086:
Version 14 ran it 3 times errors were less and less on the 4th screen froze and flashed every couple seconds. Phone went to reboot but soft bricked. Had to manually flash each partition as the recovery couldn't factory reset and software couldn't rescue. Just got back up and going
[Miscellaneous Android Development] pandavova:
So yeah, it doesn't work. My device is again stuck at the Sony logo.

I executed the script till I saw no change in the log/ cmd window. I attached the logs.
[Miscellaneous Android Development] munjeni:
You say screen? I told that on the first post that "stop" command must be sent to device before use our tool! When you do "stop" device get into black screen and all activity is stopped, but since you say that your device flashed-blinked thats indication that you didn't folow command from the first post. Version 15 is out, you should use 15 instead of 14. Further without logs and I not going to waste my time!
[Miscellaneous Android Development] munjeni:
/system/bin/sh: /data/local/tmp/superrepack: No such file or directory mean that superrepack is not inside /data/local/tmp directory or your android missing some libraries. Libraries needed for our tool is:

Interpreter '/system/bin/linker64'

Needed Library 'libcrypto.so'

Needed Library 'libc.so'

Needed Library 'libm.so'

Needed Library 'libdl.so'

if you have missing any of those I can't help. If you can't get it to work you should try https://xdaforums.com/t/script-android-10-universal-mount-system-read-write-r-w.4247311/
[Miscellaneous Android Development] munjeni:
I don't see any error in your logs, is your device bootloader unlocked?
[Miscellaneous Android Development] pandavova:
Yes, it is.
[Miscellaneous Android Development] munjeni:
I have no idea. Maybe boot image need to be repacked because of permannent dm-very? You should try this https://www.androidjungles.com/disable-dm-verity-or-android-verified-boot-without-twrp/ before my tool!
[Miscellaneous Android Development] pandavova:
???

"Install Magisk like you normally would"

Im flashing the magisk boot image already with fastboot. There is no option to "preserve AVB 2.0/dm verity or Preserve force encryption"
[Miscellaneous Android Development] munjeni:
Than I'm out of ideas, did you tried https://xdaforums.com/t/script-android-10-universal-mount-system-read-write-r-w.4247311/ ??
[Miscellaneous Android Development] pandavova:
snip
[Miscellaneous Android Development] pandavova:
Yeah, that tool also doesn't work for my device.
[Miscellaneous Android Development] munjeni:
Whats your device and rom version?
[Miscellaneous Android Development] pandavova:
Sony Xperia 5ii, XQ-AS52_EEA_58.1.A.5.159, Android 11.
[Miscellaneous Android Development] munjeni:
Can you give me boot image?
[Miscellaneous Android Development] pandavova:
Stock img: https://drive.google.com/file/d/1ZSz-CvtVdEKOP3uxIXHWPDF8axYXl8yp/view

Magisk img: https://drive.google.com/file/d/1HyQfEKFus_QYrn4snKtMwIG50MhjjKEA/view

There is a weird thing with the image going on so you need to edit something if you want to do it yourself, you can read more about it here: https://github.com/topjohnwu/Magisk/issues/3752
[Miscellaneous Android Development] munjeni:
Which one you have running currently?
[Miscellaneous Android Development] pandavova:
Magisk, obviously.
[Miscellaneous Android Development] munjeni:
Ok I will look into fstab f those image and try disable verity
[Miscellaneous Android Development] munjeni:
I will delete all avb lines from fstab and make you modified image
[Miscellaneous Android Development] munjeni:
Uploading wait please
[Miscellaneous Android Development] munjeni:
Flash this -> https://easyupload.io/unk4zo

fastboot flash boot patched.img

Let me know if it boot first! If it boot than please repeat with superrepack and let me know! If all work I will probably extend my tool a lot or at least write in details what need to be done.
[Miscellaneous Android Development] pandavova:
So I reflashed stock rom, booted one time, flashed the patched image to boot_a and boot_b. Im getting a "Your device is corrupt. It can't be trusted and will not boot. Your device will be powered off in 5 seconds." screen. Flashing the normal Magisk img works and the device boots with Magisk 22.1. If I reflash your patched img it shows me the "Your device is corrupt." screen again.
[Miscellaneous Android Development] munjeni:
That have 3 meaning, your device have avb protection active or I didn't had right mkbootimg tool to make new boot image or fstab avb removal cause bootloop. Did you tried:

fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
[Miscellaneous Android Development] pandavova:
Yeah, I tried it with this empty vbmeta file: https://androidfilehost.com/?fid=2188818919693783115

I don't know if this would be the correct one, I got it from here: https://www.androidjungles.com/download-and-flash-blank-vbmeta-file/

Or do you mean I should try to flash the normal vbmeta with that command?
[Miscellaneous Android Development] munjeni:
I'm not sure since I own xperia 10 which do not have all this featues so I can't test anything. I'm realy tired now with this tool, I will delete it right now.
[Miscellaneous Android Development] pandavova:
noooo don't delete your tool, you are my only hope xDD

just go to sleep or do something else xDD
[Miscellaneous Android Development] munjeni:
You see here is few peoples interested for my tool, and null who want to help, I realy wanted to finish tool but as you see theres no go. Do you have idea how can I repack magisk image? Do you have idea why repacked boot image not boot? Do I need to sign it? I was worked on android 3 years ago, thats long time ago when dm-verity, super partitions and b.s. was not found, in the time when I worked on android mkbootimg tool never caused bootloop, but now I see it produce "Your device is corrupt. It can't be trusted" and to be honest I'm tired of crazy google protections. If you have idea let me know!
[Miscellaneous Android Development] munjeni:
If you want we can test if bootloop is caused by fstab modification or caused by not adequate tool for repacking magisk image, are you ready to test just repacked magisk image without any modification, just repacked? If you are not ready to spend 30 minutes with me now let me know, I no want to wait long replies, allready spent 2-3 hour without figuring anything I simply do not have free time for this anymore, if you are ready let me know! I need to be sure what cuse "Your device is corrupt."
[Miscellaneous Android Development] pandavova:
yeah lets try that out! i am ready to spend time with you! its also in my interest that this tool works :D
[Miscellaneous Android Development] pandavova:
Maybe more infos for you because I don't know what you are doing with fstab. If you didn't read that github link: the magisk img was already repacked one time because if you just flash the boot img with magisk in the app and flash that, it doesn't work. something needs do be commented out for it to work https://github.com/topjohnwu/Magisk/issues/3752#issuecomment-814410901
[Miscellaneous Android Development] munjeni:
Can you confirm magisk22.1_patched_boot_58.1.A.5.159_XQ-AS52_UNTESTED.img boot on your device?? This is how I repacked justrepacked.img (hope somebody tell me what I doing wrong):

rm -rf ramdisk
mkdir ramdisk
cd ramdisk
gunzip < ../magisk22.1_patched_boot_58.1.A.5.159_XQ-AS52_UNTESTED.img-ramdisk.gz | cpio -id
find . -print | cpio -H newc -o | gzip > ../ramdisk.gz
cd ..
mkbootimg --kernel ./magisk22.1_patched_boot_58.1.A.5.159_XQ-AS52_UNTESTED.img-zImage --dt ./magisk22.1_patched_boot_58.1.A.5.159_XQ-AS52_UNTESTED.img-dtb --ramdisk ./ramdisk.gz --cmdline 'androidboot.hardware=qcom androidboot.memcg=1 lpm_levels.sleep_disabled=1 video=vfb:640x400,bpp=32,memsize=3072000 msm_rtb.filter=0x237 service_locator.enable=1 androidboot.usbcontroller=a600000.dwc3 swiotlb=2048 loop.max_part=7 cgroup.memory=nokmem,nosocket reboot=panic_warm buildproduct=pdx206 buildid=EDO-2.1.1-210330-1117 oemboot.earlymount=/dev/block/platform/soc/1d84000.ufshc/by-name/oem:/mnt/oem:ext4:ro,barrier=1:wait,slotselect,first_stage_mount buildvariant=user' --kernel_offset 0x00008000 --ramdisk_offset 0x01000000 --tags_offset 0x00000100 --pagesize 4096 -o justrepacked.img

Device is Sony Xperia 5ii, XQ-AS52_EEA_58.1.A.5.159, Android 11, it boot sucesfully magisk22.1_patched_boot_58.1.A.5.159_XQ-AS52_UNTESTED.img before repack but after repack it produce "Your device is corrupt. It can't be trusted and will not boot. Your device will be powered off in 5 seconds." and I realy have no idea why! This is just repacked image without any modification -> https://easyupload.io/ir46wk

Can you try justrepacked.img and let me know? Anybody tell me which mkbootimg tool is compatible and sure working with xperia 5II ??
[Miscellaneous Android Development] munjeni:
What I done in previous img is removed all avb lines from fstab e.g.

system /system ext4 ro wait,,avb=vbmeta_system,logical,first_stage_mount,avb_keys=/avb/q-gsi.avbpubkey:/avb/r-gsi.avbpubkey:/avb/s-gsi.avbpubkey

to

system /system ext4 ro wait,logical,first_stage_mount

but please let me know this one unmodified -> https://xdaforums.com/t/tool-win-li...s-rw-in-super-partition.4120963/post-84985101 need to know if repack cause bootloop or fstab before I start investigating
[Miscellaneous Android Development] munjeni:
13 minutes is gone and I have 10 minutes left right now untill my pc is off otherwise see you tommorow. Tommorow if we not figure out thing superrepack for sure going to the trash as I have no intention of wasting time anymore
[Miscellaneous Android Development] pandavova:
Sorry for the delay, with the "justrepacked.img" I'm also getting the "Your device is corrupt." screen.

Flashing the "normal" magisk img back lets me boot again.
[Miscellaneous Android Development] munjeni:
Ok thanks, so definitelly repacking without any single modification cause boot loop. I don't know what I need to do since it was long time ago when I used mkbootimg tool. Let see tommorow if somebody help, if not I realy going to delete superrepack... see you tommorow I must go now
[Miscellaneous Android Development] pandavova:
In the Github Issue the person repacked it with android image kitchen, so maybe its because of that?

bye bye ^^
[Miscellaneous Android Development] munjeni:
but is not you said that those one from github (from your download link) boot on your device? I used them as a base for repack
[Miscellaneous Android Development] pandavova:
Yeah it works on my device.

But the original magisk img that you would get if you flash magisk on the boot.img with the app doesn't work. The provided magisk img was already repacked with android image kitchen as stated by the uploader https://github.com/topjohnwu/Magisk/issues/3752#issuecomment-814410901
[Miscellaneous Android Development] f1^ter:
I'll add it on my own.

I tried with v13, and after the first time the command:

./superrepack /dev/block/bootdevice/by-name/super

it gave me an error mounting RW, but when I did it 3-5 times-the error disappeared and all the partitions really showed RW. After the reboot, the system was loaded surprisingly and this is magic. But then a strange thing began, if I, for example, delete an application from the system partition , then when the system is rebooted, the system somehow loads, but system crashes occur, "the user interface is stopped". I understand that the blocks were not properly converted to RW after all? And when you delete it, some of the blocks were broken. I recovered completely and went the same way, but only chose to delete the application from the product section, but when I deleted a couple of applications, then after restarting everything loaded - but the part of the Google application that is in the product-they did not start and constantly gave errors.

We are already making great progress with version 13. But still something is missing, maybe there really is some other check? I remind you that all checks using vbmeta and vbmeta_system were disabled.

Sony Xperia 1 II, FW 58.1.A.5.159
[Miscellaneous Android Development] munjeni:
You should not delete system applications otherwise framowork things which depend on those app will cause system crash, you must know which one can be deleted and which one can't, you must be carefull with it! If your /data/local/tmp/script.log contain NO errors than you are definitelly done things right and filesystem is fully ok, the rest of things you need to figure out byself with help of logcat and I can't tell you which apks is safe to delete!
[Miscellaneous Android Development] munjeni:
I found what cause bootloop! I didn't know that bootimage version header is updated to version 3 but I have old mkbootimg tool, will try compile latest one and make new image for test
[Miscellaneous Android Development] munjeni:
Hi, I'm made new repack with the right tools.

This is repacked and fstab modified -> https://easyupload.io/27e8zp

This one is repacked without any modification -> https://easyupload.io/xa4lnb

If you get it working with modified fstab try superrepack tool and let me know!