Database Info

[Q] root without flashing?

I've looked at a few threads but they seem to involve flashing before rooting...
Is there a way to root without flashing? if so... how?
Thanks

You can unlock the bootloader without flashing by booting into Bootloader modem (power off device, then power on while holding Power+VOL UP) and typing fastboot oem unlock into ADB from your computer.
But you cannot gain root access, use a custom recovery, or use a custom ROM without flashing. The "Flashing" you're hearing about is via Fastboot which allows the flashing of custom recoverys, or boot.imgs.
The one-click methods that might have allowed this in the past were based on exploits in the stock ROM/kernel. The Nexus S might contain similiar flaws to be exploited later(no current methods work fyi), but right now the easiest way to gain root is by doing what I said above or from the threads in the development section dedicated to it (also linked in the stickied FAQ if you don't know where to start).
Given that it's also possible to just as easily relock the bootloader(e.g. for warranty purposes), it's likely it will be some time before the exploits are searched for/discovered.

unremarked said:
You can unlock the bootloader without flashing by booting into Bootloader modem (power off device, then power on while holding Power+VOL UP) and typing fastboot oem unlock into ADB from your computer.
But you cannot gain root access, use a custom recovery, or use a custom ROM without flashing. The "Flashing" you're hearing about is via Fastboot which allows the flashing of custom recoverys, or boot.imgs.
The one-click methods that might have allowed this in the past were based on exploits in the stock ROM/kernel. The Nexus S might contain similiar flaws to be exploited later(no current methods work fyi), but right now the easiest way to gain root is by doing what I said above or from the threads in the development section dedicated to it (also linked in the stickied FAQ if you don't know where to start).
Given that it's also possible to just as easily relock the bootloader(e.g. for warranty purposes), it's likely it will be some time before the exploits are searched for/discovered.
Click to expand...
Click to collapse
abit confused by what your saying...
I'm interpreting what your saying as
"you can boot a boot loader/recovery without actually flashing it. It just boots that as a temporary and then apply superuser.apk, su" ???

sinatosk said:
abit confused by what your saying...
I'm interpreting what your saying as
"you can boot a boot loader/recovery without actually flashing it. It just boots that as a temporary and then apply superuser.apk, su" ???
Click to expand...
Click to collapse
The bootloader is built into the phone, there's nothing to flash for that.
Think of it as a pre-recovery. Fastboot is a feature in the Android SDK which works with the bootloader to flash things such as recovery, or boot.imgs prior to actually having a custom recovery/root. However, it does require the bootloader to be unlocked which is where the fastboot oem unlock command comes in. Once you have a custom recovery on your phone, you flash things like normal.
From the stickied FAQ:
unremarked said:
Q: How do I root/unroot the Nexus S?
Check the development section links below for more detail, but you gain root on the Nexus S by booting the phone into fastboot (aka the bootloader) mode and typing "fastboot oem unlock." This will wipe your phone and it's SD card partition. To unroot it, again boot into fastboot mode and type "fastboot oem lock."
Step 1: http://forum.xda-developers.com/showthread.php?t=878786
Step 2: http://forum.xda-developers.com/showthread.php?t=875875
Click to expand...
Click to collapse
The first step helps you set up the SDK and drivers. The second step will tell you how to root, install recovery, and flash Superuser.

Out of interest is there a step 3 that tells us how to reverse all of the above in the event of having to return the phone?

xspyda said:
Out of interest is there a step 3 that tells us how to reverse all of the above in the event of having to return the phone?
Click to expand...
Click to collapse
No, I'll add one, but generally Best Buy employees don't check things like the recovery or bootloader to see if a phone is rooted or not.
Anyhow, if you if you flash the NAND backup found here: http://forum.xda-developers.com/showthread.php?t=884093 it will restore you completely to stock, including the recovery. After that, it's just a matter of going back into the boatloader/fastboot mode and typing fastboot oem lock.
That is the only way to return to stock until Google puts out the official recovery stuff.

Fair enough, thanks for that. One question, will this actually restore to a state my nexus s was received in? Reason I ask is that I thought this was an adapted nand - although I understand this is the only option right now.
My retailer is perhaps a little more clued up than the the average best buy employee so is there anything in the software that can identify this as being a none original Google image?
Thanks again.

unremarked said:
No, I'll add one, but generally Best Buy employees don't check things like the recovery or bootloader to see if a phone is rooted or not.
Anyhow, if you if you flash the NAND backup found here: http://forum.xda-developers.com/showthread.php?t=884093 it will restore you completely to stock, including the recovery. After that, it's just a matter of going back into the boatloader/fastboot mode and typing fastboot oem lock.
That is the only way to return to stock until Google puts out the official recovery stuff.
Click to expand...
Click to collapse
this is why I started this thread... Google not released the official recovery
I already have the SDK setup, I code android applications ... no fastboot in there though. May have to compile that myself or use the one from the thread
thanks for your help...

xspyda said:
Fair enough, thanks for that. One question, will this actually restore to a state my nexus s was received in? Reason I ask is that I thought this was an adapted nand - although I understand this is the only option right now.
My retailer is perhaps a little more clued up than the the average best buy employee so is there anything in the software that can identify this as being a none original Google image?
Thanks again.
Click to expand...
Click to collapse
It will restore your phone to the state it was received in if it had shipped with Android 2.3.1. The OTA should be fairly well known to anyone you're returning it to.
I don't think so. It's entirely possible that Samsung might have something tucked away deep inside the phone, either hardware or software, but I highly doubt it. And, if there were, I think only their technicians who are trained in the intricacies of this device would know about it. As far as I understand, that NAND is completely stock without any modifications. I'll admit I haven't read the entire thread. At the very most, it may have the Superuser.apk and related binaries but I don't think so.
sinatosk said:
this is why I started this thread... Google not released the official recovery
I already have the SDK setup, I code android applications ... no fastboot in there though. May have to compile that myself or use the one from the thread
thanks for your help...
Click to expand...
Click to collapse
Ah, sorry, I'm having a hard time with explaining stuff. Some threads I'll jump in to try and help assuming the guy knows about ADB, root, system vs SD partitions, et al then find out not so much. Other threads, I'll end up making myself look silly.
Fastboot should just be an .exe file within the SDK's tool's section. You don't actually have to run it, though. Everything involving fastboot operates through CMD just like ADB, only you begin the obviously differently. (fastboot flash blahblahblah vs adb push blahblabhlah).

unremarked said:
It will restore your phone to the state it was received in if it had shipped with Android 2.3.1. The OTA should be fairly well known to anyone you're returning it to.
I don't think so. It's entirely possible that Samsung might have something tucked away deep inside the phone, either hardware or software, but I highly doubt it. And, if there were, I think only their technicians who are trained in the intricacies of this device would know about it. As far as I understand, that NAND is completely stock without any modifications. I'll admit I haven't read the entire thread. At the very most, it may have the Superuser.apk and related binaries but I don't think so.
Ah, sorry, I'm having a hard time with explaining stuff. Some threads I'll jump in to try and help assuming the guy knows about ADB, root, system vs SD partitions, et al then find out not so much. Other threads, I'll end up making myself look silly.
Fastboot should just be an .exe file within the SDK's tool's section. You don't actually have to run it, though. Everything involving fastboot operates through CMD just like ADB, only you begin the obviously differently. (fastboot flash blahblahblah vs adb push blahblabhlah).
Click to expand...
Click to collapse
well yeah I know about ADB... just nothing about rooting

Hmm the phone shipped with 2.3 and I have yet to update but as 2.3.1 is an official update I can't see that being reason not to accept a return.

[Q] Nexus 5 strange behaviour after root

As the title suggest, does anyone else having such (one, more or all) issues on Nexus 5 after root?
1. Kitkat kinda initializes after every reboot. Not like the very first time starting the device (setup assistent) but installing/updating apps (which) are already on the device (same Verstion) and re-setting configuration to what it already should be.
2. Always showing H (internet connection) and at least two bars on signal strength even when there is no signal (accourding to chrome and (stock) dialer app.
3. Loss of signal but pretending there is one (like in 2.) and only regaining signal after reboot.
4. Loss of distance between apps within the appdrawer (more apps per page) until uninstallation of an app (remains normal after reinstall)
5. many app crashes (before and after rooting)
6. sometimes notification led keeps blinking after notification was dismissed, sometimes the notification led blinks very fast.
I rooted my device with cf auto root.

Except for 4 &5, yes.

I am glad that I am not alone but does anyone know whats the source of this strange behaviour or how this can be fixed?

In a case like this i would go back to stock, make a factory reset and then rooting the N5 again, manually, without using cf auto root.
Rooting manually it's just a good way to understand the android OS, and how it's made, imho.

Is there a good low-risk way (manual/tutorial) to manually root without a custom rom and custom recovery (CWM/TWRP) ?
Because besides root access I want to stay as close as possible to stock.

Nik_B said:
Is there a good low-risk way (manual/tutorial) to manually root without a custom rom and custom recovery (CWM/TWRP) ?
Because besides root access I want to stay as close as possible to stock.
Click to expand...
Click to collapse
Wugfresh's toolkit is imho the best and safest way to root and do most changes to all nexus devices. About the only difficult you may experience is usb driver/connectivity issues. The usb driver guides are well documented and easy to follow. It's no different than the standard adb usb drivers. Most have no issues, but that is the only thing that can cause problems with adb or Wugfresh's toolkit.
Read through Wugfresh's forum topic to acquaint yourself with mtp/ptp and driver installation and you should breeze through using his toolkit.
Sent from my Apple ] [e using ProTERM 2.2

Nik_B said:
Is there a good low-risk way (manual/tutorial) to manually root without a custom rom and custom recovery (CWM/TWRP) ?
Because besides root access I want to stay as close as possible to stock.
Click to expand...
Click to collapse
custom recoveries do not prevent the OTA.. plus you can just fastboot boot recovery whateverrecovery.img
i blame your problems on the CF-autoroot as i have none of the symptoms you describe.

Looking into the script chainfire offers shows me that there are only 2 commands executed.
the
fastboot oem unlock - command is clear to me that it unlocks the bootloader
but i have some questions about the second one: fastboot boot image\CF-Auto-Root-hammerhead... ...nexus5.img
Am I correct assuming that this command tells the bootloader to start this image instead of the regular android (once?)
which modifies "something" within the "original" android os (image)?
If yes, can somebody tell me?
Is the only modification made there the mount configuration of the system partition and/or user settings?
Is a documentation for such internal matters of rooting somewhere out there?
yeah I know I have lots of questions and yes I am very curious.
Thanks in advance

Nik_B said:
Looking into the script chainfire offers shows me that there are only 2 commands executed.
the
fastboot oem unlock - command is clear to me that it unlocks the bootloader
but i have some questions about the second one: fastboot boot image\CF-Auto-Root-hammerhead... ...nexus5.img
Am I correct assuming that this command tells the bootloader to start this image instead of the regular android (once?)
which modifies "something" within the "original" android os (image)?
If yes, can somebody tell me?
Is the only modification made there the mount configuration of the system partition and/or user settings?
Is a documentation for such internal matters of rooting somewhere out there?
yeah I know I have lots of questions and yes I am very curious.
Thanks in advance
Click to expand...
Click to collapse
unless someone looks into the boot image CF has setup, there's no way to tell what his image does.
thats why its easiest to just boot a custom recovery and then flash supersu.zip, yet a lot of people want to just use toolkits cause "its easier" but when you do use a toolkit, you end up with issues.

DreamLinker said:
In a case like this i would go back to stock, make a factory reset and then rooting the N5 again, manually, without using cf auto root.
Rooting manually it's just a good way to understand the android OS, and how it's made, imho.
Click to expand...
Click to collapse
Go with this guy.

As soon as I read your thread title, I knew you rooted using an "auto root". Rooting a device is actually very simple, just takes a few minutes of your time to research the steps. As long as you have 10 minutes, a USB cable and a Windows Computer, it should be easy and result in a errorless experience.

Zepius said:
unless someone looks into the boot image CF has setup, there's no way to tell what his image does.
thats why its easiest to just boot a custom recovery and then flash supersu.zip, yet a lot of people want to just use toolkits cause "its easier" but when you do use a toolkit, you end up with issues.
Click to expand...
Click to collapse
I already know that. Maybe my question was not correct.
What I wanna know is what happens when i flash a custom recovery, root my device and so on in the background
and what are necessary steps to such actions?
Because I would like to do all those actions on my own. (for example make my own image to boot for rooting)
But I won't unless I know exactly WHAT I am doing.
Hope this for wording made my intentions clearer. (Sorry I am not that good in English)

Nik_B said:
I already know that. Maybe my question was not correct.
What I wanna know is what happens when i flash a custom recovery, root my device and so on in the background
and what are necessary steps to such actions?
Because I would like to do all those actions on my own. (for example make my own image to boot for rooting)
But I won't unless I know exactly WHAT I am doing.
Hope this for wording made my intentions clearer. (Sorry I am not that good in English)
Click to expand...
Click to collapse
fastboot boot recovery recovery.img - this just boots into the recovery once, but leaves the stock recovery as the recovery that is written to the device
when you flash supersu.zip what it does is execute a script that places the su binary in /data/xbin i believe and gives it the proper permissions, and also places supersu app on your phone.
you do not need to make your own boot image, or anything of the sort.

The root process is not capable of causing any of these issues. Root using wugfresh is the exact same as using auto root and both of these are the same as manually doing it yourself. None of them can cause visual changes or signal loss alone, and the only reason we don't recommend toolkits or auto root is so people don't get comfortable with the idea that they don't need to know fastboot commands in the event that they boot loop, etc.
Sent from my Nexus 5 using Tapatalk

joshnichols189 said:
The root process is not capable of causing any of these issues. Root using wugfresh is the exact same as using auto root and both of these are the same as manually doing it yourself. None of them can cause visual changes or signal loss alone, and the only reason we don't recommend toolkits or auto root is so people don't get comfortable with the idea that they don't need to know fastboot commands in the event that they boot loop, etc.
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Do I understand you correctly that neither wugfresh nor auto root are causing the problems in your eyes. I´m just curious because many people including me used Chainfire´s auto root but not all of them are reporting problems. In my case the Nex5 seems to forget already set default apps e.g. for tapatalk links, urls etc.
Cheers, T.

Htc one m8 - im 70 and rooting this phone on my bucket list

Ok my friends, my name is ska, im 70 yrs old and if i dont type in caps, i cant see what i am typing. I would like to correctly root my phone and unroot it later if need be, before i die and so i have come here for assistance. Although i have worked in multiple engineering fields, i no longer have the mental capability to comprehend or follow any rooting instructions unless they were written for a 6 yr old. Getting old is no fun so dont do it.
Can anyone slow it down a few gears and help me with this bucket list item?
Here is what i have:
Htc one m8(metal)
originally verizon now has straight talk sim
model number: Htc6525lvw
imei: 990 004 998 964 591
android version 5.0.1
htc sense version 6.0
software number 4.17.605.9
htc sdk api level 6.55
it took me 21 minutes to type out this information. Which i will never get back. I just want to have a outta sight phone to show off at bingo and use it as an ice breaker on dance nights.

I love this thread and really hope you can figure it out!
You'll need a few things to accomplish this. First you'll need to get s-off (which I explain below), then you get root access, and finally you install a custom recovery. Once that's done, you're good to go, and can install whatever custom ROM or flashy modifications you want without worry that you'll permanently ruin your phone. Here's a list of things you'll need to do it: KingRoot app, Sunshine app ($25! No way around this...), working Android Device Bridge (ADB) connection to a PC.
Note, rooting your phone (up to the custom recovery) will not erase any of your user data, however further changes (such as flashing a new ROM) likely will, so you'll want to back up everything.
s-on/off: This refers to the security setting of the phone. By default, the phone comes s-on, which protects access to reserved memory and prevents you from rooting your phone. You'll need to change this to s-off first. Once done though, it'll be s-off for good. There are ways to "return to stock" and set it back to s-on, or at least appear as such to a level 1 tech.
First thing you're going to want to do is get ADB working on your computer and ensure you can communicate with and control your phone from the ADB command line. This is arguably the hardest step for a lay person. Detailed instructions on how to get that working can be found here.
Once you can see your phone in ADB and have ensured that's working, you'll want to download the KingRoot app and Sunshine app to your phone using the sites I've linked. KingRoot will be used to get temporary root access to your phone. Once you get tempRoot, if you reboot your phone, you'll have to do it again. Temporary root access is required for Sunshine to do it's thing and set your phone to s-off. Once you have s-off you're essentially done, and the last bit of work is to install the custom recovery and then any custom ROMs or modifications you'll want.
So you have ADB working and downloaded the two apps above. Lets get started.
First, launch KingRoot on your phone, and let it do it's magic trying to get you temporary root access. It'll likely fail a few times, but just keep doing it again until it works.
Once KingRoot says you have root, run Sunshine. It'll evaluate your phone and check if it has root access. If all is well, it'll prompt you to go pay $25 for the app, and will reboot your phone.
Once the phone has rebooted, launch KingRoot again and check to see if you still have tempRoot. You'll likely need to re-run KingRoot a few times until it gets root again.
Now that you have tempRoot again, and have paid the $25, go ahead and run Sunshine again. This time, it'll know you're ready to go, so let it run and it'll set your phone to s-off and reboot when it's done.
At this point, you've broken the man's lock over your phone! Go you!
The last step is to install a custom recovery, I suggest TWRP, which will allow you to backup and restore your phone, and also install things like a custom ROM. Details of how to install TWRP can be found here. You'll be using the ADB to push the code to your phone which is why we set it up and tested it first.
Once TWRP is installed, I recommend making a backup of your phone so you don't lose any information. You can do this in TWRP.
As a final step, and a way to show off your technological prowess, you can install a custom ROM. a whole forum of options and detailed explanations on how to install them can be found here. Some retain the same look and feel you're used to, while others use different user interfaces to offer a modified experience. Review the options and feel free to ask questions!
Good luck!

Hope you get this done, I will help in anyway I can.
You shouldn't need kingroot anymore, just download the sunshine app (http://theroot.ninja) to your device, install it and follow the steps.

I was 68 when I did mine. Just read here and follow the instructions.

Alllllrightttttty then !!!! When can you come over and do it>????
drumz0rz said:
I love this thread and really hope you can figure it out!
You'll need a few things to accomplish this. First you'll need to get s-off (which I explain below), then you get root access, and finally you install a custom recovery. Once that's done, you're good to go, and can install whatever custom ROM or flashy modifications you want without worry that you'll permanently ruin your phone. Here's a list of things you'll need to do it: KingRoot app, Sunshine app ($25! No way around this...), working Android Device Bridge (ADB) connection to a PC.
Note, rooting your phone (up to the custom recovery) will not erase any of your user data, however further changes (such as flashing a new ROM) likely will, so you'll want to back up everything.
s-on/off: This refers to the security setting of the phone. By default, the phone comes s-on, which protects access to reserved memory and prevents you from rooting your phone. You'll need to change this to s-off first. Once done though, it'll be s-off for good. There are ways to "return to stock" and set it back to s-on, or at least appear as such to a level 1 tech.
First thing you're going to want to do is get ADB working on your computer and ensure you can communicate with and control your phone from the ADB command line. This is arguably the hardest step for a lay person. Detailed instructions on how to get that working can be found here.
Once you can see your phone in ADB and have ensured that's working, you'll want to download the KingRoot app and Sunshine app to your phone using the sites I've linked. KingRoot will be used to get temporary root access to your phone. Once you get tempRoot, if you reboot your phone, you'll have to do it again. Temporary root access is required for Sunshine to do it's thing and set your phone to s-off. Once you have s-off you're essentially done, and the last bit of work is to install the custom recovery and then any custom ROMs or modifications you'll want.
So you have ADB working and downloaded the two apps above. Lets get started.
First, launch KingRoot on your phone, and let it do it's magic trying to get you temporary root access. It'll likely fail a few times, but just keep doing it again until it works.
Once KingRoot says you have root, run Sunshine. It'll evaluate your phone and check if it has root access. If all is well, it'll prompt you to go pay $25 for the app, and will reboot your phone.
Once the phone has rebooted, launch KingRoot again and check to see if you still have tempRoot. You'll likely need to re-run KingRoot a few times until it gets root again.
Now that you have tempRoot again, and have paid the $25, go ahead and run Sunshine again. This time, it'll know you're ready to go, so let it run and it'll set your phone to s-off and reboot when it's done.
At this point, you've broken the man's lock over your phone! Go you!
The last step is to install a custom recovery, I suggest TWRP, which will allow you to backup and restore your phone, and also install things like a custom ROM. Details of how to install TWRP can be found here. You'll be using the ADB to push the code to your phone which is why we set it up and tested it first.
Once TWRP is installed, I recommend making a backup of your phone so you don't lose any information. You can do this in TWRP.
As a final step, and a way to show off your technological prowess, you can install a custom ROM. a whole forum of options and detailed explanations on how to install them can be found here. Some retain the same look and feel you're used to, while others use different user interfaces to offer a modified experience. Review the options and feel free to ask questions!
Good luck!
Click to expand...
Click to collapse
WOW THE LAST TIME I HAVE HAD MY MIND BLOWN LIKE THIS WAS BY A YOUNG LADY IN KOREA. I GUESS MY NEXT QUESTION IS WHAT IN SAM HILL ARE YOU TALKING ABOUT ? I'M GOING TO ATTEMPT TO FOLLOW YOUR INSTRUCTIONS BUT I THINK THERE IS A GOOD CHANCE I'M GONNA BREAK A HIP IF I TRY TWRPING.!!! AS SOON AS MY NIECE GETS HERE TO TAKE ME TO WALMART TO GET SOME PAPER FOR MY PRINTING UNIT. I WILL PRINT ALL THIS OUT AND START READING. I'M ONLY GOOD FOR ABOUT 5 PAGES OF EASY READING BEFORE I NOD OUT ONLY TO BE WOKEN UP BY THE IMPACT OF MY HEAD ON THE KEYBOARD. HAD TO WALK AROUND WITH GHBNM IMPRINTED ON MY HEAD FOR A WEEK LAST TIME. I'LL KEEP YOU ABREAST ON MY PROGRESS. THANK YOU FOR ALL THIS INFO AND YOUR QUICK RESPONSE ALTHOUGH I'M NOT TO SURE OF MY ABILITY TO COMPREHEND ANY OF IT.
THOUGHT IT WAS GOING TO BE LIKE MY TOASTER. PUT BREAD IN CLICK ONE BUTTON WAIT AND DING ALL DONE AND NOW HAVE YUMMY TOAST. to be continued........

To make this super simple here are the steps:
1) http://theroot.ninja/download.html (Do the first link and after you finish that do the second.)
2) At this point you could potentially go to the app store, download TWRP which is a recovery program that is almost like a computer bios would be on a computer. Once you have that you could install it after selecting your phone and the TWRP version you want, I would select 2.8.0.0 as I had issues when I tried to flash higher the first time.
3) if that doesn't work you will need to install TWRP via Fastboot the directions for which are here:
https://twrp.me/devices/htconem8gsm.html
You can just put your phone in Fastboot mode and in a terminal on your computer that your phone is attached to type:
"fastboot devices" to make sure your phone is being seen.
"fastboot flash recovery twrp.img" to flash TWRP.
"fastboot reboot" to reboot the phone.
4) Here's the hardest step if you can't install TWRP from the app, installing ADB and Fastboot but just go to Youtube and look up some videos on that. There are some more details involved but you can ask when you get this done as this is all you'll need to install the custom ROMs.

Throttled to a halt in two ways is taking its tole on my project
********could not post with quote due to some error about posting 10 times.......something....yada...yada !!*******
Well gents, my carrier has throttled my speed so slow that it feels like I'm on dial-up in Bedrock. Looking at all those Utube videos and printing out instructions ate up 5 Gb in 3 days. So to make downloading the programs I need "time out" before they can be fully downloaded. But I'm still at. So bear with me. Did I mention that I got throttled? Not only by my carrier, but my doctor had to one up my carrier by informing me that I had a heart attack while shopping for print paper with my niece. I think I had a few more when she was driving me to the ER. So I'm a bit slower this week, but I still at it. Thanks for everyones help thus far. I better get to this before it gets to me.

New to Linux, wanting to root and or flash, Xperia Z5 Android 6.0.1

Hello, this is my first post on XDA forums so take it easy on me. Recently I've started taking interest in rooting my Xperia Z5. However I don't really know much at all about Linux, and I've never rooted an android device before. I am actually a coder, in fact I'm using a laptop with a HEAVILY modded version of Win10, and with several apps of my own. I've only recently, about a few months ago, bought a decent android phone. I got the Xperia Z5 off eBay for a good price, brand new for a couple hundred bucks. I'm interested in slowly learning basic coding and hacking on android, so I figured I'd go with the first major step and getting it rooted so I can actually mod the thing. The operating system is nice, doesn't have much bloatware, but I'd like to flash a new ROM on it. I've dug around a bit, and I've seen a few root and flash methods, but I really don't have any idea which one is trusted, or which would be the most stable option. I figured my best option would be to signup here, and ask for some advice. I saw ROMX here on the forums, and it looked very promising. But since I'm new to all this, I thought it would be wise for me to ask for advice on where to start what what would be a good rom to flash. I have the E6603 Model, Android 6.0.1, with the April 1, 2016 security patch. And yes, I do fully understand the risks and dangers as well as security concerns of rooting, and flashing. But to be honest, I probably do far more dangerous things on a weekly basis. I thank you all for your time, any help is appreciated.

spynathan said:
Hello, this is my first post on XDA forums so take it easy on me. Recently I've started taking interest in rooting my Xperia Z5. However I don't really know much at all about Linux, and I've never rooted an android device before. I am actually a coder, in fact I'm using a laptop with a HEAVILY modded version of Win10, and with several apps of my own. I've only recently, about a few months ago, bought a decent android phone. I got the Xperia Z5 off eBay for a good price, brand new for a couple hundred bucks. I'm interested in slowly learning basic coding and hacking on android, so I figured I'd go with the first major step and getting it rooted so I can actually mod the thing. The operating system is nice, doesn't have much bloatware, but I'd like to flash a new ROM on it. I've dug around a bit, and I've seen a few root and flash methods, but I really don't have any idea which one is trusted, or which would be the most stable option. I figured my best option would be to signup here, and ask for some advice. I saw ROMX here on the forums, and it looked very promising. But since I'm new to all this, I thought it would be wise for me to ask for advice on where to start what what would be a good rom to flash. I have the E6603 Model, Android 6.0.1, with the April 1, 2016 security patch. And yes, I do fully understand the risks and dangers as well as security concerns of rooting, and flashing. But to be honest, I probably do far more dangerous things on a weekly basis. I thank you all for your time, any help is appreciated.
Click to expand...
Click to collapse
http://forum.xda-developers.com/xperia-z5/general/guide-rooting-unlocking-bootloader-t3354307
there is this which i followed to root my Z5 but with marshamall you do have to have a unlocked bootloader so you can use systemless root, it isnt neccisary to downgrade and backup your DRM but it is advised since sony doesnt seemingly like wanting to repair phones with missing DRM
basic how to:
- Download flashtool and a FTF of your choice
- use flashtool the extract the kernel.sin using tools > sin extractor (you will have to open the FTF file in winrar or something like to copy it)
~ you should get a kernel.elf when extracted
you can then use rootkernel to repack the kernel with a recovery menu like twrp and also disable some system verification stuff that will prevent things from working or the phone booting
this is when you need a unlocked bootloader
- from there you can flash your kernel and boot the device and flash superSU systemless (from the recovery menu )unless you havent downloaded that already
~ you can get to the recovery menu by pressing volume up while the yellow LED shows up on the bootsplash
i may have missed some stuff but that guide I linked has everything i explained here ^ this above is how ive rooted my phone and re-rooted when needed

Envious_Data said:
http://forum.xda-developers.com/xperia-z5/general/guide-rooting-unlocking-bootloader-t3354307
there is this which i followed to root my Z5 but with marshamall you do have to have a unlocked bootloader so you can use systemless root, it isnt neccisary to downgrade and backup your DRM but it is advised since sony doesnt seemingly like wanting to repair phones with missing DRM
basic how to:
- Download flashtool and a FTF of your choice
- use flashtool the extract the kernel.sin using tools > sin extractor (you will have to open the FTF file in winrar or something like to copy it)
~ you should get a kernel.elf when extracted
you can then use rootkernel to repack the kernel with a recovery menu like twrp and also disable some system verification stuff that will prevent things from working or the phone booting
this is when you need a unlocked bootloader
- from there you can flash your kernel and boot the device and flash superSU systemless (from the recovery menu )unless you havent downloaded that already
~ you can get to the recovery menu by pressing volume up while the yellow LED shows up on the bootsplash
i may have missed some stuff but that guide I linked has everything i explained here ^ this above is how ive rooted my phone and re-rooted when needed
Click to expand...
Click to collapse
Awesome thanks! I'll try it first thing tomorrow after work.

Ok so I've gotten everything done, backed up my drm unlocked the bootloader, and what not. Got to the last bit and I can't seem to get fastboot to work, it just says waiting for device. I've tried reinstalling all the drivers a few times, but nothing worked. Flashtool recognized the device, just couldn't get fastboot to recognize it. I'm running windows 10, I've made sure all the drivers are there but still no go. Any help would be greatly appreciated, I'm kinda stuck atm. EDIT, I found a fix for my case. Even though the drivers were installed, for some reason they weren't being read. Anyway all working now, thanks again.

spynathan said:
Ok so I've gotten everything done, backed up my drm unlocked the bootloader, and what not. Got to the last bit and I can't seem to get fastboot to work, it just says waiting for device. I've tried reinstalling all the drivers a few times, but nothing worked. Flashtool recognized the device, just couldn't get fastboot to recognize it. I'm running windows 10, I've made sure all the drivers are there but still no go. Any help would be greatly appreciated, I'm kinda stuck atm. EDIT, I found a fix for my case. Even though the drivers were installed, for some reason they weren't being read. Anyway all working now, thanks again.
Click to expand...
Click to collapse
atleast on windows 10 i found that i had to disable driver signature verifacation and sometimes i had to run command prompt in admin

Beginner in need of help with rooting and some clarification on Magisk/TWRP/recovery

Hello all,
I got my Oneplus6 recently, for the first time using android. I've had an old iPhone for forever.
I like the phone but I'm so far not really happy with the android version (Oreo).
For example: I pick the dark theme from the settings, and my notification tray will stay bright white. I really don't like this. Then I went ahead to try a couple of apps to dim the screen more than the default will allow (it's too bright for my taste). They worked fine, untill I pulled down the notification tray. The contrast feels like staring directly into the sun!
After learning that google now apparently blocks overlays on the notification tray, I figured my only option is to root. Also I would like to use a systemwide adblock and YT Vanced, and maybe some other cool (beginner friendly) things that require a root. However, I would very much like to keep basic functionality, mobile signal, using banking apps, and so on. I don't watch netflix or amazon, only youtube and sometimes twitch, so the L1 and L3 things are not something I worry about.
For the past 5 days or so I've been reading these forums, reddit, and researching the web for information about unlocking,rooting and so on. But I still have a couple of questions, hopefully you experienced users can help a noobie out! I really want to learn.
Currently on these forums, as far as I can see, there are ways of rooting with Magisk and (unofficial) TWRP, the latter also making a custom recovery.
Is this TWRP custom recovery something I need, when I want to keep using OxygenOS? Keep in mind I'm only really looking to apply a black theme on it all, including that blasted notification tray.
If I go with the Magisk root ( https://forum.xda-developers.com/oneplus-6/how-to/oneplus-6-magisk-root-oos-5-1-5-t3794440 ), do I still need a custom recovery? I think that is what TWRP is for. Say I want to remove my root and go back to factory default. Can I do that with the stock recovery?
Is it good to go with the guide I linked, or is it better to use the TWRP method described here: https://forum.xda-developers.com/oneplus-6/how-to/oneplus-6-unlock-bootloader-flash-twrp-t3792643
What are the major differences between them?
Should I wait until an official TWRP is released and unlock/root then?
I'm sorry if these are very silly things to ask. Keep in mind I've only been using an android device for the first time, ever, since a couple of days. I'm okay with tinkering with it while following a guide to make sure I don't brick or anything. Also I've been looking for a complete beginner guide to unlocking and rooting, but all I can seem to find are very outdated guides.
Thank you for taking the time to read!

DampDeceiver said:
Hello all,
I got my Oneplus6 recently, for the first time using android. I've had an old iPhone for forever.
I like the phone but I'm so far not really happy with the android version (Oreo).
For example: I pick the dark theme from the settings, and my notification tray will stay bright white. I really don't like this. Then I went ahead to try a couple of apps to dim the screen more than the default will allow (it's too bright for my taste). They worked fine, untill I pulled down the notification tray. The contrast feels like staring directly into the sun!
After learning that google now apparently blocks overlays on the notification tray, I figured my only option is to root. Also I would like to use a systemwide adblock and YT Vanced, and maybe some other cool (beginner friendly) things that require a root. However, I would very much like to keep basic functionality, mobile signal, using banking apps, and so on. I don't watch netflix or amazon, only youtube and sometimes twitch, so the L1 and L3 things are not something I worry about.
For the past 5 days or so I've been reading these forums, reddit, and researching the web for information about unlocking,rooting and so on. But I still have a couple of questions, hopefully you experienced users can help a noobie out! I really want to learn.
Currently on these forums, as far as I can see, there are ways of rooting with Magisk and (unofficial) TWRP, the latter also making a custom recovery.
Is this TWRP custom recovery something I need, when I want to keep using OxygenOS? Keep in mind I'm only really looking to apply a black theme on it all, including that blasted notification tray.
If I go with the Magisk root ( https://forum.xda-developers.com/oneplus-6/how-to/oneplus-6-magisk-root-oos-5-1-5-t3794440 ), do I still need a custom recovery? I think that is what TWRP is for. Say I want to remove my root and go back to factory default. Can I do that with the stock recovery?
Is it good to go with the guide I linked, or is it better to use the TWRP method described here: https://forum.xda-developers.com/oneplus-6/how-to/oneplus-6-unlock-bootloader-flash-twrp-t3792643
What are the major differences between them?
Should I wait until an official TWRP is released and unlock/root then?
I'm sorry if these are very silly things to ask. Keep in mind I've only been using an android device for the first time, ever, since a couple of days. I'm okay with tinkering with it while following a guide to make sure I don't brick or anything. Also I've been looking for a complete beginner guide to unlocking and rooting, but all I can seem to find are very outdated guides.
Thank you for taking the time to read!
Click to expand...
Click to collapse
Look in the forums of how to unlock, root and install TWRP recovery. I actually enjoy system wide black themes so this is what I would recommend.
You need to unlock your bootloader if you had not done so already. In the forum I suggested, under the rooting section, you need to grab the bootable Magisk file. You will have to put your OP6 into fastboot mode and open up a command prompt and type- fastboot boot "name of img file" to boot using that img file.
All these instructions are in the forum regarding unlocking and rooting the device. If you are only interested in obtaining a system wide black theme while also keeping everything in good shape, you need to unlock your bootloader and root with Magisk. Do not worry about installing TWRP as you do not need this for your certain needs. After you root with Magisk, you can use an app call Adaway to block ads. To obtain a system wide black/dark theme, you need to go to the Google Play Store and download an app called "Substratum" after you obtain root. It will only work with root. Also download an app called "Swift Black". This is the theme you will be applying.
I would look at the forums again, the one I am talking about is up there at the top of the page when you look at the OP6 forums. It is clearly labeled for unlocking, rooting and installing TWRP recovery. You are only interested in unlocking your bootloader and installing Magisk, that's it. It has all the instructions you need. Once you are there, install the apps above from the Google Play Store and apply the theme using Substratum. Hope this helps!

DampDeceiver said:
Hello all,
I got my Oneplus6 recently, for the first time using android. I've had an old iPhone for forever.
I like the phone but I'm so far not really happy with the android version (Oreo).
For example: I pick the dark theme from the settings, and my notification tray will stay bright white. I really don't like this. Then I went ahead to try a couple of apps to dim the screen more than the default will allow (it's too bright for my taste). They worked fine, untill I pulled down the notification tray. The contrast feels like staring directly into the sun!
After learning that google now apparently blocks overlays on the notification tray, I figured my only option is to root. Also I would like to use a systemwide adblock and YT Vanced, and maybe some other cool (beginner friendly) things that require a root. However, I would very much like to keep basic functionality, mobile signal, using banking apps, and so on. I don't watch netflix or amazon, only youtube and sometimes twitch, so the L1 and L3 things are not something I worry about.
For the past 5 days or so I've been reading these forums, reddit, and researching the web for information about unlocking,rooting and so on. But I still have a couple of questions, hopefully you experienced users can help a noobie out! I really want to learn.
Currently on these forums, as far as I can see, there are ways of rooting with Magisk and (unofficial) TWRP, the latter also making a custom recovery.
Is this TWRP custom recovery something I need, when I want to keep using OxygenOS? Keep in mind I'm only really looking to apply a black theme on it all, including that blasted notification tray.
If I go with the Magisk root ( https://forum.xda-developers.com/oneplus-6/how-to/oneplus-6-magisk-root-oos-5-1-5-t3794440 ), do I still need a custom recovery? I think that is what TWRP is for. Say I want to remove my root and go back to factory default. Can I do that with the stock recovery?
Is it good to go with the guide I linked, or is it better to use the TWRP method described here: https://forum.xda-developers.com/oneplus-6/how-to/oneplus-6-unlock-bootloader-flash-twrp-t3792643
What are the major differences between them?
Should I wait until an official TWRP is released and unlock/root then?
I'm sorry if these are very silly things to ask. Keep in mind I've only been using an android device for the first time, ever, since a couple of days. I'm okay with tinkering with it while following a guide to make sure I don't brick or anything. Also I've been looking for a complete beginner guide to unlocking and rooting, but all I can seem to find are very outdated guides.
Thank you for taking the time to read!
Click to expand...
Click to collapse
you should totally root it!
This is how I did it!
Note u will break warranty, and unlocking bootloader will completely wipe ur phone(even the storage memory)
Download the following:
https://forum.xda-developers.com/on...ol-tool-one-driversunlocktwrpfactory-t3791316 (install this on computer)
and https://drive.google.com/open?id=15mXZz4OrwRGXz5JCKeYjwukQf0raWnOb
in your phone go to settings> about phone>Select "Build number" 4 times.
Then in Settings>Developer Options> turn on "OEM unlocking", "USB debugging" and for convenience "Advanced rooting".
Click reboot and Select "Bootloader"
Plug your phone to your computer and open the software you installed and click "check device" Then unlock, on your phone you will have to use volume buttons to go up and down and then the power button to select.
(Note, never relock with custom firmware or root on it, recommend u only lock it when 100% stock or u can permanently brick if something happens when ur rooted.)
Now on that software, you had click advanced options and click "Open a free terminal with adb and fastboot privileges".
Extract that zip file and move it to your desktop.
Type: cd "C:\Users\Bradley Gregory\Desktop" or if its in the folder: cd "C:\Users\Bradley Gregory\Desktop\All files for TWRP"
Then type: fastboot flash boot_a twrp.img , (Your using the same twrp.img)
Then again: fastboot flash boot_b twrp.img
After this look at your phone and use the volume buttons till it says recovery and press power button.
If it asks for a password type ur pin in from phone, and change language before pressing checkmark.
Then copy everything from that zip onto ur phone(when ur in the temporary recovery)
Then click install, find file location of where u put your stuff on. bottom right button click (img file) then click "boot.img" then select boot.
Now click the bottom right button to change back to zips.
Flash zips in this order
1. Flash TWRPWorkingInstaller.zip
2. Flash TWRP-BLUE-FIX.zip
3. Flash Root.zip or you will bootloop
after you can reboot your phone. Open magdisk app >settings and under update settings change update channel to beta. then you can go to the app home and install directly the new update.
(optional) in magisk select download and search busybox and click install
Hope this helps!
PM me for any questions!
(don't factory reset with custom boot. also in recovery, u can now make backups of your entire phone if error happens)
I recommend u download this file:
https://forum.xda-developers.com/oneplus-6/how-to/rom-stock-fastboot-roms-oneplus-6-t3796665
if u ever hard brick this will wipe ur phone and make it normal again(wipes internal memory)

Personally, I would hold off on doing anything until we have an official twrp and more development. Right now, the solutions we've got are unforgiving. People are bricking their phones right and left because they missed a step, and the unbricking process is more involved than other android phones at the moment.
Also, before you do anything, I would take a moment to assess your computer literacy and comfort with mucking around in the system files of your devices. If you're used to things that "just work" like on iOS, you may not like what you find once you cross over into modding. If you do enjoy that kind of stuff, good, but the tradeoff for greater freedom is more work in keeping your phone updated and operational.

Don't do it!! Hold off,. I am an old hat, since 2005, and I spent the whole day yesterday fixing the brick that I turned my OnePlus 6 into. It's a pain and very easy to do.
Just wait two weeks.
Sent from my ONEPLUS A6003 using Tapatalk

Personally, I would hold off on doing anything until we have an official twrp and more development. Right now, the solutions we've got are unforgiving. People are bricking their phones right and left because they missed a step, and the unbricking process is more involved than other android phones at the moment.
Click to expand...
Click to collapse
Agree. I've been rooting and modding devices (mostly Oneplus) the last couple of years, but with the OP6 things have changed. A/B partitioning have made it somehow more complicated, at least compared to what I'm used to.
Personally I pulled the trigger anyway, i.e. not waiting for an official version of TWRP. I got TWRP and root with the method described in post 70 here: https://forum.xda-developers.com/showpost.php?p=76633618&postcount=70
If and when you do that too I recommend you to install:
* Adaway (from XDA forum) to get rid of ads
* Substratum theme engine (from Play Store)
And then some Substratum themes:
* Ozone (from Play store) to theme Oneplus OS and apps
* Swift Black (from Play store) to theme other apps
And finally some Magisk modules:
* Youtube Vanced Magisk black themed (from Magisk repo) to get themed You tube, adfree and with picture-in-picture
* Viper4Android FX (from Magisk repo) to get much better audio
* OP_AlwaysOnDisplay_enabler (from OP5T XDA forum) to enable settings for Always On Display (if you want that)
https://www.xda-developers.com/enable-always-on-display-oneplus-6-oneplus-5-5t/
Is this TWRP custom recovery something I need, when I want to keep using OxygenOS? Keep in mind I'm only really looking to apply a black theme on it all, including that blasted notification tray.
Click to expand...
Click to collapse
I strongly recommend you to use a custom recovery (TWRP) if you root and install rooted apps. If you don't it will be difficult or impossible to recover if you get in trouble. For example, it is easy to uninstall Magisk modules or Substratum themes from the recovery in case they cause bootloops. And additionaly you can make full backups of your system in TWRP. A small hint for backups is to copy them to a safe place (computer or USB stick) in case you get into trouble with the internal storage on your phone.

The A/B partitioning has definitely made things more complicated, especially with respect to flashing. I've been rooting and modding here for 5+ years, and I'm taking it very slowly so far. Right now, you can't just fix things with a quick reflash of your rom. Even factory resets can brick you. This is not a phone for noobs at the moment.

iElvis said:
The A/B partitioning has definitely made things more complicated, especially with respect to flashing. I've been rooting and modding here for 5+ years, and I'm taking it very slowly so far. Right now, you can't just fix things with a quick reflash of your rom. Even factory resets can brick you. This is not a phone for noobs at the moment.
Click to expand...
Click to collapse
There is an unbrick tool and fastboot ROMs to recover, but u r right, u just can't screw around with things like we used to due to u need a computer avail even if u bootloop

That, and there are some conflicting instructions flying around and some disagreements amongst the devs about how to do things. I would not want to be starting out with rooting on this phone tbh.

I agree with most posts here.
I've been flashing ever since the HD2 back in the days. I've really spend alot of nights fixing my phones from hard/soft bricks, never actually really broke one though.
But untill there are some stable recovery/root methods, I wouldn't want to start my android rooting experience with this phone right now. As some said, wait a couple of weeks.

Thank you everyone for replying! You've been a great help.
I figure I will wait for the official TWRP and a guide to install it by that time.
Until then I'll keep a close eye on these forums to keep learning. Cheers!

All of these guys are spot on with advice. I too have been doing this for awhile, however this is my first A/B partition phone. You definitely want TWRP. I can't count how many times I've installed a root program or tweaked a system file and messed up my device. Recovery is your friend! Make backups often!! (Once you get TWRP installed of course)

I will wait for TWRP official for sure now, but one last question.
It is possible to unlock the bootloader (that wipes all my data) right now, and not root, right? So I will just unlock it for the future when TWRP official is released and I can root w/o losing all my data?
It's safe to follow a guide to just unlock the bootloader as of right now?
Thanks again! Very much appreciated!!

DampDeceiver said:
I will wait for TWRP official for sure now, but one last question.
It is possible to unlock the bootloader (that wipes all my data) right now, and not root, right? So I will just unlock it for the future when TWRP official is released and I can root w/o losing all my data?
It's safe to follow a guide to just unlock the bootloader as of right now?
Thanks again! Very much appreciated!!
Click to expand...
Click to collapse
This is what I did. Unlock the bootloader to save from data loss later, but no recovery or root until things are a little more understood.

DampDeceiver said:
I will wait for TWRP official for sure now, but one last question.
It is possible to unlock the bootloader (that wipes all my data) right now, and not root, right? So I will just unlock it for the future when TWRP official is released and I can root w/o losing all my data?
It's safe to follow a guide to just unlock the bootloader as of right now?
Thanks again! Very much appreciated!!
Click to expand...
Click to collapse
Yes, you can unlock your bootloader and not root. You're correct that it will erase your data, but once it's unlocked you will be ready to root once official twrp and magisk root comes out.
You'll want to use Magisk because it keeps you compatible with Safety net, has root hide and really good modules as well to add stuff.
If you want a dark theme for now you can download Andromeda from the Play store, and hen substratum. It doesn't need root just some commands from your pc and adb. However it is a few dollars, so if you don't want to pay for that then you can just wait to root. The theme you'll want is swift black, but I use ozone as well. Swift black for some apps to be black theme, but ozone to get a custom accent color and dark theme for OOS quick settings, settings app, etc.

NateDev said:
Yes, you can unlock your bootloader and not root. You're correct that it will erase your data, but once it's unlocked you will be ready to root once official twrp and magisk root comes out.
You'll want to use Magisk because it keeps you compatible with Safety net, has root hide and really good modules as well to add stuff.
If you want a dark theme for now you can download Andromeda from the Play store, and hen substratum. It doesn't need root just some commands from your pc and adb. However it is a few dollars, so if you don't want to pay for that then you can just wait to root. The theme you'll want is swift black, but I use ozone as well. Swift black for some apps to be black theme, but ozone to get a custom accent color and dark theme for OOS quick settings, settings app, etc.
Click to expand...
Click to collapse
That is what i was about to type, use andromeda from play store and use substratum to theme whatever you like.

Unlocking the bootloader is required if you want root and/or custom recovery(TWRP).
Custom recovery is optional and root does not depend on it, nor does custom recovery depend on root either. What custom recovery gives you are mainly two things:
1. More features than a stock recovery.
2. Able to flash unsigned zip.
So if neither of these two really means something to you then you can stay with stock recovery.
The root procedure could be a bit different depends on whether you use a customer recovery or not.
If you do, then the root procedure usually is just as simple as flash a Magisk installation zip.
If you do not use a custom recovery, stay on the stock recovery, then the root procedure is different because the stock recovery does not allow you to flash an unsigned zip. The procedure is:
1. Obtain the stock boot image.
2. Install Magisk Manager and use it to patch the boot image.
3. Boot the phone with the patched boot image(fastboot boot patched_boot.img command), thus you get a temporarily rooted phone. Temporarily means you lost root after reboot because the patched boot image is not actually written to the ROM of your phone.
4. Now on the (temporarily) rooted phone, you have all the power to install the root permanently, by Magisk Manager.