Database Info

[Q] Formatted NVRAM using SP Flash Tool, what should I do?

Phone: Cherry Mobile Titan (Rebrand of Konka w990/Spice-mi 500/Axioo Picopad GEW)
Processor: MTK6577
Hello guys, this is my first post as I could no longer find any solution on the internet. Hoping some experts could help
I accidentally formatted the NVRAM of my phone using SP Flash Tool. The new update didn't have the option not to format it. Now my IMEI's are lost. Although it is still possible to restore them using some methods. But none of the methods I have found were permanent. A simple wipe/data factory reset from CWM Recovery removes it instantly. Is there a way I could restore the NVRAM, or at least make the restoration methods permanent?
Thanks in advance guys!
EDIT: I tried flashing all available ROMs (SP Flash Tool Based / Flashable Zips) but still it shows an invalid IMEI. I also tried restoring a backup of my stock ROM to no avail.

ToldarkenHansam said:
Phone: Cherry Mobile Titan (Rebrand of Konka w990/Spice-mi 500/Axioo Picopad GEW)
Processor: MTK6577
Hello guys, this is my first post as I could no longer find any solution on the internet. Hoping some experts could help
I accidentally formatted the NVRAM of my phone using SP Flash Tool. The new update didn't have the option not to format it. Now my IMEI's are lost. Although it is still possible to restore them using some methods. But none of the methods I have found were permanent. A simple wipe/data factory reset from CWM Recovery removes it instantly. Is there a way I could restore the NVRAM, or at least make the restoration methods permanent?
Thanks in advance guys!
EDIT: I tried flashing all available ROMs (SP Flash Tool Based / Flashable Zips) but still it shows an invalid IMEI. I also tried restoring a backup of my stock ROM to no avail.
Click to expand...
Click to collapse
I'm in same case. I accidently damage my nvram ;
i have a complet backup made with mtkdroid tools (nvram included)
but sp flash tool doent give option to restore this part? how to restore?

the same problem for me. The phone is fully working, but it is very annoying to restore imei and delete wifi network (NVRAM WARNING err...) after each new ROM. And also I cannot sell this phone to anybody in the future.
No solution for this problem?

somebody can write commenttt???
---------- Post added at 07:54 AM ---------- Previous post was at 07:48 AM ----------
hey guys .at this picture error how can i solve this error?
h t t p : / /u1306.hizliresim.com/1b/l/p975s.jpg

first, you`ll need to root your device. refer to here:
http://forum.xda-developers.com/showthread.php?t=2332783
follow the tutorial step by step, if you brick your device i will laugh at you. if you got questions, ask them before doing random stuff.
if you got it rooted, you can recover your IMEI with different software. i will link one in this post later.
for questions - use this thread or PM me.

ToldarkenHansam said:
Phone: Cherry Mobile Titan (Rebrand of Konka w990/Spice-mi 500/Axioo Picopad GEW)
Processor: MTK6577
Hello guys, this is my first post as I could no longer find any solution on the internet. Hoping some experts could help
I accidentally formatted the NVRAM of my phone using SP Flash Tool. The new update didn't have the option not to format it. Now my IMEI's are lost. Although it is still possible to restore them using some methods. But none of the methods I have found were permanent. A simple wipe/data factory reset from CWM Recovery removes it instantly. Is there a way I could restore the NVRAM, or at least make the restoration methods permanent?
Thanks in advance guys!
EDIT: I tried flashing all available ROMs (SP Flash Tool Based / Flashable Zips) but still it shows an invalid IMEI. I also tried restoring a backup of my stock ROM to no avail.
Click to expand...
Click to collapse
I think your phone is dead. Is the phone detected when you plug it in to your pc via USB?

phone isn't dead. root it first, recovering imei is easy then. cannot explain more, im on smartphone right now.
sent from my Star N9770 using XDA App

so, here is a tool to generate the IMEI`s of your smartphone. you will usually find them in the back of your device. push the generated file to /data/nvram/md/NVRAM/NVD_IMEI/ and DON'T FORGET TO SET FULL RWX rights. (with ADB, cd to the mentined folder and set MP0B_001 with chmod to mode 777, in root explorer just check every box for read write and execute. otherwise phone cannot read the IMEI.

What a lame answers. Especially ones suggesting to root phone.
They guy clearly told he is able to restore MP0B_001 in phone, but its SOFT-IMEI and is lost after wipe/factory reset.
@ Original question by ToldarkenHansam, which is kinda outdated, but considering lame answers here:
To restore HARD-IMEI in NVRAM hidden partition use SN Write Tool or Maui META 3G. They are able to write hard IMEI and calibration to NVRAM partition.
@ kokabunga - if you have nvram.bin backup you can easily resore it with SP Flash Tool. Just open your scatter file with any text editor, find a __NODL_NVRAM section and remove __NODL_ part from it. Reopen scatter in SP Flash Tool and you'll be able to check NVRAM partition.
It might not be able to upload it without other parts selected. But you can you Options->Write memory, then manually enter start address, which will be show on download/upgrade page near NVRAM and length (your nvram.bin length) - that will always work. Be careful to write correct address thou.
Sidenote: all suggested methods before only touch SOFT-IMEI, stored in /data/nvram/md/NVRAM/NVD_IMEI/MP0B_001. Its lost with any wipe/reset, because whole /data partition are formatted. Then the whole /data/nvram directory (if it's empty) are restored from hidden NVRAM partition on EMMC. If you've corrupted your NVRAM when it won't restore correct IMEI ofc. With all methods mentioned above (i.e. replacing MP0B_001, echoing to pttycmd1, using mtkdroidtools, mobileuncletools and others) will only edit MP0B_001, i.e. soft copy of IMEI, which will be lost again with next hardware reset. Sure you restore your IMEI that way every time you wipe/reset/upgrade firmware. But its more solid to fix your IMEI partition with SN Write Tool / Maui META 3G so it will be correctly restored automatically from NVRAM at every wipe/etc.
EDIT: @Chrizzly92 this software are very outdate. It generates 24 byte MP0B_001 file, used by old MT6573/6513 platforms. Newer 6575/6577 uses 120 bytes MP0B_001 which are different. If you put 24 byte MP0B_001 generated instead from imei.c software, your phone will be buggy and will be constantly loosing IMEI every few hours until reboot. It's better to use MtkDroidTools or terminal method (echoing to /dev/pttycmd1) to correctly restore 120 byte IMEI file.

n9770, mt6577, no problem at all with the generated files.
sent from my Star N9770 using XDA App

same thing happened to me.. only sn write tool maybe able to do the job..I have also lost wifi mac address..now getting nv110 error..
but I need database and modem files for xolo a700 can anyone help?

NStorm said:
What a lame answers. Especially ones suggesting to root phone.
They guy clearly told he is able to restore MP0B_001 in phone, but its SOFT-IMEI and is lost after wipe/factory reset.
@ Original question by ToldarkenHansam, which is kinda outdated, but considering lame answers here:
To restore HARD-IMEI in NVRAM hidden partition use SN Write Tool or Maui META 3G. They are able to write hard IMEI and calibration to NVRAM partition.
@ kokabunga - if you have nvram.bin backup you can easily resore it with SP Flash Tool. Just open your scatter file with any text editor, find a __NODL_NVRAM section and remove __NODL_ part from it. Reopen scatter in SP Flash Tool and you'll be able to check NVRAM partition.
It might not be able to upload it without other parts selected. But you can you Options->Write memory, then manually enter start address, which will be show on download/upgrade page near NVRAM and length (your nvram.bin length) - that will always work. Be careful to write correct address thou.
Sidenote: all suggested methods before only touch SOFT-IMEI, stored in /data/nvram/md/NVRAM/NVD_IMEI/MP0B_001. Its lost with any wipe/reset, because whole /data partition are formatted. Then the whole /data/nvram directory (if it's empty) are restored from hidden NVRAM partition on EMMC. If you've corrupted your NVRAM when it won't restore correct IMEI ofc. With all methods mentioned above (i.e. replacing MP0B_001, echoing to pttycmd1, using mtkdroidtools, mobileuncletools and others) will only edit MP0B_001, i.e. soft copy of IMEI, which will be lost again with next hardware reset. Sure you restore your IMEI that way every time you wipe/reset/upgrade firmware. But its more solid to fix your IMEI partition with SN Write Tool / Maui META 3G so it will be correctly restored automatically from NVRAM at every wipe/etc.
EDIT: @Chrizzly92 this software are very outdate. It generates 24 byte MP0B_001 file, used by old MT6573/6513 platforms. Newer 6575/6577 uses 120 bytes MP0B_001 which are different. If you put 24 byte MP0B_001 generated instead from imei.c software, your phone will be buggy and will be constantly loosing IMEI every few hours until reboot. It's better to use MtkDroidTools or terminal method (echoing to /dev/pttycmd1) to correctly restore 120 byte IMEI file.
Click to expand...
Click to collapse
Greetings NStorm i try your method i already got one backup with MTKDROID TOOLS so i can use the NVRAM.BIN , i already modify scatter file and try to write memory but i only receive red bar, no yellow or green, so i think it not work at all, any suggestions also sorry for my bad english im from Mexico, ohhh i forgot i already have a full backup from all the files in the smartphone do you know if i can FLASH the Full Backup back? or a CWM restore or other kind of solution?

foox2k said:
Greetings NStorm i try your method i already got one backup with MTKDROID TOOLS so i can use the NVRAM.BIN , i already modify scatter file and try to write memory but i only receive red bar, no yellow or green, so i think it not work at all, any suggestions also sorry for my bad english im from Mexico, ohhh i forgot i already have a full backup from all the files in the smartphone do you know if i can FLASH the Full Backup back? or a CWM restore or other kind of solution?
Click to expand...
Click to collapse
NStorm, thanks for your awesome explanation.
I do not fully understand the nvbin flashing part.
I also have a backup I believe, but I am unsure.
I do have a proper nvram backup, so the proper files that are overwritten on flash.
With SP flash tool I get error 8038 when trying to flash.
Firmware upgrade is not working either even with all partitions.
I tried to remove __NODL__ from the nvram to fix it, but no luck.
Can you explain how to make that imei file and flash it with dd command or anything?
Would be awesome to get this problem fixed!
thank you
[update]guess what, you can do it with mtk droid tools 2.4.8 too!
I tried that before, but I used a backup I made after the issue.
Found an older one and it seems to work![/update]

guys..for permanent nvram, imei error or invalid use sn write tools.
mine solve a long ago..please read this: http://forum.xda-developers.com/showthread.php?t=2206421
http://forum.xda-developers.com/showthread.php?t=2197378&page=3
btw use a complete sn write tool
well works for me ,after factory reset everthing still as writen..
my phone mtk 6577 chipset based
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Phone is Dead (canvas 2)
ToldarkenHansam said:
Phone: Cherry Mobile Titan (Rebrand of Konka w990/Spice-mi 500/Axioo Picopad GEW)
Processor: MTK6577
Hello guys, this is my first post as I could no longer find any solution on the internet. Hoping some experts could help
I accidentally formatted the NVRAM of my phone using SP Flash Tool. The new update didn't have the option not to format it. Now my IMEI's are lost. Although it is still possible to restore them using some methods. But none of the methods I have found were permanent. A simple wipe/data factory reset from CWM Recovery removes it instantly. Is there a way I could restore the NVRAM, or at least make the restoration methods permanent?
Thanks in advance guys!
EDIT: I tried flashing all available ROMs (SP Flash Tool Based / Flashable Zips) but still it shows an invalid IMEI. I also tried restoring a backup of my stock ROM to no avail.
Click to expand...
Click to collapse
i have selected "whole format" option in format tab in sp tools. but doing this my phone got dead. pls help me

Revived your ZTE V793 now!
Ok guys..
I'll share to you my ROM for flashing using SP Flash Tools application.
Note: I'll not take any responsibility for any damage, warranty void to your phone
1. Download SP Flas Tools - find it in xda or Google..
2. Download this ROM : This is backup ROM porting to my android device kindly remove in-necessary applications. As it's ready to flash via SP FLASH Tools so basically it'll be straight forward thing. Link here :
HTML:
[URL="http://www.4shared.com/archive/iBNm1jxI/V793_Files_to_FlashTool.html"]V793[/URL]
Password :
[email protected]
3. Extract the file using 7zip. Then extract the ZIP file inside.
4. Open SP_Flash_Tools.. select the extracted files earlier and select the scatter file.
5. Everything will be pick automatically.
6. Take your phone battery. Press start and wait "Searching" and connect your Phone (without battery) using USB.
7. Make sure you have the driver. Installed the driver if necessary.
8. Wait until you get "Doughnut" OK button. Warning : Never disconnect the cable during this operation as it'll brick your phone forever.
9. Once, OK. please disconnect your cable. Put the battery into the phone.
10. Make sure the battery at-least 80% before you perform the CWM steps.
Good Luck! If you need any further guide please revert here.. I'll try to create another 'empty' ROM after this if there is a request. Thanks.
---------- Post added at 04:23 AM ---------- Previous post was at 04:15 AM ----------
rohitjaiswal said:
i have selected "whole format" option in format tab in sp tools. but doing this my phone got dead. pls help me
Click to expand...
Click to collapse
Hi there..
before perform any update please... and please backup your ROM.. that's the reason "MTKdroidtools" being develop.
Use the application to gain "temp" root to able you to get the image files.
Then create SP Flash ready files from the backup image files.
If you don't have the backup ROM don't be hesitate to search it in google and XDA forum.. if your phone is "unique" please ask your friend. Loan the phone for a few minutes to make a backup images.

NStorm said:
What a lame answers. Especially ones suggesting to root phone.
They guy clearly told he is able to restore MP0B_001 in phone, but its SOFT-IMEI and is lost after wipe/factory reset.
@ Original question by ToldarkenHansam, which is kinda outdated, but considering lame answers here:
To restore HARD-IMEI in NVRAM hidden partition use SN Write Tool or Maui META 3G. They are able to write hard IMEI and calibration to NVRAM partition.
@ kokabunga - if you have nvram.bin backup you can easily resore it with SP Flash Tool. Just open your scatter file with any text editor, find a __NODL_NVRAM section and remove __NODL_ part from it. Reopen scatter in SP Flash Tool and you'll be able to check NVRAM partition.
It might not be able to upload it without other parts selected. But you can you Options->Write memory, then manually enter start address, which will be show on download/upgrade page near NVRAM and length (your nvram.bin length) - that will always work. Be careful to write correct address thou.
Sidenote: all suggested methods before only touch SOFT-IMEI, stored in /data/nvram/md/NVRAM/NVD_IMEI/MP0B_001. Its lost with any wipe/reset, because whole /data partition are formatted. Then the whole /data/nvram directory (if it's empty) are restored from hidden NVRAM partition on EMMC. If you've corrupted your NVRAM when it won't restore correct IMEI ofc. With all methods mentioned above (i.e. replacing MP0B_001, echoing to pttycmd1, using mtkdroidtools, mobileuncletools and others) will only edit MP0B_001, i.e. soft copy of IMEI, which will be lost again with next hardware reset. Sure you restore your IMEI that way every time you wipe/reset/upgrade firmware. But its more solid to fix your IMEI partition with SN Write Tool / Maui META 3G so it will be correctly restored automatically from NVRAM at every wipe/etc.
EDIT: @Chrizzly92 this software are very outdate. It generates 24 byte MP0B_001 file, used by old MT6573/6513 platforms. Newer 6575/6577 uses 120 bytes MP0B_001 which are different. If you put 24 byte MP0B_001 generated instead from imei.c software, your phone will be buggy and will be constantly loosing IMEI every few hours until reboot. It's better to use MtkDroidTools or terminal method (echoing to /dev/pttycmd1) to correctly restore 120 byte IMEI file.
Click to expand...
Click to collapse
i have imei problem , i have tried all of ways to write/restore/repair imei but failed. i have radio problem. System/dev/radio/pttycmd1
Radio is empty. there is no pttycmd1 so i can't writ imei . please tell how i can restore pttycmd1 or whole radio restore on my device ?
is it possible ? please please reply me soon. thanks,
[email protected]:crying:

Solution of NVRAM.img and no-services Lenovo S820
javedsipra said:
i have imei problem , i have tried all of ways to write/restore/repair imei but failed. i have radio problem. System/dev/radio/pttycmd1
Radio is empty. there is no pttycmd1 so i can't writ imei . please tell how i can restore pttycmd1 or whole radio restore on my device ?
is it possible ? please please reply me soon. thanks,
[email protected]:crying:
Click to expand...
Click to collapse
Solution of NVRAM.img and no-services Lenovo S820...thanks

foox2k said:
Greetings NStorm i try your method i already got one backup with MTKDROID TOOLS so i can use the NVRAM.BIN , i already modify scatter file and try to write memory but i only receive red bar, no yellow or green, so i think it not work at all, any suggestions also sorry for my bad english im from Mexico, ohhh i forgot i already have a full backup from all the files in the smartphone do you know if i can FLASH the Full Backup back? or a CWM restore or other kind of solution?
Click to expand...
Click to collapse
if you have CWM backup so you can install CWM on your phone and make a backup of current OS, then put the CWM backup in it and restore it.
if you have MTK Droid tools backup then you first make a flash able backup by choosing MD5 file from the backup. then it makes a new folder !file_to_flashtools . this is your flash able backup with scatter file.
Open MTK flashtools and select the scatter file and choose download or upgrade firmware which you like. connect the PC with battery or without battery , choose the options for battery.
make sure your android adb interface driver and preloader driver and cdc drivers are installed ?
how to install drivers ?
on your phone and select development and check debugging option and connect with PC. PC install drivers automatically if you have windows 7 . stop that process and install drivers manually . second time switch off your device put the battery out for 15 sec and put it again but no phone on. just off mode. connect with pc and install its preloader driver. Now press the power button continuously on phone device its ask for CDC drivers. install it and now your drivers are done.
for further detail contact on [email protected]

NStorm said:
What a lame answers. Especially ones suggesting to root phone.
They guy clearly told he is able to restore MP0B_001 in phone, but its SOFT-IMEI and is lost after wipe/factory reset.
@ Original question by ToldarkenHansam, which is kinda outdated, but considering lame answers here:
To restore HARD-IMEI in NVRAM hidden partition use SN Write Tool or Maui META 3G. They are able to write hard IMEI and calibration to NVRAM partition.
@ kokabunga - if you have nvram.bin backup you can easily resore it with SP Flash Tool. Just open your scatter file with any text editor, find a __NODL_NVRAM section and remove __NODL_ part from it. Reopen scatter in SP Flash Tool and you'll be able to check NVRAM partition.
It might not be able to upload it without other parts selected. But you can you Options->Write memory, then manually enter start address, which will be show on download/upgrade page near NVRAM and length (your nvram.bin length) - that will always work. Be careful to write correct address thou.
Sidenote: all suggested methods before only touch SOFT-IMEI, stored in /data/nvram/md/NVRAM/NVD_IMEI/MP0B_001. Its lost with any wipe/reset, because whole /data partition are formatted. Then the whole /data/nvram directory (if it's empty) are restored from hidden NVRAM partition on EMMC. If you've corrupted your NVRAM when it won't restore correct IMEI ofc. With all methods mentioned above (i.e. replacing MP0B_001, echoing to pttycmd1, using mtkdroidtools, mobileuncletools and others) will only edit MP0B_001, i.e. soft copy of IMEI, which will be lost again with next hardware reset. Sure you restore your IMEI that way every time you wipe/reset/upgrade firmware. But its more solid to fix your IMEI partition with SN Write Tool / Maui META 3G so it will be correctly restored automatically from NVRAM at every wipe/etc.
EDIT: @Chrizzly92 this software are very outdate. It generates 24 byte MP0B_001 file, used by old MT6573/6513 platforms. Newer 6575/6577 uses 120 bytes MP0B_001 which are different. If you put 24 byte MP0B_001 generated instead from imei.c software, your phone will be buggy and will be constantly loosing IMEI every few hours until reboot. It's better to use MtkDroidTools or terminal method (echoing to /dev/pttycmd1) to correctly restore 120 byte IMEI file.
Click to expand...
Click to collapse
your method of writing memory manually worked for me to bring back my /dev/radio folder and its contents, still cwmr write my imei though

Lenovo s850 invalid IMEI

Sir,
Recently i hav flashed row in my lenovo s850 &it worked but when i sestarted my device for the first time it didn't shown me sims so i hav googled it, it said to type *#06# it showed me invalid imei, please someone help to solve this problem..

First root your phone then Install Root explorer.
Second open root explorer go to data and delete nvram folder
Third reboot your phone go to Recovery and wipe data or factory reset.
Then Reboot

How to Fixing Lenovo S850 no Service Issued, 100% Work - Got this posting from the comments one of blog reader, a lot people got this problems when modified Lenovo S850. Beside Lenovo S850 when you got invalid IMEI and no service issued on your device, you can fix it by restore the IMEI and it will fix the problems other then Lenovo S850.
I don't know this guide can be use for other china device or just Lenovo S850 so if you try to another please give some word on comment.
No service is cause by NV file corrupt, so using flash tool we gone read back NV file and the flash it back to our device, if you do right this procedure than it will revive your device from dead. Please read careful step by step because it think it will complicated.
Disclaimer : This guide for educational purpose only, We not responsible if your device bricked after following this tutorial. (DWYOR)
Download
• SP Flash Tool v3.1320 ↦ for this guide actually you only need the flash tool, you can use any version of flash tool but recommended to use v3 flash tool.
• S850_ROW_S215_150114 ↦ 1.1 Gb, because this guide is for Lenovo S850 then you need to download Lenovo S850 stock ROM, for another china device then you need to search it on the need.
• NV_RAM ↦ Lenovo S850 NVRAM block, cannot be use for another device.
How to Fixing Lenovo S850 no Service Issued, 100% Work
1. Download all files and place on the same folder, so you can easy to search the needed files. Extract the both files too and then go to flash tool extracted folder, run flash_tool.exe for windows 7 or later please use administrator privilege
2. After you can see the flash tool windows, now pressALT + CTRL + V. This will make flash tool run onAdvanced Mode, you can see on the flash tool windows bar. On the Download tab click Scatter-Loading button and the navigate to ROM extracted then select MT6582_Android_scatter.txt this will load all ROM files to flash tool.
3. Click Windows ↦ Write Memory this will add a tab, then select the Write Memory tab, like on the below picture
4. Open scatter file that you find on the extracted ROM, using word pad or notepad. Search for NV word, you will see three address on the scatter filelinear_start_addr, physical_start_addr andpartition_size. Put the linear_start_add on the Begin Address (Hex) and partition_size on the Container Length (Hex)
5. Click on Open RAW Data, select the NV_RAM file that already downloaded
6. Last click Write Memory button, turn off your device because Lenovo S850 using non removable battery you must make sure that your device is completely turn off, connect your device to flash tool using USB cable and flash tool will recognize your device and begin to start flashing process, wait until you can see GREEN CIRCLE in the middle of flash tool.
7. Done, disconnect then try to turn on your device and normal boot. See if the service already on and can be use on your device.
Done, Congratulations i hope your Lenovo S850 already fix and can be use to make call and receive messages again. Please leave comments if you found any problem or broken link regarding this guide
Credit: GSM Somanadhan (smartphon2016 blogspot in)

Thanks for your reply, does it will replace my serial number also?
My device serial number is also invalid.

Here is the solution for BOOTLOOP after 9.0 beta

Hello everyone ,
so , I've been this and here is what i did to get back to normal :​
1- download MiFlash and the oreo 8.1 (V9.6.8.0.ODHMIFE) fastboot image from here
2- download *adb* file that i upload , and extract the files
3- download this file ,and extract the files , you will find *TWRP* folder
4- copy or move *adb* folder to the C:\
5- use Miflash to flash the fastboot image
6- when your phone start bootlooping go to the fastboot in the phone
7 - open the *adb* folder and run *Command Prompt* , write *fastboot boot recovery.img*
8- when the TWRP start go to pc and copy *TWRP* folder and place it in the main internal
9-go to restore in TWRP and chose the backup folder , restore *Boot* and *EFS* and swipe (if it doesn't show anything to restore go to TWRP>backup and copy *2018-12-06--15-41-27_PQ1A181205006* folder into *TWRP* folder "not to backup folder")
10- now in TWRP go to reboot and click bootloader
11- you will go to fastboot , flash oreo 8.1 (V9.6.8.0.ODHMIFE) by MIflash
12- everything will get back to normal !! :highfive:
update (3-10-2019) :
i recommend to flash latest official mi a1 rom maybe well fix it (using fastboot) ,
any way here is new link for TWRP file http://www.mediafire.com/file/j6682qbs7qa5sg5/TWRP.7z/file
thanks to :
@joeyhuab for the advice
@berlin51 for the link
@abhishek987 for the recovery image file​

So this will not mess up any IMEIs or anything? Is this a universal solution for everyone who messed up?\
EDIT: Nevermind, used the guide, works fine. Thanks for that!

It's working. Thank you!
Just need to copy "2018-12-06--15-41-27_PQ1A181205006" to TWRP folder.

following the tutorial, but my sim card didnt work, any solution?

adnbwta said:
following the tutorial, but my sim card didnt work, any solution?
Click to expand...
Click to collapse
IMEI must've got corrupted
Dail *#06# and check if it is showing phone's IMEI numbers n not zeroes

UCFour said:
IMEI must've got corrupted
Dail *#06# and check if it is showing phone's IMEI numbers n not zeroes
Click to expand...
Click to collapse
imei still there, both sim, but in settings-imei SV both are 00, anyway to fix it?

adnbwta said:
imei still there, both sim, but in settings-imei SV both are 00, anyway to fix it?
Click to expand...
Click to collapse
SV values are zeroes by default
Try to flash the same fastboot rom again but this time via EDL mode [ fastboot oem edl] using miflash

UCFour said:
SV values are zeroes by default
Try to flash the same fastboot rom again but this time via EDL mode [ fastboot oem edl] using miflash
Click to expand...
Click to collapse
Can you explain a bit
Sent from my OnePlus5T using XDA Labs

If anyone is planning to flash Pie stable/beta
1. First take a backup of EFS from TWRP and Low level backup of all partitions ( system n data not needed ) with low level backup tool via EDL
2. In order to get Pie booted, you just need "System.img" extracted from the OTA ( use payload dumper) or just take the system.img file floating around here
3. Transfer System.img to adb folder >> Boot to fastboot and flash the system.img only
fastboot flash system_a system.img
fastboot flash system_b system.img
Everything works except dual 4G/VoLTE
Downgrade will also won't have any issues
> For Dual 4G/VoLTE, you also need to flash modem and rpm
fastboot flash modem_a modem.img
fastboot flash modem_b modem.img
fastboot flash rpm rpm.img
fastboot flash rpmbak rpm.img [ Optional]
But now if you try to downgrade , you might end up with bootloop
>> To Fix bootloop, boot to EDL
Flash the fastboot rom you were running before when you took back of partitions
Then Use lowlevel backup tool to restore all the partitions and reboot
---------- Post added at 08:38 PM ---------- Previous post was at 08:35 PM ----------
Amanpreetsingh said:
Can you explain a bit
Sent from my OnePlus5T using XDA Labs
Click to expand...
Click to collapse
Procedure is same as flashing fastboot rom via EDL mode with MiFlash but instead of flashing it from fastboot try it from EDL mode
Use this command within fastboot mode to get to EDL
fastboot oem edl
Total process will take 10+ minutes, once the flashing status changes to "Success", hold the power button for around 10 seconds to reboot

UCFour said:
SV values are zeroes by default
Try to flash the same fastboot rom again but this time via EDL mode [ fastboot oem edl] using miflash
Click to expand...
Click to collapse
done that, but the sim still not showing, tried to swipe sim to slot 2 but no change, really confused right now

adnbwta said:
done that, but the sim still not showing, tried to swipe sim to slot 2 but no change, really confused right now
Click to expand...
Click to collapse
Check if those IMEI numbers are your phone ones only? AFAIK EFS is device specific which contains information like IMEI, MAC Address..

UCFour said:
Check if those IMEI numbers are your phone ones only? AFAIK EFS is device specific which contains information like IMEI, MAC Address..
Click to expand...
Click to collapse
both IMEI in the settings and in the box are the same, but now after flash image from EDL both IMEI become 0 and unknown, any solution?

adnbwta said:
both IMEI in the settings and in the box are the same, but now after flash image from EDL both IMEI become 0 and unknown, any solution?
Click to expand...
Click to collapse
Use this guide
https://forum.xda-developers.com/mi-a1/how-to/guide-how-to-restore-imei-permanently-t3759190
1. Download 7.8.23 Nougat Fastboot rom, flash it via EDL
2. If the phone boots fine to OS, Great! [ IMEI fix only possible with Nougat ] else restore the EFS again via TWRP [ Don't restore anything else modem/boot] to get the rom booted
3. Download Qualcomm dailog driver, IMEI to Hex converter, HEX Editor and QPST tool [ Latest ]
4. Open IMEI to HEX Converter, inpur your IMEIs and save the hex numbers somewhere else
5. Now download the QCN file linked in this post, open the QCN with hex editor and navigate to the address locations 0x17C50 & 0x02530 and replace the hex values "08 8A 16 11 11 11 11 11 11" and "08 8A 26 22 22 22 22 22 22" with the ones you saved before and save the QCN file [ You can can .qcn extension if this file doesn't work in the final step ]
https://forum.xda-developers.com/showpost.php?p=76496159&postcount=23
5. Now type *#*#717717#*#* , you will see dialog port enable status
6. Connect phone to PC, enable Dev options and USB Debugging
7. Open QPST [ Software Download ], Restore Tab see if the port is showing. If it isn't update the driver within device manager
If the port isn't showing even after driver update, detach the phone USB and re-connect phone
8. with the Com port displayed, select browse under xQCN file tab and the select the QCN file u modified with your IMEI numbers
9. Select "Allow ESN Mismatch" and hit start >> wait until status changed to memory process done successfully (something similar)
10. Reboot phone and everything will be fine
After everything is done, first its better to update to Oreo via OTA first [ Two 1GB Updates ] and then flash oreo fastboot rom

UCFour said:
If anyone is planning to flash Pie stable/beta
Click to expand...
Click to collapse
Is that for people who flash it through fastboot or is this required if we update to the stable through OTA as well?

michkost858 said:
Is that for people who flash it through fastboot or is this required if we update to the stable through OTA as well?
Click to expand...
Click to collapse
There is no official fastboot rom yet, the one available has the contents of extracted payload.bin from the OTA
Even if you update your phone via official stable OTA, you will be facing same downgrade issues
Yeah i meant it for those who are planning to flash via fastboot as most OTA users with locked bootloader wouldn't bother to downgrade

Please help me I did the steps and manages to restore the stock rom, but I get a message saying "phone not allowed" And when I want to make a call tells me "mobile network not available "

UCFour said:
Use this guide
https://forum.xda-developers.com/mi-a1/how-to/guide-how-to-restore-imei-permanently-t3759190
1. Download 7.8.23 Nougat Fastboot rom, flash it via EDL
2. If the phone boots fine to OS, Great! [ IMEI fix only possible with Nougat ] else restore the EFS again via TWRP [ Don't restore anything else modem/boot] to get the rom booted
3. Download Qualcomm dailog driver, IMEI to Hex converter, HEX Editor and QPST tool [ Latest ]
4. Open IMEI to HEX Converter, inpur your IMEIs and save the hex numbers somewhere else
5. Now download the QCN file linked in this post, open the QCN with hex editor and navigate to the address locations 0x17C50 & 0x02530 and replace the hex values "08 8A 16 11 11 11 11 11 11" and "08 8A 26 22 22 22 22 22 22" with the ones you saved before and save the QCN file [ You can can .qcn extension if this file doesn't work in the final step ]
https://forum.xda-developers.com/showpost.php?p=76496159&postcount=23
5. Now type *#*#717717#*#* , you will see dialog port enable status
6. Connect phone to PC, enable Dev options and USB Debugging
7. Open QPST [ Software Download ], Restore Tab see if the port is showing. If it isn't update the driver within device manager
If the port isn't showing even after driver update, detach the phone USB and re-connect phone
8. with the Com port displayed, select browse under xQCN file tab and the select the QCN file u modified with your IMEI numbers
9. Select "Allow ESN Mismatch" and hit start >> wait until status changed to memory process done successfully (something similar)
10. Reboot phone and everything will be fine
After everything is done, first its better to update to Oreo via OTA first [ Two 1GB Updates ] and then flash oreo fastboot rom
Click to expand...
Click to collapse
i follow the tutorial, but the imei in phone is different with the one in the box, maybe I did something wrong in step 5, can u tell me how to change or remove imei?

adnbwta said:
i follow the tutorial, but the imei in phone is different with the one in the box, maybe I did something wrong in step 5, can u tell me how to change or remove imei?
Click to expand...
Click to collapse
If the IMEI is different then u haven't edited the QCN correctly
Flash Nougat firmware again via EDL
and this time edit the IMEI hex values correctly in the qcn file via hex editor
Also make sure u have converted your IMEI to hex values

for me nothing is showing in twrp folder in restore
pls help
i folled the steps in op properly
---------- Post added at 06:24 AM ---------- Previous post was at 06:01 AM ----------
jai krishna said:
for me nothing is showing in twrp folder in restore
pls help
i folled the steps in op properly
Click to expand...
Click to collapse
I took my own backup of boot and efs.so one folder created in twrp folder.
i replaced my files with the downloaded files given in op
thanks a lot.love u all

I have a question, I am on Android P official BETA flashed with TWRP. I have backed up my previous P PE ROM with Boot, EFS, Persist, Modem full Nandroid Backup. Can I flash official P STABLE (Fastboot ROM) with MiFlash Tool when its available?? Without bricking my device??

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

[TUTORIAL][GUIDE] Complete Guide on How to Properly Flash Baseband, IMEI, Wifi MAC, Bluetooth MAC, in Infinix Note 7, (X690, X690B, X690C)

I had an Infinix Note 7, Which I format all + downloaded from SP Flash Tool, everything was gone, after 6 Months of Trial and Error, here is How I fixed it.
BASEBAND FIX:
Prerequisites: Be on Stock Rom, (The one where Baseband was, AKA, the one you were using before you messed up.), Locked Bootloader, Download TFT Tools, (It is a Crack, so No links. Search on YT).
Open TFT Tools, and Go to Mediatek Section.
Go to Bottom Left, and Click Extras.
Click "Fix IMEI Baseband" and insert Infinix Note 7 by pressing Vol+Up Button.
It will take about 2-3 Minutes to fix.
Restart Device.
IMEI FIX:
Prerequisites: Close All Apps, Otherwise the Process may Crash, Locked Bootloader, Download AfterSalesTool v1.5.1, and Modem Meta v10.2044.0.02, and a Valid Baseband (Use Above Method to Fix Baseband.)
To Fix IMEI, open AfterSalesTool, and Select Infinix from the Phone Category, and Select Model as X606, I repeat, X606.
Click the Connect Button and Insert Mobile without Pressing any Buttons.
After 2-3 Minutes, The Progress Bar will become Green, and then the Details of Phone will be listed.
Open Modem Meta Tool. Click: "More" with the Option: "DUT in Meta Mode"
Change the Port to USB, and from Auto Connection to your Device. (Connect Mobile if not Visible).
Click Connect.
It will give an error, Click OK, plug out the Cable from PC, I repeat, from PC, not Mobile, then Reconnect it, and again click Connect.
Now it will completely Connect. Search IMEI Download, And Input ONLY ORIGINAL IMEI, (Check from the BOX BEHIND). (Otherwise, I am not responsible for Thermonuclear War, or Jail, as It is Illegal)
Click Write, 2-3 Times, to make sure, it is written.
Restart Device and dial *#06#, Congrats your IMEI is Back.
WIFI MAC & Bluetooth MAC:
Prerequisites: Locked Bootloader.
Open AfterSalesTool, Select Infinix from Category, Model as: X606.
Click Connect, and wait 2-3 Minutes till it is Connected.
Go to MAC Area, And the Heads are the Prefixes of your MAC Address, The First Head is for Bluetooth (BT Means Bluetooth), and the Second Head for WiFi.
If you have noted your WiFi and BT Mac, Well and Good, Go Flash it.
But, if you haven't, like me, go search for "MAC Address Generator - Generate Random MAC Addresses" and open the website.
Enter the Bluetooth Prefix and then select the format without any colons, or dashes.
Generate it, copy it, paste it in the AfterSalesTool.
If it says, it has an Illegal Character, again generate it, Try again. Keep trying till it successfully flashes.
Do the Same for WiFi Mac, copy its Head, Format without any colons or dashes, and generate.
Keep Trying till it Flashes.
Restart to check your MAC, it will also fix your NVRAM err = 0x10
And Viola, now you have WiFi MAC, and BT MAC, IMEI, and your Baseband Back!
Now Take a Backup through SP Flash Tool, as you Can't Take Any Risk.
Take Backup of NVRAM and NVDATA:
Prerequisites: SP Flash Tool, MTK Auth Bypass Tool, and a Phone with All those things Discussed Above.
Open Scatter File, Press Ctrl+F and search for NVRAM, note down physical_addr, and partition size.
Open SP Flash Tool, and Load MT6768 Scatter File.
Go to Readback Section, and click on add.
It will ask you to where to save it and *WHAT TO NAME IT*, Name it "Nvram.bin" (Name it exactly this or it will not detect in Restore) and click save.
Now it will ask the physical_addr and Partition size. Copy those values and enter there.
Click Ok.
Now click on Add again, it will ask for where to save it, Name it: "Nvdata.bin" (Name it exactly this or it will not detect in Restore) and click Save.
Now it will ask the physical_addr and Partition size, Go to Scatter file, Press Ctrl+F and search for Nvdata.
Enter those Values in the Respected Boxes in the SP Flash tool and click OK.
Disable Auth using MTK Auth Bypass Tool, or if you have Modified SP Flash tool, Disable Auth from there. and click "ReadBack".
Connect Mobile using Vol+Up.
It will back up in the Designated Place.
Restore NVRAM and NVDATA:
Prerequisites: Nvram.bin and Nvdata.bin of a Working Phone, SP Flash tool, and an unlocked Bootloader to avoid Errors.
Let's say you #### up again, and now, your IMEI and everything is gone, you want to flash the Backup now.
To flash it, Open SP Flash tool, and use this Modified Scatter File, to flash Nvram and Nvdata.
If you face any Checksum Error, Download Checksum Generator v5.1932.00, (Search it on Internet LOL) and Extract the ZIP and place it in your firmware, Cut the Original Scatter File, and place it somewhere, and place only the Modified Scatter there, and run the checksum generator as administrator.
Select Nvram and Nvdata Partition, Disable Auth, and use Download Only Mode, and Click Flash.
After 1-2 minutes, it will be complete.
After completion, restart your device, and Viola, Your IMEI and MAC's, and Baseband is back.
I hope this Tutorial Helped a lot of you guys, as there was not much Information for me available on internet on how to fix this exact Model, as it is too stubborn to go in Meta Mode.
If you need any Assistance, Reply to this thread, or PM Me. I will help you guys. Take Care!