Related
I'm trying to put together an update to apply changes to generic android 2.2 tablet. Every time I try to apply the update.zip file I get "E:signature verification failed" I have tried many signing tools but that doesn't seems to work.
Can anyone explains to me the basics of signing?
Is signing relative to every device (maybe use same signature that is compatible with the device)
Does the device have to be rooted?
Do I need to set permission within script for files/folders applying to?
Does signing method changes depending on android version (i.e 2.1, 2.2, 2.2.1, or 2.3)
I'm totally confused and would greatly appreciate any hint/ advice
I have tried Update-zip-Packager and seems to make some progress, still having issues through.. Well, now I'm not getting the e:signature verification failed, however, I'm getting the following:
-- Install from sdcard...
Finding update package...
Opening update package...
Verifying update package...
Installing update...
Installation aborted.
Not sure if anyone is reading this, but any idea how to troubleshoot this issue?
Thanks!
Very nice thanks
This is the Stock 8.6.5.13 US update repackaged with:
* Clockworkmod support (It does not include CWM, but doesn't reflash the recovery partition either)
* Rooted (includes SuperUser.apk & su 3.0.0)
* Busybox (1.19.2)
This update worked fine on my TF101. I built it using the same method Roach2010 used to make his previous CWM-repacks so it should be ok. I have only tested this on my own tf101. Let us know when it works for yours too!
This will not work unless you have:
1. clockworkmod
2. STOCK firmware (root is fine)
3. the US or WW firmware
4. firmware 8.6.5.9
If this update will not apply, take note of which assert stopped the process. You probably applied some sort of mod to your transformer.
There was an issue in the initial release. If you downloaded it, delete it and download the new one.
CWM package for ASUS FOTA Update 8.6.5.13 US
http://bellybuttonporn.com/android/transformer/kwt-cwm-8.6.5.13-proper.zip
Problems updating? Customized Transformer? Try the Update checker.
http://bellybuttonporn.com/android/transformer/kwt-cwm-8.6.5.13-checker.zip US
The Update checker will verify all of the same files that the update verifies. It will not stop on the first error. This way, you can see ALL the files which will cause errors and fix them all at once without the tedious reboot / try update / reboot / fix problem / reboot / try update loop.
Courtesy of brk:
CWM package for ASUS FOTA Update 8.6.5.13 WW (with root and CWM recovery)
http://www.multiupload.com/KTGLKFJME5
Has this been tested yet??
Thanks
*Offtopic*
delete ffs
same here, stock but with xoom system UI and bloatware deleted.
Sorry, in my haste I didn't update the recovery binary.
Fixed version in testing now.
Updated first post, new zip is available here:
http://bellybuttonporn.com/transformer/kwt-cwm-8.6.5.13-proper.zip
cky2000 said:
for me, it did not work.
I tried from a fresh/clean install (nvflash) of US_epad-user-8.6.5.9. and got this error in CWM:
assert fail: getprop ("ro.product.device") == "EeePad" || getprop ("ro.product.device") "EeePad"
E:Error in /sdcard/kwt-cwm-8.6.13.zip
(Status 7)
Installation aborted.
bellybuttonporn
Click to expand...
Click to collapse
Seems you didn't edit the update-script to remove that check. Either way let me know how it goes. I made myself an cwm zip that I used to update my TF this afternoon. I didn't bother to add in SU seeing as though the update is just a patch and the TF should already be rooted.
@daoist If your new update.zip doesn't work let me know I'll upload mines and you can post it.
Hi,
I am still pretty new to all of this, I have rooted my TF, right now I have a US ver 8.6.5.9 rooted with CWM and I am getting the notification to update firmware.
Is this the file I need to update my TF and keep root, it looks to me like it is but I am not 100% sure, also I am not sure how to apply the patch.
To apply this do I use CWM? The step[s I think I need to do is
1. copy the file top my SD card,
2. Boot to CWM
3. choose install zip
4. pick the zip downloaded from this thread
5. then watch and make sure works, then reboot
OH, I have the netflix patch (libnvomx) file copied over the original in my TF, should I put the original back before trying ng this?
Is this correct?
thanks for any help and the file!!
John
Cordy said:
Seems you didn't edit the update-script to remove that check. Either way let me know how it goes. I made myself an cwm zip that I used to update my TF this afternoon. I didn't bother to add in SU seeing as though the update is just a patch and the TF should already be rooted.
@daoist If your new update.zip doesn't work let me know I'll upload mines and you can post it.
Click to expand...
Click to collapse
You referring to the check that goes through and looks for mods and missing apps? Is it possible someone could upload a version that doesnt run that check? I replaced SustemUI and basically deleted everything I didnt need (and didnt back up individual files, just made a full backup) so it would take me a while to track down all of the APKs.
If I recall someone posted the .9 update without the check for the existing apps.
EDIT: I actually found a backup for my stock apps and copied all of them back over and its still failing. AWS.odex, first one (and its installed).
Xerravon said:
Hi,
I am still pretty new to all of this, I have rooted my TF, right now I have a US ver 8.6.5.9 rooted with CWM and I am getting the notification to update firmware.
Is this the file I need to update my TF and keep root, it looks to me like it is but I am not 100% sure, also I am not sure how to apply the patch.
To apply this do I use CWM? The step[s I think I need to do is
1. copy the file top my SD card,
2. Boot to CWM
3. choose install zip
4. pick the zip downloaded from this thread
5. then watch and make sure works, then reboot
OH, I have the netflix patch (libnvomx) file copied over the original in my TF, should I put the original back before trying ng this?
Is this correct?
thanks for any help and the file!!
John
Click to expand...
Click to collapse
Yep, that's correct.
One note is because of how the TF handles storage, you want this in your /Removable/microSD. If you put it in /sdcard it's not actually in your sdcard.
When you reboot into CWM make sure to choose to pick a file from your sdcard, rather than just applying update.zip (in case you didn't actually name it update.zip)
ryan stewart said:
You referring to the check that goes through and looks for mods and missing apps? Is it possible someone could upload a version that doesnt run that check? I replaced SustemUI and basically deleted everything I didnt need (and didnt back up individual files, just made a full backup) so it would take me a while to track down all of the APKs.
If I recall someone posted the .9 update without the check for the existing apps.
EDIT: I actually found a backup for my stock apps and copied all of them back over and its still failing. AWS.odex, first one (and its installed).
Click to expand...
Click to collapse
The problem with removing the check is that this update is doing patching, rather than replacing files.
If you're just replacing files, you can skip the checks and it will work fine.
If you're patching files, if you skip the check, the patching process will not work (best case scenario). will leave your system in a quasi-updated state (middle case), or destroy the target file (worst case).
Maybe someone who's still on 8.5.6.9 can post their AWS.odex file for you to copy onto your device?
The issue is I have it back on my device, I found it, and the update is still hanging on that.
daoist said:
Yep, that's correct.
One note is because of how the TF handles storage, you want this in your /Removable/microSD. If you put it in /sdcard it's not actually in your sdcard.
When you reboot into CWM make sure to choose to pick a file from your sdcard, rather than just applying update.zip (in case you didn't actually name it update.zip)
Click to expand...
Click to collapse
Hi,
Thanks for the help! It worked like a charm, no problems at all.
I am wondering now, do I need to update my CWM recovery, or do I just leave it how it is?
thanks for the file and help!!!
Now I just have to figure out how to get rid of the notification...
Has anyone noticed the web browser performance? Is it still checkerboard on display? Where it displays the page in chunks... and is this android 3.2.1? or just firmware update?
Worked fine on mine, Thx.
daoist said:
The problem with removing the check is that this update is doing patching, rather than replacing files.
If you're just replacing files, you can skip the checks and it will work fine.
If you're patching files, if you skip the check, the patching process will not work (best case scenario). will leave your system in a quasi-updated state (middle case), or destroy the target file (worst case).
Maybe someone who's still on 8.5.6.9 can post their AWS.odex file for you to copy onto your device?
Click to expand...
Click to collapse
Would it be possible to remove the check and the patch? I am looking at the updater script, what I would love is to just remove its check and attempt at patching the bloatware.
For Example, the Check:
assert(apply_patch_check("/system/app/Finsky.apk", "19a70336522820f20a9e1d9f065ae56a714aa7cf", "690dc80af4303cb2df1991de9d52c269211e1dcf"));
set_progress(0.116486);
assert(apply_patch_check("/system/app/Finsky.odex", "fda5fbff54fc6c35b9210afd4a3b76b6a8862d83", "59412510a7d0a789b1e732dbffdc9feb3245e964"));
set_progress(0.119390);
And the Update:
apply_patch("/system/app/Finsky.apk", "-",
19a70336522820f20a9e1d9f065ae56a714aa7cf, 1070527,
690dc80af4303cb2df1991de9d52c269211e1dcf, package_extract_file("patch/system/app/Finsky.apk.p"));
set_progress(0.135043);
apply_patch("/system/app/Finsky.odex", "-",
fda5fbff54fc6c35b9210afd4a3b76b6a8862d83, 655760,
59412510a7d0a789b1e732dbffdc9feb3245e964, package_extract_file("patch/system/app/Finsky.odex.p"));
set_progress(0.138224);
If I didnt want it to update finksy (bad example but just one I grabbed) could I just delete everything above from the script? In the case of something like Zinio I dont even want the update since I nixed the underlying app.
I actually tried something like that but it failed immediately, no error. Im wondering if I havent zipped it up right.
Yeah, if you search through the update script for the name of the file that's erroring out, there's 2 places. First the assert, then the patch. Get rid of both and you're fine.
I'd google what those files are before you remove them from the script, just to be safe.
Just for example, Finsky is part of Market
Im wondering if there is something I am doing wrong or if there is a trick to zipping it back up. I tried removing those lines (for AWS, not Finsky ) and the update failed without an error (just aborted).
Im wondering, should I be leaving that set progress, zipping using a particular method?
The biggest problem I had was making sure the files were saved with unix line-endings. If you edited it in notepad or something like that it may have defaulted to windows line-endings.
Hi can you add this to 1st post:
CWM package for ASUS FOTA Update 8.6.5.13 WW
(with root and CWM recovery)
http://www.multiupload.com/KTGLKFJME5
If it gives you an error about some file check, edit update script and put a "#" before the line of that file.
So my sister just bought a Transformer tonight, It has never been rooted or anything.
It will not detect any updates on the "search for update" OTA thing.
I also downloaded the ICS firmware directly from Asus's website, extracted it on a microSD card, and the trasnformer still doesnt show theres any update.
In the manual update guide it says put the extracted ASUS folder on the SD card, however there is no ASUS folder in the update downloaded from their site.
No idea whats going on.
Any help is appreciated.
Did you unzipped the file you download from Asus website? You can't leave it whole, there's another zip inside that zip.
Yep I followed all the instructions
Bawb3 said:
In the manual update guide it says put the extracted ASUS folder on the SD card, however there is no ASUS folder in the update downloaded from their site.
Click to expand...
Click to collapse
Reading that gives me the feeling that you probably didn't do it right. There is no reason it won't work.
Can you post the EXACT steps you took?
I'm having the same issue
There is no ASUS directory in the zip.
Inside the second zip there is a file called blob and a directory called Meta-Inf with a bunch if files in.
Okay, I go to asus's tf101 site, download sectiion > firmware.
Download the US SKU 4.0.3 firmware update which is ~300mb
Extract that zip which yields a file with another ZIP inside of it. There is no ASUS folder.
Like the above poster said, the second zip file looks like a recovery update script that you would flash in CWM with a meta-inf with the signatures, and a blob file.
EDIT[SOLVED]:
Okay I figured it out. I downloaded the 3.2.1 update from asus, which does have the ASUS folder. This one worked and launched the update wizard.
It seems that the update wizard looks for the directory /ASUS/Update/US_epad-user-x.x.x.xx.zip file on the root of the microSd card.
So I put the ICS update which is US_epad-user-9.2.1.11.zip into the ASUS/Update/ Directory in the microSD card that I initially extracted from the 3.2 update. Sure it enough it launched the update wizard and allowed me to select that file for the update.
ASUS Didnt properly upload the ICS update it seems.
I still dont know why the OTA didnt acknowledge an update.
OK, this is just getting dumb now.
OK, this is just getting really really stupid now. ASUS I AM SERIOUSLY STARTING TO HATE YOU.
OK I have done the following across MULTIPLE reboots and really getting ticked off now. This would NOT be an issue if the recovery mode didn't give me a damned green droid with yellow triangle with ! in the middle of it.
I have:
Way 1
-------
1 - Extracted WW_epad-user-9.2.1.11.zip from the original WW_epaduser9_2_1_11UpdateLauncher.zip from ASUS site.
2 - Copied extracted WW_epad-user-9.2.1.11.zip to EP101_SDUPDATE.zip
3 - Put both zips on root of microSD. Failed. Tried with copy on /sdcard/ as well, both with and without leaving the original 2 on the microSD.
Way 2
-------
Extracted the WW zip both to the / of the tablet and to the root of the microSD, trying both with and without leaving the originals on the microSD.
Way 3
-------
Same exact as Way 1 and Way 2 but with removing the .zip extension from both files, and with swapping removal of the extension between the 2 files on both the tablet and the microSD.
Way 4
-------
Tried all permutations of Way 1, 2, and 3 with both 8.6.5.21 and 8.6.6.21.
NONE of these ways worked.
I grabbed NVFLASH with 8.6.5.13 and that flashed just fine, except that the recovery mode is still giving me the triangular ! droid image.
I absolutely positively can not root or otherwise do anything to this tablet.
The tablet is a ASUS 32GB Transformer HD Tablet (Serial #: B50KAS#####) with a 2GB microSD formatted with FAT32. (I've tried formatting NTFS and FAT32) This is not a Prime! This is the original Transformer!
I even found an article for how to create your own and tried that as well!.
(Wow really guys? You can't post outside links?? Really? What the heck is that retardation supposed to prevent? I mean really!)
All I get for that mess is the USB connection is dropped even before NVFLASH can do anything. I have Windows 7 Ultimate, Mac OS X Lion, and several distributions of Linux (ArchLinux, Ubuntu, CentOS, Debian, and OpenSUSE). I've tried on them all!! This has been a great many hours trying to figure this out, searching like crazy through these forums. (Incidently, the 10 posts requirement in order to post in the 'experienced' area is just nuts.)
I even tried both the renaming WW portion of the zip name to US as described in other areas in this forum and it still failed! I'm a programmer by trade, and I have never run up against something as stubborn as this! The recovery mode is what is breaking all of this. I absolutely can not get a stable, working recovery mode on this tablet! Heck, I'd be happy with the stock 8.6.5.21 on here or ICS (the 9.2.1.11) without ever again attempting to root the pup! Can anyone assist in getting the recovery mode back to normal? Is there a way to use NVFLASH to write the original recovery mode back such that I stop getting that dang Droid With Yellow ! Triangle image?
Do you have CWM Recovery installed? If so, it will not do the OTA updates, but you can just go into CWM Recovery and then choose the 9.2.1.11 firmware and when it is done flashing, you will have an unrooted stock ICS (with stock recovery).
CWM
Unable to root. RazorClaw tells me I'm missing the required file (though it doesn't tell me what file that its) and says Too bad!
deryldoucette said:
Unable to root. RazorClaw tells me I'm missing the required file (though it doesn't tell me what file that its) and says Too bad!
Click to expand...
Click to collapse
Razorclaw only works on 8.6.5.19.
Not certain on which version you try to run razorclaw.
use Vipermod on 8.6.5.21 or higher.
was 8.6.5.13 which is what i was able to nvflash back to the tablet. Do you know if there is a more recent nvflash packaged 8.6? Looking to see if I can at least put 8.6.5.21 on here. Currently still running the 8.6.5.13
Mine also wont OTA, i have put the downloads in ASUS/Update and nothing... does not detect updates.
Just bought my tf101 yesterday, same problem. Called support and they told me the update was not pushed to my device yet and a manual update would probably fail.how long ago was ics released?
found it, february 24th... It should be pushed to my device by now, right?
Sent from my SPH-D700 using XDA
G'day guys,
I finally managed to get it to work for me!
TLDR Version - I have the US build version - this may or may not be relevant to these instructions:
* Use "App Backup" to backup all your apps and/or data (optional)
* Factory reset
* Choose "English (US)" from the initial setup wizard and default options for the rest (skip wifi setup)
* Plug the transformer in to your PC via USB
* Create the following folder structure exactly (including case!)
<Internal Storage>\ASUS\Update
* Copy US_epad-user-9.2.1.11.zip that you extracted from US_epaduser9_2_1_11UpdateLauncher.zip to "<Internal Storage>\ASUS\Update"
* Reboot Transformer
* Choose the triangle from the notification area
* TF should update successfully!
Long version:
I followed the instructions in this thread but still wasn't having any luck.
I don't have an external SD card so I was copying the zip from the downloaded file to internal storage\Asus\Update. The triangle was appearing in the bottom right but when I went to do the update it would reboot to the android man with an "!" on his chest. I then tried a factory reset and then recopied the update and tried again. Same "!" dude. I tried another reset but did two things different and it then worked! Instead of choosing "English (UK)" on the initial setup wizard (I'm from Aus) I chose "English (US)" (just a wild guess given its US update required for my TF. The other thing that I did differently was located the update at "ASUS\Update". Note the capitalisation of "ASUS" where previously I was using Asus. I had this idea when I noticed the first time I had both "Asus" and "ASUS" folders there simulataneously. So one or both of those things made it work for me!
If these tips worked for you please post your success (or otherwise even).
Best of luck!
Make sure you are using CWM version 6.0.1.0
I am not responsible for whatever happens to your device because everyone else puts this in their threads too! get over it
Be sure to click that Thanks button if this helped you. this also appears in everyone else's thread's! deal with it
1. download the update file for your region from paugustin's thread here:
http://forum.xda-developers.com/showthread.php?t=1720157
2. unzip it inside any folder.
3. open the file called updater-script which is located at:
/META-INF/com/google/android
4. delete the line and the blank space left afterwards then save changes to the file. the line for the US version looks like this:
assert(getprop("ro.product.name") == "a700_pa_cus1");
5. highlight everything that came out of the download from step 1, zip it, and rename it to update.zip
6. place in the root of an SD card, not internal storage!
Note: a few users have recommended placing the update.zip on internal storage. i tried it again from a SD card and it worked just fine. if you're having issues with this try internal.
7. reboot to recovery mode. if you need this guide you've had to do it in the past, nuff said! :silly:
8. select Apply update.zip
9. after you select Reboot System, you will be given two options:
Yes will keep CWM recovery but you wont be able to use recovery mode at all until you unlock the bootloader again!
No will allow the update to restore stock recovery, and you will need to re-flash CWM.
10. if you chose Yes from step 9, unlock your bootloader and do the root process again. DONE!
if you chose No, unlock your bootloader, flash CWM again, and do the root process again. DONE!
there are already guides on how to do that.
BONUS FOR USA TAB OWNERS!
This is ONLY FOR UPDATING FROM the Acer_A700_AV043.RV00RC00_AV043.RV07RC06_PA_CUS1.zip file from the link in Step 1 at the top of the page.
If you are on any other version, and / or from any other country, DO NOT TRY THIS!
This is the latest update with the power option added in settings & touch sensitivity improvements, with the getprop line already deleted from the script!
A. Download this directly to your tab.
B. Reboot to recovery mode.
C. Install.
D. After selecting Reboot System you will be given two options. Refer to Step 9 above.
E. After making your choice, you will be given the option to prevent the update from deleting root :victory:
F. Unlock your bootloader again.
G. If you chose No. from Step 9, re-flash CWM 6.0.1.0
H. If you chose No. from Step E, root again if you wish.
DONE!!
I've try this, but when I do point 8 (select Apply update.zip), the update is aborded.
I'm on SDs_Acer_AV043_A700_RV07RC06_EMEA_FR.zip with the root by patched boot.
I want install Acer_A700_AV043.RV07RC06_AV043.RV23RC04_EMEA_FR.zip.
I don't know why update fail.
imtheyoyo said:
I've try this, but when I do point 8 (select Apply update.zip), the update is aborded.
I'm on SDs_Acer_AV043_A700_RV07RC06_EMEA_FR.zip with the root by patched boot.
I want install Acer_A700_AV043.RV07RC06_AV043.RV23RC04_EMEA_FR.zip.
I don't know why update fail.
Click to expand...
Click to collapse
i think i know why.
i revised step 5, check it out
That's what I had done, zip and rename in update.zip.
imtheyoyo said:
That's what I had done, zip and rename in update.zip.
Click to expand...
Click to collapse
hmm... did you put it on an sd card?
and what error is it giving you?
Sterist said:
hmm... did you put it on an sd card?
and what error is it giving you?
Click to expand...
Click to collapse
Yes, and the message was "Update aborted"
Just a question. I have unlocked my A700 via method 2, so without CWM install.
If I follow this guide, placing the update.zip on the card, and restart with Volume-down+Power, will it execute the update.zip as well?
The update.zip in fact is the altered Acer_A700_AV043.RV07RC04_AV043.RV23RC05_WW_GEN1.zip according to the instructions.
If using Root Explorer, where would I have to place the update.zip file?
---------- Post added at 10:57 PM ---------- Previous post was at 10:52 PM ----------
CheopsChefren said:
Just a question. I have unlocked my A700 via method 2, so without CWM install.
If I follow this guide, placing the update.zip on the card, and restart with Volume-down+Power, will it execute the update.zip as well?
The update.zip in fact is the altered Acer_A700_AV043.RV07RC04_AV043.RV23RC05_WW_GEN1.zip according to the instructions.
If using Root Explorer, where would I have to place the update.zip file?
Click to expand...
Click to collapse
Thanks for any advice.
CheopsChefren said:
Just a question. I have unlocked my A700 via method 2, so without CWM install.
If I follow this guide, placing the update.zip on the card, and restart with Volume-down+Power, will it execute the update.zip as well?
The update.zip in fact is the altered Acer_A700_AV043.RV07RC04_AV043.RV23RC05_WW_GEN1.zip according to the instructions.
If using Root Explorer, where would I have to place the update.zip file?
Click to expand...
Click to collapse
I'm not sure if a modified update script would run on the stock recovery. you can try it, the worst that would happen is it will decline to run the update. i would recommend you always have CWM recovery regardless of any flashing/updating plans you may or may not have.
and the location for the update.zip does not change regardless of what you use to get the file there lol it doesn't matter if you use a Toyota or Lamborghini to get to work. silly question lol..
Thanks for your answer. The problem is, an unmodified update script wont run either on my unlocked A700.
And, I am scared about using CWM, as I hear stories it will possibly brick your A700, and that is something I am not too keen about.
But, with Root Explorer compared to ES File Explorer you have more possibilities. But I agree, it was abit a silly question.
So now, how to update my unlocked A700 with the OTA delivered by Acer? That's the question.....
CheopsChefren said:
Thanks for your answer. The problem is, an unmodified update script wont run either on my unlocked A700.
And, I am scared about using CWM, as I hear stories it will possibly brick your A700, and that is something I am not too keen about.
But, with Root Explorer compared to ES File Explorer you have more possibilities. But I agree, it was abit a silly question.
So now, how to update my unlocked A700 with the OTA delivered by Acer? That's the question.....
Click to expand...
Click to collapse
by my understanding, the CWM versions to avoid are 5.4.0.0 (something like that) and the touch version(s)
unlocking your bootloader and not installing CWM is like alcohol-free-beer... pointless.
When trying the above mentioned procedure, i first got an error 6, which i solved by editing the updater-script the second time with notepad++, so i could keep the unix-like line-ends.
Then when i tried to run the update.zip from within cwm, i got error status 7.
(On both the downloaded update file from the thread mentioned above, and from the original from Acer received OTA update file)
As far as i know, after googling error status 7 has to do with the update zip not for the system trying to update. But i am sure, as i also tried with the Acer received OTA (after deleting the first line in the updater-script), i used the correct update file.
What could cause this?
Hi. Link for U.S. tab owners (www.sendspace.com) is dead. Can you post again?
eman01 said:
Hi. Link for U.S. tab owners (www.sendspace.com) is dead. Can you post again?
Click to expand...
Click to collapse
LOL stupid mistake on my part
the link wasn't really dead, i just screwed up in how i posting it lol thanks for mentioningit
Got it. Thanks.
OK. I finally tried above method to update rooted U.S. A700.
Started with:
Image Acer_AV043_A700_RV07RC06_PA_CUS1
Build Acer_AV043_A700_1.029.00_PA_CUS1
CWM Recovery 6.0.1.1
I tried both methods above- initially using the update.zip specifically provided for U.S. A700 owners in the 2nd part of 1st post of this thread
IN "BONUS FOR USA TAB OWNERS!".
Tried it on 1st external SD, then internal SD.
Both ways I get RED TRIANGLE with exclamation point and message:
"Can't open /sdcard/update.zip
(bad)"
OR
"Can't open /emmc/update.zip
(bad)"
I am, of course, sure I copied the update.zip directly from Downloads to the root of the external and internal cards;
I also made sure to use "Choose zip from SD card" in CWM to find the Update.zip file right where I put it.
Not ready to quit, I tried again using the original Update zip file and modifying updater.script myself, exactly as described in the 1st part of the 1st post. I also tried this update.zip with modified updater.script on both the external and internal SD, without success.
This time I did get further, receiving:
Finding update package...
Opening update package...
Installing update...
Mount Data success
Verifying current system...
assert failed: apply_patch_check_("EMMC:\dev\block\platform\sdhci-tegra.3/by-name/LNX:4065536:95
Then a bunch of letters/numbers
E:Error in sdcard/update.zip
(Status 7)
Installation aborted.
P.S. I verified I have the assert line deleted in the updater.script before I tried this.
I should mention that I have stock ROM, have and have NOT deleted any system apps
(I have inactivated a few like VirusScan within Android).
Luckily I was able to reboot without any problems after all these attempts, but now I am stuck.
Any ideas?
hmmm that's an error i haven't seen before. try deleting the update and downloading it again, or disabling assert check
I'm not a developer, that's the best i can suggest. you'd have to ask someone with a bit more knowledge
it might have something to do with the root method you used originally
Well, I tried yIur modified update.zip multiple times (downloaded it 3 different times, and tried both internal and external SD). As mentioned, I also tried modifying the updater.script myself (used JOTA text editor; maybe that was an issue with respect to how it saves a file, etc.).
How does one disable assert check, as you describe? A link, perhaps?
Interestingly, today I was able to flash the original1.029 update (1st A700 OTA update) after modifying it's updater.script in exactly the same fashion you describe. It put me back to stock 1.029, which I then updated to stock 1.057 (2nd A700 OTA update). I then re-unlocked bootloader, re-rooted and re-installed CWM recovery 6.0.1.1 easily and successfully as described in the threads in A700 development in this forum. Still holding out on CM ROM, as it seems fairly buggy. Thanks for trying. My way definitely took longer; don't know why your direct method would not work on my tab. Thanks.
disable asset check should be one of about 4 or 5 options to choose from, right next to ''choose from internal'' / external
it actually might not be available on this device it's been a while since I've used CWM
i do these modifications right from my tab with ES file explorer.
glad you were able to get it working
[solved] US A700 rooted OTA update
hi all,
after few days of messing about I finally managed to update a rooted US A700. I will try to guide you through what I did.
After initially booting up the A700 I upgraded it OTA to AV043_A700_RV07RC06_PA_CUS1 and after that rooted it using method #2 in the rooting thread (method #1 didn't work for some reason)
Got OTA notification saying that AV043.RV23RC03_PA_CUS1 was available (performance update, 35.72MB in size) but that wouldn't install giving error Status 7.
Installed CWM 6.1.1, still tthe same results, it wouldn't even install any of the other ROM's that are posted in this forum.
I probably should mention that I saved the original OTA update for installation later.
here is the solution (at least in my case)
Downloaded ROM Acer_A700_AV043.RV00RC00_AV043.RV07RC06_PA_CUS1.zi p from http://forum.xda-developers.com/showthread.php?t=1720157
Extracted boot.img and flashed via fastboot flash boot boot.img
Rebooted into CWM recovery and flashed the earlier saved OTA update no problem (was saved on internal memory but external memory card should work as well)
Then all that needed to be done was to root the A700 again (I used method #2 again)
Hope that helps someone.
eman01 said:
OK. I finally tried above method to update rooted U.S. A700.
assert failed: apply_patch_check_("EMMC:\dev\block\platform\sdhci-tegra.3/by-name/LNX:4065536:95
Then a bunch of letters/numbers
E:Error in sdcard/update.zip
(Status 7)
Installation aborted.
Any ideas?
Click to expand...
Click to collapse
You are not using the original bootloader so checking failed.
Simply delete this line to fix it (it happened to me last week when I created my homemade OTA update). Don't forget to unlock your bootloader after that !
Hello,
After about 4 hours of searching and trying different solutions, I give up.
I tried to update to 38R from 33R with the official OTA update. *** last log attached..
The install process mainly failed by wrong or missing .apk files, in my case - install failed for "hexoIcons.apk" and after I fixed this by copying the relevant file into '/system/app/' (I rooted the device for this), install failed with "hexo.apk", which I unable to fix (although I copied It and install the package).
Some solutions that I tried:
1. Root the device and install downloaded 38R rom with sideloader.
2. Factory reset and wipe cache/delvik, and try to update with OTA.
3. Copy mentioned above files to '/system/app'
I think that the problem is this
Code:
script aborted: assert failed: apply_patch_check("/system/app/Hexo.apk","f39cdfa05609ea66c26e61ce28eec3eb574cca67","ee4695449d527f03e618fa8784522a008fba96a3")
assert failed: apply_patch_check("/system/app/Hexo.apk","f39cdfa05609ea66c26e61ce28eec3eb574cca67","ee4695449d527f03e618fa8784522a008fba96a3")
No success this far.
Thank you for you time and effort!
Little info about me:
I am a programmer (although not an Android one)
I have a general knowledge about Android and Cyanogen (installed it before on my previous HTC device)
ur92 said:
Hello,
After about 4 hours of searching and trying different solutions, I give up.
I tried to update to 38R from 33R with the official OTA update. *** last log attached..
The install process mainly failed by wrong or missing .apk files, in my case - install failed for "hexoIcons.apk" and after I fixed this by copying the relevant file into '/system/app/' (I rooted the device for this), install failed with "hexo.apk", which I unable to fix (although I copied It and install the package).
Some solutions that I tried:
1. Root the device and install downloaded 38R rom with sideloader.
2. Factory reset and wipe cache/delvik, and try to update with OTA.
3. Copy mentioned above files to '/system/app'
I think that the problem is this
Code:
script aborted: assert failed: apply_patch_check("/system/app/Hexo.apk","f39cdfa05609ea66c26e61ce28eec3eb574cca67","ee4695449d527f03e618fa8784522a008fba96a3")
assert failed: apply_patch_check("/system/app/Hexo.apk","f39cdfa05609ea66c26e61ce28eec3eb574cca67","ee4695449d527f03e618fa8784522a008fba96a3")
No success this far.
Thank you for you time and effort!
Little info about me:
I am a programmer (although not an Android one)
I have a general knowledge about Android and Cyanogen (installed it before on my previous HTC device)
Click to expand...
Click to collapse
Have you giving the APK the right permissions ?
What's your end goal? Do you want to stick with the 38R build once it flashes successfully or do you want to update all the way to 05Q (or another particular build)? Your best option is to flash the stock images using fastboot. You can find the stock images for all builds in my OnePlus One index thread here:
[INDEX] OnePlus One Resources Compilation Roll-Up
(look in the stock images & ota section)
And I have detailed instructions on how to flash the stock images in section 8 of my guide thread:
[GUIDES][Q&A]How-To Guides For Beginners + Q&A
Permission
jamal2367 said:
Have you giving the APK the right permissions ?
Click to expand...
Click to collapse
Thanks but I granted similar permission to the new .apk files that I added.
I also tried to grant full -rw-rw-rw permission. Not worked so far.
End goal
timmaaa said:
What's your end goal? Do you want to stick with the 38R build once it flashes successfully or do you want to update all the way to 05Q (or another particular build)? Your best option is to flash the stock images using fastboot. You can find the stock images for all builds in my OnePlus One index thread here:
[INDEX] OnePlus One Resources Compilation Roll-Up
(look in the stock images & ota section)
And I have detailed instructions on how to flash the stock images in section 8 of my guide thread:
[GUIDES][Q&A]How-To Guides For Beginners + Q&A
Click to expand...
Click to collapse
I want to flash the most stable official rom (as I received OTA the 38R).
Do you think that I will be able to flash 38R directly although I have a problem to upgrade with OTA rom?
ur92 said:
I want to flash the most stable official rom (as I received OTA the 38R).
Do you think that I will be able to flash 38R directly although I have a problem to upgrade with OTA rom?
Click to expand...
Click to collapse
You can definitely flash any build via the stock images.
Transmitted via Bacon