[Info] Rooted user? Learn to update properly

Search This thread

Cirkustanz

Senior Member
May 5, 2010
301
81
I was thinking about going back to stock for the update, but that definitely sounds like too much of a hassle now. I will definitely be waiting for a flashable one now.

I could be grossly misinterpreting what I have been reading, but it seems like there won't really be a flashable upgrade this time around. And by "flashable" I am assuming you are referring to the one .zip packages you simply load in custom recovery with a stock/rooted/custom recovery enabled phone. Every indication from posts from people that are running 5.0 now are pretty much from those who used the factory image. Not that there is anything wrong with that...I thought about using that method this time around, it doesn't scare me at all as I'm quite familiar with ADB...however, I just don't like how at the time that I write this...it specifically mentions to use Chainfire autoroot. (there are instructions also posted about 5.0 rooting that do not use chainfire autoroot, but from my prior experience I've learned to be patient and wait for an updated, revised instructions that has plenty of feedback...and my number one rule is do not combine methods)

But hey, that's just me. I'm the kind of person who only shows up on the forums anymore whenever there's a new update... :)

Edit to this...I saw this post...

http://xdaforums.com/google-nexus-5/help/updating-to-l-stock-root-t2938049

and decided to give it a whirl. I do see that Bedon292 has mentioned in the dev preview thread a TWRP flashable upgrade is being worked on. Which makes me laugh, because since I alluded to my having patience before...I am probably jinxing myself into having a problem.

And yes...you will lose root if you do this. Obviously, because the system.img is rooted...but getting root and custom recovery back only takes a minute.
 
Last edited:
  • Like
Reactions: FunDionysus

Bedon292

Member
Oct 4, 2011
6
1
The people over in Dev Preview Thread are working on a flashable one right now, but its not quit ready yet.

I just ended up going with Pure White though. Its close enough for the time being.

I have just had bad luck getting adb to even see my device, so I try to stick with flashable one to not worry about it.
 

TheLastSidekick

Inactive Recognized Contributor
Aug 4, 2012
3,782
2,536
The people over in Dev Preview Thread are working on a flashable one right now, but its not quit ready yet.

I just ended up going with Pure White though. Its close enough for the time being.

I have just had bad luck getting adb to even see my device, so I try to stick with flashable one to not worry about it.
I did too even when the drivers were installed. The best advice I can give you is try multiple USB cables. Some will work, others will not. A BlackBerry data cable did the trick for me, as well as a Nexus 7 (2012) cable.
 

TheLastSidekick

Inactive Recognized Contributor
Aug 4, 2012
3,782
2,536
Adb has nothing to do with flashing stock ROMs. You would use Fastboot.
Thanks for the clarification, I was tired and forgot to say this myself. But ordinarily if you cannot use adb, your device won't be detected so you cannot use fastboot. So first, it is very important that he find the right cable and drivers.
@Bedon292

To clarify, fastboot menu is the menu you get by holding power + volume down (whilst your phone is down)...if your phone hasn't booted into Android you're more than likely unable to use adb unless its a special feature in a recovery.

adb is for pushing things into your phone and moving them

Fastboot is for writing factory images and even recoveries and bootloaders. Flash-all.bat on Windows auto writes the factory image to your device and performs the actual wipes.

And a friendly tip man, learn adb and fastboot. They truly come in handy. Don't be afraid of it, solve the connection problem and get cracking!
 
Last edited:
  • Like
Reactions: exhibit1234

Bedon292

Member
Oct 4, 2011
6
1
Thank you for the clarification about adb v fastboot, I did not actually fully understand the difference. I am mostly a lurker and just try to keep my phone rooted with the latest features.

I have never bothered to try multiple cables, I just used the first one I came across. I figured if it shows up in windows at all there should be no problem, yet I have had problems in adb. Although, I do think I might have been trying to connect with adb in the fastboot menu, so that would probably be my issue. I will try to play with it all tonight and see what I can do.
 
  • Like
Reactions: TheLastSidekick

evertking

Senior Member
May 25, 2013
767
130
thanks!

This thread is what I been needing to read. Ok... Here is my way of thinking and it goes back to when I had my s3. That after rooting and going on a ROM flashing spree with my S3.. I was told that after time its wise to return to stock(Odin) and it had to do with memory blocks or something? * I'm new to this* but after reading this I understand that using fastboot has no advantages to using TWRP? .... Both will "clean" and install and the end result will be the same? Just that the prerooted 5.0 flashable zip is a rooted way to do it? And save yourself time and useless steps, right? I just want a clean install. Hell, I just may stick to Slim and wait for their update!
Thanks for taking the time to write this up and being patient with the confused:silly:
 
Last edited:

danarama

Senior Member
Aug 22, 2010
31,277
18,811
Oxenhope, West Yorkshire, UK
This thread is what I been needing to read. Ok... Here is my way of thinking and it goes back to when I had my s3. That after rooting and going on a ROM flashing spree with my S3.. I was told that after time its wise to return to stock(Odin) and it had to do with memory blocks or something? * I'm new to this* but after reading this I understand that using fastboot has no advantages to using TWRP? .... Both will "clean" and install and the end result will be the same? Just that the prerooted 5.0 flashable zip is a rooted way to do it? And save yourself time and useless steps, right? I just want a clean install. Hell, I just may stick to Slim and wait for their update!
Thanks for taking the time to write this up and being patient with the confused:silly:
Pretty much covers it.
 
  • Like
Reactions: evertking

Mouchoir

Senior Member
Nov 13, 2014
52
4
Paris
Hello,

Thanks for you usefull thread.

However, I'm kinda noob, and I don't really know what to do : to root my Nexus 5 (4.4.4), I used Towelroot by Geohot.
How do I upgrade to Lollipop ? I must say, I don't have any updates avaliable in my settings (which would be OTA one if I understood everyting)

Thanks a lot

EDIT: Sorry for being noobish :/
 
Last edited:

danarama

Senior Member
Aug 22, 2010
31,277
18,811
Oxenhope, West Yorkshire, UK
Hello,

Thanks for you usefull thread.

However, I'm kinda noob, and I don't really know what to do : to root my Nexus 5 (4.4.4), I used Towelroot by Geohot.
How do I upgrade to Lollipop ? I must say, I don't have any updates avaliable in my settings (which would be OTA one if I understood everyting)

Thanks a lot

EDIT: Sorry for being noobish :/
Do you want root again?
 

deusfaux

Senior Member
Dec 12, 2010
214
40
Your OP doesn't seem to explain why using an OTA is not ideal in a case like mine

stock, rooted.

So why wouldn't I want to use the OTA to update everything, and prevent a wipe? Because I have to re-root after which takes all of a couple minutes? That's how I've done it all along the Nexus line so far. I don't see any great waste of time or explanation why it's a poor route to take.
 

bb709394

Senior Member
Mar 16, 2012
117
39
Hello,

Thanks for you usefull thread.

However, I'm kinda noob, and I don't really know what to do : to root my Nexus 5 (4.4.4), I used Towelroot by Geohot.
How do I upgrade to Lollipop ? I must say, I don't have any updates avaliable in my settings (which would be OTA one if I understood everyting)

Thanks a lot

EDIT: Sorry for being noobish :/

Follow these instructions: post #1, http://xdaforums.com/google-nexus-5/general/how-to-download-flash-android-5-0-t2937941. It is a nice summary of the steps involved (it is very easy to follow). Happily rooted L user! There is no need to wait for an OTA =)
 

Prancuzas

Member
Jan 23, 2012
46
1
Kaunas
So as far as I understand pre-rooted img that can be flashed via custom recovery will be out in a few days? I'm stock rooted but want to avoid cables, adb comands and oneclickeoot toolkits :)
 

r3volution327

Member
Oct 3, 2013
22
8
I have always just flashed ROM.zips, and by now there are quite a few stable builds out there. Please correct me if I'm wrong but I'm under the impression that a ROM.zip does not touch the radio or the bootloader. So I pulled those out of the image package and flashed them via fastboot. So with that being done, and a 5.0 ROM.zip, did I get it all or is there something I'm still missing?
 

Top Liked Posts

  • There are no posts matching your filters.
  • 104
    *The below post covers up to 4.4.4 only. for 5.0, read this thread: http://xdaforums.com/google-nexus-5/general/5-0-basic-overview-root-options-lollipop-t2947144*

    012.png


    I see a lot of threads asking about updating to Lollipop and about returning to stock to receive OTA updates.. from rooted users.

    I have created this thread as I have strong feelings about rooted users and OTA's in general, so I wanted to collect my thoughts together in a single thread to hopefully persuade rooted users to avoid OTA updates. Of course, you're free to choose to ignore this.
    010.png

    022.png


    OTA's are simple for unrooted, noob users. They are minimal effort, quick and require no knowledge. However they have a propensity to go wrong - often resulting in a user having to factory reset to get things working.

    OTA's are designed to be small to save on data usage. This is achieved by not supplying the entire ROM, kernel or app, but instead, including patches. These patch files (*.p) will unpack the recovery.img, bootloader.img, boot.img or *.apk and insert the new code into it. This means the OTA expects an exact version to install. You cannot skip an OTA and expect to apply a later one because the code in the patch might not "fit". Also, this is why modified users cannot apply an OTA. There are ways for rooted, stock kernel, no modification users to apply OTA updates but it is not recommended

    Please note, rooted users will still receive the OTA notification. You do not need to apply it though. Some Custom ROMS even receive it.
    020.png

    032.png


    Well if you are modified, you have to first return completely to stock to apply an OTA. This is a relatively long process compared to other options available to you. If you are simply rooted with stock kernel and no modifications, you can simply re-apply root after accepting the OTA, but it's a bit messy and still - it's an OTA that can go wrong. I think part of OTA's appeal is you can do it anywhere - but this is also it's biggest problem. rooted users need resources to be available to them so they can remedy whatever needs remedying after application.

    In short, it's just not the best option, Why would anyone ever choose "not the best"?
    030.png

    042.png


    It all depends what you want to keep going forward.

    I don't want root or custom recovery

    If you no longer want root, simply return to stock using google's factory images. The factory image package contains all the files needed to return to stock:

    - boot.img
    - recovery.img
    - bootloader.img
    - system.img
    - cache.img
    - userdata.img
    - radio.img

    It also includes a windows batch file (.bat) and a Linux shell script (.sh) that will automate the above. This will wipe your data.

    If you don't want to lose your sdcard data, if you have a custom recovery, you can factory reset, fastboot flash individually the recovery.img, system.img and boot.img as this will keep /data partition in tact, which is where your /sdcard is located

    I want to keep root

    You have a couple options here.

    You could like above, fastboot flash individually the system.img and boot.img (not recovery.img) then reflash supersu from your custom recovery. Please note, with lollipop as of now, you need as special modified boot.img, not the stock one - so this still is not the quickest method.

    Alternatively, you can flash a pre-rooted zip*. Within a couple of hours of the factory image becoming available, guys from XDA will release pre-rooted zips that you simply flash from a custom recovery. This will be a quick process. Put the zip on your /sdcard, boot into recovery and flash it.

    With both these options, you very well may need to factory reset after flashing roms, especially if it's a version jump - just as you may need to do with an OTA update. The benefit of being rooted however, is that you can use titanium backup to backup your apps and take a Nandroid backup too, rooted users upgrading should keep these available on the sdcard before updating.
    *Please note with Android 5.0 Lollipop, you need to flash a ROM.zip, Permissive kernel and SuperSU all at once. You have to download all 3 files and flash them one after the other in that order. You can flash some custom kernels, such as elementalx straight over permissive kernel. Also, you can ONLY flash elementalX as it allows root to run at boot (without permissive kernel) however, some apps NEED permissive to run anyway
    040.png

    052.png


    OTA is designed for noobs. Granted, those root users asking how to return to stock or thinking OTA is the only update method available - are also noobs... If you're going to be rooted, you should understand what you have and what it means to be rooted. Familiarise yourselves with fastboot. Familiarise yourself with your recovery. Learn how to take backups and you will get much more out of your phone that constantly wasting time returning to stock, applying OTA's then re-rooting. You're wasting time doing this - it's a fools errand. I hope this thread helps to open your eyes and your minds.

    If you still want to (return to stock in order to) accept OTA updates, even after reading this thread (perhaps because doing things properly mean more work for you) then perhaps you shouldn't be rooted. Having, maintaining and understanding root takes effort and if you're not willing to put the time in, you will become a danger to your phone and possibly a drain on this forum too ;) We write lots of guides and info threads for your benefit. If you have questions, please just ask.
    050.png

    062.png


    adb and fastboot. What is it? How can it help you? - basic information about adb and fastboot (by @rootSU)

    All you need to know about Android | Read this before you post/root ! - Understand the basics before you root (by @abaaaabbbb63 )

    How to flash a factory image | Return to stock | Unroot/SAVE your Nexus 5 - Understand how to undo whatever you do before you root (by @abaaaabbbb63 )

    OTA Help-Desk - Understand how OTA's work and what this means if you are rooted (by @Sandman-007)
    060.png
    4
    Hi! Thanks for great explanation. I've question regarding that part:

    Do you have exact link to topic with such ROM images? There are a lot of them and I am not sure where should I look for updates... Thanks in advance!

    The factory image of official is not available yet for Lollipop. There are links to pre-rooted zips available in "sticky roll-up" thread in general forum. These threads will be updated when official. If the threads are not updated, I will put new links up.
    3
    You can't flash ota with twrp.... Or let the Ota install automatically.

    You need stock recovery.
    That is not correct.

    I'm not sure why some insist on making things difficult...
    Because in many cases it doesn't make things difficult.

    In the context of what the OP was trying to say with respect to using OTA updates IFF (i.e., if and only if) you have modified your system files and are trying to return to stock solely to accept an OTA, then yes, in that specific case, the OTA update method is not for you, as it is the "long way around".

    However, if you have not modified your system files, then the OTA update method is much easier and faster. Flashing a stock ROM zip or using fastboot is the "long way around". And in this case, flashing an OTA update is not subject to having more issues than flashing a ROM zip or anything else.

    Things don't fall into a simplistic paradigm of good/bad or easy/difficult. It depends on the situation, and that's the point that hasn't been getting across in general.
    3
    Thanks for this - I am rooted and have a basic knowledge of fastboot from unlocking and rooting the N5 last year and the N4 before that.. however, as I've not touched it for about that long it's probably about time I start the reading process again to get ready for some Lollipop action!

    I had been planning on getting the factory images from Google and using fastboot to fresh flash it - looks like that's not really necessary tho?

    Thanks ;)

    ...sent from the Nexus 5000

    If you want to keep root, The best thing to do would be to wait for a pre-rooted rom.zip - which should also contain the custom boot.img needed to give root permissions...

    Just make sure you do all your backups first if you want to keep stuff.
    3
    Adb has nothing to do with flashing stock ROMs. You would use Fastboot.