Database Info

Touchscreen not working, no way into recovery mode.

Hey guys, first time poster here, and i am extremely sorry if there is a board for this device, but i couldn't find one.
I have a Trio Stealth Pro model 7c. I used Clockwork to flash a new rom, CM_NIGHTLY_xxxxxxxx.zip, everything installed fine, but when i boot up, touchscreen dosen't work at all, neither do buttons. I entered recovery mode originally running a .sh script through a terminal emulator, because the power button+volume buttons didn't work for me. I have found a rom that has confirmed working with this tablet, but i have no way of installing it.
Got anything for me guys? Or did i just wash down a tablet?

If debugging was enabled, connect to your PC and on ADB type "adb reboot recovery" and it should place your device in recovery.
Sent from my SII(i777) running AOKP and AoCP Dualbooted

Shawn said:
If debugging was enabled, connect to your PC and on ADB type "adb reboot recovery" and it should place your device in recovery.
Click to expand...
Click to collapse
Okay, that shouldn't be hard, just have to download the SDK.
How am i suppoused to get the other ROM on there though?
Can i just slap it on an SD card, and then flash it with clockwork?

LightRaider said:
Okay, that shouldn't be hard, just have to download the SDK.
How am i suppoused to get the other ROM on there though?
Can i just slap it on an SD card, and then flash it with clockwork?
Click to expand...
Click to collapse
Yup that should work !

nikufellow said:
Yup that should work !
Click to expand...
Click to collapse
Okay, i got the SDK and installed, went into CMD, hit up ADB, and it can't find my device.
Doesn't show up in device manager as well. Android debugging is turned on on my tablet.

LightRaider said:
Okay, i got the SDK and installed, went into CMD, hit up ADB, and it can't find my device.
Doesn't show up in device manager as well. Android debugging is turned on on my tablet.
Click to expand...
Click to collapse
w/ usb connected and table power off, press power + volume up you will see pink led and the computer will detect youre device

[Q] My Nexus5 got bricked

Cannot find my phone using adb/fastboot! Nothing on the screen! :'(
I got the Nexus5 2-3 weeks back, it's a good phone, everything works great!
Today finally I decided to root it and flash some customized roms.
1. My Nexus 5 had like 70% battery. I went to bootloader, unlock and root using below commands.
fastboot-windows.exe oem unlock
fastboot-windows.exe boot image\CF-Auto-Root-hammerhead-hammerhead-nexus5.img
Click to expand...
Click to collapse
2. The phone got rebooted, and then I saw a new Android 4.4. Until now everything looks fine.
Then I went to bootloader again and ran the below command.
fastboot flash recovery recovery-clockwork-6.0.4.4-hammerhead.img (which I got from cwm official site)
Click to expand...
Click to collapse
3. After this step was done, i used volume button to go to "Recovery" (I'm still at bootloader).
Now I used the below command to put the rom on my phone.
adb push myromname.zip /sdcard
Click to expand...
Click to collapse
Then I used volume key and choose "install zip from /sdcard". He was saying "Cannot open directory" twice, then "Cannot find zip file" or something.
Then I was searching the issue on google, and got some answer, and wanna have a try.
I think I touched "power" button accidently. The display was gone (and it never came back). I pushed "power" button again, nothing happened.
I tried "adb devices" and "fastboot devices", nothing worked. (I tried those toolkits, but they need at least "fastboot" working I guess).
When I connected my phone to my PC in device manager I can see "LGE AndroidNet USB Serial Port (COM4)". I don't know what that means.
I tried holding "power" key and "volumn down", but after ~15 seconds it disconnected from PC and then connected back again. Nothing changed on the phone side.
And I holded three buttons together, I got some new device called "QHSUSB_DLOAD". It can't find the driver for this one, and I have no idea what is it.
Does anyone get the same situation? Can someone help me with that? I'm sorry for the pool English! :crying:

njql007 said:
Cannot find my phone using adb/fastboot! Nothing on the screen! :'(
I got the Nexus5 2-3 weeks back, it's a good phone, everything works great!
Today finally I decided to root it and flash some customized roms.
1. My Nexus 5 had like 70% battery. I went to bootloader, unlock and root using below commands.
2. The phone got rebooted, and then I saw a new Android 4.4. Until now everything looks fine.
Then I went to bootloader again and ran the below command.
3. After this step was done, i used volume button to go to "Recovery" (I'm still at bootloader).
Now I used the below command to put the rom on my phone.
Then I used volume key and choose "install zip from /sdcard". He was saying "Cannot open directory" twice, then "Cannot find zip file" or something.
Then I was searching the issue on google, and got some answer, and wanna have a try.
I think I touched "power" button accidently. The display was gone (and it never came back). I pushed "power" button again, nothing happened.
I tried "adb devices" and "fastboot devices", nothing worked. (I tried those toolkits, but they need at least "fastboot" working I guess).
When I connected my phone to my PC in device manager I can see "LGE AndroidNet USB Serial Port (COM4)". I don't know what that means.
I tried holding "power" key and "volumn down", but after ~15 seconds it disconnected from PC and then connected back again. Nothing changed on the phone side.
And I holded three buttons together, I got some new device called "QHSUSB_DLOAD". It can't find the driver for this one, and I have no idea what is it.
Does anyone get the same situation? Can someone help me with that? I'm sorry for the pool English! :crying:
Click to expand...
Click to collapse
I`am afraid your N5 is killed in action (truly bricked), you have to turn it in for warranty/repair and have the motherboard replaced. Nothing you can do anymore afaik

I don't understand your first step...
CF Auto root unlocks the BL so it's not necessary to do it.
Moreover the right steps are the following:
- Windows:
--- Run root-windows.bat
- Linux
--- chmod +x root-linux.sh
--- Run root-linux.sh
- Mac OS X
--- chmod +x root-mac.sh
--- Run root-mac.sh
Click to expand...
Click to collapse

Primokorn said:
I don't understand your first step...
CF Auto root unlocks the BL so it's not necessary to do it.
Moreover the right steps are the following:
Click to expand...
Click to collapse
That`s because some users only start reading OP`s after they got into trouble

If u don't know what you're fully doing, then why risk it
Sent from my Nexus 5 using xda app-developers app

dicecuber said:
If u don't know what you're fully doing, then why risk it
Sent from my Nexus 5 using xda app-developers app
Click to expand...
Click to collapse
I thought I'm following the correct steps …

Thanks all who have replied, I have decided to give it back to Google

Just call for RMA and tell them your phone won't power on--just that. It happens so they won't question it.
Sent from my Nexus 5 using Tapatalk

[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:

[Q] Bootloop - how to recover file?

Hello
My Nexus 5 is all of a sudden stuck in a bootloop, see video at https://plus.google.com/+AlexanderSkwar/posts/YY6VieTVq7Z
I guess, the power button is broken, or something like this. Google will replace the device, but there's one file on the device, which I'd need access to — my Libra database…
Well, would anyone have an idea, how I could get access to it? When I connect USB cable (or use Qi charger), the system boots but then directly reboots. I cannot adb to it. I also get thrown out of the fastboot (power + volume down) menu right away.
Ideas? Anyone? :crying:
Thanks,
Alexander

Do you have a custom recovery installed? do you have adb and fastboot set up in your computer?

alexs77 said:
Hello
My Nexus 5 is all of a sudden stuck in a bootloop, see video at https://plus.google.com/+AlexanderSkwar/posts/YY6VieTVq7Z
I guess, the power button is broken, or something like this. Google will replace the device, but there's one file on the device, which I'd need access to — my Libra database…
Well, would anyone have an idea, how I could get access to it? When I connect USB cable (or use Qi charger), the system boots but then directly reboots. I cannot adb to it. I also get thrown out of the fastboot (power + volume down) menu right away.
Ideas? Anyone? :crying:
Thanks,
Alexander
Click to expand...
Click to collapse
Well maybe removing the power key or fixing it without replacing the motherboard would work, but if you that you will lose your warranty :

el_daYa said:
Do you have a custom recovery installed? do you have adb and fastboot set up in your computer?
Click to expand...
Click to collapse
Yes, I do have a custom recovery setup. Yes, I do have adb and fastboot setup on my computer.
No, I don't get into fastboot or the custom recovery. If I try to, it will reboot right away, as shown on the video. [emoji30]

bitdomo said:
Well maybe removing the power key or fixing it without replacing the motherboard would work, but if you that you will lose your warranty :
Click to expand...
Click to collapse
Uhm, well, losing my warranty is of course also something, I would not want [emoji26]

Try plugging the phone to the computer then run "adb devices" if it recognizes it try to from adb reboot into bootloader or tell it to reboot into recovery. dont know what else to do. It looks like you are going to learn some sleight of hands my friend.

el_daYa said:
Try plugging the phone to the computer then run "adb devices" if it recognizes it try to from adb reboot into bootloader or tell it to reboot into recovery. dont know what else to do. It looks like you are going to learn some sleight of hands my friend.
Click to expand...
Click to collapse
I do know my way around adb
adb devices will only show the device , if it is booted. It does not boot - what happens, is visible in the Google+ post, which contains a video.
I tried plugging it in and it is not shown. Also not with the fastboot command (ie. "sudo fastboot devices" shows nothing. Adb also does not find the device). That is, what I meant with "I cannot adb to the device".

Then I am afraid you'll need assistance from a higher level my friend, sorry I wasn't much help.

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: