Database Info

Regarding Verizon Update.

Disable Sdm 1.0 in Titanium Backup. That should stop your phone from trying to update.

I'd imagine synergy has all this disabled right?
Sent from my SCH-I535 using XDA Premium App

Lord Alekosh said:
Disable Sdm 1.0 in Titanium Backup. That should stop your phone from trying to update.
Click to expand...
Click to collapse
If you just flash a custom recovery you don't have to worry about the update. CWM doesn't allow OTAs to be installed.

can't get a ota on beans rom anyways. all im interested in is the new radios.

Of course, I just imagine there are some people rooted with the stock rom and recovery

thanks so much for this!
tired of searching through 50 replies in other threads of people panicking, when this is the ONLY info i needed to know.
:good::good::good:

Got the update notice last night and it apparently tried to flash the update. Running No Sympathy rom, rooted (of course), bootloader unlocked, TWRP recovery.
Woke up to the TWRP recovery screen. Choose Reboot, System. then after rebooting, there was a pop-up window saying the update failed. Just waiting for the developers to properly incorporate the good stuff from this update.

[Q] how to prevent system update - P3113

Does anyone know how to prevent a software update on a rooted Samsung Galaxy Tab 2 7.0? *
My tablet auto updated to the new Jelly Bean about 3 wks ago and I hated it. *I have since restored my wonderful tablet back to the ICS 4.0 it came with and rooted it. *But 2 days ago it auto downloaded the software update again and will only allow me to postpone the update rather than completely refuse it.
I do not want to have to go through the whole process again. *Does anyone know how I can prevent the update from happening? *TY!

Freeze updater.apk with titanium backup.
Posted from my Fascinate using XDA Premium

Big thank you!
MultipleMonomials said:
Freeze updater.apk with titanium backup.
Posted from my Fascinate using XDA Premium
Click to expand...
Click to collapse
Hooray - it seems to have worked! I wasn't able to find the specific file name you mentioned, but I did freeze 2 "system update" files and that has removed the update notification from my notify list and also doesn't open the update postponed window any longer from the about/software update settings either. Thank you so much, MultipleMonomials, ty, ty!

Still having problems...
Well, it seems I spoke too soon regarding my last post. All seemed to work well after freezing two "system update" files using ROM Toolbox Pro. However, after shutting my tablet down that night and turning it back on in the morning, I have since been locked up at the Samsung logo screen. I've spent the past few days trying to research my options, did the fix permissions, reset to factory default, tried restoring backups (which I didn't have), all that stuff, and I am having no luck whatsoever.
I can boot into CWM6 Recovery mode and also boot into download mode, but otherwise, I cannot get it to load past the Samsung logo and I'm officially stumped now.
Can anyone offer some suggestions as to what I should try next?

Flash a stock-based ROM without wiping data. Make a backup first.
Posted from my Fascinate using XDA Premium

It worked...
MultipleMonomials said:
Flash a stock-based ROM without wiping data. Make a backup first.
Posted from my Fascinate using XDA Premium
Click to expand...
Click to collapse
I'm back up and running and with the ICS that I wanted. I'm one happy camper! :victory:

[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] Getting bsod after reboot on Liquid Smooth

Hi. I recently installed Liquid Smooth (Unofficial) 4.3 onto my Skyrocket. Since install, if I reboot the phone it will get the ever dreaded Black Screen Of Death. The only way I've found to fix this is to clear the data partition in my recovery (TWRP updated to most recent version) and then reflash the ROM and the gapps. Any ideas on how to keep the BSOD from happening again? I've tried everything I can think of. I tried just wiping the dalvek, cache and system and then flashing the ROM again. As I said, the only way I can find to "fix" it is to wipe the data partition and then flash the ROM and gapps again. I would have asked in that specific thread, but since I am a new member I can't until I reach the 10 post requirement.

CoolWolf22 said:
Hi. I recently installed Liquid Smooth (Unofficial) 4.3 onto my Skyrocket. Since install, if I reboot the phone it will get the ever dreaded Black Screen Of Death. The only way I've found to fix this is to clear the data partition in my recovery (TWRP updated to most recent version) and then reflash the ROM and the gapps. Any ideas on how to keep the BSOD from happening again? I've tried everything I can think of. I tried just wiping the dalvek, cache and system and then flashing the ROM again. As I said, the only way I can find to "fix" it is to wipe the data partition and then flash the ROM and gapps again. I would have asked in that specific thread, but since I am a new member I can't until I reach the 10 post requirement.
Click to expand...
Click to collapse
Try using the latest CWM recovery. Some people are reporting having better luck using this for the BSOD issue.
Sent from my SAMSUNG-SGH-I727 using xda app-developers app

jondroid2 said:
Try using the latest CWM recovery. Some people are reporting having better luck using this for the BSOD issue.
Sent from my SAMSUNG-SGH-I727 using xda app-developers app
Click to expand...
Click to collapse
I will try this and will get back to you. I'd still like to know what's causing the issue in the first place. I've been flashing on Samsung devices since the original Epic 4G launched. Never have had any issues like this before.

CoolWolf22 said:
I will try this and will get back to you. I'd still like to know what's causing the issue in the first place. I've been flashing on Samsung devices since the original Epic 4G launched. Never have had any issues like this before.
Click to expand...
Click to collapse
I've had the same issue and switching to cwm solved it. It's a real pita though as a prefer twrp and my nandroids are twrp. I switch back and forth between them.

jd1639 said:
I've had the same issue and switching to cwm solved it. It's a real pita though as a prefer twrp and my nandroids are twrp. I switch back and forth between them.
Click to expand...
Click to collapse
CWM fixed my BSOD. I've had 2 successful reboots so far. I too preferred TWRP over CWM. But oh well. I am in contact with the devs for TWRP to see if they are aware of the issue and can issue a fix for it.

CoolWolf22 said:
CWM fixed my BSOD. I've had 2 successful reboots so far. I too preferred TWRP over CWM. But oh well. I am in contact with the devs for TWRP to see if they are aware of the issue and can issue a fix for it.
Click to expand...
Click to collapse
There's an build of TWRP 2.7 that I've been using and haven't had any issues with. The only thing "wrong" with it is it only reads internal storage. Here's the Link

theesotericone said:
There's an build of TWRP 2.7 that I've been using and haven't had any issues with. The only thing "wrong" with it is it only reads internal storage. Here's the Link
Click to expand...
Click to collapse
Thanks. I'll download that and keep it in reserve for future reference.

[Q] System Update fails installation and keeps returning

Hey guys,
Hoping someone here might be able to help me get rid of the bane of my existence right now. I've been reading all over and using various methods other people seem to have had success with but nothing is working for me.
I have a Samsung Galaxy Victory 4G from Virgin Mobile. I'm also responsible for 2 others that are having the same issue.
A while back I had rooted all our devices and put TWRP on them but have total stock rom.
A few weeks ago we all started getting this system update prompt that lets you install now or later. If we tried to install it with TWRP it just boots into TWRP. So I put the stock recovery back on and took the prompt and let it reboot. It begins installing but halfway through I get a red yield sign and it stops and reboots the phone. If we go this route the prompt usually doesn't show up again for days.
So I went and tried custom recovery and custom rom next. Didn't get the update on the custom rom until the next morning when I woke up. Went and got a perfect custom recovery/rom package for the phone and went total stock. Same issue as before where it gets halfway through and fails.
I've tried navigating to the root/cache folder as another thread suggested and renaming the update stored there but the update has never shown up in that directory.
Basically now, periodically this prompt continues to pop up, sometimes very frequently on the foreground of whatever you're doing on the phone and constantly reminds/annoys the hell out of us.
I'd take a screenshot but it hasn't reappeared in 2 days since I last took the update and it failed.
Appreciate any help from anyone!

Your phone needs to be stock for the update to work. No custom recovery, no root, no ROM. Flash back the official stock firmware and the update should work.
Sent from my LG-VS980 using XDA Premium 4 mobile app

bweN diorD said:
Your phone needs to be stock for the update to work. No custom recovery, no root, no ROM. Flash back the official stock firmware and the update should work.
Sent from my LG-VS980 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I had not thought to try going stock with no root. That is the only thing I haven't tried. Will report back. Thank you