Help !!!
I just updated my NEXUS 7 2013 from 4.4 to 4.4.2 but after restarting, the Android version in settings still says 4.4.
I checked for updates again in System Updates menu but my device says the system is up to date.
My device is Nexus 7 2013 32G rooted under TWRP 2.6.3.1 recovery on Super SU root.
I also tried updating manually using TWRP zip update but it failed.
here's the part of the prompt during TWRP update:
Verifying current system...
"/system/bin/debuggerd" has unexpected contents.
E: Error executing updater binary in zip '/sdcard/Dow...
Hope someone can help me find a solution for this. Thanks!
I auto updated my nexus 7 2013 wifi 32gb with 4.2.2 and there were no problems. I put the device back to stock 4.4 first and unrooted the tablet as well. My suggestion is to get the toolkit and select any version for device then select flash stock and unroot box. I did this and received the ota update the next day. After updating successfully you can root and install custom recovery again if that is what you want. Do not OEM lock the device because every time you unlock it again you will erase all content.
Best of luck
Sent from my Nexus 7 using xda app-developers app
OP: Uninstall stickmount (easiest) or flash the debuggerd in this thread.
Yea it won't update if your rooted.
-sent from my LG G2 using XDA Premium 4
player911 said:
Yea it won't update if your rooted.
-sent from my LG G2 using XDA Premium 4
Click to expand...
Click to collapse
Being rooted is fine. I was rooted just had to uninstall stickmount, and it updated from 4.3 to 4.4.2, I did lose root, but that was easily rectified.
mdamaged said:
Being rooted is fine. I was rooted just had to uninstall stickmount, and it updated from 4.3 to 4.4.2, I did lose root, but that was easily rectified.
Click to expand...
Click to collapse
How did you update? Side-load?
I'm guessing the Stickmount issue is only present on 4.4 because I was on 4.4.1 (Stock Rooted ROM by Scroler) and flashed the OTA I received on device in TWRP and it successfully updated to 4.4.2...and I never lost root ?
Sent from my Nexus 7 using Tapatalk 4
Richieboy67 said:
How did you update? Side-load?
Click to expand...
Click to collapse
Nope, OTA.
thanks
Jleeblanch said:
I'm guessing the Stickmount issue is only present on 4.4 because I was on 4.4.1 (Stock Rooted ROM by Scroler) and flashed the OTA I received on device in TWRP and it successfully updated to 4.4.2...and I never lost root ?
Sent from my Nexus 7 using Tapatalk 4
Click to expand...
Click to collapse
Can you give us the link to the stock rooted rom by scroler?? i can't seem to find it anywhere. thnks alot!
mdamaged said:
Nope, OTA.
Click to expand...
Click to collapse
Cool, I just ran the update myself with no issues. I just changed back to the stock recovery first and ran the ota to 4.4 no problem. I was worried about it though because I had issues when doing my Nexus 4 but it was my fault. At the end in the recovery when it asked if I wanted it to fix root I clicked yes. I should have clicked no and just rerooted using wug or something.
Now I am going to grab the 4.4.2 update. I do not have ota yet for 4.1 or 4.2 on my Nex 7. My Nex 4 though is all set at 4.4.2 and it seems like they really fixed tons of stuff! I can't wait to get that on the 7!!
Thanks:good:
mdamaged said:
OP: Uninstall stickmount (easiest) or flash the debuggerd in this thread.
Click to expand...
Click to collapse
I used to have OTA problems with Stickmount and that damn debuggered file on my 2012 Nexus 7. Never installed it on my flo as a result.
Are you saying that simply uninstalling Stickmount will be sufficient for an OTA to take successfully? Does uninstalling reinstate the previous debuggered file, or must we replace it manually?
mlj11 said:
I used to have OTA problems with Stickmount and that damn debuggered file on my 2012 Nexus 7. Never installed it on my flo as a result.
Are you saying that simply uninstalling Stickmount will be sufficient for an OTA to take successfully? Does uninstalling reinstate the previous debuggered file, or must we replace it manually?
Click to expand...
Click to collapse
Yes. Upon installation, Stickmount makes a backup of debuggerd in the same directory with a bak extension, when uninstalled it renames it to debuggerd, restoring the stock debuggerd, I did not have to put it back manually.
player911 said:
Yea it won't update if your rooted.
-sent from my LG G2 using XDA Premium 4
Click to expand...
Click to collapse
I flashed 4.4.1-> 4.4.2 successfully with twrp on a rooted device but it was just rooted with a modified host file, no other mods.
godutch said:
I flashed 4.4.1-> 4.4.2 successfully with twrp on a rooted device but it was just rooted with a modified host file, no other mods.
Click to expand...
Click to collapse
I thought the issue was to do with OTA updates and and not flashing updates from recovery as this is defeating the purpose of OTA udates.
Sent from my Nexus 7 using xda app-developers app
I am on 4.3, unlocked and rooted with TWRP recovery.
The 4.42 update notification had been there for a while and I finally decided to take the plunge.....
I ran the update through the notification and my device rebooted into the TWRP custom recovery. Not knowing what to do, I rebooted again and checked the version. Nothing had changed and I am still at 4.3.
However the System Update notification had disappeared. I checked for System Update and it says my device is up-to-date....
How do I get the OTA update again?
What do I have to do to get the update installed on my device?
I have since also uninstalled StickMount.
vivre said:
I am on 4.3, unlocked and rooted with TWRP recovery.
The 4.42 update notification had been there for a while and I finally decided to take the plunge.....
I ran the update through the notification and my device rebooted into the TWRP custom recovery. Not knowing what to do, I rebooted again and checked the version. Nothing had changed and I am still at 4.3.
However the System Update notification had disappeared. I checked for System Update and it says my device is up-to-date....
How do I get the OTA update again?
What do I have to do to get the update installed on my device?
I have since also uninstalled StickMount.
Click to expand...
Click to collapse
You could always just do a full wipe and restore it to factory defaults. That'll do it for sure.
Sent from my Nexus 7 using Tapatalk
dmginc said:
You could always just do a full wipe and restore it to factory defaults. That'll do it for sure.
Sent from my Nexus 7 using Tapatalk
Click to expand...
Click to collapse
Anyway to do it without wiping data? :crying:
vivre said:
Anyway to do it without wiping data? :crying:
Click to expand...
Click to collapse
Sorta yeah. But it hurts more than it helps. Wiping is really the best way to go. Or just wait a day or two and see if it comes.
Sent from my Nexus 7 using Tapatalk
vivre said:
I am on 4.3, unlocked and rooted with TWRP recovery.
The 4.42 update notification had been there for a while and I finally decided to take the plunge.....
I ran the update through the notification and my device rebooted into the TWRP custom recovery. Not knowing what to do, I rebooted again and checked the version. Nothing had changed and I am still at 4.3.
However the System Update notification had disappeared. I checked for System Update and it says my device is up-to-date....
How do I get the OTA update again?
What do I have to do to get the update installed on my device?
I have since also uninstalled StickMount.
Click to expand...
Click to collapse
The over the air will not work if you have a custom recovery. You have to flash the update zip with TWRP or whatever custom recovery you are using. You could move the update from "cache" to "storage" if you still had it or just download it to storage and then flash (Install) it with TWRP..
wantabe said:
The over the air will not work if you have a custom recovery. You have to flash the update zip with TWRP or whatever custom recovery you are using. You could move the update from "cache" to "storage" if you still had it or just download it to storage and then flash (Install) it with TWRP..
Click to expand...
Click to collapse
Thanks.
Your method worked.... but only after I uninstalled Xposed Framework ! :good:
Related
The official OTA link is http://d-h.st/3j0.
The update script checks for all the original .apks, .odexs, etc. Update fails when any of the original files are missing.
Sorry..not familiar with Moto..Gonna update wife's phone. What's the next step... Rename to update.zip and place in root of sdcard? Phone is stock not rooted.
Sent from my SCH-I535 using Tapatalk 2
caifan said:
Sorry..not familiar with Moto..Gonna update wife's phone. What's the next step... Rename to update.zip and place in root of sdcard? Phone is stock not rooted.
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
Correct.
Rename "Update.zip"
Place in root of sdcard "/mnt/external1/"
Reboot into recovery
-Shutdown
-Press Volume-Up and Power simultaneously until Motorola logo appears
-Press Volume-Up and Volume-Down simultaneously when you see the android with the ! from his open chest
-Scroll down to and select "Apply Update from External Storage"
-Scroll to and select "Update.zip"
-Grab a beer and wait
ThunderThief said:
Correct.
Rename "Update.zip"
Place in root of sdcard "/mnt/external1/"
Reboot into recovery
-Shutdown
-Press Volume-Up and Power simultaneously until Motorola logo appears
-Press Volume-Up and Volume-Down simultaneously when you see the android with the ! from his open chest
-Scroll down to and select "Apply Update from External Storage"
-Scroll to and select "Update.zip"
-Grab a beer and wait
Click to expand...
Click to collapse
dont even have to rename. just drop on sd and apple update. thanks for the upload OP.
Doesn't work if you are on the leak. Complains about build.prop not matching. Haven't tried changing it though...
Sent from my XT907 using xda app-developers app
So this is the official jelly bean update without any bugs or anything?
Sent from my XT907 using Tapatalk 2
sototallycarl said:
Doesn't work if you are on the leak. Complains about build.prop not matching. Haven't tried changing it though...
Sent from my XT907 using xda app-developers app
Click to expand...
Click to collapse
Don't try. You got to sbf.
Sent from my XT907 using Tapatalk 2
Edit: Nope, no need for SBF on a Safestrap phone, just go back into Safestrap and uninstall the recovery.
I was getting a Status 7 failure from logwrapper but it does not require SBF to fix. Hooray!
Paramemetic said:
Edit: Nope, no need for SBF on a Safestrap phone, just go back into Safestrap and uninstall the recovery.
I was getting a Status 7 failure from logwrapper but it does not require SBF to fix. Hooray!
Click to expand...
Click to collapse
Did you uninstall any bloat apps? If so, did you restore a backup or is everything just working for you? I am rooted on JB leak and uninstalled many bloat apps and just trying to figure out what my next step is here. And what does SBF stand for? Sorry for the ignorance, never owned a locked bootloader phone before so this is all new lol.
00McD00 said:
Did you uninstall any bloat apps? If so, did you restore a backup or is everything just working for you? I am rooted on JB leak and uninstalled many bloat apps and just trying to figure out what my next step is here. And what does SBF stand for? Sorry for the ignorance, never owned a locked bootloader phone before so this is all new lol.
Click to expand...
Click to collapse
I only disabled bloat apps, didn't uninstall any. It checks to make sure all system apps are present (but not enabled). Your only option if you've uninstalled bloat apps using something like TiBu and if you've installed the JB leak is to revert to ICS factory image. SBF is "system boot file."
You're going to need to grab the ICS fastboot file from the dev forum and install it before either the OTA or this will work.
Root on its own is not a problem but if you have changed system apps (bloat is all "system") you'll need to do that.
If you installed safestrap that's fine, but you have to uninstall the recovery using the app before this will work because it checks the boot sequence.
Is the official update going to be worth it if we already have the leaked jellybean? All the sites I've read provide the same information regarding the new features for the update (all the same as the jellybean leak). If anyone has updated to the official jellybean from the leaked can you provide any information regarding the differences between the two
Confirmed working, and according to the Verizon PDF this official version has improved 4g reception as well as less drops on signal, improved WiFi and Bluetooth its running fine for me, going to try root and safe strap now
---------- Post added at 06:18 AM ---------- Previous post was at 06:07 AM ----------
Root not working which means safe strap is not working.... reverting back too old jb leak for the time being
Installed and working great.
OTARootkeeper backed up root then temp uninstalled root. Booted into stock recovery, flashed OTA from sd card, booted up, restored root, made sure entitlement_check was still set to "0"....tested stock hotspot app and works great.
Thanks OP for providing the link.
Can't wait for a non Verizon version of this. The RAZR M has to be my favorite android phone so far - great form factor and great hardware... just being stuck on ice cream sandwich is a bit **** but I'm prepared to wait
Sent from my XT905 using xda app-developers app
jarzy00 said:
So this is the official jelly bean update without any bugs or anything?
Sent from my XT907 using Tapatalk 2
Click to expand...
Click to collapse
Yes, this is Verizon's official OTA. I haven't been running long so I will not comment much on stability. For the first few minutes one system app continuously force closed and restarted and the notification bar / soft keys disappeared. A reboot solved those problems.
got556 said:
Installed and working great.
OTARootkeeper backed up root then temp uninstalled root. Booted into stock recovery, flashed OTA from sd card, booted up, restored root, made sure entitlement_check was still set to "0"....tested stock hotspot app and works great.
Thanks OP for providing the link.
Click to expand...
Click to collapse
The SU binaries were deleted during my install, despite OTARootkeeper. However superuser responded to app requests giving the appearance of root.
And you are welcome.
ThunderThief said:
The SU binaries were deleted during my install, despite OTARootkeeper. However superuser responded to app requests giving the appearance of root.
And you are welcome.
Click to expand...
Click to collapse
Root checker stated I was rooted. May have to check again to make sure the binaries are still there. Will mess w/ her (g/f's) phone when she's done using it.
Just went back to Jellywiz from Paranoid on my S3 w/ some new radios we got leaked, so been busy setting all my crap back up.
Really hoping we can get Pimp My Rom on the M soon.
I also had no issues re-rooting with OTA Rootkeeper after manual update. I think I'm enjoying project butter the most!
If I install this like other people did with the leaked version, will I have any issues if there is ever another update?
techfellow said:
If I install this like other people did with the leaked version, will I have any issues if there is ever another update?
Click to expand...
Click to collapse
I don't think that will be a problem.
So I updated to 4.1.2 recently and decided I'd simply root my phone. Now today I have the AT&T updater telling me I have an update pending. I'm already on 4.1.2 and the only possible reason I could conceive as to why this is popping up is because during rooting something must have changed and that flagged the updater as me having an obsolete firmware. Anyone else getting this?
mrmcpowned said:
So I updated to 4.1.2 recently and decided I'd simply root my phone. Now today I have the AT&T updater telling me I have an update pending. I'm already on 4.1.2 and the only possible reason I could conceive as to why this is popping up is because during rooting something must have changed and that flagged the updater as me having an obsolete firmware. Anyone else getting this?
Click to expand...
Click to collapse
What is your current firmware
Sent from my GT-N7105 using xda premium
4.1.2 Baseband I317UCALK7 Build Number JZO54K.I317UCALK7
mrmcpowned said:
4.1.2 Baseband I317UCALK7 Build Number JZO54K.I317UCALK7
Click to expand...
Click to collapse
The latest is actually I317UCAMA4; the ALK7 is the one right before that
Thanks, I have TWRP installed so do I have to reinstall the stock recovery and then continue the update and whatnot?
Don't waste your time with the ATT update; just flash almost any custom ROM, and you will have all the benefits plus much more...
wase4711 said:
Don't waste your time with the ATT update; just flash almost any custom ROM, and you will have all the benefits plus much more...
Click to expand...
Click to collapse
I agree, but if you want to upgrade, use cf auto root to reinstall stock recovery, use full unroot in super su, then run update
Sent from my GT-N7105 using xda premium
Android The Greek said:
I agree, but if you want to upgrade, use cf auto root to reinstall stock recovery, use full unroot in super su, then run update
Sent from my GT-N7105 using xda premium
Click to expand...
Click to collapse
I've tried this, but the update still fails. Could it be my modified system files from setting up Google wallet?
Sent from my Nexus 7 using xda app-developers app
bookem11 said:
I've tried this, but the update still fails. Could it be my modified system files from setting up Google wallet?
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
Could be, I always keep a stock backup jsut incase. You can always dirty flash a stock rom and see if that works
Sent from my GT-N7105 using xda premium
If you are going to stick with stock, you may want to use autoruns to disable the check for updates. That way at least the notification will go away.
Android The Greek said:
I agree, but if you want to upgrade, use cf auto root to reinstall stock recovery, use full unroot in super su, then run update
Click to expand...
Click to collapse
I did all of the above. Update was downloaded successfully, Phone reboot itself and started installing update. And than "updated was interrupted" message popped out. I've tried it several times with the same result.
Any ideas what I'm doing wrong?
Hello i tried to install OTA the new update to my galaxy nexus but it failed. I tried also to install it using custom recovery but again it failed to install it. Does anyone know how i can install it without to lose my data?
In your custom recovery it should tell you why it failed. My guess is that something about your setup isn't stock, you will need to get it back to stock.
cupfulloflol said:
In your custom recovery it should tell you why it failed. My guess is that something about your setup isn't stock, you will need to get it back to stock.
Click to expand...
Click to collapse
i have found the solution. You have to open superSU go to settings and select full unroot. Then it allows you to update over the air!!!
Same issue
giwrgos said:
i have found the solution. You have to open superSU go to settings and select full unroot. Then it allows you to update over the air!!!
Click to expand...
Click to collapse
Hi, I have the same issue: JWR66Y from JWR66V failed. I just get "error" after reboot.
-i don't have root, using the stock image
-i've gone from yakjuxw to takju thanks to Efrant's guide :http://forum.xda-developers.com/showthread.php?t=1626895
So, I have 2 questions:
1.Is it possible to do the OTA in this case ?
2.Is it possible to get rid of the OTA ?
Any of the above will do just fine.
Thanks !
My issue is a little different. I got the OTA to update on my N4 via not having any modifications on my phone and having the the latest SuperSU v1.55. I remained rooted and ran the update via Flashify in TWRP 2.6 It was successful however I lost root and TWRP. My problem is now I cannot flash a custom recovery (via fastboot), for some reason they just don't stick and I am searching for help now.
Garymeister said:
My issue is a little different. I got the OTA to update on my N4 via not having any modifications on my phone and having the the latest SuperSU v1.55. I remained rooted and ran the update via Flashify in TWRP 2.6 It was successful however I lost root and TWRP. My problem is now I cannot flash a custom recovery (via fastboot), for some reason they just don't stick and I am searching for help now.
Click to expand...
Click to collapse
Is USB debugging selected in developer options?
Sent from my Galaxy Nexus using XDA Premium HD app
mrgnex said:
Is USB debugging selected in developer options?
Sent from my Galaxy Nexus using XDA Premium HD app
Click to expand...
Click to collapse
Haha I just figured that out not long ago. Wasn't sure if it was relevant but it worked!
Sent from my Nexus 4 using Tapatalk 4
I have a i9250 gsm Galaxy Nexus, maguro. JWR66V. It used to be Yajuux but I changed this to Yakju with Wug Fresh's Nexus Tool kit. I manually updated my phone to 4.3. However, about once a week, I get a notice that my phone would like to update to 4.3. The download is only 1.7mb. Once I allow the update, the phone reset, boots up and says "installing system update" with the android mascot on the screen and a swirly atom-thing at his stomach. After about a minute a message comes up that says "error!" with the android mascot now on his back. I have to remove the battery and restart my phone, otherwise it hangs. The update notice won't come back for another week, unless I stop the google service framework app and clear the data. I'm assuming these system updates are to upgrade to JWR66Y, but I don't know why I keep having these errors. Any help/advice would be appreciated.
Figured it out
Solved. I managed to sideload the update through the Nexus toolkit. Even after updating though, it didn't show the correct version. I had to unroot by uninstalling supersu (survival mode didn't work), then doing the OTA update, then reinstalling the binaries for Supersu.
Can anyone recommend a good site/feed that keeps track of these security updates/other major updates?
And the toolkit gets the credits, even when the user still has no idea what just happened.
beekay201 said:
And the toolkit gets the credits, even when the user still has no idea what just happened.
Click to expand...
Click to collapse
braindead users win again!
No Clue..
Can someone, Experienced.. Tell me what exactly to do here.. I am on Stock Rom, Rooted, with TWRP Recovery. Exact same problem when I try to install the Update. Same 1.7 MB Update. Any Help would be much appreciated.
dipenv said:
Can someone, Experienced.. Tell me what exactly to do here.. I am on Stock Rom, Rooted, with TWRP Recovery. Exact same problem when I try to install the Update. Same 1.7 MB Update. Any Help would be much appreciated.
Click to expand...
Click to collapse
The reason the update doesn't install is because you are using a third party recovery.img (twrp) and Android cannot update your phone with twrp, only with it's own recovery. You can download the update posted in one of the threads and install from twrp.
Sent from my Nexus 7 using Tapatalk 4
chrisinsocalif said:
The reason the update doesn't install is because you are using a third party recovery.img (twrp) and Android cannot update your phone with twrp, only with it's own recovery. You can download the update posted in one of the threads and install from twrp.
Sent from my Nexus 7 using Tapatalk 4
Click to expand...
Click to collapse
Thank you for this explanation. Very helpful to braindead user like myself, and will help me know what to do for future updates.
chrisinsocalif said:
The reason the update doesn't install is because you are using a third party recovery.img (twrp) and Android cannot update your phone with twrp, only with it's own recovery. You can download the update posted in one of the threads and install from twrp.
Sent from my Nexus 7 using Tapatalk 4
Click to expand...
Click to collapse
Does doing this wipe the phone?
Not if you only install the update. You will have to reinstall supersu after the update because you will lose root.
Sent from my Galaxy Nexus using Tapatalk 2
chrisinsocalif said:
The reason the update doesn't install is because you are using a third party recovery.img (twrp) and Android cannot update your phone with twrp, only with it's own recovery. You can download the update posted in one of the threads and install from twrp.
Sent from my Nexus 7 using Tapatalk 4
Click to expand...
Click to collapse
thats not correct. ive updated with OTAs through TWRP.
the update is failing because something isnt stock.
Zepius said:
thats not correct. ive updated with OTAs through TWRP.
the update is failing because something isnt stock.
Click to expand...
Click to collapse
Update through twrp by downloading the update not through ota since you have third party software.
Sent from my Nexus 7 using Tapatalk 4
chrisinsocalif said:
Update through twrp by downloading the update not through ota since you have third party software.
Sent from my Nexus 7 using Tapatalk 4
Click to expand...
Click to collapse
Requesting the download link if possible. Searched the forum but couldn't found one. Tx in Advance.
Solved. Got it! HERE
I get " Your device has been modified, software updates are not available." when checking for OTA updates in settings. Does that mean I have to flash via Odin and wipe my device for every update?
Sent from my SM-P600 using XDA Premium HD app
{Diemex} said:
I get " Your device has been modified, software updates are not available." when checking for OTA updates in settings. Does that mean I have to flash via Odin and wipe my device for every update?
Sent from my SM-P600 using XDA Premium HD app
Click to expand...
Click to collapse
No, just unroot using Super SU, then reboot. Once you're back up, check for updates and they will now come through, then after the update is done, reroot, I just did all of that so I know it will work.
Didn't work for me. I removed quite a lot of Samsung apps and other things I don't need ( atm. 51 apps). I defrosted all of them to see it that was causing it. I also unrooted multiple times to no avail.
Sent from my SM-P600 using XDA Premium HD app
{Diemex} said:
Didn't work for me. I removed quite a lot of Samsung apps and other things I don't need ( atm. 51 apps). I defrosted all of them to see it that was causing it. I also unrooted multiple times to no avail.
Sent from my SM-P600 using XDA Premium HD app
Click to expand...
Click to collapse
That's weird, I even forgot to defrost the Knox apps and the update still applied successfully. The Knox apps were the only ones I froze, and since the update was successful it must have unfrozen them when I un rooted, either that or the update didn't touch any files related to Knox, or maybe freezing apps still shows them as there to system and fw updates.
I'm getting the same message. I think it's because I deleted a few system apps, instead of just freezing them. I just have to find another copy of Windows, so I can use Odin.
I don't have anything deleted, unfrozen everything, unroot, keep getting the same message.
Did you guys re flash the stock recovery after rooting?
apascual89 said:
Did you guys re flash the stock recovery after rooting?
Click to expand...
Click to collapse
I did
RobN17 said:
I did
Click to expand...
Click to collapse
I did too, keep getting the same "device is modified" message.
{Diemex} said:
I get " Your device has been modified, software updates are not available." when checking for OTA updates in settings. Does that mean I have to flash via Odin and wipe my device for every update?
Sent from my SM-P600 using XDA Premium HD app
Click to expand...
Click to collapse
Will Triangle Away help with resetting flash counter?
Sent from my SAMSUNG-SGH-I317 using Tapatalk
wilsonhuang said:
Will Triangle Away help with resetting flash counter?
Sent from my SAMSUNG-SGH-I317 using Tapatalk
Click to expand...
Click to collapse
Flash stock recovery solved the problem for me!
But after I downloaded to update it said that failed to update, and told me to use Kies. However on Kies it said latest update is already installed.
Anyone?
59408500 said:
Flash stock recovery solved the problem for me!
But after I downloaded to update it said that failed to update, and told me to use Kies. However on Kies it said latest update is already installed.
Anyone?
Click to expand...
Click to collapse
I am currently having the exact same problem.
one step i did when i got the error was to reroot and then unroot just to make sure that it unrooted properly and to unfreeze all the apps i had frozen. i also cleared the cache in recovery.
madsquabbles said:
one step i did when i got the error was to reroot and then unroot just to make sure that it unrooted properly and to unfreeze all the apps i had frozen. i also cleared the cache in recovery.
Click to expand...
Click to collapse
How do I get to recovery mode?
adb reboot recovery in a command prompt or terminal emulator.
or hold power and volume up at boot up.
Nothing worked for me to get the OTA. For some reason I was able to update using Kies. It took forever to download the update but it worked.
californiarailroader said:
That's weird, I even forgot to defrost the Knox apps and the update still applied successfully. The Knox apps were the only ones I froze, and since the update was successful it must have unfrozen them when I un rooted, either that or the update didn't touch any files related to Knox, or maybe freezing apps still shows them as there to system and fw updates.
Click to expand...
Click to collapse
Did Samsung provide another update since MJ4?
dhonzik said:
Did Samsung provide another update since MJ4?
Click to expand...
Click to collapse
Yeah, they just released MK1 here in the US-
http://forum.xda-developers.com/showthread.php?t=2508479
madsquabbles said:
Adb reboot recovery in a command prompt or terminal emulator, or hold power and volume up at boot up.
Click to expand...
Click to collapse
Evidently just unrooting doesn't do it for everybody, so the cache must be cleared as well to allow updates again.
californiarailroader said:
Evidently just unrooting doesn't do it for everybody, so the cache must be cleared as well to allow updates again.
Click to expand...
Click to collapse
Damn you beat me to it! haha