Hi, XDA,
I own a Samsung tablet (GT-n5110) which is in bootloop (the same that is being called "soft brick" - it loops on Samsung frame and doesn't leave it).
I don't have a data backup (yes, I'm an idiot). It enters Recovery Mode (HOME+VOLUME UP+POWER), but before wiping it to factory configuration I am desperatelly trying to back the data up.
The device isn't rooted. I read in many foruns that it could be possible to back it up through ADB (in Linux, through $ sudo adb backup -all). I use Linux (ubuntu), but the device isn't recognized by ADB [$ sudo adb devices]. I have alredy updated UDEV rules with the correct idVendor and idProduct and I have alredy restarted ADB server.
I have no problem on connecting to Windows in case it is needed in any way. But untill now I haven't found a way to do it neither in Linux nor in Windows.
When I connect the device to the computer, it is recognized and charges, but it isn't possible to access the files (which alredy happened before the bootloop and surely indicated that something was wrong). In Linux, it says the computer cannot access the files because of some MTP failure (I have alredy installed and updated mtp-tools). In Windows, it simply says it cannot access the device.
Is there a way to do it? Should I keep looking?
Or is it simply impossible that a device on bootloop could be recognized by the computer to back the data up?
Thanks A LOT, I really need this help!
Hello and thank you for using XDA Assist,
please create an account and ask your question in this section. The experts there should know the best about your device.
Kind regards and good luck
Trafalgar Square
XDA Assist
Related
Hi.
I have done something stupid
Some website claimed that rom manager from clockworkmod would not work unless twrp was installed. (I guess they meant "for getting the CWM Recovery Boot Menu to work").
I had already rooted my device (Denver Tablet TAQ-80053 ARMv7 with Android 4.1.1) but I thought why not flash to TWRP with the file: "CWM-based-Recovery-v6.0.3.3-signed.zip" ?? BAD idea
Now "Recovery Mode" is only the "TeamWin Logo" then BLACK SCREEN and nothingness ??
Everything else is somewhat normal:
1) I can boot normally into the start screen of Android 4.1.1 and run applets etc.
2) I can connect to Windows 7 (x64) and get file access to everything.
But: Any flashing tool for windows cannot "see" my device, and I very much doubt that it could be a driver problem since I get full access to drives and files on the tablet (USB-connected to Windows 7 x64).
Do you have any thoughts about that ? Because to me it seems logical that a working windows-driver would also work with ADB or ... ?
I also tried the ADB installation with SDK etc. Everything installs fluently with no errors but when I do the "adb devices" command no devices are listed at all ?? The command "ADB Shell" returns an error.
Since I know about the settings needed on the tablet I have: set USB Debug Mode to ON and everytime I plug it in I select "Mass Storage Mode" to get file access from Windows; and it works fine.
As stated above, everything works except "boot into recovery mode" and ADB being able to "see" my device. Not even CWM Rom Manager can boot into recovery mode ??
I want to be able to flash a new OS but recovery mode seems to be the only way apart from the USB to Windows. I cannott accept the notion that the device is "almost bricked" just from installing the wrong
recovery image and now I cannot go back .....
I have spent too much time already and I have discovered that I am not the only one with this problem but I cannot find any solution (that actually works) anywhere. So writing to you guys must be my last
hope. The alternative is getting an axe and chop it to pieces just to be shure that it's completely dead and my $150 lost forever; gone out the window :\
Can anyone please advise me what to do ??
/Pete
PS: OMG captcha is unreadable 30 times or more . . . and then the session ran out. Great
Hi there,
I'm sorry but I can't find anything related to your question/device.
Please post that in the forum bellow for more answers from the experts but first you must register an account on XDA forum:
> Android Development and Hacking > Android Q&A, Help & Troubleshooting
Good luck
Hello xda-members,
I've been searching for 4 hours now and every time I try to use ADB along with my device I get the "unauthorized" message and can't use it.
I've been searching for answers all across the internet and tried nearly everything I could find, e.g.:
1. In windows cmd:
Code:
adb kill-server
Code:
abd start-server
2. Unplug phone
3. Reinstall drivers
4. Reboot phone / PC
5. Disable and Enable USB-Debugging-Mode
I read in several threads on other sites, that the adb key is the problem (there's no "authorization"-pop-up appearing on my phone, when connecting it via usb, furthermore I can't revoke debug permissions in developer settings), so I tried also:
1. delete .android. folder on my PC (C://User/me/.android.)
2. Copy the adb_key file to my phone (/data/misc/adb)
None of that worked. None.
I'm really desperate since I need ADB for several important reasons (to me important). I don't know when this problem occured first. When I bought the phone ADB worked fine. I don't know what to do anymore.
Technical information:
- Windows 10 PC
- Latest LG drivers, latest adb version
Phone:
- LG G4 H815 V20C (Marshmallow)
- Rooted, TWRP installed, SuperSU working without problems
So please, if anybody out there has had the same problems help me!!!
Follow_and_Feel said:
Hello xda-members,
I've been searching for 4 hours now and every time I try to use ADB along with my device I get the "unauthorized" message and can't use it.
I've been searching for answers all across the internet and tried nearly everything I could find, e.g.:
1. In windows cmd:
Code:
adb kill-server
Code:
abd start-server
2. Unplug phone
3. Reinstall drivers
4. Reboot phone / PC
5. Disable and Enable USB-Debugging-Mode
I read in several threads on other sites, that the adb key is the problem (there's no "authorization"-pop-up appearing on my phone, when connecting it via usb, furthermore I can't revoke debug permissions in developer settings), so I tried also:
1. delete .android. folder on my PC (C://User/me/.android.)
2. Copy the adb_key file to my phone (/data/misc/adb)
None of that worked. None.
I'm really desperate since I need ADB for several important reasons (to me important). I don't know when this problem occured first. When I bought the phone ADB worked fine. I don't know what to do anymore.
Technical information:
- Windows 10 PC
- Latest LG drivers, latest adb version
Phone:
- LG G4 H815 V20C (Marshmallow)
- Rooted, TWRP installed, SuperSU working without problems
So please, if anybody out there has had the same problems help me!!!
Click to expand...
Click to collapse
Greetings,
Please read the sticky threads for this forum. XDA Assist is for helping NEW members find their way, not a help desk for Senior members who should know where to ask for help.
Thread closed.
Alright, I've tried installing the drivers from Verizion and also using the drivers from the Android SDK and either way I have the same problem. ADB devices shows my phone, however whenever I try to push, pull, or reboot (the only commands I have any use for atm) the command prompt hangs like it's trying to access the device but no matter how long I leave it the device will not reboot, nor will any files appear in the correct folders on either the device or my computer.
I'm trying to root this thing and this is a pretty major roadblock.
Note:
USB Debugging enabled
ADB drivers installed
Phone shows up on "adb devices"
Also, I don't know if this is normal but, In order to get the notification that "USB debugging connecting" I have to use the internet connection option on the phone. When using MTP, Charge only and PTP that message doesn't appear and I don't see an ADB device show up in device man.
Thanks!
--------------------------------------------------------------------------
*EDIT*
I've found the proper forum here,
http://forum.xda-developers.com/android/help
Thanks again. Feel free to lock this thread.
Hi,
thanks.
Thread closed.
Kind regards
Trafalgar Square
XDA Assist
I'm having some trouble mounting a Kindle Fire in Fastboot mode on my system which is running Ubuntu 14.04.
I am new to any kind of Android development and have been following the excellent guides here by @kinfauns. Specifically I have the 5-scecond boot loop problem related to the power draw issue. The solution I'm pursuing is to swap the stock bootloader for FireFireFire. The guide says to do it with fastboot, since the conventional flash recovery method could be interrupted by the shutdown cycle.
So now, just when I think I have a solution to my real problem, I get out the fastboot cable, connect the kindle to my PC, and I get an error in Nautilus: Unable to open MTP device '[usb:001,006]'. Attempting mtpfs at the terminal returns:
Unable to open ~/.mtpz-data for reading, MTPZ disabled.Listing raw device(s)
Device 0 (VID=1949 and PID=0007) is a Amazon Kindle Fire (ID1).
Found 1 device(s):
Amazon: Kindle Fire (ID1) (1949:0007) @ bus 1, dev 6
Attempting to connect device
LIBMTP PANIC: Unable to find interface & endpoints of device
Unable to open raw device 0
I tried following a tutorial on Ubuntu forums for getting MTP to work. It involves using lsusb command to get the device id, making entries in /etc/udeb/rules.d and /lib/udev/rules.d, supposedly to allow MTP to access the device with proper credentials. However nothing worked.
Now, on the other hand, when the device is NOT in Fastboot mode, it mounts just fine, both in Nautilus and for purposes of checking with the adb devices command.
Seems to me that what I want is for it to mount in file transfer mode instead of MTP mode when in fastboot. The fix for this exact issue in Windows (as reported on other sites) is to change the driver in Windows Device Manager.
Can anybody help with this problem?
Thanks
Hello and thank you for using XDA Assist,
please create an account and ask your question here:
Kindle Fire Q&A, Help & Troubleshooting
Kind regards
Trafalgar Square
XDA Assist
Hi, I've got an old S5 with a broken screen. There's no image going on and there's no indication that the touchscreen is working.
I'm not looking to recover data, I'm looking to play around with it by controlling it from my PC. Last I remember, the phone is running a Cyanogenmod OS (I don't think LineageOS was around at that time) with either TWRP or CWM recovery, but I'd bet on TWRP.
Now: the device reaches the OS properly, I can tell because if I try to turn the ringing sound up it gives me an audio feedback.
If I connect it to a PC from the OS:
- the phone shows up in Windows Explorer as "SM-G900F"
- Device Manager shows me a "SAMSUNG Mobile USB Composite Device" under Universal Serial Bus controllers
However I cannot access any files (Windows Explorer shows the device as empty), and if I attempt to 'adb devices' in the console it shows me an empty devices list.
Now, I suspect that USB debugging might be off. So I also tried connecting it to a PC from recovery and the exact same thing as above can be observed, PLUS:
- Device manager also shows me a "SAMSUNG Android Phone" list which can be expanded to show me one entry called "SAMSUNG Android ADB Interface"
However it's the same as before, no files available and 'adb devices' shows an empty list.
Now I heard that I can theoretically enable USB debugging through ADB, by writing to a config file. That would allow me to enable USB debugging and try something like Vysor in order to control the phone from my PC.
However that's a moot point until I can figure out why the ADB service on my PC isn't seeing the device. Any help would be greatly appreciated, and if you need more info I can provide it.
Extra info:
- I installed Samsung USB drivers at some point while trying to make it work
- Windows Explorer shows a phone icon for this device, and if I recall correctly that's what happens when it's connected through MTP (Mass Storage should show it like a memory card)
_sepiroth said:
Hi, I've got an old S5 with a broken screen..........
Click to expand...
Click to collapse
I've never experienced this situation myself but, I've seen that the following thread has worked for many individuals.
https://forum.xda-developers.com/showthread.php?t=2786395
Good Luck!
~~~~~~~~~~~~~~~
Unless asked to do so, PLEASE don't PM me regarding support. Sent using The ClaRetoX Forum App on my Apple Macintosh.
Ibuprophen said:
I've never experienced this situation myself but, I've seen that the following thread has worked for many individuals.
https://forum.xda-developers.com/showthread.php?t=2786395
Good Luck!
~~~~~~~~~~~~~~~
Unless asked to do so, PLEASE don't PM me regarding support. Sent using The ClaRetoX Forum App on my Apple Macintosh.
Click to expand...
Click to collapse
Thanks a bunch, that pointed me in the right direction with my research! I solved my issue, I can now control my phone from my PC.
By doing this I ran into a couple of problems, I'm going to describe them and their solutions:
Problem 1: couldn't ADB into the device when in Recovery Mode. That is because after a long head scratching session I came to the conclusion that I didn't have TWRP Recovery installed (I had Philz Touch CWM Recovery and LineageOS 14.1 instead).
Solution 1: ADB mode is enabled in TWRP by default. So I flashed the latest TWRP through Odin, ADB instantly started working afterwards in Recovery Mode.
Problem 2: USB Debugging was disabled inside the OS.
Solution 2: from the thread that Ibuprophen posted, you can enable USB debugging in your OS by opening an ADB shell into your device and modify the build.prop like so
Code:
Adb shell
echo "persist.service.adb.enable=1" >>/system/build.prop
echo "persist.service.debuggable=1" >>/system/build.prop
echo "persist.sys.usb.config=mass_storage,adb" >>/system/build.prop
reboot
Problem 3: /system was empty so there was no build.prop. If I attempted to create a build.prop file it wouldn't be saved after a device reboot, so USB debugging still didn't work.
Solution 3: it seems like TWRP doesn't mount /system by default, only /data. You can mount it manually through ADB like this:
Code:
mount -o rw /dev/block/bootdevice/by-name/system /system
I found this out from this stackexchange question: https://android.stackexchange.com/q...data-partitions-in-recovery-mode-in-adb-shell
Problem 4: When an app tries to use USB Debugging you need to allow it to do so from the phone. Since the screen was broken, I couldn't do this.
Solution 4: You'll need to push a public key to your device with ADB. Boot into Recovery Mode and make sure your device is recognized by your PC and type
Code:
adb push <path to adbkey.pub on your PC> /data/misc/adb/adb_keys
This solution is from: https://stackoverflow.com/questions...b-rsa-key-with-broken-touch-screen-on-android
This will make sure that you won't need to confirm debugging permissions for apps coming from your machine.
So for anyone who has a broken phone screen (my screen is dead and touchscreen/touch buttons are kaput too) and wishes to control their phone from their PC but USB debugging is disabled:
1. Boot device in TWRP Recovery (flash it if you don't have it)
2. ADB into the device
3. Make sure /system is mounted (if it's empty it means it's not mounted), else mount it manually like in Solution 3
4. Configure build.prop to have USB Debugging enabled like in Solution 2
5. Push your public key to the device like in Solution 4
6. Restart the phone (into its OS)
7. Download the Chrome extension called Vysor and launch it
8. Connect your phone through a USB cable
9. The device should appear in Vysor, connect to it and have fun controlling it
Note that if you just want to backup your files, steps 1 + 2 are sufficient. After making sure ADB works you can just 'adb pull' all your files which should be located in /sdcard. Google it, it's easy to find.
The same goes for backups, you can do them directly through ADB.
Again, thanks Ibuprophen!
Vysor does not work on all graphic cards. a good free alternative is scrcpy
btw instead of flashing twrp, you can flash a modified system partition with proper entries in build.prop (for those with no custom recovery available)
aIecxs said:
Vysor does not work on all graphic cards. a good free alternative is scrcpy
btw instead of flashing twrp, you can flash a modified system partition with proper entries in build.prop (for those with no custom recovery available)
Click to expand...
Click to collapse
Very well pointed out, thanks for this.