JJB
-
Content Count
34 -
Joined
-
Last visited
-
Days Won
3
Everything posted by JJB
-
Thanx. Looks like the plug is solded only and it wouldn't make too much noises if the plug was torn of itself. Guess the board itself is loose. Those wholes look like it's screwed to the frame. Any chance those screws where torn of the thread ? Unfortunately the disassemble video does not supply too much detailed looks into the inside.
-
Fairphone similar to FxTec also offers several OS for your device (and they preinstall for you). The surprising part is how easy it is do disassemble the whole thing as it was meant to do so. In the end Fairphone is what Pro 1X should be, just missing the keyboard. And it has this really big screen. Maybe we should ask them to add a slider too. 🤔
-
And don't say sliders are out of fashion. They are ahead of time. People just don't know yet 😉
-
Same to me, just received it few weeks ago. Also had this battery drain issue solved with the entry: With the support of some members like @EskeRahn and @Hook I was able to establish a new ROM (they are delivered with stock android no matter what you ordered) without utilizing Google and made the installation using an old Windows 7 (offline): It was quite some effort getting though all of that and the phone is already showing signs of defect (USB plug loose). But anyway. I did wait for this phone so long and I love the slider idea. If there would be a Pro 2X I would
-
Hello there, recently got my new Pro 1X, but trying to load it I sensed the USB plug to be loose. While moving it slightly it was rattling inside the phone. I am not sure. As the USB module is separate, does this refer to a not so perfect clamped/glued module or might the screw or even the connection on the conductor board be broken ? I once experienced something similar on a graphics card, where the plug was loose as its screw was broken from the board. After some time of rattling the soldering of the plug broke and it was doomed. Does anybody have an idea on that ? Or ma
-
Next up I will check that F-Droid stuff and app stores 😅
-
Thanks guys for your support. Those last days were exhausting. Wouldn't make it without you.
-
What worked for me now: - Installing adb and fastboot (partially as no FxTec USB Drivers available) https://wiki.lineageos.org/adb_fastboot_guide - ADB driver install (probably no effect) https://adb.clockworkmod.com/ - Reboot into bootloader mode With the device powered off, hold Volume Down + Power Enter recovera with Volume Up + Power - Enable offline charging fastboot oem enable-charger-screen fastboot oem off-mode-charge 1 fastboot reboot - Unlocking the bootloader (skipped as already by default) fastboot flashing unlock - Flashing additional
-
For my case it looked like a drivers issue, as those manual additions did not seem to work well. If the devices register and install themselves, things seem a bit more smooth.
-
Used a Win 10 tablet now. Pluging in the device shows the Qx1050 in device manager instantly, no need for driver updates. Copied files and linked path, run "adb devices" command and everything seem working. Sideload passed on the second attempt as on the first one it told me the recovery file is corrupted and system cannot reboot anymore. But I just redid the wipe and install. Gonna test now.
-
Will check for more devices.
-
From an official side there is no support for FxTec: https://developer.android.com/studio/run/oem-usb It might be that FxTec is similar to another manufacturer maybe.
-
It might be driver. But which to take ?
-
Tried with hub and without -d no difference.
-
It looks like this:
-
You mean if I change something on the physical connection it might support the ADB commandos ?
-
Everything works fine until I try to sideload. ADB commands are not accepted.
-
I see, so I need to start with step 6 ? And should I skip: fastboot flash recovery recovery.img though they tell me other recoveries may not work for installation or updates ? Or is the placed stock recovery already similar with the one meant for lineageOS ? And what about the installation command ? It is a adb command also: adb -d sideload filename.zip "Fastboot device" at least seems to answer with an ID.
-
So I am in the right place/state sending the right commands ? Sorry for asking so silly, but I'm kinda lost in translation. I'm no native English speaker. I thought all these installation instructions are ready to use, the images are ready to use and it refers windows systems. Currently it looks like Windows (in my case Win7) is not a good place to try connect to android systems. So what chance do I have to get Lineage onto my phone finally ?
-
The target system actively refused connection: But the antivirus and firewall are all shut down. The Device shows a screen telling: "Press volume key to select..." and "FastBoot Mode" in red letters. I am in the right place, am I ? And what did you mean ? Is it a matter of Windows not being able to put images on android devices ?
-
I see, volume up not down. Worked now. Can see bootloader screen. But still "adb devices" won't work. Also fastboot commands won't react. I have a Win 7 x64 here. Is it incompatible to the adb data loaded from https://wiki.lineageos.org/adb_fastboot_guide ? Do I need the complete Android studio instead ?
-
Installed that drivers, no difference. Accepting Google services and singing contracts with dark emperor leads me to the UI finally. Activated USB debugging and developer mode. Tried to do that fastboot thing. See black screen with a robot mentioned above.
-
This leads me to a black screen with a robot saying no command. Device seems frozen until it shuts off due to power save I guess. "ADB devices" tells "deamon not running" no adb.exe there to kill "adb kill-server" tells deamon not running"
-
Rewriting my comment. Maybe I am not precise enough. Hello, I currently feel stuck with: - Cannot login without Google account (it keeps me looping like forever between start page and Google login, there is no skip button, there is only "accept Google Services" even if WIFI is blocked for that MAC address specifically) - Cannot start bootloader with Power + Volume down (Maybe I am doing this wrong, seen something about having the right timing) - Cannot enable developer options and USB debugging on device as login is not possible (as this is part of the installati
-
...
