Database Users

[ GUIDE ] How change relocked bootloader to locked

Hi all.
Today i write how restore locked bootloader on mate7 on 4.4.2 , 5.1.1 and 6.0 rom
What we need :
1. Unlocked bootloader
2. Root
3. Dc Unlocker client count ---> https://www.dc-unlocker.com/downloads
4. HCU-Client v1.0.0.0062 ---> http://hcu-client.com/download/
5. Oeminfo and Custom.bin from this link ---> https://mega.nz/#!l9ZWRTDS!Y-fYWnUIlCBDcGt_7WywDcgQAIbVR0c3SiFWGx-wYeU
6. Your Unlock code to your bootloader
7. Fx Explorer.
8. Mobopx tool ---> https://mega.nz/#!9kBWnY7T!ybhARn5UNXAyxrdQZ1ytKks24eCyzxkgdVhEza6zwFQ
9. Downgrade pack b500 for downgrade from 6.0 to 5.1.1
10. Downgrade pack b300 for downgade from 5.1.1 to 4.4.2
11. Twrp Backup your firmware you have now installed
12. All firmware for your device
And patience
Ok let's start now
What we must do first???
First we must downgrade from 6.0 if you have on your mt7 to 5.1.1
How do it???
Here i write how i do it :
1. I have b571 instaled and rooted
2. Downloaded custom.bin and oeminfo we copy to :
- Oeminfo copy to System(root)/dev/block/platform/hi_mci0/by-name and overwrite
- Custom.bin copy to System(root) /data and overwrite and set permission to 0775
3. Go back to System(root) and push search and write recovery ( it take some time to search )
4. When its finish you see folder recovery and open in new window
5. When it's open you see log and now you must delete this file
6. Now go to System(root)/data/system/dropbox and open ( delete all file in side )
7. Now go to System(root)/log/log-services and delete all folder
8. Open SrkTool via Administrator and go to unlock bootloader
9. When you unlock use Mobopx tool to flash stock recovery
10. When it's finish go to SuperSu and do it full unroot
11. Copy B500 update.app to dload in internal sdcard and flash using 3 bottom method
12. When you Have now B500 flash latest 5.1.1 and flash
13. Copy B300 update.app to dload in internal sdcard and flash using 3 bottom method
14. When you Have now B300 flash latest 4.4.2 and flash
15. When you have now latest 4.4.2 (in my case it's B137sp03) download first 4.4.2 for your mate7
16. When you download copy update.app to dload in internal sdcard and flash ( in my case it's b120sp04 )
17. When we have first 4.4.2 go to setting and then backup & reset and do it factory data reset and internal memory to.
18. When its boot go to setting/about phone and push 7 time on bulid number and go to developers option ( enable usb debugging )
19. Now open SrkTool and relock your bootloader
20 . When you have relocked we can go to next step
How change relock to locked bootloader
1. Open Dc Unlocker and create new count ( you must buy 4 credits )
2. When you have active your count open HCU Client and log there
3. When you login you has connect to server.
4. Now go to dialpad in your mate7 and write this code *#*#2846579#*#* push 1 and 2 ( change to Manufacture Mode and plug mate7 to your pc via usb cable )
5. In Hcu push Read Phone and when its connected go to unlock and push Lock Bootloader its take 1 min
6. When it's finish change Manufacture Mode to Hisuite Mode
7. Now go to SrkTool and push 7 then 5 and your phone go to fastboot mode and you see you have locked bootloader.
How Lock bootloader on latest full 6.0
1. When you have locked bootloader on your first 4.4.2 update to latest 4.4.2 using ota update
2. When it's Upodate you must unlock bootloade, reboot device, relock bootloader and lock bootloader (go to setting and then backup & reset and do it factory data reset and internal memory to.)
3. Now Flash latest 5.1.1 and do it that same unlock bootloade, reboot device, relock bootloader and lock bootloader (go to setting and then backup & reset and do it factory data reset and internal memory to.)
4. Now Flash first 6.0 full rom and do it that same unlock bootloade, reboot device, relock bootloader and lock bootloader
(go to setting and then backup & reset and do it factory data reset and internal memory to.)
5. Update to last 6.0 using Ota update and do it that same unlock bootloade, reboot device, relock bootloader and lock bootloader (go to setting and then backup & reset and do it factory data reset and internal memory to.)
Why we must unlock bootloader, relock and lock after full update rom???
Because all firmware have diffrent data formate in rom. When you lock bootloader all this information go to sevice when you use HCU Client.
If you want lock bootloader on 6.0 you must flash first Marshmallow (in my case it's B522 ) and do it format using backup & reset and do it factory data reset and internal memory to. Now you can relock first Marshmallow and update to last firmware and send your device to huawei services. Your warranty it's back and they repair your device
That all. Cheers
If you want you can buy me bear :highfive:

bricked device don't know how to fix (L31)

first off i cant use erecovery because im in unofficial nrd90m so it wont find anything, i accidently put the wrong oem info onto my device and i cant even boot into twrp, i have access to fastboot but i dont know enough about it to fix my issue unlocked boot loader and rooted if possible i want to downgrade to mm and get the official latest nougat update for uk(L31 single sim) i tried flashing stock recovery (nougat) and it says remote command not allowed.

bghyt said:
first off i cant use erecovery because im in unofficial nrd90m so it wont find anything, i accidently put the wrong oem info onto my device and i cant even boot into twrp, i have access to fastboot but i dont know enough about it to fix my issue unlocked boot loader and rooted if possible i want to downgrade to mm and get the official latest nougat update for uk(L31 single sim) i tried flashing stock recovery (nougat) and it says remote command not allowed.
Click to expand...
Click to collapse
Hello,
This thread will help you:
-Unlock bootloader (you must have the unlock code)
-flash oeminfo
-put the rollback package in dload folder (a little xda search)
-put B160 in dload
and you will get MM.

Besstheone said:
Hello,
This thread will help you:
-Unlock bootloader (you must have the unlock code)
-flash oeminfo
-put the rollback package in dload folder (a little xda search)
-put B160 in dload
and you will get MM.
Click to expand...
Click to collapse
I tried that yesterday after i posted this and it says FAILED stat does not match or somthing simular i will try again tommrow but that is probaly what it said.

P10 Plus heavely bricked

Guys, I need you :angel:
I have a P10 Plus (VKY-L09C55B142) and I tried to debrand (with L29) it but something went wrong. At first boot, I noticed that the OEM information was wrong (under phone's information menu I can see: name ONYX D189, model D189-L29, serial: NRD90M test-keys). After that, trying another guide, my phone bricked with FRP locked (and I can't activate it because it switch off itself) and bootloader unlocked. So I purchased DC Phoenix (3 day) to solve FRP that now is unlocked. But now my phone doesn't boot on Android; I can only use fastboot and recovery (I can install TWRP). If I try to flash something, erecovery start to install but stuck at 5% (even with DC Phoenix).
What can I do?
I made a backup with TWRP before do any guide but I don't know if it's usable

need full stock firmware by HWOTA

Gamkutopolowk said:
need full stock firmware by HWOTA
Click to expand...
Click to collapse
Do you know where I can find necessary files?

see what happened to me
https://forum.xda-developers.com/showpost.php?p=75355361&postcount=40
you can recover and rebrand to dual sim using this how-to and the files from the same post
https://forum.xda-developers.com/showpost.php?p=72416532&postcount=10
which and the end worked for me. You need time, patience and a SD card and few reboots.
Could be necessary a factory reset but only if you have bad luck
ps assuming that you have the code for boot unlock

http://www.stechguide.com/huawei-p10-plus-b181-nougat-update/
download three files from firmware finder C432B181
only methode 1

This is the process I followed to reset my p10 + phone to original stock, it is in Spanish but it is easy to understand.
video clic

P9 lite brick? @transition Nougat-MM. PHONE locked, FRP unlock

Hi, second post on the forums, I'm in bigger trouble now.
I unlocked my bootloader and then rooted my VNS-L21 so I could edit my hosts file. I tried going back to official and unrooted firmware afterwards, but something went wrong along the way.
The stages:
-OFW VNS-L21C432B504, obtained bootloader code through DC-unlocker (developer options on, OEM unlock on, debug usb on)
-unlocked bootloader with SRKtool using this method get-instant-huawei-bootloader-unlock-code/
-rooted using Magisk and made a full backup through Revolution Recovery using this method https://ministryofsolutions.com/2018/05/huawei-p9-lite-root-for-nougat-new-method.html
- some tinkering here but don't remember exactly plus I guess it's not that relevant ; I think I got rid of root here
- downgraded from Nougat to MM using dload method according to this thread https://forum.xda-developers.com/hu...torial-rollback-n-to-mm-c432-devices-t3563955 (first flashing rollback package from C432B504 to C900B300, then flashing C432B160 - full)
- everything went fine, bootloader relocked; but I was unable to upgrade to Nougat/B504 - settings-update showed "no updates available", putting update.app in dload folder (obtained from firmware finder, TeamMT, full B504 file) didn't work, pressing three buttons resulted in error (the version not compatible or sth)
-tried dload with previous rollback file
...and now I'm here:
- phone constantly stuck at boot screen (red Huawei logo)
- dload not starting by pressing three buttons
- recovery not starting by pressing volume up
The only thing I can get is white fastboot screen when connected to PC. It says "phone locked" (bootloader) in green, "FRP unlocked" in red. As usb debugging/oem unlock were not enabled this time, platform-tools/adb with command "adb devices" says nothing is connected, similar goes for SRK
Is it hopeless and my phone is thrash or is there anything I can do? Please help!
PS. All I wanted to do with my root was to change hosts file and then unroot/relock phone, seems like it wasn't worth all this work ( https://forum.xda-developers.com/huawei-p9lite/help/retaining-modified-hosts-file-unrooting-t3868641 )
Update: "fastboot devices" in adb directory resulted in detecting my device, next I found and tried command "fastboot oem [PASSWORD]", now there's a change: "This device cannot be trusted" is showing again, in fastboot I see "PHONE Unlocked" in red now. So time to flash some firmware with a command? But which firmware and how exactly to do that?

You have again unlocked your Bootloader? I suggest you flash a Nougat Compatible TWRP and then from within TWRP make wipes. After that use Hurupdater to flash Nougat firmware. First flash TWRP. If it boots into TWRP then format data and then wipe Dalvik/Art Cache, Cache, Data, System and Internal. Next download Hurupdater and stock Nougat Firmware. You need to download three ZIP update.zip, update_data_full_public.zip and regional update file. Next rename them as suggested in Hurupdater thread. Finally place all four files in same folder in SD card and then install and select only Hurupdater.zip to flash. After it complete reboot to stock recovery and factory reset. If all goes well you will be on Nougat.

Thank you so much, HuRU update method was what finally got me from Marshmallow to Nougat

So. I take it your phone is working now? Glad to know and be of help. If you need help with anything then just ask

Yes, it is, I'm currently struggling with systemless hosts on my Magisk rooted Nougat but other than that - everything works fine. Turns out that most of the recoveries I found then were meant for Nougat, only one recovery file worked on Marshmallow (and I've tried quite a few of such files and they were hard to find).
________________
After flashing TWRP recovery, updating Magisk to 17.3 beta and installing newest (4.0.10) version of Adaway - the problem is gone. My guess is that the fault was on Magisk's side as after updating it the "systemless hosts" function in Adaway was no longer grayed out.

Need help raising it from the graveyard

Hello everyone.
I managed to brick my p9 lite (VNS-L31C432 dual sim) by flashing the rollback package over B161 (I know B160 is for DS, I just missed the correct update.app twice). The current status of my phone right now is:
- Phone won't boot, is stuck at "Phone is booting now"
- VolUP + VolDOWN + Power combination doesn't access to dload. If I have it connected via usb to my computer it kinda enter to dload but an usb plug symbol appears and does nothing
- Can unblock/rebock bootloader
- Can access to TWRP 3.0.2-0
- Can access to Fastboot and flash partitions, however when I do it TWRP lose the ability to mount them and they appear as 0MB partitions (I have to change fs to EXT2 then to EXT4 to make them work again).
So, from where should I start to try to recover my phone?

Mairtrus said:
Hello everyone.
I managed to brick my p9 lite (VNS-L31C432 dual sim) by flashing the rollback package over B161 (I know B160 is for DS, I just missed the correct update.app twice). The current status of my phone right now is:
- Phone won't boot, is stuck at "Phone is booting now"
- VolUP + VolDOWN + Power combination doesn't access to dload. If I have it connected via usb to my computer it kinda enter to dload but an usb plug symbol appears and does nothing
- Can unblock/rebock bootloader
- Can access to TWRP 3.0.2-0
- Can access to Fastboot and flash partitions, however when I do it TWRP lose the ability to mount them and they appear as 0MB partitions (I have to change fs to EXT2 then to EXT4 to make them work again).
So, from where should I start to try to recover my phone?
Click to expand...
Click to collapse
Hello,
unlock again the bootloader then use correct rollback package (or flash L31C432OEMinfo_bin dual sim file with TWRP) and DLOAD correct firmware this time...
If you are unsure just ask...
Cheers

Dadditz said:
Hello,
unlock again the bootloader then use correct rollback package (or flash L31C432OEMinfo_bin dual sim file with TWRP) and DLOAD correct firmware this time...
If you are unsure just ask...
Cheers
Click to expand...
Click to collapse
Thanks, pal, but I already fixed it, doing a lot of trial-errors
If someone who had the same problems I had is reading this, what you really need to do is:
As Dadditz said, flash first your correct oem info, then unlock the bootloader
If you can't access dload, find the full-ota package for the exact same version of MM you previously had (before the brick, of course). Unzip the UPDATE.APP and then use UpdateExtractor to get BOOT, SYSTEM, RECOVERY, RECOVERY2 and CUST. Flash all of them via Fastboot.
If you try to boot and it gets into eRecovery, then it's a good sign. Put the UPDATE.APP from the previous step in the dload folder of your SD, use the dload method and let the install run. It will probably fail at the end, this seems to be normal.
You phone will boot and it will probably feel like it's working ok again, but I bet there are chances that a some stuff doesn't work or even appear at all (first time the fingerprint config didn't appeared to me, second time was the google account login). Turn off the phone, install the correct version of TWRP, wipe cache/dalvik, then do a factory reset (dunno if both are needed, I just did it this way and it worked ok).
Reboot you phone. Now it should really be working ok again.
If you little P9-Lite refuses to update to a newer version, use Firmware Finder to upgrade whatever version FullOTA-MF-PV you want to (in my case, I did to B370).
Enjoy
I'm still wondering why installing the wrong rollback package messes up with the recovery2 partition...

Mairtrus said:
Thanks, pal, but I already fixed it, doing a lot of trial-errors
If someone who had the same problems I had is reading this, what you really need to do is:
As Dadditz said, flash first your correct oem info, then unlock the bootloader
If you can't access dload, find the full-ota package for the exact same version of MM you previously had (before the brick, of course). Unzip the UPDATE.APP and then use UpdateExtractor to get BOOT, SYSTEM, RECOVERY, RECOVERY2 and CUST. Flash all of them via Fastboot.
If you try to boot and it gets into eRecovery, then it's a good sign. Put the UPDATE.APP from the previous step in the dload folder of your SD, use the dload method and let the install run. It will probably fail at the end, this seems to be normal.
You phone will boot and it will probably feel like it's working ok again, but I bet there are chances that a some stuff doesn't work or even appear at all (first time the fingerprint config didn't appeared to me, second time was the google account login). Turn off the phone, install the correct version of TWRP, wipe cache/dalvik, then do a factory reset (dunno if both are needed, I just did it this way and it worked ok).
Reboot you phone. Now it should really be working ok again.
If you little P9-Lite refuses to update to a newer version, use Firmware Finder to upgrade whatever version FullOTA-MF-PV you want to (in my case, I did to B370).
Enjoy
I'm still wondering why installing the wrong rollback package messes up with the recovery2 partition...
Click to expand...
Click to collapse
Yep, factory reset + wipe cache did the work..
Cheers