Related
Hi im running this rom
http://forum.xda-developers.com/showthread.php?t=741775
and i have recieved a notification for new software update (the one with better russian keyboard) and i tried downloading but it didnt work. Is it possible to do this (im rooted with unrevoked)? Also would i lose my root? i dont care if i do, im more interested in getting the new update and unrooting, thanks
yes you would lose root.
you are aware that if you install it you may never be able to root your phone again? well at least until one of the devs here finds a way.
i'm sure that update will get rooted and added to the ROMs soon if they haven't been already.
but other than that if you don't care then you should be find installing it.
i tried updating using system update, but it wouldnt work, my clockwork mod said the update failed
how can i update to this safely?
i know theres a way, do u know it?
cgrec92 said:
yes you would lose root.
you are aware that if you install it you may never be able to root your phone again? well at least until one of the devs here finds a way.
i'm sure that update will get rooted and added to the ROMs soon if they haven't been already.
but other than that if you don't care then you should be find installing it.
Click to expand...
Click to collapse
It would be extremely easy to root the phone after installing this update...
adbirdie said:
i tried updating using system update, but it wouldnt work, my clockwork mod said the update failed
how can i update to this safely?
i know theres a way, do u know it?
Click to expand...
Click to collapse
You shouldn't try to install OTA updates to rooted phones. It usually won't work.
If you want the new version you can either install an RUU with the official version and then root, or you can install a newer rooted stock ROM through recovery.
yaaaaa bout that im on a mac, tehehe, and i dont mind losing my root
^havent heard of an ruu working on mac
The easiest thing for you to do is install a new custom ROM that is based on the new version (mine and a couple of others).
teppic74 said:
It would be extremely easy to root the phone after installing this update...
Click to expand...
Click to collapse
hence the third line of my post.
what if i just wanted the update and i didnt want my root tho?
Reboot into recovery, apply zip from sd card, toggle signature verification so its off, the update zip is downloaded to your sd cards download folder. Apply it. Then use unrevoked to root your phone again.
Sent from my HTC Desire
do i have to download the system update first, and then it will become update.zip, or is already do, can u walk me step by step through?
update: i tried what u said elmalote and it didnt work, what do i do now????
The ROM you are on has been updated with the latest OTA now so I'm not sure why you want to go another way than just flashing that ?
-----------------------------------
- Sent via my HTC Desire -
the ota didnt go throught properly, i did what elmalote said, but it said installation aborted
elmalote said:
Reboot into recovery, apply zip from sd card, toggle signature verification so its off, the update zip is downloaded to your sd cards download folder. Apply it. Then use unrevoked to root your phone again.
Sent from my HTC Desire
Click to expand...
Click to collapse
Is it a fully safe way to try install OTA update over the rooted ROM? I have branded ROM rooted using unrEVOked and I would like to try to install OTA update this way.
it didnt work for me, but if u try please tell me, it shouldnt screw up your phone.
does any one know how to install ota on a rooted phone
adbirdie said:
it didnt work for me, but if u try please tell me, it shouldnt screw up your phone.
Click to expand...
Click to collapse
I'm not so sure about that. I've looked into OTA update downloaded into sd-card and it contains:
- system updates (new files, patches and so on)
- recovery img
- hboot update
- radio image
So let's assume that I toogle verification process (turn it off). OTA update will install over rooted ROM. After this, I have new recovery (because OTA update contains it).
I can see possibility of bricking my phone, when following situation appears:
- OS doesn't start-up (fell into boot-loop, whatever)
- recovery is back to stock, so no possibility to restore from nandroid backups
What do you think about that? Can someone confirm this is safe/dangerous?
Barthand, relax, i tried this, and i just rebooted my phone and it was fine. if you don't want to do it, then don't, but don't fret. it didn't work for me but it didn't screw up my phone either, now back to the main problem does anyone else have any solutions to install ota on a rooted phone.
bump..........
Hi,
What are experiences of current owners of Nexus phones ? My Desire Z is rooted ( only rooted, don't have a custom ROM), and I never got Gingerbread update so I'd hate the same thing happening to G Nexus.
Thanks.
zljk said:
Hi,
What are experiences of current owners of Nexus phones ? My Desire Z is rooted ( only rooted, don't have a custom ROM), and I never got Gingerbread update so I'd hate the same thing happening to G Nexus.
Thanks.
Click to expand...
Click to collapse
That will never happen with the GN. When you own this phone you're first in line for the updates until the next is coming out then you're second but still faster than the others.
Sent from my HTC Desire using XDA App
When you're rooted you can't get the OTA updates. You have to unroot to apply them. That's true for all Android phones.
You cant get them at all?
Not even: get update and apply it, loose root because of the update, reroot?
Sent from my A500 using Tapatalk
TulpiX said:
You cant get them at all?
Not even: get update and apply it, loose root because of the update, reroot?
Sent from my A500 using Tapatalk
Click to expand...
Click to collapse
you could do that, but chances are someone will get the OTA before you and pre root it for everyones pleasure and you can just flash that via recovery
TulpiX said:
You cant get them at all?
Not even: get update and apply it, loose root because of the update, reroot?
Sent from my A500 using Tapatalk
Click to expand...
Click to collapse
If my experiences with my OG Droid match up with the Nexus line, if you've only rooted and haven't actually installed another ROM, you should be able to apply the OTA update and lose root because of it. Then just root again.
martonikaj said:
When you're rooted you can't get the OTA updates. You have to unroot to apply them. That's true for all Android phones.
Click to expand...
Click to collapse
I've seen some threads claiming that root itself doesn't affect updates, but changing of data on system partition.... Was kind of hoping there is a way to have my cake and eat it too - don't mind having to root the phone all over again after the OTA....
Anyhow - as an alternative, is there a way to get official Nexus updates ( stock ) using other channels except OTA ? What was happening with old Nexus phones ?
zljk said:
I've seen some threads claiming that root itself doesn't affect updates, but changing of data on system partition.... Was kind of hoping there is a way to have my cake and eat it too - don't mind having to root the phone all over again after the OTA....
Anyhow - as an alternative, is there a way to get official Nexus updates ( stock ) using other channels except OTA ? What was happening with old Nexus phones ?
Click to expand...
Click to collapse
The alternate way to get official Nexus updates is to download the update zip file once someone copies it off their device and uploads it, and install it in whatever fashion works.
I rooted my Nexus One without unlocking the bootloader or using custom recovery. I definitely still got OTA updates and they worked fine, but would unroot the phone.
The solution is to use a custom recovery and apply the update .zip manually, then reflash superuser before rebooting. Whenever an OTA update comes out, someone eventually uses logcat to get the URL to the zip and posts it so anyone can download it.
I was rooted on Froyo and got the OTA update to Gingerbread no problem, but I lost root. I eventually got root again (Gingerbreak) and when the 2.3.4 update came out, I did it manually in custom recovery to keep root.
Now I run CM7.1 so I definitely don't get OTA updates from Google
TulpiX said:
You cant get them at all?
Not even: get update and apply it, loose root because of the update, reroot?
Sent from my A500 using Tapatalk
Click to expand...
Click to collapse
It will often download and you can try but it will either fail, unroot you, or cause troubles.
You're best off applying the pre-rooted update, or unrooting and taking the OTA.
martonikaj said:
When you're rooted you can't get the OTA updates. You have to unroot to apply them. That's true for all Android phones.
Click to expand...
Click to collapse
True. However it's trivial to repackage an OTA update to a rooted update and since it's very compatible with the source in AOSP and you get working drivers very early you can start messing around with it straight away.
blunden said:
True. However it's trivial to repackage an OTA update to a rooted update and since it's very compatible with the source in AOSP and you get working drivers very early you can start messing around with it straight away.
Click to expand...
Click to collapse
Of course, as is often the case for most phones supported here on XDA. the rooted OTA comes in the form of a .zip soon after it comes out.
slowz3r said:
you could do that, but chances are someone will get the OTA before you and pre root it for everyones pleasure and you can just flash that via recovery
Click to expand...
Click to collapse
When flashing the rooted OTA via recovery, does it wipe the phone (apps and all)?
Also for the other method, when unrooting >> applying OTA >> rooting again, does it wipe the phone at any point during this process?
Help would be appreciated and rewarded!
I just received my OTA update notification and found the update zip itself in the cache of my phone. I can post that update zip here if a mod can come along and tell me where to put it. I am going to wait till I'm home so I can have my rooting facilities handy before starting.
phazerorg said:
I rooted my Nexus One without unlocking the bootloader or using custom recovery. I definitely still got OTA updates and they worked fine, but would unroot the phone.
The solution is to use a custom recovery and apply the update .zip manually, then reflash superuser before rebooting. Whenever an OTA update comes out, someone eventually uses logcat to get the URL to the zip and posts it so anyone can download it.
I was rooted on Froyo and got the OTA update to Gingerbread no problem, but I lost root. I eventually got root again (Gingerbreak) and when the 2.3.4 update came out, I did it manually in custom recovery to keep root.
Now I run CM7.1 so I definitely don't get OTA updates from Google
Click to expand...
Click to collapse
+1. Exactly.
There is a lot of wrong (or slightly incorrect) information in this thread.
Have root has no impact whatsoever in your ability to receive or apply the OTA update. This has been the case on every Android device. However, if you have a custom recovery flashed, you will not be able to automatically apply the update - you will have to find the zip file in the cache and use your custom recovery to apply it.
On a slightly separate note, once you apply the update either automatically or manually via custom recovery, you will lose root. However, if you do have a custom recovery, as long as you flash ChainsDD's superuser package immediately after applying the update, but before rebooting, you will retain root.
On another separate not, if you flash the update as is from Google, it includes a file (/system/recovery-from-boot.p) that re-flashes the stock recovery on every boot, so you will lose your custom recovery. Either remove the file before flashing the update, or just re-flash your custom recovery.
Anyone tried the recent OTA update using the "OTA survival" option in superuser?
I'm in AT&T S3, rooted but with stock recovery, using mrrobinson's method, building number I747UCALEM.
Wondering whether anyone has tried doing the OTA update and keeping root by using the "temp unroot" and/or "OTA survival" options in Superuser? If so, was it successful, and would you mind giving a quick rundown of the steps?
Thanks!
I did it, I installed Voodoo root keeper backed up my SU app with this app then I removed root with this app also, after thid I just hit the check for update and applied the OTA.
After appling OTA I went to Voodoo app and restored root.
It was very easy let me know if you need any more help.
Sent from my SAMSUNG-SGH-I747 using xda premium
IcOpRo said:
I did it, I installed Voodoo root keeper backed up my SU app with this app then I removed root with this app also, after thid I just hit the check for update and applied the OTA.
After appling OTA I went to Voodoo app and restored root.
It was very easy let me know if you need any more help.
Sent from my SAMSUNG-SGH-I747 using xda premium
Click to expand...
Click to collapse
Thanks for the reply. Sounds like you used another app, Voodoo Root Keeper, not Superuser?
Just to err on the side of caution, I should do the following?:
1. get voodoo root keeper
2. go into Superuser and check the "ota survival" box
3. go into voodoo hit "protect root"
4. still in voodoo hit "temp. un-root (keeps backup)"
5. go to about device>software update to check for update
6. apply update
7. once update completes, go back to voodoo? or superuser?
If you're on UCALEM and you're trying to get to the latest version (LH9), you'll have two OTAs to apply: LEM->LG1 and LG1->LH9.
Save yourself a headache and just flash a full LH9. That way you won't have to worry about root. You can find a full flashable LH9 here and also here (in the PIECES section at the bottom of the post).
Either way you go, make sure you make a nandroid first.
drothenberger said:
If you're on UCALEM and you're trying to get to the latest version (LH9), you'll have two OTAs to apply: LEM->LG1 and LG1->LH9.
Save yourself a headache and just flash a full LH9. That way you won't have to worry about root. You can find a full flashable LH9 here and also here (in the PIECES section at the bottom of the post).
Either way you go, make sure you make a nandroid first.
Click to expand...
Click to collapse
Thanks for this advice. I currently don't have a custom recovery installed. How do I go about making a nandroid without it? Do I need to install a custom recovery first?
jhc5 said:
Thanks for this advice. I currently don't have a custom recovery installed. How do I go about making a nandroid without it? Do I need to install a custom recovery first?
Click to expand...
Click to collapse
Sorry, I missed that you still had stock recovery installed. You'll need to have a custom recovery to use the zips from either of the links I posted. If you want to stay on stock recovery, you'll need to apply the two OTAs from AT&T to upgrade.
To install a stock recovery, you can:
Install ROM Manager and use that to flash CWM
Install GooManager and use that flash TWRP
Follow the instructions in this post
Currently trying to update my Nexus 7 to JSS15R (8MB OTA that may have helped multitouch issue?)
I am running rooted stock ROM, unlocked bootloader etc. Current build number is JSS15Q.
I've heard the newer versions of SuperSU have the OTA fix built in. I haven't been able to update though. I noticed there was an update and I went to update my Nexus 7. It went to update like it should, but I got an error and it never changed.
Flashed the OTA fix thinking it would help. No.
Forced OTA update by stopping Google Framework. No.
Flashed SuperSU 1.65 and tried to update again. No.
Any suggestions on what I should do? Manually flash the update without loosing root or an data?
Did you reflash the ota after you flashed supersu?
What was the error message?
sfhub said:
Did you reflash the ota after you flashed supersu?
What was the error message?
Click to expand...
Click to collapse
I read the new SuperSU versions have the OTA fix built in which allows OTA update.
When I initially went to update before everything, it rebooted then just came up with the "open android guy" with an error. Not sure what it exactly said, but I ran into the problem when I updated to JSS15Q.
I updated to JSS15Q by flashing the SuperSU OTA update fix with temporary TWRP. It then went through no problem. I followed that same method this time, but it didn't work.
When I did the j to q update while rooted the ota had an error as well. I had to install the full q rom from google. (I'm stock with root and I changed the system font) But this time around when I got the r ota I double checked what version supersu was runing and its at 1.65. I applied the r ota with no errors.
church said:
When I did the j to q update while rooted the ota had an error as well. I had to install the full q rom from google. (I'm stock with root and I changed the system font) But this time around when I got the r ota I double checked what version supersu was runing and its at 1.65. I applied the r ota with no errors.
Click to expand...
Click to collapse
Yeah I'm running 1.65 currently, but the update won't show up anymore. Check for updates and there's nothing.
datallboy said:
Yeah I'm running 1.65 currently, but the update won't show up anymore. Check for updates and there's nothing.
Click to expand...
Click to collapse
If its like the last issue with J to Q. You are updated but it doesn't show the name change in system. I could be wrong. It should have already been downloaded to your tablet. Check with a root explorer to find the ota zip or download the R ota found somewhere on this forum and manually flash it. I'm glad I didn't have to mess with anything this time around.
church said:
If its like the last issue with J to Q. You are updated but it doesn't show the name change in system. I could be wrong. It should have already been downloaded to your tablet. Check with a root explorer to find the ota zip or download the R ota found somewhere on this forum and manually flash it. I'm glad I didn't have to mess with anything this time around.
Click to expand...
Click to collapse
I found a zip for the ota update, don't remember where, but should I be able just to flash it with TWRP without loosing anything?
It will lose the option to blend milkshakes
church said:
It will lose the option to blend milkshakes
Click to expand...
Click to collapse
Not asking for sarcasm, just solutions. Will I lose root or any data? Or is it just like OTA update if I do it manually.
Oh you're using twrp? Disregard what I said. I'm coming from stock with stock recovery and rooted.
church said:
Oh you're using twrp? Disregard what I said. I'm coming from stock with stock recovery and rooted.
Click to expand...
Click to collapse
Stock recovery is on my device. I'm temporarily booting TWRP with the Nexus Toolkit so I can flash things.
datallboy said:
I read the new SuperSU versions have the OTA fix built in which allows OTA update.
When I initially went to update before everything, it rebooted then just came up with the "open android guy" with an error. Not sure what it exactly said, but I ran into the problem when I updated to JSS15Q.
I updated to JSS15Q by flashing the SuperSU OTA update fix with temporary TWRP. It then went through no problem. I followed that same method this time, but it didn't work.
Click to expand...
Click to collapse
Next time you have an error with stock recovery (android fallen down) press/hold power, then press/release VolUp, then release Power.
This will show you the error log.
As to your current problem, if your unit won't download and notify you about JSS15R download it by hand and place in your virtual sdcard, then temporary boot into tarp and choose install, selecting the ota zip.
---------- Post added at 08:58 PM ---------- Previous post was at 08:55 PM ----------
datallboy said:
Not asking for sarcasm, just solutions. Will I lose root or any data? Or is it just like OTA update if I do it manually.
Click to expand...
Click to collapse
Install the ota update.zip, then before reboot, immediately install supersu.
Do it that way and you won't lose root.
Forced OTA and it failed. I had already flashed the superSU.zip before
If you can't read this is the log...
Finding update package...
Opening update package...
Verifying update package...
Installing update...
Verifying current system...
assert failed: apply_patch_check ("/system/build.prop" [numbers and letters]
E: Error in /cache/(update file.zip)
(Status 7)
Installation aborted.
Any way to manually flash the update? Because SuperSU OTA isn't working.
So, you modified the build.prop, restore your backup of the original and it will work. Or flash the full factory image.
Guhrasoh said:
So, you modified the build.prop, restore your backup of the original and it will work. Or flash the full factory image.
Click to expand...
Click to collapse
Now that you mention it I tweaked it with PimpMyRom. I'll take that off and try to update.
I am a bit late, but I tried fixed my build.prop to its original state and I still can't OTA update...
I noticed on stock recovery there's an option to update with ADB. Is there an update file I can use to just manually install the update? I know the JSS15R update didn't do much, but I would like to know for future reference and when Android 4.4 is released.
datallboy said:
I am a bit late, but I tried fixed my build.prop to its original state and I still can't OTA update...
I noticed on stock recovery there's an option to update with ADB. Is there an update file I can use to just manually install the update? I know the JSS15R update didn't do much, but I would like to know for future reference and when Android 4.4 is released.
Click to expand...
Click to collapse
The same OTA update.zip you used before is used to do sideload in adb as well.
You'll also get the same errors if you have modified files.
If you post the errors, they can be diagnosed.
If you modified a lot of files, sometimes it is easier using the factory images.
sfhub said:
The same OTA update.zip you used before is used to do sideload in adb as well.
You'll also get the same errors if you have modified files.
If you post the errors, they can be diagnosed.
If you modified a lot of files, sometimes it is easier using the factory images.
Click to expand...
Click to collapse
Status 7 error, the log is posted in one of the above posts. I use "PimpMyROM" for a short while, which modifies the file. I deleted all the tweaks that went into the build.prop.
datallboy said:
Status 7 error, the log is posted in one of the above posts. I use "PimpMyROM" for a short while, which modifies the file. I deleted all the tweaks that went into the build.prop.
Click to expand...
Click to collapse
Unless you are very careful with your edit or made a backup, you need to get the real file. When you edit, even if you have an extra space left over, the sha1 checksum check will fail.
sfhub said:
Unless you are very careful with your edit or made a backup, you need to get the real file. When you edit, even if you have an extra space left over, the sha1 checksum check will fail.
Click to expand...
Click to collapse
I'll probably just backup apps + data and use JSS15R factory image. Made the mistake of not making a backup of my build.prop.
Good thing it's a Nexus Device!
When you get and accept the ota update it downloads into your storage, would it be possible to use the stock recovery to find it and reinstall?
Pp.
PanchoPlanet said:
When you get and accept the ota update it downloads into your storage, would it be possible to use the stock recovery to find it and reinstall?
Pp.
Click to expand...
Click to collapse
Can't you pull the recovery.img out?
Sent from my SM-G925T using XDA Free mobile app
Sorry but I don't pull anything.
I just download.
Pp.
I've posted the G925T's OF6 stock recovery over in the OP of this thread. Is that what you're looking for?
Aou said:
I've posted the G925T's OF6 stock recovery over in the OP of this thread. Is that what you're looking for?
Click to expand...
Click to collapse
Was wondering if I find ota download that I accepted when I updated, can I use that downloaded ota file and use stock recovery to reinstall update.
When you accept ota a file is download into your storage (don't know where ) just wanted to find and reflash.
After ota phone went from great to awesome, but decided to play with smartswitch and reinstall / restore after back up, but after restore I lost the ability to disable tmobile my account app.
After ota I had the ability to disable, after smartswitch no option to disable? ???
Pp. Thanks for input.
Still no answer to my question. ???
Pp.
PanchoPlanet said:
Was wondering if I find ota download that I accepted when I updated, can I use that downloaded ota file and use stock recovery to reinstall update.
When you accept ota a file is download into your storage (don't know where ) just wanted to find and reflash.
After ota phone went from great to awesome, but decided to play with smartswitch and reinstall / restore after back up, but after restore I lost the ability to disable tmobile my account app.
After ota I had the ability to disable, after smartswitch no option to disable? ???
Pp. Thanks for input.
Click to expand...
Click to collapse
Sorry, I must have accidentally marked this as "Read" or something.
To answer the first question: no. Even if you found the OTA update.zip, it's useless once you are already updated. The update.zip files only contain patches for files, and patches for whole partitions. The first thing it does is check to see what version you currently have, and if it doesn't match what it's expecting, it will abort. Past that, even if you fool it somehow, it verifies every single file that it is going to patch. If it finds something it is not expecting, it will abort.
As for disabling the T-Mobile app, I don't really know. I think on 5.0.2 I disabled it, but then I rooted right away and started freezing all the bloat soon after. On 5.1.1 leak, I think I still had that disabled. By the time OF6 came around, I believe it was still disabled. Don't know for sure now, because I'm rooted again and have all this stuff frozen with TiBu.