Hey XDA community, two weeks ago I purchased a Moto X40 from Aliexpress and it finally arrived yesterday. After going through some posts here, I successfully ported the Chinese ROM (retcn) to the European version (reteu). There might be easier and faster methods, but I'm sharing the one that worked for me.
Working features:
Unlock
NFC Payment
5G
OTA Update
Not yet tested:
Banking apps
Issues
- VPN, but you can check this comment for a fix
https://www.reddit.com/r/motorola/comments/zo38xu/_/j1u5t9l
Here's the step-by-step guide:
Ensure you have the latest version of fastboot installed.
Download the Motorola USB drivers: https://en-us.support.motorola.com/app/answers/detail/a_id/88481/~/where-can-i-download-the-usb-drivers-for-my-device?
Download the reteu ROM: https://mirrors.lolinet.com/firmware/motorola/rtwo/official/RETEU/
While the ROM is downloading, enable Developer mode and OEM Unlock on your device.
Follow the official Motorola bootloader unlock guide: https://motorola-global-portal.custhelp.com/app/standalone/bootloader/unlock-your-device-a
After unlocking the bootloader, extract the ROM file and return to fastboot mode.
Change to reteu by entering "fastboot oem config carrier reteu".
Download and install MotoFlashPro: https://forum.xda-developers.com/t/utility-motoflashpro.4252201/. Choose the flashfile.xml from the extracted ROM folder, and your phone will be flashed.
When the welcome screen appears, go back to fastboot mode and relock the bootloader using "fastboot oem lock".
That's it! I'm now enjoying the EU ROM on my Moto X40. I'll update this post after I activate 5G on my SIM, test banking apps, and check for any OTA updates (the latest security patch for this ROM is from February 2023).
I hope this helps some of you out there!
Cheers!
EDIT: 5G works!
EDIT 19/05: OTA Update received
GigogoHK said:
Hey XDA community, two weeks ago I purchased a Moto X40 from Aliexpress and it finally arrived yesterday. After going through some posts here, I successfully ported the Chinese ROM (retcn) to the European version (reteu). There might be easier and faster methods, but I'm sharing the one that worked for me.
Working features:
Unlock
NFC Payment
Not yet tested:
5G
OTA Updates
Banking apps
Here's the step-by-step guide:
Ensure you have the latest version of fastboot installed.
Download the Motorola USB drivers: https://en-us.support.motorola.com/app/answers/detail/a_id/88481/~/where-can-i-download-the-usb-drivers-for-my-device?
Download the reteu ROM: https://mirrors.lolinet.com/firmware/motorola/rtwo/official/RETEU/
While the ROM is downloading, enable Developer mode and OEM Unlock on your device.
Follow the official Motorola bootloader unlock guide: https://motorola-global-portal.custhelp.com/app/standalone/bootloader/unlock-your-device-a
After unlocking the bootloader, extract the ROM file and return to fastboot mode.
Change to reteu by entering "fastboot oem config carrier reteu".
Download and install MotoFlashPro: https://forum.xda-developers.com/t/utility-motoflashpro.4252201/. Choose the flashfile.xml from the extracted ROM folder, and your phone will be flashed.
When the welcome screen appears, go back to fastboot mode and relock the bootloader using "fastboot oem lock".
That's it! I'm now enjoying the EU ROM on my Moto X40. I'll update this post after I activate 5G on my SIM, test banking apps, and check for any OTA updates (the latest security patch for this ROM is from February 2023).
I hope this helps some of you out there!
Cheers!
Click to expand...
Click to collapse
There's a thread on the X30 Pro forum where someone confirmed banking + 5G works after converting to EU Model. So we're just waiting to see if OTA is working and if you can enable OEM Unlocking after relock. The guide is very helpful!
thank you guide.if this all working i am ready to buy x40，hope you can update this post.
GigogoHK said:
Hey XDA community, two weeks ago I purchased a Moto X40 from Aliexpress and it finally arrived yesterday. After going through some posts here, I successfully ported the Chinese ROM (retcn) to the European version (reteu). There might be easier and faster methods, but I'm sharing the one that worked for me.
Working features:
Unlock
NFC Payment
Not yet tested:
5G
OTA Updates
Banking apps
Here's the step-by-step guide:
Ensure you have the latest version of fastboot installed.
Download the Motorola USB drivers: https://en-us.support.motorola.com/app/answers/detail/a_id/88481/~/where-can-i-download-the-usb-drivers-for-my-device?
Download the reteu ROM: https://mirrors.lolinet.com/firmware/motorola/rtwo/official/RETEU/
While the ROM is downloading, enable Developer mode and OEM Unlock on your device.
Follow the official Motorola bootloader unlock guide: https://motorola-global-portal.custhelp.com/app/standalone/bootloader/unlock-your-device-a
After unlocking the bootloader, extract the ROM file and return to fastboot mode.
Change to reteu by entering "fastboot oem config carrier reteu".
Download and install MotoFlashPro: https://forum.xda-developers.com/t/utility-motoflashpro.4252201/. Choose the flashfile.xml from the extracted ROM folder, and your phone will be flashed.
When the welcome screen appears, go back to fastboot mode and relock the bootloader using "fastboot oem lock".
That's it! I'm now enjoying the EU ROM on my Moto X40. I'll update this post after I activate 5G on my SIM, test banking apps, and check for any OTA updates (the latest security patch for this ROM is from February 2023).
I hope this helps some of you out there!
Cheers!
Click to expand...
Click to collapse
Yup, can confirm EU ROM is working great with my 12/512GB Moto X40
Magisk works and SafetyNet passes as well
I tried 5G today and I get 200mbps, definetly an improvement over my previous Snapdragon 888
GigogoHK said:
Hey XDA community, two weeks ago I purchased a Moto X40 from Aliexpress and it finally arrived yesterday. After going through some posts here, I successfully ported the Chinese ROM (retcn) to the European version (reteu). There might be easier and faster methods, but I'm sharing the one that worked for me.
Working features:
Unlock
NFC Payment
5G
Not yet tested:
OTA Updates
Banking apps
Here's the step-by-step guide:
Ensure you have the latest version of fastboot installed.
Download the Motorola USB drivers: https://en-us.support.motorola.com/app/answers/detail/a_id/88481/~/where-can-i-download-the-usb-drivers-for-my-device?
Download the reteu ROM: https://mirrors.lolinet.com/firmware/motorola/rtwo/official/RETEU/
While the ROM is downloading, enable Developer mode and OEM Unlock on your device.
Follow the official Motorola bootloader unlock guide: https://motorola-global-portal.custhelp.com/app/standalone/bootloader/unlock-your-device-a
After unlocking the bootloader, extract the ROM file and return to fastboot mode.
Change to reteu by entering "fastboot oem config carrier reteu".
Download and install MotoFlashPro: https://forum.xda-developers.com/t/utility-motoflashpro.4252201/. Choose the flashfile.xml from the extracted ROM folder, and your phone will be flashed.
When the welcome screen appears, go back to fastboot mode and relock the bootloader using "fastboot oem lock".
That's it! I'm now enjoying the EU ROM on my Moto X40. I'll update this post after I activate 5G on my SIM, test banking apps, and check for any OTA updates (the latest security patch for this ROM is from February 2023).
I hope this helps some of you out there!
Cheers!
EDIT: 5G works!
Click to expand...
Click to collapse
You can connect a vpn since the option in settings about the vpn does not appear on my device Where is the data saving below, the option about the vpn should appear but in the capture that command does not appear
I tried to run today Cloudflare Warp and noticed the VPN option is not available. I've read somewhere it could be a bug or it needs to activate the multiuser option. I'll research it further
April security patch with reteu rom and closed bootloader The vpn thing has not been corrected, hopefully there is a solution to this
ziggmax said:
April security patch with reteu rom
Click to expand...
Click to collapse
I'm still in February, no OTA update yet. I created a multiuser account and can see the VPN option. It's something related to Google Apps Account security policies ?
ziggmax said:
You can connect a vpn since the option in settings about the vpn does not appear on my device Where is the data saving below, the option about the vpn should appear but in the capture that command does not appear
Click to expand...
Click to collapse
GigogoHK said:
I tried to run today Cloudflare Warp and noticed the VPN option is not available. I've read somewhere it could be a bug or it needs to activate the multiuser option. I'll research it further
Click to expand...
Click to collapse
Have you tried accessing VPN settings using an activity manager such as Shortcut Maker?
TheMystic said:
Have you tried accessing VPN settings using an activity manager such as Shortcut Maker?
Click to expand...
Click to collapse
If I already tried with that app but it won't let me add the apps
GigogoHK said:
I tried to run today Cloudflare Warp and noticed the VPN option is not available. I've read somewhere it could be a bug or it needs to activate the multiuser option. I'll research it further
Click to expand...
Click to collapse
I did that too but it won't let me install apps outside of chrome but it's annoying that to use a vpn you have to enable multi-user Hopefully they will fix it soon with an update.
ziggmax said:
If I already tried with that app but it won't let me add the apps
Click to expand...
Click to collapse
Try installing a VPN app like Netguard or a real VPN.
ziggmax said:
I did that too but it won't let me install apps outside of chrome but it's annoying that to use a vpn you have to enable multi-user Hopefully they will fix it soon with an update.
Click to expand...
Click to collapse
Not sure what you mean by 'won't let me install apps outside of Chrome'.
VPN has nothing to do with multi-user feature.
I managed to fix the VPN issue without the multi user setting, check the video of this comment
https://www.reddit.com/r/motorola/comments/zo38xu/_/j1u5t9l
GigogoHK said:
I managed to fix the VPN issue without the multi user setting, check the video of this comment
https://www.reddit.com/r/motorola/comments/zo38xu/_/j1u5t9l
Click to expand...
Click to collapse
This method worked perfectly for me
The uncertain about having OTA updates and the disappointment of the camera are making me consider switching to another phone
GigogoHK said:
The uncertain about having OTA updates and the disappointment of the camera are making me consider switching to another phone
Click to expand...
Click to collapse
The camera doesn seem unable to focus when scanning QRs. I haven't done much photo taking yet.
Zechosenjuan said:
The camera doesn seem unable to focus when scanning QRs. I haven't done much photo taking yet.
Click to expand...
Click to collapse
I have problems with autofocus on recording videos aa well
Just received this OTA, update and installed successfully.
- Autofocus improved
- VPN dialog still not available (need to use tools)
GigogoHK said:
Just received this OTA, update and installed successfully.
- Autofocus improved
- VPN dialog still not available (need to use tools)
View attachment 5913631
Click to expand...
Click to collapse
Would you recommend doing the conversion?
Related
I dont have it very clear, do I have to do testpoint in order to unlock my bootloader in 9.2.6.0 Global Stable?
Now, you don't need testing point method to unlock bootloader.
You will need to unlock here:
http://en.miui.com/unlock/
It might be needed an Chinese VPN to do it
It takes 360 hours.
And then you can flash global rom. Be sure to keep bootloader unlocked or else the phone will need the testpoint method to work again.
I advise you to read a little bit on MIUI foruns before advancing.
I'm waiting to unlock my own phone, but so far I've managed to work with Chinese Rom in English, after gaps installation.
Is it possible to replace the recovery.img file in the ROM ZIP with TWRP? ie. rename TWRP to recovery.img, so that when it's flashed, you get TWRP with a locked bootloader?
I know this approach was used on older Xiaomi phones, but I'm not sure if it can be used with any model.
Pumpino said:
Is it possible to replace the recovery.img file in the ROM ZIP with TWRP? ie. rename TWRP to recovery.img, so that when it's flashed, you get TWRP with a locked bootloader?
I know this approach was used on older Xiaomi phones, but I'm not sure if it can be used with any model.
Click to expand...
Click to collapse
i'm kinda guessing, but if you push 'tempered' img in locked bootloader most likely it will bootloop.
anyway, how you get twrp without unlocking bootloader?
same situation for mine, come with 9.2.6.0 Global Stable. What I had done so far:
1. already received SMS for unlock permission
2. proceed to bind device & account, but stuck here, I got 86006 error.
Few methods tried but still failed:
1. tried many VPN for China, failed.
2. tried xiamitool to flash development or China ROM, failed because older version not allow, & bootloader unlocked are required.
I try to avoid test point, please help me. anyone know when MIUI 10 development will available to download?
djlah said:
1. tried many VPN for China, failed.
Click to expand...
Click to collapse
There are only a few VPN apps that work with binding the account to the phone. Xiaomi makes it harder than it should be. I tried many apps on my new Mi Note 3 last night and finally found one that worked. It was Solo VPN.
You can also use PlexVPN or Turbo VPN up to v1.3 (can be downloaded from this thread. https://forum.xda-developers.com/redmi-note-4/how-to/solution-error-10008-unlocking-t3584341)
Pumpino said:
There are only a few VPN apps that work with binding the account to the phone. Xiaomi makes it harder than it should be. I tried many apps on my new Mi Note 3 last night and finally found one that worked. It was Solo VPN.
You can also use PlexVPN or Turbo VPN up to v1.3 (can be downloaded from this thread. https://forum.xda-developers.com/redmi-note-4/how-to/solution-error-10008-unlocking-t3584341)
Click to expand...
Click to collapse
thanks for sharing. Solo tested, still 86006 error. Plex also failed, Turbo don't have China server, FlyVPN don't have free trial for China. Other VPN tried like Nord, VPN unlimited, Proton, also no luck. Why Xiaomi makes it harder?
djlah said:
thanks for sharing. Solo tested, still 86006 error. Plex also failed, Turbo don't have China server, FlyVPN don't have free trial for China. Other VPN tried like Nord, VPN unlimited, Proton, also no luck. Why Xiaomi makes it harder?
Click to expand...
Click to collapse
Did you use the VPN Turbo APK from the thread I linked to? I've used Plex and Solo successfully this week. Choose the Shanghai server in Plex if it's available. Otherwise, try China and Hong Kong in those apps.
Edit: Note that you'll need to log out of your Mi account before connecting to the VPN and then try adding it from the developer options menu again.
Does the error message mention "API"? If not, the VPN might not be your only problem.
Pumpino said:
Did you use the VPN Turbo APK from the thread I linked to? I've used Plex and Solo successfully this week. Choose the Shanghai server in Plex if it's available. Otherwise, try China and Hong Kong in those apps.
Edit: Note that you'll need to log out of your Mi account before connecting to the VPN and then try adding it from the developer options menu again.
Does the error message mention "API"? If not, the VPN might not be your only problem.
Click to expand...
Click to collapse
thanks for the tips. I just redo as you said. sign out then connect VPN Shanghai, still failed. if you read Chinese, this is the exact message: "86006 : 参数组合非法"
Do I really need to wait 360hours after SMS approval?
djlah said:
thanks for the tips. I just redo as you said. sign out then connect VPN Shanghai, still failed. if you read Chinese, this is the exact message: "86006 : 参数组合非法"
Do I really need to wait 360hours after SMS approval?
Click to expand...
Click to collapse
You need to wait 360 hours after you've bound the account to the phone, yes. It's 72 hours for older models and 360 for new models. There's no way around it. However, if you're receiving that message when you run the unlocking program, it sounds like your phone is already linked to your Mi account.
Pumpino said:
You need to wait 360 hours after you've bound the account to the phone, yes. It's 72 hours for older models and 360 for new models. There's no way around it. However, if you're receiving that message when you run the unlocking program, it sounds like your phone is already linked to your Mi account.
Click to expand...
Click to collapse
woow, 360hours! no choice then if this is their policy, have to wait. that's message is display when I click "add account & device" from mi unlock status. I will not get success unlock bootloader if run the unlocking program. will prompt you to bind your phone first. will share again once 360 hours wait is over......
Pumpino said:
Did you use the VPN Turbo APK from the thread I linked to? I've used Plex and Solo successfully this week. Choose the Shanghai server in Plex if it's available. Otherwise, try China and Hong Kong in those apps.
Edit: Note that you'll need to log out of your Mi account before connecting to the VPN and then try adding it from the developer options menu again.
Does the error message mention "API"? If not, the VPN might not be your only problem.
Click to expand...
Click to collapse
dear tried your method but still not able to unlock boot-loader of redmi5 Plus, i have an old MI account which was used before Redmi pro and i have get permission to unlock boot-loader about 6 months ago, i am on latest official global Rom 9.2.6.0 (NEGMIEK) and i didn't find any way to unlock boot-loader and flash TWRP to install Gcam on my redmi 5 Plus.
tried almost every VPN and every method available on XDA but it seems if i am on developer rom than my MI account could be bind to device, also it shows that MI disable the feature in global rom for unlocking boot-loader.
Note: please correct me if i am wrong regarding disabling the feather of unlocking bootloader in global rom
irfan.shikarpuri said:
dear tried your method but still not able to unlock boot-loader of redmi5 Plus, i have an old MI account which was used before Redmi pro and i have get permission to unlock boot-loader about 6 months ago, i am on latest official global Rom 9.2.6.0 (NEGMIEK) and i didn't find any way to unlock boot-loader and flash TWRP to install Gcam on my redmi 5 Plus.
tried almost every VPN and every method available on XDA but it seems if i am on developer rom than my MI account could be bind to device, also it shows that MI disable the feature in global rom for unlocking boot-loader.
Note: please correct me if i am wrong regarding disabling the feather of unlocking bootloader in global rom
Click to expand...
Click to collapse
if only development rom are allow to bind the device, then we gonna wait until MIUI 10 release
I faced problem 10008 in attempt of an unblocking of the uploader in redmi 5 plus.
If you have the Chinese firmware, then download the DNS Changer program https://play.google.com/store/apps/details?id=com.burakgon.dnschanger&hl=en)
You launch it and you select custom DNS. As the first dns you register 61.155.18.36, and the second 123.131.131.182 and you click start.
djlah said:
same situation for mine, come with 9.2.6.0 Global Stable. What I had done so far:
1. already received SMS for unlock permission
2. proceed to bind device & account, but stuck here, I got 86006 error.
Few methods tried but still failed:
1. tried many VPN for China, failed.
2. tried xiamitool to flash development or China ROM, failed because older version not allow, & bootloader unlocked are required.
I try to avoid test point, please help me. anyone know when MIUI 10 development will available to download?
Click to expand...
Click to collapse
Same with mine, waiting global dev to release, hopefully soon
XavierBrian said:
Same with mine, waiting global dev to release, hopefully soon
Click to expand...
Click to collapse
based on historical, roughly is July for developer version, and August for Stable version. 5 months waiting time from now :crying:
djlah said:
based on historical, roughly is July for developer version, and August for Stable version. 5 months waiting time from now :crying:
Click to expand...
Click to collapse
Seriously???:crying:
migueltb01 said:
I dont have it very clear, do I have to do testpoint in order to unlock my bootloader in 9.2.6.0 Global Stable?
Click to expand...
Click to collapse
yes
psychem said:
yes
Click to expand...
Click to collapse
I already did it, thank you!
migueltb01 said:
I already did it, thank you!
Click to expand...
Click to collapse
thanks for update sharing. I'm really newbie for phone tear down. can you share what's the difficulty level, any per-caution or risks. thanks.
TESTED IN INDIAN AND BRAZILIAN DEVICES
https://motoota.lolinet.com/index.p...&carrier=retbr&sn=SERIAL_NUMBER_NOT_AVAILABLE
FOR MEXICAN USERS
https://motoota.lolinet.com/index.p...&carrier=amxmx&sn=SERIAL_NUMBER_NOT_AVAILABLE
Pre-requisites:
1. Battery 50+%
2. Locked bootloader
How to install ?
Step 1: Place the downloaded zip in internal storage and rename it.
( Indian / Brazilian: Blur_Version.29.11.30.albus.retail.en.US.zip or Mexican: Blur_Version.29.11.31.albus.retail.en.US.zip)
Step 2: Go to settings -> apps -> show system apps
and then give storage permission for Motorola update services.
Step 3: Reboot the phone and then check for update in settings app.
#Youtube video tutorial by Rocha Tech
https://youtu.be/xJO31p4GLmU
(Just watch the video without sound if you understand the language )
#FAQ
1. What about my data after i install this update?
Ans: Your data is safe after installing the update. For more safety, you can backup your data as an additional safety measure.
2. Will this work on my bootloader unlocked device ?
Ans: No, it will not work with bootloader unlocked. You need to flash the Oreo stock rom to be able to flash this on your device.
3. Why my country name is not mentioned for updates ?
Ans: You may try Indian update zip file and if it doesn't work then try the Mexican one.
Credits:
Helton Vezzoni @erfanoabdi
Any info about the build, software channel, etc?
XBrav said:
Any info about the build, software channel, etc?
Click to expand...
Click to collapse
Load it up and tell us.
kewlzter said:
Load it up and tell us.
Click to expand...
Click to collapse
Definitely trying. Stock recovery was not spawning ADB, so I'm trying to boot TWRP live. It's been a while, and it's hanging on the TWRP page.
XBrav said:
Definitely trying. Stock recovery was not spawning ADB, so I'm trying to boot TWRP live. It's been a while, and it's hanging on the TWRP page.
Click to expand...
Click to collapse
I tried TWRP (installed) didn't work.
I'll try returning to stock and sideloading tomorrow after work.
Ok, trying the stock way:
1) Reboot into bootloader (Power + Vol Down)
2) Select boot into Recovery.
3) At "No Command" Screen, hold down Power and press Vol Up.
4) Load from SD card, or live dangerously like me and sideload via ADB (Minimal ADB and Fastboot seems to work for me)
Will update once the push is complete.
I just downloaded.
Gave "Motorola Update Services" storage permission.
Copied the file from the computer to the phone's internal storage.
Checked for updates
And voilá, there was the update.
I'm already running Pie.
Up and running here. Didn't like my original image, but after flushing data, it booted fine. It did say I no longer qualify for updates which seems to be a new thing with Motorola and Pie, but common across other devices too. Either way, it all seems to be working.
victorhbm15 said:
I just downloaded.
Gave "Motorola Update Services" storage permission.
Copied the file from the computer to the phone's internal storage.
Checked for updates
And voilá, there was the update.
I'm already running Pie.
Click to expand...
Click to collapse
Did it work really..??
Do we need unlocked bootloader or will it work for all..
Currently running Stock Oreo Firmware locked Bootloader.
Trying to sideload via ADB, will post results after completion of process.
Hello!
Is there an .xml file for this update?
OR
Any proper guide for sideload method?
Thanks
OK! I found a guide for Oreo OTA sideload install.
https://forum.xda-developers.com/z2-play/how-to/official-oreo-z2-play-t3784660
I guess for Pie it is the same.
Tried.
Didn't work.
Can anybody guess what I did wrong?
OldUncle said:
Tried.
Didn't work.
Can anybody guess what I did wrong?
Click to expand...
Click to collapse
Did you follow the steps I posted earlier? What does the phone show for errors?
For those of you who were curious:
1) Software channel remained the same.
2) Dual sim in XT1710-09 seems to be working fine so far (haven't tested a second sim, but the sim statuses are showing for both card slots).
3) No issues with mods so far (Tried the battery pack and gamepad. Hasselblad, projector and speaker are not with me).
4) Build number is PPS29.133-30, Patch Level September 1, 2019.
My phone is in Canada, and the modem patch included works fine as far as I've seen. I haven't fully tested the bluetooth stability yet to see if it's working better than before. Android Auto is working great though.
My smartphone Model name is XT-1710-10, Dual SIM.
I was successfully able to sideload the Update, with the command
"adb sideload Blur_Version.29.11.30.albus.retail.en.US.zip".
It took around 15 to 18 mins for the sideload process to complete, later the phone restarted and showed the usual Moto loading screen for another 12mins or so, for a moment i thought it was stuck, but no, it successfully completed the update process.
Everything is functioning as usual, i noticed that the placement of signal bar, wifi icons, and battery icons on the top right corner of the screen seem to be not proper.
Same is the case with the arrangement of signal and wifi icons on top right portion inside notification drop down menu, seems to be too close to the screen edge.
Additional features I saw after the update are, 3 finger screenshot, Screenshot editor, Media controls provision inside 'Moto Actions'; Attentive display inside 'Moto display'.
Also the addition of "Digital Wellbeing" inside settings Menu.
---------- Post added at 01:33 PM ---------- Previous post was at 01:17 PM ----------
OldUncle said:
Hello!
Is there an .xml file for this update?
OR
Any proper guide for sideload method?
Thanks
OK! I found a guide for Oreo OTA sideload install.
https://forum.xda-developers.com/z2-play/how-to/official-oreo-z2-play-t3784660
I guess for Pie it is the same.
Tried.
Didn't work.
Can anybody guess what I did wrong?
Click to expand...
Click to collapse
It took around 3hrs for me to solve the problem, I am still not clear, what was I doing wrong.
What worked for me somehow was... I properly uninstalled the old ADB installations first vis control panel and then downloaded the latest version of adb i.e adb-setup-1.4.6.exe, and repeated the normal procedure of adb sideload, this time it worked.
I couldn't find an option to enable Android Pie navigation gestures, even in System>Gestures, there is no option.
Do existing TWRP and Magisk root work?
Thanks to everyone who replied with advices :good:
It is my first try to Sidload OTA.
I found out that, I needed the latest OPS27.76-12-25-22/23 stock firmware and I was using OPS27.76-12-25-13.
I fastbooted to the latest but, it didn't work again and I think the reason is that my device is XT1710-11 (Chinese), though I have fastbooted it to RETEU version (Modems preserved) and works fine.
If my guess is correct, that means I need to wait for the fastboot version for Pie
snuk182 said:
Do existing TWRP and Magisk root work?
Click to expand...
Click to collapse
its working great
I get error while sideloading.. i need OPS27.76-12-25-22/23 firmware and I am using OPS27.76-12-42-13/16. On bell canada.
Any advise?
saurav112214 said:
I get error while sideloading.. i need OPS27.76-12-25-22/23 firmware and I am using OPS27.76-12-42-13/16. On bell canada.
Any advise?
Click to expand...
Click to collapse
https://mirrors.lolinet.com/firmware/moto/albus/official/
Get the firmware you need from that link and then fastboot flash it to your device.
But make sure if this OTA Pie is for your device.
XBrav said:
Did you follow the steps I posted earlier? What does the phone show for errors?
For those of you who were curious:
1) Software channel remained the same.
2) Dual sim in XT1710-09 seems to be working fine so far (haven't tested a second sim, but the sim statuses are showing for both card slots).
3) No issues with mods so far (Tried the battery pack and gamepad. Hasselblad, projector and speaker are not with me).
4) Build number is PPS29.133-30, Patch Level September 1, 2019.
My phone is in Canada, and the modem patch included works fine as far as I've seen. I haven't fully tested the bluetooth stability yet to see if it's working better than before. Android Auto is working great though.
Click to expand...
Click to collapse
I too have an XT1710-09 (Europe, RETEU software channel). Any idea if this firmware will work for me? Thanks!
Apologies if this is reported elsewhere (I couldn't find it) but here is a new unlock method by 'mashed-potatoes' on github and it's flippin' awesome!
See: "github.com/mashed-potatoes/PotatoNV[/" (had to format like this due to XDA newbie rules)
I've just unlocked a P10 bootloader with it - the phone was running Oreo with a March 2019 security patch :good:
It is a test point method - so back cover needs to be removed (TP location easily found on YouTube)
When I realised I was stuck on a patch >June18 I thought bootloader unlocking wouldn't be possible (although I was trawling XDA archives to see if flashing board software for unlocked fastboot might provide a route). Anyway, didn't need any of that cuz I ran PotatoNV.exe and put the phone in TP mode and ker-boom: BL unlocked! Amazing work.
EDIT:
A few extra tips to help get through the process:
- You will need to install Test-point drivers - can be found by running the Potato program and following the web address to the User Manual - link to drivers is there. (Uninstall drivers when finished or else phone won't be recognized properly by PC later!)
- Open up Device Manager to check that you are booting to TP - devices changes from 'USB SER' to 'USB (COM')' - or something like that, I don't exactly remember!. It might take a few goes to boot into TP - disconnect then reconnect battery each attempt.
Thanks for sharing this program. this works for me, after bricking my phone 2 years ago. I finally got to unlock my bootloader. And its working now and doing great.
Hello,
Does this soft FACTORY RESET after bootloader unlock?
Regards
RJ
tested on huawei p10 vtr-l09 with emui 9.1 and works perfectly, does not erase data or do hard reset, excellent tool ?
---------- Post added at 07:52 AM ---------- Previous post was at 07:51 AM ----------
rafjak said:
Hello,
Does this soft FACTORY RESET after bootloader unlock?
Regards
RJ
Click to expand...
Click to collapse
no friend, i did it and it doesn't factory reset
Hey bro, could you please tell me the steps you made?
I am in emui 9.1 too.
Thanks.
josua19 said:
tested on huawei p10 vtr-l09 with emui 9.1 and works perfectly, does not erase data or do hard reset, excellent tool
---------- Post added at 07:52 AM ---------- Previous post was at 07:51 AM ----------
no friend, i did it and it doesn't factory reset
Click to expand...
Click to collapse
itsjhndnllclrg said:
Thanks for sharing this program. this works for me, after bricking my phone 2 years ago. I finally got to unlock my bootloader. And its working now and doing great.
Click to expand...
Click to collapse
Hi, can you help with the steps please, i'm a newbie at using git.
Never mind, thanks.
HOW TO OPEN PotatoNV.exe
New_ said:
Apologies if this is reported elsewhere (I couldn't find it) but here is a new unlock method by 'mashed-potatoes' on github and it's flippin' awesome!
See: "github.com/mashed-potatoes/PotatoNV[/" (had to format like this due to XDA newbie rules)
I've just unlocked a P10 bootloader with it - the phone was running Oreo with a March 2019 security patch :good:
It is a test point method - so back cover needs to be removed (TP location easily found on YouTube)
When I realised I was stuck on a patch >June18 I thought bootloader unlocking wouldn't be possible (although I was trawling XDA archives to see if flashing board software for unlocked fastboot might provide a route). Anyway, didn't need any of that cuz I ran PotatoNV.exe and put the phone in TP mode and ker-boom: BL unlocked! Amazing work.
Click to expand...
Click to collapse
Hi, please please explain how to run the potato project
found it, please ignore the post
Friends could pass the tutorial video of the TP location
New_ said:
Apologies if this is reported elsewhere (I couldn't find it) but here is a new unlock method by 'mashed-potatoes' on github and it's flippin' awesome!
See: "github.com/mashed-potatoes/PotatoNV[/" (had to format like this due to XDA newbie rules)
I've just unlocked a P10 bootloader with it - the phone was running Oreo with a March 2019 security patch :good:
It is a test point method - so back cover needs to be removed (TP location easily found on YouTube)
When I realised I was stuck on a patch >June18 I thought bootloader unlocking wouldn't be possible (although I was trawling XDA archives to see if flashing board software for unlocked fastboot might provide a route). Anyway, didn't need any of that cuz I ran PotatoNV.exe and put the phone in TP mode and ker-boom: BL unlocked! Amazing work.
EDIT:
A few extra tips to help get through the process:
- You will need to install Test-point drivers - can be found by running the Potato program and following the web address to the User Manual - link to drivers is there. (Uninstall drivers when finished or else phone won't be recognized properly by PC later!)
- Open up Device Manager to check that you are booting to TP - devices changes from 'USB SER' to 'USB (COM')' - or something like that, I don't exactly remember!. It might take a few goes to boot into TP - disconnect then reconnect battery each attempt.
Click to expand...
Click to collapse
I DOWNLOADED THE FILE FROM GIT.. BUT IT DOESNT HAVE BOOTLOADER FILES INCLUDED WHERE CAN I GET?
KIRIN 960 HUAWEI P10,
1. DOWNLOADED THE ZIP FROM GITHUB
2. RUN THE PROGRAM USING VISUAL INSTALLER
3. PUT THE P10 TO TESTPOINT METHOD AND ENABLE HUAWEI COM 1.0
4. PROGRAM ERRORS WHEN LOOKING FOR BOOTLOADER FILES.
where can i get bootloader files ? for kirin 960 i can
Please do you add support for newer Kirin CPUs? Kirin 990 etc...
DasXardas said:
Please do you add support for newer Kirin CPUs? Kirin 990 etc...
Click to expand...
Click to collapse
Err, no. Finding bootloader exploit on newer Kirin's would be like finding Holy Grail.
You could always join 'Big Huawei Exploits' group on Telegram and ask them how it's going rolleyes
New_ said:
Err, no. Finding bootloader exploit on newer Kirin's would be like finding Holy Grail.
You could always join 'Big Huawei Exploits' group on Telegram and ask them how it's going rolleyes
Click to expand...
Click to collapse
Thank you. I'll try them.
Is it possible to unlock bootloader & root phone, which was rebranded with "funky huawei" ?
Huawei P10, from VTR-L09 to VTR-L29
[QUOTE = "New_, publicación: 83667321, miembro: 10899731"]
Grandes hazañas de Huawei
[/CITAR]
Please link
Many thanks, it worked flawlessly on my P10 running EMUI 9.1! Test points and disassembly instructions can easily be found on the interwebs. Do not forget to write down the bootloader unlock code PatatoNV generates: I needed it after I bootlooped and downloaded the latest rom with erecovery.
M1chiel said:
Many thanks, it worked flawlessly on my P10 running EMUI 9.1! Test points and disassembly instructions can easily be found on the interwebs. Do not forget to write down the bootloader unlock code PatatoNV generates: I needed it after I bootlooped and downloaded the latest rom with erecovery.
Click to expand...
Click to collapse
Did you lost the unlocked BL after you dl the latest rom and recovery?
Sterben11 said:
Did you lost the unlocked BL after you dl the latest rom and recovery?
Click to expand...
Click to collapse
I downloaded the latest rom twice through erecovery. The first time it locked my bootloader, but the second time it did not. The first time I could easily unlock again with the code generated by the patatoNV tool.
M1chiel said:
I downloaded the latest rom twice through erecovery. The first time it locked my bootloader, but the second time it did not. The first time I could easily unlock again with the code generated by the patatoNV tool.
Click to expand...
Click to collapse
Ah yes I bricked my phone 2 times already and experienced what erecovery is for. It's my first time to mess with my good ol p10 have you tried any working open kirin custom on it? cuz everytime I flash a 9.0/9.1 compatible rom it ends on bootloop I used adb and fastboot btw. This is my last question sorry a noobie here.
(take note I followed every instructions on their support page on how to flash)
Sterben11 said:
Ah yes I bricked my phone 2 times already and experienced what erecovery is for. It's my first time to mess with my good ol p10 have you tried any working open kirin custom on it? cuz everytime I flash a 9.0/9.1 compatible rom it ends on bootloop I used adb and fastboot btw. This is my last question sorry a noobie here.
(take note I followed every instructions on their support page on how to flash)
Click to expand...
Click to collapse
The AEX roms worked for me, the omniroms unfortunately did not boot (emui 9.1). They are supposed to work on emui 9.0. Did you do the factory reset from emui recovery? AEX is very basic android and quite nice, although not as fluent as emui.
So to use this, you will need to be bootloader unlocked, magisk rooted, and twrp installed, DM Verity Disabled this is a must!!(its always good to make a nandroid before making any changes on your phone). What this will do is more or less provision your Lg G8x to your Desired Carrier, it will also let you change your apns, so you have volte working and also the data indicator will change to match the carrier. WIfi calling is working on tmobile, will need someone to test other carriers.
There seems to be confusion , this is only for the Stock rom. this will do nothing for GSI roms.
Instructions:
1.Extract to Content of zip to Sdcard
2.Make a copy/backup of your own files: Go to twrp and backup your product partition and your op configs in case you need to restore them
3.Copy and paste the files from my zip to:
/product/op/config
and this single file cust.prop to /product/op
make sure permissions are 644.
4.Reboot your device it should now be provisioned to your Desired Carrier.
Click to expand...
Click to collapse
Download
Sprint Untested
SPR-VOLTE-FIX
MediaFire is a simple to use free service that lets you put all your photos, documents, music, and video in a single place so you can access them anywhere and share them everywhere.
www.mediafire.com
T-Mobile
Tmo-VOLTE-VOWIFI-FIx-G8x
MediaFire is a simple to use free service that lets you put all your photos, documents, music, and video in a single place so you can access them anywhere and share them everywhere.
www.mediafire.com
VZW Untested
VZW-VOLTE-FIX
MediaFire is a simple to use free service that lets you put all your photos, documents, music, and video in a single place so you can access them anywhere and share them everywhere.
www.mediafire.com
Credits:
vl48 this guy is awesome, and also very patient an expert in lg devices.
Can you write a guide for ATT LG G8X (LMG850UM) on
How to bootloader unlocked, magisk rooted, and twrp installed, DM Verity Disabled? It's confusing which method is valid and which files to use.
e20140 said:
Can you write a guide for ATT LG G8X (LMG850UM) on
How to bootloader unlocked, magisk rooted, and twrp installed, DM Verity Disabled? It's confusing which method is valid and which files to use.
Click to expand...
Click to collapse
There is one already made, you just need the correct twrp from telegram
siulmagic said:
There is one already made, you just need the correct twrp from telegram
Click to expand...
Click to collapse
Why not post on xda? Is everyone switching to telegram? I've read everything on xda and don't see a specific method to unlock bootloader+twrp+DM but a few failed attempts on ATT version of the G8X. I only see working solution for India, Europe, and Sprint Models. You are the only one that has successfully unlock it. I am sure more people will need help as 3G is going away and we need Volte working on this phone.
well the basic gist of it is:
This will WIpe Your Phone, make sure to backup first.
Cant post the recovery zip, but pm il send it to you. i will move this to a proper thread later today. and better formatted
1.install qpst/qualcom driver or use windows update ones
2. download firehose uncompress it somewere on your pc
3.download g8x twrp and magisk 20.4 zip also the dm verity zip
also make sure to grab the eng abl for the g8x(eng bootloader that will allow us to unlock).
4. enable oem unlock in developer settings
5. boot phone into edl mode
6.start qpst set storage type to ufs, slect built type, make sure it is flat build
7.Look for select programer then click browse, here you will chose the firehose file
8. click select port on qfil then double click 9008 com port were the phone is detected in edl mode
9.now in qfil select tools then partition manager
10. when the list of partitions show up look for abl_a,abl_b,modem a/b, and modemst1 and 2, you will right click each of them and click manage partition data then read data, this will back them up to your computer(be very careful you can wipe your whole phone if you click in the wrong place)
11.after you back up everything select load img and flash abl_a to Abl_a and abl_b. after this unplug phone and boot into bootloader mode.
To boot into bootloader mode turn off your phone and hold volm down and plug in your usb cable, this should boot it into bootloader mode .
12. if you see text that says you active boot slot, you now have successfully flashed the eng bootloader witch will allow you to unlock the bootloader.
13. now while the phone is pluged into your computer you will open a adb window and type fastboot oem unlock , the phone will ask you to agree to unlock the bootloader, select yes.
14.after this reboot your phone into edl mode, reflash your backup abl_a to abl_a and abl_b, this will restore stock bootloader you wont have fastboot anymore but no worries, also you can flash your stock rooted boot.img to boot_a and boot_b.
15. After you reboot into android, install magisk manager, flash the g8x twrp zip and without reboot, also flash magisk 20.04 zip, if you do not do it this way you will break your boot.img and have issues, like freezing system.
16 now reboot to recovery wipe data then reboot and flash the dm verity disabler to disable encryption. after this create a nandroid backup, then just reboot back to system and enjoy.
17. profit
Nice
I need to return my G8X since it has the latest 20g firmware. If anyone wants me to try or test something, please let me know before it's going back.
e20140 said:
Nice
I need to return my G8X since it has the latest 20g firmware. If anyone wants me to try or test something, please let me know before it's going back.
Click to expand...
Click to collapse
why 0o with gpst and firehose you can root bl unlock any att g8x, unless there something im not aware of?
I post the short error log here. The firehose we got can't read the partitions correctly. Maybe the mappings are different, IDK? If you want to read the full log, let me know.
e20140 said:
I post the short error log here. The firehose we got can't read the partitions correctly. Maybe the mappings are different, IDK? If you want to read the full log, let me know.
Click to expand...
Click to collapse
thats a driver error, you need to let windows install the driver from windows update or like i did use qpst on windows 7. i never got that erro fixed, so i just used windows 7 on a old laptop i have, and it works mint.
I don't have Window 7 to try but tried on other Win 10 PCs and Laptops, just no luck. I can use QPST to flash flat built on my G6 fine, really don't think it's driver issue.
e20140 said:
I don't have Window 7 to try but tried on other Win 10 PCs and Laptops, just no luck. I can use QPST to flash flat built on my G6 fine, really don't think it's driver issue.
Click to expand...
Click to collapse
well thats the error i got, with my g8 and g8x on windows 10.
wangsu10 suggested the error could be installation selection option for the QCOMM driver. Need to be install as 2nd option " ETHERNET-DHCP". I already returned mine
Maybe you can try it on your Win10 and report back. If it works, we need to have it added to the OP for all others to see.
Thank you for sharing this. I have a sprint model that ended up with T-mobile provisioning after I boot loader unlocked it. The only issue I think I have at least the obvious is google messages will never verify and setup rcs. I suspect this will be permanent eventually as they begin to roll out their other layer of security for verifying that which would basically black list bootloader unlocked or rooted devices...will your files/instructions aid in any issues with RCS currently before before Google makes the final rollout?
nate0 said:
Thank you for sharing this. I have a sprint model that ended up with T-mobile provisioning after I boot loader unlocked it. The only issue I think I have at least the obvious is google messages will never verify and setup rcs. I suspect this will be permanent eventually as they begin to roll out their other layer of security for verifying that which would basically black list bootloader unlocked or rooted devices...will your files/instructions aid in any issues with RCS currently before before Google makes the final rollout?
Click to expand...
Click to collapse
Thats an easy fix search for carrier services on play store , update it and see if chat features get enabled, I got rcs working just fine on att g8x bl unlocked and rooted ofc.
siulmagic said:
Thats an easy fix search for carrier services on play store , update it and see if chat features get enabled, I got rcs working just fine on att g8x bl unlocked and rooted ofc.
Click to expand...
Click to collapse
Yeah I did this, and by default it was already installed. Still no luck. I tried clearing data while on airplane mode everything. Nothing works yet.
@siulmagic where is the twrp image for the g8x? Did they pull it down?
nate0 said:
@siulmagic where is the twrp image for the g8x? Did they pull it down?
Click to expand...
Click to collapse
the one here never worked properlly, if you want a working one join telegram and i can send it to you,.
nate0 said:
Yeah I did this, and by default it was already installed. Still no luck. I tried clearing data while on airplane mode everything. Nothing works yet.
Click to expand...
Click to collapse
there is another app that needs updated i forgot witch one it was.
siulmagic said:
the one here never worked properlly, if you want a working one join telegram and i can send it to you,.
Click to expand...
Click to collapse
Newbie to Telegram, how does one find the group please?
mangojain said:
Newbie to Telegram, how does one find the group please?
Click to expand...
Click to collapse
LG Mobiles India 🇮🇳
Political Discussion, Obscene material/words, Selling, Fraudulent link posting will lead to Ban SHARING COPYRIGHT CONTENT & PIRACY NOT ALLOWED, it leads to REPORT & BLOCK Photography Group: @lgg8xphotography OT Group: @LG_G8X_OffTopic
t.me
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