Is your bootloader unlocked...?
Anyways...I just installed on android 12 ..seems to be working...just trying a backup.
Last edited:
How To Guide (Guide) Install TWRP + Root + Install Magisk + Bypass Safetynet
- Thread starter PlasmaTornado
- Start date
Anyways...I just installed on android 12 ..seems to be working...just trying a backup.
"I deleted nandata folder as someone said"
where you you find and delete them from
So I am sorry I am trying to read through this thread but just had my 4 year old in my ear lol. Which one works? The whole rooting thing which is easy or the conversion from T-Mo to Global? Or both... Please tell me both lol
Yes My bootloader is unlocked
Well i dont know about T mobile...But I'm on android 12...NE2215 and installed TWRP ...Tied the backup but failed . Where do I find the nandata file to delet...???
Now read my post here to change from NE2211 ...NE2213 to NE2215
forum.xda-developers.com
Now read my post here to change from NE2211 ...NE2213 to NE2215
Simple Way to change from NE2211 to NE2213
Sorry i posted this in Question Should of been in " General" or 'How To" I have a NE2210 (china) running on adroid 13 and can switch between changing it from NE2211 and NE2213 android 13 . First you need Oxygen Updater ( download from google...
forum.xda-developers.com
Ok well here's my last and final question... All I want to do is root via this method and as stated above in my previous post's I do have the T-Mobile OnePlus 10 Pro version on Android 12 with unlocked bootloader. I no longer am going to risk trying to flash global firmware until the tool is cracked for good. All I want to do is Root the device via this method. At this point I'm debating even rooting it at all . This may be my last OnePlus device. Thank you
Anyone having issues with the updater not wanting to update?
I have disabled all magisk modules, and clicked uninstall, restore images. (without rebooting, i move to the next step).
When I try to do normal OTA, everything looks like itll be OK, then before it actually starts to download, I get "Installation problem."
I try Oxygen Updated, download the OTA, use system updater apk, does the same thing. Looks like it will begin, but then "Installation problem."
Is this because I have TWRP installed?
edit : self- answer, yes ofc its because of TWRP, duh lol mb
I have disabled all magisk modules, and clicked uninstall, restore images. (without rebooting, i move to the next step).
When I try to do normal OTA, everything looks like itll be OK, then before it actually starts to download, I get "Installation problem."
I try Oxygen Updated, download the OTA, use system updater apk, does the same thing. Looks like it will begin, but then "Installation problem."
Is this because I have TWRP installed?
edit : self- answer, yes ofc its because of TWRP, duh lol mb
Last edited:
You should be fine as long as you havent done any of the region swapping.... I do not advise doing any further updates past where u are tho... Just unlock your bootloader... Then reboot to system.... Check to make sure everything works..... Then follow the Root procedure EXACTLY ... no twrp just yet... Only root! ... Then boot up and make sure all works ..... Finally follow the Twrp procedures EXACTLY ....
Now for me, twrp is my ONLY recovery, and decryption works just fine in twrp .. when I reboot to recovery I don't have the original one on any slot... But that was my own preference... And once I loaded twrp and was able to enter passcode to decrypt my data, then I flashed magisk again INSIDE twrp. I don't know if this helps in any way but it sure didn't harm!
Attachments
-
Screenshot_2023-02-06-13-49-14-51_fc704e6b13c4fb26bf5e411f75da84f2.jpg -
Screenshot_2023-02-06-13-38-47-19_d5715f55f4275eb1c7563b8b2c000f1d.jpg -
Screenshot_2023-02-06-13-48-57-67_fc704e6b13c4fb26bf5e411f75da84f2.jpg -
Screenshot_2023-02-06-13-40-40-29_40dbc481ca5b738a325e5182fc08a331.jpg -
Screenshot_2023-02-06-13-39-12-82_0ecf870e1d5390b9ac21ebc76f00749d.jpg
I did exactly this.
The instructions in the OP are written to make us achieve this.
So if we followed them we ended up with TWRP flashed on both slots.
In my case, when i decided to unlock the bootloader i had PIN security enabled, so, it happened exactly as you said: the first time i entered in TWRP, it asked me my pin and then entered and decrypted succesfully and then i deleted "nandata" folder so backup don't fail and i made a full backup with everything ticked.
So, at this state i had a full backup with everything ticked of a NON ROOTED NE2215.C.22 phone with TWRP flashed in a and b slots.
Then booted into system, all ok. So i rebooted again into TWRP and flashed magisk, rebooted into system, installed magisk apk, checked that root was working OK, and booted into TWRP to made a second backup, this time with the phone rooted.
Then i booted into system and only changed the wallpaper. My aim was to test restoring this second backup and confirm everything was OK and my TWRP was making working bakups and restoring well.
Then, after succesfull restore message from TWRP (with all partitions ticked) I rebooted and got stuck on boot animation.
The only way i found of booting into system again was making a Wipe from TWRP and start with an out of the box android 13 BUT with all my files in data folder and rests of half applied root...
So...
a) are you or someone being able to boot into system succesfully AFTER a succesful restore from TWRP ?
b) What am i doing wrong to not being able to boot into system after successful TWRP restore? (also tried without security PIN enrolled and still got stuck on boot animation!).
Thank you very much @beatbreakee for all your hard work AND for sharing it and for your ideals. You make the world a less ****tier place.
Last edited:
being in NE2215_11.C.22, rooted and with TWRP on both of recovery slots:
Can somebody tell me what would happen if i flash through TWRP the 4,5 gig zip file of full NE2215_11.C.22?
Can somebody tell me what would happen if i flash through TWRP the 4,5 gig zip file of full NE2215_11.C.22?
What do you plan to do with the phone rooted and with TWRP?
I guess i want to know what the posbilites are on what I can do
Well, I WAS planning to make TWRP backups and mess and tweak the hell out of it without fear and if something went wrong simply restore as i allways did with my OP 5T and OP 2 BUT everytime y restore a TWRP backup i got stuck in boot animation and the only way i found to be able to boot is wiping (factory reset) from TWRP. So, I don't loose any data but is very annoying having to start all over again!
So i wanted to know how could i "restore" NE2215_11.C.22 the closest to stock possible (i don´t care relocking bootloader because i will root it again)
The best way to restore this device closest to stock is to do a full flash of the downgrade package in local update. You'll be back down to A12 and as stock as you can get without MSM, then just update back to A13 and the correct revision (C branch) you would like.
Thank you very much for this answer !
So i wil end up like i had it when opened from the box as nothing happened? (stock recovery, locked boot loader)
Can you tell me (and this thread) exactly what tool is needed (have to flash only or make another thing like deleting cow files...), which file, where to download, links, everything that worked out OK for you?
Or maybe links or names of another threads that has this info ?
You do not want to flash this device without local update apk, that will usually lead to more issues than it's worth. Here are the downgrade packages. Make sure to use them as they say, take the rollback zip in Local Update APK. That's the safest way I know of to return your phone to as close to stock as possible.
Last edited:
Have the exact same problem. So how does one update the system? There appears to be no full c26 stock rom, only the OTA. How to proceed?
Similar threads
Top Liked Posts
-
There are no posts matching your filters.
-
1
Thank You !
a)
Have you made this procedure yourself?
b)
Is not a risk the fact that i am in NE2215_11.C.22, rooted and with TWRP in borh slots ?
c)
I mean: this way will flash an image that overwrites ALL partitions of the phone including both recovery partitions?
c.1)
it also include data partition so we must not leave anything we care inside the phone before making this procedure ?
d)
So, from that OnePlus Forum post you shared:
We must use this app:
to load this file:
Thank You!1
Hey, sorry about the timing. I hope the process went well for ya.
I've not done this myself, I just have seen that this is the best and only official way to get your phone to as close to stock as possible. I'm not sure if it will flash the recovery's as well, you may need have the original images for those. But it will wipe data partition for sure. And lastly, yeah. Use that app to take the rollback package.1
Thank you very much for answering, i was really waiting your input...
I did not had the guts to do it before your answer and i don't know if i have them now...
You "saw" like in other posts that someone(s) did it and worked for him/them ?
Fear to brick if this procedure does not flash recoveries a and b and if i flash them separately one tiny bit change and broom...
Besides the fear... I would really like the ability that TWRP provides of doing backups !! This is for what i installed it! He has been protecting us since it came out!
It would be awesome if someone reply to really know if someone was actually able of restoring a TWRP backup and then boot system normally!
Maybe i am doing something wrong putting all the checks in all partitions and modem, etc and is not needed to include all and therefore it will not restore all and won't get stuck at boot-animation ?1Yes. You can do your own research if you want, it's all here or on the sister forum the mods don't like mentioned. That rollback zip is the safest and officially released way to revert back to close stock. I'm not sure if it flashes recoveries, as I haven't seen that question asked before tbh.
I've only seen one guy here claim to restore a TWRP backup and have it working on this device and that's @Canuck Knarf iirc, (apologies if I got the user wrong, I'll cross reference when I get home from work) he's got a psuedo bypass for engineering mode from a successful TWRP backup.
I, myself, have decided TWRP isn't worth it on this device since it must be flashed to the device and I've seen multiple people create backups that lead them to bootloops. Not worth the hassle. -
16Please note, the TWRP image used IS NOT the official TWRP image.
I am not responsible for any any harm, such as bricking, or bootloops, which may happen to your device. This is what worked for me.
Warning
As stated by @beatbreakee , do not flash anything on a T-Mobile related device.
Please read beatbreakee's comment regarding this.
Warning
This has only been tested on Android 13. This guide may not work for other Android versions.
Prerequisites
- Unlocked Bootloader
- Magisk 25.2 Installation ZIP (see attached files)
- TWRP Image (download from GDrive)
- ADB and Fastboot tools are installed on your machine. Please see this guide
- Android 13
Step 1 - Unlocking Bootloader:
1.A - Enable OEM Unlocking:
1. Open Settings Application -> About device -> Version -> Tap on Build Number 7 times
2. Open Settings Application -> Additional Settings -> Developer Options
3. Enable OEM Unlocking
4. Enable USB Debugging
1.B - Entering Bootloader
The bootloader must be unlocked in order to flash the recovery.
Ensure the device is connected to the computer via ADB by entering the following command
Code:adb devices
The output should be something similar to this:
(note the device name on the left will not be the same)
Reboot into the bootloader by entering the following command:
Code:adb reboot bootloader
1.C - Unlock
Once entered, enter the following command:
WARNING: THIS WILL WIPE ALL DATA ON THE DEVICECode:fastboot flashing unlock
Use the volume keys to select unlocking, and then use the power button to confirm.
Once complete, enter the following command:
Code:fastboot reboot
You will now have to go through the device setup.
Repeat steps 1.A and 1.B to enter back into the bootloader
Step 2 - Flashing TWRP:
2.A - Entering Bootloader
Repeat steps 1.A and 1.B to re-enter the bootloader
2.B - Flashing TWRP:
Again, this IS NOT the official TWRP image. I am not responsible for any harm which this may cause to this device. That being said, it appears to be functional.
The image used is from a leak found on this XDA post
This is not a bootable image. You must flash. fastboot boot img will not work
Enter the following commands to flash the TWRP image:
Code:fastboot flash recovery_a twrp.imgCode:fastboot flash recovery_b twrp.imgCode:fastboot reboot recovery
You should notice you are in TWRP.
You may need to change the language to English.
2.C - Changing TWRP Language:
1. Tap on the button on the Second column, Third Row
2. Tap on the World icon
3. Select your language
4. Tap on the button on the bottom right corner of your display.
2.D - Booting into your phone
1. Select Reboot
2. Select System
You should now have successfully booted in the system with TWRP installed as your recovery
Step 3 - Flashing Magisk:
3.A Preparing the Device:
1. Move the Magisk-v25-2.zip to your device
2. Reboot into your recovery / TWRP
This can be done by entering the following ADB command:
Code:adb reboot recovery
3.B - Flashing Magisk:
1. Tap Install
2. Select the Magisk-v25-2.zip
3. Swipe to flash (this may take some time)
4. Tap Reboot
5. Tap System
You should now enter the device
3.C - Installing Magisk APK
Install the Magisk APK, click here to download the APK.
Install the APK, and you should have root!
If you encounter a createTarFork() exited with error 255, do the following:
1. Reboot into TWRP
2. Select File Manager
3. Navigate to /data
4. Copy /data/fonts into /sdcard/
5. Copy /data/nandswap into /sdcard/
6. Delete /data/fonts
7. Delete /data/nandswap
The error should now be resolved
The deleted files should not cause any issues. If any issues do occur, then promptly restore them using the backups made to /sdcard/.
Step - Bypassing Safetynet:
This is optional; however, highly recommend
Note, due to the nature of Safetynet, this can change at anytime and may begin failing in the future.
A - Repackaging Magisk
1. Launch Magisk Manager
2. Tap Settings Icon (Top Right Corner)
3. Tap "Hide The Magisk App"
4. Enter New Application Name
5. Click OK and wait
6. Uninstall original Magisk APK if it has persisted
B - Enable Zygisk & Deny List
1. Launch Magisk Manager
2. Tap Settings Icon (Top Right Corner)
3. Enable "Zygisk"
4. Enable "Enforce Deny List"
C - Configure Deny List
it is recommended to add any application you would like to hide from Magisk here
1. Launch Magisk Manager
2. Tap Settings Icon (Top Right Corner)
3. Tap "Configure DenyList"
4. Tap the 3 dots in the top right and select "Show System Apps"
5. Select the following applications:
~ Android System
~ Google Play Store
~ Google Play Services
~ Google Services Framework
D - Delete App Data
1. Launch Settings Application
2. Select Apps
3. Select App Management
4. Clear data for the following apps:
~ Google Play Store
~ Google Play Services
~ Google Services Framework
5. Reboot the device
E - Flash Universal Safetynet Fix
1. Download the Universal Safetynet Fix
2. Launch Magisk
3. Select Modules
4. Select "Install From Storage"
5. Select Universal Safetynet Fix
6. Wait for Flashing to complete
7. Reboot
F - Test Safetynet
1. Install YASNAC
2. Grant Super User rights
3. Select "Run Safetynet Attestation"
If both checks pass, you successfully have passed Safetynet!
5
Absolutely despicable and such an anti-consumer technique.
This stands against everything OnePlus was. It's sad to see OnePlus turn into such an anti-developer phone
A Carrier should never have this much power over a device. It is absurd4also everyone should know, that EVERY fw on the internet no matter whether it is labeled, 2213, or 2215... 2217, as well as 2413-2419 ALL have EVERY other model's manifest built in and all of the restrictions / bloatware that each region comes with, saved into the OFP extracted files.... so there really is nothing that expressly was bricking your phones by simply flashing a different labeled FW..... the brick came from the manifest reading the region identifiers that the manifests are labeled under.... it is a file that is again picked by some random hidden check inside the TMO EFS, and as soon as your phone tries to boot the newly flashed FW, the TMO Lock is what bricks your phone, to either a bootloop state, or if you continue to force a flash by using Fastboot , you will have a non responsive phone, thanks to this stupid security issue. If unresponsive, the only way out is MSM Tool... and i can help you locate your test points if your buttons dont work.
I cannot publicly post a picture nor a description of where the test points lie inside the 10T , because i already got a cease and desist letter from BBK and i dont know if they have said anything to the mods here about posting Undisclosed hardware access points.... but ive been a member here almost 10 years, and i aint risking a ban from a tattle tale company! There are test points on the 10 t though,.. just well hidden!
The 2nd pic is of the 2217 Unpacked OFP , yet the build prop shows a 2210-2211 base in one and a 2413-2415 base in the.... with NO 2217 in either prop,or manifest file, yet when my phone was flashed back from Brick status, THIS is the FW that was used, and my phone identifies as a 2217 NA now..... can oneplus be any more clear that they have completely turned against us, by straight SHOWING US that they are being super cryptic and sneaky in something as common as the BUILD.PROP files?!?4
Following the method created by @dladz should still work perfectly fine!I wonder about any major issues with this TWRP as of now. Updating ZIP OOS13 with flashing magisk direclty is working etc.?
There could still be issues with this TWRP as this is not an official image.
AFAIK Switching ROM is still untested, but decryption, backups and flashing are all confirmed working, which for me makes me feel significantly more comfortable4i wouldnt advise ANYONE with an original TMOBILE device, ANY attempt to flash ANY firmware from the official builds just yet. Tmobile embedded a VERY WELL HIDDEN check into the EFS partition that only appeared in builds after 11_A.14 ... This check forcefully activates a lock triggered by the CarrierDevicePolicy.xml in the efs system... and if the Region and model does not match the original build that it came with, all of your apps will be completely disabled and there is nothing accessible but the settings button. It also disables ADB/USB debugging completely, and deauthorizes your computer from the adb wireless keys too... then it removes the USB DEBUGGING toggle from settings, followed by a persistent message that your phone is "Violating Contract Policy... Please contact after sales for support" ... Tmobile cannot remove this warning... and even them sending an UNLOCK request to your phone for APPROVED will get ignored by your phone. You can hear ringing, but cannot accept calls... hear emails but not open them,.. and you dialer is in emergency calls only!...
At this point you will think panic is the only option, but instead just Pull your sim card, and use your buttons to force reboot and enter recovery .... Then do a Format Data ,,,, followed by a reboot, but do not put your sim back in... Until you go thru the whole setup wizard, enable usb debugging, and then flash a rollback package to a fw earlier than the one i listed above, your phone will INSTANTLY lock again any time you insert ANY sim card.
Im very sure that there is a system process that can be disabled which will at least block the lockout.... but i dont have that knowledge as to which process(es) are calling it! A logcat generated about 15 screens on my computer as soon as i plugged a sim in... so that was too much for me to sift thru. This is present on both the 10 Pro and 10 T so be warned.... If you are already not using your original T-MO firmware, but you also have been loading other regions with no problem, that does not matter.... I have found an exact reference to the ORIGINAL FW build and Model # that was loaded by TMO at the factory level, in several different TXT and XML files inside the EFS part. AND my 10T and 10 Pro BOTH have been fully bricked, then formatted and flashed thru an authorized MSM Account.... Doing an ERASE ENTIRE FILE SYSTEM, thru msm, did not get rid of this file, so i doubt a twrp level wipe will do it either... MAYBE an "unlock Critical" in Fastboot, followed by a "Fastboot wipe", "DM-verity disable", and "VB-Meta erasure" MIGHT take out this crazy security system, but i know this .... if you flash an original FW using TWRP, it has protections in it to keep IT (twrp) from being overwritten, so you might find yourself in bootloop territory if you region hop.... cuz the fw might notice the changes to the partitions... For now, until someone is brave enough to challenge the Android 12 kernel and remove these trapdoors, I would just be happy you have TWRP, and wait for the person who finds and slays the Tmobile Dragon hidden in our phones! But this is truly an android 12 function that was put in place for Carrier and Manufacturer benefit ONLY. Another strike against 1+
