Database Develop

[Q] Problems with enabling sideloading

Okay everybody, first off let me apologize, as I am sure that this is asked quite a bit. However, I am not very savvy with using terminal and such to enable sideloading on my Captivate, and I cannot get any of the methods to work properly.
I started off with the Unleash the Beast root on my phone, then for some reason I thought that froyo was out as an official update, because when I went to check for an update, it would download a package, reboot my phone, then tell me that the update could not be applied. So, thinking that it was due to the root, I had to use Odin to get Unleash the Beast off the phone; however, whatever "update" the phone was attempting to apply still would not work. So I reverted back to root the phone. I have used the One Click Root to program, I have installed BusyBox, and allowed SuperUser access. I am trying to enable sideloading so that I can download the Market Access app, but I am having troubles getting it to work. I have a Mac, and I have used many methods to try and enable it, but no matter what I do it will not work.
Again, I apologize for my ignorance. I have searched all over, and I still can't get this stuff to work. If anybody could provide any assistance, it would be greatly appreciated.
Thanks

goosefraba91 said:
Okay everybody, first off let me apologize, as I am sure that this is asked quite a bit. However, I am not very savvy with using terminal and such to enable sideloading on my Captivate, and I cannot get any of the methods to work properly.
I started off with the Unleash the Beast root on my phone, then for some reason I thought that froyo was out as an official update, because when I went to check for an update, it would download a package, reboot my phone, then tell me that the update could not be applied. So, thinking that it was due to the root, I had to use Odin to get Unleash the Beast off the phone; however, whatever "update" the phone was attempting to apply still would not work. So I reverted back to root the phone. I have used the One Click Root to program, I have installed BusyBox, and allowed SuperUser access. I am trying to enable sideloading so that I can download the Market Access app, but I am having troubles getting it to work. I have a Mac, and I have used many methods to try and enable it, but no matter what I do it will not work.
Again, I apologize for my ignorance. I have searched all over, and I still can't get this stuff to work. If anybody could provide any assistance, it would be greatly appreciated.
Thanks
Click to expand...
Click to collapse
Could you provide a little more information about your phone? Is it stock JF6 with just root? If not provide firmware information and anything else that might be useful
P.S. Questions belong in the Q&A section

I'm not really sure what JF6 is haha...After I used Odin and set it back to stock conditions, the only thing I did was use the One Click Root.

As far as sideloading goes, the One Click De-Cripple method on page 2 of the general forum worked for me. If you want to know what version your phone is, go to the about phone section under your settings menu. If you need or want to upgrade to JH7, which was the last OTA update from ATT, do a search and there are a few options out there for that.

Well unfortunately I cannot use OCD on Mac..I tried to do the command prompts, but the su is asking for a password, which is odd because the way I understand it, it shouldn't be doing that

goosefraba91 said:
Well unfortunately I cannot use OCD on Mac..I tried to do the command prompts, but the su is asking for a password, which is odd because the way I understand it, it shouldn't be doing that
Click to expand...
Click to collapse
You did type adb shell first right? Then you should get a "$" where you then type su. It then echoes back su and you should see a "#".
From what you just said, it sounds like you're attempting to get root access on your mac through terminal, which in that case should be your password.

miztaken1312 said:
You did type adb shell first right? Then you should get a "$" where you then type su. It then echoes back su and you should see a "#".
From what you just said, it sounds like you're attempting to get root access on your mac through terminal, which in that case should be your password.
Click to expand...
Click to collapse
Ok, I got that to work. Now I'm just having trouble entering the code for mac. Like I said, I'm not very savvy with this stuff, so pardon my ignorance, haha.
I'm using the method in the "How to: Remove (Almost) Every Trace of AT&T" thread. (I would post a link, but since I'm a new user, it won't let me)
Is there anything different that I need to put into terminal other than the "./adb"?

I tried to paste the link to this thread but being a new member I am not allowed to post a link because of spam issues. Do a google search for "how to enable non market apps on captivate consolidated" and this will be the first xda thread that comes up.
This thread gives several methods for permanent enabling of sideloading. Being a noob, all of them were a little intimidating to me except for METHOD 3. You don't need a computer and you can do it all on your phone with Root Explorer, SQ Lite, and Terminal Emulator which are all available on the market. The step by step is pretty good and I have done it twice with no issues.

Roof King said:
I tried to paste the link to this thread but being a new member I am not allowed to post a link because of spam issues. Do a google search for "how to enable non market apps on captivate consolidated" and this will be the first xda thread that comes up.
This thread gives several methods for permanent enabling of sideloading. Being a noob, all of them were a little intimidating to me except for METHOD 3. You don't need a computer and you can do it all on your phone with Root Explorer, SQ Lite, and Terminal Emulator which are all available on the market. The step by step is pretty good and I have done it twice with no issues.
Click to expand...
Click to collapse
That method worked great. Thank you!

No prob!
Happy Modding!

Glad you got it working. For the record, the next time you guys wanna post links, just replace the http in the front with hxxp. Most people will fix it when they copy/paste it
Sent from my Captivate

[Q] Already Rooted Honeycomb Preview v4 Exists?

Is there an already rooted version of deeper-blue's Honeycomb preview image v4 anywhere?
I'm at wits end getting connected through ADB to my NC on my Laptop (running Ubuntu). I've tried about every walk through I can find. Including the one on NookDevs. I've had no issues connecting to other devices through ADB in the past.
I'd love to be able to use adbWireless. However I have to root before I can do that which requires ADB access ...
So I was just curious if there's an "already rooted" image floating around anywhere? I couldn't find one on XDA. I figure if it's not posted here it doesn't exist. I thought I'd ask though.
Edit: Looking for one that boots off of the SDCard

Like this?
http://forum.xda-developers.com/showthread.php?t=947071

Keep in mind to use that su update. The one in that link had a advertisement line if code after requesting su so it messes alot of stuff up. The su update is in a cm7 gapps thread in android development
Sent from one of those missing Droids

RickOSidhe said:
Like this?
http://forum.xda-developers.com/showthread.php?t=947071
Click to expand...
Click to collapse
I was actually looking for one that boots off of the SDCard. Sorry I should have specified that. I've updated my first post. I'll most likely flash to internal memory when the official Honeycomb source is released and there's a final version.
altimax98 said:
Keep in mind to use that su update. The one in that link had a advertisement line if code after requesting su so it messes alot of stuff up. The su update is in a cm7 gapps thread in android development
Sent from one of those missing Droids
Click to expand...
Click to collapse
Thanks for the heads up on that.

How do I root the frk76 OTA update?

I don't run any roms just root. I received the OTA update lastnite and without thinking, I allowed it to update. I usually use SuperOneClick but that doesn't seem to work with this update. I have searched high and low and can't find any information on rooting this. Any help is appreciated.

SOLVED. I reverted to SuperOneClick 1.7 and used rageagainstthemachine and it worked after a reboot. zergRush in 2.2 doesn't seem to work against this update.

SuperOneClick 2.2.2 Will Work With FRK76 if...
I took the rageagainstthecage exploit file from SuperOneClick 1.7 and placed it in the "Exploits" sub-directory of SuperOneClick 2.2.2 and it worked as well after a reboot. Note: You'll get a warning message about it's incompatibility with Android 2.3 + (not an issue as FRK76 is 2.2.3)

Don't know what the above means
Does 2.3.1 work without modification?

While I still have my 2 year old droid, I don't have my windows computer any more. Is there any way to do this with a Mac?

Noob needing help
sir_lunatic said:
I don't run any roms just root. I received the OTA update lastnite and without thinking, I allowed it to update. I usually use SuperOneClick but that doesn't seem to work with this update. I have searched high and low and can't find any information on rooting this. Any help is appreciated.
Click to expand...
Click to collapse
Good day, I've scoured the xda dev & android forums, and haven't been able to come up with a resolution to this: I let the OTA [FRK76 - 2.2.3] update slip through, and now i'm having issues rooting.
Besides the fact i'm running linux, i refuse to use any of the one click methods.. Would rather root manually so i know what's happening.
I'm running Ubuntu & doing this all through ADB / terminal, following the instructions listed in android forums [Rooting the Droid without rsd lite up to and including FRG83D], i get to step 13 and i still see the $ & not #.
As there anyone out there who can assist?
Thanks much in advance!

sir_lunatic said:
SOLVED. I reverted to SuperOneClick 1.7 and used rageagainstthemachine and it worked after a reboot. zergRush in 2.2 doesn't seem to work against this update.
Click to expand...
Click to collapse
how does one get an older version of SuperOneClick 1.7?

envoy510 said:
Does 2.3.1 work without modification?
Click to expand...
Click to collapse
As per i know it does not.

Pete has a stock rooted FRK76 Rom on his website, fyi

My D1 seems remarkably resistant to rooting. I downloaded SOC 2.3.3, added rageagainstthecage to the exploits folder, and it still won't even really get to the "Waiting for Device" command. It kills/boots the ADB daemon then hangs. If I kill one of the ADB processes manually, I can get it to skip the automatic version check and get to "Waiting for Device" but then nothing happens there, either.
Any help (or hell, an alternate rooting method- I'd do it the long way too) would be great.

flukehawkins said:
My D1 seems remarkably resistant to rooting. I downloaded SOC 2.3.3, added rageagainstthecage to the exploits folder, and it still won't even really get to the "Waiting for Device" command. It kills/boots the ADB daemon then hangs. If I kill one of the ADB processes manually, I can get it to skip the automatic version check and get to "Waiting for Device" but then nothing happens there, either.
Any help (or hell, an alternate rooting method- I'd do it the long way too) would be great.
Click to expand...
Click to collapse
The rageagainstthecage exploit works for the FRK76 build, but I couldn't get SuperOneClick to run without crashing, so I just did it manually.
Download SuperOneClick 1.7
Extract, and use the rageagainstthecage, busybox, su, Superuser.apk with this guide: http://forum.xda-developers.com/showpost.php?p=8315805&postcount=2
The only difference is the block device /system is mounted from (the guide says mtdblock3, and I think on the droid it is mtdblock4). Just type `mount` on the command line and look for the line that has /system and check the mount path.

I used superoneclick 1.7 to root a stock frk76.
On a note to new users...if you are on windows 7, I could not get it to work. I had an old xp machine that I downloaded soc1.7 to, when I first tried to run it, my PC posted an error about .net 2.0 framework. I Google, found, and downloaded the net 2 0 framework and it worked instantly.
It did not give me recovery. I used rsdlite and only rsd recovery after I rooted it to install cwm. Once you install cwm go directly to it and flash your new rom.
For me, after I rooted and had a stock rom, my recovery would not survive a reboot. But after moving cm7 and gapps to my SD card, re-rsd recovery. Booted directly to recovery. Flashed. Once booted I went to rom manager and had it reflash cwm recovery again and it never had another issue.
My steps may sound confusing but this is what I did.
I do not have sdk setup completely on my laptop and found this to be extremely easy. It works 100% and supplied no errors. I hope this helps someone else.

Is there a RUU i can run to unroot my phone?

YoungCorruptionV2.0 said:
Is there a RUU i can run to unroot my phone?
Click to expand...
Click to collapse
No ruu on here but you can simply flash an unrooted stock rom and accept updates thru Verizon.

stkiswr said:
No ruu on here but you can simply flash an unrooted stock rom and accept updates thru Verizon.
Click to expand...
Click to collapse
Ah okay thanks for the tip. I'll look in the development section for one

YoungCorruptionV2.0 said:
Ah okay thanks for the tip. I'll look in the development section for one
Click to expand...
Click to collapse
You may be able to find it on rom manager but def can find it on peter Alfonso site

App that runs the 2 Pie root commands from the phone

since the phone maintains the 2 pushed files on the phone after reboot, is it possible to make an app that can be run from the phone itself to run the two adb commands of Pie root that do the rooting?

Well Google now doesn't work worth an iPhone. .I've spoken those last two lines ADB shell commands out loud for the past 15 minutes and I don't get root

You cannot do it from the phone. That method lacks sufficient permissions
Sent from my XT1058 using XDA Free mobile app

Neighbor808 said:
You cannot do it from the phone. That method lacks sufficient permissions
Sent from my XT1058 using XDA Free mobile app
Click to expand...
Click to collapse
I'm starting to believe you....

doitinthedirt said:
I'm starting to believe you....
Click to expand...
Click to collapse
We KNOW that the commands MUST be run from ADB (and not from a SHELL, as your screenshot shows you have tried).....
But before we discount the idea completely, perhaps an experienced DEV could commend on this possibility:
Guys, have a look at this thread regarding running adb commands (through adb wireless) from another android device:
http://androidforums.com/android-applications/783226-run-adb-shell-another-android-phone.html
See the last 2 posts. This user successfully connected one android device to another via WiFi and was able to run adb commands.
Now first, I know that "ADB Wireless" requires root access, however there are 2 non-root variants aptly called "ADB Wireless (No Root)" -- see the play store.
Having read up on those specific apps, I've found that they require you to first connect the USB cable to the PC, and run an adb command to activate ADB over WiFi. What I'm not sure about is if you must do this each time the phone is rebooted. If not, then we have the possibility to actually run adb commands through TCP/IP possibly from the phone itself.
Consider the possibility of using the loop-back address...for instance: adb connect 127.0.0.1 in order to achieve a connection to the device itself.
If the adb command to activate adbwireless on non-rooted devices must be run each time the phone is rebooted, then this solution is probably going to go nowhere....but its worth checking out nonetheless....
We would definitely need a working adb binary for the Moto X in order for this to be possible at all.
See this link: http://forums.androidcentral.com/be...ol-native-adb-fastboot-your-phone-tablet.html
This user has repacked the adb and fastboot binaries (called "kadb" and "kfastboot") so they can be run on an android device itself. The intention is to use USB-OTG to connect another android device and run adb commands on the connected device.
^^ This definitely shows that it is possible to at least run adb commands from another android device connected via USB-OTG.
I know that many users are looking for a way to use PIE without having to connect to the PC after each reboot, hence the reason the "TowelRoot" app has had so much interest...
Unfortunately, TowelRoot has inherent limitations, because of the SU context (Non--Trusted App) as I understand. Several of us (myself included) have attempted to reach out to the developer for comment as to why this SU context is being used, and whether or not it can be modified to use the "Kernel" SU context that jcase is using with PIE, but none of us have received a response....
Do any experienced DEVS care to comment on the possibility of using the methods I have described, or something similar?
EDIT: Also, @doitinthedirt : have you tried to unlock your bootloader via the middleman? Or do you have a 2013 variant that he can not access the code for? The BL unlock solution is far superior to any of these temp-root methods, and it is permanent. (disregard if you already know this and are unable to obtain a code...)

I was running those commands from the same phone.. it was on a wifi network only to access internet. i used an app https://play.google.com/store/apps/details?id=com.spartacusrex.spartacuside
Only had about 10 minutes to mess around with it.. going to experiment more tonight.. and another app https://play.google.com/store/apps/details?id=jackpal.androidterm
The wireless from my nexus 7 was going to be my next try if i I couldnt get anywhere running from phone itself. And no I have not tried the middleman.. phone is july 3 2014 make so going to send a paypal to him and see if i get a code to unlock.

Getting nowhere..

doitinthedirt said:
Getting nowhere..
Click to expand...
Click to collapse
I appreciate your enthusiasm, but you are still trying to run the commands from a terminal SHELL. We -know- that this won't work. I'm not sure you understand what I was trying to express in my earlier post. I will attempt to experiment with the kadb binary, but you shouldn't continue trying to do this from ANY terminal emulator - it simply won't work, as @Neighbor808 has correctly advised...
Both of the apps you have linked ARE terminal emulators (hence running from SHELL).
If an experienced DEV could read my post, they might be able to comment further.
EDIT: I believe this is a lost cause:
From the dev who compiled the kadb binary: "Note : You do not need to be rooted, you do however need a custom recovery or temp boot a custom recovery."
This means that it should -absolutely- work for those of us who are unlocked, but definitely not temp-rooted.
Additionally, the AdbWireless method seems to fall short as well. It will probably work, but only if you connect to your PC first to run an ADB command to activate adb over WiFi, which defeats the whole idea of not having to use a PC.
The only method that IS viable for those of you using PIE, is the USB-OTG method. If you have ANOTHER android device (NOT your X) that:
1. has custom recovery
and
2. supports USB-OTG
Then you could purchase a USB-OTG cable, install the flashable zip containing the kadb and kfastboot binaries from the post I linked earlier, and run the ADB commands FROM the 2nd device.
This may be an option for you. Assuming you have installed custom recovery on your Nexus 7 (it definitely supports USB-OTG), you should be able to install the flashable zip, and run the commands from your Nexus 7 (just like you would from a PC, except using the command "kadb" instead of "adb".....i.e.:
kadb shell chmod 755 /data/local/atvc/root.sh
kadb shell /data/local/atvc/root.sh
I see no reason that this would not work....all the other methods I suggested have been eliminated as possibilities during my research/testing.
I don't, however, see how this is any better than simply connecting to your pc and running the adb commands the traditional way.
Good Luck
---------- Post added at 02:48 AM ---------- Previous post was at 02:19 AM ----------
doitinthedirt said:
Well Google now doesn't work worth an iPhone. .I've spoken those last two lines ADB shell commands out loud for the past 15 minutes and I don't get root
Click to expand...
Click to collapse
Oh wow! I missed this post. You are joking, right? You've --spoken-- the commands to Google Now?!?! LMFAO + ROFL + LOL....I just can't find a way to express just how humorous this post is
Good One :silly:

Use towel root if your trying to root from your phone.
Sent from my XT1058 using XDA Premium 4 mobile app

Thanks Sir, towelroot does not root my moto X

[email protected] said:
Use towel root if your trying to root from your phone.
Sent from my XT1058 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
This:
samwathegreat said:
I know that many users are looking for a way to use PIE without having to connect to the PC after each reboot, hence the reason the "TowelRoot" app has had so much interest...
Unfortunately, TowelRoot has inherent limitations, because of the SU context (Non--Trusted App) as I understand. Several of us (myself included) have attempted to reach out to the developer for comment as to why this SU context is being used, and whether or not it can be modified to use the "Kernel" SU context that jcase is using with PIE, but none of us have received a response....
Click to expand...
Click to collapse

samwathegreat said:
This:
Click to expand...
Click to collapse
Oh yeah? What about this?
Sent from my XT1058 using XDA Premium 4 mobile app

[email protected] said:
Oh yeah? What about this?
Sent from my XT1058 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Um... Pointing out the inherent limitations of the towel root and why it doesn't work for many and causes issues for others. I'm going to assume that because you are using the XDA app, you didn't see the quote attached to my post, but if you view it in a browser you should understand the point I was making...
I'm glad that towel root is actually working for you. Are you experiencing the random reboots?

[email protected] said:
Use towel root if your trying to root from your phone.
Sent from my XT1058 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
towel root will not work on the motoX

it doesn't work for Him I get that same screen saying you should have root but if he would bother checking with file explorer root access he will find out he doesn't have root

yamaha83 said:
towel root will not work on the motoX
Click to expand...
Click to collapse
Not entirely accurate. Some have managed to use after rooting with PIE, but it does cause issues for many and (once again) has inherent limitations due to the SU context being used.
---------- Post added at 02:26 PM ---------- Previous post was at 02:22 PM ----------
doitinthedirt said:
it doesn't work for Him I get that same screen saying you should have root but if he would bother checking with file explorer root access he will find out he doesn't have root
Click to expand...
Click to collapse
I don't think hovax is foolish enough to mistakenly believe he has root when he does not lol. He has obviously managed to get it to work for him, as have many others. I am curious if he is experiencing the problems that many others are with towel root, however.

a simple screenshot showing root access in system folder like this one from my other moto x running ios 4.4 rooted with slap, that will convince me

doitinthedirt said:
is it possible to make an app that can be run from the phone itself to run the two adb commands of Pie root that do the rooting?
Click to expand...
Click to collapse
If it was possible, I would have thought JCASE would have released it that way, instead of having to do the process while connected to the PC.

doitinthedirt said:
a simple screenshot showing root access in system folder like this one from my other moto x running ios 4.4 rooted with slap, that will convince me
Click to expand...
Click to collapse
You have to realize that many users including hovax are much more experienced than you seem to be. All the proof you should need is located in the towel root discussion thread.
Remember: you were trying to -speak- adb commands using Google now in order to root your phone...
Some of your comments are likely being taken as insults...
EDIT: I won't be posting any further in this thread. This idea is going nowhere and (obviously) does not belong in the original android development sub-forum.
EDIT2: Mods moved the thread to the appropriate location, so I will continue posting here.

I dont believe anyone has ever rooted an x with tr. all you get is the page pictured in the post above by the guy saying tr says you should have root... ive got it on two moto xs a broken one and a replacement one both on 4.4.2 and fx explorer and root checker confirm no root. one is 15 april 2014 build and the other is 03 july 2014 build. both fail under tr.

OnePlus left a backdoor in its devices capable of root access

Just a month ago, OnePlus was caught collecting personally identifiable data from phone owners through incredibly detailed analytics. While the company eventually reversed course on the data collection, another discovery has been made in the software of OnePlus phones. One developer found an application intended for factory testing, and through some investigation and reverse-engineering, was able to obtain root access using it.
Read more Androidpolice:
http://www.androidpolice.com/2017/11/13/oneplus-left-backdoor-devices-capable-root-access/

Does anyone know if uninstalling that app via adb (without root: https://www.google.nl/amp/s/www.xda...arrier-oem-bloatware-without-root-access/amp/) will cause any problems?

swa100 said:
Does anyone know if uninstalling that app via adb (without root: https://www.google.nl/amp/s/www.xda...arrier-oem-bloatware-without-root-access/amp/) will cause any problems?
Click to expand...
Click to collapse
You can root easily using the EngineerMode APK then (after that) uninstall it! ::

I'm trying to push the su binaries, but when I try to mount /system as rw using "mount -o rw,remount,rw /system" I get the following error:
Code:
mount: '/dev/block/dm-0'->'/system': Device or resource busy
Any ideas on how to get around this? Something to do with dm-verity?
Update:
Got the system to mount using:
Code:
mount -o rw,remount -t ext4 /dev/block/dm-0 /system
But whenever I try to push the su binary, the phone reboots.
Update 2:
SuperSu is now working. See https://www.reddit.com/r/oneplus/comments/7cuu0w/gain_root_via_the_recent_backdoor/

I think it's time to switch to aosp
Sent from my Oneplus 5 using Tapatalk

Waits patiently for him to push apk out to root without rooting

Yeah,im waiting/on it since morning.I did run the adb command,it says Root successfull in engineering mode app ,but Super su says Binary not found.
And the best part it has MR ROBOT references everywhere.
The guy who found exploit has twitter account themed MrRobot.
The final best one the IRONY,the password of backdoor is 'ANGELA'
Looks like fan of series in Oneplus or Qualcomm.

I will be incredibly happy even if the only thing this allows us to do is to install adaway without having to unlock bootloader, install custom recovery and all that...

I've found the app and set "Modify system settings" to "no". Would that stop someone giving root access? [I know it can be re-enabled, just asking]
Alan

IonAphis said:
I will be incredibly happy even if the only thing this allows us to do is to install adaway without having to unlock bootloader, install custom recovery and all that...
Click to expand...
Click to collapse
i don't understand what's the matter with unlocking the bootloader n flashing a custom recovery n everything ? what's the problem with it ?

ReyTheBoss said:
i don't understand what's the matter with unlocking the bootloader n flashing a custom recovery n everything ? what's the problem with it ?
Click to expand...
Click to collapse
Reasons.

This app "Engineer mode" is present in many "chinese" phones and in mediateks phones.
Personnaly, i'm not surprised but this exploit was never expoited before...
Time to install aosp rom... OnePlus is a youg company and i think security is not a priority for them

AOSP and other open source ROMs are most secure than Oxygen, but has too much bugs and requires more time to configure it.
Isn't a good solution to all users.

bartito said:
AOSP and other open source ROMs are most secure than Oxygen, but has too much bugs and requires more time to configure it.
Isn't a good solution to all users.
Click to expand...
Click to collapse
blinkin said:
I think it's time to switch to aosp.
Click to expand...
Click to collapse
I'm going to suggest the NoLimits ROM, which is based upon OOS but no spying junk; I'm not seeing the engineering mode app in the list of apps.
https://forum.xda-developers.com/on...xxx-nolimits-1-1-speed-ram-optimized-t3627121
(Don't be lazy; push yourself to learn something new.)
It's pretty stable and has a few nice bells and whistles which make it a compelling alternative to OOS.
If you want spying junk you can't easily get rid off, stick with OOS. If you want more control and better privacy, go with a custom ROM, even one that is based on OOS.

ReyTheBoss said:
i don't understand what's the matter with unlocking the bootloader n flashing a custom recovery n everything ? what's the problem with it ?
Click to expand...
Click to collapse
Same question here, is that hard to unlock the bootloader and install a custom recovery?
The only reason that I can think is because maybe someone that don't have access to a PC

ReyTheBoss said:
i don't understand what's the matter with unlocking the bootloader n flashing a custom recovery n everything ? what's the problem with it ?
Click to expand...
Click to collapse
Unlocking bootloader wipes of our data including internal storage. And we have to take backup whole data and restore once its done which is pain in the a$$

When will the APK come out to root? Hopefully before OnePlus patches it.

pacattack81 said:
When will the APK come out to root? Hopefully before OnePlus patches it.
Click to expand...
Click to collapse
But... The reason you gained access in the first place is because the app was there. When the app goes so does your root access. No?
I am surprised that no one is commenting on the weird apparent coincidence that the password is a theme on the same movie that the discoverer of the exploit is a fan on. Emphasis on "apparent". Anyone want to bet that we soon learn that the "discoverer" is either an OP or Qualcomm employee who had a hand of putting it there in the first place?
And finally, is there any apparent downside of just deleting this thing? Or a Magisk module to disable it, just like the one that got made for the other Spyware?

NoLimits is removing EngineeringMode app (and also other related apps) if you select the agressive debloating mode on install.
I have done it this morning on my rooted O+5.
Now I delete the following apps each time that I reinstall OOS:
Code:
/system/app/AndroidPay"
/system/app/BasicDreams"
/system/app/BookmarkProvider"
/system/app/BTtestmode"
/system/app/Calculator"
/system/app/Calendar"
/system/app/CalendarGoogle"
/system/app/Chrome"
/system/app/DMAgent"
/system/app/Drive"
/system/app/Duo"
/system/app/Email"
/system/app/EngineeringMode"
/system/app/EngSpecialTest"
/system/app/ExactCalculator"
/system/app/FaceLock"
/system/app/Gmail2"
/system/app/GoogleTTS"
/system/app/GoogleWallpaperPicker"
/system/app/LatinIME"
/system/app/LatinIme"
/system/app/LatinImeGoogle"
/system/app/LiveWallpapersPicker"
/system/app/LogKitSdService"
/system/app/Maps"
/system/app/messaging"
/system/app/Music2"
/system/app/MusicFX"
/system/app/NFCTestMode"
/system/app/OemAutoTestServer"
/system/app/OEMLogKit"
/system/app/OPBackup"
/system/app/OPBugReportLite"
/system/app/OPPush"
/system/app/OPSocialNetworkHub"
/system/app/OpenWnn"
/system/app/OPLauncher_aosp"
/system/app/OPWallpaperResources"
/system/app/PartnerBookmarksProvider"
/system/app/Photos"
/system/app/PhotosOnline"
/system/app/PicoTts"
/system/app/PrintSpooler"
/system/app/SecureSampleAuthService"
/system/app/SensorTestTool"
/system/app/Stk"
/system/app/talkback"
/system/app/Videos"
/system/app/WifiRfTestApk"
/system/app/YouTube"
/system/priv-app/Eleven"
/system/priv-app/Gallery2"
/system/priv-app/H2DefaultIconPack"
/system/priv-app/H2FolioIconPack"
/system/priv-app/H2LightIconPack"
/system/priv-app/Launcher3"
/system/priv-app/Launcher3-azaidi"
/system/priv-app/OPDeviceManager"
/system/priv-app/OPDeviceManagerProvider"
/system/priv-app/OneplusCircleIconPack"
/system/priv-app/OnePlusGallery"
/system/priv-app/OneplusIconPack"
/system/priv-app/OneplusSquareIconPack"
/system/priv-app/OPMms"
/system/priv-app/Snap"
/system/etc/usb_drivers.iso"
/system/bin/bugreport*"
/system/bin/fmfactorytest*"
/system/bin/oemlogkit"
/system/bin/WifiLogger_app"
CaptShaft said:
I'm going to suggest the NoLimits ROM, which is based upon OOS but no spying junk; I'm not seeing the engineering mode app in the list of apps.
https://forum.xda-developers.com/on...xxx-nolimits-1-1-speed-ram-optimized-t3627121
(Don't be lazy; push yourself to learn something new.)
It's pretty stable and has a few nice bells and whistles which make it a compelling alternative to OOS.
If you want spying junk you can't easily get rid off, stick with OOS. If you want more control and better privacy, go with a custom ROM, even one that is based on OOS.
Click to expand...
Click to collapse

I have two question to the people who actually have some knowledge. If I gain root access via ADB and that app:
1) will I be able successfully to flash OTAs in the future?
2) will the root disappear once the next ota is applied to my phone (in case the answer for the previous question is positive)?