Here's the issue, that I've resolved, but I'm looking for a reason why this happened.
Have a Galaxy Note 10.1 (2014 Edition) running Android 5.11, rooted and running xposed.
Arrived home a few days ago and my PIN is no longer recognized to unlock the device. I been using the same pin for months and nothing of any significance had changed on the device. A couple of days earlier I had upgraded busybox and a certificate I use for an email account had expired, but I've restarted the device and used the lock screen pin multiple times after both events. Very strange that the device just stopped recognizing the pin as the correct one.
Anyway I was, fortunately, able to find a way to get into the device and authorize adb connections and took care of the issue (without having to reflash anything).
Anyone have any ideas why the device would just stop allowing the pin to unlock the device?
Mark
mlutzow said:
Here's the issue, that I've resolved, but I'm looking for a reason why this happened.
Have a Galaxy Note 10.1 (2014 Edition) running Android 5.11, rooted and running xposed.
Arrived home a few days ago and my PIN is no longer recognized to unlock the device. I been using the same pin for months and nothing of any significance had changed on the device. A couple of days earlier I had upgraded busybox and a certificate I use for an email account had expired, but I've restarted the device and used the lock screen pin multiple times after both events. Very strange that the device just stopped recognizing the pin as the correct one.
Anyway I was, fortunately, able to find a way to get into the device and authorize adb connections and took care of the issue (without having to reflash anything).
Anyone have any ideas why the device would just stop allowing the pin to unlock the device?
Mark
Click to expand...
Click to collapse
Can you please point me in the direction of a good guide to follow to root my p607t on official 5.1.1?
I've looked all over the place and there's no real confident answer out there and I'm afraid to mess anything up, cause boot loops, ect. I've got lots of experience rooting Androids in the past but this specific T-Mobile modem sounds like it is super picky.
Much thanks to anybody who can help :good:
Galaxy_Guardian_S said:
Can you please point me in the direction of a good guide to follow to root my p607t on official 5.1.1?
I've looked all over the place and there's no real confident answer out there and I'm afraid to mess anything up, cause boot loops, ect. I've got lots of experience rooting Androids in the past but this specific T-Mobile modem sounds like it is super picky.
Much thanks to anybody who can help :good:
Click to expand...
Click to collapse
Sorry for the delay in response, autoroot works great. Just find the closet match to the lt...
Related
Ok, first of all, new to rooting and all that follows. However, I'm not new to forums and if this is in the wrong category, or if I overlooked a similar post, I am sorry. Feel free to redirect me to wherever you see fit. I know just too well how similar posts can be annoying, but I feel like I've exhausted Googlesearching and looked everywhere I can think of.
So, I have a Note II. N7100, Android 4.4.2 and I want to root it. Googlesearching has found me a lot of nice looking ROMs, and besides looks the added functions tempt me. Wont be long until I upgrade to a Note 4 or 5 anyway, figure I might as well. For what its worth, I live in Norway, and AT&T does not exist over here, nor does any other major american carrier. USB debugging was on the entire time.
I got the Odin V3.10, and appropriate clockworksmod files, and thought everything was peaches. Into download mode (after backing up ofc), Odin finds it, I upload everything and Odin says "PASS" in nice, green letters. When it reboots, it looks the same as before, but.. "Unfortunately, SuperUser has stopped", Titanium backup does not work since it apparently isnt rooted. Root Checker says the same. However, when checking for updates my phone displays "The operating system on your device has been modified in an unautorized way. Try downloading software updates using Samsung KIES on your PC, or visit a customer service center."
Read alot about devices having to be unlocked from carrier, however all google searches on "how to check for carrier lock on Note 2" yields numbersequences I have to input into the dialler and dial. None of the sequences give anything other than "Connection problem or invalid MMI code". I honestly dont remember if its carrier locked or not.
I came across an article here on XDA saying that with the later versions of android, KNOX has become an issue when trying to root, but someone had found a way around it. I downloaded MJ5BLPatch.tar.md5, uploaded to my phone via Odin, and here it fails, looses connection with the device and cant reconnect. Phone displays something alon the lines of "Invalid magic code" or the similar in red text.
I am the newb here, looking for help, and if I screwed up big somewhere I am cool with a little flaming. I just want to squeeze this for what use I can before upgrading, and probably rooting that too.
Any help as to how I can root it and load custom ROMs? I appreciate any and all help, sincerely.
Forget that MJ5 bootloader related stuff.
Reflash CWM using Odin and untick auto reboot, run through and reboot manually.
After reboot into recovery flash SuperSu.zip, start supersu after reboot system and disable knox by following the advices from app.
Thank you very much. i feel exceedingly stupid, I had been using the guide found on Note2root.com, when I applied step by step from this guide (http://forum.xda-developers.com/showthread.php?t=2143479) everything worked out. hope this may be of help to anyone having the same issues.
Again, thank you very much for your help.
Hey guys,
I really need to find at least the stock ROM for the new-ish Blu Advance 4.0L (model A010U), because the most recent OTA update unforgivingly bricked mine. Now I want to try to re-flash the stock ROM, but I am also open to custom ROMs, if there are any available. Please help me out! Thanks in advance
I am really surprised no one has replied yet, but again I am facing the same problem and I've been searching the Internet for one month now and I found absolutely nothing for this phone (specifically for version A010U).
So I am going to post a different question in the hopes that someone will read it and help us out:
I have two Blu Advance 4.0 L A010U phones, which are identical except for the color (white and green). They were manufactured a month apart one in 10/2015 and one in 9/2015.
Unfortunately after only a couple of months of light use and for no apparent reason (did not drop it, or wet it, etc) it started going through a boot loop. It will start, show the "bold like us" logo then restart again without making it to the operating system at all. Like I said I've been looking for over a month to find a ROM (stock or modded) to reflash but with no luck. Then I had an idea. Since I have the other identical phone that's working fine, is there a trick I can do using the working phone to create a ROM that I can use in my broken one. By the way, the non working phone will allow me to get into the recovery menu, but unfortunately nothing happens if I wipe the cache or even if I reset to factory defaults.
Anyone knows what's causing that "boot loop", how to fix it and where to find a ROM or even "extract" or "create" one using a working Advance 4.0 L ???
Thank you very much!
Man I wish I knew. I'm kinda a novice. I have the same phone with a similar problem... I downloaded the recent ota update and the first time it said it couldn't unzip it. I tried again and it seemed to work but when it rebooted into recovery it said there was an error... So it won't boot up, it just goes to the screen that says "no command". I'm pretty sure the there's a way to make a copy of the working ROM but since I don't use a PC for anything I've never taken the time to learn the method.
Deuler93 said:
Hey guys,
I really need to find at least the stock ROM for the new-ish Blu Advance 4.0L (model A010U), because the most recent OTA update unforgivingly bricked mine. Now I want to try to re-flash the stock ROM, but I am also open to custom ROMs, if there are any available. Please help me out! Thanks in advance
Click to expand...
Click to collapse
I just got ahold of a couple of these devices myself and am in the process of going through all the in's and out's of them....I'm a Samsung nerd so I haven't messed with something like these in a while but I got one (that was supposedly dead bricked per the lady friend of mine I got them from) at least able to boot into factory mode and recovery via ADB and just as I'm posting this I'm in adb shell going through the device's internal memory.....so we'll see what all I find and can pull out of this one and possibly know enough to post an intelligible reply with solutions next time
The boot looping sounds like a common problem with these and when I get to that point I'm going to get rid of the stock bootanimation.zip ASAP and try something else. I get the idea that these things aren't exactly power houses built for much so the littlest thing or small bug in their coding could lead to this kind of crap happening.
Hopefully you figure yours out before I toss these out the window! lol
Cheers y salud!
---------- Post added at 02:27 AM ---------- Previous post was at 02:20 AM ----------
good.m. said:
Man I wish I knew. I'm kinda a novice. I have the same phone with a similar problem... I downloaded the recent ota update and the first time it said it couldn't unzip it. I tried again and it seemed to work but when it rebooted into recovery it said there was an error... So it won't boot up, it just goes to the screen that says "no command". I'm pretty sure the there's a way to make a copy of the working ROM but since I don't use a PC for anything I've never taken the time to learn the method.
Click to expand...
Click to collapse
Forgot to add a couple things about your post, sorry! I beleive (and I just started digging into this phone) that the no command part is the locked bootloader these phones appear to have. I think it was a combo of holding both volume buttons down from a powered off state then pressing power button on that came up with the option for factory mode or recovery (which led to the sad 'no command' droid), i went into factory mode and theres an option for Tp Upgrade which Im assuming is F/W or something similar but I just hooked up to the PC and in that mode it's reading the internal and external memory of the phone and that's about where I'm at so far.
Wow! I'm surprised this thread is still going.
Anywho, I found a repository that is storing the default ROM for the 4.0L. The files were just added recently. I would have liked to have seen a custom Lollipop ROM made by now, but this device is far too irrelevant to get any attention, unfortunately. Just root and forget, I guess.
I can't wait to try it, thank you! And btw, were you able to get root successfully and if so, how?
Deuler93 said:
Wow! I'm surprised this thread is still going.
Anywho, I found a repository that is storing the default ROM for the 4.0L. The files were just added recently. I would have liked to have seen a custom Lollipop ROM made by now, but this device is far too irrelevant to get any attention, unfortunately. Just root and forget, I guess.
Click to expand...
Click to collapse
Hey Deuler93 -
You have my respect for digging out that BLU ROMs link and sharing with the rest of us. I downloaded the one for my Advance and used SP flash tool to flash the phone that was stuck on a boot-loop. Of course first I had to download and install the MediaTeK drivers for USB connectivity with my PC. Everything worked flawlessly, no glitches what so ever. All these links are easily found and widely available online if anyone is interested I can share here too. I just hope that this boot-loop was due to some software glitch and not hardware failure. Everything seems to work fine for now, keepint my fingers crossed it will NOT happen again.
Well, one less headache to worry about. By the way we're not that far, if you're ever in the Chicago area, I owe you a beer or something. Thank you!
Hi guys !
Thank you very much for the Advance 4.0L Roms.
I have successfuly recovered my phone, but the IMEI got lost.
So, I need to root it in order to recover the IMEI, but I just can´t get success on any method :
Kingroot
Framaroot
Towelroot
is there another way to root it ?
Thank you very much.
I got temporary root using the kingroot apk. But it messed things up and I don't trust it anymore. None of the other mentioned methods worked for me either, maybe try the PC kingroot method
well this helps one thing
good.m. said:
Man I wish I knew. I'm kinda a novice. I have the same phone with a similar problem... I downloaded the recent ota update and the first time it said it couldn't unzip it. I tried again and it seemed to work but when it rebooted into recovery it said there was an error... So it won't boot up, it just goes to the screen that says "no command". I'm pretty sure the there's a way to make a copy of the working ROM but since I don't use a PC for anything I've never taken the time to learn the method.
Click to expand...
Click to collapse
umm. . . when the no command option comes up just press the power button and the rest of options will appear. doesnt exactly solve your problem however unless you have the ZIP file to install, which is what I'm looking for.
What might happen if a ROM is used for another blu phone. ??
A similar phone as well.
Plz advise.
Damn! This thread just keeps going!
I haven't even looked here in a while, so I will bunch my commentary here. I'm also salaried now, so I bought into a OnePlus X (onyx), a more expensive cheapo device, so I do not use the 4.0L anymore.
As for rooting tools, I used the Kingroot APK successfully in the stock environment. I never tried flashing something SuperSU myself, but it could work. Is flashing a SU app possible from the fastboot interface?
And to Steve's question - it is technically possible to flash a ROM for a different device onto your own device, but is considered a bad idea due to the possibility of introducing incompatibilities and missing proprietary requirements. I feel like this would hold especially true to stock ROMs because the manufacturer probably has no interest in supporting anything more than the device that they are manufacturing for. Doing so removes many possible "compatibility" issues from even having to be considered, but I digress. In short, try to find a ROM made for your device and your device only.
Did you find the zip file for the recovery
Marya Wynter said:
umm. . . when the no command option comes up just press the power button and the rest of options will appear. doesnt exactly solve your problem however unless you have the ZIP file to install, which is what I'm looking for.
Click to expand...
Click to collapse
i root my blu advance 4.0l a010u with the kingoroot PC apk, but i got some issues with the lock screen and some apps, so, i need some advice..
i was looking for a zip to use it via recovery but i can't find any..
Recover IMEI
srspinho said:
Hi guys !
Thank you very much for the Advance 4.0L Roms.
I have successfuly recovered my phone, but the IMEI got lost.
So, I need to root it in order to recover the IMEI, but I just can´t get success on any method :
Kingroot
Framaroot
Towelroot
is there another way to root it ?
Thank you very much.
Click to expand...
Click to collapse
You dont need root to recover imei all you have to do is type *#*#84666364#*#* in your dialer and you will be entered in EngineerMode then go into connectivity ,CDS information and radio information phone 1 or 2 then you will see AT+ type something eg.A then backspace and select the first thing you see. Put a space after AT+ and then put you imei code here "IMEI" between these "" You can find your imei by removing your battery it willl be there. After sending command reboot and imei is back.
links are down....check this instead
Hey guys, links here seems to be down .
Maybe this link would be useful for you all... stock firmware can be downloaded and useful help on videos is available too... Enjoy
Hi all
My Note 4 screen has started locking up (i.e. continuing to work in the background and the screen is still responding to system events (SMS notifications etc) but it is not responding to touch.
I have tried several factory resets, after which the screen stays responsive for about 3 or 4 pages, then locks up again.
Background: the phone was rooted about a year ago, to get around the SD card restriction, and has worked fine up until the last week. I gave the phone to a friend who put CWM-based recovery manager and the latest Samsung Android 5.1.1 on it. After setting the phone up successfully and downloading all my apps on to it and getting everything running perfectly, I used CWM to back up the OS image onto the SD card.
Phone worked great for about a day, then started freezing. Wiping the caches / restoring / factory resets and all permutations of these have so far proved ineffective...
Any pointers or suggestions gratefully received :fingers-crossed:
Vaughan
v00n said:
Hi all
My Note 4 screen has started locking up (i.e. continuing to work in the background and the screen is still responding to system events (SMS notifications etc) but it is not responding to touch.
I have tried several factory resets, after which the screen stays responsive for about 3 or 4 pages, then locks up again.
Background: the phone was rooted about a year ago, to get around the SD card restriction, and has worked fine up until the last week. I gave the phone to a friend who put CWM-based recovery manager and the latest Samsung Android 5.1.1 on it. After setting the phone up successfully and downloading all my apps on to it and getting everything running perfectly, I used CWM to back up the OS image onto the SD card.
Phone worked great for about a day, then started freezing. Wiping the caches / restoring / factory resets and all permutations of these have so far proved ineffective...
Any pointers or suggestions gratefully received :fingers-crossed:
Vaughan
Click to expand...
Click to collapse
You do have a Developer Device , right?
Sent from my SM-N910V using Tapatalk
jpcalhoun said:
You do have a Developer Device , right?
Sent from my SM-N910V using Tapatalk
Click to expand...
Click to collapse
Not sure what you mean.. I am not a developer yet, just an interested amateur.
I took the phone in to a repair shop last night, the guy reckoned the problem was down to a poor screen replacement, and they hadn't used the correct bonding cement, and that the screen had separated from the LCD such that capacitance couldn't do its thing.
However if this were the case, the screen would not work at all, even briefly after a system reset.
v00n said:
I took the phone in to a repair shop last night, the guy reckoned the problem was down to a poor screen replacement, and they hadn't used the correct bonding cement, and that the screen had separated from the LCD such that capacitance couldn't do its thing..
Click to expand...
Click to collapse
I should add that the repairer is simply dismantling and rebuilding the phone to see if it's a loose/dirty connector somewhere. He's not going to try to fix it with firmware/software.
v00n said:
I should add that the repairer is simply dismantling and rebuilding the phone to see if it's a loose/dirty connector somewhere. He's not going to try to fix it with firmware/software.
Click to expand...
Click to collapse
The retail version of the Note 4 cannot be rooted, only the Developer Edition of the Note 4 can be rooted and only the Developer Edition has an unlocked bootloader which will allow the installation of a custom recovery like twrp and root. There are a couple of ways to tell if you have a developer device but the fastest is to remove the battery and see if the words "Developer Device" is printed on the phone's casing. If you don't see "Developer Device" printed then you don't have a developer device so you cannot root the phone, you cannot install twrp or other custom recovery and you cannot install a custom ROM.
jpcalhoun said:
The retail version of the Note 4 cannot be rooted, only the Developer Edition of the Note 4 can be rooted and only the Developer Edition has an unlocked bootloader which will allow the installation of a custom recovery like twrp and root. There are a couple of ways to tell if you have a developer device but the fastest is to remove the battery and see if the words "Developer Device" is printed on the phone's casing. If you don't see "Developer Device" printed then you don't have a developer device so you cannot root the phone, you cannot install twrp or other custom recovery and you cannot install a custom ROM.
Click to expand...
Click to collapse
I posted this question in the wrong forum. I am in the UK, I bought the phone directly from Samsung UK the day it came out. It is not a Verizon phone. If I could find a way to delete or lock off this thread I would.
I have now re-posted the question in the main Note 4 forum.
So, my phone reset itself randomly today and I noticed it was unable to turn on Wi-Fi for some reason. I uninstalled an app I've had for a long time called Power Toggles as I know it also can turn on/off the Wi-Fi (to make sure the phone and it weren't fighting) and I got the idea to check the root using Root Checker. Turns out, it failed . . . So something funny is going on.
I have not knowingly taken any type of update but every once in a while, my phone has tried to update and then said it aborted it due to suspected root. Not sure if that's what happened this time around as it happened while it was in my pocket (or at least it was working before I put it away and then later on, it basically stopped working and just seems to continuously reboot for funsies).
I tried rooting my phone using Kingoroot, an LG one click method (both script and GUI) with no luck. I've never had trouble rooting my phone, especially with one click roots before! I reinstalled LG drivers, disabled and re-enabled USB debugger, switched between MTP and PTP connections, etc. I can't seem to get it to recognize the phone. When doing one root method though, it reminded me to accept the RSA fingerprint and I realized that my phone is not asking me for the RSA fingerprint for my computer. I even tried revoking previous fingerprints and no luck there either. So I'm not sure what might be repressing that option but I'm assuming that's the "root" of my rooting issue.
Anyway, does anyone know
a) why my phone would suddenly be acting this way (I think I read someone else had similar symptoms in one of the one click root forums. Tried searching for more mentions but the website seems to be halting and letting me know the issue has been sent to administrators or something to that effect).
b) how do I solve this?
Below is what I'm running:
Android Version
5.0.1
Kernal Version:
3.4.0
Build Number:
LRX21Y
Software Version:
D85021I
Security Software Version:
MDF v1.1 Release 2
I have a TWRP backup made from quite a while ago (possibly a year ago) so i can try and utilize that but I'm not sure if that will do me any good if I can't root my phone first. I don't want to do anything out of desperation that's going to put me into more trouble down the road. At least as of now, my phone boots up correctly (even if it does seem to reset fairly regularly and has a constant battery drain from trying to turn on the wifi).
Any help you guys can give me would be greatly appreciated. Hopefully, I won't just have to buy a new phone . . . Thanks in advance!
Turns out Bluetooth no longer works either. Just thought that might be worth mentioning.
http://forum.xda-developers.com/lg-g3/help/wi-fi-bluetooth-fm-radio-d855-t3284582 Old problem, not much that can be done :|
jbrookley said:
So, my phone reset itself randomly today and I noticed it was unable to turn on Wi-Fi for some reason. I uninstalled an app I've had for a long time called Power Toggles as I know it also can turn on/off the Wi-Fi (to make sure the phone and it weren't fighting) and I got the idea to check the root using Root Checker. Turns out, it failed . . . So something funny is going on.
I have not knowingly taken any type of update but every once in a while, my phone has tried to update and then said it aborted it due to suspected root. Not sure if that's what happened this time around as it happened while it was in my pocket (or at least it was working before I put it away and then later on, it basically stopped working and just seems to continuously reboot for funsies).
I tried rooting my phone using Kingoroot, an LG one click method (both script and GUI) with no luck. I've never had trouble rooting my phone, especially with one click roots before! I reinstalled LG drivers, disabled and re-enabled USB debugger, switched between MTP and PTP connections, etc. I can't seem to get it to recognize the phone. When doing one root method though, it reminded me to accept the RSA fingerprint and I realized that my phone is not asking me for the RSA fingerprint for my computer. I even tried revoking previous fingerprints and no luck there either. So I'm not sure what might be repressing that option but I'm assuming that's the "root" of my rooting issue.
Anyway, does anyone know
a) why my phone would suddenly be acting this way (I think I read someone else had similar symptoms in one of the one click root forums. Tried searching for more mentions but the website seems to be halting and letting me know the issue has been sent to administrators or something to that effect).
b) how do I solve this?
Below is what I'm running:
Android Version
5.0.1
Kernal Version:
3.4.0
Build Number:
LRX21Y
Software Version:
D85021I
Security Software Version:
MDF v1.1 Release 2
I have a TWRP backup made from quite a while ago (possibly a year ago) so i can try and utilize that but I'm not sure if that will do me any good if I can't root my phone first. I don't want to do anything out of desperation that's going to put me into more trouble down the road. At least as of now, my phone boots up correctly (even if it does seem to reset fairly regularly and has a constant battery drain from trying to turn on the wifi).
Any help you guys can give me would be greatly appreciated. Hopefully, I won't just have to buy a new phone . . . Thanks in advance!
Click to expand...
Click to collapse
Well ok, you have that TWRP backup, how about accessing TWRP?
Can you enter recovery?
Does it display your IMEI in system settings, what does it do when you try to enable wifi?
Can you make backup of your current ROM in TWRP, then try to restore the old one, try restoring only system partition if the backup was made on same Android Lollipop 5.0.1. ?
Well, I was able to get into recovery and run an old image but it appears to have the same issue. My IMEI is fine (I did a full backup including IMEI but it had a valid IMEI before as well) so that wasn't the issue. Looking at that other thread someone posted, it looks like my phone is just screwed and this is a well known issue. It looks like people were able to fix it by replacing the motherboard, which is obviously not an option for me. If that's the case, I'm guessing this is my first and last LG phone. I've never had this kind of issue with a Samsung. In fact, I'm now back on an old S4 until I can figure out what to do. Not sure what phone to get at this point.
Natus, to answer your question, the Wi-Fi icon just kinda goes in a loop like it's trying to start it up. Opening up the Wi-Fi menu has it say it's starting up the Wi-Fi but never gets there. Unfortunately, it eats up battery fast, heats it up quickly, and eventually restarts.
I'm open to any other ideas but I'm guessing it's a hardware problem at this point. Thanks for the info, everyone! I do appreciate the help!
If you have any suggestions for a new phone, I'm all ears. Trying to stay out of a payment plan so I'm looking at the Nexus 6P but I'm wondering if there's one coming down the pipeline I might want to hold off for. I'd rather buy directly from the manufacturer than go through AT&T, given the option. Might need to start a new thread for that one though . . . Thanks!
jbrookley said:
Well, I was able to get into recovery and run an old image but it appears to have the same issue. My IMEI is fine (I did a full backup including IMEI but it had a valid IMEI before as well) so that wasn't the issue. Looking at that other thread someone posted, it looks like my phone is just screwed and this is a well known issue. It looks like people were able to fix it by replacing the motherboard, which is obviously not an option for me. If that's the case, I'm guessing this is my first and last LG phone. I've never had this kind of issue with a Samsung. In fact, I'm now back on an old S4 until I can figure out what to do. Not sure what phone to get at this point.
Natus, to answer your question, the Wi-Fi icon just kinda goes in a loop like it's trying to start it up. Opening up the Wi-Fi menu has it say it's starting up the Wi-Fi but never gets there. Unfortunately, it eats up battery fast, heats it up quickly, and eventually restarts.
I'm open to any other ideas but I'm guessing it's a hardware problem at this point. Thanks for the info, everyone! I do appreciate the help!
If you have any suggestions for a new phone, I'm all ears. Trying to stay out of a payment plan so I'm looking at the Nexus 6P but I'm wondering if there's one coming down the pipeline I might want to hold off for. I'd rather buy directly from the manufacturer than go through AT&T, given the option. Might need to start a new thread for that one though . . . Thanks!
Click to expand...
Click to collapse
I'd wait for note 7 or even iphone 7 =]
Hi all! Sorry my first post is begging for help. Anyway.
In the midst of setting up fingerpint recognition on my S7, I was prompted for my PIN. By whatever ****ery, the PIN I have used for months and entered during setup stopped working. I have submitted this to Samsung. This wasn't a problem until my phone died and now requires a PIN instead of print upon unlock.
I have rooted all of my phones previously and searched the whole goddamn forum for a solution. USB debugging is turned off, the phone is not rooted, everything is bone stock. I have the Verizon (Exynos) variant.
I have tried all solutions from the most recent thread I could find but to no avail:
https://forum.xda-developers.com/showthread.php?t=2620456
My only idea is to try to use Heimdall (I'm on Linux) to root and flash stock Android or something in hopes that this might save my user data but replace the OS. When I've tried finding my device using ADB through terminal I only get "unauthorized," presumably I need to unlock my phone first to turn on USB debugging/media transfer. Maybe there is a way to turn on ADB through recovery mode but I'm not sure. Google Device Manager only locks my phone but does not provide a new password. I only need the pictures but Google Photos does not back them up in the background, only if I'm able to unlock the phone and open the app up. I took all precautions to stop this from happening. These pictures are vital to my job. Please help.