Alright so here's the thing.
I just got a Galaxy Gear 2 Neo. I installed the Gear Manager App on my phone, and verified the Gear is the correct one. After that, the phone proceeds briefly to download some drivers or something I presume, and then the app "bounces". It just keeps opening and FC'ing, and repeating over and over. I have tried rebooting my phone, reinstalling the app. Disabling the bluetooth, turning off and on and restarting the watch.
I am beginning to think that I am going to have to return to stock S5. I still have the Mar 31st build and all original infos related to the launch. When I initially rooted, I removed a TON of crap from the phone and things I thought I would never use according to the guides that were released by other users.
I guess my question is, what am I going to have to do? I want to keep rooted as x-posed and xtether have been a lifesaver! If I have to odin back to stock, with the Mar 31st build, would I still be able to Re-root and return things to how they are now with no issues?
I am sure a lot of you, if you've read this far are like "is this guy on crack?" I am not all TOO knowledgeable with rooting, but I have successfully done it twice, and I need to push out of my bubble of fear about screwing up my device! It's my life-line to work.
~Kevin
kprice8 said:
Alright so here's the thing.
I just got a Galaxy Gear 2 Neo. I installed the Gear Manager App on my phone, and verified the Gear is the correct one. After that, the phone proceeds briefly to download some drivers or something I presume, and then the app "bounces". It just keeps opening and FC'ing, and repeating over and over. I have tried rebooting my phone, reinstalling the app. Disabling the bluetooth, turning off and on and restarting the watch.
I am beginning to think that I am going to have to return to stock S5. I still have the Mar 31st build and all original infos related to the launch. When I initially rooted, I removed a TON of crap from the phone and things I thought I would never use according to the guides that were released by other users.
I guess my question is, what am I going to have to do? I want to keep rooted as x-posed and xtether have been a lifesaver! If I have to odin back to stock, with the Mar 31st build, would I still be able to Re-root and return things to how they are now with no issues?
I am sure a lot of you, if you've read this far are like "is this guy on crack?" I am not all TOO knowledgeable with rooting, but I have successfully done it twice, and I need to push out of my bubble of fear about screwing up my device! It's my life-line to work.
~Kevin
Click to expand...
Click to collapse
Once you odin back to stock NI2 and re-root you can flash this in safestrap to get your wifi tether without having to use xposed. As for the rest of your questions I think I answered them in the other thread. Easy to follow directions to root NI2 are there as well in the OP. We do have the option to flash backwards with the firmware so far.
Thank you for the reply Misterxtc, I am sorry for the delay in reply. I managed to get the gear to connect, after watching it FC and re-open 20 times, my techie buddy put one finger on it, and it worked. Cheeky bastard. Anyhow. I replied to your other post.
Thanks again.
Related
Hey guys,
quick question. I just picked up a G tab and used Z4 root app. My problem is, everytime I shut off the unit and power it on, for the next use, I lose root and app downloaded apps are gone. Is this a known issue or is there something specific I need to do?
Well maybe you did temporary root ?
I know for a certain fact that after JM6 the z4root wouldnt work well, you might wanna give a go at SuperOneClick.
sedde said:
Well maybe you did temporary root ?
I know for a certain fact that after JM6 the z4root wouldnt work well, you might wanna give a go at SuperOneClick.
Click to expand...
Click to collapse
I try the Z4 multiple times and it was the permanent root option.
Right now it's 100% stock. Where can I get the Super One click?
I just re-booted my VZW Tab and it was rooted with Z4 and it seems to be permanent here. Not sure why yours would not be. Mine is completely stock with root.
siafu said:
I just re-booted my VZW Tab and it was rooted with Z4 and it seems to be permanent here. Not sure why yours would not be. Mine is completely stock with root.
Click to expand...
Click to collapse
Yeah I don't get it at all. The Z4 root app disappear from my list and the new market I installed disappears as well. I have to reinstall both after every boot. Does anyone have any ideas what to do?
Breakthecycle2 said:
Yeah I don't get it at all. The Z4 root app disappear from my list and the new market I installed disappears as well. I have to reinstall both after every boot. Does anyone have any ideas what to do?
Click to expand...
Click to collapse
I would say you should try a hard reset and re-do it.
SuperOneClicker can be found here in xda.
I can also vouch for Z4 permanent root on the Verizon Tab.
I have a real problem I think. Before I go return it, does anyone have a system dump so I can try and reflash this tab and start fresh? I did a system wipe and now Im getting FC in masses. Nothing stays installed and it keeps asking me to log in after every boot as if I just bought it.
I had a similar problem - I couldn't remove anything I had installed to one point and couldn't install anything new. I ran 'dmesg | busybox grep error' in a terminal on it and had lots of errors on the device used for the /data partition. I had to bring it back to verizon and get it replaced. New tab had been fine since then.
-Dan
Problem With Verizon Galaxy Tab
i am having the exact same issue as well. Seams as anyhting you do, it just goes back to the way it was after a reboot.
dragonfire540 said:
i am having the exact same issue as well. Seams as anyhting you do, it just goes back to the way it was after a reboot.
Click to expand...
Click to collapse
So it seems to be a few of us. I guess I'm going back to best buy for a new one.
I ended up returning mine. Best Buy said they've never seen anything like this and there was def something wrong...lol. Really BB?
Editing,,,
Well, it worked flawlessly on my new tab so I guess it was just the defective one. Thanks guys.
OK. I rooted using Z4 I added Rom Manager and some other apps. I wanted to created a back and the tab when back to the original state, I unrooted and uninstall all the apps and rebooted the Gtab but now it bringing back to the with Rom manager FC.... any ideas?
I'm trying to do a hard reset by pressing vol up and power.... it goes into recovery and it stop about 20% I get the triangle imagen and reboots....
Can someone help me to do the right steps?
thanks
I had the issue where rebooting my tab caused everything to revert back to a previous state and giving me various force close messages. This was on a completely stock Verizon tab with no attempts at rooting. I did a full factory reset dozens of times, and every time it went back to a previous state. I posted on here about it a few weeks ago, and no one seemed familiar with the problem. I ended up returning the tab to Best Buy and exchanging it for a new one. No problems since then.
teardropcity said:
I had the issue where rebooting my tab caused everything to revert back to a previous state and giving me various force close messages. This was on a completely stock Verizon tab with no attempts at rooting. I did a full factory reset dozens of times, and every time it went back to a previous state. I posted on here about it a few weeks ago, and no one seemed familiar with the problem. I ended up returning the tab to Best Buy and exchanging it for a new one. No problems since then.
Click to expand...
Click to collapse
Exact same string of problems here. I too returned mine and no issues since.
My roommate just got a new Fascinate. I have been trying to get it to sync with Facebook but I get multiple errors. At first it can't login, when I finally get that to work it says it says sync is unavailable. I've seen solutions to this but nothing works or is recent.
I convinced him to get an Android over an IPhone and he is ready to return it. Any ideas?
Edit: He will not root. I am going to try a hard reset tomorrow, but this seems to be a problem with the Galaxy S devices from what I have read in the last few hours.
Sent from my Nexus One using XDA App
Rooting would not help this issue, unfortunately. As far as I know, there hasn't ever been a known fix for this issue. It typically resolves itself within a couple days. Keep in mind that you can always install the Facebook app, and it will sync fine. It just won't sync the Facebook contacts. Once the SNS sync works out its attitude issues, FB contact syncing will work too. Tell him to give it a little time.
So would a hard reset be worth it at all?
I've had mine for a month. The Feeds and updates widget started having issues last week, I think on the 27th. It had worked fine before that. Since then it has been on and off.
You can install the official Facebook app for Android. It looks like it works correctly.
Doubtful. This same problem happened to me after I got a warranty replacement Fascinate. I tried everything, but nothing worked, so I gave up for a while. A few days later, I tried again, and then it synced without any problem.
Btw, the official Samsung Froyo upgrade was just leaked this morning. I can't guarantee that it will fix this issue, but it's worth a shot, and there are other benefits as well. It appears that it's been packaged so that it's installable using the stock recovery, so you shouldn't need to root in order to install it. However, the phone will be rooted as part of the install. You can download it here:
http://forum.xda-developers.com/showthread.php?t=937237
Just download that zip file to the phone's SD card, boot into recovery (hold power button + volume up + volume down from a powered off state) and flash it from there. Just FYI, if the concern with rooting is about warranty, we have methods of returning the phone to a 100% stock configuration in case you have to do a return or something, so there shouldn't be anything to worry about.
I would have to sneak it by him. I have flashed more roms than I can count on my N1 so I am definitely capable. What are the chances of bricking?
Edit: It looks like I can sneak it by after reading the thread fully. I need to do some research first. I am way too broke to brick a phone.
Thanks for your help btw.
It's almost impossible to brick this phone. As long as you can get into download mode and link it to the ODIN app on your PC, you can restore to full stock configuration. The best ODIN restore to use, should it come to that, is Adrynalyne's complete DI01 restore. It restores the ROM, kernel, radio, and recovery all to bone stock DI05 build. Just make sure that anything you flash from ODIN is done using the PDA button, NOT the Phone button. Using the Phone button will nuke the radio to an unrecoverable state.
I think I've figured it out now. Thanks for your help.
Does anyone know which is newer, and what changed between the two?
I have XXUAME2, and I've updated my firmware through Kies. I don't remember what I had before. This one must be newer.
Haven't noticed any change, apart from the blue default background in the wallpapers is now a bit darker without the sun flare. I might've noticed a few very minor things in the settings, though I don't remember what they were.
Well I was on XXUAMDC when I first got my handset, and flashed XXUAMDN via Odin when getting root access. I found it removed any carrier branding and fixed a bug with the standard launcher not allowing sorting apps in folders properly. Just wondering if XXUAME2 is newer and fixes anything else.
StuartTheFish said:
Well I was on XXUAMDC when I first got my handset, and flashed XXUAMDN via Odin when getting root access. I found it removed any carrier branding and fixed a bug with the standard launcher not allowing sorting apps in folders properly. Just wondering if XXUAME2 is newer and fixes anything else.
Click to expand...
Click to collapse
I'll tell you a sad story about XXUAME2.
I rooted my phone a few weeks after I got it, everything worked fine. Then I saw the firmware update in Kies, sure I'll download! I already knew updating stock firmware would remove root, but I could always flash it again. So after I updated my firmware, I flashed root again. This time the phone couldn't recognise the superuser app, and kept alerting that there was a threat (meaning the superuser app) every 5 minutes but root still worked. So I removed superuser completely. The threat messages didn't stop, though. I flashed a clean stock ROM, everything was fine.
Until, an ancient evil awakens! (not really ancient, but...) My Group Play app started acting weirdly. It was constantly 50-70% of my battery drain, even above the screen, on my battery page. I freezed the app and hoped for the best, but it didn't work. I couldn't remove it because my root messed up. BetterBatteryStats didn't recognise anything odd. I asked XDA, but my thread only got 1 answer telling me to look for updates, and none were to be found. Google didn't tell me anything. So I gave up, and did a factory reset. I didn't really mind, I got the phone back running and looking the same in one evening, it's not as if I had years worth of stuff in it yet. This was 2 days ago, and everything seems to be pretty much normal.
I probably messed up somewhere, but thought I'd still write a cautionary tale about updating firmware while rooted. As I mentioned, probably nothing of importance was updated, so it would be a little safer to not update. You won't miss out.
Tozenator said:
I'll tell you a sad story about XXUAME2.
I rooted my phone a few weeks after I got it, everything worked fine. Then I saw the firmware update in Kies, sure I'll download! I already knew updating stock firmware would remove root, but I could always flash it again. So after I updated my firmware, I flashed root again. This time the phone couldn't recognise the superuser app, and kept alerting that there was a threat (meaning the superuser app) every 5 minutes but root still worked. So I removed superuser completely. The threat messages didn't stop, though. I flashed a clean stock ROM, everything was fine.
Until, an ancient evil awakens! (not really ancient, but...) My Group Play app started acting weirdly. It was constantly 50-70% of my battery drain, even above the screen, on my battery page. I freezed the app and hoped for the best, but it didn't work. I couldn't remove it because my root messed up. BetterBatteryStats didn't recognise anything odd. I asked XDA, but my thread only got 1 answer telling me to look for updates, and none were to be found. Google didn't tell me anything. So I gave up, and did a factory reset. I didn't really mind, I got the phone back running and looking the same in one evening, it's not as if I had years worth of stuff in it yet. This was 2 days ago, and everything seems to be pretty much normal.
I probably messed up somewhere, but thought I'd still write a cautionary tale about updating firmware while rooted. As I mentioned, probably nothing of importance was updated, so it would be a little safer to not update. You won't miss out.
Click to expand...
Click to collapse
The reason for that is chainfire's root method doesn't work for newer versions (or should I say didn't, apparently it does now). The newer kernel didn't allow root access, making the su binary appear to be missing. The error messages are also normal on newer versions, since it detects something is trying to get root access. To get around the missing binary issue, you can use djembey's modified version of getting root instead, which afaik installs the older kernel again so it can actually get root. Then to get rid of the repeated error messages, you have to disable KNOX. Again, it says how in djembey's root thread.
XXUAMDN is one of the newer versions which didn't work via chainfire's method, yet I have root access with no issues after following djembey's thread. Might be worth a look to get yours sorted.
StuartTheFish said:
The reason for that is chainfire's root method doesn't work for newer versions (or should I say didn't, apparently it does now). The newer kernel didn't allow root access, making the su binary appear to be missing. The error messages are also normal on newer versions, since it detects something is trying to get root access. To get around the missing binary issue, you can use djembey's modified version of getting root instead, which afaik installs the older kernel again so it can actually get root. Then to get rid of the repeated error messages, you have to disable KNOX. Again, it says how in djembey's root thread.
XXUAMDN is one of the newer versions which didn't work via chainfire's method, yet I have root access with no issues after following djembey's thread. Might be worth a look to get yours sorted.
Click to expand...
Click to collapse
Interesting, very interesting. I might look into rooting one more time, then. Thanks!
Funny how you helped me instead of the other way around. Thanks again, I hope more people notice your thread and maybe you'll get your answer!
where is this new firmware xxuamdn, havent found anything about it..
im having camera, battery drain, slowness issuess still hope it fixes..
Sent from my GT-I9500 using xda app-developers app
I have none of those issues, but never did even on the older version. All I did was Google for galaxy s4 update and I found a download link for it along with Odin. But there's also XXUAME2 out there and I don't know which one I'd be better having. Unless the only difference is the radio depending on where in the world you are?
Hey guys. I rooted my M a couple days ago (5th or 6th device ive rooted) and am having some trouble this morning.
Everything seemed to be fine, I got rid of some crapware, grabbed droidwall, font installer, etc. The only major(?) change i made was putting safestrap on the phone. Afterwords, I rebooted and seen that there was no "splash screen" show up like the directions said there would be, so i figured it didnt work. This was a couple days ago. I didnt have any problems with the phone starting up at all until I changed the font a couple times. The first time, I changed it, rebooted normally, and everything changed over and appeared normal. After a few minutes of looking through the options again, I found one I liked better and installed that one. Reboot - stuck on the boot screen. Bummer. Tried to get it to start back up and it always does the same thing.
So I did some reading and am currently charging up my phone and downloading the razr_M_utility to restore and start over. Not sure what I did or why this happened. I dont recall making any other changes that could have caused it. I did use uninstall master to uninstall some of the bloatware, and thought that maybe I got rid of something that i wasnt supposed to. However, I have rebooted a few times since then and its been fine until now. Plus I'm pretty sure that I didnt uninstall anything to cause a problem.
Any additional thoughts on this would be appreciated. Like everyone else, im learning as i go! thanks
tangler27 said:
Hey guys. I rooted my M a couple days ago (5th or 6th device ive rooted) and am having some trouble this morning.
Everything seemed to be fine, I got rid of some crapware, grabbed droidwall, font installer, etc. The only major(?) change i made was putting safestrap on the phone. Afterwords, I rebooted and seen that there was no "splash screen" show up like the directions said there would be, so i figured it didnt work. This was a couple days ago. I didnt have any problems with the phone starting up at all until I changed the font a couple times. The first time, I changed it, rebooted normally, and everything changed over and appeared normal. After a few minutes of looking through the options again, I found one I liked better and installed that one. Reboot - stuck on the boot screen. Bummer. Tried to get it to start back up and it always does the same thing.
So I did some reading and am currently charging up my phone and downloading the razr_M_utility to restore and start over. Not sure what I did or why this happened. I dont recall making any other changes that could have caused it. I did use uninstall master to uninstall some of the bloatware, and thought that maybe I got rid of something that i wasnt supposed to. However, I have rebooted a few times since then and its been fine until now. Plus I'm pretty sure that I didnt uninstall anything to cause a problem.
Any additional thoughts on this would be appreciated. Like everyone else, im learning as i go! thanks
Click to expand...
Click to collapse
Utility is gonna take care of it for you...I'm certain. I cant think of anything that caused it though. That's kinda weird. But if I were you I would just stick with the stock ROM with that issue and just troubleshoot it and if it happens again...hit it with the utility again
Also if you don't mind losing camcorder the 4.2.2 ROMs are great and don't require safe strap as Kong as you unlock boot loader through the utility. But will void your warranty.
Good luck! And follow those instructions on Matt's utility perfectly!
Sent from my XT907 using xda app-developers app
I bought an unlocked AT&T S4 a few months ago. It had Lollipop on it when I got it. I rooted it with Kingoroot and, Kingoroot's idiosyncrasies notwithstanding, everything worked fine. I was able to tweak some apps' config files, give myself 16 million color bombs in Candy Crush, and things like that.
Then I flew too close to the Sun - TWRP, Cyanogenmod (or whatever it's called), etc. A few misteps found me with a boot loop problem. "Software not athorized by AT&T..." was all she wrote.
I started reading some of the forums, played a bit with Kies, installed Odin, and finally got the phone to start up. Problem is I'm now running Jellybean with no Wi-Fi. The phone works fine otherwise and Smart Switch reinstalled all of my apps ( I wasn't expecting that). I rooted it using saferoot (pretty cool!). But I'd like to go back to Lollipop and get my Wi-Fi back, though I'd settle for Jellybean if I can get Wi-Fi working, if that's the best I can do.
Can somebody point me in the right direction?
Sounds like your phone has a locked bootloader which means you cannot install TWRP, or CWM,
Have you checked here for a solution: http://forum.xda-developers.com/showthread.php?t=2616221 ?
audit13 said:
Sounds like your phone has a locked bootloader which means you cannot install TWRP, or CWM,
Have you checked here for a solution: http://forum.xda-developers.com/showthread.php?t=2616221 ?
Click to expand...
Click to collapse
Nailed it! After following that link and finding the common elements in a few others, I'm back on Lollipop, Wi-Fi is working, and I've freed up probably half of my device's memory! But I need more!!!
Thank you.