I cannot find a method in Linux or Windows that will allow me to access the files in the system.img partition image from:
RUU_ENDEAVOR_U_ICS_40_hTC_Asia_SEA_WWE_1.29.728.12_Radio_1.1204.105.14_release_261350_signed.exe
I have never had a problem "unpacking" system.img files from other HTC phones using unyaffs or even in Windows with WinImage for EXT2/3/4 partitions.
Obviously many Devs have had success with the HOX system.img! Could someone please tell me what file system the system partition uses AND/OR reveal the correct approach to accessing the files within the img?
I presume the partition formats are identical in:
RUU_ENDEAVOR_U_ICS_40_hTC_Asia_SEA_WWE_1.28.728.9_Radio_1.1204.103.14_release_256493_signed.exe
...so I suppose there's no point in making an attempt with its system.img either!
Any help will be greatly appreciated!!
Thanks in advance.
BTW: I'm not one who asks for assistance as his 1st move.
I have been searching for resolution to this problem for @least a week!
Using appropriate keywords the best I have come up with is either others in this same predicament or suggested remedies which are not effective.
The overall picture I have got is that those with the solution seem reluctant to share the knowledge, which I find strange in development communities.
if you want just access to files inside the img, in windows use this jar attached to convert it to ext4 and then mount with DiskInternals Linux Reader.
or in linux use this tool to unpack.
http://forum.xda-developers.com/showthread.php?p=28837507#post28837507
don't even try to repack it will not work.
if you know how it posible to repack files to this img format please let me know.
Thanks heaps avicohh!
I solved the problem only a few hours before your post came in.
I used a slightly different approach through linux but basically same process & result.
If you follow this:
http://forum.xda-developers.com/showthread.php?t=1081239
you'll be able to unpack AND repack but it's done in linux.
I used Ubuntu 12.04 LTS (64bit) to compile & use the ext4_utils in the thread above.
Since you were so kind to answer my query please feel free to PM me if i can help you!! My use of the forum is sometimes sporadic though, unfortunately.
EDIT: Sorry, just realised we both had the same thread! So it doesn't work for repacking?? I'll see if I can find something that works.
Obviously something does but there's not as much free sharing of really useful stuff as I would have expected with this kind of thing.
Yap.. is the same thread.
probably the odin (samsung) img and the stock htc img they not exactly the same format.
i seraching after sulution to this thing because i'm trying to make custom rom to be able to flash on device with stock rom/locked bootloader from the stock recovery like the ruu firmwares.
Related
Hi,
I've been especially interested in getting Linux working on the Desire, and have discovered that the Ubuntu available for the Nexus one will not work. However,
(i cant post the link, but google "Archlinux on the Desire, Chroot inside" and it will be the first result).
is a thread where i followed the instructions and successfully chrooted into Archlinux. Problem is that Arch doesn't have a very large ARM repository - so no X.
There are a few questions i have. Firstly: Is it possible to add the Debian or Ubuntu repo to Pacman (the package manager for Arch)?
Is it possible to install Aptitude (and then add the repository)?
Something else that I am wondering. In the Thread provided, the tar.bz2 extracts to a fully functional chroot - how would one go about preparing Linux like that (for ARM) for another distro?
The problem with the Ubuntu chroot is that it wants to mount a .img. If the contents of the .img were extracted (i don't know how to do this), could it be manually chrooted from a directory instead of a file.
Thanks for readin'
Josh.
You could try putting the contents of the Ubuntu image on the ext partition of your SD.
You could do it quite easily on your phone.
Mount the image somewhere then just cp the files over to the ext partition.
hello, long time I visit this great site, but had never encouraged me to register. I managed to run ubuntu in the desire, following the same tutorial for the nexus one but with some minimal changes. If people are interested I can create a mini howto...
Sorry about english : )
Yes please do XD
Sent from my HTC Desire using XDA App, WHILE SHOUTING AT THE CAT
Yeah, please do!
I attempted to follow the nexus one guide, but i don't know enough about linux to work out why things don't/shouldn't work properly.
So yeah, if you made a guide, it'd be great!
Josh.
Does anyone know how to go about modifying the recovery partition? I've been unable to even extract the files. I can't mount /dev/block/mtdblock2 (in recovery or out of it), and I can't mount a loop back device off any of the recovery.img's..
Any help would be appreciated. Thanks!
*bump* Someone out there knows an answer to this. I can feel it ;-)
I've figured it out more or less. For those of you who stumbled onto this post by searching and are wondering the answer, it appears boot.img and recovery.img are raw images containing a concatenated kernel and ramdisk. The good news is there's a perl script that can extract them, found here under alternative method.
phazen18 said:
I've figured it out more or less. For those of you who stumbled onto this post by searching and are wondering the answer, it appears boot.img and recovery.img are raw images containing a concatenated kernel and ramdisk. The good news is there's a perl script that can extract them, found here under alternative method.
Click to expand...
Click to collapse
Thank you! I've been searching for 2 days on how to access mtdblocks0-3!
I recently did this for the E4GT and have been asked to do it here as well.
I've received a TON of PM's and emails asking how to do this and I've decided to do a write-up for everyone. Now to start off, this does not automatically make you a Super Duper Developer, this does not show you how to make your own TAR ROMs, nor does it show you how to make your own Odin One-Clicks. What it does do is show you how to pull files from those stock leaked/official ROMs so that you can proceed to make yourself into a Super Duper Developer!
In essence if the Developer knows what they are doing they could use this method to extract all the files from the build and could then add them to a ZIP and have a stock odexed ROM within minutes and do it all through Windows! Depending on time I may or may not do a tutorial on that as well...
So let's begin!
We've all seen those pesky TAR.MD5 packages that we can flash through Odin. How often have you wanted to look inside them and see what is inside before flashing? There are several ways to do it and the most common answer requires Linux and Dsixda's Kitchen utility. This tutorial gives you the ability to do that through Windows and without having to extract the full ROM. These instructions are specific to the Samsung Galaxy S3 (all variants) but can be used on most Samsung Galaxy phones.
Each TAR.MD5 release contains multiple files. Each of these files corresponds to a specific partition on your device. These files are formatted to be mounted by your device but not by a computer. We will be converting them from a .img.ext4 partition type to an ext4.img type partition so we can mount them and read them through Windows. For this tutorial we will be opening up the system.img.ext4 (the system files partition).
Before you dive in there are a few things you'll need.
- A PC running Windows.
- A stock TAR.MD5 release. Several are available at www.rwilco12.com.
- DiskInternals Linux Reader (must be installed on the Windows PC). You can download DiskInternals Linux Reader here.
- SGS2toEXT4 Utility available here. *Be sure to extract the JAR file from the ZIP archive.
- 7-Zip available here.
For the rest of the tutorial please visit my site: www.rwilco12.com
Enjoy!
Reserved.
Awesome! First!
Sent from my SPH-L710 using xda app-developers app
great it's work fine with me on windows8
if you let me a noop question
can we cook the rom in this way ? i mean after upack the image we can edit the files or the apk or the font and repack it again as a md5.tar extension
is that possible
regards
IRoN MaN9 said:
great it's work fine with me on windows8
if you let me a noop question
can we cook the rom in this way ? i mean after upack the image we can edit the files or the apk or the font and repack it again as a md5.tar extension
is that possible
regards
Click to expand...
Click to collapse
Unfortunately no. That part does require Linux but this could help simplify the process if you prefer a Windows environment.
رد: [TUTORIAL] How To Extract Files From a TAR.MD5 Stock ROM (SPH-L710)
rwilco12 said:
Unfortunately no. That part does require Linux but this could help simplify the process if you prefer a Windows environment.
Click to expand...
Click to collapse
Relly sad hope that you can develop this threat in the future so we can cook the stock roms anyway thank you very much for your answer
Regards
IRoN MaN9 said:
Relly sad hope that you can develop this threat in the future so we can cook the stock roms anyway thank you very much for your answer
Regards
Click to expand...
Click to collapse
I might have some other stuff in the works for you guys here soon.
رد: [TUTORIAL] How To Extract Files From a TAR.MD5 Stock ROM (SPH-L710)
rwilco12 said:
I might have some other stuff in the works for you guys here soon.
Click to expand...
Click to collapse
I can't wait to see your next work
Hey after installing linux reader on windows it shows mf5 file in HEX manner , it dont convert it in .zip file..
any way to do it?
mjp93 said:
Hey after installing linux reader on windows it shows mf5 file in HEX manner , it dont convert it in .zip file..
any way to do it?
Click to expand...
Click to collapse
You need to extract it from the img file by saving it. After extracting you'll need to package it in a ZIP.
I followed the guide to the t and its saying that the image is invalid. Any ideas?
macasus76 said:
I followed the guide to the t and its saying that the image is invalid. Any ideas?
Click to expand...
Click to collapse
What device and what files are you using?
Using windows Vista x64 the file is a I537UCUCNE3 stock odin image. I created a .img file using ext4 tool you posted but the Linux viewer says invalid
The image here shows my created .img file on the left, the Linux reader on the right and the error in the middle
This tutorial is no good anymore.
Finally !!
I found how do that after to waste a day to search one real solution.
Is only to use the ClassyKitchen free version for windows.
I found it here:
https://forum.xda-developers.com/chef-central/android/tool-classykitchen-android-roms-t3862584
Basically, after to open the program, you will choose "create new project" on the tab "Projects utils", and choose the firmware from PC or from mobile root. So, the program will extract the folders and files to PROJECT/system folder, and you will can access them by windows explorer, including the app folder with all original apks.
I was looking for a way to restore the calculator apk after delete it before to find another to replace it.
[ ].
[OBSOLETE THREAD]
This thread is obsolete. A solution was found, which is posted here:
http://forum.xda-developers.com/g4/help/method-to-root-lg-g4s-model-h735-lg-g4-t3248030
Please use the new thread for discussions.
------------------------
Original thread:
------------------------
Hi,
I have been trying to root the LG G4S (H735), also known as "LG G4 Beat".
I tried two things:
Approach 1
I tried the method posted by konsolen in this thread:
http://forum.xda-developers.com/g4/general/lg-g4s-world-root-lg-devices-t3231759
but it didn't work for me. I tried several times with varying approaches, but the boot process always gets stuck on the LG logo.
Approach 2
I also tried to inject the root as suggested in this thread for the G4:
http://forum.xda-developers.com/g4/help/rooting-lg-h735-g4-beat-t3192491
I've used the Inject_Root_G4.zip from this link, which I believe is the same shared elsewhere:
https://mega.nz/#!BIxUzbqI!nt2YnGnGQlSiBQ-Ar-c-q7oDMIEsg6xd0Kmek-q0clg
And I get the same problem - stuck on the LG logo when booting.
For anyone who wants to reproduce Approach 2 to maybe find a solution:
1. Start up LGFlashTool2014. You can follow instructions in thread by konsolen (see Approach 1 above). You can use his .kdz file as well. Important: Pull out your USB cable as soon as the green letters COMX (with a number instead of X) appear on the phone. My flashtool actually didn't display the progress percentage, but apparently this at 9%. It doesn't matter if you don't see the percentage though, I've verified with this KDZ image that if you pull the cable at the very moment the green letters appear, nothing is corrupted. The phone will still display 0%. Leave it as it is after you unplugged the cable.
2. Kill your flash tool with the windows task manager. After it closed, you can plug the phone back in and open a windows command line in the folder where your Send_Command.exe is (you can download the package in konsolen's instructions which contains Send_Command.exe as well).
3. Open the console to your phone with
Code:
Send_Command.exe \\.\COMX.
(with your number instead of X)
You will have to do steps 1-3 every time you want to get this console, for example to run all the dd commands below.
4. Calculate the dd parameters and backup your system partition into a .img file. There is an excellent guide by dominik-p for how to determine your individual dd parameters:
http://forum.xda-developers.com/g4/help/how-to-determine-dd-parameters-lg-g4-t3184867
5. Keep a copy of your system.img somewhere safe, you can use it to restore your system if something goes wrong. So don't use this original in the next steps!
6. Copy the .img file to a linux system and mount it. I'm guessing who is trying this knows how to do this. Anything you change in the folder you mounted the image on, will be saved in the image. You can then use this updated image to overwrite your original system partition, again with dd (as described in the thread by dominik-p) using your parameters. So here's the crucial bit: You get root access to your system files via linux. When you know the right things to mess with, you can root your phone with the updated image. Injecting the root as done in step 8 is one way to change the system on the G4 in order to root it.
7. [Optional] If you are new to this, you may want to do a simple test before you continue.
Create a testfile (test.txt) on the mounted system partition. Then copy the .img file back to your phone and try to "dd" it back over your system partition.
Then, check if you see the test file on your system partition -- you may have to reboot the phone after the dd command (and log back in with Send_Command.exe) in order to see the updates.
8. Inject root with the Inject_Root_G4.zip on the mounted folder of the image on your linux system. You can follow instructions (Step 2) here:
http://forum.xda-developers.com/g4/general/lg-g4-100-root-success-directives-root-t3180586
9. Copy the new img file to your phone and "dd" it over your system partition, using your own dd parameters.
10. Reboot the phone (you can also just type LEAVE in the Send_Command.exe console).
Now, it should be rooted - if it worked for you!
If it worked for you, that's great. It didn't for me, it got stuck on the LG logo in the boot process again. So I had to write my original system.img back onto my system partition to get the phone back.
I did get the following errors in Step 8 above, though I did try anyway to use the resulting image. The errors may have something to do with my problem, but it may also be because the inject root is for the G4, not the G4s.
Code:
sudo ./autoroot.sh
cp: cannot create regular file ‘operatingtable/lib64/libsupol.so’: No such file or directory
chmod: cannot access ‘operatingtable/lib64/libsupol.so’: No such file or directory
chcon: cannot access ‘operatingtable/lib64/libsupol.so’: No such file or directory
chmod: cannot access ‘operatingtable/bin/app_process64_original’: No such file or directory
chcon: cannot access ‘operatingtable/bin/app_process64_original’: No such file or directory
chmod: cannot access ‘operatingtable/bin/app_process_init’: No such file or directory
chcon: cannot access ‘operatingtable/bin/app_process_init’: No such file or directory
If anyone finds a solution to this, or has any ideas what could be tried, I would be very interested to hear it. I'm new to rooting phones and don't have much experience beyond what I did in the last days.
Cheers
Jennifer
jen.magnolis said:
4. Calculate the dd parameters and backup your system partition into a .img file. There is an excellent guide by @dominik-p for how to determine your individual dd parameters:
http://forum.xda-developers.com/g4/help/how-to-determine-dd-parameters-lg-g4-t3184867
Click to expand...
Click to collapse
Happy that my guide has helped you
As I said here:
http://forum.xda-developers.com/g4/help/rooting-lg-h735-g4-beat-t3192491/page5
Everyone who is interested to inject root must edit the autoroot.sh from the inject.zip and use the correct files from SuperSU
More information about the files:
https://su.chainfire.eu
Maybe you have to use other files. Not the files from the inject.zip
Download the Update-SuperSU zip from http://download.chainfire.eu/supersu
Copy the files you need to the "su" folder of the extracted inject.zip
For information which files are needed read the "update-binary" file from the SuperSU zip.
(located here META-INF/com/google/android/update-binary)
Good luck everyone :good:
Thanks again for the links! I'll try again soon, when I get time for it, and report the results here
By the way, here's the ls -lR of my system.
Ok, no problem, take your time.
I've got also lot of other work to do...
I just read your system.txt (thanks)
According to these lines:
Code:
lrwxr-xr-x. 1 root 2000 13 Aug 24 02:05 app_process -> app_process32
-rwxr-xr-x. 1 root 2000 13588 Aug 24 02:05 app_process32
It seems that the firmware is 32 bit.
More info about your firmware is in /system/build.prop
So you have to take the right lines from update-binary and copy them and edit the autoroot.sh
Please don't ask me which lines. It's a bit difficult... (you have to understand the logic in update-binary)
Then copy the files from the right folder (arm?) to the "su" folder.
Sorry. I'm out now here for the next time. I have a H815 and happy with it.
I think you will find the solution. :good:
Custom Recoverys
Hi All
Are there any custom recovery's for the G4 beat/G4s
Thanks
Thanks dominik-p for your help. Good luck with your other work, don't worry I won't distract you with asking questions You already helped a lot.
benji5688, you can check for official firmware (.kdz file) on this link, pasting your IMEI instead of YOUR-IMEI in the link below.
http://csmg.lgmobile.com:9002/csmg/b2c/client/auth_model_check2.jsp?esn=YOUR-IMEI
I did not find any for mine there, but I did find it on
http://devtester.ro/projects/lg-firmwares/
Which brought me to this link where I could find mine:
http://pkg02.azure.gdms.lge.com/dn/downloader.dev?fileKey=FW703UV132GQAUP7A0ED99N/H73510c_00.kdz
but you should look for your specific model.
jen.magnolis said:
Hi,
I have been trying to root the LG G4S (H735), also known as "LG G4 Beat".
I tried two things:
Click to expand...
Click to collapse
LOL
I did the exact same thing as you, and really the EXACT, I also contacted dominik-p for the same problem you got with the bs. LOL
Was about to do the same thing you did here too just told that to dominik-p lol.
You post is great, well detailled. Hope someone found something
But got something different. my phone is the LGH731 LG G4 Vigor from Videotron in Canada.
If someone need files or system.img LINK
That's not the exact same thing as the post owner but i'm pretty sure the root method will be. (DON'T use this system.img to inject in you H735) it's from a H731 and they don't have the same partition size.
Ha, that's funny, and you got the same problem of course (frozen logo boot).
We will find a solution. It's just a matter of time. I'm a bit pressed for work in the next days but I'll get back into it around mid week. I think the main problem was, as I suspected and also as dominik-p pointed out, we've been using the wrong inject files. And the G4s is 32 bit so obviously it won't work with 64 bit libs.
First thing I'll try is using the other files from the link dominik-p shared. I'll also read the guide and try to understand which files need to be changed to gain root access in general, i.e. learn the basics of how to root. Then I think/hope I'll be able to fix this. And finally get to move all my stuff onto SD and get my storage back
Meanwhile, if you get any new results, let me know.
Cheers
jen.magnolis said:
Ha, that's funny, and you got the same problem of course (frozen logo boot).
We will find a solution. It's just a matter of time. I'm a bit pressed for work in the next days but I'll get back into it around mid week. I think the main problem was, as I suspected and also as dominik-p pointed out, we've been using the wrong inject files. And the G4s is 32 bit so obviously it won't work with 64 bit libs.
First thing I'll try is using the other files from the link dominik-p shared. I'll also read the guide and try to understand which files need to be changed to gain root access in general, i.e. learn the basics of how to root. Then I think/hope I'll be able to fix this. And finally get to move all my stuff onto SD and get my storage back
Meanwhile, if you get any new results, let me know.
Cheers
Click to expand...
Click to collapse
Yes i'm trying this today (the 32-64 bits thing)
Custom recovery
What does this file do though?
Is it a custom recovery or is it the stock rom?
Thanks Benji
benji5688 said:
What does this file do though?
Is it a custom recovery or is it the stock rom?
Thanks Benji
Click to expand...
Click to collapse
It's the stock ROM. It can be used for recovery, depending what your problem is. If you destroyed your ROM by trying to root, you can recover with this.
If you mess with something in your system partition (where the Android OS is installed), you'd need a copy of your individual system partition (like a "backup") to restore. This highly depends on your phone/version, so you have to do this backup yourself. You can follow the instructions with the dd parameters, linked to from the main thread.
Are there any custom recoverys
Hi
Are there any custom recovery available, I want to get Xposed.
Can anyone make one?
Thanks for all the help
benji5688 said:
Hi
Are there any custom recovery available, I want to get Xposed.
Can anyone make one?
Thanks for all the help
Click to expand...
Click to collapse
I far as I know to get Xposed you need to be rooted... Well there is no root method availaible, well you can try the methods that Jen explained here but I doubt they will work... if yes, you lucky ****
Is the g4s running marshmallow? Is so you would need to use a compatible su install.
Sent from my VS986 using XDA Free mobile app
larsdennert said:
Is the g4s running marshmallow? Is so you would need to use a compatible su install.
Sent from my VS986 using XDA Free mobile app
Click to expand...
Click to collapse
No the problem is really just changing the 64 bits command to make then use the 32 bits ones
I manage everything except this one
Code:
chcon --reference=operatingtable/bin/app_process32 operatingtable/bin/app_process64_original
I agree with xsteacy, this will most likely not work, that's why we opened this discussion
We just have to find the right files to use (instead of the 64 bit ones).
I will get back onto the subject by Wednesday when I have time.
I solved it! My phone is rooted
I asked someone to test my script before I post the results. Hang on there, tomorrow I'll post the solution.
Good times!
jen.magnolis said:
I solved it! My phone is rooted
I asked someone to test my script before I post the results. Hang on there, tomorrow I'll post the solution.
Good times!
Click to expand...
Click to collapse
0.0 OH!?
Ok I'm putting it out there for others to test as well.
Please report if it worked so I can take this into account before updating the main thread instructions.
In the attached .zip file there is a README with instructions.
Note: Thanks goes to @konsolen who shared instructions on how to open the COM port on the H735.
The script in konsolens post is essentially the upater-binary script of the SuperSU package, but with a few modifications.
That may have been necessary on konsolens phone, but it didn't work on mine. For me, using the original script worked.
However, the zip file has to be extracted manually with busybox before the updater-binary script is started. I am not
sure if busybox absolutely needs to be in the /sbin folder, but that's where I saw elsewhere that it belonged, so
I moved it over there in my script. I haven't tested this with busybox being elsewhere.
Thanks goes also to @dominik-p for sharing the link to excellent documentation and for his instructions on how
to make a backup (with dd) of your system, in case anything goes wrong.
UPDATE: I did all commands in root_lgh375.sh manually when I found it already worked, so please report if all is good with the script, but I think it should be, it only does what I did manually.
Congratulations @jen.magnolis
Well done
I downloaded a samsung galaxy s22 Odin firmware and unpacked the zip and the AP tar file and then I un lz4'd the super.img, unsparsed it and then I ran lpunpack on the unsparsed image to get unreadable images
Have you used one of the following?
Extract system.img,vendor.img and product.img from super.img
After lots of search i found a way to extract those img file from super.img What is need? 1.Computer with linux os. extract zip file from this post and place your super.img in same location where you extract.. then run below cmd... simg2img...
forum.xda-developers.com
super_img_lpmake_lpunpack.zip | by MrWaehere for Utilities
Download GApps, Roms, Kernels, Themes, Firmware, and more. Free file hosting for all Android developers.
androidfilehost.com
ze7zez said:
Have you used one of the following?
Extract system.img,vendor.img and product.img from super.img
After lots of search i found a way to extract those img file from super.img What is need? 1.Computer with linux os. extract zip file from this post and place your super.img in same location where you extract.. then run below cmd... simg2img...
forum.xda-developers.com
super_img_lpmake_lpunpack.zip | by MrWaehere for Utilities
Download GApps, Roms, Kernels, Themes, Firmware, and more. Free file hosting for all Android developers.
androidfilehost.com
Click to expand...
Click to collapse
I have. I can get system.img out but I can't open it. I think it's a f2fs partition but I haven't found any tools that can extract files from it
It seems on newer firmware this method of unpacking and extracting system.img out of super.img no longer works. It seems now that when you extract system.img from super.img.raw it gives you a file that reads just as data and does not have the ext4 filesystem magic header bytes.
Have uploaded two screenshots to show how super.img.raw looks and how system.img looks after extraction from super.img. Any thoughts on this?
This firmware is being pulled from latest tar files for SM-S901U
Update, am working on a way and almost got it now. Will probably create a post on this once done and link from here. If you dont hear back from me, i failed. :'(
UPDATE: had some luck following this guys tutorial although a little different was able to extract files. Still cant mount but much closer. Device is f2fs file system. The reason it's not working is most methods on xda are for ext4
How to Extract F2FS Image from Android Device Flash - Baremetallics
How to Extract F2FS Image from Android Device Flash
baremetallics.com
kalexander7 said:
Update, am working on a way and almost got it now. Will probably create a post on this once done and link from here. If you dont hear back from me, i failed. :'(
UPDATE: had some luck following this guys tutorial although a little different was able to extract files. Still cant mount but much closer. Device is f2fs file system. The reason it's not working is most methods on xda are for ext4
How to Extract F2FS Image from Android Device Flash - Baremetallics
How to Extract F2FS Image from Android Device Flash
baremetallics.com
Click to expand...
Click to collapse
Is this also work for other's like erofs?
Mr Hassan said:
Is this also work for other's like erofs?
Click to expand...
Click to collapse
I doubt it although it may be alike using same linux tools like fsck. Erm I'm still stuck on trying to get this f2fs image too mount. It seems corrupt and although I was able to extract libs and apks they're coming out corrupted. Anyone in the community have any knowledge in this area?
kalexander7 said:
I doubt it although it may be alike using same linux tools like fsck. Erm I'm still stuck on trying to get this f2fs image too mount. It seems corrupt and although I was able to extract libs and apks they're coming out corrupted. Anyone in the community have any knowledge in this area?
Click to expand...
Click to collapse
Bro samsung have many dev's to mount fsf2 and already many dude done
The erofs not possible
Mr Hassan said:
Bro samsung have many dev's to mount fsf2 and already many dude done
The **** is erofs
Click to expand...
Click to collapse
what?