Hello together,
first I wanna say sorry for my bad english...i'm still learning
I've got three days before the A510 from my cousin, with the note that it always hangs during the Acer logo. He said he wanted to make an update and after that it would no longer boot.
When I type "fastboot devices" in cmd, no model appears.
Drivers are installed,'ve tried different USB ports. Used as the operating system Windows 8 64bit.
USB debugging is probably not been turned on (according to statement of my cousins).
Does anyone know this problem and can anyone help me with this?
Is the first time that I have to do with an Acer device, so am really encouraging hose...
I just tried the whole on a Windows 7 64bit computer times. Now there stands the following things in cmd after typing "fastboot devices": "fastboot devices" a "?" then some space and "fastboot".
If I type "fastboot oem unlock" there are two pictures on the tablet and the message that I should confirm with Vol- and Vol+ to select ... but when I do, it says:
"SetUnlockMode: Error occured while unlock the device ..."
"Fastboot: Failed to set unlock mode"
Now I am even more confused than before ...
Thanks for the help!!!
Related
So i just got my first android device about 4 hours ago. Been reading a lot and got the sdk all setup. ADB is working fine i can see the device by typing "adb devices". I've added Fastboot to the .bash_profile and "fastboot --help" shows the help file so its working but i'm trying to flash a recovery.img and after i put in "fastboot flash recovery recovery.img" i just get "<waiting for device>
Its a Dell Streak and i know the id is -i 0x413c I've been searching google like a mad man and every instance i find is either for ubuntu or XP and solved by updating the drivers yet there is no need for the drivers on Mac.
Any help?
figured it out.. i had so many tabs open and so much going on i overlooked the simplest thing!
the device wasn't in bootloader mode! haha (power on device while holding the camera button to get into fast boot...) i feel like a fool... oh well, we all have our days right?
waiting for device
Hi fone_fanatic, I got similar problem. I've been trying to search for solution but I just found your post. I hope you can help me out.
I was trying to install recovery to my LG P350, got errors and when it reboots it self, it just says:
fastboot mode started
udc_start()
and when I plugged it in to my pc it says:
fastboot mode started
udc_start()
-- suspend --
-- reset --
-- portchange --
-- reset --
and so on and so forth...
I have tried downloading sdk and all drivers needed for my lg phone.
Tried using cmd promt and typed in "cd (directory where skd located)"
Then typed in "fastboot erase recovery" It says waiting for device. Tried "fastboot devices" but no list for devices.
I am not familliar with bootloader mode. I really hope you can give me some hints or fix for my problem. Thanks in advance..
Hey everyone,
Just got my Xoom an hour ago. Been preparing to unlock it as soon as I got it. I am running Linux Mint 10, and have installed the sdk and adb/fastboot.
However, when I type in the command to boot my Xoom into the bootloader it works and takes me into the "Starting Fastboot protocol support" screen. Then when I type the "./fastboot oem unlock" command, it just says "<waiting for device> in the Terminal. Any ideas how to proceed? I've tried taking the usb in and out, I've tried using a different usb port.
Thanks
Nerver mind. I figured it out
Hi, I'm trying to unlock my phone so I can install Kali Linux on my A466BG. I've read a lot on the web but came to a problem. I've got Android SDK on my PC and installed platform-tools. My device shows up after entering "adb devices." I've enabled developer mode and usb debugging and OEM unlocking. My problem is...I can't unlock the bootloader and use fastboot. After pressing power and up volume I get into the menu (and I actually reset my phone to factory settings so I'll have more space) but I can't find bootloader. My phone shows up fine on my PC and under devices, but when I switch to the other menu (with reset options) it doesn't show up anymore. Not even under "adb devices." I tried entering "adb reboot-bootloader" but it just restarts and goes to the normal android phone screen. I tried "fastboot -i 0x1bbb oem device-info" and it says "waiting for device." I'm not sure how to boot into fastboot and unlock my bootloader. Or why my phone doesn't show up on my PC after pressing power and up volume. Please reply with instructions. Thank you
Hi, me again. I found a video on YouTube on how to install Kali Nethunter on Android phones. I got it and now I'm installing Metasploit. It's just the command line but that should work. Check You Tube on "Nethunter without root" if you want to know. Thanks
I'm back...Not satisfied with Nethunter on Termux. I would like to know how to root the phone and install Kali. Can anyone look at the above question and reply with how to root my Alcatel A466BG? I'll check back tomorrow. Thanks in advance!
I think I bricked my acer iconia tab a700. Every time I start the tab there only comes the acer logo and on the left upper corner there stands "Bootloader Version JB-653b3d3 (Unlock Mode)".
I know there is a thread about this (https://forum.xda-developers.com/t/acer-a700-bricked.1952590/) but that doesn't help me. If I follow the instructions of this thread to get into fastboot nothing happens.
Can someone help me how I can get into fastboot mode to connect the tab with my pc? Tanks in advance.
Fastboot deals with tablet's bootloader, whereas ADB deals with tablet's Android OS. What is really your goal?
BTW:
"Bootloader Version JB-653b3d3 (Unlock Mode)" states your tablet got booted into Fastboot mode. When in Fastboot mode no UI is presented to you: Fastboot is command-line driven.
jwoegerbauer said:
Fastboot deals with tablet's bootloader, whereas ADB deals with tablet's Android OS. What is really your goal?
BTW:
"Bootloader Version JB-653b3d3 (Unlock Mode)" states your tablet got booted into Fastboot mode. When in Fastboot mode no UI is presented to you: Fastboot is command-line driven.
Click to expand...
Click to collapse
My goal is to install an OS to use my tablet. I still don't found the OS but I think thats not the biggest problem.
If it states for that my tablet boots into fastboot how can I connect it with my PC because the tablet is rebooting after 15 sec. And if I connected it on my pc and typed "adb devices" in my command line nothing comes up.
If "adb devices" doesn't list your tablet ( connection type ) then may be USB Debugging didn't get enabled on tablet.
jwoegerbauer said:
If "adb devices" doesn't list your tablet ( connection type ) then may be USB Debugging didn't get enabled on tablet.
Click to expand...
Click to collapse
in this case i can throw the tablet in the trash?
Hopefully someone here can help me through my problem,
Device Details: BLU G60/BLU VIVO X6
Android 9/Pie
OEM Unlocking: Allowed
USB Debugging: Enabled
Hey, I'm pretty new to this way of customizing my phone (adb, root, roms etc), and I'm trying to root my phone with Magisk. I have a patched boot.img, my bootloader is allowed to be unlocked and I'm doing exactly what the root guide says (https://www.mobilewithdrivers.com/magisk-root/blu-g60-64gb-3gb-ram) but it wont work, I keep getting different errors and I see all my fellow droid users so happy with their rooted devices, I want to root mine too. So what I'm asking is; Can someone with an actual brain (Mine wont work) to try and help me out or walk me through step-by-step?
Thanks for reading!
Some of the issues I have:
"adb reboot booter" and "fastboot reboot bootloader" both reboot the device but in the top left corner it says "fastboot mode" and just freezes, when I do any command it just says "device null" but when I reconnect the USB cable, it just powers off.
"fastboot flashing unlock" results in "FAILED (remote: Not implemet.)" Yes, spelt like that.
"fastboot oem unlock" says, unkown cmd...
Wrong driver in use. Use the one provided by BLU suitable to your phone.
i couldnt find any drivers for the exact device, only google ones...
any ideas?
If you have a mac, you could try that. They usually don't require drivers.