Database Info

[Q] Rooted and unlocked bootloader

Hi Everyone,
I am new in XDA with Nexus 5 mobile, i am wondering can i update my rooted and unlocked bootloader Nexus 5 through OTA with stock rom and stock kernal? Thanks Everyone

Duckone said:
Hi Everyone,
I am new in XDA with Nexus 5 mobile, i am wondering can i update my rooted and unlocked bootloader Nexus 5 through OTA with stock rom and stock kernal? Thanks Everyone
Click to expand...
Click to collapse
Yes, you will receive and be able to install the OTA (if you also have the stock recovery) but you will loose root though.

Thanks alot for your kind reply.

This is all covered in the "ota helpdesk" thread stuck at the top of this general forum.
Always read stickies before asking questions... including the one that says not to ask questions in the general forum
-----------------------
Sent via tapatalk.
I do NOT reply to support queries over PM. Please keep support queries to the Q&A section, so that others may benefit

rootSU said:
This is all covered in the "ota helpdesk" thread stuck at the top of this general forum.
Click to expand...
Click to collapse
The Helpdesk thread must have been un-stickied in the last few days, because I saw you give this answer several times but had to go digging to find it myself.
There's conflicting information out there -- I've spent hours reading posts here but have had some places tell me that I *can't* get an OTA update when rooted, while some tell me that I *can*. I think the nuance is the problem. It sounds like OTA will work, but only if you haven't changed any system files, and also will wipe out your root and custom recovery. Still, I'd rather have to re-root than to manually update.
The best solution is the one that gets me from "rooted, stock version X" to "rooted, stock version X+1" in the least amount of time!

Ghengis042 said:
...I'd rather have to re-root than to manually update...
Click to expand...
Click to collapse
Actually, flashing the stock image yourself is quite easy and can be less problematic.

PhilipTD said:
Actually, flashing the stock image yourself is quite easy and can be less problematic.
Click to expand...
Click to collapse
Good to know. So, I'm getting an N5 in the next week or two (shipped today, but has to be forwarded overseas by a relative ) and want it rooted, stock. Best bet is to OTA update (if it doesn't ship with 4.4.2) -> unlock bootloader -> install CWM -> install SuperSU? Then, next time Google issues an update, download the OTA ZIP and install it from CWM?
Won't that remove CWM and root, like I was saying? Or is there some version of the "stock image" I can download that doesn't overwrite recovery and/or the su binary/APK?

What you've said is correct, and then after an OTA just reflash CWM* and then re-root it - takes all of 30 seconds if you have the image on your computer
*CWM might give you the option of removing the stock recovery reflash script before rebooting, so say yes to it if it mentions it

Ghengis042 said:
... Or is there some version of the "stock image" I can download that doesn't overwrite recovery and/or the su binary/APK?
Click to expand...
Click to collapse
Take a look here.

PhilipTD said:
Actually, flashing the stock image yourself is quite easy and can be less problematic.
Click to expand...
Click to collapse
I am new to Android, so i would like to ask more before root, that would be less problem
BTW thanks for everyone's reply

adb Nexus tool kit help

Night folks
I have an Nexus 5. I'm trying to update the OS to 4.4.4 using NEXUS TOOL KIT (Last released version). But When the tool kit makes its way by cheking my ADB STATUS it gets an error saying I must turn on Debugging opitions and stuff but i've aready done that! and all the other procedures and still I cant get it to work!
My device:
Nexus 5 D821
Ktu84M
Xposed
franco Kernel
Please Guys, if u can help on something. Let me know
x Chowder

x Chowder said:
Night folks
I have an Nexus 5. I'm trying to update the OS to 4.4.4 using NEXUS TOOL KIT (Last released version). But When the tool kit makes its way by cheking my ADB STATUS it gets an error saying I must turn on Debugging opitions and stuff but i've aready done that! and all the other procedures and still I cant get it to work!
My device:
Nexus 5 D821
Ktu84M
Xposed
franco Kernel
Please Guys, if u can help on something. Let me know
x Chowder
Click to expand...
Click to collapse
As many people will soon comment, toolkits aren't recommended by people on here. Short explanation: they don't teach people the process which keeps people from solving simple issues. Seeing as you're using a custom kernel I would flash the factory image of 4.4.4. There's also a thread currently in the general forum about an auto updater which might help me you out as well.

Rooted users should flash a rooted stock zip. It's the easiest and quickest method. Link in my signature under resources section
Sent from my Nexus 5 using Tapatalk

Thank u very much guys. So I'm supposed to flash the ROM through recovery. Will my data be wiped?
Sent from my Nexus 5 using XDA mobile app

x Chowder said:
Thank u very much guys. So I'm supposed to flash the ROM through recovery. Will my data be wiped?
Sent from my Nexus 5 using XDA mobile app
Click to expand...
Click to collapse
If its the one from my signature under the resources section, its just a rom It doesnt wipe. Flashing zips via recovery doesnt wipe the data unlike flashing factory images. In fact factory images only wipes data if you flash the userdata.img (which happens if you use the flash-all.bat) but if yo just flash system.img and boot.img, it doesnt wipe anything, although rooted users are best using the zip anyway

rootSU said:
If its the one from my signature under the resources section, its just a rom It doesnt wipe. Flashing zips via recovery doesnt wipe the data unlike flashing factory images. In fact factory images only wipes data if you flash the userdata.img (which happens if you use the flash-all.bat) but if yo just flash system.img and boot.img, it doesnt wipe anything, although rooted users are best using the zip anyway
Click to expand...
Click to collapse
Sorry to ask but, What is ODEX and DEODEX ?? Does it have anything to do w/ AOSP?
Sorry mate but I'm sort of a complete noob

x Chowder said:
Sorry to ask but, What is ODEX and DEODEX ?? Does it have anything to do w/ AOSP?
Sorry mate but I'm sort of a complete noob
Click to expand...
Click to collapse
Stock is odexed
When you install an app from play, those apps default settings are stored dalvik-cache however apps that come with a ROM use .odex files instead.
With a deodexed ROM , the apps that come with the ROM also use dalvik-cache.
Sent from my Nexus 5 using Tapatalk

rootSU said:
Stock is odexed
When you install an app from play, those apps default settings are stored dalvik-cache however apps that come with a ROM use .odex files instead.
With a deodexed ROM , the apps that come with the ROM also use dalvik-cache.
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Adding some more info, deodexed ROM's or apps allow for easier theming, with a (questionable or not) small performance loss.

beekay201 said:
Adding some more info, deodexed ROM's or apps allow for easier theming, with a (questionable or not) small performance loss.
Click to expand...
Click to collapse
True. I ALWAYS go for deodexed as it's easier for theming and mods, This excludes xposed however. There may be a small perormance hit being deodexed, but customisation wins out for me.
That said, those wanting stock experience should stick with odexed

rootSU said:
True. I ALWAYS go for deodexed as it's easier for theming and mods, This excludes xposed however. There may be a small perormance hit being deodexed, but customisation wins out for me.
That said, those wanting stock experience should stick with odexed
Click to expand...
Click to collapse
Performance difference is way too slight to notice on the Nexus 5, it's only a bit noticeable on low-end/old devices. Might as well be going for deodexed.

How to upgrade to LP 5.01 (Stage Fright Patch) w/o wiping data or reflashing recovery

This is an upgrade pathway that worked well for me in upgrading to 5.0.1 originally from KK as I described in THIS post. All the same thanks go out for the original ideas and guidance to: dottat, Dees Troy, and Darth.
The same method works. Even if you're S-OFF, the trick is following the S-ON instructions...that's it.
Find the latest S-ON RUU and instructions HERE.
The latest TWRP (for the HTC One M8) HERE.
The latest SuperSU per the instructions HERE.
Install the S-on 5.0.1 RUU by whatever method you chose from the link above. I used the fastboot method and it did a great job upgrading the stystem. Most importantly, it did NOT wipe my data. You can also use the htc_fastboot.exe in it's extraction directory for all subsequent fastboot operations [highly recommended]. It will reboot and take at least 5 minutes to update all of your applications. At first, it looks like it hangs on the Verizon splash for a minute or three, then it shows you the upgrade of your applications with a count up. How long it takes depends on how many applications you have and how large they are.
Follow the guides to install TWRP and reinstall SuperSU for root. (step 5) I went to the new TWRP page (step 2) and loaded mine by fastboot, then used the new TWRP to flash SuperSU as described.
If you haven't taken the OTA, that should take care of the upgrade nag screens and keep your data intact. If you have, keep reading.
REMINDER: to reflash any tweaks. My favorite package is HERE at the bottom of the links list. It has just about everything I like.
ADDITIONAL INFO FROM dotatt
You also would be wise to note if the user was already getting nagged for the ota they will still be nagged about it even after upgrading this way. Couple more steps needed
Click to expand...
Click to collapse
AND HIS DESCRIPTION VIA PM
If the user doesn't download the OTA and defer it they might be able to get away with it. Once the file is downloaded (and it goes in /cache) the user will need to wipe cache to delete the actual file as well as go into app manager and clear data on the htcdm app. When they enter the software update screen again it should check and show no updates available instead of asking when to install the deferred update.
Click to expand...
Click to collapse
Click to expand...
Click to collapse
If you need to get rid of the nag screen, the update files, and clear htcdm data, you may be able to use THIS (M8vzw OTA Killer updated for Lollipop) tool.

I have a problem and need help, maybe you can help. I was stock but was s-off and took the stage fright update and phone did all the update and when the phone booted it did not go past the Verizon bootup screen, can anybody help me with this? Thanks you.
Sent from my Nexus 6 using Tapatalk

luvtorev01 said:
I have a problem and need help, maybe you can help. I was stock but was s-off and took the stage fright update and phone did all the update and when the phone booted it did not go past the Verizon bootup screen, can anybody help me with this? Thanks you.
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
I answered your other post. Please only post for help in one thread. Thanks.
Sent from my Nexus 6 using Tapatalk

Thanks for keeping your eyes open, dottat. Good reminder that he'll have to reflash TWRP and SuperSU though. And, he'll have to reflash any tweaks.

homers1 said:
Thanks for keeping your eyes open, dottat. Good reminder that he'll have to reflash TWRP and SuperSU though. And, he'll have to reflash any tweaks.
Click to expand...
Click to collapse
You also would be wise to note if the user was already getting nagged for the ota they will still be nagged about it even after upgrading this way. Couple more steps needed ?
Sent from my Nexus 6 using Tapatalk

Big problem can't sideload

Hello.
Somewhere in my process of rooting my nexus 5 after flashing android 6.0
I must have done a big misstake, It's stuck at loading after I installed SuperSu.
I normal cases i would just sideload in cm or something and make it all over, but now i can't even install nexus 5 drivers on my computer when it's in bootloader
Any ideas what to do?
And no i was so stupid that I didn't make a recovery..
I hope you can help me / MrBerit

Use Nexus Root Toolkit if u have windows, and use Advanced tools to force the flash, if u have Linux u shouldn't need to reinstall the drivers
Sent from my Nexus 6 using Tapatalk

Try to search for wug's toolkit or skipsoft toolkit for nexus devices here in the forums, what you just need to do is download the firmwar foryour device(you will get a confirmation for that) and then on bootloader jush flash it. There are instructions there and it should be easy enough to navigate around

Oh ffs stop suggesting toolkits to people who clearly don't know what they are doing!
@MrBerit , are you sure its bootlooping after flashing SuperSU? How long did you wait for? What SuperSU version are you flashing?
Sent from my Nexus 10 using Tapatalk

MrBerit said:
Hello.
Somewhere in my process of rooting my nexus 5 after flashing android 6.0
I must have done a big misstake, It's stuck at loading after I installed SuperSu.
I normal cases i would just sideload in cm or something and make it all over, but now i can't even install nexus 5 drivers on my computer when it's in bootloader
Any ideas what to do?
And no i was so stupid that I didn't make a recovery..
I hope you can help me / MrBerit
Click to expand...
Click to collapse
There are many previous posts which advised that if you install supersu on 6. O it will cause a boot loop. Unless, you have installed before hand the special kernel that allows it

funnel71 said:
There are many previous posts which advised that if you install supersu on 6. O it will cause a boot loop. Unless, you have installed before hand the special kernel that allows it
Click to expand...
Click to collapse
Indeed, it's all over latest pages on SuperSu thread. I figured, since this always happens every time a new major version comes out, and users come in like where's ma r00t access... "Chainfire probably already has a beta going against M", I thought.
But yeah, in short, root needs SuperSU (beta) and kernel support.
Sent from my Nexus 10 using Tapatalk

soupysoup said:
Use Nexus Root Toolkit if u have windows, and use Advanced tools to force the flash, if u have Linux u shouldn't need to reinstall the drivers
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
This solved my problem thx ^^
phantom146 said:
Try to search for wug's toolkit or skipsoft toolkit for nexus devices here in the forums, what you just need to do is download the firmwar foryour device(you will get a confirmation for that) and then on bootloader jush flash it. There are instructions there and it should be easy enough to navigate around
Click to expand...
Click to collapse
thx ^^
beekay201 said:
Oh ffs stop suggesting toolkits to people who clearly don't know what they are doing!
@MrBerit , are you sure its bootlooping after flashing SuperSU? How long did you wait for? What SuperSU version are you flashing?
Sent from my Nexus 10 using Tapatalk
Click to expand...
Click to collapse
I have been rooting for servral years, but after android 5.0 i did like it as it was, I was flashing 6. ***-
It was stil in bootloop this morning so around 6 h.
beekay201 said:
Indeed, it's all over latest pages on SuperSu thread. I figured, since this always happens every time a new major version comes out, and users come in like where's ma r00t access... "Chainfire probably already has a beta going against M", I thought.
But yeah, in short, root needs SuperSU (beta) and kernel support.
Sent from my Nexus 10 using Tapatalk
Click to expand...
Click to collapse
Yeah i Guess i will have to wait until a beta comes out for it, if i not installing paranoid android against..

MrBerit said:
This solved my problem thx ^^
thx ^^
I have been rooting for servral years, but after android 5.0 i did like it as it was, I was flashing 6. ***-
It was stil in bootloop this morning so around 6 h.
Yeah i Guess i will have to wait until a beta comes out for it, if i not installing paranoid android against..
Click to expand...
Click to collapse
I have successfully rooted on 6.0 using HellsGod kernel and SuperSU 2.50, there is also a v2.51 and 2.52 out now that I haven't flashed yet, I still have Android Pay access, I did loose it when I changed dpi, but once I put the stock build.prop back it was fine again, my advice would be to do like I did, root and install twrp, flash XtraSmooth 6.0 ROM, download the factory image from Google and flash the system.img, bootloader, and radio. That will give u the latest non rooted stick image. From there flash SuperSU in twrp and you will be rooted no problem
Sent from my Nexus 6 using Tapatalk

@MrBerit if you used the toolkit to flash you can use it to root Marshmallow. I used it to root and it went fine. Just ensure that you have the latest updates for the new MRA58K build.
Yes I know toolkits are not the recommended option but it made rooting 6.0 a breeze.
Sent from my SHIELD Tablet using Tapatalk

[MOD] Enable Native Tethering

Update: the patch for the latest OTA can be found here: http://forum.xda-developers.com/droid-turbo/general/enable-su4tl-49-stock-tethering-to-t3380911
Even though it's been reported that the old version works with the SU4TL-49 OTA, I recommend flashing the updated patch with the OTA, since the patch flashes a modified build.prop file, and the new patch will include any changes made to the build.prop by the OTA update.
This is exactly what the thread title says. The zip replaces the stock build.prop file with one modified to enable native tethering. This is not guaranteed to work with any other build than SU4TL-44. I have personally tested this on my own phone. If you use this on any other build, you do so at your own peril.
Flash in TWRP.
And a quick apology, I had thought I was in the General section when I started the new thread. If any moderators want to move this to the General section, by all means, please do.

pastorbennett said:
This is exactly what the thread title says. The zip replaces the stock build.prop file with one modified to enable native tethering. This is not guaranteed to work with any other build than SU4TL-44. I have personally tested this on my own phone. If you use this on any other build, you do so at your own peril.
Flash in TWRP.
And a quick apology, I had thought I was in the General section when I started the new thread. If any moderators want to move this to the General section, by all means, please do.
Click to expand...
Click to collapse
Flashed this to my Turbo yesterday; works like a charm. Thanks!

Guys, I'm sure this is dumbest question ever asked on XDA, but would somebody give me a hand on how to flash this via TWRP? I put the extracted files on my phone but couldn't find them to install from within TWRP, probably because they're not an .apk - do I need to somehow make these part of a ROM and flash the whole thing?
Just did sunshine/update/TWRP/root and everything is working great, if that makes any difference.
Thanks a lot!

thetastycat said:
Guys, I'm sure this is dumbest question ever asked on XDA, but would somebody give me a hand on how to flash this via TWRP? I put the extracted files on my phone but couldn't find them to install from within TWRP, probably because they're not an .apk - do I need to somehow make these part of a ROM and flash the whole thing?
Just did sunshine/update/TWRP/root and everything is working great, if that makes any difference.
Thanks a lot!
Click to expand...
Click to collapse
With TWRP you do not flash the extracted files. You flash the zip. It has to be a "flashable" zip, but this one is.
Over in the bootloader unlock warning image thread, some people were trying to flash a zipped file that was not meant to be flashed. The image was meant to be unzipped/extracted and then flashed with ADB.
But in this case this is a TWRP flashable zip.

Worked perfectly! Thank you both so much - this is a lifesaver!!

pastorbennett said:
This is exactly what the thread title says. The zip replaces the stock build.prop file with one modified to enable native tethering. This is not guaranteed to work with any other build than SU4TL-44. I have personally tested this on my own phone. If you use this on any other build, you do so at your own peril.
Flash in TWRP.
And a quick apology, I had thought I was in the General section when I started the new thread. If any moderators want to move this to the General section, by all means, please do.
Click to expand...
Click to collapse
Worked as advertised. I still have unlimited data and racked up an impressive 180GB of data. What a life saver!

Anyone tried this with the latest OTA yet?

Jazzy Josh said:
Anyone tried this with the latest OTA yet?
Click to expand...
Click to collapse
It works just fine.

Jazzy Josh said:
Anyone tried this with the latest OTA yet?
Click to expand...
Click to collapse
KOAO said:
It works just fine.
Click to expand...
Click to collapse
It works with the latest OTA? That's good to know. I hadn't tried, since the patch basically overwrites the stock build.prop, and there's always going to be a few changes in the file whenever a new update is installed.
I did put together a patch for the latest OTA, which I would recommend flashing if you used the SU4TL-44 version, as the build.prop file reports the software version to the OS.
The thread for that patch is here:
http://forum.xda-developers.com/droid-turbo/general/enable-su4tl-49-stock-tethering-to-t3380911
Sent from my XT1254 using XDA-Developers mobile app