Hi, I'm trying to help a friend unbrick his nexus 7.
The problem is that he is a stock clean user. No root, no custom recovery, all plain stock
This also means that he never enabled usb debugging in dev options
Now im trying to reflash factory image but everytime it gets stuck at the same point of unlocking bootloader (wiping user data)
Will it be possible to reflash factory if adb debug wasn't enabled in the device?
(adb device returns empty, but fastboot works)
If the answer is no, is there any way to edit the build.prop and/or where the adb gets flagged as enabled?
(The only solution i found requires going through adb shell, which in my case isn't working)
thank you for any suggestion
Related
Short version - is it possible to copy files from my phone to my PC using fastboot (or perhaps adb)? The cyanogenmod WIKI for fastboot, among others, imply that you can (under the section Examples -> Manual Nandroid Restore it says "Make a Nandroid backup, and copy the folder off your SD card to your desktop."). Sorry I'm not allowed to post the link due to being a new user, but this is what it says:
"Make a Nandroid backup, and copy the folder off your SD card to your desktop.
cd ~/Desktop/path/to/backup/
fastboot flash userdata data.img
fastboot flash system system.img
fastboot flash boot boot.img
fastboot reboot"
If it is possible, is "flash" the correct command to be using? The description of the flash command when you run "fastroot help" implies it writes data to the phone, not from the phone to the PC... Unfortunately almost everything I search for around the flash command is examples showing how to load ROMs etc, I can't seem to find anything else that points to it being used to backup data...
[UPDATE] - From what I understand you can't copy files off the phone using fastboot commands, but can using adb - so a few questions:
- Does anyone know why adb wouldn't see my device (when I run "adb devices") but fastboot does (note that I'm on the fastboot screen)?
- Does adb require debugging mode to be on?
[UPDATE-2] - Still can't get adb working, suspect it's because USB debugging isn't enabled (though not sure how I can check?). I did try using fastboot to erase the /cache partition in case the lockout data was stored in there - but this didn't work unfortunately. Looking likely I'll just have to wipe it with fastboot oem unlock
Long version / background info:
Using a Samsung Nexus S with Android 4.1
The other night someone down the pub decided to try to unlock my phone, and apparently got the pattern wrong so many times it's now requiring me to enter my Google account details.
Fine, I enter the username / pass, only it says they're wrong - I know they're correct because I've just confirmed they are by logging into Gmail. It says they're incorrect so quickly that I suspect it's not even connecting to the web to check. The icons at the top imply there is signal, but it looks as though 3G / data is off, and there's no WiFi icon even though I'm sat next to my wireless router. I can't find any way to re-enable WiFi / 3G without first unlocking the phone - which requires a net connection. So I got into Fastboot Mode and selected Recovery and the device looks as though it's doing something (deleting all user data I assumed), but when it starts up it's exactly the same - which implies the user data hasn't been erased.
Then I installed fastboot, and the drivers for the Nexus S.
When I run "fastboot devices" I can see the phone listed, however bizarrely "adb devices" lists nothing.
"fastboot oem unlock" seems to work (the phone prompts me to confirm I want to give root access & delete all user data). I haven't done this yet as I want to see if I can save my data somehow using adb or fastboot commands.
For adb to work, your phone must be booted and USB debugging enabled. In your current situation, as far as I know, a factory reset is the only option.
The phone is either in ADB mode or in Fastboot mode. It can never be in both ADB and Fastboot at the same time. ADB requires the phone is up and running, Fastboot requires the phone is in bootloader mode. ADB requires debugging turned on.
If you unlock your bootloader, you can boot the phone using fastboot and your own recovery image using "fastboot boot myrecovery.img" (notice, no flash keyword here). Booting your device with this recovery image, you can do whatever you like and the image permits, e.g. running ADB and copying files. You'll need this recovery image, though.
Thanks, I did try fastboot with a recovery image, but it currently doesn't work because I need to unlock the bootloader (which will wipe all data anyway). Sounds like I will need to just wipe it
kuisma said:
The phone is either in ADB mode or in Fastboot mode. It can never be in both ADB and Fastboot at the same time. ADB requires the phone is up and running, Fastboot requires the phone is in bootloader mode. ADB requires debugging turned on.
If you unlock your bootloader, you can boot the phone using fastboot and your own recovery image using "fastboot boot myrecovery.img" (notice, no flash keyword here). Booting your device with this recovery image, you can do whatever you like and the image permits, e.g. running ADB and copying files. You'll need this recovery image, though.
Click to expand...
Click to collapse
Facing same issue.
Is there anyway so I could copy userdata.img to my pc and then delete gesture.key file (I am running Lollipop) with NO USB DEBUGGING ON in Fastboot mode.
I have gone through "unpacking and packing .img files"http://forum.xda-developers.com/galaxy-s2/general/ref-unpacking-repacking-stock-rom-img-t1081239
But it is out of my knowledge range can anyone get through it and explain me the same.
Hi! I am in the same situation... ADB not working, only fastboot... Any way to save my data? Do I need to unlock bootloader to install a stock recovery? Thank you!
Hi - I am in exactly same situation as well. I am using Oneplus 8t. Any help is greatly appreciated. thanks
Hey guys , anyone have a way to enable usb debugging via fastboot ?
Flashing something may do it ?
Leonardo_f said:
Hey guys , anyone have a way to enable usb debugging via fastboot ?
Flashing something may do it ?
Click to expand...
Click to collapse
i also need to find out because i cant even get into my phone due to bootloop issues...i bought my HTC MyTouch 4G from someone & been trying to fix my bootloop, every forum says to make sure "usb debugging" is enabled but i have no idea if it is or if it isnt
also when i use "adb devices" in cmd nothing shows up under list of devices...i just hope there is a command in adb or fastboot to enable/disable usb debugging
GarciaGotti said:
i also need to find out because i cant even get into my phone due to bootloop issues...i bought my HTC MyTouch 4G from someone & been trying to fix my bootloop, every forum says to make sure "usb debugging" is enabled but i have no idea if it is or if it isnt
also when i use "adb devices" in cmd nothing shows up under list of devices...i just hope there is a command in adb or fastboot to enable/disable usb debugging
Click to expand...
Click to collapse
I don't know whether you can enable USB debugging through fastboot ... i'll leave that to the experts.
However you can see your devices when connected to a PC in fastboot mode!
just run ...
fastboot devices
khajoor said:
However you can see your devices when connected to a PC in fastboot mode!
just run ...
fastboot devices
Click to expand...
Click to collapse
yeah i got that part, but when i try to flash or write anything to the device using fastboot i get nothing but errors so im guessing usb debugging must not be enabled
I'm sorry to say, you cannot enable USB Debugging through fastboot.
Hit the thanks button if i helped answer your question
Those errors have nothing to do with USB debugging. Your bootloader might not be unlocked so the flashing commands aren't working, or you're using wrong commands. USB debugging is at the ROM level and is for enabling adb while booted into the ROM. At the bootloader level, only fastboot commands work if the bootloader is unlocked. adb does not work. You need a custom recovery like CWM/TWRP for adb to work, and this recovery has to be flashed via 'fastboot flash recovery <recovery name>.img' on an unlocked bootloader.
Sent from my Nexus 7 using xda premium
Hello,
I'm also interested on this topic. My screen is broken, but the phone is working. I can boot and I feel the phone working and recognising my finger to unlock. However, because I'm stupid and I didn't have the "USB debugging ON" I can't access my files via ADB or any recovery software.
However, I can boot on fastboot and I see my device on "fastboot devides". Can I do something to access my files from there? I don't know... maybe unlock bootloader and flash any kind of TRWP with full adb or something like that.
THanks ¡
lotuxete said:
Hello,
I'm also interested on this topic. My screen is broken, but the phone is working. I can boot and I feel the phone working and recognising my finger to unlock. However, because I'm stupid and I didn't have the "USB debugging ON" I can't access my files via ADB or any recovery software.
However, I can boot on fastboot and I see my device on "fastboot devides". Can I do something to access my files from there? I don't know... maybe unlock bootloader and flash any kind of TRWP with full adb or something like that.
THanks ¡
Click to expand...
Click to collapse
As its name implies, Fastboot operates on device's bootloader and not on device's Android files as ADB does.
BTW: You always can access the user-data stored in Android's file system if USB-MTP mode got enabled on Android device.
jwoegerbauer said:
As its name implies, Fastboot operates on device's bootloader and not on device's Android files as ADB does.
BTW: You always can access the user-data stored in Android's file system if USB-MTP mode got enabled on Android device.
Click to expand...
Click to collapse
True, I can see my Xiaomi on "Windows Explorer", but it's an empty folder because I can't select MTP mode instead of "only charge" mode that it's launched by default.
What if I flash a TWRP recovery (I'll need to open bootloader first) and then from TRWP I try adb?
It must be a solution... if profesional people can do it so we do.
Thanks.
Hello,
Recently I flashed a CWM file on my android 'Lava Iris X1 Grand'. Now my phone is stuck in a bootloop. For some reason i cant enter recovery mode even before my phone was stuck in a bootloop. I am not sure whether my phone has USB debugging enabled or not. I have even rooted my android with KingRoot. I have downloaded your Minimal Adb and Fastboot but it cant find my device.
Overall problem:
1) Phone Stuck in Bootloop
2)USB debugging enabled ? Not sure
3) Can't enter recovery mode
4) ADB wont find my device
Note : When I used Minimal Adb and Fastboot, when i type Fastboot devices some numbers appear but when I used the command 'adb devices' my device is not shown. I have a backup at my phone through the Flashify app but since recovery mode cant show I cant recover it.
Please help me out here. I don't know what else to do.
Thank You in advance
Fixed
Sorry posted in wrong section
My phone is fixed now using SP Flash Tool
OEM unlocking and USB Debugging enabled.
ADB never finds the phone in my windows 10 install no matter what drivers I force it to use. - Tried USB 2 and 3.
Fastboot does find it if I manually start it in fastboot mode, but it can't do anything to it
Fails to write when doing oem unlock
Just sits there if I tell it to write the recovery image.
Phone functions fine, I just want root and a 3rd party rom to be rid of any built in spyware.
Any ideas? any way to root it without flashing then I can just have the twrp app flash it?
Nevermind, found a way around it. This dialpad command made it work
Personmans said:
Hope this will help someone with trouble getting ADB/Fastboot to work. I assume you have a similar environment to me: Windows 10, with working ADB drivers on another device (LG G4 in my case)
Set up LeMax2 in developer mode and enable USB debugging as usual.
Plug in usb and dial *#*#76937#*#* check the box that says "Enable AT Port"
The device should immediately give you the approval message for USB debugging.
Note: This will not stick after a reboot.
Once I had this working, I did an adb reboot recovery, but fastboot still did not work. With the device connected and at the stock recovery screen, I had to open device manager, delete the LeMax device, and allow it to detect again. Finally it appeared in fastboot devices and I was able to flash recovery.
Click to expand...
Click to collapse
I have this phone and now it wont boot. Im thinking there is no OS to boot. It tries and says DM varity disabled at top of screen then says software cant be checked for corruption /bootloader unlocked. When in bootloader there is no recovery to boot into as well when plugged into desktop . ADB devices command is not seeing it. So my question is where do I start to install recovery and make PC (adb/fastboot) recognize device. If I could get adb to identify device shouldn't I be able to fastboot boot (twrp-disc.img) then flash twrp.zip then reboot bootloader and flash factory ROM and kernel or custom? Hate if I sound like a noob im learning all I can. Any help is greatly appreciated!
ADB, Fastboot & Recovery are 3 completely things independent from each other:
ADB program deals with Android OS ( folders / files / settings )
Fastboot program deals with device's bootloader
Recovery is a special bootable partition on device, which contains a recovery application installed in it
If
Code:
adb devices
doesn't show you a connected "device" then either USB debugging isnt enabled or Android OS isn't accessable at all or Android's USB service isn't set to "adb"
If
Code:
fastboot devices
doesn't show you device's mode as "fastboot" then device's bootloader isn't accessable at all.
Back to your "issue", well, it's NORMAL, starting from Android Marshmallow on ALL devices with an unlocked bootloader & disabled "dm-verity" will boot with those warning, so nothing to worry about, and , at the moment it's not possibile to remove those warnings.
When Fastboot is working, then you should be able to boot device into a Custom Recovery, of course only if that is at 100% suitable to the device.