Related
I would try to be as descriptive as possible.
Check if BLU allowed:
Dial *#*#7378423#*#*
Service info > Configuration > Rooting Status. It says Bootoader unlock allowed: yes
Go to SONY official webpage to get the unlock key. http://unlockbootloader.sonymobile.com/instructions
Enter the IMEI code and get the KEY in mail.
Put the phone in fastboot mode.
Code:
D:\>fastboot -i 0x0fce getvar version
version: 0.5
finished. total time: 0.002s
D:\>fastboot -i 0x0fce oem unlock 0xMYKEYINRIGHTCASE
...
FAILED (remote: Command did not succeed)
finished. total time: 0.036s
Curiously if I run the second command again, it succeeds.
Code:
D:\>fastboot -i 0x0fce oem unlock 0xMYKEYINRIGHTCASE
...
OKAY [ 0.171s]
finished. total time: 0.172s
Now if my bootloader is not supposed to be unlocked or the key is wrong then I believe the behavior should be consistent and should always FAIL. Unfortunately that is not the case. What is worse is that when now I do
Code:
D:> fastboot reboot
rebooting...
finished. total time: 0.002s
It does not reboot anymore and goes into boot loop. The only way out is to flash the stock ROM using flashtool and get it back.
What I really want to do:
Build and flash AOSP 4.3 onto the device. I have already build it and also downloaded pre-build img from one of the threads. Using fastboot flash works for boot, system and userdata on second attempt just like bootloader. However fastboot flash cache fails consistently. Rebooting again put me back into boot loop.
Is there any way to find out if the bootloader is actually unlocked or not?
I would appreciate any help in debugging/troubleshooting this problem. Looking forward.
P.S.: Not sure if this belongs here or in development forum.
bump up.
Any help would be appreciated from devs.
Go to configuration again and check rooting status. If you are truly unlocked, it will say:-
Bootloader unlocked: Yes
Sent from my C6603 using xda app-developers app
shoey63 said:
Go to configuration again and check rooting status. If you are truly unlocked, it will say:-
Bootloader unlocked: Yes
Sent from my C6603 using xda app-developers app
Click to expand...
Click to collapse
Thanks for responding. But unfortunately for me as soon as I run the oem unlock command twice, it does not boot anymore and I have to reflash it again. Post reflash when I go back I still see the previous status.
Adding some background:
This issue occurred only after I reflashed the stock ROM using SONY companion. This might have locked the bootloader again and corrupted the process of unlocking it. Is this a possibility? Any body who had similar problem?
Could you reflash to stock and check the bootloader unlock status? If you can reflash via PC Companion, it usually means that your bootloader was not unlocked. If yours was unlocked, it would fail and you would have to use Emma instead.
pandaball said:
Could you reflash to stock and check the bootloader unlock status? If you can reflash via PC Companion, it usually means that your bootloader was not unlocked. If yours was unlocked, it would fail and you would have to use Emma instead.
Click to expand...
Click to collapse
I can reflash to stock using flashtool, does that mean anything?
Sent from my Nexus 4 using xda app-developers app
nivarp said:
I can reflash to stock using flashtool, does that mean anything?
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
No. If you can repair your phone via PC Companion, your bootloader is locked. Only if you are unable to do that with an error code along the lines of "This phone's software has been modified" then your bootloader is unlocked. Flashtool works regardless of bootloader unlock status.
pandaball said:
No. If you can repair your phone via PC Companion, your bootloader is locked. Only if you are unable to do that with an error code along the lines of "This phone's software has been modified" then your bootloader is unlocked. Flashtool works regardless of bootloader unlock status.
Click to expand...
Click to collapse
I can repair which essentially means that the bootloader is locked. However I still see the configuration saying bootloader unlock allowed to be yes. Strange that i am not able to unlock it.
Hey all. I'm coming back from a custom ROM/kernel and I've successfully flashed the latest factory image. However, fastboot is spitting out an error when I go to relock the bootloader. Here's the output:
C:\Users\***>fastboot flashing lock
...
OKAY [ 0.002s]
finished. total time: 0.003s
After I issue the command my N6's screen goes unresponsive for a few minutes, after which I can still use the volume keys to navigate the bootloader. However, after a reboot, the device is still unlocked.
Has anyone else encountered this issue?
Try using "fastboot OEM lock". Fastboot flashing lock is only for the 5X/6P from what I understand.
pmikec said:
Hey all. I'm coming back from a custom ROM/kernel and I've successfully flashed the latest factory image. However, fastboot is spitting out an error when I go to relock the bootloader. Here's the output:
C:\Users\***>fastboot flashing lock
...
OKAY [ 0.002s]
finished. total time: 0.003s
After I issue the command my N6's screen goes unresponsive for a few minutes, after which I can still use the volume keys to navigate the bootloader. However, after a reboot, the device is still unlocked.
Has anyone else encountered this issue?
Click to expand...
Click to collapse
I don't know why it refuses to relock but another question: why do you want it to be relocked? It is adviced to only relock a bootloader when it is absolutely needed (warranty case, resale...)
Face_Plant said:
Try using "fastboot OEM lock". Fastboot flashing lock is only for the 5X/6P from what I understand.
Click to expand...
Click to collapse
This did the trick. I'm not sure why I didn't just try the old command myself before asking. Thanks!
Hi everybody, I have a little question regarding my P10.
The model of my phone is VTR-L09C521B101
Is there a way to flash this phone with VTR-L09C432 version?
or i need to flash with same model version (VTR-L09C521)?
Thnks
Yes, it is possible to 'rebrand'. The procedure is explained in the Mate 9 forum. It is not so easy and involves unlocking the bootloader.
Updating can be done with the Firmware Finder (Playstore).
M1chiel said:
Yes, it is possible to 'rebrand'. The procedure is explained in the Mate 9 forum. It is not so easy and involves unlocking the bootloader.
Updating can be done with the Firmware Finder (Playstore).
Click to expand...
Click to collapse
thanks for the answer!!
regarding bootloader, the phone shows this:
PHONE RELOCKED
FRP LOCK
ADB shows me that the phone is unlocked, the problem is when I try to send something to phone it shows:
Error Remote command not allowed.
any ideas?
thanks!
I've tried to reword the mate 9 instructions for the p10 here: https://forum.xda-developers.com/p10/help/rebrand-firmware-finder-t3685951
As for adb, what command are you trying? Do you see your phone if you type ADB Devices?
Quintman said:
I've tried to reword the mate 9 instructions for the p10 here: https://forum.xda-developers.com/p10/help/rebrand-firmware-finder-t3685951
As for adb, what command are you trying? Do you see your phone if you type ADB Devices?
Click to expand...
Click to collapse
Quintman, no the phone is not listed with adb devices command. I can only enter with fastboot.
Let me paste the commands that I have tried:
C:\adb>fastboot devices
WPG7N17320000978 fastboot
C:\adb>fastboot oem get-bootinfo
...
(bootloader) unlocked
OKAY [ 0.001s]
finished. total time: 0.001s
C:\adb>fastbot oem lock <my_unlock_code>
...
FAILED (remote: Command not allowed)
finished. total time: 0.016s
C:\adb>fastboot oem unlock <my_unlock_code>
...
FAILED (remote: Command not allowed)
finished. total time: 0.016s
C:\adb>fastboot oem relock <my_unlock_code>
...
FAILED (remote: stat not match)
finished. total time: 0.016s
The Strange thing is that in the phone shows PHONE RELOCKED, not unlocked as ADB shows.
Since I uploaded boot img of another version (C432) full OTA, could this be the problem? in this case what can I do?
thanks for your help!!
Could this be happening because of FRP Lock?, none of the software I have tried (DC-phoenix, chimera and Unlocker v2) worked. Im this close to throw this f*ckin phone to trash u.u
fmm1977 said:
Could this be happening because of FRP Lock?, none of the software I have tried (DC-phoenix, chimera and Unlocker v2) worked. Im this close to throw this f*ckin phone to trash u.u
Click to expand...
Click to collapse
edit: just found this in another thread "FRP Lock occurs when the phone has a firmware mismatch and or oem unlocking is not on in developer options"
Hmm, i've just checked my phone and in fastboot it says PHONE Locked, and FRP Unlock. I think that may be your issue. What exactly did you do to flash your phone with the other version? put an UPDATE.APP into a \Dload folder and 3 button update?
is your phone booting (guessing not). my guess is that you need to get a hold of your stock firmware file an flash that first.
Quintman said:
edit: just found this in another thread "FRP Lock occurs when the phone has a firmware mismatch and or oem unlocking is not on in developer options"
Hmm, i've just checked my phone and in fastboot it says PHONE Locked, and FRP Unlock. I think that may be your issue. What exactly did you do to flash your phone with the other version? put an UPDATE.APP into a \Dload folder and 3 button update?
is your phone booting (guessing not). my guess is that you need to get a hold of your stock firmware file an flash that first.
Click to expand...
Click to collapse
Ok, this is what I've done step by step:
1.- With the unlock code provided by huawei, I have unlocked my phone (my version is VTR-L09C521B101 stock)
2.- Once unlocked, I have downloaded another ROM version (VTR-L29C605B151) in the web page says this rom is for latin america), so with the Huawei Update Extractor, I have extracted all files.
3.- Via ADB/FASTBOOT, I sent the files to my phone, boot.img first and then the others. (big big mistake!)
4.- Rebooted the phone, and then keeps restarting at huawei logo.
5.- Seeing that it did´t worked, what I did was to lock the phone again thinking to send it to Huawei (at this point the phone shows as "unlocked" via fastboot commands, however when I start the phone in fastboot mode, in the screen shows "PHONE RELOCKED, FRP LOCK"
6.- Sent to huawei's service, they said that they cannot fix my phone because it was tampered/rooted.
7.- Right now all I need to fix my phone is to LOCK/UNLOCK again in order to rebrand it to L29 version, since the original stock rom dont exist (not as FULL OTA).
And that´s what I did so far my friend.
Questions:
1.- Is there a way to connect to my phone and change the oem info file? or something?
2.- Do I need to wait the stock rom to be released in order to reflash via Dload method?
3.- What if the stock ROM version of my phone is never released?
thank you for your answer my friend!!
Hmm ok. I am just not sure on your step 3, I've never heard of a method that involves a boot.img... what I would suggest, is to try and download the stock firmware files (need the larger full ota files), extract the update.app file and put on sd card in \dload.
Then hold down both volume up and down and power (3 button method)
It will try and flash the stock image back to the phone.
I just tried the Dload method and nothing happened (always stuck in 5%), now im going to try to use a smaller memory card (mine is 64 Gb). lood
U have disconnected the USB cable when u try 3 button update
berka38 said:
U have disconnected the USB cable when u try 3 button update
Click to expand...
Click to collapse
Yes sr!!
Hello, I'm trying to follow This guide and This one to unlock the bootloader with no luck.
This is what I get:
Code:
C:\Minimal ADB and Fastboot>fastboot devices
ZY322MF6XP fastboot
C:\Minimal ADB and Fastboot>fastboot oem get_unlock_data
...
FAILED (remote: unknown command)
finished. total time: 0.000s
I updated drivers and adb and fastboot with no luck.
Any help?
Edit: I have a Moto G6 Plus in RETLA channel with the march security patch.
I'd double check that Allow OEM Unlock in dev options is actually on
ZeroPoke said:
I'd double check that Allow OEM Unlock in dev options is actually on
Click to expand...
Click to collapse
Tried it with it on and off twice!
Angelelz said:
Tried it with it on and off twice!
Click to expand...
Click to collapse
Same thing happened to me. When you get your unique identifier find an online generator and then paste that into the Motorola website, worked for me.
H0LT3R said:
Same thing happened to me. When you get your unique identifier find an online generator and then paste that into the Motorola website, worked for me.
Click to expand...
Click to collapse
Yeah, can't get the unique identifier though, that particular command is not working for me. Anyone have any idea why?
Hi,
For Working this command "Fastboot oem get_unlock_data"
First you need to remove or delete your phone's SCREEN LOCKS like your fingerprint, face-unlock, pattern or password etc... And keep on NONE option in lock screen. After all above procedure done than, You run that commend "Fastboot oem get_unlock_data". After runing thant command, You will not get "FAILED (remote: unknown command)"
It will work 200%.
PRUTHVIRAJ S VASUDEV said:
It will work 200%.
Click to expand...
Click to collapse
no. it doesnt.
It depends on your fastboot version. Please check "fastboot --version" and post it here.
---------- Post added at 03:49 AM ---------- Previous post was at 03:44 AM ----------
...or try "fastboot oem help". This option will show you whether this command is available.
hi!
i have same problem.
product: Lenovo TB-7504x
fastboot getvar info:
warranty: yes
unlocked: no
secure: yes
kernel: lk
product: WT98997_LTEROW
version-preloader: 0.1.00
version: 0.5
PS: Allow OEM Unlock in developer options is actually on
Also having this issue trying to root my LG G6; I successfully set up adb, fastboot, and started up into bootloader, but it keeps returning the failed/unknown command error when I try to do any further steps. "fastboot devices" shows up correctly but "fastboot oem device-info", device-id, "fastboot flash recovery twrp.img", all keep failing
renforrest-EX said:
Also having this issue trying to root my LG G6; I successfully set up adb, fastboot, and started up into bootloader, but it keeps returning the failed/unknown command error when I try to do any further steps. "fastboot devices" shows up correctly but "fastboot oem device-info", device-id, "fastboot flash recovery twrp.img", all keep failing
Click to expand...
Click to collapse
same
Did you try another USB port? Some users reported that USB 3.0 did not work but 2.0.
I would be willing to bet this is happening on devices that are not allowed to be unlocked. Like those purchased from a phone company.
its been a week since i'm trying on my htc 10, but getting the same error, i tried,
- delete the drivers and re-install
- delete sync manager
- enabled debug & oem unlock
- done reset factory for the phone
- change USB ports and cables
- tried 3 latops
nothing works, sometimes i'll just the error "waiting for any phone" and other times "FAILED (remote: unknown command)"
Angelelz said:
Hello, I'm trying to follow This guide and This one to unlock the bootloader with no luck.
FAILED (remote: unknown command)
finished. total time: 0.000s[/CODE]
I updated drivers and adb and fastboot with no luck.
Try fastboot oem unlock first, then fastboot oem get_unlock_data
Any help?
Edit: I have a Moto G6 Plus in RETLA channel with the march security patch.
Click to expand...
Click to collapse
Try fastboot oem unlock first then fastboot oem get_unlock_data
I'm following a tutorial and obviously got stuck and the very same step as you did. And presumably you are following a tutorial, too.
1. Go to Security Settings and remove device lock (PIN, fingerprint, whatever you are using) and set it to NONE.
2. Go to Developer Settings and Unlock Bootloader. (If you skip step 1., you'll be asked to unlock your device here, but find that the Unlocking failed afterwards. Hence, go to step 1. and remove the lock first.)
3. fastboot oem unlock
Done. (Bootloader is unlocked now. Confirm via boot to fastboot mode (Volume down + Power button))
fastboot oem get_unlock_data is probably removed (deprecated) and maybe you don't even need a key from the manufacturer to unlock anymore.
gelignite said:
maybe you don't even need a key from the manufacturer to unlock anymore.
Click to expand...
Click to collapse
You still need a key to unlock the bootloader for the first time! When it's locked with status "flashing_locked" you don't need a key for it.
Is it a brand new device...?
WoKoschekk said:
You still need a key to unlock the bootloader for the first time! When it's locked with status "flashing_locked" you don't need a key for it.
Is it a brand new device...?
Click to expand...
Click to collapse
If that question refers to my post: I have a Moto E4 (XT1762). Bought it like half a year ago to tinker around with. I started it, ran all updates available and set a device lock (here: PIN).
Today I finally found the time to get started with lineageos and followed the guide at: rootmygalaxy.net (download-and-install-lineage-os-16-on-motorola-moto-e4-android-9-0-pie)
I got stuck at the error the OP had. (This lead me here.)
In my case I got past the error by doing the steps mentioned in my first post, i.e.
1. started the device (normal boot) and got rid of the device lock (PIN in my case), enabled USB debugging, enabled bootloader unlocking
2. powered off the device and started it again in fast boot mode (volume down + power button)
3. On computer / in terminal: fastboot oem unlock (without any key from the manufacturer)
The device showed a confirmation dialog. (Volume up: Yes, Volume down: No)
Code:
[email protected]:~/downloads/lineageos/Android_SDK_platform_tools/platform-tools$ ./fastboot oem unlock
(bootloader) Start unlock flow
OKAY [ 9.657s]
Finished. Total time: 9.667s
Now in fast boot screen I see Device Status: unlocked
I just wanted to share my experiences from today's struggles and maybe it'll help the OP.
gelignite said:
If that question refers to my post: I have a Moto E4 (XT1762). Bought it like half a year ago to tinker around with. I started it, ran all updates available and set a device lock (here: PIN).
Today I finally found the time to get started with lineageos and followed the guide at: rootmygalaxy.net (download-and-install-lineage-os-16-on-motorola-moto-e4-android-9-0-pie)
I got stuck at the error the OP had. (This lead me here.)
In my case I got past the error by doing the steps mentioned in my first post, i.e.
1. started the device (normal boot) and got rid of the device lock (PIN in my case), enabled USB debugging, enabled bootloader unlocking
2. powered off the device and started it again in fast boot mode (volume down + power button)
3. On computer / in terminal: fastboot oem unlock (without any key from the manufacturer)
The device showed a confirmation dialog. (Volume up: Yes, Volume down: No)
Code:
[email protected]:~/downloads/lineageos/Android_SDK_platform_tools/platform-tools$ ./fastboot oem unlock
(bootloader) Start unlock flow
OKAY [ 9.657s]
Finished. Total time: 9.667s
Now in fast boot screen I see Device Status: unlocked
I just wanted to share my experiences from today's struggles and maybe it'll help the OP.
Click to expand...
Click to collapse
Moto E4 is a developer's device without a locked bootloader. I thought you were talking about a Moto G6.
Baronstragen said:
Try fastboot oem unlock first then fastboot oem get_unlock_data
Click to expand...
Click to collapse
fastboot oem unlock worked for me
My friend have Problem his device after trying to install custom ROM just a reboot but not go into system so he go to Huawei shop and I wait 3 days after that told him should go to another shop We can't fix it!, but before that his phone his phone open bootloader and can use ADB ،When the device is returned from him it's locked and can't open bootloader or do anything ،They told him not responsible for this and can't the installation the system in his device wtf Huawei Oh really !
So he needs his phone, I take phone but does not can't do anything like open bootloader or any thing with ADB or format and His system was returned to Android 6 !
albelushi7 said:
My friend have Problem his device after trying to install custom ROM just a reboot but not go into system so he go to Huawei shop and I wait 3 days after that told him should go to another shop We can't fix it!, but before that his phone his phone open bootloader and can use ADB ،When the device is returned from him it's locked and can't open bootloader or do anything ،They told him not responsible for this and can't the installation the system in his device wtf Huawei Oh really !
Click to expand...
Click to collapse
If your friend was able to flash custom ROM, he had to have Bootloader unlocked.
It means that he did have Bootloader code - he had to keep it because same Bootloader code is good for the same phone for the whole life. Unfortunately, people didn't dare to care about that, similarly like not caring to learn first (before they bricked the phones) about what and how to flash - this is unfortunately one of the reasons (bad posts on Internet) that Huawei changed the policy about BL codes (and now everyone, also those who do care what and how) suffer.
Anyway, for P9 you can still buy the BL code for 4-5 USD.
Also, if they returned the phone unbricked, with MM, you should be able to upgrade to Nougat by DLOAD, not needing to unlock BL (ir they didn't put c300 MM)
zgfg said:
If your friend was able to flash custom ROM, he had to have Bootloader unlocked.
It means that he did have Bootloader code - he had to keep it because same Bootloader code is good for the same phone for the whole life. Unfortunately, people didn't dare to care about that, similarly like not caring to learn first (before they bricked the phones) about what and how to flash - this is unfortunately one of the reasons (bad posts on Internet) that Huawei changed the policy about BL codes (and now everyone, also those who do care what and how) suffer.
Anyway, for P9 you can still buy the BL code for 4-5 USD.
Also, if they returned the phone unbricked, with MM, you should be able to upgrade to Nougat by DLOAD, not needing to unlock BL (ir they didn't put c300 MM)
Click to expand...
Click to collapse
Thanks for your reply, now cant flash anything < . I try to fix what can be fixed, he has the code but now when doesn't work or something is wrong, when try with ADB to unlock bootloader (.. "FAILED > emote: Command not allowed) also FRP LOCK .
i try many version with DLOAD but does not work! < Maybe can give me to try it ! another thing when try to format It seems not working only 2 % .fact now I do not know what to do with his phone but I will try!
To unlock FRP, you must unlock OEM from Settings, Development menu.
As you described, phone was bootable (to MM) when returned from service - but now, after the failed DLOADing, etc, is it bootable any more
You cannot DLOAD any P9 firmware to any P9 phone. Firmware must be:
- of the same model and cust (otherwise you first needed to rebrand)
- it must be shown eg in FirmwareFinder as FullOTA-MF-PV (not just FullOTA-MF)
If not cared about (specially about model and cust) - no wonder if it bricked the phone
If you cannot boot anymore to read full model, cust and build number from Settings, About, you can read from Fastboot (switch off, connect to PC, press and keep pressing Vol-, boot by Pow). You will need ADB & Fastboot installed on your PC - if not, search for Minimal ADB and Fastboot on XDA and install.
You can copy to bat file and execute:
Code:
fastboot devices
PAUSE
fastboot oem get-bootinfo
PAUSE
fastboot oem get-product-model
PAUSE
fastboot getvar vendorcountry
PAUSE
fastboot oem get-build-number
PAUSE
fastboot oem oeminforead-SYSTEM_VERSION
zgfg said:
To unlock FRP, you must unlock OEM from Settings, Development menu.
As you described, phone was bootable (to MM) when returned from service - but now, after the failed DLOADing, etc, is it bootable any more
You cannot DLOAD any P9 firmware to any P9 phone. Firmware must be:
- of the same model and cust (otherwise you first needed to rebrand)
- it must be shown eg in FirmwareFinder as FullOTA-MF-PV (not just FullOTA-MF)
If not cared about (specially about model and cust) - no wonder if it bricked the phone
If you cannot boot anymore to read full model, cust and build number from Settings, About, you can read from Fastboot (switch off, connect to PC, press and keep pressing Vol-, boot by Pow). You will need ADB & Fastboot installed on your PC - if not, search for Minimal ADB and Fastboot on XDA and install.
You can copy to bat file and execute:
Code:
fastboot devices
PAUSE
fastboot oem get-bootinfo
PAUSE
fastboot oem get-product-model
PAUSE
fastboot getvar vendorcountry
PAUSE
fastboot oem get-build-number
PAUSE
fastboot oem oeminforead-SYSTEM_VERSION
Click to expand...
Click to collapse
fastboot oem get-bootinfo
...
(bootloader) locked
OKAY [ 0.013s]
finished. total time: 0.014s
-----
fastboot oem get-product-model
...
(bootloader) EVA-L19
OKAY [ 0.011s]
finished. total time: 0.012s
----
fastboot getvar vendorcountry
vendorcountry: hw/meafnaf
finished. total time: 0.010s
------
fastboot oem get-build-number
...
(bootloader) :System 8.0.0.046(0OHZ)
OKAY [ 0.011s]
finished. total time: 0.012s
-----
fastboot oem oeminforead-SYSTEM_VERSION
...
FAILED (remote: Command not allowed)
albelushi7 said:
fastboot oem get-bootinfo
...
(bootloader) locked
OKAY [ 0.013s]
finished. total time: 0.014s
-----
fastboot oem get-product-model
...
(bootloader) EVA-L19
OKAY [ 0.011s]
finished. total time: 0.012s
----
fastboot getvar vendorcountry
vendorcountry: hw/meafnaf
finished. total time: 0.010s
------
fastboot oem get-build-number
...
(bootloader) :System 8.0.0.046(0OHZ)
OKAY [ 0.011s]
finished. total time: 0.012s
-----
fastboot oem oeminforead-SYSTEM_VERSION
...
FAILED (remote: Command not allowed)
Click to expand...
Click to collapse
According to:
Code:
(bootloader) locked
your Bootloader is locked.
Does the Fastboot show also FRP locked?
And you cannot login to Android (to unlock OEM=FRP)?
According to:
Code:
(bootloader) EVA-L19
vendorcountry: hw/meafnaf
Your P9 should be L19 (dual SIM), and you had c185 Middle East cust.
From your previous posts, phone was on MM (EMUI 4), maybe you successfully upgraded to Nougat (EMUI 5)
But according to:
Code:
(bootloader) :System 8.0.0.046(0OHZ)
you attempted to flash some Oreo (EMUI 8) - and that bricked the phone?!
zgfg said:
According to:
Code:
(bootloader) locked
your Bootloader is locked.
Does the Fastboot show also FRP locked?
And you cannot login to Android (to unlock OEM=FRP)?
According to:
Code:
(bootloader) EVA-L19
vendorcountry: hw/meafnaf
Your P9 should be L19 (dual SIM), and you had c185 Middle East cust.
From your previous posts, phone was on MM (EMUI 4), maybe you successfully upgraded to Nougat (EMUI 5)
But according to:
Code:
(bootloader) :System 8.0.0.046(0OHZ)
you attempted to flash some Oreo (EMUI 8) - and that bricked the phone?!
Click to expand...
Click to collapse
the FPR loked its showed in fastboot and the system not boot anymore
actually its 8 oreo When I checked it through adb , but i said m.m Because recovery and erecovery like on emui4 !
also when i try use Erecovery Touch Not working to Connect to Wi-Fi !
Yes is P9 L19 c185 and when try use DLOAD FullOTA-MF-PV in stuck huawei logo
albelushi7 said:
the FPR loked its showed in fastboot and the system not boot anymore
actually its 8 oreo When I checked it through adb , but i said m.m Because recovery and erecovery like on emui4 !
also when i try use Erecovery Touch Not working to Connect to Wi-Fi !
Yes is P9 L19 c185 and when try use DLOAD FullOTA-MF-PV in stuck huawei logo
Click to expand...
Click to collapse
It's bricked since you flashed Oreo Bootloader over the MM or N firmware, and hence it also does not accept DLOAD
To fix, you would need to flash by Fastboot, but Bootloader is locked and you are not allowed to.
To unlock BL you would need to unlock FRP, but due to the brick you cannot enter to System to unlock OEM/FRP
Hence you are stuck…
-You can try one more DLOAD by downloading this package:
https://androidhost.ru/bN4
You will have to unzip/untar (whatever applies), you should find a folder Docs inside with the Installation guide.
This is official package for DLOAD repair (P9 L19 c185 b403) for Huawei service shops, but I'm not sure would it work over your bricked Bootlloader from Oreo
-Certainly you could recover by TestPoints (but you can also definitely brick the phone by one wrong move there),
but it requires openening back-cover, short-connecting two pins and flashing the appropriate bord firmware (you would also need TestPoints drivers).
It's risky, TG I never need it, if you want to learn about you will need to search on the Net and XDA
-Otherwise, due to the facts as above, I can only recommend you to seek for the paid help from DC Phoenix:
https://www.dc-unlocker.com/DC-Phoenix-flash-repair-tutorial
Ask them in advance, it might cost you cca 20 EU credits (tools and instructions for unlocking FRP and Bootloader, unbricking and flashing official Nouga firmware).
You can probably arrange also for debranding to L19 c432 Nougat if you wish
If you would then want to rebrand and upgrade to AL10 c00 b540 Oreo, you will have to start with:
- unbricked phone with latest Nougat firmware
- having Bootloader code ready
and to carefully follow OP instructions from this thread:
https://forum.xda-developers.com/p9/development/rebrand-update-tool-hwota7-p9-eva-t3820849
zgfg said:
It's bricked since you flashed Oreo Bootloader over the MM or N firmware, and hence it also does not accept DLOAD
To fix, you would need to flash by Fastboot, but Bootloader is locked and you are not allowed to.
To unlock BL you would need to unlock FRP, but due to the brick you cannot enter to System to unlock OEM/FRP
Hence you are stuck…
-You can try one more DLOAD by downloading this package:
https://androidhost.ru/bN4
You will have to unzip/untar (whatever applies), you should find a folder Docs inside with the Installation guide.
This is official package for DLOAD repair (P9 L19 c185 b403) for Huawei service shops, but I'm not sure would it work over your bricked Bootlloader from Oreo
-Certainly you could recover by TestPoints (but you can also definitely brick the phone by one wrong move there),
but it requires openening back-cover, short-connecting two pins and flashing the appropriate bord firmware (you would also need TestPoints drivers).
It's risky, TG I never need it, if you want to learn about you will need to search on the Net and XDA
-Otherwise, due to the facts as above, I can only recommend you to seek for the paid help from DC Phoenix:
https://www.dc-unlocker.com/DC-Phoenix-flash-repair-tutorial
Ask them in advance, it might cost you cca 20 EU credits (tools and instructions for unlocking FRP and Bootloader, unbricking and flashing official Nouga firmware).
You can probably arrange also for debranding to L19 c432 Nougat if you wish
If you would then want to rebrand and upgrade to AL10 c00 b540 Oreo, you will have to start with:
- unbricked phone with latest Nougat firmware
- having Bootloader code ready
and to carefully follow OP instructions from this thread:
https://forum.xda-developers.com/p9/development/rebrand-update-tool-hwota7-p9-eva-t3820849
Click to expand...
Click to collapse
I can't believe the phone back to work again!
How to bring the phone back to life and to work? The phone was restarting at the Huawei logo, adb not working and I have bootloader code but not working FPR looked and bootloader looked
Dload not working , so what I do , try use DC phoneix and go forward the bootloader unlocked and FPR but unfortunately must phone go to update mode but unfortunately now stuck again with no fastboot and no recovery !
finally I try with testpoint with IDM and Huawei bored and working!
and upgrade or install system with dload
After that install Android 7 and update to Oreo 8 with TWRP ?.