Database Users

[Q] Did I f* up my Play?

Hey guys. I hate making my first post a really noobie question but here it goes.
I just updated my rooted Xperia Play to 2.3.3 and it erased and/or re-wrote all of my system apps. I stupidly converted some of my downloaded apps into system apps using Titanium (because system apps turn red on the list. It helped me quickly figure out what was external and what was internal. Stupid, yes, and more trouble then it was actually worth.) so those apps were lost. Didn't matter, I had backups but I lost my root so I couldn't access them.
Forgetting what I used to root my phone originally I decided to use z4root after reading about it somewhere. The site I got it from is usually trust worthy but when I downloaded the file my OfficeScan (its a school bought computer) warned me of a potential virus threat. I wrote it off as just the pop-up ad and un-zipped and transferred the file to my phone. I still am not sure if it was a virus or not... Running z4root it got up to "acquiring shell root..." or something like that before kicking me back to the home screen with no change. I, again, stupidly, re-ran it several times without rebooting between each attempt. Giving up I then realized to reboot. Strangely rebooting was A LOT faster then it was usually is and I don't know if that was z4 or 2.3.3.
Anyway I remembered that I used Gingerbreak last time and re-installed that. I made several attempts with that with no change either. Too many to count, but at least more than 8. Several attempts I got a call or a text and, checking them, ended the process. 2 attempts I left running for about half an hour (I know that the instructions say it will never take more then 10 minutes) and some I ended with a battery pull after more then 10mins(as per instruction).
So I guess I have several questions:
1. How bad did I f* up, If I did so?
2. Any suggestions on how to re-root/fix it?
3. Will switching to an empty SD card, successfully rooting it, and switching back to the full card still keep the root?
4. Does an in phone factory reset work the same as flashing the same rom or will I need to actually flash that new rom?
5. If I do need to flash, where can I find a regular Play rom? Or do you have suggestions about a better rom?
6. Is the fast reboot the work of the half done, possibly a virus, z4root process or just the 2.3.3 update?
7.Lastly Was this tl and you ;dr?
Normally, I wouldn't care if there was no fix; My phone boots much faster, I didn't lose all my apps and only some apps launch a little slower then before. But I made tons of progress on Zenonia 2 and I want my back ups for that... lol.
Any help appreciated. Also thanks for putting up with a noob that's writing way to formally

1. Messing with the system apps, and not backing them up probably caused you to not have an OTA update. I'm guessing you flashed it? Not restoring anything and not doing an OTA was mistake number one. Trying to use z4root was mistake number 2.
2. Get the generic UK firmware from here http://forum.xda-developers.com/showthread.php?t=1097591
-Flash that with Bin4ry and Androxhyde's flashtool
-Put in your carrier's APN settings, configure your google account, wifi etc. etc.
-Get Gingerbreak 1.2, run it(I used Astro to open the apk, and you need uunknown sources enabled).
Gingerbreak only worked for me when I formatted an SD card right before running it. I used a spare that was lying around, not the usual one with all my data, and I suggest you do the same if you kept your titanium backups. Hopefully you'll get rooted after about 3-5 minutes. Do not mess with any apps/bloatware after you have the root.
-After you have root, go into the settings menu and start an OTA update.
You should now have 2.3.3 WITH root.
-Once the phone is updated, install Titanium Backup and start backing up your old apps from before you messed up the phone and lost root.
-At this point feel free to remove the bloatware, but make sure you back it up in titanium for later.
3. Switching SD cards won't affect root at all.
4. A factory reset will reset whatever ROM was installed last. In other words, you can't revert back to 2.3.2 with a reset, it'll just reset 2.3.3 - It's really just for wiping data and settings.
5.The regular play ROM is the UK generic I posted above. The only "better" roms are customs that you need an unlocked bootloader to install. Currently they're still buggy and in development and not worth getting unless you like incomplete ROMs with bugs, and wanna lose the ability to update normally. Both OTA updates and the Sony Ericsson Update Service will brick your phone once the bootloader's unlocked.
6. My phone was booting a bit faster after updating to 2.3.3, and became even faster after removing some bloatware.
-Root doesn't speed up the boot process.
-I highly doubt an Android phone would have a virus that makes it boot faster, it's probably just from the update.
7. No, it wasn't. No, I didn't.

Thanks for the (semi-)quick response. Been browsing around the web with this tab open, constantly refreshing like a creep. I'll try your advice soon but its like 3am, just wanted to say thanks and love your Stocking pic.
Btw is there a difference between A US, UK or CAN rom or do those even exist?

The only real differences are carrier specific apps, and some versions have different games installed.
Sent from my R800

Seems like I was to late to flash and the link to the rom you gave me may have been updated to 2.3.3 as well. I was looking for a Canada/Rodgers rom anyway but the forum search isn't turning up anything and google seems to hate me...
Help anyone?

The link was for 2.3.2 in the generic.
The only rogers rom available is for 2.3.3 so you won't be getting root without an unlocked bootloader with that one.
Just follow the directions and it should be fine.
The rogers apps are available in the android market separately.
Sent from my R800

[Q] Can't get root to restore

I have Voodoo OTA Rootkeeper installed & had done a temp unroot, so I could access Amazon prime content, but now I can't get it to restore the root. Any ideas what I'm doing wrong? And it does say "root su restored" after I push the "restore root" button, but even after 2 device restarts, I'm still unrooted. NEED to get on the regular market!

Could it be because it update the os to 6.2? I don't recall what it was before & it never ASKED me to update it, but idk

LoriH7 said:
Could it be because it updated the OS to 6.2? I don't recall what it was before & it never ASKED me to update it, but I don't know.
Click to expand...
Click to collapse
I doubt it, it's working fine for me and many others on 6.2.

If you used it to unroot before 6.2, then when 6.2 silently upgraded, it would have undone the rooting and killed your OTA rooting.
6.2 didn't ask anyone. if you had wifi connected, it would download without messages. and at some point it would have rebooted, like for me. Or others said once they turned it off it went ahead and did it.
super one click will reroot it in less than a minute and you should be good until next time they do this.

Thelgow said:
If you used it to unroot before 6.2, then when 6.2 silently upgraded, it would have undone the rooting and killed your OTA rooting.
6.2 didn't ask anyone. if you had wifi connected, it would download without messages. and at some point it would have rebooted, like for me. Or others said once they turned it off it went ahead and did it.
super one click will reroot it in less than a minute and you should be good until next time they do this.
Click to expand...
Click to collapse
Thanks! I'd bet that's what happened. It's almost always connected to wifi & I've had it rooted for a couple of weeks. Thanks. Back to super one click....

Ok, so I rerooted, but all of my google services are broken still. Reinstalled the apks, but it refuses to install the googleframework.apk. It's on there, asks me about permissions & then says it won't install. I'm clearly missing a step or something.

wierd issue
When I try to reroot my KF after the 6.2 update it roots the device then attempts to reboot into root... and that is when it fails... it just sits on the kindle fire screen flashing like it is rebooting I let it sit for a few minutes and never fineness, however if I hold down the power it will shutdown and I can start it back up but only half way rooted ... and never finished installing superuser or busybody... any ideas?

Not sure about those issues. Different people reported different problems.
Seems not everyone used the same methods. for me googleframework and market worked perfectly fine afterwards, i didnt need to do anything else.

Once my KF updated to 6.2, I could not restore root through OTA Rootkeeper either. Connected it to my computer, ran SuperOneClick, root was restored and backed up my root once again. I think I needed to reset once to ensure that all of my sideloaded apks still worked.

Well I got it figured out I just did a factory reset and reapplied root and now it is working thanks guys
Sent from my Kindle Fire using xda premium

[Q] Can't install latest OTA update after unroot

Hey guys,
So I've googled around for this issue but I still have a question that no other thread I've found seems to answer.
A few weeks ago I rooted my Razr M. I froze a couple of the verizon apps (like the google chrome bookmarks) and backed up and deleted the amazon apps, IMDB, and Audible apps with titanium. When the new OTA was released this week I restored and thawed all of those apps, but the OTA wouldn't install. It reached about 1/4 through the bar of Andy and then he would be on his side with the caution sign. The phone would reboot and say that the installation failed. I decided to unroot, thinking that may have been the cause, but I still got the same error. From there I did a factory reset, and I'm still getting the same error.
Here's my question: I saw on a couple threads that a factory reset doesn't restore everything in /system, which is where I'm worried there's a discrepancy that isn't allowing the update. Is there a way to do a harder reset that will completely bring the phone back to stock?
I'm currently on System version 98.12.4.XT907.Verizon.en.US if that helps. Android 4.1.1. Baseband version is SM_BP_1139.000.32.62P.

JadedRescue said:
Hey guys,
So I've googled around for this issue but I still have a question that no other thread I've found seems to answer.
A few weeks ago I rooted my Razr M. I froze a couple of the verizon apps (like the google chrome bookmarks) and backed up and deleted the amazon apps, IMDB, and Audible apps with titanium. When the new OTA was released this week I restored and thawed all of those apps, but the OTA wouldn't install. It reached about 1/4 through the bar of Andy and then he would be on his side with the caution sign. The phone would reboot and say that the installation failed. I decided to unroot, thinking that may have been the cause, but I still got the same error. From there I did a factory reset, and I'm still getting the same error.
Here's my question: I saw on a couple threads that a factory reset doesn't restore everything in /system, which is where I'm worried there's a discrepancy that isn't allowing the update. Is there a way to do a harder reset that will completely bring the phone back to stock?
I'm currently on System version 98.12.4.XT907.Verizon.en.US if that helps. Android 4.1.1. Baseband version is SM_BP_1139.000.32.62P.
Click to expand...
Click to collapse
Sounds like you did not defrost those system apps using titanium backup before you factory reset. I would restore from your stock backup and unfreeze those apps with titanium and try the ota again. The OTA checks for certain bloatware apps before it will allow it to install the update.

slogar25 said:
Sounds like you did not defrost those system apps using titanium backup before you factory reset. I would restore from your stock backup and unfreeze those apps with titanium and try the ota again. The OTA checks for certain bloatware apps before it will allow it to install the update.
Click to expand...
Click to collapse
I definitely did defrost those apps.

I'm having the same issue. Stops at about 1/4 of the way and then restarts. I'm gonna try it again without my Rogers(non-verizon) sim card and see if it works. Maybe it checks which sim card is being used.
EDIT: Didn't work, sim card irrelevant.

If you really want the ota then why don't you try mattlgroff's utility here:
http://forum.xda-developers.com/showthread.php?p=39576818
It will return you back to completely stock with one click and then you should be able to take the ota and reroot unlock if desired
Sent from my XT907 using Xparent BlueTapatalk 2

RSD
vLegend said:
I'm having the same issue. Stops at about 1/4 of the way and then restarts. I'm gonna try it again without my Rogers(non-verizon) sim card and see if it works. Maybe it checks which sim card is being used.
EDIT: Didn't work, sim card irrelevant.
Click to expand...
Click to collapse
I tried using Mattlgroff's method (which i'm sure is fine for most) but seems to be geared towards linux users mostly, and I ran into some issues. I have always used RSD to get back to stock and never had an issue. Check it out How To Restore Stock Firmware on Razr M. This will hard restore your phone to the factory image, as well as unroot it, no need to unfreeze or reinstall bloat. It will also obviously erase the internal SD card contents so make sure you back those up.

Yeah looks like slogar25 and cliMAKtic are right. I tried a few more things and its not working. I'll do an rsd in the next couple days and try the ota again.

I'm going to try rsd sometime tonight, I'll let everyone know how it goes. Thanks for all the help!!

I like rsd too. The point is to return too stock.
Sent from my XT907 using Xparent BlueTapatalk 2

Same issue, stops 1/4 of the way through.
Flashing back to stock with the RAZR M utility 1.10 once my phone hits 100% battery (at 93% now). Will let you know if I can take the update after.

Keep in mind
RSD is great to get back to clean stock, but keep in mind that it will remove your root. After taking the OTA update, you will be running firmware v4.1.2. If you used MotoFail2Go exploit to root your phone originally you should note that the exploit apparently does not work for the updated firmware. Instead you should use motochopper, an updated exploit that works on 4.1.2 to root your phone, developed by Drjbliss over at Droidrzr.

I honestly don't care too much about being unrooted at this point anyway, having root wasn't doing too much for me. I managed to get back to the original stock ICS using RSD and everything worked out! Downloaded one update to 4.1.1, then the second update to 4.1.2, and everything went swimmingly.
Thank you so much for all your help everyone!

[Q] Encrypting a Galaxy Note 3

I have a new Galaxy Note 3 (having bricked one trying to understand why it wouldn't encrypt) and now with a full stock rom I still find that the phone is impossible to encrypt.
I have an encrypted SD card in it. (only thing I can think of that might be causing problems)..
Settings > General > Security > Encrypt Device keeps stopping after a single shutdown,
How the heck do I encrypt this thing?? - Am I missing the blindingly obvious..
Thanks

tahnoonp said:
I have a new Galaxy Note 3 (having bricked one trying to understand why it wouldn't encrypt) and now with a full stock rom I still find that the phone is impossible to encrypt.
I have an encrypted SD card in it. (only thing I can think of that might be causing problems)..
Settings > General > Security > Encrypt Device keeps stopping after a single shutdown,
How the heck do I encrypt this thing?? - Am I missing the blindingly obvious..
Thanks
Click to expand...
Click to collapse
I'm having the exact same issue. Encryption is requited to get my work email and I can't get it to go.

Finally got mine to encrypt
Took me a bunch of tries.. and finally once i opened a chat with samsung support it finally worked.. i was at 100% charge, plugged into the wall and if finally worked. not sure if thats a bug in its detection if your over the stated 80% or not... good luck.. i finally got it working though.. only did a fast encryption as it didn't work on previous tries either way... so i just chose one and tried it again.

tahnoonp said:
I have a new Galaxy Note 3 (having bricked one trying to understand why it wouldn't encrypt) and now with a full stock rom I still find that the phone is impossible to encrypt.
I have an encrypted SD card in it. (only thing I can think of that might be causing problems)..
Settings > General > Security > Encrypt Device keeps stopping after a single shutdown,
How the heck do I encrypt this thing?? - Am I missing the blindingly obvious..
Thanks
Click to expand...
Click to collapse
I have the Google Policy Manager and Encryption is required for me too. I started at 81% and the first time I did it, it just rebooted. The second time I did it it worked like it was suppose to. Try it again right after it reboots and see if it works.

Make sure the phone is charged and keep trying over and over.
It will work eventually.

I gave up. I'm using touchdown now for work email which will allow me to skip full device encryption
Sent from my SM-N900V using Tapatalk

Same problem here, it will not encrypt
....help please

This is the answer I found doing a couple of root and unroot
1.If you encrypt the device and then root it you will net get past the passcode in the phone (black screen)
2. If you root the phone first and ten try to encrypt you will get the problems mentioned in this thread
..any tips how to get the phone rooted and then encrypted?

greffel said:
This is the answer I found doing a couple of root and unroot
1.If you encrypt the device and then root it you will net get past the passcode in the phone (black screen)
2. If you root the phone first and ten try to encrypt you will get the problems mentioned in this thread
..any tips how to get the phone rooted and then encrypted?
Click to expand...
Click to collapse
Bump. I'm looking for this answer too.

digittante said:
Bump. I'm looking for this answer too.
Click to expand...
Click to collapse
anyone at all? im stuck. Bump!

was having a similar problem on nexus 4 but safe mode helped there.
dind't help on my new n3. shouldn't have rooted before encrypting.
tried pressing encrypt about 10 times.
tried boot into recovery + wipe . also tried safe mode. also tried unroot + factory reset (pretty sure recovery + wipe /data is the same as reset user data from settings).
waiting for the firmware image to download - decided to try a firmware reflash

and then before flashing it I tried rebooting to recovery and powering off and encrypting and it worked. or maybe it was that random 12th time it worked because of an unrelated reason.
and after trying to root it again it just booted to a black screen after cf-root and enter encryption password screen.
*sigh*

My Work-Around
svyr said:
and then before flashing it I tried rebooting to recovery and powering off and encrypting and it worked. or maybe it was that random 12th time it worked because of an unrelated reason.
and after trying to root it again it just booted to a black screen after cf-root and enter encryption password screen.
*sigh*
Click to expand...
Click to collapse
I'm an AT&T customer, but I bought a T Mobile Note 3 off of Craigslist, unlocked it, rooted using Chainfire's ODIN thread, and then used the RegionFree Lock Away app. I was unable to encrypt just like you guys until I did the following. Flashed TWRP tar file from the TWRP site using ODIN. Rebooted into recovery and made an image, backup up everything, just in case. Rebooted and went in the SU Superuser application that Chainfire originally installed and uninstalled through the settings in the program. Once I rebooted I was able to encrypt the device (without fast method), I already had my SD Card encrypted. Once I encrypted the device I downloaded Kingo Root at the advice of DesignGears and used the one click root application from the Kingo Root site (google it.) After I did that, I now have full root access back, encryption, and never had to uninstall the region lock, so I didn't lose phone connectivity, applications, or anything else during the process. I recommend using TitaniumBackup and syncing via Google Drive or Dropbox before you start the process so you can restore your apps and data, once again, just in case.

encrypted ATT Note 3 not able to root
I was able to unroot my ATT Note 3 and then encrypted it. But Kingo Root failed to root the device. (I used it to root the phone once previously)
Now I stuck in a status with encrypted phone not able to root anymore.
Any suggestions please?
GHolbrook4 said:
I'm an AT&T customer, but I bought a T Mobile Note 3 off of Craigslist, unlocked it, rooted using Chainfire's ODIN thread, and then used the RegionFree Lock Away app. I was unable to encrypt just like you guys until I did the following. Flashed TWRP tar file from the TWRP site using ODIN. Rebooted into recovery and made an image, backup up everything, just in case. Rebooted and went in the SU Superuser application that Chainfire originally installed and uninstalled through the settings in the program. Once I rebooted I was able to encrypt the device (without fast method), I already had my SD Card encrypted. Once I encrypted the device I downloaded Kingo Root at the advice of DesignGears and used the one click root application from the Kingo Root site (google it.) After I did that, I now have full root access back, encryption, and never had to uninstall the region lock, so I didn't lose phone connectivity, applications, or anything else during the process. I recommend using TitaniumBackup and syncing via Google Drive or Dropbox before you start the process so you can restore your apps and data, once again, just in case.
Click to expand...
Click to collapse

I was able to get mine to encrypt after killing the bloat apps. All Google sync, amazon, and Verizon services. I can't say which one was killing it since it stopped pretty much every app or service that wasn't critical to the device.

Can anyone confirm that Encryption will never work once we root our phone ?

nlatifolia said:
Can anyone confirm that Encryption will never work once we root our phone ?
Click to expand...
Click to collapse
Same question here... Anyone was able to encrypt after being rooted???

Same question, rooted can't encrypt.

Just got a note 3 and this is an old thread. So wanted to update this question.
To encrypt device after root all that is needed to do is run the following command from terminal or adb shell as root. You must have the latest busybox installed.
pkill -KILL daemonsu
After running this command you should be back at the "$" prompt and out of root. Do not run su again.
Then encrypt your device. Encryption should work fine. Once rebooted you will have root again.
I had to repeat the above steps because I ran su again. Running su restarts daemonsu.
Good luck

Hi,
I was able to root and encrypt my sm-n900 note3 using the steps mentioned on this post:
http://forum.xda-developers.com/showthread.php?t=2791587
Just make sure that you have your backups ready case something goes wrong
I've installed the bloatwares after rooting and encrypt.

[Q] Help troubleshooting 0x1117008 with latest OTA update

Hi folks,
I've got a Verizon LG G2, and I've performed the following tweaks:
- Disabled a few unneeded services (e.g. verizon location agent, sync service, etc. using the built-in android capability
- Rooted via "ioroot" technique
- Installed ClockWorkmod Superuser app (for some reason the ioroot app wasn't prompting before allowing root)
- Backed up and then uninstalled extra cruft using Titanium Backup.
Lately I noticed that there's an OTA update available. However, when I try to install it, it reboots and eventually gives me a 0x1117008 error. Through a little bit of searching, I concluded that 0x1117008 was perhaps an error indicating that the device had been rooted. And sure enough, the Status section in About Phone did indicate "rooted" in Rooting Status.
Through using Voodoo OTA Rootkeeper, I was able to un-root the phone. I also removed other traces of the SuperUser apk and used the "forel.lee" trick to reset the "Rooting Status" property back to "unrooted". However even after all of this, the update failed with 0x1117008. "Rooting Status" still shows "unrooted" after the failed update, too. So my next strategy was to restore the bundled cruft apps via Titanium Backup, and re-enable the unneeded services (and subsequently performing the root removal steps). And sure enough, 0x1117008 once again.
My questions at this point are:
- Is 0x1117008 really because the error detected that the device was rooted? Or is it perhaps some generic message that could mean multiple things?
- If 0x1117008 is indeed because root was detected, does that imply that the update process does a different/more-thorough check for a device having been rooted? And if so, what indicators of having been rooted might I be missing? e.g., could it even be going as far as detecting the presence of apps such as Titanium Backup Root as indication of being rooted?
- Other posts indicate that a way to get the OTA update working is to do a factory reset and then upgrade from there. But that'd blow out all of my data such as text messages and app-specific stuff, right?
Any questions or suggestions on how to proceed would be greatly appreciated. I'm not overly concerned about this incremental upgrade, but my fear is that when the KitKat update eventually comes out, I'll be in the same boat. Worst case scenario, I suppose a factory reset combined with the same steps that I used to migrate data from my old phone (Google online backup, SMS Backup & Restore, etc.) might allow me to do it. But that was a headache I'd like to avoid if at all possible.
Thanks!

d3leted

Well, I tried doing a factory reset, and it still resulted in a 0x1117008 error on attempting to install the OTA update! It wasn't really straightforward, but here's what I did to get the phone updated:
Create Titanium Backup Root backup
Create SMS Backup & Restore backup
Via adb shell, make a tarball of all of /sdcard
Get a copy of that tarball via adb pull
Do factory reset. This will clear everything in /sdcard!
Remove evidence of root
Use LG Mobile Support Tool to get latest ROM. I can't link to it, but google for B2CAppSetup.exe The option to update the software is available via a menu option. It's about 2GB and takes a while to download.
Re-root (ioroot 1.7)
adb push sdcard tarball back on device
Extract sdcard tarball via adb shell
Restore messages via SMS Backup & Restore
I had unchecked the option to have Google back up my apps during one of my factory resets, and this apparently deleted my online backups. So my app restores were manually via Titanium Backup
It's possible that this upgrade may have succeeded without doing a factory reset, which would have made things much easier. Also, I did note that during the Firmware Update process, it said "UNROOTED" on the screen. It's not clear if it would have succeeded if it were detected as rooted.
Edit: It appears that SMS Backup & Restore is redundant, as Titanium Backup can restore SMS messages. And Contacts as well. (I have a number of non-google-synced contacts)

forrestgump2000 said:
Well, I tried doing a factory reset, and it still resulted in a 0x1117008 error on attempting to install the OTA update! It wasn't really straightforward, but here's what I did to get the phone updated:
Create Titanium Backup Root backup
Create SMS Backup & Restore backup
Via adb shell, make a tarball of all of /sdcard
Get a copy of that tarball via adb pull
Do factory reset. This will clear everything in /sdcard!
Remove evidence of root
Use LG Mobile Support Tool to get latest ROM. I can't link to it, but google for B2CAppSetup.exe The option to update the software is available via a menu option. It's about 2GB and takes a while to download.
Re-root (ioroot 1.7)
adb push sdcard tarball back on device
Extract sdcard tarball via adb shell
Restore messages via SMS Backup & Restore
I had unchecked the option to have Google back up my apps during one of my factory resets, and this apparently deleted my online backups. So my app restores were manually via Titanium Backup
It's possible that this upgrade may have succeeded without doing a factory reset, which would have made things much easier. Also, I did note that during the Firmware Update process, it said "UNROOTED" on the screen. It's not clear if it would have succeeded if it were detected as rooted.
Edit: It appears that SMS Backup & Restore is redundant, as Titanium Backup can restore SMS messages. And Contacts as well. (I have a number of non-google-synced contacts)
Click to expand...
Click to collapse
I'm getting the same error... do you have any suggestions on how to get the update applied without the full reset? Thanks.
Edit: LG Support Tool finally worked to complete the update.

Encounter the same error while doing ota update. G2 rooted.
trickskevry said:
I'm getting the same error... do you have any suggestions on how to get the update applied without the full reset? Thanks.
Edit: LG Support Tool finally worked to complete the update.
Click to expand...
Click to collapse
I encounter the same problem here while updating via OTA. Please guide me. Did u do factory reset using LG Support Tool or did u simply update kitkat via PC Suite? Will it also encounter the same error when using the latter method?

Anyone Helping with This???
dhs.sun said:
I encounter the same problem here while updating via OTA. Please guide me. Did u do factory reset using LG Support Tool or did u simply update kitkat via PC Suite? Will it also encounter the same error when using the latter method?
Click to expand...
Click to collapse
I have the same problem, I have not seen anyone with help for us???

Reviving an old thread. I'm getting the same error with the Latest January 2015 update. Rooted with towel root. Stock ROM, no frozen apps. My Wife's stock unrooted G2 updated fine.
David

Same error here. Rooted with Towel Root and stock rom. Wifi hotspot mod is about the only thing I've done with the root. Wondering if reverting the hotspot mod will allow it to update.