Develop Bugs

[Q]Another Bricked Kindle Thread: No Pwer, wont turn on

Hello
Im now the proud owner of a bricked first gen kindle fire. I decided to go ahead and successfully installed this ROM on my device. After messing around with the apps the screen froze, i decided to do a hard reset and now my device wont turn on and im not seeing any lights when its plugged in. After some investigation ive come to the conclusion that the device has a bootloader error of some kind. Ive tried using fire kit and the shorting trick to get around this issue but its seems that im out of my depth. Im messed around with "soupkit" and have gotten the drivers installed on my linux distro (ubuntu) howver when i run "adb devices" im not seeing my device. I occassionally see the device pop up in my listing when i run "lsusb" however.
any help would be greatly appreciated.

what you linked as a rom is not a rom unless you flashed update.zip but everything would surely go wrong if you flashed the kindle fire utility??? Power on issues are usually from a completely dead battery. It could fail to turn on depending on what you did flash if it was way off the chart incorrect. So I`m confused about your post you must clarify. You will certaily need firekit to repair if it fails to power on with a full battery pm me I will try to assist you in fixing your completely brain dead device.

0beah said:
Hello
Im now the proud owner of a bricked first gen kindle fire. I decided to go ahead and successfully installed this ROM on my device. After messing around with the apps the screen froze, i decided to do a hard reset and now my device wont turn on and im not seeing any lights when its plugged in. After some investigation ive come to the conclusion that the device has a bootloader error of some kind. Ive tried using firekit and the shorting trick to get around this issue but its seems that im out of my depth. Im messed around with "soupkit" and have gotten the drivers installed on my linux distro (ubuntu) howver when i run "adb devices" im not seeing my device. I occassionally see the device pop up in my listing when i run "lsusb" however.
any help would be greatly appreciated.
Click to expand...
Click to collapse
The "shorting trick" will work...but rarely on the first shot. Keep trying and don't give up.
A few things to note before trying the shorting trick:
* Be sure you aren't using a USB 3.0 port
* Make sure the power is completely off. Even if there are no outward signs of life, the device can still be on and the Firekit will fail. Hold the power button for 15 seconds or so to make sure there is no power to the device before plugging in and attempting the shorting trick.
* Be sure you fully understand the instructions in the Firekit/Rekindle threads. There is important information there that can easily be overlooked if you aren't attentive.
Unfortunately, the USBboot method is one of the few things you're completely on your own with. No one here can help you with it. That being said, it's one of those things you just need to be persistent with it. Everyone I've seen use the Firekit, has succeeded, eventually.

shorting trick again.
So I've done the shorting trick again. Connected the 3rd dot on the board to the metal case around it. Fire kit sees something obviously and my usb port pick up this:
Bus 001 Device 016: ID 0451:d00f Texas Instruments, Inc.​
Still no light still no power and fire kit moves from:
waiting for OMAP44xx device...​
to:
< waiting for device >​
and just hangs there. I've been informed that for custom roms it will take a while, but how long is that exactly? i've left it there fro roughly about half an hour.
advice?

0beah said:
So I've done the shorting trick again. Connected the 3rd dot on the board to the metal case around it. Fire kit sees something obviously and my usb port pick up this:
Bus 001 Device 016: ID 0451:d00f Texas Instruments, Inc.​
Still no light still no power and fire kit moves from:
waiting for OMAP44xx device...​
to:
< waiting for device >​
and just hangs there. I've been informed that for custom roms it will take a while, but how long is that exactly? i've left it there fro roughly about half an hour.
advice?
Click to expand...
Click to collapse
BTW the rom i used was gotten from here

Yeah leaving it <waiting for device> really does nothing If you dont get any action within 3 or 4 mins start the procedure again. You must keep the short until it runs through as well 30 mins is overkill. Make sure you are contacting the correct test point here it is shown circled in red http://forum.xda-developers.com/showpost.php?p=19762674&postcount=51 .

Thepooch said:
Yeah leaving it <waiting for device> really does nothing If you dont get any action within 3 or 4 mins start the procedure again. You must keep the short until it runs through as well 30 mins is overkill. Make sure you are contacting the correct test point here it is shown circled in red http://forum.xda-developers.com/showpost.php?p=19762674&postcount=51 .
Click to expand...
Click to collapse
Yeah thats exactly what i did. Unfortunately im busy with work now but im gonna leave it plugged in and the fire kit running for the rest of the day and see if there's any change.

You can leave it plugged in for 10 years and firekit running and if your not shorting it there never will be a change.

same hinesAn
So I'm definitely not sure if I'm shorting this properly. I have set up a pin to touch the point and the frame to leave my hands free. Running some diagnostics. Not sure if its relevant but I'm in the 11.10 environ of ubuntu btw. I'm noticing the device keeps getting disconnected by the system with the following message:
device: 38 was not an MTP device
USB disconnect, device number 38
checking on some libmtp things maybe the issue is that my linux install just doesn't recognize the device?

Use the intel 86 desktop CD image http://releases.ubuntu.com/precise/

Okay so ive made a live cd off of the link provided (cant make a bootable usb at the moment). Same issue as before except now i get the following according to th logs:
[ 3824.857537] usb 1-1.2: new high-speed USB device number 24 using ehci_hcd
[ 3824.950355] usb 1-1.2: unable to get BOS descriptor
[ 3825.427367] usb 1-1.2: USB disconnect, device number 24​

A live CD will not work because of persistent only a live USB has this capability sorry. You could try my iso its possible that it may work as a live CD http://forum.xda-developers.com/showthread.php?t=1413358 post 7 but I have never tested use the per instructions to created the CD. Sorry for the large download but its totally prefab create boot and use nothing else needed. The way you're doing it when you reboot no Soupkit changes will be saved to the CD.

Thepooch said:
A live CD will not work because of persistent only a live USB has this capability sorry. You could try my iso its possible that it may work as a live CD http://forum.xda-developers.com/showthread.php?t=1413358 post 7 but I have never tested use the per instructions to created the CD. Sorry for the large download but its totally prefab create boot and use nothing else needed.
Click to expand...
Click to collapse
Im sorry im not following exactly why i NEED persistent? is it only the adb drivers? cause ive gotten those dld via PPA. Just would like to now out of curiosity really. Regardless i'll grab a 4gb USB ASAP.

The persistent or Casper r/w allows for changes to be save between reboots on a live USB that's why it will not work on a CD because no data including udev rules aren't preserved. Soupkit is intended to either be ran on a live USB or a full install. I recommended 12.04 because through the process of testing Soupkit well over 200 times that I found there to be some mild issues that accompanied the use of 11.10. I tested every viable distro that allowed for persistent xubuntu,kubuntu, multiple distros of Ubuntu and Linux mint mate and found that 12.04 Ubuntu and Linux mint mate 32 bit worked the very best with less hassles to the user.

rsomeoe Having
I now have 12.04 tried running the firekit tool while doing the "shorting trick". Still no change as from before. Still getting:
[ 716.828012] usb 1-2: new high-speed USB device number 8 using ehci_hcd
[ 716.960808] usb 1-2: unable to get BOS descriptor
[ 719.962054] usb 1-2: USB disconnect, device number 8​

0beah said:
I now have 12.04 tried running the firekit tool while doing the "shorting trick". Still no change as from before. Still getting:
[ 716.828012] usb 1-2: new high-speed USB device number 8 using ehci_hcd
[ 716.960808] usb 1-2: unable to get BOS descriptor
[ 719.962054] usb 1-2: USB disconnect, device number 8​
Click to expand...
Click to collapse
So i now have a pen drive. installed soupkit. ran the firekit install on in and now im now stuck at "waiting for device:". Any assistance?

[Q] Kindle 1st gen working BUT "Unknown Device" in Device Manager

Hi all.
I have seen this in another kind of devices but haven't found thread related about Kindle Fire (1st gen).
A little introduction:
- My kindle was in CM10 and I noticed it started to be detected as Unknown Device in Windows, so
- I used TWRP to flash 6.3.1 stock ROM BUT forgot to wipe before flashing and rebooting. In that moment my situation was an endless loop wih the Kindle being rebooted after 15 seconds aproximately.
- I modified a cable to make it "factory cable" but even in fastboot (plain kindle fire logo) the Unknown Device was there.
- After many tries I managed to make a Reset to factory defaults in Android in the 15 seconds
- Currently the kindle is in stock ROM but still is not correctly detected.
Of course, I have re-installed the drivers in my computer and even tried in a fresh windows installation with no previous drivers without luck. Also, booted an Ubuntu USB with SoupKit and no lsusb changes after plugin the device (just a few dmesg messages about being unable to enumerate USB device on port).
So, if some of you have any idea to try, please tell me. I have the factory cable and the back cover of the kindle removed... ready for anything!
Thank you for your time!

soukron said:
Hi all.
Also, booted an Ubuntu USB with SoupKit and no lsusb changes after plugin the device (just a few dmesg messages about being unable to enumerate USB device on port).
Click to expand...
Click to collapse
This is the part I mentioned before about dmesg messages:
Code:
[ 234.956030] usb 2-5: >new full-speed USB device number 4 using ohci_hcd
[ 235.136035] usb 2-5: >device descriptor read/64, error -62
[ 235.420038] usb 2-5: >device descriptor read/64, error -62
[ 235.700026] usb 2-5: >new full-speed USB device number 5 using ohci_hcd
[ 235.880055] usb 2-5: >device descriptor read/64, error -62
[ 236.164040] usb 2-5: >device descriptor read/64, error -62
[ 236.444025] usb 2-5: >new full-speed USB device number 6 using ohci_hcd
[ 236.852030] usb 2-5: >device not accepting address 6, error -62
[ 237.028025] usb 2-5: >new full-speed USB device number 7 using ohci_hcd
[ 237.436025] usb 2-5: >device not accepting address 7, error -62
[ 237.436037] hub 2-0:1.0: >unable to enumerate USB device on port 5
And there's no reference in lsusb:
Code:
[email protected]:~$ lsusb
Bus 001 Device 004: ID 1307:0163 Transcend Information, Inc. 256MB/512MB/1GB Flash Drive
Bus 001 Device 005: ID 0bda:8187 Realtek Semiconductor Corp. RTL8187 Wireless Adapter
Bus 002 Device 002: ID 04ca:0022 Lite-On Technology Corp.
Bus 002 Device 003: ID 046d:0a0b Logitech, Inc. ClearChat Pro USB
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
[email protected]:~$ lsusb -t
/: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=ohci_hcd/10p, 12M
|__ Port 3: Dev 2, If 0, Class=HID, Driver=usbhid, 1.5M
|__ Port 4: Dev 3, If 0, Class=audio, Driver=snd-usb-audio, 12M
|__ Port 4: Dev 3, If 1, Class=audio, Driver=snd-usb-audio, 12M
|__ Port 4: Dev 3, If 2, Class=audio, Driver=snd-usb-audio, 12M
|__ Port 4: Dev 3, If 3, Class=HID, Driver=usbhid, 12M
/: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci_hcd/10p, 480M
|__ Port 9: Dev 5, If 0, Class=>ifc, Driver=rtl8187, 480M

From what I've seen, this is usually a problem with the bootloader. How or why, I don't know. That being said, Firekit w/shorting trick seems to be the most successful at resolving this issue.

soupmagnet said:
From what I've seen, this is usually a problem with the bootloader. How or why, I don't know. That being said, Firekit w/shorting trick seems to be the most successful at resolving this issue.
Click to expand...
Click to collapse
I'm trying to follow this thread http://forum.xda-developers.com/showthread.php?t=1636883 but I don't know how to check if the "short trick" is well performed or not. Is there anything I should notice? At this moment if I make the short trick and plug in the usb connector, nothing seems to be working in the kindle but dmesg is continuously showing errors like previous ones.
Regards,

Are you using Firekit? What command?
"That's a special kind of stupid. The kind that makes me laugh"

I'm still in the step of the process when I make the short trick, plug the usb and the kindle should be detected. Should I try the usbboot commands even when there's no kindle entry in lsusb output?

YES absolutely! And hold the power button for 15 seconds to make sure the CPU isn't running before attempting the short.
"That's a special kind of stupid. The kind that makes me laugh."

soupmagnet said:
YES absolutely! And hold the power button for 15 seconds to make sure the CPU isn't running before attempting the short.
Click to expand...
Click to collapse
The command is ./usbboot aboot.bin u-boot.bin; ./fastboot boot twrp-blaze-2.0.0RC0.img but it keeps stopped in waiting for OMAP44xx device....
I'm going to try a few times more. Thank you!
BTW, what are the next steps? Because this unit is working properly but the USB port to transfer data between computer and device: it boots, it loads stock firmware, and works properly.

soukron said:
The command is ./usbboot aboot.bin u-boot.bin; ./fastboot boot twrp-blaze-2.0.0RC0.img but it keeps stopped in waiting for OMAP44xx device....
I'm going to try a few times more. Thank you!
BTW, what are the next steps? Because this unit is working properly but the USB port to transfer data between computer and device: it boots, it loads stock firmware, and works properly.
Click to expand...
Click to collapse
Are you using a 32bit or 64bit machine? If you have SoupKit installed, option 2 should have installed 32bit libs, but sometimes it fails...mostly due to Ubuntu servers and them trying to make 32bit libs obsolete. If you're running a 64bit machine, try installing 32bit libs again and see if you get any errors.
Code:
sudo apt-get install ia32-libs
Also since you have SoupKit installed, run it and select option 4 to launch the Firekit. There's really no difference in using Firekit and manually entering the commands for Rekindle but it makes things a little easier. Select "usb_install_fff_twrp". The important thing to know about the "usb_fix_parts..." and "usb_install..." commands in Firekit is that they both use "fastboot boot ..." instead of "fastboot flash ..." to install TWRP and FFF. Meaning, if you reboot or shut the device down before actually installing a bootloader, the device won't turn back on and you'll have to do the shorting trick again.
That being said, from the moment you make the short, you only have about 2 seconds to plug the device in and have Linux detect it before the CPU resets and you have to start all over again.
Hold the power button for 10-15 seconds to make sure the CPU is off before attempting the short.
Launch Firekit and select "usb_install_fff_twrp". When the command is run, you will get the "Waiting for OMAP4 device..." prompt. Let it wait.
To do the shorting trick...
Something I have found to be most useful in this situation is to use a sharp pair of tweezers or safety pin to make the short.
Keep the device flat on a desk or table with the USB connection pointed away from you. Use one hand to hold the short, one hand to plug the device in, and use your body against the other end of the device as leverage as you plug it in.
Using a safety pin, stick the sharp end of the safety pin into the short point and press it in a little to keep it from sliding off when you plug the device in. Squeeze the other end of the safety pin or tweezers to make contact with the metal frame and immediately plug the device in while holding the short.
If the tweezers slip or make contact with the frame before you are ready, hold the power button for 10-15 seconds to make sure the device is completely shut down and try again.
You should see something going on in the terminal to let you know it's working...let it finish.
It might take a few attempts to get the timing right but persistence (and practice) is key...don't give up.
Follow these instructions and I'm positive you'll get it working again. Good luck.

OK, it's a matter of time and try it.
My computer is 64bit, but I am booting a LiveUSB with Ubuntu 12.10 32bits, so no problem around it.
About the short, one friend of mine solded a thin wire in the point in the board and I only have to connect the other side to the wire to the frame each time, so it also seems to be fine. http://forum.xda-developers.com/attachment.php?attachmentid=1045562&d=1336355873
My main concern: once I manage to make properly the short trick and the process goes forward, what will be the next step? What should I expect of this usb_install_fff_twrp command? Will it fix the hardware detection problem automatically?
Thank you again for all your help, I know you answer a lot this kind of questions and your help is very valuable.

soukron said:
OK, it's a matter of time and try it.
My computer is 64bit, but I am booting a LiveUSB with Ubuntu 12.10 32bits, so no problem around it.
About the short, one friend of mine solded a thin wire in the point in the board and I only have to connect the other side to the wire to the frame each time, so it also seems to be fine. http://forum.xda-developers.com/attachment.php?attachmentid=1045562&d=1336355873
My main concern: once I manage to make properly the short trick and the process goes forward, what will be the next step? What should I expect of this usb_install_fff_twrp command? Will it fix the hardware detection problem automatically?
Thank you again for all your help, I know you answer a lot this kind of questions and your help is very valuable.
Click to expand...
Click to collapse
When the OMAP4 device is detected, you will see something similar to this in the terminal:
http://forum.xda-developers.com/attachment.php?attachmentid=1262650&d=1345043823
That will temporarily install the bootloader, which is likely the cause of Linux not being able to detect it in the first place. When you see the yellow triangle on your Kindle, you'll know the Firekit worked. But you still have to permanently install the bootloader via fastboot (or TWRP if accessible) before you reboot the device.
Will it work to get Linux to detect it? Most likely, but there's no way to know for sure until you get a new bootloader installed.
On second thought...
I just realized you may not even have to do that in the first place. Lucky you? If your device is working properly as you said, boot into Android and open up the Terminal Emulator. Make sure the u-boot.bin is on your sdcard and enter the following:
Code:
su
dd if=/sdcard/u-boot.bin of=/dev/block/mmcblk0p2
reboot
See if that works.

Yes, working with stock ROM but without root access. If there's any way of rooting it without connecting it to the computer I can do it and then use dd to override the block device.

soukron said:
Yes, working with stock ROM but without root access. If there's any way of rooting it without connecting it to the computer I can do it and then use dd to override the block device.
Click to expand...
Click to collapse
Nope...you need root access to use the 'dd' command.

soupmagnet said:
Nope...you need root access to use the 'dd' command.
Click to expand...
Click to collapse
Dude, thank you for your all work but I'm giving up. I'll close it and use it without data cable. I always can use dropbox like applications to transfer data.
Again, thank you, I really appreciate your help.

soukron said:
Dude, thank you for your all work but I'm giving up. I'll close it and use it without data cable. I always can use dropbox like applications to transfer data.
Again, thank you, I really appreciate your help.
Click to expand...
Click to collapse
If y wer on windows, u could have just grabbed a copy of kindle fire utility and had rooted it in merely seconds..
Sent from my GT-I8350 using Board Express

prahladvarda said:
If y wer on windows, u could have just grabbed a copy of kindle fire utility and had rooted it in merely seconds.
Click to expand...
Click to collapse
Unfortunately, it won't work in this situation.

[Q] Phone doesn't boot

Hey community,
I have big problems with my Fairphone.
It doesn't boot, it happens nothing, totally black screen, no fairphone logo, no system popup...
I turned it off yesterday and since then I've got this issues.
I tried :
-every key combination but nothing happened
-to connect it with my computer and charger but nothing happened, no sign, no LED signal
-removed battery and sim card
I didn't make something unusual, only turned it off, so can anyone please help me?
Thanks in advance

DarkerTimes said:
Hey community,
I have big problems with my Fairphone.
It doesn't boot, it happens nothing, totally black screen, no fairphone logo, no system popup...
I turned it off yesterday and since then I've got this issues.
I tried :
-every key combination but nothing happened
-to connect it with my computer and charger but nothing happened, no sign, no LED signal
-removed battery and sim card
I didn't make something unusual, only turned it off, so can anyone please help me?
Thanks in advance
Click to expand...
Click to collapse
Hi can you try if the recovery mode still works? (e.g turn off the phone and power it on by keeping the power and volume up button pressed).
If that doesn't work try removing the battery and connecting the device to a Linux PC and see if a new device appears (by running dmesg). Do you see a device appear?

_keesj said:
Hi can you try if the recovery mode still works? (e.g turn off the phone and power it on by keeping the power and volume up button pressed).
If that doesn't work try removing the battery and connecting the device to a Linux PC and see if a new device appears (by running dmesg). Do you see a device appear?
Click to expand...
Click to collapse
Hi,
recovery mode doesn't work, the phone is completely dead.
Then I will try your tip with the Linux PC. But first I have to find one^^
I will tell you when i have access to a linux computer and when it gets the device.
Thanks for your help
Gesendet von meinem GT-I9505 mit Tapatalk

DarkerTimes said:
Hi,
recovery mode doesn't work, the phone is completely dead.
Then I will try your tip with the Linux PC. But first I have to find one^^
I will tell you when i have access to a linux computer and when it gets the device.
Thanks for your help
Gesendet von meinem GT-I9505 mit Tapatalk
Click to expand...
Click to collapse
You might like to know that you can run many versions of Linux directly from a DVD drive or USB drive. A popular one, and probably the easiest, is: http://www.ubuntu.com/desktop
To "run dmesg", as suggested by @_keesj, do the following:
Start Ubuntu
When the desktop is open, press the Windows key.
Connect your phone.
Type "Terminal".
Press Enter or click the Terminal icon.
Type dmesg, press Enter.

Vinnl said:
You might like to know that you can run many versions of Linux directly from a DVD drive or USB drive. A popular one, and probably the easiest, is: http://www.ubuntu.com/desktop
To "run dmesg", as suggested by @_keesj, do the following:
Start Ubuntu
When the desktop is open, press the Windows key.
Connect your phone.
Type "Terminal".
Press Enter or click the Terminal icon.
Type dmesg, press Enter.
Click to expand...
Click to collapse
Thank you very much, I will try
Gesendet von meinem GT-I9505 mit Tapatalk

Vinnl said:
You might like to know that you can run many versions of Linux directly from a DVD drive or USB drive. A popular one, and probably the easiest, is: http://www.ubuntu.com/desktop
To "run dmesg", as suggested by @_keesj, do the following:
Start Ubuntu
When the desktop is open, press the Windows key.
Connect your phone.
Type "Terminal".
Press Enter or click the Terminal icon.
Type dmesg, press Enter.
Click to expand...
Click to collapse
View attachment 2925701
I got this message when i connect my Phone to a 32bit Ubuntu VM (VMWare-Player)
Do you know an option for dmesg to make the text shorter? Its such a huge text, larger than the Terminal is able to display.

DarkerTimes said:
View attachment 2925701
I got this message when i connect my Phone to a 32bit Ubuntu VM (VMWare-Player)
Do you know an option for dmesg to make the text shorter? Its such a huge text, larger than the Terminal is able to display.
Click to expand...
Click to collapse
Congratulation for your first GNU/linux use !:highfive:
Yeah dmesg is super huge, it contains record of all that happened on your system since your started it up. (it s a bit more complicated in fact).
I dont know any option to make it shorter, but there are ways
- to only get the bottom of it,
- to save its output in a file
Code:
dmesg > ~/Desktop/dmesg-output.txt
- or to increase the amount of message your terminal can display (right click, profile, profile preferences, scrolling, unlimited).
However here you only need to look at what happened recently (i.e when you connected your phone)
If you connecte your phone and then run the dmesg command the end of the output should show the device detection in the last 50 lines.
I cant acces your attachement, is this only me ?
With a working phone on a non VM ubuntu you should see something like this.
(It may be different on your system, as long as you can read som usb lines, further more containing MT65xx or Mediateck, you are good to go !
....
...
[ 237.437926] usb 2-1.6: new high-speed USB device number 5 using ehci-pci
[ 237.530804] usb 2-1.6: New USB device found, idVendor=0e8d, idProduct=2000
[ 237.530809] usb 2-1.6: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[ 237.530812] usb 2-1.6: Product: MT65xx Preloader
[ 237.530814] usb 2-1.6: Manufacturer: MediaTek
[ 237.637040] cdc_acm 2-1.6:1.1: ttyACM0: USB ACM device
[ 237.692248] usbcore: registered new interface driver cdc_acm
[ 237.692250] cdc_acm: USB Abstract Control Model driver for USB modems and ISDN adapter
....
That would means that your OS detected that a new device was connected to USB and that it recognise a mediateck phone.
I hope it's also the case with your phone !
BTW I don't know vmware so well, but sometimes virtual machine prevent virtualised operating system to acces usb port. Maybe someone can confirm that this issue wont appear here ? Or you can check it out by plugging some working usb device and look if some lines get added to dmesg

MoreThanADev said:
I cant acces your attachement, is this only me ?
Click to expand...
Click to collapse
Nope, apparently the attachment wasn't uploaded correctly.

MoreThanADev said:
I cant acces your attachement, is this only me ?
Click to expand...
Click to collapse
hope it works now
View attachment 2927858
here is the output from dmesg:
first run:
[ 5.270990] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002
[ 5.271001] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[ 5.271010] usb usb1: Product: EHCI Host Controller
[ 5.271019] usb usb1: Manufacturer: Linux 3.13.0-35-generic ehci_hcd
[ 5.271027] usb usb1: SerialNumber: 0000:02:03.0
[ 5.272005] hub 1-0:1.0: USB hub found
[ 5.272231] hub 1-0:1.0: 6 ports detected
[ 5.273333] ehci-platform: EHCI generic platform driver
[ 5.273386] ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver
[ 5.273404] ohci-pci: OHCI PCI platform driver
[ 5.273465] ohci-platform: OHCI generic platform driver
[ 5.273494] uhci_hcd: USB Universal Host Controller Interface driver
[ 5.273813] uhci_hcd 0000:02:00.0: UHCI Host Controller
[ 5.273822] uhci_hcd 0000:02:00.0: new USB bus registered, assigned bus number 2
[ 5.274010] uhci_hcd 0000:02:00.0: irq 18, io base 0x000020c0
[ 5.274349] usb usb2: New USB device found, idVendor=1d6b, idProduct=0001
[ 5.274351] usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[ 5.274352] usb usb2: Product: UHCI Host Controller
[ 5.274353] usb usb2: Manufacturer: Linux 3.13.0-35-generic uhci_hcd
[ 5.274355] usb usb2: SerialNumber: 0000:02:00.0
[ 5.274492] hub 2-0:1.0: USB hub found
[ 5.274546] hub 2-0:1.0: 2 ports detected
second run
[ 201.982468] usb 2-2.1: new full-speed USB device number 4 using uhci_hcd
[ 202.310781] usb 2-2.1: New USB device found, idVendor=0e8d, idProduct=0003
[ 202.310840] usb 2-2.1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
[ 202.448421] cdc_acm 2-2.1:1.0: ttyACM0: USB ACM device
[ 202.456529] usbcore: registered new interface driver cdc_acm
[ 202.456544] cdc_acm: USB Abstract Control Model driver for USB modems and ISDN adapters
[ 202.471104] usbcore: registered new interface driver usbserial
[ 202.471210] usbcore: registered new interface driver usbserial_generic
[ 202.471344] usbserial: USB Serial support registered for generic
[ 202.481866] usbcore: registered new interface driver option
[ 202.482531] usbserial: USB Serial support registered for GSM modem (1-port)
[ 241.102849] usb 2-2.1: USB disconnect, device number 4
[ 266.180249] usb 2-2.1: new full-speed USB device number 5 using uhci_hcd
[ 266.581692] usb 2-2.1: New USB device found, idVendor=0e8d, idProduct=0003
[ 266.581747] usb 2-2.1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
[ 266.660505] cdc_acm 2-2.1:1.0: ttyACM0: USB ACM device
what to do now?
btw, every 50-60 seconds i got the pluggin and unplugg sound from my windows system
Edit:
i have a second Fairphone now and tried to turn on the first one with tha accu of the second one and the second phone with the accu of the first one. both doesn´t start. only the second one with the second accu is working.

DarkerTimes said:
second run
[ 266.180249] usb 2-2.1: new full-speed USB device number 5 using uhci_hcd
[ 266.581692] usb 2-2.1: New USB device found, idVendor=0e8d, idProduct=0003
[ 266.581747] usb 2-2.1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
[ 266.660505] cdc_acm 2-2.1:1.0: ttyACM0: USB ACM device
what to do now?
Click to expand...
Click to collapse
These lines are your phone so there is still some life in it. But it doesnt even start the preloader which appears after these lines if I plug in my phone (powered off).
Maybe this low level mode is enough for the SP flash tool and you can try the unbrick guide: http://forum.xda-developers.com/wik...o_restore_Fairphone_if_you_totally_bricked_it
Make sure to chose the correct image (FUSE for upgraded partition layout, 1G13G for the old layout)
You might want to uncheck "userdata", this might give you a chance of keeping your apps and settings.
Other than that you could contact Fairphone support.

My Solution
Code:
#include
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
I had the same Problem while trying install CM11.
What works for me @ a Win7 PC:
- remove the Battery (Force shutdown the phone)
- plugin the Battery
- Turn on the Phone while pressing the power-button and the volume-UP button. (release power button after 6 Secs)
- Now you're in the recovery menu
- If you have CWM (like me) goto --> install zip --> install zip from sideload
If you have another bootloader you'll find the "install zip from sideload" somewhere...
- Download the Original zip-file from Fairphone (Fairphone Website --> SUPPORT --> SOFTWARE --> UPDATES --> SOFTWARE --> DOWNLOADS)
- Download / install the MTK6589 ADB Driver (http://forum.xda-developers.com/showthread.php?t=2247537)
- now download a tool which contains the adb.exe (I tooked the "MTK droid root & tools" http://forum.xda-developers.com/showthread.php?t=2160490)
- Start the MTK tool as Admin and press "ADB-Terminal"
- in the Terminal write: "adb push NAMEOFTHEZIPFILE.zip"
- now your phone should start transfer, reboot and install the original OS
Hope this works for you too...
* More about ADB and Sideload (http://forum.xda-developers.com/showthread.php?t=2318497
Regards

_tmp said:
These lines are your phone so there is still some life in it. But it doesnt even start the preloader which appears after these lines if I plug in my phone (powered off).
Maybe this low level mode is enough for the SP flash tool and you can try the unbrick guide: http://forum.xda-developers.com/wik...o_restore_Fairphone_if_you_totally_bricked_it
Make sure to chose the correct image (FUSE for upgraded partition layout, 1G13G for the old layout)
You might want to uncheck "userdata", this might give you a chance of keeping your apps and settings.
Other than that you could contact Fairphone support.
Click to expand...
Click to collapse
shooter_92 said:
Code:
#include
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
I had the same Problem while trying install CM11.
What works for me @ a Win7 PC:
- remove the Battery (Force shutdown the phone)
- plugin the Battery
- Turn on the Phone while pressing the power-button and the volume-UP button. (release power button after 6 Secs)
- Now you're in the recovery menu
- If you have CWM (like me) goto --> install zip --> install zip from sideload
If you have another bootloader you'll find the "install zip from sideload" somewhere...
- Download the Original zip-file from Fairphone (Fairphone Website --> SUPPORT --> SOFTWARE --> UPDATES --> SOFTWARE --> DOWNLOADS)
- Download / install the MTK6589 ADB Driver (http://forum.xda-developers.com/showthread.php?t=2247537)
- now download a tool which contains the adb.exe (I tooked the "MTK droid root & tools" http://forum.xda-developers.com/showthread.php?t=2160490)
- Start the MTK tool as Admin and press "ADB-Terminal"
- in the Terminal write: "adb push NAMEOFTHEZIPFILE.zip"
- now your phone should start transfer, reboot and install the original OS
Hope this works for you too...
* More about ADB and Sideload (http://forum.xda-developers.com/showthread.php?t=2318497
Regards
Click to expand...
Click to collapse
Hey guys,
sry that I've been away for this long period of time.
The problem is that i can't enter recovery mode, so the only way to try it would be with the SP flash tool but I decided to contact the fairphone support and sent it back for repairing it.
But thanks all for your help!!
Edit: I got my phone back now. The issues were caused by damaged mainboard, they change it completely.
Sent from my Galaxy S4 using Tapatalk

I have the same problem
Hey,
I have the same problem, did it fall under warranty or did you have to pay for the repair?

hewitje240 said:
Hey,
I have the same problem, did it fall under warranty or did you have to pay for the repair?
Click to expand...
Click to collapse
Hi, did fall under warranty
Sent from my GT-I9505 using XDA Free mobile app

Recovering files from dead(?) HTC One X

I'm trying to salvage some important files from a dead HTC One X (stock everything) - from what I've been told, it was in use and suddenly turned off. After attempts to charge the phone etc. to no avail (monitor does not turn on, no LEDs turn on at all) it was sent for repair with the instructions to not proceed if they could not salvage the files. The repair shop opened the phone, molested some plastic parts and sent it back in two parts, stating that they could not proceed further without loosing the data on the phone. I have no idea what they tried, so I'm hoping they didn't try very much before giving up.
So - I put the thing back together and tried to turn it on and charge it. The display and LEDs show no signs of life, even when charging, holding down power button etc. When I attach the phone to my (Linux) PC, I get the following in dmesg:
Code:
[142745.586102] usb 3-2: new high-speed USB device number 99 using xhci_hcd
[142745.603030] usb 3-2: New USB device found, idVendor=0955, idProduct=7130
[142745.603038] usb 3-2: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[142745.603042] usb 3-2: Product: APX
[142745.603045] usb 3-2: Manufacturer: NVIDIA Corp.
which is the only sign of life I've seen so far (why NVIDIA vendor ID and not HTC?). When holding down the power button for ~15 seconds, there's a "USB disconnect" and it re-appears.
Sometimes the phone seems to enter a slightly different state, giving me some sort of connect-timeout-reconnect loop four times:
Code:
[143124.943256] usb 3-2: new high-speed USB device number 101 using xhci_hcd
[143129.944609] xhci_hcd 0000:00:14.0: Timeout while waiting for address device command
[143130.148758] usb 3-2: Device not responding to set address.
[143130.352699] usb 3-2: device not accepting address 101, error -71
I was hoping that it was just a busted display, and booting a recovery image would let me grab the files via adb - but it does not show up when doing "fastboot devices". I've tried different blind combinations of holding the power button and volume down, but nothing seems to happen (not sure if I'm doing something wrong though, since nothing appears on screen).
Maybe someone here on xda has an idea on how I could get into the device? Recovering the phone does not matter, but getting the files is very important to the owner.

Tausen said:
I'm trying to salvage some important files from a dead HTC One X (stock everything) - from what I've been told, it was in use and suddenly turned off. After attempts to charge the phone etc. to no avail (monitor does not turn on, no LEDs turn on at all) it was sent for repair with the instructions to not proceed if they could not salvage the files. The repair shop opened the phone, molested some plastic parts and sent it back in two parts, stating that they could not proceed further without loosing the data on the phone. I have no idea what they tried, so I'm hoping they didn't try very much before giving up.
So - I put the thing back together and tried to turn it on and charge it. The display and LEDs show no signs of life, even when charging, holding down power button etc. When I attach the phone to my (Linux) PC, I get the following in dmesg:
Code:
[142745.586102] usb 3-2: new high-speed USB device number 99 using xhci_hcd
[142745.603030] usb 3-2: New USB device found, idVendor=0955, idProduct=7130
[142745.603038] usb 3-2: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[142745.603042] usb 3-2: Product: APX
[142745.603045] usb 3-2: Manufacturer: NVIDIA Corp.
which is the only sign of life I've seen so far (why NVIDIA vendor ID and not HTC?). When holding down the power button for ~15 seconds, there's a "USB disconnect" and it re-appears.
Sometimes the phone seems to enter a slightly different state, giving me some sort of connect-timeout-reconnect loop four times:
Code:
[143124.943256] usb 3-2: new high-speed USB device number 101 using xhci_hcd
[143129.944609] xhci_hcd 0000:00:14.0: Timeout while waiting for address device command
[143130.148758] usb 3-2: Device not responding to set address.
[143130.352699] usb 3-2: device not accepting address 101, error -71
I was hoping that it was just a busted display, and booting a recovery image would let me grab the files via adb - but it does not show up when doing "fastboot devices". I've tried different blind combinations of holding the power button and volume down, but nothing seems to happen (not sure if I'm doing something wrong though, since nothing appears on screen).
Maybe someone here on xda has an idea on how I could get into the device? Recovering the phone does not matter, but getting the files is very important to the owner.
Click to expand...
Click to collapse
For me the battery is dead. Try changing battery... Has the repair center remounted all connectors like the screen/battery connector?

[solved] adb lists no device with phone in recovery mode

I'm trying to upgrade my Google Nexus 5x to Oreo. (Phone purchased directly from Google and presently on T-Mobile via Ting MVNO.) I don't seem to be getting the OTA and I guess that's because T-Mobile has not released it yet. (In the past I thought that upgrades came directly from Google so this is a bit puzzling to me.) This leaves me trying to sideload following the instructions at https://developers.google.com/android/ota.
I installed the SDK tools (on Linux Debian 9.0 Stretch), put the phone in developer mode and have put the phone in recovery mode using 'adb reboot recovery'. At this point I run into difficulty as 'adb devices' lists no device.
Contents of /var/log/messages for this process is:
Code:
Sep 27 08:37:54 yggdrasil kernel: [500679.560432] usb 3-2: new high-speed USB device number 11 using xhci_hcd
Sep 27 08:37:54 yggdrasil kernel: [500679.703784] usb 3-2: New USB device found, idVendor=18d1, idProduct=4ee7
Sep 27 08:37:54 yggdrasil kernel: [500679.703786] usb 3-2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
Sep 27 08:37:54 yggdrasil kernel: [500679.703787] usb 3-2: Product: Nexus 5X
Sep 27 08:37:54 yggdrasil kernel: [500679.703788] usb 3-2: Manufacturer: LGE
Sep 27 08:37:54 yggdrasil kernel: [500679.703789] usb 3-2: SerialNumber: <obfuscated>
Sep 27 08:37:54 yggdrasil mtp-probe: checking bus 3, device 11: "/sys/devices/pci0000:00/0000:00:14.0/usb3/3-2"
Sep 27 08:37:54 yggdrasil mtp-probe: bus: 3, device: 11 was not an MTP device
Sep 27 08:38:34 yggdrasil kernel: [500719.623295] usb 3-2: USB disconnect, device number 11
The last line is produced by the 'adb reboot recovery' command and there is nothing further until the phone restarts (on its own.)
I searched the forum for this issue and found two threads, one of which referred to a thread with a solution but my search foo is not up to finding that thread. :-/ Any help with getting Oreo on my otherwise unmodified/unrooted/not unlocked phone is welcome! (I'm jealous that my wife has had Oreo on her 5X via Verizon and she still thinks that Oreo is just a cookie. )
Thanks!
Edit:
Before issuing 'adb reboot recovery' and after starting the adb server, the device shows up in the listing:
Code:
[email protected]:/home/hbarta/Downloads# adb devices
List of devices attached
<obfuscated> device
[email protected]:/home/hbarta/Downloads#
After rebooting to recovery mode the phone shows the green android on its back with a red triangle with '!' on it. Below that in white text it states "No command".
I have also tried this using Ubuntu Mate 16.10 and Xubuntu 16.04 with the same results. (All are Debian based.)
Edit.2 I got some further help from Ting support. He suggested installing the community maintained package for ADB (vs. just unpacking the zip file.) That configures udev rules and adds me to 'plugdev' (or maybe I was already there.) It appears that the benefit of that is that I no longer need to be root to execute the 'adb' commands. Otherwise the results were the same.
I checked Developer settings and unlocked the bootloader to see if that made a difference. I think it did not.
While the phone was in recovery mode, I was poking randomly at the power and volume buttons to try to reboot it when the phone display changed to a recovery menu. One option was "apply update from ADB" which I executed. The phone screen then prompted me to execute the 'adb sideload <filename>' command which I did on the PC after verifying that the phone was now listed in ADB devices (it was.)
Download completed and following reboot the phone is now running Android 8.0.0 I snagged a picture of the screen after download and before reboot if anyone is curious.

Just an fyi, the android on its back is the stock recovery. To get into it simultaneously press and release the power and vol up key. You might have to try it a few times as the timing is a little tricky.

jd1639 said:
Just an fyi, the android on its back is the stock recovery. To get into it simultaneously press and release the power and vol up key. You might have to try it a few times as the timing is a little tricky.
Click to expand...
Click to collapse
Thanks for the tip. Yes, standard recovery as this is the first time I've done anything other than wait for an OTA. I didn't realize that I need to press buttons to actually start recovery but I must have pressed vol up and pwr within the timing constraints while trying to reboot.