Hello all. I hope this community that looks so professional can help me with this, I will help as far as I can people here too, however Android is not my strong point.
Well, I've been asked to get access to a Samsung Galaxy Mini that is password locked. The owner of this device is not a computer-friendly person, neither a device-friendly one. So we have the password lost, and USB debugging is disabled neither root has been applied to this device. So, I've been reading some threads here, and that's what I've done:
1. Reboot the device and enter into system recovery mode.
2. I tried to do an "adb push" to put the rooting file into sdcard but I got a "permission denied" message.
3. I tried to access /data/system/ directory to delete password.key but I can’t do the “cd” to this directory.
So I don’t know what to do. We don’t want to reset the device to factory defaults. What could I do? Any help will be appreciated.
Related
Okay here is the thing, I am a bit of an advanced user, and have been flashing ROM's for quite a while, so i am not a noob and I have already tried everything in the book to fix my problem.
Info:
1- Drivers installed on Windows 7 and have been working for the past 4 months.
2- USB Debugging ticked
3- Windows recognizes the Galaxy Tab 7" GSM (P1000 International)
Problem:
1-Running "adb shell" in adb results in: error: device not found
2-CWM Restore stops at android_secure.img not found and aborts.
How did it happen (Detailed):
1- Was on Overcome 2.0.1 "Hermes" and found out that there was an update on kies from someone.
2- Decided to restock
3- Flashed P1000JPJM5 (I already did that quite a few times and no problems ever occurred from that)
4- When i restocked i wanted to root, so i went into settings>Application>developement> and ticked USB Debugging
5- Plugged in USB and I opened up Super One Click Root v1.7 and hit Root, however, Nothing happened and it was "Waiting for device" forever.
6- tried Super One Click root v1.9 with the same result
7- Opened adb and typed "adb shell" and got error: device not found.
8- I downloaded Better Terminal app from the market and tried "adb shell" and i got "Adb not found" as a result
9- I wanted to root my device to use the Bootloader Batch and change my protected boot loaders
10- tried everything, Restore factory from 3e Recovery, Doing the same from Setting>Privecy, Flashing the same ROM Over and Over again with no luck
11- learned later that flashing ChainFire's Gingerbread P1000XXJMQ is safe on protected boot Loaders so i did that
12- the problem persisted and i just cant use adb
13- I had a CWM Backup done so i thought doing a restore might solve the problem, but that resulted in a failure in restore. it stops at android_secure.img not found and aborts restore.
If anyone kow's a solution or at least knows what might have gone wrong Please shed some light on how to go about this issue.
Thanks
While the device is plugged in, go to device manager and delete/uninstall the device. Should ask you if you want to delete the driver files also, check the box and go.
After that it will probably ask you to restart, restart the computer and reinstall the device with the google drivers.
pwolfamv said:
While the device is plugged in, go to device manager and delete/uninstall the device. Should ask you if you want to delete the driver files also, check the box and go.
After that it will probably ask you to restart, restart the computer and reinstall the device with the google drivers.
Click to expand...
Click to collapse
well its like i said earlier it is NOT a driver issue.
I mean even Emulater apps from within the Tab are not recognizing ADB
DistortedWisdom said:
well its like i said earlier it is NOT a driver issue.
I mean even Emulater apps from within the Tab are not recognizing ADB
Click to expand...
Click to collapse
Did you at least try what I suggested?
I can't get my galaxy tab to be seen by adb either. At least not since upgrading to Gingerbread.
I'm using the
"sprint_p100_Samung_GALAXY_Tab_USB_Drivers.msi" file from the Samsung web site.
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 ! )
Im trying to access the data on a Galaxy S4 on which the screen is not working at all(no backlight and doesn't respond to touch). the data I mainly require is the contacts.db file. what I have tried sofar:
1. tried to access the data via USB but cant access the content due to the lock on the phone.
2. tried to access the data with KIES but once again failed to do so due to the lock on the phone.
3. Downloaded the ADB shell and installed the required USB drivers but cant access the phone, when running the command "adb devices" it says no devices found which I think is because the USB Debugging setting on the phone is not enabled.
4. Also tried to sync with the Google account but unfortunately it was not setup to sync contacts with the Google account.
Some other suggestions were to get another S4 and connect its screen to the the one in question which im sure will work but is there no other way to access the data or to somehow remove the pattern lock from the phone? maybe using another platform to gain full access to the phone or anything?
Hello, and welcome to XDA Assist! You may want to try this tool: [Tool][Windows] Control a device with a broken screen, or possibly use a programme such as Droid Explorer to view your files. If all fails, try and ask here: General discussion Questions and Answers. You will need to register to post.
Good luck!
Dear all,
I do have a tricky question and I know already that this could be suspicious.
Allow me describe the issue.
I have Realme 5 where the user set password (not pin or gesture), but is unable to remember.
Now when phone starts (even before Android boot) it asks for password (not gesture or pin) which the user is unable to repeat.
Easy solution is factory reset, which is fine to be done.
But there is number of photos he wants to safe.
And I'd like to ask if there is a way to do so.
USB Debug is not allowed, therefore my thinking to use ADB is no possible as phone is not visible.
Is there any way to achieve the goal to safe the photos?
Can I make a backup, do factory reset and restore from backup?
Or is there any other chance? Via recovery/custom ROM? I guess not, since USB Debug is not allowed, right?
Thank you for hints or send me PM if you do not wish to discuss it here.
Jindrich
thanks all who checked this out.
I know how "silly" the request is, as this would be solution for any stolen device.
On the other hand, I was thinking about approaches and seems to me there is no way
Since I do not know pwd, I can't use recovery either, although there is sdcard slot, since I'll be asked for pwd before entering recovery (or before installing something via recovery).
I can't use ADB either, due to USB debug not enabled, this is also a dead end...
So I do not see a way how to get access DCIM folder..
J.
Hi, I've a tablet which needed to be reset from recovery, at boot it asked to login to google account, I've tried all I have but seams I can't guess the right one. This version of Android don't let me skip this process, I've also tried to cut the network down, and all else I've read in google, there is no escape. I've wiped data and cache from recovery, didn't help. I've tried with ADB to send a "adb shell dpm remove-active-admin eu.sisik.devowner/.DevAdminReceiver" but I'm unautorized.
How can overcome it? How can I get an autorized from ADB of recovery console? There is any apk that can I upload that delete that info?
If not I have to trash the tablet and buy a new one (((
Thank you
It looks that USB-debugging ( AKA ADB ) didn't get properly enabled on the tablet, hence none of ADB commands will ever work. This cannot be changed afterwards.