Database Users

[Q] Error 7 When installing 2.3.7 from Recovery

Hello XDA Developers! Last time I was here I was hacking a HTC Blue Angel..That was a long time away....I digress
I have this phone which is currently running a 2.3.4 rom and I have ClockworkMod Recovery v2.5.0.5, and when I download any of the 2.3.7 roms this is what happens:
I drag the recovery zip to my phone with no extraction at all and select install zip from recovery menu. It does nothing.
I extract the zip file and end up with recovery.img and a zip file. I drag both to the root of my memory card and then select install zip from my phone. I then get the following error:
i.imgur.com/xlHip.png
I have absolutely no idea what to try from here, the biggest problem i've dealt with thus far was a md5 mismatch...
Kevin

normankev said:
Hello XDA Developers! Last time I was here I was hacking a HTC Blue Angel..That was a long time away....I digress
I have this phone which is currently running a 2.3.4 rom and I have ClockworkMod Recovery v2.5.0.5, and when I download any of the 2.3.7 roms this is what happens:
I drag the recovery zip to my phone with no extraction at all and select install zip from recovery menu. It does nothing.
I extract the zip file and end up with recovery.img and a zip file. I drag both to the root of my memory card and then select install zip from my phone. I then get the following error:
i.imgur.com/xlHip.png
I have absolutely no idea what to try from here, the biggest problem i've dealt with thus far was a md5 mismatch...
Kevin
Click to expand...
Click to collapse
Try toggling script asserts, or re-download the file.
Also, I suggest updating your recovery to 2.5.1.8.

Thanks for the quick reply!
I toggled script asserts so it was enabled, for the raw unmodified zip file nothing happened, and for the extracted zip file I got an Error seven again
I've tried redownloading the file multiple times, even getting earlier versions of the rom to try.
How would I go about updating recovery? I don't have a functional usb cable at the moment unfortunately but if absolutely neccessary I can hack one up.

normankev said:
I toggled script asserts so it was enabled, for the raw unmodified zip file nothing happened, and for the extracted zip file I got an Error seven again
Click to expand...
Click to collapse
I think you should have the asserts disabled to get past the error. (use the extracted zip, which gave you the error 7)
If this does not help, probably best way to go forward is to get a usb cable and try flashing using fastboot

[Q] MDL update failing

I have a non-rooted phone with TWRP installed. When the phone tries to install the MDL update, the phone boots into recovery, but goes to TWRP. And it fails each time. Has anyone else successfully loaded the update with TWRP installed on a non-rooted phone? Do I need to remove TWRP to get this to work and, if so, how is that done?
Here's the log from TWRP:
Running boot script...
Finished running boot script.
I:Inserting 'install =/cache/321a2cb29b9c.update_SPH-L720_MDC_CSB_user_RP_to_MDL_CSB_user_RP-1.zip'
I:Copying file /cache/recovery/log to /cache/recovery/last_log
I:Attempt to load settings from settings file...
I:Loading settings from '/data/media/0/TWRP/.twrps'.
I:Backup folder set to '/external_sd/TWRP/BACKUPS/cdc9d69d'
I:Version number saved to '/cache/recovery/.version'
I:Switching packages (TWRP)
I:Set page: 'action_page'
Processing AOSP recovery commands...
I:command is: 'install' and I:value is: '=/cache/321a2cb29b9c.update_SPH-L720_MDC_CSB_user_RP_to_MDL_CSB_user_RP-1.zip'
I:Unable to mount '/usb-otg'
I:Actual block device: '', current file system: 'vfat'
I:Unable to mount '/usb-otg'
I:Actual block device: '', current file system: 'vfat'
I:Full zip path: '/external_sd/=/cache/321a2cb29b9c.update_SPH-L720_MDC_CSB_user_RP_to_MDL_CSB_user_RP-1.zip'
Installing zip file '/cache//321a2cb29b9c.update_SPH-L720_MDC_CSB_user_RP_to_MDL_CSB_user_RP-1.zip'
Installing '/cache//321a2cb29b9c.update_SPH-L720_MDC_CSB_user_RP_to_MDL_CSB_user_RP-1.zip'...
Checking for MD5 file...
I:Cannot find file /cache//321a2cb29b9c.update_SPH-L720_MDC_CSB_user_RP_to_MDL_CSB_user_RP-1.zip.md5
Skipping MD5 check: no MD5 file found.
Register_libbootloader_updater Qcom msm8960
Verifying current system...
partition read matched size 9214720 sha 752ba02ce73412313a123b43ac0ae9bc46e13d22
partition read matched size 52009728 sha 52d27452b5e779ba0fdb676c453d3f2d1f294569
2049134592 bytes free on /cache (87488677 needed)
script aborted: assert failed: getprop("ro.secure")=="1"
assert failed: getprop("ro.secure")=="1"
E:Error executing updater binary in zip '/cache//321a2cb29b9c.update_SPH-L720_MDC_CSB_user_RP_to_MDL_CSB_user_RP-1.zip'
E:Error installing zip file '/cache//321a2cb29b9c.update_SPH-L720_MDC_CSB_user_RP_to_MDL_CSB_user_RP-1.zip'
Done processing script file

I installed OUDHS ( http://forum.xda-developers.com/showthread.php?t=2254678 ) over TWRP and still get the same error I bolded from the log above.
Can someone please tell me how to get the stock recovery back? Do I need to flash/odin the base ROM? If so, where can I find the Sprint version?

You want to unroot? There are threads on the MDL update with flashable versions. Read thoroughly because a lot has changed.
Here: http://forum.xda-developers.com/showthread.php?t=2270065

jejb said:
I installed OUDHS ( http://forum.xda-developers.com/showthread.php?t=2254678 ) over TWRP and still get the same error I bolded from the log above.
Can someone please tell me how to get the stock recovery back? Do I need to flash/odin the base ROM? If so, where can I find the Sprint version?
Click to expand...
Click to collapse
Here - I placed the Stock Recovery in tar form on RWilco12's Repo. Just flash With Odin.
I'll be making a one click for this as well. (I'll also make sure all the stock items are tar'd and in one click formats.)
http://www.rwilco12.com/downloads.php?dir=Files/Devices/Samsung%20Galaxy%20S4%20%28SPH-L720%29/Recovery/Stock/MDC
As far as the update failing or not, and if you want to go back completely stock; there are also MDC NoData and Full Restore tars and in his Repo. Depending on your flash history, you may want to obtain root and use Chainfrire's Triangle Away. (Even though the i9505 variant isn't on his supported list, it does work resetting the binary counter) Then you'd want to flash the stock build.
http://www.rwilco12.com/downloads.php?dir=Files/Devices/Samsung%20Galaxy%20S4%20%28SPH-L720%29/Stock%20ROMs/MDC/

MoHoGalore said:
Here - I placed the Stock Recovery in tar form on RWilco12's Repo. Just flash With Odin.
I'll be making a one click for this as well. (I'll also make sure all the stock items are tar'd and in one click formats.)
http://www.rwilco12.com/downloads.php?dir=Files/Devices/Samsung%20Galaxy%20S4%20%28SPH-L720%29/Recovery/Stock/MDC
Click to expand...
Click to collapse
Thanks much! But I'm having an issue loading this. The Odin load started off well, but it's been sitting in the following state for like 10 minutes now. I'm afraid to unplug the phone/stop the update for fear of having a brick. Loading TWRP and OUDHS with Odin only took a few seconds, so it's not looking good.

jejb said:
Thanks much! But I'm having an issue loading this. The Odin load started off well, but it's been sitting in the following state for like 10 minutes now. I'm afraid to unplug the phone/stop the update for fear of having a brick. Loading TWRP and OUDHS with Odin only took a few seconds, so it's not looking good.
Click to expand...
Click to collapse
Looks like you renamed the file. Did you?
Pull battery, boot back into Odin mode and don't rename the file. There's no reason to. It should be .tar.md5

No. I did notice the rename when my Win7 system pulled it down, but I did nothing to it explicitly.

jejb said:
No. I did notice the rename when my Win7 system pulled it down, but I did nothing to it explicitly.
Click to expand...
Click to collapse
Look at my post above. I added a picture. There shouldn't be anything renaming it.
Download a fresh copy, pull battery, get back to Odin mode and re-flash.

MoHoGalore said:
As far as the update failing or not, and if you want to go back completely stock; there are also MDC NoData and Full Restore tars and in his Repo. Depending on your flash history, you may want to obtain root and use Chainfrire's Triangle Away. (Even though the i9505 variant isn't on his supported list, it does work resetting the binary counter) Then you'd want to flash the stock build.
http://www.rwilco12.com/downloads.php?dir=Files/Devices/Samsung%20Galaxy%20S4%20%28SPH-L720%29/Stock%20ROMs/MDC/
Click to expand...
Click to collapse
So in reading about Triangle Away, it seems I may have screwed myself up by loading a custom recovery, even though I'm not rooted? That sucks, if so. But I've not read about anyone else having issues like this and I can't be the only one to have loaded a custom recovery and tried to do the update. Thanks for the procedure, though. I guess I may have to try all of that to get back to stock (if the phone isn't bricked, still trying to load).

Delete

jejb said:
So in reading about Triangle Away, it seems I may have screwed myself up by loading a custom recovery, even though I'm not rooted? That sucks, if so. But I've not read about anyone else having issues like this and I can't be the only one to have loaded a custom recovery and tried to do the update. Thanks for the procedure, though. I guess I may have to try all of that to get back to stock (if the phone isn't bricked, still trying to load).
Click to expand...
Click to collapse
It's not bricked. It's just a failed flash. You have a few choices.
My recommendation for you;
1. Get the rooted, nodata, MDC One Click, the exe. (That way we know nothing will be renaming the file)
2. Put your phone in Odin mode and flash.
3. Go get Chainfire's Triangle Away v2.90 (This is a link to Chainfire's XDA thread which is permissible)
4. Use the app.
5. Backup anything you'd like to keep to pc.
6. Go get the Stock MDC Full Restore and flash via Odin.
Now you'll be back to stock, un-rooted and Official on build and binary and can apply the update from OTA.
You can get the stock build from the Repo.

Turns out it was IE that was forcing the rename on the file. So I pulled it down with firefox and it did not rename it. But when I try to load it, it tells me the MD5 hash did not match and ends. So I took the MD5 off the end and tried it just as a .tar file. Got the same endless load as the first time I tried it above.
I may have to go through the steps you spelled out in your last post, and I really appreciate you taking the time to do that. But shouldn't this stock recovery at least load? I'm a bit worried that if this file won't load, will the others I pull down from the same download site give me the same issues?

Give me a min and I'll upload my tested copy to dev host so you'll have an md5 to compare. Possible it was a bad upload from me to the repo.
Sent from my SPH-L720 using Xparent Skyblue Tapatalk 2
:Edit: Here's the tested copy of the Recovery. http://d-h.st/0fp

MoHoGalore said:
Give me a min and I'll upload my tested copy to dev host so you'll have an md5 to compare. Possible it was a bad upload from me to the repo.
Sent from my SPH-L720 using Xparent Skyblue Tapatalk 2
:Edit: Here's the tested copy of the Recovery. http://d-h.st/0fp
Click to expand...
Click to collapse
Thank you SO much! That copy did work successfully via Odin to put the stock recovery back on the phone. And the MDL update ran successfully after that was done. So I'm now up to the latest level and not rooted. I'll probably put the OUDHS recovery on again now that I have a good copy of the stock recovery that I can always go back to if needed.
It's folks like you that make this board such a valuable resource. Thanks again.

Good to know you got up and running. And I replaced it again on the Repo. Looks like Dev Host went down in the last few minutes so I was worried if you got it or not.
Glad to help. :beer:

[Q] Nexus 4 OTA Update failed with error

Yesterday i got a notification that my KitKat update is ready. I downloaded it restarted the phone as required but the process failed with the below error
/system/lib/hw/power.msm8960.so has unexpected contents
Downloaded the zip file and tried to flash it via TWRP and again got the same error.
Could anybody please let me know the fix. I am rooted with franco kernel r#193

Is the file modified?
Suman_Auddy said:
Yesterday i got a notification that my KitKat update is ready. I downloaded it restarted the phone as required but the process failed with the below error
/system/lib/hw/power.msm8960.so has unexpected contents
Downloaded the zip file and tried to flash it via TWRP and again got the same error.
Could anybody please let me know the fix. I am rooted with franco kernel r#193
Click to expand...
Click to collapse
Just make sure that you have not modified that file.
Also some people had the same issue and it turned out that they had the file renamed to power.msm8960.so.bak, if so
use a file explorer to rename it back to the original (without .bak), and if that still fails, download the file from the factory image and replace it, then try to flash the zip file.

Suman_Auddy said:
Yesterday i got a notification that my KitKat update is ready. I downloaded it restarted the phone as required but the process failed with the below error
/system/lib/hw/power.msm8960.so has unexpected contents
Downloaded the zip file and tried to flash it via TWRP and again got the same error.
Could anybody please let me know the fix. I am rooted with franco kernel r#193
Click to expand...
Click to collapse
same here but i have "framework-res.apk" has unexpected contents.

In order to use OTA, your system files should be stock and unmodified and it looks like you modified that file, my suggestion, is to download the factory image of your current build of 4.3 from here
https://developers.google.com/android/nexus/images#occam
check what version you have, mine was JWR66Y when I upgraded.
then extract the factory image on your desktop and copy and replace "any" file that you have modded (with TWRPs file manager + ADB), before flashing Kitkat OTA zip, (note: when replacing files make sure that system files you replace have the right permissions e.g. chmod 755)
OR you could flash the Kitkat factory image directly instead of the OTA, ONLY IF you know how to do so without wiping your device's data, remember that this can cause you problems later.
Be careful, I hope you had a nandriod backup, before this happened.

Thanks for all your sugeestions, renaming the file worked for me. Flashing the zip file now via TWRP.

Flashing the zip file failed with error error executing updater binary in zip....any suggestion

Suman_Auddy said:
Flashing the zip file failed with error error executing updater binary in zip....any suggestion
Click to expand...
Click to collapse
Please post the whole error message.

Flashing Cyanogenmod Rom Error

Device: Nexus 7 (Wi-Fi) (Old one)
Android: 4.3
When i go to flash cyanogenmod 10.2.0-grouper.zip i get this error
Updating partition details...
Installing 'usb-otg/cm-10.2.0-grouper.zip'...
Checking for MD5 file...
Skipping MD5 Check: no MD5 file found.
assert failed: getprop("ro.product.device") == "grouper" | | getprop("ro.build.pr
E:Error executing updater binary in zip '/usb-otg/cm-10.2.0-grouper.zip'
Error flashing zip 'usb-otg/cm-10.2.0-grouper.zip'
Updating partition details...
Can anyone please help this has been going on forever now and its getting super annoying.

What recovery are you using? Last I heard TWRP over 2.6.3.0 had issues. Try that certain version or use CWM
Sent from my Nexus 5

Pirateghost said:
What recovery are you using? Last I heard TWRP over 2.6.3.0 had issues. Try that certain version or use CWM
Sent from my Nexus 5
Click to expand...
Click to collapse
Lol ok ill try that. I'm on 2.6.3.1 ill try the other version of TWRP first.

How Did You Solve This?
HVC FOG3Y34 said:
Lol ok ill try that. I'm on 2.6.3.1 ill try the other version of TWRP first.
Click to expand...
Click to collapse
So can you give me a little more detail on what you did? This is my first unlock, root, custom recovery, and custom ROM ever, so if I made a mistake, I'm not sure I could even identify it. I used wugfresh's Nexus Root Toolkit to reach this point.
I have TWRP 2.6.3.1. Is the solution to flash a previous version of TWRP? If so, can you direct me to instructions for that?

StarSphere said:
So can you give me a little more detail on what you did? This is my first unlock, root, custom recovery, and custom ROM ever, so if I made a mistake, I'm not sure I could even identify it. I used wugfresh's Nexus Root Toolkit to reach this point.
I have TWRP 2.6.3.1. Is the solution to flash a previous version of TWRP? If so, can you direct me to instructions for that?
Click to expand...
Click to collapse
Hey im sorry. i don't really remember what i did, it was a very annoying time for me. All i remember is googling most of the stuff. Just google how to flash custom recovery on nexus 7 jelly bean or something. sorry...

StarSphere said:
So can you give me a little more detail on what you did? This is my first unlock, root, custom recovery, and custom ROM ever, so if I made a mistake, I'm not sure I could even identify it. I used wugfresh's Nexus Root Toolkit to reach this point.
I have TWRP 2.6.3.1. Is the solution to flash a previous version of TWRP? If so, can you direct me to instructions for that?
Click to expand...
Click to collapse
Fastboot flash recovery nameofrecoveryimage.img
It's that simple
Sent from my Nexus 5

Complete Instructions
I'm a newbie, and this is what I did. I can't take responsibility for anything that happens to anyone's device, nor answer any questions, because I only half understand it myself. I am sorry I can't include links. I am too new, and the website won't trust me to do that. So, you will have to search for these things on your own.
Download Stuff to your PC Note: Some antivirus software may trigger false positives on these kinds of files and block them from downloading, so you may have to temporarily disable the website shielding portion of your program.
1) The fastboot.exe file. If you want a big download, you can get it in the Android SDK. However, I got it from the CyanogenMod Installer. The installer failed to work with my device, but conveniently downloaded the fastboot.exe file for me. I'm not sure I would recommend this route if you don't want CyanogenMod.
2) TWRP 2.6.3.0. You can get it from androidfilehost.
Safety Stuff
1) Compare the MD5 code on the website to the one in your downloaded TWRP image.
A Windows utility to do that is called MD5 SHA Checksum Utility.
An Android utility to do that is called MD5 Checker.
2) Completely back up your current Android ROM. Nexus Root Toolkit is great for this and many other things. It can be downloaded from wugfresh.
The Custom Recovery Flash
1) Make sure USB debugging is still enabled on your Android device. The video links on wugfresh's page can show you how to do that.
2) Make sure your Android device is connected to your PC via USB cable.
3) Boot your Android device into the bootloader. I used Nexus Root Toolkit -> Advanced Utilities Launch -> Reboot Bootloader to do this, but I think you can also do it by turning your device off, then holding down the Power and Volume Down buttons simultaneously (don't quote me on that).
2) Search for the location of fastboot.exe on your PC. Mine was in my user directory, where CyanogenMod's installer left it: C:\Users\{Username}\cminstaller\bundle\win32
3) On your PC, open a command line. Go into the directory where you found fastboot.exe above.
4) Type fastboot flash recovery {Complete directory location and file name of TWRP image}. If you would rather not be using the complete directory location, you can always copy the TWRP image into the same directory as the fastboot.exe file, before doing this step.
5) The command window should soon say "finished". Mine took under 2 seconds.
6) On your Android device, the bootloader should currently have a big green arrow that says "Start". Press the volume down button until the arrow says "Recovery". Then press the power button. Your device should now start TWRP 2.6.3.0.
Best of all, using TWRP 2.6.3.0 for custom recovery, instead of the newest version, really did solve the original problem. Yeah!
Unfortunately, the next time I used Nexus Root Toolkit, it insisted on updating back to TWRP 2.6.3.1. So, hopefully I won't have to flash another ROM in the near future and the next TWRP version will fix the problem more permanently.

[Q] Miracast installation how-to (Project from Kensuke)

Hi,
The project this question is about:
Miracast on "Older" Device:
(Project can be found here: [nourl]https://github.com/kensuke/How-to-Miracast-on-AOSP/wiki[/nourl])
I'm very thankful for the work of Kensuke and his project to bring Miracast to the Nexus 7 2012 Model. I've been constantly watching it and finally its out for 4.4.2!
My problem is:
I unlocked + rooted my Nexus 7 via the Nexus Root Toolkit 1.8.0 with my current Android 4.3 Jelly Bean. I installed the "Team Win Recovery Project" but now I'm stuck on how to proceed to get the ROM from Kensuke.
Do I have to install 4.4.2 stock first or can I somehow install directly the .zip File for the "grouper" Wifi Nexus 7. A few instructions or a guide on how to install from 4.3 to 4.4.2 miracast rom would be awesome
I'm relatively new to the whole rooting scene so please be patient with me
Any help is very much appreciated!
Best regards
Halcyon

Hi, I'm Kensuke, thanks your using my ROM.
what error happen?
KK rom required latest recovery. such as TWRP 2.6.3.1

s107ken said:
Hi, I'm Kensuke, thanks your using my ROM.
what error happen?
KK rom required latest recovery. such as TWRP 2.6.3.1
Click to expand...
Click to collapse
Not really an error.
I just need to know how to get from rooted stock 4.3 with TWRP to 4.4.2 miracast ROM from you.
Do I have to install 4.4.2 stock first or can I just straight go to 4.4.2 miracast from your ROM?
And how can I install your rom? I put it on my device and then?
Looking for kind of a short/quick guide.
Thanks for replying so quickly and your great work, kensuke

MSHalcyon said:
Not really an error.
I just need to know how to get from rooted stock 4.3 with TWRP to 4.4.2 miracast ROM from you.
Do I have to install 4.4.2 stock first or can I just straight go to 4.4.2 miracast from your ROM?
And how can I install your rom? I put it on my device and then?
Looking for kind of a short/quick guide.
Thanks for replying so quickly and your great work, kensuke
Click to expand...
Click to collapse
OK
my device N7 2012 3G "tilapia" example. if your device is grouper, substitute tilapia/grouper .
Files
1) stock 4.3 - nakasig-jwr66y-factory-bdbb7bd7.tgz
2) recovery - openrecovery-twrp-2.6.3.1-tilapia.img
3) 4.4 ROM - 20131222_mira01_aosp442r1_tilapia-ota-eng.zip
latest Miracast ROM links
http://forum.xda-developers.com/showthread.php?t=2515833
How to flash 4.3 to 4.4
1) put 4.4 ROM on sdcard
$ adb push 20131222_mira01_aosp442r1_tilapia-ota-eng.zip /sdcard/
Click to expand...
Click to collapse
2) goto recovery
$ adb reboot recovery
Click to expand...
Click to collapse
3) recovery operate
wipe Data / Cache / Dalvik, Flash 4.4 ROM, reboot
Only this. Stock 4.3 to Custom 4.4 directly.
If reboot-loop happen, Full Wipe needed.
Warning!
My ROM didn't contain gapps and SuperUser.
Your data should back up before flashing.

s107ken said:
OK
my device N7 2012 3G "tilapia" example. if your device is grouper, substitute tilapia/grouper .
Files
1) stock 4.3 - nakasig-jwr66y-factory-bdbb7bd7.tgz
2) recovery - openrecovery-twrp-2.6.3.1-tilapia.img
3) 4.4 ROM - 20131222_mira01_aosp442r1_tilapia-ota-eng.zip
latest Miracast ROM links
http://forum.xda-developers.com/showthread.php?t=2515833
How to flash 4.3 to 4.4
1) put 4.4 ROM on sdcard
2) goto recovery
3) recovery operate
wipe Data / Cache / Dalvik, Flash 4.4 ROM, reboot
Only this. Stock 4.3 to Custom 4.4 directly.
If reboot-loop happen, Full Wipe needed.
Warning!
My ROM didn't contain gapps and SuperUser.
Your data should back up before flashing.
Click to expand...
Click to collapse
First of all thanks for helping me
Good guide so far I followed all your instructions, but I get the following error on the part 3) "Flash 4.4 ROM"
Log from TWRP v2.6.3.1
Updating partition details...
Installing 'sdcard/20131222_mira01_aosp442r1_grouper-ota-eng.zip'
Checking for MD5 file...
Skipping MD5 check: no MD5 file found.
Error flashing zip 'sdcard/20131222_mira01_aosp442r1_grouper-ota-eng.zip'
Updating partition details...
Click to expand...
Click to collapse
Is there a way to give you more than that log? Or do you know whats the problem here?
Thanks in advance for all your great work on the project and the help you have provided so far!

I have only tilapia.
Current ROM - Factory 4.3 - JWR66Y - nakasig-jwr66y-factory-bdbb7bd7.tgz
download mira roms from google drive, check md5 carefully
20131222_mira01_aosp442r1_tilapia-ota-eng.zip
md5sum:f642d88304b86cd788e09c1e0d06ff82
20131222_mira01_aosp442r1_grouper-ota-eng.zip
md5sum:6f60ec33438fc9b6d9ad355ffbaf676b
Flashing log...
Code:
Updating partition details...
Installing '/sdcard/20131222_mira01_aosp442r1_tilapia-ota-eng.zip'...
Checking for MD5 file...
Skipping MD5 check: no MD5 file found.
// about 30~ seconds
script succeeded: result was [/system]
Updating partition details...
Code:
Installing '/sdcard/20131222_mira01_aosp442r1_grouper-ota-eng.zip'...
Checking for MD5 file...
Skipping MD5 check: no MD5 file found.
This package is for "grouper" devices; this is a "tilapia".
E:Error executing updater binary in zip '/sdcard/20131222_mira01_aosp442r1_grouper-ota-eng.zip'
Error flashing zip '/sdcard/20131222_mira01_aosp442r1_grouper-ota-eng.zip'
Updating partition details...
I don't know your trouble. maybe download error?

s107ken said:
I have only tilapia.
Current ROM - Factory 4.3 - JWR66Y - nakasig-jwr66y-factory-bdbb7bd7.tgz
download mira roms from google drive, check md5 carefully
20131222_mira01_aosp442r1_tilapia-ota-eng.zip
md5sum:f642d88304b86cd788e09c1e0d06ff82
20131222_mira01_aosp442r1_grouper-ota-eng.zip
md5sum:6f60ec33438fc9b6d9ad355ffbaf676b
Flashing log...
Code:
Updating partition details...
Installing '/sdcard/20131222_mira01_aosp442r1_tilapia-ota-eng.zip'...
Checking for MD5 file...
Skipping MD5 check: no MD5 file found.
// about 30~ seconds
script succeeded: result was [/system]
Updating partition details...
Code:
Installing '/sdcard/20131222_mira01_aosp442r1_grouper-ota-eng.zip'...
Checking for MD5 file...
Skipping MD5 check: no MD5 file found.
This package is for "grouper" devices; this is a "tilapia".
E:Error executing updater binary in zip '/sdcard/20131222_mira01_aosp442r1_grouper-ota-eng.zip'
Error flashing zip '/sdcard/20131222_mira01_aosp442r1_grouper-ota-eng.zip'
Updating partition details...
I don't know your trouble. maybe download error?
Click to expand...
Click to collapse
I redownloaded the file and checked md5 before, it didn't work because on mac it automatically first extracts your zip file. I downloaded it now without extraction and it worked! Thank you so much for your help.
Installed all google apps after that, worked like a charm!!