Search results

i understand recommended to use chinese TWRP, but please at least post the file or link to the chinese TWRP.

hi peaktogoo, can you guide us on where we can download LR Team TWRP? Thanks :)

the latest build 7th May is very smooth

both your HAVOC OS and travarilo are official? Which one is the real official one?

dt2w solution https://forum.xda-developers.com/showthread.php?p=81018651#post81018651

apparently the solution in this link works to enable back d2tw

build 25th Nov 2019 still missing dt2w

looks like double tap to wake(dt2w) is gone in this update

https://forum.xda-developers.com/asus-zenfone-max-pro-m1/how-to/pie-rolled-t3907776

https://dl.wafuu.id/?dir=firmwares credit to krasCGQ

download 050 firmware from https://download.sourceforge.net/project/x00td-team/FIRMWARE/16.2017.1903.050-20190401/PIE_20190401_firmware.zip and flash it

just flashed 16th May build, it's really smooth and fast. Performance is comparable to when selinux was still permissive months ago. really awesome job on the 16th May build.

try use other kernel. Default kernel failed safetynet. But when i use PBH v15 kernel, it passes safetynet.

This looks like you changed value in build.prop to Huawei phone. This is not related to Havoc-OS Sent from my ZenFone Max Pro M1 using Tapatalk

still permissive

can i use default kernel in 25th March 2019 build? or there are still kernel issues in 25th Mar 2019 that i had to use other kernel?

Solution : https://forum.xda-developers.com/showpost.php?p=79178735&postcount=3094

i take back about there are issue with 12th Feb 2019 build. I did two changes and i managed to successfully flash 12th Feb 2019 build: 1) flash the 12th Feb 2019 build from internal storage as opposed to SD card last time 2) i used TheRagingBeast kernel last time, so i flash back 11th Feb 2019...

i think there are issue with 12-Feb-2019 build, during flashing saw message saying failed to unmount /system and /vendor, reboot and device black screen after Asus logo. Flashed back to 11-Feb-2019 build and everything is working fine. edit 13th Feb 2019: managed to flash successfully...

may i know if this ROM is patched with August 2018 security patch?

Noted. Thanks. Will try. :) edit: OMG, it works. Thank you very much :good:

Will the method in first post still works if I replace the adb.exe inside unlock folder with adb.exe from official adb installation? Sent from my Mi A1 using Tapatalk

799

Hi, can I too get a promo codes please? Thanks. Sent from my Nexus 5 using Tapatalk

Hi amnher, Thank you very much for the info. This is an even better news to me. [emoji16]

Guys, anyone know what happened to OmniROM? The last nightly is on 30th Aug 2016.

I flash franco r85 kernel as a workaround for the wifi issue.

i'm on 0309, call history is still missing. :(

very cool and simple boot animation... i really like AndroidParticles2 & AndroidMinimal1... please keep continue the good work... :)

i use teamviewer for this... teamviewer does not require u to have static WAN ip... the only thing u need is teamviewer account which is free...

i really like the black and white icons... thank you very much... :D

i do Nandroid backup once or twice every week... - backup before update ROM or change to other ROM - backup before i update kernel - backup after i update alot of apps on that day

hi CloudsITA, is it possible for u to charge the full version in US dollars instead of Euros? It's a huge different for my country currency if it's in US dollars instead of Euros... Thanks...

My first smartphone is Nokia n70 running on Symbian S60v2 before the version number reboot if i remember correctly...

Galaxy S 2 should be the best phone atm... Droid 3 should be one of the best 5 when it's launch soon, being a global phone(GSM+CDMA) + physicalqwerty keyboard... hope the lootloader for Droid 3 will be unlocked...

edit: nvm, just got the invite... Thank you very much... :D

Android 2.3.4 in my Samsung Galaxy S 2... :D

what i'll do is try to wipe cache partition and wipe dalvik cache before i flash a new ROM... if it still fails then i will do wipe cache partition and wipe dalvik cache and factory reset before i flash new ROM... my last resort will be to flash stock ROM then flash custom ROM again...