I'm trying to help a member of xoomforums.com but usb debugging isn't checked. Is there a way to unlock it with it being unchecked. He has a xoom that doesn't toggle to android recovery.
hi
yesterday i bought this xoom from a shop returns auction knowing that it was password protected.
but i had read the guides how to hard reset on this forum and thought it would be an easy fix, as i have rooted and installed many different roms on my htc hd desire and my onda vi40 tablet with relative ease.
i got back from the auction and went to hard reset and quickly found out the xoom does'nt have the recovery mode, just 'nvflash' 'rsd' and 'fastboot'
searching more i found there are few like this all wi fi models but no real answer how to fix??
the closest help i found was this guide external factory reset?
i got to the point where you type 'adb devices' into 'cmd' but it doesn't find mine?
but then i don't know what mode i should put my xoom in 'nvflash' 'rsd' 'fastboot' or the password screen?
when my xoom is on the password screen it it shows up on the computer as mz604 (portable media player)
SOMEBODY PLEASE HELP!!!!!!!!!!!!
i hope i have'nt bought myself a heavy paperweight!!!!
for anybody that is worried that i have maybe stole this i have the invoice that i could take a picture of as proof of purchase and post it on here if i have to. it came boxed still with clear protectors on the back....
http://www.xoomforums.com/forum/mot...-all-i-get-nvflash-rsd-fastboot-scrolls.html#
Boot into fastboot, then unlock it (fastboot oem unlock)
You don't actually need to use adb to unlock these devices.
solarnz said:
Boot into fastboot, then unlock it (fastboot oem unlock)
You don't actually need to use adb to unlock these devices.
Click to expand...
Click to collapse
Thanks man.
solarnz said:
Boot into fastboot, then unlock it (fastboot oem unlock)
You don't actually need to use adb to unlock these devices.
Click to expand...
Click to collapse
Not really sure how to use fastboot without the sdk.
Install the sdk then.
It's exactly the same, the only reason you need 'USB Debugging' enabled, is to be able to reboot into the bootloader.
So to skip that, just choose fastboot from menu in the bootloader, which the user has obviously been able to get into.
Thanks, he got it wiped.
Hey guys I really hope you can help me out because I have a bricked N5. So this is my first time attempting to flash anything to my phone and I decided to check out the android L preview. I watched a bunch of videos and got everything set up (SDK, unlocked bootloader). After I unlocked the bootloader, I forgot to enable usb debugging before I booted into fastboot and attempted to flash L. When I try to flash L I get "writing bootloader... FAILED (remote: invalid bootloader image)" every time. So I said screw it I'll just flash 4.4.4 and be done with it but I get the same FAILED msg in cmd. I'm assuming this is the issue that's preventing me from successfully flashing anything to my phone but not 100% sure. I've tried to get my phone into recovery mode but can't seem to make that work either. What can I do to fix this? keep in mind that just today was the first time I've ever used the command prompt =/ Thanks in advance for giving this a read and I really hope its just some simple fix *fingers crossed*
USB Debugging has NOTHING to do with bootloader or fastboot. The ONLY thing USB Debugging is related to is ADB while booted into Android.
You might want to read some more threads: [Resource] All Guides and Info Threads
Lethargy said:
USB Debugging has NOTHING to do with bootloader or fastboot. The ONLY thing USB Debugging is related to is ADB while booted into Android.
You might want to read some more threads: [Resource] All Guides and Info Threads
Click to expand...
Click to collapse
well turn's out all I had to do was restart my laptop and now everything has decided to work. Thanks for the response Lethargy
Hello to You all!
Having a hell of a problem here and I cant solve it by myself, tryed like 10 times over the past year and its time to realize I´ve been beaten...
I wonder if its possible to enable usb debugging in bootloader mode? I have this Mediapad x2 that i tryed to unlock the bootloader on a year ago and though the bootloader unlocked (shown as "unlocked" in bootloader mode) the phone never restarted again... It loops at the bootscreen. Vol down gets me to bootloader though, both vol up/down gets me to auto restore but even if I have the right file on the SD-card the phones autorestore hangs at 90%...
All manual commands like "fastboot flash system system.img" or "fastboot flash recovery TWRP.img" only give´s me "FAILED (remote: Command not allowed)"...
I THINK it must be the USB debugging that doesn´t allow me to write, I´m not that advanced in this area...
Any help appreciated mates, I really liked this phone.
Thank You.
XDA Visitor said:
Hello to You all!
Having a hell of a problem here and I cant solve it by myself, tryed like 10 times over the past year and its time to realize I´ve been beaten...
I wonder if its possible to enable usb debugging in bootloader mode? I have this Mediapad x2 that i tryed to unlock the bootloader on a year ago and though the bootloader unlocked (shown as "unlocked" in bootloader mode) the phone never restarted again... It loops at the bootscreen. Vol down gets me to bootloader though, both vol up/down gets me to auto restore but even if I have the right file on the SD-card the phones autorestore hangs at 90%...
All manual commands like "fastboot flash system system.img" or "fastboot flash recovery TWRP.img" only give´s me "FAILED (remote: Command not allowed)"...
I THINK it must be the USB debugging that doesn´t allow me to write, I´m not that advanced in this area...
Any help appreciated mates, I really liked this phone.
Thank You.
Click to expand...
Click to collapse
Hello,
Do you have correct fastboot drivers installed on your system? Please run it with administrative privileges.
Please register for XDA account to post and reply in the forum.
Regards
Vatsal,
Forum Moderator.
Thread closed as you already posted it here https://forum.xda-developers.com/general/xda-assist/1-year-problem-failed-remote-command-t3535310
Hello,
So, apparently i messed up. I installed nethunter on my phone, everything was working well, finished the configuration and then i had the idiotic idea to lock the bootloader since it was locked at the beginning when i received the phone, so i locked the bootloader not knowing the consequences of that.
Now i don't have how to go to enter in recovery mode, i can't boot. The program adb and fastboot doesn't detect the phone when i do adb devices or fastboot devices. I don't know how to proceed from here.
Any ideas ?
Kind regards,
C666PO said:
Hello,
So, apparently i messed up. I installed nethunter on my phone, everything was working well, finished the configuration and then i had the idiotic idea to lock the bootloader since it was locked at the beginning when i received the phone, so i locked the bootloader not knowing the consequences of that.
Now i don't have how to go to enter in recovery mode, i can't boot. The program adb and fastboot doesn't detect the phone when i do adb devices or fastboot devices. I don't know how to proceed from here.
Any ideas ?
Kind regards,
Click to expand...
Click to collapse
Yes,there are several unbrick tools on the forum i used this one and it worked for me!
I am not able to share links so im posting a few screew shots but if you google oneplus 7 pro unbrick you ahould find this thread easy
C666PO said:
Hello,
So, apparently i messed up. I installed nethunter on my phone, everything was working well, finished the configuration and then i had the idiotic idea to lock the bootloader since it was locked at the beginning when i received the phone, so i locked the bootloader not knowing the consequences of that.
Now i don't have how to go to enter in recovery mode, i can't boot. The program adb and fastboot doesn't detect the phone when i do adb devices or fastboot devices. I don't know how to proceed from here.
Any ideas ?
Kind regards,
Click to expand...
Click to collapse
I replied to you from the xda labs app and i couldnt attach a link but it works from the browser so i apologise for my first reply hope this one is more helpfull
https://forum.xda-developers.com/on...mega-unbrick-guide-hard-bricked-t3934659/amp/
Hello, i wanted to ask how to fix the fastboot mode.
Everytime when i try to access it, it just says "Entering Fastboot..."and thats all.
I dont want to close it, thats not my problem, i just wanna flash a recovery.img, and the fastboot seems not working. Any ideas?
M3DUS4 said:
Hello, i wanted to ask how to fix the fastboot mode.
Everytime when i try to access it, it just says "Entering Fastboot..."and thats all.
I dont want to close it, thats not my problem, i just wanna flash a recovery.img, and the fastboot seems not working. Any ideas?
Click to expand...
Click to collapse
this could be because the galaxy A51 wasnt built with fastboot, and the code to launch this option was just reused from a different device, or because something isnt connecting properly.
Hello, I have the same ... Android 11 (and currently 12) (from Frija). So it is not the fault of incorrect configuration or with connecting. Only something is wrong with this phone ...
I have this device and this solved it for me:
Enable OEM unlocking in developer settings
Shut down the phone
Hold volume up and volume down
Plug in a USB cable connected to a computer (the computer being turned on)
Keep holding
You're in download mode!
Side note: This might not work in USA or Canada, I am from europe and it works here. I have no idea if it works in another region. Also, you can't just flash a recovery.img on Samsung since there is no real "fastboot", you have to use download mode and Odin.
But I know how to enter download mode... Problem is Fastboot mode...
There is no fastboot mode on a modern Samsung device. If there is, it's fake and you cannot flash anything with it. As you can see even from Wikipedia, Odin is the Samsung replacement of fastboot.
So no fastboot, only download mode.
If a guide is saying to use fastboot, it is not compatible with Samsung.
If you would tell me why you specifically need fastboot, I'll be happy to tell you how you can do it with Odin, if possible.
Because I have Samsung Galaxy A51 5G (A516B) with new Android 12 and I can't do a root! Because I can't upload TWRP (custom recovery) because I haven't OEM unlock option in Deveoper Option. I tried trick with set back date by 7days but not succes. Everything I;ve metioned here - I did at my phone with Android 11.
And... I have read that I can turn this fu**ing OEM option by comend at ADB: fastboot oem unlock.
Phew ...
So this fastboot method is the last method to do a root with my phone.
Upload TWRP by Odin in download mode -ends red warning - of corse...
Have you any ideas?
I would be grateful for help...
I have read this fastboot method at:
How to Unlock Bootloader On Samsung Galaxy Phones [EASY GUIDE]
Are you looking for a Complete tutorial on How To Unlock Bootloader on Samsung Galaxy Phones? If yes, then you have come to the right place.
www.guidetoroot.com
Yeah, that guide is not relevant on any modern Samsung device. Besides, even if it was, which it isn't, you would first need to enable OEM unlocking from the Developer Settings.
But the fact that you don't have an option for OEM unlock is weird, since I have the exact same device model and it is there for me.
May I ask what is your region and is your phone locked to a telephone carrier?
My region is PLS - Poland. And not - phone is not locked. Have you the newest system Android 12?
Yes, I do. It's weird that there isn't even an option for you.
I'll try to come up with some new ideas if I have time...
I'll be glad for it...
Hej, do you have any idea?
stanwin said:
Hej, do you have any idea?
Click to expand...
Click to collapse
Have you tried everything listed here?
BloodyFruitDestroyer said:
Have you tried everything listed here?
Click to expand...
Click to collapse
Yes, I did. Evething exept the last one...
You could try it. It might be risky, but it's the only option I personally can come up with right now.
I've tried this option but Odin stuck on "files verification". Any help?
have any of you encountered this problem?
And how did you solve it?
You can also try searching for combination firmware for your device online