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

[Completed] usb problems on a rooted J100H with twrp recovery - advice please

Hi all,
advice needed please. I've been using my Samsung J100H with out any issues for the last 4 months. I rooted as soon as I got it, and a couple of days ago I got TWRP on to it as well. My problem is that I was trying to flash TWRP with Odin, and had some kind of connection drama before I got as far as flashing anything (wasn't recognising the handset in download mode and I was trying different connections and cables). In the end I flashed TWRP with Rashr and it worked perfectly. Since then I can't get my handset to connect to any desktop/laptop. tried both W7 and Linux. All drivers are correctly installed and previously working fine.
So is this a firmware issue? And if so, will flashing back to stock sort that out? And if I do that I will presumably lose root?

Hi,
There is no dedicated forum for your device at this time but you may want to ask your question with all relevant details in the following Android Q&A thread: http://forum.xda-developers.com/showthread.php?t=2259645
Good luck.

Shield Tablet LTE stuck at Bootmenue/Bootloop

Hey Folks,
got some messy Prob's with my old nVidia Shield LTE Tablet.
The Facts:
-KillSwitch not Triggered and it was succesfully Rooted in November 2015, TEGRA-OTA was also Removed (nomoreota)
-worked for Months (beneath one year), only Super-SU penetrated me periodely that it needs to be Updated, but it couldnt be done, it said "not enough Space" after trying to install a newer Version. :silly:
-past Month (January 2017) i decided to do a Factory-Reset, because Girlfriend should get the Shield, thats where the Problem started:
After clicking Factory-Reset, it began to work. After 4 Hours and nothing happening, i decided to Power it Off and start fresh with Installing a clean Stock-ROM and remove the TEGRA-OTA as i done a year before.
But from now on things get messy and to complicated for me.
In the Past i rooted and flashed it with "Shield-RAM", found here on xda.
But this Time it didnt ended with a working Shielt-Tablet. It stucks alwas in a Bootloop, in Recoverymode also as in normally booting the flashed OS.
Confused an disturbed by this, i tried different Recoverys (TWRP 2.8 and 3.0, also a CWM), all with the same Effect: Bootloop
Now i only can acces the Bootmenue which says Bootloader Unlocked.
I dont now what to do from here on and would be very happy and glad, if someone can help me figuring out whats going wrong.
If further Details are needed i will do my best to provide things i forgot here to mention.
With kind regards - ToxicFighter1
Ps.: excusy my bad spelling, bit rusty in flawless english typing:good:

Hi !
There is this thread where you can try to get it back to stock https://forum.xda-developers.com/shield-tablet/general/unofficial-update-original-shield-t3281541
This nice index may help as well
Good luck !

Thanks, but that's not the problem. If I boot into Fastboot / Bootloader, it's totally fine. In fact, I can plug the tablet up to my PC when it's in any state and doesn't experience the issue. It only occurs when I have it plugged into AC. SO far, I've tried 3-4 different cables and power supplies for 2.4A, 2.1A, and 1.2A - all adapters which worked 100% prior to updating.
Suggestions?

OK - Finally fixed it...
I replaced everything as shown above, but ran into the issue again as soon as FlashFire installed the OTA. So, I tried a different way to upgrade and no longer have the issue. Below is what I did...
- Installed 4.4.0 via ADB/fastboot wirhOEM recovery
- Completed initial setup and upgraded to 5.0 via built in system update
- Rebooted
- Booted to bootloader and flashed TWRP recovery
- Booted to TWRP
- Installed SuperSU via sideload
I would have started out applying 5.0 via adb/fastboot, but have yet to see a full image available yet. Used same TWRP and SuperSU as originally used. Just eliminated GlashFire from process. Once I rebooted and everything loaded, plugged into 2.4a power, and it worked without going into boot loop.
Hope this may help someone else - Thanks

Hey Folks,
thx for the few answers, i'll try these Tips out the upcomig Days.
Lot'a Stuff to do atm, bit Busy.
With kind regards - Toxic

xanthrax said:
Hi !
There is this thread where you can try to get it back to stock https://forum.xda-developers.com/shield-tablet/general/unofficial-update-original-shield-t3281541
This nice index may help as well
Good luck !
Click to expand...
Click to collapse
Hey there, and personally Thx for the provided Link.
As announced i did try it, but with no Success.
I'll or explicit the Tablet gets Stuck at Step 17, the Bootsreen doesn't disapear.
Dont know whats Wrong, cause i did all as menitioned in the Post, every ADB/Fastbootstep with Succes-Message, and because Bootloader was already Unlocked, i took the Rooted Image.
But now, im still on Bootscreen, sick
With kind regards!

Problems installing lineage 14.1 on Galaxy Note 10.1 GT-N8010

Tried lineage-14.1-20170305-UNOFFICIAL-n8013.zip on a Galaxy Note 10.1 GT-N8010 (16GB), but after reboot, i am stuck in a never ending "boot logo" (?) (blue circle repeatedly shifting from right to left on a blue bow, nothing else), tried it twice, waited twice for more than 15mins, nothing changed (nevertheless, I could successfully install cm-13.0-20160831-UNOFFICIAL-n8013.zip).
Has anybody sucessfully installed 14.1 on a GT-N8010 ?
Further info: I have an additional 64GB-SD-card where I stored the aforementioned lineage file as well as open_gapps-arm-7.1-nano-20170418.zip and open_gapps-arm-7.1-stock-20170418.zip.
Tried all installations (also cm-13) using twrp-2.8.6.0-gt-n8010.
Any comments appreciated, even more so if they help getting 14.1 installed.
Regards
aqua14
2017-04-19 10:30 (MESZ)
Additional observation while again trying to install lineage-14.1-20170305-UNOFFICIAL-n8013.zip:
* Meanwhile I found that lirokoa recomended the TWRP version mentioned in the CM13 thread, i.e. twrp-2.8.7.0-gt-n8013 (instead of 2.8.6.0 in my first try) and managed to install it on my Galaxy GT-N8010, but after all, this made no difference.
* However, while carefully watching the flash log I found that the "target" was logged to be "samsung/p4noterfxx/p4noterf: 4.4.2/....", and not "samsung/p4notewifi...." as I rather would expect for a GT-N8010.
Hence my question: can it be that (a) either during the paketing of lineage-14.1-20170305-UNOFFICIAL-n8013 something went wrong, or that (b) my tablet pretends to be a different one (namely GT-N8000)? I suspect this confusion could be the reason of the aforementioned boot trouble.
At least I am sure of this fact: I haven't got a tablet with phone function, its the version only having the wifi function, and in the system info provided by JellyBean as well as KitKat I could read its the GT-N8010.
Any constructive hints or suggestions appreciated
Regards
aqua14
Additional observation:
* Both lineage-14.1-20170305-UNOFFICIAL-n8013.zip and lineage-14.1-20170116-UNOFFICIAL-n8013.zip don't work on my GT-N8010 (reboot after flashing leads to a boot loop) , whereas cm-14.1-20161208-UNOFFICIAL-n8013.zip did work (not everything tested yet, but wifi, installing apps (another keyboard, file manager, ...) worked ok.
2017-04-20
Eventually ...
I guessed just from the beginning, that the right path might again be hidden in all the tidbits given in the discussion around the lineage 14.1 thread (hxxps://forum.xda-developers.com/galaxy-note-10-1/development/rom-nougat-t3505239)
... and indeed! It took me a while to crawl through all comments, questions, answers, and unfortunately also complaints, the latter in some parts being expressed even in close-to-nasty manners. Being a developer as well (DB area) I as well appreciate constructive criticism and prefer it to demotivating complaint. However, some of the participants obviously never have learnt making an effort to keep the difference between both, maybe they are even unlucky enough not to perceive hours and hours of voluntary work of their contemporaries as a gift. Hey guys! Behave!
Whatsoever. I finally made the way through the texts and even managed to install the latest version (lineage-14.1-20170305-UNOFFICIAL-n8013.zip) and ... beneath my sincere thanks going to lirokoa (taking a bow 4 u), I'd like to greet and thank all the testers *and* contributors of helpful hints (regarding the installation of the ROM itself as well a manifold of aspects to special apps), also including especially those who took their time to precisely & factually describe which procedure did fail (!), which -in sum- made my day start successfully now!
For all those still struggling: keep trying!
After all this reading I restarted a new try and had my breakthough ~after having read the following comments in the aforementioned thread: #352/p.36, #364+#365/p.37 and some others of similar content, hence thanks also to alessandro_xda, hektor2hektor2, CDiazF04, but also all the others who keep the discussion vivid and interesting, and a special smile to miz_pimp for having increased the level of friendliness throughout the course .
And yes, I agree that many contributors are right in suggesting to include the one or other hint to the post #2 of liroka.
I guess it's presumably just lack of time on his side that this has not yet happened. On the other hand... :-> if I could walk through all the interesing discussion in one evening and draw my conclusions in order to get a free ride to another "new life" of my ol' N8010, ... I am quite positive that others can do so as well.
Continuously following the discussion...
aqua14

Thanks guys!
Just had the same problem. I just needed to upgrade twrp and try again. I really appreciate this site! Now my old tablet is doing better than my husband's new one.

Finally loaded Lineage 14.1
I have just updated my GT-N8010 with lineage-14.1-20170810-UNOFFICIAL-n8013.zip + open_gapps-arm-7.1-mini-20181010.zip & used the latest TWERP release 3.0.2 to do this.
I initially tried loading these two as above, the first issue was that having loaded them the tablet would get stuck with a battery symbol and would not boot. The way I found around this was to boot the tablet into Odin mode but choose Reboot Phone rather than going into Odin itself. This then enabled Lineage to boot but it then got stuck in a loop, the lineage logo would go through its line with a moving O, then have three O's and start again.
Eventually I found that I could get cm-13.0-20160831-UNOFFICIAL-n8013.zip to load with open_gapps-arm-7.1-mini-20181010.zip and this worked well. I then did a dirty load (No Wiping) of lineage-14.1-20170810-UNOFFICIAL-n8013.zip and this is now working without problems.
Hope this helps and best of luck!!

macgd016 said:
Finally loaded Lineage 14.1
I have just updated my GT-N8010 with lineage-14.1-20170810-UNOFFICIAL-n8013.zip + open_gapps-arm-7.1-mini-20181010.zip & used the latest TWERP release 3.0.2 to do this.
I initially tried loading these two as above, the first issue was that having loaded them the tablet would get stuck with a battery symbol and would not boot. The way I found around this was to boot the tablet into Odin mode but choose Reboot Phone rather than going into Odin itself. This then enabled Lineage to boot but it then got stuck in a loop, the lineage logo would go through its line with a moving O, then have three O's and start again.
Eventually I found that I could get cm-13.0-20160831-UNOFFICIAL-n8013.zip to load with open_gapps-arm-7.1-mini-20181010.zip and this worked well. I then did a dirty load (No Wiping) of lineage-14.1-20170810-UNOFFICIAL-n8013.zip and this is now working without problems.
Hope this helps and best of luck!!
Click to expand...
Click to collapse
Have you tried out my LineageOS 14.1 ROM? https://androidfilehost.com/?fid=1322778262904016892

I'm sorry to say that I have not as I was not aware of your rom till now so thanks for for your post and I have downloaded it just in case I find issues with 14.1-20170810. Out of interest how does it differ from 14.1-20170810

macgd016 said:
I'm sorry to say that I have not as I was not aware of your rom till now so thanks for for your post and I have downloaded it just in case I find issues with 14.1-20170810. Out of interest how does it differ from 14.1-20170810
Click to expand...
Click to collapse
Mine is more up-to-date. But I will be making a update for that ROM later this week.
Here is my thread for the ROM: https://forum.xda-developers.com/galaxy-note-10-1/development/rom-lineageos-14-1-t3848514

Oreo rom for Samsung galaxy note 10.1 gt n8000
Pls any Oreo rom for gt n8000 my nougat rom can't play videos since i rooted it, after unrooting it still can't play any video. Pls is there any fix.

Flash stock rom via Odin.

JJEgan said:
Flash stock rom via Odin.
Click to expand...
Click to collapse
Will flashing the phone with lineage 14.1 again help? Cus I can't go back using stock rom

Back to stock then flash custom rom.
Problems fixes use SEARCH.
Rom is in testing so its up to you to flash with potential problems or not .

I have the same problem. Note 10.1 N8010 and it is stuck on the logo " blue circle repeatedly shifting from right to left on a blue bow".
I cannot locate the file TWRP for the note 10.1 N8010.
The suggestions were to update Twrp but the file I have found online is (
twrp-3.4.0-0-lt03wifiue.img.tar7.5M2020-06-23 21:11:34 EDT
This file is loaded using odin and it is successful but the Twrp doesn't work anymore. Therefore, I had to go back and load the file (twrp-2.8.6.0-gt-n8010.tar).
Can someone please help me with this issue.

TWRP site is twrp.me

Có ai up rom android 7.1.2 hoặc 9.1 cho galaxy GT-N8010, qua TeamViewer không? cảm ơn.
[email protected]
Translated by GT:
Has anyone uploaded rom android 7.1.2 or 9.1 for galaxy GT-N8010, via TeamViewer? thank.
[email protected]

See your other post

TWRP Freezes on 1st instal

I have asked on a few threads including the TWRP thread but no one seems to be answering for some reason so I thought I'd risk putting up a separate post to try and get an answer.
I followed the instructions to the letter on how to install TWRP from the thread and it installed all ok, the only problem is that the screen is totally frozen and there is nothing I can do to get it to work. I have now gone back to Oreo via Odin until I can get help on what's gone wrong. Would it make a difference if I tried from Nougut 7.0?
I have rooted and installed roms, TWRP's pretty often last year with my M10, M8 etc so I'm not that new to this but it's got me foxed this time.

Good question. I had an issue after installing CarHDROM, v9 for a bit where I could get into TWRP, but the phone would boot loop getting out of TWRP and I had a hard time getting back into recovery or download mode.
I re-flashed the phone and TWRP as well, and after that all was well. I did not change anything on the re-flash.
Sometimes things just get mux'ed.