Database Users

[Q] Fail Updating to 4.2.2

Unlocked Bootloader.
CWM.
Root.
Fail in updating, with message something like assert fail apply_update_check status 7.
Revert to Stock Recovery and Unroot (bootloader is still unlock), update again, result in error with the android robot and red exclamation.
Happen to my Nexus 7 and Galaxy Nexus as well (same unlock bootloader cwm root, same revert method, same error).
Has anyone face this and any solution to make OTA works?

Get back to stock, then try again
Sent from my Nexus 4 using xda premium

Had the same problem. This will answer all your questions
http://forum.xda-developers.com/showthread.php?t=2145848

thanks for the link. it did not directly make my device can be updated, but incase others have this problem and looking for solution, here are the things I did and fix it:
flash boot.img and flash system.img
these 2 files are needed to be at STOCK, I extract from the factory image, and flash through fastboot.
flashing these 2 files WILL NOT CAUSE application to be formatted (like what I thought at the first time).
It will simply remove any tweak done to system such as ads blocking (adaway, etc), battery icon mod, etc.
Then, you can update just fine.
Again, BIG THANKS to xda community.

raijinshou said:
thanks for the link. it did not directly make my device can be updated, but incase others have this problem and looking for solution, here are the things I did and fix it:
flash boot.img and flash system.img
these 2 files are needed to be at STOCK, I extract from the factory image, and flash through fastboot.
flashing these 2 files WILL NOT CAUSE application to be formatted (like what I thought at the first time).
It will simply remove any tweak done to system such as ads blocking (adaway, etc), battery icon mod, etc.
Then, you can update just fine.
Again, BIG THANKS to xda community.
Click to expand...
Click to collapse
Sorry, but I searched and searched but I still don't understand. I removed all my mods.
I wanted to update to 4.2.2 but it says apply_patch_check error about Currents.
How do I flash that boot.img and system.img? Trough custom recovery or stock? And where can I find those files? Thanks.

Guzanni said:
Sorry, but I searched and searched but I still don't understand. I removed all my mods.
I wanted to update to 4.2.2 but it says apply_patch_check error about Currents.
How do I flash that boot.img and system.img? Trough custom recovery or stock? And where can I find those files? Thanks.
Click to expand...
Click to collapse
boot.img and system.img can be founded in the STOCK ROM, here is the link for STOCK 4.2.1 for Nexus 4:
https://docs.google.com/open?id=0B_zuNWpIf1ujNlFDVnZ3dzg2WEU
(Source: http://www.randomphantasmagoria.com/firmware/nexus-4/occam/ )
Extract the file, you can find boot.img and system.img inside it.
To flash these 2 files, since I am not familiar with fastboot, I am using Nexus 4 Toolkit to help with it.
You can download Nexus 4 Toolkit: http://goo.im/devs/mskip/toolkit/google_nexus4/Google_Nexus_4_ToolKit_v1.3.0.exe
(Source: http://forum.xda-developers.com/showthread.php?t=1995688 )
Copy boot.img and system.img to Nexus 4 Toolkit folder of "put_img_files_to_flash_here"
then using "11. Boot or Flash .img Files to Device option", flash the file to the correct partition
(when flashing boot.img, to boot partition | when flashing system.img, to system partition).

[Q] Nexus 7 32GB stock kernel

Hi guys! I need stock kernel form android 4.2.2
Best for me is recovery image from Franco kernel updater.
Nexus 7 32GB android 4.2.2 Wi-Fi

LukasDee said:
Hi guys! I need stock kernel form android 4.2.2
Best for me is recovery image from Franco kernel updater.
Nexus 7 32GB android 4.2.2 Wi-Fi
Click to expand...
Click to collapse
Download the stock image file and extract the boot.img from there and place it in kerne_backup folder.
http://www.droid-life.com/2013/02/12/download-nexus-7-android-4-2-2-jdq39-update/

thatromo arch
Finding update package...
Opening update package...
Installing Update...
Verifying current system...
assert failed: apply_patch_check(EMMC:/dev/block/platform/sdhci-tegra.3by-name/LNX:5060608:319331fae14ec8a88063751475fce26bae328e0:5062656:af83f09e77a64ed7eda2adad2a16bd0c12d5d7fd")
Installation Aborted.
I see this ;/
Nexus not boot up. its stock on boot loader

If you are trying to perform an upgrade to 4.2.2, then you would need the boot image from the version of the ROM you are upgrading from.
If you already have 4.2.2 (see your sig), why would you be trying to install an update package?
If you already have 4.2.2, but a custom kernel, you can flash the boot.img file from the Google distro a bunch of different ways, here's 3:
1) fastboot (unlocked bootloader):
- fastboot flash boot boot.img
2) ADB (with custom recovery running)
- adb push boot.img /sdcard/boot.img
- adb shell dd if=/sdcard/boot.img of=/dev/block/platform/sdhci-tegra.3/by-name/LNX
3) restore only the boot image from a prior Nandroid backup (twrp)
If you want decent help, you really ought to state:
- is your bootloader unlocked?
- do you have a custom recovery installed?
- if Yes (to the above question), did you make any Nandroid backups prior to the custom kernel install?

LukasDee said:
Finding update package...
Opening update package...
Installing Update...
Verifying current system...
assert failed: apply_patch_check(EMMC:/dev/block/platform/sdhci-tegra.3by-name/LNX:5060608:319331fae14ec8a88063751475fce26bae328e0:5062656:af83f09e77a64ed7eda2adad2a16bd0c12d5d7fd")
Installation Aborted.
I see this ;/
Nexus not boot up. its stock on boot loader
Click to expand...
Click to collapse
*face palm*
I told you to extract the boot.img file and put it in the kernel_backup folder. I didn't say flash the file...
Sent from my Nexus 4 using Tapatalk 2

Ok. I restore bootloader and nexus boot up
Thanx for support.
Sent from my Nexus 7 using xda app-developers app

LukasDee said:
Ok. I restore bootloader and nexus boot up
Thanx for support.
Click to expand...
Click to collapse
You are going to run into a huge amount of trouble if you don't understand the difference between bootloader and boot partition.
Perhaps it's just a language thing, but understanding the difference means the difference between a tablet which survives and one that becomes a brick.
good luck

Finally I using nexus toolkit and install fresh android 4.2.2 using image from Google dev web site and re unlock and root my tablet. After this everything working like before
I know this is stupid solution but work.
Sent from my Nexus 7 using xda app-developers app

[Q] Can't install 4.4.2 OTA update due to font file

I have a Nexus 7 (2012) with 4.4, rooted, TWRP 2.6.0.0. I'm trying to update to the 4.4.2 OTA update, but it's not working. Whether I run it from the system notification prompt or try to install the file manually (in /cache) via TWRP, it fails with this error:
"/system/fonts/Roboto-Bold.ttf" has unexpected contents.​
Then it says there's an error executing the updater binary, an error flashing zip file, etc. All the standard stuff when it bombs out of an install.
I did change my font using ROM Toolbox Pro a while back, but I restored the original font and tried running it again. Still got the error. I tried downloading a fresh copy of the .ttf file and replacing the one in /system/fonts, but still got the error. It seems a little silly for the whole update to crash due to a font file, but whatever...
Can anyone help me figure out what's going on, and how to get this OTA to install properly? Thanks in advance!

Probably it's easier to flash the 4.4.2 factory image resp. system.img and boot.img of it manually than trying to recover the correct 4.4 state.
There are already some posts where I described how to do it and there is also a post in my blog describing the process.
Sent from my Nexus 7 using xda app-developers app

AndDiSa said:
Probably it's easier to flash the 4.4.2 factory image resp. system.img and boot.img of it manually than trying to recover the correct 4.4 state.
There are already some posts where I described how to do it and there is also a post in my blog describing the process.
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
Well, after every failure, it reboots and goes right back to functioning perfectly as it was on 4.4. But, I will consider the direct flash of 4.4.2 if no one else has any other suggestions. Thanks!

[Q] Secure Booting Unsuccessful; Standard issue, but confused and stuck...

So I've searched and read for about the last 4 hours, and I'm only more confused than before.
Using a Verizon VS980:
1.Took the OTA (to VS96012B) when I first got the phone
2. Rooted using ioroot script
3. installed latest twrp (2.6.3.3) using Freegee
4. Downloaded CM10.2 stable directly from Get.cm as well as appropriate GAPPS
5. Rebooted into TWRP
6. Wiped (but did not backup since I didn't care about keeping user data...did this wipe the factory OS too then?)
7. Attempted to flash CM10.2 and got the following error:
"Skipping MD5 check: no MD5 file found.
assert failed: run_program("/system/bin/loki.sh
E:Error executing updater binary in zip '/sdcard
Error flashing zip '/sdcard/download/cm-10.2.0
8. Attempted to reboot into stock since CM flash had failed and got "secure booting unsuccessful" error message
Why would the CM10.2 install be failing under the above messages? And did I blow away my factory ROM? I just used the generic TWRP 2.6.3.3 "factory reset option"??
Dear lord help me. I've read so many threads, but I've ended up much more confused.
In theory, the stock ROM should still be installed since the CM10.2 flash failed, what do I need to do to A.)Be able to successfully flash the CM10.2 without getting the "error executing updater binary in zip" problem, or B.) Be able to at least boost back into stock LG image?
Thanks,
-A

Planning on using this to go back to how it shipped stock, and then re-rooting, and re-installing TWRP and taking another shot at a ROM. Can someone please tell me if this is the right direction?
http://forum.xda-developers.com/showthread.php?t=2449670

After going back to stock I would go this route if u take 12b OTA.
http://forum.xda-developers.com/showthread.php?t=2587296
Sent from Verizon logo plastered G2 bastard

Thanks for the reply! I've edited the OP for a little additional detail/clarity. I'm trying to figure out at this stage why my CM10.2 install failed first and foremost. I'd like to be able to avoid going all the way back to stock if possible?
Any suggestions on why I was getting the below message during attempting to install?
"
Attempted to flash CM10.2 and got the following error:
"Skipping MD5 check: no MD5 file found.
assert failed: run_program("/system/bin/loki.sh
E:Error executing updater binary in zip '/sdcard
Error flashing zip '/sdcard/download/cm-10.2.0
"

amazonparrot said:
Thanks for the reply! I've edited the OP for a little additional detail/clarity. I'm trying to figure out at this stage why my CM10.2 install failed first and foremost. I'd like to be able to avoid going all the way back to stock if possible?
Any suggestions on why I was getting the below message during attempting to install?
"
Attempted to flash CM10.2 and got the following error:
"Skipping MD5 check: no MD5 file found.
assert failed: run_program("/system/bin/loki.sh
E:Error executing updater binary in zip '/sdcard
Error flashing zip '/sdcard/download/cm-10.2.0
"
Click to expand...
Click to collapse
It seems like the recovery u flashed from freegee was not properly loki'd for the 12b firmware. It allowed u to overwrite the stock recovery but not flash any ROMs. U could try pushing the patched Loki img and recovery in the thread I posted earlier using adb. U can follow the same instructions in the thread u linked just use the updated patched files.
When u wiped prior to flashing cm10.2, if u wiped system then u have no ROM on ur device to boot into. Always make a backup just in case. That way if u have a bad download or the ROM just won't boot, u gotta plan B.
Sent from Verizon logo plastered G2 bastard

truckroot said:
It seems like the recovery u flashed from freegee was not properly loki'd for the 12b firmware. It allowed u to overwrite the stock recovery but not flash any ROMs. U could try pushing the patched Loki img and recovery in the thread I posted earlier using adb. U can follow the same instructions in the thread u linked just use the updated patched files.
When u wiped prior to flashing cm10.2, if u wiped system then u have no ROM on ur device to boot into. Always make a backup just in case. That way if u have a bad download or the ROM just won't boot, u gotta plan B.
Sent from Verizon logo plastered G2 bastard
Click to expand...
Click to collapse
If I just used the standard TWRP Wipe/factory reset, (which I did) my factory system ROM should be still there, but for whatever reason I'm unable to boot it.
I'm assuming the threads and methods you referenced will work with ADB sideload?
Thanks again

amazonparrot said:
If I just used the standard TWRP Wipe/factory reset, (which I did) my factory system ROM should be still there, but for whatever reason I'm unable to boot it.
I'm assuming the threads and methods you referenced will work with ADB sideload?
Thanks again
Click to expand...
Click to collapse
Yeah. I would try pushing the patched Loki img via adb, then try flashing the cm10.2 ROM. Otherwise u can sideload a stock ROM and flash that.
Sent from Verizon logo plastered G2 bastard

Managed to get back to stock!
Re-rooted, and used Freegee to install latest CWM ths time. Attempted to install CM10.2 again (fresh download) and it STILL gives the error:
Attempted to flash CM10.2 and got the following error:
"Skipping MD5 check: no MD5 file found.
assert failed: run_program("/system/bin/loki.sh
E:Error executing updater binary in zip '/sdcard
Error flashing zip '/sdcard/download/cm-10.2.0
Why am I still unable to flash a ROM?

amazonparrot said:
Managed to get back to stock!
Re-rooted, and used Freegee to install latest CWM ths time. Attempted to install CM10.2 again (fresh download) and it STILL gives the error:
Attempted to flash CM10.2 and got the following error:
"Skipping MD5 check: no MD5 file found.
assert failed: run_program("/system/bin/loki.sh
E:Error executing updater binary in zip '/sdcard
Error flashing zip '/sdcard/download/cm-10.2.0
Why am I still unable to flash a ROM?
Click to expand...
Click to collapse
Read that some are having issues using Freegee/Flashify to install a working loki'd recovery with 12b OTA. ADB seems to work best. Glad to hear u were able to get back to stock though.
Sent from Verizon logo plastered G2 bastard

I'm actually on 11A :-/
I was planning on using CM10.2 since I just want a 4.3 or 4.4 ROM thats actually stable, but maybe its just the particular ROM I'm trying? I'll try doing ADB to push a different recovery just in case.
Any recommendations on a good stable ROM?

amazonparrot said:
I'm actually on 11A :-/
I was planning on using CM10.2 since I just want a 4.3 or 4.4 ROM thats actually stable, but maybe its just the particular ROM I'm trying? I'll try doing ADB to push a different recovery just in case.
Any recommendations on a good stable ROM?
Click to expand...
Click to collapse
The unofficial cm 4.4.2 is a good one. OP has good directions on getting ROM to run perfectly with kernel settings.
If ur on 11a u should have zero issues flashing, def try a different ROM.
Sent from Verizon logo plastered G2 bastard

Same error... kinda freaking out now #FML
I am so lost and confused. Definately in over my head right now. I usually depend on the one click methods to flash, and this time I'm bricked. Same problem as post #1 on the thread. Not very familiar with adb. Is anyone with experience in this area able/willing to remote into my mac or even over the phone to help a brother out? I'm willing to compensate you for your time.
Thanks,
Vinnie

[Q] Nexus 4 kitkat 4.4.3 Update error

Hi,
I have been trying to update my N4 for quite sometime now and have had a particular issue every time. First I tried with the OTA file and adb sideload. Didn't work. Then this morning I received the OTA on the phone itself, tried doing it but still got the same error message. It says "Installation aborted. Error (Status 7)" I have no clue whatsoever what it is. Please help.
I am using stock rom, rooted.
P.S. if this has already been posted by someone else, kindly direct me to that thread.
Thanks

Error status 7 means modification to the /system directory. You must fastboot flash the stock 4.4.2 /system image only from the factory image package and then you will be able to sideload the update, all with no loss of data. This is what I did since my /system was heavily modified. After flashing the ota, re apply all your /system tweaks, if any.
Sent from my Nexus 4 using XDA Free mobile app

I used the following thread.
Long story short I grabbed the stock ROM and flashed only the system. img to phone
http://android.stackexchange.com/qu...ttempting-to-adb-sideload-the-ota-update-on-n
Sent from my Nexus 4 using XDA Premium 4 mobile app

anubhavmehta said:
Hi,
I have been trying to update my N4 for quite sometime now and have had a particular issue every time. First I tried with the OTA file and adb sideload. Didn't work. Then this morning I received the OTA on the phone itself, tried doing it but still got the same error message. It says "Installation aborted. Error (Status 7)" I have no clue whatsoever what it is. Please help.
I am using stock rom, rooted.
P.S. if this has already been posted by someone else, kindly direct me to that thread.
Thanks
Click to expand...
Click to collapse
Recovery versión?
Sent from my Nexus 4

Thanks a lot!
Hey, thanks for the info. One more question though, will fastboot flashing 4.4.2 system image remove all data? I guess the problem here might be because of Xposed Module, which might have made some changes in the system directory. The other issue that I am having is that I am unable to access any content on my laptop with my phone connected over USB, so i am unable to take backup of my data. I tried backup using recovery as well but it didn't work as well.
lolcakes203 said:
Error status 7 means modification to the /system directory. You must fastboot flash the stock 4.4.2 /system image only from the factory image package and then you will be able to sideload the update, all with no loss of data. This is what I did since my /system was heavily modified. After flashing the ota, re apply all your /system tweaks, if any.
Sent from my Nexus 4
Click to expand...
Click to collapse

CWM 6.0.4.3
tupac4u said:
Recovery versión?
Sent from my Nexus 4
Click to expand...
Click to collapse

Flashing the entire factory image will delete all your data and return your device to pure stock, but we are not asking you to do that. All you need to do is flash the system.img which is located in the factory image which will return your /system partition to pure stock, and this will not delete any data because it does not touch your /data partition.
Xposed does modify /system and was most likely the cause for your ota error. You can try disabling xposed and flashing again, but if you get more problems, it makes the most sense to flash system.img and then flash the ota and re apply xposed.
Sent from my Nexus 4 using XDA Free mobile app

yep, tried that. didn't work. I'll try the fastboot system.img solution and hope it works.
lolcakes203 said:
Flashing the entire factory image will delete all your data and return your device to pure stock, but we are not asking you to do that. All you need to do is flash the system.img which is located in the factory image which will return your /system partition to pure stock, and this will not delete any data because it does not touch your /data partition.
Xposed does modify /system and was most likely the cause for your ota error. You can try disabling xposed and flashing again, but if you get more problems, it makes the most sense to flash system.img and then flash the ota and re apply xposed.
Sent from my Nexus 4 using XDA Free mobile app
Click to expand...
Click to collapse

I am having the same problem, my nexus 4 is unrooted with clean stock img but I still get error in the middle of the OTA update to 4.4.3, anyone one know why? Please help

Worked!
All done with absolutely no loss of data. Thanks a lot! :good:
lolcakes203 said:
Flashing the entire factory image will delete all your data and return your device to pure stock, but we are not asking you to do that. All you need to do is flash the system.img which is located in the factory image which will return your /system partition to pure stock, and this will not delete any data because it does not touch your /data partition.
Xposed does modify /system and was most likely the cause for your ota error. You can try disabling xposed and flashing again, but if you get more problems, it makes the most sense to flash system.img and then flash the ota and re apply xposed.
Sent from my Nexus 4 using XDA Free mobile app
Click to expand...
Click to collapse