Database Users

Stock Netflix.apk needed

I'm trying to upgrade my rooted TF101 to 9.2.1.11 and every zipI use complains on an assert failure for /system/app/Netflix.apk. Oddly, I can't get Ti backup to restore it, so I tried downloading it and putting it in that directory. This doesn't work. Does anyone have the stock Netflix.apk they can post so I can move past this? thx!!

Here ya go!
Title says it all.

Thanks! But no cigar!
I tried that, but it gives me the following error when I attempt to apply the zip from the sd card:
ClockworkMod Recovery v3.2.0.1 roach2010-tf101-r1
-- Installing: /sdcard/ics-us-8.6.5.21-to-9.2.1.11-CWM-rooted.zip
Finding update package...
Opening update package...
Installing update...
Verifying current system...
assert failed: apply_patch_check("/system/app/Netflix.apk", "459b736ea95188dd3500005f621b4fa22291c40c", "58c70e894dfc98166d16c64cb9555a7e83ceb7e4")
E:Error in /sdcard/ics-us-8.6.5.21-to-9.2.1.11-CWM-rooted.zip
(Status 7)
Installation aborted.
Click to expand...
Click to collapse
Any suggestions out there in the development community? I didn't think that uninstalling Netflix would cause such a hassle later on. Is there a different version of the .apk I can try? Or a different way of installing it (I just copied it over after remounting /system/app as rw).
Alternatively, can I unroot, then download the update, then re-root? Anybody have any practice with that, or will the Netflix.apk package.
Thank you! Have a nice day (or evening).

crinis said:
I tried that, but it gives me the following error when I attempt to apply the zip from the sd card:
Any suggestions out there in the development community? I didn't think that uninstalling Netflix would cause such a hassle later on. Is there a different version of the .apk I can try? Or a different way of installing it (I just copied it over after remounting /system/app as rw).
Alternatively, can I unroot, then download the update, then re-root? Anybody have any practice with that, or will the Netflix.apk package.
Thank you! Have a nice day (or evening).
Click to expand...
Click to collapse
That wasn't a zip file, it was an apk. And you don't flash those in recovery. Just put it in /data/app directory, then restart the tablet. Or you can try to execute it, and it will automatically install to the appropriate folder.

I solved it!
Yes, I just copied it over using scp (after remounting /system as rw). I'm no noob!
Here's what I did to get it to work.
I unzipped the rooted zip file, edited the updater-script to remove references to Netflix.apk (three of them), then rezipped it up, copied it to the sdcard , rebooted to recovery, then flashed it. Worked! Here's the exact steps took:
On my linux latop:
mkdir /tmp/ics-us-8.6.5.21-to-9.2.1.11-CWM-rooted
cd /tmp/ics-us-8.6.5.21-to-9.2.1.11-CWM-rooted
unzip ~/Download//tmp/ics-us-8.6.5.21-to-9.2.1.11-CWM-rooted.zip
vi ./META-INF/com/google/android/updater-script
# /Netflix\.apk finds the lines, I deleted two, and modified the third to remove the reference.
zip -r /tmp/ics-us-8.6.5.21-to-9.2.1.11-CWM-rooted.zip *
scp /tmp/ics-us-8.6.5.21-to-9.2.1.11-CWM-rooted [email protected]:/Removable/MicroSD
Click to expand...
Click to collapse
From there it's all Clockwork.
Thanks so much for the help of this forum. I love xda developers!

How to update to JB using DLPKGFILE and KEEP ROOT! Works!

Right, so, through a bit of trial and error using guidance from the forums, this is how I updated to JB and kept root for WW after the update originally failed.
download BOTH files from here (massive thanks to ch3mn3y):
http://www25.zippyshare.com/v/91334594/file.html
http://www1.zippyshare.com/v/96461494/file.html
then extract the .zip file.
download the command file from here (massive thanks to krabappel2548):
http://www.mediafire.com/?yq1bt16mnm7tc8d
extract it.
place the dlpkgfile and command file, both unzipped onto your tab. Use a root explorer to paste the command file into /cache/recovery and the dlpkgfile (the actual file, not the folder) to /cache.
go to Voodoo OTA Rootkeeper and temp unroot.
turn off the tab.
boot into recovery with Vol - and power, then when it says to press volume up to boot into RCK, do it.
You'll see the android with the blue wires and it will go through the install process if you have done it right. let it do its thing.
obviously, when it has settled, restore root with Voodoo.
If you get the android with red exclamation mark, i reccomend downloading the ICS zip of your current firmware and SKU and sticking it on a micro SD card, and letting it restore any programmes you've deleted.

rickykemp said:
Right, so, through a bit of trial and error using guidance from the forums, this is how I updated to JB and kept root for WW after the update originally failed.
download BOTH files from here (massive thanks to ch3mn3y):
http://www25.zippyshare.com/v/91334594/file.html
http://www1.zippyshare.com/v/96461494/file.html
then extract the .zip file.
download the command file from here (massive thanks to krabappel2548):
http://www.mediafire.com/?yq1bt16mnm7tc8d
extract it.
place the dlpkgfile and command file, both unzipped onto your tab. Use a root explorer to paste the command file into /cache/recovery and the dlpkgfile (the actual file, not the folder) to /cache.
go to Voodoo OTA Rootkeeper and temp unroot.
turn off the tab.
boot into recovery with Vol - and power, then when it says to press volume up to boot into RCK, do it.
You'll see the android with the blue wires and it will go through the install process if you have done it right. let it do its thing.
obviously, when it has settled, restore root with Voodoo.
If you get the android with red exclamation mark, i reccomend downloading the ICS zip of your current firmware and SKU and sticking it on a micro SD card, and letting it restore any programmes you've deleted.
Click to expand...
Click to collapse
Will your last line lose root on us, or will voodoo root keeper save it via that or does it wipe/reset the entire system?

Ashcunak said:
Will your last line lose root on us, or will voodoo root keeper save it via that or does it wipe/reset the entire system?
Click to expand...
Click to collapse
When i ran ran the zip of .30 i did lose root, but it was easily restored using 1 click transformer root.

I tried it twice but it always failed at about 1/3 of the process... Hopefully I can reboot w/ any damage...
WHY!?? :'(
Btw here's the part of the log where it shows the failure in installation:
I:Enable RSA key verification.
Installing update...
Finding update package...
I:Update location: /cache/dlpkgfile
Opening update package...
I:1 key(s) loaded from /res/keys
Verifying update package...
I:comment is 1682 bytes; signature 1664 bytes from end
I:whole-file signature verified against key 0
I:verify_file returned 0
Installing update...
Check : blob size = 13104069
Verifying current system...
file "/system/lib/libGLESv1_CM.so" 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: assert failed: apply_patch_check("/system/lib/libGLESv1_CM.so", "ed4c7834196831836c73d0374529a0278c2fa91c", "a52756f5a63c9827632587d025ee28f67739bd97")
assert failed: apply_patch_check("/system/lib/libGLESv1_CM.so", "ed4c7834196831836c73d0374529a0278c2fa91c", "a52756f5a63c9827632587d025ee28f67739bd97")
E:Error in /cache/dlpkgfile
(Status 7)
Installation aborted.
I:result_code: 410
Check and format /storage to vfat if needed...
Mount /btmac successfully
Done
Btw the command file is just a file with content --update_package=/cache/dlpkgfile in it.
You can create it with notepad, save as .txt, and remove the .txt

rickykemp said:
When i ran ran the zip of .30 i did lose root, but it was easily restored using 1 click transformer root.
Click to expand...
Click to collapse
OH, wow, im so outa date thanks, i rooted on the first revision that came out and havent really watched whats out there for root options. i see this now thanks so much i was worried id have to all sorts of downgrading. link for anyone else whos "outa it" like me http://forum.xda-developers.com/showthread.php?p=26918790

WIIstpM said:
file "/system/app/Music2.apk" 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: assert failed: apply_patch_check("/system/app/Music2.apk", "c9bc168a88b5106e0e04f8e70023a4c33009021b", "cbb199983ab1cb9beee6b20ec4db659ccd49d757")
assert failed: apply_patch_check("/system/app/Music2.apk", "c9bc168a88b5106e0e04f8e70023a4c33009021b", "cbb199983ab1cb9beee6b20ec4db659ccd49d757")
Click to expand...
Click to collapse
Maybe u delete or freeze Music2.apk? First time when i forget to unfreeze /system apps my update failed too (but i dont remember when).

ch3mn3y said:
Maybe u delete or freeze Music2.apk? First time when i forget to unfreeze /system apps my update failed too (but i dont remember when).
Click to expand...
Click to collapse
I think I found the problem: I remember I pushed jelly bean's music2.apk in system/app! Restored the original music app.
Gonna try update again!
Now it the turn of libGLESv1_CM.so ...

Going to give it a try.
Just to make sure, is this for WW version, right?

ch3mn3y said:
Maybe u delete or freeze Music2.apk? First time when i forget to unfreeze /system apps my update failed too (but i dont remember when).
Click to expand...
Click to collapse
MM the Music app problem is resolved.. but now the same thing happens but with "/system/lib/libGLESv1_CM.so"
...

Tequila.CZ said:
Going to give it a try.
Just to make sure, is this for WW version, right?
Click to expand...
Click to collapse
Yep.

Thanks.
Looking good., but got this error:
file "/system/app/EmailWidget.apk" 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: assert failed: apply_patch_check("/system/app/EmailWidget.apk", "5655101db862ccc0b2e60bd8ee276192f80e0ac7", "25adaa94e23e2aa87a7dd7f01956ccbabbb960fc")
assert failed: apply_patch_check("/system/app/EmailWidget.apk", "5655101db862ccc0b2e60bd8ee276192f80e0ac7", "25adaa94e23e2aa87a7dd7f01956ccbabbb960fc")
E:Error in /cache/dlpkgfile
Already got this before my update notification stopped working.
I deleted Email app, returned it back to system but seems I dont have the right version. (found in someones dropbox posted here)
Also reflashed Ww. 30 hoping this would overwrite the widget with correct version. Obviously it did not...
Would be glad for any help.

As it is MY dlpkgfile it can need MY files. I could upload /system, but first its strange to copy/paste whole android and second it is 624mb and third it will work only for rooted and at least fourth i updated my pad.
If it helps my pad was reflashed to .30 using wolfs method cos i had screen issue.
Sent using tf300t - stock JellyBean (rooted)

ch3mn3y said:
As it is MY dlpkgfile it can need MY files. I could upload /system, but first its strange to copy/paste whole android and second it is 624mb and third it will work only for rooted and at least fourth i updated my pad.
If it helps my pad was reflashed to .30 using wolfs method cos i had screen issue.
Sent using tf300t - stock JellyBean (rooted)
Click to expand...
Click to collapse
Could you please try to upload just the EmailWidget?
When I tried using OTA I got an error on Email.apk first. Then I downloaded it from dropbox and it passed. But EmailWidget did unfortunately not.
Also trying to find a tool that could extract the .30blob file. I guess the apps should be there. Found something but probably Linux only so no go for me.

You guys made my day! I had the red triangle and couldn`t get the update anymore. Tried everything, nothing worked.
Now I just followed your guide, dl. your files and all went fine.
So sad I was ony able to hit the Tanks-button once. Thank you thousand times!
Sent from my ASUS Transformer Pad TF300T using Tapatalk 2

Here is emailwidget .apk and .odex but from jb not ics cos i didnt made a backup. But i think that it wasnt changed.
http://db.tt/cYSWYcXo
Sent using tf300t - stock JellyBean (rooted)

ch3mn3y said:
Here is emailwidget .apk and .odex but from jb not ics cos i didnt made a backup. But i think that it wasnt changed.
http://db.tt/cYSWYcXo
Sent using tf300t - stock JellyBean (rooted)
Click to expand...
Click to collapse
Oh man. I love you. Here I come on JB!
The EmailWidget was the missing piece.
Big thanks to rickykem, ch3mn3y and overyone who helped to create this workaround!

y17dt said:
You guys made my day! I had the red triangle and couldn`t get the update anymore. Tried everything, nothing worked.
Now I just followed your guide, dl. your files and all went fine.
So sad I was ony able to hit the Tanks-button once. Thank you thousand times!
Sent from my ASUS Transformer Pad TF300T using Tapatalk 2
Click to expand...
Click to collapse
+1:good:

Can someone post the original /system/lib/libGLESv1_CM.so pleeease...
Sent from my LG-P970 using xda premium

WIIstpM said:
Can someone post the original /system/lib/libGLESv1_CM.so pleeease...
Sent from my LG-P970 using xda premium
Click to expand...
Click to collapse
I only have it from JB. Unfortunately it seems the file was updated together with the system so it will most probably be useless.
Don't have a libs backup from WW.30

WIIstpM said:
Can someone post the original /system/lib/libGLESv1_CM.so pleeease...
Sent from my LG-P970 using xda premium
Click to expand...
Click to collapse
Here you go, from ICS:
http://db.tt/z5B5Q3jL
Trimis de pe ASUS Transformer Pad TF300T

Req: file - System/bin/debuggerd

Tried updating from 4.2.1 to 4.2.2.
But assert check failed returning above file in results. Somehow it's been modified. No idea when and how.
Anyone running 4.2.1, could you please provide me this file.
Thanks in anticipation.
Sent from my Nexus 7 using Tapatalk HD

gurudev32 said:
Tried updating from 4.2.1 to 4.2.2.
But assert check failed returning above file in results. Somehow it's been modified. No idea when and how.
Anyone running 4.2.1, could you please provide me this file.
Thanks in anticipation.
Sent from my Nexus 7 using Tapatalk HD
Click to expand...
Click to collapse
I have the exact same issue!

Here is the list of only apps with root access in my tab.
Carbon - App backup and restore, Solid explore, Stick mount, SuperSU, System tuner pro and Terminal Emulator.
Thought to seek out the culprit!
Sent from my Nexus 7 using Tapatalk HD

https://dl.dropbox.com/u/17326185/debuggerd
MD5: B59443115C4181F49A57C1290EE3225B
https://dl.dropbox.com/u/17326185/build.prop
MD5: D9D1855E0C90049DC410A4406B802259
Pulled this from the 4.2.1 factory image. I seem to have got past the debuggerd error message now (though I need to revert my build.prop entirely, apparently).
Included build.prop (not yet tested) from 4.2.1 image too.
Working for me and now running 4.2.2.
At your own risk, yadda yadda, not responsible for explosions or anything less terrible, blah blah.
FWIW, I had been using Stickmount and superSU.

PhoenixTank said:
Pulled this from the 4.2.1 factory image. I seem to have got past the debuggerd error message now (though I need to revert my build.prop entirely, apparently).
Included build.prop (not yet tested) from 4.2.1 image too.
Working for me and now running 4.2.2.
At your own risk, yadda yadda, not responsible for explosions or anything less terrible, blah blah.
FWIW, I had been using Stickmount and superSU.
Click to expand...
Click to collapse
Thanks Now 'm on 4.2.2

In the future, If you want to pull arbitrary file(s) from Google N7 factory images, a useful skill set is to figure out how to use "sim2img" utility and loopback mounts (Windows need not apply).
Those system.img files shipped by Google are "sparse ext4 images" - they can not be directly mounted as a loopback, but that's where the "sim2img" utility comes in
The sequence goes like this:
- use sim2img to convert Google image file to regular ext4 image file
- loopback mount reg. image file
- grab whatever files you want (and check user/GRP ownership & modes)
It really is just that easy.
The "sim2img" utility is part of the android ext4_utils toolset. See this XDA thread from the Galaxy S forums for more details. (Yes the N7 system.img files from Google are also in this format.)
cheers

PhoenixTank said:
https://dl.dropbox.com/u/17326185/debuggerd
MD5: B59443115C4181F49A57C1290EE3225B
https://dl.dropbox.com/u/17326185/build.prop
MD5: D9D1855E0C90049DC410A4406B802259
Pulled this from the 4.2.1 factory image. I seem to have got past the debuggerd error message now (though I need to revert my build.prop entirely, apparently).
Included build.prop (not yet tested) from 4.2.1 image too.
Working for me and now running 4.2.2.
At your own risk, yadda yadda, not responsible for explosions or anything less terrible, blah blah.
FWIW, I had been using Stickmount and superSU.
Click to expand...
Click to collapse
How to make it? and i will lose all data? thanks

TheRejzo said:
How to make it? and i will lose all data? thanks
Click to expand...
Click to collapse
Big thanks.
Replacing the debuggerd file allowed twrp to load the 4.2.2 update.
Also interesting, other than titanium, the only other root app on this device is Stickmount.

Did not work for me ...
I have a N7 3G and the same message when trying to update. Replaced mine with the one from the download, no change, same error.

diba320 said:
Did not work for me ...
I have a N7 3G and the same message when trying to update. Replaced mine with the one from the download, no change, same error.
Click to expand...
Click to collapse
First of all, thanks a lot to PhoenixTank who provides me the solution. :good:
In fact to make it work, I had to change the permissions allowed on that file named "debuggerd", I checked what permissions were allowed on the original file and do the same on the copied one. I did it with ES explorer in root mod.

TheRejzo said:
How to make it? and i will lose all data? thanks
Click to expand...
Click to collapse
You'd need to backup and rename the existing debuggerd then move/copy the 4.2.1 debuggerd file to /system/bin/
Then match the permissions of the old debuggerd (I think it was 644, but I wouldn't swear by it).
The OTA zip should actually go through after that, or at least tell you about a new file you need to fix. You shouldn't lose any data, but you should probably clear cache and dalvik cache.
I did most of this via adb shell, but there are root file managers that can help. If you aren't confident about doing this and how it works, my posting was not really for you. Strongly suggest reading up until you feel confident before you start changing things around in the system partition.
diba320 said:
Did not work for me ...
I have a N7 3G and the same message when trying to update. Replaced mine with the one from the download, no change, same error.
Click to expand...
Click to collapse
Unfortunately the 3G version is different to the Wifi Nexus 7, and as you've found, the files will not work.
Since I posted, Google pulled the 4.2.1 factory images from the download site - I'm not really in a good position to help you here.
The 4.2.2 factory image might be of more use if you can't source the 3G specific files. i.e. flash the new factory image.

Had this same problem. Will try solution tomorrow morning. Probably will download the links rather than trying to extract them myself (though I may leave that for a later exercise).
Would like to note that I also use StickMount as well as SixAxis Controller, Wifi Key Recovery, AppSync and LMT Launch err.
Seems like stick mount is the common one though.
Sent from my Nexus 7 using xda app-developers app

PhoenixTank said:
https://dl.dropbox.com/u/17326185/debuggerd
MD5: B59443115C4181F49A57C1290EE3225B
https://dl.dropbox.com/u/17326185/build.prop
MD5: D9D1855E0C90049DC410A4406B802259
Pulled this from the 4.2.1 factory image.
Click to expand...
Click to collapse
bftb0 said:
In the future, If you want to pull arbitrary file(s) from Google N7 factory images, a useful skill set is to figure out how to use "sim2img" utility and loopback mounts (Windows need not apply).
Those system.img files shipped by Google are "sparse ext4 images" - they can not be directly mounted as a loopback, but that's where the "sim2img" utility comes in
The sequence goes like this:
- use sim2img to convert Google image file to regular ext4 image file
- loopback mount reg. image file
- grab whatever files you want (and check user/GRP ownership & modes)
It really is just that easy.
The "sim2img" utility is part of the android ext4_utils toolset. See this XDA thread from the Galaxy S forums for more details. (Yes the N7 system.img files from Google are also in this format.)
cheers
Click to expand...
Click to collapse
Thanks guys
Those 2 files worked.
I got past "Verifying current system" and am now on 4.2.2.
I wanted to try to get the files myself as an exercise but Google pulled the 4.2.1 images from their website.
What is weird... is that I noticed a /system/bin/debuggerd.bak file that I didn't make myself, don't know what did (though StickMount seems to be the current suspect).
The weird thing is that debuggerd and debuggerd.bak were exactly the same.

FunkyELF said:
I wanted to try to get the files myself as an exercise but Google pulled the 4.2.1 images from their website.
Click to expand...
Click to collapse
oldblue910 (OP of the OTA thread) has got you covered. Select the link on the rhs of the page as appropriate for your device (nakasi/nakasig)
cheers

I want to do this, but I can't find the system/bin folder, what root explorer apps do you guys use?
EDIT: Used Total Commander, copied the permissions from old file to new and voilah! It worked.
No need to download build prop.
Now I am on 4.2.2
EDIT 2: Now WiFi only says SAVED and not CONNECTED.

Just want to say THANK YOU!! I've been researching this error since Friday and finally found the solution here! And yes, I too have Stickmount!

Rody2k6 said:
I want to do this, but I can't find the system/bin folder, what root explorer apps do you guys use?
EDIT: Used Total Commander, copied the permissions from old file to new and voilah! It worked.
No need to download build prop.
Now I am on 4.2.2
EDIT 2: Now WiFi only says SAVED and not CONNECTED.
Click to expand...
Click to collapse
Can only recommend that you clear cache and dalvik cache. I have not experienced Wifi issues since the update.
To anyone I've helped, you are very welcome and I appreciate those thanks clicks too.

bftb0 said:
In the future, If you want to pull arbitrary file(s) from Google N7 factory images, a useful skill set is to figure out how to use "sim2img" utility and loopback mounts (Windows need not apply).
Those system.img files shipped by Google are "sparse ext4 images" - they can not be directly mounted as a loopback, but that's where the "sim2img" utility comes in
The sequence goes like this:
- use sim2img to convert Google image file to regular ext4 image file
- loopback mount reg. image file
- grab whatever files you want (and check user/GRP ownership & modes)
It really is just that easy.
The "sim2img" utility is part of the android ext4_utils toolset. See this XDA thread from the Galaxy S forums for more details. (Yes the N7 system.img files from Google are also in this format.)
cheers
Click to expand...
Click to collapse
can i do the reverse ? i.e. ext4 partition back to flashable img ?
that way it would be easier to root as I just need to dump a copy of su into it then flash.
And for Windows, just get oracle virtualbox(or your favorite VM, even virtual PC should work) and boot a copy of debian

chimpanzeexda said:
can i do the reverse ? i.e. ext4 partition back to flashable img ?
that way it would be easier to root as I just need to dump a copy of su into it then flash.
And for Windows, just get oracle virtualbox(or your favorite VM, even virtual PC should work) and boot a copy of debian
Click to expand...
Click to collapse
Yes. I did exactly the same thing, but for 4.2.1. Guess I need to repeat it now for 4.2.2. Note in this case "flashable" means the fastboot way (as with the Factory ROM flashes), not via custom recovery.
Uhh let's see - the script tool used for re-packing is ./mkuserimg.sh - see the links I provided above

I need some help... I'm rather noobie. Had issue with upgrading to 4.2.2 so copied the debuggerd and build.prop files over to the system/bin directory. Still failed to upgrade. Tried it again today and now the N7 will not boot up. I can see it's on but it just stops at a blank screen. I have stock 4.2.1 w/root. Stock bootloader. I'm thinking its refusing to boot because I forgot to change the file permissions on the debuggerd file but not sure how to try and fix it. Please advise...
UPDATE: Managed to flash the system partition for 4.2.2 so hoping I'm good to go. Asked this question in another post but is it necessary to update any of the other partitions?

[Q] Android is upgrading every startup

Everytime I turned on my phone or if it rebooted, I always get:
Android is upgrading
-----------------------------
Starting Apps.
I am on stock ROM, TWRP recovery, Faux kernel. I think this happens after I wiped dalvik/cache in the recovery. Any idea how to stop it? It's nothing very major though as it only takes a few seconds.

are you using any sound/volume mods? or any other flashable mods? i think awesomebeats dies this, at least others have complained about it wiping the dalvik after every reboot.

cdon2109 said:
Everytime I turned on my phone or if it rebooted, I always get:
Android is upgrading
-----------------------------
Starting Apps.
I am on stock ROM, TWRP recovery, Faux kernel. I think this happens after I wiped dalvik/cache in the recovery. Any idea how to stop it? It's nothing very major though as it only takes a few seconds.
Click to expand...
Click to collapse
That's normal if you've wiped the Dalvik cache, and no you can't stop it.
Edit: so wait, this is happening even when you reboot normally after not wiping any caches or flashing a kernel?

CMNein said:
That's normal if you've wiped the Dalvik cache, and no you can't stop it.
Edit: so wait, this is happening even when you reboot normally after not wiping any caches or flashing a kernel?
Click to expand...
Click to collapse
yes.. and it updates apps after delvic wipe.. but in my case whenever i restart I see the "Android is upgrading" box for about 3-5 sec.. no update app progress bar.. and when I wipe delvic this upgrading apps takes like a min or so with my 150+ apps.. but this "Android is upgrading" dialogue box appears only for 3-5 sec..
I am using PA 3.99 with franco kernel.. once booted every thing inside is running smoothly and no fc's...

Same here. No odex files in app folder. No wipe, no cache clearing. Plain reboot. And Android is upgrading message on every boot. (Starting apps)
No optimizing apps message though.
Sent from my Nexus 4

Wouldn't it be related to "zipalign apk on each boot" parameter ? or an other init script put in place by a dirty flash (no /system or /data format) or a kernel... ?

Seems likely. Could you explain in detail kindly?
Sent from my Nexus 4

anandbibek said:
Seems likely. Could you explain in detail kindly?
Sent from my Nexus 4
Click to expand...
Click to collapse
Have a look in the files located in this folder for example (maybe there's another location for init scripts) :
- /system/etc/init.d/
- /system/addon.d/
and open each one, to see what are the tasks contained

benbugohit said:
Have a look in the files located in this folder for example (maybe there's another location for init scripts) :
- /system/etc/init.d/
- /system/addon.d/
and open each one, to see what are the tasks contained
Click to expand...
Click to collapse
Removed the scripts present in init.d folder and then booted with empty folder, but message still present.
Checked the addon.d folder, but those scripts are only for backing up gapps etc.
Not sure where else to try. Please advise.
Thanks.

anandbibek said:
Removed the scripts present in init.d folder and then booted with empty folder, but message still present.
Checked the addon.d folder, but those scripts are only for backing up gapps etc.
Not sure where else to try. Please advise.
Thanks.
Click to expand...
Click to collapse
Did you try to re-flash your (stock) ROM (and the kernel after 2 reboots) with wiping only /cache and dalvik-cache ? with latest 2.6.2.0 TWRP ?

happens to me too
Sent from my Nexus 4

I've seen people get this with stuff like V6 Supercharger by Zepplinrox and similar scripts.

Edit : @Dungeon47: thanks for this information that users can't provide...
HeyyMyNameIs said:
happens to me too
Sent from my Nexus 4
Click to expand...
Click to collapse
A pity that so much details are missing : what did you do before it happened ?
What's your set up ? rom, kernel ? after having update your rom ? kernel ? apps ? which versions ?
Did you try to revert to a clean install after having backup up your apps+datas ?

benbugohit said:
Edit : @Dungeon47: thanks for this information that users can't provide...
A pity that so much details are missing : what did you do before it happened ?
What's your set up ? rom, kernel ? after having update your rom ? kernel ? apps ? which versions ?
Did you try to revert to a clean install after having backup up your apps+datas ?
Click to expand...
Click to collapse
im sorry, just wanted the OP to know that he is not the only one with this "problem" by the way im rooted stock rom and kernel, some apps start up when i boot like nova launcher, lucky patcher sidebar and udn. But i am not looking for a fix for this as this does not take that long and i just said that to let the OP know that he is not alone with this "problem"
Sent from my Nexus 4

Ok guys,
Here's the solution. Don't flame me for talking about unholy stuffs. I'm posting this only because it is the cause of the problem.
If you are using LP or such tools to create .odex files of some app in /app folder. It won't cause any boot msg.
But after you dirty flash a ROM, that .odex files somehow gets backdated and causes the UPGRADING msg.
Fix is, delete the odex files, and re create them if needed. Once after every dirty flash.
Sent from my Nexus 4

I have found fix for this error, it is mainly due to odex files which are created by lucky patcher so deleting these files using lucky patcher itself will surely remove this error with 50 percent success rate. Here's the fix; open lucky patcher, there in lower left section you can see Toolbox, click that Toolbox then select 4th last option i.e Remove all odex files.Thats it android will reboot on itself and vola no android is upgrading. .
Check out attachment for help.
:good:Hits Thanks If I helped u:good:

Updating CM10.1 on i9505 international

I keep getting status 7 errors when I try to update my CM install on my i9505 international, (i'm using latest philz recovery). So far I have solved the problem by doing a full wipe and a ROM prep wipe. This is obviously not great because I have to set up the phone from scratch.
For various reasons I do not have access to a computer so cannot do the unzip / modify / rezip solutions referred to in many posts.
Is there another way i can update to the latest nightly builds? And what is causing this problem?
Thanks for help

as far as i know this is because the rom is build for us t-mobile edition.
you need to delete one line ... otherwise it won't work. so you need a computer for this.
also full wipe isn't enough. also delete preload and system.
hope this helps

birdr said:
I keep getting status 7 errors when I try to update my CM install on my i9505 international, (i'm using latest philz recovery). So far I have solved the problem by doing a full wipe and a ROM prep wipe. This is obviously not great because I have to set up the phone from scratch.
For various reasons I do not have access to a computer so cannot do the unzip / modify / rezip solutions referred to in many posts.
Is there another way i can update to the latest nightly builds? And what is causing this problem?
Thanks for help
Click to expand...
Click to collapse
You can do everything you need on your phone. I use Root Explorer to unzip, delete the format line and zip. Works fine if you do that and it's pretty easy to do.
chrisknife said:
as far as i know this is because the rom is build for us t-mobile edition.
you need to delete one line ... otherwise it won't work. so you need a computer for this.
also full wipe isn't enough. also delete preload and system.
hope this helps
Click to expand...
Click to collapse
That's not true and it's not why anyway. It's a problem with the recovery.

do you have any nfo ( workaround) how the update procedure can be done?

3bs11 said:
You can do everything you need on your phone. I use Root Explorer to unzip, delete the format line and zip. Works fine if you do that and it's pretty easy to do.
That's not true and it's not why anyway. It's a problem with the recovery.
Click to expand...
Click to collapse
ok sorry then...
i thought it's the same like on aokp nightlies.
for me it helped to delete preload and system...
had this error before too. after formating this it worked.

Thanks all. I got this working based on the advice given.
Precisely:
1. I extracted the nightly using ES file explorer.
2. I used a text editor to remove the line
format("ext4", "EMMC", "/dev/block/mmcblk0p16", "0", "/system");
from
/META-INF/com/google/android/updater-script
3. Then I re-zipped using ES file explorer.
4. Then i flashed as normal with philz recovery, wiped cache and rebooted.
Worked first time and everything upgraded as expected.
Thanks again for the help.