yashsingh1/xdaforums huggingface dataset:
[Android Q&A, Help & Troubleshooting] trippinz:
I have a HTC phone with HTC Sense, the dialer in Sense shows the recent calls then all your sim contacts. By mistake in an attempted effort to delete my google account contacts accidentally also deleted my sim contacts. However i can still see them in the call log (as i have mentioned before not in recent calls but under that where it shows all of my contacts). I can see the deleted contact's name and under it is a phone number but when i attempt to view the contact it says "contact not found".

Is there a way to recover my contacts from the list into a exported file (any format) or better still back into my phone?
[Nexus 7 Q&A, Help & Troubleshooting] leelaa:
I bougt a seven from currys uk on 16th july. I have discoverd i have screen lift down the left side. Who do i go o to return it? Or can i even return it at this point?
[Nexus 7 Q&A, Help & Troubleshooting] subvertbeats:
Just take it back there, show them the issue and demand an exchange :good:
[Nexus 7 Q&A, Help & Troubleshooting] leelaa:
Even though i bought it offline, i can take it back to my local store?
[Nexus 7 Q&A, Help & Troubleshooting] phillipm:
Yes you can just take it back to any currys store, even pc world.
[Nexus 7 Q&A, Help & Troubleshooting] jcsugrue:
You bought it offline... but not at a store? :confused:
[Nexus 7 Q&A, Help & Troubleshooting] bob_man_uk:
i had a similar problem with a phone i had bought recently from t-mobile.

you can take it back to the store you bought it from, if you have the receipt/bank statement proving purchase, it will be easier, though you dont always have to have this is you paid with a credit card.

just make sure that you return it to stock settings, remove root etc and they should accept it without question, well maybe one... whats wrong with it, they may say that it works fine even with the screen lift, simple say that its a manufacturing fault and you want a replacement.

if you get a particularly miffed "team" member simple ask to speak to their manager, i prefer to do this when its close to closing time as they tend to want you out sharpish.

im not 100% on the law but depending on how long you've had the device and how long it took you to notice the defect you may also want to take it to trading standards, usually advising currys of this if you end up hitting a brick wall says to them that you have at least read up on your consumer rights and arent willing to back down.

the trading standards website has a contact number if you want to talk it over with them

EDIT -> if you bought it "online" and you mean off-the-(internet)line then you might get away with returning it to the store, but your rights are actually different, they would be able to advise you on who to call to get your product returned, i didnt notice your message about buying it offline... and actually find it confusing.
[Nexus 7 Q&A, Help & Troubleshooting] leelaa:
Thanks for the help guys. I will be taking it tomorrow and shall demand a new one. Will put it back to stock/unroot and oem lock. Will also take all the papers that came when i got it delivered and a bank statement.

Very much appreciated. Thank you :)
[Nexus 7 Q&A, Help & Troubleshooting] subvertbeats:
YNWA lad :good:
[Nexus 7 Q&A, Help & Troubleshooting] leelaa:
YNWA ;)
[Kindle Fire Q&A, Help & Troubleshooting] Jared631:
Yes, another one of these issues. None of the other threads provided me any help, so new thread time! Allright, so I had just flashed a stock 6.3.1 Kindle Fire Rom. It all went well. Then I wanted to install FireFireFire Dualboot for other purposes, so i rebooted my Kindle fire first, (I always do this before I do anything rom/recovery related.) I went to adb shell on my computer told it to reboot into fasboot using "fastboot -i 0x1949 flash bootloader u-boot.bin" It boots into fastboot but, the bootloader diddn't seem to install and now my device can't be found on the KFU or standard ADB shell. I would appreciate any help on this issue as I need this kindle fire to be working. I have rebooted it 3 times too see if it could be found it just show "Unknown Device". Thanks, I can provide more info if the need be.
[Kindle Fire Q&A, Help & Troubleshooting] soupmagnet:
When you say, " the bootloader diddn't seem to install", could you be more specific?

What does your boot screen look like now?

Were there any error messages?

Did fastboot hang at "waiting for device"?

Do you have custom recovery installed?

Of so, what custom recovery do you have installed?
[Kindle Fire Q&A, Help & Troubleshooting] Jared631:
1. Boot screen is saying "KindleFire" the stock one not FFF.

2. No error messages

3. Yes, it hangs at "waiting for device"

4. No I don't

That's what I meant by "It diddn't seem to install".
[Kindle Fire Q&A, Help & Troubleshooting] soupmagnet:
Okay, the "waiting for device" simply means the drivers aren't working properly. I do not use Windows so I cannot offer any real help other than to tell you to reinstall them. There is a world of different suggestions for fixing the driver problem that you can find by searching the forums or even Google, but they're all hit and miss.

I will tell you to work on the driver issue until you can't take it anymore and then consider, possibly, other options.
[Kindle Fire Q&A, Help & Troubleshooting] Jared631:
Well, I might as well as just use soupkit, as I am dualbooting Ubuntu and Windows XP Pro. I have to wait a bit untill I can use it but, I have it all setup, so I'll get back too you when I get to try it out. If this doesn't work I will do the reinstall drivers, like you said, and hopefully that works. Thanks, for the help!

Update:

Soupkit diddn't work. (FK, not USBboot)

So, now onto Windows XP driver reinstallation.... Yay...

If this doesn't work I guess ill have to do the shorting trick.
[Kindle Fire Q&A, Help & Troubleshooting] Jared631:
Alright, So I did all of your suggestions, soupmagnet. None of them have worked, so I'm lead to beilive it's in some sort of state that won't allow it to be recognized on any ADB shell. I'm going to try the shorting trick, if that doesn't work then I'm pretty much screwed for all I know.

UPDATE:

Just too make sure it wasn't just my Lenovo computer, I pulled out my old gateway, setup the driovers correctly and everything. ( I tested too see if it detected my phone, it did) and it still diddn't detect my Kindle Fire, just said "Unknown Device"
[Kindle Fire Q&A, Help & Troubleshooting] Paced98:
I also have this same issue as well, was going to root my stock 6.2.1, but unplugged it on accident, no FFF, and stuck on the stock orange kindle fire logo.
[Kindle Fire Q&A, Help & Troubleshooting] soupmagnet:
With the device plugged in and powered up, in the Linux terminal, enter...

lsusb

You should see a device labeled either Lab 126 (normal mode) or Google Inc. (fastboot).

Also pay attention to the numbers assigned to the device. You should see one of the following sets:

1949:0006 (for normal mode)

18d1:0100 (for fastboot) -sorry for the typo: fixed-

Anything different will throw off the SoupKit, but it is still fixable.

If "lsusb" doesn't show anything of the sort, you may have bigger problems.
[Kindle Fire Q&A, Help & Troubleshooting] Paced98:
thanks, mine showed up what you wrote and changed to normal mode, and finally used ZombiePiratez unbrick tool and worked:good:
[Kindle Fire Q&A, Help & Troubleshooting] Jared631:
Thanks. I'll check that out. So to be clear it should just inform me of what mode it is in, correct? Not fix it.
[Kindle Fire Q&A, Help & Troubleshooting] soupmagnet:
What "lsusb" does, is tells you what USB devices are detected by the system. It doesn't fix anything. It's used a lot as a troubleshooting tool.
[Kindle Fire Q&A, Help & Troubleshooting] Jared631:
Yay.... Progeress?

Alright, here is what I got.

Bus 002 Device 003: ID 1949:0006 Lab126

So that means it is in normal mode, correct?

----------------------------------------------------------------------------------

Don't know if this helps but,
[Kindle Fire Q&A, Help & Troubleshooting] soupmagnet:
Correct. So, if you ran the SoupKit and rebooted afterwards, there's no reason it shouldn't work.

Since you are in normal mode, send "adb devices" and tell me what happens. Include error messages if any.

[Edit:] Apparently you posted the pics as I was writing this. This is very interesting. I've seen an issue like this in the not too recent past where a user had a BSOD in the middle of flashing the bootloader. It sort of hard-bricked his device except he could still power it on, but it would not accept commands for anything, and he had the same "unknown device" error. As far as I can remember, it was his bootloader that was messed up, even though it would still power up.

What does "lsusb" give you in fastboot mode?
[Kindle Fire Q&A, Help & Troubleshooting] Jared631:
Adb devices

This is what happens.

rainbowdash@RDE-Lenovo-G550:~$ adb devices
List of devices attached

rainbowdash@RDE-Lenovo-G550:~$ adb kill-server
rainbowdash@RDE-Lenovo-G550:~$ adb devices
* daemon not running. starting it now *
* daemon started successfully *
List of devices attached

rainbowdash@RDE-Lenovo-G550:~$
[Kindle Fire Q&A, Help & Troubleshooting] soupmagnet:
Also, what is the output of...

sudo /etc/udev/rules.d/51-android.rules
[Kindle Fire Q&A, Help & Troubleshooting] kinfauns:
Before you guys get too far off track...

1949:0006 is shared by the the stock system software, recoveries, CM7 based ROMs and the stock bootloader. These two numbers alone are insufficient to determine the "mode" of the device, so you might very well be in fastboot mode. If you get these numbers, you have to take a look at the bcdDevice value.

lsusb -v | grep bcdDevice

1.00 is the bootloader.

2.16 is one of the others.

More info here...

http://xdaforums.com/showthread.php?t=1668159
[Kindle Fire Q&A, Help & Troubleshooting] Jared631:
sudo /etc/udev/rules.d/51-android.rules

rainbowdash@RDE-Lenovo-G550:~$ sudo /etc/udev/rules.d/51-android.rules
sudo: /etc/udev/rules.d/51-android.rules: command not found
rainbowdash@RDE-Lenovo-G550:~$

Here is what I have in the file it's refering too.

# adb protocol for blaze / otter (Amazon Kindle Fire)
SUBSYSTEM=="usb", ATTR{idVendor}=="1949", ATTRS{idProduct}=="0006", MODE="0666", OWNER="root", GROUP="androiddev", SYMLINK+="android%n"

# fastboot protocol for blaze / otter (Amazon Kindle Fire)
SUBSYSTEM=="usb", ATTR{idVendor}=="18d1", ATTRS{idProduct}=="0100", MODE="0660", OWNER="root", GROUP="androiddev", SYMLINK+="android%n"
[Kindle Fire Q&A, Help & Troubleshooting] soupmagnet:
Sorry, I left out "gedit". It should be "sudo gedit /etc..." oh well, whatever.

Either way, that much is correct. It's a tricky situation with stock software because, the boot logo and boot animation are basically the same, and as kinfauns has said, the two modes share the same IDs. But in your case, you can't send either fastboot or adb commands, which makes for an interesting situation. Your udev rules are configured properly for the device, so other than it being in fastboot with a partially broken bootloader, I can't imagine what would cause it to not connect properly.

Definitely use the command that kinfauns gave you and find out what mode you are in. If you are in fastboot, it would seem that your bootloader is corrupt in some way and you would have to use the Firekit to fix it.

As far as I know, if you are using the "shorting trick" correctly to boot the device in USBboot mode, the Firekit should work regardless. (Someone correct me if I'm wrong)

I knew that. I just forgot, that's all. ::looks around::
[Kindle Fire Q&A, Help & Troubleshooting] Jared631:
I'm going to use the "shorting trick" as a last resort. It's looking like I will anyways. I will post as soon as I get that mode (USB cord is being used at the moment)
[Kindle Fire Q&A, Help & Troubleshooting] soupmagnet:
If (when) you try the shorting trick, it's best to use a sharp pair of tweezers or a safety pin to keep from losing the connection while plugging the USB cable in. And the picture of the actual point posted on Pokey's thread is a little misleading...it's considerably smaller.
[Kindle Fire Q&A, Help & Troubleshooting] Jared631:
Ok! I will make sure to do that.
[Kindle Fire Q&A, Help & Troubleshooting] Jared631:
Alright

Heres what I got after running: lsusb -v | grep bcdDevice

rainbowdash@RDE-Lenovo-G550:~$ lsusb -v | grep bcdDevice
Couldn't open device, some information will be missing
Couldn't open device, some information will be missing
Couldn't open device, some information will be missing
Couldn't open device, some information will be missing
bcdDevice 3.02
bcdDevice 3.02
bcdDevice 3.02
Couldn't open device, some information will be missing
Couldn't open device, some information will be missing
bcdDevice 3.02
bcdDevice 3.02
Couldn't open device, some information will be missing
Couldn't open device, some information will be missing
bcdDevice 3.02
bcdDevice 3.02
bcdDevice 3.02
Couldn't open device, some information will be missing
bcdDevice 14.10
bcdDevice 1.00
rainbowdash@RDE-Lenovo-G550:~$

Were we looking for this?

bcdDevice 1.00
[Kindle Fire Q&A, Help & Troubleshooting] kinfauns:
Sorry... I never have many USB devices attached, so it's pretty obvious for my setup. You obviously have a lot more. Do this...

lsusb -vd 1949:0006 | grep bcdDevice

to limit the output to only that particular device.

Yes, I believe you will see 1.00 again, which means your bootloader still has control of the device and that almost always means you are in fastboot mode. Make sure your KF is not plugged into a USB 3.0 port, you'll need to have it in a USB 2.0 port. Run this command...

fastboot -i 0x1949 getvar product

If it tells you that it's waiting for device, force the KF to turn off by pressing and holding the power key until it powers down. Then turn it back on again. If you get a response, then you are in fastboot and you can run fastboot commands.
[Kindle Fire Q&A, Help & Troubleshooting] Jared631:
....

When I ran

lsusb -vd 1949:0006 | grep bcdDevice

rainbowdash@RDE-Lenovo-G550:~$ lsusb -vd 1949:0006 | grep bcdDevice
bcdDevice 1.00
rainbowdash@RDE-Lenovo-G550:~$

--------------------------------------------------------------------------------

The lenovo G550 Only has USB 2.0 ports, I checked that before I started anything. When I ran

fastboot -i 0x1949 getvar product

rainbowdash@RDE-Lenovo-G550:~$ fastboot -i 0x1949 getvar product
< waiting for device >
((Rebooted))
product: kindle
rainbowdash@RDE-Lenovo-G550:~$

Does this mean anything?

EDIT: Whoops, sorry about that. Thanks Soupmagnet.
[Kindle Fire Q&A, Help & Troubleshooting] soupmagnet:
You entered the command wrong.

product, not produc
[Kindle Fire Q&A, Help & Troubleshooting] Jared631:
I edited my post.

Thanks, I hadn't noticed that.
[Kindle Fire Q&A, Help & Troubleshooting] soupmagnet:
[Edited:] See below
[Kindle Fire Q&A, Help & Troubleshooting] Jared631:
I just want to thank you guys some much.

rainbowdash@RDE-Lenovo-G550:~$ fastboot -i 0x1949 flash bootloader u-boot.bin
sending 'bootloader' (203 KB)... OKAY
writing 'bootloader'... OKAY
rainbowdash@RDE-Lenovo-G550:~$ adb devices
* daemon not running. starting it now *
* daemon started successfully *
List of devices attached

rainbowdash@RDE-Lenovo-G550:~$ adb devices
List of devices attached
2182000600000001	recovery

rainbowdash@RDE-Lenovo-G550:~$

I couldn't have achived this without you.
[Kindle Fire Q&A, Help & Troubleshooting] soupmagnet:
Before you get ahead of yourself, though, let's take we a look at the situation. You're trying to dual boot your Kindle, which is fine, but takes slight bit more experience than what you're probably used to. Not so much to actually do it, but to understand what is really happening with your device and why the dual boot works.

Before you flash a new bootloader, I suggest you flash a custom recovery first, and flash FFF1.4 while in recovery to make sure everything is running correctly. And before you get in over your head, do some research on repartitioning to get an idea of how to fix any problems as they arise. A great place to go, is Hashcode's Clockwork Recovery thread. There is a lot of knowledge and experience in that thread and I personally learned a lot from it.

---------- Post added at 11:39 AM ---------- Previous post was at 11:31 AM ----------

Also, since your device is working as it should, I'm very interested to know if your Linux works to send commands after installing Soupkit. I would like to identify and eliminate any problems that would keep it from working properly.
[Kindle Fire Q&A, Help & Troubleshooting] Jared631:
Thanks!

I have TWRP and FFF 1.3 installed as of right now. I looked at 1.4a and got the flashable .zip I shall try that. Thanks alot man.
[Kindle Fire Q&A, Help & Troubleshooting] Jared631:
Alright, I was having issues with the .zip So, I just flashed the bootloader manually. I'd like to thank you for making me decide to use Ubuntu as my Main OS again. (I stopped thinking it was to difficult. Now, I love it, much simpler than Windows XP for the things I do.)

EDIT: Yeah soupkit works fine, what type of /errors/ are you looking for?
[Kindle Fire Q&A, Help & Troubleshooting] soupmagnet:
The "not working" kind. It works for you so I'm happy. Good luck on future endevors.
[Kindle Fire Q&A, Help & Troubleshooting] Jared631:
Thanks. Again.

Thanks, and you probably have no idea how glad I am to have had received help with this. (I thought I was screwed.) :highfive:
[Kindle Fire Q&A, Help & Troubleshooting] fmilovanov:
uates its

Folks - I have a problem with my KF. A while ago I've rooted it, installed FFF and TWRP via KFU (Kindle Fire Utility) and installed CM9 on it. Today I tried to install Jelly Bean on it, and since among prerequisites was TWRP 2.1+/2.2, tried to install it. I completely forgot about KFU and tried to follow instructions from TRWP page:

teamw.in/project/twrp2/79

Foolishly, I did not realize that fastboot -i 0x1949 flash recovery openrecovery-twrp-2.2.0-blaze.img should be run from a command line and I run it from adb shell - it gave me some error and I restarted my KF. Expectedly, it went into fastboot mode (yellow triangle on boot) - but I now can't connect to it: none of KFU tools (Bootmode menu, Install FFF, etc) sees it (as well as fastboot tool itself) - I get < waiting for devive > message and nothing happens. Tried adb shell - device not found, adb devices shows empty list.

What should I do? All these tools (fastboot, adb) saw the Kindle before, now they don't. And my Windows now gives me USB Device Not Recognized error. Looked and Device Manager - DeviceID for it is 18D1.

Please help :cowboy:

---------- Post added at 09:09 PM ---------- Previous post was at 08:58 PM ----------

Oops.... problem was solved once I've manually re-installed drivers from the latest KFU download.
[Galaxy S III Q&A, Help & Troubleshooting] mister_schaffner:
Hi

Accidentally bought a device with a box and all from Ebay and I noticed that the seller wrote the IMEI number

Invalid.

Bottom line I get the number GENERIC "004999010640000/01"

Is there any chance someone could help me? The device is GT-I9300 International

Of course I do not have a backup of the original EFS folder ..???

:crying:
[Galaxy S III Q&A, Help & Troubleshooting] large12006:
Sounds like a cheap chinese knock off too me. The IMEI is hardwired into the device and shouldn't be gone. Unless the seller has fluffed up the EFS folder. Get it sent back pronto boss
[Galaxy S III Q&A, Help & Troubleshooting] speedyjay:
+1 their is no way to change the imei so that sounds like the Chinese dual core to me buddy
[Galaxy S III Q&A, Help & Troubleshooting] pepi1234:
Delete efs folder with root explorer reboot your phone and it will be back there is a backup in the factory folder from there it wil be restoret

---------- Post added at 10:28 PM ---------- Previous post was at 10:20 PM ----------

i use the Galaxy S III (international version). Do i need to backup my IMEI with QPST as refer in this post [FIX/TOOL] Backup/Restore/Fix IMEI App v1.2.2.2b now available - Updated 8/04/2012!!!?

The ROM of my SGS3 is CM9.0, when i follow the instruction in the post to run the script to let my phone enable to DIAG mod, the fail feedback from the terminal prompt shown NOT EXIST DICTIONARY.

echo smd,bam > /sys/class/android_usb/android0/f_rmnet/transports f_rmnet NOT EXIST

echo diag > /sys/class/android_usb/android0/f_diag/clients f_diag NOT EXIST

so I doubt the original post unavailable for the SGS3 i9300.
[Galaxy S III Q&A, Help & Troubleshooting] ag4751:
Have a look here,may help

http://xdaforums.com/showthread.php?t=1264021
[Galaxy S III Q&A, Help & Troubleshooting] mister_schaffner:
I try this and its dont help i have the same generic IMEI

:crying:
[Galaxy S III Q&A, Help & Troubleshooting] Chaitanyapatel8880:
I have tried EACH AND EVERY POST here regarding restoring the IMEI and NONE of them helped me. All of them are made if you have EFS BACKUP. Best Solution. Send it back.. I hope you have return back guarantee...
[Galaxy S III Q&A, Help & Troubleshooting] ceo.mtcl:
You have 45 days to return the phone based upon the return policy of eBay. Tell them that yiuvget no signal with the phone when yiuvget use it. They will make a return immediately.
[Galaxy S III Q&A, Help & Troubleshooting] spocky12:
If you didn't return you phone to warranty yet, follow this procedure :

- make a backup of your current efs folder (tar AND partition IMG) using EFS Pro.

- send me those files by pm.

- if you are lucky (and I have some free time), I might be able to restore your imei :fingers-crossed:
[Galaxy S III Q&A, Help & Troubleshooting] zeek333:
Hi

I have same prob with IMEI :crying:

I was trying different roms and rename a .nv_data.bak nothing helps

On this forum some ppl suggested to do some changes in nv_data.bin but for galaxy s2 and I have s3

The thing is i can't find IMEI 004999010640000 in hex on nv_data.bin. I think in hex it should be 48bec40e080

does any1 got idea where this IMEI 004999010640000 is located?
[Samsung Galaxy Tab Plus] pirateradio:
Excuse, no permissions to write in Developer Forum. So i ask here...

First thanx to the very good development of cm for the galaxy tab!

Using cm-10-20120830 there is some trouble with compass alignment. No correct value for north before and after compass alignment.

No fix in GPS apps. Getting correct current position but nix fix status in applications like gps essentials.

Any suggestions?

greets pirate
[Samsung Galaxy Tab Plus] gingerboy92:
try using gps status from playstore to calibrate the compass, not sure if that will work.. there's something wrong with the gps on mine too.. about 20KM/h off from the actual speed(was driving at ~100KM/h, but the app only shows ~80KM/h, was using sygic and gps status for the speed, about the same reading)
[Samsung Galaxy Tab Plus] pirateradio:
Problem with compass:

After some more 'alignment' (rotating the tab in all axis) i have a correct compass reading in 'gps essentails'

- but - a wild changing and not correct north in 'gps status' app!

Whats that? :confused:

Problem with gps fix:

Correct coordinates shown in all apps - but - in no application there is a fix.

'gps status' shows 4 satellites ( i am shure there were more in stock) in view. But lock shows 0, also after longer time. So i think no problem with agps data, only with 'fix' announcement. When i start the app there is also a short popup saying 'locked in 9 seconds'.

I am confused!
[Samsung Galaxy Tab Plus] gingerboy92:
looks like we have problem here. 4 satellites, 9 secs lock. but no actual lock showing.
[Samsung Galaxy Tab Plus] mcgleevn:
I am glad to see I'm not the only one noticing compass issues... my Google Sky Map refuses to work!

Anywho, I did the whole 'back to stock and get a lock' to no avail.
[LG Optimus Me P350] rickyreyne:
MAY PASS THIS ROM: http://xdaforums.com/showthread.php?t=1836116, to p350?:confused:
[LG Optimus Me P350] ahirwar:
jb

you need to wait for jb rom on p350, because some great dev like ron gokhle, keyur maru (rom2maru) and Venkat kamesh working on it :)
[LG Optimus Me P350] Ron G:
sorry but no one are working on jb for now
[LG Optimus Me P350] ahirwar:
oops

Oops