I'm trying to compile PAC for Micromax A116
I used these sources :
https://github.com/zeetherocker/android_device_micromax_a116
https://github.com/zeetherocker/android_vendor_micromax_a116
I haven't used a kernel during compilation But the sources are here :
https://github.com/zeetherocker/android_kernel_micromax_a116
The kernel sources are a little different for the mediatek devices... I didn't get the procedure for compiling it so I just removed it and didn't use it for compilation...
The rom compiled without any probs... But then when I flashed it it didn't go beyond the Canvas logo... And I'm not even able to take log... ADB doesn't detect it... I flashed a custom kernel too but no luck still stuck in the same state...
I downloaded cm11 for the device which was ported from a different device for A116... I unzipped it changed a few files from the etc, lib and bin folders.... Then it started showing the bootanimation... But still didn't boot up and still no luck with ADB...
I need help with this... Thanks in advance..!!
twrp Porter-
as we know there is no tool available to port twrp for mt67XX. Phone so here i create a Simple and user friendly tool to Manually Port twrp for the Mediatek MT67XX Phone also Work with MT65XX new 32 bit phone .
The tool is Not based on Source This is a manually Porting Method where we use Stock Recovery to Port a custom Recovery. i have Port twrp for almost all latest MT67XX Chip from source and you can use as a Port Recovery,[Link below]..
What you need
1. tool Download Here https://androidfilehost.com/?fid=962021903579481564
2. Stock recovery [dump using SP tool or using Miracle box] Rename it 'stock.img'
3. Ported twrp from same chip [ Here is My collection- https://www.androidfilehost.com/?w=files&flid=220042] select according your chip if not work try from other phone. rename it 'port.img'
Note- i have Not enable auto copy to keep work with all chip Manually copy Paste Require.
Instructions-
Place port.img and stock.img in tool folder
Run twrp Kitchen.exe and follow on screen instructions
Donation-
You can Donate Me http://paypal.me/droiddeveloper
Faq-
1. Touch Not Work-
it's due to kernel source try to port from other twrp,
final solution use OTG or compile from source.
2. unable to mount partition's-
check and fix fastab in ramdisk folder before hiting enter.
3,. is this Work on old MT65XX Phone-
yes you can use it for MT65XX phone.
4. is This Method work 100% on all Phone-
No it can't work 100% on all phone but work on up to 90% of Mediatek Phone.
5. is this Support Nougat and oreo Images-
yes this one Support oreo and Nougat Recovery Images.
XDA:DevDB Information
twrp porter , Tool/Utility for all devices (see above for details)
Contributors
XN Logos
Version Information
Status: Beta
Current Beta Version: 1.0
Beta Release Date: 2017-09-30
Created 2017-10-01
Last Updated 2018-01-06
@XN Logos
Thanks for the tool.
I cannot download the recovery
MT6757 6.0 MM.rar
MT6757 Nougat helio P25 6GB RAM.zip
MT6797 Helio X27 6.0MM.rar
you can download from androidfilhost.
here is twrp for ulefone t1 ported using this tool base umi plus e. Helio p25, this tool not work on umidigi crystal 4GB/64GB i have tried but not success. https://androidfilehost.com/?fid=673368273298987398
Thank u for your great job, i think the recovery we obtain is called "image-new.img" (and not "recovery-new.img" as it's mentioned in the screen instruction). I successfully get this recovery but don't know how to flash it ( because my phone is locked and not rooted "LENOVO C2- k10a40-" ( MT6735 ). HELP PLZ and thanks again .
walid77dz said:
Thank u for your great job, i think the recovery we obtain is called "image-new.img" (and not "recovery-new.img" as it's mentioned in the screen instruction). I successfully get this recovery but don't know how to flash it ( because my phone is locked and not rooted "LENOVO C2- k10a40-" ( MT6735 ). HELP PLZ and thanks again .
Click to expand...
Click to collapse
You can flash it using SP flash tools, take scatter file from your ROM and then flash with SP tools...
Here is Fastboot Guide, but you can face adbd and large image error with fastboot.
Code:
fastboot oem unlock
fastboot flash recovery recovery-new.img
Please, help me to find usb vcom drivers for my device : LENOVO C2, k10a40, MT6735. Thank u again
walid77dz said:
Please, help me to find usb vcom drivers for my device : LENOVO C2, k10a40, MT6735. Thank u again
Click to expand...
Click to collapse
I beleive that any question not related to TWRP porter is OT here. Check driver v. 5.1632.
mod edit - needrom links removed not allowed due to registration required in order to download
Here is all Flash tools and drivers-
https://androidfilehost.com/?w=files&flid=216849
XN Logos said:
Here is all Flash tools and drivers-
https://androidfilehost.com/?w=files&flid=216849
Click to expand...
Click to collapse
You can get all news about Mediatek driver and tools (like Flashtool) here:
http://www.androidiani.com/forum/mo...l-flash-di-telefoni-con-chipset-mediatek.html
The latest driver (ADB + Preloader) is 5.1632 (the link that I posted), and is good fro XP up to Windows 10 and didn't rqeuire to disable driver sign.
The latest version for Flashtool (for Windows and Linux) is 5.1728
In the link that I posted are available Gogle Platform Tools (adb.exe/fastboot.exe) usefull for flash boot or recovery without using Flashtool.
base added for Helio X23 [Rename rk.bak to recovery.img]
https://androidfilehost.com/?fid=745849072291678959
Hi
great tool for mtk user y have à mt6797M ( elephone s7 4G )
if I understand correctly I need the recovery stock (I have) and a port recovery ( don't have ) but there are none in the link you give., I tried with MT6797 + helio + x25 + 6.0 but I have a MT6797M with android 7, I'm not sure try to flash .
is it possible for you to make a port of the MT6797M Helio X20 M ?
And my fil name: image-new.img not recovery-new.img it's normal ?
Thinking i got same request as Bradco but MT6753M chip Cubot Cheetah 2
I was not able to find the "1st kernel file", guessing it is xx.img-zImage file.
Here my device nougat stock recovery (or at page 4 device review)
With my device at the moment TWRP seems to work only on Marshmallow. It would be nice if someone like to share an updated recovery
BTW
It took me a few retries to check extracting recoveries requiers 3 or 4 times press enter instead of just a singel press any key
@toBsucht Psp @Bradco we have twrp for both Phone 1. Elephone S7 and 2.cubot cheetah 2 no need to Port again. search Forum..
XN Logos said:
@toBsucht Psp @Bradco we have twrp for both Phone 1. Elephone S7 and 2.cubot cheetah 2 no need to Port again. search Forum..
Click to expand...
Click to collapse
yes there is this twrp: TWRP 3.0.3 by Jemmini (I have it) available on needrom and xda
it works with android 6 without problem but not with android 7.
This TWRP 3.0.3 by Jemmini is based on rom: S7_4g_20170110092009_v1.9.zip which is a rom android 6: https://bbs.elephone.hk/thread-12895-1-1.html#.WdiBplu0OM
My rom got this one: s7_4g_20170814163417_v2.4.zip which android 7 v2.4
I tried this :
1. clean install the rom: s7_4g_20170814163417_v2.4.zip
2. start the phone
3. flash the twrp : TWRP_303_Elephone_S7_4g_v1.9
4. reboot the phone but it is blocking on the logo ( I access the recovery but can not start the phone )
5. y tried 2/3 times but once the recovery install it remains on the logo.
after searching I found only this recovery TWRP_303_Elephone_S7_4g_v1.9
I do not know if there is an update because all DROPbox links are down.
@Bradco
Please read carefully the object of this thread. It's only about TWRP porter.
Is not a thread of support for mod recovery about specific devices.
For this please post in the specific thread for the device. Thanks.
@XN Logos
I propose to add this as first object of firs post
- Scope of this thread
Scope of this thread is only to discuss about TWRP porter application.
Please don't discuss about support for recovery for specific devices.
For this please post in the specific thread for the devices.
bovirus said:
@Bradco
Please read carefully the object of this thread. It's only about TWRP porter.
Is not a thread of support for mod recovery about specific devices.
For this please post in the specific thread for the device. Thanks.
@XN Logos
I propose to add this as first object of firs post
- Scope of this thread
Scope of this thread is only to discuss about TWRP porter application.
Please don't discuss about support for recovery for specific devices.
For this please post in the specific thread for the devices.
Click to expand...
Click to collapse
yes sorry,
I explain just my situation, the subject of my post is well on the port of TWRP for processor MT6797M and not on elephone s7. I must speak well of the phone to explain the problem correctly.
Ps : y test this tuto : https://forum.xda-developers.com/showthread.php?p=32965365#post32965365
but y don't find the file BoardConfig.mk
Pretty much same here!
i took a look to default.prop it use a string:
ro.build.version.sdk=24 (stock v14 recovery)
ro.build.version.sdk=23 ( twrp recovery)
even more that needs to be updated in default.prop file from old TWRP to enable it on API24 i.g.
ro.build.fingerprint (seems to be a littel more work)
i stopped repacking TWRP since i note bad image maybe brick my phone.
Also someone told me marshmallow uses ID_creation code = MOB30J; Nougat uses ID_creation code = NHG47N .... idk
funny i removed a additioinal password request. Another user now got additional :highfive: and idk how it occur
Yes Guys, This thread is only for tool Not for Specific Device. So you can ask only for Port base [MT67XX] not for twrp. if you need twrp You can contact Me or create yourself using tool.
XN Logos said:
Yes Guys, This thread is only for tool Not for Specific Device. So you can ask only for Port base [MT67XX] not for twrp. if you need twrp You can contact Me or create yourself using tool.
Click to expand...
Click to collapse
ok I understand, I want to try to do it myself, can you make a port of MTK 6797M ?
( this is what I needed at the start, I came on this thread to do the twrp myself.
thank you in advance
As already written it is not that easy to use if some errors occur. Also i did not 100% on it which files i have to remove if tool say "delete following":
1. kernel (is it x.img-zImage?)
2. kernel offset (i guess i found)
and that flase "press ANY key" message! Just as a little sidenote for your update.
I just spent a few days compiling this kernel. Fixed the paths and whatnot for RNDIS, etc. Its compiling fine but upon packing it with AnyKernel2 and flashing, I get a System Destroyed message, where I have to boot a TWRP img via fastboot and restore a working boot.img. I tried a brand new kernel source with no edits as well, same issue. What am I missing?
I did a make for tissot-perf_defconfig first, then I built it with make -j4 (i have 4 threads). Compiles to a Image.gz-dtb, place it in the AnyKernel2 root and zip it and flash. Flashes fine, boot fails before boot anim.
I tried manually packing the kernel into a boot.img i pulled from a TWRP backup (RR), but fastboot complains its missing DTB no matter which kitchen I use (AIK, Carliv Image Kitchen). Maybe this is the issue?
Thanks!
PS: I'm running it on top of RR 8.1 if that affects anything.
Also is there a Telegram I can join for these questions?
edit: tried pulling the config from a stock boot img using extract-ikconfig. still the same issue booting.
Hi everyone,
I tried searching for a solution, and despite the multiple guides around, I haven't found one for my specific situation.
I have the S6 Lite running Lineage Recovery and Lineage OS 18.1. I have patched the boot.img that was included in the Lineage OS ZIP using Magisk Manager. However, I cannot flash it in any way. I have tried:
flashing using fastboot, however, no matter how I try booting into fastboot, no device is found
flash using heimdall flash --BOOT boot.img, however the error ERROR: Protocol initialisation failed! is shown, despite heimdall print-pit successfully completing
Am I making some silly mistake, or is this not the correct way to root the device? Thank you!
Hi! You shouldn't have to use a patched boot.img unless you're trying to root a stock rom.
With magisk v22 you can just rename the magisk.apk to .zip and flash through lineage recovery adb, this info is in the second paragraph on topjohnwu's magisk github page so please make sure you're not downloading from some shady source (unless you just skimmed straight to the github download then I'd recommend atleast reading the main page so you know what you're doing in the future).
Hopefully this works for you!
Nervusrek said:
Hi! You shouldn't have to use a patched boot.img unless you're trying to root a stock rom.
With magisk v22 you can just rename the magisk.apk to .zip and flash through lineage recovery adb, this info is in the second paragraph on topjohnwu's magisk github page so please make sure you're not downloading from some shady source (unless you just skimmed straight to the github download then I'd recommend atleast reading the main page so you know what you're doing in the future).
Hopefully this works for you!
Click to expand...
Click to collapse
Thank you very much, this worked perfectly! Will read the documentation more carefully next time.
To be fair, the instructions specifically for Samsung are not particularly clear to me either. It jumps from determining the existence of a ramdisk (yes, good), to the SAR=yes section, which goes right into patching the firmware.
Hello, Sorry if this is the wrong place to post this,
I have recently bought an SM-J337U and wanted to root it, I have searched for a TWRP build but there doesn't seem to be one for this phone. I have been able to get magisk working correctly however. I have tried to build TWRP minimal for the device by creating a device tree with the twrpdtgen python script, flashing the resulting image results in a bootloop with only the screen flashing briefly. I have tried for the past few days to change things around in the device tree (boardconfig/fstab) but haven't gotten anything to work. I also tried to build the full omnirom which results in the same bootloop problem (however at one point I was able to get to the recovery screen but there were errors about the cache partition and permission errors). So I'm looking for help in properly building TWRP for this device. If there's any more information that is needed, I am happy to supply it.
Edit: after going back and starting from scratch, it now shows a single line "Unable to normal boot. invalid RAMDISK LENGTH!"