[OxygenOS Pie] Closed Beta *** Leaked build available *** - OnePlus 3 Guides, News, & Discussion

Finally they made it real!! Closed Beta is now opened for Oneplus 3/3t owners
If you want to be part of this beta testing, follow this link: https://www.xda-developers.com/oneplus-3-3t-closed-beta-oxygenos-9-android-pie/
IMPORTANT : Use leaked builds at your own risk
Download
(OP3 OnePlus3Oxygen_16_OTA_073_all_1903190037_c3d5b3a79f9b4895.zip)
(OP3T OnePlus3TOxygen_28_OTA_073_all_1903190038_308835b6760c41bd.zip)
Instructions (Read carefully)
* Flash through TWRP (by @dianlujitao) and do a Factory Reset before boot the device (source)
* Your device will became encrypted during boot (data partition may be corrupted on encrypted devices)
* magisk v18.1 is working
(source)
* Stock recovery will overlap TWRP unless you flash magisk before reboot.
Bugs:
None so far...
Thanks for initial testers:
@Chuck Bartowski
@himsin

Sounds amazing, waiting to see the final version coming out

FSadino said:
Finally they made it real!! Closed Beta is now opened for Oneplus 3/3t owners
If you want to be part of this beta testing, follow this link: https://www.xda-developers.com/oneplus-3-3t-closed-beta-oxygenos-9-android-pie/
Click to expand...
Click to collapse
How will I know of I get selected for closed beta testing?? And when will close beta be available for testing

alrd apply hope this early appril can roll out

Closed beta pie for op3/t leaked

helderfp said:
Closed beta pie for op3/t leaked
Click to expand...
Click to collapse
Where?

helderfp said:
Closed beta pie for op3/t leaked
Click to expand...
Click to collapse
and why do you think that?

abhibnl said:
and why do you think that?
Click to expand...
Click to collapse
Because i download the rom from a leaked link

helderfp said:
Because i download the rom from a leaked link
Click to expand...
Click to collapse
Can you share a link via PM?

abhibnl said:
While I won't ask you to post a leaked build, can you post some SS running that ROM and showing this thread in XDA app to show that you are not just joking around and have actually used the ROM?
Or you can download AIDA64 and post SS from that app.
Click to expand...
Click to collapse
Review from techibee
https://www.youtube.com/channel/UCAL31QQ9hsw8utl2GSgOchg

jay_snake said:
Where?
Click to expand...
Click to collapse
https://yadi.sk/d/Dj_6zddVg5-yog

Thread cleaned
Link restored
Please see rule 12
XDA has been the place to find leaked builds since there were leaked builds
Thank you for your cooperation

Does it work as a daily driver or still too buggy?
(he said, before inevitably rushing to install it)

helderfp said:
Review from techibee
https://www.youtube.com/channel/UCAL31QQ9hsw8utl2GSgOchg
Click to expand...
Click to collapse
Appreciate it. I'll find and download it to test it over weekend.

Thanks for the build!
Any way to decrypt?
I tried flashing Magisk (18.1) after flashing the ROM but it didn't work.
I also tried flashing Magisk + Universal DM-Verity ForceEncrypt disabler (https://forum.xda-developers.com/android/software/universal-dm-verity-forceencrypt-t3817389) but that gave me a bootloop.

To everyone who will rush to flash it - please don't just download and flash. Make sure you are ready for broken device, storage encryption and decryption errors, and data errors.
Make sure to take a complete backup of internal storage and then attempt to flash it using stock or twrp recovery.
Or you should rather wait til a developer figures out a way to make twrp compatible with its firmware for encryption/decryption errors

Just flash it and do a factory reset before booting rom. That will do the trick. My phone was decrypted and first boot took around 15 mins and encrypted phone.
BTW anyone tried if magisk is working on closed beta?

himsin said:
Just flash it and do a factory reset before booting rom. That will do the trick. My phone was decrypted and first boot took around 15 mins and encrypted phone.
BTW anyone tried if magisk is working on closed beta?
Click to expand...
Click to collapse
Magisk is working, I'm now using the closed beta with Magisk 18.1.
At first boot Magisk Manager (the application) was not installed and I had to install it manually. Also, Magisk Manager was saying that Magisk was not installed, but a reboot solved it. Now it is working perfectly.
And, if you were responding to me, I'm sorry I wasn't very clear, I wanted to keep the phone decrypted (disabling force encrypt at first boot), but I have failed and I'm using the phone encrypted at the moment.

I just installed it via stock recovery with locked bootloader... Everything is fine..

himsin said:
Just flash it and do a factory reset before booting rom. That will do the trick. My phone was decrypted and first boot took around 15 mins and encrypted phone.
BTW anyone tried if magisk is working on closed beta?
Click to expand...
Click to collapse
Did you used stock or TWRP recovery?

Related

How to root 3T on OOS4.0 ?

Hey,
I bought my phone 2 days ago, after charging it I updated to OOS4.0 through the system updates using VPN, when I got home I unlocked the bootloader but did nothing else afterwards. I'm seeing a lot of threads with people having issues with TWRP and encryption, considering my last device was the OPO and I was running Lollipop (was too lazy to update it ) I'm kinda out of the loop.
How can I root it now that it's running Nougat ? simply flashing the twrp img using fastboot and then flashing the SuperSU zip or is there a different method ?
Any kind of help is greatly appreciated.
Also, one more question, is Xposed working on Nougat ? I had quite a few useful modules on my OPO, wanted to know if that's possible on the 3T as well.
The beta builds of the TWRP which are compatible with the OOS 4.0.0 are available. You can find them from the thread.
If you want to use the Xposed modules, you should downgrade to 3.5.4.
WeirdSoup said:
The beta builds of the TWRP which are compatible with the OOS 4.0.0 are available. You can find them from the thread.
If you want to use the Xposed modules, you should downgrade to 3.5.4.
Click to expand...
Click to collapse
And where should I download SuperSU from ? Heard the project is being taken over or smth like that
B00steed said:
And where should I download SuperSU from ? Heard the project is being taken over or smth like that
Click to expand...
Click to collapse
http://www.supersu.com/download
Actually, I'm using the Magisk instead. https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
WeirdSoup said:
http://www.supersu.com/download
Actually, I'm using the Magisk instead. https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
Click to expand...
Click to collapse
Is it better to install this instead of SuperSU ?
If you are interested in using apps which detect root or a modified system/bootloader (Android Pay, Pokémon Go, some banking apps) then yes. Otherwise, no benefit of Magisk (v10.2) for you and may as well use SuperSU which is simpler to install.
B00steed said:
Is it better to install this instead of SuperSU ?
Click to expand...
Click to collapse
It's case by case, and I don't know which one is good for you. Do some research and figure out yourself.
---------- Post added at 11:30 AM ---------- Previous post was at 11:24 AM ----------
23Six said:
If you are interested in using apps which detect root or a modified system/bootloader (Android Pay, Pokémon Go, some banking apps) then yes. Otherwise, no benefit of Magisk (v10.2) for you and may as well use SuperSU which is simpler to install.
Click to expand...
Click to collapse
Magisk is open source, and it is also easy to install. You can also install the Magisk modules. It's not a simple root-hide app as many people still misunderstand.
So, with oxygen 4.0.1 the procedure will be the same?
TWRP Stuck Mount password
Greetings guys..
Yesterday I got my 3T and upgraded OTA latest OxygenOS 4.0.1. I was able to unlock bootloader and install TWRP 3.0.3 but when I access bootloader the first screen ask me to provide "Decrypt password" to mount, and if I ignore and slide to start modification I don't have access to internal card (assume its READ-ONLY), just folders are visible but unable to find or install SU package.
I check all the forums but didn't find any relevant information how to get out of TWRP "Decrypt password" issue. I don't want my phone to be encrypted, so I would appreciate if you can please help me to root my 3T.
Cheers
junostik said:
Greetings guys..
Yesterday I got my 3T and upgraded OTA latest OxygenOS 4.0.1. I was able to unlock bootloader and install TWRP 3.0.3 but when I access bootloader the first screen ask me to provide "Decrypt password" to mount, and if I ignore and slide to start modification I don't have access to internal card (assume its READ-ONLY), just folders are visible but unable to find or install SU package.
I check all the forums but didn't find any relevant information how to get out of TWRP "Decrypt password" issue. I don't want my phone to be encrypted, so I would appreciate if you can please help me to root my 3T.
Cheers
Click to expand...
Click to collapse
I think you need latest twrp beta 1, it should be in twrp tread, look in last pages or here https://forum.xda-developers.com/oneplus-3t/how-to/rom-oxygenos-3-5-4-mm-ota-update-t3519074
bertozzi243 said:
I think you need latest twrp beta 1, it should be in twrp tread, look in last pages or here https://forum.xda-developers.com/oneplus-3t/how-to/rom-oxygenos-3-5-4-mm-ota-update-t3519074
Click to expand...
Click to collapse
Thanks for quick reply, I'll check it.
bertozzi243 said:
I think you need latest twrp beta 1, it should be in twrp tread, look in last pages or here https://forum.xda-developers.com/oneplus-3t/how-to/rom-oxygenos-3-5-4-mm-ota-update-t3519074
Click to expand...
Click to collapse
Installed TWRP 3.0.3.1 BETA .... How long does it really take to decrypt new phone without any apps? Just to have an idea. When I started TWRP it asked for password and I used the PIN assigned to login to screen ... now going on for 5 minutes now.
Following on the screen:
Mount
Try Decryption
Updating partition details...
....done
Unable to mount storage
Full SELinux support present
---------blue animation-----------
junostik said:
Installed TWRP 3.0.3.1 BETA .... How long does it really take to decrypt new phone without any apps? Just to have an idea. When I started TWRP it asked for password and I used the PIN assigned to login to screen ... now going on for 5 minutes now.
Following on the screen:
Mount
Try Decryption
Updating partition details...
....done
Unable to mount storage
Full SELinux support present
---------blue animation-----------
Click to expand...
Click to collapse
I read that it takes some minutes if you are f2s and encrypted but I don't know how to proceed since I haven't flashed twrp and root yet.
Sorry but you may have to wait someone who has already done it

What is the correct way to re-enable encryption?

If I have formatted and installed with encryption disabled, what is the right way to get encryption back?
Can I just go into Settings>Security & Fingerprint>Encrypt Phone and enable it there?
Yup, that should do the trick. Didn't try on T3, but used same method on one of my prev phones.
Did that work?
I did it on OOS 4.1.1 with twrp and franco kernel installed. It worked for me :good:
AndreiVolk said:
I did it on OOS 4.1.1 with twrp and franco kernel installed. It worked for me :good:
Click to expand...
Click to collapse
I wonder if it works with a non oos rom though
stonew5082 said:
I wonder if it works with a non oos rom though
Click to expand...
Click to collapse
Well all custom roms work fine with encrypted devices so i don't see why it shouldn't be possible to encrypt your device on a custom rom. If you want to be 100% sure ask in the thread of your rom
AndreiVolk said:
Well all custom roms work fine with encrypted devices so i don't see why it shouldn't be possible to encrypt your device on a custom rom. If you want to be 100% sure ask in the thread of your rom
Click to expand...
Click to collapse
It worked. I disabled root to be on the safe side and encrypted. I get errors in twrp now, but they don't seem to effect anything.
stonew5082 said:
It worked. I disabled root to be on the safe side and encrypted. I get errors in twrp now, but they don't seem to effect anything.
Click to expand...
Click to collapse
May i know what error TWRP gives after you encrypt your phone ?
I plan to do so as well...
stonew5082 said:
It worked. I disabled root to be on the safe side and encrypted. I get errors in twrp now, but they don't seem to effect anything.
Click to expand...
Click to collapse
nicknacknuke said:
May i know what error TWRP gives after you encrypt your phone ?
I plan to do so as well...
Click to expand...
Click to collapse
Root is not a problem neither. i did it with root enabled.
That twrp error is normal. When you boot in twrp it shows the error that it can't mount data because you're encrypted and you need to type in your password first.
I also suggest you to use blu_spark's twrp because it's always updated. The official twrp for the op3t hasn't a maintainer anymore and it seems abbandoned..
AndreiVolk said:
The official twrp for the op3t hasn't a maintainer anymore and it seems abbandoned..
Click to expand...
Click to collapse
How do you figure that?
https://eu.dl.twrp.me/oneplus3t/
Didgeridoohan said:
How do you figure that?
https://eu.dl.twrp.me/oneplus3t/
Click to expand...
Click to collapse
I mean here on xda. The last build on xda is the 3.0.4.1 which it never came out. There was the 3.1.0.0 which had the wipe bug for the 3t. I don't know who is making those builds and i don't neither know if they test it.
AndreiVolk said:
I mean here on xda. The last build on xda is the 3.0.4.1 which it never came out. There was the 3.1.0.0 which had the wipe bug for the 3t. I don't know who is making those builds and i don't neither know if they test it.
Click to expand...
Click to collapse
You were talking about the official builds... That's the official downloads from the official TWRP website (https://twrp.me). There's a world outside XDA as well...

Questions regarding xiaoumi.eu ROM

I made the update from stable global to beta global last week, because I needed to unlock bootloader. Now my plan was to wait for the first stable release of Lineage, but I didn't know about Xiaoumi.eu rom and that headphone volume was so bad on this stock (beta) rom...
Now my questions are:
Which partitions have to be wiped before flashing the ".eu" rom?
(Already googled this one on my own, see "EDIT")Are the weekly versions like Beta versions? If yes then would this one be the latest stable rom:
xiaomi.eu_multi_MIMAX2_V8.5.15.0.NDDCNED_v8-7.1.zip
Other than that there shouldn't be any other Things to worry about, right?
Thanks in advance!
EDIT: So I googled a bit about the meaning of weekly and I guess it will work well enough for me, downloading this one right now:
xiaomi.eu_multi_MIMAX2_7.10.12_v9-7.1.zip
I couldn't find much about my other questions though..
EDIT 2: I just went the "factory reset" way and wiped data, cache and dalvik and it worked.
No further questions from me.
Were you able to install Xposed on this ROM?
haven't tried yet, I don't have the time eight now to fix it if it starts acting weird or bootloops...
maybe I have some time in the weekend, I really need xposed fir pbmc...
dnbdel said:
Were you able to install Xposed on this ROM?
Click to expand...
Click to collapse
Good news, look at my reply in this thread: https://forum.xda-developers.com/mi-max-2/how-to/xposed-mi-max-2-t3686416
Tazmaniiac said:
I finally managed to flash xposed-v88.2-sdk25-arm64-test4.zip from the official MIUI 9 Github thread.
I'm on latest weekly MIUI 9 xiaomi.eu rom (7.10.19), which is Android 7.1 with Magisk 14.0. Flashed via iscle's TWRP.
Download for test4 (Android 7.1), Android 7.0 would be this one
Got the downloadlink from here: http://en.miui.com/forum.php?mod=viewthread&tid=946636&highlight=xposed
I suggest you to read the description in the MI Forum thread. I haven't tested any modules yet, I only know that the framework is active for me and that it disabled SafetyNet.
Click to expand...
Click to collapse
Tazmaniiac said:
Good news, look at my reply in this thread: https://forum.xda-developers.com/mi-max-2/how-to/xposed-mi-max-2-t3686416
Click to expand...
Click to collapse
Thanks man, sadly I the phone still won't boot after installing this updated Xposed version. Here are the steps I did:
Install newest Xiaomi ROM (7.10.19)
Flash TWRP
Install Magisk 14 zip via TWRP
Boot up again to check if Magisk was installed (it was)
Flash V88.2_Sdk25_Arm64 Xposed zip
-> Phone doesn't boot
Did I do a dumb mistake here or sth?
dnbdel said:
Thanks man, sadly I the phone still won't boot after installing this updated Xposed version. Here are the steps I did:
Install newest Xiaomi ROM (7.10.19)
Flash TWRP
Install Magisk 14 zip via TWRP
Boot up again to check if Magisk was installed (it was)
Flash V88.2_Sdk25_Arm64 Xposed zip
-> Phone doesn't boot
Did I do a dumb mistake here or sth?
Click to expand...
Click to collapse
Nope, that's more or less how I did it. But before I flashed this version of Xposed I installed the Xposed Installer. Maybe that's necessary, but I think not.
Can you try out flashing the no-verity-opt-encrypt.zip? I did it for something else earlier and also after every attempt of flashing Xposed.
If I understand it right some Xiaomi phones bootloop after you write to /system, then you have to flash that file to fix it. Xposed writes to /system, so that could be a solution.
Before you flash that research it a little bit more, because I don't know much about this topic and don't want to give you false advice.
EDIT:Did you flash the xposed version from my downloadlink? It is different from the regular 88.2 SDK25, it's a testversion made by the xposed creator specifically for MIUI 9 devices.

[TOOL][10.0]ONE CLICK TWRP+MAGISK FOR ANDROID Q by Jay's Dev Team.

Jay's Dev Team
Patched Boot Image Flasher for OnePlus 6T!
Another Work made by Jay's Dev Team! No more abandoned support, more frequent updates and tested builds!
Features:
•Android 10 Ports compatible (7T, Pixel 4xl, etc.)
•OOS OpenBeta 1 Q , H2OS BETA 1 Q compatible.
•Pre rooted (Just install Magisk apk)
•TWRP 3.3.1.20 preinstalled
How to Install:
Notes: Backup Your nudes before flashing!
1.Reboot to fastboot
2.Run flasher.bat
3.Enjoy
After it will finish flashing (5-10 seconds), Your phone will automatically reboot into Main OS.
Download:
Patched Boot Image Flasher Android Q Beta 1
NEW
OOS Stable Android 10 Root+Twrp TEST BUILD
Warning! If your device doesn't boot, just use EDL mode or fastboot to go back to stock firmware.
If You have any other problems, just ask here on XDA or for the fastest support ask someone in our Telegram group
Join our group!
Jay's Dev Team:
MounirHero - OnePlus 6T Maintainer & Tester - Donate to Mounir
Jay - OnePlus 6 Main Developer - Donate to Jay
Credits:
@MounirHero for maintaining and testing.
@ProtoDeVNan0 for base OP6 Ports.
erfanoabdi for vendor patcher idea.
Mauronofrio for Twrp.
TopJohnWu for Magisk.
OnePlus for latest firmwares and for creating OP6/6T!
If I forgot anyone, just PM me on Telegram!
​
Thanks !
TWRP work but no decrypt because no format data ?
Heldwin said:
Thanks !
TWRP work but no decrypt because no format data ?
Click to expand...
Click to collapse
Exactly:good:
MounirHero said:
Exactly:good:
Click to expand...
Click to collapse
Perfect ! I do that.
don't update magisk to 20 ?
Nice work dude, I think a lot of people will appreciate this to ease confusion about the whole A10 ordeal for now.
Work perfectly Bro
Thanks for sharing.
UPDATE :
- After flashing it works fine i have TWRP and Magisk for Root but suddenly my sound is not working event when connecting Headset.
Thanks man. !
raidenXXIX said:
Work perfectly Bro
Thanks for sharing.
Click to expand...
Click to collapse
hello no working mac wifi for me.
regards
raidenXXIX said:
Work perfectly Bro
Thanks for sharing.
UPDATE :
- After flashing it works fine i have TWRP and Magisk for Root but suddenly my sound is not working event when connecting Headset.
Click to expand...
Click to collapse
Reinstall the rom through local upgrade to go back to stock
Boot to stock OS and then try again
cultofluna said:
Reinstall the rom through local upgrade to go back to stock
Boot to stock OS and then try again
Click to expand...
Click to collapse
I come from OOS OB 9.0.17 then updated via system update TUT by Sir Funk Wizard then try this to have TWRP + Rooted.
but in end it works perfectly but my sound system fully wipe like my OP6T is in MUTE MODE.
raidenXXIX said:
I come from OOS OB 9.0.17 then updated via system update TUT by Sir Funk Wizard then try this to have TWRP + Rooted.
but in end it works perfectly but my sound system fully wipe like my OP6T is in MUTE MODE.
Click to expand...
Click to collapse
If you flash back the stock boot img sound is working?
Try this...
If sounds are still broken , factory reset...
cultofluna said:
If you flash back the stock boot img sound is working?
Try this...
If sounds are still broken , factory reset...
Click to expand...
Click to collapse
So if i still do this and Still encountering Sound problem i just need to factory reset.
ok i'll try this one, i also see this as a solution about the issue but i don't want my apps to be wipe and install again via backup because it's hassle, that's why i'm trying to get an answer on it without getting a data loss from my current applications installed.
anyways thanks bro for answering my concern. :good:
raidenXXIX said:
So if i still do this and Still encountering Sound problem i just need to factory reset.
ok i'll try this one, i also see this as a solution about the issue but i don't want my apps to be wipe and install again via backup because it's hassle, that's why i'm trying to get an answer on it without getting a data loss from my current applications installed.
anyways thanks bro for answering my concern. :good:
Click to expand...
Click to collapse
You've been moved from Pie to android Q
Its good to make a clean install and start fresh from scratch..
cultofluna said:
You've been moved from Pie to android Q
Its good to make a clean install and start fresh from scratch..
Click to expand...
Click to collapse
If i do this one, maybe i'll try some custom ROM on Android 10 base since i'm starting from the scratch again before settling on my main ROM again
once again Thanks bro
Just need format infernal storage or format all partitions ?
Heldwin said:
Just need format infernal storage or format all partitions ?
Click to expand...
Click to collapse
if you encountering any problem after flashing this on your latest FW, try first to factory reset and check if the issue is still the same.
raidenXXIX said:
if you encountering any problem after flashing this on your latest FW, try first to factory reset and check if the issue is still the same.
Click to expand...
Click to collapse
OK, I can confirm a couple things:
1. With this boot.img I have magisk
2. With this boot.img I have TWRP
But...
I have no MAC ID, so no wifi.
After a complete reset, including formatting data, still no MAC, no wifi
Could this be a difference between the international version and the US version?
michaave said:
OK, I can confirm a couple things:
1. With this boot.img I have magisk
2. With this boot.img I have TWRP
But...
I have no MAC ID, so no wifi.
After a complete reset, including formatting data, still no MAC, no wifi
Could this be a difference between the international version and the US version?
Click to expand...
Click to collapse
I had the same issue with international version.
So will this do all the necessary steps to root my phone and add twrp ? Im still stock and unrooted.
If so, anything i need to do prior ?
Yes, make sure you're on first android Q beta and you have unlocked bootloader.

General [IMG] Boot + magisk patched boot images

Hi, I have decided to gather boot images and magisk patched images to one thread for now. I will try to edit this thread to be up-to-date. You can let me know what could you want next or if anything is wrong etc.
Stock boot.img files (direct links): ​
EU NE2213_11_A.12​
Stock boot.img - link
EU NE2213_11_A.10​
Stock boot.img - link
​Magisk patched boot.img are here a file that can be downloaded (I am using magisk canary usually, but in Magisk, you can change the channel from the canary to stable etc.) - names as the versions come. ​
Below this there are those magisk patched files which you just flash (or boot and then flash directly from the Magisk app) via fastboot ​
Reserved
Don't you need to patch vendor_boot.img as well like OnePlus 9 pro ?
HessNL said:
Don't you need to patch vendor_boot.img as well like OnePlus 9 pro ?
Click to expand...
Click to collapse
Apparently not. I have patched that stock boot via magisk, then via fastboot boot <patchedimage.img> booted (and also tested if it actually boots) and when it booted, via magisk app I did "Direct install (recommended)", rebooted and done.
Oh okay you had a temporary boot we that's good to know well it works that's the most important thing ain't it
Noob question I been on locked bootloader for years so haven't been in the root scene, but I have US model NE2215 I'm guessing I need to wait for the firmware to be available to get the boot img? Did I just got my phone too early? Already oem unlocked now just waiting for twrp and root info. I always wanted a OnePlus phone because the community is big, but doesn't seem like much people upgraded from 9 pro.
HessNL said:
Oh okay you had a temporary boot we that's good to know well it works that's the most important thing ain't it
Click to expand...
Click to collapse
Yes, because this is probably and currently the most secure option to root it as we haven't got twrp available yet.
BuBbLeFIZzY said:
Noob question I been on locked bootloader for years so haven't been in the root scene, but I have US model NE2215 I'm guessing I need to wait for the firmware to be available to get the boot img? Did I just got my phone too early? Already oem unlocked now just waiting for twrp and root info. I always wanted a OnePlus phone because the community is big, but doesn't seem like much people upgraded from 9 pro.
Click to expand...
Click to collapse
That's not that you have it early. The phone itself is early in spite of rooting and doing things like rooting, custom recoveries, ROMs etc. I currently can't find boot img for your model, but once I do, I will post it here for you with patched one.
Thank you kouzelnik3 for this thread !
I was going to dl original firmware and patch it myself but found your thread in time with all ready to flash
Rooted OP10 pro done, now i can't wait to see some TWRP and roms in the future
fozzy056 said:
Thank you kouzelnik3 for this thread !
I was going to dl original firmware and patch it myself but found your thread in time with all ready to flash
Rooted OP10 pro done, now i can't wait to see some TWRP and roms in the future
Click to expand...
Click to collapse
You're really welcome, I wanted to unite those currently quite hard rooting stuff!
And yes, I can't wait to see twrp too!
Is there a known stock boot.img of the NE2215_11_A.10? I assume I shouldn't use the 2213_11_A.10.
GeekMcLeod said:
Is there a known stock boot.img of the NE2215_11_A.10? I assume I shouldn't use the 2213_11_A.10.
Click to expand...
Click to collapse
Not yet unfortunately. Or I don't know about it yet. :/
kouzelnik3 said:
Not yet unfortunately. Or I don't know about it yet. :/
Click to expand...
Click to collapse
Yeah.. I googled a lot last night once I got my phone trying to find it to root it. I need me that extra bit of customization.
Is there a way I can get it from my phone?
what am i doing wrong here rooted for 7+ years and some reason can't get this working.
Just moved over from ColorOS to Oxygen - when i try to flash the boot.img (patched one) all i get is this
Johnstan725 said:
what am i doing wrong here rooted for 7+ years and some reason can't get this working.
Just moved over from ColorOS to Oxygen - when i try to flash the boot.img (patched one) all i get is this
Click to expand...
Click to collapse
Ignore me but for anyone else that tries looks like i had to reboot bootloader and flash the img via bootloader...
thought it's normally flashed via fastboot?! weird phone
Johnstan725 said:
Ignore me but for anyone else that tries looks like i had to reboot bootloader and flash the img via bootloader...
thought it's normally flashed via fastboot?! weird phone
Click to expand...
Click to collapse
You should wipe the phone and start all over or else you won't be able to take ota updates. Never flash the patched boot image since you bypass the magisk backup feature. You have to wait for the full update package to update if you flash the boot. Ppl have previously had update issues after flashing.
g96818 said:
You should wipe the phone and start all over or else you won't be able to take ota updates. Never flash the patched boot image since you bypass the magisk backup feature. You have to wait for the full update package to update if you flash the boot. Ppl have previously had update issues after flashing.
Click to expand...
Click to collapse
Wiped the phone already, what difference would it make if i remove root or flash stock boot then flash ota and reflash boot?
Johnstan725 said:
Wiped the phone already, what difference would it make if i remove root or flash stock boot then flash ota and reflash boot?
Click to expand...
Click to collapse
Not sure what else magisk does during the backup process, but doing what you’re describing didn’t work for users on 8T and they usually ended up soft bricking. Everyone who flashed it vice installing from magisk app had to wait for op to post the full rom or for someone to post a repacked fastboot rom to update.
You do what you need to do, I’m just giving you some experience and recommendations since you just wiped and flashed the boot.
g96818 said:
Not sure what else magisk does during the backup process, but doing what you’re describing didn’t work for users on 8T and they usually ended up soft bricking. Everyone who flashed it vice installing from magisk app had to wait for op to post the full rom or for someone to post a repacked fastboot rom to update.
You do what you need to do, I’m just giving you some experience and recommendations since you just wiped and flashed the boot.
Click to expand...
Click to collapse
Interesting.
I moved over from ColorOS to oxygen OS, wiped the device then just booted a patched boot img, and installed direct.
I assume I flash ota and go onto magisk and do inactive slot? Where does the issue lie what method should I have gone down?
Johnstan725 said:
Interesting.
I moved over from ColorOS to oxygen OS, wiped the device then just booted a patched boot img, and installed direct.
I assume I flash ota and go onto magisk and do inactive slot? Where does the issue lie what method should I have gone down?
Click to expand...
Click to collapse
Hmmm. Well you should be fine if you patched the boot and let magisk do the install. I only suggested wiping since you said you flashed the img from the bootloader.
You might run into the same problem I have with the 9RT. I too upgraded from color to oos and couldn’t update at all, even though I rooted from the magisk app. I had to wait for someone to make a fastboot rom. I had no problems updating color following my method, but not oos after switching. Hopefully that’s not the case for you.

Categories

Resources