Related
Even though I'll probably be on to a new phone by the time the Inc 2 receives its OTA ICS update, I nevertheless want to be able to upgrade to it when it arrives. My question is, will the nandroid backup I have (Android version 2.3.3 with superuser but none of the bloat removed) be able to receive it? Or will I need to go through the whole process of unrooting and restoring 2.3.4 first?
Sent from my Incredible 2 using XDA
tattedupboy said:
Even though I'll probably be on to a new phone by the time the Inc 2 receives its OTA ICS update, I nevertheless want to be able to upgrade to it when it arrives. My question is, will the nandroid backup I have (Android version 2.3.3 with superuser but none of the bloat removed) be able to receive it? Or will I need to go through the whole process of unrooting and restoring 2.3.4 first?
Sent from my Incredible 2 using XDA
Click to expand...
Click to collapse
you wouldnt want to take the ota regardless as it will likely block root and might bring an hboot that cannot be reverted from
id imagine we d get a leak of the ota ahead of time or just wait for a dev to make an update.zip version of it once its pulled from the servers or a phone
I also had a question about the OTA update. I HTC unlocked and rooted with SU and CWM recovery. I do have some of the bloated apps uninstalled with Titanium Backup. As soon as I heard that the upgrade for ICS was coming out, I flashed the stock recovery from the most recent RUU. Does anyone forsee any problems recieving the ICS OTA with this setup?
Well, not sure I would have done it that way... with the stock recovery you lose CWM's capabilities waiting for Vzw to release the ICS upgrade, and that could take months and months. Additionally, if you accept the ICS OTA my guess is that you'll lose root as well, and be stuck with Vzw's typical bloatware until you re-root. And we don't know if the new OTA will be immediately re-rootable. Some of the previous upgrades have required reverting to earlier versions.
As nitsuj17 remarks a few posts earlier, I would imagine that once the ICS upgrade for the Dinc2 is released, somebody will quickly get hold of it and post up a version for us rooted folks and we can just flash it from CWM. And use TB or AntTek App manager or whatever tool is your favorite to freeze or delete the Vzw crap. That's what I'm planning to do...
HI ALL!!! I have been using XDA for years and have always had my questions answered without even have to post one....BUT, I recently bought a xperia play that was flashed to cricket. And I seen there was a new ota update but in my settings/about phone/ there is no update option which i think is very strange. Now I have root if that will help anyone and I'm currently on 2.3.3 & my bootloader is unlocked.
What can i do to be able to update my play? And is it even worth the update?
Thanks alot!!!
It is very good that there is no OTA update option for you. With an unlocked bootloader, you will brick your device with OTA updates ;-).
Don't know how you get updates, you will have to ask a pro - look around in the forum, but not via OTA
// it's not that strange that the option is gone - as you already said, your play is flashed and played with. The owner before you will have deleted the system app for OTA updates.
i just seen--- my bootloader is locked, sorry. But Yeah i got the phone already flashed. but from what i've been seeing, maybe the ota update is not all that good anyway.
I'm rooted but running a stock rom. Yesterday I got a notification of an OTA update trying to be pushed to my phone. I did some reading and found out it's the fault of Apple (insert several nasty words here) forcing Samsung to remove the global search function. I've delayed it twice now by 8 hours, but it says it won't delay any more, and will automatically install in 8 hours.
What's the easiest way to circumvent this? I'm sorry if it's been answered before, but I barely have time to post this thread because my life's so busy, so please have mercy and just point me in the right direction!
Root, flash cwm and install custom rom.
Sent from my GSIII
Same happened to me yesterday. Still searching a way to avoid update..
Sent from my SAMSUNG-SGH-I747 using xda premium
If you have root , install Titanium backup , and freeze "FWUpgrade 1.2.0".
If i am not mistaken that will prevent any OTA updates. Or as others said custom rom time.
I got the update but because I'm rooted, it never got pushed to the phone.
Sent from my Supercharged Inspire 4G
ghost77 said:
If you have root , install Titanium backup , and freeze "FWUpgrade 1.2.0".
If i am not mistaken that will prevent any OTA updates. Or as others said custom rom time.
Click to expand...
Click to collapse
Thank you! I've frozen it and will let everyone know in a few hours if it worked. Thanks!
maxh said:
Thank you! I've frozen it and will let everyone know in a few hours if it worked. Thanks!
Click to expand...
Click to collapse
You can also just take the update and replace the apk. It's linked to in the development section for root without tripping flash counter.
Life is a prison, death and release.
maxh said:
I'm rooted but running a stock rom. Yesterday I got a notification of an OTA update trying to be pushed to my phone. I did some reading and found out it's the fault of Apple (insert several nasty words here) forcing Samsung to remove the global search function. I've delayed it twice now by 8 hours, but it says it won't delay any more, and will automatically install in 8 hours.
What's the easiest way to circumvent this? I'm sorry if it's been answered before, but I barely have time to post this thread because my life's so busy, so please have mercy and just point me in the right direction!
Click to expand...
Click to collapse
If you are rooted and have CWM installed, the update will be downloaded to the phone, it will restart, but it will fail to install the update as it needs stock recovery for the update to happen. Your phone will restart again saying that the update has failed and you will be back to where you started.
Source: I was rooted and I wanted to update the OTA update. There was no way I could do it with CWM installed. I had to unroot the phone to get the update and root it again.
AlwaysNoob said:
If you are rooted and have CWM installed, the update will be downloaded to the phone, it will restart, but it will fail to install the update as it needs stock recovery for the update to happen. Your phone will restart again saying that the update has failed and you will be back to where you started.
Source: I was rooted and I wanted to update the OTA update. There was no way I could do it with CWM installed. I had to unroot the phone to get the update and root it again.
Click to expand...
Click to collapse
To confirm, this is exactly what happened.
Thanks!
I'd like to have the flexibility of choice - I want to be able to prevent my carrier, US Cellular, or Samsung from disabling our crippling the Note should I choose not to return it.
UPDATE: Answered here.
http://forum.xda-developers.com/showpost.php?p=69377632&postcount=42
Package disabler pro
Sent from my SM-N930F using Tapatalk
And then what?
how do you know it's gonna work? I would think OS updates would have been taken care outside of standard packages.
You can go to settings and set to manual updates. It won't "disable but it won't update unless you tell it to
Sent from my SM-G935T using Tapatalk
Well on my first note mine was set to manual and it pushed the update through regardless a few hours after the notification arrived. IMO anybody able to root has nothing to lose by rooting if they're intending to keep it at this point.
Package disabler. Disable System update SDM's. Don't touch anything to do with Knox though.
Disable these:
Security policy updates
Software update
System update 1
System update 2
I've had those frozen on both my original Note 7 and my replacement Note 7 and get no OTA's at all. Don't think they can push them to you with these disabled.
Just bought the Package Disable Pro+ Premium.
Strange.
Have disabled the "Security Policy updates" and "Software update", BUT my replaced Note7 does not have the 2 System Updates. processes.
Anyone knows what should I do?
Also I have the GearVR, and have not connected it to my handset after they push down the patch to disable the use with Note7.
Anyone knows which process to disable too, so that I can continue using the GearVR?
Pls help... Thanks!
flanky79 said:
Just bought the Package Disable Pro+ Premium.
Strange.
Have disabled the "Security Policy updates" and "Software update", BUT my replaced Note7 does not have the 2 System Updates. processes.
Anyone knows what should I do?
Also I have the GearVR, and have not connected it to my handset after they push down the patch to disable the use with Note7.
Anyone knows which process to disable too, so that I can continue using the GearVR?
Pls help... Thanks!
Click to expand...
Click to collapse
I think you have to edit the build-prop (which means you need to be rooted) to get the Gear VR to work.
As far as the 2 system sdm updates - they are on both my Note 7's, but then I haven't ever taken an OTA or any update as I disabled all of that first thing I got the phones (one was my OG N7, the other the replacement N7). So I can't help you if you have already taken an update, but those system SDMs should be there unless they removed them in an update somehow, which I doubt.
teegunn said:
I think you have to edit the build-prop (which means you need to be rooted) to get the Gear VR to work.
As far as the 2 system sdm updates - they are on both my Note 7's, but then I haven't ever taken an OTA or any update as I disabled all of that first thing I got the phones (one was my OG N7, the other the replacement N7). So I can't help you if you have already taken an update, but those system SDMs should be there unless they removed them in an update somehow, which I doubt.
Click to expand...
Click to collapse
Ya, after I received the replacement on 16/9/16 (Singapore), I received an OTA update within the next couple of days that give the green battery.
That is the only update I received.
If it helps, my version is 6.0.1,
Baseband: N960FXXU2BPI5
Build number: MMB29K.N930FXXU2BPI9
So strange...
Does that mean the only choice I have is to root the phone?
(I haven't rooted before)
What is the best "stock" rooted package now?
I'm fine with the default Samsung apps generally, and does not need to have much default functions disabled.
flanky79 said:
Ya, after I received the replacement on 16/9/16 (Singapore), I received an OTA update within the next couple of days that give the green battery.
That is the only update I received.
If it helps, my version is 6.0.1,
Baseband: N960FXXU2BPI5
Build number: MMB29K.N930FXXU2BPI9
So strange...
Does that mean the only choice I have is to root the phone?
(I haven't rooted before)
What is the best "stock" rooted package now?
I'm fine with the default Samsung apps generally, and does not need to have much default functions disabled.
Click to expand...
Click to collapse
This is the first Android phone I have not rooted. Ever. So honestly, I cannot guide you on the root process, as I never did it on either of my Note 7's. I was eventually going to root, but then the recalls hit and I figured there was no point since I will be giving it up soon. But if you took the green battery update, my understanding is that you cannot root and cannot go back to the previous firmware. I do not know if the update you took got rid of the two system update SDM's, someone else will have to help you with that. I would bet that you can still prevent further OTA's with package disabler pro - however, I do not know that for sure. Hopefully others will see this thread and these posts and chime in with info that clears this up for you.
I rooted my replacement note 7 (with green battery update) a few days ago with no problem in anticipation of a crippling update pushed by Samsung: http://forum.xda-developers.com/note-7/development/recovery-official-twrp-galaxy-note-7-t3446047. But by doing so you trigger knox and lose access to secure folder and shealth. I solved the shealth problem by disabling encryption on my device with Hydra Kernel http://forum.xda-developers.com/note-7/development/kernel-hydrakernel-v1-1-t3452433 while keeping stock ROM. I am considering changing to HydraRom http://forum.xda-developers.com/note-7/development/rom-hydra-rom-v1-0-t3447611 just in case.
Hope this helped!
Considering the fact that the phone automatically runs an update at its first boot is there a way to easily shield the device from the mobile network (so that it won't update)?
Cr4z33 said:
Considering the fact that the phone automatically runs an update at its first boot is there a way to easily shield the device from the mobile network (so that it won't update)?
Click to expand...
Click to collapse
Not sure... but you could try removing the sim card
LightningJay said:
Not sure... but you could try removing the sim card
Click to expand...
Click to collapse
OK then it needs a mobile data subscription?
I thought OTAs would be running 'for free' if they are from the same carrier you are connected to?
Sent from my Samsung Galaxy S7 edge with stock Samsung Marshmallow firmware
LightningJay said:
I rooted my replacement note 7 (with green battery update) a few days ago with no problem in anticipation of a crippling update pushed by Samsung: http://forum.xda-developers.com/note-7/development/recovery-official-twrp-galaxy-note-7-t3446047. But by doing so you trigger knox and lose access to secure folder and shealth. I solved the shealth problem by disabling encryption on my device with Hydra Kernel http://forum.xda-developers.com/note-7/development/kernel-hydrakernel-v1-1-t3452433 while keeping stock ROM. I am considering changing to HydraRom http://forum.xda-developers.com/note-7/development/rom-hydra-rom-v1-0-t3447611 just in case.
Hope this helped!
Click to expand...
Click to collapse
What is your replacement baseband Version that you rooted? By any chance was it PI4?
shellie03 said:
What is your replacement baseband Version that you rooted? By any chance was it PI4?
Click to expand...
Click to collapse
My baseband version is PI5
Nice! Can you paste a link of the root method you did, please?
Sent from my SM-N930T using XDA Premium HD app
shellie03 said:
Nice! Can you paste a link of the root method you did, please?
Sent from my SM-N930T using XDA Premium HD app
Click to expand...
Click to collapse
I followed this method http://forum.xda-developers.com/note-7/development/recovery-official-twrp-galaxy-note-7-t3446047
Cr4z33 said:
OK then it needs a mobile data subscription?
I thought OTAs would be running 'for free' if they are from the same carrier you are connected to?
Sent from my Samsung Galaxy S7 edge with stock Samsung Marshmallow firmware
Click to expand...
Click to collapse
My replacement N7 DL'd the update first thing. I did remove the sim and also shut off WIFI, but it had already DL'd the update. But I did not let it install the update. I rebooted and skipped activating the phone. I didn't do any of the first boot setup stuff - skipped all of that, then went to the play store, logged in with my gmail and first thing I installed as package disabler pro. I immediately disabled all the System updates (4 packages). After that I quit getting the notice to install the already DL'd update. Once you disable the System update SDM's, you can't even get into the phone update OTA selection in settings, it kicks you right out. So even though it had DL'd the update, I was able to prevent it from installing.
I do think the phone is trying to look for an update constantly now though. When I look at my GSM battery monitor, system updates is right near the top of what android system is using all the time. I still have excellent battery life, but I think disabling OTA system updates will make the phone constantly try to look for updates that it simply can't run because the SDM's are disabled. I can live with that as gimping the phone with a crappy OTA that limits the battery or might add other possible things I didn't want was the main goal. Phone runs great and battery life is great. That's all I need.
Hello All,
It been a while since I've been lurking on the forums. Last time I was here was just after when I got the pixel xl and needed to root and unlock it, and was looking for how to update.
Back then when the update past 7.1.1 released they were having issues keeping root and unlocked status after the update.
I'm looking to update my phone now to the newest, stable release, that will let me keep root and unlocked bootloader on a Verizon Google pixel xl.
Here is where I'm currently at:
Verizon Google pixel xl.
Rooted
Unlocked bootloader
7.1.1 (NOF27B) stock image
Flash fire installed
Twrp installed
As of late I've had the common battery issue with this version get worse as the phone ages and now after landing in Indianapolis a few hours ago I'm having radio issues that I'm hoping a fresh install or update will fix.
I'm just looking for some direction on what steps I need to do to update and not lose root or unlocked bootloader.
I need to get full functionality of my phone back asap, so I appreciate all of your help with this.
Thank you
Hobocoe said:
Hello All,
It been a while since I've been lurking on the forums. Last time I was here was just after when I got the pixel xl and needed to root and unlock it, and was looking for how to update.
Back then when the update past 7.1.1 released they were having issues keeping root and unlocked status after the update.
I'm looking to update my phone now to the newest, stable release, that will let me keep root and unlocked bootloader on a Verizon Google pixel xl.
Here is where I'm currently at:
Verizon Google pixel xl.
Rooted
Unlocked bootloader
7.1.1 (NOF27B) stock image
Flash fire installed
Twrp installed
As of late I've had the common battery issue with this version get worse as the phone ages and now after landing in Indianapolis a few hours ago I'm having radio issues that I'm hoping a fresh install or update will fix.
I'm just looking for some direction on what steps I need to do to update and not lose root or unlocked bootloader.
I need to get full functionality of my phone back asap, so I appreciate all of your help with this.
Thank you
Click to expand...
Click to collapse
This excellent guide by HomeBoy76 should give you all the info that you need....
https://forum.xda-developers.com/pixel-xl/how-to/guide-pixel-xl-android-8-1oreo-unlock-t3715279
Hobocoe said:
Hello All,
It been a while since I've been lurking on the forums. Last time I was here was just after when I got the pixel xl and needed to root and unlock it, and was looking for how to update.
Back then when the update past 7.1.1 released they were having issues keeping root and unlocked status after the update.
I'm looking to update my phone now to the newest, stable release, that will let me keep root and unlocked bootloader on a Verizon Google pixel xl.
Here is where I'm currently at:
Verizon Google pixel xl.
Rooted
Unlocked bootloader
7.1.1 (NOF27B) stock image
Flash fire installed
Twrp installed
As of late I've had the common battery issue with this version get worse as the phone ages and now after landing in Indianapolis a few hours ago I'm having radio issues that I'm hoping a fresh install or update will fix.
I'm just looking for some direction on what steps I need to do to update and not lose root or unlocked bootloader.
I need to get full functionality of my phone back asap, so I appreciate all of your help with this.
Thank you
Click to expand...
Click to collapse
I do not think there is anyway to upgrade the 7.1.1 firmware to 8.10 firmware and not lose root. I would suggest you use my guide and Do #4 wipe data and then do #7 root.
Why wipe data? There have been a lot of changes to the firmware since 7.1.1 (NOF27B) stock image.
Note: Copy/Backup the information on your internal storage you want to keep to your computer i.e., pictures SMS, files etc. Why? Because using flash-all with the -w will wipe your internal storage.
It's actually pretty simple, just download the latest factory image of either Oreo,. Flash the flash all script included with fast boot. Afterward boot into the system without setting up a pin or password or anything, set it up, then reboot into boot loader and boot the latest TWRP, then within TWRP flash TWRP zip file and Magisk root. Reboot system.
Homeboy76 said:
I do not think there is anyway to upgrade the 7.1.1 firmware to 8.10 firmware and not lose root. I would suggest you use my guide and Do #4 wipe data and then do #7 root.
Why wipe data? There have been a lot of changes to the firmware since 7.1.1 (NOF27B) stock image.
Note: Copy/Backup the information on your internal storage you want to keep to your computer i.e., pictures SMS, files etc. Why? Because using flash-all with the -w will wipe your internal storage.
Click to expand...
Click to collapse
Thank you everyone for the responses. Homeboy 76, I just had a quick question regarding your guide. The steps for the bootloader. Are you just showing all 3 options (unlock, lock, stock) for thurougness? Or do I have to return the bootloader to stock and lock it before I can install the update and root again?
Also I should test a factory reset before I try updating to see if my radio problem is worse than I expected. If I just go into the system and do a factory reset, besides losing root will it be fine doing that? Or does that get it into a weird root/stock limbo and brick it? Or prevent me from installing the update?
Thank you for your help with this. I just don't want to brick my phone while trying to fix it.
Hobocoe said:
Thank you everyone for the responses. Homeboy 76, I just had a quick question regarding your guide. The steps for the bootloader. Are you just showing all 3 options (unlock, lock, stock) for thurougness? Or do I have to return the bootloader to stock and lock it before I can install the update and root again?
Also I should test a factory reset before I try updating to see if my radio problem is worse than I expected. If I just go into the system and do a factory reset, besides losing root will it be fine doing that? Or does that get it into a weird root/stock limbo and brick it? Or prevent me from installing the update?
Thank you for your help with this. I just don't want to brick my phone while trying to fix it.
Click to expand...
Click to collapse
"...for thurougness?
Yes
Or do I have to return the bootloader to stock and lock it before I can install the update and root again?
No, Do not lock the boot loader.
Also I should test a factory reset before I try updating to see if my radio problem is worse than I expected. If I just go into the system and do a factory reset, besides losing root will it be fine doing that?
Yes
If it locks the bootloader, go here to unlock it:
[How-to] Unlock bootloader on Verizon Pixel/XL by burduli
Or does that get it into a weird root/stock limbo and brick it? Or prevent me from installing the update?
No, No.
Homeboy76 said:
"...for thurougness?
Yes
Or do I have to return the bootloader to stock and lock it before I can install the update and root again?
No, Do not lock the boot loader.
Also I should test a factory reset before I try updating to see if my radio problem is worse than I expected. If I just go into the system and do a factory reset, besides losing root will it be fine doing that?
Yes
If it locks the bootloader, go here to unlock it:
[How-to] Unlock bootloader on Verizon Pixel/XL by burduli
Or does that get it into a weird root/stock limbo and brick it? Or prevent me from installing the update?
No, No.
Click to expand...
Click to collapse
Thank you homeboy for the assistance. It's much appreciated. Luckily my phone issues were related to the location I was in. Indianapolis doesn't like my phone number for some reason.. But ill still be updating either way.
Thanks again.
Hobocoe said:
Thank you homeboy for the assistance. It's much appreciated. Luckily my phone issues were related to the location I was in. Indianapolis doesn't like my phone number for some reason.. But ill still be updating either way.
Thanks again.
Click to expand...
Click to collapse
You're welcome