Database Users

SBF/Bootloader Unlocking Blocked on New Atrix

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

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

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

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

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

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

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

i replied on the other forum

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

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

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

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

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

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

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

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

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

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

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

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

LG G4 (all variants) Unlock and Root Discussion/News (ONLY)

Hoyo folks.
So I'm sure you've all seen the plethora of "Do we haz root?" "How 2 unlok?" "unlok guide here"(which doesn't work) ect. Here in this thread I will attempt to summarize the current status of Unlock, Custom Recovery, and Root for each model.
Some of our devs now have Devices in hand, THANK YOU TO ALL THAT HAVE DONATED! It REALLY helps the entire G4 community! Now we wait with baited breath. (No pressure guys)
So without Further ado, here is a list of the status of all devices.
CURRENT Unlock/Recovery/Root Status, in order of success:
H815 (Europe Open model ONLY) -
Unlocked? - YES (Via LG's Official Unlocker)
Custom Recovery? - YES (TWRP info)
Root? - YES (Root Info)
NOTE: LG's offcial unlocker is a PERMANENT change. You cannot Re-lock, if you wanted to send in for a warranty claim. If you aren't willing to do that, lets wait and see if the dev's efforts will pay off with a more friendly unlock (which it may or may not)
H815 (Asia) -
NO to all - "adb reboot bootloader" gets into bootloader screen, locked
H815 (USA) -
NO to all - "adb reboot bootloader" gets into bootloader screen, locked
H815 (France) -
NO to all - "adb reboot bootloader" gets into bootloader screen, locked
H815TR (Turkey) -
NO to all - "adb reboot bootloader" gets into bootloader screen, locked
H818P (Thailand) -
NO to all - "adb reboot bootloader" gets into bootloader screen, locked
H818N -
NO to all - "adb reboot bootloader" gets into bootloader screen, locked
H811 (T-Mobile) -
NO to all - and "adb reboot bootloader" doesn't work
H810 (AT&T) -
NO to all - and "adb reboot bootloader" doesn't work
LS991 (Sprint) -
NO to all - and "adb reboot bootloader" doesn't work
F500S -
NO to all - and "adb reboot bootloader" doesn't work
F500K -
NO to all - and "adb reboot bootloader" doesn't work
F500L -
NO to all - and "adb reboot bootloader" doesn't work
VS986 (Verizon) -
No to all - and "adb reboot bootloader" doesn't work, AND no "Enable OEM Unlock" in developer settings.

I suggest editing the thread title to be more concise/official since that is the intent of this thread:
Something like "LG G4 (all variants) Root Discussion/News"

After OEM Unlocking in Development settings and rebooting, TMO G4 reboots only after adb reboot bootloader. Anybody confirm this for TMO G4? We need root first!

For any one that ones the source code is available from LG.
T-Mobile
International
Both kernels are compile-able with a little finagling.
On Root:
From what I can see in the International code is there are the defprefs for all of the p1 versions, and it doesn't "Appear" to have ping pong patched.
I have heard "rumors" that jcase , autoprime and thecubed, are working on a root for the device, but I have not heard from either of them. They did just release pingping v6 which supports the M9, a 64-bit kernel, meaning they have made one that works with the 64-bit linux kernel. For any one curious about their progress you can always check them out on twitter. For those of you posting about root and such, you can always see if there is anything you can do to support them in their efforts.
Thanks for making the thread, I think this phone will be a fun one, and I do expect to see some great things happen.
Have a good day all!

H818P Thailand can use adb reboot boot loader

MicroMod777 said:
After OEM Unlocking in Development settings and rebooting, TMO G4 reboots only after adb reboot bootloader. Anybody confirm this for TMO G4? We need root first!
Click to expand...
Click to collapse
Thanks for confirming. Same behavior on my TMo G4.

Not as skilled as some but I do currently maintain the HTC One M8 for DirtyUnicorns.
I have my G4 pre-ordered from Verizon. It has shipped today and current tracking has it arriving Tuesday 6/2. If no one beats me to it, I will post at least the basics of how that variant functions in terms of adb and fastboot. Anything else needed I will gladly try to provide from the VZW variant.

Ok, so I'm I correct that its possible to root (when available) without it being unlocked? And with just root you could run apps like Titanium but you couldn't install a recovery or different rom while it's still locked?

NCguy said:
Ok, so I'm I correct that its possible to root (when available) without it being unlocked? And with just root you could run apps like Titanium but you couldn't install a recovery or different rom while it's still locked?
Click to expand...
Click to collapse
Yes

NCguy said:
Ok, so I'm I correct that its possible to root (when available) without it being unlocked? And with just root you could run apps like Titanium but you couldn't install a recovery or different rom while it's still locked?
Click to expand...
Click to collapse
Correct. Having root access to the operating system and having a unlocked bootloader are two different things.

barcodelinux said:
Correct. Having root access to the operating system and having a unlocked bootloader are two different things.
Click to expand...
Click to collapse
So it sounds like without the needed file from LG this is not going to be a developer friendly phone?

NCguy said:
So it sounds like without the needed file from LG this is not going to be a developer friendly phone?
Click to expand...
Click to collapse
I know with the last LG I had, the Optimus L90, there was a LAF partition the you had to zero out to get to fastboot. Once that was done, you could:
Code:
fastboot oem unlock
Now this was on a T-Mobile device, and T-Mobile is known for not locking bootloaders. I don't remember having an unlock.bin file, but I could be mistaken.

NCguy said:
So it sounds like without the needed file from LG this is not going to be a developer friendly phone?
Click to expand...
Click to collapse
Well we have 14 days to return it if LG doesn't give us what we need!

MicroMod777 said:
Well we have 14 days to return it if LG doesn't give us what we need!
Click to expand...
Click to collapse
That's true. I actually haven't purchased mine yet but I had high hopes for this device. Was going to be my first carrier-supplied phone. I guess I'll wait for the oneplus 2 if this doesn't get sorted out.

Has anyone been able to get:
Code:
adb devices
I keep getting error: device not found when trying to talk to my G4.
Yes, I have adb set up correctly.
Yes, I have tried different USB cables, including the stock white LG cable.
Yes, I have updated the SDK Tools to 24.3 (latest) and Android 5.1.1. I can get adb to talk to my N7, S4, and my M8 fine. Just not my G4.
Yes, I have USB debugging enabled on the phone.

barcodelinux said:
Has anyone been able to get:
Code:
adb devices
I keep getting error: device not found when trying to talk to my G4.
Yes, I have adb set up correctly.
Yes, I have tried different USB cables, including the stock white LG cable.
Yes, I have updated the SDK Tools to 24.3 (latest) and Android 5.1.1. I can get adb to talk to my N7, S4, and my M8 fine. Just not my G4.
Yes, I have USB debugging enabled on the phone.
Click to expand...
Click to collapse
You need to install the LG device drivers first

has anyone tried to get into the bootloader on linux? a couple phones i had, you had to use sudo, then type the absolute path to platform-tools, even if you open terminal within the sdk, I.E.,
sudo /home/username/SDK/platformtools/fastboot oem unlock " or adb reboot-bootloader"
sometimes had to use su, im sure you could do the same on windows.
anyway worth a shot.

H815 - International variant here with me can officially use adb reboot bootloader
fw: V.10A

So far i got this but after this pc won't recognize phone have to reboot
{
"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"
}
https://imageshack.us/i/exlSOF19j

Worked for me on my LG-H815... It's possible to check the status of the bootloder.
Mine says it's locked. Now there's an option to: "fastboot flash unlock unlock.bin"
But where is the unlock.bin file?

Verizon 2nd Gen moto E 5.1 update(option to unlock bootloader)

{
"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"
}
Seems like our bootloader can be unlocked now via developer options. Do y'all think we can get root soon?

Thats in the 5.0.2 dev options as well, still doesnt allow

wait, so the verizon model does NOT have a root option? crap. guess i'll be returning mine for another carrier
does any other phone carrier have this problem? or is it just verizon? cause im just mostly getting the phone to use as a media player device but I prefer to still have root.

Get the Boost variant, it has root.
Sent from my XT1528

Will boost version work with a Verizon SIM and Verizon LTE?

wpbear said:
Will boost version work with a Verizon SIM and Verizon LTE?
Click to expand...
Click to collapse
No, it will not. It will also not work with domestic GSM networks.

does anyone know if the Sprint version has root? It seems the only colour boost has is white and i really dont want a white phone

it's unlocked going to try an root ill post back with result after you take the update immediatley go into dev hit oem unlock then go into fastboot an it will be unlocked i messed up an rebooted it an it factory locked itself so

So were you able to root it?

It didn't have the device lock on it so I'm assuming but I couldn't do it due to reboot n relocking bootloader is my presumption
Sent from my XT1528 using XDA Free mobile app

So the method you are suggesting is to download and take the 5.1 update. After it updates and boots up go to developer mode and check OEM Unlock. Then fastboot and it should show that the boatloader is unlock? Is that correct? Then in fastboot flash recovery.img (TWRP) and then using TWRP flash SuperSU, right?
---------- Post added at 01:08 AM ---------- Previous post was at 12:56 AM ----------
@Soldier1184 - I guess my unit was up for two updates. One to update to the latest 5.0.2 and then another to 5.1. Before I updated to the latest 5.0.2 I had checked off on the OEM Unlock box then took the 5.0.2 update. After the update and the next boot up I checked OEM Unlock and it was still checked. I then went into fastboot but it still says that it was locked. So I have a few questions. 1) Should I not let it boot up after the update and go into fastboot first? 2)Or the method you are suggesting only works after the 5.1 update? I know you don't have a definitive answer to those but I was just wondering what you think and since I haven't updated to 5.1 yet I can give a test.

When I did it it was unchecked then I updated after that immediately checked oem unlock my fastboot didn't state locked or unlocked it wasn't even there then I rebooted again after I unchecked it it stated locked so I switched oem on again in dev menu still no go so since I can't test it again take the update do the steps n pm back with results if it doesn't say device locked in-between charging n USB thing then reboot leave oem checked n fastboot again n post back
Sent from my XT1528 using XDA Free mobile app

No go...I install the update...upon rebooting I hurry and got it go into fastboot but it already says "Locked"....I reboot then got into developer tools and rechecked OEM Unlock...reboot into fastboot...still says "Locked"...oh well...guess I'll have to wait. The worst thing is that I just cracked my RAZR Maxx's screen and now I have no way to tether....

im very frustrated trying to restore factory and relock bootloader

I tried the searches, i tried the restore to stock, i tried windroid, i tried everything.
i have a moto x pure with originally 6.0.1 but it was with a unlocked bootloader. now i want to restore it back. i tried everything i could find to relock it and now i am trying the system images from motorola but i keep getting this ******* response
tail_XT1575_MPH24.49-18_18\CLARK_RETUS_MPH24.49-18_18_retus_US>fastboot flash
rtition gpt.bin
target reported max download size of 536870912 bytes
sending 'partition' (32 KB)...
OKAY [ 0.003s]
writing 'partition'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.354s
can someone please help me. the bat all files are not working and now manually isnt working either. step by step instructions would be appriciated. ive been trying at this for 5 hours now

You cannot lock the bootloader again. Once it's unlocked it's a done deal. Warranty wise
Sent from my XT1575 using Tapatalk

You can relock... But there is no reason to. If it is not locking you are not 100% stock. I think there was discussion on this in the firmware thread.

Problem with 'gpt.bin' not flashing is you are trying to downgrade, regardless of an unlocked bootloader or not, you cannot downgrade the partition table (gpt.bin is the partition table). If you want to relock you need to factory default in recovery, flash the stock ROM that is the same or newer version than you have installed (you cannot downgrade), and you must use the 'fastboot oem lock begin" commands to start and 'fastboot oem lock' to end the flashing sequence.
Although this process works, it isn't really relavent and means nothing because Moto will always know it was unlocked (the generation of the unlock token voided your warranty, whether unlocked or not), your bootloader status will never return to 0 and your software status will always show modified.
Be aware that we have seen a few Moto G 2015 devices get bricked by this, if somehow the bootloader version doesn't match the ROM (can happen... we have seen it more than once) due to flashing multiple stock images or failed/improper OTA flash, and the bootloader gets locked it becomes insta-brick and won't go past the bootloader and won't unlock again. It seems the only way out is to flash a newer official stock image if/when one becomes 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"
}
Sent from my 0PJA2 using Tapatalk

So you either haven't flashed anything, or you returned to stock and took an OTA and it went official again (lucky you, it's inconsistent).
Bootloader status can never be returned to 0.
Sent from my Motorola XT1575 using XDA Labs

Jessooca said:
I have the latest July update (minor sec update) my phone is stock and I have the latest firmware, spoke to Tom (rootjunky) and he was stumped as well. I have the same issue and I'm not downgrading anything, nor flashing an older firmware, yet still have your same issue. Unlocked the bootloader and that didn't help either.
Probably have rootjunky remotely look at my XT1575 and see if he can figure it out..... I will let you know the issue when we know.
Curious.... Does your phone always startup and go into that bootloader/fastboot screen??
Click to expand...
Click to collapse
It did for a bit not but anymore. It was doing bootloops but when I put back twrp and reflashed a ROM on XDA it stopped doing it
Sent from my 0PJA2 using Tapatalk

ok an update.
so i downloaded from here http://www.gammerson.com/2015/09/restore-stock-firmware-rom-in-moto-x-style-pure-2015.html which is the same as a link from XDA and already had the download.
so i flashed it three times to assure it was flash entirely.
1) first time it just flashed the software
2)second time the radios started to work
3) third time was just to make sure it worked properly
it started to change the bootloader date and returned the unlocked bootloader message. after i did that, everything worked the way it was supposed to minus the bootloader lock.
it gave me a notification that there is an update available for marshmallow, downloaded and flashed automatically so i think im in good hands so far. i guess everything is ok now and after nougat, ill just root it back again.

Jonathanlc2005 said:
ok an update.
so i downloaded from here http://www.gammerson.com/2015/09/restore-stock-firmware-rom-in-moto-x-style-pure-2015.html which is the same as a link from XDA and already had the download.
so i flashed it three times to assure it was flash entirely.
1) first time it just flashed the software
2)second time the radios started to work
3) third time was just to make sure it worked properly
it started to change the bootloader date and returned the unlocked bootloader message. after i did that, everything worked the way it was supposed to minus the bootloader lock.
it gave me a notification that there is an update available for marshmallow, downloaded and flashed automatically so i think im in good hands so far. i guess everything is ok now and after nougat, ill just root it back again.
Click to expand...
Click to collapse
Try windroid tool kit it works except for root but it does have a bootloader relock to it.

[N00b][PRA-LX1] I'm confused and need help for custom ROMs installation.

Hello everyone. I've searched the form without any results tho.
I have a Huawei P8 Lite 2017 (PRA-LX1) and I wanted to flash it up with a LineageOS unofficial ROM.
Now, I have a bit of experience in flashing phones back in the days (I flashed a SII, a SIII, a J1, Galaxy Core) and it was SO SIMPLE.
I'm confused right now, i was going to flash TWRP on my phone when i saw this unlock bootloader thing and i mean, how do I do that?
Apparently I have to pay 4€ for this DC unlocker (although, i checked their website and I don't know what to select to get this bootloader code, help me please), but i don't understand what should I do with that code once i get it.
After doing "something" i'll be able to flash TWRP on my phone and go ahead with the simple flashing Roms+gapps like always...
The point is:
- What is the use of that code? Where should i put it?
- Is is safe to install an unofficial version of TWRP (i haven't find any at all for my model tbh, unofficial neither, help me please)
sorry for my bad english and thanks in advance if you'll help me ^_^ Have a nice day!

Huawei stopped sending bootloader unlock codes which are necessary to have an unlocked bootloader. DC Unlocker can give you this code for credits. (Search for it in Google i think there are tutorials for this)
Once you got the BL unlock code, you need to reboot to fastboot then in cmd you need to type: fastboot oem unlock bl unlock code. This will wipe your data so do a backup. About TWRP, if i were you, i would use the latest whatever official/unofficial recovery which can be flashed in fastboot by command: fastboot flash recovery recovery.img (if i'm not mistaken)
Good luck! :good:

_MartyMan_ said:
Huawei stopped sending bootloader unlock codes which are necessary to have an unlocked bootloader. DC Unlocker can give you this code for credits. (Search for it in Google i think there are tutorials for this)
Once you got the BL unlock code, you need to reboot to fastboot then in cmd you need to type: fastboot oem unlock bl unlock code. This will wipe your data so do a backup. About TWRP, if i were you, i would use the latest whatever official/unofficial recovery which can be flashed in fastboot by command: fastboot flash recovery recovery.img (if i'm not mistaken)
Good luck! :good:
Click to expand...
Click to collapse
Thanks for your reply! Please see the image below for what i'm going to say next.
I was going to buy some credits to unlock the bootloader, as i've read in another thread, it only requires 4€ (4 credits). Although, I don't kno which one of these two options is the correct one... Can anyone help me with that?
{
"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"
}
Also, thanks for the TWRP tip, I'll try to find one which is compatible with my system :good:

Chueven said:
Thanks for your reply! Please see the image below for what i'm going to say next.
I was going to buy some credits to unlock the bootloader, as i've read in another thread, it only requires 4€ (4 credits). Although, I don't kno which one of these two options is the correct one... Can anyone help me with that?
Also, thanks for the TWRP tip, I'll try to find one which is compatible with my system :good:
Click to expand...
Click to collapse
I don't know which one to use, as i didn't use that method.
EDIT: Just get 4 credits, if i'm not mistaken there's only one option to get the bl unlock code in the app and that's 4 credits.
I could only find one TWRP for this device: LINK
Made by @Dil3mm4
From this thread

_MartyMan_ said:
I don't know which one to use, as i didn't use that method.
EDIT: Just get 4 credits, if i'm not mistaken there's only one option to get the bl unlock code in the app and that's 4 credits.
I could only find one TWRP for this device: LINK
Made by @Dil3mm4
From this thread
Click to expand...
Click to collapse
I just realized it doesn't matter, i just have to pay 4 credits and all the possible options will unlock once i pay ^^
So after i read the bootloader code, how should i use it?

Chueven said:
I just realized it doesn't matter, i just have to pay 4 credits and all the possible options will unlock once i pay ^^
So after i read the bootloader code, how should i use it?
Click to expand...
Click to collapse
This will wipe everything from your phone!
Reboot to fastboot mode then in cmd type: fastboot oem unlock bootloadercodehere

_MartyMan_ said:
This will wipe everything from your phone!
Reboot to fastboot mode then in cmd type: fastboot oem unlock bootloadercodehere
Click to expand...
Click to collapse
AHHHHHHH! i get it now! damn that's super simple.... thanks a lot! I'll try it when i get money on paypal really really thanks

Chueven said:
AHHHHHHH! i get it now! damn that's super simple.... thanks a lot! I'll try it when i get money on paypal really really thanks
Click to expand...
Click to collapse
You’re welcome :good:

Chueven said:
Thanks for your reply! Please see the image below for what i'm going to say next.
I was going to buy some credits to unlock the bootloader, as i've read in another thread, it only requires 4€ (4 credits). Although, I don't kno which one of these two options is the correct one... Can anyone help me with that?
Also, thanks for the TWRP tip, I'll try to find one which is compatible with my system :good:
Click to expand...
Click to collapse
Unlocked it recently you go to buy account number credits 4 than go to server put in the username you chose and the code they send you go to unlocking show bootloader code than copy it