Database Info

[Q] Home hardkey not working after OTA update

I do not want to restore if possible. I did OTA update to my wife's stock rooted phone last night and now the home key does not work. Back key is only way to home screen. It vibrates when pressed but no action. She is already pissed about her tethering being disabled again. Any suggestions appreciated. I really don't want to have to tell her I have to restore. She didn't want the update in the first place.

Sounds to me like a fxz flash is the best option.
Flash back to 2.3.5 and root.
Flash one of our handy ROM'S that are currently available.
Get your teathering via sqlite.
Then your set!
Sent from my MB865 using xda premium

Thanks. I already had her talked into it. Think I figured out possible problem. I remember she uninstalled ONE of the original at&t apps. Update said completed but I think may have corrupted something. She had a lot of FC today, definitely major issue. Back to stock we go!

Hmm. I don't think it should have ever updated over the air with some of the att bloatware missing.
Atleast it didn't for me.
Well, it sounds like your on your way!
Sent from my MB865 using xda premium

If you haven't flashed yet, you can boot into Recovery from the Atrix 2 Bootstrap and make a Nandroid backup, then after you flash to stock and update to 2.3.6 and root you can "Advanced Restore" the "data" part of the backup to keep your apps and settings.

How to remove the update notification?

Since my phone is rooted, the OTA update notification is on my phone. The first time it came, I tried to perform the update not knowing it would fail since it won't work on rooted phones.
It's not worth the hassle to me to 1: return the phone to stock, perform the update, and re-root the phone, or even not re-root the phone, or 2: load the rooted updated here.
I just want the OTA update to go away, keeping the phone like it is for now.
The notification is persistent through a restart, and I don't see a way to clear it. It's been like this for a few days now.
Any ideas?
Thanks.

In the same boat, would love to know if there's a way to get rid of this daily annoyance.

Go to the Android store and download NoBloat free(it has a Android holding an AK)...then go to system apps and look for the update notifier which is syncmldm2.apk, select it, then choose disable only...and viola! Its gone!
Sent from my SGH-T769 using xda premium

You could also freeze Device Management 2.0 with Titanium Backup.
Sent from my SGH-T769 using xda premium

lbingham said:
You could also freeze Device Management 2.0 with Titanium Backup.
Sent from my SGH-T769 using xda premium
Click to expand...
Click to collapse
I'm probably missing it, but I don't see Device Management 2.0 in the list, even if I filter all by name.
Do you mean Download manager 2.3.6?

Are you on stock and rooted? I was able to install the update on stock and rooted from kies. I did have to reroot and uninstall bloat ware again but everything else stayed in tact.
Sent from my SGH-T769 using xda app-developers app

jmoak said:
Are you on stock and rooted? I was able to install the update on stock and rooted from kies. I did have to reroot and uninstall bloat ware again but everything else stayed in tact.
Sent from my SGH-T769 using xda app-developers app
Click to expand...
Click to collapse
Yeah, stock rooted. Obviously I'm lazy with this, but I don't want to mess with Kies either. I'd have to a: reload it, install kies, get it working, load the update, re-root the phone, and *THEN* reconfigure/reinstall all my apps and settings.
Sorry, but I just want the notification icon to go away!
The first app that was mentioned, doesn't work either, nothing is listed as was described. There was one or two things similar, but not the same.

syncmldm2.apk is listed under Titanium as "Software update v3.1201.4.2". If removing that doesn't get rid of the notification, I believe wssyncmlnps.apk is also related to software updates. Remember to "nand you shizz" and titanium backup before removing either as it may cause instability (although it may not). I believe I removed the wssyncmlnps.apk or something similar on my Exhibit with little consequence- probably since they never intended on updating that thing...

I had that icon, I tried to install the update a few times (failed due to root) after a few failed attempts the icon gave up and went away.
Sent from my SGH-T769 using xda app-developers app

Cirkustanz said:
Yeah, stock rooted. Obviously I'm lazy with this, but I don't want to mess with Kies either. I'd have to a: reload it, install kies, get it working, load the update, re-root the phone, and *THEN* reconfigure/reinstall all my apps and settings.
Sorry, but I just want the notification icon to go away!
The first app that was mentioned, doesn't work either, nothing is listed as was described. There was one or two things similar, but not the same.
Click to expand...
Click to collapse
All of my apps and settings stayed intact after the update over kies. I just had to reroot and uninstall the bloatware again.

The only way for you to get rid of the notification would be to update via Kies Software. Doesn't work via OTA when you are rooted, regardless if you're running the stock firmware. I just updated the firmware now with Kies, but oddly enough, the notification was still there! I clicked it and updated OTA, and it worked because the phone lost root upon the update via Kies. So yes, I had to update my device twice..
Well, time to re-root and uninstall bloatware.
EDIT: Well, upon restarting device, I am experiencing a lot of force closing issues. I reinstalled ClockworkMod Recovery and tried fixing permissions, but that didn't seem to work. Anyone have any ideas or fixes? Maybe I should reinstall my apps again.. >_>

Most likely you will need to wipe your phone and start fresh.

rbeier1221 said:
Most likely you will need to wipe your phone and start fresh.
Click to expand...
Click to collapse
Seems like it, thanks for input.. I'm going to backup my apk's and data, and everything using MyBackup Pro, so I can speed up the whole process. Hopefully everything turns out good. Oh, one question, when upgrading to official stock ROM releases, you always have to wipe if your rooted?? If so, I never knew that..
EDIT: omg backup app not working! Help! I refuse to wipe if I can't backup my apps!
Sent from my SGH-T769 using xda-developers app

I wouldn't think so, but there is always the chance an app incompatibly with an upgrade can occur and muck it all up.
Have you tried using Titanium?

Ah, I see.
Titanium seems very popular.. I've never used it before. I guess I'll try it. If all else fails, I do have a Nandroid from yesterday.
EDIT: okay, everything is restored and back to normal. Thanks.
Sent from my SGH-T769 using xda-developers app

Mine went away today, without doing anything.
If only real problems would go away if you ignored them long enough.

[Q] Jelly Bean Flash gone wrong

My phone got stuck in what appeared to be recovery mode while trying to flash Jelly Bean using this guide:
http://www.android.gs/update-verizon-galaxy-s3-to-vralg7-ics-update-rooted-and-deodexed-firmware/
The phone seemed to flash took about 8 minutes then just went blank. Nothing. After about 10 minutes of waiting still nothing. I finally tried to get it to respond by hitting up/down/power and home buttons and still nothing. I then pulled the battery figuring I had bricked it anyway. After pulling the battery I restarted the phone and it came on but in a stock configeration. Not bricked but lost my root and cannot seem to get the phone to restore from Titanium Pro back up (not rooted any more). Any help getting things back the way they were would be appreciated.

drzcharlie said:
My phone got stuck in what appeared to be recovery mode while trying to flash Jelly Bean using this guide:
http://www.android.gs/update-verizon-galaxy-s3-to-vralg7-ics-update-rooted-and-deodexed-firmware/
The phone seemed to flash took about 8 minutes then just went blank. Nothing. After about 10 minutes of waiting still nothing. I finally tried to get it to respond by hitting up/down/power and home buttons and still nothing. I then pulled the battery figuring I had bricked it anyway. After pulling the battery I restarted the phone and it came on but in a stock configeration. Not bricked but lost my root and cannot seem to get the phone to restore from Titanium Pro back up (not rooted any more). Any help getting things back the way they were would be appreciated.
Click to expand...
Click to collapse
Section 5 of my guide...use the prerooted jellybean version. This will wipe your internal so back up what you dont want to lose.

By the way what you linked is for an ICS update not the jb leaks. Listen to droid style. I woke audio recommend getting your files, etc from here in XDA or rootz wiki. I see a lot of problems of people following these random guides online.
Sent from my SGS3 running Eclipse 2.1

kintwofan said:
By the way what you linked is for an ICS update not the jb leaks. Listen to droid style. I woke audio recommend getting your files, etc from here in XDA or rootz wiki. I see a lot of problems of people following these random guides online.
Sent from my SGS3 running Eclipse 2.1
Click to expand...
Click to collapse
I've noticed this as well. It seems every week or two someone is having major issues and they stem from using these rooting guides from sites I've never heard of.
Sent from my SCH-I535 using xda app-developers app

droidstyle said:
Section 5 of my guide...use the prerooted jellybean version. This will wipe your internal so back up what you dont want to lose.
Click to expand...
Click to collapse
After this happened I read more, a lot more about rooting and decided I wasn't rooted now.
Trying to root again produces an (amb?) error which I can't get past.

drzcharlie said:
After this happened I read more, a lot more about rooting and decided I wasn't rooted now.
Trying to root again produces an (amb?) error which I can't get past.
Click to expand...
Click to collapse
Do you have a super su app n the phone because what you linked is supposed to be pre rooted
Sent from my SGS3 running Eclipse 2.1

No Super SU, though I had it previously. I've checked in my applications list and it's not there.

[Q] Help with recovery after failed ROM installation

So after 6 months of perfectly working NON rooted phone, I decided to root my Verizon Galaxy S3. I previously owned a Moto Droid 2 and rooted and had no problems ever. Unfortunately, within hours of a successful root, I made the mistake of downloading ROM manager (since it worked fine on my Droid 2) and tried installing the first listed AOKP custom ROM. It rebooted and did everything that was expected, until it just hung on the boot up screen for over an hour. I then decided to (for better or worse) pull the battery and just boot into recovery. Unfortunately, this brought me to a message from Verizon saying "you are doing bad things, bring your phone to Verizon" (more or less anyway). So I fixed that much by getting the factory image/reboot and installing via Odin. My problem now is it constantly keeps failing/closing android process every minute or so. I can't navigate it long enough to do anything before it fails again and takes me back to lock screen followed by home screen. When I boot to recovery, it says I have no files to restore either, but I KNOWWW for a fact I did a backup through CWM before I did ANYTHING involving any custom ROMs. PLEASE help me! Ask any and all related questions that will help you and I'll do my best to answer them.

Can you check your file system and see if your CWM folder has a backup? It should be Sdcard/CWM or extsdcard/CWM. If not, do you mind flashing another rom or that same rom?
Sent from my SCH-I535 using xda app-developers app

JoeS8705 said:
So after 6 months of perfectly working NON rooted phone, I decided to root my Verizon Galaxy S3. I previously owned a Moto Droid 2 and rooted and had no problems ever. Unfortunately, within hours of a successful root, I made the mistake of downloading ROM manager (since it worked fine on my Droid 2) and tried installing the first listed AOKP custom ROM. It rebooted and did everything that was expected, until it just hung on the boot up screen for over an hour. I then decided to (for better or worse) pull the battery and just boot into recovery. Unfortunately, this brought me to a message from Verizon saying "you are doing bad things, bring your phone to Verizon" (more or less anyway). So I fixed that much by getting the factory image/reboot and installing via Odin. My problem now is it constantly keeps failing/closing android process every minute or so. I can't navigate it long enough to do anything before it fails again and takes me back to lock screen followed by home screen. When I boot to recovery, it says I have no files to restore either, but I KNOWWW for a fact I did a backup through CWM before I did ANYTHING involving any custom ROMs. PLEASE help me! Ask any and all related questions that will help you and I'll do my best to answer them.
Click to expand...
Click to collapse
2 questions: Which factory image did you use to restore (link to thread)? Did you change the default backup location in CWM (ie, did you backup to the external sd or the internal - internal is default)?

There is a file in both extsdcard and sdcard with clock work mod back up. I did manage to factory reset and re root, so phone is functional again, just with none of my apps or settings. I have a feeling I'm going to need to un root in order to re receive my JB update too?
Sent from my SCH-I535 using xda app-developers app

Didn't unlock bootloader?

I don't know for sure. I unzipped SU plus bootloader file exactly as specified in forums/video. Had no problems until I tried installing that ROM through ROM manager. And forgive me for trying that. I hadn't rooted in over a year. But main problem now is just that I want to recover how my phone was ie settings and set up if possible.
Sent from my SCH-I535 using xda app-developers app

JoeS8705 said:
There is a file in both extsdcard and sdcard with clock work mod back up. I did manage to factory reset and re root, so phone is functional again, just with none of my apps or settings. I have a feeling I'm going to need to un root in order to re receive my JB update too?
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
How big are those 2 folders?

One is 4.82 gb...so I'd think there has to be a file in there.
Sent from my SCH-I535 using xda app-developers app

JoeS8705 said:
One is 4.82 gb...so I'd think there has to be a file in there.
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
That sounds about the right size for a backup. When you go into CWM and do the restore (or restore from external - which ever has that folder, you didn't say) it doesn't show a backup?
What version of CWM are you running?

It's version CWM6023touchvzw.tar.md5. And it's on the external. But no matter which option of restore I choose in the recovery boot, it says file not found.
Sent from my SCH-I535 using xda app-developers app

JoeS8705 said:
It's version CWM6023touchvzw.tar.md5. And it's on the external. But no matter which option of restore I choose in the recovery boot, it says file not found.
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
Maybe after all that flashing and Odin-ing your recovery install got wanked, somehow.
Let's try this: it will re-install the latest CWM, clean and then let's see if it'll recognize your backups.
http://www.clockworkmod.com/rommanager/
download the touch image for the d2vzw (or just click here)
put that in the root of your internal sd card.
Open up terminal emulator on your phone and type the following:
Code:
su
dd if=/sdcard/recovery-clockwork-touch-6.0.2.3-d2vzw.img of=/dev/block/mmcblk0p18
reboot recovery
(partition 18 is your recovery partition)
That'll push the known good CWM to your recovery partition and boot you into it. It won't mess with any sort of data anywhere else on the phone.

Alright, thanks. I'll give this a try after I get back home from work.
Sent from my SCH-I535 using xda app-developers app

recovery
JoeS8705 said:
So after 6 months of perfectly working NON rooted phone, I decided to root my Verizon Galaxy S3. I previously owned a Moto Droid 2 and rooted and had no problems ever. Unfortunately, within hours of a successful root, I made the mistake of downloading ROM manager (since it worked fine on my Droid 2) and tried installing the first listed AOKP custom ROM. It rebooted and did everything that was expected, until it just hung on the boot up screen for over an hour. I then decided to (for better or worse) pull the battery and just boot into recovery. Unfortunately, this brought me to a message from Verizon saying "you are doing bad things, bring your phone to Verizon" (more or less anyway). So I fixed that much by getting the factory image/reboot and installing via Odin. My problem now is it constantly keeps failing/closing android process every minute or so. I can't navigate it long enough to do anything before it fails again and takes me back to lock screen followed by home screen. When I boot to recovery, it says I have no files to restore either, but I KNOWWW for a fact I did a backup through CWM before I did ANYTHING involving any custom ROMs. PLEASE help me! Ask any and all related questions that will help you and I'll do my best to answer them.
Click to expand...
Click to collapse
COuld you possibly link the file you used to get back to stock? i resently tried to root my device and it won't start.

No problem. Once again, I'm at work. I'll post it when I get home though.
Sent from my SCH-I535 using xda app-developers app

[Q] 4.2 to 4.3 Saving App Data

I have a possibly simple yes or no question in the case there is no alternative. So, I am currently running 4.2.2 PAC-Man Rom and I want to update to the 4.3 version of it. Technically, speaking, I have no issues in updating the ROM itself. The problem is when I try to keep my app data moving from 4.2.2 to 4.3. Whenever I try to restore data via Titanium Backup, the phone will allow it, but upon the next shutdown, will not boot again. Likewise, I have also tried to flash 4.3 and then do an advanced restore via CWM and only restore data. This has the same results as the previous option in that I can boot the phone, but if I shut it off, it won't restart. Basically, I can keep and install the original app apks, but the moment I try to restore any form of app data from the previous iteration of the ROM, my phone will refuse to restart. This predicament is met on any 4.3 ROM I have tried. I have never had this problem before, as I have been able to move from 4.1.2 to 4.2.1 to 4.2.2 (I suppose 4.3 is different?). This brings me to my question, is it possible to keep app data moving from 4.2 to 4.3? I fear I already know the answer. In any case, thank you for your time.
Tl;DR
When moving to 4.3, restoring app data from previous rom (PAC-man 4.2.2) causes the phone to lose the inability to boot. Is there any way to keep app data, or is it a lost cause? Thank you for your time.

One thing that comes to mind is are you restoring any system data? That causes problems.
Other than that I would download and install all my apps through the app store and reboot.
Then make a restore image to fall back on so you don't have to repeat these steps.
Now start restoring you app data SELECTIVELY. And restore app data ONLY. And do it one by one and reboot. This is the only way I know that can pin point the problem or the one restore data piece causing you problem.
Identifying it is the hardest part, any better ideas are welcomed.
Once identified just avoid that one app as your migration casualty.
Good luck,
Sent from my SAMSUNG-SGH-I727 using xda app-developers app

verissimus said:
I have a possibly simple yes or no question in the case there is no alternative. So, I am currently running 4.2.2 PAC-Man Rom and I want to update to the 4.3 version of it. Technically, speaking, I have no issues in updating the ROM itself. The problem is when I try to keep my app data moving from 4.2.2 to 4.3. Whenever I try to restore data via Titanium Backup, the phone will allow it, but upon the next shutdown, will not boot again. Likewise, I have also tried to flash 4.3 and then do an advanced restore via CWM and only restore data. This has the same results as the previous option in that I can boot the phone, but if I shut it off, it won't restart. Basically, I can keep and install the original app apks, but the moment I try to restore any form of app data from the previous iteration of the ROM, my phone will refuse to restart. This predicament is met on any 4.3 ROM I have tried. I have never had this problem before, as I have been able to move from 4.1.2 to 4.2.1 to 4.2.2 (I suppose 4.3 is different?). This brings me to my question, is it possible to keep app data moving from 4.2 to 4.3? I fear I already know the answer. In any case, thank you for your time.
Tl;DR
When moving to 4.3, restoring app data from previous rom (PAC-man 4.2.2) causes the phone to lose the inability to boot. Is there any way to keep app data, or is it a lost cause? Thank you for your time.
Click to expand...
Click to collapse
What recovery are you using? If it's not TWRP 2.6.0.3 or newer, or the custom CWM provided by Team Chopsticks, you will continue to have this problem. Also, it has absolutely nothing to do with restoring data.

Fixed XD
Okay, so I have been doing nandroid backups the whole time, so I haven't really lost anything. I did try to install apps using Google Play and it would cause the same problem that restoring data only via cwm would. That said, I got bored and just left the phone boot looping and slept for 5 hours. Interestingly enough, upon checking on it later, it had in fact booted and it did function. Naturally, I reverted back to 4.2 and tried to upgrade again, this time timing it. Over all, it took about 1 hour for the phone to stop bootlooping and actually boot up. I don't really know what is wrong, but hey, it works. Nevertheless, I would like to thank you guys for your input. Sorry that my problem wasn't actually what I thought it was. :/ Good day.

verissimus said:
Okay, so I have been doing nandroid backups the whole time, so I haven't really lost anything. I did try to install apps using Google Play and it would cause the same problem that restoring data only via cwm would. That said, I got bored and just left the phone boot looping and slept for 5 hours. Interestingly enough, upon checking on it later, it had in fact booted and it did function. Naturally, I reverted back to 4.2 and tried to upgrade again, this time timing it. Over all, it took about 1 hour for the phone to stop bootlooping and actually boot up. I don't really know what is wrong, but hey, it works. Nevertheless, I would like to thank you guys for your input. Sorry that my problem wasn't actually what I thought it was. :/ Good day.
Click to expand...
Click to collapse
This is due to the recovery version you are on as the guy before your last post indicated. It has nothing to do with your restoration of data, but rather the recovery used to flash the rom and the way it's handling the partitions.
Long story short, update your recovery to one of the ones indicated two posts above mine and you should be good to go.
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2

bps119 said:
This is due to the recovery version you are on as the guy before your last post indicated. It has nothing to do with your restoration of data, but rather the recovery used to flash the rom and the way it's handling the partitions.
Long story short, update your recovery to one of the ones indicated two posts above mine and you should be good to go.
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
Click to expand...
Click to collapse
Ah, okay, that makes a great deal of sense. Thank you for elucidating, I shall do just that.