Doesn't work to well to restore partions but backs them up great; fastboot and fastbootd do however restore perfectly.Thanks. Since TMO has released the A11 update, I think I use that to return to stock, and then carry out the process above.
Doesn't work to well to restore partions but backs them up great; fastboot and fastbootd do however restore perfectly.Thanks. Since TMO has released the A11 update, I think I use that to return to stock, and then carry out the process above.
Since me posting this I tried flashing global and didn't get signal. This is since A11 Verizon update. So might just be my carrier. Did however work on A 10 perfectlyAwesome. Thanks.
Since me posting this I tried flashing global and didn't get signal. This is since A11 Verizon update. So might just be my carrier. Did however work on A 10 perfectly
Are you making sure to go into recovery after flashing global and doing a full wipe? Factory reset . Will not boot to anything but bootloader if not.I also tried to convert again to global, I flashed the stock fastboot ROM (11.0.0-GLOBAL-OnePlus8Oxygen_15.O.30_OTA). Flashing went well but phone ended up on the bootloader screen. Tried the earlier A10 global ROM versions but with same results. So am forced back on T-Mobile.
Do not know why when the same procedure & same global ROM had worked perfectly few weeks ago?
Are you making sure to go into recovery after flashing global and doing a full wipe? Factory reset . Will not boot to anything but bootloader if not.
That's definitely your problem. Flash global rom,get to recovery one way or the other after it's finished and yes it's the screen your speaking of. English,advanced. Wipe data,factory reset. Have to wipe data when switching from one build to the next. Stinks to set-up again but that's unfortunately what has to happen..No, I did not do that.
Just to confirm, after flashing recovery, I need to go to the device recovery (which shows up in English & 2 other languages) & do a full wipe, then reset?
That's definitely your problem. Flash global rom,get to recovery one way or the other after it's finished and yes it's the screen your speaking of. English,advanced. Wipe data,factory reset. Have to wipe data when switching from one build to the next. Stinks to set-up again but that's unfortunately what has to happen..
Get the latest a11 version you can. And local upgrading will probably break data. So after you flash . Just stay where your at. You can try taking ota after flashing,if it breaks data. You just have to start over.Great, and thanks.
I am on T-Mobile Android 11. Which global version should I flash? 11.0.2.2. seems to be the latest, or does not matter as it will upgrade OTA automatically.
Get the latest a11 version you can. And local upgrading will probably break data. So after you flash . Just stay where your at. You can try taking ota after flashing,if it breaks data. You just have to start over.
It will indeed workThanks a ton. Will try & report.
It will indeed work
Thought that was your issue. Good dealWorked finally. thanks.
I tried flashing latest 11, but that did not work. So I had to MSM to 10, and then upgrade to 11. Thanks for help.Thought that was your issue. Good deal
I'm on Verizon and best I remember if your a carrier branded device & take local upgrade or system update you will loose data. Because it flashes the global modem. You can always try though. No limit on how many times we can msm.I am currently on TMO OP8 version 11.0.1.1 and want to convert to global since I have recently received my unlock token. I'm just wondering if I need to use the MSM tool to go to 10.5.7 or can I just do the following:
fastboot flash cust-unlock <unlock_token.bin>
fastboot oem unlock
Extract all files from fastboot rom zip (I downloaded 10.5.7 and 10.5.12 from here - https://sourceforge.net/projects/fastbootroms/files/OnePlus 8/)
Reboot to fastboot
Run flash-all.bat
A bunch of stuff will flash and phone will reboot twice
Complete setup (skip what I can to get to booted)
You are now on Global Rom and can upgrade to A11 with local upgrade or oxygen updater
Thanks!
I am on tmobile and took an ota update and still have data. It may be different for the Verizon model however because it's a slightly different model due to the mmwave function.I'm on Verizon and best I remember if your a carrier branded device & take local upgrade or system update you will loose data. Because it flashes the global modem. You can always try though. No limit on how many times we can msm.
And QTI telephony stuff for sure.I am on tmobile and took an ota update and still have data. It may be different for the Verizon model however because it's a slightly different model due to the mmwave function.
hi ,I am unable to unlock the bootloader. Is there any thread for step by step*** Use this at your very own risk.
***Backup your persist.img. There is a guide to fix it if needed.
*** Backup your working modem. Sometimes it is as simple as restoring it if you lose signal.
*** When flashing, you must understand the difference between fastboot and fastbootd to avoid flashing errors.
*** Backup your files in a safe place.
*** Some users are reporting that the whole thing is not working and going on a blame streak. So if you're not quite ready, please don't attempt this.
Basic Instructions: "I will test again since some users are losing signal after flashing". There is a debate whether msm and update the tmobile firmware, or flash the global. Again this is a WIP.
MSM. Here is the thread.
Unlock bootloader or re-unlock bootloader ... Enable OEM Unlock in developer options. flash token.
Fastboot
Code:fastboot flash cust-unlock <unlock_token.bin>
and now your bootloader is unlocked.Code:fastboot oem unlock
Here is the t-mobile article for the 6t. same instructions for the 8 if you're new to this.
NEXT:
Link to fastboot thread
https://forum.xda-developers.com/oneplus-8/how-to/rom-stock-fastboot-roms-oneplus-8-t4084629
Download the global fastboot rom from here.
Unzip and flash all.
Link to twrp thread:
https://forum.xda-developers.com/oneplus-8/development/recovery-unofficial-twrp-oneplus-8-t4101315
If you want to root.
Boot into twrp or flash the twrp installer. TWRP 3.3.1-10 Test by mauronofrio and or TWRP 3.3.1-10 Test Installer by mauronofrio "newer ones may work"
After booting, you can flash magisk with-in twrp and you're rooted.
I have used oxygen updater to update the firmware while rooted. After the local install, open magisk and flash on the inactive slot.
---------------
If you ever want to revert, use the msm tool. Here is the thread.
https://forum.xda-developers.com/oneplus-8/how-to/op8-unbrick-tool-to-restore-device-to-t4093043
---------
Old information from the old thread is below, if you want to use it only for reference or for backing up the FP persist
---------------
Old Instructions
Here we go .....
This is fairly new and hasn't been tested so, proceed with caution. There are more knowledgable people here. This was just tested quick and it worked.
Requirements
1-Be on T-mobile firmware and update to the latest version. If you are bootloader unlocked, you mean not be able to take OTA's and you may need to reflash with MSM and update, then unlock the bootloader again. Thread Thanks @Some_Random_Username
2 - Unlock your bootloader.
3- --! IMPORTANT: Make a TWRP backup of your MODEM because we'll restore that later, why? because t-mobile sim doesn't work on the Global Modem. You can also back everything up in TWRP just in case.
If you have OTG, make the backup there so it is safe. You can restore the modem through TWRP with the OTG.
4-Backup your persist. Otherwise you may lose the fingerprint.
You'll need root.
Code:adb shell
HTML:su
ThenCode:dd if=/dev/block/bootdevice/by-name/persist of=/sdcard/persist.img
Then copy it from from Sdcard to a safe placeCode:adb pull sdcard/persist.img
*** You may lose signal again if you update the global version. It is a WIP but keep your modem backed up!
With all the above:
It is simple. Download the global firmware and flash it through fastboot. Here is the thread
.. I tested with "10.5.5-GLOBAL-OnePlus8Oxygen_15.O.14" Thanks @mauronofrio
- Reboot to fastboot
- Unzip and flash-all
- It will reboot to the global firmware. "Now you won't get cellphone signal"
- Skip the setup and reboot to fastboot.
- reboot to twrp, do not flash it.
link to twrp thread. . I used TWRP 3.3.1-2 Test by @mauronofrioCode:fastboot boot twrp.img
- plug in the OTG or locate the backup and Restore the Modem" to get signal
- Reboot and you'll have signal.
To root. you can flash the patched boot located in the sourceforge folder " Patched-Stock-Boot" on this thread
You can also flash magisk in twrp. I prefer the patched boot.Code:fastboot flash boot filename.img
Bonus: I am running the Nolimit magisk rom Thanks @xXx
https://forum.xda-developers.com/on...gisk-rom-xxx-nolimits-11-0-speed-ram-t4088609
Thanks @Some_Ghost for testing.
Instructions for it are in the op. The link right under where he says and now your bootloader is unlockedhi ,I am unable to unlock the bootloader. Is there any thread for step by step
This is real good insight. Thank you. Let us know how it goes.I was on TMO android 11.0.1.1, patched boot. I Just factory reset and try to directly flash all of global A11 fastboot version. Got a lot of "Invalid sparse file format at header magic" errores haha and some others... so no luck. What should I try now? MSM global A11?, fastboot a earlier global version or msm a earlier version... or msm back to tmo?
Other errors are:
fastboot: error: cannot load 'opproduct.img': No such file or directory
Are those errors common?
PS: Try to flash all fastboot A10 Global, and failed to flash everything ahaha.. "remote: 'Flashing is not allowed for Critical Partitions"
PS2: Cannot MSM to Global, dont recognize my phone.
PS3: Now phone only turn on at "crushdump mode", No other mode start :'C
PS4: I've succesully MSM to tmo factory(drivers wsnt fine :$), then unlock bootloader and try to flash global A10 15_O.12 version got many errors, but android start as global without phone network, can connect to wifi, there is no OTA available:
Sending 'aop' (200 KB) OKAY [ 0.008s]
Writing 'aop' FAILED (remote: 'Flashing is not allowed for Critical Partitions
')
fastboot: error: Command failed
Sending 'bluetooth' (460 KB) OKAY [ 0.016s]
Writing 'bluetooth' FAILED (remote: 'Flashing is not allowed for Critical Partitions
')
fastboot: error: Command failed
Sending 'boot_a' (98304 KB) OKAY [ 2.345s]
Writing 'boot_a' OKAY [ 0.364s]
Finished. Total time: 3.212s
Sending 'dsp' (65536 KB) OKAY [ 1.568s]
Writing 'dsp' FAILED (remote: 'Flashing is not allowed for Critical Partitions
')
fastboot: error: Command failed
Sending 'dtbo' (8192 KB) OKAY [ 0.195s]
Writing 'dtbo' OKAY [ 0.034s]
Finished. Total time: 0.344s
Sending 'LOGO' (7784 KB) OKAY [ 0.202s]
Writing 'LOGO' FAILED (remote: '(LOGO_a) No such partition')
fastboot: error: Command failed
Sending 'modem_a' (524288 KB) OKAY [ 12.254s]
Writing 'modem_a' OKAY [ 1.970s]
Finished. Total time: 35.172s
fastboot: error: cannot load 'oem_stanvbk.img': No such file or directory
Sending 'qupfw' (56 KB) OKAY [ 0.013s]
Writing 'qupfw' FAILED (remote: 'Flashing is not allowed for Critical Partitions
')
fastboot: error: Command failed
Sending 'storsec' (20 KB) OKAY [ 0.007s]
Writing 'storsec' FAILED (remote: 'Flashing is not allowed for Critical Partitions
')
fastboot: error: Command failed
Sending 'multiimgoem' (16 KB) OKAY [ 0.011s]
Writing 'multiimgoem' FAILED (remote: 'Flashing is not allowed for Critical Partitions
')
fastboot: error: Command failed
Sending 'uefisecapp' (124 KB) OKAY [ 0.009s]
Writing 'uefisecapp' FAILED (remote: 'Flashing is not allowed for Critical Partitions
')
fastboot: error: Command failed
Sending 'reserve' (397888 KB) OKAY [ 9.275s]
Writing 'reserve' FAILED (remote: '(reserve_a) No such partition')
fastboot: error: Command failed
Sending 'recovery' (102400 KB) OKAY [ 2.431s]
Writing 'recovery' OKAY [ 0.454s]
Finished. Total time: 3.419s
Sending 'vbmeta' (8 KB) OKAY [ 0.003s]
Writing 'vbmeta' OKAY [ 0.002s]
Finished. Total time: 0.059s
Sending 'vbmeta_system' (4 KB) OKAY [ 0.004s]
Writing 'vbmeta_system' OKAY [ 0.002s]
Finished. Total time: 0.059s
Sending 'opproduct' (48828 KB) OKAY [ 1.152s]
Writing 'opproduct' FAILED (remote: 'Flashing is not allowed for Critical Partitions
')
fastboot: error: Command failed
Rebooting into fastboot OKAY [ 0.003s]
< waiting for any device >
PS5: I start over again, msm tmo a10, then unlock bootloader, try again flash all fastboot img of global A10(15.O.12) with same error and all the same, restart into fastboot to re lock bootloader and see if I can now OTA and the phone got corrupted after re locking xD... I think its because I have MSM opened BEWARE! will try again...
PS6: I start all over again, and instead flashall global A10 15.O.12 I flashall A10 15.O.21... now no errors, start with phone network and can also OTA! Will report anything if something wrong...
Thank you
That's what I did was will back to the latest version of 10 and then did the flash all to the global version of 10 and from there did the OTA go version 11 and all is good nowwhat global ROM do you flash it? I have same trouble with 10.5.3... but 10.5.12 was fine, I have to rollback to my tmo factory version before win MSM.
fastboot flash cust-unlock <unlock_token.bin>
fastboot oem unlock
adb shell
su
dd if=/dev/block/bootdevice/by-name/persist of=/sdcard/persist.img
adb pull sdcard/persist.img
fastboot boot twrp.img
fastboot flash boot filename.img
You are correct msm. Unlock bl. Flash all. Update. But I'm here to tell you guys I took the bootloader lock plunge and came out just fine??? as you can see I'm on T-Mobile with signal and a locked bootloader which you can tell by the L1 widevine cert I have ?I don't think that's correct. The OP stated differently about 10 posts ago. MSM, then unlock bootloader, then flash all, then update. Pretty sure the OP is correct
Thats what I'm saying, this is to flash rom, it not necessarily converting the phone to a global phone since it still need Tmobile Modem bin file in order to be function as a phone. If you take the phone outside the U.S it questionable if it works, that is why I say this is only for Dev Rom and in this case stock global rom but it is not a global phone.
It at least we can run different firmwares on T-Mobile. You could try the global msm on T-Mobile and report back. As being sim unlocked depends on the bands enabled in other countries but should work with any sim.again, this does not make it a global sim unlock phone, you are flashing a previous Tmobile Modem on top of a Global rom.