yashsingh1/xdaforums huggingface dataset:
[Moto X Q&A] Cozume:
when I put the phone in recovery TWRP 2.6.3.1, adb will recognize my device but it thinks it is my Samsung Galaxy Nexus.
[Moto X Q&A] hovax615@hotmail.com:
Uninstall everything on your USB ports/drivers restart let windows redownload the USB ports/drivers and run the Motorola drivers install

MOTO X Slapped
[Moto X Q&A] Cozume:
yeah, that is looking like what I am going to have to do :( :(
[Moto X Q&A] yghrv:
I hit the issue earlier and fixed it with the steps. hope will help you too.

1. connect your phone with computer

2. go to C:\Program Files\Common Files\Motorola Shared\Mobile Drivers\

3. run Motorola Driver Installer.exe, choose clean and Reinstall.
[Moto G Q&A, Help & Troubleshooting] motoG_2014:
delete
[Nexus 4 Q&A, Help & Troubleshooting] jinjin12:
How do i back up my EFS or IMEI on NExus 4? I searched google but there are basically no topics on this.

The only topics i found said that you don't need to back up EFS/IMEI on Nexus 4 since it's only really for samsung phones and google phones don't have EFS folders?

IS this true?

if so then how come there is a way to back up EFS for NEXUS 5 and not for nexus 4?
[Nexus 4 Q&A, Help & Troubleshooting] Berrydroidcafe:
As far as my understanding is, the IMEI is hard coded on the phone so I am not sure if it can be backed up besides writing it down somewhere.

http://xdaforums.com/nexus-4/help/backup-imei-nexus-4-t2003518

Sent with my Nexus® 10 minus 3
[Nexus 4 Q&A, Help & Troubleshooting] lopezk38:
tl,dr

The Nexus 4 does NOT have an EFS partition to back up, because the contents of the EFS folder are stored elsewhere where they do not need to be backed up.

Some unnecessary thoughts below

A quick Google tells me that LG has been using EFS partitions for awhile before the Nexus 4 was released, even the Optimus G has an EFS partition even though the Nexus 4 is based upon it. Google must have stored the IMEI/other EFS stuff elsewhere on the phone compared to the Optimus G to make the phone more developer friendly, probably in a hidden partition which you can't modify to prevent any corruption or deletion. If my theory is correct, this would explain why some Nexus 4s lose their IMEI after the partition table gets messed up, it probably corrupts said hidden partition, although that would not explain why I (or others) didn't lose my IMEI when I had to wipe the eMMC and reflash the partitions and all the system stuff with the LG download tool. Maybe the IMEI is stored in another chip on the motherboad, maybe on an EEPROM/NAND flash chip, and symlinked to the eMMC or otherwise linked to the eMMC? I dunno, just a thought
[MDA II, XDA II, 2060 ROM Development] nebondkiev:
:?

I try to update my XDA II but when erasing the current ROM it stack

than error appears. Than after I reset my device it only "serial" shown on the LCD screen I dont know what to do...
[One (M7) Q&A, Help & Troubleshooting] bernz_eazy:
good day! has anyone experienced their battery being stucked at 1% after flashing the latest eragon?.. i have flashed eragon v23 in the past without any problems.. saw that the rom was updated so i gave it a go.. 1st download thru androidfilehost was a bad download.. 2nd download thru htcfanboys was a good one. flashed rom perfectly.. flashed kernel ok.. then i just noticed that my battery was 1%.. so i plugged it in my charger light flashed red so i suppose it was charging but battery is not going up.. unplugged it got a reminder that of low battery.. i have unplugged for good 15mins browsing still the battery won't die.. went to recovery found out that my battery was still 75%.. reflashed rom full wipe,cache,data,system.. same issue.. could it be just another bad download?.. or am i missing something?.. thanks for any reply
[One (M7) Q&A, Help & Troubleshooting] raxbg:
Bump.

I have the same issue, but with I installed a stock rom. The rom was at 4.4 not 4.4.2 so I downloaded an 180mb OTA, it installed ok, then there was another update 320mb, it also installed ok, but since then the battery is stuck at 1%. Going into recovery shows the battery level corectly though.

Please help
[One (M7) Q&A, Help & Troubleshooting] ryodu:
I had the same Problem after flashing a custom Kernel.

Maybe try another one?

Sent from my HTC One
[Captivate Q&A, Help & Troubleshooting] hieuduc88:
I having back stock rom KK4 to restore the original my imei. After finishing for flashing I897UCKK4 Odin One Click - Stock, NO Bootloaders, Re-partition, Full Wipe. KK4 is good but it still return face imei: 004999010640000 and no produce code,etc....Please help
[Captivate Q&A, Help & Troubleshooting] BWolf56:
First, you don't have to start another thread for the same issue you were having. It clutters the forum.

Now that being said, I assume you meant "fake" imei? Are you able to make calls? Do you get signal?

Last thing, did you search how to recovery your imei? There are are few ways.
[Captivate Q&A, Help & Troubleshooting] hieuduc88:
Sorry for this theard, U can go to close it. Sr for my eng is bad. I will search for that. Thank you
[Galaxy Note II Q&A, Help & Troubleshooting] tysonpr33:
I live in Puerto Rico and im trying to make my N7100 work better with Net10, is it possible to flash a i317 at&t modem on a N7100 and if possible will it help in any way?
[Galaxy S I9000 Q&A, Help & Troubleshooting] need4steer:
videos and screenshots which demonstrates the bluish / blueish screen issuse

reserved for videos and screenshots which demonstrates this issue.

In the meantime,

YouTube videos which demonstrates this issue

[YOUTUBE]kvux8SM03Sk[/YOUTUBE]

[YOUTUBE]f91FvwVQW38[/YOUTUBE]

Screenshots that I posted in another post.
[Galaxy S I9000 Q&A, Help & Troubleshooting] SferaDev:
I saw pawitps commit on gerrit, I'll add it right now. Should be solved on OmniROM, Paranoid Android and Nameless future builds.

See you!
[Galaxy S I9000 Q&A, Help & Troubleshooting] need4steer:
Cool!

Thanks a lot for your great contribution!

Please let us know so I'll update the ROMs list that we can use, so we'll know we have other great ROMs to flash.
[Galaxy S I9000 Q&A, Help & Troubleshooting] need4steer:
List of ROMs that I9000 devices with the blue screen (blue tint/hue) issue can flash

The list of ROMs that I9000 devices with the blue screen (blue tint/hue) issue can flash moved to here.
[Galaxy S I9000 Q&A, Help & Troubleshooting] MrCabana:
grrrrrrrrrrrr

Too bad I didn't find this useful post in time before I broke my "uncalibrated screen" and replaced it with a new one.

Glad to know it was NOT a hardware problem, that means my first guess was right.

Thank you very much for the great work, guys !!!!
[Galaxy S I9000 Q&A, Help & Troubleshooting] need4steer:
Well brother, a lot of credit goes to you since I got a lot of information from you, and it was you who got me realizing that this is a program issue and not a hardware one.

You got me motivated to keep trying and reading and researching, and I'm so glad that pawitp was, and is, willing to help solving this issue.

Thanks a lot!
[Galaxy S I9000 Q&A, Help & Troubleshooting] MrCabana:
I am glad I was of help for others who face this same problem in the future.

If it's not asking too much, since I got some brain's attention for this device, I have another problem/question to report (I can start another thread if you guys think is necessary).

The problem is ... after replacing the "uncalibrated screen" with a brand new one, the battery indicator stopped working. That means the phone will always report it as 100% charged and won't allow the cable to charge it. I have to wait until it shuts down with no more power and charge it outside the device with a spare charger.

Secondly, the back camera stopped working while front camera is perfect. Both of them are attached with the same connectors to the MOBO, making them just 1 single part. How can one work perfect and the other one just go dead like that?

Thirdly, the USB connection is hard to be stablished with the computer. Even in service mode (i.e. to use odin). It does connect sometimes, but then it freezes even during a ROM update. This is making it impossible for me to mess with it and roll back to Froyo if things go wrong.

Again, those 3 problems CAN be due to malfunctioning hardware, but I believe it 's too much of a coincidence for these 3 unrelated things to happen right after the screen replacement, followed by an update to a nightly build of CyanogenMOD (don't remember exactly which one).

Any help would be greatly appreciated.
[Galaxy S I9000 Q&A, Help & Troubleshooting] need4steer:
While I and some other might help you here, it's better for you to open a new thread with appropriate title so others will be able to see your issue and help solve it. In this thread you'll see people who are interested in the bluish screen.

Anyway here are my comment for your device's issues:

Did you try another battery?

Did you tried different ROMs?

What's happening in recovery mode?

Perhaps one of the pins in the connector is bad?

Is the connector looking okay for you?

Did you tried different ROMs?

Is it happening in the same USB port in your computer?

Is the USB port connected directly to the motherboard, or is it one that is connected to the chassis, and from there to the motherboard?

The problems occurred only after the update? If so, revert. (I know that you don't have a USB connection, but you can take your sdcard to another device and copy to it the latest stable ROM)

If not, then if you ask me - it might be a hardware issue. It's very probable since before it you had no issues with the same ROM.
[Galaxy S I9000 Q&A, Help & Troubleshooting] MrCabana:
I don't have another battery nor different ROM's. I tried to revert to Froyo, but since USB is malfunctioning, I gave up on it. Recovery mode also reports battery as 100% even if it's nearly dead.

Yes, the connector is looking okay to me. I removed it myself very carefully while replacing the digitizer. I'm almost sure it is NOT a hardware problem.

I tried many different cables and USB ports. Both chassis front and rear mobo. Even different PC's. Same results. 1 every 30 tries will let me use ODIN, and 1 every 30 tries, ODIN will complete uploading. That's frustrating.

[/QUOTE]

The problems occurred right after replacing the digitizer. Since I had Android 4.2.2 already installed, I didn't insist on trying different ROM's or rolling back to Froyo.

Thanks for the quick reply.
[Galaxy S I9000 Q&A, Help & Troubleshooting] need4steer:
I must admit that it's not looking good since it's probably a hardware issue. If not, why these 3 things stopped working right after you replaced the digitizer?

However, if you want my advice, do open a new thread with appropriate topic name and include all this information so others will see it. Maybe someone will suggest something that we didn't think of.

In addition, while Android 4.2.2 is already installed in your device, don't forget that you can continue updating to newer versions:
[Galaxy S I9000 Q&A, Help & Troubleshooting] MrCabana:
Alright, I willl try to update version and see what happens.

Thank you.
[Galaxy S I9000 Q&A, Help & Troubleshooting] MrCabana:
I just updated to the newest nightly version, Android 4.4. Despite I now have neat KK, the problems persist.

Anyway, thanks for your help and I will follow your advice of opening a new thread.
[Galaxy S I9000 Q&A, Help & Troubleshooting] need4steer:
First of all, congratulation! I had no doubt you'll do it easily.

These 3 problems will persist in this and in any ROM, since unfortunately it seems like a hardware problem.

However, I might be wrong (hopefully), and posting a dedicated thread for these problems will make them exposed to others so you might get some good solutions for them.

Good luck!
[Galaxy S I9000 Q&A, Help & Troubleshooting] tetakpatak:
Great effort, [MENTION=5157668]need4steer[/MENTION] thank you for announcing so clearly the solution for blueish-screen-bug!

Many people have been reporting this problem in the past, this thread is most welcome! :)
[Galaxy S I9000 Q&A, Help & Troubleshooting] kssthomas:
Thanks

Thanks for the help, I thought I will never be a new software! :D

[YOUTUBE]bwmSi6VYmLU[/YOUTUBE]
[Galaxy S I9000 Q&A, Help & Troubleshooting] need4steer:
Thanks a lot for both of you for your appreciation!

I'm glad that I'm able to help others.
[Galaxy S I9000 Q&A, Help & Troubleshooting] gameguard025:
Galaxy S i9000 display issue

Oops, Sorry need4steer for sending a PM to you.. I don't know I can post on this thread.. :)

By the way.. I figured what my problem is.. It's Screen Burn In.. That problem on screen I encountered was not only happening when playing flappy bird, it's noticeable on bright displays, tried some apps that can remove it.. I tried the "Screen Burn-In Tool" Tried it for 8 hours of non-stop color switching, but nothing changes at all.. Any remedies to remove the screen burn ins in my Galaxy S GT-I9000?

Thanks for the help! :)
[Galaxy S I9000 Q&A, Help & Troubleshooting] need4steer:
Hi

I'm not familiar with the screen burn in issue.

However, a Google search for i9000 screen burn in site:xdaforums.com or i9000 screen burn in on top site:xdaforums.com shows a lot of interesting threads in this forum.

In addition, since this thread is dealing with the bluish screen issue and not with the burn in issue, I think it'll be the best if you'll post a new thread in this forum so your problem will be exposed to others and they'll be able to give additional and more appropriate solutions.

BTW, it's always better to post screenshots, so be sure to include the ones you sent me in PM.

If you need any help whatsoever please notify me and I'll do my best :)

Good luck!
[Galaxy S I9000 Q&A, Help & Troubleshooting] tetakpatak:
Added link to this thread on the bottom of the OP of my i9000 guide:

http://xdaforums.com/showthread.php?t=2444308

Thank you for doing this, [MENTION=5157668]need4steer[/MENTION] :)
[Galaxy S I9000 Q&A, Help & Troubleshooting] need4steer:
Thanks a lot for your appreciation!

BTW, I just noticed that I didn't included your thread also under modified stock ROMs in the list of ROMs that we can flash.

Sorry about that :)

Users who know other ROMs who can work for devices with this bluish screen issue, and wish to add them to this list - please notify me (here or in PM) and I'll gladly add them.
[Galaxy S I9000 Q&A, Help & Troubleshooting] kssthomas:
Hello

Unfortunately, I do not like this version. ( cm-11-20140215-NIGHTLY-galaxysmtd.zip )

A bit choppy.

When dialing is very slow.

Camera handling is difficult for me. (Settings)

Settings Alarm disaster.

And there are some small flaw.

I have now use been to a factory ROM, as long as it will not be another.

But I thank you for your work, I hope you will have ROM is working well and there will be no blue screen.

We continually monitor and I see if someone will produce a new ROM again.

Sincerely kssthomas
[Galaxy S I9000 Q&A, Help & Troubleshooting] need4steer:
Yeah, I see what you're saying, though I believe it's an issue of how much available free memory you have.

I just don't allow too much to run in real-time - and then everything working pretty well.

Besides I'm truly love this ROM.

BTW, as I'm writing this I'm already flashing the updated cm-11-20140216-NIGHTLY-galaxysmtd.zip

Currently there are no too many AOSP ROMs we can you. However I already sent PM to a lot of developers so they'll implement the bluish screen fix in their future ROMs. A lot already responded that they'll do.

Stay tuned to the list of ROMs that we can flash - where I'll update new ROMs as often as they'll be available.

In the meantime you might want to use CyanogenMod 7.2 which gives you great Gingerbread 2.3.7 experience comparing the stock ROMs.
[Verizon Samsung Galaxy S III] daoist:
I am having a similar issue.

Can you check your logcat to see what's going on?

I'm getting a segfault in webview code. I believe my issue is only in apps which provide a webview (e.g. mostly apps which display ads).

There were a flurry of updates to the google stuff (google search, google play services) as well as to a bunch of xposed modules over the past couple days. Sometime after this I noticed my problems starting.
[Verizon Samsung Galaxy S III] awstuder:
This is actually my first time checking a logcat. What should i be looking for? I'm a little overwhelmed with all the colors and all the text in the one log that i made trying to open the app.

I filtered the log with the name of the app and also "seg" to see what i would get. CrashAnrDetector w/ the letter D inside a blue square that has (SEGV_ACCERR), fault addr #######.

was that what you were talking about? From what i could see there were crash reports with webview code when the app was opening up a website.

:fingers-crossed:
[Verizon Samsung Galaxy S III] BadUsername:
Sometimes xposed breaks apps or system ui. Disable it, reboot, and see if your problems persist, it's hard to read a logcat.
[Verizon Samsung Galaxy S III] ATGkompressor:
I had a similar problem, tried everything u guys have. Ultimately...Nandroid...never go wrong with a Nan handy. I haven't touched Wanam since I flashed wicked. My problems started with either the 2.7.3 Wanam update, the torch update or both.
[Verizon Samsung Galaxy S III] awstuder:
unfortunately i've tried disabling xsposed, uninstalling all the modules, reinstalling everything and rebooting everytime and the problem does persist.

:(
[Verizon Samsung Galaxy S III] awstuder:
I think i'll try that next. I used to have TWRP but had to flash the stock recovery just to upgrade to 4.3. I'll try to get a clean copy of stock OS, flash and just start over from scratch. I'll be sure to let you guys know if i got it to work.
[Verizon Samsung Galaxy S III] awstuder:
ran into a bump in the road. flashing a stock copy of android 4.0.4 did not work. Browsing through a few forums informed me that i'm unable to downgrade after i've taken the 4.3 upgrade. so next i tried to flash TWRP to boot into recovery mode and flash a rom from there. That didn't work either. I kept getting an authentification error.

As of now i can't get into download mode anymore. I get the yellow triangle saying Verizon detects unauthorized software. I'm able to get into recovery mode but i'm not sure what i can do with stock android recovery....

what can i do from here?

EDIT: I am able to get into download mode. I'm not sure why i wasn't before and now i am...

EDIT2: I have tried flashing the "official" stock android 4.3 but it fails everytime. I have also tried flashing twrp and cwm but i get a red Secure Check Fail: recovery. I suspect the bootloader has been locked. I'll look into ways of getting it unlocked again...
[Verizon Samsung Galaxy S III] BadUsername:
http://xdaforums.com/showthread.php?t=2586319
[Verizon Samsung Galaxy S III] daoist:
Same here. Disabling all xposed modules didn't work. Disabling xposed entirely didn't work. Doing both and then uninstalling didn't work. My guess is that along the way either xposed or wanam xposed made some sort of change that it can't roll-back when it's disabled/uninstalled.

I resorted to taking a TiBu update of everything and reflashing.

Once I get my battlestation fully armed and operational I plan on taking frequent nandroids and seeing if I can replicate the issue. Once I do that, (if I do) I can compare the last known good nandroid to see what messed up.
[Verizon Samsung Galaxy S III] awstuder:
I wasn't able to do this right away since had class in the morning but as soon as i got home, i did this and it fixed my soft-bricked phone.

thank you thank you!

Now back to the problem at hand......let's see if the problem still persists.
[Verizon Samsung Galaxy S III] awstuder:
It's completely fixed! No apps (so far :fingers-crossed:) have crashed and i'm able to happily play my games again! sigh. that was refreshing.

Thank you to everyone! i will edit my first post to outline what i did and how i fixed it, finally....
[Verizon Samsung Galaxy S III] rsswga:
during saferoot process your suppose to update SU then continue with finishing up the root process..took me several hours to figure this out..no errors now since I figured this out
[Verizon Samsung Galaxy S III] awstuder:
That... Actually makes sense. When I used safe root I didn't check for any other updates because I assumed the program took care of that for me. That and because when I opened su there were no notifications to update. So maybe that could be a solution as well.
[Verizon Galaxy Note 3 General] RoachHero:
I am very disappointed at the rate development is going for this phone. I thought sprint note 3 dev was dead. They had more development for the phone than the Verizon version. I switched.... should have stayed.
[Verizon Galaxy Note 3 General] Saythis:
It's because of Verizon.
[Verizon Galaxy Note 3 General] toddnbrown:
Could you be more specific? What functionality are you missing? I mean, is there some specific feature your phone doesn't have? Seems like you might just be bored. My Note 3 does about anything any other android phone can... and then some.
[Verizon Galaxy Note 3 General] shiftr182:
Smart thing to do would have been to check before you switch. Personally I like being able to make calls without losing them and having service everywhere. You have 14 days to go back.
[Verizon Galaxy Note 3 General] streetracer8605:
Safestrap allows for a lot of customization for roms and such. Part of the problem is the locked bootloader, and so far every person who starts a thread to crack it gets locked. People, one person more than others on here, seem to be against allowing anyone to unlock it and instead recommended people to drop over $700 on a "developer" device since they did and lock any thread that ventures away from that. Hopefully someone won't get too irritated by the attempts to block progress on here and will actually accomplish this instead of being lazy and just saying "go buy a developer device". Until then, thank goodness for safestrap and the roms we do have now.
[Verizon Galaxy Note 3 General] harrychimp:
+1

I was with Sprint for four years. I was constantly flashing ROMs, kernels, themes, etc. chasing a myth that there was Dev software out there that would improve Sprint service. I live in the 2nd largest metropolitan in the U.S. and I couldn't get service at stadiums and other highly populated events. It was downright frustrating and embarrassing having a flagship phone that couldn't send/receive texts, use data, and sometimes not even make calls. Yeah, I was duped by all the false Sprint advertising. But not any longer.

I like AOSP. But what I like more is a reliable service that allows my phone to work virtually everywhere.
[Verizon Galaxy Note 3 General] Naddict:
XDA is here to learn, hope you all take adavantage of the large amount of knowledge to help you in your plight to learn.
[7" Kindle Fire HD Q&A, Help & Troubleshooting] gokulshivin:
Hi to all... I have rooted my 7inch kindle fire HD, and it was working fine until I uninstalled the default launcher using titanium backup app downloaded from pay store. After uninstalling, I tried to restart the kindle, but from that time, whenever I restart the kindle, the 'kindle fire' logo is only displayed on the screen until the battery dies. Is there any way to just reinstall the default launcher app back to my kindle, when the screen displays only the logo?

Note: Before I uninstalled the default launcher, I copied the application from system/app to my internal memory.

Plz help
[7" Kindle Fire HD Q&A, Help & Troubleshooting] stunts513:
If you didn't have twrp recovery installed then no you have to get a fastboot cable and reflash a system image. On the bright side system images are prerooted, so you only have to reinstall the system apps again.