I was not carful and I formatted my flash together with NVRAM information. Now I lost IME, Wireless MAC address and BT MAC address. If found a workaround for IMEI with AT commands but after restore the process needs to be repeated.
I found numerous programs that can recreate NVRAM information for MTK chipset but none of them are working for my Cube T8 plus. I guess it is a driver issue. I tried SN Write Rool, IMEIFix, MAUI Meta 3G and some other without success. They all fail on the second stage when T8 should wake from sleep.
SN Write Tool v2.1504 gives following output:
Searching preloader com port and handshake - OK as soon as I connected T8 which is shut down
Searching kernel com port and handshake - T8 gets stuck here, wakes from sleep and shows battery charging sometimes with META_MAUI_DB_INCONSISTENT or similar errors.
I tried 1.1_20151224 and 20160218 versions of firmware., with the same result.
When choosing the MD1 DB file, I tried both "BPLGUInfoCustomApp_MT6735_S00_MOLY_LR9_W1444_MD_LWTG_MP_V40_1_ltg_n" and " BPLGUInfoCustomApp_MT6735_S00_MOLY_LR9_W1444_MD_LWTG_MP_V40_1_lwg_n" with the same result.
I'm guessing that drivers are the problem. I can normally flash firmware but I guess for IMEI writing I'm missing something.
Drivers I used:
Driver_Auto_Installer_v1.1236.00.zip
MediaTek_USB_VCOM_drivers.zip
I tried on both windows 7 and windows 8.
If somebody managed to recover NVRAM information on Cube T8 using SN Write, please give me some info.
Cube T8 IMEI lost
Did you find away to get your INEI reinstalled on the Cube T8> Mine has gone as well
Hi, I have the solution you need mate
Always happy to help especially in such annoying thing you're experiencing. I had exactly the same thing, didn't notice I am downloading+formatting in the flash tool, lost everything, IMEI, MAC, everything!
Luckily, there's something that helps permanently (well, until you'll flash a new ROM which in that case you'll need to do it again). Only thing you must have knowledge with is with Xposed.
if you don't know what Xposed is, well my friend there's only that much of how I can help you
Follow the steps below to get your IMEI back:
1. Install Xposed (if you haven't done so regarless already)
2. Search and install the module called: Phone Id Changer
3. Activate the Phone Id Changer module and restart the tablet
4. You will now the App installed (Phone Id Changer)
5. Open the app, add your IMEI, MAC and everything else you'd like to add
6. Save Changes & Exit app
Voila, your problems solved.
Make sure to insert your IMEI and other details only, otherwise it is now allowed to do so.
Related
Hello,
I have an emei problem on my note 2 clone mtk6575
after searching and flashing and modding and learning , i have been able to boot android on this device after it got bricked while READING memory/nand from SP flash tool!!!
Now no emei , no baseband , and i do not even know were to start.
Tried mobile uncle tools, engineering mod , its says radio on , absent , but the AT command failed to send.
tried mtk droid tools , to restore my nvram.bin and .tar , and even to set the imei , its says pttycmd1 not found and nothing happens.
tried spflash tool , edited scatter file to enable nvram to show up , loaded the nvram image , but the spflash starts speaking about layouts , formatted , and used firmware upgrade mod , got an error , with no text string to explain.
tried to copy the nvram files from stock rom via adb , restarted , still the same.
logcat shows something about nvram like nvram not ready , nothing else , neither do dmesg.
the partition is mounted , or i wouldn't see the files under /data/nvram right? so mtd2 is not corrupted.
tried all the flashing tools , Maui META 3G , sn write tool , imei&sn writer .... all with the same issue:
the device goes into meta mode , and the cdc drivers are installed , detected and loaded with given virtual com port , but the utilities are all getting time out , they are sending commands to device but device is not answering , and the strange thing is i can adb shell to it , with aprox all stuff mounted , and no nothing in dmesg regarding modem , nvram , radio , usb ....
I have also tried a lot of other stuff , like copying my stock modem.img , resetting permissions under nvram , using write memory of SPFT to write the raw data of my stock nvram to nvram address ..... i do not know what i might be doing wrong as well as what i am exactly doing lol
I hope someone is actually having this issue or not but might be able to give a clue on what to do , since the past 2 month and thanks to the xda developpers forums and wikis i have diged into android, ported recoveries roms boot.img's , and just do not want to go for compiling kernels and building android from scratch yet...
Thanks in advance
Hello,
first of all, i have to say i am googling around and found nothing, exept how i use a scatterfile etc.
My problem:
After flashing a custom cwm with spflashtools to my jiayu g2f, i got the nvram warning under wifi.
This warning comes, because wifi/bt MAC is random and IMEI is lost.
This is reproducable.
So my question is:
All tutorials said, flashing a custom cwm with spflash is not a problem:
just select modem db file and scatter, select only the recovery and change the file to the custom one.
I take the custom one from needrom. It works, when
flashing via mtk droid, but when flashing with spflash, i get the nvram error.
I recognize, that the size of the file is another than the original size in the official rom. Isnt there a need of editing the scatterfile to fit it to the new size or is the recovery area on the phone big enough?
Today i make my own cwm via mtk droid tools and i flash it. Also with this, i am able to reproduce the nvram error.
For me, it is only possible to write the IMEI and WLAN MAC and BT MAC back with SN Station writer. All other tools
will fail on my device.
Thanks for reading,
Nine
So I got a cheap android tablet and I wanted to root it. I was successful so I decided to install TWRP. I searched for my specific model and found an image on a german forum. I downloaded and flashed it and it got stuck in a reboot loop. So I looked at the image and it was for the QV1030. I tried to get it into recovery but couldn't. Many sources told me to hold Vol Up and Lock, and I tried this and more. Nothing would make it enter recovery mode. Then I read about SP Flash Tool and found the stock rom for the tablet and decided I would try to flash that. It kept coming up with an error, and every source online told me to format the flash except for the bootloader and then I could flash it. So I did. Now it doesn't show anything on screen, and SP Flash Tool comes up with error 6045. But it does show up in device manager under com ports as, "MediaTek USB Port" so I think I can still do something about it. I don't have any backups. I don't know what I'm doing. I require assistance please.
So I reflashed the entire backup and it come up with no error. The logo comes up and it plays the chime. The logo does this little shimmer effect and once it gets to this screen, it shimmers indefinitely. If I plug it in, it begins installing a driver and then stops part way through.
drsinclair said:
So I reflashed the entire backup and it come up with no error. The logo comes up and it plays the chime. The logo does this little shimmer effect and once it gets to this screen, it shimmers indefinitely. If I plug it in, it begins installing a driver and then stops part way through.
Click to expand...
Click to collapse
I left it for about 5 minutes and it finished the driver. I thought it froze but I was wrong. It shows up now on device manager under Portable Devices as, "MTP USB Device". I tried to see if it was listed as a device by ADB. It is not. Lets just say I've already learned a thing or two about this stuff. Good thing I did it on an 80 dollar chinese tablet and not my HTC One M9
drsinclair said:
I left it for about 5 minutes and it finished the driver. I thought it froze but I was wrong. It shows up now on device manager under Portable Devices as, "MTP USB Device". I tried to see if it was listed as a device by ADB. It is not. Lets just say I've already learned a thing or two about this stuff. Good thing I did it on an 80 dollar chinese tablet and not my HTC One M9
Click to expand...
Click to collapse
I got it to work again mostly. So I realized that I wasn't flashing the whole backup. Some things didn't have a path and I had to set it manualy. Now it has CFW for some reason, but I reset it and it works now. The only thing is WiFi is not turning on. Any ideas about that?
drsinclair said:
I got it to work again mostly. So I realized that I wasn't flashing the whole backup. Some things didn't have a path and I had to set it manualy. Now it has CFW for some reason, but I reset it and it works now. The only thing is WiFi is not turning on. Any ideas about that?
Click to expand...
Click to collapse
I actually want to upgrade this from Android 4.2.2 to a more recent version. Do you guys have any ideas about that?
So I've come to the conclusion that while the device is no longer bricked, the current installation is written over the old one and things are conflicting. I know this because I looked through the cache and found filenames referring to apps I had installed before breaking it. So would the solution be to wipe the system partition and reflash the system.img so everything is fresh? Or does the problem lie elsewhere.
I formated the system partition, used SP Flasher to flash system.img and then did a factory reset. The issue has still not been solved. And now that I have done that, I don't have root access anymore. Framaroot says it was successful and I restart and check root explorer on ES File Explorer and it doesn't work.
I gained root access using a different method. However the WiFi still doesn't work. I think it may be that the mac address information was from the backup I flashed from the internet, and therefore doesn't match. I found a guide that tells me how to hex edit a file and put in my real mac address, but it's unavailable under wifi. I don't have the sticker on the back that says it either. How else can I find it?
Turns out the mac address can be anything. I used SN Write tool and an AB DB for my chipset and it still didn't solve the problem. I have no idea what to do. Can anyone help me?
I fixed the issue by grabbing a different backup from some russian website and flashing the system.img and secro.img to it. It now works fine 100%. Thanks
help - link
drsinclair said:
I fixed the issue by grabbing a different backup from some russian website and flashing the system.img and secro.img to it. It now works fine 100%. Thanks
Click to expand...
Click to collapse
Hey man! I have the same problems with my QV 830. Can you give me the link for system.img and secro.img, please?
Hello , Guys
Since you all probably know, Lenovo A7020a48 has Android 6.0 Marshmallow which cannot be rooted because of the following :
1 - We got a locked bootloader, we can't flash or boot into custom recoveries and sadly at the moment I couldn't find a way to unlock it.
2 - We don't even have a custom recovery made for that model yet, I tried different version of TWRP for A7020a40 ~ A7020a46 models and they all crashed upon booting to them.
3 - Kingroot and similiar apps can't root Android 6.0.
So the only way to root your phone would be to downgrade it to Android 5.1 Lolipop which is easy.
Here is download links for the stock roms :
A7020a48_LL_S125_160419_ROW.rar.7z
A7020a48_S259_160721_ROW.7z
When you finish downloading please don't forget that we are going to use the SP Flash Tool provided in the rom as only that version "SP_Flash_Tool_5.1552.00" worked for me with no errors however with latest versions i got problems.
Obviously you are going to install the USB drivers and CDC drivers located at the "DRV_Tools" folder in the rom you downloaded.
after installing the drivers correctly turn off your phone, open SP flash tool, and choose the scatter file located at : "\SW\target_bin\MT6755_Android_scatter.txt" and then choose "Download Mode" then wait for it to finish checking the files, then click on the download button on the top left corner.
Then connect your device and wait for it to detect the device .
Wait until the flashing is complete Then After the green circle appears, simply disconnect your phone and boot into system normally.
Note: You might see a black box in the bottom left corner saying "efuse flash done or similar stuff" don't worry about it" it won't appear again however if you got an error saying "DL image failed" then you did something wrong repeat the previous steps again and make sure you choose everything correct especially your rom.
Now to the last part, finish the first time setup screens by skipping most of them and DO NOT UPDATE YOUR SYSTEM AT ALL
if you got a notification to update, simply ignore it or press cancel, and open google chrome, download king root and wait for it to simply root you phone.
Congratulations that's the first part for rooting your phone.
Now to Fixing Your IMEI
Simply Enable USB debugging in options and enable OEM unlocking.
Then power off your phone.
Download this tool : MauiMETA_v9.1635.23.rar
Yes Again it has to be that specific versions, with other versions i couldn't connect to my device however with this version i could.
Extract it to a random location on your pc and MauiMeta.exe and click on options and enable "enable composite kernel usb (adb)" then click on reconnect.
Now you have to connect your device with usb and turn it on, don't worry MauiMeta will change the boot to META mode automatically after it starts booting leave it as it's and wait for the tool to connect to your phone.
***After it connects simply choose IMEI download and a new window should appear, first click on upload from flash button then click yes to retrieve the modem file from your phone, then simply type your IMEI ( Please note that changing your IMEI is illegal however you should only use this method to fix your IMEI not change it ! , you have been warned)
Note : IMEI numbers should be 15 numbers however with MauiMeta you should only type the first 14 number as the 15th number is only a checksum number and will be added automatically.
After typing the IMEIs and checking them simply click on download to flash.
After it says "flashing is successful" then close the window and click Disconnect, and your phone should turn off automatically and you should start it up again.
*** Note : If you have a corrupted NVRAM file on your phone then you are lucky since that rom comes with the modem db file as well to fix NVRAM issues, simply click "Change NVRAM database file" then click No to choose the file, The file exists in the ROM package you downloaded earlier in the following location : "SW\modemdb\MDDB_InfoCustomApp....etc.EDB" and continue the rest of the steps normally.
Please Note that I won't provide support for this, I have only created this tutorial to save time for other people and I'm not expert yet to fix all the problem you may face however after following these steps i managed to root my device and even fix the invalid imei errors i got.
Also if you found errors in my thread or mistakes Please let me know so i can fix them.
Good luck and Don't hard brick your phone XD
I get this error in SP FLASH TOOL 5.1552.00- STATUS_SEC_PL_VFY_FAIL (-10*****)
Any idea ?
Error coming?
i got the same error in SP FLASH TOOL 5.1552.00- (BROM ERROR : STATUS_SEC_PL_VFY_FAIL (-1073610746))
nishkarshxda said:
i got the same error in SP FLASH TOOL 5.1552.00- (BROM ERROR : STATUS_SEC_PL_VFY_FAIL (-1073610746))
Click to expand...
Click to collapse
Use This Version Of Flash tool enable usb and storage checksum hit download ( Use different usb port better use backside of CPU )
Sp-flash-tool-V5-1548
10000% Working
mobile not getting switched on after downgrading
Hi, I tried to flash my Lenovo vibe K5 note (a7020a48 4 GB RAM). It was done without any error but I couldn't switch on my mobile nor it was detected in my computer. Please help me
Bro i download and flashed successfully but phone cant turn on but i flashed again marshmallow phone will turn on...Why lollipop cant boot... Second link for rom is lollipop or not
Any proof?
Bro where did you get these two rooms from? Tell us the source. Otherwise, how will we know?
after flash mobile no on anybody can u help me to how to flash 5.0 in lenovo k5 note
It worked great thanks .......though minor glitches may occur such as not playing any sound and not supporting JIO sim card. These can be fixed by System Updating your phone to the latest version preferably through a sound wifi connection.
Hello guys,
I have come many times here to root my phone and I did success, thanks to you.
But now there is a new problem and I did not find any solution, then I will try to explain with my bad english what I did :
At first I tried to flash TWRP (an unofficial one many said it was working) on the phone after unlocking the bootloader, SP flash tool said it was successful.
But it was not, after reboot former recovery was still there, not TWRP (does anyone knows why it did not work ?).
I tried to install Lineage, which bricked my phone. After the debrick, I installed Android 10 GSI, and it worked but impossible to use MTP, Bluetooth or to download with the HTMLViewer (in other words, the system was unusable).
Then I reinstalled the ROM provided by Blackview, and installed Magisk, rooted the phone, also suppressing all the Google stuff it was possible.
And there is the main problem : I think I erased the NVRAM while unbricking the phone and then I have got an overlay of red chinese caracters on the corner of the screen. I tried to replace the original IMEI and MEID successfully with MAUI Meta, but chinese caracters are remaining here.
A screenshot of the ugly writings : https ://ibb.co/bWWp1wr
My phone is a Blackview BV9500 Plus.
Any suggestion about how to remove them ?
Thanks in advance !
I have just tried to replace the BT/Wifi adresses with SN Writer.
The soft said it was a success, but in the system parameters of the phone these adresses were not modified. I wonder why...
I guess these adresses (and/or the serial number, in others words all the parameters of the NVRAM) are the causes of the message. What do you think about that ?
Also, in the official firmware, there are some files for only one choice for the AP and MD databases (what are the correct ones ?).
I think I almost tried everything I am able to do...
Any suggestion or solution ?
Thanks
John Manjiro said:
I have just tried to replace the BT/Wifi adresses with SN Writer.
The soft said it was a success, but in the system parameters of the phone these adresses were not modified. I wonder why...
I guess these adresses (and/or the serial number, in others words all the parameters of the NVRAM) are the causes of the message. What do you think about that ?
Also, in the official firmware, there are some files for only one choice for the AP and MD databases (what are the correct ones ?).
I think I almost tried everything I am able to do...
Any suggestion or solution ?
Thanks
Click to expand...
Click to collapse
Hi John, same issue here, but not same process. Phone won't boot so I've restored which made IMEIs being 111111 and 22222. Used MetaModem (successor of AMUI Meta or whatever you used is called) to restore correct IMEIs. But got those red "TEE" and "Google" followed by Chinese chars. Will keep you updated here if I can find a solution.
@John Manjiro
It seem's Trusted Execution Environment (TEE) for Android is installed on your phone. It's a secure Operating System (OS) what runs in parallel to Android OS. TEE protects phone from malicious apps installed by the user and potential vulnerabilities that may be discovered in Android.
Did you ever find a solution to this?
huafu said:
Hi John, same issue here, but not same process. Phone won't boot so I've restored which made IMEIs being 111111 and 22222. Used MetaModem (successor of AMUI Meta or whatever you used is called) to restore correct IMEIs. But got those red "TEE" and "Google" followed by Chinese chars. Will keep you updated here if I can find a solution.
Click to expand...
Click to collapse
I'm having the same issues with a BV9800 Pro.
cnorman27 said:
I'm having the same issues with a BV9800 Pro.
Click to expand...
Click to collapse
Still same issue, got a long email thread with BlackView team which tried to help even tho they seem to not get well my Enlgish. They keep giving me a version of SNWritter where I had to modify some ini file in some tee subfolder. But the exe couldn't launch and was complaining about MVC100.dll missing. I could fix that by downloading from the web a SNWritter tool with working exe. Now I need to find some special screwdriver so that I can remove the battery from the phone. Doing so will keep the phone appearing as MT65XX Preloader in the devices manager and not for only one second...
Just FYI, I gave up and was using it with this **** red overlay.
Last week I was really bored of this overlay so I've installed AOSP 10 GSI. Tho it doesn't pass safety net, and believe me I've tried many way to make it pass. So I cannot use most of my banking apps + no google pay :-(
I even tried with AOSP 9, 10 and 11, as well as LineageOS 15, 17 and 18... unable to pass safety net even with universal safety net fix, magiskhidepropsconf, ...
Hahaha, looks like I just needed to write the previous post and finally got it wokring on PixelExperience Android 10 rooted and passing SafetyNet!!!!
Quick howto if someone is interested:
with SPFlashTools, restore the original ROM
Activate developer mode + USB debug
on the computer, adb reboot bootloader
Download PixelExperience system image and extract it (on linux with unxz) - I've tried many other ROMs with no success. Also while the device is not an A/B, you must download A/B images else they do not work.
fastboot -w && sleep 1 && fastboot flash system path/to/downloaded/system.img && fastboot reboot
Skip everything you can skip at first boot (you can restore later from an online backup or another android phone)
Download MagiskManager apk
adb push path/to/MagiskManager.apk /sdcard/download/
On the phone go in the file manager in download folder and install MagiskManager
copy the boot-signed.img from stock ROM on the device adb push path/to/boot-signed.img /sdcard/download
Open Magisk Manager, install, uncheck the first checkbox (to disable encryption, I forgot the exact label) but keep "recovery mode" checked, then click on next, then second option (patch boot image) and select the boot-signed.img you uploaded on step 10
download on your computed the patched image using adb pull
adb reboot bootloader
fastboot flash boot path/to/downloaded/patched-boot-magisk.img
You need to reboot in recovery mode, this is important: press power and volume up until you see the Blackview logo (can take up to 40 seconds)
select "reboot" (first option) in the recovery mode
once rebooted, open magisk manager, activate magisk hide and go in plugins.
install MagiskHideProps Config but do not reboot yet
install SafetyNet fix (download from here, it's not in online modules)
click on reboot
It'll reboot in recovery, that is normal and you MUST boot your device into recovery each time you need to boot/reboot it. Once in recovery, as before select reboot
Once it has rebooted, go in magisk and change in the settings so that the default method is not "prompt" but "grant".
from your computer:
adb shell
su
props
Select device fingerprint, then choose from certified, google, pixel 2, android 10
confirm but do not reboot when asked, simply exit
adb reboot recovery
again, select "reboot system"
Once booted, open Magisk Manager, click SafetyNet, it should pass SafetyNet.
Scroll down notification, and choose "continue device setup"
continue as normal the setup of the bv9500 plus!