Never flash a boot image!Hello, my phone is 2215 and tried to flash your boot image. Phone boot but only some shortcurt with black wallpaper...have to rollback. Pretty weird.
I am seconds away from throwing this device out of the window, with the new command given it says:First of all you shouldn't use fastboot oem unlock but fastboot flashing unlock. The previous command doesn't work on newest devices like oneplus 10 pro or pixel.
Finally! thank youit's not "flash" but "flashing" .
And remember to update platform tools.
Hey guys,
I am a bit confused after reading most of the posts.
Is this rooting procedure working as described for the global version or not? for all versions or just for later versions than NE2215_11.A.12?
the only issue is the netflix app?
it would great if someone could put in short words the current situation. Thanks.
regards
mvk
Probably a oneplus software issuedoes it something to do with rooting using this procedure or it is a bug of this phone on Android 13?
That is annoying. The only bugs I ran into are fingerprint is not the default login method since C19 and the swipe down from the top sometimes stops working unless I turn off the screen and turn it back on since C22.FYI: Getting a bug on C22 that is reproducible and wanted to share for others. While on (usually an incoming) call screen will stay black and not come back on even if pressing side buttons or tapping screen.
Once call is ended, full functionality returns. Very annoying as you cannot search/use phone while on phone. Are others experiencing as well after upgrading as well?
Hi,This is for the Global Rom.
Step 1: Unlock your bootloader.
Step 2: Download and install Magisk Stable or Canary. Your choice, but I used Canary.
https://github.com/topjohnwu/Magisk
Step 3: You can use either patch the stock boot or use my patched boot rom.
https://androidfilehost.com/?w=files&flid=333790
Step 4: Reboot to bootloader
Code:adb reboot bootloader
Step 5: BOOT the patched boot rom! DO NOT FLASH!
Code:fastboot boot patched_boot.img * change patched_boot.img to whatever your filename is.
Step 6: Open Magisk and perform a direct install.
Step 7: Enjoy!
Additional steps to pass safetynet:
Step 8: Open Magisk, open the Settings menu, enable Zygisk, and reboot.
Step 9: Download and install Universal Safetynet Fix (Zygisk) by @kdrag0n.
https://github.com/kdrag0n/safetynet-fix/releases
Step 10: I forget if you really need this or not, but install it anyways.
MagiskHide Props
Step 11: Reboot.
Step 12: Enjoy!
Netflix Error -93:
WARNING: Netflix will not work after bootloader unlock. OnePlus's fault.
Here's how to get Netflix to work, but DRM will drop from L1 to L3.
Step 1: Uninstall Netflix.
Step 2: Flash Shamiko in Magisk and reboot.
Step 3: Install this version of Netflix.
Step 4: Open Netflix and close the app.
Step 5: Update Netflix from Google Playstore.
Step 6: Open Netflix and log in and force close the app.
Step 7: Open the app again and be greeted with error code 93, then force close the app.
Step 8: Open the app again and enjoy Netflix.
Updates:
NE2215_11.A.12
NE2215_11.A.13
NE2215_11.A.14
NE2215_11.A.15
NE2215_11.A.16
NE2215_11.A.17 Stock boot image and OTA. Thanks @mrdark5555
NE2215_11.C.19 Stable Color/OxygenOS 13
NE2215_11.C.20
NE2215_11.C.21
NE2215_11.C.22
The 10 Pro series is as follows:My OP10 is NE2215. But how can I know if it is the Global Rom or not?
oneplus playing games since US-China relations are not good. The NA version was always the global model. this guide was made before oneplus repleased a eu "global" version. None of the files I'm posted here will work with 2213. You can refer to this post for your phone. https://forum.xda-developers.com/t/...r-magisk_patched-guides-ne2213.4429711/unreadHi,
some vendors named the EU Version as "EU Global version". Is this rooting procedure working with the Global EU version numbered "NE2213"? Thanks
Thank you for the information provided. It is helpful. However, I'm still not sure how I can tell if I'm on the Global ROM or if I'm just on the US Rom. How can I verify?The 10 Pro series is as follows:
2210 China (Color OS)
2211 Indonesia (Color, Oxygen, or Hydrogen OS)
2213 Europe - Global (Oxygen OS)
2215 North America - (Oxygen OS)
2217 T-Mobile Exclusive
The only real difference is in the 2210, and the 2217. The 2210 has an OPPO proprietary OS, meaning it does NOT come with Google Play ANYTHING.. it uses a chinese store and service known as Heytapp ... The 2217 has a T-Mobile baked Bootloader, and Oxygen OS, with a hidden security bit that detects if the region changes. If that bit is triggered it can blow the RPMB fuse (it doesnt always) but this will trigger the " One-Plu-BaLoo!", my special nickname for the INFINITE BOOT LOOP! Further attempts to outsmart the phone instead of flashing the OEM stock shipped FW, will flip that "security bit" and your phone will go into an unresponsive state, where the only way to detect it by PC, is to open it and short out the Test Points. (Be Warned!) It CAN be circumvented as i have done a running count of 23 phones now, all T-Mobile without bootloop or brick. I have only bricked 1 T-Mobile which was mine, at the beginning which is how i learned in detail about this specific model. (Advice: If you have ANY desire or inclinations toward the possibility of modding/unlocking/rooting your phone, I would HIGHLY advise NOT purchasing the 2217 ... both the 2217 10 Pro, and 2419 10T are T-Mobile Exclusives, and both have special coding customized into their OS, to make their models the MOST locked down devices possible). To attempt doing ANY level of modification to one of these devices on Android 12, or 13 is a VERY VERY high stakes dice game, where the winning numbers are chosen by T-Mobile and the rulebook does not exist! I have seen IN PERSON, 3 of the exact same 2217 all pulled straight from the boxes, with IMEI in the same 100 batch, and every one on the 11_a.08 fw:
1 had direct fastboot access right out of the box,
1 could reach fastboot ONLY after setup then adb enabled and fastboot via command line,
Then the 3rd required setup ----> enable adb -----> MUST first boot to FASTBOOTD ----> Then you could command line boot to Fastboot.
(W . T . O . M .G . F?)
So bottom line is, if you can, just avoid the 2217. The only benefit of the 2217 is the "IP68" standard. It is the only of the variants that have it. The 2213 EU/Global has the MOST versatility, as it has ALL bands readily available of all the other variants combined! Otherwise I would have not kept either of these yet i have both 2217 and 2419, and i got both of them FREE thru Dad's executive discount. I still considered returning them! Great phones... Dont bend them, and Dont sit with em in your pockets and they will be awesome. I get nearly 30+ hours on both, plus the 10T goes from 2% to 100% in barely 20 min. 10 Pro Camera is better ... 10T seems a bit sturdier... but neither have the potential of the older brother, 9R as it is easily rooted, unlocked, and region swapped PLUS if you brick it, you can fire up MSM Tool and recover it. Brick either of the 10/Pro/R/T series, and you will be paying some one from a foreign country to log into your computer, and hopefully not rip you off.
Just some information for those who might be interested.
Cheers
if you are on 2215, then its not global. The Global fw has ALL bands accessible. This honestly is nothing more than a fw "flex" on the EU model. There is nothing restricting the 2215 from accessing all the extra bands, except a few bits being flipped in the efs. I was able to trace down exactly which file and where it was located in the EFS, and using ONLY diag mode i opened the file, and saw exactly where they blocked those bands from activation. Its kinda a chump move that they pulled, because the Global fw is the one that gets the MOST attention, and always gets the most feedback when it comes to new release beta builds! In the US we actually help the development of all Global fw,, because that version is usually the one that is universal for all of our carriers here, so you end up with a lot more diversified input being that in every state we have at least 6+ carriers, therefore we torture test the networks and can identify problems in a much shorter time! But to cripple the device capability just over a GLOBAL label is drastic for ANY popular phone, and thats exactly what they did, cuz the main difference between the NA and EU is only the 6 disabled 4g bands, (which are primarily for those in china... indonesia). And honestly the extra 6 bands are all 4g, so there isnt much purpose for them unless you are in china. While they do have 5g access over there, it is highly prioritized, and thus throttled after paid data limits, due to the higher density & saturated areas of their much larger population. That plus smog factor seriously hampers data transfers as ive been told, so for them they need those bands to hit more towers or they drop to 2g speeds. (yikes!) .... But to answer your question again, no unfortunately if your model is currently flashed and showing 2215 then you my friend are on the US/NA fw.Thank you for the information provided. It is helpful. However, I'm still not sure how I can tell if I'm on the Global ROM or if I'm just on the US Rom. How can I verify?
Yeah bro, i hear you... Also they went stupid with the numbering system for no good reason other than to confuse ppl... The 10 Pro series all stem from a 2210 base model, and were released as (NE) 2210, 2211, 2213, 2215 and 2217 , Ch, In, Eu, Na, Tmo .... but the 10R is the (CPH) 2411 <all region> ... and the 10T starts (CPH) 2413, 2415, 2417, 2419, In, Eu (Global again), Na, Tmo... but THIS TIME "In" stands for India, whereas the 2211 "In" is actually for Indonesia. For the 10T India got their own build, while China got the same phone, under a completely different name, "Oneplus Ace Pro". The 10R hadnt even been released til late October this year, so why didnt they just kick the 10T series in starting with 2411? Then it would be easier for people such as myself who have BOTH phones. (During a VERY SLEEPY session where i was going to drastic measures, trying to revive my 2217, after it went unresponsive, I literally spent over 2 hrs trying to make QFIL work, once i opened it up and jumpered the Test Points... And then i realized one reason it was failing to even attempt to run was because i had loaded all the 2417 files! Not paying attention because the official fw only have the model #, and not the beginning letters, I finally stared at the file on my screen wondering,oneplus playing games since US-China relations are not good. The NA version was always the global model. this guide was made before oneplus repleased a eu "global" version. None of the files I'm posted here will work with 2213. You can refer to this post for your phone. https://forum.xda-developers.com/t/...r-magisk_patched-guides-ne2213.4429711/unread
The us store sells NE2215Will this method work with the 12GB RAM version of the Unlocked OnePlus 10 Pro on the US oneplus.com store? They don't mention NE2215 on the site so just want to confirm. Thank you
If we were still on Android 12, then root disables ram expansion, but I thought oppo fixed that in Android 13 since mine works again.I rooted my NE2215_11_C22 using this method and it seemed to have worked fine. installed lsposed and modules such as call recorder enabler and core patch.
However just yesterday i noticed that Ram Extension in 'about phone' has been disabled and does not work. even after restarting.
Is it because of root or did i disable something while debloating?
i could only find this reddit post about it:
https://www.reddit.com/r/oneplus/comments/xfbtbr
anyone else who rooted having this issue or tried this fix?
you can see in the attached file that it doesn't show the added ram.
This is why it messed up.I had unchecked "apply system updates automatically on restart" in developer options.
thankyou once again for your helpyou seem to be having issues updating so just try updating while unrooted. You can download the update file and the system updater from the update post above this post
adb reboot bootloader
fastboot boot patched_boot.img
* change patched_boot.img to whatever your filename is.
Got it from my device. I'll try to see if I can dump the files tomorrow.Hello, did you get the boot.img from the original firmware or did you extract from your device. If you have the full flash file for NE2215 please post a link. Thanks