Related
So I'm currently on 4.4 (19.5.3) and am rooted. Having tons of issues (can't answer phone calls unless screen is off, gmail sync) and assuming an update and possible wipe will fix most of them.
How can I get to the latest software without loosing root? Preferably without wiping, but if need be I have TiBackup.
I would recommend downloading SunShine and spending the $25 to unlock your device. Since you're still on 19.5.3 you should be able to unlock with no issues. Once unlocked you'll be able to flash TWRP (or a recovery of your choice) and then you can install custom ROMs. I recommend @Topsnake's Venom 4.4.4 Moto X Port. There are also a few debloated Stock 4.4.4 ROMs to choose from. Or you can go with a custom ROM such as Team Gummy or a CM nightly (unfortunately CM dropped the Ultra/Maxx so you won't see new nightlies until someone takes up development for it). Another major benefit of unlocking would be gaining the ability to flash root without an additional exploit so you won't need to worry about losing it.
Hmm, like the idea...downside is that I have a cracked screen and its very possible I'm going to have to replace this device in the near future. Which I think means I'll have to rebuy sunshine again which is kind of lame.
rmoney said:
Which I think means I'll have to rebuy sunshine again
Click to expand...
Click to collapse
You will; SunShine payments are on a per device basis. It may seem like a steep price but considering how much work is put into it, the devices that they've bought (and bricked), and the benefit you get from it, I think it's well worth the price. Think of it as buying a developer version of a device for only $25 extra. Although, considering you'll most likely be buying a new soon due to your screen, I'd recommend just waiting to use SunShine when you get the new phone.
In the mean time, I believe there are ways to upgrade to 4.4.4 and retain root. Pretty certain there is a thread or two on it in these Ultra forums. I know that you can at least move to 19.6.3 and retain root. But really, the difference between 4.4 and 4.4.4 isn't worth the hassle and risk of losing root. I'd probably just stick with what you have until you replace your phone.
rmoney said:
Hmm, like the idea...downside is that I have a cracked screen and its very possible I'm going to have to replace this device in the near future. Which I think means I'll have to rebuy sunshine again which is kind of lame.
Click to expand...
Click to collapse
You may want to tackle replacing the screen yourself. It's not all that technical, and as long as you have a few good Torx screwdrivers and pry tool, any decent tinkerer can manage the repair.
I'm wondering how to update 4.4 -> 4.4.4 if I have root/wp-off/bl-unlocked.
OTA update fails to install. TWRP removed, SuperSU superuser removed. OTA still fails.
I really don't want to wipe data, so RSDLite is a last option
mr_const said:
I'm wondering how to update 4.4 -> 4.4.4 if I have root/wp-off/bl-unlocked.
OTA update fails to install. TWRP removed, SuperSU superuser removed. OTA still fails.
I really don't want to wipe data, so RSDLite is a last option
Click to expand...
Click to collapse
What reason is it giving for the failure?
Sent from My Droid Ultra
Caseyk621 said:
What reason is it giving for the failure?
Sent from My Droid Ultra
Click to expand...
Click to collapse
No reason, just says update failed.
mr_const said:
No reason, just says update failed.
Click to expand...
Click to collapse
Run the correct 4.4 FXZ and just delete the line in the XML reading "erase userdata" Then it will install a clean system while keeping all your apps/data. Then it should take the OTA
Hmm, at this point I may just replace my device (I have insurance so its only $100 and then $25 for Sunshine).
But now my concern is the new device coming with 4.4.4, is this supported by Sunshine? I'd rather keep my broken screen rooted phone than have a brand new one thats not rooted.
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?
All,
I'm currently rooted with towelroot. From all that I read, towelroot is the only option that won't take the update. So far, is my only option to unroot, wipe and reflash back to stock? Or there any other other options? I would like to update my radio don't seem like its available to flash yet.
Thanks for any opinion and suggestions.
Nutzzer said:
All,
I'm currently rooted with towelroot. From all that I read, towelroot is the only option that won't take the update. So far, is my only option to unroot, wipe and reflash back to stock? Or there any other other options? I would like to update my radio don't seem like its available to flash yet.
Thanks for any opinion and suggestions.
Click to expand...
Click to collapse
No words.....
If a newer radio (which offers no promise of improved performance) outweighs the desire to have root and bump, then you should use the recovery tool to get your phone back to bone stock and then take the update. There are plenty of threads that talk about how to do this - usually from people that have taken the update and want to get back to where they were. Maybe that should be a sign for you. If you do take the update, don't come back here crying when you realize what you are missing out on....... Good luck.
sic0048 said:
No words.....
If a newer radio (which offers no promise of improved performance) outweighs the desire to have root and bump, then you should use the recovery tool to get your phone back to bone stock and then take the update. There are plenty of threads that talk about how to do this - usually from people that have taken the update and want to get back to where they were. Maybe that should be a sign for you. If you do take the update, don't come back here crying when you realize what you are missing out on....... Good luck.
Click to expand...
Click to collapse
you can get root and bump after the upgrade just use stump root
Thank you all! Will wait it out for a couple more days to see what I will do.
jerrycoffman45 said:
you can get root and bump after the upgrade just use stump root
Click to expand...
Click to collapse
This time, but what about next time? There is no guarantee that root and or bump will ever survive a OTA update.
That is correct from what I have read lolipop will be harder to root and we might not get root
or you could just flash this
http://forum.xda-developers.com/att-lg-g3/development/rom-stock-rooted-att-odexed-d85010f-t2945873
Wickidmasshole said:
or you could just flash this
http://forum.xda-developers.com/att-lg-g3/development/rom-stock-rooted-att-odexed-d85010f-t2945873
Click to expand...
Click to collapse
Arrrghhh! Where was that last night when my laptop and phone were fighting with flash tool over download mode and firmware install? lol.
KennyG123 said:
Arrrghhh! Where was that last night when my laptop and phone were fighting with flash tool over download mode and firmware install? lol.
Click to expand...
Click to collapse
there wouldn't of been a fight if you had waited until 6:46am!!
So I'm running completely stock, never rooted Android 5.0 on my Nexus 5. I got the 5.0.1 update today and when I go to install, it gives me the dead android pic with "error". Anybody else having the same issue? Also, would me enabling developer options have anything to do with it?
P.S. Already cleared my cache partition and it's still giving me the error.
Oh sweet jesus, how many more threads like this we going to have.
You modified /system in some way. Read one of the million threads already here on the forum with similar problem.
beekay201 said:
Oh sweet jesus, how many more threads like this we going to have.
You modified /system in some way. Read one of the million threads already here on the forum with similar problem.
Click to expand...
Click to collapse
or just give it out so we noobs can easily be guided?
beekay201 said:
Oh sweet jesus, how many more threads like this we going to have.
You modified /system in some way. Read one of the million threads already here on the forum with similar problem.
Click to expand...
Click to collapse
Except, like I said, I didn't. I did not root or unlock the bootloader or play around with the phone at all, strictly for this reason. I didn't want to go through the struggle of factory resetting my device every now and then. The closest thing to "modifying" the phone was me unlocking developer settings and I was asking if that could have something to do with it.
Every other thread on the forums has to do with people rooting so no, it's not like one of the millions of other threads.
Describe more.
The best way to update is by flashing the factory image in fastboot, i don`t trust/hate OTA`s personaly
I updated from kitkat to Lollipop with no issues from the OTA update. That was really recent and I haven't changed anything having to do with the system since then. Yet the 5.0.1 update is giving me the error message.
I'm trying to avoid doing a factory reset as that was the main reason that I've kept the phone completely stock. I figured not rooting the phone would let me update in peace and, since it's a nexus, it's been enough to handle my needs without any customization.
kubus908 said:
I updated from kitkat to Lollipop with no issues from the OTA update. That was really recent and I haven't changed anything having to do with the system since then. Yet the 5.0.1 update is giving me the error message.
I'm trying to avoid doing a factory reset as that was the main reason that I've kept the phone completely stock. I figured not rooting the phone would let me update in peace and, since it's a nexus, it's been enough to handle my needs without any customization.
Click to expand...
Click to collapse
Is your bootloader unlocked? I don't know why the ota isn't working but something must have changed on your device
Sent from my Nexus 9 using XDA Free mobile app
jd1639 said:
Is your bootloader unlocked? I don't know why the ota isn't working but something must have changed on your device
Sent from my Nexus 9 using XDA Free mobile app
Click to expand...
Click to collapse
Just double checked and nope, bootloader is locked. Yeah :/ I was trying to see if it's an issue with anybody else on completely stock devices. So far mine is a no go, even though the 5.0 update worked flawlessly. Why would the 5.0 update go through, yet the 5.0.1 believes the system has been modified..?
kubus908 said:
Just double checked and nope, bootloader is locked. Yeah :/ I was trying to see if it's an issue with anybody else on completely stock devices. So far mine is a no go, even though the 5.0 update worked flawlessly. Why would the 5.0 update go through, yet the 5.0.1 believes the system has been modified..?
Click to expand...
Click to collapse
Well, there's a way to get the ota but it is going to be tedious. It involves rooting with towelroot, then using bootunlocker from the play store. That'll allow you to unlock the bootloader without wiping your device. Then you'll need to flash the system, boot, and recovery image with fastboot from the 5.0 factory image. Then do the ota.
Sent from my Nexus 9 using XDA Free mobile app
jd1639 said:
Well, there's a way to get the ota but it is going to be tedious. It involves rooting with towelroot, then using bootunlocker from the play store. That'll allow you to unlock the bootloader without wiping your device. Then you'll need to flash the system, boot, and recovery image with fastboot from the 5.0 factory image. Then do the ota.
Sent from my Nexus 9 using XDA Free mobile app
Click to expand...
Click to collapse
May as well skip the ota if you're going to go through this process.
---------- Post added at 07:06 PM ---------- Previous post was at 07:05 PM ----------
digitLIX said:
or just give it out so we noobs can easily be guided?
Click to expand...
Click to collapse
Or wait for the next time the question is asked.
Should be any minute now.
Thanks! I may just wait until the next update and see if there's a chance it'll work. Or I may just have to do a fresh new install which I am not looking forward to at all Lol. But thank you for your help!
Uhhhh, ok. So I'm not exactly sure what happened. I figured I'd give the OTA another try because why not...and it worked I noticed it downloaded a bigger file too, 30ish mb as opposed to the 13mb OTA that would give me an error. Not sure if I got sent a wrong update file or what, but if your issue comes close to what I experienced, just keep trying the OTA update. I'm also on T-Mobile (phone bought directly from T-Mobile) in case that makes any difference.
Latest DPD1 6.0.1 MM Factory Tar Image
Full System Restore ImagesFully Stock Odin Factory Tar Image (Caution This Will Lock Your Bootloaders And Keep You From Downgrading To KitKat Firmwares)
6.0.1 MM VZW-G900VVRU2DPD1-20160511030450.zip
5.0 KK G900VVRU2BPB1_G900VVZW2BPB1_VZW.zip
5.0 KK G900VVRU2BOK3_G900VVZW2BOK3_VZW.zip
5.0 KK G900VVRU2BOG5_G900VVZW2BOG5_VZW.zip
Full System Restore Images With No Aboot Bootloader For Dev Unlocked Bootloaders
6.0.1 MM PD1_Full_Factory_Restore_No_Aboot.tar.zip
Firmware Only (Bootloader,Modem,Kernel,Recovery)
Modem OnlyVZW_BOK3_MODEM_NONHLOS_ONLY.tar.md5
VZW_BOK3_MODEM_ONLY.tar.md5
Kernel(Boot.img) OnlyVZW_BOK3_KERNEL_ONLY.tar.md5
For Dev. Ed. owners
Here is a full stock tar without the bootloader and without the recovery for Dev. Ed. owners
https://www.androidfilehost.com/?fid=24052804347794573
Just make sure you have SuperSU on your SD card to flash it in recovery after updating to re-root https://download.chainfire.eu/696/SuperSU
This is for Developer Edition owners only
jrkruse said:
BOG5 Factory Tar Images
Fully Stock Odin Factory Tar Image (Caution This Will Lock Your Bootloaders And Keep You From Downgrading To Obtain Root!!)
G900VVRU2BOG5_G900VVZW2BOG5_VZW.zip
Full Stock Odin Factory Tar Image With BOD5 Bootloaders (This Will Allow You To Still Downgrade To Earlier Builds)
VZW_BOG5_RETAIL_FULL_FIRMWARE_WITH_BOD5_BL.tar.zip
Click to expand...
Click to collapse
So if I am on Stock OE1 and flash the second link are you saying I can downgrade to root?
XNO said:
So if I am on Stock OE1 and flash the second link are you saying I can downgrade to root?
Click to expand...
Click to collapse
I'm wondering the same thing. It's been a while since I've heard anything about efforts to downgrade from OE1. I'm unrooted and would so desperately like to root, but unfortunately installed stock OE1 :crying:, and then OG5. I really really hope there will be some method of rooting in my situation. Hating the fact that I bought a device that I can't use the way I'd like because some screwball company thinks people are too stupid to be trusted.
I really appreciate everyone's efforts here. Keep up the wonderful work and keep us updated!
XNO said:
So if I am on Stock OE1 and flash the second link are you saying I can downgrade to root?
Click to expand...
Click to collapse
equazcion said:
I'm wondering the same thing. It's been a while since I've heard anything about efforts to downgrade from OE1. I'm unrooted and would so desperately like to root, but unfortunately installed stock OE1 :crying:, and then OG5. I really really hope there will be some method of rooting in my situation. Hating the fact that I bought a device that I can't use the way I'd like because some screwball company thinks people are too stupid to be trusted.
I really appreciate everyone's efforts here. Keep up the wonderful work and keep us updated!
Click to expand...
Click to collapse
Sorry guys! You can try but Im sure the tar image with the bod5 bootloaders will fail if your already on BOE1 or higher
jrkruse said:
Sorry guys! You can try but Im sure the tar image with the bod5 bootloaders will fail if your already on BOE1 or higher
Click to expand...
Click to collapse
Thanks I found out the hard way LOL. All good now tho.
XNO said:
So if I am on Stock OE1 and flash the second link are you saying I can downgrade to root?
Click to expand...
Click to collapse
I too am interested in this. I lost root and was hoping this version that Verizon installed today would allow me to re-root.
skister77 said:
I too am interested in this. I lost root and was hoping this version that Verizon installed today would allow me to re-root.
Click to expand...
Click to collapse
Oh dear lord, no no no no. Stop asking the same questions repeatedly hoping for a different answer. For the last time, if you are on oe1 and didn't keep the od bootloader, that's it, you're done.
And for the record, why would Verizon release an update that would re-allow to root? Why would that ever happen intentionally?
skister77 said:
I too am interested in this. I lost root and was hoping this version that Verizon installed today would allow me to re-root.
Click to expand...
Click to collapse
ldeveraux said:
Oh dear lord, no no no no. Stop asking the same questions repeatedly hoping for a different answer. For the last time, if you are on oe1 and didn't keep the od bootloader, that's it, you're done.
And for the record, why would Verizon release an update that would re-allow to root? Why would that ever happen intentionally?
Click to expand...
Click to collapse
To add to what ldeveraux wrote, your question was literally answered two posts above yours. Does anyone even bother to read anything anymore? Or is it that reading comprehension is completely a thing of the past?
ldeveraux said:
Oh dear lord, no no no no. Stop asking the same questions repeatedly hoping for a different answer. For the last time, if you are on oe1 and didn't keep the od bootloader, that's it, you're done.
And for the record, why would Verizon release an update that would re-allow to root? Why would that ever happen intentionally?
Click to expand...
Click to collapse
Stuff happens. Maybe somebody made a mistake.
Sent from my SM-G900V using XDA Free mobile app
DraconicSeed said:
Stuff happens. Maybe somebody made a mistake.
Sent from my SM-G900V using XDA Free mobile app
Click to expand...
Click to collapse
It's true that mistakes can happen, but once they patch the bootloader to prevent downgrading, they don't actually have to touch it again. So if they don't change anything in it, then the chance of breaking it is slim to none. Not to mention this update didn't do much anyways.
[/COLOR]
ldeveraux said:
Oh dear lord, no no no no. Stop asking the same questions repeatedly hoping for a different answer. For the last time, if you are on oe1 and didn't keep the od bootloader, that's it, you're done.
And for the record, why would Verizon release an update that would re-allow to root? Why would that ever happen intentionally?
Click to expand...
Click to collapse
So just to be clear Ideveraux, because I don't quite understand, are you saying OE1 is not rootable but OG5 has a chance?
Spartan117H3 said:
It's true that mistakes can happen, but once they patch the bootloader to prevent downgrading, they don't actually have to touch it again. So if they don't change anything in it, then the chance of breaking it is slim to none. Not to mention this update didn't do much anyways.
Click to expand...
Click to collapse
It involved a security update so I was hoping maybe someone messed up somewhere :silly: one can hope. I purchased my phone with OE1 already installed so I was kinda screwed from the ground up and going from an S4 rooted running TWRP and a Hyperdrive ROM to a stock unrooted bloated phone rubs me harsh lol
XNO said:
So just to be clear Ideveraux, because I don't quite understand, are you saying OE1 is not rootable but OG5 has a chance?
Click to expand...
Click to collapse
Anything OE1 or higher cannot be rooted. OG5 is higher than OE1, and therefore has the same issues for people who want to root that OE1 has. OE1 has a bootloader that disallows downgrading of firmware which is required to root these phones. The only way you can still downgrade OE1/OG5 is if you came from a rooted phone and did NOT take OTA OE1/OG5, and flashed a firmware that did not change the bootloader.
DraconicSeed said:
It involved a security update so I was hoping maybe someone messed up somewhere :silly: one can hope. I purchased my phone with OE1 already installed so I was kinda screwed from the ground up and going from an S4 rooted running TWRP and a Hyperdrive ROM to a stock unrooted bloated phone rubs me harsh lol
Click to expand...
Click to collapse
The stagefright that was incompletely patched was apparently 4 lines of code somewhere in one of the system files, wouldn't be in the bootloader. I understand the sentiments, I would have returned the phone immediately in your case. I'm already running out of patience even being rooted, with the locked bootloader and whatnot. Trying to patiently wait for the Nexus 6 2015 this year.
Spartan117H3 said:
Anything OE1 or higher cannot be rooted. OG5 is higher than OE1, and therefore has the same issues for people who want to root that OE1 has. OE1 has a bootloader that disallows downgrading of firmware which is required to root these phones. The only way you can still downgrade OE1/OG5 is if you came from a rooted phone and did NOT take OTA OE1/OG5, and flashed a firmware that did not change the bootloader.
The stagefright that was incompletely patched was apparently 4 lines of code somewhere in one of the system files, wouldn't be in the bootloader. I understand the sentiments, I would have returned the phone immediately in your case. I'm already running out of patience even being rooted, with the locked bootloader and whatnot. Trying to patiently wait for the Nexus 6 2015 this year.
Click to expand...
Click to collapse
Thanks Spartan, I'm just messing with ldeveraux because all i ever read from him is negative comments like he is super annoyed at everyone asking questions.
XNO said:
Thanks Spartan, I'm just messing with ldeveraux because all i ever read from him is negative comments like he is super annoyed at everyone REPEATING questions.
Click to expand...
Click to collapse
FTFY
XNO said:
Thanks Spartan, I'm just messing with ldeveraux because all i ever read from him is negative comments like he is super annoyed at everyone asking questions.
Click to expand...
Click to collapse
It has been repeated a million times though, in basically every "recent" thread so I can see why people would be frustrated. The issue is, the more people post the same questions, the more hidden the important questions get, leaving people even less likely to read/search the thread for their answers. Just basic forum etiquette IMO. I'm just a little more patient at times answering questions, that's all.
Verizon s5
Spartan117H3 said:
Anything OE1 or higher cannot be rooted. OG5 is higher than OE1, and therefore has the same issues for people who want to root that OE1 has. OE1 has a bootloader that disallows downgrading of firmware which is required to root these phones. The only way you can still downgrade OE1/OG5 is if you came from a rooted phone and did NOT take OTA OE1/OG5, and flashed a firmware that did not change the bootloader.
The stagefright that was incompletely patched was apparently 4 lines of code somewhere in one of the system files, wouldn't be in the bootloader. I understand the sentiments, I would have returned the phone immediately in your case. I'm already running out of patience even being rooted, with the locked bootloader and whatnot. Trying to patiently wait for the Nexus 6 2015 this year.
Click to expand...
Click to collapse
well it sounds like to me everybody in the computer world cannot find a way to unlock the bootloader that is on OE1 or higher I'm thinking surely there's somebody out there that can figure out a way to do it so I would be able to contain root against
trucker950 said:
well it sounds like to me everybody in the computer world cannot find a way to unlock the bootloader that is on OE1 or higher I'm thinking surely there's somebody out there that can figure out a way to do it so I would be able to contain root against
Click to expand...
Click to collapse
There was an $18,000 bounty for a root method and bootloader unlock before one came out. Geohot used Pinkie Pie's findings of an exploit in all Linux kernels to create his root. He now works for Google's Project Zero and isn't allowed to provide root, and even if he was allowed, he probably doesn't care anymore. That exploit has since been patched, hence the need to downgrade to apply Towelroot. Since then, Verizon has blocked the ability to downgrade.
Notes: Bootloader is still locked despite the length of time this phone has been out. This phone is also "dying" and support is mostly gone considering many of the devs went to other devices/new S6, or devices/carriers that don't have this locked bootloader issue. Look at the Note forum. There's still not even a real root for them, they have a temporary one the last time I checked.
So no. Not only are few people looking if they are at all, but support of this phone from Verizon is probably gone as well. This OG5 is more of a mandatory security patch than a new update. 5.0 is most likely the last version for Verizon's S5 (I'd be surprised if they released 5.1/5.1.1).
Spartan117H3 said:
There was an $18,000 bounty for a root method and bootloader unlock before one came out. Geohot used Pinkie Pie's findings of an exploit in all Linux kernels to create his root. He now works for Google's Project Zero and isn't allowed to provide root, and even if he was allowed, he probably doesn't care anymore. That exploit has since been patched, hence the need to downgrade to apply Towelroot. Since then, Verizon has blocked the ability to downgrade.
Notes: Bootloader is still locked despite the length of time this phone has been out. This phone is also "dying" and support is mostly gone considering many of the devs went to other devices/new S6, or devices/carriers that don't have this locked bootloader issue. Look at the Note forum. There's still not even a real root for them, they have a temporary one the last time I checked.
So no. Not only are few people looking if they are at all, but support of this phone from Verizon is probably gone as well. This OG5 is more of a mandatory security patch than a new update. 5.0 is most likely the last version for Verizon's S5 (I'd be surprised if they released 5.1/5.1.1).
Click to expand...
Click to collapse
You couldn't have summed up the S5 situation any better. Cheers!