I am stock. I did have the phone rooted, to update swype, but have since unrooted with the auto root and am trying to upgrade.
I renamed the file to update.zip and placed it on my sd card, it wouldn't read the internal memory.
The upgrade status bar moves a little, then goes away and the phone just sits at the android screen with !. I hit menu and it takes me back to the stock loader and displays the following error.
assert failed: apply_patch_check("/system/app/AccountAndSyncSettings.apk", "4261bad3b74be40688f02d082d3f6a264bff28ec", "aed607fdd6c6a0da665f1f91dc8d1b76fdd435b0")
E:Error in /tmp/sideload/package.zip
(status 7)
Bielinsk said:
I am stock. I did have the phone rooted, to update swype, but have since unrooted with the auto root and am trying to upgrade.
I renamed the file to update.zip and placed it on my sd card, it wouldn't read the internal memory.
The upgrade status bar moves a little, then goes away and the phone just sits at the android screen with !. I hit menu and it takes me back to the stock loader and displays the following error.
assert failed: apply_patch_check("/system/app/AccountAndSyncSettings.apk", "4261bad3b74be40688f02d082d3f6a264bff28ec", "aed607fdd6c6a0da665f1f91dc8d1b76fdd435b0")
E:Error in /tmp/sideload/package.zip
(status 7)
Click to expand...
Click to collapse
Are you running from stock recovery or CWM? That is the first file the updater is checking for, so the install failed at virtually the first step.
I am trying from stock recovery.
after that failed, I did put on CWM and try from there, same issue.
Right now I am back to stock, with only root.
Bielinsk said:
I am trying from stock recovery.
after that failed, I did put on CWM and try from there, same issue.
Right now I am back to stock, with only root.
Click to expand...
Click to collapse
I guess the other possibility is the error is further down in the check list and this is just what is displaying on your screen.
I'm sure you can slowly go through and figure out what file it is complaining about, but probably the quickest way to get the update to work is to flash the EG30 kernel/ROM in ODIN. Your data should be preserved.
http://forum.xda-developers.com/showthread.php?t=1383927
BTW I don't believe you need to rename to update.zip. I know I mentioned that earlier, but that is just force of habit from other platforms. Also as you discovered, the stock recovery only looks on the external SD card for updates.
Thanks for the help. I will try to flash through ODIN back to stock and see if I can update from there.
Well knowing that you don't want clean out everything on your phone, do a back up of the app's or data that you want/need, and place it on the pc as a back up, then just fully restore the phone, or odin to a full stock eg30 then use the update zip, then Root and reinstall all the data you want from your back ups back
Doing the one click back to stock eg30 seems to allow the update to complete.
Thank you for your time and assistance.
Are you sure ur Modem is eg30?? And not eg31!!
Bobby O'S Epic Touch..
rob97ss said:
Are you sure ur Modem is eg30?? And not eg31!!
Bobby O'S Epic Touch..
Click to expand...
Click to collapse
Yes, I never applied any modem.
After update, it appears I am up to EK02, 2.3.6 and now re-rooting.
Bielinsk said:
Doing the one click back to stock eg30 seems to allow the update to complete.
Thank you for your time and assistance.
Click to expand...
Click to collapse
Though i mentioned it on the message to do that first lol, but hey you got it! and welcome bro , but glad that i was of some help to you.
i'm having the same issue, can't figure this out.
I rooted using this method - http://forum.xda-developers.com/showthread.php?t=1321582
and unrooted using the same method.
So now i'm stock and unrooted, can't get this update to work, getting the same errors as the first post.
Please let me know what i should do.
Honestly I would ODIN the EK12 leak. It removes CIQ.
trying to fix this without rooting and/or wiping everything...
Signature Failed
Hi all,
So I was on EG31 and odined back to EG30 so my baseband is S710.10 S.EG30 and my kernel is CL435734. I'm trying to update to EK02. I was getting the OTA message when I was on EG31 but now I'm not getting it anymore. I'm now trying to manually flash it but I keep getting the message below. If anyone has seen this before, help would be appreciated.
In stock recovery mode:
-- Install /sdcard ...
Finding update package...
Opening update package...
Verifying update package...
E:signature verification failed
install_package = (2)
Installation aborted.
Thanks,
BlueKalel
Please verify you are using STOCK RECOVERY (not CWM) and you downloaded the Official Sprint EK02 OTA update.
Also verify you put the update on EXTERNAL SD.
The official Sprint update link is available in the Auto Root sticky (Resource #A10)
sfhub,
I re-odined EG30 again using http://forum.xda-developers.com/showthread.php?t=1383927. then downloaded the OTA EK02 from reference A10 stock recovery version and I still get the same error. I get the Triangle with the exclamation mark and android guy. I hit menu and it shows me the error.
Any other suggestions?
Thanks,
BlueKalel
BlueKalel said:
I hit menu and it shows me the error.
Click to expand...
Click to collapse
What is the error it shows?
Could you confirm you put the Sprint OTA on the external SD?
The error is the same as above.
The file I download was 182a027d4f63.SPH-D710_update_EG30_to_EK02.zip. And I placed it in both /sdcard and
/sdcard/external_sd
Sent from my SPH-D710 using XDA App
BlueKalel said:
The error is the same as above.
The file I download was 182a027d4f63.SPH-D710_update_EG30_to_EK02.zip. And I placed it in both /sdcard and
/sdcard/external_sd
Sent from my SPH-D710 using XDA App
Click to expand...
Click to collapse
It is strange because it isn't even getting to the point of trying to install the update. It is complaining the the zip is corrupted (or the files in the zip aren't what it is expecting). This could either be because the files really are incorrect, the zip is corrupted, or the recovery program isn't stock (thus is checking the wrong signatures)
Can you get an md5sum on the update file you put on your external SD (not the one on your PC)?
It should match
182a027d4f63.SPH-D710_update_EG30_to_EK02.zip [MD5: 49bc6cab6887015557a4d4950813c554]
Ok great got it to work. The MD5 was incorrect got a new one checked MD5 then flashed now I'm running ek02.
Thanks!
Sent from my SPH-D710 using XDA App
Related
Alright, so last night I saw that the CM nightly build had been working for others so I decided to try it. I wiped and flashed but got a boot loop. I went back to recovery to try to wipe and reflash but the flash failed halfway through. I go to hboot and see that I'm back to S-ON... So now I'm stuck with a phone that won't boot, won't let me flash a rom in recovery, and won't even let me install the stock rom with hboot. I spent about 4 hours on it last night messing around with fastboot and trying apache14's OTA rollback method but was never able to get it to work. The adb shell won't recognize that I have the edited misc.img on my sd, even with a newly formatted card with no other data. Before anyone states the obvious, I was using the first version of the G2 clockwork mod, and if there was an option for a backup in there, I didn't see it anywhere. Any help is appreciated. Thanks in advance.
man i've been trying to help someone in a similar spot for 2 days now. so do u still have a custom recovery on there now?
so hboot recognizes the stock rom? what exactly happens when you try to flash it?
Yeah I managed to get a newer clockwork on here. Turns out a friend of mine just bought a G2 so I'm going to attempt to make a nandroid backup of his and apply it to mine. Think that will work?
It recognizes it, but just says "Main version is older! Update fail!" after it scans the image. I assume that's because I had the ota applied before I flashed the cm rom.
thenpaxtongoes said:
Yeah I managed to get a newer clockwork on here. Turns out a friend of mine just bought a G2 so I'm going to attempt to make a nandroid backup of his and apply it to mine. Think that will work?
It recognizes it, but just says "Main version is older! Update fail!" after it scans the image. I assume that's because I had the ota applied before I flashed the cm rom.
Click to expand...
Click to collapse
you should be able to just flash a rom in recovery. do full wipe then apply one of these roms:
mine: http://forum.xda-developers.com/showthread.php?t=836042
pauls: http://forum.xda-developers.com/showthread.php?t=836784
btw-your alot better off then the guy im trying to help
Alright, I'm downloading it. I don't see why this would work when the desire rom and CM roms didn't but it's definitely worth a try. Thank you for the help. I'll post my results in a minute.
Edit: Nope
It starts to install and then:
Finding update package...
Opening update package...
Installing update...
Formatting SYSTEM:...
E:
"system" wipe failed!
E: can't format system:
E: Failure at line 6
format System:
installation aborted
thenpaxtongoes said:
Alright, I'm downloading it. I don't see why this would work when the desire rom and CM roms didn't but it's definitely worth a try. Thank you for the help. I'll post my results in a minute.
Edit: Nope
It starts to install and then:
Finding update package...
Opening update package...
Installing update...
Formatting SYSTEM:...
E:
"system" wipe failed!
E: can't format system:
E: Failure at line 6
format System:
installation aborted
Click to expand...
Click to collapse
hmm thats a little more info then u gave last time. which rom did u try?
Your odex rom. And I actually tried Paul's rom last night with the same results. I have to go to work right now so there's not much else I can do but I appreciate the help. I'm really banking on the nandroid restore of my friend's g2 backup working but we'll see what happens.
I had this happen to me also. Since you have clockwork recovery installed, you should be able to use the instructions in this post using adb while in recovery mode:
forum.xda-developers.com/showthread.php?t=831398
The only change you'll have to make is you need to mount the sdcard in order to follow the instructions.
mount -o rw -t vfat /dev/block/mmcblk1p1 /sdcard
/cache also has available space so you might be able to use that without mounting /sdcard.
Hope this helps!
remember that in his first post he said that the phone has reverted to s-on. you've tried the original unrooted stock ROM? because with s-on I don't think you'll be able to flash any of pre-rooted ROM.
Mine had clockwork installed when I tried to install the signed ship rom in order to revert back to stock so I was s-on also. It appears that mmcblk0p17 was not WP in clockwork recover in my case, so I was able to dd the modified image to that partition through adb and then the shipped rom was able to flash normally.
Thank you again for all your help guys, but the nandroid backup worked. Though I am stuck on baconbits and my wifi card is not working at the moment all I need to do is follow the unroot instructions and i'll be fine. I hope...
Sent from my T-Mobile G2 using XDA App
Ok. So I've rooted using Zedomax's Kernal.
I'm not trying to make a back-up of my stock ROM, but there is an issue.
Code:
-- Installing package...
Finding update package...
Opening update package...
Verifying update package...
[COLOR="Red"]E:failed to verify whole-file signature
E:signature verification failed[/COLOR]
Installation aborted.
[code]
I'm having some weird verification issue. I'm trying to make a back-up of my Stock ROM since that is VERY important. :p, but as you can see, I can't. Any ideas?
I've been searching, but I've seen things on where people are trying to flash a ROM and having this issue. It was solved by renaming the ROM to update.zip. As you can see, I'm not trying to flash a ROM, I'm trying to make a back-up, so that's not going to work for me.
Thanks for any help. Finally got my phone back from that guy over on mobiletechvideos, and I'm not trying to get it bricked again. Taking precautions. :cool:
FIXED (I think): So All I did was flash CWM using Odin instead of using ROM Manager, and it gave me CWM instead of the Stock Recovery. So now I was able to make a back-up.
I think I lost my Root, but since I have a back-up I don't really care anymore. I'll just flash the Kernal again and then just flash Starburst.
Hanging on Clockwork Mod
I did exactly what you did, and then reflashed ZedoMax's ROM, but think it did not work right. When I reboot into recovery, I get the exclamation point inside a triangle with little green android guy, and have to hold down power button long time and _then_ it reboots into clockwork mod. That’s not right, is it? It's a SGS2, Sprint, rooted, and then ran into same trouble as you: Recovery 3e requires signature verification for flashing external files, so it balked, throws error can't read file signature, hard stop. Replaced CWM with this: acs-eb30-clockwork-epic-touch-4g-sep-20-4-00-pm.tar to try to get around rebooting issue, but I am not good to go yet, am I? Do I have to go back to stock and start over?
Same problem. Anyone?
pdaddy said:
Same problem. Anyone?
Click to expand...
Click to collapse
If you want a kernel that overclocks, I say go with Rogue Desperado. Zedomax hasn't been updated in a long time and you will get a lot more user support because most people overclocking are either using Rogue with SETCPU or repacked stock with Tegrak app. I honestly don't remember if Zedomax even has the latest version of CWM which is 5.0.2.7. If you want to play it safer, go with one of the kernels I mentioned and you wont have any issues with backups or restoring them
Sent from my SPH-D710 using xda premium
not enough posts to mention my issue in THIS THREAD
NEW Epic today...fresh out of the box, did the OTA to GB and then followed THESE DIRECTIONS verbatim
When I go into CWM and I go to 'update from .zip' when I select the ACS ICS .zip It ABORTS "e-signature failed..."
What am I doing wrong?
I DL'd all the files in the directions on my laptop first, then moved them to my SD card, if that matters at all...
When you go to "Install ZIP from SD card", it should open up a new menu. On that menu hit "toggle signature verification" and it should say "Signature check: disabled", then wipe all your caches three times and try reinstalling.
andr0idn00b said:
not enough posts to mention my issue in THIS THREAD
NEW Epic today...fresh out of the box, did the OTA to GB and then followed THESE DIRECTIONS verbatim
When I go into CWM and I go to 'update from .zip' when I select the ACS ICS .zip It ABORTS "e-signature failed..."
What am I doing wrong?
I DL'd all the files in the directions on my laptop first, then moved them to my SD card, if that matters at all...
Click to expand...
Click to collapse
Update from zip is only for OTA official releases from Sprint. You need CWM and to choose install from zip, then choose zip from sd card will be on your next menu. If you do not have "Install from Zip" then your CWM did not stick and you might have missed something in the rooting process.
That's exactly the issue...CWM will NOT take...I've even wiped back to FroYo, redone the OTA, and tried to do it all again, via Odin. Odin shows successfull each time...but when I do the "3 finger grip" it is simply the Android recovery, NOT CWM. WTF?
I miss the FroYo "one click root" lol
AAARRGGHHH
No it won't if you didn't put in CWM and then install a kernel right away. Why didn't you just flash ACS from rooted froyo? The OTA was BS and caused problems rooting. If you are dead set on rooting the OTA then follow the following or go back to froyo and flash ACS:
http://forum.xda-developers.com/showthread.php?t=1339478&highlight=root+EI22+OTA
I did it that way because I got a new Epic, after my old rooted FroYo phone broke.
I have wiped my new one back to stock FroYo...from stock froyo, what is the easiest method to get ACS ICS? don't be scared to talk me like I'm a 3 year old lol
I'd rather feel stupd with working ACS ICS, than smart with a bricked Epic lol
THANKS!
OK, do the one click root for CWM 3.1.0.1 here:
http://forum.xda-developers.com/showthread.php?t=1076967
Then you should be able to flash your ROM from there. Then if you want the new EI22 modem, you can flash the new modem in clockwork from here:
http://forum.xda-developers.com/showthread.php?t=1123103
Thanks
I'll do it in the morning, and post up the result
Thanks again for the help
OK, did it like that, and everything is ok now.
I did it to my wife's Epic (new out of the box also) and it WILL not update to the EI22 modem
'script aborted (no error message)E:Error in /sdcard/modem.EC05toEI22.zip
(Status 7)
Installation aborted.'
I have re-loaded it onto the SD card, and have even used the SD card from my phone (knowing that it worked ok in mine)
WTF?
andr0idn00b said:
OK, did it like that, and everything is ok now.
I did it to my wife's Epic (new out of the box also) and it WILL not update to the EI22 modem
'script aborted (no error message)E:Error in /sdcard/modem.EC05toEI22.zip
(Status 7)
Installation aborted.'
I have re-loaded it onto the SD card, and have even used the SD card from my phone (knowing that it worked ok in mine)
WTF?
Click to expand...
Click to collapse
What modem is she on? Check the baseband in settings. If she is on EC05, redownload the file and try again. Check her CWM version. Should be purple letters (3.1.0.1) or cyan (5.0.2.7).
I did hers like 10 minutes after mine, with the same files that worked for mine lol
yes, she is on EC05.
I will redownload it tomorrow, when I have a solid signal (epic for wifi to my laptop)
Speaking of, slightly OT, what is the best method to use my epic for my wifi signal for my laptop with the ACS ICS? (wireless tether, wifi tether, etc...)
andr0idn00b said:
I did hers like 10 minutes after mine, with the same files that worked for mine lol
yes, she is on EC05.
I will redownload it tomorrow, when I have a solid signal (epic for wifi to my laptop)
Speaking of, slightly OT, what is the best method to use my epic for my wifi signal for my laptop with the ACS ICS? (wireless tether, wifi tether, etc...)
Click to expand...
Click to collapse
The Wireless Hotspot should be on that ROM. It is native to the phone so works best.
Which CWM is her phone on? Same version as yours?
yes, same everything as mine...just re-downloaded the EC05 to EI22 and tried it again on her phone...same results...
any suggestions?
andr0idn00b said:
yes, same everything as mine...just re-downloaded the EC05 to EI22 and tried it again on her phone...same results...
any suggestions?
Click to expand...
Click to collapse
It reads like an sd card error. Are you choosing install zip from sd card? Maybe try to Odin the EC05 modem in and then try it. What does her baseband say?
Sent from my SPH-D700 using XDA App
yeah, install .zip from SD card. Everything else on the SD is accessible.
I have not really played with Odin much...how do I upload it using that?
Baseband still EC05...CHECK THAT!!! IT WAS EC05...
I just looked at it now, and it's EB13? WTF?!?
I have a EC05.zip.
Should I load that, via CWM, then run the EC05 to EI22?
reloaded EC05 modem via Odin
Then CWM EC05 to EI22
FIXED!!
andr0idn00b said:
reloaded EC05 modem via Odin
Then CWM EC05 to EI22
FIXED!!
Click to expand...
Click to collapse
AH! Glad to help.
Hi,
I have a GSM Galaxy Nexus (yakju) on Jelly Bean 4.1.1, rooted. Had CWM but flashed stock recovery to resolve the below-mentioned issue with OTA.
I've been having some trouble updating to OTA 4.1.2. Whenever I get the OTA push, I proceed with the upgrade but the process fails. I get the following error messages in recovery:
Code:
Finding update package...
Opening update package...
Verifying update package...
Verifying current system...
assert failed: apply_patch_check("/system/app/Gmail.apk", "d547e1c4367c20c48614c2623c9e30f72976bf67", "21177453e64d114f4c208720a0f57d9765665a1d")
E: Error in /tmp/sideload/package.zip [COLOR="Red"][B](in case I do it with stock recovery)[/B][/COLOR]
E: Error in /cache/24a9a760f32e.signed-yakju-JZO54K-from-JRO03C.24a9a760.zip [COLOR="red"][B](in case of OTA with CWM)[/B][/COLOR]
(Status 7)
Installation aborted.
Now as I gathered from the message, it seems that it cannot authenticate the Gmail app currently in my system. I'm using the 100% stock version, but I do recall that sometime back I used the "merge system apps updates into ROM" feature in Titanium Backup Pro. I believe it merged the updated Gmail, Maps and Play Store apps into the system.
Could someone help me figure out a way to make the system recognize the files as original? I've read at places that I can disable the assert on said files in the OTA file, but I don't want to do that. I want to fix this thing once and for all so that I can get future OTAs (4.2 JB) without any problem. Please help me out. Thanks!
A better way to load 4.1.2 is to download the stock ROM from Google's website and load it using fastboot. This way you can receive OTAs in the future since you be 100% stock.
Ieatnoobs said:
A better way to load 4.1.2 is to download the stock ROM from Google's website and load it using fastboot. This way you can receive OTAs in the future since you be 100% stock.
Click to expand...
Click to collapse
Thanks for replying. Could you please share what's the procedure for that? And by stock ROM, I assume you mean the 15MB update archive? Or should I be downloading the full ROM?
Also, I understand that I will lose root, which I can get again no problem. But will there be any other data loss? Please confirm. Thanks!
Evo911 said:
Thanks for replying. Could you please share what's the procedure for that? And by stock ROM, I assume you mean the 15MB update archive? Or should I be downloading the full ROM?
Also, I understand that I will lose root, which I can get again no problem. But will there be any other data loss? Please confirm. Thanks!
Click to expand...
Click to collapse
Hi Evo,
to go to 4.1.2 stock rom, you can download the factory image from Google for Galaxy Nexus GSM. This one is about 235 MB big. Unpack it and also check out this thread.
Just flashing should not delete your data, but unlocking your boot loader will and of course if you wipe and make a clean ROM flashing.
Ok we've got a problem.
I downloaded the factory image and flashed it. My bootloader was unlocked already, but it still wiped my device clean. No pictures, nothing on the internal memory, it wiped EVERYTHING. I used Galaxy Nexus Toolkit by Mark Skippen to flash the image.
Ben, you said just flashing should not wipe my data. Instead, it's wiped EVERYTHING.
I took a NANDROID backup just before the flash, and also took full Titanuim Backups today. Unfortunately I forgot to copy them off the device, so they are gone with it! And I'm left with a brand ****ing new GNex! :s
Is there any way to recover the data that was on there? I've read thread names that one can recover data off of microSD cards. Can the same work for the phone memory? I need a way out. There was some precious personal and work data in there that I cannot afford to lose. Someone please help me recover that? Thanks!
T989 without any SD card in it, the one I had died apparently new one on order. Went to flash the latest PA rom but kept getting error 7 using CWM. I updated my recovery to the latest TWRP and still will not flash. I tried updating to the newest radio UVMC6, but that wont flash. I am currently on CM10.1 nightly. My process for flashing is recovery, superwipe, flash, which is when the flash errors out and I re wipe and then I can flash my CM10 back on. So I can flash CM10 all day long but nothing else. I searched on here and found that the ATT version of this phone has this problem and you have to flash an AOKP and then flash whatever you want, other phones with similar problems say use ODIN and flash stock and then go from there. I am just looking for any advice on this situation. I could not find anything specific enough in my search to help me and I am hoping someone here can. Thanks in advance.
Note: I have also tried flashing CM10.1 RC5 and has the same problems.
moebawlz said:
T989 without any SD card in it, the one I had died apparently new one on order. Went to flash the latest PA rom but kept getting error 7 using CWM. I updated my recovery to the latest TWRP and still will not flash. I tried updating to the newest radio UVMC6, but that wont flash. I am currently on CM10.1 nightly. My process for flashing is recovery, superwipe, flash, which is when the flash errors out and I re wipe and then I can flash my CM10 back on. So I can flash CM10 all day long but nothing else. I searched on here and found that the ATT version of this phone has this problem and you have to flash an AOKP and then flash whatever you want, other phones with similar problems say use ODIN and flash stock and then go from there. I am just looking for any advice on this situation. I could not find anything specific enough in my search to help me and I am hoping someone here can. Thanks in advance.
Note: I have also tried flashing CM10.1 RC5 and has the same problems.
Click to expand...
Click to collapse
For onw those superwipe scripts are not needed with twrp, u might be getting the error from that, are u trying to flash from internal SD card since ur external died? That might cause it but I don't think so, I would suggest trying a manual wipe of all partitions, data, system, cache, dalvik, 2x , then flash, if that doesn't work try using Odin, go back to stock and start over, that should fix it definetly
Sent from my SGH-T989 using xda premium
soupysoup said:
For onw those superwipe scripts are not needed with twrp, u might be getting the error from that, are u trying to flash from internal SD card since ur external died? That might cause it but I don't think so, I would suggest trying a manual wipe of all partitions, data, system, cache, dalvik, 2x , then flash, if that doesn't work try using Odin, go back to stock and start over, that should fix it definetly
Sent from my SGH-T989 using xda premium
Click to expand...
Click to collapse
Thank you... I wasnt sure about superwipe on TWRP since I just put it on and came from CWM. I am trying to flash from the internal card and the new external card will be at my doorstep tomorrow so I will drop that in as well. I will drop back in once I get all this done and hopefully all goes well.
Again thanks.
moebawlz said:
Thank you... I wasnt sure about superwipe on TWRP since I just put it on and came from CWM. I am trying to flash from the internal card and the new external card will be at my doorstep tomorrow so I will drop that in as well. I will drop back in once I get all this done and hopefully all goes well.
Again thanks.
Click to expand...
Click to collapse
Good glad I can help, let me know how it all goes, now I'm interested lol
Sent from my SAMSUNG-SGH-T989 using xda premium
Ok so I got my new SD card. Tossed that in, just figured I would try flashing from the external, no luck there. Same issues.
Odin back to stock using this tutorial http://forum.xda-developers.com/showthread.php?t=1513359&page=3
Used http://forum.xda-developers.com/showthread.php?t=2195283 this to regain root.
Got CWM back on but now I cannot flash SuperUser
When I go to flash Superuser it says
Mounting System
Deleting System:bin/su...
Deleting System:xbin/su
Extracting files to SYSTEM
Setting SYSTEM:bin/su permissions to 06755...
Creating SYSTEM:xbin/su symbolic link...
E: Error in /emmc/Superuser-3.0.7-efghi-signed.zip
(Status 0)
Installation aborted
So on the plus side I didn't brick the phone... downside now I am back to Gingerbread and currently stuck here...
Possibly a bad zip file?
Any ideas on this?
Quick update... I am a moron... Did not realize that root is kept with this restore... Got Superuser from market and am good to go.
Installing TWRP now and will have an update on the flash soon.
OK... the fun seems to have just begun
I cannot install TWRP from GooManager. No clue why, looking on here and I found //techerrata.com/browse/twrp2/hercules (cant link too new of a member)
So as it seems I can download the .img and GooManager should see it and if that doesnt happen I can install it through the terminal with these commands
su
dd if=/sdcard/recovery.img of=/dev/block/mmcblk0p22
OR flash it with ODIN... Which I would assume I get the .tar file and follow the same process as putting the recovery files in?
Aside from TWRP being an issue, I tried installing the PA rom with CWM and I got this:
Installing update
set_perm:some changes failed
E:Error in /sdcard/pa_hercule...zip
(Status 7)
Installation aborted
The same error I had in the first place
moebawlz said:
OK... the fun seems to have just begun
I cannot install TWRP from GooManager. No clue why, looking on here and I found //techerrata.com/browse/twrp2/hercules (cant link too new of a member)
So as it seems I can download the .img and GooManager should see it and if that doesnt happen I can install it through the terminal with these commands
su
dd if=/sdcard/recovery.img of=/dev/block/mmcblk0p22
OR flash it with ODIN... Which I would assume I get the .tar file and follow the same process as putting the recovery files in?
Aside from TWRP being an issue, I tried installing the PA rom with CWM and I got this:
Installing update
set_perm:some changes failed
E:Error in /sdcard/pa_hercule...zip
(Status 7)
Installation aborted
The same error I had in the first place
Click to expand...
Click to collapse
I'm not sure what your overall problem is, but if you are going to install TWRP do not use Goo Manager or the img file. They have been messing up peoples phones. Odin the tar or try the zip from the TWRP thread.
meekrawb said:
I'm not sure what your overall problem is, but if you are going to install TWRP do not use Goo Manager or the img file. They have been messing up peoples phones. Odin the tar or try the zip from the TWRP thread.
Click to expand...
Click to collapse
Well that could be a problem... I just got GooManager to do what I wanted it to do before I saw this message. If I overwrite it with the tar will that be ok or am I better off starting this process over and Odin back to factory stock again?
Along with that after I got TWRP working through Goo Manager again I tried flashing PA again and I had the same error as I did in the first place.
Maybe my phone just hates anything but the nightly I had before...
moebawlz said:
Well that could be a problem... I just got GooManager to do what I wanted it to do before I saw this message. If I overwrite it with the tar will that be ok or am I better off starting this process over and Odin back to factory stock again?
Click to expand...
Click to collapse
If you can boot into TWRP, then they must have fixed the Goo problem.
It seems like you have tried most everything. Maybe you should Odin back to stock. If you are comfortable doing it, that is.
i went to flash with goo last night and it bricked the phone kind of, i had to ODIN and reflash the CWM again and bam the phone rebooted no problem
meekrawb said:
If you can boot into TWRP, then they must have fixed the Goo problem.
It seems like you have tried most everything. Maybe you should Odin back to stock. If you are comfortable doing it, that is.
Click to expand...
Click to collapse
I did Odin back to stock before. I am still on stock gingerbread right now with root access and am getting the errors I have been. I followed the tutorials in the sticky thread that I posted before that got me back to stock.
Within TWRP I tried installing the newest Cyanogen Mod and got
E:Error executing updater binary in zip
Error flashing zip
When I try installing the PA rom I get the same error
Any thoughts? Would going back to stock through Odin and doing this again potentially fix it? or is that a shot in the dark?
Lucky for me I kept a backup saved on my PC from before I did anything here. So I am back to the CM 10.1 Nightly I started on for the time being.
Is there any other method of flashing a rom that I might be able to try?
moebawlz said:
I did Odin back to stock before. I am still on stock gingerbread right now with root access and am getting the errors I have been. I followed the tutorials in the sticky thread that I posted before that got me back to stock.
Within TWRP I tried installing the newest Cyanogen Mod and got
E:Error executing updater binary in zip
Error flashing zip
When I try installing the PA rom I get the same error
Any thoughts? Would going back to stock through Odin and doing this again potentially fix it? or is that a shot in the dark?
Click to expand...
Click to collapse
It would be a shot in the dark. I did a Google search for your error and a couple of people said they were able to fix it by using TWRP 2.3. That was for different phones though. Maybe try that before going stock.
I am by no means a pro at this and am still learning as I go. Just to make sure of what I am doing, can I Odin TWRP 2.3? I also found this
http://forum.xda-developers.com/showthread.php?t=1639673
or
http://forum.xda-developers.com/showthread.php?t=1658418
Just a thought here... I keep gettin emmc errors... I was reading about upgrading and downgrading TWRP through the Terminal Emulator and it said use emmc or sdcard depending on what the phone reads it as.
When I first got the phone i recall seeing emmc when i would go into any file browser. Now it just says sdcard0 (internal) & sdcard1 (external)
So how can I get recovery to stop looking for emmc and start looking for sdcard0?
Unless I am way off in left field here with this.
moebawlz said:
I am by no means a pro at this and am still learning as I go. Just to make sure of what I am doing, can I Odin TWRP 2.3?
Click to expand...
Click to collapse
Yes, use Odin and the 2.3.3.0 tar from the techerrata website. I like using the Odin method because I have never had a problem upgrading recovery that way. I don't know about the emmc errors because I have only used the dd method like twice.
Edit: Maybe your internal memory is corrupted? I'm not sure how to test for that though.
moebawlz said:
Well that could be a problem... I just got GooManager to do what I wanted it to do before I saw this message. If I overwrite it with the tar will that be ok or am I better off starting this process over and Odin back to factory stock again?
Along with that after I got TWRP working through Goo Manager again I tried flashing PA again and I had the same error as I did in the first place.
Maybe my phone just hates anything but the nightly I had before...
Click to expand...
Click to collapse
I think u must be getting bad DL then because none of that sounds right lol, if u got twrp to load into your device and all is working fine then the only other option is a bad DL, try checking the DL with a root browser or something to see the size of the file, status 7 errors are from the zip, usually bad install script in the ROM, which could be caused by a bad DL, check the DL size and let me know
Sent from my SGH-T989 using xda premium
went back to 2.3.3 and still having the same error.
Is there a way to correct any possible errors in my internal memory?
moebawlz said:
went back to 2.3.3 and still having the same error.
Is there a way to correct any possible errors in my internal memory?
Click to expand...
Click to collapse
If the DL is good, I don't know what else to tell u that is very strange indeed, but interesting too, I've never not been able to install at all, I'm curious..
Sent from my SGH-T989 using xda premium