Related
Hey everybody,
I apologize in advance if this post is a duplicate but I have tried searching for a solution and still lost. Here is what I did: I used the Odin to restore stock rom, then re-rooted using the one click method, then downloaded a rom from theunlockr.com, then used rommanger to install it. My rom has gave me no problems but now when I try to reboot into recovery to install something else(Like the 2.3 keyboard or a lagfix) i get this error:
E:Can't open /sdcard/update.zip
(No such file or directory)
Installation aborted
Can someone please help me? Thank you, BTW I have a Samsung Vibrant running axura-froyo-rom
I had the same problem too.
When I put update.zip at the root directory of internal memory... once I restart the phone (not get into the recovery mode), this file is missing / dissapear. So... I always got this message too :
E:Can't open /sdcard/update.zip
(No such file or directory)
Installation aborted
anybody can help us pleaseeeeee
I got my phone to factory settings using odin then i rerooted my phone and flashed the same custom rom back on and it worked. Try reflashing your phone, backup first, might work.
CarlosCruz15 said:
I got my phone to factory settings using odin then i rerooted my phone and flashed the same custom rom back on and it worked. Try reflashing your phone, backup first, might work.
Click to expand...
Click to collapse
thanks for reply.
how to use factory setting using odin ? tick the "re-partition" box ?
can you explain to us step by step please ?
I'm so frustated
Did you guys delete the update.zip after rooting?
If you do not see
sdcard/update.zip using a file manager, download the update.zip from my noob guide, move it to internal memory and then try to flash CWR.
Also, look in the bottom of the noob guide (last few posts) for a solution to a RECENT issue with CWR... I assume whatever Koush did in the last update is causing this problem? BUT, there is a fix posted by another XDA user... just a matte of downloading the file and putting it in the right place.
mikomikos said:
thanks for reply.
how to use factory setting using odin ? tick the "re-partition" box ?
can you explain to us step by step please ?
I'm so frustated
Click to expand...
Click to collapse
check out this link...its what i used
http://forum.xda-developers.com/showthread.php?t=734475
listen to s15's post....he knows what he is talking about. i followed his noob guide in his sticky and everythign worked perfectly! his vids are also very helpful. one thing i have found that works a lot as well is if you download ROM Manager from the market and then click on "fix permissions"... don't know if this would help in this situation but i have had that fix weird stuff.
s15274n said:
Did you guys delete the update.zip after rooting?
If you do not see
sdcard/update.zip using a file manager, download the update.zip from my noob guide, move it to internal memory and then try to flash CWR.
Also, look in the bottom of the noob guide (last few posts) for a solution to a RECENT issue with CWR... I assume whatever Koush did in the last update is causing this problem? BUT, there is a fix posted by another XDA user... just a matte of downloading the file and putting it in the right place.
Click to expand...
Click to collapse
yeah this, the update.zip is ESSENTIAL for your phone to run the clockwork recovery, it stores all the things needed, and when you click "reinstall packages" your system goes in update.zip and looks for what to boot up and finds CWR and boots that so you see that screen.
Don't delete it if you did.
i have tried numerous times to root,but cant seem to get update.zip file in right place,can anyone help? thanks. challenged noob!!
Rayn1328 said:
i have tried numerous times to root,but cant seem to get update.zip file in right place,can anyone help? thanks. challenged noob!!
Click to expand...
Click to collapse
When you usb into your phone it needs to be in the initial area of your sdcard.
You might have a bad update.zip file. Two things, verify the md5(if possible) from where you got it and check the properties and make sure it's not names update.zip.zip. The later is very common.
Try this method too btw, when I Odin back to stock I always use this one to root again. Follow the 'Automated Method' area.
http://forum.xda-developers.com/showthread.php?t=786877
you will need these drivers AND set your phone to debugging mode (settings/applications/development check USB debugging).
http://forum.xda-developers.com/showthread.php?t=728929
hey all,
Newbie here trying to flash a ROM, i am running into this same error, i have tried everything here and i have one question (might be a stupid question) but my root sd folder is called SD/, not SDCard/ ...is this a path error?
Please note it file must be in the internal card, not the SD card.
This step drove me nuts.
"2. Copy the update.zip (and the ROM) to the INTERNAL SD (not the external SD Card). sdcard/ " (http://forum.xda-developers.com/showthread.php?t=732458)
i ran into the same problem...how do i get from 3e to CWR?
here's what's shown in my vibrant directory: Android, DCIM, external_sd, LOST.DIR
i dont have an internal sd (the card) so it's not shown?
the path i got error on: /mnt/internal_sd/update.zip
1. when i tried to "reinstall packages" i keep getting the error that the update.zip file cant be found. should i create a folder for it or something? i think it's a matter of pathing but i cant find out the right place to put the file...(to get from 3e to CWR)
2. i see people suggesting boot with odin or sth like that...does that solve my problem and how do i do that?
janthe6th said:
i ran into the same problem...how do i get from 3e to CWR?
here's what's shown in my vibrant directory: Android, DCIM, external_sd, LOST.DIR
i dont have an internal sd (the card) so it's not shown?
the path i got error on: /mnt/internal_sd/update.zip
1. when i tried to "reinstall packages" i keep getting the error that the update.zip file cant be found. should i create a folder for it or something? i think it's a matter of pathing but i cant find out the right place to put the file...(to get from 3e to CWR)
2. i see people suggesting boot with odin or sth like that...does that solve my problem and how do i do that?
Click to expand...
Click to collapse
You definitely have an internal sd card. Use Astro file manager or something similar and put update.zip on the root of internal sd card, meaning not in a folder. It should look like sdcard/update.zip. If you are having the 3e mismatch recovery issue read this http://forum.xda-developers.com/showthread.php?t=833423
Sent from my SGH-T959 using Tapatalk 2
i go to the link that you linked and ran the script. then i download the update.zip file at the noob guide with a slimbean 4.2.2 rom and addons. this time i would just put it in the root folder (technically not in any folder). when i try to reinstall packages, the screen shows that it is "replacing stock recovery with clock work recovery"... but then it would go back to the 3e.
so...i guess putting the files in the root folder is correct. but someone it still wont let me get tot CWR...
janthe6th said:
i go to the link that you linked and ran the script. then i download the update.zip file at the noob guide with a slimbean 4.2.2 rom and addons. this time i would just put it in the root folder (technically not in any folder). when i try to reinstall packages, the screen shows that it is "replacing stock recovery with clock work recovery"... but then it would go back to the 3e.
so...i guess putting the files in the root folder is correct. but someone it still wont let me get tot CWR...
Click to expand...
Click to collapse
You have to reinstall packages twice for it to work properly. It is normal to not work the first time, just reinstall packages again and you should be good to go. If you keep having issues you should just flash back to stock 2.1 with Odin and go from there.
Sent from my SGH-T959 using Tapatalk 2
So I flashed this ROM a bit earlier, and now, like a few other users in that thread, I cannot seem to be able to write anything to /sdcard. Installing and updating apps still works ok, but downloading anything with the browser, deleting any files in /sdcard, copying anything with wifi file explorer to /sdcard, or any I/O related thing to /sdcard fails.
Now here's the crazy thing. I've factory reset + wiped system and installed another ROM, as well as factory reset + wiped system and restored a backup, and still no go. Seems like something got borked pretty good...
Please advise.
Update...
Have tried a few more things, here's what works:
I can write to SDcard when connected to the computer via USB using the computer to send the files.
I can write to the SDcard when using TWRP's file manager.
I have tried fixing permissions, but that did not solve the problem.
TweakerL said:
Have tried a few more things, here's what works:
I can write to SDcard when connected to the computer via USB using the computer to send the files.
I can write to the SDcard when using TWRP's file manager.
I have tried fixing permissions, but that did not solve the problem.
Click to expand...
Click to collapse
have you tried this?
http://forum.xda-developers.com/showthread.php?t=1670824
then use ADB to push the ROM you want.. hope you know about pushing ADB... i just did it last night...
Hi folks
I hope I am not breaking any rules. I tried my best to read up on the problem and see if it's already been fixed. So far I haven't encountered anything which is specific to my needs, but I learned enough to pose a well-formed question.
Phone: Samsung Galaxy SIII International (GT-I9300)
ROM: Stock Samsung, version 4.1.2, the update with Multi-window. Do not have the exact build number unfortunately.
Root status: Rooted
Recovery: Stock recovery. (I JUST rooted the phone, nothing else.)
So the problem is:
1. I used ES File Explorer in root mode, mounted /system as writable, and made an edit to build.prop (added "qemu.hw.mainkeys=0" to the end of the file to enable navbar) and saved the file. I rebooted the phone and now it is stuck with a looping Samsung logo.
2. I have made a backup of build.prop and placed it in /sdcard/ but unfortunately I haven't made a copy on my PC. Also note that I don't have an external SD card, I am using the 16GB space that came with the phone. So the build.prop backup is on the phone.
3. I do not have a USB cable (I have one that has a loose connection somewhere and my phone is not detected 99% of the times I've used that cable)
What I have found after 2 hours of searching online:
1. Factory Reset through recovery (I am able to boot into stock recovery by doing Vol Up + Home + Power) will not restore /system partition so that won't fix this.
2. ES File Explorer might have messed up the file permissions of the build.prop file.
3. I can use PC ODIN to flash the stock firmware (I might lose data but at least the phone would be back to normal).
4. I can use adb to push a good build.prop file and set the correct permissions (my most fav. set of instructions are from here: http://forum.xda-developers.com/showthread.php?t=1660596 Of course I got the idea from several other threads)
5. I can sideload a good build.prop file that someone might be generous to provide me using adb.
I don't have a data cable, so you can see how that Might be a problem. What I DO have is a USB OTG cable and a pen drive. Now, in the stock recovery, I noticed an option "apply update from external storage". Assuming I have an update.zip with the proper build.prop in it, can I load the update.zip into a usb pen drive (formatted to fat32)? Does "apply update" here work for such zip files or is it only meant to be used for full firmware images? If so, can I just download the latest stock firmware and apply it from here without wiping the /data partition?
If I can get this resolved tonight I can get my phone up and running before tomorrow's work week. I will buy an USB cable ASAP (it's 12 AM here so going out to get it is not an option now). But even if I do, I still have 5 months worth warranty left and I'd like to stick with the stock recovery and avoid incrementing the flash counter altogether, despite Triangle Away.
Thank you very much for the help in advance.
Adb pull your backup» then push it back?
slaphead20 said:
Adb pull your backup» then push it back?
Click to expand...
Click to collapse
I don't have a working data cable, so I cannot connect to the PC. That was my first idea, though, thanks! I am currently reading about making an Update.zip. It's very unfortunate that I didn't note my firmware details after the OTA...
Just set permissions - use Properties in ES FE in root mode. RW. R.. R.. should work.
LenAsh said:
Just set permissions - use Properties in ES FE in root mode. RW. R.. R.. should work. If not try 777 for giggles.
Click to expand...
Click to collapse
I am unable to boot into the phone, it is stuck in a bootloop
I don't have a USB cable to use ADB. I don't even have a custom recovery. All I have is the stock recovery and the option to "apply update from external storage". I now remembered that I also have an SD card on which I can put an update.zip or the stock firmware. Unfortunately I didn't note down the firmware details after the last OTA from 4.1.1 to 4.1.2, so I don't know which one to download.
Can I use the option "apply update from external storage" to flash an update.zip or is that only meant for full firmwares? Thanks!
Oops - silly me.
You are running stock recovery - never use it but does it have a fix permissions option?
Failing that you may have to reflash the ROM. Stock recovery is very restrictive on what you can flash.
LenAsh said:
Oops - silly me.
You are running stock recovery - never use it but does it have a fix permissions option?
Failing that you may have to reflash the ROM. Stock recovery is very restrictive on what you can flash.
Click to expand...
Click to collapse
Fix permission option on the stock recovery? I don't think so, haven't been able to find it. Here are the options I have:
reboot system now
apply update from adb
apply update from external storage
wipe data/factory reset
wipe cache partition
apply update from cache
Interestingly, when I selected the last option, it had these 3 folders:
fota/
lost+found/
recovery/
I was hoping fota/ had the files from my last OTA update but nope.
I guess you are not sure whether I can flash an update.zip through stock recovery... so I just have to wait till I get my USB cable and try out some adb magic?
EDIT: I'm retiring for the day. Thanks for the suggestions @LenAsh and @slaphead20. I'm gonna buy a cable next week and try to set the permission to 644 (RW-R-R) using this thread as my reference (http://forum.xda-developers.com/showthread.php?t=1660596). Thanks for your suggestions, I will post back when this is all resolved.
In the meanwhile, please keep the ideas coming
PS: Oh wait, I am still curious. What is the worst thing that could happen if I try to flash an update.zip through stock recovery? I am very curious to see if it will work.
You could flash a later custom recovery (this one works well http://forum.xda-developers.com/showthread.php?t=2002953) via Odin and then fix permissions that way. Even if that doesn't work, you could then flash anything you like without having issues that the stock recovery presents.
EDit: still need a cable though...
Trouble is he hasn't got a cable, I had same thinking, that he could use the aroma file manager in philz but he's stuffed without a cable!
Possible to make an update.zip with just the build.prop in it. Copy it to a memory card and use recovery to flash it?
I would try that first.
Edit: i just remembered i have done that a few times with my htc desire. Was running clockwork mod though.
Its really easy, find a small flashable mod in zip format and delete all the mod files and copy your build prop in. Edit the updater script to just write your /system/build.prop.
Copy the zip to you mem card. Use a usb adapter in a pc, stick it in your phone and use recovery to flash from external sd.
And after typing all that i reread your post and your running stock recovery and i think you would need a signature or something on the zip so it would not work. Ooops.
Sent from my GT-I9300 using xda premium
Stock recovery won't let you flash anything much... so perhaps his only option is Odin. When he has a cable.
On a side-note, how can someone not have a USB cable of any kind kicking around??
LenAsh said:
Stock recovery won't let you flash anything much... so perhaps his only option is Odin. When he has a cable.
On a side-note, how can someone not have a USB cable of any kind kicking around??
Click to expand...
Click to collapse
Just edited my post
Sent from my GT-I9300 using xda premium
@LenAsh, @slaphead20, @ficti0n851
Hehe, yeah, I'm stuffed without a cable I lost it recently and I'm the only one with a recent phone. All my family members' phones use different cables.
Anyway, I managed to borrow a friend's cable and am currently downloading drivers for the S3. Once that's done I will use ADB to set the file permission and try rebooting my phone, failing which I will restore the backup build.prop, set permissions and reboot the phone. Failing which... well, maybe I'll reflash the stock firmware (I managed to find out the exact build details btw! )
I'll keep you posted, thanks for taking the time guys
--
EDIT:
ADB was a success! I got in and changed the permission to 644 and rebooted, done! Funny thing was that /system/build.prop file was not even there, there was only /system/build.prop.bak. I was not able to find my original backup on the sd card, but I copied the .bak file (probably generated by ES FE) and set its permissions and that worked. And now I have also have the software keys!
Thanks for your comments guys. This was fun!
----
EDIT 2:
For anybody else who has the same problem, I did it using the commands in these great ADB guides:
http://forum.xda-developers.com/showthread.php?t=1660596
and
http://forum.xda-developers.com/showthread.php?t=879701
Also, how do I edit the title of the topic? Want to add a [Solved] tag.
ficti0n851 said:
Possible to make an update.zip with just the build.prop in it. Copy it to a memory card and use recovery to flash it?
I would try that first.
Edit: i just remembered i have done that a few times with my htc desire. Was running clockwork mod though.
Its really easy, find a small flashable mod in zip format and delete all the mod files and copy your build prop in. Edit the updater script to just write your /system/build.prop.
Copy the zip to you mem card. Use a usb adapter in a pc, stick it in your phone and use recovery to flash from external sd.
And after typing all that i reread your post and your running stock recovery and i think you would need a signature or something on the zip so it would not work. Ooops.
Sent from my GT-I9300 using xda premium
Click to expand...
Click to collapse
Hey, I know this post is from forever ago, but is there a chance you could explain this step by step for a noob?
I have got my phone stuck in a bootloop by fiddling with build.prop, and I have the original file before playing with it. I have a rooted device with custom recovery, so how I could I use minimal ADB to push the original build.prop located on my device (sdcard) to root/system??
---------- Post added at 11:11 PM ---------- Previous post was at 11:06 PM ----------
gautham_y said:
@LenAsh, @slaphead20, @ficti0n851
Hehe, yeah, I'm stuffed without a cable I lost it recently and I'm the only one with a recent phone. All my family members' phones use different cables.
Anyway, I managed to borrow a friend's cable and am currently downloading drivers for the S3. Once that's done I will use ADB to set the file permission and try rebooting my phone, failing which I will restore the backup build.prop, set permissions and reboot the phone. Failing which... well, maybe I'll reflash the stock firmware (I managed to find out the exact build details btw! )
I'll keep you posted, thanks for taking the time guys
--
EDIT:
ADB was a success! I got in and changed the permission to 644 and rebooted, done! Funny thing was that /system/build.prop file was not even there, there was only /system/build.prop.bak. I was not able to find my original backup on the sd card, but I copied the .bak file (probably generated by ES FE) and set its permissions and that worked. And now I have also have the software keys!
Thanks for your comments guys. This was fun!
----
EDIT 2:
For anybody else who has the same problem, I did it using the commands in these great ADB guides:
http://forum.xda-developers.com/showthread.php?t=1660596
and
http://forum.xda-developers.com/showthread.php?t=879701
Also, how do I edit the title of the topic? Want to add a [Solved] tag.
Click to expand...
Click to collapse
Bro, I got the same problem as you had, except that I have a custom recovery, and the original build.prop file, and a USB cable, but I still haven't figured out what to do completly. Can you please take a minute to explain this for a complete noob? You have probably forgot all about this, but I am shooting for this chance. :/
black_hawk1990 said:
Hey, I know this post is from forever ago, but is there a chance you could explain this step by step for a noob?
I have got my phone stuck in a bootloop by fiddling with build.prop, and I have the original file before playing with it. I have a rooted device with custom recovery, so how I could I use minimal ADB to push the original build.prop located on my device (sdcard) to root/system??
---------- Post added at 11:11 PM ---------- Previous post was at 11:06 PM ----------
Bro, I got the same problem as you had, except that I have a custom recovery, and the original build.prop file, and a USB cable, but I still haven't figured out what to do completly. Can you please take a minute to explain this for a complete noob? You have probably forgot all about this, but I am shooting for this chance. :/
Click to expand...
Click to collapse
Hey, are you still having problems or did you solve it yourself? Anyway... If you still don't know what to do, describe best what you did to end up in a bootloop. As far as I understand what your problem is, you should use your recovery to move the backup of the original build.prop file to the system folder.
I changed my phones build.prop and when rebooted it does not started and ended up in bootloop and when I searched for how to fix this problem it showed that clear all the data from the phone but nothing happened and when I tried to install custom ROM in my phone my pc is not detecteing my phone .so what should i do ?
@Rajsh90: pull out battery for some minutes, put it in, reboot into downloadmode. Connect with PC, start Odin and hope that a COM-flag colours. Flash latest firmware.
Hi there ! I have a big issue with my Prestigio 4040.I put a modified vold.fstab file in the system folder and after restarting it doesn't read my sd card.I tried to enter the recovery mode , the robot stays with a triangle with ! inside it and it doesnt work.I tried to go from a browser to download the original vold file but the browser doesn't let me download the file cause it needs sd card.I tried modifying the file using total commander it didn't work.Can somebody help me please ?
CoolViber said:
Hi there ! I have a big issue with my Prestigio 4040.I put a modified vold.fstab file in the system folder and after restarting it doesn't read my sd card.I tried to enter the recovery mode , the robot stays with a triangle with ! inside it and it doesnt work.I tried to go from a browser to download the original vold file but the browser doesn't let me download the file cause it needs sd card.I tried modifying the file using total commander it didn't work.Can somebody help me please ?
Click to expand...
Click to collapse
ive noticed that when these kind of problems occur, even hard reset doesnt help much. Only thing that is is to flash the original software, or at least LEWA ports, as these are changing and reverting root files back to working state. so i suggest you download these:
http://4pda.ru/forum/dl/post/2599564/1.0.10.part1.rar
http://4pda.ru/forum/dl/post/2599568/1.0.10.part2.rar
extract, and flash it trough SP flash software, if you dont know exact procedure, well google it out, these things are the same regarding to mt6575 series of chips.
Best of luck
Hi
I have a Prestigio PAP4322 and yesterday i decided to root it.After rooting I deleted the settings.apk (accidentally touched that) and now my phone is kinda useless.I dont have a backup.
I searched for a backup and found one.Extracted the settings.apk but that didnt solve anything since it couldnt be installed.Than i tried to install the rom manager to restore the backup that i found,but my device isnt supported clockworkmod and i cant boot into clockworkmod recovery to restore that backup.
Than i found somoene that told me to put the setting.apk file in the system/app folder and than restart the phone.After restarting the phone,he stuck in the loading screen.Tried a lot of times and he still stuck at loading screen.
So i decided to boot into system recovery and wipe data/factory reset.
And now my phone is unrooted,cant access play store (after selecting to log in with an excisting account the app crashes),settings.apk is still missing and i cant turn on usb debuging(since settings.apk is missing).
Pls help
dark3578 said:
Pls help
Click to expand...
Click to collapse
it's kind of difficult
but, if you can rooted it again, maybe you. can try to push the system.apk to system/app folder again, but don't forget to give the same PERMISSION like the others Apk in that folder, then reboot your phone
if it's still doesn't working, use adb to push the system.apk into system folder
nasheich said:
it's kind of difficult
but, if you can rooted it again, maybe you. can try to push the system.apk to system/app folder again, but don't forget to give the same PERMISSION like the others Apk in that folder, then reboot your phone
if it's still doesn't working, use adb to push the system.apk into system folder
Click to expand...
Click to collapse
I know how to root it,but cant turn on usb debugging.If you can help me to turn on usb debugging...
dark3578 said:
I know how to root it,but cant turn on usb debugging.If you can help me to turn on usb debugging...
Click to expand...
Click to collapse
make sure to instal USB driver first and Android SDK on your computer, then you can doing debugging
use Android Commander Software to get Easley pushing to the system