Related
I just wanted to let you guys know a couple things from what I've been playing around with.
1. The Amazon G6 I bought had an unlockable bootloader. Just went through the normal request procedure and it was given to me.
2. You can install normal G6 firmware on it. Software channel will still say AMZ but you won't have the bloat apps or an Amazon option in your settings.
3. No Magisk support (which appears to be the same as unlocked version).
4. Project Treble works but I haven't figured it out yet. Spent some time to get the correct drivers installed to be able to flash on it. Couldn't get a 64-bit GSI to work (I don't think our phone supports it?) but got a 32-bit one to work. Going to double check on 64-bit because I had to restart the 32-bit one a couple times to get it to work.
When I started the Treble rom it said I had a password to enter, which I didn't, so I had to factory reset again. Also couldn't get Google Play Services to work. I registered my number with Google but it didn't change anything. Also kept getting toast notifications about apps not working right because update channel was null or something like that. Not sure if that is because of Google Play or something else.
Anyway, I haven't seen much discussion about any of this so figured I'd just post what I know.
gpgorbosjr said:
I just wanted to let you guys know a couple things from what I've been playing around with.
1. The Amazon G6 I bought had an unlockable bootloader. Just went through the normal request procedure and it was given to me.
2. You can install normal G6 firmware on it. Software channel will still say AMZ but you won't have the bloat apps or an Amazon option in your settings.
3. No Magisk support (which appears to be the same as unlocked version).
4. Project Treble works but I haven't figured it out yet. Spent some time to get the correct drivers installed to be able to flash on it. Couldn't get a 64-bit GSI to work (I don't think our phone supports it?) but got a 32-bit one to work. Going to double check on 64-bit because I had to restart the 32-bit one a couple times to get it to work.
When I started the Treble rom it said I had a password to enter, which I didn't, so I had to factory reset again. Also couldn't get Google Play Services to work. I registered my number with Google but it didn't change anything. Also kept getting toast notifications about apps not working right because update channel was null or something like that. Not sure if that is because of Google Play or something else.
Anyway, I haven't seen much discussion about any of this so figured I'd just post what I know.
Click to expand...
Click to collapse
FYI G6's SOC is arm (32bits) so you better stop flashing 64bit builds before you brick your device
CreasingMass Dev said:
FYI G6's SOC is arm (32bits) so you better stop flashing 64bit builds before you brick your device
Click to expand...
Click to collapse
Well actually the SOC is 64 bit. But I guess Motorola used 32 bit software because ......Motorola.
Thanks for the warning but I'm not worried. It just won't load the os if it's an issue and you can flash the stock one back easily enough.
I'm assuming we will be able to get 64 bit roms on this phone when twrp and all that come. The SOC itself is 64-bit.
Consult Here
But I think I just may use this as a backup play around with phone anyway since we couldn't get the G6+ in US.
gpgorbosjr said:
Well actually the SOC is 64 bit. But I guess Motorola used 32 bit software because ......Motorola.
Thanks for the warning but I'm not worried. It just won't load the os if it's an issue and you can flash the stock one back easily enough.
Click to expand...
Click to collapse
Yea i just read the actual SOC "supports" 64bit, anyway stuff on the G6 is 32bit so yea
CreasingMass Dev said:
FYI G6's SOC is arm (32bits) so you better stop flashing 64bit builds before you brick your device
Click to expand...
Click to collapse
CreasingMass Dev said:
Yea i just read the actual SOC "supports" 64bit, anyway stuff on the G6 is 32bit so yea
Click to expand...
Click to collapse
Yep. I was editing my post as you replied but like I said I'm sure this phone will get 64-bit ROMS at the end of the day when stuff is sorted out.
And I definitely would've been more careful flashing but I knew the stock firmware restore worked and I've done a lot of crazy stuff to phones in my days and never messed one up so bad I couldn't get to bootloader.
I am getting my g6 from Amazon tommorow....I m out of the phone flashing hobby for a while...not completely sure if I understand the o.p. here ,
Can I install stock g6 on this device removing Amazon stuff? I guess yes ...can. Someone post the link ? ..does this void warranty?
How do I root or install magiks ?
Super helpful post -- thanks!
Just got an "exclusive" G6 from amazon.
Alas bootloader is not unlockable. What's worse, I only realized that after I've attempted to flash stock G6 image.
Now I can only boot in fastboot mode.
Does anybody know if there are stock images for amazon G6?
Or if there's any other way to unbrick amazon phone using stock G6 image.
zzyxy said:
Just got an "exclusive" G6 from amazon.
Alas bootloader is not unlockable. What's worse, I only realized that after I've attempted to flash stock G6 image.
Now I can only boot in fastboot mode.
Does anybody know if there are stock images for amazon G6?
Or if there's any other way to unbrick amazon phone using stock G6 image.
Click to expand...
Click to collapse
you didn't go to Motorola's site did you? easily unlock your bootloader there.
supergear said:
you didn't go to Motorola's site did you? easily unlock your bootloader there.
Click to expand...
Click to collapse
I did, and it the page gave me a popup that said that my phone is not eligible and the button to request the code never showed up. I did get unlock code for another G6 (i.e. no amazon prime special), so I'm pretty sure I didn't mess up the process.
Can also confirm I'm not able to unlock the bootloader. So either something's wrong with the system on Motorola's end or you got extremely lucky getting an unlock code. Double checked everything and used the data scrub tool. No luck.
I have an Amazon G6. I was able to enter developer mode and toggle "Unlocked Bootloader", so I assume my is unlocked. Regarding OP's message:
> 1. The Amazon G6 I bought had an unlockable bootloader. Just went through the normal request procedure and it was given to me.
> 2. You can install normal G6 firmware on it. Software channel will still say AMZ but you won't have the bloat apps or an Amazon option in your settings.
What do you mean "went through the normal request procedure and it was given to me."? And where do I get a "normal G6 firmware" for it? I am already sick of the Amazon apps and I want a clean phone. Can OP possibly write up a more detailed guide?
You have to go to the Motorola bootloader unlock page and request a code. The toggle just allows you to unlock the bootloader if an unlock key is granted through fastboot. So far I've only seen one person that successfully received an unlock key. Everyone else gets the device not eligible message.
Also unable to unlock
I received the 64GB version, today, and get the message from the Motorola website that my device is ineligible to be unlocked. Darn the luck, I bought it hoping for the best. Should I try again, later?
CreasingMass Dev said:
Yea i just read the actual SOC "supports" 64bit, anyway stuff on the G6 is 32bit so yea
Click to expand...
Click to collapse
The G6's SOC is 64 bit like the guy said, no supporting, it IS 64 bit, if you were to look in any CPU app it will show 64 bit architecture running in 32 bit mode, so there ya go
So do people recommend paying the extra money to buy a non-exclusive version?
Same here. Very disappointed with Amazon!
Meep70 said:
I received the 64GB version, today, and get the message from the Motorola website that my device is ineligible to be unlocked. Darn the luck, I bought it hoping for the best. Should I try again, later?
Click to expand...
Click to collapse
Chatted with Motorola, they can't help. They said just keep reading forums.....
That's what I figured. I'm quietly watching, and I occasionally try to see if something changes on Motorola's side.
Today I received a T-Mobile, SIM unlocked, OnePlus 7Pro GM1915.
I have already followed the steps to flash international firmware and that went fine. Only issue I had was my SIM was being detected but no service, an OTA update to 10.0.3 fixed that issue. I haven't had a phone with root access/unlocked bootloader since my 1st gen Moto X so excuse my ignorance if some of these question are common sense, but I've done some searching online and can't find any straight forward answers.
1. Now that I have installed the international firmware I don't need to get a bootloader unlock from T-Mobile, correct? I can just use the OEM unlock option and unlock via fastboot?
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?
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? I would assume yes since you can do an OTA update and keep Magisk, but I just wanted to verify.
Again, sorry if some of this is common sense, but I've searched around and can't find straight forward answers fort any of this.
First, sim unlocked you're good to go. No need to bother T-Mobile. Bootloader unlock is through OnePlus. Guides aplenty here, search will turn up what you need. I'm personally running the box stock firmware unrooted and at the moment I'm very happy with it.fotr the first time in a long time I don't see much value in going through the process of rooting because the stock ROM pretty much has everything that I used to get with rooting and a custom ROM. I will probably do it anyway at some point, just because I feel wierd not having root.
Sent from my OnePlus 7 Pro using XDA Labs
guitardoc64 said:
First, sim unlocked you're good to go. No need to bother T-Mobile. Bootloader unlock is through OnePlus. Guides aplenty here, search will turn up what you need. I'm personally running the box stock firmware unrooted and at the moment I'm very happy with it.fotr the first time in a long time I don't see much value in going through the process of rooting because the stock ROM pretty much has everything that I used to get with rooting and a custom ROM. I will probably do it anyway at some point, just because I feel wierd not having root.
Sent from my OnePlus 7 Pro using XDA Labs
Click to expand...
Click to collapse
Thanks for the feedback.
I think I'm going to update to the newest firmware. Worst case I decide I want to root I'll use MSM and downgrade, my phone will get wiped when I unlock my bootloader anyway.
guitardoc64 said:
First, sim unlocked you're good to go. No need to bother T-Mobile. Bootloader unlock is through OnePlus. Guides aplenty here, search will turn up what you need. I'm personally running the box stock firmware unrooted and at the moment I'm very happy with it.fotr the first time in a long time I don't see much value in going through the process of rooting because the stock ROM pretty much has everything that I used to get with rooting and a custom ROM. I will probably do it anyway at some point, just because I feel wierd not having root.
Sent from my OnePlus 7 Pro using XDA Labs
Click to expand...
Click to collapse
The reason I root is adblocker system wide
jamescable said:
The reason I root is adblocker system wide
Click to expand...
Click to collapse
I found an app called block this. It does a good job and doesn't need root. It might not block ads on YouTube but it gets rid of the annoying ones in games.
Sent from my OnePlus 7 Pro using XDA Labs
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/
Hello all!
Thanks for taking the time to click into this.
About me: I mostly see myself as a somewhat tech-savvy noob - I have rooted several devices in the past, flashed ROMs, etc.
New Device: OnePlus 8T T-Mobile Variant purchased from OnePlus.com
Condition: Brand New - never started the device
I would like to essentially imitate Calyx as described here.
=> install TWRP/Magisk + flash 'LineageOS for MicroG'
Questions:
1) Will I be able to unlock the bootloader given that this is the T-Mobile variant purchased from OnePlus?
2) Do I need to take additional steps because this phone is the T-Mobile variant?
3) basic question: I have never started the phone so it has no personal data - should I back up the current setup in case I need to return to OOS for any reason or can I track down the default OOS installation making that all unnecessary?
(I remember in the past default Samsung installations were easily tracked down and flashed using Odin).
4) Would you recommend any detailed instructions to go through the process of backup, installing custom recovery, accessing root privileges, flashing LineageOS for MicroG, etc?
(I feel like I am piecing parts together from different places and it's all not fitting together)
Thank you so much for reading this.... I feel like I'm going down several rabbit holes currently so any perspective or support is welcome!
It would be helpful to hear any thoughts from some more experienced peeps before I move ahead.
Thank you!
Currently, I am trying to get the SIM unlocked, then unlock the bootloader, and proceed with the plan above.
I am considering returning the phone and getting a different one that has more users on XDA to avoid having bizarre issues arise with the steps involved with the T-Mobile version of the 8T and being totally on my own.
doctadocta said:
Currently, I am trying to get the SIM unlocked, then unlock the bootloader, and proceed with the plan above.
I am considering returning the phone and getting a different one that has more users on XDA to avoid having bizarre issues arise with the steps involved with the T-Mobile version of the 8T and being totally on my own.
Click to expand...
Click to collapse
yeah I dont see much help for Tmo version and I faced lots of issues just trying to get a brand new one recognized by my computer.
Ejvyas said:
yeah I dont see much help for Tmo version and I faced lots of issues just trying to get a brand new one recognized by my computer.
Click to expand...
Click to collapse
whoa! that's helpful feedback. Thank you for posting!
Based on your comment, I am leaning towards returning the phone.
I think I learn best through examples and may need a little support.
I am now wondering how I can figure out which phones have the largest 'community' on XDA.
I have the T-Mobile variant. There's more support and options available so don't be discouraged.
Normally, you have to be SIM unlocked before you can do anything else, like bootloader unlocking. If the phone is being paid for or financed and you haven't been a long time customer you may or may not get it SIM unlocked.
That said, I got mine SIM unlocked after contacting the T-Mobile Tforce people on Facebook. Then I saw this thread on Rebranding the T-Mobile variant.
[GUIDE] Convert TMO to EU via MSM Tool, no SIM Unlock or Bootloader Unlock needed!
*** Use this at your very own risk. *** You will lose all data *** Backup your working modem and persist, just in case *** Read the entire post and follow the steps closely before asking for help. Post all error messages and steps you took...
forum.xda-developers.com
Following it I changed the T-Mobile firmware to the European firmware. If nothing else you get more recent updates and a local update feature (full OTA updates can be downloaded and installed locally). As a result of the conversion I was able to simply fastboot unlock the bootloader without need for waiting for a code from OnePlus. The phone is now bootloader unlocked and rooted with Magisk.
Note that according to the OP, SIM unlock is not necessary for the conversion but you'll still need to be SIM unlocked to be able to unlock the bootloader.
Now that I'm "free" I now have the itch for a custom ROM. Over the years all of my devices run either with microG or just UnifiedNlp but no Google. I feel the need to do the same here. Currently I just have most Google apps disabled and using FOSS apps in their place but still...
Besides LineageOS for microG, the 8T also has Carbon ROM and crDroid. They historically have always had signature spoofing support so I assume they still do with Android 11. That means microG can be used.
Check the guides and ROM/Kernel threads for more info.
I don't know if I can get to trying anything this week but I hope to. I work at a drive-in movie theater and with Spider-Man coming out this week I'll be quite busy.
marcdw said:
I have the T-Mobile variant. There's more support and options available so don't be discouraged.
Normally, you have to be SIM unlocked before you can do anything else, like bootloader unlocking. If the phone is being paid for or financed and you haven't been a long time customer you may or may not get it SIM unlocked.
That said, I got mine SIM unlocked after contacting the T-Mobile Tforce people on Facebook. Then I saw this thread on Rebranding the T-Mobile variant.
[GUIDE] Convert TMO to EU via MSM Tool, no SIM Unlock or Bootloader Unlock needed!
*** Use this at your very own risk. *** You will lose all data *** Backup your working modem and persist, just in case *** Read the entire post and follow the steps closely before asking for help. Post all error messages and steps you took...
forum.xda-developers.com
Following it I changed the T-Mobile firmware to the European firmware. If nothing else you get more recent updates and a local update feature (full OTA updates can be downloaded and installed locally). As a result of the conversion I was able to simply fastboot unlock the bootloader without need for waiting for a code from OnePlus. The phone is now bootloader unlocked and rooted with Magisk.
Note that according to the OP, SIM unlock is not necessary for the conversion but you'll still need to be SIM unlocked to be able to unlock the bootloader.
Now that I'm "free" I now have the itch for a custom ROM. Over the years all of my devices run either with microG or just UnifiedNlp but no Google. I feel the need to do the same here. Currently I just have most Google apps disabled and using FOSS apps in their place but still...
Besides LineageOS for microG, the 8T also has Carbon ROM and crDroid. They historically have always had signature spoofing support so I assume they still do with Android 11. That means microG can be used.
Check the guides and ROM/Kernel threads for more info.
I don't know if I can get to trying anything this week but I hope to. I work at a drive-in movie theater and with Spider-Man coming out this week I'll be quite busy.
Click to expand...
Click to collapse
Do you know how to fix this ?
"Automatic Detection of DDR failed"
Ejvyas said:
Do you know how to fix this ?
"Automatic Detection of DDR failed"
Click to expand...
Click to collapse
Excuse the late reply.
No, not too versed on this device really. I searched for that error and got a lot of hits but didn't have the time to read up. Sorry.
This is a brand new China hardware GM1910 OnePlus 7 pro. 256g 12gig ram model.
No matter how precisely I follow directions it just gives buzzarre responses.
Clues anyone?
The first time it soft bricked a few days back was my fault.
I had android 11 OxygenOS and tried to flash pixel recovery and ROM.
Supposed to have OOS 12.1 which I had this time.
After I flash the pixel recovery it acts all bizzare and refuses to boot to the recovery.
Then it shows this?
I only have the picture. Fastboot mode. And power off.
Is it because it's Chinese? Off AliExpress.
I'm feeling like I've just bought a lemon?
From the OnePlus forums:
GM1910 is the Chinese variant OnePlus 7 Pro running HydrogenOS (with GM21 build tag).
It is possible to flash both GM21AA (global) and GM21BA (EU) OxygenOS firmware on top of the HydrogenOS using the Local Upgrade method.
Bootloader unlocking is not necessary for switching to OxygenOS.
After conversion, you'll get OTA update from the respective branch.
Have you considered trying this first and then maybe try flashing other ROMs after getting to know the device / reading more?
https://onepluscommunityserver.com/list/Unbrick_Tools/OnePlus_7_Pro/Global_GM21AA/R/
Unbrick tool howto:
t-ryder said:
From the OnePlus forums:
GM1910 is the Chinese variant OnePlus 7 Pro running HydrogenOS (with GM21 build tag).
It is possible to flash both GM21AA (global) and GM21BA (EU) OxygenOS firmware on top of the HydrogenOS using the Local Upgrade method.
Bootloader unlocking is not necessary for switching to OxygenOS.
After conversion, you'll get OTA update from the respective branch.
Have you considered trying this first and then maybe try flashing other ROMs after getting to know the device / reading more?
https://onepluscommunityserver.com/list/Unbrick_Tools/OnePlus_7_Pro/Global_GM21AA/R/
Click to expand...
Click to collapse
It's my first ever OnePlus an I bought it as a hobby cellphone. The directions for unlocking the bootloader worked on it. This happened after the pixel experience failure. When I tried to relock the bootloader and it acted wierd.
I could not find any information on the GM1910 model.
Thanks for starting my investigation.
Anything helps at this point
I don't know if the GM21AA unbrick tool will work on the GM1910 tho...
t-ryder said:
I don't know if the GM21AA unbrick tool will work on the GM1910 tho...
Click to expand...
Click to collapse
It does. I think I tried a similar tool to this one 2 days back and after trying various button combinations achieved a boot.
Do you know if this model can boot PE 12 or 13 or will I just get another brick?
The whole point of the purchase was to have an easy time with unlocking the bootloader an trying custom roms.
Was not expecting a nightmare?
My last OnePlus was 8T and 9, and since then I got Google Pixels and other phones...
Bryceicle1971 said:
Do you know if this model can boot PE 12 or 13 or will I just get another brick?
Click to expand...
Click to collapse
I don't know. Just trying to help with the stuff I remember. I mean, you can try and as long as you don't do some crazy stuff and hardbrick it, you can always go back with the unbrick tool. Did that a lot of times when doing ROM hopping back then. The OnePlus devices have an easy to unlock BL, and that's good. But flashing them was a pita (for me). Now on the Pixels I had and have all is much more easier (IMO).
Follow this here (says GM1910 is supported by PE 13)
https://wiki.pixelexperience.org/devices/guacamole/
There is some installation guide too.
Thanks for all the help I'll go see some options. It's very hard to find accurate I formation about this phone as it's reached legendary status. I really like it dispite it being power hungry.
I was just hoping for a few options besides the stock ones. Nothing too crazy.
It's a beautifully performing cellphone dispite being near 4 years old now.
I will keep Google pixel in mind. There are ones the same age as my OnePlus that are dirt cheap. If I find them as easy to work with as you have I might buy a more modern one.
I just wish I knew about the bootloader.
It seems to be permanently unlocked now which could make life difficult? No relocking guide works.
Thanks again
t-ryder said:
Follow this here (says GM1910 is supported by PE 13)
https://wiki.pixelexperience.org/devices/guacamole/
There is some installation guide too.
Click to expand...
Click to collapse
I may of ruled out pixel experience official as I seem to have a permanently unlocked bootloader even when bricked. I don't know?
It's bricked twice now trying official. Might have more luck with unofficial
No luck with that tool. Off for night shift. Tried it 3 times. I put OnePlus in the drawer. Last time the hardware sat in the drawer an bang. 2 days later got a boot. Hoping for magical booting properties again
Bryceicle1971 said:
I may of ruled out pixel experience official as I seem to have a permanently unlocked bootloader even when bricked. I don't know?
Click to expand...
Click to collapse
Try installing LineageOS, not sure if it'd help, but it's a good test I'd assume.
Info about guacamole | LineageOS Wiki
wiki.lineageos.org
Also, using MSM tool should normally relock the bootloader. Are you sure your bootloader is actually unlocked when you use it?
Honkette1738 said:
Try installing LineageOS, not sure if it'd help, but it's a good test I'd assume.
Info about guacamole | LineageOS Wiki
wiki.lineageos.org
Also, using MSM tool should normally relock the bootloader. Are you sure your bootloader is actually unlocked when you use it?
Click to expand...
Click to collapse
Thanks for lineage info. Never heard of MSM. I've no idea why it says senior member lol. I cant even code man
I need help from other xda members. So thank you all
Bryceicle1971 said:
Never heard of MSM.
Click to expand...
Click to collapse
It's the unbrick tool linked earlier in the thread.
Yes I tried that but still get the system destroyed message. It's bright and my little Oppo A96 4g did it's best.
Not sure if you can read it but it says internal system an recovery destroyed.
I did wonder if it's still locked but just saying unlocked because of all the different activities trying to revive it.
I just hope it's not unrecoverable as I just got it and waited a month. So that would be horrible
Bryceicle1971 said:
Yes I tried that but still get the system destroyed message. It's bright and my little Oppo A96 4g did it's best.
Not sure if you can read it but it says internal system an recovery destroyed.
I did wonder if it's still locked but just saying unlocked because of all the different activities trying to revive it.
I just hope it's not unrecoverable as I just got it and waited a month. So that would be horrible
Click to expand...
Click to collapse
Maybe try this page? I'm not exactly sure if it'll be different but it's worth a shot.
[OP7PRO][LATEST OOS 11.0.5.1 GM21AA/GM21BA] Collection of unbrick tools
Disclaimer: By attempting any of the processes listed in this thread you accept full responsibility for your actions. I will not be held responsible if your device stops working, catches fire, or turns into a hipster and claims to have been...
forum.xda-developers.com
Weirdly enough, I can't find anyone with a OnePlus 7 Pro with this error, only OnePlus 8 owners or newer.
Hey guys thanks for all the clues and raising my level from barely above noob
Using an EU MSMdownloadtool.
Believe it or not it was an annoying man who helped me.
Highonandroid man on YouTube
He has a highly comprehensive guide on how to correctly use the MSMdownloadtool an get your OnePlus devices into EDL mode.
Will post if boot happens
MSMdownloadtool and a European fastboot ROM an Highonandroid guys guidance all worked.
Thank you all so much