[GUIDE] De-branding Your 3 Handset

[v4ndr4k3]

For best results I recommend using a Ubuntu live disk when flashing the images or make a small dual boot on your PC dedicated to flashing your phone.[/QUOTE]

can you give instructions on how to use Ubuntu live disk when flashing the images? thank you!

 

[addicted2phones]

tried all 3 drivers that cpomes in that still wont talk to pc in dl mode im on rs3

I also had that problem, I had to restart my laptop and then it worked. When you browse for the drivers from device manger I’d select “let me pick from a list of devices” then select another icon, (sorry not in front of my computer so can’t tell you further)

But from there I could select the adb drivers and some how it connected.

Remember your when checking adb devices it might you might have to use adb devices -I 0x1532 and might respond to that like mine did.

 

[lwp2013]

Is it possible to get command lines for Mac use? I know the ADB install side, I had a pixel so didn't bother with anything like this, havent tinkered with an android phone in ages. Regards

 

[ayaz51]

Flash all file

ok managed to figure out command lines but theres seems to an issue with the flash all file, the comand lines are coming up with the following

./flash_all.sh: line 3: fastboot: command not found
./flash_all.sh: line 5: fastboot: command not found
./flash_all.sh: line 7: fastboot: command not found
./flash_all.sh: line 9: fastboot: command not found
./flash_all.sh: line 11: fastboot: command not found
./flash_all.sh: line 13: fastboot: command not found
./flash_all.sh: line 15: fastboot: command not found
./flash_all.sh: line 17: fastboot: command not found
./flash_all.sh: line 19: fastboot: command not found
./flash_all.sh: line 21: fastboot: command not found
./flash_all.sh: line 23: fastboot: command not found
./flash_all.sh: line 25: fastboot: command not found
./flash_all.sh: line 27: fastboot: command not found
./flash_all.sh: line 29: fastboot: command not found
./flash_all.sh: line 31: fastboot: command not found
./flash_all.sh: line 33: fastboot: command not found
./flash_all.sh: line 35: fastboot: command not found
./flash_all.sh: line 37: fastboot: command not found
./flash_all.sh: line 39: fastboot: command not found
./flash_all.sh: line 41: fastboot: command not found
./flash_all.sh: line 43: fastboot: command not found
./flash_all.sh: line 45: fastboot: command not found
./flash_all.sh: line 47: fastboot: command not found
./flash_all.sh: line 49: fastboot: command not found
./flash_all.sh: line 51: fastboot: command not found
./flash_all.sh: line 53: fastboot: command not found
./flash_all.sh: line 55: fastboot: command not found
./flash_all.sh: line 57: fastboot: command not found
./flash_all.sh: line 59: fastboot: command not found
./flash_all.sh: line 61: fastboot: command not found
./flash_all.sh: line 63: fastboot: command not found
./flash_all.sh: line 65: fastboot: command not found
./flash_all.sh: line 67: fastboot: command not found
./flash_all.sh: line 69: fastboot: command not found
./flash_all.sh: line 71: fastboot: command not found
./flash_all.sh: line 73: fastboot: command not found
./flash_all.sh: line 75: fastboot: command not found
./flash_all.sh: line 77: fastboot: command not found
./flash_all.sh: line 79: fastboot: command not found
./flash_all.sh: line 81: fastboot: command not found
./flash_all.sh: line 83: fastboot: command not found
./flash_all.sh: line 85: fastboot: command not found
./flash_all.sh: line 87: fastboot: command not found
./flash_all.sh: line 89: fastboot: command not found
./flash_all.sh: line 91: fastboot: command not found
./flash_all.sh: line 93: fastboot: command not found
./flash_all.sh: line 95: fastboot: command not found
./flash_all.sh: line 97: fastboot: command not found
./flash_all.sh: line 99: fastboot: command not found
./flash_all.sh: line 101: fastboot: command not found
./flash_all.sh: line 103: fastboot: command not found
./flash_all.sh: line 105: fastboot: command not found
./flash_all.sh: line 107: fastboot: command not found
./flash_all.sh: line 109: fastboot: command not found
./flash_all.sh: line 111: fastboot: command not found
./flash_all.sh: line 113: fastboot: command not found

any ideas?

 

[eoghan2t7]

ok managed to figure out command lines but theres seems to an issue with the flash all file, the comand lines are coming up with the following

./flash_all.sh: line 3: fastboot: command not found
./flash_all.sh: line 5: fastboot: command not found
./flash_all.sh: line 7: fastboot: command not found
./flash_all.sh: line 9: fastboot: command not found
./flash_all.sh: line 11: fastboot: command not found
./flash_all.sh: line 13: fastboot: command not found
./flash_all.sh: line 15: fastboot: command not found
./flash_all.sh: line 17: fastboot: command not found
./flash_all.sh: line 19: fastboot: command not found
./flash_all.sh: line 21: fastboot: command not found
./flash_all.sh: line 23: fastboot: command not found
./flash_all.sh: line 25: fastboot: command not found
./flash_all.sh: line 27: fastboot: command not found
./flash_all.sh: line 29: fastboot: command not found
./flash_all.sh: line 31: fastboot: command not found
./flash_all.sh: line 33: fastboot: command not found
./flash_all.sh: line 35: fastboot: command not found
./flash_all.sh: line 37: fastboot: command not found
./flash_all.sh: line 39: fastboot: command not found
./flash_all.sh: line 41: fastboot: command not found
./flash_all.sh: line 43: fastboot: command not found
./flash_all.sh: line 45: fastboot: command not found
./flash_all.sh: line 47: fastboot: command not found
./flash_all.sh: line 49: fastboot: command not found
./flash_all.sh: line 51: fastboot: command not found
./flash_all.sh: line 53: fastboot: command not found
./flash_all.sh: line 55: fastboot: command not found
./flash_all.sh: line 57: fastboot: command not found
./flash_all.sh: line 59: fastboot: command not found
./flash_all.sh: line 61: fastboot: command not found
./flash_all.sh: line 63: fastboot: command not found
./flash_all.sh: line 65: fastboot: command not found
./flash_all.sh: line 67: fastboot: command not found
./flash_all.sh: line 69: fastboot: command not found
./flash_all.sh: line 71: fastboot: command not found
./flash_all.sh: line 73: fastboot: command not found
./flash_all.sh: line 75: fastboot: command not found
./flash_all.sh: line 77: fastboot: command not found
./flash_all.sh: line 79: fastboot: command not found
./flash_all.sh: line 81: fastboot: command not found
./flash_all.sh: line 83: fastboot: command not found
./flash_all.sh: line 85: fastboot: command not found
./flash_all.sh: line 87: fastboot: command not found
./flash_all.sh: line 89: fastboot: command not found
./flash_all.sh: line 91: fastboot: command not found
./flash_all.sh: line 93: fastboot: command not found
./flash_all.sh: line 95: fastboot: command not found
./flash_all.sh: line 97: fastboot: command not found
./flash_all.sh: line 99: fastboot: command not found
./flash_all.sh: line 101: fastboot: command not found
./flash_all.sh: line 103: fastboot: command not found
./flash_all.sh: line 105: fastboot: command not found
./flash_all.sh: line 107: fastboot: command not found
./flash_all.sh: line 109: fastboot: command not found
./flash_all.sh: line 111: fastboot: command not found
./flash_all.sh: line 113: fastboot: command not found

any ideas?

What operating system are you using on your PC?

 

[ayaz51]

What operating system are you using on your PC?

osx, now iive tried on PC, cant get fastboot to pick it up. windows recognises it, adb drivers fully working. god Mac is so much easier

 

[awells845]

This thread seems pointless. No one has successfully debranded there Three Razer Phone. All I've seen is people brick there device by trying. The thread needs to be closed.

 

[Robeus_ViP]

I de-branded my Three Razer Phone without any issues, 0 error messages and working OTAs . Maybe that's because I have experience of flashing my previous Xiaomi device like a billion times : )
Windows 10 + proper adb drivers installation = easy de-branding.

 

[awells845]

I wonder if it's more successful without the flash all bat file and just flashing the scripts manually.

 

[Robeus_ViP]

I wonder if it's more successful without the flash all bat file and just flashing the scripts manually.

I just followed this guide and it worked fine. No manual scripting, .bat file does the same thing that you can do manually but prevents possible mistakes/typos. Again, in my experience most of the issues come from incorrect android/fastboot/adb drivers or wrong versions of the android platform tools (adb.exe, fastboot.exe etc.).
Also you can try to put all files on your boot drive root. For example, I placed them at C:\android\platform-tools\adb.exe and C:\android\cheryl-global-851\flash_all.bat.
If nothing helps, try different USB cable and port, I used Anker Powerline+ (A8168HA1) and plugged it directly to the motherboard rear USB 3.0.

 

[awells845]

I just followed this guide and it worked fine. No manual scripting, .bat file does the same thing that you can do manually but prevents possible mistakes/typos. Again, in my experience most of the issues come from incorrect android/fastboot/adb drivers or wrong versions of the android platform tools (adb.exe, fastboot.exe etc.).
Also you can try to put all files on your boot drive root. For example, I placed them at C:\android\platform-tools\adb.exe and C:\android\cheryl-global-851\flash_all.bat.
If nothing helps, try different USB cable and port, I used Anker Powerline+ (A8168HA1) and plugged it directly to the motherboard rear USB 3.0.

I gave it and a try and it worked. I flashed all the scripts manually because when I use to have the OnePlus One back in the day, I used a flash all bat file and it hanged and bricked it. But all good here Glad to see the back of Three bloatware.

---------- Post added at 06:02 PM ---------- Previous post was at 06:00 PM ----------

I just followed this guide and it worked fine. No manual scripting, .bat file does the same thing that you can do manually but prevents possible mistakes/typos. Again, in my experience most of the issues come from incorrect android/fastboot/adb drivers or wrong versions of the android platform tools (adb.exe, fastboot.exe etc.).
Also you can try to put all files on your boot drive root. For example, I placed them at C:\android\platform-tools\adb.exe and C:\android\cheryl-global-851\flash_all.bat.
If nothing helps, try different USB cable and port, I used Anker Powerline+ (A8168HA1) and plugged it directly to the motherboard rear USB 3.0.

It worked, thanks

 

[Robeus_ViP]

Glad to hear! So maybe we should add this to the guide?

 

[awells845]

Glad to hear! So maybe we should add this to the guide?

:good:

 

[lwp2013]

I've skipped all this and just updated with the Oreo DP1. Debranded and running . Was pretty easy, ended up manually flashing though took forever as there were about 20 odd lines to flash

 

[nexy33]

well still no luck fired the laptop back to windows 7 can do and reboot bootloader it'll goto do mode then it rises to install driver force it to take the ADB driver again won't do nothing won't communicate, debugging and item unlock are both on does same on windows 10 on desktop I give up

Sent from my Phone using Tapatalk

 

[v4ndr4k3]

I'm always stuck at waiting for the device when I click the flash_all.bat file
Drivers Installed properly and no yellow warning triangle marks on device manager, also it can read fastboot devices command and shows up the serial number, tried different usb ports and cables still no effect.


C:\Users\Drake\Desktop\cheryl-global-851>set fastboot_cmd=fastboot

C:\Users\Drake\Desktop\cheryl-global-851>fastboot flash partition:0 gpt_both0.bi
n
< waiting for device >

 

[nexy33]

finally had to prefix all commands like so
devices -I 0x1532 for it to work

??? happy dance

Sent from my Phone using Tapatalk
cheers Roxas598

 

[finbaar]

Struggling with this. I can't get my phone to be recognised in either W10 or Linux. In W10 I can reboot into download mode using ADB but then my laptop just sees it as an "Android". Which drivers should it be using at this point? In Linux (Zorin OS) I don't get the option to authorise the RSA fingerprint even though the phone thinks it is in USB debug mode and ADB Devices brings up nothing, not even xxxxxxx unauthorised. Any ideas folks as I have no intention of setting up this device on the Three firmware.
Oh, I have tried 4 USB leads and different ports. It is worth noting that I have a windows laptop and a linux laptop.

 

[Robeus_ViP]

Android 8.1 Oreo OTA update installs without any issues on de-branded phone, confirmed.

 

[driftingpyros]

Anyone have trouble using their hotspot with Three UK on 8.1 after debranding?

Mine turns on, connects up fine, but can't get internet access on the connected device.

I flashed Go unbranded MR3, then upgraded OTA to 8.1.

Locked bootloader, all stock