ok so heres the deal. i bricked my last gt540 but was able to bring it to the store and swap it out.
lol so here we are on the new one and i have it rooted, latest recovery i can find 3.0.2.4...i managed to flash mur4ik's cm7 2.3.3 but now it seems as if im stuck with it. whether i try and flash from clockwork or rom manager i always get a failed attempt. once i noticed it was cause the rom wasnt signed so i toggled the option to off and still it failed. any help would be awesome.
thanks gents!
any help would be super!
try flashing roms using the fastboot method
lol it seems like a major task for me. cant seem to figure out how to do.
ive similar problem,
installed euro 2.1 build using KDZ image. recovery comes up.
If i try to restore zip from sd using update-cm-7.0.2-GT540-MUR4IK-signed.zip i keep on getting:
Installing update
assert failed: getprop("ro.product.device" == "swift" || "ro.build.product" == "swift" || "ro.product.board" == "swift" ||
E:Error in /sdcard/clockworkmod/backup/update-cm-7.0.2-GT540-MUR4IK-signed.zip
(Status 7)
Installation aborted
anyone ?
tmuehlhoff said:
ive similar problem,
installed euro 2.1 build using KDZ image. recovery comes up.
If i try to restore zip from sd using update-cm-7.0.2-GT540-MUR4IK-signed.zip i keep on getting:
Installing update
assert failed: getprop("ro.product.device" == "swift" || "ro.build.product" == "swift" || "ro.product.board" == "swift" ||
E:Error in /sdcard/clockworkmod/backup/update-cm-7.0.2-GT540-MUR4IK-signed.zip
(Status 7)
Installation aborted
anyone ?
Click to expand...
Click to collapse
i used the same method. sounds like the same issues. i think we need some help lol.
kdm212 said:
i used the same method. sounds like the same issues. i think we need some help lol.
Click to expand...
Click to collapse
ive read about different hardware used in gt540/swift types.. .maybe thats the issue here?!
so then what should we do? where did you read this stuff?
dunno- therere millions of threads out there. maybe someone feels like and gives us a hint what to do....
ok so i managed to figure out fastboot via cmd. i was overthinking it. anyway i get to the step where i need to send and write the fastboot flash boot boot.img. it sends it but fails to write to the phone.
(remote: flash write failure)
any suggestions?
Have you tried downloading the files again. Sometimes the download is corrupt which will cause a fail in the recovery. I have had it a few times myself. After downloading the file again (often from another source) the recovery completes itself succesfully.
i have tried to redownload. im actually going to bring the phone all the way back to stock and see what happens. kinda start from scratch.
Try this way go to market and Download bt file manager and seleact the update package and extract to a folder then try install zip from sD method try and rply
Sent from my GT540 using XDA Premium App
kdm212 said:
i have tried to redownload. im actually going to bring the phone all the way back to stock and see what happens. kinda start from scratch.
Click to expand...
Click to collapse
Get in emergency mode and reflash boot.img via CMD with fastboot commands and you will get the same error probably, but you just reboot it, let it boot it will work
Sent from my GT540 using XDA App
Related
Running FRF91 & need to manually update? Somehow my ota has never worked and it's time to do an update even though gingerbread isn't ready. Please post the location where to get the most current version of OTA.
Thanks,
Big_O said:
Running FRF91 & need to manually update? Somehow my ota has never worked and it's time to do an update even though gingerbread isn't ready. Please post the location where to get the most current version of OTA.
Thanks,
Click to expand...
Click to collapse
This will get you to FRG83D: http://android.clients.google.com/p...signed-passion-FRG83D-from-FRF91.7957af1a.zip
And then this will get you to FRG83G: http://android.clients.google.com/p...igned-passion-FRG83G-from-FRG83D.2854b06b.zip
I have installed the image from HTC developer site (FRG 83) to my nexus one.
And then i tried to install the FRG83D (from the link in earlier response), but i get
Code:
Installing update...
assert failed: file_getprop("/system/build.prop", "ro.build.fingerprint") == "google/passion/passion/mahimahi:2.2/FRF91/43546:user/release-keys" || file_getprop("/system/build.prop", "ro.build.fingerprint") == "google/passion/passion/mahimahi:2.2.1/FRG93D/75603:user/release-keys"
E:Error in /sdcard/update.zip
(Status 7)
Thanks efrant!
hap497 said:
I have installed the image from HTC developer site (FRG 83) to my nexus one.
And then i tried to install the FRG83D (from the link in earlier response), but i get
Code:
Installing update...
assert failed: file_getprop("/system/build.prop", "ro.build.fingerprint") == "google/passion/passion/mahimahi:2.2/FRF91/43546:user/release-keys" || file_getprop("/system/build.prop", "ro.build.fingerprint") == "google/passion/passion/mahimahi:2.2.1/FRG93D/75603:user/release-keys"
E:Error in /sdcard/update.zip
(Status 7)
Click to expand...
Click to collapse
The zip file above is only for FRF91
u need to google another one that is from FRG83 to FRG83D
Sent from my Nexus One using Tapatalk
hap497 said:
I have installed the image from HTC developer site (FRG 83) to my nexus one.
And then i tried to install the FRG83D (from the link in earlier response), but i get
Code:
Installing update...
assert failed: file_getprop("/system/build.prop", "ro.build.fingerprint") == "google/passion/passion/mahimahi:2.2/FRF91/43546:user/release-keys" || file_getprop("/system/build.prop", "ro.build.fingerprint") == "google/passion/passion/mahimahi:2.2.1/FRG93D/75603:user/release-keys"
E:Error in /sdcard/update.zip
(Status 7)
Click to expand...
Click to collapse
link to the file you need is in sticky
I had to follow this pathway as well. I went back to FRF91 on the HTC site, and the phone would not OTA to the most current. Its odd though, because I did this last week on a different Nexus, HTC site FRF91, and the other OTAs went right through when I turned it on; it OTA itself to FRG83G just fine. Maybe they killed those updates from FRF91 thru FRG83G when GRI40 was released?
Anywho, the updates will eventually get you to GRI40 manual install (if you dont get the OTA notification for it -- like I didn't).
Odd thing though, I went from latest market in FRG83G back to older market when I finally flashed the GRI40 update.zip. D'oh!
I am in the same situation, except when I went to FRG83D I lost my recovery and now I can't go to 83G then GRI40.
I found a recovery.img for stock recovery but when I try to flash using fastboot I get a signature verification failed.
Any ideas? Thanks
izmatron said:
I am in the same situation, except when I went to FRG83D I lost my recovery and now I can't go to 83G then GRI40.
I found a recovery.img for stock recovery but when I try to flash using fastboot I get a signature verification failed.
Any ideas? Thanks
Click to expand...
Click to collapse
i would try going back to frf91 and then upgrading one step at a time... frg83, frg83d, frg83g, gri40. (its what i did, and it was flawless)
there are links in these parts to those updates. verify md5s first, then flash away!
fastboot is your friend.
nexusonemeover said:
i would try going back to frf91 and then upgrading one step at a time... frg83, frg83d, frg83g, gri40. (its what i did, and it was flawless)
there are links in these parts to those updates. verify md5s first, then flash away!
fastboot is your friend.
Click to expand...
Click to collapse
Cool, but how with no recovery? Still fastboot? If so, how do I flash a .zip rather than a .img?
izmatron said:
Cool, but how with no recovery? Still fastboot? If so, how do I flash a .zip rather than a .img?
Click to expand...
Click to collapse
yeah. unzip the file from the htc dev website and then run the fastboot commands:
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img
etc... for the remaining img files.
be sure to fastboot erase userdata and fastboot erase cache first
when done, you can fastboot reboot
if you need more info, this thread has the main idea to follow...
http://forum.xda-developers.com/showthread.php?t=614850
but, use the htc dev site zip file of frf91
nexusonemeover said:
yeah. unzip the file from the htc dev website and then run the fastboot commands:
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img
etc... for the remaining img files.
be sure to fastboot erase userdata and fastboot erase cache first
when done, you can fastboot reboot
if you need more info, this thread has the main idea to follow...
http://forum.xda-developers.com/showthread.php?t=614850
but, use the htc dev site zip file of frf91
Click to expand...
Click to collapse
Thanks, I got the OTA and back at FRG83D but it won't update to FRG83G OTA. I tried checking in and still no update. Ideas?
http://forum.xda-developers.com/showthread.php?t=923856
Sent from my Nexus One using XDA App
Tried to update to 83d and recovery aborted.
Said E: No signature
E: Verification failed.
Tried Clockwork recovery and still aborted with signature verification off.
Any ideas?
Big_O said:
Tried to update to 83d and recovery aborted.
Said E: No signature
E: Verification failed.
Tried Clockwork recovery and still aborted with signature verification off.
Any ideas?
Click to expand...
Click to collapse
I've never used ClockworkMod, but it should work with signature verification off. What version of Android are you and an what file are you using to update? There are different files to use if you are on FRF91 or FRG33 or FRG83 or etc...
ok. I have rolled back to FRF91 from htc site.
And there are the links for FRG83D and FRG83G. But where can I find the links for frg83 and gri40?
This will get you to FRG83D: http://android.clients.google.com/pa...1.7957af1a.zip
And then this will get you to FRG83G: http://android.clients.google.com/pa...D.2854b06b.zip
hap497 said:
ok. I have rolled back to FRF91 from htc site.
And there are the links for FRG83D and FRG83G. But where can I find the links for frg83 and gri40?
This will get you to FRG83D: http://android.clients.google.com/pa...1.7957af1a.zip
And then this will get you to FRG83G: http://android.clients.google.com/pa...D.2854b06b.zip
Click to expand...
Click to collapse
This should take you from FRF91 to GRI40 directly: http://android.clients.google.com/p...b119f8.signed-passion-ota-102588.656099b1.zip
Make sure you are on HBOOT 0.35 (http://android.clients.google.com/packages/ota/passion/d6096cac5e9f.signed-hboot-0.35.0017.zip) before you use that update.
Thank you, efrant.
I have 2 questions.
1. how can i find out what is my current version of HBOOT? if I flash the FRF 91 image from HTC website?
2. If i update to HBOOT 0.35, can I roll back the HBOOT to my current version (whatever it is from #1 answer)?
Thank you.
hap497 said:
Thank you, efrant.
I have 2 questions.
1. how can i find out what is my current version of HBOOT? if I flash the FRF 91 image from HTC website?
2. If i update to HBOOT 0.35, can I roll back the HBOOT to my current version (whatever it is from #1 answer)?
Thank you.
Click to expand...
Click to collapse
1. Turn off your phone, and turn it back on while holding down the trackball. What version do you see? 0.33 or 0.35?
2. No. You cannot roll back to 0.33 if you upgrade to 0.35. But anyway, you cannot run GRI40 on the 0.33 HBOOT... You will be running Froyo until you decide to update...
Thank you, efrant.
I have 1 more question.
I can update the nexus the image from HTC using the 'fastboot' from command line.
What is the purpose of HBoot ? why I need to update that in order to update GRI40?
Is there anyway i can update to GRI40 using fastboot command?
Thank you.
Hey guys,
So I attempted to root my nexus s and ran into some troubles.
I started the process on my mac.....(keep in mind I also have a PC, so that is still an option to work with) I got the bootloader unlocked.....I have ClockwordMod Recovery v3.0.0.0 working.......but as soon as I try to restart the device it just wont go past the google splash screen with the padlock.
I've tried to install superuser .zip files.....nandroid backup .zips....with no success. I always get hung up on the splash screen!
I feel terrible I don't know where I went wrong
dannykavs said:
Hey guys,
So I attempted to root my nexus s and ran into some troubles.
I started the process on my mac.....(keep in mind I also have a PC, so that is still an option to work with) I got the bootloader unlocked.....I have ClockwordMod Recovery v3.0.0.0 working.......but as soon as I try to restart the device it just wont go past the google splash screen with the padlock.
I've tried to install superuser .zip files.....nandroid backup .zips....with no success. I always get hung up on the splash screen!
I feel terrible I don't know where I went wrong
Click to expand...
Click to collapse
Did you follow the terrible guide at http://nexusshacks.com/nexus-s-hacks/how-to-root-nexus-s/ where you flash the insecure boot image that is way out of date and only for the i9020t?
Are you trying to restore a stock rom or a custom rom? Either way, grab the full package OTA of a stock rom for your device (around 90mb) or your custom rom of choice and flash that from CWM. That will write a new boot.img as well as /system, etc.
krohnjw said:
Did you follow the terrible guide at http://nexusshacks.com/nexus-s-hacks/how-to-root-nexus-s/ where you flash the insecure boot image that is way out of date and only for the i9020t?
Are you trying to restore a stock rom or a custom rom? Either way, grab the full package OTA of a stock rom for your device (around 90mb) or your custom rom of choice and flash that from CWM. That will write a new boot.img as well as /system, etc.
Click to expand...
Click to collapse
I didn't follow that guide thankfully but I still think I followed an outdated procedure.
So when i try to install a rom Clockwork always aborts the installation.
here is the error I get:
assert failed: getprop("ro.product.device")=="crespo" || getprop("ro.build.product") =="crespo" || getprop ("ro.product.board") == "crespo" E: Error in /sdcard/update-cm-7.1.0.1-NS-signed.zip
(status) 7
Installation aborted
dannykavs said:
I didn't follow that guide thankfully but I still think I followed an outdated procedure.
So when i try to install a rom Clockwork always aborts the installation.
here is the error I get:
assert failed: getprop("ro.product.device")=="crespo" || getprop("ro.build.product") =="crespo" || getprop ("ro.product.board") == "crespo" E: Error in /sdcard/update-cm-7.1.0.1-NS-signed.zip
(status) 7
Installation aborted
Click to expand...
Click to collapse
Do you have a GSM Nexus S (i9020t, i9020a, i90230) or the CDMA Nexus S 4G? If it's the latter you are trying to flash a ROM that's not for your device. Get a rom for the NS4G from that development forum (device = crespo4g).
have you tried flashing a rom?
krohnjw said:
Do you have a GSM Nexus S (i9020t, i9020a, i90230) or the CDMA Nexus S 4G? If it's the latter you are trying to flash a ROM that's not for your device. Get a rom for the NS4G from that development forum (device = crespo4g).
Click to expand...
Click to collapse
It is the GSM Nexus S i9020A. Don't believe that to be an issue.
I've threw so many different zip files on my sd card when I mount it via usb and I always seem to get that same error message. Pretty frustrating....I always read about people not being able to flash recovery but I'm there.....I just can't seem to find anyone who has my same issue...
Any other information I can provide that would be useful?
Try a more recent version of cwm.
albundy2010 said:
Try a more recent version of cwm.
Click to expand...
Click to collapse
I've actually got version 3.1 going right now with no luck
What is the latest version ?
Update CWM to higher than 4.0.0.0. You could flash the zip below in recovery and if that doesn't work then find the new version with fastboot.
http://forum.xda-developers.com/showthread.php?t=1248760
EDIT: Just flash one of these with fastboot: http://forum.xda-developers.com/showthread.php?t=988686&highlight=clockwork+recovery
The first and second ones will work for you.
irishrally said:
Update CWM to higher than 4.0.0.0. You could flash the zip below in recovery and if that doesn't work then find the new version with fastboot.
http://forum.xda-developers.com/showthread.php?t=1248760
EDIT: Just flash one of these with fastboot: http://forum.xda-developers.com/showthread.php?t=988686&highlight=clockwork+recovery
The first and second ones will work for you.
Click to expand...
Click to collapse
Thanks for the suggestion. I will give this a go first thing in the morning and report back.
Bedtime zzzzzzzZzzZzz
irishrally said:
Update CWM to higher than 4.0.0.0. You could flash the zip below in recovery and if that doesn't work then find the new version with fastboot.
http://forum.xda-developers.com/showthread.php?t=1248760
EDIT: Just flash one of these with fastboot: http://forum.xda-developers.com/showthread.php?t=988686&highlight=clockwork+recovery
The first and second ones will work for you.
Click to expand...
Click to collapse
Yup so I went ahead and flashed the recovery from the second link you gave me and on my first try i was able to install the CyanogenMod 7.1 zip file. Made my day!
Thanks everyone!
http://forum.xda-developers.com/showthread.php?t=1250583
for reference, I just rooted my new (to me) nexus s the other day with this. It couldn't be any easier really.
when i try to upgrade my n7 3g using OTA or manual update i will give me a message
'assert failed: getprop("ro.product.device") == "tilapia" ll getprop("ro.build.product") == "tilapia" E : Error in /sdcard/0/357318e165a8.signed-nakasig-JDQ39-from JPO40D.357318e1.zip (status 7) Installation aborted.
i used 4.2.1 stock rom
locked bootloader
unroot.
Hmmm, I notice you said "unroot"
stock recovery or custom?
That assert is there to insure that it is only flashed to a tilapia/nakasig (3g) N7
The getprop values in question are being read from the *recovery*, not the installed ROM... so, the most reasonable conclusion is that you have a custom recovery or stock recovery from a grouper device installed on your (tilapia) 3g N7.
Flash the stock tilapia recovery there and try again.
This would be an unreasonable hypothesis for a never-rooted tab, but you did say "unrooted"
bftb0 said:
Hmmm, I notice you said "unroot"
stock recovery or custom?
That assert is there to insure that it is only flashed to a tilapia/nakasig (3g) N7
The getprop values in question are being read from the *recovery*, not the installed ROM... so, the most reasonable conclusion is that you have a custom recovery or stock recovery from a grouper device installed on your (tilapia) 3g N7.
Flash the stock tilapia recovery there and try again.
This would be an unreasonable hypothesis for a never-rooted tab, but you did say "unrooted"
Click to expand...
Click to collapse
Hi!
im having the same problem, Nexus 7 3G is rooted with custom recovery...
is there a way to install the 4.2.2 update with custom recovery or do i have to return to stock?
thank you!
R: [Q] unable to update my n7 3g to android 4.2.2
You are maybe using a recovery for grouper. Just flash the right tilapia recovery and all should works.
Nexus 7 3G - Tapatalk
Hum... I had this kind of problem, I guess.
I searched many threads when I rooted and unlocked my Nexus 7 3g, to avoid this "status 7" problem.
I chose Wug´s nexus toolkit, unlocked and rooted my device. After that, I installed, via toolkit, the TWRP recovery.
When I received the system update notification, my device asked me to reboot, then a screen of TWRP appeared to me. I just rebooted the system and now, without update, I don´t even get the message again.
I assume that the Wug´s toolkit flashed a grouper version of TWRP. What I have to do now ? I would like to do the things manually. Maybe flash a factory image from here with this method.
I´m very noob with this kind of thing, because I still have a old milestone 2 with a locked bootloader. The method to flash ROM in milestone 2 is quite different...
Anybody can help me ?
mouse100 said:
You are maybe using a recovery for grouper. Just flash the right tilapia recovery and all should works.
Nexus 7 3G - Tapatalk
Click to expand...
Click to collapse
thank you , ill flash it as soon as i get home and check if it works!
azfarmiera said:
when i try to upgrade my n7 3g using OTA or manual update i will give me a message
'assert failed: getprop("ro.product.device") == "tilapia" ll getprop("ro.build.product") == "tilapia" E : Error in /sdcard/0/357318e165a8.signed-nakasig-JDQ39-from JPO40D.357318e1.zip (status 7) Installation aborted.
i used 4.2.1 stock rom
locked bootloader
unroot.
Click to expand...
Click to collapse
hey there.i get the solution.i just flash stock recovery and wait until OTA update notification on phone and it will update 4.2.2.thank for your help
bisco said:
thank you , ill flash it as soon as i get home and check if it works!
Click to expand...
Click to collapse
just flashed openrecovery-twrp-2.4.1.0-tilapia.img recvery file but update still does not work
bftb0 said:
Flash the stock tilapia recovery there and try again.
Click to expand...
Click to collapse
Is just the stock recovery posted somewhere? I can't seem to find it.
Sent from my SGH-I777 using xda app-developers app
rthisp said:
Hum... I had this kind of problem, I guess.
I searched many threads when I rooted and unlocked my Nexus 7 3g, to avoid this "status 7" problem.
I chose Wug´s nexus toolkit, unlocked and rooted my device. After that, I installed, via toolkit, the TWRP recovery.
When I received the system update notification, my device asked me to reboot, then a screen of TWRP appeared to me. I just rebooted the system and now, without update, I don´t even get the message again.
I assume that the Wug´s toolkit flashed a grouper version of TWRP. What I have to do now ? I would like to do the things manually. Maybe flash a factory image from here with this method.
I´m very noob with this kind of thing, because I still have a old milestone 2 with a locked bootloader. The method to flash ROM in milestone 2 is quite different...
Anybody can help me ?
Click to expand...
Click to collapse
Found how? Same here with cwm... Chose reboot and now still on 4.2.1 and no more ota update available... Even when I check for updates.
theBeachBoy said:
Found how? Same here with cwm... Chose reboot and now still on 4.2.1 and no more ota update available... Even when I check for updates.
Click to expand...
Click to collapse
finally I found it. took so long I almost abandonned
I had to use stock recovery and adb sideload the zip file, it would not work with CWM eveb if I manually edit the script to skip that assert line, it would crash later in the modem part of the update.
Also, if you have a 3G version you need to use nakasig instead of nakasi, I have used the link from there to get the zip file: http://forum.xda-developers.com/showthread.php?t=1745781
[Q] OTA failed and displayed dead Android saying Error! Tried to sideload the zip file using Toolkit 1.6.8 and it didn't go through. Tried to load it using TWRP and this is what I get:
Code:
Verifying current system...
assert failed: apply_patch_check("/system/build.prop". "5a778d005448ec19
E:Error in /sdcard/de8b8...zip
(Status 7)
Error flashing zip '/sdcard/de8b8...zip
I'm running rooted stock ROM, never tried anything else so I don't know how I could have messed up something.
Thanks for any ideas!
domi_niku said:
[Q] OTA failed and displayed dead Android saying Error! Tried to sideload the zip file using Toolkit 1.6.8 and it didn't go through. Tried to load it using TWRP and this is what I get:
Code:
Verifying current system...
assert failed: apply_patch_check("/system/build.prop". "5a778d005448ec19
E:Error in /sdcard/de8b8...zip
(Status 7)
Error flashing zip '/sdcard/de8b8...zip
I'm running rooted stock ROM, never tried anything else so I don't know how I could have messed up something.
Thanks for any ideas!
Click to expand...
Click to collapse
Flash a stock rom and install the OTA through adb sideload with adb and not by a toolkit, worked for me. After that reroot. Also read this thread well http://forum.xda-developers.com/showthread.php?t=2145848.
gee2012 said:
Flash a stock rom and install the OTA through adb sideload with adb and not by a toolkit, worked for me. After that reroot.
Click to expand...
Click to collapse
I'm gonna try the stock 4.2.2 ROM, thanks.
It still doesn't the answer the following question: what's wrong?
domi_niku said:
I'm gonna try the stock 4.2.2 ROM, thanks.
It still doesn't the answer the following question: what's wrong?
Click to expand...
Click to collapse
Did you try a different kernel in the past? ie Franco's kernel?
harpo1 said:
Did you try a different kernel in the past? ie Franco's kernel?
Click to expand...
Click to collapse
No, never. I just wiped the phone and installed stock 4.2.2 using the Toolkit and now it won't boot.
EDIT: I guess that's because the Toolkit doesn't support 4.2.2. Oh well just flashed it using ADB. Hope I can get all my app data back...
so I was so elated to finally have KitKat. I downloaded the update from one of the sites linked in the General Forum for the Nexus 7, and attempted to adb sideload it. This is what I got:
Verifying current system…
“/system/etc/audio_effects.conf” has unexpected contents.
E:Error in /tmp/update.zip
(Status 7)
Installation aborted.
What do I do?
Thank you for your help
Should I try to download again? It seems as though I have some sort of audio that messed it up.
Sent from my Nexus 7 using Tapatalk
Here is my audio.conf it talked about:
https://db.tt/TwT6k3ez
Sent from my Nexus 7 using Tapatalk
i had the same problem
i downloaded the lastest 4.3 image from google (https://developers.google.com/android/nexus/images#nakasijwr66y)
you must have a clean and fresh install of it.
trying to flash this via CWM or TWRP recovery failed.
so i extractet the image and used the "flash-all.bat/flash-all.sh"
all user data were gone (i dont care about at my tablet ) but so a could flash the rom.
after that i could flash the update to 4.4
oder esyer now. flash the stock 4.4 image
https://developers.google.com/android/nexus/images#nakasikrt16o
(links are for wifi model)
jma9454 said:
so I was so elated to finally have KitKat. I downloaded the update from one of the sites linked in the General Forum for the Nexus 7, and attempted to adb sideload it. This is what I got:
Verifying current system…
“/system/etc/audio_effects.conf” has unexpected contents.
E:Error in /tmp/update.zip
(Status 7)
Installation aborted.
What do I do?
Thank you for your help
Click to expand...
Click to collapse
I've attached the original file I extracted from the 4.3 stock image (nakasi-jwr66y-factory-1e503532.tgz).
You can try copying it to /system/etc/ (ensuring permissions are correct) and then retry the installation.
I suspect that if you've been playing around with audio tweaks then it's going to fail on other files too.
If it does, then you can use fastboot to _just_ flash the system.img and you won't lose any of your data.
Same thing happened to me. But it's worse, it's stuck on bootloader and Windows won't recognize the device (unkown device on device manager) so I can't even use adb to flash factory image. I'm really desperate here, anyone here with a tip?
fabulosospucas said:
Same thing happened to me. But it's worse, it's stuck on bootloader and Windows won't recognize the device (unkown device on device manager) so I can't even use adb to flash factory image. I'm really desperate here, anyone here with a tip?
Click to expand...
Click to collapse
Use Wug toolkit to install drivers (it has a couple of possibilities) until it works, then install factory image.
I got it to work on windows 8.1, so it's possible.
I'm having a similar problem. I tried to adb sideload 4.4 that I downloaded from the google website and got an error. Now my nexus 7 is bootlooping at the google logo and returning to twrp shortly after. I can't seem to use fastboot and I've wiped everything. I'm also on a Mac. Any help would be greatly appreciated. I can't seem to figure out a solution.
I received the error message "E: Error executing updater binary in zip '/data/media/0/sideload.zip' "
brian_199 said:
I received the error message "E: Error executing updater binary in zip '/data/media/0/sideload.zip' "
Click to expand...
Click to collapse
You need to post the whole error message, not just that one line.
fozzie said:
You need to post the whole error message, not just that one line.
Click to expand...
Click to collapse
Updating partition deltails...
Starting ADB sideload feature...
Installing '/data/media/0/sideload.zip'...
Checking for MD5 file...
Skipping MD5 check: no MD5 file found.
file_getprop: failed to stat "/system/build.prop": No such file or directory
E: Error executing updater binary in zip '/data/media/0/sideload.zip'
brian_199 said:
Updating partition deltails...
Starting ADB sideload feature...
Installing '/data/media/0/sideload.zip'...
Checking for MD5 file...
Skipping MD5 check: no MD5 file found.
file_getprop: failed to stat "/system/build.prop": No such file or directory
E: Error executing updater binary in zip '/data/media/0/sideload.zip'
Click to expand...
Click to collapse
There's your problem. You have no /system/build.prop file.
Did you delete it? Have you a backup? You need to get it back on the device.
Edit: I've attached the build.prop from the N7 2012 (nakasi/grouper) JWR66Y ROM.
fozzie said:
There's your problem. You have no /system/build.prop file.
Did you delete it? Have you a backup? You need to get it back on the device.
Edit: I've attached the build.prop from the N7 2012 (nakasi/grouper) JWR66Y ROM.
Click to expand...
Click to collapse
Thank you, I really appreciate it. How can I reinstall the build.prop.zip?
You wouldnt happen to have a stock build.prop for KRT16O would!d you? My dumbass forgot to back mine up before I edited mine to add mods. :banghead:
Sent from my Nexus 7 using xda app-developers app
y0brando said:
You wouldnt happen to have a stock build.prop for KRT16O would!d you? My dumbass forgot to back mine up before I edited mine to add mods. :banghead:
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
Just unzip the file
brian_199 said:
Thank you, I really appreciate it. How can I reinstall the build.prop.zip?
Click to expand...
Click to collapse
Just use something like Root Explorer to copy it from your SD card to /system/ (and check permissions are 644 or rw-r--r--).
GMPOWER said:
Just unzip the file
Click to expand...
Click to collapse
thanks, worked like a champ :victory: :victory::good:
I have the same problem.
Verifying current system…
“/system/xbin/dexdump” has unexpected contents.
E:Error in /tmp/update.zip
(Status 7)
Installation aborted.
please help me.
very thank you for your help.
supernuta said:
I have the same problem.
Verifying current system…
“/system/xbin/dexdump” has unexpected contents.
E:Error in /tmp/update.zip
(Status 7)
Installation aborted.
please help me.
very thank you for your help.
Click to expand...
Click to collapse
If you can say what device and ROM you're coming from, I can probably post the right version of the file.
I'm from nexus4 jb4.3 JWR66Y occam
thank you very much.
supernuta said:
I'm from nexus4 jb4.3 JWR66Y occam
thank you very much.
Click to expand...
Click to collapse
Here you go.