Database Users

[Q] Issue With Nexus Q Booting After Flash

Hi there,
I was able to boot the Q fine. I enabled USB debugging, used ADB to reboot into bootloader ran the oem unlock/unlock_accept command successfully. I rebooted and flashed CWM recovery v 6.0.2.7 steelhead. Once this was done, I rebooted into recovery and used adb to push the latest stable release of CM 10.1 to the sdcard. I then flashed this via CWM recovery, and performed a factory reset.
Now that I have rebooted system, it just sits on the cyanogenmod loading splash screen. I left it for over 2 hours at first, then I power cycled device and left it over night. I attempted to go back into recovery, but covering the LED on the top does not seem to result it anything. I power cycled the Q again, and held my hand over the LED from boot to attempt to get into recovery but I am not able to. I also powered device up and waited until the ring LED began to light up, then covered the top LED to see if this allowed to boot into recovery but still no change.
I let the Q boot up once more, and after sitting on the splash screen loading for about 10 minutes, I connected the device back to my PC, and found that adb can see the device. However now that it is running CM 10.1, adb security is enabled and my PC is unauthorized. I am unsure how to proceed at this point. Do I need to try a different PC than the one that was originally used to flash to see if it works (I doubt it will as that wont be authorized either, right?) or am I doing something wrong while trying to get into recovery?
If anyone can shed some light, or assist even getting into recovery, or providing a way to get around the adb authority requirement it would be greatly appreciated.

Ok scratch the above.. I managed to tap on the top LED about 50 times during boot, at which point it turned to red solid LED ring and loaded enough for me to get in using fastboot. I flashed the recovery again, ran a factory reset/wipe cache on it twice, and rebooted. it is now sitting at the home screen ready for me to purchase an OTG USB cable tomorrow and set up cyanogen mod!

[Q] Black screen after attempting to flash image in bootloader.

Hello everyone.
I've looked everywhere to try to find the problem, but I can't seem to find the same situation in any thread.
After making the mistake of wiping the internal storage completely in recovery mode while trying to flash a new ROM, I was left with flashing the recovery image in bootloader mode, sort of as a last resort, even if I had to re-root the device afterwards. I downloaded the "nakasi" image and extracted it in the "platform-tools" folder. After attempting to flash it through fastboot, the device still gave me the message "Booting Failed". I later realized that the contents in the .zip file inside the .tgz was to be extracted as well, so I knew by then it really wasn't flashing anything to the device (newb mistake).
After realizing that and selecting "restart Bootloader" on the device to do it the correct way, the screen suddenly went black before i even hit the power button. The device will not even boot on anymore. I've tried the soft reset method (Power + Vol. Down) for 30 seconds and even took off the back and tried the hard reset method aswell. The device still will not boot. Whenever I try the soft reset method connected via USB, I still hear the usb connect and disconnect sound, so my computer is still recognizing something.
**Right before I decided to flash a new ROM, I remember the device was at 37%, and the total time before the screen went completely black was around an hour and a half, which made me believe that the battery just reached 0%. However, I charged it for about an hour via AC, and i'm still getting the same results. I'm just going to leave it to charge overnight for now and see if it makes a difference.
My question is though, did I just accidentally brick it somehow? Based on the situation, can that really happen, even though I could boot into everything (bootloader, recovery, etc.) just fine before?
**Update 1/9/2014 Left it to charge for nearly 24 hours and it still will not boot up.

[Q] Blank screen software problem (Never dropped and no water damage)

Had my Galaxy S5 G900F for under a year and had it rooted within a week of owning it. There were no problems with the phone at all until I installed lucky patcher. Lucky patcher was not working so I restarted my phone then when it came back on the screen never came back on. I was still receiving text messages and phone calls but the screen was blank and touch was not working. I know for sure that I can still get into Download mode by having it connected to my computer it is detected in Odin (download mode and recovery have a blank screen too). I am unsure If i can get into recovery and even if I got into it I wouldn't be able to see what I am doing.
I am thinking I need to wipe data and cache but I cannot as I cant see recovery.
Is there anything else I can try?

Citrusflow said:
I am thinking I need to wipe data and cache but I cannot as I cant see recovery.
Is there anything else I can try?
Click to expand...
Click to collapse
Do you have Android SDK Installed on your PC and have a custom Recovery on your phone.
If so you can try to Factory rest this way, by connecting your phone to your PC (phone turned on as normal)
Go to the SDK\Tools folder and click monitor.bat the Android Device Monitor window will open (it is slow to load), you should then see your device on the left and a list of folders and files on the right, if you don't make sure the DDMS button is selected and the file explorer tab selected.
Now try the below process
1. Go to the SDK\Platform tools folder, hold down the shift key on your PC and right click the mouse button and select Open Command Window Here
2. Type adb reboot recovery and hit return and wait for the phone to reboot, you can check this in the Android Device Monitor window
The device and files etc will disappear and when booted into recovery appear again, if the device doesn't appear then the rest of this process won't work if it does and you have the device and the list of files and folders again then it should
3. now type adb --wipe_data and hit return, leave the phone alone for a minute or two as you can't see the screen you can't see the progress
4. after a couple of minutes type adb reboot and hit return
The device should hopefully reboot normally, if it doesn't then unplug the USB, pull the battery wait a minute reinsert it and boot normally
This should work as long as you have a custom recovery and Developer Options USB debugging selected on your phone

Okay so I just turned my phone on to try what you said and I didn't even get to try. It wont boot normally now. It has the glowing blue light at the top (Usually on when Samsung logo is on) so I am guessing its in a boot loop. Screen is still black

RSD Lite Flash Failure?

So I pulled out my XT907 to test a new cable I have. The port on the phone has been damaged and it won't charge and won't be recognized by my PC. The port stopped working ages ago during a reset to stock using RSDlite. So when the device tries to boot, it goes straight to the fastboot screen and tells me there was a flash failure. This screen also tells you if you have a USB cable connected. Heres where I am confused. According to this screen, when I plug in a cable, the device registers it as being plugged in (or not plugged in), but the PC won't say anything. Since then I thought I also lost TWRP as a result of the flash failure. Today I found out I was very wrong. I got the device to boot to TWRP without issue, the red Motorola logo even appears at boot which hasn't happened since RSDlite failure. From there I went to the file manager and discovered the whole system is still there. So I am confused as to what is really happening here: 1) Either the USB port on the phone works or it doesn't, depending on what you believe (the phone or the PC) 2) If RSDlite did fail, as fastboot says, how would I even be able to boot to TWRP? 3) Given number 2, if the flash really did fail would it cause the device not to be recognized? 4) Also given number 2, the logo shouldn't even appear period. EDIT: 5) With the device powered off and I plug it into an outlet or my PC, it will power on into fastboot and also says USB connected.

So I decided to dig out the phone and play around with it. I can still get into TWRP so I managed to flash system and boot. Here's the weird part. I thought the phone wouldn't charge. I was wrong. It charges on almost every cable, but my PC will not recognize it in AP fastboot or TWRP. I had forgotten about the 3 button trick, volume up + volume down + power brought me to the recovery menu. I just let it sit there for the few seconds it stays and suddenly the red logo appeared...and the phone booted...normally. So it does charge, but adb or fastboot is a no go. Looks like if I keep this phone, I'll be flashing what I can or am able to with TWRP, on an external SD card if I can't download it to internal.
So it appears only the AP fastboot partition is damaged...every time It boots to it (if I didn't intentionally do it) it says "fastboot flash failure". So since I can't use RSD lite, what are my options?

So the only thing that was damaged was AP fastboot and anything beyond that, including 'charging mode' (thanks for that trick @sd_shadow though it didn't work). For a couple years I thought the clip inside the charging port on the phone was too badly damaged to take a charge or be recognized by my PC. So with intentions of fixing it myself, I put it in a drawer until such time. I knew there was some hope in salvaging it despite the 'flash failure' because every cable I tried, would only charge the phone so no PC means no RSD Lite. I was convinced TWRP would save me and I would find a way to flash everything I needed, but was only able to get as far as the boot.img and system.img. So last night I started to play around with the phone after having plugged it in and noticed the green light in the upper left corner turned on. I spent a few hours flashing and reading and flashing some more before I found another post by @sd_shadow referencing to three buttons, press and hold in this order: volume down, volume up and power. That got me to the stock Motorola recovery screen, which only hangs around for abut 10 seconds, so you have to be quick at selecting an option. I did not select an option, and much to my surprise the phone booted all the way and properly. And that was the only issue. I still had TWRP too. However anytime I needed to reboot, it would go straight to the AP fastboot screen. The 3 buttons bypassed that.
I looked inside the charging port on the phone as I had many times before, and noticed what looked like a piece of foil stuck inside of it. I tried to dig it out but I just managed to push it between the crack in the clip. I plugged it back into my PC and I was even more surprised when it made the familiar connect sound. So I assume that piece of foil was actually a pin, and I managed to seat it just right that the phone charges, is recognized by my PC and i was able to SUCCESSFULLY recover using RSD Lite. We're back in business

J5 2016 (j5xnlte) with broken screen stuck booting to TWRP.

Yesterday I dropped my phone, cracking the screen protector on the right side, a little lower than the middle of the screen. The screen worked fine at the time.
A few hours later I noticed that the bottom of the screen was not working properly. Upon removing the screen protector I saw a barely visible crack, running upwards along the right side of the screen and bending left towards the top.
At this time I connected the phone to my PC and with some fiddling managed to authorize adb, clicking the checkbox to always trust this device. (I had to open an app that enabled screen rotation, so I could get the checkbox and "ok" button on the working part of the screen. I downloaded scrcpy and verified that it worked. I also made an additional backup of my images, although they should be backed up to my NAS.
This morning the screen is almost completely gone. I tried to connect to adb because I remembered I have some recorded calls I want to keep, but I could not get a connection. While trying to accept the connection I inadvertently rebooted the phone to TWRP.
While TWRP is starting I have adb access. I can sort of make out the top left of the TWRP logo on the phone. After 90 seconds the adb connection drops. at the same time the logo disappears and is replaced with some buttons I can't read. some parts of the screen give a haptic feedback when touched. I can disable/enable the screen using the power button, but that's it.
$ adb reboot
$ adb reboot bootloader
$ adb reboot system
$ adb reboot safe mode #(probably not right?)
withing 90 seconds after boot all cause the phone to reboot to recovery
I'm hoping to achieve the following from best, to worst solution:
* use scrcpy while I set up my new phone
* boot to system, so I can transfer files using USB
* make the adb connection stable, to recover files
* copy files directly from the SDcard to Windows, macOS, or linux. (SDcard is formatted as internal)
* copy files during the 90 second window
The last one I can probably manage, but will be tedious to do manually, some automation would be nice.
I'm thinking about a script that I can start from adb, that will move items to a usb otg device. However I can only plug in the usb otg after I disconnect the adb usb cable.
For completeness:
It's a j5xnlte, with LineageOS 17 from here: https://forum.xda-developers.com/t/...al-stable-lineageos-17-1-for-j5-2016.4070629/
I have a 64GB micro SD card formatted as internal storage.
The phone is not encrypted.
The phone is rooted using magisk
The images I used to flash twrp, lineage, magisk and gapps are still on the phone. I could try reflashing them, but I don't know how to do that withing the 90s adb window.
I hope there is something that can be done. If not, thanks for helping this phone last 6 years already.