[ROM] Vivo NEX Global ROM 1.7.18 (service split)

[nirvanahh]

Yes, same error here. and ddr and frp say "this partition has no corresponding file".

download the last one file i uploaded , you can use Google translation， that guide may be useful.

---------- Post added at 05:12 PM ---------- Previous post was at 05:07 PM ----------

We should find a way to enter 9008 mode. AFT is an official BBK service tool, it can also flash from 9008. There is a drop menu, look at the end of my video. Try to select 9008 instead of other phones in that menu, maybe AFT itself can reboot the phone into edl mode...

There may be hardware lock to enter EDL. If so - its really bad, need to remove back cover and short some points on the PCB to reflash.
https://www.stupdroid.com/2018/07/edl-flashing-y71.html

i had upload 9008 driver and a hacked aft, also some guidances to initial 9008 driver.

 

[paatha13]

It is a new device. I have mentioned these problems with an employee of the official vivo service center, it saw, that he can only upgrade or recover a phone with the same version of software, using AF Tools.

If there is damaged boot in the phone or otherwise it cant be recovered using AFT, warranty politics of vivo prescribed to change system board for free, with the old board have to be returned to vivo. He dont know, how to enter 9008 mode on nex.



Nobody can say, what to do to 100% recover your bricked phone, you may do flash on your own risk. This is a new device, all of these are now on warranty.

Exactly as you described with details,right now the risk is very high and since there’s no warranty that even with Vivo own recovery tool as AF tool will be able to recover in case of brick due to attempt flashing other version than those Chinese version came out of box, better all of us don’t make any attempt to that.

If I was living in China or India that Vivo has service center both country and since replacing motherboard is free of charge I could take the risk but right now anyone living other country not deserved the risk.

Nevertheless if anyone finds a way it’s always welcome shares its experience and steps followed to other users and members of XDA.




Sent from my iPad using Tapatalk Pro

 

[BlackPanther_]

download the last one file i uploaded , you can use Google translation， that guide may be useful.

---------- Post added at 05:12 PM ---------- Previous post was at 05:07 PM ----------



i had upload 9008 driver and a hacked aft, also some guidances to initial 9008 driver.

To use 9008 driver we need to put the phone into EDL.

 

[STEVE_MARS]

It is a new device. I have mentioned these problems with an employee of the official vivo service center, it saw, that he can only upgrade or recover a phone with the same version of software, using AF Tools.
If there is damaged boot in the phone or otherwise it cant be recovered using AFT, warranty politics of vivo prescribed to change system board for free, with the old board have to be returned to vivo. He dont know, how to enter 9008 mode on nex.

Nobody can say, what to do to 100% recover your bricked phone, you may do flash on your own risk. This is a new device, all of these are now on warranty.

I think that BBK has locked all possibilities: Unlock bootloader, enter EDL mode, change id model... and dont release source code.

 

[BlackPanther_]

Not all, but can do some **** to us if used hardware EDL lock. The phone will go to EDL automatically, if it can not boot from emmc.

 

[paatha13]

I think that BBK has locked all possibilities: Unlock bootloader, enter EDL mode, change id model... and dont release source code.

When purchased Vivo Nex I knew that will never release source kernel judging from negative track history all that years,BUT I never thought that would make it impossible even flashing official stock rom on their device!!!

It’s by far the worst experience within Android OS manufactures.

I couldn’t imagine those top level restrictions policy.

With Vivo Nex release since was a major FIFA 18 sponsored it with millions users and customers knowing Vivo across the globe it would have been a good start to be more user and developer friendly but seems that not the case unfortunately.

As much I love Vivo Nex and appreciate the very high level of performance with majority of aspects and unique design,but probably will be my first and the last one purchasing Vivo smartphone.

With such stupid restricted policy much worse even compared to Apple the only thing they’ve been successfully doing is to make users and customers not want to deal with Vivo anywhere anytime.




Sent from my iPad using Tapatalk Pro

 

[STEVE_MARS]

When purchased Vivo Nex I knew that will never release source kernel judging from negative track history all that years,BUT I never thought that would make it impossible even flashing official stock rom on their device!!!

It’s by far the worst experience within Android OS manufactures.

I couldn’t imagine those top level restrictions policy.

With Vivo Nex release since was a major FIFA 18 sponsored it with millions users and customers knowing Vivo across the globe it would have been a good start to be more user and developer friendly but seems that not the case unfortunately.

As much I love Vivo Nex and appreciate the very high level of performance with majority of aspects and unique design,but probably will be my first and the last one purchasing Vivo smartphone.

With such stupid restricted policy much worse even compared to Apple the only thing they’ve been successfully doing is to make users and customers not want to deal with Vivo anywhere anytime.




Sent from my iPad using Tapatalk Pro

I totally agree with you... but it so pretty

 

[BlackPanther_]

Dont worry, we on the right way, we need time to break this security.
Flashing only system and data images cannot brick the phone, if it will not boot after this, recovery and bootloader will work and you always can load official firmware back.

 

[FUKU_]

When purchased Vivo Nex I knew that will never release source kernel judging from negative track history all that years,BUT I never thought that would make it impossible even flashing official stock rom on their device!!!

It’s by far the worst experience within Android OS manufactures.

I couldn’t imagine those top level restrictions policy.

With Vivo Nex release since was a major FIFA 18 sponsored it with millions users and customers knowing Vivo across the globe it would have been a good start to be more user and developer friendly but seems that not the case unfortunately.

As much I love Vivo Nex and appreciate the very high level of performance with majority of aspects and unique design,but probably will be my first and the last one purchasing Vivo smartphone.

With such stupid restricted policy much worse even compared to Apple the only thing they’ve been successfully doing is to make users and customers not want to deal with Vivo anywhere anytime.




Sent from my iPad using Tapatalk Pro

vivo nex was my 1st vivo phone too. never heard of that company before. took a risk here but i saw the innovation in this phone... im pretty damn disappointed by vivo for their policies... they want to FORCE you to use their software rather than you actually wanting to use it... so sad...

 

[xreactx]

We need to Make Vivo Great Again...

 

[MobilePerson]

Congratulations guys for your efforts !!!!

 

[xreactx]

Congratulations guys for your efforts !!!!

Congratulations for what?

 

[marcus_sk]

I would support you:

not sure if i reached fastboot mode, because it looks different for me than other phones (and the difference is not chinese )

1. phone is in normal booted mode, pluged in via edl cable (null cable), oem unlock in dev options enabled
2. powershell: adb reboot bootloader (I thought this would be wrong, but this was the first command in a youtube video for unlocking vivo phones/same vivo compiled adb/fastboot files as here posted for download)
2. (optional?) powershell: fastboot bbk unlock_vivo --> Failed (remote: unclock fail.) (yes: unclock^^)
but the phone booted after the "reboot bootloader" showing the following: Fastboot (blablabla Chinese), more Chinese, green Button (translated in english: boot system) and black button (translated: recovery).
3. step by step aftool via video tut
a) selecting India as default country (in unzipped firmware folder you are going to find the countries: hk, cn, in, ru etc.)
b) checking if all files are checked and looks valid
c) hitting "Download" Button
Error message:
"This mobile phone brush authorization failure, please try again after recovery mode clean data, or use 9008 upgrade"
Info message:
"Download terminated! To download again, you need to disconnect your phone from your computer....."

Ok, some questions:
I. what is meant with "please try again after recovery mode clean data"?
II. is the firmware provided in 1st post usable for 9008 upgrade method?
III. Are you aware of some malware detection because of aftool auth-exe? maybe false positive...

some infos about my environment:
using win10 64bit via virtualbox with usb3 extension package.
the passthrough of usb (phone and fastboot) needs some work:
after I installed the adb-driver, vivo-driver and qfil-driver the phone is recognized in the virtual machine, in virtualbox you should do a fix mapping of the "nex" for the vm/guest. after the phone reached the "fastboot mode" (I am not sure about the right fastboot mode) the device would not be recognized anymore in the vm/guest. you should use a usb-debug tool like "USB View" to investigate the vendor and product IDs (hex-codes) of the "android adb interface" when the phone is in "fastboot". with these info you could bind the usb-device to the vm. voila the phone automatically jumps into the vm/guest.
Only in case that you are concerned about the malware detection, too.

 

[xreactx]

I am trying to use QFIL on Windows 10 through a virtual machine on my mac; however, I am unable to get my vivo device to be recognized through the program. When I was looking through the QFIL configuration settings I noticed the storage options with eMMC is by default. Has anyone tried changing it to UFS since newer flagship devices have UFS storage?

 

[BlackPanther_]

This mobile phone brush authorization failure, please try again after recovery mode clean data, or use 9008 upgrade

The tool says, that you try to load in the phone an incorrect rom. You try to load PD1805_EX_A rom in an PD1805_A device. And says, that you can try to flash in 9008(EDL) mode. Yes, in this mode you can load emmc with any images, that fit in the corresponding partition. But we dont know, how to enter this mode and there is possibility of vivo s_h_i_t here - hardware EDL Lock. I.e. open the phone and short special points on PCB. This method vivo was already previously used in some their phones. All, that we can try for now - select different buttons on the phone, while connecting it to the AFT. Some old vivo models enters EDL with v-, some with v+ , some with v+ and v- simultaneously.

 

[paatha13]

I would support you:

Ok, some questions:
I. what is meant with "please try again after recovery mode clean data"?
II. is the firmware provided in 1st post usable for 9008 upgrade method?
III. Are you aware of some malware detection because of aftool auth-exe? maybe false positive...

some infos about my environment:
using win10 64bit via virtualbox with usb3 extension package.
the passthrough of usb (phone and fastboot) needs some work:
after I installed the adb-driver, vivo-driver and qfil-driver the phone is recognized in the virtual machine, in virtualbox you should do a fix mapping of the "nex" for the vm/guest. after the phone reached the "fastboot mode" (I am not sure about the right fastboot mode) the device would not be recognized anymore in the vm/guest. you should use a usb-debug tool like "USB View" to investigate the vendor and product IDs (hex-codes) of the "android adb interface" when the phone is in "fastboot". with these info you could bind the usb-device to the vm. voila the phone automatically jumps into the vm/guest.
Only in case that you are concerned about the malware detection, too.

You should disable Windows Defender the same too also must do before using QFIL or AF Tool.

I am trying to use QFIL on Windows 10 through a virtual machine on my mac; however, I am unable to get my vivo device to be recognized through the program. When I was looking through the QFIL configuration settings I noticed the storage options with eMMC is by default. Has anyone tried changing it to UFS since newer flagship devices have UFS storage?

I've already tried this but not helpfull.

 

[BlackPanther_]

Have win 10 with embedded defender in it, no positive reaction to AFT. My video was recorded with windows defender active.

Has anyone tried changing it to UFS since newer flagship devices have UFS storage?

You can try change anything in QFIL, but it will not work without established connection to the phone via USB EDL com-port.
These service tools are very special and in most cases will not work properly on virtual machines.

 

[stealthj]

I will try this when I get back to the US.

 

[OreoLivesOn]

About this ROM

I dont get it, what is different with this rom than my current rom?

 

[STEVE_MARS]

I dont get it, what is different with this rom than my current rom?

We are trying install Global ROM into chinese phones.