FORUMS
Remove All Ads from XDA

Manually patch boot.img for systemless root?

22 posts
Thanks Meter: 3
 
By MalikDrako, Junior Member on 7th January 2017, 12:06 AM
Post Reply Email Thread
I have a rare phone running Android 6.0 on a MT6750 with an unlocked bootloader (might be MT6750T since it is 1920x1080, but the only things I have found say MT6750)

I have been unable to get TWRP working on this phone after trying several porting guides and TWRP images. Almost all port attempts result in the boot image (logo.bin - android logo), followed by a black screen for a few seconds, then it reboots into Android.

Is it possible to manually patch the boot.img to gain root? If so, can someone point me to a guide for it? I found https://forum.xda-developers.com/and...iatek-t3309909 but PATH doesnt seem to be set anywhere in my boot image (grep -nrw 'boot.img-ramdisk' -e "PATH"). I tried adding "export PATH $PATH:/data/bin" or "export PATH /sbin:/vendor/bin:/system/sbin:/system/bin:/system/xbin::/data/bin" to init.environ.rc with other exports, but I get a boot loop
 
 
4th May 2017, 09:57 AM |#2  
Member
Thanks Meter: 26
 
More
try recompile the decompiled boot.img without doing any changes and flash the compiled boot.img to see that there is no problem with respect to compilation of boot.img
7th September 2017, 11:45 AM |#3  
rajeshca911's Avatar
Member
Flag Vizag
Thanks Meter: 8
 
More
Quote:
Originally Posted by shankar_vl

try recompile the decompiled boot.img without doing any changes and flash the compiled boot.img to see that there is no problem with respect to compilation of boot.img

i decompiled and recompiled without any changes using kitchen tools and flashed back ... but its showing error.
same with recovery.img also


btw im using oppo f3 mt6750t
7th September 2017, 12:20 PM |#4  
Member
Thanks Meter: 26
 
More
Quote:
Originally Posted by rajeshca911

i decompiled and recompiled without any changes using kitchen tools and flashed back ... but its showing error.
same with recovery.img also


btw im using oppo f3 mt6750t

Then its a compilation error. Its not being compiled correctly.
Btw, systemless root by supersu and magisk do a lot things like starting sudaemon, injecting supolicy changes, mounting su.img, etc. Its better to port a custom recovery and let supersu or magisk zip do all the required things to root your device.

Or if you want to be ambitious, dirty your hands with hackings, unzip these zip files and try to implement manually what is programmed there.

My suggestion is go for porting recovery from devices matching your device specs ( need not be 100%). There are several threads on this forum helping you out on this. I think chances of porting a workable custom recovery are brighter than manually compiling su compatible boot.img.
7th September 2017, 12:48 PM |#5  
rajeshca911's Avatar
Member
Flag Vizag
Thanks Meter: 8
 
More
There's the problem..
I did port custom recovery.
But when I flash it back to device it's showin error.

I understand that I need to dirt my hands more to get root my device

So I decided to compile revovery.. But oppO f3 source files r not available. I tried with omni Tom source. But it failed
7th September 2017, 04:50 PM |#6  
Member
Thanks Meter: 26
 
More
Quote:
Originally Posted by rajeshca911

i decompiled and recompiled without any changes using kitchen tools and flashed back ... but its showing error.
same with recovery.img also


btw im using oppo f3 mt6750t

Quote:
Originally Posted by rajeshca911

There's the problem..
I did port custom recovery.
But when I flash it back to device it's showin error.

I understand that I need to dirt my hands more to get root my device

So I decided to compile revovery.. But oppO f3 source files r not available. I tried with omni Tom source. But it failed

You said that even the imgs just compiled without any changes made to decompiled files are not able to boot. Then there must be something wrong with compiling. Your tools for compiling may not be correctly working.

There are carlive image kitchen tools. get them here https://forum.xda-developers.com/and...droid-t3013658. They are known for flawless working.

What is more important now is that you have right tools for compiling imgs. Then you can think of further.
7th September 2017, 05:38 PM |#7  
rajeshca911's Avatar
Member
Flag Vizag
Thanks Meter: 8
 
More
Quote:
Originally Posted by shankar_vl

You said that even the imgs just compiled without any changes made to decompiled files are not able to boot. Then there must be something wrong with compiling. Your tools for compiling may not be correctly working.

There are carlive image kitchen tools. get them here https://forum.xda-developers.com/and...droid-t3013658. They are known for flawless working.

What is more important now is that you have right tools for compiling imgs. Then you can think of further.

Thanks bro. But im using carliv kitchen tools only.
I didn't tried with other kitchen tools yet.. So i give a try other tools
7th September 2017, 05:59 PM |#8  
Member
Thanks Meter: 26
 
More
Quote:
Originally Posted by rajeshca911

Thanks bro. But im using carliv kitchen tools only.
I didn't tried with other kitchen tools yet.. So i give a try other tools

no need. carliv tools are perfect. stick with them.

are you able to successfully flash imgs with sp flash tools? no matter whether you are able to boot with them.

as for porting, use twrp or any other custom recovery of SoC as yours, mt6750t and of OS version similar to yours as well.
7th September 2017, 06:14 PM |#9  
rajeshca911's Avatar
Member
Flag Vizag
Thanks Meter: 8
 
More
Quote:
Originally Posted by shankar_vl

no need. carliv tools are perfect. stick with them.

are you able to successfully flash imgs with sp flash tools? no matter whether you are able to boot with them.

as for porting, use twrp or any other custom recovery of SoC as yours, mt6750t.

Ok.. I stick with carliv as u suggested. And... Yes... Im able to flash img files to phone but not with sp flash tools. Im using professional tools ( uni tools from volcano) and also flashing using a cracked download tool meant for oppo devices. ( the download tool was created on base of sp flash tools only)

Then...
I just tried twrp porting only ( same soc mt6750t quitel k6000 plus i think.. Which chipset is mt6750t)
Also tried with oppo f1s twrp which chipset is mt6750.. ( not 6750t.. ) both went wrong..
seniors and xda developrs ( zackie& a guy from Indonesia unfortunately i forgot his name) also tried to. Port twrp for me. I also tried flashing their img files ..everything went not well.. There i have understood that either compiling or flashing causing error in my device
Thats y im trying to find other wayz.. There i found ur thread .& fetching useful checklist
7th September 2017, 06:40 PM |#10  
Member
Thanks Meter: 26
 
More
Quote:
Originally Posted by rajeshca911

Ok.. I stick with carliv as u suggested. And... Yes... Im able to flash img files to phone but not with sp flash tools. Im using professional tools ( uni tools from volcano) and also flashing using a cracked download tool meant for oppo devices. ( the download tool was created on base of sp flash tools only)


Then...
I just tried twrp porting only ( same soc mt6750t quitel k6000 plus i think.. Which chipset is mt6750t)
Also tried with oppo f1s twrp which chipset is mt6750.. ( not 6750t.. ) both went wrong..
seniors and xda developrs ( zackie& a guy from Indonesia unfortunately i forgot his name) also tried to. Port twrp for me. I also tried flashing their img files ..everything went not well.. There i have understood that either compiling or flashing causing error in my device
Thats y im trying to find other wayz.. There i found ur thread .& fetching useful checklist

As you tried various flashing methods, you might have already known all the related intricasies of flashing. still I just want to mention that I presume you might have then known vcom drivers, creating scatter file with mtkdroid tools, loading scatter file and, most importantly switching off phone and plugging phone to PC just after clicking on flash button in sp flash tool.

And about the other tools of flashing you mentioned, sorry I will not be helpful.

A thing to mention regarding porting is taking care of mount points in fstab file and a similar file if any at /etc folder in ramdisk of decompiled port recovery. mount points should be same as fstab of your boot.img.

Besides, ensure kernel (Imaze) of port recovery is replaced with that of boot.img.
7th September 2017, 07:21 PM |#11  
rajeshca911's Avatar
Member
Flag Vizag
Thanks Meter: 8
 
More
Quote:
Originally Posted by shankar_vl

As you tried various flashing methods, you might have already known all the related intricasies of flashing. still I just want to mention that I presume you might have then known vcom drivers, creating scatter file with mtkdroid tools, loading scatter file and, most importantly switching off phone and plugging phone to PC just after clicking on flash button in sp flash tool.
And about the other tools of flashing you mentioned, sorry I will not be helpful.

A thing to mention regarding porting is taking care of mount points in fstab file and a similar file if any at /etc folder in ramdisk of decompiled port recovery. mount points should be same as fstab of your boot.img.

Besides, ensure kernel (Imaze) of port recovery is replaced with that of boot.img.

Your not helpfull??.. I don't agree with that. May be im Not in the position to catch your mind.
However.. Im not going to miss single chance to upgrade myself ( yes ofcourse from devs n seniors like u)
As you said
1) i have installed vcom drivers & fetched scatter file. ( again not from mtk droid tools) . I heard mtkdroid tools nOt fully supporting mt67xx Series. Even i tried modified mtkdroid tools developed by dev havoc.. And droid tool showed some info like cpu info.. Etc. But right hand side there was an error which saying that its usable to fetch info. . I presume the error may b causing by oppo. Own OS ( Color OS based on android 6.0).. And my last try was 2 months ago. So i dont know if there is any improvements in droid tools or not. Please privide me links if they updated/ supported 67xx series

2)yes i agree with mount points you mentioned. I was just replacing fstab file from stock to. Port. I didnt edit any. . I will check again and update u.

3) Actually im in dilemma to blame on cimpiling or flashing.. The device is not booting even i didn't modify any item after repack. I need solution for that. If that resolved... Automatically everything will b set up by themselves.. Pls share any views regarding this..
I know its difficult to u to guide until u have hands on it or personally seen d procedures & results

I may upload videos / pictures/ share Team viewer etc.. if u want to see it personally.. So.. U can better understand my problem , my flaws where i need to b improved ( onlynif u wish) however i need a mentor to guide n judge methods im following
Post Reply Subscribe to Thread

Guest Quick Reply (no urls or BBcode)
Message:
Previous Thread Next Thread
Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes