Login

**amhonra** · 2018-08-14, 08:48

(2018-08-10, 18:26)Cleopatra Wrote: [Only registered and activated users can see links Click here to register]

Keep always in mind that onto Oreo something is different (compared to the previous Android versions).
For example : there are "default.prop" and "prop.default".

Good luck

(2018-08-11, 03:13)amhonra Wrote: Thank you Cleopatra, Downloading now, and later I will try again with your tutorial. I succeded last year porting one for a mt6735.

I will keep in touch. Have a great day..
--------------------------------------------------------------------------

Edit :

Files in step 19 of the tutorial dont exist in the ramdisk folder, The structure is different in oreo.

@Cleopatra

Do you think you can help me with the twrp and I make a donation ??

**Cleopatra** · 2018-08-14, 18:07

(2018-08-14, 08:48)amhonra Wrote: @Cleopatra

Do you think you can help me with the twrp and I make a donation ??

I could try.

Actually it is holiday week (the feast of August 15) in Italy.
Please be patient.

Let's talk later then.

**amhonra** · 2018-08-14, 23:03

(2018-08-14, 18:07)Cleopatra Wrote: I could try.

Actually it is holiday week (the feast of August 15) in Italy.
Please be patient.

Let's talk later then.

THank you so much, Enjoy your holidays and be happy please.

I will be surfing the net meanwhile. keep in touch.

**amhonra** · 2018-08-24, 02:12

(2018-08-14, 18:07)Cleopatra Wrote: I could try.

Actually it is holiday week (the feast of August 15) in Italy.
Please be patient.

Let's talk later then.

Hello Cleopatra

Did you enjoy your holiday ?, I hope so.....

Couldnt find anything ( that works ) on the web about rooting and Twrp for UMIDIGI Z2

Can you help me please..

THanks in advance

**amhonra** · 2018-08-26, 11:34

(2018-08-14, 18:07)Cleopatra Wrote: I could try.

Actually it is holiday week (the feast of August 15) in Italy.
Please be patient.

Let's talk later then.

Any news ???

**BMH** · 2018-09-03, 00:31

Hi Cleopatra,

I have phone with MTK6735m chip and could unlock the bootloader but could not root the phone. When I try to flash the TWRP rom via SP Flash tool it is unsucessful.

I did flash the twrp rom via "fastboot flash recovery "location:\recovery.img" and it seem flashed with success. But the phone turn-on and stuck in the logo its all.

I try to boot in recovery and it is nothing also stuck with the logo only.

I think that maybe the problem about the recovery image file that there are something wrong. Can you help me to look its and cook for the me right TWRP ROM for my device? I can send to you the original file of Recovery and scatter file.

Thanks.

P.S. Link recovery file: [Only registered and activated users can see links Click here to register]
Link for scatter file: [Only registered and activated users can see links Click here to register]

**rauliordache** · (This post was last modified: 2018-09-28, 15:52 by rauliordache.)

Hi everyone,

I have two OFFICIAL builds for my device:
- the first one, based on 3.10.65+ kernel, with Lollipop 5.1 and
- the second one, 3.18.35+ kernel, with Nougat 7.0

The first build, has the bootloader locked, and in FastBoot, the volume-UP button doesn't work (for confirming the fastboot oem unlock). So, it cannot be unlocked for further mods.
The second build can be unlocked (the bootloader) - and thus custom ROMs can be booted.

I want to port some ROMs with 3.10.65+ (because all ROMs with 3.18.35+ have some problems on my chipset, MTK6753: gps problems).
I have changed the partition names (in boot.img), and TWRP works great in flashing the new build (3.10.65+), but when booting, it stucks at logo.

Porting ROMs with the same kernel (3.18.35+) works great.
Porting ROMs with the 3.10.65+, even after changing the fstab, kernel (from stock 3.10.65+ boot.img) + partition layouts, cannot be booted. In addition, in the second case, I have changed from boot.img: - all occurrences of
/dev/block/platform/mtk-msdc0/... with
/dev/block/platform/mtk-msdc0/11230000-msdc0/... (fstab, .rc files, update-script, etc.) according with the newer partition layout.

I have tried just to do this with my stock official 5.1 3.10.65+ ROM. It doesn't work (with the preloader+lk.bin unlocked from 3.18)

The question is: Is it possible to have the second build flashed (which has another preloader + lk.bin) from 3.18.35+ - whos bootloader can be unlocked - , and then, using the files from the first build to port a ROM with kernel 3.10.65+ ? Or I am trying the "impossible" ?

In fact, I am not mixing "kernels" regarding boot.img. I am "mixing" a preloader+lk.bin (from one build, which runs Nougat, on 3.18.35+ kernel) with boot.img+system (based on 3.10.65+)
Thank you!

**Cleopatra** · 2018-09-28, 18:07

(2018-09-28, 15:51)rauliordache Wrote: Hi everyone,

I have two OFFICIAL builds for my device:
- the first one, based on 3.10.65+ kernel, with Lollipop 5.1 and
- the second one, 3.18.35+ kernel, with Nougat 7.0

The first build, has the bootloader locked, and in FastBoot, the volume-UP button doesn't work (for confirming the fastboot oem unlock). So, it cannot be unlocked for further mods.

The second build can be unlocked (the bootloader) - and thus custom ROMs can be booted.

I want to port some ROMs with 3.10.65+ (because all ROMs with 3.18.35+ have some problems on my chipset, MTK6753: gps problems).
I have changed the partition names (in boot.img), and TWRP works great in flashing the new build (3.10.65+), but when booting, it stucks at logo.

Porting ROMs with the same kernel (3.18.35+) works great.
Porting ROMs with the 3.10.65+, even after changing the fstab, kernel (from stock 3.10.65+ boot.img) + partition layouts, cannot be booted. In addition, in the second case, I have changed from boot.img: - all occurrences of
/dev/block/platform/mtk-msdc0/... with
/dev/block/platform/mtk-msdc0/11230000-msdc0/... (fstab, .rc files, update-script, etc.) according with the newer partition layout.

I have tried just to do this with my stock official 5.1 3.10.65+ ROM. It doesn't work (with the preloader+lk.bin unlocked from 3.18)

The question is: Is it possible to have the second build flashed (which has another preloader + lk.bin) from 3.18.35+ - whos bootloader can be unlocked - , and then, using the files from the first build to port a ROM with kernel 3.10.65+ ? Or I am trying the "impossible" ?

In fact, I am not mixing "kernels" regarding boot.img. I am "mixing" a preloader+lk.bin (from one build, which runs Nougat, on 3.18.35+ kernel) with boot.img+system (based on 3.10.65+)
Thank you!

Hello,

In my view, you are trying the "impossible"

**powerinside** · 2018-11-04, 09:43

Great work!

**Leemc7433** · 2019-06-27, 06:31

(2016-05-20, 22:25)Cleopatra Wrote: [Only registered and activated users can see links Click here to register]

1) Above all download: [Only registered and activated users can see links Click here to register]
Mirror: [Only registered and activated users can see links Click here to register]

2) Unzip Carliv.zip and click on carliv.bat ... please see the next screenshot :

3) Copy the recovery.img of your stock rom and paste it into the "recovery-resources" folder (inside Carliv unzipped folder) ... please see the next two screenshots :

4) Type R (and press enter), then type 1 (and press enter) ... please see the next screenshot :

5) Type 1 (Unpack image) and press enter ... and see what happens ... please see the next two screenshots :

6) Now you can see the next message : "Your image is unpacked in recovery folder". Open the "recovery" folder (inside Carliv unzipped folder) and you will can see with your own eyes the "ramdisk" folder and the other 10 files ... please see the next screenshot :

7) And this is the content of the "ramdisk" folder (of my unpacked stock recovery) ... please see the next screenshot :

8) Create a folder on your desktop and rename it "stock" ... then copy the entire content of "recovery" folder (the "ramdisk" folder and the other 10 files) and paste them into the folder just created on your desktop (stock folder).
9) Delete your stock recovery.img from "recovery-resources" folder (inside Carliv unzipped folder).
10) Delete all files from the "recovery" folder (inside Carliv unzipped folder).
11) Copy the custom recovery.img (the TWRP that you want to port for your device) and paste it into "recovery-resources" folder.
12) Now repeat the steps 3, 4 and 5 for the custom recovery.img.
13) Create another folder on your desktop and rename it "port" ... then copy the entire content of "recovery" folder (the "ramdisk" folder and the other 10 files) and paste them into the "port" folder.
14) Delete all files (unpacked custom recovery.img) from the "recovery" folder (inside Carliv unzipped folder).
15) DO NOT DELETE the custom recovery.img from "recovery-resources" folder.
16) Open simultaneously the stock folder and the port folder (on your desktop) ... please see the next screenshot :

17) Copy the "recovery.img-kernel" and "recovery.img-kernel_offset" from stock folder ... and paste/overwrite them into port folder. Please see the next screenshot :

18) Open simultaneously the "ramdisk" folder in both stock folder & port folder ... please see the next screenshot :

19) Copy the "fstab" (in my case "fstab.mt6752"), the "meta_init.modem.rc", the "meta_init.project.rc", the "meta_init.rc" and the "ueventd.rc" from stock folder ... and paste/overwrite them into port folder. Please see the next screenshot :

20) You should be able to see the port folder ("ramdisk" folder) like in the next screenshot :

21) Now copy the "ramdisk" folder and the other 10 files from port folder (on your desktop) ... and paste them into "recovery" folder (inside Carliv unzipped folder). Then type 2 (Repack image) and press enter. Please see the next screenshot :

22) "Your new image was repacked as recovery-date-time.img. You can find it in [output] folder". Open "output" folder (inside Carliv unzipped folder) ... and you will find your TWRP ported img. Please see the next screenshot :

23) Now copy the "recovery-date-time.img" from "output" folder and paste it into a new folder on your desktop. Then, rename your ported twrp img like "recovery.img". Copy the scatter file of your stock rom and paste it into the new folder on your desktop (together your ported recovery img). Then, flash it with SP Flash Tool. Please see the next screenshots :

24) Restart your phone in recovery mode ... and see what happens. Please see the next screenshot :

That's all

€5 little papa donate

€10 Big papa donate

€20 Super papa donate
If this tutorial has helped you make a TWRP or learn something new today, consider donating to Cleopatra for her hard work. She has worked selflessly hundreds of hours on CPA here to help users over the years and she would greatly appreciate the show of support.

Hi Cleopatra I was wondering if you can help me, Please bare in mind i am a newbie in this
I have a tablet with a custom build on it which is stopping me from installing simple things like netflix for the kids which is the reason i bought it
am looking for an easy way to install another rom/build onto it (not that bothered what build as long as it works, Thanks)
Current details are as follows:
Brand: hyd
Board: kt096h_101
Device: kt096h_101
Hardware: mt6582
Product: kt096_101
Bootloader: unknown
Build Fingerprint: alps/kt096h_101/kt096h_101:4.4.2/KOT49H/1531192359:user/test-keys
Release: 6.0
Codename: REL
Build Version: KOT49H
Build Date: 2018-07-10
Built By: azhuo@azhuo-desktop
Build Number: eng.azhuo.1531192359

API level: 19

CPU ABIs: armeabi-v7a armeabi

Kernel Version: Linux version 3.4.67

Dalvik 1.6.0

Also says in another app its a MediaTek MT6753
Model - KT107H (kt096h_101)
Manufacturer - JTY
Hardware - mt6753

I hope all this information can help
Hope to here to your reply soon, Thank you..

Login
Username:
Password:	Lost Password?
	Remember me