Database Users

Stuck on Samsung Custom Screen w/ Custom ROM

Hey,
So I flashed a custom rom on my AT&T Galaxy S IV. Everything seems to be working fine.
Until, I hold on my power menu than click on Reboot my phone. When I do that, my phone shuts down and reboots but it's always stuck in the Samsung Custom Screen. The max I have waited is 30 minutes for it to work. But it never does.
I'm running TWRP Recovery Mode.
I tried every roms in the AT&T Section. All of them seems to have that problem. I also used ktoonsez kernel. Nothing at all.
With stock AT&T rom everything seems to be fine.
I was wondering if it's happening to you guys as well. If you can try, please hold into your power button and reboot your phone clicking on reboot.
Thank you!

I have that happen sometimes, but if I go into recovery when that happens and fix permissions it boots up fine after.
Sent from my SGH-I337 using Tapatalk 4 Beta

Flash a different kernel.
Period
your welcome

TehZam said:
Hey,
So I flashed a custom rom on my AT&T Galaxy S IV. Everything seems to be working fine.
Until, I hold on my power menu than click on Reboot my phone. When I do that, my phone shuts down and reboots but it's always stuck in the Samsung Custom Screen. The max I have waited is 30 minutes for it to work. But it never does.
I'm running TWRP Recovery Mode.
I tried every roms in the AT&T Section. All of them seems to have that problem. I also used ktoonsez kernel. Nothing at all.
With stock AT&T rom everything seems to be fine.
I was wondering if it's happening to you guys as well. If you can try, please hold into your power button and reboot your phone clicking on reboot.
Thank you!
Click to expand...
Click to collapse
make sure you flashed the correct ktoonsez kernal..one for aosp, one for touchwiz

And flash Loki Doki patch if required, although you'd probably get the 'software not compatible' error if Loki was missing.

KonoeKyon said:
I have that happen sometimes, but if I go into recovery when that happens and fix permissions it boots up fine after.
Sent from my SGH-I337 using Tapatalk 4 Beta
Click to expand...
Click to collapse
I'll try and post back to you!
TheAxman said:
Flash a different kernel.
Period
your welcome
Click to expand...
Click to collapse
If you don't mind me asking, what kernel are you using?
mixlex said:
make sure you flashed the correct ktoonsez kernal..one for aosp, one for touchwiz
Click to expand...
Click to collapse
I have used the Touchwiz kernal.
blyndfyre said:
And flash Loki Doki patch if required, although you'd probably get the 'software not compatible' error if Loki was missing.
Click to expand...
Click to collapse
Tried that and done that, no go.
________________________________________
Thank you everybody for the help.

what procedures are you using for all of this? is there a specific guide you are following?

xBeerdroiDx said:
what procedures are you using for all of this? is there a specific guide you are following?
Click to expand...
Click to collapse
So at first I used this [ROOT] Root Samsung Galaxy S4 with Motochopper. Same problem.
Went back to stock and used this
[ROOT[RECOVERY] Loki + TWRP + Motochopper CASUAL-R527b release:27May13. Same problem encountered.
Went back to stock and did it again using Same problem with this one as well.
It happens with every custom rom besides the stock rom and Cyanogenmod Rom. I can't even reboot to do anything .
Thanks for the help guys, I greatly appreciate it.

There is something else happening, does this happen on a backup you may have?
You do have a backup correct? It is rule #1

TheAxman said:
There is something else happening, does this happen on a backup you may have?
You do have a backup correct? It is rule #1
Click to expand...
Click to collapse
Yes, I do have a backup. It happens to every custom ROM that I have encountered with.
Stock & Cyanogenmod roms work fine when rebooting.
Would you mind sharing what kernel you are using? I jused used faux kernel. Same thing.

i meant more like what procedures are you using when you wipe and flash? your issue is not related to root method or a particular custom recovery.

xBeerdroiDx said:
i meant more like what procedures are you using when you wipe and flash? your issue is not related to root method or a particular custom recovery.
Click to expand...
Click to collapse
Sorry for the confusion, I used your guide!

I have the solution.
I can bet that when you wiped your phone you didnt just factory reset on twrp you WIPED the whole partition.
So when TWRP made another one it messed up thats why it doesnt work after a reboot.
I am 1000000% sure of this.
So go back to stock then factory reset through STOCK recovery and then install rom and factory reset click the icon on the left not the one on the right that makes you type 'yes'
TWRP doesnt format the partition correctly for our phones.
and the fact that the bootloader is still locked messes things up.

I am 1000000% sure of this.
are you really sure?
j/k, perfect.

TheAxman said:
I am 1000000% sure of this.
are you really sure?
j/k, perfect.
Click to expand...
Click to collapse
yep I am that sure haha.

jetlitheone said:
I have the solution.
I can bet that when you wiped your phone you didnt just factory reset on twrp you WIPED the whole partition.
So when TWRP made another one it messed up thats why it doesnt work after a reboot.
I am 1000000% sure of this.
So go back to stock then factory reset through STOCK recovery and then install rom and factory reset click the icon on the left not the one on the right that makes you type 'yes'
TWRP doesnt format the partition correctly for our phones.
and the fact that the bootloader is still locked messes things up.
Click to expand...
Click to collapse
Your method worked! Thank you very much, I greatly appreciate it.

Got rooted, installed custom recovery, lost root, now i'm confused...

So I used the Auto CF root and all went well. Next, I went back into recovery and installed the TWRP Recovery though odin. It installed fine. After that I noticed I no longer had root and I can't figure out how to get it back. Supersu was still installed, it just wouldn't work.
At this point, i've tried redoing the root process a couple of times and it says that it worked fine, but doesn't do the job. Anyone got any ideas on what to do?
If anyone's curious, I started on totally stock OTA MF9.
Thanks

Just flash one of the stock rooted mf9 ROMs in the development thread pic one with no data wipe so you don't have to set everything up again.
SGS4 Sent

ifly4vamerica said:
Just flash one of the stock rooted mf9 ROMs in the development thread pic one with no data wipe so you don't have to set everything up again.
SGS4 Sent
Click to expand...
Click to collapse
Thanks for the tip. Downloading the odexed version of this. Slow download so almost 2 hrs left.
[ROM][ZIP]Stock Rooted Deodexed/Odexed MF9 with SuperSU/Busybox 1.20.2
Hopefully it works. I tried wiping cache and dlvik cache and now when i turn the phone on it just keeps giving errors that this and that app can't open so the phone is essentially unusable. Didn't think wiping cache would do that.

Yeah sometimes things just go screwy. Have you tried fixing permissions? While you wait for a download you can wipe cache davlik and fix permissions its in the advanced menu of twrp. The odexed with no data wipe should fix you up I would recommend wiping cache davlik and system before you flash it. If it still gives errors you may have to wipe the data also and start fresh. You can also try TWRP version 5.0.2 if you aren't on it there is a flashable in the dev forum also. Some people have reported issues with the newer version. I think you will be fine flashing that stock odexed ROM though.
SGS4 Sent

Out of curiosity, would there be any danger in installing a custom rom while my phone is in this state? Downloading Blu Kuban Rom and it's going to finish much earlier than the stock rom. I know I would lose all my apps and need to reinstall those.

iivisionii said:
Out of curiosity, would there be any danger in installing a custom rom while my phone is in this state? Downloading Blu Kuban Rom and it's going to finish much earlier than the stock rom. I know I would lose all my apps and need to reinstall those.
Click to expand...
Click to collapse
Nope no danger at all. In fact I recommend blu Kuban. Its a nice ROM. Just do a full wipe of system data cache davlik and preload before flashing to avoid issues. All the custom ROMs have root built into them so you should be good to go.
SGS4 Sent

ifly4vamerica said:
Nope no danger at all. In fact I recommend blu Kuban. Its a nice ROM. Just do a full wipe of system data cache davlik and preloaded.
SGS4 Sent
Click to expand...
Click to collapse
Thanks. I'll have an update soon. Either that or a panic attack and a question in roughly 30-45 minutes.

Did you try to install super SU from the market. Maybe super user is acting up on you.
Sent from my SPH-L720 using Tapatalk 4 Beta

daniel4653 said:
Did you try to install super SU from the market. Maybe super user is acting up on you.
Sent from my SPH-L720 using Tapatalk 4 Beta
Click to expand...
Click to collapse
I tried installing supersu from the market. Next I even tried downloading it to my phone and loading the zip in recovery. No go both ways. I hoped wiping cache and delvick cache would help, but instead the phone is pretty much unusable now. It's really weird.

iivisionii said:
I tried installing supersu from the market. Next I even tried downloading it to my phone and loading the zip in recovery. No go both ways. I hoped wiping cache and delvick cache would help, but instead the phone is pretty much unusable now. It's really weird.
Click to expand...
Click to collapse
Here goes that frantic post. I installed the rom, worked fine. I did one of the updates for the status bar, now whenever it goes to boot it gets stuck at the samsung galaxy s4 screen. I've tried doing a full wipe, wiping cache and delvick cache and even trying to install the stock rooted rom or the blu rom on top of itself and i still get the same thing. Any ideas? I'm trying not to be too flash happy because I don't want a brick.

iivisionii said:
Here goes that frantic post. I installed the rom, worked fine. I did one of the updates for the status bar, now whenever it goes to boot it gets stuck at the samsung galaxy s4 screen. I've tried doing a full wipe, wiping cache and delvick cache and even trying to install the stock rooted rom or the blu rom on top of itself and i still get the same thing. Any ideas? I'm trying not to be too flash happy because I don't want a brick.
Click to expand...
Click to collapse
Have you tried the battery pull trick once frozen?

ObrienDave said:
Have you tried the battery pull trick once frozen?
Click to expand...
Click to collapse
I finally got out of the boot logo. I looked around the forums and found someone with a similar problem. Seems the recovery wasn't deleting all the files for him so he deleted everything manually instead of just wiping. I did the same and installed triforce rom and it's booted now.
Just for future reference though, would you mind explaining or pointing me to where I can read about the battery pull trick?

iivisionii said:
I finally got out of the boot logo. I looked around the forums and found someone with a similar problem. Seems the recovery wasn't deleting all the files for him so he deleted everything manually instead of just wiping. I did the same and installed triforce rom and it's booted now.
Just for future reference though, would you mind explaining or pointing me to where I can read about the battery pull trick?
Click to expand...
Click to collapse
Basically, quite a few people have recommended pulling the battery once frozen.
Even when you do a power off, you are NOT completely removing power from the system.
Disconnecting the power is the only way to accomplish this.

ObrienDave said:
Basically, quite a few people have recommended pulling the battery once frozen.
Even when you do a power off, you are NOT completely removing power from the system.
Disconnecting the power is the only way to accomplish this.
Click to expand...
Click to collapse
Ah ok. Good tip to know. I had tried that and it didn't work. Seems to be working ok now. I'm gonna be careful not to screw it up cuz its already 1 am, hehe. Thanks for everyone's tips.

[Q] Help! Nexus 4 stuck in bootloop after 4.4 update.

Hi guys,
I tried to update my Nexus 4 to 4.4 when Google pushed the update out for it yesterday, I forgot I had unlocked the phone (I don't have any custom ROMs on it, just SuperSU.)
Every time I try and power it on, the loading screen is endless, although I can hold power and volume down to enter recovery mode, nothing seems to be working.
I am a bit of a novice so any help or suggestions would be really appreciated!
Thanks.

The first few pages of the forum is littered with posts like this, i was in the same situation.
What i did was download the 4.3 rom from google, and flash /boot and /system onto the phone. I suspect the 4.4 rom would also work.
This got the phone booting without harming (most of) my data, but much of the UI was mangled and didnt work properly. I tried to backup my images over USB but it didnt work, you might have a better result. I also wanted to backup my SMS but they had all vanished.
I rebooted the phone to recovery (TWRP) and used adb to backup the sdcard (adb pull /sdcard sdcard) then did a full flash using the 4.4 rom downloaded from google and that got it working again. Then i reflashed the latest version of TWRP recovery and SuperSU.
Hope that helps.

That's really helpful, thanks! Is there ANY chance of a step-by-step? I'm a complete 'noob' probably a mistake to root in the first place :crying:
If you're busy don't worry, just don't want to **** things up more than I have haha.
Thanks, appreciate it.

GeorgeAmodio said:
That's really helpful, thanks! Is there ANY chance of a step-by-step? I'm a complete 'noob' probably a mistake to root in the first place :crying:
If you're busy don't worry, just don't want to **** things up more than I have haha.
Thanks, appreciate it.
Click to expand...
Click to collapse
Look here http://forum.xda-developers.com/showthread.php?t=2010312 for flashing a factory image guide.

gee2012 said:
Look here http://forum.xda-developers.com/showthread.php?t=2010312 for flashing a factory image guide.
Click to expand...
Click to collapse
Got stuck in google screen, tried to flash factory images but my pc won't detect the phone anymore. Any advice?
Edit: Solved.

arffrhn said:
Got stuck in google screen, tried to flash factory images but my pc won't detect the phone anymore. Any advice?
Edit: Solved.
Click to expand...
Click to collapse
Cheers guys, a lot more helpful than the bloke from Google. Will try it in the morning!

This will surely help
If somebody is facing boot loop after kitkat update on nexus 4 and no data backup can try to go to safe mode and backup their data. To goto safe mode on boot screen just keep pressing up and down volume button for some time phone will get into safe mode and can be backed up.

Hi,
It also happened to me, dont know if it is related to having ROOT or not, but i had to manually flash factory image (4.4) and it worked. I flashed everything except userimage.img but on first boot it took like 15 minutes to reboot and then all my personal data (photo, music...) was gone....
So just be cautious before upgrading!

Hi,
It also happened to me, dont know if it is related to having ROOT or not, but i had to manually flash factory image (4.4) and it worked. I flashed everything except userimage.img but on first boot it took like 15 minutes to reboot and then all my personal data (photo, music...) was gone....
So just be cautious before upgrading!

gee2012 said:
Look here http://forum.xda-developers.com/showthread.php?t=2010312 for flashing a factory image guide.
Click to expand...
Click to collapse
Yeah that is pretty much what I did to fix mine except that I did not flash the userdata (step 10 in chapter D) so that I would't loose my data.

arffrhn said:
Got stuck in google screen, tried to flash factory images but my pc won't detect the phone anymore. Any advice?
Edit: Solved.
Click to expand...
Click to collapse
What did you end up doing for your PC to detect your phone?

iamj00 said:
What did you end up doing for your PC to detect your phone?
Click to expand...
Click to collapse
I had sideloaded a rom in recovery so that it will replace the lost system.img on my phone. Then, it booted up and I flashed back factory images the usual way. Everything is running smoothly again.

arffrhn said:
I had sideloaded a rom in recovery so that it will replace the lost system.img on my phone. Then, it booted up and I flashed back factory images the usual way. Everything is running smoothly again.
Click to expand...
Click to collapse
I don't know what any of that means or how to do it...

iamj00 said:
I don't know what any of that means or how to do it...
Click to expand...
Click to collapse
This is sideload guide. And the is the rom I used to sideload before: Purity. After I had successfully booted into the system. I flashed 4.4 factory images using this awesome noob friendly guide for a clean kitkat update.

arffrhn said:
I had sideloaded a rom in recovery so that it will replace the lost system.img on my phone. Then, it booted up and I flashed back factory images the usual way. Everything is running smoothly again.
Click to expand...
Click to collapse
iamj00 said:
What did you end up doing for your PC to detect your phone?
Click to expand...
Click to collapse
Installing the driver. Refer to this thread http://forum.xda-developers.com/showthread.php?t=1992345
Boot to bootloader and connect to your PC, usually Windows will find the driver automatically

[Q] Phone Won't Reboot Without Looping.

I got my new Note 3 2 weeks ago and after a week of ownership decided to root it and install a custom rom.
Rooting went fine and then I installed my first custom rom Echoe Rom v.4.1 Full. But the problem I had was that, after installing all my apps, when I went to reboot the phone it just went into a continuous bootloop. So I thought I'd try another rom and installed Omega v4.0 and had the same problem, boot loop after rebooting.
So my question is why? Why are all roms causing me bootloops after I reboot? I'm having to either keep charging the phone and keeping it on 24/7 or if, for some reason it does power off, clearing davik cache and performing a factory reset to enable me to boot the phone up again and go through the whole install process over again.
Can I do anything to stop this or has anyone any idea why it is happening please?

Prozac69 said:
I got my new Note 3 2 weeks ago and after a week of ownership decided to root it and install a custom rom.
Rooting went fine and then I installed my first custom rom Echoe Rom v.4.1 Full. But the problem I had was that, after installing all my apps, when I went to reboot the phone it just went into a continuous bootloop. So I thought I'd try another rom and installed Omega v4.0 and had the same problem, boot loop after rebooting.
So my question is why? Why are all roms causing me bootloops after I reboot? I'm having to either keep charging the phone and keeping it on 24/7 or if, for some reason it does power off, clearing davik cache and performing a factory reset to enable me to boot the phone up again and go through the whole install process over again.
Can I do anything to stop this or has anyone any idea why it is happening please?
Click to expand...
Click to collapse
Check this thread

Dahdoul said:
Check this thread
Click to expand...
Click to collapse
Thanks but I've tried that and am still getting bootloops on all roms I install! I'm now trying [26.11.2013] X-NOTE v5.1 N9005 MJ7 and yet again, after going through the initial setup and installing my apps, I'm getting bootloop when rebooting the phone.

Prozac69 said:
Thanks but I've tried that and am still getting bootloops on all roms I install! I'm now trying [26.11.2013] X-NOTE v5.1 N9005 MJ7 and yet again, after going through the initial setup and installing my apps, I'm getting bootloop when rebooting the phone.
Click to expand...
Click to collapse
Check this ROM it fixes all my issues,Wipe/Factory reset from recovery mod then flash the first PreRooted rom via Odin 3.04 in the thread and make sure you unroot your device.

Dahdoul said:
Check this ROM it fixes all my issues,Wipe/Factory reset from recovery mod then flash the first PreRooted rom via Odin 3.04 in the thread and make sure you unroot your device.
Click to expand...
Click to collapse
Many thanks Dahdoul. I'm downloading the first PreRooted rom from the thread. Hope that's the right one! Do I need to unroot the phone before powering it up and, if so, how do I unroot it?

Prozac69 said:
Many thanks Dahdoul. I'm downloading the first PreRooted rom from the thread. Hope that's the right one! Do I need to unroot the phone before powering it up and, if so, how do I unroot it?
Click to expand...
Click to collapse
two ways to Unroot your device:
Go to superuser app in your phone then settings press on unroot completely option and you are ready to go.
OR
In recovery mod Wipe cache partitions and reset factory settings then flash the stock rom by odin.

[Q] Safestrap and Restoring Stock ROM

I have a rooted Galaxy Note 3 (Verizon). I'm running Safestrap and made a backup of the stock ROM about two weeks ago.
...I had not tried any other ROMs, now I wish I had. Something went wrong with my stock ROM, long story short - it's just not workin' right and I want to restore it from the backup I've made.
I want to restore it to the stock ROM slot (not a new ROM slot).
The backup is on a Micro SD card, Safestrap sees the backup file. The 'Restore' button is not red (while I've got the stock ROM activated).
I haven't done anything yet. I'm hoping I can just hit restore and it'll restore the stock ROM slot to the backup I made a couple weeks ago.
...is it that simple? Is there anything I should or should not do?

Twisked said:
I have a rooted Galaxy Note 3 (Verizon). I'm running Safestrap and made a backup of the stock ROM about two weeks ago.
...I had not tried any other ROMs, now I wish I had. Something went wrong with my stock ROM, long story short - it's just not workin' right and I want to restore it from the backup I've made.
I want to restore it to the stock ROM slot (not a new ROM slot).
The backup is on a Micro SD card, Safestrap sees the backup file. The 'Restore' button is not red (while I've got the stock ROM activated).
I haven't done anything yet. I'm hoping I can just hit restore and it'll restore the stock ROM slot to the backup I made a couple weeks ago.
...is it that simple? Is there anything I should or should not do?
Click to expand...
Click to collapse
It is that simple, just hit restore, select the file, then swipe the restore button.

airmaxx23 said:
It is that simple, just hit restore, select the file, then swipe the restore button.
Click to expand...
Click to collapse
Just one more question, if for any reason the restore fails... will Safestrap be unaffected?
What I mean by that is, I have another ROM (Hyperdrive) up and running that I can choose with Safestrap. If for some reason the restoration of the Stock ROM (in the stock ROM slot) fails, Safestrap will keep on working and I can choose Hyperdrive.
...and then if I reboot, I can still choose to boot up into Recovery mode with Safestrap. Is that correct?

Twisked said:
Just one more question, if for any reason the restore fails... will Safestrap be unaffected?
What I mean by that is, I have another ROM (Hyperdrive) up and running that I can choose with Safestrap. If for some reason the restoration of the Stock ROM (in the stock ROM slot) fails, Safestrap will keep on working and I can choose Hyperdrive.
...and then if I reboot, I can still choose to boot up into Recovery mode with Safestrap. Is that correct?
Click to expand...
Click to collapse
If the restore fails you'll get a message saying that it failed, you can then just restore a different backup.

airmaxx23 said:
If the restore fails you'll get a message saying that it failed, you can then just restore a different backup.
Click to expand...
Click to collapse
I've only got the one backup file that I'd made.
If it does fail, could I download a stock ROM from somewhere to put into the Stock ROM slot?
I'm not sure how Safestrap works, in my thinking if I screw up (wipe out) the Stock ROM slot then I've deleted Safestrap too. I think that's where my biggest worries are coming into play here. I'm hoping my understand of that is wrong.
...thanks by the way for your replies :good:
EDIT: I found a site that has a rooted stock ROM for the Verizon Galaxy Note 3. Downloading it now to be safe.

Twisked said:
I've only got the one backup file that I'd made.
If it does fail, could I download a stock ROM from somewhere to put into the Stock ROM slot?
I'm not sure how Safestrap works, in my thinking if I screw up (wipe out) the Stock ROM slot then I've deleted Safestrap too. I think that's where my biggest worries are coming into play here. I'm hoping my understand of that is wrong.
...thanks by the way for your replies :good:
Click to expand...
Click to collapse
If for some odd reason your backup fails you could place one of the available ROMs on your sdcard and install it from there. In a worst case scenario you always have Odin and the .tar files to restore your phone.

airmaxx23 said:
If for some odd reason your backup fails you could place one of the available ROMs on your sdcard and install it from there. In a worst case scenario you always have Odin and the .tar files to restore your phone.
Click to expand...
Click to collapse
Hopefully last question (sorry, want to make sure I have my head wrapped around this)
You said if the restore fails I'll simply get a failed message. ...if that happens, could I choose to boot with the Hyperdrive ROM and restart the phone with no problems?
I guess what I'm trying to ask is, isn't Safestrap running from that Stock ROM slot? Or does it run independently of whatever ROMs are in the slots.

Twisked said:
Hopefully last question (sorry, want to make sure I have my head wrapped around this)
You said if the restore fails I'll simply get a failed message. ...if that happens, could I choose to boot with the Hyperdrive ROM and restart the phone with no problems?
I guess what I'm trying to ask is, isn't Safestrap running from that Stock ROM slot? Or does it run independently of whatever ROMs are in the slots.
Click to expand...
Click to collapse
If the restore fails it will not effect SafeStrap, you will just be able to boot up HyperDrive afterwards. The chances of it failing are extremely slim.

airmaxx23 said:
If the restore fails it will not effect SafeStrap, you will just be able to boot up HyperDrive afterwards. The chances of it failing are extremely slim.
Click to expand...
Click to collapse
Thank you so much for all your help! I'm probably going to wait 'til tomorrow evening to do this (need my phone runnin' smoothly from now 'til then for work).
...not sure which reply of yours to click 'THANKS' on. I guess the first one, but they were all helpful. :good:

Twisked said:
Thank you so much for all your help! I'm probably going to wait 'til tomorrow evening to do this (need my phone runnin' smoothly from now 'til then for work).
...not sure which reply of yours to click 'THANKS' on. I guess the first one, but they were all helpful. :good:
Click to expand...
Click to collapse
One more thing, more of a "heads up". During the restore if your screen turns off and pressing Power or Home doesn't turn it on just leave it and when the restore is done it will turn on or just reboot on it's own. Restores can take 5 minutes or more depending on how big of a backup file you have.

airmaxx23 said:
One more thing, more of a "heads up". During the restore if your screen turns off and pressing Power or Home doesn't turn it on just leave it and when the restore is done it will turn on or just reboot on it's own. Restores can take 5 minutes or more depending on how big of a backup file you have.
Click to expand...
Click to collapse
Thought you might like to know, my meeting for tomorrow was cancelled so I went ahead and tried the restoration. ...worked FLAWLESSLY!! Whew!! :laugh:
So my phone is back, everything is running PERFECTLY.
Which brings me to a new question (hopefully you might know). I'm on 4.3 and do not want to get the OTA update for 4.4 from Verizon. It will download automatically (640 MBs or so), and a notification will appear that can't be swiped away.
Is there something in Titanium Backup that I can freeze to prevent the OTA update? To stop that non-swipable notification from appearing?

Twisked said:
Thought you might like to know, my meeting for tomorrow was cancelled so I went ahead and tried the restoration. ...worked FLAWLESSLY!! Whew!! :laugh:
So my phone is back, everything is running PERFECTLY.
Which brings me to a new question (hopefully you might know). I'm on 4.3 and do not want to get the OTA update for 4.4 from Verizon. It will download automatically (640 MBs or so), and a notification will appear that can't be swiped away.
Is there something in Titanium Backup that I can freeze to prevent the OTA update? To stop that non-swipable notification from appearing?
Click to expand...
Click to collapse
Yes, you can follow THIS guide to remove the notification and prevent further OTA updates from showing up.