Related
So I want to update to 4.2.2 using the Nexus Toolkit (I have the latest one) but have been running into problems. Every time I try to update it fails: assert failed: apply_patch_check ("/system/lib/libSR_AudioIn.so", bcc09f67f497c66aedece202942bc4c45f712f62", "85eeeb97d102a3f6656e58cb25ad97bbe29ec613")
After reading around I found out that the Beats Audio drivers I had installed (and thought I removed) modified that .so file. I'd like to be able to just replace that single file with the stock version to save me the hassle of flashing the whole stock image.
Does anyone know where I can find a copy of that file, or a work around that I can use?
Thanks!
http://forum.xda-developers.com/showthread.php?t=2144330
use 'search thread', people have similar issues, you'll find a solution there.
Yeah, I read through about 10 different threads about this but none of them actually had a solution... Just a bunch of "This is happening UPDATE: Fixed it" type posts. No one has actually posted their solution in any of the threads I've looked through (including the one you linked). Thanks for the link though.
issak42 said:
http://forum.xda-developers.com/showthread.php?t=2144330
use 'search thread', people have similar issues, you'll find a solution there.
Click to expand...
Click to collapse
i am also looking for SiMILAR Method like how we installed BEATS AUDIO so the method should be the same if someone can provide stock audio driver ZIP so we can reflash it back to get old drivers
I had this same exact problem.
I had beats audio installed and even with the script uninstaller and uninstalling the APP my LIB file was missing. i copied it from N4 and still it kept failing on that LIB file every time i applied the OTA zip
the BEST way to resolve this is to
extract the SYSTEM.IMG and BOOT.IMG file from the 4.2.1 stock image
FASTBOOT FLASH SYSTEM.IMG to your device
FASTBOOT FLASH BOOT.IMG to your device
this will flash the stock system files AND kernal to your device.
reboot your device and try to flash the OTA again and it should work.
Thanks. That's exactly what I did... I decided to use the Nexus 7 Toolkit to just restore to stock (I was getting frustrated so I didn't care if it removed all my apps, etc). It turns out the toolkit lets you restore the stock image without wiping all of your apps/sd data so I was able to update and everything was great. Not rooted anymore, but I'll deal with that later .
nextelbuddy said:
I had this same exact problem.
I had beats audio installed and even with the script uninstaller and uninstalling the APP my LIB file was missing. i copied it from N4 and still it kept failing on that LIB file every time i applied the OTA zip
the BEST way to resolve this is to
extract the SYSTEM.IMG and BOOT.IMG file from the 4.2.1 stock image
FASTBOOT FLASH SYSTEM.IMG to your device
FASTBOOT FLASH BOOT.IMG to your device
this will flash the stock system files AND kernal to your device.
reboot your device and try to flash the OTA again and it should work.
Click to expand...
Click to collapse
i had the same deal. flashed system.img, updated, flashed su. i didn't flash boot though
?need to flash boot.img
Thanks for above. I have solved the beats audio problem as per above. I only flashed the system.img and not the boot.img. Does this matter? Or should I do so to get the latest kernel? or is my kernel 3.1.10-g05b777c the latest?
Cheers,
Sam
yuo need to be on stock everything so to be safe and retain all user data and apps, just flash system.img and boot.img
it wont hurt anything and saves you headaches
I am currently in the same boat. I can't seem to find the stock image for 4.2.1. On Google's site they only have 4.1.2 and 4.2.2. Does any one know where I can get it or at least the system.img and boot.img from it?? Thanks for the help.
Leif
Leifrn said:
I am currently in the same boat. I can't seem to find the stock image for 4.2.1. On Google's site they only have 4.1.2 and 4.2.2. Does any one know where I can get it or at least the system.img and boot.img from it?? Thanks for the help.
Leif
Click to expand...
Click to collapse
http://goo.im/devs/WugFresh/stock/nakasi
burnitdown said:
i had the same deal. flashed system.img, updated, flashed su. i didn't flash boot though
Click to expand...
Click to collapse
same here. Now on 4.2.2 rooted.
I tried flashing boot.img but I cant seem to fastboot to device because of an unknown partition error. What to do??
swidnik0
You sir, are a gentleman. Thanks for you help.
Leif
Try this command to resolve partition issue
Leonhan said:
I tried flashing boot.img but I cant seem to fastboot to device because of an unknown partition error. What to do??
Click to expand...
Click to collapse
> fastboot flash system system.img
[email protected] said:
> fastboot flash system system.img
Click to expand...
Click to collapse
Oh there, spot on! Thanks man!
nextelbuddy said:
I had this same exact problem.
I had beats audio installed and even with the script uninstaller and uninstalling the APP my LIB file was missing. i copied it from N4 and still it kept failing on that LIB file every time i applied the OTA zip
the BEST way to resolve this is to
extract the SYSTEM.IMG and BOOT.IMG file from the 4.2.1 stock image
FASTBOOT FLASH SYSTEM.IMG to your device
FASTBOOT FLASH BOOT.IMG to your device
this will flash the stock system files AND kernal to your device.
reboot your device and try to flash the OTA again and it should work.
Click to expand...
Click to collapse
Sorry for noon question
Any link for the guide ?
For flashing boot.IMG system.IMG
Sorry I have never done these things before
Sent from my Nexus 7 using Tapatalk HD
How/where to extract system.img and boot.img ??
rm79 said:
Thanks. That's exactly what I did... I decided to use the Nexus 7 Toolkit to just restore to stock (I was getting frustrated so I didn't care if it removed all my apps, etc). It turns out the toolkit lets you restore the stock image without wiping all of your apps/sd data so I was able to update and everything was great. Not rooted anymore, but I'll deal with that later .
Click to expand...
Click to collapse
How/where to extract system.img and boot.img ??
after I flashed 4.2.1 system and boot images
so after flashed system.img and boot.img i was able to upgrage 4.2.2 OTA but now my nexus is not rooted. so if im gonna root it again will i lose all my data and apps?
ashok_jeev said:
so after flashed system.img and boot.img i was able to upgrage 4.2.2 OTA but now my nexus is not rooted. so if im gonna root it again will i lose all my data and apps?
Click to expand...
Click to collapse
If your bootloader is already unlocked, then rooting it won't wipe your data.
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).
Is it possible on an unlocked nexus 7 to effectively install a custom ROM from fastboot with the command "fastboot update </path/to/your/RomFile.zip>" without using a custom recovery such as TWRP?
Sent from my Nexus 7 using Xparent Green Tapatalk 2
Fastboot is used to flash .img file not .zip
norcal61 said:
Is it possible on an unlocked nexus 7 to effectively install a custom ROM from fastboot with the command "fastboot update </path/to/your/RomFile.zip>" without using a custom recovery such as TWRP?
Sent from my Nexus 7 using Xparent Green Tapatalk 2
Click to expand...
Click to collapse
What you can do is fastboot flash system system.img.
system.img can come from a backup, a google stock image or make it yourself
So there is no way to flash an actual zip file via fastboot? I found this article here on xda http://forum.xda-developers.com/wiki/index.php?title=Flashing_Guide_-_Android
Sent from my Nexus 7 using Xparent Green Tapatalk 2
Why would you want to? Flash recovery with fastboot and flash your ROM from there.
Sent from my Nexus 7 using Tapatalk HD
korockinout13 said:
Why would you want to? Flash recovery with fastboot and flash your ROM from there.
Sent from my Nexus 7 using Tapatalk HD
Click to expand...
Click to collapse
I want to be able to format my internal SD from TWRP which would wipe everything off the SD including any zip files then flash the zip from my computer from a command prompt with the tablet booted into the boot loader.
Sent from my Nexus 7 using Xparent Green Tapatalk 2
norcal61 said:
I want to be able to format my internal SD from TWRP which would wipe everything off the SD including any zip files then flash the zip from my computer from a command prompt with the tablet booted into the boot loader.
Sent from my Nexus 7 using Xparent Green Tapatalk 2
Click to expand...
Click to collapse
That's quite pointless to format everything... But in this case, you can adb sideload the zip from recovery. No need for the file on the sd card.
Sent from my Nexus 7 using Tapatalk HD
norcal61 said:
So there is no way to flash an actual zip file via fastboot? I found this article here on xda http://forum.xda-developers.com/wiki/index.php?title=Flashing_Guide_-_Android
Sent from my Nexus 7 using Xparent Green Tapatalk 2
Click to expand...
Click to collapse
Only STOCK factory ROMs are flashable this way...
cf. this line from the flash-all.* script for the full factory image of Jellybean 4.2.2.. for 'grouper'.
Code:
fastboot -w update image-nakasi-jdq39.zip
In image-nakasi-jdq39.zip the following files are found...
boot.img
recovery.img
system.img
userdata.img
----
CUSTOM ROMs, however, can only be flashed via a CUSTOM RECOVERY, such as CWM or TWRP.
And as korockinout13 alludes to, it's a trivial matter to FASTBOOT FLASH a custom recovery... and then flash the ROM of your choice.
If you already have FASTBOOT (and your question suggests that you do)... then what's the problem?
Rgrds,
Ged.
The bootloaders of different Android devices have differing capabilities precisely because they are proprietary. Moreover, it is the bootloader that actually implements the heavy lifting of installs etc - the PC fastboot program does little more than send ASCII commands and push blobs of data across the USB cable.
Some Android devices have had bootloaders that understand how to unpack .zip files that contain other types of archives (.tar files, et cetera) but required that the .zip file is placed onto an external SD card using a standardized name for that device. (When the bootloader starts up, it would look for that file automatically). But this was for signed factory bundles, not for arbitrary aftermarket customization. In any event, this doesn't apply to the N7 afaik.
None of these behaviors are standardized though; each vendor decides how it will interpret and respond to fastboot commands from the PC.
The N7 bootloader clearly understands what a sparse ext4 image file is (for use with system.img and userdata.img files) - if it handled them as a pure binary blob, how would it be possible to use the same userdata.img file with 8Gb, 16Gb, and 32Gb devices? Moreover, the N7's "fastboot format" command clearly is capable of creating ext4 filesystems.
So would it be possible to create "sparse ext4" system.img/userdata.img image files corresponding to a custom ROM that could flashed in exactly the same way as the factory image using fastboot? Yes, absolutely. (I've done just that.)
But this is NOT the same thing as taking a custom ROM .zip file (intended to be processed by a recovery using an "edify" script) and flashing it with fast boot; it ain't that easy.
hi,
i have a nexus 7 and i want to flash a custom rom but i wiped everything and the zip gone from my tablet now the tablet is without os,please help!!
paul20 said:
hi,
i have a nexus 7 and i want to flash a custom rom but i wiped everything and the zip gone from my tablet now the tablet is without os,please help!!
Click to expand...
Click to collapse
Better to stick with stock and not attempt to flash custom ROMs if you don't know how to use a custom recovery or toolkit.
paul20 said:
hi,
i have a nexus 7 and i want to flash a custom rom but i wiped everything and the zip gone from my tablet now the tablet is without os,please help!!
Click to expand...
Click to collapse
Not a big deal. You need to download the factory image for your nexus 7 and find instructions on how to restore with fastboot. That will take you back to factory stock. Or another option is to fastboot flash TWRP custom recovery and use the adb sideload feature within TWRP to flash a custom ROM of your choice. You can find instructions on both of these procedures here at xda or with a simple Google search. Let me know if that works out for you. If you need more help I can give you a hand when I get home from work
Sent from my Nexus 7 using Xparent Green Tapatalk 2
everything okay i flashed stock rom with the toolkit and then the custom one,it's ok now i am not so noob but it's my first tablet without external sd card and i got panik
thanks everyone
paul20 said:
hi,
i have a nexus 7 and i want to flash a custom rom but i wiped everything and the zip gone from my tablet now the tablet is without os,please help!!
Click to expand...
Click to collapse
Fastboot flash a custom recovery. Then, there are many threads showing how to get the .zip to the device for flashing.
Sent from my Nexus 7 using xda premium
norcal61 said:
Not a big deal. You need to download the factory image for your nexus 7 and find instructions on how to restore with fastboot. That will take you back to factory stock. Or another option is to fastboot flash TWRP custom recovery and use the adb sideload feature within TWRP to flash a custom ROM of your choice. You can find instructions on both of these procedures here at xda or with a simple Google search. Let me know if that works out for you. If you need more help I can give you a hand when I get home from work
Sent from my Nexus 7 using Xparent Green Tapatalk 2
Click to expand...
Click to collapse
Hey guys,
I made the same mistake as paul20 with my HTC ONE and your answer saved my morning, thanks! adb sideload feature rocks!
rebel1699 said:
Fastboot flash a custom recovery. Then, there are many threads showing how to get the .zip to the device for flashing.
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
Can you point me to one of those threads?
fastboot error
GedBlake said:
Only STOCK factory ROMs are flashable this way...
cf. this line from the flash-all.* script for the full factory image of Jellybean 4.2.2.. for 'grouper'.
Code:
fastboot -w update image-nakasi-jdq39.zip
In image-nakasi-jdq39.zip the following files are found...
boot.img
recovery.img
system.img
userdata.img
----
CUSTOM ROMs, however, can only be flashed via a CUSTOM RECOVERY, such as CWM or TWRP.
And as korockinout13 alludes to, it's a trivial matter to FASTBOOT FLASH a custom recovery... and then flash the ROM of your choice.
If you already have FASTBOOT (and your question suggests that you do)... then what's the problem?
Rgrds,
Ged.
Click to expand...
Click to collapse
========================================
the fastboot says --
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
i m porting the stock rom (it is a zip file) which has boot.img ,recovery.img ,system.img ,userdata.img into it yet the error comes.
the prob is that the rom is not detecting my sd card and neither the CWM i tried a different sd card yet it isnt detecting...i alst tried mounting sd card it showed error there also! plz help me! everything was working sommoth! this problem came after i ported droid_dd_gb_13.3 v3 ...my device is micromax a57 plz help mee!!!
GedBlake said:
Only STOCK factory ROMs are flashable this way...
cf. this line from the flash-all.* script for the full factory image of Jellybean 4.2.2.. for 'grouper'.
Code:
fastboot -w update image-nakasi-jdq39.zip
In image-nakasi-jdq39.zip the following files are found...
boot.img
recovery.img
system.img
userdata.img
----
CUSTOM ROMs, however, can only be flashed via a CUSTOM RECOVERY, such as CWM or TWRP.
And as korockinout13 alludes to, it's a trivial matter to FASTBOOT FLASH a custom recovery... and then flash the ROM of your choice.
If you already have FASTBOOT (and your question suggests that you do)... then what's the problem?
Rgrds,
Ged.
Click to expand...
Click to collapse
where do you get those .img files from?? bY the way im using sony xperia sp and bricked i guess ;(
no adb, can't enable USB debugging
korockinout13 said:
That's quite pointless to format everything... But in this case, you can adb sideload the zip from recovery. No need for the file on the sd card.
Sent from my Nexus 7 using Tapatalk HD
Click to expand...
Click to collapse
What if you can't enable USB debugging because you accidentally formated /persist and can't get into your system? 16 hours of that arrow turning and nothing...
Can someone help me, I have same problem but i extracted my Zip file and have Boot.img if i flash that will it work again
Can't update from 4.3 Using stock kernel ( swapped from franco to install the ota)
Tried CWM and TWRP, both fail.
here what happens: https://www.dropbox.com/s/6a1oesuwa3zgk1h/2013-11-14%2004.12.43.jpg?m
the same problem, the same CWM version
Not sure if it helps, but I followed this guide and now I am on KitKat
Download the JWR66Y factory image, extract everything and flash the system.img in fastboot mode, which should restore any changes made to the system partition. Try again after that
I'm having the same issue. I was on JWR66V and tried to update to 4.4 in cwm but it wanted me to be on JWR66Y... so after much hunting around I finally found a working JWR66Y flash able zip and was able to update to that.
However, I noticed that supersu got screwed up in the process, saying it couldn't find binaries. I downloaded and flashed the latest supersu, but that had no effect. I figured I would go ahead and try updating to 4.4 anyway and fix the root issue later...
The 4.4 update seemed to be going OK in cwm until I hit that same issue you did at about 75%. I've seen elsewhere that certain versions of supersu have been causing update problems. My only other thought is maybe I need to update my cwm to a newer version.
Eregoth said:
Download the JWR66Y factory image, extract everything and flash the system.img in fastboot mode, which should restore any changes made to the system partition. Try again after that
Click to expand...
Click to collapse
Why not getting directly the kitkat-image and flash boot.img and system.img in fastboot mode? No further update needed ...
Sent from my Nexus 7 using xda app-developers app
Is it possible? It not I will wait till I get home tonight. I'm thinking flash a stock rom zip. Then opt in. Don't loose all internal storage? Thoughts
Sent from my Nexus 6P using Tapatalk
iamdarren said:
Is it possible? It not I will wait till I get home tonight. I'm thinking flash a stock rom zip. Then opt in. Don't loose all internal storage? Thoughts
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
Yes it is possible. Just download the complete N factory image, plus the modified boot image (kernel).
Extract the system.img, and vendor.img out of the factory image.
And now, flash the three files using TWRP - system.img (system image), vendor.img (vendor image), and boot.img (kernel).
DJBhardwaj said:
Yes it is possible. Just download the complete N factory image, plus the modified boot image (kernel).
Extract the system.img, and vendor.img out of the factory image.
And now, flash the three files using TWRP - system.img (system image), vendor.img (vendor image), and boot.img (kernel).
Click to expand...
Click to collapse
Where can I find the modified boot image?
Edit: Found it, nevermind.
messiahfreedom said:
Where can I find the modified boot image?
Edit: Found it, nevermind.
Click to expand...
Click to collapse
Grab it from here, and make sure to download the corresponding boot.img to your build number.
Link: http://forum.xda-developers.com/nexus-6p/general/stock-modified-boot-img-regular-root-t3306684
DJBhardwaj said:
Yes it is possible. Just download the complete N factory image, plus the modified boot image (kernel).
Extract the system.img, and vendor.img out of the factory image.
And now, flash the three files using TWRP - system.img (system image), vendor.img (vendor image), and boot.img (kernel).
Click to expand...
Click to collapse
If we do it this way, will we lose data? Can we just update from 6.0.1?
jorgis1 said:
If we do it this way, will we lose data? Can we just update from 6.0.1?
Click to expand...
Click to collapse
You can if you were on a stock rom.
Sent from my Nexus 6P using Tapatalk
jorgis1 said:
If we do it this way, will we lose data? Can we just update from 6.0.1?
Click to expand...
Click to collapse
No, you won't loose any data. Your userdata/data partition will stay as is. You will just wipe the system and boot through TWRP, and then flash the listed image files.
superchilpil said:
You can if you were on a stock rom.
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
But if we do it the manual way as stated before, do we lose root? What about gapps? Will those be included?
flashfire is a great app, does it all for you...
I simply downloaded OTA through the system update, then after it was downloaded instead of allowing it to "Restart and Install" which would have failed due to my custom recovery, I just opened flashfire. It found the OTA automatically and I hit Flash button. Done!
I ended up loading up from the PC. It's better this way because I only had 2gb of space on my 64gb!!! Bad thing is, I have spent about 2hrs installing!
Sent from my Nexus 6P using Tapatalk
So I can use flashfire to flash the latest N beta even though I'm currently running a custom ROM?
Sent from my Nexus 6P using XDA-Developers mobile app
GatorsUF said:
flashfire is a great app, does it all for you...
I simply downloaded OTA through the system update, then after it was downloaded instead of allowing it to "Restart and Install" which would have failed due to my custom recovery, I just opened flashfire. It found the OTA automatically and I hit Flash button. Done!
Click to expand...
Click to collapse
Foes your custom recovery still work? I tried this method and it just wouldn't boot into TWRP. Been trying all day thru different methods. Idk how to use adb fastboot on a computer so I'm a lil lost when trying any other method. I've been using Wug's toolkit but until he pushes an update for it I'm on stock MM until i can figure something out.
x.0ni.x said:
Foes your custom recovery still work? I tried this method and it just wouldn't boot into TWRP. Been trying all day thru different methods. Idk how to use adb fastboot on a computer so I'm a lil lost when trying any other method. I've been using Wug's toolkit but until he pushes an update for it I'm on stock MM until i can figure something out.
Click to expand...
Click to collapse
why does the wug toolkit not work?
I don't know a lot about Flashfire as far as it's compatibility with Custom Roms and such. I was previously on stock android Marshmellow with root and twrp. My phone downloaded the OTA for Android N when I "enrolled" in the beta program. I chose not to allow the phone to attempt to install the OTA as it would likely fail due to my custom recovery, to my surprise when I opened flashfire it offered to install the "update.zip" (AKA the OTA) and I simply hit "flash". It installed the OTA (did not use TWRP) and rooted my phone all on it's own, I did not lose anything no data was lost.
As a side not I would not recommend using Flashfire if you don't know how to use fastboot commands and the Android SDK. It is not complicated and it is a almost certain way to fix your phone when things go haywire. I strongly encourage you to learn how to use it as it is essential to owning a Nexus imo. These root kits and flashfire programs are cool, but they are always subject to failures...