Related
Some info first:
Carrier: Sprint
Running the Latest TWRP (packaged with Pantheon Kernel), and SuperSu (Huge thanks to joemossjr, Uzephi, and enetec for their respective works, and others!)
So, I'm just trying to grab a little clarity...
Currently I am on "Slot A". When I first purchased the phone, I was on Slot B, and the series of events occurred as such:
Performed all security updates to October
Unlocked Bootloader
Flashed TWRP
Flashed SuperSu
-profited-
Stuck a fork in electrical socket and pressed "reboot system [SLOT A] (When I was on Slot B) - *womp womp*
Was unable to boot to anything except fast-boot
Flash-alled fresh system (Thanks again to all the work over in the development section!)
Performed all security updates to October
Flashed TWRP
Flashed SuperSu
-back in the money-
^^^ Where I am at now, except on SLOT A
So... here's where I need some clarity... if the Slot A / Slot B system works as a pass/trade system between two OS's, effectively allowing consecutive updates.. why did my system hit the crapper when i switched slots?
Theoretically, it should have simply booted into whatever my prior to flashing [what goes here? was it SuperSu that caused the derp, or TWRP?]
Also, now that we have a functioning TWRP as well as a functioning Security check for October, will we get to the point where we are able to actually just flash to separate partitions easily, and thus boot into separate roms easily?
I totally assume I'm missing some vital information above with my understanding about the discrepancies between Slots, as well as other partitions , so feel free to point at laugh at the short-bus kid... so long as you fill me in the gaps in my understanding.
Thanks!
My experiences are according with all you reported... I've done some "stock system" backups too (both A & B...) and I can confirm they differ from day one too...
It seems to be clear that things are a bit more complex than our speculations on them...
So far what I've tested: When you flash all, you go back to slot A (I assume the fastboot erase DDR is what causes it to go back to slot A). In essence, I have had October update on slot A and B by choice by choosing a different flashall zip.
oem is one partition. it is one HUGE partition, but one none-the-less (about 600 MB). The phone sees it as two though (sde19 and sdf19) User data is one partition. (sdb21) SSD is one partition (sdb1).
This means dual booting an OS needs to be similar (where they can share userdata and not cause boot loops) as user data (/data) is shared across both boot-a/boot-b ; system_a/system_b (sde17/sdf17 ; sde18/sdf18)
A lot of vendor specific issues in /crypto of the kernel causes some idiosyncrasies with encryption. any kernel update I do that involves /crypto or /fs edits causes a plethora of headaches.... one kernel update broke ADB and partially broke fastboot
Edit: your user data was decrypted with SU. So slot B was not encrypted. when you went to slot A (was encrypted) your phone couldn't read it.
Uzephi said:
...
This means dual booting an OS needs to be similar (where they can share userdata and not cause boot loops) as user data (/data) is shared across both boot-a/boot-b ; system_a/system_b (sde17/sdf17 ; sde18/sdf18)
Click to expand...
Click to collapse
I agree. When I made some speculations about dual booting (in another thread) I was thinking the same OR switching/recovering different /data by TWRP backup/restore...
Uzephi said:
...
Edit: your user data was decrypted with SU. So slot B was not encrypted. when you went to slot A (was encrypted) your phone couldn't read it.
Click to expand...
Click to collapse
If things here works as on Moto Z (Griffin) your sentence should be... "You have /data decrypted since of SuperSU tweak. Slot B has no more force encryption enabled since of this tweak. When you went to slot A (still with force encryption enabled since of no tweak installed), your phone will begin to encrypt /data partition again (it can read both encrypted and not encrypted, but if not encrypted it will encrypt at first boot) and, since of the long time required by operation on any /data partition not just formatted, it seems to hang/bootlooping..."
enetec said:
If things here works as on Moto Z (Griffin) your sentence should be...
Click to expand...
Click to collapse
The Griffin is different. The kryo msm8998 has it's own encryption chip built on the CPU. our kernels disable that so then everything goes software encryption which causes a bunch of issues. It's the only way we could get TWRP to decrypt the phone.
Uzephi said:
The Griffin is different. The kryo msm8998 has it's own encryption chip built on the CPU. our kernels disable that so then everything goes software encryption which causes a bunch of issues. It's the only way we could get TWRP to decrypt the phone.
Click to expand...
Click to collapse
...interesting!
enetec said:
...interesting!
Click to expand...
Click to collapse
https://www.qualcomm.com/documents/snapdragon-835-mobile-platform-product-brief Page 2 of the PDF, they call it "Qualcomm Haven Suite."
So essentially, Qualcomm took the initiative to "secure" us... For **our** benefit... Potentially against our will... Whereas before, we could choose to software encrypt if we wanted, and software decrypt at our discretion...
Obviously I'm being facetious, this seems to me to clearly be for the benefit of OEMs and Providers. Don't get me wrong, hardware microchipped encryption is kick-ass, especially how fast it manages it.... Just not how it's been utilized here.... As a massive firewall against 3rd party fingers in the pie.
Some_Donkus said:
So essentially, Qualcomm took the initiative to "secure" us... For **our** benefit... Potentially against our will... Whereas before, we could choose to software encrypt if we wanted, and software decrypt at our discretion...
Obviously I'm being facetious, this seems to me to clearly be for the benefit of OEMs and Providers. Don't get me wrong, hardware microchipped encryption is kick-ass, especially how fast it manages it.... Just not how it's been utilized here.... As a massive firewall against 3rd party fingers in the pie.
Click to expand...
Click to collapse
Yes, it's a simple flag in the defconfig file
Here is the slot swappin' solution you were looking for!
Download the most current official Google fastboot:
https://developer.android.com/studio/releases/platform-tools.html
Go into fastboot mode and type on PC:
fastboot set_active _a
(then boot to recovery, check TWRP to see you are on slot _a)
fastboot set_active _b
(then boot to recovery, check TWRP to see you are on slot _b)
Please note: I am sure the a/b switch inside our phone's TWRP will eventually work, but it doesn't currently (as of 17NOV2017); other a/b phones have had the same issue.
What is interesting to me is that flashall flashes both slots, and you can manually choose to flash a specific boot with $flash boot_a or $flash boot_b. With this ability and enough experimenting I'm sure there's a workaround somewhere.
Some_Donkus said:
What is interesting to me is that flashall flashes both slots, and you can manually choose to flash a specific boot with $flash boot_a or $flash boot_b. With this ability and enough experimenting I'm sure there's a workaround somewhere.
Click to expand...
Click to collapse
this method works for me
https://forum.xda-developers.com/showpost.php?p=74543389&postcount=10
jhofseth said:
this method works for me
https://forum.xda-developers.com/showpost.php?p=74543389&postcount=10
Click to expand...
Click to collapse
Oh, haha! I totally missed this post in the thread. Herp-A-Derp! Thank you! (I've been peepin' stuff via the XDA labs on my phone and I'm not used to the notifications and such, thanks for the rewind redirect!)
So... theoretically... if I used the above method to swap into the "other" slot and flash both slots identical, with TWRP and SuperSu... I would be able to swap slots back and forth as I pleased... (even though they would be the same.. and thus making swapping between them.. kind of pointless...) because both would then have the same flag...
If i wanted to modify -ONE- of them, I would have to ensure that it matched the encryption state of the other... correct?
jhofseth said:
Download the most current official Google fastboot:
https://developer.android.com/studio/releases/platform-tools.html
Go into fastboot mode and type on PC:
fastboot set_active _a
(then boot to recovery, check TWRP to see you are on slot _a)
fastboot set_active _b
(then boot to recovery, check TWRP to see you are on slot _b)
Please note: I am sure the a/b switch inside our phone's TWRP will eventually work, but it doesn't currently (as of 17NOV2017); other a/b phones have had the same issue.
Click to expand...
Click to collapse
Great!
Anyway, looking at my a & b backups, it seems to me TWRP a/b switch is already working (they are different...).
---------- Post added at 02:52 PM ---------- Previous post was at 02:50 PM ----------
Some_Donkus said:
What is interesting to me is that flashall flashes both slots, and you can manually choose to flash a specific boot with $flash boot_a or $flash boot_b. With this ability and enough experimenting I'm sure there's a workaround somewhere.
Click to expand...
Click to collapse
I could be wrong but... I've intended from my tests that fastboot without any slot specified flashes only the current one, not both...
---------- Post added at 02:56 PM ---------- Previous post was at 02:52 PM ----------
Some_Donkus said:
...
So... theoretically... if I used the above method to swap into the "other" slot and flash both slots identical, with TWRP and SuperSu... I would be able to swap slots back and forth as I pleased... (even though they would be the same.. and thus making swapping between them.. kind of pointless...) because both would then have the same flag...
If i wanted to modify -ONE- of them, I would have to ensure that it matched the encryption state of the other... correct?
Click to expand...
Click to collapse
Theoretically... yes!
(But don't bet your ass on it... :laugh
Some_Donkus said:
Oh, haha! I totally missed this post in the thread. Herp-A-Derp! Thank you! (I've been peepin' stuff via the XDA labs on my phone and I'm not used to the notifications and such, thanks for the rewind redirect!)
So... theoretically... if I used the above method to swap into the "other" slot and flash both slots identical, with TWRP and SuperSu... I would be able to swap slots back and forth as I pleased... (even though they would be the same.. and thus making swapping between them.. kind of pointless...) because both would then have the same flag...
If i wanted to modify -ONE- of them, I would have to ensure that it matched the encryption state of the other... correct?
Click to expand...
Click to collapse
Once you have successfully booted into the other slot's boot (TWRP), you can see what condition the data partition is in with respect to encryption. If files are encrypted and you already backed up important data (i.e., same data partition shared by both slots, but different systems, boots, etc.), I would recommend formatting data in TWRP. After that, you should do this:
https://forum.xda-developers.com/showpost.php?p=74540731&postcount=21
This way, you will always be able to access data on the data partition, because it won't be encrypted.
(Either system partition can cause data to become encrypted again, so if you have to format data in one and run the above linked command, you would need to do the same in the other boot (TWRP).)
jhofseth said:
Once you have successfully booted into the other slot's boot (TWRP), you can see what condition the data partition is in with respect to encryption. If files are encrypted and you already backed up important data (i.e., same data partition shared by both slots, but different systems, boots, etc.), I would recommend formatting data in TWRP. After that, you should do this:
https://forum.xda-developers.com/showpost.php?p=74540731&postcount=21
This way, you will always be able to access data on the data partition, because it won't be encrypted.
(Either system partition can cause data to become encrypted again, so if you have to format data in one and run the above linked command, you would need to do the same in the other boot (TWRP).)
Click to expand...
Click to collapse
https://plus.google.com/+DeesTroy/posts/i33ygUi7tiu
Hopefully... Encryption won't be a worry
Uzephi said:
https://plus.google.com/+DeesTroy/posts/i33ygUi7tiu
Hopefully... Encryption won't be a worry
Click to expand...
Click to collapse
That all sounds like an insane amount of redundant PitA!!
I really wish I could be of more service in the coding department to help chip away at these types of lockdowns. Unfortunately, my skills are limited to Python and basic C++ console stuff.
This kind of stuff makes me pine for the days when my biggest challenge was trying to modify the UI in Qbasic and installing a power supply without a keyed molex lol.
So, IF we end up at a wall regarding this severe encryption despite the progress made so far, would we be able to patch in security updates "off the cuff" via custom made twrp or fastboot packages?
Uzephi said:
https://plus.google.com/+DeesTroy/posts/i33ygUi7tiu
Hopefully... Encryption won't be a worry
Click to expand...
Click to collapse
Very interesting article about how much Google "love us"...
Please note that at lower level even Motorola did the same on old Griffin (Moto Z)... if you upgraded bootloader (by OTA or by a flashall) during MM->N upgrade, you'll never able to install MM or downgrade bootloader (soft brick in first case and refuse to flash in second one...).
Obviously newer bootloader was't required and gave no benefits on older one...
For this reason on Moto's I ever hint not to flash bootloader even during flashall/debrick...
enetec said:
Very interesting article about how much Google "love us"...
Please note that at lower level even Motorola did the same on old Griffin (Moto Z)... if you upgraded bootloader (by OTA or by a flashall) during MM->N upgrade, you'll never able to install MM or downgrade bootloader (soft brick in first case and refuse to flash in second one...).
Obviously newer bootloader was't required and gave no benefits on older one...
For this reason on Moto's I ever hint not to flash bootloader even during flashall/debrick...
Click to expand...
Click to collapse
Tried adding the code from the pixel 2 because the xl 2 is it's own beast and due to the fact were not running Oreo like there it broke right around 78% and it was due to missing proprietary Google files
First, let me say that this is only an attempt to pull this information out from a lot of different threads that require a bunch of research and a lot of institutional knowledge of Android. The idea of this thread is going from 100% T-Mobile Stock 10.0.8 to Rooted Global Firmware.
Please take the time to read every step carefully. It'll explain a little bit as to the why behind some of the steps. PM me if I've missed anything.
This has been revamped as some of the steps are no longer required. Devices coming from 10.0.6 and below might have to try a different set of steps. Click here for the post with the old instructions
Requirements:
ADB setup and working
Global Fastboot ZIP Grab the latest version (10.0.8 as of 3/20)
For Root:
Magisk Canery apk
Modded-Boot.img From here or make your own pulling your own boot.img and using magisk to create a modded boot.img file
=-=-=-=-=-=-=-=-=-=-=-==-=-=-=-=-=-=-=-=-=-=-==-=-=-=-=-=-=-=-=-=-=-==-=-=-=-=-=-=-=-=-=-=-==-=-=-=-=-=-=-=-=-=-=-==-=-=-=-=-=-=-=-=-=-=-=
This group of instructions are going to walk you through on how to unlock your bootloader. This is the first general step in converting your device into a global device.
1. Either follow the rules via T-Mobile (paid off and 40 days on the network) or visit this thread and get the hook up from our friend (send him some cash, for real I did this and it worked hopefully he keeps up with this for a while!). This will allow you to use the Unlock App to permanently unlock your phone.
2. Open the "Unlock" app that's preinstalled on your phone and click on Permanent Unlock. If you have completed Step One correctly, it'll congratulate you and ask you to reboot your phone.
3. Reboot your phone and Enable Developer Settings. Check out the OEM Unlock button is now able to be switched off. Switch it off.
4. Be sure to also tick USB Debugging.
5. You'll now need to submit a request for an unlock_code.bin (could also be labeled unlock_token.bin) file from OnePlus via this link. It takes a week. Seriously almost down to the second. There's no avoiding this. I've read several people try (myself included) all met with the same fate. Wait. 7 whole days. You'll get an email from OnePlus containing the unlock_code.bin file. Download this file and save it to your ADB folder.
5a. Open CMD (with admin rights) and navigate to your ADB folder. I've heard users try to use Powershell and while it works mostly, ymmv. I stick with CMD and haven't had any issues.
Mine would be--
Code:
cd c:\adb\
6. Reboot your phone into fastboot--
Code:
adb reboot bootloader
Code:
fastboot flash cust-unlock unlock_code.bin
Code:
fastboot oem unlock
This will unlock your bootloader and wipe your device
=-=-=-=-=-=-=-=-=-=-=-==-=-=-=-=-=-=-=-=-=-=-==-=-=-=-=-=-=-=-=-=-=-==-=-=-=-=-=-=-=-=-=-=-==-=-=-=-=-=-=-=-=-=-=-==-=-=-=-=-=-=-=-=-=-=-=
Now that you've unlocked your bootloader, lets get to flashing the Global Rom--
7. Extract the contents of the Global Fastboot Rom zip folder directly into your ADB folder.
a. If you did this correctly your ADB folder will be filled with a bunch of new .img files. Like boot.img8. Open CMD (with admin rights) and navigate to your ADB folder. I've heard users try to use Powershell and while it works mostly, ymmv. I stick with CMD and haven't had any issues.
Mine would be--
Code:
cd c:\adb\
This will also wipe your data, be sure to save anything that you need prior to running the following command.
Code:
flash-all.bat
9. If you've never flashed via fastboot before, this is going to spit a bunch of information to you that might look like garbage. Your phone will boot a few different times including into FastbootD (link for explanation) But it's telling you what it's flashing and how fast it's doing it. There's a common looking error that happens every time you do this. It says "Invalid sparce file format at header magic". This is normal, just ignore it and keep waiting. Once everything settles, the device will reboot by itself. If it doesn't, like bootloops to the bootloader, start over and go back to Step 8 and try again.
10. You've now fully converted to the Global Firmware. Confirm this by going to settings > about phone and look at Build Number. Should say 10.0.8(as of the time of this post).
You're done! Continue on if you want to root your device...
=-=-=-=-=-=-=-=-=-=-=-==-=-=-=-=-=-=-=-=-=-=-==-=-=-=-=-=-=-=-=-=-=-==-=-=-=-=-=-=-=-=-=-=-==-=-=-=-=-=-=-=-=-=-=-==-=-=-=-=-=-=-=-=-=-=-=
If you're interested in root:
11. Boot the device from the modded-boot.img file to give your self temp root. Once this is done, boot the device.
Code:
adb reboot bootloader
fastboot boot modded-boot.img
12. Install Magisk Manager Canary from here
13. Check in the middle of the screen for "advanced options" and make sure Preserve force encryption and preserve avb 2.0/dm-verify are checked.
14. Now look under the first Magisk check and make sure that it's telling you there's an update to "Magisk" and run through that update via direct install.
15. Once that finishes it'll have you reboot the phone.
16. You've now fully converted to the Global Firmware and Rooted. Confirm this by going to settings > about phone and look at Build Number. Should say 10.0.8(as of the time of this post)
=-=-=-=-=-=-=-=-=-=-=-=
Shoutouts will go here soon.
nolimit78 said:
First, let me say that this is only an attempt to pull this information out from a lot of different threads that require a bunch of research and a lot of institutional knowledge of Android. This will be a living first post as I'm currently not able to successfully get rooted. The idea of this thread is going from 100% T-Mobile Stock to Rooted Global Firmware. Once I can replicate and get root stable on my phone I will finalize this post. I will also add in shout outs to where I pulled this information from, both thread post and user, as it was through our group that I was able to piece this together. All this will be updated and make to look nice later.
The reason we flash to Indian and then Global is because if you don't, wifi/data and camera will be broken. I can't explain why it works, it just does.
Ok. Now to the good stuff. Please take the time to read every step carefully. It'll explain a little bit as to some of the why behind the steps. PM me if I've missed anything.
Requirements:
ADB setup and working
Global OTA ZIP (download from here)
Indian Fastboot ROM(download from here)
1. Unlock your bootloader. Either follow the rules via T-Mobile (paid off and 40 days on the network) or visit this thread and get the hook up from our friend (send him some cash, for real I did this and it worked hopefully he keeps up with this for a while!).
2. Move the Global Rom.zip file to the root of your OnePlus7T. It'll save you time later. Do this now or there's a later step where I give you the chance.
2. Open the "Unlock" app that's preinstalled on your phone and click on Permanent Unlock. If you have completed Step One correctly, it'll congratulate you and ask you to reboot your phone.
3. Reboot your phone and Enable Developer Settings. Check out the OEM Unlock button is now able to be switched off. Switch it off.
4. Be sure to also tick USB Debugging.
4. You'll now need to submit a request for an unlock_code.bin file from OnePlus via this link. It takes a week. Seriously almost down to the second. There's no avoiding this. I've read several people try (myself included) all met with the same fate. Wait. 7 whole days. You'll get an email from OnePlus containing the unlock_code.bin file. Download this file and save it to your ADB folder.
5. Reboot your phone into fastboot adb reboot bootloader
6. Extract the Indian Fastboot Rom folder directly into your ADB folder.
a. If you did this correctly your ADB folder will be filled with a bunch of new .img files. Like boot.img
7. Open CMD (with admin rights) and navigate to your ADB folder.
Mine would be-- cd c:\adb\
8. flash-all.bat
9. It will also ask you to wipe data. This is your call. If you followed Step 2, this will wipe out this file and you'll need to replace it once your phone has converted.
9. If you've never flashed via fastboot before, this is going to spit a bunch of information to you that might look like garbage. But it's telling you what it's flashing and how fast it's doing it. There's a common looking error that happens every time you do this. It says []. This is normal, just ignore it. Once everything settles, the device will reboot by itself. If it doesn't, start over and go back to Step 5 and try again.
10. Once the device boots up, you should now be on the Indian build for the OnePlus 7T.
11. You should have already moved the Global OTA to the root of the OnePlus 7t. If you haven't, do so now.
12. Go to settings > system updates and look for the gear on the top right-hand corner. If it's not there, something didn't flash right. Go Back to Step 2 and try again. Click on it and select Local Upgrade
13. Select the Global OTA file and it'll start to flash from within the update app.
14. Once that finishes it'll have you reboot the phone.
15. You've now fully converted to the Global Firmware. Confirm this by going to settings > about phone and look at Build Number. Should say 10.0.6(as of the time of this post, I'll try to update this as I can)
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=--==
This is where we should be able to root. Once I can verify getting this setup and replicate it I will continue with the tutorial. Hopefully, everyone who reads this will find it helpful.
Click to expand...
Click to collapse
I'm having a issue when inflash globel my phone stays on Indian firmware
Are we 100% sure that WiFi/Data/Camera will be broken if you just go straight to Global? Because just this morning I flashed from TMO 10.0.4 to Global 10.0.6 using the fastboot flashable ROM with perfect VoLTE/WiFi/Camera...
Also fully rooted!
Edit: Updated to 10.0.7, kept root via Magisk Manager install to inactive slot.
Reserved for old instructions. Going from 10.0.7 and up the instructions were changed and certain steps weren't needed, like flashing Indian before Global.
Keeping these here just in case someone purchases a phone with older firmware and doesn't want to wait updating to the latest version.
Requirements:
ADB setup and working
Global OTA ZIP (grab the 10.0.6 from here)
Updated 10.0.7 OTA Build from hereas well
Indian Fastboot ROM(grab the latest from here)
Pre-Rooted 10.0.6 boot.img file here
Magisk Canery apk
=-=-=-=-=-=-=-=-=-=-=-==-=-=-=-=-=-=-=-=-=-=-==-=-=-=-=-=-=-=-=-=-=-==-=-=-=-=-=-=-=-=-=-=-==-=-=-=-=-=-=-=-=-=-=-==-=-=-=-=-=-=-=-=-=-=-=
This group of instructions are going to walk you through on how to unlock your bootloader. This is the first general step in converting your device into a global device.
1. Either follow the rules via T-Mobile (paid off and 40 days on the network) or visit this thread and get the hook up from our friend (send him some cash, for real I did this and it worked hopefully he keeps up with this for a while!). This will allow you to use the Unlock App to permanently unlock your phone.
2. Open the "Unlock" app that's preinstalled on your phone and click on Permanent Unlock. If you have completed Step One correctly, it'll congratulate you and ask you to reboot your phone.
3. Reboot your phone and Enable Developer Settings. Check out the OEM Unlock button is now able to be switched off. Switch it off.
4. Be sure to also tick USB Debugging.
5. You'll now need to submit a request for an unlock_code.bin file from OnePlus via this link. It takes a week. Seriously almost down to the second. There's no avoiding this. I've read several people try (myself included) all met with the same fate. Wait. 7 whole days. You'll get an email from OnePlus containing the unlock_code.bin file. Download this file and save it to your ADB folder.
6. Reboot your phone into fastboot--
Code:
adb reboot bootloader
Code:
fastboot oem unlock
This will unlock your bootloader and wipe your device
=-=-=-=-=-=-=-=-=-=-=-==-=-=-=-=-=-=-=-=-=-=-==-=-=-=-=-=-=-=-=-=-=-==-=-=-=-=-=-=-=-=-=-=-==-=-=-=-=-=-=-=-=-=-=-==-=-=-=-=-=-=-=-=-=-=-=
Now that you've unlocked your bootloader, lets get to flashing the Global Rom--
7. Extract the contents of the Indian Fastboot Rom zip folder directly into your ADB folder.
a. If you did this correctly your ADB folder will be filled with a bunch of new .img files. Like boot.img8. Open CMD (with admin rights) and navigate to your ADB folder. I've heard users try to use Powershell and while it works mostly, ymmv. I stick with CMD and haven't had any issues.
Mine would be--
Code:
cd c:\adb\
This will also wipe your data, be sure to save anything that you need prior to running the following command.
Code:
flash-all.bat
10. If you've never flashed via fastboot before, this is going to spit a bunch of information to you that might look like garbage. Your phone will boot a few different times including into FastbootD (link for explanation) But it's telling you what it's flashing and how fast it's doing it. There's a common looking error that happens every time you do this. It says "Invalid sparce file format at header magic". This is normal, just ignore it and keep waiting. Once everything settles, the device will reboot by itself. If it doesn't, like bootloops to the bootloader, start over and go back to Step 5 and try again.
11. Once the device boots up, you should now be on the Indian build for the OnePlus 7T.
12. Be sure to copy the Global OTA to the root storage of your OnePlus 7T. If you haven't, do so now.
13. Reboot the phone and boot the Modded-boot.img file from the bootloader
Code:
adb reboot bootloader
fastboot boot modded-boot.img
14. Once the phone boots up, you should now have temp root. Go to settings > system updates and look for the gear on the top right-hand corner. If it's not there, something didn't flash right. Go Back to Step 2 and try again. Click on it and select Local Upgrade
15. Select the Global OTA file and it'll start to flash from within the update app. Let this finish before proceeding.
16. Install Magisk Manager Canary from here
17. Check in the middle of the screen for "advanced options" and make sure Preserve force encryption and preserve avb 2.0/dm-verify are checked.
18. Now look under the first Magisk check and make sure that it's telling you there's an update to "Magisk" and run through that update via direct install.
19. Once that finishes it'll have you reboot the phone.
20. You've now fully converted to the Global Firmware and Rooted. Confirm this by going to settings > about phone and look at Build Number. Should say 10.0.6(as of the time of this post, I'll try to update this as I can)
If you'd like to update to 10.0.7:
1. Download and move the OTA file for 10.0.7 to the root of your OP7T
2. Go to Settings > System > System Updates and look for the gear in the top right.
3. Select Local upgrade and select the update file for 10.0.7.
4. Let it run through and finish, don't reboot.
5. Open Magisk Manager
6. Update and select direct install to inactive boot partition to update.
7. Once this finishes, reboot and you're now on 10.0.7 rooted.
=-=-=-=-=-=-=-=-=-=-=-=
nolimit78 said:
Yup, tried to be slick by going straight to Global and ran into this problem. Data worked for me but Camera was super unstable and Wifi was the only solid no that I got. Required more research to discover that this issue is avoided by flashing the indian rom first.
Tell me more about this. What steps did you take to do this? I'm thinking that once you flash the global ROM to reboot, and then use the a image-new.img that boots a temp-magisk to then use magisk canary to install magisk on the inactive slot (should be a right?)
Click to expand...
Click to collapse
Hmm I'll watch and see if my Camera is unstable but it seems fine so far.
To root I flashed (not booted) a 10.0.6 Magisk patched boot img (fastboot flash boot patched_boot.img) that someone posted in the "how to patch boot with Magisk" thread and installed Magisk Manager Canary.
I used Oxygen Updater to local update to 10.0.7 (it says 10.3.0 because of a typo from OnePlus, see another thread. It says 10.0.7 in settings) but make sure to download the full 2gb update not the 200 something mb incremental one because it will fail.
Then when the update is done, don't hit reboot, go to Magisk Manager, make sure you're set to the Canary channel (unless you patched the boot img yourself with something else) and install and choose inactive slot. Then you can hit reboot in Magisk.
Perfect, means I was thinking correctly with an extra unneeded reboot. Updated info in OP.
Just now noticed this thread so I'll crosspost my applicable results from the MSM thread https://forum.xda-developers.com/showpost.php?p=81227253&postcount=113
I want to share my experience in case it might help someone else as I was quite confused for a while over the past few weeks trying to get off tmobile slow updates.
I can also confirm jumping straight from tmobile 10.0.4 to global 10.0.6 works. I didn't have the 10.0.7/10.3.0 downloaded and I have slow internet so I can't say if that would work but I have upgraded to it since via oxygen updater.
Basic steps how I got there is, assuming you know how to do stuff like enable dev mode and usb debugging
-sim unlock https://forum.xda-developers.com/oneplus-7t/how-to/t-mobile-free-op7t-sim-unlocking-t4014053
-request bootloader unlock token and wait 7 days https://www.oneplus.com/unlock_token
-unlock bootloader
-get fastboot rom https://forum.xda-developers.com/oneplus-7t/how-to/rom-stock-fastboot-roms-oneplus-7t-t3979213
-use all in one tool to flash flashboot rom https://forum.xda-developers.com/android/software/tool-tool-one-driversunlocktwrpfactory-t3358711
I told the AIO tool I had a oneplus 7 (7T not an option) and did "flash factory images", and chose wipe and reboot to be safe and just waited until the phone came back to factory setup screen
that's it. oxygen updater incremental update failed for 10.0.7/10.3.0 but full worked fine, I've never used oxygen updater until now so idk if that is fairly normal or not. VoLTE works, WiFi calling, etc all seem to be working as far as I can tell (although it seems the global doesn't have the quick select option to disable wifi calling like the tmobile rom did).
I've also now installed Magisk Canary, patched boot img and have certified play store now and google pay is fully functional and I have used camera for mobile banking deposit. Still no issues with wifi, camera, anything
Once converted to Global oos, will it support Dual SIM?
ysfk7 said:
Once converted to Global oos, will it support Dual SIM?
Click to expand...
Click to collapse
Yes it will support dual SIM as long as you have the dual SIM tray.
rgreen83 said:
Just now noticed this thread so I'll crosspost my applicable results from the MSM thread https://forum.xda-developers.com/showpost.php?p=81227253&postcount=113
I want to share my experience in case it might help someone else as I was quite confused for a while over the past few weeks trying to get off tmobile slow updates.
I can also confirm jumping straight from tmobile 10.0.4 to global 10.0.6 works. I didn't have the 10.0.7/10.3.0 downloaded and I have slow internet so I can't say if that would work but I have upgraded to it since via oxygen updater.
Basic steps how I got there is, assuming you know how to do stuff like enable dev mode and usb debugging
-sim unlock https://forum.xda-developers.com/one...cking-t4014053
-request bootloader unlock token and wait 7 days https://www.oneplus.com/unlock_token
-unlock bootloader
-get fastboot rom https://forum.xda-developers.com/one...us-7t-t3979213
-use all in one tool to flash flashboot rom https://forum.xda-developers.com/and...ctory-t3358711
I told the AIO tool I had a oneplus 7 (7T not an option) and did "flash factory images", and chose wipe and reboot to be safe and just waited until the phone came back to factory setup screen
that's it. oxygen updater incremental update failed for 10.0.7/10.3.0 but full worked fine, I've never used oxygen updater until now so idk if that is fairly normal or not. VoLTE works, WiFi calling, etc all seem to be working as far as I can tell (although it seems the global doesn't have the quick select option to disable wifi calling like the tmobile rom did).
I've also now installed Magisk Canary, patched boot img and have certified play store now and google pay is fully functional and I have used camera for mobile banking deposit. Still no issues with wifi, camera, anything
Click to expand...
Click to collapse
FYI link to fastboot rom is broken.
Crappyvate said:
FYI link to fastboot rom is broken.
Click to expand...
Click to collapse
Sorry bout that, crosspost fail
Crappyvate said:
FYI link to fastboot rom is broken.
Click to expand...
Click to collapse
I clicked on it and it worked, but I didn't check through mobile. Can you show me what happens when you try?
There is no link to request unlock file from OnePlus. Also will regular global OTA updates work? Or will I have to manually update every time?
Will this work for McLaren 5g?
I just followed the instructions in post#7 and was able to do this successfully as well (direct Tmobile->Global, without the Indian version flash in between). Note that the phone will reboot sometime in the middle of the flash, do NOT manually go into the phone and reboot yet again, just wait for it to complete.
Is waiting around for OnePlus to send you an unlock token really necessary to unlock the bootloader? I ask this because it's not necessary on the OP7 with the use of the MSM Tool (https://forum.xda-developers.com/oneplus-7-pro/help/how-to-convert-tmobile-op7-to-t3935947) Would this tool work on the OP7T or does it need its own?
tkoreaper said:
Is waiting around for OnePlus to send you an unlock token really necessary to unlock the bootloader? I ask this because it's not necessary on the OP7 with the use of the MSM Tool (https://forum.xda-developers.com/oneplus-7-pro/help/how-to-convert-tmobile-op7-to-t3935947) Would this tool work on the OP7T or does it need its own?
Click to expand...
Click to collapse
Yes, unfortunately the loophole that let this work on the 6T and 7 was corrected for the 7T+
cm0002 said:
Yes, unfortunately the loophole that let this work on the 6T and 7 was corrected for the 7T+
Click to expand...
Click to collapse
i guess thats why i can unlock the bootloader and convert the Tmo 6T without asking the unlock_code.bin from oneplus. thank you kindly for the info
I got the unlock bin today I just flashed via fastboot received message the bootloader is unlocked, but the device status still states locked?
nolimit78 said:
...
4. Reboot your phone and Enable Developer Settings. Check out the OEM Unlock button is now able to be switched off. Switch it off.
...
Click to expand...
Click to collapse
So OEM Unlock button suppose to be OFF or ON?
OxygenOS v10.5.12 just dropped.
Installed and rooted no problem. Now I just have to wait for my my buds to get here.
Change log available? It's not even showing on UK site yet.
spotmark said:
Installed and rooted no problem. Now I just have to wait for my my buds to get here.
Click to expand...
Click to collapse
Awesome!
r3k0 said:
Change log available? It's not even showing on UK site yet.
Click to expand...
Click to collapse
Here's the change log as posted on Oxygen Updater.
System
• Newly adapted OnePlus Buds, easier to take advantage of wireless connection
• Provided a variety of clock styles for you. You can customize on your own. (Go to Settings>Customization>Clock style)
• Optimized the touch experience in game mode to enhance the user experience
• Fixed the issue that the wireless charger base re-started automatically
• Fixed the ARCore failure
• Updated Android Security Patch to 2020.07
• Updated GMS package to 2020.05
• Improved system stability
Network
• Improved the performance and stability of Wi-Fi transfers
• Improved connection stability of mobile network to improve user experience
anyone have the magisk patched .12AA boot.img??
Update available for me, hopefully the AR issue is resolved
Patched 10.5.12.IN11AA boot.img
https://gofile.io/d/dCbFDY
I hope they keep randomizing the updates for EU and US, so we in the EU continue to get the new updates before the US-version does, as we saw here with .12(US) and .11(EU)
How do I update and keep root? when I go to update it says 'root is detected, system will download the entire package and root will be undone'.
r3k0 said:
Change log available? It's not even showing on UK site yet.
Click to expand...
Click to collapse
Its the same as our 10.5.11 IN11BA We are one version number behind, same patch but with a lower number.
AppEx213 said:
How do I update and keep root? when I go to update it says 'root is detected, system will download the entire package and root will be undone'.
Click to expand...
Click to collapse
I just do it the "old fashioned" way.
I download it all, copy the .zip over to the PC so I can extract the boot.img -> transfer it to the phone -> update the phone -> install magisk (if you don't already have it), and then click "install" on magisk, click patch image, pick the boot.img, transfer the file "downloads/magisk_patched.img" to the ADB-folder on your PC -> reboot the phone to fastboot -> open CMD, go to the ADB-folder -> "fastboot flash boot magisk_patched.img" -> "fastboot reboot" -> now you're rooted again
dmbardal said:
I just do it the "old fashioned" way.
I download it all, copy the .zip over to the PC so I can extract the boot.img -> transfer it to the phone -> update the phone -> install magisk (if you don't already have it), and then click "install" on magisk, click patch image, pick the boot.img, transfer the file "downloads/magisk_patched.img" to the ADB-folder on your PC -> reboot the phone to fastboot -> open CMD, go to the ADB-folder -> "fastboot flash boot magisk_patched.img" -> "fastboot reboot" -> now you're rooted again
Click to expand...
Click to collapse
Or just install update DONT reboot, install magisk to inactive slot (after OTA), reboot and your are good to go..
I don't know about you, but with this update on my IN2020 unit, I can't manage to see any remnant of green tint on my screen anymore. Before that, there was still a slight green tint, even with 10.5.11, at very low brightness. What about you? Any improvement?
Still no dual sim
pyry666 said:
Or just install update DONT reboot, install magisk to inactive slot (after OTA), reboot and your are good to go..
Click to expand...
Click to collapse
See, I tried that and I don't see an option to flash it to the inactive slot....
AppEx213 said:
How do I update and keep root? when I go to update it says 'root is detected, system will download the entire package and root will be undone'.
Click to expand...
Click to collapse
Perform the OTA installation but don't reboot, and then...
See awesome instructions towards the end of this thread:
https://forum.xda-developers.com/oneplus-8-pro/how-to/10-5-10-rooted-ota-updating-to-10-5-11-t4130715/post83023399#post83023399
Well everything blue up on me this time. I had successfully updates, preserved Magisk root, then used xXx TWRP installer, and then flashed with Kn kernel flasher to install it again. This had all worked fine before, but this time on rebooting, it would only go into TWRP and not reboot.
I stupidly feflashed the tool with TWRP, but now stuck on fastboot mode.
I hate having to go back to the beginning - so would appreciate any idea.
Yeah...starting to get annoying
polo2883 said:
Still no dual sim
Click to expand...
Click to collapse
Stoked for another update. Im grateful they are working hard to get these issues fixed. Hopefully we'll have dual sim and AOD soon
Hi, as written in the title, I would like to root my phone. I never touch root with xiaomi (the only thing I've done is unlock bootloader)
I usualy root samsung's phone
I want to know if it possible to have my phone rooted with magisk, twrp as custom recovery with android 11
Sorry if my english is bad, sorry if wrong place/category
The best way is to searc already written threat..
Or watch YouTube.
You need to download ADB ,ind ADB folder put oFox or TWRP ,depens what tou want from recovery. in that folder, holding shift+left click open powershell, then type , fastboot flash recovery _name of recovery.img
Fastboot boot name of recovery.img
And that it.
tze_vitamin said:
The best way is to searc already written threat..
Or watch YouTube.
You need to download ADB ,ind ADB folder put oFox or TWRP ,depens what tou want from recovery. in that folder, holding shift+left click open powershell, then type , fastboot flash recovery _name of recovery.img
Fastboot boot name of recovery.img
And that it.
Click to expand...
Click to collapse
Of course I have already searched
If I write here, it is because I did not find some information
Flash twrp, like you say, yes but is twrp for this phone compatible with android 11 or 10 only ?
Most of guide I found say "root ... android 10" or just root without precise the version
That's why I want to be sure
Rooting with Magisk is pretty much always the same, doesn't matter if Samsung or Xiaomi.
1. Download https://androidfilehost.com/?fid=2188818919693773066 (link from https://forum.xda-developers.com/t/...-lite-mi10i-redmi-note-9-pro-5g-beta.4228655/)
2. "fastboot boot twrp_xyz.img" (don't flash custom recovery as internal memory can't be decrypted in TWRP afterwards)
3. install magisk.zip
Works on stock Android 11.
_mysiak_ said:
Rooting with Magisk is pretty much always the same, doesn't matter if Samsung or Xiaomi.
1. Download https://androidfilehost.com/?fid=2188818919693773066 (link from https://forum.xda-developers.com/t/...-lite-mi10i-redmi-note-9-pro-5g-beta.4228655/)
2. "fastboot boot twrp_xyz.img" (don't flash custom recovery as internal memory can't be decrypted in TWRP afterwards)
3. install magisk.zip
Works on stock Android 11.
Click to expand...
Click to collapse
(don't flash custom recovery as internal memory can't be decrypted in TWRP afterwards)
Is it still possible to backup/restore in case of problem ?
No need to reset ?
Xyphoseos said:
(don't flash custom recovery as internal memory can't be decrypted in TWRP afterwards)
Is it still possible to backup/restore in case of problem ?
No need to reset ?
Click to expand...
Click to collapse
Backup most probably yes, I never tried restore so can't confirm. But obviously you will need to "hot boot" TWRP whenever you want to use it, so you must have PC at hand.
_mysiak_ said:
Backup most probably yes, I never tried restore so can't confirm. But obviously you will need to "hot boot" TWRP whenever you want to use it, so you must have PC at hand.
Click to expand...
Click to collapse
Ive read in some guide (that there were not clearly) twrp is flashed, phone reseted and vmbeta disable (or something like that) this make us able to see those crypted data in twrp
Maybe Im wrong
Xyphoseos said:
Ive read in some guide (that there were not clearly) twrp is flashed, phone reseted and vmbeta disable (or something like that) this make us able to see those crypted data in twrp
Maybe Im wrong
Click to expand...
Click to collapse
I don't know about this. I want my phone encrypted, so I boot TWRP after every OTA update to root it again..
_mysiak_ said:
I don't know about this. I want my phone encrypted, so I boot TWRP after every OTA update to root it again..
Click to expand...
Click to collapse
okay, thank you for your help !
Root like this prevent me from ota updates right ?
Xyphoseos said:
okay, thank you for your help !
Root like this prevent me from ota updates right ?
Click to expand...
Click to collapse
For incremental ("small" OTA) update you will need to restore stock images in Magisk.
Full ("big" OTA) update can be installed without any further steps.
In both cases, after a reboot you will have updated system with no root, so you need to reinstall Magisk from TWRP.
What Android you have. I am on A11 and Orangefox working perfect
Hi,
having Android 11
"reboot bootloader" doesn't seem to work on my Sharp.
"reboot sideload" works: is there a version of that "twrp img" that can be sideloaded on Android 11?
( has to be a zip )
petit-lion said:
Hi,
having Android 11
"reboot bootloader" doesn't seem to work on my Sharp.
"reboot sideload" works: is there a version of that "twrp img" that can be sideloaded on Android 11?
( has to be a zip )
Click to expand...
Click to collapse
If "reboot bootloader" is the command line and does not work, do it manually ?
Btw, thank you again @_mysiak_ , everything works like a charm
_mysiak_ said:
Rooting with Magisk is pretty much always the same, doesn't matter if Samsung or Xiaomi.
1. Download https://androidfilehost.com/?fid=2188818919693773066 (link from https://forum.xda-developers.com/t/...-lite-mi10i-redmi-note-9-pro-5g-beta.4228655/)
2. "fastboot boot twrp_xyz.img" (don't flash custom recovery as internal memory can't be decrypted in TWRP afterwards)
3. install magisk.zip
Works on stock Android 11.
Click to expand...
Click to collapse
Xyphoseos said:
If "reboot bootloader" is the command line and does not work, do it manually ?
Click to expand...
Click to collapse
What I mean is "adb reboot bootloader" just reboots, does not go into bootloader.
Manually, the vol-down power goes into "factory reset", there is no other option.
It's a Sharp, and these phones are known not to be very bootloader-tolerant.
Only "adb reboot sideload" works and goes into "sideload" mode, waiting for a ZIP file to be uploaded.
Then, the "sideload" zip must contain a valid signature, and "edify" commands.
That motivated my question:
For Android 11, is there a zip sideloadable of twrp, with a valid signature?
petit-lion said:
What I mean is "adb reboot bootloader" just reboots, does not go into bootloader.
Manually, the vol-down power goes into "factory reset", there is no other option.
It's a Sharp, and these phones are known not to be very bootloader-tolerant.
Only "adb reboot sideload" works and goes into "sideload" mode, waiting for a ZIP file to be uploaded.
Then, the "sideload" zip must contain a valid signature, and "edify" commands.
That motivated my question:
For Android 11, is there a zip sideloadable of twrp, with a valid signature?
Click to expand...
Click to collapse
I dont know, sorry
petit-lion said:
What I mean is "adb reboot bootloader" just reboots, does not go into bootloader.
Manually, the vol-down power goes into "factory reset", there is no other option.
It's a Sharp, and these phones are known not to be very bootloader-tolerant.
Only "adb reboot sideload" works and goes into "sideload" mode, waiting for a ZIP file to be uploaded.
Then, the "sideload" zip must contain a valid signature, and "edify" commands.
That motivated my question:
For Android 11, is there a zip sideloadable of twrp, with a valid signature?
Click to expand...
Click to collapse
Not sure why you discuss Sharp phone in this topic, but nevertheless, "adb sideload" mode is for stock ROM updates/installations. As far as I'm aware, it is not possible to install anything else this way.
_mysiak_ said:
Not sure why you discuss Sharp phone in this topic, but nevertheless, "adb sideload" mode is for stock ROM updates/installations. As far as I'm aware, it is not possible to install anything else this way.
Click to expand...
Click to collapse
Sorry, I saw "root Android 11" and jumped into it.
Desperate to find an access to that damn Sharp.
petit-lion said:
Sorry, I saw "root Android 11" and jumped into it.
Desperate to find an access to that damn Sharp.
Click to expand...
Click to collapse
You will need either unlocked bootloader + device specific custom recovery, or functional exploit which could root the phone. You are most probably out of luck, so buying a phone with good support on XDA might save you some headaches.
_mysiak_ said:
You will need either unlocked bootloader + device specific custom recovery, or functional exploit which could root the phone. You are most probably out of luck, so buying a phone with good support on XDA might save you some headaches.
Click to expand...
Click to collapse
Learned the lesson
But this Sharp Sense 3 was offered to me by a carrier.
It had initially Android 9 Pie on it, and, biiig mistake, let it upgrade itself
(no upgrade until root from now on!)
Anyway, that's an interesting challenge. Had a look at the open-source visible code from Sharp, checked the 'recovery.cpp' part, and tried all the 'reboot' allowed in the code (eg oem-xxx ...).
Saw the "panic" code (Snapdragon 630 has a panic mode), but could not trigger it.
Saw the part from the Google code handling the sideload signature, and this one will be hard to beat!
And, unfortunately the part handling 'bootloader', Sharp cutstomized, is not visible.
To be continued...
I have a mi10t lite with vodafone brand. I would like to have a europe firmware so i can receive the last ota and so on..
is this a way I can do too?
Hi guys I know their are threads how to do this but they are all over the place, If you'd like a complete tutorial, that will get your 2020 MOTO G Stylus phone rooted without any errors let me know.
Edit: It looks like people are interested so here goes. The tutorial below is for the 2020 version I tested on Android 10 on two variants. This method once followed correctly will take no more than 30 min tops. Not sure if this will work on updated versions but you could try at your own risk. If this helped you leave a like, if you have any questions let me know.
prerequisites:
PC (duh lol)
Fully Charged Device
Motorola Account (for bootloader unlock purposes)
adb fastboot installed (take note of your folder location especially the platform-tools folder
motorola drivers (link in step 5 if drivers don't install correctly after connecting phone)
Tutorial:
Unlocking bootloader
1. first step is to unlock bootloader(all data will be erased) for this you will need your unlock key
2. go to settings, about phone build # hit a bunch of times to enable developer options
3. once enabled go to developer option enable OEM unlock, disable automatic update (do not update), and enable USB debugging.
4. while phone is on plug into pc to allow drivers to install, also allow usb debugging when prompted. go to where you have adb installed and go in the platform tools folder (this is where I do everything on my phones without errors) hit shift+right click and choose "open command window here" type in "adb devices" without quotes and check if the device is present.
5. now to test if you have fastboot drivers power off phone, then hold power+volume down to enter fastboot mode, plug phone into your computer and repeat step 4 this time typing "fastboot devices" if your phone shows up move on to next step if not download Motorola drivers and install then repeat this step. You can get the driver here and install https://combofile.com/index.php?a=downloads&b=file&id=3396.
6. once your device is detected its time to unlock bootloader, go to https://motorola-global-portal.custhelp.com/app/standalone/bootloader/unlock-your-device-a sign in and follow the steps, they are simple and straight forward so I won't list them here. Once unlocked restart your phone, set up and proceed to below steps.
Rooting
1. with bootloader unlocked time to get root. download the latest magisk manager (23 I believe) let it install and power off your phone we will use it later. We will be getting the specific boot image for your device through temporary twrp.
2. go to https://forum.xda-developers.com/t/recovery-unofficial-twrp-3-5-0.4155041/ and download TWRP credits to @vache. Place the file in your platform-tools folder.
3. enter fastboot mode (by now it should be second nature) and plug into pc, verify fastboot device connected, by opening command window again in platform-tools folder
4. once verified type the following command without the quotes "fastboot boot twrp-3.5.0-0-rav-sofia.img" be patient, when it boots into twrp, cancel any password creation.
5. go to backup and select storage, choose a sd card, do not decrypt or do anything besides what I'm saying here. it will take you back to the beginning after sd card selected as storage, click backup and select only boot at the very top and creat backup. once done go out to twrp main menu and hit reboot, select "reboot system"
6. now to patch boot, open magisk manager and go to install, it will then give you the option to locate and patch boot.img, however we will be going into twrp backup on your sd card and locate boot.emmc.win (not the other two) once selected hit lets go on Magisk and allow it to patch. your patched boot.img will be in a download folder on your internal memory. Copy that file to your computer and then again move it to platform-tools folder
7. power off device and enter fastboot mode for the final time connect to pc, open command window in platform-tools folder and type the following command without the quotes "fastboot flash boot nameofbootfile.img" hit enter and allow to flash, once completed type "fastboot reboot" your device should now reboot, don't worry if it takes slightly longer than usual.
8. finally go into the magisk manager and let it complete its setup, it should reboot one more time and boom, you have root, remember to use magisk hide, That's it all set. If followed correctly this should only take about 30 min to a hour.
Shucks! I thought this was a tutorial.
zapjb said:
Shucks! I thought this was a tutorial.
Click to expand...
Click to collapse
I got you, updated tutorial up. Let me know if it helps.
If we have updated to Android 11, such as myself, and want to use the tutorial... Couldn't we just BACKUP (which is needed to root anyways), and do a FACTORY SETTINGS RESET to bring our OS back to Android 10?
Killabee0311 said:
If we have updated to Android 11, such as myself, and want to use the tutorial... Couldn't we just BACKUP (which is needed to root anyways), and do a FACTORY SETTINGS RESET to bring our OS back to Android 10?
Click to expand...
Click to collapse
I'm pretty sure a factory reset would restore to 11 not 10. As the 11 update replaced the 10 OS altogether.
Killabee0311 said:
If we have updated to Android 11, such as myself, and want to use the tutorial... Couldn't we just BACKUP (which is needed to root anyways), and do a FACTORY SETTINGS RESET to bring our OS back to Android 10?
Click to expand...
Click to collapse
I'm not sure if a factory reset would take the OS back to 10, you might need to search around for downgrade options. I'd advise anyone not to update to android 11, 10 is great especially with root. I have magisk pass safteynet, and even able to play pokemon go with gps spoof and smali patcher.
kgalv419 said:
I'm not sure if a factory reset would take the OS back to 10, you might need to search around for downgrade options. I'd advise anyone not to update to android 11, 10 is great especially with root. I have magisk pass safteynet, and even able to play pokemon go with gps spoof and smali patcher.
Click to expand...
Click to collapse
I'm on stock and want to flash this rom. I need to start from scratch. I need to unlock the bootloader, I got the email from Motorola months ago, but haven't had time to figure out how to use fastboot. It's been years since I used it. I'm also on Android 11 and I need to find out how to downgrade to Android 10. Any advice is appreciated.
I have an annoying Security Update that keeps popping up saying that I need to restart my device, and that it only takes 90 seconds. I'm afraid that if I restart my device, the update will install and I won't be able to downgrade to Android 10 from 11, and then I 'll be stuck with this stock rom. Can I disable this pop up?
New Version : RPRS31.Q1-56-9-9 Includes Updates of Android Security Patches through 1 October 2021.
I have not turned iff my device or restarted it since the pop up for the update.
EpicSaga said:
I'm on stock and want to flash this rom. I need to start from scratch. I need to unlock the bootloader, I got the email from Motorola months ago, but haven't had time to figure out how to use fastboot. It's been years since I used it. I'm also on Android 11 and I need to find out how to downgrade to Android 10. Any advice is appreciated.
I have an annoying Security Update that keeps popping up saying that I need to restart my device, and that it only takes 90 seconds. I'm afraid that if I restart my device, the update will install and I won't be able to downgrade to Android 10 from 11, and then I 'll be stuck with this stock rom. Can I disable this pop up?
New Version : RPRS31.Q1-56-9-9 Includes Updates of Android Security Patches through 1 October 2021.
I have not turned iff my device or restarted it since the pop up for the update.
Click to expand...
Click to collapse
Ok if you have your unlock code you should still be able to unlock bootloader. However the first thing you need to do is enable your developer options and enable OEM unlock, enable USB debugging and disable automatic updates that should stop updates you can also go on app info when you get the notification and disable notifications for system updates. If you have an unlock bootloader you should be able to root even android 11
kgalv419 said:
Ok if you have your unlock code you should still be able to unlock bootloader. However the first thing you need to do is enable your developer options and enable OEM unlock, enable USB debugging and disable automatic updates that should stop updates you can also go on app info when you get the notification and disable notifications for system updates. If you have an unlock bootloader you should be able to root even android 11
Click to expand...
Click to collapse
Thank you very much. How do I disable automatic updates and how do I go on app info to disable notifications for system updates? Now a message is on the same screen that says that if I don't restart my phone by the 21st, it will automatically update it.
For downgrading to android 10:
1. Grab the moto flash tool from here
2. Grab the a10 firmware from your device here
3. Unzip the moto flash tool and put the firmware zip in the folder called firmware
4. Plug your device in to your pc in bootloader mode
5. Start the moto flash tool and follow the instructions
(Unlocked bootloader required)
EpicSaga said:
Thank you very much. How do I disable automatic updates and how do I go on app info to disable notifications for system updates? Now a message is on the same screen that says that if I don't restart my phone by the 21st, it will automatically update it.
Click to expand...
Click to collapse
Pretty sure theres a setting in developer options to turn off automatic updates.
ph4n70m-404 said:
Pretty sure theres a setting in developer options to turn off automatic updates.
Click to expand...
Click to collapse
Yes, it's off, and it's been turned off, but I still got a message from Motorola that if I don't restart my phone so that the security patch can update, it will restart automatically on the 21st( a few hours from now).
EpicSaga said:
Yes, it's off, and it's been turned off, but I still got a message from Motorola that if I don't restart my phone so that the security patch can update, it will restart automatically on the 21st( a few hours from now).
Click to expand...
Click to collapse
I don't know of any solution to this but you should be able to update and keep magisk if you let it do the ota update then use the magisk manager to flash to the other slot.
ph4n70m-404 said:
Pretty sure theres a setting in developer options to turn off automatic updates.
Click to expand...
Click to collapse
I already turned it off, but I still got the notification for the update.
ph4n70m-404 said:
I don't know of any solution to this but you should be able to update and keep magisk if you let it do the ota update then use the magisk manager to flash to the other slot.
Click to expand...
Click to collapse
I don't have magisk, my phone ia stock. Can I put magisk on my phone without unlocking the bootloader? I need some assistance with unlocking it.
EpicSaga said:
I already turned it off, but I still got the notification for the update.
Click to expand...
Click to collapse
I got a notification again today saying that it will update today if It don't do it manually.
EpicSaga said:
I don't have magisk, my phone ia stock. Can I put magisk on my phone without unlocking the bootloader? I need some assistance with unlocking it.
Click to expand...
Click to collapse
Assuming you have a non Verizon or any other oem that blocks unlocking the bootloader follow the steps from the original post:
(step one makes no sense they wrote it kinda weird)
2. go to settings, about phone build # hit a bunch of times to enable developer options
3. once enabled go to developer option enable OEM unlock, disable automatic update (do not update), and enable USB debugging.
4. while phone is on plug into pc to allow drivers to install, also allow usb debugging when prompted. go to where you have adb installed and go in the platform tools folder (this is where I do everything on my phones without errors) hit shift+right click and choose "open command window here" type in "adb devices" without quotes and check if the device is present.
5. now to test if you have fastboot drivers power off phone, then hold power+volume down to enter fastboot mode, plug phone into your computer and repeat step 4 this time typing "fastboot devices" if your phone shows up move on to next step if not download Motorola drivers and install then repeat this step. You can get the driver here and install https://combofile.com/index.php?a=downloads&b=file&id=3396.
6. once your device is detected its time to unlock bootloader, go to https://motorola-global-portal.custhelp.com/app/standalone/bootloader/unlock-your-device-a sign in and follow the steps, they are simple and straight forward so I won't list them here. Once unlocked restart your phone, set up and proceed to below steps.
EpicSaga said:
I don't have magisk, my phone ia stock. Can I put magisk on my phone without unlocking the bootloader? I need some assistance with unlocking it.
Click to expand...
Click to collapse
you can install magisk manager with bootloader locked but there is no sense in installing it on locked bootloader, because when you unlock your bootloader your devices will be factory reset, if you checked my instructions you will see that magisk manager is needed to patch boot.img that you will get from TWRP backup. You seem a bit green about the whole fastboot process, if that's the case I'd advise you to do a little reading up on adb fastboot, which needs to be installed to unlock your bootloader, if you go in blind you can brick your device and I wouldn't want that.
kgalv419 said:
...I'd advise you to do a little reading up on adb fastboot, which needs to be installed to unlock your bootloader, if you go in blind you can brick your device and I wouldn't want that.
Click to expand...
Click to collapse
Sometimes it's been a couple years between me rooting phones. When I come back to root another phone I read & read & read & read some more here. And I have in case the shtf a back up phone to be safe.
EpicSaga said:
I'm on stock and want to flash this rom. I need to start from scratch. I need to unlock the bootloader, I got the email from Motorola months ago, but haven't had time to figure out how to use fastboot. It's been years since I used it. I'm also on Android 11 and I need to find out how to downgrade to Android 10. Any advice is appreciated.
I have an annoying Security Update that keeps popping up saying that I need to restart my device, and that it only takes 90 seconds. I'm afraid that if I restart my device, the update will install and I won't be able to downgrade to Android 10 from 11, and then I 'll be stuck with this stock rom. Can I disable this pop up?
New Version : RPRS31.Q1-56-9-9 Includes Updates of Android Security Patches through 1 October 2021.
I have not turned iff my device or restarted it since the pop up for the update.
Click to expand...
Click to collapse
Re: bootlock unlock code email
I went on the Lenovo/Motorola website just yesterday and input the long 5-line code from my phone (required) from SDK platform. Once I did this, the website replied that I will receive email with a unique 20-character bootloader unlock code (this is the part you should check again). Instead of getting a code, the email asked that I first "verify my email", so I followed the directions, clicked the link, the link brought me to their website and I was able to verify my account. Once that happened, the page just kinda froze. So I repeated the process and when I clicked the "verify email" button, it brought me again to the website but thus time to my profile page. There was no Bootloader Unlock Code, nor was I emailed the code as assured as I was, as per their website suggests. I repeated the process a 3rd time but the same thing happened. And when I tried to went back #2 + #3 times, I input all the information again, clicked on the "send email" link (where they email you the 20-character code) I never received any additional emails. I only received 1 email (the first time I input this into their website). So, the site will only work 1 time per unique phone (serial). I called customer support and got nowhere! I have Metro by T-Mobile Motorola Moto G Stylus XT2043-4. I hope you see this and please let me know if you are able to unlock or get a email code as promised (or not). And if you have any information on how else to solve this issue, please let me know. I hope this helps & my apologies for being a bearer of bad news. If I solve this issue, I will respond back.