Related
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!
OK so here's my problem... I'm trying to do some ota updates. my nexus 7 is on jss15j with elementalx kernel, custom 2.6.0.0 twrp recovery, 1.62supersu. I install the zip file from jss15j to jss15q ota update from xda, install the zip supersu fix, go to flash the ota update and it fails every time, no matter what I do. I also tried to flash to stock jss15j kernel and it also fails...
please help, I might just have to wait to get home and use the wug toolkit to flash the ota update but I'd like to be able to in twrp...
Philaphlous said:
OK so here's my problem... I'm trying to do some ota updates. my nexus 7 is on jss15j with elementalx kernel, custom 2.6.0.0 twrp recovery, 1.62supersu. I install the zip file from jss15j to jss15q ota update from xda, install the zip supersu fix, go to flash the ota update and it fails every time, no matter what I do. I also tried to flash to stock jss15j kernel and it also fails...
please help, I might just have to wait to get home and use the wug toolkit to flash the ota update but I'd like to be able to in twrp...
Click to expand...
Click to collapse
Assuming you have some reason you really want to run the ota rather than factory image with nowipe option... And you really want to install jss15q rather than latest jss15r...
Post the exact error message without the funny numbers. Either type or take a photo
sfhub said:
Assuming you have some reason you really want to run the ota rather than factory image with nowipe option... And you really want to install jss15q rather than latest jss15r...
Post the exact error message without the funny numbers. Either type or take a photo
Click to expand...
Click to collapse
OK, I'd love a factory image guide with nonwipe option if possible. latest is great too, I've got a lot of random reboots on jss15r...
I'll try to grab the error log
Philaphlous said:
OK, I'd love a factory image guide with nonwipe option if possible. latest is great too, I've got a lot of random reboots on jss15r...
I'll try to grab the error log
Click to expand...
Click to collapse
Just choose the nowipe option in this post.
http://forum.xda-developers.com/showthread.php?p=45671279#post45671279
Also when I said error log, I meant the error message from installing the ota update.zip. With that error message I can usually tell you why your ota update.zip is failing.
I was able to update this morning. I got home and was able to use the wug toolkit. I flashed back the stock recovery, flashed the stock kernel. Then was able to allow the update to jss15r, then flashed the updated custom twrp recovery, flashed elementalx back and I'm all good to go! Flashing stock recovery probably did it for me, not too much of a hassle. I was thinking I was going to have to do a full wipe...
Sent from my Nexus 7 using Tapatalk
Your issue was the custom kernel. If it was the OTA update zip and you were doing it via adb sideload, it checks for a stock boot image and if it doesn't find it, it errors out. I had this happen with faux123's kernel installed. I realized it when the error output said something about the boot image.
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 previously applied a patch from sfhub "boot-ts10-lock.img" but i flashed "boot-ts-unlock.img" before updating to accept the whole update from 4.4.2 (in case a Touchscreen fix is included.).
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!
Step one : Go to the right forum.
Wrong subforum, but basically it's because you're rooted. The easiest solution is to just flash the system.img file from the factory image via fastboot and you should be good to go :good:
Thread moved to the right sub-forum and to the right section...
arviverona said:
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 previously applied a patch from sfhub "boot-ts10-lock.img" but i flashed "boot-ts-unlock.img" before updating to accept the whole update from 4.4.2 (in case a Touchscreen fix is included.).
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!
Click to expand...
Click to collapse
ota updates only work on devices that are not modified i.e. patched but you can still be rooted (aosp browser, mods to system will bork any ota). if you do not know how to reverse the patch/mod you applied to you device you need to reflash a stock version of the system (search for stock images) then apply the ota.
OP: Uninstall stickmount (doing so will copy back the stock debuggerd), and try the OTA again.
Thanks guys!
I tried uninstalling the STICKMOUNT app but still update wont install OTA or manual method. Thanks anyway.
I guess i have to flash stock ROM.
Should i just use UNROOT setting in the Super SU menu rather than flashing stock ROM? i use stock rom and rooted it with SUPER SU.
Thanks,
arviverona said:
I tried uninstalling the STICKMOUNT app but still update wont install OTA or manual method. Thanks anyway.
I guess i have to flash stock ROM.
Should i just use UNROOT setting in the Super SU menu rather than flashing stock ROM? i use stock rom and rooted it with SUPER SU.
Thanks,
Click to expand...
Click to collapse
It's not root stopping the OTA. So unrooting is a waste of time. You can just put back the debuggerd file manually (using TWRP). You can find it in post 1 here:
http://forum.xda-developers.com/showthread.php?t=2534698
Direct link: http://forum.xda-developers.com/attachment.php?attachmentid=2403508&d=1384921832
...also make sure you have the latest TWRP. You will likely lose root once you do finally update, so be prepared to reroot using the latest SuperSU.
mdamaged said:
It's not root stopping the OTA. So unrooting is a waste of time. You can just put back the debuggerd file manually (using TWRP). You can find it in post 1 here:
http://forum.xda-developers.com/showthread.php?t=2534698
Direct link: http://forum.xda-developers.com/attachment.php?attachmentid=2403508&d=1384921832
...also make sure you have the latest TWRP. You will likely lose root once you do finally update, so be prepared to reroot using the latest SuperSU.
Click to expand...
Click to collapse
Is the debuggered flash work for DEB as well? I still havent taken the update to 4.4.2, its showing on my scree to touch and update. (rooted and unlocked), but if i plan to in the future, I will need that debuggered flash, newest SuperSU and newest TWRP (which i have now)
Duffmantp said:
Is the debuggered flash work for DEB as well? I still havent taken the update to 4.4.2, its showing on my scree to touch and update. (rooted and unlocked), but if i plan to in the future, I will need that debuggered flash, newest SuperSU and newest TWRP (which i have now)
Click to expand...
Click to collapse
It should work, worst case scenario, it will just complain ""/system/bin/debuggerd" has unexpected contents" ...stickmount made a copy of your debuggerd, it should still be in system/bin/debuggerd.backup, so you could restore that one or you could do a md5sum of that system/bin/debuggerd.backup with the one I linked and see if the md5sum matches, if it does, then the one I linked will work, if not, then make a flashable zip with the one that's in system/bin/debuggerd.backup and flash that one.
Just to reiterate what I stated earlier, if that debuggerd.backup is the correct one, then simply uninstalling stickmount SHOULD restore it without flashing, it worked for me going from 4.3 to 4.4.2. I verified this with md5sum before I took the OTA.
I can only postulate the reason it does not work for some is because the debuggerd.backup they have is from a older update, thereby the md5sum no longer checks out, so when they uninstall stickmount like I suggest, it's still the wrong debuggerd the update expects.
mdamaged said:
It should work, worst case scenario, it will just complain ""/system/bin/debuggerd" has unexpected contents" ...stickmount made a copy of your debuggerd, it should still be in system/bin/debuggerd.backup, so you could restore that one or you could do a md5sum of that system/bin/debuggerd.backup with the one I linked and see if the md5sum matches, if it does, then the one I linked will work, if not, then make a flashable zip with the one that's in system/bin/debuggerd.backup and flash that one.
Just to reiterate what I stated earlier, if that debuggerd.backup is the correct one, then simply uninstalling stickmount SHOULD restore it without flashing, it worked for me going from 4.3 to 4.4.2. I verified this with md5sum before I took the OTA.
I can only postulate the reason it does not work for some is because the debuggerd.backup they have is from a older update, thereby the md5sum no longer checks out, so when they uninstall stickmount like I suggest, it's still the wrong debuggerd the update expects.
Click to expand...
Click to collapse
Actually I dont have stickmount installed, if that makes a difference.
Duffmantp said:
Actually I dont have stickmount installed, if that makes a difference.
Click to expand...
Click to collapse
Well then your debuggerd should be stock, and this is all just academic. If the update fails, it won't be due to the debuggerd (unless there is some other app I do not know about that messes with debuggerd and you have that installed).
Duffmantp said:
Actually I dont have stickmount installed, if that makes a difference.
Click to expand...
Click to collapse
Xposed Framework installed? I know it modifies something in system/bin but can't remember exactly what it was.
wantabe said:
Xposed Framework installed? I know it modifies something in system/bin but can't remember exactly what it was.
Click to expand...
Click to collapse
That would be system/bin/app_process, using the uninstall feature in the xposed app restores it.
mdamaged said:
That would be system/bin/app_process, using the uninstall feature in the xposed app restores it.
Click to expand...
Click to collapse
That's it!
I'm trying to get my HTC M8 back to stock so I can get the new 4.4.3 update, however, I am unable to find the stock kernel for my device.
It is software version 1.54.401.10.
I flashed to the elementalx kernel and put on a TWRP recovery.
I am able to download the update but when it installs, it just goes into recovery.
I made a backup of the original kernel a few months ago however it doesn't seem to be on my phone anymore.
When I look for stock kernels they all seem to be different versions than my device.
Can someone give me a bit of advice?
There are numerous guides for other versions but none mentions my software version.
Any kernel doesn't matter.
Your problem is you don't flash stock recovery.
TWRP or any custom recovery don't work for OTA.
ckpv5 said:
Any kernel doesn't matter.
Your problem is you don't flash stock recovery.
TWRP or any custom recovery don't work for OTA.
Click to expand...
Click to collapse
How can I put the stock recovery back?
I put the stock recovery on and tried to update however I get a red triangle with an exclamation mark now...
why's it not taking properly?
I'm new to this obviously. I've figured out that's just how the stock recovery is. Now I'm trying to figure out why the ota doesn't work with the stock recovery.
I get this error when I try to install the update.
/system/lib/modules/adsprpc.ko has unexpected contents. Installation aborted.
robgo said:
I'm new to this obviously. I've figured out that's just how the stock recovery is. Now I'm trying to figure out why the ota doesn't work with the stock recovery.
I get this error when I try to install the update.
/system/lib/modules/adsprpc.ko has unexpected contents. Installation aborted.
Click to expand...
Click to collapse
This means that something of the system has been changed by you, so the ckecksum of the OTA doesn't match the configuration of your system and thus abort the installation process.
Sent from my HTC One_M8 using XDA Free mobile app
robgo said:
I'm new to this obviously. I've figured out that's just how the stock recovery is. Now I'm trying to figure out why the ota doesn't work with the stock recovery.
I get this error when I try to install the update.
/system/lib/modules/adsprpc.ko has unexpected contents. Installation aborted.
Click to expand...
Click to collapse
This means your ROM is modified, not pure stock.
I suggest you make a backup with your current ROM and restore the pure stock backup that I posted here : http://forum.xda-developers.com/showthread.php?p=54564526#post54564526
1. flash back the TWRP recovery
2. make backup of your current one
3. restore pure stock backup that I linked above
4. flash stock recovery
5. reboot then do the OTA
robgo said:
I'm new to this obviously. I've figured out that's just how the stock recovery is. Now I'm trying to figure out why the ota doesn't work with the stock recovery.
I get this error when I try to install the update.
/system/lib/modules/adsprpc.ko has unexpected contents. Installation aborted.
Click to expand...
Click to collapse
@robgo please close this thread http://forum.xda-developers.com/htc-one-m8/help/ota-update-4-4-3-t2856172. To open up two threads to aks the same question doesn't help to get to a solution any faster ....
Regarding the error. It means what @ckpv5 and I already told you.
ckpv5 said:
Any kernel doesn't matter.
Your problem is you don't flash stock recovery.
TWRP or any custom recovery don't work for OTA.
Click to expand...
Click to collapse
Oh ok, I didn't know the kernel apparently doesn't matter when doing OTA's and here I am telling him to go back to stock kernel because it's a kernel related error he has...
Best I keep out of this one then, I never even flashed another kernel.
BerndM14 said:
Oh ok, I didn't know the kernel apparently doesn't matter when doing OTA's and here I am telling him to go back to stock kernel because it's a kernel related error he has...
Best I keep out of this one then, I never even flashed another kernel.
Click to expand...
Click to collapse
Right ... it's kernel related error but to be precised, it's the kernel module error.
Flashing a stock kernel without flashing stock module, the same error will occur.
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.