Hi, I'm trying to update mi nexus 7 wifi (through ADB sideload) to the KRT16S 4.4 update, but i get this error:
"/system/lib/libwebrtc_audio_preprocessing.so" has unespected contents.
E:Error executing updater binary in zip '/data/media/0/sideload.zip'
Click to expand...
Click to collapse
how can I solve?
Put that file back to stock (looks like an audio mod of some sort).. or you can pull the boot.img and system.img from the factory image and just flash them in fastboot
NeoMagus said:
Put that file back to stock (looks like an audio mod of some sort).. or you can pull the boot.img and system.img from the factory image and just flash them in fastboot
Click to expand...
Click to collapse
how can i open on windows the system.img file? 7zip doesn't work...
I use winzip, the files you are looking for are compressed in image-nakasi-krt16s.zip .. I extract to platform-tools in the SDK and then flash in fastboot
Thank you, I'll try
Inviato dal mio HTCSensation utilizzando Tapatalk
Related
Hi there
I've built Firefox OS for the Galaxy Nexus but I'm struggling to find a way of creating a flashable zip to distribute.
This is my first ROM that I have successfully compiled, but everything seems to be working so I wouldn't mind sharing it with the rest of the internet. Any tips?
Thanks!
ojdon said:
Hi there
I've built Firefox OS for the Galaxy Nexus but I'm struggling to find a way of creating a flashable zip to distribute.
This is my first ROM that I have successfully compiled, but everything seems to be working so I wouldn't mind sharing it with the rest of the internet. Any tips?
Thanks!
Click to expand...
Click to collapse
After building from the B2G directory (the folder from where you run ./config.sh and ./build.sh) you should locate boot.img, userdata.img and system.img and copy them over to a folder, then you can flash using fastboot via:
adb reboot bootloader
fastboot flash boot boot.img
fastboot flash userdata userdata.img
fastboot flash system system.img
fastboot erase cache
fastboot reboot
janjongboom said:
After building from the B2G directory (the folder from where you run ./config.sh and ./build.sh) you should locate boot.img, userdata.img and system.img and copy them over to a folder, then you can flash using fastboot via:
adb reboot bootloader
fastboot flash boot boot.img
fastboot flash userdata userdata.img
fastboot flash system system.img
fastboot erase cache
fastboot reboot
Click to expand...
Click to collapse
Firefox OS in Galaxy Nexus, I want to take a look! Keep us up to date man!
janjongboom said:
After building from the B2G directory (the folder from where you run ./config.sh and ./build.sh) you should locate boot.img, userdata.img and system.img and copy them over to a folder, then you can flash using fastboot via:
adb reboot bootloader
fastboot flash boot boot.img
fastboot flash userdata userdata.img
fastboot flash system system.img
fastboot erase cache
fastboot reboot
Click to expand...
Click to collapse
Ah didn't know this thread had replies so sorry for a bit of a bump. I was kind of after directions on how to create a flashable zip? It's just that I was aiming to avoid end users from using adb and fastboot. Do you know how to create a flashable zip instead?
Thanks for the guidance!
How to get Stock kernel back to get nexus 7 ota updates
i once used DR BEATS audio mod it is not installed now but still i cannot install OTA update which i still repent installing that mod
The easiest way for you would be to do the update manually:
- Get the factory image and extract the following files:
- bootloader-grouper-4.23.img
- boot.img
- system.img
If you want to keep root, get
- UPDATE-SuperSU-v1.51.zip
and copy it to /sdcard and be sure, that you have a custom recovery installed.
Do a nandroid backup before starting and then do a
fastboot flash bootloader bootloader-grouper-4.23.img
fastboot reboot-bootloader
fastboot flash boot boot.img
fastboot flash system system.img
reboot into recovery and flash UPDATE-SuperSU-v1.51.zip
Do a reboot system and, congrats, you should be on Android 4.3 without loosing any data.
AndDiSa said:
The easiest way for you would be to do the update manually:
- Get the factory image and extract the following files:
- bootloader-grouper-4.23.img
- boot.img
- system.img
If you want to keep root, get
- UPDATE-SuperSU-v1.51.zip
and copy it to /sdcard and be sure, that you have a custom recovery installed.
Do a nandroid backup before starting and then do a
fastboot flash bootloader bootloader-grouper-4.23.img
fastboot reboot-bootloader
fastboot flash boot boot.img
fastboot flash system system.img
reboot into recovery and flash UPDATE-SuperSU-v1.51.zip
Do a reboot system and, congrats, you should be on Android 4.3 without loosing any data.
Click to expand...
Click to collapse
Can you guide me how to fastboot flash is it in cwm custom recovery or i need to do that with wugfresh toolkit
Sent from my Nexus 7 using Tapatalk HD
Neither you need a PC to do it. Read about both adb and fastboot instead of having everything spoon fed. That way when something goes wrong you have some idea what to do.
Sent from my Nexus 7 using Tapatalk 4 Beta
I used the fastboot command and updated every time when I bought nexus 7 (wifi) from last year.
However, when I updated from jwr66v to jwr66y, I used wipe function in CWM. Then, I got the "archive does not contain boot.sig" and "archive does not contain recovery.sig" and "failed to allocate XXXXXXX.byte"...
Then I tried to get back version to 4.2.2, but I also got the same error message. I follow the guidehttp://forum.xda-developers.com/showthread.php?t=1907796 to manual flash each .img files, the same problem occur at flashing system.img
At now, I could not get into android system, just hang on the "Google" logo.
I have read the same problem in another threadhttp://forum.xda-developers.com/showthread.php?t=1992063, but I could not have any idea to solve it?
Anyone have idea?
Thank you very much.
PS: I used the platform-tools r22.0.5
"boot.sig и recovery.sig"
You must install the recovery.img and boot.img
Solution
Here's a solution for ya: http://shuiqingwang.blogspot.com/2013/03/solvedfastboot-wired-errors.html
Basically use these commands:
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash userdata userdata.img
fastboot flash recovery recovery.img
I know this post is late, but this worked for me
vitaminan said:
I used the fastboot command and updated every time when I bought nexus 7 (wifi) from last year.
However, when I updated from jwr66v to jwr66y, I used wipe function in CWM. Then, I got the "archive does not contain boot.sig" and "archive does not contain recovery.sig" and "failed to allocate XXXXXXX.byte"...
Then I tried to get back version to 4.2.2, but I also got the same error message. I follow the guidehttp://forum.xda-developers.com/showthread.php?t=1907796 to manual flash each .img files, the same problem occur at flashing system.img
At now, I could not get into android system, just hang on the "Google" logo.
I have read the same problem in another threadhttp://forum.xda-developers.com/showthread.php?t=1992063, but I could not have any idea to solve it?
Anyone have idea?
Thank you very much.
PS: I used the platform-tools r22.0.5
Click to expand...
Click to collapse
hi guys i need your help..I've flashed last flyme 5.0.10.0 G via TWRP but iìve forgot to replace in update.zip the recovery and bootloader img. Now my phone not have nothing recovery and the bootloader is again lock...Solutions?
You have to unlock the bootloader again. You can flash that daily update that let you unlock the bootloader from Flyme's file system explorer, IIRC.
Solitario88 said:
hi guys i need your help..I've flashed last flyme 5.0.10.0 G via TWRP but iìve forgot to replace in update.zip the recovery and bootloader img. Now my phone not have nothing recovery and the bootloader is again lock...Solutions?
Click to expand...
Click to collapse
No solutions exist :crying:
Really?? And the flash tool??
Inviato dal mio PRO 5 utilizzando Tapatalk
I am in the same situation. Unfortunately there is no way to get the token signed which is required to unlock the bootloader.
Sent from my SM-920F using Tapatalk
Solitario88 said:
Really?? And the flash tool??
Inviato dal mio PRO 5 utilizzando Tapatalk
Click to expand...
Click to collapse
With a Meizu phone, forgetting 1 or more steps in a modding procedure is equal to trash the phone. I'm really sorry
crime_of_heart said:
I am in the same situation. Unfortunately there is no way to get the token signed which is required to unlock the bootloader.
Sent from my SM-920F using Tapatalk
Click to expand...
Click to collapse
And for original recovery? This is big problem... However about the flash tool?? Work or not?
Inviato dal mio PRO 5 utilizzando Tapatalk
What I don't understand is how the recovery becomes corrupt.
If you flash the update.zip, the following gets updated:
bootloader on [sdb] [unlockable ONLY if on the 5.6.1.19.daily rom]
ldfw on [ldfw]
dtb on [dtb]
logo.bin on [bootlogo]
boot.img on [bootimg]
recovery.img on [recovery]
system.new.dat on [system]
The only way i see is if you flash a non-signed recovery after you flash the update.zip and then reboot.
Is this correct or do people have other experiences ?
st0rm77 said:
What I don't understand is how the recovery becomes corrupt.
If you flash the update.zip, the following gets updated:
bootloader on [sdb] [unlockable ONLY if on the 5.6.1.19.daily rom]
ldfw on [ldfw]
dtb on [dtb]
logo.bin on [bootlogo]
boot.img on [bootimg]
recovery.img on [recovery]
system.new.dat on [system]
The only way i see is if you flash a non-signed recovery after you flash the update.zip and then reboot.
Is this correct or do people have other experiences ?
Click to expand...
Click to collapse
Or get a tool to sign the recovery imge with correct key. The multitool exists but the key is missing to sign the file.
Sent from my SM-920F using Tapatalk
Solitario88 said:
Really?? And the flash tool??
Inviato dal mio PRO 5 utilizzando Tapatalk
Click to expand...
Click to collapse
Sign up (link)
the only way i see, u cannot lose recovery and get locked bl with normal update file, only if u deleted recovery and bl files from zip and forgot to put there your's. This is happens because before update, phone is deleting everything by the command in update.zip, in this case recovery gonna be deleted, but not reinstalled again. This is my opinion how it's gonna be.
that is impossible that you have no recovery in your phone.Try to enter the recovery by push the volume button.If it is not work,then try to enter the bootloader with the volume button and unlock the bootloader again.But in fact i am not sure if a special situation happend on your phone because this brand of phone is extremely weird.
afraid to loose recovery
st0rm77 said:
What I don't understand is how the recovery becomes corrupt.
If you flash the update.zip, the following gets updated:
bootloader on [sdb] [unlockable ONLY if on the 5.6.1.19.daily rom]
ldfw on [ldfw]
dtb on [dtb]
logo.bin on [bootlogo]
boot.img on [bootimg]
recovery.img on [recovery]
system.new.dat on [system]
The only way i see is if you flash a non-signed recovery after you flash the update.zip and then reboot.
Is this correct or do people have other experiences ?
Click to expand...
Click to collapse
Hello
I am afraid to loose recovery while flashing a new sock ROM...
In a stock image, should we really remove recovery.img OR replace it with your TWRP_3.0_m86_patched_st0rm77.img file to be sure to keep TWRP running ?
As said p82maarj
in https://forum.xda-developers.com/meizu-pro-5/development/recovery-twrp3-0m86patchedst0rm77-t3469296
Isn't it simplier to perform those steps in TWRP :
flash rom zip, flash unlocked bootloader zip and flash TWRP zip
Click to expand...
Click to collapse
?
Thanks in advance for your input.
EDIT : indeed all is well working smoothly without modifying the ROM if you flash the 3 zips in that order.
patco06 said:
Hello
I am afraid to loose recovery while flashing a new sock ROM...
In a stock image, should we really remove recovery.img OR replace it with your TWRP_3.0_m86_patched_st0rm77.img file to be sure to keep TWRP running ?
As said p82maarj
in https://forum.xda-developers.com/meizu-pro-5/development/recovery-twrp3-0m86patchedst0rm77-t3469296
Isn't it simplier to perform those steps in TWRP :
?
Thanks in advance for your input.
EDIT : indeed all is well working smoothly without modifying the ROM if you flash the 3 zips in that order.
Click to expand...
Click to collapse
IDK the best approach but If you replace recovery and end up with a locked boot loader twrp wont be booted. This can soft-brick your phone, esp if the stock image wont boot either.
Thankfully there is this ugly guide on here to restore the unlocked bootloader + recovery. Ugly because you have to install a 32 bit windows in vmware player, fully update that installation and then you can use the tools there to repair your phone.
Is it possible to extract a copy of a system image from an updated G4+? Like the boot.img, recovery.img, system.img, etc? To be flashed in fastboot
Yep. You have to flash TWRP and backup all img's. They'll appear with 'win' extension, so just change them to 'img'.
PocketGorgon said:
Is it possible to extract a copy of a system image from an updated G4+? Like the boot.img, recovery.img, system.img, etc? To be flashed in fastboot
Click to expand...
Click to collapse
Flashfire app has a fastboot compatible image backup feature.
I need the files to fix my g4