Related
There doesn't seem to be a comprehensive guide on this, so I thought I would provide one.
READ THIS FIRST
DO NOT TAKE ANY OTA UPDATES!!!
Please consider the following:
Ask yourself these two questions: "Why do I want to unlock my bootloader? Why do I need root access?" If the answer to either one of those is "I don't know," don't do it. Both of these actions weaken the security of your phone, and there's no reason to do that if you're not sure why.
This guide is for the Droid Turbo, model XT1254. It is not for the Droid Turbo 2, and it is not for any phone that is not named Droid Turbo.
Standard XDA rules apply. I'm not responsible for anything you do, and neither is anyone else other than you.
I'm assuming that you are running a Windows PC. If you have a Mac, I can't help you. If you're running Linux, you shouldn't need help.
This method is not free. It costs $25 (USD). If that's not okay with you, don't do this.
Once your bootloader is unlocked, you CANNOT safely re-lock and unlock it again. See this thread for what happens when you try to do that: http://forum.xda-developers.com/droid-turbo/help/relocked-bootloader-bricked-t3306081#post65095391
Still here? Cool.
Section 0: Installing Firmware Version MCG24.251-5
1. Go to Settings -> About phone -> Build number. If it says SU4TL-44, SU4TL-49 or MCG24.251-5, skip to section 1 of this guide. If it says MCG24.251-5-5, you need to take an extra step to unlock your bootloader. I'll explain later. For now, just skip to section 1 of this guide. If it says anything else, keep reading.
Flashing MCG24.251-5 using this method will erase all of your data. Back up any important files/information before proceeding.
2. Download and install Minimal ADB and Fastboot from here: http://forum.xda-developers.com/showthread.php?t=2317790.
3. Download and install the Motorola Device Manager from here: https://motorola-global-portal.custhelp.com/app/answers/detail/a_id/88481
4. Download the MCG24.251-5 firmware package from here: https://www.androidfilehost.com/?fid=889764386195901169
5. Extract the contents of the MCG24.251-5 firmware package to the installation directory of Minimal ADB and Fastboot (C:\Program Files (x86)\Minimal ADB and Fastboot on any 64-bit installation of Windows).
6. Power off your phone.
7. Hold down the volume down button and power on your phone. Release the volume down button when you see that the phone has booted into bootloader mode. You'll see a dead green android.
8. Plug the phone into your computer.
9. Open the Minimal ADB and Fastboot shortcut on your desktop. This will open a command prompt.
10. Type "fastboot devices" and press enter. If it displays your device's serial number, you're ready to go. If it displays nothing, your computer is not recognizing your device properly.
11. Navigate to the installation directory of Minimal ADB and Fastboot and double click on FlashAll.bat. This will flash MCG24.251-5 to your device and erase all of your data.
12. Use the power button to select Start in the bootloader menu to boot normally.
13. Set up your phone at least to the point where you can install apps if you want to.
For now, just try to ask someone nicely to help you out with this. I'll try to get this done before the end of the day.
Section 1: Unlocking the Bootloader
1. Download Sunshine from here: http://theroot.ninja/download.html
2. Move the apk file to a convenient location on your phone. If you downloaded it with your phone, it's in your downloads folder already, so leave it there.
3. Use any file browser on your phone to navigate to the folder that contains the Sunshine apk file. Tap on it to install it.
4. If a message comes up and says that you need to enable installation of apps from unknown sources, follow the instructions on that message to enable it.
5. Enable Wi-Fi on your phone if it is disabled. Even if you aren't connected to a Wi-Fi network, it still needs to be on.
6. !!!DO THIS STEP ONLY IF YOU'RE ON MCG24.251-5-5!!! Follow the instructions here to obtain temporary root: https://forum.xda-developers.com/g4-play/development/root-autoinitroot-motorola-bootloader-t3639316/. DO NOT perform the uninstall step.
7. Open your app drawer and start Sunshine.
8. Follow the instructions.
9. !!!FOR MCG24.251-5-5 ONLY!!! Sunshine will reboot your phone automatically, and it will go into a bootloop. This is normal. Don't panic. Hold down the volume down button until the phone goes into bootloader mode. Plug your phone into the computer, start Minimal ADB and Fastboot (see Section 0 for link if you didn't have to install it before this point), and enter the command fastboot oem config fsg-id "". This will disable the temporary root exploit. Reboot your phone normally, and everything should be happy again.
10. If, when your phone reboots, you see a "Warning: The bootloader is unlocked" message, you have successfully unlocked your bootloader. If you do not see this message, open Sunshine again and follow the directions again. If you're on MCG24.251-5-5, you'll have to gain and uninstall temproot again at the appropriate times.
Section 2: Installing TWRP
Team Win Recovery Project is arguably the most important tool to have on a bootloader-unlocked phone. This is how you install it:
1. Download and install Minimal ADB and Fastboot from here: http://forum.xda-developers.com/showthread.php?t=2317790. If you already did this in section 0, you don't have to do it again.
2. Download the latest TWRP .img file from here: https://www.androidfilehost.com/?w=files&flid=39562
NOTE: The TWRP file that you download should have a .img extension. Make sure you can see this. If you don't see .img at the end of the filename, Google how to make file extensions visible on your version of Windows and do it. If you do not do this, you may run into trouble later.
3. Download and install the Motorola Device Manager from here: https://motorola-global-portal.custhelp.com/app/answers/detail/a_id/88481. If you already did this in section 0, you don't have to do it again.
3. Rename the file that you downloaded in step 2 to TWRP.img
4. Copy TWRP.img to the directory that you installed Minimal ADB and Fastboot to. The default location on an installation of 64-bit Windows is C:\Program Files (x86)\Minimal ADB and Fastboot.
5. Turn off your phone.
6. Hold the volume down button and press the power button to boot into bootloader mode. You should see a green android lying on his back with his chest open, and some information about your phone. Poor little guy...
7. Plug your phone into your PC.
8. Double click on the Minimal ADB and Fastboot shortcut that's on your desktop. It will open a command prompt.
9. Type "fastboot devices" without quotes and press enter. If it gives you your phone's serial number, you're good to go. If it gives you nothing, your device is not detected. This can happen for several reasons, and I won't discuss them here. However, if you followed these directions and all of your hardware is functioning properly, you should be good to go.
10. Type "fastboot flash recovery TWRP.img" without quotes and press enter. It should tell you that the flash was successful. You might see some "not found" errors. These are normal and can be ignored.
11. Highlight "Recovery mode" on your phone using the volume up and down buttons.
12. Press the power button to boot into TWRP.
13. TWRP will boot, and it will ask you if you want to allow write access to the system partition. IT IS VERY IMPORTANT THAT YOU ALLOW THIS. Check the box that says to never ask this question again.
14. Select Reboot, followed by System to boot the phone normally.
Section 3: Gaining Root Access
If you intend to install a custom rom, these steps are not necessary. Custom roms almost always come with root access built in. Refer to the thread of your custom rom of choice for installation instructions.
If you do not want a custom rom, and you simply want root access on the stock Droid Turbo rom, continue reading.
1. If you are on the stock marshmallow rom, build MCG24.251-5 or higher, download the latest version of both Magisk and Magisk Manager to your phone: https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445.
NOTE: You need to be on marshmallow to use Magisk to root your phone. The Magisk thread says it supports lollipop and higher, but it only supports lollipop for some stock Samsung roms. This does not apply to you. If you want to root your phone on lollipop, you'll need to use SuperSU. I won't go into that here because I don't think there is a lot of demand for it, but if you need help with that, reach out to someone here. It's not difficult.
2. Install Magisk Manager the same way you installed Sunshine.
3. Turn off your phone.
4. Hold the volume down button and press the power button to boot into bootloader mode. You should see a green android lying on his back with his chest open, and some information about your phone. Andy, what have they done to you?
5. Use the volume up and down buttons to highlight "Recovery mode."
6. Press the power button to select Recovery mode.
7. Select Install from the TWRP main menu.
8. Select the most recent version of Magisk (the .zip file, NOT the Magisk Manager .apk file) that you downloaded.
9. Swipe the bar at the bottom of the screen to flash this zip file.
10. When it finishes, select Wipe Cache/Dalvik and swipe the bar at the bottom of the screen.
11. Select Reboot System
Section 4: Passing Safetynet using Stock, Unrooted Marshmallow
If you are running stock marshmallow with an unlocked bootloader, you will fail safetynet verification (and be unable to use Android Pay). Installing Magisk is the only recommended method, as of this writing, to bypass this limitation. If you completed Section 3, you shouldn't have any trouble. Understand, however, that there is a constant game of cat and mouse going on between Google and Magisk's developer, so sometimes Google will update safetynet to beat Magisk. If that happens, wait for Magisk Manager to tell you that a new version of Magisk is available, and it will install the new version for you. That's your best bet for passing safetynet again.
If you really want to pass safetynet, but you really don't want to be rooted, you can disable root (Superuser access) in the Magisk Manager settings.
Section 5: Miscellaneous
Here are some links to stuff you can flash now that your bootloader is unlocked:
Official LineageOS 12.1 (Android 5.1.1): http://forum.xda-developers.com/dro.../moto-maxx-xt1225-droid-turbo-xt1254-t3260253
Official LineageOS 13.0 (Android 6.0.1): http://forum.xda-developers.com/dro.../moto-maxx-xt1225-droid-turbo-xt1254-t3353298
AOSPExtended (Android 7.X): https://forum.xda-developers.com/moto-maxx/general/rom-aospextended-rom-v3-1-t3555361
Unofficial LineageOS 14.1 (Android 7.X): http://forum.xda-developers.com/moto-maxx/development/rom-t3494646
crDroid (Android 7.X): http://forum.xda-developers.com/moto-maxx/development/rom-crdroid-android-t3491257
Android Open Kang Project (Android 7.X): http://forum.xda-developers.com/droid-turbo/development/rom-aokp-7-x-quark-t3504629
Resurrection Remix (a great LineageOS-based rom, Android 5.1.1): http://forum.xda-developers.com/moto-maxx/development/rom-resurrection-remix-5-5-5-t3197643
Resurrection Remix (Android 6.0.1): http://forum.xda-developers.com/moto-maxx/development/rom-resurrection-remix-t3316232
Resurrection Remix (Android 7.X): https://forum.xda-developers.com/moto-maxx/development/rom-resurrection-remix-t3511109
Computerfreek274's optimized stock rom (Android 6.0.1): http://forum.xda-developers.com/droid-turbo/development/computerfreekunlocked1-0-t3255945
MoKee Open Source Project (Android 6.0.1): http://forum.xda-developers.com/moto-maxx/development/rom-mokee-opensource-project-t3188936
Bliss Rom (Android 6.0.1): http://forum.xda-developers.com/droid-turbo/development/rom-bliss-rom-6-4-team-bliss-t3422937
Android Open Kang Project (Android 6.0.1): http://forum.xda-developers.com/droid-turbo/development/rom-android-kang-project-t3422456
Android Open Kang Project (Android 7.X): https://forum.xda-developers.com/droid-turbo/development/rom-aokp-7-x-quark-t3504629
Change the splash screen (the bootloader unlocked warning message) that you see when you first start your phone: http://forum.xda-developers.com/dro...custom-boot-logos-accepting-requests-t3262873
Xposed framework and installer (make sure to use the sdk22-arm version if you're running a lollipop rom, sdk23-arm if you're running marshmallow. Not available for nougat yet.): http://forum.xda-developers.com/showthread.php?t=3034811
Alternative Material Design Xposed Installer that provides additional features: http://forum.xda-developers.com/xposed/material-design-xposed-installer-t3137758
Pon-3 Audio Mod (modified and improved Viper4Android. It makes your phone sound better.): http://forum.xda-developers.com/showthread.php?t=2530976
Other modded Viper4Android versions that are better than PON-3: http://forum.xda-developers.com/android/software/viperaudio-viperatmos-3-8-sq-driver-t3289075
Theme your TWRP with different colors: http://forum.xda-developers.com/android/themes/theme-twrp-3-0-0-0-dark-stock-colors-t3310235
More TWRP themes: http://forum.xda-developers.com/showpost.php?p=66276401&postcount=2889
Android N Emojis: http://android.wonderhowto.com/how-to/get-android-nougats-all-new-emojis-right-now-0170328/
Section 6: Troubleshooting
Issue: When you try to boot TWRP, you see a screen that says "no command." TWRP does not boot.
Solution: The screen you are seeing is the stock Droid Turbo recovery menu (the menu that you're trying to replace with TWRP). If you see this after flashing TWRP, one of two things happened:
-You did not boot into the recovery menu immediately after flashing TWRP, and it was therefore replaced by the stock recovery menu.
-When you flashed TWRP, the process did not complete successfully.
The solution to both of these problems is to repeat section 2 and follow the instructions more carefully.
Issue: When TWRP asked you if you wanted to allow write access to the system partition, you selected no. Now you cannot flash anything.
Solution: At the main TWRP menu, select Mount. Uncheck the box that says "Mount system partition as read-only."
Issue: Fastboot says "cannot load TWRP.img" when you try to flash it.
Solution: This error indicates that Fastboot cannot find TWRP.img. The most common source of this problem is that you did not make your file extensions visible, and so when you renamed the TWRP file to TWRP.img, you actually renamed it to TWRP.img.img (including the hidden .img file extension that you didn't realize was there). Google how to enable file extensions on your version of Windows, follow those instructions, and if this is the issue you will see it.
nice write up - will follow these when I get my phone tomorrow.
worked!
Just tried this. Worked amazingly, and exactly as you described! Thanks!!
Thanks just got this phone yesterday. I came from a Verizon s4 with a unlockable bootloader so now running cm on a phone is really awesome for me. Although I was concerned about the $25. I love paying people for there work but it seemed different and I was expecting the app to be a scam or something. However everything went okay. I wish there was a way to get viper4android working. Does anyone know about that? I thought installing cm would have fixed the issue. Anyways thanks a lot. I wonder if I can change my username. Lol.
I keep getting a "no command" screen after step 6 in section 3. Everything else worked perfect. Any ideas?
22e said:
I keep getting a "no command" screen after step 6 in section 3. Everything else worked perfect. Any ideas?
Click to expand...
Click to collapse
So you can't boot into twrp?
Sent from my XT1254 using Tapatalk
SpyderPride said:
So you can't boot into twrp?
Sent from my XT1254 using Tapatalk
Click to expand...
Click to collapse
Nope, no matter what I do, it stays on that screen. I have to reboot and then it returns to normal. I've followed all of the steps twice now and got the same results each time. I do have the phone still plugged into the computer charging.
s4shield said:
Thanks just got this phone yesterday. I came from a Verizon s4 with a unlockable bootloader so now running cm on a phone is really awesome for me. Although I was concerned about the $25. I love paying people for there work but it seemed different and I was expecting the app to be a scam or something. However everything went okay. I wish there was a way to get viper4android working. Does anyone know about that? I thought installing cm would have fixed the issue. Anyways thanks a lot. I wonder if I can change my username. Lol.
Click to expand...
Click to collapse
https://www.androidfilehost.com/?w=files&flid=44797 try this just flash it through TWRP its basically viper4android i've used it before
5.1
HI, I am on SU3TL-39, android 5.1, system 23.11.39.quark_verizon.verizon.en.US vzw.
I have been holding off on an OTA that my phone keeps prompting me to do, should I now take that OTA?
CatMan8 said:
HI, I am on SU3TL-39, android 5.1, system 23.11.39.quark_verizon.verizon.en.US vzw.
I have been holding off on an OTA that my phone keeps prompting me to do, should I now take that OTA?
Click to expand...
Click to collapse
if u want an unlocked bootloader then take the OTA
22e said:
I keep getting a "no command" screen after step 6 in section 3. Everything else worked perfect. Any ideas?
Click to expand...
Click to collapse
The screen that you're seeing is the stock Droid Turbo recovery menu, which means that TWRP is not getting flashed. What result does it give you after section 2, step 10?
s4shield said:
Thanks just got this phone yesterday. I came from a Verizon s4 with a unlockable bootloader so now running cm on a phone is really awesome for me. Although I was concerned about the $25. I love paying people for there work but it seemed different and I was expecting the app to be a scam or something. However everything went okay. I wish there was a way to get viper4android working. Does anyone know about that? I thought installing cm would have fixed the issue. Anyways thanks a lot. I wonder if I can change my username. Lol.
Click to expand...
Click to collapse
Yeah, I did the exact same thing. The MDK bootloader is golden. I broke my phone once and almost cried. Luckily, I was able to get another MDK on Swappa. The seller wasn't even charging extra for it! He/she must not have known what they had.
As for Viper4Android, I've added a link to section 4 that you might want to look at.
iceblitz4 said:
https://www.androidfilehost.com/?w=files&flid=44797 try this just flash it through TWRP its basically viper4android i've used it before
Click to expand...
Click to collapse
Thanks! If I can only remove all the brony stuff from the app. Lol. I guess I can change the icon. I have to pretend at least that I don't have a mangina when I'm with my friends. No seriously this post made my day. I thought I was stuck without viper on my phone.
s4shield said:
Thanks! If I can only remove all the brony stuff from the app. Lol. I guess I can change the icon. I have to pretend at least that I don't have a mangina when I'm with my friends. No seriously this post made my day. I thought I was stuck without viper on my phone.
Click to expand...
Click to collapse
Such is life. Sometimes if you want the wubz, you gotta take the brony.
TheSt33v said:
Such is life. Sometimes if you want the wubz, you gotta take the brony.
Click to expand...
Click to collapse
Ha ha ha!
successful for me, thanks!
to comment on @22e issue, I had the same problem. i was able to correct it by copying the TWRP.img file to the same directory as the minimal adb fastboot files were installed in.
also, a shortcut after flashing TWRP is to type "fastboot reboot-bootloader". this will return back to bootloader rather than having to reboot, power off, and then press the buttons to get to bootloader.
hope this helps.
Awesome post. It definitely will come in handy. One question, at what point should I create a backup image via twrp? Is it before section 3 step 7?
s4shield said:
Thanks just got this phone yesterday. I came from a Verizon s4 with a unlockable bootloader so now running cm on a phone is really awesome for me. Although I was concerned about the $25. I love paying people for there work but it seemed different and I was expecting the app to be a scam or something. However everything went okay. I wish there was a way to get viper4android working. Does anyone know about that? I thought installing cm would have fixed the issue. Anyways thanks a lot. I wonder if I can change my username. Lol.
Click to expand...
Click to collapse
Download the file www.viperforandroid.com install goto menu set as expert ui under ui setting open viper4android check on click box click appropriate sound changer so it sounds right to u I suggest doing on headphones than use thoose settings as base settings for phone bt ect.. The the real good sound comes in under conolover files you must download impulse response files or. Irs files dfx_pro_surround_2.irs, Dolby,, dfx ect. After u download you unzip and using a file manager find unzipped file and goto sd card u will see viper4android folder inside that folder you will see 2 other folders one being kernel place irs files in kernel folder. Now when you click impulse response you will have the audio producing files. Like Dolby digital cinema, stereo, HD. Ect there are hundreds I'll post my walk though install video
can you help me sir
my friend have verizon moto droid ultra xt1254 and he already give it to me
and i got this phone with google account privacy and he forgot last email in this device, so i cant finished setup wizard and go to home screen
this device locked bootloader so i cant do something to
what should i can do?
jco23 said:
successful for me, thanks!
to comment on @22e issue, I had the same problem. i was able to correct it by copying the TWRP.img file to the same directory as the minimal adb fastboot files were installed in.
also, a shortcut after flashing TWRP is to type "fastboot reboot-bootloader". this will return back to bootloader rather than having to reboot, power off, and then press the buttons to get to bootloader.
hope this helps.
Click to expand...
Click to collapse
Thanks for the help.
After I got stuck, I downloaded and installed KingRoot. It successfully rooted my phone. I downloaded two different root checkers and they confirmed. Everything works correctly within Rom Toolbox Pro now, I can remove apps (stupid NFL mobile, Amazon, etc). My software status says "Modified". I did not need to format or anything like that. Is that normal? My only issues are with XBlast Tools and SuperSU, when I change a setting in XBlast, it does NOT get updated. Even after a reboot. In SuperSU cannot update binaries for some reason.
I cannot post outside links for screen shots yet.
Recently I unlocked the bootloader on my ZF5 to flash a modded cm 13 ROM, but after that I found out that the camera stopped working. I know somehow it is happening because I unlocked the bootloader incorrectly. I searched many solutions but any of them corrected the problem. When I open any camera app, all I see is a black image. Some one please help me with this. Thx.
The only fix...
Dude, i have that problem too. No custom rom can fix our camera as we have Zen5(A500CG/A501CG) with different hardware models. Most of the zen5 devices work fine after unlocking bootloader but my friend....our cameras won't work if we unlock bootloader. I have tried each and every methods to unlock and each and every custom rom available over the net but no luck. Camera remains black/dark/blank. The only solution is to revert back to stock OS. Start flashing with this version UL-ASUS_T00F-WW-2.21.40.30-user.zip, otherwise the camera won't work in stock too.
If u want to stay on custom rom(as im doing right now, i love CM), then install pixelmaster camera from play store, turn ON flash, set focus to INFINITY.......the camera will be blank but at least it will capture images.
a8962383 said:
Dude, i have that problem too. No custom rom can fix our camera as we have Zen5(A500CG/A501CG) with different hardware models. Most of the zen5 devices works fine after unlocking bootloader but my friend....our cameras won't work if we unlock bootloader. I have tried each and every methods to unlock and each and every custom rom available over the net but no luck. Camera remains black/dark/blank. The only solution is to revert back to stock OS. Start flashing with this version UL-ASUS_T00F-WW-2.21.40.30-user.zip, otherwise the camera won't work in stock too.
If u want to stay on custom rom(as im doing right now, i love CM), then install pixelmaster camera from play store, turn ON flash, set focus to INFINITY.......the camera will be blank but at least it will capture images.
Click to expand...
Click to collapse
Do you know a guide to go back to stock rom and relock the bootloader?
soares7vinicius said:
Do you know a guide to go back to stock rom and relock the bootloader?
Click to expand...
Click to collapse
The proper way to revert back to stock is as below:
1. Download ADB folder and extract: https://drive.google.com/file/d/0B-Fin8UxrD6PUmN6SkVPMXR3UTA/view
2. Download UL-ASUS_T00F-WW-2.21.40.30-user.zip(for WW model only ) and copy to ADB folder: http://dlcdnet.asus.com/pub/ASUS/Ze...ser.zip?_ga=1.182320871.1398112610.1460908265
3. If you have other than WW model, please search and download the UL-ASUS_T00F-WW-2.21.40.30-user.zip here: https://www.asus.com/id/support/Download/39/1/0/2/96nqlxHp1VKV4Rdz/32/
4. Extract the fastboot.img, boot.img, and recovery.img files from the downloaded rom/zip file and copy to ADB folder
5. Reboot your device to bootloader. Turn off device > press volume up+power button together > after asus logo appears, release power but keep vol up pressed > you are in bootloader mode. Go to ADB folder and open command window(CMD) there by pressing shift+right mouse click
6. Run this commands,
Code:
fastboot flash fastboot fastboot.img
fastboot reboot-bootloader
wait for reboot...
Code:
fastboot flash boot boot.img
fastboot flash recovery recovery.img
7. Now select recovery from the fastboot menu and wait for reboot to recovery
8. In the recovery select wipe/factory reset data, this may take some time
9. Then select wipe cache
10. Then select apply update from ADB
11. Run this command,
Code:
adb sideload UL-ASUS_T00F-WW-2.21.40.30-user.zip
12. Let it be installed. It will take around 10mins, then reboot system.
13. You will find kitkat is installed.
14. Download UL-ASUS_T00F-WW-2.22.40.54-user.zip, UL-ASUS_T00F-WW-3.24.40.78-user.zip, UL-ASUS_T00F-WW-3.24.40.87-user.zip from this link for your model: https://www.asus.com/id/support/Download/39/1/0/2/96nqlxHp1VKV4Rdz/32/
15. Copy the UL-ASUS_T00F-WW-2.22.40.54-user.zip file into your SDCard/internal storage, then disconnect usb cable. Your phone will detect an update and proceed with the update.
16. Do step 15 for other two files as well. Please follow the sequence of the files, otherwise the update will fail.
17. Enjoy stock lollipop on your zen 5.
Hope it helps.
a8962383 said:
The proper way to revert back to stock is as below:
1. Download ADB folder and extract:
2. Download UL-ASUS_T00F-WW-2.21.40.30-user.zip(for WW model only ) and copy to ADB folder:
3. If you have other than WW model, please search and download the UL-ASUS_T00F-WW-2.21.40.30-user.zip here:
4. Extract the fastboot.img, boot.img, and recovery.img files from the downloaded rom/zip file and copy to ADB folder
5. Reboot your device to bootloader. Turn off device > press volume up+power button together > after asus logo appears, release power but keep vol up pressed > you are in bootloader mode. Go to ADB folder and open command window(CMD) there by pressing shift+right mouse click
6. Run this commands,
Code:
fastboot flash fastboot fastboot.img
fastboot reboot-bootloader
wait for reboot...
Code:
fastboot flash boot boot.img
fastboot flash recovery recovery.img
7. Now select recovery from the fastboot menu and wait for reboot to recovery
8. In the recovery select wipe/factory reset data, this may take some time
9. Then select wipe cache
10. Then select apply update from ADB
11. Run this command,
Code:
adb sideload UL-ASUS_T00F-WW-2.21.40.30-user.zip
12. Let it be installed. It will take around 10mins, then reboot system.
13. You will find kitkat is installed.
14. Download UL-ASUS_T00F-WW-2.22.40.54-user.zip, UL-ASUS_T00F-WW-3.24.40.78-user.zip, UL-ASUS_T00F-WW-3.24.40.87-user.zip from this link for your model:
15. Copy the UL-ASUS_T00F-WW-2.22.40.54-user.zip file into your SDCard/internal storage, then disconnect usb cable. Your phone will detect an update and proceed with the update.
16. Do step 15 for other two files as well. Please follow the sequence of the files, otherwise the update will fail.
17. Enjoy stock lollipop on your zen 5.
Hope it helps.
Click to expand...
Click to collapse
Thanks! I'll try it. But after that the bootloader will be relocked?
soares7vinicius said:
Thanks! I'll try it. But after that the bootloader will be relocked?
Click to expand...
Click to collapse
yes, it will be locked.
a8962383 said:
yes, it will be locked.
Click to expand...
Click to collapse
After doing step 6, I can't boot into recovery. What's wrong?
soares7vinicius said:
After doing step 6, I can't boot into recovery. What's wrong?
Click to expand...
Click to collapse
when u reboot into recovery, u will see an android logo with "!" sign. Now, press.......Power + Vol Down + Vol UP sequentially at a time.
a8962383 said:
when u reboot into recovery, u will see an android logo with "!" sign. Now, press.......Power + Vol Down + Vol UP sequentially at a time.
Click to expand...
Click to collapse
Thanks, but I found another problem, when i sideload this package to recovery it shows that i need to upgrade to newest 4.3 image first. What package is that?
Edit: Forget it, it worked! Thanks!
soares7vinicius said:
Thanks, but I found another problem, when i sideload this package to recovery it shows that i need to upgrade to newest 4.3 image first. What package is that?
Click to expand...
Click to collapse
If the firmware flashing is successful, just follow the steps. Don't read or worry about anything in the console. Please follow the firmware up-gradation version as I mentioned, otherwise it will fail.
Btw, did you check the how many cores online with your kernel from kernel adiutor?
If you use hotplug as governor, camera won't start and you need 4 of 4 cores.
soares7vinicius said:
Recently I unlocked the bootloader on my ZF5 to flash a modded cm 13 ROM, but after that I found out that the camera stopped working. I know somehow it is happening because I unlocked the bootloader incorrectly. I searched many solutions but any of them corrected the problem. When I open any camera app, all I see is a black image. Some one please help me with this. Thx.
Click to expand...
Click to collapse
Delete
a8962383 said:
Dude, i have that problem too. No custom rom can fix our camera as we have Zen5(A500CG/A501CG) with different hardware models. Most of the zen5 devices work fine after unlocking bootloader but my friend....our cameras won't work if we unlock bootloader. I have tried each and every methods to unlock and each and every custom rom available over the net but no luck. Camera remains black/dark/blank. The only solution is to revert back to stock OS. Start flashing with this version UL-ASUS_T00F-WW-2.21.40.30-user.zip, otherwise the camera won't work in stock too.
If u want to stay on custom rom(as im doing right now, i love CM), then install pixelmaster camera from play store, turn ON flash, set focus to INFINITY.......the camera will be blank but at least it will capture images.
Click to expand...
Click to collapse
Man, so this is a error on a Drive ?!
So, why the mans can put the Asus camera on the roms, or, can fix this ?
I think this is a driver error and can be solved ?
JulianoJr said:
Man, so this is a error on a Drive ?!
So, why the mans can put the Asus camera on the roms, or, can fix this ?
I think this is a driver error and can be solved ?
Click to expand...
Click to collapse
It's not a driver error. Many developers have already ported Asus Pixelmaster camera with their ROMs and with proper drivers as well. The main problem is, there are few Zen5 devices which use camera api in a different manner like mine. Cyanogenmod source doesn't have it's api calls as per these certain devices needed. As most of the custom ROMs are based on CM, so none of them could make camera working. It's basically a firmware issue which is still unresolved.
So we can't use any roms :c
JulianoJr said:
So we can't use any roms :c
Click to expand...
Click to collapse
lolz.....no bro, we can't. If u really want to use custom ROM, then install Pixelmaster camera and use with this settings:
Go to settings>Resolution to 8MP>focus to infinity>turn on flash>Optimization ON>Anti-shake Auto>Image quality FINE.
This setting will at least capture images but the screen will be black. After taking the first image, u will see the camera screen but with very low light/brightness. It won't help much though. Honestly, I have tried all the custom ROMs over the net.If u want, u can. Good luck.
To Root your Mi A2 you will have to first unlock its bootloader, follow all steps correctly to gain root access on your Mi A2 device,
NOTE : All data will be wiped during bootloader unlocking, so make sure to backup each and every thing on your device.
first of all enable developer option & then enable OEM unlocking & USB debugging,
Now setup adb and fastboot drivers on your laptop/PC,
Now connect your Mi A2 (on state) and allow USB debugging popup.
now boot into fastboot mode (power off and press & hold volume down + power key simultaneously)
now connect your mi a2 to your laptop/pc,
now run fastboot oem unlock it will unlock the bootloader and reboot your device, also will wipe data,
now again setup the device and enable developer option, enable OEM unlocking, enable USB debugging, and connect to allow usb debugging.
now once again boot into fastboot mode (as described above), and connect your mi a2 to your laptop/pc
now download august months (V9.6.10.0.ODIMIFE, August 5 2018.) patched_boot.img (dont use if you are on any other month patch) use that months patched_boot.img file only.
now put the patched_boot.img to adb folder.
now again open the command or powershell window, and run fastboot boot patched_boot.img
it will boot your device, now just download the Magisk manager apk and install it.
open magisk manager and click on install, then direct install (recommended),
it will now download the magisk zip file and flash it at its own, after its done simply reboot your Mi A2 and voila we have successfully rooted our Mi A2.
let me know if you have any issues following this tutorial.
This should be in the guides section as this is nothing development related
Benjamin_L said:
This should be in the guides section as this is nothing development related
Click to expand...
Click to collapse
thanks, but how can i delete this post?
androwide said:
thanks, but how can i delete this post?
Click to expand...
Click to collapse
Report it and let the mods do it
Will this void my warranty? If yes, then does "unrooting" bring back my warranty?
pratyush2173 said:
Will this void my warranty? If yes, then does "unrooting" bring back my warranty?
Click to expand...
Click to collapse
If rooting voids your warranty depends a lot where you live. It's just a disclaimer from the devs that they can't be held responsible for any damage.
Benjamin_L said:
If rooting voids your warranty depends a lot where you live. It's just a disclaimer from the devs that they can't be held responsible for any damage.
Click to expand...
Click to collapse
Depends on Xiaomi to be honest, I searched and found conflicting opinions about xiaomi being okay with rooting and still provide warranty on the device (hardware, that is). Technically, they shouldn't as rooting allows you do to things that can easily shorten your device's life. But I just wanted to use substratum on my new Mi A2 without losing the warranty on a brand new phone as it might have defects which I haven't noticed yet. (And as I've heard andromeda is **** so won't pay for that.)
pratyush2173 said:
Depends on Xiaomi to be honest, I searched and found conflicting opinions about xiaomi being okay with rooting and still provide warranty on the device (hardware, that is). Technically, they shouldn't as rooting allows you do to things that can easily shorten your device's life. But I just wanted to use substratum on my new Mi A2 without losing the warranty on a brand new phone as it might have defects which I haven't noticed yet. (And as I've heard andromeda is **** so won't pay for that.)
Click to expand...
Click to collapse
Xiaomi does not stand above european law so not really. But as I said, depends where you live of course. A modified boot image should do no harm still.
Thanks for this guide, will I be able to update my phone after I use the patched_boot.img?
estetico said:
Thanks for this guide, will I be able to update my phone after I use the patched_boot.img?
Click to expand...
Click to collapse
It will overwrite the patched boot image so you'll have to update the patched boot image for each update
Benjamin_L said:
It will overwrite the patched boot image so you'll have to update the patched boot image for each update
Click to expand...
Click to collapse
are you sure? If the OTA has check for modified system partition it will fail.
munchy_cool said:
are you sure? If the OTA has check for modified system partition it will fail.
Click to expand...
Click to collapse
I didn't have a chance to try it yet so I can't be sure. Will test when the September update drops
Benjamin_L said:
It will overwrite the patched boot image so you'll have to update the patched boot image for each update
Click to expand...
Click to collapse
And just in case, if I update phone with root will there be any soft damage like boot loop or device getting bricked? Or will it just overwrite and become like it was before?
veeru1saini1 said:
And just in case, if I update phone with root will there be any soft damage like boot loop or device getting bricked? Or will it just overwrite and become like it was before?
Click to expand...
Click to collapse
Most likely the last yes.
I have a problem with my A2. I followed your rooting instructions and everything went well and I got a root. But then I wanted to install TWRP and I followed those instructions:
fastboot flash boot_b TWRP-3.2.3-jasmine-20180804.img
fastboot set_active b
fastboot reboot (with holding volume up)
It went to TWRP
I changed the partition to A and rebooted system
Now I can't boot OS anymore. It's loading all the time and nothing happens.
What can I do now? Please help, I am not the advanced Android user.
I still can go into Fastboot and TWRP, but I'm not sure what to do and I don't want to do something wrong more.
Yaroray said:
I have a problem with my A2. I followed your rooting instructions and everything went well and I got a root. But then I wanted to install TWRP and I followed those instructions:
fastboot flash boot_b TWRP-3.2.3-jasmine-20180804.img
fastboot set_active b
fastboot reboot (with holding volume up)
It went to TWRP
I changed the partition to A and rebooted system
Now I can't boot OS anymore. It's loading all the time and nothing happens.
What can I do now? Please help, I am not the advanced Android user.
I still can go into Fastboot and TWRP, but I'm not sure what to do and I don't want to do something wrong more.
Click to expand...
Click to collapse
Are you sure you change to a? go fastboot and fastboot set_active a and fastboot reboot
T4Ump said:
Are you sure you change to a? go fastboot and fastboot set_active a and fastboot reboot
Click to expand...
Click to collapse
Yes, I'm sure I changed partition to A, but I finally managed to fix it. I powered off phone from TWRP and then booted it again (after an hour ) and it worked.
Now I have one more question. When I boot from Fastboot with patched_boot.img, root is gained. But when I restart my phone normally the root is gone. Is it normal and how to get constant root?
Yaroray said:
Yes, I'm sure I changed partition to A, but I finally managed to fix it. I powered off phone from TWRP and then booted it again (after an hour ) and it worked.
Now I have one more question. When I boot from Fastboot with patched_boot.img, root is gained. But when I restart my phone normally the root is gone. Is it normal and how to get constant root?
Click to expand...
Click to collapse
You dont need TWRP, because A2 has ****ing A/B and TWRP is not supported, because bootlooping after install twrp. Dowloand ROM from Xioami webpage and unpack original boot.img, flash to b and a (original boot)
try if mobile normal boot to system. Go fastboot and patched_boot.img flash to b / a.
T4Ump said:
You dont need TWRP, because A2 has ****ing A/B and TWRP is not supported, because bootlooping after install twrp. Dowloand ROM from Xioami webpage and unpack original boot.img, flash to b and a (original boot)
try if mobile normal boot to system. Go fastboot and patched_boot.img flash to b / a.
Click to expand...
Click to collapse
Twrp just does not work properly currently. It will be supported in the near future
Benjamin_L said:
Twrp just does not work properly currently. It will be supported in the near future
Click to expand...
Click to collapse
Yea, i know. I tried first day when i got mobil, twrp root etc.
Hard to find much on or about these $64.00 tablets from Walmart, so I thought I would throw this out there. The bootloader is unlockable and it has project treble support. Support is A-only, no seamless updates. Magisk installed just fine and then Riru-Core and EdXposed. I don't know where one would get stock boot.img so I tackled mine by using mtk-su by @diplomatic. Once I got a root shell I used dd to dump boot.img with "dd if=/dev/block/by-name/boot of=/sdcard/boot.img". It looks weird but platform and soc weren't needed. Install Magisk Manager and let it patch stock boot.img. Transfer magisk_patched.img to PC. Tablet connected to PC use "adb reboot bootloader" once in fastboot mode use "fastboot flashing unlock" and follow on-screen prompts to unlock bootloader. Set tablet up again in developer options for adb as unlocking performs factory reset. Reinstall Magisk Manager then use "adb reboot bootloader" again and finally the money shot "fastboot flash boot magisk_patched.img". I'm not sure if it was helpful or needed but I then used "fastboot oem reboot-recovery" and wiped cache partition from stock recovery. After cache wipe completes, reboot system and go to Magisk Manager and check installation and updates then tend to whatever you think necessary. In the Magisk downloads section is Riru-Core and EdXposed which install same as any other module. From there I can confirm Gravitybox works, so far I've enabled the advanced power menu,navbar tweaks changed button color and button glow color and duration, also forced overflow menu. Bloat is very minimal on these with I believe 5 Sam Walton based apps which put up no resistance to pm hide command and later removal. I removed them (and then some) after making a backup with Advanced Tools Pro. Still in the process of finding out what should or shouldn't be removed. I stumbled upon a simply named but quietly complex root app by the name of Disable Application (ROOT) that is worth checking out. And of course fastboot and adb commands above are without the quotation marks. If you pick up any of my bad habits from reading the above, which in turn have any ill effects on your device, I am in no way responsible. In other words, wuzzn't me.
edit: I had this tucked away and easy to miss so here it is.
magisk_patched.img, mt8163_scatter and a few more things
IMG Files pulled from device using dd
I have added a full backup taken with TFM Tool that can be flashed with TFM or individually with fastboot
(Folder emptied by google)
There is an SP Flash Tool backup and tools on @CaffeinePizza 's server here: https://www.nathanbar.net/files/android/
There is also a flashing guide that works very well in post #192 by @CaffeinePizza
Wait, so the bootloader is unlockable via fastboot? My intel indicated otherwise (probably due to wrong commands being tried). @NFSP G35, @DB126, @pbeamtn will want to hear about this. Thanks. That means there isn't much need for an unlock tool that runs from Android root.
Wow... I totally entered the wrong commands in fastboot /facepalm
This is really good to know though. @diplomatic was able to help me unlock the bootloader on my 10" Onn tablet via 'other' means... but it's awesome that's not required and thus available to a large audience!
I'll give this a shot on both variants of the 10" (the one with the keyboard actually has slightly different hardware/software)
Also, thanks for drawing my attention here with the mention @diplomatic
I have been trying to build TWRP for this thing, but haven't been successful just yet.
If anyone cares to lend some guidance, I wouldn't turn it down
tek3195 said:
Hard to find much on or about these $64.00 tablets from Walmart, so I thought I would throw this out there. The bootloader is unlockable and it has project treble support. Support is A-only, no seamless updates....
...Tablet connected to PC use "adb reboot bootloader" once in fastboot mode use "fastboot flashing unlock" and follow on-screen prompts to unlock bootloader.
Click to expand...
Click to collapse
Confirmed working (not there was any doubt). Thanks for you excellent post.
---------- Post added at 11:41 PM ---------- Previous post was at 11:36 PM ----------
diplomatic said:
Wait, so the bootloader is unlockable via fastboot? My intel indicated otherwise (probably due to wrong commands being tried). @NFSP G35, @DB126, @pbeamtn will want to hear about this. Thanks. That means there isn't much need for an unlock tool that runs from Android root.
Click to expand...
Click to collapse
Not necessarily. Your tool has two distinct advantages:
- ability to easily lock and unlock
- preserves contents of data partition
In the absence of TWRP I would be loath to unlock via the stock method unless working with a virgin device. Yes, there are ways to backup/restore contents ofthe data partition outside of a dedicated recovery but I don't have the time or ambition to mess with such clumsy approaches. Your non-destructive unlockbl.sh script makes it easy.
DB126 said:
In the absence of TWRP...
Click to expand...
Click to collapse
Well... I got TWRP to boot... but the screen is portrait and the touch input is landscape :silly:
NFSP G35 said:
Well... I got TWRP to boot... but the screen is portrait and the touch input is landscape :silly:
Click to expand...
Click to collapse
Can I get a copy of your TWRP ?
Nevermind, just realized you said both 10" and not 8".
tek3195 said:
Can I get a copy of your TWRP ?
Nevermind, just realized you said both 10" and not 8".
Click to expand...
Click to collapse
Yeah, I was going to mention that.
But here's the guide I used... If it worked on the 10, it should work on the 8...
https://forum.xda-developers.com/android/general/guide-porting-twrp-source-t3843473
You'll just need to use mtk-su to pull your stock recovery image (***Make sure you save it!!!)
I also only got it to boot by using dd from mtk-su, for some reason the fastboot flash would take, but wouldn't boot... Furthermore, the tablet won't boot at all with a bad recovery (it will just boot loop) and can kill the battery. I nearly bricked one of mine. So do be careful.
The stock recovery image will flash via fastboot though, just have to make sure to erase first, and make sure you have a decent charge on the battery, otherwise fastboot won't let you flash.
diplomatic said:
Wait, so the bootloader is unlockable via fastboot? My intel indicated otherwise (probably due to wrong commands being tried). @NFSP G35, @DB126, @pbeamtn will want to hear about this. Thanks. That means there isn't much need for an unlock tool that runs from Android root.
Click to expand...
Click to collapse
What is this tool? @diplomatic I need some help with a different device. Huawei MediaPad T3_7. Can't find anyone with support for it to unlock the bootloader via online service. Sigma Key has full support but way to expensive for a hobbiest like myself. It has MTK MT8127 on Android 6.0 and I haven't been able to find a temp root solution or any other support for it. This is the 7th one of these I've owned but 1st one since no official unlock. I still have working TWRP and custom rom I cooked in Superr's Kitchen but no way to use them. Any thoughts on unlocking?
NFSP G35 said:
Yeah, I was going to mention that.
But here's the guide I used... If it worked on the 10, it should work on the 8...
https://forum.xda-developers.com/android/general/guide-porting-twrp-source-t3843473
You'll just need to use mtk-su to pull your stock recovery image (***Make sure you save it!!!).
Click to expand...
Click to collapse
Thanks for link,haven't seen that one before.
Is there any particular reason to use mtk-su ? I have Magisk fully operational already. Or do I need to un-root before pulling recovery.img ? Shouldn't matter should it?
Oh yeah, I forgot you had Magisk... Shouldn't need mtk-su then if you do from a terminal emulator.
I like using mtk-su so I can do everything from the computer via ADB shell
NFSP G35 said:
Well... I got TWRP to boot... but the screen is portrait and the touch input is landscape :silly:
Click to expand...
Click to collapse
I really recommend compiling it from source code if you want to have any hope of it working correctly. To rotate the touch input you can try this in your BoardConfig.mk:
Code:
RECOVERY_TOUCHSCREEN_SWAP_XY := true
RECOVERY_TOUCHSCREEN_FLIP_X := true
...or some combination of those 2.
tek3195 said:
What is this tool? @diplomatic I need some help with a different device. Huawei MediaPad T3_7. Can't find anyone with support for it to unlock the bootloader via online service. Sigma Key has full support but way to expensive for a hobbiest like myself. It has MTK MT8127 on Android 6.0 and I haven't been able to find a temp root solution or any other support for it. This is the 7th one of these I've owned but 1st one since no official unlock. I still have working TWRP and custom rom I cooked in Superr's Kitchen but no way to use them. Any thoughts on unlocking?
Click to expand...
Click to collapse
Well, you need to get root first to unlock it from Android. And I'm not sure it'll work on the mt8127....
tek3195 said:
Thanks for link,haven't seen that one before.
Is there any particular reason to use mtk-su ?
Click to expand...
Click to collapse
Although not directly related I opt for mtk-su for simplicity and portability. No prep required other than changing permissions on the executable.
diplomatic said:
I really recommend compiling it from source code if you want to have any hope of it working correctly. To rotate the touch input you can try this in your BoardConfig.mk:
Code:
RECOVERY_TOUCHSCREEN_SWAP_XY := true
RECOVERY_TOUCHSCREEN_FLIP_X := true
...or some combination of those 2.
Click to expand...
Click to collapse
Yeah, I saw that in several guides. I fought with compiling from source several times and just can't seem to get it even close to working. It took several tries just to get the build to finish and even then it just boot looped.
Doing a repack was the only thing I could get to boot.
I'd prefer to build from source, but it's kinda overwhelming.
NFSP G35 said:
Oh yeah, I forgot you had Magisk... Shouldn't need mtk-su then if you do from a terminal emulator.
I like using mtk-su so I can do everything from the computer via ADB shell
Click to expand...
Click to collapse
Ok cool, just making sure. Not trying to avoid or discount mtk-su, I think it's freakin awesome. But, you can also use adb shell from pc with Magisk. When you get shell and enter su you just have to grant permission for shell when prompted on device.
This is great!
Has anyone searched for a way to hide the walmart nav bar button?
blueberry.sky said:
This is great!
Has anyone searched for a way to hide the stupid walmart nav bar button?
Click to expand...
Click to collapse
Just use the Custom Navigation Bar app or adb commands to customize the Navbar.
You don't even need root.
^ can confirm. Actually, I saw the post in my email and was coming here to answer, but creeve4 beat me to it lol
Wait, if it has Treble support, is it possible to flash an Android Q GSI whenever it comes out?
Pix12 said:
Wait, if it has Treble support, is it possible to flash an Android Q GSI whenever it comes out?
Click to expand...
Click to collapse
Should be possible. Android Q Beta 4 GSI is out if anyone wants to try now.
xda-developers.com/install-android-q-beta-gsi-project-treble
NFSP G35 said:
Yeah, I was going to mention that.
But here's the guide I used... If it worked on the 10, it should work on the 8...
https://forum.xda-developers.com/android/general/guide-porting-twrp-source-t3843473
You'll just need to use mtk-su to pull your stock recovery image (***Make sure you save it!!!)
I also only got it to boot by using dd from mtk-su, for some reason the fastboot flash would take, but wouldn't boot... Furthermore, the tablet won't boot at all with a bad recovery (it will just boot loop) and can kill the battery. I nearly bricked one of mine. So do be careful.
The stock recovery image will flash via fastboot though, just have to make sure to erase first, and make sure you have a decent charge on the battery, otherwise fastboot won't let you flash.
Click to expand...
Click to collapse
tek3195 said:
Hard to find much on or about these $64.00 tablets from Walmart, so I thought I would throw this out there. The bootloader is unlockable and it has project treble support. Support is A-only, no seamless updates. Magisk installed just fine and then Riru-Core and EdXposed. I don't know where one would get stock boot.img so I tackled mine by using mtk-su by @diplomatic. Once I got a root shell I used dd to dump boot.img with "dd if=/dev/block/by-name/boot of=/sdcard/boot.img". It looks weird but platform and soc weren't needed. Install Magisk Manager and let it patch stock boot.img. Transfer magisk_patched.img to PC. Tablet connected to PC use "adb reboot bootloader" once in fastboot mode use "fastboot flashing unlock" and follow on-screen prompts to unlock bootloader. Set tablet up again in developer options for adb as unlocking performs factory reset. Reinstall Magisk Manager then use "adb reboot bootloader" again and finally the money shot "fastboot flash boot magisk_patched.img". I'm not sure if it was helpful or needed but I then used "fastboot oem reboot-recovery" and wiped cache partition from stock recovery. After cache wipe completes, reboot system and go to Magisk Manager and check installation and updates then tend to whatever you think necessary. In the Magisk downloads section is Riru-Core and EdXposed which install same as any other module. From there I can confirm Gravitybox works, so far I've enabled the advanced power menu,navbar tweaks changed button color and button glow color and duration, also forced overflow menu. Bloat is very minimal on these with I believe 5 Sam Walton based apps which put up no resistance to pm hide command and later removal. I removed them (and then some) after making a backup with Advanced Tools Pro. Still in the process of finding out what should or shouldn't be removed. I stumbled upon a simply named but quietly complex root app by the name of Disable Application (ROOT) that is worth checking out. And of course fastboot and adb commands above are without the quotation marks. If you pick up any of my bad habits from reading the above, which in turn have any ill effects on your device, I am in no way responsible. In other words, wuzzn't me.
Click to expand...
Click to collapse
How do you get to fastboot mode? When I tried it with the one in the store I managed to get it to the menu where you can choose recovery, bootloader/fastboot, or normal boot but it just froze after choosing fastboot. Which I thought meant that they removed fastboot entirely like some other tablets do.
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.