Database Info

Jiayu G3 Root

Does any one tested Bin4ry solution on Jiayu G3?
http://forum.xda-developers.com/showthread.php?t=1886460

luznykolo said:
Does any one tested Bin4ry solution on Jiayu G3?
http://forum.xda-developers.com/showthread.php?t=1886460
Click to expand...
Click to collapse
Not yet. Today I will receive my new Jiayu G3 ... and I would like to root it. So very interested to learn about it.

G3 is easy to root. I did root many G3 last week.
Sent from my Honor U8860 using xda-developers app

xjarl said:
G3 is easy to root. I did root many G3 last week.
Sent from my Honor U8860 using xda-developers app
Click to expand...
Click to collapse
Can you provide the link to the guideline you used?
Is it http://techideki.com/how-to-root-jiayu-g3-working-recovery-mode/ ... or the link mentioned above?

xjarl said:
G3 is easy to root. I did root many G3 last week.
Sent from my Honor U8860 using xda-developers app
Click to expand...
Click to collapse
Yeah sure bro but it will be my first smartphone and I can't copy from any device because i don't have it
I have problem. All look fine but have to messages:
"remote object 'system app/Back-Restor.apk does not exist"
"remote object 'system/bin/ric' does not exist
After that my phone reboot and have a screen:
Full restore
a full restore of all data from a connected
desktop computer has been requested. Do
you want allow this to happen?
If you did not request the restore yourself, do
not allow the operation to proceed. This will
replace any data currently on the device!
Please enter your device encryption
password below
______________________________
If the restore data is encrypted, please enter
the password below
_______________________________
I have to install some backup .apk to my Jiayu G3 phone?

I tried to root my Jiayu G3. I tested whether all drivers were installed correctly.
The situation where I have no battery on the Jiayu G3 and plugged in into the USB port is a problem
Driver is mising for MT65xx preloader ... any clue where this driver can be found?

pinibo said:
I tried to root my Jiayu G3. I tested whether all drivers were installed correctly.
The situation where I have no battery on the Jiayu G3 and plugged in into the USB port is a problem
Driver is mising for MT65xx preloader ... any clue where this driver can be found?
Click to expand...
Click to collapse
can send me files of your drives because i have code 10 error

luznykolo said:
can send me files of your drives because i have code 10 error
Click to expand...
Click to collapse
The drivers you can download via the program pdanet:
http://junefabrics.com/android/download.php
When the program asks to replace some existing drivers, you should do that.
Here you can find the flashtool and recovery.img:
http://pan.baidu.com/share/link?shareid=65391&uk=537002687

Thanks but what about Mediatek da USB VCOM? I have code 10 after installing.
Smart Phone Flash Tool will be work properly?
All drivers installed correctly but i have message from sp flash tool
SP FLASH TOOL ERROR: (8100)
[Android USB] Can not find USB port!
something different now: New message
Brom error: S_FT_NEED_DOWNLOAD_ALL_FAIL (4050)
Need download all images!

luznykolo said:
Thanks but what about Mediatek da USB VCOM? I have code 10 after installing.
Smart Phone Flash Tool will be work properly?
All drivers installed correctly but i have message from sp flash tool
SP FLASH TOOL ERROR: (8100)
[Android USB] Can not find USB port!
something different now: New message
Brom error: S_FT_NEED_DOWNLOAD_ALL_FAIL (4050)
Need download all images!
Click to expand...
Click to collapse
I just was successful in installing the driver for MT65xx Preloader (had to manually install it during the flashing exclamation mark).
When I now connect the phone without battery, I have no more exclamation marks.
Now, when I start the flash tool and connect my device without battery I get every time a different error and a window that pops-up with some (vague) explanation. Also the bottom bar of the flash tool becomes red.
It does not look good to me and I have to dive into more details to see what I should do.
In the device manager I do not have further exlamation marks ....to be continued.
So, it seems I am now on the same level as you are.

Thats right.
I think that this error means that we have to mark all files on the list but we don't have these files on the computer. I read some hint on similar tutorial (with only recovery checked on the list)
"Please note that, even though it isn't mandatory to select it on the list of images to flash, preloader file must be present in the same folder as the other partition(s) that you want to flash, or else phone will not be able to enter into download mode."

xjarl said:
G3 is easy to root. I did root many G3 last week.
Sent from my Honor U8860 using xda-developers app
Click to expand...
Click to collapse
Can you send us the mentioned files to root jiayu g3?

luznykolo said:
Can you send us the mentioned files to root jiayu g3?
Click to expand...
Click to collapse
Preamble: DO A BACKUP OF boot.img and recovery.img BEFORE MODIFYING ANYTHING!
-if you are not familar with SP Flash Tool, please google for a full guide regarding this theme: "How to Root JiaYu G3 + working Recovery mode"
the easyest way to install the needed drivers ist to install the app pdanet: h t t p:// junefabrics.com/android/
if some drivers are missing you can find also drivers in the zip files
I attached 2 zip files.
1.) use the files in root.zip with SP_Flash_Tool_v3.1222.00 to flash patched root and recovery with working cwm (english language, searched a while for that)
2.) file root.zip is meant for rooting with cwm (use only if flashing files from 1. does not the complete job)
hint: I struggled a bit on connecting the pone: press power and volume up and plug USB in was only working with attached battery
cheers and sorry for my bad english....

hi, do you know how to upload to phone another language (czech language)? or link to another custom rom. I fail to find anything. Thanks a lot

poweronat said:
Preamble: DO A BACKUP OF boot.img and recovery.img BEFORE MODIFYING ANYTHING!
-if you are not familar with SP Flash Tool, please google for a full guide regarding this theme: "How to Root JiaYu G3 + working Recovery mode"
the easyest way to install the needed drivers ist to install the app pdanet: h t t p:// junefabrics.com/android/
if some drivers are missing you can find also drivers in the zip files
I attached 2 zip files.
1.) use the files in root.zip with SP_Flash_Tool_v3.1222.00 to flash patched root and recovery with working cwm (english language, searched a while for that)
2.) file root.zip is meant for rooting with cwm (use only if flashing files from 1. does not the complete job)
hint: I struggled a bit on connecting the pone: press power and volume up and plug USB in was only working with attached battery
cheers and sorry for my bad english....
Click to expand...
Click to collapse
Thank you poweronat.
Just one question: if there is something goes wrong, how can I restore previous situation?
Thanks

Please google for "How to Root JiaYu G3 + working Recovery mode"
to get a full description of backing up boot.img and recovery.img
if youve done this right you should have a backup of your boot and recovery partitions which can be stored back if a fault occours.
the partitions should be the following (please re-check with your device):
boot: F88000 - 1588000 = length of 600000
recovery: 1588000 - 1B88000 = length of 600000
good luck

poweronat said:
Please google for "How to Root JiaYu G3 + working Recovery mode"
to get a full description of backing up boot.img and recovery.img
if youve done this right you should have a backup of your boot and recovery partitions which can be stored back if a fault occours.
the partitions should be the following (please re-check with your device):
boot: F88000 - 1588000 = length of 600000
recovery: 1588000 - 1B88000 = length of 600000
good luck
Click to expand...
Click to collapse
Where i can check this?
Spflash Tool not working for me. I've installed pda drivers. Driver successfuly installed but when i click download connect the phone without battery. Then i put the battery nothing happens. I the bottom bar i have: EMMC | Searching and nothing happens.
I've tried one more. Now i have "BROM Error" and next try "USB Cable not connected
Should i have clean sd card or something?

did you laod MT6577_Android_scatter_emmc.txt before trying to flash boot and recovery?
also it is recommended to DO A BACKUP BEFORE FLASHING

I receive access vaolation error when i try to start SP flash tool
i really need help

aha, dont know this, sorry.
ive done this with windowx XP phps you do have another machine to test this on

[Q] Rooting Tinji GT-i9220 MT6575

Hello together,
i've tried to root my new Tinji GT-i9220 with an MT6575 processor but im stuck.
Im 100% sure that i installed the drivers right.
First i have tried most of the one click tools without any noticeable success.
Than i followed this (http://forum.xda-developers.com/showthread.php?t=1923764) tutorial.
On my phone there are no mmcblk's but mtd's so the so i saved the scatter file generated by MTK Rom Studio (for some reason it suggest MT6573_Android_scatter instead of 6575) without the "_emmc" at the end.
Because of the missing "_emmc" i have to choose between 4 different Read Methods when reading the boot and recovery.img from the phone
"Read Page + Spare", "Read Page Only", "Read Spare Only" and "Read Page With ECC".
The Files created by "Read Page + Spare" and "Read Spare Only" produces error messages when TWRP or MKTDroidTools try to modify the files.
The "Read Page Only" and "Read Page With ECC" files pass through TWRP fine, but when im trying to upload the modified recovery.img to the phone in SP Flash Tool i get the Following Error:
BROM ERROR : S_DA_DRAM_NOT_SUPPORT (3004)
[H/W] The handset doesn't support DRAM. Please ask for help.
Click to expand...
Click to collapse
And here i am asking for help
Is it correct to choose "Read Page Only" while reading the files from the phone?
Does anyone know what else i can try to get the phone rooted?
Let me thank you for any help in advance.
Ohh before i forget here are a few specs from the phone and software versions i use
Tinji GT-i9220
BB Chip: MT6575
MS Board: android_2x_gb2
Modem Vers.: MAUI.11AMD.W11.50.SP.V16. 2012/06/18 16:51
UBoot Vers. : 2010.06
Kernel Vers. : 2.6.35.7
Android Vers.: 4.1.4
Sm Ver.: i9220_Dual-core1.4G_1GRAM
Custom Bild Verno.: 1346511946
SP Flash Tool V3.1304.0.sn119
Port TWRP V2.4.4.0 for MT6575/ 77/ 89
MTK Rom Studio 1.1.77.301
If you need any further information i just ask.

Another question i've made a backup of every mtd on the phone, but if i load the scatter file SP Flash Tool throws the error
BROM ERROR : S_DL_PC_BL_INVALID_GFH_FILE_INFO (5066)
Click to expand...
Click to collapse
for the DSP BL and Preloader.
Does anyone have an idea why?

Problem solved
Okay i solved my problems, had to remove some empty bytes from DSP_BL and Preloader files to get SP Flash Tool to load them correctly.
After that i found out that i had to take the yaffs2 images i've created with the "Read Page and Spare" option and then delete a bunch of bytes to make them readable for unyaffs once unyaffs was able to read them i was able to flash them to the phone.
After i managed to boot again, rooting the phone was kinda easy, i know that some people also have problems rooting exactly this phone so if anyone is interested i could upload a prerooted rom without the preinstalled chinese apps.
Is there an option to mark a question as solved?

Not for me. I have the same problem !
gagginator said:
Okay i solved my problems, had to remove some empty bytes from DSP_BL and Preloader files to get SP Flash Tool to load them correctly.
After that i found out that i had to take the yaffs2 images i've created with the "Read Page and Spare" option and then delete a bunch of bytes to make them readable for unyaffs once unyaffs was able to read them i was able to flash them to the phone.
After i managed to boot again, rooting the phone was kinda easy, i know that some people also have problems rooting exactly this phone so if anyone is interested i could upload a prerooted rom without the preinstalled chinese apps.
Is there an option to mark a question as solved?
Click to expand...
Click to collapse
Hey,
I have got the same problem but with another phone, it is a clone S3 mini with MK6575.
I get a similar error when I try to load the preloader and dsp_bl which I have generated with another exactly same type.
Currently my phone is dead, I can just comunicate with the SP flash tool but til now I can't make it work again.
These are the data extracted from the phone:
bb chip MT6575
ms board E952
IMEI xxxx
modem ver. MAUI.11AMD.W11.50.SP.V18.P2. 2012/10/10 18:37
Bar code : xxxx
build time Wed May 29 15:29:24 CST 2013
Uboot Ver. : 2010.06
Kernel Ver. : 2.6.35.7 ([email protected]) (gcc version 4.4.3 (GDC) ) #1 PREEMPT Wed May 29 15:26:11 CST 2013
Android Ver.: 2.3.3
SW Ver. : JRO03H.I8190XXALJL
Custom Build Verno. : V2G.13.05.29
How have you solved the problem with the preloader and dsp_bl ?
(I had a look to your files and they are very similar, if not exactly the same, to mine)
Thanks a lot in advance for any help in the stuff !

giuspepoli said:
How have you solved the problem with the preloader and dsp_bl ?
(I had a look to your files and they are very similar, if not exactly the same, to mine)
Thanks a lot in advance for any help in the stuff !
Click to expand...
Click to collapse
Basicly i just looked at the files i have generated with SP Flash Tools and the ones of other MTK6575 phones in an hex editor.
Ive noticed that all i all the other preloader files started with the same "MMM" string, so i just deleted anything in front of the first occuring of "MMM" in my preloader file. I also had to remove a bunch of bytes at the end of both files but i dont remember how i figured out how many
I could look at the files and maybe tell you more when im done with work

Partially solved but still problems
gagggi said:
Basicly i just looked at the files i have generated with SP Flash Tools and the ones of other MTK6575 phones in an hex editor.
Ive noticed that all i all the other preloader files started with the same "MMM" string, so i just deleted anything in front of the first occuring of "MMM" in my preloader file. I also had to remove a bunch of bytes at the end of both files but i dont remember how i figured out how many
Click to expand...
Click to collapse
I tried to remove the bytes before the "MMM" and some tentative removing others at the end but I did not succeeded in the ingestion of the preloader and dsp_bl files into the SP Flash Tools. On the other hand, I have processed the files with MTK Studio Pro and now the ingestion does not create problems. The phone now can at least boot in the recovery mode (for some reason not in the download mode), SP Flash Tools can see the nand and transfer the files.
However, I'm getting problems with other files, "sec_ro", "fat", "system" (or "android"), "cache" and "usrdata" when downloading (or update firmware).:crying:
The error is "s_ft_nand_readlen_not_page_alignment".
I tried to read the files again many times, also with different format page, spare, etc... with the other working phone obtaining the same error.
Any suggestion ?

giuspepoli said:
I tried to remove the bytes before the "MMM" and some tentative removing others at the end but I did not succeeded in the ingestion of the preloader and dsp_bl files into the SP Flash Tools. On the other hand, I have processed the files with MTK Studio Pro and now the ingestion does not create problems. The phone now can at least boot in the recovery mode (for some reason not in the download mode), SP Flash Tools can see the nand and transfer the files.
However, I'm getting problems with other files, "sec_ro", "fat", "system" (or "android"), "cache" and "usrdata" when downloading (or update firmware).:crying:
The error is "s_ft_nand_readlen_not_page_alignment".
I tried to read the files again many times, also with different format page, spare, etc... with the other working phone obtaining the same error.
Any suggestion ?
Click to expand...
Click to collapse
Could you send me your updated preloader and dsp_bl working files ?
In this case, I could try if this would solve the problems.

Hi all... where I can get oficial rom for this device ? Tinji I9220 MT6575

Lenovo P780 errors- "Kernel Block Map to PMT mismatch" "No find KernelGZ" "No Split"

Lenovo P780 errors- "Kernel Block Map to PMT mismatch" "No find KernelGZ" "No Split"
DISCLAIMER
---------------
I ASSUME THAT THE PERSON READING THIS THREAD/ARTICLE IS FAMILIAR WITH WHAT IS ROOTING AND ITS RISKS. ITS YOUR OWN RISK TO ROOT YOUR PHONE AND INSTALL
CUSTOM RECOVERY OR CUSTOM ROM. ITS YOUR CHOICE. I AM NOT RESPONSIBLE FOR ANY BRICKED PHONE ARISING OUT OF THE PROCESS/OBSERVATION FOLLOWED IN THIS THREAD
THIS THREAD IS ONLY FOR THOSE:
=> KNOW HOW TO USE TOOLS LIKE MTK DROID TOOLS AND SP FLASH TOOLS
=> HAVE ISSUES OR DIFFICULTIES OR ERRORS WHILE ROOTING OR INSTALLING CUSTOM RECOVERY
BASED ON THE ABOVE POINTS, PLEASE PROCEED FURTHER
FOR PEOPLE WHO ARE FACING LOT OF DIFFICULTIES ROOTING AND UPDATING CUSTOM RECOVORY ON LENOVO P780 PHONE
THESE ARE JUST MY OBSERVATION, THE DIFFICULTIES AND ERRORS I FACED AND HOW I FOUND WAYS AROUND THEM IN DUE COURSE.
I WONT GUARANTEE IT WILL WORK FOR YOU, BUT IT MAY, MOST PROBABLY OR GIVE YOU MORE HELP IN SOME PARTICULAR SITUATIONS.
FIRST THINGS FIRST. DO IT WITHOUT FAIL
PLEASE KEEP A FACTORY IMAGE BACKUP OF YOUR WORKING PHONE BY USING SP FLASH TOOL. STORE IT ON A SEPARATE DRIVE OTHER
THAN PHONE MEMORY/PHONE SD CARD. PROCESS THIS ROM IMAGE WITH MTKDroid TOOL BEFORE DOING ANY KIND OF WRITE OPERATION ON YOUR PHONE
TAKE A BACKUP OF YOUR CONTACTS, MESSAGES, IMEI, PHOTOS/VIDEOS, PERSONAL STUFF, SETTINGS ETC AND STORE THEM ON YOUR DESKTOP/LAPTOP/EXTERNAL DRIVE
GENERALLY GOOD PRACTICE IS TO TAKE ALL SORT OF BACKUP FROM THE ACTUAL PHONE ITSELF BEFORE DOING ANY WRITE OPERATIONS.
THERE ARE PLENTY OF CHINESE MEDIATEK PHONES FOR WHICH FINDING PROPER IMAGE IS NEXT TO IMPOSSIBLE
THERE IS NO BETTER FRIEND THAN A FACTORY IMAGE TAKEN OUT OF YOUR OWN WORKING PHONE. YOU WONT REGRET
PHONE MENTIONED THROUGHOUT THE THREAD:
LENOVO P780 8 GB MODEL. Bought in INDIA 2013
Android version : 4.4.2
Baseband version : P780.V24, 2015/01/06 09:40
Build number : P780_ROW_8G_S228_150112
IMPORTANT PREPARATION AND GROUND WORK
FIRST OF ALL HAVE LOADS OF PATIENCE. DO NOT HURRY IN TO DOING THINGS FAST AND REPENT LATER. DEVOTE LOTS OF TIME TO UNDERSTAND THE PROCESS
READ EVERYTHING AND WATCH ALL RELEVANT INTERNET VIDEOS FULLY, CAREFULLY AND PROPERLY.
DO NOT FORGET TO TAKE A COMPLETE FACTORY IMAGE BACKUP OF YOUR PHONE USING SP FLASH TOOL. PROCESS THE IMAGE WITH MTKDroid TOOL. THIS IS VERY IMPORTANT
1. Have a reliable PC or Laptop. I have rooted and updated custom recovery on my phone using Win 8.1 laptop.
Hence I would prefer a PC/Notebook with windows OS(7/8.1) installed. It is easier to find software and drivers for windows.
2. Connect your switched ON phone to PC and verify if it is detected properly by your PC.
You should be able to access the phone storage and SD card if any
3. Ensure your phone is always USB debugging mode enabled.
4. Use a tool like "usbdview" to clean up errant drivers first. Have a clean device manager at beginning.
5. Ensure you have installed proper ADB drivers. Check in device manager you should have something like "ADB interface" with no yellow triangle.
That means your drivers are properly installed. If finding drivers are difficult use PDAnet or search for universal ADB drivers and install them correctly
6. Preloader or VCOM drivers should be installed correctly. The one which worked perfectly for me was the one which I saw in You Tube by ITXTutor.
Search for "How to Install MTK Preloader 65xx Driver Correctly - Windows 8.1 64bit approved ! [HD]-PAxTCvRmlio" in You Tube.
Go Through the tutorial and download files from there. Do it exactly as it says in the tutorial.
[NOTE : IF YOUR ANTI VIRUS BLOCKS MTKDroid TOOL CREATE AN EXCEPTION]
7. Download MtkDroidTools-v2.5.3 tools on your PC. Once downloaded run the application as administrator. Switch ON your phone
Connect phone to PC. Take screen shot of MtkDroid tool application with your phone details. Create a scatter file and save it.
During this process MTKDroid showed only one error
04/06/15 14:09:29 ATTENTION!
04/06/15 14:09:29 File /system/recovery-from-boot.p which restore factory recovery in case of phone switching on in a normal mode Is Found!
[NOTE : I CAN SAY CONFIDENTLY YOU CAN IGNORE THIS ERROR. IT MIGHT BE SOMETHING THAT LENOVO USES TO ENFORCE ITS OWN RECOVERY IMAGE. THIS ERROR
FURTHER CREATES SOME PROBLEM DURING ROM IMAGE PROCESSING.]
8. Download SP Flash Tool v5.1352.01. Run the tool as administrator. Open the scatter file saved in previous step.
Go to Readback. Do a complete readback on phone. Start address always from 0x0000. Wait until READ back completes. It may take 15 to 30 minutes
and you end up with atleast 700MB size file.
My backup was 1 GB. Less than 700 MB means, there is some issue with read back. The factory image of kitkat which came as OTA was more than 700 MB.
Don't continue. Retry readback properly. You might have missed or incorrectly done some procedure(for e.g. wrong end address).
9. Once read back is complete, Run MtkDroidTools-v2.5.3 tools on your PC. Connect phone(switched on) to your PC.
Go to "root, backup, recovery" tab. Click on "To process ROM_ file from Flash Tool".
It will pop up asking to load the ROM image which you made in previous step.
Load that image. MTK should automatically start processing image.
At this point I got error as follows
05/06/15 19:16:27 --- Kernel Block Map to PMT mismatch!
05/06/15 19:16:27 -------------------------------------------
05/06/15 19:16:27 BlockName Offset
05/06/15 19:16:27 -------------------------------------------
05/06/15 19:16:27 Kernel: __NODL_PRELOAD 0x0000000003980000
05/06/15 19:16:27 PMT: PRELOAD
05/06/15 19:16:27 Kernel: __NODL_BMTPOOL 0x0000000118980000
05/06/15 19:16:27 PMT: FAT
05/06/15 19:16:27 -------------------------------------------
DON'T WORRY ABOUT THIS ERROR AS WELL. LET THE PROCESS CONTINUE
MTKDroid TOOL will ask if you need to make a CWM recovery automatically, click no and one more window will pop up, press cancel.
[NOTE : EVEN IF YOU SELECT YES TO MAKE CWM RECOVERY, MTKDroid TOOL WILL THROW MORE ERROR AS COPIED BELOW.
IT WONT CREATE CWM RECOVERY IMAGE. HOWEVER PROCESS WILL COMPLETE]
05/06/15 19:16:34 --- ERROR :No find KernelGZ
05/06/15 19:16:34 --- ERROR :No Split Boot Image
Because of PMT mismatch error Flash tool will create two scatter files.
MT6589_Android_scatter_emmc.txt and
MT6589_Android_scatter_emmc_PMT.txt.
MTK Log is as below.
05/06/15 19:16:27 --- scatter from PMTis write to the file:
C:\Users\..\Desktop\MtkDroidTools-v2.5.3\backups\Lenovo-P780_150112_ForFlashtoolFromReadBack_150605-191615\MT6589_Android_scatter_emmc_PMT.txt
05/06/15 19:16:27 - Use it if SP FlashTool errors of 8038 or 4050 occurs
The entire processed ROM file will be kept in backups directory of MtkDroidTools directory. Ensure you make a copy of this for safe keeping. This
is very important especially MT6589_Android_scatter_emmc_PMT.txt file will be very useful later.
[WHY YOU NEED TO DO ALL THESE FIRST IS BECAUSE IF YOU BRICK YOUR PHONE, EVEN A SOFT BRICK, MTKDroid TOOL IS VERY MUCH USELESS.
THIS TOOL WORKS ONLY IF YOUR PHONE IS SWITCHED ON AND BOOTED TO HOMESCREEN. MTKDroid USES ADB DRIVERS TO CONNECT WITH PHONE AND NOT VCOM DRIVERS.
IF PHONE IS NOT DETECTED BY MTKDroid THEN PROCESSING ROM IMAGE WILL NOT BE POSSIBLE. THAT OPTION WILL BE DISABLED ON THE MTKDroid TOOL.
SO NO SCATTER FILES, NO RECOVERY, BOOT, PRELOADER IMAGES, ETC, OF YOUR PHONE. SO BE VERY CAREFUL]
------------------- PROCEED FURTHER ONLY AFTER IF YOU HAVE COMPLETED ABOVE TASKS -------------------------
NOW ACTUAL PROCESS OF ROOTING AND CUSTOM RECOVERY STARTS
FIRST THING YOU WILL HAVE TO TRY IS ROOT THE PHONE USING FREELY AVAILABLE TOOLS
1. I tried various methods of rooting but, not one worked on Lenovo P780.
framaroot, towelroot, iroot, root genius, geno, mobogenie and many more didn't work.
Finally the latest version of Kingoroot did succeed to some extent.
2. Kingoroot version which worked partially was 1.3.8.2338
By partially, I mean kingo app did say Root was successful on both PC and phone. However Root checker application said "Root is not properly installed"
Application like SuperSU and busybox did not work after installation due to improper rooting.
[TRICK : DO A FACTORY REST]
3. I booted the phone in to FACTORY recovery. Did a "Factory Reset"
Now things started to brighten up!! The ever tough Lenovo P780 started to give in slowly and steadily.
After Factory reset done and phone booted up. The first thing I did was to take SP flash tool Readback once again, so that I have a clean factory image.
you may skip read back if you don't need a clean image.
4. Used another rooting application this time, i.e., iRoot older version 1.7.9.2
Viola!!! phone got rooted properly this time.
Root checker showed "Root Available", busybox and other applications started working.
NOW WE HAVE ROOT ACCESS TRY INSTALLING CUSTOM RECOVERY
[NOTE : EVEN IF YOUR PHONE DOES NOT GET ROOTED BY 3RD PARTY APPLICATION READ ON THERE IS STILL HOPE]
1. MOST HELPFUL LINK ESPECIALLY FOR ROOTING CUSTOM RECOVERY INSTALLATION IS GIVEN BELOW
http://forum.xda-developers.com/lenovo-p780/help/rooting-tutorial-kitkat-t2835605
IF ROOT FAILED FOR YOU USE TUTORIAL IN LINK TO ROOT AND TRY. THAT IS A DIFFERENT PROCESS. BUT FIRST CUSTOM RECOVERY
2. Go through the link fully. Get a good understanding. No need to do it exactly as it says. A little bit of tweak worked for me,.
3. I first tried to overwrite the factory recovery with the same factory recovery image that I backed up earlier, to see how it goes.
It is always good to try this as a first step to write using flash tool. Use the scatter files and recovery image from back up.
Here's the sequence of steps I tried.
a) Using SP-Flash-Tool-v5.1352.01, Tried to overwrite only the recovery image again with same factory image(download only). Note I used
MT6589_Android_scatter_emmc.txt scatter file which was created from my phone from MTK droid tools.
I got error from flash tool
"PMT changed for the ROM; it must be downloaded"
Error number 8038. The image was not downloaded
b) Now I realized why MTKdroid tool created another scatter file MT6589_Android_scatter_emmc_PMT.txt. It was for this issue.
I retried the same steps again, but now with MT6589_Android_scatter_emmc_PMT.txt file. Flash tool downloaded the factory recovery image successfully.
I powered on the phone, but was shocked to see it was not booting up. It came to lenovo logo and displayed error something like "DL install failed"
It was never booting up. It was SOFT BRICKED!!!!
How come with just overwriting factory recovery image again with same image.... I don't know reason for that.
Even a simple, harmless operation of overwriting factory image caused a soft brick.
This is the main reason WHY do a complete read back and relevant back up before starting write operations!!!!
I tried several other scatter files along with TWRP and CWM recovery images downloaded from the internet. I tried with all scatter files from
http://forum.xda-developers.com/lenovo-p780/help/rooting-tutorial-kitkat-t2835605. It did not work.
c) Finally after several attempts, the working combination for me was a little surprise.
I tried MT6589_Android_scatter_emmc_PMT.txt file created from my phone, along with SP_Flash_Tool_v3.1304.0.119_lenovo and TWRP_v2.7.1.1_P780_ROW_KK_Corrected
both downloaded from http://forum.xda-developers.com/lenovo-p780/help/rooting-tutorial-kitkat-t2835605
Select DA DL check box and do a download only.
This combination worked. Now I have a fully rooted and TWRP installed on my Lenovo P780.
Hope this helps!!!

Question Lenovo Phab PB1 770m no operating system help

Hi all i have new Lenovo PB1 770m I attempted to root it the TWRP was installed but it was not rooted
then I tried to update the firmware to the latest 151111 and no go, in the end i managed to delete the operating system so now I can boot to recovery mode only, When I try to restart it comes up with No OS Installed, I have tried to install xposed v79 sdk21 arm64zip no go, Ok now I know that I am an IDIOT for
not making a backup of original system and not cheking the firmware was the same as the root guide,
On the top of recovery screen is :- 2.8.7.7 SevenMaxs and TeamWin Recovery Project, I guess this could
be an expensive lesson, I have been looking for an original ROM with no luck so any help would be very
much appreciated, Thanks pluto1956, Mike
ps used info and files from here to try and root. http://forum.xda-developers.com/andr...oting-t3290347
UPDATE I managed to get a ROM from Russian site PB1-770M_S000156_150930_ROW_fastboot.7z 1.8gig
instructions say to be installed from computer via usb my problem is I can only access the internal storage or external SD card not the Usb-otg so it seems I can only update from the sd or internal memory
tried putting the rom on both but no go

Hi is there anybody that knows where and how to install the stock firmware for the phab PB1-770M

HELP
Same as above. need a stock rom. formatted internal storage mistakenly. HELP!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!

naeemdurrani said:
Same as above. need a stock rom. formatted internal storage mistakenly. HELP!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
Click to expand...
Click to collapse
Well i did it. Is really simple but it seems nobody has this problem before. You need
- Download Stock Firmware from russian lenovo site
- The Tool i used is QPST_2.7.422 QFIL it cames with the Drivers (i used Win8.1)
- Put phone in Download mode (press vol up and down same time and connect phone to PC)
- Open QFIL program and select flat build
- In select programmer you select prog_emmc_firehose_8936.mbm
- In load xml i selected rawprogram_unsparse and path0
- After that you click download and wait like 4 min and when say finish succesfully you start phone manually
I hope this helps.

Thanks brother, yesterday i downloaded one russian rom in zip format and there was a .bat file included in it. i only double clicked and it flashed through adb and fastboot and it was successfull. i got the operating system 5.0.2 but WLAN is not working, tried flashing several time but no luck. i learned that it is still under warranty ..so sent it to warranty. in a week it will be back with be for testing again hopefully.
well i will try your method as soon as i get my beast again. Thank you so much for helping out in timely manner, really appreciate it brother.
jotade said:
Well i did it. Is really simple but it seems nobody has this problem before. You need
- Download Stock Firmware from russian lenovo site
- The Tool i used is QPST_2.7.422 QFIL it cames with the Drivers (i used Win8.1)
- Put phone in Download mode (press vol up and down same time and connect phone to PC)
- Open QFIL program and select flat build
- In select programmer you select prog_emmc_firehose_8936.mbm
- In load xml i selected rawprogram_unsparse and path0
- After that you click download and wait like 4 min and when say finish succesfully you start phone manually
I hope this helps.
Click to expand...
Click to collapse
---------- Post added at 08:10 AM ---------- Previous post was at 08:06 AM ----------
it is very easy my friend just look into the only topic/thread about Phab plus in xda. it will guide you well.
if you get any error in recovery like footer is wrong/signature verification failed. connect your phone and first check if your device in being tracked by adb. use adb devices.
if your device appear in the list of devices ..use fastboot oem unlock then flash sevenmax twrp again after entering into temporary twrp as per phab plus thread.
0verdaflow said:
How can you root this damn phones.... i was trying like for 2 days....
Click to expand...
Click to collapse

jotade said:
Well i did it. Is really simple but it seems nobody has this problem before. You need
- Download Stock Firmware from russian lenovo site
- The Tool i used is QPST_2.7.422 QFIL it cames with the Drivers (i used Win8.1)
- Put phone in Download mode (press vol up and down same time and connect phone to PC)
- Open QFIL program and select flat build
- In select programmer you select prog_emmc_firehose_8936.mbm
- In load xml i selected rawprogram_unsparse and path0
- After that you click download and wait like 4 min and when say finish succesfully you start phone manually
I hope this helps.
Click to expand...
Click to collapse
Could you please elucidate more? I downloaded the ROM and the flash program. However, I've no clue how to get going. I don't even see the xml files anywhere (as mentioned by you).
Just don't want to screw it up bad so being little more cautious.

jotade said:
Well i did it. Is really simple but it seems nobody has this problem before. You need
- Download Stock Firmware from russian lenovo site
- The Tool i used is QPST_2.7.422 QFIL it cames with the Drivers (i used Win8.1)
- Put phone in Download mode (press vol up and down same time and connect phone to PC)
- Open QFIL program and select flat build
- In select programmer you select prog_emmc_firehose_8936.mbm
- In load xml i selected rawprogram_unsparse and path0
- After that you click download and wait like 4 min and when say finish succesfully you start phone manually
I hope this helps.
Click to expand...
Click to collapse
im getting this error
Start Sending Programmer
Download Fail:System.Exception: Unable to download Flash Programmer using Sahara Protocol
at QC.QMSLPhone.Phone.QPHONEMS_SaharaArmPrgDownload(String sFileName)
at QC.SwDownloadDLL.SwDownload.QPHONEMSSaharaDownloadArmPrg(UInt64& version, String armPrgPath)
Download Fail:Sahara FailSahara Fail
Finish Download
cant flash the stock rom

man dont use Qfil program.
the rom which you downloaded should be in zip format, unzip it, there is a file download_with_partiotion.bat.
run it and sit back until it is finished.
Wakatsik said:
im getting this error
Start Sending Programmer
Download Fail:System.Exception: Unable to download Flash Programmer using Sahara Protocol
at QC.QMSLPhone.Phone.QPHONEMS_SaharaArmPrgDownload(String sFileName)
at QC.SwDownloadDLL.SwDownload.QPHONEMSSaharaDownloadArmPrg(UInt64& version, String armPrgPath)
Download Fail:Sahara FailSahara Fail
Finish Download
cant flash the stock rom
Click to expand...
Click to collapse

naeemdurrani said:
man dont use Qfil program.
the rom which you downloaded should be in zip format, unzip it, there is a file download_with_partiotion.bat.
run it and sit back until it is finished.
Click to expand...
Click to collapse
i cant use the .bat cause my phone is already bricked...it wont be recognize by the app...the only way is thru QFIL but the problem is that i always get the error above

Hi, same here. I tried using QFIL and getting Sahara Fail. Then tried clicking on the bat file but its not working since the phone is not recognized. Please help.
EDIT : I got the QFIL working just now and my phone is working. Flashed the stock rom and I think it will be just fine.

whiskey_1388 said:
Hi, same here. I tried using QFIL and getting Sahara Fail. Then tried clicking on the bat file but its not working since the phone is not recognized. Please help.
EDIT : I got the QFIL working just now and my phone is working. Flashed the stock rom and I think it will be just fine.
Click to expand...
Click to collapse
My phone was wiped by me . I have TWRP and my phone is read as ADB interface (when in recovery mode). I tried adb devices and it returned 1f82f24b recovery. I also can access my phone memory from PC when in TWRP recovery which enables me to transfer files.
My problem is it is only read as ADB interface not as Qualcom COM port device. When I try Download_with_partition.cmd I get the error that it can not distinguish devices and to try. Any solution by those managed to install it successfully?

For everyone landing in this page due to wiping his OS of Lenovo Phab Plus by mistake (like I did), please refer to this thread:
Lenovo Phab Plus PB1-770M Stock ROM needed

Thanks!
jotade said:
Well i did it. Is really simple but it seems nobody has this problem before. You need
- Download Stock Firmware from russian lenovo site
- The Tool i used is QPST_2.7.422 QFIL it cames with the Drivers (i used Win8.1)
- Put phone in Download mode (press vol up and down same time and connect phone to PC)
- Open QFIL program and select flat build
- In select programmer you select prog_emmc_firehose_8936.mbm
- In load xml i selected rawprogram_unsparse and path0
- After that you click download and wait like 4 min and when say finish succesfully you start phone manually
I hope this helps.
Click to expand...
Click to collapse
I was not doing the 8936.mbn part!
By default it is 8916 so it doesnt work. but after changing that setting, it work!:highfive::good:

I can't unbrick
Hi!
I have a Lenovo Phab PB1-770M, this phone won't turn on, only Lenovo logo, or fastboot or flashmode.
With Flashtool i can't flash. In Fastboot i flash a recovery or operating system, i reboot the phone and again only the Lenovo screen, operating system not starting.
What can i do?

naeemdurrani said:
man dont use Qfil program.
the rom which you downloaded should be in zip format, unzip it, there is a file download_with_partiotion.bat.
run it and sit back until it is finished.
Click to expand...
Click to collapse
this is what i get running the .bat command >
'adb' is not recognized as an internal or external command,
operable program or batch file.
╟δ╚╖▒ú╩╓╗·─▄╣╗╩╢▒≡adb╔Φ▒╕!╟δ╓╪╩╘úí
please ensure the phone can distinguish adb devices! Please retry!
Press any key to continue . . .

[guide] Blu Vivo XL4 | | Vivo Xi || Vivo Xi+

The BLU VIVO XL4 has arived.
Sorry this guide is not for very new users, it relies on certain amount of prior knowledge.
**NOTE**
Unlocking Bootloader WILL set warranty flag to "NO"
Make the read-back backup, BEFORE unlocking, so there is a possibility to restore warranty to "yes"
Getting SPFlash Tool to work on BLU VIVO XL4
I used sp flash tool version 5.18.28
Needs custom DA file and Auth file. Both have been found from a near clone device.
Open flash tool select the DA file and Auth file from the link below.
add the scatter file from archive. There is a preloader file in the archive also. This is needed for spflash tool to open the Auth file.
Stock Rom and Auth file
Then follow the guide found on youtube.
Not planning to go into too much detail about the actual pulling of the firmware, as there is already
a fantastic guide with step-by-step photos and also a video.
Just the basics
Pull stock rom with spflash tool once just from the "boot region" to get the preloader file.
Process that file with the Wwr_MTK tool to get partition table information.
And one more time pull as one large binary file from the "user region" then split it into
individual images using the tool called "Wwr_MTK" it can be found on other site(Hovatek). I cannot put a
link as it is against forum rules (no advertising other forums)
But there is a youtube video that describes the process. And gives link for download of the tool.
**NOTE-1**
The Wwr_MTK tool did not have the correct chip (mt6762 In fact the "family class" for the chip is mt6765) as an option. Because of this you will need to add it to the tool before using it. Open the downloaded zip.( I used "WwR_MTK_2.40_Eng" ). Open "Template.ini" with text editing software, in the section labeled "CPU" add "MT6765 2" , keep same format as the rest of the file. Save the changes and close Template.ini.
Now when you run the tool, you will be able to create the scatter file as you split the rom into files.
**NOTE-2**
The tool connects to internet and downloads fresh the files and scripts when you start it. There is a 30 second ad screen displayed. If you block internet to the tool, then the add screen turns into 2 minute wait screen. I am not suggesting that you hack the tool to by-pass it, just letting you know what to expect.
IT IS HIGHLY RECOMMENDED TO MAKE YOUR OWN FULL BACKUP BEFORE PERFORMING THESE STEPS
AFTER YOU HAVE MADE FULL BACKUPS
Now to start modifying
DOWNLOAD
UNLOCK BOOTLOADER
unlocking bootloader is no more complicated then then enabling OEM unlock toggle in dev options menu.
Then performing Command in terminal. Just like so many android devices.
Unlock Bootloader
1. Enable Developer options on phone:
open settings--> "about device"--> click build number 5-7 times--> go back one screen in settings
-->select more "more settings" --> scroll to bottom "Develpoer options" --> enable "usb debugging"
2. Open cmd or power shell terminal
3. reboot phone to bootloader with the following commands
Code:
adb reboot bootloader
4.Once the phone has finished loading into fastboot mode type this command
Code:
fastboot oem unlock
I also did --MIGHT be an optional step
Code:
fastboot flashing unlock
Do not think both were needed.
After each command when phone was rebooted,
it took extra time to open. But did not show the normal recovery screen while
it did the factory reset. But a reset did happen both times,
as I had the setup wizard each time.
Even after unlocking bootloader, doing a "fastboot boot *xyz.img" (boot or recovery test images)
Phone would only cycle to off then do a full reboot. Doing "fastboot flash boot boot.img" does flash the boot.
And "fastboot flash recovery recovery.img" does flash the recovery.
TWRP
1. Download TWRP From Link above
2. Enable Developer options on phone:
open settings--> "about device"--> click build number 5-7 times--> go back one screen in settings
-->select "more settings" --> scroll to bottom "Develpoer options" --> enable "usb debugging"
3. Open cmd or power shell terminal
4. reboot phone to bootloader with the following commands
Code:
adb reboot bootloader
5. Now give the command to flash twrp, assuming you downloaded the file to default download folder
Code:
fastboot flash recovery %userprofile%\downloads\TWRP-3_2_3-1020-OMFG-mod_b6-device-name-vivo-wipe-misc.img
5. Reboot to twrp. Needed to boot directly to twrp, or stock recovery will be re-flashed by phone.
Code:
fastboot oem reboot-recovery
Once inside twrp It is asking for password to unlock (decrypt)***automatic decrypt not work on this device as of YET***
this is supposed to be same password used to unlock phone.
Because this twrp does not work with encryption, every time you reboot you will have to select language, if changed from default.
To get recovery to be functional, you need to make phone patched for both "DM-Verity" and "Force-encryption"
I do this with
"Universal Disabler"
https://forum.xda-developers.com/android/software/universal-dm-verity-forceencrypt-t3817389
There is similar utiliy built into this Recovery image.
to use the built in option , Select ADVANCED, Then RM Forceencrypt
This will flash the lazypatcher with options set to remove encryption both in boot.img and /vender/*fstab : remove dm-verity.
--OR-- manually do the following steps
Steps
1. Download Zip from Link above.
2. Open TWRP
3. Open Wipe menu
4. Select format /data
5. Key in "YES" and swipe
6. Return to Home Page of TWRP
7. Choose reboot menu then recovery
8. Recovery should now have access to Internal memory (temp for now)
9. Use abd push to put the zip file downloaded above to internal memory
Code:
adb push %userprofile%\downloads\Disable_Dm-Verity_ForceEncrypt_12.16.2018.zip /sdcard/
10. Select install menu , and install the Disable_Dm-Verity_ForceEncrypt_12.16.2018.zip
Do not rename the file. It installs and makes the patch base on the file name.
If you want to have root also, then flash Magisk at this point.
Now the dm-verity and force encryption are off. You can flash gsi custom rom, if you desire. At the moment, I have only been able to boot the phone with working cell data and calls on the PHH-Phusion --vanilla builds. Do not know why the gapps versions do not allow rill to function.
As of the writing of this I have put up V4 of the TWRP port. This version uses the correct mount points for this phone, not the ones from the source of the port. Also corrected the device name in default.prop, to match device name. Build fingerprint has been left as is. Fixed the micro sdcard name and OTG names. Added mipe to the "misc" /"para" partition to escape a factory reset recovery loop that [uu]could[/u] happen under certain situations.
And my prefered ported recovery from LRTeam TWRP-3_2_3-1020-OMFG-mod_b6-device-name-vivo-wipe-misc.img.
DOWNLOADS
Files
1. Sp Flash tool (v 5.18.28 or newer) https://androidmtk.com/smart-phone-flash-tool
2. stock XL4 ROM, DA file, TWRP all in shared folder https://androidfilehost.com/?w=files&flid=287088
3. stock Xi+ ROM, TWRP in shared folder https://androidfilehost.com/?w=files&flid=287703
4. Unviversal DM-Patch disable tool thread
5. Youtube Guide Video to use backup image splitter tool "WWR_MTK" https://www.youtube.com/watch?v=GMAytZ56hac
Kernel sources have been published 12-12-2018, by BLU
I have them synced to GitHub while I make test builds.
https://github.com/mrmazakblu/BLU-VIVO-XL4-kernel
Default defconfig should be arch/arm64/config/k62mv1_64_bsp_defconfig. Based off of build description in "getprop"
Built kernel has not been able to be booted yet.
TWRP is first ported and provided thanks to @Voinea12
.

placeholder not really welcomed here on XDA
just pm a moderator or report this thread when you`re ready to upload something, until then, thread closed

After seeing that the Blu vivo xl4 requires an "auth file" in order to flash with spflash tool, I asked BLU to supply the file.
They responded with a big fat NO.
.......
.......
THE NEXT DAY THE FILE WAS POSTED ON A DIFFERENT THREAD.
SO THERE HELP WAS NO LONGER NEEDED.

Just made successfull readback on preloader. and currently reading full rom.
will post link when done.
here is auth file and DA file I used.
pulled firmware is here.
there are more images in complete firmware, but the ones included should be enough , as long as you NEVER do format all from spflash tool.
STOCK ROM

So far all attempts to load twrp have failed.
Also just tried to flash boot.img with the built kernel. When rebooted, phone just stayed on black screen. No back-light , nothing.
Just a repeating connect disconnect sound from pc. Long pressing power and trying to get into the bootloader menu failed.
Was able to Que up sp flash tool and keep holding the volume down button , on the next time it cycled on off preloader was caught and i was able to flash back the correct boot.img.
Working version is available now

Thread was opened.

mrmazak said:
So far all attempts to load twrp have failed.
Also just tried to flash boot.img with the built kernel. When rebooted, phone just stayed on black screen. No back-light , nothing.
Just a repeating connect disconnect sound from pc. Long pressing power and trying to get into the bootloader menu failed.
Was able to Que up sp flash tool and keep holding the volume down button , on the next time it cycled on off preloader was caught and i was able to flash back the correct boot.img.
Click to expand...
Click to collapse
My streak with SP Flash is still a losing one, the auth file works for my phone as well (Blu Vivo XI+), I just used the preloader.img that was in the update.zip and ran it through the WwR MTK Tool and got the preloader.bin to go with the auth file as you indicated you had done, that was one hurdle that your post helped me solve, but for some reason when I start reading the full rom I get about 6-10 MB into it and then it disconnects from my phone and stops. Not sure if its driver related or what, which drivers did you use for the readback?

psychofad said:
My streak with SP Flash is still a losing one, the auth file works for my phone as well (Blu Vivo XI+), I just used the preloader.img that was in the update.zip and ran it through the WwR MTK Tool and got the preloader.bin to go with the auth file as you indicated you had done, that was one hurdle that your post helped me solve, but for some reason when I start reading the full rom I get about 6-10 MB into it and then it disconnects from my phone and stops. Not sure if its driver related or what, which drivers did you use for the readback?
Click to expand...
Click to collapse
To be honest I have not installed driver specific for this. I have vcomm drivers installed, same from couple years ago.
Is the readback stopping because you set wrong hex address length in the readback tab?

mrmazak said:
To be honest I have not installed driver specific for this. I have vcomm drivers installed, same from couple years ago.
Is the readback stopping because you set wrong hex address length in the readback tab?
Click to expand...
Click to collapse
No, I got the readback of the EMMC_USER just fine and ran it through the WwR MTK tool and it gave me the hex address to use for the full rom readback, t then told me
Code:
The file size is smaller than the start position of the LK (uboot). To determine the type of processor and memory, it is necessary to read the full firmware in the SP Flash Tool, specify the parameters for reading: Start address: 0x0, Lenght: 0x1D1EC00000.
So I entered those two addresses as EMMC_USER readback. If my phone is off and I just connect it to the usb without holding any keys it gives me another error.....and I'm an idiot. just figured it out as I was looking at logs, apparently I must have changed the usb speed in sp flash which changes it's pid causing it to try and read from another port. It's downloading now

Thanks to @hanuma there is now a material themed twrp port.
The V2 version loads. But has no adb or mtp access
https://forum.xda-developers.com/showpost.php?p=78498431&postcount=95
https://mega.nz/#F!225EzQwT!t8hvGvmFoNYNvXev-Li1fQ

******EDIT*****
Most of the following problems did not repeat in same way when I tried to repeat the install process.
Main issue was with simcard. But exact process to get installed and working is still not known.
-- install after already having rooted, encryption removed stock, seems to work.
-- fresh full stock rom, full encryption, then gsi seems to not work sim card.
PHH-treble gsi images do boot this device. I do not have a bug list as yet.
working:WITH encryption removed:
1. wifi
2. camera
3. fingerprint- unlock
4. music
5. video
NOT working :WITH encyyption removed:
1. cell signal
2. cell data
3. phone
4. sms
---------------------------------------------------------------------------------------------------
---------------------------------------------------------------------------------------------------
working:WITH encryption enabled
1. phone
2. sms
NOT working:WITH encryption enabled
1.. everything else
EDIT
Much of the force closing problems were from a corrupted external sdcard. When I removed the card , the force close messages did not come.
Getting 4G data connection was not stable. after a full reset and rom re-install I was not able to get data connection, and only able to have connection to make calls when set to 3G connection only.
some bugs in vendor I assume will need some help solving this.
EDIT 2
Finally got around to trying again. his time I started with vanilla version of phh-treble gsi.
4G data and sms, calls in out all work. Camera , video both work.
WiFi tethering did not work.
Setup that worked :
force encryption removed with universal dm-verity patcher, ( bothboot.img and vendor partitions both edited).
magisk patched boot

Would this work on Blu Vivo XI since same chipset?

sinkoo1979 said:
Would this work on Blu Vivo XI since same chipset?
Click to expand...
Click to collapse
It should. I have been working with few users with Xi+ it works for them. And another user of Xi provided a twrp port, but no details on if this read-back worked. It must have, I suppose it must have.
Please do try to do the readback for your self, and share the files. will help with twrp if I can

Guide has been revised.
The original guide suggests to format /data and patch device to remove force encryption. This works fine for stock rom, and modifying stock rom. But I have found that removing encryption will not allow the phone to work as a phone when flashed with GSI. The down side is, at the moment, there is no twrp that is working to read the encrypted /data.

mrmazak said:
Guide has been revised.
The original guide suggests to format /data and patch device to remove force encryption. This works fine for stock rom, and modifying stock rom. But I have found that removing encryption will not allow the phone to work as a phone when flashed with GSI. The down side is, at the moment, there is no twrp that is working to read the encrypted /data.
Click to expand...
Click to collapse
Can any of this be done without a computer

Decaphyz said:
Can any of this be done without a computer
Click to expand...
Click to collapse
No, you need fastboot(PC preogram) to unlock bootloader and either sp flash tool or fastboot to flash recovery.

mrmazak said:
No, need you fastboot(PC preogram) to unlock bootloader and either sp flash tool or fastboot to flash recovery.
Click to expand...
Click to collapse
Oof

mrmazak said:
Thanks to @hanuma there is now a material themed twrp port.
The V2 version loads. But has no adb or mtp access
https://forum.xda-developers.com/showpost.php?p=78498431&postcount=95
https://mega.nz/#F!225EzQwT!t8hvGvmFoNYNvXev-Li1fQ
Click to expand...
Click to collapse
I just did this, and it worked the first time. I got into the phone and set it up. But it was super laggy after a while. So I decided to reset the phone like how you would normally do to fix a problem, and now... it’s making me boot into the recovery each and every time I try and boot into the system... i installed the gsi rom "PixelExperience for AOnly" at max lees site

IndifferentBear said:
I just did this, and it worked the first time. I got into the phone and set it up. But it was super laggy after a while. So I decided to reset the phone like how you would normally do to fix a problem, and now... it’s making me boot into the recovery each and every time I try and boot into the system... i installed the gsi rom "PixelExperience for AOnly" at max lees site
Click to expand...
Click to collapse
dont panic. this is minor bug. Easiest way to solve is to flash stock recovery. and do factory reset from there.
You can install image from twrp or fastboot, even spflashtool.
It is from the flag that is set into para(misc) partition.
You can clear it manually with terminal also, or even use one of the othe rtwrp images I shared. One with "misc" in the file name.
If you use one of those recoveries and do reset will also clear that reboot condition

mrmazak said:
dont panic. this is minor bug. Easiest way to solve is to flash stock recovery. and do factory reset from there.
You can install image from twrp or fastboot, even spflashtool.
It is from the flag that is set into para(misc) partition.
You can clear it manually with terminal also, or even use one of the othe rtwrp images I shared. One with "misc" in the file name.
If you use one of those recoveries and do reset will also clear that reboot condition
Click to expand...
Click to collapse
thanks dude! can you give me the command to run in terminal to do it? ill try that first, then ill try flashing stock recovery!
---------- Post added at 02:47 AM ---------- Previous post was at 02:44 AM ----------
mrmazak said:
dont panic. this is minor bug. Easiest way to solve is to flash stock recovery. and do factory reset from there.
You can install image from twrp or fastboot, even spflashtool.
It is from the flag that is set into para(misc) partition.
You can clear it manually with terminal also, or even use one of the othe rtwrp images I shared. One with "misc" in the file name.
If you use one of those recoveries and do reset will also clear that reboot condition
Click to expand...
Click to collapse
but i was required to wipe the sys, data, cache, and dalvik/art to have a clean install.
---------- Post added at 03:33 AM ---------- Previous post was at 02:47 AM ----------
mrmazak said:
dont panic. this is minor bug. Easiest way to solve is to flash stock recovery. and do factory reset from there.
You can install image from twrp or fastboot, even spflashtool.
It is from the flag that is set into para(misc) partition.
You can clear it manually with terminal also, or even use one of the othe rtwrp images I shared. One with "misc" in the file name.
If you use one of those recoveries and do reset will also clear that reboot condition
Click to expand...
Click to collapse
YO! Oaky so basic laly when i flashed that misc recovery IT BOOTED!!!!! thank you soo much dude, your the best!