Related
Does it present any security issues to unlock a bootloader without rooting? I don't mean if you lose your phone, I mean is there a security issue with any apps you install?
That's always a risk. Read playstore comments before installing anything.
Has nothing to do with being rooted or not...or boot loader state.
Sent from my Moto X cellular telephone...
Cozume said:
Does it present any security issues to unlock a bootloader without rooting? I don't mean if you lose your phone, I mean is there a security issue with any apps you install?
Click to expand...
Click to collapse
You could have asked at AC and I would answer it over there.
Unlocking bootloader and/or running custom recovery is a big risk. When you unlocked bootloader, all the partitions in your phone can be accessed and modified. I can flash custom recovery to your phone. Custom recovery give full root access to the phone. It is then easily possible to copy all your data from the phone and also disable the lock for your phone. Although if you encrypt your phone, then custom recovery will require the password to give access to the /data partition, which is where all the user datas are. I guess if someone is determine enough, then they can make an image copy of your phone and try to decrypt it.
If you want to keep your data safe, disable USB Debugging (because exploits can be used with ADB to gain access to the phone), use stock recovery and lock bootloader. However, if the phone brick then you can't get back your data in the phone.
eksasol said:
Unlocking bootloader and/or running custom recovery is a big risk. When you unlocked bootloader, all the partitions in your phone can be accessed and modified.
Click to expand...
Click to collapse
but can an app do this? And if so, what permissions would the app need to do this. Also, I am not talking about flashing a custom recovery; just an unlocked bootloader.
eksasol said:
If you want to keep your data safe, disable USB Debugging (because exploits can be used with ADB to gain access to the phone), use stock recovery and lock bootloader.
Click to expand...
Click to collapse
but can an app do harm to your phone if you have USB debugging enabled? I know a person who finds your phone can. I am asking about apps.
Cozume said:
but can an app do this? And if so, what permissions would the app need to do this. Also, I am not talking about flashing a custom recovery; just an unlocked bootloader.
Click to expand...
Click to collapse
If the phone isn't root, then probably not, unless there is some security holes it can exploit. With root it is possible to modify the whole system. Motorola and HTC have an extra layer to prevent simple root to modify the system partition, but as you can see, just visit dev section if you want to remove it.
but can an app do harm to your phone if you have USB debugging enabled? I know a person who finds your phone can. I am asking about apps.
Click to expand...
Click to collapse
It is possible for apps to get access to sensitive data and change system settings with USB Debugging enabled. Helium required it turned on to make backup of your contacts, sms and apps data for example.
If you have an older Android phone, you don't need to do anything except to enable USB Debugging and run a program to install root. But we're trusting apps like SuperUser and SuperSU to control apps access to root, so that's a layer of protection. But KitKat is much safer now.
You don't need root to install malware and virus to your phone. Just download an infected app or use unreliable app stores like Aptoide. Also if you have the option "Unknown sources" enabled, which almost all of us do, the app can utilize it to automatically install other apps in the background.
Point I'm trying to make is, if the phone have unlocked bootloader, or even locked bootloader with custom recovery, and someone else have a hold of it, then all bets are off.
eksasol said:
If the phone isn't root, then probably not, unless there is some security holes it can exploit. With root it is possible to modify the whole system.
Click to expand...
Click to collapse
great, that is what I want to know. I knew a human being in possession of your phone could do more damage if it were unlocked, which is why I got rid of the bootloader unlocked warning message.
BTW - do you know if flashing the original kit kat boot logo to replace the bootloader warning message presents a problem for accepting the OTA update to 4.4.2?
eksasol said:
Motorola and HTC have an extra layer to prevent simple root to modify the system partition, but as you can see, just visit dev section if you want to remove it.
Click to expand...
Click to collapse
Ok so then on my Moto X, since flashing a new logo doesn't even require root, it shouldn't have affected any system files and then it would be safe to take the OTA after removing the bootloader unlocked warning?
eksasol said:
It is possible for apps to get access to sensitive data and change system settings with USB Debugging enabled. Helium required it turned on to make backup of your contacts, sms and apps data for example.
Click to expand...
Click to collapse
good to know!
eksasol said:
But we're trusting apps like SuperUser and SuperSU to control apps access to root, so that's a layer of protection.
Click to expand...
Click to collapse
ok, that is how I understand it. Unless I give the app access to root through SuperSU, it can't.
eksasol said:
But KitKat is much safer now.
Click to expand...
Click to collapse
why is this?
eksasol said:
Also if you have the option "Unknown sources" enabled, which almost all of us do, the app can utilize it to automatically install other apps in the background.
Click to expand...
Click to collapse
thanks, Amazon app store required that to be enabled to load apps from their app store.
Cozume said:
great, that is what I want to know. I knew a human being in possession of your phone could do more damage if it were unlocked, which is why I got rid of the bootloader unlocked warning message.
Click to expand...
Click to collapse
BTW - do you know if flashing the original kit kat boot logo to replace the bootloader warning message presents a problem for accepting the OTA update to 4.4.2?
Ok so then on my Moto X, since flashing a new logo doesn't even require root, it shouldn't have affected any system files and then it would be safe to take the OTA after removing the bootloader unlocked warning?
Click to expand...
Click to collapse
That depend on the checking that the dev put in the OTA package. On the Nexus device, if you are missing any original system APK, modify the radio partition, modify GPS setting file, or modify the build.prop, etc, the OTA will fail. So I assume the same with Moto X OTA. The safest bet is to make sure all the partition are original first (except the /data partition where your data resides) before receiving an OTA.
ok, that is how I understand it. Unless I give the app access to root through SuperSU, it can't.
Click to expand...
Click to collapse
Yes. The actual component of root isn't the SuperSU app, but a 'su' binary. Without the SuperSU app, anything can have full fledged root access. You need SuperSU to control that access.
why is this?
Click to expand...
Click to collapse
For many reason, I'm not a developer so I can only talk about what I know and seen from a user perspective. It used to be that you can flash an exploited update.zip to modify the stock recovery of Android, in order to make it ignore the package signatures, so the recovery could flash any package without the correct signature. Now there are no such exploits for latest stock recovery. With USB Debugging enabled in Android 4.3 or newer, it would not even allow access when connected to a PC unless you accept to trust that PC in a pop up dialog in the phone, I'm not sure if it's mean the phone is totally invulnerable to exploits (like memory overflow), you'll have to ask someone smarter. Also apps like Framaroot that I just linked won't work anymore.
eksasol said:
That depend on the checking that the dev put in the OTA package. On the Nexus device, if you are missing any original system APK, modify the radio partition, modify GPS setting file, or modify the build.prop, etc, the OTA will fail. So I assume the same with Moto X OTA. The safest bet is to make sure all the partition are original first (except the /data partition where your data resides) before receiving an OTA. My guess is if you tried it with modified logo it will either fail or overwrite it.
Click to expand...
Click to collapse
OK, I think I am going to unroot and flash back to stock just to be sure.
Thanks again! I would hit the thanks button but I used up all my thanks today and it won't let me.
Cozume said:
OK, I think I am going to unroot and flash back to stock just to be sure.
Thanks again! I would hit the thanks button but I used up all my thanks today and it won't let me.
Click to expand...
Click to collapse
You already gave me enough thanks at AC.
eksasol said:
You already gave me enough thanks at AC.
Click to expand...
Click to collapse
what is your user name there?
Cozume said:
what is your user name there?
Click to expand...
Click to collapse
someguy
Why so paranoid? Have you read any posts on xda of such things....I haven't.
If you are sideloading apps the risk increases for sure. But apps on the play store would have tonnes of comments about it if the app was screwing up the system.
Sent from my Moto X cellular telephone...
eksasol said:
someguy
Click to expand...
Click to collapse
ok great!
kj2112 said:
Why so paranoid? Have you read any posts on xda of such things....I haven't.
If you are sideloading apps the risk increases for sure. But apps on the play store would have tonnes of comments about it if the app was screwing up the system.
Click to expand...
Click to collapse
I am just trying to understand how all of this works.
Okay one thing why are you trying to unlock the bootloader without rooting?? Or did I read everything wrong? And yes unlocking the bootloader allows you to write to every partition of the phone. Except when HTC and you're s-on you have to manually flash the boot.img via fastboot. But with moto. There is no point in unlocking the bootloader if you're not doing anything. Two it voids your warranty. Three it can disable functions on your phone like features, camera options I think and yeah etc. But if you follow instructions you won't have any problems ever rooting or shouldn't if you semi have a brain and know how to follow instructions if not well you can somewhat brick :$ I don't mess with moto much but I have. Sorry this thread was in my latest and scrolling through xda. Lol. You can unlock you're phone straight from the moto website. But if you're not rooting. Eh no point.
Sent from my Rezound using xda-developers app. CyanogenMod 11. S-off
I just read this thread, particularly page 2 why we can't relock the Motorola bootloader (yet it seems), unlike Nexus devices, I think it's really bad for security.
edit: link: http://forum.xda-developers.com/showthread.php?t=2575586&page=2
pball52998 said:
Okay one thing why are you trying to unlock the bootloader without rooting??
Click to expand...
Click to collapse
I rooted but a friend of mine is unlocked but not rooted. She wanted to be unlocked because it wipes your device so wanted to do it before she got the phone all set up. She is afraid of rooting. Anyhow, maybe she shouldn't have unlocked but she did.
pball52998 said:
There is no point in unlocking the bootloader if you're not doing anything. Two it voids your warranty.
Click to expand...
Click to collapse
She has the dev ed so it doesn't void her warranty. And she may want to Wifi tether in the future so I told her she needs to unlock and root for that so get the dev ed. She did and unlocked but is afraid to go any further.
pball52998 said:
You can unlock you're phone straight from the moto website. But if you're not rooting. Eh no point.
Click to expand...
Click to collapse
It increases the phone's resale value to unlock it.
eksasol said:
I just read this thread, particularly page 2 why we can't relock the Motorola bootloader (yet it seems), unlike Nexus devices, I think it's really bad for security.
Click to expand...
Click to collapse
I thought I saw a thread where someone could relock the Moto X bootloader.
And what about this?
Re-Lock Your Bootloader
It should just be a command like fastboot_oem_lock or something but idk. And two if she has the dev edition. Root that thing!!! XD that's what it's for!! Just install twrp via goo manager. Wipe factory reset all that good stuff. After making a back up. Notice after backing up. Then flashing rom and gapps In that order. I mean its a lot easier than htc rezound or htc one, htc in general and such lol.
Sent from my crappy apple iPad.....
pball52998 said:
Wipe factory reset all that good stuff. After making a back up.
Click to expand...
Click to collapse
well, I didn't wipe and do a factory reset when I rooted so I guess I did it wrong, lol! That is what she is afraid of - not doing it right and messing up her phone.
And I don't have a backup, but do I really need one if I can flash the factory images?
if i update my moto x dev edition will it break foxfi. i see they just updated to 4.4 but im scared to do it hate having to use the bluetooth connection.
trinniboy68 said:
if i update my moto x dev edition will it break foxfi. i see they just updated to 4.4 but im scared to do it hate having to use the bluetooth connection.
Click to expand...
Click to collapse
Since you have the developer edition, are you rooted? If so, why not use the stock framework tether? You can use the Xposed module, or the Entitlement Check remover.
Also, if you are rooted, you can use the latest experimental build of WiFi Tether for Root Users.
Is there a specific reason you are wanting to use FoxFi? The only reason I can imagine is that you are not rooted.....but if you aren't rooted, why did you get the Developer Edition?
@trinniboy68,
I agree with @samwathegreat. If you have a Dev Edition, why not unlock your bootloader and root? It doesn't void your warranty on the Dev Edition. And its pretty easy on the Dev Edition.
If you root, and all you want to do is Tether, then to make taking future OTA's easier, I suggest using Wifi Tether For Root app (See my notes about setup at the bootom of THIS PAGE. )
Another option is [APP][MOD][Root]Hotspot Entitlement Bypass v1.1 5/9/2014, but it does make changes to the build.prop, and while it undoes them, I haven't tested to see if it changes the checksum of the build.prop when it reverts its changes(if it does, that would get in the way of future OTA's)
moto x
KidJoe said:
@trinniboy68,
I agree with @samwathegreat. If you have a Dev Edition, why not unlock your bootloader and root? It doesn't void your warranty on the Dev Edition. And its pretty easy on the Dev Edition.
If you root, and all you want to do is Tether, then to make taking future OTA's easier, I suggest using Wifi Tether For Root app (See my notes about setup at the bootom of THIS PAGE. )
Another option is [APP][MOD][Root]Hotspot Entitlement Bypass v1.1 5/9/2014, but it does make changes to the build.prop, and while it undoes them, I haven't tested to see if it changes the checksum of the build.prop when it reverts its changes(if it does, that would get in the way of future OTA's)
Click to expand...
Click to collapse
i have an unlocked bootloader. havent rooted yet cause i like the features of the moto are there roms that will dupl. the stock moto. i have verizon unlimited internet so need the ability to wifi link to my computer. as i am on the road a lot and its more secure to use my own wifi than someone elses. having a mac there arent any hacks for my phone, the one i did find the dev. isnt supporting it yet and bricking my phone i cant take right now as im fairly new to this. i rooted my s3
trinniboy68 said:
i have an unlocked bootloader. havent rooted yet cause i like the features of the moto are there roms that will dupl. the stock moto. i have verizon unlimited internet so need the ability to wifi link to my computer. as i am on the road a lot and its more secure to use my own wifi than someone elses. having a mac there arent any hacks for my phone, the one i did find the dev. isnt supporting it yet and bricking my phone i cant take right now as im fairly new to this. i rooted my s3
Click to expand...
Click to collapse
No 'hacks' for your phone? The entire android SDK is available for MAC. We have several users here who have flashed their phones 100% with MAC.
If you download the MAC Toolkit, it includes everything you need, even though it isn't supported by its devs anymore. You just won't use any of the scripts (that's all that no longer supported). Also, since you have the DEV edition, you WON'T lose your warranty by rooting it. It's HIGHLY unlikely you will brick your phone unless you do something totally stupid that is well documented here (like: you NEVER downgrade or flash older firmwares/versions on your Moto X - this is one of the few ways you can brick it).
Since you have already unlocked the BL, all you would do is fastboot flash TWRP recovery, and it will root for you. Then you can use either method that @KidJoe and I have suggested for you. There honestly isn't much at all you can mess up.
Additionally, once you install TWRP, you can take a full backup that you could restore in the event of a problem. PLUS the SBF images are available, so even without a backup your phone could still be restored back to stock.
trinniboy68 said:
i have an unlocked bootloader. havent rooted yet cause i like the features of the moto are there roms that will dupl. the stock moto. i have verizon unlimited internet so need the ability to wifi link to my computer. as i am on the road a lot and its more secure to use my own wifi than someone elses. having a mac there arent any hacks for my phone, the one i did find the dev. isnt supporting it yet and bricking my phone i cant take right now as im fairly new to this. i rooted my s3
Click to expand...
Click to collapse
Some of these sentences run together, so If I miss anything, I'm sorry.
Rooting wont remove any features of the stock Moto roms. As far as "other roms" duplicating stock, I haven't run anything but the stock rom. While there are "alternates" (like CM) if they are NOT based on stock, they will not have the Moto specific features like active display, always on listening (OK google now....), etc.
I have unlimited data too. I purchased the Dev X since I was going to have to buy an X at full retail because I wanted to keep my Unlimited (and be able to root without waiting on vulnerabilities/exploits).
All I've done is unlocked the bootloader, to root I just flashed TWRP recovery, and installed SuperSU (see -> http://forum.xda-developers.com/moto-x/moto-x-qa/step-step-instructions-unlocking-t2649738 although the TWRP and SuperSU versions linked are a little out of date now, they still work on 4.4 and 4.4.2). Then I use Wifi Tether for Root as mentioned earlier, greenify, Root Explorer, Quick Boot (reboot), Adree and not really much else that needs root, and no extra tweaks/hacks. In other words, I run stock, but rooted, with a few apps that need ROOT access, and nothing else modified on my phone.
The tools to flash the stock SBF files are RSDLite and mFastboot. Rsdlite is a GUI tool that flashes the full SBF/XML file, all commands, in like a batch mode. mFastboot is a command line tool that allows you to flash parts/pieces one at a time. I don't know if there is an RSDlite for Mac OS, but there is an mFastboot. So if you mess your phone up badly enough, you can usually recover with the stock images. (the only note being DO NOT DOWNGRADE your ROM!! for more see -> http://mark.cdmaforums.com/MotoX-Downgrade.htm )
thanks
KidJoe said:
Some of these sentences run together, so If I miss anything, I'm sorry.
Rooting wont remove any features of the stock Moto roms. As far as "other roms" duplicating stock, I haven't run anything but the stock rom. While there are "alternates" (like CM) if they are NOT based on stock, they will not have the Moto specific features like active display, always on listening (OK google now....), etc.
I have unlimited data too. I purchased the Dev X since I was going to have to buy an X at full retail because I wanted to keep my Unlimited (and be able to root without waiting on vulnerabilities/exploits).
All I've done is unlocked the bootloader, to root I just flashed TWRP recovery, and installed SuperSU (see -> http://forum.xda-developers.com/moto-x/moto-x-qa/step-step-instructions-unlocking-t2649738 although the TWRP and SuperSU versions linked are a little out of date now, they still work on 4.4 and 4.4.2). Then I use Wifi Tether for Root as mentioned earlier, greenify, Root Explorer, Quick Boot (reboot), Adree and not really much else that needs root, and no extra tweaks/hacks. In other words, I run stock, but rooted, with a few apps that need ROOT access, and nothing else modified on my phone.
The tools to flash the stock SBF files are RSDLite and mFastboot. Rsdlite is a GUI tool that flashes the full SBF/XML file, all commands, in like a batch mode. mFastboot is a command line tool that allows you to flash parts/pieces one at a time. I don't know if there is an RSDlite for Mac OS, but there is an mFastboot. So if you mess your phone up badly enough, you can usually recover with the stock images. (the only note being DO NOT DOWNGRADE your ROM!! for more see -> http://mark.cdmaforums.com/MotoX-Downgrade.htm )
Click to expand...
Click to collapse
thank you for the info
I'm strongly considering switching from Tmo to RW to save some money. I have the S4 currently, which is feature packed but just feels like a llittle kids phone. Since RWs version of the Moto X uses proprietary software for wifi calling, has this made rooting the device difficult in any way? If I want to run stock android but have root access with the X on RW will I have any difficulty or limitations/
Also, I tether occasionally, maybe once every few weeks when I'm on the go and want to use my Nexus 10 and there's no wifi around. I know RW opposes tethering. How likely are they to go after someone who tethers if they stay well below their monthly data? Have any of you heard back from them after tethering? And does androids built in tethering feature/app work once rooted, or will I have to use a third party tethering app?
Thanks.
legato89 said:
I'm strongly considering switching from Tmo to RW to save some money. I have the S4 currently, which is feature packed but just feels like a llittle kids phone. Since RWs version of the Moto X uses proprietary software for wifi calling, has this made rooting the device difficult in any way? If I want to run stock android but have root access with the X on RW will I have any difficulty or limitations/
Also, I tether occasionally, maybe once every few weeks when I'm on the go and want to use my Nexus 10 and there's no wifi around. I know RW opposes tethering. How likely are they to go after someone who tethers if they stay well below their monthly data? Have any of you heard back from them after tethering? And does androids built in tethering feature/app work once rooted, or will I have to use a third party tethering app?
Thanks.
Click to expand...
Click to collapse
YES! I'm on RW with unlocked bootloader (thanks middleman), and the WiFi tether app works perfectly (NO native/built-in tether ability on the RW variant). If you unlock your bootloader (see the China Middleman Back??) thread in the general sub-forum. let me know and I'll link you to the appropriate instructions.
I don't know if this will work with tethered root (PIE), but I doubt it. I only KNOW that it works if you have unlocked bootloader.
Additionally, the tether app I refer to "hides" tether usage, so likely they will assume you are using that data on the device itself. I've had no issues, but stay WELL within the 5GB limit (rarely exceed 2GB).
Good Luck
samwathegreat said:
YES! I'm on RW with unlocked bootloader (thanks middleman), and the WiFi tether app works perfectly (NO native/built-in tether ability on the RW variant). If you unlock your bootloader (see the China Middleman Back??) thread in the general sub-forum. let me know and I'll link you to the appropriate instructions.
I don't know if this will work with tethered root (PIE), but I doubt it. I only KNOW that it works if you have unlocked bootloader.
Additionally, the tether app I refer to "hides" tether usage, so likely they will assume you are using that data on the device itself. I've had no issues, but stay WELL within the 5GB limit (rarely exceed 2GB).
Good Luck
Click to expand...
Click to collapse
Thanks for your reply. The tethering/mobile hotspot is completely removed from the Moto X RW ROM if I'm understanding you correctly then?
Which tethering app do you use? and please do link me to the instructions you used. Does OTA updating still work when you unlock the bootloader and apply root?
legato89 said:
Thanks for your reply. The tethering/mobile hotspot is completely removed from the Moto X RW ROM if I'm understanding you correctly then?
Which tethering app do you use? and please do link me to the instructions you used. Does OTA updating still work when you unlock the bootloader and apply root?
Click to expand...
Click to collapse
OTA updating will stop working at the point you flash a custom recovery (which is required to root). You can cross that bridge when a new OTA comes out, as we will no doubt have to advise countless people on what steps to take to be able to accept the OTA. Basically it involves disabling any modifications made to /system, disabling Xposed (if installed), and flashing back STOCK RECOVERY. Being unlocked has no affect on being able to accept the OTA.
Here is the relevant thread. http://forum.xda-developers.com/moto-x/general/solved-republic-wireless-unlocked-t2755730
Be sure to use the specific wifi-tether app listed in POST # 2 in that thread. You'll notice that it didn't work for me until I did a complete return-to-stock for unknown issues. The built-in hotspot feature has somehow been disabled by RW, and attempting to use it results in the RW app immediately "stealing" back WiFi, and a message saying something to the effect of "WTF? The phone just stole back WiFi access" appears on the screen LOL! Neither the Xposed module or the entitlement bypass worked for me, with any of the options (including the Sprint-specific build.prop tweak).
PLUS, native tether does NOT 'HIDE' usage, so they might know you are indeed tethering!!! I don't suggest trying...
Good Luck, let me know if you have additional questions.
I got my Moto X a few days ago and I'm very impressed. Republic has the 30 day trial period, but I'm more 90% sure I'm sticking with it, but if I do want to return it, can I unroot/lock the bootloader? Will they check to see if it has been rooted?
Are these the instructions I should follow? I'm on 4.2.2
http://forum.xda-developers.com/moto-x/general/guide-republic-wireless-moto-x-kitkat-4-t2738233
You can always flash back to stock but you can never return the phone to its locked bootloader state. It would read "relocked" and not "locked"
Sent from my XT1049 using XDA Free mobile app
Before I update my DevEd to 4.4.4, I want to ensure that I will still be able to root (use recovery tool or something else?) and that there is some way to use tether.
On 4.4.3, I've been happy using WiFi Tether for Root users - would be nice if this continued to work, but am okay using a different method if need be.
Can someone confirm that both root & tether are functional, and if so, what method(s) are working?
With an Unlocked Bootloader, Yes, you can root by flashing TWRP and SuperSU, the same process. Just make sure you have the latest TWRP and SuperSU from their source web sites. That will be true for ALL updates so long as you have an unlocked bootloader. And it can be dev edition or carrier edition, as long as the bootloader is unlocked.
Wifi tether for root still works on my VZW Dev X with 4.4.4 update.
Mercutio5 said:
Before I update my DevEd to 4.4.4, I want to ensure that I will still be able to root (use recovery tool or something else?) and that there is some way to use tether.
On 4.4.3, I've been happy using WiFi Tether for Root users - would be nice if this continued to work, but am okay using a different method if need be.
Can someone confirm that both root & tether are functional, and if so, what method(s) are working?
Click to expand...
Click to collapse
Of course...you're unlocked. Same method - flash TWRP and it will root for you. Since you don't seem to be aware -- you can NOT update unless you flash back stock recovery and un-do any changes you made to /system including installing Xposed (if you did). If all you are using root for is WiFi Tether, nothing to worry about as you probably haven't modified /system. You WILL have to flash back the stock recovery.img before you can accept any OTA. Its always been like this.
WiFi tether should work on 4.4.4, as should the entitlement 'hack'. (I believe both have been confirmed, but check the entitlement hack threads to be sure about it)
And finally......since you mention being on 4.4.3 now, I'm assuming you are using the XT1053 GSM Dev edition (since 4.4.3 was never released for VZW). If so...you do realize that 4.4.4 isn't out yet for the XT1053, right?
It's only out for the VZW XT1060 and soak-tests are just now happening for the AT&T XT1058.
samwathegreat said:
Of course...you're unlocked. Same method - flash TWRP and it will root for you. Since you don't seem to be aware -- you can NOT update unless you flash back stock recovery and un-do any changes you made to /system including installing Xposed (if you did). If all you are using root for is WiFi Tether, nothing to worry about as you probably haven't modified /system. You WILL have to flash back the stock recovery.img before you can accept any OTA. Its always been like this.
WiFi tether should work on 4.4.4, as should the entitlement 'hack'. (I believe both have been confirmed, but check the entitlement hack threads to be sure about it)
And finally......since you mention being on 4.4.3 now, I'm assuming you are using the XT1053 GSM Dev edition (since 4.4.3 was never released for VZW). If so...you do realize that 4.4.4 isn't out yet for the XT1053, right?
It's only out for the VZW XT1060 and soak-tests are just now happening for the AT&T XT1058.
Click to expand...
Click to collapse
I'd just assumed to be on 4.4.3 since it's previous to 4.4.4 - but you're correct, I'm on 4.4.2 VZW. After reading through some update methods discussed on XDA, it seems that using RSDLite w/FXZ is the easiest - no need to undo any changes made to /system (I'm sure I've made some, but have no idea what they might have been) and no need to remove TWRP. Plus it supposedly preserves all the data.
And thank you for assuaging my concerns re: root & tether
Mercutio5 said:
I'd just assumed to be on 4.4.3 since it's previous to 4.4.4 - but you're correct, I'm on 4.4.2 VZW. After reading through some update methods discussed on XDA, it seems that using RSDLite w/FXZ is the easiest - no need to undo any changes made to /system (I'm sure I've made some, but have no idea what they might have been) and no need to remove TWRP. Plus it supposedly preserves all the data.
And thank you for assuaging my concerns re: root & tether
Click to expand...
Click to collapse
Take caution!! The original leaked fxz was indeed a keep data fxz. It's now gone. The new official leaked fxz is NOT a keep data fxz.
All you have to do is edit the XML file and remove the line containing 'erase userdata' and it will preserve your data.
If you don't do this all your data WILL be erased.
Keep that in mind...
Good luck
samwathegreat said:
Take caution!! The original leaked fxz was indeed a keep data fxz. It's now gone. The new official leaked fxz is NOT a keep data fxz.
All you have to do is edit the XML file and remove the line containing 'erase userdata' and it will preserve your data.
If you don't do this all your data WILL be erased.
Keep that in mind...
Good luck
Click to expand...
Click to collapse
Yikes!! Thank you for the heads up.
How did the leaked FXZ disappear? Surely someone's still got it somewhere?
Mercutio5 said:
Yikes!! Thank you for the heads up.
How did the leaked FXZ disappear? Surely someone's still got it somewhere?
Click to expand...
Click to collapse
Its all the same "inside" except the included XML file now contains the "Erase USERDATA" statement. Just remove that line from the XML before flashing with RSDLite and you're good.
No reason for the original leak to stick around.
Hi,
I have a Nexus 6 that I am going to start using for work.
My work has a policy that they do not allow rooted devices.
I rooted my Nexus 6 simply to get LED LightFlow to trigger the hidden LED.
When I rooted I used the Nexus Root Toolkit from Wugfresh. I did not use a Custom Recovery and I kept the stock OS (5.0.1 LRX22C)
I really would rather not have to do a wipe/reset if I don't have to. I just need the device unrooted to adhear to company policy.
(and ideally to be able to get the 5.1 OTA when it is released later this month)
D.
GADGTGUY said:
Hi,
I have a Nexus 6 that I am going to start using for work.
My work has a policy that they do not allow rooted devices.
I rooted my Nexus 6 simply to get LED LightFlow to trigger the hidden LED.
When I rooted I used the Nexus Root Toolkit from Wugfresh. I did not use a Custom Recovery and I kept the stock OS (5.0.1 LRX22C)
I really would rather not have to do a wipe/reset if I don't have to. I just need the device unrooted to adhear to company policy.
(and ideally to be able to get the 5.1 OTA when it is released later this month)
D.
Click to expand...
Click to collapse
Um how will you work know? do they have software they put on the phones? also if your worried just use root cloak. It hides root from set apps.
You can flash the images from the Google Stock image file, and skip userdata - that will restore your phone to stock, without wiping data. Look at the stickies in the general forum for N6
the_rooter said:
Um how will you work know? do they have software they put on the phones? also if your worried just use root cloak. It hides root from set apps.
Click to expand...
Click to collapse
They push a BES client that checks. They already told me they know the phone is rooted. (big brother)
jj14 said:
You can flash the images from the Google Stock image file, and skip userdata - that will restore your phone to stock, without wiping data. Look at the stickies in the general forum for N6
Click to expand...
Click to collapse
Thanks for this info....
I just noticed that in SuperSU there is a feature called: Full unroot
Can I simply do this and presto... the phone is unrooted?
Since I kept the stock OS and didn't put a custom recovery on the phone... do you think this might do the trick?
D.
GADGTGUY said:
I just noticed that in SuperSU there is a feature called: Full unroot
Can I simply do this and presto... the phone is unrooted?
Since I kept the stock OS and didn't put a custom recovery on the phone... do you think this might do the trick?
D.
Click to expand...
Click to collapse
It may - but it still won't get you direct OTA (since OTA now checks for any change to system files)
GADGTGUY said:
[snip]I just noticed that in SuperSU there is a feature called: Full unroot
Can I simply do this and presto... the phone is unrooted?
Since I kept the stock OS and didn't put a custom recovery on the phone... do you think this might do the trick?
D.
Click to expand...
Click to collapse
Just to echo what jj14 said. The "Full unroot" option in SuperSU will remove root, but it won't (at least it hadn't on the last version of it that I tried) revert one file that root modifies, so, while you won't have root, and the BES client should work, the update checks the entire file system, so it will fail. A quick flash of only the system.img file using fastboot will remove root and leave everything else untouched.
Thanks for all the advice guys!
I appreciate the assistance... this is why this community rocks!
D.
I should have paid closer attention to the Nexus Root Toolkit from WugFresh.
There is a built in option that unroots without a refresh.
D'oh
D.
GADGTGUY said:
I should have paid closer attention to the Nexus Root Toolkit from WugFresh.
There is a built in option that unroots without a refresh.
D'oh
D.
Click to expand...
Click to collapse
Many of us would recommend you learn fastboot commands manually rather than relying on toolkits. This helps you get out of trouble when things go wrong. That said, its too late now