Today I face problem about root this device after install custome recovery the device turn to white screen so I dcided to do more resarch about android now I repack the system and out SU in xbin and superuser.apk in app now I want to repack to ext4 system and repack to tar via program izarc
izarc cand add files to tar bulid my system now is about 900mb
anyone have soulation can share with me please
Related
Does anyone know what file system or method to unpack (and repack) the stock rom .img files? It is not yaffs (no surprises there) or ext4 img.
Hi guys, I could successfully unpacked and repacked system.img on 4.0.4 for my Galaxy S III by learning from xda, add root files, delete unnecessary system apps, etc, and using "tar -cvf ...." to make an tar pack to flash with ODIN, thx to all xda developpers.
But when I did this again on new GSIII 4.1.1 firmwares like DI2, My phone jammed in the 2nd screen, could someone help me?
Here is what I did on 4.1.1 firmwares in Ubutu, just like what I did on 4.0.4
1. unpack system.img from tar files
2. exchange system.img to system.img.ext4 in Ubutu
3. unpack system.img.ext4 with
Code:
mkdir systest; mount -o rw,loop system.img.ext4 systest
oh just forget the folder name.
4. modify the files in systest folder blablabla
5. repack system.img from systest folder using
Code:
sudo mkuserimg.sh -s systest systest-new.img ext4 temp 1536M
6. then make a new tar file to flash with recovery.img, hidden.img etc.
This tar file could be flashed with ODIN successfully, but like I said above, my phone didn't response in the 2nd screen with Samsung logos, I've wiped userdata in stock recovery but it didn't work.
Then I didn't modify any files, just unpack and repack system.img, flash it with ODIN, my phone remains the same
Could someone kindly to figure it out what I did wrong on new 4.1.1 firmwares? Is it about Samsung file format in 4.1.1?
Oh no replies until now...:crying:
I tested other 4.1.1 firmwares, unpack and repack system.img, then zip into new tar file, flash it, also stuck on the Samsung Logo with vibration
but it worked on all 4.0.4 firmwares
Hello,
i have a Wiko PULP 3G, without a working root method.
I take a look at the Firmware files, there seems no CRC Protection. Even a Satellite Receiver or a TV Firmware have such.
I changed Text in the image with a HEX Editor(ro.sys.usb.storage.type) to get Massstorage. I flashed the modified image.
The Program just done it. Okay i have still no Massstorage. But on the Mobile i can see the build.prop has really changed
like i edit it.
I wonder if i can change Textfiles, it may possible to mount system as r/w.
Its a 1.9GB image difficult to find the Init/fstab.
Questions:
1. What do i need to modify to get mass_storage ?
2. How are the typical Textlines for a phone to make system read-only?
3. If i have write access to /system i can put a "su" file(any?) to system install SuperSU and have root?
Okay i have modified a boot.img, repack it and flashed it.
I set ro.secure=0, ro.debuggable=1 and massstorage in build.prop.
I got masstorage )))))
But how do i get the su to xbin. In the extracted Boot.img or Recovery.img there is no xbin.
Other .img files cant be xtracted.
With adb push this dont work, no permission.
Ideas?
If this is a raw system partition ext4 image, you can just mount it (with -o loop) on your Linux PC and modify the contents.
_that said:
If this is a raw system partition ext4 image, you can just mount it (with -o loop) on your Linux PC and modify the contents.
Click to expand...
Click to collapse
Thanks, but its not a raw image. I think its Android Sparse Image Format.
Linux cant mount it. Yaffey is not able to handle it.
I wonder why there i no tool where you can put a Firmware in and click on "Root it" and ready is the new one?!
Now i found tools to depack/pack the system image.
But the Phone dont boot, it starts and restart in Recovery.
If i do a root filecheck in Recovery it says 1 file added and 1 file changed - FAIL.
There must be something like a modify protection
DELETED
recovery.img needed
nalas said:
Hello
I have a question to devs:
I have stock rom with system.img, boot.img and recovery.img files.
I want to add root access into the rom, but with kitchen I can add supersu.zip file and do flashable rom zip file for all.
The problem is with no custom recovery on my device - I can flash only via SPD flashtool so I need raw file like system.img , boot.img and recovery.img
Anybody knows how add root and compile system.img with root? so I can flash via SPD flashtool?
I tried add su , superuser.apk and busybox but not works - after reboot I opened supersu app and had binary install error .
PLS Help.
Regards
nalas
Click to expand...
Click to collapse
assuming u r having a mediatek mobile i can help u build a custom recovery twrp..... send me ur chipset name and recovery.img file
DELETED
DELETED
DELETED
I need someones copy of it im on samsung one ui pie s8 plus unlocked exynos please help i have no bootanimation binary file from system/bin
Can someone send thiers please i really really need help
Just download the Odin flash archive and extract it from there. (system.img is ext4 fs)