Hi. So I wanted to put together a little write-up on how to root the T-Mobile McLaren 5G variant, at least how I rooted mine, as there doesn't seem to be anything about this yet. I was actually able to root my device last night successfully, so I hope this guide helps others go through the process.
**WARNING** Unlocking your bootloader will render your phone unable to take OTA updates! This is a newly discovered problem that hopefully will be fixed soon. But currently, unlocking the bootloader will wipe your data and also a reserve.img needed for the OTA updates. Proceed with caution!
*I do not take ANY credit for this work. I am simply gathering data from various sources into one single reference guide*
*Credit is due to HolyChickenGuy and dstryrwiz mostly, as I gathered most of the data from these members. Also, topjohnwu of course for Magisk.*
So, anyhow, with this version of the OnePlus Pro 7T being carrier-locked, you must of course follow different procedures than a typical unlocked phone. And because OnePlus thinks they are special somehow, you also have to obtain an unlock code for the bootloader. :laugh:
Steps that I followed:
1. Obtain SIM unlock status via T-Mobile. In order to do this, I simply just asked a T-Mobile employee via Twitter if they could provide me a permanent unlock. And without any issues, they were very kind to do so....even after day 2 of owning the phone. And on the EIP, it's not paid off.
2. After getting them to add your IMEI to the unlock list, go to the system settings --> WiFi & internet --> SIM & network section. There will be an option called "Network Unlock" at the very bottom under the 'Advanced' section. Click that and then go through the prompts. You want to choose "Permanent Unlock". Then, if T-Mobile made on their promise, it should ask to reboot...after which the 'OEM unlocking' option under the Developer Options will no longer be grayed out. Woohoo!
3. After obtaining successful SIM unlock, now you have to submit a form to OnePlus to obtain the actual unlock.bin file to get the bootloader unlocked, generated from a unique 64 character code you will obtain in the next step.
Ensure that USB Debugging is turned ON. In fact, make sure it's always on during this entire procedure, because it's required. Enter fastboot mode via holding the power and volume DOWN buttons during boot up. Or easiest way is to simply soft reboot with the "Advanced reboot" option enabled from the Developer Options. Once in fastboot mode, enter the following command to obtain this 64 character code...fastboot oem get_unlock_codeThis will spit out that 64 character code. Now go to this page, sign in, and fill out the form to submit for the .bin file.NOTE: This takes at LEAST 7 days to get the .bin file. For whatever reason...it must be an automated system. I tried contacting them twice, but they wouldn't budge and told me I had to wait. LOL. And it seriously took EXACTLY 7 days and like 12 minutes for the email to arrive.
4. So after you have the "key" to finally unlock this darn phone, enter fastboot mode again and enter the following commands...
fastboot flash cust-unlock "%path\to\unlock_code.bin%"fastboot oem unlock <<-- This step will ERASE everything on your phone. Most people know this, but I have to say it. Internal storage will be wiped too. :good:
Finally, the phone is unlocked. Now we can root it.
*I used various information from different forum postings...and some previous knowledge of course. Again, I don't take credit for any of this. I'm just following instructions.
5. Download the unofficial TWRP .img file for the OnePlus 7T Pro from here. To be honest, I am not even sure if using TWRP for this part is really necessary, but somehow I came to that conclusion. LOL. This process worked for me, so yeah. Anyhow, enter fastboot mode again and boot to TWRP (do NOT flash it!) by entering the following...
fastboot boot "%path\to\twrp-3.3.1-5-hotdog-unified-mauronofrio.img%"Now in TWRP, enter the following commands to extract your stock boot.img file...
adb shell dd if=/dev/block/bootdevice/by-name/boot of=boot.imgadb pull /boot.imgThis will copy your boot.img file to wherever adb is running on your computer.
6. Take that boot.img file and copy it over to your internal SD on your phone. Boot your phone up as normal, and go grab Magisk Manager from Git here. Open up Magisk Manager, expand the "Advanced Settings" option, and check the "Preserve force encryption" and "Preserve AVB 2.0/dm-verity". Select the "Install" button from the regular Magisk option and choose "Select and Patch a File ". Find your boot.img file and Magisk Manager will created a patched .img file. Copy this new .img file from your phone over to your PC.
7. Enter fastboot mode again. Now just boot from this newly patched .img file by entering the following...
fastboot boot "%path\to\magisk_patched.img%"
8. Final step. And hopefully your phone boots up.
*If not, and you're stuck in a boot loop...you might need to make the A or B partition active. To do this, while back in fastboot mode, enter either command (most likely B)...
fastboot --set-active=afastboot --set-active=bAgain, hopefully the phone just booted up normally without having to do that. Now in your phone, open up Magisk Manager again and simply choose the same Install option, but instead select "Direct Install". Magisk will now flash that .img file, ultimately granting permanent root privileges.
Reboot and enjoy!!
***Here is a good write up on adb and how to get it running on your PC....https://www.xda-developers.com/install-adb-windows-macos-linux/***
worked like a charm, now all we need it global firmware. any idea on getting twrp installed?
which device did you select from the OnePlus token unlock? it doesnt have an option for 7t pro mclaren, only:
OnePlus 6t
OnePlus 7 pro
OnePlus 7t
OnePlus 7t (5g)
TapRooted said:
which device did you select from the OnePlus token unlock? it doesnt have an option for 7t pro mclaren, only:
OnePlus 6t
OnePlus 7 pro
OnePlus 7t
OnePlus 7t (5g)
Click to expand...
Click to collapse
The 5G one.
Bildo41383 said:
worked like a charm, now all we need it global firmware. any idea on getting twrp installed?
Click to expand...
Click to collapse
Great! Yeah I wish. TWRP doesn't work yet even just booting it. You can't mount system and it won't decrypt. You can use it with a decrypted system, but I think it still won't mount the system partition, so there's really no point.
js042507 said:
Great! Yeah I wish. TWRP doesn't work yet even just booting it. You can't mount system and it won't decrypt. You can use it with a decrypted system, but I think it still won't mount the system partition, so there's really no point.
Click to expand...
Click to collapse
Good to know, I was going to decrypt my phone just but there is no point of doing this if I can't use TWRP =/ ...
stock and magisk patched 5G McLaren boot images
OnePlus 7T Pro 5G McLaren
2 boot images (zipped with ZArchiver app), one is stock and the other patched with latest available Magisk.
4.14.117-perf+
#1 Wed Dec 4 20:44:37 CST 2019
Android security patch level
November 1, 2019
As mentioned, booting the unzipped Magisk patched boot image requires an unlocked bootloader.
I've tried getting my phone permanently unlocked with 2 different reps.
They both gave me the same answer, need this phone to be on the network for 40 days before they're willing to assist me any further.
Curious to know what you've said to get them to assist you so early.
Was hoping there's a workaround for this, but there doesn't appear to be one.
https://forum.xda-developers.com/oneplus-7t/how-to/t-mobile-free-op7t-sim-unlocking-t4014053
There is. Works for the 5G.
LLStarks said:
https://forum.xda-developers.com/oneplus-7t/how-to/t-mobile-free-op7t-sim-unlocking-t4014053
There is. Works for the 5G.
Click to expand...
Click to collapse
Yep, this guy unlocked mine pretty quick.
incinandseril said:
I've tried getting my phone permanently unlocked with 2 different reps.
They both gave me the same answer, need this phone to be on the network for 40 days before they're willing to assist me any further.
Curious to know what you've said to get them to assist you so early.
Was hoping there's a workaround for this, but there doesn't appear to be one.
Click to expand...
Click to collapse
Yeah, like I stated before, I simply asked them via Twitter DM. No questions asked. I told her that I wanted to unlock my phone for rooting, etc...and she obliged without any issues. I don't know. Try again maybe. Or use the other method people have posted.
Edit: This is literally what I said...
"Hi. I just recently purchased the new OnePlus 7t McLaren phone this past weekend, and I am definitely loving it. However, I noticed that I am unable to unlock my device. This is always something I do, so I can run certain tasks from my phone. Is there anyway somebody could please send me a permanent unlock code?? I would very much appreciate it!!!"
What's crazy is the fact that the person I spoke with on Twitter said that she won't do it because I was honest about wanting it unlocked for rooting purposes.
"It's super important that we set the right expectations. To protect our customers, T-Mobile does not support rooting (or un-rooting) Android devices.We never advise customers to root a device for any reason. Once a device is rooted, it is treated as a 3rd Party Device, meaning we are unable to troubleshoot if there are issues later on - this would also cause the warranty on the device to be voided.
If the device meets the unlock requirements (found here: https://t.co/ypU2LH9DIX) we can definitely assist with unlocking it, however we do not advise/cannot assist with rooting the device. I hope that clears things up a bit, but please let me know if you have any other questions."
I guess you lucked out with the person that helped you out.
I've messaged the guy from the other thread in hopes of a response about being able to assist me.
incinandseril said:
What's crazy is the fact that the person I spoke with on Twitter said that she won't do it because I was honest about wanting it unlocked for rooting purposes.
"It's super important that we set the right expectations. To protect our customers, T-Mobile does not support rooting (or un-rooting) Android devices.We never advise customers to root a device for any reason. Once a device is rooted, it is treated as a 3rd Party Device, meaning we are unable to troubleshoot if there are issues later on - this would also cause the warranty on the device to be voided.
If the device meets the unlock requirements (found here: https://t.co/ypU2LH9DIX) we can definitely assist with unlocking it, however we do not advise/cannot assist with rooting the device. I hope that clears things up a bit, but please let me know if you have any other questions."
I guess you lucked out with the person that helped you out.
I've messaged the guy from the other thread in hopes of a response about being able to assist me.
Click to expand...
Click to collapse
I spoke with someone in the TMo app, and I told them I needed my phone unlocked because I use my phone when leaving the country for work and it's important to be able to use it. He had no problem unlocking it. I did the same thing unlocking the 6T.
Has anyone tried setting up Gcam with App Systemizer? Or is that too risky at the moment?
LLStarks said:
Has anyone tried setting up Gcam with App Systemizer? Or is that too risky at the moment?
Click to expand...
Click to collapse
I did just a couple days ago and it's SO worth it. No issues at all either. I can even switch between all 3 lenses without any problems. The portrait mode is night and day with the stock camera. If you have questions about the process, let me know.
js042507 said:
I did just a couple days ago and it's SO worth it. No issues at all either. I can even switch between all 3 lenses without any problems. The portrait mode is night and day with the stock camera. If you have questions about the process, let me know.
Click to expand...
Click to collapse
I would like to get this setup as well ?
As long as it's idiot-proof, I'm in. My main concern for this device at the moment is rescue methods. I'm hoping nothing should require more than reflashing stock boot if things go wrong. But here we are dealing with Magisk modules. If a module goes haywire and starts causing bootloops, is disabling the module in TWRP possible over adb if we can't decrypt the partitions? Would a factory reset using either TWRP or stock recovery be the only way out? Or do we just reflash stock boot?
incinandseril said:
I've tried getting my phone permanently unlocked with 2 different reps.
They both gave me the same answer, need this phone to be on the network for 40 days before they're willing to assist me any further.
Curious to know what you've said to get them to assist you so early.
Was hoping there's a workaround for this, but there doesn't appear to be one.
Click to expand...
Click to collapse
I told them I was traveling for the holidays. They had me pay $75 on the phone (2 EIP payments) then unlocked it for me.
Do I need to do both "unlock_code.bin%" and "fastboot oem unlock" at the same time? or can I just do the unlock_code.bin now and the oem unlock sometime in the future when I'm ready to unlock the bootloader?
justthefacts said:
Do I need to do both "unlock_code.bin%" and "fastboot oem unlock" at the same time? or can I just do the unlock_code.bin now and the oem unlock sometime in the future when I'm ready to unlock the bootloader?
Click to expand...
Click to collapse
You have to run the flash command using the .bin file first...then it will let you run fastboot oem unlock. They are separate commands. And yes, you could run the unlock command later. But I think you'd have to do the .bin command again when you're ready. I'm not sure to be honest.
Related
OFFICIAL ONEPLUS 2 STOCK RESET
SOURCE : OnePlus L2 Support Team
VERSION : OxygenOS 2.2.0
DOWNLOADS
1. OnePlus2 Stock Reset Oxygen OS 2.2.0 Google Drive | Mediafire
2. Qualcomm Drivers Version 1.00.11 Google Drive | Mediafire
INSTRUCTIONS
You are doing this on your own responsibility. I take no responsibility whatsoever.
(THIS WILL WIPE YOUR ONEPLUS INCLUDING INTERNAL SD)
Download both the files from above and extract them (WinRAR, WinZIP, 7ZIP etc). You should have 2 folders: "OnePlus2_14_A.11_151211" and "qc"
A. Install the Certificates followed by the Qualcomm drivers.
1. Restart your computer with Driver Signature Enforcement Disabled (Advanced Startup) Let me Google it For You
2. Open the folder "qc" and install the Test Certificate in the following Stores: Trusted Root, Trusted Publisher, Third-Party Root and Personal
3. Run the Qualcomm setup wizard (also located in the qc folder)
4. When completed, restart your PC again with Driver Signature Enforcement Disabled (Advanced Startup)
5. Turn off your phone and disconnect the USB cable from the phone.
6. Hold vol-up and plug in the USB(Do not press Power button). The screen will stay black but you will hear a sound from windows that a device is attached.
7. The driver should now automatically install. If not, go to device manager and right click "Unknown Device" and click "Update Driver" Search up the QC folder and press ok. The driver should now install. (Got the RELINK issue? Take a look here: http://forum.xda-developers.com/show...1&postcount=46)
B. Flashing Process
1. Open the OnePlus2_14_A.11_151211 folder and open "MSM8994DownloadTool.exe"
2. Look if your phone is detected in the list. everything is Chinese but you will see one row with different chinese text from the rest within the list. If not, recheck if driver is detected in Device Manager (If not, go back to Step A - Line 4).
3. First click the right square Chinese button. This will perform an integrity check on the downloaded files by verifying the MD5 hash values.
4. The system will seem to hang for a bit but should give you a pop up with the results of the above verification. When everything is ok. Press the start button. and let the progress finish. (If something is not ok, you will have to re-download the images. Google Drive can help extract only the necessary files.)
5. When it's done. Disconnect the USB cable and turn on the device.
C. Reset TAMPER Flag (Optional)
(This may potentially change your SmartPhone to a rather large paperweight and I will just laugh at you bearing no responsibility)
+ This part of the guide is not an Official Procedure and is in no way affiliated to OnePlus
+ It is advisable to do this before any of the above mentioned operations.
+ Prerequisites:
Root
HEX Editor with root features
Root File Manager
+ BEWARE: You are modifying partitions which cannot be restored regardless of what you flash. You have been warned AGAIN
1. In File Manager browse to the devinfo partition (dev/block/bootdevice/by-name/)
2. Open devinfo using the HEX Editor.
3. Modify the TamperBit (attached screenshot) from 01 to 00.
4. Save and reboot to fastboot.
5. Type fastboot oem device-info to confirm.
CREDITS
OnePlus Team for the Files.
@paultje162 for adaptation of Instructions. Refer his thread here if you are looking for an older version of stock reset (2.1.1).
@thedropdead for his work on Tamper Reset
If this thread has helped you, do press the THANKS button. Should you have issues, questions or doubts, write in this thread.
Just need to confirm that these files are actually official
Pm me the s3 support link
---------- Post added at 13:14 ---------- Previous post was at 13:10 ----------
And my friend
You need to install the test certificate first !
Edit:- file confirmed legit ! Totally official, way to go, @fareed_xtreme !
[email protected] said:
Just need to confirm that these files are actually official
Pm me the s3 support link
---------- Post added at 13:14 ---------- Previous post was at 13:10 ----------
And my friend
You need to install the test certificate first !
Click to expand...
Click to collapse
Thanks for spotting the error. I have fixed the heading. S3 Link PMed.
fareed_xtreme said:
Thanks for spotting the error. I have fixed the heading. S3 Link PMed.
Click to expand...
Click to collapse
Whenever you get drivers like this, dig into their folders and you'll find important documents and instructions to use
That is how I found out about this certificate
Is there any similar process por ONEPLUS ONE?
I only have fastboot mode, without recovery and bootloader locked (fastboot oem unlock doesn't work)
http://forum.xda-developers.com/showthread.php?t=2970390
@xbit
xbit said:
Is there any similar process por ONEPLUS ONE?
I only have fastboot mode, without recovery and bootloader locked (fastboot oem unlock doesn't work)
Click to expand...
Click to collapse
Quick search and: http://forum.xda-developers.com/oneplus-one/general/guide-unbrick-oneplus-one-t3013732
beaverhead said:
http://forum.xda-developers.com/showthread.php?t=2970390
@xbit
Click to expand...
Click to collapse
This didn't work for me:
fastboot oem unlock didn't work because I had a corrupt bootloader.
Spannaa said:
Quick search and: http://forum.xda-developers.com/oneplus-one/general/guide-unbrick-oneplus-one-t3013732
Click to expand...
Click to collapse
But this was great! My OPO is alive now. Thanks
Thank you!!!! this worked.
I was eventually able to get the restore program to recognize it and restore it so it could boot normally. Thank you!
Download from your Link
https://drive.google.com/folderview?id=0BxFd4Zc3_d1CWDdOSFFIVG42VTg&usp=sharing
the File:
OnePlus2_14_A.11_151211.rar
Extract it.
But where is the "QC Folder"
found only "OnePlus2_14_A.11_151211"
Your Link to:
http://forum.xda-developers.com/show...1&postcount=46
is wrong. (Not complete) Error 404
Wagi99 said:
Download from your Link
https://drive.google.com/folderview?id=0BxFd4Zc3_d1CWDdOSFFIVG42VTg&usp=sharing
the File:
OnePlus2_14_A.11_151211.rar
Extract it.
But where is the "QC Folder"
found only "OnePlus2_14_A.11_151211"
Your Link to:
http://forum.xda-developers.com/show...1&postcount=46
is wrong. (Not complete) Error 404
Click to expand...
Click to collapse
Yep, the qc folder is missing from the zip.
The link should be: http://forum.xda-developers.com/showpost.php?p=64674951&postcount=46
I suspect these are both down to copying & pasting the instructions from @paultje162's thread and I'm sure @fareed_xtreme will sort it out when he gets the chance.
Wagi99 said:
Download from your Link
https://drive.google.com/folderview?id=0BxFd4Zc3_d1CWDdOSFFIVG42VTg&usp=sharing
the File:
OnePlus2_14_A.11_151211.rar
Extract it.
But where is the "QC Folder"
found only "OnePlus2_14_A.11_151211"
Your Link to:
http://forum.xda-developers.com/show...1&postcount=46
is wrong. (Not complete) Error 404
Click to expand...
Click to collapse
Thanks for spotting the errors. I have updated them. It is indeed a miss on my part in regards to the QC. Hence I have uploaded it separately and updated the instructions.
Spannaa said:
Yep, the qc folder is missing from the zip.
The link should be: http://forum.xda-developers.com/showpost.php?p=64674951&postcount=46
I suspect these are both down to copying & pasting the instructions from @paultje162's thread and I'm sure @fareed_xtreme will sort it out when he gets the chance.
Click to expand...
Click to collapse
Yup, A copy paste is not the right way to copy a link. Haven't been around these threads for quite some time and guess i did not remember that the links are trimmed down. Thanks for the correct link.
Updated Information with UnTamper Guide
Hello
Doing the anti tamper method you did. Shouldn't this be easier by doing "fastboot oem lock" ?
I think it should have the same effects. Of course, this command must be done when an official ROM is on the phone, doing this in a custom ROM can cause unexpected behaviour, including bricking.
albertocastillo2001 said:
Hello
Doing the anti tamper method you did. Shouldn't this be easier by doing "fastboot oem lock" ?
I think it should have the same effects. Of course, this command must be done when an official ROM is on the phone, doing this in a custom ROM can cause unexpected behaviour, including bricking.
Click to expand...
Click to collapse
From my personal experience, if the Tamper Flag trips, then no matter how official you go it will not go back to Device Tamper= False.
The files in my First Post restores your phone back to an out of box phone state even locking the bootloader but it will not change the tamper flag. Those files are used by OnePlus Support to fix OS issues. Also the fastboot oem lock has not managed for me personally to get the tamper flag back to default (Same as in OPO once down, its down). So the only way for now for the OPT is by modifying the bit that handles the tamper flag.
You are right. Tamper Flag usually trips when you try to relock the bootloader when having root and other non-stock partitions (custom kernel, recovery etc). (Learned the hard way with my old OnePlus 2. Got it swapped for a new one though as the old one was faulty )
Hope this helps.
fareed_xtreme said:
From my personal experience, if the Tamper Flag trips, then no matter how official you go it will not go back to Device Tamper= False.
The files in my First Post restores your phone back to an out of box phone state even locking the bootloader but it will not change the tamper flag. Those files are used by OnePlus Support to fix OS issues. Also the fastboot oem lock has not managed for me personally to get the tamper flag back to default (Same as in OPO once down, its down). So the only way for now for the OPT is by modifying the bit that handles the tamper flag.
You are right. Tamper Flag usually trips when you try to relock the bootloader when having root and other non-stock partitions (custom kernel, recovery etc). (Learned the hard way with my old OnePlus 2. Got it swapped for a new one though as the old one was faulty )
Hope this helps.
Click to expand...
Click to collapse
Thanks for your reply. I noticed that these are the files that OnePlus team sends you when they want to remote into your device to flash the system. I noticed these are password encrypted. I have a session with them on Monday 6th.
I sent the files they sent me to decryption to get the password to a website that does this. However, they couldn't. My other plan was just to catch the password when having the remote session with them.
Since you already posted the files here, this is no longer needed. Seems you did this earlier than me.
The reason they want to do a full flash on my phone is due to the fact that I have a dual SIM issue. At the beginning both SIMs worked until I had to do a change on the second SIM network (it's an international SIM card that works in every country so you must set up the network manually). Since I tried to change the network. Something got messed up and now only one SIM works at a time. I tried restoring the network settings to automatic with no go. And I also tried to do hard restore on the phone to start over to ensure this would solve the issue.
This didn't solve the issue. So it probably means the settings were done in a partition which is not "/data". So a hard reset obviously wouldn't work. But a full flash surely will.
I asked them if I could do this myself by just sending me the files. I have a good expertise on fastboot, ADB and Linux, and I also understand the partition list and partition images. However, since the phone is not rooted or modified in anyway. I decided I will let them do it for me.
I do have a question thought. How did you find about the anti tamper thing? I assume you had remote session with them, and this is why you have those files. Did they "relock" this for you?
I assume they look at this when they get defective devices returned.
Thanks
albertocastillo2001 said:
Thanks for your reply. I noticed that these are the files that OnePlus team sends you when they want to remote into your device to flash the system. I noticed these are password encrypted. I have a session with them on Monday 6th.
I sent the files they sent me to decryption to get the password to a website that does this. However, they couldn't. My other plan was just to catch the password when having the remote session with them.
Since you already posted the files here, this is no longer needed. Seems you did this earlier than me.
The reason they want to do a full flash on my phone is due to the fact that I have a dual SIM issue. At the beginning both SIMs worked until I had to do a change on the second SIM network (it's an international SIM card that works in every country so you must set up the network manually). Since I tried to change the network. Something got messed up and now only one SIM works at a time. I tried restoring the network settings to automatic with no go. And I also tried to do hard restore on the phone to start over to ensure this would solve the issue.
This didn't solve the issue. So it probably means the settings were done in a partition which is not "/data". So a hard reset obviously wouldn't work. But a full flash surely will.
I asked them if I could do this myself by just sending me the files. I have a good expertise on fastboot, ADB and Linux, and I also understand the partition list and partition images. However, since the phone is not rooted or modified in anyway. I decided I will let them do it for me.
I do have a question thought. How did you find about the anti tamper thing? I assume you had remote session with them, and this is why you have those files. Did they "relock" this for you?
I assume they look at this when they get defective devices returned.
Thanks
Click to expand...
Click to collapse
Please note that the Tamper part of the guide is NOT done by OnePlus. Please note that OnePlus is in no way affiliated to the Tamper part of the guide. The Tamper guide is a result of comprehensive research conducted by thedropdead (information provided in the First Post). The guide is an easier interpretation of all the research that went in there.
OnePlus will only reflash this package which will re-lock the Bootloader only. Tamper Flag is not modified. So sit tight and let them reflash it for you.
You are right to assume I had a session with them earlier and that's how i have the files.
Thanks for your reply.
I would say that if the remote support doesn't untamper the device then it might mean they don't even look at it if the device is returned.
Thanks!
albertocastillo2001 said:
Thanks for your reply.
I would say that if the remote support doesn't untamper the device then it might mean they don't even look at it if the device is returned.
Thanks!
Click to expand...
Click to collapse
Remote Support didn't look into mine. However, not very sure about whether it is checked on returning it. Mine went untampered.
fareed_xtreme said:
Remote Support didn't look into mine. However, not very sure about whether it is checked on returning it. Mine went untampered.
Click to expand...
Click to collapse
Oh, then what happened? I thought the remote support tried to fix your phone. Since you said they didn't untamper the device after I expected they remoted to your phone. What happened then?
Thanks
There is tool from Asus this month to unlock the bootloader. You should know that you lose the guarantee and may no longer receive official updates. After you install the apk and restart the phone, all data on the internal memory will be deleted.
Whoa! the unlock tool is out!
Is there any chance someone can make a root guide? I really want to buy Zenfone 3 Ultra but I wouldn't do it without root method out there. Any help is appreciated.
Were waiting on a dev to compile TWRP for us then we can get root
Trying to root ZU680KL
Hi!
I have unlocked my ZU680KL with the Asus unlock tool. Bootloader shows 'unlocked'.
Then I unpacked the stock boot.img (from WW_13.6.15.21_20161215, this what I have installed) and using Vim I set:*ro.secure=0, ro.adb.secure=0, and*ro.debuggable=1 in default.prop.
Repacked the new boot.img and flashed it with 'fastboot flash boot new-boot.img'.
'adb shell getprop' indicates that the new setting was applied.
Yet in the stock recovery mode I cannot install SuperSU-v2.79.zip and no adb devices are seen in recovery mode.
What else is needed? Do I have to edit something in the stock recovery or must wait for custom TWRP?
I was following the basic instructions found here:
https://machiry.wordpress.com/2012/10/26/getting-root-access-on-android-the-actual-way/
iirc, there's already a thread going where both root & TWRP have been successfully loaded
.
hillg001 said:
iirc, there's already a thread going where both root & TWRP have been successfully loaded
.
Click to expand...
Click to collapse
Any news?
https://forum.xda-developers.com/ze...t-zenfone-3-ultra-7-0-ww14-1010-1703-t3612108
ndi said:
There is tool from Asus this month to unlock the bootloader. You should know that you lose the guarantee and may no longer receive official updates. After you install the apk and restart the phone, all data on the internal memory will be deleted.
Click to expand...
Click to collapse
when the ultra 3 first came out, many suggested waiting for a boot loader unlocker, & not updating any Android versions, because an unlock program might not work on subsequent Android versions. Is that the case? ... or does the unlocker work on the newest Android version too.
Thanks
.
The official download link is
http://dlcdnet.asus.com/pub/ASUS/ZenFone/ZU680KL/ZU680KL_SIGNED_Android_M_UnlockTool_2017_0222.zip
Available from page:
https://www.asus.com/us/supportonly/Zenfone3 Ultra(ZU680KL)/HelpDesk_Download/
I have just downloaded the zip, made the APK and installed it on my Zenfone 3 Ultra.
When I run the app, after clicking all the "are you sure..." acknowledgements, the app does not succeed in unlocking the bootloader. The error message indicates an unknown or perhaps network error, and suggests I "try again later..."
Running WW_14.1010.1804.75_20180612
Anybody else seeing this?
Ideas??
Reading on the ASUS blogs, they indicate it isn't supported anymore (no surprise), but shouldn't it still work??
heroxbd said:
The official download link is
http://dlcdnet.asus.com/pub/ASUS/ZenFone/ZU680KL/ZU680KL_SIGNED_Android_M_UnlockTool_2017_0222.zip
Available from page:
https://www.asus.com/us/supportonly/Zenfone3 Ultra(ZU680KL)/HelpDesk_Download/
Click to expand...
Click to collapse
Note the links above no longer work. Yes, you can get to the page, but the unlocker isn't there any more.
ndi said:
There is tool from Asus this month to unlock the bootloader. You should know that you lose the guarantee and may no longer receive official updates. After you install the apk and restart the phone, all data on the internal memory will be deleted.
Click to expand...
Click to collapse
Does anybody know which version(s) of the stock ROM this works with? I've tried a couple, and all of them just yield the "unknown error" when running the unlocker.
If you know of a stock ROM version this works with, please post a URL for where I can find it (as it's proven really hard to find specific versions...)
Thanks in advance.
agree it no longer works. getting the unknown error...wait message that everyone else is getting. there are other XDA threads that indicate the same.
Keeping bootloader locked. Used ADB to install full root with Magisk and Recovery with TWRP. Phone is working fine and even the SafetyNet checks pass as well. Debloated with ADB App Control program (paid for full version).
-
jrchester said:
Used ADB to install full root with Magisk and Recovery with TWRP. Phone is working fine and even and SafetyNet checks pass as well. Debloated with ADB App Control program (paid for full version).
Click to expand...
Click to collapse
How did you do that? Can I get more details?
Madlzz said:
How did you do that? Can I get more details?
Click to expand...
Click to collapse
Hi Madlzz:
Checkout my XDA post here for more details on how I did this:
unlocking bootloader zenfone ultra
Hi all ive had my zenfone 3 ultra (zu680kl) for some years, until a couple of days ago, my friend wanted to see if my phone could be charged with a dash charger, where others wouldnt my battery was already low and overnight it ran out and when i...
forum.xda-developers.com
- John
Madlzz said:
How did you do that? Can I get more details?
Click to expand...
Click to collapse
Hello. I can confirm that on this phone TWRP can be flashed WITHOUT unlocking the bootloader, since that seems not to be an option anymore (since the official unlock tool doesn't work anymore and neither are the usual commands for unlock).
Indeed it is weird that we can install a custom recovery and root with the locked bootloader but i've done it yesterday and there is no problem. My bootloader is locked, I have TWRP installed and root by Magisk latest.
You just need to boot into fastboot mode (press volume up and power at the same time), connect your phone to PC, go into where you have stored your adb and fastboot folder and in that folder open a CMD prompt and enter the command "fastboot flash recovery" and copy the name of the TWRP for our device after "recovery". And press enter. Then you disconnect from PC and navigate in the fastboot menu to the section "recovery" and press power button to boot into TWRP.
After that you can flash latest Magisk zip from the "install" section in TWRP and there you go, you have root.
And the bootloader will still remain locked, hence the safetynet will pass without any problems (play store certified).
lucy1983 said:
Hello. I can confirm that on this phone TWRP can be flashed WITHOUT unlocking the bootloader, since that seems not to be an option anymore (since the official unlock tool doesn't work anymore and neither are the usual commands for unlock).
Indeed it is weird that we can install a custom recovery and root with the locked bootloader but i've done it yesterday and there is no problem. My bootloader is locked, I have TWRP installed and root by Magisk latest.
You just need to boot into fastboot mode (press volume up and power at the same time), connect your phone to PC, go into where you have stored your adb and fastboot folder and in that folder open a CMD prompt and enter the command "fastboot flash recovery" and copy the name of the TWRP for our device after "recovery". And press enter. Then you disconnect from PC and navigate in the fastboot menu to the section "recovery" and press power button to boot into TWRP.
After that you can flash latest Magisk zip from the "install" section in TWRP and there you go, you have root.
And the bootloader will still remain locked, hence the safetynet will pass without any problems (play store certified).
Click to expand...
Click to collapse
It's what I've been saying and what I posted originally. I posted to help others out. I don't have to argue with users here that say it can't be done. I did it and mine is still working 100% correctly. I stand by what I said originally and what you just posted. And the comment that I was lucky is ludicrous. Luck has nothing to do with it.
jrchester said:
It's what I've been saying and what I posted originally. I posted to help others out. I don't have to argue with users here that say it can't be done. I did it and mine is still working 100% correctly. I stand by what I said originally and what you just posted. And the comment that I was lucky is ludicrous. Luck has nothing to do with it.
Click to expand...
Click to collapse
Yup. It's not a matter of luck. It just can be done without unlocking bootloader on this phone. I can't explain why, because on the majority of phones you can't do anything without unlocking the bootloader. Although an explanation could be the lack of server maintenance from Asus side (since the problem with the unlock tool seems to be from their servers) for this phone. But yeah, you can have TWRP and root on this phone with the bootloader locked. That is a fact.
PS: I'm running the latest official firmware (.75) from Asus.
lucy1983 said:
Yup. It's not a matter of luck. It just can be done without unlocking bootloader on this phone. I can't explain why, because on the majority of phones you can't do anything without unlocking the bootloader. Although an explanation could be the lack of server maintenance from Asus side (since the problem with the unlock tool seems to be from their servers) for this phone. But yeah, you can have TWRP and root on this phone with the bootloader locked. That is a fact.
PS: I'm running the latest official firmware (.75) from Asus.
Click to expand...
Click to collapse
Ditto. Running 1804.75_20180612 official. Also running and keeping Magisk at 23.0 to retain safety check functions. Magisk 24 removes that, but you can reinstall back to 23.0 without any issues and just ignore the updates.
jrchester said:
Ditto. Running 1804.75_20180612 official. Also running and keeping Magisk at 23.0 to retain safety check functions. Magisk 24 removes that, but you can reinstall back to 23.0 without any issues and just ignore the updates.
Click to expand...
Click to collapse
You can install Magisk 24 without any problems. For me it doesn't break safetynet and play store says "certified". Even without enabling zigisk.
Hello! I can't seem to make TWRP Official app (from Google Playstore) and Magisk root to work.... so hacking game is still a distant possibility here. I downloaded both app, but couldn't get them to work, so now uninstalled both.
My phone is: Moto G7-Power with Android 9 (Pie), my questions are:
1. Which of these two should I install first on android without PC? Magisk or TWRP? Seem to get conflicting instruction from those tutorials on Youtube.
2. After downloaded "TWRP Official app" from Google Playstore, chose my phone from the list and downloaded the version for my phone. It said downloaded successful, but I can't flash TWRP, can't open it in recovery mode (hardreset), it wouldn't do anything!
3. As for Magisk apk... one of the two files won't install, the zip files.... it said "failed"... so what do I do then?
Can anyone please help me fix all these problems? Very frustrating right now.
Morky001 said:
Hello! I can't seem to make TWRP Official app (from Google Playstore) and Magisk root to work.... so hacking game is still a distant possibility here. I downloaded both app, but couldn't get them to work, so now uninstalled both.
My phone is: Moto G7-Power with Android 9 (Pie), my questions are:
1. Which of these two should I install first on android without PC? Magisk or TWRP? Seem to get conflicting instruction from those tutorials on Youtube.
2. After downloaded "TWRP Official app" from Google Playstore, chose my phone from the list and downloaded the version for my phone. It said downloaded successful, but I can't flash TWRP, can't open it in recovery mode (hardreset), it wouldn't do anything!
3. As for Magisk apk... one of the two files won't install, the zip files.... it said "failed"... so what do I do then?
Can anyone please help me fix all these problems? Very frustrating right now.
Click to expand...
Click to collapse
Hello, Morky.
I am afraid I don't understand what you really mean by your question above. You have not used a PC yet but tried to flash TWRP. Please give me more insight on what you are trying to do.
x.ak**** said:
Hello, Morky.
I am afraid I don't understand what you really mean by your question above. You have not used a PC yet but tried to flash TWRP. Please give me more insight on what you are trying to do.
Click to expand...
Click to collapse
Thank you, Kumar for your response. First of, I'm NOT a techie like you. I just followed these tutorials on YouTube....
With TWRP app this is what happened (or not happened):
https://www.youtube.com/watch?v=RtvI2C9VrOY
Started having problem at the 3:00 min mark here as well... even with hardreset
https://www.youtube.com/watch?v=wEHChHcpZEI
I couldn't do what this guy did at the 3:00 min mark....
With Magisk Manager app.... what happened was just like at the 3:00 min mark on this video
https://www.youtube.com/watch?v=DvlLy42UtGg
I thought explaining what'd happened by referencing what I was doing per these tutorials would better answer your questions, since I don't know how else to say it, again not a techie person.
<Morky>
You have to unlock your bootloader first. It requires that you read out a encrypted code from the phone, via the USB port using ADB/Fastboot. The code is entered into a web page at Motorola, and if your phone can be unlocked, they will send you a unlock code. Then you fastboot the unlock code. then fastboot twrp. then flash magisk.
you may consider going to the forum page for your phone, it will have all the details.
https://forum.xda-developers.com/g7-power
look under the guides section
hope that helps
Nivead said:
You have to unlock your bootloader first. It requires that you read out a encrypted code from the phone, via the USB port using ADB/Fastboot. The code is entered into a web page at Motorola, and if your phone can be unlocked, they will send you a unlock code. Then you fastboot the unlock code. then fastboot twrp. then flash magisk.
you may consider going to the forum page for your phone, it will have all the details.
https://forum.xda-developers.com/g7-power
look under the guides section
hope that helps
Click to expand...
Click to collapse
Nivead, I did unlocked the OEM before downloading that though, but still didn't work. The phone is an unlocked phone.
And, thank you for your help.
Morky001 said:
Kumar, I did unlocked the OEM before downloading that though, but still didn't work.
Click to expand...
Click to collapse
And.. thank you.
Morky001 said:
Thank you, Kumar for your response. First of, I'm NOT a techie like you. I just followed these tutorials on YouTube....
With TWRP app this is what happened (or not happened):
https://www.youtube.com/watch?v=RtvI2C9VrOY
Started having problem at the 3:00 min mark here as well... even with hardreset
https://www.youtube.com/watch?v=wEHChHcpZEI
I couldn't do what this guy did at the 3:00 min mark....
With Magisk Manager app.... what happened was just like at the 3:00 min mark on this video
https://www.youtube.com/watch?v=DvlLy42UtGg
I thought explaining what'd happened by referencing what I was doing per these tutorials would better answer your questions, since I don't know how else to say it, again not a techie person.
<Morky>
Click to expand...
Click to collapse
Hello, Morky.
I do not understand how one can flash any image directly from the device without rooting it. Now, in order to root your device you will need either TWRP or flash SUPERSU or Magisk using fastboot. If you wish to root your device and install TWRP on it, you will require access to a computer.
The phone has to be BOOTLOADER unlocked in order to install TWRP and Magisk. Turning on OEM unlock, is a step in unlocking the phone - but it does not unlock the bootloader.
When you are saying the phone is unlocked, I believe you mean the phone is unlocked so it will run on any cell phone carrier - a way the phone is sold. But its not bootloader unlocked.
Bootloader unlocked is different - Most phones are sold with the bootloader locked and because of that, you cannot modify the operating system. Unlocking the bootloader allows you to modify the the android operating system.
You will have to install Motorola USB drivers on your computer. Go to the Motorola page at: https://motorola-global-portal.custhelp.com/app/standalone/bootloader/unlock-your-device-a and read about unlocking the bootloader. You will have to create a Motorola account to get an unlock code, if the bootloader can be unlocked. The pages will also have a link to obtain the Motorola USB drivers (MotorolaDeviceManager_2.5.4.exe).
You will need to install Minimal ADB Fastboot, a terminal program that allows you to push data/commands back and forth between the computer and your phone via the USB port. https://forum.xda-developers.com/showthread.php?t=2317790 You will use the FASTBOOT command to obtain the encrypted unlock code from the phone. You will also use FASTBOOT to install the unlock code that Motorola will send you,
After the bootloader is unlocked, you will use FASTBOOT to install TWRP into your phones recovery partition. TWRP info at https://www.xda-developers.com/how-to-install-twrp/ TWRP is a backup and recovery program that is used to install programs, etc,
After you install TWRP, you can install MAGISK, which will ROOT the phone. Magisk info at https://forum.xda-developers.com/apps/magisk.
Please go to the forum I told you about and under the guides section you will find documentation that explains how to root the phone and install custom ROMs.
https://forum.xda-developers.com/g7-power A guide will give you the finer details for your phone model.
Before you do any of the above, I advise you strongly to have a backup. Using FASTBOOT there is a command called "getvar all", it will return a long printout of info and it will include a readout of the original firmware installed on the phone. You will want to know this in case you brick the phone. Having this info will allow you to obtain the original firmware and be able to restore it via FASTBOOT. Firmwares at https://mirrors.lolinet.com/firmware/moto/ .l After installing TWRP, you should backup the phone to your SD card and then move the backup to your computer for future needs.
Good luck.
Nivead said:
The phone has to be BOOTLOADER unlocked in order to install TWRP and Magisk. Turning on OEM unlock, is a step in unlocking the phone - but it does not unlock the bootloader.
When you are saying the phone is unlocked, I believe you mean the phone is unlocked so it will run on any cell phone carrier - a way the phone is sold. But its not bootloader unlocked.
Bootloader unlocked is different - Most phones are sold with the bootloader locked and because of that, you cannot modify the operating system. Unlocking the bootloader allows you to modify the the android operating system.
You will have to install Motorola USB drivers on your computer. Go to the Motorola page at: https://motorola-global-portal.custhelp.com/app/standalone/bootloader/unlock-your-device-a and read about unlocking the bootloader. You will have to create a Motorola account to get an unlock code, if the bootloader can be unlocked. The pages will also have a link to obtain the Motorola USB drivers (MotorolaDeviceManager_2.5.4.exe).
You will need to install Minimal ADB Fastboot, a terminal program that allows you to push data/commands back and forth between the computer and your phone via the USB port. https://forum.xda-developers.com/showthread.php?t=2317790 You will use the FASTBOOT command to obtain the encrypted unlock code from the phone. You will also use FASTBOOT to install the unlock code that Motorola will send you,
After the bootloader is unlocked, you will use FASTBOOT to install TWRP into your phones recovery partition. TWRP info at https://www.xda-developers.com/how-to-install-twrp/ TWRP is a backup and recovery program that is used to install programs, etc,
After you install TWRP, you can install MAGISK, which will ROOT the phone. Magisk info at https://forum.xda-developers.com/apps/magisk.
Please go to the forum I told you about and under the guides section you will find documentation that explains how to root the phone and install custom ROMs.
https://forum.xda-developers.com/g7-power A guide will give you the finer details for your phone model.
Before you do any of the above, I advise you strongly to have a backup. Using FASTBOOT there is a command called "getvar all", it will return a long printout of info and it will include a readout of the original firmware installed on the phone. You will want to know this in case you brick the phone. Having this info will allow you to obtain the original firmware and be able to restore it via FASTBOOT. Firmwares at https://mirrors.lolinet.com/firmware/moto/ .l After installing TWRP, you should backup the phone to your SD card and then move the backup to your computer for future needs.
Good luck.
Click to expand...
Click to collapse
Deae Nivead,
..Oy! That sounds painful!! Guess, I have no business be doing this lock/unlock/rooting thing, huh?! Not a techie at all, this is very foreign to me! And those guys on YouTube... they lied then, said I could do all these without PC... Yeah, right! Turned out, it wasn't as easy as they were showing on videos. (((sigh))) Would be easier if I just send my phone to you?!?!!!
Thank yoooouuu soooo much for taking the time to write/tell me all this, truly appreciate your help and replies.
<Morky>
x.ak**** said:
Hello, Morky.
I do not understand how one can flash any image directly from the device without rooting it. Now, in order to root your device you will need either TWRP or flash SUPERSU or Magisk using fastboot. If you wish to root your device and install TWRP on it, you will require access to a computer.
Click to expand...
Click to collapse
Kumar,
I guess those YouTube tutorials omitted left out a lot of steps and not as easy nor simple as they made it to be.... "without PC" as they claimed. How would someone with no background in computer programing, nor a "techie" like you here at xda... like me would know that?! If you "don't understand how....." I wouldn't understand either!! More so than you. One thing I've learnt now, all those tutorials about rooting and TWRP. on YouTube... are crap.
Hey folks,
So somehow when unlocking my bootloader with the unlock_key/code from OnePlus, I switched the ROM from the T-Mobile variant to the stock OnePlus variant. I may have corrupted/wiped one of the two slots and gotten lucky, that was months ago and I've forgotten.
Mostly I wanted to confirm an unlocked bootloader in the event there is a stable and up-to-date ROM made available on this device. It's my primary phone and I don't want to be alpha testing updates, so I'm happy with the stock OnePlus OS.
However, my device won't apply updates. I'm NOT rooted, though the bootloader is unlocked. What are my options for applying updates?
Do I need to re-enable bootloader via adb, which will likely wipe the OS and require re-configuration of all my apps and settings? If I apply root (and wipe-OS), can the root receive updates easily?
Been about two months now without the latest security patch, things could be worse but I definitely want to update!
ANy thoughts are appreciated, thanks!
lifebringer123 said:
Hey folks,
So somehow when unlocking my bootloader with the unlock_key/code from OnePlus, I switched the ROM from the T-Mobile variant to the stock OnePlus variant. I may have corrupted/wiped one of the two slots and gotten lucky, that was months ago and I've forgotten.
Mostly I wanted to confirm an unlocked bootloader in the event there is a stable and up-to-date ROM made available on this device. It's my primary phone and I don't want to be alpha testing updates, so I'm happy with the stock OnePlus OS.
However, my device won't apply updates. I'm NOT rooted, though the bootloader is unlocked. What are my options for applying updates?
Do I need to re-enable bootloader via adb, which will likely wipe the OS and require re-configuration of all my apps and settings? If I apply root (and wipe-OS), can the root receive updates easily?
Been about two months now without the latest security patch, things could be worse but I definitely want to update!
ANy thoughts are appreciated, thanks!
Click to expand...
Click to collapse
If you do a factory reset with the MSM tool you will get the T-Mobile ROM back and it will also relock the bootloader (and of course wipe all your apps and settings). You will definitely be able to get updates that way. I don't know if there is a way to get updates without wiping all of your data.
towardsdawn said:
If you do a factory reset with the MSM tool you will get the T-Mobile ROM back and it will also relock the bootloader (and of course wipe all your apps and settings). You will definitely be able to get updates that way. I don't know if there is a way to get updates without wiping all of your data.
Click to expand...
Click to collapse
OK, thank you! I will give it a try eventually...
Any recommended ROMS that are lightweight but super stable and also regularly updated? Like LineageOS (which I believe is not updated for this phone)...
nothing beats stock in stability period. yes you can update vs stock OTA on unlocked bootloader
You can also update and receive OTA while rooted with magisk, my current method is here:
1) click "try again." click "resume" which may or may not reboot the device.
2) adb reboot fastboot
3) fastboot boot previous_magiskpatched_boot.img
4) find active slot with adb shell /bin/getprop ro.boot.slot_suffix
5) dd
if=/dev/block/bootdevice/by-name/boot_a_or_b of=/sdcard/Download/boot.img to backup stock boot.img
6) direct install magisk, reboot
7) repeat step 5 to backup patched boot.img
8) adb pull sdcard/Download patched and stock.img
towardsdawn said:
You can also update and receive OTA while rooted with magisk, my current method is here:
1) click "try again." click "resume" which may or may not reboot the device.
2) adb reboot fastboot
3) fastboot boot previous_magiskpatched_boot.img
4) find active slot with adb shell /bin/getprop ro.boot.slot_suffix
5) dd
if=/dev/block/bootdevice/by-name/boot_a_or_b of=/sdcard/Download/boot.img to backup stock boot.img
6) direct install magisk, reboot
7) repeat step 5 to backup patched boot.img
8) adb pull sdcard/Download patched and stock.img
Click to expand...
Click to collapse
thanks!
Ytube21 said:
nothing beats stock in stability period. yes you can update vs stock OTA on unlocked bootloader
Click to expand...
Click to collapse
Are you saying that if I re-lock my bootloader, it will NOT wipe my OS/factory reset, and I'll be able to update the OS via OTA updates?
Remember, bootloader is unlocked but I'm on the stock ROM (not the T-Mobile ROM, though this is the physical T-Mobile variant).
lifebringer123 said:
Are you saying that if I re-lock my bootloader, it will NOT wipe my OS/factory reset, and I'll be able to update the OS via OTA updates?
Remember, bootloader is unlocked but I'm on the stock ROM (not the T-Mobile ROM, though this is the physical T-Mobile variant).
Click to expand...
Click to collapse
Hello there, lifebringer123.
I believe Ytube21 made a grammatical error in his response to you. I believe what he intended to imply was that, with an unlocked bootloader, you can install OTA updates on the stock ROM.
Because the phone will be transitioning from a non-assured software integrity state and unprotected personal data condition to a guaranteed software integrity state and protected data condition, relocking the bootloader will result in a factory reset to ensure no trace of a root related process capable of accessing /data.
Since I assume you don't have unlocked firmware, I'm guessing you don't have the "Local upgrade" option in settings (Settings -> System -> System update -> Gear settings icon in top right corner -> Local upgrade), which means you're missing out on the most direct and authentic way of installing OTA updates.
However, I have another idea in mind, which I'm not sure will work, but could if your circumstances allow it. Is it possible to install the most recent OnePlus Nord N200 OTA update after flashing TWRP?
Here's what I'm thinking:
1. Download the most appropriate TWRP image (Current most recent TWRP for OnePlus Nord N200)
2. Boot OnePlus Nord N200 into bootloader (adb reboot bootloader while the device is on, or, while the device is off, hold the volume down and power key for a while, release the power button when the OnePlus logo comes up (but keep pressing the volume down button), go appropriately through the menu (select suitable language, then choose Advanced -> Reboot to fastboot)
3. Ensure that fastboot detects your OnePlus Nord N200 (fastboot devices)
4. Momentarily boot into recovery (fastboot boot NameOfRecoveryHere.img (This will only boot the recovery, not install it)
5. Flash the desired OTA update .zip file using the recovery and reboot
Note: Your build number will be useful for me to point you in the right direction for finding the appropriate .zip for the OTA update (Step 5)
Apart from the way described above, I'm very confident you won't be able to properly apply updates without wiping your phone. I would suggest just backing up your phone (Save anything you want to preserve) to a secure location and then following the procedures mentioned by towardsdawn of utilizing MSM tools to restore the T-Mobile ROM.
If you have any questions or issues, please let me know.
Aselloph said:
Hello there, lifebringer123.
I believe Ytube21 made a grammatical error in his response to you. I believe what he intended to imply was that, with an unlocked bootloader, you can install OTA updates on the stock ROM.
Click to expand...
Click to collapse
The OS notices the OTA updates, but it cannot apply/install them no matter what I do to try.
Aselloph said:
Because the phone will be transitioning from a non-assured software integrity state and unprotected personal data condition to a guaranteed software integrity state and protected data condition, relocking the bootloader will result in a factory reset to ensure no trace of a root related process capable of accessing /data.
Click to expand...
Click to collapse
Makes sense; thanks.
Aselloph said:
Since I assume you don't have unlocked firmware, I'm guessing you don't have the "Local upgrade" option in settings (Settings -> System -> System update -> Gear settings icon in top right corner -> Local upgrade), which means you're missing out on the most direct and authentic way of installing OTA updates.
Click to expand...
Click to collapse
That is correct; I don't have that option. I also no longer have the "T-Mobile" Splash sceen on startup, my assumption since doing this earlier this year was that I may have wiped the t-mobile branded ROM variant, and the phone reverted to the "slot B" stock variant. But I could be wrong. In any case...
Aselloph said:
However, I have another idea in mind, which I'm not sure will work, but could if your circumstances allow it. Is it possible to install the most recent OnePlus Nord N200 OTA update after flashing TWRP?
Here's what I'm thinking:
1. Download the most appropriate TWRP image (Current most recent TWRP for OnePlus Nord N200)
2. Boot OnePlus Nord N200 into bootloader (adb reboot bootloader while the device is on, or, while the device is off, hold the volume down and power key for a while, release the power button when the OnePlus logo comes up (but keep pressing the volume down button), go appropriately through the menu (select suitable language, then choose Advanced -> Reboot to fastboot)
3. Ensure that fastboot detects your OnePlus Nord N200 (fastboot devices)
4. Momentarily boot into recovery (fastboot boot NameOfRecoveryHere.img (This will only boot the recovery, not install it)
5. Flash the desired OTA update .zip file using the recovery and reboot
Note: Your build number will be useful for me to point you in the right direction for finding the appropriate .zip for the OTA update (Step 5)
Apart from the way described above, I'm very confident you won't be able to properly apply updates without wiping your phone. I would suggest just backing up your phone (Save anything you want to preserve) to a secure location and then following the procedures mentioned by towardsdawn of utilizing MSM tools to restore the T-Mobile ROM.
If you have any questions or issues, please let me know.
Click to expand...
Click to collapse
Model DE2118
Build 11.0.1.9.DE18CB
ONE PLUS Nord N200 5G
(dre8t, but unlocked bootloader via unlock_code.bin)
I would give that a whirl if you could point me to the current OTA update .zip package. However, I bookmarked that TWRP thread months ago, but it still hasn't been updated, and I never did get it working correctly. But I'll try it. If it works and the manual OTA update .zip is only monthly/quarterly, the inconvenience is not severe. Still, I'm not using root or any custom ROM at the moment, so I should really go back to a locked bootloader so I can receive OTA updates, and suck up the loss of a few hours of restoring settings/apps...
Again (for all on thread), if there is a solid Custom ROM which regularly gets security updates, please point me to that thread/ROM! The
Thank you so much for your time!
Successful conversion of N200 5G from T-Mo to OEM without MSM tool! (Credit to Summersofar)
Hey there. i'm a new XDA Member myself. i've been mostly stalking these forums for the N200 Ever since people started the root phase and twrp projects for codename HOLI. but i'm here to convert @summersofar's guide in order to make it more...
forum.xda-developers.com
Try re-doing it. First, use MSM tool to return to Tmo, then unlock the bootloader again, then follow that guide.
It should completely fix your broken slots. And yes, my phone is rebranded, and it can apply updates perfectly.
I'm even rooted.
justauserthatusesaphone said:
Successful conversion of N200 5G from T-Mo to OEM without MSM tool! (Credit to Summersofar)
Hey there. i'm a new XDA Member myself. i've been mostly stalking these forums for the N200 Ever since people started the root phase and twrp projects for codename HOLI. but i'm here to convert @summersofar's guide in order to make it more...
forum.xda-developers.com
Try re-doing it. First, use MSM tool to return to Tmo, then unlock the bootloader again, then follow that guide.
It should completely fix your broken slots. And yes, my phone is rebranded, and it can apply updates perfectly.
I'm even rooted.
Click to expand...
Click to collapse
Thanks! When OTA updates end for our OS, in 1-2 years, what will you do? Switch phones, or do you think you have a custom ROM/OS that sounds stable enough?
I'll try the MSM tool, debate rooted or not, then report back...
Thanks again all!
lifebringer123 said:
Thanks! When OTA updates end for our OS, in 1-2 years, what will you do? Switch phones, or do you think you have a custom ROM/OS that sounds stable enough?
I'll try the MSM tool, debate rooted or not, then report back...
Thanks again all!
Click to expand...
Click to collapse
you're welcome, sorry for being late lol
after 2-3 years, ill probably keep this phone and install lineageos or pixel experience (that is, if it gets support)
although by that time, the trade in value is probably 2 dollars so I'll use it if i ever get into android development.
Any word on custom ROMs for this like Lineage OS or Pixel Experience?
**Edit: Be sure to read comments at the end of this post******
I've already posted this a few times but I figured I would try to save some people time who want/need to root from any security patch. This is a copy and paste from an answer I gave in another thread but it's a basic how to.
Install DSU sideloader app from playstore to boot a prerooted GSI then use Partitions Backup and Restore app from playstore to save copies on your device. Install magisk app and patch the extracted boot.img and then transfer backups along with the patched boot image to your PC for safekeeping and flash the patched boot.img in fastboot. You can rename any .bin files to .img to flash them if they get extracted as a .bin file. Check your settings in the partitions Backup and Restore app before starting the backup process. You can choose to save them in an easy to find directory and for me it was better to choose to save them RAW/uncompressed then just compress them all into a single archive rather than having a hundred separate archives for each individual partition because it makes it easier if you have to reflash things if you need to recover. You may want to disable battery optimization for the app because it takes a while to extract all the images doing a full backup but its well worth the wait time if it saves you from a brick later on.
I wish I had time to elaborate but hopefully someone else can take the time to elaborate and add to this for anyone needing step by step. I'm surprised nobody has done this already.
Credits to AndyYan for giving advice on the root method. I stole this from him and just made a post with a title that makes it easier to find since so many are still asking how to go about rooting their devices.
*****REQUEST TO COMMUNITY********
There are many who are already on August Security patch and i dont have time to update and post the newest images. So if you are on august patch and pull backups I ask that someone please be so kind as to upload a copy of your backup to Google Drive or a filehosting server of choice and post a new thread so that others can unbrick their devices.
*Please ***DO NOT include**** the following partitions*:
DEVINFO
DINFO
FRP
KEYMASTER_A
KEYMASTER_B
KEYSTORE
LOGDUMP
***MDM1M9KEFS1
***MDM1M9KEFS2
***MDM1M9KEFS3
***MDM1M9KEFS4
MODEMDUMP
OPLUS_SEC_A
OPLUS_SEC_B
RAWDUMP
SECDATA
STORSEC
USERDATA
VM-KEYSTORE
*** These partitions may/contain YOUR personal device info, DO NOT make these public***
You can make a new Google account for the sole purpose of uploading these for the community so as not to fill your own GDrive. Be sure to change permissions for the images to share with anyone who has the link. This would be very much appreciated by many.
*****Update 09/18/2022*****
Thanks to ctschrodinger88 & dmtec for posting more detailed instructions!!! you can find ctschrodinger88's instructions below, scroll down to the 5th post.
dmtec also posted instructions in another thread linked here: https://forum.xda-developers.com/t/august-boot-img.4491831/post-87426877
we are still in need of august modems if anyone cares to upload them to their drive and link them or any other filehosting service.
can you suggest me a pre rooted gsi rom please?
thanks
fictisio said:
can you suggest me a pre rooted gsi rom please?
thanks
Click to expand...
Click to collapse
i used crdroid but its buggy, launcher crashes but its useable, atleast to get this done and then be sure to discard it in the DSU sideloader notification when you reboot so the inactive slot is empty, it will make for easier updates/mods later
has anyone had luck flashing the file in this article? https://www.getdroidtips.com/oneplus-nord-2t-5g-firmware-flash-file-2/#google_vignette
I used the info provided and referenced here as a guide and some external pieces and have things working.
I'll caveat the following, I don't remember the current firmware version I started with, but I'll try to remember to update.
I have the Nord N20 5g, but not the T-mo branded one, though in looking at this, the concepts should be the same.
Base assumptions:
- If you haven't done these beforehand, stop and take care of it. Research if you need, but please DO NOT just keep going or copy, paste, and run, without understanding to some extent what you're doing. If you just run commands it can be much harder to fix later.
a. Your phones bootloader is unlocked. (If you haven't already done it, when you do, your data will be gone, so if you care, back it up NOW)
b. You have access to an Android terminal of some sort (adb or on-device terminal) and you know how to use it. Unless you absolutely can't use a computer for some reason, I would use adb, it makes data backup easier (IMO).
c. You have somewhere to store your backed up partitions (THIS IS IMPORTANT)
Step 0: Download a pre-rooted Generic System Image (GSI) to use. Put it in a good working directory. This page links to several. https://github.com/phhusson/treble_experimentations/wiki/Generic-System-Image-(GSI)-list
I used the LineageOS image by @AndyYan
If you are wondering about the various file endings this is the basic version
Code:
<ARCH>_xyZ
<ARCH> can either be arm, a64 (arm32_binder64) or arm64
x can either be a or b
y can either be v, o, g or f
Z can be N or S
b = a/b
a = a-only
g = gapps
o = gapps-go
v = vanilla (no gapps included)
f = floss (free & open source apps instead gapps)
N = no superuser
S = superuser included
From: https://forum.xda-developers.com/t/teclast-t30-t1px-suitable-gsi-roms.4211427/
Step 1: Enable the Dynamic System Update (DSU) feature flag, you can follow the exact steps for this in this section https://developer.android.com/topic/dsu#feature-flag
If you are unsure, just run the `adb shell` command.
Step 2:
If the image you downloaded needs to be in ".gz" format. Some of the tools will handle alternate types, but that's because it rebundles it at ".gz", you can save some effort doing it yourself.
Code:
gzip -c [IMG_NAME]..img> [IMG_NAME].gz
Step 3: Push the image to the device
`adb push [IMG_NAME].gz /storage/emulated/0/`
This is where I switched from ADB to on-the-device.
Step 4: Download the DSU Sideloader: https://github.com/VegaBobo/DSU-Sideloader
You can do this with adb but I wasn't able to get it to run, so I went with the DSU Sideloader app above which made it much simpler.
Step 5: Run DSU Sideloader. You can follow the instruction there in the README. You will need to run a command that the app provides, either via adb or an emulator. Then you will reboot via the notification.
Step 6: [Once you reboot] Enable Developer tools in phone settings.
Step 7: BACKUP, BACKUP, BACKUP (Please do this now. It will help make life much, much better if you ever have an issue and need to reset.)
This was my process:
Bash:
adb shell
su
mkdir /sdcard/partitions
cd /dev/block/by-name/
for x in *; do dd if=/dev/block/by-name/$x of=/sdcard/partitions/$x ; done
# Note the collective size will be greater than the default space on the GSI boot, so you will want to separate things
# Back on local machine
mkdir [working_dir]
cd [working_dir]
adb pull /sdcard/partitions
# Your files from the adb command should populate the folder
mv [working_dir]/partitions/* [working_dir]/
# On device
rm /sdcard/partitions/*
# repeat the commands above as often as needed.
I don't know for sure all the files you will want to backup, but I pulled everything just to be safe. Keep them safe, because it is your safety net if you fall.
Step 8: Get boot_a or boot_b back on the device along with Magisk.apk (Please only download from here: https://github.com/topjohnwu/Magisk/releases)
Step 9: Install Magisk.apk (you can do this via
Code:
adb install ./magisk.apk
)
Step 10: Launch Magisk and install it to the book image stored on your sdcard.
Step 11: Pull the patched image to your local machine.
Code:
adb pull /sdcard/Download/magisk_patched-[stuff].img
Step 12: Boot phone to fastboot
Code:
adb reboot bootloader
Step 13: This is where there is an ideal and a real.
Ideal command
Code:
fastboot boot magisk_patched.img
where fastboot transfers the files and things just work, and if you reboot the system the regular boot.img is used. I haven't been able to get that to with this device.
I instead just ran
Code:
fastboot flash boot magisk_patched.img
which replaced the existing boot image, which is good, if it works, but if it doesn't, this is why you have backups!!!! Reboot the phone.
Step 14: When you boot, finish installing Magisk and you'll be ready to go.
If I remember other steps I'll add, or if you have questions I will try to help answer.
I just got a MetroPCS nord n20 (gn2200) and will try to root in the next couple days.
ScarletWizard said:
n20
Click to expand...
Click to collapse
Have they removed the unlock portal?
Damn, it's been a long time. Glad to be back.
ScarletWizard said:
No. My serial is 7 digits
Click to expand...
Click to collapse
seems to be a common defect.... if ur device is paid off oneplus can generate you a token but it takes weeks of back-and-forth with support to get it escalated...tmobile may or may not allow you to do that on a device that isnt paid off but i wouldnt even ask tmobile about it if your not paid off already, will only make it harder for those who are trying to unlock theirs if it IS the case that tmobile doesnt want you to unlock it until youve paid the device off in full....oneplus will probably uphold tmobiles decision if your device isnt paid off. for now, we are able to unlock tmobile devices through the portal regardless of the financial status of the device. though you will still be SIM locked unless tmobile unlocks that for you. and their definitely NOT gonna do THAT til it gets paid off.
U.S. carriers dont like customers having unlocked devices and is against most user-agreement policies and can get your service terminated leaving you owing for a device you cant use and for the price of the contract you were on for service
your device is a CPH2459 and not a GN2200?
fictisio said:
can you suggest me a pre rooted gsi rom please?
thanks
Click to expand...
Click to collapse
Andy Yan's Lineage18 or 19..
DrScrad said:
Andy Yan's Lineage18 or 19..
Click to expand...
Click to collapse
pixel experience, crdroid... havent gotten kaleidoscope to work yet. Have heard that someone got aosp a13 going.... There are so many and so long as u use a matching security patch ur good. might work with a newer patch but of the ones ive tried i got thw matching patches to work. If you find one thats on a newer patch in the gsi page you should be able to follow the link and find an older release to match the patch ur on. If ur on may patch try to find a may patch just to make it pess likepy that there will be priblems. If on july or august, likewise find july or august sec patch release. newer patched systems MIGHT work with ur older patched bootloader and other partitions(modems etc...) but def would not advise just straight flashing mismatching security patches... Best to sideload first and see if u can get it working first. Its not very simple to dual boot these devices but i think someone did some work and posted a work around for doing that on a/b devices somewhere on xda......
Am willing to share my stock image with anyone willing to help. I am on the September security update on a OnePlus Nord N20 5G unlocked (Non-Carrier). I am running version 11 and android security update 2022-09-05.
I am having real issues getting LineageOS through DSU. It fails immediately on start every time. Bootloader is unlocked, it even shows through fastboot (Secure boot = on though), flag is set per instructions, and I am trying to install lineage-19.1-20221011-UNOFFICIAL-arm64_bvS.gz . I tried two different versions of the DSU app but nada.
oromis995 said:
Am willing to share my stock image with anyone willing to help. I am on the September security update on a OnePlus Nord N20 5G unlocked (Non-Carrier). I am running version 11 and android security update 2022-09-05.
I am having real issues getting LineageOS through DSU. It fails immediately on start every time. Bootloader is unlocked, it even shows through fastboot (Secure boot = on though), flag is set per instructions, and I am trying to install lineage-19.1-20221011-UNOFFICIAL-arm64_bvS.gz . I tried two different versions of the DSU app but nada.
Click to expand...
Click to collapse
make sure u r using a lineage version with the same security patch as your current OS if your on September u need a GSI on september. i personally gave up on lineage after trying a couple but was successful with a few others while dsu sideloader still worked for me, im not sure what i did to break it on my devices but i havent been able to get it to work on either device in a while.
i have yet to try the october firmware but it should be easy to downgrade and root if you think its the new updates. although make sure ur disabling verity. u might wanna disable the checks on vbmeta_boot too... i usually just disable it on all 3 vbmeta's to be safe.... i have a full july dump and someone else has posted the august dump on TG but that doesnt help in your case since you have the CPH2459 and we are on GN2200's nobody has been able to successfully crossflash them yet and im not sure if it will be possible or not but everyone that has tried it has bricked their devices so far. most have gotten them running again but have lost fingerprint
ScarletWizard said:
im on gn2200
Click to expand...
Click to collapse
Ok my last upload didn't upload correctly for some reason. I will re upload tomorrow I think..... I need to figure out exactly which partitions are device-specific.... I know which partitions get updated in the incrementals so if all of them don't get flashed then everything won't match but I have a feeling that the incrementals update a device-specific partition or two and if so then u will lose fingerprint at minimum...... I think I should just pull full backup of all partitions and then go for it. Worst case so long as u do everything right. U just don't boot and have to reflash the stock boot image... Be sure to flash the stock image to both slots just in case and then switch back to ur active slot and flash the patched boot image. I mean if it was me I would b comfortable doing it but that's completely ur call, I don't wanna encourage anything because there ALWAYS a risk something could go wrong. Power outage or something and it's screwed up but any time u r flashing u will always be taking a risk. Though I think the risk is minimal so long as u do everything right and there's not much to the simple root process, patch the boot image and flash, if it doesn't work then reflash the stock one. If it DIES work out for u we would b grateful for the October firmware if u wanna share it, we didn't get October yet.
ScarletWizard said:
If it dies. Lol scary.
I'm in the process of doing the partition thing
Click to expand...
Click to collapse
If it DOES.. Sry
ScarletWizard said:
who is the ADMIN of this n20 thread?
Click to expand...
Click to collapse
Just look.for the moderator edits lol
PsYk0n4uT said:
seems to be a common defect.... if ur device is paid off oneplus can generate you a token but it takes weeks of back-and-forth with support to get it escalated...tmobile may or may not allow you to do that on a device that isnt paid off but i wouldnt even ask tmobile about it if your not paid off already, will only make it harder for those who are trying to unlock theirs if it IS the case that tmobile doesnt want you to unlock it until youve paid the device off in full....oneplus will probably uphold tmobiles decision if your device isnt paid off. for now, we are able to unlock tmobile devices through the portal regardless of the financial status of the device. though you will still be SIM locked unless tmobile unlocks that for you. and their definitely NOT gonna do THAT til it gets paid off.
U.S. carriers dont like customers having unlocked devices and is against most user-agreement policies and can get your service terminated leaving you owing for a device you cant use and for the price of the contract you were on for service
Click to expand...
Click to collapse
One small problem, although Metron PCS uses T-Mobile towers, they are their own entity and T-Mobile does not have their Bootloader codes. Only OnePlus and Metro PCS have the Metro PCS unlock.bin file. That's what I came here was to try and find a dedicated metro bootloader unlock web page. Like the T-Mobile dedicated page. There is not one so it's going too take several calls over several weeks unless some one here knows a different way or a link to a metro PCS bootloader unlock page? Anyone chime in on this and save all of us that are running in circles back down the straight path to an unlocked bootloader..
jayram1408 said:
One small problem, although Metron PCS uses T-Mobile towers, they are their own entity and T-Mobile does not have their Bootloader codes. Only OnePlus and Metro PCS have the Metro PCS unlock.bin file. That's what I came here was to try and find a dedicated metro bootloader unlock web page. Like the T-Mobile dedicated page. There is not one so it's going too take several calls over several weeks unless some one here knows a different way or a link to a metro PCS bootloader unlock page? Anyone chime in on this and save all of us that are running in circles back down the straight path to an unlocked bootloader..
Click to expand...
Click to collapse
I'm about to file a FCC complaint to get mine then.