Software version : MA 1.7.12 N8
Total Disk Space : 8G
Adb in normal startups and fastboot in bootloader mode ( after pressing power + volume down ) are not working
Could anyone tell me how to solve this Thanks in advance
Have you enabled USB Debugging?
I don't think there's an option to enable USB Debugging in the original system before getting into fastboot and rooting the device.
Are you able to boot into the ROM? You just can't use adb & fastboot?
Yes I can boot into the ROM. It's the original ROM. And I can't use adb or fastboot.
You have a start button? Try start + power to boot into fastboot mode.
Thanks for your reply&time.
I believe that power + volume down is the way to boot into fastboot now, and after booting into fastboot and connecting the USB line, (fastboot devices) command in the computer (tried Mac OS X 10.8, Windows XP virtual machine and Windows 7) shows no device connected. When using start+power, my device boots normally into the original rom.
All right. I think I just got rid of the fastboot issue. There's something missing with the driver. I'll post my solution after I verify it and flash DPRom successfully.
The problem is acutually pretty silly. A proper adb driver is required for fastboot.
I installed tineprogramming's adb driver to fix it.
(http://forum.xda-developers.com/showthread.php?t=1454685)
Hello everyone,
I'm trying to install Full Recovery on my phone using Fastboot mode. Windows recognizes the phone (Vodaphone Smart II) with normal boot mode, but when I fastboot the phone, windows sees it as Android 1.0 in Devices Manager, and fail to install the driver. And whenever I try to install/update phone's driver, windows just doesn't load it. (PS: I successfully installed that same driver while in normal boot mode).
Also, can't find any driver via windows update.
Thanks in advance for your help.
All I know:
- On normal boot its stuck in HTC logo
- When in fastboot and trying to go into recovery it restarts my fastboot menu
- Adb, fastboot and ruu don't detect it
- Shows in device manager as Android USB Device
- Software status: Modified and Relocked
What I tried:
- Connecting to the pc and trying to do anything with adb
- Placing recovery image and rom files on sdcard and switching between HBOOT and Fastboot as its scanns for zip files but after it loads the file and checks it, device gets rebooted and once again stuck on logo
Need help, I'm looking for solution for last 2 days
up
ROM stock
Recovery TWRP
Hi all,
I would recover data from an s6 with broken lcd.
First time i connected it to pc via usb, it was recognized in recovery mode by adb.
I tried to access data with adb shell but no contents found in folder "data". I tought "no root permission?!"
So I installed TWRP recovery via Odin. Now, when i connect it to pc it's not recognized anymore by adb "no devices attached". I just can view "Samsung Mobile USB Composite Device" under device manager in windows and an error about MTP driver installation.
How I can determine in which boot mode is the telephone?
Could you suggest me a way to try to recover data, if present?
Thanks in advance.
additional info:
when i connect the phone to the pc trough usb, it takes about 15s being recognized by windows. next windows try to install MTP driver and it fails.
In Odin it appears "added" but if I try to flash a recovery it stucks on "setup connection"
I have access to fastboot and EDL mode. Does this mean that I can also access the mode that will show the phone after the adb devices command?
If device gets booted into FASTBOOT or EDL mode then it can't additionally get accessed via ADB: this can only get achieved when device got booted into RECOVERY mode.
To clarify:
ADB ( short for Android Debug Bridge ) deals - as its name implies - with a device's Android OS.
FASTBOOT deals - as its name implies - with device's bootloader, if that isn't bricked.
EDL ( short for Emergency Download Mode ) - specific to devices with a Qualcomm Snapdragon chipset - deals with the device itself, is used if bootloader is bricked.
Thank you for your quick help. Is it possible to access adb during bootloop?
I entered something called recovery mode, but the computer doesn't recognize that any device has been connected - adb devices doesn't see anything either.
On one of the pages I read this information:
Spoiler
Ed Reynolds says:
December 2, 2018 at 4:31 am
Unfortunately, there really is no “recovery” per set, yet. There is a mode where one can factory reset the phone which can be reached using the hardware buttons. However, from there, you cannot do anything other than reboot to a simpler form of phone. There are no options to go into bootloader or Fastboot mode. ADB won’t get you there. Sometimes, using ADB, you can boot into a simple android recovery with no command! There you remain until hard booting back it back into full functionality. Developer is apparently working on it
Reply
Deepak Gupta says:
December 2, 2018 at 4:38 am
Hi Ed Reynolds,
Thanks for sharing your knowledge. We appreciate your efforts. Yes, stock recovery doesn’t offer many options. One has to install a custom recovery like TWRP to get over this problem and to maximize productivity.
Reply
Ed Reynolds says:
December 8, 2018 at 7:48 pm
That is correct. but, in order to install a custom recovery, one must be able to get into bootloader, in some way. Either through physical buttons or through the ADB tool. forget about using the physical buttons – they get you to the recovery that you mention, but cannot get you into Fastboot (bootloader) mode. If you use the ADB tools while in this particular recovery mode, and try to reboot into bootloader mode from there, it boots back into the system. So, using that route, you cannot ever get to a place where you can install TWRP or anything else, for that matter – including applying an unlocking code if one were available. Next, if you try to get into recovery mode using the ADB tools (not the physical buttons, you do arrive at a more “conventional” recovery — with the picture of the little Android symbol, etc. However, there are no commands to use to get into Fastboot or bootloader mode. I have had this problem before and sometimes, using the physical buttons, you can reveal commands at this stage. However, even here, no combination of physical buttons reveals any commands. Then, as a last ditch effort, you use the ADB tools to boot into bootloader mode, you return to the system! The result is, again, you cannot install any sort of custom recovery because there is no internal or external way to flash it. If you have overcome this problem, please share! It is very frustrating! Thanks. Ed
Does this mean that I will need to flash custom recovery to gain access via adb during bootloop?
Android's Recovery is nothing else than a minimalistic working Android OS, comparable to Windows Recovery Environment ( WinRE ), so it's accessible via ADB.
A Custom Recovery ( like TWRP ) isn't needed at all, because such a only is an UI version operable by touches.
So if Windows don't see device when is in recovery mode (but recognize correctly when is in fastboot mode), there is a problem with drivers?
I want to access to adb pull for backup. Device is rooted with unlocked bootloader and allowed USB debugging and no PIN password, but bootlooped after trying to restart after uninstalling YouTube app
OMG
when in Recovery mode then you've to connect device via USB-cable with computer and you can launch adb pull command on computer.
When I in recevery mode, computer not recognize it - adb commands not working, device manager don't see any device. When I on fastboot or EDL, computer recognize phone, commands working and device manager shows device on list
Then obviously USB Debugging didn't get enabled in Android's Developer Options.
Robert997 said:
When I in recevery mode, computer not recognize it - adb commands not working, device manager don't see any device. When I on fastboot or EDL, computer recognize phone, commands working and device manager shows device on list
Click to expand...
Click to collapse
As the other user said, USB Debugging is not enabled or proper drivers are not installed. The drivers for fastboot and adb are different. Search for correct drivers, disable driver signing in Windows and install the drivers.