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
[CHINA PHONE] - How to modify backup file of Android system <3e>.. Help me Plz..
Dear All..
My phone was brick when I modify a build.prop file.
That is a china phone, and I can't find any rom or data backup on internet.
The phone have Android system recovery <3e>. The system can't backup and create to ***.zip file type, it just create to ***.backup file type.
So I now have a userdata***.backup file ( include fail build.prop), and build.prop file ok.
Can anyone help me to modify the backup file by build.prop file ok..
This is my backup file:
mediafire.com/download/ac1ldbk5d6ary7v/backup.rar
I really looking forward to your help.
Thanks ..
I've been trying to get my device into dsixda kitchen but can't configure the edify file. Can someone tell me how to make it? Also there is a partition called "konka". What is that? I have attached the dumchar_info, mounts and emmc files from proc folder of stock rom and the updater script from a working custom rom I found online. My phone is Symphony Xplorer W128 bulid.id= W128. It runs on the mtk6582 chipset.
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
Hello, after a lot of struggle i successfully repack system.img
but my file is in system.img.ext4 before extracted and its repack in system.img not in EXT4 ,so its not flash-able ,its says in odin (invaild dev type etc ,) while i trying to flash
so kindly share your experience is that the problem is EXT4? i mean its need must in EXT4 img ? if yes so how can i repack it again in ext4 ? or how can i change img. to img.ext4?