Database Info

How to port roms to your mtk with android device

HOW TO PORT ROMS TO YOUR MTK WITH ANDROID DEVICE
Most of us have always wanted to use custom roms but there just no custom roms for our devices so we just use different app launchers and uninstall some bloatware to make our stock rom feel good.
Rom porting makes it possible to use a custom rom on your mtk device provided in this tutorial they have the same chipset (example: mtk 6582 ported to mtk6582).
THINGS NEEDED :
1. B1 archiver / ES FILE EXPLORER
2. Root Browser.
4. A rooted device is also needed but not much important if you have CWM INSTALLED WITHOUT ROOT.
PROCEDURE :
1. Make a backup of your current rom, preferably CWM backup. You can either use MTK DROID TOOLS or ROM MANAGER...
The location of the backup will be at clockwork/backup/"date and time of the backup ". This is very important since we will need stuff from the back up and we will also use the backup to recover the phone should the ported rom give any problems.
2. At this point I presume you have already downloaded the apps needed and the custom rom you want to use which is in a zip format( this was not important but I had to bring it up cause I know zombies could be reading this.
3. Now extract the custom Rom with Root Browser. if you extracted with Root Browser then the location will be "speedsoftware/extracted/"folder with the name of the custom rom "".
4. Now open Root Browser and open the folders side by side "custom rom which will be ported at one side and other side will be used for searching for the location of the things needed for the custom rom.
5. Delete the following from the Custom rom:
Boot.img
logo.bin (You do this only when you like the Your current logo.bin)
system/vendor
system/usr
system/lib/hw
system/lib/modules
system/lib/libncurses.so
system/etc/firmware
system/etc/vold.fstab
system/etc/vold.fstab.nand
system/etc/bluetooth
6. Now that you have deleted them from the custom rom replace them. You will find the boot.img at clockworkmod/back/"folder with date and time"/boot.img. The rest of the files and folders will br located in the Root /system. Just copy and paste
7. Now at the custom Rom panel go back to where you find the "META-INF" folder,open /google/android will now long press on "updater script" and tap on open with then select text editor.
8. Check The mount & format point check something like this mmcblk0p. A number is always written after the "P" replace the number of your BASE to PORT.
9. Check multi select in B1 archiver Select ( do not archive the folder the files are in but the individual files in the folder containing the extracts)
10. Compress to ZIP file wait till the process finished. Now boot to recovery and flash your ROM
Good luck in porting Your Rom... I have used this method to port 5 roms including AROMA ROMS. and I have never ported a Rom with a pc before
MAYBE U NEED TO EXTRACT THE BOOT IMG TOO IF THIS DIDNT WORKED
DO IT AS FOLLOWS
Requirements:
-- BusyBox (cpio, gunzip and gzip is mandatory)
-- /System Write Permissions (Does not need to be a modified kernel)
-- Terminal Emulator
-- ES File Explorer (or similar)
-- Hex Editor (or use of DD)
-- Open up your android terminal emulator.
-- Now go ahead and pull your boot.img from your device (or use another one if you wish)
-- Open up your boot.img with the Hex Editor and look for: ANDROID!. Remove everything before it so that the ANDROID! header is the first to be read then save it over top of the boot.img. NOTE: This is only required if you are using a stock boot.img.
OR USE THIS IF U DIDNT UNDERSTOOD THIS
Hello Everyone, I’ll show you how to Unpack and Repack your Phone’s Boot.img & Tweak Karnel. Lets start.
Make a new folder named “boot edit” in cache/
image
Pull your boot.img in this folder
image
Now open ApkTool. Long press on “cache“, click on Get Access Permission.
image
Open cache folder and do same with boot edit. Give ApkTool access permission
image
Open boot edit, click on boot.img select Expack(MT65xx), press ok
image
It will unpack your boot.img.
image
Now open file manager & go to cache/boot edit/. You wil find your unpacked boot.
image
Now edit/modify the files or tweak karnel.
Again open ApkTool. Goto cache/boot edit click on ramdisk select repack-mt65xx.
image
It will repack your boot.
image
You will find an img file named new.img
image
This file is your Tweaked/edited/custom boot.img!!
Flash it via Recovery or Flashify & Enjoy..
FOR DETAILED AND STEP WISE GUIDE WITH SCREEN SHOTS SEE HERE
Mod Edit: link removed
XDA:DevDB Information
HOW TO PORT ROMS TO YOUR MTK WITH ANDROID DEVICE, ROM for all devices (see above for details)
Contributors
manhar2108, manhar2108, 2108kick
Source Code: Mod Edit: link removed
ROM OS Version: 5.1.x Lollipop
ROM Kernel: Linux 3.4.x
Based On: all
Version Information
Status: Stable
Created 2015-08-16
Last Updated 2015-08-16
HIT THANKS IF I HELPED U

Good guide..
Especially for noobs....

Darshan601 said:
Good guide..
Especially for noobs....
Click to expand...
Click to collapse
i too am a noob so i tried and made this guide

how bout porting 5.1 rom to 4.4.2 stock?
what should I consider?
aside from tweaking kernel

manhar2108 said:
i too am a noob so i tried and made this guide
Click to expand...
Click to collapse
Yeah....Even I am a noob

gunzgunz said:
how bout porting 5.1 rom to 4.4.2 stock?
what should I consider?
aside from tweaking kernel
Click to expand...
Click to collapse
just replace all these files and use stock kernal to port them
good luck

Sir i tried your guide in porting rom. Mt6582 tp mt6582 chipset roms.. But after replacing those files you mentioned and when i flashed it to my phone, it was tuck in boot screen and keep on restarting. How am I going to fix this?

Thread closed. Pay per click links are not allowed on XDA.
Darth
Forum Moderator

[GUIDE][ROOT][MEDIATEK] Systemless root for mediatek

*****Keep in mind that I or XDA or anyone else is not responsible for what happens to your device make sure you have a nandroid backup before proceeding
This is based on my personal experience I'm not a Dev
How to enable systemless root on mediatek !!!!
Step 1:
Get the booting of your phone via readback using spflashtool or dumping the ROM IMG !!
Step 2:
Unpack the boot IMG using mkbootimg or carliv IMG kitchen or Android kitchen !!!
Step 3:
Open the ramdisk folder and open the init.rc using notepad++
Step 4
Goto the line
Code:
export PATH /sbin:/system/bin:/system/xbin:/vendor/bin
**The line may vary but it will look similar !!!
Add the path of your su file at the end
Like I was t to install it at my data partition so
Add
Code:
:/data/bin
At the end of the line and save !!
Then change the permissions of /data/bin to 644 else apps won't be able to read the path due to insuffient permission !!!
Then repack the boot.img
Flash the bootimg via sp flash tool of flashify or any other method
Step 6:
***note use the su binaries of your CPU only
Like I used arm 7 binaries for my device !!
To know your CPU type
Download terminal emulator or use adb shell and type cat /proc/cpuinfo
Now using adb push copy the su file to the /data/bin folder or make a flashable zip to do the same !!
If you can't push via adb try doing it in adb supported recovery !!!
You might need to create the bin folder manually
And don't forget to set the permission to 0755 and reboot !!
Plz let me know if it works !!!
And also let me know if it doesn't !!!!
I can't post the flashable zip because I'm still new !!!

Can you post some more info for this? What mtk chipset is it tested with? What android version? When you repack the kernel image, do you use android headers or mediatek headers?

AlexZap said:
Can you post some more info for this? What mtk chipset is it tested with? What android version? When you repack the kernel image, do you use android headers or mediatek headers?
Click to expand...
Click to collapse
Carliv Image Kitchen will repack the same way it was unpacked so you do not have to worry.
I also want more info for this because I'm not even finding the first link export .....

kirito9 said:
Carliv Image Kitchen will repack the same way it was unpacked so you do not have to worry.
I also want more info for this because I'm not even finding the first link export .....
Click to expand...
Click to collapse
the point is that the systemless installer is supposed to unpack and repack the kernel... and i dont know/dont think it can handle a mediatek header

AlexZap said:
the point is that the systemless installer is supposed to unpack and repack the kernel... and i dont know/dont think it can handle a mediatek header
Click to expand...
Click to collapse
Ohh, it could be that it doesn't support Mediatek because I tried a systemless SuperSU and it didn't boot the MT6580 device. I had to flash the boot.img to fix.

kirito9 said:
Ohh, it could be that it doesn't support Mediatek because I tried a systemless SuperSU and it didn't boot the MT6580 device. I had to flash the boot.img to fix.
Click to expand...
Click to collapse
There is no reason systemless root shouldn't work on mediatek phones other then the different kernel headers. The OP says he got it working, which is why I posted my questions to him... but he has failed to respond.

AlexZap said:
There is no reason systemless root shouldn't work on mediatek phones other then the different kernel headers. The OP says he got it working, which is why I posted my questions to him... but he has failed to respond.
Click to expand...
Click to collapse
There isn't? Strange, then why when I flashed the SuperSU systemless zip from here it didn't boot but when flashed the SuperSU from here it did but said in SuperSU app, couldn't find the su binary.
Maybe I should push "su" to xbin folder or bin? What are your thoughts?

kirito9 said:
There isn't? Strange, then why when I flashed the SuperSU systemless zip from here it didn't boot but when flashed the SuperSU from here it did but said in SuperSU app, couldn't find the su binary.
Maybe I should push "su" to xbin folder or bin? What are your thoughts?
Click to expand...
Click to collapse
I think you need to read some more on how and why systemless root works and what it is for.
Regular root, the summer you installed, puts a bunch of binaries in the /system partition on your android phone, and while giving you root, it breaks a lot of things because it modifies the stock image, something that android doesn't expect to ever change except for system upgrades.
Systemless root fixes this. It does nothing to the system partition. It creates a mountable image and stores it in the /data partition that contains the su binary and whatever else is needed for root. It then modifies the boot image (the ramdisk that is packed with the kernel) so that on boot, it mounts this su image inside the already mounted system partition. This keeps the system partition stock, but at the same time, gives you root. Things like safetynet are unbroken and you can run things like android pay that check for a modified system image.
In order to do its magic, the systemless root installer has to be able to unpack and repack the boot partition. If you have a mediatek phone, you have about an 80% chance that your boot image is different then the rest of the android world. Mediatek phones have their own header in their images like boot and recovery (except for some very new devices). I am 95% certain that the systemless root installer does not know anything about mediatek headers. So it may unpack something, but clobber the boot image on repack. The author of this thread purports to have it working. I ask how. Is he one of the 20 or so percent without a mediatek header? Or did he do something else

AlexZap said:
.................
Click to expand...
Click to collapse
Yeah lol, first time working with android 6.0 and this systemless root. I know that's what the systemless root does, that's why after flashing the MT6580 device that I have, it didn't boot. Don't think the systemless supports this MT6580 as it uses it's own MTK header and not the standard AOSP.
Seems like OP as disappeared from this thread.

Sorry I took so long to respond
AlexZap said:
There is no reason systemless root shouldn't work on mediatek phones other then the different kernel headers. The OP says he got it working, which is why I posted my questions to him... but he has failed to respond.
Click to expand...
Click to collapse
And yes I got the systemless root working on my Panasonic T41 running CM 12
The SuperSU installer doesn't work on mediatek 'coz in cannot unpack the boot.img with mtk headers so i did it manually but SuperSU tried to fix the placement of the binaries !!
So i used another superuser !!

uttarayan21 said:
And yes I got the systemless root working on my Panasonic T41 running CM 12
The SuperSU installer doesn't work on mediatek 'coz in cannot unpack the boot.img with mtk headers so i did it manually but SuperSU tried to fix the placement of the binaries !!
So i used another superuser !!
Click to expand...
Click to collapse
I have found that magisk works flawlessly on my Jiayu s3... it uses hybrid headers in the images... but magical does the unpack/repack just fine.
Sent from my KFTHWI using XDA Premium 4 mobile app

AlexZap said:
I have found that magisk works flawlessly on my Jiayu s3... it uses hybrid headers in the images... but magical does the unpack/repack just fine.
Click to expand...
Click to collapse
Well but in my case when i tried it on CM 12.1 mtk6582
The phone got bricked !!
The SuperSU installer couldn't even get the boot image from my phone !! :crying: so i tried to modify the installer script with other tools but it was waaaay too complex for me so tried to do this instead with another superuser and it worked !!
I also had to modify the init.rc to start the daemonsu service !!! :good:

uttarayan21 said:
Well but in my case when i tried it on CM 12.1 mtk6582
The phone got bricked !!
The SuperSU installer couldn't even get the boot image from my phone !! :crying: so i tried to modify the installer script with other tools but it was waaaay too complex for me so tried to do this instead with another superuser and it worked !!
I also had to modify the init.rc to start the daemonsu service !!! :good:
Click to expand...
Click to collapse
I think magisk is better at handling boot image formats.

AlexZap said:
I think magisk is better at handling boot image formats.
Click to expand...
Click to collapse
I agree with @AlexZap and i am using it and it is working perfectly
Sent from my Z14 using Tapatalk

Does this work for the newer chipsets? I tried on Android 6.0 / MT6750, but I dont see the path export anywhere in the boot image (grep -nrw 'boot.img-ramdisk' -e "PATH")

MalikDrako said:
Does this work for the newer chipsets? I tried on Android 6.0 / MT6750, but I dont see the path export anywhere in the boot image (grep -nrw 'boot.img-ramdisk' -e "PATH")
Click to expand...
Click to collapse
magisk works flawlessly. no need to muck around, just flash it from twrp
Sent from my KFGIWI using XDA Premium 4 mobile app

AlexZap said:
magisk works flawlessly. no need to muck around, just flash it from twrp
Click to expand...
Click to collapse
I've been having trouble getting TWRP to run on this phone (black screen for a few seconds then it reboots into android), although I just discovered an unmodified repacked boot image wont boot, so either the phone is doing some verification that is failing or the tool I used cant repack it right

MalikDrako said:
I've been having trouble getting TWRP to run on this phone (black screen for a few seconds then it reboots into android), although I just discovered an unmodified repacked boot image wont boot, so either the phone is doing some verification that is failing or the tool I used cant repack it right
Click to expand...
Click to collapse
any chance the boot loader is locked? usually flashing a bad image will brick your phone if the boot loader is locked, but you never know.
have you tried unpacking the boot image with carliv's image kitchen? it throws out a bunch of info on how the image is made. as long as it is repacked the same way (Carliv's tool does this automatically), it should work fine. unless whoever your phone manufacturer is somehow included another signature check... which is really really out of the ordinary.

AlexZap said:
any chance the boot loader is locked? usually flashing a bad image will brick your phone if the boot loader is locked, but you never know.
have you tried unpacking the boot image with carliv's image kitchen? it throws out a bunch of info on how the image is made. as long as it is repacked the same way (Carliv's tool does this automatically), it should work fine. unless whoever your phone manufacturer is somehow included another signature check... which is really really out of the ordinary.
Click to expand...
Click to collapse
I just tried Carliv's image kitchen, and both boot and twrp port worked first try

How to change Permissions?
i could not understand it
can u help me Please?

[RECOVERY] TWRP 2.8.7.0 for Onda v919 Air CH DualOS

Actually the first working version of custom recovery for Onda v919 Air CH DualOS -> TWRP 2.8.7.0.
This is the port TWRP for Teclast x98Pro provided by user Dani Basabe on this resource, for which many thanks to him, honor and respect.
All basic functions are working: touch, install, wipe, backup and restore, OTG-function (can make a backup on a flash drive) & etc.
Only no vibration feedback. I suppose it's not the worst thing in life...
With the appear of TWRP can install different system mods, for example, audio. After taking a backup copy of the system, of course.
I have to say: xposed on this device doesn't run! After installation bootloop.
Installation:
Place twrp.img in the root of internal /sdcard and run the following commands via adb shell or a terminal emulator app:
Code:
su
dd if=/sdcard/twrp.img of=/dev/block/by-name/android_recovery
(I described the usual and most simple way for me. With devices through adb-interface I'm working with Total Commander with the plugin. We can try to install TWRP through fastboot commands:
adb reboot bootloader
fastboot flash recovery twrp.img)
To enter in TWRP after selecting "Android" in the main boot menu, hold down volume "-" before the advent of the service menu where the volume keys select "Recovery Mode" and press the power button.
Or you can use this method: http://forum.xda-developers.com/android/development/root-how-to-root-access-tablet-onda-t3396299
Download

Work fine!!
I just installed!
Excellent!
Thank you

ViAlexSt said:
Actually the first working version of custom recovery for Onda v919 Air CH DualOS -> TWRP 2.8.7.0.
This is the port TWRP for Teclast x98Pro provided by user Dani Basabe on this resource, for which many thanks to him, honor and respect.
All basic functions are working: touch, install, wipe, backup and restore, OTG-function (can make a backup on a flash drive) & etc.
Only no vibration feedback. I suppose it's not the worst thing in life...
With the appear of TWRP can install different system mods, for example, audio. After taking a backup copy of the system, of course.
I have to say: xposed on this device doesn't run! After installation bootloop.
Installation:
Place twrp.img in the root of internal /sdcard and run the following commands via adb shell or a terminal emulator app:
Code:
su
dd if=/sdcard/twrp.img of=/dev/block/by-name/android_recovery
(I described the usual and most simple way for me. With devices through adb-interface I'm working with Total Commander with the plugin. We can try to install TWRP through fastboot commands:
adb reboot bootloader
fastboot flash recovery twrp.img)
To enter in TWRP after selecting "Android" in the main boot menu, hold down volume "-" before the advent of the service menu where the volume keys select "Recovery Mode" and press the power button.
Download
Click to expand...
Click to collapse
Thank you very much!
Please, try to do the mod to enable audio on latest firmware with old bios.

mismamente said:
Please, try to do the mod to enable audio on latest firmware with old bios.
Click to expand...
Click to collapse
The difficulty is that I have sound. How do I determine whether sound on other devices? I have tried to use Viper-mod, but for some reason it stubbornly refuses to install the driver. You can try different audio mods from this forum, after making the system backup. Mods based on Viper most likely will not start, therefore it's necessary to try with another engine.
I currently run an interesting RemixOS: version 2.0 starts successfully, but no wifi and sound. While thinking about it, what libraries to take from stock firmware.

mismamente said:
Thank you very much!
Please, try to do the mod to enable audio on latest firmware with old bios.
Click to expand...
Click to collapse
Try Remix OS - boot 20160429, but system audio libraries other.

ViAlexSt said:
Try Remix OS - boot 20160429, but system audio libraries other.
Click to expand...
Click to collapse
thank you, I will try.

I have a cube tablet which has the same processor (intel bay trail), how did you port the twrp? I would like to do the same from my stock recovery (if you don't mind). Thanks. All I want is advice/tips... The recovery that I've ported just reboots when entered on recovery from Droidboot.

XDA_h3n said:
I have a cube tablet which has the same processor (intel bay trail) ... The recovery that I've ported just reboots when entered on recovery from Droidboot.
Click to expand...
Click to collapse
I can't say for sure how identical processors in terms of porting TWRP (Cherry Trail <=> Bay Trail). May need more significant changes to the original TWRP. General method for porting one: from stock recovery move to port kernel and recovery.fstab. Further it's necessary to look and compare other files. Unpack/pack images possible using Carliv Image Kitchen for Android. But in your place I would have found TWRP for a more suitable tablet. What is your model? Maybe I will prompt the object of porting.

ViAlexSt said:
I can't say for sure how identical processors in terms of porting TWRP (Cherry Trail <=> Bay Trail). May need more significant changes to the original TWRP. General method for porting one: from stock recovery move to port kernel and recovery.fstab. Further it's necessary to look and compare other files. Unpack/pack images possible using Carliv Image Kitchen for Android. But in your place I would have found TWRP for a more suitable tablet. What is your model? Maybe I will prompt the object of porting.
Click to expand...
Click to collapse
Well, I've tried the method of replacing zimage and dtb images and the recovery.fstab, which was the image I created before. It just doesn't work. I would think it's something to do with an partition layout issue.
I've been using the Teclast X98 twrp, as their rom actually works on our tablet without any modifications needed other than a couple of framework changes with resolution as it causes issue with the system ui being bigger.
Anyhow, thanks for your help, I'll try to see what I can do from the tool you've provided, as I used to unpack and repack the images using another kitchen tool. It quite off-topic from this thread; thanks for you help. Here's my stock recovery if you do have free time.

XDA_h3n said:
Well, I've tried the method of replacing zimage and dtb images and the recovery.fstab, which was the image I created before. It just doesn't work. I would think it's something to do with an partition layout issue.
Click to expand...
Click to collapse
I'm pretty sure that your chances of success will increase significantly if you select TWRP for a more suitable machine. I suggest to try TWRP for Onda v820w, as most similar devices Cube iWork7: Bay Trail+Android 4.4.4 (see attachment; autor kostyamat@4pda). About dt.img: I can't tell you how to do when porting, but if you are compiling TWRP this point is taken into consideration when editing BoardConfig.mk. What concrete advice I can't give, my recovery/TWRP hasn't dt.img.
For example: I to run on Onda TWRP 3.0.2.0 for Cube iWork8 Ultimate did (unpacked Carliv Imagetool):
1. Replaced all: recovery.img-base, recovery.img-cmdline, recovery.img-kernel, recovery.img-kernel_offset, recovery.img-pagesize, recovery.img-ramdisk-compress, recovery.img-ramdisk_offset, recovery.img-tags_offset.
2. In folder 'ramdisk':
- etc/recovery.fstab -> edited blocks like me;
- replaced: file_contexts, selinux_version, service_contexts, default.prop;
- file names init.recovery.***.rc, ueventd.***.rc changed like me, contents are not changed.
It was enough for a successful launch. But there is a little roughness in it work, so don't share.
Successful porting!

ViAlexSt said:
I'm pretty sure that your chances of success will increase significantly if you select TWRP for a more suitable machine. I suggest to try TWRP for Onda v820w, as most similar devices Cube iWork7: Bay Trail+Android 4.4.4 (see attachment; autor kostyamat@4pda). About dt.img: I can't tell you how to do when porting, but if you are compiling TWRP this point is taken into consideration when editing BoardConfig.mk. What concrete advice I can't give, my recovery/TWRP hasn't dt.img.
For example: I to run on Onda TWRP 3.0.2.0 for Cube iWork8 Ultimate did (unpacked Carliv Imagetool):
1. Replaced all: recovery.img-base, recovery.img-cmdline, recovery.img-kernel, recovery.img-kernel_offset, recovery.img-pagesize, recovery.img-ramdisk-compress, recovery.img-ramdisk_offset, recovery.img-tags_offset.
2. In folder 'ramdisk':
- etc/recovery.fstab -> edited blocks like me;
- replaced: file_contexts, selinux_version, service_contexts, default.prop;
- file names init.recovery.***.rc, ueventd.***.rc changed like me, contents are not changed.
It was enough for a successful launch. But there is a little roughness in it work, so don't share.
Successful porting!
Click to expand...
Click to collapse
Thank you a lot for all of your help
I've got it working on my tablet. I am very grateful for your help.
Recovery just doesn't mount the partitions correctly, but I'll be modifying the recovery.fstab until I'll find a way. Intel does the mount points like /dev/block/platform/intel/by-label/boot on stock recovery. I'll need to find the true location of all of the partitions, but it is fixable.
Again, I am very grateful :laugh:
Lol the original recovery.fstab from the port, has the same guid name on the partition blocks. That fixed it. Everything is mounting! Thanks.
Anybody with an Linx 7 or a Cube iWork 7 I'd posted in the linx forums and there is a tool that should do everything for you soon

TWRP Recovey for Sony Xperia E4G

I'm build TWRP recovery for e4g(e2003).
tested and working all funtions.
Needs:
-pc
-fastboot and drivers
-unlocked bootlader
1. Unlock bootloader (developer.sonymobile.com/unlockbootloader/)
2. install android fastboot drivers (find in net or forum)
3. download recovery.img file and copy fastboot folder.
4. connect your phone in fastboot mode (hold volume up and plug in usb)
5. open command line in fastboot folder(hold shift and right click)
6. type "fastboot flash recovery recovery.img"
7. Wait until you see the phone OK.
8. unplug phone and start in to recovery mode (hold volume down and power)
download link
TWRP_2.8.7.0_for_E4g

Wow thanks n_s218 for your awesome work:good:

Perfect!
Nice work

@n_s218 Can we port lollipop based rom from elephone p6000 or other same CPU and GPU phones to e4g?
Like this thread: http://forum.xda-developers.com/android/development/guide-how-to-port-lollipop-based-roms-t3223938

shinyghosts said:
@n_s218 Can we port lollipop based rom from elephone p6000 or other same CPU and GPU phones to e4g?
Like this thread: http://forum.xda-developers.com/android/development/guide-how-to-port-lollipop-based-roms-t3223938
Click to expand...
Click to collapse
we can try

Flashtool
I can flash this recovery with Flashtool or not?
no question, i forgot tha flashtool cant flash recovery. sorry for spam.

n_s218 said:
we can try
Click to expand...
Click to collapse
I found this rom for Elephone P6000 We can maybe port this to e4g. http://www.needrom.com/download/elephone-p6000-3/
and all rom for P6000: http://www.needrom.com/category/elephone/p6000/
How Can we get E4g stockboot.img and META-INF folder for port this MIUI7 rom?
Thanks:good:

This app works great for backing up partitions, in options change it to (img) http://forum.xda-developers.com/android/apps-games/app-partitions-backup-t3003599

shinyghosts said:
I found this rom for Elephone P6000 We can maybe port this to e4g. http://www.needrom.com/download/elephone-p6000-3/
and all rom for P6000: http://www.needrom.com/category/elephone/p6000/
How Can we get E4g stockboot.img and META-INF folder for port this MIUI7 rom?
Thanks:good:
Click to expand...
Click to collapse
If MIUI, then there's a newer version on MIUI pro.
You can back up boot image as @pryerlee said or via Flashify. For META-INF, we can take it from Elephone (as it's newer Android version so might be different) and just modify some lines (like the partition id's or the getprop lines at the beginning).
@n_s218 thank you, works great! This might be the beginning of custom ROMs for this device :victory:

Tomi_Ohl said:
If MIUI, then there's a newer version on MIUI pro.
You can back up boot image as @pryerlee said or via Flashify. For META-INF, we can take it from Elephone (as it's newer Android version so might be different) and just modify some lines (like the partition id's or the getprop lines at the beginning).
@n_s218 thank you, works great! This might be the beginning of custom ROMs for this device :victory:
Click to expand...
Click to collapse
Thanks:good: I have backup boot image with Partitions Backup & Restore app but this backup is 32mb so it is very big file elephone's miui boot image only 7mb.
and I have a another question Can we get boot.img in ftf file? but E4g's ftf doesn't contain kernel.sin but we have a boot.sin Can we getting boot image from this boot sin(elf)? look this thread:
http://forum.xda-developers.com/showthread.php?t=2699858

shinyghosts said:
Thanks:good: I have backup boot image with Partitions Backup & Restore app but this backup is 32mb so it is very big file elephone's miui boot image only 7mb.
and I have a another question Can we get boot.img in ftf file? but E4g's ftf doesn't contain kernel.sin but we have a boot.sin Can we getting boot image from this boot sin(elf)? look this thread:
http://forum.xda-developers.com/showthread.php?t=2699858
Click to expand...
Click to collapse
1. most of file empty (look at with hex editor) actually ~8 mb
2.boot partition backup file(boot.img) you must rename boot.elf and extract with flashtool elf extractor . you will get two file : boot.elf.0 = kernel , boot.elf.1=ramdisk

Thanks man...

n_s218 said:
1. most of file empty (look at with hex editor) actually ~8 mb
2.boot partition backup file(boot.img) you must rename boot.elf and extract with flashtool elf extractor . you will get two file : boot.elf.0 = kernel , boot.elf.1=ramdisk
Click to expand...
Click to collapse
Thanks:good: so that boot backup is a boot image? Is this right?:laugh:

Any recovery for e4 dual...
Can someone help with e4 dual e2115 for recovery....

shinyghosts said:
Thanks:good: so that boot backup is a boot image? Is this right?:laugh:
Click to expand...
Click to collapse
yes. right.
also you can boot.sin in ftf file ectract with flashtool sin editor

So I've tried to port Euphoria OS from P6000 using this guide.
I've done the ROM part, the updater script was also fine, but I've failed to port kernel: tried both tools mentioned there, Michfood's tool gave error for p6000 boot IMG, carliv's for both.
I've tried to flash the ROM with stock boot IMG, but with it the phone shuts down after Sony logo.
BTW I've backed up stock boot IMG via TWRP, but this shouldn't matter imo.
So can anyone help me with kernel?
EDIT: I'll try if the kernel in MIUI gives error too.
EDIT2: yes, same... Carliv's kitchen says unsupported archive format for ramdisk, Michfood's says something about that end offset is lower than start...
EDIT3: found this alternative for stock boot IMG. Still no solution for p6000 one
EDIT4: successfully decompiled P6000 kernel via Carliv's kitchen 1.0, by choosing regular Android (not mtk) mode. So now both kernels are decompiled but via different tool, so the output is not the same... Still didn't try the tool from EDIT3, it might be the solution.
EDIT5: I have no idea how to use tool from EDIT3 Now I'm downloading ftf, will see if I can do sth... Also I'll try this other tutorial for 64bit.

n_s218 said:
yes. right.
also you can boot.sin in ftf file ectract with flashtool sin editor
Click to expand...
Click to collapse
Thanks for information:good:

I did everything right. but not working. I think problem in boot.img
I working solve problem

n_s218 said:
1. most of file empty (look at with hex editor) actually ~8 mb
2.boot partition backup file(boot.img) you must rename boot.elf and extract with flashtool elf extractor . you will get two file : boot.elf.0 = kernel , boot.elf.1=ramdisk
Click to expand...
Click to collapse
this confused me,u read my mind,man,ty
but i cant follow this,can i use boot.sin file?

zokipfc said:
this confused me,u read my mind,man,ty
but i cant follow this,can i use boot.sin file?
Click to expand...
Click to collapse
yes. extract boot.sin via flashtool sin editor. Do you get boot.elf(boot.img)

Panasonic Eluga Note (MTK 6753) TWRP and root!

{
"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"
}
I successfully ported TWRP to Panasonic Eluga Note (MTK6753) after a four day effort. Not a dev here. First time doing this.
<TLDR? skip this>
When I started using android in my HTC HD2, every ROM was pre rooted. I took it for granted.
So I get this cheapo MTK and breaking into it is like banging head against a wall!! I was frustrated with the battery drain: Device never sleeps since the last OTA!
So I learnt SP flash tools and downgraded. ( wiped nvram and created another mess in the process- which is a different story. I solved it)
I could spend this effort and time to stop that pesky "Panasonic" bootaudio too. And that's the first thing I deleted after I booted TWRP, even before rooting.
</TLDR? skipped this>
First things first, enable ADB, enable OEM unlock in developer options, and go to bootloader to unlock it <fastboot oem unlock> THIS WILL WIPE DATA!!
Second thing: Backup nvram.img by sp flash readback and learn how to flash it back (search XDA)- Sometimes you can learn from other's mistakes too! I spent a day and half writing back IMEI and WIFI Mac.
Process (if you don't trust me and want to reproduce the steps yourself)
1. Download stock firmware. (google knows)
2. Patch boot.img so that it doesn't overwrite TWRP with stock recovery on each boot (extract by Carliv Image kitchen and hash out the three lines 663, 664 and 665 mentioning "service flash_recovery /system/bin/install-recovery.sh" in init.rc). I created two copies in the same folder (boot.img, and boot-verified.img) and copied scatter into the same folder for flashing. That's what I saw in the firmware folder.
3. Port TWRP using Carliv Image Kitchen method. I downloaded TWRP from here https://forum.xda-developers.com/android/software/twrp-porter-maker-mediatek-mt67xx-32-t3681861 but didn't use their method. It didn't work. The TWRP for this chip was stated as android N, but worked well.
4. Flash ported TWRP after copying scatter file to the Carliv Imagekitchen output folder and selecting that scatter in SP droid tools. I again created recovery.img and recovery-verified.img. Don't know if its needed that way. You could wait and flash boot and recovery together from the same folder.
5. That's it, you can enter custom recovery now. Get that pesky "panasonic" bootaudio off the system/media folder now! You can stay content after this or proceed to root.
<nandroid backup now, including Nvram and NVdata. Just in case>
6. Download Supersu zip flashable and flash it via TWRP. https://download.chainfire.eu/1113/SuperSU/UPDATE-SuperSU-v2.82-20170528234214.zip?retrieve_file=1 worked for me.
7. Reboot, check root!
If you're more daredevil,
8. Download Xposed flashable zip SDK23 and flash it. Download Xposed installer and copy it to SDcard too.
9. Reboot to recovery and flash the zip. Reboot, install xposed installer. Reboot again.
You're done!
I'll upload my boot.img and ported TWRP if anyone shows any interest in this.
Cheers!
(Bonus: this phone has built in IPtables support in the kernel! I used to flash custom kernel for this ability in other Stock ROMs. AFfirewall works "out of the box"- after rooting, of course!)
Edit: uploaded my modded boot.img and ported TWRP. find it here https://drive.google.com/file/d/1sM1BnyBUFN7PfncFcM7vzIet6gKt3G_L/view?usp=sharing
If you want to go the easy route, unzip the folder and flash it with sp flash. You'll be able to boot into recovery and do the other steps for rooting.
Rememer ONLY DOWNLOAD, don't format, or format and download, or anything!

Brilliant Work man. I also was sort of in your situation as well . i have a panasonic Eluga A3 (Qmobile Noir E2) in my country. Stock Qmobile rom was horrendous. so i flashed the panasonic rom but hated the boot audio and the bloatware that came with it. so i decided to make a slimmed down version of it and successfully did it by using superr's kitchen. and also using the kitchen i removed the encryption on the boot.img and then patched it using magisk for easy rooting without recovery. when flashed together with the modded system.img and modded boot.img and twrp, i was totally in control of my device.
If you need any help with anything mtk send me a pm
also are you able to access internal storage in twrp or not ??

andromodgod said:
If you need any help with anything mtk send me a pm
also are you able to access internal storage in twrp or not ??
Click to expand...
Click to collapse
I can access internal storage in twrp. There's a choice to select the internal storage. Havent backed up to it or anything. But its there. I copied a file into it through TWRP now, and it works. I think its all about the fstab. If you don't get access to internal storage, see for any red errors in TWRP output. I can look into my fstab to see what's relevant.
I have a little hiccup though. Now my network drops (both sim at a time), even during a call. But maybe its because I swapped sim 1 and sim 2. I'll let things settle and see if it will persist. In the meanwhile, I swapped sims back to original.

bad.bid said:
I can access internal storage in twrp. There's a choice to select the internal storage. Havent backed up to it or anything. But its there. I copied a file into it through TWRP now, and it works. I think its all about the fstab. If you don't get access to internal storage, see for any red errors in TWRP output. I can look into my fstab to see what's relevant.
I have a little hiccup though. Now my network drops (both sim at a time), even during a call. But maybe its because I swapped sim 1 and sim 2. I'll let things settle and see if it will persist. In the meanwhile, I swapped sims back to original.
Click to expand...
Click to collapse
i wasn't able to access internal storage at first because device was encrypted beforehand. also sim issues might be caused by imei/nvram . check if your device imei matches your imei on the device box.

andromodgod said:
i wasn't able to access internal storage at first because device was encrypted beforehand. also sim issues might be caused by imei/nvram . check if your device imei matches your imei on the device box.
Click to expand...
Click to collapse
Ya, I fixed Imei issues. this one is like a signal drop once every 15 minutes.

bad.bid said:
I successfully ported TWRP to Panasonic Eluga Note (MTK6753) after a four day effort. Not a dev here. First time doing this.
<TLDR? skip this>
When I started using android in my HTC HD2, every ROM was pre rooted. I took it for granted.
So I get this cheapo MTK and breaking into it is like banging head against a wall!! I was frustrated with the battery drain: Device never sleeps since the last OTA!
So I learnt SP flash tools and downgraded. ( wiped nvram and created another mess in the process- which is a different story. I solved it)
I could spend this effort and time to stop that pesky "Panasonic" bootaudio too. And that's the first thing I deleted after I booted TWRP, even before rooting.
</TLDR? skipped this>
First things first, enable ADB, enable OEM unlock in developer options, and go to bootloader to unlock it <fastboot oem unlock> THIS WILL WIPE DATA!!
Second thing: Backup nvram.img by sp flash readback and learn how to flash it back (search XDA)- Sometimes you can learn from other's mistakes too! I spent a day and half writing back IMEI and WIFI Mac.
Process (if you don't trust me and want to reproduce the steps yourself)
1. Download stock firmware. (google knows)
2. Patch boot.img so that it doesn't overwrite TWRP with stock recovery on each boot (extract by Carliv Image kitchen and hash out the three lines 663, 664 and 665 mentioning "service flash_recovery /system/bin/install-recovery.sh" in init.rc). I created two copies in the same folder (boot.img, and boot-verified.img) and copied scatter into the same folder for flashing. That's what I saw in the firmware folder.
3. Port TWRP using Carliv Image Kitchen method. I downloaded TWRP from here https://forum.xda-developers.com/android/software/twrp-porter-maker-mediatek-mt67xx-32-t3681861 but didn't use their method. It didn't work. The TWRP for this chip was stated as android N, but worked well.
4. Flash ported TWRP after copying scatter file to the Carliv Imagekitchen output folder and selecting that scatter in SP droid tools. I again created recovery.img and recovery-verified.img. Don't know if its needed that way. You could wait and flash boot and recovery together from the same folder.
5. That's it, you can enter custom recovery now. Get that pesky "panasonic" bootaudio off the system/media folder now! You can stay content after this or proceed to root.
<nandroid backup now, including Nvram and NVdata. Just in case>
6. Download Supersu zip flashable and flash it via TWRP. https://download.chainfire.eu/1113/SuperSU/UPDATE-SuperSU-v2.82-20170528234214.zip?retrieve_file=1 worked for me.
7. Reboot, check root!
If you're more daredevil,
8. Download Xposed flashable zip SDK23 and flash it. Download Xposed installer and copy it to SDcard too.
9. Reboot to recovery and flash the zip. Reboot, install xposed installer. Reboot again.
You're done!
I'll upload my boot.img and ported TWRP if anyone shows any interest in this.
Cheers!
(Bonus: this phone has built in IPtables support in the kernel! I used to flash custom kernel for this ability in other Stock ROMs. AFfirewall works "out of the box"- after rooting, of course!)
Edit: uploaded my modded boot.img and ported TWRP. find it here https://drive.google.com/file/d/1sM1BnyBUFN7PfncFcM7vzIet6gKt3G_L/view?usp=sharing
If you want to go the easy route, unzip the folder and flash it with sp flash. You'll be able to boot into recovery and do the other steps for rooting.
Rememer ONLY DOWNLOAD, don't format, or format and download, or anything!
Click to expand...
Click to collapse
Can you please mention the steps and software needed for rooting the device plz plz plz

gt612 said:
Can you please mention the steps and software needed for rooting the device plz plz plz
Click to expand...
Click to collapse
No need to quote the whole post!
Download twrp and boot from here. https://drive.google.com/file/d/1sM1BnyBUFN7PfncFcM7vzIet6gKt3G_L/view?usp=sharing
download super su from the link in original post. flash iso files in the twrp boot zip (they are for the updated latest version of android 6.0.1). flash supersu via twrp. search for how to do these things.

Hello. I have an Allveiw V2 Viper S (the romanian version fo the eluga note). I got a stock rom (not from my phone) from where i took and modified both the boot.img and the recovery.img and also used the scatter from here to. I couldn`t make mtk droid tools to see my device. I managed to unlock the bootloader, but when i tried to flash the boot and recovery spft gave me a " Obtain DRAM Faild" error. Can you please help?
Thanks!

madhogg said:
Hello. I have an Allveiw V2 Viper S (the romanian version fo the eluga note). I got a stock rom (not from my phone) from where i took and modified both the boot.img and the recovery.img and also used the scatter from here to. I couldn`t make mtk droid tools to see my device. I managed to unlock the bootloader, but when i tried to flash the boot and recovery spft gave me a " Obtain DRAM Faild" error. Can you please help?
Thanks!
Click to expand...
Click to collapse
This was an impulse project. I learned many things in the way. But I have left that effort behind. So, for now: no idea. Hope google helps!

bad.bid said:
I successfully ported TWRP to Panasonic Eluga Note (MTK6753) after a four day effort. Not a dev here. First time doing this.
<TLDR? skip this>
When I started using android in my HTC HD2, every ROM was pre rooted. I took it for granted.
So I get this cheapo MTK and breaking into it is like banging head against a wall!! I was frustrated with the battery drain: Device never sleeps since the last OTA!
So I learnt SP flash tools and downgraded. ( wiped nvram and created another mess in the process- which is a different story. I solved it)
I could spend this effort and time to stop that pesky "Panasonic" bootaudio too. And that's the first thing I deleted after I booted TWRP, even before rooting.
</TLDR? skipped this>
First things first, enable ADB, enable OEM unlock in developer options, and go to bootloader to unlock it <fastboot oem unlock> THIS WILL WIPE DATA!!
Second thing: Backup nvram.img by sp flash readback and learn how to flash it back (search XDA)- Sometimes you can learn from other's mistakes too! I spent a day and half writing back IMEI and WIFI Mac.
Process (if you don't trust me and want to reproduce the steps yourself)
1. Download stock firmware. (google knows)
2. Patch boot.img so that it doesn't overwrite TWRP with stock recovery on each boot (extract by Carliv Image kitchen and hash out the three lines 663, 664 and 665 mentioning "service flash_recovery /system/bin/install-recovery.sh" in init.rc). I created two copies in the same folder (boot.img, and boot-verified.img) and copied scatter into the same folder for flashing. That's what I saw in the firmware folder.
3. Port TWRP using Carliv Image Kitchen method. I downloaded TWRP from here https://forum.xda-developers.com/android/software/twrp-porter-maker-mediatek-mt67xx-32-t3681861 but didn't use their method. It didn't work. The TWRP for this chip was stated as android N, but worked well.
4. Flash ported TWRP after copying scatter file to the Carliv Imagekitchen output folder and selecting that scatter in SP droid tools. I again created recovery.img and recovery-verified.img. Don't know if its needed that way. You could wait and flash boot and recovery together from the same folder.
5. That's it, you can enter custom recovery now. Get that pesky "panasonic" bootaudio off the system/media folder now! You can stay content after this or proceed to root.
<nandroid backup now, including Nvram and NVdata. Just in case>
6. Download Supersu zip flashable and flash it via TWRP. https://download.chainfire.eu/1113/SuperSU/UPDATE-SuperSU-v2.82-20170528234214.zip?retrieve_file=1 worked for me.
7. Reboot, check root!
If you're more daredevil,
8. Download Xposed flashable zip SDK23 and flash it. Download Xposed installer and copy it to SDcard too.
9. Reboot to recovery and flash the zip. Reboot, install xposed installer. Reboot again.
You're done!
I'll upload my boot.img and ported TWRP if anyone shows any interest in this.
Cheers!
(Bonus: this phone has built in IPtables support in the kernel! I used to flash custom kernel for this ability in other Stock ROMs. AFfirewall works "out of the box"- after rooting, of course!)
Edit: uploaded my modded boot.img and ported TWRP. find it here https://drive.google.com/file/d/1sM1BnyBUFN7PfncFcM7vzIet6gKt3G_L/view?usp=sharing
If you want to go the easy route, unzip the folder and flash it with sp flash. You'll be able to boot into recovery and do the other steps for rooting.
Rememer ONLY DOWNLOAD, don't format, or format and download, or anything!
Click to expand...
Click to collapse
Brother i try this method at Panasonic eluga ray 700 (MT6753_EB_90S55ER7_V1008) flash complete and successful install problem my set dead not On so i install original Panasonic eluga ray 700 (MT6753_EB_90S55ER7_V1008) flash set is dead and not connecting to pc plz help me what i can do ......

andromodgod said:
Brilliant Work man. I also was sort of in your situation as well . i have a panasonic Eluga A3 (Qmobile Noir E2) in my country. Stock Qmobile rom was horrendous. so i flashed the panasonic rom but hated the boot audio and the bloatware that came with it. so i decided to make a slimmed down version of it and successfully did it by using superr's kitchen. and also using the kitchen i removed the encryption on the boot.img and then patched it using magisk for easy rooting without recovery. when flashed together with the modded system.img and modded boot.img and twrp, i was totally in control of my device.
If you need any help with anything mtk send me a pm
also are you able to access internal storage in twrp or not ??
Click to expand...
Click to collapse
Panasonic eluga ray 700 (MT6753_EB_90S55ER7_V1008) after flash set is dead and not connecting to pc plz help us expert......
....

Network drop
Hello dear friend I successfully flash twrp 3.0.2 but I see network signal problem signal drop many time..
Pls tell me how to resolve these issue..

Singnal drop
bad.bid said:
Ya, I fixed Imei issues. this one is like a signal drop once every 15 minutes.
Click to expand...
Click to collapse
Dear sir panasonic eluga note network signal drop many time a day after installing ur ported twrp ..Pls tell me how to resolve signal drop issue..

Really wanna do it but your steps sound way complicated for "non-MTK pro guy". I have that device lying unused. it would be awesome if you could throw a "readme" file in your drive or here with simpler guidance steps like other "TWRP & root installation guide" we have for other phones. Plus You seem like you could port/build a ROM for this device and make substratum friendly. I know it's a big ask & I have a feeling that you like dark UI for that device too . Hoping for the best response.

If you're more daredevil,
8. Download Xposed flashable zip SDK23 and flash it. Download Xposed installer and copy it to SDcard too.
9. Reboot to recovery and flash the zip. Reboot, install xposed installer. Reboot again.
I have a doubt about these two steps
Should i have to flash it twice and have to download two separate file which is one flashable zip and installer. And in the next step 9th which zip file should i flash.
My questions might sound silly but i am asking so because when last time i tried i installed xposed, installed its firmware and then downloaded a module it was cynolockscreen something and applied it. It asked ne to reboot i did but then my phone crashed. Screen was going on and off then i rebooted to recovery and did a factory reset amd since then i haven't done any thing in my phone not even flashed the SuperSU...
Can you please help me with the further steps...

rooting eluga note
can u pls tell me how to root eluga note? i've tried many apps to root it but nothing worked