One Plus 8 5G, a few questions

[Two Sheets]

I was here back in the 2008/09 era. I got a new One Plus 8 5G (T-Mobile) direct from One Plus. It's brand new T-Mobile Version. This device is network unlocked (whatever that means) I did the updates to Android 11 and Oxygen OS. Factory reset and checked to make sure the network unlocked feature was greyed out. It wasn't, so I unlocked it again. It's greyed out again. Always greyed out unless you factory reset it.

I have it on Verizon but I have T-mobile network service as well. The One Plus messages (default app) is broken, only sends but does not receive. Google messages does it all without any text issues. Could be OS related or version related , but One Plus Messages has been a known issue with the One Plus 8 models.

I want to run the Global Rom. I downloaded the official global rom from One Plus, put it in my root storage menu. A youtube video says that you should keep it there until another update is released. At that point I can use the system update to point to (local upgrade) the global rom in my storage and install it. This is more of a hack without unlocking the boot loader. One Plus will send me a token to unlock the bootloader if I request it.

I want it to be a clean phone good on any network with the global rom and no bloatware. Do I need the token to install the global rom? The youtube video guy had Android 11 on it when performing his global rom install vs. Android 10 to global rom. The phone came with Android 10.

 

[Evender99]

Yes u need the unlock token to switch to global rom. Tmo rom is cancer, request for bootloader unlock and use the fastboot method to install global oxygen os and profit.

 

[Two Sheets]

Anybody know where to find the correct windows 10 USB drivers for OnePlus phones. On the bright side, I can't brick my phone if I don't have the correct USB drivers.

 

[Two Sheets]

Ok, I got the USB drivers working.

Now I am hung up on this part below (Step 3) I can't get the unlock code. The filename, directory name, or volume label syntax is incorrect. After entering all the info in Step 4 on the 3rd entry with the oem get unlock code.

I enabled developer mode, Enabled Oem lock, downloaded the ADB software etc.

Step 4. Enter fastboot mode to get unlock code​

1. Download “fastboot_windows.zip” and unzip it on your computer. Remember the “root directory ”
2. Power off your OnePlus 6T. Press and hold“Volume +”and “Volume -”.Then Press power key to enter “fastboot mode”
3. Connect to your computer > Command：cd “root directory ”> Command: fastboot.exe oem get_unlock_code

 

[Two Sheets]

Using this thread as a notebook. >>>>> fastboot oem get_unlock_code <<<<<<< is the correct way to get the unlock code.

If someone can give me a link to the correct USB drivers for the Oneplus 8, I can get this thing unlocked.

Right now the phone hangs on "waiting for device". I need USB drivers that will work in fast boot. I switched the USB to MTP (file transfer) in developer settings, but it does not translate to fast boot.

 

[Two Sheets]

Update, I tend to learn through osmosis. A little sleep and the insight downloaded upon thee. Ok, so I submitted my OnePlus Unlock token form.

All I want is the Global Rom when all is said and done. I am waiting on a Verizon 5G sim card. The 4G sim card from my old phone has problems receiving texts. I think it has more to do with the 4G sim card on a 5G phone. The phone works perfect on the T-mobile network.

 

[Two Sheets]

For the life of me I cannot figure out how to flash my unlock token into my OnePlus 8

I am in fastboot mode. I have the root files in the correct order. The instructions say Command: fastboot flash cust-unlock <unlock_token.bin>

My file is unlock_code.bin


What is the correct syntax to write to get the cmd to recognize my target file unlock_code.bin and flash it to unlock my phone. In the past the instructions have been wrong. With DOS codes you have to have it exact or you get syntax error.

 

[Two Sheets]

Fixed, after a few minutes of suicidal ideations, I got my unlock token to take. My bootloader is now unlocked.

 

[thattechguy_69]

For the life of me I cannot figure out how to flash my unlock token into my OnePlus 8

I am in fastboot mode. I have the root files in the correct order. The instructions say Command: fastboot flash cust-unlock <unlock_token.bin>

My file is unlock_code.bin


What is the correct syntax to write to get the cmd to recognize my target file unlock_code.bin and flash it to unlock my phone. In the past the instructions have been wrong. With DOS codes you have to have it exact or you get syntax error.

you can use the TOOL ALL IN ONE which helps you unlock the bootloader and does the cmd stuff for you. Link on my thread and scroll down: https://forum.xda-developers.com/t/...nternational-with-bootloader-re-lock.4345305/

 

[Two Sheets]

That wouldn't be any fun. I have to learn to do this myself without making mistakes. The end justifies the means, my bootloader is unlocked now.

Can you point me to the correct T-mobile stock Android 10 OS rom file? I am on Android 11 and need the stock file to be able to load the global rom.

 

[FoxyDrew]

That wouldn't be any fun. I have to learn to do this myself without making mistakes. The end justifies the means, my bootloader is unlocked now.

Can you point me to the correct T-mobile stock Android 10 OS rom file? I am on Android 11 and need the stock file to be able to load the global rom.

Here's T-MO Android 10. After flashing re-unlock the bootloader and flash this version of the GLOBAL ROM in fastboot. After succefully on Global, just boot up and take the OTA to the latest version and your golden.

 

[FoxyDrew]

That wouldn't be any fun. I have to learn to do this myself without making mistakes. The end justifies the means, my bootloader is unlocked now.

Can you point me to the correct T-mobile stock Android 10 OS rom file? I am on Android 11 and need the stock file to be able to load the global rom.

The T-MO Android 10 link I gave you is via MSM tool as thats the only version of stock firmware we have for Android 10 on T-MO. If you've never used MSM tool before you might have driver issues, DM me if you need.

Edit: My first post had the wrong link for the Global ROM you need. HERE is the correct link and I updated my post above too.

 

[Two Sheets]

I am confused here. The MSM tool is asking me for passwords. I thought it was plug and play. Factory resetting my phone deleted the phone drivers in Windows 10.

 

[Two Sheets]

And the next question. If the Android 11 version (on my phone) is older than the Global Rom from OnePlus on Android 11. Why can't I just flash the global version now that my bootloader is unlocked?

 

[Two Sheets]

Ok, I fixed my connection issues. Now the question. What state do I load my phone into to get the updates started via MSM tools? I have the correct ROm, but I don't know how to get it started.

 

[Two Sheets]

I am on stock Android 10 now. I am having troubles installing the 10.5.12 global rom. When I use the flash all bat command line in the rom. It starts fine but hangs with "waiting for device"

Below is what the command prompt says from my Rom flash attempts. The same thing happened 2x. It hangs on < waiting for any device >. I left it on for 30 minutes without progress at that point.


Do you want to wipe all the data ( Reccomended )[Y/N]?y

Erasing 'userdata' OKAY [ 0.275s]



F2FS-tools: mkfs.f2fs Ver: 1.12.0 (2018-11-12)



Info: Disable heap-based policy

Info: Debug level = 1

Info: Trim is disabled

Info: Set conf for android

Info: Segments per section = 1

Info: Sections per zone = 1

Info: sector size = 512

Info: total sectors = 210903704 (102980 MB)

Info: zone aligned segment0 blkaddr: 512

Info: add quota type = 0 => 4

Info: add quota type = 1 => 5

[f2fs_init_sit_area: 535] Filling sit area at offset 0x00600000

[f2fs_init_nat_area: 569] Filling nat area at offset 0x00e00000

[f2fs_write_root_inode:1147] Writing root inode (hot node), 1c000 0 200 at offset 0x00114688

[f2fs_write_default_quota:1223] Writing quota data, at offset 0001c601, 0001c602

[f2fs_write_qf_inode:1318] Writing quota inode (hot node), 1c000 0 200 at offset 0x00114689

[f2fs_write_default_quota:1223] Writing quota data, at offset 0001c603, 0001c604

[f2fs_write_qf_inode:1318] Writing quota inode (hot node), 1c000 0 200 at offset 0x00114690

[f2fs_update_nat_root:1372] Writing nat root, at offset 0x00000e00

[f2fs_add_default_dentry_root:1567] Writing default dentry root, at offset 0x0001c600

Info: Overprovision ratio = 0.620%

Info: Overprovision segments = 645 (GC reserved = 330)

[f2fs_write_check_point_pack: 713] Writing main segments, cp at offset 0x00000200

[f2fs_write_check_point_pack: 850] Writing Segment summary for HOT/WARM/COLD_DATA, at offset 0x00000201

[f2fs_write_check_point_pack: 877] Writing Segment summary for HOT_NODE, at offset 0x00000202

[f2fs_write_check_point_pack: 889] Writing Segment summary for WARM_NODE, at offset 0x00000203

[f2fs_write_check_point_pack: 900] Writing Segment summary for COLD_NODE, at offset 0x00000204

[f2fs_write_check_point_pack: 908] Writing cp page2, at offset 0x00000205

[f2fs_write_check_point_pack: 928] Writing NAT bits pages, at offset 0x000003fe

[f2fs_write_check_point_pack: 949] Writing cp page 1 of checkpoint pack 2, at offset 0x00000400

[f2fs_write_check_point_pack: 968] Writing cp page 2 of checkpoint pack 2, at offset 0x00000405

[f2fs_write_super_block:1001] Writing super block, at offset 0x00000000

Info: format successful

Sending 'userdata' (85 KB) OKAY [ 0.009s]

Writing 'userdata' OKAY [ 0.002s]

Erasing 'metadata' OKAY [ 0.001s]

Erase successful, but not automatically formatting.

File system type raw not supported.

Finished. Total time: 6.233s

Sending 'boot_a' (98304 KB) OKAY [ 2.271s]

Writing 'boot_a' OKAY [ 0.413s]

Finished. Total time: 2.780s

Sending 'dtbo' (8192 KB) OKAY [ 0.191s]

Writing 'dtbo' OKAY [ 0.043s]

Finished. Total time: 0.253s

Sending 'modem_a' (524288 KB) OKAY [ 12.122s]

Writing 'modem_a' OKAY [ 1.955s]

Finished. Total time: 14.523s

Sending 'recovery' (102400 KB) OKAY [ 2.361s]

Writing 'recovery' OKAY [ 0.392s]

Finished. Total time: 2.857s

Sending 'vbmeta' (8 KB) OKAY [ 0.008s]

Writing 'vbmeta' OKAY [ 0.001s]

Finished. Total time: 0.021s

Sending 'vbmeta_system' (4 KB) OKAY [ 0.010s]

Writing 'vbmeta_system' OKAY [ 0.001s]

Finished. Total time: 0.023s

Rebooting into fastboot OKAY [ 0.002s]

< waiting for any device >

 

[FoxyDrew]

I am on stock Android 10 now. I am having troubles installing the 10.5.12 global rom. When I use the flash all bat command line in the rom. It starts fine but hangs with "waiting for device"

Below is what the command prompt says from my Rom flash attempts. The same thing happened 2x. It hangs on < waiting for any device >. I left it on for 30 minutes without progress at that point.


Do you want to wipe all the data ( Reccomended )[Y/N]?y

Erasing 'userdata' OKAY [ 0.275s]



F2FS-tools: mkfs.f2fs Ver: 1.12.0 (2018-11-12)



Info: Disable heap-based policy

Info: Debug level = 1

Info: Trim is disabled

Info: Set conf for android

Info: Segments per section = 1

Info: Sections per zone = 1

Info: sector size = 512

Info: total sectors = 210903704 (102980 MB)

Info: zone aligned segment0 blkaddr: 512

Info: add quota type = 0 => 4

Info: add quota type = 1 => 5

[f2fs_init_sit_area: 535] Filling sit area at offset 0x00600000

[f2fs_init_nat_area: 569] Filling nat area at offset 0x00e00000

[f2fs_write_root_inode:1147] Writing root inode (hot node), 1c000 0 200 at offset 0x00114688

[f2fs_write_default_quota:1223] Writing quota data, at offset 0001c601, 0001c602

[f2fs_write_qf_inode:1318] Writing quota inode (hot node), 1c000 0 200 at offset 0x00114689

[f2fs_write_default_quota:1223] Writing quota data, at offset 0001c603, 0001c604

[f2fs_write_qf_inode:1318] Writing quota inode (hot node), 1c000 0 200 at offset 0x00114690

[f2fs_update_nat_root:1372] Writing nat root, at offset 0x00000e00

[f2fs_add_default_dentry_root:1567] Writing default dentry root, at offset 0x0001c600

Info: Overprovision ratio = 0.620%

Info: Overprovision segments = 645 (GC reserved = 330)

[f2fs_write_check_point_pack: 713] Writing main segments, cp at offset 0x00000200

[f2fs_write_check_point_pack: 850] Writing Segment summary for HOT/WARM/COLD_DATA, at offset 0x00000201

[f2fs_write_check_point_pack: 877] Writing Segment summary for HOT_NODE, at offset 0x00000202

[f2fs_write_check_point_pack: 889] Writing Segment summary for WARM_NODE, at offset 0x00000203

[f2fs_write_check_point_pack: 900] Writing Segment summary for COLD_NODE, at offset 0x00000204

[f2fs_write_check_point_pack: 908] Writing cp page2, at offset 0x00000205

[f2fs_write_check_point_pack: 928] Writing NAT bits pages, at offset 0x000003fe

[f2fs_write_check_point_pack: 949] Writing cp page 1 of checkpoint pack 2, at offset 0x00000400

[f2fs_write_check_point_pack: 968] Writing cp page 2 of checkpoint pack 2, at offset 0x00000405

[f2fs_write_super_block:1001] Writing super block, at offset 0x00000000

Info: format successful

Sending 'userdata' (85 KB) OKAY [ 0.009s]

Writing 'userdata' OKAY [ 0.002s]

Erasing 'metadata' OKAY [ 0.001s]

Erase successful, but not automatically formatting.

File system type raw not supported.

Finished. Total time: 6.233s

Sending 'boot_a' (98304 KB) OKAY [ 2.271s]

Writing 'boot_a' OKAY [ 0.413s]

Finished. Total time: 2.780s

Sending 'dtbo' (8192 KB) OKAY [ 0.191s]

Writing 'dtbo' OKAY [ 0.043s]

Finished. Total time: 0.253s

Sending 'modem_a' (524288 KB) OKAY [ 12.122s]

Writing 'modem_a' OKAY [ 1.955s]

Finished. Total time: 14.523s

Sending 'recovery' (102400 KB) OKAY [ 2.361s]

Writing 'recovery' OKAY [ 0.392s]

Finished. Total time: 2.857s

Sending 'vbmeta' (8 KB) OKAY [ 0.008s]

Writing 'vbmeta' OKAY [ 0.001s]

Finished. Total time: 0.021s

Sending 'vbmeta_system' (4 KB) OKAY [ 0.010s]

Writing 'vbmeta_system' OKAY [ 0.001s]

Finished. Total time: 0.023s

Rebooting into fastboot OKAY [ 0.002s]

< waiting for any device >

This is a driver issue. Download the latest Google USB drivers and make sure your device is showing up correctly as "Android Bootloader Interface" in device manager.