Root 4.4.3 Ota failing

Modman · Jun 17, 2014

I flashed stock recovery but didn't unroot.
The ota failed with the dead android.
When I booted back up I was unrooted.
I rerooted with wugs and went back to check the cache folder with
Scary Aliens ota verifier, but there was no ota.zip file in the cache folder to verify.

Did it never download the ota even though it said it did?

Or how did it disappear?

scary alien · Jun 17, 2014

Modman said:
I flashed stock recovery but didn't unroot.
The ota failed with the dead android.
When I booted back up I was unrooted.
I rerooted with wugs and went back to check the cache folder with
Scary Aliens ota verifier, but there was no ota.zip file in the cache folder to verify.

Did it never download the ota even though it said it did?

Or how did it disappear?

Hey Modman :wavey:.

I believe the .zip file gets automatically removed after both/either a successful or failed OTA installation.

I typically save-off the .zip file for safe-keeping and testing with my OTA Verifier app, but didn't notice a new one on my N7 this past week/weekend.

Is the 4.4.3 for the 1st gen N7 rolling-out? (I've not heard or checked)...I'll check mine here in a few and see.

I'm hitting the hay for the evening, but if you need any help or have questions, let me know.

(my Android Root Toolkit app should have stock and several custom recoveries for the 2012 N7 available if one needs them, too).

funkylogik · Jun 18, 2014

Hey Scary dude. I hadn't heard of your app.
AFAIK official 443 hasn't dropped for this tab yet but I'm a. 3rd party firmware type guy (which i recommend highly) 😸

scary alien · Jun 18, 2014

funkylogik said:
Hey Scary dude. I hadn't heard of your app.
AFAIK official 443 hasn't dropped for this tab yet but I'm a. 3rd party firmware type guy (which i recommend highly) 😸

Hey Funky! :wavey:

Actually, I checked right afterwards and my first gen / 2012 N7 did have a 4.4.3 OTA update waiting to install!

So, I first saved 4.3+ root with my Android Root Toolkit app, then I allowed the OTA to be downloaded (but didn't install). I used Root Explorer to copy the ce921efc1fa9197e9b336ce3f89cbfa2275ea4bb.signed-nakasi-KTU84L-from-KOT49H.ce921efc.zip file to my "SD card" for safe keeping and later analysis if I needed.

Then I ran OTA Verifier against it and it came up clean except for a warning about there not being enough space to do the OTA installation:

Failed expression at line #1098:

apply_patch_space(35440244) || abort("Not enough free space on /system to apply patches.");

You should note that my app actually checks /cache to see if it has enough space and not the /system partition, so I'm not actually sure what was going on there (I'll have to do a little cross-checking and testing re. that particular test).

I went-ahead and did the OTA installation since I knew I had at least 425MB free in /cache and 4.4.3 updated just fine.

Oh, and root was indeed retained

(if you use the 4.3+ save root feature (1) in my Android Root Toolkit app, remember that it only "lasts" one reboot cycle, so do the save just before you do the OTA installation).

Cheers!

(1) All credit to Pau Oliva for this method

Modman · Jun 18, 2014

Android rootkit app?
Is this available in play store?
Does this work if super su is installed?
Wish I would have thought to copy and verify file before installing.

scary alien · Jun 18, 2014

Modman said:
Android rootkit app?

Android Root Toolkit

I think its in my signature in an earlier post, too, along with my other apps (including the OTA Verifier that we've already discussed).

Is this available in play store?

Yep! See above

.

Does this work if super su is installed?

Android Root Toolkit functions all require that you be rooted.

Wish I would have thought to copy and verify file before installing.

I could pretty easily make a shell of the OTA's .zip file when I get home tonight that you could use to verify (i.e., I'd strip-out all of the files except for the updater-script file that my app uses to verify things). Then, you could still do the verification, etc.

OTA Verifier does require root, but if you are rooted, that enables it to see and check the root-protected files that the updater-script file might reference.

Lemme know if you're interested in a "validate only" version of the 4.4.3 OTA .zip file.

John Bean · Jun 18, 2014

Many thanks Scary, I didn't know about your toolkit either but now that I do it just saved me messing around with a PC to get root back on my N7.

I got the same (incorrect) error as you did from the OTA Verifier but I ignored it with similar success

scary alien · Jun 18, 2014

John Bean said:
Many thanks Scary, I didn't know about your toolkit either but now that I do it just saved me messing around with a PC to get root back on my N7.

I got the same (incorrect) error as you did from the OTA Verifier but I ignored it with similar success

You're most welcome, John! Glad it was useful :thumbup:

.

I'll try to figure-out what the deal is with the apply_patch_space logic (I've looked at the code that Google/Android uses and it checks /cache like I coded my app to do--but maybe I left some debugging stuff in there on accident :dontknow:

).

Cheers!

Modman · Jun 18, 2014

yes would be useful. Also if you have the official ota will it flash through twrp?

will you or someone else eventually post it somewhere?

like can you just clear cache dalvik cache with twrp and flash ota?

Would save time waiting for it to showup and download the conventional way.

Would that method leave all the data and installed apps intact?

scary alien · Jun 18, 2014

Modman said:
yes would be useful.

Here's an "empty" version of the OTA .zip file that you can use with OTA Verifier: View attachment 443-n7-naksai-OTA-empty.zip

I basically removed all of the files except for the files in the META-INF\com\google\android structure (i.e., the signing files and the updater-script and update-binary, of which the updater-script file is the only useful file to OTA Verifier. Note: this file is NOT useful for flashing since there are no resource / payload files present for it to use for it's commands.

I'm guessing you do have some files that don't match what the OTA expects which accounts for your initial installation failure...

Also if you have the official ota will it flash through twrp?

will you or someone else eventually post it somewhere?

like can you just clear cache dalvik cache with twrp and flash ota?

Would save time waiting for it to showup and download the conventional way.

Well, I've got the 2012 (first gen) grouper/nakasi wi-fi version of the OTA...I was about to post it on my dropbox for you, but I see that it's also available here:

http://android.clients.google.com/packages/ota/google_nakasi/ce921efc1fa9197e9b336ce3f89cbfa2275ea4bb.signed-nakasi-KTU84L-from-KOT49H.ce921efc.zip

courtesy of this G+ post: https://plus.google.com/+DroidLife/posts/bjbNvcra5XJ

In reviewing the updater-script file, I don't see any checks that tests the currently installed recovery, so my thought is that it should flash from a custom recovery okay, but I haven't tried so I can't say 100% for sure (if you're brave enough, you could always just make a Nandroid backup, squirrel it off of your device to a safe place, and try it--knowing you'll be able to restore the Nandroid and/or flash the factory image).

Or, if you have re-rooted, and have verified that you've resolved any issues pointed-out by OTA Verifier, you could re-flash the stock N7 recovery using either manually or using my Android Root Toolkit app. Then you should be able to simply copy the above full OTA file (ce921efc1fa9197e9b336ce3f89cbfa2275ea4bb.signed-nakasi-KTU84L-from-KOT49H.ce921efc.zip) to your /cache folder and reboot--that should simulate receiving the OTA.

Would save time waiting for it to showup and download the conventional way.

Would that method leave all the data and installed apps intact?

Yes.

scary alien · Jun 18, 2014

John Bean said:
I got the same (incorrect) error as you did from the OTA Verifier but I ignored it with similar success

Just a quick follow-up here: I was indeed testing /system in my OTA Verifier app for the logic in the apply_patch_space processing when I should have been testing the free space in /cache.

I'm pretty sure I changed this in one of the last two minor releases because of seeing the (I believe misleading) abort verbiage in the apply_patch_space line in one of my N5 OTA's that are similar to what I also found in the recent N7 OTA:

apply_patch_space(35440244) || abort("Not enough free space on /system to apply patches.");

where the abort command misleadingly references "/system" instead of the proper /cache partition.

I've changed and re-published my app a little bit ago...it'll show up in the Play Store in a few hours.

Cheers!

Modman · Jun 18, 2014

System/bin/debuggerd is screwed up again.
Do you have one laying around I can download?

Thanks again

scary alien · Jun 18, 2014

Modman said:
System/bin/debuggerd is screwed up again.
Do you have one laying around I can download?

Thanks again

LOL, that does sound familiar...let me see if I can pull it out of my N7...brb.

scary alien · Jun 18, 2014

Modman said:
System/bin/debuggerd is screwed up again.
Do you have one laying around I can download?

Thanks again

Here's the 4.4.3 one: View attachment debuggerd.zip

(I had to pack it in a .zip file so that I could attach it here)

It's SHA1 sum matches one of the values that the 4.4.3 OTA is looking for (OTA's usually look / allow for the current and prior version of files), so it should pass the verification.

SHA1 sum:

7114cdf5aa0a1cfd416d5b2d741bea9ad59a2718 *debuggerd

Cheers!

Modman · Jun 18, 2014

Thanks again but with stock recovery seems I have to let it download the ota by itself again. Simply putting it in the cache folder and rebooting does not start the install of the ota.
I remember I had to wait for days last time and it eventually came down and installed

scary alien · Jun 18, 2014

Bummer

You could try the Google Services Framework trick: https://plus.google.com/app/basic/stream/z13cjtkwmqutcdnxq04cfnczcwicfrgxmok0k to try to force the download (using my phone so I cant properly research for ya...)

Modman · Jun 19, 2014

That sometimes works but also sometimes breaks Google play with an RPC error.
Even though it eventually usually goes away. I might just wait.

Modman · Jun 20, 2014

I just waited ota came back today.

Now it is successful

I rerooted with wugs because your root saver didnt work.

Its debuggerd every time.

Are we getting any more otas or is that it for this tablet?

Was surprised we got it.

scary alien · Jun 20, 2014

Modman said:
I just waited ota came back today.

Now it is successful

I rerooted with wugs because your root saver didnt work.

Its debuggerd every time.

Are we getting any more otas or is that it for this tablet?

Was surprised we got it.

Glad to hear you got the OTA installed! :thumbup:

Hmm, the 4.3+ save root worked for me...:dontknow: (the 4.3+ save root only works for one reboot cycle--i.e., if you reboot, you'd have to re-run the save before installing the OTA).

Google did release factory images for 4.4.4 just yesterday (or late the day before), so I'd half-expect another OTA in the not too distant future...

I've had the issue with the debuggerd file myself, too, but not sure what the genesis of that and it's getting out-of-sync with the other stock files... :thinking:

Modman · Jun 21, 2014

Really. What is the life cycle of a Nexus Device?

This a 2012 tablet and we are still receiving updates.

Do you think we will get android 5?

I thought maybe this tablet would be abandoned by then.

Another funny thing is my wife has the 2013 and the screen stopped
Responding and we had to send it in for repairs after a year.

This tablet doesn't have as good resolution is a year older
Its been rooted rerooted and reflashed from scratch once. never had
An extended warranty.

The worse thing that ever happened to to this tablet was a near soft brick when I took the ota from jelly bean to KitKat.

During that time the lag was horrible.
After doing a wipe and fresh install it has been working
Good ever since.

This has been my first successful ota since wiping and flashing the fresh KitKat build.

Hook · Jun 21, 2014

I think any Nexus device gets updates until it is deemed to close to or below minimum requirements for the new version. It would not surprise me if the Nexus 7 (2012) was dropped from 5 (or 4.5-- whichever is announced next week) but it also wouldn't surprise me if it wasn't. I don't think the limit is time bound.

jhawkkw · Jun 21, 2014

Google promises 18 months of support, but after that is up to how long the hardware supports the OS and how long the hardware manufacturer supports the hardware in terms of keeping up to date binaries.

Bob Denny · Jun 24, 2014

scary alien said:
Here's the 4.4.3 one: View attachment 72302

(I had to pack it in a .zip file so that I could attach it here)

It's SHA1 sum matches one of the values that the 4.4.3 OTA is looking for (OTA's usually look / allow for the current and prior version of files), so it should pass the verification.

Cheers!

StickMount changed /system/bin/debuggerd and for some reason the /system/bin/debuggerd.backup that I found is the same damn modified version. So the OTA to go to KTU84L (4.4.3) fails for unexpected contents (SHA mismatch) on /system/bin/debuggerd.

Can someone please post the standard /system/bin/debuggerd from a 4.4.2 (KOT49H) system so I can get past this pain?

[edit]Maybe this is it. He said it was the one that the 4.4.3 OTA is looking for. I apologize. I can't delete this post.

scary alien · Jun 24, 2014

Bob Denny said:
StickMount changed /system/bin/debuggerd and for some reason the /system/bin/debuggerd.backup that I found is the same damn modified version. So the OTA to go to KTU84L (4.4.3) fails for unexpected contents (SHA mismatch) on /system/bin/debuggerd.

Can someone please post the standard /system/bin/debuggerd from a 4.4.2 (KOT49H) system so I can get past this pain?

[edit]Maybe this is it. He said it was the one that the 4.4.3 OTA is looking for. I apologize. I can't delete this post.

Ah, that rings bell, Bob! :thumbup:

I'll see if I can get you the 4.4.2 debuggerd file...hang on for a bit (I gotta dig out my Linux laptop so I can extract the file).

Edit: I see you made an edit...do you still need that one or are you saying that the one I posted before will work?

Bob Denny · Jun 24, 2014

Yee haw!! The one you posted is actually the 4.4.2 (KOT49H) one, just what I needed to go to 4.4.3 (KTU84L) It's running right now.

OTHERS: The one that scary alien posted attached to this post in the current thread is the one you need for the 4.4.2 to 4.4.3 OTA. Put it into /system/bin, replacing the one there. Then set permissions to rwxr-xr-x and owner to root/cache. Then do the OTA.

Root 4.4.3 Ota failing

Android Enthusiast

not really so scary

share the love peeps ;)

not really so scary

Android Enthusiast

not really so scary

Happy Wanderer

not really so scary

Android Enthusiast

not really so scary

not really so scary

Android Enthusiast

not really so scary

not really so scary

Android Enthusiast

not really so scary

Android Enthusiast

Android Enthusiast

not really so scary

Android Enthusiast

Ever since DU... ;-)

Chinchillin'

Well-Known Member

not really so scary

Well-Known Member

BEST TECH IN 2023

Smartphones

Best Android Phones

Upcoming

Best iPhones

Upcoming

Tablets

Best Tablets

Upcoming

Laptops

Best Laptops

Upcoming

Televisions

Best TVs

Upcoming

Game Consoles

Best Game Consoles

Upcoming

Wearables

Best Wearables

Upcoming

Smart Home

Smart Home Tech

Upcoming

Similar threads