Database Develop

[Q] Can I ADB pull media files from device? Help please!

Hey guys!
I've been having a lot of problems with a Samsung Galaxy S Plus recently. After my girlfriend entered the wrong picture password a number of times in a row, the phone locked down. I tried to activate data connection using the power menu (hold power button), which I had deactivated before it locked down. My attempts to log in failed when the device returned either 'invalid username' or 'invalid password' (they are - of course - neither). This is apparently a known problem. I then followed the following instructions to trick the device into thinking the google account had been verified: droidwiki .de/Muster_vergessen#Muster_l.C3.B6schen (warning, that site is in German). For this I successfully managed the following steps:
1.) Installation of ADB tools
2.) Installation of ClockwordMod using Odin in order to accomplish the ...
3.) Activation of USB debugging.
4.) Rooting the phone using these instructions: androiddrole .com/how-to/how-to-easily-root-samsung-galaxy-s-plus-i9001
All these steps worked as expected. Then however, the trouble started: When trying to set the number of failed pattern attempts to 0, the following command failed: "cd /data/data/com.android.providers.settings/databases" ("can't cd to /data/data/com.android.providers.settings/databases"). Additionally I could no longer boot into android as the phone kept booting directly into CWM (This is apparently also a known problem). I proceeded to install a newer version of ClockworkMod Touch (using zip on sd card) hoping this would allow me to break the loop. It didnt. So I replaced ClockwordMod with TeamWin Recovery Project (TWRP). This did finally allow me to exit the recovery mode only to get stuck in a full-out reboot loop: Samsung logo -> black screen -> Samsung logo -> black screen. In order to get out of this reboot loop I used Odin to flash boot_loader.tar and the original version of ClockwordMod onto the device. After a number of failed attempts this suddenly worked - kinda:
The current situation is this: The phone no longer boots directly into recovery mode (good). It doesnt boot into android either though. It just reboots over and over again - this can be stopped however by using 'Volume Down' + 'Home' + 'Power' to access ClockwordMod.
My hopes of getting my phone unlocked and working as before again are rather slim at this point. I would still like to save my substantial collection of photographs from the media folders on the device, before I wipe the entire thing (or buy a new phone).
Therefore my question to you:
Is it possible to extract the photos (stored in the standard media locations of android 2.3) to a PC using only USB-Debugging/Odin/ClockwordMod (being unable to boot into android)?
I tried to pull the media files using the 'adp pull' command, but I couldnt get it to work (maybe because I didnt get the command or the file-paths correctly). Any suggestions would be GREATLY appreciated.

Solution
Attention: If you want your media files, backup your current state first. Go to backup and restore -> backup. Then do steps written below. Backup will be in CWM folder on your sdcard.
This is called a soft-brick. It's good that you can access download and recovery mode using 3 button combinations. First, download a stock Gingerbread ROM for your device model and put it on your sdcard. Boot into CWM and select Wipe user data -> Yes. Wipe Cache Partition -> Yes. Go to Advanced menu and select Wipe Dalvik cache -> Yes. Now return to previous menu and select install zip from sdcard -> choose zip from sdcard -> select name.of.downloaded.rom.zip -> Yes -> Wait 1-2 minutes to flash -> Wipe user data -> Wipe Cache Partition -> Wipe Dalvik Cache. Then select Reboot system now from main menu, and wait 4-5 minutes for it to boot first time.
DaniTheMan said:
Hey guys!
I've been having a lot of problems with a Samsung Galaxy S Plus recently. After my girlfriend entered the wrong picture password a number of times in a row, the phone locked down. I tried to activate data connection using the power menu (hold power button), which I had deactivated before it locked down. My attempts to log in failed when the device returned either 'invalid username' or 'invalid password' (they are - of course - neither). This is apparently a known problem. I then followed the following instructions to trick the device into thinking the google account had been verified: droidwiki .de/Muster_vergessen#Muster_l.C3.B6schen (warning, that site is in German). For this I successfully managed the following steps:
1.) Installation of ADB tools
2.) Installation of ClockwordMod using Odin in order to accomplish the ...
3.) Activation of USB debugging.
4.) Rooting the phone using these instructions: androiddrole .com/how-to/how-to-easily-root-samsung-galaxy-s-plus-i9001
All these steps worked as expected. Then however, the trouble started: When trying to set the number of failed pattern attempts to 0, the following command failed: "cd /data/data/com.android.providers.settings/databases" ("can't cd to /data/data/com.android.providers.settings/databases"). Additionally I could no longer boot into android as the phone kept booting directly into CWM (This is apparently also a known problem). I proceeded to install a newer version of ClockworkMod Touch (using zip on sd card) hoping this would allow me to break the loop. It didnt. So I replaced ClockwordMod with TeamWin Recovery Project (TWRP). This did finally allow me to exit the recovery mode only to get stuck in a full-out reboot loop: Samsung logo -> black screen -> Samsung logo -> black screen. In order to get out of this reboot loop I used Odin to flash boot_loader.tar and the original version of ClockwordMod onto the device. After a number of failed attempts this suddenly worked - kinda:
The current situation is this: The phone no longer boots directly into recovery mode (good). It doesnt boot into android either though. It just reboots over and over again - this can be stopped however by using 'Volume Down' + 'Home' + 'Power' to access ClockwordMod.
My hopes of getting my phone unlocked and working as before again are rather slim at this point. I would still like to save my substantial collection of photographs from the media folders on the device, before I wipe the entire thing (or buy a new phone).
Therefore my question to you:
Is it possible to extract the photos (stored in the standard media locations of android 2.3) to a PC using only USB-Debugging/Odin/ClockwordMod (being unable to boot into android)?
I tried to pull the media files using the 'adp pull' command, but I couldnt get it to work (maybe because I didn't get the command or the file-paths correctly). Any suggestions would be GREATLY appreciated.
Click to expand...
Click to collapse

LCD broken, need to wipe data

For Phone specs see signature.
I've damaged my display i.e. my LCD is broken so nothing is displayed but I can turn the phone on as my morning alarm does go off and the 'menu' and 'back' controls light up so board is functioning.
I have decided to sell it as is, so someone else can faff around with it if they want to repair it. What I need to do now is try and wipe my data off of the phone before selling.
BUT...I'm not sure what the steps are for the N7000. I have downloaded the Android SDK and ODIN. Have also seen these instructions elsewhere...
1. Download factory_reset.tar.md5
2. Open ODIN
3. put factory_reset.tar.md5 in PDA section and do not check/uncheck anything else...
4. Put your phone in download mode and connect it to PC..........................Not sure how to put the N7000 into download mode, tbh I had only ever heard of recovery mode. Instructions were as follows....
Volume down + home +power
That will lead to warning Page
Here you have to press volume up to enter download mode.
5. Hit start and it will flash and reboot.................................What exactly am I flashing here? I thought we were just wiping data why do I need to flash anything?
Is there another or better way of wiping the data or will the above work?
Thanks

What is the recovery you have? (before you say gain to check your signature, it states philz and running 4.2.2. So confused.).
Vol up + home + power for about 10 seconds should take you to recovery mode. Connect phone to pc and run adb devices. Check if the device is listed. Then using some Linux commands you can wipe data and your internal sd card.
About adb please Google.
Using odin, if you have the file you mentioned, (idk much about the file) but what it seems to do is when flashed using odin it will run flash a blank data & cache partiton thus performing factory reset. This will not wipe your internal storage.

nokiamodeln91 said:
What is the recovery you have? (before you say gain to check your signature, it states philz and running 4.2.2. So confused.).
Vol up + home + power for about 10 seconds should take you to recovery mode. Connect phone to pc and run adb devices. Check if the device is listed. Then using some Linux commands you can wipe data and your internal sd card.
About adb please Google.
Using odin, if you have the file you mentioned, (idk much about the file) but what it seems to do is when flashed using odin it will run flash a blank data & cache partiton thus performing factory reset. This will not wipe your internal storage.
Click to expand...
Click to collapse
Thanks for getting back to me. Never got 'adb devices' to work, don't know why. For the first time I've managed to get access to see my internal storage. As I had pattern security enabled on the phone I assume I must have managed to get into recovery mode and do what I believe was a factory reset.
Am I right in assuming my personal data i.e. contacts data has been deleted?

Don't know. What exactly did you do?

wipe data/factory reset changes doesn't apply (Note N7000ZSLO2 Model:SHV-E160S)

*NEED HELP PLS*
1-My phone doesn't keep time/date/language when I reboot
2-The language goes back to French when I reboot
3-All my apps show the stop error when i make any setting change after reboot
4-Any app that I install after reboot will disappear on the next reboot, except the SU app I installed as zip from sdcard in CWM-based recovery window
5-The phone make sound when I connect to pc but doesn't to ask to chose connection mode, so pc doesn't detect it even though I have USB Debug enabled
6-I did the wipe data/factory reset several times but there's no change when i switch ON the phone even though the wipe data/factory reset was successful.
7-The only button combination that works is the one to go to Download Mode (Volume Down + Home + Power )
8-I can only go to Recovery Mode when I try to factory reset in the phone settings. The phone will restart and take me to Recovery Mode
-Odin is unable to detect the phone.
I just think is the internal storage that is corrupted or something but i can't tell for sure. So please i need ur help on how to fix this problem or if there is any app that i can install as zip from sdcard in CWM that can scan or format or fix this problem
Samsung Galaxy Note N7000ZSLO2
Model Number : SHV-E160S

[Resolved]Brick in TWRP by trying to install Elite ROM

Hey,
Here's the context: I tried to install Elite ROM.
In the instructions there was this: "Wipe Everything in wipe section (dont wipe sdcard) and Change FileSystem of DATA Partition only to f2fs & FORMAT Data otherwise phone wont boot".
I was in TWRP and followed instructions.
Wipe everything: OK
Change filesystem of data partition to f2fs: OK
Format the data partition: not OK. It said me
Code:
/data : Device or resource busy.
. I couldn't do anything from there, or I thought this way at least... I think the f2fs filesystem f*cked it.
First error: I rebooted my phone. So yeah, now I'm not in TWRP anymore. I tried to boot into Recovery but Vol Up + Power brought me to Huawei eRecovery. I tried the Huawei eRecovery but it didn't work. Expected, because I installed TWRP and apparently it doesn't work anymore when you flash it. So OK.
Basically I want to get into TWRP because I could maybe solve the problem from here. I don't know how to solve this Device or resource busy, but there is a solution, like always.
Now, there is a problem. When I do
Code:
adb devices
or
Code:
fastboot device
, I get nothing. BUT, something encouraging is that I have HiSuite that shows up when I connect my phone to the PC, everytime, even if I close it. But then, HiSuite tells me to connect my phone, so I think it doesn't recognize the phone fully. Maybe it recognizes some hardware in my phone that matches Huawei phones, but still not really recognizing my phone. My phone is not appearing on the device list of Windows, I just have a "USB Mass Storage Device" in the USB controllers.
UPADTE: I managed to go into TWRP by pressing Vol Up + Vol Down + Power, so no need of ADB for now. I'm updating. Below, only for informational purpose.
UPDATE 2: As I managed to boot to TWRP, I was able to format /data and to install Kernel & ROM from my SD card! To boot in TWRP and not eRecovery, make sure you're pressing Vol Up + Vol Down + Power and not only Vol Up + Power.
The goal is to force ADB to see the phone so I can interact with it
So for now I have several theories I tried to follow, without success:
- Forcing Debugging mode on my phone (maybe it's only that)
- Find a version of ADB that can see the phone
- Find drivers that can recognize the phone fully
An other way could be to backup the partitions saved before in TWRP. But as I can't access to TWRP without ADB on this phone, for now I don't believe this is a path to explore.
Have you any other theories, and have you solutions for these 3 majors theories?
Thank you so much and see you,
Celgost

[VolUP]+[Power] - This works if the phone is turned off. When the "data" is busy, you need to reboot into the recovery mode from the TWRP.

It's true but not totally in that case. If you aren't in TWRP anymore and wiped all partitions, you cant Access TWRP neither with ADB nor with Vol UP + Power. Because Huawei added eRecovery, which coexists with other recoveries. My theory is that eRecovery is one layer below regular recoveries. You Can Access twrp only with Vol UP + Vol Down+ Power. I suppose there is a strict condition to boot into erecovery when there is not for Twrp.

It works always, you just need to release the buttons, after the appearance of the logo.

No OS Installed! Message After LineageOS 15.1 Flash

Hi All,
I've run into an issue whilst trying to flash LOS 15.1 on a Moto x4 (XT1900-01). After flashing LOS 15.01, I get the message "No OS Installed! Are you sure you wish to reboot?" for every Reboot menu option available in TWRP (3.2.3-1) (reboot options from Reboot menu: System, Recovery, Bootloader, Slot A, Slot B). I'm not sure what happened. Here are the steps I took prior to hitting this:
1. Unlocked the bootloader
2. Flashed TWRP per the instruction on TWRP for Payton on TWRP site
2-1. fastboot boot twrp-3.2.1-1.img
2-2. adb push twrp-3.2.1.zip /sdcard
2-3. Installed the twrp-3.2.1.zip from TWRP (apparently to install to boot partition on both slots)
3. Installed LOS 15.01:
3-1. Formatted via TWRP by doing Wipe -> Format Data
3-2. Advanced Wipe via TWRP by doing Advanced Wipe -> Select System
3-3. copied LOS to sdcard: adb push Lineage15.zip /sdcard
3-4. TWRP Install by Install -> select the Lineage15.zip
4. Once complete, select reboot and this is where the message "No OS Installed! Are you sure you wish to reboot?" comes up.
I haven't opted to reboot for fear of not being able to get back to recovery. I'm not sure what to do at this point. I'd like to understand what happened, but I would also like to find a way to recover from this and either get back to square 1 with stock ROM or even better complete the LOS install. Thanks in advance!

Just reboot recovery

St.Noigel said:
Just reboot recovery
Click to expand...
Click to collapse
I tried to reboot to recovery ignoring the error, I get nothing now. Phone won't turn on, can't key combo (vol up + power, vol down + power, any of them) and it just seems dead now. I've held each of the key combos for a couple minutes each, nada. Any thoughts from here?

mikeybravo said:
I tried to reboot to recovery ignoring the error, I get nothing now. Phone won't turn on, can't key combo (vol up + power, vol down + power, any of them) and it just seems dead now. I've held each of the key combos for a couple minutes each, nada. Any thoughts from here?
Click to expand...
Click to collapse
Did you try to connect phone to the PC? Is phone charged?

St.Noigel said:
Did you try to connect phone to the PC? Is phone charged?
Click to expand...
Click to collapse
Yes, phone was at about 98 percent when doing reboot. Plugged into computer (Mac), adb devices returns nothing. Not sure how this could've gone as bad as it seems it did? Not sure of anything else I can try here...

have you access to Windows or Linux PC? I know nothing about Mac... (

St.Noigel said:
have you access to Windows or Linux PC? I know nothing about Mac... (
Click to expand...
Click to collapse
Yes, I plugged into both Mac and PC. MDM installed on PC as well adb tooling. Plugging into either computer does nothing, doesn't show up in device list. Tried the key combos while connected to each (vol up + power, vol down + power, power, power + vol up + vol down all for a couple/few minutes each). What I don't understand is what the heck happened. TWRP should've been flashed to boot on both slots based on TWRP docs for Payton. I read something about some issues with A/B slot switching (or not switching), but if TWRP was flashed to boot on both slots, I would've expected to at least be able to get back to recovery? I'm not really sure what to do from here since I can't even get the phone to turn on.

I have had seen that message on my phone too. I just reboot and it works just fine.

I ran into the same problem. I managed to fix my phone. From what I understand this happens if no OTA update was flashed before to initialize the partition structure in slot B. Check out [1] which suggests to install copy-partitions-payton.zip via sideloading it into TWRP before installing Linageos.
Concerning your brick: Your phone should still be recognized by your computer. Check the device manager or lsusb on Linux. For me I got something like "Qualcomm, Inc. Gobi Wireless Modem (QDL mode)". Reading through the threads [2,3,4] it became clear to me that I needed a "blankflash" or the qboot utility to recover the phone. The utility talks to the phone via a serial interface over USB. Look through the threads to find the qboot utility. I needed many tries to find the correct qboot utility and to get it to successfully blankflash my phone. The --debug=2 command-line switch of qboot helped me to get confidence that something is happening at all. I needed to press vol+ and power before starting the qboot utility with "./qboot blank-flash --debug=2" on Linux. I think it was also necessary to then _not_ hold these buttons for too long. As I said the debug outputs help to figure this out. Good Luck!
[1] https://forum.xda-developers.com/moto-x4/development/rom-lineage-os-15-1-t3802265
[2] https://www.reddit.com/r/LineageOS/comments/9yahhc/i_hardbricked_my_new_phone_looking_for_advice/
[3] https://forum.xda-developers.com/moto-x4/help/moto-x4-hard-brick-t3777529
[4] https://forum.xda-developers.com/moto-x4/help/q-howto-x4-to-los-setup-bricked-t3883645

@macin42, thanks for the info on this. It makes sense, and I will give it a go. I'll follow up with the outcome as soon as I do; planning by the end of the weekend to give it a go.

@macin42, your instructions worked perfectly! Thanks so much for the help on this. As a recap on the issue: the problem for me was that I skipped the "Copy Partitions" step as it was a new phone and the phone hadn't received any "first" OTA updates. This step was necessary and wasn't mentioned in the official LineageOS install instructions on the LineageOS site. This step was mentioned however on the XDA LineageOS install instructions.
To recover from this, I followed the instructions that were given as help above by doing the following:
1. Downloaded the blankflash.zip from link provided above
2. Installed the Motorola Device Manager drivers (already had)
3. Installed adb and fastboot (already had)
4. Plugged in phone to PC via USB
5. Ran the following command while holding down the power up + volume buttons: qboot blank-flash --debug=2
NOTE: The qboot command didn't work for me the first time, but I re-tried a couple of times and it ended up working after the second or third try.
6. Once this completed the phone turned on and made it to the bootloader.
7. Once I made it here I was able to redo the steps that were given on the XDA thread to install LineageOS (post above), which were:
- Download the Copy Partitions zip from link above then:
- fastboot boot twrp.img
- adb sideload copy-partitions-payton.zip
- In TWRP, click "Wipe", "Format Data", then type "yes" as prompted.
- adb sideload lineageos-nightly.zip
- Navigate back to the Reboot menu in TWRP, select reboot, then select recovery, swipe to reboot. I did get the same "No OS installed" warning here but it wasn't an issue.
- This brought me to the LineageOS recovery.
- I chose to install Mind the GApps, so from the LineageOS recovery I selected Apply Update, Apply from ADB, then on computer adb sideload mind-gapps.zip
- Reboot
From here it was business as usual with the typical phone setup. Thanks again to those that helped on this!

Glad it worked out. In case your microphone and or sound does not work (silence in calls, recorder app does not work) please let me know - that's where i am currently stuck with my xt1900-7.