yashsingh1/xdaforums huggingface dataset:
[Vivo Nex Questions & Answers] AdrienIwy:
Update : It's stopped working or working like 3 times on 54 :eek:

Anyone knows where I can buy a new fingerprint reader ? :confused:

I checked eBay, Aliexpress and others sites but I can only find screen or others parts but not the actual fingerprint reader :mad:

I even contacted Vivo by mail but they said me that I need to get to a local service store and I can't cause I'm in France.
[Vivo Nex Questions & Answers] Saloei:
Your scanner could just be disconnected considering you dropped the phone a few times. If you could open up the phone you'd be able to check. I've never done it so I can't help but this video might get you started >> https://www.youtube.com/watch?v=H-lIsNoM39w
[Vivo Nex Questions & Answers] AdrienIwy:
Hi Saloei, thanks for answering but I've already opened my phone and checked if the ribbon connector wasn't disconnected however it didn't change anything.. :crying: I think the problem is coming from the bga chip that manage the scanner, it might be desoldered a bit, that can explain the fact that it's working 1/5 times.

Update : I've just opened my phone another time and I've manage to take pictures of it and read the QR CODE on the chip. I've also learned that the fingerprint scanner is made by Goodix, I've contacted them but no responses.. sorry for flooding but does anyone knows to how to find it from this code (from qr 7Q7988XB03VG )

Or this picture? Thanks ?
[Vivo Nex Questions & Answers] timvonlee:
It happened to me because I changed the dpi from 540 to 360. FP scanner works well, but everytime you restart your phone in non-default dpi the FP scanner stops working.

Solution is to

1. Restore the stock dpi

2. Restart the phone and then

3. Change the dpi according to your preference.

Repeat all this on every restart.

I'm three months late to this thread. I also have this issue with my current vivo phone which has an in display FP scanner (IQOO). It happened to me because I had disabled almost all of the bloatware apps. If you restore those apps through adb or by factory resetting the FP scanner will work again.

Thanks.
[Vivo Nex Questions & Answers] AdrienIwy:
Hello Timvonlee, do you had an error of fingerprint authentification in settings?

How do I restore bloatware apps through Adb ?

I've already tried factory reset.

Thanks for answering
[Vivo Nex Questions & Answers] timvonlee:
https://xdaforums.com/showpost.php?p=79510981&postcount=166

https://xdaforums.com/showpost.php?p=79468247&postcount=8
[Vivo Nex Questions & Answers] AdrienIwy:
Thanks, but I think it will do nothing because I've already factory reset it and it does the same thing exept it restore all from factory.
[Vivo Nex Questions & Answers] Goldflamex:
Hi Nexers, I have a Vivo Nex S Chinese Version (living in Europe). Unfortunately I dropped the phone back in February and my screen went black. I ordered a new screen on Taobao which then took roughly three months to get here:rolleyes:. So I finally assembled the new display last weekend, everything works perfectly except the fingerprint reader. The reader seems to be not recognized because in the settings tab every fingerprint option is grayed out. Currently I’m troubleshooting, everything seems to be plugged in correctly. Could this be because of a link between display and fingerprint sensor (security issiue)? Does somebody has experienced something like this?

Thank you

Cheers
[Vivo Nex Questions & Answers] Lyngze:
I just experienced the same thing.

I had my phone om yesterday, everything worked just fine.

The phone ran out of power and when I got home I plugged it in for the night. This morning the scanner did not recognize my finger, and I figured I would re add my fingerprints, but upon removing Them the option is now grayed out and I cannot add or use fingerprints.

The options menu says "Fingerprint authentication error. Restart the device or contact custommer service."

I have of course restarted the phone, and the engineering menu also says "IC not found"...

No drops or anything for me... Any ideas?
[Vivo Nex Questions & Answers] AdrienIwy:
Hi guys, I haven't seen your messages until today, now I still didn't found any website that are selling these. I'm starting to lose patience and hope..
[Vivo Nex Questions & Answers] Jeanjipm:
Hi guys, exactly the same problem for m'y vivo nex s... Same conditions, as Lyngze no drops, the fingerprint scanner just stoped working one day, after removing the memorised fingerprints, the option menu turns gray with same message.

Is anybody found à solution ?
[Vivo Nex Questions & Answers] tweako:
I've also the same problem :(

I had some RSI problems with my hand so I've used my phone with my other hand for a few months.

In this period i didn't used the FP reader. When I start using my phone with my normal hand the FP reader doesn't work anymore??

I also got the message: Fingerprint authentication error. Restart the device or contact customer service
[Vivo Nex Questions & Answers] AdrienIwy:
Hey guys, sorry to up my old topic, but like 2 months ago, sound from the speaker started to make weird noises and stopped working like 1 week later. Same for the vibration motor and it was a pain to charge the battery. But I noticed when I was pushing on the back cover, sound was working a bit so I took appart the back cover and started jiggling the flex connector that was between the motherboard and the daughter board. I tought that the soldering circuit inside the flex connector was faulty. So I ordered a flex connector on aliexpress, just received it this morning and put it in my phone. And guess what! Sound, vibration, charging and also THE FINGERPRINT READER worked fine !
[Vivo Nex Questions & Answers] tweako:
Wow that's great!

Which one did you buy?
[Vivo Nex Questions & Answers] AdrienIwy:
https://a.aliexpress.com/_BU2sS3 don't know if I can publish Ali links but it's the nex pcb fpc one and it's sold by SK Store
[Vivo Nex Questions & Answers] Huuhuynh89:
I just made the same mistakes as you and I have solved it.

Sorry . My English is bad. I am faulty like you and I replaced 2 cables in the phone. Is it working. It is two wires connecting the charging board to the main circuit. I think you are like that. You try to find 2 strings that and replace.
[Networking] dreckis604:
Hi there... i need disable EDGE from connecting on my Rogers HTC touch... i am getting billed for my usage from the weather updates etc.... and i need to disable this so i can only use the wifi. problem is i cant find anything on how to disable this?
[Networking] rajib:
welcome to the forum dreckis604 :)

check this thread..

http://xdaforums.com/showthread.php?t=331817

there are a lot of other similar threads. which will tell you to delete your gprs settings, so your phone does not know how to connect to gprs. there is also a program called nodata.

you'll find a lot more if you do a little searching.
[Fire General] k4y0z:
Features.

Uses 5.3.2 Preloader/TZ for easy access to bootrom (using left volume button/only 5th gen)

Uses 5.6.3 LK for full compatibility with newer kernels.

Hacked fastboot mode lets you use all fastboot commands (flash etc).

Boots custom/unsigned kernel-images (need to be patched)

Sets androidboot.unlocked_kernel=true (enables adb root-shell)

For the devs: sets printk.disable_uart=0 (enables debug-output over UART).

NOTE: Hacked fastboot can be reached via TWRP.

NOTE: Hacked fastboot won't patch your boot/recovery-images, so you can easily go back to stock.

Use TWRP for autopatching.
[Fire General] k4y0z:
Version 1.4 (25.03.2019)

Update TWRP to twrp-9.0 sources

Implement downgrade-protection for LK/PL/TZ

Add scripts to enter fastboot/recovery in case of bootloop

Automatically restore boot-patch when you boot into recovery

Version 1.3 (20.03.2019)

Fix Prime Video for ford (5th gen), thanks [MENTION=7839832]MontysEvilTwin[/MENTION] (See Post #537 for more info).

Version 1.2.1 (17.02.2019)

Fix bug in 7th gen.

16.02.2019

Now also unlock for the 7th gen :)

Version 1.2 (14.02.2019)

Updated TWRP to contain new microloader..

Added TWRP shell command reboot-amonet to reboot into hacked fastboot.

Version 1.1 (14.02.2019):

Fixed bug, caused when flashing large images via hacked fastboot.

Include stock recovery.img and script to flash back.

Source Code:

https://github.com/chaosmaster/amonet

https://github.com/chaosmaster/android_bootable_recovery
[Fire General] Rortiz2:
Nice job.
[Fire General] ANDROID2468:
Anyone who wants to update to the latest FW without undoing the unlock you can get it here

I'm also releasing a customized fire os that I'm calling "fire os revamped" ( comes with nova launcher and other enhancements) it will be on xda soon

edit: here it is.
[Fire General] Pix12:
So I can do this without opening it up if I'm on a newer version?

---------- Post added at 06:44 PM ---------- Previous post was at 06:34 PM ----------

So my 5.1.1 Fire, which I believe was originally on 5.0.1 worked.

---------- Post added at 06:51 PM ---------- Previous post was at 06:44 PM ----------

I mean it worked without having to brick or open it up.
[Fire General] hwmod:
[MENTION=7104332]k4y0z[/MENTION] awesome work ! My congratulations again for the great achievement and implementation.

Your solution is letting users revive their "bricks" and make them free to use their gadget as they wishes.

There is still some quirk I have on the 7th Gen tablets with the "microloader" code, though it works well

with the 5th Gen, so I am assuming that something can be improved on the 7th Gen and maybe in general.

Your work opens up to new ROMS and other possible use of the tablet for things I have been dreaming about

for long time, having Linux load from µSDCard, from SSD on OTG or from the network (BOOTP/DHCP/NFS ... ).

I know this will take some time and effort but now more than ever I feel the target objective is on sight.

The first thing would be rebuild a completely modular kernel, maybe a more recent one (4.x).

In all Linux OS the correct way for a normal user to gain read/write access to the serial ports (UARTs) is to make himself a member of the "dialup" group.

You can do this by issuing once the following command (two alternatives given here, use only one):

sudo adduser MY_USER_NAME dialout

or

usermod -a -G dialout MY_USER_NAME

This avoids using "sudo" and having to type password several times to gain permission to access the serial device,

it also solved many issues I was having due to multiple concurrent access to the Serial Ports and/or USB Ports from

various software and devices (Bluetooth, Camera, Phones, Digital Signing, Crypto Cards, Prolific/FTDI serial converters ... ).

And this is another suggestion for those continuously testing phones and tablets ...

To avoid trashing the tablet connectors due to continuous connect/disconnect of the USB cables I highly recommend

using the following type of USB Multiport Hub with power switches or similar (there are both USB 2.0 and USB 3.0 versions)

they are inexpensive and really unique in its type having an on/off switch for every port effectively help to avoid damaging connectors.

Have a good hacking night. :good:

.:HWMOD:.

---------- Post added at 02:34 AM ---------- Previous post was at 02:17 AM ----------

This is the proof that it was possible to make the hack available to a bigger group of users.

Another big achievement obtained by the awesome [MENTION=7104332]k4y0z[/MENTION] though in my tests this is not

always possible yet, more testing will probably reveal the reason and let's improve on that.

This is especially annoying on the 7th Gen tablets but I keep hoping a simpler way would help there.

Disconnecting the battery does the difference at times and that means just removing two small screws.

.:HWMOD:.
[Fire General] DB126:
Outstanding contribution. Clear, concise and relevant to a broad community with appropriate acknowledgements. This is what XDA is all about.
[Fire General] k4y0z:
What quirks other than the non-functional screen?

Have you tested what I suggested in the other thread?

That would be the "correct" way of course, I just assumed people where using live-systems, so sudo seems like the easier solution.
[Fire General] hwmod:
Yes I tried to use the file "boot.7th.patched.img" you shared and the UART but the tablet doesn't boot up,

it crashes as soon as the "microloader.bin" is executed, the logs says something like "undefined, aborting"

instead of printing the heading "microloader by xyz. Copyright 2019" as it does with the 5th Gen.

It doesn't print the message "Something went horribly wrong!" that the code print if an error is detected.

It seems the error has to do with a wrong load address, after the error the processor registers are dumped.

Two things I noticed the first shouldn't be a problem but all the image wrappers contains a residual

from the mt8163 platform, the parameters "bootopt=64S3,32N2,32N2". It is present also in "microloader.bin".

I understand that probably it doesn't do anything bad on our Fire mt8127 platform but removing these would

also ensure that possible behaviours are also removed and we don't have that "cmdline" parameter hanging

around without a precise scope.

The second thing is that it seems to me the "boot.7th.patched.img" you shared and asked me to try doesn't

come from version 5.6.3 of the firmware and that may be another point which might break the loading

process and the version mismatches I am seeing on the 7th Gen.

So we don''t have a native "preloader" for the 7th Gen that allow booting images as we have for the 5th Gen so

we are forced to use the one we have from 5th Gen but the we have no matching secondary loader and that

might be another reason we are having a hard time replicating the process that run smoothly on the 5th Gen.

However, even on the 7th we have gained "root" by using the "SuperSu" and also the TWRP seems to be working

well and following that path also the touch screen problems do not show up and everything run natively correct.

Now, what's happen when we face the update route is still unknown, however we will soon learn that since this

evening my 5th Gen downloaded as much as 18 components that needed to be updated on 5.6.3.

I captured them all and have saved the 18 pieces, all are "apk" files, no ".zip" and no ".bin" files.

I am going to download the update version you released today and the patched TWRP and

tomorrow I will restart testing everything again and will let you know if something changes and if there are

further improvements for the 7th Gen.

One request I have is: where can I put more kernel "cmdline" parameters as you did with "printk_disable_uart=0" ?

That's all for now, thank you again for the nice surprises !

.:HWMOD:.
[Fire General] k4y0z:
Ok that shouldn't happen, it should at least get further than that.

You are testing it with the 5th gen preloader/lk correct?

Maybe I messed something up creating the image.

I have attached a new one from the 7th 5.6.3 firmware.

Please use the new version 1.1 of the package I just updated a few minutes ago.

(It uses different addressing).

I don't think that will cause any issues, the kernel should at least load and print something to UART.

It's not even loading the microloader correctly. (which should work, since it works for TWRP)

I will have to think about that, the flags would need to be stored somewhere.

Sadly the 5.6.3 bootloader doesn't suppoert "oem append-cmdline" anymore.
[Fire General] hwmod:
What about "fastboot --cmdline" that is in the help of newer version ?

I have never been able to use that. Can that be made to work in some way ?
[Fire General] k4y0z:
I haven't tried, my fastboot doesn't support this option.

If the 5.6.3 LK supports it, it should work in hacked fastboot mode.
[Fire General] hwmod:
Here it is !

Taken from Fedora 29 should work on any recent Linux.

See the line I have made in bold in the included help output here.

Seems to indicate that "fastboot" will pass the "cmdline" parameter,

obviously it needs to be implemented in the target platform though.

# fastboot --help
usage: fastboot [OPTION...] COMMAND...

flashing:
update ZIP Flash all partitions from an update.zip package.
flashall Flash all partitions from $ANDROID_PRODUCT_OUT.
On A/B devices, flashed slot is set as active.
Secondary images may be flashed to inactive slot.
flash PARTITION [FILENAME] Flash given partition, using the image from
$ANDROID_PRODUCT_OUT if no filename is given.

basics:
devices [-l] List devices in bootloader (-l: with device paths).
getvar NAME Display given bootloader variable.
reboot [bootloader] Reboot device.

locking/unlocking:
flashing lock|unlock Lock/unlock partitions for flashing
flashing lock_critical|unlock_critical
Lock/unlock 'critical' bootloader partitions.
flashing get_unlock_ability
Check whether unlocking is allowed (1) or not(0).

advanced:
erase PARTITION Erase a flash partition.
format[:FS_TYPE[:SIZE]] PARTITION
Format a flash partition.
set_active SLOT Set the active slot.
oem [COMMAND...] Execute OEM-specific command.

boot image:
boot KERNEL [RAMDISK [SECOND]]
Download and boot kernel from RAM.
flash:raw PARTITION KERNEL [RAMDISK [SECOND]]
Create boot image and flash it.
[B] --cmdline CMDLINE Override kernel command line.[/B]
--base ADDRESS Set kernel base address (default: 0x10000000).
--kernel-offset Set kernel offset (default: 0x00008000).
--ramdisk-offset Set ramdisk offset (default: 0x01000000).
--tags-offset Set tags offset (default: 0x00000100).
--page-size BYTES Set flash page size (default: 2048).
--header-version VERSION Set boot image header version.
--os-version MAJOR[.MINOR[.PATCH]]
Set boot image OS version (default: 0.0.0).
--os-patch-level YYYY-MM-DD
Set boot image OS security patch level.

Android Things:
stage IN_FILE Sends given file to stage for the next command.
get_staged OUT_FILE Writes data staged by the last command to a file.

options:
-w Wipe userdata.
-s SERIAL Specify a USB device.
-s tcp|udp:HOST[:PORT] Specify a network device.
-S SIZE[K|M|G] Break into sparse files no larger than SIZE.
--slot SLOT Use SLOT; 'all' for both slots, 'other' for
non-current slot (default: current active slot).
--set-active[=SLOT] Sets the active slot before rebooting.
--skip-secondary Don't flash secondary slots in flashall/update.
--skip-reboot Don't reboot device after flashing.
--disable-verity Sets disable-verity when flashing vbmeta.
--disable-verification Sets disable-verification when flashing vbmeta.
--wipe-and-use-fbe Enable file-based encryption, wiping userdata.
--unbuffered Don't buffer input or output.
--verbose, -v Verbose output.
--version Display version.
--help, -h Show this message.

.:HWMOD:.
[Fire General] k4y0z:
Just noticed in mine there is

I don't think it's supported by LK.

I suppose you could just rebuild a kernel-image with the appropriate cmdline.
[Fire General] hwmod:
Yes that was another form of of passing the same arguments in a previous version of "fastboot".

I am keeping a collection of "fastboot" version and by looking to the "lk" binaries I see there are

still a lot of referrals string related to "cmdline" handling.

If there is a way to still pass some parameter it might be feasible to inject some on the "cmdline".

Another thing I have been exploring is the MISC partition which contains the ENV variable of "lk".

There is a parameter written in the "lk" environment which reside in that MISC partition which is

"off-mode-charge=1", that parameter is followed by a simple CRC sum of the bytes of the string.

I thought that maybe by writing more parameters in MISC it would result to a parameter injection

but I didn't have the success I hoped, maybe I didn't test well enough or failed something, anyway

that MISC partition is almost empty and maybe it can be used too as extra persistent memory should

we need to save something bigger than a couple of kilobytes.

Have fun !

.:HWMOD:.
[Fire General] kozyy:
Wasn't exactly clear on this, so on the 7th gen we can sideload the 5.0.1 firmware (bricking the device) then we're able to enter boot-rom and are able to continue with the rest of the the steps?
[Fire General] mateo121212:
with the new files k4y0z posted i am working on streamlining the process to make a simpler method for the 7th gen. also the SU 2.82 sr5 edits the .sh file that rebuilds the recovery. thats why some people lose there recovery even if they flash both system and boot from same FW.

.
[MTCD  Android Head Units Q&A] kmlnvm:
When I tell google assistant to increase/decrease brightness (or volume) it says ok, but nothing changes.

Does anybody have the same issue?

Is there any chance to solve this?
[MTCD  Android Head Units Q&A] bobodaclownster:
I use the program dimly to adjust the screen brightness.
[MTCD  Android Head Units Q&A] kmlnvm:
does it have integration with google assistant?
[General Questions and Answers] Reckless459:
So I just got the Aristo 3 and wanted to root it. after an extensive search I have come up empty. Does anyone know if there is a method available to use yet or maybe something is in the works? I've unlocked flashing but I cant seem to boot recovery. Any help would be greatly appreciated.
[General Questions and Answers] Nvitethedark:
Same ive spent about 6 hours researching this ive never built my own root before however i just dont have the time to do whats needed. From what i researched get the original boot rom from lg bridge and perform a restore to download the factory boot image then use magisk to rebuild the image
[General Questions and Answers] Reckless459:
Hmm I'll give it a try. The phone is still new enough that I don't have much saved to it and if I brick it can take it back
[General Questions and Answers] Nvitethedark:
should be able to just get the boot image may be the aristo 2 dev would pick this up since he's familiar with it I see you have a few posts in that forum maybe you can send that dev a message see if they would pick it up.
[General Questions and Answers] theprotechman:
I eagerly await any progress in this run! My girlfriend cracked her screen on her Aristo 2 and decided that it was time to upgrade. I've never been disappointed in the idea of upgrading my phone...until it meant giving up my Aristoboy Mk.2(which was/is quite formidable)and rooted status along with it. If there is anything I might read about the process online, I would at very least consider the task myself. I am learning, but I have some decent skills and experience behind me. Please let me know if I can assist in any way. If not, I hope to see the first strides towards tackling this latest addition to the Aristo line!

My thanks to all my fellow devs here! You each make up a piece of the whole collection that make this, hands down the best forum/online community available the world over! Keep it up! We are making a difference in so many lives!

Your friend,

~[ProTech]~
[General Questions and Answers] Reckless459:
So I've been busy as **** lately, but I found that the issue seems to be with the os more than the phone itself. I'm not that proficient with downgrading the os to a earlier version since this phone came stock with Oreo. I will try and talk to some of the devs who did the aristo 2 x210ma. Hopefully they have a solution. I've been using my 2 instead. I never realized how much you can't do with a stock phone and os.