This is becoming the hardest way to root apparently -_-
I`m trying to get z4root on to my Galaxy S Captivate from Rogers (SGH-I896)
I`ve downloaded the apk file and placed it on my desktop, when trying to copy the file to my phone I get this error message.
(I tried to post a picture here but apparently I need to post 8 times?*fail)
It says an unexpected error is preventing the operation.
Error 0x80070057: The parameter is incorrect.
clicking try again just prompts the message again.
Phone is connected in USB mass storage mode.
USB debugging is on.
It appears the app is no longer available in the market so is this the only way to get it on my phone?
I've literally tried downloading the apk 5 different times from different places and they all give the same message when I try to copy, also tried copying the file pretty much everywhere possible on the phone. any help would be greatly appreciated.
If i connect my tablet to a computer the computer sees it but doesnt see it, I need to flash a new rom because my rom file got messed up, and it wont let me pull it off a thumbdrive through the dock.
Edit:
I'm getting " The process Android.process.media" has stopped unexpectedly please try again.
when i try to open a file delete a file view media, OR start the tablet.
Hi to all here. i just want to ask anyone what to do with my phone. well first of all, my phone is a sky pantech vega racer im-a760s, not really a match for samsungs popularity but budget wise this is the model for me. it has a dual core. now my problem starts when i started editing the build.prop in its system (tweaked for some texting problem of limited character sending). of course i know what im doing on that part, but the only thing i didn't think that would happen was, i copied it in my computer, i edited it there, then i saved it as "all" in file type so it wont become a ".txt" format. but when i placed it in my phone. the file instantly disappeared, i think it was only hidden and the phone just cant identify it nor read it like something. now i restarted the phone, it booted up to its logo then it just went blank and it just stops there. i tried pushing recovery with adb in my pc cmd. but it cannot detect my device(no problem with my adb installation to eliminate this from the question), i also tried putting an sd card with a recovery file but there was no option for sd card path. but the phone can still function well, i know because it can still be loaded under flashboot, download screen and S / W upgrade menu and it can still perform wipes for all partition and caches and can reset for factory settings etc. but whenever i will reboot, its not going to complete. anyone please help me how to make my phone be detected by my pc. The usb drivers are just fine, updated it many times, read all procedure for making the driver connect perfectly. i reformatted the sd so it wont be a problem when i put it in. but in the recovery menu i just cant see my sd card, theres just the option for "update from external storage" but it doesn't have anything inside. what a mess. i cant make my phone reflashed cause its not responding with the connection with my pc. but when i am opening an odin (just used for connection monitoring) there are two yellow boxes with com port like these: 0:[com7] and 0:[com9], so i know it is still somehow communicating with my pc. please help any advice, i dont want to resort to jtag for im not sure if it will support my phone and it's already avialable for the model but definitely not going to send my phone for repair cause it will be costly. thanks to all who will respond. Please help thank you. additionally: OS was ics version 4.0.4 and rooted. already gone through rooting several times with no problem. just the editing part.
to edit Android files on Windows use only Notepad++ anyway do not use Windows notepad this is for Windows files formatting only
well, you have to get build.prop from your phone edit on PC then copy back
so enter recovery connect phone to PC create a folder say C:\tmp
to get build.prop from phone
Code:
adb devices
adb shell
mount system
exit
that's to mount system partition then
Code:
adb pull /system/build.prop C:\tmp\build.prop
edit it and copy back to phone
Code:
adb push C:\tmp\build.prop /system/build.prop
maybe is not your case ? but I wanted to give you an idea
@ruscan.calin
Thanks, great. i will try this one once i get my phone recognized by my pc, adb seems not able to find my devcie have this message like this one:
"
c:\>adb devices
adb server is out of date. killing...
*daemon started successfully *
list of devices attached "
and that's it nothing happens.
thanks for the advice i will definitely use this once i get my phone connected with my system. thanks a lot
cruelink said:
@ruscan.calin
Thanks, great. i will try this one once i get my phone recognized by my pc, adb seems not able to find my devcie have this message like this one:
"
c:\>adb devices
adb server is out of date. killing...
*daemon started successfully *
list of devices attached "
and that's it nothing happens.
thanks for the advice i will definitely use this once i get my phone connected with my system. thanks a lot
Click to expand...
Click to collapse
start phone in recovery mode do not connect to PC at this time
open Device Manager now connect phone to PC
if you see ADB Interface connecting in Dev Manager it's ok if not you have a problem with phone drivers so install it again
ruscan.calin said:
start phone in recovery mode do not connect to PC at this time
open Device Manager now connect phone to PC
if you see ADB Interface connecting in Dev Manager it's ok if not you have a problem with phone drivers so install it again
Click to expand...
Click to collapse
Hi, cant still afford to make the adb component in my device manager to appear, but it's good to inform you that it helped me a bit because i was able to see the storage of my phone and i was also able to put some files in there without any hassle that alone was satisfying me that my phone is not really dead. sad to say i did everything i could to have my pc detect my phone via recovery menu, but still no devices found. it's really weird that some links are saying that i should make my phone's "usb debugging" enabled, wherein fact i cant even go beyond my original problem(bricked phone), i can't even see the inside of my phones directory, only the storage one that was activated just recently. i even did a reinstallation of my usb, uninstalled every other phone related usb installation to avoid conflicts reinstalled my phones proper usb installer then restart. no progress still to be called. it makes me feel that the phone was just trap in the state of booting and not knowing what to do because it cant see any command inside its system. i cant go into the systems directory as well. and that's the only way i think i could revive my phone in replacing a new build.prop, as you advised to be edited in a notepad++ which i recently acquired and installed. by the way how do i save the build.prop to its original file format, and what is the extension. thanks alot for helping out. im getting a little brighter each step of the way, im not loosing it to come to smashing my phone to pieces instead of keeping a very expensive paper weight.
usb debugging enabled is not useful in this case (you can't set it )
build.prop is a file with .prop extension save file with notepad++ name it build.prop then check location of file it should be build.prop notepad from Windows saves it as build.prop.txt that's not good also notepad adds some formatting characters inside file that's wrong so use only Notepad++ when working on Android files (or VIM for Windows editor etc anyway do not use Windows editors they are good for Windows files only)
-try these things on another computer (to install drivers etc)
-I advised somebody to send a mail to manufacturer and he got a reply with a link to stock rom... that's great !
-if you link me your build.prop file I can tell you if it's ok
-pc link - that's to be solved firstly check manufacturer site for sync software/ drivers even send mail
isa. rgiespea
ruscan.calin said:
usb debugging enabled is not useful in this case (you can't set it )
build.prop is a file with .prop extension save file with notepad++ name it build.prop then check location of file it should be build.prop notepad from Windows saves it as build.prop.txt that's not good also notepad adds some formatting characters inside file that's wrong so use only Notepad++ when working on Android files (or VIM for Windows editor etc anyway do not use Windows editors they are good for Windows files only)
-try these things on another computer (to install drivers etc)
-I advised somebody to send a mail to manufacturer and he got a reply with a link to stock rom... that's great !
-if you link me your build.prop file I can tell you if it's ok
-pc link - that's to be solved firstly check manufacturer site for sync software/ drivers even send mail
Click to expand...
Click to collapse
that's great news, you actually come to emailing the phones manufacturer? wow, im flattered. well you're a very nice guy to help me out on this. and i have good news too. i found out that i have a little conflicting usb drivers, as i have installed samsung for my previous phone(samsung galaxy 1) i had it liquidated for this new one. but a little hard on the support. you gave me a new idea about the usb. so i uninstalled all the related usb drivers and have it reinstalled. now i am able to communicate with OTA firmware server, and i got a reading that was not happening before(stucked in just detecting the phone) now i have a percentage reading of downloading or so. but i still have to wait if it will complete and have it repaired. so by now you can give me a little more help cause im still not at it in pushing through the use of adb programming. and the link you mentioned, i'll wait for the progress about it and see what really was it. and thanks a lot. really appreciate it.
fixed bricked phone via OTA by fixing link to pc.
Hi, i thank you for your help. i managed to fix the phone myself. i just missed the simple step that you advised me. fix the link first to pc. i have installed another model of the phone for the same manufacturer with different type so that was causing the mixed up for updating and recovering via the OTA site of the phone. so yey. you helped a lot. i thank you. i am now running at ics version 4.0.4 and now rooted. i will not commit the same mistake of saving the build.prop with another format. that was bad. so then i'll be very careful in editing the build.prop and first of all, i will keep a backup inside where i can access it even if it will be hard bricked. never forget that one from now on. so this is it. i thank you. of all the place ive been circling around for answer. here is where i found it. and just one person. hooray. thank you very much.
cruelink said:
Hi, i thank you for your help. i managed to fix the phone myself. i just missed the simple step that you advised me. fix the link first to pc. i have installed another model of the phone for the same manufacturer with different type so that was causing the mixed up for updating and recovering via the OTA site of the phone. so yey. you helped a lot. i thank you. i am now running at ics version 4.0.4 and now rooted. i will not commit the same mistake of saving the build.prop with another format. that was bad. so then i'll be very careful in editing the build.prop and first of all, i will keep a backup inside where i can access it even if it will be hard bricked. never forget that one from now on. so this is it. i thank you. of all the place ive been circling around for answer. here is where i found it. and just one person. hooray. thank you very much.
Click to expand...
Click to collapse
that's good news ! and thanks for feedback
feedback is an invaluable resource ! (some just forget about that from my experience :laugh: NOT your case ! )
I am running a CM11 Nightly on my jfltevzw. I am trying to update to a new nightly by dragging and dropping it onto my phone, the way I always do. However for some reason when I try to do it now, I get an error message saying "Cannot copy item: This device has either stopped responding or has been disconnected." even though it shows up on my explorer. I have no idea what happened. It was working fine like a day ago. I have rebooted my computer and everything, but it just won't work. Help!
Usually CM roms have this kind of MTP bugs when you move big files, try rebooting your phone, if you still got a problem, try using adb, or Usb Mode, or copy files over wifi (Airdroid, or ES file explorer ..)
silv3rfox said:
Usually CM roms have this kind of MTP bugs when you move big files, try rebooting your phone, if you still got a problem, try using adb, or Usb Mode, or copy files over wifi (Airdroid, or ES file explorer ..)
Click to expand...
Click to collapse
How do I get to USB mode? I tried ADB and it didn't work.
Rooted Nexus 5 running stock 4.4.4. Trying to copy the large TWRP folder from nexus 5 to Windows 8.1 laptop using the usb cable that came with the nexus.
Copying starts fine but at the last "15 minutes remaining" to finish point, the copying stalls and Windows puts up a popup saying it couldn't find the object to copy. When I try to go elsewhere in the nexus file structure I discover the connection has been lost and Windows can no longer see the nexus 5 files. So I need to shut down the laptop to safely disconnect the nexus.
This happens repeatedly. Smaller folders copied fine.
Is this because there is something special about twrp nandroid backup files that make them uncopyable, or could this mean there is a corrupt file or something else?
What should I do?
Anderson2 said:
Rooted Nexus 5 running stock 4.4.4. Trying to copy the large TWRP folder from nexus 5 to Windows 8.1 laptop using the usb cable that came with the nexus.
Copying starts fine but at the last "15 minutes remaining" to finish point, the copying stalls and Windows puts up a popup saying it couldn't find the object to copy. When I try to go elsewhere in the nexus file structure I discover the connection has been lost and Windows can no longer see the nexus 5 files. So I need to shut down the laptop to safely disconnect the nexus.
This happens repeatedly. Smaller folders copied fine.
Is this because there is something special about twrp nandroid backup files that make them uncopyable, or could this mean there is a corrupt file or something else?
What should I do?
Click to expand...
Click to collapse
There isn't anything special with TWRP backups. I'm also using Win 8.1 and never got such problems. Try this: http://www.nirsoft.net/utils/usb_devices_view.html. Run as admin, delete all usb related drivers, restart laptop and try again. BTW - you don't need to shutdown laptop to safely remove Nexus.
Thank you very much. I have adb installed. Will deleting these drivers mess up my adb installation?
SOLVED
I solved the problem. In case someone else runs into the same problem, here's the solution I discovered.
It did have to do with the size of the folder - indirectly. The problem was the 2 minute screen timeout I have on my nexus. When the display shut off on the phone the copying stalled. I changed the display timeout to 30 minutes and the folder had time to copy successfully. Obviously I don't want the display timeout to remain at 30 minutes and returned it to 2 min.
Note:
I was copying using the laptop. Maybe if I did it using the phone with a file manager like ES Explorer (if that is possible) this timeout wouldn't be a problem. Don't know. But at least I solved the problem for me.