Hey been on these forums forever since i was installing themes on my hp ipac or htc shadow. Not a noob by any meens. Been flashing android since my G1. Now that thats out of the way im trying to flash a ICS leak to mess with the webtop 3.0. I was coming from a stock/rooted .181...
1. I fastbooted to .181 using the droid razr 1.6 utility.
2. then i root using ICS installer Combo.
3. Next i use the ICS installer Combo to install the .79 leak.
4. allowed rom manager and su user permissions. i get an error that it can not mkdir to /sdcardEXT.. is this a normal error? Either way once the phone reboots it starts install but then gets the ! in the triangle and what i assume, fails and reverts back to .181.... What am i doing wrong iv been at it for like 3 hours and im pulling my hair out trying to figure out what im missing. My battery is at 40%, is that an issue? Assuming not since if i can fastboot to .181 i should be able to install .79
Hopefully this makes sense and thanks for taking a look
I had something similar to this happen to me when downgrading-rooting-upgrading my Transformer Prime. It failed the upgrade OTA part because I had modified the build.prop and that kept it from installing the upgrade and I got the ! triangle. Have you changed anything? Frozen any apps? Changed your build.prop from stock?
There is a directory you can look in for the log file of why it failed the upgrade. I think it is under /cache/recovery directory from root. (you have to be rooted to see it and use a root explorer). Open the log file and see why its failing.
Thanx for the quick reply. if memory serves me right i modified the build prop to mess with the s-voice app. so your saying fastbooting wouldnt restore this? if not i guess il have to figure out how i changed it and change it back before trying this install again
Well, I would have thought fastbooting would bring it to total stock, but I had made a change in my build.prop AFTER I had downgraded I believe. I think I would check that directory if you can /cache/recovery for the log file and see whats causing your failure specifically. Again, you'll need a good root explorer (like "Root Explorer") and make sure you have it do root so you can see the sub directories too. I was using ES Explorer and it was not seeing the /cache/recovery directory, just /cache and using Root Explorer showed me the sub folder.
PS> Changing your build.prop back to what it looked like before the change didn't work for me. I had to get a stock, unmodified build.prop form another user on here for it to work.
PPS> Why are you wanting to install the leak? Its pretty much been all but confirmed its happening OTA very soon.
Ok i checked out the build.prop alot of stuff in there but seems to all be correct.
I checked that log file and at the very bottom i get this.
Finding update package...
I:Update location: /cache//Blur_Version.6.12.181.XT912.Verizon.en.US.zip
Opening update package...
I:1 key(s) loaded from /res/keys
Verifying update package...
E:failed to open /cache//Blur_Version.6.12.181.XT912.Verizon.en.US.zip (No such file or directory)
I:verify_file returned 1
E:signature verification failed
Installation aborted.
Have no idea what that means tho... If anyone needs the whole log to help me out let me know
Well, thats a lot different than what mine said so your problem is different, but I'm sure someone can help with that info. Heres what mine said when it was the build.prop:
file "/system/build.prop" doesn't have any of expected sha1 sums; checking cache
failed to stat "/cache/saved.file": No such file or directory
failed to load cache file
script aborted: assert failed: apply_patch_check("/system/build.prop"
etc...
Shinare said:
Well, thats a lot different than what mine said so your problem is different, but I'm sure someone can help with that info. Heres what mine said when it was the build.prop:
file "/system/build.prop" doesn't have any of expected sha1 sums; checking cache
failed to stat "/cache/saved.file": No such file or directory
failed to load cache file
script aborted: assert failed: apply_patch_check("/system/build.prop"
etc...
Click to expand...
Click to collapse
Yeah hopefully someone can, i mean with the ota around the corner this is not too big of an issue as long as it doesn't effect the official ota. Thanks for taking the time tho.
Well, the only other thing I can think of thats happened in the past is the wrong "region" file for the phone you are trying to update.
Like you are on US_ENG on your phone and you are trying to flash a WW_ENG or something so its not matching up? *shrug* just a blind guess. Hope someone can help you out.
This may or may not help, but I got that error back in the day flashing a ROM on my D2. In clockwork there was a option to disable and enable signature verification.
Or maybe the zip is messed up?
See the thing is i did this all through the guide in the dev section. i would have posted it there but i didnt have enough posts to post there, im more of a reader than a preacher. i only downloaded the 2 files with the 2 different batch scripts. 1 to fastboot to .181 and 1 to install ICS. Il figure it out eventually, but thanks guys. hopefully someone gets me there sooner.
**fixed it, i ended up using the permissions option in rom manager and also made sure the phone was over 50% and it worked so hopefully this helps soeone eles if they stumble across it.
Related
I live in India & I got the 65.1.21.en.03 OTA (168.9 MB) this morning.
Mentioned changes included bug fixes, a newer baseband and kernel, and the Bejeweled 2 game... although it is still on Gingerbread 2.3.5.
Anyone know how and where I can extract the downloaded update from my phone? Device isn't rooted.
Downloading..
The path/filename is
/cache/Blur_Version.65.1.12.XT910.PSHAsiaRetail.en.03.zip
and it's crc is
# cat /cache/Blur_Version.65.1.12.XT910.PSHAsiaRetail.en.03.crc
2663201091
Does the OTA break root?
The update failed on my rooted xt910. Will investigates later.
Sent from my XT910 using XDA App
Got update today!
I also got update today(india).. Dont know what are the changes happened.. Did not root my phone..
we (at Indonesia) also got the update today.
Tried to update my rooted Razr but like bahathir mine is also failed.
Do we need to get un-rooted before we install this update?
Update work fine on my rooted phone. The update did break the root. Install OTA rootkeeper will help to restore the root.
Sent from my XT910 using XDA App
Updates:
Problems:
1) Update failed.
2) Don't know which file(s) was/were changed, or failed crc check
Investigations and Findings:
0) Put the update file into external microSD. or rename it as update.zip
1) Boot to stock recovery mode.
Power off -> Power + Vol Up + Vol Down for 5 secs or until boot menus appear.
Select Recovery; Wait untul the trianagle with ! mark appear.
Vol Up + Vol Down until the selections appear
Select apply from sdcard and select the update file
In my case, the installation stopped because /system/build.prop has been changed. The changes were done by Motomizer app.
Solution:
Get the proper build.prop file and put it back to /system
Repeat the recovery again... You also can use $ adb reboot recovery from your PC/laptop.
Luckily, I only had one file conflicted by the upgrade.
Important Note:
The update is immune to to zergRush exploit, and you cannot gain ROOT anymore for time being!
Thank you.
So update breaks root and phone cannot be rooted? My update is still downloading
---------- Post added at 08:18 PM ---------- Previous post was at 08:18 PM ----------
How to get the update.zip file? Its only OTA
polaris441 said:
Update work fine on my rooted phone. The update did break the root. Install OTA rootkeeper will help to restore the root.
Sent from my XT910 using XDA App
Click to expand...
Click to collapse
I wish I had seen your post this afternoon.
Updated. Did NOT break root.
bahathir,
can you tell me how to get the original build.prop? My failure was definitely caused by the motomizer also.
Thanks again.
Since I cannot find SEAOP stock ROM, I recreated the file based on one of the build.prop from a stock ROM I found in xda motorola dev forum. Luckily it works
Sent from my XT910 using XDA App
Most of the time, official update will changes file's permission to default. This mean, the suid permission of the /system/xbin/su wil be removed. Check your build version to make sure the update is successful.
Sent from my XT910 using XDA App
bahathir said:
Since I cannot find SEAOP stock ROM, I recreated the file based on one of the build.prop from a stock ROM I found in xda motorola dev forum. Luckily it works
Sent from my XT910 using XDA App
Click to expand...
Click to collapse
care to share the file(build.prop).
Does anyone get a /tmp/sideload/package.zip (status 7) error in the stock recovery?
I've tried everything I could've possibly done(restore, stock files etc) but I still get this error. I really dont care much about my root and losing it would make no difference to me. I use the camera extensively so this update is very important to me.
Please help guys!
Thanks!
EDIT:
This is the exact thing that I see every time I try to install the update
Finding update package......
Opening update package.....
Verifying update package......
Installing update......
assert failed: mount("ext3", "MTD", "system", "/system")
E:Error in /tmp/sideload/package.zip
(Status 7)
Installation Aborted.
/edit Ignore this, it was me thinking Astro file browser should of been working, Root Explorer works fine.
Would there be any other cache location,
I don't appear to have it in /cache/Blur.... (I did the put the update off for an hour option) and searching for it's up to 30mins and still going which is making the phone a pretty good hand warmer.
Here is my SEAOP build.prop Enjoy.
You need root power to access /cache. You need to copy it out AFTER the downloading finished but BEFORE you start installing the updates.
From Connectbot terminal
Code:
$ su
# ls /cache
# cat /cache/Blur_....zip > /sdcard/Blur_....zip
1) Get the root power;
2) list /cache directory and look for update file, mine is Blur_Version.65.1.12.XT910.PSHAsiaRetail.en.03.zip
3) copy the file from the /cache to /sdcard. Then you can copy to microSD's SD-ext
Good luck.
cheekrox said:
Updated. Did NOT break root.
Click to expand...
Click to collapse
how come?? is there something special method to keep the device rooted?
Hello everyone.
It seems my transformer prime is missing an odex file and cannot run the new system update.
I have tried factory reset and everything now i can think of, nothing helped.
How the file has even got missing is beyond me, but the device is rooted and i have OTA rootkeeper and titanium backup.
the file it says is missing is the Galaxy4.odex, located in /system/app/
the error_log from failed update state:
Code:
failed to stat "/system/app/galaxy4.odex": No such file or directory.
file "/system/app/galaxy4.odex" does not have any of the expected sha1 sums; checking cache
failed to load cashe file
script aborted: assert failed: apply patch:check("/system/app/Galaxy4.odex", ---list of numbers---, --list of numbers--not the same")
E:Error in /cache/dlpkgfile
(Status 7)
Installation Aborted
I:result code 410
Does anyone have an idea how i can restore this file to do the update?, or can make some kind of copy /backup that i can install of this file?
All help appreciated!
Silverdream
FYI:
I have WW_epad-9.4.2.14-20120214
Silverdream said:
Hello everyone.
It seems my transformer prime is missing an odex file and cannot run the new system update.
I have tried factory reset and everything now i can think of, nothing helped.
How the file has even got missing is beyond me, but the device is rooted and i have OTA rootkeeper and titanium backup.
the file it says is missing is the Galaxy4.odex, located in /system/app/
the error_log from failed update state:
Code:
failed to stat "/system/app/galaxy4.odex": No such file or directory.
file "/system/app/galaxy4.odex" does not have any of the expected sha1 sums; checking cache
failed to load cashe file
script aborted: assert failed: apply patch:check("/system/app/Galaxy4.odex", ---list of numbers---, --list of numbers--not the same")
E:Error in /cache/dlpkgfile
(Status 7)
Installation Aborted
I:result code 410
Does anyone have an idea how i can restore this file to do the update?, or can make some kind of copy /backup that i can install of this file?
All help appreciated!
Silverdream
Click to expand...
Click to collapse
Do you have a root file manager of some sort, if so, check if that file is:
A) Actually present
B) Has the correct permissions
I do have that odex file on my computer from a system dump that I did at some point, but I honestly can't be sure which version it is.
You could of course download the full update from ASUS website and run it from external SDcard. Search the forum, you should find the exact method of doing this fairly easily.
You could also try to update to .15 first from ASUS website and then do the .21 update. WW versions are present in the download section of the TF201 minisite.
I hope one of these suggestions is of use to you.
Thanks for reply.
I tried most of those, before you wrote it, It just did not want to update when missing files. Then i figured out to hell with it, installed the bootload enabler and a new custom .21 ROM instead.
Bricked once, but now it seems just fine
Hi,
I'm trying to update to the new .28.
I've tried through the OTA, it found the update but failed (showed me the dead android with the warning sign)
I've downloaded the manual update file corresponding with my model (WW), and it failed too.
Just to mention, I did not root before. Now, trying to install it with various methods from the site I did root it. but didn't manage to install.
My last_log ends as follows:
Code:
I:Enable RSA key verification.
Installing update...
Finding update package...
I:Update location: /sdcard/WW_epad-user-9.4.2.28.zip
Opening update package...
I:1 key(s) loaded from /res/keys
I:comment is 1682 bytes; signature 1664 bytes from end
E:failed to verify whole-file signature
I:verify_file returned 1
E:signature verification failed
Installation aborted.
I:result_code: 80000002
Check and format /storage to vfat if needed...
Mount /btmac successfully
Done.
I:timed out waiting for key input; rebooting.
This update is very important to me since my WIFI reception is unacceptable and I heard that they improved it.
What can I do?
i was having the same problem. this is how i solved it:
-first download voodoo ota root keeper from the market and backuproot.
-download the update from the asus website.
-extract the file from the zip.(it should be another zip)
-rename the zip to EP201_SDUPDATE.zip(be care full not to write .zip.zip like some people have done)
-now copy the file to the root of your sd card
-power off the device
-hold volume down + power button
- when you see some writting on the top of the screen let go of both buttons and press the volume up button.
-the device should not start to update
-when it is done try and restore root with voodoo ota root keeper. if that doesnt work use the method here:
http://forum.xda-developers.com/showthread.php?t=1706588
or here
http://forum.xda-developers.com/showthread.php?t=1704209
just download the tool, extract it to a folder, put your device in debugging mode, make sure drivers are installed and run the tool. i just did it and it worked for me. hope this helps
I was so hopeful...
but that didn't work.
Spook77 said:
I was so hopeful...
but that didn't work.
Click to expand...
Click to collapse
try putting the zip to the root of the internal memory
Dead android appeared even faster than previous attempts...
try connecting it to your pc when you do it. not sure if it makes a difference but its worth a try. also make sure you are extracting the zip inside the other zip you downloaded from the asus website. you want to use the one with the word user not the one with thte word updatelauncher. also make sure you are naming the file correctly. make sure you didnt rename it zip.zip. and the name should be all cipital letters.
Still dead android (of course using the zip file inside the original)
in the internal memory
and making sure the name is correct.
But Andy keeps dying. the poor little fellow.
spook77 can you boot into ICS ??
If by boot into ICS you mean if my tablet OS loads and it has ICS, than yes.
my problem is upgrading to .28
I keep getting the dead android animation with exclamation mark over him when I try to upgrade to .28
after that the tablet continues loading and loads the .21 I had before.
I've lost hope of being able to do this by myself.
I'd like to send the tablet to Asus labs for fix.
How can I unroot the tablet so my warranty will still be valid?
for some reason it seems like the zip file you downloaded doesn't seem to be valided...
make sure you are downloading the correct ww/us/tw and not just renaming it
if you have any modified files when you are rooted, you have to restore everything back to default
Hi all. I have a US I535 Verizon S3 which I rooted when I got it and kept rooted through an update with Voodoo Rootkeeper. I have since temp unrooted and tried to apply the OTA update to 4.3 (I don't have time to wipe, install via recover, and put everything back) and the upgrade is failing to apply around 25% with this message found in /data/log/recovery_log.txt:
Installing update...
try_update_binary(path(/cache/fota/update.zip))
radio.diff not found
Register_libbootloader_updater Qcom msm8960
[DEBUG] setprocattrcon: open failed, errno=2
[DEBUG] setprocattrcon: open failed, errno=2
Verifying current system...
file "/system/csc/feature.xml" doesn't have any of expected sha1 sums; checking cache
failed to stat "/cache/saved.file": No such file or directory
failed to load cache file
failed to stat "/data/.saved.file": No such file or directory
failed to load data file
script aborted: "/system/csc/feature.xml" has unexpected contents.
"/system/csc/feature.xml" has unexpected contents.
E :Error in /cache/fota/update.zip
(Status 7)
E:Error in /cache/fota/update.zip
(Status 7)
FOTA_update_success_log_result()
Update Fail. File is written. status = 7
Installation aborted.
Does anyone know how to correct this either by updating the xml file or fixing whatever may be the "true cause" of that error?
UPDATE: I remembered thanks to an old post on xda:
Luckily I recovered root on my Vzw S3 after the 4.1.1 OTA. I discovered that you can move GPS/BT toggle widgets to /system/app/ and it no longer asks for confirmations. Super fast toggles with no hassle! There's a small app in the Play store called "/system/app mover" to do it.
Click to expand...
Click to collapse
Would that be detected and block the update? I'm going to use TiBU to convert Power Toggles back to a user app and see if that gives me the green light, but it doesn't seem like it would be related to the xml error.
Thanks a bunch!
my /ssyte/csc/feature.xml (4.1.2)
CPngN said:
Hi all. I have a US I535 Verizon S3 which I rooted when I got it and kept rooted through an with Voodoo Rootkeeper. I have since temp unrooted and tried to apply the to . (I don't have time to wipe, install via recover, and put everything back) and the is failing to apply around 25% with this message found in /data/log/recovery_log.txt:
Click to expand...
Click to collapse
Here's the text of my /system/csc/feature.xml that the is complaining about:
http://pastie.org/private/8argqzzxwlgafxfceuhepq
Thanks all
Hey guys
I tried to change the ROM from my chinese Mi Box to the US version with a guide
But I made something wrong and ended up in the stock-recovery
luckily I was able to update the Box from the recovery with a update.zip (which is for the MDZ-19-AB US version)
Everything worked fine, but I was greedy and wanted to update with the same procedure to Android TV 8.0 and I soft-bricked the device but I can still get into the recovery
I tried to go back to Android TV 7.0 with the update.zip but the update checks if ("ro.product.device") is equal to "once" which was "once" but after the 8.0 update is somehow empty
I even tried tho unbrick it with a guide and the USB burning tool but that doesnt work either
I tried to take the update.zip remove the check form the updater-script and zip it and even sign it (with multiple different tools) but I am unable to get it working (either "footer is wrong" or "failed to verify whole-file signature" error comes up)
TL/DR: Can someone take the update.zip remove the check for the device in the updater script(first line), zip and sign it properly so I can update it with the stock-recovery?
it seems like I am unable to do it myself
please PM me if you can help I'n not allowed to add outside-links :crying:
remo_94 said:
Hey guys
I tried to change the ROM from my chinese Mi Box to the US version with a guide
But I made something wrong and ended up in the stock-recovery
luckily I was able to update the Box from the recovery with a update.zip (which is for the MDZ-19-AB US version)
Everything worked fine, but I was greedy and wanted to update with the same procedure to Android TV 8.0 and I soft-bricked the device but I can still get into the recovery
I tried to go back to Android TV 7.0 with the update.zip but the update checks if ("ro.product.device") is equal to "once" which was "once" but after the 8.0 update is somehow empty
I even tried tho unbrick it with a guide and the USB burning tool but that doesnt work either
I tried to take the update.zip remove the check form the updater-script and zip it and even sign it (with multiple different tools) but I am unable to get it working (either "footer is wrong" or "failed to verify whole-file signature" error comes up)
TL/DR: Can someone take the update.zip remove the check for the device in the updater script(first line), zip and sign it properly so I can update it with the stock-recovery?
it seems like I am unable to do it myself
please PM me if you can help I'n not allowed to add outside-links :crying:
Click to expand...
Click to collapse
that would be nice if anyone actually had the keys needed to sign it to pass verification lol
remo_94 said:
Hey guys :crying:
Click to expand...
Click to collapse
Hey, you can extract the updater-script from the package, edit it, then repack it to the same zip(preserving the signature)
Ricky Divjakovski said:
Hey, you can extract the updater-script from the package, edit it, then repack it to the same zip(preserving the signature)
Click to expand...
Click to collapse
wouldnt that break the whole file signature?
elliwigy said:
wouldnt that break the whole file signature?
Click to expand...
Click to collapse
Pretty sure it doesnt aslong as you repack with the update method, same way your able to mod certain apps inside/system preserving the signature
But.. im pretty sure ive got amlogics keys somewhere though
Ricky Divjakovski said:
Pretty sure it doesnt aslong as you repack with the update method, same way your able to mod certain apps inside/system preserving the signature
But.. im pretty sure ive got amlogics keys somewhere though
Click to expand...
Click to collapse
I guess with the "update method" you mean just edit the file in the archive without extracting and repacking.
I tried with WinRAR and 7-zip, I tried editing it inside the archive and saving the changes, I tried extracting editing and repacking it, I even edited the MANIFEST.MF to the new SHA-1 value of the update-script but I only get "failed to verify whole-file signature"
I thought it was enough if I sign my update.zip with the Android testkeys isn't that possible?
remo_94 said:
I guess with the "update method" you mean just edit the file in the archive without extracting and repacking.
I tried with WinRAR and 7-zip, I tried editing it inside the archive and saving the changes, I tried extracting editing and repacking it, I even edited the MANIFEST.MF to the new SHA-1 value of the update-script but I only get "failed to verify whole-file signature"
I thought it was enough if I sign my update.zip with the Android testkeys isn't that possible?
Click to expand...
Click to collapse
Ill look more into it tonight