I have a stock, non rooted, ad free R1 HD. The Wireless update downloaded the System Update, but I'm afraid to apply it if it might screw something up. I don't give a whoot abut VoLTE, and am on AT&T so having band 12 available is pointless. Can I just ignore it and not risk anything going wrong?
No it's not, have a look here for safe options.
http://forum.xda-developers.com/r1-hd/development/prime-stock-rom-6-5-flashed-via-twrp-t3455532/
Related
Has anyone else received this update?
Not here.
Los Angeles, CA
lol figures once i get root an update starts rolling out, it probably enables wifi n like they released for the EVO today.
1.22.605.2 is the software version i have (rooted)
It adds 3G Mobile hotspot and fixes the signal issue, im in a pickle now though lol. cant remove superuser
Not exactly a pickle - just don't do the upgrade, wait for someone else to take the OTA download and make it root-safe.
where did you confirm this info as to what the update offers?
I guess i am confused, what would happen if we did the update with our rooted phones?
Nothing. Because with rooted phones you won't see the OTA Update...but if you were to manually upgrade without it being root proofed....you'd loose root.
Wait - weren't we already at 1.22.605.2? That's what rev I'm running, and I haven't taken an OTA since the first few days after launch.
giantcrazy said:
Wait - weren't we already at 1.22.605.2? That's what rev I'm running, and I haven't taken an OTA since the first few days after launch.
Click to expand...
Click to collapse
Incredible OTA Update 1.65.605.2
I'm confused to, so if you are rooted, you won't see this update? or you will see it and if you do it, you lose root? I have the stock rom, which is what I thought disabled your OTA's is this an incorrect thinking?
giantcrazy said:
Wait - weren't we already at 1.22.605.2? That's what rev I'm running, and I haven't taken an OTA since the first few days after launch.
Click to expand...
Click to collapse
The name of this post is Incredible OTA Update 1.65.605.2 so even though we are at 1.22.605.2 that is not 1.65.605.2
Thats the thing, i was rooted and did get the OTA update notifications, hit accept for the update by mistake. And the only reason why i confirmed that info is because i have it on my inc.
P.S sorry lol made a type in the title of the post, its 1.35.605.2
So if you updated as root, did you lose your Root? It is not guaranteed that you would loose it, just likely is all. I feel like they released it to break our Root, and nothing more... but maybe they fixed a few issues too... we have the same screen grounding issue the EVO had, and the recent update fixed theirs... but who knows...
EDIT: Posted an article to an outdated update. Oops...
so i assume you lost root?
Yes i did.
I haven't seen it yet. <-- OHIO
have you tried redoing root? did you loose recovery?
I havent tried redoing the root process again, but how is that going to work? isn't the root process based off of the original software? the baseband is different as well.
Haven't seen it yet either <-- Rhode Island
Didn't find any information on it either. Was their a "more info" link included with yours? as with other OTA updates. Changelog, etc.?
Better question would be, do you have a screen shot of your About Phone page (baseband, software version, etc.)
somebody who gets the update needs to upload the file so a dev can do something with it.
I have just received a replacement D3 and it had shipped with the 5.7.906 update. I was wondering if there was a way to root it and if ROMs that use the old BP tools and things like that, that prevent from downgrading. If so, can I install a ROM that uses the 5.7.906 system apps will install correctly and work. Currently I have not found or seen anyone with the fast boot /.XML/RSD lite files to restore it if anything goes wrong. I'm just worried that I won't be able to get back to stock if something goes wrong in the install process. Any help will be appreciated. Thank you in advance.
Intriguing!
Did youo receive your phone as a replacement from Verizon? If it's brand new and it runs on 5.7.906, I surmise that the next official OTA would certainly be 5.7.906. This will absolutely make some folks relaxed since they're worrying that 5.7.906 might not be the right update path. In this case, if anything goes wrong, just head over the thread about OTA Leak and flash it onto your device.
About ROM, unless the developer specifies in their thread, your phone should be ok with any.
Good luck!
You are most likely the luckest droid 3 user youhave the lastest ota update already
sent from my FULLY CUSTOMIZED DROID3 using swype and the gifts god gave me
I may get an LG G4 and have a couple of quick questions.
Can I just run the phone as stock/rooted? What's the latest official Android version? What's the current easiest root method? If I get a new phone that I want to run stock/rooted, do I just accept all updates and then root when I get to the latest version? Any systemless root option?
With root, can I still take OTAs and then (hopefully) re-root after or once the update installs or will the rooted phone not take OTAs and then I'm forever on the path of having to manually flash updates?
Yes you can run the phone stock rooted and still take updates. But if you do take any updates you take a chance at either losing root or bricking your phone (Someone with more experience would have to answer that but thats my guess) The current version is 5.1 (6.0 for international and sprint). So far this is the easiest root method http://forum.xda-developers.com/showthread.php?t=3191038 (only for h811 with 10n base) after you do this root method be sure to download twrp and install it with flashify. If you're running 10h base use one click twrp. So far there is no systemless root for 5.1 (only for 6.0) that's about all i got for you.
I saw where the thread to return to "stock" was removed due to a brick issue.
I have the T-Mo G4, running H81110n, and I'd like to un-root it so that I can trade it in back to T-Mo for something new. What's the easiest way to do that, without triggering alarms? The G4 is still new enough that trading it in is worth it, rather than just tossing it in a drawer with all my other old phones.
I used the "low effort" root from jcase/autoprime/tylerfixer back in July. Other than flashing the upgrade to H1110n, I haven't done anything crazy with it.
Thanks!
-m0j0
m0j0 said:
I saw where the thread to return to "stock" was removed due to a brick issue.
I have the T-Mo G4, running H81110n, and I'd like to un-root it so that I can trade it in back to T-Mo for something new. What's the easiest way to do that, without triggering alarms? The G4 is still new enough that trading it in is worth it, rather than just tossing it in a drawer with all my other old phones.
I used the "low effort" root from jcase/autoprime/tylerfixer back in July. Other than flashing the upgrade to H1110n, I haven't done anything crazy with it.
Thanks!
-m0j0
Click to expand...
Click to collapse
http://forum.xda-developers.com/tmobile-g4/development/rom-g4-h811-10n-stock-restore-t3191756
so i am still on oe2 build and my s6 edge is rooted. can anyone give me opinions if i should update from 5.0.2 and lose root. is it worth it? is there anything i will be missing out on if i do update?
p.s. i used the root to enable hidden menu so i can manually select wcdma/gsm frequency because i am using tmo and get many signal issues on lte between phone calls...
clip3009 said:
so i am still on oe2 build and my s6 edge is rooted. can anyone give me opinions if i should update from 5.0.2 and lose root. is it worth it? is there anything i will be missing out on if i do update?
p.s. i used the root to enable hidden menu so i can manually select wcdma/gsm frequency because i am using tmo and get many signal issues on lte between phone calls...
Click to expand...
Click to collapse
I will always be pro-root over pro-update. I would keep root, were I in your position. However, here's my two cents:
So to clarify, you are on 'G925VVRU1AOE2' correct? Then we discard the model number (G925V), the Verizon and region identifiers (VRU), and we're left with '1AOE2'. Note the '1A'.
The 6.0.1 firmware is G925VVRU4CPC2 (or 4CPD2 for the latest). Notice the '4C' in contrast to your '1A'. If you flash either 6.0.2 firmware, your bootloader rollback index will update to '4'. This means you'll never be able to flash a stock firmware less than '4'. If you wanna go backwards from there, the furthest you could go back would be 5.1.1 Lollipop '4BOG7'. You would be unable to go any further backwards, as the firmware before that is '3BOG5'. Make sense? Keep this lil tidbit in mind when making your decision.
An alternative may be to just update to '2AOF1'. If I recall correctly, OF1 is rootable. However don't quote me on that.
I think that depends on what rooted features you use. I have the latest build 4CPF4 and it's very good in terms of stability. Samsung also updated the TouchWiz so you do get some added features there as well. I personally don't use "edge" features so I can't review them for you.
I prefer rooted devices too for things like exposed framework and the ability to modify the host file, etc. But this phones feels snappy enough that I don't have to tweak it.
Sent from my SM-G925V using XDA-Developers mobile app
It took me a long time but I have finally gotten things settled down and working adequately on my new 405QA with Android 9, root w/Magisk, etc. I read here <https://www.theandroidsoul.com/lg-v40-update/> and elsewhere there may be an Android 10 coming. While for some that may be great news, for me it isn't. I need to rest and recover from the migration from my old Samsung Note 3 with 4.4.2!
So the question is: how do I 100% avoid any new Android OS updates from being (a) downloaded and (b) installed? In developer options, I have turned OFF "automatic system updates". But I fear this is not enough.
On my old Samsung, rooted with SuperSu, this alone seemed to prevent OS updates. But somehow I wonder if using Magisk and all will make preventing updates a bit different. What is the best way to handle this?
Thanks!
So, what you have done already is enough. Also, for a number of carriers you only get OTA if you are with the original firmware so if you cross-flashed your phone to unlocked US kdz, it is unlikely you would get any OTA updates even if you didn't disable in developer options. Any further options, you'd need to be rooted (which you are), disable/freeze both 'Software Update' apps and 'Fota Update' app. Titanium Backup is the best to freeze these.
Android# said:
So, what you have done already is enough. Also, for a number of carriers you only get OTA if you are with the original firmware so if you cross-flashed your phone to unlocked US kdz, it is unlikely you would get any OTA updates even if you didn't disable in developer options. Any further options, you'd need to be rooted (which you are), disable/freeze both 'Software Update' apps and 'Fota Update' app. Titanium Backup is the best to freeze these.
Click to expand...
Click to collapse
Thanks. Have not cross-flashed but I have used Magisk debloat to deal with fota and software updater. I feel better/safer now. Cheers