Hey folks,
So somehow when unlocking my bootloader with the unlock_key/code from OnePlus, I switched the ROM from the T-Mobile variant to the stock OnePlus variant. I may have corrupted/wiped one of the two slots and gotten lucky, that was months ago and I've forgotten.
Mostly I wanted to confirm an unlocked bootloader in the event there is a stable and up-to-date ROM made available on this device. It's my primary phone and I don't want to be alpha testing updates, so I'm happy with the stock OnePlus OS.
However, my device won't apply updates. I'm NOT rooted, though the bootloader is unlocked. What are my options for applying updates?
Do I need to re-enable bootloader via adb, which will likely wipe the OS and require re-configuration of all my apps and settings? If I apply root (and wipe-OS), can the root receive updates easily?
Been about two months now without the latest security patch, things could be worse but I definitely want to update!
ANy thoughts are appreciated, thanks!
lifebringer123 said:
Hey folks,
So somehow when unlocking my bootloader with the unlock_key/code from OnePlus, I switched the ROM from the T-Mobile variant to the stock OnePlus variant. I may have corrupted/wiped one of the two slots and gotten lucky, that was months ago and I've forgotten.
Mostly I wanted to confirm an unlocked bootloader in the event there is a stable and up-to-date ROM made available on this device. It's my primary phone and I don't want to be alpha testing updates, so I'm happy with the stock OnePlus OS.
However, my device won't apply updates. I'm NOT rooted, though the bootloader is unlocked. What are my options for applying updates?
Do I need to re-enable bootloader via adb, which will likely wipe the OS and require re-configuration of all my apps and settings? If I apply root (and wipe-OS), can the root receive updates easily?
Been about two months now without the latest security patch, things could be worse but I definitely want to update!
ANy thoughts are appreciated, thanks!
Click to expand...
Click to collapse
If you do a factory reset with the MSM tool you will get the T-Mobile ROM back and it will also relock the bootloader (and of course wipe all your apps and settings). You will definitely be able to get updates that way. I don't know if there is a way to get updates without wiping all of your data.
towardsdawn said:
If you do a factory reset with the MSM tool you will get the T-Mobile ROM back and it will also relock the bootloader (and of course wipe all your apps and settings). You will definitely be able to get updates that way. I don't know if there is a way to get updates without wiping all of your data.
Click to expand...
Click to collapse
OK, thank you! I will give it a try eventually...
Any recommended ROMS that are lightweight but super stable and also regularly updated? Like LineageOS (which I believe is not updated for this phone)...
nothing beats stock in stability period. yes you can update vs stock OTA on unlocked bootloader
You can also update and receive OTA while rooted with magisk, my current method is here:
1) click "try again." click "resume" which may or may not reboot the device.
2) adb reboot fastboot
3) fastboot boot previous_magiskpatched_boot.img
4) find active slot with adb shell /bin/getprop ro.boot.slot_suffix
5) dd
if=/dev/block/bootdevice/by-name/boot_a_or_b of=/sdcard/Download/boot.img to backup stock boot.img
6) direct install magisk, reboot
7) repeat step 5 to backup patched boot.img
8) adb pull sdcard/Download patched and stock.img
towardsdawn said:
You can also update and receive OTA while rooted with magisk, my current method is here:
1) click "try again." click "resume" which may or may not reboot the device.
2) adb reboot fastboot
3) fastboot boot previous_magiskpatched_boot.img
4) find active slot with adb shell /bin/getprop ro.boot.slot_suffix
5) dd
if=/dev/block/bootdevice/by-name/boot_a_or_b of=/sdcard/Download/boot.img to backup stock boot.img
6) direct install magisk, reboot
7) repeat step 5 to backup patched boot.img
8) adb pull sdcard/Download patched and stock.img
Click to expand...
Click to collapse
thanks!
Ytube21 said:
nothing beats stock in stability period. yes you can update vs stock OTA on unlocked bootloader
Click to expand...
Click to collapse
Are you saying that if I re-lock my bootloader, it will NOT wipe my OS/factory reset, and I'll be able to update the OS via OTA updates?
Remember, bootloader is unlocked but I'm on the stock ROM (not the T-Mobile ROM, though this is the physical T-Mobile variant).
lifebringer123 said:
Are you saying that if I re-lock my bootloader, it will NOT wipe my OS/factory reset, and I'll be able to update the OS via OTA updates?
Remember, bootloader is unlocked but I'm on the stock ROM (not the T-Mobile ROM, though this is the physical T-Mobile variant).
Click to expand...
Click to collapse
Hello there, lifebringer123.
I believe Ytube21 made a grammatical error in his response to you. I believe what he intended to imply was that, with an unlocked bootloader, you can install OTA updates on the stock ROM.
Because the phone will be transitioning from a non-assured software integrity state and unprotected personal data condition to a guaranteed software integrity state and protected data condition, relocking the bootloader will result in a factory reset to ensure no trace of a root related process capable of accessing /data.
Since I assume you don't have unlocked firmware, I'm guessing you don't have the "Local upgrade" option in settings (Settings -> System -> System update -> Gear settings icon in top right corner -> Local upgrade), which means you're missing out on the most direct and authentic way of installing OTA updates.
However, I have another idea in mind, which I'm not sure will work, but could if your circumstances allow it. Is it possible to install the most recent OnePlus Nord N200 OTA update after flashing TWRP?
Here's what I'm thinking:
1. Download the most appropriate TWRP image (Current most recent TWRP for OnePlus Nord N200)
2. Boot OnePlus Nord N200 into bootloader (adb reboot bootloader while the device is on, or, while the device is off, hold the volume down and power key for a while, release the power button when the OnePlus logo comes up (but keep pressing the volume down button), go appropriately through the menu (select suitable language, then choose Advanced -> Reboot to fastboot)
3. Ensure that fastboot detects your OnePlus Nord N200 (fastboot devices)
4. Momentarily boot into recovery (fastboot boot NameOfRecoveryHere.img (This will only boot the recovery, not install it)
5. Flash the desired OTA update .zip file using the recovery and reboot
Note: Your build number will be useful for me to point you in the right direction for finding the appropriate .zip for the OTA update (Step 5)
Apart from the way described above, I'm very confident you won't be able to properly apply updates without wiping your phone. I would suggest just backing up your phone (Save anything you want to preserve) to a secure location and then following the procedures mentioned by towardsdawn of utilizing MSM tools to restore the T-Mobile ROM.
If you have any questions or issues, please let me know.
Aselloph said:
Hello there, lifebringer123.
I believe Ytube21 made a grammatical error in his response to you. I believe what he intended to imply was that, with an unlocked bootloader, you can install OTA updates on the stock ROM.
Click to expand...
Click to collapse
The OS notices the OTA updates, but it cannot apply/install them no matter what I do to try.
Aselloph said:
Because the phone will be transitioning from a non-assured software integrity state and unprotected personal data condition to a guaranteed software integrity state and protected data condition, relocking the bootloader will result in a factory reset to ensure no trace of a root related process capable of accessing /data.
Click to expand...
Click to collapse
Makes sense; thanks.
Aselloph said:
Since I assume you don't have unlocked firmware, I'm guessing you don't have the "Local upgrade" option in settings (Settings -> System -> System update -> Gear settings icon in top right corner -> Local upgrade), which means you're missing out on the most direct and authentic way of installing OTA updates.
Click to expand...
Click to collapse
That is correct; I don't have that option. I also no longer have the "T-Mobile" Splash sceen on startup, my assumption since doing this earlier this year was that I may have wiped the t-mobile branded ROM variant, and the phone reverted to the "slot B" stock variant. But I could be wrong. In any case...
Aselloph said:
However, I have another idea in mind, which I'm not sure will work, but could if your circumstances allow it. Is it possible to install the most recent OnePlus Nord N200 OTA update after flashing TWRP?
Here's what I'm thinking:
1. Download the most appropriate TWRP image (Current most recent TWRP for OnePlus Nord N200)
2. Boot OnePlus Nord N200 into bootloader (adb reboot bootloader while the device is on, or, while the device is off, hold the volume down and power key for a while, release the power button when the OnePlus logo comes up (but keep pressing the volume down button), go appropriately through the menu (select suitable language, then choose Advanced -> Reboot to fastboot)
3. Ensure that fastboot detects your OnePlus Nord N200 (fastboot devices)
4. Momentarily boot into recovery (fastboot boot NameOfRecoveryHere.img (This will only boot the recovery, not install it)
5. Flash the desired OTA update .zip file using the recovery and reboot
Note: Your build number will be useful for me to point you in the right direction for finding the appropriate .zip for the OTA update (Step 5)
Apart from the way described above, I'm very confident you won't be able to properly apply updates without wiping your phone. I would suggest just backing up your phone (Save anything you want to preserve) to a secure location and then following the procedures mentioned by towardsdawn of utilizing MSM tools to restore the T-Mobile ROM.
If you have any questions or issues, please let me know.
Click to expand...
Click to collapse
Model DE2118
Build 11.0.1.9.DE18CB
ONE PLUS Nord N200 5G
(dre8t, but unlocked bootloader via unlock_code.bin)
I would give that a whirl if you could point me to the current OTA update .zip package. However, I bookmarked that TWRP thread months ago, but it still hasn't been updated, and I never did get it working correctly. But I'll try it. If it works and the manual OTA update .zip is only monthly/quarterly, the inconvenience is not severe. Still, I'm not using root or any custom ROM at the moment, so I should really go back to a locked bootloader so I can receive OTA updates, and suck up the loss of a few hours of restoring settings/apps...
Again (for all on thread), if there is a solid Custom ROM which regularly gets security updates, please point me to that thread/ROM! The
Thank you so much for your time!
Successful conversion of N200 5G from T-Mo to OEM without MSM tool! (Credit to Summersofar)
Hey there. i'm a new XDA Member myself. i've been mostly stalking these forums for the N200 Ever since people started the root phase and twrp projects for codename HOLI. but i'm here to convert @summersofar's guide in order to make it more...
forum.xda-developers.com
Try re-doing it. First, use MSM tool to return to Tmo, then unlock the bootloader again, then follow that guide.
It should completely fix your broken slots. And yes, my phone is rebranded, and it can apply updates perfectly.
I'm even rooted.
justauserthatusesaphone said:
Successful conversion of N200 5G from T-Mo to OEM without MSM tool! (Credit to Summersofar)
Hey there. i'm a new XDA Member myself. i've been mostly stalking these forums for the N200 Ever since people started the root phase and twrp projects for codename HOLI. but i'm here to convert @summersofar's guide in order to make it more...
forum.xda-developers.com
Try re-doing it. First, use MSM tool to return to Tmo, then unlock the bootloader again, then follow that guide.
It should completely fix your broken slots. And yes, my phone is rebranded, and it can apply updates perfectly.
I'm even rooted.
Click to expand...
Click to collapse
Thanks! When OTA updates end for our OS, in 1-2 years, what will you do? Switch phones, or do you think you have a custom ROM/OS that sounds stable enough?
I'll try the MSM tool, debate rooted or not, then report back...
Thanks again all!
lifebringer123 said:
Thanks! When OTA updates end for our OS, in 1-2 years, what will you do? Switch phones, or do you think you have a custom ROM/OS that sounds stable enough?
I'll try the MSM tool, debate rooted or not, then report back...
Thanks again all!
Click to expand...
Click to collapse
you're welcome, sorry for being late lol
after 2-3 years, ill probably keep this phone and install lineageos or pixel experience (that is, if it gets support)
although by that time, the trade in value is probably 2 dollars so I'll use it if i ever get into android development.
Any word on custom ROMs for this like Lineage OS or Pixel Experience?
Related
Hello
I have a new M10 Pro (BLA-A09) here in the US, and I haven't activated it yet as I remain undecided about using it. The activity in this thread is limited, and I thought that there were more ROMS available. Perhaps I'm wrong, but I see very little activity for this phone. My current phone is an LG V10 which is unrootable, therefore moving to the M10P would be a good change since I can at least root the M10P and remove the bloatware.
I have a bootloader unlock code that I got on the last day! And I am on build 8.0.0.65 (C567).
I've read most of the current threads in this forum and the ROMS/kernels forum, and I remain confused as to what can be done with this phone.
I ask:
1. Can the phone truly be rooted? If yes, what for? To remove bloatware only? Or are there rooms (xirin, etc)?
2. I think that I read that rooting removes the data partition. Is that true? And how does that hurt?
3. I know that I can rebrand the phone with funkyhuawei. Why would I want to do that here in the US?
4. An OTA that follows a root, requires re-rooting the phone after the OTA, right?
Thank you for the help. I am excited about using this very powerful phone, I superficially read some threads before buying it, and I thought that it would be a very rootable and ROMable phone; I am not sure if that is the case.
nabril15 said:
Hello
I have a new M10 Pro (BLA-A09) here in the US, and I haven't activated it yet as I remain undecided about using it. The activity in this thread is limited, and I thought that there were more ROMS available. Perhaps I'm wrong, but I see very little activity for this phone. My current phone is an LG V10 which is unrootable, therefore moving to the M10P would be a good change since I can at least root the M10P and remove the bloatware.
I have a bootloader unlock code that I got on the last day! And I am on build 8.0.0.65 (C567).
I've read most of the current threads in this forum and the ROMS/kernels forum, and I remain confused as to what can be done with this phone.
I ask:
1. Can the phone truly be rooted? If yes, what for? To remove bloatware only? Or are there rooms (xirin, etc)?
2. I think that I read that rooting removes the data partition. Is that true? And how does that hurt?
3. I know that I can rebrand the phone with funkyhuawei. Why would I want to do that here in the US?
4. An OTA that follows a root, requires re-rooting the phone after the OTA, right?
Thank you for the help. I am excited about using this very powerful phone, I superficially read some threads before buying it, and I thought that it would be a very rootable and ROMable phone; I am not sure if that is the case.
Click to expand...
Click to collapse
1: yes. For anything you need root for, really.
Most bloatware can be removed without root, unless you want to start removing system apps. There are a few treble roms available over at the treble forum https://forum.xda-developers.com/project-treble.
Most, if not all, should be compatible. And you have https://openkirin.net/ which are for Huawei phones.
2. It does not. Well, it depends on where you read it. TWRP couldn't decrypt /data before, so you had to Format it and remove the encryption flag in fstab, but that is not needed anymore. (Official TWRP still can't, see download link below)
3. Do not rebrand. A09 is not compatible with L09/L29/AL and you will brick.
Also, if you had used it you would now be bootloader locked. What FH does is that it flashes an included oeminfo that has dualsim enabled. This also changes your IMEI, IMEI2 and SN in fastboot, making your old unlock code invalid. And right now there is no way to get a new one (I'm not sure if DC still works with A09, it doesn't on C432 as of B145.)
4. Yes. As ramdisk is overwritten you have to flash Magisk again (I suggest Magisk as SuperSU is not updated anymore)
Basically, you want to:
Go here to download TWRP: https://forum.xda-developers.com/mate-10/development/huawei-mate-10-pro-twrp-3-2-1-0-t3769904
Magisk: https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
Or Beta Magisk, can be buggy: https://forum.xda-developers.com/apps/magisk/beta-magisk-v13-0-0980cb6-t3618589
Backup your sdcard contents.
Go to Settings -> System -> About Phone -> Tap Build number until Developer options is enabled
Go to Settings -> System -> Developer options
Enable OEM Unlocking
Reboot to fastboot.
Unlock bootloader using: fastboot oem unlock ##unlock_code##
Use Volume key to move to 'Yes' on phone, then power to accept.
Wait for format to finish, setup phone again.
Transfer magisk zip to sdcard.
Reboot to fastboot again
Flash TWRP using: fastboot flash recovery_ramdisk twrp_bla_alp_0.7.img
Reboot to recovery by holding Power and Volume Up.
Enter your Pin
Now flash Magisk
Finished.
ante0 said:
1: yes. For anything you need root for, really.
Finished.
Click to expand...
Click to collapse
Thanks a lot ante0. I really appreciate it.
1. You pasted
Enable OEM Unlocking
Reboot to fastboot.
How do I reboot into fastboot?
2. So, can I use twrp? I really like it and have been using it for years on other phones and tablets.
3. I will use magisk and not SU, right?
4. I've been using the phone on wifi only and without a sim card, so it's not active on ATT here in the US. In the twrp thread I see that for OTA I need the following:
Flash with TWRP Magisk Uninstaller
Flash in Fastboot Mode recovery_ramdisk.img (=EMUI Recovery) + ramdisk.img + kernel.img
In Systemupdate settings (dot menu) use "Download and install current full package" (=FullOTA-MF, some GB) instead of only OTA (some MB)
Wow. How complicated, but I'm sure it's not that difficult. Although, in that same thread, I also read that some people have installed the OTA without removing magisk.
5. Kirin or treble roms? I can't see screenshots of either, so how do we decide?
Thanks again
nabril15 said:
Thanks a lot ante0. I really appreciate it.
1. You pasted
Enable OEM Unlocking
Reboot to fastboot.
How do I reboot into fastboot?
2. So, can I use twrp? I really like it and have been using it for years on other phones and tablets.
3. I will use magisk and not SU, right?
4. I've been using the phone on wifi only and without a sim card, so it's not active on ATT here in the US. In the twrp thread I see that for OTA I need the following:
Flash with TWRP Magisk Uninstaller
Flash in Fastboot Mode recovery_ramdisk.img (=EMUI Recovery) + ramdisk.img + kernel.img
In Systemupdate settings (dot menu) use "Download and install current full package" (=FullOTA-MF, some GB) instead of only OTA (some MB)
Wow. How complicated, but I'm sure it's not that difficult. Although, in that same thread, I also read that some people have installed the OTA without removing magisk.
5. Kirin or treble roms? I can't see screenshots of either, so how do we decide?
Thanks again
Click to expand...
Click to collapse
1. Either you can use adb: adb reboot bootloader
Or power off phone then hold volume down and plug in usb
Or plug in usb, reboot, hold volume down.
2. Yes, it's fully functional.
3. Magisk is preferable. Mainly because it's being updated, and can pass Safetynet if any of your apps need it to pass.
4. You *should* only need to flash recovery_ramdisk (I guess you can use the one from the last update on http://pro-teammt.ru/firmware-database/?firmware_model=BLA-A09&firmware_page=0)
To get recovery_ramdisk you need to download update.zip from pro-teammt.ru, then extract update.app from it.
Download Huawei Update Extractor https://forum.xda-developers.com/showthread.php?t=2433454
Extract Huawei Update Extractor zip and run the exe. Go to settings in the program and disable header check.
Next open up update.app in it, rightclick on recovery_ramdisk and click on Extract Selected.
Now you can flash that image using fastboot (fastboot flash recovery_ramdisk RECOVERY_RAMDISK.img)
This will restore stock recovery and will let you flash OTA directly from System Update.
The reason you have to restore stock recovery is because phone will reboot to recovery to update, but if you have TWRP flashed it won't update at all
You would have to flash back both TWRP and Magisk after update finishes.
(You can actually flash FULLOTA Update.zip directly in TWRP if you use HuRUpdater, but seeing as the US Mate 10 Pro rarely get any updates it's not really needed.)
5. Kirin is treble, they are built for Huawei devices rather than being just for treble enabled devices.
I've only really used Lineage, but moved back to stock as TWRP does not work with Treble roms. It should work once we get 8.1 firmware though.
ante0 said:
5. Kirin is treble, they are built for Huawei devices rather than being just for treble enabled devices.
I've only really used Lineage, but moved back to stock as TWRP does not work with Treble roms. It should work once we get 8.1 firmware though.
Click to expand...
Click to collapse
thanks again Ante
Would you say that it makes sense for me to, when I put the sim in the phone and use it (if I decide to), to attempt an OTA update first, and then do root and whatever else? My phone's build is from December 2017, so I assume that ATT will have some sort of update for the phone.
You mentioned that the US Mate10 rarely gets updates. So, then how would any of us get any updates , security or otherwise? How will we get 8.1, for example? Are you in the US, btw? What ROM are you using on this phone?
ante0 said:
5. Kirin is treble, they are built for Huawei devices rather than being just for treble enabled devices.
I've only really used Lineage, but moved back to stock as TWRP does not work with Treble roms. It should work once we get 8.1 firmware though.
Click to expand...
Click to collapse
thanks again Ante
Would you say that it makes sense for me to, when I put the sim in the phone and use it (if I decide to), to attempt an OTA update first, and then do root and whatever else? My phone's build is from December 2017, so I assume that ATT will have some sort of update for the phone.
You mentioned that the US Mate10 rarely gets updates. So, then how would any of us get any updates , security or otherwise? How will we get 8.1, for example? Are you in the US, btw? I assume that you have the device; what ROM are you using?
nabril15 said:
thanks again Ante
Would you say that it makes sense for me to, when I put the sim in the phone and use it (if I decide to), to attempt an OTA update first, and then do root and whatever else? My phone's build is from December 2017, so I assume that ATT will have some sort of update for the phone.
You mentioned that the US Mate10 rarely gets updates. So, then how would any of us get any updates , security or otherwise? How will we get 8.1, for example? Are you in the US, btw? I assume that you have the device; what ROM are you using?
Click to expand...
Click to collapse
I do not have a US Mate 10 Pro (A09), but the global (L29) on C432.
You can read a bit in this thread about the US version updates:
https://forum.xda-developers.com/mate-10/development/huawei-mate-10-pro-bla-a09-c567-usa-t3775258
I guess the lack of updates is due to the problems Huawei has with the US government. :/
You do get updates, but there seem to be a few months between them.
I would update and then root. There is an update in that thread which is fairly new, but it has not been indexed by Firmware Finder (pro-teammt.ru). You could flash it using TWRP and HuRUpdater as I don't think you have Nocheck recovery for A09.
FOR MOTO G7 PLUS ONLY!!!
Hello, everyone.
I created a .bat file "executable " For those who want to flash the stock rom on your Moto G7 Plus.
Just put it in the stock Rom folder along with the fastboot files and run the file.
For those who want the file, just download it by the following link or download the file that is on the thread.
http://www.mediafire.com/file/q836uaerr17pn0f/Flash_ROM_G7%252B.zip/file
Could you share where to get the Stock ROM fein?
---------- Post added at 11:13 PM ---------- Previous post was at 10:25 PM ----------
Tried the same sequence with a Stock ROM last week, but didn't achieve to get back to original ROM. I always get the prompt in the initial boot, that a different OS is installed than the original. This has the consequence that I cannot upgrade wit OTA anymore. And there is an upgrade already available (Jan security patch)
moto g7 G7........
any one have a flash rom.bat stock rom for moto g7.......
Which stock rom did you flash on your Moto g7 plus?
Where can I find the stock rom?
Nes.
NesNol said:
Where can I find the stock rom?
Nes.
Click to expand...
Click to collapse
Didn't you just find it yesterday on the telegram group?
What was the problem that you asked again here today?
Latest Stock ROM RETAIL at that link is the one we have all been using.
You'll need to download it to a computer, unzip it in a folder with the fastboot/ADB files, then fastboot flash it with phone attached in bootloader mode.
NesNol said:
Where can I find the stock rom?
Nes.
Click to expand...
Click to collapse
You have a model of the XT1965-3 smartphone and region of the software is reteu? Then this your last firmware.
"Your device has loaded a different operating system."
baikal0912 said:
You have a model of the XT1965-3 smartphone and region of the software is reteu? Then this your … .
Click to expand...
Click to collapse
Thank you very much!
I guess that the software channel was reteu.
A second moto g7 phone I bought - and is unmodified - says "software channel: reteu".
The information on the package of my phone says XT1965-3.
I flashed this image already, the result is a 'working' system except for the message at the start "Your device has loaded a different operating system." .
NesNol said:
Thank you very much!
I guess that the software channel was reteu.
A second moto g7 phone I bought - and is unmodified - says "software channel: reteu".
The information on the package of my phone says XT1965-3.
I flashed this image already, the result is a 'working' system except for the message at the start "Your device has loaded a different operating system." .
Click to expand...
Click to collapse
This will get rid of that message we all got too:
[Bootlogo] Modded Bootlogo from unlocked bootloader
The new RETEU stock version was just updated in last few days, before that not available and you could have used the RETAIL channel that I mentioned above, it worked fine for several users on RETEU channel.
Dahenjo said:
This will get rid of that message we all got too:
The new RETEU stock version was just updated in last few days, before that not available and you could have used the RETAIL channel that I mentioned above, it worked fine for several users on RETEU channel.
Click to expand...
Click to collapse
Get rid of the message?
Does that also mean that OTAs will work? That banking apps will not complain about the integrity of the system?
Thanks!
NesNol said:
Get rid of the message?
Click to expand...
Click to collapse
Yes, you said: except for the message at the start "Your device has loaded a different operating system."
After unlocking bootloader there is some message like this on starting device, keep in mind we all got these too and everything is fine but we like to cover it up with a different bootlogo, just looks better that is its only purpose. This message is because you also upgraded the firmware, meaning it's not really a different OS but only a different version of your correct OS.
Does that also mean that OTAs will work? That banking apps will not complain about the integrity of the system?
Click to expand...
Click to collapse
For G7 Plus we are not getting the OTAs properly after unlocking or rooting, I was originally rooted on PPW29.98-28 and repeatedly got the notifications of upgrading to 29.98-66-2 but it kept failing, the only way to stop it was freezing the Moto Update Process using Titanium Backup. So my only remaining option to upgrade was to fastboot flash the full firmware, as you just did, it wipes your data but gets you to the same place.
With future updates we may be able to capture them and then a dev can make them into a TWRP flashable zip with no wiping of internal data. We had that on G5 Plus which was a nice thing and they are still doing that. But until that might happen the best we can do is the same for now - when your channel has an update just get it from lolinet (these are all official stock firmwares there) and fastboot flash after backing up your data.
Usually it is more from the rooting (if you did that too) that may mess up your banking or other apps, but in Magisk there are settings that may work on that, you'll just have to try and see but there are mixed results. My choice is to not use banking apps on my devices anyway even if not unlocked or rooted, I just do it from home on a computer that I won't forget and leave out in public somewhere. :crying:
Dahenjo said:
Yes, you said: except for the message at the start "Your device has loaded a different operating system."
…
…
Click to expand...
Click to collapse
Hi,
thank you very much for your elaborate answer!
I will come back on it soon.
Nes
Dahenjo said:
Yes, you said: except for the message at the start "Your device has loaded a different operating system."
After unlocking bootloader there is some message like this on starting device, keep in mind we all got these too and everything is fine but we like to cover it up with a different bootlogo, just looks better that is its only purpose. This message is because you also upgraded the firmware, meaning it's not really a different OS but only a different version of your correct OS.
For G7 Plus we are not getting the OTAs properly after unlocking or rooting, I was originally rooted on PPW29.98-28 and repeatedly got the notifications of upgrading to 29.98-66-2 but it kept failing, the only way to stop it was freezing the Moto Update Process using Titanium Backup. So my only remaining option to upgrade was to fastboot flash the full firmware, as you just did, it wipes your data but gets you to the same place.
With future updates we may be able to capture them and then a dev can make them into a TWRP flashable zip with no wiping of internal data. We had that on G5 Plus which was a nice thing and they are still doing that. But until that might happen the best we can do is the same for now - when your channel has an update just get it from lolinet (these are all official stock firmwares there) and fastboot flash after backing up your data.
Usually it is more from the rooting (if you did that too) that may mess up your banking or other apps, but in Magisk there are settings that may work on that, you'll just have to try and see but there are mixed results. My choice is to not use banking apps on my devices anyway even if not unlocked or rooted, I just do it from home on a computer that I won't forget and leave out in public somewhere. :crying:
Click to expand...
Click to collapse
So you expect that in future my phone will be OK again? And receive OTAs while having Magisk installed.
I tried indeed to Magisk my phone, as I did with my old OnePlus One.
Which leads to TWRP, but then I discovered that the recovery has disappeared on this Moto!?
Then I was lost, and read about A/B and treble(?).
Concerning the banking applications: Even if I handle the banking transactions on my Mac, I still need the banking app on my phone for authentication.
Which is also true for accessing my medical data (GP, hospitals, etc), insurance companies, taxes, etc.
Last question: Is there a full description of how to magisk my phone?
Dahenjo said:
Yes, you said: except for the message at the start "Your device has loaded a different operating system."
…
…
…
…
Click to expand...
Click to collapse
I have replied to this messages twice.
None has arrived?!
Nes
---------- Post added at 01:34 PM ---------- Previous post was at 01:33 PM ----------
Dahenjo said:
Yes, you said: except for the message at the start "Your device has loaded a different operating system."
…
…
…
…
Click to expand...
Click to collapse
I have replied to this message twice.
None has arrived?!
Nes
NesNol said:
So you expect that in future my phone will be OK again? And receive OTAs while having Magisk installed.
I tried indeed to Magisk my phone, as I did with my old OnePlus One.
Which leads to TWRP, but then I discovered that the recovery has disappeared on this Moto!?
Then I was lost, and read about A/B and treble(?).
Concerning the banking applications: Even if I handle the banking transactions on my Mac, I still need the banking app on my phone for authentication.
Which is also true for accessing my medical data (GP, hospitals, etc), insurance companies, taxes, etc.
Last question: Is there a full description of how to magisk my phone?
Click to expand...
Click to collapse
Sorry not to reply yet, I sometimes have other things going on besides my phone. Also I thought I gave you a good answer on the situation, based on what I know as just another user (not a dev, not with Moto).
Yes, there have been changes since your last phone, it was the same for me. So it's good to find out as much as possible before deciding to unlock & root again, because the results may not be like before. We used to unlock and flash TWRP directly but we can't do that now or maybe brick the phone. It is always the risk when choosing not to remain fully stock/locked/etc as when you bought it, and with that is a responsibility to do the research first and not just expect other users to tell you every step.
So I don't know if things will change, but for now we can't get OTAs anymore after unlocking. For me I didn't mind and I am willing to upgrade manually if that let's me work with the device the way I like with root & using custom ROMs etc. I didn't plan to ever go back to how I bought it and don't need banking apps or other types that rooting might mess up. For others that may not be the case so they must learn the situation then decide for themselves.
As for installing Magisk, now we have TWRP working enough to just put the Magisk zip on your SD card and install it in TWRP. Before we had a functional TWRP we had another method by installing Magisk Manager and using it to patch the boot.img then fastboot flash that, but it's not needed anymore since TWRP, just do it the old way now.
Flashing the roms from lolinet, in my case ( RETEU[/URL) is a complete reset of the phone, I assume.
To flash, these steps should be right:
Copying the firmware to sdcard.
Boot in TWRP
Flashing the lolinet firmware.
Delete Dalvik Cache.
Should TWRP and Magisk be reinstalled immedeately after this procedure? Or renew the developer mode, reinstall twrp and magisk?
Woif said:
Flashing the roms from lolinet, in my case RETEU is a complete reset of the phone, I assume.
To flash, these steps should be right:
Copying the firmware to sdcard.
Boot in TWRP
Flashing the lolinet firmware.
Delete Dalvik Cache.
Should TWRP and Magisk be reinstalled immedeately after this procedure? Or renew the developer mode, reinstall twrp and magisk?
Click to expand...
Click to collapse
It won't work to flash full firmware in TWRP, so far the only way is using fastboot with phone connected to a computer in bootloader (unlocked) mode. Unzip firmware into your fastboot/ADB folder and also the batch file available in this thread, then run the batch file.
Yes this will reset/wipe your phone (except for SD) so backup your data first, and it will be like when you first bought it. You can reinstall TWRP and then Magisk, but boot to system first and set things up including enabling USB debugging setting in developer options again.
I am going to try and update now as the notifications are much too annoying.
Moto G7 Plus - lake Stock rom / firmware download here
NesNol said:
Where can I find the stock rom?
Nes.
Click to expand...
Click to collapse
Moto G7 Plus - lake
Download the Moto G7 Plus - lake stock firmware according to the Country/region/retail/carrier for example US Retail > T-Mobile, Verizon or Amazon, and everything is flashed through fastboot mode
XT1965-2 > https://boycracked.com/2019/02/11/official-motorola-moto-g7-plus-xt1965-2-stock-rom/
XT1965-3 > https://boycracked.com/2019/02/11/official-motorola-moto-g7-plus-xt1965-3-stock-rom/
XT1965-4 > https://boycracked.com/2019/02/11/official-motorola-moto-g7-plus-xt1965-4-stock-rom/
XT1965-6 > https://boycracked.com/2019/07/26/official-motorola-moto-g7-plus-xt1965-6-lake_retcn-stock-rom/
XT1965-9 > https://boycracked.com/2019/07/26/official-motorola-moto-g7-plus-xt1965-9-lake-stock-rom/
XT1965-T > https://boycracked.com/2019/07/26/o...-g7-plus-xt1965-t-lake-us-t-mobile-stock-rom/
Remove the line
'fastboot erase userdata'
from the flashROM.bat file and it won't factory reset. It will act like an upgrade.
Sent from my Moto Z (2) using XDA Labs
vickbuitenzorg said:
Moto G7 Plus - lake
Download the Moto G7 Plus - lake stock firmware according to the Country/region/retail/carrier for example US Retail > T-Mobile, Verizon or Amazon, and everything is flashed through fastboot mode
Click to expand...
Click to collapse
Can I use a different retail code than current stock? My phone is XT1965-2, PPW29.98-28, RETLA. The system reminders are all in Spanish. Could I update to PPW29.98-66, EEGB (UK English) without a problem?
Also, if this is possible, could I update by removing the 'fastboot erase userdata' line from the BAT file, or, due to the language change, would I need to leave that line and do a factory reset?
Hi. So I wanted to put together a little write-up on how to root the T-Mobile McLaren 5G variant, at least how I rooted mine, as there doesn't seem to be anything about this yet. I was actually able to root my device last night successfully, so I hope this guide helps others go through the process.
**WARNING** Unlocking your bootloader will render your phone unable to take OTA updates! This is a newly discovered problem that hopefully will be fixed soon. But currently, unlocking the bootloader will wipe your data and also a reserve.img needed for the OTA updates. Proceed with caution!
*I do not take ANY credit for this work. I am simply gathering data from various sources into one single reference guide*
*Credit is due to HolyChickenGuy and dstryrwiz mostly, as I gathered most of the data from these members. Also, topjohnwu of course for Magisk.*
So, anyhow, with this version of the OnePlus Pro 7T being carrier-locked, you must of course follow different procedures than a typical unlocked phone. And because OnePlus thinks they are special somehow, you also have to obtain an unlock code for the bootloader. :laugh:
Steps that I followed:
1. Obtain SIM unlock status via T-Mobile. In order to do this, I simply just asked a T-Mobile employee via Twitter if they could provide me a permanent unlock. And without any issues, they were very kind to do so....even after day 2 of owning the phone. And on the EIP, it's not paid off.
2. After getting them to add your IMEI to the unlock list, go to the system settings --> WiFi & internet --> SIM & network section. There will be an option called "Network Unlock" at the very bottom under the 'Advanced' section. Click that and then go through the prompts. You want to choose "Permanent Unlock". Then, if T-Mobile made on their promise, it should ask to reboot...after which the 'OEM unlocking' option under the Developer Options will no longer be grayed out. Woohoo!
3. After obtaining successful SIM unlock, now you have to submit a form to OnePlus to obtain the actual unlock.bin file to get the bootloader unlocked, generated from a unique 64 character code you will obtain in the next step.
Ensure that USB Debugging is turned ON. In fact, make sure it's always on during this entire procedure, because it's required. Enter fastboot mode via holding the power and volume DOWN buttons during boot up. Or easiest way is to simply soft reboot with the "Advanced reboot" option enabled from the Developer Options. Once in fastboot mode, enter the following command to obtain this 64 character code...fastboot oem get_unlock_codeThis will spit out that 64 character code. Now go to this page, sign in, and fill out the form to submit for the .bin file.NOTE: This takes at LEAST 7 days to get the .bin file. For whatever reason...it must be an automated system. I tried contacting them twice, but they wouldn't budge and told me I had to wait. LOL. And it seriously took EXACTLY 7 days and like 12 minutes for the email to arrive.
4. So after you have the "key" to finally unlock this darn phone, enter fastboot mode again and enter the following commands...
fastboot flash cust-unlock "%path\to\unlock_code.bin%"fastboot oem unlock <<-- This step will ERASE everything on your phone. Most people know this, but I have to say it. Internal storage will be wiped too. :good:
Finally, the phone is unlocked. Now we can root it.
*I used various information from different forum postings...and some previous knowledge of course. Again, I don't take credit for any of this. I'm just following instructions.
5. Download the unofficial TWRP .img file for the OnePlus 7T Pro from here. To be honest, I am not even sure if using TWRP for this part is really necessary, but somehow I came to that conclusion. LOL. This process worked for me, so yeah. Anyhow, enter fastboot mode again and boot to TWRP (do NOT flash it!) by entering the following...
fastboot boot "%path\to\twrp-3.3.1-5-hotdog-unified-mauronofrio.img%"Now in TWRP, enter the following commands to extract your stock boot.img file...
adb shell dd if=/dev/block/bootdevice/by-name/boot of=boot.imgadb pull /boot.imgThis will copy your boot.img file to wherever adb is running on your computer.
6. Take that boot.img file and copy it over to your internal SD on your phone. Boot your phone up as normal, and go grab Magisk Manager from Git here. Open up Magisk Manager, expand the "Advanced Settings" option, and check the "Preserve force encryption" and "Preserve AVB 2.0/dm-verity". Select the "Install" button from the regular Magisk option and choose "Select and Patch a File ". Find your boot.img file and Magisk Manager will created a patched .img file. Copy this new .img file from your phone over to your PC.
7. Enter fastboot mode again. Now just boot from this newly patched .img file by entering the following...
fastboot boot "%path\to\magisk_patched.img%"
8. Final step. And hopefully your phone boots up.
*If not, and you're stuck in a boot loop...you might need to make the A or B partition active. To do this, while back in fastboot mode, enter either command (most likely B)...
fastboot --set-active=afastboot --set-active=bAgain, hopefully the phone just booted up normally without having to do that. Now in your phone, open up Magisk Manager again and simply choose the same Install option, but instead select "Direct Install". Magisk will now flash that .img file, ultimately granting permanent root privileges.
Reboot and enjoy!!
***Here is a good write up on adb and how to get it running on your PC....https://www.xda-developers.com/install-adb-windows-macos-linux/***
worked like a charm, now all we need it global firmware. any idea on getting twrp installed?
which device did you select from the OnePlus token unlock? it doesnt have an option for 7t pro mclaren, only:
OnePlus 6t
OnePlus 7 pro
OnePlus 7t
OnePlus 7t (5g)
TapRooted said:
which device did you select from the OnePlus token unlock? it doesnt have an option for 7t pro mclaren, only:
OnePlus 6t
OnePlus 7 pro
OnePlus 7t
OnePlus 7t (5g)
Click to expand...
Click to collapse
The 5G one.
Bildo41383 said:
worked like a charm, now all we need it global firmware. any idea on getting twrp installed?
Click to expand...
Click to collapse
Great! Yeah I wish. TWRP doesn't work yet even just booting it. You can't mount system and it won't decrypt. You can use it with a decrypted system, but I think it still won't mount the system partition, so there's really no point.
js042507 said:
Great! Yeah I wish. TWRP doesn't work yet even just booting it. You can't mount system and it won't decrypt. You can use it with a decrypted system, but I think it still won't mount the system partition, so there's really no point.
Click to expand...
Click to collapse
Good to know, I was going to decrypt my phone just but there is no point of doing this if I can't use TWRP =/ ...
stock and magisk patched 5G McLaren boot images
OnePlus 7T Pro 5G McLaren
2 boot images (zipped with ZArchiver app), one is stock and the other patched with latest available Magisk.
4.14.117-perf+
#1 Wed Dec 4 20:44:37 CST 2019
Android security patch level
November 1, 2019
As mentioned, booting the unzipped Magisk patched boot image requires an unlocked bootloader.
I've tried getting my phone permanently unlocked with 2 different reps.
They both gave me the same answer, need this phone to be on the network for 40 days before they're willing to assist me any further.
Curious to know what you've said to get them to assist you so early.
Was hoping there's a workaround for this, but there doesn't appear to be one.
https://forum.xda-developers.com/oneplus-7t/how-to/t-mobile-free-op7t-sim-unlocking-t4014053
There is. Works for the 5G.
LLStarks said:
https://forum.xda-developers.com/oneplus-7t/how-to/t-mobile-free-op7t-sim-unlocking-t4014053
There is. Works for the 5G.
Click to expand...
Click to collapse
Yep, this guy unlocked mine pretty quick.
incinandseril said:
I've tried getting my phone permanently unlocked with 2 different reps.
They both gave me the same answer, need this phone to be on the network for 40 days before they're willing to assist me any further.
Curious to know what you've said to get them to assist you so early.
Was hoping there's a workaround for this, but there doesn't appear to be one.
Click to expand...
Click to collapse
Yeah, like I stated before, I simply asked them via Twitter DM. No questions asked. I told her that I wanted to unlock my phone for rooting, etc...and she obliged without any issues. I don't know. Try again maybe. Or use the other method people have posted.
Edit: This is literally what I said...
"Hi. I just recently purchased the new OnePlus 7t McLaren phone this past weekend, and I am definitely loving it. However, I noticed that I am unable to unlock my device. This is always something I do, so I can run certain tasks from my phone. Is there anyway somebody could please send me a permanent unlock code?? I would very much appreciate it!!!"
What's crazy is the fact that the person I spoke with on Twitter said that she won't do it because I was honest about wanting it unlocked for rooting purposes.
"It's super important that we set the right expectations. To protect our customers, T-Mobile does not support rooting (or un-rooting) Android devices.We never advise customers to root a device for any reason. Once a device is rooted, it is treated as a 3rd Party Device, meaning we are unable to troubleshoot if there are issues later on - this would also cause the warranty on the device to be voided.
If the device meets the unlock requirements (found here: https://t.co/ypU2LH9DIX) we can definitely assist with unlocking it, however we do not advise/cannot assist with rooting the device. I hope that clears things up a bit, but please let me know if you have any other questions."
I guess you lucked out with the person that helped you out.
I've messaged the guy from the other thread in hopes of a response about being able to assist me.
incinandseril said:
What's crazy is the fact that the person I spoke with on Twitter said that she won't do it because I was honest about wanting it unlocked for rooting purposes.
"It's super important that we set the right expectations. To protect our customers, T-Mobile does not support rooting (or un-rooting) Android devices.We never advise customers to root a device for any reason. Once a device is rooted, it is treated as a 3rd Party Device, meaning we are unable to troubleshoot if there are issues later on - this would also cause the warranty on the device to be voided.
If the device meets the unlock requirements (found here: https://t.co/ypU2LH9DIX) we can definitely assist with unlocking it, however we do not advise/cannot assist with rooting the device. I hope that clears things up a bit, but please let me know if you have any other questions."
I guess you lucked out with the person that helped you out.
I've messaged the guy from the other thread in hopes of a response about being able to assist me.
Click to expand...
Click to collapse
I spoke with someone in the TMo app, and I told them I needed my phone unlocked because I use my phone when leaving the country for work and it's important to be able to use it. He had no problem unlocking it. I did the same thing unlocking the 6T.
Has anyone tried setting up Gcam with App Systemizer? Or is that too risky at the moment?
LLStarks said:
Has anyone tried setting up Gcam with App Systemizer? Or is that too risky at the moment?
Click to expand...
Click to collapse
I did just a couple days ago and it's SO worth it. No issues at all either. I can even switch between all 3 lenses without any problems. The portrait mode is night and day with the stock camera. If you have questions about the process, let me know.
js042507 said:
I did just a couple days ago and it's SO worth it. No issues at all either. I can even switch between all 3 lenses without any problems. The portrait mode is night and day with the stock camera. If you have questions about the process, let me know.
Click to expand...
Click to collapse
I would like to get this setup as well ?
As long as it's idiot-proof, I'm in. My main concern for this device at the moment is rescue methods. I'm hoping nothing should require more than reflashing stock boot if things go wrong. But here we are dealing with Magisk modules. If a module goes haywire and starts causing bootloops, is disabling the module in TWRP possible over adb if we can't decrypt the partitions? Would a factory reset using either TWRP or stock recovery be the only way out? Or do we just reflash stock boot?
incinandseril said:
I've tried getting my phone permanently unlocked with 2 different reps.
They both gave me the same answer, need this phone to be on the network for 40 days before they're willing to assist me any further.
Curious to know what you've said to get them to assist you so early.
Was hoping there's a workaround for this, but there doesn't appear to be one.
Click to expand...
Click to collapse
I told them I was traveling for the holidays. They had me pay $75 on the phone (2 EIP payments) then unlocked it for me.
Do I need to do both "unlock_code.bin%" and "fastboot oem unlock" at the same time? or can I just do the unlock_code.bin now and the oem unlock sometime in the future when I'm ready to unlock the bootloader?
justthefacts said:
Do I need to do both "unlock_code.bin%" and "fastboot oem unlock" at the same time? or can I just do the unlock_code.bin now and the oem unlock sometime in the future when I'm ready to unlock the bootloader?
Click to expand...
Click to collapse
You have to run the flash command using the .bin file first...then it will let you run fastboot oem unlock. They are separate commands. And yes, you could run the unlock command later. But I think you'd have to do the .bin command again when you're ready. I'm not sure to be honest.
Check your OnePlus updater.
mingkee said:
Check your OnePlus updater.
Click to expand...
Click to collapse
Yes, A-12 has been released for the N200, but it may screw up your phone. I bought three of the unlocked US market 5g N200s due to the 3g phase out. Yesterday two of them updated to A-12 and now neither of them will work for voice /mms/sms. The phones detect a SIM installed but will not access the mobile network at all. I'm using Consumer Cellular which in turn uses At&T towers. Nothing I've tried makes any difference, can't even place a call on my brand new phones. OnePlus tech support is useless, their solution is send the devices to them for "repair" after their update broke my phones. After chatting with their rep I have 0% confidence they will actually do anything except keep my phone for a month or so and send it back in the same condition. According to their tech, no roll back tool exists for the unlocked variant.
Scragge said:
Yes, A-12 has been released for the N200, but it may screw up your phone. I bought three of the unlocked US market 5g N200s due to the 3g phase out. Yesterday two of them updated to A-12 and now neither of them will work for voice /mms/sms. The phones detect a SIM installed but will not access the mobile network at all. I'm using Consumer Cellular which in turn uses At&T towers. Nothing I've tried makes any difference, can't even place a call on my brand new phones. OnePlus tech support is useless, their solution is send the devices to them for "repair" after their update broke my phones. After chatting with their rep I have 0% confidence they will actually do anything except keep my phone for a month or so and send it back in the same condition. According to their tech, no roll back tool exists for the unlocked variant.
Click to expand...
Click to collapse
S build based on Color OS and even the font changed.
I think I can deal with mine, but the most important of all, there's no player error on rooted N200 with S
Scragge said:
Yes, A-12 has been released for the N200, but it may screw up your phone. I bought three of the unlocked US market 5g N200s due to the 3g phase out. Yesterday two of them updated to A-12 and now neither of them will work for voice /mms/sms. The phones detect a SIM installed but will not access the mobile network at all. I'm using Consumer Cellular which in turn uses At&T towers. Nothing I've tried makes any difference, can't even place a call on my brand new phones. OnePlus tech support is useless, their solution is send the devices to them for "repair" after their update broke my phones. After chatting with their rep I have 0% confidence they will actually do anything except keep my phone for a month or so and send it back in the same condition. According to their tech, no roll back tool exists for the unlocked variant.
Click to expand...
Click to collapse
THANK YOU for posting this!! My mom purchased an N200 for the exact same reason and after the A-12 update she's having the same issues with her device. All her voice, sms, and mms transmissions go through Cricket wireless (which also uses AT&T network) She contacted OnePlus customer service and they said they'd get back to her within 48 hours. It's now been 48 hours but with it being a weekend, she's hoping to hear back from them by Monday. She went to the Cricket store yesterday and they cleaned and tried a new SIM card to see if that might fix the issue but it didn't.
While it doesn't sound like there's any fix available yet, it's helpful knowing that this issue is affecting someone else using the AT&T carrier network. Hopefully between OnePlus and the AT&T wireless carriers they'll figure out a solution sooner rather than later.
Best of luck with your devices.
The12thJuror said:
THANK YOU for posting this!! My mom purchased an N200 for the exact same reason and after the A-12 update she's having the same issues with her device. All her voice, sms, and mms transmissions go through Cricket wireless (which also uses AT&T network) She contacted OnePlus customer service and they said they'd get back to her within 48 hours. It's now been 48 hours but with it being a weekend, she's hoping to hear back from them by Monday. She went to the Cricket store yesterday and they cleaned and tried a new SIM card to see if that might fix the issue but it didn't.
While it doesn't sound like there's any fix available yet, it's helpful knowing that this issue is affecting someone else using the AT&T carrier network. Hopefully between OnePlus and the AT&T wireless carriers they'll figure out a solution sooner rather than later.
Best of luck with your devices.
Click to expand...
Click to collapse
Yeah, I called OP three times got the same promise from OPs customer service and they never got back with me. I've never dealt with a less enthusiastic company when dealing with a serious product defect. The tech support people at first acted like the didn't believe me when I described the problem. Then once I had (I think) convinced them the problem was real, their response was like "oh well, too bad, so sad". OP offered no solutions or even ideas of what to try to do to fix the problem.
Do they test anything before pushing out an update?
I had a two day window left for returning the devices for a refund so now they're gone, and I'm gone as an OP customer, I can't just do without a phone while they fumble around trying to figure out the details for some (maybe) upcoming patch.
Good devices, terrible customer service. Never settle, nope, never again.
Scragge said:
According to their tech, no roll back tool exists for the unlocked variant.
Click to expand...
Click to collapse
Try this
OnePlus Community
Introducing our new OnePlus Community experience, with a completely revamped structure, built from the ground-up.
forums.oneplus.com
For those of you who want to downgrade from 12 to 11, use fastboot enhanced/payload dumper, boot fastbootd, delete all of the "my_" partitions, flash android 11 ROM zip (payload.bin button). Reboot bootloader, use the command fastboot -w to initiate a factory reset, reboot recovery and wipe data (this fixes mismatching metadata/userdata partitions) reboot device and voila you're on Android 11 again. Confirmed on my converted TMobile variant.
Also T-Mobile variant got official A12 OTA with the same C.15 build number.
And AT&T doesn't play nice with OnePlus, their new sim cards will not let you use a OnePlus device at all because they are unsupported.
Travisholt92 said:
For those of you who want to downgrade from 12 to 11, use fastboot enhanced/payload dumper, boot fastbootd, delete all of the "my_" partitions, flash android 11 ROM zip (payload.bin button). Reboot bootloader, use the command fastboot -w to initiate a factory reset, reboot recovery and wipe data (this fixes mismatching metadata/userdata partitions) reboot device and voila you're on Android 11 again. Confirmed on my converted TMobile variant.
Also T-Mobile variant got official A12 OTA with the same C.15 build number.
And AT&T doesn't play nice with OnePlus, their new sim cards will not let you use a OnePlus device at all because they are unsupported.
Click to expand...
Click to collapse
Do you know where to download the A12(or at least the latest A11 update so I can update to A12 via OTA) stock firmware/update or could you upload it for the T-MO(metro) variant or show how to update OTA even when I unroot both slots the OTA still fails
Tyreethetruth said:
Do you know where to download the A12 stock firmware/update or could you upload it for the T-MO(metro) variant or show how to update OTA even when I unroot both slots the OTA still fails
Click to expand...
Click to collapse
I'll get the link scraped today. To fix OTA you have to reflash the stock build to restore avb (android verified boot / vbmeta verification). Without this being restored you can't flash OTA's using the normal methods. But once I get a link to the T-Mobile/metro update, you can use fastboot enhanced to manually upgrade like I did. I'll make a tutorial for the manual upgrade/downgrade process. I first have to downgrade from OxygenOS 12 to 11, then use the MSMtool to restore stock T-Mobile software. Easy stuff
Travisholt92 said:
I'll get the link scraped today. To fix OTA you have to reflash the stock build to restore avb (android verified boot / vbmeta verification). Without this being restored you can't flash OTA's using the normal methods. But once I get a link to the T-Mobile/metro update, you can use fastboot enhanced to manually upgrade like I did. I'll make a tutorial for the manual upgrade/downgrade process. I first have to downgrade from OxygenOS 12 to 11, then use the MSMtool to restore stock T-Mobile software. Easy stuff
Click to expand...
Click to collapse
Thank you! I been stuck on the same update like 4-5 updates ago
On this build (metro/TMobile version converted. I can't keep android auto connected. I went into developer options and selected the default to transfer files/ android auto and all the other options but it just connects for a few and then disconnected and says device unsupported.
Rooted device and using a alpine iLX-w650
Tyreethetruth said:
Thank you! I been stuck on the same update like 4-5 updates ago
Click to expand...
Click to collapse
The link to the download is literally a https link in the logcat when downloading the OTA. In case you're wondering how to manually download the zip onto a computer, that is how to get the link. If anyone else beats me to sharing the link it would save me from having to downgrade to get the link for the T-Mobile variant myself
"adb logcat > logcat.txt"
Travisholt92 said:
The link to the download is literally a https link in the logcat when downloading the OTA. In case you're wondering how to manually download the zip onto a computer, that is how to get the link. If anyone else beats me to sharing the link it would save me from having to downgrade to get the link for the T-Mobile variant myself
"adb logcat > logcat.txt"
Click to expand...
Click to collapse
So I get on computer and go on bootloader and type "adb logcat"?
Negative, while booted and after you start to download the android 12 OTA you can run the adb command to get the link while the OS is running.
https://android.googleapis.com/packages/ota-api/package/7cd89efc84e6db817ed16b59b0af3120521ab323.zip
(Shout out to @lzgmc )
I dirty flashed this (DE2118 T-Mobile/Metro) build over the leaked unlocked variant (DE2117) OxygenOS 12 build most are running and did not have to factory reset after flashing with Fastboot Enhanced.
My TMobile variant is now running the T-Mobile firmware. No downgrade required for that.
Downgrade process is download the android 11 build from OnePlus, boot fastbootd, use fastboot enhanced to delete all of the "my_" partitions, flash "payload bin" (full android 11 ota zip from OnePlus), make sure to tick ignore unknown partitions. After that is done shut the phone down and boot to fastboot/bootloader using the key combo, and flash the same payload again with ignore unknown partitions ticked. This will update the partitions that were inaccessible in fastbootd (such as modem). After this you will have to use a terminal with adb/fastboot to run "fastboot -w" this will wipe metadata(encryption key for userdata) and userdata. Reboot to recovery and perform factory reset there as well. After that you should be good to reboot to OxygenOS 11. To return to stock T-Mobile after that just use msmtool
Travisholt92 said:
Negative, while booted and after you start to download the android 12 OTA you can run the adb command to get the link while the OS is running.
https://android.googleapis.com/packages/ota-api/package/7cd89efc84e6db817ed16b59b0af3120521ab323.zip
(Shout out to @lzgmc )
I dirty flashed this (DE2118 T-Mobile/Metro) build over the leaked unlocked variant (DE2117) OxygenOS 12 build most are running and did not have to factory reset after flashing with Fastboot Enhanced.
My TMobile variant is now running the T-Mobile firmware. No downgrade required for that.
Downgrade process is download the android 11 build from OnePlus, boot fastbootd, use fastboot enhanced to delete all of the "my_" partitions, flash "payload bin" (full android 11 ota zip from OnePlus), make sure to tick ignore unknown partitions. After that is done shut the phone down and boot to fastboot/bootloader using the key combo, and flash the same payload again with ignore unknown partitions ticked. This will update the partitions that were inaccessible in fastbootd (such as modem). After this you will have to use a terminal with adb/fastboot to run "fastboot -w" this will wipe metadata(encryption key for userdata) and userdata. Reboot to recovery and perform factory reset there as well. After that you should be good to reboot to OxygenOS 11. To return to stock T-Mobile after that just use msmtool
Click to expand...
Click to collapse
Alright cool thanks for the download so just go to twrp/orangefox and install it or do I get on pc and flash it via adb? Does it have to only be fastboot enhanced?
Tyreethetruth said:
Alright cool thanks for the download so just go to twrp/orangefox and install it or do I get on pc and flash it via adb? Does it have to only be fastboot enhanced?
Click to expand...
Click to collapse
PC and flash via fastbootd then again in fastboot after fastbootd. Fastboot enhanced is the easiest way to do it, otherwise you will need to fix custom recovery to support android 12 or use command line tools to unpack the oneplus ota file to manually flash each partition.
Travisholt92 said:
PC and flash via fastbootd then again in fastboot after fastbootd. Fastboot enhanced is the easiest way to do it, otherwise you will need to fix custom recovery to support android 12 or use command line tools to unpack the oneplus ota file to manually flash each partition.
Click to expand...
Click to collapse
Gotcha, how do I go to fastbootd and fastboot? Its confusing me which one is which
Tyreethetruth said:
Gotcha, how do I go to fastbootd and fastboot? Its confusing me which one is which
Click to expand...
Click to collapse
fastboot = bootloader
Fastbootd has access to more critical partitions and can be accessed by the command "fastboot reboot fastboot" at the bootloader or by hitting the "reboot to fastbootd" button in fastboot enhanced. Make sure to flash it in fastbootd BEFORE flashing it again in fastboot
Travisholt92 said:
fastboot = bootloader
Fastbootd has access to more critical partitions and can be accessed by the command "fastboot reboot fastboot" at the bootloader or by hitting the "reboot to fastbootd" button in fastboot enhanced. Make sure to flash it in fastbootd BEFORE flashing it again in fastboot
Click to expand...
Click to collapse
Gotcha, one last thing how do I flash using fastboot enhance? Idk what to pick to flash the A12 OTA
EDIT: Nvm I extracted the update and found the payload
Magisk patched boot.img for this release: https://drive.google.com/file/d/1A2x8YbnnO6SJq-R-1rdZZ18CU673Z2-Y/view?usp=sharing
Lineage installation on N200 REQUIRES that you are running Android 11 or phone will soft loop after installing the Lineage boot.img
If you are updated to Android 12 firmware and want to install Lineage, you MUST downgrade first to:
DE2117 OEM Android 11 FINAL OTA
WARNING: This WILL erase all user data.
1. Place the firmware .zip file in the user root of internal phone storage.
2. Sideload OnePlus firmware Downgrade Tool on phone and use tool to flash the Android 11 firmware.
There is an Emergency Firmware install tool that OnePlus posted to the OP forum that does NOT check root status when the need to downgrade back to A11 was first acknowledged due to modem issue with first A12 OTA release.
This file was removed in a few days when they posted the official Downgrade tool replaced it.
I have used this tool to upgrade DE2117 C_16 to DE2117 C_17 while rooted and the built in upgrade tool failed at 37%.
Nice, first thanks for the hard work you're putting in. Second, is there an advantage to converting first to DE2117 then installing lineage as opposed to just installing lineage from DE2118 that you know of? I know in the other post you answered my other question stating that the Lineage will install on either so I wasn't sure if I'd get any benefit from starting over and converting my DE2118. TIA
Link575 said:
Nice, first thanks for the hard work you're putting in. Second, is there an advantage to converting first to DE2117 then installing lineage as opposed to just installing lineage from DE2118 that you know of? I know in the other post you answered my other question stating that the Lineage will install on either so I wasn't sure if I'd get any benefit from starting over and converting my DE2118. TIA
Click to expand...
Click to collapse
Lineage is using own kernel and boot.img on A11 so in the short run it is not going too make any difference, but when Lineage moves forward to A12 the OEM Firmware has newer drivers and is updated sooner, has more OEM features and bugfixes as well as no carrier bloatware.
It is possible that OP will neuter the Carrier firmware with an OTA update to prevent cross flashing device away from the Carrier rom in the next OTA update by preventing fastbootd from flashing the us oem from a carrier phone.
They have already removed fastboot boot command to boot a boot image without flashing it for test before you flash and to allow Magisk to make a backup of the original boot.img before adding Magisk.
I would convert NOW, before they decide to slam the door on this ability with a future OTA that will not allow you to downgrade and prevent this as they are under contract with the carriers to not allow this to be done.
Ok, thank you for the explanation. Guess I'll back everything up and convert it.
scanman0 said:
Lineage installation on N200 REQUIRES that you are running Android 11 or phone will soft loop after installing the Lineage boot.img
If you are updated to Android 12 firmware and want to install Lineage, you MUST downgrade first to:
DE2117 OEM Android 11 FINAL OTA
WARNING: This WILL erase all user data.
1. Place the firmware .zip file in the user root of internal phone storage.
2. Sideload OnePlus firmware Downgrade Tool on phone and use tool to flash the Android 11 firmware.
There is an Emergency Firmware install tool that OnePlus posted to the OP forum that does NOT check root status when the need to downgrade back to A11 was first acknowledged due to modem issue with first A12 OTA release.
This file was removed in a few days when they posted the official Downgrade tool replaced it.
I have used this tool to upgrade DE2117 C_16 to DE2117 C_17 while rooted and the built in upgrade tool failed at 37%.
Click to expand...
Click to collapse
This worked perfectly after following your convert guide and upgrading to 12. Downgraded back to 11 so I could install lineageOS. Thanks again!
This reddit post has a link to an English version of the downgrade apk which makes it a little easier.
keeps saying verification failed
weirdfate said:
keeps saying verification failed
Click to expand...
Click to collapse
Did you remove root (Restore boot.img) and then factory reset?
You will loose all data doing this anyway.
I m trying as well .. but stuck with verification failed message just as scanman0 I m on stock android12 no root if anyone know how to fix it ... please assit
I just downgraded. Make sure you remove root via magisk. Then proceed to rollback to Android 11. Everything worked fine. I'll install lineage tonight when I get home.
radekmazur said:
I just downgraded. Make sure you remove root via magisk. Then proceed to rollback to Android 11. Everything worked fine. I'll install lineage tonight when I get home.
Click to expand...
Click to collapse
I did not have to remove root. I used the version posted that does not check for root but maybe there's a different reason.
Does the downgrade apk have to be sideloaded via ADB?
T3CHN0T33N said:
Does the downgrade apk have to be sideloaded via ADB?
Click to expand...
Click to collapse
Just place apk in phones working directory, same path where your downloads folder is. Then install from there like any other apk and run. I also kept the FW file in the same directory but I'm not sure if that was necessary.
So, just to confirm, I press "local install" and select the firmware zip and it closes? Is the tool supposed to do anything else or am I good to flash LineageOS?
T3CHN0T33N said:
So, just to confirm, I press "local install" and select the firmware zip and it closes? Is the tool supposed to do anything else or am I good to flash LineageOS?
Click to expand...
Click to collapse
Ummm if I remember correctly hit local install and then it will prompt to point towards which FW to use. After you hit it, it will go back to the previous screen, I think verify and unpack it, then install it. Mine did appear like it was doing nothing after picking the FW and so I picked again which screwed things up so just wait after picking, it should start.
After its done it will give a message saying to restart phone I think for it to take effect, then after you restart it should ask to wipe phone, then restart again and you'd be in A11 presumably. Once in A11 your good to follow the normal procedure to install Lineage. This is all from memory though so I MAY have missed something but I don't think I did.
Link575 said:
Ummm if I remember correctly hit local install and then it will prompt to point towards which FW to use. After you hit it, it will go back to the previous screen, I think verify and unpack it, then install it. Mine did appear like it was doing nothing after picking the FW and so I picked again which screwed things up so just wait after picking, it should start.
After its done it will give a message saying to restart phone I think for it to take effect, then after you restart it should ask to wipe phone, then restart again and you'd be in A11 presumably. Once in A11 your good to follow the normal procedure to install Lineage. This is all from memory though so I MAY have missed something but I don't think I did.
Click to expand...
Click to collapse
When you say "screwed things up" what do you mean? How did it effect the install?
T3CHN0T33N said:
When you say "screwed things up" what do you mean? How did it effect the install?
Click to expand...
Click to collapse
Nothing major, caused the UI to glitch out and made it seem like the process was stuck at 81% but when I closed the app and tried to do it again it jumped to 100 and said to restart the device.
I've downgraded a second time (I'm very indecisive on which OS I want to use) and that one went as expected since I knew to give it a second to start doing its thing.
Link575 said:
Nothing major, caused the UI to glitch out and made it seem like the process was stuck at 81% but when I closed the app and tried to do it again it jumped to 100 and said to restart the device.
I've downgraded a second time (I'm very indecisive on which OS I want to use) and that one went as expected since I knew to give it a second to start doing its thing.
Click to expand...
Click to collapse
Weird, for me it just closes the app and does nothing, both the official and emergency ones. I even tried adding it to magisk's deny-list.
But I just restored the boot image via magisk (didn't restart) and it works now...
scanman0 said:
Did you remove root (Restore boot.img) and then factory reset?
You will loose all data doing this anyway.
Click to expand...
Click to collapse
Yes I factory restored the phone and tried again. Still fails every time
Has anybody had any luck figuring out the verification failed message? I too have tried both the official and emergency apps, of course I can't read the actual message in what I presume is Chinese, but it doesn't do anything and the other version says verification failed. Have not rooted. Kind of at a loss right now and all I want to do is install Lineage! I've already got my unlock token from OnePlus, but my understanding is that the phone still needs to be on A11 before installling Lineage.