Database Develop

Any other way to root this device on 4.3 without unlocking it?

Seems like that I would never make it to unlock it.:crying:

super0dd said:
Seems like that I would never make it to unlock it.:crying:
Click to expand...
Click to collapse
No not right now.
Remind me where you are getting stuck?
The tricky part is updating to 4.3 if you are on 4.2.2 and then you unlock, but if you are locked on 4.2.2 then just upgrade to 4.3 and then unlock, fastboot flash cwm and use my superuser zip to root. Easy!

sbdags said:
No not right now.
Remind me where you are getting stuck?
The tricky part is updating to 4.3 if you are on 4.2.2 and then you unlock, but if you are locked on 4.2.2 then just upgrade to 4.3 and then unlock, fastboot flash cwm and use my superuser zip to root. Easy!
Click to expand...
Click to collapse
All right, just let me tell you my whole story.
Someday I seemed to overcharge my tablet and thus broke the power management chip on the motherboard and then I found it stuck on the boot screen and was only able to boot to recovery. After I finally surrendered to it, I went to have Asus's guy replaced it a new motherboard, which took me like 230 bucks(much close to a new nexus 7).When I got my tablet back, it was already on 4.3 (10.26.1.18 CN), then I found it incapable to be unlocked. But I still want to root it anyway since the stock Chinese firmware is not even with GApps and lacks a lot of features that others possess. At least, I need Play Store!
Problem1: I am not sure if Asus's server records the existence or S/N of the current motherboard, which is most likely to incapacitate the unlock process.
Problem 2:
Code:
Unknown error occured, which may a network error
Please try later
That's the problem I meet all the time. I don't know if the official unlock tool is available for 4.3(the official webpage says that it is for 4.2.2 only and I can't find any other similar unlock tool for even ME302c:crying, as the firmware version is already 4.3 when I got it and it doesn't seem to be feasible fo downgrade it.
Problem 3: I have tried every root tools I know, and failed. Not possible to use the masterkey…
Thank you anyway.:victory:

super0dd said:
All right, just let me tell you my whole story.
Someday I seemed to overcharge my tablet and thus broke the power management chip on the motherboard and then I found it stuck on the boot screen and was only able to boot to recovery. After I finally surrendered to it, I went to have Asus's guy replaced it a new motherboard, which took me like 230 bucks(much close to a new nexus 7).When I got my tablet back, it was already on 4.3 (10.26.1.18 CN), then I found it incapable to be unlocked. But I still want to root it anyway since the stock Chinese firmware is not even with GApps and lacks a lot of features that others possess. At least, I need Play Store!
Problem1: I am not sure if Asus's server records the existence or S/N of the current motherboard, which is most likely to incapacitate the unlock process.
Problem 2:
Code:
Unknown error occured, which may a network error
Please try later
That's the problem I meet all the time. I don't know if the official unlock tool is available for 4.3(the official webpage says that it is for 4.2.2 only and I can't find any other similar unlock tool for even ME302c:crying, as the firmware version is already 4.3 when I got it and it doesn't seem to be feasible fo downgrade it.
Problem 3: I have tried every root tools I know, and failed. Not possible to use the masterkey…
Thank you anyway.:victory:
Click to expand...
Click to collapse
Ah OK - the issue is Asus have replaced your motherboard so the mac address you are now supplying does not match the serial number of the device that they have in their database.
The ONLY way to proceed is to contact asus and get them to update their database with your new mac address - stating that you can't use their online web services like device tracking etc until they do so. They will eventually do it but if you can hold of a rep in Taiwan that will speed things up.
There is no other way.

sbdags said:
Ah OK - the issue is Asus have replaced your motherboard so the mac address you are now supplying does not match the serial number of the device that they have in their database.
The ONLY way to proceed is to contact asus and get them to update their database with your new mac address - stating that you can't use their online web services like device tracking etc until they do so. They will eventually do it but if you can hold of a rep in Taiwan that will speed things up.
There is no other way.
Click to expand...
Click to collapse
Uh, do Asus guys have my MAC address? I am not sure.
Okay, I'll phone them tomorrow. It's quite a warm Sunday night now in China.
Thanks a lot.

super0dd said:
Uh, do Asus guys have my MAC address? I am not sure.
Okay, I'll phone them tomorrow. It's quite a warm Sunday night now in China.
Thanks a lot.
Click to expand...
Click to collapse
Of course they do - it is tied to your wifi hardware.

Upgrade path from B123

I'm running a P7 with the firmware it shipped with and I'd really like to get it up to date, but every package I've tried so far has failed during package verification. There seems to be very little info on how to update your phone from such an old build. Can anyone please help because I'm at my wit's end here. I have a limited date cap so can't just keep downloading updates in the hopes that one of them will work.
I would be greatly indebted to anyone who could help me. This issue is making me want to cry.

Do you have a phone with a provider/network lock? Which roms did you try so far? You may give B133 a shot, if that doesn't work you'd have to go the way over a custom rom and then getting back to the stock one. I can describe the process more detailed in case it's necessary.

Thanks for the response!
I think the issue is that it is a network locked ROM. I got the phone from a provider called Vodacom and get their splash screen and everything. I went to speak to them and they told me I'm not supposed to be able to update my firmware because that requires rooting the phone, which voids my warranty. Sales people being sales people, I'm not sure how truthful this is. I can't imagine a provider refusing to let you update your phone.
So far I've tried B133, B609, B617 and B853, none of which works, sadly. Someone suggested I unlock the bootloader and I got the unlock code through the Huawei site, but when I try to boot using the three-button method it tells me that no update.app file was found, so I'm not sure how to get to where I enter the unlock code.

Hm, you might search around a bit and find an easier way, but if not, unlock the bootloader, flash twrp and any emui 2.3 based custom rom. Then flash the stock recovery and make a forced update (3 buttons) with B133.
To access the bootloader you have to press volume- and power until a white screen with some text appears.
Anyway, to update would definitely be worth it.

Yeah, I did precisely that last night and ended up soft-bricking my phone. It wouldn't even work when I flashed the original firmware. It's currently in at a repair shop and I hope they can fix it. Lesson learned though.
Thanks for the help anyway.

It's not that easy to hardbrick the P7, it's very likely that he will be able to fix it! With some time for trying, you probably would have been able to do it by yourself, too.
Your very welcome

Yeah, the thing is I was up all night trying to fix it. Flashing it back the original software should theoretically have done it, so I have no idea why it didn't.

V405UA vibration problem

Hello guys,
I bought new (open box) v40 on ebay and it stated V405UA unlocked. It came with Android 10 v30d.
All is working good except vibration. It doesn't vibrate at all. I tried factory reset, safe mode, application to test vibration and checking battery saver. And it doesn't work for notifications or keyboard feedback.
I contacted seller and he suggested i try to flash V40UA US android 9. I tried flashing V405UA020g_00_USC_US_OP_0424.kdz with LGUP from this forum and it showed me crossflash error (US>EU).
I then tried V405EBW android 10 V405EBW30d_00_OPEN_EU_DS_OP_1223.kdz and it showed me different crossflash error (jadypn_lao_eea>@judypn_la).
Can you please help me identify problem with vibration or recommend what file to flash, as I cannot find any EU V405UA fw.
Thanks in advance

sojkaCZ said:
Hello guys,
I bought new (open box) v40 on ebay and it stated V405UA unlocked. It came with Android 10 v30d.
All is working good except vibration. It doesn't vibrate at all. I tried factory reset, safe mode, application to test vibration and checking battery saver. And it doesn't work for notifications or keyboard feedback.
I contacted seller and he suggested i try to flash V40UA US android 9. I tried flashing V405UA020g_00_USC_US_OP_0424.kdz with LGUP from this forum and it showed me crossflash error (US>EU).
I then tried V405EBW android 10 V405EBW30d_00_OPEN_EU_DS_OP_1223.kdz and it showed me different crossflash error (jadypn_lao_eea>@judypn_la).
Can you please help me identify problem with vibration or recommend what file to flash, as I cannot find any EU V405UA fw.
Thanks in advance
Click to expand...
Click to collapse
whoa boy, what a mess. Well, how big of a mess depends on some unknown things, but there's potential there
First, you say u were on 30d. Which 30d? At&t? vzw? Euro version? There are a lot of 30d's.
Second, the version you were on u may not be able to get back to, if they were at&t or sprint, as they don't make thieir kdz available. No one has one, anywhere. What should have been done, if on one of those firmwares, was to use a special too (bkerler edl) to back up all your partitions first.
Third, the issues you're running into with crossflashing are pretty easily overcome. You just have to use the correct lg up version and matching dll. Also, to crossflash u have to do a partition d/l, none of the other options will work.
Fourth, vibration issue is almost certainly a hardware issue. Probably why it was an 'open box'. Personally, if that doesn't work when I buy it, I return it. It's unfortunate the seller told you to modify the phone, as that usually is the reason they will refuse a return, if it's been modified?
I'd guess the vibration thing is a hw issue, unfortunately.
So what firmware do you WANT to be on? 9 or 10? Which carrier do u use? U need firmware that has those bands. If u can't return and have to live with the no vibration, to me anyway, not end of world.
cheers

Hi,
Thanks for quick reply. I apologise for chaotic first post.
I was on european 30d, there was no further info in system menu i can recall sadly.
I solved issues with crossflashing and successfully flashed these firmwares:
V405UA21c_00_USC_US_OP_1028.kdz
V405EBW30d_00_OPEN_EU_DS_OP_1223.kdz
but none of them solved the issue. (first one recommended by seller, second to get back to european)
Seller offered me that I can return the phone and they will solve the issue, as there is 30 day return policy and 12 month warranty. They even would pay for shipping.
I am now considering returning the phone, but I have smart bracelet which I mainly use for notifications, so I do not depend on vibrations so much. And seller is half of europe apart.
The reason I was thinking that it was software issue was that I found on xda and elsewhere that android recoverry from google backup can be corrupted and then vibrations do not work and my previous phone Xiaomi Mi A2 Lite has occasional problems with vibrations, which is odd coincidence.
Phone was sold as open-box, but the phone itself was sealed. But i think seller flashed the firmware, because it is US version with EU fw and android 10 out of the box. Seller even helped me to get right version of LGUP.
My last question would be if there is a way to tell what causes the issue, if it is hardware.

sojkaCZ said:
Hi,
Thanks for quick reply. I apologise for chaotic first post.
I was on european 30d, there was no further info in system menu i can recall sadly.
I solved issues with crossflashing and successfully flashed these firmwares:
V405UA21c_00_USC_US_OP_1028.kdz
V405EBW30d_00_OPEN_EU_DS_OP_1223.kdz
but none of them solved the issue. (first one recommended by seller, second to get back to european)
Seller offered me that I can return the phone and they will solve the issue, as there is 30 day return policy and 12 month warranty. They even would pay for shipping.
I am now considering returning the phone, but I have smart bracelet which I mainly use for notifications, so I do not depend on vibrations so much. And seller is half of europe apart.
The reason I was thinking that it was software issue was that I found on xda and elsewhere that android recoverry from google backup can be corrupted and then vibrations do not work and my previous phone Xiaomi Mi A2 Lite has occasional problems with vibrations, which is odd coincidence.
Phone was sold as open-box, but the phone itself was sealed. But i think seller flashed the firmware, because it is US version with EU fw and android 10 out of the box. Seller even helped me to get right version of LGUP.
My last question would be if there is a way to tell what causes the issue, if it is hardware.
Click to expand...
Click to collapse
Interesting, good that your seller sounds pretty responsible. Have never used android recovery from google backup, so no help there. The only thing I can thing of to help determine what the no vibration issue is, other than opening the phone, would be to use a logcat and see if there's any error info in it.
Start the logcat just before doing something that would cause the vibration to go on, then shut the logcat. Look for errors...
Additionally, as you've experienced one significant issue, fully check everything else; camera, flash, speakers, anything and everything hw related. that's what I'd do anyway.
cheers

Nothing else seems to be defective.
I tried capturing vibrations on logcat, screenshot attached

sojkaCZ said:
Nothing else seems to be defective.
I tried capturing vibrations on logcat, screenshot attached
Click to expand...
Click to collapse
I'm no expert but from that output, seems to me the software thinks it did it's job. No indications of any problem, but it may be the software tell's it to 'vibrate' and whether it does or not, doesn't matter, as it may not have any checks for errors of any kind.
Additionally, it seems pretty unlikely LG is going to put out an OS version where something as common as the vibrate function doesn't work? Have not heard of any version doing that anyway.
cheers

sojkaCZ said:
Hello guys,
I bought new (open box) v40 on ebay and it stated V405UA unlocked. It came with Android 10 v30d.
All is working good except vibration. It doesn't vibrate at all. I tried factory reset, safe mode, application to test vibration and checking battery saver. And it doesn't work for notifications or keyboard feedback.
I contacted seller and he suggested i try to flash V40UA US android 9. I tried flashing V405UA020g_00_USC_US_OP_0424.kdz with LGUP from this forum and it showed me crossflash error (US>EU).
I then tried V405EBW android 10 V405EBW30d_00_OPEN_EU_DS_OP_1223.kdz and it showed me different crossflash error (jadypn_lao_eea>@judypn_la).
Can you please help me identify problem with vibration or recommend what file to flash, as I cannot find any EU V405UA fw.
Thanks in advanceI
Click to expand...
Click to collapse
sojkaCZ said:
Hello guys,
I bought new (open box) v40 on ebay and it stated V405UA unlocked. It came with Android 10 v30d.
All is working good except vibration. It doesn't vibrate at all. I tried factory reset, safe mode, application to test vibration and checking battery saver. And it doesn't work for notifications or keyboard feedback.
I contacted seller and he suggested i try to flash V40UA US android 9. I tried flashing V405UA020g_00_USC_US_OP_0424.kdz with LGUP from this forum and it showed me crossflash error (US>EU).
I then tried V405EBW android 10 V405EBW30d_00_OPEN_EU_DS_OP_1223.kdz and it showed me different crossflash error (jadypn_lao_eea>@judypn_la).
Can you please help me identify problem with vibration or recommend what file to flash, as I cannot find any EU V405UA fw.
Thanks in advance
Click to expand...
Click to collapse
You need use LGUP Dual i
sojkaCZ said:
Hello guys,
I bought new (open box) v40 on ebay and it stated V405UA unlocked. It came with Android 10 v30d.
All is working good except vibration. It doesn't vibrate at all. I tried factory reset, safe mode, application to test vibration and checking battery saver. And it doesn't work for notifications or keyboard feedback.
I contacted seller and he suggested i try to flash V40UA US android 9. I tried flashing V405UA020g_00_USC_US_OP_0424.kdz with LGUP from this forum and it showed me crossflash error (US>EU).
I then tried V405EBW android 10 V405EBW30d_00_OPEN_EU_DS_OP_1223.kdz and it showed me different crossflash error (jadypn_lao_eea>@judypn_la).
Can you please help me identify problem with vibration or recommend what file to flash, as I cannot find any EU V405UA fw.
Thanks in advance
Click to expand...
Click to collapse
You need install lgup dualmode.

AsItLies said:
I'm no expert but from that output, seems to me the software thinks it did it's job. No indications of any problem, but it may be the software tell's it to 'vibrate' and whether it does or not, doesn't matter, as it may not have any checks for errors of any kind.
Additionally, it seems pretty unlikely LG is going to put out an OS version where something as common as the vibrate function doesn't work? Have not heard of any version doing that anyway.
cheers
Click to expand...
Click to collapse
Yeah, I have similar thoughts. Thanks for help

hoangan102 said:
You need use LGUP Dual i
You need install lgup dualmode.
Click to expand...
Click to collapse
Hi,
I have already solved flashing complications.
Do I need Dual Mode for flashing or for testing in "PHONESETTING"?

How To Guide x70 Pro Plus Origin OS to FunTouch 36.9.3

Foreword: My time with Vivo has come to an end. After flashing a wrong devicecfg and accidentally rebooting my device it is now in a hard bricked state.
Vivo has locked down EDL, there is absolutely no way to flash or backup anything in EDL mode without the official Tools (namely Vivo AFTool 5.9.80).
Vivo India refers me to Vivo Germany - Vivo Germany has outsourced its customer support to bulgaria.
The people on the other side of the line know absolutely nothing about the technical aspect and refuse to put me through to anyone with any kind of knowhow.
Due to their anti consumer and anti repair attitudes I will not buy another Vivo phone.
With this out of the way: You might end up like me with a hard brick. Or without signal.
Even if this will not save you from a hard brick I can not stress this enough: Make a BACKUP! And backup your data. This will wipe your phone.
This process is IRREVERSIBLE unless you have a split ROM of the chinese Firmware or your own Backup.
THIS or BL UNLOCK will break your portrait mode. No more bokeh, neither in Origin OS nor FunTouch.
Do NOT flash fsg, modemst1 and modemst2. They are commented out in the COMMANDS file.
You do this at your own risk. As said before this might brick your device.
Unlock your Bootloader
Backup your Partitions
Download my Flash Folder and Extract it: Android File Host
Open 01COMMANDS.txt and read the instructions
Open a command shell in the same folder that you can find 01COMMANDS.txt in
Run the given commands in blocks or one after the other
If you do not have signal after flashing you might have to erase modemst1 and modemst2 partitions, so that they get replaced by the backup in fsg.
A magisk flashed boot.img and adb-modded recovery is included so you can flash it after booting up FunTouch once and backup all your partitions again.
Thanks again to @Pervokur for helping me along the way. There is definitely an easier method that involves less risky flash operations.
My phone died on the cross while I was trying to figure it out, so maybe someone else will pick up the torch.
I will not be able to offer any kind of support.

RIP @Killuminati91's Vivo, who died for the cause.
Sorry to hear that, man, you were so close to what looked like an easy switch between ROMs.
I know you said you were no developer but you are still a leap ahead of most of us here. Long do we miss the good old days where ROMs, kernels and pure innovation shortly followed our much-wanted phone when flashing a few ROMs a week was normal.
Thanks for all your help, perhaps one day there will be a way to recover your phone.

Many thanks, may I relock the bootloader when i finished change to Global rom?

amos0609 said:
Many thanks, may I relock the bootloader when i finished change to Global rom?
Click to expand...
Click to collapse
Same question

Great works I tried to relock and was successful, but the device Google Pay store CTS is not verified.

amos0609 said:
Great works I tried to relock and was successful, but the device Google Pay store CTS is not verified.
Click to expand...
Click to collapse
how did you relock the bootloader, does the portrait mode work again?

does any one change the origin os /ocean into funtouch？
version？ how to relock after it can switch to funtouch？
by the way, I saw the post on the taiwan vivo phone of fb
the second hand goods, it wrote he change the origin os into funtouch
and he sell this service , it charge 2000 nt dollars in taiwan.
maybe someone can save your phone.
Killuminati91​

I think the only problem that keeps the phone from being recognized as official FunTouch is dm-verity.
In theory both phone versions have the same exact hardware.

i'm fail in step 2 :RECREATE DYNAMIC PARTITIONS) & step 3 :FLASH DYNAMIC PARTITIONS)

I thought you fixed your issue with I think wifi or your signal, and you were good to go, and you successfully swapped over to Funtouch?? Was there other issues that you encountered that you continued to mess with it and caused your phone to get bricked? Good job getting this far and sharing the info!

stevenkh168 said:
i'm fail in step 2 :RECREATE DYNAMIC PARTITIONS) & step 3 :FLASH DYNAMIC PARTITIONS)
Click to expand...
Click to collapse
Message?
silence360 said:
I thought you fixed your issue with I think wifi or your signal, and you were good to go, and you successfully swapped over to Funtouch?? Was there other issues that you encountered that you continued to mess with it and caused your phone to get bricked? Good job getting this far and sharing the info!
Click to expand...
Click to collapse
I wanted to find a smoother solution for the dm-verity message and the constant "update to fix broken system prompts" by flash-disabling it. Noticed that portrait mode was not working anymore, so I wanted to return to OriginOS, check if it works and return to FunTouch with a more streamlined, simpler solution to write a guide. Signal was fixed but it sometimes would not connect for the first 10 minutes after a reboot.
When switching back to FunTouch I flashed boot, recovery, vendor_boot, and the vbmeta's while trying to figure out what exactly is needed to get the device recognized as IN. Was not working so I tried devcfg and accidentally rebooted before flashing more partitions. -> Bootloop without recovery / fastboot.

Killuminati91 said:
Message?
I wanted to find a smoother solution for the dm-verity message and the constant "update to fix broken system prompts" by flash-disabling it. Noticed that portrait mode was not working anymore, so I wanted to return to OriginOS, check if it works and return to FunTouch with a more streamlined, simpler solution to write a guide. Signal was fixed but it sometimes would not connect for the first 10 minutes after a reboot.
When switching back to FunTouch I flashed boot, recovery, vendor_boot, and the vbmeta's while trying to figure out what exactly is needed to get the device recognized as IN. Was not working so I tried devcfg and accidentally rebooted before flashing more partitions. -> Bootloop without recovery / fastboot.
Click to expand...
Click to collapse
did you try using the OriginOS's camera app on FuntouchOS ? I find it when u use the front facing camera, the portrait mode still work. In the other hand, the back camera is not working in portrait mode. I follow your guide and using the FuntouchOS about 2 days. Everything works fine, except the portrait mode and the AOD. Cant use it anymore.

Oh I see, now that is weird that the portrait mode is not working. So even if you switch not all functionality has returned. Thanks for the explanation. Hopefully someone can continue your work, and find a solution for a seamless transition.

Yeah, returning to Origin did not fix portraits either, so flashing the cam apk itself wouldnt work. I am not sure what exactly is causing it, I just noticed it after flashing FunTouch. Maybe it is disabled by unlocking the BL or a hidden eFuse? Dont know if its possible to get it back.
Im in contact with someone in china, vivo service center remote flashing is my last straw to get this back to work but I doubt that they will do that. A cracked AFTool 5.9.80. would solve all of ours problems but we will not see that for at least half a year i think. I've been gone from android for a few years - all the hurdles surprised me, manufacturers locking down their bootloaders and EVEN edl is kinda disappointing.

Killuminati91 said:
Yeah, returning to Origin did not fix portraits either, so flashing the cam apk itself wouldnt work. I am not sure what exactly is causing it, I just noticed it after flashing FunTouch. Maybe it is disabled by unlocking the BL or a hidden eFuse? Dont know if its possible to get it back.
Im in contact with someone in china, vivo service center remote flashing is my last straw to get this back to work but I doubt that they will do that. A cracked AFTool 5.9.80. would solve all of ours problems but we will not see that for at least half a year i think. I've been gone from android for a few years - all the hurdles surprised me, manufacturers locking down their bootloaders and EVEN edl is kinda disappointing.
Click to expand...
Click to collapse
hope to see some good news from you sir.

hi i have som big problem with flashing x70 pro plus to funtouch , can some one help me with it ?
cant flash step 2 and 3

Killuminati91 said:
Yeah, returning to Origin did not fix portraits either, so flashing the cam apk itself wouldnt work. I am not sure what exactly is causing it, I just noticed it after flashing FunTouch. Maybe it is disabled by unlocking the BL or a hidden eFuse? Dont know if its possible to get it back.
Im in contact with someone in china, vivo service center remote flashing is my last straw to get this back to work but I doubt that they will do that. A cracked AFTool 5.9.80. would solve all of ours problems but we will not see that for at least half a year i think. I've been gone from android for a few years - all the hurdles surprised me, manufacturers locking down their bootloaders and EVEN edl is kinda disappointing.
Click to expand...
Click to collapse
Update us...
have you been able to solve it?

amos0609 said:
Great works I tried to relock and was successful, but the device Google Pay store CTS is not verified.
Click to expand...
Click to collapse
NHQ Thang said:
how did you relock the bootloader, does the portrait mode work again?
Click to expand...
Click to collapse
same question

adkana4310 said:
Update us...
have you been able to solve it?
Click to expand...
Click to collapse
If u asking me so no im still on the same cant flash

redwatch99 said:
hi i have som big problem with flashing x70 pro plus to funtouch , can some one help me with it ?
cant flash step 2 and 3
Click to expand...
Click to collapse
Someone who can help me solve it ?

How To Guide FYI: NE2217 T-mobile (Carrier locked, BL locked) <== Dont Flash Any Other Region w/o reading.

!!! This is a HIGH RISK method of performing any form of modification, if you are on a T-Mobile ne2217 !!!
There are unidentified files that your device might have conflict with, and cause a bootloop!
Proceed at your own risk! You have been warned!​
OK, first lemme explain. The NE2217 (10 pro) itself does not have any special restrictions on it, unlike the CPH 2419 (10T) which is an exclusive T-Mobile variant. My guide on region swapping the CPH2419 (10T, link below) is still valid for the NE2217 (US- NA) . But there are conditions required or you will enter an infinite bootloop which becomes un-recoverable, without an edl flash. I do not have the specifics as to exactly which partitions cause this, but basically the bottom line is, IF YOU HAVE NOT UNLOCKED YOUR BOOTLOADER, EVEN IF YOU ARE SIM UNLOCKED, do not attempt to region swap.
There are a couple of partitions that are specially locked, that ONLY become write capable using the fastboot command, "Unlock Critical". Without a Bootloader unlock, the Oxygen Updater/Local Update programs, CANNOT make the needed changes to the Kernel, as well as these other important partitions, which have instructions that implicitly block changing to other regions. I cannot confirm if this exists in other countries with carrier locks, but i do know for a fact that T-Mobile has this enforced on all of the 10 Pro (ne2217) purchased through them.
As mentioned in previous threads that ive replied in, I suspected that the apps Oxygen Updater and Local Update, do not have the permissions capable to make direct changes to the boot.img, or recovery.img directly, primarily because those partitons cannot be altered while the system is currently running. These images can only be altered through Fastboot, or EDL thus the need for an MSM Tool if you cannot unlock your bootloader via conventional methods. So what happens is upon "Pre-boot" those special instructions i spoke of, take authority and put the carrier specific files, into an untouchable state that are locked behind the USERDATA partition, so these applications just copy the updated files to the inactive partition and performs the changes during the next boot, and even a hard wipe factory reset does not have the authority to erase the carrier instructions. The only way they are removed is by Unlocking your Bootloader! When you do that, the Qualcomm Processor has an embedded command, which is required to ERASE the entire Userdata partition, to protect the encrypted files protected by the bootloader lock! You can read about that by googling "Qualcomm Bootloader Unlocking".
Hope that makes sense to the majority of you. So again, the ONLY requirement for you to be able to go from 'ne2217', to any other fw is YOUR BOOTLOADER MUST BE UNLOCKED!
Failure to follow that one requirement will indeed force your device into an unusable, infinite bootloop, which can be resolved only by an EDL flash, which as of right now we do not have the tools that can perform this on CONSUMER level. You will have to RMA, your device, or go thru third party channels, which in itself is very risky, and puts you at risk of viruses/malware/wormholes/zombie-apocalypse because you must give someone full access to your computer remotely, and pray that the person only does what you requested. (NOT IDEAL).
Now if you're on a T-Mobile locked device, you are NOT hopeless... as I am on a T-Mobile locked device, and i am now bootloader unlocked as well! These two conditions are independent of each other, but trust me when i tell you that YOU DO NOT WANT TO GO THRU WHAT I HAVE EXPERIENCED, IN ORDER TO REACH THIS GOAL!
In so I will not publicly disclose how i was able to enter the real Fastboot Mode, so that i could pull the unlock code needed to request the unlock token from T-mobile.
(If you are so inclined to do this that you are willing to forgo ALL precautions and risk the possibility of bricking your device, or you have already landed yourself in an unrecoverable bootloop state, and are willing to try ANYTHING, you can join Bootloopers Anonymous, by clickiing it, and drop a message. This is a brand new telegram channel, and i will try to watch it for your requests. And again i strongly advise that you DO NOT embark on MY adventure, but if Unlocked Bootloader by Any Means Necessary is your ultimate goal, and nothing less is acceptable, i will try to help you achieve it... *** YOUR DEVICE WILL ENTER A COMPLETELY UNUSABLE STATE FOR A MINIMUM OF 7 DAYS!! *** but bear in mind that EVEN IF you have to use my method, you will be still subject to the 7-day waiting period outlined by OnePlus company policy. No one can overcome that, as the unlock token comes thru a separate division of Oppo/Oneplus that only generates the token through an automated request which is pushed after the expiration of 7 full days (1-week) has passed. YOU HAVE BEEN WARNED!)
The 10-Pro doesn't require the "In-Depth Testing" app to get your BL unlocked. That said, it also does not mean that OPPO has not designed one for this device because indeed they have. That application is individually encoded with device specifications so that only devices and regions EXPRESSLY AUTHORIZED by Oppo, can submit a request to unlock. DO NOT TRY sideloading any "In Depth Testing" apk floating around on the internet, as these can be altered to contain malware or worse, and then if your device becomes corrupted by it, Oppo can deny you an RMA on your device, thus charging you for the repair as there are warnings that you must acknowledge to even run the app, and attempting to circumvent the safeguards that this app already has in place is considered a violation of ToS.
If OPPO adds your device/region to the list of allowed devices, you will be able to download this application through OFFICIAL channels, and it will be made known to the public.
Once you are completely knowledgeable that your BL has indeed been fully unlocked, you can proceed to follow the instructions in the link to my guide below. The guide is for the CPH2419 (10T), but the instructions are completely compatible with the 10 Pro entire series, assuming your BL is unlocked. On the 10T this is not a requirement, and i honestly do not understand why this enforcement was put into our 10 Pro model, released almost a year earlier. Probably just an oversight by T-Mobile which might be corrected in future builds.
How to use Oxygen Updater + Local Update apks to switch regions.

EDIT: Local Update downgrade it currently installing
No Go, The update installed and downgraded but it just loads to the welcome screen and crashes and boot loops

supercobaltss said:
EDIT: Local Update downgrade it currently installing
No Go, The update installed and downgraded but it just loads to the welcome screen and crashes and boot loops
Click to expand...
Click to collapse
again, what most ppl are failing to do is follow my guide exactly as i defined. The VERY 1st thing you MUST DO... prior to unlocking the Bootloader... Prior to even downloading ANY rollback packages is, you MUST go and Download ANY of the Android 13 beta updates that are available in Oxygen updater. Turn on advanced mode, and select the whichever model you prefer... Its actually best to choose the region you plan on swapping to, for easier transition with the rollback package. IMHO i would always pick the EU model whenever attempting this, simply because that one usually has more bands available. But the main idea behind this is to make the phone, first BREAK the connection it has with T-Mobile's custom kernel, and modem... which is done just by upgrading to an Android 13 beta, as T-Mobile does not EVER release any beta builds, so by doing an actual OS upgrade, your phone must load the OS kernel, and several other partitions/files which i am sure that T-Mobile has branded in the 2217. Upgrading to a newer OS will without a doubt overwrite the carrier locked files, because the Upgrade comes from a higher authority in the chain of trust. Until TMO releases an update, then this is a requirement so that the rollback package of that region can safely downgrade the files, in their correct partitions. If you download a beta 13 thru oxygen updater, you can local update flash it, without problem. I did it myself to several demo devices at Tmobile stores here in Texas to test the technique, after i bricked mine by using a rollback package first!
Remember the 2217 is a T-Mobile EXCLUSIVE! No other carrier may sell this same model... but ALL of the internals are the exact same, and as im sure we are all well aware of, T-Mobile doesnt have the fastest adaptations when it comes to OS updates.
But there are several key identifiers which point to a custom made BL, Kernel, and Modem: 1. The build for all T-Mobile versions is on a revision that no other model has released... This alone could cause BL because if you flash a build that is older than the one you have currently, several files have anti-downgrade measures built into them. This is why we need the signed rollback packages to downgrade. But even if OPPO signed a rollback, unless they released one with T-Mobiles file specs, then anything you flash can create a conflict with an existing file... BL! But i know of about 13 ppl who have attempted my method, plus i just did another one myself last night for someone who contacted me and offered to compensate me royally if i would meet them since we were local logistically. 2. AFAIK, when installing a different rom to a device, you cannot downgrade the modem version. I know this is apparent with Samsung... as if you try to flash a rom with a lower modem version, it usually bricks, and you have to use odin to flash the newer modem back, in order to boot. Again this is taken care of by installing the NEWEST beta for Android 13, unless you had my situation which is, my phone CAME WITH updated security, and build already installed for October 2022. I havent heard of anyone who has said they even have the option to update theirs past August. So new purchases have to be careful. T-mobile sold mine with a blocked Fastboot, that doesnt respond to the button combo. Which clearly identifies they modified the recovery partition. 3. E-fuses have become a staple in Android devices for the past 5+ years.
Sure we have not heard of anything being in the T-mobile fw... but also who here can say that they have a FULL BUILD of the Tmo fw to examine? No one.... there is a generic 2217 build floating around that claims to be official, yet it is the ONLY build that does not have an OTA formatted file structure. All the 10 Pro OTA have been in payload.bin format, yet this happens to come only as a decrypted OFP, or a compressed OFP. *** OPPO is not directly supporting the 10 Pro 2217 or 10 T 2419 ! As these are proprietary T-Mobile builds. This is why you cannot find either of those models fw in the Oppo repository. So if OPPO doesnt release builds for TMO, then how exactly did an "Official 'OFP' for 2217" get released? *** OFP is an Official OPPO format for all the OPPO model phones. 10 Pro is still branded Oneplus, thus just about any OFP file you find in the wild, is almost 100% guaranteed NOT to be an official released build for our phones. Every package for this and the 10T that they have OFFICIALLY released, has been in Payload.bin format, because they havent released any full images yet! So in theory, who's to say that TMO didnt place an efuse into their specific model? Its only code, and if set, then it could have been burned during the initial release, or a later update, like AMAZON did with updates to the Firestick/FireTV devices, which would ONLY allow newer updates to certain files in THEIR build. That would totally explain a bootloop, because the rollback packages all push you back to 11_A.013 .... that build is from Feb-March 2022. Rolling back would almost guarantee that some files are overwritten with older components, which would cause a brick by e-fuse standards. We had to be lucky enough to catch it early in the FIrestick forum, to stop ppl from installing the update. Everyone who did, had their ability to unlock/load custom fw to their devices blocked, and there is still today no way to circumvent it. Sure new methods to mod became available, but only minimal changes, cuz the e-fuse blocked downgrading to exploitable builds. Since TMO has gone this far to stop us from modifying this phone, you can bet solidly on the fact that they have several safeguards in place to protect their investment.
Now im not trying to discourage anyone or discredit anything anyone has said or experienced regarding this phone, but look at the NUMEROUS unanswered replies to handfuls of problems that only happen to 1 or 2 ppl... they all have the same final result, but its astounding how many different scenarios ppl have found, that no one else has experienced, yet it leads to another bricked device. If this problem was rampant among a significant number of users, and it was triggered by the exact same scenario, then TMO would have to address it with an update... But all we know for sure is that there is some file(s) that is not compatible with any other model except the 2217. Til we have an EXACT culprit identified, all we can do is speculate, which is why I am going to re-label this as HIGH RISK in the OP. It has about a 40-50% chance of causing a bootloop, and about a 10% chance to leave your device unresponsive! There have been several released guides for other devices that have close to the same success rate / risk factor. All i can do is share what I have done, and what i know from personal exp.
Im sorry if anyone lands themselves on the wrong side of that equation, but it is a risk that only you can decide if its worth taking. For me, that answer is and always will be YES because i will not own a device that i do not OWN! For others this may be a touch more out of their league, and if thats true they should steer clear, until I or another user can get hold of an official TMO OTA, to examine the diff files in each.
****** Now all of that being said.... if ANYONE wishes to contribute to finding a solution to this dumpster fire, I am not asking for donations.... What i am asking, is for SOMEONE who might have a T-Mobile 10Pro on the release build, or any build PRIOR to 11_A.13 and is looking to help, we NEED an exact copy of an OTA update that might be sitting in your notifications. All updates download to the /sdcard/ partition of your phone in a folder that is accessible without root permissions. If you accept the download for the update, and DONT begin the install immediately, you can locate and pull that OTA to your computer, then delete the file from your phone, and it will cancel the update on reboot. No loss to you, but EXTREMELY HELPFUL to us, because we will have something from TMO to work with, which may give us a clue as to what we need to remove from the updater script ! *******
and FYI the signatures used to sign some of the OTA we already have, are already deciphered and as such can be used to create new signatures after making some changes to the respective regions package. But to make having these be of any value, we need to know what to take out or change in the manifest, that will prevent alterations of the files causing bootloops. If anyone can help with an upload of a TMO-OTA please share publicly or dm myself or one of the other devs who have expressed interest in this issue.
Thanks

I can probably pull the update from my wifes phone. She never updates anything. I did get my 10 pro to boot to android 13 but everything just says its disabled. This is only the 3rd phone ive done this with so ill warranty another one if i have to lol.

supercobaltss said:
EDIT: Local Update downgrade it currently installing
No Go, The update installed and downgraded but it just loads to the welcome screen and crashes and boot loops
Click to expand...
Click to collapse
Yup, this happened to me as well. Setup wizard crashes before I even get very far in it, and I've wiped multiple times trying to complete it somehow.

GuyInDogSuit said:
Yup, this happened to me as well. Setup wizard crashes before I even get very far in it, and I've wiped multiple times trying to complete it somehow.
Click to expand...
Click to collapse
Ive tried to convert multiple different ways. Upgrading to 13 basically screws you with the disabled apps BS, Downgrading just crashes the device. Either way its broken. I've went through 3 devices now messing around.

So I guess it's time to replace it, then? Crap.

GuyInDogSuit said:
So I guess it's time to replace it, then? Crap.
Click to expand...
Click to collapse
Start a RMA on OnePlus website, don't go through T-Mobile. They will have you send in phone and then either reflash your phone and send it back or just send you a new phone which is what they did when I had to do it. All that bs about voiding warranty when unlocking bootloader is just that, bs. They fix or replace without any issues but you have to go through OnePlus.

FML.
I've gotten it working for the most part, but what's most concerning is that there's no IMEI. And it doesn't charge or even acknowledge the cable. Fantastic.

jeffsga88 said:
Start a RMA on OnePlus website, don't go through T-Mobile. They will have you send in phone and then either reflash your phone and send it back or just send you a new phone which is what they did when I had to do it. All that bs about voiding warranty when unlocking bootloader is just that, bs. They fix or replace without any issues but you have to go through OnePlus.
Click to expand...
Click to collapse
I can't even request an RMA as I don't have an IMEI to provide. It's blank in the phone. I think I'm screwed. Or try T-Mobile. Dunno. This sucks.

GuyInDogSuit said:
I can't even request an RMA as I don't have an IMEI to provide. It's blank in the phone. I think I'm screwed. Or try T-Mobile. Dunno. This sucks.
Click to expand...
Click to collapse
The T-Mobile version has your IMEI sketched into the back cover of your phone. You should be able to use that.

jeffsga88 said:
The T-Mobile version has your IMEI sketched into the back cover of your phone. You should be able to use that.
Click to expand...
Click to collapse
Oh. Uh.... completely forgotten about that.

I just updated to Android 13 on the TMO NE2217, device not unlocked, still financed. And now have the option to unlock the BL.

beatbreakee said:
All updates download to the /sdcard/ partition of your phone in a folder that is accessible without root permissions. If you accept the download for the update, and DONT begin the install immediately, you can locate and pull that OTA to your computer, then delete the file from your phone, and it will cancel the update on reboot.
Click to expand...
Click to collapse
Is this still useful, with the NE2217_11_C.26 update? And either way, how can I delete it? I couldn't find anything big in /sdcard. Thanks!

deleted

psm321 said:
Is this still useful, with the NE2217_11_C.26 update? And either way, how can I delete it? I couldn't find anything big in /sdcard. Thanks!
Click to expand...
Click to collapse
^
^
^
^
^
THIS Please my phone ignored my saying no and next reboot the damn thing will go off on me ... so frustrating that even when you set the darn thing to OFF on auto update and such it STILL does this BS...
Damn TMobile and their special lock junk UGH ...
anyway ... please can one direct with a screen shot and file manager they used to find this file so I can delete the thing? ... I have tried to find it and struck out ... but having got the notification today and the Oxygen app is showing 'REBOOT' instead of 'resume' when I ignored the update previously has me thinking if I reboot I will see android 13 pop up and in this case means I will lose my whoop as something with it breaks pairing my wearable ... whoop has offered no timetable for a fix