Related
Want to buy this phone. Need it rooted to do a couple things. Has anybody gotten TWRP and root on it yet?
You can root it by first unlock the bootloader then install magisk via patch boot image method.
How should I get the boot image to actually use that method?
You can download the firmware here: https://mirrors.lolinet.com/firmware/moto/foles/official/RETUS/
Inside zips, find boot.img
Does anyone know anything about custom recovery TWRP yet that's what I'm looking for
there is no custom recovery
ahalol said:
You can root it by first unlock the bootloader then install magisk via patch boot image method.
Click to expand...
Click to collapse
What is the way to unlock the bootloader? I don't believe Motorola officially released it for the phone yet. Have you rooted this phone?
Thereplierbro said:
What is the way to unlock the bootloader? I don't believe Motorola officially released it for the phone yet. Have you rooted this phone?
Click to expand...
Click to collapse
Official unlock from Motorola is available, as long as you aren't referring to the Verizon version.
wraith1932 said:
Official unlock from Motorola is available, as long as you aren't referring to the Verizon version.
Click to expand...
Click to collapse
Does the Verizon one have a greyed out "OEM Bootloader unlock"
Because I bought one off offer up that had the button available but it was purchased from Verizon
Also I asked Motorola for the unlock website an they said they haven't released it yet for Moto z4
Can't say for sure myself, I got the carrier unlocked version. But I believe that button in the options is there no matter what, I remember it on my original Z Force Droid (Verizon only version, no bootloader unlock, official or not).
I would bet that, if it was bought at Verizon, then there won't be a bootloader unlock available - ever.
Dunno what that last part is supposed to mean... Never saw a device-specific Moto Bootloader Unlock page, going all the way back to the original Moto X. There's the page explaining the unlock process, a disclaimer ("anything you do from here isn't our fault, or responsibility to fix" basically), and a link to the next step (with a "log in to Moto" in between). After login, it brings you to instructions to get a code to put in, and the button to check if the device is eligible for unlocking the bootloader.
I would include a link to the first page if I could. Almost there, just one more post...
wraith1932 said:
Official unlock from Motorola is available, as long as you aren't referring to the Verizon version.
Click to expand...
Click to collapse
wraith1932 said:
Can't say for sure myself, I got the carrier unlocked version. But I believe that button in the options is there no matter what, I remember it on my original Z Force Droid (Verizon only version, no bootloader unlock, official or not).
I would bet that, if it was bought at Verizon, then there won't be a bootloader unlock available - ever.
Dunno what that last part is supposed to mean... Never saw a device-specific Moto Bootloader Unlock page, going all the way back to the original Moto X. There's the page explaining the unlock process, a disclaimer ("anything you do from here isn't our fault, or responsibility to fix" basically), and a link to the next step (with a "log in to Moto" in between). After login, it brings you to instructions to get a code to put in, and the button to check if the device is eligible for unlocking the bootloader.
I would include a link to the first page if I could. Almost there, just one more post...
Click to expand...
Click to collapse
All other phones, if the button is not greyed out and you can press the option (and it asked for your password) then it's unlockable. I know because I got a few freaking pixel phones with non usable Bootloader. Wasted about $1,000 looking for a cellphone to use with Sprint that I can root. Every one of them is Verizon.
https://support.motorola.com/us/en/solution/ms87215
DM Verity disabled too?
What about DM verity? Has anyone figured out how to disable that? I need to add a couple of lines to the build.prop file, but can't seem to change the write permissions even with root; any edits made directly on the phone using an editor with root permissions, don't persist after a system reboot. Edits made to the build.prop file externally, and pushed pre-boot via ADB, result in boot loop due to DM verity failing.
(For clarity, I do not have this phone, yet, I have a Z2 Play, but I faced these challenges with that device too)
Jade Eyed Wolf said:
What about DM verity? Has anyone figured out how to disable that? I need to add a couple of lines to the build.prop file, but can't seem to change the write permissions even with root; any edits made directly on the phone using an editor with root permissions, don't persist after a system reboot. Edits made to the build.prop file externally, and pushed pre-boot via ADB, result in boot loop due to DM verity failing.
(For clarity, I do not have this phone, yet, I have a Z2 Play, but I faced these challenges with that device too)
Click to expand...
Click to collapse
I hope a real dev jumps on board to this cellphone. It's pretty decent for what it is honestly
Thereplierbro said:
I hope a real dev jumps on board to this cellphone. It's pretty decent for what it is honestly
Click to expand...
Click to collapse
One of my main reasons for waiting to get one
Jade Eyed Wolf said:
One of my main reasons for waiting to get one
Click to expand...
Click to collapse
It's basically useless until then
Could I get a little guidance on how to patch and flash the boot image? I have ADB/Fastboot setup as well as the XT1980-4 firmware downloaded.
Do I just place the boot.img file on my phone, patch it in Magisk Manager, and flash with fastboot? Anything I need to be careful of?
Also, how should I go about backups here? I've only messed with this stuff when I had a Galaxy S4, everything was super simple with easy bootloader unlock and custom recovery.
battleof3 said:
Could I get a little guidance on how to patch and flash the boot image? I have ADB/Fastboot setup as well as the XT1980-4 firmware downloaded.
Do I just place the boot.img file on my phone, patch it in Magisk Manager, and flash with fastboot? Anything I need to be careful of?
Also, how should I go about backups here? I've only messed with this stuff when I had a Galaxy S4, everything was super simple with easy bootloader unlock and custom recovery.
Click to expand...
Click to collapse
What you said was correct. That's how you patch and flash. Nothing particular to be careful. The only thing would be in order to receive future OTA, you should not modify you /system and /vendor partition during your use of the phone.
ahalol said:
What you said was correct. That's how you patch and flash. Nothing particular to be careful. The only thing would be in order to receive future OTA, you should not modify you /system and /vendor partition during your use of the phone.
Click to expand...
Click to collapse
Dug a little deeper and bootloader is locked tight, no flashing for me. Returning and buying a secondhand LG V30 for cheap. It's unfortunate that carriers love their walled gardens.
See, this is why I was asking about DM Verity. You need to disable that first before flashing anything via ADB/Fastboot.
With DM Verity on, at system startup, the device generates a hash of the /system and /root directories. If the hash does not match the one from the factory, due to changes pushed via ADB or Fastboot or patching other system files with something different, the system reboots, again and again.
I had this same issue with my Z2 Play, which is why I brought it up here.
Rooting these devices is useless, unless you also disable DM Verity.
I tried to follow this method and ended up flashing the wrong boot image (I did go to the right software variant but it was outdated) so i had to go through and try all the images they had and none of them worked so i had to look elsewhere.
After some digging i found a VERY handy tool made by lenovo themselves that lets you update and recover the firmware.
If you use the rescue option and enter your phones info (it seems to verify your phones info so you can only download for devices you have) and it'll download the latest zip for you so you can get the boot image.
Here's the link to the smart assistant
TL;DR Open smart assistant, click flash, click "Go rescue", Click "Moto Phone", enter your phone's info (make sure your phone is connected in fastboot mode), click the download icon next to the file name.
Make sure you DO NOT click the rescue button when the download is finished as that will factory reset your phone, just copy the zip or boot image and close it
I posted a thread on this, commented on a couple other threads, posted on Reddit, and I simply cannot get straight answers across the board. All the feedback I'm getting is different. I am willing to PayPal friends and family $5 to the first person that can answer my questions with links to sources just so I can ensure the information I'm getting is correct. I haven't rooted a phone since my 1st Gen Moto X so I'm out of the loop, but have a understanding of everything.
I have a GM1915 OnePlus 7 Pro that is T-Mobile SIM unlocked. I followed the tutorials HERE and HERE to flash the global firmware and all went well. Only issue I had was my SIM was being detected but no service, so I did an OTA update to 10.0.3 and my service is working fine now. Here are where my questions begin:
1. Now that I have installed the international firmware I don't need to get a bootloader unlock from T-Mobile/OnePlus, correct? I can just use the OEM unlock option and unlock via fastboot?
I have had people tell me I am good to enable OEM unlocking and use fastboot oem unlock, others have told me I still need to request a unlock, others tell me to downgrade to SP3. I just need a straightforward answer: Can I use OEM unlocking or do I need to request an unlock from OnePlus?
2. I know bootloader/root can sometimes cause certain applications to not function, but I've also read Magisk has a setting to correct this. I'm mainly just concerned with Google Pay, is there a method for it to still function with root?
Again, I've had some people tell me I can't use Google Pay, Netflix, or anything like that at all, others tell me Magisk Hide and SafetyNet will fix this issue. I also had an individual state "However, recent changes coming might thwart this.". Again, can I use Google Pay or can't I?
3. Part of me would actually like to use the phone stock for a week or so to see if I even feel like I need root access. I am currently on OS 10.0.3, if I update to the newest OS (looks like 10.3.1 is the newest) will I still be able to root with Magisk and flash TWRP? I would assume yes since you can do an OTA update and keep Magisk, but I just wanted to verify.
So if I update to 10.3.1 can I still follow the same tutorial listed under question 1 and it will work? Doesn't the most recent version of TWRP/Magisk support 10.3.1? Or will I need to use MSM and go back to 9.5.X (can't remember the exact version, but it's the OS it puts you on when you follow the steps for international firmware flashing)? Can I even go back to 9.5.X after updating to 10.3.1? I see release notes for TWRP that state is now have Android Q support but I just want to ensure it's compatibile with 10.3.1 or whatever the newest OS is.
Code:
mauronofrio matarrese
2019-08-18T15:04:57Z
Upload New Blobs for Android Q
I know regardless my phone is going to get wiped, I just want to be prepared on what I need to do if I decide to root.
I don't need links to tutorials, there are plenty of them and I understand how flashing TWRP and Magisk works, I just need my above questions answered with sources. I have searched around for a couple days and cannot get straight forward answers for any of these. First to answer every question with sources I'll send $5 PayPal.
ThisIsCheez said:
I posted a thread on this, commented on a couple other threads, posted on Reddit, and I simply cannot get straight answers across the board. All the feedback I'm getting is different. I am willing to PayPal friends and family $5 to the first person that can answer my questions with links to sources just so I can ensure the information I'm getting is correct. I haven't rooted a phone since my 1st Gen Moto X so I'm out of the loop, but have a understanding of everything.
I have a GM1915 OnePlus 7 Pro that is T-Mobile SIM unlocked. I followed the tutorials HERE and HERE to flash the global firmware and all went well. Only issue I had was my SIM was being detected but no service, so I did an OTA update to 10.0.3 and my service is working fine now. Here are where my questions begin:
1. Now that I have installed the international firmware I don't need to get a bootloader unlock from T-Mobile/OnePlus, correct? I can just use the OEM unlock option and unlock via fastboot?
I have had people tell me I am good to enable OEM unlocking and use fastboot oem unlock, others have told me I still need to request a unlock, others tell me to downgrade to SP3. I just need a straightforward answer: Can I use OEM unlocking or do I need to request an unlock from OnePlus?
2. I know bootloader/root can sometimes cause certain applications to not function, but I've also read Magisk has a setting to correct this. I'm mainly just concerned with Google Pay, is there a method for it to still function with root?
Again, I've had some people tell me I can't use Google Pay, Netflix, or anything like that at all, others tell me Magisk Hide and SafetyNet will fix this issue. I also had an individual state "However, recent changes coming might thwart this.". Again, can I use Google Pay or can't I?
3. Part of me would actually like to use the phone stock for a week or so to see if I even feel like I need root access. I am currently on OS 10.0.3, if I update to the newest OS (looks like 10.3.1 is the newest) will I still be able to root with Magisk and flash TWRP? I would assume yes since you can do an OTA update and keep Magisk, but I just wanted to verify.
So if I update to 10.3.1 can I still follow the same tutorial listed under question 1 and it will work? Doesn't the most recent version of TWRP/Magisk support 10.3.1? Or will I need to use MSM and go back to 9.5.X (can't remember the exact version, but it's the OS it puts you on when you follow the steps for international firmware flashing)? Can I even go back to 9.5.X after updating to 10.3.1? I see release notes for TWRP that state is now have Android Q support but I just want to ensure it's compatibile with 10.3.1 or whatever the newest OS is.
Code:
mauronofrio matarrese
2019-08-18T15:04:57Z
Upload New Blobs for Android Q
I know regardless my phone is going to get wiped, I just want to be prepared on what I need to do if I decide to root.
I don't need links to tutorials, there are plenty of them and I understand how flashing TWRP and Magisk works, I just need my above questions answered with sources. I have searched around for a couple days and cannot get straight forward answers for any of these. First to answer every question with sources I'll send $5 PayPal.
Click to expand...
Click to collapse
Firstly I can't give you a reputable source, and I don't want any money. I actually recently bought a Renewed Oneplus 7 Pro from amazon when it was 420, its the Black 8GB 256GB T-Mobile GM1915 model. So here is what I found out , and currently running Ill post some pics to show you
1. If you followed the guides above exactly and everything went smoothly your pefectly fine to use OEM Unlock, it basically installs a version of the firmware that doesn't check for a boot loader unlock token. I had originally requested one as well than found this nifty guide and it worked amazingly.
2. Yes it will work perfectly fine with Magisk, just use the Hide Magisk , it will resintall under a new name. Than you can even go further and use magisk hide to hide it from each app independently. As for google pay I have mine setup and it worked fine. I haven't actually been able to go into store and use it as we are very closed off in home now, but It allowed me to add my card fine, verify with my bank and all that good stuff. As for netflix yes it will work but since you unlocked bootloader you lose the Widevine DRM L1 certification and thus can't watch in HDR anymore. It still works fine though and honestly looks alright to me.
3. I had updated my T-Mobile OS all the way to latest version forget what it was at the moment, and than I did the tutorial to unlock the bootloader and flash twrp/magisk/rom. It worked out perfectly fine so you should be fine as well. What I would do is use the tutorial above unlock bootloader, because that version of the OS doesn't check for unlock token, than flash a stock Global rom 10.3.2 is avaliable now. and enjoy it for awhile and when your ready install a custom rom and magisk.
I'll add some pictures of things you asked about. Sadly I can't show my model number in system due to rom but i showed it connected to my pc.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Kireyev said:
Firstly I can't give you a reputable source, and I don't want any money. I actually recently bought a Renewed Oneplus 7 Pro from amazon when it was 420, its the Black 8GB 256GB T-Mobile GM1915 model. So here is what I found out , and currently running Ill post some pics to show you.
[/HIDE]
Click to expand...
Click to collapse
This was more than helpful, and a first hand account. I know you said that you didn't want any money but I am prepared to send it, if you don't want it I will donate to a charity of your choice.
3. I had updated my T-Mobile OS all the way to latest version forget what it was at the moment
Click to expand...
Click to collapse
When you say this, did you update your firmware OTA on the T-Mobile firmware, or the Global/International firmware using OTA? I don't want to skip any incremental updates and cause issues so I might update using OTA to the newest it provides than use Oxygen Updater to get to 10.3.2. As long as I can be on the newest firmware and still unlock my bootloader and flash TWRP I'm fine. I mainly got this phone because it ticks every feature box I want and it can be rooted, but I'm up for using it stock for a while to see if I even want root.
Edit: I reread you post and think I looked over something about unlocking the bootloader. So the specific version of the firmware you flash to to swap to the international firmware doesn't require an unlock token, so if I wanted to use the OEM unlock I'd need to be back on that version, but if I wanted to unlock after I update to 10.3.2 I'd need to request a token. Am I understanding that correctly?
ThisIsCheez said:
This was more than helpful, and a first hand account. I know you said that you didn't want any money but I am prepared to send it, if you don't want it I will donate to a charity of your choice.
When you say this, did you update your firmware OTA on the T-Mobile firmware, or the Global/International firmware using OTA? I don't want to skip any incremental updates and cause issues so I might update using OTA to the newest it provides than use Oxygen Updater to get to 10.3.2. As long as I can be on the newest firmware and still unlock my bootloader and flash TWRP I'm fine. I mainly got this phone because it ticks every feature box I want and it can be rooted, but I'm up for using it stock for a while to see if I even want root.
Click to expand...
Click to collapse
It was the T-Mobile firmware. 10.0.3 version. I had done it before I was even thinking about unlocking bootloader and flashing. Than when I saw the custom ROMS + Kernels where you can gain massive performance gains or optimize battery like mad I was sold on it. Plus the ugly t-mobile boot screens annoyed me. It is an amazing phone and prices can be had at its a steal. Also their is a TWRP that lets you dual boot and use shared data partition. So you could have one boot as a custom ROM, and another as stock and have the data shared in a common partition. Get a little of both ^_^
Like I have two profiles and one is more performance / battery Optimized
This other was more for fun on seeing how far I can push scores I am bored during this lockdown lol
Kireyev said:
It was the T-Mobile firmware. 10.0.3 version. I had done it before I was even thinking about unlocking bootloader and flashing. Than when I saw the custom ROMS + Kernels where you can gain massive performance gains or optimize battery like mad I was sold on it. Plus the ugly t-mobile boot screens annoyed me. It is an amazing phone and prices can be had at its a steal. Also their is a TWRP that lets you dual boot and use shared data partition. So you could have one boot as a custom ROM, and another as stock and have the data shared in a common partition. Get a little of both ^_^
Like I have two profiles and one is more performance / battery Optimized
This other was more for fun on seeing how far I can push scores I am bored during this lockdown lol
Click to expand...
Click to collapse
Thanks for all the replies. Would you care to answer this question below? And if you do not want the cash what charity would you like it donated to?
Edit: I reread you post and think I looked over something about unlocking the bootloader. So the specific version of the firmware you flash to to swap to the international firmware doesn't require an unlock token, so if I wanted to use the OEM unlock I'd need to be back on that version, but if I wanted to unlock after I update to 10.3.2 I'd need to request a token. Am I understanding that correctly?
ThisIsCheez said:
Thanks for all the replies. Would you care to answer this question below? And if you do not want the cash what charity would you like it donated to?
Edit: I reread you post and think I looked over something about unlocking the bootloader. So the specific version of the firmware you flash to to swap to the international firmware doesn't require an unlock token, so if I wanted to use the OEM unlock I'd need to be back on that version, but if I wanted to unlock after I update to 10.3.2 I'd need to request a token. Am I understanding that correctly?
Click to expand...
Click to collapse
You know I am honestly not sure on this part, I did the bootloader unlock right after I followed that tutorial with the MSM tool. I am pretty sure its just the t-mobile firmware that blocks you from doing OEM unlock with out token. Not the global. But one way to find out be enable OEM unlock in developer settings, and run the fastboot oem unlock cmd. See if it works. If not you have your answere and will have to go back to other version. If you want you can always relock bootloader. I would test this but as I've already unlocked , re-locking and unlocking probably not give proper answer. But if you want I can install 10.3.3 lock bootloader and try to unlock it again lol.
EDIT: a test in sues.
Kireyev said:
You know I am honestly not sure on this part, I did the bootloader unlock right after I followed that tutorial with the MSM tool. I am pretty sure its just the t-mobile firmware that blocks you from doing OEM unlock with out token. Not the global. But one way to find out be enable OEM unlock in developer settings, and run the fastboot oem unlock cmd. See if it works. If not you have your answere and will have to go back to other version. If you want you can always relock bootloader. I would test this but as I've already unlocked , re-locking and unlocking probably not give proper answer. But if you want I can install 10.3.3 lock bootloader and try to unlock it again lol.
EDIT: a test in sues.
Click to expand...
Click to collapse
So I tried fastboot oem unlock after updating to 10.3.1 and it asked me if I wanted to unlock without prompting for an unlock token. I didn't choose the option to unlock, I kept it locked, but I think if I can get that far I should be able to unlock without a token on 10.3.1
ThisIsCheez said:
So I tried fastboot oem unlock after updating to 10.3.1 and it asked me if I wanted to unlock without prompting for an unlock token. I didn't choose the option to unlock, I kept it locked, but I think if I can get that far I should be able to unlock without a token on 10.3.1
Click to expand...
Click to collapse
I can confirm now officially. After locking my bootloader, using MSM tool to go back to T-Mobile updating to 10.0.3 and trying to unlock bootloader it wouldn't work as I thought.
When using the MSM tool to go to international version and updating all the way to 10.3.2, it worked perfectly fine. So you can be on global rom and not worry about being able to unlock bootloader later due to updates Very awesome can get on global rom and not compromise bootloader so can have all security in place
Kireyev said:
I can confirm now officially. After locking my bootloader, using MSM tool to go back to T-Mobile updating to 10.0.3 and trying to unlock bootloader it wouldn't work as I thought.
When using the MSM tool to go to international version and updating all the way to 10.3.2, it worked perfectly fine. So you can be on global rom and not worry about being able to unlock bootloader later due to updates Very awesome can get on global rom and not compromise bootloader so can have all security in place
Click to expand...
Click to collapse
You are the GOAT. Not only does this help me but hopefully some other members of the community that wish to update and try stock before unlocking the bootloader.
Kireyev said:
I can confirm now officially. After locking my bootloader, using MSM tool to go back to T-Mobile updating to 10.0.3 and trying to unlock bootloader it wouldn't work as I thought.
When using the MSM tool to go to international version and updating all the way to 10.3.2, it worked perfectly fine. So you can be on global rom and not worry about being able to unlock bootloader later due to updates Very awesome can get on global rom and not compromise bootloader so can have all security in place
Click to expand...
Click to collapse
Just as verification that I wasn't using the PayPal reward as a ploy to get someone to respond and bail, Kireyev declined payment so I made a donation to ExtraLife in his name. Thanks again for your help to me and the community.
https://www.extra-life.org/index.cfm?fuseaction=donorDrive.participant&participantID=408732
Kireyev said:
I can confirm now officially. After locking my bootloader, using MSM tool to go back to T-Mobile updating to 10.0.3 and trying to unlock bootloader it wouldn't work as I thought.
When using the MSM tool to go to international version and updating all the way to 10.3.2, it worked perfectly fine. So you can be on global rom and not worry about being able to unlock bootloader later due to updates Very awesome can get on global rom and not compromise bootloader so can have all security in place
Click to expand...
Click to collapse
hey thank you both for this thread but admittedly i am a little lost and i really do not want to brick this device, ive rooted devices in the pas, some even requiring hardware modifications to do so. but i just want to make sure i do everything right
im on a sim unlocked t-mobile 10.0.3.gm31cb right now
what are the exact steps i need to follow to unlock bootloader, and get on the latest rom ?
Outta said:
hey thank you both for this thread but admittedly i am a little lost and i really do not want to brick this device, ive rooted devices in the pas, some even requiring hardware modifications to do so. but i just want to make sure i do everything right
im on a sim unlock
Click to expand...
Click to collapse
If you follow the main guide on xda exactly you're going be fine. Once on global your essentially done because than you can flash a twrp through fastboot and install any rom, kernel you want. As well as magisk. The most important part is that msm guide. Now if you want to be more official get an unlock token and do it the regular way through fastboot with the unlock token. It took about a week in a half to get mine. But the msm guide works perfectly. Also I've gotten my device stuck in multiple fastboot loops and stuff their is always a way back.
Kireyev said:
If you follow the main guide on xda exactly you're going be fine. Once on global your essentially done because than you can flash a twrp through fastboot and install any rom, kernel you want. As well as magisk. The most important part is that msm guide. Now if you want to be more official get an unlock token and do it the regular way through fastboot with the unlock token. It took about a week in a half to get mine. But the msm guide works perfectly. Also I've gotten my device stuck in multiple fastboot loops and stuff their is always a way back.
Click to expand...
Click to collapse
Exactly which guide, at least 5 have been discussed lol what are the exact steps to take to go from stock be tmo to bootloader unlocked and rooted on latest stock rom.
I also don't mind sending you a monetary gift for your help. Thanks in advanced.
Outta said:
Exactly which guide, at least 5 have been discussed lol what are the exact steps to take to go from stock be tmo to bootloader unlocked and rooted on latest stock rom.
I also don't mind sending you a monetary gift for your help. Thanks in advanced.
Click to expand...
Click to collapse
This guide
https://forum.xda-developers.com/oneplus-7-pro/help/how-to-convert-tmobile-op7-to-t3935947
Once you follow this you will be off TMobile stock and on global stock. Here you can choose to unlock bootloader or not. You don't need to root and install twrp to be on global rom. Just basically do the msm guide than. Update through the oxygen updater app to latest.
Kireyev said:
This guide
https://forum.xda-developers.com/oneplus-7-pro/help/how-to-convert-tmobile-op7-to-t3935947
Once you follow this you will be off TMobile stock and on global stock. Here you can choose to unlock bootloader or not. You don't need to root and install twrp to be on global rom. Just basically do the msm guide than. Update through the oxygen updater app to latest.
Click to expand...
Click to collapse
just bricked my phone at this part:
3) Hold both volume buttons for 5 seconds then plug in the USB cable. OR In ADB type "adb reboot edl".
phone turned off and wont turn back on, any idea what tro do now?
Outta said:
just bricked my phone at this part:
3) Hold both volume buttons for 5 seconds then plug in the USB cable. OR In ADB type "adb reboot edl".
phone turned off and wont turn back on, any idea what tro do now?
Click to expand...
Click to collapse
Yep your in download mode, its not bricked no worries. just hold volume up and power button for awhile you well feel a vibrate and than it will reboot
Kireyev said:
If you follow the main guide on xda exactly you're going be fine. Once on global your essentially done because than you can flash a twrp through fastboot and install any rom, kernel you want. As well as magisk. The most important part is that msm guide. Now if you want to be more official get an unlock token and do it the regular way through fastboot with the unlock token. It took about a week in a half to get mine. But the msm guide works perfectly. Also I've gotten my device stuck in multiple fastboot loops and stuff their is always a way back.
Click to expand...
Click to collapse
Kireyev said:
Yep your in download mode, its not bricked no worries. just hold volume up and power button for awhile you well feel a vibrate and than it will reboot
Click to expand...
Click to collapse
Thanks again, saved, do you have any idea what my issue is, why isn't msm seeing my device? Adb does..
Outta said:
Thanks again, saved, do you have any idea what my issue is, why isn't msm seeing my device? Adb does..
Click to expand...
Click to collapse
strange all you really need do is hook it up to pc, enable usb debugging which u've done. type adb reboot edl, wait for it and have msm open and it should connect. My only thing to suggest would be try another cable or another port on the pc. sometimes i've also noticed fastboot can be odd for me and I have to reboot the computer for it to notice my phone . I'd suggest try those things. Did you check your system model and see if it was the 1915 model with the GM31CB?
dont know if you got it or not but heres link to the commands https://droidfeats.com/unlock-bootloader-oneplus-7-pro-t-mobile/
Howdy all,
I'll try to keep things brief but informative.
Yesterday I got the unlock bin for my T-Mobile Oneplus 7 Pro. I unlocked it, flashed LineageOS (latest 17.1), Magisk (19.04 but then updated to latest after install), DM-Verity, and TWRP (unified Q version).
I have installed Nethunter, F-Droid, and some other basic apps.
I just got a new SIM Card from T-Mobile and activated it last night, however it shows the same as the empty SIM slot (which my phone doesn't have a physical second slot) and on the lock screen at the top left rotates between saying: "No SIM card" "No SIM card - T-Mobile" "No SIM card - No service". In the phone the top right does not show any bars, x'ed out or otherwise, however one time after taking it out, googling, then putting it back in it sis appear x'ed out until reboot.
I cannot send texts as it says no preferred SIM card selected, and I cannot make calls due to a lack of service; however, I can receive texts and calls and even answer calls and speak to the calling party just fine.
I was getting nothing, then I saw where someone received a text and it fixed it for them, so I texted myself, got a backlog of texts, but nothing else came of that.
I have no idea what to do from here and only vauge idea of why it may be like this but no understanding of it.
I found this reddit post seeming to detail the issue, but I do not know if it applies to me (presumably does) and I do not understand any of the information in the post, nor do I know what to do with this information:
reddit.com/r /oneplus /comments /gb5jlk /factory_reset_no_sim_card_detected_oneplus_7_pro /
(sorry for the spaces, can't post outside links until after I've posted 10 posts)
and with that I'm all out of idea and knowledge. My background is in Offensive Security, but I know very little about SIM Cards and smart phones so all help is greatly appreciated!
Is the device sim unlocked?
wired57 said:
Is the device sim unlocked?
Click to expand...
Click to collapse
I didn't do it so I'm going to assume it is not. I've only unlocked the bootloader (obviously). How would I go about unlocking the SIM?
Also, the original carrier was T-Mobile and the SIM is also T-Mobile, I assumed this would be ok but is there an issue since I didn't unlock it yet I installed custom stuffs - or what would be causing an issue by not unlocking it? (just trying to learn more )
MagicCooki3 said:
I didn't do it so I'm going to assume it is not. I've only unlocked the bootloader (obviously). How would I go about unlocking the SIM?
Also, the original carrier was T-Mobile and the SIM is also T-Mobile, I assumed this would be ok but is there an issue since I didn't unlock it yet I installed custom stuffs - or what would be causing an issue by not unlocking it? (just trying to learn more )
Click to expand...
Click to collapse
How did you root?
Did you grab a patched boot image or did you boot with the TWRP image and install Magisk yourself?
Grabbing the wrong image is the number one thing that causes WiFi and SIM issues.
tech_head said:
How did you root?
Did you grab a patched boot image or did you boot with the TWRP image and install Magisk yourself?
Grabbing the wrong image is the number one thing that causes WiFi and SIM issues.
Click to expand...
Click to collapse
I used this method (copied from irsa mintTM in a YouTube comment)
"REBOOT TWRP
FORMAT DATA (If you are encryted) your internal memory will be lost!!!
REBOOT TWRP
WIPE DATA & CACHE
Flash Rom
Flash TWRP Installer
REBOOT TWRP
WIPE DATA & CACHE
Flash Rom again
Flash TWRP again
REBOOT TWRP
Flash Magisk 19.4!!!! <----This version
Flash DM Verity zip file <--- Always last file before system reboot
REBOOT SYSTEM AND ENJOY"
Gotta unlock for custom ROMs. Flash back to TMobile firmware do a sim unlock, then you can flash back.
wired57 said:
Gotta unlock for custom ROMs. Flash back to TMobile firmware do a sim unlock, then you can flash back.
Click to expand...
Click to collapse
Oh ok, gotcha! I'll give that a go using this video and method and I'll update you if that fixed everything.
youtube .com/ watch?v=4CeCM88ecv4
Thank you so much!!
wired57 said:
Gotta unlock for custom ROMs. Flash back to TMobile firmware do a sim unlock, then you can flash back.
Click to expand...
Click to collapse
I got the T-Mobile stock everything back and everything locked back down, but my SIM card is showing now service now - the same no sim message as was on LineageOS, not even receiving texts now.
I'll re-seat and mess with it when I get some more time.
wired57 said:
Gotta unlock for custom ROMs. Flash back to TMobile firmware do a sim unlock, then you can flash back.
Click to expand...
Click to collapse
Also, I went to the unlock app and it says it's fully unlocked already and can be used with any carrier...
If you didn't use the msm tool to get you back to the T-Mobile firmware, then you probably aren't on T-Mobile firmware. I had the same issue trying to get lineage to work, and was able to get back to stock and have data.
Since you probably don't have the bootloader unlock code, you need to convert to international firmware, and fully update to at least 10.3.2 before you flash lineage. If you don't, you won't have service.
Sent from my GM1915 using Tapatalk
mjdavis871 said:
If you didn't use the msm tool to get you back to the T-Mobile firmware, then you probably aren't on T-Mobile firmware. I had the same issue trying to get lineage to work, and was able to get back to stock and have data.
Since you probably don't have the bootloader unlock code, you need to convert to international firmware, and fully update to at least 10.3.2 before you flash lineage. If you don't, you won't have service.
Sent from my GM1915 using Tapatalk
Click to expand...
Click to collapse
I did use the MSM tool, it's locked, has the T-Mobile boot animation and everything.
I do have the unlock file & code, I had to wait a week to get it.
So you got the Edge S and want GApps? Basically you unlock your bootloader, root with Magisk, then install MagiskGApps.
DISCLAIMER: UNLOCKING YOUR BOOTLOADER MAY VOID YOUR WARRANTY, AND DOING ALL THESE THINGS IN THIS GUIDE MAY RESULT IN DAMAGE/BRICKING YOUR PHONE. I AM NOT RESPONSIBLE FOR ANYTHING YOU DO TO YOUR PHONE. PROCEED AT YOUR OWN RISK.
1. Unlock the bootloader: that should be doable with their global bootloader unlock website here.
2. Download Lenovo Motoroa Smart Assistant (Rescue and Smart Assistant), and follow its instructions to "rescue" your device. It will lead you to boot into bootloader mode and download the firmware. Find the firmware file via the LMSA's downloads (should have a "show folder" button). You'll need the boot.img file for Magisk.
3. Download Magisk, then follow its instructions. You'll have to copy the boot.img to your device, then use Magisk to patch the boot file, then copy the modified one to your PC.
4. You'll need fastboot. If you don't have it already, you can download the Android SDK platform tools here. Then go into the folder, Shift+Right Click the folder, then "Open Command Prompt" or "Open PowerShell," you should have something close to one of those two. Copy your Magisk modified .img file to that folder, then you'll want to input:
fastboot flash boot [modified .img file]
Once that completes, you should see in large text, "Start" on your phone next to the power button. Press the power button, and it should boot, and you should have root now.
5. Download MagiskGApps to your phone, open Magisk on your phone, click the button that looks like a puzzle piece at the bottom of the screen, "Modules." Click "Install from storage," locate the MagiskGApps file, and install it. After that it will ask you to restart your phone, do that, then you'll just have to be patient as it takes time once its restarted to load everything. You also may need to update some or all of the apps, then you should be able to use the notification to finish setting up the phone with Google Setup.
Thanks to Motorola for making it easy to unlock their bootloaders
Thanks to the whole Magisk team for making an easy, awesome root (and more!)
Thanks to Wacko1805 (and team?) for making MagiskGApps. This is really awesome.
unlock the BL and get root is will make some apps fingerprint and face ID fail?
kimker said:
unlock the BL and get root is will make some apps fingerprint and face ID fail?
Click to expand...
Click to collapse
Magisk has a "Magisk Hide" which will allow it to pass SafetyNet, and most things which check on device security will think the device is secure. But unlocking BL and rooting does make the device less secure, and therefore incurs its own risks apart from bricking or damaging the device.
HopelesRomantc91 said:
Magisk has a "Magisk Hide" which will allow it to pass SafetyNet, and most things which check on device security will think the device is secure. But unlocking BL and rooting does make the device less secure, and therefore incurs its own risks apart from bricking or damaging the device.
Click to expand...
Click to collapse
yes, i knew the unlock and root will take risk.. but not sure is Payment business apps using fingerprint will work normal.
kimker said:
yes, i knew the unlock and root will take risk.. but not sure is Payment business apps using fingerprint will work normal.
Click to expand...
Click to collapse
Google Pay works. But according to the Motorola website you should be able to relock the bootloader if yours doesn't work. But there's never any guarantee. If you need your device secure, recommend don't unlock bl or root, or wait to see if there's a root option without bootloader unlock that can be easily undone.
HopelesRomantc91 said:
Google Pay works. But according to the Motorola website you should be able to relock the bootloader if yours doesn't work. But there's never any guarantee. If you need your device secure, recommend don't unlock bl or root, or wait to see if there's a root option without bootloader unlock that can be easily undone.
Click to expand...
Click to collapse
I saw that someone’s edge s had unlocked the BL and Flash G100 firmware and everything worked normally, and then tried to lock the BL again, but it was unsuccessful and the system could not start. The flashing tool does not recognize the machine.
kimker said:
I saw that someone’s edge s had unlocked the BL and Flash G100 firmware and everything worked normally, and then tried to lock the BL again, but it was unsuccessful and the system could not start. The flashing tool does not recognize the machine.
Click to expand...
Click to collapse
That's not good. Hopefully they can restore it back somehow. With this guide to unlock and flash gapps why would you need to flash G100 though? This seems to be itright now without one of rom developer's releases to get root & apps. For me this is all i would look for. Titanium backup on it and restore.. done until PE rom comes out.
kimker said:
I saw that someone’s edge s had unlocked the BL and Flash G100 firmware and everything worked normally, and then tried to lock the BL again, but it was unsuccessful and the system could not start. The flashing tool does not recognize the machine.
Click to expand...
Click to collapse
I would think yes, if you flash different firmware, locking the BL would likely cause problems. It's very difficult to do anything w/o unlocked bootloader, except sometimes rooting is doable. That's pretty much the behavior I expect. If they come to this subforum, we might be able to help.
HopelesRomantc91 said:
I would think yes, if you flash different firmware, locking the BL would likely cause problems. It's very difficult to do anything w/o unlocked bootloader, except sometimes rooting is doable. That's pretty much the behavior I expect. If they come to this subforum, we might be able to help.
Click to expand...
Click to collapse
thank you. They did not ask for help. It seems that the lock BL is a self-verification switch, and then performs a verification system integrity.
HopelesRomantc91 said:
I would think yes, if you flash different firmware, locking the BL would likely cause problems. It's very difficult to do anything w/o unlocked bootloader, except sometimes rooting is doable. That's pretty much the behavior I expect. If they come to this subforum, we might be able to help.
Click to expand...
Click to collapse
I'm curious,If you unlock and flash other firmware and then flash back to the original firmware, can it be locked again?
Mine doesn't let me unlock its BL. I've got unlock code from moto and did a factory reset with SIM card in slot 1. After enabling developer mode and debugging the switch still is greyed out. So no chance to unlock it.
Has anyone got an idea what to try now?
Moto support answered yesterday to my request but also no solution since I told them that it doesn't work
Device is not branded. I got it from Amazon so no provider branding.
If this won't be able to be unlocked and rooted I'll have to return it and switch to a Google Pixel.
kischde said:
Mine doesn't let me unlock its BL. I've got unlock code from moto and did a factory reset with SIM card in slot 1. After enabling developer mode and debugging the switch still is greyed out. So no chance to unlock it.
Has anyone got an idea what to try now?
Moto support answered yesterday to my request but also no solution since I told them that it doesn't work
Device is not branded. I got it from Amazon so no provider branding.
If this won't be able to be unlocked and rooted I'll have to return it and switch to a Google Pixel.
Click to expand...
Click to collapse
I had the same issue, you need to factory reset WITH your sim card in the phone, this will let you open the OEM unlock slide thing in the dev mode.
Then once its done you can fastboot and unlock the bootloader.
I did so, maybe I explained not so well. SIM was inserted and then I did factory reset by starting it from settings. After restart it's still the same - switch / unlock slider greyed out.
kischde said:
I did so, maybe I explained not so well. SIM was inserted and then I did factory reset by starting it from settings. After restart it's still the same - switch / unlock slider greyed out.
Click to expand...
Click to collapse
On my OG Pixel XL, I had to wait 7 days for the slider to become normal. By the time I got around to do it on the Edge S it was about the same time.... could be related
Now as you said that I remember that thingy with another device. Maybe a Xiaomi I think... With that I had to wait several days until the unlock code was delivered.
But there was a message, too, when trying to get it sooner, which said you needed to wait some more time.
Not sure if it's the the same for Moto devices? Then again, when thinking that you experienced the same with a Pixel, too...
Did anyone else make such an experience with his/her g100?
kischde said:
Now as you said that I remember that thingy with another device. Maybe a Xiaomi I think... With that I had to wait several days until the unlock code was delivered.
But there was a message, too, when trying to get it sooner, which said you needed to wait some more time.
Not sure if it's the the same for Moto devices? Then again, when thinking that you experienced the same with a Pixel, too...
Did anyone else make such an experience with his/her g100?
Click to expand...
Click to collapse
Make sure your on the latest OTA, Lenovo made a mistake on previous versions with the OEM Unlocking function not being enabled. They fixed it in latest ota.
RSA tool said the file I uploaded yesterday is the latest one available (and it's exactly the same as the installed version).
The device was released just a few days ago in Europe. Perhaps they fixed the unlock switch in other regions and still need to fix it in Europe..
Will wait until weekend if they come up with a solution. If not I'm afraid I have to return the device as I need it personally AND professionally, too - I'm field agent, so.... :/
HopelesRomantc91 said:
I would think yes, if you flash different firmware, locking the BL would likely cause problems. It's very difficult to do anything w/o unlocked bootloader, except sometimes rooting is doable. That's pretty much the behavior I expect. If they come to this subforum, we might be able to help.
Click to expand...
Click to collapse
The poor guy whose phone turned bricks went to the after-sales department of moto, and the answer was that he needed to replace the phone motherboard. .
kimker said:
The poor guy whose phone turned bricks went to the after-sales department of moto, and the answer was that he needed to replace the phone motherboard. .
Click to expand...
Click to collapse
Ouch...
kimker said:
I'm curious,If you unlock and flash other firmware and then flash back to the original firmware, can it be locked again?
Click to expand...
Click to collapse
I would assume so, but I don't really know why anyone would want to relock.
MOD Edit: check post #25#25 before you proceed.
craznazn said:
This thread was created before I made the MSM conversion, hence the confusion. Probably could be locked now.
And if the OP is still reading this, for your own good don't mess with modemst1/2/persist unless you really know what you're doing.
Click to expand...
Click to collapse
As title suggests, I am trying to convert from the T-Mobile software to Global or EU. Have already read the threads claiming you can just flash the firmware that you want and everything will work fine as long as you also flash the T-Mobile carrier, modem, modemst1, and modemst2 images. However, there is no local upgrade option in settings, so I decided to go the manual route by downloading full zip, using payload dumper and flashing all required partitions, including the T-Mobile modem partitions and whatnot. Well, in terminal when trying to flash certain ones, I get the error:
FAILED (remote: 'Flashing is not allowed for Critical Partitions
')
fastboot: error: Command failed
So I basically just reboot, nothing seems changed and I still have a working phone. What gives? I'm coming from the OnePlus 7 Pro and although had my ups and downs (generally forgetting a step or making small mistakes) it was a fairly easy experience and I could usually just retrace my steps or do some research on forums and figure it out. This time I have looked through so many forums here and on other sites but I can't figure out what's going on.
Details:
Phone is fully functional as of right now
Running 11.2.2.2 (T-Mobile) attempting to convert to 11.2.4.4 (EU)
Had mobbdeep network unlock for me, then requested unlock token from OnePlus, flashed unlock_code.bin, unlocked Bootloader
Successfully rooted with Magisk, although failed SafetyNet so installed latest canary build and everything is working flawlessly now
Can't local upgrade, can't flash via Fastboot, no TWRP available for this device, is there anything that I am missing? or another way that I can flash full update or partitions?
I know I may seem impatient, but I've seen so many others say they already converted to global, and it's working after flashing necessary modem and carrier partitions. Just wondering EXACTLY how they were able to do it, when I followed exact steps from these threads and I've done this sort of thing so many times in the past it is downright frustrating at this point. I've also contacted OnePlus to see if there is an MSM tool available for this device and they sort of made it seem that there was and said my concern will be escalated and I will get a response via email within 24 hours (fingers crossed).
My next steps will be to re-lock the bootloader and start from scratch. After that, I guess my only recourse is to wait for TWRP or MSM tool and official guide for converting to global ROM. Thanks in advance for any and all clarifications.
Side Note: Already tried fastboot flashing unlock_critical command and similar ones, always returns message saying already unlocked. And the conversion guide I was following was from this thread: https://forum.xda-developers.com/t/tmo-eu-global-the-way-i-did-it.4264883/
Certain partitions need to be flashed from the bootloader fastboot, not fastbootd.
Either way, there is no going back to the T-Mobile firmware as there's no unbrick tool yet.
Don't do this.
lrod55 said:
As title suggests, I am trying to convert from the T-Mobile software to Global or EU. Have already read the threads claiming you can just flash the firmware that you want and everything will work fine as long as you also flash the T-Mobile carrier, modem, modemst1, and modemst2 images. However, there is no local upgrade option in settings, so I decided to go the manual route by downloading full zip, using payload dumper and flashing all required partitions, including the T-Mobile modem partitions and whatnot. Well, in terminal when trying to flash certain ones, I get the error:
FAILED (remote: 'Flashing is not allowed for Critical Partitions
')
fastboot: error: Command failed
So I basically just reboot, nothing seems changed and I still have a working phone. What gives? I'm coming from the OnePlus 7 Pro and although had my ups and downs (generally forgetting a step or making small mistakes) it was a fairly easy experience and I could usually just retrace my steps or do some research on forums and figure it out. This time I have looked through so many forums here and on other sites but I can't figure out what's going on.
Details:
Phone is fully functional as of right now
Running 11.2.2.2 (T-Mobile) attempting to convert to 11.2.4.4 (EU)
Had mobbdeep network unlock for me, then requested unlock token from OnePlus, flashed unlock_code.bin, unlocked Bootloader
Successfully rooted with Magisk, although failed SafetyNet so installed latest canary build and everything is working flawlessly now
Can't local upgrade, can't flash via Fastboot, no TWRP available for this device, is there anything that I am missing? or another way that I can flash full update or partitions?
I know I may seem impatient, but I've seen so many others say they already converted to global, and it's working after flashing necessary modem and carrier partitions. Just wondering EXACTLY how they were able to do it, when I followed exact steps from these threads and I've done this sort of thing so many times in the past it is downright frustrating at this point. I've also contacted OnePlus to see if there is an MSM tool available for this device and they sort of made it seem that there was and said my concern will be escalated and I will get a response via email within 24 hours (fingers crossed).
My next steps will be to re-lock the bootloader and start from scratch. After that, I guess my only recourse is to wait for TWRP or MSM tool and official guide for converting to global ROM. Thanks in advance for any and all clarifications.
Side Note: Already tried fastboot flashing unlock_critical command and similar ones, always returns message saying already unlocked. And the conversion guide I was following was from this thread: https://forum.xda-developers.com/t/tmo-eu-global-the-way-i-did-it.4264883/
Click to expand...
Click to collapse
Curious, do you have the stock T-Mobile oneplus9 regular boot.img you can share ? I am looking to try several things on my end but I forgot to backup that img file. Thank you in advance.
inspron said:
Curious, do you have the stock T-Mobile oneplus9 regular boot.img you can share ? I am looking to try several things on my end but I forgot to backup that img file. Thank you in advance.
Click to expand...
Click to collapse
I should still have the boot.img I backed up from stock 11.2.2.2 (T-Mobile). I'll attach it here when I get off work
LLStarks said:
Certain partitions need to be flashed from the bootloader fastboot, not fastbootd.
Either way, there is no going back to the T-Mobile firmware as there's no unbrick tool yet.
Don't do this.
Click to expand...
Click to collapse
+1 . I myself love flashing things and have the unlocked op9. Just got in mail and unlocked and rooted this evening. I however will not be flashing anything but magisk updates till an msm tool is available for us to use.
inspron said:
Curious, do you have the stock T-Mobile oneplus9 regular boot.img you can share ? I am looking to try several things on my end but I forgot to backup that img file. Thank you in advance.
Click to expand...
Click to collapse
This should be the stock boot.img from the 11.2.2.2 T-Mobile build. Named it that way so as to not confuse it with stock boot image from 11.2.4.4 (EU)
boot(old).img (Google Drive link)
mattie_49 said:
+1 . I myself love flashing things and have the unlocked op9. Just got in mail and unlocked and rooted this evening. I however will not be flashing anything but magisk updates till an msm tool is available for us to use.
Click to expand...
Click to collapse
Will heed your guys' warnings. Just was super curious (and confused) as to how others were able to get it to work
Following in case there is a breakthrough. I hate the locked T-Mobile BS. And all I want to be able to do is stay awake while charging. My 6 did it no problem. But this thing is making me mad.
jaed.43725 said:
Following in case there is a breakthrough. I hate the locked T-Mobile BS. And all I want to be able to do is stay awake while charging. My 6 did it no problem. But this thing is making me mad.
Click to expand...
Click to collapse
You know the unlocked global version works with carrier sims. I'm on verizon . Bought the unlocked 9 popped the verizon sim in and everything works perfect. Vvm/5g everything. And unlocked to my liking
mattie_49 said:
You know the unlocked global version works with carrier sims. I'm on verizon . Bought the unlocked 9 popped the verizon sim in and everything works perfect. Vvm/5g everything. And unlocked to my liking
Click to expand...
Click to collapse
Yes, I am very aware of that. The issue is I have the T-Mobile version because I got if 1/2 off with a trade in. Will this warrant a trade after I pay it off? Maybe. But I would rather just put on Lineage OS if that becomes possible.
lrod55 said:
As title suggests, I am trying to convert from the T-Mobile software to Global or EU. Have already read the threads claiming you can just flash the firmware that you want and everything will work fine as long as you also flash the T-Mobile carrier, modem, modemst1, and modemst2 images. However, there is no local upgrade option in settings, so I decided to go the manual route by downloading full zip, using payload dumper and flashing all required partitions, including the T-Mobile modem partitions and whatnot. Well, in terminal when trying to flash certain ones, I get the error:
FAILED (remote: 'Flashing is not allowed for Critical Partitions
')
fastboot: error: Command failed
So I basically just reboot, nothing seems changed and I still have a working phone. What gives? I'm coming from the OnePlus 7 Pro and although had my ups and downs (generally forgetting a step or making small mistakes) it was a fairly easy experience and I could usually just retrace my steps or do some research on forums and figure it out. This time I have looked through so many forums here and on other sites but I can't figure out what's going on.
Details:
Phone is fully functional as of right now
Running 11.2.2.2 (T-Mobile) attempting to convert to 11.2.4.4 (EU)
Had mobbdeep network unlock for me, then requested unlock token from OnePlus, flashed unlock_code.bin, unlocked Bootloader
Successfully rooted with Magisk, although failed SafetyNet so installed latest canary build and everything is working flawlessly now
Can't local upgrade, can't flash via Fastboot, no TWRP available for this device, is there anything that I am missing? or another way that I can flash full update or partitions?
I know I may seem impatient, but I've seen so many others say they already converted to global, and it's working after flashing necessary modem and carrier partitions. Just wondering EXACTLY how they were able to do it, when I followed exact steps from these threads and I've done this sort of thing so many times in the past it is downright frustrating at this point. I've also contacted OnePlus to see if there is an MSM tool available for this device and they sort of made it seem that there was and said my concern will be escalated and I will get a response via email within 24 hours (fingers crossed).
My next steps will be to re-lock the bootloader and start from scratch. After that, I guess my only recourse is to wait for TWRP or MSM tool and official guide for converting to global ROM. Thanks in advance for any and all clarifications.
Side Note: Already tried fastboot flashing unlock_critical command and similar ones, always returns message saying already unlocked. And the conversion guide I was following was from this thread: https://forum.xda-developers.com/t/tmo-eu-global-the-way-i-did-it.4264883/
Click to expand...
Click to collapse
you flash from bootloader (fastboot) or from fastbootd
FAILED (remote: 'Flashing is not allowed for Critical Partitions this is when you flash in fastboot
only fastbootd can flashh all partition
jaed.43725 said:
Following in case there is a breakthrough. I hate the locked T-Mobile BS. And all I want to be able to do is stay awake while charging. My 6 did it no problem. But this thing is making me mad.
Click to expand...
Click to collapse
You know there's a specific option under the development settings called 'stay awake', right?
TheKnux said:
You know there's a specific option under the development settings called 'stay awake', right?
Click to expand...
Click to collapse
I can not select it. It is greyed out for some reason.
TheKnux said:
You know there's a specific option under the development settings called 'stay awake', right?
Click to expand...
Click to collapse
On the T-Mobile version it is not selectable.
jaed.43725 said:
On the T-Mobile version it is not selectable.
Click to expand...
Click to collapse
Yeah that's BS because I definitely selected it while I was backing up my data before I converted from T-Mobile firmware.
jaed.43725 said:
On the T-Mobile version it is not selectable.
Click to expand...
Click to collapse
I'm on t-mobile version i can select it as well. Pretty sure everything in developers options is selectable. Some don't stick for whatever reason.
Ya, I don't know what this things deal is. But as soon as I get the ability to flash to international I'm doing it.
Where is the guide for flashing a OnePlus 9 from T-Mobile to International?
Btw for everyone following this thread, its an easy to miss step, but if you follow the guides for converting, all you have to do is go into fastboot and then use command “fastboot reboot fastboot”. This apparently puts you in fastbootd (never had to use this before, I would just use commands and flash stuff from bootloader screen but whatever) where you can then flash the needed partitions. Also, no hate to the guy who posted the recent conversion thread but it is super unorganized and a little too easy to miss that step, as well as MAKE SURE you read through the .bat file they provided because it is NOT correct. They have some typos in there so it wasn’t working for me at first. It’s a pain in the ass but I highly recommend going through each command, copy/paste, and read it to make sure there’s no typos then hit enter or you will run into errors like I did. Good luck