Develop Bugs

X2 Pro: "Your device is corrupt. It can’t be trusted and may not work properly."

X2 Pro: "Your device is corrupt. It can’t be trusted and may not work properly."
Hi everybody,
my Aquaris X2 Pro worked fine with rooted BQ 1.7.3 firmware (Android 8.1 based) - Magisk was installed and worked fine and also the xposed framework.
Today the device was normally working as it suddenly just reboots
After that the usual "unlocked bootloader" screen appears but then it only shows a screen with the message "Your device is corrupt. It can’t be trusted and may not work properly."
I can select "continue" - but that only leads back to the "unlocked bootloader" warning screen --> a boot loop :crying:
Does anybody know how I can bring back my device back to work - without losing all my settings and stuff?
And any idea what happened (so that I can prevent it to do so in future)?

Hmm, I'm not 100% sure, but I think I saw that message / boot process once as I tried to root my X2 Pro.
I had done a
Code:
fastboot flashing unlock / unlock-critical
but no
Code:
fastboot oem unlock
(or the other way round? Definitely only done one of them - I was following instructions from a thread here)
and was trying to boot a magisk patched boot-img via
Code:
fastboot boot magisk_patched.img
So, it looked like the bootloader was "NOT fully" unlocked and it detected booting a "not correctly signed" bootloader.
Perhaps check your unlock status via
Code:
fastboot getvar all
But note - UNLOCKING again will wipe your data ... and can only be done if the setting in developer options is active (I fear that THAT may have changed on your device)
You could also try booting the second slot
Code:
fastboot getvar current-slot
and then
Code:
fastboot set_active a/b
(if current-slot gives a, boot b and vica versa).
Last idea: try flashing ONLY the stock boot.img. If you can do this, this should re-enable you to boot. You will loose root, but may be able to backup (most) of your settings via Helium

Thanks a lot for your help!
Inbetween I had to go the hard way and reflashed the newest BQ factory image v2.0.2 (based on Android 9) to both parts _a and _b - losing all my data...
after that I patched the boot.img for magisk and reflashed that to my _a boot partition (and still have the original boot.img in _b).
It did cost me a bit of my spare time - but it wasn't as hard as I expected...
I was able to restore a lot of my settings with Titanium backup....
merlinwv said:
I had done a
Code:
fastboot flashing unlock / unlock-critical
but no
Code:
fastboot oem unlock
Click to expand...
Click to collapse
That was exactly what I did - the first time I only did a "flashing unlock", no "unlock-critical" - so now I had to do it to flash the complete factory image, and therefore it wiped all my data again
merlinwv said:
I was following instructions from a thread here)
Click to expand...
Click to collapse
I used the BQ batch script to flash it, but did not execute the erase commands.
But that did not help to keep my data as I needed to execute a "unlock-critical"...
merlinwv said:
So, it looked like the bootloader was "NOT fully" unlocked and it detected booting a "not correctly signed" bootloader.
Click to expand...
Click to collapse
Hmm, it worked for several months without problems - don't know why it suddenly complained about it.
merlinwv said:
Perhaps check your unlock status via
Code:
fastboot getvar all
Code:
fastboot getvar current-slot
Click to expand...
Click to collapse
Very interesting commands which I didn't know - I already wondered how I can get that information
merlinwv said:
Last idea: try flashing ONLY the stock boot.img. If you can do this, this should re-enable you to boot. You will loose root, but may be able to backup (most) of your settings via Helium
Click to expand...
Click to collapse
That would be a great idea :good: which I could've tried - but I didn't...; maybe next time - although I hope the problem will never come back

Bodenseematze said:
Thanks a lot for your help!
...
I used the BQ batch script to flash it, but did not execute the erase commands.
But that did not help to keep my data as I needed to execute a "unlock-critical"...
Click to expand...
Click to collapse
You are most welcome
The erase commands are not the ones doing the factory-reset - if you want to keep your data during a "factory-flash" you need to comment/delete the lines which flash the userdata-partition.
But I do not know if you can flash the factory image without unlocked critical (=boot) flashing. I never tried this myself. Some phones allow flashing of correctly signed boot images even when critical is locked, others prevent ALL flashing then.
Of course, for "he who knows what he is doing" there is always the possibility to flash in EDL-mode (turn off, afterwards keep vol+, Vol- and Power pressed - will bring you to a special flash mode that allows flashing even when locked - but via a special serial interface etc. pp.). Google it - this would have helped you regarding "loose of userdata when doing unlock critical". But of course - you need to edit the file because in EDL mode, normally userdata is flashed, too.
Just something to keep in mind for the next time
Hmm, it worked for several months without problems - don't know why it suddenly complained about it.
That would be a great idea :good: which I could've tried - but I didn't...; maybe next time - although I hope the problem will never come back
Click to expand...
Click to collapse
I think that perhaps an update was installed (explanation for the reboot?!) that switched to the other boot-slot and did a more thorough check of the boot-chain. This was the reason to suggest trying the other boot-slot (which would then be the pre-update version, that may still boot - and even have root)

merlinwv said:
Of course, for "he who knows what he is doing" there is always the possibility to flash in EDL-mode
Click to expand...
Click to collapse
Again: very interesting information! :good:
merlinwv said:
I think that perhaps an update was installed (explanation for the reboot?!)
Click to expand...
Click to collapse
I hope that wasn't the reason, because I explicitly switched off all automatic updates. And I did not do a manual update!
merlinwv said:
that switched to the other boot-slot and did a more thorough check of the boot-chain. This was the reason to suggest trying the other boot-slot (which would then be the pre-update version, that may still boot - and even have root)
Click to expand...
Click to collapse
I tried to switch to the other slot and boot it - but that didn't help either and led to the same problem...
What I didn't tried was to only flash the boot.img - will do this next time

[GUIDE] Relock bootloader (Should work in all versions)

Guide updated!!!!!
If you wanna get back to stock ROM and relock bootloader + get OTAs working again, this is the right place!
DISCLAIMER: Relocking bootloader erases all your data/internal storage and (off course) remove TWRP/modules/root, so do a backup of all your data first. Also, I'm not responsible for any bricked devices (phones, SD Cards, etc). I tested it in my XT1955-1 and it worked fine, but we all know that errors might occur.
Finally, let's go to the steps.
Step 1 - Downloading necessary files
Download Android Platform Tools here and then extract it.
Install Motorola Drivers on your PC (download here).
Download the lastest firmware according to your variant/software channel here and extract it in the same folder you had extracted Android Platform Tools.
Download the "Lock Script" here, according to your android version and PC's OS.
For example: if your PC uses Windows as OS, and your phone is in android 10, download the "Lock-10q_windows.bat" file.
Or if you have a Linux distro on your PC and android 9 on your phone, download "Lock-9pie_linux.sh" file.
Place the file inside the platform-tools folder, where the ROM was extracted too.
Step 2 - Preparing your phone
Remove all your google account in device's settings and then go to Developer Options. Enable Android debugging and OEM unlocking (if you can't enable OEM unlocking, you may need to root your device first to get it avaible again (see Rooting thread)).
Power off your phone and put it fastboot mode. Connect it on PC using USB cable.
Step 3 - Installing Stock ROM and re-locking bootloader
Just double click on the Lock.bat/.sh file and it will reflash stock ROM and lock bootloader. Now all you have to do is wait till it finishes. This should take a few minutes to be done.
The phone will boot automatically after the last command is executed.
It seems to be a little hard, but it's easy. If you have any questions, let me know, I'll try to answer ASAP.

Very nice, it's really working! Thanks!

Works on xt1955-4 thanks very much, will the warranty still apply?

piotr1859 said:
Works on xt1955-4 thanks very much, will the warranty still apply?
Click to expand...
Click to collapse
run
Code:
fastboot getvar all
Will tell you if warranty is voided.
Sent from my ali using XDA Labs

piotr1859 said:
Works on xt1955-4 thanks very much, will the warranty still apply?
Click to expand...
Click to collapse
Yes, should work fine. Afaik, once you unlock your bootloader, your warranty is avoid, theoretically. But I guess you can send it to service center (if it's needed) with no problems. They don't always check if you have unlocked your bootloader or not.

Warning: Due to some changes in bootloader and people getting hard bricks in February security patch, i don't recommend to relock bootloader in that version, do it in December security patch instead!

Hello guys. I have Motorola Moto G7 Power (XT1955-4). I've tried to put in twrp and a rom, but when I rebooted my device it don't power on anymore. So I've searched many guides to repair. I've used "blankflash" and after many times I was finally power on my device and go in Fastboot Mode. But now there's another problem. When I connect with usb and open CMD and type "adb devices" appear:
LIST OF DEVICES ATTACHED
or
WAITING FOR DEVICES
I tried many things to fix it but nothing work. Now I've uninstalled everything on my pc, drivers too.
Maybe I've installed bad "blankflash"???
How can I fix my troubles?

DarkAngelNoctis said:
Hello guys. I have Motorola Moto G7 Power (XT1955-4). I've tried to put in twrp and a rom, but when I rebooted my device it don't power on anymore. So I've searched many guides to repair. I've used "blankflash" and after many times I was finally power on my device and go in Fastboot Mode. But now there's another problem. When I connect with usb and open CMD and type "adb devices" appear:
LIST OF DEVICES ATTACHED
or
WAITING FOR DEVICES
I tried many things to fix it but nothing work. Now I've uninstalled everything on my pc, drivers too.
Maybe I've installed bad "blankflash"???
How can I fix my troubles?
Click to expand...
Click to collapse
If the device is in fastboot mode only fastboot commands will work
Code:
fastboot getvar all
edit:grammer
Sent from my ali using XDA Labs

sd_shadow said:
If the device is in fastboot mode only fastboot commands work like
Click to expand...
Click to collapse
Ok. Thanks!

LuisLFSS said:
Warning: Due to some changes in bootloader and people getting hard bricks in February security patch, i don't recommend to relock bootloader in that version, do it in December security patch instead!
Click to expand...
Click to collapse
hey would it be safe to use this method on security patch version April1,2020? if not please point me in the right direction.
thanks

darko454 said:
hey would it be safe to use this method on security patch version April1,2020? if not please point me in the right direction.
thanks
Click to expand...
Click to collapse
Yes, it's safe. Now we have blankflash so it's safe

LuisLFSS said:
Yes, it's safe. Now we have blankflash so it's safe
Click to expand...
Click to collapse
ok thanks!

LuisLFSS said:
Yes, it's safe. Now we have blankflash so it's safe
Click to expand...
Click to collapse
Hi, can you send a link to blankflash for XT1955-1?
THANK YOU.

hawkdown77 said:
Hi, can you send a link to blankflash for XT1955-1?
THANK YOU.
Click to expand...
Click to collapse
Yes, join in my group: t.me/motog7brasil

LuisF201707 said:
If you wanna get back to stock ROM and relock bootloader + get OTAs working again, this is the right place!
DISCLAIMER: Relocking bootloader erases all your data/internal storage and (off course) remove TWRP/modules/root, so do a backup of all your data first. Also, I'm not responsible for any bricked devices (phones, SD Cards, etc). I tested it in my XT1955-1 and it worked fine, but we all know that errors might occur.
Finally, let's go to the steps.
Step 1 - Downloading necessary files
Download Android Platform Tools here and then extract it.
Install Motorola Drivers on your PC (download here).
Download the lastest firmware according to your variant/software channel here and extract it in the same folder you had extracted Android Platform Tools.
Step 2 - Preparing your phone
Remove all your google account in device's settings and then go to Developer Options. Enable Android debugging and OEM unlocking (if you can't enable OEM unlocking, you may need to root your device first to get it avaible again (see Rooting thread)).
Power off your phone and put it fastboot mode. Connect it on PC using USB cable.
Step 3 - Installing Stock ROM
If you're already in stock ROM with no modules and stuff installed on it, just skip this and jump to the next step. If you're not, then stay here.
Open CMD (command prompt) in the same folder you had extracted firmware and android platform tools.
Shift+right click and then "Open command window here" or just type CMD in the folder path bar at the top in windows explorer. Run this commands all at once in CMD:
Once it is done, DON'T power on your phone, just leave it as it is and let's go to the last step.
Step 4 - Relocking Bootoader
In cmd, run this commands all at once
Done! The phone will boot automatically after the last command is executed.
It seems to be a little hard, but it's easy. If you have any questions, let me know, I'll try to answer ASAP.
Click to expand...
Click to collapse
There is an bat file out to relsash stock rom with out trying all that stuff in manually

Help
I followed all the steps and managed to block the bootloader but when I turn on the phone I get "start up failed" can someone help me.
I did it in the April 1 patch

JPalomo1997 said:
I followed all the steps and managed to block the bootloader but when I turn on the phone I get "start up failed" can someone help me.
I did it in the April 1 patch
Click to expand...
Click to collapse
Which android version? There's april security patch for android 9 and 10...

roadkill42 said:
There is an bat file out to relsash stock rom with out trying all that stuff in manually
Click to expand...
Click to collapse
I know... I'll update the thread soon

chrisbchrisb85 said:
For step 4 relocking the bootloader what does "run these commands all at once" mean??? As soon as I lock the bootloader I can no longer flash anything else, therefore still stuck with a boot screen warning
Click to expand...
Click to collapse
"run these commands all at once" = copy all the commands and execute them in cmd...
And which android version did you install? because the commands to flash android 10 are different than android 9 ones

Guide updated!!!!!
I removed those annoying commands and put a link to download Scripts that already do everything automatically. Now the guide is simpler and easier

Question Help I made a mistake and updated something in the development settingsAnd the recovery does not workLE 2120

On the screen I get: your device is corrupted and cannot be trusted and cannot reboot

Simply disable Developer options and the any settings you altered there will revert to baseline.
If that doesn't get it then it's not Developer options...

blackhawk said:
Simply disable Developer options and the any settings you altered there will revert to baseline.
If that doesn't get it then it's not Developer options...
Click to expand...
Click to collapse
Thanks for answering
The device may boot into a bootloader or an error on the screen

EranG90 said:
Thanks for answering
The device may boot into a bootloader or an error on the screen
Click to expand...
Click to collapse
You locked the bootloader while running modified software.
Unlock it again
Code:
fastboot oem unlock

craznazn said:
You locked the bootloader while running modified software.
Unlock it again
Code:
fastboot oem unlock
Click to expand...
Click to collapse
Thank you
I have now done that and the screens are in the same condition as in the pictures
It is good? Should I keep waiting? (I don't know really what to do, I am new at this. I don't know even if the device got the commend from the pc)

We can't really help you until you confirm what you did to get it in this state in the first place?
Did you install the OxygenOS 12 Developer Preview?
Did you try rooting by replacing the stock boot.img?
Please confirm what caused this in the first place as changing something in the developer settings alone would not cause this.

djsubterrain said:
We can't really help you until you confirm what you did to get it in this state in the first place?
Did you install the OxygenOS 12 Developer Preview?
Did you try rooting by replacing the stock boot.img?
Please confirm what caused this in the first place as changing something in the developer settings alone would not cause this.
Click to expand...
Click to collapse
Sorry like I said before I am new at this
I have change somting in the DSU option. I think this was the Acronyms
I believe I chosed GSI+"Somting"
then the device rebbot with qualcomm screen and then the error apper

EranG90 said:
Sorry like I said before I am new at this
I have change somting in the DSU option. I think this was the Acronyms
I believe I chosed GSI+"Somting"
then the device rebbot with qualcomm screen and then the error apper
Click to expand...
Click to collapse
OK, If you used DSU to try out the Android 12 Developer Preview your bootloader needs to be unlocked, try running :
fastboot oem unlock
Bear in mind it will wipe the phone though, then reboot back into the Android 11 rom, set it up and THEN try DSU.
You need to have previously allowed bootloader unlocking in your developer options (see below)

djsubterrain said:
OK, If you used DSU to try out the Android 12 Developer Preview your bootloader needs to be unlocked, try running :
fastboot oem unlock
Bear in mind it will wipe the phone though, then reboot back into the Android 11 rom, set it up and THEN try DSU.
Click to expand...
Click to collapse
Thank you
I have run this command and waited 40 min with thoose screen and stop becuse I did't saw nothing in progressing.
It is good? Should I keep waiting? (I don't know really what to do, I don't know even if the device got the command from the pc)

EranG90 said:
Thank you
I have run this command and waited 40 min with thoose screen and stop becuse I did't saw nothing in progressing.
It is good? Should I keep waiting? (I don't know really what to do, I don't know even if the device got the command from the pc)
Click to expand...
Click to collapse
Thank you so mach
I fixed my Pc usb and done the command and unlock oem
now I got only bootloader in my device
the recovery and the start options reboot the phone to the bootloader only
What I need to do now do get androird 11 back to the device?

EranG90 said:
Thank you so mach
I fixed my Pc usb and done the command and unlock oem
now I got only bootloader in my device
the recovery and the start options reboot the phone to the bootloader only
What I need to do now do get androird 11 back to the device?
Click to expand...
Click to collapse
If you're stuck on bootloader only you can try running these commands in fastboot :
fastboot -w
fastboot --set-active=a
fastboot reboot
If the phone does not boot properly then try these :
fastboot -w
fastboot --set-active=b
fastboot reboot
"fastboot -w" wipes your userdata. The "fastboot --set-active" command tells the phone which A/B slot you want to use, "fastboot reboot" is the command to restart the phone.
If you just keep getting sent back to fastboot and it won't boot then you're likely going to have to use the MSM tool to restore the phone to factory settings.

djsubterrain said:
If you're stuck on bootloader only you can try running these commands in fastboot :
fastboot -w
fastboot --set-active=a
fastboot reboot
If the phone does not boot properly then try these :
fastboot -w
fastboot --set-active=b
fastboot reboot
"fastboot -w" wipes your userdata. The "fastboot --set-active" command tells the phone which A/B slot you want to use, "fastboot reboot" is the command to restart the phone.
If you just keep getting sent back to fastboot and it won't boot then you're likely going to have to use the MSM tool to restore the phone to factory settings.
Click to expand...
Click to collapse
Really really thank you
I have tried all 4 commands (-w, --setactive=a/b and reboot)
all of them after I turn off and back on my phone show me the bootloader
can you send me a link to how I use the MSM tool to restore the phone to factory settings?

You have a LE2120 so there is no msm package publicly available yet.
In the screenshots, it shows that your fastboot drivers are not installed. Did you fix that first? The command take less than a second to run.

craznazn said:
You have a LE2120 so there is no msm package publicly available yet.
In the screenshots, it shows that your fastboot drivers are not installed. Did you fix that first? The command take less than a second to run.
Click to expand...
Click to collapse
Yes all the commands are run very fast it is no longer whiting for device
and the device state is unlock
what can I do to get android 11 on my phone? I am really new in this

EranG90 said:
Yes all the commands are run very fast it is no longer whiting for device
and the device state is unlock
what can I do to get android 11 on my phone? I am really new in this
Click to expand...
Click to collapse
try
Code:
fastboot reboot fastboot
and what shows up?

https://forum.xda-developers.com/t/...u-via-msm-no-unlock-bin-needed.4272837/unread
You can download and take the flashall.bat from this conversion guide and download your version of oneplus9pro rom to your pc then use payload dumper to extract all images, then place the flashall.bat in the same folder as all your files you dumped then plug ur phone in(while it is on bootloader screen) and double click the flashall.bat

craznazn said:
try
Code:
fastboot reboot fastboot
and what shows up?
Click to expand...
Click to collapse
thank you for answring
that what show up:
Rebooting into fastboot OKAY [ 0.004s]
< waiting for any device >
fastboot: error: Failed to boot into userspace fastboot; one or more components might be unbootable.

Shooter7889 said:
https://forum.xda-developers.com/t/...u-via-msm-no-unlock-bin-needed.4272837/unread
You can download and take the flashall.bat from this conversion guide and download your version of oneplus9pro rom to your pc then use payload dumper to extract all images, then place the flashall.bat in the same folder as all your files you dumped then plug ur phone in(while it is on bootloader screen) and double click the flashall.bat
Click to expand...
Click to collapse
Thank you
I will try anything to fix that but I am new in all this
Where I am download the flashall.bat? where I save it? How to run it?
I have download the global version for onplus9pro. What I need to do with it?

https://androidfilehost.com/?fid=14943124697586337355
This is the link to the op's zip(he created for the thread for converting tmobile variants to EU). . Click the link and download the zip, put it on your pc, then u have to extract all files. The flashall.bat is one off the files in that zip.. Then Google search the Chinese version of tue latest op9pro OS11.. Get it on your pc. U have to use payload dumper(which you will need to search android get on ur pc, extracted as well). Then once u get payload dumper ready, and ur rom, take them payload.bin from ur rom folder and put it in the payload input folder. Then double click the payload.bin and it will slowly extract all your files and put them into the payload output folder. Once it's done take the flashall.bat and put it in there. Then ur ready to plug ur phone in(in bootloader mode) and double click the flashall.bat

Shooter7889 said:
https://androidfilehost.com/?fid=14943124697586337355
This is the link to the op's zip(he created for the thread for converting tmobile variants to EU). . Click the link and download the zip, put it on your pc, then u have to extract all files. The flashall.bat is one off the files in that zip.. Then Google search the Chinese version of tue latest op9pro OS11.. Get it on your pc. U have to use payload dumper(which you will need to search android get on ur pc, extracted as well). Then once u get payload dumper ready, and ur rom, take them payload.bin from ur rom folder and put it in the payload input folder. Then double click the payload.bin and it will slowly extract all your files and put them into the payload output folder. Once it's done take the flashall.bat and put it in there. Then ur ready to plug ur phone in(in bootloader mode) and double click the flashall.bat
Click to expand...
Click to collapse
And honestly, you could prob just download the zip I mentioned, the first one just to get the flashall.bat, and just extract it, plug ur phone in(in bootloader mode) and click the flashall.bat. It would put the EU version of OS on your phone. Use cld then use the loavl update in system settings to switch to ur variant after. Much easier.

General Soft bricked when update C.62 to C.63, help needed please.

I was on C.62 AA with a working Magisk.
Yesterday I tried to update to C.63 AA with following steps:
1. Disable all Magisk module and reboot.
2. Restore Stock Image from Magisk Manager.
3. Update to C.63 from System Settings menu.
4. Install Magisk to inactive slot, then reboot.
That's it.
After reboot, my OP9P starts, but can't get into lock screen. Instead it only show black screen with a nonstop vibration.
I didn't do backup since I was NOT expecting this to happen.
Now I'm desperate for any help to unbick it or at lease get my files in sdcard back.
I can go into bootloader and fastbootd mode. ANY help would be much appreciated.

dna1982 said:
I was on C.62 AA with a working Magisk.
Yesterday I tried to update to C.63 AA with following steps:
1. Disable all Magisk module and reboot.
2. Restore Stock Image from Magisk Manager.
3. Update to C.63 from System Settings menu.
4. Install Magisk to inactive slot, then reboot.
That's it.
After reboot, my OP9P starts, but can't get into lock screen. Instead it only show black screen with a nonstop vibration.
I didn't do backup since I was NOT expecting this to happen.
Now I'm desperate for any help to unbick it or at lease get my files in sdcard back.
I can go into bootloader and fastbootd mode. ANY help would be much appreciated.
Click to expand...
Click to collapse
Unfortunately the only thing that's going to get device up and going again is msm or factory reset. You could possibly get a boot without wiping if you have untouched boot images of build you were on but then you don't know which side it booted to. I'd factory reset . Or keep device dead. You will still have patched boot.img so just reinstall magisk manager after reset.

mattie_49 said:
Unfortunately the only thing that's going to get device up and going again is msm or factory reset. You could possibly get a boot without wiping if you have untouched boot images of build you were on but then you don't know which side it booted to. I'd factory reset . Or keep device dead. You will still have patched boot.img so just reinstall magisk manager after reset.
Click to expand...
Click to collapse
I do have untouched boot images(C.63 AA) from the other thread.
I did try to "fastboot boot boot.img", result the same -- black screen with a nonstop vibration.
I think something went wrong during the update process.
Maybe flashing a stock rom in fastboot mode will help, but I don't know how and I can't find any info about howto flash OxygenOS 12 in fastboot on OP9P.

what you can try is the c63 full rom via fastbootd with the tool Fastboot Enhance to flash
[TOOL][Windows] Fastboot Enhance [Payload Dumper & Image Flasher]
Fastboot Enhance What it can do? - Show fastboot vars - Switch between fastbootd & bootloader - Switch between A & B slot - Flash Payload.bin in fastbootd - Flash images - Erase partitions - Delete logical partitions - Create logical partitions...
forum.xda-developers.com

but that will be difficult because there is no aa full rom (only india) since the update to c63 was only released globally as an incremental update

ChrisFeiveel84 said:
what you can try is the c63 full rom via fastbootd with the tool Fastboot Enhance to flash
[TOOL][Windows] Fastboot Enhance [Payload Dumper & Image Flasher]
Fastboot Enhance What it can do? - Show fastboot vars - Switch between fastbootd & bootloader - Switch between A & B slot - Flash Payload.bin in fastbootd - Flash images - Erase partitions - Delete logical partitions - Create logical partitions...
forum.xda-developers.com
Click to expand...
Click to collapse
ChrisFeiveel84 said:
but that will be difficult because there is no aa full rom (only india) since the update to c63 was only released globally as an incremental update
Click to expand...
Click to collapse
The Fastboot Enhance Tool you post does look promising.
I guess I will just wait for AA full rom to come out.
Thank you.

dna1982 said:
The Fastboot Enhance Tool you post does look promising.
I guess I will just wait for AA full rom to come out.
Thank you.
Click to expand...
Click to collapse
Last full rom for aa is
C48
I don't think that oneplus will release a full aa again

ChrisFeiveel84 said:
Last full rom for aa is
C48
I don't think that oneplus will release a full aa again
Click to expand...
Click to collapse
I will wait a week or two before flash DA C.63.

dna1982 said:
I do have untouched boot images(C.63 AA) from the other thread.
I did try to "fastboot boot boot.img", result the same -- black screen with a nonstop vibration.
I think something went wrong during the update process.
Maybe flashing a stock rom in fastboot mode will help, but I don't know how and I can't find any info about howto flash OxygenOS 12 in fastboot on OP9P.
Click to expand...
Click to collapse
It's fastboot flash boot boot.img sir.

mattie_49 said:
It's fastboot flash boot boot.img sir.
Click to expand...
Click to collapse
1. "fastboot flash" change partition permanently, while "fastboot boot" change partition temporary.
2. I also tried "fastboot flash", no luck.

dna1982 said:
I will wait a week or two before flash DA C.63.
Click to expand...
Click to collapse
The problem came up when you tried carrying root over. I've had issues as well . Make sure your on 25.2 magisk manager, disable all modules . Only uninstall magisk,restore images,start system update when finished don't reboot. Go into magisk install to inactive slot for ota. And reboot.

Just flash the full DA C.63 over it using FBE. Make sure you go to the partitions screen and search cow and delete all cow partitions before you flash or you will brick. This should at least enable you to get your files backed up so you can MSM.
Before that though, go to fastboot and try fastboot --getvar current-slot to find out what slot you're on. From there do fastboot --set-active=a or --set-active=b, whichever is not active currently. Fastboot reboot and see if your old OTA boots.

EtherealRemnant said:
Just flash the full DA C.63 over it using FBE. Make sure you go to the partitions screen and search cow and delete all cow partitions before you flash or you will brick. This should at least enable you to get your files backed up so you can MSM.
Before that though, go to fastboot and try fastboot --getvar current-slot to find out what slot you're on. From there do fastboot --set-active=a or --set-active=b, whichever is not active currently. Fastboot reboot and see if your old OTA boots.
Click to expand...
Click to collapse
he can also see which slot is active directly with fbe because fbe shows this itself, just like he can change the slot with fbe

dna1982 said:
1. "fastboot flash" change partition permanently, while "fastboot boot" change partition temporary.
2. I also tried "fastboot flash", no luck.
Click to expand...
Click to collapse
fastboot flash only flashes the active slot and does not switch to the inactive slot.. and fastboot boot only boots an image that you have specified

ChrisFeiveel84 said:
he can also see which slot is active directly with fbe because fbe shows this itself, just like he can change the slot with fbe
Click to expand...
Click to collapse
FBE's slot changer doesn't always work in my experience. Both times I tried it for the purposes of changing the slot to boot from, it didn't actually change the slot, but when I switched slots to choose which to install to, that worked correctly. I only tell people to use things I'm confident work correctly and I know fastboot slot switching is one of those things that does.

EtherealRemnant said:
FBE's slot changer doesn't always work in my experience. Both times I tried it for the purposes of changing the slot to boot from, it didn't actually change the slot, but when I switched slots to choose which to install to, that worked correctly. I only tell people to use things I'm confident work correctly and I know fastboot slot switching is one of those things that does.
Click to expand...
Click to collapse
I also noticed that if you change the slot with fbe, the active slot is still displayed in fbe, but if you then reconnect the cell phone to the pc, fbe then shows that it has changed the slot

dna1982 said:
I was on C.62 AA with a working Magisk.
Yesterday I tried to update to C.63 AA with following steps:
1. Disable all Magisk module and reboot.
2. Restore Stock Image from Magisk Manager.
3. Update to C.63 from System Settings menu.
4. Install Magisk to inactive slot, then reboot.
That's it.
After reboot, my OP9P starts, but can't get into lock screen. Instead it only show black screen with a nonstop vibration.
I didn't do backup since I was NOT expecting this to happen.
Now I'm desperate for any help to unbick it or at lease get my files in sdcard back.
I can go into bootloader and fastbootd mode. ANY help would be much appreciated.
Click to expand...
Click to collapse
Is there any update regarding this thread? The same thing happens to me after I update my phone from C.62 DA to C.63 DA my phone is stuck on a black screen and then keeps on vibrating. I am also desperate to at least recover my data.

JeanFlasher said:
Is there any update regarding this thread? The same thing happens to me after I update my phone from C.62 DA to C.63 DA my phone is stuck on a black screen and then keeps on vibrating. I am also desperate to at least recover my data.
Click to expand...
Click to collapse
Sorry to hear that.
But you don't have to wait, since there is DA C.63 full rom.
Just flash it in fastboot mode by using Fastboot Enhance tool.
Good luck and tell us how it goes.

dna1982 said:
Sorry to hear that.
But you don't have to wait, since there is DA C.63 full rom.
Just flash it in fastboot mode by using Fastboot Enhance tool.
Good luck and tell us how it goes.
Click to expand...
Click to collapse
It didn't work for me real bummer. I've tried to do what EtherealRemnant suggested (ie: full flash DA C.63 over it using FBE), still out of luck.

JeanFlasher said:
It didn't work for me real bummer. I've tried to do what ChrisFeiveel84 suggested, still out of luck.
Click to expand...
Click to collapse
Did you follow the steps that @EtherealRemnant post?
And what is the result? We need details to help you.

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.