Oukitel WP10 - General development and hacking.

Oukitel WP10 - General development and hacking. - General Topics

I bought the Oukitel WP10 as my replacement for my previous phone, an AGM X2, which is was getting on in age. Reasons for purchase: 5g, ruggedized phone, giant battery, POGO pins on the backside for connecting ???
The phone, physically, is fine, It's giant brick with a big battery, a decent camera and all the usual sensors are there. It as the potential to be a really neat phone....and then you boot it up. Something was and is.....not right. The developers lobotomized their rom. Why? Who knows. Will they fix it? {edit: they did sorta}. The app drawer is missing so the phone dumps all your apps out on the home pages. 3rd party widgets don't work : you can set them up but if you reboot the phone, they don't update. The recent apps tab works with gestures and 3 button navigation but only with the stock launcher, which appears to be launcher 3 but is named quickstep? 3rd party launchers load, but can not access the recent apps tab. Some 3rd party apps refuse to load producing various error codes. The user interface feels like someone had an iphone and tried to model it's interface to this phone. This person did not succeed.
I have emailed the company my complaints and reasonably expect nothing to happen as I am sure the person who did this to this phone did it on purpose. May they be cursed with pubic lice and hemorrhoids.
That being said, if the phone's UI could be fixed, it would be a really nice phone and I have plans to mate those POGO pins with an Arduino or a PI because, let's face it, they aren't gonna make any accessories, are they? But I can make some really neat ones out of an Arduino and a 3d printed cover that fits over those POGO pins.
So the plan will be: 1. Root the phone - accomplished. 2. Compile TWRP against it. 3. Modify the stock rom so it it is fully functional. 4. Begin development of a customizable Android 10 rom. 5. Begin development of an Android 11 rom.
At this time, I can confirm that the bootlooder can be unlocked, you can sideload things with ADB, and a stock rom apparently exists and can be accessed through the Oukitel website. There is some kind of flashing tool too, but everything is in chinese. I downloaded the stock rom and it appears to be the same build as on the phone. I tried flashing just for giggles but kept getting signature errors. There was something in the chinese instructions about coping and renaming some files prior to flashing but I have not had time to figure it out yet as it is all in chinese.
I will be trying to extract the boot img as it appears that Magisk would work if I can patch the boot img and reflash. If/when I am successful, I will post it here. Any help is welcome.

**** 02/03/2021: Well wouldn't you know it, they released an update....so maybe not do this right away*******
Guide to rooting the Oukitel WP10.
disclaimer: I have tried to make the steps straightforward yet detailed. This is a high-risk activity with a high probability of failure.
Prologue: This guide assumes basic familiarity with ADB, fastboot, sideloading, and booting into your recovery. Please note ADB, fastboot commands will vary slightly depending on your installation, and whether you are a PC, a Mac or a Linux box.
Preplanning: inevitability screwing up your phone.
i. Back up, copy over and otherwise remove any valuable data from your phone. This process will delete all your old data.
ii. Obtain a copy of the stock rom. At the time of writing it is: OUKITEL_WP10_EEA_V10-R11 .zip which is hosted on Mega. You can find it at the Oukitel site -> Downloads.
iii. To reflash the stock rom you apparently need a tool called SPMDT. I am not familiar this tool and the instructions from Oukitel are all in Chinese so this will not be covered here at this time. It may be easier to do all of this using SPMDT. Review chinese Oukitel instructions on how to swap checksums and how to use SPMDT to restore your phone.
1. Install Magisk Manager - this is the tool we will use to root this phone. A more detailed explanation about how it works is here. Download directly on your phone and install or download to your computer and sideload using ADB.
Code:
adb install MagiskManager-v8.0.7.apk
2. Open Magisk Manager and verify that you can install Magisk. This phone does have a ramdisk, is encrypted but does not have a/b partitioning. There are 3 options: At this time, I can't find a TWRP custom recovery and do not yet know how to make one so downloading a zip to load with TWRP is not possible. A direct install seems to be for updating a previous Magisk installation? I am not sure and available information seems ambiguous. This leaves option 2: patch the stock boot image.
-2a. On your computer, open the stock rom and extract the boot.img file. Using ADB, upload it to your phone:
Code:
adb push boot.img /sdcard
This should send it to the users default directory. The /sdcard part may vary.
-2b. Open Magisk Manager on your phone and select option 2. Choose the boot.img file and Magisk will give it the clap.
-2c. Download the file to your desktop. Can probably open "Android Storage" in your file system and copy it over or use the following ADB command:
Code:
adb pull /sdcard/Download/magisk_patched_mzhsO.img ~/Desktop
Again, the *.img name and your preferred directory may vary and adjust command syntax for your OS.
3. Unlock the bootloader. You must first enable developer tools on your phone and then go to Settings ->System ->Advanced ->Developer Options -> OEM unlocking (turn slider on). This does not unlock the bootloader. It just allows you to unlock the bootloader. To unlock the bootloader, plug your phone into your computer using the USBc cable, make sure USB debugging is on and reboot your phone into fastboot by holding down the vol up and power buttons as the phone reboots. In the bootloader menu, choose fastboot by using the volume up to cycle through the menu options and then the volume down key to start fastboot. When all is ready:
Code:
fastboot flashing unlock
and a teeny-tiny prompt will pop up asking if you really want to do that. Use volume keys to navigate.
To relock the bootloader later (not now):
Code:
fastboot flashing lock
will button it up again. You might not need this ever.
4. I can't remember if it forces you to reboot at this point but if it does, just boot into fastboot again. Do not try to install the modified boot img file yet. If you do, you will send it into a fastboot bootloop (soft bricking your phone). This happened to me. I then learned that this phone, and I assume, most android phones past Android 8 are protected by Android Verified Boot which is part of a system that verifies that the firmware you are running is legit. In this case, it causes the bootloader to verify the boot and recovery partitions. We have to disable it to install the modified boot img. I borrowed the following commands from these threads here and here and here
-4a. vbmeta.img apparently contains checksums of the boot, recovery and maybe system partitions. The guy from the first link installed a custom vbmeta.img using the command below. I do not know whether this is generic vbmeta, whether it is vendor specific so I did not use the custom vbmeta he created.
-4a. Since I didn't know whether to use a vbmeta.img from another phone, I poked around until I found the 3rd link above which stated that I could just use a dummy vbmeta.img generated by using a python script AVBtool
I cloned it into Pycharm (or your preferred IDE...or you can rawdog it from the command line) from Google's github and ran the script as below:
Python:
avbtool make_vbmeta_image --flags 2 --padding_size 4096 --output vbmeta_disabled.img
-4b. I installed the vbmeta_disabled.img using fastboot.
Code:
fastboot --disable-verity --disable-verification flash vbmeta vbmeta_disabled.img
-4c. I then installed the modified boot.img (as discussed above):
Code:
fastboot flash boot magisk_patched_mzhsO.img
-4d. and rebooted: fastboot reboot
5. The system rebooted into the modified stock rom and I reinstalled everything I had backed up earlier. I confirmed Magisk had given me root access. HOWEVER: SafetyNet failed the ctsProfile check! There seems to be a fix for it here but since I don't know what it means or what it does and since the phone appears to be working, it will have to wait for later.
Epilogue. I am happy to report, that, after a bit of fiddling around, Magisk's Quickswitch module coupled with a very dodgy alpha Lawnchair2 apk I got from APKmirror through their Telegram group has resulted in a mostly functional rom! I now have an app drawer and gestures mostly works with the Lawnchair 2 launcher. Widgets still need to be reinstalled if you reboot. So...it now sucks a lot less.
Gentle reminder: this guide is rough and the result of only 1 pass through. And I screwed it up.

Due to an OTA update being provided from Oukitel it became necessary to learn how to use the SP Flash Tool.
Guide to reinstalling the Stock firmware for your Oukitel WP10.
(the bootloader will remain unlocked if you unlocked it as in the previous post)I loosely borrowed from the gents at GetDroidTips This process assumes you are using a Debian based linux distro.
1. Download the stock rom OUKITEL_WP10_EEA_V10-R11. Extract rom folder.
2. Download the latest SP Flash Tool . Extract.
3. On linux, there is an error regarding libpng12 which deprecated in newer versions of linux. For the reckless, a nice person from SO made up a custom .deb to install to fix this problem here. Otherwise you have to manually install it so that this program can find it.
4. Open your SP Flash Tool folder and run flash_tool. A nice little gui should pop up if it runs.
4a. Go to the Download tab and choose "MTK_AllInOne_DA.bin" as your download agent.
4b. Under scatter-loading file, navigate to the stock rom folder and "MT6873_Android_scatter.txt" should be the only option and choose it.
4c. Reading the windows instructions here recommended unticking the "preloader" in the payload section below these options on the Download tab as it might brick the phone, so I did. I do not know if this is necessary.
5. Turn off your phone. Then plug the USB cord in and hold the volume up key down so the flash tool will detect the device via USB. Can also try holding the volume down key down. Do not press power button like you would if you were planning to boot into fastboot.
If all goes well the flash tool will reflash the stock rom and reboot into stock rom. The bootloader will remain unlocked until you use fastboot to relock in the post above. There was an OTA update yesterday: OUKITEL WP10 EEA_V14_20210118 . The phone UI feels a little snappier but it appears that the stock rom launcher still does not have an app drawer. This might be a Google thing and not a Oukitel thing. However, 3rd party launchers with app drawers now work with 3 button navigation! The recents tab and app drawer appear to be functional. Gesture control still appears to be not functional with 3rd party launchers and some but not all not all widgets will update after a reboot. Cause to be determined. I have not tried to repeat the root procedure above.

hello, I am new and have been looking for threads about rooting c19 oukitel, but seems non exists. How could i start one?

dreadeye said:
hello, I am new...
Click to expand...
Click to collapse
....for phones that have a small user base, you can just start a thread for your phone under general like I did. Xda may be like Stack Xch where you need to have a certain number of posts before you can start your own thread. I don't recall. If so, you will have to reply to some posts first.

calfax said:
Will they fix it? {edit: they did sorta}.
Click to expand...
Click to collapse
Hey Calfax, not to hijack your thread, but I am thinking about getting this phone, would you mind explaining what the new update did and did not fix?

glitchhawk said:
Hey Calfax, not to hijack your thread, but I am thinking about getting this phone, would you mind explaining what the new update did and did not fix?
Click to expand...
Click to collapse
It fixed your ability to use a 3rd party launcher. It did not fix the widgets issue. I think this is an Android 10 issue more that Oukitel specific. Having a phone with an 8000 mAh battery has helped tremendously over the last few days.
The phone does not like to use 4g data and I do not know why.

sup op,
Just got oukitel wp10 today. I have just done a quick read through everything here and am probably going to try and get root going asap.
I have read elsewhere that treble based phones (such as this one) can basically have any treble enabled custom rom installed on them. I know very little about this but is it a concept your are familiar with?
am very glad someone has taken the intitiative here regardless. thanks for that!!
p.s. ditto on the pubic lice and hemorrhoids thing and also for whoever designed the xda app

Also, I bet the 4g issue your having is related to what bands the phone operates on. Who is your carrier?

I have obtained root and have a few nuggets of wisdom to offer regarding OP's instructions. First off BIG THANKS TO OP ONCE AGAIN FOR TAKING THE INITIATIVE!!
1. The first problem I ran into was with creating a vbmeta dummy image at OP's #4a in his second comment on this thread. There is a link to AVB Tools in the first paragraph and what is supposed to be a link to the tool on google's github page in the second paragraph but the link in the second paragraph to the github page is not working, so I defaulted to the first link but the AVB tool on that page, for whatever reason, is not working properly, while the tool on googles github page DOES WORK AS INTENDED.
I think what OP intended to link to was the following: https://github.com/PixelExperience/external_avb
REGARDLESS, I have attached a copy of my vbmeta "dummy" image to this post, so you can just use that instead if you prefer.
2. If you update your phone after isntalling magisk, you will have to go through the fastboot process again, and yes this means YOU HAVE TO DO THE VBMETA STEP AGAIN BEFORE THE MAGISK STEP OR YOU WILL BRICK YOUR PHONE.
3. I bricked my phone and was having trouble running the SPFLASH tool, linked in OP's third comment on this thread. IF YOU ARE HAVING ANY TROUBLE RUNNING THIS TOOL JUST DOWNLOAD THE LATEST VERSION OF UBUNTU AND RUN THE SPFLASH TOOL FROM AN UBUNTU LIVE USB. I tried on a couple different linuxes with the right kernel version and still had trouble so just do it from ubuntu live if you are having trouble.
4. If you are stuck in a bootloop like I was, you can still run the SPFLASH tool. Just get the tool setup, press download, then plug in your phone and hold the volume up button as it enters the off-stage of the bootloop, the SPFLASH tool will pick it up and start the flash process if you time it right.
5. OP says he is still having trouble with third part launchers but I was able to get Nova launcher running by installing it, then when holding down on the nova launcher icon on the home screen of the default launcher, there is an option to make nova the default launcher from there. idk if every 3rd party launcher will be able to do this, but Nova was.
6. OP also mentioned having issues with gestures, and pointed to it seeming to be a Google issue, and I have confirmed that it most certainly is, as there is a message in My Nova launcher settings that says:
Android 10 gestures Navigation
Google has not yet made gesture navigation compatible with 3rd party launchers. There is nothing that Nova Launcher can do to change this until a future Android update.
Click to expand...
Click to collapse
CURSED BE TO GOOGLE. PRAISES TO OP

Found this in the stock rom zip and translated it (was half in Chinese). Thought someone might find the info useful
Project Name: S1000D-Cloud Base-S85
Clients: Ozzie ...
Customer Configuration:
MT6873, FLASH: 128GB+8GB (Integrated UfS+DDR4X), Global GSM 4-band (2/3/5/8)+W 7-band(1/2/4/5/6/8/19, with RXD)+TD 2-band(34/39)+TDD 5-band(34/38/39/40/41)+FDD 18-band(1/3/5/8)+W 7-band(1/2/4/5/6/8/19, with RXD)+TD 2-band (34/39) + TDD 5-band (34/38/39/40/41) + FDD 18-band (1/3/5/5/6/8/19, with RXD 1/2/3/4/5/7/8/12/13/17/18/19/20/25/26/28A/28B/66) + CDMA 3-band (BC0/BC1/BC10, with RXD) + 5G 11-band (N1/3/5/8/20/28/38/41/77/78/79），Support NFC,support LCD screen (3 and backlight), support 9V2A charging, support oncell/incell TP (motherboard does not support separate TP connector), three rear camera: 4800W main rear camera+1300W wide angle camera+200W macro camera does not support thermal imaging, front camera 1600W, support fingerprint, battery built-in non-removable, does not support front flash, support secondary board SIM card, does not support T card, does not support RGB signal light (FPC), does not support HALL, support side buttons, support earpiece (connector FPC), support dual silicon wheat (main mic sub-board patch, sub-mic motherboard patch), smart amplifier, support TYPE-C headset (sub-board end), support light distance sensor (FPC), support G-Sensor, support GPS/WIFI/Bluetooth/FM, support geomagnetic, support gyroscope, support OTG, support rear camera flash (connector, FPC), support/laser distance measurement (sub-bo
ard end)/temperature measurement/night vision (plug-in) Support wireless charging (sub-board compatible）, Does not support UV / heart rate/air pressure / volatile gas detection/intercom plug-in / encryption chip/night vision fill light (FPC), antenna shrapnel (battery cover full paste&screen shrapnel full paste), support motherboard side ANT6 antenna, support motor, support power button，
Software version: //192.168.1.50/alps_q0_mp2_1/s1000_mt73_A_L/s1000d-yj-s85-a2-66-l-128G8G-fhdp-bom5-q0-cts-eu/R11
Release Date: 2020-12-17 16:08
LCD: 6.67FHD.Huaxing glass, middle perforated, cover glass Corning 3rd generation FT8756
SENSOR:
Wide Angle CAM Win-win-win-win-win I., SWAQ6925001A-VA S5K3L6XX03-FGX9
Macro Shadow Collar I., YL-YJS85-02M1-WJ 200W GC02M2
Post-secondary Shadow Collar I., YL-YJS85-02M1-WJ GC032A
Ex CAM Win-win-win-win-win I., SWAC205S100B-VA S5K3P9SP04-FGX9
Flash Model:
UFS+LPDDR4X(128GB+8GB) H9HQ16AFAMMDAR-KEM
UFS+LPDDR4X(128GB+8GB) H9HQ15AFAMADAR-KEM
UFS+LPDDR4X(128GB+8GB) KM8V8001JM-B813
Language Type: Multi-lingual
Version Download Instructions: Normal download, no need to erase
Download tool version: SP_MDT_AFterSale_20.32
Release Notes: First Archive
Click to expand...
Click to collapse

Hard bricked my wp10 with spflash. DO NOT FORGET TO UNTICK PRELOADER USING SPFLASH TOOL.
Hopefully the oukitel people can help cause I have spent hours now trying different fixes and have only managed to get a blank black screen by opening the phone, unplugging and replugging the battery (so technically some progress). But i can't justify spending any more time trying to fix.
This phone is (was) great and its nice to have no restrictions on rooting or whatever but great power/responsibility/etc, u know the drill
kinda surprised there isn't more activity around this phone on XDA though Cuz it is a sweet one.

Has anyone pursued anything further with this beast of a phone?
I have purchased one and used it several weeks now, and did find the operating system leaving a lot to be desired, and really dislike the iPhone-like swiping gestures that I initiate accidentally all the time. My company phone for my job is a newer iPhone with the same gesture motions, unlike my previous employer-provided iPhone.
This WP10 has amazing potential but really could still use a better custom ROM.
And my 6800mah Blackview BV9800 battery outlasts this 8000mah battery.
My biggest complaint so far is the GPS fixing using Locus Maps Pro or Google Maps.
I get a display of a multitude of satellites within view,but within 5 seconds, all GPS satellite fixing disappears on the Locus satellite display screen,and I can no longer get a location fix.
Same problem with Google maps, although I don't have any advanced tools to see the satellites being used as I do with Locus.
With locust, I can refresh the GPS connection and they reappear, but then still disappear immediately. This is very annoying when using a rugged outdoor smartphone for rugged outdoor navigation.
I might be replacing the faulty touch screen interface on my 1-year-old Blackview BV9800 if I cannot find an easy solution for this Oukitel WP10GPS issue.
A custom ROM or updated upgraded ROM would be very nice!
I'm not sure why the battery does not last as long as the Blackview's smaller battery, but I liked the size of the battery on this better than the current flagship Blackview models, and I also liked the more ruggedized case with far more screws securing the case halves together.
The BV9800 was the last of its kind from Blackview, the BV9900 has a slightly smaller battery and a less rugged appearing case, & the new 5G rugged version using the BL6000 is just an upgraded 5G version of the BV9900, same case design, battery still smaller than BV9800.
This is why I jumped ship after 3 Blackview rugged phones and tried out this Oukitel WP10. It has potential to be superior to the BV9800, but ROM issues are making me question switching back to the BV9800.

chuck.lambert78 said:
Has anyone pursued anything further with this beast of a phone?
I have purchased one and used it several weeks now, and did find the operating system leaving a lot to be desired, and really dislike the iPhone-like swiping gestures that I initiate accidentally all the time. My company phone for my job is a newer iPhone with the same gesture motions, unlike my previous employer-provided iPhone.
This WP10 has amazing potential but really could still use a better custom ROM.
And my 6800mah Blackview BV9800 battery outlasts this 8000mah battery.
My biggest complaint so far is the GPS fixing using Locus Maps Pro or Google Maps.
I get a display of a multitude of satellites within view,but within 5 seconds, all GPS satellite fixing disappears on the Locus satellite display screen,and I can no longer get a location fix.
Same problem with Google maps, although I don't have any advanced tools to see the satellites being used as I do with Locus.
With locust, I can refresh the GPS connection and they reappear, but then still disappear immediately. This is very annoying when using a rugged outdoor smartphone for rugged outdoor navigation.
I might be replacing the faulty touch screen interface on my 1-year-old Blackview BV9800 if I cannot find an easy solution for this Oukitel WP10GPS issue.
A custom ROM or updated upgraded ROM would be very nice!
I'm not sure why the battery does not last as long as the Blackview's smaller battery, but I liked the size of the battery on this better than the current flagship Blackview models, and I also liked the more ruggedized case with far more screws securing the case halves together.
The BV9800 was the last of its kind from Blackview, the BV9900 has a slightly smaller battery and a less rugged appearing case, & the new 5G rugged version using the BL6000 is just an upgraded 5G version of the BV9900, same case design, battery still smaller than BV9800.
This is why I jumped ship after 3 Blackview rugged phones and tried out this Oukitel WP10. It has potential to be superior to the BV9800, but ROM issues are making me question switching back to the BV9800.
Click to expand...
Click to collapse
i think the gesture issue might be an android 10 problem although i dont recall having this sort of problem b4 bricking my phone.
the gps issue i did experience and i can say that on other devices i have seen improvement to gps services from installing custom rom, walking/driving forward while trying to get directions or current location on map app, also enable wifi and bluetooth monitoring (google.says it helps but in most situations/locations i doubt it does)

É possível instalar o gsi treble rom no wp10? Notei vários erros.

Related

[Q] Huawei Y201 NFC U8666n-1 trouble

OK so I recently switched this neat, cheap and decent entry phone, and of course wanted to root and unlock the bootloader.
Using the technique outlined in http://forum.xda-developers.com/showthread.php?t=2066887 "[ROOT][CWM] Huawei Ascend Y201 Pro U8666" I managed to happily root the device. Meaning I could install droidwall and adfree, and uninstall one or two of the annoying Huawei apps. (Surprisingly there are less Vendor apps on this than the previous Ideos U8150 I had.)
So happy that that worked, I thought I would go to the next stage and unlock the boot loader, in preparation for maybe installing clockworkmod recovery. And eventually a ROM if I could find one that looked "safe" and sound.
Cranking up the "UnlockBootloader.exe" as before and clicking the unlock BOOTLOADER initiated something on my phone... However when I switched off my phone preparatory to rebooting, I found what I guess to be a bricked/borked device.
There's no vibrate, no flash on screen, no logo, no pink screen that other people talk about in the few reports I have found around the web. Just that the lower backlit soft buttons flash ten times and then nothing else happens. I can't even find information about what this obviously low level failure message means...
As you can guess, I have tried all sorts of things to get it going: battery removal; powering from USB while botting; any and all of the key press holds for boot; all to the same effect. Have tried several times to find anything similar on the net and can't seem to find anything similar. Especially the ten flash indicator
So my question is "Is this an absolute sign that the device is bricked?" I guess I could try to play the innocent and send it back under warranty, but I guess someone will realise it was my fault. Unless a memory failure happened at the exact time I was flashing/unlocking...
And a warning that same device owners should be careful when following the guide. I'm pretty sure I had everything as outlined. I'm running XP, didn't have it mounted, had fastboot off, etc... Although now its hard to check on the device to see if that was the case

and also
I should also perhaps add that before using UnblockBootLoader with root success, I tried the ICS "adb restore" directory traversal vulnerability, which is part of Root_with_restore, and was unsuccessful.
And that there's no life reported at a low, USB device level to my linux kernel, when plugged in now. So I can't even try a firmware patch using adb etc.

Of course I can't post a relevant cautionary note into the above mentioned thread, as I have yet to reach the 10 post milestone mark, enabling me to post in that section...

Hi,
Sorry for opening an old thread, have the same issue and just wanted to know if you manged to resolve this or it you just took it back to the shop?
Regard

No solution
No - I never managed to work out or find a solution. I just got a new one, and only went as far as the root'ing stage.
I have never seen an applicable ROM for this device anyway, so I guess it wasn't too much of an issue. And root'ing to get those crucial management apps installed, and also being able to remove some Huawei "cruft" is the real thing you need.

[Completed] Jide Ultratablet ADB-Fastboot Recovery Flash Problem

Where to begin? Logic would dictate, the beginning.
I'll do my best to be brief with the backstory.
Months ago I ordered a Jide Ultratablet to use as my portable workhorse. At first things were peachy until a rather monumental lag began to manifest every 15-45 seconds. It made the device impossible to utilize in any productive fashion, so I contacted Jide and opened up a support ticket. After months (in no way an exaggeration) of barely responsive correspondence, during which I sent them a video to demonstrate the problem, they finally came back to me with an email containing a link to a compressed folder containing the Remix 2.0 images, and also a link to a rather vague and complicated tutorial on how to flash Remix 1.5 manually to a device. (In fact, I tried to include a link to the tutorial, but I am unable to since I haven't posted to the forum enough. I am happy to PM it or email it to anyone who might like to help) I can only assume I am meant to apply the same logic to the Remix 2.0 files they sent me. Seemed a bit dicey at first glance, but while I'm by no means an expert, I'm no slouch in this arena and I'm a very quick study.
Now, on to the proverbial meat and potatoes:
If you were able to contact me for a link to the tutorial in question, you will have undoubtedly seen that they indicate one should use ADB-Fastboot as a means to flash the recovery image. No real surprises there. I have ADB and Fastboot installed on my PC (Windows 10). I also have the ADB drivers installed and have confirmed the addition to my PATH. (eg: ;C:\ADB) I can also confirm that it is working fine since I am able to pull up a terminal and issue the ADB command and it gives me the usual wall of commands. The problem is that my device (Ultratablet) is not being seen by ADB. I have checked my USB drivers and they are all up to date and installed properly. My PC sees the device no problem and there is no indication of any sort of connection error. I've also tried different cables and ports. Yet, I can't access it via ADB and thus am unable to issue commands to my device such as "adb reboot bootloader" or "fastboot reboot-bootloader".
My next logical approach was to attempt forcing the device into fastboot mode using the hardware button combination, which is not listed specifically for the Ultratablet anywhere, I might add. (Power key + Volume up) It brings me to a boot options menu with the selections "Continue/Fastboot Protocol/Recovery Kernel/Reboot/Poweroff/Forced Recovery". Ateempting to select Fastboot Protocol causes the display to shut off for a moment, the device to vibrate once, and then the display to turn back on back at the same menu full of selections.
So, in summary, I am expected to flash the device using fastboot and yet I can't even get the device into fastboot mode, let alone issue commands from my PC terminal. As I highlighted near the beginning, teh Jide support team is incredibly unresponsive and not overly helpful. I have notified them of this same set of issues, but I don't expect to hear back in any expedient fashion and I thought one of the mighty members here on XDA might be able to help me come up with a next step in the meantime. I'd cerainly love to be able to use my shiny new tablet.
In any case, thank you for your time.
Kind regards.
Shaiden

XDA Visitor said:
Where to begin? Logic would dictate, the beginning.
I'll do my best to be brief with the backstory.
Months ago I ordered a Jide Ultratablet to use as my portable workhorse. At first things were peachy until a rather monumental lag began to manifest every 15-45 seconds. It made the device impossible to utilize in any productive fashion, so I contacted Jide and opened up a support ticket. After months (in no way an exaggeration) of barely responsive correspondence, during which I sent them a video to demonstrate the problem, they finally came back to me with an email containing a link to a compressed folder containing the Remix 2.0 images, and also a link to a rather vague and complicated tutorial on how to flash Remix 1.5 manually to a device. (In fact, I tried to include a link to the tutorial, but I am unable to since I haven't posted to the forum enough. I am happy to PM it or email it to anyone who might like to help) I can only assume I am meant to apply the same logic to the Remix 2.0 files they sent me. Seemed a bit dicey at first glance, but while I'm by no means an expert, I'm no slouch in this arena and I'm a very quick study.
Now, on to the proverbial meat and potatoes:
If you were able to contact me for a link to the tutorial in question, you will have undoubtedly seen that they indicate one should use ADB-Fastboot as a means to flash the recovery image. No real surprises there. I have ADB and Fastboot installed on my PC (Windows 10). I also have the ADB drivers installed and have confirmed the addition to my PATH. (eg: ;C:\ADB) I can also confirm that it is working fine since I am able to pull up a terminal and issue the ADB command and it gives me the usual wall of commands. The problem is that my device (Ultratablet) is not being seen by ADB. I have checked my USB drivers and they are all up to date and installed properly. My PC sees the device no problem and there is no indication of any sort of connection error. I've also tried different cables and ports. Yet, I can't access it via ADB and thus am unable to issue commands to my device such as "adb reboot bootloader" or "fastboot reboot-bootloader".
My next logical approach was to attempt forcing the device into fastboot mode using the hardware button combination, which is not listed specifically for the Ultratablet anywhere, I might add. (Power key + Volume up) It brings me to a boot options menu with the selections "Continue/Fastboot Protocol/Recovery Kernel/Reboot/Poweroff/Forced Recovery". Ateempting to select Fastboot Protocol causes the display to shut off for a moment, the device to vibrate once, and then the display to turn back on back at the same menu full of selections.
So, in summary, I am expected to flash the device using fastboot and yet I can't even get the device into fastboot mode, let alone issue commands from my PC terminal. As I highlighted near the beginning, teh Jide support team is incredibly unresponsive and not overly helpful. I have notified them of this same set of issues, but I don't expect to hear back in any expedient fashion and I thought one of the mighty members here on XDA might be able to help me come up with a next step in the meantime. I'd cerainly love to be able to use my shiny new tablet.
In any case, thank you for your time.
Kind regards.
Shaiden
Click to expand...
Click to collapse
Greetings,
Thank you for using XDA Assist.
First, you'll need to create an account so you can post in the other sections.
After you have done that, you can post your questions and ask the experts here:
http://forum.xda-developers.com/android/help
You're sure to receive quality answers there.
Good luck and welcome to XDA!

S5 glitching in and out of monitor mode? or just a patchwork mess?

Im new to all this so pay no attention if its nonsence...
My S5 G900f has a qualcomm snapdragon chipset, that doesn't support monitor mode, which i believe means that it doesnt support packet injections or packet capturing (driver related?)
using the dsploit.apk for things like session hijacking, replacing web page images of a target and using script 'injection' to inject custom java script into a target web page, all sounds like things you'd need monitor mode to do. and if it is then i was able to do it with my S5.
I dont know a lot about coding or how it all fits together and communicates with the hardware, so i may sound completely stupid, but this has done my head in for ages, so why not get it out there.
1. when i attempted to upgrade from my first custom rom, i had a bit of trouble, softbricked my phone and then flashed the two roms in various, alternate, wipe, format and install combinations until it finally booted to set up, and i stopped panicking. but this caused features from the first rom to appear within the second rom.
ie: 3minute battery mod was installed through a add-on zip along with the first rom and nothing to do with the second at all.
2. inconsistencies within the file system, like file names that were apps included with the first rom.
3. dsploit.apk was bugged and crashed every 5 or 10 minutes. then would seem to glitch or stutter for a couple seconds before correcting its self and accomplishing its pen test.
4. i also remember watching green text in the terminal as it failed to connect or ID some part of the system but continued to retry in quick succession until it glitched and worked. (i think this was a similar type of app i was trying out at the same time but instead of GUI stutters, i could see the text rapidly stuttering and glitching.)
4. the dsploit.apk worked for me back then, even though it was temperamental. ive downloaded the apk a couple times since with various roms and ive got no where with it...
was thinking maybe different aspects of the two roms had been filed or grouped together and created unstable triggers within the software, allowing it to briefly communicate with the chipset. i may be way off, but ive been sat here waiting for someone to solve this issue forever, i thought id share my thoughts, on the off chance it turns out to be something and i can finally get my S5 into monitor mode without OTG cables and other unwanted auxiliary components.
thanks in advance
G Carter

Do a clean install of you ROM, and please, don't panick. If you want to have a good time flashing ROMs and stuff, panicking is the last thing you want to do, it will cause stress and stress can lead to not being careful enough so stuff like this happens, well, always, if you are experiencing issues do a clean install. Just boot into recovery (I recommend TWRP) and wipe everything except external sd. Open ADB and sideload the ROM (or, if you have enough memory on a flash drive, plug it into your android and flash it from there) and then Google Apps.

General ROLL-UP -Joying 2GB - Sofia ( Non MTCB/MTCD )- Tips, tricks and mods

There is getting to be quite a bit of information to look through when looking for tip/solutions related to the new Joying 2GB / Sofia units. Since this is not a MTCB or MTCD unit, the threads seem to be scattered all over and very difficult to find in searching. I have seen roll-up threads for other units, that contain information such as ROMS available, tips, tricks and useful information. Kind of a "one stop shop" for the newer Joying HUs. If you have useful software, mod, tips, customization's, get something to work, etc please post here and I can include.
CPU Information - Rockchip Sofia x64 C3230RK / mali 450 GPU / Up to 1.2Ghz / 4 core / FYT5009 SoM - rated to run at up to 85C. My particular is unit clocked at 1.04Ghz.
Advanced Settings Password: 3368
Homescreen menu: 8086
Backlight Current menu: 5768
Android 6 Thread
https://forum.xda-developers.com/an...ing-intel-head-unit-android-6-update-t3597121
Android 6 specific tips:
ADB Access: https://forum.xda-developers.com/showpost.php?p=71616884&postcount=273 -OR-
https://forum.xda-developers.com/showpost.php?p=72057022&postcount=12
Viper4Android: https://forum.xda-developers.com/showpost.php?p=72064749&postcount=41
Latest ROM - Current ROM can be downloaded from link on the Joying blog site.
https://www.carjoying.com/Joying-blog/59.html
Android 5.1 Discussion about the Feb 22, 2017/March 5, 2017/March 15, 2017 updates:
https://forum.xda-developers.com/an...d-units/joying-intel-update-feb-22nd-t3561285
People have experienced issues with the Joying Launcher (UI3) after the update. This seems related to having other packages (google voice search ) installed prior to installing the ROM. Install time 25-35 minutes.
Recovery from non-bootable system - Without being able to access recovery, about the only solution is to reload the ROM package. Unzip ROM to SD card or USB stick, put in unit (GPS Maps slot, if using SD card ) and press the 'recessed' reset button. The unit should find the update and reload the ROM. This will wipe your data, but does leave the apps. If you use titanium backup, and have a backup, you can restore your data fairly easily. See blog article above for step by step instructions.
Root - Unit comes with root accessible in adb. SuperSU can be installed easily. There are 2 methods for installing superSU. The first method is an overwrite of the boot partition with a pre-rooted image. Problem here is if future upgrade makes boot partition changes, this method will overwrite with an older version. I recommend method 2, which modifies the existing boot partition ( need source so I can provide credit ).
https://forum.xda-developers.com/showpost.php?p=69648860&postcount=84&nocache=1&z=8361786322568856 (over-writes boot partition / may not work on Joying Feb update )
https://drive.google.com/file/d/0B4qmTV7N4JliSjZMdGg3Z18wbkU/view?usp=sharing ( modifies existing boot partition )
OS & Google Apps - Android 5.1.1 ASOP based w/ pico installation of google applications. Voice actions are supported with installation of 'Google App' from play store. No support for google search talk back.
Recovery- A recovery partition is present but does not have any type of graphical UI. It does look like a complete stock android ( command line ) recovery, but no access using USB is available. It maybe be possible using PC-PC OTG cable.
SD Cards - I have not heard of any sdcard size limitations, up to 200GB have been reported to work. Must be formatted as FAT32. NTFS, exFAT, and ext3/4 do not work. You can format a USB stick with ext4 and it will work fine.
Google Voice Calling - Stock BT dialer crashes when being called from google applications ( such as google voice search ). Workaround is available.
https://forum.xda-developers.com/an...oogle-voice-to-initiate-calls-joying-t3528923
Enable OK Google from any screen - https://forum.xda-developers.com/showpost.php?p=72447390&postcount=968
Bluetooth Tethering & BT Settings - Bluetooth tethering, connects instantly, very reliable connection, works great for streaming music, gps etc. Saves phone battery vs WIFI hotspot. Limited to ~2Mbs ( slower than WIFI sharing )
https://forum.xda-developers.com/an...elopment/bluetooth-settings-launcher-t3504526
(also good discussion here on the effects of process killing when entering standby )
Difficult to pair BT devices - Forces device pairing into database - Device pairs normally once HU thinks it has connected previously. I was able to pair TPMS, keyboard, etc using this method(s).
https://play.google.com/store/apps/details?id=com.brachcon.btautopair&hl=en
Modified stock bluetooth app to allow connection to all devices
https://forum.xda-developers.com/showpost.php?p=71280945&postcount=88
Backup Cam guideline mods - Make your lines match your camera view
https://forum.xda-developers.com/showpost.php?p=70325711&postcount=403
Apps not working after resume - The joying code will kill most applications when going into standby. This is really bad for apps that are supposed to be run at boot and background process, as they are not restarted when exiting standby. Symptoms include, widgets not updating, apps not getting GPS lock, process show running but background services are no longer running. This can be fixed by installing an updated apk file in /system/app/Sofia-1-C9-Server-V1.0 which removes the task killer. Also the key/button mods V2+ (below) will remove the task killer.
https://forum.xda-developers.com/showpost.php?p=71047452&postcount=62
Key/Button Mods - Extend the usefulness of your steering wheel keys and on unit buttons- V2+ also removes app kill on standby.
https://forum.xda-developers.com/an...-units/joying-2gb-steering-wheel-key-t3543390
If you just want to change the SRC button to call up google voice search, go here. ( also removes task killer )
https://forum.xda-developers.com/showpost.php?p=70480258&postcount=549
Immersive Mode / removes top navigation bar - No app needed - Full Screen on apps you choose, can be set from adb w/ root. Argument is list of package names separated by "," or "*" for all apps. ( survives reboot )
Specific apps:
settings put global policy_control immersive.full="com.google.android.apps.maps,com.pandora.android,com.spotify.music"
All apps:
settings put global policy_control immersive.full="*"
Clear / back to default
settings put global policy_control immersive.full=
Change Overscan - problems touching the corners, changing overscan can help:
https://forum.xda-developers.com/showpost.php?p=71492575&postcount=169
Phone/Tablet view on apps - No app needed - Change from 160dpi -> 161dpi gives "phone" view of many apps instead of "tablet" with no noticeable size change to other things. Done via adb. Requires reboot to take effect.
> wm density 161 # ( phone mode apps )
> wm density 160 # ( original tablet mode apps )
Heatsink mod Unit can run hot at heavy cpu load (such as benchmark testing). Can slightly reduce performance by throttling. Some users opt to add additional heatsink/fan to reduce temperatures.
https://forum.xda-developers.com/an...inside-look-joying-android-head-unit-t3546872
Red Themed Radio - Re-theme of stock apps - Don't like the look, change it. Can be done easily by unzipping the apk file, change images, rezip and install.
https://forum.xda-developers.com/showpost.php?p=70367793&postcount=434
More Radio Mods ( Layout change, more colors )
https://forum.xda-developers.com/showpost.php?p=71625005&postcount=286
xposed / xposed framwork - At this time, I am not aware of any way to make this work with the new Joying units. I have tried several packages and all have resulted in a non-bootable system. Please let me know you go get it to work.
Viper4android - Installer script that works on these models
https://forum.xda-developers.com/showpost.php?p=71317345&postcount=101
Nova or other launcher - Need to freeze or remove stock Joying launcher(s) in some cases, for other launchers to work correctly.
Other very useful Joying 2gb/sofia threads:
Audio Discussion / DACs - https://forum.xda-developers.com/an...ts/joying-2gb-sofia-headunits-common-t3577217
https://forum.xda-developers.com/an...pment/joying-android-5-1-1-2gb-units-t3465561
https://forum.xda-developers.com/an...opment/2gb-ram-intel-cpu-heres-specs-t3468322

Yes this is really needed. A FAQ with overview links and tips in just one post

Some people mentioned it was possible to boot into a restore function from a memory card with the update zip. If true, do we know what the exact process is? Any keys need to be held down?
Update, verified this procedure works:
sonof said:
I did recover from endless Android logo (resulting from trying to root with Joying HU root.zip found in this thread).
I did the following:
Put latest Joying update files to microSD card and insert it to GPS slot. Press and hold both reset and power buttons. Once it boots continue holding reset button.
This lead to automatic install of Joying update files and my HU was back alive but I hate the Joying company for not providing means to enter recovery and a complete ROM.
Edit: For me it did not ask if I want to update or not. It just began updating automatically. In contradict to the post above. But I was unable to boot to Android when I tried this.
Click to expand...
Click to collapse

My VW has reverse parking sensors. Does it not support those?

Just installed this unit. Speedwise it's night and day compared to my old Erisin (1gb 3188). Display is nice and crisp. Bit of a fiddle getting it mounted because of all the crap that needs to be stuffed behind it, but after some swearing and elbow grease I got it secured.
From the instructions, I cut an orange wire because I don't have a backup camera. I do however have optical parking sensors. On my Erisin this was supported (it showed a car model and visual indicators on screen). This unit doesn't appear to have this function. Can anyone confirm? I still get the beep from the speakers, so it's not really a big issue, but would be nice to know.
---------- Post added at 10:49 PM ---------- Previous post was at 10:49 PM ----------
catu said:
My VW has reverse parking sensors. Does it not support those?
Click to expand...
Click to collapse
Didn't see your post before asking the same question

anotheruserx said:
I'd like to work on this one.
But I have two questions;
1) did you manage to get any logs of how it failed?
2) When you made it unbootable, what was the exact procedure you used to recover the unit?
Click to expand...
Click to collapse
I didn't get any logs, as I couldn't connect to it until I reloaded the ROM. If I was able to make a USB connection, at least I could have looked at the logcat.
Procedure to recover: Insert USB drive with ROM, push recessed reset button, wait 30m for ROM to install, set up apps again. I have this procedure down pretty good. - The joys of playing with the system partition without USB access or recovery tools.

catu said:
My VW has reverse parking sensors. Does it not support those?
Click to expand...
Click to collapse
Actually, it turns out it does, however only when there's an obstacle (hopefully we can change this). Yesterday I only tested while stationary. Today I used it while driving, and noticed that whenever the sensor picked something up, the unit does actually display the sensors. It feels next to useless for me when it only shows on beeps, but at least we know it's there.

Well, that is the way my discarded Newsmy worked. Takes getting used to, but you then again you don't really need confirmation that "nothing" is in your way
Will need to think about this then, thank you.. Cant make up if I want this or the Ownice C500.

catu said:
Well, that is the way my discarded Newsmy worked. Takes getting used to, but you then again you don't really need confirmation that "nothing" is in your way
Will need to think about this then, thank you.. Cant make up if I want this or the Ownice C500.
Click to expand...
Click to collapse
After updating to the January firmware parking sensors are gone completely.
edit: enabling "radar" is the solution

Installed supersu (like described in this thread) yesterday and updated it from the play store. Worked fine.
Then I installed Viper4android, also from the store. I didn't expect it to work, but it does! Driver installed, and after a reboot it does exactly what it's supposed to.
Also installed Nova Launcher and set as default home. No issues with that so far. I have not frozen or uninstalled any of the original launchers.

On my Joying unit 130N2 (8 inch unit for VW) the backlight on the display does not work when it is cold. We had minus 8 degrees centigrade here and it took more than 10 minutes before the backlight came on. The radio is playing music and it is actually possible to change channel as long as you know where to touch the monitor. Today it was 5 degrees and it took only about 3 seconds before the backlight came on. I wrote Joying about it and they confirmed to me that there was an issue with 8 inch models for VW. They told me that they were working on a completely new firmware that would fix the problem. I told them that to me it seemed to be a hardware problem and how they wanted to fix that with a software. Their answer of course "No worry my friend ......". I told them that I wanted to return the radio because a radio that doesn't work when it is cold is useless to me. They told me that I would have to send it to China so that their engineers could investigate the problem. I then told them that I had bought it from a German website and it was delivered to me from Germany so if their wanted it to be sent to China then they would have to pay me for it - in advance. They told me that their warehouse in Germany did not accept any returns so it was impossible for me to return it. Then I opened a case with Paypal for selling defective merchandise. Then suddenly their warehouse in Germany was accepting returns. I had put this text also on the Joying Forum, but of course they deleted it. So when dealing with Joying and in case you have problems my advice is to be very tough on them otherwise they will BS you.

Kurt Lund said:
On my Joying unit 130N2 (8 inch unit for VW) the backlight on the display does not work when it is cold.
Click to expand...
Click to collapse
I have the same problem on the same unit. With the car headlights off, backlight is dim when it's cold, but gets brighter when it has time to warm up. And when the headlights are on, the backlight isn't on at all until it warms up.
I thought about writing Joying about it but I expected the kind of response you got. Plus, I've had my unit for a few months already so a PayPal claim isn't an option. Please let us know if you hear anything else about it from Joying.

Hi Joshnat,
Yes we have the same problem. Sometimes I can get mine to light up by turning the headlights on and off a couple of times. Are you sure that you cant make a Paypal claim? As far as I know you have 180 days.
Anyway, you should write to them and let them know that you know that many others have this problem.
Regards
Kurt

Kurt Lund said:
On my Joying unit 130N2 (8 inch unit for VW) the backlight on the display does not work when it is cold. We had minus 8 degrees centigrade here and it took more than 10 minutes before the backlight came on. The radio is playing music and it is actually possible to change channel as long as you know where to touch the monitor. Today it was 5 degrees and it took only about 3 seconds before the backlight came on. I wrote Joying about it and they confirmed to me that there was an issue with 8 inch models for VW. They told me that they were working on a completely new firmware that would fix the problem. I told them that to me it seemed to be a hardware problem and how they wanted to fix that with a software. Their answer of course "No worry my friend ......". I told them that I wanted to return the radio because a radio that doesn't work when it is cold is useless to me. They told me that I would have to send it to China so that their engineers could investigate the problem. I then told them that I had bought it from a German website and it was delivered to me from Germany so if their wanted it to be sent to China then they would have to pay me for it - in advance. They told me that their warehouse in Germany did not accept any returns so it was impossible for me to return it. Then I opened a case with Paypal for selling defective merchandise. Then suddenly their warehouse in Germany was accepting returns. I had put this text also on the Joying Forum, but of course they deleted it. So when dealing with Joying and in case you have problems my advice is to be very tough on them otherwise they will BS you.
Click to expand...
Click to collapse
You may have a faulty screen, my first one did something similar and wasn't very responsive to touches. I returned and my second unit was like night and day with how much better it looked and worked.

Has anyone got a factory backup camera to work? I have a 2015 Camry and right now I have the older Pumpkin rk3066 and the place that installed it hooked up the factory backup camera. I got my new Joying hu yesterday and am going to install tomorrow myself. I'm really hoping I can use my factory camera with this head unit also.
Sent from my LG-H918 using Tapatalk

mad212 said:
Has anyone got a factory backup camera to work? I have a 2015 Camry and right now I have the older Pumpkin rk3066 and the place that installed it hooked up the factory backup camera. I got my new Joying hu yesterday and am going to install tomorrow myself. I'm really hoping I can use my factory camera with this head unit also.
Sent from my LG-H918 using Tapatalk
Click to expand...
Click to collapse
I have the same car and HU, my oem backup carmera works. I bought a harness on Amazon including backup camera, USB, and aux in.
https://www.amazon.com/gp/product/B01BM3QGCO/ref=oh_aui_detailpage_o01_s00?ie=UTF8&psc=1

Quick tip:
You can adjust backup camera brightness, saturation and contrast by touching the screen while backup camera is on.

Is there a trick to putting in the sd cards? Mine won't click in so it won't mount.
Edit: Forget it i just had to get the edge of a screwdriver and push it in. Had me worried for a minute.
Sent from my LG-H918 using Tapatalk

Does anyone have a link or info on the dummy proof DIY on how to Root the joying unit? I want to install some of these enhancements so need to root the device and have never done it so was looking to see if anyone has a link or good write up for the slow like me. Appreciate it. I have a Joying 2gb 7 inch unit.
Looking to install this option
https://drive.google.com/file/d/0B4q...ew?usp=sharing ( modifies existing boot partition )

thedru13 said:
Does anyone have a link or info on the dummy proof DIY on how to Root the joying unit? I want to install some of these enhancements so need to root the device and have never done it so was looking to see if anyone has a link or good write up for the slow like me. Appreciate it. I have a Joying 2gb 7 inch unit.
Click to expand...
Click to collapse
Within the zip there is a file with instructions - HOWTO.txt
How-To install:
1. You need a Windows PC that is connected to the same WiFi network as your HU.
2. Unzip the attached file somewhere to your disk.
3. Run CMD.exe as Administrator
4. Change directory to the folder that you unzipped.
5. Run the install.bat script with an IP address of your HU as a parameter:
C:\Users\<username>\Downloads\Joying_JY-UL135N2_SuperSU> install.bat 192.168.123.137
6. Wait until script finishes and reboot your Head Unit.
7. DONE!
You should now have the SuperSU application working.

second hand rooted LG V500N with unknowns

Hi,
I got "new" phone, model as per title. It appeared it's been previously rooted and has Magisk installed. Poor creature selling this to me has no idea about those things and he got it like that from his friend in different country.
As this is replacement of my personal phone, after I sunk S9+ and decided to break up with "S", I have not much eagerness to experiment.
Current firmware (as what phone shows) is V30c-KOR-XX seems based on Android 11.
I'd leave as it is but... Google Pay doesn't like the fact phone is rooted. I have no issue with that phone is rooted but with that I can't use Google Pay.
Additionally, despite setting EN-US as language I see lots of Chinese or Korean or Japanese "letters" here and there - not causing any more issues than esthetic. I'd prefer to not have it so probably to load phone with some different firmware. Would be lovely if that could actually have "Polish" (as I am).
Also, I tried to get to "recovery" and phone does not react to Power+Vol Up - please correct me if that's not the right combination. When I used Magisk to reboot into Recovery then I see "No command" message...
Magisk is current - 24.1 and same "app".
So my options would be:
- fixing what is currently (ignore not having Polish on it) and making GPay works
- loading some factory firmware and unrooting it
- loading something different which would also allow to make GPay to work
I'm not complete noob, and got years of Linux exp as this is my only OS I work on. Also I was playing with rooting, firmwares and kernels but that was age of Samsung S2 and S4 when I did it last time, therefore I know many things changed and some might be easier some harder to do. Additionally, this is my first LG as somehow I always had "S's".
What I'd like to ask community here is to help me determine exact (versions, links) software I possibly could use and provide some guidance on how to do this "these days".
So to make things easier, I will ask questions:
1. What firmware should I load and how (preferably using Linux)?
2. How to fix (if necessary) "missing" recovery ?
3. How to make GPay running if suggested firmware is not factory one?
To be clear, I don't mind using current firmware loaded on phone if I can make things work. Less work is better for me as I can't be left without phone for longer than a day.

Database Info

welcome