I am rooted, and only because I wanted to edit the build prop to tweak the setting to allow all apps in dual window. I have done nothing else, not even custom recovery or removed any bloat. <br />
<br />
I don't care of I lose root. <br />
<br />
Can I take the OTA with no issues, or do I have to return to stock?<br />
<br />
Also, does anyone know if the setting will change when I do update?<br />
<br />
Thanks!<br/>
If you're just rooted and not Bump'd, I'd suggest you do the "Repair device" thing from LG PC Suite to regain stock level and then take the OTA.
Not sure if you'll be allowed to take the OTA with your device state as rooted as that currently.
Thanks. I just used stump method, still did not unlock the bootloader.
Related
I have rooted my tablet and now not able to update system. I was told that I could use OTA RootKeeper but not certain if it would work with my device. Can anyone help :crying:
Was just wondering if there was anyone that uses the phone that is not rooted and after the update still been able to tether with the changing of the APN in the device settings?
Only reason I ask is I have a One S as well that just after the update I can no longer change the APNs the device switches back on its own.
Opps so sorry this belongs in q a
if you can please move.
subscribing for a response - i just cancelled my update to hear if the update will be an issue
I'm tethered to it right now.
How are you guys tethering without root? Foxfi?
Oh crap I'm sorry, totally didn't see the not rooted part.
Make my own APN in the settings of the to bypass the software on the phone and on my computer changed the user agent string of my browser to that which is on my phone. Can also use a tablet one too.
That works as long as the phone allows you to change APN setting.
The previous version of software on the galaxy does allow you to set and use your own APN.
I'm just not sure about this new version.
Don't really want to update and lose that ability again like on the one s I have too.
stevessvt said:
Oh crap I'm sorry, totally didn't see the not rooted part.
Click to expand...
Click to collapse
I'm considering rooting to tether as I have to travel a lot in the upcoming months. What guide did you use?
Did you have to unroot to get the update then update then root again? What's the flash counter?
Lastly, what app do you use? Free Wifi Tether?
Thanks! I can PM if you want.
Dumb Question (noob)
I'm now rooted on UVLH2 if I update to the new release today, will it remain rooted or must I re-root, and is there a different root procedure or do I again use the same root process?
Sorry If I'm posting a question in the wrong place.
Thank you!
bobolinko said:
I'm now rooted on UVLH2 if I update to the new release today, will it remain rooted or must I re-root, and is there a different root procedure or do I again use the same root process?
Sorry If I'm posting a question in the wrong place.
Thank you!
Click to expand...
Click to collapse
I rooted mine before UVLH2 & after the update root was gone with counter set to 0. So, I guess same will happen for a new update & you'll have to root again.
By the way I checked for software update over data connection and got the message " Access to the software update service is provided to users in the order in which they request it. Try later."
What does that mean?
--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Phone: T-mobile Samsung Galaxy S3 16+32(class 10) gig
ROM: Stock (not sure for how long!)
Rooted: Of course Yes!
Past companions:
HTC Touch Diamond
Nokia 1110
Motorola C155
Try the APN trick method and change your computers user agent to that of the phone.
Works before the update I know that just not sure if will work after the update.
As far as upgrade from rooted? If the update comes thru and you have stock recovery should update ok but will probably lose root.
Anyone yet try this after the latest update.
No one has tried this after the update at all?
TheArtiszan said:
No one has tried this after the update at all?
Click to expand...
Click to collapse
Quiet sounds of crickets chirping...
Guess i will spend some time backing up my data just incase i have to downgrade.
Do the update and test it out.
Ill report back what i find.
I just updated. You lose root.
TheArtiszan said:
Guess i will spend some time backing up my data just incase i have to downgrade.
Do the update and test it out.
Ill report back what i find.
Click to expand...
Click to collapse
U do loose root but you can gain it back the same way you originally gained root. I just tried the free wifi app from the app store and it worked flawless. Hope it helps.
I never had root on mine (yet)
But do the tether work around and I also use with another provider.
That after the update to my One S I can't even change the APN for use on the other provider.
But I did go ahead and do the update to the Galaxy S 3 to UVLJ4 and not rooted can still change APN for use with other providers and can do the APN trick for free tethering yet.
tethering works for me .... mess around with the settings
I have a rooted Tmobile S4 and would like to check for OTA updates. I have Super SU Pro and Triangle Away (stock kernel). I ran TA and set "system modified workaround" and then rebooted. This seems to temporarily disable root but OTA still says "Your device has been modified. Software updates are not available". After the 5 minutes, I ran TA again and disabled "system modified workaround" and then tried OTA (without rebooting) and got the same result. Am I using this correctly and should it work to permit OTA updates?
iraf said:
I have a rooted Tmobile S4 and would like to check for OTA updates. I have Super SU Pro and Triangle Away (stock kernel). I ran TA and set "system modified workaround" and then rebooted. This seems to temporarily disable root but OTA still says "Your device has been modified. Software updates are not available". After the 5 minutes, I ran TA again and disabled "system modified workaround" and then tried OTA (without rebooting) and got the same result. Am I using this correctly and should it work to permit OTA updates?
Click to expand...
Click to collapse
Follow these instructions precisely. It sounds like you haven't performed steps 6 and 7, perhaps.
http://forum.xda-developers.com/showthread.php?t=2336392
RiverCity.45 said:
Follow these instructions precisely. It sounds like you haven't performed steps 6 and 7, perhaps.
http://forum.xda-developers.com/showthread.php?t=2336392
Click to expand...
Click to collapse
I was not trying to get my phone back to stock, only to be able to check for OTA updates. My understanding from reading the Triangle Away descriptiopn is that (provided you had Super SU Pro) you could do this.
iraf said:
I was not trying to get my phone back to stock, only to be able to check for OTA updates. My understanding from reading the Triangle Away descriptiopn is that (provided you had Super SU Pro) you could do this.
Click to expand...
Click to collapse
I see. You may want to address that question in the Triangle Away thread. Probably more likely to get help there. http://forum.xda-developers.com/showthread.php?t=1494114
iraf said:
I was not trying to get my phone back to stock, only to be able to check for OTA updates. My understanding from reading the Triangle Away descriptiopn is that (provided you had Super SU Pro) you could do this.
Click to expand...
Click to collapse
Is your recovery stock also? Plus sometimes you'll need to perform a factory reset before it will be "Official"
AFAIK, yes. Is there a way to check? I am reluctant to do a factory reset at this point unless absolutely necessary.
baseballfanz said:
Is your recovery stock also? Plus sometimes you'll need to perform a factory reset before it will be "Official"
Click to expand...
Click to collapse
iraf said:
AFAIK, yes. Is there a way to check? I am reluctant to do a factory reset at this point unless absolutely necessary.
Click to expand...
Click to collapse
Read step 9 and 10
http://forum.xda-developers.com/showthread.php?t=2336392
Sorry if my lack of knowledge is ticking some people off but unless I am misunderstanding a feature of Triangle Away (with Super SU Pro) (quite possible), I thought that I could temporarily alter the status of the phone such that OTA would work but WITHOUT unrooting the phone or returning it to stock. I thought that was what the "System modified workaround" feature was there to do. I've read what I thought were the relevant parts of the Triangle Away thread but I admit that I could easily have missed something in the 380 pages.
baseballfanz said:
Read step 9 and 10
http://forum.xda-developers.com/showthread.php?t=2336392
Click to expand...
Click to collapse
iraf said:
Sorry if my lack of knowledge is ticking some people off but unless I am misunderstanding a feature of Triangle Away (with Super SU Pro) (quite possible), I thought that I could temporarily alter the status of the phone such that OTA would work but WITHOUT unrooting the phone or returning it to stock. I thought that was what the "System modified workaround" feature was there to do. I've read what I thought were the relevant parts of the Triangle Away thread but I admit that I could easily have missed something in the 380 pages.
Click to expand...
Click to collapse
Dude, you don't have to read 380 pages to follow step 10 which says to factory reset. Of course, you would want to back up your data to an external location first.
Sent from my SCH-i705 using xda app-developers app
I rooted my Nexus7 using Wug's NRT, worked great. Then I took the OTA update to 4.4.3 and lost root. I thought to myself, no problem, I'll just run NRT again. I've selected the model and version fine, ADB and all the necessary files are loaded, bootloader is unlocked, and I've tried both just running the "root" command and running the unlock first, followed by the root script.
The scripts appear to complete successfully, but the device is not rooted.
Also, interestingly, the unlock command does not actually wipe the device.
Any help would be appreciated!
Edit: Well, I'm not sure why this wasn't rooted, but I ended up just doing a factory reset/wipe cache and installed CM and now everything works. I suspect something may have been screwed up by rooting and then doing the OTA update. I'll leave this thread here in case others have the problem.
I'm gonna take a wild guess and say that you were probably choosing the Nexus 7 2012 version (the build names are the same). That's what will happen if you choose the wrong build.
Can the build.prop still be edited to allow tethering without the carrier check?
Yes but you need root and if you have root you have magisk and if you have magisk you can install the tether module which changes the build prop for you.
bigv5150 said:
Yes but you need root and if you have root you have magisk and if you have magisk you can install the tether module which changes the build prop for you.
Click to expand...
Click to collapse
Can i edit it by just unlocking the boot loader and do it through adb? I don't want to root since certain apps don't work with it.
you can root, modify build.prop then unroot...
gatortuba said:
Can i edit it by just unlocking the boot loader and do it through adb? I don't want to root since certain apps don't work with it.
Click to expand...
Click to collapse
I'm pretty sure magisk has a module that hides root or magisk hide root I've never had to hide root so I really don't know but I'm pretty sure you can do that
gatortuba said:
Can i edit it by just unlocking the boot loader and do it through adb? I don't want to root since certain apps don't work with it.
Click to expand...
Click to collapse
If you have time, I would try Magisk with the hide enabled and see if your apps complain. I have not had any detect it yet. Back with supersu even with its hide add on it was a challenge but Magisk is spot on.
With magisk I was able to still use snap chat since it hides the root. YOu should be fine using other apps with magisk.
gatortuba said:
Can i edit it by just unlocking the boot loader and do it through adb? I don't want to root since certain apps don't work with it.
Click to expand...
Click to collapse
You can pull the build.prop through ADB, edit it, push it back and chmod the permissions of the file. There are guides out there with all of the necessary steps. I used to do it this way, but it got to be a pain when they started monthly updates. I went back to rooting the monthly updates and editing the build.prop.
brkshr said:
You can pull the build.prop through ADB, edit it, push it back and chmod the permissions of the file. There are guides out there with all of the necessary steps. I used to do it this way, but it got to be a pain when they started monthly updates. I went back to rooting the monthly updates and editing the build.prop.
Click to expand...
Click to collapse
Do i need to unlock to bootloader to root with magisk?
brkshr said:
You can pull the build.prop through ADB, edit it, push it back and chmod the permissions of the file. There are guides out there with all of the necessary steps. I used to do it this way, but it got to be a pain when they started monthly updates. I went back to rooting the monthly updates and editing the build.prop.
Click to expand...
Click to collapse
How does Magisk work when updates need to be applied?
brkshr said:
You can pull the build.prop through ADB, edit it, push it back and chmod the permissions of the file. There are guides out there with all of the necessary steps. I used to do it this way, but it got to be a pain when they started monthly updates. I went back to rooting the monthly updates and editing the build.prop.
Click to expand...
Click to collapse
Does it work on the latest build?
Hi, are you using pixel 2 xl..? If you are, can you provide me a copy of the build.prop of pixel 2 xl?
brkshr said:
You can pull the build.prop through ADB, edit it, push it back and chmod the permissions of the file. There are guides out there with all of the necessary steps. I used to do it this way, but it got to be a pain when they started monthly updates. I went back to rooting the monthly updates and editing the build.prop.
Click to expand...
Click to collapse
Another, possibly easier option is to install Magisk, download a file explorer from the play store, then scroll down to build.prop and just add the net.tethering.noprovisioning=true. Worked like a boss.
cedargreen said:
Another, possibly easier option is to install Magisk, download a file explorer from the play store, then scroll down to build.prop and just add the net.tethering.noprovisioning=true. Worked like a boss.
Click to expand...
Click to collapse
I can't get the file it needs, all of the files are in a payload.bin file.
Ok don't get mad I need to know if I unlocked device will wipe..
I don't want root
After unlock how. Can edit build prop to get tether working and ones I do will I be getting ota ?
vivrosh said:
Ok don't get mad I need to know if I unlocked device will wipe..
I don't want root
After unlock how. Can edit build prop to get tether working and ones I do will I be getting ota ?
Click to expand...
Click to collapse
If you use Magisk, pretty sure you can just sideload the OTA updates. You will have to go to the TWRP and Magisk threads for the XL 2. Magisk is root, but does not break Android Pay.
Can anyone summarize how best to enable hotspot tethering on the pixel 2 xl? I don't need root, and prefer to not have it enabled. I don't mind rooting it once to enable it, then unrooting, so long as the tethering capability remains and so long as Android updates occur as normal, without the need to re-enable tethering. Is this possible? Thank you.
vinhdizzo said:
Can anyone summarize how best to enable hotspot tethering on the pixel 2 xl? I don't need root, and prefer to not have it enabled. I don't mind rooting it once to enable it, then unrooting, so long as the tethering capability remains and so long as Android updates occur as normal, without the need to re-enable tethering. Is this possible? Thank you.
Click to expand...
Click to collapse
Good question.
vinhdizzo said:
Can anyone summarize how best to enable hotspot tethering on the pixel 2 xl? I don't need root, and prefer to not have it enabled. I don't mind rooting it once to enable it, then unrooting, so long as the tethering capability remains and so long as Android updates occur as normal, without the need to re-enable tethering. Is this possible? Thank you.
Click to expand...
Click to collapse
You can change build prop and then remove root but when you take the ota it may fail I'm not sure I just flash factory images to update. The other issue would be if the ota overwrites the build prop. If that happens you would have to repeat the process after every update.
bigv5150 said:
You can change build prop and then remove root but when you take the ota it may fail I'm not sure I just flash factory images to update. The other issue would be if the ota overwrites the build prop. If that happens you would have to repeat the process after every update.
Click to expand...
Click to collapse
I'm so sorry for the stupid question, but how do you do that? How to edit the build prop? I can't find any guide. I don't see any tethering module in magisk and I can't use my preferred tethering app with magisk (I contacted the dev and he said magisk broke the app). Not being able to tether is the only reason why my new P2X continues in a drawer and in I'm still using my Note 4. Please shed some light on this moron.