[Completed] [SOLVED] Turn on USB debugging with black screen

[Completed] [SOLVED] Turn on USB debugging with black screen - XDA Assist

Hi Everyone,
I'm using a Samsung GT-N7105. It has 16GB of internal memory. It has no external SD card.
A few days ago my phone's screen went black. Everything else works fine, including touch, just that the screen is always completely black.
I took it to a repair centre. After the repair centre ran some tests, (they kept my phone for 2 days,) they confirmed it was the LCD screen problem (i.e. a hardware issue). Since that LCD screen is expensive to repair, I chose not to repair it.
So now I want to install Android Screencast on my phone. I connect my phone to my desktop, and to my surprise I discover that USB debugging isn't enabled anymore!
So I call the repair centre and ask them what software changes they made to my phone. Their response is:
1) The partition table has definitely NOT been altered.
2) "Your Android version has not been upgraded."
3) "We used a special software to format your phone." They declined to tell me what software they used, and they don't seem to know which partitions have been "formatted"! But they did say that "format" was not the same as "factory reset".
(Btw the people at the repair centre are non-native English speakers, whereas my first language is English, so it was hard to ask about technical details.)
Therefore my best guess about the software state of my phone is:
1) It's running stock Android 4.1.2, which it's been running since the first day I bought it
2) The bootloader should have no KNOX nonsense
3) Recovery should be stock recovery
4) A few partitions have been "formatted" to unknown states
5) There are no longer any pattern, PIN, or password locks on my phone. If my phone is on and it's been sitting idle, I just have to tap the home button, then swipe the screen, and it unlocks.
I can reconstruct the partition table of my internal memory if you guys need it. I did an entire dump of mmcblk0 about two months ago.
(Btw the size of that dump of mmcblk0 is 15,758,000,128 bytes, which is significantly less than 16GB, even if you count by 1000s instead of 1024s. Unimportant side question, but does anyone know why?)
**************
My main question is: How do I enable USB debugging ON ANDROID with the black screen restriction?
I've searched the forums, and in thread 2395047 (can't post links yet) the recommendation is to flash CWM recovery to get adb access. But keep in mind that my ultimate goal is to be able to install Android Screencast on my phone, so that I can regain full phone functionality (with the help of an attached computer screen). I don't quite see how adb access via CWM recovery can help me to achieve this goal.
Also, I've never actually used CWM recovery before and don't know how it works. One of my concerns is: Once I have flashed CWM recovery, and after I boot into recovery, do I immediately get adb access just by hooking up to USB cable to the desktop? Or do I first have to select some setting, which would be tough to do with a black screen?
Thanks in advance for all your help!
Ernest
(Note to mods: I accidentally posted this question earlier to xda assist when I wasn't logged in. You can delete the earlier duplicate.)

Hello,
I've been dealing with android for a while and have been a member of XDA for a while. In my time here I've searched for a solution to this issue many times all over the web and XDA but never came up with anything useful.
Of the possible solutions I've found, the most likely possibility is to use an OTG cable and mouse to interface your device but this requires you to see the screen which is not an option for you. adb in this situation is only useful if you want to retrieve data from your device. I do remember finding something on the web that could potentially help you turn on USB debugging but I'm having trouble finding it now. I'll keep looking but can't promise anything. In the meantime, try posting your question in the forum linked below.
http://forum.xda-developers.com/galaxy-note-2/help
If that doesn't help you find answers then try posting your question in the forum linked below.
http://forum.xda-developers.com/android/help
I hope this helps, good luck.

Hi Droidriven!
Thank you so much for taking the time to read and reply to my question.
Guess what, with the help of workdowg, I managed to work out a solution! My saving grace is that I'm running Android 4.1.2 and not one of the newer versions. My understanding is that if I was running one of the newer versions of Android, then I wouldn't even be able to get adb access via CWM recovery, because of the extra security measures. (Although I might be wrong about this point; I am still noob.)
I solved my problem in the following way:
1) Flash CWM recovery via ODIN Download mode
2) Boot into recovery, connect phone to desktop computer, open a command line terminal
3) Type "adb shell" to get a root shell in CWM recovery
4) In that root shell, type all the commands in the last code box at the end of the following post:
http://forum.xda-developers.com/showpost.php?p=63829295&postcount=27
(Much thanks to workdowg for this step)
5) Type "exit 0" to exit the shell in CWM recovery, then type "adb reboot"
6) Wait for my phone to reboot to Android
7) Type "adb devices", and now I see that I have adb connection to Android
After this, I was also able to successfully run Android Screencast with my phone. I can see my screen again!
So now, everyone please help me think of some useful search tags for this post / thread.

ErnestChia said:
Hi Droidriven!
Thank you so much for taking the time to read and reply to my question.
Guess what, with the help of workdowg, I managed to work out a solution! My saving grace is that I'm running Android 4.1.2 and not one of the newer versions. My understanding is that if I was running one of the newer versions of Android, then I wouldn't even be able to get adb access via CWM recovery, because of the extra security measures. (Although I might be wrong about this point; I am still noob.)
I solved my problem in the following way:
1) Flash CWM recovery via ODIN Download mode
2) Boot into recovery, connect phone to desktop computer, open a command line terminal
3) Type "adb shell" to get a root shell in CWM recovery
4) In that root shell, type all the commands in the last code box at the end of the following post:
http://forum.xda-developers.com/showpost.php?p=63829295&postcount=27
(Much thanks to workdowg for this step)
5) Type "exit 0" to exit the shell in CWM recovery, then type "adb reboot"
6) Wait for my phone to reboot to Android
7) Type "adb devices", and now I see that I have adb connection to Android
After this, I was also able to successfully run Android Screencast with my phone. I can see my screen again!
So now, everyone please help me think of some useful search tags for this post / thread.
Click to expand...
Click to collapse
I'll have to remember that, I wasn't aware of the difference in 4.1.2, I've not had to deal with 4.1.2, that's good to know.
Glad you got it going, now see if you can find one of your devices on eBay that is no longer working in one or another but still has a good digitizer and glass, you may find one cheap, then you can use the digitizer+glass from the used one to fix the one you are using.
Sent from my SCH-I535 using Tapatalk

Droidriven said:
Glad you got it going, now see if you can find one of your devices on eBay that is no longer working in one or another but still has a good digitizer and glass, you may find one cheap, then you can use the digitizer+glass from the used one to fix the one you are using.
Click to expand...
Click to collapse
That's a really good idea, which I didn't even consider. (Maybe because I've never meddled with hardware before.)
Thanks!

Related

[Q] custom rom for my tf300t ?

hi,
I'm afraid that installing a custom rom on my asus tf300 would break compatibility
with the keyboard dock. Also mine is azerty .
I'm looking for cyanogenmod in particular, what do you think ?
Also there are other consideration for a custom rom:
- my main motivation to install a custom is to get rid of the bloatware.
I just do not wish to spend time with every added apps to understand their purpose,
and they take space.
- ads. I've installed overcome rom in my previous tablet (unfortunately bricked),
and one thing I really liked, is how lot of ads in apps were filtered.
Too much ads popping from nowhere now , which discourage the use of "free" apps.
- if there's some built in mechanism to limit the risk of bricking that would be nice.
My previous tablet was bricked without any reason, perhaps because I didn't use the original charger.
- somehow all the updates that pop up frequently, nags me.
To summarize, I'm looking for a custom rom, that is compatible with my azerty keyboard dock of the tf300;
and preferably all the criteria mentioned above ( no bloat, blocked ads, anti bricking mechanism, less updates).
Thanks

extrabigmehdi said:
hi,
I'm afraid that installing a custom rom on my asus tf300 would break compatibility
with the keyboard dock. Also mine is azerty .
I'm looking for cyanogenmod in particular, what do you think ?
Also there are other consideration for a custom rom:
- my main motivation to install a custom is to get rid of the bloatware.
I just do not wish to spend time with every added apps to understand their purpose,
and they take space.
- ads. I've installed overcome rom in my previous tablet (unfortunately bricked),
and one thing I really liked, is how lot of ads in apps were filtered.
Too much ads popping from nowhere now , which discourage the use of "free" apps.
- if there's some built in mechanism to limit the risk of bricking that would be nice.
My previous tablet was bricked without any reason, perhaps because I didn't use the original charger.
- somehow all the updates that pop up frequently, nags me.
To summarize, I'm looking for a custom rom, that is compatible with my azerty keyboard dock of the tf300;
and preferably all the criteria mentioned above ( no bloat, blocked ads, anti bricking mechanism, less updates).
Thanks
Click to expand...
Click to collapse
Curious AZERTY Keyboard is french layout? But still ASUS Brand Keyboard Dock correct?

Lummers said:
Curious AZERTY Keyboard is french layout? But still ASUS Brand Keyboard Dock correct?
Click to expand...
Click to collapse
yes. With US keyboard the first letters you see in top left are QWERTY, while for french keyboard it' s AZERTY.
If I set improperly the local, I guess I'll get the Q letter when I type A on keyboard and so on.
I think the layout of keyboard was selected, with first run (choose you language , hour etc...).
My guess is that asus use a "standard rom" despite the different keyboards , but I'm not 100% sure.
Maybe cyanogenmod handle this ?
Annoying, with my samsung P1000 using a custom rom, was more straightforward.

Finally used CROMi-Xenogenesis mod.
It was harder than I thought, with silly unexpected problems from time to time.
For instance, you can't use the bootloader unlocker from asus, if you set the font size of system to max (try if you don't see why).
The dos shell that refused to change dir once in administartor mod , in order to use that fastboot thing ( weird, but worked after typing a drive letter ). Twrp that refused to mound the sd card even with fat32 system (I realized later I could reset while keeping the rom to install).
And finally , no f***** step by step manual, to install the custom rom.
Overcome was more newbie friendly.
No problem with locals, as already announced before by the author of rom.
Now it seems : less bloated, and I have ads blocked .
Will customize more later.

extrabigmehdi said:
Finally used CROMi-Xenogenesis mod.
It was harder than I thought, with silly unexpected problems from time to time.
For instance, you can't use the bootloader unlocker from asus, if you set the font size of system to max (try if you don't see why).
The dos shell that refused to change dir once in administartor mod , in order to use that fastboot thing ( weird, but worked after typing a drive letter ). Twrp that refused to mound the sd card even with fat32 system (I realized later I could reset while keeping the rom to install).
And finally , no f***** step by step manual, to install the custom rom.
Overcome was more newbie friendly.
No problem with locals, as already announced before by the author of rom.
Now it seems : less bloated, and I have ads blocked .
Will customize more later.
Click to expand...
Click to collapse
I'm using Comi-X a well, I didn't know you were looking for that I had a post earlier that I had great help from people on the board.
I'm using Hund's Kernel so I'm overclocking a little on that machine.
No more lag!! It's amazing how much faster it is with the rom.
Please let me know if you need a hand with anything, I'm still a noob but I'll try my best to help you out.

extrabigmehdi said:
Finally used CROMi-Xenogenesis mod.
It was harder than I thought, with silly unexpected problems from time to time.
For instance, you can't use the bootloader unlocker from asus, if you set the font size of system to max (try if you don't see why).
The dos shell that refused to change dir once in administartor mod , in order to use that fastboot thing ( weird, but worked after typing a drive letter ). Twrp that refused to mound the sd card even with fat32 system (I realized later I could reset while keeping the rom to install).
And finally , no f***** step by step manual, to install the custom rom.
Overcome was more newbie friendly.
No problem with locals, as already announced before by the author of rom.
Now it seems : less bloated, and I have ads blocked .
Will customize more later.
Click to expand...
Click to collapse
I would suggest doing the NvFlash for your tablet so it becomes unbrickable now that you have a custom ROM. Link in sig

cmendonc2 said:
I would suggest doing the NvFlash for your tablet so it becomes unbrickable now that you have a custom ROM. Link in sig
Click to expand...
Click to collapse
Unfortunately I just find this nvfash thing just too much confusing.
For miscellaneous reasons:
1) there's no "official" tutorial to restore bricked tablet with nvflash
2) I don't understand what nvflash (or the steps to create "nvflash backup files" ) will exactly change to my current install, if there's a risk of incompatibility/conflict, if I'll need to re-install twrp afterward. Would the bootloader be changed ? Its there a nvflash bootloader ? Unclear.
3) Sorry the part " you will need to flash the AndroidRoot patched custom bootloader" is just Chinese to me.
4) If I install in future , a new rom based on a new android version (and I guess a new bootloader ?) , would I loose the ability to use nvflash ?
5) which file do I need to keep exactly, and where. Let's say I want to save space, do I need to keep blob files etc inside tablet ?
6) ironically there's a risk of bricking my tablet while following this "anti-brick" tool, and with the not so clear tutorial, I have reasons to hesitate.

extrabigmehdi said:
Unfortunately I just find this nvfash thing just too much confusing.
For miscellaneous reasons:
1) there's no "official" tutorial to restore bricked tablet with nvflash
2) I don't understand what nvflash (or the steps to create "nvflash backup files" ) will exactly change to my current install, if there's a risk of incompatibility/conflict, if I'll need to re-install twrp afterward. Would the bootloader be changed ? Its there a nvflash bootloader ? Unclear.
3) Sorry the part " you will need to flash the AndroidRoot patched custom bootloader" is just Chinese to me.
4) If I install in future , a new rom based on a new android version (and I guess a new bootloader ?) , would I loose the ability to use nvflash ?
5) which file do I need to keep exactly, and where. Let's say I want to save space, do I need to keep blob files etc inside tablet ?
6) ironically there's a risk of bricking my tablet while following this "anti-brick" tool, and with the not so clear tutorial, I have reasons to hesitate.
Click to expand...
Click to collapse
1.) Google NvFlash Commands, or read original NvFlash thread, or ask a dev at AndroidRoot
2.)NvFlash files are backups. It doesnt change the BL. The BL just needs to be jellybean
3.) NvFlash is done using a custom version of CWM recovery, so it runs all the scripts for u. You just have to press a few buttons
4.) If you've done NvFlash once, it doesnt matter what you do to your tablet like changing BL
5.) The blob file is about 2 MB, the other backups that are recommended are about 10MB. You wont run out of space. The files that need to be saved are listed in the guide, as well as the way to save them
6.) If you follow the guide down to the word, there is no problem. Unlocking your bootloader and and flashing a rom has the same risk of bricking. If you have any questions ALWAYS ask before proceeding.

cmendonc2 said:
1.) Google NvFlash Commands, or read original NvFlash thread, or ask a dev at AndroidRoot
2.)NvFlash files are backups. It doesnt change the BL. The BL just needs to be jellybean
3.) NvFlash is done using a custom version of CWM recovery, so it runs all the scripts for u. You just have to press a few buttons
4.) If you've done NvFlash once, it doesnt matter what you do to your tablet like changing BL
5.) The blob file is about 2 MB, the other backups that are recommended are about 10MB. You wont run out of space. The files that need to be saved are listed in the guide, as well as the way to save them
6.) If you follow the guide down to the word, there is no problem. Unlocking your bootloader and and flashing a rom has the same risk of bricking. If you have any questions ALWAYS ask before proceeding.
Click to expand...
Click to collapse
I was reading about the NvFlash as it was just recently released.
Couple of questions (sorry if hijacked this thread)
Does it work with TWRP? Or will I have to use CWM?
I've read the NvFlash Guide but I'm still unsure of the necessities.

Lummers said:
I was reading about the NvFlash as it was just recently released.
Couple of questions (sorry if hijacked this thread)
Does it work with TWRP? Or will I have to use CWM?
I've read the NvFlash Guide but I'm still unsure of the necessities.
Click to expand...
Click to collapse
So to get TWRP, u flash a custom CWM, but after you have your backups and blobs, you can flash back TWRP

cmendonc2 said:
1.) Google NvFlash Commands, or read original NvFlash thread, or ask a dev at AndroidRoot
2.)NvFlash files are backups. It doesnt change the BL. The BL just needs to be jellybean
3.) NvFlash is done using a custom version of CWM recovery, so it runs all the scripts for u. You just have to press a few buttons
4.) If you've done NvFlash once, it doesnt matter what you do to your tablet like changing BL
5.) The blob file is about 2 MB, the other backups that are recommended are about 10MB. You wont run out of space. The files that need to be saved are listed in the guide, as well as the way to save them
6.) If you follow the guide down to the word, there is no problem. Unlocking your bootloader and and flashing a rom has the same risk of bricking. If you have any questions ALWAYS ask before proceeding.
Click to expand...
Click to collapse
All right , basically you replace the "recovery tool" with one custom that allows to save the nvflash files (how I interpret it).
I tried to follow the steps but not without problems.
I tried to install "Universal Naked Driver" , but it didn't work.
I uninstalled the asus official driver first , but the universal naked driver wasn't recognized.
Reading some discussions, suggested that it doesn't work with win 7 x64 anyways.
So I re-installed again the "ASUS Pad PC Suite" in order to get the driver again, but also all the stuff I don't care , such like asus clouds and asus sync (if I try to skip, the setup freeze).
Then I followed the step for nvflash, and I got a problem at step where I type "adb pull /data/media/AndroidRoot " . I got the error "device not recognized" .
I retyped again the menu command to generate the blob ; thinking it might help, and all I got is a new wifi error.
So I searched a bit on the web, some discussion suggesting I do the adb command in regular android mode, and after enabling "debug mode".
But enabling the debug mode is not anymore straightforward, you must do some kind of magical trick, where you tap seven time the version build :crying:. I'm happy I didn't install the java sdk, some people suggest to install it in order to use the adb thing :silly:.
So I finally got 8 files .
Reboot in "APX mode" , I get this time the error in windows that the driver is missing. This time I used "universal naked driver " for this,
driver recognized. Reboot of windows, just in case.
Finally I got a frightening black screen, making you think that the tablet might be bricked (they say "blank screen" in tutorial , but I was hoping a white background ).
But fortunately I ended all the nvflash steps successfully.
And then I reflashed TWRP.

extrabigmehdi said:
All right , basically you replace the "recovery tool" with one custom that allows to save the nvflash files (how I interpret it).
I tried to follow the steps but not without problems.
I tried to install "Universal Naked Driver" , but it didn't work.
I uninstalled the asus official driver first , but the universal naked driver wasn't recognized.
Reading some discussions, suggested that it doesn't work with win 7 x64 anyways.
So I re-installed again the "ASUS Pad PC Suite" in order to get the driver again, but also all the stuff I don't care , such like asus clouds and asus sync (if I try to skip, the setup freeze).
Then I followed the step for nvflash, and I got a problem at step where I type "adb pull /data/media/AndroidRoot " . I got the error "device not recognized" .
I retyped again the menu command to generate the blob ; thinking it might help, and all I got is a new wifi error.
So I searched a bit on the web, some discussion suggesting I do the adb command in regular android mode, and after enabling "debug mode".
But enabling the debug mode is not anymore straightforward, you must do some kind of magical trick, where you tap seven time the version build :crying:. I'm happy I didn't install the java sdk, some people suggest to install it in order to use the adb thing :silly:.
So I finally got 8 files .
Reboot in "APX mode" , I get this time the error in windows that the driver is missing. This time I used "universal naked driver " for this,
driver recognized. Reboot of windows, just in case.
Finally I got a frightening black screen, making you think that the tablet might be bricked (they say "blank screen" in tutorial , but I was hoping a white background ).
But fortunately I ended all the nvflash steps successfully.
And then I reflashed TWRP.
Click to expand...
Click to collapse
Woah....
Totally sounds like a little bit of a challenge for people that are new to the android scene..
I'm going to give this a whirl this week sometime and get it backed up.

Im also looking into NVflash, my bootloader is unlocked but I have yet to root and pick a rom. I am also looking for something that will work with a keyboad, I have yet to buy one but my birthday is coming up.

Bricked Jiayu G4T, Help Required

Hallo,
being new to this forum and also new to Android devices, please feel free to move my post into the correct section of the forum if I used the wrong one. The use of the search function is also not unknown to me, however I may not know all terms to be used (rookie) and english still is a foreign language for me.
Anyway, I have a serious problem with my brandnew Jiayu G4T phone and at least I need some help in sorting my thoughts and ideas after several days of browsing through the community.
What I know for sure:
Phone starts booting but stops on the third screen (1st: Jiayul ogo white, 2nd: Jiayu logo green falling in place, 3rd: Jiayu logo white fading).
I am able to boot into stock recovery and into factory mode (mostly chinese characters).
I have access to my phone by adb shell and can look into the directories.
The event occured after an overnight update with weird behavior of the phone (what happened is posted in the assumption section, it was still pretty early and I was clearly not fully awake.
I had the Xposed framework and XPrivacy installed and running. All other apps were pretty common.
In ADB my phone is listed as 0123456789ABCDEF (weird number)
What I do not know / Assumptions:
In /data I see plenty of files telling me that the data wipe from recovery was not successfull, the data belong to previously installed apps.
It seems that I was able to flash a new ROM, in system/app I do not see any of my previously installed apps. Superuser.apk is still present.
I also can access data however only after using su in shell.
I cannot delete the data using rm or wipe data being in [email protected] #, I have no idea why. Read only....
SP Flash tool told me that the flash of the new ROM was successful (red, pink, yellow progress bar followed by green circle). I think that is a good sign.
I also was able to apply ADB sideload for installing a new ROM and the phone told me I was successful. Not sure if this is true considering that my phone still is not booting.
After finding my phone in the morning mobile connections were both down, I think that an Android update was not successful and it might have happened that I restricted this very app with XPrivacy inadvertently.
The phone identifier seems to tell me that XPRivacy might still be active somewhere....
What I think about the next steps:
I think that getting rid of the old data might be the key for success, but I have no idea HOW....
Any thoughts from your side re highly appreciated,
Thomas

Tomcat117 said:
Hallo,
being new to this forum and also new to Android devices, please feel free to move my post into the correct section of the forum if I used the wrong one. The use of the search function is also not unknown to me, however I may not know all terms to be used (rookie) and english still is a foreign language for me.
Anyway, I have a serious problem with my brandnew Jiayu G4T phone and at least I need some help in sorting my thoughts and ideas after several days of browsing through the community.
What I know for sure:
Phone starts booting but stops on the third screen (1st: Jiayul ogo white, 2nd: Jiayu logo green falling in place, 3rd: Jiayu logo white fading).
I am able to boot into stock recovery and into factory mode (mostly chinese characters).
I have access to my phone by adb shell and can look into the directories.
The event occured after an overnight update with weird behavior of the phone (what happened is posted in the assumption section, it was still pretty early and I was clearly not fully awake.
I had the Xposed framework and XPrivacy installed and running. All other apps were pretty common.
In ADB my phone is listed as 0123456789ABCDEF (weird number)
What I do not know / Assumptions:
In /data I see plenty of files telling me that the data wipe from recovery was not successfull, the data belong to previously installed apps.
It seems that I was able to flash a new ROM, in system/app I do not see any of my previously installed apps. Superuser.apk is still present.
I also can access data however only after using su in shell.
I cannot delete the data using rm or wipe data being in [email protected] #, I have no idea why. Read only....
SP Flash tool told me that the flash of the new ROM was successful (red, pink, yellow progress bar followed by green circle). I think that is a good sign.
I also was able to apply ADB sideload for installing a new ROM and the phone told me I was successful. Not sure if this is true considering that my phone still is not booting.
After finding my phone in the morning mobile connections were both down, I think that an Android update was not successful and it might have happened that I restricted this very app with XPrivacy inadvertently.
The phone identifier seems to tell me that XPRivacy might still be active somewhere....
What I think about the next steps:
I think that getting rid of the old data might be the key for success, but I have no idea HOW....
Any thoughts from your side re highly appreciated,
Thomas
Click to expand...
Click to collapse
This is your solution right here (hopefully)
1) If you have not installed the drivers, download, unpack and install drivers http://uloz.to/xwWU1vKw/mtk6589-driver-zip.
2) Download and unpack Stock ROM http://www.ejiayu.com/en/News2-1-100.html.
3) Download and unpack FlashTools http://uloz.to/x6U5ZDKs/spflash3-1316-0-150-zip, and Click on Flash_tool.exe.
4) Click button "Scatter-loading" and select a the MT6589_Android_scatter_emmc.txt in ROM.
5) Turn off your phone and remove the battery!
6) Press F9 (or hit Download button) and connect your phone into the computer via USB data cable.
7) The process will start and a red progress bar will appear after color purple, yellow. And green circles display. Finish. You can now safely disconnect your phone and turn it on.

Egbert
jimmys01 said:
This is your solution right here (hopefully)
Click to expand...
Click to collapse
This actually is a thread I found very early and unfortunately it was not working.
Honestly I assume that Isomehow lost root: How does this sound in the view of my observations and assumptions?
Thomas

[Q] NEC Medias W N-05E root? (dual screen phone)

Hi!
Is there a root available or in the works for the dual-screen NEC Medias W N-05E?
The question has been asked (no answer so far) at the end of a thread under the N-05D but that's a quite different model.
I'd like to create a separate thread for this model to give it more visibility. Hope that's ok!
Thanks in advance!

bohemianRhapsody said:
Hi!
Is there a root available or in the works for the dual-screen NEC Medias W N-05E?
The question has been asked (no answer so far) at the end of a thread under the N-05D but that's a quite different model.
I'd like to create a separate thread for this model to give it more visibility. Hope that's ok!
Thanks in advance!
Click to expand...
Click to collapse
OK! I've made some progress on this: the japanese blogger "dupondroid" appears to say that run_root_shell (hosted at github)
successfully gives temp root. At least, that's my necessarily blurry understanding via google translate. Would any japanese readers here be able to post a better translation?
And a thread at r-2ch dot com links to the github commit in run_root_shell which made that possible: it's commit ID 811be8639aed64c158798a72a1d520a4d21e8b8b "Support N-05E"
Code:
+ { "N-05E", "A1000311", 0xc0094430, 0xc0093ebc }
So it definitely seems temp root is possible.
Sorry for the lack of links but I'm a new user so can't add them for now.

root is easy
bohemianRhapsody said:
OK! I've made some progress on this: the japanese blogger "dupondroid" appears to say that run_root_shell (hosted at github)
successfully gives temp root. At least, that's my necessarily blurry understanding via google translate. Would any japanese readers here be able to post a better translation?
And a thread at r-2ch dot com links to the github commit in run_root_shell which made that possible: it's commit ID 811be8639aed64c158798a72a1d520a4d21e8b8b "Support N-05E"
Code:
+ { "N-05E", "A1000311", 0xc0094430, 0xc0093ebc }
So it definitely seems temp root is possible.
Sorry for the lack of links but I'm a new user so can't add them for now.
Click to expand...
Click to collapse
root is easy via a tool called impactor.
however it's only temporary, I couldn't get /system mounted for rw. so I made a new recovery image to push.
that didn't work either, although I cannot write to recovery there is no error. recoverybkp was successful.
Also I found that the code to enter in recovery mode is based on your imei.
If I remember correctly digit 2,12,13,14 of your imei.
So possible attack vectors are:
1) kernel module to unlock partitions
2) figure out how update.dat files are constructed.
3) write to recovery partition

it0 said:
root is easy via a tool called impactor.
however it's only temporary, I couldn't get /system mounted for rw. so I made a new recovery image to push.
that didn't work either, although I cannot write to recovery there is no error. recoverybkp was successful.
Also I found that the code to enter in recovery mode is based on your imei.
If I remember correctly digit 2,12,13,14 of your imei.
So possible attack vectors are:
1) kernel module to unlock partitions
2) figure out how update.dat files are constructed.
3) write to recovery partition
Click to expand...
Click to collapse
I can't seem to get anything to work i'v tried Impactor did not work just gave me errors also tried run_root_shell but had to have some device.db file with I didn't really figured out, could some one please help?

Lukas_a_1996 said:
I can't seem to get anything to work i'v tried Impactor did not work just gave me errors also tried run_root_shell but had to have some device.db file with I didn't really figured out, could some one please help?
Click to expand...
Click to collapse
I used impactor 0.9.14, you just hook up the phone using microusb and put the phone in usb debugging mode under development options. then selecct "# start telnetd as root on port 22" from the pulldown and click start.
Then using a tool like putty ,telnet to your phone on port 22 (make sure it's connected to you wifi network when you do).
What android version are you running ? 4.1.2 is vulnarable for this attack.

it0 said:
I used impactor 0.9.14, you just hook up the phone using microusb and put the phone in usb debugging mode under development options. then selecct "# start telnetd as root on port 22" from the pulldown and click start.
Then using a tool like putty ,telnet to your phone on port 22 (make sure it's connected to you wifi network when you do).
What android version are you running ? 4.1.2 is vulnarable for this attack.
Click to expand...
Click to collapse
Thanks for the reply . I tried to run the command in impactor but whatever i do i get "Signature bugs unavailable" could it be that i have the wrong ADB drivers installed or is my Impactor setup wrong?
Edit: yeah im running 4.1.2 Build A1001231

You could try if you can just get an adb connection working.
with commands like
adb devices
adb shell
If that works then the rest should work as well.

it0 said:
You could try if you can just get an adb connection working.
with commands like
adb devices
adb shell
If that works then the rest should work as well.
Click to expand...
Click to collapse
All the adb commands basically work but nothing works with impactor i just get error

it0 said:
You could try if you can just get an adb connection working.
with commands like
adb devices
adb shell
If that works then the rest should work as well.
Click to expand...
Click to collapse
Bump!

How to Root Medias N05e
Dear All Pro
Does anyone show me how to root N05e? because there is very few information about that. I want to Swapfile to increase Ram size but it required N05e must be rooted.
So if anyone have any information about N05e, please share. Thanks

nguyenbuulam said:
Dear All Pro
Does anyone show me how to root N05e? because there is very few information about that. I want to Swapfile to increase Ram size but it required N05e must be rooted.
So if anyone have any information about N05e, please share. Thanks
Click to expand...
Click to collapse
There is a way for temp root N05E, basically u can use pm disable command or other su stuff. But u cannot mount system rw right now.

Some news about rooting
If someone in doubt, temp root is 100% working with run_root_shell https://github.com/android-rooting-tools/android_run_root_shell
With this I was able to copy full system, boot and recovery image. But I can't push new boot or recovery.
More than that, almost all fuctions in standard recovery mode (available through "reboot recovery" in root shell) are protected with some code. And it's not 2,11,12,13 numbers of IMEI.
Anyone know where to get this code? Or how to write new boot, recovery image? If we do so, we can get permanent root access =)
Maybe someone have Japanese friends? Search all English web, but maybe in Japan web there are some info.
P.S. with Impactor you only can start talnetd from root, becouse Impactor can't remount /system in rw mode and ro.kernel.qemu=1 option is not working

How to enter recovery mode?
Despite starting this thread, in the end I never did bother to attempt rooting.
Anyway, unfortunately now the phone refuses to boot. Not triggered by anything obvious, haven't installed any new software recently, etc. Just hung one day and then when I removed and re-inserted the battery, it won't get any further than the "docomo" splash screen. I.e. the OS doesn't appear to be getting bootstrapped at all. The "docomo" splash screen appears and disappears then the phone sits there with both screens powered up but blank.
As it happens, I had ADB Debug enabled in the developer options at the time, so I've tried to see if I can adb shell into the device, but no luck. Not surprised as it's clearly not getting far enough into the boot for that to work.
Any other suggestions? From the way it happened I do suspect it might just be hardware failure....
Not even sure how I enter recovery mode -- what are the key combinations for this?

bohemianRhapsody said:
Despite starting this thread, in the end I never did bother to attempt rooting.
Any other suggestions? From the way it happened I do suspect it might just be hardware failure....
Not even sure how I enter recovery mode -- what are the key combinations for this?
Click to expand...
Click to collapse
In recovery mode, clear cache, etc..
To get there hold volume down and power at the same time,then you'll see the broken android then wait/ press vol down a couple of times to see the menu.

GRbit said:
Some news about rooting
If someone in doubt, temp root is 100% working with run_root_shell https://github.com/android-rooting-tools/android_run_root_shell
With this I was able to copy full system, boot and recovery image. But I can't push new boot or recovery.
More than that, almost all fuctions in standard recovery mode (available through "reboot recovery" in root shell) are protected with some code. And it's not 2,11,12,13 numbers of IMEI.
Anyone know where to get this code? Or how to write new boot, recovery image? If we do so, we can get permanent root access =)
Maybe someone have Japanese friends? Search all English web, but maybe in Japan web there are some info.
P.S. with Impactor you only can start talnetd from root, becouse Impactor can't remount /system in rw mode and ro.kernel.qemu=1 option is not working
Click to expand...
Click to collapse
did you ever figure out the recovery keys?

hamishhhhs said:
did you ever figure out the recovery keys?
Click to expand...
Click to collapse
No I didn't(
I'm actually sold this phone and lost interest in the topic.

GRbit said:
No I didn't(
I'm actually sold this phone and lost interest in the topic.
Click to expand...
Click to collapse
do you by chance still have the files you dumped?
Ive teamed with a friend in twitter to try and make a rom for this but I haven't gotten very far

hamishhhhs said:
do you by chance still have the files you dumped?
Ive teamed with a friend in twitter to try and make a rom for this but I haven't gotten very far
Click to expand...
Click to collapse
Sorry, but this was too long time ago. Nothing left

GRbit said:
Sorry, but this was too long time ago. Nothing left
Click to expand...
Click to collapse
how would j be able to get the files from my phone?

hamishhhhs said:
how would j be able to get the files from my phone?
Click to expand...
Click to collapse
I dunno man.
I've already described (in the first post you have quoted) what I achieved with this github repo https://github.com/android-rooting-tools/android_run_root_shell . That's all I've got.

[SOLVED] Android Trojan.Gorilla.AM or Guerrilla.AM on my device OEM launcher...

(NOTE: this post is a duplicate of a similar thread I started on the Android Central user forum)
Hello everyone,
In the continuing saga of the Leagoo T5C i bought before the holidays from GearBest, I've seen the good (the price and overall build quality, along with a reasonably good user experience), the bad (some notifications that I just can't get rid of, among other things), and I now present you the ugly: after watching a review video on YouTube about my device, I learned that it came loaded with a Trojan called "Gorilla.AM"...
***EDIT: apparently, the Trojan's name could actually be "Guerrilla.AM", I'm not sure.***
Needless to say, I did as the tester had, and installed Malwarebytes, which, sure enough, found the exact same Trojan on my device.
You can watch the video here: https://www.youtube.com/watch?v=R5l3z7BvBtk
It so happens that it's embedded in Leagoo's own application launcher, called Sujet (in French; maybe it's called "Subject" in English, I don't know). I can force quit the application, since I use another launcher called Apex (good pick, by the way), but Malwarebytes can't seem to shake the Trojan off my device nonetheless.
A quick search on Google gives very little in the way of information about this malware, but I'd like to be on the safe side, so I came here.
Any contribution would be welcome at this stage.

Hi. I've seen your post on a french-speaking forum but for my own reasons I don't want to help there, too many morons.
Leagoo is well-known for smartphones with built-in spyware/adware. I've had both a Z5 and a M5 and both had such crap in the stock firmware.
This one is new to me but you'll probably have to follow the same steps to get rid of it.
Try
Code:
adb shell pm disable <internal name of that launcher>
first (from a PC connected to the device with ADB - zillions of tutorials available for this)
The internal name can be found by guessing or by using one of the many apps that will show you the information. One is https://play.google.com/store/apps/details?id=com.csdroid.pkg
If that fails, try adding "-k -user 0" to the command line.
If it fails again (denied) then you have no choice but to root your device first, then use this pm command from a root shell or directly delete the folder for "Sujet/Subject" from /system/app or /system/priv-app where you'll find it.

Lannig said:
Hi. I've seen your post on a french-speaking forum but for my own reasons I don't want to help there, too many morons.
Leagoo is well-known for smartphones with built-in spyware/adware. I've had both a Z5 and a M5 and both had such crap in the stock firmware.
This one is new to me but you'll probably have to follow the same steps to get rid of it.
Try
Code:
adb shell pm disable <internal name of that launcher>
first (from a PC connected to the device with ADB - zillions of tutorials available for this)
The internal name can be found by guessing or by using one of the many apps that will show you the information. One is https://play.google.com/store/apps/details?id=com.csdroid.pkg
If that fails, try adding "-k -user 0" to the command line.
If it fails again (denied) then you have no choice but to root your device first, then use this pm command from a root shell or directly delete the folder for "Sujet/Subject" from /system/app or /system/priv-app where you'll find it.
Click to expand...
Click to collapse
Hi,
OK, first off, thanks for the reply. Secondly, as I've stated before, I'm new to Android, and though I know my way around the command line in both Windows, Linux et OS X (not so much macOS: my MacBook Pro is 12-years old...), I suppose there are some things to set up first, before you can actually do what you suggest.
I understand that ADB stands for Android Debug Bridge, so is it an existing functionality in, say, Windows, that you can trigger from the command line, or a third-party software you have to install first?
On the Android side, what action should I take? Any Developer command to enable/disable to let ADB interact with my device the way it's supposed to?

Yes, you need to enable debug mode on your phone too. I could refer you to one of the zillion tutorials available on the net, but here's a summary.
Go to settings > about... (à propos)
Make at least 7 rapid touches on the line that says "build number" or its french translation.
This will make a new settings menu available from the main settings page: developer options
In this new menu, enable USB debugging.
Then you need to install ADB on your Mac and I'm at loss to help you there because I'm totally foreign to Macs. Never used one.
This seems like a good start: https://www.xda-developers.com/install-adb-windows-macos-linux/
Note: you may also try issuing the commands mentioned above from a terminal emulator running directly on your Android device, although I'm told that it's not exactly the same thing protection-wise.
Install this: https://play.google.com/store/apps/details?id=jackpal.androidterm and try typing the commands from the emulator window. If it works, no need for ADB (although having ADB will probably prove useful sooner or later and I encourage you to take the step).
EDIT: forget the guys from Phonandroid, they're brain-damaged beyond help

Lannig said:
Yes, you need to enable debug mode on your phone too. I could refer you to one of the zillion tutorials available on the net, but here's a summary.
Go to settings > about... (à propos)
Make at least 7 rapid touches on the line that says "build number" or its french translation.
This will make a new settings menu available from the main settings page: developer options
In this new menu, enable USB debugging.
Then you need to install ADB on your Mac and I'm at loss to help you there because I'm totally foreign to Macs. Never used one.
This seems like a good start: https://www.xda-developers.com/install-adb-windows-macos-linux/
Note: you may also try issuing the commands mentioned above from a terminal emulator running directly on your Android device, although I'm told that it's not exactly the same thing protection-wise.
Install this: https://play.google.com/store/apps/details?id=jackpal.androidterm and try typing the commands from the emulator window. If it works, no need for ADB (although having ADB will probably prove useful sooner or later and I encourage you to take the step).
EDIT: forget the guys from Phonandroid, they're brain-damaged beyond help
Click to expand...
Click to collapse
OK, thanks for the heads-up; I've already installed a Terminal emulator on the phone, so I'm gonna give it a go in a moment. I concur about Phoneandroid, alas: I've just received flak from one of the moderators because I'd double-posted on the same subject, whereas I'd just posted one thread, in the wrong part of the forum, according to him. Go figure...

OK, please feed back on your attempts, both from terminal emulator and through ADB.
Alas, I suspect that root will be required. It was for me on my Z5 and M5 to get rid of Leagoo's crapware.
Phonandroid is a bunch of losers with bloated egos posing as experts when 2/3 of the replies given are total BS.

"Er, Houston, we've had a problem..."
On Windows: "ADB is not a recognized name for a command applet..."
On OS X: "adb: command not found"
Stumped, I am...

"Er, Houston, we've had a problem..."
On Windows: "ADB is not a recognized name for a command applet..."
On OS X: "adb: command not found"
Stumped, I am...

(Additional question, not quite related: Aida64 indicates that my device runs a 4.4.49 version of the Android kernel, when the current version for Android 7.x is supposed to be 4.4.1; how does that compute--no pun intended--with my issue?)

Missing adb command is because the adb.exe (Windows) or adb (Mac) file is not in the command path. Either make the folder that contains the adb[.exe] file the current folder using the cd command or use whatever context menu for opening a command line window within the currently selected folder works, or even add that folder to the PATH variable. Google "add directory to path" for Windows and MacOS.
No idea about the kernel version. Minor kernel versions may vary within an Android release. Not surprising and most definitely unrelated to your problem. The crapware certainly isn't part of the kernel. It's most likely a system app i.e. a folder within either /system/app or /system/priv-app folders. You can't delete it without root, but you might be able to disable (freeze) it with the commands I gave you.

OK, thanks. I did "cd" to the folder where I had unzipped ADB on Windows (on the Mac, when I tried to open the ADB executable, I got a "cpu not supported" error message in the Terminal, as I feared, since my MBP is 32-bit-only, and most Mac applications nowadays only support 64-bit CPUs), and still got the "adb unrecognized command" error in PowerShell.
The phone was plugged in, and the right USB mode, so I'm still a bit baffled here. Gonna try it again with a different approach. Will keep you posted.
Over and out...

OK, here's what I got: "Error: java.lang.SecurityException: Shell cannot change component state for com.leagoo.launcher3/null to 2"
Basically, from my poor understanding of how Android works, it's root or die, right?

UglyStuff said:
OK, here's what I got: "Error: java.lang.SecurityException: Shell cannot change component state for com.leagoo.launcher3/null to 2"
Basically, from my poor understanding of how Android works, it's root or die, right?
Click to expand...
Click to collapse
I see that this phone has 7.x android. So, a Magisk Systemless flash might work. After rooting your device, get a good launcher integrate it to /system. Then delete your stock launcher all together.
Tell me if this works.
---------- Post added at 01:23 PM ---------- Previous post was at 01:20 PM ----------
rhn19 said:
I see that this phone has 7.x android. So, a Magisk Systemless flash might work. After rooting your device, get a good launcher integrate it to /system. Then delete your stock launcher all together.
Tell me if this works.
Click to expand...
Click to collapse
If you are new to this, use an app from play store for uninstalling and integrating apps.

Hi,
Yes, like I said, I'm a newbie when it comes to Android, so I'll abstain from rooting my device for now, but I'll keep your suggestions under advisement, because I suppose there'll be no other option in the long run. I'm gathering info on how to safely root a device.
I've done countless jailbreaks on iPhones, and it was always absolutely painless, but then, I had better understanding of how iOS works than I have Android, so until I know more about the OS, I'll keep my phone as it is.
Thanks again!

UglyStuff said:
Hi,
Yes, like I said, I'm a newbie when it comes to Android, so I'll abstain from rooting my device for now, but I'll keep your suggestions under advisement, because I suppose there'll be no other option in the long run. I'm gathering info on how to safely root a device.
I've done countless jailbreaks on iPhones, and it was always absolutely painless, but then, I had better understanding of how iOS works than I have Android, so until I know more about the OS, I'll keep my phone as it is.
Thanks again!
Click to expand...
Click to collapse
Jailbreaking vs Rooting is like 5-1 on difficulty level. Because Android is Open source while IOS is not. I would highly suggest you Root it if your phone does not have warranty. After all something that is on /system partition like your launcher will need superuser access to modify it. I cannot think of a way that wont void your warranty.
You can flash TWRP and then boot into aroma-fm but that will void your warranty. Rooting is the preferred option here.

Yeah, well, the phone is brand-new, and still under warranty, but that's not what's holding me back: I'd rather not brick it, most of all, because I need it, if not as my main phone, at least for connectivity.
I've read tutorials on this very website about using TWRP to flash a new baseband, but I'm curious about what firmware to choose, where to download it from to be sure it's not laden with bad stuff, and how sure I'll be to have an operable phone afterwards.

UglyStuff said:
Yeah, well, the phone is brand-new, and still under warranty, but that's not what's holding me back: I'd rather not brick it, most of all, because I need it, if not as my main phone, at least for connectivity.
I've read tutorials on this very website about using TWRP to flash a new baseband, but I'm curious about what firmware to choose, where to download it from to be sure it's not laden with bad stuff, and how sure I'll be to have an operable phone afterwards.
Click to expand...
Click to collapse
Why do you want a new firmware? I don't get you man, do you want to clear out the malware or try a new ROM? Because i think you would have to build a new ROM, there is not one available i guess.

That's the thing: the malware on my phone is part of the application launcher installed by the OEM. In other words, it's embedded inside the ROM. If I root my phone and somehow manage to get rid of this launcher, what's to tell me that Leagoo won't push it silently back onto my device under the disguise of an update?
I don't know what to do here. I understand that based on stock Android, each OEM applies a certain number of modifications to accommodate the hardware it used to build the phone, and since the SoC is brand-new, I gather there aren't many drivers available, unless I leave the current baseline in place.
I'm kinda caught between a rock and a hard place here...

UglyStuff said:
That's the thing: the malware on my phone is part of the application launcher installed by the OEM. In other words, it's embedded inside the ROM. If I root my phone and somehow manage to get rid of this launcher, what's to tell me that Leagoo won't push it silently back onto my device under the disguise of an update?
I don't know what to do here. I understand that based on stock Android, each OEM applies a certain number of modifications to accommodate the hardware it used to build the phone, and since the SoC is brand-new, I gather there aren't many drivers available, unless I leave the current baseline in place.
I'm kinda caught between a rock and a hard place here...
Click to expand...
Click to collapse
If you use malwarebytes after root that thing wont happen. And almost all of the OEMs have a trigger which voids when rooting or flashing firmware. After that the OEM wont give you updates unless you use the A/B partitioning system.

OK, I understand how rooting my phone would void the warranty: after all, it's a substantial change in the phone software, and the OEM can't be made responsible for any mishap that occurs after I've rooted the phone.
What's the A/B partitioning system (I suppose it helps partition your storage space)? I don't have a microSD card installed (I use the slot for my second SIM), but I do have 32 Gb of storage space, minus what's already used up.
Do you know KingRoot? Is it as good and (reasonably) safe a rooting tool as they say it is?

How do I fix "Pixel is Starting" message that's stuck on screen?

Posted this on Google Pixel forum earlier but haven't had much action there, perhaps it's a better question for this community as would like to figure things out sooner than later as I'm currently without a phone.
Hope all reading are healthy and safe...
Pixel 3 on verizon still on Pie (9) with PQ3A.190801.002 build, which I believe is from August 2019. Have not modified phone at all.
One morning the other day turned phone on and stuck with a "Pixel is starting" message. I can access settings and receive calls, when connected to BT in car can make calls too. Cannot receive messages though receive "You have new messages" notifications, got an alert about a VM that I was able to access.
I realize I can likely do a Factory Reset to fix THOUGH I do not want to go down that path without giving it a go trying to at the very least pull some data off the phone (texts, photos, videos). Yes, everything *should* be backed up...
I tried connecting to computer to see if could recognize as drive and transfer files onto computer (Pixel and MTP USB drivers would not install- tried on two laptops running Win7). I know I should probably be updating to Android 10 and am fine doing so, but would like to recover files first.
I mention some potential solutions below I found by some fellow XDA members when searched this topic before posting and am curious if there is anything I should attempt to do before/instead of possibly going with one of the 2 below.
Thanks SO much in advance,
Matt
Possible easier solution:
From _Ra1n_ on xda forums
"I couldn't fix the "Pixel is starting..." issue. Factory Flashing (after removing -w) QQ1A.191205.008 resulted resulted in being stuck at the "G" screen. I flashed the QQ1A.200105.002 factory image (again with -w removed) and was left in the same "Pixel is starting..." state.
Here is where things get interesting:
Over adb I launched the Settings app:
Code:
adb shell am start -a android.settings.SETTINGS
Next, I went into "Security," which prompted for my PIN, and then removed the screen lock. After doing this, I was able to get into /sdcard in the ADB shell, something that was not possible before.
Back in the settings app, I enabled USB File Transfer and copied all my files & photos off. I was also able to launch apps from within the apps list in Settings. This let me export settings/data from other apps that allowed it.
So it seems that entering your PIN in the Settings app also unlocks the phone!
Possible more complicated solution:
From sic0048 on XDA forums
"Is you bootloader unlocked? If so, you can flash the factory image and remove the "-w" command as suggested above, but if your bootloader is not unlocked this will not be an option. If you are on a locked bootloader, you can sideload an OTA image (which really is a full factory image). This will not wipe your phone or do a factory reset. It will however replace your OS with a clean version. Hopefully that fixes the issue. If not, then you will have to do a factory reset in order to "clean out" the problem."

Can you get into Settings? If so, you should be in pretty good shape. It seems like in the "Pixel is starting..." state, USB File Transfer (ie: MTP mode) only works AFTER the phone is unlocked (fingerprint or PIN). The problem is since the lock screen doesn't load, you can't actually unlock. You have to remove your PIN and/or fingerprint (I set "screen lock" to "None") and USB File Transfer should then work.
You should also be able to launch apps from the app list in Settings.
Link to my thread for reference (just in case someone arrives here from a search): https://forum.xda-developers.com/pixel-3-xl/help/stuck-pixel-starting-boot-t4038847

Yes, I can get into settings and just disabled the lock screen. I don't notice any difference but if you are saying that's what it takes to enable MTP then great. Seems like for MTP to even work requires some futzing in Windows, a known MTP issue I guess? I will have to play around on how to enable MTP and then hopefully device manager will recognize on computer now that lock screen disabled. When connecting to computer I'm alternating between use USB for file transfer both with and withOUT USB debugging on, even using USB for charging only, each time it tries to install drivers for Pixel 3, MTP, occasionally ADB. It's never installed Pixel 3, ADB installed once and MTP actually installed once (after disabling lockscreen) but asked for a restart and then didn't install the next time...
As far as launching apps from the settings, I *can* get into the app list but Android 9 does not give an option to open them (unless I need to do something else that's not currently set-up). I know you said this:
"There should be a "Open" shortcut just below the app icon to the left of "Uninstall" (or "Disable" if it is a built-in app)." But I don't see one. If I can get into my backup app, I can hopefully back up my latest SMS which I'm not sure would be possible by just copying things onto computer, such as photos/videos.
Once I get MTP enabled, should I just be able to access my files by opening my phone as a device or will I need to get into ADB to access?
Thank you for your continued help
Matt
_Ra1n_ said:
Can you get into Settings? If so, you should be in pretty good shape. It seems like in the "Pixel is starting..." state, USB File Transfer (ie: MTP mode) only works AFTER the phone is unlocked (fingerprint or PIN). The problem is since the lock screen doesn't load, you can't actually unlock. You have to remove your PIN and/or fingerprint (I set "screen lock" to "None") and USB File Transfer should then work.
You should also be able to launch apps from the app list in Settings.
Link to my thread for reference (just in case someone arrives here from a search): https://forum.xda-developers.com/pixel-3-xl/help/stuck-pixel-starting-boot-t4038847
Click to expand...
Click to collapse

Matt Spo said:
Seems like for MTP to even work requires some futzing in Windows, a known MTP issue I guess?
Click to expand...
Click to collapse
Honestly, it should "just work." I'm not sure why you're having issues. Did USB File Transfer work before you ran into this problem?
Matt Spo said:
As far as launching apps from the settings, I *can* get into the app list but Android 9 does not give an option to open them (unless I need to do something else that's not currently set-up).
Click to expand...
Click to collapse
Ah, I forgot Android 9 didn't have this! If you're familiar with ADB, you can launch apps by activity. You may be able to launch the Pixel Launcher with: "adb shell am start com.google.android.apps.nexuslauncher/.NexusLauncherActivity"
Matt Spo said:
Once I get MTP enabled, should I just be able to access my files by opening my phone as a device or will I need to get into ADB to access?
Click to expand...
Click to collapse
With USB File Transfer enabled you should be able to just access it like you normally would with it plugged into a computer. I was able to, at least.
Matt Spo said:
Thank you for your continued help
Click to expand...
Click to collapse
Of course!

_Ra1n_ said:
Honestly, it should "just work." I'm not sure why you're having issues. Did USB File Transfer work before you ran into this problem?
Click to expand...
Click to collapse
Never attempted USB file transfer before now!
_Ra1n_ said:
Ah, I forgot Android 9 didn't have this! If you're familiar with ADB, you can launch apps by activity. You may be able to launch the Pixel Launcher with: "adb shell am start com.google.android.apps.nexuslauncher/.NexusLauncherActivity"
Click to expand...
Click to collapse
Sounds good, essentially launching the Pixel Launcher will allow me to see all of my apps on the device and open whatever necessary?
_Ra1n_ said:
With USB File Transfer enabled you should be able to just access it like you normally would with it plugged into a computer. I was able to, at least.
Click to expand...
Click to collapse
Sounds great, just need to get USB File Transfer working on computer (trying on 3 diff ones).
_Ra1n_ said:
Of course!
Click to expand...
Click to collapse

Sorry I'm likely not replying to this in sequence. That adb shell Pixel Launcher did not work, gave a type 3 error, does not exist.
MTP is not installing allowing me to access the phone as a device. Perhaps that's because I'm stuck with "Pixel is Starting" on my screen? I can launch ADB though, just trying to figure out to command to launch Google Photos so I can perform cloud backup from there onto my account. Also, would like to perform backup of SMS/MMS. The app I use "SMS Backup & Restore" gave me a shell command to try to launch a backup but did not work. I'm also trying a program called "backuptrans" which I was able to install on phone via ADB but am still trying to figure out a command that will launch the app so I can possibly use for backup of sms/mms/photos.
I am without root if that matters for anything. I have not given up hope of saving these photos/videos, sms/mms but it's getting frustrating trying various commands each night in ADB to launch apps to no avail.
Thanks,
Matt
_Ra1n_ said:
Honestly, it should "just work." I'm not sure why you're having issues. Did USB File Transfer work before you ran into this problem?
Ah, I forgot Android 9 didn't have this! If you're familiar with ADB, you can launch apps by activity. You may be able to launch the Pixel Launcher with: "adb shell am start com.google.android.apps.nexuslauncher/.NexusLauncherActivity"
With USB File Transfer enabled you should be able to just access it like you normally would with it plugged into a computer. I was able to, at least.
Of course!
Click to expand...
Click to collapse
Matt Spo said:
Never attempted USB file transfer before now!
Sounds good, essentially launching the Pixel Launcher will allow me to see all of my apps on the device and open whatever necessary?
Sounds great, just need to get USB File Transfer working on computer (trying on 3 diff ones).
Click to expand...
Click to collapse

Let's take a few steps back. Does the following adb command list the contents of your internal storage?
Code:
adb shell ls /sdard
If so, everything is certainly still there. You can lookup how to use the "adb pull" command to pull files/folders manually. If not, please post any errors that are returned.
The following command should copy the DCIM folder from internal storage onto your computer (where the camera app stores pictures & videos):
Code:
adb pull /sdcard/DCIM
That will copy the DCIM folder into the directory your currently in. You mentioned you were using Windows 7, the command prompt (C:\some\path>) indicates your current directory.
The following commands should open Google Photos and SMS Backup & Restore, respectively:
Code:
adb shell am start -n com.google.android.apps.photos/.home.HomeActivity
Code:
adb shell am start -n com.riteshsahu.SMSBackupRestore/.activities.IntroActivity

Thanks for your continued help, posted responses below. Also, after a lot of searching someone recommended the app "Backuptrans Data Sync," which apparently can backup all I'm looking to (SMS/MMS/Photos/Videos) and I have since installed the .apk to my phone (provided by developer) via ADB and am trying to figure out the exact ADB command to trigger that to open on my phone so I can attempt a connection to their software on PC via WiFi since I cannot get USB working. Supposed it's activity name is "com.backuptrans.datasync.DataSync"
_Ra1n_ said:
Let's take a few steps back. Does the following adb command list the contents of your internal storage?
Code:
adb shell ls /sdard
That gives me error message "closed"
If so, everything is certainly still there. You can lookup how to use the "adb pull" command to pull files/folders manually. If not, please post any errors that are returned.
The following command should copy the DCIM folder from internal storage onto your computer (where the camera app stores pictures & videos):
Code:
adb pull /sdcard/DCIM
That will copy the DCIM folder into the directory your currently in. You mentioned you were using Windows 7, the command prompt (C:\some\path>) indicates your current directory.
The following commands should open Google Photos and SMS Backup & Restore, respectively:
Code:
adb shell am start -n com.google.android.apps.photos/.home.HomeActivity
Gives type 3 error, activity class does not exist
Code:
adb shell am start -n com.riteshsahu.SMSBackupRestore/.activities.IntroActivity
Click to expand...
Click to collapse
Gives type 3 error, activity class does not exist

Matt Spo said:
Thanks for your continued help, posted responses below.
Click to expand...
Click to collapse
Of course! I just wish we were making progress!
The "error: closed" message suggests you may not be using an up-to-date version of the Android Platform Tools (https://developer.android.com/studio/releases/platform-tools). Does the following command produce the same error?:
Code:
adb shell ls /storage
Are you absolutely sure you removed your PIN/passcode and disabled the lock screen? If you go into Settings > Storage, does the phone display the usage breakdown between (images & video, music & audio, ect) as you'd expect it?
The following ADB command will list every "package" currently on the phone:
Code:
adb shell pm list packages
Without getting into too much detail, every app resides in it's own "package." Locate the package for the app you want to launch and attempt to launch the app with the following command:
Code:
adb shell monkey -p app.package.name -c android.intent.category.LAUNCHER 1
Replacing app.package.name with the package you want to launch. For example, the following command should launch Google Photos:
Code:
adb shell monkey -p com.google.android.apps.photos -c android.intent.category.LAUNCHER 1

_Ra1n_ said:
Let's take a few steps back. Does the following adb command list the contents of your internal storage?
Code:
adb shell ls /sdard
If so, everything is certainly still there. You can lookup how to use the "adb pull" command to pull files/folders manually. If not, please post any errors that are returned.
The following command should copy the DCIM folder from internal storage onto your computer (where the camera app stores pictures & videos):
Code:
adb pull /sdcard/DCIM
That will copy the DCIM folder into the directory your currently in. You mentioned you were using Windows 7, the command prompt (C:\some\path>) indicates your current directory.
The following commands should open Google Photos and SMS Backup & Restore, respectively:
Code:
adb shell am start -n com.google.android.apps.photos/.home.HomeActivity
Code:
adb shell am start -n com.riteshsahu.SMSBackupRestore/.activities.IntroActivity
Click to expand...
Click to collapse
_Ra1n_ said:
Of course! I just wish we were making progress!
The "error: closed" message suggests you may not be using an up-to-date version of the Android Platform Tools (https://developer.android.com/studio/releases/platform-tools). Does the following command produce the same error?:
Code:
adb shell ls /storage
I believe I am using the most current version of Android Platform Tools as I just downloaded it within the last week. As far as the command above receiving same "closed" error, no, I get "emulated self"
Are you absolutely sure you removed your PIN/passcode and disabled the lock screen? If you go into Settings > Storage, does the phone display the usage breakdown between (images & video, music & audio, ect) as you'd expect it?
Definitely disabled the lock-screen and fingerprint. Yes, going into Settings>Storage displays the usage breakdown as I would expect it. Fwiw- in "Security & Location" phone is encrypted.
The following ADB command will list every "package" currently on the phone:
Code:
adb shell pm list packages
Without getting into too much detail, every app resides in it's own "package." Locate the package for the app you want to launch and attempt to launch the app with the following command:
Code:
adb shell monkey -p app.package.name -c android.intent.category.LAUNCHER 1
Replacing app.package.name with the package you want to launch. For example, the following command should launch Google Photos:
Code:
adb shell monkey -p com.google.android.apps.photos -c android.intent.category.LAUNCHER 1
Click to expand...
Click to collapse
Yes, that command does display every package name. Trying to launch Google Photos via monkey command above led to "No Activities Found to Run, Monkey Aborted." Same message when trying to launch SMS Backup & Restore.
I don't believe I previously mentioned it, but device is NOT rooted. Imagine you probably figured that, lol.

Matt Spo said:
I believe I am using the most current version of Android Platform Tools as I just downloaded it within the last week. As far as the command above receiving same "closed" error, no, I get "emulated self"
Click to expand...
Click to collapse
I assume the following command returns the same "closed" error as before, then?:
Code:
adb shell ls /storage/emulated
Matt Spo said:
Definitely disabled the lock-screen and fingerprint. Yes, going into Settings>Storage displays the usage breakdown as I would expect it. Fwiw- in "Security & Location" phone is encrypted.
Click to expand...
Click to collapse
This is expected. All modern phones are encrypted whether or not a PIN is set. The PIN, fingerprint, ect. simply protects the key. This enables the user to set a PIN quickly and allows the PIN to be changed without re-encrypting everything with a new key.
Matt Spo said:
I don't believe I previously mentioned it, but device is NOT rooted. Imagine you probably figured that, lol.
Click to expand...
Click to collapse
In theory, that shouldn't matter. Nothing we've tried so far requires root and I recovered without root when this occurred on my phone.
Clearly your phone is reacting differently than mine did when I ran into this. Other than the Pixel 3 / Pixel 3 XL difference, the only other thing I can think of is that I was on Android 10 not Android 9. Without digging through the source code, Android 10 likely handles the device encryption differently.
Unfortunately I'm not really sure what else to suggest. You may have success updating to Android 10. I doubt it fixes the "Pixel is starting" issue though it may unlock the phone and let you pull data off. I would recommend doing this by sideloading a recent OTA instead of doing a System Update on the phone. If you'd like guidance with this, let me know. Google's page containing all of the OTA images & instructions for sideloading them is: https://developers.google.com/android/ota

_Ra1n_ said:
I assume the following command returns the same "closed" error as before, then?:
Code:
adb shell ls /storage/emulated
"Permission denied" is the error I get when I try that command. Does knowing that change anything regarding your thoughts on the matter?
This is expected. All modern phones are encrypted whether or not a PIN is set. The PIN, fingerprint, ect. simply protects the key. This enables the user to set a PIN quickly and allows the PIN to be changed without re-encrypting everything with a new key.
In theory, that shouldn't matter. Nothing we've tried so far requires root and I recovered without root when this occurred on my phone.
Clearly your phone is reacting differently than mine did when I ran into this. Other than the Pixel 3 / Pixel 3 XL difference, the only other thing I can think of is that I was on Android 10 not Android 9. Without digging through the source code, Android 10 likely handles the device encryption differently.
Unfortunately I'm not really sure what else to suggest. You may have success updating to Android 10. I doubt it fixes the "Pixel is starting" issue though it may unlock the phone and let you pull data off. I would recommend doing this by sideloading a recent OTA instead of doing a System Update on the phone. If you'd like guidance with this, let me know. Google's page containing all of the OTA images & instructions for sideloading them is: https://developers.google.com/android/ota
Click to expand...
Click to collapse
Thank you for that link and for all of your efforts thus far. I messaged google tech support with the issue, I guess before I go the sideloading route to install Android 10, which may or may not help me, I'll see what they say. But I will certainly reach out, privately(?) if I need further assistance.

Matt Spo said:
Thank you for that link and for all of your efforts thus far. I messaged google tech support with the issue, I guess before I go the sideloading route to install Android 10, which may or may not help me, I'll see what they say. But I will certainly reach out, privately(?) if I need further assistance.
Click to expand...
Click to collapse
Yeah, wait until you hear back from Google and see what (if anything) they have to say first.
One random thought I had regarding updating to Android 10: Note that on the Verizon model, since the bootloader is locked, you cannot downgrade (as far as I'm aware, hopefully someone can correct me if I'm wrong). I would first try sideloading QQ1A.200105.002 since that is the version I had success recovering my data on.

_Ra1n_ said:
Yeah, wait until you hear back from Google and see what (if anything) they have to say first.
One random thought I had regarding updating to Android 10: Note that on the Verizon model, since the bootloader is locked, you cannot downgrade (as far as I'm aware, hopefully someone can correct me if I'm wrong). I would first try sideloading QQ1A.200105.002 since that is the version I had success recovering my data on.
Click to expand...
Click to collapse
Sorry for delay, been trying some things in the interim, unfortunately none of which have helped. I have now updated my Computer OS from Win7 to Win10 which helps get drivers recognized, both MTP and ADB (MTP was not working with Win7). Everything seems to be "running" properly. Upon doing some research, it seems like MTP connection for transfer has been disabled, possibly with my latest software update, which I believe is November 2019 (Android Pie). I could not find anyone mentioning that MTP/USB transfer has been RE-enabled with Android 10.
Could that be a reason I am getting the messages I am getting for ADB commands or is that a separate entity, unaffected by MTP mode being disabled by Google? It seems to me, that possibly my best/only option at this point, in order to (hopefully) recover SMS/MMS as well as photos/videos is to sideload updated software? If MTP still not enabled in the sideloaded update you mention, thereby having same results with ADB commands, perhaps I could at least have the option like you initially mentioned of opening the apps via settings, something which is not an option with Pie?
As always, thanks for your continued help. Btw, Google Tech support had no information to help my situation!

Matt Spo said:
I have now updated my Computer OS from Win7 to Win10 which helps get drivers recognized, both MTP and ADB (MTP was not working with Win7). Everything seems to be "running" properly.
Click to expand...
Click to collapse
In theory that should make a difference. MTP has been a standard for quite some time. Not sure what is (or was) causing your driver issues (if any). Out of curiosity, do you have another computer (or a friend/family member's computer) you can try plugging the phone into?
Matt Spo said:
Upon doing some research, it seems like MTP connection for transfer has been disabled, possibly with my latest software update, which I believe is November 2019 (Android Pie). I could not find anyone mentioning that MTP/USB transfer has been RE-enabled with Android 10.
Click to expand...
Click to collapse
Interesting, I hand't heard of this. In developer options, what happens when you set "Default USB configuration" to "File Transfer" and then plug the phone in?
Matt Spo said:
Could that be a reason I am getting the messages I am getting for ADB commands or is that a separate entity, unaffected by MTP mode being disabled by Google? It seems to me, that possibly my best/only option at this point, in order to (hopefully) recover SMS/MMS as well as photos/videos is to sideload updated software?
Click to expand...
Click to collapse
Honestly, I'm starting to think that your issue is either A) different than mine in some way or B) The "Pixel is starting..." bug acts differently on Android 9 and Android 10. What we've learned from ADB is that your phone isn't mounting the internal storage. It is possible that Android 10 mounts (and/or unlocks) the Internal storage earlier in the boot process than Android 9. This may be why I was able to access the data from the "Pixel is starting..." screen but you can not.
Unless you can find someone more knowledgeable that has something better to try, I would update to QQ1A.200105.002 (the Feb 2020 update) since that is where I had luck. Since your device has a locked bootloader, you will not be able to revert back to Android 9 (if that matters at this point). Let me know if you need help with this.
Matt Spo said:
If MTP still not enabled in the sideloaded update you mention, thereby having same results with ADB commands, perhaps I could at least have the option like you initially mentioned of opening the apps via settings, something which is not an option with Pie?
Click to expand...
Click to collapse
At this point, I'd say anything is possible.

_Ra1n_ said:
In theory that should make a difference. MTP has been a standard for quite some time. Not sure what is (or was) causing your driver issues (if any). Out of curiosity, do you have another computer (or a friend/family member's computer) you can try plugging the phone into?
It seems like drivers are working, at least according to device manager. I have tried 3 diff windows 10 computers, all with USB-C->USB-A connections. I might try to find someone with a USB-C port so I can go USB-C->USB-C but given the state of the world right now, tough to go to someone's house or have them let me borrow a computer to test.
Interesting, I hand't heard of this. In developer options, what happens when you set "Default USB configuration" to "File Transfer" and then plug the phone in?
Tried that, nothing happened!
Honestly, I'm starting to think that your issue is either A) different than mine in some way or B) The "Pixel is starting..." bug acts differently on Android 9 and Android 10. What we've learned from ADB is that your phone isn't mounting the internal storage. It is possible that Android 10 mounts (and/or unlocks) the Internal storage earlier in the boot process than Android 9. This may be why I was able to access the data from the "Pixel is starting..." screen but you can not.
I was able to pull up directory of what apps were installed on the phone via ADB, is that different? When you say "access the data" do you mean open the individual apps from the settings menu? If so, you previously mentioned that that might be a new Android 10 option?
Unless you can find someone more knowledgeable that has something better to try, I would update to QQ1A.200105.002 (the Feb 2020 update) since that is where I had luck. Since your device has a locked bootloader, you will not be able to revert back to Android 9 (if that matters at this point). Let me know if you need help with this.
If I were to update to that update you mentioned (the following link lists what you mentioned- 105.002 as the January update, with 205.002 being February update), is it just following the steps here? https://developers.google.com/android/ota OR here https://drive.google.com/file/d/0Bz6x7k-VkpUJMlZ1aEliVnhMOHM/view Do I have to sideload each OTA image in sequence from what I'm currently on until I get to the one you mentioned? Thought I saw mention of that somewhere.
At this point, I'd say anything is possible.
Click to expand...
Click to collapse
Before going with the sideloaded OTA updates, I found the following sites which had a bunch of tips for people who have had recent trouble getting various Pixel phones to mount as drives on CPU, I am going to play around with these tips first, perhaps it's glitchy software update(s)? https://support.google.com/pixelphone/thread/8621523?hl=en&msgid=16913445 AND https://www.reddit.com/r/GooglePixel/comments/58mp7o/pixel_xl_wont_connect_to_windows_10_pc/

Matt Spo said:
I was able to pull up directory of what apps were installed on the phone via ADB, is that different? When you say "access the data" do you mean open the individual apps from the settings menu? If so, you previously mentioned that that might be a new Android 10 option?
Click to expand...
Click to collapse
Yes. Even without a security PIN set, the "internal storage" (where app data is stored, where your photos are stored, ect) is still encrypted. Really your PIN only encrypts the key to unlock the internal storage. This is why you can set a PIN after you've used the phone and have a lot of data stored on it without waiting for the data to be encrypted (and change/remove your PIN without waiting for the data to be decrypted/re-encrypted). When a PIN is not set, the phone (should) automatically unlock the storage with the stored key. (I'm over-simplifying a little bit, of course)
My comment about Android 9/10 differences was a (somewhat educated) guess that Android 10 "unlocks" the "always-encrypted" internal storage at a different time than Android 9. If this "unlock" occurs earlier, the internal storage may be accessible once on the "Pixel is starting..." screen. Unfortunately we're fighting with a bug/glitch; none of this is an exact science.
Matt Spo said:
If I were to update to that update you mentioned (the following link lists what you mentioned- 105.002 as the January update, with 205.002 being February update), is it just following the steps here? ... Do I have to sideload each OTA image in sequence from what I'm currently on until I get to the one you mentioned? Thought I saw mention of that somewhere.
Click to expand...
Click to collapse
Yes, follow the steps on Google's OTA page. No, you do not need to flash the OTAs in sequence. The OTAs available on that page are "Full" OTAs; you can jump straight to any Full OTA as long as it is more recent that the version you're currently on.
Matt Spo said:
Before going with the sideloaded OTA updates, I found the following sites which had a bunch of tips for people who have had recent trouble getting various Pixel phones to mount as drives on CPU, I am going to play around with these tips first, perhaps it's glitchy software update(s)?/
Click to expand...
Click to collapse
If the issue was only an MTP issue, you'd still be able to access the data through ADB, something that it doesn't seem like we've been able to accomplish. Since you've tried multiple computers, I don't think this is related.

_Ra1n_ said:
Yes. Even without a security PIN set, the "internal storage" (where app data is stored, where your photos are stored, ect) is still encrypted. Really your PIN only encrypts the key to unlock the internal storage. This is why you can set a PIN after you've used the phone and have a lot of data stored on it without waiting for the data to be encrypted (and change/remove your PIN without waiting for the data to be decrypted/re-encrypted). When a PIN is not set, the phone (should) automatically unlock the storage with the stored key. (I'm over-simplifying a little bit, of course)
My comment about Android 9/10 differences was a (somewhat educated) guess that Android 10 "unlocks" the "always-encrypted" internal storage at a different time than Android 9. If this "unlock" occurs earlier, the internal storage may be accessible once on the "Pixel is starting..." screen. Unfortunately we're fighting with a bug/glitch; none of this is an exact science.
Yes, follow the steps on Google's OTA page. No, you do not need to flash the OTAs in sequence. The OTAs available on that page are "Full" OTAs; you can jump straight to any Full OTA as long as it is more recent that the version you're currently on.
If the issue was only an MTP issue, you'd still be able to access the data through ADB, something that it doesn't seem like we've been able to accomplish. Since you've tried multiple computers, I don't think this is related.
Click to expand...
Click to collapse
I reached back out to Google Tech. Support since realizing my issue seems to stem from the phone NOT being able to be controlled through connected device (computer) but not being allowed to do so, only allowing connection via "this device." They recommended updating software to most recent version of Android 10, which hopefully fixes that connection problem. I guess my decision is either upgrading to the software version you were on, was it - 105.002 (January) or 205.002 (February)? I saw a discrepancy in previous post between software version # and Month. Perhaps that will allow me to do what I need to do, if not I upgrade to the latest version. If I go straight to the latest version, there's no turning back to trying your software, since bootloader locked. Would you recommend starting with your software update and then potentially moving on to most recent if that doesn't work?
Thank you again for all of your help thus far, seems like this could be the home stretch, exhausted all possible scenarios. If upgrading software doesn't work, seems like I am SoL in hopes of backing up.
Matt

Matt Spo said:
I reached back out to Google Tech. Support since realizing my issue seems to stem from the phone NOT being able to be controlled through connected device (computer) but not being allowed to do so, only allowing connection via "this device." They recommended updating software to most recent version of Android 10, which hopefully fixes that connection problem. I guess my decision is either upgrading to the software version you were on, was it - 105.002 (January) or 205.002 (February)? I saw a discrepancy in previous post between software version # and Month.
Click to expand...
Click to collapse
You're correct; I mistyped that a few posts back. The version I had success recovering on was "QQ1A.200105.002" specifically.
Matt Spo said:
Perhaps that will allow me to do what I need to do, if not I upgrade to the latest version. If I go straight to the latest version, there's no turning back to trying your software, since bootloader locked. Would you recommend starting with your software update and then potentially moving on to most recent if that doesn't work?
Click to expand...
Click to collapse
Correct, if you sideload the most recent update you will not be able to sideload an older update with a locked bootloader. My gut instinct would be to update to the version I had success with because we know it worked at least once. Obviously I can't guarantee it will work for you, but I'm really hoping it does. If it doesn't help, updating to the latest version would be the next step.
Matt Spo said:
Thank you again for all of your help thus far, seems like this could be the home stretch, exhausted all possible scenarios. If upgrading software doesn't work, seems like I am SoL in hopes of backing up.
Click to expand...
Click to collapse
Of course! I'm still hopeful this will work out!
Random aside: @Ditamae ran into the exact same issue as me and seems to have had similar success with recovering data. He responded to my original post about this issue: https://forum.xda-developers.com/showpost.php?p=82567069&postcount=5. He indicated he was on the January 2020 update as well.

Database Info

welcome