Recently I was playing around with my Samsung GT-P3110, having just rooted it.
I transferred a file using adb push, it appeared to work, the problem is now I can't get it off, nothing I do using root and command line on the tablet or root explorer makes it budge!
I did the transfer after an aborted rom install which left my tablet going straight to CWM recovery, I was trying to transfer a backup onto the tablet. Trouble is that I am now running low on space and this folder is about 2Gb.
I can't see an adb command to delete from the tablet, plus adb is no longer seeing the tablet either!
Any ideas?
Cheers,
Katoiam
I followed you on your little quest for an answer, and was saddened by the response. Not one helpful word, just a bunch of people telling you to go somewhere.
I don't own a Tab myself, but encountered the exact same problem on my G3. There was no way to edit the permissions, so Android considered it untouchable.
The solution is an easy one and I can't believe no one could spare the time to say "Delete it in Recovery" but that's what it'll take.
Related
I have a G2 that was running a cyongenmod based rom of some sort or another (can't remember) and over the past few days it started freezing and hanging on boot and acting generally weird. Well, now it will not fully boot up. If the red cynogenmod animation goes away at all I am presented with a powered up yet black screen. Anyway, because this seems like a straight up software issue I thought that perhaps installing a new rom would solve my problem. The problem is that in its current state I can't figure our how to move the new rom I downloaded from my PC to the phone.
I had hoped to use adb and just code in the proper command but I can't seem to get the command right.
Any help?
A few details:
When connected to my PC via USB it is recognized by adb
I have the new .zip file in a few places on the PC, both the desktop and the platform-tools folder
I guess I could buy a microSD card adapter and just do things that way but I would rather save the trip and the money and learn something new.
Never mind, I was able to execute the command, but now I have a different question.
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 ! )
http://www.youtube.com/watch?v=JmvCpR45LKA
I have seriously searched EVERY DAMN INCH of the Internet for this. Okay, obviously, I've seen all the posts like this one:
http://forum.xda-developers.com/showthread.php?t=2351390 (I actually wanted to reply there but can't, sad)
And I've done all those steps, I've uninstalled everything, I've reinstalled everything, I've called my mom to tell her she wasn't lying to me about me being special, I've done it all ten times. This is what happens:
System stuff: Windows XP, cyanogenmod 10, ADB and Apps set to root, USB debugging on, Android 4.2.2, latest Android Commander, Galaxy S3 Sprint, Android Debug Bridge version 1.0.31
I open cmd and type adb devices, it shows me a device is available:
adb server is out of date. killing...
* daemon started successfully *
List of devices attached
ba0a8be4 device
I open Android Commander, it has a blank line that's highlighted blue, I click "OK", it says:
Connected device has status offline and cannot be used. Please reboot your device.
I reboot my device, same thing happens.
Does anyone have any ideas? I'm seriously about to just flash it to 421 but I hate just giving up. I hate it almost as much as I hate asking for help. I spent 7 hours last night (I was up until 2am!!) and then another 4 or 5 today just trying to figure this out. I'm completely lost here. Oh, another thing, since I'm at it, does anyone know how to delete the saved RSA key from my phone? I looked in that data/adb place that link said and renamed it but it didn't seem to reset the key... maybe I need to restart, I'll try restarting after I rename it. Yep, I bet that'll work. It probably had it in memory. Anyway, pointless rant about RSA done. I hope someone has some ideas before I resort to just sitting in the corner, cuddling up with my phone, and crying until my mommy tells me I'm special.
Another possibly important thing is that Droid Explorer works briefly (I can see phone's files come up) but then crashes when I try opening anything.
It also, as I was just playing with it, seems like Android Commander causes the adb server to become outdated. Does that mean anything? I just ran adb devices, then tried AC, then did adb dev again and it needed to restart the service. I don't know if that means anything. Just something I noticed.
Oops I had to update the link, I just realized I copied the wrong one from the page suggestions it does. This now has the one I meant.
Did you find a solution? I am having the same problem.
I gave up. Flashed stock, then cm 10 with system and cache wipes then cm 10.1 without wiping system. Haven't tried with my computer since I mostly use my phone. I'll check later and update this and let you know. I would have just kept stock but my god that stuff sprint puts on sickens me......
I found a solution and it works.
http://forum.xda-developers.com/showpost.php?p=40276190&postcount=1488
Yeah, I even said in my message that I made sure that was up to date. I was able to connect to adb and see it show up as a device now but Android Commander doesn't work. I did find out that adb push (and I assume pull) works but that probably worked before and I just didn't try. Anyway, I'm not too concerned. Glad you got yours figured out.
Hope this helps!
I managed to get android commander to work by installing the latest adb with the sdk manager and then I copied adb.exe, AdbWinApi.dll and AdbWinUsbApi.dll to the bin folder located where ever you install android commander!
lukesheardown said:
I managed to get android commander to work by installing the latest adb with the sdk manager and then I copied adb.exe, AdbWinApi.dll and AdbWinUsbApi.dll to the bin folder located where ever you install android commander!
Click to expand...
Click to collapse
Copying the adb files to the bin directory worked for me, thanks!
Good Evening,
I have a Motorola G.
I was running a rooted version for a while, although I am admittedly not an expert. however, i did follow the steps and it was working fine, for about a year.
Well today i was low on internal memory space available, and tried transferring some more data onto it. I didn't realize the size of the data. I got a message from the computer saying there was no more space, and unplugged and went to work.
Phone was not really responsive, but I figured I would delete a couple things once I got to work until I could clear it out.
I took phone out, and it's on a black screen. I tried to restart it, it's freezing at the blue M .
Nothing seems to work, I think the memory is just so full the phone can't even boot, so I decided to do a hard reset. Unfortunately, I'm having some difficulty. I've downloaded and installed the updated Composite ADB Driver from Google, and it DOES show in the Device Manager when I plug in the phone.
I've also downloaded the SDK manager and updated it. I plug the phone in and administratively launch a command prompt. I direct the Command Prompt to the folder containing a recovery.img file, and from that point I am lost. The computer doesn't seem to identify the phone , i'm getting either or error: Device not found.
I'm not sure what I've done wrong, I am sure i'm using the newest ADB Drivers......
I tried the "adb devices" within the command prompt, and in that case it comes up blank....
Can someone please help me?
Thank you....
Hello all,
So I have a Kindle Fire HDX and I decided to try play around with safestrap on it. It was going well but me being stupid didn't realise that when I was wiping everything, I was not just wiping the contents of the rom slot but the entire device! So I am in a soft-brick state at the moment, which is OK because I have been here with lots of devices before, just not any quite as restricted and complicated as the HDX. So my only option is to push the zip file or sideload it through ADB, which seemed to be a fairly easy task. My first challenge was installing the necessary drivers for windows 8.1 to recognise the device in adb sideload mode. I managed to do this successfully however now I have a problem when trying to sideload or push files to the device. When sideloading, the server starts successfully but I get a *failed to write data 'protocol fault (no status)' * error. When trying to push files I get an error:closed, the same by running the usb command (I am not sure what this one does but I seen it as a possible solution so have tried it). When I run the devices command I see my device connected and it is shown to be in sideload mode. I have tried the following in order to resolve this error, all have been unsuccessful:
New USB cable
Different versions of ADB (minimal and android studio)
Different computers and operating systems (each again with minimal adb and android studio)
Updating the packages in android studio, including installing the official kindle fire driver from amazon
Killing the server and starting again
None of these steps have helped and I am finding this to be incredibly frustrating as in every thread I have read online one of these solutions has managed to fix the problem for the person asking the question. I figured there isn't a place on the internet with a better knowledge and understanding of adb than here so there would be no better place to ask. Any help you guys could offer would be much appreciated. Also I am relatively new (and dumb) when it comes to adb and using the command line so if you guys could dumb it down as much as possible that would be brilliant.
Thanks in advance
EDIT: I have also noticed that when trying to format the device from the TWRP menu I get an 'unable to locate device to partition' error. I'm guessing this has something to do with it
Just thought I'd update this thread with the fix I found in case anyone else in future has this problem and googles around. I am not sure if I specified but the issue was with a kindle fire hdx 7". Safestrap would not let me change the active rom slot to the default OS and it was stuck in rom slot 1. So I contacted amazon and asked them if there was anything they could do to help me. They started off by giving me the usual reset by holding the power button. I thought there is no way that could fix it because I wiped the system files and that is the problem (I could see from TWRP that the system files were empty). So just in case I done as he said and after holding for a full 40 seconds, the previously soft bricked kindle booted back into the stock os and whilst it was completely wiped, it was now fully functional! I am sure this will only work for a very small percentage of people with a soft brick but definitely try it none the less. I would be interested to hear anyone who actually knows the technical aspects of this chime in with what happened here. Did it just look like I wiped the entire system in TWRP because it was hiding the system files? (even though I could see the folder and it appeared empty). Or does the kindle have a built in recovery drive through which it will replace these files when the power button is held for 40 seconds?
Hi,
Thanks for using XDA Assist if you are getting partition error then possibly your partition table is wrong rectify it and see
Good luck!
No Response .. Thread Closed .. Thanks