Hi!
I've been using my Note 4 since shortly after launch, and it's managed to stay afloat for the time being. Unfortunately, the display (I'm assuming backlight LED) crapped out save for a few temporary parts of the screen that work for a few seconds at a time.
The postive side is that I unlocked the bootloader and installed JasmineROM a few months ago, but I don't remember whether or not USB debugging was re-enabled. In addition, the last backup is only 2 months old, which is nice.
So far I've tried multiple methods: ADB to try and use ADB shell to enable usb debugging, but my phone always seems to go offline after a few seconds in recovery. By trial and error, I concluded that the touch aspect of the screen is fine after taking a call successfully, so it's only the display backlight that's broken. I'm wondering if it's feasible to try and memorize the location of the backup password (to log in from a restart) and somehow enable MTP, if anyone has successfully done this before?
Also, does anyone have any suggestions for other ways to go about recovering internal storage data?
Thanks for the help!
Edit: I figured it out! Just happened to have installed a remote control app a while ago that was functional without logging in.
Related
Hello,
I have some issues with my phone behaving strangely and forgetting settings after long power-up times without reboot.
I am on rooted Adam kernel 1.6 knox-free with stock 4.2.2 rom XXUDMH5. I only flashed Adam kernel because whatever i tried, I lost Wifi with stock kernel after I tried CF-Auto-Root (got no clue why, but I am not the only one). Phone normally works quite fine, and after greenifying some apps and disabling some bloatware I normally get battery times of four days+ with moderate use (I am not a power-phoner).
However, after some days of power-on time, the phone starts behaving strangely. I got issues with screen auto brightness not working (screen staying on lowest brightness level all the time), touch screen not reacting properly, apps not starting etc. Two times the phone got hot while charging, apparently something running on heavy duty, with the result that after hours of charging battery power increased only little, if at all. Normally those issues went away after re-booting the phone.
Today, after charging over night, I found the phone with screen on, and looking into power history I found that it had been on for six hours. Apart from the hardware damage this might bring (screen burn-in), the other issue is that after the re-boot, I lost almost all settings. I had to enter passwords again for Samsung account etc., and I had to re-configure everything from keyboard settings, vibration feedback, screen turn-off delay, and remote access features.
When I tried to login to Tomtom live services, I had to enter the password again, too, and then the app told me that my account was already associated with another phone (which it was not, of course). Fortunatelly it allowed me to transfer to my "new" phone.
My questions are: Are those settings (screen turn-off delay, keyboard, remote access etc.) kernel or rom related? Does anybody know where those are stored (some xml file perhaps)? Can I make a backup (I have titanium backup) and restore only those settings if need be?
Many thanks in advance!
One addition: When I started Titanium backup, it notified me that the Android ID has changed and if I want to keep the new one or restore the previous one from a backup. Also, the lockscreen personalization (I replaced that "Live Companion" text) was lost.
So, after being on for more than four or five days the phone is forgetting all settings. Am I really the only one?
I have a GS5 that I dropped and broke the screen. The phone is fully functional except for the screen not displaying or the digitizer working. The phone is rooted on Lollipop and WiFi and USB debug mode are turned on. Bluetooth is turned off. Titanium backup is installed but for some reason wasn't running scheduled backups for some reason.
I have recovered contacts, photos, etc. I have not found a way to recover application data yet.
Based on what I have found, the only options to recover the app data seems to be either dr.fone or replacing the screen at least temporarily. I have a quote from a local shop who said they would recover the data by temporarily installing a screen for $80. I could buy a new screen for less than that, but I don't want to use the phone as there's some damage to the case etc and it's old anyway. I have a new GS5 (a donated one) that I've already got up and running. All I need is the app data. As for dr.fone, it says it can recover the data, but it needs root...which I have.
Does anyone have any idea on how to get dr.fone to work? Or, is there another option I'm not thinking of?
The other thing I've read is that I could simply plug the phone into a HDMI TV and it will automatically display. If so, I would simply need to get a hub compatible with the phone so I could also have my wireless keyboard/mouse installed. Is that a viable option? If so, I could run titanium backup normally and then just copy the data to the new phone.
Hello everyone,
after the pie update 10.0.4.0 I am noticing a strange problem, which I am trying to figure out right now.
It began, that after waking up and picking up my phone, the lock screen pattern was enabled again (I am using the smart lock feature at home when connected to my wifi). On the phone there was a notification like "After a reboot you have to enter the pin again to unlock the phone" or something similiar.
After some time I noticed, that the phone wakes up by itself, the screen comes on and there is no carrier signal ("emergency calls only") for a very short time (maybe a second or two). After that the notification "Checking SD-card" appears. So it seems like the SIM & SD-card would have been unmounted by the system. It can happen everytime and is not related to a specific app.
What I did:
1.) I put the SD-card into my PC and checked it for corruption
2.) Disabled some gallery apps, which I installed last december
3.) Waited for the february 10.0.5.0 update
Unfortunately, without success.
Today I was able to note the exact time the issue happend again (14:51 o'clock) and pulled a logcat. I wanted to read an Focus news article from the notification tray and then it happened. Because I am not sure, if a hardware or software problem is the cause , I need your help:
It would be awesome, if someone could have a look at the attached logcat and give me some hints and advices what might be the problem.
Thank you very much!
I have lost all hope that Google will do anything or I will find a fix by myself with no experience in coding or how android devices work. I've tried my absolute hardest to save my phones photos with no progress. With quarantine happening I've spent a good amount of time looking in to this, here is everything I know.
A simple reboot very rarely fixes it for some people
Rebooting multiple times very rarely fixes it, worked for some people. I've rebooted 100+ times and it didn't
Rebooting to safe mode does nothing, worked in this persons case
You can bypass the lockscreen to another looping screen, shown here, by either brute forcing it, shown in video here. Or by hitting enter and the power button simultaneously when putting in the correct pin, something I found out myself by messing around. From here you can enable USB-Debugging and other settings. Unfortunately, any setting that requires a pin crashes the settings app so you cannot remove the pin from there. In the Google support thread he mentions you can create a new user and control your phone from there but I haven't been able to do it myself
The phone is shown as encrypted in the settings
Other people who were experiencing this issue found a way to replicate it but still no progress from Google has been made
Sideloading the latest OTA does nothing
Phone is only detected in ADB when it is locked, isn't when on the Pixel is starting screen.
Phone is not detected by a PC, shows as MTP USB Device in device manager or another unknown device
Phones storage cannot be accessed in Ubuntu, although it's detected and shown
The confirm prompt that is supposed to show when doing the ADB backup command doesn't show up
ADB pull cannot access the phones files
When on the Pixel is starting screen it's detected as unlocked when using this ADB command
3rd party data recovery softwares successfully install the APK but fail to launch, you can grant app permissions via settings on the phone
Trying to start ANY application with adb commands shows this error message
Uninstalling every app that can be uninstalled from settings does nothing
Disabling/enabling EVERY setting in the settings app did nothing
This bug dates back to FIVE YEARS AGO (Edit: make that seven!)
Deleting locksettings.db or gesture.key on a rooted device with custom recovery or on ADB works, source. REQUIRES AN ALREADY ROOTED DEVICE. Also shown to work here (scroll all the way to the bottom)
Leaving the Pixel is starting screen overnight doesn't work
Leaving the phone on zero battery for multiple days doesn't work
A security update happened the same night the loop started
Locking the phone via Google Find My Device worked for someone in the original support thread which has been locked, multiple threads on the same issue have been made.
Restarting the bootloader in recovery mode worked for someone in the thread too
Disabling live wallpaper in settings does nothing
Someone said that switching to 3 button navigation fixes it, it does not
Could be caused by SoundAssistant/apps with appear on top permissions source
Isn't caused by a wallpaper, i've disabled every wallpaper process and app
Likely caused by corrupt update
Disabling/Force stopping wallpaper related apps changed the wallpaper on the pixel is starting screen to a pink sky with mountain range one
Switching active partitions requires an unlocked device
While on pixel is starting screen, ADB shows the device as unlocked
Aaaand that's all I can remember, there is probably more but these are all that comes to mind. School is starting extremely soon and I am very, very close to taking the hard to swallow factory reset pill but everything I did would've gone to waste, 6 months without a phone I won't get back. So I've come to you guys and am asking if there is ANYTHING I can do that doesn't require a data wipe. Thank you for your time.
For the sources & clickable links, please go to my reddit post (/r/AndroidQuestions/comments/ihcdc0/pixel_4_on_a_lockscreen_loop_for_176_days_what/) add reddit dot com before the link as I cannot post links as a new user.
EDIT: I am now severely ****ed. Sideloaded android 11, didn't fix it. Went to see developper options and fat fingered disable developper options and to re-enable you need your pin which crashes the settings app. Since it wasn't fixed in android 11, september 5 security update AND september 1st google play update I am 100% certain that there will be no fix put out. Resetting later today and never buying a Google phone.
Without flashing a fresh OS I'm not sure if anything can be done. But a clean flash will wipe everything. Google won't help because they don't care.
frankbodyofwater said:
I have lost all hope that Google will do anything or I will find a fix by myself with no experience in coding or how android devices work. I've tried my absolute hardest to save my phones photos with no progress. With quarantine happening I've spent a good amount of time looking in to this, here is everything I know.
A simple reboot very rarely fixes it for some people
Rebooting multiple times very rarely fixes it, worked for some people. I've rebooted 100+ times and it didn't
Rebooting to safe mode does nothing, worked in this persons case
You can bypass the lockscreen to another looping screen, shown here, by either brute forcing it, shown in video here. Or by hitting enter and the power button simultaneously when putting in the correct pin, something I found out myself by messing around. From here you can enable USB-Debugging and other settings. Unfortunately, any setting that requires a pin crashes the settings app so you cannot remove the pin from there. In the Google support thread he mentions you can create a new user and control your phone from there but I haven't been able to do it myself
The phone is shown as encrypted in the settings
Other people who were experiencing this issue found a way to replicate it but still no progress from Google has been made
Sideloading the latest OTA does nothing
Phone is only detected in ADB when it is locked, isn't when on the Pixel is starting screen.
Phone is not detected by a PC, shows as MTP USB Device in device manager or another unknown device
Phones storage cannot be accessed in Ubuntu, although it's detected and shown
The confirm prompt that is supposed to show when doing the ADB backup command doesn't show up
ADB pull cannot access the phones files
When on the Pixel is starting screen it's detected as unlocked when using this ADB command
3rd party data recovery softwares successfully install the APK but fail to launch, you can grant app permissions via settings on the phone
Trying to start ANY application with adb commands shows this error message
Uninstalling every app that can be uninstalled from settings does nothing
Disabling/enabling EVERY setting in the settings app did nothing
This bug dates back to FIVE YEARS AGO (Edit: make that seven!)
Deleting locksettings.db or gesture.key on a rooted device with custom recovery or on ADB works, source. REQUIRES AN ALREADY ROOTED DEVICE. Also shown to work here (scroll all the way to the bottom)
Leaving the Pixel is starting screen overnight doesn't work
Leaving the phone on zero battery for multiple days doesn't work
A security update happened the same night the loop started
Locking the phone via Google Find My Device worked for someone in the original support thread which has been locked, multiple threads on the same issue have been made.
Restarting the bootloader in recovery mode worked for someone in the thread too
Disabling live wallpaper in settings does nothing
Someone said that switching to 3 button navigation fixes it, it does not
Could be caused by SoundAssistant/apps with appear on top permissions source
Isn't caused by a wallpaper, i've disabled every wallpaper process and app
Likely caused by corrupt update
Disabling/Force stopping wallpaper related apps changed the wallpaper on the pixel is starting screen to a pink sky with mountain range one
Switching active partitions requires an unlocked device
While on pixel is starting screen, ADB shows the device as unlocked
Aaaand that's all I can remember, there is probably more but these are all that comes to mind. School is starting extremely soon and I am very, very close to taking the hard to swallow factory reset pill but everything I did would've gone to waste, 6 months without a phone I won't get back. So I've come to you guys and am asking if there is ANYTHING I can do that doesn't require a data wipe. Thank you for your time.
For the sources & clickable links, please go to my reddit post (/r/AndroidQuestions/comments/ihcdc0/pixel_4_on_a_lockscreen_loop_for_176_days_what/) add reddit dot com before the link as I cannot post links as a new user.
Click to expand...
Click to collapse
change your usb default options to "transfer files" in developer options
if you're wanting to connect to adb the way I have been doing it is by setting up adb to connect through wifi. this is the procedure I used to delete digital wellbeing.(improves system performance and battery) Windows 10.
read this thread on how to set up tcpip adb connection
https://developer.android.com/studio/command-line/adb
jalado said:
change your usb default options to "transfer files" in developer options
if you're wanting to connect to adb the way I have been doing it is by setting up adb to connect through wifi. this is the procedure I used to delete digital wellbeing.(improves system performance and battery) Windows 10.
read this thread on how to set up tcpip adb connection
Click to expand...
Click to collapse
I was able to connect to adb via USB but tried connecting through wifi which worked but I dont see why it was needed, deleting digital wellbeing unfortunately didnt do anything. Thanks for replying though
frankbodyofwater said:
I was able to connect to adb via USB but tried connecting through wifi which worked but I dont see why it was needed, deleting digital wellbeing unfortunately didnt do anything. Thanks for replying though
Click to expand...
Click to collapse
what is your issue you're having? you said you weren't able to download your files etc?
what was the problem in the 1st place?
Got one of these zenfone 2 lasers with stock rom that goes into a bootloop any time wifi is turned on, which is now all the time since I tried to use the reset rom option in the power+vol button menu and the first thing it does at boot is attempt to connect to wifi. I've never tried to run any 3rd party os on it ever, though I thought I might try it one day.
I've manage to bypass the out of the box setup a new phone goes through and have access to the settings but I'd rather not repeat the steps to get to this point again, I'm wondering if I should enable debug mode / unlock the bootloader or something before trying to flash any other stock or possibly 3rd party roms.
The phone boots np after a reset but bootloops any time wifi is turned on(crashes at first attempt then never gets past the asus start screen), but I have enough data on my plan to not need wifi, would be nice to continue to use this phone for awhile longer before deciding on a replacement. I think the problem is in the broadcom chip since the bluetooth also died just before finding out this wifi issue.
Appreciate any advice someone might have, thanks!