Can anyone confirm that after the latest jelly bean update 4.1.1 the wifi notification is back. I used sqleditor and returned the 2 values in the db secure and system to 0 and rebooted just as it worked before. This time its not working. Has anyone experienced this when rooting from 4.1.1?
micahansel said:
Can anyone confirm that after the latest jelly bean update 4.1.1 the wifi notification is back. I used sqleditor and returned the 2 values in the db secure and system to 0 and rebooted just as it worked before. This time its not working. Has anyone experienced this when rooting from 4.1.1?
Click to expand...
Click to collapse
Its there, but the old fix does not work. The new fix requires .png's to be removed. Most custom ROMs have this disabled as well.
Didact74 said:
Its there, but the old fix does not work. The new fix requires .png's to be removed. Most custom ROMs have this disabled as well.
Click to expand...
Click to collapse
Is this what we must do for the new mod? http://forum.xda-developers.com/showthread.php?t=1784615
Update: i have tried doing the above method using link above. Page 2 actually contains a zip file you flash an .apk file that supposedly does everything for you. I did this and settings crashed. I read somewhere about deleting an odex file in system/app... i did this and after reboot phone would not get past verizon bootscreen. Fortunately i had a nandroid backup. Anyways Im still searching for a fix that i can do myself. I am looking for mods because I prefer using the stock over modified Roms.
Related
I'm running stock rooted with a few minor tweaks - Notification toggles and Google now installed. Last night I received the message that there was an software update. What happens if I install it? Will I just lose root or will everything be changed back to stock?
EDIT: I misclicked and posted this in the wrong forum. Mods, can you move it?
JoeyBert said:
I'm running stock rooted with a few minor tweaks - Notification toggles and Google now installed. Last night I received the message that there was an software update. What happens if I install it? Will I just lose root or will everything be changed back to stock?
EDIT: I misclicked and posted this in the wrong forum. Mods, can you move it?
Click to expand...
Click to collapse
I updated mine and lost root.
Went through the rooting process again and I have root. No big deal.
Hi, as the title states, yesterday I received a notification from Verizon that a new update is ready to be installed. I can only defer it for 5 days, which I did. I'm running TouchWiz Eclipse ROM 1.0. I went ahead and renamed SMD.apk to SMD.bak, because I read somewhere that's what I needed to do to prevent Verizon from pushing updates.
What I wanted to do is confirm that what I did would work (as in prevent Verizon from updating my awesome ROM and thus bricking my device). Also, I think the update is already downloaded and just ready to be installed. Will that affect anything? Would renaming SMD.apk still prevent it from being installed, or is that only to prevent it from being downloaded?? Please halp!!
Cheers,
ED
ExcludedDroid said:
Hi, as the title states, yesterday I received a notification from Verizon that a new update is ready to be installed. I can only defer it for 5 days, which I did. I'm running TouchWiz Eclipse ROM 1.0. I went ahead and renamed SMD.apk to SMD.bak, because I read somewhere that's what I needed to do to prevent Verizon from pushing updates.
What I wanted to do is confirm that what I did would work (as in prevent Verizon from updating my awesome ROM and thus bricking my device). Also, I think the update is already downloaded and just ready to be installed. Will that affect anything? Would renaming SMD.apk still prevent it from being installed, or is that only to prevent it from being downloaded?? Please halp!!
Cheers,
ED
Click to expand...
Click to collapse
Best way to check is to go into Settings/About Phone/Software Update. If it force closes then you're all set. Renaming or uninstalling "smd 1.0" causes the phone to not actively poll for future OTAs from that moment on. Using a file explorer, check in /cache and delete the update.zip for VRBMF1 cuz you deferred the OTA which means it saved to your phone already.
I checked Settings>About device but there's no Check for upgrade option. I assume it was taken out as part of the ROM. I went ahead and deleted some sort of fupgrade in /cache. Then went and wiped cache in recovery and fixed permissions just to top it off. I think I'm good!! Thanks
ExcludedDroid said:
I checked Settings>About device but there's no Check for upgrade option. I assume it was taken out as part of the ROM. I went ahead and deleted some sort of fupgrade in /cache. Then went and wiped cache in recovery and fixed permissions just to top it off. I think I'm good!! Thanks
Click to expand...
Click to collapse
i think eclipse is aosp not touchwiz , iam running the same thing but its aosp eclispe here the link to verified
http://forum.xda-developers.com/showthread.php?t=2142267 if it is you will never have problems of verizon trying to push ota updates
xavierxxx2p said:
i think eclipse is aosp not touchwiz , iam running the same thing but its aosp eclispe here the link to verified
http://forum.xda-developers.com/showthread.php?t=2142267 if it is you will never have problems of verizon trying to push ota updates
Click to expand...
Click to collapse
There is a touchwiz version, it just wasn't updated in awhile and it's pretty buried in the development section.
Sent from my SCH-I535 using Tapatalk 4 Beta
I tried downgrading my Beanstalk OS (4.4) to Unofficial CM 10 (4.3) but got the Status 7 error. I found out that you can bypass the error by editing the updater-script file and removing the assert code. But I also learned that you can brick your phone if you do it wrong. I want to make sure this will work.
Is this the best way to downgrade and avoid the Status 7 error?
I need help on this too.
I was about to flash back to stock until I saw this thread.
Anybody could find a solution for that? I have a similar problem.
status 7 error means ur recovery version for 4.4 and 4.3 are diffrent.
I don't know how to overcome this because I was stuck in same problem.then I try to do it by odin for 2.3.3 stock rom.
at that time my phone get stuck in loop then I go to samsung store but they also can't fix it.
then I search on net to recover it.
I use some random technjque and finally got succeess
Sent from my SAMSUNG-SGH-I997 using xda app-developers app
volkix said:
Anybody could find a solution for that? I have a similar problem.
Click to expand...
Click to collapse
If u cannot go back to 4.3 flash an old recovery which is compatible with 4.3 and then try if this does not works then it hardly takes 10/12 mins to go back to 2.3.6 and from there to 4.3.
Restore a previous backup of a jellybean rom. It worked for me.
androidnooob98 said:
Restore a previous backup of a jellybean rom. It worked for me.
Click to expand...
Click to collapse
Can anyone confirm we can downgrade from 4.4 straight back to 4.2? KK is still so bugging for me.
Yes, you can remove the assert in the edify updater-script, but in doing so, you must ensure that the ROM you are flashing is exactly right for your phone. We are talking same the same target kernel and if it specifies a build number you need to be in, don't glaze over it.
Sent from my ST18i
giobuon said:
Can anyone confirm we can downgrade from 4.4 straight back to 4.2? KK is still so bugging for me.
Click to expand...
Click to collapse
I've tested. We can go from 4.4 to 4.2 without any problem.
Sharing this here in case it saves somebody else an hour or so.
I rooted my stock Infinity ROM at ICS and have followed all the OTA updates to current 4.2.1 just using OTA Rootkeeper, apparently successfully. It was only recently when I tried to add another app that required root that I discovered I couldn't grant root permissions. To make it worse, I cleared SU data in an attempted fix which successfully removed root from apps that had been OK :crying:
Then I came across this fix that had been applied to a TF300:
http://forum.xda-developers.com/showthread.php?t=2183105
It works as described on the TF700 too and seems to have completely fixed my problem.
Thanks to Koush for the fix to blubbhome for posting it somewhere I could find it.
I am out of warranty now and about to install a different ROM so thanks to all devs for the good work.
Hey everyone. The old flash CWM_CustomBootanimation_44_Enable.zip that worked with 4.4.2 no longer
works with 4.4.4. Just shows a blank screen.
I've been unable to find a working confirmed flashable that can renable boot animation zip functionality
for 4.4.4 and above. Does anyone have any idea how i can modify the old mod or know of a already existing fix?
variance said:
Hey everyone. The old flash CWM_CustomBootanimation_44_Enable.zip that worked with 4.4.2 no longer
works with 4.4.4. Just shows a blank screen.
I've been unable to find a working confirmed flashable that can renable boot animation zip functionality
for 4.4.4 and above. Does anyone have any idea how i can modify the old mod or know of a already existing fix?
Click to expand...
Click to collapse
Sounds like something right up @tdunham's alley...
Sent from my SM-G900P using XDA Free mobile app
You could try the bootanimation fix I posted for android L, but backup first.
http://forum.xda-developers.com/showpost.php?p=57221888&postcount=115
Probably worse case scenario is this will kill your bootanimations but its worth a try.
Only flash the 5.0 bootanimation file from the bottom of the post.