yashsingh1/xdaforums huggingface dataset:
[Miscellaneous Android Development] nobreak1970:
Ok I will try this one. The one on the hovatek forums has a bit coin farming trojan in it.

I got the GUI version of it from there, apparently virus free, and tried it. the recovery image it output did not boot with fastboot boot recovery.img. Just a black screen and then a reboot.

I'm stumped.
[Miscellaneous Android Development] nobreak1970:
Update: techguy777 that one that you offered is the same version I already have.
[Miscellaneous Android Development] psychofad:
I''m sorry about that, was already thinking it!:p Small issue, my post count isn't high enough to start one it seems :crying:
[Miscellaneous Android Development] gemah:
I just realized that booting in factory mode gives you the option to clear eMMC. That's interesting, but highly risky as well. If we cleared eMMC, could we force writing things to storage perhaps?

That's a loose assumption, but still something worth taking note of (I think).
[Miscellaneous Android Development] nobreak1970:
No worries. I wish they weren't so different as it would save us all some time. :)
[Miscellaneous Android Development] Techguy777:
Putting this out there if anyone gets the phone and downloads the update please try to save the update zip to your PC or cloud or anything. If you can extract it and get the boot.img and recovery img that would be great thanks in advance.
[Miscellaneous Android Development] gemah:
Here I'm, poking things at random again. I just came accross this MTKLogger Exploit that supposedly allows rooting. Guess which phone comes with MTKLogger? That's right ;^). I wonder if we could make good use of this exlpoit to root and effectively hack the Vivo XI.
[Miscellaneous Android Development] MicroMod777:
Where would the update.zip download to, to pull?
[Miscellaneous Android Development] psychofad:
Not sure, but it may be as out of reach as the boot image. I tweeted BLUProducts and asked for a copy of stock firmware and source, may start emailing them. I believe if they used any of Google's open source code, they are technically supposed to release it upon request. I need to verify that info, but worth a shot.
[Miscellaneous Android Development] MicroMod777:
I might just put my phone in fastboot mode, and take it back to Bestbuy this Saturday and get it exchanged for another one, plus add the Geeksquad insurance. What you guys think??
[Miscellaneous Android Development] Techguy777:
Well first off it would only be there if you don't install it first. I'm not 100 percent sure for Blu you need to get es file explorer or solid explorer and look around. I would try es file explorer than click on the left Sd card analyst it will put the files in order largest to smallest and that should be up there. The specific location depends on device. I don't even know if you'll be able to get it off but you should.

---------- Post added at 01:37 AM ---------- Previous post was at 01:35 AM ----------

Also if you go into settings apps and clear data for Google services framework it might show up to download again is what a online guide said. It couldn't hurt to try.
[Miscellaneous Android Development] MicroMod777:
Moved...
[Miscellaneous Android Development] nobreak1970:
THIS thread is for the 3gb/32gb VIVO XI

Thanks.
[Miscellaneous Android Development] nobreak1970:
This keeps getting confused with the VIVO XI+ I'll have a mod close it and do private research. Thanks.
[Miscellaneous Android Development] Techguy777:
Dude I understand what you are saying but it's better to have more heads and it isn't like anyone else has your model so if the 6771 version finds root you'll be able to to it'll probably be the same way. Point is you'll have no better chance by shutting it down.

---------- Post added at 11:11 AM ---------- Previous post was at 11:08 AM ----------

Nice that's what I would do if I had the phone receipt.

---------- Post added at 11:14 AM ---------- Previous post was at 11:11 AM ----------

How do you open a thread I've never done it? Is there any restrictions like some many thanked post or anything?

---------- Post added at 11:56 AM ---------- Previous post was at 11:14 AM ----------

It seems to me that the update might be the same update for each chip. If the change log and update file size are the same on the 6267 and 6771 than it's probably the same firmware so it's like that the boot and recovery are the same. It's also a dangerous assumption. I do believe one of the people on this thread has pulled the update firmware and is working on rooting. We'll have to wait to see.
[Miscellaneous Android Development] Techguy777:
Ok here is the update zip seriously not Dave got the ota link and I downloaded it and uploaded it to my Google drive he had 6771 chip. It has the scatter file and preloader also the boot is a patch so I don't know if that'll work or not but here it is.

https://drive.google.com/file/d/1v9DspVLki7gEzIfq6PxOunC1l_a5t1bB/view?usp=drivesdk

---------- Post added at 07:40 PM ---------- Previous post was at 07:38 PM ----------

Link to the ota download also of drove doesn't work.

https://android.googleapis.com/pack.../9b39890a1202ae46c13d30d6f32ccd12969c1994.zip

---------- Post added at 07:41 PM ---------- Previous post was at 07:40 PM ----------

Big thanks to seriouslynotdavid.
[Miscellaneous Android Development] MicroMod777:
Sweet. So now somebody has to make TWRP out of the boot.img so we can fastboot into it?
[Miscellaneous Android Development] Techguy777:
No boot img is kernel that's for root and recovery is twrp. Unfortunately this zip file is very different to what I'm used to seeing I don't see a recovery so it's not a complete firmware there is a boot patch but I don't think you can use magisk and just flash that but maybe. Really what some needs to do is to learn how to unpack these system images and stuff I believe you'd rename boot.img.p to boot.img and then unpack it or extract it. I don't know I'm lost now because I don't know if this will restore your device if you boot loop either. I'm going to look into at the very least we have the scatter file and preloader.bin which we needed. Now if the magisk manager would just patch the boot and root the device we would be set and it might. If you use the 6771 phone install magisk manager on that phone then rename boot.img.p to just boot.img and then patch it in the manager. You have to use magisk manager on the device your going to root I believe magisk looks at your architecture and your boot Dev block and sets it up. Like mmcblk0pboot partition.

I just ordered my first pic last night it'll be here Friday ill try to unpack them and figure out what the boot I'm going should have and what it needs. If you guys already know how to extract or un pack IMG flies tear it up.
[Miscellaneous Android Development] mrmazak:
Just jumping in here. I have Vivo XL4 coming in few days. It also comes with Android 8.1 and has [MT6762-Helio P22] chip.

Hope we can all work together and get these things on to twrp and root.

As I understand it, all devices that are released with android 8 and above are supposed to be "project treble" compliant.

Which means no boot.img, should have separate "kernel.img" and "ramdisk.img". Then also a "recovery_ramdisk.img"

I had the Vivo X in March, and had to send it back because could not get it rooted,. I was able to spflash read back the phone, but not able to flash any custom images, because of authentication. It did allow me to flash back the read back images, and also the Gionee-SW17W08A_2201 stock firmware (sim did not work though)

Hope this time we all have better outcome.
[Miscellaneous Android Development] nobreak1970:
Yeah I've pretty much given up on this phone until (IF) the pie update drops. I'll try to get it before it installs.

I love the phone for the price for sure. But getting the images is near impossible at this point in time. Wwr tool doesn't work and I don't trust it. Hovtek downloads have bitcoin farming trojans in them anyway. I found one.

Peace guys.

I'll follow this thread in the meantime just in case there's a breakthrough! :)
[Miscellaneous Android Development] nobreak1970:
We are very close here I think. Big hurdle: get the stock recovery off the device(s).

I was able to download a twrp image that was created for another MTK device with same processor set.

I was able to fastboot boot recovery.img it via command line. No errors. It wouldn't boot into it, just a blank screen, because obviously the TWRP image I booted into was for a different device. So, I know we can flash a custom recovery (after you unlock your BL). Just stuck here lol.
[Miscellaneous Android Development] mrmazak:
Try to use this auth file.

It is the one i needed to pull images from the VIVO - X

The X has / had MT6757-Helio P25

not the same, but hopefully close enough

EDIT

DID NOT work
[Miscellaneous Android Development] SeriouslyNotDavid:
See, now that is what I am talking about. Good stuff man. Just remember the new cheap chinese phones are Treble and Android One compliant, especially if they want MTK, Qualcomm, and Google Support so adb commands will definitely work. It is just a matter of flashing the right recovery and patching boot.img. Now, the only question left is whether or not MTK Secure Boot chipsets will allow the changes to be kept. Perhaps a forced rewrite in the event of an unauthorized recovery it will flash an additional recovery_xxx.. I'm not too big on the dev side of things but I am a power user and it isn't unheard of. Keep at it bro, you are definitely on the right track. Even so, during the pie update, just logcat the update prior to downloading it or cancel the update and turn off Wifi/Mobile Data, then run logcat, turn on wifi/mobile data then wait for update to start downloading and find zip file. That is how I got the OTA link. The future is bright and I don't think it will be long before root is yours. I think take it easy on the flashing until there is something concrete on the an android forum or telegram group regarding the chipset. And once you get the Pie firmware, release it to the public so that devs can start understanding the mediatek chipset.
[Miscellaneous Android Development] mrmazak:
The Xiaomi Redmi 6 Has same chipset, and an Official twrp. And a dedicated page at XDA.

https://xdaforums.com/redmi-6

I assume this may be #1 choice to use for porting twrp.

On that thread I have found the auth file and DA agent supposedly for that device. Because they have same chipset does not mean for sure the same file will work for your devcie. It is based on the pre-loader file that has "signed" the da and auth file. But here is the files, you can try. Unzipp and select these files with spflash tool to test.

EDIT

DID NOT WORK

.
[Miscellaneous Android Development] mrmazak:
I contacted BLU this morning and asked for kernel Sources to the Vivo XL4 and they just published them . SO that is fastest time I have seen so far. 5-6 hours and here are kernel source.

I will ask for Vivo Xi also if anyone will be building it.
[Miscellaneous Android Development] mrmazak:
[MENTION=2930839]nobreak1970[/MENTION] What is your build description

adb shell getprop ro.build.description

I am searching in this kernel sorce for your defconfig, to see if is possible built from same source.
[Miscellaneous Android Development] nobreak1970:
full_k62v1_64_bsp-user 8.1.0 O11019 1542211516 release-keys
[Miscellaneous Android Development] mrmazak:
Thank you. This tells me 64-bit build. So the twrp you need to use also needs to be from 64-bit device.

Unfortunately the redme 6 that has official twrp is a 32-bit unit

k62v1_64_bsp this defconfig is in the source i have but gave a build error. Now I know it should be correct, i will move forward and try debug the source

How about one more hint . What do you get from

adb shell cat /proc/version
[Miscellaneous Android Development] nobreak1970:
Linux version 4.9.77 (android@buildsrv02) (gcc version 6.3.1 20170109 (Linaro GCC 6.3-2017.02) ) #1 SMP PREEMPT Thu Nov 15 00:25:07 CST 2018
[Miscellaneous Android Development] mrmazak:
Oh, you have an update too.

I received mine today, and have same kernel number.

And same "need auth file" to connect to spflash.

Hopes are still high that once I sort out the bugs in there released source and get kernel to build. I should be able to swap that kernel into generic twrp , and well you know
[Miscellaneous Android Development] nobreak1970:
Awesome!
[Miscellaneous Android Development] nobreak1970:
I see that our kernel source is out?

Now what? and THANK YOU!

:)
[Miscellaneous Android Development] mrmazak:
I have compiled the stock kernel from those sources, and used the twrp porting tool found on Hovatech forum. I used the stock recovery from last years model (vivo X). Then unpacked that poted twrp, and swapped in the built kernel. It jut needs to be tested with "fastboot boot new-test-twrp.img" to see if it loads.

If it loads then you can use the adb shell from that twrp to copy your stock boot.img and stock recovery.img.

and make correct twrp from that.

because this is test version, I do not want to put it out without good warning that it is only a test build and not to flash it to device, and definitely DO NOT use it to try to install anything onto phone.

With that warning , here goes, this needs a tester. ( I cannot test, as I have said before I have "VIVO XL4" not "Xi")

on my xl4 it just went to black screen then full reboot.

EDIT

Got report already, this did NOT boot..

.
[Miscellaneous Android Development] YTG20:
Blu vivo xi

I am on this train what's the step to unlock the

Bootloader

---------- Post added at 02:16 AM ---------- Previous post was at 02:10 AM ----------

Need a tutorial pls
[Miscellaneous Android Development] psychofad:
Just a side note, I noticed we have the recovery-from-boot.p file on our phones, so from what I have read this will prevent permanent flashing of recovery until the file is renamed or removed. Not sure how this would affect fastboot boot recover.img if at all but thought I would share what I found from casual filesystem browsing using X-plore app (lets you have some access to root folders without root but limited)
[Miscellaneous Android Development] nobreak1970:
Just FYI...the XI non plus version has face unlock. It's buried in smart Lock settings. I found the facelock.apk when browsing around using adb. I was like...hmmmm.
[Miscellaneous Android Development] psychofad:
Nice! Do you see the little Red IR light next to the camera when you unlock with your face? It's becoming more clear, these phones share an OS and most of the same hardware besides the processor, which they both have AI, ram and storage which is a common way to save a few bucks, and perhaps the fact that the Plus has wireless charge and nonplus has a lower res screen (0.3 inches smaller), seems like the kernel is the same as well, so if we get root on one the other is surely rooted as well.

Your Kernel: Linux version 4.9.77 (android@buildsrv02) (gcc version 6.3.1 20170109 (Linaro GCC 6.3-2017.02) ) #1 SMP PREEMPT Thu Nov 15 00:25:07 CST 2018

Mine on Plus: Linux version 4.4.95 (android@buildrpc05) (gcc version 6.3.1 20170109 (Linaro GCC 6.3-2017.02) ) #1 SMP PREEMPT Sat Oct 27 20:13:10 CST 2018

Linux version is higher on yours, but your update was 19 days after mine so its possible that Linux had updated in that span, the rest looks identical. Curious if the Features tab in settings exists in the non plus version of the phone and if it mentioned the face unlock there, seems like a lost opportunity for Blu not to market the lower cost phone that has Face Unlock :rolleyes::confused: ..
[Miscellaneous Android Development] Techguy777:
Adb reboot bootloader

Fastboot oem unlock

Volume up to confirm.
[Miscellaneous Android Development] psychofad:
Before you do that, enable developer options and enable oem unlock if you have not already
[Miscellaneous Android Development] mrmazak:
I ended with root from magisk patched boot.img.

Other member shared DA file, and Auth file that worked to connect with spflash tool. TWRP still not working but it has root. And can flash the backed up images with flash tool.

Here is the scatter I used and auth files needed to get started with wwr tool to pull your images.

https://www.androidfilehost.com/?w=files&flid=287088

[MENTION=2930839]nobreak1970[/MENTION]
[Miscellaneous Android Development] nobreak1970:
so same DA file and other stuff as the XL4?
[Miscellaneous Android Development] nobreak1970:
Ill need a step by step for what you're talking about. :)
[Miscellaneous Android Development] mrmazak:
SPFlash tool version 5.1812 or newer

The Auth file and DA file from the flash tool in this post are what is needed. To make things easier You could use the flash tool in the link in this post

https://xdaforums.com/showpost.php?p=78476653&postcount=50

But the link will probably be down soon. It is a pay per click link and XDA does not allow them. (I will have the same file in my android file host folder)

That is all that is different from other devices, following the guide on wwr_mtk tool. The picture guide on Hovatak leaves nothing to be confused over., It is best to follow that guide after you have the correct SPFlash tool with custom DA file and Auth file.

The full flash tool in my folder or the post linked above have the auth file loaded.Or you can just download the auth file seperate and use in different version tool, as long as it is not an older version, as the MT6762(MT6765 series) will report as unsupported on older flash tools.
[Miscellaneous Android Development] psychofad:
Not sure if the preloader bin from the BLU VIVO XL4 will work with you phone, if you have issues, just grab the preloader.img from the update.zip from before and process it in the WwR MTK tool to get a preloader.bin that is for your phone, thats what I did and after some small technical difficulties of my own making I was also able to back up the plus. Still gotta break it into partitions and find a place to upload it to share with others, then I will see if the Blu Vivo XI+ is nicer to twrp :fingers-crossed::fingers-crossed::fingers-crossed:
[Miscellaneous Android Development] mrmazak:
I would think that this should be obvious, but test you can use sp flash to flash stock files onto phone, before attempting twrp.
[Miscellaneous Android Development] nobreak1970:
Yeah can't get the tool(s) to detect my device.

Good luck all. Think Ill just wait.
[Miscellaneous Android Development] mrmazak:
do not think the recovery-from-boot.p is the reason for "fastboot boot" not working with TWRP. Because it also does not work with boot.img either.

But i just did this. I renamed that file to end with the traditional *.bak. and tried to fastboot boot the twrp , and it still just does a loop back to full reboot.

This phone being treble ready , it should be good to go with this aosp pie gsi

I may try it this week.
[Miscellaneous Android Development] mrmazak:
TWRP is , for the basic part, working.

encryption and mount points need to be tweaked.

[MENTION=8317880]Voinea12[/MENTION] shared on telegram group, Made for Vivio Xi, So I repacked the image with my stock XL4 kernel and it worked.

To keep the downloads simple I have just added the files shared into my file host folder.

twrp1

twrp2

TWRP-VIVO-XL4-V1.img the one I put XL4 kernel into

https://www.androidfilehost.com/?w=files&flid=287088
[Miscellaneous Android Development] nobreak1970:
ok so twrp1 and twrp2 are ready for testing with fastboot boot command for the vivo xi???

UPDATE: tried all 3 with that command and none succeeded. :(

the command worked fine, no errors, but just got the black screen then reboot.
[Miscellaneous Android Development] mrmazak:
The "boot" command has not worked for me either. But I have spflash backup of my stock, so I just flashed with "fastboot flash recovery"

Do not know why fastboot boot fails though
[Miscellaneous Android Development] hanuma:
TWRP Recovery 3.2.3 for vivo XL4

Download

TWRP Recovery 3.2.3 for vivo XI+

Download

Install:

1. Copy to Micro SDCard the file "Magisk-v18.zip"/ "remove_encryption.zip"

2. Flash the "recovery.img"

3. Enter into TWRP and Install the patch "Magisk-v18.zip"

4. Install "remove_encryption"

5. "Format Data"

6. Reboot to the System
[Miscellaneous Android Development] mrmazak:
Thank you, do you know where it came from?

Or what works, and not work
[Miscellaneous Android Development] nobreak1970:
Hmm. Outta nowhere. I can't test it because I don't have the stock recovery on my vivo xi.

I wonder if vivo xi and xl4 have same recovery.
[Miscellaneous Android Development] mrmazak:
I have been sharing with hovatek each success also , maybe it is same file.

[MENTION=5365188]psychofad[/MENTION] has them pulled, just waiting for somewhere to load them.

If he can put the stock boot.img and stock recovery.img here I will add to my android file host (the whole rom if he cares to. You can put on gdrive and I can copy if he wants)
[Miscellaneous Android Development] hanuma:
I ported it
[Miscellaneous Android Development] nobreak1970:
For the vivo xi? Not plus version.
[Miscellaneous Android Development] mrmazak:
Yes I opened it , then I recognized the user name. I beleive you are involved in many things.

Thank you.

Does encryption work on this one?
[Miscellaneous Android Development] hanuma:
Install:

1. Copy to Micro SDCard the file "Magisk-v18.zip"/ "remove_encryption_65.zip"

2. Flash the "recovery.img"

3. Enter into TWRP and Install the patch "Magisk-v18"

4. Install "remove_encryption_65"

5. Format Data

6. Reboot to the System

Download Files
[Miscellaneous Android Development] mrmazak:
thanks.

I was suggesting doing the disable encryption with a shell command. That way it is more versitile to different devices.

from inside twrp

do these two lines

adb shell mount -o rw,remount /vendor
adb shell sed -i.bak 's/forceencrypt/encryptable/g' /vendor/etc/fstab.*

or Have it done as a batch(or sh) script too.
[Miscellaneous Android Development] nobreak1970:
well this is great for the XL4 for sure!

But doesn't flash to vivo xi.

I got this error just testing it with the fastboot boot command:

Downloading 'boot.img' OKAY [ 1.502s]

booting FAILED (remote: 'invalid ramdisk address: overlap with lk')
[Miscellaneous Android Development] nobreak1970:
I ran that file thru the Hovatek Twrp Porter....and it fastboot boot'ed OK this time. but doesn't boot into is. Still just back to OS
[Miscellaneous Android Development] hanuma:
Is your vivo XL device?
[Miscellaneous Android Development] nobreak1970:
Nope. But I created this thread for my device: vivo xi.

So, how can what you have done for the XL4 be adopted for my device?
[Miscellaneous Android Development] hanuma:
I need stock recovery.img and boot.img VIVO Xi
[Miscellaneous Android Development] nobreak1970:
Herein lies the problem.

No tool recognizes the device on my laptop. I used to do this all the time for older 65xx devices. Blue Studio series, etc. For some reason wwr and/or spflash tools do not see the device. the only thing I can do on wwr is create a fake scatterfile for it.
[Miscellaneous Android Development] hanuma:
Driver_Auto_Installer_v5.1632.00
[Miscellaneous Android Development] nobreak1970:
thank you trying now
[Miscellaneous Android Development] nobreak1970:
Yeah sorry but I don't have any of the files needed to run this stuff.

No DA file

No scatter file

When trying to create a scatter file, the version of the program doesn't have my chipset.

etc, etc, etc.
[Miscellaneous Android Development] hanuma:
WwR_2.40?
[Miscellaneous Android Development] nobreak1970:
2.30 :(
[Miscellaneous Android Development] nobreak1970:
Much nicer version! 2.40

here is the readout:

Brand: BLU; Model: Vivo XI;

Hardware: MT6765

Platform: mt6765

File system: EXT4

Android version: 8.1.0

Firmware version: 1542211516

Baseband version: MOLY.LR12A.R2.MP.V28.16.P12, 2018/10/19 11:11

Build number: CSW1707BA_2405_T1043

Description: full_k62v1_64_bsp-user 8.1.0 O11019 1542211516 release-keys

Serial number: QWDIAURKKJ6DD6WW

Root: No

Full memory of ROM: 0x747C00000 (29820 MB)

Full memory of the disk 1: 0x76E480000 (30436 MB)

Not sure why phone is advertised with 6762 chipset and it reads 6765!!
[Miscellaneous Android Development] hanuma:
WwR_2.40