T-mobile OP7T flashed to Global Rom - Can I re-lock? - OnePlus 7T Questions & Answers

The Netflix app (not aware of others yet) is no longer working.
Should I re-lock the bootloader to fix this issue? I think it's just a simple command with fastboot:
Code:
fastboot oem lock
Will the cause some problems? I read online the locking the bootloader will cause issues like a "device corrupt" screen.
I only needed global rom for the dual sim capability. I don't need root.
Please advise.

I have coverted two 6T TMo's and three 7t's to Global, the last 7T when I used the fastboot OEM Lock command it bricked the phone, using the All in one tool, so I unbricked, using msm, then unlocked bootloader, then Flashed to TMO, then reflashed to Global, and used fastboot command and it Bricked the phone again, as you mentioned "device corrupt" Then I redid the whole process again and left the bootloader unlocked.
I would like to know why the first 4 phones I locked back after taking from TMO Brand to Global, right after they were converted and Did Not Brick, but the last phone 7t bricked it twice, so I left it alone.
I read somewhere by someone, they did not recommend Locking after change to global. As it would brick or worse. I dont understand how I could do 4 phones no issue, last phone bricked twice.. ????

Related

Accidentally locked bootloader

Alright guys, I was trying to fix my fingerprint (which I ended up doing) by flashing the global dev ROM 7.8.31 via fastboot with the miflash tool but I accidentally locked the bootloader while doing so. My phone came with the bootloader unlocked and now I can no longer unlock the bootloader. in developper options, the OEM unlocking option is enabled but no matter what I do in fastboot, the process simply does not work. I get the remote token verification has failed message. I have tried every freakin guide out there but my phone now refuses to get unlocked. I can't flash anything with miflash tool anymore, it just says failed, even when trying to flash the global dev 7.8.31 ROM. Anyone can help me here? Xiaomi says my device is unsupported for unlocking yet it was unlocked from the start........
What i did was the official unlock guide from xiaomi where you will get the code from them. Sadly you have to wait for 3days to be able to unlock them again.
Well check this thread...
en.miui.com/thread-781303-1-1.html
You can reapply if you got rejected
blaspheme000 said:
What i did was the official unlock guide from xiaomi where you will get the code from them. Sadly you have to wait for 3days to be able to unlock them again.
Click to expand...
Click to collapse
Well I did that but it kept on saying I had too many IP requests of sorts but I used TunnelBear and set my location to Hong Kong and that allowed me to bypass that and the request was passed through. Surprisingly, I got a message 4 hours later that said I was able to unlock it instead of the 2-7 days it took for most people to get theirs
Same happened to me. I re-lock bootloader to install android pay, and bricked my phone.
Have to reboot in EDL mode (after >50 tries) and flash again.
But... Flashed a locked bootloader version, so i have to request for official unlock (phone came unlocked)
Now I have unlocked bootloader, with Magisk and Safety Net module with Android Pay working fine.
PS: i also had the IP problem. Used a Chinese proxy to override restriction.

Tmobile Oneplus 7t - Relocked Bootloader Stucks in Your device is corrupt. It can't be trusted and will not boot

Hi,
I have recently bought a T-mobile version of OP7T. Even though T-Mobile unlocked the network permanently, I still didn't like T-mobile branding at the start, plus I wanted Stock OxygenOs. So what did I do?
(No root and No TWRP)
1. I've Unlocked the bootloader via the method in this post. Stage-1
2. I have flashed the stock rom which I downloaded from this post. Stage-2
3. Phone loads up perfectly fine and now I have stock OOS. to make sure everything is fine, I also did a factory reset and re-flashed the stock rom to make sure there's no track of previous roms.
4. I then wanted to relock the bootloader in order to keep my device safe and enjoy having a normal device like any others without the ugly message at the startup.
5. So I put it in fastboot mode and executed "fastboot flashing lock" or "fastboot oem lock" and it gave me the options and I locked the bootloader.
6. after this, I can't do anything else. it keeps showing me the page where it says Your device is corrupt. It can't be trusted and will not boot and in order to get rid of I need to keep unlocking the devices relfashing everything and the rest of the story.
I've read all the accurate and inaccurate infos on forums where another guy claims when he did turn everything to stock (recovery + rom + factory reset) things go back to normal and he's done. in my case it doesn't work.
Please help me, how I can be able to relock the bootloader without running into Your device is corrupt. It can't be trusted and will not boot.
Thanks.
First I think no help is stupid, since that is the regular way of doing it. Second you should have read extensively before doing what you did. T-mobile is very specific device. What he probably didn't mention is that you need the original rom t-mobile branded, since you need original software to be able to relock bootloader. I would recommend use msm- tool to recover you device. Read carefully and next time just be sure that what you are doing is informed.
I have unlocked the device and installed everything. the phone works like a charm.
My only problem is that I can't re-lock the bootloader.
bahadorkh said:
I have unlocked the device and installed everything. the phone works like a charm.
My only problem is that I can't re-lock the bootloader.
Click to expand...
Click to collapse
That was my point in order to relock your device you must have the original firmware that the phone came with if it's t-mobile. Installed in both slots. Then you can relock you device.
Please try this thread
[OP7T T-MOBILE][OOS 11.0.1.5 HD63CB] Unbrick tool to restore your device to OxygenOS
Disclaimer: By attempting any of the processes listed in this thread you accept full responsibility for your actions. I will not be held responsible if your device stops working, catches fire, or turns into a hipster and claims to have been...
forum.xda-developers.com
After the first boot you must update via OTA, then after the 7T reboots you can go back into the bootloader and relock it. I'm typing this message out on my T-Mobile 7T running the Global OOS 11 version. _ANY_ modification to the system whatsoever will cause the "Device is Corrupt" error, due to a mismatch of the keys used by OnePlus to sign the firmware. I've attached a screenshot of my "About phone" section as proof of the conversion, however, I can't show proof of my bootloader's state because I don't have access to a PC at the moment and *#*#7378423#*#* didn't work, neither did *#*#7378423*#*#. If I remember to the next time I'm near a PC I'll add proof of that too.
For further reading see::
1.) https://source.android.com/security/verifiedboot/boot-flow#locked-devices-with-custom-key-set
And
2.) https://source.android.com/security/verifiedboot/dm-verity
P.s. I do realize that I'm almost a year late to this discussion, but I thought knowing would/could still be useful to someone.

Hello figuring out what device I have

The title probably isn't chest, but I purchased what was supposed to be the HD1905 off of eBay. Well I got sent a HD1907. It appears that is already the global firmware (I think) on it so I'm guessing they did the conversion without bootloader unlocking to pass it off as the unlocked version.
Anyways does it appear in correct and I can start flashing the hotdogb ROMs after I get my unlock code from OnePlus to unlock this bootloader? I have been away from Android for a long time and returned to Samsung so it's basically locked down too. Honestly I'm much happier with the OnePlus I just hate this theme they did in their new os so want to try some more AOSP style
If your bootloader is unlocked, you should have the warning boot splash screen saying this device is unsecure. If so, u don't need OnePlus unlock code. You should get into bootloader mode which will also say "unlocked" on the last line in red.
A Comprehensive Guide on How to Unlock and Relock the Bootloader on OnePlus 8T
A comprehensive guide on how to unlock the bootloader on OnePlus 8T. Further learn how to relock the bootloader after restoring stock OxygenOS software.
www.thecustomdroid.com
See photo of warning boot splash screen at this link
How to Unlock the Bootloader on Your OnePlus 7 Pro
The OnePlus 7 Pro is truly the best phone that the company has ever created to date — it's even one of the hottest phones around regardless of OEM. It offers an awesome display with minimal bezels, a smooth 90-hertz refresh rate, a pop-up selfie camera, and the best triple camera system in a...
oneplus.gadgethacks.com
See photo of warning boot splash screen in bootloader or fastboot mode
[CLOSED] T-Mobile 7T Conversion to International WITHOUT unlocked bootloader/SIM unlock!
Here is a patched MSM download tool for TMobile OP7T. It will bypass the need to sim unlock before unlocking the bootloader, and will also bypass the need of an unlock token file from OnePlus (hence skip the wait period of 1 week to get the...
forum.xda-developers.com
This is how to truly convert hd1907 from BL locked, sim-locked, T-Mobile to unlocked Global or International
Thanks guys. No the bootloader is still locked which is why I have requested the code from OnePlus. Figured I'd do it correctly which will also give my note 20 time to return in case I screw up . I guess to be safe I'll do the conversion myself and then flash a ROM. Now to decide which one I want to try first
Or i guess thank you HueyT I didn't even notice you were the only response
Yapp is best for hd1907 converted to global

Re-locking Bootloader

Hello!
So, I've purchased a T-Mobile LG G8 ThinQ phone for use in Canada and wanted to remove the T-Mobile splash.
After reading a bit on the forums here, it seems like it'll be too complex for someone like me. (I'm lazy)
So, I uninstalled Magisk, which supposedly uninstalls root and I'm looking to relock my boot loader.
Just I'm having a hard time getting back into bootloader with the vol- and power button method, and using adb to reboot into bootloader doesn't seem to give the desired results.
The phone just reboots like normal with the unlocked bootloader warning.
Reason I wanna relock it is so that I can use Android Pay again and using Magisk Hide or the alternative would require them to give a guaranteed result.
One day it could be patched and I won't be near a PC to resolve the issue and I personally don't like carrying my wallet.
cheddarest said:
Hello!
So, I've purchased a T-Mobile LG G8 ThinQ phone for use in Canada and wanted to remove the T-Mobile splash.
After reading a bit on the forums here, it seems like it'll be too complex for someone like me. (I'm lazy)
So, I uninstalled Magisk, which supposedly uninstalls root and I'm looking to relock my boot loader.
Just I'm having a hard time getting back into bootloader with the vol- and power button method, and using adb to reboot into bootloader doesn't seem to give the desired results.
The phone just reboots like normal with the unlocked bootloader warning.
Reason I wanna relock it is so that I can use Android Pay again and using Magisk Hide or the alternative would require them to give a guaranteed result.
One day it could be patched and I won't be near a PC to resolve the issue and I personally don't like carrying my wallet.
Click to expand...
Click to collapse
I'm not an expert (or even that experienced with phone flashing), but a li'l Googling gives this result. The relevant part being:
Re-locking the bootloader​To re-lock the bootloader:
For newer devices (2015 and higher):
fastboot flashing lock
For older devices (2014 and lower):
fastboot oem lock
Note: Re-locking the bootloading on a Motorola Xoom erases all user data (including the shared USB data).
blaacksheep said:
I'm not an expert (or even that experienced with phone flashing), but a li'l Googling gives this result. The relevant part being:
Re-locking the bootloader​To re-lock the bootloader:
For newer devices (2015 and higher):
fastboot flashing lock
For older devices (2014 and lower):
fastboot oem lock
Note: Re-locking the bootloading on a Motorola Xoom erases all user data (including the shared USB data).
Click to expand...
Click to collapse
Sure, I'll try that if you can help me figure out why I can't get back into the bootloader.
You need to use QFIL to put flash back the engineering abl file to get fastboot. Then you can run the command.
armodons said:
You need to use QFIL to put flash back the engineering abl file to get fastboot. Then you can run the command.
Click to expand...
Click to collapse
Thank you! That worked, I was flashing abl_a and abl_b with the backup images to see if that did anything.

Bricked Mi 10T - Bootloader Re-Locked - MIUI 13

I have a Mi 10T purchased in Italy, and therefore coming factory loaded with a "branded" firmware RJDEUHG. It should be a Windtre modded ROM, please correct me if I'm wrong.
The latest known working ROM was the miui_APOLLOEEAHGGlobal_V12.5.3.0.RJDEUHG_da9e1c75b5_11.0.
Tired of waiting for the slow updates, compared to the unbranded global rooms, I decided to de-brand the phone and upgrade to a stock RJDEUXM.
But none of the XM firmware would load from recovery, therefore I applied and successfully unlocked the bootloader.
With the bootloader unlocked I managed to successfully flash
apollo_eea_global_images_V13.0.2.0.SJDEUXM_20220329.0000.00_12.0_eea_ad6f7ce846
apollo_eea_global_images_V12.5.12.0.RJDEUXM_20220208.0000.00_11.0_eea_664a15ed19
but both got stuck in a bootloop right after flashing.
During one of the many attempts, I used the MiFlash tool and accidentally left the default Flash & Lock option, the flashing was successful and the bootloader was locked.
At the moment I'm on V13.0.2.0.SJDEUXM, and can load onto bootloader and recovery, while, as mentioned before, the system won't load and get stuck in bootloop.
If I try to unlock the bootloader once again, the MiUnlock does not recognize the phone while in fastboot mode, remaining in the "Not connected to the phone" screen.
Any help would be really appreciated.
maybe, this is the solution, seems the same issue
https://c.mi.com/thread-3265050-1-0.html
fastboot devices
fastboot continue
if you have some lucky, boot normally
otherwise follow all the step
bye

Categories

Resources