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?
Related
Hi,
the question is already in the header.
Is it possible to Root/Unlock Bootloader without wipe?
I only found a Nexus 4 thread for that. I costumized my phone already... i dont want to reinstall everything
To unlock bootloader without data wipe you would need to have root. To have root without an unlocked bootloader on Nexus devices, there would need to be an exploit found in Android 4.4. As far as I know, this does not exist. So, to answer your question: it is possible if an exploit for root exists
dastimlein said:
I costumized my phone already... i dont want to reinstall everything
Click to expand...
Click to collapse
On another note:
This is why, on a Nexus device, you unlock the bootloader right after checking USB port is working fine. You can always lock it back if you take good care of your USB port/cable.
a hammerhead wrote this.
why still no exploit for kitkat ? :crying:
I'm lazy to wipe and i didn't unlocked the bootloader on first day because i did want to stay stock this time (what a bad idea)
andQlimax said:
why still no exploit for kitkat ? :crying:
I'm lazy to wipe and i didn't unlocked the bootloader on first day because i did want to stay stock this time (what a bad idea)
Click to expand...
Click to collapse
because its so easy to unlock no one cares to look.
if you want to root, unlock your bootloader and get over it.
Zepius said:
because its so easy to unlock no one cares to look.
if you want to root, unlock your bootloader and get over it.
Click to expand...
Click to collapse
Yeah, I know how to... Its not that the point
I was just a bit sarcastic.. Its not that much dramatic
But I'm still lazy to wipe
I'm that lazy to wipe that I'm looking to find an exploit by myself
Inviato dal mio Nexus 5 utilizzando Tapatalk
andQlimax said:
Yeah, I know how to... Its not that the point
I was just a bit sarcastic.. Its not that much dramatic
But I'm still lazy to wipe
I'm that lazy to wipe that I'm looking to find an exploit by myself
Inviato dal mio Nexus 5 utilizzando Tapatalk
Click to expand...
Click to collapse
You can backup/restore almost everything needed via apps or adb, even without root. Apps, texts, call logs, bookmarks, etc.The amount of time wasted finding an exploit that isn't available and you could be done wiping, rooting, logging back into your accounts, and enjoying the benefits of root.
If you're that lazy why are looking for an exploit yourself. That didn't sound lazy to me
es0tericcha0s said:
You can backup/restore almost everything needed via apps or adb, even without root. Apps, texts, call logs, bookmarks, etc.The amount of time wasted finding an exploit that isn't available and you could be done wiping, rooting, logging back into your accounts, and enjoying the benefits of root.
Click to expand...
Click to collapse
I'm in the OP's situation -- set up the phone, convinced myself I wouldn't need root this time, but having second thoughts. My main concern is that adb backup -> wipe -> adb restore will "miss" something, and I won't be able to get it back. There's no one specific thing I'm worried about, just a sort of nagging concern.
I'm thinking of waiting until my previous phone is fixed (busted USB port...) then doing my test-restore there. That should work, right?
Ghengis042 said:
I'm thinking of waiting until my previous phone is fixed (busted USB port...) then doing my test-restore there. That should work, right?
Click to expand...
Click to collapse
Yeah.
There's also helium. Cant hurt to take multiple backups.
Well Helium is just a pretty front-end for ADB right? I figure if adb "misses" something it's likely Helium would too.
And I just had another concern occur to me -- if my older device (SGS2 running CM 10.1) can't use the ART runtime, will that mean I can't restore my (ART-using) N5 backup? I want to install apps + data with a single command, if possible, but if the apps are backed up as ART-compiled, does that mean the code that's intended for Dalvik has been removed? Might be a better question for the runtime thread.
Wait? What? Are you trying to restore sgs2 into a nexus 5?
Sent from my Nexus 5 using Tapatalk
Hi All
I have a 1st edition Xoom, WiFi, that I bought in March of 2011. I never rooted it before but am considering doing it now if it is still feasible. It looks like my current Android version is 4.1.2.
One thing - due to my work email, they made me encrypt the tablet. I hated it the moment I did it because it slowed it down quite a bit. But its done and there does not seem to be an option to un do it, unless rooting it will. I am ok with that as I do not need that email on this device. But is rooting an option with an encrypted tablet? Is it the same process? Does it change anything?
So - my questions are:
Is it still feasible to root this tablet?
Is this page this the latest/greatest Root for the Xoom?
[**]http://forum.xda-developers.com/showthread.php?t=1010568
What version of Android would I have once done?
Any other factors I need ot consider?
I rooted my phone a few years ago and it was straight forward. But I do not want to end up with a 10.1 inch brick.
Thanks.
Gamul1 said:
Hi All
I have a 1st edition Xoom, WiFi, that I bought in March of 2011. I never rooted it before but am considering doing it now if it is still feasible. It looks like my current Android version is 4.1.2.
One thing - due to my work email, they made me encrypt the tablet. I hated it the moment I did it because it slowed it down quite a bit. But its done and there does not seem to be an option to un do it, unless rooting it will. I am ok with that as I do not need that email on this device. But is rooting an option with an encrypted tablet? Is it the same process? Does it change anything?
So - my questions are:
Is it still feasible to root this tablet?
Is this page this the latest/greatest Root for the Xoom?
[**]http://forum.xda-developers.com/showthread.php?t=1010568
What version of Android would I have once done?
Any other factors I need ot consider?
I rooted my phone a few years ago and it was straight forward. But I do not want to end up with a 10.1 inch brick.
Thanks.
Click to expand...
Click to collapse
How did you encrypt the tablet anyway?
superbay said:
How did you encrypt the tablet anyway?
Click to expand...
Click to collapse
Its been a few years so its fuzzy. I think it was in the settings under security. But at the time I followed some directions. It took over night to do. Now when I go to settings I see the encryption option but it does nothing.
Un. Encryption is not the reason I want to root. The device is slow and I hear I may be able to speed it up a bit. Plus, there is a game that crashed the tablet because of the tegra 2 chip and k read some steps on making a change that prevents the crash.
Gamul1 said:
Its been a few years so its fuzzy. I think it was in the settings under security. But at the time I followed some directions. It took over night to do. Now when I go to settings I see the encryption option but it does nothing.
Un. Encryption is not the reason I want to root. The device is slow and I hear I may be able to speed it up a bit. Plus, there is a game that crashed the tablet because of the tegra 2 chip and k read some steps on making a change that prevents the crash.
Click to expand...
Click to collapse
Then dont hesitate and go for it
May I add that rooting will need an unlocked bootloader which will wipe /data so you'd loose everything
matt4321 said:
May I add that rooting will need an unlocked bootloader which will wipe /data so you'd loose everything
Click to expand...
Click to collapse
I am ok with that. I was just trying to figure out if this older tablet that was encrypted can be rooted. And, if the thread I referenced was the latest still. It is a couple years old so I was not sure that meant the android OS was old or updated or if there was a newer thread somewhere I can't find.
Gamul1 said:
I am ok with that. I was just trying to figure out if this older tablet that was encrypted can be rooted. And, if the thread I referenced was the latest still. It is a couple years old so I was not sure that meant the android OS was old or updated or if there was a newer thread somewhere I can't find.
Click to expand...
Click to collapse
what android version are you on? this will help me tell you through how to root
matt4321 said:
what android version are you on? this will help me tell you through how to root
Click to expand...
Click to collapse
According to my settings page, my Android version is 4.1.2.
Gamul1 said:
According to my settings page, my Android version is 4.1.2.
Click to expand...
Click to collapse
Are you familiar with fastboot/adb?
you need to unlock your bootloader using
Code:
fastboot oem unlock
then you need to flash a custom recovery, I suggest this one: http://forum.xda-developers.com/showthread.php?t=1782235
use the command:
Code:
fastboot flash recovery recovery.img
then
Code:
fastboot reboot
upon rebooting when you see the motorola logo, wait about 2 seconds, then you need to press the volume down button, then volume up to select android recovery.
Once in recovery you will need to flash this file to gain root:
http://forum.xda-developers.com/showpost.php?p=30464067&postcount=408
After all this you will have Android 4.1.2 with a custom recovery and root access, from now on it will be easy to swap between ROMs, android versions etc.
Always make a backup
matt4321 said:
snipped a bunch of great info...
Click to expand...
Click to collapse
Thanks! I will give this a try. A few other questions around this:
1. Will the device still be encrypted once this is done?
2. If not - do you know if it is possible to fool the mail program into thinking it is still encrypted?
Thanks!
Gamul1 said:
Thanks! I will give this a try. A few other questions around this:
1. Will the device still be encrypted once this is done?
2. If not - do you know if it is possible to fool the mail program into thinking it is still encrypted?
Thanks!
Click to expand...
Click to collapse
The device will no longer be encrypted, all data is wiped anyway.
You can re-encrypt the device though by going to settings>security>encryption>encrypt tablet
matt4321 said:
The device will no longer be encrypted, all data is wiped anyway.
You can re-encrypt the device though by going to settings>security>encryption>encrypt tablet
Click to expand...
Click to collapse
Thanks! But if I go this route I won't want it encrypted again. I was just curious if being rooted there was a way to fool it. Sort of a best of both worlds thing. But no more encryption for me again. It killed this thing the first time.
Is it possible to root one plus one, without deleting any data and apps from it? I just want root access but don't want any custom rom.
yes, of course..
root doesn't delete any of your data
senaferdy79 said:
yes, of course..
root doesn't delete any of your data
Click to expand...
Click to collapse
Thanks for that. How can I do that?
#newtorooting
senaferdy79 said:
yes, of course..
root doesn't delete any of your data
Click to expand...
Click to collapse
That isn't technically true. In order to get root you must have a custom recovery installed. In order to install a custom recovery you must unlock the bootloader. Unlocking the bootloader wipes the device.
---------- Post added at 08:13 PM ---------- Previous post was at 08:10 PM ----------
sourabhkejriwal said:
Thanks for that. How can I do that?
#newtorooting
Click to expand...
Click to collapse
Sorry you got your hopes up, but the other poster isn't right. As per my reply to him you need to unlock your bootloader first, which is going to wipe your device. I'd suggest backing up any files that you have that are important to you. As for your apps and settings, you'll have to set them up again afterwards. Go to my guide thread here:
http://forum.xda-developers.com/oneplus-one/general/guides-bacon-timmaaas-how-to-guides-t2839471
You need to follow (in order) sections 1, 2, 3, and 4. This will give you root access on your stock ROM. You should also follow section 10, it's very important that you make a backup of your EFS partition.
timmaaa said:
That isn't technically true. In order to get root you must have a custom recovery installed. In order to install a custom recovery you must unlock the bootloader. Unlocking the bootloader wipes the device.[
Click to expand...
Click to collapse
So are you saying all the many how to's that tell you that you can skip installing recover are wrong? Apparently, I don't have enough posts yet to create a link but I've seen posts here on XDA that say other wise and the one I have in front of me at the moment is from ibtimes . com titled "how-root-oneplus-one-install-twrp-recovery-1450708"
Their "Step-7" reads
Step-7: If you want to root the phone without installing TWRP recovery, type the following command
fastboot boot twrp.img
Click to expand...
Click to collapse
I guess the real question being, why would you need a custom recovery?
pdhx said:
So are you saying all the many how to's that tell you that you can skip installing recover are wrong? Apparently, I don't have enough posts yet to create a link but I've seen posts here on XDA that say other wise and the one I have in front of me at the moment is from ibtimes . com titled "how-root-oneplus-one-install-twrp-recovery-1450708"
Their "Step-7" reads
I guess the real question being, why would you need a custom recovery?
Click to expand...
Click to collapse
You're looking at outdated information. They used to be correct, but now they are wrong. This is because you can no longer use the fastboot boot recovery.img command with a locked bootloader. In fact, that functionality was removed quite some time ago.
You need a custom recovery because that's how you flash SuperSU to get root. There's no way around it.
Transmitted via Bacon
The default recovery will only flash cm signed zip, which is another reason for needing a custom recovery. That method you mention at ibtimes meant that it would allow you to, for one boot cycle, do a "live boot" of twrp
Sent From Lollipopified Bacon Goodness!
But how is anything going to be written to the system partition if it is locked ?
timmaaa said:
You're looking at outdated information. They used to be correct, but now they are wrong. This is because you can no longer use the fastboot boot recovery.img command with a locked bootloader. In fact, that functionality was removed quite some time ago.
You need a custom recovery because that's how you flash SuperSU to get root. There's no way around it.
Click to expand...
Click to collapse
Ugh, was afraid of that, you might want to add a comment to that effect to your guide....
Would have been nice to just add a setting to the default recovery to allow you to toggle whether you need a signed zip or not. Sucks that I could root my SGS III (which is far less hacker friendly than the One) without wiping it but I can't do that for the One, all i want is root for the moment. However, after playing around some more I'm getting stick before I even get that far; I can get ADB to find the device but when I adb reboot bootloader I cannot get fastboot to find the device. I've tried multiple drivers, different USB ports. When my One goes into fastboot the screen seems awfully dim, almost like it hasn't completely initialized, is that normal? And if so, any suggestions on why I can get adb to work but not fastboot?
pdhx said:
Ugh, was afraid of that, you might want to add a comment to that effect to your guide....
Would have been nice to just add a setting to the default recovery to allow you to toggle whether you need a signed zip or not. Sucks that I could root my SGS III (which is far less hacker friendly than the One) without wiping it but I can't do that for the One, all i want is root for the moment. However, after playing around some more I'm getting stick before I even get that far; I can get ADB to find the device but when I adb reboot bootloader I cannot get fastboot to find the device. I've tried multiple drivers, different USB ports. When my One goes into fastboot the screen seems awfully dim, almost like it hasn't completely initialized, is that normal? And if so, any suggestions on why I can get adb to work but not fastboot?
Click to expand...
Click to collapse
The one's bootloader is not like a nexus one where you can at least reboot recovery etc, once it boots thats it
what do get when you type fastboot devices ?
bombadier said:
The one's bootloader is not like a nexus one where you can at least reboot recovery etc, once it boots thats it
Click to expand...
Click to collapse
Which seems to be somewhat limiting for such an otherwise developer friendly device?
bombadier said:
what do get when you type fastboot devices ?
Click to expand...
Click to collapse
Nada, nothing, nil. however, "adb devices" works fine... WTF?
pdhx said:
Which seems to be somewhat limiting for such an otherwise developer friendly device?
Nada, nothing, nil. however, "adb devices" works fine... WTF?
Click to expand...
Click to collapse
Point one was just to say there is not anything really you can do in the bootloader, being able to reboot to recovery etc is actually a handy feature
Try a different fastboot.exe ? if you say that adb works perfectly then there has to be something wrong with your fastboot binary
I have attached my one,download and change the name back to .exe and see what happens
Going to need more info in order to help
bombadier said:
Point one was just to say there is not anything really you can do in the bootloader, being able to reboot to recovery etc is actually a handy feature
Try a different fastboot.exe ? if you say that adb works perfectly then there has to be something wrong with your fastboot binary
I have attached my one,download and change the name back to .exe and see what happens
Going to need more info in order to help
Click to expand...
Click to collapse
Fair point about bootloader, what I don't get is why they forced you to have to do the unlock to root? All I started out wanting to do was install Titanium and run a Nandroid or two. Guess if I'm going to have to wipe I guess I may end up installing a Lollipop ROM. However, I still can't get there. The fast boot you supplied gives the same problem. I was running the latest fastboot from the Android SDK and your's appears to be the same (though I haven't done a binary compare). As far as I can tell that leaves the device drivers, the laptop, or the phone itself. I'm running Win 7 SP 1 64 bit and I've tried various drivers including the Samsung the Google generic and they make no difference. Not sure how they would since adb works but I've seen some suggestions that drivers can be finicky in this regard.
What else can I tell you that might help?
Seems since I can get into the recovery that comes with the phone I could maybe get a works around somehow?
pdhx said:
Fair point about bootloader, what I don't get is why they forced you to have to do the unlock to root? All I started out wanting to do was install Titanium and run a Nandroid or two. Guess if I'm going to have to wipe I guess I may end up installing a Lollipop ROM. However, I still can't get there. The fast boot you supplied gives the same problem. I was running the latest fastboot from the Android SDK and your's appears to be the same (though I haven't done a binary compare). As far as I can tell that leaves the device drivers, the laptop, or the phone itself. I'm running Win 7 SP 1 64 bit and I've tried various drivers including the Samsung the Google generic and they make no difference. Not sure how they would since adb works but I've seen some suggestions that drivers can be finicky in this regard.
What else can I tell you that might help?
Seems since I can get into the recovery that comes with the phone I could maybe get a works around somehow?
Click to expand...
Click to collapse
They're "forcing" you to unlock the bootloader in order to root the device because that's the universally accepted standard (unlock bootloader, install custom recovery, flash root). Some devices have super secure bootloaders and that's why you end up needing to use hacks to get those devices rooted, but that isn't the normal way to go about it. Anyway, there's no advantage to leaving the bootloader at all. There's also no disadvantage to unlocking the bootloader at all. You might say that the fact that the device is wiped during the unlocking process is a disadvantage, but that fact is very well documented both here, on the OnePlus forums, and pretty much any other reputable tech site that mentions unlocking the bootloader on this phone. The point to that last sentence? It pays to research a device thoroughly before buying it, or before using it, the wiping of the device is no issue at all if you do it when you receive the phone (prior to using it), like many people have. But in your situation you're just going to have to backup any important media from the phone prior to unlocking.
Anyway, on to your fastboot issue. Exactly which drivers do you have installed on your PC? Do you have any other phone drivers or software installed on the PC? And do you have access to another PC in case the one you're using is the source of the issue?
Got it, 27th try (give or take) is the charm.... Had to use USBdeview and uninstall the Google and the Qualcomm drivers. Reinstalled the Google drivers (after a reboot) and got it to work. Guess I could have figured that out from dev manager by watching what drivers got activated while fastboot was active but nothing ever jumped out at me as an obvious culprit.
Interesting to note that TWRP now automatically prompts you to install SuperSU if you reboot after installing it. Maybe it found the zip but either way, nice touch!
Now to go and decide what ROM to install....
Thanks for your help!
I would suggest temasek unofficial cm12 ROM. Been using it pretty much as a daily driver since version 1.something of the ROM and no problems. At this point it's been almost a month of not having to boot into my cm11s ROM lol. I use it with AK kernel, seems like a good match cuz both devs are working together looks like. Flash AK ukm special edition after flashing his kernel and install synapse from play store if you want to play around with settings of the kernel
Sent From Lollipopified Bacon Goodness!
zenix23456 said:
I have been using AnyRooter for months and it is quite good to root OnePlus phones.
Click to expand...
Click to collapse
Except the Oneplus One.
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.
Hi
Couldn't find any thread about it. So posting it
I red on official website that I might loose some functionalities "You may lose some key functions like telephone, radio, and audio playback.".
Can anyone put some light on what I might loose as per this? (I know data will be lost and etc but what about this line pls?
Nothing , they are just pretending . only ur warranty voids
Sent from my Moto G using Tapatalk
Sorry for posting thread in wrong section.
As far as I know you still get OTA updates as well, correct? Assuming unlocked bootloader and stock operating system.
jitin02 said:
Hi
Couldn't find any thread about it. So posting it
I red on official website that I might loose some functionalities "You may lose some key functions like telephone, radio, and audio playback.".
Can anyone put some light on what I might loose as per this? (I know data will be lost and etc but what about this line pls?
Click to expand...
Click to collapse
No data is lost for unlocking bootloader.... Believe me i have unloacked it and flashed CM rom and its working better than before..
shashidhar941997 said:
No data is lost for unlocking bootloader.... Believe me i have unloacked it and flashed CM rom and its working better than before..
Click to expand...
Click to collapse
Of course data is lost... everything on the phone is wiped clean, it is impossible at present to unlock the G3 without wiping out all user data.
To the OP, you do not lose any functionality by unlocking alone, everything will work EXACTLY as before as long as the only thing you do is unlock... that being said, if you change anything, such as adding root access, flashing Xposed, installing a custom recovery, that changes the device so it could potentially cause an issue outside of Motorola's control or outside of their supported practices. For example, you will not be able to receive OTA updates if you have modified the /system partition, the OTA system will see that that the partition has been mounted R/W and will not offer further OTA's, but you can still sideload them manually. If you install a custom recovery and nothing else, you may be offered an OTA, but it will fail since it requires stock recovery.
Basically, if you are careful and willing to do a little research and go beyond the "stock" experience, you will have to do a few things manually, and unlocking is the beginning of that process. Unlocking just for the sake of doing it and not continuing is a waste of time.
acejavelin said:
Of course data is lost... everything on the phone is wiped clean, it is impossible at present to unlock the G3 without wiping out all user data.
To the OP, you do not lose any functionality by unlocking alone, everything will work EXACTLY as before as long as the only thing you do is unlock... that being said, if you change anything, such as adding root access, flashing Xposed, installing a custom recovery, that changes the device so it could potentially cause an issue outside of Motorola's control or outside of their supported practices. For example, you will not be able to receive OTA updates if you have modified the /system partition, the OTA system will see that that the partition has been mounted R/W and will not offer further OTA's, but you can still sideload them manually. If you install a custom recovery and nothing else, you may be offered an OTA, but it will fail since it requires stock recovery.
Basically, if you are careful and willing to do a little research and go beyond the "stock" experience, you will have to do a few things manually, and unlocking is the beginning of that process. Unlocking just for the sake of doing it and not continuing is a waste of time.
Click to expand...
Click to collapse
So basically it's like my oneplus one... The ota thing. Who cares .
And yes I was thinking of rooting, xposedify, twrp .......
Tks fr info ..... But another of my worry is locking bl. Acc. To what I red is you can't lock it properly. As my devic is 1 month old (not even 1) I don't want to risk it
jitin02 said:
So basically it's like my oneplus one... The ota thing. Who cares .
And yes I was thinking of rooting, xposedify, twrp .......
Tks fr info ..... But another of my worry is locking bl. Acc. To what I red is you can't lock it properly. As my devic is 1 month old (not even 1) I don't want to risk it
Click to expand...
Click to collapse
The bootloader cannot be relocked... there is a procedure to appear locked, but it you can never actually undo the unlock procedure... One thing to keep in mind is that when you unlock you lose your warranty, but it is not based on whether your device shows it's locked or not, the minute you accept the T&C on Motorola's site and get the unlock token, your warranty is gone, it doesn't even matter if you actually unlock the device or not.
acejavelin said:
The bootloader cannot be relocked... there is a procedure to appear locked, but it you can never actually undo the unlock procedure... One thing to keep in mind is that when you unlock you lose your warranty, but it is not based on whether your device shows it's locked or not, the minute you accept the T&C on Motorola's site and get the unlock token, your warranty is gone, it doesn't even matter if you actually unlock the device or not.
Click to expand...
Click to collapse
Them I m not unlocking. Lol
shashidhar941997 said:
No data is lost for unlocking bootloader.... Believe me i have unloacked it and flashed CM rom and its working better than before..
Click to expand...
Click to collapse
better than before means do u notice quick battery darning i also unlocked nd CM 12.1 excluding battery it better than before
acejavelin said:
Of course data is lost... everything on the phone is wiped clean, it is impossible at present to unlock the G3 without wiping out all user data.
Click to expand...
Click to collapse
Is the SD Card safe or should that be removed prior to unlocking bootloader?
MrTooPhone said:
Is the SD Card safe or should that be removed prior to unlocking bootloader?
Click to expand...
Click to collapse
I would remove it if you want to keep it setup as is... It does a factory reset which will wipe the SD card.
Sent from my MotoG3 using Tapatalk
---------- Post added at 07:44 AM ---------- Previous post was at 07:43 AM ----------
MrTooPhone said:
Is the SD Card safe or should that be removed prior to unlocking bootloader?
Click to expand...
Click to collapse
It will wipe SD card.
Sent from my MotoG3 using Tapatalk
acejavelin said:
I would remove it if you want to keep it setup as is... It does a factory reset which will wipe the SD card.
Sent from my MotoG3 using Tapatalk
---------- Post added at 07:44 AM ---------- Previous post was at 07:43 AM ----------
It will wipe SD card.
Sent from my MotoG3 using Tapatalk
Click to expand...
Click to collapse
It did not wipe mine. It only formats the internal partitions. Most phones you have to specify if you want the SD formatted as well.
quakeaz said:
It did not wipe mine. It only formats the internal partitions. Most phones you have to specify if you want the SD formatted as well.
Click to expand...
Click to collapse
Unlocking the bootloader should wipe all user partitions, including SD card, the bootloader unlock factory reset is a complete wipe, unless something has changed. You don't get an option of what to erase when unlocking the bootloader.
Sent from my MotoG3 using Tapatalk
acejavelin said:
Unlocking the bootloader should wipe all user partitions, including SD card, the bootloader unlock factory reset is a complete wipe, unless something has changed. You don't get an option of what to erase when unlocking the bootloader.
Sent from my MotoG3 using Tapatalk
Click to expand...
Click to collapse
I know there's no option. I've just never seen a phone that wipes SD by default, including this one. Usually wiping user data consists of the /data partition. But if you're more comfortable pulling the SD out, better safe than sorry...
Sent from my MotoG3 using Tapatalk
quakeaz said:
I know there's no option. I've just never seen a phone that wipes SD by default, including this one.
Sent from my MotoG3 using Tapatalk
Click to expand...
Click to collapse
Hmm... For a normal factory reset I would agree, for bootloader unlock reset it should wipe it. What's the point of the security feature of wiping the device when bootloader unlock occurs if it leaves a major security hole by not wiping the SD card?
I can't speak from experience on this, I removed mine as a precautionary measure because back in the older HTC days of Gingerbread/Jellybean, there were a few cases where the SD card would be trashed when unlocking the bootloader.
Sent from my MotoG3 using Tapatalk
Neither unlocking the bootloader nor a factory reset do ANYTHING LIKE wiping your phone. Neither would either make any sense at all.
You are not supposed be able to unlock the bootloader so what sort of software do you think could be included to detect or stop it happening? Samsung KNOX comes to mind but that ain't Moto.
Factory resets remove apps, call logs, contacts, and anything else on the internal SD. Stuff that is on the external SD is not affected, only the Data and the Cache partitions.
I unlocked my bootloader but that didn't prevent me from receiving the MM Ota update two days ago. So, unlocking void only your warranty, nothing else. It will for sure wipe your phone's data.
There are a number of reasons for unlocking Bootloader. Especially for those that cannot or do not want to return phone to manufacturer.
(1) Android can become corrupt at any time. It can happen randomly. Without an unlocked Bootloader, you may no longer be able to load Android or access your files. With a custom recovery - you still have ADB and root access to your files. Also in the event that factory firmware images do not work, you now have the option of flashing a custom ROM.
(2) Lost / accidentally deleted photos. Without an unlocked Bootloader and root access, your options are very limited. If you have root access, there are apps that can recover deleted photos. You also have the possibility of making a backup image of internal storage and transferring that to PC for use with Data recovery software.
(3) You need an unlocked Bootloader to flash a custom Kernel / ROM. These can provide better performance, improved battery-life, a greater range of features and in some cases, improved app compatibility.
(4) This one may be less of an issue, but worth considering. Having an unlocked Bootloader can get you out of a situation where phone is locked due to 'Device Protection.'
Related: http://www.androidpolice.com/2015/0...ne-you-might-trip-a-72-hour-security-lockout/
lost101 said:
(4) This one may be less of an issue, but worth considering. Having an unlocked Bootloader can get you out of a situation where phone is locked due to 'Device Protection.'
Click to expand...
Click to collapse
Though you also have to consider the other side of that medal.
With a locked bootloader and device protection active, the phone is useless to everyone except yourself.
If the phone is lost this *might* increase the chance that it's being returned to you.
And if it's stolen you at least have the satisfaction that the thief can only use it as a paperweight.
If the bootloader is unlocked, whoever found or stole the phone can overcome the device protection and can use or sell the phone...