Hey,
having a problem with installing zips
phone doesn't seem to be able to install any ROM or superuser but can install gapps, google now, recoveries, etc.
the error looks like this
E: error in sdcard/roms/path
(Status 0)
Aborted
Been looking around and people with status 0 problems normally get them by doing something wrong with the update binary when developing their own roms. I recently messed up my phone a little and although I got it working again I think the update binary might still be changed.
Since I know nothing about any of this kind of thing,
Does anyone have access to a stock or tested and working update-binary file that I can replace mine with,
or at least check to see if there's any differences, to see if that's the problem?
If anyone has any ideas about what might be causing the problem i'd appreciate help
Thanks
i would start be reflashing the recovery becasue i highly doubt that the roms that all these DEV have built is the issue with binary script if you want to pull one from a stock rom. you can grab one from Vincoms thread. and not to mention make sure you have atleast attempted to download the rom twice incase you have a bad zip folder. another thing you cant would be to flash from the internal
crashpsycho said:
i would start be reflashing the recovery becasue i highly doubt that the roms that all these DEV have built is the issue with binary script if you want to pull one from a stock rom. you can grab one from Vincoms thread. and not to mention make sure you have atleast attempted to download the rom twice incase you have a bad zip folder. another thing you cant would be to flash from the internal
Click to expand...
Click to collapse
No it's 100% a problem with the phone,
I've tried multiple recoveries, multiple roms, that were downloaded multiple times from multiple sources, and while running multiple roms (from recoveries) and all give the exact same error. TWRP's error looks a little different but I'm pretty sure its the same thing.
I thought there was just a .tar file on vincom's thread for the stock firmware
i'll check again to see if I can find what I need from there though,
thanks.
there is a zip stock recovery fashable file, but not a tar one, either revert to full stock via odin then reinstall a custom recovery, or backup your sdcards and reformat them to see if that corrrects your problem
Related
Hey guys, I am trying to flash Cognition 2.3b3 from Cognition 2.3b2, and the flash keeps failing in clockwork recovery. I have voodoo lag fix disabled, I flash clockwork recovery, and I have even tried installing the update with the wipe option checked. I keep getting an error during the installation saying "installation aborted. Cannot open /sdcard/Cognition2.3b3.zip.
Does anyone have any ideas?
Did you try redownloading the zip file? It may be a corrupt download?
If not, I wouldn't know since I haven't upgraded to b3 yet
I did try redownloading the zip. I can't figure what the problem is. The file came straight from designgears sight. I do not have winzip installed on my laptop. Could that make a difference?
Just sharing my experiance.
I had stockish eclair with voodoo (deleted one system file by mistake and it wouldn't boot) so i flashed Cognition 2.3b3 thro odin , it went thro without problems kernel detected ext4 present (from previous voodoo) and everything works fine
So you don't need to disable voodoo lag fix if your next rom supports it. And you could also try flashing with odin if clockwork fails.
bparkerson04 said:
I did try redownloading the zip. I can't figure what the problem is. The file came straight from designgears sight. I do not have winzip installed on my laptop. Could that make a difference?
Click to expand...
Click to collapse
Give us a Step by step of what you did so we can help further. When asking for help it helps us alot to give as much information as possable
I think I figured out what the problem was. I was deleting some stuff from my internal sd card, and I deleted the update.zip I used to root my phone when it was stock. I didn't think I needed it anymore. The thought occurred to me just now to put that file back, and I was just able to flash the rom. Go figure. Thanks for all of the input guys. I guess I will always need to keep that update.zip on my root sd.
I can flash clockworks recovery through adb and can get in but I'm getting some errors:
E: Can't find misc
E: failed to find "cache" partition to mount at "/cache"
E: Can't mount /cache/recovery/command
E: Can't mount /cache/recovery/log
E: Can't open /cache/recovery/log
And a bunch few more which seem to repeat
I also tried to run the restore to stock from here but get an error right when I have to click to write the image.
When I just boot all I see is the unlocked lock and google. It used to boot into storage so I can mount it but not anymore. The only thing I have on the SD is the super user app, Netarchy kernel for 4G, CM7 latest stable for NS and thats it.
Need help
I can push something to the phone through the sdk but I don't know how to mount the sd card to do it.
ufff.... nevermind. I tried the factory restore one more time on another machine 32 bit and it works. It's restoring the image again. Will be locked again so I'll have to try again tomorrow. But the steps on rooting the NS4G don't really work well.
There is a bunch of stuff missing. Like the recovery gets overwritten each time. There are some links missing and dead.
Someone should fix that before we brick some phones.
OK, it restored but only gave me the sd card mount thing. I tried going back to fastboot and unlocked was still there. So I flashed recovery again and wanted to see if I can put the stock rom for 4G from here on it.
No go. I get:
assert failed: write_raw_image("/tmp/netharchy.img", "boot")
Installation aborted.
Help
ok, I'm not sure what ROM I have but I unplugged the cable and bam... sign in screen came in so I'm sighing in. Once I can get to the main menu I'll check versions and kernel but it looks like I have root. It's just that recover is not working well. I have 3.0.0.5. should I get a different one?
OK, I restored again because wifi didn't work. I think it was because I was trying to flash after the first restore and it wouldn't take. So now I checked and the lock when I boot showes up as unlocked but none of the root apps work so I don't think I have root. Not sure.
I also have to figure out what's up with that recovery. I know I need to rename the original so it doesn't flash it every time on boot but I think I need a new version. Anyone know which one is the latest and which one works on NS4G?
3005 is the problem. Use 3024. I don't know for sure but are you absolutely sure cm7 is compatible with the ns4g? Isn't a lot of stuff still not working? Isn't 4g still not working? If flashing the wrong rom is what happened here then this problem isn't going away. Many people are doing this and almost bricking their phones. I read one post recently that pointed to a doc that said the gsm and cdma are two separate versions of the same os. I thought I read something that said kernels might be cross compatible but roms aren't yet.
Here are the correct recovery files for the ns4g
I think I remember seeing recovery ***** about cache when I was nandroid for the first time. I think after that I chose factory reset and clear dalvik and some other cache and might have rebooted then came back and flashed cwm again and tried nandroid and it worked that time. This was the very last step for me after I had managed to get the su file to the root of the card, flashed it in cwm, rebooted and changed the filename of the script to check and reinstall stock recovery in system/etc. I forget the name but it was a .sh file. It's name was in the guides somewhere...
I think that's backwards. Roms might be compatible but kernels which these roms come with are not. So I believe that it I just flash netarchys kernel which now supports NS4G all should work ok.
Like I said, I'm back to stock and all looks like exactly like it was before ie. no root but the weird part is that fast boot menu says "unlocked". And I also get the lock which looks unlocked with the google sign during boot.
So how is that possible? Anyone?
When trying any app with root it tels me it has no access or it failed. Ie, su cmd says access denied.
BTW, why you attached two files? What is the difference between the two?
herbthehammer said:
3005 is the problem. Use 3024. I don't know for sure but are you absolutely sure cm7 is compatible with the ns4g? Isn't a lot of stuff still not working? Isn't 4g still not working? If flashing the wrong rom is what happened here then this problem isn't going away. Many people are doing this and almost bricking their phones. I read one post recently that pointed to a doc that said the gsm and cdma are two separate versions of the same os. I thought I read something that said kernels might be cross compatible but roms aren't yet.
Here are the correct recovery files for the ns4g
I think I remember seeing recovery ***** about cache when I was nandroid for the first time. I think after that I chose factory reset and clear dalvik and some other cache and might have rebooted then came back and flashed cwm again and tried nandroid and it worked that time. This was the very last step for me after I had managed to get the su file to the root of the card, flashed it in cwm, rebooted and changed the filename of the script to check and reinstall stock recovery in system/etc. I forget the name but it was a .sh file. It's name was in the guides somewhere...
Click to expand...
Click to collapse
Thanks for your help. I'm rooted and recovery is sticking ok. It was the old recovery. As soon as I flashed it all was good.
One is stock and the other is cwm that works with the ns4g. It wouldn't hurt to have the stock laying around. There might be a time when you need it.
Thanks for the stock recovery.
Sent from my Nexus S 4G using XDA App
I have been able to get into CWM Recovery v5.8.0.2 but there are no system files or any files on the phone, i can load new ROM's on the SD Card but every time i install it, it comes back with installation aborted, i have tried multiple different ROM's, any suggestion will be greatly appreciated. The phone does not boot any further
Are you sure youre not flashing a Nexus S 4G rom on a Nexus S. Or the opposite?
I am sure, i downloaded all the correct ROM's from CWM and am sure i have a Nexus S not 4G, it was rooted before and worked fine, i tried getting it back to stock and when it booted, it stopped on the boot ROM, from there i went through the procedure on loading CWM recovery and finally got back into recovery mode but from there i cannot flash anything and as mentioned, there are no file whatsoever on the phone, it is as if it was wiped clean.
Have you accidentally flashed a NS4G recovery by any chance? Try reflashing your recovery.
Also, any other errors listed?
I flashed using the CWM v5.8.0.2-touch on the Nexus S category, so am sure and triple checked and redid the flash a couple of times, its as if the new flash does not find any files to flash and i cannot see any files on the phone, there is only the update.zip file on there
Jpienaar2012 said:
I flashed using the CWM v5.8.0.2-touch on the Nexus S category, so am sure and triple checked and redid the flash a couple of times, its as if the new flash does not find any files to flash and i cannot see any files on the phone, there is only the update.zip file on there
Click to expand...
Click to collapse
try a different recovery, or the non touch cwm recovery.
I loaded v5.0.2.0 from CWM and still the same, it changes CWM but cannot load any new ROM's
Jpienaar2012 said:
I loaded v5.0.2.0 from CWM and still the same, it changes CWM but cannot load any new ROM's
Click to expand...
Click to collapse
dont load from there, flash a new recovery via fastboot.
I only downloaded the recovery file from CWM but loaded it through fastboot, but still the same result
Jpienaar2012 said:
I only downloaded the recovery file from CWM but loaded it through fastboot, but still the same result
Click to expand...
Click to collapse
download from somewhere else and try.
any suggestions on where else i could get it from?
Download stock fastboot.imgs for your specific device. Flash them all = stock and start over
i have also downloaded from nexushacks.com and same result
Sorry, but where can i get the stock files from?
Search Google. Go to official Google site with them. Can't recall the exact URL but it will come up. There is a thread on these forums as well with the links to factory images and instructions if you need them.
PSA. Stay away from nexusshacks. That guy is a tool.
Thanks, will have a look on what i can find
Ihave tried stock and various developers and still no luck, i tried fast boot update from terminal and get
archive does not contain 'android-info.txt'
archive does not contain 'android-product.txt'
error: update package has no android-info.txt or android-product.txt
Any suggestions
Jpienaar2012 said:
Ihave tried stock and various developers and still no luck, i tried fast boot update from terminal and get
archive does not contain 'android-info.txt'
archive does not contain 'android-product.txt'
error: update package has no android-info.txt or android-product.txt
Any suggestions
Click to expand...
Click to collapse
Did you grab your image from here and follow the instructions to start the script?
https://developers.google.com/android/nexus/images
Thanks, this worked and my phone is back to normal again. Don't trust what other people say on the web cause most of the time they give you crap.
I need to move back to GB for wi-fi calling purposes (I live in a hovel) and so I followed the One-Click directions but DID NOT load bootloaders as it seemed like there may be some issues in doing so.
Now I'm interested in installing Vahalla Black but when I try to install the zip file for it, it says something to the effect of "install /sdcard", opens it and tries to verify the update package and then says the e-signature verification failed.
Do I need to load bootloaders? I don't have CWM, only Android System Recovery (it's stock). I've also re-downloaded VB Final just in case there was a bad download of it but still got the error.
It sounds like you used the Heimdal One-Click that took you back to stock. If so, you need to flash a custom kernel to flash a custom ROM.
lumin30 said:
It sounds like you used the Heimdal One-Click that took you back to stock. If so, you need to flash a custom kernel to flash a custom ROM.
Click to expand...
Click to collapse
Yes, that's exactly what I did. Wasn't aware I need to flash a custom kernel and then a custom ROM. I'll do that and see if it fixes things. Thanks!
NVM, got the thing to work proper ly now. Love the long battery life and Wi-Fi calling! Forgotten how much I missed it here in the hollow
hi, i've got CyanogenMod 7.2 (Alpha9) on my galaxy 3, i initially used odin, then found i had the 0kb free space issue, but then used CWM to flash from a zip file and it's now working fine.
i'd like to put the MTD version on it, and i'm trying to follow the instructions here http://forum.xda-developers.com/showthread.php?t=2309390, but i can't get odin to flash the 1Ghz overclock mtd kernel.
the version of odin that i initially flashed the rom with has no problem establishing a connection with my phone, but says the .tar file is an invalid image when i try to load it in the PDA section.
i've tried a couple of other versions of odin, and they all accept it as a valid image, but none of them get past the point where it says setup connection.
alternatively, a link to a version of the same kernel that i can use CWM recovery to flash would be ideal, i've got to grips with CWM and find it easy to work with, but i'm struggling somewhat with odin.
i've realised my problem all along was that my copy of the mtd update was corrupt. i have re-downloaded it and all is going smoothly so far.
Mr Creosote said:
i've realised my problem all along was that my copy of the mtd update was corrupt. i have re-downloaded it and all is going smoothly so far.
Click to expand...
Click to collapse
Finally ! Have fun with the ROM.
marcellusbe said:
Finally ! Have fun with the ROM.
Click to expand...
Click to collapse
thanks, i'm very happy with it now that the battery isn't draining really quickly like it was with the non-mtd version. i'd been going about it the right way all along, lol, it just never occurred to me that i had a corrupt file. was only when i double clicked on it to look at the contents of the zip that i realised it was corrupt. i was beginning to worry that the world of android modding was hopelessly impenetrable.