You can use ADB on unrooted devices to remove the "What's New" option from the NavRing and to remove the Small Apps Widget launcher from Recent Apps.
I will assume you know how to install and use ADB.
To remove the "What's New" option from the NavRing:
Code:
adb shell
pm block com.sonymobile.advancedwidget.entrance
exit
adb reboot
Make sure to reboot before proceeding if you're removing both items.
To remove the Small Apps Widget Launcher from the Recents screen:
Code:
adb shell
pm block com.sony.smallapp.launcher
pm block com.sony.smallapp.app.widget
exit
adb reboot
To revert changes substitute "unblock" for "block" in the command.
Good to note that these work just have to be run seperatley, i tried to block all 3 at the same time and it did not work you have to remove the whats new then reboot then remove the small apps then reboot again
Thanks for this OP i hate that whats new thing
aford89 said:
Good to note that these work just have to be run seperatley, i tried to block all 3 at the same time and it did not work you have to remove the whats new then reboot then remove the small apps then reboot again
Thanks for this OP i hate that whats new thing
Click to expand...
Click to collapse
Thanks, added to OP.
Thank you!
The what's new was really bugging me :-/
do you know if the block command does the same as "deactivate" would do from the Settings->Apps menu? (if it were enabled)
punshkin said:
Thank you!
The what's new was really bugging me :-/
do you know if the block command does the same as "deactivate" would do from the Settings->Apps menu? (if it were enabled)
Click to expand...
Click to collapse
I assume so, the "pm" is for the package manager commands.
I can not thank you enough! I still don't know what Sony was thinking with "What's New".
Favorite'd, I just know I'll be needing this soon enough xD
Working like a charm. Glad to have my recents cleaned up. Any other bloatware we can disable this way? Love to get rid of the walkman, sony app updates, movie, movie creator, etc
Im just trying to do this but when I type adb shell reboot it says device not found. It does say im in [email protected] though. Anyone know whats wrong?
Mr Sliff said:
Im just trying to do this but when I type adb shell reboot it says device not found. It does say im in [email protected] though. Anyone know whats wrong?
Click to expand...
Click to collapse
do adb devices, should be able to see your device listed. if it reads not autorized: unlock your lockscreen and confirm the dialog to give computer access.
cyphomatic said:
do adb devices, should be able to see your device listed. if it reads not autorized: unlock your lockscreen and confirm the dialog to give computer access.
Click to expand...
Click to collapse
Thats the weird thing, my device is listed when I do that.
ADB, SDK, JDK, JRE, USB debug, USB drivers: all set up correctly?
Thanks! worked perfectly for me, at least it did when I installed the Android SDK on my Windows partition instead of my Mac ... Really didn't want to work on the Mac side, nor is there a native way to transfer wirelessly from my Mac but everything works well on the Windows end.
Thanks again OP :good:
Can this method be used to disable the other system apps?
Mr Sliff said:
Im just trying to do this but when I type adb shell reboot it says device not found. It does say im in [email protected] though. Anyone know whats wrong?
Click to expand...
Click to collapse
Got the same thing before I found out you need to exit remote shell before you run reboot command (I'm new to using adb for anything other than push/pull)
So after:
pm block com.sonymobile.advancedwidget.entrance
exit
adb reboot
phroenix said:
Got the same thing before I found out you need to exit remote shell before you run reboot command (I'm new to using adb for anything other than push/pull)
So after:
pm block com.sonymobile.advancedwidget.entrance
exit
adb reboot
Click to expand...
Click to collapse
Yea, you need to exit shell before running any adb command, I'll add that to the OP.
Alright for some reason it doesent remove whats new for me. Ive rebooted a few times and it doesnt work. Removing the small apps did work though.
Mr Sliff said:
Alright for some reason it doesent remove whats new for me. Ive rebooted a few times and it doesnt work. Removing the small apps did work though.
Click to expand...
Click to collapse
im getting the same thing. says the blocked state is true, then i reboot, still there
ikon8 said:
You can use ADB on unrooted devices to remove the "What's New" option from the NavRing and to remove the Small Apps Widget launcher from Recent Apps.
I will assume you know how to install and use ADB.
To remove the "What's New" option from the NavRing:
Code:
adb shell
pm block com.sonymobile.advancedwidget.entrance
exit
adb reboot
Make sure to reboot before proceeding if you're removing both items.
To remove the Small Apps Widget Launcher from the Recents screen:
Code:
adb shell
pm block com.sony.smallapp.launcher
pm block com.sony.smallapp.app.widget
exit
adb reboot
To revert changes substitute "unblock" for "block" in the command.
Click to expand...
Click to collapse
This whole thread is actually a repetition of what has already been discussed and suggested over here:
http://forum.xda-developers.com/z3-compact/help/deactivated-apps-getting-activated-t2889082
Can you use adb to get rid of the nav bar too?
oh Thankgod ! whats new and the quick launch widget are gone !!!!
Thankyou Thankyou Thankyou
ps; is there a list of commands to get rid of certain other apps, widgets, bloat etc ?
Related
The world's first ereader with a color Mirasol display is finally on the market, but unfortunately it's running a severely locked-down Android by the Korean bookstore chain Kyobo. The Kyobo ui is entirely in Korean, the browser blocks downloads, and the reader app is crap. In other words, it's basically useless to anyone outside of Korea. A few enterprising Americans have imported them and been extremely disappointed. Will someone please take a look at this device and see if it can be rooted or if something else can be done to make it of use to the rest of us?
Please use the Q&A Forum for questions Thanks
Moving to Q&A
Nate over at The Digital Reader has a firmware update that supposedly contains all of the installed apps. He is asking for someone to try and hack it. He has a download link for the firmware at The Digital Reader.
I also posted this as a question here on XDA:
http://forum.xda-developers.com/showthread.php?t=1432283
it is rooted since some time already.
files and instructions are in the following archive, but since instructions are in korean, i'll do a writeup below.
(argh! spambot won't allow this link, so you'll have to piece it together...)
www<dot>4shared<dot>com/zip/aLwRc7ZG/mirasol_rooting.html
edit: needed files are also in an attachment below
the gist is that you need to flash the boot partition via fastboot, setup root and busybox, and then modify secure->install_non_market_apps in settings.db.
you will need to have adb and fastboot from the android sdk working on your computer. There are many posts about this elsewhere, so i won't go into the details.
also, i only print filename without path, just find the corresponding file in the mentioned archive and modify the commands accordingly.
flash the boot partition via fastboot
first get your kyobo into fastboot mode (with usb cable attached) by pressing volume-down at bootup. timing here can be a bit finicky, but easiest seems to be to shut it down completely and then press just after pressing power.
issue a 'fastboot devices' on computer, if successful it should give you the response '???????????? fastboot' or similar. if empty or hangs, try again by rebooting the kyobo by pressing power with volume-up held (you can go into fastboot immediately after reboot by volume-down as expected).
when positive response above, you can flash by
Code:
fastboot flash boot boot.img
and then reboot by
Code:
fastboot reboot
edit: simplified fastboot instructions, thanks to smb_gaiden, whose button-poking-fu is strong.
setup root and busybox
with boot partition flashed you now have adb access, so let's use it. let the device boot as normal, and then issue the following.
Code:
adb push busybox /data/local/tmp
adb push fixsu.sh /data/local/tmp
adb push su /data/local/tmp
adb shell chmod 777 /data/local/tmp/busybox
adb shell chmod 777 /data/local/tmp/fixsu.sh
adb shell chmod 777 /data/local/tmp/su
adb shell /data/local/tmp/fixsu.sh
adb shell ln -s /data/local/tmp/busybox /system/xbin/busybox
after this, install some apk's from the archive
Code:
adb install superuser.apk
adb install blackmart.apk
fix non-market apps setting
only thing left is to change a setting to allow non-market apps to be installed. if you don't care about your current settings (locale, etc), you can just push the settings.db from the archive like so:
Code:
adb push settings.db /data/data/com.android.providers.settings/databases/
if you *do* care about your settings, you'll need to pull the settings.db, edit it in some sqlite db editor (set secure->install_non_market_apps to 1) and push the result.
that's it. all rooted. now you just need to install angry birds and yer' set ;-)
Adb doesn't seem to start properly on device
Hello.
I did succeed in flashing the bootloader via fastboot.
However when I boot device - I see adb on usb only for some initial seconds, and then it disappears.
For that matter my device already had December firmware on it.
Any ideas how to activate adb on device?
Thank you,
Leonid
it may be that persist.service.adb.enable is reset, stopping the adbd service. try flashing the attached boot image instead, see if that fixes it. it is the same as above, except that persist.service.adb.enable is ignored.
edit: i took a look at the december update, afaict it should pose no problem (very few changes in there).
Once these steps are done, how do you install google market?
Thanks.
edit: the original instructions were snafu, so i replaced them with something that should actually work.
getting android market running on the kyobo
needed files are in the attached archive.
install like so:
Code:
adb remount
adb push DrmProvider.apk /system/app
adb push MediaProvider.apk /system/app
adb push DownloadProvider.apk /system/app
adb push GoogleServicesFramework.apk /system/app
adb push Market-3.4.4.apk /system/app
adb push init.qcom.post_boot.sh /system/etc
adb push fix-shared-user.sh /data/local/tmp
adb shell chmod 777 /data/local/tmp/fix-shared-user.sh
adb shell /data/local/tmp/fix-shared-user.sh
wait for the reboot, find market in the menu, and off you go (with downloads this time ;-)
if downloads still do not work after this, try re-executing the last line. android periodically writes to the file we are modifying, which might clobber our changes if unlucky.
I am thinking about buying one of these because I have seen it on sale for 50% discount. However, the general reviews aren't too encouraging, so will rooting make any difference to overall performance?
fatboy1976 said:
I have seen it on sale for 50% discount.
Click to expand...
Click to collapse
where is that?
throwaway4096 said:
you'll need GoogleServicesFramework.apk and Market-3.4.4.apk from the following links:
http://androidmarketu.googlecode.com/files/GoogleServicesFramework.apk
http://forum.xda-developers.com/showthread.php?t=1391565
install like so:
Code:
adb remount
adb push GoogleServicesFramework.apk /system/app
adb push Market-3.4.4.apk /system/app
find Market in the menu and off you go.
Click to expand...
Click to collapse
I'm finding the market force closes when downloading an app.
May I seek help from someone who has rooted recently? I am finding it pretty difficult to get into fastboot. So some questions as I continue to play.
Which version is currently rootable? I bought mine this week and want to be sure it is still applicable with the method here.
Do I need a USB driver to work this hack? EDIT: Yes, found with a web search.
When do I press the volume keys? Immediately after power? Similar timing? When I see the flicker on the screen? When I see the logo? Before all that? EDIT: I did not need the volume up key to get into fastboot.
Thanks!
rooting for beginners
Some friends and i ordered the kyobo to solve our eye-problem (nystagm)
We still can´t figure out, how to root it.
Can you please give us some rooting instruktion vor beginners??
It would be so essential for us, as the kyobo is little worth without forgeign apps!
Thank you very much!
Joe
send2toonie said:
I'm finding the market force closes when downloading an app.
Click to expand...
Click to collapse
Hi, I am stuck with the same problem. Have tried many things?!
---------- Post added at 04:57 PM ---------- Previous post was at 04:32 PM ----------
smb_gaiden said:
May I seek help from someone who has rooted recently? I am finding it pretty difficult to get into fastboot. So some questions as I continue to play.
Which version is currently rootable? I bought mine this week and want to be sure it is still applicable with the method here.
Do I need a USB driver to work this hack? EDIT: Yes, found with a web search.
When do I press the volume keys? Immediately after power? Similar timing? When I see the flicker on the screen? When I see the logo? Before all that? EDIT: I did not need the volume up key to get into fastboot.
Thanks!
Click to expand...
Click to collapse
Hi, Managed to root my kyobo after about 8 h trying. I installed the firmware update on my kyobo, that is found on the web, as instructed from the SD card. Then I installed fastboot and adb on my computer (search for 'how to install fastboot and adb'), as I found instructions for that as well. To enter fastboot I kept Kyobos, volume down button for about 10 sec, when booting the device (kyobo connected to computer with USB) - nothing happens -> however on my computers command window (cmd), 'fastboot devices' command produces an answer with '? ..' as it should. The biggest issue I had was to get adb working. For this purpose I installed and removed a couple of USB drivers - I don't really know how I got it to work finally.
You can tell if you have succeeded installing a useful usb driver, if you enter the 'adb devices' command in the cmd window and it returns a device number. Then you are ready to go with the rest of the commands/instruction as seen in the insturction of this thread.
From the blackmart application I was able to install many useful applications - the Launcher application can replace the Kyobo "home" application, which is very useful.
I installed android market as well, but so far I have not been able to download and install applications. I think It might be a permission issue between kyobo software and the installed android market?
Hey Guys!
is there a way to root the kyobo via mikrosd?
thanks a lot
Joe
Hey Joe. I've seen you on this forum as well as The Digital Reader asking for help with the Kyobo rooting. I too am a beginner and I'm trying to build up the nerve to try it. Wish us both luck and I hope someone can share rooting-for-dummies with us.
@fatboy1976: rooting won't improve performance in itself. it makes the device better as you can install apps, but ofc the hardware is still the same.
@send2toonie: yes, sorry about that. it worked for me, but only thanks to other changes. it's hard to keep track :-/. i updated the original post with new instructions which should work properly.
@smb_gaiden: hah, excellent, i never tried that! original post updated.
@Joe84: it should be possible to root via microsd by creating an update.zip. i haven't gotten around to trying that yet, but maybe in future. for now this is as simple as it gets.
Kaarlos said:
Hi, I am stuck with the same problem. Have tried many things?!
---------- Post added at 04:57 PM ---------- Previous post was at 04:32 PM ----------
Hi, Managed to root my kyobo after about 8 h trying. I installed the firmware ...(updated -see above..) .., which is very useful.
I installed android market as well, but so far I have not been able to download and install applications. I think It might be a permission issue between kyobo software and the installed android market?
Click to expand...
Click to collapse
Jep! With the updated instuctions the Android Market now finally works!! Thanks! (Installed twice)
Kaarlos said:
Jep! With the updated instuctions the Android Market now finally works!! Thanks! (Installed twice)
Click to expand...
Click to collapse
Hi,
Could you post the OS/processor version and driver name that got adb working for you. If you can also remember the keys pressed to put the Kyobo in the correct boot mode for adb, that would be nice too.
I have also managed to load apps on my Kyobo but that is without having su, Superuser, adb and Android Market working. The above info would be helpful in fixing that. Holding the volume down fir 10 seconds after pressing power on puts the Kyobo into fastboot mode. Adb requires a different mode and set of key presses. This is because there is a menu of boot options being displayed which can't be seen on the Mirasol screen. I suspect this is because of display settings within the boot.img but that is only a guess on my behalf.
How should I go about factory resetting my rooted, HD 7" that's running a different launcher? So that it can go back to as clean as possible and be updatable and used normally without bricking/dying. I heard it's dangerous to just use the native factory reset as it can end up with bricks.
Its running on some older firmware that was rootable not long after it became possible and is running Vire Launcher instead of the typical amazon launcher. I'd like to go back to Stock somehow.
Sorry for the double post but seriously no-one knows how to go back to fully default?
Shadowshinra said:
Sorry for the double post but seriously no-one knows how to go back to fully default?
Click to expand...
Click to collapse
For stock with no root:
Run these commands to unblock OTA:
Code:
adb shell pm unblock com.amazon.dcp and
adb shell pm unblock com.amazon.otaverifier
Also, look for /system/priv-app/deviceSoftwareOTA.apk and make sure the extension is (plain) "apk"
Put OS 5.1.2 onto /sdcard (not inside a folder) and press Update now in Device settings.
For latest stock with root, follow this root guide: http://forum.xda-developers.com/fire-hd/general/how-to-upgrade-to-lollipop-root-gapps-t3163950 without installing Gapps/xposed/makespace. If you're running OS 4.5.3 now you can use 5.2.0_stock_recovery_uboot.zip at step 10.
DoLooper said:
For stock with no root:
Run these commands to unblock OTA:
Code:
adb shell pm unblock com.amazon.dcp and
adb shell pm unblock com.amazon.otaverifier
Also, look for /system/priv-app/deviceSoftwareOTA.apk and make sure the extension is (plain) "apk"
Put OS 5.1.2 onto /sdcard (not inside a folder) and press Update now in Device settings.
For latest stock with root, follow this root guide: http://forum.xda-developers.com/fire-hd/general/how-to-upgrade-to-lollipop-root-gapps-t3163950 without installing Gapps/xposed/makespace. If you're running OS 4.5.3 now you can use 5.2.0_stock_recovery_uboot.zip at step 10.
Click to expand...
Click to collapse
Seems simple enough, the adb commands seemingly worked but I can't seem to rename the APK_ back into APK using ES file explorer, it just says renaming progress and the bar doesn't fill up.. so I haven't done the last step yet.
Shadowshinra said:
Seems simple enough, the adb commands seemingly worked but I can't seem to rename the APK_ back into APK using ES file explorer, it just says renaming progress and the bar doesn't fill up.. so I haven't done the last step yet.
Click to expand...
Click to collapse
Try rebooting and see if it got renamed. Are you sure you're rooted and have root explorer on in es file explorer? Maybe you used JMZ's Fire Tool to block OTA? See if you have it and try that for unblocking. Or, if rooted this command might work:
Code:
adb -d shell "su -c 'mount -o remount,rw /system; cd /system/priv-app/; mv DeviceSoftwareOTA.apk_ DeviceSoftwareOTA.apk'"
If you can't get it renamed, try doing the update. Don't think it'll work, but worth a shot. If it doesn't work, you'll need to boot twrp and install 5.1.1 or 5.1.2 from there: http://forum.xda-developers.com/showpost.php?p=62011272&postcount=2
DoLooper said:
Try rebooting and see if it got renamed. Are you sure you're rooted and have root explorer on in es file explorer? Maybe you used JMZ's Fire Tool to block OTA? See if you have it and try that for unblocking. Or, if rooted this command might work:
Code:
adb -d shell "su -c 'mount -o remount,rw /system; cd /system/priv-app/; mv DeviceSoftwareOTA.apk_ DeviceSoftwareOTA.apk'"
If you can't get it renamed, try doing the update. Don't think it'll work, but worth a shot. If it doesn't work, you'll need to boot twrp and install 5.1.1 or 5.1.2 from there: http://forum.xda-developers.com/showpost.php?p=62011272&postcount=2
Click to expand...
Click to collapse
Definitely rooted, heck you yourself helped me do it a long time ago, even Root checker says i'm still rooted, I do have JMZ tool, the OTA section is gray though, reboot didn't help, will try the adb command
Edit, upon entering the command CMD appeared to hang/stall/do nothing. Not letting any other commands to be typed afterwards.
Shadowshinra said:
Edit, upon entering the command CMD appeared to hang/stall/do nothing. Not letting any other commands to be typed afterwards.
Click to expand...
Click to collapse
CTRL-C to get out. EDIT @Shadowshinra: Do you get # prompt with "adb shell" "su"?
DoLooper said:
CTRL-C to get out. EDIT @Shadowshinra: Do you get # prompt with "adb shell" "su"?
Click to expand...
Click to collapse
You mean the popup on the kindle? Now you mention it, It hasn't been popping up since I've been attempting this, so somehow I/it semi-unrooted itself despite the rootchecker saying it's fine? Or were the changed we did responsible?
Edit: Oh wait I know what you mean now, the # sign isn't there either, it's a $ so yeah It's unrooted itself somehow or I did something unknowingly, which is odd seeing as the Vire Launcher, root checker and all my apps are still working..
Edit2: Ran supersu, turned it off and on, appears to have fixed it? I was able to rename it aftar that.. it can't have been that simple lol..
Shadowshinra said:
Edit: Oh wait I know what you mean now, the # sign isn't there either, it's a $ so yeah It's unrooted itself somehow or I did something unknowingly, which is odd seeing as the Vire Launcher, root checker and all my apps are still working..
Edit2: Ran supersu, turned it off and on, appears to have fixed it? I was able to rename it aftar that.. it can't have been that simple lol..
Click to expand...
Click to collapse
Yes, there's a twilight-zone state in which root apps partially work but you can't get full superuser access until you update binaries by running superSU app. No idea how you lost su. Anyway, I trust you can update to unrooted stock 5.1.2 now.
DoLooper said:
Yes, there's a twilight-zone state in which root apps partially work but you can't get full superuser access until you update binaries by running superSU app. No idea how you lost su. Anyway, I trust you can update to unrooted stock 5.1.2 now.
Click to expand...
Click to collapse
When I tried to use that update it just says Validating update file, and seemingly loading forever, i'll edit if it ever completes, but if I turn on wifi it will try to download an update from there can that not be used instead or does that cause the bricks I've heard about?
Shadowshinra said:
When I tried to use that update it just says Validating update file, and seemingly loading forever, i'll edit if it ever completes, but if I turn on wifi it will try to download an update from there can that not be used instead or does that cause the bricks I've heard about?
Click to expand...
Click to collapse
The OTA update should be fine. I actually thought the manual method would be faster, but . . .
DoLooper said:
The OTA update should be fine. I actually thought the manual method would be faster, but . . .
Click to expand...
Click to collapse
Ah I see, however another issue has arisen, upon hitting update and it attempting to do so after a reboot, the team win recovery menu shows up instead, If I click reboot from there I'm just taken back to the dashboard on the original rooted firmware, I guess the TWRP is interfering in some manner? Also do I have to reenable the Fire Launcher and uninstall Virelauncher before all of this or will the updating process just do all of that.
Shadowshinra said:
Ah I see, however another issue has arisen, upon hitting update and it attempting to do so after a reboot, the team win recovery menu shows up instead, If I click reboot from there I'm just taken back to the dashboard on the original rooted firmware, I guess the TWRP is interfering in some manner? Also do I have to reenable the Fire Launcher and uninstall Virelauncher before all of this or will the updating process just do all of that.
Click to expand...
Click to collapse
@bibikalka, I totally forgot @Shadowshinra would have TWRP, coming from rooted OS4. Any problem with him following your steps here to restore stock? http://forum.xda-developers.com/fire-hd/general/how-to-restore-stock-fireos-t3164267 Thanks!
Long story short... I have a non-rooted SGH-M919 (Samsung Galaxy S4) with a completely broken screen. USB to PC transfer doesn't work, it's set to charge only, Kies doesn't see it...etc.
I have found that it's still on my wifi and on my google play account so I can install apps from the website. Does anybody know any apps I can install that will instantly let me access my files (and transfer them) without needing to do anything on the phone's side? Remote access would be great but I'd settle for file sharing even if only on the local network.
Any other ideas would be great! I need to recover pictures and contacts that aren't on google, or the SD card. New phone doesn't take the SIM.
You're probably not going to like this answer, but I recommend you simply have the screen fixed. If MTP isn't enabled and you can't enable it, and it's not rooted... There's just not much you can do.
NetworkAuditor said:
You're probably not going to like this answer, but I recommend you simply have the screen fixed. If MTP isn't enabled and you can't enable it, and it's not rooted... There's just not much you can do.
Click to expand...
Click to collapse
That's not too helpful... I found a (paid) app that attempts to recover files from the phone's download mode, which I think I could get to. There's gotta be other (free) options out there if download mode has access to files. Also as I said, I'm sure there's some app out there that shares files on the local network. I just need a name if anybody has one.
Thanks for answering still... but I know there's options.
UnknownCloakedMan said:
That's not too helpful... I found a (paid) app that attempts to recover files from the phone's download mode, which I think I could get to. There's gotta be other (free) options out there if download mode has access to files. Also as I said, I'm sure there's some app out there that shares files on the local network. I just need a name if anybody has one.
Thanks for answering still... but I know there's options.
Click to expand...
Click to collapse
Oh! Well if you can get to recovery, you may be able to pull the files off the device or back it up entirely.
Search "adb from recovery" and see if that gets you anywhere. If you *can* use adb, you might be able use adb's "backup" command to back up whatever you have on there.
NetworkAuditor said:
Oh! Well if you can get to recovery, you may be able to pull the files off the device or back it up entirely.
Search "adb from recovery" and see if that gets you anywhere. If you *can* use adb, you might be able use adb's "backup" command to back up whatever you have on there.
Click to expand...
Click to collapse
No custom recovery and no root access so I don't think adb will work for me... will it? I've confirmed USB debugging is off.
UnknownCloakedMan said:
No custom recovery and no root access so I don't think adb will work for me... will it? I've confirmed USB debugging is off.
Click to expand...
Click to collapse
Well, I've never used adb from recovery before, but a quick search makes me think it could be possible. If you're desperate to recover the data, I' m assuming anything is worth a try.
Now most of the time, stock recovery doesn't have adb access, but if you can manage to unlock your phone, you would be able to install CWM recovery and boot to it.
However, this is unlikely, as IMO, the SGS4 is one of the most painful phones to try to unlock, especially when you don't have access to the screen.
soo.. I am trying adb right now. I did...
adb shell
cd /sdcard/DCIM/Camera
ls
and all my pictures are listed! I tried doing a pull at that point and it says device not found... which it clearly is since it's reading the info. Any idea what my next step is? mounting or something? I feel like I'm so close!
EDIT:
BOOM! got it! I read one post online that said "stay out of shell for pull" I reopened my adb window and just did "adb pull /sdcard/DCIM/Camera" and all is recovered now. Thanks and I hope this post helps somebody in the future!
UnknownCloakedMan said:
soo.. I am trying adb right now. I did...
adb shell
cd /sdcard/DCIM/Camera
ls
and all my pictures are listed! I tried doing a pull at that point and it says device not found... which it clearly is since it's reading the info. Any idea what my next step is? mounting or something? I feel like I'm so close!
EDIT:
BOOM! got it! I read one post online that said "stay out of shell for pull" I reopened my adb window and just did "adb pull /sdcard/DCIM/Camera" and all is recovered now. Thanks and I hope this post helps somebody in the future!
Click to expand...
Click to collapse
Glad you got everything resolved! Now for my own curiosity, how did you manage to get adb working?
NetworkAuditor said:
Glad you got everything resolved! Now for my own curiosity, how did you manage to get adb working?
Click to expand...
Click to collapse
Nothing special at all. It only required:
> Phone in download mode, wired to PC with USB cable
> ADB installed on PC
> Samsung USB Drivers
> Open adb command prompt, and run the pull command (after finding the exact directory using adb shell)
Got an Oppo R9s through aliexpress. First time it arrived the home button wouldn't work, neither the fingerprint scanning. After sending it back and waiting three months I got a working device, but seems to have malware on it.
The lock screen is filled with chinese pictures. Doesn't seem malicious, but I can't remove it. After resetting the device to factory settings it's the first thing that installs itself after giving it network access. The wallpaper option in settings doesn't work. More importantly, when I add a phone contact, the phone app crashes opening as well as the contacts app, which renders the phone completely useless, not being able to make a simple phone call. Also, simple mode doesn't work either.
So my guess this is a modified rom to have some malware always present and basic functionality is either removed or crippled. Following instructions to enter fastboot mode (volume up + power on) seem to enter an endless loop, so it looks like this option is disabled. Using volume down I'm able to enter a recovery mode, where it says it's version 1.2 (root), and allows me to select some rom for flashing.
Before trying to wade through all the threads regarding rooting and flashing, I was considering simply replacing the ColorOS rom with a clean one. However I'm unable to find any for R9s, is it that this model doesn't have one available? Even looking at the international Oppo forums they don't have any R9s download links. So I guess I have to spend some hours reading and fishing links from long threads like https://forum.xda-developers.com/android/help/oppo-r9s-rooting-t3496781 ?
The about info of the device says this is an Oppo R9s, ColorOS v3.0, Android 6.0.1, MSM8953 OctaCore, 4GB ram, build number R9s_91_A.28_191025, baseband version Q_V1_P14,Q_V1_P14, Kernel 3.18.24-G201710252140.
romfury88 said:
Got an Oppo R9s through aliexpress. First time it arrived the home button wouldn't work, neither the fingerprint scanning. After sending it back and waiting three months I got a working device, but seems to have malware on it.
The lock screen is filled with chinese pictures. Doesn't seem malicious, but I can't remove it. After resetting the device to factory settings it's the first thing that installs itself after giving it network access. The wallpaper option in settings doesn't work. More importantly, when I add a phone contact, the phone app crashes opening as well as the contacts app, which renders the phone completely useless, not being able to make a simple phone call. Also, simple mode doesn't work either.
So my guess this is a modified rom to have some malware always present and basic functionality is either removed or crippled. Following instructions to enter fastboot mode (volume up + power on) seem to enter an endless loop, so it looks like this option is disabled. Using volume down I'm able to enter a recovery mode, where it says it's version 1.2 (root), and allows me to select some rom for flashing.
Before trying to wade through all the threads regarding rooting and flashing, I was considering simply replacing the ColorOS rom with a clean one. However I'm unable to find any for R9s, is it that this model doesn't have one available? Even looking at the international Oppo forums they don't have any R9s download links. So I guess I have to spend some hours reading and fishing links from long threads like https://forum.xda-developers.com/android/help/oppo-r9s-rooting-t3496781 ?
The about info of the device says this is an Oppo R9s, ColorOS v3.0, Android 6.0.1, MSM8953 OctaCore, 4GB ram, build number R9s_91_A.28_191025, baseband version Q_V1_P14,Q_V1_P14, Kernel 3.18.24-G201710252140.
Click to expand...
Click to collapse
Are you trying to replace the ROM or just remove the Malware? I've never heard of this device before so I can't point you towards any ROMs, But I can certainly help you remove Malware embedded in the ROM.
theashleyd123 said:
Are you trying to replace the ROM or just remove the Malware? I've never heard of this device before so I can't point you towards any ROMs, But I can certainly help you remove Malware embedded in the ROM.
Click to expand...
Click to collapse
I'm not interested in changing ROMs, just remove the malware that prevents normal device usage. That's why I was asking for links to ColorOS firmware, I presume reinstalling those would restore normal operation. However if that's not possible I'll take any non-malware ROM.
I followed the recommendation from http://community.oppo.com/en/forum.php?mod=viewthread&tid=50113 to use "adb shell" commands and disable ROM programs, finally getting to remove the lock screen pictures. After a while of having the phone turned on, I heard a weird ping sound and then the touch screen stopped responding. It works fine, since I can power off swiping to the right on the off screen, or I can swipe down and play with the toggles, but the launcher and settings app don't seem to receive touches. So maybe I disabled something affecting the screen? I did run:
adb shell pm hide com.android.browser
adb shell pm hide com.android.contacts
adb shell pm hide com.oppo.usercenter
adb shell pm hide com.nearme.gamecenter
adb shell pm hide com.nearme.atlas
adb shell pm hide com.nearme.statistics.rom
adb shell pm hide com.oppo.launcher
adb shell pm hide com.oppo.market
adb shell pm hide com.oppo.music
adb shell pm hide com.sohu.imputmethod.sogouoem
adb shell pm hide com.redteamobile.roaming
adb shell pm hide com.redteamobile.virtual.softsim
adb shell pm hide com.coloros.lives
adb shell pm hide com.nearme.themespace
adb shell pm hide com.nearme.themespacelib
adb shell pm hide com.coloros.pictorial
Rebooting or recovery mode doesn't work, so I figured to install a ROM from https://forum.xda-developers.com/showpost.php?p=70366156&postcount=13 in recovery mode (where the touch screen works fine). After installation the "optimizing android apps" kept there forever, so I turned it off/on manually, and now I launch into the original launcher with a few chinese icons, but still the screen doesn't seem to work.
Touches work for the notifications and such, but nothing for the launcher or settings, so now I'm unable to turn on USB debugging to send adb shell commands. :crying:
You've disabled your launcher and a couple of required android services (Browser etc) Use adb again to sideload a new launcher too.
---------- Post added at 10:44 AM ---------- Previous post was at 10:42 AM ----------
Also try reenabling the input method.
theashleyd123 said:
You've disabled your launcher and a couple of required android services (Browser etc) Use adb again to sideload a new launcher too.
I did these after installing replacements, like that post explained. Chrome as browser, Google APKs for contacts/calendar, Novo launcher instead of stock… and everything seemed to be working fine.
I can't enable debugging on the device, adb commands don't seem to reach the device. I've never used sideload before, does it work even without debug mode enabled?
Click to expand...
Click to collapse
romfury88 said:
theashleyd123 said:
You've disabled your launcher and a couple of required android services (Browser etc) Use adb again to sideload a new launcher too.
I did these after installing replacements, like that post explained. Chrome as browser, Google APKs for contacts/calendar, Novo launcher instead of stock… and everything seemed to be working fine.
I can't enable debugging on the device, adb commands don't seem to reach the device. I've never used sideload before, does it work even without debug mode enabled?
Click to expand...
Click to collapse
You can sideload an app via recovery by pushing it to /system/app
And then use adb shell chmod 644 "/system/app/APKNAME"
Click to expand...
Click to collapse
theashleyd123 said:
romfury88 said:
You can sideload an app via recovery by pushing it to /system/app
And then use adb shell chmod 644 "/system/app/APKNAME"
Click to expand...
Click to collapse
I can't due to adb not being able to connect to the device, since I can't put it in debug mode. When the device is in recovery mode I can't access it either, I only get "- waiting for device -"
Click to expand...
Click to collapse
Finally managed to flash a good original ROM on the device. Conveniently the chinese rom prevents running dangerous adb commands, but at least I seem to have gotten rid of the malware and I'm able to change desktop wallpapers and the lockscreen magazine
$ adb shell pm hide com.oppo.music
Error: java.lang.SecurityException: Neither user 2000 nor current process has android.permission.MANAGE_USERS.
Click to expand...
Click to collapse
romfury88 said:
Finally managed to flash a good original ROM on the device. Conveniently the chinese rom prevents running dangerous adb commands, but at least I seem to have gotten rid of the malware and I'm able to change desktop wallpapers and the lockscreen magazine
Click to expand...
Click to collapse
hi romfury88 how did u manage to flash original ROM can u guide me pls. thanks
Oppo R9S
ulyong23 said:
hi romfury88 how did u manage to flash original ROM can u guide me pls. thanks
Click to expand...
Click to collapse
Just bought an OPPO R9S and was wondering you managed to flash the original ROM? I have the exact same issues that romfury had.
Fluid Navigation Gesture
Installation
The app has a built-in option to hide the software navigation keys (if necessary) but it requires either root or a pc is required to grant a system permission.
Instructions:
1-Enable Developer Mode in the Android settings.
2- Enable USB Debugging
3- Install Adb (links bellow)
4- Run the following adb command to grant the
Permission:
Windows: adb shell pm grant com.fb.fluid android.permission.WRITE_SECURE SETTINGS
macOS: Jadb shell pm grant com.fb.fluid android.permission.WRITE_SECURE_SETTINGS
You can restore the navigation keys using the app or by run this
adb command:
Windows: adb shell wm overscan O,0,0,0
macOS: /adb shell wm overscan 0,0,0,0
Actions:
Back
Home
Recent apps
Toggle split screen
Open notifications
Open power dialog
Open quick settings
Launch Google search overlay
Open keyboard selector
Voice Search
Launch assistant
Launch app
Launch shortcut
Download:
https://play.google.com/store/apps/details?id=com.fb.fluid
Hey guys
So I am a beta tester and I made a review of the app with detailed instructions in my channel so for anyone interested to see and understand it
youtu.be/y1X3wQnEMBc
I get an error when running the command: Bad argument: java.lang.IllegalArgumentException: Unknown permission: android.permission.WRITE_SECURE
stevenlientje said:
I get an error when running the command: Bad argument: java.lang.IllegalArgumentException: Unknown permission: android.permission.WRITE_SECURE
Click to expand...
Click to collapse
The correct one is android.permission.WRITE_SECURE_SETTINGS
Regurding the fluid app
Hi its perfectly working on my note 9 as i want to remove the app please help me to remove the app the installation was done with the pc guide lines so any one who has the idea of how to remove the app from a note 9 as i did rwmove but the side still is thier
wasp45 said:
Hi its perfectly working on my note 9 as i want to remove the app please help me to remove the app the installation was done with the pc guide lines so any one who has the idea of how to remove the app from a note 9 as i did rwmove but the side still is thier
Click to expand...
Click to collapse
Read the guide. It tell how you can do it.
Have you tried to reboot device after removing it?
Force kill app not work! Pro version
What happens? @@Deadpool96
Sent from my [device_name] using XDA-Developers Legacy app
Unable to restore navigation keys on Yureka Black
I am using Yureka Black device and tried enabling fluid navigation. That worked well. But now i just want to restore my navigation keys but unable to do so. I tried from the app and from the ADB as well (adb shell wm overscan 0,0,0,0) but nothing works. Please help. I have tried rebooting and all
Twrp
Any devs can make a flashble zip for granting cammand through twrp? I iz noob.
does not work on Android 10, quits immediately (Google Pixel 3)
Recent apps
Hi, a little help here.
i have a oneplus 7 (not pro), and i installed FNG in august, and i absolutely loved it
but, since this week's update (i think on sep 21), the gesture for "previous app" changed its behavior. instead of showing the 3 previous app (one swipe changed to the latest, a second one to the one before, a third the one before, and then returning to show the previous app). it was super useful because i drive a cab and could change between 4 apps with ease while driving without little distraction, and also because recent apps has to rotate because it does not support landscape mode anymore (DON'T GET ME STARTED ON THAT, but any help on that would be also very useful).
now, it only shows the last app, and when on android auto it's common that it shows that, which only block the screen and is completely useless.
so, i'm willing to send a lot of good vibrations to whoever can help me with that (that's a once in a lifetime offer, guys). thanks for any help you can offer with this
I have an error running this command : error: device '(null)' not found
Hi, I had an error message whilst trying to hide naviagion bar using computer (win10). Error -> device unauthorized (I have screenshot of it, but I can't send link here. - (I have USB debbuging on)
MikePlays_ said:
Hi, I had an error message whilst trying to hide naviagion bar using computer (win10). Error -> device unauthorized (I have screenshot of it, but I can't send link here. - (I have USB debbuging on)
Click to expand...
Click to collapse
Mmm, sounds more like an ADB problem, rather than an FNG one.
Hi, MikePlays_
I've had this problem myself occasionally when running ADB, not specifically with FNG, but with other apps requiring an ADB command line to be run.
Usually, when you run ADB for the first time, both your PC and your Android device displays a dialog box to confirm USB debugging authorisation. I'm a little hazy on the precise details of this dialog box, because it's been quite a while since I used ADB.
Anyhow, if this doesn't happen or you get an error message, then you can try to revoke USB debugging authorisations, and begin again, with the FNG ADB command line. Sometimes a reboot of both your PC and your Android device may be required after revocation.
You should find the revoke authorisation option in your Android devices Developer Options settings. See my screenshot below, taken from my Android 9 Moto G6.
I can't say for certain if this will work for you, but when I've had weird ADB authorisation problems in the past, this has usually fixed the problem.
Good luck & I hope this helps
Rgrds,
Ged.
Sent from my moto g(6) using XDA Labs
GedBlake said:
Mmm, sounds more like an ADB problem, rather than an FNG one.
Hi, MikePlays_
I've had this problem myself occasionally when running ADB, not specifically with FNG, but with other apps requiring an ADB command line to be run.
Usually, when you run ADB for the first time, both your PC and your Android device displays a dialog box to confirm USB debugging authorisation. I'm a little hazy on the precise details of this dialog box, because it's been quite a while since I used ADB.
Anyhow, if this doesn't happen or you get an error message, then you can try to revoke USB debugging authorisations, and begin again, with the FNG ADB command line. Sometimes a reboot of both your PC and your Android device may be required after revocation.
You should find the revoke authorisation option in your Android devices Developer Options settings. See my screenshot below, taken from my Android 9 Moto G6.
I can't say for certain if this will work for you, but when I've had weird ADB authorisation problems in the past, this has usually fixed the problem.
Good luck & I hope this helps
Rgrds,
Ged.
Sent from my moto g(6) using XDA Labs
Click to expand...
Click to collapse
Well, thanks for fast reply, I don't know how to properly use ADB, is there any tuturial for that? I can't see any dialog box on computer, so something is wrong.
MikePlays_ said:
Well, thanks for fast reply, I don't know how to properly use ADB, is there any tuturial for that? I can't see any dialog box on computer, so something is wrong.
Click to expand...
Click to collapse
As per my previous post, try revoking your USB debugging authorisations, and then reboot both your PC and your Android device. If all goes well, the dialog box should then appear when you run the ADB command. If I remember correctly, it's similar in function to pairing two Bluetooth devices together, with a unique code, and which you then have to confirm.
As for tutorials, try this to begin with...
https://www.xda-developers.com/quickly-install-adb
In the meantime, I'll get my laptop out, and see if I can grab a screenshot of the dialog box you should expect to see. Give me an hour or so
Rgrds,
Ged.
Sent from my moto g(6) using XDA Labs
GedBlake said:
As per my previous post, try revoking your USB debugging authorisations, and then reboot both your PC and your Android device. If all goes well, the dialog box should then appear when you run the ADB command. If I remember correctly, it's similar in function to pairing two Bluetooth devices together, with a unique code, and which you then have to confirm.
As for tutorials, try this to begin with...
https://www.xda-developers.com/quickly-install-adb
In the meantime, I'll get my laptop out, and see if I can grab a screenshot of the dialog box you should expect to see. Give me an hour or so
Rgrds,
Ged.
Sent from my moto g(6) using XDA Labs
Click to expand...
Click to collapse
well, now I tried it again, when I was trying to allow USB debbuging, it gave me error -> screenshot at the bottom. But thank you very much for that quick response, I did not expect that
OK, I was mistaken. No dialog box appears on the PC, but one does appear on your Android device, and it looks like the screenshot below...
Rgrds,
Ged.
MikePlays_ said:
well, now I tried it again, when I was trying to allow USB debbuging, it gave me error -> screenshot at the bottom. But thank you very much for that quick response, I did not expect that
Click to expand...
Click to collapse
That's great news. Hope you get FNG working, with a disabled stock Nav Bar.
It's a terrific app, and one I couldn't imagine without, on my phone and tablet.
Rgrds,
Ged.
Sent from my moto g(6) using XDA Labs
GedBlake said:
OK, I was mistaken. No dialog box appears on the PC, but one does appear on your Android device, and it looks like the screenshot below...
Rgrds,
Ged.
Click to expand...
Click to collapse
Problem I have with it is even smaller pop up over that, it writes when I want to press "ok", it writes "an app is obscuring a permission request. Settings can't verify your response." It is visible on screenshot too, but it has low quality.