Join us on Tl   Wh

Hovatek Forum DEVELOPMENT Android TWRP for MT6739 (Android Go Edition)

TWRP for MT6739 (Android Go Edition)

TWRP for MT6739 (Android Go Edition)

twilightened
twilightened
twilightened
Enthusiastic Member
5
26-02-2019, 01:13 AM
#1



Hi. I have an MT6739 phone manufactuerd by Vanzo, but sold under the brand name "General Mobile" (Turkish brand). It is an Android GO (8.1.0 Oreo) device with 1GB of ram and 16GB of storage. It does not have an A/B partition system. I tried your Auto TWRP porting software and flashed the output recovery.img to my recovery partition using SPFlash tool. Everything went OK however, when i tried to boot into recovery the phone directly throws me into my Android home screen. I mean it first tries to boot into recovery, then fails and just opens up like i normally turned it on. I am posting a link to my original recovery.img and also the ported recovery.img below (both files under the same link). Any help appreciated:

https://we.tl/t-kBNGJtnIkE
This post was last modified: 26-02-2019, 01:19 AM by twilightened.
hovatek
hovatek
hovatek
Administrator
49,765
26-02-2019, 09:30 AM
#2
(26-02-2019, 01:13 AM)twilightened Hi. I have an MT6739 phone manufactuerd by Vanzo, but sold under the brand name "General Mobile" (Turkish brand). It is an Android GO (8.1.0 Oreo) device with 1GB of ram and 16GB of storage. It does not have an A/B partition system. I tried your Auto TWRP porting software and flashed the output recovery.img to my recovery partition using SPFlash tool. Everything went OK however, when i tried to boot into recovery the phone directly throws me into my Android home screen. I mean it first tries to boot into recovery, then fails and just opens up like i normally turned it on. I am posting a link to my original recovery.img and also the ported recovery.img below (both files under the same link). Any help appreciated:

https://we.tl/t-kBNGJtnIkE

retry porting but select 8.1 or 8.0 instead
or you can also try philz porting tool @ https://www.hovatek.com/forum/thread-21495.html
twilightened
twilightened
twilightened
Enthusiastic Member
5
26-02-2019, 11:06 AM
#3
OK I will try and share the results. I actually tried Philz already, and although it booted up just fine, it couldn't mount any partitions. And somebody told me that GSI (generic system image) roms can't be installed using Philz. Is that true?
This post was last modified: 26-02-2019, 11:10 AM by twilightened.
hovatek
hovatek
hovatek
Administrator
49,765
26-02-2019, 03:14 PM
#4
(26-02-2019, 11:06 AM)twilightened OK I will try and share the results. I actually tried Philz already, and although it booted up just fine, it couldn't mount any partitions. And somebody told me that GSI (generic system image) roms can't be installed using Philz. Is that true?

mount points can be fixed in fstab, as for philz & GSI, only one way to find -- by testing
but first try out the other two options for twrp
twilightened
twilightened
twilightened
Enthusiastic Member
5
26-02-2019, 04:23 PM
#5



I have tried 8.1 (non-GO version) and 8.0 as you have suggested but unfortunately none of them even booted up. Can i get boot logs so that i can at least find out what the problem is? How can i get them?
hovatek
hovatek
hovatek
Administrator
49,765
27-02-2019, 09:10 AM
#6
(26-02-2019, 04:23 PM)twilightened I have tried 8.1 (non-GO version) and 8.0 as you have suggested but unfortunately none of them even booted up. Can i get boot logs so that i can at least find out what the problem is? How can i get them?

whats the status of dm_verity in your recovery?
if dm_verity's found, did you patch and flash boot before flashing recovery?
This post was last modified: 27-02-2019, 09:23 AM by X3non.
twilightened
twilightened
twilightened
Enthusiastic Member
5
27-02-2019, 11:38 AM
#7
(27-02-2019, 09:10 AM)X3non
(26-02-2019, 04:23 PM)twilightened I have tried 8.1 (non-GO version) and 8.0 as you have suggested but unfortunately none of them even booted up. Can i get boot logs so that i can at least find out what the problem is? How can i get them?

whats the status of dm_verity in your recovery?
if dm_verity's found, did you patch and flash boot before flashing recovery?

There is no dm_verity. And I previously patched my boot and using Magisk already.
hovatek
hovatek
hovatek
Administrator
49,765
27-02-2019, 03:46 PM
#8
(27-02-2019, 11:38 AM)twilightened There is no dm_verity. And I previously patched my boot and using Magisk already.

so its back to philz recovery, you can unpack using the guide @ https://www.hovatek.com/forum/thread-15817.html
replace the values of \etc\*.fstab with the values from fstab in stock recovery. this should fix the mount errors
twilightened
twilightened
twilightened
Enthusiastic Member
5
27-02-2019, 05:23 PM
#9
(27-02-2019, 03:46 PM)X3non
(27-02-2019, 11:38 AM)twilightened There is no dm_verity. And I previously patched my boot and using Magisk already.

so its back to philz recovery, you can unpack using the guide @ https://www.hovatek.com/forum/thread-15817.html
replace the values of \etc\*.fstab with the values from fstab in stock recovery. this should fix the mount errors

Thanks. I will try.

Edit: I changed the values and copied the ones from stock rom, but i think i changed a little bit too much because Philz couldn't find external storage Smile Can you help me with these files please:

https://we.tl/t-Ei9pryG5xt
This post was last modified: 27-02-2019, 06:05 PM by twilightened.
hovatek
hovatek
hovatek
Administrator
49,765
28-02-2019, 05:50 PM
#10
(27-02-2019, 05:23 PM)twilightened Thanks. I will try.
Edit: I changed the values and copied the ones from stock rom, but i think i changed a little bit too much because Philz couldn't find external storage Smile Can you help me with these files please:

https://we.tl/t-Ei9pryG5xt

philz can't show both internal and external at the same. its either you're using intsd or extsd
you can copy and flash your files from intsd
Users browsing this thread:
 1 Guest(s)
Users browsing this thread:
 1 Guest(s)
Join us
WhTlYt