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.
Related
hi, yesterday i just bought a bricked motorola defy, since i read that was almost imposible to brick one...i thought it'd be easy to unbrick
ill explain:
black screen, no recovery, no bootloader mode....
theorically it had android 2.2
when i conect it to the pc it connects and instantly disconects (someone posted the same and he said that randomly it'd connect succesfully)
battery shows 4v (so itd flash)
white led shows up when i connect the usb without battery and turns off when i put the battery
rsd cant recognise it (windows neither)
also tried a linux script, but it neither recognises it...
i thought id be an uncharged battery + wrong sbf
but i cant get it to connect...
id apreciate fast responses
May be your battery will b low....Try to charge it and than try...
Sent from my MB525 using XDA App
i already charged it with the mvgyber fix... i guess the red cable goes to the + (top right) and the black to the - (top left...)
if so, i tried.
also tried a linux script, but it neither recognises it...
Click to expand...
Click to collapse
What script did you use?
Is it sbf_flash? Please give us more details! Like the name of the script/binary file you used, the parameters passed at runtime, the error you received after running the script/binary tool.
Did you tried to see if any information is added in the linux log files while connecting the phone to your computer using a "microUSB to USB" cable?
i tried the sbf_flash one, (there are others?)
it says, waiting for phone... or something like that...(i dont have linux here)
if the battery shows 4v it isnt a battery issue am i right?
Not as far as I know, but sbf_flash is a binary tool and since you said that you have tried a linux script I thought that you are using something else.
Basically, when a device is connected to a computer running linux, via USB, you can find informations about the attached device in some log files (/var/log/messages or /var/log/udev).
If/when you will have a linux around, let me know and I'll try to help you (if I can).
tomorrow ill have linux access, ill post logs...
btw... has nobody seen a solution for the connecting-disconeccting issue? ive seen few posts with it, but anyone posts a solution, just someone saying is luck...
i thought electronics had no true randomness,
im getting this at /var/log/messages
May 12 08:11:01 ubuntu kernel: [ 1192.928137] usb 1-6: new high speed USB device using ehci_hcd and address 9
May 12 08:11:01 ubuntu kernel: [ 1193.062719] usb 1-6: configuration #1 chosen from 1 choice
May 12 08:11:04 ubuntu kernel: [ 1196.056253] usb 1-6: USB disconnect, address 9
May 12 08:11:17 ubuntu kernel: [ 1209.308069] usb 1-6: new high speed USB device using ehci_hcd and address 10
May 12 08:11:17 ubuntu kernel: [ 1209.442678] usb 1-6: configuration #1 chosen from 1 choice
May 12 08:11:20 ubuntu kernel: [ 1212.436317] usb 1-6: USB disconnect, address 10
at udev, i cant see anything related to the phone...
Those messages appear in the log file exactly when the phone is connected to the computer?
In my /var/log/messages other information appears when the phone is plugged in (like device manufacturer, device serial number etc) but all my log messages go into /var/log/messages (I'm using Gentoo at home), but in Ubuntu it seems that most of these messages go to /var/log/udev.
What version of sbf_flash did you use? The last version is 1.23 (mbm).
A few days ago I came across an article describing the udev configuration in order to be able to connect to the phone using adb. I don't know if this will help you since USB debugging must be turned on and for that you need a running android device. I'll send you the link via PM since I do not have enough posts in this forum to be allowed to write url's in the post.
ill post the last lines of the udev log, at night (3h actually)
but somehow i dont know why, but the behaviour is the same, gets conection, looses conection...
maybe is a hardware issue...
Here's what's added in my /var/log/message when I connect my (working defy) via USB: (USB debugging is not turned on and the USB connection is set to charge only)
May 12 22:33:07 tuxtm kernel: [ 2506.674023] usb 1-4: new high speed USB device using ehci_hcd and address 3
May 12 22:33:07 tuxtm kernel: [ 2506.788858] usb 1-4: New USB device found, idVendor=22b8, idProduct=41d9
May 12 22:33:07 tuxtm kernel: [ 2506.788863] usb 1-4: New USB device strings: Mfr=1, Product=2, SerialNumber=3
May 12 22:33:07 tuxtm kernel: [ 2506.788866] usb 1-4: Product: MB525
May 12 22:33:07 tuxtm kernel: [ 2506.788869] usb 1-4: Manufacturer: Motorola
May 12 22:33:07 tuxtm kernel: [ 2506.788871] usb 1-4: SerialNumber: <serial_number_here>
May 12 22:33:07 tuxtm kernel: [ 2506.789567] scsi2 : usb-storage 1-4:1.0
May 12 22:33:08 tuxtm kernel: [ 2507.790153] scsi 2:0:0:0: Direct-Access Motorola MB525 0001 PQ: 0 ANSI: 2
May 12 22:33:08 tuxtm kernel: [ 2507.790684] sd 2:0:0:0: Attached scsi generic sg1 type 0
May 12 22:33:08 tuxtm kernel: [ 2507.792748] sd 2:0:0:0: [sdb] Attached SCSI removable disk
with lsusb i get nothing by connecting, if i put the battery in, the next 4sec i get a texas instruments device, then goes off
i guess is hw issue, im trading that brick for a working samsung wave device.
tyvm for the help, but i guess it was a fully brick.
ANSWER!!!
Flash sbf file using rsd lite............IT WORKS........I DID IT...........I THINK U R A NEWBIE
im a newbie, but, rsd cant recognise it, when i plug the phone without battery:
-white led ON
-put the battery (here i can press whatever button, no change)
-white led off
-pc detects new hw (motorola flashing device)
-3seconds
-pc looses conection with motorola flashing device
(even pressing show device at light speed once conected, i doesnt detect anything)
and since on linux i get same result (connect - disconect), it means isnt a pc issue (also tried on another pc)
got an answer for you too
pjgowtham said:
............IT WORKS........I DID IT...........I THINK U R A NEWBIE
Click to expand...
Click to collapse
It's the little "arrow down" key on the left side of your keyboard. Just above the "CTRL" and "arrow up" Key.
hallo.. i'm newbie. i got some proble in my defy
I made a mistake in ROM CM7: I "install the 2nd init". and the results stuck on the boot logo .. : (
I finally went into the boot loader, then flash again use 3.4.2_177 SBF-005_NORDIC (do not wipe the data) .. remain stuck at the boot logo. and I try to use flash SBF-Stock.UKTmobile 3.4.3_11 (not wipe the data) and the results .... still stuck>> it's just an animated logo appears only.
AND THEN ---------------------------------
for this case:
I want to get into stock recovery:
1. defy turn off, turn the power button + volume down (hold a while)
2. logo appears>> android +! (the menu does not appear anything)
3. and I do not know anymore what should I do: (
please help me
thanks before
omneon said:
1. defy turn off, turn the power button + volume down (hold a while)
2. logo appears>> android +! (the menu does not appear anything)
3. and I do not know anymore what should I do: (
Click to expand...
Click to collapse
you did tap the lower right corner of your screen when android appeared, didn't you?
If right corner doesn't do the trick, try instead pushing both volume buttons at the same moment. Worked for me
Sent from my MB525 using XDA App
Hi all,
I am trying to get fastboot to work on Mac OS X with my Xperia Play. I can't seem to get it to recognize my device at all.
It works fine in Windows when using fastboot on my other computer. (I have gotten it to work this way) ADB works in OS X for me and sees the device just fine. It's just whenever I try to use fastboot it never will see the device.
Here is some interesting findings. The device is connected and in fastboot mode (the led is blue) and OS X seems to see it. Issuing 'system_profiler SPUSBDataType' in terminal gives me the following:
Code:
USB High-Speed Bus:
Host Controller Location: Built-in USB
Host Controller Driver: AppleUSBEHCI
PCI Device ID: 0x283a
PCI Revision ID: 0x0003
PCI Vendor ID: 0x8086
Bus Number: 0xfa
S1Boot Fastboot:
Product ID: 0x0dde
Vendor ID: 0x0fce (Sony Ericsson Mobile Communications AB)
Version: 1.00
Serial Number: CB5A1GD1EX&ZLP
Speed: Up to 480 Mb/sec
Manufacturer: Sony Ericsson Mobile Communications AB
Location ID: 0xfa200000 / 2
Current Available (mA): 500
Current Required (mA): 0
Whenever I issue 'fastboot devices' it yields nothing. If I start the phone up normally and issue 'adb devices' I get the device readout fine.
Has anyone else had this issue or ran into such problems? I feel like I might be overlooking something. Please excuse my ignorance on the subject. This all is still very new for me, as this is my first android device and I just got the phone over the past weekend.
Any help would be greatly appreciated. Thanks!
xSoNiCcRaCkErSx said:
Hi all,
I am trying to get fastboot to work on Mac OS X with my Xperia Play. I can't seem to get it to recognize my device at all.
It works fine in Windows when using fastboot on my other computer. (I have gotten it to work this way) ADB works in OS X for me and sees the device just fine. It's just whenever I try to use fastboot it never will see the device.
Here is some interesting findings. The device is connected and in fastboot mode (the led is blue) and OS X seems to see it. Issuing 'system_profiler SPUSBDataType' in terminal gives me the following:
Code:
USB High-Speed Bus:
Host Controller Location: Built-in USB
Host Controller Driver: AppleUSBEHCI
PCI Device ID: 0x283a
PCI Revision ID: 0x0003
PCI Vendor ID: 0x8086
Bus Number: 0xfa
S1Boot Fastboot:
Product ID: 0x0dde
Vendor ID: 0x0fce (Sony Ericsson Mobile Communications AB)
Version: 1.00
Serial Number: CB5A1GD1EX&ZLP
Speed: Up to 480 Mb/sec
Manufacturer: Sony Ericsson Mobile Communications AB
Location ID: 0xfa200000 / 2
Current Available (mA): 500
Current Required (mA): 0
Whenever I issue 'fastboot devices' it yields nothing. If I start the phone up normally and issue 'adb devices' I get the device readout fine.
Has anyone else had this issue or ran into such problems? I feel like I might be overlooking something. Please excuse my ignorance on the subject. This all is still very new for me, as this is my first android device and I just got the phone over the past weekend.
Any help would be greatly appreciated. Thanks!
Click to expand...
Click to collapse
you are not alone bro and I'm not new to android have rooted everything ive had. some were tricky but this damn xperia is kicking my a$$.. im on windows 7
Thanks bori!
I did some extensive research on the issue and it seems a lot of people are also having the same issue on all platforms. From what I found the issue seems to fix itself on Windows by installing the google_usb and fastboot drivers. On linux it seems the issue is in adding the device's vendorID to the udev configuration. For Mac it is just suppose to 'work'. Sometimes these fixes work, sometimes they don't. For everyone with the issue for OS X though, not a single one had a solution or a person that got it working unfortunately.
It seems to be a very tricky device indeed.
bori1030 said:
you are not alone bro and I'm not new to android have rooted everything ive had. some were tricky but this damn xperia is kicking my a$$.. im on windows 7
Click to expand...
Click to collapse
if your on Win7 like me its piss easy.
http://www.youtube.com/watch?v=LRH3pC7MhEA
you shouldnt have any qs after the video. The only thing you do is hold the search button for Fastboot blue led mode
I don't know if you are still trying to do this or not, but I just stumbled upon this thread while doing some research of my own. I am running 10.6.6 and say, for example, if I want to boot the CWM that is listed in the developer forum, all I have to type is "fastboot-mac -i 0xfce boot recoveryPLAY.img" Just make sure that your phone is in fastboot mode. Power off the device and while holding the search button plug in your USB cable. The LED should be blue. If you notice the 0xfce is the vendor id for the phone. Adding the -i 0xfce works for any of fastboot's commands, ie fastboot-mac -i 0xfce flashall, etc
Hi there,
The other day I split some water over my nexus and rather expectedly I began getting errors. It was not being recognised by my PC nor would it charge through both USB and AC power. USB fried most likely so I returned it under warranty and it came back working and charging, however, when I plugged it into my PC windows could not install the correct drivers (by default) - although I could access the SD card and MTP was working fine. Since then I have installed the Universal Naked Drivers and my phone is recognised as ADB and fastboot interfaces (when turned on and in fastboot respectively), BUT, I could not find the device using ADB or fastboot commands ("fastboot command read error 2147483647"). After tinkering for a while I tried 'Wugs Nexus Root Toolkit v1.5.2' and managed to find my device using both adb and fastboot commands. Using the adb and fastboot.exe's in the program's install I could run everything as usual so at the very least I know my phone is (sort of) working.
Although I can get things to work I would like it to work without having to use 'hacks' of some sort. For example if I plug it into another computer it won't install the correct drivers. Can anyone shed some light as to what is still broken?
Phone details:
Galaxy Nexus rooted
Running Jelly Bean 4.1.1 (ROM)
Build no: JRO03C
Baseband version: I9250XXKK6
Kernel Version: 3.0.31-g6fb96c9 [email protected] ) #1 SMP PREMPT Thu Jun 28 11:02:39 PDT 2012
Quick bump because I changed the OP.
I'd simply return it. Sounds to me the water spill definitely broke something.
Petrovski80 said:
I'd simply return it. Sounds to me the water spill definitely broke something.
Click to expand...
Click to collapse
I've considered it, but it can do everything... just not by itself.
This leads me to believe that the hardware is fine, just some of the software is broken. Unfortunately I have no idea what specific bit that is...
Sigh**
and the saga continues http://forum.xda-developers.com/showthread.php?t=1599747
Well, I tried to flash my device and bricked it. I just bought it today, bought a new back for it, and got it unlocked by Alejandrissimo today, so I'm really upset with myself. And I'm willing to spend money to fix it if that's what it takes.
When I plug the device into Linux I see
Feb 27 22:17:41 alexander kernel: [95344.195631] usb 2-2: new high-speed USB device number 16 using ehci_hcd
Feb 27 22:17:41 alexander kernel: [95344.329601] usb 2-2: New USB device found, idVendor=05c6, idProduct=9008
Feb 27 22:17:41 alexander kernel: [95344.329612] usb 2-2: New USB device strings: Mfr=1, Product=2, SerialNumber=0
Feb 27 22:17:41 alexander kernel: [95344.329619] usb 2-2: Product: QHSUSB_DLOAD
Feb 27 22:17:41 alexander kernel: [95344.329624] usb 2-2: Manufacturer: Qualcomm CDMA Technologies MSM
Feb 27 22:17:41 alexander kernel: [95344.330368] qcserial 2-2:1.0: Qualcomm USB modem converter detected
Feb 27 22:17:41 alexander kernel: [95344.330583] usb 2-2: Qualcomm USB modem converter now attached to ttyUSB2
Feb 27 22:17:41 alexander mtp-probe: checking bus 2, device 16: "/sys/devices/pci0000:00/0000:00:13.2/usb2/2-2"
Feb 27 22:17:41 alexander mtp-probe: bus: 2, device: 16 was not an MTP device
So obviously it's connecting. I just don't know what to do with it at this point besides experience that sinking feeling.
s1tool doesn't ever find the phone, though it tries.
drinkypoo said:
Well, I tried to flash my device and bricked it. I just bought it today, bought a new back for it, and got it unlocked by Alejandrissimo today, so I'm really upset with myself. And I'm willing to spend money to fix it if that's what it takes.
Click to expand...
Click to collapse
Alejandrissimo is the best, he fixed it for me. Which also goes to show that these problems are easily fixable if you have the right tools.
drinkypoo said:
Alejandrissimo is the best, he fixed it for me. Which also goes to show that these problems are easily fixable if you have the right tools.
Click to expand...
Click to collapse
Hi mate,
i have a developers (prototype / "brown") device Xperia Z aka C6603
I can enter Fastboot mode but no FLASHMODE, when i do try to enter FLASHMODE Flashtool can not recognize the phone
and my Windows 7 OS asks for QHSUSB_DLOAD drivers with VID_05C6&PID_9008
The problem is not in findign the Qualcomm drivers for the asked device... the problem is Flashtool dont see it as a FLASHMODE device.
The device was bricked when i got it so i revived it with FASTBOOT mode and TWRP recovery, and now is working on with RomAmur ROM (doesnt really matter), but what matters i cannot turn OFF my new phone (because i'll get boot-loops) and my WiFi, and Bluetooth dont work along with tethering (USB or WiFi Hotspot)
Plz help me how to contact Alejandrissimo
N/A said:
Hi mate,
i have a developers (prototype / "brown") device Xperia Z aka C6603
I can enter Fastboot mode but no FLASHMODE, when i do try to enter FLASHMODE Flashtool can not recognize the phone
and my Windows 7 OS asks for QHSUSB_DLOAD drivers with VID_05C6&PID_9008
The problem is not in findign the Qualcomm drivers for the asked device... the problem is Flashtool dont see it as a FLASHMODE device.
The device was bricked when i got it so i revived it with FASTBOOT mode and TWRP recovery, and now is working on with RomAmur ROM (doesnt really matter), but what matters i cannot turn OFF my new phone (because i'll get boot-loops) and my WiFi, and Bluetooth dont work along with tethering (USB or WiFi Hotspot)
Plz help me how to contact Alejandrissimo
Click to expand...
Click to collapse
Wrong device, contact him via unlock-bootloader.com
Sent from my R800i using Tapatalk 2
fma965 said:
Wrong device, contact him via unlock-bootloader.com
Sent from my R800i using Tapatalk 2
Click to expand...
Click to collapse
Thx m8, will do that
Hi everybody.
I try to install Cyanogenmod on my LG G3 (model D855P bought on Brazil), but the install stopped after some minutes before finish.
I received the LG loop logo. After read some topic's about this error, I try to write a original firmware (.TOT D855AT European). The install runing with any problems. But now, my smartphone is show in LGUP with "Unknow" in the model, but show me the connection port is COM3.
I used the Boarddiag to verify the phone and any error founded. I try to re-write the SDRAM with files extract from LGD855PAT-01-V10a-370-02-JUN-10-2014-16G-32G+3, but not work. I install, but the problem continue the same.
I try the process when you change the COMxx port to COM41 and using a specified .dll, but the process stop in the first steps of validation.
Now, when I turn-on my phone, after some minutes I receive the message: Kernel Crash Handler. If I press Power+Down, the fastboot interface is started, but when I try to access using ADB (in Linux or Windows 10), the device is not listed with command ADB DEVICES. In the Windows 10, my device is recognize in "Manager Devices" with the name "Kedacom USB Device > Android Bootloader Interface".
I try to create the file on .android folder, but not work.
When run the command DMESG in the Linux, my device have this information:
usb 1-5: new high-speed USB device number 3 using ehci-pci
usb 1-5: New USB device found, idVendor=18d1, idProduct=d00d
usb 1-5: New USB device strings: Mfr=1, Product=2, SerialNumber=0
usb 1-5: Product: Android
usb 1-5: Manufacturer: Google
Anyone have some idea to help me about this problem???
fdelago said:
Hi everybody.
I try to install Cyanogenmod on my LG G3 (model D855P bought on Brazil), but the install stopped after some minutes before finish.
I received the LG loop logo. After read some topic's about this error, I try to write a original firmware (.TOT D855AT European). The install runing with any problems. But now, my smartphone is show in LGUP with "Unknow" in the model, but show me the connection port is COM3.
I used the Boarddiag to verify the phone and any error founded. I try to re-write the SDRAM with files extract from LGD855PAT-01-V10a-370-02-JUN-10-2014-16G-32G+3, but not work. I install, but the problem continue the same.
I try the process when you change the COMxx port to COM41 and using a specified .dll, but the process stop in the first steps of validation.
Now, when I turn-on my phone, after some minutes I receive the message: Kernel Crash Handler. If I press Power+Down, the fastboot interface is started, but when I try to access using ADB (in Linux or Windows 10), the device is not listed with command ADB DEVICES. In the Windows 10, my device is recognize in "Manager Devices" with the name "Kedacom USB Device > Android Bootloader Interface".
I try to create the file on .android folder, but not work.
When run the command DMESG in the Linux, my device have this information:
usb 1-5: new high-speed USB device number 3 using ehci-pci
usb 1-5: New USB device found, idVendor=18d1, idProduct=d00d
usb 1-5: New USB device strings: Mfr=1, Product=2, SerialNumber=0
usb 1-5: Product: Android
usb 1-5: Manufacturer: Google
Anyone have some idea to help me about this problem???
Click to expand...
Click to collapse
Any luck unbricking your device?
I have the same problem here