Database Info

Android-Wifi-Tether on Sprint 2.1 RUU

I went from a stock 1.5 to 2.1 using the Sprint 2.1 RUU and all is well. I understand it's a dev build and as such is already root but when I trying installing android-wifi-tether (both 2.0 and 1.6) it all looks well except when I touch the icon to start and it fails. The 1.6 version did report I didn't have root.
What do I need to do in ADB/shell to ensure the proper permissions are there for AWT? This is the last thing I want to get working and I'm happy.
Do I need to remount the filesystem as rw? Add superuser? Not sure what's needed.
Please help.

mobilehavoc said:
I went from a stock 1.5 to 2.1 using the Sprint 2.1 RUU and all is well. I understand it's a dev build and as such is already root but when I trying installing android-wifi-tether (both 2.0 and 1.6) it all looks well except when I touch the icon to start and it fails. The 1.6 version did report I didn't have root.
What do I need to do in ADB/shell to ensure the proper permissions are there for AWT? This is the last thing I want to get working and I'm happy.
Do I need to remount the filesystem as rw? Add superuser? Not sure what's needed.
Please help.
Click to expand...
Click to collapse
is busy box installed?
is SU working?

feefeeboomboom said:
is busy box installed?
is SU working?
Click to expand...
Click to collapse
I haven't done anything since flashing the 2.1 RUU. What steps do I need to do to get busybox and su working?

if you installed the RUU that was just 'leaked' (from what i understood our 2.1 builds are based off this ruu already). The build does not include busy box or anything for that matter that is required for wireless tether-
damageless said:
Here is a link to the latest RUU from Sprint.
You cannot simply extract it. This still has root since it is a test release. I recommend just doing an adb pull of your system directory after you flash it. Don't do this when the final one comes out or else you might be stuck without root.
You will need to add busybox, patch sh and su, and make sure that you do another recovery image and such. I also recommend adding Superuser.apk and stuff. If you use the Desire build.prop, you can get most of the protected apps working.
Enjoy.
http://dl.damagedroms.com/2.0/RUU_Hero_C_Sprint_2.20.651.1_signed_test.exe
Leak, I know who you are.
Click to expand...
Click to collapse
http://benno.id.au/blog/2007/11/14/android-busybox
Busy Box link for you, I'm not really sure how to get it working but it's a start, alot of results come up if you google "busybox for android", so I hope that helps ya out bud

mobilehavoc said:
I went from a stock 1.5 to 2.1 using the Sprint 2.1 RUU and all is well. I understand it's a dev build and as such is already root but when I trying installing android-wifi-tether (both 2.0 and 1.6) it all looks well except when I touch the icon to start and it fails. The 1.6 version did report I didn't have root.
What do I need to do in ADB/shell to ensure the proper permissions are there for AWT? This is the last thing I want to get working and I'm happy.
Do I need to remount the filesystem as rw? Add superuser? Not sure what's needed.
Please help.
Click to expand...
Click to collapse
Add SU and make sure you have USB debugging on (Menu/Settings/Applications/Development/USB Debugging). This is needed so when you try to start the WIfi Tether app that is says do you allow root permissions.

dwertz said:
Add SU and make sure you have USB debugging on (Menu/Settings/Applications/Development/USB Debugging). This is needed so when you try to start the WIfi Tether app that is says do you allow root permissions.
Click to expand...
Click to collapse
How do I add su? Any guides on here. Don't understand why busy box is required for wifi tether.

mobilehavoc said:
I went from a stock 1.5 to 2.1 using the Sprint 2.1 RUU and all is well. I understand it's a dev build and as such is already root
Click to expand...
Click to collapse
Who told you that the RUU was rooted already? It's not. Why would it be? Sprint has no interest in you being root.
As for why do you have to install busybox? Because the application requires it.

It's rooted because it's a dev release. It just doesn't appear to have busybox or superuser installed

mobilehavoc said:
How do I add su? Any guides on here. Don't understand why busy box is required for wifi tether.
Click to expand...
Click to collapse
Here is the superuser.apk You have to have root.
Put superuser.apk in your C:\AndroidSDK\Tools\
adb remount
adb push superuser.apk /system/app/

mobilehavoc said:
It's rooted because it's a dev release. It just doesn't appear to have busybox or superuser installed
Click to expand...
Click to collapse
It has no reason to have either one. As for whether or not it's rooted... when you connect to it with adb, what do you get?

posguy99 said:
It has no reason to have either one. As for whether or not it's rooted... when you connect to it with adb, what do you get?
Click to expand...
Click to collapse
Not sure what you mean but I was able to push a new build prop onto the phone using adb with no issues.

posguy99 said:
It has no reason to have either one. As for whether or not it's rooted... when you connect to it with adb, what do you get?
Click to expand...
Click to collapse
The leak actually is rooted. It's an engineering leak, so root can work his magic- but only from the adb shell.

why do you need superuser?
superuser requires root, if you had root, you wouldnt need it.
you can just dl the wifi tether for root from the market
program and it would work right?

10 chars and a poke

trouble with adb

for some reason, i cannot gain permission through adb, i have tried everything. all i get is the $ sign. yes usb debugging is enabled, im running stock rom just updated with ota. i AM rooted, i have my drivers installed, idk why i cant get # via adb, someone help? any advice?

sk8dayfuknight said:
for some reason, i cannot gain permission through adb, i have tried everything. all i get is the $ sign. yes usb debugging is enabled, im running stock rom just updated with ota. i AM rooted, i have my drivers installed, idk why i cant get # via adb, someone help? any advice?
Click to expand...
Click to collapse
Follow the steps in this link: http://forum.xda-developers.com/showthread.php?t=1152148
He did an awesome job with this.
If you did follow this then you probably need to boot into recovery and change permissions settings.

when i type in su in adb i get # but when i type in adb shell i still get $, it says adb: Not found

sk8dayfuknight said:
for some reason, i cannot gain permission through adb, i have tried everything. all i get is the $ sign. yes usb debugging is enabled, im running stock rom just updated with ota. i AM rooted, i have my drivers installed, idk why i cant get # via adb, someone help? any advice?
Click to expand...
Click to collapse
i have the same issue after OTA update. root only with terminal emulator on the device. try'd to fix permission in recovery, no changes. adb shell gives me no #, only $, allways permission denied by trying su.
Edit:
it looks like that only adb can't switch the user. su_2.3.6.3_efgh is sccessfully installed via CWM 4.0.1.4 without any errors. all root apps (e.g. Titanium Backup Pro, Root Explorer, Superuser, Terminal Emulator) are working perfect. root check from market told me that adb binary is set to default shell user access as a standard non-root user. any idears?

holly1963 said:
i have the same issue after OTA update. root only with terminal emulator on the device. try'd to fix permission in recovery, no changes. adb shell gives me no #, only $, allways permission denied by trying su.
Edit:
it looks like that only adb can't switch the user. su_2.3.6.3_efgh is sccessfully installed via CWM 4.0.1.4 without any errors. all root apps (e.g. Titanium Backup Pro, Root Explorer, Superuser, Terminal Emulator) are working perfect. root check from market told me that adb binary is set to default shell user access as a standard non-root user. any idears?
Click to expand...
Click to collapse
i found i only have trouble with stock rom, i flashed leedroid rom last night and was able to get "#" with "adb shell" on the first try...

sk8dayfuknight said:
i found i only have trouble with stock rom, i flashed leedroid rom last night and was able to get "#" with "adb shell" on the first try...
Click to expand...
Click to collapse
for now i don't want to flash a custom rom, i'am using the VF stock ROM. So I still have the same issue

holly1963 said:
for now i don't want to flash a custom rom, i'am using the VF stock ROM. So I still have the same issue
Click to expand...
Click to collapse
You need to have Busybox installed.
Sent from my HTC Sensation 4G using Tapatalk

Rhiannon224 said:
You need to have Busybox installed.
Sent from my HTC Sensation 4G using Tapatalk
Click to expand...
Click to collapse
thanks for your help, busybox is successfully installed but i still can't change the user with adb
inside the trouble guide thread from the development they advice to flash a custom rom, but this is not my target.

seems the only way to get "#" from adb shell is with a custom rom. for me at least. i tried everything, changing the permissions of su, fixing permissions in recovery, and installing busybox,

When you type su are you going back to your phone and allowing super user for the unknown device? - I know that is a basic answer.

zylith said:
When you type su are you going back to your phone and allowing super user for the unknown device? - I know that is a basic answer.
Click to expand...
Click to collapse
i have thought about that method, but in the superuser.apk nothing comes up when trying to get a shell to my phone thorugh adb...

sk8dayfuknight said:
i have thought about that method, but in the superuser.apk nothing comes up when trying to get a shell to my phone thorugh adb...
Click to expand...
Click to collapse
When you're in CMD and type adb shell or su, if its the first time you should see a request to allow or deny su permission on the phone, right? Does that happen when you attempt?
Sent from my HTC Sensation Z710e

BlackElvis79 said:
When you're in CMD and type adb shell or su, if its the first time you should see a request to allow or deny su permission on the phone, right? Does that happen when you attempt?
Click to expand...
Click to collapse
there is no request on the phone, nothing happens (screen was on)

Open super user- and see if you already hit deny- You can also change it from there. Also when you type "adb devices" does your phone show up with serial number?

sk8dayfuknight said:
for some reason, i cannot gain permission through adb, i have tried everything. all i get is the $ sign. yes usb debugging is enabled, im running stock rom just updated with ota. i AM rooted, i have my drivers installed, idk why i cant get # via adb, someone help? any advice?
Click to expand...
Click to collapse
Try rooting again. Reinstall superuser.,also download busybox installer from the market and instal
Sent from my HTC Sensation Z710e using XDA App

It is not working with the stock ROM no point redoing every thing it wont work no matter how many times you try.
I doubt we will get much help it is not a problem with a custom ROM so there wont be that many peeps who will be looking into it.
Best bet it to stick a custom stock based ROM with a stock kernel.

[Q] Superuser permissions

Hello
Have unlocked the phone and installed custom android OS a while ago, but then all of a sudden i do not have root access anymore, even tryed to reinstall the phone. Though i do have a bad feeling about it wasn't needed
My problems is that im unable to give programs root access, it looks like the phone is not rooted acording to the programs.
Also if i try the following:
adb shell
su
then i get "permission denied"
Can't seem to figure out where my flaw is. Even tryed to
Anyone got an idea to what the problem might be? Have looked through the nexus s forum for clues but no luck.
/Fonain

fonain said:
Hello
Have unlocked the phone and installed custom android OS a while ago, but then all of a sudden i do not have root access anymore, even tryed to reinstall the phone. Though i do have a bad feeling about it wasn't needed
My problems is that im unable to give programs root access, it looks like the phone is not rooted acording to the programs.
Also if i try the following:
adb shell
su
then i get "permission denied"
Can't seem to figure out where my flaw is. Even tryed to
Anyone got an idea to what the problem might be? Have looked through the nexus s forum for clues but no luck.
/Fonain
Click to expand...
Click to collapse
Most likely the permissions on the su binary are f'd up (assuming it's present). The easiest fix is just to reflash the su binary (mount /system first) through CWM.

do you by any chance have a guide to do that? or a link to one?

fonain said:
do you by any chance have a guide to do that? or a link to one?
Click to expand...
Click to collapse
There are several rooting guides here if you do not have CWM installed:
http://forum.xda-developers.com/showthread.php?t=1067813
They will go over quite a few things. However, if you are unlocked and have fastboot set up it's as simple as downloading the recovery image, and then using fastboot to flash the recovery (fastboot flash recovery recovery.image.name.img)
Once CWM is installed boot into recovery and flash the su binary here:
http://forum.xda-developers.com/showthread.php?t=682828

well the funny thing is that i already have 2.3.6.1 installed, but i still dont have su rights.
When i try to follow the buttom guide where to install superuser. where it states that i should write "adb remount". Then i get the message back where it says "Operation not allowed", or when i type su i get the message "permission denied".
I seriously don't understand what i have done wrong :S
/Fonain

krohnjw said:
Most likely the permissions on the su binary are f'd up (assuming it's present). The easiest fix is just to reflash the su binary (mount /system first) through CWM.
Click to expand...
Click to collapse
Thanks for this, solved my issue

thanks figured it out
/Fonain

Sorry to bring back an old topic, but Ive petty much done everything and still the SU no permission no root access for everything occurs. NO TIT backup, no rommanager, no nothing T_T, why???

try chmod the folder/file or using sudo

james7132 said:
try chmod the folder/file or using sudo
Click to expand...
Click to collapse
Can you elaborate please. Whats chmod or sudo and how do I go about doing them?

[ROOT][TOOL][2012-07-24] GS3DebugFSRoot: Root the Verizon GSIII without flashing

THIS WILL NOT WORK WITH JELLY BEAN.
---
Here's a easy-to-use tool based on the method in this thread.
If you like this tool, please click the Thanks button!
Even better, see my signature.
DISCLAIMER: As with any rooting tool, there is some chance that something will go wrong. Use of this tool is at your own risk, and I will not be responsible if you brick your phone in the process. Although there have been zero reports of this tool breaking anyone's phone, don't run it if you aren't comfortable with the possibility of having something go wrong and having to re-Odin back to stock or worse.
Instructions:
Install the USB drivers if you don't have them already: Verizon_Wireless_I535_GSIII_Samsung_USB_Driver_v1_4_6_0.exe
Download the package and extract it somewhere (you'll need 7-Zip or some other modern compression tool) Make sure you extract all the files to a folder somewhere! Running it straight from your compression program probably won't work.
On your phone, enable installation of third-party apps (Settings --> Security --> Unknown sources, near the bottom in the "Device administration" section)
On your phone, enable USB debugging (Settings --> Developer options --> USB debugging)
On your PC, make sure you don't have any other Android devices connected, any Android emulators running, or any Android tools like PdaNet running.
Plug your phone into a USB port on your computer. For best results, use a port directly on the machine, and not a USB hub.
Double-click RootDebugfs.bat and follow the directions on the screen. Your phone will reboot 3 or 4 times during the process; just leave it plugged in. To be safe, don't switch to any other applications while the root process is running.
DOWNLOAD GS3DebugFSRoot R2 FOR US GALAXY S III VARIANTS ONLY!!!
(Released July 24, 2012)
If anything goes wrong, post here and I'll see what I can do.
Credits:
* miloj, for the debugfs root method for the Asus TF300T
* sparkym3, for his script for rooting the Asus Transformer Prime - this is a modified version of that script
* ChainsDD, for Superuser

Version History:
The most recent version is always at the top.
r2 2012-07-24
+ Changed font color to white for readability
+ Cleaned up output
+ Fixed typo in title (GSII instead of GSIII)
+ Fixed Unknown Sources/USB Debugging directions
+ Included latest version of adb from platform-tools 13, might make things more reliable
* Includes ChainsDD Superuser 3.1.3 and su binary 3.1.1
* Known to work with LF2 and LG1.
r1 2012-07-23
* Initial beta
* Includes ChainsDD Superuser 3.1.3 and su binary 3.1.1
* Works with LF2. Probably works with LG1.
Possible future features:
* APK version of the tool! I'm still not sure if this is possible - currently researching.
Sadly, I don't think this is going to happen.
* Unroot tool.
* Choice of Superuser or SuperSU.

FAQs:
Q: What versions of the stock ROM does this work with?
A: It's known to work with anything from LF2 up to LHE. It seems likely that DebugFSRoot will be able to work with any ICS ROMs. We'll have to wait and see if it works on JB or not.
Q: I'm getting an error like "adb is not recognized as an internal or external command", or "cannot stat 'su': No such file or directory". What do I do?
A: Don't run the tool straight from your compression program. Make sure to extract all the files somewhere first.
Q: Will this wipe my data?
A: Nope.
Q: How can I unroot? Will flashing a stock ROM unroot?
A: Flashing a stock ROM will unroot and also remove any modifications you made to /system.
Q: Everything seems to have worked fine, and the Superuser app shows the binary as present and working. However, none of my root apps work. What do I do?
A: This seems to happen to a very small number of people, and the cause is unknown. If this happens to you, try installing Chainfire SuperSU.
Q: Is this any better than flashing the root66 ROM?
A: The end result should be pretty much the same, but this tool is much smaller to download than the root66 ROM.
A: If you are on a phone with the stock LG1 ROM update, root66 will downgrade you to LF2, while this tool will leave your ROM alone.
Q: Is this any better than using the VRALEC boot chain method?
A: The boot chain is a little more complicated. It requires flashing two bootloaders, flashing recovery, and using Triangle Away to reset the Custom Binary Download counter. If you intend to install a custom recovery/custom ROMs anyway, it's fine and probably quicker. However, if all you want is root to run Titanium Backup or other root apps, GS3DebugFSRoot is easier.
Q: Will this increment the flash counter?
A: Not on its own. If you flash anything else after rooting, however, you might, so read up on what you're doing.
Q: Will this cause the "custom unlock" boot screen to appear?
A: In general, no. However, the spyware Samsung/Verizon included (SysScope/libcordon) is paranoid, and a lot of tweaks you can do after rooting will trigger it. If you don't want to risk getting the custom unlock screen, don't freeze any apps using Titanium Backup and generally limit your tweaking to things you could do without root.
Q: Can Samsung/Verizon block this method in the future?
Yes. It's very possible that a future OTA will patch the exploit that this tool uses. If you want to root, it's always best to do it now!

I just tried this and it appears to work. Installed Titanium Backup and SuperUser permissions were given. Thanks!
P.S.
Some of the instructions in the console app are incorrect for the location of enabling Debug Mode and Installing Unknown App Sources.

DFieldFL said:
I just tried this and it appears to work. Installed Titanium Backup and SuperUser permissions were given. Thanks!
P.S.
Some of the instructions in the console app are incorrect for the location of enabling Debug Mode and Installing Unknown App Sources.
Click to expand...
Click to collapse
Ah, I forgot to update that part in the Transformer Prime script I based this on. I'll fix it tomorrow.
Did you get the custom unlock boot screen?

Noxious Ninja said:
Ah, I forgot to update that part in the Transformer Prime script I based this on. I'll fix it tomorrow.
Did you get the custom unlock boot screen?
Click to expand...
Click to collapse
Also title says Galaxy S II not III.

Noxious Ninja said:
Ah, I forgot to update that part in the Transformer Prime script I based this on. I'll fix it tomorrow.
Did you get the custom unlock boot screen?
Click to expand...
Click to collapse
The boot screen looks the same to me.

Worked for me, thanks

Cant recognize the phone using this tool. Yet device is recognized by adb in a standalone cmd prompt..
saying "adb is not an executable file"

phantomevo77 said:
Cant recognize the phone using this tool. Yet device is recognized by adb in a standalone cmd prompt..
saying "adb is not an executable file"
Click to expand...
Click to collapse
Same thing happening to me.
EDIT: Just switched usb ports and unplugged and replugged my phone in and it worked!

If my gs3 came updated with the newest version, will this still work?

Next release will be out tonight after I test it.
DFieldFL said:
Some of the instructions in the console app are incorrect for the location of enabling Debug Mode and Installing Unknown App Sources.
Click to expand...
Click to collapse
Fixed in the next version. Also, I added those steps to the main post.
open1your1eyes0 said:
Also title says Galaxy S II not III.
Click to expand...
Click to collapse
Typo on my part. Will be fixed in the next release.
phantomevo77 said:
Cant recognize the phone using this tool. Yet device is recognized by adb in a standalone cmd prompt..
saying "adb is not an executable file"
Click to expand...
Click to collapse
I'm not sure about this one. However, I had packaged a slightly older version of adb, which could cause a difference. The next release will have the latest adb.
eakrish said:
If my gs3 came updated with the newest version, will this still work?
Click to expand...
Click to collapse
I think so, but I don't know if it's been tested. Worst case should be that it would fail when trying to copy su into /system/xbin/, and you might have to manually clean up a few things:
Code:
adb shell
[COLOR="Red"]$[/COLOR] rm /data/local/tmp
[COLOR="Red"]$[/COLOR] mv /data/local/tmp.bak /data/local/tmp
[COLOR="Red"]$[/COLOR] rm /data/local/su
[COLOR="Red"]$[/COLOR] rm /data/local/debugfs
[COLOR="Red"]$[/COLOR] rm /data/local/debugfsinput
[COLOR="Red"]$[/COLOR] exit
Really worst case is that your /system is screwed up and you have to re-flash a stock ROM with Odin, but that is highly, highly unlikely with this method.

Thanks for this awesome tool!!! Will there be a reversal to what this script does, aka, non-root to reverse changes if necessary or will that require odin flash?

It's probably possible to unroot via script. I think it might even be possible to move this into an APK and do away with adb altogether. I'll play around with it.

Is there an unroot method that's just as easy? I'd prefer not to reflash the phone to get rid of root. I guess I'm one of the oddballs here as I can care less about custom roms, I only root to be able to backup and remove bloatware.
edit: sorry I typed and posted this as others were doing the same... I couldn't delete or edit the post for a few minutes because of my newby status.

edthesped said:
Is there an unroot method that's just as easy? I'd prefer not to reflash the phone to get rid of root. I guess I'm one of the oddballs here as I can care less about custom roms, I only root to be able to backup and remove bloatware.
Click to expand...
Click to collapse
You should be able to do it via adb shell.
Code:
adb remount rw
adb shell
$ su
# rm /system/xbin/su
# exit
And then uninstall the Superuser app.
I'll try and add it to the script.

Thank You ! so much ... The tool works perfectly on my stock VZ ... Finally can get rid of all the crap that VZ puts in.

Noxious Ninja said:
It's probably possible to unroot via script. I think it might even be possible to move this into an APK and do away with adb altogether. I'll play around with it.
Click to expand...
Click to collapse
That would be awesome. It would be cool if you could make it unroot as well. Keep up the good work!
Tap'd via SGSIII(!)

CooL Very Very CooL
Thanks Noxious Ninja

eakrish said:
If my gs3 came updated with the newest version, will this still work?
Click to expand...
Click to collapse
Mine came with the update and I was able to root successfully with this tool. Very nice.

[Rom][Pre-Rooted][7.0][G920v] Offical nougat pre rooted rom

most of members the old method didn't work with him so i decide to make a pre rooted rom
*Do It AT YOUR OWN RISK!* I am not responsible for ANY damage to your device
Here is the video in how to install it all link that you will need it i put it in description of the video
please don't forget to hit thanks it takes 5 days from me to upload it
[YOUTUBE]
https://www.youtube.com/watch?v=NS0Ggcq0TfU[/YOUTUBE]
also you can open the video from here
https://www.youtube.com/watch?v=q8OT36kfo24

Tears of Joy . Woks Perfect.. Thank you @faw_wal

DDwhite said:
Tears of Joy . Woks Perfect.. Thank you @faw_wal
Click to expand...
Click to collapse
You Welcome

Many thanks faw_wal

I could place it in writing. the steps to follow
I do not know which file I should download first.
Additional I would like to know if you could share a script or a way to remove verizon apps, and keep a clean phone as if it were a total samsung

Thanks for this faw_wal

zpeady said:
Many thanks faw_wal
Click to expand...
Click to collapse
Enjoy

jotademanuel said:
I could place it in writing. the steps to follow
I do not know which file I should download first.
Additional I would like to know if you could share a script or a way to remove verizon apps, and keep a clean phone as if it were a total samsung
Click to expand...
Click to collapse
I'm sorry but it's a lot of steps to write it follow the video if video show to you black screen tonight i'm gonna to fix this problem

no-go
Tried many times, unable to get past the mounting of /system. Hard lock-up.
Edit: Had root on 7.0 finally. Looked like I was using the wrong sboot. I have too many...
Note: Tried to update superSU after I had everything how I wanted it. Lost root. Had to start over. Use caution...

I have gotten my phone rooted thanks for your help.
Now we need to find a way to bypass the system rw,remount freeze, which I think is being controlled by smu_protection or something like that.

EvilRubberDuck said:
Thanks for this faw_wal
Click to expand...
Click to collapse
You Welcome
AndroidFan16 said:
I have gotten my phone rooted thanks for your help.
Now we need to find a way to bypass the system rw,remount freeze, which I think is being controlled by smu_protection or something like that.
Click to expand...
Click to collapse
I think you phone now is rooted and you can mount system as rw just start adb
write adb shell then write su it will ask to get root from your device and then retry if doesn't work with download any explorer app like root explorer and you can edit system from it

lyphe said:
Tried many times, unable to get past the mounting of /system. Hard lock-up.
Click to expand...
Click to collapse
did you get root in super su ?

It works for the mount /system via adb? because I did it from root explorer but it freezes again, if works via adb, tell me, Im now in the 5.1.1 android rom version

does not work video ((

faw_wal said:
You Welcome
I think you phone now is rooted and you can mount system as rw just start adb
write adb shell then write su it will ask to get root from your device and then retry if doesn't work with download any explorer app like root explorer and you can edit system from it
Click to expand...
Click to collapse
Tried it on both, including
Code:
mount -o rw,remount /system
Freezing up
Especially with Amaze. Tried to write on the system partition and it hangs until I do a fresh reboot.

Has anyone tried if Samsung pay still works after root?

Ok, I'm in this nougat rom now, but the writable system still as a dream for us. I'll go back to the stock and enjoy of my Samsung apps instead of freezing my phone. Has someone knowledge about change the imei of this device? I want root for this. Or, if you know how to reboot the lollipop rooted rom correctly, can you explain me how?
Sent from my SM-G920V using XDA-Developers Legacy app

faw_wal said:
did you get root in super su ?
Click to expand...
Click to collapse
Edited original post. Finally got it working, but then lost it trying to update superSU binary.

ok i will corporate with @AndroidFan16 to figure what is the problem and when solve it i will publish it here

aceisaneight said:
Has anyone tried if Samsung pay still works after root?
Click to expand...
Click to collapse
Unsure if it "works" or not, as I never use it. However... It is bothering me to add my VISA-XXXX to Android Pay after boot. I'd say fairly good chance it does, simply because this root has thus far not touched /system for most of us. I do believe that is the red flag for SafetyNet/Pay (but I dunno. It does ask me however...)