Search results

May be? you're write. There is a working proposal on magisk))) or blu_spark] I wanted to advise, and you are frightened, this is your personal, on 4dda.ru for a long time already everything works (magisk & oreo) I Ask, TopJohnWu, for edit it, he was busy Sorry, my English is bad)))

And, what is about safetynet? I think? you don't know, what is required for this???? Sorry? My english is bad)))

I'm sorry that there is no one-minded people))) Somethink like this))) and yes I installed a different version can add a lot of screenshots

Hi, magisk don't work on Oreo!!! But I did several tests and it work fine(including SafetyNet). I found a solution!!! I'm on OP3

Edit boot.img in hex editor add androidboot.selinux=permissive like on screen in attachment

Accidentally I saw this topic, yes its possible. You can see it here OP3 - root & locked bootloader it's my video and it's not a channel

Be carefully, you can lose you data!!! For me all work fine))) 1.Flash Oreo via trwp 2.Downgarde bootloader for DM-Verity 3. Flash Magisk via twrp 4. Turn off the phone manualy 5.Turn on & boot in twrp 6.Do the backup of boot 7.And edit boot.win in hex editor on pc...

But you forgot to say that when you set selinux permissive via fastboot you'll have a big freeze in system;)

Magisk 14.0 & Oreo(beta25) still testing, later i'll share it)))

No, it doesn't lock the bootloader. For 3t you need another bootloader))) Maybe later I'll post a normal guide, at the moment we are testing on 4pda.ru and also for 3t

Yes, it must kept, because magisk wouldn't work without it, i did a lot of test before for SuperSu on locked bootloader)))

as I understand, the new bootloader doesn't perceive the "fastboot oem selinux permissive":):confused: Couldn't verify it and yes, it allowe selinux in permissive, until it is disabled (fastboot oem selinux enforcing) it's a vulnerability of old bootloader))) I did this when I received the root...

Bootloader path: /dev/block/bootdevice/by-name/aboot Path in zip: firmware-update/emmc_appsboot.mbn I took it from OOS 3.2.6 create zip and flash it via twrp, but at first time i have a little problem - "ask a pass" - had to do "format userdata((( and i think for dirty flash you need: (and...

flash magisk via twrp, reboot into bootloader and type "fastboot oem selinux permissive" if bootloader doesn't allowed it((( you need to downgrade bootloader)))

For me magisk 14.0 works fine:D

I did it just for the sake of experiment!!! fWgQ8sXAwZg

Hello))) One question, I am the owner of Oneplus 3, the bootloader is locked, stock android 7.1.1 (beta17), the security patch May 1, 2017, system root works, but sometimes i have a little lags (freez) in system. Why it's happens (what could be the reason)??? And i apologize for my english:)

Yes, it will work. In this zip is bootloader from oos 3.2.6.

:D

Thank you, cool ))) I think people are doing something wrong!!! The factory will n't stamp different versions.:o

I think everyone can understand, why we couldn't get all the working of supported LTE Bands for our phones It's very sad Sorry and smile for my english

@otonieru, it's for you!!! i think you can explain to other, what and how it happens on our phone And thank you for understanding!!! Хорошо, я постараюсь объяснить хоть чуть-чуть))) Суть в том, что аппаратное обеспечение у нас одинаковое, для всех версий телефонов, не исключая Т-версию (тока...

Hi, @otonieru!!! I don't use telegram and whatsapp, only viber))) And i think it will be difficult to me, speak in english:D

Don't worry, it's OKay and thanks for testing

It works, but not until the end, tests are needed. And i'm sorry a little busy to answer

Yes, you unlock it, but: I look at your screenshots and why are you say that your phone connected to band 20, don't orient the people.

Okay))) I read a couple of posts and what i wanna say: 1. On oos 4.1.0 patched rmt will not work, and yes i do all test on OOS 4.1.0, still testing, because the phone overheat without interruption:( 2. Hardware of all version are the same, but i need to see the architecture of the motherboard...

Yes, you are right, but i delete only 2500))

In the coming week I will try to solve this problem)))

and whats a problem?:confused:

Maybe everything has its time. Somebody can share the backup of QCN from 3t EU, in PM, please:o

Hi @otonieru:) And thanks:D I took a look your QCNs, and i think you deleted a lot of NvItems, because it's enough to delete only 1943 - MEID (US & CN) and 2500 - IMEI & Mac. If you remember, when i tried to change IMEI on the phone (attached screenshots), i found which NvItems responsible for...

Ha-ha!!! I helped you in PM, could at least change the content of the message:D And it's only for LTE CA (b3 & b7):p This works unstably, in a week I'll try to find the optimal configuration, that's why i didn't share it, all this on the test))) And I gave it to you and a few people for...

I use qcn a3003, b3 & b7 from 3T cn, hw id 237 and 3g work fine for me:)

LTE CA on A3000cn. Will work b3+b3, b7+b7, b3+b7. You need to restore qcn A3003 and change HW id to 237 or 228/229.

Hi, i didn't forgot, I've got a bit of spare time and decided to continue work on the B20;)

It's strange, for me all seven modes for hwid works fine. I think, it need a more simple guide. And qcn which is on first page for B5 & B8, it is made by analogy of the guide which i shared.

You need to flash only b4.qcn, then unlock b4, select and flash any fbrx_cal, set hwid on 232 (it's hw id from us version) and after this reboot your phone. And try to set other values in hw id.

Thanks @otonieru, you are right!!! I'm not explained everything in detail, because i thought that everyone can do it without problems.:D

If I will have time, I will try to make the guide simpler, but i don't know where else easier.:confused:

If you need B5 use 1. A3000_us 2. Unlock B5 3. A3000_us 4. Set HW =226 or you can try another, maybe will work 237. and i'm on OOS 4.0.1 I'm sorry, i don't have US version:D You need to test all of this for yourself As i said that's all for testing.

Hi everybody. It's all for testing. I'm sorry it took so long. I was a little busy. 1. Here are archives which include separate QCNs for each LTE Bands from those versions of the phones: A3000_cn A3000_us A3003_eu A3010_cn_3T 2. Use QXDM and NV Calculator for unlocking LTE Bands, if it needed...

Okay, why do you need the EFS? I restored EFS from the A3003 to my A3000cn, and NvRam was empty. Maybe I didn't understand you correctly:)

Okay, i understand you, but need to restore it to phone and see is there my IMEI

EFSs didn't help you. I have tried it.

Are you restored the my backup of QCN to your phone?

Somebody can check the QCN on the presence of IMEI. It's backup from my phone - A3000cn.

Hello everybody. I'm sorry it took so long, the other day I get a new motherboard for PC, my MB burned, i think so:D And my holidays a little delayed;) I have shared earlier, but i can't get any data from my HDD I hope, next week, i share all for tests:)

I Checked my patch for dm and it's worked. Sorry english is bad. simply rewrite emmc_appsboot.mbn(3.2.6) to /dev/block/bootdevice/by-name/aboot

I advised you to initially change the bootloader. patch dm-verity will change your bootloader to 3.2.6