Database Info

Stock rom req for n8000+ deluxe mt6577 1gh dual core

Hi developers, i just received this china phone Model N8000+ Deluxe with MT6577 1GH Dual Core running Android 4.0.4. My problem is that i have flashed wrong boot image, so now when i switch on the phone, the screen are all white. try searching from internet but all i get is for N8000 model only. Could someone pls someone out there have the stock rom link for download? pls help tq

Same Boat!
I am in the same boat! ANYONE out there with the original firmware to the N8000+? I had the phone for literally 4 hours! ANYONE out there with the original firmware so that it can be reflashed?

ShawvMedia said:
I am in the same boat! ANYONE out there with the original firmware to the N8000+? I had the phone for literally 4 hours! ANYONE out there with the original firmware so that it can be reflashed?
Click to expand...
Click to collapse
Hi shaw,i have called my supplier, they said the stock rom will available in 2 or 3 weeks...

fadhil3536 said:
Hi shaw,i have called my supplier, they said the stock rom will available in 2 or 3 weeks...
Click to expand...
Click to collapse
2 or 3 weeks!? NOOOOOOOOOOO! So I guess I learned a valuable lesson... lol... :silly:. Thanks for finding that out. There has to be someone on here with the same phone as us who can extract the rom faster than that... hopefully.

ShawvMedia said:
2 or 3 weeks!? NOOOOOOOOOOO! So I guess I learned a valuable lesson... lol... :silly:. Thanks for finding that out. There has to be someone on here with the same phone as us who can extract the rom faster than that... hopefully.
Click to expand...
Click to collapse
hi shaw did manage to bring alife ur phone agai?

fadhil3536 said:
hi shaw did manage to bring alife ur phone agai?
Click to expand...
Click to collapse
I use this for N8000
http://forum.xda-developers.com/showthread.php?t=1695210
No work gps and wifi low and bluetooth don't work perfectly but all work normally.
Need use drivers. You need test yours drivers for your mobilephone. My is a:
ov5640_yuv = CAMERA OK
hi704_yuv = CAMERA Front don't work perfectly but unique work
RX_50NT_323A = VIDEO OK
and others using others configurations. Read forum for more details

sanderfuture said:
I use this for N8000
http://forum.xda-developers.com/showthread.php?t=1695210
No work gps and wifi low and bluetooth don't work perfectly but all work normally.
Need use drivers. You need test yours drivers for your mobilephone. My is a:
ov5640_yuv = CAMERA OK
hi704_yuv = CAMERA Front don't work perfectly but unique work
RX_50NT_323A = VIDEO OK
and others using others configurations. Read forum for more details
Click to expand...
Click to collapse
I have a nandroid backup image using clockwork. My device now its origimal rom and rooted. The important thing thos you must have recovery.put backup image in sd card ang restore via rocovery.

I am using this phone currently (N8000+ MT6577 dualcore) and already managed to extract the full backup. Please PM me if you still need the backup. Unable upload now because the backup is in my home computer.

Just finished uploading stock rom (unrooted/untouched) into my 4shared. Please find these files useful in restoring your device:
1) MT6577 scatter for n8000+
2) original uboot.img
3) original boot.img
4) original recovery.img
5) original system.img
6) original logo.img
Remember to extract and put into same directory/folder before loading the scatter file via SP Flash tool (or need to select manually if load scatter without files in same directory/folder)
The above stock rom details :
Model number - e1908_v77_jbl1
Android version - 4.0.4
Baseband version - MAUII.11AMD.W12.22.SP.V1,2012/07/28 12:23
Kernel version - 3.0.13 SMP PREEMPT Mon Aug 6 14:49:18 CST 2012
Build Number - E1908_V77_JBL1_20120806
NOTE : The original rom doesn't wake up the phone when press home button. Need to root and edit mtk-kpd.kl file to make home button wake up.
UPDATE : Some people are having problem to root the device. Here is my copy of pre-rooted system.img
I only root it from the original and nothing more. Only for N8000+, please do not use on other model. I will not be responsible if you brick your device by flashing into other model.
No mod recovery yet because my current mod recovery will boot loop after factory reset from Backup & reset setting.

Notification LED does not work
Someone managed to flash the LED notification on the part of the freight side of the mobile sensor

please tell me from which shop you bought the star n8000+ with analog tv ? mine did not had tv and sell it. Now I want to buy it again but have certainly ANALOG tv. please send me a message to order. thanks!!!

help
Hi,
can somebody give me full dump of E1908_V77_JBL1_20120806 firmware? Espessially i need EBR1 EBR2 and MBR files. I tryed to repartition my /data to 2GB and now my phone does not boot up. Thank u!!!

Try to root "e1901_v77_jbl1_notv_20121011"
aze2learn said:
Just finished uploading stock rom (unrooted/untouched) into my 4shared. Please find these files useful in restoring your device:
1) MT6577 scatter for n8000+
2) original uboot.img
3) original boot.img
4) original recovery.img
5) original system.img
6) original logo.img
Remember to extract and put into same directory/folder before loading the scatter file via SP Flash tool (or need to select manually if load scatter without files in same directory/folder)
The above stock rom details :
Model number - e1908_v77_jbl1
Android version - 4.0.4
Baseband version - MAUII.11AMD.W12.22.SP.V1,2012/07/28 12:23
Kernel version - 3.0.13 SMP PREEMPT Mon Aug 6 14:49:18 CST 2012
Build Number - E1908_V77_JBL1_20120806
NOTE : The original rom doesn't wake up the phone when press home button. Need to root and edit mtk-kpd.kl file to make home button wake up.
UPDATE : Some people are having problem to root the device. Here is my copy of "pre-rooted system.img"
I only root it from the original and nothing more. Only for N8000+, please do not use on other model. I will not be responsible if you brick your device by flashing into other model.
No mod recovery yet because my current mod recovery will boot loop after factory reset from Backup & reset setting.
Click to expand...
Click to collapse
I have rooted my old phone (Star N9770-e1809 c_v77_gq1008_9p017). Now I want to root my new phone too. Please guide me how do you create stock rom image before I try to root it.
My phone is:
Model number - e1901_v77_jbl1_notv
Android version - 4.0.4
Baseband version - MAUI.11AMD.W12.22.SP.V8.P2,2012/08/22 19:39
Kernel version - 3.0.13 SMP PREEMPT Thu Oct 11 14:06:43 CST 2012
Build Number - E1901_V77_JBL1_NOTV_20121011
And it doesn't wake up the phone when press home button too. Please tell me how to edit mtk-kpd.kl file to make home button wake up.
How noob I am !

codric72 said:
Hi,
can somebody give me full dump of E1908_V77_JBL1_20120806 firmware? Espessially i need EBR1 EBR2 and MBR files. I tryed to repartition my /data to 2GB and now my phone does not boot up. Thank u!!!
Click to expand...
Click to collapse
Here : http://www.4shared.com/zip/CgW-4Tq4/MBR_EBR1_ori_reupload.html
Anijja said:
I have rooted my old phone (Star N9770-e1809 c_v77_gq1008_9p017). Now I want to root my new phone too. Please guide me how do you create stock rom image before I try to root it.
My phone is:
Model number - e1901_v77_jbl1_notv
Android version - 4.0.4
Baseband version - MAUI.11AMD.W12.22.SP.V8.P2,2012/08/22 19:39
Kernel version - 3.0.13 SMP PREEMPT Thu Oct 11 14:06:43 CST 2012
Build Number - E1901_V77_JBL1_NOTV_20121011
And it doesn't wake up the phone when press home button too. Please tell me how to edit mtk-kpd.kl file to make home button wake up.
How noob I am !
Click to expand...
Click to collapse
Please check PM

How to make my home button wake up phone??

How to make my home button wake up phone
yhao said:
How to make my home button wake up phone??
Click to expand...
Click to collapse
For me:-
- After ROOT your phone use "Root Browser"(it's free) to go to the folder: system/usr/keylayout,
- Open file "mtk-kpd.kl" in text mode with any text editor
- move to the line: "key 102 HOME" and add " WAKE" (without quote) at the end of this line
- press "Save icon" to Save Changes.
- Shut down and then restart.
I have done it with my S3-clone (e1901_v77_jbl1_notv) and hope it also work with other model

Does any one know how to root this device??
E1901_V77_GQ2002_9P017
Kernel ver: 3.0.13

Preloader and DSP_BL N8000+
Hi friends!
Someone who has the preloader and DSP_BL of this model?
Thank you very much!

Complete Stock Rom
aze2learn said:
Just finished uploading stock rom (unrooted/untouched) into my 4shared. Please find these files useful in restoring your device:
1) MT6577 scatter for n8000+
2) original uboot.img
3) original boot.img
4) original recovery.img
5) original system.img
6) original logo.img
Remember to extract and put into same directory/folder before loading the scatter file via SP Flash tool (or need to select manually if load scatter without files in same directory/folder)
The above stock rom details :
Model number - e1908_v77_jbl1
Android version - 4.0.4
Baseband version - MAUII.11AMD.W12.22.SP.V1,2012/07/28 12:23
Kernel version - 3.0.13 SMP PREEMPT Mon Aug 6 14:49:18 CST 2012
Build Number - E1908_V77_JBL1_20120806
NOTE : The original rom doesn't wake up the phone when press home button. Need to root and edit mtk-kpd.kl file to make home button wake up.
UPDATE : Some people are having problem to root the device. Here is my copy of pre-rooted system.img
I only root it from the original and nothing more. Only for N8000+, please do not use on other model. I will not be responsible if you brick your device by flashing into other model.
No mod recovery yet because my current mod recovery will boot loop after factory reset from Backup & reset setting.
Click to expand...
Click to collapse
@aze2learn Could you send me the complete stock rom for N8000+? I need all IMG files, including "preloader, dsp_bl, cache, ebr1...".
I hope your answer. Thank you very much!

manolin8 said:
@aze2learn Could you send me the complete stock rom for N8000+? I need all IMG files, including "preloader, dsp_bl, cache, ebr1...".
I hope your answer. Thank you very much!
Click to expand...
Click to collapse
The reason why I don't share preloader and dsp_bl because some people are 'brilliant' enough to brick their phone WITHOUT reading and knowing anything by simply flashing every single rom found for the similar model. Wrong uboot is enough to brick a phone but still can be repair by trial and error using MDT ... a wrong preloader will render a phone useless and even TP (testpoint) sometimes won't help. As I understand, some model won't allow preloader flashing with/without TP.
cache.img is not important in reviving dead phone because it has nothing in it. ebr1 is in my previous post. Please contact me through PM if you really need these files and mention the reason why. Have a brick N8000+ do you?
I don't have a 'complete' stock rom. I have a BACKUP from my own phone. Please understand the difference.
ps : the original backup was lost when my 500gb hdd crashed 2 months ago .. the only rom backup I have now is all inside the phone itself.

Root Qmobile A2 V3

Hey and Salam everybody,
important note: i am taking no responsibility if your phone dies or what so ever. do wipe reset your phone through stock recovery before proceeding. only use the softwares i provided. and also only email me if you run into problems using the softwares i provided. and please wipe data reset ur phone before proceeding. all the softwares are in my dropbox
This is my first ever post so make sure if you get your problem solved i would very much appreciate that you help others too.
All the credit goes to rua1 (http://forum.xda-developers.com/member.php?u=5119815)
I bought the phone a month back and spent 3 weeks trying to root this MTK6575 Chipset.
You can only root this phone through test point from PMT method. Google test point and pmt for more information.
Attached a pic showing a test point cable . people having knowledge of modding 360 will know what a pmt is. its pogo mo thoin. but for phone its bit different.
first of all turn your phone on and connect it to mtkdroidtools and then make scatter of it. and save it for future use . picture attach. clik blocks map and then click create scatter.
its better to go into stock recovery and wipe data reset and wipe cache. take your sim cards out and your memory card. you dont need them.
my phone details.
Model Number : A2
Android version : 2.3.6
Baseband Version: MAUI.11AMD.W11.50.SP.V14.P2, 2012/09/07 10:26
Kernal Version: 2.6.35.7 [email protected] #1 Thu Oct 11 13:41:54 HKT 2012
Build Number : ALPS.GB2.MP.v2.2
Custom Build Version : S8035S_PP_F1_PK_1.06_V3
Files you need:
1 Drivers For MTK6575 - Qmobile A2 V3
2 Google ADB Latest
3 MTK Droid Tools
4 Smart Phone Flash Tools
5 Superuser-3.1.3-arm-signed
you can find all these files in my dropbox
https://www.dropbox.com/sh/3wjle4gfu9ekc2x/2Y2f1yuZlE
install drivers for mtk6575
open flash tools and select scatter loading. select the scatter MT6575_Android_scatter that was made earlier and click ok. go to second tab in flash tools. now your in read back tab. click add. save the file titled rom_1 in the extracted mkt droid tools folder. then select hex and read page only . in start address write 0x0000000000000000 and in length 0x10da0000 < this is the address of cache in scatter and your might be different depending on the date you bought the phone.
click ok
now click read back plug in the usb cable with no battery in and just touch the needle with the test point in pic. it will start reading back. once it completes it will give you green circle.
now go to mtkdroidtools and open mtkdroidtools.exe turn on your phone normally and let the tools detect the phone. once it detects you will see different information on main screen. now goto second tab (root, backup, recovery) and click " to process file ROM_ from flash tool" at this point locate the file rom_1 you just saved in rom folder of extracted mtk droid tools. once you give it the location it will start processing. it will ask you if you want it to automatically make cwm ? click yes once the process gets complete you will have multiple files in
\MTK Droid Tools\MtkDroidTools\backups\A2_121030_ForFlashtoolFromReadBack_130415-104113
your folder name will be different depending on date and time.
inside the folder you will have lots of files. the file you need to flash will be A2_121030__recovery_130415-104113 again the numbers at the end of the file depends on your date and time.
now again open spflash tools on the main screen select scatter loading. locate this folder.
\MTK Droid Tools\MtkDroidTools\backups\A2_121030_ForFlashtoolFromReadBack_130415-104113
open the scatter and uncheck all boxes . check only one box that says recovery. double click on and find this file.
A2_121030__recovery_130415-104113
its in \MTK Droid Tools\MtkDroidTools\backups\A2_121030_ForFlashtoolFromReadBack_130415-104113
now click download ignore the warning take the battery out insert the usb cable and make sure to touch the test point after u click download . note that from this method ur phone is in bootrom mode. if everything is successfull youll get a green circle.
you might get errors and for that your scatter must be edited for example adding __NODL_ before CACHE in scatter. if that doesnt work then you might have to add __NODL_ before USRDATA and if still ur gettin error well then email me.
now to test recovery press both vol+ and vol- button at the same time and hit power . go into recovery by pressing vol+. and you have cwm on your phone. now the first and most important thing take backup and save it,
its also better to stay into recovery and open mtk droid tools and make bakcup by going into second tab.
after that put Superuser-3.1.3-arm-signed on ur sd to flash through cwm
now flash superuser-3.1.3-arm-signed through cwm
turn on your phone and see if you have superuser on ur home screen
open super user and grant permission and voila your rooted go to info tab and check for updates
thats it your phones rooted.
if i helped you then press thank
in the attachment you can see the cable i made. make yours the same way
UPDATE: SPFT and MTKDROIDTOOLS update versions have been put in dropbox.
again if you encounter pmt layout changed or other errors then email me so i can help you gettin rid of errors with editing the scatter. [email protected]

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!!!

[ROM][TWRP] LineageOS 12.1 for Teclast tPad 98 Octa Core (rev. M1E9) with ASB 2019-04

Hello world,
following my efforts to create a LOS12.1 build for the Elephone P6000 Pro based on cm12-amami, I have created another cm12-amami based ROM for the
Teclast tPad 98 Octa Core (revision M1E9)
based on ASB security level 2019-04-05. My build includes a TWRP recovery needed to install, as well as instructions in a README, and is available for download from here:
LineageOS for Teclast tPad 98 Octa Core (rev. M1E9) with current ASB 2019-04-05 security patches
Please note that the standard disclaimer applies: When following the instructions, your tablet's warranty is void. Use at your own risk! I am not responsible for any damage or problems you may run into/have.
Owners of other revisions of tPad 98 Octa Core:
It might work out to use this build for other hardware revisons of tPad 98 than M1E9 (such as M1E1 to M1E8 or M2E1 and so on) as well with the changes described in the README - unfortunately, I am not able to test this as I don't own any other revision.
Have fun!
awl

Updated to ASB 2018-09-05. For details & download link see above...

awl14 said:
Updated to ASB 2018-09-05. For details & download link see above...
Click to expand...
Click to collapse
One more time, updated to ASB 2018-12-05 (including some fixes to avoid German O2/E-Plus SIM/network combinations being detected as national roaming).
Download location as before:
LineageOS 12.1 (aka CyanogenMod 12.1) for the Teclast tPad 98 (M1E9) based on AOSP 5.1.1
Have fun!
awl

ive got a Teclast tPad 98 Octa Core (revision M1E9)
i need a stock ROM with Scatter file
the Teclast site wont let me download it is there anywhere else i can download it from?

pandashoe said:
ive got a Teclast tPad 98 Octa Core (revision M1E9)
i need a stock ROM with Scatter file
the Teclast site wont let me download it is there anywhere else i can download it from?
Click to expand...
Click to collapse
Have you seen the README file for my ROM? It clearly states:
. Use the MT6753 scatter file from the latest stock ROM available from
http://www.teclast.com/tools/pad/pad.php?t=p
(for M1E9, this is https://pan.baidu.com/s/1bptuKXL for V1.04)
Click to expand...
Click to collapse
I have just checked both links, and both do work well. (You need to use the Chinese language Teclast webpages, the English ones are completely outdated...)
HTH & best regards
awl

BTW. file name is 98 八核 升级版 (M1E9)-Android6.0-V1.04-9D7B.rar - you might find it elsewhere
If you are still unable to download from baidu (last time I checked, there were several options such as a Chrome plugin) or elsewhere, please let me know.

baidu wont let me download it i did get the MT6753 scatter but sp flash tool gives me this ERROW8417)
---------- Post added at 02:44 PM ---------- Previous post was at 02:43 PM ----------
(8417)

pandashoe said:
baidu wont let me download it i did get the MT6753 scatter but sp flash tool gives me this ERROW8417)
Click to expand...
Click to collapse
I have attached the scatter file only from the tPad 98 M1E9 latest 1.04 stock ROM to this post - hope this helps...
Best,
awl

Sent you a thanks for sending me the scatter.txt
it downloaded the red bar then after that a BROM ERROW
there no life in it anywhere so i think i must have totally bricked it

Using Mediatek's "SP Flash Tool" and the full stock ROM download, you can almost always revive your device (https://androidmtk.com/flash-stock-rom-using-smart-phone-flash-tool) - it is nearly impossible to brick these MTK devices software-wise, so if you don't have a real hardware defect, you should simply select "Format All & Download" with the full stock ROM, and get your tablet working again.
If you still did not succeed in downloading the full M1E9 stock ROM from Baidu, just let me know, and I'll send you a private download link via PN.
Best regards,
awl

hi again and many thanks for all your help baidu still wont work for me could you send me the full stock ROM
ive used Sp flash tools many times before without any problem so fingers crosses i can get it right and all of this so i can have a recovery on it lol

once again many thanks for the stock rom but i had these 3 folders before and noting in them works the sp flash took doesent load so used my own and it gets an errow so downloaded the new V 5.1824 with the same result i get status scatter file invalid
the download-agent is MTK_AllInOne_DA.bin
i really did think this would cure my problem as its a newish tablet hardly use and never dropped

Can you try to make SP Flash tool look like in the attached screenshot? Especially, select "Firmware Upgrade" or even "Format All + Download" instead of just "Download", then hit the "Download!" button and only then connect your tablet (which has to be fully switched off)...
If you are following these instructions, and it still doesn't work, then sorry, I am at my wits' end...

ive used sp flash tools since i had my htc desire years ago and never had this problem before the scatter.txt wont load on the tool
so ive tryed everything as if it wont load how can i flash it lol
am going to try on another laptop thats the only thing left as ive tryed different cables,sp flash tools and different scatter files
let you know if thats any better

hi tryed in on my other laptop and the same result scatter wont load what v of the sp flash tool to you use?

pandashoe said:
hi tryed in on my other laptop and the same result scatter wont load what v of the sp flash tool to you use?
Click to expand...
Click to collapse
version: SP_Flash_Tool_v5.1820_Win
What exactly do you mean by: scatter file "won't load"? Do you get an error message already when selecting the scatter file in the SP Flash tool, or an error later after clicking on the download button and starting the firmware write process to the device?
Can you post a screenshot of your SP Flash tool (like mine above) immediately before pressing the download button, and then another one showing the exact error message?
Edit:
And have you tried using a different micro USB cable and USB port on your PC? Maybe you simply have a defective cable or port!?

scatter load
View attachment 4719011
ive used all different cables and even a different laptop

first scatter file
View attachment 4719012
or this if i use the first scatter file you sent me

So this means that you get these errors when selecting the scatter file, i.e. even before clicking on the download button?
Just wildly guessing, but: Have you tried to remove the spaces from the path to both (a) SP Flash Tool itself and (b) the ROM image?
I have seen the most weird errors resulting from spaces in file paths when software wasn't able to handle them...
Fingers crossed...
awl
Edit: And please definitely make sure that your tablet is NOT YET connected when selecting the scatter file. Only connect your tablet after clicking on the Download button.

no the tablet is not connected to the pc and i took out the _ and even renamed the .txt but still wont load onto the sp flashtool
its all very strange how you can get it to work and i cant!!!
---------- Post added at 03:44 PM ---------- Previous post was at 03:15 PM ----------
yep still the same the scatter files out of the Chinese folder wont work infact the sp tools out of the chinese folder wont load
so non of the stuff in the 3 chinese folders doesnt load on any of my laptops

HELP: Attempting to obtain root on BLU G9 Pro

Hello all, so long story short I had bought a BLU G9 Pro which came with Android 9 Pie. The only device-specific guide I could find online about obtaining root was: https://www.getdroidtips.com/root-blu-g9-pro/
The information on that guide is trivial and can be applicable to almost any device. The root method worked, however, there was an OTA update to Android 10 (and then later a security update) which I took. I then attempted to re-root the device utilizing the same method. However, now it seems that everytime I flash a Magisk modded boot.img my device gets stuck in a bootloop and will not go past the bootloader. I believe that this device may be uncharted territory but it is a great phone and I would love to have both Magisk root and the latest Android 10 firmware. I have found that Magisk supports both Android 10 and A-only devices so I do not see what is causing the problem. Additionally, I attempted to flash an AOSP GSI of Android 10 which refused to boot before I even installed Magisk. I am new to modern Android devices with Project Treble so please forgive me if there is something obvious I am missing. Any help is appreciated, thanks in advance!

@eLatErbI
Try flashing GSI like said in https://source.android.com/setup/build/gsi#flashing-gsis
May be vbmeta flashing is required for your device.
You can get vbmeta.img from your stock firmware.

It seems that Verified Boot could definitely be getting in the way. Could this possibly explain why Magisk is working on the Android 9.0 version of the stock ROM but not Android 10? However, I thought Magisk disabled verified boot in the kernel (boot.img) also I do not have a vbmeta.img in any stock firmware for this phone. Any other means of disabling verified boot? Thanks in advance!

Hi, I have the same problem with my G9 PRO, I tried to boot all kinds of GSI roms with and without magisk and it doesn't work (bootloop). I cannot find the vbmeta partition anywhere so I am hesitant to try to flash it without a backup. There is a mention of it in the fstab of the boot partition, however it is not in the stock firmware or in my own backups. Magisk did also work for me before the Android 10 update. Does anyone have an idea of how AVB works without a vbmeta partition or a verity file?

You can extract the boot.img from your phone if you updated to 10. I updated and used SP Flash to read the boot.img and WwR_MTK to get the partition length and starting value for the boot.img and patched it using Magisk and reflashed it over fastboot. I know this thread is a bit old but if anyone is interested, reply and I will post the link that explains. I have Android 10 running on my Blu G9 pro rooted.

tuffasagong said:
You can extract the boot.img from your phone if you updated to 10. I updated and used SP Flash to read the boot.img and WwR_MTK to get the partition length and starting value for the boot.img and patched it using Magisk and reflashed it over fastboot. I know this thread is a bit old but if anyone is interested, reply and I will post the link that explains. I have Android 10 running on my Blu G9 pro rooted.
Click to expand...
Click to collapse
Hi. Please post the link. It will be very helpful for me. I have the BLU_G0231WW android 10.

Here is the link: https://forum.hovatek.com/thread-21970.html
This is what I did to root the phone:
Download WwR_MTK 2.30 and SP Flash (I used version 5.2112)
**Open WwR_MTK 2.30 and create a basic Scatter File by choosing the Platform Type (processor) which for Blu G9 Pro is MT6771. Click create and save as - I saved all files in one folder.
**Open SP Flash Tool and under the download tab choose the scatter file we just created it will have only Preloader under it.
**Go to the Readback tab press Add -- Double click on what was added and just keep it saved as ROM_0 (once again I saved it in the same folder as the scatter file) -- the Start Address is in the scatter file as "physical_start_addr:" it should be 0x0 and the length is "partition_size:" and the value should be 0x80000. Keep the Region as EMMC_USER unless you want the preloader but to get the boot.img we don't need that. Turn off your phone and press the Read Back button with the Arrow and plug your phone into the computer. It will read the file and give you a big Green Check to let you know it completed succesfully.
**Once you have the ROM_0 open it up in WwR_MTK 2.30 Under Step 3 (Choose the EMMC_USER partition in the prepared backup) you will get an error that says "The file size is smaller than the start position of the LK (uboot)" press OK -- You will get another error that says "To determine the ype of process and memory.... blah blah blah" Press OK
**Click the Scatter File tab -- Under the Name field find boot. We now get the starting value of the boot.img and the partition length. We need these values to put back into SP Flash.
**Go to SP Flash and Readback tab again. Press add. Double Click the new add and save it as boot.img -- Region is EMMC_USER and the start address is going to be the HEX value next to Boot and length the length address next to boot. For the BLU_G0231WW_V10.0.04.07_GENERIC Build these addresses are:
Start: 0x20C00000 and Length: 0x2000000
Push ok when you put the start address and length for the boot.img and once again push Readback and connect your phone while off. The File size I got was a boot.img of 32,768 KB in size which is much bigger than the boot.img of the Android 9 (which was like 9 MB in size).
**Install Magisk on the phone and patch the boot.img and flash it with fastboot and boom, you have a rooted BLU G9 Pro with the latest Update. Keep your stock boot.img as I rooted my phone with the 10.0.04.04 update and could not update to 10.0.04.07 until I reflashed the stock boot.img in case there is another update.
That is all there is to it and you should be able to use this tutorial to root if BLU pushes anymore updates.

tuffasagong said:
Here is the link: https://forum.hovatek.com/thread-21970.html
This is what I did to root the phone:
Download WwR_MTK 2.30 and SP Flash (I used version 5.2112)
**Open WwR_MTK 2.30 and create a basic Scatter File by choosing the Platform Type (processor) which for Blu G9 Pro is MT6771. Click create and save as - I saved all files in one folder.
**Open SP Flash Tool and under the download tab choose the scatter file we just created it will have only Preloader under it.
**Go to the Readback tab press Add -- Double click on what was added and just keep it saved as ROM_0 (once again I saved it in the same folder as the scatter file) -- the Start Address is in the scatter file as "physical_start_addr:" it should be 0x0 and the length is "partition_size:" and the value should be 0x80000. Keep the Region as EMMC_USER unless you want the preloader but to get the boot.img we don't need that. Turn off your phone and press the Read Back button with the Arrow and plug your phone into the computer. It will read the file and give you a big Green Check to let you know it completed succesfully.
**Once you have the ROM_0 open it up in WwR_MTK 2.30 Under Step 3 (Choose the EMMC_USER partition in the prepared backup) you will get an error that says "The file size is smaller than the start position of the LK (uboot)" press OK -- You will get another error that says "To determine the ype of process and memory.... blah blah blah" Press OK
**Click the Scatter File tab -- Under the Name field find boot. We now get the starting value of the boot.img and the partition length. We need these values to put back into SP Flash.
**Go to SP Flash and Readback tab again. Press add. Double Click the new add and save it as boot.img -- Region is EMMC_USER and the start address is going to be the HEX value next to Boot and length the length address next to boot. For the BLU_G0231WW_V10.0.04.07_GENERIC Build these addresses are:
Start: 0x20C00000 and Length: 0x2000000
Push ok when you put the start address and length for the boot.img and once again push Readback and connect your phone while off. The File size I got was a boot.img of 32,768 KB in size which is much bigger than the boot.img of the Android 9 (which was like 9 MB in size).
**Install Magisk on the phone and patch the boot.img and flash it with fastboot and boom, you have a rooted BLU G9 Pro with the latest Update. Keep your stock boot.img as I rooted my phone with the 10.0.04.04 update and could not update to 10.0.04.07 until I reflashed the stock boot.img in case there is another update.
That is all there is to it and you should be able to use this tutorial to root if BLU pushes anymore updates.
Click to expand...
Click to collapse
Thank tuffasagong.
I now have my blu g9 pro magisk rooted on Android 10. I added viper4Android, Adaway and more tweaks.
Have you noticed the desktop mode when screen casting to second display? I wonder if there is a way to reduce lag when using bluetooth mous.

&oot4peace said:
Thank tuffasagong.
I now have my blu g9 pro magisk rooted on Android 10. I added viper4Android, Adaway and more tweaks.
Have you noticed the desktop mode when screen casting to second display? I wonder if there is a way to reduce lag when using bluetooth mous.
Click to expand...
Click to collapse
flashed magisk but bricked phone Does anyone happen to have g9 pro v10 firmware G0230WW or G0231WW readback rom? please i need to unbrick and firmware on web wont work. Please help..

Tesh3180 said:
flashed magisk but bricked phone Does anyone happen to have g9 pro v10 firmware G0230WW or G0231WW readback rom? please i need to unbrick and firmware on web wont work. Please help..
Click to expand...
Click to collapse
Search here: BLU Stock Firmware Repository (Mediafire)

lopestom said:
Search here: BLU Stock Firmware Repository (Mediafire)
Click to expand...
Click to collapse
thanks but already tried that file and wont work..

Tesh3180 said:
thanks but already tried that file and wont work..
Click to expand...
Click to collapse
Which version were you on? The latest at the time? A little more info did you flash a Magisk patched boot image?

Blu pushed out a new update 10.0.04.08 a couple weeks ago. Reflash the stock Boot image to update. Boot image has the same length and start addresses. I just reflashed the magisk Boot image I made with 10.0.04.07 and works fine.

tuffasagong said:
Here is the link: https://forum.hovatek.com/thread-21970.html
This is what I did to root the phone:
Download WwR_MTK 2.30 and SP Flash (I used version 5.2112)
**Open WwR_MTK 2.30 and create a basic Scatter File by choosing the Platform Type (processor) which for Blu G9 Pro is MT6771. Click create and save as - I saved all files in one folder.
**Open SP Flash Tool and under the download tab choose the scatter file we just created it will have only Preloader under it.
**Go to the Readback tab press Add -- Double click on what was added and just keep it saved as ROM_0 (once again I saved it in the same folder as the scatter file) -- the Start Address is in the scatter file as "physical_start_addr:" it should be 0x0 and the length is "partition_size:" and the value should be 0x80000. Keep the Region as EMMC_USER unless you want the preloader but to get the boot.img we don't need that. Turn off your phone and press the Read Back button with the Arrow and plug your phone into the computer. It will read the file and give you a big Green Check to let you know it completed succesfully.
**Once you have the ROM_0 open it up in WwR_MTK 2.30 Under Step 3 (Choose the EMMC_USER partition in the prepared backup) you will get an error that says "The file size is smaller than the start position of the LK (uboot)" press OK -- You will get another error that says "To determine the ype of process and memory.... blah blah blah" Press OK
**Click the Scatter File tab -- Under the Name field find boot. We now get the starting value of the boot.img and the partition length. We need these values to put back into SP Flash.
**Go to SP Flash and Readback tab again. Press add. Double Click the new add and save it as boot.img -- Region is EMMC_USER and the start address is going to be the HEX value next to Boot and length the length address next to boot. For the BLU_G0231WW_V10.0.04.07_GENERIC Build these addresses are:
Start: 0x20C00000 and Length: 0x2000000
Push ok when you put the start address and length for the boot.img and once again push Readback and connect your phone while off. The File size I got was a boot.img of 32,768 KB in size which is much bigger than the boot.img of the Android 9 (which was like 9 MB in size).
**Install Magisk on the phone and patch the boot.img and flash it with fastboot and boom, you have a rooted BLU G9 Pro with the latest Update. Keep your stock boot.img as I rooted my phone with the 10.0.04.04 update and could not update to 10.0.04.07 until I reflashed the stock boot.img in case there is another update.
That is all there is to it and you should be able to use this tutorial to root if BLU pushes anymore updates.
Click to expand...
Click to collapse
I've followed this and have gotten quite far but I can't seem to find any working fastboot drivers for the G9 pro, I have tried several different ones and with every one I get absolutely no hits on "fastboot devices" and upon any attempts to flash, it leaves me at "waiting for device" I just want to know if you had a specific driver or if it's different issue

Cathedralruins said:
I've followed this and have gotten quite far but I can't seem to find any working fastboot drivers for the G9 pro, I have tried several different ones and with every one I get absolutely no hits on "fastboot devices" and upon any attempts to flash, it leaves me at "waiting for device" I just want to know if you had a specific driver or if it's different issue
Click to expand...
Click to collapse
Use the Platform Tools for A9 or A10.
Downloads - Read and accept the terms.: platform-tools-latest-windows.zip
Device need OEM Unlock & USB Debugging enable.
Maybe your PC need USB Drivers: drivers USB OEM
Maybe need MTK USB driver: MTK Driver

lopestom said:
Use the Platform Tools for A9 or A10.
Downloads - Read and accept the terms.: platform-tools-latest-windows.zip
Device need OEM Unlock & USB Debugging enable.
Maybe your PC need USB Drivers: drivers USB OEM
Maybe need MTK USB driver: MTK Driver
Click to expand...
Click to collapse
First off, thank you for your really speedy assistance with this, I appreciate it.
A couple things, to note, the device has already had OEM unlocking and usb debugging enabled, it works with adb, but is not recognized at all by fastboot itself, I'm definitely going to try those drivers and that version of the platform tools. Is there any log, device list, or any other info I can dump that would be useful in troubleshooting this?
Thanks again for your assistance, lopestom.

Cathedralruins said:
First off, thank you for your really speedy assistance with this, I appreciate it.
A couple things, to note, the device has already had OEM unlocking and usb debugging enabled, it works with adb, but is not recognized at all by fastboot itself, I'm definitely going to try those drivers and that version of the platform tools. Is there any log, device list, or any other info I can dump that would be useful in troubleshooting this?
Thanks again for your assistance, lopestom.
Click to expand...
Click to collapse
Bootloader unlocked?
Authorization PC vs device already has with USB debugging?
If yes so look drivers.

Hello there,
My technical skills when comes to android phones is next to zero, but I have been running linux (Fedora, Endeavour, currently Debian 11), I am not affraid of the terminal.
I have bought a Blu g9 pro, like 3 months ago, it came out of the box with android 9, then It updated to android 10.
It is very close to stock android, and I am ok with it, exept for a few creepy apps that I would like to remove,
I would like your input on what is the safest aproach, can I just 'debloat' the current system? or might as well replace it with something else?
Thank you.

I attempted to flash the patched boot image from Magisk but my G9 Pro started boot looping. I've tried to flash every firmware that I can find for this model but I keep getting an error message from the Flash tool.
Any guidance?

tuffasagong said:
Here is the link: https://forum.hovatek.com/thread-21970.html
This is what I did to root the phone:
Download WwR_MTK 2.30 and SP Flash (I used version 5.2112)
**Open WwR_MTK 2.30 and create a basic Scatter File by choosing the Platform Type (processor) which for Blu G9 Pro is MT6771. Click create and save as - I saved all files in one folder.
**Open SP Flash Tool and under the download tab choose the scatter file we just created it will have only Preloader under it.
**Go to the Readback tab press Add -- Double click on what was added and just keep it saved as ROM_0 (once again I saved it in the same folder as the scatter file) -- the Start Address is in the scatter file as "physical_start_addr:" it should be 0x0 and the length is "partition_size:" and the value should be 0x80000. Keep the Region as EMMC_USER unless you want the preloader but to get the boot.img we don't need that. Turn off your phone and press the Read Back button with the Arrow and plug your phone into the computer. It will read the file and give you a big Green Check to let you know it completed succesfully.
**Once you have the ROM_0 open it up in WwR_MTK 2.30 Under Step 3 (Choose the EMMC_USER partition in the prepared backup) you will get an error that says "The file size is smaller than the start position of the LK (uboot)" press OK -- You will get another error that says "To determine the ype of process and memory.... blah blah blah" Press OK
**Click the Scatter File tab -- Under the Name field find boot. We now get the starting value of the boot.img and the partition length. We need these values to put back into SP Flash.
**Go to SP Flash and Readback tab again. Press add. Double Click the new add and save it as boot.img -- Region is EMMC_USER and the start address is going to be the HEX value next to Boot and length the length address next to boot. For the BLU_G0231WW_V10.0.04.07_GENERIC Build these addresses are:
Start: 0x20C00000 and Length: 0x2000000
Push ok when you put the start address and length for the boot.img and once again push Readback and connect your phone while off. The File size I got was a boot.img of 32,768 KB in size which is much bigger than the boot.img of the Android 9 (which was like 9 MB in size).
**Install Magisk on the phone and patch the boot.img and flash it with fastboot and boom, you have a rooted BLU G9 Pro with the latest Update. Keep your stock boot.img as I rooted my phone with the 10.0.04.04 update and could not update to 10.0.04.07 until I reflashed the stock boot.img in case there is another update.
That is all there is to it and you should be able to use this tutorial to root if BLU pushes anymore updates.
Click to expand...
Click to collapse
Saved me - TY. This worked for me for Mintt Ultramintt Y3 - basically an Aussie rebadged Blu G9 Pro. I used this method for it with Pie 9 (before allowing update to 10). Cheers