Hi guys, a got a big problem. Today i've bought an used S5. I always root my phones an install costum roms via twrp, so I wanted to do the same for the S5.
I don`t want that my knox increased so i tried the method with flashing the kernel. Normally nothing new. So I entered the download mode an start. Now I cant start the phone it always start in download mode with the error message " could not do normal boot " . As I wrote the phone is bought today and I forgot to enable usb debugging. What could I do know? (At the moment I downlaod a custom rom, but the download is really slow, and try to throw it by adb sideload on the galaxy. Dont know if it words, but didn't hinkt it will work.)
Has anybody a solution for my issue?
Thanks in advanse
Sagin
AMAIK, download mode works regardless of setting for USB debugging. The only problem is, that in some cases the driver gets installed only when USB debugging is enabled.
tetakpatalked from Nexus 7 flo
I agree with @tetakpatak. Try flashing stock ROM through Odin (even with USB Debugging set to off) and report back if it works I too rooted my S5 the same day I got it
Related
Hey,
i've got a huge problem with my Nexus 7 32 GB 3G. I've had root and i made an update many times without any problem, but once i was making some update of 4.2.2 the device didn't want to turn on and it freezed on Google logo. I tried to do plenty of ways to repair it; unroot, factory reset, wipe... Then i tried to do a flash via Nexus 7 Toolkit, but... there is the problem! How can i do the flash without enabled USB debugging? Is there any way to evade it? Or can I enable USB debugging from my PC for example? HOW??? PLEASE!
Is there anyone who can help me with solving this problem?
Any ideas, recommendations..?
Thank you for all of your responds.:good:
flash a factory image using fastboot...
USB debugging doesn't have anything to do with fast boot mode. Fast boot is the proper way to flash the images.
USB debugging only matters within the booted OS.
You should spend some time learning the right way to do things instead of relying on toolkits.
Sent from my Galaxy Nexus
BerryRide said:
Hey,
i've got a huge problem with my Nexus 7 32 GB 3G. I've had root and i made an update many times without any problem, but once i was making some update of 4.2.2 the device didn't want to turn on and it freezed on Google logo. I tried to do plenty of ways to repair it; unroot, factory reset, wipe... Then i tried to do a flash via Nexus 7 Toolkit, but... there is the problem! How can i do the flash without enabled USB debugging? Is there any way to evade it? Or can I enable USB debugging from my PC for example? HOW??? PLEASE!
Is there anyone who can help me with solving this problem?
Any ideas, recommendations..?
Thank you for all of your responds.:good:
Click to expand...
Click to collapse
Hi, BerryRide...
You don't need USB Debugging enabled (as far I'm aware, it's not possible anyway, in FASTBOOT/BOOTLOADER mode)...
Download the factory stock image for your device, from here...
https://developers.google.com/android/nexus/images.
Shutdown your tablet... and reboot into FASTBOOT/BOOTLOADER mode (Vol Down BUTTON + PowerOn BUTTON)...
Hook your tablet up to your computer, via a USB cable (preferably the USB cable that originally shipped with your tablet)...
And run...
Code:
fastboot devices
This should return a SERIAL NUMBER, indicating you have a FASTBOOT connection, and you can then run whatever FASTBOOT commands you like... including what is in the FLASH-ALL script in the FACTORY STOCK image for your specific device.
Rgrds,
Ged.
Bumping this thread because it just really helped me!!! Thanks @GedBlake!!!!
For the longest time I could never get fastboot or flash-all to work without first enabling USB debugging and much swearing and dealing with permissions. Wound up that my device wasn't getting recognized by Windows at the bootloader. It finally worked after a manual update Device Manager -> Update Drivers using the SDK Manager directory (I subsequently read about in this thread: http://forum.xda-developers.com/showthread.php?t=1583801).
Updating my three Nexii 7 to MRA58V was a breeze this time. Wow- thanks again for the direction.
I recently bought a refurbished 2012 Nexus 7 on 4.2. The only things that I have done on the phone are entering my Google account details and downloading a single app (papyrus). I then clicked to install the automatically downloaded software update (it downloaded 4.3), and after restarting the tablet was stuck on the Nexus X boot animation forever. Factory reset/cache wipes do not help.
I found drivers for the phone to be recognized while showing the X, and I found drivers for the phone to be recognized after selecting the a "apply update from ADB" option from stock recovery. However Windows does not recognize the phone at all in recovery mode before selecting that option. Nothing changes in the device manager when plugged/unplugged. Windows doesn't attempt to install anything. It's as if I unplugged the cord once it enters recovery from the bootloader. I assume USB debugging is off, because it would be at the default setting. I tried using the Flash Stock + Unroot option in the Nexus Root Toolkit with the Soft-Bricked/Bootloop setting in, but that fails in both normal recovery (with the device unnoticed) and sideload mode. I'm guessing that debugging needs to be on for this?
Does anyone have any suggestions for other things to try? I have no way of knowing what the original owner may or may not have done, and this was the first time that I restarted the device, so I have no way to know if the problem was caused by the OTA or not.
EDIT: It looks like I made the situation worse. I attempted running the Flash Stock + Unroot option from the bootloader. I am not sure what happened, but now the device starts at the Google page with green start in an arrow. I have the bootloader options, and start and recovery options give me a "booting failed" message in the top left and just stay on the google page. Restarting the bootloader gives me the normal bootloader android image and the options have the same effects.
For anyone who runs into this problem, I seem to have at least temporarily solved it.
I followed the advice here to manually flash the factory image. I am now back to where I was when I bought the phone, and I will immediately enable debugging and test it's ability to restart, connect in recovery mode, etc now.
EDIT: It can restart normally (with the unlocked logo), but it is still completely unrecognized in recovery unless I choose the sideload option like before. Should I return the tablet?
wioneo said:
For anyone who runs into this problem, I seem to have at least temporarily solved it.
I followed the advice here to manually flash the factory image. I am now back to where I was when I bought the phone, and I will immediately enable debugging and test it's ability to restart, connect in recovery mode, etc now.
EDIT: It can restart normally (with the unlocked logo), but it is still completely unrecognized in recovery unless I choose the sideload option like before. Should I return the tablet?
Click to expand...
Click to collapse
still have a problem?
Wrong drivers, try other USB ports. Had that happen with another tablet. Only recognized in adb side load with galaxy nexus driver loading, possibly from universal adb drivers... Switched to a port on the other side and correct drivers finally worked.
Sent from my Le Pan TC1020 using Tapatalk
norwoodesteel said:
still have a problem?
Click to expand...
Click to collapse
As far as I know, no. I was never able to get the device is to be detected by my computer while in stock recovery mode, however it was detected after I flashed ClockworkMod Recovery. So I still have no idea what was causing that problem, but it is no longer relevant.
Hi all,
I greatly need your help or some advice. I searched for more than 6h yesterday and Im surprised I couldnt find a solution to my problem.
Typical stuff : I broke the screen of my Nexus 4, that is completely stock 5.0.1. The phone is unrooted, bootloader is locked and obviously USB Debugging is disabled.
I need to backup some data from my phone : pictures, notes and if possible my contacts.
When I connect my phone via USB to my PC, I cant browse my files since my screen is locked. My screen is not responding at all, so no way I can unlock it. Only thing I can do is install new applications on my phone, but no way to launch them since I'd need to unlock my screen again.
I have installed adb and fastboot in order to try and use Android Screen Control, but I dont have USB Debugging enabled.
So I read that I could sideload a kernel that has USB Debugging enabled by default.
I got into Recovery Mode, and tried sideloading a zip file containing a Kernel found on the forum, but I always get an error saying the footer is wrong and the signature of the file didnt pass verification. I guess I can only sideload OTA updates ?
I tried fastbooting CWM recovery, that also didnt work.
adb devices command lists my 'recovery' device.
At this stage, all I need is to either be able to unlock my phone so I can access my files via USB (i tried few apps without success), or to enable USB debugging so I can connection using sideload, use Android Screen Control, reset the pattern lock, and backup my phone.
Also, USB OTG isnt enabled by default on Nexus 4, so that's another dead-end
So what are my options ? Where could I find a kernel that has USB Debug enabled, and how can I sideload it considering phone is not rooted, and bootloader is locked (unlocking it and whipping data defies the purpose).
THANK YOU for any advice!
There is nothing you can do with a locked bootloader and no custom recovery. Sorry man, but you're not going to be able to access your data.
Sent from my Nexus 9 using XDA Free mobile app
I've exactly the same problem, but my bootloader is unlocked and I'm rooted.
I'm also on a Nexus 4 with 5.0.1 and I'm trying to get control over my device from my Windows PC. But I don't know which kernel to use and how (yet) to enable USB debugging.
Help is appreciated.
Joakim_Lind said:
I've exactly the same problem, but my bootloader is unlocked and I'm rooted.
I'm also on a Nexus 4 with 5.0.1 and I'm trying to get control over my device from my Windows PC. But I don't know which kernel to use and how (yet) to enable USB debugging.
Help is appreciated.
Click to expand...
Click to collapse
All you need is a custom recovery to boot into to access your files. If you don't have one, download the latest version of twrp from here. http://techerrata.com/browse/twrp2/mako
Then flash that using fastboot. If you need help let us know.
Sent from my Nexus 5 using XDA Free mobile app
Hmm, "error: cannot load 'open recovery-twrp-2.3.2.3-mako'.
Sure usb-debugging doesn't have to be enabled?
Joakim_Lind said:
Hmm, "error: cannot load 'open recovery-twrp-2.3.2.3-mako'.
Sure usb-debugging doesn't have to be enabled?
Click to expand...
Click to collapse
You have an ancient version of twrp. Install the latest. I'm positive you don't need usb debugging enabled.
Sent from my Nexus 5 using XDA Free mobile app
Yes, you're so right! I also missed .img in the command
But what kernel would you recommend me to use so I have usb-debugging I can have usb-debugging enabled?
I am in almost completely the same situation! My N4 fell yesterday and shattered at the bottom right hand corner. No the touch screen doesn't work and there are sections of the screen that are black. However, I have...
root
cwm recovery
stock 5.0.1 kernel
windows 7
adb not working
fastboot working
usb debugging disabled
a need for usb debugging to become enabled.
I would like a kernel with usb debugging enabled and instructions on how to install it. Or if you have another fix, instructions on that.
So as the title suggest, my screen is working but not recognizing touch. Basically useless.
Device is rooted, Usb debugging is enabled but RSA Key is not authorised to this pc.
Stock Lollipop with custom kernel.
Problem 1 -
I am already with CWM recovery. From what I have read from cwm recovery I must be able to get access to adb recovery mode so I can backup my app data from system but the device stills shows "Unauthorized" in recovery mode. I dont know why this is happening?
Problem 2 -
I bought the OTG USB Y Cable thinking I might be able to install a differnet kernel that support otg through external power source but then I read that most kernel require to manually enable the option in settings/tweaker app for OTG SUPPORT. I cannot do this becasue as i said my screen is not working.
Please help me out.
Does your computer recognize the phone in bootloader? If so I would suggest you flash twrp and then try booting to recovery. Then you can check if your computer recognizes it now.
theminikiller said:
Does your computer recognize the phone in bootloader? If so I would suggest you flash twrp and then try booting to recovery. Then you can check if your computer recognizes it now.
Click to expand...
Click to collapse
Yes.
Already did that and it did work.
Was able to backup few imp. data.
I just have one more question -
Is there some kernel which support otg in Lollipop without me manually going into settings/tweaker app for kernel and enabling it?
Because I cannot do it manually coz the screen is broken.
Hi, all. I'm a dumbass and tried to update my phone today without making sure I was doing it right. Long story short, I have a recovery that doesn't work with N (TWRP, my device was on preview #2) and a good bootloader. However, when I updated, I forgot to turn on usb debugging. Now that the update failed, I can only boot to recovery (doesn't work) and the bootloader. NRT doesn't recognize the phone because debugging isn't enabled.
Can someone walk me through getting my phone running again?
Never mind. I got it. I have a USB hub that my phone doesn't like, apparently.