Database Develop

Failed OTA to 4.2

I had the notification for 4.2 update yesterday morning and after pondering for the day I decided to initiate the upgrade which for some reason or another the update failed.
Is there anyway of finding out why the update failed and since the failure I've had no further notifications of the update so how can I try the update again?
Thanks
Jon

Update just failed for me too, which having read up, looked like it might have been because of having an alternate recovery installed.
So I removed the recovery .................UPDATE FAILED
Removed root.....................................UPDATE FAILED
Locked Bootloader..............................UPDATE FAILED
Full system wipe.................................UPDATE FAILED
You can force a retry by going to App,------All-------Google Services Framework and stopping the process and wiping the data
Then checking for update manually.
Some folks say you can have problems with Play and push notification after the framework wipe, but as I had gone the route of restoring to default, I wasn't bothered as I will just do the same again.
I wonder if there is a deeper issue however, than just my tablet.
Phil
jonchill said:
I had the notification for 4.2 update yesterday morning and after pondering for the day I decided to initiate the upgrade which for some reason or another the update failed.
Is there anyway of finding out why the update failed and since the failure I've had no further notifications of the update so how can I try the update again?
Thanks
Jon
Click to expand...
Click to collapse

did you guys did anything or change anything from system, like change the proxyprovider.apk for flash support? Mine failed through OTA and even via manual update but then I changed back the those apks and things went well and now I am on 4.2. Just sharing my experience and hope it can help you guys. somewhat.

If you guys replaced the stock recovery, deleted or froze any stock apps,or modified any system configuration files, OTA is going to fail.

My tablet updated just fine and it is both rooted and unlocked. My galaxy nexus which is the same (both rooted and unlocked) for some reason fails on the 4.2 update.

I had the exact same problem over the past two days, I don't have a custom recovery, just unlocked bootloaded and root.
just lou said:
If you guys replaced the stock recovery, deleted or froze any stock apps,or modified any system configuration files, OTA is going to fail.
Click to expand...
Click to collapse
OOOOOH! I froze then deleted the KOREAN IME app, because why the heck do I need a Korean app on my tablet? Hmm, so what are my options? Can I just redownload the Korean IME off the play store and OTA will work then?
Was there any other forced IME like Chinese that's 'baked in' to the Google ROM? I forgot if I may have deleted any others, but I think it was only Korean.

just lou said:
If you guys replaced the stock recovery, deleted or froze any stock apps,or modified any system configuration files, OTA is going to fail.
Click to expand...
Click to collapse
That explains it then I've deleted and frozen stock apps.
Thanks

I'm the same, i deleted system apps.
Is the only way to fix this to use a pc and adb the 4.1.2 zip and gapps?
Is there any way to fix it from the device itself?
(I've tried flashing the 4.1, 4.1.2 and 4.2 via CWM)
Would reflashing the 4.1 gapps help?
Sent from my Nexus 7 using xda premium

I had the same problem. Used titanium backup and the "integrate system apps updates into ROM" option and then couldn't update to 4.2.
Tried several things I read in this forum but nothing worked.
Had to erase everything and flash the stock ROM I downloaded from Google. They have a 4.2 stock ROM too so didn't need to update afterwards.
Then restore all your apps from backup and you are set.
Sent from my Nexus 7 using Tapatalk 2

Wow, all because a damn Korean IME app? Geez, what a pain, Google. :|

Chocoburger said:
Wow, all because a damn Korean IME app? Geez, what a pain, Google. :|
Click to expand...
Click to collapse
The alternative is that you restore your system folder to its original state (i.e. get hold of that Korean IME app, stick it back in /system/app and set the correct permissions). I had to do this with Google Wallet but it can be done if you know exactly what you've changed and avoids flashing a factory image and setting your device up again (albeit that Titanium makes this relatively painless now).

Have a brand new 32 GB N7, and having the same update fail, right out of the box, like wtf

CFRTim said:
Have a brand new 32 GB N7, and having the same update fail, right out of the box, like wtf
Click to expand...
Click to collapse
Me too. Also a 32gb N7. I owned it less than a week. Multiple factory resets didn't correct the issue either. I returned it to the store for a refund. Didn't want to keep a device that would never install updates.

I have 32 gigabyte Nexus 7 and it came with Android 4.2 out of the box so I guess no problems with the updates
Sent from my Nexus 7 using XDA Premium HD app

CFRTim said:
Have a brand new 32 GB N7, and having the same update fail, right out of the box, like wtf
Click to expand...
Click to collapse
So your saying you opened it, turned it on, signed in.....then your status bar should show system update available, click it, accept, let it do its thing and it just failed?
Sent from my Nexus 7 using Tapatalk HD

If you search the forums this has been addressed and solved. You need to reflash the os - you don't need root. Use wugs toolkit. Its a problem on googles end where the nexus was formatted incorrectly, and a reflash fixes it.
Sent from my Nexus 7 using Tapatalk HD

Yep. Got the Android robot on his back, with the triangle/exclamation point on top of him, after downloading, restarting and almost complete install. I've tried multiple times and miserably failed each time, at the same point. Eventually, I was able to manually update it using Wug's Nexus Toolkit, since all other methods failed. Thank you Wug
Sent from my Nexus 7 using Tapatalk 2

OTAs and CWM/TWRP

I'm reading the threads and seeing a consistent pattern (and experienced it myself). Referring at least to 4.1.2 -> 4.2 and 4.2 -> 4.2.1, it seems that you can do the OTA update if you if you have CWM but not TWRP. If you accept the OTA and have CWM, it will reboot into CWM, apply the update, ask if you want to preserve recovery and su, and reboot you into the new version.
If you have TWRP, though, it seems people get stuck at error 7 or similar.
When a larger version comes out in the future though I suspect we'll have to flash by hand as the OTA could blow away custom recovery; but for the two mentioned above at least, it wont kill CWM and installs fine with it in place.
I've loved TWRP in the past, but in this case it looks like CWM is handling the OTAs more gracefully. It's just a random chance that I have the latest CWM on my N7 instead of TWRP.

I have never used twrp, but I have done the last updates through cwm recovery and kept recovery and kept root. Definitely recommend cwm recovery.

I just got the OTA here, on TWRP 2.3.2.1, Nexus 7 no 3G. No errors, just worked.

Yeah just got the new update and I'm still rooted
-Google

iGoogleNexus said:
Yeah just got the new update and I'm still rooted
-Google
Click to expand...
Click to collapse
And you are using which recovery?

Both work. If they don't something else is going on.
Sent from Tapatalk XDA Premium
<><><><><><><><><><><><>
Nexus 7
Clean ROM 3.0 - Leankernel 0.8.x

jb0ne said:
And you are using which recovery?
Click to expand...
Click to collapse
CWM ...
-Google

Worked for me using TWRP
Sent from my SAMSUNG-SGH-T989 using xda premium

Just took the 4.2.1 update im still rooted using TWRP...

Status 7 is usually a security thing regarding the signature I think. If anything CWM has signature verification off by default.
Sent from my Nexus 7 using XDA Premium HD app

I really don't understand why people are having such a hard time understanding what is wrong when they receive an error message with the OTA update.
It's not complicated people. You don't need to be a friggin' brain surgeon or a senior level developer. The error message TELLS YOU what the issue is.
Verifying current system...assert failed: apply_patch_check("/system/SOMEFILE")
Guess what? Something is wrong with SOMEFILE. You either modified it, deleted it, "froze" it in TiBu, or did something else that is causing the update to break.
If you look at the updater-script, you can see everything thing the OTA does. It's just a long batch script basically.
The ONLY way this 4.2.1 OTA update is going to fail due to recovery is if you are using the wrong recovery for your device (ie: grouper on talapia, etc.).

I hear what you are saying but....my N7 is stock, untouched, unlocked & rooted, yet I had problems with CWM & TWRP with the OTA and flashing the update manually.
I had to go back to stock recovery for both updates.
But I can see in this thread some have the OTA update working fine, one thing we all have in common is the N7, yet varied results.

jersonf said:
I hear what you are saying but....my N7 is stock, untouched, unlocked & rooted, yet I had problems with CWM & TWRP with the OTA and flashing the update manually.
I had to go back to stock recovery for both updates.
But I can see in this thread some have the OTA update working fine, one thing we all have in common is the N7, yet varied results.
Click to expand...
Click to collapse
Was your unit a 3G or Wi-Fi only model?

OTA?
I hate to be the hater, but why would anyone here take an OTA? The reason this site exists is specifically to help people to not use the stock software. If cwm survives OTAs it is probably an accident, lol.
Sent from my Nexus 7 using xda premium

brizey said:
OTA?
I hate to be the hater, but why would anyone here take an OTA? The reason this site exists is specifically to help people to not use the stock software. If cwm survives OTAs it is probably an accident, lol.
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
What are you talking about?
XDA is in no way a site dedicated exclusively to "help people not use the stock software". It's a place where people can discuss their hardware/software including stock/custom/etc. usage and modifications. So not only is your comment 100% incorrect, but it's also contrary to this thread in particular. The thread title clear talks about using a CUSTOM recovery with an update to the stock software. So even if you were right (you aren't), your point is counter-intuitive.
There are many people here that are either mostly or completely stock. That's their personal preference and it's completely fine and acceptable. And it most certainly doesn't mean they don't deserve help or assistance here.
---------- Post added at 03:17 PM ---------- Previous post was at 03:13 PM ----------
Also, while OTA updates are written in such a way to remove suid root on the su binary and reinstall the stock recovery image, most new custom recoveries have a work around in place to prevent this. Not to mention it's trivial to restore them back after the update.

brizey said:
OTA?
I hate to be the hater, but why would anyone here take an OTA? The reason this site exists is specifically to help people to not use the stock software. If cwm survives OTAs it is probably an accident, lol.
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
No accident ... I updated my N7 from 4.1 to 4.2 still rooted.. And I just updated again to 4.2.1 ... Don't know about you but I love these kind of updates
Also I like my devices stock, rooted and a few tweaks here and there along with rooted applications... I'm sure there are many of me out there.
-Google

I prefer to never actually flash the recoveries.. just adb boot them as required - that means my system is always stock for the updates and I can pick a recovery at random should I want them (although generally I only use them to get a root shell to install su when I get a new phone).

I am rooted stock with cwm touch and the ota fails staus 7. I'm pretty sure I didn't do anything to "break" the update for myself. It's kind of funny the clockwork stops and asks about flashing an untrusted rom and then doesn't allow it. I would rather sit out of this whole 4.2 bs anyway.

I was rooted and stupidly just clicked the update to 4.2.1 without thinking, it didn't even occur to me to take any measures to keep root or custom recovery. So I lost both. It only took a few minutes with Wugs' toolkit to fix though.

I've taken three OTAs with TWRP and had no problems with any of them.
Sent from my Nexus 7 using Tapatalk HD

Nexus & laggy after 4.4 update

It was smooth before,now its so laggy...
anyone else have this issue?
I'm going to try a factory restore after I back my stuff up but if this is the way its going to be on 4.4 i'm going to be kind of :crying:

Try a clean flash and ull feel the difference, besides half of the apps u use are not optimized for KK so that might be the issue.
Remember after first boot tablet is laggy and services in the background will stop soon.

xateeq said:
Try a clean flash and ull feel the difference, besides half of the apps u use are not optimized for KK so that might be the issue.
Remember after first boot tablet is laggy and services in the background will stop soon.
Click to expand...
Click to collapse
yea im gonna try that,just gotta back up my pics and stuff.
whats that last phone in your pic(the nokia one). I remember it but cant remember the model #.

I guess I got lucky. Mine has been great since the update.

You need to wipe the device clean and begin from scratch. Mine runs better than 4.3 ever did, overall i think its great.

yep, do fresh stock install then 4.4 rocks
cr0wnest said:
You need to wipe the device clean and begin from scratch. Mine runs better than 4.3 ever did, overall i think its great.
Click to expand...
Click to collapse
+1
My 4.4 is great, I did a stock 4.4 KRT14S fresh wipe install, and then installed my apps and entered settings. It runs a lot better than 4.2.2 and 4.3.

yep, same results here! Laggy as hell, i did a backup using helium (as not rooted) to my pc of various game data then let the ota upgrade start, followed by a hard reset a.k.a. a clean install (me thinks??)
Google Play automatically then re installed my apps and settings (most of them!) Finally a restore of some apps and theme settings again using helium from my PC = slow, and getting various app and system crashes ever since...? #Disappointed
Sent from my Nexus 7 using xda app-developers app

nigelhealy said:
+1
My 4.4 is great, I did a stock 4.4 KRT14S fresh wipe install, and then installed my apps and entered settings. It runs a lot better than 4.2.2 and 4.3.
Click to expand...
Click to collapse
So how do I do "a stock 4.4 KRT14S fresh wipe install" ?

illingd said:
So how do I do "a stock 4.4 KRT14S fresh wipe install" ?
Click to expand...
Click to collapse
Many ways, the way I did was to http://www.wugfresh.com/nrt/ this, get drivers installed (once only and the most fiddly thing of all overall) and do "unlock" (once only), and then as I tried 4.2.2. , 4.3, 4.4, 4.4.1 and back to 4.3..... etc is "stock+unroot" then root. Then I copy supersu.zip to /sdcard to keep root on it if it loses root which it does in a few situations. e.g. 4.4 then root then installed Franco kernel lost root.
There is the adb sideload and other methods but once I got the WUGS NRT working, I stuck with that.
I now don't use any google backup/restore at all now, I just install what I want and configure myself. That way it is as vanilla as possible. A few APKS hard to get, I copy them onto fileserver I can access from anywhere.
I've done this with my N4 and N7 2012.

Just purchased a Verizon droid 4

I just purchased a droid 4 from Verizon, have wiped it a few times, but my front facing camera, keyboard, soft key lights are not working. I have searched online for fixes, Motorola said i could pay 150.00 in order to get it replaced. I figured i would come here first to see if anyone had a suggestion or a link to where i could wipe it before it took the 4.4 patch to where it seems to have totally messed it up according to other online sources .

timothy_pierce said:
I just purchased a droid 4 from Verizon, have wiped it a few times, but my front facing camera, keyboard, soft key lights are not working. I have searched online for fixes, Motorola said i could pay 150.00 in order to get it replaced. I figured i would come here first to see if anyone had a suggestion or a link to where i could wipe it before it took the 4.4 patch to where it seems to have totally messed it up according to other online sources .
Click to expand...
Click to collapse
Are you running with the stock rom?
Have you tried a custom rom?
I mean do you know if it't software issue or hardware issue?
Sent from my XT894 using Tapatalk

dom2319 said:
Are you running with the stock rom?
Have you tried a custom rom?
I mean do you know if it't software issue or hardware issue?
Sent from my XT894 using Tapatalk
Click to expand...
Click to collapse
I am running the latest version of android for that series of phone, believe its 4.4 from verizon, i have not rooted it yet, i am trying to figure out how to get it back to the original state before the updates. As it seems since the update many consumers have had these same issues with out being able to fix them, i have tried fixes that i obtained from the Motorola forums and the lighting situation did not work. Am not sure its hardware due to the keyboard being functional. I appreciate any and all help.

ok found a video on how to bypass the non sim set up panel and here are the versions of android i am running.
98.72.188.xt984.Verizon.en.US
Android version 4.1.2 sorry i messed up the version earlier.

timothy_pierce said:
ok found a video on how to bypass the non sim set up panel and here are the versions of android i am running.
98.72.188.xt984.Verizon.en.US
Android version 4.1.2 sorry i messed up the version earlier.
Click to expand...
Click to collapse
Hi Timothy,
OK you're running Android JellyBean, AFAIK Verizon never released a Kit-Kat (Android 4.4) update for the device.
Personally, given that AFAIK it's not possible to roll back to a previous version of Android (you can only reinstall the previous version), I would suggest you root it, install SafeStrap and do a quick install of something like Cyanogen (not the best ROM for Droid 4 IMHO but will quickly do the job). At least those can be rolled back.
Rooting and installing SafeStrap is SO utterly easy on this device that it should be made harder
For a start, everything you'll need, if you want, can be grabbed from my Google Drive
h t t p s://drive.google.com/folderview?id=0B3MTT4jOK738fmdLLURMQVBGWkVpTDBMTmg1UGFUd3JWNDNlcUVzQWZFQXBpT3dCMFJhdTg&usp=drive_web&tid=0B0EWnwDplBc0fnBGbDg3ZmdZNC1ET1JZeVRWdE8tZ2p1Um41OThLeTZ2WWtRNE9TUXJpS2M
If you don't have any file manager yet (as you'll need one), ES File Explorer is a great one, as you'll most certainly need it.
Rooting:
Get Towel root from:
h t t p s://drive.google.com/folderview?id=0B0EWnwDplBc0fi1KMVVIRmQteDhFYWcwSGFselpXWmpfV29LWlZlZVVHdlU0b0FBQnYtNkk&usp=drive_web&tid=0B0EWnwDplBc0fnBGbDg3ZmdZNC1ET1JZeVRWdE8tZ2p1Um41OThLeTZ2WWtRNE9TUXJpS2M#list
install it and root your Droid4
Installing SafeStrap:
Check out this page for info about SafeStrap
h t t p://blog.hash-of-codes.com/how-to-safestrap/
Once your device is rooted, you can install SafeStrap
Again you can grab a copy from my Google drive:
h t t p s://drive.google.com/folderview?id=0B0EWnwDplBc0fk5aeUhFSjlQMzZ2TXNYM0lsWVRDWklLOU1nYkUybzU1emJDV1IwS0tkazg&usp=drive_web&tid=0B0EWnwDplBc0fnBGbDg3ZmdZNC1ET1JZeVRWdE8tZ2p1Um41OThLeTZ2WWtRNE9TUXJpS2M
Installing a custom rom:
Once you have installed SafeStrap
You can download CM11 which I've tested from:
h t t p s://drive.google.com/folderview?id=0B0EWnwDplBc0fnJJd0s1ZV85aEE1YkF0TjNzM28tcmxfOVkzZVJ0OUVhLThrR29sb19vVW8&usp=drive_web&tid=0B0EWnwDplBc0fnBGbDg3ZmdZNC1ET1JZeVRWdE8tZ2p1Um41OThLeTZ2WWtRNE9TUXJpS2M
- Copy the file to your SDcard0 (usually named MOT)
- Boot into SafeStrap, create a small partition (1000 MB for data is enough) in Slot1
- install CM 11 and see if the problem is fixed in CM11 and report back to me
Take care
Dominique

or just see [INDEX] Motorola Droid 4

Nexus 6 shows 4,000% battery life after root?

I got my Nexus 6P for Christmas, and I decided to root my Motorola Nexus 6 from last year. I've been waiting to do this for a few months, and was excited to finally enable several of the options I couldn't otherwise enable (such as double tap to wake and auto rotate on the lock screen and Google Now launcher). About an hour ago I got around to rooting and done so with little issues. It's been a little under an hour since I rooted, and I just now noticed that the battery life is being displayed as having over 4,000% charge. I rooted following the steps in a YouTube video by DroidModderX and the device is running perfectly fine. The device hasn't died yet, and I'll be interested to see when it will die. The battery life seems to fluctuate between 4,001% and 4,204% (Those two figures being the highest and lowest figures respectively). Rebooting does not fix this error.
I know it's not a massive problem, but I'd like to know what's causing this issue and how to resolve it. I haven't flashed any custom OS's on my phone, I'm still running stock Android 6.0.1 Marshmallow with the latest December security patches. The device is carrier unlocked also. How can I fix this?
Thanks,
Eamonn.

sonic2kk said:
It's been a little under an hour since I rooted, and I just now noticed that the battery life is being displayed as having over 4,000% charge. being the highest and lowest figures respectively). Rebooting does not fix this error.
Click to expand...
Click to collapse
You need to use updated root files. The battery issue arises when you're on 6.0.1 but aren't using the right file version. Easily fixed not to worry, just re-root with updated files and it will resolve with no lasting harm.

sansnil said:
You need to use updated root files. The battery issue arises when you're on 6.0.1 but aren't using the right file version. Easily fixed not to worry, just re-root with updated files and it will resolve with no lasting harm.
Click to expand...
Click to collapse
Ah, thank goodness. I'll re-root tomorrow and post back if I have any problems. Thanks!

Thanks, that fixed the issue. I re-rooted and everything is working fine. I flashed the ElementalX kernel. However on boot I now get a warning with a red triangle saying "Your device is corrupt. It cannot be trusted and may not work properly". This warning goes away, and the phone proceeds to boot up successfully. Everything on the device works perfectly fine with no issues. I am successfully rooted running Android Marshmallow 6.0.1, but this screen scares me somewhat. I rooted my Galaxy SII and I have a yellow triangle on boot but only on the Samsung splash screen. Is this something new in Android M or something unique to Nexus devices? I researched this a bit and found one post on Reddit that said this happened in the M previews, and that it was nothing to be concerned about. Is there a way to remove this screen, or is it just like the yellow triangle on the SII? Should I even be concerned with this, or is it something to just dismiss? Is my device at risk any more than normal when rooting, and have I done something wrong? I'm a bit of a newbie at the rooting stuff, but I intend to use my Nexus 6 and SII to learn more about it (and my 6P way into the future, once I get a new phone).
Thanks in advance.

Why did you need root for the Google now launcher?

mikeprius said:
Why did you need root for the Google now launcher?
Click to expand...
Click to collapse
What do you mean? I can run the Google Now launcher perfectly fine. Root works fine as well. The problem isn't with the Google Now launcher but with the warning on boot. I didn't need to root, I chose to. Am I misunderstanding?

Your original post made it seem like you need root for double tap to wake and Google now launcher.

sonic2kk said:
Thanks, that fixed the issue. I re-rooted and everything is working fine. I flashed the ElementalX kernel. However on boot I now get a warning with a red triangle saying "Your device is corrupt. It cannot be trusted and may not work properly". This warning goes away, and the phone proceeds to boot up successfully. Everything on the device works perfectly fine with no issues. I am successfully rooted running Android Marshmallow 6.0.1, but this screen scares me somewhat. I rooted my Galaxy SII and I have a yellow triangle on boot but only on the Samsung splash screen. Is this something new in Android M or something unique to Nexus devices? I researched this a bit and found one post on Reddit that said this happened in the M previews, and that it was nothing to be concerned about. Is there a way to remove this screen, or is it just like the yellow triangle on the SII? Should I even be concerned with this, or is it something to just dismiss? Is my device at risk any more than normal when rooting, and have I done something wrong? I'm a bit of a newbie at the rooting stuff, but I intend to use my Nexus 6 and SII to learn more about it (and my 6P way into the future, once I get a new phone).
Thanks in advance.
Click to expand...
Click to collapse
https://www.androidfilehost.com/?fid=24269982087021512 gives you 6.0.1 bootstack for Nexus 6 (shamu). Flash this in TWRP. This should fix your corrupted boot splash screen. It's new in Android M when you've installed custom kernel and/or roms. It does not hurt anything except Android Pay is unlikely to work once rooted.
EDIT: I forgot to included mmb29k, non-encrypt boot.img made by GerardF: https://www.androidfilehost.com/?fid=24340319927534323 (flash this also after you flash the bootstack).

HueyT said:
(removed url) gives you 6.0.1 bootstack for Nexus 6 (shamu). Flash this in TWRP. This should fix your corrupted boot splash screen. It's new in Android M when you've installed custom kernel and/or roms. It does not hurt anything except Android Pay is unlikely to work once rooted.
EDIT: I forgot to included mmb29k, non-encrypt boot.img made by GerardF: (removed url) (flash this also after you flash the bootstack).
Click to expand...
Click to collapse
Worked perfect. That got rid of the corrupt message. One last question: (This is the last one, I swear! ) Are you saying that Android Pay won't work at all after rooting or that it wouldn't have worked if that screen had have appeared on boot? I hope to use the service if and when it comes to the UK.
mikeprius said:
Your original post made it seem like you need root for double tap to wake and Google now launcher.
Click to expand...
Click to collapse
Ah, sorry for the confusion my friend ?

I would have kept it at 4,000% - that's like 2 weeks of battery life with no charge...

orangekid said:
I would have kept it at 4,000% - that's like 2 weeks of battery life with no charge...
Click to expand...
Click to collapse
Haha if it wasn't a display error I might have (Though it would have only been like 3 days on the Nexus 6 )

Stupid question but where do I get updated files. I followed the method on root junky for the Nexus 6

Dalek Caan said:
Stupid question but where do I get updated files. I followed the method on root junky for the Nexus 6
Click to expand...
Click to collapse
Sorry, I don't remember where I got the updated files now. I do remember sticking to looking on XDA and not just searching randomly online, maybe you could try searching the forums?

is it possible to root with chainfire root files. I did a clean install of the January security update, then flashed the latest boot.img from chainfire then flashed SuperSU 2.66.zip through TWRP, but im still getting this. I received this same issue with the last patch. Im at the point where it isnt worth rooting. Any help would be appreciated.