Living with Root and Knox (SELinux = enforcing) - Tipps n Tricks collection - Galaxy Note 3 General

So you want to keep (knox) warranty and still use root?
Well there is RDLV and the "forbidden" Tool for that, BUT you will still have SELinux on enforcing mode, which means you don't have full control even with root. While technically most things still do work, they might work a lil different or need a different approach.
Lets collect our findings here...
---
First of all, remounting system with apps like solid explorer does not seem to work.
A workaround for this is to run the following command in terminal or through quick terminal etc:
Code:
/system/bin/mount -o rw,remount /dev/block/mmcblk0p2 /system
This command gets through where other methods fail. Once you have mounted the system writable like this, you can go back to your root explorer app to delete things etc on system partition. Solid explorer gives me error messages still when I delete apps from /system/app/, but they still disappear / get deleted.
---
This also brings me to my next workaround:
To delete system apps and not just freeze them with Titanium, you need to remount system like above and then delete the apks from the /system/app/ directory. A reboot should then remove everything else related to that app afaik. (like the /data/data/ of the app etc.)
Titanium on the other hand gives me an error when I try to delete a system app, even after remounting system to rw.
---
If you want to edit things from your system partition, like build.prop etc. Copy them to your sd first and edit them there. Then mount system rw, and create a backup of the file you are editing. (make a copy and just append "_bak" or smth to the file name) And finally copy the sd file over the corresponding file in system. Make sure you check permissions before and after you copied everything and edit them if they do not match up.
---
My final Tip for now:
I noticed that most root methods on SELinux (this includes RDLV and the forbidden one) use install-recovery.sh to start su as a system daemon which handles all the su requests. (as far as I understood it at least).
Well we can also use this file (or create an install-recovery-2.sh in /etc/ which gets called by the first one by default when you got the root) to run init.d scripts or other stuff.
I don't have tested it yet but I will put the code below once it works...
Code:
tbd
..
hopefully we find a way to turn off this selinux enforcing mode while keeping knox warranty at some point.. - xposed framework might be the answer but not sure - in theory its able to overwrite all methods used by apps. (but I guess selinux above xposed still in system rights and therefore cannot be affected by it?)

And another one:
Don't like this big n clunky user interface? The DPI for the Note 3 is set to 480, thats for old people! If you have want things a bit more refined and more "space" on the screen, edit your build.prop (like I mentioned above) and set the "ro.sf.lcd_density" value down.
I used 360 instead of 480 and that seems perfect to me. It looks like 240 DPI used to look on the Note 1. - You could try 320 or 400 as well.
If you want to set the dpi of individual apps, install xposed and the app settings module. (I would still set browser to 360 or even 320 dpi, 400 is just too much - the adress bar is so damn huge still)

Glad to see you still at it homie. Kingoapp is great. "Google kingoapp" anyone needing help. Just don't post any links please.
Sent from Heaven.

dallastx said:
Glad to see you still at it homie. Kingoapp is great. "Google kingoapp" anyone needing help. Just don't post any links please.
Sent from Heaven.
Click to expand...
Click to collapse
Definitely try out at least the dpi change to 360 or 400, that one is golden =). (nothing special but still..)
--
so far I haven't found anything that does not work at least with a workaround. Some apps do not work as supposed, but thats because they havent adapted yet to the new environment as far as I can tell. And yea, you cannot edit the selinux stuff or turn it off (at least not easy) but thats it. What I did not yet try, which is for risk-friendly people only anyway, is to mess with the efs folder. (you can change your devices mac there, good for privacy concerns hehe). Could be that selinux blocks that one as well, but other than that most things work alright. Just no custom recovery yet, but this could maybe be made possible through the install-recovery.sh file, telling it to start up a custom recovery but not actually flashing it hard onto the device.

Reboot apps I can't get to work. You know the apps that restart phone, bootloader etc... Even through the side 4 button mod. I can only reboot through factory restart. Pressing the power button and using the default restart button.
Sent from Heaven.
---------- Post added at 06:50 PM ---------- Previous post was at 06:49 PM ----------
Yea I always do DPI changes for Gmail , browser, settings, and few other apps
Sent from Heaven.

aww yea youre right - I havent got any app to reboot the phone yet, only the normal reboot through the stock power menu works for me. Didnt try terminal yet.
Maybe not "reboot" but "shutdown -r now"

dallastx said:
Reboot apps I can't get to work. You know the apps that restart phone, bootloader etc... Even through the side 4 button mod. I can only reboot through factory restart. Pressing the power button and using the default restart button.
Click to expand...
Click to collapse
The 4 way reboot menu from Wanam's xposed module works fine for me if you wanted to check that out.

I got one. Enter download mode by powering off. Then hold volume_down+home+power then press volume_up when promtped. Ok now this is what blows my mind. Everyone says pull battery to exit. I did this and the center off my screen looked messed up for about 8 seconds and I thought there must be a better way. Guess what to exit just hold power by itself for about 10 secs and you reboot out of download mode. Great easy way to check counter and no longer have to remove case, battery, etc.
Sent from my SM-N900W8 using XDA Premium 4 mobile app

TheAvatar said:
The 4 way reboot menu from Wanam's xposed module works fine for me if you wanted to check that out.
Click to expand...
Click to collapse
Yea i tried it but didnt work... It may of been conflicting with other apps. But what root method are you using?
---------- Post added at 07:16 PM ---------- Previous post was at 07:11 PM ----------
JohnnyRebel said:
I got one. Enter download mode by powering off. Then hold volume_down+home+power then press volume_up when promtped. Ok now this is what blows my mind. Everyone says pull battery to exit. I did this and the center off my screen looked messed up for about 8 seconds and I thought there must be a better way. Guess what to exit just hold power by itself for about 10 secs and you reboot out of download mode. Great easy way to check counter and no longer have to remove case, battery, etc.
Sent from my SM-N900W8 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Yea i have always got out of download mode on Note 3 by just holding power button.
---------- Post added at 07:20 PM ---------- Previous post was at 07:16 PM ----------
zroice said:
And another one:
Don't like this big n clunky user interface? The DPI for the Note 3 is set to 480, thats for old people! If you have want things a bit more refined and more "space" on the screen, edit your build.prop (like I mentioned above) and set the "ro.sf.lcd_density" value down.
I used 360 instead of 480 and that seems perfect to me. It looks like 240 DPI used to look on the Note 1. - You could try 320 or 400 as well.
If you want to set the dpi of individual apps, install xposed and the app settings module. (I would still set browser to 360 or even 320 dpi, 400 is just too much - the adress bar is so damn huge still)
Click to expand...
Click to collapse
Only reason i wouldn't change the DPI for everything because some apps will look crazy. Then you will have apps also like the play store that may not work correctly.

JohnnyRebel said:
I got one. Enter download mode by powering off. Then hold volume_down+home+power then press volume_up when promtped. Ok now this is what blows my mind. Everyone says pull battery to exit. I did this and the center off my screen looked messed up for about 8 seconds and I thought there must be a better way. Guess what to exit just hold power by itself for about 10 secs and you reboot out of download mode. Great easy way to check counter and no longer have to remove case, battery, etc.
Sent from my SM-N900W8 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
good finding! (lol i couldve came up with this myself lol - holding power long enough always does a forced reboot).
I noticed too that when you pull the battery that sometimes you get lines on the screen - really scary, thought I messed up my device but after like 10 seconds or so they disappeared. But definitely something you want to avoid!
Holding down power to exit the download mode instead of pulling battery from now on.

I use Rootr Browser Pro... I can delete things out of the system partition and write into the system partition (after setting it for root privelege in settings and supersu) however I can''t just overwrite files.... The file I wish to overwrite must 1st be deleted or renamed,usually with .bak. Haven't had to use terminal.
Another handy tip, in the CSC folder, rename the customer.xls to customer.xls.bak and then a new option will be available in the settings/device/lock screen menu to add app shortcuts to the lock screen
if you add this code to the others.xml file AFTER <FeatureSet> and BEFORE </FeatureSet>
<CscFeature_Sip_UseSymbolInCMKey>true</CscFeature_Sip_UseSymbolInCMKey>
<CscFeature_Sip_EnableSymbolInSecondary>en_GB;en_U S;de;fr;es;it</CscFeature_Sip_EnableSymbolInSecondary>
You will then enable sub symbols on the default keyboard.
Works a dream...

TheAvatar said:
The 4 way reboot menu from Wanam's xposed module works fine for me if you wanted to check that out.
Click to expand...
Click to collapse
wait a minute - the 4 way reboot does work for you? Are you on Knox 0x0 still? And SELinux status enforcing? For me no "reboot" apps seem to work. They all just try to reboot (and SELinux denies it then most likely)
---
one other problem occured: when using xprivacy and deinstalling an app the system locks up. Can someone confirm this?

Why do people insist on DELETING apps from system? Just use pm disable, sheesh.

khaytsus said:
Why do people insist on DELETING apps from system? Just use pm disable, sheesh.
Click to expand...
Click to collapse
The xprivacy lockup also happens with user apps deinstallation. Just want to make sure its not me or my setup but xprivacy thats causing this. I turned it off and it works, turn it on, device hangs on deinstallations.

zroice said:
And another one:
Don't like this big n clunky user interface? The DPI for the Note 3 is set to 480, thats for old people! If you have want things a bit more refined and more "space" on the screen, edit your build.prop (like I mentioned above) and set the "ro.sf.lcd_density" value down.
I used 360 instead of 480 and that seems perfect to me. It looks like 240 DPI used to look on the Note 1. - You could try 320 or 400 as well.
If you want to set the dpi of individual apps, install xposed and the app settings module. (I would still set browser to 360 or even 320 dpi, 400 is just too much - the adress bar is so damn huge still)
Click to expand...
Click to collapse
Yeah, thanks for the tip. I used xpose app setting to set my nova launcher to be about 400. I will try modify the build.prop then.

Ok so what i did to quickly update to mj4 since it is now live. "you will lose root and everything on internal storage so back it up"
Be sure make COPY of backup of your titanium folder if use NOVA be sure to do a backup of your current layout. Copy these folders to your EXTsd. Remove card afterwards.
I was rooted so i kept getting "Cant up dated Modded system". Even unrooting i cant getting Modded system. I use almost the same root method as OP uses called kingoapp "cant provide links so google is your friend"
Anyhow.. i wanted to make sure i didnt trip KNOX and grew impatient for an update.zip. I didnt want to flash anything through ODIN, so i figured would use Kies.
Kies will see your phone as already updated. At the top of the app if you click tools then "firmware and initialization" Kies will override whatever is on your phone and update to mI5. This will take about 30 min but much quicker then trying to download the entire stock firmware from hotfile.
Once your phone is up go ahead and go to to settings on you phone and system update. Update will run and restart your phone. You are now on the latest firmware mj4.
Reroot and reinstall SD card. You are now rooted on latest update.
Notes - I tried everything to try to trick system to thinking its not modded including unrooting. Nothing worked reasoning i resorted to flashing through Kies.

dallastx said:
Ok so what i did to quickly update to mj4 since it is now live. "you will lose root and everything on internal storage so back it up"
....
Click to expand...
Click to collapse
Ohh theres an update? Well I bought a 2nd note today - couldnt resist it was 500€ only (they usually go for about 550 here). And mine had some display issues... gonna sell the first one and keep second - screen is better. Anyway, I got to redo everything now and restore the "old one" to stock.
To restore stock safely I would always suggest using Kies and doing a forced firmware update like dallas described. I read that flashing the same firmware twice with odin can already trip knox. (at least if you were tempering with the system)
But note that this will most likely update the bootloader of your phone as well.
---
Now I got the old bootloader on my new and still branded n3 - can someone explain what the difference actually is to the new bootloader? I mean both don't allow SELinux permissive, and both can be rooted (at least with the "tool")?
On S4 etc I understand that new firmware version introduced knox, and that there was firmware out without knox, but if you upgraded once you couldnt go back. But there are no knox free firmwares for the n3 are there? (I mean stock ones)

zroice said:
Ohh theres an update? Well I bought a 2nd note today - couldnt resist it was 500€ only (they usually go for about 550 here). And mine had some display issues... gonna sell the first one and keep second - screen is better. Anyway, I got to redo everything now and restore the "old one" to stock.
To restore stock safely I would always suggest using Kies and doing a forced firmware update like dallas described. I read that flashing the same firmware twice with odin can already trip knox. (at least if you were tempering with the system)
But note that this will most likely update the bootloader of your phone as well.
---
Now I got the old bootloader on my new and still branded n3 - can someone explain what the difference actually is to the new bootloader? I mean both don't allow SELinux permissive, and both can be rooted (at least with the "tool")?
On S4 etc I understand that new firmware version introduced knox, and that there was firmware out without knox, but if you upgraded once you couldnt go back. But there are no knox free firmwares for the n3 are there? (I mean stock ones)
Click to expand...
Click to collapse
Yea go ahead and do all your updates then root. I think the update may me just for Sprint N900p.

so there is still no way to get rid of "enforcing selinux" without tripping knox counter?
need this only to get my OTG cable to USB OBD working, seems SELinux is blocking serial usb communication :/

zroice said:
wait a minute - the 4 way reboot does work for you? Are you on Knox 0x0 still? And SELinux status enforcing? For me no "reboot" apps seem to work. They all just try to reboot (and SELinux denies it then most likely)
Click to expand...
Click to collapse
Sorry for the late reply. I was Knox 0x0, used Root De La Vega, installed xposed framework then grabbed wanam from the play store. Just had to enable it and it was all good.

Related

[How To] Install The New GOT Update On Milestone

Hello My Friends I've Heard You Are Having Troubler Installing The New Upgrade Or Understanding What Is Needed To Be Done.
Note: THIS IS A WINDOWS BASED HOW TO AND WILL WORK ON WINDOWS ONLY​
Before I Start I must Say, This Is a combination of process and I have not created any of those files or own the right to them so all the links are the same links found on other posts from where i got the info, so by downloading those files you are, supporting them not me i take no credit for this work
Well Here Is the quick Easy Guide In How To Do This
-Fist we Need To Get The Tools To Perform This Operation
pulled From This Tread we need
1. Motorola Drivers For Either 32 or 64 Bits
2. RSD Lite, witch is a tool for flashing your phone.
3. The GOT Open Recovery ToolUpdate: Added Latest version from G.O.T.'S Blog
4.The Firmware Files From Got
2.2.1 FIRMWARE FILES
DACH – GERMANY
http://www.multiupload.com/G9PP7JN78C
DACH AUSTRIA
http://www.multiupload.com/P8DDXCWW03
RETAIL EUROPE (RTEU)
http://www.multiupload.com/6X7H39HGCG
FRANCE RETAIL
http://www.multiupload.com/PK28LXE4SE
ITALY WIND
http://www.multiupload.com/3KYMZNRZW2
UK RETAIL (RTUK)
http://www.multiupload.com/60B78PRKNY
TELUS CANADA
http://www.multiupload.com/5S2CYGP3VW
Click to expand...
Click to collapse
EDIT: G.O.T. Has Added the burnerable open recovery to these sfb files so no need to flash it latter
-Now That We Have The Stuff We Need We are going to do it, fist i must say that unlike other roms that are applied by a backup restore (corect me if im whrong) this is a full flash and its going to reset everything so no apps will remain no setting will remain and is highly recommended that you uninstall every app you have, don't back them up(except for apps some apps that have a create backup file, those seem to work) just uninstall them, and when we are done have them installed again, Here Is A Tool That Will Help You Get There Faster
1.ok you have everything uninstalled right? now time for some action
2.install the proper divers (32 or 64)
3.install the RSD Lite tool
4.unzip the 2.2.1 FIRMWARE FILES you downloaded and you will find a ".sbf" file
5.now connect your phone to USB cable and turn it off
6.boot it in boot-loader mode (press the D-PAD UP key while pressing the power button), some night need you to release the button after a minute, a black screen will be shown on your phone and you will see the divers being installed on your computer.
7.when drivers are done open the RSD Lite tool and your device should appear you can click on it to see details.
8.now click on the "..." buttons that are close to the start button and look for the ".sbf" file, after a couple of seconds it should be ready to start
9.press the start button and do not unplug the cable or let your computer show the screen saver or go to sleep, the posses must not be stopped while it has started .
10.when the posses is done the devise will restart and voala, you have 2.2
-As GOT stands there are some bugs on the firmware and they have developed a fix to them and get root and overclock, here is what you have to do.
1. unzip the got open recovery tool into the root of your SD card
2.check this quote
NOTE: On some devices, we have encountered that rooting directly after flashing without rebooting after the initial flash can bring some issues with RootExplorer not asking for root permissions. To be safe, reboot after flash so that the “welcome to milestone” menu comes up, set up the device in general, then reboot to recovery and root the device as well as apply our 2.2.1 tweaks with Launcher, Services.jar fix and Wireless Tethering app.
Click to expand...
Click to collapse
this means if the fist time your milestone got restarted and you saw "Welcome to Milestone" Message You are good an you can root.
but if you didn't then restart you phone and see if the message comes out, if not , a factory reset should have that scree message shown.
3. open the open recovery by pressing camera and power button at the same time while the device id off. you should see a scree with a "!" symbol on it then press fist volume rocker up button a leave it pressed then press camera button, some letter will pop out.
4. using the pad scroll down to "apply update.zip", after a couple of seconds the GOT menu should pop out (everything from now on uses the pad)
5.root your phone (why not)
6.go down to "Launch 2.2.1 Menu" Option.
7.Here you will see the "Fix Bugs They Are Talking About
One of the first things you should do is use the “Fix 2.2.1 bugs” selection in the new OR 2.2.1 menu after you flash the sbf file.
This tweak will fix some of the issues with the generic sbf build such as dual USB notifications, replacing some stock Motorola applications such as the old launcher/mediagallery and adding the Wireless Tethering application.
Click to expand...
Click to collapse
8. there is the overclock too.
Now your device should have all the things you need to start playing with it,I encourage you to check on some tweaks the GOT team might have, and you might want.
I Hope This Was Helpful enjoy ^_^
To Do For This thread:
Code:
1. Make It More Easy To Use, and clear to read
2. Add Suggestions
3. Add screenshots
4. Add Other OS Options
5. Add Attachments (For Some reason I Can't Now)
Please Post And Rate If This Was Useful
Bug Counter:
Common Problems Found On Thread
http://forum.xda-developers.com/showthread.php?t=810726
1. AppBrain Market Sync Not Connecting To server.
2. Google Chrome To Phone Not Working.
3. WiFi Having Trouble To Connect On Some Routers, Sometimes Not Connecting At All on WPA2
4. Activating The Camera From The The Albums Will "Force Close"
5. Facebook Sync Is Not Working
6. The menu button on the keyboard activates the voice recognition option, and cannot be used to trigger shortcuts anymore (To me its more like a change on the way the keyboard works instead of a bug since you can use the menu button on the screen to trigger keyboard shortcuts)
7. No Vibration On key press
8. Russian Language Will Have Problems with phone and contacts apps
9. problem with android id
If Any Of Those Work On Yours Please Report Witch version you installed maybe yours can help fix others,you think you found a bug and its not listed? post it here and post
Fixing Problems:
1. Problem with android ID:
A. If Not Installed The Update Yet(Needs Root)
-Install This AppAndroidID
-Back your android ID up, and put ir somewhere safe
-follow the guide to update to froyo
-Install This App againAndroidID
-restore your android id
B. If Already did it(Needs Root)
-install this appAndroidID
-invent a number that might serve as your android ID (you need numbers and letters)
-input it on the app
okay nice tut, butttttt... im stuck at the part where i should install openrecovery. at first, to come to the "!" screen, camera screen + power did not work. i got there by pressing X + Power... but now i dont know how to access the menu where i should install update.zip..
please help!
November91 said:
okay nice tut, butttttt... im stuck at the part where i should install openrecovery. at first, to come to the "!" screen, camera screen + power did not work. i got there by pressing X + Power... but now i dont know how to access the menu where i should install update.zip..
please help!
Click to expand...
Click to collapse
okay i got it, im so sorry, i used the up button on the dpad
Also I did not see a launch 2.2.1 menu option. But I have currently launched the GOT open recov without an issue. I have rooted as well as many other things but didn't see that specific menu.
FoTwoZero said:
Also I did not see a launch 2.2.1 menu option. But I have currently launched the GOT open recov without an issue. I have rooted as well as many other things but didn't see that specific menu.
Click to expand...
Click to collapse
Silly question are you suing the newest version?
if you press down should on the open recovery menu it should be your sixth option, I have recorded a video about it this morning but its backwards I'm Going To Try And Have it Fixed and up today hopefully
For Tmobile USA ?
Which SBF for a german Mlestone on TMobile USA ? Will telus do fine ?
gbzygil said:
Which SBF for a german Mlestone on TMobile USA ? Will telus do fine ?
Click to expand...
Click to collapse
your Should use the rom depending on which band your phone has
German milestone should work with Europe ROM
under setting about phone check the Build Number
and look for that same number in here
http://and-developers.com/sbf:milestone
it will give us an idea where the phone is actually from
hi there. i have instaled europe GOT_RTEU_2_2_1FULL.zip version and now sometimes my touchscreen does not work. i mean that if i put the phone in standby and i try to unlock the touchscreen is not responding. i have to power off/on to make it work again. thanks in advance
Facebook app wont Synch with my contacts on first launch of FB app.
No other bugs so far...
Israel milestons should use retail europe?
Sent from my Milestone using XDA App
protozeloz said:
2. Google Chrome To Phone Not Working.
Click to expand...
Click to collapse
for me it's working perfectly. RTEU
Thank for this tutorial.
My milestone works fine so far, but 3g mobile hotspot and wireless tether not working.
Flash on milestone is so cool
something i don't get
I updated the firmware with RSD Lite, and used the one click tool, because:
whenever i try to hit update.zip i will get an errormessage, stating that these blocks couldn't be found -> ergo, the card not be mounted.
The HTC stuff i always managed, but this one is a mistery to me. Also, i did format fat32, pushed the stuff and then straight on bootup trying to hit the update.zip, without success.
I've read about how other people solved that problem, none of those approaches helped me.
Any hint is more than welcome.
2 bugs i've discovered so far: Battery drain like almost to be declared useless, some market apps "vanish" after installing them. I suppose those fixes would have done the job. I might attempt to use root explorer and execute the scripts like that, still I'd like to know why I'm unable to get the update.zip, resp. the G.O.T or any other "intelligent" boot menu installed.
Edit2: Even when installing the vulnerable sbf, i still get the error: E: Can't mount /dev/block/mmcblk0p1 ....
plvt_florian said:
hi there. i have instaled europe GOT_RTEU_2_2_1FULL.zip version and now sometimes my touchscreen does not work. i mean that if i put the phone in standby and i try to unlock the touchscreen is not responding. i have to power off/on to make it work again. thanks in advance
Click to expand...
Click to collapse
This could be for any reason try this
-Re download and re flash the files(do the whole thing again)
-there is an app i have called sd dual mount that makes my screen go crazy wen i connect the phone to an usb port, it was stable on 2.1 but now goes crazy on 2.2 check some of your apps to ensure they are not the ones responsible for this
hanslast said:
Facebook app wont Synch with my contacts on first launch of FB app.
No other bugs so far...
Click to expand...
Click to collapse
yurasts said:
Israel milestons should use retail europe?
Sent from my Milestone using XDA App
Click to expand...
Click to collapse
you can try with the retail Europe,
evolucja said:
for me it's working perfectly. RTEU
Click to expand...
Click to collapse
can you tell me if you have an android ID? it should work when your device has it
czescdziadek said:
Thank for this tutorial.
My milestone works fine so far, but 3g mobile hotspot and wireless tether not working.
Flash on milestone is so cool
Click to expand...
Click to collapse
you can try and uninstall the wireless teeter app an have it reinstalled that should sort it out
MenoDev said:
I updated the firmware with RSD Lite, and used the one click tool, because:
whenever i try to hit update.zip i will get an errormessage, stating that these blocks couldn't be found -> ergo, the card not be mounted.
The HTC stuff i always managed, but this one is a mistery to me. Also, i did format fat32, pushed the stuff and then straight on bootup trying to hit the update.zip, without success.
I've read about how other people solved that problem, none of those approaches helped me.
Any hint is more than welcome.
2 bugs i've discovered so far: Battery drain like almost to be declared useless, some market apps "vanish" after installing them. I suppose those fixes would have done the job. I might attempt to use root explorer and execute the scripts like that, still I'd like to know why I'm unable to get the update.zip, resp. the G.O.T or any other "intelligent" boot menu installed.
Edit2: Even when installing the vulnerable sbf, i still get the error: E: Can't mount /dev/block/mmcblk0p1 ....
Click to expand...
Click to collapse
have you tried re downloading the files and doing all over again?, it could be a broken file
thats why i tell devs and chefs they should add an MD5 sum to their files larger than 20MB some errors are caused by just having downloaded broken files
Root phone from the GOT OR menu doesn't seem to actually root my phone (2.2.1 UK version)
Superuser whitelist app FCs instead of prompting to allow access. Have tried using Better Terminal for root access & also Wireless Tether app.
Anyone else getting this? Any ideas? Do any of the 1-click root apps still work with this build of Froyo? Which can we use?
aboycalledsu said:
Root phone from the GOT OR menu doesn't seem to actually root my phone (2.2.1 UK version)
Superuser whitelist app FCs instead of prompting to allow access. Have tried using Better Terminal for root access & also Wireless Tether app.
Anyone else getting this? Any ideas? Do any of the 1-click root apps still work with this build of Froyo? Which can we use?
Click to expand...
Click to collapse
i can confirm this. Simply trying it a second time worked for me
I'd like to add something for Linux users:
Using a virtual machine (virtualizing WinXP) that has USB support (eg Oracle VM VirtuaBox, since VirtualBox OSE does not support USB forwarding) can do this pretty easy. So no worries when trying this via a VM.
i try to instal GOT and its succesfull.
but why i install the application not bring to SD card
but still bring to internal memory
many said 2.2 automatic have app2sd
can you help me?
THX
m0jo said:
i can confirm this. Simply trying it a second time worked for me
Click to expand...
Click to collapse
not for me unfortunately!
weird...

Blocking Mode Fix (Root Required)

**I am not responsible for any damage you do to your phone. This as any other mod is done at your own risk. This is just a guidline on how to get a real fix for blocking mode on your VZW Jelly Bean device.**
This blocking mode fix has been confirmed on both the VZW Note 2 and the VZW Galaxy S3
*You need to be rooted.*
IF YOUR ON A NON-VZW BASED ROM:
JUST FOLLOW PART 3!! (and part 4 if you like!)
IF YOUR ON A VZW BASED ROM:
Part 1
There are two apks that are the reason for blocking mode not working. The two files are the secContacts.apk and the secPhone.apk. You will need download these two apks from a other carriers rom and replace them in the system/app folder in root explorer (or your choice system file explorer) and change the permissions.. (For example download a flashable "att" note 2 rom and copy the secContacts.apk and the secPhone.apk and paste them into your system/app folder. Restart then change the permissions then restart again. Same thing with the Galaxy s3 only you have to download files from another carrier galaxy s3 Rom. From this point on blocking mode will work 100 percent.
Part 2
Now that you have blocking mode working, how can you access it. You can get a shortcut maker app and have a blocking mode home screen icon... OR..You can have it in the settings menu like it's supposed to be! Now just like before there is an apk that VZW had changed to block this. It is the secSettings.apk. So from the same rom you downloaded from before copy the sec.Settings.apk from the other carrier Rom and paste it in your system/app folder in root explorer. At this point you may or may not get a chance to restart your phone (it might freeze for a sec and restart by itself. Once phone restarts change the permissions and restart again. **NOTE: Some roms settings mave have more or less options then the stock. To access these just also copy and paste the secSettingsProvider.apk and everything will work perfectly** **NOTE: menu appearance will not change yet!**
Part 3
Last step. Now that you have the new menu there are still two more files that are causing the menu to change. In root explorer navigate to /efs/imei and delete the map_code.dat and then go to /system/Csc and delete the sales_code.dat. Now restart your phone and you are good to go. **NOTE: after deleting these files any VZW apps on your phone or in market will not be recognized on your phone. For example if you try to download a VZW app from the market it will say your device is not recognized. But they have 'market unlocker' apps that can trick the market to see you as any carrier you want. Also VZW Apps like backup assistant might not work properly.
Part 4
This is not really related to blocking mode but I though I might throw it in here as a bonus. If you copy the feature.xml from another carrier (ex is use the ATT one) and paste it in you /system/csc (I'm my opinion) makes your VZW phone better.The stock email app for example will never try to connect to the VZW server again. It will just go straight to the email app. It also seems to make your phone more responsive and work better with certain samsung apps. (Ex: the samsung apps.apk connects better with samsung push service.* Like I said just a little something extra I noticed.*
ENJOY!
EDIT: Those of you having trouble with step 2 with the secSettings.apk, try the file from either of these rom:
EDIT: You may need to wipe first.
4.1.1: http://forum.xda-developers.com/showthread.php?t=2033132
or
4.1.2: http://forum.xda-developers.com/showthread.php?t=2113436
or
4.1.2: http://wanamlite.com/2013/03/07/romcwmxxemb5jelly-bean4-1-2-deodexed-stock-rom/
alphamik3 said:
**I am not responsible for any damage you do to your phone. This as any other mod is done at your own risk. This is just a guidline on how to get a real fix for blocking mode on your VZW Jelly Bean device.**
This blocking mode fix has been confirmed on both the VZW Note 2 and the VZW Galaxy S3
*You need to be rooted.*
IF YOUR ON A NON-VZW BASED ROM:
JUST FOLLOW PART 3!! (and part 4 if you like!)
IF YOUR ON A VZW BASED ROM:
Part 1
There are two apks that are the reason for blocking mode not working. The two files are the secContacts.apk and the secPhone.apk. You will need download these two apks from a other carriers rom and replace them in the system/app folder in root explorer (or your choice system file explorer) and change the permissions.. (For example download a flashable "att" note 2 rom and copy the secContacts.apk and the secPhone.apk and paste them into your system/app folder. Restart then change the permissions then restart again. Same thing with the Galaxy s3 only you have to download files from another carrier galaxy s3 Rom. From this point on blocking mode will work 100 percent.
Part 2
Now that you have blocking mode working, how can you access it. You can get a shortcut maker app and have a blocking mode home screen icon... OR..You can have it in the settings menu like it's supposed to be! Now just like before there is an apk that VZW had changed to block this. It is the secSettings.apk. So from the same rom you downloaded from before copy the sec.Settings.apk from the other carrier Rom and paste it in your system/app folder in root explorer. At this point you may or may not get a chance to restart your phone (it might freeze for a sec and restart by itself. Once phone restarts change the permissions and restart again. **NOTE: Some roms settings mave have more or less options then the stock. To access these just also copy and paste the secSettingsProvider.apk and everything will work perfectly** **NOTE: menu appearance will not change yet!**
Part 3
Last step. Now that you have the new menu there are still two more files that are causing the menu to change. In root explorer navigate to /efs/imei and delete the map_code.dat and then go to /system/Csc and delete the sales_code.dat. Now restart your phone and you are good to go. **NOTE: after deleting these files any VZW apps on your phone or in market will not be recognized on your phone. For example if you try to download a VZW app from the market it will say your device is not recognized. But they have 'market unlocker' apps that can trick the market to see you as any carrier you want. Also VZW Apps like backup assistant might not work properly.
Part 4
This is not really related to blocking mode but I though I might throw it in here as a bonus. If you copy the feature.xml from another carrier (ex is use the ATT one) and paste it in you /system/csc (I'm my opinion) makes your VZW phone better.The stock email app for example will never try to connect to the VZW server again. It will just go straight to the email app. It also seems to make your phone more responsive and work better with certain samsung apps. (Ex: the samsung apps.apk connects better with samsung push service.* Like I said just a little something extra I noticed.*
ENJOY!
Click to expand...
Click to collapse
what does deleteing the /efs/imei, and sales_code.dat. do?
Sec settings crashes after I replace it, fix permissions, and reboot. Tried cache wipes, etc. No luck on that part. Using a Sprint base MB1 for all files.
countryfolk07 said:
Sec settings crashes after I replace it, fix permissions, and reboot. Tried cache wipes, etc. No luck on that part. Using a Sprint base MB1 for all files.
Click to expand...
Click to collapse
I didn't mess with it long, but I got it to work once, but then I wiped and tried again and the same method I used didn't work, so I tried following the OP and didn't work.
if deleting those two files isn't that big of a deal I may try and figure out how to appropriately port this MOD using VZW .apks edited using int. .apks
andybones said:
I didn't mess with it long, but I got it to work once, but then I wiped and tried again and the same method I used didn't work, so I tried following the OP and didn't work.
if deleting those two files isn't that big of a deal I may try and figure out how to appropriately port this MOD using VZW .apks edited using int. .apks
Click to expand...
Click to collapse
Which rom are you on? I can give you the files iv been working with if you want to try. Iv been working with an ATT Rom. This method after wiping worked with the files iv been using.
As for the sales_code.dat and map_code.dat as i know that are just for the market to reconginze your device a VZW.for certain VZW apps. Like i said the only thing it did after deleting them for me was the market thing. certain apps like backup assistant might not work properly. everything else is fine.
Also yea a port might be better. Let me know whats up.
alphamik3 said:
Which rom are you on, and is your boot loader unlocked? I can give you the files iv been working with if you want to try. Iv been working with an ATT Rom. This method after wiping worked with the files iv been using.
As for the sales_code.dat and map_code.dat as i know that are just for the market to reconginze your device a VZW.for certain VZW apps. Like i said the only thing it did after deleting them for me was the market thing. certain apps like backup assistant might not work properly. everything else is fine.
Also yea a port might be better. Let me know whats up.
Click to expand...
Click to collapse
I have CleanROMACE downloaded, I got it working with that, very strange though, I did get it showing, blocking mode did turn on and everything got he noti in the status bar I didnt test to make sure they work im sure they do.
I did comb through the VZW secsettings.apk and the one that makes it work and I cannot find a single thing that is making blocking mode show..
very weird..
I'm going to try going thru the SecConacts.apk and SecPhone.apk to see if I an get a port. if you don't use the att secconacts andsecphone, does blocking mode what just not work? fc? do you know by chance?
thank you
andybones said:
I have CleanROMACE downloaded, I got it working with that, very strange though, I did get it showing, blocking mode did turn on and everything got he noti in the status bar I didnt test to make sure they work im sure they do.
I did comb through the VZW secsettings.apk and that makes it work and I cannot find a single thing that is making blocking mode show..
very weird..
I'm going to try going thru the SecConacts.apk and SecPhone.apk to see if I an get a port. if you don't use the att secconacts andsecphone, does blocking mode what just not work? fc? do you know by chance?
thank you
Click to expand...
Click to collapse
Ok so on my note 2 I am also on clean Rom ace. So all I did was delete the Sale_code and map_code files and it will show blocking mode in the menu and blocking mode already works. no need to replace any files because clean rom uses generic apks i guess that work for all carriers. so blocking mode already works.. as for the galaxy s 3 i used an att rom to get blocking mode to work with the method in the op. I will upload the files and send you a link in a minute
alphamik3 said:
Ok so on my note 2 I am also on clean Rom ace. So all I did was delete the Sale_code and map_code files and it will show blocking mode in the menu and blocking mode already works. no need to replace any files because clean rom uses generic apks i guess that work for all carriers. so blocking mode already works.. as for the galaxy s 3 i used an att rom to get blocking mode to work with the method in the op. I will upload the files and send you a link in a minute
Click to expand...
Click to collapse
I found the post i got the files from: http://forum.xda-developers.com/showthread.php?t=2033132
This is for the Galaxy S3. This rom is for the ATT/Bell/Rogers/Telus version. i used the above method on a vzw based rom and it wokerd.
For the Galaxy Note 2. i just used the files on clean rom ace on a vzw based rom on the note 2 with the above method and it worked.
alphamik3 said:
I found the post i got the files from: http://forum.xda-developers.com/showthread.php?t=2033132
This is for the Galaxy S3. This rom is for the ATT/Bell/Rogers/Telus version. i used the above method on a vzw based rom and it wokerd.
For the Galaxy Note 2. i just used the files on clean rom ace on a vzw based rom on the note 2 with the above method and it worked.
Click to expand...
Click to collapse
can you upload the feature.xml you pulled from there so i don't need to DL a whole package just to compare the xml's? thanks!!
alphamik3 said:
I found the post i got the files from: http://forum.xda-developers.com/showthread.php?t=2033132
This is for the Galaxy S3. This rom is for the ATT/Bell/Rogers/Telus version. i used the above method on a vzw based rom and it wokerd.
For the Galaxy Note 2. i just used the files on clean rom ace on a vzw based rom on the note 2 with the above method and it worked.
Click to expand...
Click to collapse
that ROM is 4.1.1 though, and we are on 4.1.2
---------- Post added at 01:43 PM ---------- Previous post was at 01:42 PM ----------
Thebear j koss said:
can you upload the feature.xml you pulled from there so i don't need to DL a whole package just to compare the xml's? thanks!!
Click to expand...
Click to collapse
the feature.xml from my cell/message block should actually work
andybones said:
that ROM is 4.1.1 though, and we are on 4.1.2
---------- Post added at 01:43 PM ---------- Previous post was at 01:42 PM ----------
the feature.xml from my cell/message block should actually work
Click to expand...
Click to collapse
the files still work.. i will try to find a 4.1.2 rom though
and here is a link to the feature.xml i am using.. it was from the ATT CSC from clean rom ace 4.6.1
http://www72.zippyshare.com/v/65690441/file.html
alphamik3 said:
the files still work.. i will try to find a 4.1.2 rom though
and here is a link to the feature.xml i am using.. it was from the ATT CSC from clean rom ace 4.6.1
http://www72.zippyshare.com/v/65690441/file.html
Click to expand...
Click to collapse
here is a european stock 4.1.2 rom: http://wanamlite.com/2013/03/07/romcwmxxemb5jelly-bean4-1-2-deodexed-stock-rom/
here is a link for SynergyROM: http://forum.xda-developers.com/showthread.php?t=2113436
i would try the european rom first. but the should both work.
Another way to do this is to use the 23 lidroid toggle MOD and just enable the "dormant mode" that is blocking mode, this way you don't have to mess with settings.apk and anything with market. long press the toggle to access the settings. and flash the phone and contacts. i havent tested to see if anything works but it should id imagine. if not at least u dont have to mess with settings..
andybones said:
Another way to do this is to use the 23 lidroid toggle MOD and just enable the "dormant mode" that is blocking mode, this way you don't have to mess with settings.apk and anything with market. long press the toggle to access the settings. and flash the phone and contacts. i havent tested to see if anything works but it should id imagine. if not at least u dont have to mess with settings..
Click to expand...
Click to collapse
This worked for me.
Sent from my SCH-I535 using xda app-developers app
andybones said:
Another way to do this is to use the 23 lidroid toggle MOD and just enable the "dormant mode" that is blocking mode, this way you don't have to mess with settings.apk and anything with market. long press the toggle to access the settings. and flash the phone and contacts. i havent tested to see if anything works but it should id imagine. if not at least u dont have to mess with settings..
Click to expand...
Click to collapse
True. Although I personally could are less about any of verizons apps. I think they all are garbage, so for me i dont care about the market saying my device isnt recognized because i dont use them anyway. And the whole reason behind verizon changed everything in the the first place P*$$ed me off and drove me to want to change everything back, the way it should be, the way ALL the other carriers have there phone set up. This is how i found my method. So swapping the settings.apk for another, and deleting 2 (IMO) useless files, will make the menu look the way it was intended to with blocking mode in the menu, no replacement airplane mode toggle, and NO permenant backup assistant accounts, which shows up even if backup assistant is deleted on your phone. There is obviously more than one way to achieve this a blocking mode fix. Its good to have options.
alphamik3 said:
True. Although I personally could are less about any of verizons apps. I think they all are garbage, so for me i dont care about the market saying my device isnt recognized because i dont use them anyway. And the whole reason behind verizon changed everything in the the first place P*$$ed me off and drove me to want to change everything back, the way it should be, the way ALL the other carriers have there phone set up. This is how i found my method. So swapping the settings.apk for another, and deleting 2 (IMO) useless files, will make the menu look the way it was intended to with blocking mode in the menu, no replacement airplane mode toggle, and NO permenant backup assistant accounts, which shows up even if backup assistant is deleted on your phone. There is obviously more than one way to achieve this a blocking mode fix. Its good to have options.
Click to expand...
Click to collapse
I wasn't posting this to put you down, just a simpler way to do it.
Just because you don't think that those file are important doesn't mean EVERYONE else feels that way. I give you mad props for finding the other two (useless) files to get it to show in settings (which isn't even made for our phones and adds a lot of MORE useless crap).. IMHO
I'm sure many users enjoy your method, but I think many others will also appreciate NOT having to replace their settings.apk and remove files that a VZW phone needs. Pushing the Phone.apk and Contacts.apk from Synergy is no biggie since we use that ROM anyway.
No need to get defensive bud. Team work is the key here, I'd like to eliminate all int. .apks, and try and port w.e code is missing from our VZW .SecPhone.pk and SecContacts.apk.
again, like I said - mad props for figuring this out bro, many many people across VZW on sgiii and note2 were requesting this like crazy.
and again wasn't trying to put your method down by any means, just letting those know of another way.
andybones said:
I wasn't posting this to put you down, just a simpler way to do it.
Just because you don't think that those file are important doesn't mean EVERYONE else feels that way. I give you mad props for finding the other two (useless) files to get it to show in settings (which isn't even made for our phones and adds a lot of MORE useless crap).. IMHO
I'm sure many users enjoy your method, but I think many others will also appreciate NOT having to replace their settings.apk and remove files that a VZW phone needs. Pushing the Phone.apk and Contacts.apk from Synergy is no biggie since we use that ROM anyway.
No need to get defensive bud. Team work is the key here, I'd like to eliminate all int. .apks, and try and port w.e code is missing from our VZW .SecPhone.pk and SecContacts.apk.
again, like I said - mad props for figuring this out bro, many many people across VZW on sgiii and note2 were requesting this like crazy.
and again wasn't trying to put your method down by any means, just letting those know of another way.
Click to expand...
Click to collapse
I wasn't trying to sound like I was getting defensive I was just saying what I thought. Thanks you for the props. I also have to give you props. I agree the missing code is a better and easier method then mine. And I agree team work makes the dream work lol.. I have no idea how to edit the code and go through lines of code of apks so your skills clearly surpass mine.. but yeah glad I can help with what I discovered and hope we can figure it out properly.

Help zte axon mini rooting

hi.. I just bought axon mini from China, is it possible to root this device? I wanted to install gapps to pla COC.. my android version is 5.1.1
thanks in advance..
Sent from my ZTE B2015 using Tapatalk
Can't find a dedicated and trusted one... I suggest try the oneclick root apps
I tried kingoroot and framaroot but no luck
Sent from my ZTE B2015 using Tapatalk
orbitz52 said:
I tried kingoroot and framaroot but no luck
Sent from my ZTE B2015 using Tapatalk
Click to expand...
Click to collapse
Try a few more, that's the only choice now unless you build a prerooted firmware or recovery for rooting
still not rooted..
Sent from my ZTE B2015 using Tapatalk
Root Done, Solved
Gents, I just got this phone (Axon Mini, B2016, Totally English ROM) less than a month ago and managed to root it and to replace kingroot with SuperSU, perfect.
Can't find a custom recovery yet though, I looked everywhere, so no Xposed so far. But the Phone is pretty good after tweaking the governor and removing crap (touchpal keyboard and other stuff)
I had managed to root the phone once, but after playing with link2SD (I liked it to use to managed apps) it turned out that link2D destroyed and deleted the entire system/app folder, do not use this app on this phone, it doesn't suppert 64 bit either, it cannot even freeze apps at all. So......
I found the official ROM, and flashed it with the stock recovery......everything back to the beginning. I'm not sure where I found it, but I do have the file on the SD card and on my PC at home.
However I after 1 million attempts to root it again with every single "one click" root app, I gave up. I was away on holidays so I decided to wait til I was back home to try via PC.
Back home, once again I failed 258 times.....nearly giving up again.....than.....Eureka.....
Basically:
- Install PC king root on your COMPUTER as well as the phone driver (on my PC it installed automatically, no download needed)
- in dev options, debug on and bootloader unlocked.
- here is the magic trick.....when plugging to the PC choose "install driver option", and NOT "media device MTP" or any other option.
- Run the King root app and press ROOT.......done......finally.
If you got it right you should be very lucky and certainly relieved!!!!! what a pain!!! very little on the web.
Now, not being used with kingroot, I felt uncomfortable with it as I always had SuperSU.
but before the next step, I'd like to say that I found, in the end, Kingroot a more feature rich app. It had done so far a good job as a SU app, plus it gives you the option to turn ON/OF (safely) most of the app receivers, which can be used to stop undesirable apps to wake up the phone. I did not used the "purify" app though and I found I don't really need it, but it isn't a bad app either and looked very professional.
But if you still want to replace it with super SU, it is DEAD EASY, in 2 steps.
- google and download an app called SuperSU Me.apk (my version was 6.7(64), and the actual package name is darkslide.com.supersume), run it and that is done. Kingroot will disappear and super SU will be installed.....sooooo easy.
- now you can go to playstore and update superSU, it WILL install the binaries fine via NORMAL method. Reboot and smile.
Done, no recovery needed.
But now I would consider you THE MASTER if you can come up with a custom recovery (kernel 3.10.49) so I could try install Xposed.......I miss gravitybox sooo much.
Cheers
D....
demenicis said:
Gents, I just got this phone (Axon Mini, B2016, Totally English ROM) less than a month ago and managed to root it and to replace kingroot with SuperSU, perfect.
Can't find a custom recovery yet though, I looked everywhere, so no Xposed so far. But the Phone is pretty good after tweaking the governor and removing crap (touchpal keyboard and other stuff)
I had managed to root the phone once, but after playing with link2SD (I liked it to use to managed apps) it turned out that link2D destroyed and deleted the entire system/app folder, do not use this app on this phone, it doesn't suppert 64 bit either, it cannot even freeze apps at all. So......
I found the official ROM, and flashed it with the stock recovery......everything back to the beginning. I'm not sure where I found it, but I do have the file on the SD card and on my PC at home.
However I after 1 million attempts to root it again with every single "one click" root app, I gave up. I was away on holidays so I decided to wait til I was back home to try via PC.
Back home, once again I failed 258 times.....nearly giving up again.....than.....Eureka.....
Basically:
- Install PC king root on your COMPUTER as well as the phone driver (on my PC it installed automatically, no download needed)
- in dev options, debug on and bootloader unlocked.
- here is the magic trick.....when plugging to the PC choose "install driver option", and NOT "media device MTP" or any other option.
- Run the King root app and press ROOT.......done......finally.
If you got it right you should be very lucky and certainly relieved!!!!! what a pain!!! very little on the web.
Now, not being used with kingroot, I felt uncomfortable with it as I always had SuperSU.
but before the next step, I'd like to say that I found, in the end, Kingroot a more feature rich app. It had done so far a good job as a SU app, plus it gives you the option to turn ON/OF (safely) most of the app receivers, which can be used to stop undesirable apps to wake up the phone. I did not used the "purify" app though and I found I don't really need it, but it isn't a bad app either and looked very professional.
But if you still want to replace it with super SU, it is DEAD EASY, in 2 steps.
- google and download an app called SuperSU Me.apk (my version was 6.7(64), and the actual package name is darkslide.com.supersume), run it and that is done. Kingroot will disappear and super SU will be installed.....sooooo easy.
- now you can go to playstore and update superSU, it WILL install the binaries fine via NORMAL method. Reboot and smile.
Done, no recovery needed.
But now I would consider you THE MASTER if you can come up with a custom recovery (kernel 3.10.49) so I could try install Xposed.......I miss gravitybox sooo much.
Cheers
D....
Click to expand...
Click to collapse
great!
Can I know what governor settings you have, as I strugle with lag
CPU tuner
screen on, ondemand, max=min=1344,threshold 25
screen of,battery saver,max 400,min 200
it only works every other reboot.
---------- Post added at 11:30 PM ---------- Previous post was at 11:19 PM ----------
AXON MINI (B2016).....GUESS WHAT? XPOSED INSTALLED......up and running... gravity box works perfectly.....menu button on Nov bar and everything
amazing.
no recovery yet.
download flashfire....from chain fire, obviously!, exposed.zip.....sdk22 (arm 64bit)
tried once it went black and never back......volume + & power for 10 secs
then I tried again ticking "auto mount" option.
stuck on the the boot logo for far more than usual, ~3mins, then it run some command lines for while then the logo move ahead. reboot again and it seems the dalvik cache had been cleared.....updating 205 apps.. 10 minutes later...... done. simple but my heart was pumping hard!
please note I had super SU and not king root.
axon mini b2016, international ROM.
cheers.
---------- Post added at 11:35 PM ---------- Previous post was at 11:30 PM ----------
i mean I did all that without a custom recovery.....stock one is still there but pretty useless so far other than for flashing stock ROM.
to make this phone simply perfect I still need a custom ROM to be able to backup my OS. but as long as I don't mess the system up....I already have all i need.
---------- Post added at 11:40 PM ---------- Previous post was at 11:35 PM ----------
phone is now smooth like butter. no lag at all. it seems xposed actually made it faster on its own.
even the gallery,which was lagging a bit is just fine now.
---------- Post added at 11:42 PM ---------- Previous post was at 11:40 PM ----------
sorry, one more. installed asus browser which is basically the old aosp browser.....chrome uninstalled (this ****, thanks goodness)

Verizon Root Guide (Knox still good)

I take no credit other than compiling info and making a guide. All credit goes to http://forum.xda-developers.com/member.php?u=4911585 (br3w3r, Chainfire and Princecomsy)
http://forum.xda-developers.com/att-...-root-t3410403
Also credits to Mastajeff for originally making the guide for T-Mobile.
First off download these files: http://d-h.st/PK3q
Extract them to whatever folder you want, there will be 5 files in there.
Folder named: "su" contains the SuperSU and thing needed to root the phone
ADB Setup EXE called: "adb-setup-1.4.3.exe" Needed to install ADB and the Drivers
Special patched Odin that skips the SHA 225 called: Odin PrinceComsy.exe (Mainly for AT&T)
.ini file named: "Odin3.ini"
Last, file, named: "Samsung_G935x_QC_Rooted_BOOT.TAR", this is the engBoot for the phone.
NOTE: Some users have experienced endless boot loop; this seems to be caused by using a package disabler that disabled certain services.
If you used one and end up getting an endless boot loop try wiping the cache and factory reset the phone.
I suggest you backup your phone before doing this, just in case something happens.
Install ADB by running adb-setup-1.4.3.exe
Make sure to put your phone into downloading mode (Power off--- Hold Down arrow + Home + Power button)
Open up Odin and click AP and mount Samsung_G935x_QC_Rooted_BOOT.TAR
Once restarted put the phone into USB debugging mode (Need Developer options for this)
To get developer mode, go to "About" then tap "build number" about 6 or 7 times
Go back to settings and you should now see developer options, turn on USB debugging
Now back on your PC, Move the folder named "su" into your ADB folder (Default Path: C:\adb)
Run CMD by either Win + R and typing cmd or from the control panel.
Once CMD is open type this
Code:
cd C:\adb\su
or whatever your path to your "su" folder.
After that type root.bat
Wait for the CMD to finish and then your phone should restart
Once your phone has finally restarted you will notice that SuperSU was installed and root should be working, download root checker to find out for yourself.
If your CMD just says starting Daemon and doesn't proceed any further than that, then you forgot to make sure USB debugging was turned on.
If everything went well you will see the CMD was able to push SuperSU.
You can now install Xposed via Flashfire. Unfortunately, TWRP does not work on this method, so, DO NOT TRY, there is a chance that you can Brick your phone from doing that.
NOTE: DO NOT UPDATE THE SU BINARY!
Fix for wifi bug on restart: http://forum.xda-developers.com/tmo...ticky-root-t3327399/post67592828#post67592828
Thanks 2swizzle for mentioning this.
If you want to fix the lag/slowness download any CPU or Kernel Editor or changer.
This one works fine: https://play.google.com/store/apps/details?id=com.grarak.kerneladiutor&hl=en
To fix the lag
Open up the APP
Go into the CPU settings
Set CPU Governor to ondemand
Apply on boot
Thanks to orgulloso4202 I have found a way to fix the battery drain and help with Youtube and the CPU.
L Speed seems work fine and my battery no longer drains when using the recommended Profile.
Interesting. First Sammy I've seen that Knox is intact but Samsung Pay won't work.
Have been searching a bit after rooting mine, don't suppose anyone has word on how to or if you can install TWRP or Xposed?
AlphaD1 said:
Have been searching a bit after rooting mine, don't suppose anyone has word on how to or if you can install TWRP or Xposed?
Click to expand...
Click to collapse
Got Xposed with flashfire but sadly it left me in a boot loop on the verizon logo, think I need to start over.
If we can get the bootloader unlocked it will be fun times indeed!
Going to try this soon.
Don't care if my phone blows up, it's the 4th here in the U-S-A!
Besides my trusty Nexus 6 and even Note 5 are ready for duty!
Xposed would be nice, I do miss those features.
Layer support even just to change up the statusbar.
Themes have done a nice job to blackout the device.
Root, center clock and some battery icon customizations and I'm all set for sure.
Perhaps the horrid standby time will be fixed.
Because as of late this phone has lead to high frustration to the point where I want to see how good it skips across the lake! But when I think of how much I paid for it, well I keep it in my pocket!
TWRP doesnt work, but you can install Xposed from flashfire.
Argyrus said:
TWRP doesnt work, but you can install Xposed from flashfire.
Click to expand...
Click to collapse
So with Xposed working, that means battery saving apps like Greenify and Amplify work now for our devices?
GigaSPX said:
So with Xposed working, that means battery saving apps like Greenify and Amplify work now for our devices?
Click to expand...
Click to collapse
Not 100% sure.
I haven't really installed it on my phone. I only know Xposed work due to the countless others that tried it; however, I don't see why those should not work.
Xposed is working fine and you guys need to install a kennel app and change the engboot settings to ondemand, that's why it lags and slow
2swizzle said:
Xposed is working fine and you guys need to install a kennel app and change the engboot settings to ondemand, that's why it lags and slow
Click to expand...
Click to collapse
Root gives performance issues??
GigaSPX said:
Root gives performance issues??
Click to expand...
Click to collapse
Negative. The eng kernel has shown some lag and performance slowdowns for some people but can be remedied by changing the governor.
Sent from my SM-G935V using Tapatalk
MisterSprinkles said:
Negative. The eng kernel has shown some lag and performance slowdowns for some people but can be remedied by changing the governor.
Sent from my SM-G935V using Tapatalk
Click to expand...
Click to collapse
Which governer do you recommend we use for optimal performance?
zachchen1996 said:
Which governer do you recommend we use for optimal performance?
Click to expand...
Click to collapse
Would seem the consensus is on-demand.
Sent from my SM-G935V using Tapatalk
Am I missing the download files for Verizon or are they not posted here
Can anyone report that they are suffering overheating issues after rooting even after a FDR? Thanks!
shawnten said:
Am I missing the download files for Verizon or are they not posted here
Click to expand...
Click to collapse
They are posted here: http://forum.xda-developers.com/tmobile-s7-edge/how-to/how-to-root-s7-edge-t3410470
I guess maybe I should make a thread here with all the download links and some other links that fix things.
Thread updated!
Added links and more stuff.
farfromovin said:
Interesting. First Sammy I've seen that Knox is intact but Samsung Pay won't work.
Click to expand...
Click to collapse
If you try opening the app you will get a message saying: "Access denied. Unauthorized modifications have been made to your device."
I am guessing that the app has some other type of security that checks if phone has been modded.
Anyone tried to unroot? Does Samsung Pay work if you revert NB to stock?
Sent from my SM-T320 using Tapatalk
How do we install xposed with flashfire?

Complete Root for G935P

THIS IS FOR QUALCOMM SM-G935P
I saw that the original root thread was missing a few information on the first and second post, so I decided to still offer the same information, while making the entire root process easy to follow along. All work goes to those at the Samsung G935P Root Forum and @colormedroid .
The Files Needed Are:
Odin by Princecosmy: ODIN
G935A: Galaxy S7 Edge
SuperSU: SuperSU Root
Minimal ADB and Fastboot: XDA Forums
You will also need Package Disabler Pro for Samsung: Package Disabler Pro (Samsung) $0.99
I know it costs money, but it is worth it, especially on future devices that support Samsung Admin while waiting for root.
Make sure all files above are downloaded and ready to be accessed.
These steps are best done on a factory reset (can be found in FAQ #3) on PF2 update.
Step By Step Instructions
1. After downloading Package Disabler Pro and getting it set up, you'll need to disable three packages: samsung dm phone interface, samsung dm service, and securityLogAgent.
2. Turn off your phone and boot into Download/Bootloader mode by pressing and holding the Vol Down+Home+Power after your phone is off.
3. Plug Phone into Flash the G935A.TAR in ODIN under AP and your device should restart by itself.
4. Your phone should boot straight into Android. Most likely you will have no LTE. Do not worry, that is normal. Continue onto step 5.
5. Copy the files from SuperSU to the location of your Minimal ADB and Fastboot folder on the computer (Default is "C:\Program Files (x86)\Minimal ADB and Fastboot")then after you enable USB debugging in the Developer Options menu on your phone (If you don't have Developer Options in Settings, go to About Phone, and tap on Build Number 7 Times), Run the Root.Bat file from your Minimal ADB and Fastboot Folder.
6. Open Build.Prop with BuildProp Editor and change the following settings
ro.cdma.default_numeric=310000
Change the value to 310120
ro.cdma.default_alpha=Chameleon
Change "Chameleon" to Sprint
Edit*ro.build.characteristics=Chameleon
Change "Chameleon" to Sprint
After a reboot, you should be good to go and have LTE.
Any other questions, feel free to post to the thread and myself and other helpful members of the community can help!
FAQ
1. Download and install BusyBox on Rails and get it set up. After that's set up, open up SuperSU, go to settings, and under Security check Enable SU during boot. Next, download Kernel Toolkit and under CPU set the Big Cores Maximum Frequency to 2150 Mhz. Don't forget to apply to boot from the side menu.
2. I'm stuck on the LTE splash screen. What do I do?
A: Press and hold the Volume Down + Power button down until your phone restarts. You may have to Factory Reset your device if it stays stuck on the splash screen. Get the files from FAQ #3 to successfully reset. If you wish to Re-Root, activate device beforehand by doing the Device Setup or by going into Settings - Activate Device. After Activated, follow the step by step guide.
3. I'd like to unroot and return to factory stock. How would I go about this?
A: Download the factory firmware from HERE and extract the file. Once Extracted, open ODIN and load each file in their appropriate space (BL file to BL, AP file to AP, CP file to CP, and CSC file to CSC). Make sure your phone is in download/bootloader mode by holding the Vol Down+Home+Power after the phone is off. Click Start once in download/bootloader mode and you should be back to stock once your phone reboots.
4. My WiFi credentials keep on getting erased after a reboot. What gives?
A: This seems to be an issue across all the QC S7 variants. Here's what I did to fix it. Use BuildProp Editor and change: ro.securestorage.support=true to ro.securestorage.support=false
Once the edit is saved correctly, restart your phone.
Credit goes out to: @guaneet for this fix
More answers to FAQ's to come.
Thanks, this guide is a bit clearer for beginners like me
EDIT: I can't seem to find the Minimal ADB and Fastboot Folder, where is it? (solved)
EDIT2: Where do I find the root.bat file in my phone? (solved, I had to run it from the computer not the phone)
This doesn't trip Knox right? So if I root and decide to go back stock, Samsung pay should work right?
JG96EVO said:
This doesn't trip Knox right? So if I root and decide to go back stock, Samsung pay should work right?
Click to expand...
Click to collapse
Correct. It requires to be on unchanged software. When going on complete factory reset using ODIN, it reverts any and all software changes made.
That changing the thing to sprint an the numbers to 310120 does not work for me when i do that i get no data wel 3g an it comes in an out then goes to roaming..an i cant change apns an there r no sprint apns as well...not sure if anyone els is having that
donbudafuko said:
That changing the thing to sprint an the numbers to 310120 does not work for me when i do that i get no data wel 3g an it comes in an out then goes to roaming..an i cant change apns an there r no sprint apns as well...not sure if anyone els is having that
Click to expand...
Click to collapse
Did you let the phone set up once before rooting? Did you also go into mobile networks and change roaming settings to home only?
Edit: The setup to bring your phone to Sprint did work because Sprint does not allow (unless with MSL) editing of APNs. I also made an edit that changes ro.build.characteristics=Chameleon in Build.Prop to ro.build.characteristics=Sprint. Hopefully that helps as well.
So let me throw out some errors that happened with me with the solvencies so no one has to feel like an idiot like me...
1. If Odin throws an error on your pit it will look like its good to go. It is not. Let your phone setup and then reodin
2. After initializing the 3 you disabled, go to settings, activate device. Let it activate but do NOT press done or ok or restart or a winky face emoticon or anything... But the home button and disable that same three again. Reboot. If your device keeps trying to be crazy, pick yourself up and try again.
3. For the bad file... Enable USB debugging, install the and drivers and the such then... Plug your phone into your computer and agree to the popup on your phone. After you agree (You have to be down with MTP, you know me) run the bad file on your computer. It'll say stuff and take a couple of minutes. Let it run. After reboot, reboot again. Root achieved.
Thanks so much for your clarification OP, I would've loved to use this post when I did mine lol
NOTE: Your mileage may vary... I did the buildprop change from Chameleon and the 31000 change and it negated my service. I went and changed it back, restarted, re-enabled the 3, activated the device, homed out, re-disabled the 3 and restarted. My LTE is back up and running
4. My WiFi credentials keep on getting erased after a reboot. What gives?
A: This seems to be an issue across all the QC S7 variants. Here's what I did to fix it. Use BuildProp Editor and change: ro.securestorage.support=true to ro.securestorage.support=false
Even after making these changes and verifying, my WiFi credentials and still being erased.
Hardcorp said:
4. My WiFi credentials keep on getting erased after a reboot. What gives?
A: This seems to be an issue across all the QC S7 variants. Here's what I did to fix it. Use BuildProp Editor and change: ro.securestorage.support=true to ro.securestorage.support=false
Even after making these changes and verifying, my WiFi credentials and still being erased.
Click to expand...
Click to collapse
Verify your edit stuck. Make sure there is not any extra "space" in line or end of that line. Reboot.
xyameax said:
Did you let the phone set up once before rooting? Did you also go into mobile networks and change roaming settings to home only?
Edit: The setup to bring your phone to Sprint did work because Sprint does not allow (unless with MSL) editing of APNs. I also made an edit that changes ro.build.characteristics=Chameleon in Build.Prop to ro.build.characteristics=Sprint. Hopefully that helps as well.
Click to expand...
Click to collapse
Tryed that still the samething..really doesnt mayter thimo i have data an call service as is so um goid just wanting to let everyine els know it might not work
LeftyGR said:
Verify your edit stuck. Make sure there is not any extra "space" in line or end of that line. Reboot.
Click to expand...
Click to collapse
After the next reboot they started to stick.
why can i not update su? without updating i cannot use buildprop editor... i even tried downgrading from pf2 to pe1.... no luck. phone also says custom on boot.
Are there still issues with lag and battery drain after root?
wojo797 said:
why can i not update su? without updating i cannot use buildprop editor... i even tried downgrading from pf2 to pe1.... no luck. phone also says custom on boot.
Click to expand...
Click to collapse
Updating supersu has had mixed results. Some have no problem, but it has been suggested by chainfire himself to not update it.
ch0de said:
Are there still issues with lag and battery drain after root?
Click to expand...
Click to collapse
If you follow the Kernal Auditor step, it helps with the lag and battery drain. It is because the phone is in performance mode first upon root, and so the phone throttles on heat. Setting it to Interactive brings down heat and ultimately lag and brings back battery life.
wojo797 said:
why can i not update su? without updating i cannot use buildprop editor... i even tried downgrading from pf2 to pe1.... no luck. phone also says custom on boot.
Click to expand...
Click to collapse
Are you on the Qualcomm or Exynos device? Are you sure you're G935P? I ask to try again one more time and make sure SU is installed on your phone. It may take a while for the prompt to open as well, but give it time.
xyameax said:
If you follow the Kernal Auditor step, it helps with the lag and battery drain. It is because the phone is in performance mode first upon root, and so the phone throttles on heat. Setting it to Interactive brings down heat and ultimately lag and brings back battery life.
Click to expand...
Click to collapse
Just to clarify, and I apologize for my ignorance..
When you say "helps" with battery drain and lag, does that mean it fixes the issue and it preforms at "stock", or does that mean its better then doing nothing but still more lag and battery/heat the unrooted stock ?
As per XDA forum rules, duplicating threads is not allowed. There is nothing wrong with making your contribution to the existing thread. Please continue there:
SM-G935P Root
THREAD CLOSED

Categories

Resources