Database Info

settings.db and settings.db.backup. . . .i screwed up.

I searched for anything similar before I posted here, however I doubt anyone else was dumb enough to do what I did.
Long story short I got a replacement phone because of the random lockup issues. I agreed to keep this one at stock JF6 for a couple of weeks to appease the manager at my local AT&T store. He said nothing about me rooting it though
Everything works fine, great even. I still love this phone even without Froyo, but I stupidly deleted settings.db and settings.db.backup.
How the heck am I to sideload if I don't have the file to edit?! Again, the phone works fine without the files there at all. . .
Thank you in advance.

It works fine? Have you rebooted the phone at all? There is a lot more than just side loading settings in that db file. If you haven't rebooted, my guess is that everything was saved in memory and being run that way. However, you may be in for a serious problem should a reboot occur.
Anyone have some thoughts on a solution? Would posting another settings.db work for him or are they very device specific?

Settings DB has some device specific settings. The only recourse is to do a Flash back to stock if you deleted system files.
Rooting the phone is not keeping it stock as rooting is making changes to files. Deleting and or modding settings.db is also not keeping it stock... so you really didn't honor the managers request.
You can always sideload a non-rooted phone using ADB or side load wonder machine.

Yeah, I went ahead and bit the bullet and rebooted it. It's fine, absolutely fine, strangely.
The manager only asked that I not replace the O.S. with say, 2.2 so I can have flash and other specs I bought this phone for. Regardless of the issues with AT&T and Samsung, I want what I paid full price for as a consumer.
That being said, rooting for one click lag fix is all that was done to this phone other than deleting a little bloatware. All of this went fine.
The problem lies in my dumbness being allowed to have two identical phones in each hand and trying to clear off the old phones files before sending it back to AT&T. I had a memory lapse and when I snapped to I was deleting on the wrong phone. Nothing suspicious, no mal intent. Just stupid human error.
I, like trekie, have been wondering if I can just use a stock setting.db and edit it to match whatever it needs to match on my phone. I do not remember what all lies in the file.
Because the phone is ok, my guess is it reads from settings.db for changes. If there are no changes, the programs that relied on settings.db just go on as they are. If there is no settings.db, the program just continues on with the values last obtained from said database.
Thoughts?

My guess. Slap on the odin and get that thing back to its out-of-the-box configuration. Good luck!

Thanks, I'm deffinately not waiting around for my froyo update from AT&T just because the Vibrant is getting it lol!

[Q] Inspire thinks it's in a car dock with non-Inspire based kernels

Now, from what I can gather, this problem stems from a faulty or dirty Micro-USB port. I tried compressed air, but it did nothing for me.
I decided to do a complete unroot, S-ON, factory restore and call HTC to see if I could get it fixed. To my surprise, the problem vanished. Thinking I had lucked out and that fixed it, I re-rooted the phone and the problem still didn't reappear.
Then, thinking I would start small, I flashed a Sense kernel. As soon as I rebooted it went straight to Car Home and began answering in speakerphone. For laughs I went ahead and flashed MIUI then CM7, both of which exhibited the same behavior.
After all of this, I got to wondering just why the stock ROM and kernel worked but nothing third party would. Then it hit me that all the 3rd party stuff I had been using were DHD ports, and not based off the Inspire. I downloaded and flashed ClearDroid, which has an Inspire base, and the problem is once again dormant.
The only sense I can make from it is that HTC has implemented some kind of fix for shoddy USB ports in the Inspire kernel.
So now here's the question: Does anybody know anything about this, and would it be possible to implement said fix in, say, and AOSP kernel?

When you flash a Rom there is a folder created called data on the root of your phone. This contains many files that control various settings on your phone. There is a file in particular where cardock settings get synced in data/data/Com.android.providers.settings/databases/settings.db. When you sign in with your google account some of these settings get restored to the mode in which you had it in when you wiped your phone. This is what causes some people to think that parts of their old Rom are bugging out their phone, I guess in a way it is, but its googles fault. The car dock is getting resynced to being on even though you haven't done anything. In order to fix it you must use SQL editor to open the database and look for the carmode or dock settings and set them back to 0. Once you do this it the next time the phone autosyncs it will save your newer settings.

Also Im pretty sure when your rooted this setting will take effect as to where a nonrooted phone doesn't allow the permission to execute the command.

Gizmoe said:
When you flash a Rom there is a folder created called data on the root of your phone. This contains many files that control various settings on your phone. There is a file in particular where cardock settings get synced in data/data/Com.android.providers.settings/databases/settings.db. When you sign in with your google account some of these settings get restored to the mode in which you had it in when you wiped your phone. This is what causes some people to think that parts of their old Rom are bugging out their phone, I guess in a way it is, but its googles fault. The car dock is getting resynced to being on even though you haven't done anything. In order to fix it you must use SQL editor to open the database and look for the carmode or dock settings and set them back to 0. Once you do this it the next time the phone autosyncs it will save your newer settings.
Click to expand...
Click to collapse
I'll try that, but I can completely wipe my phone (cache, system, data, d-cache), flash CM 7.1.0, and without even logging into my Google account it happens.

After searching it seems this is a common problem with the phone. Some people where able to fix it and some where not. Even when it does go away for a while it will re emerge and get worse.
Some of the fixes are
1. turning airplane mode on for 10 min and then shutting it off
2. Changing chargers(dont ask me)
3. Blowing out port which you said you tried.
I am still not 100% its not some internal issue but why even bother if the hardware is malfunctioning.
I would start the warranty process and get it replaced.

Backing up to the beginning.....Are you flashing ROMs or kernels? Seems to me you are flashing ROMs but keep using the word kernel.
Why not just remove the car dock app from the ROM or use Titanium Backup to freeze it?

Agoattamer said:
Backing up to the beginning.....Are you flashing ROMs or kernels? Seems to me you are flashing ROMs but keep using the word kernel.
Why not just remove the car dock app from the ROM or use Titanium Backup to freeze it?
Click to expand...
Click to collapse
Both.
With the stock ROM and kernel, everything is fine. With the stock ROM and a DHD-based kernel it happens. With any AOSP ROM it happens.
Removing the Car Dock app keeps it from launching, but the phone still defaults to speakerphone for all calls (incoming and outgoing).

Gizmoe said:
After searching it seems this is a common problem with the phone. Some people where able to fix it and some where not. Even when it does go away for a while it will re emerge and get worse.
Some of the fixes are
1. turning airplane mode on for 10 min and then shutting it off
2. Changing chargers(dont ask me)
3. Blowing out port which you said you tried.
I am still not 100% its not some internal issue but why even bother if the hardware is malfunctioning.
I would start the warranty process and get it replaced.
Click to expand...
Click to collapse
The problem about warrantying it is when it's in a stock state, it works fine.
I've never dealt with HTC, but I can't exactly see it going over well if I call up and say "My phone acts funky when I run CyanogenMod".
The airplane mode fix is something I haven't heard before. I guess I'll give it a go.

[Q/A][Discussion] NEC Terrain general discussion

Hello!
This is a discussion thread for NEC Terrain.
The hardcore steps, which are bootloader unlock, rooting and even repartitioning have found their solutions and can be found in:
http://forum.xda-developers.com/show....php?t=2515602 for the discussion
https://github.com/x29a/nec_terrain_root for an apk which opens for you an ability to have the system area of the phone writeable
https://github.com/alex-kas/nec_terrain for the last ideas on how recovery and boot images should be and a list of stock apps to disable with explanations
So, all questions regarding all the above should be asked in that thread as they are off-topic here.
Currently we have to use this device with its stock components. You are welcome to contribute with workaround related to known oddities here.
Note that many questions were already asked in the above mentioned thread and some of them have answers. However, since that thread is supposed to for the rooting/unlocking, it is more than logic to separate the topics and discuss the end-user phone features here.
If you have a serious idea towards a new custom ROM then you should go here
http://forum.xda-developers.com/android/software-hacking/rom-nec-terrain-custom-rom-t3162061
That thread is dedicated for the developers of a new csutom ROM for NEC Terrain
Thanks for understanding the thread aim and welcome!

First exploration
You can find apps which can be disabled with some explanation why in
https://github.com/alex-kas/nec_terrain/tree/master/system
The speciall account should be paid to the following issues:
Why stock Contacts and Phone must not be disabled
Why apps with provider in their name should treated carefully
Current impossibility to activate a soft keyboard (if you need chinese, for example).
The latter question of a soft-keyboard for this phone has been asked before in
http://forum.xda-developers.com/show....php?t=2806270
and has no answer. There is further discussion on this in my github (see above)
On more oddity which at least my phone has: when I travers to
Settings->wrieless & networks->more...->Mobile networks
I see as the last option "network operators". This option i constantly greyed out. It is useful in roaming as often different orpeators have different prices. Also, near the borders of a country som eforeignn operators can be captured. This is bad. Anyone with ideas on this?

i was wondering if someone with a fully functional Terrain upload their /system/app folder and its contents, I've seemed to remove an essential app somewhere and now I can't do phone calls or terrain hotspot.

Daxiongmao87 said:
i was wondering if someone with a fully functional Terrain upload their /system/app folder and its contents, I've seemed to remove an essential app somewhere and now I can't do phone calls or terrain hotspot.
Click to expand...
Click to collapse
I can do this tomorrow. I am able to phone call, hotspot, etc. I've noticed that with me, sometimes the phone UI won't show up when someone calls me so I cannot answer the phone... If this happens, just do a Wipe Data on the phone apk and reboot.
Sent from my LG-D415 using XDA Forums

@jasonmerc much appreciated! My backup phone just isn't cutting it for me!

Daxiongmao87 said:
@jasonmerc much appreciated! My backup phone just isn't cutting it for me!
Click to expand...
Click to collapse
No problem man . Just curious, what is your backup phone?
Sent from my LG-D415 using XDA

My nieces phone for her upcoming birthday. The excuse I'm making to myself is that I'm "test driving" it. It's called the Xperia Tipo, she's only 9 and would be using it at more or less a little toy; no SIM card. I have better ones actually, HTC One and a Moto X (2013), the latter being my favorite phone without a hardware keyboard.

I'm wondering about 2 questions, guys:
1. @Daxiongmao87, what is the hotspot you are talking about?
2. @jasonmerc, can you provide to me the list of your apps, enabled and disabled? Or, if you just uninstalled them (so no disabled) then only enabled.
I want to see the list given in adb shell by
pm list packages -e -f [for ENabled with file-names]
pm list packages -d -f [for DISabled with file-names]
I'm curious about this can/cannot do phone calls. I had established some dependence but you have said you CAN do calls with attsettingsprovider disabled and even see contacts. Very strange to me and I want to find the truth I.e. Can I or not eventually get rid of stock contacts at all.
Thanks in advance.

@alex-kas hotspot meaning wireless tethering. There's a system app with the package name containing hotspot. I believe jasonmerc already provided me with that earlier along with the phone apk, but ultimately did not help fix my issue. My symptom for the two issues are as follows:
Wifi Hotspot (Tethering)
-Under the Tethering & portable hotspot menu, toggling Portable Wi-Fi hotspot reveals a subtext that reads "Failed to set transmit power"
Phone Calls
-My phone no longer notifies me whether or not I have a SIM card. No icon or any indicator at all. My signal icon always shows zero bars. attempting to make a phone causes Contacts to crash ("Unfortunately, Contact has stopped.") and haults the phone call process.
I hope this information helps a little bit. More than likely i'm missing a vital app that I carelessly removed upon tinkering.

Daxiongmao87 said:
@alex-kas hotspot meaning wireless tethering. There's a system app with the package name containing hotspot. I believe jasonmerc already provided me with that earlier along with the phone apk, but ultimately did not help fix my issue. My symptom for the two issues are as follows:
Wifi Hotspot (Tethering)
-Under the Tethering & portable hotspot menu, toggling Portable Wi-Fi hotspot reveals a subtext that reads "Failed to set transmit power"
Phone Calls
-My phone no longer notifies me whether or not I have a SIM card. No icon or any indicator at all. My signal icon always shows zero bars. attempting to make a phone causes Contacts to crash ("Unfortunately, Contact has stopped.") and haults the phone call process.
I hope this information helps a little bit. More than likely i'm missing a vital app that I carelessly removed upon tinkering.
Click to expand...
Click to collapse
Have you read my github?
https://github.com/alex-kas/nec_terrain/tree/master/system
If not, try to see there. I spent quite a time and I'm sure my phone IS working in both aspects you mention. Pay attention to: contacts, phone, attsettingsprovider and installation of "dw contacts". All of that is by purpose. Perhaps, my phone would not work w/o "dw contacts" but I just learned that a replacement (which joins phone app and contacts app, which are disintegrated once you remove attsettingsprovider) MUST be.
You will find there files: lists of enabled and disabled programs. Compare with yours. In adb shell:
pm list packages -d [gives disabled packages] -s [if only system]
pm list packages -e [gives enabled packages, all, system and 3-rd party] -s [if only system]
My lists contain ONLY system apps. 'system' are those who reside in /system/apk OR in /data but are upgrades to initial system apps. Hope this helps. If you have put there superuser - it is system now, for example.
I can also imagine that moving some app to sdcard makes the system buggy. I had no full skype autostart then it was moved.
hotspot in the name does NOTHING with tethering.

@alex-kas you should have a full list of apps I have installed already, I PM'd you a list a while back. About to do the /system/app dump, most likely I'll package it as a zip or 7z file and upload and share from Google Drive.
Also as a little update, I mentioned the GPL stuff in my ATT thread. Waiting for a response
Sent from my LG-D415 using XDA

Here's the contents of my /system/app folder. Apparently I don't have ATTSettingsProvider.apk, BUT I still have ATTSettingsProvider.odex if that makes a difference.
https://drive.google.com/file/d/0BxupjEjigG4taFZhWXl3RjVULTA/view?usp=sharing

alex-kas said:
Have you read my github?
https://github.com/alex-kas/nec_terrain/tree/master/system
If not, try to see there. I spent quite a time and I'm sure my phone IS working in both aspects you mention. Pay attention to: contacts, phone, attsettingsprovider and installation of "dw contacts". All of that is by purpose. Perhaps, my phone would not work w/o "dw contacts" but I just learned that a replacement (which joins phone app and contacts app, which are disintegrated once you remove attsettingsprovider) MUST be.
You will find there files: lists of enabled and disabled programs. Compare with yours. In adb shell:
pm list packages -d [gives disabled packages] -s [if only system]
pm list packages -e [gives enabled packages, all, system and 3-rd party] -s [if only system]
My lists contain ONLY system apps. 'system' are those who reside in /system/apk OR in /data but are upgrades to initial system apps. Hope this helps. If you have put there superuser - it is system now, for example.
I can also imagine that moving some app to sdcard makes the system buggy. I had no full skype autostart then it was moved.
hotspot in the name does NOTHING with tethering.
Click to expand...
Click to collapse
http://pastebin.com/1yRtvVhz
Thank you for your assist!!
And @jasonmerc thanks a bunch!! Giving it a shot now
EDIT: back online with wifi tethering and cell network thanks again guys
Edit 2: By the way, has anyone experienced unexpected reboots during high RAM usage? Games for example?
Sent from my NEC-NE-201A1A using XDA Free mobile app

@alex-kas after successfully applying your custom recovery and resizing my partitions i seemed to have lost my boot animation and sound. It just shows a black screen. Is this intended? Perhaps with the new build.prop?

Yeap, i disabled bootanimation. It seems to increase the boottime even more.
Sent on the go

Yes, I've experienced reboots when doing multiple things. For me it's usually just watching a video or something... Perhaps it overheats and that's what causes the reboot. On average my Terrain's CPU is somewhere in the 120°F range, and if I use it it can go up to 145°F at times. It will sometimes even get so hot that I get a notification stating the device is too hot to continue charging, and I need to try charging again in a few minutes. Is this normal?
Sent from my LG-D415 using XDA

jasonmerc said:
Yes, I've experienced reboots when doing multiple things. For me it's usually just watching a video or something... Perhaps it overheats and that's what causes the reboot. On average my Terrain's CPU is somewhere in the 120°F range, and if I use it it can go up to 145°F at times. It will sometimes even get so hot that I get a notification stating the device is too hot to continue charging, and I need to try charging again in a few minutes. Is this normal?
Sent from my LG-D415 using XDA
Click to expand...
Click to collapse
Hmm I thought I replied to this. I experience overheats as well, but mostly when using maps. However, I haven't been able to see a correlation between reboots and overheating. I have a feeling that when available memory gets too low the system becomes unstable and inevitably reboots. With the new partition size I was able to install hearthstone without any need for apps like Link2SD, but upon loading all of its assets to start an actual game session it reboots every single time. When not attempting to play that game, during times where the phone feels sluggish or unresponsive, it often follows with a reboot.

Daxiongmao87 said:
Hmm I thought I replied to this. I experience overheats as well, but mostly when using maps. However, I haven't been able to see a correlation between reboots and overheating. I have a feeling that when available memory gets too low the system becomes unstable and inevitably reboots. With the new partition size I was able to install hearthstone without any need for apps like Link2SD, but upon loading all of its assets to start an actual game session it reboots every single time. When not attempting to play that game, during times where the phone feels sluggish or unresponsive, it often follows with a reboot.
Click to expand...
Click to collapse
This is exactly what I have denoted as the kernel bug, see
http://forum.xda-developers.com/showpost.php?p=61915007&postcount=293
In addition to the info there: reboots happen if several not so big files (say, 50MiB each) are read in a row, not just a single file of > 500MiB. Loading a large set of game assets just confirms this.
I traced this bug and the point is that its origin is a mystery to me. It is in a part which I would never imagine was changed from the linux source. Just no need for this.
In short, the ext2,3,4 driver, reading data, then caches them (linux always caches, all it reads, as much as possible). At some point the cache request to allocate the memory just ignores the negative answer (i.e. no memory), it just does not check this answer at all and caches to NULL, i.e. start of the memory, where the memory map is. As it is the kernel, it has right to write there, writes, kernel panics - reboot.
How come? I have no idea. This code was already working in about 2005 ... and bug-free in about 2008 ...

@alex-kas you get what you pay for I guess...
Sent from my LG-D415 using XDA

jasonmerc said:
@alex-kas you get what you pay for I guess...
Sent from my LG-D415 using XDA
Click to expand...
Click to collapse
What exactly you mean? The phone is not that cheap. If new. Especially from att.

Honor 6 L04 issues with the Lollipop update

After downloading and flashing the official B521 update, sure there was no usable keyboard app, so I had to voice search to a 3rd party site to download one, but other than that all was well... or so I thought. I happened to switch my phone's mobile data setting to 3G only, during a spot of bad reception (the constant switching made it impossible to do anything), after which I realised that this update had removed all the LTE options from the dropdown menu.
My first instinct was to go to the "project act menu" from the dialler, but that would not load at all, when typed in correctly and confirmed...the phone just clears the number input area and doesn't open any menu. At this point, I did not know how I was going to sort out the issue, I thought maybe a .prop or .db file would be the answer. I have edited such files on other phones to do a number of things, should be simple right? Boy was I wrong.
Before beginning to poke around I did some searches of course, and found that you can get the 4G options back, by editing a value in the /data/data/com.android.providers.settings/databases/settings.db ...So I unlocked my bootloader, rooted, and did just that. Put the file back in place, swell, guess I'll reboot. Then it froze on the Honor logo, impossible to turn off, with good timing--I was able to access the stock recovery and fastboot modes.
Since then I have been able to get my phone to boot by deleting the settings.db, so that Android created a new one, only problem is... this new file of course has so much hardware specific things missing from it...It's kind of a joke. All I wanted to do was allow myself to freely switch between 4G and 3G on the Lollipop update, and in trying to do so, bricked the device and had to lose all the stock settings in order to get it working again.
I changed the permissions and ownership of my edited settings.db (as best as I could in root explorer) after replacing it, but nothing seems to help as far as I can tell, if the settings stay I cannot boot.
How exactly am I meant to get the original database back? I assume if I can downgrade to the Kitkat, that will sort that side out, but even if I do that...and then reflash Lollipop... I'm still going to be losing the 4G option, unless I never change it from auto--ever.
This is just silly and frustrating... Literally all I want is the official settings.db for this phone on lollipop aside from: the network modes changed so that I can switch between 2G/3G/4G, 3G only, and 4G only modes. I cannot for the life of me figure out how to do this on my own, and I wish I made a backup before trying...
Please help, thanks~

Getting an OTA update after installing TWRP and rooting OR use RUU?

I have an HTC One E8... I know, it's ancient... But... It's been a good phone until this past year when it really started dragging. Takes forever to do anything. A year ago, the main camera (is that the front or back camera) stopped working (phone doesn't even recognize that it's there -- flash doesn't work either with a flashlight app). Before that, phone dialing using my Bluetooth earpiece stopped working. Maybe related, but the phone doesn't work as a phone (holding it to your ear). If I'm not using the Bluetooth earpiece, it will only work on Speaker-phone mode (voice command apps such as Google Assistant and song recognition apps like Sound Hound don't 'hear' anything). Lastly, the Bluetooth has been disconnecting for no apparent reason. My earpiece will say 'Phone 1 disconnected', but when I look at the Bluetooth icon on the phone, it still thinks it's connected. Tapping the icon to turn off Bluetooth and then tapping again 'fixes' the problem and it connects again. It's just annoying when it does this in the middle of a conversation (and because, when it happens, the other party doesn't hear me yelling at them to wait because my Bluetooth disconnected because the phone doesn't know that anything is wrong). I had read ones that the Bluetooth drivers for this phone were sketchy. It's strange, though, this this problem has really gotten worse over the past couple of months without me making any changes to the phone. Lastly, the battery has really gone downhill. The phone will unexpectedly shut off around 30% battery. (I even tried the HTC battery recalibration technique -- no joy.) I chalked all of this up (except for the battery issue) to software. I thought maybe a good ol' factory reset (wipe) would fix the issues. For years (literally) it's been nagging me about a system update (Android 6.0). I never did it because the phone was already running slow and it's always screaming about being out of storage space. It hovers around 500MB free most of the time. I don't have that much installed on it. Any apps that will allow it, have been moved to the SD card.
That's the back-story to give you some insight as to what's going on with the phone. I included all of that 'other' stuff (camera and voice dialing issues) in case someone has seen them before and can offer any suggestions there.
So here's where I'm at. I decided to try to do a factory reset to 'refresh' the OS (remove all the patches and updates) and start over. Afterwards, I wanted to run Link2SD with a 64GB SD card so I wouldn't have the space limitations that I'm experiencing now after all of the apps have updated. The other night, after backing up the internal memory and the SD card, I started the process. (BTW, I have another SD card that I'm going to use that I've already partitioned per the Link2SD instructions.) After much trial and error, dead download links, incompatible versions of adb.exe and fastboot.exe I finally managed to get TWRP recovery installed. Then there was the issue of getting a working SuperSU installed. Finally did that. The phone booted and started walking me through the process of setting up my Google account. Everything seemed to go well. The phone was just as speedy as the day I got it. I was even able to restore my 15000 text messages and it was still zippy. It was wonderful! Unfortunately, the camera still doesn't work. Seems like voice dialing isn't working at the moment either. The Bluetooth issue seems to have gone away. Since the camera still isn't working, it looks like I'm gonna have to bite the bullet and get a new phone. This one will just become a 'toy' or a temporary backup phone in the event something tragic happens to the new phone. I'll just use this one on Wi-Fi only to check the weather and maybe play some games (which I had pretty much stopped doing because it was so slow and always out of storage). I would also use it as my portable media device for listening to downloaded podcasts and music while I'm running or riding my bike. It could also (maybe without mobile data) track my runs and rides, etc. As long as it doesn't get slow like it was before, I think it'll do just fine in its re-purposed life. (It was so slow I could barely play music from Google Music and have Google Fit tracking my run at the same time. It would take forever to switch screens!)
Ah, what's this?! Oh, there's that software update again. I guess I'll go ahead and do it before I start setting up a bunch of apps and tweaking the phone to my preferences. Nope! It downloads the OTA update into the Downloads folder and starts the process, but when it reboots, it reboots in Recovery mode into TWRP. I'm now finding that you can't easily do an OTA update after you've rooted your phone and put a custom recovery on it. I've seen lengthy instructions on how to put get a stock recovery.img out of the OTA zip file in the Downloads folder. I've moved it to my PC and pulled the firmware.zip file out. When I try to open the firmware.zip file to get to the recovery.img file, Windows is saying it's corrupted. I also see something about using an RUU.exe or RUU.zip file to restore the phone to stock. I've downloaded the correct RUU .exe file for my Sprint e8 in case I decide to go that route.
Here's my question... I know, finally! Since I don't have really anything on this phone since I did the reset and root, would it just be simpler to use the RUU method to blow it away and start over instead of trying to resolve the corrupt firmware.zip file issue and all of the other steps that follow? That's question #1. Question #2 is this... Will this RUU that I downloaded actually take the phone straight to Marshmallow before it starts walking me through setting up my Google account? If so, that's great! I'm all for the ease of that. I noticed that OTA download was about 250MB, while the RUU download is 1.5GB. Why such a difference? Is it because the RUU is the full-blown deal and not just the patches? I'm fine doing the RUU and then reinstalling and rooting the phone afterwards if that'll work. I still have all the files that I previously downloaded.
Sorry for the novel, but I wanted to be as thorough as possible to eliminate the back and forth "Did you try this?" "Did you try that?" However, if there is anything that I left out that would help with your answer/advice, please don't hesitate to ask. Thanks in advance for any guidance you can give a noob.
lrbarrios