Related
After I got my new nexus, I decided to root it. I used mskips toolkit with 4.1 and it worked like a beaut. But I can't for the life of me root 4.1.2.
Checklist:
Downloaded the drivers succesfully
Can enter ADB succesfully. Under device manager it says "Google Nexus 7 ADB interface"
Tried WugFresh's toolkit
Unlocked bootloader
Tried installing custom recovery (see below)
(Checklist to know what I have done, for people to help me and future people with problems)
The reason adding CWM or TWRP doesn't work is because the device can't be rooted. You need to be rooted to change recovery file names, and whenever I boot recovery, I get the dead android and a red ! (stock recovery).
When it sees if busybox is installed, and sends the command, it comes back negative.
I'm having the exact same problem -- generating the same set of error messages as you show at the top of your screen capture. I bought a new Nexus 7 32GB and updated it to 4.1.2 before trying to root it. At the time I hadn't read anything that told me this might be a bad idea. I figured -- update to the latest version then root it. I've tried changing how I have it connected (media or camera), what USB port I connect to, what USB cable I use, which boot options I select -- NOTHING makes a difference. I have gotten my bootloader to unlock, or so it seems, as I've got the unlocked padlock image during boot up. But I'm totally stuck on how to proceed to get root.
lesdense said:
I'm having the exact same problem -- generating the same set of error messages as you show at the top of your screen capture. I bought a new Nexus 7 32GB and updated it to 4.1.2 before trying to root it. At the time I hadn't read anything that told me this might be a bad idea. I figured -- update to the latest version then root it. I've tried changing how I have it connected (media or camera), what USB port I connect to, what USB cable I use, which boot options I select -- NOTHING makes a difference. I have gotten my bootloader to unlock, or so it seems, as I've got the unlocked padlock image during boot up. But I'm totally stuck on how to proceed to get root.
Click to expand...
Click to collapse
When you run wugs toolkit to root, does it reboot your nexus? I have not rooted a 32GB yet but I have done a 16GB on 4.1.2 factory image without any problems.
There is nothing different between rooting an 8/16GB unit versus the 32GB ones. Nor does 4.1.1 or 4.1.2 matter.
I bought a 32GB one a few days ago, upgraded to 4.1.2, and had the bootloader unlocked, custom recovery installed and device rooted in about 5 minutes.
The issues you are having are why I hate these "toolkits". They don't always work properly, and when they fail, the user has no idea what's going on. It's much better for people to actually perform the steps manually so that they understand what's going on behind the scenes. Because when you understand, you can better troubleshoot problems.
Based on the errors, it looks like the toolkit failed to remount /system as writable. As such, it couldn't push the APKs for superuser, nor make the su binary suid root. Which of course would break the rest of the install script.
It's a very simply process and doesn't need a toolkit. Use the android development toolkit tools adb and fastboot.
1) adb reboot bootloader
2) fastboot oem unlock
(select yes on tablet)
3) fastboot reboot-bootloader
(confirm bootloader is unlocked)
4) fastboot erase recovery
5) fastboot flash recovery <recovery.img>
(recovery.img should be a downloaded custom recovery file - CWM or TWRP, your choice).
6) Reboot into recovery
7) adb push <superuser.zip> /sdcard/superuser.zip
(superuser.zip should be whatever recovery flashable 'root' zip you want to use).
8) Using recovery, flash the zip file.
9) Reboot
10) Done.
phonic said:
There is nothing different between rooting an 8/16GB unit versus the 32GB ones. Nor does 4.1.1 or 4.1.2 matter.
I bought a 32GB one a few days ago, upgraded to 4.1.2, and had the bootloader unlocked, custom recovery installed and device rooted in about 5 minutes.
The issues you are having are why I hate these "toolkits". They don't always work properly, and when they fail, the user has no idea what's going on. It's much better for people to actually perform the steps manually so that they understand what's going on behind the scenes. Because when you understand, you can better troubleshoot problems.
Based on the errors, it looks like the toolkit failed to remount /system as writable. As such, it couldn't push the APKs for superuser, nor make the su binary suid root. Which of course would break the rest of the install script.
It's a very simply process and doesn't need a toolkit. Use the android development toolkit tools adb and fastboot.
1) adb reboot bootloader
2) fastboot oem unlock
(select yes on tablet)
3) fastboot reboot-bootloader
(confirm bootloader is unlocked)
4) fastboot erase recovery
5) fastboot flash recovery <recovery.img>
(recovery.img should be a downloaded custom recovery file - CWM or TWRP, your choice).
6) Reboot into recovery
7) adb push <superuser.zip> /sdcard/superuser.zip
(superuser.zip should be whatever recovery flashable 'root' zip you want to use).
8) Using recovery, flash the zip file.
9) Reboot
10) Done.
Click to expand...
Click to collapse
I agree with you, the problem of the tool kits, I experimented two of then
M, is that you are lost when something don't work, I lost hours and hours before understand it and do it by myself for 50 per cent .
Now that everything is good, I am very prudent with theses helpers,:good:
I was poking around in the nexus 7's bootloader menus (the one with reboot, start, shutdown) and found a option to flash over ADB. Thus could it be possible to Flash ROMS over ADB without rooting?
Your device doesn't need to be rooted to flash a rom but the bootlader must be unlocked to boot or flash custom recovery in order to flash a custom rom.
x10knight said:
I was poking around in the nexus 7's bootloader menus (the one with reboot, start, shutdown) and found a option to flash over ADB. Thus could it be possible to Flash ROMS over ADB without rooting?
Click to expand...
Click to collapse
Stock recoveries generally validate the .zip payload via cryptographic signatures - so while you can shove any zip file you want across that adb sideload connection, it will refuse to process any that are not properly signed. That feature is in the stock recovery only to support manual application of factory-signed OTA bundles.
[INFO] How to sideload 5.1.1 (LYZ28E), & maintain no encryption - no wipe required
Simplified procedures with LMY47M / LYZ28E now available as a factory image.
Hopefully this isn't blatantly obvious to everyone, it is a little different than the normal sideload procedure. Thought it might be useful to some who want to load 5.1.1 (and get Wifi calling with T-Mobile!) and not be forced to encrypt.
Requirements:
1. I'm assuming you have adb/fastboot working on your computer / connecting to your device and you understand a little bit about using adb / fastboot with an android phone.
2. Your phone cannot be encrypted, if you're encrypted already - this will not un-encrypt your data - you need to turn off forced encryption and format the "userdata" partition to disable the encryption.
3. You need to have an unlocked bootloader for this to work of course.
How to follow this procedure:
1. If you're on LMY47M (T-Mobile) and unencrypted, you can follow option 2, starting with Step 3 - only a small ~150MB download required.
2. If you're on anything other than LMY47M, you should use option 1 unless you have a desire to flash LMY47M and sideload LYZ28E.
I didn't do much here - except spent a bunch of time writing the procedure.
All Credit for tools / ideas goes to:
- efrant for his explanation of how to get OTA updates to work with TWRP ( http://forum.xda-developers.com/nexus-6/general/nexus-6-ota-help-desk-t2992919/page4 )
- hlxanthus for the NO FORCE ENCRYPT mod ( http://forum.xda-developers.com/nexus-6/development/mod-disable-force-encryption-rom-kernel-t3000788 )
- Q9Nap and mhous33 for the LMY47M factory image ( http://forum.xda-developers.com/nexus-6/development/fxz-nexus-6-recovery-flashable-fastboot-t3066052 )
- bbedward and others for the original disable forced encryption boot.img ( http://forum.xda-developers.com/nexus-6/development/disable-forced-encryption-gain-root-t2946715 )
- TeamWin - the TWRP Developer ( https://twrp.me/ )
——————————————————————————————————
OPTION 1 - Easy Method - Flash the LYZ28E factory image directly:
1. Download hlxanthus's NO FORCE ENCRYPT mod and put it onto your phone so you can flash it later (in /storage/sdcard0) - https://basketbuild.com/filedl/devs...u/misc/NO_FORCE_ENCRYPT_shamu_v1.0-signed.zip
2. Download LYZ28E for Nexus 6 ( https://dl.google.com/dl/android/aosp/shamu-lyz28e-factory-b542b88a.tgz ) and extract the files, there is a zip file you want to extract that too.
Boot to the bootloader ("adb reboot bootloader") and fastboot flash the boot, cache, recovery, radio and system:
Code:
fastboot flash boot boot.img
fastboot flash cache cache.img
fastboot flash recovery recovery.img (OPTIONAL - If you have TWRP or another alternative recovery you can skip this step)
fastboot flash radio radio-shamu-<variable>.img
fastboot flash system system.img
3. Restart the Bootloader, and flash TWRP, found here: ( https://twrp.me/devices/motorolanexus6.html )
Code:
fastboot flash recovery twrp-2.8.6.0-shamu.img
4. Restart the Bootloader again and then go to Recovery (TWRP). Now flash NO_FORCE_ENCRYPT_shamu_v1.0-signed.zip through TWRP, and flash SuperSU if you want root and whatever other zips you want to flash (Xposed, etc)
After flashing the NO FORCE ENCRYPT mod, reboot and you should be running 5.1.1 with all of your data and with your userdata partition intact and unencrypted!
———————————————————————————————————————————————————
OPTION 2 - SIDELOAD Method (Makes sense if you’re already on LMY47M):
1. Download hlxanthus's NO FORCE ENCRYPT mod and put it onto your phone so you can flash it later (in /storage/sdcard0) - https://basketbuild.com/filedl/devs...u/misc/NO_FORCE_ENCRYPT_shamu_v1.0-signed.zip
2. Follow the normal procedure, if you're already on LMY47M you can skip to step 3. Download LMY47M for Nexus 6 ( https://dl.google.com/dl/android/aosp/shamu-lmy47m-factory-5228e84a.tgz ) and extract the files, there is a zip file you want to extract that too.
Boot to the bootloader ("adb reboot bootloader") and fastboot flash the boot, cache, recovery, radio and system:
Code:
fastboot flash boot boot.img
fastboot flash cache cache.img
fastboot flash recovery recovery.img
fastboot flash radio radio-shamu-<variable>.img
fastboot flash system system.img
3. Now flash TWRP, found here: ( https://twrp.me/devices/motorolanexus6.html )
Code:
fastboot flash recovery twrp-2.8.6.0-shamu.img
4. Restart the bootloader, and enter recovery mode (TWRP). Once in TWRP, go to Advanced -> ADB Sideload. You may need to unplug/plug in the USB cable to your computer again.
Download my version of LYZ28E from here: https://www.androidfilehost.com/?fid=23991606952609905
Note: I modified this version to work with TWRP, it will not work with the stock recovery (because I modified it, the signature on the file is now invalid). The only thing I changed was I edited the updater-script to remove the release keys check which seems to fail on the stock recovery and doesn't work right with TWRP).
Code:
adb sideload f69096766706fab3c721163f02aad9073a989d00.unsigned-shamu-LYZ28E-from-LMY47M-fullradio-fix-superblock-use-TWRP.zip
5. After it finishes, do not reboot yet. Go back and I recommend rebooting to recovery again. Now flash NO_FORCE_ENCRYPT_shamu_v1.0-signed.zip through TWRP, and flash SuperSU if you want root and whatever other zips you want to flash (Xposed, etc)
After flashing the NO FORCE ENCRYPT mod, reboot and you should be running 5.1.1 with all of your data and with your userdata partition intact and unencrypted!
why would you think that you have to be encrypted to push anything to recovery??? plus sideload is only one method to do it, the other is adb push. and if you use twrp recovery, you don't need any of those method's, as you can just move files over to twrp via your usb.
simms22 said:
why would you think that you have to be encrypted to push anything to recovery??? plus sideload is only one method to do it, the other is adb push. and if you use twrp recovery, you don't need any of those method's, as you can just move files over to twrp via your usb.
Click to expand...
Click to collapse
Sorry if I gave the impression you need to be encrypted to push to recovery, that wasn't my intent. Where did I give that impression? I can try to fix it in my original post. At no point in this procedure will your phone be encrypted - there will be times that the kernel will have the force encryption option turned ON in the fstab but you never will boot the phone when that is the case (like right after LRX22C is loaded, after LYM47M is sideloaded, and after you flash the stock boot.img for LYM47M - but you are not booting in any of these cases - not before you install a no forced encryption kernel)
adb push requires the phone is booted right? I wasn't able to get adb push to work in recovery.
I also didn't know TWRP allowed you to copy data over to your phone via USB, I know CWM recovery can do it - but that was a feature missing from TWRP - maybe they added it, I didn't check. You can do an adb push with TWRP, but what in my procedure would you change to use the adb push method in TWRP versus whatever I put in there? The only thing I can think of is asking you to put the mod file on the phone in the beginning.
liqice said:
Sorry if I gave the impression you need to be encrypted to push to recovery, that wasn't my intent. Where did I give that impression? I can try to fix it in my original post. At no point in this procedure will your phone be encrypted - there will be times that the kernel will have the force encryption option turned ON in the fstab but you never will boot the phone when that is the case (like right after LRX22C is loaded, after LYM47M is sideloaded, and after you flash the stock boot.img for LYM47M - but you are not booting in any of these cases - not before you install a no forced encryption kernel)
adb push requires the phone is booted right? I wasn't able to get adb push to work in recovery.
I also didn't know TWRP allowed you to copy data over to your phone via USB, I know CWM recovery can do it - but that was a feature missing from TWRP - maybe they added it, I didn't check. You can do an adb push with TWRP, but what in my procedure would you change to use the adb push method in TWRP versus whatever I put in there? The only thing I can think of is asking you to put the mod file on the phone in the beginning.
Click to expand...
Click to collapse
"So I just figured out how to sideload LYZ28E on my Nexus 6 without enabling forced encryption. "
actually adb push is very easy.. boot unto recovery, type adb push filename.zip, then it pushes to your phone and is listed in the main storage filesystem. id say its nearly identical to adb sideload.
simms22 said:
"So I just figured out how to sideload LYZ28E on my Nexus 6 without enabling forced encryption. "
actually adb push is very easy.. boot unto recovery, type adb push filename.zip, then it pushes to your phone and is listed in the main storage filesystem. id say its nearly identical to adb sideload.
Click to expand...
Click to collapse
Sorry maybe that first sentence is poorly worded. What I meant was, I figured out how to get LYZ28E onto my phone and disable the forced encryption on the OS too. The process wasn't as straightforward because the 2nd sideload wouldn't work correctly without booting into the OS first. After that, I couldn't get the LYZ28E image to sideload on stock recovery or TWRP without errors - but I was able to modify the LYZ28E OTA file so it would load with TWRP, and then I was able to load the no encrypt mod and supersu and get the phone working the way I wanted again.
Are you saying it would be easier if I push the zip file to the phone and install using TWRP as a zip file instead of trying to sideload it?
Step 3: "Hold down the Power and Volume Up button (may need to do it a few times) to get to the Recovery menu".
Actually, the correct key combination is: Hold power, then (while holding power button) press and release volume up.
Works first time, every time.
cam30era said:
Step 3: "Hold down the Power and Volume Up button (may need to do it a few times) to get to the Recovery menu".
Actually, the correct key combination is: Hold power, then (while holding power button) press and release volume up.
Works first time, every time.
Click to expand...
Click to collapse
Thanks, updated the original post.
liqice said:
Sorry maybe that first sentence is poorly worded. What I meant was, I figured out how to get LYZ28E onto my phone and disable the forced encryption on the OS too. The process wasn't as straightforward because the 2nd sideload wouldn't work correctly without booting into the OS first. After that, I couldn't get the LYZ28E image to sideload on stock recovery or TWRP without errors - but I was able to modify the LYZ28E OTA file so it would load with TWRP, and then I was able to load the no encrypt mod and supersu and get the phone working the way I wanted again.
Are you saying it would be easier if I push the zip file to the phone and install using TWRP as a zip file instead of trying to sideload it?
Click to expand...
Click to collapse
easier/harder isnt an option here, since any way takes seconds. im just saying there are several options for this, thats all
liqice said:
Code:
fastboot flash f69096766706fab3c721163f02aad9073a989d00.unsigned-shamu-LYZ28E-from-LMY47M-fullradio-fix-superblock-use-TWRP.zip
Click to expand...
Click to collapse
Shouldn't this step be
Code:
adb sideload f69096766706fab3c721163f02aad9073a989d00.unsigned-shamu-LYZ28E-from-LMY47M-fullradio-fix-superblock-use-TWRP.zip
instead of fastboot flash?
So if your starting out with 47E, your rooted and have TWRP ..... would you use adb sideload in TWRP or you issue the command from the PC?
Chahk said:
Shouldn't this step be
Code:
adb sideload f69096766706fab3c721163f02aad9073a989d00.unsigned-shamu-LYZ28E-from-LMY47M-fullradio-fix-superblock-use-TWRP.zip
instead of fastboot flash?
Click to expand...
Click to collapse
Oops, you're right. Thanks!
Gage_Hero said:
So if your starting out with 47E, your rooted and have TWRP ..... would you use adb sideload in TWRP or you issue the command from the PC?
Click to expand...
Click to collapse
This is where I was, LMY47E, rooted, unencrypted and with TWRP. I followed the entire procedure - went back to LRX22C using fastboot, then sideloaded LMY47M (T-Mobile version) - then flashed the no force encrypt boot.img - booted, after it finished booting, rebooted to the bootloader and so on ...
When you go to LRX22C you flash back to the stock recovery. So you need to boot into the stock recovery, pick "apply update from adb" and then run the adb sideload command from the PC.
Cheers for this.. just what I was looking for. I'm at work so I only scanned this quickly, but any major change in the directions from what you've posted going from an unencrypted LMY47D?
With the factory images being posted, I just did the following:
Flashed the factory images
While still in bootloader, flashed TWRP
Rebooted into TWRP
Pushed SuperSU and the No_Force_encrypt to the /sdcard/ partition
Installed via TWRP
Profit.
lamenting said:
Cheers for this.. just what I was looking for. I'm at work so I only scanned this quickly, but any major change in the directions from what you've posted going from an unencrypted LMY47D?
Click to expand...
Click to collapse
For LMY47D you need to get to LMY47M first, so you would follow the entire procedure, downgrade to LRX22C and then sideload LMY47M and so on.
Heavily updated the procedure since LMY47M and LYZ28E factory images are now available directly from Google.
Should be a lot easier and more straight forward now!
I just recently have this Nexus 6 and came from an LG G2. I went through the process of unlocking the phone and installing rooted LMY47D which meant 2 factory resets in a short period.
I'm now on 5.1 and would like to get rid of the memory leak which this build apparently has.
The title mentions "maintain no encryption".
I never found the time to find out about Lollipop. The title implies that encryption is mandatory on 5.1.1
Is this so?
I merely want the latest upgrade to 5.1.1 and don't want to enforce encryption on my data (Google already knows everything about me) is this the way to achieve this?
I am correct in thinking that I will not get an OTA offered anymore?
Boot loader and radio only...
So if I understand the instructions correctly, if you are still encrypted but rooted, from any Lollipop installation, fast boot flash the factory images... then flash TWRP ... root and done right? Then I have another question... the kernel I am running EX 1.07 along with Flar's app is running perfect for me.... any dangers in just flashing the boot loader and radio? I would like to wait on the system part until the kernel has been updated.....
Also, if I needed to do a restore, if I only flash the boot loader and radio have I pooched being able to go backwards to a nand backup?
FYI, step 3 in option one should read:
fastboot flash recovery twrp-2.8.6.0-shamu.img
vs
fastboot flash twrp-2.8.6.0-shamu.img
frater said:
I just recently have this Nexus 6 and came from an LG G2. I went through the process of unlocking the phone and installing rooted LMY47D which meant 2 factory resets in a short period.
I'm now on 5.1 and would like to get rid of the memory leak which this build apparently has.
The title mentions "maintain no encryption".
I never found the time to find out about Lollipop. The title implies that encryption is mandatory on 5.1.1
Is this so?
I merely want the latest upgrade to 5.1.1 and don't want to enforce encryption on my data (Google already knows everything about me) is this the way to achieve this?
I am correct in thinking that I will not get an OTA offered anymore?
Click to expand...
Click to collapse
Starting with Android Lollipop (5.0) and newer - at least on the Nexus 6 - encryption is turned on by default for the userdata partition.
You would - if you wanted to - backup all of the data on your userdata partition (e.g. Any pictures you've taken with the phone, etc - all of the data basically that shows up when you plug your phone into your computer).
Then you need to be running an OS that doesn't force encryption (for example if you follow my instructions) - this would also get you running 5.1.1.
After that you need to format your userdata - it wouldn't be encrypted at that point, and then copy your data back if you want to.
If you don't care about encryption, you can simply flash the factory 5.1.1 image following my instructions and skip the TWRP parts.
AS TITLE
Install all adb drivers properly on your PC.
If you're on Marshmallow, this might help you to unlock your bootloader https://www.asus.com/zentalk/in/thread-116376-1-1.html it's a simple APK you can install on your phone.
Connect your phone to PC and reach it with adb.
Go into fastboot mode (adb reboot bootloader) and type from your cmd "fastboot oem device-info" i think is still a must to check if it worked properly.
If you're sure it's unlocked now, then flash root .zip file with TWRP, I did not flash TWRP on my ze500kl, so I think on ze550kl you can try to boot TWRP rather than flashing it as well (fastboot boot TWRPname.img), try to boot TWRP, because if you flash it there are chances to brick your phone (for example if TWRP isn't right for it), but if you try to just boot it i don't think you can damage your rom.
If you flash a root .zip file, make sure you made a full nandroid backup with twrp first, or at least to have an uninstaller .zip for it as well.. I recommend you to make a stock nandroid backup anyway before any kind of modding (espacially FLASHING).
I personally use Magisk superuser (https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445).
I don't own a ze550kl, i own a ze500kl and this method perfectly works for me. As long as you can unlock your bootloader, i think you can flash the root without problems if you manage to boot into the proper TWRP version for ze550kl.
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.