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, 01:06 AM
Post Reply Email Thread
7th September 2017, 08:21 PM |#11  
rajeshca911's Avatar
Member
Flag Vizag
Thanks Meter: 10
 
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
 
 
9th September 2017, 08:51 PM |#12  
Senior Member
Thanks Meter: 37
 
Donate to Me
More
Quote:
Originally Posted by rajeshca911

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

I empathize with your frustration.

Truth is that with the devices which have not caught the fancy of developers, not having proven root methods, custom recovery, etc only, we take initiatives ourselves and learn the things the hard way which is essentially a true way learning. With popular devices having already so many developments, there is no scope for adventurism and fun as well.

Just see back what are all you gained in doing the things you did with your device for gaining root. Could it have been possible with the so called popular devices?

Now let's come to the issue. In all times of failed booting on compiled imgs, how did you restore them? flashing again stock boot and recovery imgs? and with tools you mentioned?

If you could flash stock boot and recovery with the tools you mentioned, then there is no problem with those flashing tools. Then it comes to the decompiling and recompiling of imgs.

If it could be possible, can you share here stock boot.img, and custom recovery you have selected for porting (also mention the device name, recovery pertained). Let me try.
10th September 2017, 05:26 AM |#13  
rajeshca911's Avatar
Member
Flag Vizag
Thanks Meter: 10
 
More
Yup.. Bro.
What have you said all true.. during this journey i have learned so manythings like porting custom recovery , read back firmware etc and i cant forget what i have learned.. so many trail and errors

below link is the stock and custom recovery i tried to port

https://drive.google.com/file/d/0B6w...?usp=drive_web

and a developer also tried to to port recovery for me .. below is the link which he modified for me
https://www.androidfilehost.com/?fid=745425885120760137

Im also enclosing stock boot.img
https://mega.nz/#!MF1ySQ4D!ku6RWfOP8...43J0I0tiCHRa8k

My Device Details are
Manufacture : Oppo
Device name : Oppo f3
Model No : CPH1609
chipset : MT6750T , 4gb Ram , 64 Gb storage

[ I Really praying Inside .... god may give result for our endless efforts }
10th September 2017, 09:30 PM |#14  
Senior Member
Thanks Meter: 37
 
Donate to Me
More
@rajeshca911 can you give details for the custom recovery you have given links, like name of the device, its os ( lollipop, marshmallow, like), and chipset if possible, it pertained to.
11th September 2017, 05:28 AM |#15  
rajeshca911's Avatar
Member
Flag Vizag
Thanks Meter: 10
 
More
Quote:
Originally Posted by shankar_vl

@rajeshca911 can you give details for the custom recovery you have given links, like name of the device, its os ( lollipop, marshmallow, like), and chipset if possible, it pertained to.

Aquired custom recovery from
Device : qukitel K6000 plus, chipset MT6750T
android version 6.0 (from below)
https://www.google.co.in/amp/s/forum...-t3620241/amp/
13th September 2017, 08:29 AM |#16  
Junior Member
Thanks Meter: 1
 
More
Quote:
Originally Posted by rajeshca911

Aquired custom recovery from
Device : qukitel K6000 plus, chipset MT6750T
android version 6.0 (from below)
https://www.google.co.in/amp/s/forum...-t3620241/amp/

I think the signature of the boot.img gets changed. Try to sign it after decompiling and recompiling by AVB patcher from here: https://forum.xda-developers.com/and...ified-t3600606
13th September 2017, 09:57 AM |#17  
rajeshca911's Avatar
Member
Flag Vizag
Thanks Meter: 10
 
More
Quote:
Originally Posted by anandverma458

I think the signature of the boot.img gets changed. Try to sign it after decompiling and recompiling by AVB patcher from here: https://forum.xda-developers.com/and...ified-t3600606

Shall i sign both boot.img and recovery.img as well?? or is it enough to sign compiled recovery.img ?

---------- Post added at 07:57 AM ---------- Previous post was at 07:44 AM ----------

i generated public and private keys also signed and generated
boot_signed.img
recovery_signed.img

first i flashed both the images... result was soft brick and i had to flash original boot.img
second i flashed only signed recovery.img and same was repeated.
13th September 2017, 10:10 AM |#18  
Junior Member
Thanks Meter: 1
 
More
Quote:
Originally Posted by rajeshca911

Shall i sign both boot.img and recovery.img as well?? or is it enough to sign compiled recovery.img ?

---------- Post added at 07:57 AM ---------- Previous post was at 07:44 AM ----------

i generated public and private keys also signed and generated
boot_signed.img
recovery_signed.img

first i flashed both the images... result was soft brick and i had to flash original boot.img
second i flashed only signed recovery.img and same was repeated.

Actually, I had the same problem (I have vivo 1603). When I flashed boot.img after decompiling and recompiling,it bootlooped. I had twrp installed, so I first restored the backup of stock boot.img, and then installed the recompiled boot.img without rebooting. That worked for me

As you don't have custom recovery, I suggest that you first flash stock boot.img, and after the process completes, flash the recompiled boot.img without rebooting your device.
13th September 2017, 11:10 AM |#19  
Senior Member
Thanks Meter: 37
 
Donate to Me
More
Hey bro, I decompiled the stock boot.img to see that if 'verify' flag was preventing booting the system with other than stock recovery. Dm-verity is a recent security control for preventing booting with changed/modified kernel/system. But I could not find any such flags, but found verity_key, so I just deleted it and decompiled the boot.img. I am not sure whether it can solve your booting problem. Let's see will this now allow to boot with custom kernel. Here is the modified stock boot.img. http://www.mediafire.com/file/tc1k1g..._oppo_boot.img

Flash first this boot.img and then flash the custom recovery.imgs (you can try your recoveries also)

I have also ported two recovery.imgs. Both are ported from the twrps for the same device, K6000 plus. However, what I found for this k6000 plus was different in size. So I ported two twrp recovery imgs. Here are two twrp ported recoveries, one is from you have given links to and another is from what I found on this forum.
http://www.mediafire.com/file/4als7q...ort_twrpv1.img
http://www.mediafire.com/file/5xz738...ort_twrpv2.img

Once again, I reiterate that first flash the modified boot.img and then try flashing the recoveries.

Best of luck
13th September 2017, 02:03 PM |#20  
rajeshca911's Avatar
Member
Flag Vizag
Thanks Meter: 10
 
More
Quote:
Originally Posted by anandverma458

Actually, I had the same problem (I have vivo 1603). When I flashed boot.img after decompiling and recompiling,it bootlooped. I had twrp installed, so I first restored the backup of stock boot.img, and then installed the recompiled boot.img without rebooting. That worked for me

As you don't have custom recovery, I suggest that you first flash stock boot.img, and after the process completes, flash the recompiled boot.img without rebooting your device.

Bro thanks for your advice.. and i did same what you have said.. i flashed stock boot.img with out rebooting flashed recompiled boot.img the device didnt boot up.. i think culprit is something else .. that prevets booting custom images
13th September 2017, 02:20 PM |#21  
rajeshca911's Avatar
Member
Flag Vizag
Thanks Meter: 10
 
More
Quote:
Originally Posted by shankar_vl

Hey bro, I decompiled the stock boot.img to see that if 'verify' flag was preventing booting the system with other than stock recovery. Dm-verity is a recent security control for preventing booting with changed/modified kernel/system. But I could not find any such flags, but found verity_key, so I just deleted it and decompiled the boot.img. I am not sure whether it can solve your booting problem. Let's see will this now allow to boot with custom kernel. Here is the modified stock boot.img. http://www.mediafire.com/file/tc1k1g..._oppo_boot.img

Flash first this boot.img and then flash the custom recovery.imgs (you can try your recoveries also)

I have also ported two recovery.imgs. Both are ported from the twrps for the same device, K6000 plus. However, what I found for this k6000 plus was different in size. So I ported two twrp recovery imgs. Here are two twrp ported recoveries, one is from you have given links to and another is from what I found on this forum.
http://www.mediafire.com/file/4als7q...ort_twrpv1.img
http://www.mediafire.com/file/5xz738...ort_twrpv2.img

Once again, I reiterate that first flash the modified boot.img and then try flashing the recoveries.

Best of luck

Bro first of all Thanks for the efforts & time you allocated for my device.. coz you confirmed that verification was not in boot.img though i flashed your boot.img and the device didnt boot up. it showed an error saying boot was corrupted please take to service centre "so i have googled again and found interesting things about preloader.bin , below link was video tutorial to flash modified preloader.bin for mt6753 device
https://www.youtube.com/watch?v=YS1GFPJB53Q
he used modified preloader.bin to boot into custom recovery.img so i assume that preloader.bin have keys/checksums to verify the boot and recovery images
the same topic was going on xda
https://forum.xda-developers.com/and...t2909259/page3

but unfortunately i have no enough knowledge about editing preloader.bin so it may take some time google/learn and flash.
i believe your custom images will be prefect after deriving solution. i will update my progress soon. please do share if you know anything about the same.

Click image for larger version

Name:	Untitled.png
Views:	30
Size:	26.0 KB
ID:	4271201

Thanks in advance
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