Has anyone been able to do a clean ROM install on their phone and NOT have to factory reset their watch to get it to re-pair? It's not a huge deal, but it's kind of a pain, and I feel like hte pairing information should be able to be backed up and restored across a ROM install so the watch doesn't know the difference.
I hear ya brother i got to reset my watch to get it to connect after flashing new roms too. I've tried to connect without resetting but still haven't found a way
Related
After performing a factory reset prior to installing a 4.2 ROM and then flashing said ROM, I discovered that the Google backup saved my contacts and such, but not my wifi passwords. This occasionally happens while wiping and flashing new ROMs, and is usually fixed by re-wiping and re-flashing. Then, upon first boot everything loads perfectly.
Problem is, I'm starting to get tired of this and I'm wondering why it does this and if there's any easier way to circumvent this problem other than the one I just explained, which is getting really annoying, tbh. Any help would be gladly appreciated.
AdrianE46 said:
After performing a factory reset prior to installing a 4.2 ROM and then flashing said ROM, I discovered that the Google backup saved my contacts and such, but not my wifi passwords. This occasionally happens while wiping and flashing new ROMs, and is usually fixed by re-wiping and re-flashing. Then, upon first boot everything loads perfectly.
Problem is, I'm starting to get tired of this and I'm wondering why it does this and if there's any easier way to circumvent this problem other than the one I just explained, which is getting really annoying, tbh. Any help would be gladly appreciated.
Click to expand...
Click to collapse
Happened to me once as well. Next time, you could try removing and re-adding your Google account.
Tried this a few times and nothing happened. Any other ideas?
Sent from my Galaxy Nexus.
AdrianE46 said:
After performing a factory reset prior to installing a 4.2 ROM and then flashing said ROM, I discovered that the Google backup saved my contacts and such, but not my wifi passwords. This occasionally happens while wiping and flashing new ROMs, and is usually fixed by re-wiping and re-flashing. Then, upon first boot everything loads perfectly.
Problem is, I'm starting to get tired of this and I'm wondering why it does this and if there's any easier way to circumvent this problem other than the one I just explained, which is getting really annoying, tbh. Any help would be gladly appreciated.
Click to expand...
Click to collapse
What about using Titanium Backup to save the wifi info? That's what I do, since my Google account won't save the wi fi info either
Hello everybody,
I'm running the latest stock Android 4.3 on a rooted Note 2 with CWM installed. What happens is that when I use the phone to make or receive phone calls (streaming music is ok instead) in my car (but I experienced the same problem in another car) the Bluetooth all of a sudden goes off and I need to either turn the screen on or toggle the bluetooth button.
Any idea on how to fix it?
Thank you,
Davide
Hi! Have you tried a Factory Reset? It will wipe your phone clean, so back-up your stuff first. Come back after with the results, maybe this will fix the Bluetooth issue.
Ruwin said:
Hi! Have you tried a Factory Reset? It will wipe your phone clean, so back-up your stuff first. Come back after with the results, maybe this will fix the Bluetooth issue.
Click to expand...
Click to collapse
Actually I wanted to avoid that...
Okay, so let's try something else first and see where it leads: Go to CWM and make a Nand Backup. Then wipe your Cache and Dalvik Cache. Reboot and test. Most probably this will not solve, but it's worth trying. Get back in CWM and this time wipe Data + Dalvik + Cache (Factory Reset basically). Boot and test. If not working, you can restore the Nand Backup to get back your apps and data. If it is working, well, lucky you, you'll have a great time installing all your apps back
I went through from 4.1.1 to 4.1.2, no problems, phone ran fine after update. Then went to 4.3, same thing. The phone was running fine so I booted back into recovery and removed Knox as well as manually rerooted by flashing SuperSU. Rebooted after that and still no problems, phone was running great. I then make a backup so I have a restore point of stock 4.3, rooted, and without Knox. I then go on and try to flash Dandroid and get a status 7 error and the phone was acting up after I rebooted.
At this point I go back to my backup and simply restore it and reboot again. The phone boots up, so that's a good thing. The problem is the GApps will not run and it continuously has a pop-up notification. The phone is rendered unusable like this. I got lucky once and was able to try and launch ROM Manager to see if fixing permissions would work, but it also closed. I tried flashing a 4.3 GApps package with no success and even tried reflashing the 4.3 update but got a status 6 error.
I'm at a loss here, does anyone have any ideas on this?
Not sure if this will help much, but even when plugged in via USB my computer will not recognize the device. The S3 states that it is connected and it does show up in Device Manager, it just won't show up as any kind of readable memory.
Trying to ADB sideload a rooted stock 4.3 ROM now. Any advice at all would be a help.
EDIT: I took a video (https://www.youtube.com/watch?v=tJ-eaQ_9mVI) of the problem so everyone can see what I'm talking about and I also found a fix.
I'm not sure what was causing it, but after a solid day of researching it online the closest thing I got was resetting app preferences and also trying to clear any data of Google apps. This seemed to sometimes slow the popups down for me or create a longer gap before they just came right back in full force. So, going off that small success I had managed to navigate my way over to Settings -> Accounts -> Backup and reset -> Factory data reset and ran that. The first boot after that took a very long time, I'd say a solid twenty minutes but it did work. No more error and everything has been going smooth for me since. A restore of apps with Titanium Backup also did not bring the problem back up again, so the device seems to be good as new again.
I apologize if any of these is out of line, I just thought I would follow up with a solution in case anyone else has this problem and can't seem to fix it. Maybe this will help them.
Hey guys I'm loving the 360. Got a small problem. I'm a crack flasher on my Note 3. Is there any way to flash a ROM and re-pair my watch back to my phone without having to reset the watch and lose all my data?
I have tried using titanium backup and backing up Bluetooth pair setting and it didn't help. Thanks
yeah, I ran into the same issue. I had to reset the moto 360 inorder to get it up and running properly again.
I previously had a G watch and was in a similar situation. When updating from one nightly to the next (aka no data wipe) it'll be fine and just work. However, whenever you wipe data, you'll need to factory reset the watch. Luckily the only thing you'll really be losing is fitness data.
Hi All,
Having some issues with my Galaxy Note 10.1 which I've had for quite a while now. It's rooted but with Android 5.0 stock rom and a custom kernel.
Just now (like 20mins ago) I tried to enable Adblock plus app, the app said it can't automatically change the settings - even though SuperSU was installed and had no issues with it previously. So like all things thought I'd give it a reboot that ought to clear it out. That didn't work, so tried clearing cache (Dalvik/ART/Cache), Still no joy.
I'm a s/w engineer, but not and android/bootloader expert, so I've tried to grab the dmesg and boot logs which I've attached, I've got some stuff on the internal SD (app data) which I'd like to keep, hence I'm not going for the full wipe.
Please take a look at the logs and see if you can determine how to fix this issue, my initial thoughts were there are some issues with the flash storage (bad sectors/partition table?), if I could grab the image and dd the image again I'd be OK - but I don't know much about about android boot loader/kernel etc so can't say.
Ok it has been fixed by wiping data - but I've lost my data and installed apps!
Is there anyway to find out which file/app is causing the boot loop so I can restore data, delete the offending file?
Well, I shall give a bump to this topic, with a little more info. Though probably not really useful.
First I had stock 5.1.1 deodex pre root etc ROM that, after I tried to insert a nano sim card (mine is a 601 3G model) that got stuck, it entered on a bootloop, I had to open it, take the sim card out, and it was still on a boot loop. Tried to install another image, still bootloop, tried to reinstall the original one I had, still bootloop, wiped data, worked fine.
Then almost 2 weeks later, everything worked fine, went to watch a video, the sound was mute, tried to turn it on but everything looked fine, decided to restart because it would probably fix the problem. Got a bootloop. Wiped the data, everything was fine again.
Now, a little more than 2 weeks later, seems like the wifi is not working, thought all my other devices are, guess it's the same problem, decided to restart it, and bootloop again. I'm currently trying to update my TWRP, and gonna try a different ROM, and wait to see if something like that happens, until then, I wonder what could be happening... I remembered an Asus Device that I had that had different firmware versions for 4.4 and 4.1, so if I tried to flash a 4.4 on a 4.1 firmware it wouldn't work, and for downgrade, the same problem happened, and wondered if Samsung has some difference between versions 4 and 5.
ssj4maiko Let me know if you find a more stable rom - I went back to pretty much stock, but with root as I wanted to use all the Samsung apps, but this constant random bootloops are annoying!