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.

Nexus s cannot start

Can anyone help me???
When I turn on my nexus s, it starts CyanogenMod (loop screen).
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
When I turn on to fastboot mode, I cannot use Volume up/down to choose menu.
(view attach file)
What do I do now?
Thanks a lot,
Thai

Just try use nexus root tool kit maybe bootloop Irish usually corrupt flash file or kernel not compatible
Sent from my Nexus S using Tapatalk

makanorang12 said:
Just try use nexus root tool kit maybe bootloop Irish usually corrupt flash file or kernel not compatible
Sent from my Nexus S using Tapatalk
Click to expand...
Click to collapse
Thanks for your comments.
I try many ways and apps but I cannot.
I think the reasons is my pc cannot connect to the phone. I use "adb devices" command it shows "unauthorized".
In fastboot mode, my pc cannot see the phone.
I try all drivers that I know but it still the same.
I do not know USB debugging mode is enable or not.

tnmthai said:
Thanks for your comments.
I try many ways and apps but I cannot.
I think the reasons is my pc cannot connect to the phone. I use "adb devices" command it shows "unauthorized".
In fastboot mode, my pc cannot see the phone.
I try all drivers that I know but it still the same.
I do not know USB debugging mode is enable or not.
Click to expand...
Click to collapse
Remove all the drivers and just install one driver. I recommend PDANet drivers.

1630
ej8989 said:
Remove all the drivers and just install one driver. I recommend PDANet drivers.
Click to expand...
Click to collapse
yes, I did but it stills the same.
I also try in other pc.
Other ideas please?

tnmthai said:
yes, I did but it stills the same.
I also try in other pc.
Other ideas please?
Click to expand...
Click to collapse
What did you do right before this happens?
Does the volume buttons work before?

digimon04 said:
What did you do right before this happens?
Does the volume buttons work before?
Click to expand...
Click to collapse
First, It can start into ClockworkMod. I used to restore CyanogenMod.
Volume up/down and power work before. They are good when I use ClockworkMod.
Thanks all.

tnmthai said:
First, It can start into ClockworkMod. I used to restore CyanogenMod.
Volume up/down and power work before. They are good when I use ClockworkMod.
Thanks all.
Click to expand...
Click to collapse
a cache wipe/ data wipe might help
but first, you have to find a way into recovery

digimon04 said:
a cache wipe/ data wipe might help
but first, you have to find a way into recovery
Click to expand...
Click to collapse
Thanks. That's my problem.

tnmthai said:
Thanks. That's my problem.
Click to expand...
Click to collapse
Apart from the volume buttons, does the power button work in bootloader mode? I mean even you can't move up/ down, you can still activate "reboot bootloader" in bootloader screen by pushing the power button.

digimon04 said:
Apart from the volume buttons, does the power button work in bootloader mode? I mean even you can't move up/ down, you can still activate "reboot bootloader" in bootloader screen by pushing the power button.
Click to expand...
Click to collapse
Thanks Digimon04,
Yes, I can use power button.
If there is in fastboot, after rebooting it goes back to fastboot.
If I remove battery and press only power button, it goes to CyanogenMod.
I cannot do anything else.
Thanks all,

tnmthai said:
Thanks Digimon04,
Yes, I can use power button.
If there is in fastboot, after rebooting it goes back to fastboot.
If I remove battery and press only power button, it goes to CyanogenMod.
I cannot do anything else.
Thanks all,
Click to expand...
Click to collapse
That means fastboot is working correctly. Did you install Nexus Root Toolkit as suggested in #2?
Inside Nexus Root Toolkit, choose correct phone model and then launch advanced utilities. Navigate to the quick tools and select fastboot-bootloader. Press List devices to ensure that your device is recognized by the PC. Go back and you can flash stock or other ROMs. If your device is not recognized by the PC, you could follow the instruction from the Nexus Root Toolkit to remove and re-install the driver.
Last but not least, I'm afraid you couldn't use adb command in bootloader since the system is not on.

digimon04 said:
That means fastboot is working correctly. Did you install Nexus Root Toolkit as suggested in #2?
Inside Nexus Root Toolkit, choose correct phone model and then launch advanced utilities. Navigate to the quick tools and select fastboot-bootloader. Press List devices to ensure that your device is recognized by the PC. Go back and you can flash stock or other ROMs. If your device is not recognized by the PC, you could follow the instruction from the Nexus Root Toolkit to remove and re-install the driver.
Last but not least, I'm afraid you couldn't use adb command in bootloader since the system is not on.
Click to expand...
Click to collapse
Thanks.
As I mentioned before. In fastboot mode, my pc cannot see the phone. I use "adb devices" command it shows no device.
In CyanogenMod mode (just start screen loop), my pc can see the nexus s but I use "adb devices" command it shows "unauthorized".
I also use Nexus Root Toolkit for device list or somethings you said..
Any idea else ?
Thanks all.

tnmthai said:
Thanks.
As I mentioned before. In fastboot mode, my pc cannot see the phone. I use "adb devices" command it shows no device.
In CyanogenMod mode (just start screen loop), my pc can see the nexus s but I use "adb devices" command it shows "unauthorized".
I also use Nexus Root Toolkit for device list or somethings you said..
Any idea else ?
Thanks all.
Click to expand...
Click to collapse
As your phone can't boot into system, adb won't work. Without the volume buttons, you can't get into custom recovery.
Your phone can only go to bootloader and therefore, fastboot is the only option. If your computer can't see the phone, try replace the USB cable or plug into another USB port. If that still won't work, probably driver on PC might not be loaded correctly. Mere re-installation of driver won't help. I have done it once in the past. You have to pick out all relevant drivers in USBdeview before re-install the driver where Nexus Root Toolkit provide a complete guide.
You may try to press reboot/ reboot bootloader/ reboot recovery under quick tools in advanced utilities of NRT.(remember to select fastboot - bootlaoder). If your phone responds to it, that means driver is loaded and PC can communicate with the phone. You need to make fastboot work before you can do anything to rescue your phone.

digimon04 said:
As your phone can't boot into system, adb won't work. Without the volume buttons, you can't get into custom recovery.
Your phone can only go to bootloader and therefore, fastboot is the only option. If your computer can't see the phone, try replace the USB cable or plug into another USB port. If that still won't work, probably driver on PC might not be loaded correctly. Mere re-installation of driver won't help. I have done it once in the past. You have to pick out all relevant drivers in USBdeview before re-install the driver where Nexus Root Toolkit provide a complete guide.
You may try to press reboot/ reboot bootloader/ reboot recovery under quick tools in advanced utilities of NRT.(remember to select fastboot - bootlaoder). If your phone responds to it, that means driver is loaded and PC can communicate with the phone. You need to make fastboot work before you can do anything to rescue your phone.
Click to expand...
Click to collapse
Many thanks for your guide. I will do it as you said.
But I am busy this week, I will do it next week.
Thanks a lot.

tnmthai said:
Can anyone help me???
When I turn on my nexus s, it starts CyanogenMod (loop screen).
When I turn on to fastboot mode, I cannot use Volume up/down to choose menu.
(view attach file)
What do I do now?
Thanks a lot,
Thai
Click to expand...
Click to collapse
use fastboot and try to return stock (4.1.2) or check your power button, sometimes it's

Fastboot Mode Issue

Dear All,
Please help me regarding fastboot. When I press 3 keys (vol-up, vol-down and power key) while phone is off. I see the black and white screen written boot modes. From there when I select AP Fastbood device is restart with red Motorola logo and end up on home screen.. I have tried several times to turn off the device and repeat this process but no issue still there..
Moreover, if I did not select any options from boot modes than device automatically rebooted after 3 or 4 seconds..
Please help me out.. I want to unlock the boot loader root and install custom ROM..
Currently Model Number is XT925 and device is completely stock.. never rooted before...
thanks and regards,

akkay1 said:
Dear All,
Please help me regarding fastboot. When I press 3 keys (vol-up, vol-down and power key) while phone is off. I see the black and white screen written boot modes. From there when I select AP Fastbood device is restart with red Motorola logo and end up on home screen.. I have tried several times to turn off the device and repeat this process but no issue still there..
Moreover, if I did not select any options from boot modes than device automatically rebooted after 3 or 4 seconds..
Please help me out.. I want to unlock the boot loader root and install custom ROM..
Currently Model Number is XT925 and device is completely stock.. never rooted before...
thanks and regards,
Click to expand...
Click to collapse
After you use the volume down key to highlight "Fastboot", do you then press the volume up key to select it? If you just sit there and wait it will reboot normally. You must press the volume up key after you've highlighted the menu option.

akkay1 said:
Dear All,
Please help me regarding fastboot. When I press 3 keys (vol-up, vol-down and power key) while phone is off. I see the black and white screen written boot modes. From there when I select AP Fastbood device is restart with red Motorola logo and end up on home screen.. I have tried several times to turn off the device and repeat this process but no issue still there..
Moreover, if I did not select any options from boot modes than device automatically rebooted after 3 or 4 seconds..
Please help me out.. I want to unlock the boot loader root and install custom ROM..
Currently Model Number is XT925 and device is completely stock.. never rooted before...
thanks and regards,
Click to expand...
Click to collapse
try this,
-install adb on your pc
-plug in phone when powered up
- open a command prompt in your adb dir
- type in: adb devices then enter. it should show your phone in the prompt. also check your phone, there may be a popup to acknowledge.
- rerun adb devices until it shows your phone properly or you cant proceed
-now type in: adb reboot bootloader
if it works, the phone should reboot to the fastboot screen.
if it doesnt stick in fastboot, im sorry but i dont know what else to tell you to try.

Thank-you for the Response
bweN diorD said:
try this,
-install adb on your pc
-plug in phone when powered up
- open a command prompt in your adb dir
- type in: adb devices then enter. it should show your phone in the prompt. also check your phone, there may be a popup to acknowledge.
- rerun adb devices until it shows your phone properly or you cant proceed
-now type in: adb reboot bootloader
if it works, the phone should reboot to the fastboot screen.
if it doesnt stick in fastboot, im sorry but i dont know what else to tell you to try.
Click to expand...
Click to collapse
Thankyou so much for the reply, i followed your instructions and finally get in fastboot mode and unlocked the boot loader. However, is there any way from which I can go into recovery.. because through hardware way I am unable to go in recovery. Thanks
EDIT: I have tried entering command adb reboot recovery, then phone was rebooted and there was green android on screen with chest open.. thats it... i have waited for few minutes and rebooted the device mannually.

akkay1 said:
Thankyou so much for the reply, i followed your instructions and finally get in fastboot mode and unlocked the boot loader. However, is there any way from which I can go into recovery.. because through hardware way I am unable to go in recovery. Thanks
EDIT: I have tried entering command adb reboot recovery, then phone was rebooted and there was green android on screen with chest open.. thats it... i have waited for few minutes and rebooted the device mannually.
Click to expand...
Click to collapse
That's the entry to stock recovery. You have to push a combination of buttons from there to get into recovery. I forget the button combination, it has been posted many times, try searching or wait for someone else to jump in with the answer.
Sent from my LG-VS980 using XDA Premium 4 mobile app

Not sure where to post this question been reading so many post my eyes are tired......
- XT926 upgraded to kitkat 183.46 last week via flash in RSD from JB 4.1.2
- Root went well DONE (Towel root .apk)
- Unlock went well DONE (Motopocalypse .apk) yes fastboot shows the #3
- Flashed TWRP 2.7.1 DONE (did it using the adb in motopocolypse)
- Backed up my current stock ROM in TWRP seemed to go well the program confirmed the backup was successful...So I thought
- Got confident and wanted to try flashing CM11 (Kitkat version)
- After flashing CM11 my phone got stuck at boot like many others have.... no problem I backed up my stock ROM in TWRP.....So I thought
- Went to restore my stock ROM using TWRP and yup you guessed it like many others the restore failed half way through
Not a big deal starting fresh can be a good thing BUT I really need my old text messages and all I have is a USB backup of the phone (Internal/SDcard) on my PC and of course the TWRP back-up on the SDcard that won’t restore ...... Is there any way to get these messages back to my phone????

wonka144 said:
Not a big deal starting fresh can be a good thing BUT I really need my old text messages and all I have is a USB backup of the phone (Internal/SDcard) on my PC and of course the TWRP back-up on the SDcard that won’t restore ...... Is there any way to get these messages back to my phone????
Click to expand...
Click to collapse
Not sure how to help you with your immediate problem at hand, but going forward, I definitely recommend the sms backup + from the Google Play Store. Nice thing with that app is, you can link it to your gmail account, and all your text messages are backed up to your gmail.

[Q] ADB stops recognising device

Hi,
I'm trying to sideload the final 5.0 build to my Nexus 5.
The ADB drivers are installed. This command prompt is opened in the desktop. I manage to get to the point in Recovery Mode where I need to flash the 'update.zip' (which I have named exactly that and this happens.
Anyone help me please?
Thanks beforehand.
I'm not a regular here, if I have broken the rules, please let a moderator know and sort me out. If this is an illegal thread, please delete it. Apologies.

ibz100 said:
Hi,
I'm trying to sideload the final 5.0 build to my Nexus 5.
The ADB drivers are installed. This command prompt is opened in the desktop. I manage to get to the point in Recovery Mode where I need to flash the 'update.zip' (which I have named exactly that and this happens.
Anyone help me please?
Thanks beforehand.
I'm not a regular here, if I have broken the rules, please let a moderator know and sort me out. If this is an illegal thread, please delete it. Apologies.
Click to expand...
Click to collapse
Your usb drivers are not installed correctly, reinstall the drivers and enable usb debugging in developer options. Check if you succeeded by typing in cmd (while the phone is in fastboot): fastboot devices. You should see a serialnumber if all went well.

Hi, @ibz100. It actually looks like your drivers are installed properly. At least your ADB drivers. You only use ADB while booted into the android OS, or from recovery. However, while you're booted into the bootloader (also known as fastboot mode) you'll want to use "fastboot" commands.
So boot back into the bootloader either the same way using ADB while booted into the OS, or from a powered down state hold Volume down(-) & Power keys. You can also use both volume keys + power to access the Nexus 5's secondary bootloader.
Once in fastboot mode, run the command
Code:
fastboot devices
If your serial number appears like it did for ADB devices, then your fastboot drivers are successfully installed. If not, then we need to get your fastboot drivers set up.
Read here if you need to install them. Feel free to reply here if you're having trouble installing them and I can help you through that as well.
Also useful: http://forum.xda-developers.com/google-nexus-5/general/noob-read-adb-fastboot-how-hep-t2807273
If your drivers are properly installed, run the command "fastboot" without quotations to see a list of available commands to be used in fastboot. If you're still not sure what to do, just ask.
If you want to use ADB to apply the update.zip, boot into recovery mode (I'm going to assume you're using a stock recovery). Use the commands I mentioned above to get to the bootloader. Now use the volume keys to navigate from "Start" to "Recovery Mode" With Recovery selected, key the Power button. You should see a picture of an android with an exclamation mark with the text "No Command". From there hold down the Power button and tap Volume UP(+) once. This will boot you into stock recovery mode. From there use the volume keys to navigate to "Apply update from ADB". Power key to select.
Check out the Roll-up sticky guide by @rootSU for all the information you need to get yourself up and running.
http://forum.xda-developers.com/goo...urce-guides-info-threads-linked-read-t2784527
Again, if you need any more help just reply and let me know, I'm more than happy to help.

Try loading koush's universal adb drivers I was having the same problem but this solved it for me. Sidelosd worked a treat and running lollipop without problems so far...

Thabk you everybody, I'll try your recommended (re)installation of my fastboot drivers later and get back to you if I have any further updates on my situation.
Big thanks for all the replies guys, I really was taken aback by the sheer effort you put into helping people around here. Rest assured that it doesn't go unappreciated. Keep up the good work!

ibz100 said:
Thabk you everybody, I'll try your recommended (re)installation of my fastboot drivers later and get back to you if I have any further updates on my situation.
Big thanks for all the replies guys, I really was taken aback by the sheer effort you put into helping people around here. Rest assured that it doesn't go unappreciated. Keep up the good work!
Click to expand...
Click to collapse
Well I've had my fair share of driver issues. I blame my PC. Anyways, I know how frustrating it can be.
However going back to what I said before, since your ADB drivers are properly installed (being as your device ID showed up and reboot bootloader worked) I wouldn't think it's too far fetched that you already have fastboot drivers installed. Before you try deleting/reinstalling them, I would first boot into the bootloader and run the command "fastboot devices" (no quotes). If you device ID shows up in fastboot, there's no need to mess with your drivers.
Again, the reason ADB "stopped recognizing your device" is because you booted into fastboot mode. While you're in fastboot, you need fastboot commands.
If you boot back into the OS, or into recovery, ADB will recognize your device again. That's how it's supposed to be.
So power down the phone. Hold Volume Down(-) & Power until the phone boots into the bootloader and type;
Code:
fastboot devices
If your ID shows up in a similar fashion to the way it did in your screenshot, you're golden. Let us know how it goes! :good:

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: