Database Info

is it ahome????????????????

after installing ahome my touchscreen was a little to responsive when i dialed 1 pressing once it would dial it 2 times so i thought a factory reset would fix it when i did the factory reset my phone wont get past the flashing android im probably just going to flash back to rc29 and check with if the touch screen works like it should if it doesnt i can take it to t-mobile for a fix if it does work ill go back to jf rc33 1.42

Oh. Ok. Thanks for telling us.

nabzilla1990 said:
after installing ahome my touchscreen was a little to responsive when i dialed 1 pressing once it would dial it 2 times so i thought a factory reset would fix it when i did the factory reset my phone wont get past the flashing android im probably just going to flash back to rc29 and check with if the touch screen works like it should if it doesnt i can take it to t-mobile for a fix if it does work ill go back to jf rc33 1.42
Click to expand...
Click to collapse
First of all... let me address this before someone rips you apart here. Your question (if it is one) is a bit difficult to read. I am certainly not an english teacher but maybe a period here and there would make it easier to understand. Because I honestly don't know if you are asking a question, stating that you're having a problem with reflashing, going back to factory settings or other. I mean I had to read it 5 times!
Secondly... if you do a factory restore from the settings and you get the flashing android on boot you should let it keep flashing for a few minutes. You need to be patient because it is wiping all of your previous data/settings and restoring them to default.
Third. If it stays on the flashing android for longer then say three to five minutes (depending on how much you need to wipe) then go ahead and boot up in recovery mode and do a wipe from there. If you still get stuck on the flashing android then yes... reflash.
Fourth. Do not assume it is an app that causes this problem unless you are CERTAIN of it. Hundreds if not thousands of people have downloaded this app (including myself) and have not had a similar problem. Maybe do a search for the app name and read what people are saying about it. If it is the app then believe me you won't be the only one commenting. If you're lucky there will be a fix so you won't have to wipe or reflash.
Finally... every so often (especially before making a major change like apps to sd, themes, etc) it'll be a good idea to do a backup with Nand so even if you do end up messing something up (by app or user error) you can always reflash your image to your phone.
Good luck!

EDIT: Whoops! Wrong thread!

I'm very sorry for my poor English but my story is after installing ahome
everything was fine until I rebooted my phone. After rebooting the phone I
tried dialing a number and when I pressed a number once the it would dial
the number twice for example when dialing 7 instead of only dialing the
number 7 it would dial 77, or when using useful switchers turning off the wifi I
would try to check the wifi on but with one push it would check and uncheck
the wifi. Later I did a factory data reset and rebooted the phone I couldn't get
past the flashing android. I reverted back to stock rc33 just in case its a
hardware problem I can let t-mobile know thanks for the replies

i doubt it's a hardware problem.
i had the same problem, coincidentally after installing aHome; i was unable to get past the "flashing android" screen. The first reboot that i did, though, was after using the JF auto-updater app, so i'm not entirely sure where the problem lies.
long story short, i wiped my system, and am now in the process of installing Windows and the Android SDK to my system so i can do a restore.

thanks im gonna go back to root then

yeah, aHome still has lots of thigns to be fixed specially that force close issue every time u return to home :/ i liek dxtop better dont feel like scrolling tru 10 pages like the iphone..

[Q] Force Close out of the box!!! What do i do?

Just picked up the Viewsonic G Tablet. Got it back to my office, charged it, powered it on and the first thing i see is force close...wtf!
I am new to all of this so any suggestions need to be rather detailed.
Thanks

uncledavek said:
Just picked up the Viewsonic G Tablet. Got it back to my office, charged it, powered it on and the first thing i see is force close...wtf!
I am new to all of this so any suggestions need to be rather detailed.
Thanks
Click to expand...
Click to collapse
If you can get to the factory reset in the settings menu that would the first thing to do. And then check for an update. Make sure you set the wifi to not turn off and I would keep the screen from shutting off while downloading the update. Check in settings "about Device". If your not 3389 or higher then you need to update

I had this problem back in November when I first got my tab. Even though nothing seemed to work right, I was able to connect it to my desktop and push across clockworkmod v .08 and a custom rom. So, I never used the original rom more than 10 minutes.
If you can't get it connected while booted in original rom, then Bekit's NVFLash full restore procedure works really well. Just follow the steps carefully and it's a quick and painless factory reset to a known working rom.
These things are virtually unbrickable (is that a word?).

uncledavek said:
Just picked up the Viewsonic G Tablet. Got it back to my office, charged it, powered it on and the first thing i see is force close...wtf!
I am new to all of this so any suggestions need to be rather detailed.
Thanks
Click to expand...
Click to collapse
badfrog is correct. If you factory reset the device it should be fine from there - then you set up your wifi and get the update.
Go into your app drawer and choose Settings. I don't remember if you can do it from the menu button as I'm on a different launcher.
Inside Settings go to Security and select Factory Data Reset. Do this, the unit will reboot and come back up at which point you'll be asked to set it up. It may take some time. Set your Date and Time correctly and set up your Wifi and such.
Once that's done you'll likely get a prompt to update very soon after Wifi connects. DO NOT DO IT, yet.
Within Settings, go into Display and set the Display Timeout to Never.
This ensures that the tablet doesn't sleep or turn off your wifi while it's downloading the update. It's not likely to happen but if your connection is on the slow side and the timeout is set too low, it can mess things up.
Once you've done that, proceed to let the tablet update itself. Again, it may take a bit of time.
Once it's done, make sure you take not of what you have. You'll find this information under Settings in the About section. The last version I got was 3389 - but something newer MAY be there for you. If you get anything less than 3389 then you will have to wait until you get another notification for an update. I don't remember how they work - but I THINK you should get the newest one there.
Once you've confirmed you're on the most current build, It may not be absolutely necessary to do it, but I would factory reset again just to clear the 'gunk' of the older TnT out in case there is actually any.

When I got mine and powered it on the 1st time, I got a bunch of FCs. I powered off and then on, and no more FCs, and it was fine after that. I think I posted asking about that, and someone (roebeet, I think) said it was a known problem. I don't remember the TNT version, but it was the one before 3389, or one before the one before 3389.
Jim

It is a known problem, especially with the older firmware. Sometimes the FC's are so bad that you can't even get into the settings to do a data wipe.
I've actually called CS about this, as an example of why they need an offline updater of some kind to get around issues like these. Suggestion: if you don't want to install clockworkmod, at least try to update the firmware to the latest and greatest, via one of the newer stock ROMs we're retrieved:
http://forum.xda-developers.com/showthread.php?t=842000
That might get you enough access to get into the Settings menu and do the factory restore.

[Q] LGL45C factory reset problems

Hi all, I come to you all in this time of great need. I have in my possession a LG Optimus Net or LGL45C as its know technically.
I started to suffer from problems from gapps resulting from uninstalling the Google Talk app(yes doing this in retrospect was incredibly stupid). After failing to resolve my problem when trying to re-install it, I decided to take the easy way and just do a factory reset and start from scratch. Little did I know what was to meet me. I was given the "Touch to the android to begin" screen like so many others, but it was not meant to be that simple. I would touch the android, and it would light gleefully but it would not reveal to me the next step and sit there motionless. So I proceeded to the next logical step, touching each corner in succession to skip the setup process. But no matter how many times I repeated it, nothing came of it. Next I booted into recovery mode(stock I never bothered to install CWM, another one of my mistakes) and did another factory reset, clear cache, etc. This too did not work. And I thought, there was always installing CWM through ADB where then I can then just flash to a stock ROM I downloaded. But Alas!! USB debugging some how got disabled and it was all fruitless. A little google-fu later I came across a method to flash .kdz using obscure LG utilities. With renewed hope I followed the steps but to no avail. Now I come to you stranger, and plead you in somehow help me in recovering some use of this phone. I have exhausted all my options and I hope someone out there read this and comes in my time of need. Sorry for the long block of text :silly::silly::silly::silly:

Having the same problem as you, bookface.
I couldn't install CWM from the links provided in another post, all lead to a 404 Dropbox page. This sucks. And when I tried to use the installer from Play, I got a dialog saying it's not compatible. Some would say to ignore it, it would be fine...
But if something doesn't feel right, don't do it, I've always been told...
So, I was rooted, but phone started acting funny. Done a factory reset. Since I didn't have CWM, I thought it would clear that mess up.
Nope, almost all apps crash. I'm lucky that at least the browser, Gmail, and music apps work, but everything else, including Google Play Store, all crash upon launch.
Net10's forum is a lame excuse as a "forum." Seems like TracFone employees have NO concept of how a forum works. I looked at there for the same issue, and they rather take software/hardware issues to private messages?
I have NO computer, my hubby's friend who helps him says "You have an Android tablet, that is a computer!" Technically, yes and no. Since I can't root that thing, it's useless. (If you want to know, Polaroid PMID709 4.1 with Rockchip RK29xx, and impossible to root fully, it's "semi-rooted".)
And I'm lost. I and my hubby need this phone to work. Because we need it fpr work (our jobs). And I'm getting sick of TracFone screwing up Android ROMs.
Please help!

youve made much more headway than i. trying to help my neighbor with his. he set a lockscreen password on his lgl34c and then promptly forgot it.
so upon a bit of research, this model is a doozie to work with. i had intended to overdeliver by flashing him a ROM that might allow some hotspotting and the like. upon closer inspection, i dont believe that i will be able to do that. at best a towelroot...
but ONLY IF i can get past this lockscreen. i've tried to factory reset by:
1) removing/replacing battery then holding vol down+power and waiting for LG splashscreen then releasing power (still holding vol down ) and then re-pressing(holding) power again
2) turning phone off and holding home+vol up+power and holding 30-40 sec
ive repeated both methods many many times, and these are the only methods that i have seen described in my google searching. in fact, yours is the most advanced post i have found yet.
how can i factory reset this phone without access to the settings menu?

System UI has stopped/force closing

Hello everyone.
So I just got this phone off of ebay recently, and yesterday I started getting the "System UI has stopped" message. I select the OK button and it just keeps repeating the same error and wont let me access the desktop.
Phone is stock, no root or twrp, with the latest sw update, and I am using Nova Launcher instead of the stock launcher.
I googled this problem and it seems that you need to reboot into recovery and wipe cache partition. I did that, and upon reboot I still get the same error.
I ended up going back into stock recovery and factory resetting.
Has anyone else encountered this problem?

UPDATE...
After factory resetting, I restored phone as a new device. A short time later, after updating apps and downloading some others, I once again got the System UI stopped error. Going back to my backup phone until I can get this sorted out.

UPDATE #2...
Sent BLU a trouble ticket via their tech support page on Sunday. In the meantime, did ANOTHER factory reset and whatnot over the weekend, and the phone was fine up until about an hour ago, and I got the same error.
This time, I called them directly. They actually had my trouble ticket on file, and asked me if I did a hard reset, which I have done MANY times.
They then apologized, and asked me where I bought the phone from (ebay auction).
They then told me that I need to obtain the original sales receipt of the phone in order to process a warranty claim. Now I gotta ask the person who sold me the phone if they still have the receipt?????
This is ridiculous.
Anyway, back to my Moto X pure 2015 until I get this sorted out.

Back to the matter at hand and not how unnecessary you may think it is to obtain a receipt for your purchase...
Can anyone install "MTK Engineering" from the Play Store, go to the "Log and Debugging" tab, open MTKLogger, start recording a video of the device, press play, reproduce the issue, then press stop to stop capturing logs?
BLU needs our help to capture logs since they can't reproduce the issue.

vicks1008 said:
Back to the matter at hand and not how unnecessary you may think it is to obtain a receipt for your purchase...
Can anyone install "MTK Engineering" from the Play Store, go to the "Log and Debugging" tab, open MTKLogger, start recording a video of the device, press play, reproduce the issue, then press stop to stop capturing logs?
BLU needs our help to capture logs since they can't reproduce the issue.
Click to expand...
Click to collapse
My advice would be: In SP flash tool load the Android scatter txt from the GIONEE E8 ROM(which can be found in the development thread), after loading that uncheck the top check mark so it clears all the other check marks. Then double click on the system field, navagate to where you have the stock BLU pure xl system image located(which can be found in the development thread), double click on it to load it into the system field. Then click download on SP flash tool, plug usb into computer, power off your phone hold the volume down key while plugging USB into phone. Then wait till the progress bar goes across the bottom in sp flash tool once its done flashing it will say success and now you will be flashed back to stock system. Hopefully this will get rid of whatever is corrupting your system.

Try running the phone without Nova .. I tried several launchers - and things didn't quite go right. What I've found is that not all applications run as smoothly as my OPO use to run - probably because my OPO was rooted and I pretty much did whatever I wanted with it. Not with this running stock - I don't have "proof" but the Pure XL really didn't like it when I installed a different launcher and/or themes .. once I uninstalled the launchers/themes - I rebooted and it was fine.

Jaybird thanks for the suggestion. However, I still had this issue even on stock launcher. I ended up selling the phone anyways.
And I must say here, I apologize if people were annoyed with the fact that I mentioned needing a receipt for my phone in order to send it in for repair/exhange.. This phone has been out for less then a year and in my opinion should be covered under warranty, whether i have a receipt or not.
Its 2016, don't tell me they can't look up the serial number and see that it's under warranty. But whatever.

Just would like to chime in and say I randomly got this same issue after getting a phone call. Suddenly I have no UI what-so-ever but apparently everything else works. I did see this flash of some screen saying "Preparing files for first time use..." just before I lost all ability to use my phone. And despite going into TWRP and clearing both Cache and Dalvik Cache I still have no ability to use my phone.
---------- Post added at 06:13 PM ---------- Previous post was at 05:54 PM ----------
I managed to get the phone working. Ran the factory reset through TWRP and it seems to be back in working order.

How do I fix strange behavior after 7.1.1 OTA update?

I have a Pixel and recently received the 7.1.1 OTA update. This morning my phone restarted and failed to boot properly. It does boot, and I get to the home screen where all apps seem to be functional. But there are several problems, including 1) I can't turn on cellular data, 2) the home button and the task switcher button do not work. Also, when I press the back, home or task switcher buttons, I get vibration feedback which is not how I had the phone set. Another odd thing is that when I check settings, it shows that the phone is on Android version 7.1 It is as if the phone tried to revert back to 7.1, but did not do so fully. Another anomaly is that when I got to the Play Store, all my apps appear as if they are not updated, even though I just installed available updates yesterday.
When I go to System Update, it shows a 261.9 MB update available to download. I assume that's 7.1.1 OTA update. I could try downloading and re-installing it, but before doing so, I wanted to see if anyone thinks that could cause more problems. Or, does anyone have another suggested step I could take. I would like to avoid a factory reset, if possible. Hopefully, there's another simple, quick solution.

Most likely it is easily fixable by just flashing the full stock 7.1.1 image from Google. Unfortunately it will wipe your device, but it is basically a surefire way to fix whatever went wrong.

It sounds like what happened is the OTA failed somewhere, bad download etc. As the pixel has the dual partitions if an OTA fails it will revert back to the last known working system. As @renegadeone8 mentioned, flashing the full 7.1.1 zip should cure your issues. You will have to unlock the bootloader to do so. (No a bad idea anyway imho Incase you have errors)
No harm in trying the OTA again. If it fails you won't be any further behind than you are now.

I'm having very similar issues, I also have no notifications and cannot pull down the full drop down menu or turn my data back on.

Thanks, k.s.deviate. I wish I had read your response earlier. It probably would have been good for me to at least try re-installing 7.1.1 again. However, I read from users on a different forum that they had experienced odd behavior very similar to what I experienced. In their case they didn't realize, at first, that the problem was associated with the 7.1.1 update. So, they re-installed it. Unfortunately, they had the same problems re-occur. For them the only solution was a factory reset and then not downloading 7.1.1 again.
That's what I've done. Everything is working great now. Android shows the 7.1.1 update available. Based on your assessment, I'm partially tempted to try installing it again. However, if it does end up with problems again, like it did the first time, I don't feel like I have the time to go through the whole factory re-install process again. So, I'm just going to stick with 7.1 for now and wait until either 1) I feel I have more time or 2) Google releases another update (7.1.2 ?) that might fix this problem. Thanks, again, though for your feedback.

exactly same here, so bad download could be ruled out. Also I've seen discussion on reddit and google forum, but unfortunely no solution was presented