Related
This is a tutorial on how to Unlock the bootloader of xperia devices.
First of all: This will void your warranty and only necessary to install custom kernels or custom roms. If someone told you to unlock the bootloader for rooting, you needn't do that. Just check out my rooting guide here. So let's go on - and - read everything carefully!!!!
I accept no responsibility for any damage of your phone or pc! You do all this on your own risk!
It will void your warranty and you will loose DRM, so you can't use trackid anymore. You mustn't do updates over the air, otherwise your phone will brick!!! You won't be able to update phone via pc companion or sony update service anymore, you will have to flash the rom via flashtool!
Unlocking the bootloader will wipe your /data partition. So please save your personal data before unlocking!
First you check, if your bootloader is unlockable. For that you have to be on stock sony rom. You type: *#*#7378423#*#*
Now you are in the service menu. Go to "Service info" -> Configuration and look at the bootloader status.
If Rooting Status -> Bootloader unlock allowed: yes, you can go on
{
"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"
}
1. Manually like on sony's homepage
2. Automatic with the SE Bootloader Unlocking Tool by quangnhut123
3. Testpoint Method
1. Manually
For this you need the following tools/files/etc:
- Android SDK from here
- Modified android_winusb.inf-file from here
- Fastboot.exe (Just search for it on google for example)
So let's start:
Go here and click yes. After that type in your IMEI. Go to your phone and type *#06#* and you will see your IMEI. Now go back to your browser, type in your Name, Email-adress and your IMEI and click submit.
LEAVE THE WINODW OPEN, IT WILL PROMPT YOUR UNLOCK CODE. Write it down on a piece of paper and lets go on.
Now we will set up android sdk. You install it to the directory you want and start it.
Check your Android Version, the Tools, and from extras the google usb driver and install them.
Now you go to the installation folder and open tools
and paste the fastboot.exe there:
Now you go back to the installation folder and open extras > google. There you paste the modified android_winusb.inf
Now we have everything set up and can go on the phone :good:
Turn off your phone and hold the unlock button (usually the volume up button) and connect to pc. The blue led will light up.
Go on the pc and your pc will ask you for drivers. Point to the android_winusb.inf-file and your phone will be recognized. If not, download flashtool from here and install it. You go to the installation folder and open drivers and install all the drivers provided.
Now we open a command window from windows and go to the installation folder of the android sdk. Then we go in the tools folder. Use the following commands to navigate:
cd .. = one folder up
cd foldername = open folder
dir = show content of the folder
And we can see the fastboot.exe in the tools folder:
Now the unlock process begins, make sure the phone is charged (over 20% is a must have, better fully)
We type in the command window:
fastboot.exe -i 0x0fce getvar version
and if we get a value like 0.3 the phone is connected and responsing.
The next step unlocks the bootloader
To unlock your bootloader now enter the following code:
fastboot.exe -i 0x0fce oem unlock 0xKEY
Watch Out: You have to change KEY to the key you got earlier!
If everything goes well, you have an unlocked bootloader now! Congratulations
Now we are able to flash a custom kernel/rom, so check this out to know how to install the new kernel/rom
This tutorial is based on the tutorial from sony. I don't own any files and if sony doesn't like me to do this tutorial, please let me know and I will delete this topic!
2. Automatically with the SE Bootloader Unlocking Tool by quangnhut123
For that you go to this thread and hit thanks. After that download the tool.
Remember, unlocking the bootloader will void warranty! After unlocking bootloader, never try to update ota (=over the air)! PC Companion and SEUS won't recognize your phone after the following steps!
Make sure your pc is connected to the internet, to get the unlock code from sony website. You will lose DRM like in the other tutorial!
If you want to unlock now, follow these steps:
1. Extract "SE Bootloader_Unlocking_Relocking_1.6.rar" and you'll find out "Flashtool-drivers.exe", run it to install. Check all drivers/phones, just to be sure all drivers are installed
2. Go to phone an input on the dial pad *#06#* to promt your IMEI.
3. Open the unlocking tool and in the first text field input the first 14 digits of your IMEI.
4. Press the Get Unlock Code button. Your unlock code will automatically appear in the Unlock Code Box.
5. Now turn off the phone, hold Volume Up and while pressing it you connect the USB cable to the computer. The blue led should appear, which means you are in fastboot mode to unlock bootloader.
6. Click the Unlock BL button. The program will automatically unlock your bootloader!
Click to expand...
Click to collapse
That's it, this is easier for newbie's, but remeber, it voids warranty! And do it on your own risk!
3. Testpoint method
If you don't want to void your warranty (okay you do, but you can relock your bootloader and with some luck sony won't notice it's been opened, so you still have your warranty ) you can use the testpoint method.
You have to mess around with the hardware. This sounds strange, right?
But it isn't even hard. Just read this great tutorial by DragonClawsAreSharp!
But note: This method will only work if your device was produced before building number 12w11 (as far as I know). You can check this number on the sticker under the battery
If you want to install a custom rom/kernel now, just go here for a guide
Thanks!!
Thanks!! Thumbs up!!
Nice guide for the newbie,deserved thumbs up from me
Sent from my GT-P1000 using xda premium
hi
in Bootloader unlock allowed i have No
what can i do?
midomad said:
hi
in Bootloader unlock allowed i have No
what can i do?
Click to expand...
Click to collapse
If bootloader unlock allowed:no you can't unlock it like this. Maybe you have a netlock or simlock?
Then you can just unlock using a paid method, for example wotan server, but that's more complicated and I can't promise that it works, because fastboot is disabled then
mihahn said:
If bootloader unlock allowed:no you can't unlock it like this. Maybe you have a netlock or simlock?
Then you can just unlock using a paid method, for example wotan server, but that's more complicated and I can't promise that it works, because fastboot is disabled then
Click to expand...
Click to collapse
so if i desimlock my phone i can unlock bootloader?
midomad said:
so if i desimlock my phone i can unlock bootloader?
Click to expand...
Click to collapse
Not sure some people say yes, other no. Maybe search on google for a solution
can u give the rom that can flash with lock bootloader?
hamimi said:
can u give the rom that can flash with lock bootloader?
Click to expand...
Click to collapse
There aren't so many, look in development section there's a thread with all roms listed. Open some roms and you will see on their thread if they are for locked bootloader
For example on ics there is MiniCMSandwich or Realics lite and some MIUI roms. There sould be roms for gingerbread, too, just look in development please :good:
reupload please
hey can you reupload se bootloader unlocking for xperia 2011 ?? cause the link by quangnhut123 is dead
Nice tutorial.
And why don't you add test point tutorial also? while it may looks tricky, I was using it with ease..
priendy said:
hey can you reupload se bootloader unlocking for xperia 2011 ?? cause the link by quangnhut123 is dead
Click to expand...
Click to collapse
Sorry, I don't have it installed. Please ask quangnhut123
ardian1899 said:
Nice tutorial.
And why don't you add test point tutorial also? while it may looks tricky, I was using it with ease..
Click to expand...
Click to collapse
Okay will add the link to a tutorial if the author gives me the permission
So my phone says No to bootloader unlock allowed. What do I do now? Does this mean I cannot unlock to bootloader no matter what?
garychencool said:
So my phone says No to bootloader unlock allowed. What do I do now? Does this mean I cannot unlock to bootloader no matter what?
Click to expand...
Click to collapse
Yes this means you can't, but have you got a simlock? Cause if yes you must unlock the simlock (for example with wotan server which costs some money or maybe your provider could do it) and with much luck you can unlock after that. :good:
Try first if you can go in fastboot mode, so set everything up, android-sdk and all the drivers, the winusb file etc, and connect your phone when it's off with pressed volume up key to pc. If the blue led lights up, you should be able to unlock the simlock and after that you could unlock the bootloader.
But I'm not sure, some people told us, that the unlocking of the simlock doesn't change anything for them...
Hope the day will come that for new phones like my ST15i can unlock without loosing DRM
when type in this code nothing happens?
amnher said:
Hope the day will come that for new phones like my ST15i can unlock without loosing DRM
Click to expand...
Click to collapse
I don't think there'll be a way, but for what do you need DRM? You don't loose features...
abumaha said:
when type in this code nothing happens?
Click to expand...
Click to collapse
So you type
Code:
fastboot.exe -i 0x0fce oem unlock 0xKEY
and nothing happens (of course you replace KEY with your unlock code)? Have you set everything up and phone is already plugged in the computer (and it's in fastboot mode)?
What a value do you get if you type
Code:
fastboot.exe -i 0x0fce getvar version
?
Maybe your bootloader is already unlocked. Please just start flashtool (if you haven't got it yet download it from development section) and if it has started connect phone in fastboot mode (shut down, hold volume up, connect to pc). Please post the log here (Please as a code!)
My phone wont turn on!!!!Ray
Ok, I flashed the fxp145 kernel and unlocked the kernel. It did boot into cam but it gave me an error saying sector 7 so I gave it another shot after removing the battery, but that didnt happen,it didnt boot up and neither is it showing charger status on led. But, there is warmth on the battery. i charged the battery for five hours straight, and now it blinks red when i push the powre button, but it wont still wont turn on. Is there anything i can do?
This should take you from the LG "Unlock Bootloader" form through to a fully-functional rooted TWRP'd device. This process wasn't quite as well documented as I would like, so I decided to take a shot at it. I don't guarantee any of this; it's all at your own risk. All props should go to those who went first. I merely got lost trying to follow and so built a map.
Ideally you want an “external” microSD card for this.
This also assumes you have already filled out the LG form and received the unlock.bin file. If not, retrieve it from LG using the tricks in this thread.
You also will want the twrp-3.1.1-0-h930.img image or the US998 TWRP unofficial alpha based on it. (They're the same except for a properties file change.)
And you need the Android development tools installed. I'm assuming you've done that.
1. Back up everything. It’s all going away.
2. If running Android Studio or Helium Desktop, shut it down. Otherwise you may see adb version issues.
a. Side-note: Don’t trust Helium to let you restore your data. Look for “Helium ceases to recognize backups” at https://github.com/koush/support-wiki/wiki/Helium-Wiki - It’s simply the wrong tool for this job.
3. Before you begin, copy the following files to your External SD Card. Otherwise you’ll have to do it later or attempt an adb sideload:
a. Magisk-v15.3.zip
b. no-verity-opt-encrypt-6.0.zip
c. (Optional)LG-rctd-disabler-1.0.zip4. Ensure you’re in developer mode. If Settings doesn’t have Developer Options, go to Settings – About Phone – Software Info, click Build number 7 times.
5. As per the LG page, http://developer.lge.com/resource/mobile/RetrieveBootloader.dev , ensure Developer Options “OEM Unlock” and “USB Debugging” are enabled.
6. Connect to USB and switch to Photo Transfer Mode. (If you’re a normal user, you probably default to USB. You need Photo.)
7. On your PC, copy the unlock.bin file LG emailed you into your Android development tools directory (in my screenshots, sdk\platform-tools), and run:
adb devices
to ensure the device (and only the device) is listed. If it’s not listed, verify that Photo Transfer 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"
}
8. Reboot phone into Fastboot mode
adb reboot bootloader
You should hear the Windows sounds of USB devices going and coming. And the phone has an odd screen.
9. From the same directory (Android tools),
fastboot flash unlock unlock.bin
This takes only a few seconds to run.
10. Reboot with:
fastboot reboot
You will get entirely different start-up screens than normal. Including a warning that your device cannot be checked for corruption. (and a reference to http://g.co/ABH)
Your phone has now been hard reset.
11. Go through the initial phone setup options, to get to Android. Switch USB to Photo Transfer again.
12. You can verify that it’s unlocked either from the Developer Options – OEM Unlock is no longer available because it’s already unlocked, or by:
Installing TWRP:
1. Switch back to developer mode, USB debugging. (OEM Unlock is now not selectable, because it's on permanently.)
2. Switch USB to Photo again; default is charging.
3. As before, on your PC from the Android tools directory,
adb reboot bootloader
4. Fastboot flash recovery twrp-3.1.1-0-h930.img
5. This part is tricky… read the whole thing before starting.
a. Turn OFF the phone, using the volume key to change from Restart at the top to “Power off”.
b. Disconnect the USB cable
c. Holding both the Volume-Down and Power button, turn phone on.
d. As soon as the LG logo appears, continue pressing “Down” but release and re-press Power. Continue holding both until a menu appears.
e. Select to erase all data. You will be asked this several times; keep saying “Yes”.
f. Eventually you will boot into TWRP.6. Back up the system. This isn’t essential, but you’d be silly not to.
a. In TWRP, set system writable
b. Select “back up”. Note there’s no data, because that partition is encrypted.
c. Select the SD card (or USB; I use a micro SD card.)
d. Back it up. This will take around seven minutes.7. Turn off data encryption and install stuff… all in TWRP:
a. Wipe Data – Factory Reset
b. Wipe Data – Format Partition
c. Install – set storage to the External SD
d. Install the Magisk zip
e. Install the no-verity-opt-encrypt-6.0.zip
f. Install the LG-rctd-disabler-1.0.zip; this reduces LG root checks, which may impede performance.
g. Reboot – to SystemIf booting fails with an encryption error, did you format (b above) the partition? If not, reinstall TWRP (except you don't need to backup again) and do both the wipe and format.
You will now have to set up the phone again, but should have root (via Magisk.)
EDIT: This has been added to the steps above.
_______
Good write up, but please add the "don't check root" file. It would go into the section where you flash the no verity file.
LG-rctd-disabler-1.0.zip
https://build.nethunter.com/android-tools/lg-rctd-disabler/
Recently, we discovered a system module on many LG devices which scans for root access. Called*RCTD, the tool is activated whenever an LG phone running stock-based software has been rooted. This has led to device slowdowns (as the process never shuts down) and also has left some users feeling uneasy about it as well.
we can now disable this check with a simple application
Click to expand...
Click to collapse
A lot of people are already using it when flashing TWRP with the phone.
_____
ANOTHER EDIT:
After installing TWRP, it's a good idea to download TWRP Manager from the Play Store.
From that app, you can easily reboot into TWRP without doing the power/volume button dance. In the app's settings, change app start up screen to be reboot options. That way, every time you open the app, that's the immediate option you can choose.
Sent from my official carrier unlocked LG V30+ US998
Now that the US998 is unlocked and rooted. Has anyone tried to get that secret T-Mobile menu working to see if band 71 can be enabled?
ChazzMatt said:
Good write up, but please add the "don't check root" file. It would go into the section where you flash the no verity file.
Click to expand...
Click to collapse
I wasn't even aware of it! Good reason for the write-up.
US998?
Is this safe for US998? Just asking since the TWRP file says it is for H930.
One question. Works on every firmware or only on 10f?
crothlisberger said:
Is this safe for US998? Just asking since the TWRP file says it is for H930.
Click to expand...
Click to collapse
Yes. We're trying to get the V30 TWRP developer @jcadduonoto change the TWRP name and the description, but he's ignoring us right now. It's compatible with US998. Been proven many times.
If the TWRP developer would edit the thread title, op, and even the file properties it would eliminate a lot of confusion. For instance, doesn't need show H930 when plugged into your PC in TWRP mode. I don't have an H930, I have US998. It could easily say "V30" or "JOAN" (the LG code name for this device).
It's just the H930/H930G was placed on LG Developer Bootloader Unlock list back in December. We're playing catch up to them.
Sent from my official carrier unlocked LG V30+ US998
Dizzyrul3z said:
One question. Works on every firmware or only on 10f?
Click to expand...
Click to collapse
Some have problems with any other firmware than 10f on the H930, personally i dont have problems with 10f or 10v, didnt try 11m yet.
Dizzyrul3z said:
One question. Works on every firmware or only on 10f?
Click to expand...
Click to collapse
What's 10f? I have 10c.
This is my rooted US998 with TWRP.
Sent from my official carrier unlocked LG V30+ US998
Thanks
Thanks for gathering all this together. Was able to follow the steps last night and am up and running rooted now.
Additional information - As the guide states, it uses Magisk however SuperSU also works fine for root.
Thanks @Wotta for the write-up.
Disclaimer : And yes...Understand with different root comes advantages / disadvantages.
vinniej said:
Additional information - As the guide states, it uses Magisk however SuperSU also works fine for root.
Thanks @Wotta for the write-up.
Disclaimer : And yes...Understand with different root comes advantages / disadvantages.
Click to expand...
Click to collapse
That is good to know for anyone who doesn't like to use the one from the person who stole code from Chainfires hard work.
Do Wifi calling and HD voice and video work with the rooted US998? I have had the VS996 since late October and although I love the phone, I really miss having a rooted device (mostly for nandroid backups, but also for ad blocking).
Does this work for the V300L?
jake2447 said:
Thanks for gathering all this together. Was able to follow the steps last night and am up and running rooted now.
Click to expand...
Click to collapse
You're welcome. I'm glad it was clear.
BobberK said:
Does this work for the V300L?
Click to expand...
Click to collapse
Read paragraph #2 of the op:
Wotta said:
This also assumes you have already filled out the LG form and received the unlock.bin file. If not, retrieve it from LG using the tricks in this thread.
Click to expand...
Click to collapse
Are you able to get bootloader unlock.bin from the LG Developer Bootloader Unlock list website?
It's only for V30/V30+ that are eligible to do that.
I'm not being smart aleck. The US998 V30 is not officially listed as eligible (yet). But someone found a way to hack the dropdown list and still get US998 V30 unlock.bin. It works if you follow the right steps. The US998 V30+ SHOULD also work, but does not (yet).
So, the answer for you is probably no. But you'll have to try to get bootloader unlock.bin from the LG Developer Bootloader Unlock list website to know for sure.
Sent from my official carrier unlocked LG V30+ US998
This will not work on T-Mobile version right?
nofroyo said:
This will not work on T-Mobile version right?
Click to expand...
Click to collapse
See the answer immediately above your question. You need bootloader unlock.bin from LG.
Sent from my official open market LG US998 V30+
Will it work on Indian dual sim model i.e. H930DS. ?
Can't access TWRP
Hi guys,
I'm having a problem entering TWRP.
I unlocked my bootloader and "successfully" installed TWRP. But I can't get past step 5 (the tricky part). So after flashing TWRP I disconnect the phone from the PC and switch it off. Then as described in step 5 I access the part where I'm supposed to do the factory data reset. But once I hit yes for the second time the black-orange warning screen pops up immediately and after a few seconds the phone reboots to the normal software which is NOT completely reset.
So I just can't access the custom recovery TWRP no matter what I do or how often I try...
I would be very grateful for any help
Is there any way to bypass Xiaomi's account system and wait time? It isn't only the pain in the ass, but I would trust an XDA developer a lot more than a Chinese corporation like Xiaomi with any possible privacy issues related to their bootloader unlock process.
I've seen a thread for the Mi 4c which seems to be similar to what I'm looking for.
https://forum.xda-developers.com/mi-4c/general/guide-unlocking-mi4c-bl-verification-t3336779
Has anything similar been done for the Mi 8 Lite?
Thanks!
No
Good luck. Just be patient and read all you can about Mi8 Lite while waiting. That is what I did. Made the time pass more quickly. NOTE: Do not change sim cards mid-way through. It will reset your 15 days. Almost got burned by doing that myself.
I had the same issue. Try to use Miflash unlock version 2.3.803.10. MAYBE it can work.
u need to wait, no other way
MiFlash Unlock Tool Version 3.3.827.31
Have your SIM in phone.
Login to your MI account on the phone and on PC.
Set your SIM phone number in MI account settings (PC).
Find Mi Unlock Status item in Developer settings in phone settings and
Add account and Device
Turn off phone. Connect it to PC. Start MiFlash Unlock.
When it asks for phone, boot it in Fastboot (hold vol+ and power button)
Proceed...
On my friends Redmi 4x it showed 72 hrs to unlock.
On a fresh Mi account...
dakok said:
MiFlash Unlock Tool Version 3.3.827.31
Have your SIM in phone.
Login to your MI account on the phone and on PC.
Set your SIM phone number in MI account settings (PC).
Find Mi Unlock Status item in Developer settings in phone settings and
Add account and Device
Turn off phone. Connect it to PC. Start MiFlash Unlock.
When it asks for phone, boot it in Fastboot (hold vol+ and power button)
Proceed...
On my friends Redmi 4x it showed 72 hrs to unlock.
On a fresh Mi account...
Click to expand...
Click to collapse
My 3 redmi note 4x's were unlocked same day. Newer devices have the longer wait time. So far nothing you can do but wait.
The solution is in files
I know how to flash without Unlock Bootloader.
kevinramir said:
I know how to flash without Unlock Bootloader.
Click to expand...
Click to collapse
Well good for you and so do I. It is very limited what you can do though.
The solution is in files
No, is just modify files
cidxtc said:
Well good for you and so do I. It is very limited what you can do though.
Click to expand...
Click to collapse
I've tried some versions of this program, but none worked, and I've seen and heard reports that the miunlock program does not really work properly. So I gave up unlocking and I want to undo it.
Please give me a name of a good device so that I can change it on my MI8 Lite? preference Motorola and Samsung.
kevinramir said:
I know how to flash without Unlock Bootloader.
Click to expand...
Click to collapse
Can you please help me with this? Do you have any guide or advice for this?
matheusfdelgado said:
I had the same issue. Try to use Miflash unlock version 2.3.803.10. MAYBE it can work.
Click to expand...
Click to collapse
HOLY **** THIS VERSION ACTUALLY WORKED FOR ME
Thank you so! much dude!!!
Marlonese said:
HOLY **** THIS VERSION ACTUALLY WORKED FOR ME
Thank you so! much dude!!!
Click to expand...
Click to collapse
{
"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"
}
Not working anymore
Got mine to work with the newest version now too, tho
Still sad that Xiaomi tries to make it so hard to unlock bootloader
I've just done unoff unlocking process without paying. If it is interesting, i can describe.
And for Mi8 also, but it need to edl-autorization flash (some money).
domestik said:
I've just done unoff unlocking process without paying. If it is interesting, i can describe.
And for Mi8 also, but it need to edl-autorization flash (some money).
Click to expand...
Click to collapse
? You don't have to pay to unlock your bootloader officially?
MartonDev said:
? You don't have to pay to unlock your bootloader officially?
Click to expand...
Click to collapse
unofficial unlock
So here is instruction to get unofficial unlocked Mi8 Lite device ("platina").
Must say "bla-bla" about risk of damaging. My phone was "baseband unknown" problem, so no way to unlock officially.
You must have some skills.
All you need files except FW's are in attachment.
1. I have MI8Lite CN version 9.6.6.0. I dont know how about other versions.
2. Remove back cover and antenna cover to reach TP.
3. Extract attach, run miflash, select extracted directory, connect phone in 9008 mode and flash.
In \images only few files and corrected loader, so you dont need auth-account to flash.
4. At end of flashing (not during process!!!!) I got an error. It is normal.
5. Reconnect battery, press Vol-down, connect to PC. You must have fastboot mode and NO info on screen (it is normal, bcz your phone now "wayne" not "platina").
6. Run mi_unlock_en_sod, press left key in it then press right key. You must see green text in this program and your phone reboots. Still garbage on screen! But now unlocked!
7. Go to FW-directory of your phone (same as in your phone), edit flash_all.bat. Remove First and second line (checking phone model), save file.
8. Execute command "fastboot flash antirbpass dummy.img". Result must be OK.
9. Run flash_all.bat.
10. That's all. Your phone must turns on, unlocked and "platina".
11. Corrected firehose loader from \images can be used to flash any MI8Lite FW without edl auth.
On Mi8 process much easy but expensive. You need to flash 9.5.11.0 version via edl auth, run mi_unlock_en_sod, press left, press right. I have been done huge amount.
On Redmi Note 7 process must be same as on Mi8Lite bcz it is one phone in two different cases.
https://yadi.sk/d/SF1Uh7D7yrYqnQ
domestik said:
So here is instruction to get unofficial unlocked Mi8 Lite device ("platina").
Must say "bla-bla" about risk of damaging. My phone was "baseband unknown" problem, so no way to unlock officially.
You must have some skills.
All you need files except FW's are in attachment.
1. I have MI8Lite CN version 9.6.6.0. I dont know how about other versions.
2. Remove back cover and antenna cover to reach TP.
3. Extract attach, run miflash, select extracted directory, connect phone in 9008 mode and flash.
In \images only few files and corrected loader, so you dont need auth-account to flash.
4. At end of flashing (not during process!!!!) I got an error. It is normal.
5. Reconnect battery, press Vol-down, connect to PC. You must have fastboot mode and NO info on screen (it is normal, bcz your phone now "wayne" not "platina").
6. Run mi_unlock_en_sod, press left key in it then press right key. You must see green text in this program and your phone reboots. Still garbage on screen! But now unlocked!
7. Go to FW-directory of your phone (same as in your phone), edit flash_all.bat. Remove First and second line (checking phone model), save file.
8. Execute command "fastboot flash antirbpass dummy.img". Result must be OK.
9. Run flash_all.bat.
10. That's all. Your phone must turns on, unlocked and "platina".
11. Corrected firehose loader from \images can be used to flash any MI8Lite FW without edl auth.
On Mi8 process much easy but expensive. You need to flash 9.5.11.0 version via edl auth, run mi_unlock_en_sod, press left, press right. I have been done huge amount.
On Redmi Note 7 process must be same as on Mi8Lite bcz it is one phone in two different cases.
]
I have a Redmi Note 7. I have "NV data is corrupted" on my device and locked bootloader. Need to unlock it in order to replace the QCN file and fix baseband, IMEI, modems, etc. Can you explain to me how did you unlock your bootloader? Pls
Click to expand...
Click to collapse
Disclaimer: I hope you don't break your phone, but if you do, it's not my fault. Since you are choosing to modify your phone, you accept full responsibility for whatever happens to it, including any damage that may have occurred as a result of incorrectly flashing your device.
Hey guys, similar to all of @Some_Random_Username's unbrick threads, here are the EDL packages (also known as MSM tools or unbrick tools) that can revive a bricked OnePlus Nord N200 5G.
Important: This is only for the T-Mobile variant of the N200. This will not work on the factory unlocked variant and may or may not work for the Metro variant.
Downloads:
11.0.1.5.DE18CB
Original archive
Google Drive
7z format (thanks @edale1)
AnddoidFileHost
MEGA
zip format (thanks @nv270)
Rethink Files
Also available at https://onepluscommunityserver.com/
Instructions:
Launch MsmDownloadTool V4.0.exe.
On the login prompt select "Others" in the dropdown menu and click on Next.
Wait a few seconds until main window shows up.
Press Start button so that it waits for your device to be connected
Power off your device
Press and hold the volume up and down buttons to get into Qualcomm EDL mode.
Plug your device to your computer.
Should you not manage to do that and have adb access, you can use adb reboot edl instead
Wait ~300 seconds.
Enjoy your brand new device.
FAQ:
Does this work on Mac or on Linux?
Unfortunately no, tool is Windows only. You should need at least Windows 7.
Why is my antivirus freaking out when unzipping the archive or running the tool?
In an effort to protect reverse engineering from being done (and by extension prevent conversion process like it was done on 6T and 7Pro), OnePlus now use VM Protect V3 in their MSM tools. As this tries to detect debug environment, this is seen as malicious behaviour by some antivirus.
How can I check my device project ID?
Use getprop ro.boot.project_name. This however involve having ADB access or access to OxygenOS to use Termux or whatever terminal emulator you prefer.
My device isn't detected
Go to device manager and make sure your phone shows up as QDLOADER 9008.
If it shows up as QHUSB_BULK, it means Qualcomm driver wasn't installed automatically by Windows Update. Download the latest one from Microsoft website at http://download.windowsupdate.com/c..._fba473728483260906ba044af3c063e309e6259d.cab (source https://www.catalog.update.microsof...updateid=8ee52ba0-bdef-4009-88cf-335a678dd67a ) and install it manually by right clicking on QHUSB_BULK and selecting "Update driver software" and "Browse my computer for driver software" to where you downloaded CAB file.
If you can't get into EDL mode by hardware keys, you may use adb reboot edl (will require your phone to still have ADB access)
MSM tool is stuck on "Param pre-processing"
Ensure you're using the Qualcomm drivers linked above.
MSM tool is stuck on "Sahara communication failed"
Unplug your phone, get in fastboot mode, turn off phone, wait 15 secondes and get back in Qualcomm EDL mode. You can also try using a USB 2.0 port instead of a 3.0 one.
What is SMT Download mode?
Just don't try to unlock that mode, it will wipe your IMEI and your Widevine certificate if you use it.
How can I fix "SMT config not found" error?
Please refer to https://forum.xda-developers.com/showpost.php?p=83448961&postcount=61
Credits:
@Some_Random_Username for help getting files and for the mirror
@edale1 and @nv270 for repacking and mirroring the files
@nache2001 for testing the tool out on his device
OnePlus for the device and OS
@Nache and others who have the unlocked version from the oneplus store and have the bootloader locked and phone bricked .. This version will not work with your phone as i just tried it myself today .. hopefully someone gets a hold of the msmdowmload from the tech support ..
patiently waiting for the unlock
So just to confirm: For those of us with Tmobile version, this will install default rom from OnePlus and get rid of all the bloatware from Tmobile and technically make our devices be like they are originally purchased from OP?
And of course, in order to use this our bootloader needs to be unlocked?
Will this lock bootloader again?
And do we unlock it with same code we got from OP first time?
Thanks!
xentonix said:
So just to confirm: For those of us with Tmobile version, this will install default rom from OnePlus and get rid of all the bloatware from Tmobile and technically make our devices be like they are originally purchased from OP?
And of course, in order to use this our bootloader needs to be unlocked?
Will this lock bootloader again?
And do we unlock it with same code we got from OP first time?
Thanks!
Click to expand...
Click to collapse
My understanding is the T-Mobile MSM Tools will restore a T-Mobile variant phone to the state it was in coming from T-Mobile; meaning if you debloated the phone, the bloat will be back.
You can use the MSM Tools even with a locked bootloader.
If your bootloader is unlocked, I believe this will lock it. (it may SIM lock your phone again as well, unsure...)
I think the same unlock token will work, but I'm hesitant to say 'yes' without someone testing it first.
xentonix said:
So just to confirm: For those of us with Tmobile version, this will install default rom from OnePlus and get rid of all the bloatware from Tmobile and technically make our devices be like they are originally purchased from OP?
And of course, in order to use this our bootloader needs to be unlocked?
Will this lock bootloader again?
And do we unlock it with same code we got from OP first time?
Thanks!
Click to expand...
Click to collapse
1. Nope, this will revert your device back to the T-Mobile stock ROM, including all the bloatware. Thsi does not convert your device into an unlocked variant.
2. This works whether your bootloader is locked or unlocked. If your bootloader is unlocked, using this tool will lock it again, and you will need to unlock it by flashing unlock_code.bin again.
edale1 said:
My understanding is the T-Mobile MSM Tools will restore a T-Mobile variant phone to the state it was in coming from T-Mobile; meaning if you debloated the phone, the bloat will be back.
You can use the MSM Tools even with a locked bootloader.
If your bootloader is unlocked, I believe this will lock it. (it may SIM lock your phone again as well, unsure...)
I think the same unlock token will work, but I'm hesitant to say 'yes' without someone testing it first.
Click to expand...
Click to collapse
lzgmc said:
1. Nope, this will revert your device back to the T-Mobile stock ROM, including all the bloatware. Thsi does not convert your device into an unlocked variant.
2. This works whether your bootloader is locked or unlocked. If your bootloader is unlocked, using this tool will lock it again, and you will need to unlock it by flashing unlock_code.bin again.
Click to expand...
Click to collapse
Thank you!
I read an article that was bit unclear and pointed to this so I wanted to confirm.
Also, from everything else I gathered, there is still no way to flash Tmob variant with non Tmob rom?
I was interested to try LineageOS but that's not available also seems like.
Phone's too new still. I think we need the MSM Tools for all the variants available before someone can figure out how to flash one variant into another, and we currently only have the T-Mobile variant's MSM Tools.
{
"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"
}
incoming August 176 patch
I have update installed.
You can use restore image on Magisk uninstall before you start. If you encounter problem, you can use original boot image and run "mock patch"
Install update and switch to Magisk when you're prompted to restart, and let Magisk to install in unused partition, and restart after finished
If you have problem with CTS after update, install riru from Magisk and download safetynet fix, and install in Magisk as well (you have to reboot twice)
I've successful restored my N200 phone several times using the MSM, but this most recent time it appears the process was interrupted and I get the following error when turning on the phone. I can not boot the phone back into EDL mode to run MSM tool again. Every 10 or so boots the phone will boot into fastboot instead of throwing the error. I tried flashing a backed up boot.img and super.img, but no luck getting past the error. Any way to recover?
automatic ddr failed
Thank you! I could only get this to work by:
Unplug phone
Open MSMDownloadTool, don't click start
Hold down volume up and down
Plug phone into USB 2.0 port
Release volume up and down, verify device shows up as QDLOADER in Device Manager
Click "Enum" in MSMDownloadTool
Click on the device in the list and click "Start"
I got bootloader unlock code. I need SIM unlock "One Plus Nord N200 5G" by Metro. Help me!
towardsdawn said:
Thank you! I could only get this to work by:
Unplug phone
Open MSMDownloadTool, don't click start
Hold down volume up and down
Plug phone into USB 2.0 port
Release volume up and down, verify device shows up as QDLOADER in Device Manager
Click "Enum" in MSMDownloadTool
Click on the device in the list and click "Start"
Click to expand...
Click to collapse
I bricked my phone late last night and found this forum & thread; my problem was that each time my computer kept showing my phone as "Kedacom" until I scrolled through and found this post.
You guys saved my ass AND saved me a trip to T-Mobile too! I owe you guys big time!
I successfully flashed a metro-pcs device using the tool in this thread. I bricked my device using the dsu loader in developer options. "Oem unlocking" is greyed out. Can anyone point me to a good bootloader unlocking tutorial for this devicel? Is it possible to use this tool with a rom that has already been rooted? Thanks,
Noob here. One thing to note: device was not recognized in the beginning. I held vol up/down at the same time and then plugged in device. Although the screen was black, the device was shown as "connected" and had no issues flashing. After 300 secs, voila!
bleezycheesy said:
I successfully flashed a metro-pcs device using the tool in this thread. I bricked my device using the dsu loader in developer options. "Oem unlocking" is greyed out. Can anyone point me to a good bootloader unlocking tutorial for this devicel? Is it possible to use this tool with a rom that has already been rooted? Thanks,
Noob here. One thing to note: device was not recognized in the beginning. I held vol up/down at the same time and then plugged in device. Although the screen was black, the device was shown as "connected" and had no issues flashing. After 300 secs, voila!
Click to expand...
Click to collapse
You can try this tutorial. It worked for me on Tmobile, no idea about MetroPCS. Key line is
Code:
adb shell pm uninstall --user 0 com.qualcomm.qti.uim
MSMDownloadTool wipes the entire device and relocks the bootloader if it was unlocked, it doesn't care if you're rooted.
towardsdawn said:
You can try this tutorial. It worked for me on Tmobile, no idea about MetroPCS. Key line is
Code:
adb shell pm uninstall --user 0 com.qualcomm.qti.uim
MSMDownloadTool wipes the entire device and relocks the bootloader if it was unlocked, it doesn't care if you're rooted.
Click to expand...
Click to collapse
Thanks for the reference. It worked!
why no have msm tool for global n200 be2117,
jasmok said:
why no have msm tool for global n200 be2117,
Click to expand...
Click to collapse
OnePlus doesn't seem to want to release it.
bleezycheesy said:
Thanks for the reference. It worked!
Click to expand...
Click to collapse
no it doesn't works on metro variant
Hello everyone!
I recently had the pleasure(pain) of flashing my Ace Pro and I wanted to share the steps I took in doing so. This post will act a as guide/discussion area regarding flashing the Ace Pro(Chinese Release) into the OnePlus 10T 5G(Global Release).
Henceforth, I will refer to the OnePlus Ace Pro as Ace Pro, and the OnePlus 10T 5G as 10T.
A little bit of backstory:
I currently live in China and have no way of purchasing a device overseas and having it shipped in. Instead, I did a little bit of research and decided to purchase an Ace Pro and have a go at flashing it myself. As far as I can tell, the Ace Pro and 10T are identical hardware-wise and flashing between the 2 different market varients can be done with a little bit of effort and headache.
Before we go any further, let me link some useful articles and resources I've found along the way in order to successfully flash your own Ace Pro:
Fastboot Enhance, a powerful tool that will allow you to flash your device with your desired OS
ADB Platform Tools, a tool used to unlock your bootloader
OnePlus USB Drivers, an USB driver used to allow for your phone to communicate with your computer seamlessly(Even though not officially supported, the Ace Pro and 10T work with the 1.0 Release of the USB Drivers)
2415_11_C.22 Update, a stable release of Oxygen 13 that I personally recommend to be flashed on your 10T
Daxiaamu Tools and ROMs, a Chinese enthusiast that has developed his own tools to aid in unlocking, flashing and relocking of devices.
Disclaimer: I am not responsible for any damage that you may inflict upon your own device, proceed with caution and at your own risk! Back up all data before proceeding!!
We begin our journey by first unlocking the Ace Pro's bootloader, unlocking the bootloader is an essential step in flashing your device.
To do this, we need to first enable Developer Tools by going into: Settings > About Device > Version > And tapping the Build Number box until you have become a developer.
After this, navigate to Developer Options. If you cannot find this option, I recommend using the search bar at the top of the settings menu to find this option. Once you're in this menu, enable OEM Unlocking and USB Debugging. This allows for our computer to communicate with our Ace Pro.
Here I recommend installing your Oneplus USB Driver. This will allow your phone to communicate with your PC for the upcoming step.
After installing the drivers, plug your phone into your computer using either the USB cable that came in the box, or a reliable cable that you know will carry data.
Press on Transfer Files/Android Auto when prompted.
Allow for debugging on your device after plugging it into your computer with the prompt that shows up.
Once you are sure that both OEM Unlocking and USB debugging have been enabled, run your ADB Platform Tools by performing the following steps:
Unzip your ADB Platform Tools and have it placed in a memorable place(preferably the desktop)
{
"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"
}
Holding Shift + Right Click in an empty space brings up this option menu. Click on Open PowerShell window here.
This brings up a Windows Powershell terminal that allows you to enter commands that will directly affect your Ace Pro.
Run the command
Code:
adb devices
This show bring up an entry with a mess of both numbers and characters. This shows you that both your computer and ADB tool recognizes your device and you can move forward.
Now we want to put the device into the bootloader by using:
Code:
adb reboot booloader
This will now run on your device putting it into the bootloader state.
Note: DO NOT UNPLUG YOUR DEVICE IN THIS STATE
After making sure that your device is in the bootloader, run the command:
Code:
fastboot flashing unlock
You will be presented with a prompt asking you if you are sure that you want to unlock your bootloader. Using the volume rocker as a selector and the power button as a confirmation button, highlight the UNLOCK THE BOOTLOADER option using the volume rocker and confirm it by pressing the power button.
Your Ace Pro's bootloader is now unlocked.
NOTE: YOUR DEVICE WILL BE FORMATTED ONCE YOU UNLOCK THE BOOTLOADER! ALL EXISTING DATA WILL BE LOST!
Once unlocking your bootloader, your phone will enter 'Orange State' where it lets you know that your device is untrusted due to its unlocked nature. Do not be alarmed by this.
Proceed by setting your phone up as normal and repeat the earlier step where you become a developer and enable USB Debugging.
This time, OEM unlocking will be enabled by default, this is due to the nature of your device being unlocked.
We now want to put our device into fastboot mode by using ADB. In the Powershell window, type:
Code:
adb reboot fastboot
This will once again change the state of your phone and put it in fastboot mode where 3 language options are available. Do not configure your phone in this state, we will come back to it later.
Now, run Fastboot Enhance as an administrator on your PC. The window should open up and you should be able to see your device with the device name being labeled as 'fastboot'.
Double click this option and another Window should show up.
Make sure that the status of the device is as follows:
Secure Boot: Disabled
Seamless Update: Yes
Current Slot: a
In Fastbootd: Yes
System Update Status: None
Once in this state, we want to click on the partitions tab above and search for 'cow' in the search bar. Results will pop up if you have used/updated your device in ColorOS. You want to highlight these results and press delete on the right hand side. Having them remain in your device will have the possibility of bricking your device when flashing the new OxygenOS ROM.
Once done deleting, return to the Basic Properties tab and press Flash Payload.bin. This will open a browser in where you need to find the zip file containing the ROM that you want to flash.
Find your payload.bin file and open.
Your device will now begin to flash, it took me around 10 minutes before the device was done flashing.
Once flashed, go to your phone and select your language of choice. For most of us, it will be English. This option can be selected like earlier, using the volume rocker as a selector and the power button as a confirmation switch.
Select the option to format your phone once again. Enter the pass code that is present on the screen and confirm the formatting procedure.
The device should still be in Orange State since we have not relocked our bootloader, instead we will now see the OxygenOS boot animation before proceeding to set up our device.
From this point onward, your device is now flashed with OxygenOS.
If you would like to relock your bootloader, read on.
The benefits of relocking your bootloader is that you will be able to receive OxygenOS updates as normal and be able to use NFC functions such as Google Wallet.
Once again, enable developer options and make sure that both OEM Unlocking and USB Debugging is enabled.
Open the ADB Powershell window mentioned before and make sure that your device is still recognized by using the command:
Code:
adb devices
Once your device shows up, put it back into the bootloader state by using the command:
Code:
adb reboot bootloader
Your phone will now enter the bootloader state once again.
We can now relock our bootloader by using the command:
Code:
fastboot flashing lock
This will prompt you to use your volume rocker and power button one more time. Select the option LOCK THE BOOTLOADER and press the power button to confirm. Your device will now format for the last time and load you into OxygenOS 13.
Note: I personally had an issue where after flashing and relocking the bootloader, my phone decided to bootloop(device stuck at OnePlus logo and keeps on turning on and off again), I solved this by holding the volume down and power button and setting it to restart. After loading into the operating system, I updated my device by using OTA updates and installing C4515_11_C.23. This allowed for my device to install the latest update and it seemed to have fixed the bootlooping problem for me.
Another method to fix the bootlooping issue after flashing your phone if you already have the latest update installed is to enable developer options after flashing and applying the same update using the local update feature.
To do this, enable developer options first, the instructions to do that were described earlier in this guide. Transfer the .bin file by drag and dropping your .bin file to a location on the device that you are familiar with. (Placing the .bin file in the downloads folder is a foolproof method)
From there onwards, you want to go into Settings > About Device > Tap on the blue OxygenOS banner > 3 dots menu in the top right corner > Local Install > Select your .bin file you used to flash the device with earlier. Your device should then update with said .bin file and the bootlooping issue should be solved.
Credit to thegreatn_ for this discovery.
Edit: Some of you may experience that your OEM unlocking is still enabled even after flashing your device and relocking your booloader. Remember earlier when your bootloader was in an unlocked state, the OEM unlocking option would be on by default and greyed out so that you could not turn it off which may present a security risk.
Rest assured that you can turn off OEM unlocking once your device has been relocked and everything will function as intended. YOUR DEVICE SHOULD NOT BE ROOTED IF YOU INTEND TO TURN THIS OFF! ONLY DO THIS WITH THE OFFICIAL FIRMWARE INSTALLED! Not having the official firmware installed and turning off OEM unlocking can brick your device!
Credit to Adly1991 for this information.
Please let me know if there's any questions you'd like to ask. This is my first time flashing and it may seem daunting at first, but I believe with a little bit of confidence, you too will be able to successfully flash your Ace Pro.
Good luck!
I'm 8T user , but thanks for sharing your experience and the information.
Abdo Ismail said:
I'm 8T user , but thanks for sharing your experience and the information.
Click to expand...
Click to collapse
It was really hard for me to find a place where I could get all the information I needed about flashing my phone as a noob. If this post helps even just a single person I'd be over the moon. Thanks for the feedback!
Thanks so much. Followed the instructions and worked perfectly!
breadsnack said:
Hello everyone!
I recently had the pleasure(pain) of flashing my Ace Pro and I wanted to share the steps I took in doing so. This post will act a as guide/discussion area regarding flashing the Ace Pro(Chinese Release) into the OnePlus 10T 5G(Global Release).
Henceforth, I will refer to the OnePlus Ace Pro as Ace Pro, and the OnePlus 10T 5G as 10T.
A little bit of backstory:
I currently live in China and have no way of purchasing a device overseas and having it shipped in. Instead, I did a little bit of research and decided to purchase an Ace Pro and have a go at flashing it myself. As far as I can tell, the Ace Pro and 10T are identical hardware-wise and flashing between the 2 different market varients can be done with a little bit of effort and headache.
Before we go any further, let me link some useful articles and resources I've found along the way in order to successfully flash your own Ace Pro:
Fastboot Enhance, a powerful tool that will allow you to flash your device with your desired OS
ADB Platform Tools, a tool used to unlock your bootloader
OnePlus USB Drivers, an USB driver used to allow for your phone to communicate with your computer seamlessly(Even though not officially supported, the Ace Pro and 10T work with the 1.0 Release of the USB Drivers)
2415_11_C.22 Update, a stable release of Oxygen 13 that I personally recommend to be flashed on your 10T
Daxiaamu Tools and ROMs, a Chinese enthusiast that has developed his own tools to aid in unlocking, flashing and relocking of devices.
Disclaimer: I am not responsible for any damage that you may inflict upon your own device, proceed with caution and at your own risk! Back up all data before proceeding!!
We begin our journey by first unlocking the Ace Pro's bootloader, unlocking the bootloader is an essential step in flashing your device.
To do this, we need to first enable Developer Tools by going into: Settings > About Device > Version > And tapping the Build Number box until you have become a developer.
After this, navigate to Developer Options. If you cannot find this option, I recommend using the search bar at the top of the settings menu to find this option. Once you're in this menu, enable OEM Unlocking and USB Debugging. This allows for our computer to communicate with our Ace Pro.
Here I recommend installing your Oneplus USB Driver. This will allow your phone to communicate with your PC for the upcoming step.
After installing the drivers, plug your phone into your computer using either the USB cable that came in the box, or a reliable cable that you know will carry data.
Press on Transfer Files/Android Auto when prompted.
Allow for debugging on your device after plugging it into your computer with the prompt that shows up.
Once you are sure that both OEM Unlocking and USB debugging have been enabled, run your ADB Platform Tools by performing the following steps:
Unzip your ADB Platform Tools and have it placed in a memorable place(preferably the desktop)
View attachment 5844957
Holding Shift + Right Click in an empty space brings up this option menu. Click on Open PowerShell window here.
This brings up a Windows Powershell terminal that allows you to enter commands that will directly affect your Ace Pro.
Run the command
Code:
adb devices
This show bring up an entry with a mess of both numbers and characters. This shows you that both your computer and ADB tool recognizes your device and you can move forward.
Now we want to put the device into the bootloader by using:
Code:
adb reboot booloader
This will now run on your device putting it into the bootloader state.
Note: DO NOT UNPLUG YOUR DEVICE IN THIS STATE
After making sure that your device is in the bootloader, run the command:
Code:
fastboot flashing unlock
You will be presented with a prompt asking you if you are sure that you want to unlock your bootloader. Using the volume rocker as a selector and the power button as a confirmation button, highlight the UNLOCK THE BOOTLOADER option using the volume rocker and confirm it by pressing the power button.
Your Ace Pro's bootloader is now unlocked.
NOTE: YOUR DEVICE WILL BE FORMATTED ONCE YOU UNLOCK THE BOOTLOADER! ALL EXISTING DATA WILL BE LOST!
Once unlocking your bootloader, your phone will enter 'Orange State' where it lets you know that your device is untrusted due to its unlocked nature. Do not be alarmed by this.
Proceed by setting your phone up as normal and repeat the earlier step where you become a developer and enable USB Debugging.
This time, OEM unlocking will be enabled by default, this is due to the nature of your device being unlocked.
We now want to put our device into fastboot mode by using ADB. In the Powershell window, type:
Code:
adb reboot fastboot
This will once again change the state of your phone and put it in fastboot mode where 3 language options are available. Do not configure your phone in this state, we will come back to it later.
Now, run Fastboot Enhance as an administrator on your PC. The window should open up and you should be able to see your device with the device name being labeled as 'fastboot'.
Double click this option and another Window should show up.
Make sure that the status of the device is as follows:
Secure Boot: Disabled
Seamless Update: Yes
Current Slot: a
In Fastbootd: Yes
System Update Status: None
Once in this state, we want to click on the partitions tab above and search for 'cow' in the search bar. Results will pop up if you have used/updated your device in ColorOS. You want to highlight these results and press delete on the right hand side. Having them remain in your device will have the possibility of bricking your device when flashing the new OxygenOS ROM.
Once done deleting, return to the Basic Properties tab and press Flash Payload.bin. This will open a browser in where you need to find the zip file containing the ROM that you want to flash.
Find your payload.bin file and open.
Your device will now begin to flash, it took me around 10 minutes before the device was done flashing.
Once flashed, go to your phone and select your language of choice. For most of us, it will be English. This option can be selected like earlier, using the volume rocker as a selector and the power button as a confirmation switch.
Select the option to format your phone once again. Enter the pass code that is present on the screen and confirm the formatting procedure.
The device should still be in Orange State since we have not relocked our bootloader, instead we will now see the OxygenOS boot animation before proceeding to set up our device.
From this point onward, your device is now flashed with OxygenOS.
If you would like to relock your bootloader, read on.
The benefits of relocking your bootloader is that you will be able to receive OxygenOS updates as normal and be able to use NFC functions such as Google Wallet.
مرة أخرى ، قم بتمكين خيارات المطور وتأكد من تمكين كل من إلغاء تأمين OEM وتصحيح أخطاء USB.
افتح نافذة ADB Powershell المذكورة من قبل وتأكد من أنه لا يزال يتم التعرف على جهازك باستخدام الأمر:
Code:
أجهزة adb [/ CODE]
بمجرد ظهور جهازك ، أعده إلى حالة أداة تحميل التشغيل باستخدام الأمر:
[كود] adb reboot bootloader [/ CODE]
سيدخل هاتفك الآن في حالة أداة تحميل التشغيل مرة أخرى.
يمكننا الآن إعادة توصيل محمل الإقلاع الخاص بنا باستخدام الأمر:
[كود] قفل وميض fastboot [/ CODE]
سيطالبك هذا باستخدام زر التحكم في الصوت وزر الطاقة مرة أخرى. حدد الخيار LOCK THE BOOTLOADER واضغط على زر الطاقة للتأكيد. سيتم الآن تنسيق جهازك لآخر مرة وتحميلك إلى OxygenOS 13.
ملاحظة: لقد واجهت شخصيًا مشكلة حيث بعد وميض أداة تحميل التشغيل ، قرر هاتفي تشغيل bootloop (الجهاز عالق على شعار OnePlus ويستمر في التشغيل وإيقاف التشغيل مرة أخرى) ، لقد قمت بحل هذه المشكلة عن طريق الضغط على زر خفض الصوت وزر الطاقة وتعيينه لإعادة التشغيل. بعد التحميل في نظام التشغيل ، قمت بتحديث جهازي باستخدام تحديثات OTA وتثبيت C4515_11_C.23. سمح ذلك لجهازي بتثبيت آخر تحديث ويبدو أنه قد أصلح مشكلة bootlooping بالنسبة لي.
يُرجى إعلامي إذا كان هناك أي أسئلة تود طرحها. هذه هي المرة الأولى التي تومض فيها وقد يبدو الأمر شاقًا في البداية ، لكنني أعتقد بقليل من الثقة ، أنك أيضًا ستكون قادرًا على وميض Ace Pro بنجاح.
حظ سعيد!
[/QUOTE]
أ Do you provide phone costum recovery Oneplus 10T
Click to expand...
Click to collapse
Hello, Im facing this issue when tried to unlock.
The code fastboot flashing unlock not be proceeded but show the whole line with options as below image.
Could you please help !!1
thk202 said:
Hello, Im facing this issue when tried to unlock.
The code fastboot flashing unlock not be proceeded but show the whole line with options as below image.
Could you please help !!1
View attachment 5856125
Click to expand...
Click to collapse
Hey there, I'm not 100% sure on how to solve this issue but I'll try my best.
First of all, please ensure that your phone is plugged into your computer at all times.
Make sure that your cable supports data transfer and try other cables and see if this problem persists.
The fact that ADB is recognizing your device tells me that your cable is probably not to blame.
Make sure that your phone is on beforehand and that USB debugging and OEM Unlocking are both enabled in the developer settings.
You have to also make sure to select allow on your phone when it asks whether the connected computer is allowed to debug your phone. This is important since it allows your computer to run commands on your phone itself.
Does your phone go into the fastboot screen when you run the adb reboot bootloader command?
Let me know so I can narrow your problems down further and solve the issue!
@thk202 I'm not a vendor of any type. This was just my personal experiences. Can you describe what's gone wrong?
thank you, i finally did it following your steps .. and i think recommendation of 2415 version solved my problem and also instantly got C.26 update through OTA
since i tried 2413 before and alwayes got modem issue.
Adly1991 said:
thank you, i finally did it following your steps .. and i think recommendation of 2415 version solved my problem and also instantly got C.26 update through OTA
since i tried 2413 before and alwayes got modem issue.
Click to expand...
Click to collapse
I remember reading somewhere that 2413 gets updates quicker than 2415 for some reason. But I for one was used to the slow update schedule from Samsung for years so it never affected me. 2415 C22 was a stable OxygenOS 13 release that allowed for OTA to C26 to fix any sort booting issues after relocking your bootloader. I remember relocking my bootloader and having it go into a constant bootloop/soft brick after the C22 flash but after OTA to C26, the bootlooping fixed itself and everything was stable again.
breadsnack said:
I remember reading somewhere that 2413 gets updates quicker than 2415 for some reason. But I for one was used to the slow update schedule from Samsung for years so it never affected me. 2415 C22 was a stable OxygenOS 13 release that allowed for OTA to C26 to fix any sort booting issues after relocking your bootloader. I remember relocking my bootloader and having it go into a constant bootloop/soft brick after the C22 flash but after OTA to C26, the bootlooping fixed itself and everything was stable again.
Click to expand...
Click to collapse
shall i disable OEM option in developer option after relock .. already locked the device but i am afraid to disable OEM option since a read somewhere that it bricked someone device ..
Adly1991 said:
shall i disable OEM option in developer option after relock .. already locked the device but i am afraid to disable OEM option since a read somewhere that it bricked someone device ..
Click to expand...
Click to collapse
Erm I've actually got no clue, I know for a fact that if your bootloader is unlocked, OEM unlocking is on by default and greyed out so you cannot turn it off while the bootloader is in it's unlocked state. I did re-enable developer options after locking my phone again and OEM unlocking was turned off by default. This hasn't bricked my phone and I'm assuming that if it had the potential chance to, OnePlus would have greyed it out. See below:
How I fixed my "bootloop" problem:
I flashed C.26 through Fastbootd and wiped data, and... bootloop!
Looks like device is trying to access wrong slot A or B and unable to.
You need to hold power button + volume up, it should reboot normally. It's a temporary solution, you will face it again after another reboot.
Then you need to transfer the same zip you used to flash into root directory of the phone (where all the folders are living). Go to settings -> About device -> Status -> Tap 7 times on build number to unlock local update feature.
Next, tap on big OxygenOS banner -> Three-dots menu at the top right -> Local install. After, select the zip file you previously copied. Confirm and wait for phone to update itself.
Update will be installed and bootloop issue should be fixed.
breadsnack said:
Erm I've actually got no clue, I know for a fact that if your bootloader is unlocked, OEM unlocking is on by default and greyed out so you cannot turn it off while the bootloader is in it's unlocked state. I did re-enable developer options after locking my phone again and OEM unlocking was turned off by default. This hasn't bricked my phone and I'm assuming that if it had the potential chance to, OnePlus would have greyed it out. See below:
View attachment 5859683
Click to expand...
Click to collapse
for my case OEM did not turn off by default, however, i did it and there is no issues .. thanks
thegreatn_ said:
How I fixed my "bootloop" problem:
I flashed C.26 through Fastbootd and wiped data, and... bootloop!
Looks like device is trying to access wrong slot A or B and unable to.
You need to hold power button + volume up, it should reboot normally. It's a temporary solution, you will face it again after another reboot.
Then you need to transfer the same zip you used to flash into root directory of the phone (where all the folders are living). Go to settings -> About device -> Status -> Tap 7 times on build number to unlock local update feature.
Next, tap on big OxygenOS banner -> Three-dots menu at the top right -> Local install. After, select the zip file you previously copied. Confirm and wait for phone to update itself.
Update will be installed and bootloop issue should be fixed.
Click to expand...
Click to collapse
This is another method of solving the bootlooping issue. I'm assuming that the device just automatically unscrews itself when it receives an update through within the OS. The bootlooping issue is probably because its trying to find a bootable OS through both slot A and B until it manages to fix itself. I personally just flashed C22 and updated to C26 and it had the same effect as flashing C26 and flashing C26 again in local updates.
Thanks for the info! I'll append it to the guide in a bit...
Adly1991 said:
for my case OEM did not turn off by default, however, i did it and there is no issues .. thanks
Click to expand...
Click to collapse
Sweet, will append this information to the guide!
breadsnack said:
This is another method of solving the bootlooping issue. I'm assuming that the device just automatically unscrews itself when it receives an update through within the OS. The bootlooping issue is probably because its trying to find a bootable OS through both slot A and B until it manages to fix itself. I personally just flashed C22 and updated to C26 and it had the same effect as flashing C26 and flashing C26 again in local updates.
Thanks for the info! I'll append it to the guide in a bit...
Click to expand...
Click to collapse
I'd like to point out that there is no need to unpack the zip file, Updater will do everything automatically.
This is to inform that i got update c.26 and c.27 through OTA with no issue ..
Wonderful lemme know if you run into any more issues and I'll be glad to help
Adly1991 said:
This is to inform that i got update c.26 and c.27 through OTA with no issue ..
View attachment 5882617
Click to expand...
Click to collapse
thk202 said:
Hello, Im facing this issue when tried to unlock.
The code fastboot flashing unlock not be proceeded but show the whole line with options as below image.
Could you please help !!1
View attachment 5856125
Click to expand...
Click to collapse
how you fixed this issue ? i got same problem .