Database Users

[UPDATED]Recover your dead X8/W8.

Hello there fellow X8/W8 users!
This post is intended to point your attention to the simple fact that there's a hardware imposed danger to hard brick your Xperia X8 and W8, applies to E15i/a and E16i/a, at the attempt to unlock the boot loader!
The phones affected by the problem are units being manufactured at, and after, 11W29!
To check if your device is affected by the problem follow this simple steps:
Turn off the phone and open it up
Take out the battery
Look at the sticker below
If the date code on the sticker reads 11W29, or any later date (11W30, 11W31, 11W32, 11W33, ...), DO NOT attempt to unlock the boot loader.
These phones ship with a revamped chipset configuration having the security hole the boot loader unlock uses effectively closed. This means that upon unlocking the boot loader your phone will end up as a hard brick - and you will have NO means to revive the phone yourselves. You either have to send it off to Sony for repair (recommended solution) or find a phone repair shop being able to resurrect shot devices!
The symptom you will experience when unlocking the boot loader on an affected device is like this:
The boot loader unlock will most likely go through fine
At restart the phone will show NO signs of life anymore.
NO LED, NO LCD output, NO vibration.
This is the point where you can not do anything anymore yourself to resurrect the device.
You have been warned, DO NOT TRY to unlock the boot loader on phones manufactured PAST 11W29!
But it has been seen that there are few devices with manufacturing code above 11W29 have also successfully unlocked their bootloader.
For example me,i have 11W34 and unlocked the bootloader just fine..
But let me remind you again that this was just a matter of luck.
You might not be so lucky...
Also if you have manufacturing code above 11W29 and are desperate to unlock your bootloader then there are paid methods for it as reported by few users who had successfully unlocked their bootloader with manufacturing date above 11W29.
Update (2012/02/23):
To clear up the "no means to resurrect the phone yourself": This is true unless you are a experienced electronics technician. If you own a JTAG box (RIFF Box, Medusa Box) you may attempt to resurrect the device through JTAG. It may also be possible to resurrect the device through UART flash by using a test pin connection. Google is your friend here to dig up the required informations.
As posted by baiclark: There's an option to unlock the boot loader on 11W29+ devices, though this involves some Software (setool2) where you need to buy credits to perform the unlock. This is an untested procedure. If you decide to jump the gun please report your experience.
Update: Home-Brew unbricking with Omnius
Forum member aze2learn posted a guide about how to unbrick your hard bricked W8/X8 by using a modified Nokia CA-42 cable and Omnius. Find his valuable contribution at this post.
/!\ Be warned that this requires basic electronics skills to make it happen. /!\

Unbrick your briked X8/W8 via flashtools
Hi all
I made this thread since some guys were having trouble unbricking their X8/W8 via FLASHTOOLS...
And let me make it clear that the following post wont help you if your phone has bricked in attempt to unlock your bootloader when your phones manufacturing code was above 11W29.
In such a case the only (period) solution is to send it off to SONY to have it repaired.
How to unbrick your Soft Bricked phone..
What do you need?
Flashtools.(thanks to androxyde and bin4ry)
X8 stock firmware.
Or from here.
Or here.
X8 drivers installed.
WinRar
Your X8/W8 phone
A USB cable
A PC
Relaxed mind..
Click to expand...
Click to collapse
Now lets begin.
1.First of all download and install Flashtools from the link provided above.
2.Download SE firmware in *.ftf file format and put it in Flashtool/firmwares folder.
3. Now, run the FlashTool and click the
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Lighting bolt button to start flash.
4.Now click flashmode and choose Xperia X8 (E15i).
4.Now wait for a while till it says you to "remove your phone,press the back button and hold it and install the USB".
Do it and wait for the flashing proceedure to finish...
If everything works fine then CONGRATULATIONS!!!!!! you have successfully unbricked your phone and installed the 2.1.1.A.0.6 version with 015 baseband, fresh and stock!
If your phone doesnt boots up still, then you might have gone wrong somewhere in the flashing process..
So read the steps carefully and do it again..
[OPTIONAL STEP]
Guide for installing the required drivers for flashing, skip this if you have PC Companion installed and connected your phone in flash mode at least once!
If your phone is not recognized by Flashtool that means you don’t have the required drivers installed.
Open folder /Flashtool/drivers and install ggsetup-2.2.0.11
If after the above Flashtool still doesn’t recognize your phone, do the following:
From Flashtool/drivers folder extract the zip file XXX_ADB_driver which corresponds to your phone model
Open “Device manager” on the computer and find the device which is with an exclamation mark on it (do this with connected to the computer phone)
Right click on the device and choose Uptade driver
Choose to find the driver manually and browse to the folder where you’ve extracted the zip file.
That should install the required drivers on your computer.
Click to expand...
Click to collapse
Now as you have successfully unbricked your phone, the first thing you would possibly do is rooting your phone...
So here i show you how to Root your phone with flashtools..
1.Start Flashtool
2.Connect the device to the computer and wait until it's recognized
3.Click the icon with the "Padlock [the second in a row]
4.FT will start pushing files, wait till it finishes. Meanwhile the phone will reboot once.
5.When it's over Flashtool will notify "Root Access Allowed"
6.Open the application list on the phone and look for the app "Superuser".
7.If "Superuser" is there you have Rooted your device successfully.
Congrats!
That's it...........
If you found this thread useful don't forget to click the THANKS button for me...
Thanks to
Bin4ry and androxyde..(for flashtools)
crowds for the original guide..
Leajian for allowing me to use content from his guide.
BlackRabbit1703 for the mirror of firmware.
And all the people who liked my work...
See ya..

um, mine's an 11W29 and it unlocked just fine. it's only the one's AFTER it that have issues.

I have 11W33 and unlocked 2 times now without a problem ! and works fine

Realtbhuion said:
um, mine's an 11W29 and it unlocked just fine. it's only the one's AFTER it that have issues.
Click to expand...
Click to collapse
We also had a few phones in the 11W3x region that unlocked perfectly, but the hard bricks we observed so far all start at 11W29 - and newer.
The source from where we got the information about the hard brick danger is a post of the_laser on setool.net ...
seems most of lately produced msm7227-based phones have chipset with FIXED security hole, which used to altbypass unlock.
(that is not 100% confirmed, we only have few reports, however better be warned)
such phones will DIE after successful unlock procedure.
such dead phones CAN NOT be recovered. ( perhaps, jtag can fix that, perhaps, qualcomm fixed jtag security hole too )
there is NO WAY to determine if phone has fixed chipset or chipset with security hole.
the ONLY safe way is to use unlock by resurrection cables.
if phone can be connected and booted by resurrection cables, phone is safe to unlock.
if phone can not be booted by resurrection cables, phone has fixed chipset and could not be unlocked.
you have been warned.
get and use resurrection cables.
update:
e16 phone with manufacture date 11w38 affected, i think we should care about phones which produced after 11w26
Click to expand...
Click to collapse
As you can see the_laser referenced 11W26 as the "threshold" where our observation is that 11W29 is where the trouble really starts.
EDIT: See this thread for reference - post #62 and #63 where we summed up a few hard bricks. But that's just the tip of the iceberg, there have been way more.
You're of course free to dismiss the warning and do as you please, just don't come ranting about your hard brick - you've been warned.

My phone is 11W30 (I forgot to check this before unlock bootloader) but all works fine for me.

Mine was 11W37, and I said "was" 'cause I just bricked it.
So Im reading this thread too late lol
However, this situation only hurries things because I'm getting Xperia Ray soon. Now I have to get it sooner.
For now, I have a fa(i)lPhone, wich was a present from my dad. So no worries at all. But having my X8 completely bricked will be a good challenge, as I'll try to bring it back to life no matter if you say there is nothing I can do.
Of course, in case I achieve it, I'll share it! If not, then I'll have a nice modern piece of decoration for my living room: a smartphone XD

x8-11w37 new phone HARD BRICK!
I was lucky ennough they replaced my bricked x8. . No unlocked bootloader for me.

El Brillantinas said:
Mine was 11W37, and I said "was" 'cause I just bricked it.
But having my X8 completely bricked will be a good challenge, as I'll try to bring it back to life no matter if you say there is nothing I can do.
Of course, in case I achieve it, I'll share it!
Click to expand...
Click to collapse
To be precise - there is something that can be done, it's just not very easy.
On the one hand you can try to read up over at setool.net. The latest versions of SETool are able to resurrect shot W/X8's. However, you either need to know to which test-pins to you need to connect the cable from your computer or simply try to get one of the Qualcomm resurrection cables fitting the W/X8. Apart from that you need "credits" for SETool to actually perform the operation. This means you have to pry your W/X8 apart to gain access to the PCB - that's not exactly something everyone around here is able to do - and connect to the right pins to flash in UART mode.
On the other hand you can always try to find someone (private person / repair shop) having a RIFF Box to see if the phone can be resurrected by JTAG, though the way it sounds (the post I read on setool.net about UART resurrection) a JTAG restore seems to be impossible - but feel free to try.
If you can work out a working, and relatively simple to follow, solution to restore shot W/X8's be our guest to write up a post.

thks, for the info, My x8 manuf.code is 11W28, is it safe for unlock BL?

Can i unlock my bootloader?
My W8 code is 11W25 can i unlock my bootloader??

B.Jay said:
If the date code on the sticker reads 11W29, or any later date (11W30, 11W31, 11W32, 11W33, ...), DO NOT attempt to unlock the boot loader.
Click to expand...
Click to collapse
NarutoDroid said:
thks, for the info, My x8 manuf.code is 11W28, is it safe for unlock BL?
Click to expand...
Click to collapse
akhi24nick said:
My W8 code is 11W25 can i unlock my bootloader??
Click to expand...
Click to collapse
So ... 11W28 and 11W25 are below 11W29, right?
No guarantee given as there's always the chance that you may mess up, but it should be safe to try and unlock the boot loader.

Mine is 11W21 (uhm semms a old version or something like that...?), soon I'll try unlocking...
But it has a f..... sinaptic touchscreen, damn...

Hmmmm..... I got 11W34 and i can unlock my Droid

11W48
Hi there,
actually I was following guides in the manner google -> blogs -> direct links to oneclickroot/roms -> direct links to bootloader unlocker and...
Well, unfortunately 11W48 (pretty fresh, huh?) got hard bricked xD
I understand it's motherboard failure now and we can do NOTHING more than sending my new paperweight back to SE?
Also I'm looking forward to finding another way to unlock bootloader with new chips in case the one I get back won't be <11W29
Thanks in advance for your reply

Ahh i wish so much i had red this thread and didn't act too much excited about unlocking it.

10W48 ---> unlock with flashtool!

2010matej said:
10W48 ---> unlock with flashtool!
Click to expand...
Click to collapse
Man.... You are exceptional on EARTH.....
You unlocked bootloader with 11w48 making. You have battery backup beyond 6 days.
May be you can overclock your X8 upto 1Ghz and have Multitouch instead of dualtouch even its also possible that SE will make a firmware 4.0 only for you....
Really, you are an amazing guy...

that's very good to warn everyone here before attempting ^^

my is 11w06

SBF/Bootloader Unlocking Blocked on New Atrix

So, I don't mean to start a panic for the remaining Atrix faithful here, but it seems like Motorola has started to block the ability to flash SBF's, including the pudding/IHOP files, on New and replacement Atrix phones. I've been in discussions with at least three recipients of replacement devices over the last three days that all have the same issue.
Anytime any SBF file is flashed to the device it fails with the error SFV:106:1:2 Unable to reenumerate device (or something similar). It does not put you into fastboot or give you the options it used to, you simply have to battery pull and the phone boots normally as if nothing ever happened. Even the current version SBF for AT&T (4.5.141) will not flash to the phone; it ends in the same error.
Without being able to flash ANY SBFs, that means the bootloader on these new phones remains locked down for the moment. I know we have lost many of our original developers that worked to try to unlock the bootloader the first time, but I also know we have many talented devs currently with us.
Is there anyone able to provide insight as to what might have been changed by Motorola and how we might be able to overcome it?
Here are links to my discussions with them, as well as another post I just found that is similar from a Bell user:
http://www.atrixforums.com/forum/showthread.php?p=107507
http://forum.xda-developers.com/showthread.php?p=25167191 (not sure if same situation, sounds possibly similar)
Sent from my MB860 using Tapatalk 2

Can anyone confirm this has happened to them? Motorola will lose alot of loyal customers, myself included, if they pull this bull.

yes it is true. i got my atrix today, i sent it in and i tried to unlock it right away but that proved to be impossible. if you follow those links, i have the exact same symptoms.

If anyone who is experiencing this can run some tests for samcripp, it looks like he's willing to help where he can. See this post here: http://www.atrixforums.com/forum/motorola-atrix-hacks/3331-tut-unlocking-bootloader-installing-custom-roms-63.html#post108017
Thanks!

That is so lame! This was my first Motorola smartphone and I have a feeling it will be my last.
Sent from my MB860 using xda premium

Just use the automated boot loader unlock it worked for my friend
Sent from my MB860 using XDA

kufusoto said:
Just use the automated boot loader unlock it worked for my friend
Sent from my MB860 using XDA
Click to expand...
Click to collapse
So far, that has failed with the same result for the two users that have tried it under these conditions.

i replied on the other forum

kufusoto said:
Just use the automated boot loader unlock it worked for my friend
Sent from my MB860 using XDA
Click to expand...
Click to collapse
did he ever send it into moto for any repairs?

Unable to unlock BL
I have had my Atrix 4G for almost 1 year. It was purchased as a refurb directly from AT&T. It came with Froyo on it & I patiently waited for and applied the OTA to 2.3.4 and 2.3.6. I was able to successfully root it but it will not give me the Unique ID when I run "fastboot oem unlock". It says:
C:\fastboot>fastboot oem unlock
...
(bootloader) OEM unlock is not implemented
OKAY [ 0.001s]
finished. total time: 0.001s
I will get the FUSE and edit this post.
ReservedOdm: 10000000000030001000300000000

BKrenning said:
I have had my Atrix 4G for almost 1 year. It was purchased as a refurb directly from AT&T. It came with Froyo on it & I patiently waited for and applied the OTA to 2.3.4 and 2.3.6. I was able to successfully root it but it will not give me the Unique ID when I run "fastboot oem unlock". It says:
C:\fastboot>fastboot oem unlock
...
(bootloader) OEM unlock is not implemented
OKAY [ 0.001s]
finished. total time: 0.001s
I will get the FUSE and edit this post.
Click to expand...
Click to collapse
You need to flash the "pudding" SBF unlocker file before using the fastboot commands. See the Unlock/IHOP sticky post at the top of the Development section.
Sent from my MB860 using Tapatalk 2

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
this is what i get after trying the automatic unlock tool.
it says unlocked but its not. its not rooted either. what did you use to root? like ^^^ it never showed my unique ID and just hung there.

thegogetter- said:
this is what i get after trying the automatic unlock tool.
it says unlocked but its not. its not rooted either. what did you use to root? like ^^^ it never showed my unique ID and just hung there.
Click to expand...
Click to collapse
how is it not unlocked, if it says unlocked and starts fastboot? just fastboot flash romracers recovery onto it and thats it, than you can flash custom roms.

das8nt said:
So, I don't mean to start a panic for the remaining Atrix faithful here, but it seems like Motorola has started to block the ability to flash SBF's, including the pudding/IHOP files, on New and replacement Atrix phones. I've been in discussions with at least three recipients of replacement devices over the last three days that all have the same issue.
Anytime any SBF file is flashed to the device it fails with the error SFV:106:1:2 Unable to reenumerate device (or something similar). It does not put you into fastboot or give you the options it used to, you simply have to battery pull and the phone boots normally as if nothing ever happened. Even the current version SBF for AT&T (4.5.141) will not flash to the phone; it ends in the same error.
Without being able to flash ANY SBFs, that means the bootloader on these new phones remains locked down for the moment. I know we have lost many of our original developers that worked to try to unlock the bootloader the first time, but I also know we have many talented devs currently with us.
Is there anyone able to provide insight as to what might have been changed by Motorola and how we might be able to overcome it?
Here are links to my discussions with them, as well as another post I just found that is similar from a Bell user:
http://www.atrixforums.com/forum/showthread.php?p=107507
http://forum.xda-developers.com/showthread.php?p=25167191 (not sure if same situation, sounds possibly similar)
Sent from my MB860 using Tapatalk 2
Click to expand...
Click to collapse
I get that error when
1. I try to flash a SBF file not meant for my phone. (Yeah... Stupid move)
2. There is a hardware problem with my phone.
---------- Post added at 05:22 PM ---------- Previous post was at 05:19 PM ----------
thegogetter- said:
this is what i get after trying the automatic unlock tool.
it says unlocked but its not. its not rooted either. what did you use to root? like ^^^ it never showed my unique ID and just hung there.
Click to expand...
Click to collapse
If it never showed your unique ID, your phone has been unlocked before.
crnkoj said:
how is it not unlocked, if it says unlocked and starts fastboot? just fastboot flash romracers recovery onto it and thats it, than you can flash custom roms.
Click to expand...
Click to collapse
It did not start at fastboot automatically, he made it start at fastboot. =D Funny what some people do...

When I try to flash a recovery it hangs on waiting on device and doesn't do anything. I tried that already. I don't have root either

das8nt said:
You need to flash the "pudding" SBF unlocker file before using the fastboot commands. See the Unlock/IHOP sticky post at the top of the Development section.
Sent from my MB860 using Tapatalk 2
Click to expand...
Click to collapse
That's what I figured. I was hoping someone had come up with an easier route by now or at least figured out what was in the OTA that is blocking the phone from giving out it's unique id.
There is a Samsung Note on CL calling my name. Maybe I'll answer it--LOL.
Thank you for your help!

thegogetter- said:
When I try to flash a recovery it hangs on waiting on device and doesn't do anything. I tried that already. I don't have root either
Click to expand...
Click to collapse
Have you installed the drivers for your phone? If you're trying to flash a recovery, you should be unlocked and to unlock your phone, you would need the drivers.

Off the top of my head, the error from rsd seems like one you get when you try to use a ramloader from ATT with a Bell phone. That is why there were radio sbfs for Bell and for ATT separately.
You have to realise that the sbf files with the unlockable bootloaders are mods of existing sbf files and may simply be out of date with regard to the new phones. You would need a new sbf file to hack in the replacement bootloader. So what you are really looking for is another unlockable bootloader in the wild as part of a sbf that can be stripped down to just the bootloader part.
Or Motorola could just take it's **** out of it's ***.
Cheers!

i sent my atrix to get fixed in the last 3 weeks and i got it back, the bootloader was still unlocked but it needed to be "reminded" of it if you will. it had stock 4.5.151 on it and when it booted up there was no "unlocked" text and i couldn't flash a recovery, so i all i had to do was SBF to 2.3.4 and flash the trololol.sbf and it "reminded" my phone that it was unlocked. during the flashing process it rebooted and showed up as "unlocked" in the corner without having to re "fastboot oem unlock" it and i could flash a recover from there. using the latest RSDLite and Windows XP via Bootcamp with an AT&T Atrix and all AT&T files.

i got it to work after using a different computer and loading fresh drivers. thanks guys.

[TUTORIAL] How to Flash Stock Motorola Fastboot files

Welcome to my first tutorial! Please make suggestions in this thread on how to improve it. I will try to be a comprehensive as possible but also as general as possible since flashing firmware to Motorola phones is a pretty consistent process.
Disclaimer:
Please note, like almost everything else on XDA-Developers.com doing this process without fully understanding it can possibly brick the phone (although if it probably already is) thus, I cannot be held liable for any damages caused by following this process.
In other words, the person performing the work performed in this post is fully responsible for their actions on this phone.
/Disclaimer
Before starting with the flashing a Motorola phone, please review the following information:
In most cases firmware versions CANNOT be downgraded
Firmware from other regions can sometimes be flashed, but not always, this is why it is always recommended to stick with the same firmware branch that is already on the phone
The phone that will be flashed should be fully charged, the fastboot flashing process only allows for phones that are over 50 or 60% to be flashed.
If the phone that is trying to be flashed is under 50 or 60%, purchase a "factory adapter" - http://shop.teamblackhat.info/Factory-Adapters-motadapt.htm or make one - http://forum.xda-developers.com/showthread.php?t=1077414
Use a USB 2.0 port that is directly connected to the motherboard of the computer (preferably on the back of a desktop, or internal ports on a laptop)
Now, prepare the computer for the flashing process
Download the latest Motorola USB & Charging Drivers from http://www.motorola.com/Support/CA-EN/Support-Home/USB-Drivers-and-PC-Charging-Drivers
Download the latest available RSD Lite software (~6mb) - As of March 4th 2013, it is 6.1.4 and can be downloaded from here : http://d-h.st/KNN
Ensure the computer can detect the phone in fastboot mode (I have seen a number of problems with different versions of Windows, if it doesn't work on one PC, try a different one). To perform the test, power off the phone completely and boot it into fastboot mode. Unfortunately since Motorola phones are all built uniquley, this tutorial cannot cover all of the different methods to boot a phone in fastboot, but the most common method is to hold the VOLUME UP button and VOLUME DOWN button while pressing POWER. A menu will most likely appear, use the VOLUME DOWN button and navigate to "AP Fastboot", now press the VOLUME UP button. The phone should say it is OK to Program like in the following screen
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Next, connect the USB cable to the computer, it should detect and install a driver. Check in device manager for a "Mot Single ADB Interface" under ADB Interface. If it is not listed, try to force the drivers to look in the "C:\Program Files\Common Files\Motorola Shared\Mobile Drivers\Drivers" folder.
Once the driver is loaded, open up RSD Lite and the internal codename should be listed under one of the ports. In RAZR HD (GSM) it says Fastboot VANQUISH_U S.
At this point, I would recommend to download the firmware to the computer that will be used for the flashing (once the phone is detectable in RSD Lite, that is a good indication the computer can detect the phone, navigate to http://motofirmware.center and locate the correct firmware and version that should be loaded on the phone. If the firmware is not listed there, please put a request into the firmware team (supply the default.prop and build.prop files). They are pretty good with locating firmware! The firmware files are generally large (ranging anywhere between 200mb and 1500mb) so now would be a good time to top-up that phone charge (if possible). If it isn't possible to charge the phone, don't worry, the phone will automatically turn off if it doesn't detect a flashing process after a few minutes.
Flashing Time!
Once the preparation has completed, flashing is very straightforward. Extract the downloaded firmware files to a folder on your hard disk, then use RSD Lite to load the XML file up. Power on the phone into fastboot mode again, and plug in the phone into an internal USB port on the computer, then press the start button. If everything is successful the phone should begin booting into the stock system. The flashing process usually takes 10-20 minutes depending on the size of the files and the power of the phone. If there are any failures, be sure to read the "Before getting started" section again, and hopefully someone on the forum can help recover the phone with you!

Re: [TUTORIAL] How to Flash Stock Motorola Fastboot & SBF files
danifunker said:
Welcome to my first tutorial! Please make suggestions in this thread on how to improve it. I will try to be a comprehensive as possible but also as general as possible since flashing firmware to Motorola phones is a pretty consistent process.
Disclaimer:
Please note, like almost everything else on XDA-Developers.com doing this process without fully understanding it can possibly brick the phone (although if it probably already is) thus, I cannot be held liable for any damages caused by following this process.
In other words, the person performing the work performed in this post is fully responsible for their actions on this phone.
/Disclaimer
Before starting with the flashing a Motorola phone, please review the following information:
In most cases firmware versions CANNOT be downgraded
Firmware from other regions can sometimes be flashed, but not always, this is why it is always recommended to stick with the same firmware branch that is already on the phone
The phone that will be flashed should be fully charged, the fastboot flashing process only allows for phones that are over 50 or 60% to be flashed.
If the phone that is trying to be flashed is under 50 or 60%, purchase a "factory adapter" - http://shop.teamblackhat.info/Factory-Adapters-motadapt.htm or make one - http://forum.xda-developers.com/showthread.php?t=1077414
Use a USB 2.0 port that is directly connected to the motherboard of the computer (preferably on the back of a desktop, or internal ports on a laptop)
Now, prepare the computer for the flashing process
Download the latest Motorola USB & Charging Drivers from http://www.motorola.com/Support/CA-EN/Support-Home/USB-Drivers-and-PC-Charging-Drivers
Download the latest available RSD Lite software (~6mb) - As of March 4th 2013, it is 6.1.4 and can be downloaded from here : http://d-h.st/KNN
Ensure the computer can detect the phone in fastboot mode (I have seen a number of problems with different versions of Windows, if it doesn't work on one PC, try a different one). To perform the test, power off the phone completley and boot it into fastboot mode. Unfortunatley since Motorola phones are all built uniquley, this tutorial cannot cover all of the different methods to boot a phone in fastboot, but the most common method is to hold the VOLUME UP button and VOLUME DOWN button while pressing POWER. A menu will most likley appear, use the VOLUME DOWN button and navigate to "AP Fastboot", now press the VOLUME UP button. The phone should say it is OK to Program like in the following screen
Next, connect the USB cable to the computer, it should detect and install a driver. Check in device manager for a "Mot Single ADB Interface" under ADB Interface. If it is not listed, try to force the drivers to look in the "C:\Program Files\Common Files\Motorola Shared\Mobile Drivers\Drivers" folder.
Once the driver is loaded, open up RSD Lite and the internal codename should be listed under one of the ports. In RAZR HD (GSM) it says Fastboot VANQUISH_U S.
At this point, I would recommend to download the firmware to the computer that will be used for the flashing (once the phone is detectable in RSD Lite, that is a good indication the computer can detect the phone, navigate to http://sbf.droidevelopers.org and locate the correct firmware and version that should be loaded on the phone. If the firmware is not listed there, please put a request into the firmware team (supply the default.prop and build.prop files). They are pretty good with locating firmware! The firmware files are generally large (ranging anywhere between 200mb and 1500mb) so now would be a good time to top-up that phone charge (if possible). If it isn't possible to charge the phone, don't worry, the phone will automatically turn off if it doesn't detect a flashing process after a few minutes.
Flashing Time!
Once the preperation has completed, flashing is very straightforward. Extract the downloaded firmware files to a folder on your hard disk, then use RSD Lite to load the XML or SBF file up. Power on the phone into fastboot mode again, and plug in the phone into an internal USB port on the computer, then press the start button. If everything is sucessful the phone should begin booting into the stock system. The flashing process usually takes 10-20 minutes depending on the size of the files and the power of the phone. If there are any failures, be sure to read the "Before getting started" section again, and hopefully someone on XDA can help recover the phone with you!
Click to expand...
Click to collapse
Would be best to download the files before entering the bootloader... I heard some nasty stories bout battery emptying out in BL/recovery and it messed up while flashing.
Charge up the phone before flashing and have the files ready prior to flashing.
Sent from my XT925 using xda app-developers app

saloums7 said:
Would be best to download the files before entering the bootloader... I heard some nasty stories bout battery emptying out in BL/recovery and it messed up while flashing.
Charge up the phone before flashing and have the files ready prior to flashing.
Sent from my XT925 using xda app-developers app
Click to expand...
Click to collapse
Yes, I understand what you're saying, but I've seen a lot of nightmare PCs out there recently, so I want to do a compatibility check before you end up downloading a large file and not being able to use it.

danifunker said:
Yes, I understand what you're saying, but I've seen a lot of nightmare PCs out there recently, so I want to do a compatibility check before you end up downloading a large file and not being able to use it.
Click to expand...
Click to collapse
Works like a charm. Thank you.

danifunker said:
Yes, I understand what you're saying, but I've seen a lot of nightmare PCs out there recently, so I want to do a compatibility check before you end up downloading a large file and not being able to use it.
Click to expand...
Click to collapse
Good point good thing I have unlimited bandwidth so that doesn't affect me too much
Sent from my XT925 using xda app-developers app

If you have "battery low" during flashing, and you can't make the phone boot, just discharge it completely and then plug the phone into charger (it will charge in "emergency mode" without booting).

Thanks for this post....after issues with CM 10 and no GPS....I flashed back to Rogers/Fido 4.1.2. very happy....here is hoping if there are any future updates this ROM will auto update. Or I can wish for a working CM 10.1 some day
Sent from my XT925 using xda app-developers app

shredrex said:
Thanks for this post....after issues with CM 10 and no GPS....I flashed back to Rogers/Fido 4.1.2. very happy....here is hoping if there are any future updates this ROM will auto update. Or I can wish for a working CM 10.1 some day
Sent from my XT925 using xda app-developers app
Click to expand...
Click to collapse
Hi shredrex, I am also having the same problems and I want to flash back to rogers/fido 4.1.2. May I know where you got your files from? I would really appreciate it!!

taeotut said:
Hi shredrex, I am also having the same problems and I want to flash back to rogers/fido 4.1.2. May I know where you got your files from? I would really appreciate it!!
Click to expand...
Click to collapse
I posted the wrong link in the original tutorial, thanks for flagging it.
Check this site : http://sbf.droid-developers.org/
Good luck!

i´m trying to install the telcel firmware and also used 2 different computers with the lastest drivers and rds lite 6.1.4
I followed all the steps and doesn´t work for me I´ve got the next error
failed flashing process. unknown fastboot command getvar
Help me please

Hi danifunker, I am new to Motorola and I have the RAZR i (XT890). I'm making two guides related to helping new people to Motorola phones here . May I link your guide here, of course giving full credit? I basically would like to recommend new users to the RAZR i to read good guides like this before they brick their phone. We get about 5 bricks a day over there!

gorefrausto said:
i´m trying to install the telcel firmware and also used 2 different computers with the lastest drivers and rds lite 6.1.4
I followed all the steps and doesn´t work for me I´ve got the next error
failed flashing process. unknown fastboot command getvar
Help me please
Click to expand...
Click to collapse
The firmware you downloaded has a .xml file in it. Remove the line with Getvar in it, and try to flash again.

elcacho said:
The firmware you downloaded has a .xml file in it. Remove the line with Getvar in it, and try to flash again.
Click to expand...
Click to collapse
Thanks, now I´m installing the firmware

elcacho said:
The firmware you downloaded has a .xml file in it. Remove the line with Getvar in it, and try to flash again.
Click to expand...
Click to collapse
Can we have this put into the tutorial please.
Also, as for the OP in general, thanks for putting this here; its not so clear elsewhere on this section of the forum and everything that is useful to a Motorola noob is specifically for the XT926... even the blog posts linked to. I had a lot of anxiety over trying this in the past because things as fundamental as this, concerning Motorola and these phones in particular as well, are scattered and disorganised in various places on the internet. Its frustrating and makes one want to shy away from trying things out for fear of not being able to return to stock or bricking their device. I come from an SGS2 which had no fastboot to worry about, for example, and even though the RAZR HD forum had few participants when I first got mine, there was still a lot to be confused about and to shy away from.

Im trying to flash the filmware to my phone cause my camera stopped working shortly after i updated my droid razr to 4.1.2, and when i did the ap fastboot filmware update, everything comes back like it already was should i remove everything from my phone and try again?
Edit: My Safestrap is gone, and now i have no service..
Edit Again: Service restored after i removed everything, another problem tho. Camera still wont initialize now

Firmware Motorola V9 bootloader 04.C1
Dear XDA members, need firmware in Portuguese with the Motorola V9 bootloader 04.C1. I thank you.

Thanks for detailed instuctions! Worked perfectly for Motorola XT862.

Ok to program option
I have been running 4.2.2 aokp unofficial, and its been awesome.. i need to flash back to stock because im going to be selling my phone soon, when i try to use mattlgraf's utility i always get the unable to mount error message.. im going to be trying this option aswell, but I have a feeling it wont work because i dont get the "OK to program" in AP Fastboot, if you have any idea why this is happening just reply to this post, thanks for all the material guys.
---------- Post added at 11:05 AM ---------- Previous post was at 10:58 AM ----------
thetigerag said:
I have been running 4.2.2 aokp unofficial, and its been awesome.. i need to flash back to stock because im going to be selling my phone soon, when i try to use mattlgraf's utility i always get the unable to mount error message.. im going to be trying this option aswell, but I have a feeling it wont work because i dont get the "OK to program" in AP Fastboot, if you have any idea why this is happening just reply to this post, thanks for all the material guys.
Click to expand...
Click to collapse
I got an error message that said "Failed flashing process. Unknown fastboot command" im not sure if this is due to the new firmware because of running 4.2.2 or what.. any information would be appreciated - Thanks.

Use MATT's utility v1.2
Look for the v 1.2 and give it a try.
I was able to go back to stock ICS on the xt925 (Rogers)

itzik_man said:
Look for the v 1.2 and give it a try.
I was able to go back to stock ICS on the xt925 (Rogers)
Click to expand...
Click to collapse
Yes, 1.20 was the utility i originally used.
I get the error message 'fastboot' is not recognized as an internal or external command, operable program or batch file. multiple times, then it takes me back to the main screen.
---------- Post added at 10:45 PM ---------- Previous post was at 10:04 PM ----------
Got it all worked out, thanks guys.

[Flashtool] How to flash the Sony Xperia Z5 Compact with stock ROM [Flashtool]

Over the past couple of days, I have been experiencing various issues with flashtool. Using the internets help and many hours of my time I managed to fix most of these problems that occurred for me. Although there are hundreds of Flashtool step by step instructions, I thought it would be best for an updated and more in depth on what you should be aware of first before clicking "Flash".
Firstly, I do not take responsibility for any device broken or damaged since there is ALWAYS a minute chance of your device bricking.
Lets start, shall we?
Things Needed
Z5 Compact
Original Cable (or any cable actually that is working and can transfer files)
Flashtool 0.9.22.3
Sony Xperia Z5 Compact Stock Rom
Okay to start off.. Yes, this should work with other phones however I am not providing the stock roms for those, it takes a simple google search to find them ie. "Sony Xperia Z5 Stock Rom ftf"
You don't need the latest stock rom either since you can update once the phone is setup depending on if you have access to OTA updates (Over the Air).
Step 1.
Download flashtool if you haven't already. If you have an older version of flashtool, uninstall it and make sure all old files are gone for good and also be sure the new one is fully installed. I prefer to use the magnet link on the website (for torrents) since using uploaded.net takes forever.
Step 2a.
If you're on Windows 8/8.1/10 then please take note to this specific paragraph, any other OS skip to 2b Windows 8/8.1 like to have its security tight, so they block you from installing drivers with unsigned certificates to "keep your computer from harm" but just go ahead and follow the instructions to allow your computer install these drivers. If the drivers aren't installed correctly, then you won't be flashing anything today Okay, go to Settings>General and then click on 'Restart Now' under 'Advanced Startup'.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
This will restart your PC. It will then take you to a screen that gives you various options. On Windows 8 you will see 'Troubleshoot' and on Windows 8.1 you will see 'Start-up Settings'. Select either that appears. This will take you to another page that will ask to restart windows in order to use some advanced startup features, just click 'Restart'. If it already takes you to the page without restart, or if your computer just restarted and you're getting the options of what to select, make sure you select 'Disable driver signature enforcement'.
Your computer should now restart with driver signature enforcement disabled. Now, go ahead and carry on with the instructions in 2b!
Step 2b.
Navigate to the 'drivers' folder where you installed Flashtool. If you cant remember where you installed it, the default directory should be in "C:\Flashtool". Open 'Flashtool-drivers.exe' and install:
Flashmode Drivers
Fastboot Drivers
Z5 Compact Device Driver (Or whatever your device is)
Now we have successfully installed the drivers for flashtool and our device!
Step 3.
Find the stock rom you downloaded, copy and paste it into your firmwares folder in flashtool. For me, this is in "C:\Users\Matty\.flashTool\firmwares". People have been saying to delete the folders inside the firmwares folder, do not do this as the flash might not work.
Step 4.
Note
If you're running 64bit, I recommend you to not use Flashtool64.exe at first, just use the standard 'Flashtool.exe'. If you dont get an icon on your desktop from the setup, just navigate to the folder in the directory you installed it in, then right click and click send to desktop so you can access it easy
Step 5.
Open Flashtool from your newly created shortcut on your desktop. Click the Flash icon, then click Flashmode, then hit Ok. Click your Firmware on the left to start off with. You might have to hit the firmware dropdown until it gets to the actual firmware like so:
If you want to remove all your data, where it says Wipe, hit all the boxes. (APPS_LOG, DIAG, SSD, USERDATA). Then click Flash. You will now see "Preparing files for flashing" on your screen. Be very patient, and in the meantime, turn your phone off ready to enter Flashmode. Make sure your phone is switched off and NOT plugged.
When you see this box come up on your computer, It's probably time to connect the USB to your computer, and enter flashmode on your phone.
Plug the USB into your computer
(TRY USB 2.0 FIRST, SOME REASON NO USB 3.0 PORT WORKED FOR ME+MANY OTHER PEOPLE HAD PROBLEMS WITH USB 3.0 I.E loader.sin errors)
Entering Flash Mode
Hold the Volume Down button and plug the USB cable from your computer into your phone. You should hear the Windows noise it makes to say the device is connected to the PC. If any extra drivers are needed to complete the flash it could take longer for the flash to start. You should then see a constant green light in the top right of your device, gently put it somewhere without unplugging the charger and let Flashtool do the hard work
Step 6.
Leave the device for no longer than 30 minutes. However, if you're unsure be safe and leave it for a full hour, go out have a nice brew, do a tap and dance and come back and it should be done. The only reason it would get stuck is because you unplugged the phone during the Flash, or if the cable somewhat died throughout the operation. If so, repeat the instructions in hope your device will be as good as new
Flashtool will now let you know when it is done. It will say "Flashing finished, please uplug and start your phone."
If it says that, hooray! You have successfully flashed your phone with stock rom!
If not and you get an error before it even wants to flash, or throughout the process you get an error, post it below and I'll take a look. I'm not very good but I know quite a few errors.
END OF TUTORIAL
I just thought I'd help the community out in a way that I can, since I'm bad at like everything else lol.
Peace folks :highfive: :cyclops:

Great write-up! I know it probably would have helped me months ago for something like this to exist. For anyone coming here for info, it also took me three PC's before I found one that played well with flash tool. Also if you ever get a failure, reboot PC, phone, and try again. Persistence pays off.

civicsr2cool said:
Great write-up! I know it probably would have helped me months ago for something like this to exist. For anyone coming here for info, it also took me three PC's before I found one that played well with flash tool. Also if you ever get a failure, reboot PC, phone, and try again. Persistence pays off.
Click to expand...
Click to collapse
Thanks buddy! I suppose the old saying does work.
"Have you tried turning it off and on again?" Works mostly for me lol

If you're on Windows 8/8.1
Click to expand...
Click to collapse
on Windows 10 to
Good work

ciopik said:
on Windows 10 to
Good work
Click to expand...
Click to collapse
I'll add that now, thanks man

The firmware folder is not detected by Flashtool although I have put it in the correct folder...
I have tried hundred of times, i just dont understand

you dont need unlock bootloader for stock kernel\rom right?

If you want to upgrade you better use Xperia companion.
If you want to downgrade and use FlashTool and if you have a problem you better have unlocked bootloader.

Guys,
This is a good tutorial. but I met a dead end, i got " processing partition.sin finished with errors" message, any suggestion?
Thanks for the help, this is my first time flashing
Regards

I am facing same issue i have xperia z5 dual unlocked bootloader i have installed flashtool and drivers correctly and i have placed the ftf firmware in given directory also but flashtool not showing any thing but for m4 aqua i am able to see the ftf firmware please help me
---------- Post added at 09:36 AM ---------- Previous post was at 09:32 AM ----------
EMJI79 said:
The firmware folder is not detected by Flashtool although I have put it in the correct folder...
I have tried hundred of times, i just dont understand
Click to expand...
Click to collapse
Same problem here:crying:

when i get to step 6 it starts flashing but then my phone just switch on on itself and the process stop

my IMEI become unknown,
please help

hi, can i do this on Z5C Docomo (SO-02H)?
also can i flash global rom on that...?

Hey guys.
I have a Z5 Compact (E5823) that's stuck on android version 5.1.1. It never shows any available updates in the Software Update screen. I'd like to get it on 6.0 in the least just for the better permissions system it contains.
In searching for a way to update it, naturally I found this page and all the helpful info it contains. I've never been steered wrong by XDA in the past. I've always found information on this site helpful, and it works.
I've downloaded Flashtool.
I've followed all of the instruction for installation, including the annoying driver installation process for Windows 8.1.
I've downloaded multiple firmwares from Xperifirm.
I can get everything happening, and it looks to work when looking at the Flashtool screen. It says it's complete (just like the little image at the bottom of the initial post).
Nothing seems to have happened to the phone. I boot it back up and it's still running the same old 5.1.1. Flashtool runs through it's process very fast, as in a few seconds, not the half an hour suggested.
The phone came from Hong Kong as far as I can tell. It may have been a refubished phone, I can't be sure. I'm trying to get the Customised AU version 6.0 software on it.
What am I doing wrong? I don't know what else to try, and it's annoying me. PLEASE HELP.
Thanks. Paul.

plazmafire said:
Hey guys.
I have a Z5 Compact (E5823) that's stuck on android version 5.1.1. It never shows any available updates in the Software Update screen. I'd like to get it on 6.0 in the least just for the better permissions system it contains.
In searching for a way to update it, naturally I found this page and all the helpful info it contains. I've never been steered wrong by XDA in the past. I've always found information on this site helpful, and it works.
I've downloaded Flashtool.
I've followed all of the instruction for installation, including the annoying driver installation process for Windows 8.1.
I've downloaded multiple firmwares from Xperifirm.
I can get everything happening, and it looks to work when looking at the Flashtool screen. It says it's complete (just like the little image at the bottom of the initial post).
Nothing seems to have happened to the phone. I boot it back up and it's still running the same old 5.1.1. Flashtool runs through it's process very fast, as in a few seconds, not the half an hour suggested.
The phone came from Hong Kong as far as I can tell. It may have been a refubished phone, I can't be sure. I'm trying to get the Customised AU version 6.0 software on it.
What am I doing wrong? I don't know what else to try, and it's annoying me. PLEASE HELP.
Thanks. Paul.
Click to expand...
Click to collapse
You better ask your question in the Z5 section, you're more likely to have answers and it's the same process (sorry I don't remember guq I did at the time I had the phone).
Sent from my HTC U12+ using XDA Labs

EMJI79 said:
You better ask your question in the Z5 section, you're more likely to have answers and it's the same process (sorry I don't remember guq I did at the time I had the phone).
Sent from my HTC U12+ using XDA Labs
Click to expand...
Click to collapse
Will do.
Thanks.

Hey, man, I used 9.18.5 and it worked

Mamada. said:
Hey, man, I used 9.18.5 and it worked
Click to expand...
Click to collapse
Any idea where I can find a good copy of version 9.18.5?

Hey,
I'm experiencing an issue with Flashtool.
Last weekend I successfully rooted my Z5C with the "How to root Z5C - the new, less painful way"-guide.
Finally the Z5C was flashed with Nougat (Customized DE) and rooted with Magisk (rooted with SuperSU first, but then switched to Magisk), even with working TA partition.
After reading that the Australian Stock ROM doesn't have battery drain issues, I tried flashing that one. Unluckily I'm always getting the following error:
17/059/2019 18:59:25 - ERROR - Processing of system.sin finished with errors.
17/059/2019 18:59:25 - INFO - Ending flash session
17/059/2019 18:59:25 - ERROR - ERR_SEVERITY="MINOR";ERR_CODE="0017";ERR_DYNAMIC="80090012";
Now I can't boot my phone and TWRP seems to be gone too, so I can't restore the backup I did beforehand.
Any idea how to fix this error?
EDIT:
If anyone wonders: I managed to make it work by downloading the firmware again and using a different USB-cable on a different USB-port. Can't say which of those things exactly helped.

T-Mobile get Unlock Code to Submit to OnePlus for unlock token

This took me way too long to figure out so Hopefully this will make it quicker for someone:
OnePlus Help Page
Dr. Mario said:
fastboot oem get_unlock_code
Click to expand...
Click to collapse
(Found ten pages in at https://forum.xda-developers.com/t/t-mobile-bootloader-unlock.4181339/page-10#post-83922873)
Once you have the unlock code go to: One Plus Unlock Token Page
If your phone does not show up in fastboot and you are on windows 10: https://forum.xda-developers.com/t/guide-fix-device-not-showing-up-in-fastboot-mode-windows-10.4194491/
The drivers will not install in windows 10 unless you Disable driver signing enforcement first.
In case you did not know, your phone comes with driver installation software that will show up when you plug your phone into your computer. However, if you have USB debugging turned on first, they will not pop up.
This is all basic stuff, but some times people need help with the basics!
(edited for clarity)
-----------------------------------------------------------------------------------------------------------
Edited to add the following next step
One week later (pretty much to the second) go back to: One Plus Unlock Token Page (you should also get an e-mail with a link. Download the file unlock_code.bin and place it in the same directory you will be running fastboot from.
Don't forget that if you continue past this point you will wipe your phone and have to go through the setup process again. Your phone will also ask for confirmation of this.
Also, as of 11.0.4.6.KB09CB continuing will change your widevine to L3.
Open a command prompt or terminal window and run the following:
adb reboot bootloader
fastboot flash cust-unlock unlock_code.bin
fastboot flashing unlock
------------------------------------------------------------
To Root:
Rooting instructions

However, if you have USB debugging turned on first, they will not pop up.
Click to expand...
Click to collapse
Thats good tip! I never have USB debugging turned off before 1st connection...
ALSO,
There are differences between
FASTBOOTD
AND
FASTBOOT

How long do they send the token

Can this be done with a temporary sim unlock?

jefffeely said:
This took me way too long to figure out so Hopefully this will make it quicker for someone:
OnePlus Help Page
(Found ten pages in at https://forum.xda-developers.com/t/t-mobile-bootloader-unlock.4181339/page-10#post-83922873)
Once you have the unlock code go to: One Plus Unlock Token Page
If your phone does not show up in fastboot and you are on windows 10: https://forum.xda-developers.com/t/guide-fix-device-not-showing-up-in-fastboot-mode-windows-10.4194491/
The drivers will not install in windows 10 unless you Disable driver signing enforcement first.
In case you did not know, your phone comes with driver installation software that will show up when you plug your phone into your computer. However, if you have USB debugging turned on first, they will not pop up.
This is all basic stuff, but some times people need help with the basics!
(edited for clarity)
-----------------------------------------------------------------------------------------------------------
Edited to add the following next step
One week later (pretty much to the second) go back to: One Plus Unlock Token Page (you should also get an e-mail with a link. Download the file unlock_code.bin and place it in the same directory you will be running fastboot from.
Don't forget that if you continue past this point you will wipe your phone and have to go through the setup process again. Your phone will also ask for confirmation of this.
Also, as of 11.0.4.6.KB09CB continuing will change your widevine to L3.
Open a command prompt or terminal window and run the following:
adb reboot bootloader
fastboot flash cust-unlock unlock_code.bin
fastboot flashing unlock
------------------------------------------------------------
To Root:
Rooting instructions
Click to expand...
Click to collapse
This is horrible T-Mobile Tech had no idea what 64 digit code i needed to unlock bootloader told me to contact one plus they told me to contact T-Mobile Technician so the rep put me in touch with a tech from Metro Pcs who said my imei is T-Mobile not Metro and hung up on me Its a never ending battle i need to find a Factory Unlocked Nord 10 5g if i want to root i do like the the stock rom Oxygen but i never owned a phone before that wasn't rooted I have now 4 of these Phones if anyone has a factory unlocked nord 10 5g willing to sell or barter with me as i have a bunch of cellphones please contact me or if you work for T-mobile and can get me this code i need for the token please contact me Thanks

superbart007 said:
Can this be done with a temporary sim unlock?
Click to expand...
Click to collapse
No, requires permanent. Talk to TMobile support on Twitter and tell them you use your phone for development purposes.

Okay I know this is stupid, but since it takes a freaking week (I thought I'd sit down and flash Lineage "real quick"...joke's on me), does the OnePlus site want everything on BOTH lines of that unlock code section, appended together as one long string? Or is that two separate codes?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

matt314159 said:
Okay I know this is stupid, but since it takes a freaking week (I thought I'd sit down and flash Lineage "real quick"...joke's on me), does the OnePlus site want everything on BOTH lines of that unlock code section, appended together as one long string? Or is that two separate codes?
View attachment 5537469
Click to expand...
Click to collapse
Just flash my EU conversion, update to the latest stable OOS, then go lineage away and forget this nonsense unlock.bin.
But to answer your question: Copy both lines as 1 line without any breaks or spaces. Then enjoy waiting 2 weeks for the code, if the website decides to work at all.

craznazn said:
Just flash my EU conversion, update to the latest stable OOS, then go lineage away and forget this nonsense unlock.bin.
But to answer your question: Copy both lines as 1 line without any breaks or spaces. Then enjoy waiting 2 weeks for the code, if the website decides to work at all.
Click to expand...
Click to collapse
Thanks! Yep, in the end that's what I did. Flashed international FW with the MSM tool, then unlocked the bootloader without waiting for the token. Then spent about two more hours troubleshooting a bunch of unrelated stuff due to some user error, but in the end, landed with the phone on LOS 18.1 so I'm happy.

jefffeely said:
This took me way too long to figure out so Hopefully this will make it quicker for someone:
OnePlus Help Page
(Found ten pages in at https://forum.xda-developers.com/t/t-mobile-bootloader-unlock.4181339/page-10#post-83922873)
Once you have the unlock code go to: One Plus Unlock Token Page
If your phone does not show up in fastboot and you are on windows 10: https://forum.xda-developers.com/t/guide-fix-device-not-showing-up-in-fastboot-mode-windows-10.4194491/
The drivers will not install in windows 10 unless you Disable driver signing enforcement first.
In case you did not know, your phone comes with driver installation software that will show up when you plug your phone into your computer. However, if you have USB debugging turned on first, they will not pop up.
This is all basic stuff, but some times people need help with the basics!
(edited for clarity)
-----------------------------------------------------------------------------------------------------------
Edited to add the following next step
One week later (pretty much to the second) go back to: One Plus Unlock Token Page (you should also get an e-mail with a link. Download the file unlock_code.bin and place it in the same directory you will be running fastboot from.
Don't forget that if you continue past this point you will wipe your phone and have to go through the setup process again. Your phone will also ask for confirmation of this.
Also, as of 11.0.4.6.KB09CB continuing will change your widevine to L3.
Open a command prompt or terminal window and run the following:
adb reboot bootloader
fastboot flash cust-unlock unlock_code.bin
fastboot flashing unlock
------------------------------------------------------------
To Root:
Rooting instructions
Click to expand...
Click to collapse
I have done everything that I am suppose to and I will say this is the not the first phone I have rooted however I will say this is by far the most difficult. Now with that being said, have you or did you run into the error telling you to enter a valid IMEI. I know mine is correct T-Mobile verified it with me several times when they were so kind to network unlock my phone the same day I bought it. Any advice or suggestions would be appreciated.

a
Anyone have the conversion zip????

My problem is that my phone shipped with an incomplete serial number. The oneplus token website calls for an 8 digit serial but I only have 7 digits. OnePlus 9 Pro 5G from T-Mobile. Oneplus tech said I needed to add a 0 on the front end, but if I do that then the unlock code through ADB will not match to the change. Therefore my information is incorrect. I am in touch with Oneplus, but wish there was a third party token generator for my current details. Not sure if I have any other options. Grrrr!

TheGhost1951 said:
My problem is that my phone shipped with an incomplete serial number. The oneplus token website calls for an 8 digit serial but I only have 7 digits. OnePlus 9 Pro 5G from T-Mobile. Oneplus tech said I needed to add a 0 on the front end, but if I do that then the unlock code through ADB will not match to the change. Therefore my information is incorrect. I am in touch with Oneplus, but wish there was a third party token generator for my current details. Not sure if I have any other options. Grrrr!
Click to expand...
Click to collapse
Convert to EU via MSM, unlock bootloader with no unlock.bin

craznazn said:
Convert to EU via MSM, unlock bootloader with no unlock.bin
Click to expand...
Click to collapse
Thank you, will look into the conversion.

matt314159 said:
Thanks! Yep, in the end that's what I did. Flashed international FW with the MSM tool, then unlocked the bootloader without waiting for the token. Then spent about two more hours troubleshooting a bunch of unrelated stuff due to some user error, but in the end, landed with the phone on LOS 18.1 so I'm happy.
Click to expand...
Click to collapse
Hello there can you help me out with The OnePlus 8 t mobile it's locked and OEM is grey.. I talked to t mobile .. and I don't have a t mobile account since I live in Pakistan.
It's carrier locked and it's t mobile firmware ..
Please guide me how can I fix it
My mail: [email protected]
Thanks
.

craznazn said:
Just flash my EU conversion, update to the latest stable OOS, then go lineage away and forget this nonsense unlock.bin.
But to answer your question: Copy both lines as 1 line without any breaks or spaces. Then enjoy waiting 2 weeks for the code, if the website decides to work at all.
Click to expand...
Click to collapse
Hey there, maybe you could help with how to unlock bootloader without the token?
i'm on international firmware.
I did just submit my token to oneplus but would rather not wait.
Do i need something else?
thanks!!

hugh288 said:
Hey there, maybe you could help with how to unlock bootloader without the token?
i'm on international firmware.
I did just submit my token to oneplus but would rather not wait.
Do i need something else?
thanks!!
Click to expand...
Click to collapse
Shouldn't need the token on international firmware. A simple fastboot oem unlock should do it. Just be sure you have OEM unlocking enabled under developer options.

hugh288 said:
Hey there, maybe you could help with how to unlock bootloader without the token?
i'm on international firmware.
I did just submit my token to oneplus but would rather not wait.
Do i need something else?
thanks!!
Click to expand...
Click to collapse
If you converted via MSM, you don't need an unlock code.

craznazn said:
If you converted via MSM, you don't need an unlock code.
Click to expand...
Click to collapse
I did try to fastboot oem unlock but it says I need the token.

hugh288 said:
I did try to fastboot oem unlock but it says I need the token.
Click to expand...
Click to collapse
Are you on OOS12? If so, then yeah you do need it.
If you just flash the conversion, you can unlock it then upgrade to OOS12