Basically I have the preview build of Jelly Bean (JRN84D) but it keeps alerting me to install the OTA version which fails, I know there are lots of threads about this but I can't seem to find the answer in them, I tried flashing the stock recovery but when I try to boot into it I get the Red exclamation mark and can't do anything with the volume or power keys, this is the same exclamation mark I get when trying to install the update.
I think the recovery file may be corrupt, is this the key to getting OTA update? Also my radio is XXLF1 if that helps. Thanks for any help offered, I watched the video and everybody hates noobs but I tried the solutions in other posts and it seems to have got worse.
EDIT: I can access recovery now, but the update still fails.
Sgtpanda said:
Basically I have the preview build of Jelly Bean (JRN84D) but it keeps alerting me to install the OTA version which fails, I know there are lots of threads about this but I can't seem to find the answer in them, I tried flashing the stock recovery but when I try to boot into it I get the Red exclamation mark and can't do anything with the volume or power keys, this is the same exclamation mark I get when trying to install the update.
I think the recovery file may be corrupt, is this the key to getting OTA update? Also my radio is XXLF1 if that helps. Thanks for any help offered, I watched the video and everybody hates noobs but I tried the solutions in other posts and it seems to have got worse.
EDIT: I can access recovery now, but the update still fails.
Click to expand...
Click to collapse
Flash the Stock Recovery/Radio/Bootloader for Takju from the hosted Google Factory Images through Fastboot. It won't erase your data/apps. For the Recovery, you will need to extract it manually from the image while the bootloader and radio should be standalone.
dnlsmy said:
Flash the Stock Recovery/Radio/Bootloader for Takju from the hosted Google Factory Images through Fastboot. It won't erase your data/apps. For the Recovery, you will need to extract it manually from the image while the bootloader and radio should be standalone.
Click to expand...
Click to collapse
When you say the Takju Google Factory Image do you mean the 4.0.4 takju image? as that's the only one I can find on their site.
Thanks.
Sgtpanda said:
When you say the Takju Google Factory Image do you mean the 4.0.4 takju image? as that's the only one I can find on their site.
Thanks.
Click to expand...
Click to collapse
Yes.
Sent from my Galaxy Nexus using xda app-developers app
wilsonlam97 said:
Yes.
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
Flashed the radio, bootloader and recovery from it and it still doesn't work, if I press up and power button after it fails it gives me a status 7 error, might just flash stock and unroot if there's no other way.
Sgtpanda said:
Flashed the radio, bootloader and recovery from it and it still doesn't work, if I press up and power button after it fails it gives me a status 7 error, might just flash stock and unroot if there's no other way.
Click to expand...
Click to collapse
What is the error?
Sent from my Galaxy Nexus using Tapatalk 2
efrant said:
What is the error?
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
E: Error in /cache/edfff6d328f1.signed-takju-JRO03C-from-JRN84D.edfff6d3.zip
(Status 7)
Installation aborted.
Any ideas or am I screwed and should go ahead and try flash stock rom and unroot? Will that even help?
Sgtpanda said:
E: Error in /cache/edfff6d328f1.signed-takju-JRO03C-from-JRN84D.edfff6d3.zip
(Status 7)
Installation aborted.
Click to expand...
Click to collapse
What's the FULL error.
Also, are you using a recovery that is different from CWM 5.5.0.2 or 5.5.0.4? If so, get rid of it, and use one of those.
efrant said:
What's the FULL error.
Also, are you using a recovery that is different from CWM 5.5.0.2 or 5.5.0.4? If so, get rid of it, and use one of those.
Click to expand...
Click to collapse
I'm using stock recovery because everything I've read says to use stock if you want to accept OTA updates, the full error is:
Finding update package...
Opening update package...
Verifying update package...
Installing update...
Verifying current system...
assert failed: apply_patch_check("/system/app/ApplicationsProvider.apk","08db09578758c61cf5c8ec895b1331a5fa4cc349","512784ba869d55f3cf2d291baaa5f6a0aa90b960")
E: Error in /cache/edfff6d328f1.signed-takju-JRO03C-from-JRN84D.edfff6d3.zip
(Status 7)
Installation aborted.
Sgtpanda said:
I'm using stock recovery because everything I've read says to use stock if you want to accept OTA updates, the full error is:
Finding update package...
Opening update package...
Verifying update package...
Installing update...
Verifying current system...
assert failed: apply_patch_check("/system/app/ApplicationsProvider.apk","08db09578758c61cf5c8ec895b1331a5fa4cc349","512784ba869d55f3cf2d291baaa5f6a0aa90b960")
E: Error in /cache/edfff6d328f1.signed-takju-JRO03C-from-JRN84D.edfff6d3.zip
(Status 7)
Installation aborted.
Click to expand...
Click to collapse
Where did you get the preview build? Based on that error, it would seem to me like you flashed a non-stock version of JB 4.1 like bigxie's ROM. If that is the case, you need to flash a stock ROM before any update can be applied...
efrant said:
Where did you get the preview build? Based on that error, it would seem to me like you flashed a non-stock version of JB 4.1 like bigxie's ROM. If that is the case, you need to flash a stock ROM before any update can be applied...
Click to expand...
Click to collapse
Now that you've mentioned that name, yes that's the ROM I got, I'm gonna go ahead and guess there's no way to return to stock without wiping data is there?
Sgtpanda said:
Now that you've mentioned that name, yes that's the ROM I got, I'm gonna go ahead and guess there's no way to return to stock without wiping data is there?
Click to expand...
Click to collapse
Maybe. You can try this without wiping and see if it works. Then apply the JRO03C-from-JRN84D update form here.
efrant said:
Maybe. You can try this without wiping and see if it works. Then apply the JRO03C-from-JRN84D update form here.
Click to expand...
Click to collapse
And if I do that then will I be able to accept any future OTA updates through android and have it update automatically without having to flash the updates myself?
Sgtpanda said:
And if I do that then will I be able to accept any future OTA updates through android and have it update automatically without having to flash the updates myself?
Click to expand...
Click to collapse
If you follow method 2, then yes, you will be able to automatically accept OTA updates and have it install automatically. BUT, you MAY need to do the first one (i.e., to JRO03C) manually (if you don't get it shortly after you flash JRN84D). After that, you will be all set for the next update.
efrant said:
If you follow method 2, then yes, you will be able to automatically accept OTA updates and have it install automatically. BUT, you MAY need to do the first one (i.e., to JRO03C) manually (if you don't get it shortly after you flash JRN84D). After that, you will be all set for the next update.
Click to expand...
Click to collapse
I'll try it, thanks for the help.
EDIT: It worked! Did it without wiping and it accepted the OTA without needing to do it manually, once again thanks so much for helping!
First of all, please excuse my noobishness. Please show some compassion
I have a Samsung Galaxy S III, AT&T rooted, not having luck installing ROM. I've tried CM and it errors out.
The goal is to upgrade from Android version 4.0.4.
I have ClockworkMod Recovery v6.0.4.7 if that makes any difference.
Any help would be appreciated.
Thanks!
What installation errors are you getting?
audit13 said:
What installation errors are you getting?
Click to expand...
Click to collapse
Installing update....
set_perm: some changes failed
E: Error in /data/media/cm-10.2.0-d2att.zip
(Status 7)
Installation aborted.
You may need to update your boot loader..... Not sure though.
Sent from my d2lte using xda app-developers app
The status 7 error can be caused by an outdated recovery which, in your case, wouldn't be the case.
You need to make sure that your bootloader is supported by the rom you want to install. You can find the rom's supported bootloader in the rom's updater script file.
audit13 said:
The status 7 error can be caused by an outdated recovery which, in your case, wouldn't be the case.
You need to make sure that your bootloader is supported by the rom you want to install. You can find the rom's supported bootloader in the rom's updater script file.
Click to expand...
Click to collapse
Is updating the bootloader an option?
Arbaj said:
Is updating the bootloader an option?
Click to expand...
Click to collapse
You can update the bootloader but, for CM-based ROMs, you can update to a 4.1.1 or 4.1.2 bootloader and it should work. I wouldn't update to the latest 4.3 bootloader unless you have to.
delete
robgo said:
Can anyone tell me what this error could mean?
/system/lib/modules/adsprpc.ko has unexpected contents. Installation aborted.
I have my phone rooted, s-on, with elementalx kernel. I'm trying to get ota update but it stops and gives me that error.
Click to expand...
Click to collapse
You have to be stock in order to install the OTA, that as far as I know also includes stock Kernel seeing as the file adsprpc.ko is the problem, .ko files are kernel loadables.
Try installing stock kernel and try again.
Thread closed no longer needed.
Ghost
Hi everyone,
I posted this thread in General Discussion Q&A and then found this forum, so I posted once again in hoping to get some solution.
I have updated my rooted Nexus 7 2013-LTE using the method described here from 4.4.2 to 4.4.3 succesfully:
liliputing.com/2014/06/upgrade-nexus-android-4-4-3-without-losing-root.html
I used SuperSU and Xposed framework was temporarily uninstalled. However, when I tried the same procedure to update from 4.4.3 to 4.4.4, following errors are appearing:
file "/system/bin/debuggerd" doesn't have any of expected sha1 sums; checking cache
failed to stat "/cache/saved.file": No such file or directory
failed to load cache file
script aborted: "/system/bin/debuggerd" has unexpected contents.
"/system/bin/debuggerd" has unexpected contents.
E:Error in /cache/0c3dd9bfb71f2b8437be322e6cab5832ce2b4d35.signed-razorg-KTU84P-from-KTU84L.0c3dd9bf.zip
(Status 7)
Installation aborted.
It seems that file debuggerd is somehow changed (my guess by stickmount app). Is it correct that I have to replace the one installed in my /system/bin/ with the original one to continue updating to 4.4.4? Does anyone have the original debuggerd file nexus 7 2013-lte 4.4.3?
Thx u all
hood2ts said:
It seems that file debuggerd is somehow changed (my guess by stickmount app). Is it correct that I have to replace the one installed in my /system/bin/ with the original one to continue updating to 4.4.4? Does anyone have the original debuggerd file nexus 7 2013-lte 4.4.3?
Thx u all
Click to expand...
Click to collapse
Did you try uninstalling stick mount first? That should put the original debuggerd back.
Did you flash back to the stock recovery before accepting the OTA?
meekrawb said:
Did you try uninstalling stick mount first? That should put the original debuggerd back.
Click to expand...
Click to collapse
I tried uninstalling stickmount, but the debuggerd file is still unchanged. The OTA update is still failed. Anyway, thank u for suggesting an idea.
nhizzat said:
Did you flash back to the stock recovery before accepting the OTA?
Click to expand...
Click to collapse
Nice thing to update using method described in:
liliputing.com/2014/06/upgrade-nexus-android-4-4-3-without-losing-root.html,
is that you move forward with what you have. Will try flashing back to the stock revovery if that simpler method not working .
Not sure why anybody would make a guide on how to update without losing root. Worried about losing data and settings? Sure. Worried about losing root? Never.
If you want simple, you can either use adb sideload with the stock recovery or flash the OTA in a custom recovery like you would any other zip file. If you find you don't have root, flash SuperSU.zip again.
Finally, I used NRT to flash to 4.4.4 using system image with option not to wipe data. Many thanks to nhizzat and meekrawb.
I have an LG G3 on T-Mobile, running android 4.4.2 and my software version is D85110r. I downloaded and installed Stump Root and when I load the app it says "Device is already Rooted". Then I remember I had previously rooted the phone last summer when I got it. But I'm having issues with several apps not working because of root permission. So then I download and install SuperSU and when I run it, it gives me the message, "There is no SU binary installed, and SuperSU cannot install it." It then says something about if you have android 4.3 you need to re-root your phone. How do I proceed? Do I need to un-root my phone and then re-root? Thanks for any help you can provide!
Anyone?
same here. I am not on 4.3 but still getting the same message. Fix?
Leykis said:
I have an LG G3 on T-Mobile, running android 4.4.2 and my software version is D85110r. I downloaded and installed Stump Root and when I load the app it says "Device is already Rooted". Then I remember I had previously rooted the phone last summer when I got it. But I'm having issues with several apps not working because of root permission. So then I download and install SuperSU and when I run it, it gives me the message, "There is no SU binary installed, and SuperSU cannot install it." It then says something about if you have android 4.3 you need to re-root your phone. How do I proceed? Do I need to un-root my phone and then re-root? Thanks for any help you can provide!
Click to expand...
Click to collapse
Hello! I had no problems rooting my F400k with this root tool.. I also tried rooting with Stump but it failed many times.. I suggest format your phone then try this root tool. Look at number 5 of this post.
Attached is the root tool. Good luck
Showtek1980 said:
Hello! I had no problems rooting my F400k with this root tool.. I also tried rooting with Stump but it failed many times.. I suggest format your phone then try this root tool. Look at number 5 of this post.
Attached is the root tool. Good luck
Click to expand...
Click to collapse
This thing does not work as of JANUARY 17. The phone does not go into recovery mod, but just restarts once you click run.bat file
sharkoparko said:
This thing does not work as of JANUARY 17. The phone does not go into recovery mod, but just restarts once you click run.bat file
Click to expand...
Click to collapse
You've flashed other root tools like Stump, etc.. right? It probably left some files behind after unrooting.. Factory reset and try that root tool again.. I've always used it and rooting was a breeze!:fingers-crossed::good: If you have updated to the latest firmware then maybe rooting isn't possible at the moment. Try downgrading to the previous version you had after you've factory resetted and used that root tool.. Good luck mate!