Database Users

OTA update safe with just rooted phone?

I searched and found no answer. My Vibrant is just rooted to turn off the boot up and turn off sounds. Nothing else has done, is the OTA safe for my phone?

parahelium said:
I searched and found no answer. My Vibrant is just rooted to turn off the boot up and turn off sounds. Nothing else has done, is the OTA safe for my phone?
Click to expand...
Click to collapse
There are reports that it works with RyanZA's lag fix and root in some instances.
There are reports that the OTA update bricks even virgin stock phones, so it is a shot in a dark.

Personally I think I'm gonna wait till some one uploads the update and does some testing to see what is making the phone soft brick .
Sent from my SGH-T959 using XDA App

parahelium said:
I searched and found no answer. My Vibrant is just rooted to turn off the boot up and turn off sounds. Nothing else has done, is the OTA safe for my phone?
Click to expand...
Click to collapse
Root is ok but you will have to undo any lagfixes if you applied them.
It will most likely unroot your device but you can use the same method to root again.

dublued said:
Root is ok but you will have to undo any lagfixes if you applied them.
It will most likely unroot your device but you can use the same method to root again.
Click to expand...
Click to collapse
Not to be a downer but not necessarily. I was rooted with no lag fix (currently or prior) at all and it soft bricked my phone. I had the Samsung AP installed but that is about it, didn't remove bloatware or change the startup/shutdown sounds.
Got the phone running again with ODIN so I am back to stock now, without the update

gancho said:
Not to be a downer but not necessarily. I was rooted with no lag fix (currently or prior) at all and it soft bricked my phone. I had the Samsung AP installed but that is about it, didn't remove bloatware or change the startup/shutdown sounds.
Got the phone running again with ODIN so I am back to stock now, without the update
Click to expand...
Click to collapse
What a bummer...I'm rooted w/ Ryans LagFix....hope to hear some good news in a few on a solution...

lqaddict said:
There are reports that it works with RyanZA's lag fix and root in some instances.
There are reports that the OTA update bricks even virgin stock phones, so it is a shot in a dark.
Click to expand...
Click to collapse
does the virgin stock phones mean that it is unrooted or nothing is changed in the out of the box phone?

No Success Here
My Rooted Vibrant that also went through OCLF failed to boot and hung on the Vibrant splash screen. Had to use Odin and the stock build to get it back and running. Thankful I had made backups prior to trying the OTA.
I've since renamed /etc/system/otacerts.zip to stop the OTA update but I would love to get rid of the OTA update icon. Anyone have any ideas?

mine was rooted with just the ji6 modem flashed from odin.. and some other mods like mobile ap and metamorph..
so i got the update.. and it failed on install... ahhh.... flashed back pure stock on odin.. waaaaiiitning.. praying it comes back again!

Stock phone, rooted with no lagfix ever applied.
Phone is toast. I'm at work so waiting for Odin to download slowly so I can reflash the phone to stock.
Might just say skip it and apply one of the custom roms. It seems neither TMO or Samsung can get their **** together. I waited patiently for the OTA and got screwed.

Updated ok with root
My phone had the OCLF v 2.1 plus root installed. Yesterday I removed the lag fix since most folks recommended this prior to updating. Crossed my fingers and hoped my update would arrive soon.
Today my update arrived. It installed with no issues, after which my phone is still rooted. It did pause for several minutes at the Galaxy S screen, I was wondering if I had bricked it but I waited and it came through ok.
I'm not planning to reinstall the lag fix anytime soon as I don't notice that much of a change - except in the Quadant scores ;-)

d01100100 said:
Stock phone, rooted with no lagfix ever applied.
Phone is toast. I'm at work so waiting for Odin to download slowly so I can reflash the phone to stock.
Might just say skip it and apply one of the custom roms. It seems neither TMO or Samsung can get their **** together. I waited patiently for the OTA and got screwed.
Click to expand...
Click to collapse
That's what I ended up doing. I didn't want to potentially wait until the end of October so I just went ahead and flashed Bionix. I don't think I'm going back to stock ever.

atatistcheff said:
My phone had the OCLF v 2.1 plus root installed. Yesterday I removed the lag fix since most folks recommended this prior to updating. Crossed my fingers and hoped my update would arrive soon.
Today my update arrived. It installed with no issues, after which my phone is still rooted. It did pause for several minutes at the Galaxy S screen, I was wondering if I had bricked it but I waited and it came through ok.
I'm not planning to reinstall the lag fix anytime soon as I don't notice that much of a change - except in the Quadant scores ;-)
Click to expand...
Click to collapse
How many "minutes" did you wait? The notice before the update said it would take 10 minutes. I'm willing to wait, but not all night
The update portion with a status bar went my pretty quickly. My phone's been sitting on "Vibrant" for about 5 minutes and I'm starting to sweat.
I had been rooted and had OCLF but reversed both before applying the update. I also had the mobile AP, customized swype skin and custom battery meter but everything else was stock.

gancho said:
Not to be a downer but not necessarily. I was rooted with no lag fix (currently or prior) at all and it soft bricked my phone. I had the Samsung AP installed but that is about it, didn't remove bloatware or change the startup/shutdown sounds.
Got the phone running again with ODIN so I am back to stock now, without the update
Click to expand...
Click to collapse
i want to remove mobile AP just incase that is what is causing the soft bricks. ive noticed many people have problems have flashed the mobile ap. is there a way to remove with like uninstalling an application?
--without odin or flashing back to stock

I was rooted and removed some of the Samsung bloatware apps such as MediaHub etc...saw the update was available this morning and started it, phone was stuck on the Samsung Vibrant screen ever since. I put in for a replacement, could probably fix it with ODIN but new phone should be here tomorrow. I was actually having issues before that, so it could have been the phone itself...no way to be 100% sure.

For the people who had issues with their OTA, did you have a file named update.zip previously on the /sdcard directory? It's the only thing I can think of that might interfere with the OTA download, causing it to truncate. Phone is recovered and re-rooted, but the Update Firmware shows no update available. I'm going to Odin flash the 9-28 JI6 image.

That is what I am thinking as well. I have removed the update.zip from the internal storage now. The OTA is here and I postponed for a day just to be safe. I really need the GPS fix.
d01100100 said:
For the people who had issues with their OTA, did you have a file named update.zip previously on the /sdcard directory? It's the only thing I can think of that might interfere with the OTA download, causing it to truncate. Phone is recovered and re-rooted, but the Update Firmware shows no update available. I'm going to Odin flash the 9-28 JI6 image.
Click to expand...
Click to collapse

fine over here
My phone is rooted with RyanZA's one click lag fix and the update worked fine for me. I've never removed bloatware or anything though. Total I think it took about 8 minutes from start to finish.
I received the update this morning but my battery was below 10% and said I need more juice in order to install. I recharged and it kept saying the same thing after postponing a couple times. I restarted my phone and all works good now.
I'm noticing very good improvements in signal strength and flawless gps now. Maybe a speed increase also? I'm not sure about the speed thing just yet. Seems a bit snappier to me.

Lost Root
I updated to JI6 using odin based on the info in android development section, and I most definitely lost root.
Trying one click root/unroot to see if I can get root back

Nightfall983 said:
I updated to JI6 using odin based on the info in android development section, and I most definitely lost root.
Trying one click root/unroot to see if I can get root back
Click to expand...
Click to collapse
Using the recovery mode / update.zip (the classic root method) worked for me after Odin flashing JI6.

[SOLVED] Republic Wireless (Unlocked) Wireless tether Issues / Problems

Hi guys, Trying to get wifi tether set up on my unlocked, rooted Republic Wireless Moto X.
I've followed the guides for the VZW / ATT units, and they partially work but not quite. Seems the RW app has some conflicts with it.
I followed the guide here for "Wifi tether for root users" http://forum.xda-developers.com/showpost.php?p=52664158&postcount=4
It does partially work. It will successfully start tether, but you cannot change the SSID, and cannot enable encryption. No matter what you put in the "SSID" it will always show up as "wlan0" for the SSID, and unsecured. But I can connect and use the tether succcessfully (albeit with no encryption and strange SSID)...
But you CAN successfully connect and use tether. The main problem is that when you STOP tether, wifi will NOT re-enable. You have to reboot the device to get it (wifi) working correctly again. This means you will need to reboot after each time you tether....not to mention not being able to change SSID / enable encryption.
I also tried the Xposed module, and following instructions here: http://forum.xda-developers.com/moto-x/themes-apps/xposed-moto-x-4-4-tether-apk-t2601859
Also followed all steps including #6 (SPRINT ONLY - change build.prop file) (since this is sprint MVNO).
This also APPEARS to work correctly, but when I change Wifi tether for root users to use the "Native tethering", it STARTS, then it says (and I quote) "What the hell! The phone just took back wifi control???"
So it seems the RW app is preventing native tether from working.
There must be some kind of solution for us. Maybe temporarily disabling the RW app until after finished tethering, then re-enabling it?
I'd like tether to work mostly seamlessly, and don't want to have to reboot phone after each time tethering.
Any suggestions / ideas?
Thanks
-samwathegreat

samwathegreat said:
snip
Click to expand...
Click to collapse
http://forum.xda-developers.com/moto-x/general/how-to-wifi-tether-stock-4-2-2-t2449534
Follow this link.
Change the file extension from .man to .apk and install.
Follow the rest of the set up guide for tether.

!
Cyphir said:
http://forum.xda-developers.com/moto-x/general/how-to-wifi-tether-stock-4-2-2-t2449534
Follow this link.
Change the file extension from .man to .apk and install.
Follow the rest of the set up guide for tether.
Click to expand...
Click to collapse
Thanks Cyphir!
I will try this as soon as I arrive home.
I see that this guide is for 4.2.2.....I'm assuming it also applies to kit kat? Also, I checked that link, and it already has the apk extension.... I'm not seeing a .man extension...
Will reply back with results....

samwathegreat said:
Thanks Cyphir!
I will try this as soon as I arrive home.
I see that this guide is for 4.2.2.....I'm assuming it also applies to kit kat? Also, I checked that link, and it already has the apk extension.... I'm not seeing a .man extension...
Will reply back with results....
Click to expand...
Click to collapse
Thanks!!! Ok...very interesting. If I download that file on laptop, it downloads with APK extension, but if I download on phone it downloads MAN extension....
So followed instructions, and it does allow me to set SSID and encryption (THANKS!) But I'm still having some issues. Observations below:
1. When you have just rebooted your device, and click to start tether, it doesn't work (and no SSID is broadcast). But if you stop tether and start again, it does work.
2. If you follow all instructions in the linked post, but ALSO check the box for "Reload Wifi Driver 2", tether still does not start on first attempt after fresh reboot. Again, stopping and starting again works.
3. Wifi is NEVER restored correctly after reboot. It DOES reconnect to wifi, but the android OS doesn't know it. If you go into wifi settings, it will say you aren't connected, and if you try it will 'fail'....but if you check your router, the phone IS connected. But the WIFI icon completely disappears and is not restored. It won't come back until you reboot.
Also, after stopping tether, the Republic app says: "Not Connected to Wi-Fi" and underneath that "Great! Wi-Fi Calls, messages, and data" Very strange. Reboot fixes everything.
So thank you very much! You got me SSID change and encryption. Now I need to find a solution to:
1. I'd like tether to work first time. I still have to (after fresh reboot) start, stop, and start again for it to work.
2. Need to fix Wifi icon after tethering stops without having to reboot.
samwathegreat

samwathegreat said:
snip
Click to expand...
Click to collapse
That is very strange. I set it up just as the link said to, granted SU and it works perfectly the first go around. Make sure that all the settings are exactly as the post says.
It reconnects to WiFi for me right away when turned off as well.

Cyphir said:
That is very strange. I set it up just as the link said to, granted SU and it works perfectly the first go around. Make sure that all the settings are exactly as the post says.
It reconnects to WiFi for me right away when turned off as well.
Click to expand...
Click to collapse
Ok yes, very strange. So you are on 4.4.2 Kit Kat, right? Although I haven't changed *anything* and until a couple days ago I was locked & stock, I'm considering SBFing back to stock and starting over. Before I do, I'd like to make sure you're on 4.4.2 and not jellybean.
So it starts first time for you, and wifi icon comes back immediately after stopping?
Also, does your republic app (in the pulldown status bar) say "Not connected to Wi-Fi, Great! Wi-Fi Calls, messages, and texts"?
samwathegreat

samwathegreat said:
Ok yes, very strange. So you are on 4.4.2 Kit Kat, right? Although I haven't changed *anything* and until a couple days ago I was locked & stock, I'm considering SBFing back to stock and starting over. Before I do, I'd like to make sure you're on 4.4.2 and not jellybean.
So it starts first time for you, and wifi icon comes back immediately after stopping?
Also, does your republic app (in the pulldown status bar) say "Not connected to Wi-Fi, Great! Wi-Fi Calls, messages, and texts"?
samwathegreat
Click to expand...
Click to collapse
Yes, running 4.4.2. I was probably the first RW member with an unlocked bootloader. I fastboot/mfastboot ed back to stock 4.2.2 to remove root when I was still on 4.2.2 then used the update.zip to OTA to 4.4.2 then reflashed TWRP and SU.
Are you safestrapped running 4.4.2 or are you running stock 4.4.2 from OTA with root gained from TWRP and SU?
If you are going to SBF back to stock, just SBF the RW 4.4.2 and then reflash TWRP and SU. If the app still fails after that, then I am not sure.

Cyphir said:
Yes, running 4.4.2. I was probably the first RW member with an unlocked bootloader. I fastboot/mfastboot ed back to stock 4.2.2 to remove root when I was still on 4.2.2 then used the update.zip to OTA to 4.4.2 then reflashed TWRP and SU.
Are you safestrapped running 4.4.2 or are you running stock 4.4.2 from OTA with root gained from TWRP and SU?
If you are going to SBF back to stock, just SBF the RW 4.4.2 and then reflash TWRP and SU. If the app still fails after that, then I am not sure.
Click to expand...
Click to collapse
No safestrap...was never rooted until after 4.4.2 (thanks to china bl unlock).
That was the idea...just sbf, then flash twrp from bootloader, and install su from twrp. I guess I'll try that. I can't imagine why or how mine won't work....but if yours is working, then it must be me. SBF it is. Bummer....because I'm going to have to set everything (apps, widgets, etc) up -again- :/
Will post results.

samwathegreat said:
No safestrap...was never rooted until after 4.4.2 (thanks to china bl unlock).
That was the idea...just sbf, then flash twrp from bootloader, and install su from twrp. I guess I'll try that. I can't imagine why or how mine won't work....but if yours is working, then it must be me. SBF it is. Bummer....because I'm going to have to set everything (apps, widgets, etc) up -again- :/
Will post results.
Click to expand...
Click to collapse
Wow!! After SBF back to 4.4.2 stock, flash twrp, install root, I updated the preinstalled apps (including RW), installed ES file explorer (to rename man to apk), and installed as per guide. Now it works!!! Not only does it start first time, but just as you said, the wifi icon is restored as well.
I have absolutely no idea what the problem was. As I reinstall my apps, I'll check to make sure none of them interfere, but problem seems to be cured. Many thanks.

samwathegreat said:
Wow!! After SBF back to 4.4.2 stock, flash twrp, install root, I updated the preinstalled apps (including RW), installed ES file explorer (to rename man to apk), and installed as per guide. Now it works!!! Not only does it start first time, but just as you said, the wifi icon is restored as well.
I have absolutely no idea what the problem was. As I reinstall my apps, I'll check to make sure none of them interfere, but problem seems to be cured. Many thanks.
Click to expand...
Click to collapse
Final update: having re-installed all of my apps, everything is still behaving as it should. Whatever the problem is, RSD to stock fixed it. Issue solved.

Native Tethering
samwathegreat said:
Final update: having re-installed all of my apps, everything is still behaving as it should. Whatever the problem is, RSD to stock fixed it. Issue solved.
Click to expand...
Click to collapse
FYI, I got stock tethering to work by using the xposed X tether module and by changing the following build.prop variables in "/system/build.prop":
From -> to
"ro.moto.tether_dun_required=1" -> "ro.moto.tether_dun_required=0"
"ro.tether.denied=true" -> "ro.tether.denied=false"
Let me know if you have any questions.

evidenceunseen said:
FYI, I got stock tethering to work by using the xposed X tether module and by changing the following build.prop variables in "/system/build.prop":
From -> to
"ro.moto.tether_dun_required=1" -> "ro.moto.tether_dun_required=0"
"ro.tether.denied=true" -> "ro.tether.denied=false"
Let me know if you have any questions.
Click to expand...
Click to collapse
This method does not appear to work the Republic Wireless variant. Stock tether framework appears to be completely disabled (tether violates their TOS) on the RW model. When you try to activate it with xposed framework module and build.prop mod, the phone automatically "steals" back wifi access, disabling the native tether before it even starts.
I was able to get Wifi Tether for root users to work successfully.

samwathegreat said:
This method does not appear to work the Republic Wireless variant. Stock tether framework appears to be completely disabled (tether violates their TOS) on the RW model. When you try to activate it with xposed framework module and build.prop mod, the phone automatically "steals" back wifi access, disabling the native tether before it even starts.
I was able to get Wifi Tether for root users to work successfully.
Click to expand...
Click to collapse
The app breaks wifi for me once I turn tethering off.

legato89 said:
The app breaks wifi for me once I turn tethering off.
Click to expand...
Click to collapse
You probably didn't uninstall a different version of WiFi Tether for root users. The linked version is signed with different keys, so it is necessary to completely uninstall any current version before you install the linked one.
If you read all the posts in this thread, you would have seen that a similar issue was happening to me until I did a full return to stock. Then everything worked perfectly....and it still does today.

I'm on stock and rooted and I did try the apk linked, as well as others, uninstalling each before trying another.

I works for both me and @samwathegreat. Could you try flashing back to stock and trying again?
Sent from my XT1049 using XDA Free mobile app

Cyphir said:
I works for both me and @samwathegreat. Could you try flashing back to stock and trying again?
Sent from my XT1049 using XDA Free mobile app
Click to expand...
Click to collapse
Before I do this, why would reflashing to stock fix everything? Are there any alternative solutions? I am basically on a stock ROM straight from RW, and am curious why it doesn't work for me but works for you guys.

legato89 said:
Before I do this, why would reflashing to stock fix everything? Are there any alternative solutions? I am basically on a stock ROM straight from RW, and am curious why it doesn't work for me but works for you guys.
Click to expand...
Click to collapse
If you read this thread from the beginning, you would have seen that I had to flash the RW firmware before it worked for me. Afterwards, it worked perfectly and it still does today. As long as you flash the correct RW 4.4.2 firmware, it is the exact same stock firmware pre-installed on all RW devices. It is signed with Motorola release keys.
Basically, re-flashing the stock firmware can fix a damaged or corrupted file system. It didn't work for me at all until I did this. For some reason, it worked for Cyphir without flashing anything. My only guess is that something was out of place in my filesystem. I don't have any other explanations.
Save what is important to you and give it a shot if you are interested in being able to tether. I don't have any other advice or options for you otherwise. Follow all the instructions exactly.

samwathegreat said:
If you read this thread from the beginning, you would have seen that I had to flash the RW firmware before it worked for me. Afterwards, it worked perfectly and it still does today. As long as you flash the correct RW 4.4.2 firmware, it is the exact same stock firmware pre-installed on all RW devices. It is signed with Motorola release keys.
Basically, re-flashing the stock firmware can fix a damaged or corrupted file system. It didn't work for me at all until I did this. For some reason, it worked for Cyphir without flashing anything. My only guess is that something was out of place in my filesystem. I don't have any other explanations.
Save what is important to you and give it a shot if you are interested in being able to tether. I don't have any other advice or options for you otherwise. Follow all the instructions exactly.
Click to expand...
Click to collapse
It's really annoying how you assume I haven't read over and tried everything except for reflashing several times now, and just want more information before I h have to spend the time backing up and restoring. It's not unreasonable for someone to expect things to work the first time being on a clean stock build.

legato89 said:
It's really annoying how you assume I haven't read over and tried everything except for reflashing several times now, and just want more information before I h have to spend the time backing up and restoring. It's not unreasonable for someone to expect things to work the first time being on a clean stock build.
Click to expand...
Click to collapse
Annoying?
samwathegreat said:
Wow!! After SBF back to 4.4.2 stock, flash twrp, install root, I updated the preinstalled apps (including RW), installed ES file explorer (to rename man to apk), and installed as per guide. Now it works!!! Not only does it start first time, but just as you said, the wifi icon is restored as well.
I have absolutely no idea what the problem was. As I reinstall my apps, I'll check to make sure none of them interfere, but problem seems to be cured. Many thanks.
Final update: having re-installed all of my apps, everything is still behaving as it should. Whatever the problem is, RSD to stock fixed it. Issue solved.
Click to expand...
Click to collapse
Cyphir said:
I works for both me and @samwathegreat. Could you try flashing back to stock and trying again?
Click to expand...
Click to collapse
It looks quite clear to me. It *worked* out of the box for Cyphir. It didn't for me.
I stated very clearly that *I have absolutely no idea what the problem was*
My expectation was that it would work out of the box for me as well. It didn't. Why? Heck if I know!?
Moral of the story: "Whatever the problem is, RSD to stock fixed it".
That seems cut-and-dry to me. And all of that was outlined here already.
I'm done. Especially after the "annoying" comment you made. Someone else can help you. I've been more than clear that there is nothing else that will get this to work for you.
What is annoying is your unwillingness to do what both Cyphir AND myself suggested. If you are using Titanium Backup, you can backup AND restore in the matter of a few minutes. *FAR* less time than you have no doubt spent "reading over and trying everything except for reflashing".
My last suggestion is **DO NOT** backup the WiFi Tether APK. Install it from scratch from Cyphir's link. Do this before you restore ANYTHING. I bet it works immediately. And you had better save your backups to your PC, otherwise it will all get erased when you flash the SBF (flashing erases internal memory as well). Aside from that, Good Luck.
I agree that " It's not unreasonable for someone to expect things to work the first time being on a clean stock build". That's the same situation *I* was in. I just wasn't too "unreasonable" to try the only possible way of getting it to work -- flashing the stock firmware.
You and I wouldn't be the first people to have something not function correctly on unmodified, stock firmware. I can't tell you how many different individuals, with countless different issues, 100% *FIXED* their issues by simply re-flashing the stock firmware....
What I can tell you is that their issues would have never been fixed if they were too stubborn to do it.

Update from NAE to NG2!

Anyone receive this update yet?

I took the update and my build number updated, but my baseband and software still say NAE (Happened to me late time too) so hopefully the .tar file gets released soon or a way to redownload the update file and place it on my external sd card and reflash it.

churchey360 said:
I took the update and my build number updated, but my modem and software still say NAE (Happened to me late time too) so hopefully the .tar file gets released soon or a way to redownload the update file and place it on my external sd card and reflash it.
Click to expand...
Click to collapse
Did you have root? Retain root after the update?

No I was unrooted stock NAE

churchey360 said:
No I was unrooted stock NAE
Click to expand...
Click to collapse
Thanks for the reply. I'm all stock with Towelroot only. just wondering if the new "Google security fixes" will break the Towelroot exploit as I'm assuming that it will.
Also assuming that this is pretty much a useless update that only closes that exploit since Sprint was too sorry to include wifi calling as it should have.

troyboytn said:
Thanks for the reply. I'm all stock with Towelroot only. just wondering if the new "Google security fixes" will break the Towelroot exploit as I'm assuming that it will.
Also assuming that this is pretty much a useless update that only closes that exploit since Sprint was too sorry to include wifi calling as it should have.
Click to expand...
Click to collapse
Were you able to obtain root after the update?

chico1983 said:
Were you able to obtain root after the update?
Click to expand...
Click to collapse
Yeah the easiest way for me is to just flash Philz recovery with Odin and it has an option in advanced settings to reroot then just download supersu from the playstore

churchey360 said:
Yeah the easiest way for me is to just flash Philz recovery with Odin and it has an option in advanced settings to reroot then just download supersu from the playstore
Click to expand...
Click to collapse
Worked just like you said. I tried CF-autoroot and did not work for me. Have you been able to get the hot spot mod to work?

churchey360 said:
Yeah the easiest way for me is to just flash Philz recovery with Odin and it has an option in advanced settings to reroot then just download supersu from the playstore
Click to expand...
Click to collapse
but No baseband downgrade on NG2?
Philz still the bomb?

I want to do the reverse
I took the OTA to NG2 and now apps that I regularly use (DoggCatcher and Daily Roads) are reporting storage problems and are unable to write to ext SD card, even after applying NextApp fixes. Maybe I need to reset the paths or something, but if that doesnt work, what would be the best way to revert back to NAE?

rastapapa said:
I took the OTA to NG2 and now apps that I regularly use (DoggCatcher and Daily Roads) are reporting storage problems and are unable to write to ext SD card, even after applying NextApp fixes. Maybe I need to reset the paths or something, but if that doesnt work, what would be the best way to revert back to NAE?
Click to expand...
Click to collapse
Read this might help
http://forum.xda-developers.com/showthread.php?t=2840591

This is probably stupid and already answered in another thread but I'm a noob, don't flip out on me... Let's say, theoretically, I was to accept the
NG2 update. I'm rooted with Towelroot, using Supersu and Titanium backup. I've backed up then delete almost all of my bloatware with TB and have no further use for root at the time. If I were to break root with the update, will all that stuff stay the same and be safe until I can root again? I.e. If I break root, touch none of those root apps, then root again later, will they even "know" anything happened?

Since you can't take an OTA while rooted, that won't work.

frostedunit said:
Since you can't take an OTA while rooted, that won't work.
Click to expand...
Click to collapse
My phone says it has already downloaded it and is pretty enthusiastic about me accepting it. What do I do? Live with the icon in my status bar? Can I remove it? What happens if I hit [accept]?

tamiller said:
My phone says it has already downloaded it and is pretty enthusiastic about me accepting it. What do I do? Live with the icon in my status bar? Can I remove it? What happens if I hit [accept]?
Click to expand...
Click to collapse
Long press on notification it should show app info, push on that should take you to the application, then Clear Cache > uncheck Show Notification, that should stop it from showing.

2WhiteWolves said:
Long press on notification it should show app info, push on that should take you to the application, then Clear Cache > uncheck Show Notification, that should stop it from showing.
Click to expand...
Click to collapse
Thanks for posting this...EXACTLY what i was looking for. I didn't even know there was a new update out and this damn thing was nagging me when i woke up this morning. Now the more important question...What does the "HD Voice Icon" look like....lol.
But seriously, if i am stock rooted NAE, is there an upgrade path out there yet, to keep me stock rooted? And what else is in this thing, it's reporting almost 120MB....???

johnnyphive said:
Thanks for posting this...EXACTLY what i was looking for. I didn't even know there was a new update out and this damn thing was nagging me when i woke up this morning. Now the more important question...What does the "HD Voice Icon" look like....lol.
But seriously, if i am stock rooted NAE, is there an upgrade path out there yet, to keep me stock rooted? And what else is in this thing, it's reporting almost 120MB....???
Click to expand...
Click to collapse
Read this, might help with the upgrade. Read all of the thread.
http://forum.xda-developers.com/showthread.php?t=2840591
So far from what I have read, I have know idea where the HD Voice Icon is, and no one else does either, not unless it is known in another thread that I don't know about.

johnnyphive said:
Thanks for posting this...EXACTLY what i was looking for. I didn't even know there was a new update out and this damn thing was nagging me when i woke up this morning. Now the more important question...What does the "HD Voice Icon" look like....lol.
But seriously, if i am stock rooted NAE, is there an upgrade path out there yet, to keep me stock rooted? And what else is in this thing, it's reporting almost 120MB....???
Click to expand...
Click to collapse
You will have to first install the stock NAE tar file with odin to return your phone to a stock unrooted condition with the stock recovery. Then you can take the ota. After that you can reroot again with cf autoroot.

Now the question is can you keep the domestic sim unlock if you do this?

Xposed for Samsung Galaxy J3

Hey! So recently I got a Samsung Galaxy J3 and was wondering if it was possible to get Xposed on it? Flashing a Zip is not an option, by the way.

Hey man, I'm right there with you, I want to know as well. I hope this thread gets more attention! I got this phone recently myself and am so far very sad at the lack of ability to do things with it root-wise, such as getting root to frickin stick and getting things like Xposed installed (with-out boot looping your device....).

Hi,
If you're on 5.0.x, flash Xposed by arter97.
If you're on 5.1.x, flash Xposed by wanam.
Find both on Xposed General thread.
Sent from my ASUS_Z00AD

krasCGQ said:
Hi,
If you're on 5.0.x, flash Xposed by arter97.
If you're on 5.1.x, flash Xposed by wanam.
Find both on Xposed General thread.
Sent from my ASUS_Z00AD
Click to expand...
Click to collapse
The problem is that I don't have custom recovery either, and I'm not yet experienced enough to know how to flash something like xposed without it, without bootlooping. I actually already have the xposed you're talking about, wanam is what I need since im on 5.1, so if someone guides me on how to flash it or at least points me in the right direction, maybe that'd help.
Also as a side question, somewhat related to this, anyone know what I should do about custom recovery? There are models close to mine but not the exact same that are covered by TWRP or CWMR, but I've been very strongly advised against such a course of action.

darknaio said:
The problem is that I don't have custom recovery either, and I'm not yet experienced enough to know how to flash something like xposed without it, without bootlooping. I actually already have the xposed you're talking about, wanam is what I need since im on 5.1, so if someone guides me on how to flash it or at least points me in the right direction, maybe that'd help.
Also as a side question, somewhat related to this, anyone know what I should do about custom recovery? There are models close to mine but not the exact same that are covered by TWRP or CWMR, but I've been very strongly advised against such a course of action.
Click to expand...
Click to collapse
I'd recommend TWRP, actually. If your device doesn't have a custom recovery developed, it could be a pain. Just hoping if someone could develop it one for your device.
Sent from my ASUS_Z00AD

krasCGQ said:
I'd recommend TWRP, actually. If your device doesn't have a custom recovery developed, it could be a pain. Just hoping if someone could develop it one for your device.
Sent from my ASUS_Z00AD
Click to expand...
Click to collapse
I would agree with you, as I had TWRP on my last phone and liked it quite a bit. I just don't know which phone's TWRP to try and how to try and flash it on there. Do I do it through Odin? Theres (if I recall correctly) a TWRP for the Samsung Galaxy J2 and J5, on either side of my J3 (Which it's so odd that the newer phone came out with a "series" number in the middle like that). Which would you suggest I do, J2 or J5, or neither?

darknaio said:
Hey man, I'm right there with you, I want to know as well. I hope this thread gets more attention! I got this phone recently myself and am so far very sad at the lack of ability to do things with it root-wise, such as getting root to frickin stick and getting things like Xposed installed (with-out boot looping your device....).
Click to expand...
Click to collapse
Me being dumb, I tried manually installing the required files for Xposed a few weeks ago and it bricked immediately. So I had to get a replacement. I'm not sure if it's because I did it wrong but based on that I don't think we'll ever be able to install Xposed which really sucks. Coming from my previous phone which had a lot of tweaks from xposed it just feels weird using a normal phone.

darknaio said:
am so far very sad at the lack of ability to do things with it root-wise, such as getting root to frickin stick
Click to expand...
Click to collapse
I know what you mean. Every time I restart my phone I have to re-root it if I want to do something with it. Luckily I don't really need root on this phone. Mainly because of the lack of things you can do with it. Hoping to see something come out of this though

EqiiKxDude said:
Me being dumb, I tried manually installing the required files for Xposed a few weeks ago and it bricked immediately. So I had to get a replacement. I'm not sure if it's because I did it wrong but based on that I don't think we'll ever be able to install Xposed which really sucks. Coming from my previous phone which had a lot of tweaks from xposed it just feels weird using a normal phone.
Click to expand...
Click to collapse
I know exactly what you both mean. My previous crappy phone had loads of things from xposed on there that I missed. However the good news I guess is since I don't need certain UI tweaks because I'm satisfied with what this phone comes with I'm not missing out on too much. And thus far every time I get bootloop I just use Odin to flash a copy of the original firmware and somehow it doesn't reset everything so I can still keep trying without losing all my apps. Just haven't found anything that sticks. Maybe one of us should try a custom recovery from a different Samsung Galaxy J Series like the 2 or 5.

darknaio said:
I know exactly what you both mean. My previous crappy phone had loads of things from xposed on there that I missed. However the good news I guess is since I don't need certain UI tweaks because I'm satisfied with what this phone comes with I'm not missing out on too much. And thus far every time I get bootloop I just use Odin to flash a copy of the original firmware and somehow it doesn't reset everything so I can still keep trying without losing all my apps. Just haven't found anything that sticks. Maybe one of us should try a custom recovery from a different Samsung Galaxy J Series like the 2 or 5.
Click to expand...
Click to collapse
Yeah I mainly used Xposed on my previous phone to make it look more like Lollipop but since this phone comes with it I don't need it as much. And I didn't know you were able to unbrick this phone? I would have saved about $40 if I knew that ? well then yeah we should probably try one of them. I think we should go with the newest one though

Thats what I was thinking, but I don't know which J series came out before the J3 this year or I'd try that one. And yep, luckily able to unbrick it thanks to Odin. Actually unbricked it from even worse than a boot loop, I accidentally destroyed my recovery somehow so I couldn't even boot into that and do a factory reset, but thankfully Odin's separate from the recovery so it still worked. End of the day if you can at least get your phone recognized by your computer and can flash something onto it, flashing stock = unbrick (usually).

I own the J3 also. Have gained temp root via king root so I could debloat the system. We need a cf auto root option. Our device is 5.1.1 and I think the kernel has to be modified for true root. Then development can start. As for xposed,you need full root for that to work properly. I suggest to you all to get a copy of the device firmware,install odin on pc so you can reinstall firmware if you decide to use temp root and end up boot looped after debloating to much or making other potentially harmful changes.

Curtis1973 said:
I own the J3 also. Have gained temp root via king root so I could debloat the system. We need a cf auto root option. Our device is 5.1.1 and I think the kernel has to be modified for true root. Then development can start. As for xposed,you need full root for that to work properly. I suggest to you all to get a copy of the device firmware,install odin on pc so you can reinstall firmware if you decide to use temp root and end up boot looped after debloating to much or making other potentially harmful changes.
Click to expand...
Click to collapse
I have the same thing, temp root that's lost when I reboot. I've already had to go the Odin route with the original firmware so I've got my backup covered. I'm also working with the dev behind Super Sume and he thinks he has the issue resolved, if not he's going to teamview with me to try and get past this. If we manage to solve the problem I'll post the results and subsequent steps here. Hopefully this will lead to root sticking through reboot. If so then at minimum may be able to solve -some- of the problems. Though I don't know if this will fix Xposed not working, as it always caused me to boot-loop in the past (only solved by going into TWRP and rebooting from there) and even if root sticks the only way to flash Xposed according to current theories is to do so from custom recovery, which I haven't found one for this device yet.
Have you been able to get a custom recovery on your J3? If so that would be the other key part to solving a lot of these problems. If I get the Super Sume to work and someone else can manage to get a custom recovery working, maybe that'll be the start of this device's support here =D.

No but I believe by repacking an edited firnware you can add xposed that way.

Curtis1973 said:
No but I believe by repacking an edited firnware you can add xposed that way.
Click to expand...
Click to collapse
Unfortunately I wouldn't know the first thing about editing a firmware, much less be able to add Xposed lol. Could that be a way to manually add custom recovery? Or are we still dependent on someone making a version compatible with this phone?

will need a custom recovery built for the device. with proper root you could then use flashify to install it to the device. root opens the door for everything. temp root will never get much except ability to debloat the device.
---------- Post added at 08:17 AM ---------- Previous post was at 08:15 AM ----------
i reached out to chainfire in hopes of cf auto root for the j3. but have not heard back. but does not mean i wont. will see. otherwise i will keep on trying what i can.

Quick question. Has anyone updated their J3 yet? I keep getting a notification for a Software update, is it safe?

EqiiKxDude said:
Quick question. Has anyone updated their J3 yet? I keep getting a notification for a Software update, is it safe?
Click to expand...
Click to collapse
Ive been seeing that too and ignoring/swiping it away. Not sure what it is though.

my system is edited so im not getting update pushes. probably nothing significant.

Curtis1973 said:
my system is edited so im not getting update pushes. probably nothing significant.
Click to expand...
Click to collapse
Your J3 is modified? Temp root, or something else?

(Lots of words) I want to understand why I lose root instead of just flashing to fix

Let me start by saying I never gave rooted phones much though. I knew of them but never even knew anyone that ever had one. I figured the Galaxy S8 (G950U) would be a good phone to start with:laugh: Since it was my first rooted phone I couldn't resist experimenting, a lot. So I would flash this flash that, whatever I thought had a very small chance of working i flashed, lol. I usually would end up having to fireing up Odin and flashing the most important files on my PC, Partcyborg's awesome work, which I can flash with my eyes closed basically by now :laugh: Some things I would flash would just cause me to lose root though. It's driving me nuts not to be able to get it back without Odin. I could use Odin+Partcyborg's rom and have it back in 15 minutes, but I'm tired of being feed I'm ready to hunt, lol.
The thing is, I still have TWRP Safestrap custom recovery that I can access. I flash Supersu, it appears to flash fine but changes nothing, not even an SU icon in the app drawer. I did make SupoerSU Pro a system app a while ago, was that a mistake? I see it in the Apps list in Settings but I can't do much there except disable it and enable it (no it's not disabled,lol)
How can I get root back using custom recovery only? What should I have checked in Safestrap when flashing SuperSU?, Cache, System, Modem, etc? If anyone would care to explain some of the reasons I lose root but not custom recovery it would really calm my curiosity . I'm sure it would help a lot of other noobs also.
Boot animations is another thing that I find very interesting. Trying to change it has been the cause of at least 10 factory resets
I go to /system/media/ and swap out Booitanimation.zip, change the permission then I either get no change or I have reflash with Odin. What is all the files labeled Battery _000 Battery _001 Battery_002 all the way to Battery_100? Does the resolution need to be exactly the same as stock?
Is my rooted S8 not as rooted as other rooted phone? Lol, does that sentence make sense? Because of its locked bootloader and lack of custom roms is why I ask. Am I an idiot for buying a S9+ (G965U) since I love having root? I was hoping someone "cough...Part...cough cough...cyborg would be on it. If not though, no big deal. I do still have the S8 and still use it a lot even though it has no service, lol. Amazing phones not so amazing bootloaders though:laugh:
Thanks for reading. If you only skimmed it, thank you also. I know it's very long, lol. I just found something called a Combination Rom. Since I still have Safestrap I'm gonna do what I usually do, flash it and ask questions later:laugh:

Gregbmil1 said:
Let me start by saying I never gave rooted phones much though. I knew of them but never even knew anyone that ever had one. I figured the Galaxy S8 (G950U) would be a good phone to start with:laugh: Since it was my first rooted phone I couldn't resist experimenting, a lot. So I would flash this flash that, whatever I thought had a very small chance of working i flashed, lol. I usually would end up having to fireing up Odin and flashing the most important files on my PC, Partcyborg's awesome work, which I can flash with my eyes closed basically by now :laugh: Some things I would flash would just cause me to lose root though. It's driving me nuts not to be able to get it back without Odin. I could use Odin+Partcyborg's rom and have it back in 15 minutes, but I'm tired of being feed I'm ready to hunt, lol.
The thing is, I still have TWRP Safestrap custom recovery that I can access. I flash Supersu, it appears to flash fine but changes nothing, not even an SU icon in the app drawer. I did make SupoerSU Pro a system app a while ago, was that a mistake? I see it in the Apps list in Settings but I can't do much there except disable it and enable it (no it's not disabled,lol)
How can I get root back using custom recovery only? What should I have checked in Safestrap when flashing SuperSU?, Cache, System, Modem, etc? If anyone would care to explain some of the reasons I lose root but not custom recovery it would really calm my curiosity . I'm sure it would help a lot of other noobs also.
Boot animations is another thing that I find very interesting. Trying to change it has been the cause of at least 10 factory resets
I go to /system/media/ and swap out Booitanimation.zip, change the permission then I either get no change or I have reflash with Odin. What is all the files labeled Battery _000 Battery _001 Battery_002 all the way to Battery_100? Does the resolution need to be exactly the same as stock?
Is my rooted S8 not as rooted as other rooted phone? Lol, does that sentence make sense? Because of its locked bootloader and lack of custom roms is why I ask. Am I an idiot for buying a S9+ (G965U) since I love having root? I was hoping someone "cough...Part...cough cough...cyborg would be on it. If not though, no big deal. I do still have the S8 and still use it a lot even though it has no service, lol. Amazing phones not so amazing bootloaders though:laugh:
Thanks for reading. If you only skimmed it, thank you also. I know it's very long, lol. I just found something called a Combination Rom. Since I still have Safe-strap I'm gonna do what I usually do, flash it and ask questions later:laugh:
Click to expand...
Click to collapse
so the boot animations off top of my head are now located in something something and your carriers folder...The can be changed
Is it actually not rooted or is su just not responding
I have had it where the prompt never comes up and granting all just never works either normally a few reboots later it starts....
the custom rom thing is most def cause of locked boot-loader....
Up til boot-loader revision 2 is all we have root for and cannot be downgraded 3 and up....
I have myself tried flashing stock system img and then su and busy box from safe strap and up til now even this has been a no go...
Safe-strap is cool but basically No better than flashfire.IMO.
I am working with the possible bluetooth fix right now and have bricked and flashed 20 times over in the last 12 hours...

It actually is not rooted anymore after I flashed what claimed to be a boot animation for the G950U. If I open the SuperSU app it points me to a non-working site that has directions on "How to root". Plus all of the apps I have downloaded that require root all tell me I'm not rooted. Oddly enough though I was able to flash Xposed and had a green light once I opened it, (remember I still had SafeStrap recovery) it could only be accessed manually. I was shocked and yet even more confused, lol. I only tried out 2 modules before I reflashed Partcyborgs files again. Again, I was very confused as to why the modules actually worked but root only apps would start , only Xposed modules. I did only try 2 though AdBlocker Reborn and SpeedUp, both acted as if everything was normal . I wonder if it had something to do with making SuperSU a system app, which it no longer is since I reflashed with Odin.
Thanks for the info on the Bootanimation, but still I can't even delete the one I have now, for educational purposes only, Haha. It is a pretty freaking sweat bootanimtion Partcyborg included. I can't find it though T-Mobile (G950U) btw