Related
So I have a black Nexus 5 with a capacity of 16GB. The device is only about 4 months old, so I still have it covered with warranty until June 2016. The device is as good as new and I'm very happy with it because everything is so fast and smooth.
Recently I've been thinking about rooting the device for maybe some little extras. For example, I have GTA SA installed but I would like to play it with the Cleo mod to have a little bit more fun. Or maybe I'll install some kind of adblocker so I could enjoy my brand new phone without the annoying gold diggers. Or perhaps I want to hide some apps from my app drawer so it would look neat and organised. Or I would like to install an apk that isn't available for non-rooted devices. Or in case I want to see the battery percentage next to the time display or anything like that.
As you can see I would only want to root it for rather small reasons. I definitely don't want to overclock anything because it already meets my criteria for speed, nor do I want to install any custom ROMs because I really like the pure android experience. So I have a few questions because I'm a total noob at the field of tweaking android:
Is my current data going to be wiped if I would want to root it?
I'm aware of the upcoming Android L release, so would I be able to update it right away (remember, I'm not going to use any custom ROMs) or would I have to unroot and reset everything first?
In case something goes wrong and I want to use my warranty, could any traces be found after I would have unrooted the device? (because rooting voids your warranty, right?)
What would be the top reasons to root the Nexus 5? For example, any features the device should've had but unfortunately hasn't.
And is it actually 100% safe...?
So regarding to the last question... A friend of mine has a rooted Moto G, he made me familiar with rooting and it's probably thanks to him that I'm considering it. Everything was going well but there were a few times that he woke up and his phone wasn't worth more than a brick. Apparently, it was because of some ROM he installed. This probably won't affect me in any way because like I said, I'm not going to install any custom ROMs, but my friend expected everything to be normal while it wasn't. He probably did everything like it should be done but then he suddenly woke up with a brick next to his head. So apparently, even if you do everything exactly like they tell you to do it, there's still a slight chance that it's going to end up badly, right?
So basically, I'm considering rooting my device but I'm still not sure what I would have to do because there are lots of tutorials and everything is quite confusing and I have some questions. All the help would be greatly appreciated, thanks in advance!
root/unlockbootloader/install twrp&busybox no data loss
root/unlockbootloader/install twrp&busybox no data loss without P.C, okay here we go mod's remove if you think it's not helping. download towelroot by geohot,now the rest from playstore, es file exploer,super su,busybox,reboot app,nexus unlock bootloader,
make sure you have security unknowen sources ticked and verify apps unticked.
download towelroot from chrome with es file exploer open and install hit make it rain tab, next install busybox,next install super su app.unlockbootloader with in the app.,install twrp and auto install recovery for hammerhead from twrp, now you should have full root after reboot.super user and busybox unlocked bootloader and twrp installed, and you know what the reboot app is for . no data loss and without a P.C, or you could use fastboot install just look in Q&A, kind regard's joe hope this help's.
Spaceblow said:
Is my current data going to be wiped if I would want to root it?
Click to expand...
Click to collapse
Yep; when you unlock bootloader of your device (before root), all of data will be wiped.
Spaceblow said:
I'm aware of the upcoming Android L release, so would I be able to update it right away (remember, I'm not going to use any custom ROMs) or would I have to unroot and reset everything first?
Click to expand...
Click to collapse
Nope. When you upgrade to Android L, it might be overwrite existing system clearly.
Spaceblow said:
In case something goes wrong and I want to use my warranty, could any traces be found after I would have unrooted the device? (because rooting voids your warranty, right?)
Click to expand...
Click to collapse
We are using Google Nexus. Just revert with Nexus Factory Image.
http://developers.google.com/android/nexus/images
Spaceblow said:
What would be the top reasons to root the Nexus 5? For example, any features the device should've had but unfortunately hasn't.
Click to expand...
Click to collapse
In my case, to connect NTFS filesystem.
Spaceblow said:
And is it actually 100% safe...?
Click to expand...
Click to collapse
Maybe, but it's at your own risk.
Jongmin Kim said:
Yep; when you unlock your device (before root), all of data will be wiped.
Nope. When you upgrade to Android L, it might be overwrite existing system clearly.
No. We are using Google Nexus. Just revert with Nexus Factory Image.
http://developers.google.com/android/nexus/images
In my case, to connect NTFS filesystem.
Maybe, but it's at your own risk.
English is too difficult... I'm trying to understand right now.
Click to expand...
Click to collapse
root and then unlock bootloader with the app from playstore. has to be this way. regard's p.s no data wiped ,
Spaceblow said:
So I have a black Nexus 5 with a capacity of 16GB. The device is only about 4 months old, so I still have it covered with warranty until June 2016. The device is as good as new and I'm very happy with it because everything is so fast and smooth.
Click to expand...
Click to collapse
First of all:
Lethargy said:
I think OP got his question reversed. Should be:
"Why buy a Nexus 5 if you're not going to root?"
:angel:
Click to expand...
Click to collapse
Spaceblow said:
So I have a few questions because I'm a total noob at the field of tweaking android:
Is my current data going to be wiped if I would want to root it?
I'm aware of the upcoming Android L release, so would I be able to update it right away (remember, I'm not going to use any custom ROMs) or would I have to unroot and reset everything first?
In case something goes wrong and I want to use my warranty, could any traces be found after I would have unrooted the device? (because rooting voids your warranty, right?)
What would be the top reasons to root the Nexus 5? For example, any features the device should've had but unfortunately hasn't.
And is it actually 100% safe...?
Click to expand...
Click to collapse
1. Unlocking the bootloader is what wipes the data partition, not root access.
2. Don't bother with OTAs to update, they're too much of a bother to try to get to work, when you can just flash factory images/zip, most likely before you even get the OTA pushed to you.
3. Depends where you bought it from. If you got it off the Play Store, then Google does not care about the software you have on your device as long as it's a legitimate manufacturing fault covered by the warranty. You can RMA to Google with a custom ROM and kernel if you wanted to. If you bought it from elsewhere, You'll have to send it to LG for repair. It's possible to reflash factory images and reset the tamper flag, there isn't anything else on the Nexus 5 that will tell LG anything. The easiest way is using LG Flashtool, which can be found in the first link of my signature. If your device is completely dead however, it doesn't matter since LG wouldn't be able to boot it up.
4. Root access is simply root access. You get access to /system, and therefore can use root apps and other modifications.
5. The root process itself is pretty much 100% safe. The Nexus 5 is really, really hard to brick, unless you flash something that isn't meant for your device or something similar, so user error is the only risk in the process. Software-wise, of course root access comes at some form of a security risk. Just be sure of what apps you're granting root access to and you should have no problem.
Spaceblow said:
So regarding to the last question... A friend of mine has a rooted Moto G, he made me familiar with rooting and it's probably thanks to him that I'm considering it. Everything was going well but there were a few times that he woke up and his phone wasn't worth more than a brick. Apparently, it was because of some ROM he installed. This probably won't affect me in any way because like I said, I'm not going to install any custom ROMs, but my friend expected everything to be normal while it wasn't. He probably did everything like it should be done but then he suddenly woke up with a brick next to his head. So apparently, even if you do everything exactly like they tell you to do it, there's still a slight chance that it's going to end up badly, right?
Click to expand...
Click to collapse
Most likely user error, or simply because a Moto device could be locked down more (which also makes it riskier and harder to restore) and not as easy to develop for. The Nexus 5 is one of the hardest devices to brick (again, excluding user error), and if you have any issues it would either be user error or a bug in the ROM/kernel.
Spaceblow said:
So basically, I'm considering rooting my device but I'm still not sure what I would have to do because there are lots of tutorials and everything is quite confusing and I have some questions. All the help would be greatly appreciated, thanks in advance!
Click to expand...
Click to collapse
Check out the first link of my signature and read some threads before proceeding blindly.
There are ways to gain root access without unlocking the bootloader and without a PC as mentioned above, but it's recommended to do it the traditional way by backing up your internal storage to a PC first and using fastboot. Those methods are useful for other devices that are more locked down. This is a Nexus device, it's better to do it properly.
Lethargy said:
First of all:
1. Unlocking the bootloader is what wipes the data partition, not root access.
2. Don't bother with OTAs to update, they're too much of a bother to try to get to work, when you can just flash factory images/zip, most likely before you even get the OTA pushed to you.
3. Depends where you bought it from. If you got it off the Play Store, then Google does not care about the software you have on your device as long as it's a legitimate manufacturing fault covered by the warranty. You can RMA to Google with a custom ROM and kernel if you wanted to. If you bought it from elsewhere, You'll have to send it to LG for repair. It's possible to reflash factory images and reset the tamper flag, there isn't anything else on the Nexus 5 that will tell LG anything. The easiest way is using LG Flashtool, which can be found in the first link of my signature. If your device is completely dead however, it doesn't matter since LG wouldn't be able to boot it up.
4. Root access is simply root access. You get access to /system, and therefore can use root apps and other modifications.
5. The root process itself is pretty much 100% safe. The Nexus 5 is really, really hard to brick, unless you flash something that isn't meant for your device or something similar, so user error is the only risk in the process. Software-wise, of course root access comes at some form of a security risk. Just be sure of what apps you're granting root access to and you should have no problem.
Most likely user error, or simply because a Moto device could be locked down more (which also makes it riskier and harder to restore). The Nexus 5 is one of the hardest devices to brick (again, excluding user error), and if you have any issues it would either be user error or a bug in the ROM/kernel.
Check out the first link of my signature and read some threads before proceeding blindly.
There are ways to gain root access without unlocking the bootloader and without a PC as mentioned above, but it's recommended to do it the traditional way by backing up your internal storage to a PC first and using fastboot. Those methods are useful for other devices that are more locked down. This is a Nexus device, it's better to do it properly.
Click to expand...
Click to collapse
lol yeah i have to agree with you, but i find this help's when on the go,
joecool666 said:
lol yeah i have to agree with you, but i find this help's when on the go,
Click to expand...
Click to collapse
If you don't have access to a PC, or you're using a locked-down Samsung/HTC/Moto/Sony/whatever device, then sure, go ahead and use the exploit methods.
But if you do have access to a PC, and it's a Nexus device, just do it properly, it'll cause fewer possible issues.
Lethargy said:
If you don't have access to a PC, or you're using a locked-down Samsung/HTC/Moto/Sony/whatever device, then sure, go ahead and use the exploit methods.
But if you do have access to a PC, and it's a Nexus device, just do it properly, it'll cause fewer possible issues.
Click to expand...
Click to collapse
i do use my p.c and lg flashtool and fastboot.just incase lol.and it is the better way of doing it, p.s when OTG rooting don't forget to bring the XDA app.
joecool666 said:
root and then unlock bootloader with the app from playstore. has to be this way. regard's p.s no data wiped ,
Click to expand...
Click to collapse
You mean Towelroot? I'm also considering this option because it would be nice to keep all my data.
Lethargy said:
First of all:
1. Unlocking the bootloader is what wipes the data partition, not root access.
2. Don't bother with OTAs to update, they're too much of a bother to try to get to work, when you can just flash factory images/zip, most likely before you even get the OTA pushed to you.
3. Depends where you bought it from. If you got it off the Play Store, then Google does not care about the software you have on your device as long as it's a legitimate manufacturing fault covered by the warranty. You can RMA to Google with a custom ROM and kernel if you wanted to. If you bought it from elsewhere, You'll have to send it to LG for repair. It's possible to reflash factory images and reset the tamper flag, there isn't anything else on the Nexus 5 that will tell LG anything. The easiest way is using LG Flashtool, which can be found in the first link of my signature. If your device is completely dead however, it doesn't matter since LG wouldn't be able to boot it up.
4. Root access is simply root access. You get access to /system, and therefore can use root apps and other modifications.
5. The root process itself is pretty much 100% safe. The Nexus 5 is really, really hard to brick, unless you flash something that isn't meant for your device or something similar, so user error is the only risk in the process. Software-wise, of course root access comes at some form of a security risk. Just be sure of what apps you're granting root access to and you should have no problem.
Most likely user error, or simply because a Moto device could be locked down more (which also makes it riskier and harder to restore) and not as easy to develop for. The Nexus 5 is one of the hardest devices to brick (again, excluding user error), and if you have any issues it would either be user error or a bug in the ROM/kernel.
Check out the first link of my signature and read some threads before proceeding blindly.
There are ways to gain root access without unlocking the bootloader and without a PC as mentioned above, but it's recommended to do it the traditional way by backing up your internal storage to a PC first and using fastboot. Those methods are useful for other devices that are more locked down. This is a Nexus device, it's better to do it properly.
Click to expand...
Click to collapse
This is some great information, thank you very much! So in case I would want to do it manually, this thread has everything I need (in combination with the 15 seconds ADB Installer)?
Spaceblow said:
This is some great information, thank you very much! So in case I would want to do it manually, this thread has everything I need (in combination with the 15 seconds ADB Installer)?
Click to expand...
Click to collapse
Yep. :good: I also recommend using TWRP instead of CWM as your recovery. PhilZ Touch is also another good alternative, but it is no longer maintained and probably won't work for Lollipop's default encryption.
Latest SuperSU is located here, flashable in a custom recovery.
Lethargy said:
Yep. :good: I also recommend using TWRP instead of CWM as your recovery. PhilZ Touch is also another good alternative, but it is no longer maintained and probably won't work for Lollipop's default encryption.
Latest SuperSU is located here, flashable in a custom recovery.
Click to expand...
Click to collapse
Thanks for helping me but I used Towelroot and it works flawlessly!
Spaceblow said:
Thanks for helping me but I used Towelroot and it works flawlessly!
Click to expand...
Click to collapse
Cool. :good:
Even though you now have root access, I recommend using Bootunlocker or whatever app to unlock the bootloader from within Android (which doesn't wipe), then flashing a custom recovery with fastboot while in the bootloader anyways.
Why?
If something goes wrong and your phone doesn't boot, you'll have no choice but to unlock the bootloader WITH a wipe using fastboot, then flash a custom recovery or reflash factory images, unless you've done the above, in which case you can dirty-flash (no wipe) a stock ROM zip downloadable here. :angel:
back up
Spaceblow said:
Thanks for helping me but I used Towelroot and it works flawlessly!
Click to expand...
Click to collapse
make sure you make a back up back up most important,regard's joe
To be clear, the *whole* phone including your sdcard partition will be wiped so make sure you back up before unlocking your bootloader. I would use an app like ES File Explorer and copy all your files to Dropbox or Google Drive if you dont have a computer but you'll need a computer anyway.
Sent from my Nexus 5 using XDA Free mobile app
MrObvious said:
To be clear, the *whole* phone including your sdcard partition will be wiped
Click to expand...
Click to collapse
If we want to be clear, we should also be accurate. The *whole* phone is not wiped. The /data partition is wiped, which includes /data/app (where user apps are stored) /data/data (where user settings and app data is stored) and /data/media (where /sdcard data is stored)
Lethargy said:
Cool. :good:
Even though you now have root access, I recommend using Bootunlocker or whatever app to unlock the bootloader from within Android (which doesn't wipe), then flashing a custom recovery with fastboot while in the bootloader anyways.
Why?
If something goes wrong and your phone doesn't boot, you'll have no choice but to unlock the bootloader WITH a wipe using fastboot, then flash a custom recovery or reflash factory images, unless you've done the above, in which case you can dirty-flash (no wipe) a stock ROM zip downloadable here. :angel:
Click to expand...
Click to collapse
Thanks for the tip but then I'll be unable to receive OTA updates unless I restore everything, including everything being wiped, right?
joecool666 said:
make sure you make a back up back up most important,regard's joe
Click to expand...
Click to collapse
By using Titanium Backup?
Spaceblow said:
Thanks for the tip but then I'll be unable to receive OTA updates unless I restore everything, including everything being wiped, right?
Click to expand...
Click to collapse
All guides and info threads are in my signature. One such INFO thread is OTA help-desk, which explains that you can receive OTA with custom recovery, however there are extra steps.
However, please let me explain 1 thing. OTA is the ultimate noob move. Only root-noobs receive OTA updates. They are the most inconvenient method of updating your OS if you are rooted. Long before you even receive the OTA update, there will be a pre-rooted flashable.zip that can be flashed via recovery.
noobs will often say "but..but..but I wont have to wipe if I accept an OTA"... Little do they know... Even after an official OTA, things screw up. Whenever an OS is upgraded, a wipe is highly recommended as OTA's are imperfect and data between apps and settings conflicts between versions.
OTA is a fools errand if you're rooted. Now you're rooted, leave OTA to the unrooted and learn to manage your rooted device properly. All the info you could ever need is available in my signature as previously mentioned.
Spaceblow said:
Thanks for the tip but then I'll be unable to receive OTA updates unless I restore everything, including everything being wiped, right?
By using Titanium Backup?
Click to expand...
Click to collapse
or helium back up
Owning a Nexus makes fastboot your best friend, especially if you have issues.
Read up on adb/fastboot and forget OTA's. Nothing like a clean fresh install of a new version. And there's many options to save /backup your data and important files.
Without learning fastboot and adb.... Simple fix issues can become major headaches.
Don't be intimidated. Read, learn, then do. ?
---------- Post added at 09:49 AM ---------- Previous post was at 09:48 AM ----------
@rootSU has everything you need in his sticky roll up thread.
rootSU said:
All guides and info threads are in my signature. One such INFO thread is OTA help-desk, which explains that you can receive OTA with custom recovery, however there are extra steps.
However, please let me explain 1 thing. OTA is the ultimate noob move. Only root-noobs receive OTA updates. They are the most inconvenient method of updating your OS if you are rooted. Long before you even receive the OTA update, there will be a pre-rooted flashable.zip that can be flashed via recovery.
noobs will often say "but..but..but I wont have to wipe if I accept an OTA"... Little do they know... Even after an official OTA, things screw up. Whenever an OS is upgraded, a wipe is highly recommended as OTA's are imperfect and data between apps and settings conflicts between versions.
OTA is a fools errand if you're rooted. Now you're rooted, leave OTA to the unrooted and learn to manage your rooted device properly. All the info you could ever need is available in my signature as previously mentioned.
Click to expand...
Click to collapse
Well, you convinced me to take my N5 to a step further.
So I already Towelrooted my phone which gave me root access and an untouched bootloader and recovery. My next step would be to backup every app and all data to be sure in case something goes wrong, this would be done by using Titanium Backup. Then I should be unlocking the bootloader by simply using BootUnlocker for Nexus Devices so I wouldn't get my data wiped (I know I would be able to restore it with my backup but I rather do it a bit faster and less complex). When I did that, I have to head over to this thread and flash TWRP by following the instructions at "2. Installing a Custom Recovery".
So after all these steps my phone would have no limitations and it would be as unlocked as for example your Nexus 5, right?
Just seen this by droid modder x on YouTube will this work on our device I don't wanna screw my device up that's why I'm asking here's the link too
http://droidmodderx.com/how-to-root-any-and-all-android-devices-with-one-click-root-app
Sent from my A0001 using XDA Premium HD app
I would follow this guide:
http://forum.xda-developers.com/oneplus-one/general/guides-bacon-timmaaas-how-to-guides-t2839471
^this will help you do the unlock, root, flash for our amazing phone. Also there are rootkits and some people say to not use them but that is a personal preference.
But would that screw up the device if I did use the king root app ?
Sent from my A0001 using XDA Premium HD app
ward24 said:
But would that screw up the device if I did use the king root app ?
Sent from my A0001 using XDA Premium HD app
Click to expand...
Click to collapse
The question is why would you even use that app when you don't need to? Exploits and hacks aren't needed on this phone, all you need to do is go to my guide that you've been linked to above and follow the instructions to unlock your bootloader and root your device.
XDA Moderator
Transmitted via Bacon
Yes sir!!!
Sent from my A0001 using XDA Premium HD app
Rooted now thanks Heisenberg!
Sent from my A0001 using XDA Premium HD app
Good Morning, just a little information, there is no way to install super SU zip file with the stock cyanogen recovery? I need root to change timestamp of some video files that I copied into my OPO (MTP chaged all of them to the date of when i copied these files) and a rooted phone is the only option.
Thanks.
kingnappa said:
Good Morning, just a little information, there is no way to install super SU zip file with the stock cyanogen recovery? I need root to change timestamp of some video files that I copied into my OPO (MTP chaged all of them to the date of when i copied these files) and a rooted phone is the only option.
Thanks.
Click to expand...
Click to collapse
No, you can't flash SuperSU with the stock recovery. You need to unlock your bootloader and install TWRP.
XDA Moderator
Transmitted via Bacon
Heisenberg said:
No, you can't flash SuperSU with the stock recovery. You need to unlock your bootloader and install TWRP.
XDA Moderator
Transmitted via Bacon
Click to expand...
Click to collapse
That's what I thought, thanks.
BTW has anyone used thik Kingroot app? Does it work? Because I don't want to unlock bootloader and lose everything again just for my videos-
kingnappa said:
That's what I thought, thanks.
BTW has anyone used thik Kingroot app? Does it work? Because I don't want to unlock bootloader and lose everything again just for my videos-
Click to expand...
Click to collapse
You don't have to lose everything, just back it up first. Of course you probably wouldn't be in this position if you had properly researched the phone when you decided to buy it.
XDA Moderator
Transmitted via Bacon
Kingroot does not root opo. Have tested several times. Maybe I was unlucky
I don't get why it is preferable to root by unlocking the bootloader and losing all apps+settings in the process when the kingroot method would provide root without losing apps+settings...
galmok said:
I don't get why it is preferable to root by unlocking the bootloader and losing all apps+settings in the process when the kingroot method would provide root without losing apps+settings...
Click to expand...
Click to collapse
Because Kingroot is an exploit, it's a hack. It's like smashing a window to get inside your house when all you need to do is open the front door (unlock bootloader, root). On top of that, unlocking the bootloader is how it was designed to be done. Also, I don't get why people even lose any data or apps by unlocking the bootloader in the first place. Anyone with any sense researches their phone properly before jumping in and knows to unlock the bootloader before committing any data to it. The fact that unlocking wipes the device isn't even specific to this phone, it's a standard across all Android devices, so anyone who's modifying their device should know this anyway.
Heisenberg said:
Because Kingroot is an exploit, it's a hack. It's like smashing a window to get inside your house when all you need to do is open the front door (unlock bootloader, root). Also, I don't get why people even lose any data or apps by unlocking the bootloader in the first place. Anyone with any sense researches their phone properly before jumping in and knows to unlock the bootloader before committing any data to it. The fact that unlocking wipes the device isn't even specific to this phone, it's a standard across all Android devices, so anyone who's modifying their device should know this anyway.
Click to expand...
Click to collapse
Actually, with my Samsung Galaxy S2 (previous phone), all I had to do was install an update via builtin bootloader and I was rooted without having unlocked the bootloader. Worked great. I assumed the OnePlus (my current Android) would offer the same. Too late did I learn that unlocking the bootloader would erase everything. It wasn't even possible to make a backup of everything, locking me in the non-root position. So, if KingRoot can root my phone, this is clearly a great option as it would allow me to make a full backup of the phone (and restore should it be necessary, e.g. after unlocking bootloader). Exploits/hacks are not bad. Often they offer features not available otherwise, like KingRoot's non-destructive rooting.
galmok said:
Actually, with my Samsung Galaxy S2 (previous phone), all I had to do was install an update via builtin bootloader and I was rooted without having unlocked the bootloader. Worked great. I assumed the OnePlus (my current Android) would offer the same. Too late did I learn that unlocking the bootloader would erase everything. It wasn't even possible to make a backup of everything, locking me in the non-root position. So, if KingRoot can root my phone, this is clearly a great option as it would allow me to make a full backup of the phone (and restore should it be necessary, e.g. after unlocking bootloader). Exploits/hacks are not bad. Often they offer features not available otherwise, like KingRoot's non-destructive rooting.
Click to expand...
Click to collapse
Actually, the entire reason you had to root that way with your Samsung is because they've locked the bootloader down so that it cannot be unlocked. That's actually why exploits like Kingroot exist in the first place, in order to root devices that cannot be rooted in the normal way. As I said, if you had done the proper research in the first place you wouldn't be in the position you're in now. Exploits aren't bad, they have a place, they have a reason to exist, but it isn't to root devices like this which are open and able to be rooted in the way that was always intended.
I see a lot of ex Samsung users complaining that they have to go through the process of unlocking the bootloader and all that to root the phone, and complaining that their usual exploit doesn't work, not realising the whole time that they've got it completely backwards; the exploit is the round-about way of doing things, unlocking the bootloader is the intended way of doing things.
Edit:
Having the bootloader unlocked is essential for insurance purposes too. If you have trouble with your phone in future and need to flash the stock images because it won't boot you'll be forced to unlock the bootloader to do so. You won't be able to salvage any data from the phone. It's better to do it now when you actually have some control over the situation.
Heisenberg said:
Actually, the entire reason you had to root that way with your Samsung is because they've locked the bootloader down so that it cannot be unlocked. That's actually why exploits like Kingroot exist in the first place, in order to root devices that cannot be rooted in the normal way. As I said, if you had done the proper research in the first place you wouldn't be in the position you're in now. Exploits aren't bad, they have a place, they have a reason to exist, but it isn't to root devices like this which are open and able to be rooted in the way that was always intended.
I see a lot of ex Samsung users complaining that they have to go through the process of unlocking the bootloader and all that to root the phone, and complaining that their usual exploit doesn't work, not realising the whole time that they've got it completely backwards; the exploit is the round-about way of doing things, unlocking the bootloader is the intended way of doing things.
Click to expand...
Click to collapse
Well, at least my OnePlus (11s) could be rooted without having the bootloader unlocked. This is perfect for me, as I should still be able to get OTA firmware upgrades (not possible as far as I have read about unlocking the bootloader and installing a custom bootloader to root). Of course, this method relies on vulnerabilities, and are not always going to be there. So I have to make a choice:
1) Hope rooting via hacks is enough and always available, but also get OTA.
2) Unlock bootloader etc., lose all files and settings (start from scratch), not get OTA, use lots of time to get apps/contacts/photos/settings back.
I don't have time for #2 which is why I am (was) still unrooted. #1 took 2 minutes (1 minut of waiting) with kingroot and for now is good enough. I will begin using a decent backup program (instead of adb backup) so I can make a hopefully smooth transition to the unlocked/replaced bootloader case.
---------- Post added at 11:16 AM ---------- Previous post was at 11:15 AM ----------
Oh, and the only reason I rooted was to get more details about unwanted battery usage (BetterBatteryStats).
galmok said:
Well, at least my OnePlus (11s) could be rooted without having the bootloader unlocked. This is perfect for me, as I should still be able to get OTA firmware upgrades (not possible as far as I have read about unlocking the bootloader and installing a custom bootloader to root). Of course, this method relies on vulnerabilities, and are not always going to be there. So I have to make a choice:
1) Hope rooting via hacks is enough and always available, but also get OTA.
2) Unlock bootloader etc., lose all files and settings (start from scratch), not get OTA, use lots of time to get apps/contacts/photos/settings back.
I don't have time for #2 which is why I am (was) still unrooted. #1 took 2 minutes (1 minut of waiting) with kingroot and for now is good enough. I will begin using a decent backup program (instead of adb backup) so I can make a hopefully smooth transition to the unlocked/replaced bootloader case.
---------- Post added at 11:16 AM ---------- Previous post was at 11:15 AM ----------
Oh, and the only reason I rooted was to get more details about unwanted battery usage (BetterBatteryStats).
Click to expand...
Click to collapse
You can still get OTA updates with an unlocked bootloader and root, where did you read otherwise? Whoever said that is dead wrong. You might wanna read the edit I made to my post above too.
How to root sony xperia xa f3111
hung2161998 said:
How to root sony xperia xa f3111
Click to expand...
Click to collapse
At the moment you can't, locked Bootloader root may also be a thing of the past since the introduction of drm-verity security with the z3+, kingroot doesn't work either and apparently they want several hundred requests before offering device support if it'll work at all. Until someone builds a kernel+recovery for unlocked bootloader root were stuck. I get mine this week all being well so will try and help in this department for lb+ulb time permitting as my m2 has always been rooted. Will take some getting used to a stock device. There's nothing on 4pda yet either
aidy.lucas said:
At the moment you can't, locked Bootloader root may also be a thing of the past since the introduction of drm-verity security with the z3+, kingroot doesn't work either and apparently they want several hundred requests before offering device support if it'll work at all. Until someone builds a kernel+recovery for unlocked bootloader root were stuck. I get mine this week all being well so will try and help in this department for lb+ulb time permitting as my m2 has always been rooted. Will take some getting used to a stock device. There's nothing on 4pda yet either
Click to expand...
Click to collapse
Boss im gonna wait for your method
Sent from my F3112 using Tapatalk
yeyi01 said:
Boss im gonna wait for your method
Click to expand...
Click to collapse
Still stock here, currently no way to back up ta keys and not unlocking till there is. No working twrp either as far as I know. I'll wait for now
Sent from my Xperia XA using XDA Labs
aidy.lucas said:
Still stock here, currently no way to back up ta keys and not unlocking till there is. No working twrp either as far as I know. I'll wait for now
Click to expand...
Click to collapse
+1
To answer your question root is working on f3111 (as long as no bad feedback reported) and now for XA ultra too! TWRP is fully working as long as you don't have any encrypted partition or if you know the pin/password, it's a little different than before because of news Marshmallow security not because of me or TWRP.
OK, now you need to unlock your bootloader and void your warranty, and nothing more than that. You can wait for a exploit to come and backup your TA but for me it's a wast of time or wait for Kingroot but result will be same, not sure to backup TA. An other thing, I can bet that Kingroot will not be OTA survivor
rrvuhpg said:
To answer your question root is working on f3111 (as long as no bad feedback reported) and now for XA ultra too! TWRP is fully working as long as you don't have any encrypted partition or if you know the pin/password, it's a little different than before because of news Marshmallow security not because of me or TWRP.
OK, now you need to unlock your bootloader and void your warranty, and nothing more than that. You can wait for a exploit to come and backup your TA but for me it's a wast of time or wait for Kingroot but result will be same, not sure to backup TA. An other thing, I can bet that Kingroot will not be OTA survivor
Click to expand...
Click to collapse
I'd stay stock before I use dodgy kingroot. If you still get ota updates after rooting with Kingroot you ain't fully rooted for a start and Sony ric is still active. Encryption is on by default there's no way to change it or the password that I see. Until there's a way to keep my ta keys it's not gonna happen I don't think.
Sent from my Xperia XA using XDA Labs
aidy.lucas said:
I'd stay stock before I use dodgy kingroot. If you still get ota updates after rooting with Kingroot you ain't fully rooted for a start and Sony ric is still active. Encryption is on by default there's no way to change it or the password that I see. Until there's a way to keep my ta keys it's not gonna happen I don't think.
Click to expand...
Click to collapse
You can stay with a default disabled encryption only after root and you can switch back on and set your own password if you want. That's the only way I found but it's possible. What I want to say for Kingroot is I have a big doubt if it will be possible to dump TA with temp root on Marshmallow. You right for RIC but you forget dm-verity as additional security
What about temp root? Anyone anything know about it on XA? Titanium Backup & Trimmer should work fine with it
Rafixxxx said:
What about temp root? Anyone anything know about it on XA? Titanium Backup & Trimmer should work fine with it
Click to expand...
Click to collapse
There is no temp root or ta keys back up or use of ivy root. Unlocked bootloader currently only way to get any sort of root then tb should work fine though I've not used it in years
Sent from my Xperia XA using XDA Labs
I C,
hope there will be an Exploit soon
Hey everyone,
Was directed here by a few friends, I will admit that I am only a month into my android and I admit I know bugger all around this subject.
Basically I want to root my XA, get rid of the stupid apps that Sony insist on clogging my internal memory and also force install to my SD card as I keep getting on certain apps "not enough storage space" on my all but empty 200gb card.
I understand very little about rooting, I have tried many different things, I have spent last 2 hours working with SDK stuff and going thru cmd to get to the end and have "error: java.lang.securityexception: package android does not belong on 2000" appear to then find the phone needs to be rooted in the first place *growling a lot at the lappy by now*.
All I want is a way to root my phone successfully and force apps to install onto my huge SD card, if after that I can delete playstions, spotify, hangouts and other clutter than thats a bonus.
Remember please I am totally new to this field and rather dense with my lack of knowledge so pretend I am a lil kid that needs the big verion with pictures lol.
Thank you in advance
mogi99999 said:
I C,
hope there will be an Exploit soon
Click to expand...
Click to collapse
We can cross fingers with the "Dirty Cow" kernel exploit CVE-2016-5195 :fingers-crossed:
rrvuhpg said:
We can cross fingers with the "Dirty Cow" kernel exploit CVE-2016-5195 :fingers-crossed:
Click to expand...
Click to collapse
what this ?
leap_ahead said:
what this ?
Click to expand...
Click to collapse
Thats a 9yr old Root exploit that literally works on any android
.
DAM11MAD said:
I have unlocked bootloader but I still can't root it I have looked for manual rooting paths but no luck they are all out of date and don't work with ADB drivers anymore. So don't waste your time unlocking bootloader because It takes forever due to the fact that nothing works for the XA atm, I spent 5 hours unlocking bootloader only to find I still can't root it.
Click to expand...
Click to collapse
I think you are not good enough to root your device, root is working on XA and Ultra since months ago.
is there a toolkit to do the root and flash twrp?
hi guys
im new on pixel series. i want to know if i do unlock bootloader, is there any feature will gone if i do that?
like samsung lost knox or sony lost drm for camera and entertaiment
thankyou
xerxess said:
hi guys
im new on pixel series. i want to know if i do unlock bootloader, is there any feature will gone if i do that?
like samsung lost knox or sony lost drm for camera and entertaiment
thankyou
Click to expand...
Click to collapse
You have to work a bit to keep GPay working, and the solution definitely requires root. The current solution has been working for a few months and works on Android 10, but who knows if they will "fix" the current hack. You will absolutely not be able to download Netflix from the Play Store. There is one build on APK Mirror that will sideload and run, but of course you will get no updates. I've been running that build on the Pixel for about 6 months, and I have a tablet that does get Netflix updates yet I see no difference between that Feb build and Netflix even from a few days ago. Those are the only two things impacting me. Obviously, need to hide apps with Magisk and such is user specific (my car's door unlock/diagnostics/etc detects root without hiding it, but it works fine once hidden).
sliding_billy said:
You have to work a bit to keep GPay working, and the solution definitely requires root. The current solution has been working for a few months and works on Android 10, but who knows if they will "fix" the current hack. You will absolutely not be able to download Netflix from the Play Store. There is one build on APK Mirror that will sideload and run, but of course you will get no updates. I've been running that build on the Pixel for about 6 months, and I have a tablet that does get Netflix updates yet I see no difference between that Feb build and Netflix even from a few days ago. Those are the only two things impacting me. Obviously, need to hide apps with Magisk and such is user specific (my car's door unlock/diagnostics/etc detects root without hiding it, but it works fine once hidden).
Click to expand...
Click to collapse
first i wanna say thankyou for reply. ah i see so the only thing feature lost function is GPay (without little tweak). is it possible to relock again? if yes , is feature fully function again? tbh i dont really need GPay.
xerxess said:
first i wanna say thankyou for reply. ah i see so the only thing feature lost function is GPay (without little tweak). is it possible to relock again? if yes , is feature fully function again? tbh i dont really need GPay.
Click to expand...
Click to collapse
You can relock the BL, but you need to first return to absolute stock (no root, no kernel, no custom recovery, etc - pretty much flash the factory image with wipe to both slots to be safe). Then the relock will perform another factory reset anyways. So, if you are asking if you can keep anything you've done while unlocked the answer is no. To me, the biggest reason for unlocking beyond root is that it is almost impossible to hard brick the Pixel with an unlocked BL. It is pretty easily accomplished when locked down and can even happen as a result of a bad OTA or something that is not your fault at all.
sliding_billy said:
You can relock the BL, but you need to first return to absolute stock (no root, no kernel, no custom recovery, etc - pretty much flash the factory image with wipe to both slots to be safe). Then the relock will perform another factory reset anyways. So, if you are asking if you can keep anything you've done while unlocked the answer is no. To me, the biggest reason for unlocking beyond root is that it is almost impossible to hard brick the Pixel with an unlocked BL. It is pretty easily accomplished when locked down and can even happen as a result of a bad OTA or something that is not your fault at all.
Click to expand...
Click to collapse
understood, if only need back to absolute stock its okay for me. though it will like other smartphone need "drm" to relock.
yeah agree, why i think to unlock is about avoid brick or similar thing. but before i do that i need to know what feature will lost, so i asking here.
if relock again, all things will back to normal again right?
xerxess said:
understood, if only need back to absolute stock its okay for me. though it will like other smartphone need "drm" to relock.
yeah agree, why i think to unlock is about avoid brick or similar thing. but before i do that i need to know what feature will lost, so i asking here.
if relock again, all things will back to normal again right?
Click to expand...
Click to collapse
No, there is no residual damage like lost Knox. Everything would return to normal once BL is locked back up.
sliding_billy said:
No, there is no residual damage like lost Knox. Everything would return to normal once BL is locked back up.
Click to expand...
Click to collapse
understood, thank you very much. really appreciate your time.
Hi,
I've done a quick search but can't find anything definitive so a quick response on here would be greatly appreciated.
Are there any reasons not to root on a P7P? Like tripping Knox on Samsung devices? Basically, irreversible side effects of unlocking the BL or installing Magisk? I'm rooted on a Doogee S98 Pro, a Xiaomi MiPad 4 and a Samsung Tab S6 at the moment and I don't think I could go back to having no root. It's pretty much my main reason for not buying an S22 Ultra.
Hi
this is one of the major benefits of the P7P in my perspective: you can unlock, root, unroot, relock without any negative side effects. You don't trip any fuse or have other effects that cannot be undone by a simple reflash.
Plus, maybe due to this, the P7P is one of the phones where the dev community is still quite active.....
Sent from my rooted P7P
s3axel said:
Hi
this is one of the major benefits of the P7P in my perspective: you can unlock, root, unroot, relock without any negative side effects. You don't trip any fuse or have other effects that cannot be undone by a simple reflash.
Plus, maybe due to this, the P7P is one of the phones where the dev community is still quite active.....
Sent from my rooted P7P
Click to expand...
Click to collapse
Perfect answer, thanks!
Pretty hard to brick a Pixel.
Just make sure you don't relock your bootloader unless you're fully stock. I've seen a bunch of people doing that throughout these forums here for some reason.
Yup, if you want to unroot once you're rooted, it's absolutely imperative you flash full stock before toggling OEM Unlock and issuing any ADB commands to re-lock the bootloader. Do that without flashing back to factory stock and you end up with a phone that can't boot because the bootloader is locked with a non-stock build, you can't unlock the bootloader because the OEM is toggled, and you can't flash a stock build because the bootloader is locked. Brick time.
Other than that it's a fairly safe phone to play around with.
I strongly recommend Pixel Flasher, it makes the whole process easier, but make sure you read up on it before doing anything.
📳🔥PixelFlasher for Google Pixel 7 Pro Support Thread.
This is the support thread of PixelFlasher (PixelFlasher is an open-source self contained GUI tool to facilitate Pixel phone device flashing/rooting/updating with extra features). Note: This thread is meant for issues and problems faced in...
forum.xda-developers.com
GrapheneOS also supports relocking the bootloader, although I can't think of a reason why you'd want to.
The best reason not to root is that it's not needed in 2022. I can't imagine "needing" to do something with root that cannot be accomplished without root. YMMV
jaseman said:
The best reason not to root is that it's not needed in 2022. I can't imagine "needing" to do something with root that cannot be accomplished without root. YMMV
Click to expand...
Click to collapse
Call recording, full backup and restore, hosts based ad blockers.
Once rooted, it's annoying having to disable all Magisk mods, run updates, then re-root every month. I've also had updates corrupt the A/B Partitions. The warning screen for unlocked bootloader alone is a nuisance. If you're ok with that, go right ahead.
Guyinlaca said:
disable all Magisk mods, run updates, then re-root every month
Click to expand...
Click to collapse
You're adding steps and no indication of why. Just install the update with modified boot.img and call it good.
96carboard said:
Call recording, full backup and restore, hosts based ad blockers.
Click to expand...
Click to collapse
I went 3 days before rooting my P7P since I was unfamiliar with the process. I was able to root OnePlus blindfolded, but the forums made Pixel seem difficult. It was the most miserable 3 days when everything I wanted to use/customize depended on root.
without root I could not even get 5G working. Furthermore the AOSP Mods on the stock ROM... Systemless Hosts AdBlocking, Re-Vanced, .......
I unlocked and rooted the phone before even booted it the first time
Guyinlaca said:
Once rooted, it's annoying having to disable all Magisk mods, run updates, then re-root every month.
Click to expand...
Click to collapse
Updated to November, didn't disable any Magisk mods, no issues.
It's only some mods which cause issues. Not got them installed, you can perform the update without touching Magisk.
Guyinlaca said:
Once rooted, it's annoying having to disable all Magisk mods, run updates, then re-root every month. I've also had updates corrupt the A/B Partitions. The warning screen for unlocked bootloader alone is a nuisance. If you're ok with that, go right ahead.
Click to expand...
Click to collapse
You don't have to disable all your Magisk Mods
K1nsey6 said:
I went 3 days before rooting my P7P since I was unfamiliar with the process. I was able to root OnePlus blindfolded, but the forums made Pixel seem difficult. It was the most miserable 3 days when everything I wanted to use/customize depended on root.
Click to expand...
Click to collapse
And wasn't it funny when you realized that root on Pixel is actually easier than everything else?
Hello , i need help for rooting my p7p. If have a video step by step its be very helpfull. Sorry for my bad english " Salut " from Romania thanks
ZoM4cs said:
Hello , i need help for rooting my p7p. If have a video step by step its be very helpfull. Sorry for my bad english " Salut " from Romania thanks
Click to expand...
Click to collapse
Here is a guide you can follow.
96carboard said:
Call recording, full backup and restore, hosts based ad blockers.
Click to expand...
Click to collapse
Umm that's illegal bro.
chivamex10 said:
Umm that's illegal bro.
Click to expand...
Click to collapse
Maybe where you are, but not here and not in most places. So keep your legal advice to yourself, BRO.
chivamex10 said:
Umm that's illegal bro.
Click to expand...
Click to collapse
Actually in most jurisdictions it's what's called a one party consent requirement wherein one of the parties involved must be aware and consent. In this case the person doing the recording qualifies as the consenting party. In other places two party or more consent is required but not everywhere