Database Info

[Q] [A700] - Can't unlock bootloader-hangs on green Acer logo [SOLVED]

Hi All:
First-time poster here. I searched the forums but could not find an answer to my problem.
I want to root my A700 and install a custom ROM but I can't get the bootloader unlocked. I have followed the instructions from this post but can't get past the first step. ADB definitely recognizes my device [adb devices] by returning the correct s/n. When I enter [adb reboot-bootloader] my tab reboots but then hangs on the green Acer logo and goes no further. Any attempts to use ADB result in a "waiting for device" message. My only option is to power off by holding the power button then reboot normally.
Here's my device/PC info:
A700:
Android version: 4.1.1
Kernel version: 3.1.10+
Image version: Acer_AV051_A700_RV18RC01_PA_CUS1
Build Number: Acer_AV051_A700_1.052.00_PA_CUS1
PC:
Windows 8 Pro 64bit
Android SDK 64 bit (I also tried 32bit with no luck)
I have rooted devices before so I am not totally new to the process, but no expert either! Any thoughts?
Thanks in advance for any advice/info shared!
Note: Had to use Acer USB driver for ICS. There was no USB driver for JB. Could that be the problem?

Perhaps try to reboot into bootloader manualy. For this first switch off your device, then press power button and volume (-) together. As soon as the tab vibrates, release the power button and switch the screen lock two or three times. Then you should get into the bootloader mode and can try to use the adb commands. Of corse, with a connected usb cable.
Sent from my A700 using xda app-developers app

georgepcde said:
Perhaps try to reboot into bootloader manualy. For this first switch off your device, then press power button and volume (-) together. As soon as the tab vibrates, release the power button and switch the screen lock two or three times. Then you should get into the bootloader mode and can try to use the adb commands. Of corse, with a connected usb cable.
Sent from my A700 using xda app-developers app
Click to expand...
Click to collapse
Good thought but no luck.
Thanks, though.

After rebooting with "adb reboot bootloader" you should be in the bootloader, and in fastboot mode. Try issuing "fastboot devices" after rebooting.
Edit: Just tried the unlock guide from that thread, and with the ICS driver from Acer. Getting the driver to install was way worse than unlocking the bootloader (many "installations" that didn't create any files for whatever reason).
After ADB recognized my tab, I was able to follow the guide up to the "flash recovery" part.
- with "adb reboot-bootloader" you should land in the bootloader. It only shows the Acer logo and some very small written things in the upper-right corner;
- from here on you need to use fastboot: "fastboot oem unlock". Typing "fastboot devices", as I said before, works just like "adb devices";
- the whole unlocking procedure is very frustrating, because the instructions are so small and the timeout so fast. If I'm not mistaken, you need to choose with VOL- and confirm with VOL+.
PS: pmrmx was faster

rgkjr1 said:
Hi All:
First-time poster here. I searched the forums but could not find an answer to my problem.
I want to root my A700 and install a custom ROM but I can't get the bootloader unlocked. I have followed the instructions from this post but can't get past the first step. ADB definitely recognizes my device [adb devices] by returning the correct s/n. When I enter [adb reboot-bootloader] my tab reboots but then hangs on the green Acer logo and goes no further. Any attempts to use ADB result in a "waiting for device" message. My only option is to power off by holding the power button then reboot normally.
Here's my device/PC info:
A700:
Android version: 4.1.1
Kernel version: 3.1.10+
Image version: Acer_AV051_A700_RV18RC01_PA_CUS1
Build Number: Acer_AV051_A700_1.052.00_PA_CUS1
PC:
Windows 8 Pro 64bit
Android SDK 64 bit (I also tried 32bit with no luck)
I have rooted devices before so I am not totally new to the process, but no expert either! Any thoughts?
Thanks in advance for any advice/info shared!
Note: Had to use Acer USB driver for ICS. There was no USB driver for JB. Could that be the problem?
Click to expand...
Click to collapse
After the ADB reboot-bootloader, there should be some really tiny white type in the upper left corner of the green logo screen.
This is when you type "fastboot OEM unlock" then volume +, then volume -
The tiny type should change. Forever after you will have a tiny message up there about the bootloader is unlocked.

smirneger said:
After rebooting with "adb reboot bootloader" you should be in the bootloader, and in fastboot mode. Try issuing "fastboot devices" after rebooting.
Edit: Just tried the unlock guide from that thread, and with the ICS driver from Acer. Getting the driver to install was way worse than unlocking the bootloader (many "installations" that didn't create any files for whatever reason).
After ADB recognized my tab, I was able to follow the guide up to the "flash recovery" part.
- with "adb reboot-bootloader" you should land in the bootloader. It only shows the Acer logo and some very small written things in the upper-right corner;
- from here on you need to use fastboot: "fastboot oem unlock". Typing "fastboot devices", as I said before, works just like "adb devices";
- the whole unlocking procedure is very frustrating, because the instructions are so small and the timeout so fast. If I'm not mistaken, you need to choose with VOL- and confirm with VOL+.
PS: pmrmx was faster
Click to expand...
Click to collapse
pmrmx774 said:
After the ADB reboot-bootloader, there should be some really tiny white type in the upper left corner of the green logo screen.
This is when you type "fastboot OEM unlock" then volume +, then volume -
The tiny type should change. Forever after you will have a tiny message up there about the bootloader is unlocked.
Click to expand...
Click to collapse
Unfortunately, the problem is that the little white text never appears - that's where it hangs - the screen is completly blank except for the green Acer logo. And if I try to enter "fastboot devices" I simply get another adb prompt (nothing else - it just jumps to a new line.) If I enter "fastboot oem unlock", adb returns "<waiting for device>" and then goes nowhere. All the while, for both commands, the tab is stuck on the Acer logo.

rgkjr1 said:
Unfortunately, the problem is that the little white text never appears - that's where it hangs - the screen is completly blank except for the green Acer logo. And if I try to enter "fastboot devices" I simply get another adb prompt (nothing else - it just jumps to a new line.) If I enter "fastboot oem unlock", adb returns "<waiting for device>" and then goes nowhere. All the while, for both commands, the tab is stuck on the Acer logo.
Click to expand...
Click to collapse
You probably need to install adb USB drivers ( android universal USB driver I think which is different than the Acer USB driver ). While adb will work when tablet is in USB debugging mode, once it rebooted your PC can't communicate with it anymore that's why its waiting for the device.
Sent from my A701 using xda app-developers app

hey_joe said:
You probably need to install adb USB drivers ( android universal USB driver I think which is different than the Acer USB driver ). While adb will work when tablet is in USB debugging mode, once it rebooted your PC can't communicate with it anymore that's why its waiting for the device.
Sent from my A701 using xda app-developers app
Click to expand...
Click to collapse
Thanks, hey_joe. I actually already tried that but decided to try again. This time it worked! I don't know what I did differently but bootloader is now unlocked!
Thanks, All!!!

Tablet ubislate 9ci hanging on bootloading
Dear sir/madam, I am new to this forum. I purchased a new tablet Datawind Ubislate 9ci. It is a 9 inch no-bluetooth tablet.
>Details:
>*.Android 4.1.1
>*.Rock chip RK2928
>*.KERNEL linux version 3.0.36 i was trying to install CWM through mobile odin and ROM manager but my tablet was not supported so i downloaded build.prop editor from google play and changed it to some other cwm recognizable model viz. Samsung, nexus etc. When i was doing the above mentioned procedure, suddenly my tablet is coming up to bootloading and hanging there only and not opening i tried to go to recovery by pressing power and vol but i am not getting recovery menu, i also tried to hard reset by pressing reset with a needle at the back but all in vain again hanging on bootloading i also tried press and hold power & vol- and several other combinations , all in vain so kindly help me and guide me Thank you

Hello there. First of all thank you for your support. I'm here because I have the same problem as OP, but first a little context.
I have already rooted my A700 before, without any difficulties. But after a crash, I restored it to factory and tried to redo the whole procedure.
So, here I am, USB driver installed (I had to modify android_winusb manually for windows to finally accept the drivers), adb up and running, adb reboot-bootloader executed and...
Acer screen, no text, just like the OP. And a yellow "Fastboot" device in my Device Manager window. So I'm stuck here. I've tried to uninstall/reinstall the google USB drivers to no avail, unlike OP. I can access the Acer recovery with the reboot recovery prompt, but I'm not confident enough to ignore the step in this tutorial.
Additional precisions : when the device is stuck with the Acer Logo (without text) trying to use a fastboot prompt (like oem unlock) only gives me the <Waiting for device> message.
I could use the Acer recovery to install a rom from external storage, but I'm unsure if it's a good idea to NOT use CWM or TWRP
Thank you, I'm starting to miss Android 4.4 (yeah, because the Acer update manager give an error 400)
Update : I did manage to access fastboot. Just as I had to modify android_winusb with the PID of my tablet when it was running, I also had to edit the file with the PID of the tablet waiting in fastboot. I didn't noticed they were different.

Soft bricked device, can't unlock, need help.

I'm on Android 5.0.1. I changed my PIN screen lock of my xperia and 20 minutes later I forgot it out of lots of things happening at once. I try to guess it 120 times (5.0 doesn't have "Enter google password" after x tries) without any progress (I was still at school at this point). I tried to boot to recovery and wipe it, but because I had Cyanogenmod recovery it didn't work. (it doesn't work at all, when I try to wipe it, it just displays the Android and flashes a few times and that's it.). At home, I tried to use Android Device Manager to erase it, but it just rebooted into Android. I tried to unlock the screen with the lock feature, but it didn't work at all, nothing happened (if I put something in the text field it allowed me to call owner. Pressing back or home puts me back in the lock screen "swipe up to unlock" state. I tried reflashing it with flashtool, but I couldn't even connect my device through ADB, it only said
Code:
04/034/2015 18:34:13 - INFO - Device connected with USB debugging off
04/034/2015 18:34:13 - INFO - For 2011 devices line, be sure you are not in MTP mode
even though USB debugging was on, even the notification said so. ADB just doesn't find it at all. When I plug my device in my computer the window that pops up says "This folder is empty". Am I really screwed? I guess my only chance is to keep guessing the password... I don't remember the first number or how many numbers were in it... help?

pefu19 said:
I'm on Android 5.0.1. I changed my PIN screen lock of my xperia and 20 minutes later I forgot it out of lots of things happening at once. I try to guess it 120 times (5.0 doesn't have "Enter google password" after x tries) without any progress (I was still at school at this point). I tried to boot to recovery and wipe it, but because I had Cyanogenmod recovery it didn't work. (it doesn't work at all, when I try to wipe it, it just displays the Android and flashes a few times and that's it.). At home, I tried to use Android Device Manager to erase it, but it just rebooted into Android. I tried to unlock the screen with the lock feature, but it didn't work at all, nothing happened (if I put something in the text field it allowed me to call owner. Pressing back or home puts me back in the lock screen "swipe up to unlock" state. I tried reflashing it with flashtool, but I couldn't even connect my device through ADB, it only said
Code:
04/034/2015 18:34:13 - INFO - Device connected with USB debugging off
04/034/2015 18:34:13 - INFO - For 2011 devices line, be sure you are not in MTP mode
even though USB debugging was on, even the notification said so. ADB just doesn't find it at all. When I plug my device in my computer the window that pops up says "This folder is empty". Am I really screwed? I guess my only chance is to keep guessing the password... I don't remember the first number or how many numbers were in it... help?
Click to expand...
Click to collapse
Hi bro.
Download this file Here.
Extract it on your desktop.
Now this file will install the cwm recovery.
Open a command window in the folder you have extracted.
Type
fastboot flash boot boot.IMG
Now before pressing enter you just need to power off your phone connecting it to the computer while holding volume + key .
Now you can press enter.
After you flash the recovery boot to recovery and make a factory reset.
Note: after this process the WiFi may not work you just need to install this app http://forum.xda-developers.com/xperia-l/development/app-recoveries-recovery-installer-t3187915 and give root and install TWRP.
And don't worry windows won't show the internal or the external memory because your phone is locked it's kind of protecting your files .
Don't forget to hit thanks

n78 shadow said:
Hi bro.
Download this file Here.
Extract it on your desktop.
Now this file will install the cwm recovery.
Open a command window in the folder you have extracted.
Type
fastboot flash boot boot.IMG
Now before pressing enter you just need to power off your phone connecting it to the computer while holding volume + key .
Now you can press enter.
After you flash the recovery boot to recovery and make a factory reset.
Note: after this process the WiFi may not work you just need to install this app http://forum.xda-developers.com/xperia-l/development/app-recoveries-recovery-installer-t3187915 and give root and install TWRP.
And don't worry windows won't show the internal or the external memory because your phone is locked it's kind of protecting your files .
Don't forget to hit thanks
Click to expand...
Click to collapse
I did what you told me to do, and it says < waiting for device > in the console. The device displays a blue LED after I volume+ and plug the USB in. I then enter the command and it's just stuck at < waiting for device >.

pefu19 said:
I did what you told me to do
Click to expand...
Click to collapse
Did you have fastboot driver installed?
If not go to flashtool folder then to drivers there you will see a exe file ,open it and install fastboot drivers and xperia l derivers.
Edit: and I think it should be installed automatically by windows just wait for it.

n78 shadow said:
Did you have fastboot driver installed?
If not go to flashtool folder then to drivers there you will see a exe file ,open it and install fastboot drivers and xperia l derivers.
Edit: and I think it should be installed automatically by windows just wait for it.
Click to expand...
Click to collapse
I think I have them installed, but when I go to the flashtool drivers folder and install those drivers, I select xperia L drivers and the 2 on top, it says Install Failed for all of them

What windows do you use???
If 8 I think it won't work , you should try it on another one

n78 shadow said:
What windows do you use???
If 8 I think it won't work , you should try it on another one
Click to expand...
Click to collapse
I have Windows 10 x64

pefu19 said:
I have Windows 10 x64
Click to expand...
Click to collapse
Sorry bro that won't work try it on another computer with 7 or lower.
Don't forget to hit thanks if I hleped you

pefu19 said:
I have Windows 10 x64
Click to expand...
Click to collapse
windows 10 has a special 3rd party driver protection... you must disable it and install fastboot driver... AND you need a USB2.0 because 3.0 has known issues
Sent from my Xperia T using XDA Free mobile app

In Window 10 go to setting>update&security>Recovery>Advanced startup and restart pc >then choose troubleshoot>Advanced Option>Startup Setting and restart>and it will ask option choose Disable Driver signature enforcement and done......
if you have any problem ask...:laugh:

Recovery boots to system software not authorized by VW

The phone doesn't have volume buttons so I decided to root it with Towelroot and install a 4 way reboot for recovery . Now every time I try to boot it starts with recovery booting in blue then secure fail: kernel system software not authorized by Verizon Wireless... . The phone is in 4.4.2 and can't go into adb or Odin as I can't get it in download mode. Is there a fix for this or am I completely screwed ?

xTheLover said:
The phone doesn't have volume buttons so I decided to root it with Towelroot and install a 4 way reboot for recovery . Now every time I try to boot it starts with recovery booting in blue then secure fail: kernel system software not authorized by Verizon Wireless... . The phone is in 4.4.2 and can't go into adb or Odin as I can't get it in download mode. Is there a fix for this or am I completely screwed ?
Click to expand...
Click to collapse
I also face the same problem when i install TWRP 2.8.7.0 using Flashify.
With the phone powered off, press simultaneously volume down, home and power button to get into download mode. On the screen offering option to Volume Up to continue and Volume Down to cancel, press Volume Down and the phone will restart and you can use it.
The link to this forum is given below:
http://forums.androidcentral.com/ve...my-phone-hard-bricked-no-chance-recovery.html

can't get into download mode as volume buttons are broken, is there a way to boot into download mode without volume buttons on the error screen?

xTheLover said:
can't get into download mode as volume buttons are broken, is there a way to boot into download mode without volume buttons on the error screen?
Click to expand...
Click to collapse
If you are familiar with adb, and you have it installed on your computer, you can use it to boot into download mode with this command:
Code:
adb reboot download
For more information check here: http://forum.xda-developers.com/showthread.php?t=872128

Thanks for the replies but my S3 doesn't show up when I type adb devices and Odin doesn't recognize the phone as well. I have the Samsung drivers and have USB debugging checked before all. How can I get my PC to see my s3?

xTheLover said:
Thanks for the replies but my S3 doesn't show up when I type adb devices and Odin doesn't recognize the phone as well. I have the Samsung drivers and have USB debugging checked before all. How can I get my PC to see my s3?
Click to expand...
Click to collapse
While your phone is connected to the PC check Device Manager and see if there are error icons ( yellow triangle with ! ) relating to your device. I won't be able to help much with that, I haven't used Windows in almost a decade.

Nvidia Shield Tablet K1 stuck on Bootloader Info Screen / Bootloops -- Need help

Hey everyone. So some time ago I unlocked the Bootloader, rooted and flashed with custom ROM my Nvidia Shield K1 and flashed TWRP. All was going well untill I decided to flash another ROM with an app (which was stupid indeed) Long story short it seems now as if I have no ROM and no recovery and all I got is the "Bootloader info screen" or whatever its called.
So the only thing I can make it display is:
[nvtboot] (version UNDEF_BUILD)
[bootloader] (version UNDEF_BUILD)
Device - Unlocked
Serial Number xxxxxxxxxxxxxxxxxxxxxxx
Press <Power> to select [...]
Continue
Fastboot Protocol
Recovery mode
Reboot
Poweroff
1. Using Continue does nothing, just says booting failed for like 100ms and goes back to where it was.
2. Fastboot Protocol just reboots the devices to the same thing after like 2 sec
3. Recovery mode same as Fastboot Protocol
4.Reboot and Poweroff does what it says
I've tried everything I could find online with it. No physical key combination can make it boot the ROM or TWRP.
I tried adb fastbooting with minimal adb and fastboot like Ive done times before with this Shield K1 and I cant make it see this device. ( "adb devices" wont list it)
I have tried using different USB ports, usb drivers, usb cables, PCs, fastboots and reinstalled everything multiple times and nothing changes.
I tried using any and every USB driver, ADB fastbooting Nvidia offers for this device.
The PC itself seems to detect the tablet just fine. Pluggin and unpluggin results in a notification and the android device is detected in Device Manager properly.
Powering off and on the tablet also results in a notification on the PC.
I have no idea what to do at this point and my last hope is this thread.

I had the same issue. Finally decided to reflash to stock and all is well

ADB Devices is EMPTY but phone is connected

My phone stuck on Realme Powered by Android.
I googled, installed ADB and connect my phone with my PC.
Then I do ADB Devices, but the list is empty.
Anyone know how to fix this?

If USB Debugging is enabled in Android settings then wrong Android USB driver in use: download and install the one matching your phone:
Download And Install Realme USB Drivers With How To Guide
From this tutorial, you could download and install the latest Realme USB Drivers onto your PC. The smartphone market is brimming with new offerings. Among
www.getdroidtips.com

adb daemon requires android booted. stuck at splash screen = not booted. force device in fastboot mode with Vol down + Power, install drivers as suggested and fix from fastboot.exe (no adb/usb-debugging required)

aIecxs said:
adb daemon requires android booted. stuck at splash screen = not booted. force device in fastboot mode with Vol down + Power, install drivers as suggested and fix from fastboot.exe (no adb/usb-debugging required)
Click to expand...
Click to collapse
According to Google's documentation - what hasn't changed over the last years - ADB consists of 3 softwares
1. ADB Server ( Desktop PC - establishes TCP connecion with Android Device )
2. ADB Client ( Desktop PC - sends ADB commands to Android Device )
3. ADB Daemon ( Android Device - processes ADB comannds sent )
So it should be clear that to execute ADB commands all these 3 softwares must be present and running.

So how to solve it if the phone only stuck at the powered by android screen?
xXx yYy said:
According to Google's documentation - what hasn't changed over the last years - ADB consists of 3 softwares
1. ADB Server ( Desktop PC - establishes TCP connecion with Android Device )
2. ADB Client ( Desktop PC - sends ADB commands to Android Device )
3. ADB Daemon ( Android Device - processes ADB comannds sent )
So it should be clear that to execute ADB commands all these 3 softwares must be present and running.
Click to expand...
Click to collapse
I tried with volume down + power but nothing happen.
aIecxs said:
adb daemon requires android booted. stuck at splash screen = not booted. force device in fastboot mode with Vol down + Power, install drivers as suggested and fix from fastboot.exe (no adb/usb-debugging required)
Click to expand...
Click to collapse
Any ideas guys?
Thanks in advance.

we don't know what is the reason for, you didn't tell anything what you did to cause this state. we don't know why you want adb access, I can only tell you that fastboot is available without usb-debugging.
power off device, check for proper key combo especially for your device model to enter fastboot mode.
https://www.hardreset.info/devices/realme/realme-5/fastboot-mode
if still no success, it might be fastboot mode is disabled intentionally (to prevent bootloader unlocking). in that case you are left with MSM Download Tool

Actually,you'l need to long-press the power button till the phone reboots then power + volume down IMMEDIATELY.

aIecxs said:
we don't know what is the reason for, you didn't tell anything what you did to cause this state. we don't know why you want adb access, I can only tell you that fastboot is available without usb-debugging.
power off device, check for proper key combo especially for your device model to enter fastboot mode.
https://www.hardreset.info/devices/realme/realme-5/fastboot-mode
if still no success, it might be fastboot mode is disabled intentionally (to prevent bootloader unlocking). in that case you are left with MSM Download Tool
Click to expand...
Click to collapse
So actually the phone have the volume up button and power button damage. at one time, it suddenly keep restarting. Then I let it be until the power fully gone. I ordered new volume and power button and change them.
Then I connect power supply to turn it on. But it seems it is stuck in "Realme Powered By Android" screen.
I tried to force shut down it and restart but still the same.
So I want to fast boot the phone but I am not successful.
Any Idea how I can do it?

sd369888 said:
Actually,you'l need to long-press the power button till the phone reboots then power + volume down IMMEDIATELY.
Click to expand...
Click to collapse
I tried 3 minutes pressing power button but nothing change. Then I restart using volume up + power button then immediately press volume down + power when it is turned off. But it seems it is the same too.