Hi,
I want to make some changes via qpst but every time I try to write something it says read-only.
Related
Hello xda friends.... im new here and i need a help from u guys. Please help mee..
i just bricked my micromax magnus a117. What i did--- rooted my phone then installed an app meteos6589 (something like that) to increase app storage. Then i restarded my phone(with usb debugging off(if it afffects anything )). And after that it is showing micromax logo only.
so anyway i downloaded stock rom v4 from mounlisky. and tried to flash with sp tools. But but but problem is arising something like "pmt didnt mathched...................." . So sp tools is saying to select and do format+download option. But i have nothing in backup only microsd and internal sd data.
So the point is i dont have backup of nvram or anything else, phone is bricked at micromx logo, usb debugging off. So how do i get my phone back to life.
anyone please....
Any detailed help is appreciated.. thank you..
so i did it. i flashed it with stock rom. and as i was afraid of it, imei erased. but i got imei back by using mtkdroid tool(got imei numbers under mobile battery) but serial number,bluetooth address lost and in wifi showing avirtual wifi named nvram warning:err= 0*10. how to get them back?
ranganitesh said:
so i did it. i flashed it with stock rom. and as i was afraid of it, imei erased. but i got imei back by using mtkdroid tool(got imei numbers under mobile battery) but serial number,bluetooth address lost and in wifi showing avirtual wifi named nvram warning:err= 0*10. how to get them back?
Click to expand...
Click to collapse
This is a trap that I have fallen into also in the early days of my MTK experience. The way MTKDT backs up data is NOT sufficient to restore a phone or tablet back.
(Sorry, I will rant for a few)
MTKDT backs up the /data/nvram files. I almost wish MTKDT didn't exist because people think they have a copy of everything they need, but it is not everything they need as you've found. (it may have improved since my knowledge is old) The proper thing to do is backup the "NVRAM" block with SP Flash Tool. You would determine where it was by looking at the scatter file. A better safeguard is to backup the whole ROM with SPFT, then you don't even have to worry about offsets, because your offset is 0x0.
Sidenote:
When you wipe the /data partition, the /data/nvram that you've restored using MTKDT will be wiped also. So you will have to restore it again.
I think where you are at now, your only option is to inspect the NVRAM block by dumping it to your computer. You will probably also need to inspect someone else's NVRAM block that has the exact model you have. From there you can look at it with a hex editor and try to figure out how to put your information back. I have to admit, I've only had limit success in doing this. I've found for example where the Wifi MAC should go, but it repeats at different locations within the block and I think I was never successful. To check to see if your hexediting is correct, you wipe /data. On first boot MediaTek's linux/android creates the /data/nvram/* files from what it finds in your NVRAM block.
I'm sorry I'm not more help.
syserr said:
This is a trap that I have fallen into also in the early days of my MTK experience. The way MTKDT backs up data is NOT sufficient to restore a phone or tablet back.
(Sorry, I will rant for a few)
MTKDT backs up the /data/nvram files. I almost wish MTKDT didn't exist because people think they have a copy of everything they need, but it is not everything they need as you've found. (it may have improved since my knowledge is old) The proper thing to do is backup the "NVRAM" block with SP Flash Tool. You would determine where it was by looking at the scatter file. A better safeguard is to backup the whole ROM with SPFT, then you don't even have to worry about offsets, because your offset is 0x0.
Sidenote:
When you wipe the /data partition, the /data/nvram that you've restored using MTKDT will be wiped also. So you will have to restore it again.
I think where you are at now, your only option is to inspect the NVRAM block by dumping it to your computer. You will probably also need to inspect someone else's NVRAM block that has the exact model you have. From there you can look at it with a hex editor and try to figure out how to put your information back. I have to admit, I've only had limit success in doing this. I've found for example where the Wifi MAC should go, but it repeats at different locations within the block and I think I was never successful. To check to see if your hexediting is correct, you wipe /data. On first boot MediaTek's linux/android creates the /data/nvram/* files from what it finds in your NVRAM block.
I'm sorry I'm not more help.
Click to expand...
Click to collapse
So what files are needed to be backup along with mtk droid tool, just wanna know.
ranganitesh said:
So what files are needed to be backup along with mtk droid tool, just wanna know.
Click to expand...
Click to collapse
I don't use MTKDT at all. I do see some uses for it though. SPFT is a pain, but I wish every device (SoC maker) had an SPFT so you could read or write any chunk of flash.
If you look at a scatter file you will see lots of blocks/partitions that the flash is divided into. Each of these has a purpose of course, but the one marked NVRAM (a horrible confusing name) is the most important to get backed up, it has unique "calibration data" for your specific unit. You may find a "nvram.bin" that MTKDT created... this may be exactly what SPFT would backup too... if you are lucky.
So if MTKDT made a nvram.bin that is about 100x better than having a nvram.tgz or however he archives the /data/nvram files.
I have a serious problem with my Elephone P6000 (MTK6732). Following a freeze, it seems my internal storage got corrupted. After a few attempts at fixing the issue by wiping and formatting in recovery, I resorted to a clean flash through SPFT. SPFT looks like it's working, but I suspect it's not actually writing anything, because:
- the format part of the operation is way too quick
- I am not injecting a custom recovery in the scatter file, but my custom recovery remains functional on the phone
- nothing changes in terms of normally booting the phone (i.e. it doesn't)
I have some I/O errors in dmesg, and I very well understand this could simply be a case of hardware failure that no amount of hacking can fix, but I read this is not always the case so I am still giving it a shot.
I also tried using parted via adb, but the changes I make don't seem to persist. I can still mount and unmount /cache and /system and their contents don't appear to be damaged. I wanted to give SP Multiport Flash a shot, but it complains about the COM port and I can't figure out how to set it properly.
Is there anything left to try or should I assume it's indeed a hardware problem? SPFT not working really concerns me. Would a nandroid backup help? I think I made one a few months ago and I am looking for it on my PC but I haven't found it yet. For clarity, I can still boot into Fastboot and CWM, I can still use a shell via ADB and SP Flash Tool still talks to the phone.
Forgive me fot bumping this but it would be great to get some help.
Hi,
You've asked in the correct section: http://forum.xda-developers.com/android/general/p6000-thread-bug-fixes-faq-info-t3028845
so I'll close this thread.
Good night, I did the formatting and installation on my BLU PURE XL, but I can not do IMEI'S correction by Write Tool v2.1504.00, it starts loading and stops and gives error, I'll show the files I have below, I want to know Which are the correct ones and if there are new ones.
Help me please.
Thank you
APDB_MT6795_S01_L1.MP5_W15
APDB_MT6795_S01_L1.MP5_W15.31_ENUM
BPLGUInfoCustomAppSrcP_MT6795_S00_MOLY_LR9_W1423_MD_LWTG_MP_V40_P27_1_ltg_n
BPLGUInfoCustomAppSrcP_MT6795_S00_MOLY_LR9_W1423_MD_LWTG_MP_V40_P27_1_lwg_n
It's better you to write down the original IMEIs which you should have under the back cover and install an app called "Chamelephone". You can find it in the Play Store, but you'll need root access to ise it. Good luck!
Cheers
I have made a mistake trying to change a rom for my device (huawei g8 ri0-l01).
I thought my phone was gone, but step by step I was able to bring it back to life.
Now I have a working rom and I set back the IMEI's, but I still have "no service".
After reading a lot, I understand that I need to recover my "NVRAM" and to do so, I need for somebody to send my a file called "NVRAM.IMG" which applies to my device.
I can't find this file anywhere on the net.
Can somebody please send me?
umerbloch said:
I have made a mistake trying to change a rom for my device (huawei g8 ri0-l01).
I thought my phone was gone, but step by step I was able to bring it back to life.
Now I have a working rom and I set back the IMEI's, but I still have "no service".
After reading a lot, I understand that I need to recover my "NVRAM" and to do so, I need for somebody to send my a file called "NVRAM.IMG" which applies to my device.
I can't find this file anywhere on the net.
Can somebody please send me?
Click to expand...
Click to collapse
bro there is no NVRAM.img partition in phone
You probably mean efs folder
we need modem modem1 and modem2 files. if your phone is rooted you can use partitions backup in play store. it automatically marks them yellow. on the wrench key choose img format. and share it with us. I will strongly apreciate you.
I have a Lenovo tab 2 A10-70l mt8732. It received an official update to marshmallow a while back. After update, the official recovery didn't backup properly. Error can't perform backup was the message. Even though the files were created, they showed checksum fail error while restore. Due to my need to backup, I flashed my tab with splash tools and files given in official forum. After flashing, I tried to root using the superuser install button in twrp. The screen went totally blank and there was no response. In a hurry, I gave full factory reset and flashed my device. On switching on, there was an invalid IMEI sign under network settings and many device information were missing. I learns that I have corrupted my nvram folder. I have no backup with me. I can use any flash file or terminal commands but will have no access to PC or laptop for a long time. It would be very convenient if you provide help by instructions. I would be grateful for both of based and independent solutions. Feel free to ask any other info of my tab. Since I have deleted and custom installed a ROM, I am ready to take risks if they are promising.