Database Develop

Huawei P10 Lite Bricked? Need help please.

Hello all,
First of all I looked for a (sub) forum for the P10 Lite, but I can't seem to find it. If a admin/mod thinks this post should be placed elsewhere, feel free to move it.
Ok, now on to the problem I'm having with my P10 Lite (WAS-LX1A model)...
The phone is running the stock B102 firmware, I've unlocked the bootloader with the code I got from Huawei, installed TWRP and rooted the phone, all was working just fine.
Then, last saturday (June 24, 2017) there was an OTA update to B131 available, tried to install it but it failed (nothing was installed btw, it never got to then point where the OTA did anything, phone would just reboot).
So after some searching and in a lapse of judgement I decided to (re)lock the bootloader thinking that was what kept the update from installing (command: sudo fastboot oem relock <code>).
And that's where my problem gets in.
Now I have a phone which only can only get into:
1.) Huawei eRecovery: Only options I have in eRecovery are: "Download latest version and recovery", "Reboot" and "Shutdown". No option to reset to factory or anything like that. "Download latest version and recovery" fails everytime, stating: "Failed to get package info from server". Gave my phone a static DHCP lease and even put it in DMZ on the router (just in case NAT/firewall was interfering), but that didn't help at all. Rebooting or shutdown will just put the phone back into eRecovery as soon as it's booted.
2.) Emergency/EDL: This is the mode where you're supposed to put the firmware you want to flash in the "dload" folder on sd-card. Tried that too, but it gets to about 5% and fails (tried B120, B123 and B131 update files, none work). When the phone gets into this mode it's also available to ADB. However, something seems to have changed dramaticly as I no longer seem to have any permissions on the phone. "adb devices" shows my phone but it also says "unauthorised". As soon as I try to do anything that requires root priviledges (like: "adb root" or "adb shell") I get an error stating: "This adb server's $ADB_VENDOR_KEYS is not set". Clearly that means there's an issue regarding the .pub keys on client/host side not being the same. Since I cannot pull anything from, or push anything to, my phone I don't know how I can fix this... And since I'm getting this message on the same machine that I used to flash TWRP on the phone earlier (which worked just fine), it seems to me this problem exists on the phone-side.
3.) Fastboot & rescue: fastboot finds my phone just fine, yet it flatout refuses all meaningful commands (only basic commands like reboot work) with the error: "FAILED (remote: Command not allowed)". Some searching tells me this is because the bootloader is locked and that's exactly what my phone shows on it's screen when it's in fastboot mode: "PHONE Relocked" and "FRP Lock". However fastboot command: "fastboot oem get-bootinfo" returns: "(bootloader) unlocked". This confuses me, a lot; if the bootloader is unlocked then what is preventing me from flashing anything? Trying to unlock the bootloader again through fastboot (fastboot oem unlock <code> / fastboot oem unlock "<code>") gives the "FAILED (remote: Command not allowed)" error. Trying to lock the bootloader again (fastboot oem relock <code> / fastboot oem relock "<code>") gives error: "FAILED (remote: stat not match)". Obviously I cannot flash anything from fastboot anymore.
Tried all I can think of on 2 linux machines and 1 Windows 7 machine, all 64-bit, allthough 1 of the linux machine is multi-architecture so it runs 32-bit too (not related to this issue, needed 32-bit for WINE). This just to rule out an issue with my machine. All 3 machines act exactly the same though which makes me (strongly) believe the issue resides on the phone.
Trying to recovery in HiSuite (newest version) doesn't work either, it just tells my my phone isn't supported, even though it does detect my phone when it's in fastboot mode.
Nothing has been flashed, so this is not a case of a flash gone wrong, it just looks like I'm locked out of my own phone and for the life of me I cannot figure out how to get back in. And there's no way to boot into system anymore, so I cannot check/change "OEM Unlock" and "ADB Debugging" settings in the phone developers options
.
Any help/advice would be greatly appreciated! I'm stuck, Huawei customer service only tells me to do a factory reset, which I can't, and when I tell them that's not possible all becomes awfully quiet on their end (they don't respond to my mails anymore). I simply can't think of anything I could try to fix this, spend the last 5 days searching the web but nothing seems to work. Maybe some Android-guru's have some suggestions (I'm certainly open to suggestions! ).
Thanks in advance.
Info:
- phone: Hauwei P10 Lite, model: WAS-LX1A, firmware: WAS-LX1AC432B102
- (main) laptop: HP Probook running Arch linux (64bit), uname: "Linux probook 4.11.6-3-ARCH #1 SMP PREEMPT Thu Jun 22 12:21:46 CEST 2017 x86_64 GNU/Linux".
- Android SDK version 26. Package named: "aur/android-sdk-platform-tools r26.0.0-1 (1155, 9.20)" Which can be found on Arch's AUR. (I am aware I need to run fastboot as "sudo", fastboot cannot do anything without sudo priviledges).
Edit: Tried some fastboot commands with regards to "FRP Unlock", command: "sudo fastboot oem frp-unlock" returns: "FAILED (remote: oem_frp_check_password failed! Error = -1)" not sure what password is required here to be honest and "sudo fastboot oem frp-erase" returns: "FAILED (remote: Command not allowed!)".

OTA update didn't install because of custom recovery, not because bootloader was unlocked. You can unlock bootloader again and try again.. Dload for some reason won't work anymore on newer firmwares.. At the end you can always restore phone with DC-Phoenix tool, just flash stock firmware you had on the phone.

MobileTechArena said:
OTA update didn't install because of custom recovery, not because bootloader was unlocked. You can unlock bootloader again and try again.. Dload for some reason won't work anymore on newer firmwares.. At the end you can always restore phone with <snip> cannot post URL's yet <snip> tool, just flash stock firmware you had on the phone.
Click to expand...
Click to collapse
Thank you, MobileTechArena, for your time/effort,
That's what I thought regarding bootloader/recovery, however I thought of it too late.
Unlocking to bootloader again doesn't work (command: sudo fastboot oem unlock "16-digit-code"), I get the "FAILED (remote: Command not allowed)" error. Tried it with bootloader code as a string, and as "code". Both don't work, on the same machine I used previously to unlock the bootloader in the first place. The unlocking working but after giving the relock command everything seems to get blocked, even though "sudo fastboot oem get-bootinfo" still tells me the bootloader is unlocked.
With regards to DC-Unlocker, I don't have a stock B102 firmware, it simply cannot be found anywhere online. I managed to get a full TWRP backup of the B102 firmware from some helpful people on this site (on someone else's thread), but seeing as how I'm no longer able to boot into TWRP, I don't think that TWRP backup is going to do me any good. Oldest firmware I can find online is B120, which is newer than the firmware on my phone.
Read somewhere on Huawei Q&A section that they removed the "dload" method because of security risks, so yeah that method is DOA. Really sad they did this, feels like that could've saved me.
Also gave Huawei's Fastboot erase tool (version: 1006) a try. It detects my phone just fine but it cannot unlock FRP. If I use the tool to erase FRP it reboots the phone -> fails. doesn't make any changes.
Am I right in thinking it's Huawei's FRP that's preventing fastboot/adb commands?

GuessThisIsMe said:
Thank you, MobileTechArena, for your time/effort,
That's what I thought regarding bootloader/recovery, however I thought of it too late.
Unlocking to bootloader again doesn't work (command: sudo fastboot oem unlock "16-digit-code"), I get the "FAILED (remote: Command not allowed)" error. Tried it with bootloader code as a string, and as "code". Both don't work, on the same machine I used previously to unlock the bootloader in the first place. The unlocking working but after giving the relock command everything seems to get blocked, even though "sudo fastboot oem get-bootinfo" still tells me the bootloader is unlocked.
With regards to DC-Unlocker, I don't have a stock B102 firmware, it simply cannot be found anywhere online. I managed to get a full TWRP backup of the B102 firmware from some helpful people on this site (on someone else's thread), but seeing as how I'm no longer able to boot into TWRP, I don't think that TWRP backup is going to do me any good. Oldest firmware I can find online is B120, which is newer than the firmware on my phone.
Read somewhere on Huawei Q&A section that they removed the "dload" method because of security risks, so yeah that method is DOA. Really sad they did this, feels like that could've saved me.
Also gave Huawei's Fastboot erase tool (version: 1006) a try. It detects my phone just fine but it cannot unlock FRP. If I use the tool to erase FRP it reboots the phone -> fails. doesn't make any changes.
Am I right in thinking it's Huawei's FRP that's preventing fastboot/adb commands?
Click to expand...
Click to collapse
I think it is because of locked FRP, you can still try with DC-Phoenix with newer firmware. I had the same problem on P8 Lite 2017, Couldn't find B106 that i had on the phone anywhere, but successfully flashed B110.
EDIT: also check under filelist of the firmware that firmware for sure is for your region.

MobileTechArena said:
I think it is because of locked FRP, you can still try with DC-Phoenix with newer firmware. I had the same problem on P8 Lite 2017, Couldn't find B106 that i had on the phone anywhere, but successfully flashed B110.
EDIT: also check under filelist of the firmware that firmware for sure is for your region.
Click to expand...
Click to collapse
Thank you for the info, shall have another look at the firmware (or more precisely, it's region). It's the EU version I'll need that much I know.
Also did some looking into why Huawei's eRecovery isn't working, so I turned on my Kali Linux machine and did some 'wiresharking'.
Seems eRecovery is looking for something at ip: 54.229.89.249.
A Whois query shows this ip belongs to Amazon's AWS.
However, pinging the IP shows that it's not online, so no wonder why eRecovery isn't working (nice one Huawei! ).

GuessThisIsMe said:
Thank you for the info, shall have another look at the firmware (or more precisely, it's region). It's the EU version I'll need that much I know.
Also did some looking into why Huawei's eRecovery isn't working, so I turned on my Kali Linux machine and did some 'wiresharking'.
Seems eRecovery is looking for something at ip: 54.229.89.249.
A Whois query shows this ip belongs to Amazon's AWS.
However, pinging the IP shows that it's not online, so no wonder why eRecovery isn't working (nice one Huawei! ).
Click to expand...
Click to collapse
Yes, if it's eu then eu firmware is what you need. As for the eRecovery i have no idea why its looking for something on that ip. Huawei definitely need's to make restoring devices simpler.
---------- Post added at 09:36 PM ---------- Previous post was at 09:19 PM ----------
Can you connect device with HiSuite in fastboot mode? You could use this REDLOTUS tool to bypass eRecovery and flash firmware.

MobileTechArena said:
Yes, if it's eu then eu firmware is what you need. As for the eRecovery i have no idea why its looking for something on that ip. Huawei definitely need's to make restoring devices simpler.
---------- Post added at 09:36 PM ---------- Previous post was at 09:19 PM ----------
Can you connect device with HiSuite in fastboot mode? You could use this <snip> tool to bypass eRecovery and flash firmware.
Click to expand...
Click to collapse
Ok, l did get the right firmware (EU region), so that wasn't the issue.
Tried the REDLOTUS tool (thanks for that link btw, seems like a promising project), but alas it doesn't seem to work for me.
Got node js/npm installed just fine, it works, manages to get the firmware and everything, listens for HiSuite and manages to point HiSuite to local host to look for firmware there (like it should according to REDLOTUS' Readme).
Unfortunately, HiSuite doesn't give me the option to update firmware, only the systemrecovery button isn't greyed out, and systemrecovery tells me my device isn't supported. I can see on my phone's screen "rescue mode enter..." when I select systemrecovery in HiSuite, but nothing else happens.
Seems like REDLOTUS might work for me once the author manages to get it to work with eRecovery instead of HiSuite (apparantly that's being worked on atm).

hi i'm from france and i have exactly the same problem as you
the only difference is that i've "PHONE Unlocked" and "FRP Unlock" but not all of the fastboot commands works
i'm trying just right now to flash BOOT.img, RECOVERY.img and SYSTEM.img
hope it will work, sorry for my bad english

Radnaksi98 said:
hi i'm from france and i have exactly the same problem as you
the only difference is that i've "PHONE Unlocked" and "FRP Unlock" but not all of the fastboot commands works
i'm trying just right now to flash BOOT.img, RECOVERY.img and SYSTEM.img
hope it will work, sorry for my bad english
Click to expand...
Click to collapse
If your phone reads "PHONE Unlocked" and "FRP Unlock", then lucky for you, you don't have anything near my problem.
First of, if you do a: 'fastboot devices' command, does it show your phone?
Can you tell me if the following commands work, and what they return?
- fastboot oem get-bootinfo
- fastboot oem get-lock-state
- fastboot oem lock-state info
If you run Linux you'll need to "sudo" the fastboot commands.
You have enabled ADB-debugging on the phone right?
Edit: Can you still get into the stock recovery? To get there first turn the phone completely off. Then hold Volume Down (-) and Power buttons till you see the Huawei logo, then release both buttons. From stock recovery you could try a factory reset (DO NOT DO THIS IF YOU HAVE TWRP INSTALLED!!!).

hi, the phone shows me "FRP Unlock", but when i've done all the commands u gave me and there's an FB Lockstate on: LOCKED
Idk what it is
EDIT: ADB-debugging isn't enabled because i can't boot the phone, and when it started to bootloop that was when i've unlocked the bootloader and someone told me to factory reset the phone, so i think the ADB-debugging isn't enabled anymore
EDIT2: Stock recovery is working

does anyone have a twrp backup for the p10 lite ? it would be faster ....
oh and i have installed the revolution recovery, now i have the mtp and adb functionning, adb shell too, but i still cannot mount /data or /system
looks like /data is empty and unmoutable idk what to do
i can't change fs or wipe the partition pls help

Radnaksi98 said:
does anyone have a twrp backup for the p10 lite ? it would be faster ....
oh and i have installed the revolution recovery, now i have the mtp and adb functionning, adb shell too, but i still cannot mount /data or /system
looks like /data is empty and unmoutable idk what to do
i can't change fs or wipe the partition pls help
Click to expand...
Click to collapse
You can find a full TWRP backup of the B102 firmware in the thread called -> Root p10 "lite" , on page 11 user: stefanwe92 posted a link to it.
Good luck!

Thank you for answering me !
But i've the LX1A, so can i use it ?

Radnaksi98 said:
Thank you for answering me !
But i've the LX1A, so can i use it ?
Click to expand...
Click to collapse
Did/does it have a firmware like: WAS-LX1AC432B102? (the C432 is the important part). If so, then yes you should be fine.
Now beware I base this solely on the fact that there isn't any firmware on HWMT's site for the WAS-LX1C*, only for the WAS-LX1AC*. Google "hwmt" and have a look for yourself (it's in russian, so Google translate will definately help).
If you want to be absolutely sure, I'd suggest contacting user "stefanwe92", he has the phone and has uploaded the firmware, so he should be able to give you the information you need.
I wish I could've tried the TWRP myself, but my phone refuses to load the bootloader, so I can't :crying:

GuessThisIsMe said:
Did/does it have a firmware like: WAS-LX1AC432B102? (the C432 is the important part). If so, then yes you should be fine.
Now beware I base this solely on the fact that there isn't any firmware on HWMT's site for the WAS-LX1C*, only for the WAS-LX1AC*. Google "hwmt" and have a look for yourself (it's in russian, so Google translate will definately help).
If you want to be absolutely sure, I'd suggest contacting user "stefanwe92", he has the phone and has uploaded the firmware, so he should be able to give you the information you need.
I wish I could've tried the TWRP myself, but my phone refuses to load the bootloader, so I can't :crying:
Click to expand...
Click to collapse
I don't really know, on the box it's written WAS-LX1A
But i'm gonna make a backup first with twrp (yes i've successfully unbricked the phone by myself ! It work by half but man it Was hard ! I will try to makes a tutorial for you in french as soon as i can because it's hard for me to speak in english lol, so use a translator !) and then flash the backup you gave me !
I will do this tomorrow because it's late in France and it took me an entier afternoon to semi-unbrick this phone ^^
I will contact you tomorrow with good news i hope !

Radnaksi98 said:
I don't really know, on the box it's written WAS-LX1A
But i'm gonna make a backup first with twrp (yes i've successfully unbricked the phone by myself ! It work by half but man it Was hard ! I will try to makes a tutorial for you in french as soon as i can because it's hard for me to speak in english lol, so use a translator !) and then flash the backup you gave me !
I will do this tomorrow because it's late in France and it took me an entier afternoon to semi-unbrick this phone ^^
I will contact you tomorrow with good news i hope !
Click to expand...
Click to collapse
command: "fastboot oem get-build-number" should tell you exactly which firmware your phone is running.
Congrats on your success!
Regarding your English, it seems just fine to me, I understand you well. And for sure it's better than my French (dropped that subject as quickly as I could in high school ).
Hope to hear from you soon, with a working phone!
Sleep well, btw I live in the same timezone as you (I'm Dutch).

Phone has been brought back to life with the excellent help from the DC-Unlocker team.
MobileTechArena was absolutely right, only DC-Phoenix can save you in a circumstance such as the one I found myself in.
15 bucks well spent, can definately recommend it!!!
Problem solved

GuessThisIsMe said:
Phone has been brought back to life with the excellent help from the DC-Unlocker team.
MobileTechArena was absolutely right, only DC-Phoenix can save you in a circumstance such as the one I found myself in.
15 bucks well spent, can definately recommend it!!!
Problem solved
Click to expand...
Click to collapse
I fixed my bootloop that lasted for almost an month with help of MobileTechArena without DC-Phoenix so I guess we both gonna thank him :laugh:

Carkai said:
I fixed my bootloop that lasted for almost an month with help of MobileTechArena without DC-Phoenix so I guess we both gonna thank him :laugh:
Click to expand...
Click to collapse
Agreed!
Nice people those Irish, some of them like their whiskey a bit too much , but all of the Irish folk I've met in my life have been nothing but kind human beings.
Knew one Irish lad who thought nothing of starting to drink at 8 in the morning, I tell you the drive back home was very interesting (and not at all dangerous :silly.

Radnaksi98 said:
does anyone have a twrp backup for the p10 lite ? it would be faster ....
oh and i have installed the revolution recovery, now i have the mtp and adb functionning, adb shell too, but i still cannot mount /data or /system
looks like /data is empty and unmoutable idk what to do
i can't change fs or wipe the partition pls help
Click to expand...
Click to collapse
I have a identical problem... my phone is stuck in "Huawei eRecovery" screen. Same situation that you had reported (connection fail).
I found a solution to enter in FASTBOOT & RESCUE MODE and i posted in:
https://forum.xda-developers.com/general/general/solution-huawei-p10-lite-alternative-to-t3637311
I also have a TWRP backup... but my problem started when i used it to restore my phone. So i believe that it will not help you. But if you want I can send it to you. My model is a WAS-LX1A (Portugal).
Have you found a solution to your problem?

Need help

Hey guys n girls,
I'm going to root my phone. First off the why? I recently discovered PlayStation remote play and use it on my computer. I was excited to use it on my phone but then found out only Sony phones work I guess... So I read somewhere don't remember, that if I root my phone, I can add Sony files to rooted phone to allow it to use PlayStation remote.
1st phone is moto x 2nd
2nd phone zte maven 2
First phone I use for an actually phone 2nd one is brand new never used.
So I heard I need to use adb and something else I believe. Can someone help me? Once again main reason PlayStation remote play

mike543210 said:
Hey guys n girls,
I'm going to root my phone. First off the why? I recently discovered PlayStation remote play and use it on my computer. I was excited to use it on my phone but then found out only Sony phones work I guess... So I read somewhere don't remember, that if I root my phone, I can add Sony files to rooted phone to allow it to use PlayStation remote.
1st phone is moto x 2nd
2nd phone zte maven 2
First phone I use for an actually phone 2nd one is brand new never used.
So I heard I need to use adb and something else I believe. Can someone help me? Once again main reason PlayStation remote play
Click to expand...
Click to collapse
First you must unlock bootloader from official motorola site.
Google unlock moto x 2014 and do it.
Second you must download adb and fastboot to your pc.
Third with adb flash twrp.
And last flash supersu with tuttorial from xda .
Keep walking.

Thanks. Any chance you can attach links for downloads for PC and also files. If u can add tutorials I can follow those too. I have rooted couple times before but if I do the moto that's my actual phone and I don't want to mess it up. Will it mess with my plan or screw me over in any way? I've only done phones I don't use.
Thanks again for any help

So Ive been reading and need a little help.
1. I have moto x2014 (is it pure edition?)supposedly. (It's at&t white front wooden back 8gb. Believe 5.1.1) I need to know so I can do the first step.
2.downloads to adb and fastboot for PC? I was hoping someone had a link so I know I don't download anything bad.
*Edit* I used this
https://forum.xda-developers.com/showthread.php?p=48915118
3. How to flash? And need the zip packs/files for twrp and SuperSU? (Which I put on root of SD card?)
*Edit*
Also by doing this will my phone operate the same?(no extra step to put kernal/os on?) I just want to know how to root and add Sony software to use the app. Thanks again for anyone's knowledge
*Edit*
I'm having a tough time navigating the forum, thank for the help people

mike543210 said:
So Ive been reading and need a little help.
1. I have moto x2014 (is it pure edition?)supposedly. (It's at&t white front wooden back 8gb. Believe 5.1.1) I need to know so I can do the first step.
2.downloads to adb and fastboot for PC? I was hoping someone had a link so I know I don't download anything bad.
*Edit* I used this
https://forum.xda-developers.com/showthread.php?p=48915118
3. How to flash? And need the zip packs/files for twrp and SuperSU? (Which I put on root of SD card?)
*Edit*
Also by doing this will my phone operate the same?(no extra step to put kernal/os on?) I just want to know how to root and add Sony software to use the app. Thanks again for anyone's knowledge
*Edit*
I'm having a tough time navigating the forum, thank for the help people
Click to expand...
Click to collapse
Here is my help....
Twrp
https://dl.twrp.me/victara/twrp-3.1.1-0-victara.img.html
Moto drivers
https://mobilesupport.lenovo.com/us/en/solution/MS88481
Unloack bootloader
https://motorola-global-portal.custhelp.com/app/standalone/bootloader/unlock-your-device-a
Minimal fastboot an adb
https://androidfilehost.com/?fid=745425885120698566
Here toutorial for the root.
https://forum.xda-developers.com/moto-x-2014/development/root-root-moto-x-2014-android-t3249105

Thank you I will read and try. And as far as if I root the zte maven 2 I would just get the drivers for zte and switch the product name in command lines correct?

First off thanks for your help and anybody else who may contribute.
ive been trying to listen and follow lol. anything with (...) is stuff
i added
First you must unlock bootloader from official motorola site.
Google unlock moto x 2014 and do it.
(the link you added brought my to a page i click next and tryed to sign up
it said i had an account so i signed in with the email on my phone an then it
brought me to a page that wasnt available. So do you have another link or is
there something im missing. im having trouble unlocking it)
Second you must download adb and fastboot to your pc.
(i downloaded
*minimal_adb_fastboot_v1.4.2_setup application
*motoroladevicemanager_2.5.4 application)
Third with adb flash twrp.
(few things.
*adb is just command prompt right?
*flash? i know means install sorta of. do you have command line?
*the link had three things to click on
1.this was on white screen
58337e4962e12d37f740a417601db4e3 twrp-3.1.1-0-victara.img
2. twrp-3.1.1-0-victara disc /image file
3. twrp-3.1.1-0-victara.img.asc /asc file)
And last flash supersu with tuttorial from xda .
(once again, flash? im assuming i just need command line like,
adb install supersu.apk.
*also files i downloaded were
1. update-supersu-v2.76-20160630161323 /compressed zip
2. root-boot-6.0-xt1097-mpes24.49-18-7 /compressed zip)
***So is there any files im missing to root?
How do i unlock my bootloader or whatever it is? (link didnt work for me)
What is flash?(i think install)

it says my device does not qualify to unlock bootloader. so yea I don't want to give up but that killed my hopes. I can get into fasboot flash mode and have boot mode selection menu and it says device is still locked. I got the link to work and used fastboot oem get_unlock_data used their program to have same layout for unlock code and it says your device does not qualify for bootloader unlocking. if anyone can help thanks

mike543210 said:
it says my device does not qualify to unlock bootloader. so yea I don't want to give up but that killed my hopes. I can get into fasboot flash mode and have boot mode selection menu and it says device is still locked. I got the link to work and used fastboot oem get_unlock_data used their program to have same layout for unlock code and it says your device does not qualify for bootloader unlocking. if anyone can help thanks
Click to expand...
Click to collapse
Some variants of the Moto X 2014 cannot be unlocked. Put the phone in Bootloader Mode and:
fastboot getvar all
Copy and save all the info into a Notepad file, then go to the Moto/Lenovo Forums here:
https://forums.lenovo.com/t5/MOTORO...ock-Problems/m-p/3222809/highlight/true#M2654

mike543210 said:
it says my device does not qualify to unlock bootloader. so yea I don't want to give up but that killed my hopes. I can get into fasboot flash mode and have boot mode selection menu and it says device is still locked. I got the link to work and used fastboot oem get_unlock_data used their program to have same layout for unlock code and it says your device does not qualify for bootloader unlocking. if anyone can help thanks
Click to expand...
Click to collapse
What model do you have my friend?
Fot the tutorial ...
First unlock bootloader and install twrp.
All other you can flash them from the twrp recovery and i mean supersu and many more.
From adb can flash stock rom clean.

hey gus I did that command and made a save file in notepad. so just post it?
and pap I believe xt1097

according to ur link gus my phone is not unlockable becaue my cid was 0x001. so yea I guess im giving up thanks guys for your time. im really bummed because I modded and rooted things in the pass and this by far has been the hardest. I figured I could do it manually or a custom firmware would help. if I install twrp somehow as a recovery is there a way to root of that? I just don't get y I cant unlock bootloader. I understand that I cant, but don't get how there isn't a way around it. once again thanks people. this is a bummer...........................

is there any way to get unique_key for the command line?
fastboot oem unlock UNIQUE_KEY

im so annoyed right now that i cant unlock this phone. its ridiculous that i cant unlock it, like seriously please help from anyone. i dont know y i cand get the unique key to unlock my phone. can i call motorola to ask for it? or at&t? i just dont get y i cant unlock it with any method. i know there is someone out there who can help, please spare me some time and help me i beg of u.

u think this will work?
https://forum.xda-developers.com/moto-x-2014/general/root-bootloader-unlock-att-xt1097-5-1-t3309889
or is there a way to make my bootloader unsigned?
if i unlock my phone from at&t would that help?

XT1925-3 OEM Unlock disabled/greyed

Hi!
I'm from Brazil and I bought a Moto G6 XT1925-3.
I want to unlock bootloader but the option OEM Unlock is greyed out on Developer Options.
I tried RSD Lite with many firmware available on https://mirrors.lolinet.com/firmware/moto/ali/official but none worked.
Does someone have a tip?
Thanks!

I had the exact same problem. To fix it, I had to enable WiFi and get connected to the Interwebs. Wait a couple minutes to see if the option becomes available. If it does not, disable developer options, and re-enable it. That worked for me.

juicypoot said:
I had the exact same problem. To fix it, I had to enable WiFi and get connected to the Interwebs. Wait a couple minutes to see if the option becomes available. If it does not, disable developer options, and re-enable it. That worked for me.
Click to expand...
Click to collapse
I already tried everything that is possible!
I flahed retail firmware through RSD Lite and nothing happens: allow oem unlock greyed out.

Maybe your OEM is already unlocked. Try running this command: fastboot oem device-info in fastboot and see what it says

Guys, it's true!
After some days the 'Allow OEM Unlock' option became enable!
I did nothing! It's a matter of time, considered as a security measure.
That's it!

adrianogoes said:
Guys, it's true!
After some days the 'Allow OEM Unlock' option became enable!
I did nothing! It's a matter of time, considered as a security measure.
That's it!
Click to expand...
Click to collapse
Still waiting here. How much time did you wait?

You can also try to delete user 999 and oem option should reflect under dev option.

bhati2710 said:
You can also try to delete user 999 and oem option should reflect under dev option.
Click to expand...
Click to collapse
What do you mean? Please explain

You need to connect your mobile to wifi and follow steps for date change to year back.
Then look for software update. This would resolve it.
Here is the reference;
Hope it helps.

bhati2710 said:
You need to connect your mobile to wifi and follow steps for date change to year back.
Then look for software update. This would resolve it.
Here is the reference;
Hope it helps.
Click to expand...
Click to collapse
Thanks for replying, but this didn't work. I tried one year, one month, 7 days before and after and it still is grayed out :crying:

@mrsiri Are you trying to unlock the bootloader or is it already unlocked?

WoKoschekk said:
@mrsiri Are you trying to unlock the bootloader or is it already unlocked?
Click to expand...
Click to collapse
Trying to unlock it. I locked it by mistake and now need to wait 7 days for the OEM Unlock button in developer settings to be enabled. It could also be locked forever ( Is it possible?) but then there's no hope for me.
Edit: I can also boot the stock room boot.img image but that doesn't help with the OEM Unlock button. it is still grayed out. What I could do is boot a magisk patched image to get root, but by doing this all my phone did was reboot twice and forcing me to factory reset and then use the old regular non patched boot image that I'm currently using. My current flashed boot image has verity mode off, in case that could help into anything.
Thanks in advance for replying

mrsiri said:
Trying to unlock it. I locked it by mistake and now need to wait 7 days for the OEM Unlock button in developer settings to be enabled. It could also be locked forever ( Is it possible?) but then there's no hope for me.
Edit: I can also boot the stock room boot.img image but that doesn't help with the OEM Unlock button. it is still grayed out. What I could do is boot a magisk patched image to get root, but by doing this all my phone did was reboot twice and forcing me to factory reset and then use the old regular non patched boot image that I'm currently using. My current flashed boot image has verity mode off, in case that could help into anything.
Thanks in advance for replying
Click to expand...
Click to collapse
Your bootloader seems to be unlocked. It is not possible to flash another boot.img with a locked bootloader. What else should be the purpose of a unlocked bootloader?? This is the prerequisite to flash a ROM or a twrp.img
---------- Post added at 05:52 PM ---------- Previous post was at 05:49 PM ----------
What exactly is the text right under the toggle to turn on the OEM unlocking option?

WoKoschekk said:
Your bootloader seems to be unlocked. It is not possible to flash another boot.img with a locked bootloader. What else should be the purpose of a unlocked bootloader?? This is the prerequisite to flash a ROM or a twrp.img
---------- Post added at 05:52 PM ---------- Previous post was at 05:49 PM ----------
What exactly is the text right under the toggle to turn on the OEM unlocking option?
Click to expand...
Click to collapse
The text is "connect to the internet or contact your carrier". I didn't flash the boot.img, but booted it. Like when you boot TWRP, but in this case it was the original stock boot.img
My bootloader says "flashing_locked", so it is not fully unlocked. And I can't unlock it without enabling the "OEM Unlock" Button ?

Yes, you have to wait.

WoKoschekk said:
Yes, you have to wait.
Click to expand...
Click to collapse
In the end I sent my device to a repair service. Thanks for the help, but I can't rely on waiting 7 days and assuming the button will re-enable itself. I need it fixed as soon as possible.

I think that was a very bad idea! Since four days you are waiting for that button become active and there are only three days left. Do you really think a repair station will send it back in three days?? This button becomes active by itself in three days and after that they will send it back to you and earn the money for nothing!

WoKoschekk said:
I think that was a very bad idea! Since four days you are waiting for that button become active and there are only three days left. Do you really think a repair station will send it back in three days?? This button becomes active by itself in three days and after that they will send it back to you and earn the money for nothing!
Click to expand...
Click to collapse
Maybe you're right. But you have no idea all what was done in my phone. I really don't think that button was ever going to change. I'll actually be surprised if they can fix it without replacing parts. That's why I think this time it's better if the professionals take care of it, and I'll get the phone Thursday with the guarantee it will be fixed ( Motorola service is taking care of it)
---------- Post added at 11:45 PM ---------- Previous post was at 11:42 PM ----------
mrsiri said:
Maybe you're right. But you have no idea all what was done in my phone. I really don't think that button was ever going to change. I'll actually be surprised if they can fix it without replacing parts. That's why I think this time it's better if the professionals take care of it, and I'll get the phone Thursday with the guarantee it will be fixed ( Motorola service is taking care of it)
Click to expand...
Click to collapse
Yet the itch of simply waiting will now stay forever

mrsiri said:
Yet the itch of simply waiting will now stay forever
Click to expand...
Click to collapse
As soon as the bootloader is unlocked you won't have that trouble anymore.

WoKoschekk said:
As soon as the bootloader is unlocked you won't have that trouble anymore.
Click to expand...
Click to collapse
Good and bad News!
The repair service couldn't fix the problem so I wasn't charged for it.
The bad News is I'm back at the same state
This time I'll wait the 7 days.

Bricked the phone and locked the bootloader! Seriously need help from you.

Hi friends,
I am telling you the whole story in a short way,
I have needed to root my devices, so I unlocked bootloader as it said on some web sites and install a new rom. Mine was Android 8.1 Nokia 7 plus TA-1046 600CN I think now its Pie 600WW.
After that that Pie did not work well on my devices, especially sensors and notifications was awful. So tried to downgrade to stock rom, but could not.
Right now, there is no rom on my device and bootloader and also locked the critical partitions.
I have TWRP recovery installed but i cant enter the recovery mode, the device is always in download mode even try to enter with volume UP + Power button phone goes directly download mode.
I have done something stupid with locking bootloader I agree but please help me to get out of this situation.
Its too bad without a phone
Thank you very much.

I dont know if it will work. Did you try to switch the partitions from A to B or B to A?
There are tutorials on how to do that via adb. I cant tell you exactly how to do it, i did it also from tutorials.

magiQx said:
I dont know if it will work. Did you try to switch the partitions from A to B or B to A?
There are tutorials on how to do that via adb. I cant tell you exactly how to do it, i did it also from tutorials.
Click to expand...
Click to collapse
in both partitions it is saying Your device is corrupt. It can't be trusted and will not boot.
and
I cant go into recovery

That sounds bad. Sorry, im not that advanced.
Isn't it possible to force it into recovery via adb? I got no idea, just asking.

magiQx said:
That sounds bad. Sorry, im not that advanced.
Isn't it possible to force it into recovery via adb? I got no idea, just asking.
Click to expand...
Click to collapse
Unfortunately I can`t because the bootloader is locked I have to unlock it but I can not because I have to downgrade the bootloader from Pie to Oreo

It sounds like a bad situation indeed. I think you may be SOOL, but hopefully a way forward will become apparent. Otherwise a new device might be indicated ?

1.unlock bootloader
2.reflash firmware with tools.
for piehttps://forum.xda-developers.com/nokia-7-plus/how-to/guide-workaround-flashing-sparse-t3906070
for oreohttps://forum.xda-developers.com/nokia-7-plus/how-to/workaround-flashing-oreo-firmware-t3793791

I ran into a similar situation and I installed the stock rom using NOST (Nokia Online Service Tool) and the stock rom in .NB0 file type.
If you need those files PM me and I can provide them for you, most likely you have them already if you unlocked your bootloader using TechMesto's service.

Hello everyone, Please I need real help

I had a rog phone 2 with this Version 16.0631.1910.35 WW
Since the update was released, I am tried to update
So, I cannot made it I rooted my phone in somehow, I lost with the steps
So, the phone was started again without update, but it’s always starts on bootloader screen
So, I formatted my phone few days ago and the phone was stacked in booting menu
Every time same thing even when I connected it on the pc only detect the device but no storage or anything
So how can I use my phone again without any of these problem
How can really make as factory condition again without root or bootloader screen
With full performance
Thanks for support
Appreciate your concerns

Fathi Moh. said:
I had a rog phone 2 with this Version 16.0631.1910.35 WW
Since the update was released, I am tried to update
So, I cannot made it I rooted my phone in somehow, I lost with the steps
So, the phone was started again without update, but it’s always starts on bootloader screen
So, I formatted my phone few days ago and the phone was stacked in booting menu
Every time same thing even when I connected it on the pc only detect the device but no storage or anything
So how can I use my phone again without any of these problem
How can really make as factory condition again without root or bootloader screen
With full performance
Thanks for support
Appreciate your concerns
Click to expand...
Click to collapse
You are not alone bro.. it's bricked.. still waiting for mine to be shipped to china for repair

oberio28 said:
You are not alone bro.. it's bricked.. still waiting for mine to be shipped to china for repair
Click to expand...
Click to collapse
thanks for reply
thats mean i have to send it to factory fix ??
no other idea ???

Fathi Moh. said:
thanks for reply
thats mean i have to send it to factory fix ??
no other idea ???
Click to expand...
Click to collapse
If you can get your computer to recognise the device in fastboot mode using adb command to check its recognised you could maybe flash the 1910.35 raw firmware for it using the flashall_AFT.cmd within the firmware folder. I'm at work now but will provide more info later and possibly links to adb and firmware

reg66 said:
If you can get your computer to recognise the device in fastboot mode using adb command to check its recognised you could maybe flash the 1910.35 raw firmware for it using the flashall_AFT.cmd within the firmware folder. I'm at work now but will provide more info later and possibly links to adb and firmware
Click to expand...
Click to collapse
thanks for your support
I think maybe recognize the device in fast boot mood
but I wish to help me with full steps and links when u get back
thanks again
best wishes

Fathi Moh. said:
thanks for your support
I think maybe recognize the device in fast boot mood
but I wish to help me with full steps and links when u get back
thanks again
best wishes
Click to expand...
Click to collapse
Sorry for the delay in reply. I'll have a look and provide steps shortly
---------- Post added at 08:37 PM ---------- Previous post was at 08:15 PM ----------
Fathi Moh. said:
thanks for your support
I think maybe recognize the device in fast boot mood
but I wish to help me with full steps and links when u get back
thanks again
best wishes
Click to expand...
Click to collapse
Had a thought, saves me a lot of time re-writing it... Use the link to my thread that uses 1910.35 raw firmware with working links and steps.
As you already had WW 1910.35 version on the phone before, the fingerprint may have already been changed by you or the previous owner. Basically, ignore step 0. You can't boot into the android system to install the app which unlocks bootloader anyway.
Follow each instruction exactly in order of steps 3, 5 (ignoring the fastboot cmd to flash boot img), 1 then 2.
You'll be doing things in that order because you want to install adb fastboot first. In summary... After installing adb fastboot to the root of C drive on your pc, navigate to that adb folder in C drive, double click the cmd-here.exe. A cmd window will open. Then put the phone into fastboot mode and connect it to pc using the side port of the phone. Type and run the cmd 'fastboot devices' on that cmd window. If successful in recognising your phone it will show a serial number/device id. Then do steps 1 and 2

reg66 said:
Sorry for the delay in reply. I'll have a look and provide steps shortly
---------- Post added at 08:37 PM ---------- Previous post was at 08:15 PM ----------
Had a thought, saves me a lot of time re-writing it... Use the link to my thread that uses 1910.35 raw firmware with working links and steps.
As you already had WW 1910.35 version on the phone before, the fingerprint may have already been changed by you or the previous owner. Basically, ignore step 0. You can't boot into the android system to install the app which unlocks bootloader anyway.
Follow each instruction exactly in order of steps 3, 5 (ignoring the fastboot cmd to flash boot img), 1 then 2.
You'll be doing things in that order because you want to install adb fastboot first. In summary... After installing adb fastboot to the root of C drive on your pc, navigate to that adb folder in C drive, double click the cmd-here.exe. A cmd window will open. Then put the phone into fastboot mode and connect it to pc using the side port of the phone. Type and run the cmd 'fastboot devices' on that cmd window. If successful in recognising your phone it will show a serial number/device id. Then do steps 1 and 2
Click to expand...
Click to collapse
Thanks a lot, you are the One
You made my day on
I am happy to get back my Rog phone 2 to life
Really, I am so glad for you
It’s works 1000000%
Thanks again for your big support I am really appreciated

Fathi Moh. said:
Thanks a lot, you are the One
You made my day on
I am happy to get back my Rog phone 2 to life
Really, I am so glad for you
It’s works 1000000%
Thanks again for your big support I am really appreciated
Click to expand...
Click to collapse
Glad you got it working again! ?

Fathi Moh. said:
Thanks a lot, you are the One
You made my day on
I am happy to get back my Rog phone 2 to life
Really, I am so glad for you
It’s works 1000000%
Thanks again for your big support I am really appreciated
Click to expand...
Click to collapse
Oh, and well done, I forgot to give you the link to my thread!