ADB sideload error - Samsung Galaxy A3, A5, A7 (2017) Questions & Answe

Hey everyone!
My Samsung Galaxy A3 (in use since approximately 2017) started randomly turning off and restarting, until I was left with the black screen of death (endless restart attempts at the Samsung start screen until the battery dies) and I unfortunately put off the data transfer to my new phone too long.
In the phone's rescue mode, I already deleted the phone's temporary data with the option 'Wipe cache partition' in an attempt to solve the BSoD so I could easily pull the data but it didn't help. Following different tutorials for data recovery from the recovery mode, I installed an ADB driver on my PC
link: https://gsmusbdriver.com/micromax-a311
and downloaded the program adb.exe from two different sources to transfer data between the phone and PC:
link 1: https://dl.google.com/android/repository/platform-tools_r34.0.1-windows.zip
link 2: www.mediafire.com/file/6b3aw3dq8omefyw/mfastboot-v2.zip/file
I was transferring data from the phone to the PC before, so I had debugging activated in the phone settings.
In the phone's recovery mode, there were the options:
Reboot system now
Reboot to bootloader
Apply update from ADB
Apply update from SD card
Wipe data/factory reset
Wipe cache partition
Mount /system
View recovery logs
Run graphics test
Run locale test
Power off
I chose the option 'Apply update from ADB'.
When I started the adb.exe in the command line and in powershell, the phone got recognized in recovery mode using the command 'devices' and it showed mode: sideload.
But when I tried the commands 'backup [-apk] [-obb] [-shared] [-all] [-system]' or 'pull sdcard', the programs gave me the error messages
'error: connect failed: closed' (platform-tools)
and
'unable to connect for backup' (mfastboot).
Do you know this issue and a way to fix it or to work around it? Did I maybe install the wrong driver or is my data inaccessible for good? For example, there are lots of memo files on the phone which aren't synchronized to any cloud or account that I'd like to backup and transfer to my new phone.
Thank you in advance for any help!

Related

[Q] Stuck at boot, ADB not working

I was looking to do a full wipe from TWRP and wanted to wipe data as well. Knowing that that would erase everything from the internal storage and not having an SD card available to me now I decided to wipe everything and then transfer the new ROM with adb commands.
Before wiping, I wanted to make sure that adb was working first. So I downloaded the Android SDK and booted to TWRP. Went to Advanced--->ADB Sideload and started the command prompt on my PC. From the folder were adb.exe was I typed "adb usb" and got error:device not found.
I don't know why but after 30 minutes trying to fix that I pressed the "Fix permissions" option in TWRP and now my phone is stuck at the boot logo every time I try to turn it on. I also noticed in Device Manager on my PC that every time I connect the phone to the PC that there is a yellow exclamation mark next to the phone which suggests that I don't have the needed drivers. However I tried to install versions 3.10 and the newest 3.12 and the exclamation mark is still there.
So my question is how do I reach the phone with ADB and transfer the flashable ROM zipfile so I can get the phone past the boot logo?
Well I'll answer myself if anybody has the same problem in the future. It was obviously the USB driver's fault and since none of the LG's drivers worked, I used Google's USB drivers and was able to adb sideload the ROM zip and now it's booting into the OS.
So always check your drivers people! In case LG's don't work, then use Google's!

Has CM13.0 bricked my phone?

I installed CM13.0 but gapps kept crashing, so I decided to do a factory reset and reinstall the previous rom (was on CM12).
But now when I turn the phone on it just sits there showing the google logo and the unlocked padlock icon. It doesn't bootloop. I can only unplug the charger and pull the battery to stop it.
I can Vol+- power into the bootloader (which says that it's in fastboot mode and lock status is unlocked) and get into recovery mode (which mysteriously is now cyanogenmod recovery, it was clockworkmod before)
recovery has options:
-reboot system now
-apply update
-factory reset
-reboot recovery
-reboot to bootloader
-mount /system
-wipe system partition
-view recovery logs
-power off
No option to wipe dalvik/cache - i wonder if it's lost root?
I have USB drivers installed and Win10 pings when the phone goes into recovery mode. But the phone doesn't appear in windows file manager so I can't copy a rom or alternative recovery onto it
adb devices (when in recovery) finds the phone, but as unauthorised
Nexus Root Toolkit finds the device but can't proceed, but I obviously can't turn usb debugging on because I can't get into android.
The phone of course has no external SD card.
I've tried to access it through a Linux laptop with no success, though I'm a bit hazy on how you would view a phone in linux file manager.
So if I can't get ADB authorised, and can't get a zip onto the phone through an SD, and can't copy it through windows file manager, what can I do?
At the moment I'd be happy to have any recovery and any rom on it that works!
Any suggestions?
Update: managed to use fastboot without adb via linux using this guide
http://androidforums.com/threads/guide-how-to-flash-a-nexus-factory-image-manually.706533/
I'm now on Jellybean and sticking to it

Soft Bricked HTC one X not detecting adb pushed ROM

I hope all of you would be fine.
I was trying to install a custom ROM in my HTC one X via CWM recovery. I formatted the system partition (ROM) and tried to flash the new ROM. I ended up soft bricking my phone as the ROM file was corrupt. I tried to push another ROM.zip file into the phone memory via adb. My phone shows up in fastboot devices when it's turned on but it's not detected as adb device. When I turn it off then it shows up in the attached adb devices list. I used the adb push command to transfer the ROM file into the phone memory and cmd tells me it's done as it shows the transfer speed and the size of ROM file. Now the issue is that when I try to search for that ROM file in CMW recovery, it's not there in the memory.
It's been three days since I have been trying to make my phone alive but nothing seems to work.
Any help from you guys would really be appreciated
*My phone shows up in abd devices only when it's turned off.
*The adb pushed ROM.zip file is not present in the phone memory.
*All the drivers are correctly installed and my phone is listed as 'My HTC' in device manager.
Hey there, sorry for a late answer, but right now I have some town-wide internet problems, so...
Back to your problem then, if you cant have any result with adb push, try to use another method:
1. Complete steps at this link https://twrp.me/htc/htconexinternational.html to install twrp
2. Reboot to your twrp recovery
3. Choose "Mount" option and mount any partition you need(depending on your layout), after this step, you can access you phone storage with you pc.
4. Now you can wipe everything you want, do not reboot, and go to "install" option.
5. Just copy/paste you ROM, install it, reboot to fastboot, flash boot.img
Done.
Have a nice day.

Loop in MainMenu

Hallo everyone,
I started the update from Saturdayan since this is my phone is the main menu.
If I take the option for reboot then it goes after the reboot back to the main menu.
If i use connect with miassistant the computer registers a phone in the device manager but the assistant does not register the phone.
Wipe data is , now, no option. I have data on the phone that are not backuped.
How can I access this data to copy these to my computer?
Is there an tutorial or an treath that i can use to recover my data?
TWRP is not installed on my phone. Phone is not rooted. Fastboot is accessable.
Also I tried to use the adb connection.
My tests - My results
- used command devices - get my device with the result:
List of devices attached
fmaavg... sideload
Click to expand...
Click to collapse
- used adb pull /system - without result
- used shell ls - error: closed
Has someone a hint for me to solve this problem?
Do i use the adb pull correctly?

Question BOOTLOOP Nightmare!!!

Totally stock and stuck in bootloop. Is there a way I can get the data off without erasing it?
I've tried connecting it to the pc but the pc will not recognize it although in fastboot the usb cable is detected by the phone.
I've downloaded the smart and rescue app and it doesn't recognize that the phone is connected.
Recovery mode no longer offers the wipe cache option.
Is there an app on pc or some special commands or something that will allow me to retrieve my data?
Phone is completely stock BTW
TIA
Heruktiang
See if you can get to go into safe mode... may have try more then once.
Something crashed it proper. Any new apps?
If by safe mode you mean recovery mode yes I can. But it offers no solutions that i am aware of. What should I do once in recovery? there is no longer an option to wipe cache.
i just need to copy the data to my pc so i can factory reset it
Use the physical button commands to get into safe mode on boot up.
Sometimes on my Samsung just rebooting from the recovery menu would automatically trigger it to boot into safe mode when it was boot looping.
It's odd you lost the clear the cache option.
yea recent update last week and im sure there is a new app in there.
In fastboot mod my options are :
start
restart bootloader
recovery mode
power off
factory mode
switch console
barcodesbp tools
qcom
bootloader logs
switch tools mode
in recovery mode the options are:
reboot system now
reboot to bootloader
enter fastboot
apply update from adb
"" "" sd card
wipe data/factory reset
mount/system
view recovery logs
run graphics test
run locale test
power off
there must be some way to get the data off

Categories

Resources