Very new to this stuff but have experimented in simple tweaking of the tf101
- I tried updating to 3.2 via the file uploaded from this thread" [UPDATE][WW] CWM Rooted Update to STOCK 8.6.5.7 from STOCK 8.4.4.11 WW only "
but I keep getting this error:
assert failed: apply_patch_check("/system/app/SystemUI.apk"
Error in /sdcard etc etc
(Status 7)
- please correct me if im wrong(cause maybe I am), the steps I did was:
access CWM (power, -volume then a quick +volume)
install zip from sd card/ choose zip from sd card . .. yes - Install 8.6.5.7_FOTA_WW_root_rec.zip
then after "Verifying Current System..."
i get
assert failed: apply_patch_check("/system/app/SystemUI.apk"
Error in /sdcard etc etc
(Status 7)
- just so you'd know, i changed the looks of my bar buttons from this thread" [MOD] Stock/Xoom bar buttons for 3.1 rom (8.4.4.5 - 8.4.4.11 - Prime 1.6) "
- but as per the instructions before updating to 3.2, I switched back to the stock buttons which were still included in the thread w/o problems . . did it a second time after my first fail of attempting to update to 3.2
Any ideas on how to fix this, w/o wiping my entire data is very much appreciated..
current build: ww 8.4.4.11-20110711
FOTA check EVERY files it update, so since your MOD changed SystemUI.apk. FOTA will not work for you. You need to be very very close to stock for any FOTA patch to work.
Wiping /data will have no effect. The SystemUI in on your /system partition.
The updated script will check all the sha1 hashes of the system apps that it patches to make sure that it is patching the right one. If these fail, then the patch fails, which means the update fails.
After the patches apply, reboot into recovery from the menu. It will flash the blob!
You can unzip the update, and edit the updater-script in META..com...google...android
You could probably keep the odex file if it isn't modded. There will be two references- one to check the patch and one to apply the patch. Delete them both. Zip it all back together, maybe sign it for good measure, then try flashing again. You might not need to sign, but it wouldn't hurt.
EDIT: Ohh, I'm not sure if CWM will finish the OTA. It will probably patch all the system files and then bomb on the blob because it tries to copy it to the staging partition, which isn't mounted. You might be able to mount it through adb, or you could mod CWM to mount it automatically
it worked! thanks!!
i updated the updater-script , maybe removed too much since im now getting a force close on the systemui.apk and currently dont have any home buttons.. bummer..
but i believe i could just push a 3.2 systemui.apk file from one of the forums here
currently at WW 8.6.5.7
3.2
btw, this is what i removed from the line:
assert(apply_patch_check("/system/app/SystemUI.apk", "b630f0a4f2d1c8e450f6269a997c950d11694ce9", "4cbd4f2cb3f4ba71d803f930b5a9c8f850bdda31"));
set_progress(0.397204);
overdid it, or under did it? i'll keep this as reference for the future
That will be OK. There is another line much further down that actually applies the patch. That is probably why you are getting FC's. The modded file was patched, but since it was modded, the patch probably corrupted it. Pushing a new version would probably work.
Sent from my T-Mobile G2 using XDA App
I have sbf'ed 3-5 times i have gone back to .29 then ota to .33 then used the .607 update.zip and it has failed many times with the same error assert failed Motorola.Update_Nv ... GB did boot up after it but it wont recognize camera leds and sd ... then i sbf'ed to .33 and then did the update and same error can some one help me ... it might be that the update.zip for 607 is corrupt any input is appreciated.
Try to re-download the update.zip or try with this: http://modmymobile.com/forums/663-m...3-gingerbread-leak-d2g-updated-4-5-607-a.html
thank you i will let you know how that goes after i get home from work.
Have the same issue... strange thing is that it was fine for most of the month then started rebooting randomly yesterday. SBFed and now I get that same error.
Sent from my DROID2 GLOBAL using xda premium
That error means it can't update the Version number and date for the firmware, radio and flex.
It is probably because the updater script is looking for a specific version number to update from.
I haven't run the yet but will take a look at the script. That is definitely the cause of the assert failure and the solution is to be on the correct build and radio.
Nope the update failed once again even with the new link to the update zip
More detailed error msg
BP Complete...
...............................assert failed: Motorola.update_nv("0001002f000000000000000c1fbf000000000042d00000")
E: error in /sdcard/update.zip
(status 7)
Installation aborted
---------- Post added at 05:04 AM ---------- Previous post was at 04:19 AM ----------
The problem was something corrupting the update.zip while putting it on the sd card... So i used a program called teracopy to move the files and it worked .. i used the test feature which verifies the files that are being copied
Hey, I've been working on rooting my continuum with the new froyo leak. Everything seems to be working just fine and then when I try to run cwm recovery it always has the following message: E:failed to open/sdcard/update.zip (No such file or directory) E: signature verification failed Installation aborted.
I've tried starting over, renaming the zip file, deleting it from the sd card and putting it back on again, nothing seems to work and I continue getting the same message. PLEASE HELP!
choltzem said:
Hey, I've been working on rooting my continuum with the new froyo leak. Everything seems to be working just fine and then when I try to run cwm recovery it always has the following message: E:failed to open/sdcard/update.zip (No such file or directory) E: signature verification failed Installation aborted.
I've tried starting over, renaming the zip file, deleting it from the sd card and putting it back on again, nothing seems to work and I continue getting the same message. PLEASE HELP!
Click to expand...
Click to collapse
Use "toggle signature verification" in CWM ?
Forever living in my Galaxy Ace using XDA App
I don't have CWM. That is what I'm trying to reboot into when the file keeps saying it doesn't exist.
I followed all of the directions exactly, but perhaps there is something that I should have done or had on my phone before attempting?
need help... I cannot apply any updates to my AT&T Atrix 2.
i keep getting this error
assert failed: motorola.steflash("/tmp/steflash")
Milenko2121 said:
need help... I cannot apply any updates to my AT&T Atrix 2.
i keep getting this error
assert failed: motorola.steflash("/tmp/steflash")
Click to expand...
Click to collapse
What update are you trying to install? OTA updates usually require a stock system, so if you've modded your system then you'll probably need to FXZ a clean setup. *Note - ICS has no offical FXZ and should use the appropriate resources according to the version you have.
If you post more info about what you have and what you're trying to achieve then I'm sure we'll be able to help you along.
I'm trying to flash the official AT&T ICS that released yesterday.
I was originally rooted with bootstrap on 2.3.6 with the Lithium Rom.
I unrooted the phone, flashed 2.3.6 with RSDLite to get a clean phone. This is when I tried the OTA which gives me that error.
I have tried multiple scripts here. I've used RSDLite and also the fastboot scripts to return to 2.3.5/2.3.6 from ICS(or GB) countless times.
I've never had this much trouble before.
has anyone had this issue? i can't even find anything about this on google.
well if this helps anyone at all.
I am flashing above 50% battery.
after RSDLite to 2.3.6 I still get this error, but it shows 2.3.6 just fine when I start up again.
When I do the update for ICS it does everything just fine all the way up until "updating STE BP"
this is where it gets held up and throws the error.
updating STE BP ..
assert failed: motorola.steflash("/tmp/steflash")
E:error in /cache/Blur_Version.55.13.25.MB865.ATT.en.US.zip
(Status 7)
Installation Aborted
I have tried the method of downloading it straight from OTA and also from copying the file from their website to my SD Card and installing this way.
Both methods result in the problem.
the exact method I have been doing is this.
I was originally on 2.3.6 rooted bootstrap on Lithium rom
I did the clean up method for bootstrap and then ran the unroot script.
Then used RSDLite to flash to 2.3.5 (tried straight to 2.3.6 as well)
when it reboots it still throws the error even for 2.3.5/6 steflash
I then do the OTA for ICS over WiFi which again throws the error.
I would extremely appreciate any possible help you guys could give.
UPDATE:
grabbed this from the log file. here is where the STEFLASH code starts.
Code:
Extracted file "/tmp/steflash/config.txt"
minzip: Extracted file "/tmp/steflash/cops_data.csd"
minzip: Extracted file "/tmp/steflash/flash_archive.zip"
minzip: Extracted file "/tmp/steflash/production_loader.ldr"
minzip: Extracted file "/tmp/steflash/prologue_loader.ldr"
Entered SteFlashFn()
updating devtree ...
Unmounted system image
updating STE BP ..
MID launched
Flashing timed out. killing mid(97); waiting for MID exit.
Flashing failed, MID exited;; retry.
MID launched
Got MfaResult signal with value fail
Flashing failed, MID exited;; retry.
MID launched
Got MfaResult signal with value fail
Flashing failed, MID exited;; retry.
script aborted: assert failed: motorola.steflash("/tmp/steflash")
assert failed: motorola.steflash("/tmp/steflash")
E:Error in /cache/Blur_Version.55.13.25.MB865.ATT.en.US.zip
(Status 7)
Installation aborted.
blk: partition "userdata" size 4961730560 not a multiple of io_buffer_size 524288
I:Set boot command ""
Anyone?
Sent from my MB865 using xda app-developers app
Milenko2121 said:
I'm trying to flash the official AT&T ICS that released yesterday.
I was originally rooted with bootstrap on 2.3.6 with the Lithium Rom.
I unrooted the phone, flashed 2.3.6 with RSDLite to get a clean phone. This is when I tried the OTA which gives me that error.
I have tried multiple scripts here. I've used RSDLite and also the fastboot scripts to return to 2.3.5/2.3.6 from ICS(or GB) countless times.
I've never had this much trouble before.
Click to expand...
Click to collapse
Milenko2121 said:
has anyone had this issue? i can't even find anything about this on google.
Click to expand...
Click to collapse
While I'd like to tell you that you searching on Google was the right approach, you have come up short because these things have been addressed countless times here on xda. So, anyone else reading this, please include "xda" in your Google searches. That will point you back here, whereas otherwise searching xda FROM xda yields less than satisfactory results at times.
You were on 2.3.6 and wanted to update to ICS, but you had the Atrix 2 Bootstrap app and likely CWM Recovery as well. That said, and if so, you have some file finding and deleting to do:
You will need to delete all the files associated with CWM and the Atrix 2 Bootstrap (if ever installed) via Root Explorer or ADB:
Removing Atrix 2 Bootstrap:
Delete file /system/bin/logwrapper
Delete file /system/bin/hijack
Rename file /system/bin/logwrapper.bin to /system/bin/logwrapper
Delete directory /preinstall/recovery (Note: This directory might not exist)
Since you also installed the recovery on boot you need to restore the following:
Removing Bootstrap Recovery on Boot:
Delete file /system/bin/mot_boot_mode
Rename file /system/bin/mot_boot_mode.bin to /system/bin/mot_boot_mode
Thanks jboxer
Sent from my rooted Mayan Calendar
Quick question before doing all that again.
Since I did the RSD flash, shouldn't it have made it stock and not require those steps?
Sent from my MB865 using xda app-developers app
Milenko2121 said:
Quick question before doing all that again.
Since I did the RSD flash, shouldn't it have made it stock and not require those steps?
Sent from my MB865 using xda app-developers app
Click to expand...
Click to collapse
has anyone solved this because if you flashed back to stock then i agree with you, you shouldnt need to delete these files
blackiceboi said:
has anyone solved this because if you flashed back to stock then i agree with you, you shouldnt need to delete these files
Click to expand...
Click to collapse
No, it doesn't work that way. Post number 8 details how to solve this issue. Simply flashing back to stock doesn't remove the files, and therefore they must be removed manually.
Brought to you by Carl's Jr.
Apex said:
While I'd like to tell you that you searching on Google was the right approach, you have come up short because these things have been addressed countless times here on xda. So, anyone else reading this, please include "xda" in your Google searches. That will point you back here, whereas otherwise searching xda FROM xda yields less than satisfactory results at times.
You were on 2.3.6 and wanted to update to ICS, but you had the Atrix 2 Bootstrap app and likely CWM Recovery as well. That said, and if so, you have some file finding and deleting to do:
You will need to delete all the files associated with CWM and the Atrix 2 Bootstrap (if ever installed) via Root Explorer or ADB:
Removing Atrix 2 Bootstrap:
Delete file /system/bin/logwrapper
Delete file /system/bin/hijack
Rename file /system/bin/logwrapper.bin to /system/bin/logwrapper
Delete directory /preinstall/recovery (Note: This directory might not exist)
Since you also installed the recovery on boot you need to restore the following:
Removing Bootstrap Recovery on Boot:
Delete file /system/bin/mot_boot_mode
Rename file /system/bin/mot_boot_mode.bin to /system/bin/mot_boot_mode
Thanks jboxer
Sent from my rooted Mayan Calendar
Click to expand...
Click to collapse
Does this work? I have the same problem..
jackdowsan said:
Does this work? I have the same problem..
Click to expand...
Click to collapse
Are you still on 2.3.6?
"Laughter is the best medicine, except for treating diarrhea."
Apex said:
Are you still on 2.3.6?
"Laughter is the best medicine, except for treating diarrhea."
Click to expand...
Click to collapse
Lol.. Great sig..
jackdowsan said:
Does this work? I have the same problem..
Click to expand...
Click to collapse
Apex's question.. Plus, do you have the hijack and .bin files? Are you rooted?
Sent from my MB865 using xda app-developers app
Apex said:
Are you still on 2.3.6?
"Laughter is the best medicine, except for treating diarrhea."
Click to expand...
Click to collapse
Hey bro you still visit these forums?Haven't seen you in here like forever.How've you been?
Sent from my MB865 using xda premium
Yea, I was on 2.3.6 and had /system/bin/logwrapper.bin but no hijack file or any other files you mentioned..
alteredlikeness said:
Lol.. Great sig..
Apex's question.. Plus, do you have the hijack and .bin files? Are you rooted?
Sent from my MB865 using xda app-developers app
Click to expand...
Click to collapse
yea, I was rooted, that was needed to change those bin files..after that, I fxz back to 2.3.6 stock again and hopefully this time the update will work ...
UPDATE: Again the same error
updating STE BP ..
assert failed :motorola.steflash("/tmp/steflash")
E:Error in /tmp/sideload/package.zip
(Status 7)
Installation aborted.
Should I have an unlocked boot-loader or something?
deveshmanish said:
Hey bro you still visit these forums?Haven't seen you in here like forever.How've you been?
Sent from my MB865 using xda premium
Click to expand...
Click to collapse
I'm doing well, thanks! Long time, so see is right! PM me when you get a chance.
jackdowsan said:
Yea, I was on 2.3.6 and had /system/bin/logwrapper.bin but no hijack file or any other files you mentioned..
yea, I was rooted, that was needed to change those bin files..after that, I fxz back to 2.3.6 stock again and hopefully this time the update will work ...
UPDATE: Again the same error
updating STE BP ..
assert failed :motorola.steflash("/tmp/steflash")
E:Error in /tmp/sideload/package.zip
(Status 7)
Installation aborted.
Should I have an unlocked boot-loader or something?
Click to expand...
Click to collapse
The bootloader is locked up tighter than a 16th Century King's daughter's chastity belt, so don't worry about that being an issue. Are you using Root Explorer to delete and rename the appropriate files? Also, you say you've already tried to use the above steps, then used the FXZ back to stock 2.3.6 and you still can't get the Moto Server update, correct?
"Laughter is the best medicine, except for treating diarrhea."
Apex said:
I'm doing well, thanks! Long time, so see is right! PM me when you get a chance.
The bootloader is locked up tighter than a 16th Century King's daughter's chastity belt, so don't worry about that being an issue. Are you using Root Explorer to delete and rename the appropriate files? Also, you say you've already tried to use the above steps, then used the FXZ back to stock 2.3.6 and you still can't get the Moto Server update, correct?
"Laughter is the best medicine, except for treating diarrhea."
Click to expand...
Click to collapse
Yea, I used root explorer to rename and delete files..and yea, even after these and fxz back to stock 2.3.6 I still cant get the update to work. Also, weird thing is it shows no IMEI, no baseband and is always stuck in Airplane mode.
jackdowsan said:
Yea, I used root explorer to rename and delete files..and yea, even after these and fxz back to stock 2.3.6 I still cant get the update to work. Also, weird thing is it shows no IMEI, no baseband and is always stuck in Airplane mode.
Click to expand...
Click to collapse
Were you able to verify that the Atrix 2 Bootstrapper files and the Bootstrap Recovery on Boot files were in fact deleted and renamed correctly? Also, which FXZ file did you use in RSDLite?
"Laughter is the best medicine, except for treating diarrhea."
Hi,
Today I've seen this post "http://forum.xda-developers.com/galaxy-s3-mini/orig-development/rom-omnirom-gt-i8190-s3-mini-t2969867"
and really interested to install it in my mobile. But unfortunately, there is some error, I'm facing. :/ Hope someone will help..
Whenever I choose the ROM file and install:
Code:
Updating partition details...
Installing '/External_sd/omni-5.1.1-20150816-golden......
checking for MD5 file...
Skipping MD5 check: no md5 file found
Apply parsedPerms: removexattr of /system/bin/bac..
set_metadate: some changes failed
E:Error executing updater binary in zip '/external
updating partition details...
Hope someone help ASAP. :/
[Fixed] Just flashed the official Samsung stock again by Odin. All okay now..
Yay.. ;D Currently, Installing Omni's Lollipop custom rom. ;D
Glad everything worked out for you.
Thread closed.