Related
My phone (S3,CM11) randomly crashed and started bootlooping. Typically I just remove the battery, put it back in, and I'm good to go. This time however it didn't work. I'm able to get into recovery, after about 10 or so battery removals, but its clear CWM isn't how it used to be. I think it may be corrupt. The big give away is that the power button is no longer listed, or serves, as the 'enter' function. I can flash zips, and I tried re-installing the ROM, but the boot loops continue. I tried reinstalling my backup, but the MD5 sums didnt match. All solutions to fix that issue requires that I connect my phone to a computer and delete the MD5 sums, which I can't do since the phone wont boot. All my backups are poorly stored on the internal sdcard.
I'm hoping if I can re-install CWM in CWM, that I would be able to reinstall my ROM to a state I can turn the phone on. Is there another way to repair the boot file?
What are my options? Thanks!
Stump909 said:
My phone (S3,CM11) randomly crashed and started bootlooping. Typically I just remove the battery, put it back in, and I'm good to go. This time however it didn't work. I'm able to get into recovery, after about 10 or so battery removals, but its clear CWM isn't how it used to be. I think it may be corrupt. The big give away is that the power button is no longer listed, or serves, as the 'enter' function. I can flash zips, and I tried re-installing the ROM, but the boot loops continue. I tried reinstalling my backup, but the MD5 sums didnt match. All solutions to fix that issue requires that I connect my phone to a computer and delete the MD5 sums, which I can't do since the phone wont boot. All my backups are poorly stored on the internal sdcard.
I'm hoping if I can re-install CWM in CWM, that I would be able to reinstall my ROM to a state I can turn the phone on. Is there another way to repair the boot file?
What are my options? Thanks!
Click to expand...
Click to collapse
Did you rename the backups after you made them?
Sent from my HTC6525LVW using Tapatalk
BadUsername said:
Did you rename the backups after you made them?
Sent from my HTC6525LVW using Tapatalk
Click to expand...
Click to collapse
Nope. Still the default name.
Stump909 said:
Nope. Still the default name.
Click to expand...
Click to collapse
OK.
Go look for philz touch recovery in the development section. Click on his main thread link and scroll down to the unified s3 builds, download and flash the latest one in recovery, or Odin flash the .tar file if you can't get into recovery.
Setup is almost the exact same as cwm just a few more features. Try to restore the backup as normal. If it still doesn't work, go into factory reset and select the "wipe before new rom option", then flash your rom immediately afterwards.
If that still doesn't work, dig around the settings until you find the option for ignoring md5 sum check, then it will definitely let you install the backup. Just understand that there's a risk associated with doing that. If something is corrupted it could theoretically hard brick your phone, but if everything is still OK and all your backups are giving you the same issue then everything is probably fine.
Sent from my HTC6525LVW using Tapatalk
BadUsername said:
OK.
Go look for philz touch recovery in the development section. Click on his main thread link and scroll down to the unified s3 builds, download and flash the latest one in recovery, or Odin flash the .tar file if you can't get into recovery.
Setup is almost the exact same as cwm just a few more features. Try to restore the backup as normal. If it still doesn't work, go into factory reset and select the "wipe before new rom option", then flash your rom immediately afterwards.
If that still doesn't work, dig around the settings until you find the option for ignoring md5 sum check, then it will definitely let you install the backup. Just understand that there's a risk associated with doing that. If something is corrupted it could theoretically hard brick your phone, but if everything is still OK and all your backups are giving you the same issue then everything is probably fine.
Sent from my HTC6525LVW using Tapatalk
Click to expand...
Click to collapse
I appreciate the help, and the solution seemed like a homerun, but sadly things are worse. After successfully flashing the zip, the phone is now in a permanent bootloop trying to reach recovery. Now if I could only find a way to recover the data on the internal storage card.
Stump909 said:
I appreciate the help, and the solution seemed like a homerun, but sadly things are worse. After successfully flashing the zip, the phone is now in a permanent bootloop trying to reach recovery. Now if I could only find a way to recover the data on the internal storage card.
Click to expand...
Click to collapse
Last thing I can think of is you have a stuck power button that's giving you issues, look at YouTube videos to try to fix it then try it again.
Sent from my HTC6525LVW using Tapatalk
BadUsername said:
Last thing I can think of is you have a stuck power button that's giving you issues, look at YouTube videos to try to fix it then try it again.
Sent from my HTC6525LVW using Tapatalk
Click to expand...
Click to collapse
Wow, after reading up on the symptoms, that sounds like my problem. It also explains why I couldn't use that button to execute commands in recovery. Unfortunately this puts me in a bad situation. Since I tried to factory reset, and it crashed, I'm worried my install is corrupt now. I do have a backup from before the reset, but its labeled 01-01-1970. Surely that can't be good.
All I want to save at this point are my photos (some of which are more recent than my August backup). Would it be safe to restore my August backup and advanced restore the data from my most recent backup (01-01-1970)? Even if it's buggy, as long as I can transfer my photos to my external card I'd be happy. Thanks!
Stump909 said:
Wow, after reading up on the symptoms, that sounds like my problem. It also explains why I couldn't use that button to execute commands in recovery. Unfortunately this puts me in a bad situation. Since I tried to factory reset, and it crashed, I'm worried my install is corrupt now. I do have a backup from before the reset, but its labeled 01-01-1970. Surely that can't be good.
All I want to save at this point are my photos (some of which are more recent than my August backup). Would it be safe to restore my August backup and advanced restore the data from my most recent backup (01-01-1970)? Even if it's buggy, as long as I can transfer my photos to my external card I'd be happy. Thanks!
Click to expand...
Click to collapse
CWM doesn't input the proper date when you make backups. It has always defaulted to 1970 on the S3. TWRP does and I believe PhilZ recovery does as well allow you to post the proper date. Just make sure you have a total of 1+ GB file in your CWM folder. If you can pull that folder onto your computer (if its on an sd card) just right click the folder and check the date when it was created.
Edit: and as @BadUsername wrote, youtube videos may help out. I had a stuck power button and this clip helped me. It has been almost 11 months since I did this and I have been fine.
SlimSnoopOS said:
CWM doesn't input the proper date when you make backups. It has always defaulted to 1970 on the S3. TWRP does and I believe PhilZ recovery does as well allow you to post the proper date. Just make sure you have a total of 1+ GB file in your CWM folder. If you can pull that folder onto your computer (if its on an sd card) just right click the folder and check the date when it was created.
Edit: and as @BadUsername wrote, youtube videos may help out. I had a stuck power button and this clip helped me. It has been almost 11 months since I did this and I have been fine.
Click to expand...
Click to collapse
Thanks for the input. While I don't doubt you, every backup I've made has had the proper date as it's title (except for this one). Thanks for the video link!
Stump909 said:
Thanks for the input. While I don't doubt you, every backup I've made has had the proper date as it's title (except for this one). Thanks for the video link!
Click to expand...
Click to collapse
Oh, they have the dates now? Hmm, wasn't like that for the first year on the S3.
SlimSnoopOS said:
Oh, they have the dates now? Hmm, wasn't like that for the first year on the S3.
Click to expand...
Click to collapse
Yeah I didn't get the phone util the S4 was out and they've all had dates. Should I be worried in that case?
Stump909 said:
Yeah I didn't get the phone util the S4 was out and they've all had dates. Should I be worried in that case?
Click to expand...
Click to collapse
Idk if you want to try since none of the other backups worked. How many total CWM backups do you have? Is there an accompanying "BLOBS" folder as well? Or did they get rid of that too or are CWM backups now self contained? Over a year ago, there was a Blobs folder and folder of your backups.
SlimSnoopOS said:
Oh, they have the dates now? Hmm, wasn't like that for the first year on the S3.
Click to expand...
Click to collapse
SlimSnoopOS said:
Idk if you want to try since none of the other backups worked. How many total CWM backups do you have? Is there an accompanying "BLOBS" folder as well? Or did they get rid of that too or are CWM backups now self contained? Over a year ago, there was a Blobs folder and folder of your backups.
Click to expand...
Click to collapse
I have two. One marked 8-8-2014 and one 1-1-1970 (newest). I haven't looked at how they are stored in a while, but I remember it was multiple folders within folders taking up almost 2 gigs of space. As I stated, at this point if I could salvage my photos that would be enough.
Stump909 said:
I have two. One marked 8-8-2014 and one 1-1-1970 (newest). I haven't looked at how they are stored in a while, but I remember it was multiple folders within folders taking up almost 2 gigs of space. As I stated, at this point if I could salvage my photos that would be enough.
Click to expand...
Click to collapse
I think the backup is still good, you can probably salvage photos pretty easily with ADB if you have USB debugging enabled. I still think that fixing your power button will fix your problems and you'll be able to restore a backup.
Sent from my HTC6525LVW using Tapatalk
SlimSnoopOS said:
Idk if you want to try since none of the other backups worked. How many total CWM backups do you have? Is there an accompanying "BLOBS" folder as well? Or did they get rid of that too or are CWM backups now self contained? Over a year ago, there was a Blobs folder and folder of your backups.
Click to expand...
Click to collapse
I actually just checked my backups, I'm using philz latest but my backup has the correct date and I didn't have to manually input the date from within philz settings. There is also no more blobs folder. I think recently cwm redid their entire backup system, it's definitely different than it used to be. Has to be a fairly recent change though.
Sent from my HTC6525LVW using Tapatalk
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?
I have a Nexus 5 that I have had since December that has been functioning flawlessly (Google replacement for my last one with busted glass)
I have not done anything to this device (no hacking, no ROMSs, no rooting), beside replace the battery....
A few days ago, I noticed that a bunch of my "custom" ringtones were not working anymore. They just stopped showing up on the ringtone picker. The same goes for my "custom" alarm tones. I also noticed that when I go to attach a picture (to a hangout message, or SMS) that the "Recent" category shows only 1 or 2 pictures (instead of all recent pics). However, when I use RootExplorer and look at the directories, all of the files are there. The ringtones, alarms, pictures, etc. In fact the only pictures that are showing up under the "Recent" category are the ones that have been taken since I began having the problem.
There is also some other weird things happening, like I have lost some contact pictures and the phone has been acting weird.
This phone got the 5.1 update and I have already tried to wipe the /cache partition. Again, all files are there, but Android is not recognizing them...
Any help/suggestions would be greatly appreciated.
Try doing factory reset
Isus <3 said:
Try doing factory reset
Click to expand...
Click to collapse
Yeah, I will eventually try that but I was hoping that someone had a magic :fingers-crossed: fix that would be a little easier...
TaterTot24 said:
Yeah, I will eventually try that but I was hoping that someone had a magic :fingers-crossed: fix that would be a little easier...
Click to expand...
Click to collapse
If you're afraid of losing data just use applications to store it. Like titanium backup
Isus <3 said:
If you're afraid of losing data just use applications to store it. Like titanium backup
Click to expand...
Click to collapse
I guess I was just hesitant because this is the 1st phone I have had that does not have an actual "SD card" so I was not sure how it would work...
Also, the phone is not rooted -- not sure if that matters
TaterTot24 said:
I guess I was just hesitant because this is the 1st phone I have had that does not have an actual "SD card" so I was not sure how it would work...
Click to expand...
Click to collapse
Store pictures at Google photos app or use Dropbox, and for data and applications use titanium backup
Isus <3 said:
Store pictures at Google photos app or use Dropbox, and for data and applications use titanium backup
Click to expand...
Click to collapse
Does it have to be rooted? -- this is a Stock Nexus 5
TaterTot24 said:
Does it have to be rooted? -- this is a Stock Nexus 5
Click to expand...
Click to collapse
You need for titanium backup but for photos you don't.
Isus <3 said:
You need for titanium backup but for photos you don't.
Click to expand...
Click to collapse
So to keep from loosing app data, I need to use Ti Backup -- but to use Ti Backup I need to have root access...
In order to get root access, I will have to wipe my phone and loose my app data.... -- Sounds like a never-ending feedback loop
This is why I wanted to wait to do a factory reset
TaterTot24 said:
So to keep from loosing app data, I need to use Ti Backup -- but to use Ti Backup I need to have root access...
In order to get root access, I will have to wipe my phone and loose my app data.... -- Sounds like a never-ending feedback loop [emoji14]
This is why I wanted to wait to do a factory reset
Click to expand...
Click to collapse
If you have unlocked bootloader then you don't need to wipe your device for root
Isus <3 said:
If you have unlocked bootloader then you don't need to wipe your device for root
Click to expand...
Click to collapse
Ok, I guess I need to do some research on that then... Not sure how to tell if the bootloader is unlocked
Most of the stuff I looked at said it would wipe all data... Any links/suggestions on using the unlocked bootloader?
TaterTot24 said:
Ok, I guess I need to do some research on that then... Not sure how to tell if the bootloader is unlocked
Most of the stuff I looked at said it would wipe all data... Any links/suggestions on using the unlocked bootloader?
Click to expand...
Click to collapse
If you don't know how to see that then probably it's locked because it comes locked out of the box. So I'm afraid you will have to wipe your device data to fix your issue. If you're still wondering how to see that you must turn off your device and hold volume down + power button, phone will turn on and green Android will appear. At the bottom you will see lock state of bootloader
Hello, I'm new to XDA and was thinking about unlocking the bootloader, installing TWRP, and root my Oneplus one. I was wondering, what exactly does the "fastboot OEM Unlock" command actually do? I know it deletes data, but does it delete everything, and also the sdcard? Everything is backed up using the "G cloud" backup app. So am I all set to run the command? Afterwards I was thinking on installing Exodus ROM for 5.1.1 official. Thanks!
snakexpert552 said:
Hello, I'm new to XDA and was thinking about unlocking the bootloader, installing TWRP, and root my Oneplus one. I was wondering, what exactly does the "fastboot OEM Unlock" command actually do? I know it deletes data, but does it delete everything, and also the sdcard? Everything is backed up using the "G cloud" backup app. So am I all set to run the command? Afterwards I was thinking on installing Exodus ROM for 5.1.1 official. Thanks!
Click to expand...
Click to collapse
It wipes all user data from the device. This means all of your apps, all of your settings, and everything on the internal storage (photos, music, files, etc). Your OS will not be touched. Check out my guide:
http://forum.xda-developers.com/showthread.php?t=2839471
So is there a chance my phone will be bricked? I've backed up photos, videos, calls and messages, documents, and setting's.
snakexpert552 said:
So is there a chance my phone will be bricked? I've backed up photos, videos, calls and messages, documents, and setting's.
Click to expand...
Click to collapse
NO!
There is absolutely ZERO chance of your device getting bricked
Make sure that you don't tamper your USB cable while doing any of the process mention in your thread title
Follow @Heinsenberg guide, nothing will go wrong in any process.
Thanks! So am I ready to run the commands?
Mr hOaX said:
NO!
There is absolutely ZERO chance of your device getting bricked
Make sure that you don't tamper your USB cable while doing any of the process mention in your thread title
Follow @Heinsenberg guide, nothing will go wrong in any process.
Click to expand...
Click to collapse
There's never a zero chance of a brick occurring, but as long as all precautions are taken the risk can be considerably minimalised.
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...