Can't relock bootloader: bad key/unsigned boot.img message - Moto Z2 Play Questions & Answers

Hi,
I'm new to Z2 play ROM/TWRP things and here's my issue on a XT 1710-01 (on retca channel):
After unlocking my bootloader, I've installed TWRP 64 bits and did a backup before doing anything else, but for whatever reason, restoring it didn't work. I just thought then that I could re-flash the retail stock ROM available at https://mirrors.lolinet.com/firmware/moto/albus/official/RETAIL/ , which worked fine (phone boots fine, works fine and is still on retca channel, etc.), except that now, I'm unable to re-lock the bootloader, as I get a message like "signed boot.img required" (or something alike) on "fastboot oem lock" command.
I also get the "bad key" message on the unlock warning at boot time (see attached).
Here are the commands I used to reflash the stock ROM:
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
Now, I'm just wondering if I missed something or is it just that the stock ROM I reflashed is not the good one (or just unsigned) . Any help would be appreciate.
Thanks.

Need official signed by Moto image. Not available from any official source unfortunately. I have a same request to lock a bootloader.

it's very important to ask how your parachute Works before you jump off the plane

@KirMit Thanks for the follow-up.
Do you know if it would be an option for me to try to find a complete ROM/backup made by someone with the exact same model (so presumably, with the signed boot.img), flash/restore this backup on my unit and then try to relock the bootloader?

I have the same problem. Cannot find a signed boot.img
If anyone can think of a solution I would be totally interested in hearing about it.
I can live with this phone with the bootloader unlocked, but I may need to sell it, so I need to get rid of that warning screen.

Paulinga said:
I have the same problem. Cannot find a signed boot.img
If anyone can think of a solution I would be totally interested in hearing about it.
I can live with this phone with the bootloader unlocked, but I may need to sell it, so I need to get rid of that warning screen.
Click to expand...
Click to collapse
You can get rid of the warning screen, but you can't get rid of the N/A-Bad Key sign, so you must make your own boot logo (meant to cover those nasty letters with a white background) and ADB flash it as logo.bin... that's if you don't have TWRP recovery; in such case you can use a flashable zip for that matter.
Sent from my Moto Z2 Play using XDA Labs

Please look at this video:
It's in portuguese, but you will understand by just following his steps.
If you want, look at the other videos, all of them will help you(not all are about relocking bl)
If you're on october patch, there is the firmware: https://androidfilehost.com/?fid=11410932744536987421
Thanks to junior passos

xdaVTU said:
Please look at this video:
It's in portuguese, but you will understand by just following his steps.
If you want, look at the other videos, all of them will help you(not all are about relocking bl)
If you're on october patch, there is the firmware: https://androidfilehost.com/?fid=11410932744536987421
Thanks to junior passos
Click to expand...
Click to collapse
Doesn't work on my Z2p. My oem unlock is always greyed out even after trying the instructions in this video with 3 different firmwares.
For anyone who doesn't understand what's going on in the video.
1)flash the firmware.
2)flash twrp, backup boot & system.
3) restore boot and system and reboot
4) go to developer options and, enable oem unlocking
5) return to bootloader and run the lock bootloader bat file.
6)done your locked.
Or if like in my case, it does not work, oem unlocking is still greyed out.

I managed to ungrey oem unlocking but, only by flashing magisk. Somehow magisk ungreys oem unlock? Unfortunately, we cannot lock bootloader with magisk installed. Once magisk is uninstalled, oem unlocking is greyed out again?
I think I know how to get around this, adb pull boot.img that magisk has modified. Full unroot magisk, preferably with magisk uninstall zip. Then fastboot flash the patched boot image and run bootloader lock with the OEM unlock switch set.
---------- Post added at 10:32 PM ---------- Previous post was at 09:49 PM ----------
And I am locked, it worked. I now know how to lock my bootloader even when the video guide above fails to remove the greyed out oem switch.
1)flash the firmware.
2)flash twrp, backup boot & system.
3) restore boot and system
4)flash magisk and reboot
6) back up boot.img to pc
7) flash magisk uninstall zip
8)fastboot flash stock recovery
9) fastboot flash magisk modified boot
10)boot device and enable oem unlocking
11) reboot to bootloader and run bootloader lock bat file
11) oem locked!
By the way, easiest way to back up boot is use the app "partition backup & restore". Be sure to change the setting to save as img and not archive.

Yes! This!
I've never been able to go back to stock and relocking the bootloader because the OEM Unlock was always greyed out. Using the patched boot.img, as @Cupcake 1.5 explains allowed me to lock my bootloader again.
Thank you!
Cupcake 1.5 said:
I managed to ungrey oem unlocking but, only by flashing magisk. Somehow magisk ungreys oem unlock? Unfortunately, we cannot lock bootloader with magisk installed. Once magisk is uninstalled, oem unlocking is greyed out again?
I think I know how to get around this, adb pull boot.img that magisk has modified. Full unroot magisk, preferably with magisk uninstall zip. Then fastboot flash the patched boot image and run bootloader lock with the OEM unlock switch set.
---------- Post added at 10:32 PM ---------- Previous post was at 09:49 PM ----------
And I am locked, it worked. I now know how to lock my bootloader even when the video guide above fails to remove the greyed out oem switch.
1)flash the firmware.
2)flash twrp, backup boot & system.
3) restore boot and system
4)flash magisk and reboot
6) back up boot.img to pc
7) flash magisk uninstall zip
8)fastboot flash stock recovery
9) fastboot flash magisk modified boot
10)boot device and enable oem unlocking
11) reboot to bootloader and run bootloader lock bat file
11) oem locked!
By the way, easiest way to back up boot is use the app "partition backup & restore". Be sure to change the setting to save as img and not archive.
Click to expand...
Click to collapse

TravellingGuy said:
Yes! This!
I've never been able to go back to stock and relocking the bootloader because the OEM Unlock was always greyed out. Using the patched boot.img, as @Cupcake 1.5 explains allowed me to lock my bootloader again.
Thank you!
Click to expand...
Click to collapse
Hi all, ok i'm late unfortunately can you help me ? i have the boot magisk signed and key is ok. But when i'm reflashing recovery stock, there is also a bad key.
So there is still the warning at startup, i think this is due to this issue

smbld said:
Hi all, ok i'm late unfortunately can you help me ? i have the boot magisk signed and key is ok. But when i'm reflashing recovery stock, there is also a bad key.
So there is still the warning at startup, i think this is due to this issue
Click to expand...
Click to collapse
Ha, it's been too long since I used this phone. I can't help, unfortunately.

Related

They found a fix for Nougat bricked phones in N6 thread!

As title says, but we need a working backup. Mine is broken, can someone upload a working one, plz?
This is the howto:
1. Flash a stock image (I used the August stock image MTC20F)
2. Fastboot flash TWRP 3.0.2-0
3. Boot into TWRP
4. Select Wipe -> Advanced Wipe -> Select and repair each partition individually (some won't be able to, and that's fine, just move on to the next one)
5. Restore a full nandroid backup (make sure everything is selected) and reboot
6. You should now be free of the never ending boots, and if your device is bootlooped at this point (stuck at the boot animation), you can just flash stock again.
Thanks for this solution. But I have a problem because after installing the rom file .tot have a locked bootloader, and at this moment I can not do flash twrp.
In order to unlock the bootloader command "fastboot oem unlock" I get the answer that it is not possible. NTR it can not unlock it.
Goes some way to upload twrp with a locked bootloader or a way to unlock?
Danielf85 said:
Thanks for this solution. But I have a problem because after installing the rom file .tot have a locked bootloader, and at this moment I can not do flash twrp.
In order to unlock the bootloader command "fastboot oem unlock" I get the answer that it is not possible. NTR it can not unlock it.
Goes some way to upload twrp with a locked bootloader or a way to unlock?
Click to expand...
Click to collapse
My bootloader is locked, too. The only way to write to the phone seems to be via download mode, but flashing LGH790AT-00-V10f-NXS-XXX-OCT-03-2015-32G-MDA89E-US.tot doesn't work...
To install twrp we need to unlock the bootloader.
However, when the command "fastboot oem unlock" system gives the answer
FAILED (remote: oem unlock is not allowed)
Then how to unlock?
Danielf85 said:
To install twrp we need to unlock the bootloader.
However, when the command "fastboot oem unlock" system gives the answer
FAILED (remote: oem unlock is not allowed)
Then how to unlock?
Click to expand...
Click to collapse
There's really nothing you can do to force an unlock. If you can adb sideload a full OTA zip (say for 7.0) from Google and get that to boot up, that's pretty much your best bet.
Sent from my Nexus 5X using Tapatalk
I mean, the new unlock command is:
fastboot flashing unlock
oc2 said:
I mean, the new unlock command is:
fastboot flashing unlock
Click to expand...
Click to collapse
On Nexus 5X both commands can be used (oem unlock and flashing unlock)
I followed all the steps except I can't boot to recovery...when I try (manually via ADB or automatically using Wug's tool) it just goes back into the bootloop. I can't even boot temporarily to recovery (without flashing). I'm getting close to throwing in the towel...
Did not work for me, sadly
Edit: Here's how I managed to fix the problem
1. Moved Nandroid backup to PC.
2. Download factory image MTC20F from https://developers.google.com/android/nexus/images.
3. Install factory image (This will erase all data on your phone so move your files to your PC).
4. Install TWRP 3.0.2-0 from https://dl.twrp.me/bullhead/twrp-3.0...lhead.img.html via fastboot.
5. Go in TWRP>Wipe>Advanced Wipe and repair all partitions that can be repaired (System, Data, Cache).
6. Restore Nandroid backup.
7. Success.
Hope it works for other people too, cheers
Anyone in Portland Oregon and want to take a crack at unbricking my 5x? LG gave me an RMA, but given it's not a hardware issue, I'm thinking it will be a waste of time to send it in -- I'm worried they'll just say "all your hardware is fine". Happy to buy drinks or pay a bit if someone can get me up and running.

Zenfone2 stuck at bootloader!

Hello all,
I have Zenfone 2 on which I intended to use a custom ROM.
So the first thing was to unlock the bootloader.
On previous occasion, on my Nexus, I had used the - fastboot oem unlock - command and it had worked. So with that in mind, I booted into the bootloader and tried the command, but it failed - saying oem command unrecognized.
Then I searched online and apparently, to unlock the bootloader, Asus has launched an app! But to be able to install the app, I need to get a normal boot happening, which is not happening now.
In between all this, I tried the commands - fastboot flash recovery <recovery.img>, fastboot flash boot <boot.img> too. But none of these were successful, and each of them returned a 'Permission denied' message, probably coz the bootloader was locked.
Now the situation is that -
- Bootloader is locked.
- Phone is stuck in bootloader
- There is no recovery installed. In fact, from the bootloader, when I try to boot into 'Recovery Mode', it goes there for a second and returns back to the bootloader. Doesn't show the normal android image with a 'X' on top.
- There is no root access.
Now I think the first step is to get root access, and for this I want to try the method with installing CWM recovery and SuperSu.
But for this, I need to be able to push the SuperSu.zip to the phone, which I am not able to.
Can somebody please help!
r the drivers for fastboot & adb update to date?
Android version?
If the phone is stuck in bootloader, you can use Asus Flash Tool to flash .raw files and unbrick the phone.
Raw files: https://yadi.sk/d/FijRoAVJtvRiG
AFT: https://yadi.sk/d/NQCiY--IsQjBr (I use AsusFlashToolInstaller1.0.0.14.exe).
you can use Asus Flash Tool to flash .raw files and unbrick the phone.
Click to expand...
Click to collapse
Have to choose wipe the data or not?
hafiz019 said:
Have to choose wipe the data or not?
Click to expand...
Click to collapse
stay away from aft. if will f**k up yor device completely. AFT is too unstable. lot of times it bricks the device to unrecoverable state. tell me the bootloader version, ifwi version shown on screen while in bootloader mode.

Question Rooting - anyone successful?

I've been trying to root my Note 9T. The bootloader has been unlocked, and I've followed a guide from here: https://unofficialtwrp.com/twrp-3-4-2-root-redmi-note-9-5g-cannon/
I'm now stuck in a bootloop.
Anyone been successful?
I additionally tried using a different version of TWRP, which wiped the "misc" partition. Can anyone provide an image dump of the misc partition so I can flash it back on? I can't find a copy of misc in the stock firmware file.
UPDATE 1:
I put the full stock image back on and am back to having a working unrooted phone, so I don't need the misc image. Would really like to get this thing rooted though.
I've installed the Magisk APK, patched the boot image, and flashed it. But this also results in a boot loop. If I flash the stock image back it works again. Any ideas what's going on here?
UPDATE 2:
I got it working! The key was to flash the stock vbmeta.img with fastboot functions to disable it.
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
Hiya. I've tried that and managed to get to the twrp page. However, when I go to install magisk via twrp, it just reboots into a bootloop. Any ideas?
Update: This seems to have worked.
[SOLVED] Phone gets stuck in bootloop if I try to install Magisk ZIP!
From the forum I followed these step to install magisk: - Patched my boot.img of my current rom using Magisk Manager and flashed via fastboot - After rebooting from fastboot it got stuck in recovery so had to wipe all data and it booted finally...
forum.xda-developers.com
Did you manage to get Magisk working after the reinstall of stock firmware, or you've just resolved the bootloop?
dsclee1 said:
I've been trying to root my Note 9T. The bootloader has been unlocked, and I've followed a guide from here: https://unofficialtwrp.com/twrp-3-4-2-root-redmi-note-9-5g-cannon/
I'm now stuck in a bootloop.
Anyone been successful?
I additionally tried using a different version of TWRP, which wiped the "misc" partition. Can anyone provide an image dump of the misc partition so I can flash it back on? I can't find a copy of misc in the stock firmware file.
UPDATE 1:
I put the full stock image back on and am back to having a working unrooted phone, so I don't need the misc image. Would really like to get this thing rooted though.
I've installed the Magisk APK, patched the boot image, and flashed it. But this also results in a boot loop. If I flash the stock image back it works again. Any ideas what's going on here?
UPDATE 2:
I got it working! The key was to flash the stock vbmeta.img with fastboot functions to disable it.
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
Click to expand...
Click to collapse
I'm interesting in at least rooting and if possible install TWRP .
Can you post i complete procedure to root the note 9 T ?
Thanks
I can have a go. But I'm not 100% sure what exact steps I took that got it working, as I flashed and re-flashed several times. Give this a try and let me know if it works or not?
WARNING: EXPECT TO LOSE ALL THE DATA ON YOUR PHONE!
Step 1
Obviously you need to unlock the bootloader first: https://en.miui.com/unlock/
If you haven't done this already, after your application it's likely you might have to wait 7 days before Xiaomi actually let you unlock.
Unlocking wipes your data.
Step 2
Start the phone normally. Copy the latest magisk apk (https://github.com/topjohnwu/Magisk/releases) over to the phone and install it.
Step 3
Find the correct original ROM for your device (https://xiaomifirmwareupdater.com/miui/cannong/). You'll need the full image. From the ROM extract the boot.img and vbmeta.img. Copy the boot.img over to your phone.
Step 4
In magisk choose the option to install and select "Select and Patch a File" (should be the only option anyway). Select the boot.img you copied over. This will produce a new file called something like "magisk_patched-22100_XXXXX.img". Copy this file off your phone and onto your computer.
Step 5
Boot your phone to fastboot mode (you should already know how to do this, as you would have had to have done it to unlock your phone in the first place - Hold down Volume Down and the Power button at the same time).
Step 6
Run the following commands (obviously replace the boot image with the correct magisk image, and use the vbmeta.img you took from the ROM):
Code:
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
fastboot flash boot magisk_patched-22100_XXXXX.img
Hopefully this will work. But I can't be 100% sure, as the disabling of "verity" could mean that your encrypted user data now can't be read (if you've only just unlocked the bootloader then you're not going to have any data anyway, so not too much of an issue). If this is the case it's likely you'll now need to factory reset the phone. Hold down Volume Up and Power on start to reach the stock recovery menu, and there's a selection for factory reset. You can also install TWRP at this point, and could then use it's factory reset function instead. I downloaded this version of TWRP: https://www.mediafire.com/file/ou8553psro9yyt2/3.4.2_redmi_note_9_5G.rar/file, which came from the other rooting guide (https://unofficialtwrp.com/twrp-3-4-2-root-redmi-note-9-5g-cannon/ - which didn't work). Just flash that version of TWRP to the recovery partition (fastboot flash recovery recovery.img), and ignore all the steps given in the guide it came from.
Let me know how you get on.
sorry for the answer delay.
Adding my 2 cents about unlocking the bootlader .
In order to do it .
FIRST - do not try it from a virtual PC . It does not work (at least it did not work for me)
SECOND , before to run the xiaomi batch_unlock bootlader , don't forget to update google usb drivers
I hard some hard time to just connect the unlocker to my phone . Now i have to wait 167 hours to complete the process .
dsclee1 said:
I've been trying to root my Note 9T. The bootloader has been unlocked, and I've followed a guide from here: https://unofficialtwrp.com/twrp-3-4-2-root-redmi-note-9-5g-cannon/
I'm now stuck in a bootloop.
Anyone been successful?
I additionally tried using a different version of TWRP, which wiped the "misc" partition. Can anyone provide an image dump of the misc partition so I can flash it back on? I can't find a copy of misc in the stock firmware file.
UPDATE 1:
I put the full stock image back on and am back to having a working unrooted phone, so I don't need the misc image. Would really like to get this thing rooted though.
I've installed the Magisk APK, patched the boot image, and flashed it. But this also results in a boot loop. If I flash the stock image back it works again. Any ideas what's going on here?
UPDATE 2:
I got it working! The key was to flash the stock vbmeta.img with fastboot functions to disable it.
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
Click to expand...
Click to collapse
ive been trying for the last 4 hours to flash twrp on my redmi note 9T 5g global..can you please explain to me how you got it to work. i flashed the recovery.img and vbmeta.img file that i got from the unofficialtwrp.com download, when i flash boot recovery.img, it just reboots my phone into normal...and i missing something? My device is on Miui 12.0.8.0 andriod 10. should i be on the new update 12.5 andriod 11 for it to work. Please help.
dsclee1 said:
I can have a go. But I'm not 100% sure what exact steps I took that got it working, as I flashed and re-flashed several times. Give this a try and let me know if it works or not?
WARNING: EXPECT TO LOSE ALL THE DATA ON YOUR PHONE!
Step 1
Obviously you need to unlock the bootloader first: https://en.miui.com/unlock/
If you haven't done this already, after your application it's likely you might have to wait 7 days before Xiaomi actually let you unlock.
Unlocking wipes your data.
Step 2
Start the phone normally. Copy the latest magisk apk (https://github.com/topjohnwu/Magisk/releases) over to the phone and install it.
Step 3
Find the correct original ROM for your device (https://xiaomifirmwareupdater.com/miui/cannong/). You'll need the full image. From the ROM extract the boot.img and vbmeta.img. Copy the boot.img over to your phone.
Step 4
In magisk choose the option to install and select "Select and Patch a File" (should be the only option anyway). Select the boot.img you copied over. This will produce a new file called something like "magisk_patched-22100_XXXXX.img". Copy this file off your phone and onto your computer.
Step 5
Boot your phone to fastboot mode (you should already know how to do this, as you would have had to have done it to unlock your phone in the first place - Hold down Volume Down and the Power button at the same time).
Step 6
Run the following commands (obviously replace the boot image with the correct magisk image, and use the vbmeta.img you took from the ROM):
Code:
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
fastboot flash boot magisk_patched-22100_XXXXX.img
Hopefully this will work. But I can't be 100% sure, as the disabling of "verity" could mean that your encrypted user data now can't be read (if you've only just unlocked the bootloader then you're not going to have any data anyway, so not too much of an issue). If this is the case it's likely you'll now need to factory reset the phone. Hold down Volume Up and Power on start to reach the stock recovery menu, and there's a selection for factory reset. You can also install TWRP at this point, and could then use it's factory reset function instead. I downloaded this version of TWRP: https://www.mediafire.com/file/ou8553psro9yyt2/3.4.2_redmi_note_9_5G.rar/file, which came from the other rooting guide (https://unofficialtwrp.com/twrp-3-4-2-root-redmi-note-9-5g-cannon/ - which didn't work). Just flash that version of TWRP to the recovery partition (fastboot flash recovery recovery.img), and ignore all the steps given in the guide it came from.
Let me know how you get on.
Click to expand...
Click to collapse
should I be on the latest version of Miui...12.5 android 11? for me to be able to install twrp. i downgraded back to Miui 12.0.8.0 android 10 as i didnt like my data folder been blocked in android folder. My device is global cannong redmi 9T 5g with diminsity 800u soc, can you please help if you can. thanks in advance
Android 10 is fine. You need to fastboot flash recovery recovery.img
To boot into it you need to turn the phone off, then hold vol up and power until you feel a buzz, then let go.
I have the same Problem as HighEndGamer:
if I enter 'fastboot flash recovery recovery.img', it sayes that everything worked OK in just a few seconds. But nothing realy happend!
If I enter 'fastboot boot recovery.img', phone boot just as normal.
If I enter 'fastboot oem device-info', it sayes "FAILED (remote: unknown command)'.
If I enter 'fastboot oem lock', it works and I have to start from the beginning..
I have MIUI Global 12.0.2.0{QJEEUMX)
chmick said:
sorry for the answer delay.
Adding my 2 cents about unlocking the bootlader .
In order to do it .
FIRST - do not try it from a virtual PC . It does not work (at least it did not work for me)
SECOND , before to run the xiaomi batch_unlock bootlader , don't forget to update google usb drivers
I hard some hard time to just connect the unlocker to my phone . Now i have to wait 167 hours to complete the process .
Click to expand...
Click to collapse
I confirm it does not work from a VM (and the need for latest drivers). There is something funky going on with the USB communication when running from a VM: the first call of the fastboot executable from the windows VM generally works fine, but any other call hang. So the batch_unlock tool cannot work (since it does call fastboot several times).

Relock bootloader on LOS microG

Hello all
I desperately try to relock my bootloader but failed many times and I am shortly before giving up. I was once on a locked bootloader on LOS but camera didn't work. (Couldn't reproduce)
Maybe you see something I missed out / didn't understand.
The main reason is, that some apps like ebanking check the state of the bootloader. And they also don't go through Securenet because of huawei.
So what I tried with this setup:
sign both boot.img and twrp.img with BootSignature.jar using own private key
Twrp Using: twrp-3.5.2_9-0-oneplus3
boot img from:
lineage-17.1-20210330-microG-oneplus3
lineage-18.1-20210403-microG-oneplus3
With firmware: oxygenos-9.0.6-firmware-3 from https://github.com/nvertigo/firmware-3t/tree/master/archive/op3
Mostly I got the ideas from https://forum.xda-developers.com/t/device-forum-rules-please-read-before-posting.3333345/
And what I do is this:
Using fastboot flash signed recovery
boot into recovery
whipe everything (is this needed every time?), data, factory reset, all partitions except internal & usb
reboot into recovery
sideload lineageos with signed boot.img inside
fastboot oem unlock => directly restarts after 'yes'
boot into LOS
fastboot oem unlock => directly restarts after 'yes' again
Do you see something I do wrong? Should I use other versions/files?
Hope to find a way
Edit: Also I can go back to stock where it gets locked again using the latest OnePlus3_16_A.86_191104_repack.

How To Guide how to root redmagic 8 pro step by step

hello everyone this is topic for root redmagic 8 pro easy away
Frist Step Download RedMagic Rom From here
https://rom.download.nubia.com/Europe%26Asia/NX729J/V318/NX729J-update.zip
now open bootloader from developer option
reboot your phone to fast boot then enter this commind
Code:
fastboot flashing unlock
after unlocking boot loader
need to unlock cirital
Code:
fastboot flashing unlock_critical
reboot your phone to fastboot again open fastboot cmd and enter :
fastboot flashing unlock_critical
after finished all setting install magisk apk and patch
init_boot.img and boot.img
copy patch img from phone to windows folder after patch via magisk
now reboot your phone to fastboot and open fastboot cmd enter this cmd
Code:
fastboot flash init_boot_a xxxxxxxx
fastboot flash init_boot_b xxxxxxxx
fastboot flash boot_a xxxxxxx
fastboot flash boot_b xxxxxxxx
replace xxxxx with location patch in windows
I apologize if the explanation is not clear. If you have any questions, ask them here
this way is tested and working 100%
afer download frimware copy to your phone then update via ota local update
topadstore said:
afer download frimware copy to your phone then update via ota local update
Click to expand...
Click to collapse
Have u tried recalibrate fingerprint?
kaiwayne said:
Have u tried recalibrate fingerprint?
Click to expand...
Click to collapse
The fingerprint will not work. Root the device. There are other ways to fix this problem
topadstore said:
The fingerprint will not work. Root the device. There are other ways to fix this problem
Click to expand...
Click to collapse
I already know. The problem is even passing the test, i cant input any screen lock. Everytime i tried this msg appear "Screen lock was already changed. Try again with the new screen lock". Cant pass this step so cant move to fingerprint
topadstore said:
hello everyone this is topic for root redmagic 8 pro easy away
Frist Step Download RedMagic Rom From here
https://rom.download.nubia.com/Europe%26Asia/NX729J/V318/NX729J-update.zip
now open bootloader from developer option
reboot your phone to fast boot then enter this commind
Code:
fastboot flashing unlock
after unlocking boot loader
need to unlock cirital
Code:
fastboot flashing unlock_critical
reboot your phone to fastboot again open fastboot cmd and enter :
fastboot flashing unlock_critical
after finished all setting install magisk apk and patch
init_boot.img and boot.img
copy patch img from phone to windows folder after patch via magisk
now reboot your phone to fastboot and open fastboot cmd enter this cmd
Code:
fastboot flash init_boot_a xxxxxxxx
fastboot flash init_boot_b xxxxxxxx
fastboot flash boot_a xxxxxxx
fastboot flash boot_b xxxxxxxx
replace xxxxx with location patch in windows
I apologize if the explanation is not clear. If you have any questions, ask them here
this way is tested and working 100%
Click to expand...
Click to collapse
You do not need to patch boot.img and flash it, only patching init_boot.img is needed.
kaiwayne said:
I already know. The problem is even passing the test, i cant input any screen lock. Everytime i tried this msg appear "Screen lock was already changed. Try again with the new screen lock". Cant pass this step so cant move to fingerprint
Click to expand...
Click to collapse
Is there this section in the phones settings
Settings > Lock screen & security or Security > Clear credentials.
ugene1980 said:
Is there this section in the phones settings
Settings > Lock screen & security or Security > Clear credentials.
Click to expand...
Click to collapse
Yes but grayed out
kaiwayne said:
Yes but grayed out
Click to expand...
Click to collapse
Did you lock the bootloader again?
Lossani said:
Did you lock the bootloader again?
Click to expand...
Click to collapse
Dont need to ask the same thing everywhere,
Locking bootloader after you rooted = Brick....
Excuse guys, after root is it possible to install a module to enable Hey Google with screen off (or in AOD mode)? Owners said that you can say Hey Google with RM8Pro only with screen on, so sad....
VladimiroCampus said:
Excuse guys, after root is it possible to install a module to enable Hey Google with screen off (or in AOD mode)? Owners said that you can say Hey Google with RM8Pro only with screen on, so sad....
Click to expand...
Click to collapse
The other thing that bothers me is that if you have Google Assistant enabled, it breaks voice dictation. So you can't voice text if you want Google Assistant enabled. So sad!
May be interesting testing this phone with custom roms, like CRdroid or similar... a monster of power but with an operating system with some bugs it's a real shame....
topadstore said:
after finished all setting install magisk apk and patch
init_boot.img and boot.img
Click to expand...
Click to collapse
Thanks for the detailed guide.
But I came across this guide from Mr.PvT https://forum.xda-developers.com/t/root-red-magic-8-pro-v3-18.4556901/
He mentioned "Note: Absolutely do not patch the boot file, you will have a continuous boot error"
I am no expert in this, but will patching the boot.img by Magisk causing the situation Mr.PvT mentioned above?
thanks in advance!
i only patched the init_boot and that is all that is needed
Hi
Fingerprint not work with root? Any solution?
Then which is the command to relock the phone? Uninstalled root and.....
It's pretty easy to root the phone, but it's a more finicky to keep lock screen and finger print functionality. This root guide is more comprehensive and if you read the whole thread you will have success.
What worked for me: Working lockscreen after unlocking + rooting
Just got my set today and started tinkering, managed to get it unlocked and rooted and lockscreen is working (both fingerprint and pin) Here is a summary of what I did, maybe not all steps are needed, but this is what worked for me on the first...
forum.xda-developers.com
Took me a few tries to do it
Somebody said flash boot.img and init_boot
and Somebody said no need for boot.img
Who is more accurate?
And should I flash a and b ? Or just write that command?
fastboot flash init_boot (located file)
Dont_touch7 said:
Somebody said flash boot.img and init_boot
and Somebody said no need for boot.img
Who is more accurate?
And should I flash a and b ? Or just write that command?
fastboot flash init_boot (located file)
Click to expand...
Click to collapse
init_boot is all you need to patch with Magisk to gain root. Just flash it to the active slot. If you dont know your current slot:
fastboot getvar current-slot
DarkestSpawn said:
init_boot is all you need to patch with Magisk to gain root. Just flash it to the active slot. If you dont know your current slot:
fastboot getvar current-slot
Click to expand...
Click to collapse
Based on experience, you just have to run the command:
fastboot flash init_boot <patched_file>.img
It will automatically be flashed on the current active slot.

Categories

Resources