Related
Motorola just released a software download for people using 4.1.51 and 4.1.52. According to them, this will bring any phone on one of those versions back to the official Motorola Software.
Download HERE
Motorola's Announcement HERE
I currently don't have access to my phone, but I would be interested in knowing what this does with bricked phones.
thehacker010 said:
Motorola just released a software download for people using 4.1.51 and 4.1.52. According to them, this will bring any phone on one of those versions back to the official Motorola Software.
Download HERE
Motorola's Announcement HERE
I currently don't have access to my phone, but I would be interested in knowing what this does with bricked phones.
Click to expand...
Click to collapse
Well........that's slightly promising. Seems like a small reach of the olive branch. Still not a bootloader solution though.
Work on Bell Atrix ?
Thanks.
I can't use it, but that might be because it can't get out through the proxy (I'm at work). It just says "Cannot determine something or other blah blah network settings." Then when I exit the program it reboots my phone. Then my phone stays in a reboot loop until I unplug the USB.
Crappy software, there.
Edit: remove all contents
I have looked and looked to no avail, is it no longer possible to flash Lumia firmware through the Nokia Care Suite anymore? I can not seem to find the RM-820 in the open product. Everything tutorial I have seen says to find it in there I did see a comment in a thread where someone said that they didn't think Nokia is allowing that anymore. Is this true? I have the spinning cogs so I wanted to flash the firmware...
So I'm stuck and all help on the internet seems outdated. Is there something I'm missing?
just read forum... there is few ways to download firmware....
http://forum.xda-developers.com/showthread.php?t=2515453
there is a new tool released by nokia that is supposed to help recover / flash phones if they become stuck during boot or flash.
From memory it is called nokia software recovery tool. maybe you could try that if you can find it. I read about it on a site lastnight but can not remember where i saw the info about.
Google may help or it may have even been on here..
Chris
CBDSonline said:
there is a new tool released by nokia that is supposed to help recover / flash phones if they become stuck during boot or flash.
From memory it is called nokia software recovery tool. maybe you could try that if you can find it. I read about it on a site lastnight but can not remember where i saw the info about.
Google may help or it may have even been on here..
Chris
Click to expand...
Click to collapse
I downloaded and installed Nokia Care Suite on a Windows 8.1 PC just last night (EST in New York). I then used to install the Amber update onto a RM-878 that I just bought from Amazon - worked flawlessly.
Instructions in this thread: http://forum.xda-developers.com/showthread.php?t=2515453
I have installed pc suite for Lumia 520 ...but i am not getting usb connect option...
can anyone have idea?
docfreed said:
I downloaded and installed Nokia Care Suite on a Windows 8.1 PC just last night (EST in New York). I then used to install the Amber update onto a RM-878 that I just bought from Amazon - worked flawlessly.
Instructions in this thread: http://forum.xda-developers.com/showthread.php?t=2515453
Click to expand...
Click to collapse
That is exactly what I am talking about. I have read the thread, followed the thread up until it say under product type. Under the sim tray it says RM-820 and there isn't a RM-820 in there, thus this question got asked. I'm not asking for someone to hold my hand through this, I just wanted to know if the RM-820 is or isn't supported with Nokia Care Suite. I know that the software works, flawlessly even, not saying it didn't. I have the firmware downloaded don't need the firmware. Just wanted to know if the Lumia was still supported by Nokia Care Suite, if I was missing something obvious.
chasingeuphoria said:
That is exactly what I am talking about. I have read the thread, followed the thread up until it say under product type. Under the sim tray it says RM-820 and there isn't a RM-820 in there, thus this question got asked. I'm not asking for someone to hold my hand through this, I just wanted to know if the RM-820 is or isn't supported with Nokia Care Suite. I know that the software works, flawlessly even, not saying it didn't. I have the firmware downloaded don't need the firmware. Just wanted to know if the Lumia was still supported by Nokia Care Suite, if I was missing something obvious.
Click to expand...
Click to collapse
What Phone do you have - reason I ask is that the original thread is a little confusing - there is of course a Lumia 820 but its actual Product Type is RM-824 and if you use the 824 Product Type from this thread:Nokia Lumia 820 Product Code (Product Type RM-824)
at http://forum.xda-developers.com/showpost.php?p=49364933&postcount=10 it shows dozens of codes to use for the Nokia Care Suite depending on country and carrier.
docfreed said:
What Phone do you have - reason I ask is that the original thread is a little confusing - there is of course a Lumia 820 but its actual Product Type is RM-824 and if you use the 824 Product Type from this thread:Nokia Lumia 820 Product Code (Product Type RM-824)
at http://forum.xda-developers.com/showpost.php?p=49364933&postcount=10 it shows dozens of codes to use for the Nokia Care Suite depending on country and carrier.
Click to expand...
Click to collapse
It is a Lumia 920 product code RM-820 I saw the product code on that little pull out thing under the Sim tray
http://forum.gsmhosting.com/vbb/f60...ting-care-suite-download-1660094/#post9434336
Hello, I would like to do this unlock on my Ativ S.
Now I'm in the following condition:
Software: Windows Phone8
OS Version: 8.0.10327.77
Firmware revision number: 2424.13.5.1
Number Hardware Revision: 15:15:10
Radio software version: 2424.13.5.1
Radio hardware version: 0.0.0.800
Bootloader Version: 13.04.19.21
Processor SOC Version: 1.5.32
How should I preocedere order to unlock it?
thanks
You don't specify any particular unlock you want to do, so I'm going to assume interop-unlock + capability unlock. If that's not right, try actually saying which one you mean instead of using a pronoun (this) without any antecedent.
Your phone is slightly out of date (GDR2) but that may actually be a good thing anyhow.
First, dev-unlock. You will need the Windows Phone Development Registration tool, which is included in the WP8 SDK, which is available free from Microsoft.
Then, install the Interop Unlock Helper app (there is a link to it in my signature, if for some reason your search is broken...) using the Application Deployment tool (also installed with the SDK).
Run the helper app and follow its instructions...
Thanks for the reply, so the first thing to do is to install Win8 on my notebook (I have Win7)
After installing Win8 with its SDK, can I ask for help on the procedure yet?
There's a modified version of the WP8 SDK that runs on Win7. The emulator doesn't work (it requires Hyper-V, which Win7 doesn't have) but otherwise works fine.
I really told you pretty much the entire procedure. The helper app will guide you though the rest step-by-step; you just need to get as far as installing it.
Thank you, I have sought guidance on the matter.
Would this procedure?
http://forum.xda-developers.com/showthread.php?t=2422751
Can you give me an OK before beginning to drain in the SDK?
You can use Arnold Vink's MiniSDK instead of downloading the whole iso. You can find it in the stickied FAQ. Its actually starting to be pretty comprehensive, covering almost every little subject along the way.
I installed the SDK8 on win7.
Now what should I do?
Where can I find the files Interop Unlock Helper app?
It would be this: EnableAllSideloading_Release_ARM.xap
Thanks
... did you even *TRY* reading the guide linked in my signature? There's a step-by-step in there of which apps to install (with links!) at what times...
GoodDayToDie said:
... did you even *TRY* reading the guide linked in my signature? There's a step-by-step in there of which apps to install (with links!) at what times...
Click to expand...
Click to collapse
I have read the guide but I have not found the link to the helper
http://forum.xda-developers.com/showthread.php?t=2435697
Searching on google I found this which I think is fine too: http://forum.xda-developers.com/showthread.php?t=2434884
... that second link you posted is included in the first link (under "Guide for Samsung's ATIV phones"), along with a direct link to the .XAP as well. But hey, you managed to find it eventually (through the mechanism that you should have used in the first place). I guess I should have specified "there's a link that contains a link to the XAP in my signature" but I figured you'd be able to get there yourself.
Yes, because I took the file (Interop Unlock Helper app)
Do you think I should first upgrade to GDR3 and then proceed with the interop unlock or better to do it in a situation where I am (GDR2)?
... I'm trying to decide whether I should stop spoon-feeding you answers or just go on and hope eventually you'll run out of them.
There are a bunch of forum threads about GDR3 and interop-unlock. Short version: installing the Samsung update that comes with retail GDR3 will prevent interop-unlock. There are ways around it, which you should read up on as well because, while it doesn't re-lock your phone, it *does* make interop-unlock much less useful too.
I followed the steps and I completed the interop unlock but when I try to install the xap BootstrapSamsung app:
Status Error: 0x81030120
I have not updated in the GDR, are in the same terms as the POST1
How can I fix?
Thanks
You either didn't actually interop-unlock at all, or you didn't do the part of the process that prevents re-locking. That error code means you are still interop-locked. You need to change several registry values, not just one. This is in the helper app, unless you're running a *very* old version.
They are divided by 0 and I was able to complete the procedure!
I tried to install xap files but I get this error:
"Error - Deployment Optimization failed with error "Unable to read input file". Please Ensure that input XAP is not optimized for device already".
Xap from Market ?
Try this video. It is german, but you'll know what to do.
https://www.youtube.com/watch?v=bpbj4oibmOc
Hi everyone!
I was wondering if it's possible to flash android on the Alcatel Idol 4s Windows edition. The reason why i am asking is because i noticed that the TCL 950 (android smartphone) shares exactly the same SOC and specs with the Alcatel Idol 4s and it is actually made by the exact same company (TCL). It is basically the exact same phone, with a different brand on it and a different OS.
So i was wondering, would it be possible to flash the TCL 950 firmware on the Idol 4S windows in order to install Android on it? If yes, did any of you guys had the chance to find the firmware for the TCL 950? Cause i searched for it but didn't have any luck...
Thank you so much in advance!
I saw also that @compu829 commented a while back on the argument
steinwayer said:
Hi everyone!
I was wondering if it's possible to flash android on the Alcatel Idol 4s Windows edition. The reason why i am asking is because i noticed that the TCL 950 (android smartphone) shares exactly the same SOC and specs with the Alcatel Idol 4s and it is actually made by the exact same company (TCL). It is basically the exact same phone, with a different brand on it and a different OS.
So i was wondering, would it be possible to flash the TCL 950 firmware on the Idol 4S windows in order to install Android on it? If yes, did any of you guys had the chance to find the firmware for the TCL 950? Cause i searched for it but didn't have any luck...
Thank you so much in advance!
I saw also that @compu829 commented a while back on the argument
Click to expand...
Click to collapse
I still haven't found the firmware myself. As long as it was signed with the same certificate and windows phone, it should be possible.
compu829 said:
I still haven't found the firmware myself. As long as it was signed with the same certificate and windows phone, it should be possible.
Click to expand...
Click to collapse
After doing some heavy research i managed to find it!! Here it is, the TCL 950 firmware
http://pan.baidu.com/s/1geDBRnt
It is the official firmware directly from TCL i managed to talk with their assistance in China
@compu829 how can i flash this firmware now on my idol 4s??
Thank you so much in advance
@steinwayer I will need to download and extract it. I'll take a look later today.
Thanks @compu829
Did you find anything interesting ?
I'm interested in the possibilities here too. Thanks for your research and sharing it!
steinwayer said:
Thanks @compu829
Did you find anything interesting ?
Click to expand...
Click to collapse
I can't download it. Can you? If so can you put it somewhere like mega.co.nz?
I was able to download the package and re-upload it to mega with some help from my friends. Here is the link: https://mega.nz/#!ITJhjYIS!R_iUZhGZMcslAK_u1wdsJ-7q-0D5ma_KrHl4pu2CPqo
I took a quick look, and it is pretty much all mbn files that the factory would flash during assembly, so you will (most likely) need a copy of QPST. We may also be able to use WDRT to flash it. In either case, flashing will fail miserably if the certificates don't match.
So how would you suggest to do this @compu829?
steinwayer said:
So how would you suggest to do this @compu829?
Click to expand...
Click to collapse
compu829 said:
... In either case, flashing will fail miserably if the certificates don't match.
Click to expand...
Click to collapse
^^^ You probably won't be able to easily. At this point, no one here knows, but as @compu829 stated, if the certificates don't match (which they most likely don't), then you're not going to be flashing it at this point.
Would it not be possible to "force" the flashing of that image? Afer all the devices are exactly the same from an hardware perspective..
steinwayer said:
Would it not be possible to "force" the flashing of that image? Afer all the devices are exactly the same from an hardware perspective..
Click to expand...
Click to collapse
Same hardware != same implementation. There's mechanisms that will only allow certain things to be flashed, while all protections are still enabled on the device. Since it's a newer phone, I imagine qualcomm's security mechanisms are stepped up as opposed to how they are on older SoC implementations.
If anything, it will NOT be an easy feat to accomplish, so I will say no to a way of "forcing" it to flash at the moment.
It makes perfect sense
What i was thinking tho is that probably the two devices have even a different bootloader. Meaning that it would be a total wipe of the entire disk including swap partition and try to flash that rom.
I was thinking: imagine a bricked device, sometimes is possible to wipe out completely the memory on it and just flash the right rom. Sadly i do not habe much experience in mobile devices.. been developing only for desktops for years.
But if you guys manage to accomplish that it would be great.
The alcatel idol 4s is a great phone for both specs and design and is currently EXTREMELY cheap to. Buy on ebay (you can even find it at 100 bucks) mainly because of its OS
Being able to turn it into an Android phone would be an amazing feat
snickler said:
Same hardware != same implementation. There's mechanisms that will only allow certain things to be flashed, while all protections are still enabled on the device. Since it's a newer phone, I imagine qualcomm's security mechanisms are stepped up as opposed to how they are on older SoC implementations.
If anything, it will NOT be an easy feat to accomplish, so I will say no to a way of "forcing" it to flash at the moment.
Click to expand...
Click to collapse
Also, a very important factor is that the phones are made by the same shenzhen manufacturer most likely in the same plant. The only thingthey really change is the logo on the back, which comes later on, and the OS.from aanufacturing perspective it would not make much sense to lock with certificates the devices,slowing quite a bit he manufacturing process.it would have sense if the two devices were to be released in the same country, but in this case, tcl 950 is just available in asia, where idol 4s isnot. How can we verify this certificate thing @compu829 ? We have an Idol 4s
hello @snickler do you think that doing this: https://www.youtube.com/watch?v=Iwkx5CFRFKo
would give me a chance of success?
Also, in case of failure for differente certificates, do you think the process would not even start or would it start and brick my device?
Thanks
Update: I am trying to let QFIL to see my device.
First i put my device in flash mode by shutting it down and then immediately pressing and holding the volume up key. It goes in flash mode. I launch QFIL , connect the phone over the USB port, but the tool does not see my device.. i tried installing several qualcomm usb drivers, but till now no luck.
You guys have any suggestions??
@snickler @compu829 ?
Thanks in advance
It won't work. This is for phones stuck in QDLoader 9008 mode (DEAD MODE) and DLOAD mode. The Sahara protocol only accepts signed programmers that are stored in the UEFI. You also need the exact flashers for the particular phone for it to work as it's specific to the phone's bootloader (which is definitely signed)
snickler said:
It won't work. This is for phones stuck in QDLoader 9008 mode (DEAD MODE) and DLOAD mode. The Sahara protocol only accepts signed programmers that are stored in the UEFI. You also need the exact flashers for the particular phone for it to work as it's specific to the phone's bootloader (which is definitely signed)
Click to expand...
Click to collapse
Which method would you suggest me to try??
steinwayer said:
Update: I am trying to let QFIL to see my device.
First i put my device in flash mode by shutting it down and then immediately pressing and holding the volume up key. It goes in flash mode. I launch QFIL , connect the phone over the USB port, but the tool does not see my device.. i tried installing several qualcomm usb drivers, but till now no luck.
You guys have any suggestions??
@snickler @compu829 ?
Thanks in advance
Click to expand...
Click to collapse
I don't know what QFIL is, but vol up and power will put the windows phone in a flash mode that is compatible with WDRT. This mode is completely different than the Qualcomm mode. You most likely need to intentionally brick your device to enable Qualcomm recovery mode.
steinwayer said:
Which method would you suggest me to try??
Click to expand...
Click to collapse
No method. It's probably not best to randomly try things without understanding the underlying mechanisms and the implications of what could happen in the end.
Honestly, IMO, if you want Android then buy an Android phone. I understand that it would be cool to be able to swap out, but the likelihood of this happening right now is close to zero.
snickler said:
No method. It's probably not best to randomly try things without understanding the underlying mechanisms and the implications of what could happen in the end.
Honestly, IMO, if you want Android then buy an Android phone. I understand that it would be cool to be able to swap out, but the likelihood of this happening right now is close to zero.
Click to expand...
Click to collapse
If only i could put my hands on the software they use at tcl to flash their devices...
This is oje of the reasons why smartphones are still way behind computers. Not much freedom of choice and yet theorically it would be more than possible to allow a certain level of freedom on it
Few months ago a customer asked me to flash couples of Nokia XR20 prototype unit for him, so I managed to get prototype ABL dump of this phone.
WARNING: This is not a guide! DO NOT TRY IT ON OTHER SNAPDRAGON 480 BASED NOKIA PHONES INCLUDING G50, X10, X20, X100, G300 - UNLESS YOU KNOW WHAT YOU'RE DOING!
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
3. Flash prototype ABL and OEM unlock enabled frp partition manually, then you can confirm bootloader unlock:
Code:
fastboot flash abl TTG-abl.elf
fastboot reboot-bootloader
fastboot flashing unlock
fastboot flashing unlock_critical
4. Once bootloader unlock completed, please reinstall stock OS to restore ABL back to normal.
SHA256 checksum of ABL image: ac8143f6e0b449c39127aedd6463e2b9242cf37ce90a86c2988b885e34b0587f
Root Key Hash of ABL image: 622D3D5FE38C4198DDFABB264034EFDE58B986B510393A0CF163E803A3FD985E
Proof of concept is attached below, thanks to @singhnsk for testing.
Bro, Nokia x10 please?
HDK.
Where can I get?
Full name please of this app.
mishak750 said:
HDK.
Where can I get?
Full name please of this app.
Click to expand...
Click to collapse
nope, you can't use it, even if you get the full name
hikari_calyx said:
Few months ago a customer asked me to flash couples of Nokia XR20 prototype unit for him, so I managed to get prototype ABL dump of this phone.
WARNING: This is not a guide! DO NOT TRY IT ON OTHER SNAPDRAGON 480 BASED NOKIA PHONES INCLUDING G50, X10, X20, X100, G300 - UNLESS YOU KNOW WHAT YOU'RE DOING!
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
3. Flash prototype ABL and OEM unlock enabled frp partition manually, then you can confirm bootloader unlock:
Code:
fastboot flash abl TTG-abl.elf
fastboot flash frp frp_oemunlock.img
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: ac8143f6e0b449c39127aedd6463e2b9242cf37ce90a86c2988b885e34b0587f
Proof of concept is attached below, thanks to @singhnsk for testing.
Click to expand...
Click to collapse
man, I'm jealous of XR20 users!
here's hoping that someone will find a X10 prototype soon!
AltFantasy said:
man, I'm jealous of XR20 users!
here's hoping that someone will find a X10 prototype soon!
Click to expand...
Click to collapse
THAT CAME TRUE, **** YEAH!!!
Posted new topic in X10/ X20 phone section, before reading everything up here...
Seems "up the sh*t creek without a paddle" situation.
Damn Nokia, but if anyone would get it working- I'll subscribe to this topic too.
Cheers!
Visionu said:
Bro, Nokia x10 please?
Click to expand...
Click to collapse
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. WARNING: This is not a guide! Prototype ABL binaries are provided as-is...
forum.xda-developers.com
Here you go
Trying not to be offtopic, why a decent phone, from a well known brand like Nokia, that often offered android one devices has now low to zero interest from developers? It's not polemic, I am just curious
phaleg said:
Trying not to be offtopic, why a decent phone, from a well known brand like Nokia, that often offered android one devices has now low to zero interest from developers? It's not polemic, I am just curious
Click to expand...
Click to collapse
Politics+proffits= end user loss
as it comes to coders, it's only so far we get allowed to delve in to, there was time, when I have physically remodded ZTE phone, from non funcioning device in to best phone at the time ALL- during one day on PC using no more that 3 tools and 2 ROM's... now you are constrained to even to get an access to bootloader or the way to extract it without phone started. Silly win for the google (nokia) developers in constraining modifications, with time, (loss of sales) that might change, hence "politics"
Anyone managed to enable boot loader access? Mine had already A13 (funk it) with oem function access disable (grey) in developer mode
phaleg said:
Trying not to be offtopic, why a decent phone, from a well known brand like Nokia, that often offered android one devices has now low to zero interest from developers? It's not polemic, I am just curious
Click to expand...
Click to collapse
because HMD just keeps on locking down everything, and tries to stop people from even unlocking the bootloaders by using broken bootloaders for retail units.
Hikari_Calyx once wrote a whole article on Medium on why it's stupidly hard to unlock the retail units (that are made by HMD), but TL;DR: HMD locks the bootloaders even further every time a new security/feature update is released to its phones by itself, and it even janks the code that makes up the phones' bootloaders, forcing people to use prototype ABL images to unlock the phones.
The fact that you even need prototype/unreleased models of the damn retail units to unlock those units themselves is stupid enough...
As for the older models (e.g: 8 PureView, or 6.1, or whatever before 2021-or-so, I suppose? because there are exceptions, like the G10/G20) though, they're fine. All you need is an unlock key (though, unfortunately, you have to buy the key...), and adb, then use the unlock key, and you're done! Nokia even provided a bootloader unlocking service before (although, they only offered it for a limited time, and it doesn't even work across all of their phones! - they only supported the Nokia 8, and the phone had to run on Android 8 with an old security patch, or else they wouldn't allow the unlocking!)
alegatorul said:
Anyone managed to enable boot loader access? Mine had already A13 (funk it) with oem function access disable (grey) in developer mode
Click to expand...
Click to collapse
that option is useless. Ignore that.
AltFantasy said:
because HMD just keeps on locking down everything, and tries to stop people from even unlocking the bootloaders by using broken bootloaders for retail units.
Hikari_Calyx once wrote a whole article on Medium on why it's stupidly hard to unlock the retail units (that are made by HMD), but TL;DR: HMD locks the bootloaders even further every time a new security/feature update is released to its phones by itself, and it even janks the code that makes up the phones' bootloaders, forcing people to use prototype ABL images to unlock the phones.
The fact that you even need prototype/unreleased models of the damn retail units to unlock those units themselves is stupid enough...
As for the older models (e.g: 8 PureView, or 6.1, or whatever before 2021-or-so, I suppose? because there are exceptions, like the G10/G20) though, they're fine. All you need is an unlock key (though, unfortunately, you have to buy the key...), and adb, then use the unlock key, and you're done! Nokia even provided a bootloader unlocking service before (although, they only offered it for a limited time, and it doesn't even work across all of their phones! - they only supported the Nokia 8, and the phone had to run on Android 8 with an old security patch, or else they wouldn't allow the unlocking!)
Click to expand...
Click to collapse
It's sad that Nokia so fiercely fights people that would like to use android "open" as it should be :/
phaleg said:
It's sad that Nokia so fiercely fights people that would like to use android "open" as it should be :/
Click to expand...
Click to collapse
nah, blame HMD for that.
Nokia is trying to distance itself from its past with their legendary phones (like the N95, E95, N97, 3310, and soooo much more!) now, starting from when they redesigned their logo to a more.... minimalistic look, I guess? and their booths in tech events (e.g: CES) now market their IoT tech, routers, and whatnot...
As for HMD, though, they'll keep on using the old logo, because muh homage to le legendary phones and all that, blah blah. (even though their "new" N95 prototype (you can view it in MrMobile's video about the old Nokia N95) is just essentially very uniform (with just a kickstand built into the camera unit, and speakers that slide out from the left side of the phone....))
HDM or Nokia, logic is the same, it is strange to be so stricth about modding android from a company that used to produce devices with Android one (if I am not mistaken, was the type of android very stock without producers modifications in the SW)
Right, now back as we should on topic..
How did you manage to unlock the bootloader & install twrp or similar app?
alegatorul said:
Right, now back as we should on topic..
How did you manage to unlock the bootloader & install twrp or similar app?
Click to expand...
Click to collapse
I don't know if my guide will also work for your device (though, I suspect it'll still work with the XR20, since all you have to do is flashing the ABL, then do the unlocking commands and all), but here's my guide on how to unlock the bootloader.
Do note, however, that my guide is for a different device (the X10), so it has a few differences here and there, from the XR20 (the unlock commands, and the ABL files). Hikari_Calyx has already given you the commands and files in his post, so just grab that from there.
As for TWRP, you'll have to port the recovery to your phone, which means learning programming and dealing with image layouts and whatnot...
phaleg said:
HDM or Nokia, logic is the same, it is strange to be so stricth about modding android from a company that used to produce devices with Android one (if I am not mistaken, was the type of android very stock without producers modifications in the SW)
Click to expand...
Click to collapse
hahaha, nah, just because a phone runs Android One, doesn't mean its manufacturer will do such a thing. Android One is just the software/operating system part of the phones, and as for the bootloader (which is in the firmware part of the phone), they can just modify it however they want, for the sake of "security" and "stability" and blah blah blah.
It's just like if PC motherboard manufacturers like MSI and ASUS lock people to just using Windows, without any capabilities to use other OSes (e.g: Linux), then claim that they haven't done any modifications to the OS.
AltFantasy said:
hahaha, nah, just because a phone runs Android One, doesn't mean its manufacturer will do such a thing. Android One is just the software/operating system part of the phones, and as for the bootloader (which is in the firmware part of the phone), they can just modify it however they want, for the sake of "security" and "stability" and blah blah blah.
It's just like if PC motherboard manufacturers like MSI and ASUS lock people to just using Windows, without any capabilities to use other OSes (e.g: Linux)
Click to expand...
Click to collapse
Cheers mate.
I'll try with unblocking...
Anyway, the phone is 1 month old under warranty still