Related
http://forum.xda-developers.com/archive/index.php/t-644769.html << I got my idea from there.
If you update the
Code:
/data/data/com.android.providers.settings/databases/settings.db
file so that "install_non_market_apps" = 1 instead of 0, you will be able to install non-market apps off of your sdcard or wherever.
This works for me at least, but you'll have to root first.
I ended up editing the file with the SQLite Manager firefox add-on.
But, since that took me a really long time, I'll just upload the edited settings.db for you. (don't forget to make the extention .db instead of .db.txt)
Now, as far as I know, this won't mess anything up... BUT, I'd feel a lot better if someone who knows more about Android would provide some feedback before anyone else tries this. [It works for me, but I'm not sure if any other user-specific settings are kept in that file that I don't know about!]
But, at least for me, I no longer need to use adb to install apks that aren't from the Android Market.
I hope this is useful to someone...
EDIT::
You will lose your settings if you use the attached settings.db.txt file. Your best bet is to pull the file off your phone, edit it with something that understands sqlite3's database format, and then push it back. It's just better that way.
Further EDIT:: As someone pointed out later in this thread, this file unbeknownst to me when I shared it, actually has a unique ID by which phones can be identified on the android market, etc. While this isn't a huge deal, it can lead to some rather strange behavior... my phone for example has started attempting to download apps from the android market all by itself.
So--- if you want to side-load apps, change the variable in the database like I explained above.
Sorry, completely new to android but where would you put this file so it would allow side-loading?
You'd have to replace
Code:
/data/data/com.android.providers.settings/databases/settings.db
with it. You'll have to have your phone rooted first though. Then you'll have to transfer the file to your phone with adb, and you'll then copy it over the existing settings.db file.
Honestly, it might not even be worth the trouble now that attn1 is just doing the whole ROMs.
But make sure you take off the .txt.
This works. Thanks.
For some reason, i'm getting a permissons error regardless that i successfuly rooted my phone...o_o
justince said:
For some reason, i'm getting a permissons error regardless that i successfuly rooted my phone...o_o
Click to expand...
Click to collapse
did you boot the phone and do adb remount with debugging enabled?
USB debugging? Yeah.
What i did was i used the other method to sideload root explorer, took the settings.db.txt, deleted the .txt part and replaced it via root explorer, and now i can sideload whenever...however, when i try to delete any of the att bloatware, its read only o_o fawking att
Can anyone confirm any other way to remove bloatware without flashing the rom?
justince said:
USB debugging? Yeah.
What i did was i used the other method to sideload root explorer, took the settings.db.txt, deleted the .txt part and replaced it via root explorer, and now i can sideload whenever...however, when i try to delete any of the att bloatware, its read only o_o fawking att
Can anyone confirm any other way to remove bloatware without flashing the rom?
Click to expand...
Click to collapse
That's why made the ROM without all that -er- stuff.
attn1 said:
That's why made the ROM without all that -er- stuff.
Click to expand...
Click to collapse
Attn's Rom is ****ing great. many thanks btw
a little help please
a bit confused..
how do i type in this code "/data/data/com.android.providers.settings/databases/settings.db"?
adb /data/data/com.android.providers.settings/databases/settings.db
or something else because that doesnt work.
fluffyarmada said:
I'm not sure if any other user-specific settings are kept in that file that I don't know about!
Click to expand...
Click to collapse
The only issue I see (as an Android newcomer, but with a development background) is that the settings.db contains an android_id that is supposed to be unique (it gets generated when you boot the phone the first time after a reset). So anyone installing your settings.db is going to have the same ID.
I'm sure it won't be an issue for most people but I wonder if there'd be a collision in any apps that are designed to communicate between Android devices? For this reason I'll be tweaking my own settings.db once the phone arrives later today.
Big thanks for posting this though!
Thanks for that, I honestly had no idea. I'm very new to Android. And this was a kludge.
fluffyarmada said:
http://forum.xda-developers.com/archive/index.php/t-644769.html << I got my idea from there.
If you update the
Code:
/data/data/com.android.providers.settings/databases/settings.db
file so that "install_non_market_apps" = 1 instead of 0, you will be able to install non-market apps off of your sdcard or wherever.
This works for me at least, but you'll have to root first.
I ended up editing the file with the SQLite Manager firefox add-on.
But, since that took me a really long time, I'll just upload the edited settings.db for you. (don't forget to make the extention .db instead of .db.txt)
Now, as far as I know, this won't mess anything up... BUT, I'd feel a lot better if someone who knows more about Android would provide some feedback before anyone else tries this. [It works for me, but I'm not sure if any other user-specific settings are kept in that file that I don't know about!]
But, at least for me, I no longer need to use adb to install apks that aren't from the Android Market.
I hope this is useful to someone...
EDIT::
You will lose your settings if you use the attached settings.db.txt file. Your best bet is to pull the file off your phone, edit it with something that understands sqlite3's database format, and then push it back. It's just better that way.
Further EDIT:: As someone pointed out later in this thread, this file unbeknownst to me when I shared it, actually has a unique ID by which phones can be identified on the android market, etc. While this isn't a huge deal, it can lead to some rather strange behavior... my phone for example has started attempting to download apps from the android market all by itself.
So--- if you want to side-load apps, change the variable in the database like I explained above.
Click to expand...
Click to collapse
NOTE: You MUST have root access in order for this to work
sqlite3 is included in the Android SDK tools, so this would be the best way:
COMMON
Enable USB debugging (settings > applications > development > USB Debugging)
adb remount
adb pull /data/data/com.android.providers.settings/databases/settings.db settings.db
Linux/OS X
echo "update secure set value = 1 where name = 'install_non_market_apps';"|./sqlite3 settings.db
WINDOWS
echo update secure set value = 1 where name = 'install_non_market_apps';|sqlite3 settings.db
COMMON
adb push settings.db /data/data/com.android.providers.settings/databases/settings.db
Reboot phone and sideloading works. (thanks fluffyarmada)
I wonder if this might be why google voice fails to install properly for some...
Sent from my HTC Liberty using XDA App
Cobus said:
I wonder if this might be why google voice fails to install properly for some...
Sent from my HTC Liberty using XDA App
Click to expand...
Click to collapse
It is possible. The Google apps all use the android_id, afaik.
Although, I do remember I was never able to get the settings menu to setup the voicemail forwarding... I always had to use the weird GSM code. (The weird number with a bunch of * and # that you have to type in if you follow google's directions.)
judicious said:
a bit confused..
how do i type in this code "/data/data/com.android.providers.settings/databases/settings.db"?
adb /data/data/com.android.providers.settings/databases/settings.db
or something else because that doesnt work.
Click to expand...
Click to collapse
After you've rooted your phone, download the new settings.db into the same folder as where your adb program is. Then type:
adb push /data/data/com.android.providers.settings/databases/settings.db
in that folder while your phone is connect via usb.
I'm not sure if you have to restart your phone into recovery or not. Can someone check on this?
tiga2001 said:
After you've rooted your phone, download the new settings.db into the same folder as where your adb program is. Then type:
adb push /data/data/com.android.providers.settings/databases/settings.db
in that folder while your phone is connect via usb.
I'm not sure if you have to restart your phone into recovery or not. Can someone check on this?
Click to expand...
Click to collapse
Well, it's
Code:
$ adb push /path/to/file/on/computer/settings.db /path/to/file/on/phone/settings.db
So, if your settings.db is in your tools folder, then you can do
Code:
$ adb push settings.db /data/data/com.android.providers.settings/databases/settings.db
what happen to the file download? i cant find it..
judicious said:
what happen to the file download? i cant find it..
Click to expand...
Click to collapse
Please follow the instructions posted by attn1 on reply number 13 to this thread.
I removed the settings.db, because it actually has a bunch of extra settings I didn't know about like a handset specific android_id variable... that caused me a bit of trouble...
But, follow the instructions on reply #13 on this thread, and you'll be able to fix it yourself.
Sorry for the inconvenience.
so if we already used the file, is there anyway to revert it back to default and then change the settings via the method outlined above? or.. if we failed to make a copy of our original settings.db file.. basically am i SOL?
EDIT: nevermind, just rebooted into Clockwork and wiped the phone.
..
oops did not see this thread when commented on the other
poo-tang said:
+1 Maybe a complete system dump from someone could help everyone and Project Sheild users in further development.
I would personally like to start playing around with the Grid application.
Click to expand...
Click to collapse
I've never dumped a system before, but I have my shield and will dump if someone can give me a simple walkthrough. I have adb installed.
Endorn said:
I've never dumped a system before, but I have my shield and will dump if someone can give me a simple walkthrough. I have adb installed.
Click to expand...
Click to collapse
If you have ADB installed already its simple .
Just open a cmd window, make sure your Shield is connected
Code:
adb devices
and then enter this code to copy the hole contents of your devices system folder to your PC (E.G Build.prop,System apps, etc)
Code:
adb pull /system
EDIT - If need some more info, find a ADB tutorial HERE and the correct ADB drivers for Nvidia Shield HERE. After you have the system folder on your PC if you would be so kind to ZIP it and uploaded it somewhere on to the net it would be a great help.
Thanks! I'll dump as soon as I get home from work. Around 5:30 est
Thanks man you rock!
poo-tang said:
If you have ADB installed already its simple .
Just open a cmd window, make sure your Shield is connected
Code:
adb devices
and then enter this code to copy the hole contents of your devices system folder to your PC (E.G Build.prop,System apps, etc)
Code:
adb pull /system
EDIT - If need some more info, find a ADB tutorial HERE and the correct ADB drivers for Nvidia Shield HERE. After you have the system folder on your PC if you would be so kind to ZIP it and uploaded it somewhere on to the net it would be a great help.
Click to expand...
Click to collapse
I'm having trouble getting this to work. I downloaded the adb drivers for shield, but I can't find any shield adb device to install them to.
---------- Post added at 10:41 PM ---------- Previous post was at 10:36 PM ----------
Endorn said:
I'm having trouble getting this to work. I downloaded the adb drivers for shield, but I can't find any shield adb device to install them to.
Click to expand...
Click to collapse
I think the problem is USB debugging isn't turned on, but I can't find the setting on the shield anywhere... any thoughts?
usb debugging is usually in settings under developer options, alternatively you could use a file manager like astro and simply navigate to /system to copy and paste the files to your memory card. If adb is giving you trouble if you could pull system/app and system/framework that is the main thing we need. Thanks so much man!
try going the the about device page and tapping the build number 10? times
checked just now, go to settings>about shield then tap build number to unhide developer settings.
chevyowner said:
try going the the about device page and tapping the build number 10? times
checked just now, go to settings>about shield then tap build number to unhide developer settings.
Click to expand...
Click to collapse
hahaha what a crazy way to hide it. That worked thanks, pulling the system now.
Endorn said:
hahaha what a crazy way to hide it. That worked thanks, pulling the system now.
Click to expand...
Click to collapse
Nice work Thanks.
Let the theaming, modding, porting begin
Sent from my C6603 using Tapatalk 2
poo-tang said:
Nice work Thanks.
Let the theaming, modding, porting begin
Sent from my C6603 using Tapatalk 2
Click to expand...
Click to collapse
I'm going to make a post in the dev section, but figured I'd paste this here first. Enjoy!
http://www.androidfilehost.com/?fid=23060877489997514
You rock mate! Diving in now!
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.
Can anyone confirm that this 9.0 pie update breaks all call recording app from the play store. Thanks for your feedback.
Updated to Android 9 today and boldbeast no longer works, it will record my voice but not that of the call )-: I am considering root now to get the feature back as i did find it useful.
Update: found this on the play store https://play.google.com/store/apps/details?id=net.jroot3d.joneplustools&hl=en_GB
Its all working fine now as it enables the oneplus6 built in recorder.
Thanks
But that also means that it wouldn't work without root like myself. Right?
Guess I gotta stick with my 8.1 until someone figures this one out. This one feature is like super important to me atm.
Thanks again for your kind reply.
Hi,
No root required, my phone is standard no unlocked bootloader and no root.
You just need to install the software, then enable developer options on your phone, enable usb debbugging and send the following command to your phone. adb shell pm grant net.joneplustools android.permission.WRITE_SECURE_SETTINGS
Then you will have the option in the software (joneplustool) to enable call recording and also restore calling recorder at boot.
Then on the phone dialler , go into settings and enable call record.
xtruss said:
restore calling recorder at boot.
Click to expand...
Click to collapse
That's a bummer...
But hey, thanks a lot for your kind reply. And as for myself, I've been using Cherinbo, pretty decent I would say.
Well, I can confirm the paid verision of CallRecorder from skvalex still works on my Oneplus 6 with 9.0 Pie (not rooted, yet)
vibo2013 said:
Well, I can confirm the paid verision of CallRecorder from skvalex still works on my Oneplus 6 with 9.0 Pie (not rooted, yet)
Click to expand...
Click to collapse
Thanks for your feedback, and I'd like you ask a favor from you guys who is on 9.0.
Try that Cherinbo app and confirm that it's working good. I'll buy you a coffee if I could.
You seem as though you just want to promote a product to me, and one that doesn't work.
Darkest shades said:
Thanks for your feedback, and I'd like you ask a favor from you guys who is on 9.0.
Try that Cherinbo app and confirm that it's working good. I'll buy you a coffee if I could.
Click to expand...
Click to collapse
I wanted to give it a try, but I can't use it unless I give permission to access my contacts. A call recording app should work without that. So: sorry, won't test it any longer.
xtruss said:
You seem as though you just want to promote a product to me, and one that doesn't work.
Click to expand...
Click to collapse
Lol, not my intention. But the one thing that I like about this one is that all saved, recorded files doesn't appear into my music player, where as for others, they always does. Thanks for confirming that it doesn't work.
vibo2013 said:
I wanted to give it a try, but I can't use it unless I give permission to access my contacts. A call recording app should work without that. So: sorry, won't test it any longer.
Click to expand...
Click to collapse
It's ok, you help a lot already.
Thanks for your help guys.
I am very happy with the built in call recorder. What is the benefit of having a third party app to record calls?
xtruss said:
Hi,
adb shell pm grant net.joneplustools android.permission.WRITE_SECURE_SETTINGS
this adb command(below) worked on oreo and I just used it on pie, no root, works great. (you just have to run it again anytime you reboot your phone, if you're rooted, then it's permanent)
so, copy and paste in adb:
adb shell settings put global op_voice_recording_supported_by_mcc 1
>>>>then go to your phone dialer settings to see that is there.
Click to expand...
Click to collapse
Void
---------- Post added at 02:57 AM ---------- Previous post was at 02:49 AM ----------
mzsquared said:
xtruss said:
Hi,
adb shell pm grant net.joneplustools android.permission.WRITE_SECURE_SETTINGS
this adb command(below) worked on oreo and I just used it on pie, no root, works great. (you just have to run it again anytime you reboot your phone, if you're rooted, then it's permanent)
so, copy and paste in adb:
adb shell settings put global op_voice_recording_supported_by_mcc 1
>>>>then go to your phone dialer settings to see that is there.
Click to expand...
Click to collapse
Does this allow recording apps to work or just the default recorder on the dialer? Also has anyone tried ACR? People are reporting that it does still work with and without rooting.
Click to expand...
Click to collapse
dgunn said:
Void
Does this allow recording apps to work or just the default recorder on the dialer? Also has anyone tried ACR? People are reporting that it does still work with and without rooting.
Click to expand...
Click to collapse
"adb shell settings put global op_voice_recording_supported_by_mcc 1"
It enables the default, native Call Recorder found on op6 and op5 and I really like it. It recorded all my today's calls ranging from 625KB to 2.29MB all good quality(aac files)
eliaspizarro said:
Requeriments:
root
terminal with su permisions
Manual steps
Method 1 (works until reboot):
Create a file ex. incall.sh:
Code:
#!system/bin/sh
su -c 'settings put global op_voice_recording_supported_by_mcc 1'
execute from terminal: $ sh incall.sh
Method 2 (works until reboot):
with adb: > adb shell "settings put global op_voice_recording_supported_by_mcc 1"
My steps (permanent):
Install termux (add su permisions)
in termux: $ termux-setup-storage
Install termux boot
create folder un termux home path (default) named: .termux
in termux: $ ln -s /storage/emulated/0/<your boot script folder> ~/.termux/boot
create script in /storage/emulated/0/<your boot script folder>
Code:
su -c 'settings put global op_voice_recording_supported_by_mcc 1'
exit
reboot
Click to expand...
Click to collapse
..
This is what I'm getting
sh: $: not found
Just by telling us to install this and add home path here..... We need instructions
---------- Post added at 06:26 PM ---------- Previous post was at 06:04 PM ----------
and again
sh: adb: not found
mzsquared said:
xtruss said:
Hi,
adb shell pm grant net.joneplustools android.permission.WRITE_SECURE_SETTINGS
this adb command(below) worked on oreo and I just used it on pie, no root, works great. (you just have to run it again anytime you reboot your phone, if you're rooted, then it's permanent)
so, copy and paste in adb:
adb shell settings put global op_voice_recording_supported_by_mcc 1
>>>>then go to your phone dialer settings to see that is there.
Click to expand...
Click to collapse
When you say you used it on Pie, do you mean the beta or final version?
Click to expand...
Click to collapse
You can also use Tasker to enable native call recording (provided you've granted WRITE_SECURE_SETTINGS permission to Tasker).
It seems the system deactivates jOnePlus from activating call recorder after 8 hours. Anyway to make it a permanent activation?
Even after removing jOnePlus from the battery optimize list, the call recorder still gets deactivated after a couple of hours.
obislu said:
mzsquared said:
When you say you used it on Pie, do you mean the beta or final version?
Click to expand...
Click to collapse
I took the official OTA Pie upgrade and enabled the recorder with adb command after that. I'm not planning to root my phone, at least not yet. I'm enjoying the Pie Rom as is. It's all good, actually great with the night mode, there is no bloat. I disabled few apps, mainly from google and that's that. I remember times when rooting was an important necessity, I've had a Motorola Defy XT, long time ago, with 1GB RAM and no space for any extra apps, rooting was mainly used for getting the bloat out and moving apps to SD card by way of creating ext4 partition.
My OP6 has 256GB storage space, 8GB RAM and I just don't feel like constantly reloading the system, chasing newest twrps and Magisk versions, softbricking etc,etc.. and having my phone 'off line' for hours while I'm fixing it.
Click to expand...
Click to collapse
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.