Database Develop

[Q] Apps & WIFI/4G Connection Failed after Rooting with Towelroot

Hi All,
I followed ALL the instructions (and verified root work with SuperSU) on this website galaxynote3root using towelroot (sorry I can't post external link) and everything appeared to be working perfectly fine. However, after a few minutes I ran into problems:
1. First, apps like Youtube, Map, Google Play, Chrome, Browser, Netflix … all pop up with error “Unfortunately, [app name] has stopped”.
2. Phone won’t connect to internet. Any app that uses internet connection won’t work. Both WIFI and 4G connections appear to connect, but no content could be served.
3. Phone won’t see content of External SD card or internal SD storage area. Attempting to look at these storage areas results in “Empty” folder.
4. Google Play shows “No Connection” message.
5. Attempt to run PvZ game gives me this error “Unfortunately, the process com.google.process.gapps has stopped.” The game still works, though.
I can still make phone calls, but that is it. I tried to clear cache, turned off/forced close Google Framework Services, Google Play … but still didn’t help.
The only thing that I changed, other than installing tr.pkg and supersu.pkg above, was the platform.xml. In the WRITE_EXTERNAL_STORAGE tag, I found two entries:
<group gid=”sdcard_r” />
<group gid=”sdcard_rw” />
I replaced the first entry with:
<group gid=”media_rw” />
in < permission name=”android.permission.WRITE_EXTERNAL_STORAGE” >
After seeing the errors, I replaced the xml file with original version. That didn’t help. Rebooting, turning off, removing batteries multiple times didn’t help. I un-rooted the phone using the “full unroot” feature in SuperSu, and that didn’t help either. I went into Settings and turned KNOX back on, still didn’t help.
At this point, I am stuck. I don’t know what else I should try. I would appreciate any help and suggestions, I would like to avoid resetting or doing more substantial changes to the phone, though.
One more note: I was using ES File Explorer and granted its root access. I don't know if that caused the issues but I just uninstalled it, still no help. Phone while booting shows Samsung Note 3 logo and an unlock Icon with the word Custom.
My phone has Android version 4.4.2
Thank you.

vbcomer said:
Hi All,
I followed ALL the instructions (and verified root work with SuperSU) on this website galaxynote3root using towelroot (sorry I can't post external link) and everything appeared to be working perfectly fine. However, after a few minutes I ran into problems:
1. First, apps like Youtube, Map, Google Play, Chrome, Browser, Netflix … all pop up with error “Unfortunately, [app name] has stopped”.
2. Phone won’t connect to internet. Any app that uses internet connection won’t work. Both WIFI and 4G connections appear to connect, but no content could be served.
3. Phone won’t see content of External SD card or internal SD storage area. Attempting to look at these storage areas results in “Empty” folder.
4. Google Play shows “No Connection” message.
5. Attempt to run PvZ game gives me this error “Unfortunately, the process com.google.process.gapps has stopped.” The game still works, though.
I can still make phone calls, but that is it. I tried to clear cache, turned off/forced close Google Framework Services, Google Play … but still didn’t help.
The only thing that I changed, other than installing tr.pkg and supersu.pkg above, was the platform.xml. In the WRITE_EXTERNAL_STORAGE tag, I found two entries:
<group gid=”sdcard_r” />
<group gid=”sdcard_rw” />
I replaced the first entry with:
<group gid=”media_rw” />
in < permission name=”android.permission.WRITE_EXTERNAL_STORAGE” >
After seeing the errors, I replaced the xml file with original version. That didn’t help. Rebooting, turning off, removing batteries multiple times didn’t help. I un-rooted the phone using the “full unroot” feature in SuperSu, and that didn’t help either. I went into Settings and turned KNOX back on, still didn’t help.
At this point, I am stuck. I don’t know what else I should try. I would appreciate any help and suggestions, I would like to avoid resetting or doing more substantial changes to the phone, though.
One more note: I was using ES File Explorer and granted its root access. I don't know if that caused the issues but I just uninstalled it, still no help. Phone while booting shows Samsung Note 3 logo and an unlock Icon with the word Custom.
My phone has Android version 4.4.2
Thank you.
Click to expand...
Click to collapse
Update: I just tried Odin with N900AUCUCNC2_N900AATTCNC2_N900AUCUCNC2_HOME.tar and PIT file to re-partition the phone. But still no help. Same issues. It must be something related to the permission, but why replacing the system still doesn't help? Do I need to do something else? Can I install something else via Odin? Can I root via Odin and get access again to the storage areas?

Did I found a Security Hole?

I take too serious the security in my device. I'm not a computer technician or anything, just a normal-to-advanced user who tends to change things in my device more frequently than my pants. This happend accidentally while trying to replace my SystemUI.apk with a modified one. My phone uses a pattern to unlock it at system level (lockscreen protection, not SIM). So I changed the SystemUI, I've set permissions and rebooted. For some reason the apk didn't worked, resulting in a constant "Android is Upgrading" window. I pressed the power button to lock it, and the screen went off. I pressed it again and my device booted directly to my homescreen with a message saying that my System UI has stopped working. But wait: No pattern unlock? I connected my device via USB to my PC and I was able to see all my files inside (normally, if your device is locked with pattern/pin/finger/etc and connect it to a PC it will not show any file in sdcard0, just an empty folder). The phone was almost unusable because if I press OK in the FC popup a new one would appear 0.5sec later, but I was able to open multiple apps and even type with the keyboard to a Whatsapp contact (with a little of patience) within one popup and another. I even replaced my corrupted SystemUI with root explorer...
So the question is: Is this a security hole? For now this could happen only to Rooted users since there's no way to modify a System apk without root privileges. But if someone manages to break the SystemUI without needing to root the device, he would have access to anything inside your device...
Here's my device info:
Samsung Galaxy Note 4 N910C
Android Version 5.0.1
Build: N910CXXU1BOC5
Deodexed
If anyone experience in security read this, please give me an opinion. Thanks!

It's not a security hole, the keyguard doesn't really do much in the way of security. Device encryption is another matter entirely - that's sure to protect your device if the attacker doesn't know the passcode.
Rooting sidesteps many of the security measures put into place by the OS, and that's why rooting trips the Knox counter.

galaxynote2 said:
I take too serious the security in my device. I'm not a computer technician or anything, just a normal-to-advanced user who tends to change things in my device more frequently than my pants. This happend accidentally while trying to replace my SystemUI.apk with a modified one. My phone uses a pattern to unlock it at system level (lockscreen protection, not SIM). So I changed the SystemUI, I've set permissions and rebooted. For some reason the apk didn't worked, resulting in a constant "Android is Upgrading" window. I pressed the power button to lock it, and the screen went off. I pressed it again and my device booted directly to my homescreen with a message saying that my System UI has stopped working. But wait: No pattern unlock? I connected my device via USB to my PC and I was able to see all my files inside (normally, if your device is locked with pattern/pin/finger/etc and connect it to a PC it will not show any file in sdcard0, just an empty folder). The phone was almost unusable because if I press OK in the FC popup a new one would appear 0.5sec later, but I was able to open multiple apps and even type with the keyboard to a Whatsapp contact (with a little of patience) within one popup and another. I even replaced my corrupted SystemUI with root explorer...
So the question is: Is this a security hole? For now this could happen only to Rooted users since there's no way to modify a System apk without root privileges. But if someone manages to break the SystemUI without needing to root the device, he would have access to anything inside your device...
Here's my device info:
Samsung Galaxy Note 4 N910C
Android Version 5.0.1
Build: N910CXXU1BOC5
Deodexed
If anyone experience in security read this, please give me an opinion. Thanks!
Click to expand...
Click to collapse
So you gave the user root access and you say you are concerned about security? :silly: A silly screen unlock pattern is not going to save you, as anyone with a a computer can access everything on your phone and make any changes they want (granted they have access to you phone).

Security hole can be said of you are uprooted. You changed (corrupted) systemui means you have rooted device and since screen guard is part of systemui so how can you expect to work normally.
Also not difficult to reproduce. Simply delete systemui with root explorer, your device will reboot normally without pattern though you have set it. Even you can explore all files with root explorer (that means you can do almost anything) and can change pattern lock with setting too. Just you will have black wallpaper and no status bar. Once you replace systemui you will have your pattern lock back.
In sort you are rooted users your are no more secured.
Even not rooted but simply having custom recovery you are not secured. Any script having command to delete your pattern /pw it can be deleted from that even device is not rooted as custom recovery can mount partition and can edit it.
That's why Samsung trip knox even by flashing custom recovery.
Sent from my SM-N910G using xda premium

[Q] Locked out of phone - No keyboard at "To start Android, enter your pin"

I'm rooted on 6.0.1 with xposed and twrp.
I've always used a pattern to lock my phone, and I've checked the box "require pattern to start device".
Last night I decided to switch to a pin vs a pattern for some reason.
I installed a new xposed module today (xposed gel settings for those curious).
When I restarted my device it prompted me to enter my pin. A cursor is displayed in the entry field, however, no keyboard is displayed.
You can hold down the cursor in the field and it vibrates, but does nothing.
I tried wiping the cache, restarting in safe mode, using android device manager.
You can select "Emergency Call" at bottom of screen and the dialer pops up.
Does anyone know what's causing this?
I'm not sure if it's one of my xposed modules causing the problem.
The only thing I can even think of that may be causing it is:
When I flashed twrp, I opted to keep my system read only.
For some reason that leads me to believe that the system folder (where I'm assuming google keyboard is located) isn't mounted at start-up and therefor the keyboard app isn't running yet. However since you can open the dialer to make an emergency call, I'm guessing this isn't a correct guess.
Any assistance would be wonderful. Thank you!
EDIT: Super late edit, but an OTG cable and keyboard fixed the issue. I can't remember if I figured out what the issue was.

No idea what's causing that. If you have an OTG cable about you could try connecting a usb keyboard to enter pin?

just so that you know, exposed cause many undocumented issues. issues that have no explanation are generally caused by exposed, if you have it installed. I recommend getting rid of closed and reflaahing your ROM.
and, setting up as read only could cause this issue as well. why would you do read only in your recovery? lol. you use the recovery to change things, read only can't change anything.

simms22 said:
just so that you know, exposed cause many undocumented issues. issues that have no explanation are generally caused by exposed, if you have it installed. I recommend getting rid of closed and reflaahing your ROM.
and, setting up as read only could cause this issue as well. why would you do read only in your recovery? lol. you use the recovery to change things, read only can't change anything.
Click to expand...
Click to collapse
I did it initially to make a nandroid backup of my phone with plans of changing it. I was never prompted to make it read/write and can't find it in settings.

neil_swann80 said:
No idea what's causing that. If you have an OTG cable about you could try connecting a usb keyboard to enter pin?
Click to expand...
Click to collapse
I plan on trying this once I get home. Hopefully it works. I'm not sure at what point in the boot process an external keyboard is considered an input method.

nioletmc said:
I did it initially to make a nandroid backup of my phone with plans of changing it. I was never prompted to make it read/write and can't find it in settings.
Click to expand...
Click to collapse
to make a nandroid backup, you need to change something(write to storage), so read only wouldn't be able to make a backup.

Had the same issue as OP, new Nexus 6 user and have always used pin but I've changed to pattern because of this, only way to start was to use an OTG adapter and a USB Keyboard to input pin, haven't had issues with pattern unlock with xposed or otherwise.

Try to flash a keyboard. Hopefully IME switcher is shown at this stage.
Try to find a keyboard apk and use the zip posted here:
http://forum.xda-developers.com/crossdevice-dev/sony/flashable-appsflash-apps-internal-t2809020

Maybe try disabling xposed. There are two different ways to disable xposed:
1. there is a way to disable Xposed during powerup by repeatedly pressing the a hardware key.. SEE here
http://forum.xda-developers.com/xpo...-modifying-t1574401/post51306764#post51306764
Code:
Quick explanation of the safemode: It was developed by [user=4322181]@Tungstwenty[/user] and makes it possible to disable Xposed by repeatedly pressing one of the hardware buttons during early startup. The phone will vibrate twice when the first key press has been detected. Then you have five seconds to press the same button four more times. Each key press will be confirmed with a short vibration; the final one with a long vibration. It creates /data/data/de.robv.android.xposed.installer/conf/disabled, which prevents most of Xposed's actions (e.g. no hooks are made and no modules are loaded). There's no 100% guarantee that this will get you out of a bootloop, but in most cases it should.
2. you can flash an xposed disabler zip file available in the xda xposed thread
http://forum.xda-developers.com/xposed/xposed-installer-versions-changelog-t2714053
Code:
If that doesn't work, you can flash the attached Xposed-Disabler-Recovery.zip by Tungstwenty. It will be copied to your (external) SD card when you install Xposed as well. The only thing it does is copying /system/bin/app_process.orig back to /system/bin/app_process, which you can also do yourself (e.g. with adb shell in recovery mode).

So, how did your adventure end? I hate to see a loose thread...

Problem with connection

Hi. When I changed in settings network mode to 2G only, signal icon started to flicker. After reboot I have no signal at all (it is impossible to call, send/receive SMS, use data connection etc.). In info (*#*#4636#*#*) preferred mode is set to "WCDMA preferred" and I cannot change it - I can chose another value from list but changes are not saved.
In settings phone says that none of SIM cards are inserted - but I can now access SIM 1 settings. However, everything is blocked and beneath the network type there is a description: "Invalid Network Mode (-1). Ignore.".
It happend when I was on latest official CM 13.0 nightly but this is probably not ROM's fault. Problem didn't disappear after clean flash, after restore or even after flashing whole set of images with official MiFlash tool.
After some research I found that setting ro.telephony.default_network from 22,22 to 10,10 should work, as 10 is for "LTE/GSM auto" when 22 is incorrect value. Separated by comma for two SIM slots. Ok, so I tried to edit build.prop with some apps without luck - access denied (rooted). I tried to mount system rw from Root explorer - nothing happens, still ro. From ADB - no, "dev/block/bootdevice/by-name/system is read-only". I even tried to change SELinux to permissive but still nothing
Every idea is welcome, I just need to get my phone to work as a phone again

NEW TESTED METHOD - Remove FRP Lock (Tested on T580) (firmware attached)

After Struggling for so long. I was finally able to remove the FRP lock on a recently updated tablet.
First and foremost get the tablet in the download mode / Odin Mode and flash the firmware I have attached. Attached all variants.
NOTE: I used Samsung Knox app v2.14
ufile . io/9zvxi (WILL EXPIRE AFTER 30 DAYS)
Once you have done that follow @Beut 's instruction
1- Get access to email via phone or computer because when setting Knox, it will send a PIN to your email to verify it.
2-After setting a wifi connection, no need to go further. Tap Add Network
3- On the pop up keyboard, hold the third key from the left with Speaker Icon. Select from the menu the last icon on the right: Setting.
4-Tap the back arrow on the <--Samsung Keyboard , you will see the <-- Onscreen Keyboard
5- Tap Google Voice Typing , tap Your Feed , check Feed
6- Tap No Thank at the new page, then Google Search will appear, type CH, then select Chrome when it pop up.
7- Search Samsung Knox app, then look for version 2.0.10. I choose the link from apKplz as other sites have too many pop ups.
8-Tap OK when Chrome asks for permission to download. Tap open when download is done.
9- A page will pop up asking for permission to install app from unknown source. Go to setting to check unknown source.
10- Install Knox then add your email, it will send a PIN to your email to verify.
11- Complete all the setting for Knox.
12- Go to my . samsungknox . com/en-US/#/login with your email and password. After that you will see the Tab A with serial number enrolled.
13- Click on it and select Wipe Data . Within few seconds, you will see your tablet goes to Wipe Data and Factory Reset Mode.