Database Users

[Guide] Ultimate Nexus 4 Root Guide

Post One: Unlocking and Rooting
Post Two: Installing Roms / Kernels / Tweaks
Post Three: Panic Section / FAQ / Miscellaneous
Unlocking The Bootloader And Obtaining Root
*This part of the tutorial is geared towards Windows users. The MAC instructions are very similar, from what I understand. Install the package the same way. All ADB/Fastboot commands may need to start with "adb-mac" (no quotes) rather than "adb" (no quotes). Due to the vast amount of Linux distros available; instructions will vary for your device. Once ADB/Fastboot are set up all command will begin with "./adb" (no quotes) rather than "adb" (no quotes). Once ADB/Fastboot are set up; this guide is relevant to everyone.*
Time required:
20-40 minutes.
Setting up ADB for our device:
Download the AndroidSDK onto your computer.
Note: Google changes their mind every other week as to if this will be distributed as a .zip or an .exe. If you get an .zip file, simply extract the contents to your C:\ drive. For an .exe install it like you would any other program, but set the path directly to the C:\ drive when the installer asks.
Or...you can use this page to download the "ADB for Dummies AIO App."
This will automatically install ADB for you to your C:\ directory. It's very very simple this way.
If your platform-tools folder doesn't have a fastboot.exe, place this fastboot.exe file in your C:\android-sdk-windows\platform-tools (or possibly simply called tools, if you set up ADB ages ago) folder.
Now you have ADB installed! Congratulations.
Unlocking the Bootloader:
***NOTE***
This will perform a factory reset on your device. You will lose all applications. Even the data on your SD Card! I'd recommend making a Backup to your computer BEFORE performing this. There is a method for backing your data up, detailed HERE.
For the time being, there is a method available that will allow you to unlock your device (and root it) without losing your data.
For instructions, click HERE. Please note: this is a hack and isn't the "conventional" and "accepted" way of unlocking your bootloader on a nexus device. The wipe requirement is there for your safety, really, and I'm certain this will be patched in the upcoming releases.
Get the drivers:
Uninstall any previously attempted drivers if they don't work and move to the next.
Option One:
Navigate to the "Device Manager" (Control Panel > Device Manager) in Windows and Select the android device. Open the properties and select the "Install Driver" option. Pick the driver with "Install from disk." Ignore any warnings about the driver not being signed properly.
PDAnet's drivers may work if the above options don't. Simply install PDAnet (after uninstalling any previous attempted driver installations) to get the drivers.
While that is downloading, on your Nexus 4: turn USB debugging on.
To do so; you must first go to Settings>About>Build Number and click seven times.
The actual setting can then be found in Settings>Developer Options>USB Debugging
Once the drivers are installed, navigate to the C:\android-sdk-windows\platform-tools folder on your computer.
Hold shift and right click. Select "Open Command Window Here."
Plug your phone into the computer. Now in this command window type:
Code:
adb reboot bootloader
(Hit Enter)
Your phone should now boot into a screen with a green android with his chest exposed.
Type this:
Code:
fastboot oem unlock
(Hit Enter)
If your Command Prompt displays the message "waiting for device" your driver wasn't successfully installed.
Close the Command Prompt window and open Device manager while your phone is still plugged in. (Search for it using the search option).
Right Click the "Android" option and select Update Driver. Choose to "Browse My Computer" and "Let Me Pick From A List." Pick the Driver with the newest date and install it. Now retry the code above.
Your phone will ask if you want to unlock it. Select "Yes" by using the volume keys and use power to select it.
Now, navigate to "Recovery Mode" with the volume keys. Use power to select.
A screen with another Android will pop up. Press Volume Up and Power at the same time.
Select Factory Reset. This process may take a few minutes. Be patient and let it work.
Once finished, select "Reboot."
Your phone is now unlocked!
Obtaining Root Access and Custom Recovery:
Turn on USB Debugging.
To do so; you must first go to Settings>About>Build Number and click seven times.
The actual setting can then be found in Settings>Developer Options>USB Debugging
Download the following:
SuperSU (CWM .zip)
CWM (Pick the version for your device)
Place the recovery-clockwork-VERSIONNUMBER-mako.img file into your C:\android-sdk-windows\platform-tools folder.
Put the SuperSU.zip on your phone.
Open another Command Prompt if it isn't still open. (Navigate to C:\android-sdk-windows\platform-tools and shift + right click. Select "Open Command Window Here.")
With your phone plugged in type:
Code:
adb reboot bootloader
(Hit Enter)
And wait for your phone to boot into the android again.
Now type:
Code:
fastboot flash recovery IMAGENAME.img
(Change the file name to the correct file name and Hit Enter)
Once that is finished: select the "Recovery Mode" option again on your phone.
You should get a new recovery menu here. Select "install zip from sd card" and "choose zip from sd card."
Find the SuperSU.zip that you transferred earlier and select "Yes" to installing.
Navigate back to "Reboot" and reboot your phone.
You're now rooted!
However, ClockworkMod Recovery won't continue to load after this.
To fix this, find "Rom Manager" from the market. (The free version is fine.) Use the "Flash ClockworkMod Recovery" option.
If your recovery still doesn't stick around after a reboot, you have another couple options. Find a file explorer that allows root access, such as Root Explorer. Use this program to rename /system/etc/install-recovery.sh to /system/etc/install-recovery.bak. You'll need to mount the system as r/w to do this. Root Explorer provides a button at the top to do so.
Or, you can do this completely manually by firing up ADB again and running a few commands:
Code:
adb shell
(Hit Enter)
Code:
su
(Hit Enter)
Code:
mount -o remount,rw -t ext4 /dev/block/mmcblk0p1 /system
(Hit Enter)
Code:
mv /system/etc/install-recovery.sh /system/etc/install-recovery.bak
(Hit Enter)
Congratulations!
Your phone is now unlocked, rooted, and has a custom recovery!
Continue reading the next posts for info on getting custom roms, kernels, tweaks, and more!
***I take no responsibility for what happens to your phone due to following this guide! That being said, not only am I sure you'll be fine...but there are an endless amount of users who would be glad to help if you need it.***
Thanks:
Google, for making Android a reality.
VanillaTbone, for the ADB AIO app.
Efrant, for posting about a bootloader locking utility without USB.
ClockworkMod team, for being a part of making our phones as awesome as they are.
The assorted developers, who continue to push out amazing material for us to use.
The awesome community, for endlessly supporting both Android itself and its users.

Installing Custom Roms Kernels and Tweaks
All of the instructions below require your bootloader to be unlocked. Please follow the guide above and return here when you're done.
Backing Your Files Up:
Time required:
15-25 minutes.
Making a Nandroid
The first thing you're going to want to do is back up your phone's entire system. This is done by making a "nandroid."
To do this, boot into ClockworkMod Recovery. To accomplish this: Turn your phone off. Once it is completely off: hold both volume buttons and the power button until the Android with his chest exposed is displayed. Navigate to the "Recovery Mode" option and select "backup."
This will take some time. Be patient and let it finish. This process is important! You should always have a recent nandroid available on your device.
Backing Your Data Up
Install Titanium Backup from the market.
Open Titanium Backup. A Superuser request should pop up. Allow it. Note: if Titanium Backup then says it failed to obtain root access; press the menu button and select more>reload application.
Press menu>batch. Select "Backup all User Apps." Select all and "Run the Batch Operation."
Let the process complete. This may take quite some time: depending on how many applications you have installed.
You can now backup your Text Messages, Bookmarks, and WiFi addresses with Titanium Backup as well.
Press Menu>Backup Data To XML to do so.
Backing Your Contacts Up
Note: This process may or not be useful to you. The Google servers should automatically import any contacts you have stored back whenever you install a new rom. Also note that Facebook/Google+/etc contacts will need to be synced again through their respective applications.
Open the Contacts application.
Press the Menu button.
Select import/export.
Export to storage.
Installing A Rom (Or Kernel/Radios/Tweaks/Themes/etc.)
Time Required:
5-10 minutes.
Note:
Follow the guide above about backing your phone up before attempting!
This guide will also work for flashing kernels/radios/themes/tweaks/etc. Simply ignore the part about wiping data and wipe whatever the thread says you should. You only need to restore data after a rom install.
Find a Rom You'd Like To Try:
Nexus 4 Original Development
Nexus 4 Development
Download the rom you'd like to try on your device.
Most roms also require you to install "gapps" as well.
You can find the correct ones for the rom you're using in the rom thread.
Make sure the Rom and Gapps are on your SD card.
Now, open Google Wallet (if you have it installed) and press Options>Settings>Reset Google Wallet. This will prevent the "Secure Element" errors some users have experienced.
Boot into ClockworkMod Recovery by turning your device completely off. Hold volume up, volume down, and power until the green Android with the open chest is displayed. Navigate to "Recovery Mode" with the volume buttons and select using the power button.
Remember to have a recent nandroid before continuing!
Navigate to "wipe data/factory reset" and select it. Select "yes."
Wait for the process to complete. This may take some time. Be patient!
Once complete: Navigate to "Install Zip from SD card" and "Choose zip from SD card."
Find the rom's .zip and install it. Once that completes install any applicable gapps' .zip.
Select the "Reboot" option.
Congratulations! Your phone should now boot into the custom rom!
Follow the prompts to re-activate your phone.
Restoring Your Applications / Contacts / Nandroid
Time Required:
5-15 minutes.
Restoring Your Applicaions
Install Titanium Backup. Note: you may want the pro key. If you have it, you won't have to manually click "install" on each application. The process is completely automated. Open Titanium Backup (grant root access. If titanium says it failed to obtain root access, press menu>more>reload application). Press menu>batch>restore missing apps with data. Now, here you have a choice to make. Do you want a completely clean install? Select "app only" and run the batch operation (Deselect Google Wallet first. We don't want to risk restoring wallet in any way. Install it manually through the Play Store.). Do you want all of your application data (saved games/settings/etc)? Select "app+data" and run the batch operation (Deselect Google Wallet first. We don't want to risk restoring wallet in any way. Install it manually through the Play Store.). This MAY cause you problems or it may not. Personally, I often restore application data and seldom run into any trouble. If you do find that restoring data caused problems, follow the guide above to re-install your rom and restore without data. This process will take some time. Be patient (I'd suggest turning your screen off so the screen doesn't burn, but that's just me.) It will vibrate upon completion.
You can now restore your Text Messages, Bookmarks, and WiFi addresses if you backed them up by pressing Menu>Restore Data From XML.
Note:
Overclocking/CPU tweaking applications should never be restored with data. Simply deselect it from the list.
Facebook/Haxsync/Google+ may have problems restoring your contacts when installed through Titanium Backup. Simply uninstall and reinstall through the market (and be sure to log in and select to sync your contacts again).
Also, if you have NFC Task Launcher successfully launching Tasker tasks with your stickers: they may not immediately work.
Through my testing, it's as simple to fix as uninstalling NFC Task Launcher and Tasker. Restore Tasker first. Then restore NFC task launcher.
Restoring Your Contacts
If google fails to restore your contacts (not facebook/haxsync/google+/etc) you may import them manually if you backed them up.
Open the contacts application and press menu>import/export>import from storage.
Restoring A Nandroid
If your phone is acting funny or won't boot...restore a nandroid from a previous rom or working set-up.
You may also use a Nandroid to switch back to a previous rom if you decide you don't like the one you're on.
Do this by booting into ClockworkMod Recovery (hold volume up, volume down, and power while your phone is off and navigate to "Recovery Mode").
Simply select "restore" and find the most recent (or relevant) backup.
This process will take some time. Be patient and let it complete! Once done, select "Reboot."
Note:
Nandroids are stored in the "clockworkmod" folder on your SD card. They take up quite a bit of space. ALWAYS have at least one recent one on your SD card. However, since these are huge files: you may like to delete old ones to save space. You must delete backups by booting into CWM and navigating to Backup and Restore>Delete.
Important Notes About Restoration
I outline the method of using Titanium Backup above for a reason. Restoring system applications and data is the most common cause of problems on custom roms. For this reason, always ONLY restore "missing applications" from "user applications" that were backed up when restoring onto a new rom. Every time you restore system data or applications a narwhal sodomizes your favorite childhood cartoon. This is FACT.
Installing Alternate Custom Recoveries
If you find a custom recovery (such as the touch-recovery options) that came as a .img file:
Use these instructions to flash. Plug your phone into the computer. Open up ADB. Move the .img to the C:\android-sdk-windows\platform-tools folder.
Type the following:
Code:
adb reboot bootloader
(Hit Enter)
You can also manually boot to the bootloader by powering off and holding volume down, volume up, power buttons until the green Android with his chest exposed is displayed.
Then type:
Code:
fastboot flash recovery FILENAME.img
(Replace the file name with whatever the .img is called and Hit Enter).
Wait for the process to complete and reboot.
***I take no responsibility for what happens to your phone due to following this guide! That being said, not only am I sure you'll be fine...but there are an endless amount of users who would be glad to help if you need it.***

Panic Section! (Something is Wrong)
Q: My phone won't boot!
A: The easiest option is to get into recovery and restore a nandroid using the above guide (pull battery to put phone in an off-state if needed).
However, more advanced options are available if you don't have a nandroid available (You're naughty).
Do you have another rom .zip available on your SD card? If so, simply use the above guide for installing a rom to get you booting again.
If not, you can download one on your PC. Boot into fastboot (the green Android with open chest menu). Navigate to recovery and select it with the power button.
Move the .zip to the C:\android-sdk-windows\platform-tools folder.
Open ADB.
Change the NAMEOFZIP.zip below to the correct file name...and perform the action.
Code:
adb push NAMEOFZIP.zip /sdcard/NAMEOFZIP.zip
(Hit enter)
You may have to reboot recovery to get the file to show up. Now follow the guide above for flashing a rom to get you booting again.
Did you install a tweak that modified only a file or two on your phone? (Find this out by opening the .zip and looking in the folders (ignore META-INF). Good news! We MAY be able to recover you completely. If this doesn't work...you'll have to follow another method.
Get your phone into fastboot (the boot-menu that allows you to select recovery/reboot/etc). Navigate to Recovery. Start up ADB. Pull the files that were modified out of the stock rom's .zip (using whatever tweak you were installing as reference to find what was changed) that you're on into the C:\android-sdk-windows\platform-tools folder. Now we're going to push these files onto your phone...replacing the tweaked ones and hopefully getting you booted again. Use this code, but change the values of the file name and where it should reside. This is only an example!
Code:
adb shell
(Hit Enter)
Code:
su
(Hit Enter)
Code:
mount -o remount,rw -t ext4 /dev/block/mmcblk0p1 /system
(Hit Enter)
This will mount your system so you can write to it.
Code:
exit
(Hit Enter)
This should exit shell and allow the use of adb commands again. You may need to type it a couple of times (until the #_ changes back to the platform_tools> prompt).
Code:
adb push framework-res.apk /system/framework/framework-res.apk
(Press enter after each file that you need to replace).
Note: This last option probably won't work. I'd just skip over it unless you're absolutely adamant about restoring your current setup and want to try everything possible.
Q: I want my SDcard files from my phone...but I'm in a situation where I need to flash stock images! This will erase my SD content. What can I do to save it?
A: Do you have a custom recovery installed? If not, download a custom recovery from post one in this guide and flash it using those instructions. You'll need to be in a custom recovery in order to obtain ADB access without booting your phone. Boot into recovery (With phone turned off: hold Power and Volume+ and Volume- until the bootloader pops up and navigate to "Recovery"). Run the command:
Code:
adb pull /sdcard/ /SDCARD/
(Hit Enter)
This will put all of your files into a folder called "SDCARD" in your C:\ drive. Keep in mind that this will take a LONG time. Maybe a couple of hours.
To restore once you're booting again:
Move the "SDCARD" folder you created from your C:\ drive to the platform-tools folder. *Then input:
Code:
adb push SDCARD /sdcard/
(Hit Enter)
Q: How do I make an "ADB Backup?"
A: An ADB Backup will backup your phones data (applications and their settings). Follow the guide HERE about ADB Backups.
Q: My phone gets really sluggish and often turns off or reboots on its own.
A: Without knowing anything about your situation...I'd say you either have severely bad data somewhere or some bad kernel tweaks. Use the rom install guide above, paying close attention to the part about backing up and restoring if you haven't already. In the case of a kernel problem, you're likely undervolting too low. Restore the stock kernel values and see if your problems subside.
Q: My phone screen won't turn on! This requires a battery pull to fix.
A: This is called a "Black Screen of Death" or BSOD. This is generally due to using a hotplug governor (one that turns cores off with the screen off) or possibly undervolting your device too low. Change governors or up your slots a bit.
Q: My phone is doing really weird things. Regardless of kernel/rom and even if I don't restore any data at all! Either that or I simply cannot boot up! My phone is possessed no matter what I do!
Download the stock IMAGES for your device and extract the files using 7-zip. Move all of the extracted files to your platform-tools folder. Open the flash-all.sh file with a text editor. Copy and paste the commands (one by one) and wait for each process to complete for continuing.
FAQ
Roms/Kernels
Q: What is the best rom?
A: The "best" rom is a matter of opinion. Do you like a certain customization and can't live without it? Use a rom that has that option.
Q: What is the best rom for battery life?
A: Roms themselves really shouldn't impact your battery all that much. They can have an impact, but if you're really looking for better battery I'd suggest swapping kernels or tweaking yours.
Q: What is the best rom for stability?
A: All of the roms out are "stable." They may have options that don't work correctly, but generally: this is user error. If you follow my advice on installing a rom, you'll end up with MUCH fewer bugs.
Q: What is the best kernel?
A: The best kernel is a matter of opinion. Some users may love one, while others swear by another. Find one you like and tweak it accordingly.
Q: How do I tweak a kernel for better battery?
A: Generally, you'll want to either change your governor and or undervolt and or underclock your kernel. This is done either by using SetCPU or similar apps, or with an option in your rom (usually labeled "performance" or something similar). Take note: extremely high/low voltages may cause instability. Never "set at boot" until you've thoroughly tested the options you've set. Testing includes low strain (like turning your screen off for an hour) and high strain (like playing a game for an hour) scenarios. To be extra safe: run the values for a couple days before setting them at boot. Follow the users ideas in the kernel's threads for some guidelines. However, remember that not all values will play nicely with all phones.
Miscellaneous
Q: Why isn't Google Wallet working at [store]?
A: I'm not sure if it's a Google Wallet problem, or a problem with the terminal. But I personally struggle to find a terminal that consistently works in my area. Something that has generally worked for me is to open wallet and go to Options>Reset Google Wallet. You must then re-add any cards you had.
Q: Does my ass look good in these shorts?
A: Yes.
Neat Ideas / How to Show Off the Nexus 4
-Get some NFC stickers. Tagstand has them available.
You can use these to make your phone perform certain tasks when you touch the sticker. Use NFC Task Launcher to define the tasks. These are capable of doing simple things like muting your volume to the more complex like turning on Tasker tasks that do things like auto-reply to text messages while you're at work.
-Do you have any suggestions? Submit them below!
***I take no responsibility for what happens to your phone due to following this guide! That being said, not only am I sure you'll be fine...but there are an endless amount of users who would be glad to help if you need it.***

ADB Backups:
SDcard backup:
Code:
adb pull /sdcard/ /sdcard/
(This will pull all of your sdcard contents to an "sdcard" folder in your C:\ directory)
Applications and their data:
Take note, that you'll need to be using CyanogenMod's method for setting up ADB to do this. The ADB AIO application installs an older SDK without this functionality. First, get your drivers installed (detailed in post one). Once you get ADB installed (post one), navigate to the C:\android-sdk-windows\platform-tools folder on your computer. Hold shift and right click. Select "Open Command Window Here."
Input this while your phone is turned on and USB Debugging is Enabled:
To do so; you must first go to Settings>About>Build Number and click seven times.
The actual setting can then be found in Settings>Developer Options>USB Debugging
Type this:
Code:
adb backup -apk -noshared -all -nosystem
(Hit Enter)
Your phone will ask for a password. Input one and remember it.
Once the process completes: continue with unlocking and rooting your phone.
Restoration:
Upon unlocking and rooting your phone: open up ADB again.
Enter this code:
Code:
adb restore backup.ab
(Hit Enter)
Input the password you saved to this file earlier, and wait for the restore to complete.
To restore your SDcard backup, first move the "sdcard" folder that was made in the backup process to your platform-tools folder.
Then run:
Code:
adb push sdcard /sdcard/

Do you have to install "ADB" ?

As far as like...clicking it and letting the windows installer install...no.
The exe file will read the commands in cmd without "installation."

Nice Work!

I've just added this guide to the Nexus 4 Complete Index
Sent from my GT-I9100 using xda premium

Great work!!! nice and clean reading!

Can this guide include information on how to re-lock bootloader and unroot the device? Does this informaiton exist?
I need to RMA my phone due to dead pixels and I want to make sure I dont have any issues with the warranty.

jayluke said:
Can this guide include information on how to re-lock bootloader and unroot the device? Does this informaiton exist?
I need to RMA my phone due to dead pixels and I want to make sure I dont have any issues with the warranty.
Click to expand...
Click to collapse
Post 3.
fastboot oem lock
Locks the device.

How long is the first boot, after unlocking the bootloader, supposed to take? Mine's sitting there for quite a while already. (I had a lot of stuff installed, but still, this is really long.)
EDIT: When rebooting the custom recovery, you have to say "yes" to the message it gives you, something about keeping some recovery. I had originally said no because I didn't flash it, I just booted it once.

I just got my nexus yesterday, and this isnt the first phone that I have rooted.... however... my settings on the thing are extremely basic..
How do I enable usb debugging if I dont have the option in the settings?
Thanks
Chris
---------- Post added at 03:19 PM ---------- Previous post was at 03:14 PM ----------
I just got my nexus yesterday, and this isnt the first phone that I have rooted.... however... my settings on the thing are extremely basic..
How do I enable usb debugging if I dont have the option in the settings?
Thanks
Chris
Edit: Got an app to enable it... still not in the menu though.

wizshaw said:
I just got my nexus yesterday, and this isnt the first phone that I have rooted.... however... my settings on the thing are extremely basic..
How do I enable usb debugging if I dont have the option in the settings?
Thanks
Chris
---------- Post added at 03:19 PM ---------- Previous post was at 03:14 PM ----------
I just got my nexus yesterday, and this isnt the first phone that I have rooted.... however... my settings on the thing are extremely basic..
How do I enable usb debugging if I dont have the option in the settings?
Thanks
Chris
Edit: Got an app to enable it... still not in the menu though.
Click to expand...
Click to collapse
Oh geeze!
I forgot.
Settings>about>version number I think...
Click 7 times to enable developer options.
Will update op soon.

Quick question: is there a reason the first post links to SuperSU version 0.98, when version 0.99 is the most recent? If version 0.99 has known issues with the Nexus 4, I don't want to use it on my device.

The 0.99 version came out after this guide was posted. I was offered to upgrade to the new version of supersu from 0.98 and so far no problem at all.

Does this work on the latest version of JB (4.2.1)?

When installing a new ROM it says to perform a factory reset through CWM, which will remove all apps and data but should keep all your pictures, videos, songs etc.
It doesn't mention to wipe the System partition as well. Is this not necessary when flashing ROMs on a Nexus?
Prior to owning the N4 I had the Galaxy S 2 and it was always stated in the OP instructions to wipe data/factory reset, wipe system, clear cache, clear dalvik and then flash ROM and Gapps.
However, I don't notice in any guides or instructions for N4 ROMS to wipe the system partition, just the data partition. Is there a reason for this or is it not necessary to wipe the system partition? Thanks. Great guide by the way.
Peace

thank u for ur effort

Chochiwpg said:
When installing a new ROM it says to perform a factory reset through CWM, which will remove all apps and data but should keep all your pictures, videos, songs etc.
It doesn't mention to wipe the System partition as well. Is this not necessary when flashing ROMs on a Nexus?
Prior to owning the N4 I had the Galaxy S 2 and it was always stated in the OP instructions to wipe data/factory reset, wipe system, clear cache, clear dalvik and then flash ROM and Gapps.
However, I don't notice in any guides or instructions for N4 ROMS to wipe the system partition, just the data partition. Is there a reason for this or is it not necessary to wipe the system partition? Thanks. Great guide by the way.
Peace
Click to expand...
Click to collapse
I actually have a question along these lines.
I just came from a LG G2X so things were different for me whenever I flashed ROM's/kernels. For one thing, I had an external sd card so whenever CWM made it's backups, they went to that automatically and I didn't have to worry about wiping since everything was on the external. This phone doesn't have an external so where do the backups go? From the looks of the new CWM 6.0.2.0, the backups (and blobs now apparently) go to /data/media/clockworkmod. Well I guess my question here is if you have to wipe /data for installing new ROM's, how would I restore a backup because they would have been deleted off the /data partition. I tried adb pulling /data/media/clockworkmod to my computer but it won't go. Don't know if it's because that partition is mounted while the phone is in use or what. I tried the mount/umount command that OP listed but it won't work for me. Don't want to flash ANYTHING on this phone until I know for a fact I can get to the backups that I'm creating.

Can't write on internal SD card after root

After having rooted (with nexus 10 toolkit v1.3.0) my nexus 10 and flashed AOPK Nexus 10 (WIP) Task650 & Ktoonsez (1-4) rom, I'm unable to upload to, change or move any files or folders on my internal SD card. I installed Root Explorer and changed from Mount R/O to Mounted as r/w. Access is granted by Super SU. I also tried to change permission settings, unfortunatedly without any success. There appeared the following message:
"Warning
Permissions change was not successful. Please note that some file systems (e.g. SD card) do not allow permission changes."
Is there a possibility to change these permissions in order to be able to create and move files and folders on my SD card?
Thanks for taking your time to help me with my issue!
Anzirothu

1. Clear cache
2. Clear dalvik
3. Fix Permissions
forgot something ?

Thank you for your reply, Patrik!
1. done.
2. done.
3. Fix Permissions - How? With cwm? I did fix permissions with cwm recovery, but the problem persists...

Just so we are clear, when you say "upload to, change, or move" are you meaning you cannot copy a file from your computer to your Nexus 10? Or just that you cant arrange stuff through root explorer from within the tablet itself?

Neither copying from PC to Nexus nor arranging stuff through root exlorer from within the tablet itself. I can't even download an email attachment and put it to the SD card. The card seems to be locked.

I had that problem once but I dont remember what caused it or what exactly I did to fix. I think I just did a complete wipe by locking and unlocking the bootloader and then installing a new ROM again.

I think I did this too (unroot, lock bootloader, then root and unlock bootloader) and then installed the same rom again. I will try it this time with another rom.
Isn't there really no other solution to get access to my SD card again??
Thx for your help!

Are you using a toolkit to unlock and root? If so them maybe it is not doing something right and it messing up a permissions somewhere. It could also be a driver problem on your PC with being unable to copy a file to the tablet.

Thank you for your help!
I am using the nexus 10 toolkit V1.3.0. Right now I'm trying to intall twrp recovery with a fully wiped sd card. No easy task fot me being a noob...

In ClockWorkMod, make sure that /data is mounted
Then download the Android SDK: http://developer.android.com/sdk/index.html
I usually put all the files just in C:/android-sdk-windows
Once you have it all there open up the SDK Manager and download all the additional files needed. You probably only need to download "Android SDK Tools" and "Android SDK Platform-tools", but I always download the other files for whatever version of Android I am running, in our case Android 4.2. That way I have them if I need to do something else.
Once downloaded, open the Android-sdk-windows/platform-tools directory. copy:
adb.exe
adbWinApi.dll
adbWinUsbApi.dll
fastboot.exe
to your base C:/Android-SDK-Windows directory.
Now open command prompt from Start -> run
type: cd C:/Android-SDK-Windows
type: "adb devices" and it should list your tablet. It will actually say something with your devices serial number and then "Recovery" after it, showing your tablet is in recovery. If you dont see this then you either dont have your tablet mounted right from in the Recovery, ClockWorkMod is stupid, or you dont have working adb drivers.
Now copy the ROM you want to flash to C:/Android-SDK-Windows
Then type: "adb push blahblahblah.zip /data/media/0"
That should push the ROM to the root of your SD card. Give it time, it takes a while to push a ROM file. Once it is done, flash the ROM.
That *should* put it in the right spot where it looks like it is on your "internal storage" (what you see when navigating files within the ROM). If you dont see the ROM in clockworkMod then keep navigating back to the root of your internal storage and then open up "data", then "media", then "0" and you should see it. If you still cant find the ROM, push it again but just use "/data/media" as the location.
I just did all these steps myself to verify I remembered it all correct and I was able to successfully copy a ROM and find it on my tablet to flash by doing everything I just listed above. SO you should be good to go if you follow all those steps properly. I know it looks like a lot of work, but it really isnt and will go quite fast. Most of it is just the setup for getting ADB and Fastboot ready to use.
For a ROM to install, I would recommend to someone new like you either of these:
http://forum.xda-developers.com/showthread.php?t=2071082
^^^^^ That one is pretty close to the stock ROM with a few fixes and a couple extra features
or: http://forum.xda-developers.com/showthread.php?t=2071082
^^^^^ This one is pretty much CyanogenMod 10.1, but built by a different guy and not pulling every new thing from CM, just the "cherry picks" of features. It tends to be a bit more stable and less buggy than the real CM10.1 nightly's
And for a kernel you can flash and forget you will want to try this one:
http://forum.xda-developers.com/showthread.php?t=2098157
^^^^^ To flash that you will want to do a similar thing as how you pushed the ROM to your device. Only this time you will copy the kernels' "boot-r4.img" file into your android-adk-windows directory and use the command: "fastboot flash boot boot-r4.img"
While I enjoy the KTManta kernel more, it does require a bit of tweaking to get running perfect. Which is one of the things I like about it because of all the options to tweak. But for someone just learning this stuff that would be a bad thing, so Franco's kernel is much better than stock and doesnt require you to adjust anything once it is flashed to your tablet.

[GUIDE] Get Xposed working on your deodexed TouchWiz based Lollipop ROM! 2015/08/17

DISCLAIMER
The process of flashing a custom recovery/kernel/firmware may and will trigger your device's Knox Counter. Neither XDA nor I can be held responsible for your actions. Proceed with caution. During this process you will lose all your settings and apps. As long as you follow the instructions, your device's storage, internal and external, won't be touched​
Still not compatible with x64 systems! Not compatible with Samsung 5.1.x (sdk22) ROMs!
Hello, Ladies and Gentleman
Many people seem to have a hard time to understand how all of this here on XDA works. I constantly get PM's from users, asking how to do the most basic stuff like flashing a .zip or stock firmware via Odin. Usually, I don't even read them and just hit delete. I know it's not ok to deny people help, so I decided to show you how you can get Xposed working on your TW based stock or custom ROM since it's the most frequently asked question I get.
It's nothing you couldn't do if you'd just....
We're going to use @arter97's customized Xposed Framework as the one made by @darkera13 needs the user to manually modify and replace files which may be too complicated for some.
Preparation
-READ EVERYTHING OVER AND OVER AGAIN.
-A custom recovery System like TWRP or CWM (PhilZ or Stock)
-A deodexed ROM. It's the only way to go. YOU NEED A DEODEXED ROM. If your ROM is not deodexed and you flash the framework, you'll end up in a bootloop. To deodex your existing ROM carefully follow Post #2
Here are a few made by XDA Senior Member @_alexndr
Stock deodexed for SM-N9005 Galaxy Note 3 International Qualcomm.
Stock deodexed for SM-G900F Galaxy S5 International Qualcomm
-And the framework itself from here
[UNOFFICIAL] Xposed for Samsung Lollipop by arter97
-Flash a custom recovery system of your choice. This is listed under preperation on purpose since this guide is about getting Xposed on your TW Lollipop device. A guide on how to get a custom recovery system is most certainly available in your device's forum.
-Store the ROM and the Framework in an easy to find folder, which we're gonna call "folder x". It doesn't matter where you store it (ext. SD or int. SD)
The Fun Part
-Boot into your custom recovery and make a full wipe:
TWRP users: "Wipe>Advanced Wipe> Tick System, Data, Cache, Dalvik Cache> Slide to format.​CWM users: "Mounts and Storage> hit Format /System; hit Format /Data; hit Format /Cache.​
-Still in recovery system, install, or flash the files we put in folder x;
TWRP users: "Install> Navigate to folder x and choose the ROM file first> Add Zip> now choose the Xposed Framework from folder x> Slide to flash.​CWM users: "Install Zip> Choose zip from /sdcard if folder x is on internalt storage or /storage/sdcard1 if folder x is on ext. storage (SD-Card)>​choose the ROM file first> -Yes - install ROMXY.zip.​Do the same with the Xposed Framework zip file.​
-Still in recovery system, reboot device and wait for it to boot. It can take up to 20 minutes. Enjoy Xposed on your Samsung TouchWiz Lollipop ROM.
-Stuck in a bootloop? Try this and repeat the process.

XDA Senior Member @Honzze kindly pointed out to keep following in mind; You have to start JoelDroid Lollipop Batch Deodexer with Admin permissions. Otherwise this error might return "path variable" of Java "is not set".
Deodexing your existing ROM without having to flash an entire ROM
As the title says, with this awesome guide by XDA Senior Member @townsenk you don't have to reflash an entire new ROM to your device. Instead, youll just deodex those parts of your System which need to be modified in order to get Xposed working. You don't necessarily have to perform a full wipe if you do it this way. But if you encounter fc's or end up in a bootloop, you know what to do
Guide for this guide:
Regarding point 1: "...launch a DOS shell..." just means, you need to open the so called "CMD" programm in Windows. To "launch a DOS shell" or CMD from within a folder, you simply have to hold down the shift key and right click in that folder. The context menu will show an entry "open command window here". And that's it! (Windows XP users may have to search the internet for another solution)
For Galaxy S5 and Note 3 users: If ADB returns "device offline" or an empty line after "List of devices attached" make sure your using a USB 2.0 data cable on a USB 2.0 port
townsenk said:
How to DeOdex YOUR (...) Rom.
I would like to note that I appreciate all the work that developers have put forth in creating and maintaining modified Roms. there are some awesome feature rich implementations available. My intentions are not to be critical of any specific Rom or mod. Without the developers we would have nothing.
(...)
This method is very common knowledge I thought I'd just explain it in an easy to understand way.
Here is what you need.
A stock (...) ROOTED configurated phone. Debloat as needed. Set the phone up exactly how you like it with apps and such.
Make sure it's stable. (If you have issues before DeOdexing they will be there afterward!)
Here's the files you may need to make this happen
LBD2.4.zip
7-Zip
Installer template (at end of post)
1> Make sure ADB is working on your computer. USB debugging turned on. Create a folder to store your soon to be download system files and launch a DOS shell from that working folder. Working folder name should NOT contain spaces. With the phone hooked up you should be able to type adb shell and get a prompt.
2> Type these commands
adb pull /system/app app/
adb pull /system/priv-app/ priv-app/
adb pull /system/framework framework/
This will take awhile and you will be left with three folders
Create a new folder named "system" and place these three folders inside.
3> Extract and launch LBD2.4 (This is the DeOdexer and is AWESOME). Point it at your recently created "system" folder and let it do it's thing.
I'll assume this will occur without errors as I have never had any.
4> At this point you can manually apply modded apk's to the system folder but I don't really recommend it. They can be applied afterward using the seperate installer zips.
5> with 7-Zip installed open the provided Installer template. Do not Extract it. Just open it in the 7-Zip file browser using the right click context menu in windows.
Drag-Drop the contents of your system folder into the empty system folder in the 7-Zip browser It should be the three folders previously created but now they are Deodexed. Close the 7-zip file manager and select Yes if it asks you to save.
Note: The provided installer template has been modified to only wipe and replace the three system directories.
6. Copy the created installer to your sdcard and install with recovery. Wipe cache and Dalvik before rebooting.
Go have lunch. You will sit at a boot screen for about 10 minutes. Then another 20 to rebuild caches. Time varies.
7. Your system will now be Deodexed! At this point you can install your mods one at a time, I recommend this so you can test your system between installs to determine if a specific mod is creating problems.
This method has so far removed ALL of my stability issues.
Click to expand...
Click to collapse

Since I no longer own this device, I'm retiring from this thread as of now. Hope I could help you.

Don't know if someone can help me as you stated that you're retired from this thread.
I did every step you do mentioned here (for self deodexing existing rom)
I did everything successfully and deodexed my files with 2.5 deodexer, putted files in the system folder to the 7zip folder and sent to my device and flashed zip, cleaned cache and dalvik and it stuck on booting for about 15 minutes. I know, it takes alot time during rebuildup of cache, but guys, it's 15 minutes! for me, if i cleanup cache and the dalvik/art cache, it just takes 1minute on boot screen to show up the image of each apps cache, but i just sat there with lots of patient for 15 minutes or a bit more and still same, stuck in same crappy booting logo.
I did restore my system files, now i'll try to retry it and send it again. Im suspicious of the zip file being corrupted during trasmitting to Device, however install was a big success so im very sure it wasnt corrupted. I'll do 2nd test and see it again if it's happening again.
If it does, i'll most likely try to figure out other ways to deodex as there is already deodexed roms out there, so they must have done is somehow.
Thanks, hope someone can help me out with this.
P.S: My adb works fine, i got usb drivers for my device, i got usb debug on, i got lots of space on phone, i got TWRP recovery which got very high compatibility when it comes to install anything from zip via recovery where almost all roms do work stable with TWRP.

omg brilliant @nitrous² ! thanks so much! its been days i keep trying to deodex with others tool...

Sachitoge said:
Don't know if someone can help me as you stated that you're retired from this thread.
I did every step you do mentioned here (for self deodexing existing rom)
I did everything successfully and deodexed my files with 2.5 deodexer, putted files in the system folder to the 7zip folder and sent to my device and flashed zip, cleaned cache and dalvik and it stuck on booting for about 15 minutes. I know, it takes alot time during rebuildup of cache, but guys, it's 15 minutes! for me, if i cleanup cache and the dalvik/art cache, it just takes 1minute on boot screen to show up the image of each apps cache, but i just sat there with lots of patient for 15 minutes or a bit more and still same, stuck in same crappy booting logo.
I did restore my system files, now i'll try to retry it and send it again. Im suspicious of the zip file being corrupted during trasmitting to Device, however install was a big success so im very sure it wasnt corrupted. I'll do 2nd test and see it again if it's happening again.
If it does, i'll most likely try to figure out other ways to deodex as there is already deodexed roms out there, so they must have done is somehow.
Thanks, hope someone can help me out with this.
P.S: My adb works fine, i got usb drivers for my device, i got usb debug on, i got lots of space on phone, i got TWRP recovery which got very high compatibility when it comes to install anything from zip via recovery where almost all roms do work stable with TWRP.
Click to expand...
Click to collapse
Same happened to me.... Did you solved this problem?

Maurizio1953 said:
Same happened to me.... Did you solved this problem?
Click to expand...
Click to collapse
Nope, i ended up using CM12 (at that time, right now i got cm13 update).
Well i had to deodex apps to get xposed on TouchWiz, but i failed and didn't get headache because of the Xposed modules being not really well compatible on TouchWiz, so i jumped to CM, i find it more stable, and the CM13 is insane because it saves so much battery at stand by, compared to lollipop, the Android 6.0.1 Marshmallow is the biggest update in android history, that saves hell lot of battery (it can be also maybe because i don't have Xposed Framework in recent rom).
Anyway, im tired of it, and i don't need to hassle with Link2Sd because of Android Marshmallow offering to mount the SD Card, in the end, all my needs are being offered in this (for me) huge, best android update, being Marshmallow.
Try it i would say, so amazing.

Ok i would like to go to cm13 as you but i stil need the support to the gear s smartwatch so i decided to stay with touchwiz without xposed.

SM-G903U: Xposed for Nougat

Xposed or not Xposed? Well either one may or may not be good depending on the situation.
I did not create anything. I am just putting steps together and giving instructions. I am not responsible if anything breaks or catches fire. This requires at least Android 7.0.
Given what I put this phone through already (a pretty good story if you're a little nerdy like me), I decided to try it out.
1) Download FlashFire and install. Make sure it's granted root access. It might force close the first time, just swipe it closed in recent button and reopen it.
2) Download the .zip and installer from here.
3) Via ADB, install the Xposed APK, but DO NOT open the app yet.:
Code:
adb root
adb install nameofpackage.apk
4) Place the .zip it into internal storage (sdcard). I pushed it through ADB:
Code:
adb root
adb push nameofzip.zip /sdcard
5) Open FlashFire. Tap the '+' at the bottom right and select 'Flash ZIP or OTA'. Find the .zip you just put on your sdcard and select it.
4) In the 'options' window, please select 'mount /system read/write'. make sure ONLY that option is selected. Tap the check mark at the upper right.
5) Some say to do a davlik and cache wipe. If you have a near freshly flashed device or out of the box new, I wouldn't wipe anything. I have had some issues when flashing Xposed via FlashFire on this device when doing so. BUT, if you're like me and like to walk on the wild side; tap the plus sign again, select wipe and select davlik and cache ONLY. Tap the check mark.
6) I've done this next step both ways, but not sure if it makes a difference. It might though I have no real idea. Make sure the Wipe cache is first, then Xposed. I am on a fresh ROM so I did not wipe cache at all.
7) After reboot, go to the Xposed App and tap it. You're welcome.

I had a feeling this wasn't working and removed it. Everything went smooth, but I am pretty sure it wasn't working. Modules seemed to install, but didn't do anything. A few apps I use have modules and they didn't respond to Xposed. Seems like they couldn't see Xposed.

[GUIDE] Root and/or install a GSI on razer phone 2 and pass safety net (For Windows)

YOUR WARRANTY IS NOW VOID! I am not responsible for anything that could happen, dead sd card, bricked phones, you name it. You chose to install this software and you face the risk of any bugs that may affect you. This is just a warning incase anything goes wrong
ISSUE: FASTBOOT Might not work on windows 10 version 2004, a solution is to use a Linux virtual machine to use fastboot commands. Test it out first as you might be lucky and it could work for you.
A complete guide on how to either just root the razer phone 2 and/or install a gsi with everything working.
The sections are: Basics - Installing TWRP - Rooting - Installing a GSI + Root - Passing safety net to use baking apps, certain games etc.
Basics: (You will have to factory reset if you have not unlocked your bootloader before)
Download this and this file, un zip them both and move them to a known directory such as C:\ADB
Then on your phone, go into developer options and enable OEM/Bootloader unlocking, and after that reboot into the bootloader by holding POWER + VOL DOWN and plug the phone into your pc (I recommend you connect it to a USB 2.0 port, as USB 3.0 might give you issues with the fastboot commands)
Then we need to install bootloader drivers onto our phone, so open device manager, click the drop down menu next to Android Device, right click on Android and select Update Driver, then select Browse my computer for driver software, Let me pick from a list of available drivers on my computer, Show all devices, Have disk and navigate to your folder where you extracted the .zips (in my case C:\ADB) and open the usb_driver folder and select android_winusb.inf. In the next menu select Android Bootloader Interface, proceed through the warning and install it.
To unlock the bootloader open a cmd window in the directory of your platform-tools folder, which in my case would be C:\ADB\platform-tools (type cd C:\ADB\platform-tools in cmd) and run two commands: fastboot flashing unlock (after each one select yes on your phone and let it reboot - it might take a while) and fastboot flashing unlock_critical
To install the arter97 kernel/TWRP: (keep your phone in the Bootloader and plugged into the pc)
Download both the .zip and .img file from this link (i am using r12 intentionally as it causes less issues) and download this zip file as well
Move both .zip files onto your phones SD CARD (important) and rename the .img file on your PC to Boot.img and place it into your platform-tools folder (C:\ADB\platform-tools in my case)
Open a command prompt window and like before change the directory to the platform-tools folder, then run two commands: fastboot flash boot_a boot.img and fastboot flash boot_b boot.img
Now using the volume keys select the Recovery Mode option in the bootloader and press the power key to select it, if it asks for a decryption password cancel it, and if it asks to allow system modifications swipe to allow it
Go to the Install section and navigate to external_sd and navigate to the arter-r12.zip you installed, then click it and swipe to flash, after that flash the f2fs zip and after it's complete back out to the main menu, click reboot and select recovery
Once you are back in recovery, go to Wipe and select Format Data (this will not erase your sd card if it is set as external storage) and type yes
If you don't want to root then to reboot to system go into Reboot and select System, TWRP will ask you if you want to install their special app, DO NOT INSTALL IT, CLICK ON DO NOT INSTALL.
Now you are ready to proceed to the next step(s) (these are short now don't worry)
To just root and stay on the stock ROM:
Download magisk 20.1 (works better) from here and move it onto your phone sd card by going to the main TWRP menu, selecting Mount then SD card and you should be able to transfer the file onto the sd card directly from your PC
Then simply flash the magisk 20.1 zip in TWRP as we did before and you can now reboot system (make sure to not install the TWRP app)
Magisk Manager will prompt you to update magisk, DONT do it. You can however install the latest magisk manager update
To install a GSI and Root: (lineageOS is what i have linked here, however this is not the only one you can use, make sure you NEED gapps before flashing it incase they are included anywhere)
Firstly, to have bluetooth working go to Mount and select Vendor, go back, select Advanced then File Manager then navigate to /vendor/overlay/ and delete both BluetoothResCommon.apk and RazerAuraBluetoothRes.apk
Then download the latest arm-64-bvN .img file from here, unzip it on your computer and move the .img file to your phone. If you also want gapps (google apps) download this file and move it onto your SD card as well
Now, head to the TWRP Install section, at the bottom select Install Image, select the downloaded lineageOS (or your own gsi) .img file, in the next screen select System Image and swipe to flash it.
Once it has flashed back out to the main screen and click on Wipe, then select Advanced Wipe, then select System, Repair or change file system, and finally press Resize and swipe to do it, if it fails then re do this step
Then go back into the Install section and flash the opengapps zip file and after that the magisk zip file
Now you can reboot to system (might take a couple minutes) and set up the phone.
If you notice it is running slowly go into settings > Phh treble settings (might have to force close app once for it to appear) > Misc Settings > Force FPS > and select the 120.00001 at the bottom (top numbers are 1080p and bottom numbers are 1440p)
Finally, to pass safetynet:
Head into magisk manager, go to its settings and enable Hide Magisk, then call it Manager and allow it to reinstall itself, after that enable Magisk Hide in the settings aswell (hide your banking apps with this or any game that wont boot due to ROOT)
Then go into the magisk downloads section and search for the ArCore module, install this, reboot and your safetynet will pass on a gsi
This is my first xda post so my formatting may be bad but i hope it can help some people if you have any questions drop a comment and please like the post if it helped you for more people to see it.
Have a good day

Usyless said:
YOUR WARRANTY IS NOW VOID! I am not responsible for anything that could happen, dead sd card, bricked phones, you name it. You chose to install this software and you face the risk of any bugs that may affect you. This is just a warning incase anything goes wrong
A complete guide on how to either just root the razer phone 2 and/or install a gsi with everything working.
The sections are: Basics - Installing TWRP - Rooting - Installing a GSI + Root - Passing safety net to use baking apps, certain games etc.
Basics: (You will have to factory reset if you have not unlocked your bootloader before)
Download this and this file, un zip them both and move them to a known directory such as C:\ADB
Then on your phone, go into developer options and enable OEM/Bootloader unlocking, and after that reboot into the bootloader by holding POWER + VOL DOWN and plug the phone into your pc (I recommend you connect it to a USB 2.0 port)
Then we need to install bootloader drivers onto our phone, so open device manager, click the drop down menu next to Android Device, right click on Android and select Update Driver, then select Browse my computer for driver software, Let me pick from a list of available drivers on my computer, Show all devices, Have disk and navigate to your folder where you extracted the .zips (in my case C:\ADB) and open the usb_driver folder and select android_winusb.inf. In the next menu select Android Bootloader Interface, proceed through the warning and install it.
To unlock the bootloader open a cmd window in the directory of your platform-tools folder, which in my case would be C:\ADB\platform-tools (type cd C:\ADB\platform-tools in cmd) and run two commands: fastboot flashing unlock (after each one select yes on your phone and let it reboot - it might take a while) and fastboot flashing unlock_critical
To install the arter97 kernel/TWRP: (keep your phone in the Bootloader and plugged into the pc)
Download both the .zip and .img file from this link (i am using r12 intentionally as it causes less issues) and download this zip file as well
Move both .zip files onto your phones SD CARD (important) and rename the .img file on your PC to Boot.img and place it into your platform-tools folder (C:\ADB\platform-tools in my case)
Open a command prompt window and like before change the directory to the platform-tools folder, then run two commands: fastboot flash boot_a boot.img and fastboot flash boot_b boot.img
Now using the volume keys select the Recovery Mode option in the bootloader and press the power key to select it, if it asks for a decryption password cancel it, and if it asks to allow system modifications swipe to allow it
Go to the Install section and navigate to external_sd and navigate to the arter-r12.zip you installed, then click it and swipe to flash, after that flash the f2fs zip and after it's complete back out to the main menu, click reboot and select recovery
Once you are back in recovery, go to Wipe and select Format Data (this will not erase your sd card if it is set as external storage) and type yes
If you don't want to root then to reboot to system go into Reboot and select System, TWRP will ask you if you want to install their special app, DO NOT INSTALL IT, CLICK ON DO NOT INSTALL.
Now you are ready to proceed to the next step(s) (these are short now don't worry)
To just root and stay on the stock ROM:
Download magisk 20.1 (works better) from here and move it onto your phone sd card by going to the main TWRP menu, selecting Mount then SD card and you should be able to transfer the file onto the sd card directly from your PC
Then simply flash the magisk 20.1 zip in TWRP as we did before and you can now reboot system (make sure to not install the TWRP app)
Magisk Manager will prompt you to update magisk, DONT do it. You can however install the latest magisk manager update
To install a GSI and Root: (lineageOS is what i have linked here, however this is not the only one you can use, make sure you NEED gapps before flashing it incase they are included anywhere)
Firstly, to have bluetooth working go to Mount and select Vendor, go back, select Advanced then File Manager then navigate to /vendor/overlay/ and delete both BluetoothResCommon.apk and RazerAuraBluetoothRes.apk
Then download the latest arm-64-bvN .img file from here, unzip it on your computer and move the .img file to your phone. If you also want gapps (google apps) download this file and move it onto your SD card as well
Now, head to the TWRP Install section, at the bottom select Install Image, select the downloaded lineageOS (or your own gsi) .img file, in the next screen select System Image and swipe to flash it.
Once it has flashed back out to the main screen and click on Wipe, then select Advanced Wipe, then select System, Repair or change file system, and finally press Resize and swipe to do it, if it fails then re do this step
Then go back into the Install section and flash the opengapps zip file and after that the magisk zip file
Now you can reboot to system (might take a couple minutes) and set up the phone.
If you notice it is running slowly go into settings > Phh treble settings (might have to force close app once for it to appear) > Misc Settings > Force FPS > and select the 120.00001 at the bottom (top numbers are 1080p and bottom numbers are 1440p)
Finally, to pass safetynet:
Head into magisk manager, go to its settings and enable Hide Magisk, then call it Manager and allow it to reinstall itself, after that enable Magisk Hide in the settings aswell (hide your banking apps with this or any game that wont boot due to ROOT)
Then go into the magisk downloads section and search for the ArCore module, install this, reboot and your safetynet will pass on a gsi
This is my first xda post so my formatting may be bad but i hope it can help some people if you have any questions drop a comment and please like the post if it helped you for more people to see it.
Have a good day
Click to expand...
Click to collapse
Thank you excellent post just what I needed.

eedwin101 said:
Thank you excellent post just what I needed.
Click to expand...
Click to collapse
I'm glad it helped you

Usyless said:
I'm glad it helped you
Click to expand...
Click to collapse
If you don't mind what other GSI ROMs have you tried that worked well with this phone I am particularly interested in the Google pixel Android 11. Thanks again you have extended the life of this phone for me.

eedwin101 said:
If you don't mind what other GSI ROMs have you tried that worked well with this phone I am particularly interested in the Google pixel Android 11. Thanks again you have extended the life of this phone for me.
Click to expand...
Click to collapse
I know that phhussons AOSP works on this phone with no issues aswell, you might have to use securize to get safety net to pass tho.
android 11 will boot on this phone however iirc you won't be able to hear and other people won't hear you in phone calls.
havoc gsis I believe works but I haven't tested it and I have only heard of one person using it.
BLISS/LOSQ/CAOS don't work on this phone at all.
and after that I don't think there really is many more GSIs that work as they just won't boot for bizarre reasons

How about text messaging. Currently i have not been able to get SMS to work with any GSI on Android 10. Are you able to send and receive text messages? Did you have to do anything to get it working? If so, let me know because i have been having a heck of a time with it.

_Sherrif said:
How about text messaging. Currently i have not been able to get SMS to work with any GSI on Android 10. Are you able to send and receive text messages? Did you have to do anything to get it working? If so, let me know because i have been having a heck of a time with it.
Click to expand...
Click to collapse
oh this issue... are you on T-Mobile by any chance as if you are there is no fix yet and you will have to wait for official lineageOS.
I am on three (UK) and everything works perfectly.

Usyless said:
oh this issue... are you on T-Mobile by any chance as if you are there is no fix yet and you will have to wait for official lineageOS.
I am on three (UK) and everything works perfectly.
Click to expand...
Click to collapse
No AT&T.

_Sherrif said:
No AT&T.
Click to expand...
Click to collapse
you might be able to use this fix (it's a magisk module) as it is made for AT&T https://t.me/razer_phone/14202
its called a volte fix but it should help with sms, if it doesn't work you can just remove the module, reboot then delete some qualcomm.ims app (should be shown in your app list)

_Sherrif said:
No AT&T.
Click to expand...
Click to collapse
or you could try this: https://t.me/razer_phone/12949
install instructions shown in the message

Usyless said:
you might be able to use this fix (it's a magisk module) as it is made for AT&T https://t.me/razer_phone/14202
its called a volte fix but it should help with sms, if it doesn't work you can just remove the module, reboot then delete some qualcomm.ims app (should be shown in your app list)
Click to expand...
Click to collapse
Aight! Definitely worth a try. Tried everything else.
Thank you!

Thanks!! Excellente guide, very important your note : "I recommend you connect it to a USB 2.0 port", with usb 3 doesn't work bootloader commands.

frannet said:
Thanks!! Excellente guide, very important your note : "I recommend you connect it to a USB 2.0 port", with usb 3 doesn't work bootloader commands.
Click to expand...
Click to collapse
Thanks
It doesn't necessarily not work with usb 3.0, for some people (and for me) it works with a usb 3.0 port however for a lot of people they have issues with it.
I will add it tho.

Usyless said:
Thanks
It doesn't necessarily not work with usb 3.0, for some people (and for me) it works with a usb 3.0 port however for a lot of people they have issues with it.
I will add it tho.
Click to expand...
Click to collapse
It's strange. With my razer blade it has not worked (usb 3) but with a Dell Precision with a one port usb 2, work fine. I was going crazy.

frannet said:
It's strange. With my razer blade it has not worked (usb 3) but with a Dell Precision with a one port usb 2, work fine. I was going crazy.
Click to expand...
Click to collapse
Yeah I remember I helped somebody else root their phone and it didn't work with their razer blade either, they had to use some very old laptop.

Usyless said:
Yeah I remember I helped somebody else root their phone and it didn't work with their razer blade either, they had to use some very old laptop.
Click to expand...
Click to collapse
Guys, sorry for the off-topic, is available the dark mode for razer menu? i can't find it

frannet said:
Guys, sorry for the off-topic, is available the dark mode for razer menu? i can't find it
Click to expand...
Click to collapse
What do you mean razer menu? if you mean settings then it's a MAYBE.
on a gsi, dark mode is available
on stock android 9 it is possible. you need to use smali patcher to enable signature spoofing and then use swift theme installer alpha (substratum themes won't theme the settings)(you need to contact the developer to get the alpha version as others wont work)

Usyless said:
What do you mean razer menu? if you mean settings then it's a MAYBE.
on a gsi, dark mode is available
on stock android 9 it is possible. you need to use smali patcher to enable signature spoofing and then use swift theme installer alpha (substratum themes won't theme the settings)(you need to contact the developer to get the alpha version as others wont work)
Click to expand...
Click to collapse
Yeah I talk about the settings menu. I thought dark mode was available for all android versions ??

frannet said:
Yeah I talk about the settings menu. I thought dark mode was available for all android versions ?
Click to expand...
Click to collapse
yeah tbh idek, all the android fanboys were saying at how long it took apple to make a dark mode but it was implemented in android 10 later than ios 12 I swear ?
but as you are rooted you should be able to get a dark mode, just do as I said with smali patcher and the swift installer alpha

i
Usyless said:
yeah tbh idek, all the android fanboys were saying at how long it took apple to make a dark mode but it was implemented in android 10 later than ios 12 I swear ?
but as you are rooted you should be able to get a dark mode, just do as I said with smali patcher and the swift installer alpha
Click to expand...
Click to collapse
Hahaha, yeah, If I'm honest, dark mode in iOS work fine, very fine, normally I use my iPhone 11 and I play with android devices for.. for play with the OS and develoment OS, and as second andriods phone for maybe.... I go to check the gsi mode, thanks guy!!