Hi there, what is easiest way to root nougat? oxygenOS 4.0?
i mean root that is working with stable nougat version. thanks.
Unlock bootloader if you haven't already (it will wipe all your data. Yes, all.), flash TWRP recovery and use that recovery to flash SuperSU flashable zip, which you can find by googling SuperSU.
I would wait a bit. I have spend quite some time on reverting. It seems there are some issues with twrp and how it handles encryption. I couldn't bypass encryption password in twrp and flash anything. I could on 3.5 but not in nougat. There are a few threads about it. A new twrp version will probably fix it.
Didn't someone make a post that you have to change the partition to f2fs to fix the encryption issue?
The Oneplus 3T comes with f2fs (you can check the partition type in twrp>wipe>tick 'data'> repair filesystem> choose 'CANCEL'). Currently the only way to fix the encryption issue in twrp is to disable encryption I think.
Sorry i didnt mean this to be Q & A, i want only ask that is it okay to root nougat or does it have some kind of problems still..
Could i install twrp on 3.5.4, root it, then flash OOS 4.0 in twrp?
Yes that's what I did. Make sure you flash the full zip (around 1.4 GB). You will lose root though.
Can't you redo root/supersu after flashing nougat? Also you can try magisk as well on nougat. I heard that works well.
Has any of you guys tried the newest TWRP 3.2.0.0 for OnePlus 3T? Did you find a bug?
Thanks.
Info: http://www.androidpolice.com/2017/1...g-better-support-oreo-roms-pixel-2-bug-fixes/
Download TWRPfor OP3T from the official site: https://dl.twrp.me/oneplus3t/
I wonder if it triggers dmverity and how to avoid it if we just want to upgrade twrp...
jojlse said:
I wonder if it triggers dmverity and how to avoid it if we just want to upgrade twrp...
Click to expand...
Click to collapse
I assume you flash the updated Recovery followed by the patched firmware, which i assume you already have? I don't even know if the firmware is necessary but whenever i flash anything i also re-flash the patched firmware while I'm at it. No reason not to.
Alright, DM-Verity will be cleared if you flash the newest Magisk beta, and TWRP 3.2.X.X is working fine. I don't think Teamwin would release an official version of TWRP without making sure it's completely free of bugs. It flashes Oreo ROMs (Cardinal Xtended, N2Os) and also flashed OOS 5.0 very well. Add-ons such as Magisk and Magisk Modules flashed flawlessly.
So, I tried everything, flashed the ROM based on OREO like 9.6.1.0 ended in bootlooping the device, also custom rom based on OREO doesnt work too, like pixel experience, LINEAGE, ETC
Other than OREO based, ROM based on NOUGAT works well, like MIUI 8.xxx or RR based on NOUGAT
Any idea why this happens?
codearm2 said:
So, I tried everything, flashed the ROM based on OREO like 9.6.1.0 ended in bootlooping the device, also custom rom based on OREO doesnt work too, like pixel experience, LINEAGE, ETC
Other than OREO based, ROM based on NOUGAT works well, like MIUI 8.xxx or RR based on NOUGAT
Any idea why this happens?
Click to expand...
Click to collapse
-Format data
-wipe
-use otg drive since format data delete everything
-flash firmware newest 8.5.10 minimum requirment for oreo
-flash rom
-flash gapps
-reboot
evanlocked said:
-Format data
-wipe
-use otg drive since format data delete everything
-flash firmware newest 8.5.10 minimum requirment for oreo
-flash rom
-flash gapps
-reboot
Click to expand...
Click to collapse
tried it all, still bootloop
codearm2 said:
tried it all, still bootloop
Click to expand...
Click to collapse
flash any miui dev rom beyond 8.5.10 using miflash
reboot once ...
flash twrp ...
push any oreo rom (ie. LOS 15.1) and gapps while in recovery ...
Install that rom and gapps ...
reboot to twrp ...
format data ...
reboot again to twrp ...
reboot to system ...
3Dota said:
flash any miui dev rom beyond 8.5.10 using miflash
reboot once ...
flash twrp ...
push any oreo rom (ie. LOS 15.1) and gapps while in recovery ...
Install that rom and gapps ...
reboot to twrp ...
format data ...
reboot again to twrp ...
reboot to system ...
Click to expand...
Click to collapse
not working
Flashed 8.5.10 rom, ended in bootloop
flashed the LOS 15.1 and GAPPS, still bootloop
so, any one?
codearm2 said:
so, any one?
Click to expand...
Click to collapse
Your custom recovery needs to be an Oreo version compatible, so you can install oreo based roms on it.
Try to update to early version.
Regards.
codearm2 said:
So, I tried everything, flashed the ROM based on OREO like 9.6.1.0 ended in bootlooping the device, also custom rom based on OREO doesnt work too, like pixel experience, LINEAGE, ETC
Other than OREO based, ROM based on NOUGAT works well, like MIUI 8.xxx or RR based on NOUGAT
Any idea why this happens?
Click to expand...
Click to collapse
try updating firmware and twrp and flash lazy flasher zip after rom instalation hope it fix . *Lazy Flasher zip is must
Steffanom said:
Your custom recovery needs to be an Oreo version compatible, so you can install oreo based roms on it.
Try to update to early version.
Regards.
Click to expand...
Click to collapse
already 3.2.3 version which I believe supports oreo rom
Tsuzan said:
try updating firmware and twrp and flash lazy flasher zip after rom instalation hope it fix . *Lazy Flasher zip is must
Click to expand...
Click to collapse
didnt work, still bootloop
codearm2 said:
so, any one?
Click to expand...
Click to collapse
so ... what last rom boot fine in your Mi5?
3Dota said:
so ... what last rom boot fine in your Mi5?
Click to expand...
Click to collapse
any nougat rom works well
tried flashed 8.5.10 rom, still bootloop
codearm2 said:
any nougat rom works well
tried flashed 8.5.10 rom, still bootloop
Click to expand...
Click to collapse
this is quite weird ... since if you install any nougat ... you'll sure receive OTA update to oreo (dev or stable) ...
why dont you take that OTA?
3Dota said:
this is quite weird ... since if you install any nougat ... you'll sure receive OTA update to oreo (dev or stable) ...
why dont you take that OTA?
Click to expand...
Click to collapse
yes, installing the OTA based on OREO update also cause bootloop happens
basically, anything OREO based, whether it's ota or flashing it manually through TWRP, ZCX TWRP, or Mi Flash cause bootloop
Have you wipe your internal partition?
I think we need to wipe all partition after installing firmware when come from nougat to Oreo, because Oreo have new vendor partition.
At least you should use twrp-3.2.1-1-gemini
Sent from my MI 5 using Tapatalk
codearm2 said:
not working
Flashed 8.5.10 rom, ended in bootloop
flashed the LOS 15.1 and GAPPS, still bootloop
Click to expand...
Click to collapse
Try reflashing latest twrp via fastboot (not from within twrp).
After wiping all partitions (also mount and wipe vendor) and formatting data, reboot to recovery before flashing the ROM to access the data partition correctly again.
Then also try to boot (would go with a custom ROM) without any gapps, mods or root first, to further center the problem.
What happens now?
Have the same problem
Try to install latest build via fastboot --> failed
Try to install miui nougat based work, ota update to oreo based -->bootloop
Also try to flash all included internal storage but the problem still occured
Any miui nougat based and aex mod 5.1 work fine in my phone
Install lazy flasher before installing anything like SuperSU...
masruri03 said:
Have you wipe your internal partition?
I think we need to wipe all partition after installing firmware when come from nougat to Oreo, because Oreo have new vendor partition.
At least you should use twrp-3.2.1-1-gemini
Sent from my MI 5 using Tapatalk
Click to expand...
Click to collapse
already wiped, still not working
Phil_Smith said:
Try reflashing latest twrp via fastboot (not from within twrp).
After wiping all partitions (also mount and wipe vendor) and formatting data, reboot to recovery before flashing the ROM to access the data partition correctly again.
Then also try to boot (would go with a custom ROM) without any gapps, mods or root first, to further center the problem.
What happens now?
Click to expand...
Click to collapse
flashed latest twrp via fastboot, also already wiped all partition included mount and wipe vendor, also formated the data and reboot first before flashing the rom, boot without any gapps, still it doesnt work
reysack said:
Have the same problem
Try to install latest build via fastboot --> failed
Try to install miui nougat based work, ota update to oreo based -->bootloop
Also try to flash all included internal storage but the problem still occured
Any miui nougat based and aex mod 5.1 work fine in my phone
Click to expand...
Click to collapse
yeah, practically the same with mine
brhnahmad05 said:
Install lazy flasher before installing anything like SuperSU...
Click to expand...
Click to collapse
tried, doenst work
codearm2 said:
flashed latest twrp via fastboot, also already wiped all partition included mount and wipe vendor, also formated the data and reboot first before flashing the rom, boot without any gapps, still it doesnt work
Click to expand...
Click to collapse
Puh, don't know.
Do you have an old backup of your efs partition lying around?
If so, try restoring that.
If that also doesn't help, I'm through with my math here, I think...
Flash a Lineage OS 14.1 build without GApps but with a firmware that supports Oreo. Then, go to developer settings, turn on ADB and run adb devices on your computer so that the RSA Fingerprint pops up. There, make sure you tap on remember this computer and click ok.
Now, do an update to Lineage 15.1 without wiping anything. As soon as you reboot your phone, connect it to your PC and try to get a logcat. Paste the logcat here and we'll be able to see what's actually going on.
Is there any alternative method to lock bootloader and unroot the device? I have read other topics that it will required to flash back to 4.0.1 version and install stock recovery.
Possible to have adb lock bootloader and reflash latest OOS 5.0.5 without flashing Magisk module?
Sent from my [device_name] using XDA-Developers Legacy app
Switched last week from Pixel Experience 9.0 (unencrypted) to OOS 5.0.5 and locked the bootloader.
Flashed the latest OOS from TWRP (with all wipes done before);
Waited for the phone to boot OOS 5.0.5 once - without root the TWRP is gone ,replaced with stock recovery;
Rebooted to stock recovery and performed another factory reset;
Waited for the phone to boot OOS 5.0.5 again (to be sure everything it's fine);
Rebooted to bootloader (fastboot) and executed: fastboot oem lock command;
Done!
P.S. - Backup your files before any wipe or bootloader re-lock.
[d]amour said:
Is there any alternative method to lock bootloader and unroot the device? I have read other topics that it will required to flash back to 4.0.1 version and install stock recovery.
Click to expand...
Click to collapse
Do what the previous response says. Just flash the 5.0.5 full zip, reboot to wipe TWRP. Then relock bootloader.
I suspect the only reason the guide you mention, says to flash 4.0.1, is because the guide is old, and 4.0.1 was just the latest version at the time. There isn't any requirement to "downgrade" to an older version, to return to stock/unrooted/locked bootloader.
lesbianu said:
Switched last week from Pixel Experience 9.0 (unencrypted) to OOS 5.0.5 and locked the bootloader.
Flashed the latest OOS from TWRP (with all wipes done before);
Waited for the phone to boot OOS 5.0.5 once - without root the TWRP is gone ,replaced with stock recovery;
Rebooted to stock recovery and performed another factory reset;
Waited for the phone to boot OOS 5.0.5 again (to be sure everything it's fine);
Rebooted to bootloader (fastboot) and executed: fastboot oem lock command;
Done!
P.S. - Backup your files before any wipe or bootloader re-lock.
Click to expand...
Click to collapse
Didn't you face DM-verity warning?
If yes, then how you removed it:-by
"ADB sideload" command or by any other means?
Please specify..........
If I had extra problems, for sure I would warn you about them. No warning, no problem, full stock "like out of the box"!
lesbianu said:
If I had extra problems, for sure I would warn you about them. No warning, no problem, full stock "like out of the box"!
Click to expand...
Click to collapse
As per my knowledge, if you flash oxygen OS OTA without magisk then DM verity flag must be triggered, which only goes by sideloading the same OTA file or updated OTA zip file.
No idea, I told you the steps I made few days ago. They worked for me! Want to believe, good. Don't want to believe, even better.
Was on OOS 5.0.4 (bootloader unlocked), decrypted to test Pixel Experience 9.0 for 2 days and then returned to "full stock" OOS 5.0.5 (bootloader locked) to send the phone in service for upper speaker problems. I know it was not necessary to lock the bootloader, but it was my personal choice.
P.S. - Stop quoting the previous post, it's not necessary.
ersandeepkr said:
As per my knowledge, if you flash oxygen OS OTA without magisk then DM verity flag must be triggered, which only goes by sideloading the same OTA file or updated OTA zip file.
Click to expand...
Click to collapse
DM verity is triggered when changes are made to the system/kernel. If you flash a stock OTA file (with no Magisk or other changes) then DM verity is not triggered. Maybe it will be triggered when TWRP is still on the device (not 100% on that), but that will be taken care of when TWRP is overwritten.
You can sideload the OTA as described on the OnePlus website, if you like. But I don't think the result will be any different.