Decided to flash back to stock(was using lag fix ext 2 + root/busybox, etc) and used the odin one-click method. flashed back to stock fine. Decided to flash the SRE v1.2.1a
Downloaded the zip, changed to 'update.zip' and rebooted into the recovery(stock) and selected reinstall packages.
It gives me the error:
E:Can't open /sdcard/update.zi[
(No such file or directory)
Installation aborted.
I've put the sre file on my internal SD card about 5 times now and know it's on there.
What gives?
Did you rename the file update or update.zip, if you included.zip then the file in on your sd would read update.zip.zip and I have seen this happen. Coonect your phone to your pc and mount it then look in the sd and be sure you named it correctly. Thats' where I would start and post this question in the thread so the developer that made this or someone there could help you.
http://forum.xda-developers.com/showthread.php?t=751934
Rhiannon224 said:
Did you rename the file update or update.zip, if you included.zip then the file in on your sd would read update.zip.zip and I have seen this happen. Coonect your phone to your pc and mount it then look in the sd and be sure you named it correctly. Thats' where I would start and post this question in the thread so the developer that made this or someone there could help you.
http://forum.xda-developers.com/showthread.php?t=751934
Click to expand...
Click to collapse
Ditto, I've actually done this myself once so just make sure to rename it to just Update and save it and it still should be a zip file.
One thing that any of the instructions I have read neglect to tell you is that /sdcard is actually the root of the mounted sdcard on your computer so you don't put update.zip in the directory sdcard you put it right in the root.
jaseone said:
One thing that any of the instructions I have read neglect to tell you is that /sdcard is actually the root of the mounted sdcard on your computer so you don't put update.zip in the directory sdcard you put it right in the root.
Click to expand...
Click to collapse
This is incorrect.
Update.zip does indeed go on the root of the internal SD card.
/SDcard/update.zip - this is the proper path
http://forum.xda-developers.com/showthread.php?t=725555 (step 2)
OP - i expect your problem is the file name as mentioned above.
It goes in the root.... Thats how i do it!
Sent from my SAMSUNG-SGH-I897 using XDA App
I get the same message. I looked in the "Files" app and see that the card is named /sd and not /SDcard. Renaming it is disallowed. Could this be the problem?
If so, what next?
[Never mind; that directory is in the root of the internal storage and is not the same as the SD card.]
Thanks
Got it to work. On my windows system when I plug in to USB and mount the device I have two separate devices in "My Computer" for it. One is the internal storage and the other is the external SD card.
For my Galaxy S Vibrant update.zip must be at the root of the internal, not the external SD card. It won't find it if in the latter and it updates fine using the "Reinstall Packages" function when update.zip is placed in the internal root.
On a Captivate when we refer to the sd it is the root or we'll just say external sd when refering to the one you install in the slot inside the battery cover. This was a bit confusing for me in the beginning but sd is the root. I have been doing it this way since day one.
We have about 2 gig internal and 13 gig that the phone sees as sd or sdcard. Now that is confused when you add an actual external sd card. Mine came from my aria and and on my captivate it shows as "/sdcard/sd" I'm not even sure how my pc sees this.
The update should be on root of the internal 13 sd storage. On the phone it is /sdcard but on a pc copying to /sdcard/update.zip may create /sdcard/sdcard/update.zip but I haven't tried.
I use opera browser to download directly to /sdcard. So I'm not sure but I'm guessing what we see on the phone as /sdcard we see on the pc as root of a 13 gig external drive
Sent from my SAMSUNG-SGH-I897 using Tapatalk
ArcaneMethods said:
Got it to work. On my windows system when I plug in to USB and mount the device I have two separate devices in "My Computer" for it. One is the internal storage and the other is the external SD card.
For my Galaxy S Vibrant update.zip must be at the root of the internal, not the external SD card. It won't find it if in the latter and it updates fine using the "Reinstall Packages" function when update.zip is placed in the internal root.
Click to expand...
Click to collapse
thanks for the tip i just updated the zip
I had this as well, (Samsung Galaxy S) and took a few tries of copying the file between my E: and F: drive - I have a Windows PC and both drives letter showed up E: ended up being the external SD and F: the internal sd card.
Also, my folder was labelled /sd and not /sdcard.
I tried a few iterations of copying and renaming the file to both E: and F: in /sd and the root folder "/" and nothing worked.
Finally, I took out the microSD, and then copied "Update.zip" to /sd and also the root folder (so both had a copy), and renamed it to "update.zip" (case-sensitive).
Then ran "adb reboot recovery" and was able to choose "update" and it worked.
Hope this helps someone
blackinches said:
Decided to flash back to stock(was using lag fix ext 2 + root/busybox, etc) and used the odin one-click method. flashed back to stock fine. Decided to flash the SRE v1.2.1a
Downloaded the zip, changed to 'update.zip' and rebooted into the recovery(stock) and selected reinstall packages.
It gives me the error:
E:Can't open /sdcard/update.zi[
(No such file or directory)
Installation aborted.
I've put the sre file on my internal SD card about 5 times now and know it's on there.
What gives?
Click to expand...
Click to collapse
I had this as well, (Samsung Galaxy S) and took a few tries of copying the file between my E: and F: drive - I have a Windows PC and both drives letter showed up E: ended up being the external SD and F: the internal sd card.
Also, my folder was labelled /sd and not /sdcard.
I tried a few iterations of copying and renaming the file to both E: and F: in /sd and the root folder "/" and nothing worked.
Finally, I took out the microSD, and then copied "Update.zip" to /sd and also the root folder (so both had a copy), and renamed it to "update.zip" (case-sensitive).
Then ran "adb reboot recovery" and was able to choose "update" and it worked.
Hate to bring this back up but ....worked for me ! aha i added another .zip to it ...makes me feel dumb
Hi,
I have a Samsung Vibrant and I've tried all options suggested here and everytime I start to phone in recovery mode and select "reinstall packages" it tells me "Can't open sd/update.zip (such file doesn't exist)". Here is what I've tried so far:
- Plug the phone on the pc via usb. I then see the phone as a hard drive and when I open it it displays 2 drives, one is the phone and the other is the SD card (called simply SD). I copied the update.zip file and placed it directly into the SD drive.
- With a micro usb to usb adapter card I copied the update.zip file to the sd card.
- I removed the zip extension from the update.zip file (I tried doing this on the pc and directly on the phone via astro file manager).
- I´ve created an SD folder on the SD drive and placed the update.zip file there.
- I´ve created an SDCARD folder on the SD drive and placed the update.zip file there.
- I´ve tried renaming the SD drive to SDcard (the system wouldn't let me).
This issue cannot be this difficult to resolved. I really want to install I new rom on my phone and it's very frustrating not being able to resolve such a silly thing. Can anyone help?
cheers
Rafa
rawfa said:
This issue cannot be this difficult to resolved. I really want to install I new rom on my phone and it's very frustrating not being able to resolve such a silly thing. Can anyone help?
Click to expand...
Click to collapse
It sounds like your are putting update.zip on an external sdcard. Put it in the root directory of the internal sdcard.
opcow said:
It sounds like your are putting update.zip on an external sdcard. Put it in the root directory of the internal sdcard.
Click to expand...
Click to collapse
How do I do that? I thought I was putting in the root...
Ok. I had this problem the first time too. Plug your phone into your computer(make sure you're in mass storage mode and usb debugging is turned on). A pop up should come up, click on view files. Paste it right there. Then try it again.
Sent from my SGH-I897 using XDA App
rawfa said:
How do I do that? I thought I was putting in the root...
Click to expand...
Click to collapse
Maybe you were. Read what I wrote. If you are putting it in the root directory of the internal sdcard, then I don't know what the problem is.
When I connect using usb debugging mode the drivers do not show up on windoes explorer, although I can see them on the device manager console.
This is insane...I´ve tried everything and it still doesn´t work...and I bet it´s something really silly.
I am rooting my Sprint CDMA Hero and I'm stuck on this step.
Sorry if this is ridiculously basic, but every guide I have tried only says "put it on the root of your sdcard." While I now understand that this means something about no folders, I'm still having trouble finding "the root of my sdcard."
Can someone please give me the most simplistic, dumbed-down walkthrough directions or location of this alleged "root of your sdcard"?
I'm talking like "Go to My Computer, C:, wherever, wherever, wherever, "Hooray! This is the mythical root of your sdcard you've heard so much about!"
The ultimate goal is to put the latest Froyo 2.2 available on my Sprint CDMA Hero.
Thanks for any help!
1. Go to My computer
2. Click on the drive that is mapped to your Phone's storage (SD card)
3. The explorer window should display you the contents of the SD card - folders, files... whatever applicable
4. Copy the zip file to the SD card such that it does not end up in any of the existing folders or any new folder that you might create
5. When you browse the content of the SD card, if the file is directly visible without going into any folder - you have accomplished "Put file on root of your sdcard"
Hope this helps.
It's just a matter of learning the term, "root directory". The sd card top directory is the root. For example, C:\ which has your Program Files, Windows folders, etc, is the "root of your C: drive".
Similarly, the sd card directory X:\ (where X is obviously the drive letter of your sd card) is the root of your sd card.
So like andythegreenguy said, open my computer, open sd card, don't go into any aditional folders, copy files into there.
Thanks andy and C00ller, this worked!
I don't feel like such an idiot anymore.
Thanks
I was curious about this as well. So thank you very much.
for anyone interested of doing what the title says just download the file attached and adb push it to syste/etc and reboot or copy into sd and the copy it using root explorer (or any root explorer app) into system/etc and reboot
now your microsd will be /sdcard and your internal storage sd will be sdcard2
Hi there,
Anyone got the overwriting issue when you are moving the file with same name from SD folder to another SD folder?
You will get unknown issue if you click "Move to" when you get the pop up window.
The file in the target folder will be deleted, but the moving operation stopped.
Thanks
There is no issue if you overwrite the file with same name from internal memory to SD or from SD to internal memory.
here is my log...
i keep failed with unlock my bootloader on my x8,w8(root and checked unknown sources&usb debugging)
i edi do..some 1 know what problem with my step
bootTools\adb.exe' is not recognized as an internal or external command,
operable program or batch file.
'bootTools\adb.exe' is not recognized as an internal or external command,
operable program or batch file.
'bootTools\adb.exe' is not recognized as an internal or external command,
operable program or batch file.
'bootTools\adb' is not recognized as an internal or external command,
operable program or batch file.
Waiting ...
'bootTools\adb.exe' is not recognized as an internal or external command,
operable program or batch file.
Removing NAND MPU restrictions via SEMC backdoor. Permanent. Require ROOT rights.
'bootTools\adb.exe' is not recognized as an internal or external command,
operable program or batch file.
'bootTools\adb.exe' is not recognized as an internal or external command,
operable program or batch file.
'bootTools\adb' is not recognized as an internal or external command,
operable program or batch file.
'bootTools\adb' is not recognized as an internal or external command,
operable program or batch file.
Waiting ...
'bootTools\adb.exe' is not recognized as an internal or external command,
operable program or batch file.
Getting ROOT rights.
'bootTools\adb' is not recognized as an internal or external command,
operable program or batch file.
Waiting ...
'bootTools\adb.exe' is not recognized as an internal or external command,
operable program or batch file.
Writing patched semcboot. Two step process
First, we need get access to semcboot area
'bootTools\adb.exe' is not recognized as an internal or external command,
operable program or batch file.
'bootTools\adb.exe' is not recognized as an internal or external command,
operable program or batch file.
'bootTools\adb' is not recognized as an internal or external command,
operable program or batch file.
Second, we need to write semcboot
'bootTools\adb.exe' is not recognized as an internal or external command,
operable program or batch file.
'bootTools\adb.exe' is not recognized as an internal or external command,
operable program or batch file.
'bootTools\adb' is not recognized as an internal or external command,
operable program or batch file.
Press any key to continue . .
AND
he system cannot execute the specified program.
The system cannot execute the specified program.
The system cannot execute the specified program.
The system cannot execute the specified program.
Waiting ...
The system cannot execute the specified program.
Removing NAND MPU restrictions via SEMC backdoor. Permanent. Require ROOT rights.
The system cannot execute the specified program.
The system cannot execute the specified program.
The system cannot execute the specified program.
The system cannot execute the specified program.
Waiting ...
The system cannot execute the specified program.
Getting ROOT rights.
The system cannot execute the specified program.
Waiting ...
The system cannot execute the specified program.
Writing patched semcboot. Two step process
First, we need get access to semcboot area
The system cannot execute the specified program.
The system cannot execute the specified program.
The system cannot execute the specified program.
Second, we need to write semcboot
The system cannot execute the specified program.
The system cannot execute the specified program.
The system cannot execute the specified program.
Press any key to continue . . .
please help me