Database Users

Little Flashtool tutorial

This is an ancient tutorial. Stop frying me with PM's about it.

Outdated

Outdated

Thanks for this helpful guide!
Kudos!

I can get into flashboot mode but can't get into fastboot mode. I do it many times but it only charges my phone

I was never sure about using the fastboot toolbox until i read thru this. I would usually use the cmd window. I'll be flashing another of doom's test kernels later so i'll try it then. Thanks for going thru it
Sent from my R800i

I tried flashing my Xperia R800x back to stock with flashtool. The drivers installed fine but where I connect the phone flashtool says "ERROR FLASHING: Aborted"

thanks mate...help me alot

Thanks, great tutorial! Much appreciated.

Logseman said:
And now that we've covered flashing ROMs, we'll give our attention to the Fastboot Toolbox. Fastboot is a tool which can only be used normally through the command-line interface. This toolbox is basically a (quite raw) graphical shortcut to the relevant commands for our purposes.
We can activate it if we run Flashtool, click on the Flash icon, and select the Fastboot Mode.
{
"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"
}
I'll comment the buttons' functions and the equivalent fastboot command if it exists . That is for the benefit of the people who use Fastboot in non-Windows desktops.
Check current device status: this checks the status of your device, to see if it's on, off, in Flash mode or Fastboot mode.
Reboot into fastboot mode (via ADB) (adb reboot bootloader): with your device switched on, it will try to reboot directly into Fastboot mode. I'm not sure if it works...
Reboot into fastboot mode (via Fastboot) (fastboot reboot-bootloader): with your device on Fastboot mode, it will reboot in Fastboot mode again. It's mostly useful for testing purposes, but the common user won't need that too much.
Select kernel to HotBoot (fastboot boot X.img): this command will prompt you to select a certain kernel in order to boot it (NOT install it). This is helpful mostly again for testing purposes, but there are cases when it might come handy.
Select kernel to Flash (fastboot flash boot X.img): This is the command you'll be using most likely. You'll be prompted to choose a kernel, exactly like before, but in this case the kernel you choose will be INSTALLED. Unless you're a tester, make sure to flash kernels which are safe to install.
Here comes an example of flashing a kernel (DoomKernel v08):
Get Ver Info (fastboot getvar version): this is a pretty pointless command by itself as it will give you the Fastboot version installed, but the "fastboot getvar" command is pretty powerful, giving you information about a lot of the internals of the phone. Of course, those informations make sense to developers, while common users can largely ignore them.
Get Device info (fastboot devices): this command will output the Fastboot ID of your phone.
Reboot device into system (fastboot reboot): this command will reboot your phone.
With all these bases covered, you can happily operate with your Xperia Play. Have fun!
Click to expand...
Click to collapse
i unable to boot unlocker using bootflash
pls advice

Screw yourself.

Logseman said:
Screw yourself.
Click to expand...
Click to collapse
If you are referring to the last post on page 1 dated Sept. 23rd of this year, you could have said something nicer then that.
priteshc:
Easiest method is to got to Wotan Server and download their Xperia PLAY Drivers:
http://www.wotanserver.com/en/page/download
Download the X-Unlock Client and install first, it will install the fastboot and S1 drivers. Then install the Xperia PLAY Flash Driver file and install. After that you should be golden to flash away.
Good luck.

I could. And he could have not undug a thread 2 years old quoting a full post to post unintelligible crock. How does one even come here? I wrote this when we were in an ancient version of FlashTool...

Logseman said:
I could. And he could have not undug a thread 2 years old quoting a full post to post unintelligible crock. How does one even come here? I wrote this when we were in an ancient version of FlashTool...
Click to expand...
Click to collapse
True, not trying to argue or anything. And I am too a bit curious to see a thread revived after all this time. I would venture that said member did a search online and it pulled this thread up so he left a reply.
Anyways, lets consider this thread done as the information while helpful is dated. Still though despite its age thank you for posting this tutorial out 2+ years ago. I know it helped me 2+ years ago when i got my first PLAY (R800x), now R800at.

Thanks!!
Thank you with all my heart, for unraveling this blessing unto me and guiding me! :good:
I might just add that for unbricking/flashing, as these links are old, i founded out new ones:
flashtool: mediafire.com/u8i5kui5b8lg/5cz5nda84565ahb/flashtool-0.5.3.0-windows.exe
tft file for xperia play: htaaatp://download2141.mediafire.com/jbnc50uejxsg/pbh253qd2dv355b/R800i_4.0.1.A.0.283_%281247-6212%29.zip (remove "a")

You sir, are a ****ing disgrace!
I jsut followed your guide from this link
Then you forward me to this page, to download Android..
The funny thing is, the first guide is for Linux, but you end up, on a download site, where you need to install a ****ing iLivid.. And that's for Windows only.
Logseman said:
Why-and-how-to use Flashtool
Flashtool is your warranty, basically. Whereas PC Companion and SEUS are fairly limited about the kinds of reparations they can do ("no can do" with modified firmwares of any kind), Flashtool is your unbricking tool of choice. And if you have unlocked your bootloaders, it's the only 100% safe way to upgrade to new builds, as OTA and PC Companion updates can bring trouble.
In order to use Flashtool, we need FTF files with entire builds to flash. No problem: here they are, all of them. Once we have downloaded the one we want, we must put it in the "firmwares" folder of Flashtool so that it can be flashed.
Now we can fire up Flashtool, click on the left icon (the lightning bolt):
Choose Flash mode:
Select the firmware we wish (note that you have a couple of options for newer builds such as keeping your user data, but you better know what you're doing or you'll probably screw up the firmware):
Wait until the files are prepared...
And connect our device in Flash mode as specified before.
Once AND ONLY ONCE the process is finished, we can disconnect the USB cable and restart our phones.
Click to expand...
Click to collapse

This tutorial is three years old. I have not maintained it since I made it. How am I to know what's been of the links?

[Q] Bootloader Unlocked ?

my new S7 Edge (No Brand Europe) it show me OEM UNLOCK line under Developer Options Tab
I have turned on button and restarted device.
So, Can this device be Bootloader unlockable ?
{
"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"
}

wolfgart said:
my new S7 Edge (No Brand Europe) it show me OEM UNLOCK line under Developer Options Tab
I have turned on button and restarted device.
So, Can this device be Bootloader unlockable ?
Click to expand...
Click to collapse
Yes.
Oh, and thanks for making me excited before I read you weren't referring to a Vodafone branded model.

Beefheart said:
Yes.
Oh, and thanks for making me excited before I read you weren't referring to a Vodafone branded model.
Click to expand...
Click to collapse
YES? Sure ?
So, How to boot device in Fastboot mode to unlock bootloader ?

wolfgart said:
YES? Sure ?
So, How to boot device in Fastboot mode to unlock bootloader ?
Click to expand...
Click to collapse
You don't need to unlock it, that toggle being there means the bootloader isn't locked in the first place. Just untoggle it and you're good to go. Besides, I knew for a fact before I created this thread that the non-branded international model didn't have a locked bootloader. Samsung do not lock bootloaders, certain carriers when they order their phones ask Samsung to lock the bootloader for them before then applying bloat and carrier features. I'm just hoping at this point that Vodafone UK isn't one of them.

Beefheart said:
You don't need to unlock it, that toggle being there means the bootloader isn't locked in the first place. Just untoggle it and you're good to go. Besides, I knew for a fact before I created this thread that the non-branded international model didn't have a locked bootloader. Samsung do not lock bootloaders, certain carriers when they order their phones ask Samsung to lock the bootloader for them before then applying bloat and carrier features. I'm just hoping at this point that Vodafone UK isn't one of them.
Click to expand...
Click to collapse
Wrong, that toggle is not bootloader unlock, nor is it an indication you can unlock your bootloader. It simply is a setting within android OS to allow you to use selinux permissive kernels. Even the AT&T S6 had it, and their bootloader is locked down tighter then a submarine.
Sent from my SM-T710 using Tapatalk

EDIT...............

Beefheart said:
Great. Not what I read. How do you find out the bootloader is unlocked then?
Click to expand...
Click to collapse
You try to flash a custom kernel using ODIN, if it boots, it's unlocked.
I would assume there is an indication of whether your device is locked or not in the rom download screen as well.
Beware that flashing a custom kernel on the device will trip the knox counter to 0x1, which on Snapdragon SOC is irreversible (a fuse is blown), it can be undone on the Exynos version (as the flag is stored in eMMC) if the Engineering/JIG firmware ever leaks (this happened a while back on the Note 3)

mathieulh said:
You try to flash a custom kernel using ODIN, if it boots, it's unlocked.
I would assume there is an indication of whether your device is locked or not in the rom download screen as well.
Beware that flashing a custom kernel on the device will trip the knox counter to 0x1, which on Snapdragon SOC is irreversible (a fuse is blown), it can be undone on the Exynos version (as the flag is stored in eMMC) if the Engineering/JIG firmware ever leaks (this happened a while back on the Note 3)
Click to expand...
Click to collapse
Here my screen on Download Mode :
Fap Lock is OFF

wolfgart said:
Here my screen on Download Mode :
Fap Lock is OFF
Click to expand...
Click to collapse
That's FRP, which stands for Factory Reset Protection. This relates to the OEM Toggle option I talked about earlier in the thread. I was under the impression that, in order for that to be off when you get the phone, the bootloader is unlocked. But according to _Dennis_ that isn't the case.
I would really like an easy way of finding out if Vodafone have locked this bootloader without flashing a custom kernel, of which there are none at the moment anyway. If this thing is locked, I'm returning it so only have a small window to do so.

Been searching everywhere, but it seems the only way to tell this for sure is to flash a custom ROM\Root the phone and see if it works.
Going by past experience with Vodafone since the original S phone, it hasn't been locked, so it would be a shame if they have decided to start doing this!
---------- Post added at 11:04 AM ---------- Previous post was at 11:00 AM ----------
http://forum.vodafone.co.uk/t5/Samsung-Galaxy-S7-Edge/S7-Edge-Bootloader-Unlocked/m-p/2475021
Most latest posts on that thread indicate its unlikely to be locked, but we still need to wait and see.
We may even have to wait for root to become available before we can find out!

EDIT..............................

if its an international non carrier, sim free and purchased outright from samsung or anywhere else; then the boot-loader is unlocked or at the very least easily unlockable

_Dennis_ said:
Wrong, that toggle is not bootloader unlock, nor is it an indication you can unlock your bootloader. It simply is a setting within android OS to allow you to use selinux permissive kernels. Even the AT&T S6 had it, and their bootloader is locked down tighter then a submarine.
Sent from my SM-T710 using Tapatalk
Click to expand...
Click to collapse
I've since discovered your claim is completely wrong, it has nothing to do with selinux state, and it is related to the bootloader as I indicated. Read the following:-
http://android.wonderhowto.com/insp...ndroid-even-if-you-dont-plan-rooting-0167840/
Also, look at the description under the toggle.
However, I'm unsure if it does indicate the bootloader is unlocked at this time.

Beefheart said:
I've since discovered your claim is completely wrong, it has nothing to do with selinux state, and it is related to the bootloader as I indicated. Read the following:-
http://android.wonderhowto.com/insp...ndroid-even-if-you-dont-plan-rooting-0167840/
Also, look at the description under the toggle.
However, I'm unsure if it does indicate the bootloader is unlocked at this time.
Click to expand...
Click to collapse
Interesting. Ill see what mine says when I get home. Its strange I never had this on my other Samsung S devices, so it must be new.

My Verizon S7 Edge also has this toggle. I don't know if it actually unlocks the bootloader though.

Blart said:
My Verizon S7 Edge also has this toggle. I don't know if it actually unlocks the bootloader though.
Click to expand...
Click to collapse
Could you boot into your download mode and post a photo of the screen? I'd like to compare it to mine.

Beefheart said:
There is a way. Go into download mode, connect to PC and you can check via the fastboot command in a command prompt.
> fastboot devices (to check if the device is seen)
> fastboot oem device-info
Look for:-
Bootloader unlock allowed - Yes >> This means that your Bootloader is Locked
Bootloader Unlocked - Yes >> This means that your Bootloader is unlocked
Click to expand...
Click to collapse
strange, i don't have fastboot commands works on Download mode.
I always use them with my LG G4
it seems fastboot commands are not allowed ...

My wife said the same when I run through the instructions at home over the phone, I thought it was simply my laptop and a driver error. But perhaps there is an issue with the fastboot command with the S7's bootloader.
I need to find out today if this thing is bootloader unlocked, so I can return it fast if it isn't.

wolfgart said:
Here my screen on Download Mode :
Fap Lock is OFF
Click to expand...
Click to collapse
This download screen is identical to mine.

_Dennis_ said:
Wrong, that toggle is not bootloader unlock, nor is it an indication you can unlock your bootloader. It simply is a setting within android OS to allow you to use selinux permissive kernels. Even the AT&T S6 had it, and their bootloader is locked down tighter then a submarine.
Sent from my SM-T710 using Tapatalk
Click to expand...
Click to collapse
The dumb thing about this is if you can't boot the phone you cant toggle that option, you can't unlock the bootloader to flash a stock rom.
wolfgart said:
Here my screen on Download Mode :
Fap Lock is OFF
Click to expand...
Click to collapse
Heh fap lock

Fastboot Mode On LG K10 Qualcomm Variants!

Hi guys!
Never nuke your LAF partition or if you did nuke LAF consider your phone is bricked (repairable but too hard!).
Not the best idea to nuke LAF partition when that's the most important partition of your phone when you brick it!
But a little information:
{
"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 the difference between MTK & Qualcomm "Fastboot" Commands!
fastboot oem unlock works in MTK because it is present in its LK(Little Kernel)
fastboot oem unlock doesnt work in Qualcomm because it isnt present in aboot of Qualcomm
That's why fastboot getvar and download command works in fastboot that's it!

Reserved.

pvineeth97 said:
Reserved.
Click to expand...
Click to collapse
Good work!

Unlock BL.
pvineeth97 said:
Hi guys!
With the help of @Macgeek I bring you the guide to enter "Fastboot Mode" in Qualcomm Variants!
Phones Supported:
K420DS
K420N
Install LG Drivers & Python before trying this.
1. Put your phone in "Download Mode".
2. Connect the phone to your computer using USB.
3. Download these files: https://github.com/Lekensteyn/lglaf/archive/master.zip.
4. Extract those files. Enter the folder. Press "Shift" and Right Click on your mouse. Select "Open Command Window here".
5. Type "python partitions.py --wipe laf" (without quotes)
6. Remove Battery. Place Battery back. Now enter "Download Mode" again.
You entered "Fastboot"!
You loose "Download Mode". If you are rooted you can get it back by using ADB.
Now, I am looking for what possibilities are present since we entered "Fastboot".
If you unlock the bootloader using "Fastboot", Tell us! We are excited!
This is the difference between MTK & Qualcomm "Fastboot" Commands!
fastboot oem unlock works in MTK because it is present in its LK(Little Kernel)
fastboot oem unlock doesnt work in Qualcomm because it isnt present in aboot of Qualcomm
That's why fastboot getvar and download command works in fastboot that's it!
Click to expand...
Click to collapse
So like I understand I will not able to unlock my BootLoader with this guide on my UnRooted LG K420N and also will loose download mode, so will be not able to flash LG Stock KDZ Files to bring my device to life if I will have problems?
I'm very very disappointed with this device, first device that I can't get root access ?

D_Vovan_238 said:
So like I understand I will not able to unlock my BootLoader with this guide on my UnRooted LG K420N and also will loose download mode, so will be not able to flash LG Stock KDZ Files to bring my device to life if I will have problems?
I'm very very disappointed with this device, first device that I can't get root access
Click to expand...
Click to collapse
Well if you are rooted you can get the "Download mode" back by flashing back the partition using adb root shell. All devices except Qualcomm Snapdragon 410 models of LG K10 have unlocked bootloaders.
If we get hold of a "Developer" edition of the bootloader of this device (aboot) we can unlock bootloader.

I have an qualcom 410 snap dragon has locked bootloader lg ls775 stylo2

roadkill42 said:
I have an qualcom 410 snap dragon has locked bootloader lg ls775 stylo2
Click to expand...
Click to collapse
We don't know much about your device.

If i tried it how would i get download mode back im willing to try i know its not same phone but might work

roadkill42 said:
If i tried it how would i get download mode back im willing to try i know its not same phone but might work
Click to expand...
Click to collapse
You need to be rooted first.
Make a backup of "laf" partition.
Then in adb, flash the "laf" partition to flash the download mode.

Lg k10 k430dsF
Haven't any version for Lg k10 k430dsF?
Isn't compatible this fastboot?

I am trying to unlock the bootloader on the LG Tribute HD model LGELS676 which is a k6 varient. We cannot enter fastboot no matter what... Do you think this method and. zip scripts would or could work for us? Would I need to edit the scripts for our device? We can't even get temp root right now and we are going on 3 months of trying to enter fastboot lol any help is seriously appreciated

Sands207 said:
I am trying to unlock the bootloader on the LG Tribute HD model LGELS676 which is a k6 varient. We cannot enter fastboot no matter what... Do you think this method and. zip scripts would or could work for us? Would I need to edit the scripts for our device? We can't even get temp root right now and we are going on 3 months of trying to enter fastboot lol any help is seriously appreciated
Click to expand...
Click to collapse
Give me more details of your device so that I can help you.

Taken from here http://www.lg.com/us/cell-phones/lg-LS676-Virgin-tribute-hd
Technical Specifications
Carrier Virgin Mobile
Display 5.0" (1280 x 720) HD TFT Display
Battery 2,100 mAh Removable
Platform Android 6.0.1 Marshmallow build MXB48T
Processor Qualcomm Snapdragon™ 1.3 GHz Quad-Core MSM8909
Frequency LTE Bands 2/4/5/12/25/26/41; GSM 850/900/1800/1900 MHz; UMTS Bands 2/4/5; CDMA Bands 0/1/10
Technology LTE, CDMA, GSM, UMTS
Data Transmission LTE, UMTS, HSPA+, HSDPA, 1xRTT, EVDO, EVDO Rev A, GSM
Internal Memory 16 GB (up to 9.93 GB usable)
microSD card Support up to 32 GB**
RAM 1.5 GB
My device is unrooted and has a locked bootloader for obvious reasons.
I have a full adb system dump and other files I have built from source also if that is useful to you. I have linux at my disposal so if I can do anything further please let me know. We are basically in the same boat the K10 was in and development and root is at a standstill until we can access fastboot to unlock our bootloader so we can proceed. Mine is a qualcomm I'm guessing that that is why
Code:
fastboot oem unlock
or any fastboot command has zero effect and there is no known button combo to access it, adb works just fine though. I apppreciate your help very much and I know alot of other people do too

Sands207 said:
Taken from here http://www.lg.com/us/cell-phones/lg-LS676-Virgin-tribute-hd
Technical Specifications
Carrier Virgin Mobile
Display 5.0" (1280 x 720) HD TFT Display
Battery 2,100 mAh Removable
Platform Android 6.0.1 Marshmallow build MXB48T
Processor Qualcomm Snapdragon™ 1.3 GHz Quad-Core MSM8909
Frequency LTE Bands 2/4/5/12/25/26/41; GSM 850/900/1800/1900 MHz; UMTS Bands 2/4/5; CDMA Bands 0/1/10
Technology LTE, CDMA, GSM, UMTS
Data Transmission LTE, UMTS, HSPA+, HSDPA, 1xRTT, EVDO, EVDO Rev A, GSM
Internal Memory 16 GB (up to 9.93 GB usable)
microSD card Support up to 32 GB**
RAM 1.5 GB
My device is unrooted and has a locked bootloader for obvious reasons.
I have a full adb system dump and other files I have built from source also if that is useful to you. I have linux at my disposal so if I can do anything further please let me know. We are basically in the same boat the K10 was in and development and root is at a standstill until we can access fastboot to unlock our bootloader so we can proceed. Mine is a qualcomm I'm guessing that that is why
Code:
fastboot oem unlock
or any fastboot command has zero effect and there is no known button combo to access it, adb works just fine though. I apppreciate your help very much and I know alot of other people do too
Click to expand...
Click to collapse
So there are many LG phones which are in the same boat as K10! Wow! I did'nt know that!
Send me the adb system dump, other files you collected and the firmware file if you have it.
I am developing a root method for Android 6.0 with help of other devs. I can port that script to your device if you want.
Its better if you contact me on What'sapp so we can talk about getting into fastboot and root stuff and I can help you easily. I could help you build a TWRP for your device. I sent my number to you as a private message.

pvineeth97 said:
So there are many LG phones which are in the same boat as K10! Wow! I did'nt know that!
Send me the adb system dump, other files you collected and the firmware file if you have it.
I am developing a root method for Android 6.0 with help of other devs. I can port that script to your device if you want.
Its better if you contact me on What'sapp so we can talk about getting into fastboot and root stuff and I can help you easily. I could help you build a TWRP for your device. I sent my number to you as a private message.
Click to expand...
Click to collapse
Thank you so much! I'm getting out of work in a little over an hour and ill try to gather as much as i can that I have for files to help the process. I will add you on whatsapp too. I'm shaking right now hoping this 3 month ordeal to fight for root and unlocking the bootloader will soon be over. Many jumped ship already but ive been trying to tell these guys from the beginning there HAS to be a way, I know this because I worked on the LG Volt which had similar woes but were eventually overcome ? I'll Be in touch shortly. THANK YOU ?
Sent from my LGLS676

pvineeth97 said:
So there are many LG phones which are in the same boat as K10! Wow! I did'nt know that!
Send me the adb system dump, other files you collected and the firmware file if you have it.
I am developing a root method for Android 6.0 with help of other devs. I can port that script to your device if you want.
Its better if you contact me on What'sapp so we can talk about getting into fastboot and root stuff and I can help you easily. I could help you build a TWRP for your device. I sent my number to you as a private message.
Click to expand...
Click to collapse
wait a moment... does this mean there is a chance deleting my download mode and screwed up updates was not completely useless?

MRMACGEEK said:
wait a moment... does this mean there is a chance deleting my download mode and screwed up updates was not completely useless?
Click to expand...
Click to collapse
Yes, sir! That's what I am basically working for...

pvineeth97 said:
Yes, sir! That's what I am basically working for...
Click to expand...
Click to collapse
well, i can only teel you im extremely grateful and happy to havegiven you an entrypoint of some sort

MRMACGEEK said:
well, i can only teel you im extremely grateful and happy to havegiven you an entrypoint of some sort
Click to expand...
Click to collapse
Actually it even motivated me more to get root for Android 6.0!

Two cents
Sands207 said:
Thank you so much! I'm getting out of work in a little over an hour and ill try to gather as much as i can that I have for files to help the process. I will add you on whatsapp too. I'm shaking right now hoping this 3 month ordeal to fight for root and unlocking the bootloader will soon be over. Many jumped ship already but ive been trying to tell these guys from the beginning there HAS to be a way, I know this because I worked on the LG Volt which had similar woes but were eventually overcome I'll Be in touch shortly. THANK YOU
Sent from my LGLS676
Click to expand...
Click to collapse
I'm in the long thread on Androidforums.com about the LGLS775 Stylo 2 (MM 6.0) too.... Caught the entire zd4 upgrade file if that could help, download links somewhere in the thread & few other posts in XDA on this device. If you think it could help, let me know & will toss a download link in.
Got notice on Nougat upgrade... gonna factory reset, logcat it & intercept it as well.....
GREAT JOB IN HERE!!!!
zach
ps. Zd4 is 1.4gb

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

[SOLVED] Redmi A1 (Ice) - Unlock bootloader: Error 0x1002

Hello,
I have recently acquired an Xiaomi Mi A1 device to try LineageOS.
I follow the steps of the official installation guide here: https://wiki.lineageos.org/devices/tissot/install
I'm facing problems to unlock the bootloader. Despite many tries, the command "fastboot oem unlock" return the following error code "0x1002"
ADB version: 1.0.41
fastboot version: 33.0.3-8952118
USB debugging: ON
OEM unlock: ON
I have access to the fastboot mode, the device is listed with adb command "fastboot devices" and an entry appears on Windows Device Manager.
{
"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"
}
Here is the command result:
I have tried to factory reset the phone but the problem still occurs.
Also Mi Unlock tool seems not be usable because Mi Account APK (com.xiaomi.account) is not installed on the phone.
Yoru2647 seems facing the same issue: https://forum.xda-developers.com/t/urgent-help-xiaomi-mi-a1-unlock-bootloader.4295115/post-87995167
Did i miss something? Any ideas about this 0x1002 error code?
Thanks for your advices.

Eren'X said:
Hello,
I have recently acquired an Xiaomi Mi A1 device to try LineageOS.
I follow the steps of the official installation guide here: https://wiki.lineageos.org/devices/tissot/install
Thanks for your advices.
Click to expand...
Click to collapse
You must have a Xiaomi account with the associated phone,
If you don't have an account, create one and use the official Xiaomi tool to unlock the bootloader.
Unlocking bootloader:
https://new.c.mi.com/global/post/101245
https://en.miui.com/unlock/index.html

Thank you for the answer.
I tried that but I'm unable to finish it, the problem is that I cannot bind the Xiaomi account on the phone.
I'm stuck in this step:
The phone was delivered with Android 12 (Go edition) without MIUI's layer. The build number indicate: 12 V13.0.8.0SGMEUXM
That means i have not "Mi Unlock status" on developer options or "Mi Account" on phone settings.
Is it possible to install additional components for bind Mi account on the phone? or any workaround to bypass it?
I desperately tried to install Xiaomi Account APK manually with adb: https://www.apkmirror.com/apk/xiaomi-inc/mi-account/mi-account-r-22-12-26-01-release/
But it failed with the error : "Reconcile failed: Package com.xiaomi.account requires unavailable shared library security-device-credential-sdk.jar; failing!]"
Is it possible to put one of the official MIUI ROM on phone even with a locked bootloader? (like these ones: https://xiaomifirmwareupdater.com/miui/tissot/)

Eren'X said:
Thank you for the answer.
I tried that but I'm unable to finish it, the problem is that I cannot bind the Xiaomi account on the phone.
I'm stuck in this step:
The phone was delivered with Android 12 (Go edition) without MIUI's layer. The build number indicate: 12 V13.0.8.0SGMEUXM
That means i have not "Mi Unlock status" on developer options or "Mi Account" on phone settings.
Is it possible to install additional components for bind Mi account on the phone? or any workaround to bypass it?
I desperately tried to install Xiaomi Account APK manually with adb: https://www.apkmirror.com/apk/xiaomi-inc/mi-account/mi-account-r-22-12-26-01-release/
But it failed with the error : "Reconcile failed: Package com.xiaomi.account requires unavailable shared library security-device-credential-sdk.jar; failing!]"
Is it possible to put one of the official MIUI ROM on phone even with a locked bootloader? (like these ones: https://xiaomifirmwareupdater.com/miui/tissot/)
Click to expand...
Click to collapse
check your model version: My phone/features/version
Example:
220733SG, 220733SH, 220733SI, 220733SL,MDG2, MDI2

Hi,
My model version is: 220733SG

Eren'X said:
Hi,
My model version is: 220733SG
Click to expand...
Click to collapse
Code name ACE not TISSOT.
And the phone is up to date
https://xiaomifirmwareupdater.com/archive/miui/ice/.
If you really want to unlock the bootloader.
Try: download Platform tools and run CMD/Power shell from platform tools folder.
CMD fastboot oem unlock
Power shell ./fastboot oem unlock

NOSS8 said:
Code name ACE not TISSOT.
Click to expand...
Click to collapse
Good catch, I should have paid more attention to this point.
I did not find any LineageOS ROM for it. I assume it is not supported on my phone for now.
However, i tried "fastboot oem unlock" command on both command promp and powershell with and without admin rights.
The result is the same: FAILED (remote: 'Unlock failed - Err:0x1002)
In the next days, i will continue to try few others things like changing USB cable, USB port, computer, ...
The problem also may be linked to FRP mode? i will check that too.
I will share the solution if i success.
Thanks

Eren'X said:
Good catch, I should have paid more attention to this point.
I did not find any LineageOS ROM for it. I assume it is not supported on my phone for now.
However, i tried "fastboot oem unlock" command on both command promp and powershell with and without admin rights.
The result is the same: FAILED (remote: 'Unlock failed - Err:0x1002)
In the next days, i will continue to try few others things like changing USB cable, USB port, computer, ...
The problem also may be linked to FRP mode? i will check that too.
I will share the solution if i success.
Thanks
Click to expand...
Click to collapse
Have you enabled usb debugging?
And why would you want to unlock the bootloader?
may be try https://forum.xda-developers.com/t/...ck-twrp-factory-image-stock-recovery.3695256/

Eren'X said:
Hello,
I have recently acquired an Xiaomi Mi A1 device to try LineageOS.
I follow the steps of the official installation guide here: https://wiki.lineageos.org/devices/tissot/install
I'm facing problems to unlock the bootloader. Despite many tries, the command "fastboot oem unlock" return the following error code "0x1002"
ADB version: 1.0.41
fastboot version: 33.0.3-8952118
USB debugging: ON
OEM unlock: ON
I have access to the fastboot mode, the device is listed with adb command "fastboot devices" and an entry appears on Windows Device Manager.
View attachment 5821853
Click to expand...
Click to collapse
Your device has to be listed like Android Bootloader Interface, this image is referential, taken from the net.
Eren'X said:
Thank you for the answer.
I tried that but I'm unable to finish it, the problem is that I cannot bind the Xiaomi account on the phone.
I'm stuck in this step:
View attachment 5822313
The phone was delivered with Android 12 (Go edition) without MIUI's layer. The build number indicate: 12 V13.0.8.0SGMEUXM
That means i have not "Mi Unlock status" on developer options or "Mi Account" on phone settings.
Click to expand...
Click to collapse
Your device is not Xiaomi Mi A1 (Tissot) but Redmi A1 (Ice), they're very different devices, even one came with Snapdragon when yours come with MediaTek.
Pay attention specially if you think to root it or install some custom ROM on it.
It runs Android One, not Android Go (Edition).
Eren'X said:
Is it possible to install additional components for bind Mi account on the phone? or any workaround to bypass it?
I desperately tried to install Xiaomi Account APK manually with adb: https://www.apkmirror.com/apk/xiaomi-inc/mi-account/mi-account-r-22-12-26-01-release/
But it failed with the error : "Reconcile failed: Package com.xiaomi.account requires unavailable shared library security-device-credential-sdk.jar; failing!]"
Click to expand...
Click to collapse
In Xiaomi devices running Android One, you don't need (nor can't) to bind an account, and the Xiaomi Unlock tool is useless for.
Unlocking bootloader is done through command fastboot oem unlock
Eren'X said:
The problem also may be linked to FRP mode? i will check that too.
Click to expand...
Click to collapse
FRP has nothing to do with.

Eren'X said:
Good catch, I should have paid more attention to this point.
I did not find any LineageOS ROM for it. I assume it is not supported on my phone for now.
However, i tried "fastboot oem unlock" command on both command promp and powershell with and without admin rights.
The result is the same: FAILED (remote: 'Unlock failed - Err:0x1002)
In the next days, i will continue to try few others things like changing USB cable, USB port, computer, ...
The problem also may be linked to FRP mode? i will check that too.
I will share the solution if i success.
Thanks
Click to expand...
Click to collapse
Facing the same issue, FAILED (remote: 'Unlock failed - Err:0x1002) when trying "fastboot oem unlock". I have tried Please share if you find solution thanks

If all the mentioned were met, and the error persists, then try opening the CMD as admin.

NOSS8 said:
Code name ACE not TISSOT.
Click to expand...
Click to collapse
SubwayChamp said:
Your device is not Xiaomi Mi A1 (Tissot) but Redmi A1 (Ice), they're very different devices, even one came with Snapdragon when yours come with MediaTek.
Click to expand...
Click to collapse
Helpful answers.
Finally, i did it.
This article give the soluce: https://www.droidwin.com/unlock-bootloader-on-mediatek-devices-using-mtkclient
"However, there are a few MediaTek devices that don’t accept any of these Fastboot Commands. if your device also falls in this domain, then this guide shall help you out. In this tutorial, we will show you the detailed steps to unlock the bootloader on your MediaTek device using MTKClient."
I followed it step by step and it works!
SubwayChamp said:
Pay attention specially if you think to root it or install some custom ROM on it.
Click to expand...
Click to collapse
Yep, I haven't found a lot of custom ROM who support (ice) codename.
Any better place here to post about "Redmi A1/POCO C50/A1+ (ice)"?
I don't seem to be the only one to make this confusion.

Eren'X said:
Helpful answers.
Finally, i did it.
View attachment 5828629
This article give the soluce: https://www.droidwin.com/unlock-bootloader-on-mediatek-devices-using-mtkclient
"However, there are a few MediaTek devices that don’t accept any of these Fastboot Commands. if your device also falls in this domain, then this guide shall help you out. In this tutorial, we will show you the detailed steps to unlock the bootloader on your MediaTek device using MTKClient."
I followed it step by step and it works!
Yep, I haven't found a lot of custom ROM who support (ice) codename.
Any better place here to post about "Redmi A1/POCO C50/A1+ (ice)"?
I don't seem to be the only one to make this confusion.
Click to expand...
Click to collapse
Well, not, unfortunately, it seems that your device is not popular at all among developers. As a "deposit" of custom ROMs, you should try AFH, SourceForge, PlingOS, apart than from Twitter.
Depending on how many similar are the two linked devices, then you should search for something for them.

The device is young, it's been released in September 2022. I don't expect to find a custom ROM before long time.
The generic system images may be a good alternative in this case, like this one: https://forum.xda-developers.com/t/gsi-13-lineageos-20-light.4509315/
It's not my daily phone, i get it specifically to experiment. I would be careful, but for 80$ it's not a big loss if i brick it.
I will try it when i have more free time.
Thanks for helping

Eren'X said:
The device is young, it's been released in September 2022. I don't expect to find a custom ROM before long time.
The generic system images may be a good alternative in this case, like this one: https://forum.xda-developers.com/t/gsi-13-lineageos-20-light.4509315/
It's not my daily phone, i get it specifically to experiment. I would be careful, but for 80$ it's not a big loss if i brick it.
I will try it when i have more free time.
Thanks for helping
Click to expand...
Click to collapse
Yes, it's not much time since was released, the normal waiting time could be at least 6 months.
Yes, GSIs, are a good alternative.
Don't forget to back up all the partitions available, less userdata, that occupy a really huge size (about 100 GB of storage), and super partition (don't care about). And a last advice, never user format all feature through SPFT, otherwise you'll erase NVRAM partition, fingerprint, LTE signal, IMEI and more.