I have a gtablet with CM7.03 on it. It's been working for a while. I hadn't booted it in a while and just tonight I tried to boot it. The cyanogenmod logo comes up and animates for a few minutes, then the screen goes black, the process repeats.
I'm hoping someone can give me some steps to follow to figure out what's wrong. I booted in recovery mode, but wasn't sure what to do first. Should I clear caches? Any expert advice would be appreciated. I'm a programmer, but I'm new to all this Android mod stuff.
I know this is going to sound like a really dumb question, but is it charged? The reason I ask is because you mentioned not turning it on for a while and the battery can drain even then.
If it does have a charge, the only thing I could think of would be (after wiping cache and dalvik and seeing if that works) to wipe data completely IF you have a backup/don't care about starting over.
It does have a charge. I even tried booting it with it plugged in. I just constantly sits on the animated CM7 logo, then goes black, then sits on the logo again.
When I boot to ClockWorkMod recovery, I see:
wipe cache partition
wipe Dalvik cache.
Can I do both of those without losing stuff? If someone can explain what those caches are actually used for, I would really appreciate it.
Well, I couldn't wait and cleared both. Still same problem.
The odd part is that I hadn't changed anything. I'm 99.9% sure it was working. I shut it down, left it plugged in, and then days later tried to boot it.
I can only imagine that an app is starting up on boot that's having issues. Is there a "safe" mode like windows has where I can boot with the minimum OS so I can somehow remove some apps from starting?
Thanks,
Mark
markdemich said:
I have a gtablet with CM7.03 on it. It's been working for a while. I hadn't booted it in a while and just tonight I tried to boot it. The cyanogenmod logo comes up and animates for a few minutes, then the screen goes black, the process repeats.
I'm hoping someone can give me some steps to follow to figure out what's wrong. I booted in recovery mode, but wasn't sure what to do first. Should I clear caches? Any expert advice would be appreciated. I'm a programmer, but I'm new to all this Android mod stuff.
Click to expand...
Click to collapse
What I find odd is the fact that it was running fine before you shut it down for the last time.. The only thing I can think of is there was some sort of low level data corruption before the last time you shut down..
Do you remember installing any new apps or flashing anything like a different kernel, modifying the Build.Prop or anything that may have an adverse effect to normal booting? If so, that may be the cause of your trouble. Since you have at the very least a boot sequence (with Bootloop) it doesn't appear to be a soft brick so that's some good news for you.
I can only suggest if you have a backup use it via recovery mode.
If not you could try and start over from scratch by installing a fresh copy of 7.0.3 (Be sure to Wipe Data and Cache AFTER Flashing) via recovery mode if you can get the zip file copied to your internal SDCard, I say if because with some versions of ClockworkMOD for the GTAB, it will only read from the internal SDCard and not the External SDCard.
The version of CWM I use is v.2.5.1.8 which I believe is also a play on Bekits v.8 but I'm not sure at the moment.
v.2.5.1.8 will mount the USB Storage (External SDCard)via recovery (Mounts & Storage> mount USB Storage) so you can copy the fresh zip file onto it and CWM will read from that card and not the internal SDCard.
If all else fails, you may need to try and NVFlash, which is used to restore the GTAB to its original Out of the Box Condition.. Which should only be used in the event of a Soft Brick...
Good Luck!
markdemich said:
I can only imagine that an app is starting up on boot that's having issues.
Click to expand...
Click to collapse
That and filesystem problems on /data are what I suspect.
Since you are a programmer, do this to find out what's wrong:
1. Switch off gTab.
2. Attach the USB cable to the gTab.
3. Run "adb logcat > logcat.txt" (or "adb logcat | tee logcat.txt" on Unix) on the host PC.
4. Power on gTab.
This will collect logs almost right from the beginning which might hold a clue as to what's wrong.
You might also want to read through these 2 posts:
gTab partitions
gTab SD cards
Related
Just joined to say thanks to Roebeet and everyone who is active in this forum. Because of the obvious potential of the gtablet being explored here, and discussed on phandroid.com I decided to take the plunge and purchased one tonight. I might have passed this tab by, and waited months for something else...
--and here's where I cry for help!
I carefully followed a series of step-by-step instructions I found thru google, to install the latest tnt lite found here on XDA. Everything seemed to work without a hitch, and was prouder than a pappa to have completed my first root and mod ,ever!
BUT right after I DL'ed and installed the flash 10.1 apk things went south. The browser constantly crashed to the home screen, and the market and email apps were crashing also. I rebooted and now I am greeted by the tnt setup screen that is covered in an endless wave of crash warning dialogs! I can't tap them away fast enough to see the desktop.
I've tried to do a recover, but I can't get thru the setup (that keeps crashing to the first screen also) to use the USB to mount the internal mem to my Mac.
I am insanely happy about the potential of this hardware, but I've painted myself into a corner. ANY help would be greatly appreciated.
And yes, I do look very handsome in my profile pic.
From bad to WORSE!
I discovered the dcom222 thread that describes my problem and details a solution. I followed it to the letter, changing the command and using my microSD as a secondary boot to reinstall the vanilla tnt ROM.
But then it just stuck on the tnt logo, faded in and out 3-4 times, and went dark! The device won't turn on or off (had a full charge when I pulled it from the wall socket a few moments ago)
Please tell me I haven't bricked this thing!
still no luck...
I was able to power the unit back up, but I've tried to recover and flash all three setup files I have (vanilla tnt, ota update tnt and tnt lite 2) but nothing works!
All of them create a loop of some sort, whether it's the viewsonic screen, gtablet screen loop, or the tnt logo screen blinking on and off, NOTHING boots to the desktop.
Going to bed before I drive my self insane. Hopefully someone in the know will reply by the time I check this at work.
thanks in advance
You have not bricked it, don't worry. This device is very hard to truly brick. If all else fails there is nvflash or the apx mode fallback. But I don't think you need that if you are still able to boot to clockwork recovery.
In clockwork go to advanced - mounts and try mounting and unmounting your partitions. I suspect your user partition may be screwed. This seems to happen fairly frequently especially the first time you flash a ROM. It happenend on my first flash and not again since. Clockwork lets you repartition though. Search the forum for partition fix, its not too big a deal.
If that fails try roebeet's thread on nvflash recovery for TNT lite. If that fails, search for APX mode.
As far as I know there are zero bricks from ROM flashing so far.
Sent from my SMB-A1002-3G using Tapatalk
Life in LA said:
Just joined to say thanks to Roebeet and everyone who is active in this forum. Because of the obvious potential of the gtablet being explored here, and discussed on phandroid.com I decided to take the plunge and purchased one tonight. I might have passed this tab by, and waited months for something else...
--and here's where I cry for help!
I carefully followed a series of step-by-step instructions I found thru google, to install the latest tnt lite found here on XDA. Everything seemed to work without a hitch, and was prouder than a pappa to have completed my first root and mod ,ever!
BUT right after I DL'ed and installed the flash 10.1 apk things went south. The browser constantly crashed to the home screen, and the market and email apps were crashing also. I rebooted and now I am greeted by the tnt setup screen that is covered in an endless wave of crash warning dialogs! I can't tap them away fast enough to see the desktop.
I've tried to do a recover, but I can't get thru the setup (that keeps crashing to the first screen also) to use the USB to mount the internal mem to my Mac.
I am insanely happy about the potential of this hardware, but I've painted myself into a corner. ANY help would be greatly appreciated.
And yes, I do look very handsome in my profile pic.
Click to expand...
Click to collapse
Scroll down to post number #869 http://forum.xda-developers.com/showthread.php?t=842004&page=87
feeling better
Thanks for the assurances that I didn't wreck the device, and pointing me to some solutions. I have a few questions:
what is clockwork mod? If I am able to recovery boot from my micro SD card, do I already have it? (I downloaded a bunch of recovery images to start, per instructions)
If it's something I still need to download, is it a PC application? How am I supposed to change settings in it (manage partitions, etc) if I can't get the tablet to boot?
-- stuck at work and dying to get home to fix this thing...
Ok, more detailed instructions:
If you press and hold down Volume + when you are pressing the Power button to boot up, and keep holding the Volume + key until you see a message that says "Detect a Recovery Key Pressed", that should get you to a text menu from which you can navigate using the volume +/- keys and the Home soft button to flash ZIP files and do other things. That menu is ClockworkMod Recovery. Since you remember installing a recovery.img, it sounds like you probably (hopefully) have ClockworkMod Recovery on there.
If you get to ClockwordMod Recovery, you can go down to the Mounts and Storage option, then you will find the "Mount USB storage" option at the end of that list. That lets you plug in and mount your internal memory area as a standard USB drive to your Windows or Mac computer to copy over new ZIP files and the like to your G Tablet.
You can also check that partitions are all mounting and unmounting successfully in that menu. If you go instead into the Advanced menu, you will see Partition SD Card, which I believe is what you might need to do at this point.
If booting with the Volume + button held down doesn't get you anywhere and you see nothing about Recovery Key Detected and don't see any text menu, then you don't seem to have a working recovery. At that point you'll have to do what phfaty suggested, read the post he referenced, and follow the link therein to the tegratab forum post to get the NVidia Tegra SDK installed on your Windows desktop and use the NVFlash tool and APK mode (where you hold the Volume - key down while booting instead of the Volume + key) to reflash your tablet.
still not working...
The good news:
I do have clockwork mod installed. Must have been in 1 of those zips or rars I ran in the very beginning.
The bad news:
it's still caught in a boot loop. I've mounted it as an external drive 3 times now from clockwork, and tried all 3 versions of the operating system (vanilla, vanilla with the ota and tntlite 2) and NOTHING makes a difference.
Life in LA said:
The good news:
I do have clockwork mod installed. Must have been in 1 of those zips or rars I ran in the very beginning.
The bad news:
it's still caught in a boot loop. I've mounted it as an external drive 3 times now from clockwork, and tried all 3 versions of the operating system (vanilla, vanilla with the ota and tntlite 2) and NOTHING makes a difference.
Click to expand...
Click to collapse
1)Boot into clockwork.
2)Navigate to Advanced menu
3)Choose partition sdcard
4)Choose data partition desired size(1024=1GB)
5)Choose 0GB for the next selection(swap not used)
6)Do a factory reset from main menu
7)Reboot
8)If that doesn't work, then reinstall ROM, then reboot
UPDATE
partitioning the drive and wiping the user data did the trick. I'm up and running again. thanks to all who chimed in to help.
I haven't done any flashing in about a week. Everything was working fine. And just today I ran the battery completely dry (which I usually do and it keeps my battery happy).
So I power it back up after a few mins of charging.....the LG screen comes on.....then the Ultimate 1.0 Rom loading logo comes up..after that every 10-15 seconds it turns on the screen, shuts it off, turns it on, off, etc. It keeps turning on and off...even after I left it there for 5 mins.
I'm going to flash back my Froyo stock rooted rom that I made a back up. The Ultimate 1.0 isn't the only rom I've flashed in the past. CM7 as well..many of the builds.
Argh.
I have my nandroid froyo backup on my SDcard and it says it can't find it.
This whole internal sd and external sd storage is a pain in the ass. The good old G1 days. Sigh. I went ahead with formatting the card as well and copying back the nandroid backup onto the card. Nothing.
That happened to me. I had to reset - battery pull alone wouldn't work. That phone is now on its way to T-Mobile, and its warranty replacement is going to be soon due to really bad screen bleed (affects my watching video and game play).
flexnix said:
Argh.
I have my nandroid froyo backup on my SDcard and it says it can't find it.
This whole internal sd and external sd storage is a pain in the ass. The good old G1 days. Sigh. I went ahead with formatting the card as well and copying back the nandroid backup onto the card. Nothing.
Click to expand...
Click to collapse
What was "it says" - ROM Manager?
If so, it looks for a androids on the internal SD. If you had used the easy recovery install tool, you would have been able to select internal or external to use with Recovery - NOT ROM Manager.
Based on your choice, you should be able to access you nandroid in the place you chose in RECOVERY MODE.
Since you fully drained you battery, you might want to erase battery specs in recovery, turn it off, and fully charge with it turned off for 8 hours. It is not recommended that you fully drain the battery and that may be your problem.
Then you could try wiping cache, dalvek, and format /system - and reflash your ROM. Save flashing the nandroid for last.
flexnix said:
I haven't done any flashing in about a week. Everything was working fine. And just today I ran the battery completely dry (which I usually do and it keeps my battery happy).
Click to expand...
Click to collapse
have you tried a different battery?
According to the experts at Popular Mechanics running your battery dry is very bad for it. It greatly reduces the life according to them. There was a post about it last week. There are physics involved that apply to all.
when this phone crashes and won't reboot, how do we even get into recovery without rom manager??
You need to NVflash your Recovery
EmceeGeek said:
when this phone crashes and won't reboot, how do we even get into recovery without rom manager??
Click to expand...
Click to collapse
You boot the phone holding Volume Up & Power buttons until recovery screen appears.
Recovery, if you flashed it using the NVflash tool, will be accessible by booting your phone while holding Vol Up & Power. You will go into Recovery. If you have never done this or do not get recovery its because you did not flash the Recovery onto your phone.
Basically, if all you did was download ROM Manager and start flashing the G2x you are playing with fire. You need to flash the Recovery onto the phone using NVflash tool. ( Follow Step2 in the following link: http://forum.xda-developers.com/showthread.php?t=1060715 )
I would recommend anyone with the same problem or the same question to go thru the link above and you will find answers to most of your problems.
EmceeGeek said:
when this phone crashes and won't reboot, how do we even get into recovery without rom manager??
Click to expand...
Click to collapse
You need to properly install Clockworkmod recovery with NVflash. Its a process but well worth it. Rom manager is a no no with out phones.
flexnix said:
You need to properly install Clockworkmod recovery with NVflash. Its a process but well worth it. Rom manager is a no no with out phones.
Click to expand...
Click to collapse
Did you rename your nandroid backup?
If you did that would be the problem. if you want to rename it, don't leave any spaces.
Sent from my G2x
Greetings:
Today, I thought I'd make an attempt to root my phone and put on Cyanogenmod 7 on it. Right now, the screen is stuck with the LG logo and a blue glow next to the logo. I have to do a battery pull to kill it.
I've done the following, all on OS X:
1. Installed the Android SDK and did the "adb devices" command; it was found; also, enabled USB debugging.
2. Loaded flash recovery using Clockworkmod via the VirtualBox instructions on XDA (flash-clockworkmod-recovery.sh).
3. Used Clockworkmod to install the CM7 zip (did the required wipes).
I have conflicting instructions where one mentioned that the reboot after the CM 7 install was supposed to be automatic, and another that said do it manually. I had to go the manual route because when I chose reboot, the screen went black but did not boot up. I had to manually turn on the phone, but I'm not getting any farther than the LG screen.
I know something went amok; I'm hoping that it's just a small thing I might be missing. Please advise.
Thanks!
Velanche
Did you do a full wipe in clockworkmod recovery before flashing CM7? If not go back into clockwork recovery and wipe all user data. Do it a couple of times for good measure. Go under advanced and also wipe dalvik cache. Then also under advanced select fix permissions. Now reboot and be patient. It may take several minutes to boot up the first time.
Thanks a lot for the reply!
I've done the above. But I have a question about the reboot. When I've chosen it in clockworkmod, the screen went black. I take it that means that it's not working correctly? I can do a battery pull and try again in a few minutes to see if it'll work, too.
V.
velanche said:
Thanks a lot for the reply!
I've done the above. But I have a question about the reboot. When I've chosen it in clockworkmod, the screen went black. I take it that means that it's not working correctly? I can do a battery pull and try again in a few minutes to see if it'll work, too.
V.
Click to expand...
Click to collapse
Mine does that sometimes too -- doesn't actually reboot even though I select reboot. Its like it just shuts down instead. I just power the phone back on like normal and wait for it to boot up all the way.
Well it's been about 10 minutes since I've powered up the phone, and other than that faint navy blue glow next to the circle of the icon, I'm not sure if anything is happening. For sure, I didn't see the blue horizontal progress bar at all.
Should I try the whole process again, or is there something else I should check on beforehand?
V.
velanche said:
Well it's been about 10 minutes since I've powered up the phone, and other than that faint navy blue glow next to the circle of the icon, I'm not sure if anything is happening. For sure, I didn't see the blue horizontal progress bar at all.
Should I try the whole process again, or is there something else I should check on beforehand?
V.
Click to expand...
Click to collapse
My next step would be to just try flashing again: Wipe all user data, wipe dalvik cache, flash CM7, flash the latest gapps if u want, fix permissions, and then reboot.
I tried the above; still no change.
I have a feeling I'm missing something, but don't know at the moment how to work backwards.
Yea it should work. Not sure why its not. If you can boot into recovery, wipe, flash the CM7 zip, reboot, that really should be it. Works every time for me. Maybe your download is corrupt and needs to be downloaded again? I'm just making a guess.
How long did you end up waiting once you rebooted and were stuck with the LG logo? Did it ever get to the CM7 logo with the blue/cyan android on the skateboard?
I tried once more. This time though, I may have hit a major snag. I'm unable to start up my phone, at all. I tried powering it with the adapter, and I tried charing the battery. I press the power button, and I press both the power and vol down buttons...I think it's been bricked. I'm at a standstill, at this stage.
My phone's not dead, after all. Somehow, it came back to life.
1. I can boot into clockworkmod via the top power/side vol down combo that gets me the Android splash screen before the amber text.
2. After following your instructions and suggestions, I have to battery pull and power on to get the LG screen. To answer your question, once I power on the LG logo flashes after a few seconds, then reappears and stops. I'd waited as long as 10 minutes before pulling the battery.
3. No sign of the CM7 logo.
Hope this helps. BTW, I wouldn't know how to get my g2x to be recognized on my computer, except for using clockworkmod to mount the SD card.
Thanks!
V.
Ok be prepared, this post may be rather long winded however I will try my best to prevent that. I have a Tmobile G2x I purchased on launch date. Ive not attempted to Root, change roms, or anything of the sort. (as much as I always wanted to, I always felt that my skills were not good enough to attempt these ideas no matter how easy they may seem. I just did not want to be the cause of screwing up my phone that I paid dearly for)
So I have a friend who claims to be the master (of disaster so it turns out) of rooting androids and such. He stops by my house just to hang out and eventualy convinces me to let him root my phone and install CM7. Within a few minutes the phone was rooted (super1click) and was running CM7 release candidate. (I really dont know what all these things truly are but I drilled him for answers once he jacked up my phone and left me with a half-bricked phone) So he installed Rom manager and convinced me to upgrade to the premium version via marketplace so I did. He was then showing me how easy it was to flash new roms at the touch of a few buttons. He put on some other rom which looked like CM7 but claimed to have extra tweaks. It worked fine. A few minutes later he put on some Faux Rom which gave a boot up screen like my old Nexus One did. (Multicolored X) It seemed to work fine as well. Then he said lets check out the nightly CM7 Rom so he put it on. (however I dont think it ever actually put CM7 back on.-still on Faux?) Thats when things got crazy.
Now I get the com.google.process.gapps force close message all the time. He tried to fix it for 4 hours and finally gave up. Here is what I know he/we tried: After searching the internet for hours we tried everyone elses ideas. Clearing calenders cashes, un syncing, etc. We did about 40 factory resets. We have tried to install my backup (which was from BEFORE he even touched my phone) and upon holding both volume rockers and plugging in USB (no battery installed) and it still does nothing. Windows recognizes device but phone screen stays black. Tried Debug mode while doing this as well. If we hold the volume down button and power the little install bar comes on the screen and it does its thing (whatever that is) and goes right back to the way it was. I keep getting the gapps message all the time. After factory reset I cant even type in my gmail address to start the initial setup of the phone. The force close keeps cutting me off. If I type fast, I can sync the account but I cant use market whatsoever. Tried installing Rom manager to re-flash but just sticks at starting download and gapps pops up again.
My son is starting school tomorrow and he has a medical condition. I NEED this phone to communicate with the school nurse via emails and such. As of now I can only text, call, or surf web all while dodging force closes. If ANYONE out there can please help me get my phone back to normal Id greatly appreciate it. Im sure its something easy but as I said before, Im not good at this thing and thats why I never attempted it myself. Your welcome to submit answers here or PM me your phone # if you want to walk me through it on the phone. (I have a landline phone to talk to you on) Thanks in advance for everyones time and Im sorry this ended up being so long.
Download latest Gapps.zip from Cyanogen site to your phone's SD card, boot into recovery, wipe data and cache then flash the Gapps.zip file. Let me know if this helps.
I will try this now. Thank you
Im unable to get anywhere. It still has stock recovery and I cannot get to the screen where I can wipe. Im not great at this sort of thing but Im trying.
Omnichron said:
Download latest Gapps.zip from Cyanogen site to your phone's SD card, boot into recovery, wipe data and cache then flash the Gapps.zip file. Let me know if this helps.
Click to expand...
Click to collapse
i think you would be better off starting from scratch
1. remove your sd card from your phone and plug it in your computer
2. download the latest rom here
3. download gapps from the download links at the bottom of this page
4. transfer both files onto the sd card and put it back into your phone.
5. with your phone off, boot your phone into recovery by holding vol down+power
6. wipe data, cache, and dalvik cache
7. flash only the cm7 file
8. reboot normally
9. reboot into recovery
10. flash gapps
11. reboot normally
after you flash one file, it is highly recommended that you reboot before you flash another file (if your friend didnt do this, this may have been the problem)
HurtsBad said:
Im unable to get anywhere. It still has stock recovery and I cannot get to the screen where I can wipe. Im not great at this sort of thing but Im trying.
Click to expand...
Click to collapse
to flash custom recovery, use this (method two on the page)
EDIT: original post (http://forum.xda-developers.com/showthread.php?t=1056847)
Thank you guys for all your help. The instructions helped me out. Im very thankful. I can now rest better knowing that my sons school nurse can contact me if needed. Have a great night.
no more force closes? sounds good
feel free to post again if you have any more problems
sweetnsour said:
i think you would be better off starting from scratch
1. remove your sd card from your phone and plug it in your computer
2. download the latest rom here
3. download gapps from the download links at the bottom of this page
4. transfer both files onto the sd card and put it back into your phone.
5. with your phone off, boot your phone into recovery by holding vol down+power
6. wipe data, cache, and dalvik cache
7. flash only the cm7 file
8. reboot normally
9. reboot into recovery
10. flash gapps
11. reboot normally
after you flash one file, it is highly recommended that you reboot before you flash another file (if your friend didnt do this, this may have been the problem)
Click to expand...
Click to collapse
....touché
I was running CM10 on a rooted TFT101. I was having some WiFI connectivity issues so I decided I would try out a new rom. I used Titamium Backup and backed up all my needed files to my Mico SD card. Once backed up, I rebooted into CWM v6.0.1.3. I went to do a factory reset prior to flashing the new rom. The tablet just froze. I rebooted the tablet back into CWM. I tried to again do a factory reset and again the tablet just froze. I tried to boot back into CM10 and I just sits and spins and never actually boots into the OS. I decided that I would just go ahead and just flash the new rom and do a factory reset after the fact. I placed the new rom on the micro sd card and booted back into CWM. I attempted to install zip from SD card and now I get e:can't mount /sdcard/. I have tried 3 different micro sd cards and nothing. I have formatted each to fat32 and not one of them is recognized. All 3 are recognized by windows.
Since I can't boot into the OS...and I can't load a new rom....I am dead in the water. Any help would be greatly appreciated.
Thank you in advance.
If you can get it to that endless boot logo and connect it through USB, ADB (info - download) should be able to access whatever's left on your device assuming it gets far enough in the boot process. If it does, you can adb pull the backups to your computer to save them.
That being said, Easy Flasher will help you get back to 100% unrooted stock and "unbrick" your device with a few clicks. Then you can start over with a new recovery and rom. But it will wipe your entire device clean, hence why I suggest you first check if you still have backups and if you do, pull them on your computer using adb.
I can't help with the CWM problem, I haven't used it in a long time.
Lethe6 said:
If you can get it to that endless boot logo and connect it through USB, ADB (info - download) should be able to access whatever's left on your device assuming it gets far enough in the boot process. If it does, you can adb pull the backups to your computer to save them.
That being said, Easy Flasher will help you get back to 100% unrooted stock and "unbrick" your device with a few clicks. Then you can start over with a new recovery and rom. But it will wipe your entire device clean, hence why I suggest you first check if you still have backups and if you do, pull them on your computer using adb.
I can't help with the CWM problem, I haven't used it in a long time.
Click to expand...
Click to collapse
Thank you Lethe6. I saw that option and wondered if that might help me. I will try it out today.
One quick question. If I flash back to stock I am guessing I will just need to reroot once I am able to boot it back up?
Thank you again for your assistance.
Yes exactly. Easy Flasher has a root option as well so it's fairly easy to get going with customizations after restoring to stock!
Lethe6 said:
Yes exactly. Easy Flasher has a root option as well so it's fairly easy to get going with customizations after restoring to stock!
Click to expand...
Click to collapse
Go figure. I went to fix the issue last night per your instructions and I was sitting at the Google login screen for the the new rom I loaded. What ever issue I was having corrected itself. That never happens. I guess I shouldn't complain =)
Thank you again for your assistance Lethe6!