[GUIDE] Unlock the bootloader of OnePlus X without using fastboot & wiping userdata - OnePlus X Q&A, Help & Troubleshooting

[GUIDE] Unlock the bootloader of OnePlus X without using fastboot & wiping userdata
Introduction
As we know, the official way to unlock the bootloader of OnePlus X is through fastboot.
For a untouched device, the status of the bootloader should be:
Code:
fastboot oem device-info
...
(bootloader) Device tampered: [COLOR="Red"]false[/COLOR]
(bootloader) Device unlocked: [COLOR="Red"]false[/COLOR]
To unlock the bootloader, you need to enable 'OEM unlocking' under Developer options first, then via bootloader/fastboot interface:
Code:
fastboot oem unlock
It'll eventually erase the userdata.
Then the status of the bootloader should be:
Code:
fastboot oem device-info
...
(bootloader) Device tampered: [COLOR="Red"]false[/COLOR]
(bootloader) Device unlocked: [COLOR="Red"]true[/COLOR]
Inspired by the findings on similar devices, we can actually unlock the bootloader of OnePlus X without using fastboot, while keeping the userdata intact.
How-to
Warning!
It is dangerous! This whole thing is basically one giant hack - which is not intended to be done by normal users. It is messing with the bootloader partition, so it is possible that something goes wrong and you will have a nice & costly brick in your pocket. Be prepared to revive the device from a hard-brick.
1.
Enable 'OEM unlocking' under Developer options. You may need to tap the Build number 7 times under About phone to get the Developer options under Settings.
2.
We need root access (kinda expected!). To root the device without unlocking bootloader, use KingRoot. Use the Android version.
Now there is a catch! KingRoot can root the device, cause the latest build of Oxygen OS (2.2.1 ATM) contains such vulnerabilities which can be exploited by the root exploits used by KingRoot. But we can't ensure about future.
See here for more info.
3.
After being rooted, use adb shell or any terminal emulator to dump the 'aboot' i.e bootloader partition in internal sdcard:
Code:
su
dd if=/dev/block/platform/msm_sdcc.1/by-name/aboot of=/sdcard/aboot.img
4.
Now we need to modify the dumped image using hex-editor. For OnePlus X:
Code:
Unlock Bit Position - 0x000FFE10 Hex
Tamper Bit Position - 0x000FFE14 Hex
'00' means false, '01' means true. So to set the bootloader as unlocked, we just need to change the following:
{
"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"
}
Save the modified image as 'abootmod.img' inside your sdcard.
5.
Now its time to flash back the modded bootloader. Execute the following from adb shell or any terminal emulator:
Code:
su
dd if=/sdcard/abootmod.img of=/dev/block/platform/msm_sdcc.1/by-name/aboot
Do a reboot & voila! You have unlocked the bootloader! Don't just believe me - check the status of the bootloader to ensure.
Note
1. We can also reset the tamper bit using this procedure.
2. If you prefer GUI, then you can use this fantastic app by @wanam.
3. This is tested on an Asia/EU (E1003) variant of OnePlus X running Oxygen OS 2.2.1. Please test & post feedback to ensure compatibility.
4. I'm not providing pre-modified images as it increases the risk of bricking the devices having older/newer bootloaders - please do it yourself. The offsets should be unchanged in future, though.
Credits
1. @osm0sis
2. @segv11
3. @Mnt-XDA
4. My sister - for risking her device for this experiment.
5. Users of XDA & OnePlus forums.
Happy tinkering! :highfive: :good:

Reserved for future.

Where is the 000FFE14 hex ?
Found 000FFE10 hex but no 14?
Can you provide the aboutmod.img?
Sent from my ONE E1003 using XDA-Developers mobile app

sifatrhmn said:
Where is the 000FFE14 hex ?
Found 000FFE10 hex but no 14?
Can you provide the aboutmod.img?
Click to expand...
Click to collapse
It is on the same line of OOOFFE10 after four positions you will see 1 it is 000FF14 change that to O

shravanv3 said:
It is on the same line of OOOFFE10 after four positions you will see 1 it is 000FF14 change that to O[/QUOTE
where can i found line of bootloader on another device ?
there is somthing special to identified the bootloader line ?
thanks
Click to expand...
Click to collapse

deleco said:
shravanv3 said:
It is on the same line of OOOFFE10 after four positions you will see 1 it is 000FF14 change that to O[/QUOTE
where can i found line of bootloader on another device ?
there is somthing special to identified the bootloader line ?
thanks
Click to expand...
Click to collapse
No 000FF10 is for bootloader
Click to expand...
Click to collapse

shravanv3 said:
deleco said:
No 000FF10 is for bootloader
Click to expand...
Click to collapse
excuse me but cant understand
i mean line to identified the bootloader to change 00 to 10
where can i found it on another devices ?
hope you can understand me now
thanks
Click to expand...
Click to collapse

Related

[How To] Unlocking bootloader & Installing TWRP 2.8.6.1 on Oneplus 2

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Hello all,
Here a tutorial for how to install the TWRP 2.8.6.1 on a Oneplus 2 device.
Attention:
I am not liable for breaking your own phone. I do this every day for customers and often it always works. It may be that something goes wrong (errors I have not come across!
First you must unlock your bootloader, to install TWRP later.
Step 1. Unlocking your bootloader!
Download adb & fastboot: http://forum.xda-developers.com/showthread.php?t=2588979 i am using version 1.3
Enable OEM unlock and USB debugging:
Go to your phone’s settings » About phone » and tap “Build number” Seven/Ten times. This will enable Developer options on your OnePlus 2.
Now go to Settings » Developer options » and look for “Enable OEM unlock” option, tick the checkbox next to it.
On the same page, also tick the USB debugging checkbox.
Step 3.
Connect your phone to PC and open a command window on the PC.
Step 4.
Reboot your OnePlus 2 into Bootloader/Fastboot mode by issuing the following command:
Code:
adb reboot bootloader
└ Check your phone’s screen, if it asks for “Allow USB debugging”, accept it by selecting OK/Yes.
Once it is booted into Bootloader mode, issue the following command to finally unlock bootloader on your OnePlus 2:
Code:
fastboot oem unlock
└ This will unlock the bootloader on your OnePlus 2 and also completely wipe your phone while doing that. So make sure you backup everything important on your device before unlocking the bootloader.
Once bootloader is unlocked, your OnePlus 2 will automatically reboot. In case it asks for bootloader unlock permission on the device, accept it.
That’s all. Your OnePlus 2 bootloader should be unlocked now and you can install/flash a custom recovery like TWRP or CWM on it.
Installing TWRP 2.8.6.1 on Oneplus 2
Step 1.
Download the TWRP 2.8.6.1.img from here: https://xq55.app.box.com/OnePlus2Recovery/1/4224692657/34795782429/1
Note: This guide assumes that your device has an unlocked bootloader.
Step 2.
Enable USB debugging on your device:
Open Settings on your device.
Go to About phone and tap seven times on Build number, this will enable Developer options.
Now go back to Settings and you’ll see “Developer options” there, open it.
Tick the USB Debugging checkbox.
Step 3.
Open the folder where your TWRP Recovery .img file is saved.
Step 4.
Now open a command window inside that folder. To do that, “Shift + Right click” on any empty white space inside the folder and then select “Open command window here” from the context menu.
Step 5. Connect your device to the PC. And type the following into the command window we opened in step 4 above to boot your device into bootloader/fastboot mode:
Code:
adb reboot bootloader
└ If your asks for permission to “Allow USB debugging”, tap OK.
Step 6.
Once your device boots into bootloader mode, issue the following command into command window to flash the TWRP recovery .img file:
Code:
fastboot flash recovery twrp-2.8.x.x-xxx.img
└ Here modify twrp.img with the name of your TWRP recovery .img file, OR change your TWRP recovery filename to twrp.img and use the command above.
Step 7.
Once TWRP is successfully flashed on your device, issue the following command to reboot:
Code:
fastboot reboot
That’s all. We hope this guide serves you well. If there’s anything you’d like to be added/changed on this page, let us know about it in the comments section below.
Greetz,
J Hasanovic
W: http://www.gadgetshopeurope.eu
E: [email protected]
D: [email protected]
Hi, is there the same problem with TWRP 2.8.7.0 than with the ONE ? I mean it doesn't flash radio files
Thanks
Thanks for the info. Just a small check.
Is the Warrenty void? Cause oneplus is always open for developers and I remember many mentioning that..,
YOUR WARRENTY IS NOT VOID in the previous opo forums.
Is there a version of TWRP that's actually built by the TWRP team? Everyone keeps linking to this site and I don't trust it, especially because they actually branded their site's name directly into TWRP.
thebuginyou said:
Thanks for the info. Just a small check.
Is the Warrenty void? Cause oneplus is always open for developers and I remember many mentioning that..,
YOUR WARRENTY IS NOT VOID in the previous opo forums.
Click to expand...
Click to collapse
Your warranty is not void by unlocking bootloader as confirmed by Oneplus on their forum.
How is this different than Heisenberg's method in the thread stickied above?
http://forum.xda-developers.com/oneplus-2/general/guides-how-to-guides-beginners-t3146568
CafeKampuchia said:
How is this different than Heisenberg's method in the thread stickied above?
http://forum.xda-developers.com/oneplus-2/general/guides-how-to-guides-beginners-t3146568
Click to expand...
Click to collapse
It's basically the same, following either one will net the same results.
Hello can please upload the stock recovery of oxygen os.The one that is uploaded in ur link is of hydrogen os.
Thanks
Hello the recovery you uploaded,Is it same for opt using oxygen os too?

LG Tribute Empire, Model # LM-X220PM Rooting help

Hey all!
So I have a LG Tribute Empire, and I want to put LineageOS or some other variant. Its sprint locked and I can't get the bootloader to unlock.
This is what I do on my PC.
Code:
PS C:\Users\****\Desktop\platform-tools> .\adb devices
List of devices attached
LMX220PM89R84PAUZ9 device
Then,
Code:
PS C:\Users\****\Desktop\platform-tools> .\adb reboot bootloader
But all it does is just reboot.
Code:
PS C:\Users\****\Desktop\platform-tools> .\fastboot oem unlock
< waiting for any device >
I can't find anything on the internet to help me. So please help!
To prepare phone for unlocking its boot-loader you must have enabled "OEM unlock" in Settings->Developer option and then have rebooed the phone.
To unlock phone's boot-loader you run this command sequence
Code:
adb devices
adb disable-verity
adb shell "setenforce 0"
adb reboot bootloader
fastboot devices
fastboot flashing unlock [color=red]<- fastboot oem unlock is not applicable for all devices[/color]
fastboot reboot
@jwoegerbauer
I have the "OEM unlocking" turned on already.
When I try
Code:
adb disable-verity
I get
Code:
disable-verity only works for Userdebug builds verity cannot be disabled/enabled - USER build
@That_One_Dude_
Ignore it, proceed with next commands
@jwoegerbauer
Okay so I put them all in order and these are the results.
Code:
[****@****-******** ~]$ adb devices
List of devices attached
LMX220PM89R84PAUZ9 device
[****@****-******** ~]$ adb disable-verity
disable-verity only works for userdebug builds
verity cannot be disabled/enabled - USER build
[****@****-******** ~]$ adb shell "setenforce 0"
setenforce: Couldn't set enforcing status to '0': Permission denied
[****@****-******** ~]$ fastboot devices
[****@****-******** ~]$ fastboot flashing unlock
< waiting for any device >
then,
Code:
[****@****-******** ~]$ fastboot reboot
< waiting for any device >
I have been able to successfully root my Moto G7 without any problem, I don't know why this isn't working.
That_One_Dude_ said:
@jwoegerbauer
Code:
[****@****-******** ~]$ fastboot devices
Click to expand...
Click to collapse
If this command doesn't deliver an output similar to this
{
"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"
}
then your Fastboot driver isn't working at all.
This isn't surprising me because the phone is based on Mediatek chipset what requires to use a conformant Fastboot driver.
@jwoegerbauer
Okay so do I need to install a new Fastboot driver?
@That_One_Dude_
I no longer participate this thread. May be other fellow members will successfully guide you.
I have that phone as well and I am trying to get past the starting area. This chick I got it from didn't give me the pattern after she reset it and gave it to me and so I have no way to turn on ads or click on oem unlocking. So can I even proceed further. Or is the phone just a paperweight now??? I want to try a custom rom if there is any for this sprint variant which I don't even know anything about it's firmware or software and a custom recovery like the twrp touch wiz version. And hopefully root. I heard about its hardware but don't really understand whats wrong with mediatek ik 64bit? Uhmm, so I'm kinda in a worse boat than the other fellow. But if anyone hears this post and I hopefully didn't break any posting rules, I really could or would love the info on it. Thank you. Member newbie
[email protected] said:
I have that phone as well and I am trying to get past the starting area. This chick I got it from didn't give me the pattern after she reset it and gave it to me and so I have no way to turn on ads or click on oem unlocking. So can I even proceed further. Or is the phone just a paperweight now??? I want to try a custom rom if there is any for this sprint variant which I don't even know anything about it's firmware or software and a custom recovery like the twrp touch wiz version. And hopefully root. I heard about its hardware but don't really understand whats wrong with mediatek ik 64bit? Uhmm, so I'm kinda in a worse boat than the other fellow. But if anyone hears this post and I hopefully didn't break any posting rules, I really could or would love the info on it. Thank you. Member newbie
Click to expand...
Click to collapse
Add. Oops
[email protected] said:
Add. Oops
Click to expand...
Click to collapse
Adb dam spell checker.
[email protected] said:
I have that phone as well and I am trying to get past the starting area. This chick I got it from didn't give me the pattern after she reset it and gave it to me and so I have no way to turn on ads or click on oem unlocking. So can I even proceed further. Or is the phone just a paperweight now??? I want to try a custom rom if there is any for this sprint variant which I don't even know anything about it's firmware or software and a custom recovery like the twrp touch wiz version. And hopefully root. I heard about its hardware but don't really understand whats wrong with mediatek ik 64bit? Uhmm, so I'm kinda in a worse boat than the other fellow. But if anyone hears this post and I hopefully didn't break any posting rules, I really could or would love the info on it. Thank you. Member newbie
Click to expand...
Click to collapse
Hey sorry for such a late reply, but i looked and looked and I couldn't find anything about the damn phone almost anywhere.
I have not been able to unlock the bootloader of my LM-X220PM, but I was able to achieve temporary and limited root by following this thread. You will not be able to install a custom ROM on it, but you could block ads, use Titanium Backup, etc.

Development Prototype ABL binaries from Nokia 3.4 and 5.4, for bootloader unlock purpose.

You should've already figured out where are these binaries from. I can't help further for these 2 models.
WARNING: This is not a guide! Prototype ABL binaries are provided as-is, flashing them can be risky!
I'm not responsible for potentially permanent brick!
Nokia 3.4 prototype ABL image has been proved functional.
{
"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"
}
To use it:
1. Enable flashing permission with HDK (an internal flash tool used by triple-color company, sorry can't disclose more details about that). Please search for related service online, we don't provide or promote such service.
2. Download Prototype ABL from following URL:
Click here for NOKIA 3.4 (DoctorStrange ZQL1838)
Click here for NOKIA 5.4 (DoctorDoom ZQL1849)
3. Flash prototype ABL and OEM unlock enabled frp partition manually, then you can confirm bootloader unlock:
Code:
(for Nokia 3.4) fastboot flash abl DRS-abl.elf
(for Nokia 5.4) fastboot flash abl DRD-abl.elf
(IMPORTANT, DO NOT SKIP) fastboot flash frp frp_oemunlock.img
fastboot reboot-bootloader
fastboot flashing unlock_critical
fastboot oem unlock-go
4. Once bootloader unlock completed, please reinstall stock OS to restore ABL back to normal.
SHA256 checksum of ABL images:
Code:
Nokia 3.4: 79d49737009b1c87f452d814ba6cf5669ccd35a2983f4413f817a7595cb67cfc
Nokia 5.4: 333b221671ed9abe6bd471f29d3c0b14cfeaeebcdc587f882097740f244b93a9
Root Key Hash of ABL images - technically they may interchangable due to same RKH.
Code:
Nokia 3.4: 35631A56E4F0D69967853A758FEF4FF742CF7C6A71B84CE863FE3FCBC70CC394
Nokia 5.4: 35631A56E4F0D69967853A758FEF4FF742CF7C6A71B84CE863FE3FCBC70CC394
This procedure requires specific version of Android? The HDK tool is provided only by the manufacturer?
Rierei said:
This procedure requires specific version of Android? The HDK tool is provided only by the manufacturer?
Click to expand...
Click to collapse
Specific Android version is not required.
HDK access is required to allow you flash any bootloader partitions.
where can i get frp_oemunlock.img and stock os?
are they available with HDK?
Hi guys, I have bootloader unlocked and rooted my Nokia 5.4! however when I tend to delete apps from the system as usual there is always some error! Android 12 February Security Patch!
if anyone wants a recovery image to do a TWRP I can give it!
Someone made it for 3.4?
thimemoria said:
Hi guys, I have bootloader unlocked and rooted my Nokia 5.4! however when I tend to delete apps from the system as usual there is always some error! Android 12 February Security Patch!
Click to expand...
Click to collapse
May you describe how did you manage to unlock the bootloader? Do you have HDK access?
false96 said:
May you describe how did you manage to unlock the bootloader? Do you have HDK access?
Click to expand...
Click to collapse
I got in touch via Telegram with the guy who does the unlocking via TeamViewer or Anydesk and he unlocked it, since the Root process is a little different I had to flash a different boot .img
As I probably can't post links here, whoever wants it I'll send it by PV
Guys, I made a port of TWRP from A3 to Nokia 5.4! Normal boot but need to edit fstab I'll do that and study how it works anything I'll let you know or create a topic!
thimemoria said:
Guys, I made a port of TWRP from A3 to Nokia 5.4! Normal boot but need to edit fstab I'll do that and study how it works anything I'll let you know or create a topic!
Click to expand...
Click to collapse
Great work! Thanks for your efforts. I hope one day we'll have some custom roms.
thimemoria said:
if anyone wants a recovery image to do a TWRP I can give it!
Click to expand...
Click to collapse
could you let me get a copy for the Nokia 5.4
thimemoria said:
As I probably can't post links here, whoever wants it I'll send it by PV
Click to expand...
Click to collapse
hey, I also want one for my Nokia X10!
I´m also interestet in the TWRP for Nokia 5.4 - could you send it to me by PV? Thanks on behalf
thimemoria said:
Hi guys, I have bootloader unlocked and rooted my Nokia 5.4! however when I tend to delete apps from the system as usual there is always some error! Android 12 February Security Patch!
Click to expand...
Click to collapse
That's likely because the system is only mounted as r/o. You can't write there. But maybe I am wrong?
thimemoria said:
if anyone wants a recovery image to do a TWRP I can give it!
Click to expand...
Click to collapse
I never received a message from you about the twrp for Nokia 5.4
does anyone have the twrp for Nokia 5.4
[email protected] said:
does anyone have the twrp for Nokia 5.4
Click to expand...
Click to collapse
eh, no one does. The phone has just had its ABL for bootloader unlocking released, so, of course, there are no TWRP ports for it.
However, you can learn how to port TWRP into the phone (though, really, it'll require you to learn programming and whatnot).
I was going by this post further up the thread.
thimemoria said:
if anyone wants a recovery image to do a TWRP I can give it!

Sony Xperia L3 root phone.

I have a Sony Xperia L3 and i have tried to root but it seems impossible. How can i do it? I have tried to root the phone with Sony Xperia C Root but it could not do it. Kingo Root is the same, fail. Also tried dr.fone but it did not support l3.
You must unlock the bootloader and then follow this steps: https://topjohnwu.github.io/Magisk/install.html
I have check and my phone can be unlocked, i have downloaded fastboot but i do not understand what to do next. I got to step 8 https://www.xda-developers.com/install-adb-windows-macos-linux/ i can see my phone in the command line, what to do next?
I cannot find the fastboot icon under devices and printers
I got to https://mobilewithdrivers.com/unlock-bootloader/sony-xperia-l3-32gb-3gb-ram i got it into fastboot mode but no commands works, fastboot flashing unlock, fastboot oem unlock. Unknown command, command not allowed.
Should i have a unlock code? I only see Xpeira L2 on the site for getting a unlock code, no L3 https://www.getdroidtips.com/unlock-bootloader-xperia-device/
It seems to be something wrong in developer mode, oem do not turn on, no green, it is just off.
Oldschool297 said:
I have a Sony Xperia L3 and i have tried to root but it seems impossible. How can i do it? I have tried to root the phone with Sony Xperia C Root but it could not do it. Kingo Root is the same, fail. Also tried dr.fone but it did not support l3
Click to expand...
Click to collapse
What's phone's Android version? Android 8.1 ? If so, look inside here:
[HOW TO] Root Android 8.1 - DevPreview 1 - OPP5
There are probably already a couple guides up, but I wanted to post about how I went about doing this and have everything working. It may not work for everyone, but for me, it worked the first time. 0: Yep, there is a step zero here. :good...
forum.xda-developers.com
Thanks. I cannot unlock the bootloader to try. I do not get the oem under development mode to work. It is only off. I can't get it on to unlock the bootloader.
Why not contact Sony ?
Sony Support Consumer Electronics
services.sony.co.uk
I tried the guide https://www.kingoapp.com/root-tutorials/how-to-unlock-bootloader-android-device.htm i get it to fastboot and the light is blue but i only get. Failed remote: Command not allowed, Finished. total times 0.045s.
What Fastboot command did you run?
BTW: Install the suitable Fastboot driver provided by Sony, if not already done yet.
I tried
Use the Command Prompt window to retrieve your unlock key as described by your manufacturer. If you own a Motorola device run the command: fastboot oem get_unlock_data, HTC run the command: fastboot oem get_identifier_token.
Select the token which is spit out by the Command Prompt window and copy and paste it into the applicable box of the form on your manufacturer's website without any spaces.
And: fastboot -i 0x0fce oem unlock 0x07B7BFEA7AC879F0 https://www.getdroidtips.com/unlock-bootloader-sony-xperia-x-f5121f5122/
I downloaded android_winusb.inf were should i add it?
Don't understand what you've downloaded. It's an ADB driver.
Contents of relevant ADB driver 's .ZIP-file is
{
"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"
}
To install the suitable ADB driver:
Open the Device Manager. To do this, click Start and type Device Manager. Then click Device Manager.
In Device Manager, right-click the name of your computer at the top of the device list, and then click Add Legacy Hardware.
In the Welcome to the Add Legacy Hardware Wizard dialog box, click Next.
Select Select and install hardware manually from a list and click Next.
Select Show all devices and click Next.
Click Disk....
In the Disk... dialog box, click Browse... click Browse, and then select the driver file with the extension adb (written like this: xxxxxadb, where xxxxxx is the unique file name). Click Open.
In the Disk... dialog box, click... Click OK.
Highlight the Sony xxxxxx ADB Interface Driver file and then click Next twice. The installation starts.
Click Finish and restart the computer.
I get this.
I also tried https://techbeasts.com/how-to-unlock-bootloader-of-sony-xperia-devices-guide/ the problem in fastboot seems to be that i- becomes and unknown option
https://forums.androidcentral.com/t...tloader-fastboot-exe-unknown-option-i.895276/ fastboot R26 seems to work for the most i have the 34. platform-tools v 28.0.0 does not work with the provided command from the official manual.
Yes it was the version, it is the second time i try to mess with andriod phones. I learn more and more. I tried fastboot.exe i- 0x0fce getvar version and i got version 0.5, finished, total time 0.000s
I tried fastboot.exe -i 0x0fce oem unlock 0x and got FAILED, command not allowed. I did only find Sony L, L1 and L2 on sony oem https://developer.sony.com/develop/open-devices/get-started/unlock-bootloader/#unlock-code can it be that? I remeber i had a Sony Xperia X code.
I also tried fastboot flashing unlock, FAILED unknown command. with fastboot devices i got my phone visable.

Development Prototype ABL binaries from Nokia X10 and X100, for bootloader unlock purpose.

If you've followed my prototype ABL image release topics so far, then you should know where it comes from.
This topic will be edited later if X20 one is available.
{
"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"
}
WARNING: This is not a guide! Prototype ABL binaries are provided as-is, flashing them can be risky!
DO NOT FLASH IT INTO X20 OR IT WILL CAUSE DEAD BRICK!
1. Enable flashing permission with HDK (an internal flash tool used by triple-color company, sorry can't disclose more details about that). Please search for related service online, we don't provide or promote such service.
2. Download Prototype ABL from following URL:
Click here for Nokia X10 (ScarletWitch)
Click here for Nokia X100 (Deadmau5)
3. Flash prototype ABL manually, then you can confirm bootloader unlock:
Code:
(Nokia X10) fastboot flash abl SCW-abl.elf
(Nokia X100) fastboot flash abl DM5-abl.elf
fastboot reboot-bootloader
fastboot oem unlock-go
4. Once bootloader unlock completed, please reinstall stock OS to restore ABL back to normal.
SHA256 checksum of ABL image:
Code:
SCW-abl: 3a949e4b27c1b559cfd016a894fc1a4bb81d01c9ab323a86ab2603c313f4177b
QKS-abl: missing
DM5-abl: f16bafb998925b7a3f7651eb21edba8bb4283113f56628d9b0b685882015696b
Root Key Hash of ABL images:
Code:
Nokia X10: F552CB7380F2F46F92B4CC25AB923A8A234A45357601BEE1CC06D42C0790C4A0
Nokia X20: 2FDC6D616C061309BBADDDCA9C69CA0F3F8CA0E1CDF5F74F274E34B77F5CE8B6
Nokia X100: 05C8E21116890E3DAF3879ED4939F7F6267A3CA2085E3E943743E938C80C28C1
I'll have a go, thanks!
Alvy123 said:
I'll have a go, thanks!
Click to expand...
Click to collapse
it requires you to gain access of the tool from tri-color company, which is.... actually impossible.
The only way one can use it without any restrictions is if the same one is Nokia's customer support....
hikari_calyx said:
If you've followed my prototype ABL image release topics so far, then you should know where it comes from.
This topic will be edited later if X20 one is available.
WARNING: This is not a guide! Prototype ABL binaries are provided as-is, flashing them can be risky!
DO NOT FLASH IT INTO X20 OR IT WILL CAUSE DEAD BRICK!
1. Enable flashing permission with HDK (an internal flash tool used by triple-color company, sorry can't disclose more details about that). Please search for related service online, we don't provide or promote such service.
2. Download Prototype ABL from following URL:
Click here
3. Flash prototype ABL and OEM unlock enabled frp partition manually, then you can confirm bootloader unlock:
Code:
fastboot flash abl SCW-abl.elf
fastboot reboot-bootloader
fastboot oem unlock-go
4. Once bootloader unlock completed, please reinstall stock OS to restore ABL back to normal.
SHA256 checksum of ABL image:
Code:
3a949e4b27c1b559cfd016a894fc1a4bb81d01c9ab323a86ab2603c313f4177b
Root Key Hash of ABL images:
Code:
Nokia X10: F552CB7380F2F46F92B4CC25AB923A8A234A45357601BEE1CC06D42C0790C4A0
Nokia X20: 2FDC6D616C061309BBADDDCA9C69CA0F3F8CA0E1CDF5F74F274E34B77F5CE8B6
Click to expand...
Click to collapse
can I use 3rd-party tools (e.g: Fire Tool) to enable flashing perms, instead of HDK?
I presume that this is all supposed to be a bit of a mystery.
I have a custom abl on a different device.
I just de-engineered it, patched it, re-hashed it.
But thiat device does not have SecureBoot enabled.
That's a rarity.
Renate said:
I presume that this is all supposed to be a bit of a mystery.
I have a custom abl on a different device.
I just de-engineered it, patched it, re-hashed it.
But thiat device does not have SecureBoot enabled.
That's a rarity.
Click to expand...
Click to collapse
Oh wow, that's interesting. Mind telling me the full details about what you did?
AltFantasy said:
Mind telling me the full details about what you did?
Click to expand...
Click to collapse
Here's a whole thread on abl packing: https://forum.xda-developers.com/t/qualcomm-abl-android-bootloader-packing-signing.4473815/
Then there's the reverse engineering, probably using Ghidra or Ida.
Ghidra annoys me so I use my own custom stuff that simply annotates what objdump puts out.
I feel closer to the metal that way.
After unpacking/patching/packing abl you've got a modified abl that the signing is wrong.
If you're Nokia, you just take your super-secret private key and resign the abl.
If SecureBoot is not enabled on your device it does not need to be signed, but it needs to be hashed.
Hashing is not at all secret, it's just SHA256 or SHA384 on the program segments (one of which you altered).
My qcomview.exe can do that easily, it's in the sig.
I tested it for somebody; the unlock works by utilizing this abl. Thanks for the share
so far, not much luck
Nokia X10 (X20) Android 13 chances of new ROM/ some-any ways to override settings/ "jail-break"???
In short : X10, UK, Android 13 - thanks, no thanks! 0 actual improvements as per discussed to some degree on Nokia "support forum". Silly bloatware "features" added, but nothing what would be useful. Have tried 50 apps of different kinds...
forum.xda-developers.com
However, since security update, in "developer mode", I've had an option to unlock OEM loader- DONE! restarted the phone- still shows the same- bootloader UNLOCKED
Alvy123 said:
so far, not much luck
Nokia X10 (X20) Android 13 chances of new ROM/ some-any ways to override settings/ "jail-break"???
In short : X10, UK, Android 13 - thanks, no thanks! 0 actual improvements as per discussed to some degree on Nokia "support forum". Silly bloatware "features" added, but nothing what would be useful. Have tried 50 apps of different kinds...
forum.xda-developers.com
However, since security update, in "developer mode", I've had an option to unlock OEM loader- DONE! restarted the phone- still shows the same- bootloader UNLOCKED
Click to expand...
Click to collapse
that option is actually useless.

Categories

Resources