I keep hearing about an OTA update that fixes the battery life percentage issues. To get this do I have to revert back to stock, install the OTA update, then unlock and re-root or is this something that can be incorporated into future kernels?
I thought it was an update to the system. What does it include? I thought it was just some files in stuff like Bin, etc, or Lib. :/
Just got this update last week and it finally fixed the battery issue for me.
Info how to do it: How to upgrade One V with an OTA update
bradthomas127 said:
Just got this update last week and it finally fixed the battery issue for me.
Info how to do it: How to upgrade One V with an OTA update
Click to expand...
Click to collapse
That's fine and dandy but are you running a custom rom? If i revert to stick and run the ota, I get constant reboot issues after flashing a Rom after that. If I undo the ota (by running the ruu) then I can flash a Rom with no problems.
MasterTec said:
That's fine and dandy but are you running a custom rom? If i revert to stick and run the ota, I get constant reboot issues after flashing a Rom after that. If I undo the ota (by running the ruu) then I can flash a Rom with no problems.
Click to expand...
Click to collapse
I wasn't at the time i answered because i had just did the update but when i tried to go back to a custom Rom i had the same problem and had to run the RUU. Sorry about that.
Related
I reverted back to stock yesterday to receive Jelly Bean update but it says my phone is up to date.
I flashed recovery, locked the bootloader and used RUU 1.29
I'm TMobile UK CID005
When the phone rebooted update 4.0.4 came though, I downloaded and updated the phone to 2.17
No more updates are coming through however. I'm not sure if I flashed stock recovery or not (If I didn't would have update above come through?). Anyway can I reflash the stock recovery just to be sure? And how would I go about this? Also I have a custom Kernal if that makes any difference? Cheers
if you run the ruu then you're on stock already. maybe there's still no JB update for your CID.
robchongke said:
if you run the ruu then you're on stock already. maybe there's still no JB update for your CID.
Click to expand...
Click to collapse
I just unlocked my phone and the 1.25mb update came throught followed by JB. Strange
cassas00 said:
I just unlocked my phone and the 1.25mb update came throught followed by JB. Strange
Click to expand...
Click to collapse
maybe because you're still on stock rom.
Sometimes the updates won't show automatically, if you return to stock in ways like this. its recommended to check manually in the settings menu for updates .... consider this as a small "bug"
Hey guys,
I received this offiial OTA push for 4.3 update on the 27th July (GMT +8). but when i try to install it on the recovery screen, it says update failed and restarts the phone. But ever since, I couldn't get the OTA push anymore. Not even from System Updates in the settings menu.
Anyone having this problem as well? or anyone know any walkaround for this?
Thanks!
P/S I've flashed my phone with the official rom that gets OTA from google instead of Samsung. And I'm currently on 4.2.2 with fancy kernel R35
niaoRen said:
Hey guys,
I received this offiial OTA push for 4.3 update on the 27th July (GMT +8). but when i try to install it on the recovery screen, it says update failed and restarts the phone. But ever since, I couldn't get the OTA push anymore. Not even from System Updates in the settings menu.
Anyone having this problem as well? or anyone know any walkaround for this?
Thanks!
P/S I've flashed my phone with the official rom that gets OTA from google instead of Samsung. And I'm currently on 4.2.2 with fancy kernel R35
Click to expand...
Click to collapse
If i'm not wrong, if you've a custom recovery OTA update fails, happened to me with my Nexus S back a year or two, i just grabbed the official image from google and flashed it VIA ADB.
PS: i can be wrong you know.
lastforone said:
If i'm not wrong, if you've a custom recovery OTA update fails, happened to me with my Nexus S back a year or two, i just grabbed the official image from google and flashed it VIA ADB.
PS: i can be wrong you know.
Click to expand...
Click to collapse
True, I've experienced this before, I would recommend go with Official Factory image if not sure your device is running completely stock before apply OTA...
First of all your using a custom recovery an second your using a custom kernel, so its always going to fail a ota install, my suggestion just flash a ota flashable twrp or cwm zip.
lastforone said:
If i'm not wrong, if you've a custom recovery OTA update fails, happened to me with my Nexus S back a year or two, i just grabbed the official image from google and flashed it VIA ADB.
PS: i can be wrong you know.
Click to expand...
Click to collapse
fux0r99 said:
First of all your using a custom recovery an second your using a custom kernel, so its always going to fail a ota install, my suggestion just flash a ota flashable twrp or cwm zip.
Click to expand...
Click to collapse
wrong. a custom recovery does not hinder the OTA, its the custom kernel that is causing the update to fail (and any other modifications you do to /system outside of root)
and if even if he tried to flash a OTA with cwm/twrp, it would still fail because of the kernel. the OTA does an assert check on system files before installing.
Zepius said:
wrong. a custom recovery does not hinder the OTA, its the custom kernel that is causing the update to fail (and any other modifications you do to /system outside of root)
and if even if he tried to flash a OTA with cwm/twrp, it would still fail because of the kernel. the OTA does an assert check on system files before installing.
Click to expand...
Click to collapse
So in order for me to update to 4.3, I'd have to reflash the stock kernel then update with the OTA?
niaoRen said:
So in order for me to update to 4.3, I'd have to reflash the stock kernel then update with the OTA?
Click to expand...
Click to collapse
If that is the only thing you have changed from stock, yes. When it errors out in recovery, it should tell you the problem(s).
cupfulloflol said:
If that is the only thing you have changed from stock, yes. When it errors out in recovery, it should tell you the problem(s).
Click to expand...
Click to collapse
alright. Will try to revert to stock kernel and try the official OTA. Will revert back here after i've attempted it. Thanks a bunch you all
I just found a easier way to do things.
Just flash this 4.3 stock ROM over my current 4.2 rom. Works like a charm and hassle free.
Hi,
I have a rooted Sprint GS3, running the stock ROM with just one or two root based apps. Do I need to unroot to accept the OTA update? If so, how do I go about doing that?
TheSapient said:
Hi,
I have a rooted Sprint GS3, running the stock ROM with just one or two root based apps. Do I need to unroot to accept the OTA update? If so, how do I go about doing that?
Click to expand...
Click to collapse
if you would like to run a 4.3 stock ROM, there are a couple in the development section that you can choose from without having to run the 4.3 boot loader that contains KNOX. That way you don't have to go through the unroot process to accept the OTA.
jdelano said:
if you would like to run a 4.3 stock ROM, there are a couple in the development section that you can choose from without having to run the 4.3 boot loader that contains KNOX. That way you don't have to go through the unroot process to accept the OTA.
Click to expand...
Click to collapse
Thanks. I think the preference is to accept the OTA. If we need to unroot, we'll do that if we can figure out how. Sorry for being a little vague. I'm trying to help someone else out.
ok, you can go here Restore to unrooted MD4 follow that and you're good to go
I was stock rooted with clockwork recovery.
Took the OTA without unrooting with no problems at all, just had to re-root when it was done.
dotNETProgrammer said:
I was stock rooted with clockwork recovery.
Took the OTA without unrooting with no problems at all, just had to re-root when it was done.
Click to expand...
Click to collapse
Really? I thought it was always a bad idea with a custom recovery. Maybe we will try it rooted as well. Thanks.
Every other time I've tried it would download, but just wouldn't flash the OTA.
This time, it did. Surprised me.
Re
I got the update notification today when i woke up and when i clicked the restart and install it went to recovery mode, i panicked and clicked reboot (honestly still dont know what to do),
and restarted the phone without updating
I'm running stock 4.1.2 with just 2 root apps (superuser) and tatanium backup, how can i update ?
thanks
mjkubba said:
I got the update notification today when i woke up and when i clicked the restart and install it went to recovery mode, i panicked and clicked reboot (honestly still dont know what to do),
and restarted the phone without updating
I'm running stock 4.1.2 with just 2 root apps (superuser) and tatanium backup, how can i update ?
thanks
Click to expand...
Click to collapse
Relax . You do not have to update. You do not have to lose Root. Check out THIS thread. It will explain a few things to you in detail about Updates, and how to stop the update nag. If you want to update to the latest TW 4.3 Stock Rooted, check out the thread HERE. Just make sure you read, and read again before doing anything. Also make sure to download the correct Rom. There are several versions on the thread.
prboy1969 said:
Relax . You do not have to update. You do not have to lose Root. Check out THIS thread. It will explain a few things to you in detail about Updates, and how to stop the update nag. If you want to update to the latest TW 4.3 Stock Rooted, check out the thread HERE. Just make sure you read, and read again before doing anything. Also make sure to download the correct Rom. There are several versions on the thread.
Click to expand...
Click to collapse
Thanks for the answer.
I actually want to update to stock 4.3, and I was trying to achieve that by getting the OTA update.
And i was wondering if i can still do that?
If I simply can't then I'll just go to CM instead of getting other rooms since I used to have them with my old HTC.
Thanks again
If you want completely Stock Rooted 4.3, it's the second link I posted for you. It's the Stock, Rooted, Factory Rom, with Knox removed. All done by CNexus . Just be sure to read before doing anything. As there are several versions posted. I would highly suggest going this route instead of taking the OTA update. Once you take the OTA you will have Knox, and a different bootloader.
TEAM MiK MikROMs Since 3/13/11
Thanks a lot man, I'm having a problem installing the ROM, I'm getting assert error (status 7) error when trying to install the odexed rom,
I have just updated my CWM to 6.0.4.5
Sorry I cant reply to the thread directly, need 10 posts to be able to do so.
MJ
edit: now it's stuck on boot loop
edit: I downloaded the original recovery rom and installed it from ordin, then updated phone through kies. it's all good now.
Do we have to revert to stock Rom to upgrade to lollipop? Was wondering if it's the same with the htc eye update wherein you have to go back to stock and update manually before flashing the custom rom. I am having an extremely difficult time going back to stock for some weird reason.
For every major update on this device so far (AFAIK) HTC has updated the firmware. So yes, my guess will be that you will need to update firmware to run Sense Lollipop custom ROMs And unless you s-off and therefore able to update the firmware manually; your alternative will be to return to stock ROM and recovery and OTA to Lollipop.
Ohhh, Been trying to revert to stock but it just doesnt work. thanks
If I'm just rooted and not s off stock Rom and all that anything I need to do to get the lollipop update or just wait for it to hit my ota on my phone?
SOEBOMB said:
If I'm just rooted and not s off stock Rom and all that anything I need to do to get the lollipop update or just wait for it to hit my ota on my phone?
Click to expand...
Click to collapse
Just wait for it. If you're stock then you shouldn't have a problem. The only real headache will be how long you have to wait to get the OTA.
Stock: Stock ROM, Stock Recovery, No changes to system i.e no xposed framework. No deleted pre-installed apps(Facebook etc) no changes to files like platform.xml, build.prop etc.
Being rooted on the other hand shouldn't cause any problems.
I was rooted on OB7 with chainfire and the stock recovery image or whatever, it's been several years, well I used superSU and unrooted the phone and it still wouldn't let me do OTA. So tonight I downloaded the OF5 Rom and updated through Odin, Now it's telling me my device status is official and it's currently downloading the next update... The issue I am wondering about now is... Since it will OTA, I want to put UN7 on my phone and I don't want to update past PJ1, will it let me stop the updates?
Curtai said:
I was rooted on OB7 with chainfire and the stock recovery image or whatever, it's been several years, well I used superSU and unrooted the phone and it still wouldn't let me do OTA. So tonight I downloaded the OF5 Rom and updated through Odin, Now it's telling me my device status is official and it's currently downloading the next update... The issue I am wondering about now is... Since it will OTA, I want to put UN7 on my phone and I don't want to update past PJ1, will it let me stop the updates?
Click to expand...
Click to collapse
You got some OTA updates to go to get to PJ1 but there's a better way. You could get the PJ1 stock tar from the stock tar thread in general forum and upgrade through Odin again.
OTA is sequential patch updates. Stock tar is full updates. I'd recommend factory reset before flashing the marshmallow update to save time on initial boot optimization.
To answer your question about stopping the updates, turn off auto update feature in Settings when you get to PJ1. Follow the ROM OP to install once you get to PJ1- however you choose.
Note: Since your bootloader is now updated beyond OB7, keep in mind you cannot use Odin to flash full tars OB7 or lower. You cannot downgrade the bootloader but it's still possible to run older ROMs. I only recommend full stock tars no older than OG5.
Sent from my SM-N920P using Tapatalk
samep said:
You got some OTA updates to go to get to PJ1 but there's a better way. You could get the PJ1 stock tar from the stock tar thread in general forum and upgrade through Odin again.
OTA is sequential patch updates. Stock tar is full updates. I'd recommend factory reset before flashing the marshmallow update to save time on initial boot optimization.
To answer your question about stopping the updates, turn off auto update feature in Settings when you get to PJ1. Follow the ROM OP to install once you get to PJ1- however you choose.
Note: Since your bootloader is now updated beyond OB7, keep in mind you cannot use Odin to flash full tars OB7 or lower. You cannot downgrade the bootloader but it's still possible to run older ROMs. I only recommend full stock tars no older than OG5.
Sent from my SM-N920P using Tapatalk
Click to expand...
Click to collapse
So, now I am on PJ1 and I don't know how to put TWRP on my phone, I want to put tx_dbs_tx's UN7 hybrid on my phone and I am having issues both finding and putting TWRP on my phone... and I can't find a download or anything for it...
I've downloaded 2 different versions of twrp and used odin to put them on but I think I am doing something wrong because it isn't booting into twrp
Curtai said:
I was rooted on OB7 with chainfire and the stock recovery image or whatever, it's been several years, well I used superSU and unrooted the phone and it still wouldn't let me do OTA. So tonight I downloaded the OF5 Rom and updated through Odin, Now it's telling me my device status is official and it's currently downloading the next update... The issue I am wondering about now is... Since it will OTA, I want to put UN7 on my phone and I don't want to update past PJ1, will it let me stop the updates?
Click to expand...
Click to collapse
and of course I was missing a step... nobody said uncheck auto reboot and it kept keeping the bootloader locked
got it done now and I managed to get the custom rom installed... or at least I think it's working
Curtai said:
and of course I was missing a step... nobody said uncheck auto reboot and it kept keeping the bootloader locked
got it done now and I managed to get the custom rom installed... or at least I think it's working
Click to expand...
Click to collapse
Oh your talking about installing twrp? Yeah you have to not let it reboot. And when is done pull battery and boot into recovery to get it to stick. Obviously you figured it out. But just saying. I think earlier versions you didn't need to do that but now you do.
Glad you got it going. How you like the Rom? Running smooth for me.
ROM is good
Well I obviously got it going and didn't read the first couple posts after the install and didn't notice the SMS issue so I had that problem and I can't find a lot of the menu options that I had with the OB7 original I've been running for about 18 months... It's pretty smooth now and I'm wondering how fast it will fill up my internal memory I like that it's almost 20 gigs free.. for a while I was running on less than 6 I need to find an efficient way to use my external SD card... Other than that the options are neat but it seems really bloated all the extra Google apps make me sick even though I never use them... I've got titanium backup and am freezing them and will probably uninstall them soon... I want a small ROM that I can customize myself or apps that are easily removed or whatever half the apps I don't want are in ROM which is a pain to remove or I just don't know how to unless I use TB
Wow that's a novel sorry but yeah that's my ramblings for the next week I guess... Now I'm gonna hit the rack...