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.
Related
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!
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
Hi everybody.
TL;DR
Recovery hangs upon booting and fastboot mode doesn't show up ADB interface on my PC. How to flash the phone?
Long version:
I wonder if you can help me. My old faithful Note 3 is badly misbehaving. Yesterday I filled almost all its internal memory with some movies before heading out on a trip, but some time later when I reset the phone after unusually long boot all user settings were lost. Well, something went wrong, couple of hours later there was reset after reset so I wanted to restore previous backup... but couldn't. TWRP was showing error messages (TAR something something, 255) very shortly into restoring process. It couldn't restore backup but also couldn't make new one as well (similar error with TAR and code 255 when trying to backup user data).
Something was very wrong, so I thought maybe I will flash newer TWRP 3.0 and give it a try but suddenly after next reset I couldn't even get into recovery anymore - TWRP gives me black screen after several seconds into booting it. No icons, no reaction to key presses, nothing. Even holding power button does nothing.
Ooooookay, it's time to enter fastboot mode then and flash new recovery manually. So I enter it, connect phone to my laptop and... nothing! No ADB interface. Some kind of samsung driver is installing, but the most important one, for ADB, just doesn't show up. It's really weird. Reinstalling drivers doesn't help, only the same one device that shows up gets different names, but that's it - no ADB interface, and, effectively, I can't flash anything because fastbot and ADB can't see any device. Odin can't see the phone too.
What's going on? Is the internal flash dying or what? But if so what does it have to do with ADB not showing up? Do you have any ideas that I can try out in this situation? I checked my laptop with a tablet that I have on hand and it shows up its ADB interface without problem in fastboot mode even though it's the first time I connect it to this laptop, so laptop and it's system are fine.
If nothing helps then, well, One+ 3, here I come.
EDIT: Problem solved. Turns out f2fs on data partition crashed and therefore TWRP couldn't start at all. I managed to flash Philz CWM via Odin somehow (after messing with drivers for some more time) which told me there is something wrong with /data because it couldn't mount it at all. It couldn't format it either. Fortunately SlimLP managed to start and after throwing up some errors I managed to do factory reset which formatted the internal memory back to ext4. Then flashing TWRP, formatting data back to f2fs, restoring backup and voila! It works again. Good, I'll wait until Note 8 if there ever will be one.
Update 2.- It seems that the flashing I mentioned earlier didn't kill the phone and was just mere coincidence. For now, I'm still trying to find if there is a hardware damage issue.
By the way, currently if I try to charge the phone with my newest cables, it won't charge. The cables are fine, in fact, if I disconnect the battery the phone will demand 0.34amps, but when I connect the battery it instantly drops to 0s (Im using a power bank and an usbmeter, a cheap chinese one), but here is the curious thing... this doesn't happen with my usual cable. With my usual cable it will demand up to 1.4amp so this maybe be an issue of a damaged charging IC.
I bought an x820 and I can confirm some ways to go into EDL, although they may not have the exact same pattern in the X720s
I can confirm that the x820 does go into EDL mode from “vol+, vol-, power”
- It doesn’t need to be turned off to do that.
– It can go into EDL while still being connected to the PC.
– It does that in 9 seconds after the the keys combination.
– It can go into EDL with this method even if the phone is turned off and already connected by cable to the PC
** It doesn’t vibrate when going into EDL in neither case, neither of going from EDL to recovery/fastboot.
This part is curious, because my x722 when was in EDL could go into recovery/fastboot and had an specific vibrating pattern.
The power off + vol up, vol down + cable works too.
Update 1.-
Well, bad news. I did flash something, the devinfo.bin and devcfg.mbn in the flashallpackage... now the phone is "dead" again. It's as dead as it used to be before I installed the qualcomm recovery mode drivers. The thing is now I don't have neither EDL, neither Fastboot, neither recovery.
So pretty much I'm really now in serious big troubles, because now I realize that the one that kept my phone alive were the drivers.
Now I have to see how to extract that info and make the drivers to "see" again my phone, which I imagine won't be easy at all.
So if anyone knows how to force it to be in EDL again, will be much appreciated
(yeah, I already the "vol up + vol dwn + power + cable" )
-----
Hi.
I know there are a lot of threads about this, believe when I tell you that I had opened more than 20 threads and I still have on my browser 5 threads over 10 pages each one, but there is a lot of information (and a lot is repeated and sometimes it even has some issues about clarity of that information).
I had my phone over a year with stock rom and no problems at all, but when I installed lineage 16 (android 9), I got some suddens "deaths", but I was able to return to life by simply going into fastboot.... until last time, I connected my charger when I was 18% and the phone "died". It was warm until battery got drained. I believe the phone got automatically into 9008, although I'm not sure of that yet
(Update to this. I'm sure now that it wasnt on EDL mode at all if PC can't recognize it*)
The thing is, I can still access to my phone. (well, I could when I originally wrote this*)
When I installed the drivers to prepare for the Qfil flash via EDL, suddenly my PC was able to see my phone.
If I pressed Vol up + Power (over 12 seconds), the phone "turn on" into a very primitive recovery
If I pressed Vol dwn + Power (same time), the phone goes into fastboot mode.
It will vibrate once at second 6, then again at second 6.5 (so you can probably call this vibrate twice) and then again at second 12.
Every time the PC will make a notifying sound but you won't see it in device manager because those are not EDL.
You can confirm which mode you are by doing in msdos in your adb folder
adb devices
fastboot devices
In both cases the phone vibrates.
Two vibration for the reset (around the 6 seconds of pressing the buttons), and another vibration after "powering on" (around the 12 seconds), BUT I can't see a thing in the display.
If I just press power, it goes into EDL (or I guess so far)
The recovery is very very primitive. Mount /data, /system and /sdcard was really a pain. I managed to do it with the help of a friend and I recovered my info, so I can really just flash it and everything will be over in less than an hour, but I still want to bring it to life without flashing stock rom.
I tried to use screencap, screenrecord and settings, but they don't seem to be working under that recovery mode.
If I use:
adb reboot recovery
it reboots into recovery again, and unmounts everything that was mounted
adb reboot fastboot
it reboots into EDL mode I suppose (in device manager I can see the 9008 device, althogh I haven't rebooted my PC since the driver installation)
adb reboot
it reboots into EDL
fastboot reboot recovery
it reboots into EDL
fastboot reboot
it reboots into EDL
fastboot boot twrp.img
it boots into primitive recovery mode, and seems slightly different over the vol+up+power recovery mode, even that it is supposed to be the same recovery.
=======
I'm going to explain how to mount /data, /system and /sdcard
In ADB SHELL
-To mount storage-
#.- cd /dev/block/bootdevice
..#.- mount sda10 /sdcard
-To mount system-
#.- cd /dev/block/bootdevice
...#.- mount sde19 /system
-Alternative mode - mount data and/or system- (data has the storage as well)
This is a little bit more complicated, as I couldn't mount /data directly
#.- cd /dev/block/bootdevice
..#.- mount sde34 /sdcard (it can be to another folder)
..#.- cd /sdcard/etc
..#.- cp fstab.qcom /etc/fstab
..#.- mount /data
..#.- mount /system
If you want to copy data using pull, have in mind that mine stuck A LOT while trying to copy large folders containing thousands of pictures (I still can't backup the whatsapp folder, although I have a cloud backup of it, fortunatly)
Assuming you mounted /data, here is the MSDOS command to copy an example folder
---This is an example using the last method to mount /data, it is different if you mount sda10 into /sdcard--
(this is an example folder, you can create it in the windows explorer if you wish)
C:\ADB\md CameraPics
C:\ADB\adb.exe pull /data/media/0/DCIM/. CameraPics
(there is a space between DCIM/. and CameraPics)
=======
I tried "fastboot boot twrp3232.img" but still no image and I touch the screen but it never vibrates.
I tried "fastboot boot boot.img" (the boot.img that comes with the lineage16.zip)
I tried cleaning the dalvik-cache inside /data, but still nothing.
I tried to change some brightness value, but still nothing
I tried to change brightness settings through "settings" in adb shell, but it can't find the service.
I tried dumpsys battery in adb shell, but it can't find the service as well.
I want to try to reset battery value information.
I want to try to "reflash" or better said, "update" the lineage, but TWRP is not working (#.- TWRP does not appear to be running. Waiting for TWRP to start) and I can't find how to start it within adb shell.
Although I may probably be using tsonming flashall before someone may be responding (I will try to finish the other threads before flashing), but I will do it image by image and rebooting, to see which one "fix" the issue.
Thanks in advance and I hope this information can help people to recover their files before debricking the phone.
I have a LG G2 D802 32GB phone. I have been on Lineage 15 for more than 2 years without any security updates. Foolishly, I downloaded and flashed the latest copy of the same operating system. Seemed to go OK but TWRP always booted into recovery, even when 'system' was selected. I flashed the original copy of the operating system and GAPPS back which again went without error messages. This time it booted up with the LG Splash screen followed by the curved line and circles followed by a blank screen then the line and circles/blank screen again repeatedly.
Switching the phone on whilst holding down 'volume up' and plugging the PC USB cable in, gets into download mode followed by the Firmware update screen which sticks at 0%. In the top of the box below are the words 'USER B49' and on the bottom of the box, in red, 'ROOTED' even though I had never succeeded in getting Magisk to root this phone.
The PC has the correct driver and pings but there is no visible entry in File Explorer or the bottom of the screen for safely unplugging it again. This is probably because USB is in Developer Mode but not set for file transfer or PTP etc. with no obvious way of changing this.
Sorry for being so verbose but can anyone suggest how to get the phone working again please?