Database Develop

Question about ROOT access?

I figured, I would get the best response here... If you ROOT an Android phone, will downloading OTA updates through your phone brick it? I read an article about the new OTA for the EVO and it will brick rooted devices.

Misinformation. It would brick it if you applied it twice in sequence, not if you were rooted. You need the stock recovery to apply updates anyway, if you do get one it will not harm the phone because it can't be applied.

In the thread when the final OTA was coming out, lots of people that were rooted, said they installed it, it worked fine, but they lost root. So then they have to obtain root again.
So, I'd assume it would work fine if everything else was stock... you just might loose root.

So your saying, that if I were to install an OTA update through a rooted Android device running stock firmware, it would go through successfully without bricking it. But, if I ran the update a second time it would brick it. Correct?

If you're on a rooted stock rom, assuming you haven't flashed a custom recovery, the phone's recovery utility will not allow you to flash an OTA update because of a signature mismatch. I'm not sure what happened with the evo, but I don't believe it can happen with the nexus.

Okay, thanks? But I would still like some more input on this situation.

Pay attention
PurpleLlamaLover said:
Okay, thanks? But I would still like some more input on this situation.
Click to expand...
Click to collapse
If your not rooted you can still flash OTA update leaks, there are plenty out there. If you want custom roms then you have to root. The stock recovery only flashes stock updates, not rooted updates. If your not getting it by reading the forums, then I suggest you stay on stock, and wait for OTA update.

efishta said:
If you're on a rooted stock rom, assuming you haven't flashed a custom recovery, the phone's recovery utility will not allow you to flash an OTA update because of a signature mismatch. I'm not sure what happened with the evo, but I don't believe it can happen with the nexus.
Click to expand...
Click to collapse
No, this only happens with this specific update with the EVO.

Alright, great! Thanks guys. So since I believe the nexus one already got the offical OTA, did any of you lose ROOT access?

You WILL loose root when you update from an OTA update.

I had a rooted FRF50 and went to the FRF83 update and lost root/custom recovery, everything else was fine though.

I ask that you all forgiveth the newb nature of my question in advance, but if my phone has been rooted, and is currently running FRF50, is there anything I can do to the phone to have it automatically update using OTA? I ask because I received the notice for the OTA update the other day, but being rooted, got a signature mismatch error. (The only reason my phone is rooted is bc I bought it used that way-I wish I could've had it bone stock instead!) I know I can somehow do a manual update, but I'm trying to figure out for further future OTA updates if there's a way that I can have my phone simply automatically apply them.

Well, first off, thanks for hijacking.... AND, I have been doing a bunch of research. You should find the official build of froyo (FRF85B correct?) and manually update it. Just use it unrooted and it'll be easier when an OTA update comes along

[Q] Can I update? Confused by so many unclear posts.

Background information:
Bought the AT&T version when it came out right away
Got root the first time it was released
Updated root when next update came out ( Didn't know if I need to )
OTA has been Frozen since I got the phone
Is it safe for me? Should I go back to the first version and then update?
Trust me I've read the posts and since I know there have been some issues on the Verizon side I wasn't sure if that was something that was effecting AT&T too. If some one could please give me an explain of that to it would be extremely helpful as I like to know my **** so I can help others.
Thanks

Icon000 said:
Background information:
Bought the AT&T version when it came out right away
Got root the first time it was released
Updated root when next update came out ( Didn't know if I need to )
OTA has been Frozen since I got the phone
Is it safe for me? Should I go back to the first version and then update?
Trust me I've read the posts and since I know there have been some issues on the Verizon side I wasn't sure if that was something that was effecting AT&T too. If some one could please give me an explain of that to it would be extremely helpful as I like to know my **** so I can help others.
Thanks
Click to expand...
Click to collapse
Flash back to stock via RSDLite. Let it boot up. Get your gmail setup.
When the prompt comes up, DL the .54 update. Install.
Root with jcase's new root method.
Or you could just install safestrap. Install a ROM with the camera update and not worry about it until kitkat comes around.
Sent from non rooted motoX :'(

I'm not really interested in updating to another Rom unless it has the touchless controls or something really interesting. Touchless Controls is one of the main reasons I got this phone next to battery life.
Is Safestrap finally settled down? I feel like last time I check there were still messages about bugs and other issues?
matt99017d said:
Flash back to stock via RSDLite. Let it boot up. Get your gmail setup.
When the prompt comes up, DL the .54 update. Install.
Root with jcase's new root method.
Or you could just install safestrap. Install a ROM with the camera update and not worry about it until kitkat comes around.
Sent from non rooted motoX :'(
Click to expand...
Click to collapse

Icon000 said:
I'm not really interested in updating to another Rom unless it has the touchless controls or something really interesting. Touchless Controls is one of the main reasons I got this phone next to battery life.
Is Safestrap finally settled down? I feel like last time I check there were still messages about bugs and other issues?
Click to expand...
Click to collapse
the only rom out for SS that i am aware of is just a ported tmobile rom for vzw phones that has the update built in. Basically it is just the OTA stock rom running on SS. This is what I am using currently. Not sure if it flashable for ATT phones, but I'm sure there is some workaround there. Or maybe the OP on that thread can make a ATT one if you asked him. SS is stable as of now. Haven't had any new updates to it because no one is having any problems currently (at least with moto x devices).
For your question pertaining to options for taking the OTA. There are 4 methods now.
1. SS method described above
2. use the thread called something like "keep root through the OTA." It basically takes the ota without updating the BL so you can still downgrade to your stock original FW that you are on now. It's the same thing as the SS method because SS also does not udpate the BL, but you won't be using SS for this method obviously.
3. you can flash recovery.img (and system.img if you need to) or just RSD, then install pwnmymoto without running it, then take the ota and pwnmymoto will root the phone automatically after the ota is taken. you won't be able to downgrade your FW anymore with this method.
4. you can just take the ota (also must flash or use rsd to take it obviously) and then use jcase's rockmymoto root exploit. This uses adb commands and telnet stuff. Not too difficult but if you are unfamiliar with all of that then it will take at least some reading. There is also a thread out there for windows users that simplifies it pretty well.
For future Kit kat root. it is still up in the air what will happen with that. I chose to use SS because it was easy. quick. and allows me to make nandroids. I also like knowing that I can still flash to original stock FW in case that might be necessarry for getting root on kit kat. This seems less likely now that jcase created a root method for the OTA that is out, but I'm still just playing it safe personally, even if it might be pointless now.

[Q] Information Overload!

OK, I've read so much that things are just getting jumbled in my brain now. There's so much information in these threads that I don't know where to start. The world of Android apparently moves too fast for me to keep up. I've got a Verizon LG G2 that is stuck on 4.4.2, software version 24A. Right after I took the OTA KK upgrade I rooted with IORoot25. I don't think I've done anything other than root, however I have somehow can create the mobile hot spot without permissions. Not sure if there was an .apk that was put on when I rooted or how I did it because it was over a year ago.
Ever since I rooted, my phone tries to push OTA updates but they are always unsuccessful. Every morning I have to hit "Install Later" becasue it tried over night and failed. Besides this being a bit annoying, I haven't been concerned becasue the only OTAs since I got 4.4.2 was supposedly some small patch that didn't really do much (from what I read). But, the other day it notified me that it wanted to push Lollipop and needless to say, I want it.
My problem: I don't know what the hell to do! Besides rooting, I'm pretty sure the only thing I've done is download Flashify and backup my stock recovery. Flashify doesn't show that I have a custom recovery, nor do I ever remember installing one. Just whatever came with the IORoot25. Oh, and it looks like I Quarantined LGSetupWizard using App Quarentine. Pretty sure that's it. So, where do I go from here?? I'm wanting to move to Lollipop, then possibly de-bloat it, and would like a custom recovery so that I can create nandroid backups and possibly start trying out other custom ROMs.
I had an OG Droid for years and would flash ROMs frequently until I upgraded to a RAZR MAXX. Once I got the MAXX, and now the LG, all I've really done is root and hack the wifi, so I'm REALLY out of the loop now! Everything seems so complicated becasue there's just too much info out there. Could somebody please guide me in the right direction to make this as smooth as possible??
Thanks for reading and helping a NooB out. Ugh...can't believe I have to start calling myself that again!!

You could 'freeze' the update so it doesn't pop up every morning. IF you want to update- you can unroot it and then take the update and re-root it and fix the hotspot thing. I'm in the same boat, I'm about to do the same myself.

caecusscius said:
You could 'freeze' the update so it doesn't pop up every morning. IF you want to update- you can unroot it and then take the update and re-root it and fix the hotspot thing. I'm in the same boat, I'm about to do the same myself.
Click to expand...
Click to collapse
Thanks for the response. Hoe do I "freeze" the update? If I do decide to take the update and re-root, and especially if I start loading custom ROMs, I know I'm going to want to do this in the future. I've been getting theses OTA update notifications everyday for months now!!
Also, what's the easiest way to unroot?

AS long as you are running stock I believe you can accept the OTA without unrooting: I haven't done it yet as I haven't had a few free hours, but I'm going to try it tonight.
there are plenty of apps that allow you to freeze apps- titanium Backup Pro is one that comes to mind.

Rooted kitkat to new 5.1.1 release help

Have n901t. Rooted it after being talked into 5.0.1 by Tmobile rep trying to improve it. No good. So went back down to KitKat and rooted that. Obviously I cannot receive ota update for 5.1.1 now. Do I just get the stock file and flash with the phone as it currently is? Or should I flash KitKat back to it's un rooted state before updating phone? Am still a novice in the taking control of your smart phone world and would rather not brick something if it can be easily avoided. Thank you.

KDawgEnigma said:
Have n901t. Rooted it after being talked into 5.0.1 by Tmobile rep trying to improve it. No good. So went back down to KitKat and rooted that. Obviously I cannot receive ota update for 5.1.1 now. Do I just get the stock file and flash with the phone as it currently is? Or should I flash KitKat back to it's un rooted state before updating phone? Am still a novice in the taking control of your smart phone world and would rather not brick something if it can be easily avoided. Thank you.
Click to expand...
Click to collapse
You could get the official software and use odin to install it but there are a couple of things you need to be aware off. First once you upgrade to 5.1.1 you cannot downgrade back to kit kat and you will be stuck on that version, secondly in order to achieve root you might need to install a custom kernel before rooting. For that last part I would suggest you hit the forums since there a couple of posts about rooting this new version.

don't know if I am ready to start messing with kernals yet. Am patient. New root will show itself before we know it. Did the update through Odin. So far smooth sailing. Tested Simpsons tapped out since with 5.0.1 it lagged so bad it was unplayable. Still not as smooth as it was on KitKat but can still play it at least. Haven't tinkered with anything else yet.

Personally I'm waiting it out. I don't like not being able to go back, and I've had 0 luck with 5+.. So I'll wait until someone "fixes" it, if ever.

Root 5.1.1 or 6.0.1?

I have a TMobile Note 4 SM-N910T. It's currently on 5.1.1 stock and I just got the OTA Marshmallow update notification. I'd like to try Marshmallow out, but if I allow the OTA update, will I be able to root it later? Or is 6.0.1 unrootable (for now)? If I root it now (before updating to MM) will I still get the OTA update? And will it still be rooted after the update? So many questions!

ota then root

I OTA'ed, now the phone randomly reboots several times a day, and some apps don't work correctly. Great.

factory reset.

*sigh* I was afraid you were going to say that. Now the problem is backing it up. I have a Titanium Backup Pro license, but I only use it on my old rooted GS2. The Note 4 is not rooted so TB won't run on it. All the rooting tutorials say "back up your phone before you root" but you need root to run TB. Chicken or egg? I guess I could try Samsung Kies, don't know if it will back up everything. My photos are backed up to Google Photos, I guess everything else is replaceable, but I would really rather not have to reinstall all my apps one by one after a factory reset.
That brings up another question: when you to go Settings/Backup and Reset, I have "Backup my data" set to On and linked to my Google account, but nowhere can I find documentation of exactly WHAT gets backed up or to WHERE (it says to "Google servers" but what the heck does that mean? I can't find it on my Google Drive or anywhere else on my Google account dashboard.)
I do greatly appreciate your help, by the way.

You could try reinstalling through kies or smart switch. Make sure to clear caches before and after. And see if that works. If it doesnt help, you could flash recovery, root, try to backup as much as you can between reboots and then factory reset. Your apps should automatically download from play store. But without the titbackup files you'll lose settings and data in a lot of apps that Google doesn't backup.
I unlocked your mum's bootloader.

kydar said:
I have a TMobile Note 4 SM-N910T. It's currently on 5.1.1 stock and I just got the OTA Marshmallow update notification. I'd like to try Marshmallow out, but if I allow the OTA update, will I be able to root it later? Or is 6.0.1 unrootable (for now)? If I root it now (before updating to MM) will I still get the OTA update? And will it still be rooted after the update? So many questions!
Click to expand...
Click to collapse
Were you able to downgrade back to 5.1.1? My phone also download the MM ota but I haven't installed it. I rooted 5.1.1 first and am trying to locate where exactly the MM ota downloaded to.
Been hearing too much about problems with MM.

Shad0wsabr3 said:
Were you able to downgrade back to 5.1.1? My phone also download the MM ota but I haven't installed it. I rooted 5.1.1 first and am trying to locate where exactly the MM ota downloaded to.
Been hearing too much about problems with MM.
Click to expand...
Click to collapse
There aren't that many problems with MM. Just superficial stuff like not having mobile data toggle. The problems you are hearing about a factory reset will fix. Like lag, jankyness, apps loading, phone freezing temporarily. You won't be able to do OTA. It will fail because of root. You need to titanium backup or whatever method you prefer of backing up data and flash through kies, odin or smart switch. Probably easier to go that route unless you only did minor things with root like just block ads, then you can probably get away with flashing stock recovery and then OTA. You still might have to factory reset like I had to even though I flashed whole rom through smart switch. If you have xposed or modified something like swapping recent apps and back key like me, then you'll need to flash marshmallow whole and start over after backing up.
Afaik, you can't downgrade to 5.1.1 unless somebody figured out a workaround or you only flashed everything except bootloader.
I unlocked your mum's bootloader.

@Shad0wsabr3, my phone gave me the choice to delay the upgrade for a while, but eventually just did it without my consent. I suppose you could download stock 5.1.1 from sammobile if you really wanted to downgrade. I just wish I could figure out how to back up my (unrooted) phone so I could then do a factory reset and see if it helps the problems I'm having.

kydar said:
@Shad0wsabr3, my phone gave me the choice to delay the upgrade for a while, but eventually just did it without my consent. I suppose you could download stock 5.1.1 from sammobile if you really wanted to downgrade. I just wish I could figure out how to back up my (unrooted) phone so I could then do a factory reset and see if it helps the problems I'm having.
Click to expand...
Click to collapse
Iv never backed up an unrooted device so I wouldn't know. Glad you nrought that up as Iv been meaning to look into that.
Would you happen to know where the downloaded ota file location is? My phone downloaded it and I keep postponing it.

Sorry, idk exactly where in the file system it is. All I can caution you again is, I kept postponing it and postponing it, and then one day the phone just popped up a message saying it was going to reboot and update, whether I liked it or not. Well, it didn't actually SAY whether I liked it or not but it did decide that I had postponed the update long enough and it was going to apply the update, giving me no option to postpone it any longer. That sort of pissed me off.
Please let me know if you come up with a backup solution. I've tried SimpleADB or whatever it is called these days, and another app that claimed to be able to back up an unrooted phone. Neither of them worked as advertised.

Where are the root instructions for completely stock 910T with MM update?

vernj123 said:
Where are the root instructions for completely stock 910T with MM update?
Click to expand...
Click to collapse
http://forum.xda-developers.com/not...overy-n910t-t3-marshmallow-pe3-guide-t3406870

kydar said:
Sorry, idk exactly where in the file system it is. All I can caution you again is, I kept postponing it and postponing it, and then one day the phone just popped up a message saying it was going to reboot and update, whether I liked it or not. Well, it didn't actually SAY whether I liked it or not but it did decide that I had postponed the update long enough and it was going to apply the update, giving me no option to postpone it any longer. That sort of pissed me off.
Please let me know if you come up with a backup solution. I've tried SimpleADB or whatever it is called these days, and another app that claimed to be able to back up an unrooted phone. Neither of them worked as advertised.
Click to expand...
Click to collapse
I'm still researching what your dealing with. As for me I found the ota file. For those looking for it this is how and where I found it....
With RomToolbox I went to root browser. Then to data folder and a folder named fota. Within the fota folder is the ota update named update.zip. I erased that and then went into Titanium Backup and chose to freeze both software update files. So far no constant reminders that I have an update ready to be installed.
Hope this may help.