Sideload MM after TWRP and Root - X Style (Pure) Q&A, Help & Troubleshooting

OK, since I have discovered the only way Band 12 works is with the OTA rather than a zip ROM I would like to sideload the OTA. But I am unable to because I hit file verification errors. Any suggestions as how I can get back to factory and sideload form there?
FYI, the return to stock app is not the solution as it only works for Lollipop.
Thanks in advance!

Related

4.3 OTA Update Failed - Bad debuggerd file

Trying to do the 4.3 OTA update. It fails with the message indicating that /system/bin/debuggerd does not have the expected entries.
Looks like Stickmount probably corrupted the file.
Could someone please post an original /system/bin/debuggerd file from Nexus 10 for version 4.2.2 / JDQ39?
It would be greatly appreciated.
Thanks a lot in advance.
I searched all over for this damn file and only ever found one for the N7 which didn't work. Extracted this one from the N10 4.2.2 factory image and successfully updated.
https://mega.co.nz/#!8MkiBAYR!JLj5Wso5EFM6Apn3zspM7hoDtlwl-2_17qW1JDwadn0
Hopefully this link works, otherwise PM me.
Sent from my Nexus 10 using XDA Premium HD app
Thank you so much!!!
It worked perfectly!
I dropped the file in place with Root Explorer in ES File Manager.
Then used TWRP adb sideload to apply the OTA update file.
Then I used Goo Manager to reinstall TWRP recovery.
Then used TWRP adb sideload to apply the SuperSU 1.51 zip file to restore root.
All is good.....Thanks again
djd216 said:
Thank you so much!!!
It worked perfectly!
I dropped the file in place with Root Explorer in ES File Manager.
Then used TWRP adb sideload to apply the OTA update file.
Then I used Goo Manager to reinstall TWRP recovery.
Then used TWRP adb sideload to apply the SuperSU 1.51 zip file to restore root.
All is good.....Thanks again
Click to expand...
Click to collapse
I just ran the normal OTA update, then used CF-Autoroot, which also worked fine for anyone wondering (It has been updated for 1.51).

[Q] Unable to sideload stock OTA 4.3 JWR66Y from JWR66V - set_perm Status 7

I have a new tab that I manually updated via fastboot to 4.3 JWR66V. It is unlocked and rooted, but does not have a custom recovery or anything else unusual on it.
I received a notification of an OTA update and found that JWR66Y has been released. When I tried to run the OTA update, it just left me at the "No Command" prompt, so I downloaded the zip 847b52d071443031e1addb3a54c4df75d29037ae.signed-mantaray-JWR66Y-from-JWR66V.847b52d0.zip and tried to use adb sideload to upgrade.
The sideload starts, but after a short while, it errors out with the following:
set_perm some changes failed
error in /tmp/update.zip
(Status 7)
Does anyone know what might be going on here? I was trying to keep the device clean and close enough to stock that I'd be able to easily upgrade OTA or at the very least with adb sideload, but I'd obviously prefer to keep root so I can use things like Titanium and such.
DEinspanjer said:
I have a new tab that I manually updated via fastboot to 4.3 JWR66V. It is unlocked and rooted, but does not have a custom recovery or anything else unusual on it.
I received a notification of an OTA update and found that JWR66Y has been released. When I tried to run the OTA update, it just left me at the "No Command" prompt, so I downloaded the zip 847b52d071443031e1addb3a54c4df75d29037ae.signed-mantaray-JWR66Y-from-JWR66V.847b52d0.zip and tried to use adb sideload to upgrade.
The sideload starts, but after a short while, it errors out with the following:
set_perm some changes failed
error in /tmp/update.zip
(Status 7)
Does anyone know what might be going on here? I was trying to keep the device clean and close enough to stock that I'd be able to easily upgrade OTA or at the very least with adb sideload, but I'd obviously prefer to keep root so I can use things like Titanium and such.
Click to expand...
Click to collapse
With mine I installed TWRP to install the OTA, went good. And then I flashed Stock Recovery again .
"This Story Ends Where It Began" - Octavarium (Dream Theater)
Sent from my GT-I9505
The problem is because of root. You have to unroot (scroll all the way down through the SuperSu settings and do a full unroot), then apply the OTA, and re-root.
nyijedi said:
The problem is because of root. You have to unroot (scroll all the way down through the SuperSu settings and do a full unroot), then apply the OTA, and re-root.
Click to expand...
Click to collapse
That's correct, after unrooting the device, the update installed successfully. Thanks.
Further follow-up for future readers.
There was a recent update to SuperSU that indicated in the changelog it fixed a problem with root blocking OTA upgrades. I received a new OTA offer this weekend, and it was able to apply with no problem despite still being rooted with the latest SuperSU.
Thank you very much for the assistance all.
kual said:
That's correct, after unrooting the device, the update installed successfully. Thanks.
Click to expand...
Click to collapse
hi , I'm trying to update my nexus 10 to kitkat 4.4 and have a same problem.
The error in /tmp/update.zip.
I unrooted it but I still had a same error .
What should I do to fix it?
thaibinh0496 said:
hi , I'm trying to update my nexus 10 to kitkat 4.4 and have a same problem.
The error in /tmp/update.zip.
I unrooted it but I still had a same error .
What should I do to fix it?
Click to expand...
Click to collapse
Hi, i had the same error when trying to update to kitkat via ADB sideload OTA update. The problem was in the file "/system/bin/debuggerd", which was changed by SuperSu and may be by Stickmount. Update reported Error 7 while checking system.
So i replaced file "debuggerd" using root explorer with the unchanged version from factory image of JWR66Y and then uninstalled SuperSu (because it continued to change this file after reboot).
After that OTA update was applied successfully.
kual said:
Hi, i had the same error when trying to update to kitkat via ADB sideload OTA update. The problem was in the file "/system/bin/debuggerd", which was changed by SuperSu and may be by Stickmount. Update reported Error 7 while checking system.
So i replaced file "debuggerd" using root explorer with the unchanged version from factory image of JWR66Y and then uninstalled SuperSu (because it continued to change this file after reboot).
After that OTA update was applied successfully.
Click to expand...
Click to collapse
Thank you for this. it FINALLY worked for me.
Sideload r66v
Followed proc
http://forum.xda-developers.com/showthread.php?t=2379616
Hi
i got same error updating to OTA 4.4.2
problem is that i can not access to superSU
ask me binary update
i pushed update package and installed by install zip from sdcard
and installation successed but still can not access asking me binary
any tip ?
what happen if i uninstall superSU ? only thing i wouldn't like to lose whatsapp access
THNKS

Struggling to Update - Help Needed

So my son's 2012 Nexus 7 (32 GB Wi-Fi) is struggling to update. I was checking to see if he got the 5.0 update and noticed he's still on 4.4.2. When I tried to update to 4.4.3 it won't reboot and install the update.
I then tried to sideload the update and it failed due to some certificate issue. Maybe because it's unlocked? I then rooted it again (lost it after the last update apparently) and also installed TWRP. I was going to attempt to sideload from within TWRP but adb doesn't see the device in sideload mode for me for some reason.
Bottom line... Can I just flash the OTA zip file like any other file within TWRP? If not, does anyone have any over ideas of what I can do to update this this without wiping it clean?
I think you will have to flash the 5.0 and images using fastboot. Can you get into ap fastboot mode?
before that though, and to answer your questions:
- unlocked bootloader does not cause issues
- I've used twrp to flash all of the KitKat ota updates directly. simply put the update zip in the internal storage of the device (I always put it in sdcard0/) and flash. the only reason that would fail with KitKat is if you have xposed installed, which was fixed by flashing xposed Disabler zip first. I don't think having root mattered.
- for the lollipop update flashing from twrp didn't work for me. I had to first return 4.4.4 to stock system and recovery (by flashing the system.img and recovery.img files from stock 4.4.4) then adb sideload 5.0 ota update. In your case tho you'd have just updated to 4.4.4 so you can just go straight to sideloading.
All the ota update links are in the second sticky in the general section. make sure you follow the correct to:from build numbers.
I'd prefer this longer route of ota updates, but if nothing works then you can probably just flash system, recovery, and boot directly from the lollipop firmware, and leave userdata untouched. I'd also Not flash the bootloader, as it's reported to have issues.

OTA Update fails

Hello,
i have rooted my phone, installed TWRP and kept the Stock ROM 6.0.0 (didn't change anything at all)
In the past few weeks my phone annoyed me with the OTA Update so i wanted to install it. Sadly, it said somethinf about failed because of "package expects build fingerprint".
Can i somehow flash the OTA update with TWRP?
I uploaded the OTA file here: https://mega.nz/#!QlpQAJYQ!-TCIy_f-Lq8GdvRj2uxa02XJUgQqEVcXUhScl7sryJI
Just wanted to ask if anyone can help me? I've been waiting for a few days now. No solution yet :/
It annoys me a lot.
When I got this error on my OnePlus, the solution was to flash the stock recovery.
Then I was able to install the OTA.
After the update I flashed TWRP again.
savahu said:
When I got this error on my OnePlus, the solution was to flash the stock recovery.
Then I was able to install the OTA.
After the update I flashed TWRP again.
Click to expand...
Click to collapse
I tried that already. It sowhs a red android icon and update failed :/

[XT1625] OTA Update from 48 to 64 brings back the ads!

Hello! I have a problem with my device.
Right now, I have ATHENE_MPJ24.139-48 unlocked bootloader no ads, no TWRP, no root.
Originally, it had 7.0 with ads. I was able to unlock the bootloader and downgrade to ATHENE_MPJ24.139-48 without ads perfectly. I wanted to get rid of the notification of the upgrade, so I tried to do an OTA upgrade but the ads came back! So, I reverted to 48 again. I wanted to upgrade it now through the downloaded firmware, but first I wanted to install TWRP to be able to modify more things. I tried to install the latest TWRP for XT1625 and it said "OK" in fastboot. But when I try to open recovery mode, nothing shows. Strange. I upload the images of the errors with TWRP. So, is there a way to install other ROMs without this?
EDIT: The folder name is because I placed the TWRP.img inside the firmware folder because I already had adb and fastboot in there. So it was faster that way.

Categories

Resources