Related
With the new OTA being released many are asking how to restore stock recovery. I think that the original /system/etc/install-recovery.sh file is required, unfortunately I did not make a backup. Does anyone have a copy of the original version of this file? Please post it here if you have it and anyone who knows how to restore stock recovery please post any helpful instructions here. If I get the file and proper instructions I will update the OP accordingly. Thanks.
I made a backup but have no idea how to extract that file.
You have to write which TPT you have.
US or....?
16, 32 or 64GB?
toenail_flicker said:
I made a backup but have no idea how to extract that file.
Click to expand...
Click to collapse
What did you backup with? If you backed it up after installing CWM then it was probably already gone (which is why I don't have it).
In the ROW instructions they cleverly added this line to the install instructions:
cp /system/etc/install-recovery.sh /system/etc/install-recovery.sh.backup
which creates a backup of the file in /system/etc/
If you did this then you should be able to copy the file install-recovery.sh.backup from /system/etc/ using root explorer or adb.
I have the US 32GB version, I'm not sure if the files are the same but I would guess that they are. Anyway if you can get the file that would be great.
I have 183827U 64GB. Yes, I made a Nandroid backup after installing CMW. I also have Titanium and MyBackup saves, but have no idea if they save the file. I'll go looking for it with RE and let you know what I find.
---------- Post added at 01:47 PM ---------- Previous post was at 01:41 PM ----------
Seems I have install-recovery.sh but the date is recent, so I guess it's from when I rooted. No backup of the same name.
Mine is:
#!/system/bin/sh
if ! applypatch -c EMMC:/dev/block/mmcblk0p1:2048:0a48c18ee1ca32bba5a785d8ea8b6976fc0a190e; then
log -t recovery "Installing new recovery image"
applypatch EMMC:/dev/block/mmcblk0p2:3170304:fa229b8ff37128302094316ea4ced3d68ad5edcf EMMC:/dev/block/mmcblk0p1 53a249cd150c483f9255eba03adccdf6e7c014a6 3524608 fa229b8ff37128302094316ea4ced3d68ad5edcf:/system/recovery-from-boot.p
else
log -t recovery "Recovery image already installed"
fi
WE-TPT-64GB
After installing MDL custom kernel and rooting I now have a persistent notification "Detection Information - The device has detected an application attempting unpermitted actions. To protect your device, it is recommended you reboot". Rebooting doesn't stop the notification from reappearing after about 5-10mins. I have tried clearing cache via custom recovery but doesnt help. Any ideas?
Thanks!
Use titanium backup or similar app to "freeze" seandroid.apk and reboot. Nag notification should be gone.
troyboytn said:
Use titanium backup or similar app to "freeze" seandroid.apk and reboot. Nag notification should be gone.
Click to expand...
Click to collapse
Thanks, can this be removed using a Root File Explorer? Also is there another free app I can download/use to freeze?
Dont remove it....not sure of negative implications of removal. Free version of System Tuner will let you freeze it I believe.
thettaccns
troyboytn said:
Dont remove it....not sure of negative implications of removal. Free version of System Tuner will let you freeze it I believe.
Click to expand...
Click to collapse
Thanks I was wondering what to do here...:good:
---------- Post added at 08:45 PM ---------- Previous post was at 08:09 PM ----------
Actually found this... No credit goes to me I'm just passing the info along...
How to disable ANNOYING messages "DETECTION Information":
Using TITANIUM BACKUP and FREEZING app called SEAndroid.apk DOESN'T WORK PROPERLY!!
DO NOT USE IT, YOUR SYSTEM WILL GO BACK TO CUSTOM AFTER SOME TIME!!! NOT RECOMMENDED!!!!
------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
1. Use File Manager with root explorer instead and mount SYSTEM as WRITABLE.
2. Go to: /data/data/ look for com.sec.knox.seandroid and rename it to 000.knox.seandroid or whathever you wish.. Same thing applies to com.sec.knox.store
3. Go to: /system/app/ and DELETE: KNOXAgent.apk, KNOXAgent.odex, KNOXStore.apk, KNOXStore.odex
updated:
After few hours of testing (MDL), and all updates there was NO messages at all!!
!!!SOLVED!!!
troyboytn said:
Dont remove it....not sure of negative implications of removal. Free version of System Tuner will let you freeze it I believe.
Click to expand...
Click to collapse
I actually have removed them completely and the message is gone. I have not seen it since. I have rebooted several times and even flashed the blue ICS Statusbar and blue center clock mod after that. No issues at all. I deleted both SEAndroid and that SamsungKNOX or whatever that was called. I deleted them through Rom Toolbox Pro (Amazing app well worth it the price)
Sent from my SPH-L720 using xda premium
Used this method and it worked just fine.
Followed the instruction in Post #5 and it works like a Charm
satanazh said:
Followed the instruction in Post #5 and it works like a Charm
Click to expand...
Click to collapse
Me too.
Excellent!
does it work without knox?
chicagoaan said:
Thanks I was wondering what to do here...:good:
---------- Post added at 08:45 PM ---------- Previous post was at 08:09 PM ----------
Actually found this... No credit goes to me I'm just passing the info along...
How to disable ANNOYING messages "DETECTION Information":
Using TITANIUM BACKUP and FREEZING app called SEAndroid.apk DOESN'T WORK PROPERLY!!
DO NOT USE IT, YOUR SYSTEM WILL GO BACK TO CUSTOM AFTER SOME TIME!!! NOT RECOMMENDED!!!!
------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
1. Use File Manager with root explorer instead and mount SYSTEM as WRITABLE.
2. Go to: /data/data/ look for com.sec.knox.seandroid and rename it to 000.knox.seandroid or whathever you wish.. Same thing applies to com.sec.knox.store
3. Go to: /system/app/ and DELETE: KNOXAgent.apk, KNOXAgent.odex, KNOXStore.apk, KNOXStore.odex
updated:
After few hours of testing (MDL), and all updates there was NO messages at all!!
!!!SOLVED!!!
Click to expand...
Click to collapse
I don't have KnOx yet. I reflashed back to MDC and pushed the stock kernel and CWM, and was ok until I installed SU... SU seems to be what is detected but I didn't have any issues until MF9 came out and kept overheating my phone, downloading all the time and failing because I had root and wifihack.
Kingmdm said:
After installing MDL custom kernel and rooting I now have a persistent notification "Detection Information - The device has detected an application attempting unpermitted actions. To protect your device, it is recommended you reboot". Rebooting doesn't stop the notification from reappearing after about 5-10mins. I have tried clearing cache via custom recovery but doesnt help. Any ideas?
Thanks!
Click to expand...
Click to collapse
I believe this happens because your not fully MDL and you have two different versions running at the same time. For example MDC with MF9 or MDL with MF9 or MDC with MDL. To actually remove it you need to upgrade fully to the version you want not mixed.
Sent from my SPH-L720 using xda app-developers app
ROMANTiC KiD said:
I believe this happens because your not fully MDL and you have two different versions running at the same time. For example MDC with MF9 or MDL with MF9 or MDC with MDL. To actually remove it you need to upgrade fully to the version you want not mixed.
Sent from my SPH-L720 using xda app-developers app
Click to expand...
Click to collapse
This is the answer.... follow this post:
http://forum.xda-developers.com/showpost.php?p=43418277
I made the same error and did follow the full instructions to install stock rooted rom
chicagoaan said:
Thanks I was wondering what to do here...:good:
---------- Post added at 08:45 PM ---------- Previous post was at 08:09 PM ----------
Actually found this... No credit goes to me I'm just passing the info along...
How to disable ANNOYING messages "DETECTION Information":
Using TITANIUM BACKUP and FREEZING app called SEAndroid.apk DOESN'T WORK PROPERLY!!
DO NOT USE IT, YOUR SYSTEM WILL GO BACK TO CUSTOM AFTER SOME TIME!!! NOT RECOMMENDED!!!!
------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
1. Use File Manager with root explorer instead and mount SYSTEM as WRITABLE.
2. Go to: /data/data/ look for com.sec.knox.seandroid and rename it to 000.knox.seandroid or whathever you wish.. Same thing applies to com.sec.knox.store
3. Go to: /system/app/ and DELETE: KNOXAgent.apk, KNOXAgent.odex, KNOXStore.apk, KNOXStore.odex
updated:
After few hours of testing (MDL), and all updates there was NO messages at all!!
!!!SOLVED!!!
Click to expand...
Click to collapse
Thank you so much
chicagoaan said:
Thanks I was wondering what to do here...:good:
---------- Post added at 08:45 PM ---------- Previous post was at 08:09 PM ----------
Actually found this... No credit goes to me I'm just passing the info along...
How to disable ANNOYING messages "DETECTION Information":
Using TITANIUM BACKUP and FREEZING app called SEAndroid.apk DOESN'T WORK PROPERLY!!
DO NOT USE IT, YOUR SYSTEM WILL GO BACK TO CUSTOM AFTER SOME TIME!!! NOT RECOMMENDED!!!!
------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
1. Use File Manager with root explorer instead and mount SYSTEM as WRITABLE.
2. Go to: /data/data/ look for com.sec.knox.seandroid and rename it to 000.knox.seandroid or whathever you wish.. Same thing applies to com.sec.knox.store
3. Go to: /system/app/ and DELETE: KNOXAgent.apk, KNOXAgent.odex, KNOXStore.apk, KNOXStore.odex
updated:
After few hours of testing (MDL), and all updates there was NO messages at all!!
!!!SOLVED!!!
Click to expand...
Click to collapse
Could you please tell me how to mount the system as writable. Thanks
chicagoaan said:
Thanks I was wondering what to do here...:good:
---------- Post added at 08:45 PM ---------- Previous post was at 08:09 PM ----------
Actually found this... No credit goes to me I'm just passing the info along...
How to disable ANNOYING messages "DETECTION Information":
Using TITANIUM BACKUP and FREEZING app called SEAndroid.apk DOESN'T WORK PROPERLY!!
DO NOT USE IT, YOUR SYSTEM WILL GO BACK TO CUSTOM AFTER SOME TIME!!! NOT RECOMMENDED!!!!
------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
1. Use File Manager with root explorer instead and mount SYSTEM as WRITABLE.
2. Go to: /data/data/ look for com.sec.knox.seandroid and rename it to 000.knox.seandroid or whathever you wish.. Same thing applies to com.sec.knox.store
3. Go to: /system/app/ and DELETE: KNOXAgent.apk, KNOXAgent.odex, KNOXStore.apk, KNOXStore.odex
updated:
After few hours of testing (MDL), and all updates there was NO messages at all!!
!!!SOLVED!!!
Click to expand...
Click to collapse
I'm having issues with this constant error message, looked to find the above files and I have nothing. To search for the above file, I used Root Explorer. I'm using the FreeGS4 ROM and use Team Win Recovery. Would using a different ROM fix the issue? Any help getting this annoying message to go away would be appreciated. Everything works fine, it's this constant nagging of a message.
Hi guys,
Just got one of this cheap phones and after unlocking and rooting it (txs to PaulOBrien for that) I got the annoying:
Code:
Parse error
There was a problem while parsing the package
Tried a couple of things, reboots, settings, factory reset but nothing helped but found some easy workaround (Google Drive is not an option for me, not when I'm with no network)
Looks like all these problems are due some fancy security crap in new 4.2/.3 versions (never got it before in any of my previous devices)
Just move the APK to some other directory, adjust the permissions (need group read but just do 777) and install it from there.
"/mnt/obb" is a tmp dir, so anything there will disappear on the next book.
"/data/local/tmp" is what "adb install" uses so it is a good choice.
old post below
So for whoever still has the problem, go and try these steps:
1. Create a directory inside /mnt/obb/ (e.g: /mnt/obb/Apks)
Code:
d:\ADB>adb shell
[email protected]_umts:/ $ su
su
[email protected]_umts:/ # mount -o rw,remount /system
mount -o rw,remount /system
[email protected]_umts:/ # mkdir /mnt/obb/Apks
mkdir /mnt/obb/Apks
[email protected]_umts:/ # chmod 777 /mnt/obb/Apks
chmod 777 /mnt/obb/Apks
[email protected]_umts:/ # ls -la /mnt/obb
ls -la /mnt/obb
drwxrwxrwx root root 2023-12-09 18:46 Apks
[email protected]_umts:/ #
[email protected]_umts:/ # exit
exit
127|[email protected]_umts:/ $ exit
exit
d:\ADB>
2. Now, from whatever file browser you already have on your phone (I'm using Total Commander)
just copy the apk from your "sdcard" to the /mnt/obb/Apks directory
3. Adjust the permissions for the apk file (744 or rwxr--r--)
(I could added some pictures but I'm too lazy
Now it should allow you to install without the bloody error.
So to summarize the trick is to create a directory somewhere else and install the apk from there. It is not good as before, but at least I don't need an internet connection, just move the file, change permissions and install.
Will try to find out why the normal method fails (whenever I have some free time). Tthe way that is mounting the 'external' storage is causing this issue.
I guess in a couple of weeks we will get new builds or a original Motorola fix, but in the meantime this is good enough for me.
Note: /mnt/obb may go after a reboot so try to find a "permanent" one
You don't need adb to create the directory, you can do all these from the phone, just remember to adjust the permissons for the directory.
Another workaround is also to copy the apks to a usb stick and mount the usb stick with a otg cable.
Install then as usual the apks with a file explorer.
I tried that and it works fine!
Or you can just use Astro explorer. Works for me...
Enviado desde mi XT1032 mediante Tapatalk
DaRkToU said:
Or you can just use Astro explorer. Works for me...
Enviado desde mi XT1032 mediante Tapatalk
Click to expand...
Click to collapse
If you can install with Astro you can install with any other file manager, so unfortunately this does not apply to you
I does. I have the same problem, I was using Google drive but I tried with Astro and it works.
Sent from my Moto G
---------- Post added at 09:52 PM ---------- Previous post was at 09:37 PM ----------
Quick update, I've just tried on another phone and it didn't work...
Sent from my Moto G
DaRkToU said:
I does. I have the same problem, I was using Google drive but I tried with Astro and it works.
Sent from my Moto G
---------- Post added at 09:52 PM ---------- Previous post was at 09:37 PM ----------
Quick update, I've just tried on another phone and it didn't work...
Sent from my Moto G
Click to expand...
Click to collapse
The problem is with the permissions of the apk so the file manager should make no difference.
I did also tried with Astro before and got the same "Parse error", to me the only way to avoid it is use a external as vampy2k5 said, or a different directory in the file system.
solution
just upload the apk file to google drive and intall from there. works every time, no permissions mod no nothing
tampitzel said:
just upload the apk file to google drive and intall from there. works every time, no permissions mod no nothing
Click to expand...
Click to collapse
Good, can I apply your "solution" if I have no internet connection?
dubidu said:
Good, can I apply your "solution" if I have no internet connection?
Click to expand...
Click to collapse
i totally see how this could be a problem. i guess you're better off with moving the app in a folder with permissions set?
I dont think this belongs to "ANDROID DEVELOPEMENT" SECTION.. It would do good in General section..
Thread Reported !!
thank you,
Mr.Gm
Factory reset solved it for me
For me the "upload to google drive" thing doesn't work.
same here, im working on a custom version of the stock rom to try getting around it
crondom said:
For me the "upload to google drive" thing doesn't work.
Click to expand...
Click to collapse
Guys i've noticed that only certain apps doesn't work with google drive, others (majority of them) works.
crondom said:
Guys i've noticed that only certain apps doesn't work with google drive, others (majority of them) works.
Click to expand...
Click to collapse
Also, logging onto GDrive via ES Explorer, or whatever, won't work either
However, logging on directly using the G Drive App works OK, accessing and installing the same apk...weird.
I ve got this bug - Moto G 16 GB tesco
(As far as I remember retail germans got OTA with bugfix for this)
After factory resetting it 3 times and getting no joy, I did this and it worked:
Didn't backup settings, skipped wifi, skipped Google login, connected mobile to PC, transferred apk to mobile, logged into Play Store, downloaded a browser, opened and it worked.
No idea if I got lucky, or did something relevant, but it worked
Piaer said:
I ve got this bug - Moto G 16 GB tesco
(As far as I remember retail germans got OTA with bugfix for this)
Click to expand...
Click to collapse
I have a Tesco 16GB, have no problems with installing APPS placed in the internal storage, hard to explain why some are having problems.
ilike123 said:
I have a Tesco 16GB, have no problems with installing APPS placed in the internal storage, hard to explain why some are having problems.
Click to expand...
Click to collapse
This is the real workaround without needing to upload to GDrive.....
just copy or move the apk from /sdcard/xxx folder [wherever it is] to a folder in the system, like /data/any_temp_folder.
The apk will install normally then.....
irishpancake said:
This is the real workaround without needing to upload to GDrive.....
just copy or move the apk from /sdcard/xxx folder [wherever it is] to a folder in the system, like /data/any_temp_folder.
The apk will install normally then.....
Click to expand...
Click to collapse
I place the apk's in XT1032 > Internal storage, they install just fine from here, no need for any extra folders
After coming from a fresh rom install, I've been trying to install adw ex but have had issue after issue.
If I try to go through Titanium, it just hangs and never installs. If I try to install from the standalone apk, the app isn't installed.
I've even tried going through Lucky Patcher, but I get an error reading "You must uninstall application before installing this apk, as the signatures are different after the recompiling." When I try to uninstall it, I get another error.
I'm thinking there has to be some piece of this apk that's still not totally uninstalled to be giving me this error. Regular adw installs without a problem but any version of adw ex comes with an error.
Any suggestions?
Edit: I've tried wiping data and cache to no effect.
Sent from my Nexus 4 using xda premium
Same problem here
---------- Post added at 11:51 AM ---------- Previous post was at 11:04 AM ----------
If you have experience in android you can do the following
But first you must have android development tools installed...since we want to make use of "adb"
Connect your phone to the computer and make sure that usb debugging is on
On the computer,open your terminal and creat directory to the folder where the adb file is found
In my case,
./adb install -l /"Directory where the apk file is found"
That's all
Hope that helps,it worked with me :good:
Hello
I am coming to the g4 plus after having used the samesung s5 for years on MOAR rom and i am looking for how i can get my mobile hotspot back on sprint
I get Unable to connect to data network you may not be subscribed to .....
now i do not have a wifi plan per se but i do have a really old phone as a modem plan i am still paying for (back then it was 10$ a month for unlimited 2008)
so first thing i did was look for where to modify the apn settings for tethering like i had to do before but when the phone activates on sprint the apn menu disapears.
so i look for a custom rom like MOAR but for the g4 plus and i am not seeing any that say they have wifi hacks included
I did this successfully on the nougat soak, but requires root access. Add this line at the end of your build.prop (I used Root Explorer to edit the file):
net.tethering.noprovisioning=true
Save build.prop and reboot phone. Then, in the terminal emulator app, issue the following commands one at a time:
su
settings put global tether_dun_required 0
exit
Reboot phone again.
---------- Post added at 04:39 PM ---------- Previous post was at 04:30 PM ----------
You might want to try it after the build.prop edit to see if it works, the terminal emulator commands may not be necessary.
i just use airdroid for hotspot
I will take a look at airdroid tomorow if it works great if not ill have to dig into the build.prop was trying to avoid that with a ready made rom
this brings back memories of reg'editing my htc titan lol
shkrmkr said:
I did this successfully on the nougat soak, but requires root access. Add this line at the end of your build.prop (I used Root Explorer to edit the file):
net.tethering.noprovisioning=true
Save build.prop and reboot phone. Then, in the terminal emulator app, issue the following commands one at a time:
su
settings put global tether_dun_required 0
exit
Reboot phone again.
---------- Post added at 04:39 PM ---------- Previous post was at 04:30 PM ----------
You might want to try it after the build.prop edit to see if it works, the terminal emulator commands may not be necessary.
Click to expand...
Click to collapse
This totally worked on my 1625, tethering was ghosted out. After this it works. Thank you
Sent from my Moto G4 using Tapatalk
robot_head said:
This totally worked on my 1625, tethering was ghosted out. After this it works. Thank you
Sent from my Moto G4 using Tapatalk
Click to expand...
Click to collapse
You used both or only the build.prop edit. I can add it to source in that case. And is this issue only with 1625 variant?
The compliance with the provider setting is well known for Moto phones (at least the ones sold in US). I am using an app from here on XDA called Entitlement Bypass:
https://forum.xda-developers.com/moto-x/themes-apps/app-hotspot-entitlement-bypass-v1-1-5-9-t2705152
This works perfect. I used the build.prop edit and su command. Completely opened tethering.
shkrmkr said:
I did this successfully on the nougat soak, but requires root access. Add this line at the end of your build.prop (I used Root Explorer to edit the file):
net.tethering.noprovisioning=true
Save build.prop and reboot phone. Then, in the terminal emulator app, issue the following commands one at a time:
su
settings put global tether_dun_required 0
exit
Reboot phone again.
---------- Post added at 04:39 PM ---------- Previous post was at 04:30 PM ----------
You might want to try it after the build.prop edit to see if it works, the terminal emulator commands may not be necessary.
Click to expand...
Click to collapse
This worked for my XT1644. Tethering and hospot option was grayed out in settings on custom ROMs, until doing this build prop edit. I did not have to run the commands, build prop edit solved my issue. Thank you so much.
When I rooted first time,I faced this problem of hotspot. I then installed elementalx in my device which solved the problem.
shkrmkr said:
I did this successfully on the nougat soak, but requires root access. Add this line at the end of your build.prop (I used Root Explorer to edit the file):
net.tethering.noprovisioning=true
Save build.prop and reboot phone. Then, in the terminal emulator app, issue the following commands one at a time:
su
settings put global tether_dun_required 0
exit
Reboot phone again.
---------- Post added at 04:39 PM ---------- Previous post was at 04:30 PM ----------
You might want to try it after the build.prop edit to see if it works, the terminal emulator commands may not be necessary.
Click to expand...
Click to collapse
This does work on Motorola G5 plus unlocked from best bye bye using ATnT.
Unrooted XT1644. AT&T provider. Tethering & portable hotspot option is accessible, but when I click on it I encounter "account not set up for tethering...." Could I access the build prop edit via an ADB command or script?
EDIT: Nevermind. My phone's bootloader is locked so no ADB access possible anyway. Looks like I'll need to look into 3rd-party WiFi tethering apps (such as PdaNet+ or NetShare) non-root solutions.