*** ##TUTORIAL ...
HOW to Port ROMs...
For Begineers & Advanced Users
Almost Any Device to Any Device!
ONLY FOR MEDIATEK SoCs
In This Guide You'll Learn..
How to Port ROMs From the Same CPU
HOW TO PORT ROM FROM
DIFFERENT SoC!!!!!
Works for-
MT6589 to MT6577
MT6582 to MT6572
MT6577 to MT6575
Only ICS to ICS & JB to JB
May also work with 4.1 to 4.2
No Need of Source Code
No Need of Kernel Source
No Need of **ANDROID KITCHEN
No Need of LINUX...
Requirements:
* A Brain
* Patience
*Es File Explorer or
*Bluetooth File Transfer
*Rom toolbox
* Stock ROM
* And a Little Respect!!
So now Lets Begin...
PORTING For Same SoCs ( Ex: MT6572 to
MT6572)
:good:
Porting procedures rom (MT6589, MT6582, MT6572) (or
vice versa)
Read and follow the steps well both individually correctly:
* Extrack rom port into a folder that is named PORT
* Extrack stock rom into a folder that is named STOCK
* Note both good
* Copy and replace files Stock to PORT as follows:
* System / vendor
* System / usr
* System / lib / modules
* System / lib / hw
* System / lib / libncurses.so
* System / etc / firmware
* System / etc / vold.fstab
* System / etc / vold.fstab.nand
* System / etc / bluetooth
* Open build.prop and find a line of text as follows:
ro.mediatek.platform = MT65xx
(Converted to the type of your device)
example:
ro.mediatek.platform = MT6572
* META-INF/google/android open, then open the updater-
script file using a text editor
* Add this line between the lines of "set_perm"
set_perm (0, 0, 0644, "/ system/vendor/lib/hw/
gralloc.mt65xx.so");
[Replace with your mt65xx cpu]
example
set_perm (0, 0, 0644, "/ system/vendor/lib/hw/
gralloc.mt6572.so");
* Now Go back to the Rom folder and Take the boot.img
and decompile it with any bootimg-unpack tool! (This
step can be skipped)
* Now delete and rename the zImage boot.img-ramdisk
to PORT-Ramdisk
* Now Do the Same for Stock boot.img and open the
folder named PORT-ramdisk and copy all the files from PORT-
boot.img-ramdisk to ramdisk of boot.img Stock Cell
* Now Go to boot.img-ramdisk and open init.rc
* Now find these lines and replace with your cpu
Chip # Create Property
on early_property: ro.hardware = mt6589
setprop ro.mtk.hardware mt6589
on early_property: ro.hardware = mt6589
setprop ro.mtk.hardware mt6589
example
# Create Chip Property
on early_property: ro.hardware = mt6582
setprop ro.mtk.hardware mt6589
on early_property: ro.hardware = mt6572
setprop ro.mtk.hardware mt6589
For Fixing Problems...
*system/etc/permissions
*system/etc/security
*system/etc/audio
*system/etc/wifi
*system/lib/drm
*system/lib/egl
*system/lib/soundfx
END STAGE
# Before zipping Cusrom make sure the contents of the
folder Port has an arrangement like this
- Meta-Inf
- system
- boot.img
# If it is like a living doing just above the zipping process
by using Es file Explorer or Bluetooth file transfer similar applications,
* A few - Good luck *
------Niks--------
wow, is it possible to do it with the newer SOC's ? for example the MTK6752?
HOW TO RESTORE YOUR BASEBAND IF YOU LOST IT DURING A FORMAT - MT65XX DEVICES
Thanks go to abdullahi_ for this solution. His original post from another forum can be found below:
https://forum.hovatek.com/thread-116-post-376.html#pid376
Prequisites
Phone Rooted
Smart Phone Flash Tool Backup - Specifically protect_f file (for a Dual SIM phone, maybe different for a single SIM phone)
Linux OS - I used Ubuntu in a virtual machine
Android SDK platform tools for ADB access
From a terminal (CTRL + ALT + T)
Code:
mkdir -p ~/protect_f/f
cd ~/protect_f
At this point copy the file "protect_f" in the ~/protect_f
then continue:
Code:
sudo mount -t ext4 -o loop protect_f f/
Enter your password
then continue:
Code:
cd f
sudo chown -R $USER:$USER *
Copy the files in the f/md folder to a folder on your phone and using a file manager with root access copy the two files into the /protect_f folder or any toher means
NOTE: You will probably get back your cell access immediately. However, please continue to make the permissions and ownership are the same as the original.
Also if you have a dual SIM, one of the files from the protect_f folder will automatically be created in the protect_s folder
To clean up the files on the Linux OS:
Code:
cd ~/protect_f
sudo umount f/
cd ~
rm -rf protect_f
To change permissions and ownership on the files
From an adb shell for your phone:
Code:
su
cd /protect_f
ls -l
Take note of the ownership of the md folder, on the phone I used they were ccci & nvram, in Linux the ownership was 9996 & 9997.
At this point I put the phone in airplane mode, just as a precaution to make sure the rest went smoothly
Code:
cd md
chown ccci:nvram *
chmod 660 *
If you have a DUAL SIM phone, for the second folder....
Code:
cd /protect_s/md
chown ccci:nvram *
chmod 660 *
You can now take the phone off of airplane mode and reboot your phone to be sure it is working,
ALL DONE!
REMOVED
All,
I've moved this to it's own thread just to keep thing separate.
In case you are uncomfortable with kingroot, or you want a less intrusive install (since we don't need any exploits to root this device - kudos Huawei!) I have built a modified version of the boot image that uses supersu by chainfire instead. This is based on the work done here http://cn.club.vmall.com/space-uid-5467988.html, so we still owe them thanks. All this does, is move the Superuser.apk package into the system partition so that it can be installed as an administrative application, add in a /sbin/su file, and copy /sbin/su into /sbin/xbin so we can use it. Here is a full diff for the 0012 version from the default boot.img supplied by Huawei:
Code:
diff: ./charger: No such file or directory
diff: ~/mediapad/dload.012/boot/filesystem/charger: No such file or directory
diff -r ./default.prop ~/mediapad/dload.012/boot/filesystem/default.prop
4c4
< ro.secure=0
---
> ro.secure=1
6,7c6,7
< ro.debuggable=1
< ro.adb.secure=0
---
> ro.debuggable=0
> ro.adb.secure=1
diff -r ./init.rc ~/mediapad/dload.012/boot/filesystem/init.rc
528,532d527
< service load_boot /sbin/load_boot
< class main
< seclabel u:r:install_recovery:s0
< oneshot
<
Only in ./sbin: load_boot
Only in ./sbin: su
load_boot contains the following:
Code:
#!/system/bin/sh
/sbin/su --auto-daemon &
if [ ! -e /system/app/Superuser.apk ];then
mount -o rw,remount /system
cp -rpf /data/local/tmp/Superuser.apk /system/app/Superuser.apk
chmod 644 /system/app/Superuser.apk
fi
if [ ! -e /system/xbin/su ];then
mount -o rw,remount /system
cp -rpf /sbin/su /system/xbin/
chmod 06755 /system/xbin/su
fi
The /sbin/su file has an md5sum:
Code:
md5sum sbin/su
cd029c6b8b7065ff8ff2860137aeff99 sbin/su
and that matches the md5sum of the su included with v2.46 of chainfires supersu ZIP file (in the link below). So from a security perspective, I think we are pretty clean.
To use this, do the following:
0) Make sure you have unlocked the bootloader first!!!
1) Download chainfires Superuser from here: https://download.chainfire.eu/696/SuperSU/UPDATE-SuperSU-v2.46.zip , and extract the Superuser.apk file from the common folder.
2) adb shell "rm -rf /data/local/tmp/*"
3) adb push <path_to>/Superuser..apk /data/local/tmp/Superuser.apk
4) adb reboot bootloader
( your device will restart)
5) fastboot flash boot <path_to>/super_boot.img
6) fastboot reboot
7) Open the supersu App and update su (otherwise you may have strange issues)
That's it! You're rooted!
This does not do any odd exploits or camera driver adjustments or anything so there shouldn't be any issues with the camera or sound, but, as always, no guarantees.
File is to big too upload here so grab it from here:
703L
b012:
https://www.dropbox.com/s/7wqs6qghphy42sl/super_boot.b012.img?dl=0
b013 - untested for now!!! Tested and works fine:
https://www.dropbox.com/s/9so1wdbofhlbcmo/super_boot.b013.img?dl=0
b015 - Tested and works fine:
https://www.dropbox.com/s/cs767z8yjyfsfku/super_boot.703L.B015.img?dl=0
b106 - Tested and works fine:
https://www.dropbox.com/s/4qvtvpemiko01ie/super_boot.703L.B106.img?dl=0
702L
b003 - Untested! - Potentially Insecure! - I got the link for the 702L image from xda, NOT from emui.com. So I can't speak to the security:
https://www.dropbox.com/s/fp1cj25m1zzqq0m/super_boot.702L.B003.img?dl=0
Root sucessfully without any problems.
Big thanks.
dfsteen said:
All,
I've moved this to it's own thread just to keep thing separate.
In case you are uncomfortable with kingroot, or you want a less intrusive install (since we don't need any exploits to root this device - kudos Huawei!) I have built a modified version of the boot image that uses supersu by chainfire instead. This is based on the work done here http://cn.club.vmall.com/space-uid-5467988.html, so we still owe them thanks. All this does, is move the Superuser.apk package into the system partition so that it can be installed as an administrative application, add in a /sbin/su file, and copy /sbin/su into /sbin/xbin so we can use it. Here is a full diff for the 0012 version from the default boot.img supplied by Huawei:
Code:
diff: ./charger: No such file or directory
diff: ~/mediapad/dload.012/boot/filesystem/charger: No such file or directory
diff -r ./default.prop ~/mediapad/dload.012/boot/filesystem/default.prop
4c4
< ro.secure=0
---
> ro.secure=1
6,7c6,7
< ro.debuggable=1
< ro.adb.secure=0
---
> ro.debuggable=0
> ro.adb.secure=1
diff -r ./init.rc ~/mediapad/dload.012/boot/filesystem/init.rc
528,532d527
< service load_boot /sbin/load_boot
< class main
< seclabel u:r:install_recovery:s0
< oneshot
<
Only in ./sbin: load_boot
Only in ./sbin: su
load_boot contains the following:
Code:
#!/system/bin/sh
/sbin/su --auto-daemon &
if [ ! -e /system/app/Superuser.apk ];then
mount -o rw,remount /system
cp -rpf /data/local/tmp/Superuser.apk /system/app/Superuser.apk
chmod 644 /system/app/Superuser.apk
fi
if [ ! -e /system/xbin/su ];then
mount -o rw,remount /system
cp -rpf /sbin/su /system/xbin/
chmod 06755 /system/xbin/su
fi
The /sbin/su file has an md5sum:
Code:
md5sum sbin/su
cd029c6b8b7065ff8ff2860137aeff99 sbin/su
and that matches the md5sum of the su included with v2.46 of chainfires supersu ZIP file (in the link below). So from a security perspective, I think we are pretty clean.
To use this, do the following:
0) Make sure you have unlocked the bootloader first!!!
1) Download chainfires Superuser from here: https://download.chainfire.eu/696/SuperSU/UPDATE-SuperSU-v2.46.zip , and extract the Superuser.apk file from the common folder.
2) adb shell "rm -rf /data/local/tmp/*"
3) adb push <path_to>/Superuser..apk /data/local/tmp/Superuser.apk
4) adb reboot bootloader
( your device will restart)
5) fastboot flash boot <path_to>/super_boot.img
6) fastboot reboot
7) Open the supersu App and update su (otherwise you may have strange issues)
That's it! You're rooted!
This does not do any odd exploits or camera driver adjustments or anything so there shouldn't be any issues with the camera or sound, but, as always, no guarantees.
File is to big too upload here so grab it from here:
b012:
https://www.dropbox.com/s/wlsjjixext9kbjf/super_boot.b012.img?dl=0
b013 - untested for now!!! Tested and works fine:
https://www.dropbox.com/s/wchc8w6d0qy1npv/super_boot.b013.img?dl=0
Click to expand...
Click to collapse
Would this method work on a GEM-701L as well?
if you point me to the firmware image for that device i can tell you for sure.
Sent from my GEM-703L using XDA Free mobile app
thank you very much, its working great on b013 !
What i did was restoring b012 from sdcard, then i installed directly b013 update, then i rooted the phone using your method and everything is working great.
Now, this probably sounds studip, but could you please explain point 2-6? My Honor X2 is bootloader unlocked but I have no idea what I have to do when you write adb shell.. etc... Do I need any software to do what you suggest or is there a visual guide somewhere to get me going?
Thanks
Can someone give me a link to the Windows drivers please .
dfsteen said:
All,
I've moved this to it's own thread just to keep thing separate.
In case you are uncomfortable with kingroot, or you want a less intrusive install (since we don't need any exploits to root this device - kudos Huawei!) I have built a modified version of the boot image that uses supersu by chainfire instead. This is based on the work done here http://cn.club.vmall.com/space-uid-5467988.html, so we still owe them thanks. All this does, is move the Superuser.apk package into the system partition so that it can be installed as an administrative application, add in a /sbin/su file, and copy /sbin/su into /sbin/xbin so we can use it. Here is a full diff for the 0012 version from the default boot.img supplied by Huawei:
Code:
diff: ./charger: No such file or directory
diff: ~/mediapad/dload.012/boot/filesystem/charger: No such file or directory
diff -r ./default.prop ~/mediapad/dload.012/boot/filesystem/default.prop
4c4
< ro.secure=0
---
> ro.secure=1
6,7c6,7
< ro.debuggable=1
< ro.adb.secure=0
---
> ro.debuggable=0
> ro.adb.secure=1
diff -r ./init.rc ~/mediapad/dload.012/boot/filesystem/init.rc
528,532d527
< service load_boot /sbin/load_boot
< class main
< seclabel u:r:install_recovery:s0
< oneshot
<
Only in ./sbin: load_boot
Only in ./sbin: su
load_boot contains the following:
Code:
#!/system/bin/sh
/sbin/su --auto-daemon &
if [ ! -e /system/app/Superuser.apk ];then
mount -o rw,remount /system
cp -rpf /data/local/tmp/Superuser.apk /system/app/Superuser.apk
chmod 644 /system/app/Superuser.apk
fi
if [ ! -e /system/xbin/su ];then
mount -o rw,remount /system
cp -rpf /sbin/su /system/xbin/
chmod 06755 /system/xbin/su
fi
The /sbin/su file has an md5sum:
Code:
md5sum sbin/su
cd029c6b8b7065ff8ff2860137aeff99 sbin/su
and that matches the md5sum of the su included with v2.46 of chainfires supersu ZIP file (in the link below). So from a security perspective, I think we are pretty clean.
To use this, do the following:
0) Make sure you have unlocked the bootloader first!!!
1) Download chainfires Superuser from here: https://download.chainfire.eu/696/SuperSU/UPDATE-SuperSU-v2.46.zip , and extract the Superuser.apk file from the common folder.
2) adb shell "rm -rf /data/local/tmp/*"
3) adb push <path_to>/Superuser..apk /data/local/tmp/Superuser.apk
4) adb reboot bootloader
( your device will restart)
5) fastboot flash boot <path_to>/super_boot.img
6) fastboot reboot
7) Open the supersu App and update su (otherwise you may have strange issues)
That's it! You're rooted!
This does not do any odd exploits or camera driver adjustments or anything so there shouldn't be any issues with the camera or sound, but, as always, no guarantees.
File is to big too upload here so grab it from here:
b012:
https://www.dropbox.com/s/wlsjjixext9kbjf/super_boot.b012.img?dl=0
b013 - untested for now!!! Tested and works fine:
https://www.dropbox.com/s/wchc8w6d0qy1npv/super_boot.b013.img?dl=0
Click to expand...
Click to collapse
Very nice guide. I followed your instructions and I rooted successfully. I am getting a Cell broadcasts has stopped error upon boot but it really doesn't affect anything so I'm going to freeze it. The good part of this whole process is I ordered my X2 from a seller (zomlong-trading) on eBay and they said they installed an "international" ROM which has all the GAPPS like the Play Store etc.... I had the phone within a week (It shipped on Monday and I got it on Thursday) and the phone came working perfectly. I emailed Huawei for the unlock code and had it within three hours. When I went to unlock apparently the phone was already unlocked so all i had to do was follow your root procedure and that worked like a charm. I can't wait for someone to port the Chinese TWRP to an English version. I'm excited about being able to flash anything AOSP based on this when and if it ever happens. Anyway, thanks for your help.
Bunkerstudio said:
Now, this probably sounds studip, but could you please explain point 2-6? My Honor X2 is bootloader unlocked but I have no idea what I have to do when you write adb shell.. etc... Do I need any software to do what you suggest or is there a visual guide somewhere to get me going?
Thanks
Click to expand...
Click to collapse
Adb and fastboot are tools that you use to interact with android from your PC. You can look here for beginner information:
http://forum.xda-developers.com/showthread.php?t=690362
Note that there are many many threads discussing these things on xda, and the above is only one example. Search around and you will find a whole lot more information.
Confirm: Worked well with GEM-703LT version (32Gb storage)
Didn't work. Rooted using another method
dfsteen said:
All,
I've moved this to it's own thread just to keep thing separate.
In case you are uncomfortable with kingroot, or you want a less intrusive install (since we don't need any exploits to root this device - kudos Huawei!) I have built a modified version of the boot image that uses supersu by chainfire instead. This is based on the work done here http://cn.club.vmall.com/space-uid-5467988.html, so we still owe them thanks. All this does, is move the Superuser.apk package into the system partition so that it can be installed as an administrative application, add in a /sbin/su file, and copy /sbin/su into /sbin/xbin so we can use it. Here is a full diff for the 0012 version from the default boot.img supplied by Huawei:
Code:
diff: ./charger: No such file or directory
diff: ~/mediapad/dload.012/boot/filesystem/charger: No such file or directory
diff -r ./default.prop ~/mediapad/dload.012/boot/filesystem/default.prop
4c4
< ro.secure=0
---
> ro.secure=1
6,7c6,7
< ro.debuggable=1
< ro.adb.secure=0
---
> ro.debuggable=0
> ro.adb.secure=1
diff -r ./init.rc ~/mediapad/dload.012/boot/filesystem/init.rc
528,532d527
< service load_boot /sbin/load_boot
< class main
< seclabel u:r:install_recovery:s0
< oneshot
<
Only in ./sbin: load_boot
Only in ./sbin: su
load_boot contains the following:
Code:
#!/system/bin/sh
/sbin/su --auto-daemon &
if [ ! -e /system/app/Superuser.apk ];then
mount -o rw,remount /system
cp -rpf /data/local/tmp/Superuser.apk /system/app/Superuser.apk
chmod 644 /system/app/Superuser.apk
fi
if [ ! -e /system/xbin/su ];then
mount -o rw,remount /system
cp -rpf /sbin/su /system/xbin/
chmod 06755 /system/xbin/su
fi
The /sbin/su file has an md5sum:
Code:
md5sum sbin/su
cd029c6b8b7065ff8ff2860137aeff99 sbin/su
and that matches the md5sum of the su included with v2.46 of chainfires supersu ZIP file (in the link below). So from a security perspective, I think we are pretty clean.
To use this, do the following:
0) Make sure you have unlocked the bootloader first!!!
1) Download chainfires Superuser from here: https://download.chainfire.eu/696/SuperSU/UPDATE-SuperSU-v2.46.zip , and extract the Superuser.apk file from the common folder.
2) adb shell "rm -rf /data/local/tmp/*"
3) adb push <path_to>/Superuser..apk /data/local/tmp/Superuser.apk
4) adb reboot bootloader
( your device will restart)
5) fastboot flash boot <path_to>/super_boot.img
6) fastboot reboot
7) Open the supersu App and update su (otherwise you may have strange issues)
That's it! You're rooted!
This does not do any odd exploits or camera driver adjustments or anything so there shouldn't be any issues with the camera or sound, but, as always, no guarantees.
File is to big too upload here so grab it from here:
b012:
https://www.dropbox.com/s/wlsjjixext9kbjf/super_boot.b012.img?dl=0
b013 - untested for now!!! Tested and works fine:
https://www.dropbox.com/s/wchc8w6d0qy1npv/super_boot.b013.img?dl=0
Click to expand...
Click to collapse
hi
thanks for your efforts, but do you have the stock recovery.img for b013 rom
thankyou
All,
As soon as b015 goes up on the website I will pull it apart and generate a rooted version. It usually goes up within a week of the OTA update so hang in there!
-Dan
Hi there... I wonder if u can take a look @ GEM-702L ???
theres only one FW for the 702.... but there no stable working boot.img could work with...T.T
While I mean all the 703 bxyz method could root...the 702... but probably theres some problems... like GPU driver sth like that... first.. it caused no sound problem.... random freezes.... n cheesy screen
lcw622 said:
Hi there... I wonder if u can take a look @ GEM-702L ???
theres only one FW for the 702.... but there no stable working boot.img could work with...T.T
While I mean all the 703 bxyz method could root...the 702... but probably theres some problems... like GPU driver sth like that... first.. it caused no sound problem.... random freezes.... n cheesy screen
Click to expand...
Click to collapse
Do you have a link to the firmware?
dfsteen said:
Do you have a link to the firmware?
Click to expand...
Click to collapse
http://forum.xda-developers.com/huawei-mediapad/general/mediapad-x2-firmware-702l-703l-t3168925
dfsteen said:
All,
As soon as b015 goes up on the website I will pull it apart and generate a rooted version. It usually goes up within a week of the OTA update so hang in there!
-Dan
Click to expand...
Click to collapse
Thanks and btw the b015 is already on the website. Excited now
Can't wait for the root of b015 [emoji18]
Gesendet von iPad mit Tapatalk
b015 rooted is now up on the initial posting. Enjoy!
lcw622 said:
http://forum.xda-developers.com/huawei-mediapad/general/mediapad-x2-firmware-702l-703l-t3168925
Click to expand...
Click to collapse
I've posted a rooted boot.img for 702l.b003 from the link you provided. I don't own this device, so it's not tested, but let me know if it works.
Hi to all. I am a newbie ... but I try to do all my best
Above all please make a directory under /mnt (I called the directory "MyMount1"); "mylogin" represents your login name.
Open the terminal and type the next commands:
-sudo mkdir /mnt/MyMount1
-sudo chown mylogin:mylogin /mnt/MyMount1
-copy system.img & paste it into MyMount1 (computer/mnt/MyMount1)
-cd /
-cd mnt
-cd MyMount1
-mkdir sys/ && sudo mount -t ext4 -o loop system.img sys/
-sudo chown mylogin:mylogin sys (without this command you will not be able to copy and modify anything)
-cd sys
-sudo chown mylogin:mylogin addon.d (without this command you will not be able to copy and modify anything)
-then copy addon.d & paste it into Ubuntu Desktop (now you can make any changes you want)
-then delete addon.d into /mnt/MyMount1/sys
-copy addon.d (into Ubuntu Desktop) & paste it into /mnt/MyMount1/sys
-then apply the same command to every folder inside system.img (/mnt/MyMount1/sys) and repeat the procedure (copy it into Ubuntu Desktop, make changes and paste it into /mnt/MyMount1/sys).
The following screenshot will help you better understand all the steps :
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Before "sudo chown mylogin:mylogin sys" command :
After "sudo chown mylogin:mylogin sys" command :
Before "sudo chown mylogin:mylogin addon.d" command :
After "sudo chown mylogin:mylogin addon.d" command :
That's all ... for now
XDA:DevDB Information
System.img, ROM for all devices (see above for details)
Contributors
Cleopatra Bianchi
ROM OS Version: 6.0.x Marshmallow
Version Information
Status: Testing
Created 2016-03-24
Last Updated 2016-03-24
hey there!!! i can give you a couple of suggestion, even if i don't get if you are only extracting or also editing and repacking since i don't see any repack code.. anyway.. first of all you definitely should use -R in yoour chown code.. this means recursive.. so you don't have to do it for every folder, subfolder and so on!! do a chown -r for sys and you're done with it.
then another thing.. i personally use a script that will handle all this by itself, i put it in the file explorer script folder and so you can access it from everywhere just right-clicking on the file you want to mount.. it will need to edit path for pass it as variable, but it's easy.. at least once you know how to
so this is my script:
Code:
#!/bin/bash
CWD=(pwd)
simg2img [email protected] img.img; mkdir /tmp/system; mate-terminal -x sudo mount -t auto -o loop img.img /tmp/system; mate-terminal -x sudo chown -R login:login /tmp/system
just to explain, you see simg2img because i work with sparse img ( from samsung) that must be converted to regular img before get mounted, so i have the simg2img binary compiled and moved into /usr/local/bin path to access it from any path.. you will need to do the same or to remove that part if you don't need it.
also you must change mate-terminal to plain terminal since you're on unity i can see
then move the script to /home/your_login/.nautilus/script (again because you're on unity using nautilus i think) check if it has the exec bit enbled from permission and then enjoy..
oh another thing.. in case you need to copy keeping the permissions and ownership, so that you don't ahve to fix all that later you simply don't set the last part of the script - the chown part, since you can access the subfolders and files anyway and for ex. use the "cp -a /tmp/system/app /your_desired_path to work on it.
Wuby986 said:
hey there!!! i can give you a couple of suggestion, even if i don't get if you are only extracting or also editing and repacking since i don't see any repack code.. anyway.. first of all you definitely should use -R in yoour chown code.. this means recursive.. so you don't have to do it for every folder, subfolder and so on!! do a chown -r for sys and you're done with it.
then another thing.. i personally use a script that will handle all this by itself, i put it in the file explorer script folder and so you can access it from everywhere just right-clicking on the file you want to mount.. it will need to edit path for pass it as variable, but it's easy.. at least once you know how to
so this is my script:
Code:
#!/bin/bash
CWD=(pwd)
simg2img [email protected] img.img; mkdir /tmp/system; mate-terminal -x sudo mount -t auto -o loop img.img /tmp/system; mate-terminal -x sudo chown -R login:login /tmp/system
just to explain, you see simg2img because i work with sparse img ( from samsung) that must be converted to regular img before get mounted, so i have the simg2img binary compiled and moved into /usr/local/bin path to access it from any path.. you will need to do the same or to remove that part if you don't need it.
also you must change mate-terminal to plain terminal since you're on unity i can see
then move the script to /home/your_login/.nautilus/script (again because you're on unity using nautilus i think) check if it has the exec bit enbled from permission and then enjoy..
oh another thing.. in case you need to copy keeping the permissions and ownership, so that you don't ahve to fix all that later you simply don't set the last part of the script - the chown part, since you can access the subfolders and files anyway and for ex. use the "cp -a /tmp/system/app /your_desired_path to work on it.
Click to expand...
Click to collapse
Thank you very much for your suggestions
I have to admit that I am a newbie/noob ... particularly on Linux (I have installed Ubuntu OS just a week ago ... I come from the planet Windows). I have tried "android_img_repack_tools-android-6.0.1_r3_x64.tar.gz" ... but simg2img doesn't works (I am not able to convert system.img in raw). I'm trying to mod a system.img Mediatek Marshmallow.
Kindest Regards.
Cleopatra Bianchi said:
Thank you very much for your suggestions
I have to admit that I am a newbie/noob ... particularly on Linux (I have installed Ubuntu OS just a week ago ... I come from the planet Windows). I have tried "android_img_repack_tools-android-6.0.1_r3_x64.tar.gz" ... but simg2img doesn't works (I am not able to convert system.img in raw). I'm trying to mod a system.img Mediatek Marshmallow.
Kindest Regards.
Click to expand...
Click to collapse
i hano NO idea about mediatek devices, you should ask in the corresponding fora, but most likely you don't need simg 2 img since that's not a sparse img, so you could be able to mount it strait away.. or at least try first without converting it.
what's the error you're getting in terminal?
Wuby986 said:
i hano NO idea about mediatek devices, you should ask in the corresponding fora, but most likely you don't need simg 2 img since that's not a sparse img, so you could be able to mount it strait away.. or at least try first without converting it.
what's the error you're getting in terminal?
Click to expand...
Click to collapse
This is the error in terminal :
Cleopatra Bianchi said:
This is the error in terminal :
Click to expand...
Click to collapse
yeah then is definitely not a sparse img.. maybe a regular img or other kinda of..
you should search for the mtk device forum for this info.. or better yet maybe the @dsixda kitchen has a conversion binary for it, so you can see which is and use it instead of the simg2img.. this kitchen is not anymore updated, so you cannot use it for everything like repack or root, but should work for unpack
Wuby986 said:
yeah then is definitely not a sparse img.. maybe a regular img or other kinda of..
you should search for the mtk device forum for this info.. or better yet maybe the @dsixda kitchen has a conversion binary for it, so you can see which is and use it instead of the simg2img.. this kitchen is not anymore updated, so you cannot use it for everything like repack or root, but should work for unpack
Click to expand...
Click to collapse
Ok ... I'll do it. Thank you very much for your suggestions.
Happy Easter
Cleopatra Bianchi said:
Hi to all. I am a newbie ... but I try to do all my best
Above all please make a directory under /mnt (I called the directory "MyMount1"); "mylogin" represents your login name.
Open the terminal and type the next commands:
-sudo mkdir /mnt/MyMount1
-sudo chown mylogin:mylogin /mnt/MyMount1
-copy system.img & paste it into MyMount1 (computer/mnt/MyMount1)
-cd /
-cd mnt
-cd MyMount1
-mkdir sys/ && sudo mount -t ext4 -o loop system.img sys/
-sudo chown mylogin:mylogin sys (without this command you will not be able to copy and modify anything)
-cd sys
-sudo chown mylogin:mylogin addon.d (without this command you will not be able to copy and modify anything)
-then copy addon.d & paste it into Ubuntu Desktop (now you can make any changes you want)
-then delete addon.d into /mnt/MyMount1/sys
-copy addon.d (into Ubuntu Desktop) & paste it into /mnt/MyMount1/sys
-then apply the same command to every folder inside system.img (/mnt/MyMount1/sys) and repeat the procedure (copy it into Ubuntu Desktop, make changes and paste it into /mnt/MyMount1/sys).
The following screenshot will help you better understand all the steps :
Before "sudo chown mylogin:mylogin sys" command :
After "sudo chown mylogin:mylogin sys" command :
Before "sudo chown mylogin:mylogin addon.d" command :
After "sudo chown mylogin:mylogin addon.d" command :
That's all ... for now
XDA:DevDB Information
System.img, ROM for all devices (see above for details)
Contributors
Cleopatra Bianchi
ROM OS Version: 6.0.x Marshmallow
Version Information
Status: Testing
Created 2016-03-24
Last Updated 2016-03-24
Click to expand...
Click to collapse
pro tip use -R to make chown reclusive and include all the subfolders
sudo chown login:login -R (folder in sys)
---------- Post added at 08:59 AM ---------- Previous post was at 08:59 AM ----------
Cleopatra Bianchi said:
Hi to all. I am a newbie ... but I try to do all my best
Above all please make a directory under /mnt (I called the directory "MyMount1"); "mylogin" represents your login name.
Open the terminal and type the next commands:
-sudo mkdir /mnt/MyMount1
-sudo chown mylogin:mylogin /mnt/MyMount1
-copy system.img & paste it into MyMount1 (computer/mnt/MyMount1)
-cd /
-cd mnt
-cd MyMount1
-mkdir sys/ && sudo mount -t ext4 -o loop system.img sys/
-sudo chown mylogin:mylogin sys (without this command you will not be able to copy and modify anything)
-cd sys
-sudo chown mylogin:mylogin addon.d (without this command you will not be able to copy and modify anything)
-then copy addon.d & paste it into Ubuntu Desktop (now you can make any changes you want)
-then delete addon.d into /mnt/MyMount1/sys
-copy addon.d (into Ubuntu Desktop) & paste it into /mnt/MyMount1/sys
-then apply the same command to every folder inside system.img (/mnt/MyMount1/sys) and repeat the procedure (copy it into Ubuntu Desktop, make changes and paste it into /mnt/MyMount1/sys).
The following screenshot will help you better understand all the steps :
Before "sudo chown mylogin:mylogin sys" command :
After "sudo chown mylogin:mylogin sys" command :
Before "sudo chown mylogin:mylogin addon.d" command :
After "sudo chown mylogin:mylogin addon.d" command :
That's all ... for now
XDA:DevDB Information
System.img, ROM for all devices (see above for details)
Contributors
Cleopatra Bianchi
ROM OS Version: 6.0.x Marshmallow
Version Information
Status: Testing
Created 2016-03-24
Last Updated 2016-03-24
Click to expand...
Click to collapse
pro tip use -R to make chown reclusive and include all the subfolders
sudo chown login:login -R (folder in sys)
#This DTS audio for rooted and Nonrooted devices.
#To install go to GooglePlay and install Termux.
#Then paste this url to your browser and load the page it should start downloading:
https://github.com/toshiba6012/Android-DTS-No-Root-Killer-Sound/archive/refs/heads/main.zip
#Then unzip the downloaded zip file from Github to your internal storage root.
#Open the Termux app and run these commands copy them from here and paste them to
#Termux terminal just long press:
termux-setup-storage #Grant access to the prompt:
cd ~/storage/shared/termux_dTS
#Then you will have to know the architecture of your device for phones 64bit:
cd arm64-v8a
#For 32bit phones it will be:
cd armeabi-v7a
#For Android-x86 64bit it will be:
cd x86_64
#For Android-x86 32bit it will be:
cd x86
#Then to install run these commands:
cp -r usr /data/data/com.termux/files
chmod 755 /data/data/com.termux/files/usr/bin/dTS
chmod 755 /data/data/com.termux/files/usr/libexec/libdTS.so
chmod 755 /data/data/com.termux/files/usr/pulse
chmod 755 /data/data/com.termux/files/usr/pulse/default.pa
dTS
#Please note everytime the device is shutdown you need to reload the libraries.
#This simply done by the termux app just type:
dTS
#You will enjoy the sound. Take care.
Best regards
Ryan Johnson
Please make Video on How to install Dtx with Termux
riggs6012 said:
#This DTS audio for rooted and Nonrooted devices.
#To install go to GooglePlay and install Termux.
#Then paste this url to your browser and load the page it should start downloading:
https://github.com/toshiba6012/Android-DTS-No-Root-Killer-Sound/archive/refs/heads/main.zip
#Then unzip the downloaded zip file from Github to your internal storage root.
#Open the Termux app and run these commands copy them from here and paste them to
#Termux terminal just long press:
termux-setup-storage #Grant access to the prompt:
cd ~/storage/shared/termux_dTS
#Then you will have to know the architecture of your device for phones 64bit:
cd arm64-v8a
#For 32bit phones it will be:
cd armeabi-v7a
#For Android-x86 64bit it will be:
cd x86_64
#For Android-x86 32bit it will be:
cd x86
#Then to install run these commands:
cp -r usr /data/data/com.termux/files
chmod 755 /data/data/com.termux/files/usr/bin/dTS
chmod 755 /data/data/com.termux/files/usr/libexec/libdTS.so
chmod 755 /data/data/com.termux/files/usr/pulse
chmod 755 /data/data/com.termux/files/usr/pulse/default.pa
dTS
#Please note everytime the device is shutdown you need to reload the libraries.
#This simply done by the termux app just type:
dTS
#You will enjoy the sound. Take care.
Best regards
Ryan Johnson
Click to expand...
Click to collapse
HI Ryan,
Could you please give me some more detail how to install it? The linked zip is different from this one attached by you, at the end of post. Which one is right than?
Second - can I unpack files just somewhere on my internal memory or does it have to be root folder? I am not rooted by the way and I had been looking for good sound mod without root and so I found your post with DTS. I cannot install it.... Thanks for help!
Regards!
M.