First Time Install
-
@rdl85 That system is UConnect, right?
-
@crab_aesthetics I'll check next time I'm in the car and report back.
-
@crab_aesthetics as far as I could tell there was nothing labled Uconnect in the bluetooth menu/options in my Hyundai. A quick Google search Looking for Hyundai and Uconnect also didn't bring up anything. It seems like a vanilla stock Bluetooth implementation. Hope this helps.
-
Phone came and it was a dud, bum antennae! Wouldn't connect to LTE/CDMA network no matter what, even cell store guy thought it was good to go but the antennae just seemed non-functional. Have to get replacement :^(
-
@crab_aesthetics bummer! Hope you can find a replacement. 3a is a nice UT phone.
-
@rdl85 I am able to connect to my BMW i3 bluetooth and make and receive calls with a Pixel 3a running UT Version 400 (dev). Good sound and microphone performance. This is a big improvement from my old Nexus 5, which had extreme distortion in hands free calls.
-
@rdl85 Just got the replacement today, heading to the cell store after work to get a SIM and try to get it activated, then I'll flash UT later tonight when I get back. Pretty stoked.
-
@crab_aesthetics If you need help, i did my first install a few days ago... Had driver issues, reach out if you do to.
-
@trwidick Well, so far, so bad.
Began by trying to flash the phone with PQ3B.190801.002, it seemed like it was going well but then it said "Flash failed. The device has stopped responding." Now it's just in a loop where it won't leave Fastboot Mode (probably because it was in the process of writing the OS image when it failed). I'm thinking maybe it has something to do with the USB cable, but I only have the one USB C cable so I have to run to the gas station to try to get a different one, or idk maybe Walgreens but that's a lot farther to drive. I started flashing it on a Linux computer and when it failed I tried it on a Windows 10 HP laptop, but it doesn't seem to want to recognize on that one. I'm gonna go to the store and get a different cable and see if that doesn't do the trick. If not, oof idk. That would be not good.
EDIT
It turns out it was indeed the USB cable. I had initially tried with the one that it came with (USB C male to USB C male) plugging the end opposite the phone in to the computer's USB C port. This was probably my mistake.
After trying a regular USB A to USB C cable I was able to flash Android 9.0 and am now about to flash UT.
-
@crab_aesthetics good luck!
-
@crab_aesthetics When it gets to fastboot this is where i had my issus. I used windows 10.
-
@trwidick Yes the installer seemed to be going well, then it got to the point where it said to choose to boot into Recovery, then nothing worked. I will try more tomorrow.
-
@crab_aesthetics When it hits this point and does nothing. I had to go to windows device manager and then find my pixel 3a. Manually reinstall the same driver, then reload the webpage in the browswer.
Currently Using: Google Pixel 3a (sargo) OTA-17
-
@crab_aesthetics sorry but I bet my experience won't be much help. My install went like this: the installer finished the install and seemed to suggest a successful intall, but then it wouldn't boot fully into UT, just hung on Google screen. I then tried reflashing and then halfway through the reflash my 3a booted up and it just started to work. I have always wondered if the first flash had an error in one of the early steps and the second partial reflash fixed it... That whole install process was a little touch and go.
-
@trwidick i had same issue with my mx4, device under normal boot, fastboot boot, and recovery boot needed install adb driver for each boot mode under windows.
For the record : https://forums.ubports.com/topic/4026/problem-upgrading-mx4-from-ota15-to-ubport/12?_=1623732194391 -
@keneda I'm doing the installation on linux so I don't think it is a driver issue. Still stuck in Fastboot Mode, if I choose Recovery Mode I see the Google warning about 'the bootloader is unlocked and the software cannot be verified', then that message goes away and it just goes back to Fastboot Mode, like the recovery doesn't exist or something. Not really sure how to fix this :^(
Nothing shows up for command 'adb devices'.
-
@crab_aesthetics Have you tried.....fastboot reboot recovery in the terminal and see if the installer progresses. Unplugging and replugging in the cable sometime forces things on. If you are selecting the wipe option on the installer try without that.
These are all very general and not specific but things I tried on an OP5 install to get it to complete. All I can say (as I don't have your device) is keep trying, sometimes it "just works" which is frustrating and your not sure what you did but it worked. -
>>> adb reboot-bootloader error: no devices/emulators found >>> adb kill-server >>> adb start-server * daemon not running; starting now at tcp:5037 * daemon started successfully >>> adb devices List of devices attached >>> fastboot reboot recovery < waiting for any device >I don't know for sure what happened, but it seems like there is no OS to boot into and the recovery seems non-functional or non-existent. It's as if the device is not in USB-debug mode which would explain why it's not showing up as a device, but there's no OS to boot into to turn on USB debugging...
-
@crab_aesthetics Success! Kind of!
I changed it to a different USB port and now it's recognized, I'm flashing 9.0 again.
-
@crab_aesthetics Good luck. I really don't know the ins and outs of Pixel install having never tried. The OP used TWRP which was easy to get back to(most times) untill UBports recovery was installed.
