Fixed! Go here for steps
I've tried the relock.bat provided in the unofficial bootloader unlock/lock thread but I keep getting the bootloader unlocked warning. I also downloaded and tried installing the stock ROM mentioned in https://m.youtube.com/watch?v=peSI-KeEt5E&time_continue=23 but the window just closed itself so I manually flashed recovery, boot, system and vendor images using twrp. I then booted and installed the April security patch update but I got random soft-reboots in the process.
Can anyone guide me to restoring the device to locked condition? (4GB ram variant)
Update: Noticed that these reboots occur as soon as app installation is over. Disabled app updates for now
Relock Bootloader ZenFone Max Pro M1
1) Download Zenfone_Max_M1_Pro_Relock.zip and extract it to a folder on your desktop.
2) Power off your phone. Then press Power and Volume Down key together, to boot into fastboot mode.
3) Connect your Asus Zenfone Max Pro M1 to the PC using a USB cable.
4) Windows will now automatically detect the device and start installing the fastboot drivers for it. If not, download and install these ASUS drivers.
5) Open the directory where you extracted the file from #1.
6) In that directory, open a file named relock_bl.cmd
7) A Command (CMD) prompt will do the rest of the work for you.
Let the phone restart.
8) It will then erase all the data on your phone (excluding Micro SD card).
9) Now the phone won’t show the “bootloader unlocked” warning that was displayed before you relocked the bootloader.
You have successfully relocked the bootloader.
myapky said:
9) Now the phone won’t show the “bootloader unlocked” warning that was displayed before you relocked the bootloader.
Click to expand...
Click to collapse
No success. I'm following the method shown in this thread
Edit: Reboots are fixed after I wiped data before flashing the images
myapky said:
1) Download Zenfone_Max_M1_Pro_Relock.zip and extract it to a folder on your desktop.
2) Power off your phone. Then press Power and Volume Down key together, to boot into fastboot mode.
3) Connect your Asus Zenfone Max Pro M1 to the PC using a USB cable.
4) Windows will now automatically detect the device and start installing the fastboot drivers for it. If not, download and install these ASUS drivers.
5) Open the directory where you extracted the file from #1.
6) In that directory, open a file named relock_bl.cmd
7) A Command (CMD) prompt will do the rest of the work for you.
Let the phone restart.
8) It will then erase all the data on your phone (excluding Micro SD card).
9) Now the phone won’t show the “bootloader unlocked” warning that was displayed before you relocked the bootloader.
You have successfully relocked the bootloader.
Click to expand...
Click to collapse
IF YOU ARE ON THE LATEST FIRMWARE THEN THE ABOVE STEPS WORK, I CANNOT POST LINKS HERE AS I'M NOT ABLE TO.
MY PHONE FIRMWARE : Version WW-14.2016.1804.305
CONFIRM YOURS............!!!!
myapky said:
WW-14.2016.1804.305
Click to expand...
Click to collapse
OPM1.WW_Phone-14.2016.1804.305-20180521
Check this [GUIDE][Back-To-Stock] Flash Stock ROM
CHECK THIS : https://forum.xda-developers.com/showpost.php?p=76695194&postcount=95
Download stock recovery availbale at xda forum.
Than download the official latest firmware 1.4GB from asus website and place in external sdcard.
Flash stock recovery with fastboot method. Boot into recovery and flash the firmware zip..it will automatically encrypt your internal data.
SINGHYAR.
myapky said:
CHECK THIS : https://forum.xda-developers.com/showpost.php?p=76695194&postcount=95
Click to expand...
Click to collapse
This got my device into Red State with message "Your data is corrupt". Unlocked bootloader again, will try this method by installing system, boot, recovery and vendor partition images
That script is working for me, but I installed the images of the csc zip which was indonesian edition. Trying again with ZB601KL images
Thanks @myapky! Phone is now having a locked bootloader
Can I relock bootloader after installing Magisk?
Sourav-21 said:
Can I relock bootloader after installing Magisk?
Click to expand...
Click to collapse
You should lock bootloader only on stock recovery without root and with no system modification (like uninstall of system apps, property file change).
If you lock the bootloader with custom recovery or modified system then if OTA messes up boot or any other partition .. you have no way to fix it.
Also .. only locking the bootloader will not fix OTA .. as any OTA patching boot.img will mess your Magisk anyway .. so keep bootloader unlocked if you have modifications.
.A.V.i.n.a.S.h. said:
You should lock bootloader only on stock recovery without root and with no system modification (like uninstall of system apps, property file change).
If you lock the bootloader with custom recovery or modified system then if OTA messes up boot or any other partition .. you have no way to fix it.
Also .. only locking the bootloader will not fix OTA .. as any OTA patching boot.img will mess your Magisk anyway .. so keep bootloader unlocked if you have modifications.
Click to expand...
Click to collapse
Thank you. I forgot that Magisk patch the system.img. In old days superSU just modify the system partition.
I want to relock the bootloader only for the irritating Warning message at the startup. Is there any way to stop that message like moto G?
Sourav-21 said:
Thank you. I forgot that Magisk patch the system.img. In old days superSU just modify the system partition.
I want to relock the bootloader only for the irritating Warning message at the startup. Is there any way to stop that message like moto G?
Click to expand...
Click to collapse
It appears on custom ROM as well .. so not sure about any way to block it.
If i unlock via official app and when some update available and I download & flash by stock recovery will it work?
Another question is if I install custom rom then how can I back in stock rom?
Ariful Hasan Soikot said:
If i unlock via official app and when some update available and I download & flash by stock recovery will it work?
Another question is if I install custom rom then how can I back in stock rom?
Click to expand...
Click to collapse
Recommended to UNLOCK unofficially - using this Guide.
If you have unlocked officially then you will not get OTA update notification.
To update (if you are on stock system without modifications like TWRP, Root etc..),
Download full firmware from ASUS official site ( ZBL601KL OR ZBL602KL ) and try to unzip it once to check for file errors.
If no issues in unzip then keep the file in base path of Internal storage.
You will get a message like System Update file detected (if not then reboot and check).
Select the notification and authorize to update. DONE.
To revert back to Stock from Custom roms - use this GUIDE or follow the method in this thread
.A.V.i.n.a.S.h. said:
Recommended to UNLOCK unofficially - using this Guide.
If you have unlocked officially then you will not get OTA update notification.
To update (if you are on stock system without modifications like TWRP, Root etc..),
Download full firmware from ASUS official site ( ZBL601KL OR ZBL602KL ) and try to unzip it once to check for file errors.
If no issues in unzip then keep the file in base path of Internal storage.
You will get a message like System Update file detected (if not then reboot and check).
Select the notification and authorize to update. DONE.
To revert back to Stock from Custom roms - use this GUIDE or follow the method in this thread
Click to expand...
Click to collapse
I don't understand about base path of internal storage. Plz can you show a screenshot or make clear about which folder i have to put full firmware?
Ariful Hasan Soikot said:
I don't understand about base path of internal storage. Plz can you show a screenshot or make clear about which folder i have to put full firmware?
Click to expand...
Click to collapse
Just keep the file in Internal storage and not under any folder/directory in Internal Storage.
In Internal Storage you should have ..
Android (directory)
DCIM (directory)
Download (directory)
WhatsApp (directory)
..... etc
UL-ASUS_X00T-WW-14.2016.1804.252-user.zip (file)
Remember that the current UL-ASUS_X00T-WW-14.2016.1804.305-user.zip file on https://www.asus.com/in/Phone/ZenFone-Max-Pro-ZB601KL/HelpDesk_BIOS/ is corrupted.
You can download UL-ASUS_X00T-WW-14.2016.1804.252-user.zip from here - https://androidfilehost.com/?fid=674106145207491520
Related
DESCRIPTION:
Today i found the New Root & Installing Custom Recovery(TWRP) in MARSHMALLOW ROM surely...
I will Provide correct info and help......All This you are gonna do is At your Own Risk... Damage to your device of any type is at your Own Responsibility,,, Don't point finger at me or I will Just Laugh at you...
PREREQUISTES:
First of all, You should Unlock Bootloader so that on every reboot, Your Root shouldn't damage. You can unlock bootloader by simple procedure...and also enable the USB Debugging from Developers options in settings...
PROCEDURE:
FOR UNLOCKING BOOTLOADER, FOLLOW THIS
Download the Attached PC Software Named "Huawei Product ID Generator" then Extract this zip file...
Now open it, fill all Info in it and it will Generate a Product ID for your Phone....
Now go to this site Unlocking Code website
Login to this site using your Huawei id which you made in themes store or in huawei cloud!!
Use the Serial Number Written on BACK OF YOUR PHONE..!!
Fill like, smartphone>Product Model should be "HUAWEI Y300-0000"
then fill all fields and captcha also.. Click Submit and get the UNLOCKING CODE....
you can unlock bootloader wid that code then and root permanently....
After receiving the unlock code, write down the code;
Now go in your 4C's Settings>About Phone.
Then tap on Build number 10 times,,, you will get the Developers options in Last of Settings app. Open Developers option and Turn On the USB DEBUGGING.
Now connect your device to PC in MTP/FILES mode and then install the ADB drivers for it....
To install adb drivers correctly, use the Software Adb Driver Installer from here
LINK FOR ADB DRIVER INSTALLER
Full ADB folder is also attached Below.... put this folder in drive C.
Now Direct the cursor on the folder ADB, hold Shift and the right mouse button and choose "Open Command Window";
connect your phone to the PC in the "media device";
at the command prompt prescribe ADB Devices ;
then we write ADB reboot bootloader (the device will reboot mode fastboot);
then typed fastboot oem unlock **************** (where the asterisks replace unlock code);
BOOTLOADER UNLOCKED NOW!!
Now You are Ready to install TWRP recovery in Marshmallow first.... Download the Root and TWRP recovery File from here...
This File Also contain Stock Recovery of Marshmallow Rom
4C Root+TWRP by [email protected]
After this, unzip it and better come again in Fastboot Mode like above as explained, this time, move the recovery file to the adb folder which you want to install.
After that, type fastboot devices to see if your device is correctly attached to PC or Laptop. if yes then type this command in cmd to install the Custom Recovery(TWRP) in your phone.
fastboot flash recovery twrp.img
Then
fastboot reboot
This will reboot your phone and TWRP installed.
Gonna Done Root now... READ CAREFULLY... ROOTING MARSHMALLOW IS NOT EASY...
Download This Zip File and then Go in TWRP recovery and swipe for allow modifications...... and then flash that zip file named 1.zip...
After its done,, restart your phone and if it promp to install su, ignore it....
Open supersu app installed in your phone and let it update its binaries...when done, reboot to recovery again and this time flash This File.
Then reboot your phone and then supersu will be stable,,,
Now you have Successfully Rooted Marshmallow
Hit Thanks and Support me if you Like and get help from this thread...Thank you...
This is Based on Stock Huawei Kernel, Not compiled by Me...
Contributors:
@HassanMirza01
Mohamed A. Abd Ellatif
Version Information:
Status: Stable
Stable Release Date: 2015-09-28
Created on: 2016-02-19
Last Updated on: 2016-04-09
Reserved
Is this is TWRP for Marshmallow? Because the recovery files.you have uploaded are dated 25th September 2015?
@mfbcool yes...this is for Marshmallow... But dont swipe allow modifications!!
Member gettin error after swiping...just do read only...
I root my device by this method yesterday
but today root not work in titanum backup
I check it by root checker and everything is ok
Even though this method works, I would not recommend moving SuperSU to system partition. I didn't moved it and still SU permissions are working fine. I say so because Chainfire in his new SuperSU adopted a 'Systemless Root' method that roots without modifying the system partition so that apps like Android Pay work properly. He achieved this by patching the Boot image and so root is installed in boot image and is enabled at every boot (that's why you may experience some boot loops after rooting). This makes taking OTA updates and unrooting the device easier as you can unroot by flashing the Stock Boot.img instead of flashing the whole system partition.
I believe moving SuperSU to system partition destroys the main purpose and idea Chainfire had while making SuperSU compatible with Marshmallow. We all know EMUI won't update on Rooted devices. So it would be a pain to reflash whole Stock System Partition before taking OTA.
Hi thanks, I'm root my mobile I'm in android 6.0 now how to get back to kikkat a stock rom from twrp
@G E N E R A L open supersu app and tick the mount name separation and restart phone... Titanium, kingroot all will recognize root
Hit thanks if it helps....
@TMDMOOSA if you wanna go back to KK, Flash stock recovery first!!
Then flash the back pkg B320, then B070
If you gets error, flash middle pkg of chc rom and then flash directly KK Rom usin stock recovery!!
hi
i have a problem
by flashing file 1.zip phone reboot twice and screen go black and nothing happens after
by flashing the ROM problem fix but i cant root my phone
i try this three times!!
what can i do?
thnx
@inshaalmirza
hello, I by mistake flash the root.zip of lollipop to my phone running marshmallow. Now my phone is stuck on bootscreen. what should I do now. adb is not working
onlyankush_s said:
@inshaalmirza
hello, I by mistake flash the root.zip of lollipop to my phone running marshmallow. Now my phone is stuck on bootscreen. what should I do now. adb is not working
Click to expand...
Click to collapse
this happened for me by flashing right zip file!!!
no solution??
i wipe all the data (even system data) by custom recovery and turn off the phone and hold power volume down and up together
by doing this if you have ROM file in your sd , new ROM will be instal on your device
just please tell me how i can root my phone??
@inshaalmirza @ mfbcool please reply what to do
onlyankush_s said:
@inshaalmirza
hello, I by mistake flash the root.zip of lollipop to my phone running marshmallow. Now my phone is stuck on bootscreen. what should I do now. adb is not working
Click to expand...
Click to collapse
onlyankush_s said:
@ mfbcool please reply what to do
Click to expand...
Click to collapse
Flash the complete Marshmallow ROM through Stock Recovery.
matinone said:
hi
i have a problem
by flashing file 1.zip phone reboot twice and screen go black and nothing happens after
by flashing the ROM problem fix but i cant root my phone
i try this three times!!
what can i do?
thnx
Click to expand...
Click to collapse
no one??
please
@onlyankush_s go in fastboot and then flash the system.img again.... Or flash stock M wid stock recovery...
@matinone there is written that flash supersu again after flashing 1.zip
Flash supersu zip too and tell... Or flash srock rom again by same method i told in most previous posr.... I am sick right now thats why replying late!!
inshaalmirza said:
@matinone there is written that flash supersu again after flashing 1.zip
Flash supersu zip too and tell... Or flash srock rom again by same method i told in most previous posr.... I am sick right now thats why replying late!!
Click to expand...
Click to collapse
thanks a lot!!!
it worked
by the same steps.it look like i got lucky this time
hope you get better soon
hi
plz help
i flash stock recovery and my phone go to rescue mode
help
I have successfully built TWRP 3.0.0-0 for our device which fixes the weird swipe to allow modifications bug and is fully compatible with Android 6.0 Marshmallow.
See here: http://forum.xda-developers.com/android/development/recovery-twrp-3-0-0-0-huawei-honor-4c-t3349495
Also, to re-flash Stock ROM, you don't need to flash Stock Recovery. Huawei phones have 2 inbuilt recoveries. The second recovery (which is the Stock) can be accessed by 3 buttons method (Power + Volume Up + Volume Down).
@mfbcool i saw that thread early... Great work man... I know huawei have 2 inbuilt recoveries but 2nd one is erecovery and thats of no use at all... I tried it too many times!! If twrp 3.0 can flash update.app files,,, it gonna rocks , wish u best of luck man!! You did it
Hello All, this guide will help to unbrick or back to stock firmware on Indian Variants BND-L22 and BND-AL10C675
Dont try it on other variant otherwise you will fail to install and may loose your IMEI number.
Do it on your own risk. I will not be responsible for any damage to your phone.
I am not a developer so i cant help you much if this update process fails.
PreRequisites :
1. Bootloader Locked/ReLocked/UnLocked
2. Stock Recovery/TWRP. it works with TWRP, still i suggest you use stock one. Download stock recovery for BND from here
https://mega.nz/#!KixHHCKJ!4hw_lHQGYa_0BJ79lou4m34Fmi23wBctbbvdSCyvCYE
3. SD card (at least 5gb free memory)
Preparations :
1. Backup your data
2. if you are on twrp, just flash Stock recovery via Fastboot or MT
command ' fastboot flash recovery recovery.img '
3. Lock/relock your bootloader ( you may test it on unloacked bootloader)
command ' fastboot oem relock (unlock code) '
4. download this tar. gz file, extract it and Copy 'dload' folder on your SD card, put SD card in your phone
https://mega.nz/#!SuwDUTCJ!iaBnYIbLlMggGId_COuu-xY9pZ2Tec66si5PEcEhovM
This is full Stock Rom not just an OTA update.
5. charge your phone to at least 50%
Steps :
1. switch off your phone and wait for 10 secs
2. press vol.up + vol.down + power keys simultaneously
3. keep keys pressing for few seconds and your phone will boot into automatic update package installer.
4. wait till updating/installing done. If process is stucked at 99%, dont worry just wait for few mins.
5. after updating package done, your phone will boot into stock system. congratulations
Dr.Anshuman said:
Hello All, this guide will help to unbrick or back to stock firmware on Indian Variants BND-L22 and BND-AL10C675
Dont try it on other variant otherwise you will fail to install and may loose your IMEI number.
Do it on your own risk. I will not be responsible for any damage to your phone.
I am not a developer so i cant help you much if this update process fails.
PreRequisites :
1. Bootloader Locked/ReLocked (I've not tried on UnLocked bootloaders)
2. Stock Recovery (I've not tried on TWRP). Download stock recovery for BND from here
https://mega.nz/#!nyY1QRpR!gp5k4nqkQUfktrD2B5Qb1OhhAXmO5Mi2aaMPz8CD8Ts
3. SD card (at least 5gb free memory)
Preparations :
1. Backup your data
2. if you are on twrp, just flash Stock recovery via Fastboot or MT
command ' fastboot flash recovery recovery.img '
3. Lock/relock your bootloader ( you may test it on unloacked bootloader)
command ' fastboot oem relock (unlock code) '
4. download this tar. gz file, extract it and Copy 'dload' folder on your SD card, put SD card in your phone
https://mega.nz/#!SuwDUTCJ!iaBnYIbLlMggGId_COuu-xY9pZ2Tec66si5PEcEhovM
This is full Stock Rom not just an OTA update.
5. charge your phone to at least 50%
Steps :
1. switch off your phone and wait for 10 secs
2. press vol.up + vol.down + power keys simultaneously
3. keep keys pressing for few seconds and your phone will boot into automatic update package installer.
4. wait till updating/installing done. If process is stucked at 99%, dont worry just wait for few mins.
5. after updating package done, your phone will boot into stock system. congratulations
Click to expand...
Click to collapse
How come you got the stock image of bnd al-10?
Asder.mko said:
How come you got the stock image of bnd al-10?
Click to expand...
Click to collapse
Its Unofficial.
Dr.Anshuman said:
Its Unofficial.
Click to expand...
Click to collapse
That doesn't matter if it works. I'm having unlocked bootloader.
Let me check and confirm whether it works or not on unlocked device.
Dr.Anshuman said:
Hello All, this guide will help to unbrick or back to stock firmware on Indian Variants BND-L22 and BND-AL10C675
Dont try it on other variant otherwise you will fail to install and may loose your IMEI number.
Do it on your own risk. I will not be responsible for any damage to your phone.
I am not a developer so i cant help you much if this update process fails.
PreRequisites :
1. Bootloader Locked/ReLocked (I've not tried on UnLocked bootloaders)
2. Stock Recovery (I've not tried on TWRP). Download stock recovery for BND from here
https://mega.nz/#!nyY1QRpR!gp5k4nqkQUfktrD2B5Qb1OhhAXmO5Mi2aaMPz8CD8Ts
3. SD card (at least 5gb free memory)
Preparations :
1. Backup your data
2. if you are on twrp, just flash Stock recovery via Fastboot or MT
command ' fastboot flash recovery recovery.img '
3. Lock/relock your bootloader ( you may test it on unloacked bootloader)
command ' fastboot oem relock (unlock code) '
4. download this tar. gz file, extract it and Copy 'dload' folder on your SD card, put SD card in your phone
https://mega.nz/#!SuwDUTCJ!iaBnYIbLlMggGId_COuu-xY9pZ2Tec66si5PEcEhovM
This is full Stock Rom not just an OTA update.
5. charge your phone to at least 50%
Steps :
1. switch off your phone and wait for 10 secs
2. press vol.up + vol.down + power keys simultaneously
3. keep keys pressing for few seconds and your phone will boot into automatic update package installer.
4. wait till updating/installing done. If process is stucked at 99%, dont worry just wait for few mins.
5. after updating package done, your phone will boot into stock system. congratulations
Click to expand...
Click to collapse
If you have a twrp already why bother to install drivers and go for ADB you can just flash the recovery.img from twrp .It works too .just a suggestion
trixter127 said:
If you have a twrp already why bother to install drivers and go for ADB you can just flash the recovery.img from twrp .It works too .just a suggestion
Click to expand...
Click to collapse
hiiiiiiii dear....pls tell me .....this is official indian Rom for honor 7x ..........and does it contains preinstalled gapps.......
trixter127 said:
If you have a twrp already why bother to install drivers and go for ADB you can just flash the recovery.img from twrp .It works too .just a suggestion
Click to expand...
Click to collapse
yes, but when it comes to complete stock, i prefer fastboot commands.
gouravbharat2014 said:
hiiiiiiii dear....pls tell me .....this is official indian Rom for honor 7x ..........and does it contains preinstalled gapps.......
Click to expand...
Click to collapse
this is a complete Firmware including gApps.
Dr.Anshuman said:
yes, but when it comes to complete stock, i prefer fastboot commands.
Click to expand...
Click to collapse
Well, thanks for the post
Dr.Anshuman said:
this is a complete Firmware including gApps.
Click to expand...
Click to collapse
thanks a ton.........
Hi !
It work on BND-L21C432 ?
Thanks !
Thanks
Awesome it worked
saifuddin.slatewala said:
Awesome it worked
Click to expand...
Click to collapse
Model? Ota working?
DaRkLinK_35 said:
Hi !
It work on BND-L21C432 ?
Thanks !
Click to expand...
Click to collapse
This is only for L22 and AL10C675, dont try it on other versions.
Dr.Anshuman said:
This is only for L22 and AL10C675, dont try it on other versions.
Click to expand...
Click to collapse
Ok thanks for you reply !
Username.php said:
Model? Ota working?
Click to expand...
Click to collapse
honor 7x model: BND-AL10
can we use this method to roll back the faceunlock update as its having annoying touch problems? (Indian Version)
Yes it will rollback to earlier version one without face lock
saifuddin.slatewala said:
Yes it will rollback to earlier version one without face lock
Click to expand...
Click to collapse
thanks, do i need to factory reset or just flash this file on top of faceunlock from recovery?
also after this flashing, can we still get OTA updates as normal?
Thank you so much mate. I am back on stock ROM and I did get Oreo ota today just because of you.
Hi guys,
I am using Zenfone Max Pro M2. I wanted to install a custom rom and I tried to unlock bootloader but I unlocked it through official unlocktool. Now I can't flash anything or send any command through fastboot, whenever I do then it restarts the device.
When I try to keep the fastboot command running and then connect phone - it throws errors like "Fail - Too many links", "Fail - Write to device fail (No such file or directory)" or "Fail- Unknown command".
I tried unlocking bootloader with the unofficial way provided in https://forum.xda-developers.com/max-pro-m2/how-to/unlook-bootloader-root-asus-zenfone-max-t3885457
but it isn't working either, any fastboot command is rebooting the device although bootloader is unlocked.
How do I fix this?
EDIT: Things I have tried:
- Changing USB Cable and Port
- Reinstalling ADB and device driver
- Reunlocking bootloader from UnlockTool (don't know why I did that again)
- Unofficial way to unlock bootloader
None of it helped.
Thanks
Mr147 said:
Hi guys,
I am using Zenfone Max Pro M2. I wanted to install a custom rom and I tried to unlock bootloader but I unlocked it through official unlocktool. Now I can't flash anything or send any command through fastboot, whenever I do then it restarts the device.
When I try to keep the fastboot command running and then connect phone - it throws errors like "Fail - Too many links", "Fail - Write to device fail (No such file or directory)" or "Fail- Unknown command".
I tried unlocking bootloader with the unofficial way provided in https://forum.xda-developers.com/max-pro-m2/how-to/unlook-bootloader-root-asus-zenfone-max-t3885457
but it isn't working either, any fastboot command is rebooting the device although bootloader is unlocked.
How do I fix this?
EDIT: Things I have tried:
- Changing USB Cable and Port
- Reinstalling ADB and device driver
- Reunlocking bootloader from UnlockTool (don't know why I did that again)
- Unofficial way to unlock bootloader
None of it helped.
Thanks
Click to expand...
Click to collapse
Guys, no one to help or assist?
Mr147 said:
Guys, no one to help or assist?
Click to expand...
Click to collapse
Did u try running the command at the adb folder?shift+right click in adb folder?
Is Usb debugging enabled in developer options?
X10MINISTER said:
Did u try running the command at the adb folder?shift+right click in adb folder?
Is Usb debugging enabled in developer options?
Click to expand...
Click to collapse
Yes, everything done.
Still no success.
Mr147 said:
Yes, everything done.
Still no success.
Click to expand...
Click to collapse
Did ur unlocking bootloader succeed?
Did you try relocking the bootloader ?
1) Try relocking the bootloader using the methods described here :
https://forum.xda-developers.com/max-pro-m2/how-to/unroot-relock-bootloader-max-pro-m2-t3885870
See if it successfully relocks...
If it does, then next time unlock using the unofficial method only...
2) If not then maybe try contacting ASUS... Tweet them on Twitter... Companies usually respond very fast on Twitter, since their reputations are at stake...
3) All else fails then try rooting it using something like Kingroot... Once rooted, flash TWRP Recovery using Flashify... then flash any custom ROM u want...
I hope your problem gets solved... Next time be a little more cautious when taking such a risky step... See what are all the options you have before jumping into something...
X10MINISTER said:
Did ur unlocking bootloader succeed?
Click to expand...
Click to collapse
I guess it did because when I reboot it I get that bootloader unlocked splash screen.
Tyakrish said:
Did you try relocking the bootloader ?
1) Try relocking the bootloader using the methods described here :
https://forum.xda-developers.com/max-pro-m2/how-to/unroot-relock-bootloader-max-pro-m2-t3885870
See if it successfully relocks...
If it does, then next time unlock using the unofficial method only...
2) If not then maybe try contacting ASUS... Tweet them on Twitter... Companies usually respond very fast on Twitter, since their reputations are at stake...
3) All else fails then try rooting it using something like Kingroot... Once rooted, flash TWRP Recovery using Flashify... then flash any custom ROM u want...
I hope your problem gets solved... Next time be a little more cautious when taking such a risky step... See what are all the options you have before jumping into something...
Click to expand...
Click to collapse
Tried everything except 2, none worked. I'll drop them a query over twitter like you say, let's see what their reply is.
I am on stock recovery, non working bootloader but unlocked, and stock rom unrooted.
I think Pie update may give some insight on fixing this.
Mr147 said:
I guess it did because when I reboot it I get that bootloader unlocked splash screen.
Click to expand...
Click to collapse
I see.. did u've try using another laptop/pc? Sometimes antivirus blocking the tools that are needed for unlocking bootloader..
X10MINISTER said:
I see.. did u've try using another laptop/pc? Sometimes antivirus blocking the tools that are needed for unlocking bootloader..
Click to expand...
Click to collapse
I unlocked using official bootloader apk provided by asus. Now I have encrypted phone which isn't decrypting and can't flash twrp.
Mr147 said:
I unlocked using official bootloader apk provided by asus. Now I have encrypted phone which isn't decrypting and can't flash twrp.
Click to expand...
Click to collapse
Hey you said phone is encrypted ? Maybe this might work :
1) Download and install the latest Magisk Manager apk
2) Extract boot.img from stock firmware
3) Put boot.img in your internal storage and open magisk app.
4) Click on install and select patch boot Image.
5) Select stock boot.img file placed in phone memory.
6) Magisk will automatically patch the stock Image and this patched image can be installed using fastboot using this command:
fastboot flash boot patched_boot.img
This will root your phone. After that you can install Flashify to flash TWRP or PBRP
Note:
- This method is highly experimental... There are 50% chances of bootloop. I would not have recommended this method, but situation seems to demand it.
- Your data will most probably be formatted, so keep a backup.
- If it falls in a bootloop, then you need to flash original stock firmware to restore your phone.
Credits: @#ArtFuL
Who came up with this method, but removed it from the main guide, because of being experimental... (I guess)
Mr147 said:
I unlocked using official bootloader apk provided by asus. Now I have encrypted phone which isn't decrypting and can't flash twrp.
Click to expand...
Click to collapse
After going through the errors, I strongly believe that the problem is with your drivers. If reinstalling doesn't works, try a different pc. If your pc detects your device on MTP or your are able to perform adb operations without any hassle, it's not the problem with your phone.
You can decrypt the device only after flashing custom recovery.
---------- Post added at 09:35 PM ---------- Previous post was at 09:31 PM ----------
Tyakrish said:
Hey you said phone is encrypted ? Maybe this might work :
1) Download and install the latest Magisk Manager apk
2) Extract boot.img from stock firmware
3) Put boot.img in your internal storage and open magisk app.
4) Click on install and select patch boot Image.
5) Select stock boot.img file placed in phone memory.
6) Magisk will automatically patch the stock Image and this patched image can be installed using fastboot using this command:
fastboot flash boot patched_boot.img
This will root your phone. After that you can install Flashify to flash TWRP or PBRP
Note:
- This method is highly experimental... There are 50% chances of bootloop. I would not have recommended this method, but situation seems to demand it.
- Your data will most probably be formatted, so keep a backup.
- If it falls in a bootloop, then you need to flash original stock firmware to restore your phone.
Credits: @#ArtFuL
Who came up with this method, but removed it from the main guide, because of being experimental... (I guess)
Click to expand...
Click to collapse
Yes this method is highly experimental. Also in this situation, he cannot use any fastboot commands. So this method won't work
#ArtFuL said:
After going through the errors, I strongly believe that the problem is with your drivers. If reinstalling doesn't works, try a different pc. If your pc detects your device on MTP or your are able to perform adb operations without any hassle, it's not the problem with your phone.
You can decrypt the device only after flashing custom recovery.
---------- Post added at 09:35 PM ---------- Previous post was at 09:31 PM ----------
Yes this method is highly experimental. Also in this situation, he cannot use any fastboot commands. So this method won't work
Click to expand...
Click to collapse
This method didn't work, as fastboot isn't accepting any command. I tried giving command before connecting phone and then connecting, it gives me error of "File size is more than max allowed".
So is it done?
Mr147 said:
This method didn't work, as fastboot isn't accepting any command. I tried giving command before connecting phone and then connecting, it gives me error of "File size is more than max allowed".
Click to expand...
Click to collapse
See I recommend please use Linux (Manjaro or Ubuntu) , Windows will have driver issues forever and ever
had same issue after fota update UL-ASUS_X01BD-WW-15.2016
Tyakrish said:
Hey you said phone is encrypted ? Maybe this might work :
1) Download and install the latest Magisk Manager apk
2) Extract boot.img from stock firmware
3) Put boot.img in your internal storage and open magisk app.
4) Click on install and select patch boot Image.
5) Select stock boot.img file placed in phone memory.
6) Magisk will automatically patch the stock Image and this patched image can be installed using fastboot using this command:
fastboot flash boot patched_boot.img
This will root your phone. After that you can install Flashify to flash TWRP or PBRP
Thanks , this method work me. had same issue after fota update UL-ASUS_X01BD-WW-15.2016.1902.192-user
Click to expand...
Click to collapse
I've the same problem too. Let me know if you've configure it out. Thanks.
Okay @Mr147, I've fix this. I checked Windows Update and there was a pending ASUS driver update. I downloaded it and now I can use the fastboot commands.
Anyone that can fix this problem? I also experience this.
Mr147 said:
Hi guys,
I am using Zenfone Max Pro M2. I wanted to install a custom rom and I tried to unlock bootloader but I unlocked it through official unlocktool. Now I can't flash anything or send any command through fastboot, whenever I do then it restarts the device.
When I try to keep the fastboot command running and then connect phone - it throws errors like "Fail - Too many links", "Fail - Write to device fail (No such file or directory)" or "Fail- Unknown command".
I tried unlocking bootloader with the unofficial way provided in https://forum.xda-developers.com/max-pro-m2/how-to/unlook-bootloader-root-asus-zenfone-max-t3885457
but it isn't working either, any fastboot command is rebooting the device although bootloader is unlocked.
How do I fix this?
EDIT: Things I have tried:
- Changing USB Cable and Port
- Reinstalling ADB and device driver
- Reunlocking bootloader from UnlockTool (don't know why I did that again)
- Unofficial way to unlock bootloader
None of it helped.
Thanks
Click to expand...
Click to collapse
I suggest to Unlock with unofficial step, or read the post https://www.blocknesia.com/2019/04/unlock-bootloader-dan-install-twrp-asus-zenfone-max-pro-m2.html
Red Magic 5G Bootloader Unlock Guide: OR get ROOT & TWRP without unlocking the BL!!!
***Bootloader Unlock Instructions for the Nubia Redmagic 5G + installing TWRP:***
WARNING: ANY BOOTLOADER UNLOCK METHOD INVOLVES THE RISK OF BRICKING YOUR DEVICE PERMANENTLY. WHILE THERE IS USUALLY A WAY TO RECOVER, DO NOT ATTEMPT THIS PROCEDURE IF YOU DO NOT KNOW WHAT YOU ARE DOING. BAD THINGS CAN HAPPEN. YOU HAVE BEEN WARNED!!! YOU MAY BE LEFT WITH A USELESS BRICK!!! READ ALL FURTHER WARNINGS EXPERIMENTAL METHOD IN ORIGINAL DOWNLOAD FILE WORKS, I'M USING IT
If you want a NOOB guide look at this post: https://forum.xda-developers.com/nu...beginner-tutorial-unlock-bootloader-t4131585/
Also note a user has managed to fix the FP sensor post BL unlock, see this post here: https://forum.xda-developers.com/nu.../guide-calibration-finger-print-loss-t4132961
Still, I suggest root bypass it's better.
MegaNZ Link for Root without unlocking the Bootloader, and without breaking the FP, also includes instructions for installing BlackMagic5G (explanation below), adding HD VOLTE, how to restore from a brick, and some other cool tricks: https://mega.nz/file/igphSCTD#OybJo9t1zwvJ0bdbAcN2BCqxWXAfHdhk3JFB4_5xkVc
I suggest you flash my BlackMagic5G and don't unlock your bootloader at all - just root. It's CN 2.52 ROM based. You'll get VOLTE, , GApps installed, Rooted with Magisk, TWRP, debloated, YouTube Vanced, AdAway, SmartPack Kernel Manager, etc. - looks like the Global / NA variant of the ROM. Almost perfect except still uses Messages and Phone from Nubia. Plus you will enable Face Unlock not available in the Global or NA versions of the ROM, and FP will still work! Click on the Google Search bar widget and the mic icon takes you to the Google Assistant, the left icon is Google Feed, type in the middle bar for a Google Search. Has 1Weather Free weather widget that looks great, and Google Calendar widget for your whole month of activities. Translate, Lens, Chrome, all the Google Apps are there. And the Chinese Nubia apps are nearly all GONE!
MegaNZ Link for BlackMagic5G Beta - IT'S ONLY THE DATA PARTITION + ROOTED KERNEL + NA SPLASH SCREEN, you NEED to 1) install the Red Magic 2.52 ROM below FIRST 2) Root using the first link posted above 3) Flash restore this from TWRP: https://mega.nz/file/r9hF2BwS#RrAXiFWSBNX8dLqfrH8nNHo_uigPC8uYXonwhALhGbo
MegaNZ Link for the Red Magic 5G CN 2.52 ROM: https://mega.nz/file/aoxBFAqY#EDt2OZBGTME4ZGKnERKpK_t-aJT_rWgD0aqBFkilRcY
*** NOW THE BOOTLOADER UNLOCK INSTRUCTIONS ***
Go to Settings / About phone / Build Number (NX659_J_ENCommon_V3.08 on North American Variant), click 7 times, Now you are a developer message appears, go back a menu to Settings / Other system settings / Developer options.
Enable:
OEM unlocking "Allow the bootloader to be unlocked"
USB debugging "Debug mode when USB is connected"
Install Minimal ADB and Fastboot (Windows 10 in this example): https://www.androidfilehost.com/?fid=746010030569952951
Default install path is:
C:\Program Files (x86)\Minimal ADB and Fastboot\
Go to the Search button on the bottom on Windows 10, type cmd, Command Prompt will appear in the menu. Right click it and Run as Administrator. All commands to be typed will be run in this Command Prompt window (referred to as terminal) unless otherwise stated to run on the phone.
Now Terminal window appears (it says Administrator: Command Prompt in the heading):
Text displayed is:
Microsoft Windows
(c) 2020 Microsoft Corporation. All rights reserved.
C:\WINDOWS\system32>
Typed in terminal:
cd "c:\Program Files (x86)\Minimal ADB and Fastboot"
I now connected the phone to a USB port on the PC.
On the phone, a Window appeared:
"Allow USB debugging?"
The computer's RSA key fingerprint is:
[36 digit code] Example:
C8:A17:E2:01:F6:A1
:368:10:E8:33:20:FB:
93:7D
Always allow from this computer (it's my computer so I clicked it since I trust the computer)
CANCEL / ALLOW (I clicked ALLOW)
Typed in terminal:
adb reboot bootloader
The phone reboots. Once the phone screen boots, in the center it says: Now you are in fastboot mode.
From the terminal I typed:
fastboot oem nubia_unlock NUBIA_NX659J
The terminal now displayed:
...
(bootloader) START update nubia fastboot unlock flag!!!
(bootloader) START set state to 1 ok!!!
In the terminal I typed:
fastboot flashing unlock *** DO NOT TYPE THIS IF YOU WANT TO KEEP A WORKING FP!!! READ TOP OF POST!!! AVOID THIS WITH THE EXPERIMENTAL METHOD OF ROOT WITH NO BL UNLOCK ***
Now a screen appeared on the phone with a big <!> red icon in the left corner. The rest in white text is a warning message. "By unlocking the bootloader, you will be able to install custom operating system on this phone. A custom OS is not subject to the same level of testing as the original OS, and can cause your phone and installed applications to stop working properly-
Software integrity cannot be guaranteed with a custom OS, so any data stored on the phone while the bootloader is unlocked may be at risk.
To prevent unauthorized access to your personal data, unlocking the bootloader will also delete all personal data on your phone.
Press the Volume keys to select whether to unlock the bootloader, then the Power Button to continue."
I selected UNLOCK BOOTLOADER and my device was completely erased. The factory OS loaded then. This process takes some time to complete.
Now the device rebooted with a warning message, and a big <!> yellow icon in the left corner.
"The boot loader is unlocked and software integrity cannot be guaranteed. Any data stored on the device may be available to attackers. Do not store any sensitive data on the device.
Visit this link on another device:
g.co/ABH"
Now the device reloads the firmware apparently and wipes all user data. Upon setting up the phone, the fingerprint display registration comes up and asked to place my finger on the back of the phone. There is no fingerprint sensor on the back of the Redmagic 5G! It is under the screen! So this step must be skipped. The ROM setup is corrupt or incomplete, a beta possibly. I setup the phone then went into Settings / Security to try to add a fingerprint. The button to add fingerprint then appears. Once I click the button, I get this error:
Loss of fingerprint calibration data
Loss of fingerprint calibration data was detected.
Currently unable to complete fingerprint entry,
please contact Nuia after-sales service via
4007006600
See the XDA post for recalibrating the FP: https://forum.xda-developers.com/nu.../guide-calibration-finger-print-loss-t4132961
ROOT FOR ALL DEVICES:
(These files are included in the tools download zip, Magisk 20.4 and MagiskManager-v7.5.1.apk, but this is the official source as updates post): Go to XDA and Download Magisk Manager and install the APK. Download the latest Magisk as well from the Manager. You can then reboot to Recovery (volume up + power, release the power button once the screen shows it loading, hold the volume up down until you see TWRP pop up). Flash Magisk from TWRP Install / Zip / sdcard / Magisk.zip reboot and you'll have root.
BL unlock first method was tested on North American variant and it works. But it breaks your FP sensor and gives you an annoying boot prompt.
If at any time you want to remove the OEM Bootloader unlock, you plug into the PC, go to the terminal for Minimal ADB and Fastboot, type:
adb reboot fastboot
fastboot oem nubia_unlock NUBIA_NX659J
fastboot flashing lock (screen will prompt to relock BL, choose to Relock)
The phone should reboot and install the original software. BUT...
If it says you are corrupted well, you have more issues.
You'll have to reflash the stock recovery.img, reboot to stock recovery, wipe data, wipe cache, and flash the CN update.zip rom to a flash drive FORMATTED TO FAT32 (annoying as hell) But you NEED a USB-C to OTG Adapter to attach a Flash Drive / SDCARD this way). If you don't have one, you better reflash TWRP using the prior instructions and flash the update.zip from there. Install, select the update.zip, flash. Wipe Data, Cache, ART/Dalvik. Reboot.
Now it should WIPE the entire phone and be back to normal Android 10 setup non rooted, no unlocked bootloader. Always beware of data loss doing root functions!!! Always be prepared to setup your phone entirely over again. Google Backup is very good to turn on before you do any of this stuff if you have already installed apps.
*** WARNING - THIS BYPASS METHOD COULD GO AWAY AT ANYTIME. IT SHOULD EVENTUALLY BE FIXED BY NUBIA ***
mslezak said:
{Mod edit}
***Bootloader Unlock Instructions for the Nubia Redmagic 5G + installing TWRP:***
Settings / About phone / Build # click 7 times, now your a dev message appears, good back a menu, go to Additional Settings / Developer Options
Enable:
ADB debugging, + OEM unlock
Connect phone to PC, approve device on phone RSA key for USB debugging
From Minimal ADB and Fastboot:
adb reboot bootlader
fastboot oem nubia_unlock NUBIA_NX659J
fastboot flashing unlock
(approve on phone with volume keys to unlock and hit the power button, now you'll get an annoyng mesage on boot as insecure unlocked BL) *ALL YOUR DATA WILL BE WIPED*
Next:
fastboot flash recovery recovery-TWRP-3.4.1B-0324-NUBIA_REDMAGIC_5G-CN-wzsx150.img
fastboot reboot recovery
Enter TWRP, set to not be removed by updates if prompted.
Boot up the device, setup as a new device. You're on stock ROM / kernel now unlocked.
Once you get up and running you'll want APK Mirror app to install stuff on the China Variant it's in the Nubia Playstore. Gboard download as well and set as default it's a lot easier than the Chinese keyboard that swaps between Chinese and English. Set size extra tall for this huge phone (I prefer anyhow). Chrome go download it from APK Mirror app as well. Then go to XDA and Download Magisk Manager and download it and install the APK. Download the latest Magisk as well from the Manager. You can then reboot to Recovery (volume up + power). Flash Magisk from TWRP reboot and you'll have root.
Note on my testing the fingerprint did not work after unlocking the bootloader. It says to contact Nubia support at some odd number. Hopefully they fix this.
Click to expand...
Click to collapse
You were able to actually install TWRP? Not just boot it? I thought A10 devices cant have twrp permanently installed?
That is a very good question my friend. I had to reflash it several times while rooting so it appears you are correct.
Now a window when I FIRST installed popped up and said make Recovery read only so a system update. can't overwrite it, to this I didn't even pay attention. So assuming that question does lock down recovery, it should stick.
mslezak said:
That is a very good question my friend. I had to reflash it several times while rooting so it appears you are correct.
Now a window when I FIRST installed popped up and said make Recovery read only so a system update. can't overwrite it, to this I didn't even pay attention. So assuming that question does lock down recovery, it should stick.
Click to expand...
Click to collapse
So its not permanent? Thats what I thought.
Well it could be permanent...
VZTech said:
So its not permanent? Thats what I thought.
Click to expand...
Click to collapse
What I was trying to say is that I've never had a phone where I had to select "prevent recovery from being overwritten" so I just clicked off the message. Had I selected "keep TWRP from being overwritten" then possibly it sticks. It's just a matter of making the recovery partition READ ONLY.
mslezak said:
What I was trying to say is that I've never had a phone where I had to select "prevent recovery from being overwritten" so I just clicked off the message. Had I selected "keep TWRP from being overwritten" then possibly it sticks. It's just a matter of making the recovery partition READ ONLY.
Click to expand...
Click to collapse
The issue with that could be any future updates though. Rm uses there own recovery for that. They don't provide fastboot images either I believe
Can anyone send me backup of the super partition?
I accidentally flashed an image to the super partition with twrp thinking it was the system partition (it technically is tho) and it bricked my phone and messed up twrp.
Only stock recovery works but the stock recovery cannot fix it by installing a full ota from a otg drive.
I do have a backup on my phone but it is inaccessable.
Could anyone please send me a backup of the super partition or have any idea on how to fix this?
(I tried to use edl and backup my data to recover my backup of the super partition but it seemed like it needed a programmer binary from qualcomm)
Future updates...
VZTech said:
The issue with that could be any future updates though. Rm uses there own recovery for that. They don't provide fastboot images either I believe
Click to expand...
Click to collapse
Yes what I've been told by prior Redmagic Users 3 and 3S is the ROM is released, as long as your boot.img is not patched with Magisk, it can be installed through the menus in Settings / About Phone / Update or someplace like that. You just download the ROM to the appropriate folder on the phone.
So far I have 1 link to a China ROM update here: https://ui.nubia.cn/rom/detail/65
Now on how to install the ROM, I use the Chrome browser set to autotranslate webpages. Most of the Chinese will be translated from here: https://bbs.nubia.com//thread-1136030-1-1.html
Basically it's going to wipe your device clean, and you can use a Nubia backup tool which will save all your items to a folder. Which then you should copy to your PC before installing the new ROM. Then it gives you instructions to get that data back onto your updated device.
apersomany said:
I accidentally flashed an image to the super partition with twrp thinking it was the system partition (it technically is tho) and it bricked my phone and messed up twrp.
Only stock recovery works but the stock recovery cannot fix it by installing a full ota from a otg drive.
I do have a backup on my phone but it is inaccessable.
Could anyone please send me a backup of the super partition or have any idea on how to fix this?
(I tried to use edl and backup my data to recover my backup of the super partition but it seemed like it needed a programmer binary from qualcomm)
Click to expand...
Click to collapse
Your probably screwed. I had this issue on a rm3s. You will need an unbrick tool. It was released for the rm3s about 4 mos after release. NUBIA should have true fastboot images available for download, but they dont.
VZTech said:
Your probably screwed. I had this issue on a rm3s. You will need an unbrick tool. It was released for the rm3s about 4 mos after release. NUBIA should have true fastboot images available for download, but they dont.
Click to expand...
Click to collapse
That's because of the super (dynamic) partition, see from the latest (and only) ROM:
Excerpt of the ROM installation script where it delineates the dynamic vs non dynamic partitions - you have product w/ a file transfer list, then vendor, system, and odm, The other files (boot.img, dtbo.img, splash.img, etc. and other various files) should be flashable with fastboot.
# Update dynamic partition metadata
assert(update_dynamic_partitions(package_extract_file("dynamic_partitions_op_list")));
unmap_partition("product");
block_image_update(map_partition("product"), package_extract_file("product.transfer.list"), "product.new.dat.br", "product.patch.dat");
unmap_partition("vendor");
block_image_update(map_partition("vendor"), package_extract_file("vendor.transfer.list"), "vendor.new.dat.br", "vendor.patch.dat");
unmap_partition("system");
block_image_update(map_partition("system"), package_extract_file("system.transfer.list"), "system.new.dat.br", "system.patch.dat");
unmap_partition("odm");
block_image_update(map_partition("odm"), package_extract_file("odm.transfer.list"), "odm.new.dat.br", "odm.patch.dat");
# --- End patching dynamic partitions ---
apersomany said:
I accidentally flashed an image to the super partition with twrp thinking it was the system partition (it technically is tho) and it bricked my phone and messed up twrp.
Only stock recovery works but the stock recovery cannot fix it by installing a full ota from a otg drive.
I do have a backup on my phone but it is inaccessable.
Could anyone please send me a backup of the super partition or have any idea on how to fix this?
(I tried to use edl and backup my data to recover my backup of the super partition but it seemed like it needed a programmer binary from qualcomm)
Click to expand...
Click to collapse
You should be able to flash the latest ROM via EDL mode if you've ever used EDL mode before, it usually requires shorting pins together in the device, although some recoveries will let you just boot into EDL mode if the phone still boots. It will be detected. Although on this device with the dynamic partition, I don't know how you would flash these in EDL mode... dynamic partitions - you have product w/ a file transfer list, then vendor, system, and odm that do not look like fastboot flashable parts. Possibly the unbrick tool for Redmagic 3/3S could be modified to do this for you.
mslezak said:
That's because of the super (dynamic) partition, see from the latest (and only) ROM:
Excerpt of the ROM installation script where it delineates the dynamic vs non dynamic partitions - you have product w/ a file transfer list, then vendor, system, and odm, The other files (boot.img, dtbo.img, splash.img, etc. and other various files) should be flashable with fastboot.
# Update dynamic partition metadata
assert(update_dynamic_partitions(package_extract_file("dynamic_partitions_op_list")));
unmap_partition("product");
block_image_update(map_partition("product"), package_extract_file("product.transfer.list"), "product.new.dat.br", "product.patch.dat");
unmap_partition("vendor");
block_image_update(map_partition("vendor"), package_extract_file("vendor.transfer.list"), "vendor.new.dat.br", "vendor.patch.dat");
unmap_partition("system");
block_image_update(map_partition("system"), package_extract_file("system.transfer.list"), "system.new.dat.br", "system.patch.dat");
unmap_partition("odm");
block_image_update(map_partition("odm"), package_extract_file("odm.transfer.list"), "odm.new.dat.br", "odm.patch.dat");
# --- End patching dynamic partitions ---
Click to expand...
Click to collapse
Yes those .img files can easily be fastboot flashed. Unfortunately it wont solve his problem. He needs the nubia unbrick tool, which is tough to get. I dont understand why Nubia makes things difficult. They should provide proper Fastboot files.
I already tried edl (not to flash, but to recover my backup of the super partition) but it seems like it needed a firehose binary. I still can use bootloader, fastbootd, recovery. It's just that the recovery fails at assert dynamic partition update thing with a error 7 (probably because my super partition turned into a normal partiton). I tried to flash a super empty image made with lpmake and try flashing the ota but that didn't work. I think if someone gives me a backup of the super partition I could flash that and that could work. I also had an idea of flashing a super partition of another devices factory image to make my super partition a dynamic partition, but I couldn't find any online.
apersomany said:
I already tried edl (not to flash, but to recover my backup of the super partition) but it seems like it needed a firehose binary. I still can use bootloader, fastbootd, recovery. It's just that the recovery fails at assert dynamic partition update thing with a error 7 (probably because my super partition turned into a normal partiton). I tried to flash a super empty image made with lpmake and try flashing the ota but that didn't work. I think if someone gives me a backup of the super partition I could flash that and that could work. I also had an idea of flashing a super partition of another devices factory image to make my super partition a dynamic partition, but I couldn't find any online.
Click to expand...
Click to collapse
I get a Global Device on Monday. I'll try to use Qualcomm tools to make a brick restore image of Global. If I get one made I'll post all the tools to restore the device on Mega.nz. Because of the super partition it has to be done this way. Not via TWRP as you know. I'm working on Dev tools for this device as fast as possible.
mslezak said:
I get a Global Device on Monday. I'll try to use Qualcomm tools to make a brick restore image of Global. If I get one made I'll post all the tools to restore the device on Mega.nz. Because of the super partition it has to be done this way. Not via TWRP as you know. I'm working on Dev tools for this device as fast as possible.
Click to expand...
Click to collapse
Thank you so much!
Okay I can't add anything special but daaamn this community is amazing. So much help I love you all
To relock BL repeat the instructions with 1 different command
Just replace
fastboot flashing unlock
with
fastboot flashing lock
Again you approve to lock on the phone prompt with the volume keys and your phone will be wiped and all will be back to normal, you'll be locked. And back to phone setup.
I'd edit the original post but the moderators took away my rights!!! Because I posted a Telegram link WHY - how do you expect development to get better???
BTW anyone with a NEW phone arriving that can record the FP failures and all errors please contact me so I can send to Nubia. They are waiting for me to reproduce the error but I already setup my new phone... Thinking I wouldn't be the ONLY ONE to contact [email protected] ... Guys you want developer support on this phone or not. Contribute please.
mslezak said:
{Mod edit}
***Bootloader Unlock Instructions for the Nubia Redmagic 5G + installing TWRP:***
Settings / About phone / Build # click 7 times, now your a dev message appears, good back a menu, go to Additional Settings / Developer Options
Enable:
ADB debugging, + OEM unlock
Connect phone to PC, approve device on phone RSA key for USB debugging
From Minimal ADB and Fastboot:
adb reboot bootlader
fastboot oem nubia_unlock NUBIA_NX659J
fastboot flashing unlock
(approve on phone with volume keys to unlock and hit the power button, now you'll get an annoyng mesage on boot as insecure unlocked BL) *ALL YOUR DATA WILL BE WIPED*
Next:
fastboot flash recovery recovery-TWRP-3.4.1B-0324-NUBIA_REDMAGIC_5G-CN-wzsx150.img
fastboot reboot recovery
Enter TWRP, set to not be removed by updates if prompted.
Boot up the device, setup as a new device. You're on stock ROM / kernel now unlocked.
Once you get up and running you'll want APK Mirror app to install stuff on the China Variant it's in the Nubia Playstore. Gboard download as well and set as default it's a lot easier than the Chinese keyboard that swaps between Chinese and English. Set size extra tall for this huge phone (I prefer anyhow). Chrome go download it from APK Mirror app as well. Then go to XDA and Download Magisk Manager and download it and install the APK. Download the latest Magisk as well from the Manager. You can then reboot to Recovery (volume up + power). Flash Magisk from TWRP reboot and you'll have root.
Note on my testing the fingerprint did not work after unlocking the bootloader. It says to contact Nubia support at some odd number. Hopefully they fix this.
Click to expand...
Click to collapse
Just in case if somebody need a Chinese version of official ROM v2.46 for RedMagic 5G.
Code:
https://mega.nz/file/vc0DiabR#npahTop-JXZ9Mwv-lA7G6DxTG2qqOOAf6AwW8NdEEKw
mslezak said:
Just replace
fastboot flashing unlock
with
fastboot flashing lock
Again you approve to lock on the phone prompt with the volume keys and your phone will be wiped and all will be back to normal, you'll be locked. And back to phone setup.
I'd edit the original post but the moderators took away my rights!!! Because I posted a Telegram link WHY - how do you expect development to get better???
BTW anyone with a NEW phone arriving that can record the FP failures and all errors please contact me so I can send to Nubia. They are waiting for me to reproduce the error but I already setup my new phone... Thinking I wouldn't be the ONLY ONE to contact [email protected] ... Guys you want developer support on this phone or not. Contribute please.
Click to expand...
Click to collapse
we found out that using the cn rom it all works without even unlocking the bootloader, even while oem unlock was disabled in dev options but there is some kind of vbmeta img required. a full guide is incoming.
VZTech said:
The issue with that could be any future updates though. Rm uses there own recovery for that. They don't provide fastboot images either I believe
Click to expand...
Click to collapse
You can flash their NX659J-update.zip files directly from TWRP that's how we restored our bricked devices already. So OTA updates no, but you can download them anyway and flash from TWRP directly. Yes we have to figure out a concrete restore method which isn't 100% working yet. I.e. all your data is lost this way apparently AT THIS MOMENT... MORE TO COME.
Nubia Red Magic 5G and 5S Roms and Root support Thread
Second post for TWRP and Magisk installation. Mirror for all roms and tools at end of post
Latest Official Rom updates
Android 11
US/Asia - V8.70 Nubia Link MD%: will update soon
EU - V7.70 Nubia Link MD5: will update soon
China - V9.50 Nubia Link MD5: 361AC13CA52AB83C239783FBAB088CEA
Android 10
US/Asia - V8.12 Nubia Link MD5: 6e930fc2431b3daeae2d94145926a6c1
EU - V7.15 Nubia Link MD5: bb9e3153716851e87f196ae6b4f44a2e
China - V6.23 Nubia Link MD5: BD447840ACA4D48F9443B94D2EAD890F
Change Log - 8.70 / 7.70 Android 11
- Security Patch October 2022
- Game Space enhancements
- Game space Gyro sensitivity menu
- game space touch sample rate improvement
- Fixed: corner of screen non-touchable in some cases
- Fixed: issue where game would fail to close
- Fixed: location of caller display
-Fixed: screen tearing when using 144hz
-
Bugs -
in Testing
- Always on display notification not showing
- memory leak in nubia launcher (requires forced close often to stop phone from lagging)
- small window mode for telegram and discord have wrong zoom/ aspect levels.
_____________________________________________________________________________________________________________
UNBRICK TOOL for 5S - Courtesy of @johnny886
Use this tool, with directions on the thread to restore your device to USA/Asia 8.07
you can then install TWRP and after flash any region rom after creating a somewhat universal unbrick tool for those in different regions.
Follow directions on the thread. but here is a link to the Thread. A Mirror for the tool is in my Personal Mirror at the bottom of this thread post.
Link to Thread
Confirmed working with 5G devices - but its recommended to update as soon as you unbrick.
_____________________________________________________________________________________________________________
For unlocked bootloader
Fix your fingerprint sensor.
here Link
--------------------------------
Update Instructions.
Note
for Android 11 do not flash through TWRP you will softbrick.
____________________________________________________________________
For Stock devices without root
- disable security. No pin, no face unlock, no finger print, no pattern. remove all security.
-download zip file
-go to system update tap three dots and select local update
-Navigate to update.zip and select.
-your phone will reboot and install new rom
- you phone will reboot once more and you will be greeted with your lock screen
- setup Phone with security options as before flash.
For devices with "LOCKED bootloader" Root / TWRP (not tested on A11)
- take backup of vbmeta and recovery partitions in TWRP
- change the name of both files to vbmeta.img and recovery.img
(VBmeta is often 64kb big and Recovery is often 90+mb big.)
- copy and paste these new img files into the update zip.
- flash through TWRP
- go back to main menu, select advanced, then select option
"disable replace TWRP" to keep TWRP as your recovery.
for devices with "Unlocked bootloader" (not tested on A11)
-make full backup
-download zip
-install zip through TWRP
-reboot
__________________________________________________________________________________
Custom Roms and Kernels
Kernel
Mattofthedead's Redmagic 5S kernel for LOS and Stock roms LINK
Roms
Rom Builder Ra's Custom Roms - Please post any bugs or issues in the related threads.
Pixel Experience Plus
Ressurection Remix
NOTE : to boot any Custom rom on the 5S device. Flash the Rom following the directions. then flash Matts LOS kernel Version 3
__________________________________________________________________________________
------------------------------
Old roms
Android 11
V8.65 Nubia Link MD5: 3d52e18c66366d3d23744184425d3926
V8.64 Nubia Link MD5: a7e61f5e2f7c377a6850cf6ac3a62aa7
V7.65 Nubia Link MD5: 746dad5b6145dfba1108355095a6ad46
V7.64 Nubia Link MD5: 55371ee8e5728aee2bc7df5b3a7d6585
V9.42 Nubia Link MD5: D492B92DD83B366508CDD74DE7D152A3
V9.40 Nubia Link MD5: D28F26289A9B75F771EF4F623F0BB367
V8.57 Nubia Link MD5: 266819d4b09c2c52aadb39e948dc84bc
V8.59 Nubia Link MD5: d7e32b7a3e833adc57fcf734aa47f5a3
V7.57 Nubia Link MD5: 81ee71869f660a28b631d871ffb59524
V7.60 Nubia Link MD5:
V9.26 Nubia Link MD5: 8997375CD97D8F7F261F21121FC8EFAA
Android 10
v6.18 Link MD5: 9AC5EA5F64835C1995E4A81D4973FB71
V6.13 Link MD5: F38ED2D7CB58252D308B29D1D4517DB9
V7.07 Link MD5: ffc3fdaf4afc522aa3a084d9275f2cb6
V7.14 Link MD5: 0f879160fbf8b556de5303207b93d0d1
V8.07 Link MD5: b30dab221be73292c5da7884afc0363f
V8.11 Link MD5: 85d9366a3017112cb68d66041e725ce6
________________________________________________________
Personal Mirror - Located in Eastern Canada
________________________________________________________
TWRP and root guide for 5S and 5G on Android 10 only - (these steps will NOT unlock your bootloader) - these steps use a bypass method to install a recovery without unlocking bootloader. the command below is to allow flashing of partitions. bootloader status is still locked during and after process is complete.
Note. if you already have ADB and fastboot drivers installed, this folder will work as is. if not I put an installer in the folder too to install a mini adb fastboot setup. which needs windows driver signing turned off (windows 8-10) this can be done by going to advanced startup and choosing to boot without driver signing.
1. Download zip file found at the end of this post
2. Extract to root of C: drive
3. open CMD prompt with admin privileges
4. CD to the ADB folder you extracted. (CD = Change Directory)
5. Connect your device in Fastboot mode (power off. hold volume down +Power until it vibrates. then release power but continue to hold volume down)
6. Once in fastboot mode, with cable connected to the computer run these commands
7. fastboot oem nubia_unlock NUBIA_NX659J (this allows you to flash the device partitions)
8. fastboot flash recovery TWRP-xxx.img (xxx being the version number of the TWRP image you choose to install)
9. fastboot flash vbmeta vbmeta_skip.img
10. reboot to recovery (from the fastboot menu) it should load TWRP
11. if TWRP does not ask you to keep recovery from being over written, go to advanced and choose disable replace TWRP. to keep TWRP as your recovery, and stop the system from re writing the stock recovery.
12. Reboot to system for the first time and complete the initial setup. this is to create the user space partitions data/media ( preferably do not make a pin or pattern at this stage)
13. once in the rom, connect to PC and copy over the Magisk zip to the internal memory. then reboot holding Volume up
14. once back into TWRP (if you created a pin during setup TWRP will ask you for your pin to access data) go into install and flash the Magisk.zip you moved in step 13 then reboot. once back into the rom, you will see a Magisk app, tap it and allow to update, the APK will install latest version of the manager.
More NOTES.
this must be done on a clean system. you need to wipe all data partitions to boot to system. re writing VBMETA causes encryption to break. until you reboot. so you lose everything Make a backup of your data partition on to your PC before doing anything.
its also recommended to have an update.zip of your current rom (which you can download from the post above), incase you need to reinstall the rom after flashing the new recovery or VBmeta.
OEM unlocking in the developer options is NOT needed. since you are not unlocking your bootloader. this step can be ignored.
I'll update this tutorial with newer steps if needed.
Thanks to those that created all these great tools.
@wzsx150 - for their version of TWRP
John Wu - for Magisk
@mslezak vbmeta_skip
If i've helped you root your device, please hit thanks.
Link ADBmini - zip updated with Magisk 21.4 zip
MD5 for ADBfastbootmini.zip: 0ad97a9ae1539b26ef78c849b169e807
I'm working on a process that will update to Android 11, through TWRP and root, without losing data. Much like a stock update.
I will update the thread once my tests are complete.
Hello. I can not flash (i cant even copy) the zip via TWRP. I see the storage device on my windows laptop. I have wipe data cache and dalvik, but it does not copy it and i can not restore my device. Help will be appreciated
josehdx said:
Hello. I can not flash (i cant even copy) the zip via TWRP. I see the storage device on my windows laptop. I have wipe data cache and dalvik, but it does not copy it and i can not restore my device. Help will be appreciated
Click to expand...
Click to collapse
Try putting update zip on a USB key and connect via OTG and flash this way. Moving files with TWRP for some reason corrupts or does not complete transfer.
Make sure to factory reset. If you're coming from a used update, backup your data partition and wipe everything. Then check to see if the partition is in fact empty. ( I noticed sometime my data partition did not erase)
Patrick Morgan said:
Try putting update zip on a USB key and connect via OTG and flash this way. Moving files with TWRP for some reason corrupts or does not complete transfer.
Make sure to factory reset. If you're coming from a used update, backup your data partition and wipe everything. Then check to see if the partition is in fact empty. ( I noticed sometime my data partition did not erase)
Click to expand...
Click to collapse
Thanks
Working fine after full data partition wipe.
I have an additioal question regarding further updates, and i would not want to open a new topic. so, after flashing the zip, i "lost" TWRP but i already have root access. I wonder if is possible to flash upcoming updates with the default recovery built in on the phone, if not, i would assume i need to install TWRP again.in any case, will side loading update make any problem with the current system? i hope my question and context is clear
As these are official ROMs, they will replace the recovery and remove root from the phone.
If you do not have root, flashing these zips from the system menu local update should work. But if you have root or TWRP it's better to flash through TWRP.
You could just flash TWRP again after flash, but I personally modify the zip and add the recovery to it to save me going into fastboot after each update.
Is it possible to install the US rom on a device with EU rom?
in the EU version I can't set the frame rate to 144 hz.
Darkvenum79 said:
Is it possible to install the US rom on a device with EU rom?
in the EU version I can't set the frame rate to 144 hz.
Click to expand...
Click to collapse
I've spoken with another EU rom user, that has the same issue before. it seems it was an error in the stock rom.
reinstalling 7.07 from the links above should fix your problem.
both 7.07 (the EU rom) and 8.07 (the US rom) are exactly the same. the only difference is the languages from what I can tell.
I have a silly question. Unfortunately i unlocked bootloader and i lost the fingerprint capability. I have tried many times to do the calibration without success. I wonder if a factory flash (EDM or any nubia tool) can restore the capability and then use this guide to do the rooting? Thanks
josehdx said:
I have a silly question. Unfortunately i unlocked bootloader and i lost the fingerprint capability. I have tried many times to do the calibration without success. I wonder if a factory flash (EDM or any nubia tool) can restore the capability and then use this guide to do the rooting? Thanks
Click to expand...
Click to collapse
No it wont.
There is a specific step by step that is required to get it functioning again. And it only survives until your next full wipe, which i assume you will do more often flashing non official roms.
I can grab the steps and edit this post for you.
Edit -
Prep.
have a black / very dark brown leather. (belt, wallet, etc)
a soft gel plaster / Bandaid
(something skin textured and in a pink / light beige colour) texture and colour are important.
First step is clear data in the infingerprint app in app info and remove permissionfor data memory - (you need to show system apps to find it)
- digit in call phone code:
*#9959#
(android 11 use Activity launcher (playstore) to enter fingerprint menu)
- uncheck performance checkbox , check only calibration checkbox
Steps -
1. Press start then wait.
2.Press next and with plaster / bandaid press on circle
3.Press next and use wallet / belt ( the display becomes black for black calibration)
4.Press next and use gel plaster / bandaid again but pinch it in so only the part with your finger touches the circle.
If you are lucky see success alert in green color
In system app in setting In-Display-Fingerprint allow access to data memory then reboot device.
Enjoy your Finger Print once more!
P.S. = do this procedure in a very dark room to improve the chances of it succeeding.
Thanks to qtr1st (Salem) and mikekrunk (Mike) for the steps and information.
josehdx said:
I have a silly question. Unfortunately i unlocked bootloader and i lost the fingerprint capability. I have tried many times to do the calibration without success. I wonder if a factory flash (EDM or any nubia tool) can restore the capability and then use this guide to do the rooting? Thanks
Click to expand...
Click to collapse
esy re-lock bootloader fingrperint work fine without calibration
---------- Post added at 12:13 PM ---------- Previous post was at 12:08 PM ----------
Patrick Morgan said:
TWRP and root guide for 5S - (these steps will NOT unlock your bootloader) - these steps use a bypass method to install a recovery without unlocking bootloader. the command below is to allow flashing of partitions. bootloader status is still locked after process is complete.
Pretty short step by step to get twrp and Magisk if you want, on your phone. (Red Magic 5S)
Note. if you already have ADB and fastboot drivers installed, this folder will work as is. if not I put a installer in the folder too to install a mini adb fastboot setup. which needs windows driver signing turned off (windows 8-10) this can be done by going to advanced startup and choosing to boot without driver signing.
1. Download zip file attached or mirrored
2. Extract to root of C: drive
3. open CMD prompt with admin privileges
4. CD to the ADB folder you extracted.
5. Connect your device in Fastboot mode (power off. hold volume down +Power until it vibrates. then release power but continue to hold volume down)
6. Once in fastboot mode, with cable connected to the computer run these commands
7. fastboot oem nubia_unlock NUBIA_NX659J (this allows you to flash the device partitions)
8. fastboot flash recovery TWRP-xxx.img (xxx being the version number of the TWRP image you choose to install)
9. fastboot flash vbmeta vbmeta_skip.img
10. reboot to recovery (from the fastboot menu) it should load TWRP
11. if TWRP does not ask you to keep recovery from being over written, go to advanced and choose disable overwrite TWRP. to keep TWRP as your recovery, and stop the system from re writing the stock recovery.
12. Magisk zips files are in the folder. copy to device and flash through twrp. and install the apk after boot. done twrp and root.
More NOTES.
this must be done on a clean system. you need to wipe all data partitions to boot to system. re writing VBMETA causes encryption to break. until you reboot. so you lose everything Make a backup of your data partition on to your PC before doing anything.
its also recommended to have a update.zip of your current rom (which you can download from the post above), incase you need to reinstall the rom after flashing the new recovery or VBmeta.
OEM unlocking in the developer options is NOT needed. since you are not unlocking your bootloader. this step can be ignored.
I'll update this tutorial with newer steps if needed.
Thanks to those that created all these great tools.
@wzsx150 - for their version of TWRP
John Wu - for Magisk
@mslezak vbmeta_skip
If i've helped you root your device, please hit thanks.
Link ADBmini
MD5 for ADBfastbootmini.zip: e49f162080c6a2124c243716546ad710
Click to expand...
Click to collapse
where is the link of twrp.img
sansha1211 said:
where is the link of twrp.img
Click to expand...
Click to collapse
Patrick Morgan said:
Link ADBmini
MD5 for ADBfastbootmini.zip: e49f162080c6a2124c243716546ad710
Click to expand...
Click to collapse
that file called Link ADBmini has all you need
Is it ok to flash Eu rom to my NA/asia rom?
After reboot it ask me for verify pin and now I can't load the TWRP.img Partition volume Full error help me please
Rai972 said:
After reboot it ask me for verify pin and now I can't load the TWRP.img Partition volume Full error help me please
Click to expand...
Click to collapse
reboot to bootloader by... power off device -> press and hold volume down and power button until you see the logo -> connect device to your computer then do the steps 7 to 12
also once you are in TWRP make sure you ... this must be done on a clean system. you need to wipe all data partitions to boot to system. re writing VBMETA causes encryption to break. until you reboot. so you lose everything Make a backup of your data partition on to your PC before doing anything.
7. fastboot oem nubia_unlock NUBIA_NX659J (this allows you to flash the device partitions)
8. fastboot flash recovery TWRP-xxx.img (xxx being the version number of the TWRP image you choose to install)
9. fastboot flash vbmeta vbmeta_skip.img
10. reboot to recovery (from the fastboot menu) it should load TWRP
11. if TWRP does not ask you to keep recovery from being over written, go to advanced and choose disable overwrite TWRP. to keep TWRP as your recovery, and stop the system from re writing the stock recovery.
12. Magisk zips files are in the folder. copy to device and flash through twrp. and install the apk after boot. done twrp and root.
Rai972 said:
After reboot it ask me for verify pin and now I can't load the TWRP.img Partition volume Full error help me please
Click to expand...
Click to collapse
if you have not removed your pin before flashing any of the roms. it asks you for YOUR own pin that you made when you setup the phone. so use your own pin.
the process of rooting your device, clears a security partition. (the VBmeta partiton)
this deletes the encryption you had on your phone. so the devices partitions are unaccessable and need to be wiped before you can boot to system.
you need to clear data. all data. then check in TWRP file browser if your data partition is clear. .. if you see folders with random letters its not been formatted correctly.
so, in the wipe menu on TWRP you should go into advanced and change the partition type to ext4 then back to f2fs to clear the partition of data.
once your phone is clear you should be able to wipe cache and davik then reboot to system for it to start like a factory reset.
sansha1211 said:
esy re-lock bootloader fingrperint work fine without calibration
---------- Post added at 12:13 PM ---------- Previous post was at 12:08 PM ----------
where is the link of twrp.img
Click to expand...
Click to collapse
How should i relock the bootloader? Via cmd, command doesn't work. Should i lock also via developer options?
josehdx said:
How should i relock the bootloader? Via cmd, command doesn't work. Should i lock also via developer options?
Click to expand...
Click to collapse
adb devices
adb reboot bootloader
fastboot devices
fastboot flashing lock
josehdx said:
How should i relock the bootloader? Via cmd, command doesn't work. Should i lock also via developer options?
Click to expand...
Click to collapse
via cmd -- fastboot flashing lock
After i reboot in TWRP and disable replace TWRP, i install magisk from a USB otg, and then i wipe all data, then i reboot system but it keeps opening TWRP in every reboot, i had to install Stock Rom to have my phone back but without root, what im doing wrong?? thanks
Edit: now it worked, tried a few times and worked don't know what failed