[ [SOLVED] - - See Post #4
Have Nokia 7.2 (TA-1178 - - December Update Software Build 00WW_1_390)
Confirmed both Bootloader unlocked and USB debugging selected.
Trying to root using Magisk. I have also tried TWRP (Official and Unofficial).
All commands seem to work except
fastboot boot xxxx.img
OR
fastboot flash boot xxxx.img
I always get - - fastboot( FAILED (Write to device failed (No Error)
-- UPDATE --
Getting a bit further.
I did not have latest platform-tools. Most recent Tools still doesn't solve my overall dilemma of rooting.
I have changed the fastboot error message, so guess that is some progress.
Still looking for any suggestions.
I'm pretty sure that the December update patched the ability to unlock the bootloader.
SenyorMauricio said:
I'm pretty sure that the December update patched the ability to unlock the bootloader.
Click to expand...
Click to collapse
@SenyorMauricio I believe you are correct; however, I unlocked bootloader prior to accepting December update. I do have the update and have confirmed bootloader is still unlocked.
Thanks for the suggestion. That was one of my initial concerns before confirming.
[SOLVED]
I was finally successful, but pulled info from multiple places.
To help others I will do my best to list my process
If anyone has suggested edits please let me as my goal is to have one location for individuals to find information they need.
NOTE - I Am Not Responsible for bricked devices
REQUIREMENTS
1) Applicable USB cable and Computer with available USB 2 port - Note that I was unsuccessful with USB 3+ ports
2) Latest Android Platform-Tools for your Operating System(OS) https://developer.android.com/studio/releases/platform-tools
3) Latest USB / Nokia Drivers for your (OS) if not already installed. - You will need to verify and search for if needed.
4) Nokia 7.2 with unlocked bootloader (see link below if not unlocked) (My Model is TA-1178)
5) Patience
Comments Before Beginning
NOTE - I Am Not Responsible for bricked devices
UNLOCKING BOOTLOADER
NOTE: Unlocking the bootloader may void the device's warranty.; additionally all existing data on the device will be erased.
CONTINUED
[SOLVED - CONTINUED]
I unlocked the bootloader following the guidance from @singhnsk
https://forum.xda-developers.com/nokia-7-2/how-to/guide-unlocking-bootloader-t3994617
Once bootloader was unlocked I rooted my device following Option 1 on the following page.
I was not interested in a custom recovery.
https://www.techmesto.com/root-nokia-7-2-6-2/
I hope this information is helpful
bkttk2
Related
Dear Esteemed XDA members,
I have spent literally days of testing and researching to try and unbrick my phone. Friends and family have seen my obsession with trying to fix this, some even offering to buy me a new phone!!!! But this ain't about money - this is about having control of my damn device!!! I'm usually pretty good with trying to solve this kind of stuff, but this time I'm truly stumped (and desperate, and obsessed!). I have come to the conclusion that it's directly related to ARM Trusted Firmware. Here are the details of my "journey" to date... please read it, and if you know how to fix it, please share!!! then I can get my life back!!!! Before I go any further, I am certain that my problem was initially triggered by doing an official update on a rooted phone. So to avoid experiencing the same problem I'm about to describe, it's best to unroot and relock your device before loading new official firmware.
I have a Huawei Honor 4x (Che2-UL00, with Kirin 620 chipset) with an unlocked bootloader. Recently, I tried to manually upgrade from Kitkat (emui3.0) to Lollipop (emui3.1), using the official update.app from huawei's website (image was good - I checked the hash). To load the update.app, I used the official huawei recovery. The progress bar went to roughly 90% and then hung. Upon restarting my phone, it went into rescue mode with the following error: Func NO : 15 (bl31 image) Error NO : 1 (security verify failed).
Interestingly, I looked closely at the fastboot.img files for kitkat Vs lollipop (I got the image files by using HuaweiUpdateExtractor). I noticed that only the lollipop fastboot image contains this error message text. Also, bl31 is related to ARM trusted firmware, for more info search for BL31 (Secure Monitor) on google, or see bl31_main.c in the Trusted Firmware source code. So it seems that the lollipop image is using the full ARM trusted firmware, an extra layer of security which is preventing the (unlocked) bootloader from allowing me to load into recovery. I think this is the core problem, and I think there is a way to solve it but I just don't have a deep enough understanding to get there. Below I'll explain each step I went though and provide some additional diagnostic info:
1. First step was to access recovery mode (Vol UP + power). This failed and resulted in same bl31 error message.
2. Second step was to try and update again using the three-button force update (Vol Up + Vol Down + Power). It vibrates once after a few seconds, and freezes with the logo screen with the red light flashing. As an experiment, I tried this without the SDCARD and noticed it vibrated almost instantly, which suggests that it does try to load something from the SDCARD when inserted. I didn't get any further in this mode.
3. Final step I tried was to load into fastboot (Vol Down + Power). This worked and I got into a special "Rescue&Fastboot" mode. First thing I tried was to manually downgrade to kitkat by flashing the kitkat images using the fastboot flash command. The images boot.img, system.img, recovery.img flashed successfully. cust.img simply failed. I desperately wanted to flash the kitkat fastboot.img which doesn't contain the trusted firmware bl31 image stuff, but fastboot replied: FAILED (remote: Command not allowed). In fact, many of the fastboot commands fail with this same error message, even though there is the "PHONE unlocked" writing in red on my phone screen. With the limited command set available (even fastboot oem device-info is not allowed!), here is the diagnostic info I was able to get:
a) fastboot oem check-rootinfo
(bootloader) old_stat: RISK
(bootloader) now_stat: SAFE
(bootloader) change_time: 1452356543
I think this change from RISK to SAFE is the core of my problem. the change_time is from several days ago when I attempted to update. I think it reflects the trusted firmware state (I'm guessing here, as I can't find documentation for these commands).
b) fastboot oem backdoor info
(bootloader) FB LockState: LOCKED
(bootloader) USER LockState: UNLOCKED
I think that FB LockState: LOCKED means that fastboot is locked (guessing again, can't find documentation!), which explains why many of the commands fail.
c) fastboot oem check-image
(bootloader) secure image verify successfully
I think this checks the recovery image, because when I flash a different recovery, this signature check fails
d) fastboot getvar rescue_phoneinfo
rescue_phoneinfo: Che2-UL00 V100R001CHNC00B365
This appears to be the ROM version at the time of purchase.
e) fastboot oem get-build-number
(bootloader): Che2-UL00 V100R001CHNC00B384
This actually corresponds to the build number of kitkat I was using just before the failed upgrade to lollipop.
f) fastboot oem relock mycode
FAILED (remote: root type not allowed).
I tried this just to see if it wold relock. I'm not sure what the error means, but I do not that this command failed with signature verify fail if i change the recovery image.
Here are the questions I want to ask:
1. Can I force the device to flash a new image? I can't get into recovery or have full access to fastboot commands due to the trusted firmware stuff. And as I mentioned earlier the three button trick fails with a freeze at the logo screen. It appears that I need to do this using a means other than fastboot. The only interface I have is Android Sooner ADB Interface. adb devices renders nothing. Only fastboot finds a device.
2. Can I somehow make the "security verify check" pass so that I don't get that bl31 error? I'm not sure exactly which images this bl31 thing is trying to verify! Perhaps some combination of images from the new lollipop stuff I tried to flash and the kitkat build I had running previously?
3. Can somehow disable all this Trusted Firmware stuff??
4. Any other suggestions???
This is driving me to the brink on insanity!!! Gotta figure it out!! Thanks for reading and trying to help!
Hi,
Did anyone solve this problem?
I'm facing the exact same situation.
Che2-UL00 too.
Thanks in advance!
prezident36 said:
Hi,
Did anyone solve this problem?
I'm facing the exact same situation.
Che2-UL00 too.
Thanks in advance!
Click to expand...
Click to collapse
I still find it hard to believe this problem absolutely cannot be solved. However, I took it to a Huawei service center and they weren't able to unbrick it either. They had to replace the mainboard, which seems like a complete waste. Cost around $50, so not the end of the world but still annoying.
Anyway, screw this whole "trusted firmware" rubbish. I'm the owner of the device, yet I'm not "trusted".
hello, i have exactly the same problem!
---------- Post added at 10:58 PM ---------- Previous post was at 10:41 PM ----------
Where do i get the replacement mainboard from?
Me too, upgrading kitkat to lollipop. Now facing that rescue error.
My Honor 4X is unlock bootloader and root before upgrading lollipop,
Hello guys,
I'm not a noob when we speak about flashing ROMs and unlocking bootloaders. I've been doing that for some years. Yesterday I flashed the new stock ROM for LG G4 - v29a, android 7.0. Everything went fine. Later this day, I've seen a post claiming that it was possible to relock your bootloader with this specific ROM using the fastboot oem lock. And it worked indeed. The problem now is that when I turn on the phone the following message shows up on RED: "Your device is corrupt. It cannot be trusted and may not work properly".
So, here's the problem:
1 - Can't access recovery;
2- Can't access download mode;
3 - Can't boot normally;
4 - Can't re-unlock since (i guess) the IMEI is now 0;
5 - Can't flash stock ROM using LGUP;
6- Can't erase any partition via adb since the bootloader is now locked;
So, basically all my ways are locked. Any fix you know and want to share?
I read other threads with the same issue, before post this , but i cant solve it yet
Rooted HDX 4.5.5.3 -Check
Set developer mode on the Kindle -Check
Allow USB Depuration before proceed -Check
Downloaded ADB Composite Drivers / Unlock Bat's / ADB Interface- Check
I run as admin both files without problems, abut the error appears when kindle reboots "Unlock Failed- Unlock code is not correct"
(The files are placed on the correct site,by the way)
I tried
Download again ADB + Fastboot
Reinstall ADB Composite Drivers
Reboot Kindle
Download again Unlock files from original thread
Erase mutiple times unlock.code
No sucess at this point
Any suggestion its apreciated, serial number seems ok
I dont try downgrade yet , because someone post recently he bricks his device using this procedure, so i prefer stay away if is possible.
Yousucks2 said:
I read other threads with the same issue, before post this , but i cant solve it yet
Rooted HDX 4.5.5.3 -Check
Set developer mode on the Kindle -Check
Allow USB Depuration before proceed -Check
Downloaded ADB Composite Drivers / Unlock Bat's / ADB Interface- Check
I run as admin both files without problems, abut the error appears when kindle reboots "Unlock Failed- Unlock code is not correct"
(The files are placed on the correct site,by the way)
I tried
Download again ADB + Fastboot
Reinstall ADB Composite Drivers
Reboot Kindle
Download again Unlock files from original thread
Erase mutiple times unlock.code
No sucess at this point
Any suggestion its apreciated, serial number seems ok
I dont try downgrade yet , because someone post recently he bricks his device using this procedure, so i prefer stay away if is possible.
Click to expand...
Click to collapse
You need to install a vulnerable bootloader before unlocking. See step #2 in OP of linked thread. Scroll to the end of that thread to secure the referenced files as links in the OP are dead. Proceed with caution; a simple mistake can yield a world of hurt and potentially an unrecoverable device.
If your device is rooted you do NOT need to downgrade.
Yeah im following the steps correctly, i try again on my desktop tonight with Windows Vista , i think its some issue with W10 FCU on the laptop, when i tried unlock bootloader on my Blu Life One X2 on w10 , the system show excatly the same issues with unlocking tools, i repply the results
Yousucks2 said:
Yeah im following the steps correctly, i try again on my desktop tonight with Windows Vista , i think its some issue with W10 FCU on the laptop, when i tried unlock bootloader on my Blu Life One X2 on w10 , the system show excatly the same issues with unlocking tools, i repply the results
Click to expand...
Click to collapse
Can you boot into TWRP after completing step #2 of the unlock procedure? If not it is likely the vulnerable bootloader (ABOOT) was not properly installed.
Step #2 can be performed independent of steps #1 and #3. IMO it should be the first step taken after rooting. There is no need to generate an unlock code (step #1) prior to installing and testing the vulnerable bootloader and TWRP (step #2).
Davey126 said:
Can you boot into TWRP after completing step #2 of the unlock procedure? If not it is likely the vulnerable bootloader (ABOOT) was not properly installed.
Step #2 can be performed independent of steps #1 and #3. IMO it should be the first step taken after rooting. There is no need to generate an unlock code (step #1) prior to installing and testing the vulnerable bootloader and TWRP (step #2).
Click to expand...
Click to collapse
Sucess on my desktop PC , i have fully working TWRP and unlock code at the first try, dont know why fails on my laptop every time i tried, on the Blu Life X2 the bootloader and TWRP needs be patched to work on W10 , probably some issue with drivers or something weird, if someone have this issue try on other computer with old OS, thanks for the assistance
what should I do when vulnerable bootloader (ABOOT) was not properly installed
Davey126 said:
Can you boot into TWRP after completing step #2 of the unlock procedure? If not it is likely the vulnerable bootloader (ABOOT) was not properly installed.
Step #2 can be performed independent of steps #1 and #3. IMO it should be the first step taken after rooting. There is no need to generate an unlock code (step #1) prior to installing and testing the vulnerable bootloader and TWRP (step #2).
Click to expand...
Click to collapse
I can't boot into TWRP after installing aboot_vuln.mbn. What should I do now? My tablet can only get into fastboot.
hello please advice! How do I unlock the bootloader at this point and do root with magisk? please describe step by step instructions or link to instructions. sorry because this thread must be here, but I didn't find anything current. I think it's better to get advice than to do wrong and then look for how to restore your phone from a broken state.
my build: Andoid 8.0.0 Emui 8.0.0 PRA-LX1 8.0.0.401 (C432)
Phone locked, FRP unlocked
Thank you very much
niki.rsb said:
hello please advice! How do I unlock the bootloader at this point and do root with magisk? please describe step by step instructions or link to instructions. sorry because this thread must be here, but I didn't find anything current. I think it's better to get advice than to do wrong and then look for how to restore your phone from a broken state.
my build: Andoid 8.0.0 Emui 8.0.0 PRA-LX1 8.0.0.401 (C432)
Phone locked, FRP unlocked
Thank you very much
Click to expand...
Click to collapse
Huawei doesn't unlock bootloader's any more.
You'll have to find a pay service that supports your model.
Sent from my HD1907 using Tapatalk
@niki.rsb
In order to root device's Android unlocking device's boot-loader isn't a pre-requisite.
Rooting a phone's Android means giving user and/or applications administrative rights, will say unrestricted access to Android's system files.
jwoegerbauer said:
@niki.rsb
In order to root device's Android unlocking device's boot-loader isn't a pre-requisite.
Rooting a phone's Android means giving user and/or applications administrative rights, will say unrestricted access to Android's system files.
Click to expand...
Click to collapse
Wrong... you can't flash a patched boot.img without an unlocked bootloader
the only way to root the device is with a Magisk_patched boot.img
clsA said:
Wrong... you can't flash a patched boot.img without an unlocked bootloader
the only way to root the device is with a Magisk_patched boot.img
Click to expand...
Click to collapse
You should carefully read instead of replying nonsense.
I don't understand English well. I don't understand it now. I think everyone writes something different. i need root via magisk to be able to connect google pay with credit card. so the bootloader only goes through the paid service? and then proceed to root?
niki.rsb said:
I don't understand English well. I don't understand it now. I think everyone writes something different. i need root via magisk to be able to connect google pay with credit card. so the bootloader only goes through the paid service? and then proceed to root?
Click to expand...
Click to collapse
You can only unlock bootloader with a paid service.
Once the bootloader is unlocked you can use magisk and patch and then flash a rooted boot.img
Instructions for making the patched boot.img are here > https://topjohnwu.github.io/Magisk/install.html
you get the correct stock boot.img from a full firmware update.zip for your version
Bootloader Unlock Instructions found here > https://techelucid.com/unlock-bootloader-huawei/
Pre-Requisites for unlocking bootloader
Enable USB Debugging
Install USB Drivers for Huawei 98 Lite:
USB Debugging:
Goto Settings> About Phone Tap 7 Times on Build Number
Then In Settings>Developer Options and enable USB Debugging
Tick The “Oem Unlock” Checkbox
Download the following things for Huawei Device
Get and Install USB Drivers on your computer from here
Download DC Huawei Bootloader Codes from here.
Get DC Unlocker client app from here.
Buy Dc Unlocker Credit With Android App
Download and install “DC Huawei Bootloader Codes Android app“ from the link given above in downloads section.
Open the downloaded apk file and install it on your device.
Click on DC Unlocker Account.
Type your email id and complete the payment processes.
After successful payment; save the user password. You will need this while using DC unlocker pc app.
Get Huawei Bootloader Unlock Code With Dc Unlocker
Extract the downloaded DC Unlocker client app zip file.
Double click or Run dc-unlocker2client.exe.
Move to the server tab and log in. use the user password which you got in DC Huawei Bootloader Codes Android app.
Connect your device to pc and enable Manufacturer Mode (You can easily enable manufacturer mode by Typing *#*#2846579#*#* in the dial pad. After that click on Background settings > USB port settings > Manufacturer Mode).
Select the Manufacturer type “Huawei Phones” Model “Auto Detect”. After that click on the search button.
Click on Unlocking Tab. After that choose Read Bootloader Code.
Wait for some time to Unlock code to arrive. When it does, copy the data and save it in a notepad file.
Last step to Unlock Bootloader
Turn off your device.
Put it in Fastboot mode by pressing Volume down + Power button at the same time.
Connect your device to a PC with the USB cable.
Enter The Unlock Code In Code In Command prompt Window and press Enter.
Wait for a few seconds and your device will restart.
You can now go ahead and customize your device by installing TWRP or then flash SuperSu Magisk to root it. So you have succeeded to unlock your Huawei bootloader. .
Click to expand...
Click to collapse
with the bootloader unlocked you don't actually need TWRP
you can fastboot flash the patch_boot.img
just use the command
fastboot flash boot patched_boot.img
thank you for the instructions. But unfortunately the bootloader is still locked. I followed the instructions. it wrote me the bootloader number. But when I opened the command line and wrote the number, then nothing did. where should i open the dashboard? classic C: \ Windows \ system32>?
I will also provide a transcript of the dc unlocker
Check account status
User: bl21816
Credits left: 4
Activated features:
Software debugger
=============================================== ================
Before detection Huawei Android phones, enable 'Manufacture' mode:
in dial pad type * # * # 2846579 # * # * for Qualcomm and Kirin based models, or * # * # 14789632 # * # * for MTK, then select
'ProjectMenu',
'Background settings',
'USB ports settings',
'Manufacture mode'.
Step by step guide for other Huawei phone unlock:
https://www.dc-unlocker.com/huawei_phones_detect_unlock_tutorials
=============================================== ================
DC - Unlocker 2 Client 1.00.1431
Detecting phone:
selection:
manufacturer - Huawei phones
model - Auto detect (recommended)
Found Applications port COM7
=============================================== ================
Check account status
User: bl21816
Credits left: 4
Activated features:
Software debugger
Unlock Auto detect (recommended) cost 4 Cr
Service text tutorial: https://www.dc-unlocker.com/huawei-android-hisilicon-unlock-guide
=============================================== ================
=============================================== ================
DC - Unlocker 2 Client 1.00.1431
Detecting phone:
selection:
manufacturer - Huawei phones
model - Auto detect (recommended)
Found Applications port COM7
=============================================== ================
Reading bootloader code ...
Bootloader code: 9x9x2x2x2x8x5x3x
=============================================== ================
=============================================== ================
DC - Unlocker 2 Client 1.00.1431
Detecting phone:
selection:
manufacturer - Huawei phones
model - Auto detect (recommended)
Found Phone: PRA-LX1
Model: Huawei phone in fastboot mode
IMEI: 866386030063396
Serial NR. : 9DC7N17728006152
Firmware: PRA-LX1 8.0.0.401 (C432
IMEI1: 866386030090407
FB LockState: LOCKED
USER LockState: LOCKED
locked
Battery state: 4068mv
=============================================== ================
Check account status
User: bl21816
Credits left: 0
Activated features:
Software debugger
Unlock Huawei phone in fastboot mode (866386030063396) cost 15 cr
Server message:
Check prices at: https://www.dc-unlocker.com/buy/user_prices
Insufficient credits!
=============================================== ================
niki.rsb said:
i need root via magisk to be able to connect google pay with credit card. so the bootloader only goes through the paid service? and then proceed to root?
Click to expand...
Click to collapse
Right after you root Android OS, Google Pay will stop working. How to bypass this in detail is explained here.
Again:
It's a misconception if people like you think the bootloader of a device has to be unlocked in order to root device's Android OS. These people just don't know what role the bootloader has, just don't know what rooting Android OS means.
niki.rsb said:
I will also provide a transcript of the dc unlocker
Check account status
User: bl21816
Credits left: 4
Activated features:
Software debugger
=============================================== ================
Before detection Huawei Android phones, enable 'Manufacture' mode:
in dial pad type * # * # 2846579 # * # * for Qualcomm and Kirin based models, or * # * # 14789632 # * # * for MTK, then select
'ProjectMenu',
'Background settings',
'USB ports settings',
'Manufacture mode'.
Step by step guide for other Huawei phone unlock:
https://www.dc-unlocker.com/huawei_phones_detect_unlock_tutorials
=============================================== ================
DC - Unlocker 2 Client 1.00.1431
Detecting phone:
selection:
manufacturer - Huawei phones
model - Auto detect (recommended)
Found Applications port COM7
=============================================== ================
Check account status
User: bl21816
Credits left: 4
Activated features:
Software debugger
Unlock Auto detect (recommended) cost 4 Cr
Service text tutorial: https://www.dc-unlocker.com/huawei-android-hisilicon-unlock-guide
=============================================== ================
=============================================== ================
DC - Unlocker 2 Client 1.00.1431
Detecting phone:
selection:
manufacturer - Huawei phones
model - Auto detect (recommended)
Found Applications port COM7
=============================================== ================
Reading bootloader code ...
Bootloader code: 9x9x2x2x2x8x5x3x
=============================================== ================
=============================================== ================
DC - Unlocker 2 Client 1.00.1431
Detecting phone:
selection:
manufacturer - Huawei phones
model - Auto detect (recommended)
Found Phone: PRA-LX1
Model: Huawei phone in fastboot mode
IMEI: 866386030063396
Serial NR. : 9DC7N17728006152
Firmware: PRA-LX1 8.0.0.401 (C432
IMEI1: 866386030090407
FB LockState: LOCKED
USER LockState: LOCKED
locked
Battery state: 4068mv
=============================================== ================
Check account status
User: bl21816
Credits left: 0
Activated features:
Software debugger
Unlock Huawei phone in fastboot mode (866386030063396) cost 15 cr
Server message:
Check prices at: https://www.dc-unlocker.com/buy/user_prices
Insufficient credits!
=============================================== ================
Click to expand...
Click to collapse
Simply getting the code isn't enough you have to flash it see below and see the tutorial for dc unlocker here > https://forum.xda-developers.com/honor-7x/how-to/how-to-unlock-huawei-bootloader-removal-t3780903
Using your Unlock Code:
1. Turn off your phone, Boot your device into Fastboot mode with Vol down and power button.
2. CD to where you downloaded ADB/Fastboot Tools
Run these commands when inside ADB tools directory
a) fastboot devices. (your device should bee listed. If not reinstall drivers/reboot)
b) fastboot oem get-bootinfo (just to confirm everything is detected correctly
c) fastboot oem unlock 9x9x2x2x2x8x5x3x
3. Acknowledge the prompt on your phone. Device will be WIPED!
4. Once the wipe finishes it will take several minutes for phone to boot up. Do not panic. Once you See Huawei logo you are OK!
Click to expand...
Click to collapse
Note: I just read that whole thread (below) and the tutorial is out of date.
it's much easier to root now using the magisk patched_boot.img
see my post earlier on how it's done
instructions for unlocking and rooting your phone here > https://forum.xda-developers.com/p8lite/general/guide-unlock-bootloader-root-device-t3977067
He even has a free method to get the bootloader unlock code (Seems you already have yours above)
Other useful links I found during my search
HiSuite 5.0.2.300 - https://androidmtk.com/download-huawei-hisuite
Multi-Tool for Huawei - https://pro-teammt.ru/multi-tool-for-huawei-honor/
Firmware Database > https://pro-teammt.ru/en/online-firmware-database-ru/
Huawei update extractor > https://firmwarecare.com/huawei-update-extractor-v0-9-9-5
How to extract Huawei firmware and its UPDATE.APP > https://nerdschalk.com/extract-huawei-firmware-update-app/
jwoegerbauer said:
Right after you root Android OS, Google Pay will stop working. How to bypass this in detail is explained here.
Again:
It's a misconception if people like you think the bootloader of a device has to be unlocked in order to root device's Android OS. These people just don't know what role the bootloader has, just don't know what rooting Android OS means.
Click to expand...
Click to collapse
Yes you're right. I don't know exactly how it works and I don't understand it. But that's why I turned here and ask for advice on how to proceed. If I had knowledge, I wouldn't bother anyone to help me. I don't think this is anything new.
clsA said:
Simply getting the code isn't enough you have to flash it see below and see the tutorial for dc unlocker here > https://forum.xda-developers.com/honor-7x/how-to/how-to-unlock-huawei-bootloader-removal-t3780903
Note: I just read that whole thread (below) and the tutorial is out of date.
it's much easier to root now using the magisk patched_boot.img
see my post earlier on how it's done
instructions for unlocking and rooting your phone here > https://forum.xda-developers.com/p8lite/general/guide-unlock-bootloader-root-device-t3977067
He even has a free method to get the bootloader unlock code (Seems you already have yours above)
Other useful links I found during my search
HiSuite 5.0.2.300 - https://androidmtk.com/download-huawei-hisuite
Multi-Tool for Huawei - https://pro-teammt.ru/multi-tool-for-huawei-honor/
Firmware Database > https://pro-teammt.ru/en/online-firmware-database-ru/
Huawei update extractor > https://firmwarecare.com/huawei-update-extractor-v0-9-9-5
How to extract Huawei firmware and its UPDATE.APP > https://nerdschalk.com/extract-huawei-firmware-update-app/
Click to expand...
Click to collapse
Yes there are a lot of versions and procedures for how to root them on the internet. Some don't work, others worked, but currently they don't either. Or there may be new better practices. For a person who does not have much knowledge, it is very difficult to choose the right one. If what you are saying is new and mainly functional, I will look and try to proceed
niki.rsb said:
Yes there are a lot of versions and procedures for how to root them on the internet. Some don't work, others worked, but currently they don't either. Or there may be new better practices. For a person who does not have much knowledge, it is very difficult to choose the right one. If what you are saying is new and mainly functional, I will look and try to proceed
Click to expand...
Click to collapse
first just get the bootloader unlocked
I'll show you how to extract and create a rooted boot.img
clsA said:
first just get the bootloader unlocked
I'll show you how to extract and create a rooted boot.img
Click to expand...
Click to collapse
I have the bootloader unlocked. Is it now necessary to install twrp for magisk? and how do you please proceed?
niki.rsb said:
I have the bootloader unlocked. Is it now necessary to install twrp for magisk? and how do you please proceed?
Click to expand...
Click to collapse
Excellent !!
We need your firmware version to get the correct ramdisk.img
look in settings / about phone for the firmware version or just post a screen shot of that screen
this is your file (I got it from your first post) > PRA-LX1 8.0.0.401 (C432) FullOTA-MF > https://pro-teammt.ru/en/online-fir...mware_model=PRA-LX1+8.0.0.401&firmware_page=0
download the update.zip (I'm downloading it also)
Next download the Huawei update extractor > https://firmwarecare.com/huawei-update-extractor-v0-9-9-5
I posted the guide here for using the extraction tool > https://nerdschalk.com/extract-huawei-firmware-update-app/
and then follow this guide to root the ramdisk.img
Huawei
Huawei devices using Kirin processors have a different partitioning method from most common devices. Magisk is usually installed to the boot partition of the device, however Huawei devices do not have this partition. Depending on what EMUI version your device is running, the instructions will be slightly different.
Obtain Stock Images
Huawei does not release official factory images, however most firmware zips can be downloaded from the Huawei Firmware Database. To extract images from UPDATE.APP in the zip, you have to use Huawei Update Extractor (Windows only!)
EMUI 8
For EMUI 8 devices, your device has a partition named ramdisk, which is where Magisk is going to be installed.
If you plan to use custom recoveries, simply follow the instructions for custom recovery and you’re all set.
If you plan not to use custom recoveries, you will have to extract RAMDISK.img from your firmware. Follow the instructions for boot image patching above, but use the RAMDISK.img file instead of a boot image.
To flash the patched image to your device, here is the fastboot command:
fastboot flash ramdisk /path/to/magisk_patched.img
Be aware you are flashing to ramdisk, not boot!
Click to expand...
Click to collapse
Boot Image Patching
You would want to choose this method if either your device does not have custom recoveries, your device is A/B and you don’t want to mix recovery and boot images, or your device is using system-as-root without A/B partitions.
To use this method, you are required to obtain a copy of the stock RAMDISK.img, which can be found by extracting OEM provided factory images or extracting from OTA update zips. If you are unable to obtain one yourself, you might be able to find it somewhere on the internet. The following instructions will guide you through the process after you have the copy of boot/recovery image.
Copy the RAMDISK.img to your device
Download and install the latest Magisk Manager
If you are patching a recovery image, manually check “Recovery Mode” in Advanced Settings!
Press Install → Install → Select and Patch a File, and select your stock RAMDISK.img file
Magisk Manager will patch the image, and store it in [Internal Storage]/Download/magisk_patched.img
Copy the patched image from your device to your PC. If you can’t find it via MTP, you can pull the file with ADB:
adb pull /sdcard/Download/magisk_patched.img
Flash the patched RAMDISK.img to your device and reboot. For most devices, here is the fastboot command:
fastboot flash ramdisk magisk_patched.img
fastboot flash boot /path/to/magisk_patched.img or
fastboot flash recovery /path/to/magisk_patched.img if you are patching a recovery image
Click to expand...
Click to collapse
now use fastboot reboot
at this point your phone should be rooted
I uploaded the patched ramdisk.img here if you have trouble > https://www.androidfilehost.com/?fid=8889791610682890848
the unpatched RAMDISK.IMG is also their > https://www.androidfilehost.com/?w=files&flid=314978
You also have TWRP 3.11 available for your phone > https://androidfilehost.com/?fid=1899786940962602140
it's ease to flash TWRP and then root your phone with a Magisk.zip in TWRP
it's also nice if you like to flash roms or make backups of your system and data
clsA said:
this is your file (I got it from your first post) > PRA-LX1 8.0.0.401 (C432) FullOTA-MF > https://pro-teammt.ru/en/online-fir...mware_model=PRA-LX1+8.0.0.401&firmware_page=0
download the update.zip (I'm downloading it also)
Click to expand...
Click to collapse
I did not find a download file or a link where I can download, so I download here
https://androidhost.ru/1iXE is it ok?
yes build number is PRA-LX1 8.0.0.401 (C432) Emui 8, Android 8
And what is the difference between when I run through that ramdisk.img or when I make a flash twrp and install magisk.zip??
niki.rsb said:
I did not find a download file or a link where I can download, so I download here
https://androidhost.ru/1iXE is it ok?
yes build number is PRA-LX1 8.0.0.401 (C432) Emui 8, Android 8
And what is the difference between when I run through that ramdisk.img or when I make a flash twrp and install magisk.zip??
Click to expand...
Click to collapse
I posted the patched ramdisk.img for you
all you need to do is copy it to your adb/fastboot folder and reboot your phone to fastboot mode and flash it
fastboot flash ramdisk magisk_patched.img
their is no difference in the end result, either method will work to Root your phone
clsA said:
I posted the patched ramdisk.img for you
all you need to do is copy it to your adb/fastboot folder and reboot your phone to fastboot mode and flash it
fastboot flash ramdisk magisk_patched.img
their is no difference in the end result, either method will work to Root your phone
Click to expand...
Click to collapse
I did exactly and just what you wrote. the flash completed without error, but I don't know what the result should have been. I don't even have root, magisk, I didn't know the change.
niki.rsb said:
I did exactly and just what you wrote. the flash completed without error, but I don't know what the result should have been. I don't even have root, magisk, I didn't know the change.
Click to expand...
Click to collapse
Install magisk manager if it's not in your app drawer
Hey All!
I recently(2 days back) purchased a Yu Yutopia running android 5.1.1. I enabled developer options, but it didn't have the OEM unlock option. And whenever i go into fastboot, and type
Code:
fastboot -i 0x2A96 oem unlock
it says
FAILED (remote: unknown command)
finished. total time: 0.008s
Click to expand...
Click to collapse
.. Any help would be appreciated. I went through tons of documentation. the only thing missing for now is the Yutopia Drivers. Is that the problem? If so, can someone share the driver packs? This thread had it, but the link is broken, and is old.
If in Android -> Settings -> Developer options -> OEM unlock option isn't present then unlocking phone's bootloader is denied, you can't unlock it by means of Fastboot.
May be you can obtain from OEM/Carrier an unlock-key. Contact them.
BTW: You always can check Android's system file named build.prop for device's bootloader-unlock capability
Code:
adb devices
adb shell "getprop ro.oem.unlock_supported"
If the device supports "fastboot flashing unlock", then the returned value is 1
Soham41 said:
Hey All!
I recently(2 days back) purchased a Yu Yutopia running android 5.1.1. I enabled developer options, but it didn't have the OEM unlock option. And whenever i go into fastboot, and type
Code:
fastboot -i 0x2A96 oem unlock
it says .. Any help would be appreciated. I went through tons of documentation. the only thing missing for now is the Yutopia Drivers. Is that the problem? If so, can someone share the driver packs? This thread had it, but the link is broken, and is ol
Click to expand...
Click to collapse
Same here tried everything from flashing in EDL mode to downloading Yuware and trying to unlock bootloader. The adb commands
Code:
getprop sys.oem_unlock_allowed
getprop ro.oem_unlock_supported
both return blank. Using Miracle box software to check device info returns Bootloader : unknown. Trying to root via Miracle Box, Kingroot and other methods fails. The original Signed Android 5.1.1 based CM signed zips also won't flash via Recovery and the links are also almost non existent for those. Any hope of finding a original CM firmware to flash via QFIL is very slim. There has to be some way to get it working, there was a YouTube video showcasing the YU Yutopia on Stock Android 5.1.1 Engineering build that now doesn't have the OEM Unlock option only if someone would help. Getting it rooted somehow god knows how is the only option to get started.
Don't waste more time with trying to unlock phone's bootloader: it's NOT supported.
if anyone interested, I made some modifation in stock rom, so it is rooted, without unlocking bootloader, here is the link of my thread
Yu Yutopia (Yu5050) (Sambar) Stock engineering rom, rooted (Android 5.1)
For those interested, this is exactly engineering rom, with added modified patched boot, so it is rooted with magisk. v23 This is the detailed install procedure: You need to download the following: 1. YU_Yutopia_YU5050_V1_24.12.15 rom, link give...
forum.xda-developers.com