So I've searched and read for about the last 4 hours, and I'm only more confused than before.
Using a Verizon VS980:
1.Took the OTA (to VS96012B) when I first got the phone
2. Rooted using ioroot script
3. installed latest twrp (2.6.3.3) using Freegee
4. Downloaded CM10.2 stable directly from Get.cm as well as appropriate GAPPS
5. Rebooted into TWRP
6. Wiped (but did not backup since I didn't care about keeping user data...did this wipe the factory OS too then?)
7. Attempted to flash CM10.2 and got the following error:
"Skipping MD5 check: no MD5 file found.
assert failed: run_program("/system/bin/loki.sh
E:Error executing updater binary in zip '/sdcard
Error flashing zip '/sdcard/download/cm-10.2.0
8. Attempted to reboot into stock since CM flash had failed and got "secure booting unsuccessful" error message
Why would the CM10.2 install be failing under the above messages? And did I blow away my factory ROM? I just used the generic TWRP 2.6.3.3 "factory reset option"??
Dear lord help me. I've read so many threads, but I've ended up much more confused.
In theory, the stock ROM should still be installed since the CM10.2 flash failed, what do I need to do to A.)Be able to successfully flash the CM10.2 without getting the "error executing updater binary in zip" problem, or B.) Be able to at least boost back into stock LG image?
Thanks,
-A
Planning on using this to go back to how it shipped stock, and then re-rooting, and re-installing TWRP and taking another shot at a ROM. Can someone please tell me if this is the right direction?
http://forum.xda-developers.com/showthread.php?t=2449670
After going back to stock I would go this route if u take 12b OTA.
http://forum.xda-developers.com/showthread.php?t=2587296
Sent from Verizon logo plastered G2 bastard
Thanks for the reply! I've edited the OP for a little additional detail/clarity. I'm trying to figure out at this stage why my CM10.2 install failed first and foremost. I'd like to be able to avoid going all the way back to stock if possible?
Any suggestions on why I was getting the below message during attempting to install?
"
Attempted to flash CM10.2 and got the following error:
"Skipping MD5 check: no MD5 file found.
assert failed: run_program("/system/bin/loki.sh
E:Error executing updater binary in zip '/sdcard
Error flashing zip '/sdcard/download/cm-10.2.0
"
amazonparrot said:
Thanks for the reply! I've edited the OP for a little additional detail/clarity. I'm trying to figure out at this stage why my CM10.2 install failed first and foremost. I'd like to be able to avoid going all the way back to stock if possible?
Any suggestions on why I was getting the below message during attempting to install?
"
Attempted to flash CM10.2 and got the following error:
"Skipping MD5 check: no MD5 file found.
assert failed: run_program("/system/bin/loki.sh
E:Error executing updater binary in zip '/sdcard
Error flashing zip '/sdcard/download/cm-10.2.0
"
Click to expand...
Click to collapse
It seems like the recovery u flashed from freegee was not properly loki'd for the 12b firmware. It allowed u to overwrite the stock recovery but not flash any ROMs. U could try pushing the patched Loki img and recovery in the thread I posted earlier using adb. U can follow the same instructions in the thread u linked just use the updated patched files.
When u wiped prior to flashing cm10.2, if u wiped system then u have no ROM on ur device to boot into. Always make a backup just in case. That way if u have a bad download or the ROM just won't boot, u gotta plan B.
Sent from Verizon logo plastered G2 bastard
truckroot said:
It seems like the recovery u flashed from freegee was not properly loki'd for the 12b firmware. It allowed u to overwrite the stock recovery but not flash any ROMs. U could try pushing the patched Loki img and recovery in the thread I posted earlier using adb. U can follow the same instructions in the thread u linked just use the updated patched files.
When u wiped prior to flashing cm10.2, if u wiped system then u have no ROM on ur device to boot into. Always make a backup just in case. That way if u have a bad download or the ROM just won't boot, u gotta plan B.
Sent from Verizon logo plastered G2 bastard
Click to expand...
Click to collapse
If I just used the standard TWRP Wipe/factory reset, (which I did) my factory system ROM should be still there, but for whatever reason I'm unable to boot it.
I'm assuming the threads and methods you referenced will work with ADB sideload?
Thanks again
amazonparrot said:
If I just used the standard TWRP Wipe/factory reset, (which I did) my factory system ROM should be still there, but for whatever reason I'm unable to boot it.
I'm assuming the threads and methods you referenced will work with ADB sideload?
Thanks again
Click to expand...
Click to collapse
Yeah. I would try pushing the patched Loki img via adb, then try flashing the cm10.2 ROM. Otherwise u can sideload a stock ROM and flash that.
Sent from Verizon logo plastered G2 bastard
Managed to get back to stock!
Re-rooted, and used Freegee to install latest CWM ths time. Attempted to install CM10.2 again (fresh download) and it STILL gives the error:
Attempted to flash CM10.2 and got the following error:
"Skipping MD5 check: no MD5 file found.
assert failed: run_program("/system/bin/loki.sh
E:Error executing updater binary in zip '/sdcard
Error flashing zip '/sdcard/download/cm-10.2.0
Why am I still unable to flash a ROM?
amazonparrot said:
Managed to get back to stock!
Re-rooted, and used Freegee to install latest CWM ths time. Attempted to install CM10.2 again (fresh download) and it STILL gives the error:
Attempted to flash CM10.2 and got the following error:
"Skipping MD5 check: no MD5 file found.
assert failed: run_program("/system/bin/loki.sh
E:Error executing updater binary in zip '/sdcard
Error flashing zip '/sdcard/download/cm-10.2.0
Why am I still unable to flash a ROM?
Click to expand...
Click to collapse
Read that some are having issues using Freegee/Flashify to install a working loki'd recovery with 12b OTA. ADB seems to work best. Glad to hear u were able to get back to stock though.
Sent from Verizon logo plastered G2 bastard
I'm actually on 11A :-/
I was planning on using CM10.2 since I just want a 4.3 or 4.4 ROM thats actually stable, but maybe its just the particular ROM I'm trying? I'll try doing ADB to push a different recovery just in case.
Any recommendations on a good stable ROM?
amazonparrot said:
I'm actually on 11A :-/
I was planning on using CM10.2 since I just want a 4.3 or 4.4 ROM thats actually stable, but maybe its just the particular ROM I'm trying? I'll try doing ADB to push a different recovery just in case.
Any recommendations on a good stable ROM?
Click to expand...
Click to collapse
The unofficial cm 4.4.2 is a good one. OP has good directions on getting ROM to run perfectly with kernel settings.
If ur on 11a u should have zero issues flashing, def try a different ROM.
Sent from Verizon logo plastered G2 bastard
Same error... kinda freaking out now #FML
I am so lost and confused. Definately in over my head right now. I usually depend on the one click methods to flash, and this time I'm bricked. Same problem as post #1 on the thread. Not very familiar with adb. Is anyone with experience in this area able/willing to remote into my mac or even over the phone to help a brother out? I'm willing to compensate you for your time.
Thanks,
Vinnie
Related
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.
Hey guys,
I am having an issue flashing the stock android 4.2.2, coming from factory 4.2.1 only rooted. I downloaded the factory image from http://www.androidpolice.com/2013/0...us-7-3g-android-4-2-2-update-jdq39-right-now/ when I try to flash the zip file in TWRP i get an error assert failed: apple_patc h_check ("system/app/browserproviderproxy.apk
E: Error in /sdcard/"name of zip file" error flasing zip
the files that it is trying to patch do not exist in the file system. I attempted temp unroot to see if that would do it. The official OTA came through, rebooted recovery but did nothing.
Any suggestions?
Had the same issue with TWRP. With the ClockWorkMod Recovery this part works. If you made any modifikations like camera resolution, enabling of wifi tethering or what else, extract the system.img file from the factory image and flash this first to make sure that you really are on stock 4.2.1 ...
And thats it have fun with the new version 4.2.2
Best regards ...
Ah I did not think of that with the wifi tethering, how do I flash the system.img file, using ADB?
affiaff said:
Had the same issue with TWRP. With the ClockWorkMod Recovery this part works. If you made any modifikations like camera resolution, enabling of wifi tethering or what else, extract the system.img file from the factory image and flash this first to make sure that you really are on stock 4.2.1 ...
And thats it have fun with the new version 4.2.2
Best regards ...
Click to expand...
Click to collapse
I'm having an issue here as well.
I'm stock, except I did enable wifi tethering.
I can't update via CWM or OTA, because I get an error during the process.
I tried to pull the system folder out of 4.2.1 and flash that through CWM, but I also get an error when it checks the current system.
EDIT: I finally got updated. It was serious scare for a bit though. The toolkit really messed things up at first. I had to flash back to 4.2.1. After using the toolkit and having failed attempt after failed attempt, I realized I had to reflash the stock recovery first. I was then able flash the stock 4.2.1 image, reflash CWM recovery, and use CWM to install the update. There are still things that are screwy, and I've lost root (the root restore app isn't seeing it as being recoverable, but I'm tired and probably missing something). Anyways, most of my data is in tact, aside from a couple odd issues, so the rest I'll deal with tomorrow. The device does feel more responsive, so I suppose it was worth the bother, but I definitely will not be installing that tethering mod again.
So now I am little bit confused.
Downloaded the OTA update from the Google server copied it to my N7, applied the update from within TWRP 2.6.3.1.
In fact, it was running through until almost the end (I thought, wow, finally an update which works).
But then Error message:
"Error executing updater binary in zip 'sdcard/goomanager/13088e35942c77e4752aa1fdf51d54472509b941.signed-nakasi-KRT16O-from-JWR66Y.13088e35'
Error flashing zip 13088e35942c77e4752aa1fdf51d54472509b941.signed-nakasi-KRT16O-from-JWR66Y.13088e35"
Reboot System brings me back to Recovery TWRP.
Somehow I have no clue what to do next.
Can give someone a hint?
Cheers
Tom
tom1807 said:
So now I am little bit confused.
Downloaded the OTA update from the Google server copied it to my N7, applied the update from within TWRP 2.6.3.1.
In fact, it was running through until almost the end (I thought, wow, finally an update which works).
But then Error message:
"Error executing updater binary in zip 'sdcard/goomanager/13088e35942c77e4752aa1fdf51d54472509b941.signed-nakasi-KRT16O-from-JWR66Y.13088e35'
Error flashing zip 13088e35942c77e4752aa1fdf51d54472509b941.signed-nakasi-KRT16O-from-JWR66Y.13088e35"
Reboot System brings me back to Recovery TWRP.
Somehow I have no clue what to do next.
Can give someone a hint?
Cheers
Tom
Click to expand...
Click to collapse
i am in the same boat
Not really helpful, but I found a post that TWRP could be the culprit. (maybe doesn't work in CWM also)
Found some comments here: http://www.droid-life.com/2013/11/1...krt16o-official-update-for-nexus-7-2012-wifi/
I boot now into the bootloader, try to flash from there
tom1807 said:
Not really helpful, but I found a post that TWRP could be the culprit. (maybe doesn't work in CWM also)
Found some comments here: http://www.droid-life.com/2013/11/1...krt16o-official-update-for-nexus-7-2012-wifi/
I boot now into the bootloader, try to flash from there
Click to expand...
Click to collapse
TWRP is fine. Myself and others have installed the OTA via TWRP without issue. Did you download the OTA with Goomanager? I can't think of another reason the OTA zip would be in there, but let me know otherwise.
If that is the case, download the ota http://android.clients.google.com/packages/ota/google_nakasi/13088e35942c77e4752aa1fdf51d54472509b941.signed-nakasi-KRT16O-from-JWR66Y.13088e35.zip from Google's servers, push it to /sdcard/Download/ via adb and try again.
Thanks, but I downloaded from the Google server.
During installation I get metadata_set_recursive: error
Sent from my Nexus 4 using Tapatalk
tom1807 said:
Thanks, but I downloaded from the Google server.
During installation I get metadata_set_recursive: error
Sent from my Nexus 4 using Tapatalk
Click to expand...
Click to collapse
Have you modified any system apps, build.prop, kernel, etc?
No, not at all. Only root and twrp
Edit:
Exact error message: set_metadata_recursive: some changes failed
Problem solved:
Followed this guide (except the bootloader-grouper-4.23.img and KitKat is booting
Nexus 7 2012 automatically boots into recovery
My Nexus 7 automatically re-boots into recovery. The previous steps was not very helpful.. Please advise.
nolan111 said:
My Nexus 7 automatically re-boots into recovery. The previous steps was not very helpful.. Please advise.
Click to expand...
Click to collapse
He flashed the 4.3 JWR66Y factory image and then installed the OTA.
comminus said:
He flashed the 4.3 JWR66Y factory image and then installed the OTA.
Click to expand...
Click to collapse
Yup that is what I had to do. I flashed the factory image with WugFresh's NRT. I accidentally deleted the OS as well from my tab. Thankfully I had saved a copy of TB on my PC. TB saves the day yet again. However, I was still not able to sideload the OTA for KitKat. I keep getting Error: Device not found error message on command prompt? I guess I'll wait for the factory image to be uploaded by Google and then flash the files.
Hi Everyone,
I have tried and tried, but my phone refuses to let CM11 install. I had been running CM10.2, but I had all sorts of issues, so I decided to go all the way back to stock, re-root, get twrp again. It still won't install CM11. TWRP just says "failed" The log in twrp says:
set_metadata_recursive: some changes failed
E:Error executing updater binary in zip "/sdcard/Roms/cm-11-xyzblah.zip
Error flashing zipo '/sdcard/Roms/cm-11-xyzblah.zip'
Updating partition details
Any ideas? Any help would be greatly appreciated.
Bob
I like TWRP for the OTG support.
You need to update the latest version:
http://forum.xda-developers.com/showthread.php?t=2587296
(flash from current recovery).
Try flashing Philz. Its based on CWM but much better. (Includes OTG)
Plus you can still use any backup you made in TWRP
Sent from my LG-D802 using Tapatalk
hyperxguy said:
I like TWRP for the OTG support.
You need to update the latest version:
http://forum.xda-developers.com/showthread.php?t=2587296
(flash from current recovery).
Click to expand...
Click to collapse
Hmm, okay, thanks. I see the .lok files on there, but I don't know what to do with them. I did have an older version of TWRP. I went through the process they detail in that thread with the old one, but I just flashed the newest version from twrp. Do I need to go back through and do something with loki? This part gets me very confused.
I am looking help from someone who knows TWRP. My phone accidentally did an update and now it just boots into TWRP v2.6.3.2. I am new to this stuff but through learnings I have pushed the stock firmware found on this site (I am in Canada and with Telus) using adb push through command prompt. However when i go to install, it fails. I have also tried Rogers and Bell. Nothing works. I don't understand what is wrong?
What I see is:
E: storage partition '//TWRP/BACKUPS/018bf7ce0f4c6fa0' not found
Installing '/sdcard/TelusD803T10B_00.zip
Checking for MD5 file ...
Skipping MD5 check: no MD5 file found.
Verifying zip signature ...
E:Zip signature verification failed: 1
Error flashing zip '/sdcard/TelusD803T10B_00.zip
Can anyone please tell me what is going on here and what is wrong? I would really appreciate it. The phone is new and useless to me right now as is .... thank you
Did you did an OTA update while on custom ROM? have you tried other recovery? I had trouble flashing with TWRP too. Im using Philz Touch atm and it works great for me.
super114 said:
Did you did an OTA update while on custom ROM? have you tried other recovery? I had trouble flashing with TWRP too. Im using Philz Touch atm and it works great for me.
Click to expand...
Click to collapse
All I did was accept an update when prompted but didn't pay attention and when the phone rebooted it went into twrp. I had no idea what twrp was. through learning about it i got the stock roms off this website and pushed it on to the phone and tried to install but it just fails for some reason. i don't know what more i can do.
Follow the"back to stock threads" you cant accept ota's when rooted
Sent from my LG-D800 using Tapatalk
I would follow the above comment and follow the step by step guide how to get back to stock when you accidentally got OTA when rooted. Just follow the steps carefully and you'll be fine.Good luck
Have you tried this?
Just untick Zip File Signature when prompting to flash zip.That might work