Database Info

[GUIDE] To Asking Questions! (Have a problem? Start Here!)

How to Ask Questions!​
If your messing with your phone, eventually you will have a problem you cant solve on your own. We have all been there, its just part of modding your phone. but if you give some time and a little patience, most of the time its easy to get fixed.
FIRST: SEARCH!!!​​This means try searching a thread if its too long, or searching the entire G2X Section of the forum. (and we can tell if you really searched or if you just say you did to get rid of the people yelling at you) If you see nothing that relates to you, or you have tried all of that, then you can make a post, BUT FIRST...
Stuff to Try Before Posting:​​So... your having a problem with your phone... well there are a few things you can do to help fix most issues:
Go into CWM and clear Cache
try this first, it really does help solve most issues from within a rom
Make a Nandroid Backup and clear data
just do this as a test, make a backup and clear data. check to see if the problem still exists, if it fixes it then its something you installed/did to the rom that caused the problem.
if not then...
Try flashing a new ROM
even if you don't like it, even if you can never go back to gingerbread after ICS just try it to see if it fixes your problem. If it does then you can decide if ICS is worth the issue your having.
Clear App data/Reinstall App
If you having an issue related to a specific app, try going into settings and clearing that app's cache and data. if the issue still exists try uninstalling it then reinstalling it after a reboot.
If none of these things helped you, then its time to make a post.
Things to Include in your post:​​If your having an issue, many of us are willing to help to get it resolved, but first, you need to give us some useful information.
A good checklist to include in your post is the following:
Current Rom
Current kernel
If you have done ANY undervolting or overclocking.
If you had this problem before (either on other ROM's or previously on your current ROM)
If you wiped Cache
If you wiped Data
If you tried installing another ROM
Any other things you already tried (BE SPECIFIC!)
the more you include in the first post the better, too much information is MUCH better than not enough.
If you think the issue is related to a specific ROM, try posting in that ROM's thread in the development section, but please don't spend too much time there. If nobody can find a simple fix, move your discussion to a new thread in the Q and A section, don't clog up the Developer's thread with a single issue.
Once again, the more information you give us the better, and if you don't post the above, someone will most likely ask you those questions, or tell you to do those things first (or they just might ignore the question).
If you see any typos, or think of anything i could add or improve on please let me know.

t mobile lg g2x reeboting issue
Hey guys i recently tried flashing a new kernal to my lg g2x in xda development forum installation procedure went well but at the very end when you have to reebot in recovery it never rebooted back properly just got a blank screen with a notification buttons flashing at buttom of screen....... i just rooted my device so i was still running my stock rom and kernal....... what should i do to get my phone back working please help???

p999dw six digit spc code
Sorry about my weak English
i almost searched entire forum and i only get spc must be 000000. But it's not works. I live in Turkey. At first i can send spc 000000 in QPST but after when i bought the unlock code from ebay, i can't access anymore. Does anyone have an idea?
Thanks

My screen not reading my finger
Im not sure if this is the place i had to ask my question. My cell used to read my finger all the time but now it only does when i turn it on, afther it sleeps n i press the top botten to used it it wont read my finger no more. If i turn it of by taking the battery out and on again it reads my finger until it locks then it dosent. right now i have EB on the phone i cleard cache, system, dalvikcache, format/data. Ive restore basic rom then back to EB but nothing work it only reads my finger till it sleeps then it wont read it no more
PLEASE, WHAT CAN I DO??...

Oskar20022 said:
Im not sure if this is the place i had to ask my question. My cell used to read my finger all the time but now it only does when i turn it on, afther it sleeps n i press the top botten to used it it wont read my finger no more. If i turn it of by taking the battery out and on again it reads my finger until it locks then it dosent. right now i have EB on the phone i cleard cache, system, dalvikcache, format/data. Ive restore basic rom then back to EB but nothing work it only reads my finger till it sleeps then it wont read it no more
PLEASE, WHAT CAN I DO??...
Click to expand...
Click to collapse
I have the same problem and I can't find any way to fix it I am going to post a new thread about the problem.

Hi all...
I was watching, reading and was excited about cm 14.1 for my LG g2 which was running on lollypop.
What a mess I created for myself. Will explain step by step. I I would be thankful if anyone can teach me get out with it and back to LG rom lollypop.
1. I rooted my phone with one click tool.
2. Then I installed Twrp through play store app.
3. Download cm 14.1 for lg g2. The as well as open gaps.
4. Next thing I did rebooted to twrp recovery and clean it after taking back up. But was not able to flash cm 14.1. Also loaded gapps7. 1.
5. After so many trials nothing happened I even updated twrp to 2.8
6. Then I found twrp 3.0 and tried to flash it.
7. Suddenly my phone came to a stage Fastboot.
8. My computer stopped detecting it.
9. Then I re plugged it into the USB of my computer.
10. I found the partitions are there. But no system is there.
11. Even I don't know to sideload it.
12. Lg flash tool is not able to flash it.
I request if someone know the way to flash it with lg roam. I L be thankful.
Can anyone email me steps to do to get out of it.
My email is [email protected]
Thanks
Regards
Harpreet Singh

Hs-india said:
Hi all...
I was watching, reading and was excited about cm 14.1 for my LG g2 which was running on lollypop.
What a mess I created for myself. Will explain step by step. I I would be thankful if anyone can teach me get out with it and back to LG rom lollypop.
1. I rooted my phone with one click tool.
2. Then I installed Twrp through play store app.
3. Download cm 14.1 for lg g2. The as well as open gaps.
4. Next thing I did rebooted to twrp recovery and clean it after taking back up. But was not able to flash cm 14.1. Also loaded gapps7. 1.
5. After so many trials nothing happened I even updated twrp to 2.8
6. Then I found twrp 3.0 and tried to flash it.
7. Suddenly my phone came to a stage Fastboot.
8. My computer stopped detecting it.
9. Then I re plugged it into the USB of my computer.
10. I found the partitions are there. But no system is there.
11. Even I don't know to sideload it.
12. Lg flash tool is not able to flash it.
I request if someone know the way to flash it with lg roam. I L be thankful.
Can anyone email me steps to do to get out of it.
My email is [email protected]
Thanks
Regards
Harpreet Singh
Click to expand...
Click to collapse
This isn't the LG G2 forum.
http://forum.xda-developers.com/lg-g2

[Q] Question concerning Dragonzkiller's Droid x2 CM9 Rom

Alright, so here goes. I've searched the thread for the issue I'm having, but have come up empty handed. I'm not Droid noob, especially not when it comes to flashing roms. But, here are the details I have.
I had been following dragonzkiller's development on his ICS rom. I hadn't really put forth any effort looking lately until yesterday, and saw that he had the wifi and camera fixed, which were really my two biggest issues, so when I saw that, I was excited. I began working on getting it all running. I've had the x2 for about 5 months or so, and usually, the first thing I do, as soon as I get a new phone, is root it. Back in April, I rooted with GingerBreak. Worked good, no issues there. Back in June, apparently I still received the OTA update taking it to 2.3.5-418, which I found out last night had kinda broken my root. So, I went back to find a way to re-root. I did that, with a desktop .exe that went in, and was supposed to flash BSR to my phone also. After I ran that, all my root permissions started asking for options again, so I was relieved. Now, for the issues I'm having.
I downloaded an app in the play store called Online Nandroid Backup. For some reason, and I think this may be a dev issue with the app, it won't run a backup, and tells me that it wasn't able to be granted superuser permissions, even though it is prompting and I'm allowing. Issue number two is this. I've tried 3 different ways to get this working. I used ROM Toolbox Lite, selected the rom I wanted to flash, and wipe data and cache, no delvik. I've selected to run a backup of my current rom. When it boots into recovery, I only have 4 options. Reboot your phone, something about installing the rom from sdcard, wipe data, and wipe cache. I'm not given the backup option on the recovery. Furthermore, when I kinda just decided that since I hadn't had any trouble flashing a rom to any of my other phones I've had, I would just try to flash the rom, it gives me a prompt about 25% through the rom package saying E: signature could not be verified, or something to that extent.
Even though it has said not to use Rom Manager, I did download that and try that, and got pretty much the same outcome of no rom, just a bit different scenario going through. Rom Manager won't reboot into recovery, and when I select to do a backup, it reboots the phone straight up. I also used the manual entrance into recovery, volume up, but it tells me something about starting RSD protocol, and sticks at that forever.
My real questions are this... I've always ever used CWM. All of my previous phones have been supported by Rom Manager nicely, so when it came to downloading and flashing a rom on them, no problems at all. I have never used BSR, to my knowledge, so I'm not sure if the recovery screen I'm seeing is the actual BSR recovery, or if it's some other recovery. If it's not BSR, do I just flash it like I would a rom, then re-run into that? And does the signature issue that I'm running into mean that I have to wait for a signed version of the rom in order to work it? Is there any way to fix this issue, or am I basically SOL right this moment? Any information on how I can fix all of this would be greatly appreciated. Thank you.

Is it possible to get back my A510 in the manner I got it?

Hi,
I think flashing a ROM has been the biggest mistake I could make. I guess I just got greedy for a lil more performance that I decided to take the risk .Anyway, lots of things have gone wrong ever since.
To cut the story short, how can I reset my tablet to the way I got it? Locked bootloader, no cwm...how? I have restored via Nandroid, and did a factory reset...but still I can find traces of nothrills A700 ROM on my system. I wan't to get rid of all this.
Thanks!
PS: My device now shows up as "Acer A510 (registered November, 2012)" on Google Play. Previously, it showed up as "Acer A510 Tegra 3".

Please, don't start this conversation in multiple threads because people aren't answering your problems fast enough. You want to get back to stock because of problems (that have nothing to do with your flashing, but still) and people are already trying to help you with that in other threads.

[Q] Need help with my 602

I hope I am not wasting anyones time by posting something that may be and I hope is a simple fix, but I have a problem with my Verizon Xoom, a 602 (without the 4g upgrade- don't even have verizon service) that I can't figure out- and it's not for lack of searching. I have been rooting my devices and running custom Roms since my HTC Touch, (a big thank you to all of you here at xda for all the knowledge and instruction I have been able to leach) but I am very much still a noob with only the vaguest since of how Linux, android or the devices themselves actually work- and that is especially true of my xoom with all its post release changes in storage and whatnot since I bought mine, so please don't flame me to hard if this is just my ignorance- I promise you I'm not just being lazy, I just can't figure this one out. I have been running EOS for a while now without a hitch, and recently installed 150 when it became available. everything was fine until a couple of days ago when it started freezing on unlock which just took turning the screen off and back on to fix, but every app started crashing, some periodically and some such as android.process.acore, browser, and google play that won't open at all. I use Team Win's recovery and tried a wipe and reinstall, but same thing. When I try to fix permissions I get a failure with the message "E: Unable to chown '/data/app/com.google.android.youtube-2.apk' 1000 1000". Also when I try to wipe internal storage I noticed everything was still there even though my recovery was saying I had a successful wipe. I switched to clockworkmod recovery and tried to use eraseData file in the folder to wipe the old way but that didn't seem to work either (which I'm not even sure I did right but figured I better get some advice first anyway), and when I tried to flash EOS 3 stable it won't get past the EOS boot animation at all. If anybody out there knows whats up and has the time to point me in the right direction it would greatly appreciated... Thanks

Wowzers! When all else fails ... unroot / re-root. That will wipe everything.

Desperately need help w/issue After 8.0 Update...

S8+ /S8 Global Unlocked Variants, (ie: G955FD, etc) Desperately need help w/issue After 8.0 Update...
Hi, I have a G955FD & have family members with this same model, as well as the Global unlocked regular S8-dual sim. We all have the same issue after the Samsung 8.0.0 update. The phone is no longer reliable. Randomly, these devices will not have any ring on incoming calls. If they don't leave a VM, then you have no indication of a missed phone call. In addition, random periods where text messages will also just not come thru. Difference on the texts is, when you reboot, they all populate in the message app and notifications. But the incoming calls are not known and lost forever w/o a VM left for you by caller.
I have been in contact with Samsung, although they indicate right off that I have no warranty because I didn't buy a carrier device from an authorized vendor for my local use, they were open & helpful to reveal that they are aware of '8.0 ringer issues' on the unlocked global devices. BTW, this must be a huge number of people across the world with this problem, but like my friends/family, originally think they have signal/carrier issues etc. Samsung says that it should be addressed in a patch or update..... but, WHEN? I have had a messed up phone for over 3months and counting.
The only thing that can be done to attempt having the phone work 'more often' is to do a restart every hour all day long and hope that your phone will ring when someone is calling.
I, personally, being the family tech guy, am the one working on the issue so I'm here to ask for help/input.
Been dealing with this issue for over 3 months now, here's some of what I have done and what I'd like help with please...
I have attempted 5x to install a custom ROM from XDA to alleviate this issue completely, but as of now, still unsuccessful. I've been rooting/hacking my android devices since my 1st but somehow can't get the process to work thru. At this point, using Odin, I have no issue to get my phone running TWRP and rooted. Somehow, after that point something isn't going right and my phone has to be re-odin flashed with OEM ROM and then wait 1 week for OEM unlock to re-appear to try again. So, If I could complete this process next time the OEM-unlock is back up, my problem would be over.
Now, since I am having issue with completing a custom ROM install... I thought, why not flash a previous OEM ROM (7.0 NOUGAT) and again, my problem should be over and I could wait until a 9.0 update to see how that goes. So far, any 7.0 stock ROMS I have been able to find/download, have 'failed' install in Odin. (I have standard Odin, patched and Prince Comsey) so I always try them all before I say it's a true fail.
Can anyone help me to understand why, with all the root/roms Ive done, cannot get custom ROM to complete install. I was trying for the CarHD or Batman. after rom flash, something goes wrong and the phone either goes bootloop or failed verify. (BTW, couple X I did flash the no-verify to alleviate that issue but still get bootloop or no new rom boot up)
The other thing I'd love to be able to do right now that 'should' be a piece of cake, (but hasn't been) until I figure out the custom rom install issue, is to ask for anyone that can post a link to a valid ODIN-flashable Stock 7.0 NOUGAT ROM for my S8+ G955F/FD. That would solve everything for now and I'd just disable updates for the interim. As previously mentioned, the couple I have found would only FAIL on Odin flash attempts. Seeing that this is a global, unlocked device, is it possible to flash a stock rom or flash a diff CSC that can get me North America Tmobile setup (my USA provider) I noticed that the global phone has no options to disable LTE or turn wifi calling on/off etc.
I apologize if I have jumped around in my post, not provided enough details or not written very eloquently, but I am happy to provide any other needed info to move forward if any of you have ideas here. I'm just at the end of my rope with this right now.
Any help, input here is much appreciated! TIA! mark~

Trying to be helpful here.
For some folks flashing with Odin the first run through errors/fails. That issue was a PITA. I found a post somewhere which said when you hook up the phone to flash with Odin, the first attempt will fail, but to leave the phone connected, go back into download mode, and flash again. Do not unplug the phone when you do this.
For some reason there's a kink in Odin with some folks.
That info, wish I could recall who by - they deserve the recognition, anyway it solved all my Odin errors.

JeffDC said:
Trying to be helpful here.
For some folks flashing with Odin the first run through errors/fails. That issue was a PITA. I found a post somewhere which said when you hook up the phone to flash with Odin, the first attempt will fail, but to leave the phone connected, go back into download mode, and flash again. Do not unplug the phone when you do this.
For some reason there's a kink in Odin with some folks.
That info, wish I could recall who by - they deserve the recognition, anyway it solved all my Odin errors.
Click to expand...
Click to collapse
hey jeff, thanks for checking in when the OEM unlock button returns again tomorrow, I'll keep this in mind on my next attempt. i did encounter that fail several times with some OEM firmware flashes (trying to go back to 7.0) and this should resolve that problem. overall though, my real issue seems to be when attempting a root/custom rom instead of a stock replacement... and 'after' i get TWRP completed. I'm doing something wrong with a button hold sequence or something else. maybe need flash 'do not verify' right off too. I'm gonna go extra slow/careful following each step from a great, detailed post for TWRP/ROOT/ROM procedure that i found here over weekend written by 'jesec' what i hate the most is, i only have 1 shot doing this with the oem unlock button, if messed up, have to re-flash a stock rom and wait another 7 days to try this all again.
i still cannot believe its been about 13wks and samsung says they are aware, yet still has not patched this problem. i love my samsungs but im so fed up, i almost ordered a oneplus 6 this weekend just because of this random no ring issue.
thanks much!